Hello All, What about to check the existence of a PARM DD-name before the fetch of inline params? Like, if you want to pass a long parlist and it is more than 100 bytes, then just specify a //PARM DD * card before this mind flow. Anycase, this way is a LOCAL FIX for this problem, IMHO..
=Maxim 2017-12-01 18:27 GMT+03:00 Ed Jaffe <[email protected]>: > On 11/30/2017 9:10 PM, Paul Gilmartin wrote: >> >> On Thu, 30 Nov 2017 20:43:17 -0800, Ed Jaffe wrote: >> >>> >>> LONGPARM isn't used other than during initial establishment of an APF >>> authorized job step. >>> >> "LONGPARM isn't used ..." has confusing semantics. That would seem to >> imply >> that in other contexts the 100-character limit is enforced. Or in those >> other cases, >> is LONGPARM presumed? > > > LONGPARM allows parms > 100 bytes to be passed to authorized programs > invoked via JCL // EXEC statement. Nothing confusing about that. > > Stated another way: if your program is bound with AC(1) and loaded from an > APF authorized concatenation, you will need LONGPARM if you wish to receive > parms > 100 bytes. Without LONGPARM, your program will only be allowed to > receive parms <= 100 bytes. > > Programs invoked through other means (ATTACH, etc) and unauthorized programs > invoked via JCL // EXEC statement can receive long parms as well. > > It's just that simple... > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > http://www.phoenixsoftware.com/ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Regards, =Maxim Bochagov ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
