As the documentation clearly states: "The system checks for this attribute only when the program is being invoked with a parameter string of more than 100 bytes and the program is APF authorized. In this case, if the LONGPARM attribute is not set on, the system fails the invocation. "
What would you report, and to whom? If you were to install Clem's program into an APF-authorized library on your system, you could then report yourself to your own management for having compromised the security on your system by installing freeware without understanding that it allows any user to run a simple unauthorized program which exploits his program to run any program from an unauthorized library with APF-authorization. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY > > Uhhh, Clem's program is not the Initiator, and does not > >do what the Initiator does to request LongParm checking, so no > >LongParm checking is done for its ATTACHes. > > > Sounds like a bug. Or an integrity threat. If I had Clem's program > I'd report it. > > Does the Initiator check LongParm for AC=0 programs? While they > can't threaten system integrity, PARMDD has exposed them to > new unpleasant failures. It would be easy enough to relink programs > with LongParm when appropriate. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
