7.4 mjsview Log File Output Command

Synopsis

mjsview  [-sys subsystem-number](*1) [-c | -csv] [log file name]

*1:: [-sys subsystem-number] is an option of Systemwalker Operation Manager EE.

Description

The log file output by the Job Execution Control contains binary attributes, which you cannot read directly. This is why you need to use the mjsview command to edit the log file so that it can be formatted to the standard output to be read.

See the Systemwalker Operation Manager Installation Guide for how to make setting for outputting a log file.

Also note that if "Save job execution history information" (log parameter) is not selected in the [Define Operating Information] window, the log file will be output to the following location.

[Windows]

Job Execution Control spool path\hist\date.log

date: mmddyyyy format

[UNIX]

/var/spool/mjes/hist/date.log

date: mmddyyyy format

Options

-sys subsystem-number

In the system with multiple subsystems, this option is used to specify the subsystem that you want to operate. Specify the target subsystem number using a range of 0 to 9. If omitted, the default is subsystem 0.

-c

This option allows to continue monitoring the log file to continuously format and output logs even after outputting the formatted log contents up to the time of command issuance. If a log file is not found, the command quits.

If this option is omitted, the command terminates after outputting the formatted contents of the log file up to the time of command issuance.

-csv

Specifying this option outputs the contents of the log file up to the time of command issuance to a csv format file, and then the command terminates.

log file name

Specifies the log file name.

If omitted, the last log file that has output job execution history information will be targeted for this command. You must specify a full path name to the log file such as when you process the log file contents on the specific day.

Return Values

Return Value	Meaning
0	The command process has terminated normally.
Other than 0	The command process has failed. An error message is output.

Command Location

Windows	<Systemwalker Operation Manager installation directory>\MpWalker.JM\bin
Solaris HP-UX AIX Linux	/usr/lib/mjes

Privilege Required

System administrator (user belonging to the Administrator group or superuser) privileges are required.

Cautions

If Systemwalker Operation Manager is restarted or the server is down during job queuing, the log information may not be stored in the log file.
For a job for recovery, since the job is restarted when you restart Systemwalker Operation Manager, the same log could be output again.
If all of the following conditions are satisfied, the job purge log will be output to the log file at once.
- On the execution server that executes network jobs.
- You failed to connect from the execution server to the job submitting server when the job is completed. (The job submitting server encountered a system failure or line disconnection.)
- After the connection failed, the connection has succeeded. (This may occur when the job submitting server is restarted or line connection has been reestablished.)

Information

About a trigger to switch to another log file

A log file is not automatically switched to another log file when the date has changed.

If the Job Execution Control service/daemon is running since the previous day and if no job is executed since the date has changed, it means that no log files for today are output. Therefore, a log file switch does not happen in this situation. The log file will be switched to another one when a job is executed after the date has changed.

Output Example

The following is an example output in the mjsview log file output command.

05/27/2015 08:38:52 MJS901I MpMjes service start.
05/27/2015 15:10:22 MJS007I job jobschsleep(13.server1) accept
05/27/2015 15:10:22 MJS001I job jobschsleep(13.server1) start at queue1
05/27/2015 15:10:22 MJS003I job jobschsleep(13.server1) step mjsrjob start on server2:1
05/27/2015 15:10:26 MJS004I job jobschsleep(13.server1) step mjsrjob stop RC(0000)
05/27/2015 15:10:26 MJS002I job jobschsleep(13.server1) stop RC(0000)
05/27/2015 15:10:26 MJS006I job jobschsleep(13.server1) purge
05/27/2015 15:10:32 MJS007I job jobschsleep(14.server1) accept
05/27/2015 15:10:33 MJS001I job jobschsleep(14.server1) start at queue1
05/27/2015 15:10:41 MJS005I job jobschsleep(14.server1) cancel
05/27/2015 15:10:42 MJS002I job jobschsleep(14.server1) stop EC(40000222)
05/27/2015 15:10:42 MJS006I job jobschsleep(14.server1) purge

Remark:: Job Execution Control service activation
Completed job (jobnumber = 13)
Canceled job (job number = 14)

The internal code displayed with "EC" is the string of hexadecimal numbers.
The internal code displayed with "RC" is the string of decimal numbers.

The following is the example when the "-csv" option is specified.

05/27/2015, 2015/,08:38:52,MJS901I,MpMjes service start.
05/27/2015,15:10:22,MJS007I,job jobschsleep(13.server1) accept
05/27/2015,15:10:22,MJS001I,job jobschsleep(13.server1) start at queue1
05/27/2015,15:10:22,MJS003I,job jobschsleep(13.server1) step mjsrjob start on server2:1
05/27/2015,15:10:26,MJS004I,job jobschsleep(13.server1) step mjsrjob stop,RC(0000)
05/27/2015,15:10:26,MJS002I,job jobschsleep(13.server1) stop,RC(0000)
05/27/2015,15:10:26,MJS006I,job jobschsleep(13.server1) purge
05/27/2015,15:10:32,MJS007I,job jobschsleep(14.server1) accept
05/27/2015,15:10:33,MJS001I,job jobschsleep(14.server1) start at queue1
05/27/2015,15:10:41,MJS005I,job jobschsleep(14.server1) cancel
05/27/2015,15:10:42,MJS002I,job jobschsleep(14.server1) stop,EC(40000222)
05/27/2015,15:10:42,MJS006I,job jobschsleep(14.server1) purge

Remark:: Job Execution Control service activation
Completed job (jobnumber = 13)
Canceled job (job number = 14)

The internal code displayed with "EC" is the string of hexadecimal numbers.
The internal code displayed with "RC" is the string of decimal numbers.

Execution Results/Output Format

1) mm/dd/yyyy hh:mm:ss MJS001I job jobname(jobno.hostname) start at queuename
2) mm/dd/yyyy hh:mm:ss MJS002I job jobname(jobno.hostname) stop RC(rc)|EC(ec)
3) mm/dd/yyyy hh:mm:ss MJS003I job jobname(jobno.hostname) step stepname start
  yyyy/mm/dd hh:mm:ss MJS003I job jobname(jobno.hostname) step stepname start on host-name:n
4) mm/dd/yyyy hh:mm:ss MJS004I job jobname(jobno.hostname) step stepname stop RC(rc)|EC(ec)
5) mm/dd/yyyy hh:mm:ss MJS005I job jobname(jobno.hostname) cancel
6) mm/dd/yyyy hh:mm:ss MJS006I job jobname(jobno.hostname) purge
7) yyyy/mm/dd hh:mm:ss MJS007I job jobname(jobno.hostname) accept 
  yyyy/mm/dd hh:mm:ss MJS007I job jobname(jobno.hostname) accept from host-name:n
8) mm/dd/yyyy hh:mm:ss MJS901I MpMjes service start.
9) mm/dd/yyyy hh:mm:ss MJS902I MpMjes service stop.

The following describes the meaning of each log:

1) The job has started.

2) The job has finished.

3) The job step has started.(*1)

4) The job step has finished.

5) The cancel request has been accepted.

6) The job has been removed from a spool.

7) The job has been accepted.(*2)

8) The Job Execution Control service/daemon has started.

9) The Job Execution Control service/daemon has finished.

*1:

If the request source server issues a network job or distributed execution job request to a remote server, "on host-name" is appended to the log. If the request source server issues a network job request to any subsystem, ":n" is also appended to the log.

*2:

If the execution server accepts a network job or distributed execution job from a remote server, "from host-name:n" is appended to the log.

The following explains the contents of the variable parts to be output.

jobname:: Job name is output.

jobno:: The job number assigned by the Job Execution Control is output.

hostname:: The host name that submitted the job is output.

queuename:: The queue name from which the job is started.

stepname:

Job step name is output.

RC(rc)|EC(ec):

Either RC(rc) or EC(ec) is output. If the job processing is aborted due to cancel or network problems, EC(ec) is output. Otherwise, RC(rc) is output.

rc:

Job completion code is output in decimal.

ec:

Completion code of error is output in hexadecimal. If a job is canceled, "40000222" is output.

host-name:n: If the log indicates that the job step has started, the host name of the execution destination server for the network job or distributed execution job is output. If the request source server issues a network job request to any subsystem, ":n" is also appended to the log. The letter n in ":n" represents the subsystem number on the execution destination server.
If the log indicates that the job has been accepted, the host name of the server that requested the network jobs/Distributed Execution jobs is output. The letter n in ":n" represents the subsystem number on the request source server.
When subsystems are not being run, n is 0.