Job command output logged in Agent Spool directory

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent
• DSERIES- SERVER
• CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

When a command job is defined without the std_out_file clause in the job definition, the output of command will be logged in the agent spool directory.

For example in:

/opt/CA/WorkloadAutomationAE/SystemAgent/spool/D00_SCH/MAIN/WAAE_WF0.1

This may cause the agent file system to get full and causing agent to crash when the volume of the job output exceeds the disk capacity.

If the following parameter is already set in "agentparm.txt" file : agent.spool.success.autocleanup=true ,

the spool cleanup will be activated only after the job is completed successfully.

While the disk space issue may occur while the job is still running. On the other hand, client may want to remove the standard output logging to the spool only for some jobs.

 

 

Environment

Workload Automation Agent 

Resolution

In fact, the System Agent will keep the standard output under the spool directory until the job is completed.

If you have some jobs for which you do not want to get the standard output logged into the spool directory,

one possible solution is to set the std_out_file to /dev/null in your job definition.

Example:

insert_job: jobname
job_type: CMD
command: /dir/script2
machine: machineA
std_out_file: /dev/null

This will allow to avoid getting the data logged in the spool directory