On Thu, 24 Sep 2009 16:11:34 -0400, Robert A. Rosenberg wrote: > >This provides a way to support PARMX while staying compatible with >PARM (and programs that use it). If PARMX is not supplied in the JCL, >act as now. If there is a PARMX pass a 2 FW list in R1 (with the >second FW flagged as end-of-list). > >FW 1 points at a HW containing 0 (as currently occurs now in the >absence of a PARM), while FW 2 points to a HW and the PARMX contents. >If both PARM and PARMX are supplied, pass both. > No. Not compatible. One of the existing programs to which I occasionally supply an oversize PARM (when not calling it from JCL) is HLASM (ASMA90). HLASM expects the PARM (regardless of size) in the FW 1 argument, and already makes other use of the FW 2 argument (when not called from JCL). It would be badly broken by an attempt to use the scheme you propose.
-- gil ---------------------------------------------------------------------- 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
