PMFJI here but the limit with PARMDD is 32K I believe.  JES/JCL limit is 100, 
not 255.  The COBOL questions is, does the compiler correctly process PARMDD 
input > 255 characters, and if so which version(s)?  Only V5+?  I could 
understand V4 not supporting it, but not V5+.


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Ross
Sent: Tuesday, February 13, 2018 6:42 PM
Subject: Re: Question for COBOL users

We added OPTFILE as a response to customer request, I believe it was
well before PARMDD, but not positive.

Someone else asked what the COMPILER limit for reading the PARM=
options string is, but there is none.  There is a JCL/JES limit of
255 bytes.  There is no limit for SYSOPTF (using OPTFILE).

It seems pretty clear that we cannot change the default behavior to
read SYSOPTF whenever it is present, regardless of OPTFILE, so we
will probably add another (sigh) compiler option

>There is nothing to prevent a user or product to go ahead and use
>PARMDD, and it could point to the program's (compiler's) specific
>overrides.  The program (compiler) can only read the PARM for the
>length it specifies (100/255) until modified to allow a parm length of
>32K.  Maybe a couple releases down the road you can give a warning
>message that the program (compiler) specific parm will be removed.


This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

For IBM-MAIN subscribe / signoff / archive access instructions,
send email to with the message: INFO IBM-MAIN

Reply via email to