AS/400 Job log not generating

70 pts.
Tags:
AS/400
AS/400 jobs
Spool files
In my server JOB log (Spool file) {QPJOBLOG} is not generating for successfully completion jobs. Which parameters I need to check? Is there any system value I need to change?
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • azohawk
    If the job has messege logging text set as *nolist. "If the job ends normally, no job log is produced".  This can be changed on individual running jobs, changed while submitting a job or if needed to always change it-change the job desciption.
    4,055 pointsBadges:
    report
  • venky484
    what I need to change in job description *nolist to any define parameter ??
    70 pointsBadges:
    report
  • PGMBOB
    If you would check the CHGJOBD command in the manual.
    EZOHAWK suggested to change it in the required job. Changing the job description will change any job subitted for that job description.

    Here are the command notes:
    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. If no values are specified on this parameter, the values specified in the job description associated with this job are used.

    Element 1: Message Level

    The message level specifies the type of information that is logged.

    *SAME: The value does not change.

    message-level: Specify a value, ranging from 0 through 4, for the message logging level used for the job's messages. For a description of the message levels, refer to themessage level variable description in the LOG parameter of the CRTJOBD command.

    Element 2: Message Severity

    The severity level that is used in conjunction with the logging level to determine which error messages are logged in the job log of jobs using this job description.

    *SAME: The value does not change.

    message-severity: Specify a value, ranging from 00 through 99, that is used in conjunction with the logging level to determine which error messages are logged in the job log. More information on message severity is in Commonly used parameters.

    Element 3: Message Text Level

    The level of message text that is written to the job log when a message is logged according to the logging level and the logging severity.

    *SAME: The 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.


    1,235 pointsBadges:
    report
  • Yorkshireman
    you could also set joblog production to *pending - they don't clutter the outq's but can be reviewed, and (eventually) washed out of the system as needed. 

    6,085 pointsBadges:
    report
  • Gayathri123
    Hi Venky,

    Please change the below parameters in your job description to generate complete job log after job completion.

     Message logging:                                                               
       Level  . . . . . . . . . . . .                             0-4, *SAME                    
       Severity . . . . . . . . . . .   00                       0-99, *SAME                   
       Text . . . . . . . . . . . . .   *SECLVL       *SAME, *MSG, *SECLVL,                                                                                        *NOLIST 


    when you use Level 4 , the following information will be logged.

                                                   
         o  All request messages and all messages  
            with a severity greater than or equal  
            to the message logging severity,       
            including trace messages.              
                                                   
         o  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.       
                                                  
    When you use *SECLVL in text, the following messages will be logged in job log,
                                                     
         Both the message text and the message help (cause and 
         recovery) of the error message are written to the job log.

    925 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: