Writing Job Events to a Log File

Logical Names, Global Symbols, and Event Logs › Writing Job Events to a Log File

Writing Job Events to a Log File

Job Management Manager can write a job event-log file that records when a job starts, completes, or encounters an error. The file also records when other significant system activities occur. Users’ actions to control the Job Management Manager or the jobs, or to alter the job database may be logged as well.

The Event Log events are grouped by Event Classes. Select any sub-list of event classes for event logging, among the following available classes:

Class name	Default Selection	Logged Information
JOB_EVENT	X	All job events, specifically job edits and job control events as performed by the Job Management Manager. Job Events are logged as the Job Management Manager actually processes the resulting commands queue or when a job timer triggers.
NORMAL_EVENT		Normal Job Management Manager events, including successful job edits and control events.
ABNORMAL_EVENT	X	Abnormal Job Management Manager events. For example job execution failures and unprivileged access requests denied.
TERMINATION_EVENT	X	Job Management Manager exits.
INTERFACE_EVENT	X	Users’ actions through either the command line or the graphical user interface. Interface Events are logged as the user queues requests to the Job Management Manager.
MAILBOX_MESSAGE		Mailbox messages.
BROADCAST_MESSAGE		Broadcast messages to user terminals.
TIMER_SETTING		Job timer settings.
DATABASE_CHECK		Database consistency check (start and finish).
ERROR_TRAP	X	All error trapping within the Job Management Manager and utilities.
NSCHED_STATUS		All job state changes.

The following Event Classes are configured for logging by default:

JOB_EVENT, ABNORMAL_EVENT, TERMINATION_EVENT, INTERFACE_EVENT, and ERROR_TRAP.

If you have privileges to use the manager’s management commands, you can use logging commands to perform the following functions with this event-log file:

Control the types of information logged with the SCHEDULE SET LOGGING command.
Display the selection of Event Classes currently active for Job Management Manager event logging with the command SCHEDULE SHOW LOGGING.
Close and rename the event-log file with the SCHEDULE CLOSE LOG_FILE command.
Display detailed Job Management Manager event-log reports with the following command:
$ RUN NSCHED$EXE:VSS_REPORTS. EXE

The command pair SET LOGGING /CLUSTER_NODE=node name and SHOW LOGGING /CLUSTER_NODE=node name behaves differently at the DCL level and at the shell because of timing. When you wait 5 seconds between the SET and SHOW commands, both interfaces behave the same and display correct information. SHOW displays the results of the previous SET command. This timing issue occurs because the SET LOGGING/CLUSTER command sends a request to NSCHED to change. If you issue the SHOW LOGGING command immediately, the shell reacts before the change is made.

The name of the event-log file is controlled by the logical name NSCHED$LOGFILE. The system manager should define this logical name in the NSCHED$COM:UJM$MANAGER$STARTUP_nodename.COM file. If you do not define this logical name, the default name is NSCHED$DATA:VERMONT_CREAMERY.LOG.

The default list of Event Classes is governed by the logical name NSCHED$DEFAULT_LOG. See that logical name definition in NSCHED$COM:UJM$MANAGER$STARTUP_LOCAL .TEMPLATE for details.

For more details on the above commands, see the individual command descriptions in the CA Job Management for OpenVMS Command Reference Guide.

Tell Technical Publications how we can improve this information