That first sentence should have read "does not generate". :>: -----Original Message----- :>: From: IBM Mainframe Discussion List [mailto:[email protected]] On :>: Behalf Of retired mainframer :>: Sent: Saturday, April 12, 2014 8:34 AM :>: To: [email protected] :>: Subject: Re: IEBGENER PARM='SDB=?????' :>: :>: The SDB parameter does generate the optimum blocksize. It only controls :>: whether the generated blocksize can exceed 32760. Refer to the first :>: part :>: of the EXEC statement section in the IEBGENER chapter of the DFSMSdfp :>: Utilities manual. :>: :>: Note that for LARGE, the output CAN be greater than 32760 but the manual :>: gives no clue as to when it actually will be. :>: :>: :>: -----Original Message----- :>: :>: From: IBM Mainframe Discussion List [mailto:IBM- :>: [email protected]] On :>: :>: Behalf Of Paul Gilmartin :>: :>: Sent: Saturday, April 12, 2014 7:06 AM :>: :>: To: [email protected] :>: :>: Subject: IEBGENER PARM='SDB=?????' :>: :>: :>: :>: What value of IEBGENER PARM='SDB=?????' is intended to allow SDB :>: :>: to operate and select an optimum BLKSIZE for SYSUT2 regardless of :>: :>: the BLKSIZE of SYSUT1? I have tried all five documented values (YES, :>: :>: NO, LARGE, SMALL, and INPUT), and each case SYSUT2 was created :>: :>: copying BLKSIZE from SYSUT1. :>: :>: ---------------------------------------------------------------------- :>: For IBM-MAIN subscribe / signoff / archive access instructions, :>: send email to [email protected] with the message: INFO IBM-MAIN
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
