On Thu, 29 Oct 2009 17:28:44 -0400, John P. Baker wrote: > >For a short PARM= value (compatibility mode), R1 -> fullword address of >PARM= info, consisting of a 2-byte length prefix (value 0..100) followed by >a string buffer not exceeding 100 bytes. > >For a long PARM= value, R1 -> fullword address of PARM= info, consisting of
Again, NO! Provide in JCL the facility now provided by Rexx "address ATTCHMVS", in a completely compatible fashion. >a 4-byte length prefix (negated (high-order bit = B'1'), value >101..installation-defined-maximum), followed by a fullword address of a >string buffer not exceeding installation-defined-maximum bytes, followed by >a fullword ALET identifying the dataspace wherein the string buffer is >located. > An interesting alternative. But why not just use 64-bit addressing? dataspaces are _so_ 20th century. How does the JCL programmer specify the dataspace? Or does the Interpreter select one by colonic extraction? Aren't we going overboard here? While 100 characters in JCL is painfully constraining, and 255 might be an uncomfortable limit, any programmer who feels the need for >65535 in JCL, even mechanically generated JCL, should probably choose a different language. -- 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
