On 2017-01-17, at 09:11, Jesse 1 Robinson wrote: > 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. > But some users may lack authority to change their TSO PROCs or start STCs.
And allowing SYSSYM to depend on job class is treacherous. A user who changes job class e.g. to change priority may be unpleasantly astonished to find SYSSYM behavior changing. Wouldn't it have been less disruptive to control it by a JCL option statement rather than a system parameter? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
