</snip> -----Original Message----- From: john gilmore On the other hand
//SYSPRINT DD DSN=NULLFILE,BLKSIZE=0,LRECL=137,RECFM=VBA can be altered readily by simply supplying a different licit value of DSN=. This difference was the basis for my statement that DSN=NULLFILE was superior to DUMMY when used inside procedures. </snip> I believe we used the same technique for input datasets in the concatenations. It was easy for our users to call a procedure specifying //STEPXX EXEC PROC,PROJLIB1=XXX,PROJLIBY=YYY,USERLIB1=ZZZ,USERLIBZ=WWW that is, editing only the dataset names, which generated something like //SOMELIB DD DISP=SHR,DSN=GENERAL.LIB1 <-- hardcoded (while mandatory) . . . // DD DISP=SHR,DSN=GENERAL.LIBX <-- hardcoded (while mandatory) // DD DISP=SHR,DSN=XXX <-- substitution PROJLIB1 . . . // DD DISP=SHR,DSN=YYY <-- substitution PROJLIBY // DD DISP=SHR,DSN=ZZZ <-- substitution USERLIB1 . . . // DD DISP=SHR,DSN=ZZZ <-- substitution USERLIBZ // DD DISP=SHR,DSN=NULLFILE <-- default parm value . . . // DD DISP=SHR,DSN=NULLFILE <-- default parm value Generallly, the users were not supposed to be good in JCL, and there were maybe 3 copies of JCL manuals for all of us (system programmers, aplication programmers, and users). That was the time before we moved to ISPF panels and skeletons. Zaromil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
