>>> JCL has similar archaic restrictions. Why not code > BLKSIZE=0,SPACE=(10000000000,5000000000) -- (10 GB primary, > 5 GB secondary), amounts very reasonable with modern DASD, and > let the OS make the determination of blocks, tracks, or cylinders?
Paul, May be use AVGREC ? https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab600/iea3b6_Examples_of_the_AVGREC_parameter.htm https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.idad400/d4274.htm Thanks, Kolusu IBM Mainframe Discussion List <[email protected]> wrote on 04/21/2017 10:52:41 AM: > From: Paul Gilmartin <[email protected]> > To: [email protected] > Date: 04/21/2017 10:52 AM > Subject: SPACE parameters (was: FTP Failing with space issues) > Sent by: IBM Mainframe Discussion List <[email protected]> > > On Thu, 20 Apr 2017 18:11:33 +0000, Nims,Alva John (Al) wrote: > > >The closest you can get even in 2.02 is to use; BLKsize=### and BLocks . > > > Which goes against IBM's current recommendation to specify BLKSIZE=0 > and to allow SDB to operate. > > JCL has similar archaic restrictions. Why not code > BLKSIZE=0,SPACE=(10000000000,5000000000) -- (10 GB primary, > 5 GB secondary), amounts very reasonable with modern DASD, and > let the OS make the determination of blocks, tracks, or cylinders? > > Programmers focused on foreign systems such as the OP shouldn't be > burdened with knowing details of IBM DASD geometry. > > And why does the ridiculous limit, "Syntax allows for values of 0-16777215" > persist in an OS running on 64-bit hardware? > > --gil > > ---------------------------------------------------------------------- > 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
