Re: JCL SPACE ALLOCATION ISSUES

From: Clark F. Morris, Jr. (cfmtech_at_istar.ca)
Date: 02/27/04 

Date: Fri, 27 Feb 2004 13:35:33 -0400

Also make certain that you are getting blocked output. Under certain
circumstances (primarily copying from VSAM), SYNCSORT will default to
BLOCK 1 RECORD. The same may be true for SAS

Colin Campbell wrote:

> It is clear that your data set space requirement exceeds the limit for a
> single volume. You can request multiple volumes. You can also try to
> use "extended" sequential data sets, if your shop uses DFSMS to manage
> most of its DASD. The limit on one volume is the 64k tracks you saw in
> the messages if you don't use "extended".
>
> 55 million records by 242 bytes / record is approx. 13 x 10**9 bytes. A
> track holds less than 6 x 10**4, so it would appear you need something
> on the order of 220,000 tracks.
>
> I'm going to bet your input is on tape (and most likely multiple tapes,
> at that). Ever wonder why? (Grin)
>
> You probably need to check with your space management people to see if
> you can store this amount of data on your system's DASD.
>
> Finally, if identifying the record type(s) is relatively simple, you
> should be using your installation's SORT program to select the records
> and send them to the different output data sets. The commercial SORT
> programs are well known to do very efficient I/O.
>
> Mainframe SAS is a renowned CPU and other resource hog. At our shop,
> SAS is not an approved tool for use in production jobs, although a few
> programs have snuck in. One manager had one SAS program recoded in
> COBOL, and reduced the CPU usage by 94.7%.
>
> No matter how easy you find coding in SAS, you could have told SORT to
> split the data more easily.
>