> ..re > Can't it be done in JCL now that the old parm input size > restriction has been relieved? > > I would say call me stupid but too many members would take me up on the > offer. ;) > > Instead, I'll just ask, when did this occur? I remember the long-running > discussion not too long ago about this subject but did not pick up on the > "fact" <?> that it had been done.
I don't believe that it has been done (yet) and if it has been disclosed to vendors I was probably asleep at the time. But that has nothing to do with the operator command text limit. The 126 character limit for MGCRE (the command interface macro for those not familiar with z/OS arcanna) is STILL documented. Here's the relevant snip from the macro doc; TEXT=text addr Specifies <snip> the address of a command area. <snip> The first 2 bytes of this command area contain the length of the command. The command text immediately follows this 2-byte area, and can be up to 126 characters. The command must be in storage addressable by the caller at the time the caller issues MGCRE. There does not seem to be anything magical about that length. The content of the text macro parameter ends up being tacked onto the end of the CIB and the CIBX follows behind that. It is -possible- that the limit is in fact larger, but where the book specifies an actual number I tend to treat it as gospel. Someone from IBM can probably tell us whether the limit is real or a doc apar waiting to be noticed. CC ---------------------------------------------------------------------- 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
