When we did add a non-apf authorized lib to our CICS concatenation, the CICS startup abends immediately. Once we authorized it, CICS comes up OK. I realize this is just one application but it is where you tend to get a lot of libs concatenated (DB2 procs also). We did not try to execute anything from this non-apf lib but CICS tried executing its main program and I am assuming (I know the drill) that it checks status on all the libs in the startup and so abends.
John C On Tue, May 27, 2014 at 7:58 AM, Peter Relson <[email protected]> wrote: > >...the rule (at least in CICS) where in a multilib > >concatenation, if one lib is APF all the libs must be > >APF authorized, period. > > I would say that the general rule would replace "period" with "if you want > the concatenation to be considered APF-authorized". > There is no intrinsic problem with having a concatenation that mixes APF- > and non-APF-authorized libraries. > > Peter Relson > z/OS Core Technology Design > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
