IBM demurred for years allowing system symbols to be used in batch JCL. There were several spirited discussions at SHARE as to how they should work. Some possibilities:
-- Substitute values at submit time -- Substitute values at conversion time -- Substitute values at execution time These questions are complicated by the possibility of a job executing on any member of a MAS or even on another NJE node. Not to mention the chance of symbol collision with internal JCL variables. All of these possibilities confuse the question of what value did the user intend? What did she get? There was no consensus among participants. When IBM finally conceded to customer demand, they imposed some rules, which are documented. But to protect users from unexpected results, the default was to disallow substitution unless the installation explicitly allowed it--presumably after lots of testing. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Lars Höglund Sent: Wednesday, October 14, 2020 12:50 PM To: [email protected] Subject: (External):SV: INTRDR and submitted JobID CAUTION EXTERNAL EMAIL Hi Do You the reason why the default for SYSSYM is DISALLOW? //Lasse -----Ursprungligt meddelande----- Från: IBM Mainframe Discussion List <[email protected]> För Lizette Koehler Skickat: den 14 oktober 2020 20:38 Till: [email protected] Ämne: Re: INTRDR and submitted JobID I think System Symbols are only available when the JES2 Class says SYSSYM=ALLOW Otherwise I think they are not available to a batch job. They are probably available to an STC Lizette -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Sri h Kolusu Sent: Wednesday, October 14, 2020 11:02 AM To: [email protected] Subject: Re: INTRDR and submitted JobID > I've used an IKJEFT TSO ISPF step or SDSF screen scraping to extract a > job's own JobID. Is there a simpler way? Gil, How about using system symbols &SYSJOBID and &SYSJOBNM ? Something like this? //STEP0100 EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTOUT DD SYSOUT=(*,INTRDR) //SYSIN DD * OPTION COPY //* //SORTIN DD DATA,DLM=$$ //SYMSUBJ JOB (B004273,BIN#,BLDG#,DEPT#),&SYSUID, // MSGCLASS=H,MSGLEVEL=(1,1),CLASS=A,NOTIFY=&SYSUID /* // EXPORT SYMLIST=* // SET SYSJOBNM=&SYSJOBNM,SYSJOBID=&SYSJOBID /* //STEP0100 EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTIN DD *,SYMBOLS=JCLONLY JOBNAME FOR THIS JOB IS : &SYSJOBNM JOBID FOR THIS JOB IS : &SYSJOBID //SORTOUT DD SYSOUT=* //SYSIN DD * OPTION COPY /* $$ Thanks, Kolusu ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
