LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (March 1998, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Fri, 6 Mar 1998 02:59:56 GMT
Reply-To:   LPogoda <lpogoda@AOL.COM>
Sender:   "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:   LPogoda <lpogoda@AOL.COM>
Organization:   AOL http://www.aol.com
Subject:   TSO and GDG's

I have an SCL application on TSO. Everything's fine, but some of the nervous nellies in the office would -like- daily transactions processed by the system to be written out to a flat file, preferably a GDG. Each day's transactions would be written to the +1 bias number. Therein lies the problem.

At this installation, coding a GDG in JCL looks something like this: //DD DAILY DSN=XXXXXXXX.XXXXXXXX.DAILY.TRANS(+1), // DISP=(NEW,CATLG,DELETE), // DCB=(DUMMY,LRECL=80,SPACE(TRK(10,10)),RECFM=FB,BLKSIZE=0) // UNIT=SYSDA

In the DCB clause, BLKSIZE=0 tells the OS to assign an "optimum" blocksize, and DUMMY references the GDG base. The file created will have as the last qualifier G0001V00, G0002V00, etc.

Well, that's OK for a batch job, but this particular app doesn't run in batch. I can code all the parameters I need in a FILENAME statement FILENAME function *except* the DMMY. No matter where I put it, SAS says this isn't a valid option for a filename. Without it, the OS tells me it can't find the base index, and the file isn't created.

Anyone have any suggestions?


Back to: Top of message | Previous page | Main SAS-L page