Ok, wasn’t the issue all those years ago with regards to *when* the system symbols get resolved? Interpreter time vs execution time and those things occurring on potentially two different systems in the plex?
I could *easily* be mis-remembering. _________________________________________________________________ Dave Jousma Manager Mainframe Engineering, Assistant Vice President [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Sean Gleann Sent: Wednesday, June 06, 2018 11:19 AM To: [email protected] Subject: Re: Use of dynamic system symbols in JCL **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Thanks all - the SYSSYM bit was the missing link. I've defined that and now all is well. Dave's last comment regarding 'unpredictable results' is a bit worrying. Have there been problems with using these symbols? Personally I feel it's a pity that SYSSYM has to be specifically turned on or off at all. These dynamic symbols are SO useful! I'd like to see the idea extended to cover 'yesterday', 'previous work day', 'beginning of the month', etc. Thanks once again Sean On 6 June 2018 at 16:03, Jousma, David < [email protected]> wrote: > Is anyone else pushing back on turning on batch system symbol support? > We've yet to do so, for the very reasons that IBM hadn’t supported in > batch all along. My main concern is unpredictable results. > > Am I worrying for nothing? > > _________________________________________________________________ > Dave Jousma > Manager Mainframe Engineering, Assistant Vice President > [email protected] > 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f > 616.653.2717 > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Carmen Vitullo > Sent: Wednesday, June 06, 2018 10:49 AM > To: [email protected] > Subject: Re: Use of dynamic system symbols in JCL > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > Yep, need to make sure SYSSYM=ALLOW for that jobclass, > > > > CLASS og XBMProc DupJob JobRC Active SysSym > 1 PIN) NO MAXRC YES ALLOW > 2 PIN) NO MAXRC YES ALLOW > > > > > in a STC I run at IPL time I do about the same.... > > > > //CLEAN EXEC PGM=IDCAMS > //SYSPRINT DD SYSOUT=* > //SYSIN DD *,SYMBOLS=EXECSYS > DEL 'ATTS.PROD.&SYSNAME..IPLINFO' > /* > //IPLINFO EXEC PGM=IKJEFT01,REGION=0M,PARM='IPLINFO', > // DYNAMNBR=99 > //SYSEXEC DD DSN=TS.USER.REXX,DISP=SHR //SYSTSPRT DD > DSN=ATTS.PROD.&SYSNAME..IPLINFO,DISP=(,CATLG), > // UNIT=SYSDA,SPACE=(TRK,(25,5),RLSE), > // RECFM=FBA,LRECL=134,BLKSIZE=0 > //SYSTSIN DD DUMMY > //* > //IEBCOPY1 EXEC PGM=IEBCOPY,REGION=2M,TIME=10 //SYSPRINT DD SYSOUT=* > //SYSUT1 DD DISP=SHR,DSN=SYS1.&SYSNAME..PARMLIB > //SYSUT2 DD DISP=(,CATLG), > // DSN=ATTS.PROD.SYSA.D&LYYMMDD..T&LHHMMSS..PARMLIB, > // UNIT=SYSALLDA,SPACE=(CYL,(10,1,75),RLSE) > of course STC .... > > > > Carmen Vitullo > > ----- Original Message ----- > > From: "Andrew Arentsen" <[email protected]> > To: [email protected] > Sent: Wednesday, June 6, 2018 9:43:25 AM > Subject: Re: Use of dynamic system symbols in JCL > > In my JES2PARM, in the definition of the job class that I'd run this > job in, I specify SYSSYM=ALLOW. I'm sure you could put this in > dynamically with a $T of some sort. You'll also need the two periods as Rob > stated. > > Andrew Arentsen > Senior Mainframe Systems Engineer > > > > > From: "Sean Gleann" <[email protected]> > To: [email protected] > Date: 06/06/2018 09:35 AM > Subject: Re: Use of dynamic system symbols in JCL Sent by: "IBM > Mainframe Discussion List" <[email protected]> > > > > I understand what you're saying Rob, but that was one of the variants > I tried. It still produces the same error > > Sean > > On 6 June 2018 at 15:29, Rob Schramm <[email protected]> wrote: > > > You need 2 dots after symbol.. otherwise nodeis GT 8 characters > > > > Rob > > > > On Wed, Jun 6, 2018, 10:27 AM Sean Gleann <[email protected]> > wrote: > > > > > Can anyone point out what I'm doing wrong here, please? > > > > > > > > > I'm trying to create a file with a name that features today's date. > > > My statement is: > > > //OUTFILE DD DSN=BACKUP.USERDALY.D&LYYMMDD.TER, > > > // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(600,600),RLSE), > > > // DSORG=PS,RECFM=FB,BLKSIZE=27648,LRECL=1024 > > > > > > When I submit the job to the system, I get: > > > > > > IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD > > > > > > I've tried numerous variants of this statement, but I always get > > > the > same > > > failure. > > > I'm almost certainly doing something stupid, but right now I can't > > > see > > the > > > wood for the trees... > > > > > > > > > Help... Please... > > > > > > Sean Gleann > > > > > > ------------------------------------------------------------------ > > > ---- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO > IBM-MAIN > > > > > -- > > > > Rob Schramm > > > > -------------------------------------------------------------------- > > -- 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 > > > ********************************************************************** > This e-mail is confidential. If you are not the intended recipient, > you must not disclose or use the information contained in it. If you > have received this e-mail in error, please tell us immediately by > return e-mail and delete the document. > > ---------------------------------------------------------------------- > 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 > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > This e-mail transmission contains information that is confidential and may > be privileged. It is intended only for the addressee(s) named above. If > you receive this e-mail in error, please do not read, copy or > disseminate it in any manner. If you are not the intended recipient, > any disclosure, copying, distribution or use of the contents of this > information is prohibited. Please reply to the message immediately by > informing the sender that the message was misdirected. After replying, > please erase it from your computer system. Your assistance in correcting this > error is appreciated. > > > ---------------------------------------------------------------------- > 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
