18.1 Log Files

This section explains the log files that are output by Systemwalker Operation Manager.

Log file types and content

In Systemwalker Operation Manager, the following log files are output:

Log files that are output by default	Log files that are not output by default
Jobscheduler logs Job execution history logs Audit logs	Operation record information logs

Each file is explained below.

Jobscheduler logs

Log content	Job net and job execution history (start time, end time, and completion code)
Log directory	Under the Jobscheduler database directories given below, depending on the operating system used: Windows: <Systemwalker Operation Manager installation directory>\MpWalker.JM\mpjobsch\jobdb Linux: /var/opt/FJSVJOBSC Solaris: /var/opt/FJSVJOBSC HP-UX: /opt/FHPJOBSCH/db AIX: /usr/FAIXJOBSC/db Note: In case of multi-subsystems, the logs are stored under the JOBDBn directory. [n: Subsystem number. A number from 1 to 9 is used.]
File name	jobdb1.log, jobdb2.log, and jobdb3.log
Log file size or retention period	1 - 99 MB (the default is 3 MB) Note: This can be configured in Log file size in the Database sheet of the Define Jobscheduler Startup Parameters window.
Number of files for cyclic use	There are three files (jobdb1.log, jobdb2.log, and jobdb3.log). The number of files cannot be changed. The log files are rotated cyclically according to the file size, as in jobdb1.log -> jobdb2.log -> jobdb3.log -> jobdb1.log. They are not retained based on the number of days.

Job execution history logs

Log content	Job submission, start, end, deletion date, time, and job completion code
Log directory	The default directory is the following: [Windows] <Systemwalker Operation Manager installation directory>\MpWalker.JM\mpmjessv\hist [UNIX] /var/spool/mjes/hist Note: This can be changed in the Logging sheet of the Define Operating Information window. Note: In case of multi-subsystems, the log of subsystem 0 is stored under the above-mentioned directory, while the logs of other subsystems from 1 to 9 are stored under the directory with the corresponding subsystem number n.
File name	yyyymmdd.log (<date when the log file was created>.log)
File format	This contains binary attributes, therefore the file cannot be referenced directly. Use the mjsview command to reference the file.
Log file size or retention period	1 - 31 days (the default is 7 days) Note: This can be configured in the Logging sheet of the Define Operating Information window.
Handling when the retention period is exceeded	Files that have exceeded the specified number of days are deleted.

Operation record information logs

(When configured in "Systemwalker Operation Manager Environment Setup" >> "Operation information" window)

Log type	Operation information about the executed job and job net
Log directory	No default directory Note: This can be configured in the Logging sheet of the Define Operating Information window. Note: In case of multi-subsystems, the log of subsystem 0 is stored under the configured directory, while the logs of other subsystems from 1 to 9 are stored under the directory with the corresponding subsystem number n.
File name	<yyyymmdd>.csv (<date when the operation record information file was created>.csv)
File format	CSV format
Log file size or retention period	1 - 31 days Note: This can be configured in the Logging sheet of the Define Operating Information window.
Handling when the retention period is exceeded	Files that have exceeded the specified number of days are deleted.

Audit logs

Log type	Record information for operations from the Systemwalker Operation Manager client
Log directory	The default directory is the following: [Windows] <Systemwalker installation directory>\MpWalker.JM\mpcmtool\audit [UNIX] /var/opt/FJSVftlo/audit Note: This can be changed using the mpsetlogsend_omgr command.
File name	mp_omgr_audit<YYMMDD>.log (YYMMDD is the date when the operation was recorded)
File format	Text (CSV) format
Log file size or retention period	1 - 99 days or "unlimit" (the default is 31 days) Note: This can be configured using the mpsetlogsend_omgr command.
Handling when the retention period is exceeded	Files that have exceeded the specified number of days are deleted. However, they are not deleted if "unlimit" has been specified.