FWIW, I have had problems with substitution when e g: //S010 EXEC XXXXXX,PARM='&ABC.BBBB'
Didn't work but with: //S010 EXEC XXXXXX,PARM=&X'&ABC.BBBB' It worked. &X is a dummyvar set e g in the PROC stmt as X=,OTHERPARM=YYY. Or by a SET stmt. Other suggestions posted may be better solutions, but this may work. Thomas Berg "I wash off the hatred of my enemies and the greed and wrath of powerful people." “I clearly saw the skeleton underneath all this show of personality. What is left of a man and all his pride but bones?” Den ons 19 nov. 2025 00:13Phil Smith III <[email protected]> skrev: > As those who have been following along will remember (i.e., probably > nobody, as you have your own fish to fry) I've been trying to simplify our > product installation process by centralizing variables in a JCLLIB member. > This went on hold for a while but now we're trying to finish it up, and are > hitting a problem that I'm hoping someone will have a hint about. Apologies > where I use incorrect terminology; please do correct me! > > The F1 relfile is the JCLIN data. Ours includes: > //SYSLIN DD * > LIBRARY '&USSPATH.lib/libsapi.a' > > That's not getting substituted, even if we add ",SYMBOLS=(JCLONLY,JESJCL)" > to the DD. > > Is this some limitation that we've hit, where even though that sure looks > like JCL, it doesn't get processed the same way "regular" JCL would? > > Say it ain't so...! > > Thanks for any hints/tips. > > ---------------------------------------------------------------------- > 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
