On Tue, Mar 17, 2015 at 8:18 AM, Shmuel Metz (Seymour J.) <[email protected]> wrote: > In <[email protected]>, on 03/16/2015 > at 10:52 PM, Ed Gould <[email protected]> said: > >>Legally "no" but it can be done . > > You can, legally, turn APF off and later turn it off. It should be > done the way porcupines make love: very carefully.
IMO, it would be easier to just use ATTACHX with the JSCB= pointing to a copy of the current task's JSCB with the APF bit flipped off. Of course, the copy really needs to be in subpool 253 (key 0, below the line). The OP might even want a TASKLIB= if he wants to do a DYNALLOC to specify the DSNs to be searched, perhaps given in a configuration file of some sort. OK, likely overkill in this case. Another interesting parameter might be SZERO=NO to not share subpool zero to avoid "memory leaks" if, as I have seen, the ATTACH'd program doesn't bother to clean up all its memory because "the system will do that automatically". I've especially noticed this in the past because CLOSE didn't always free the I/O buffers when a DCB was closed. > > -- > Shmuel (Seymour J.) Metz, SysProg and JOAT > ISO position; see <http://patriot.net/~shmuel/resume/brief.html> -- If you sent twitter messages while exploring, are you on a textpedition? He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
