On Wed, 5 Nov 2025 07:36:18 -0500, Robert S. Hansel <[email protected]> wrote:
> is it feasible to add UAUDIT to the ID to see everything it is accessing? > This might identify programs the Started Task is executing It would be helpful if Lizette told us her goal because as you say, there are easier solutions. At this point, she wants to know the issuer of ASCRE. Since ASCRE doesn't issue any messages, she needs a dump occurring as soon as possible after the ASCRE PC instruction so that she can find it in the trace table where she can see the ASID of the issuer. >What STARTED profile is being used to assign the Started Task an ID? > Is TRACE(YES) set in this profile's STDATA segment and are you seeing IRR812I > messages as a result? if IRR812I is a WTO, then slip can take a dump on it. Good suggestion. >I believe if the task was created by a supervisor-state program >using the ASCRE macro there'll be no START command, I suspect that MVS START command uses ASCRE under the covers probably from the CONSOLE address space but that's just a guess and not important at this time. >ASCRE need not specify a PROC. True, for example CONSOLE address space. In this case, you would need to get a little creative to capture the dump at or shortly after the ASCRE. Determining the ASCRE INIT program might be difficult to determine but would be easy to set a slip. As an alternative, I would dump the STC and look at the first TCB's first save area to find the module being called and use it for the SLIP (beware of IEFBR14). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
