Peter Hunkeler replied: > Betreff: Re: Problem resolving JCL SET symbol > > > > //SAS PROC ENTRY=SASXAL0, > > // OPTIONS=, > > // SORT=4 > > > //************************************************************* > > //SAS EXEC PGM=&ENTRY,PARM='SORT=&SORT &OPTIONS' > > How about: > > //STEP1 EXEC PROC=SAS, > // PARM.SAS='SORT=4 add whatever parms you need here' > > This overrides the complete PARM field of the EXEC in the > procedure. You don't have to fiddle around with nested symbols. > > > Peter Hunkeler > CREDIT SUISSE
Thanks Peter, I had mentioned (in my 'other than ...' remark) that I don't want to do this although it is an absolutely valid idea. I want to make the JCL as simple and foolprof as possible. All that is needed here is to be able to say 'run as if variable x had value y'. So I wanted the JCL to be // SET symbol=value //<rest of JCL> so if someone other than me who has to submit the job does not have to know how to override statements hidden within a JCL procedure. (The KISS principle at it's extreme). One quick glance ... one modification ... off we go. =8) ) Robert Bardos Ansys AG, Zurich, Switzerland ---------------------------------------------------------------------- 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
