Jerry, In the distant past, forked address spaces where managed via APPC address spaces (when OE was first introduced). So that is probably the reason for the WLM managed indicator. As for Batch Inits, that is probably to indicate a JES class that is defined with WLM inits rather than JES inits, so my guess is that yes, they are mutually exclusive.
Wayne Driscoll Product Developer NOTE: All opinions are strictly my own. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Support, DUNNIT SYSTEMS LTD. Sent: Wednesday, March 19, 2008 3:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Can forked/spawned address spaces be identified as such? Anyone? In the meantime, I've found these in the ASSB: ASSBWMF1 DS XL1 WLM flags * SERIALIZATION: none ASSBWINI EQU X'80' WLM Managed Batch initiator ASSBFSAS EQU X'40' WLM Managed OE Forked/Spawned Now, are all forked/spawned address spaces managed by WLM? If not, what else would indicate a forked/spawned address space? What precisely is the difference between the 2 equates above? Are they mutually exclusive? Can there be forked/spawned address spaces with both indicators off? Jerry On Wed, 19 Mar 2008 04:11:10 -0500, Support, DUNNIT SYSTEMS LTD. <[EMAIL PROTECTED]> wrote: >Are there any control block fields or flags within these address spaces that >indentify them as being started by a fork or spawn action? Are there different >indicators for forked versus spawned address spaces? > >TIA, >Jerry ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
