As I pointed out in my earlier post, system symbols have long (always?) been honored for STC and TSO proc JCL. The change in 2.1 is to extend this support to batch JCL on a job class by class basis. If someone wants a preview of what to expect in batch with having to turn on the option for an entire job class, experiment with STC or TSO. The result for all three should be the same categories.
. . 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 [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: Tuesday, January 17, 2017 6:32 AM To: [email protected] Subject: (External):AW: Re: System Symbols (SYSSYM) > There is one case in which there might be problems. Looking at: > //MYFILE DD DSN=&SYSNAME,DISP=(,PASS),UNIT=SYSDA When using System Symbols in batch jobs was introduced with z/OS 2.1, I was always wondering what prompted IBM to define that SYSSYM= switch in the JOBCLASS definition. I knew there must be cases that will break, otherwise SYSSYM= would not have been implemented at all. I guess this is exactly the case, or at least a major one. Thanks! -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
