Coding Each AOF Rule Type › UNIX System Services Rules › )USS USSPROCBEG—Event Specifier of USS Process Event Rules

)USS USSPROCBEG—Event Specifier of USS Process Event Rules

USS process events generate the following USS messages for USS AOF rule processing:

USSPROCBEG DENM44SS 03FD 67108949 SPAWN INIT /bin/onetstat
USSPROCEND DENM44SS 03FD 67108949 SPAWN TERM /bin/onetstat

The data elements in these messages are:

• A fixed message ID for begin or end of a process
• The job name of the process.
• The ASID of the process in printable hex.
• The USS process number of the process.
• The USS service that caused the process to be created.
• The word INIT for process initialization events or the word TERM for termination events. If the process terminates abnormally the TERM word may be replaced by MEMTERM or ABTERM.
• The USS program name associated with the process. This name can be up to 128 characters long. The message text can be truncated in OPSLOG if the program name is too long. The full message text is available in the AOF rule variable USS.FULLTEXT.

Because USS process events have only two static message IDs, use the following format for coding the USS process event definition section:

)USS USSPROCBEG or USSPROCEND or USSPROC*
)PROC
  IF uss.type <> 'PROCESS' Then Return 0

You should code one USS rule for each message ID. In the USSPROCBEG rule, use the program path name and additional event data to determine if the process is managed by SSM. If so, the current state of the USS resource would be changed to the UP state and the process ID, job name, ASID, and exit timestamp would be added to the data columns of the USS resource for stopping the resource when requested. In the USSPROCEND rule, you can use the same process information to match the USS resource in SSM and set the current state to the DOWN state.