Previous Topic: Collect Log Files for Agents Running on i5/OS or UNIXNext Topic: Agent Logs


Using a Job Log to Debug a Failed Job

These job logs are different than the job logs the i5/OS system creates. The job log contains environment and other diagnostic information that you can use to debug failed jobs.

The agent stores each job log in the spool file directory using the following naming convention:

job.hash.joblog
job

Specifies the name of the job.

hash

Specifies the encryption key that the agent uses to encrypt messages.

Example: Using a Job Log to Debug a Failed Job

A job, running on a Windows system, fails. The agent records the following message in the job log named x.E61ADD84CD3C0864D155EEADD4EEECA6D509D23E.joblog.

20071125 20342154+0500 . MBAGENT X/Y/Z State SUBERROR Failed SetEnd Status(Error creating stdin file) Cmpc(20004) JobLogId(E61ADD84CD3C0864D155EEADD4EEECA6D509D23E)  User(MBAGENT) Host(workstation)

More information:

Enable or Disable Job Logs