On Tue, 3 Nov 2009 17:06:23 +0200, Binyamin Dissen wrote: > >The API is defined as 100 byte maximum and programs are coded for that. Any >change must respect the existing programs. New programs wishing to use a >larger plist can be coded to use a new way to get to the data.
The JCL manual does say, "The length of the subparameters passed must not exceed 100 characters", but I wouldn't call that an API. The Assembler Services Guide describes the API. It reads, <quote> When your program receives control from the system, register 1 contains the address of a fullword on a fullword boundary in your program's address space (see Figure 2-4). The high-order bit (bit 0) of this word is set to 1. The system uses this convention to indicate the last word in a variable-length parameter list. Bits 1-31 of the fullword contain the address of a two-byte length field on a halfword boundary. The length field contains a binary count of the number of bytes in the PARM field, which immediately follows the length field. If the PARM field was omitted in the EXEC statement, the count is set to zero. To prevent possible errors, always use the count as a length attribute in acquiring the information in the PARM field. </quote> It does not mention the 100 byte limit. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
