Space Allocation

grem · Posted: Tue Sep 11, 2012 7:49 am

Hi,

What if i have a declaration of SPACE below. and i have 7thousand inputs and all record should be wirtten on the OUT1 is this possible that my job will not abend on SPACE issue but instead not all processed records will not be written on OUT1?

//OUT1 DD DSN=FILE.QX0999.COPY.D120611,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(00080,(5,2),RLSE),
// RECFM=FB,LRECL=25

dick scherrer · Posted: Tue Sep 11, 2012 7:57 am

Hello,

No - when you run out of space, the job is terminated. Unless someone has done something to allow it to continue.

Suggest you change the SPACE to CYL rather than 80.

Bill Woodger · Posted: Tue Sep 11, 2012 8:43 am

As has been indicated, there may be something at your site which causes that behaviour (traps the space abend(s)), but the normal thing would be an abend.

Ask your colleagues or technical support.

grem · Posted: Tue Sep 11, 2012 8:51 am

thanks for your reply

Pete Wilson · Posted: Wed Sep 12, 2012 4:07 pm

What you have coded won't be enough as you're only requesting space for 5 blocks of 80 bytes primary, and 2 blocks of 80 bytes secondary space.
/ SPACE=(00080,(5,2),RLSE),
// RECFM=FB,LRECL=25

Suggest you code the following which requests enough space for 7000 records of 25 bytes in Primary space, and another 2000 for Secondary space.

/ SPACE=(25,(7,2),RLSE),AVGREC=K,
// RECFM=FB,LRECL=25

Anuj Dhawan · Posted: Wed Sep 12, 2012 8:55 pm

Okay, I've not verified so I might be mistaken but coding block size in 2012 sounds bit odd, no? It was a choice when programmers has to be smart enough to work with different DASDs with differnt geometries. With 3390 DASD packs, SMS and ACS available now, coding CYL or TRK with RLSE should be a good choice. As they say, please correct me if I'm wrong...

dick scherrer · Posted: Wed Sep 12, 2012 9:22 pm

Hi Anuj,

Anuj Dhawan · Posted: Thu Sep 13, 2012 5:40 am

Thanks Dick.

Pete Wilson · Posted: Thu Sep 13, 2012 12:30 pm

This is NOT requesting space in blocks. With the AVGREC parameter it is asking for an allocation based on expected numbers of records (7000) of a given lrecl (25) and the system then simply converts this to a TRK or CYL value for the allocation.

The AVGREC is a multiplier factor and can be U, K or M (unit, kilo, mega). (Without the AVGREC parameter it would be treated as a block allocation request.)

// SPACE=(25,(7,2),RLSE),AVGREC=K,

This is a preferable method for Users to allocate space rather than TRK or CYL as they probably know roughly how many records they're dealing with and the LRECL, so requesting space based on that knowledge without having to be aware of things like trk/cyl geometry is inifinitely better.

That is why this parameter was introduced about 20 years ago!

The equivalent in IDCAMS are the KILOBYTES and MEGABYTES keywords, combined with RECORDSIZE.

Anuj Dhawan · Posted: Thu Sep 13, 2012 2:37 pm

I'm sorry Pete. My question was posed in general and was for original poster...

Pete Wilson · Posted: Thu Sep 13, 2012 2:54 pm

No worries Anuj. At least the User gets a fuller explanation!

ps: I don't use it, but I'm not sure if block allocation is really a problem as long as BLKSIZE is ommitted or coded as 0 to get SDB.

dick scherrer · Posted: Thu Sep 13, 2012 9:38 pm

Hello,