Cisco Cisco Workload Automation 6.3 User Guide
358
Monitoring Production
Logs in CWA
You can view messages that are too long to be displayed in the log message viewer and you can copy the message text
to the clipboard for use in other applications such as e-mail. The information in the Log Details dialog is read-only.
to the clipboard for use in other applications such as e-mail. The information in the Log Details dialog is read-only.
This dialog contains the following elements:
Type – The type of log (Error or Audit).
Computer – The computer from which the log message originated.
Date – The date the message was logged.
Source – The Scheduler component that was the source of the message.
Time – The time the message was logged.
Job ID – The unique job ID number.
User – The name of the originating user.
Job Name – The name of the originating job.
Msg ID – The message number that corresponds to the message text (also corresponds with the Message list log
filter).
filter).
Agent – The name of the originating agent.
Log Message – The text of the log message.
Log Messages
Error Messages
The following table lists the CWA errors that may appear in log messages
Column Name
Log #
Description
Job %%1 terminated on signal.
2101
The job on the agent was aborted by the CWA system or
terminated in some other manner.
terminated in some other manner.
Problem with spool file for job %%1.
2102
There was a problem with the job script or the
environment file for the given job:
environment file for the given job:
The job’s script file does not exist or cannot be read.
The job data string sent by the master was corrupt.
There was an error transferring the job script from the
master to the agent.
master to the agent.
There was an error transferring the environment file from
the master to the agent.
the master to the agent.
Effective user was not found on agent for job
%%1.
%%1.
2103
The effective or runtime user (the user for whom the job
runs) does not exist on the agent.
runs) does not exist on the agent.
Job name was not provided for job %%1.
2104
The system attempted to launch a job that had no name.
Could not set group id for job %%1.
2105
The agent could not set the group id of the process
executing the job to that of the runtime user.
executing the job to that of the runtime user.
Could not set user id for job %%1.
2106
The agent could not set the user id of the process
executing the job to that of the runtime user.
executing the job to that of the runtime user.