On Tue, 4 Nov 2025 01:07:01 +0000, Lizette Koehler <[email protected]> wrote:
>I have a $hasp100 showing my STC came in via stcintrd. Including answer to your previous question (tracking where a proc is used). If my suggestions don't help, then you might consider RACF logging/audit or user exits. With any solution, beware of overhead and impact on the system. Also keep in mind this could be tricky because you are trying to capture information at the very moment of a transition from the issuer starting another address space and you will only get the issuer's jobname & asid as clues to how it's being started. 1. Try using automation for $HASP100 to display the jobname & asid. I don't think it will be the issuer but it only takes a second to write the automation. 2. If your automation supports command traps, then write automation for the S command. It's unlikely but only takes a second to verify using automation that the command is being echoed even if suppressed (because it's coming from another system, being suppressed or ???). In this case you will see the who started it. 3. If the STC is not started by the S command, then it must be started by the HLASM ASCRE macro which if I remember correctly does not issue a message. In this case, you will need a dump as close as possible to the time of the ASCRE and look for the PC in the trace table (I think). Considering SLIP limitations, SLIP MSGID=$HASP100,ACTION=SVCD is probably not a viable option but there are easy alternatives. 3a. If your automation product supports issuing a WTO directly from the SSI (e.g. AutoOperator), then write automation that creates another WTO for the correct $HASP100 and use it for the SLIP. 3b. If not supported (e.g. Netview), then write an MPF routine to issue a WTO when the correct $HASP100 occurs and SLIP on that msgid. I can't remember the command for setting the MPF exit for $HASP100 but someone using Netview should know it. 4. Converter/Interpreter exit might have the issuer's information so it might be worth a look. 5. From your first post, you wanted to identify where proc's are used. There is an MVS message displayed (STC, JOB, TSO) for each proc expanded which should be available to your automation. You can find the msgid in JESYSMSG for any job but if I remember correctly the msgid is second word of the message (instead of the first). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
