Hi Phil,
You said: "...The SYMBOLS= stuff might help here ..."
"might"??? -- No! ... "will"
Here is another one you might like. (I use it to rename Cataloged
Procedures during software upgrades.)
// EXPORT SYMLIST=*
// SET DSN=my.PROCLIB
// SET VOLUME=xxxxxx
// SET MEM=member,NEW=member$,BKP=member@
//STEP001 EXEC PGM=IEHPROGM
//SYSPRINT DD SYSOUT=*
//DF0910 DD DISP=SHR,UNIT=3390,VOL=SER=&VOLUME
//SYSIN DD *,SYMBOLS=JCLONLY
SCRATCH MEMBER=&BKP, X
DSNAME=&DSN, X
VOL=3390=&VOLUME
//STEP002 EXEC PGM=IEHPROGM
//SYSPRINT DD SYSOUT=*
//DF0910 DD DISP=SHR,UNIT=3390,VOL=SER=&VOLUME
//SYSIN DD *,SYMBOLS=JCLONLY
RENAME MEMBER=&MEM, X
NEWNAME=&BKP, X
DSNAME=&DSN, X
VOL=3390=&VOLUME
RENAME MEMBER=&NEW, X
NEWNAME=&MEM, X
DSNAME=&DSN, X
VOL=3390=&VOLUME
Regards,
David
On 2023-08-25 09:57, Phil Smith III wrote:
Gil wrote:
Is he too sharp tobe wrong?
Of course not. Why would you say that? I just meant that he was explicit about
it, had used variables/symbols wherever possible, couldn't get them to work in
this case.
What's he mean by "not just the single SET statement for each."?
It appears as if one SET can't govern multiple applied occurrences.
In what language is that true? Did it antedate "DD *,SYMBOLS=JCLONLY"?
It means that you set the variable and use it and it *doesn't get substituted*
in these cases. So the job fails with
INVALID DATA SET &whatever.
And yes, this most certainly predates z/OS 2.1. The SYMBOLS= stuff might help
here; will tinker, thanks! (Yes, you mentioned it before, but I didn't quite
take it in.)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
