Eleven defined security-related UTM events can be logged. A result is logged for each event: success or failure. Success, for example, means that when a user signs on, openUTM accepts the specified user ID and authentication data.
The table below indicates which UTM events exist and the result that causes the event to be logged.
Name of event | Meaning | Logging possible |
TASK-ON | Connect a task to the UTM application | Success |
TASK-OFF | Disconnect a task from the UTM application | Success |
SIGN | Sign on a UTM user | Success / Failure |
CHANGE-PW | Change the user password | Success / Failure |
START-PU | Create a job or start a program unit run | Success / Failure |
END-PU | Terminate a program unit run | Success |
DATA-ACCESS | Access a global service UTM storage area (ULS, GSSB, TLS) | Success / Failure |
ADM-CMD | Execute an administration call | Success / Failure |
SEL-CMD | Execute a UTM SAT administration command | Success / Failure |
CHG-PROG | Exchange load modules using BLS | Success / Failure |
Notes
The event SEL-CMD is the only event also logged if SAT logging is switched off for the UTM application, providing the generation of the BS2000 system permits SAT logging.
The events TASK-ON, TASK-OFF and CHG-PROG are always logged when logging is switched on for the UTM application (minimum logging).
The event “end of transaction” (END-PU with TACIDEN=T or C) is always logged when logging for END-PU was not explicitly switched off by event-specific preselection (OFF in the SATSEL statement) and if at least one event was logged for this transaction.
The other events in the table are only logged if they were defined by preselection and logging is switched on.
All UTM events can be linked with the ALARM function of SAT. When the event occurs, a UTM message is then output at the console of the BS2000 computer.