Perhaps this sequence of steps (from a colleague of mine) might work to get you the original job name.
As long as you are not in a system exit, like IEFUTL, you should be able to do the following: 1. Check to see if the address space is properly dubbed 2. Uset getppid() to get the parent's pid 3. Use w_getpsent() call to get information about jobname, username, and so on. 4. Is the ppid 1? Then I think you've arrived at the address space you are looking for. This I think is the one that used to be BPXAS. 5. Check to see if w_getpsent() returned a UNIX process. If so loop to #2. I'm not sure that is exactly correct, but perhaps it is in the ballpark? There is some new documentation in the z/OS 1.9 book that says you cannot issue "nested" callable services. And most importantly concerning system exits: "...if a z/OS UNIX callable service invokes an exit during the processing of the callable service, invoking z/OS UNIX callable services from the exit program is not supported." -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Support, DUNNIT SYSTEMS LTD. Sent: 19. maaliskuuta 2008 11:11 To: IBM-MAIN@bama.ua.edu Subject: Can forked/spawned address spaces be identified as such? 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
