Date: Wed, 26 Jun 1996 11:13:45 PDT
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
Subject: Re: Libnames on MVS
Hays, I will not say it is impossible to run your jobs on MVS against
datasets on VM, but it would be worth a SUGI paper. If you keep the
results on MVS, it will be easier. By the way, where is your raw data?
I normally allocate my MVS datasets in JCL. We (the list--not you) have
previously discussed whether it is better to use JCL or libnames in MVS.
I will try to cover both approaches.
If you use JCL, the creating JCL will look like:
//NEWDISK DD DSN=HAYS.DISK.DATA.HISNAME,
and you do not need a libname statement. Once the data exists, the JCL
would look like:
//OLDDISK DD DSN=HAYS.DISK.DATA.HISNAME,DISP=(OLD,KEEP,KEEP)
If you do not allocate in JCL, the libname to create a database will
LIBNAME NEWDISK 'HAYS.DISK.DATA.HISNAME'
and the libname to use existing data will look like:
LIBNAME OLDDISK 'HAYS.DISK.DATA.HISNAME' DISP=OLD;
By the way, this assumes disk--the syntax is slightly different for
Tim Berryhill - Contract Programmer and General Wizard
Frequently at Pacific Gas & Electric Co., San Francisco
The correlation coefficient between their views and
my postings is slightly less than 0
----------------------[Reply - Original Message]----------------------
I am submitting the MVS jobs from my CMS ID and would prefer to get the
physical file back on my CMS ID. Short of that, I could work with the
being created on MVS.