From: "Joel C. Ewing" <[email protected]> Date: 02/28/2013 08:05 AM
<SNIPPAGE> SYSPARM is a documented system variable that is set based on parameter options specified when the Assembler is invoked. Installations may use this parameter for their own purposes, which makes any assumptions of there being a conventional length for this parameter invalid. <SNIPPAGE> Some years ago I was doing some programming where I needed JES2 macros (ACS/WYLBUR JES2 SRB support for those of you who had that product). I also needed to pass to the routine that was being assembled, a parameter to tell it whether it was to generate a DSECT or CSECT. So, I wrote logic to parse &SYSPARM to get my information. The JES2 macros returned MNOTE 8 (IIRC) because the &SYSPARM string did not match anything they were looking for. This ultimately got escalated to the owner of the Assembler, one Dr. John Ehrman (at that time). He informed the JES2 personnel that they had an opportunity for an APAR since they do not own &SYSPARM, He did as the owner of the Assembler. -- I may not have that quote 100%, but it is quite close. So there is precedent for having various components fix their macros if they are not using &SYSPARM correctly. Regards, Steve Thompson [I do not speak for IBM, opinions expressed are not necessarily those held by IBM.] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
