If a software product expects more than 126 chars - then I would suggest that it should be up to THAT product to provide an operator interface so that the operator can "continue" entering text (eg the dialog used for the MVS "DUMP" command).
I would imagine that the 126 char limit dates *way* back to the days when every byte was sacred.... It might be worth asking IBM for the 126-char limit to be upped - but it might not be very high on their priorities. Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Hunkeler Peter (KIUK 3) Sent: 18 September 2007 14:19 To: [email protected] Subject: Re: really long z/OS operator command lines. >Can't it be done in JCL now that the old parm input size restriction >has been relieved? Unless I'm missing something, JCL PARM length has not been changed. It is only BPXBATCH that has been changed to accept more than 100 characters in some cases. EXEC PARM is still restricted to 100 chars. And even if it would (don't start that discussion again, please), it would not help the OP. He wants to pass more than 126 characters to an "MVS" (well Oracle) operator command routine. The interface is MGCRE and or an EMCS console (which then needs to use MGCR) and this interface limits the command to 126 characters. -- Peter Hunkeler Credit Suisse ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
