After dis-assembling IEFIIC, analyzing several dumps and doing quite a bit of reading, I was able to piece together a scenario that I believe to be reasonable.
Among other things, I was able to confirm that the admonition to refrain from resetting JSCBAUTH after turning it off has no exception; it is also irrelevant to the initiator. Thanks to those who provided input. Alan -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Starr, Alan Sent: Tuesday, July 19, 2011 5:59 PM To: IBM-MAIN@bama.ua.edu Subject: APF and the initiator (IEFIIC) Hi List, The subject of an APF-authorized program invoking a program that runs non-APF-authorized has been discussed many times here. The admonishment not to turn JSCBAUTH on, after having turned it off, has been repeated many times. I wonder how the initiator manages to invoke PGM=apfpgm (APF-authorized) and then PGM=nonapf (not APF-authorized) for a subsequent step or job. Does it, for example, turn on JSCBAUTH in the ATTACHed program's (job step) JSCB? Does anybody know the sequence of events and/or what the ATTACH(X) invocations look like? Cheers, Alan ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
