Conversion and execution <of batch jobs> can occur on a different systems in the sysplex. Conversion is when the system symbols in JCL are resolved; so &SYSNAME would resolve to system where conversion occurred, but the job could execute on a different system.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Charles Mills Sent: Wednesday, February 23, 2011 11:01 AM To: [email protected] Subject: Re: System symbols in dynamic allocation Thanks. Your reply crossed in the mail with my follow-up. FWIW in the case in question I am not using SVC 99 directly but rather using C fopen(); Yeah, the fact that you can't code &SYSNAME in JCL seems pretty lame. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Shmuel Metz (Seymour J.) Sent: Wednesday, February 23, 2011 6:55 AM To: [email protected] Subject: Re: System symbols in dynamic allocation In <031b01cbd2c6$62366280$26a32780$@org>, on 02/22/2011 at 11:26 AM, Charles Mills <[email protected]> said: >Do the same restrictions on static system symbols exist for dynamic >allocation as exist for JCL in the same environment I've seen no documentation for such a restriction, and the excuses IBM gave for not allowing arbitrary system symbols in batch JCL do not apply to execution time. >That seems to be what I am seeing but I don't see that restriction I would create a PMR. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
