/*JOBPARM (and its /* brethren) and JES3's //* cards, are JECL - Job Entry Control Language. JESn sees and processes these cards before it passes the stream to JCL conversion. So the symbolic you specified does not exist yet, because you're not in JCL conversion which means, alas, what seems logical won't work. (At least in VSE symbolics are a lot easier, although I have my own gripes about VSE JCS.)
(What are you doing working on the Friday after Thanksgiving? Better yet, I should ask myself the same question.) Later, Ray > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin > Sent: Friday November 25 2005 07:01 > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: Using symbolic in JCL > > In a recent note, R.S. said: > > > Date: Fri, 25 Nov 2005 09:07:48 +0100 > > > > That's because it is forbidden by IBM. I'd prefer "determinate on > > single system *only*". Limited functionality. This is more > than I have today. > > Today I have nothing. > > > With similar "more than I have today" motivation, I tried > using a SET symbol instead of a system symbol, as follows: > > // SET SYS=MVS3 > //* > /*JOBPARM SYSAFF=&SYS > **************************** INVALID /*JOBPARM CARD > *************************** > $HASP106 JOB DELETED BY JES2 OR CANCELLED BY OPERATOR > BEFORE EXECUTION > > No joy. Dammit, how many things can IBM do wrong in the JCL > parser? I suspect I've only begun the catalog. Look, IBM > guys, perform the substitution first, _then_ interpret the > statement. It's that simple! Same applies to the > misinterpretation of "//SYSIN DD DATA,DLM=&SYMBOL", etc. ---------------------------------------------------------------------- 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
