On Mon, 7 Jul 2014 07:25:38 -0500, John McKown wrote: >On Sun, Jul 6, 2014 at 10:45 PM, MichealButz wrote: >> Hi, >> >> I am getting 306 ABEND because my APF concatenation contains a NON >> authorized Library. IS it possible to remedy this (as I have a recovery >> routine) >> >> By Dynamic allocation of the dataset ? > >_IF_ I understand what you want to do, then the answer is an >unqualified NO. Let me restate the problem in my own words. You are >running some code which running APF authorized (loaded from APF >library & AC=1 on PGM=). You now want to access/run some code which >resides in an non-APF authorized library. This is _impossible_. Even >if you dynamically allocate a new DD to point to the non-APF library; >OPEN it; then do a LINK/LOAD/XCTL/ATTACHX with the DCB operand. You >will get the S306 abend in all cases. > I'll give the OP credit: As I see it, he wants to execute an AC=1 module from an APF authorized data set, however that module is not found in the authorized TSOLIB, and LOAD then searches the unauthorized STEPLIB, resulting in the S306.
>As I understand it, what happens is this: > >One: to run APF authorized basically means that the APF bit is set >"on" in the JSCB. When you (or the initiator in the case of >STEPLIB/JOBLIB) does an OPEN, the code in OPEN will look at each (or >only) library concatenated to the DD being OPEN'ed. If _every_ DSN in >the concatenation is marked as APF authorized, then OPEN will set a >bit in the DEB for the open DD which says "this DD is APF authorized". >Now, when you do a program fetch (LOAD/LINK/...), the z/OS code >responsible for doing that will basically do: "IF JSCBAPF IS TRUE AND >DEBAPF IS FALSE THEN ABEND S306". ... > I don't see the rationale of this design. IMO, a more rational design would mark each extent entry in a DEB individually as belonging to an authorized or to an unauthorized data set. Then the decision to S306 or not S306 could be made based on whether the actual data set in which the module was found was APF authorized. Why not? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
