Error creating stdout spool file

Products

• Workload Automation Agent
• DSERIES- SERVER
• CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

Description:

dSeries job has been failing due to "Error creating stdout spool file.

Solution:

If a dSeries job has failed due to "Error creating stdout spool file" you need to investigate the situation on the related Agent environment, i.e. the Unix/Linux operating system where this Agent is installed. The following are some of the common reasons:

1. The file system ran out of the available disk space. You could check it with the 'df' command (refer to your OS Reference guide for the command usage), for example as it's shown for the IBM AIX:

      # df -k               Filesystem    1024-blocks      Free %Used    Iused %Iused Mounted on               /dev/hd4            65536     46488   30%     1690    14% /               /dev/hd2          5898240   1087404   82%    29116    11% /usr               /dev/hd9var        589824    493344   17%      463     1% /var               /dev/hd3          2031616   2028036    1%       91     1% /tmp               /dev/hd1            65536     63972    3%       51     1% /home               /proc                   -         -    -         -     -  /proc               /dev/hd10opt     16842752   9292976   45%    22613     2% /opt

2. The permission on the Agent's spool directory was changed; use the 'ls -al' command against the spool directory and its subdirectories to display the permission.
   
   
3. The maximum value for a file reference has been exceeded. This value is defined by the operating system standard (LINK_MAX). It is usually 32,000 or 32,768 (depending on the OS). Most likely you haven't cleared the spool files for a long period of time so it might have reached this maximum value (you also might have too many files in the Agent's log directory so it would be useful to check this as well). You would need to move as many spool file as possible from their directories and then repeat this procedure regularly.

For all three possible cases above, stop the Agent first, and then perform necessary actions - if needed please get help from your UNIX administrator.

Environment

Release:
Component: SYSAGD