Does it actually say STCINTRD or just "INTERNAL" or does it just "show up" with a started task number. I don't think there is anything called STCINTRD, but things can be started via INTERNAL by any JOB or started task that wants to do it. As for not seeing the command, it could have been suppressed by MPF or via automation. That doesn't mean that automation started it, just that it could have suppressed the start message.
Normally if something is started by a Started Task or Batch task, the "S taskname" will show up with the taskid of the space the started it, but that can be suppressed, ours, and every other automation product that I know of, provides the ability to suppress a message or command from the syslog, as does IBM's MPF itself. On the other hand, it could be in the syslog and you are just missing it. It doesn't necessarily have to start in the first byte of the command area. However, you can always see how anything entered the system from your handy dandy SMF data. More information would be helpful. 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. However it does not >tell me who started it > > No message - submitted via >No S stcname >No automation code to start it >No scheduler activity for the stcname > >Any suggestions on how to determine how it enter the system? > >Lizette > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
