|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),
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?