On 26 May 2014 01:47, Binyamin Dissen <[email protected]> wrote: > On Sun, 25 May 2014 18:43:48 -0400 MichealButz <[email protected]> > wrote: > > :>I have an APF authorized module running of out of the LNKLIST I try to load > :>a module from an non apf dsn concatenation and get CSV019I abend > > :>I am in problem state key 8 when I do this > > :>It seems than once I am in a APF concatenation library even though I am in > :>problem state key 8 I can't load anything from a NON apf dsn concatenation > > Being load from APF is not the direct issue
Exactly. > the issue is that the jobstep is APF, i.e., the EXEC PGM= module is marked > with AC(1). *And* it came from an authorized library. > As long as the step remains marked, no loads will be done from non-APF. And there is no supported, safe way to unmark the step. > Why do you want to compromise integrity? We have this discussion on this list every year or so, and everyone agrees in the end each time that while an APF authorized program can -- pretty much by definition -- do anything it wants, including deauthorizing itself, running a mix of auth and unauth tasks, etc. etc, all of this is almost always very unwise. Then the discussion starts up again... Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
