>"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?
You made me curious, so I went to RTFM. I will submit an RCF, because the documentation couldn't be more fuzzy and confusing, IMHO. Before submitting, I would like to get your opinion on my comments below. o The Binder manual talks about: "The system checks ... and the program is APF authorized." A program is not APF authorized, the job step TCB is or is not. o The JCL Reference manual talks about: "If the program to be invoked is from an APF authorized library *or* has been bound with the AC(1) attribute..." The *or* is confusing. LONPARM is not mentioned with the LINK or ATTACH service. This makes sense and indicates to me that it is the *initiator* doing this verification when it prepares to attach the program. So the binder and JCL manuals should say that "The system will check at job step initiation when the job step will be set APF authorized.... -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
