Error Creating Stdout Spool File
productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > > CA Support Online > Support by Product > Support by Product Getting "Error creating stdout spool file" when running one JOB through CA ESP System Agent for UNIX Document ID:TEC473894 Last Modified Date:04/08/2013 {{active ? 'Hide' : 'Show'}} Technical Document Details Products CA Workload Automation Agent CA Workload Automation Agent for HP Integrity NonStop CA Workload Automation Agent for UNIX, Windows, or Linux CA Workload Automation DE CA Workload Automation ESP Edition Releases CA Workload Automation DE:Release:6.1 CA Workload Automation DE:Release:7.0 Components CA Workload Automation System Agent:SYSAGM Description: All the JOBs run through CA ESP System Agent for HPUX have worked fine for quite a while, however today all of them get "Error creating stdout spool file". Solution: For UNIX agents including CA ESP System Agent for HPUX, JOB spool output will be written by the agent user. If the agent runs as root, then only root needs to write to the spool output. In other word, only root needs to have read/write access to spool directory. When script has USER specified, root will setuid to the user and run the script with the permission of the user. Root will write the spool itself. For cmpc(4025), it's actually issued when no more space or too many index in spool sub-directory, therefore agent user (for example root) can't create a new entry for the current job. You need to clear up the spool sub-directory either manually or by scheduling clearspool utility. Please help us improve! Will this information enable you to resolve your issue? Yes No Please tell us what we can do better. {{feedbackText.length ? feedbackText.length : '0'}}/255 {{status}} Not what you were looking for? Search Again> Product Information Support by Product> Product Documentation> Communities Join a Community> Education Find training by product> SHARE THIS {{link.title}} Copyright © 2016 CA. All rights reserved. {{link.title}} North America (English) Chat with CA Just give us some brief information and we'll connect you to the right CA Expert. Our hours of availability are 8AM - 5PM CST. All Fields Required First Name Last Name Email Address How can we help you? We're matching your request. Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here. {{message.agentProfile.name}} will be helping you today. View Profile Transfered to {{message.agentProfile.name}} {{message.agentProfile.name}} joined the conversa
productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > > CA Support Online > Support by Product > Support by Product Error creating stdout spool file Document ID:TEC508415 Last Modified Date:04/08/2013 {{active ? 'Hide' : 'Show'}} Technical Document Details Products CA Workload Automation Agent CA Workload Automation Agent for HP Integrity NonStop CA Workload Automation Agent for i5/OS CA Workload Automation Agent for UNIX, Windows, or Linux CA Workload Automation DE Components CA Workload Automation System Agent:SYSAGD Description: dSeries job has been failing due to "Error creating http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec473894.aspx 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: The file system ran out of the available disk http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec508415.aspx 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 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. 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 ha
from IP address 209.244.4.106I am working on converting our Esscmd scripts to MaxL and had some questions about how to add the error trapping. The MAXL code will be in http://www.network54.com/Forum/58296/thread/1185810794/MaxL+Error+Trapping a .ksh script on our UNIX box. I am looking for MAXL code similar to the IFERROR in esscmd. In our current esscmd backup scripts, if the outline is locked when trying to EXPORT the Essbase data, an error log is generated and email notification is sent stating backup could not complete because the outline was locked (something similar exists if there's a hung process). Without this logic error creating in MAXL I would not be notified if the export failed. Anyway, I know error logic can be written into MAXL IMPORT functions but haven't figured it out for EXPORT functions and just wrapping error trapping around the whole script. I also know that we could logout all users and unlock all objects, but this doesn't always work (again, if there's a hung process). Does anyone have a sample error creating stdout script or some insight into error trapping in MAXL? Thanks!!!Scoring disabled. You must be logged in to score posts.Respond to this messageAuthorReplyToto80.118.33.228Correct answer ?No score for this postJuly 30 2007,12:10 PM .... MaxL documentation ... Most operating systems support three channels for input/output: STDIN (standard input channel) STDOUT (standard output channel) STDERR (standard error channel) Most operating systems also provide command-line options for re-directing data generated by applications, depending on which of the above channels the data is piped through. Errors in MaxL are flagged as STDERR, allowing command-line redirection of errors using operating-system redirection handles. Non errors are flagged as STDOUT; thus normal output may be logged separately from error output. Here is an example of redirecting error-output at invocation time: essmsh script.mxl 2>errorfile.err Note: Operating-system redirection handles vary; check the platform documentation. You can also redirect STDERR and STDOUT independently to different MaxL output logs, using the corresponding options in the spool command. For example, you can direct errors to one file and output to another by placing the following lines in your script: spool stdout on to 'output.txt'; spool stderr on to 'errors.txt'; or you can direct errors only. Scoring disabled. You must be logged in to score posts.Respond to this messageJHand