I think Peter is on the right track. I normally do not code any CLASS= on a job. Execution class here gets set by some pretty involved code in Exit 6, but the question is what 'jobclass' is used for options during conversion?
If I omit CLASS=, my job works, implying that 'class A' rules are in effect. Changing nothing else, I added CLASS=C (unmodified) to the job card, and I get the same 'invalid use of ampersand' error that I started with. Then I set JOBCLASS(C) to allow SYSSYM, and the job worked. So again, what determines conversion rules if no CLASS= is coded? I cannot find any parameter in our JES2 init deck that would set class A as the default. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: Friday, July 22, 2016 10:15 AM To: [email protected] Subject: (External):AW: Re: System symbols in batch JCL If anyone is still paying attention, my question lingers. Is CLASS A always used for JCL conversion? Just because it's first in the list? Is it a defined or default option? If it's always gonna be CLASS A, do I need to 'ALLOW' any other class? The conversion is not done by a class, its done by the conversion code. The CLASS only tells limits and defaults. If you allow SYSSYM on class A but not on class B, conversion will fail to resolve symbols if CLASS=B is coded on the job statement, but will do it for CLASS=A. In your case, the symbol resolution is probably done before something changes the CLASS form A to C. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
