General description

In some cases you need more information about some job activity. You can set a job description as *SECLVL message logging in order to have a more detailed joblog or spool file. 

By setting the job description to SEC LEVEL you put the log to DEBUG logging. 

 

Conclusion / Solution / Recommendation / Advice

RUN command:

CHGJOBD JOBD(library/jobName) LOG(4 00 *SECLVL)

For example your library and job name could be B_DETECTOR/SECMONITOR:

CHGJOBD JOBD(B_DETECTOR/SECMONITOR) LOG(4 00 *SECLVL)

Check additional information to know what is the meaning of each parameter.

IMPORTANT NOTE: Restart the job to aply changes.


Additional information

Additional information

IBM article here.

Message logging (LOG)

Specifies the message logging values used to determine the amount and type of information sent to the job log by this job. This parameter has three elements: the message (or logging) level, the message severity, and the level of message text.

Element 1: Level

*SAME
The message logging level does not change.
0-4
Specify the message logging level to be used for the job's messages.

0
No messages are logged.
1
All messages sent to the job's external message queue with a severity greater than or equal to the message logging severity are logged. This includes the indications of job start, job end, and job completion status.
2
The following information is logged:
Logging level 1 information
Request messages which result in a high-level message with a severity code greater than or equal to the message logging severity. Both the request message and all associated messages are logged.
Note: A high-level message is one that is sent to the program message queue of the program that receives the request message. For example, QCMD is an IBM-supplied request processing program that receives request messages.
3
The following information is logged:
Logging level 1 and 2 information
All request messages
Commands run by a CL program are logged if it is allowed by the logging of CL programs job attribute and the log attribute of the CL program.
4
The following information is logged:
All request messages and all messages with a severity greater than or equal to the message logging severity, including trace messages.
Commands run by a CL program are logged if it is allowed by the logging of CL programs job attribute and the log attribute of the CL program.

Element 2: Severity

*SAME
The message severity level does not change.
0-99
Specify the message severity level to be used in conjunction with the logging level to determine which error messages are logged in the job log.

Element 3: Text

*SAME
The message text level value does not change.
*MSG
Only the message text is written to the job log.
*SECLVL
Both the message text and the message help (cause and recovery) of the error message are written to the job log.
*NOLIST
If the job ends normally, no job log is produced. If the job ends abnormally (if the job end code is 20 or higher), a job log is produced. The messages that appear in the job log contain both the message text and the message help.

 

Atention: Remember to rollback this setting to avoid unnecessary log.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: October 22, 2018