IBM Tivoli Workload Scheduler. Error Messages. Version 8.1 (Maintenance Release October 2003) SH

Transcription

1 IBM Tioli Workload Scheduler Error Messages Version 8.1 (Maintenance Release October 2003) SH

2

3 IBM Tioli Workload Scheduler Error Messages Version 8.1 (Maintenance Release October 2003) SH

4 Tioli Workload Scheduler Error Messages, Version 8.1 Copyright Notice Copyright IBM Corporation All rights resered. May only be used pursuant to a Tioli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tioli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieal system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, proided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. U.S. Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Trademarks IBM, Tioli and the Tioli logo, are trademarks or registered trademarks of International Business Machines Corporation or Tioli Systems Inc. in the United States, other countries, or both. Windows and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and serice names may be trademarks or serice marks of others. Notices References in this publication to Tioli Systems or IBM products, programs, or serices do not imply that they will be aailable in all countries in which Tioli Systems or IBM operates. Any reference to these products, programs, or serices is not intended to imply that only Tioli Systems or IBM products, programs, or serices can be used. Subject to alid intellectual property or other legally protectable right of Tioli Systems or IBM, any functionally equialent product, program, or serice can be used instead of the referenced product, program, or serice. The ealuation and erification of operation in conjunction with other products, except those expressly designated by Tioli Systems or IBM, are the responsibility of the user. Tioli Systems or IBM may hae patents or pending patent applications coering subject matter in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drie, Armonk, New York , U.S.A.

5 ISO 9001 Certification This product was deeloped using an ISO 9001 certified quality system. Certification has been awarded by Bureau Veritas Quality International (BVQI) (Certification No. BVQI / A). BVQI is a world leader in quality certification and is currently recognized by more than 20 accreditation bodies. iii

6 i Error Messages

7 Contents Preface ii Maintenance Release ii Who Should Read This Guide ii What This Guide Contains ii Tioli Workload Scheduler Publications..... iii Accessing Publications Online ix Ordering Publications ix Proiding Feedback about Publications.....ix Contacting Customer Support ix Conentions Used in This Guide x Chapter 8. Netman Messages Chapter 9. Jobmon Messages Chapter 10. Customize Messages Chapter 11. Conman Messages Chapter 12. Installation Messages Chapter 1. Mailman Messages Chapter 2. Writer Messages Chapter 3. Schedulr Messages Chapter 13. Netman Installation Messages Chapter 14. Remote Console Installation Messages Chapter 4. Jobman Messages Chapter 5. Batchman Messages Chapter 6. Stageman Messages Chapter 15. Common Problems and Troubleshooting Scenarios Glossary Chapter 7. Compiler Messages

8 i Error Messages

9 Preface Tioli Workload Scheduler Error Messages proides details of the error messages that might be encountered during the operating of the Tioli Workload Scheduler. Maintenance Release This is a maintenance refresh of the corresponding IBM Tioli Workload Scheduler Version 8.1 manual, form number SH It contains updates for the APARS fixed with the Tioli Workload Scheduler fix packs up to fix pack 8. Throughout the book, the changed or new sections are marked by reision bars. The name of the fix pack or APAR causing the information change is also featured within the changed chapter, section, or paragraph. If your ersion of the product has not been fixed for a particular APAR, refer to the original ersion of the manual for the corresponding information. Who Should Read This Guide What This Guide Contains This guide is designed to help operators deal with any error messages they encounter during their work with Tioli Workload Scheduler. The guide lists all existing Tioli Workload Scheduler error messages and proides information in terms of explanation, system action, operator response, and other details. Such details do not appear online with the message texts, but are reported in this book. The Tioli Workload Scheduler Messages Guide contains the following sections: Chapter 1, Mailman Messages, on page 1 Describes the error messages generated by the Mailman component. Chapter 2, Writer Messages, on page 5 Describes the error messages generated by the Writer component. Chapter 4, Jobman Messages, on page 9 Describes the error messages generated by the Jobman component. Chapter 5, Batchman Messages, on page 11 Describes the error messages generated by the Batchman component. Chapter 6, Stageman Messages, on page 17 Describes the error messages generated by the Stageman component. Chapter 3, Schedulr Messages, on page 7 Describes the error messages generated by the Schedulr component. Chapter 7, Compiler Messages, on page 21 Describes the error messages generated by the Compiler component. Chapter 9, Jobmon Messages, on page 29 Describes the error messages generated by Jobmon component Chapter 10, Customize Messages, on page 33 Describes the error messages generated by the Customize component. Chapter 8, Netman Messages, on page 25 Describes the error messages generated by the Netman component. ii

10 Chapter 12, Installation Messages, on page 41 Describes the error messages generated during the installation of Tioli Workload Scheduler on Windows NT. Chapter 13, Netman Installation Messages, on page 45, Describes the error messages generated during the installation of Netman on Windows NT. Chapter 14, Remote Console Installation Messages, on page 47 Describes the error messages generated during the installation of the Tioli Workload Scheduler Remote Console. The following table can help you locate the messages by message number: Message Numbers Chapter AWS E to AWS E 1 AWS E to AWS E 2 AWS E to AWS E 3 AWS E to AWS E 4 AWS E to AWS E 5 AWS E to AWS E 6 AWS E to AWS E 7 AWS E to AWS E 8 AWS E to AWS E 9 AWS E to AWS E 10 Tioli Workload Scheduler Installation messages 11 (alphanumeric strings) Netman Installation messages (alphanumeric strings) 12 Remote Console Installation messages (alphanumeric 13 strings) Tioli Workload Scheduler Publications The following documents also proide useful information related to the product for end-to-end scheduling: Table 1. List of Tioli Workload Scheduler Publications Task Planning and installing Tioli Workload Scheduler. Using the Tioli Workload Scheduler command line, understanding how extended and network agents work, and integrating Tioli Workload Scheduler with NetView and with Tioli Business Systems Manager. Publication Tioli Workload Scheduler Planning and Installation Guide Tioli Workload Scheduler Reference Guide Order number SH SH Using the Jaa Gui. Job Scheduling Console User s Guide SH iii Error Messages

11 Table 1. List of Tioli Workload Scheduler Publications (continued) Task Installing, configuring, and using Tioli Workload Scheduler fault-tolerant agents on AS/400. Setting up and using the Tioli Workload Scheduler Plus module. Tioli Workload Scheduler last minute information. Publication Tioli Workload Scheduler AS/400 Limited Fault Tolerant Agent User s Guide Tioli Workload Scheduler Plus Module User s Guide Tioli Workload Scheduler Release Notes Order number SH SH GI Accessing Publications Online Ordering Publications You can access many Tioli publications online at the Tioli Customer Support Web site: These publications are aailable in PDF or HTML format, or both. Translated documents are also aailable for some products. You can order many Tioli publications online at the following Web site: You can also order by telephone by calling one of these numbers: In the United States: In Canada: In other countries, for a list of telephone numbers, see the following Web site: Proiding Feedback about Publications We are ery interested in hearing about your experience with Tioli products and documentation, and we welcome your suggestions for improements. If you hae comments or suggestions about our products and documentation, contact us in one of the following ways: Send an to pubs@tioli.com. Contacting Customer Support Complete our customer feedback surey at the following Web site: If you hae a problem with any Tioli product, you can contact Tioli Customer Support. See the Tioli Customer Support Handbook at the following Web site: Preface ix

12 The handbook proides information about how to contact Tioli Customer Support, depending on the seerity of your problem, and the following information: Registration and eligibility Conentions Used in This Guide Telephone numbers and addresses, depending on the country you are in What information you should gather before contacting support The guide uses seeral typeface conentions for special terms and actions. These conentions hae the following meanings: Information type Style conention Example Commands All capital letters CREATE References in the text to fields on panels All capital letters QUANTITY x Error Messages

13 Chapter 1. Mailman Messages This chapter lists the error messages issued by Mailman. All the message numbers listed below are preceded by AWS E Error Batchman abended, Status: Status Explanation: Mailman issues this message when Batchman terminates unexpectedly. Status contains an exit status message E Error creating Program. Error number System Error Explanation: Mailman was unable to start the Batchman process. Program is the fully qualified name for the Batchman program. System Error is the operating system error message. Operator Response: Make sure that the Batchman executable exists and that it has the correct file access permission. If the problem persists, contact your local serice representatie for assistance E Error creating Program. Error number System Error Explanation: Mailman was unable to start a Mailman serer process. Program is the fully qualified name for the Batchman program. System Error is the operating system error message E Error opening File. Error Error Explanation: Mailman was unable to open for writing either the Courier.msg or the Intercom.msg files. Courier.msg is opened when Mailman is running on a Standard Agent CPU. File is the fully qualified name for the message file. Error is a message that describes the error and includes the operating system error message E Error can not open input file, Error Error Explanation: Mailman is unable to open its message file, Mailbox.msg. This message is also issued if a Mailman serer process is unable to open its message file pobox/[serer].msg. Error is a message that contains information about the error and includes the operating system error message. Operator Response: Too many open files is one of the possible system messages returned. The problem comes either from your Tioli Workload Scheduler user or from your system. One of them has reached its opened files limit (typically 64 for a single user). You can see the user s limits with the limit command. The file limit is the descriptor line for csh users. Take one of the following actions: Add the following lines in your system parameters file(/etc/system) and reboot the system: set rlim_fd_max = 4096 set rlim_fd_cur = 1024 This may consume a short extra memory space, but it speeds up the system. Modify your Tioli Workload Scheduler user enironment (the following stands for a csh user): limit descriptors nnn by replacing nnn with a alue greater than the one you got with limit E Error opening PO Box for CPU Name, Error Error Message Explanation: Mailman is not able to open a message file in the Tioli Workload Scheduler directory named pobox. The message file in the pobox directory contains messages that could not be deliered. CPU Name specifies the name of the message file. Error message describes the error and includes the operating system error message E Error reading input mailbox, Error Error Message Explanation: Mailman was unable to read a message from its local mailbox, Mailbox.msg, or [Serer].msg for a serer Mailman. Error Message describes the error and includes the operating system error message. Operator Response: This is an internal error. Contact 1

14 E E E Error serer jcw bad for Serer Name Explanation: This is an MPE message. Mailman encountered an inalid alue ( alid alues 0 and 1) for a serer enironment ariable. A serer enironment ariable is an enironment ariable with the name of the Mailman serer. Serer Name is the name of the Mailman serer and of the enironment ariable E Error writing to PO Box for CPU Name, Error Error Message Explanation: Mailman was unable to write a message record to the pobox file associated with a CPU. CPU Name is the name of the CPU to which the message is sent. Error Message describes the error and includes the operating system error message E Error reading Sinfonia. Error: Error Message Explanation: Mailman encountered an error while it was reading the Sinfonia file. Mailman sends the Sinfonia file to each CPU at initialization/link time. Error Message contains the fully qualified name of the Sinfonia file and includes the operating system error message E Error opening Sinfonia on Explanation: Mailman failed to allocate the memory necessary to store the records that are to be read from the Sinfonia file. Mailman reads the records during the Symphony download to a CPU. Operator Response: Check if the system has enough memory aailable. Otherwise try to close all the applications you don t need. If the problem persists, contact E Error opening Symphony, Error: Error Message Explanation: Mailman encountered an error when attempting to open the Symphony file. Error Message contains the operating system error message E Error clearing on PO Box for File. Error: Error Message Explanation: Mailman encountered an error while rereading a record from the message file. Mailman processes message records in the following way: 1. It reads a record. 2. It processes the record. 3. It remoes the record from the message file. File is the name of the file that Mailman is processing. Error Message contains the operating system error message E Error reading PO Box for File. Error: Error Message Explanation: Mailman encountered an error while trying to read a message from a message file in the pobox directory. File is the name of the file that Mailman is processing. Error Message contains the operating system error message E Error clearing read on Mailbox. Error: Explanation: Mailman processes record messages in the following way: 1. It reads a record. 2. It processes the record. 3. It remoes the record from the message file. Mailman issues this error when the length of the reread record does not match the length of the record when it was first read E Error CPU Name not found in Symphony Explanation: Mailman cannot find the CPU name of either this node or of the master CPU in the Symphony file. CPU Name is the name of the CPU that Mailman cannot find E Error writing CPU info to Symphony for CPU Name. Error: System Error Explanation: Mailman could not write a CPU record in the Symphony file. CPU Name is the name of the CPU Mailman is trying to write of. 2 Error Messages

15 E E System Error contains the operating system error message E Error locking Straus Explanation: Mailman is unable to lock the Straus database file. This is an MPE message E Error unlocking Straus Explanation: Mailman is unable to unlock Straus. This is a MPE message E Error updating Straus Explanation: Mailman is unable to update Straus. This is a MPE message E Error unknown linktype for CPU Name, linktype is Link Type Explanation: Mailman was unable to link to a CPU because an unknown link type was found in the CPU Symphony record. CPU Name is the name of the CPU that Mailman is trying to link to. Link Type is the type of link (TCP, or DS) E Error writing to intercom. Error: Error Message Explanation: Mailman encountered an error when it tried to write a mailbox record to the Intercom.msg message file. The message could not be sent to Batchman. Error Message contains the operating system error message. Often, the operating system error message is End of file. This means that the internal size limit has been reached. Administrator Response: In response to the End of file error message, expand the message file using the etsize utility. To hae files permanently increased in size internally, insert and set the EVSIZE ariable to the desired size in the StartUp command file (before the run of Netman) in the Tioli Workload Scheduler user s home directory E Error writing to serer Serer Name. Error: Error Message Explanation: Mailman was unable to pass a message to a Mailman serer. Messages are passed to a Mailman serer process by writing mailbox records to its pobox/[serer].msg file. See the serer keyword in the CPU definition for an explanation of Mailman serer processes. Serer Name is the name of the Mailman serer to which the message is sent. Error Message describes the error and includes the operating system error message. Often, the operating system error message is End of file. This means that the internal size limit has been reached. Administrator Response: In response to the End of file error message, expand the message file using the etsize utility. To hae files permanently increased in size internally, insert and set the EVSIZE ariable to the desired size in the StartUp command file (before the run of Netman) in the Tioli Workload Scheduler user s home directory E Error: Not a remote and no batchman Explanation: Mailman cannot access the Batchman program file. Batchman does not run on Standard Agent CPUs, but is needed for Fault Tolerant CPUs. Operator Response: Make sure that the Batchman executable exists and that it has correct file access permission. If the problem persists, contact your local serice representatie for assistance E Warn: DS remotes are inalid, assuming slae for CPU Name Explanation: This is an MPE message. The MPE master does not allow Standard Agent CPUs on MPE systems. CPU Name is the name of the CPU E Error: CPU Name not found in Symphony or Straus Explanation: Mailman cannot find a CPU record in the Symphony file. CPU Name is the name of the CPU whose record Mailman cannot find. Chapter 1. Mailman Messages 3

16 E E E Error Jobman abended. Status: Exit Status Explanation: This message is issued when a Mailman process running on a standard agent CPU acknowledges that Jobman has terminated unexpectedly. Exit Status contains the Jobman exit status E Error start failed: AWS Error: Serice 2002 already actie on NCU E Master mailman gone without quit Explanation: This message is issued by a Mailman serer process when the parent Mailman process has terminated unexpectedly E Error setting traps: Error Message Explanation: Mailman issues this message when it is unable to set the termination signal handling routines. Error Message contains the operating system error message. Operator Response: This is a system error. Contact E Error: writing Symphony header Explanation: Mailman was unable to update the Symphony record header during the initialization process E Error: Can t find this cpu s record in Symphony Explanation: Mailman is unable to find in the Symphony file the CPU record for the CPU on which it is running E Error: cpu CPU Name is a domain manager but is running a prior ersion to 6.0 Explanation: Mailman issues this message when it needs to initialize a CPU that has been defined as a domain manager, but is running an earlier ersion than Maestro 6.0. CPU Name is the name of the CPU Mailman is trying to link to. Operator Response: Either upgrade the CPU to ersion 6.0 or later, or do not define the CPU as a domain manager E Error finding the new manager CPU CPU Name, Error Message Explanation: Mailman is unable to find the new manager CPU in the Symphony file during a switch manager command. CPU Name is the name of the new manager CPU. Error Message is the operating system error E Error: Switching managers in domain Domain Name Explanation: Mailman was unable to switch domain managers. Domain Name is the name of the domain where the switch was taking place. 4 Error Messages

17 Chapter 2. Writer Messages This chapter lists the error messages generated by Writer. All the message numbers listed below are preceded by AWS E Error opening connection to mailman. Error Error Text Explanation: Writer cannot connect to the remote Mailman. The socket descriptor passed to Writer by Netman is inalid. Error Text is a string indicating that the socket descriptor is inalid E Error in ntoh (Symphony rec): Error Text Explanation: An error occurred while conerting a Symphony record from network to host byte order. Error Text contains, when aailable, the record type, the expected record type and the record number E Error sending LinkInit rec: Error Text Explanation: Writer is unable to send the initialization process Link Init record to Mailman. Error Text is a string that describes the error. The information is retrieed from the operating system E Error sending LinkAck rec: Error Text Explanation: Writer is unable to send a LinkAck record to Mailman to acknowledge that a packet has been receied correctly. Error Text is a string that describes the error. The information is retrieed from the operating system E Error receiing record: Error Text Explanation: Writer was unable to read a record from Mailman. Error Text is a string that describes the reason for the error. The information is retrieed from the operating system E Error opening mailbox file: Error Text Explanation: Writer is unable to open the mailbox.msg message file. Error Text is a string that describes the error. The information is retrieed from the operating system E Error writing mailbox file: Error Text Explanation: Writer is unable to write to the message file mailbox.msg. Error Text is a string that describes the error. The information is retrieed from the operating system E Error sending LinkNack rec: Error Text Explanation: Writer is unable to indicate to Mailman with a LinkNack record that there was a communication error while receiing an initialization packet. Error Text is a string that describes the error. The information is retrieed from the operating system E Error sending LinkCmd rec: Error Text Explanation: Writer, when exiting on error, is unable to send an unlink command record to Mailman. Error Text is a string that describes the error. The information is retrieed from the operating system E Error: expecting StopSymphony rec, receied: Error Text Explanation: Writer receied an incorrect command during workstation initialization. Writer expected a stop Symphony command after mailman downloaded the Symphony file. Error Text is not used. 5

18 E E E Error: Unexpected StopSymphony record receied: Error Text Explanation: Writer receied a stop Symphony record when Mailman was not downloading the Symphony file. Error Text is not used E Error: Too few arguments Explanation: Writer is started by Netman with an incorrect number of arguments E Error unable to create stdlist Explanation: Writer is unable to create its stdlist file. Writer creates its own stdlist file when the merge stdlists option is set to no in the localopts file E Error: Could not allocate storage for comarea Explanation: Writer could not allocate memory for internal data structures. Operator Response: Check if the system has enough memory aailable. Otherwise, try to close all the applications that you do not need. If the problem persists, contact your local support representatie for assistance E Error writting an SY init record to the Mailbox Explanation: Writer is unable to write an init synchronization message to Mailman. Mailman uses this message to start its Symphony synchronization process. 6 Error Messages

19 Chapter 3. Schedulr Messages This chapter lists the error messages generated by Schedulr. All the message numbers listed below are preceded by AWS E You must be on the Tioli Workload Scheduler Master CPU to run this program Explanation: Schedulr was run on a CPU that was not the master CPU for the Tioli Workload Scheduler network. This typically occurs on the backup master when long term failoer takes place in the process of creating a new symphony file for the Tioli Workload Scheduler network. Operator Response: Run schedulr on the master CPU. If you were running schedulr on the master CPU, check that the CPU specified by the thiscpu ariable in the local options file, localopts, matches the CPU specified by the master ariable in the global options file, globalopts. Rerun the program E Error allocating memory Explanation: There is not enough memory aailable to complete the operation. Operator Response: Check if the system has enough memory aailable. Otherwise, try to close all the applications that you do not need. If the problem persists, contact your local support representatie for assistance E Error finding schedule is Error Text Explanation: Schedulr encounters an error when trying to find a schedule in the mastsked database. Error Text is the message indicating why the error occurred. Operator Response: The Mozart database may be corrupted. Run Composer and issue the build mastsked command to rebuild the Mastsked database. Rerun Schedulr. If this fails, contact the local support representatie for assistance E Error checking if date is in calendar is Error Text Explanation: Schedulr encountered an error while checking to see if a date is defined for a particular calendar in the Mozart/Calendars database. Error Text is the message indicating why the error occured. Operator Response: The Calendars database may be corrupted. Run Composer and issue the build calendars command to rebuild the Calendars database. Rerun Schedulr. If the problem persists, contact the local support representatie for assistance E Error finding calendar is Error Text Explanation: Schedulr encountered an error while searching for a particular calendar in the Mozart/Calendars database. Error Text is the message indicating why the error occured. Operator Response: The Calendars database may be corrupted. Run Composer and issue the build calendars command to rebuild the Calendars database. Rerun Schedulr. If the problem persists, contact the local support representatie for assistance E Error reading schedule is Error Message Explanation: Schedulr was unable to read a schedule from the database. The schedule was being read so that it could be written to the production file. The default production file name is prodsked. Error Message contains the reason for the error and includes the operating system error message. Operator Response: The Mastsked database may be corrupted. Run Composer and issue the build mastsked command to rebuild the Mastsked database. Rerun Schedulr. If the problem persists, contact the local support representatie for assistance E Error reading dates from calendar is Error Message Explanation: Schedulr was unable to read the dates contained in a calendar from the database. Error Message contains the reason for the error and includes the operating system error message. Operator Response: The Calendars database may be corrupted. Run Composer and issue the build calendars command to rebuild the Calendars database. Rerun Schedulr. If the problem persists, contact the local support representatie for assistance E Error locking schedules is Error Message Explanation: Schedulr is unable to lock the schedule database. The schedule database is locked before Schedulr starts selecting the schedules that will be included in the production day. Error Message contains 7

20 E E the reason for the error and includes the operating system error message. Operator Response: Schedulr may not be able to lock the Mastsked and job.sched databases because the databases may be locked by another process. Determine if another process may hae the databases locked E Error locking calendars is Error Message Explanation: Schedulr is unable to lock the Calendars database. The Calendars database is locked before Schedulr starts selecting the schedules that will be included in the production day. Error Message contains the reason for the error and includes the operating system error message. Operator Response: Schedulr may not be able to lock the Calendars database because the database may be locked by another process. Determine if another process may hae the database locked E Error, in schedule: CPU # Schedule, calendar Calendar is not in the calendars database Explanation: Schedulr is unable to find the calendar specified in a schedule. CPU is the name of the CPU where the schedule is defined. Schedule is the name of the schedule. Calendar is the name of the calendar that cannot be found. Operator Response: Confirm that the calendar specified in the schedule does not exist in the Calendars database. If it does not exist, you may remoe the reference from your schedule. Optionally, you can create the calendar with Composer and rerun Schedulr. Otherwise, contact the local support representatie for assistance. 8 Error Messages

21 Chapter 4. Jobman Messages This chapter lists the error messages issued by Jobman. All the message numbers listed below are preceded by AWS E Setgid() failed with errno = System Error Number Explanation: Jobman cannot set the process group id to the group id of the logon user. System Error Number contains the operating system error message. Operator Response: This is a system error. Contact E Setuid() failed with errno = System Error Number Explanation: Jobman cannot set the process user id to the user id of the logon user. System Error Number contains the operating system error message. Operator Response: Check the job properties in the plan list from the JSConsole or the sj schedid.jobid;l command in Conman to obtain the user id under which Tioli Workload Scheduler is attempting to launch the job. Verify this is a alid user on the system. If incorrectly documented, fix the definition in the database. You can either rerun the job with the from option (specifying the same name of the job) or submit the job into the plan. Administrator Response: If the user is not defined in the system, define it and resubmit the job or rerun it using the fromoption for itself E Chdir() failed with errno = System Error Explanation: Jobman cannot change the current working directory to the home directory of the logon user. System Error is the operating system error message. Operator Response: This is a system error. Contact E Exec failed with errno = System Error Explanation: Jobman can execute the job because the system call used to launch the job failed. System Error is the operating system error message. Operator Response: This is a system error. Contact E Monitor could not fork to create job process. Errno = Error Number Explanation: Jobman could not execute a job or check an external dependency because the fork() system call failed. Error Number is the operating system error message. Operator Response: This is a system error. Contact E Unable to retriee the passwd structure. Errno = System Error Explanation: This message is a WARNING when checking a file dependency or when getting the status of an external dependency. It is an ERROR when trying to launch a job. Jobman cannot retriee the password structure from the system for either the logon user, the Check File user (CFuser), or the Get Status user (GSuser). System Error is the operating system error message. Operator Response: Make sure that the specified user has the logon, the Check File user, or the Get Status user defined in the system. The logon user is specified in the job definition. The Check File user and the Get Status user are specified in the extended agent access method options file ([accessmethod].opts). If the user was documented incorrectly in the plan, update the alue in the database and use the rerun command with the from option so that Tioli Workload Scheduler can read the original definition or resubmit the job into the plan E Jobman attempt to create Monitor failed with errno = System Error Explanation: Jobman was unable to create a process that executes and monitors a job. System Error is the operating system error message. Operator Response: This is a system error. Contact E Setsid failed with errno = System Error Explanation: Jobman cannot create a new session. Jobman creates a new session as part of the process to create a monitor daemon process. The monitor process is the parent of the process that executes a job. System Error is the operating system error message 9

22 E E Operator Response: This is a system error. Contact E Job process Wait error System Error Explanation: A monitor process encountered an error while waiting for its child process to terminate. Jobman creates a monitor process for each job that it launches. The monitor process starts the job, waits for the job to complete, and reports the job exit status. Then, the monitor process terminates. A monitor process is also used by jobman to monitor the method that checks the status of external dependencies. System Error is the operating system error message. Operator Response: This is a system error. Contact See: The job standard list when you do a kill -15 on the jobman process for that job E Inalid test for Filename, test (Test Condition) Explanation: Jobman encountered an inalid test condition when attempting to check an open file dependency. Filename is the name of the file specified by the opens dependency. Test Condition is the qualifier specified in the opens dependency. Operator Response: Make sure that the test condition specified with the opens dependency is alid. Refer to the Tioli Workload Scheduler User s Guide for a list of alid test conditions E Failed to set groups, System Error Explanation: Jobman could not set the group access list for the user specified in the job s logon. System Error is the operating system error message. Operator Response: This is a system error. Contact E Error getting status of External Job: System Error Explanation: Jobman encountered a failure when trying to resole an external dependency. This error is also issued by Jobmon. External Job is the name of the external job (CPU#EXTERNAL.JOB). System Error is the operating system error message. Operator Response: This is embedded in other errors. Check the response associated with the error specified by System Error E Error launching job: Error Message Explanation: This message is displayed when the job fails to launch for arious reasons. Error Message contains the reason for the failure. The Error Message string is obtained from the Tioli Workload Scheduler or Utils catalogs. Operator Response: Check the response associated with the error specified by the System Error ariable. Contact E Out of memory trying to allocate CPU table. Explanation: Jobman cannot allocate memory to store its CPU table. Operator Response: Check if the system has enough memory aailable. Otherwise, try to close all the applications that you do not need. If the problem persists, contact your local support representatie for assistance E Error reading symphony. Explanation: Jobman encountered an error trying to read CPU information from the Symphony file E getlogin failed with System Error Explanation: This system error message is generated by a call to strerror(errno). System Error is the system error message indicating why getlogin failed. Operator Response: This is a system error. Contact E cuserid failed with System Error Explanation: This system error message is generated by a call to strerror(errno). System Error is the system error message indicating why cuserid failed. Operator Response: This is a system error. Contact E Experienced error Error Type. Error Number reading Courier in Source File: Function Name Explanation: Jobman was unable to successfully read a mailbox record from its mailbox file, Courier.msg. Source File is the name of the source file where the error occurred. Function Name is the name of the function where the error occurred (read_courier or delete_courier). Error Type is the internal error type for eent files messages (unison.msg - set 106). Error Number is the internal error number. 10 Error Messages

23 Chapter 5. Batchman Messages This chapter lists the error messages issued by Batchman. All the message numbers listed below are preceded by AWS E Unable to stream job JOB namein file File: Error launching inalid argument. Explanation: Batchman is unable to stream a job in the check connection batch file. An inalid argument was issued.job name is the name of the job not streamed. File is the name of the check connection batch file. Operator Response: This is an internal error. Please contact E Too many jobs are logged on for Batchman to handle Explanation: Batchman is unable to allocate memory for its internal record table during initialization. Possible causes are: The system is running out of memory Bad parameter This error message is more common for an MPE agent/master. It occurs when the default alue of the job table size has been exceeded (160). On MPE systems Tioli Workload Scheduler also tracks user scheduled jobs (from the STREAM command). Any job in the MPE job queue, whether in wait or sched status, will count towards the job table size. Operator Response: Check if the system has enough memory aailable. Otherwise try to close all the applications you do not need. If the problem persists, contact Restart Tioli Workload Scheduler after complying with Admin Response. Administrator Response: Increase the alue for MPEJOBTABLE size in the jbatchmn.maestro.ccc job on the affected agent, master, and backup master. For UNIX, modify the alue in the JM JOBTABLESIZE in the localopts file on the affected agent, master, and backup master. Stop all the Tioli Workload Scheduler background processes including Netman and restart Tioli Workload Scheduler E llegal destination CPU To CPU from From CPU, in Mailbox rec. Explanation: Batchman read from its message file, Intercom.msg, a record whose destination CPU did not match that of Batchman or any of the extended agents hosted by it. To CPU is the name of the destination CPU. From CPU is the name of the origin CPU. Operator Response: This is an internal error. Please contact E Unable to find job record in Symphony file Explanation: Batchman read a record from its local message file, Intercom.msg. The record is a job ID whose record Batchman could not find in the Symphony file. your local serice representatie for assistance E Terminating job does not hae status of Exec Explanation: Batchman read from its mailbox file, Intercom.msg, a Job Terminate record for a job that is not in the execute state. Operator Response: This is an internal error. Please contact E Inalid mailbox record receied: Record Type Explanation: Batchman read a record from its local message file, Intercom.msg, whose type is unknown or whose length does not match the record type length. Record Type is the type of the record, a two character string. Operator Response: This is an internal error. Please contact your serice representatie for assistance E Inalid dependency type discoered in Symphony file Explanation: Batchman found an inalid dependency type in the Symphony file. This message is issued also when a mailbox add dependency record with an unknown dependency type is processed by Batchman. Operator Response: This is an internal error, contact the local support representatie for assistance. 11

24 E E E Unable to find job record in Symphony file Explanation: Batchman cannot find a job record in the Symphony file when it receies a mailbox record that updates the job state. the Tioli support representatie for assistance E Bad dependency flag detected in Symphony file Explanation: Batchman found corrupted job recoery information.while it was attempting to determine the recoery action for a job that terminated with an ABEND state. your local serice representatie for assistance E Schedule Schedule Name does not exist Explanation: Batchman read from Intercom.msg a release all schedule dependencies record; but, it could not find in the Symphony file the schedule record for the schedule being released. Schedule Name is the name of the schedule. your local serice representatie for assistance E Job Job Name does not exist Explanation: Batchman read from Intercom.msg, a release all job dependencies record; but, it could not find in the Symphony file the job record for the job being released. Job Name is the name of the job. your local serice representatie for assistance E Too many jobs are scheduled for Batchman to handle Explanation: The Batchman internal Symphony record table is full and cannot add another record. Operator Response: Batchman has run out of entries in the extension area of the jobtable in the Symphony file. You may increase the size by modifying the Tioli Workload Scheduler NetConf file and restarting Tioli Workload Scheduler. The extension area is used to record ad hoc work, restart jobs, and do the iterations of the jobs that use the eery keyword. Increase the jobtable size in the Symphony file by modifying /usr/lib/maestro/netconf on the following line: mailman -parm jobtablesize where jobtablesize is an integer usually greater than 2000, normally about In order to make the changes take affect once NetConf has been modified, you must shutdown Netman and restart Tioli Workload Scheduler in this order: conman conman conman "shut" conman The shut step must be performed only on those CPUs whose NetConf files hae been updated. Note: The backup master requires this change also. For simplicity, you should make the change on the master and then distribute it to the entire network before the Conman steps explained aboe E Schedule does not exist Explanation: Batchman read from Intercom.msg a mailbox record that modified the dependencies or the state of a schedule. Howeer, Batchman was not able to find the schedule record in the Symphony file. your local representatie for local assistance E Out of memory trying to allocate CPU Count CPU table entries. Explanation: Batchman was unable to allocate memory to hold the internal CPU table that contains the CPUs for which Batchman schedules jobs. CPU Count is the number of CPUs that Batchman is allocating memory for. Operator Response: Check if the system has enough memory aailable. Otherwise try to close all the applications you don t need. If the problem persists, contact E Could not find job/schedule as a holder. Recnum Record Number Explanation: The holder of a resource can not be found in the list of holders that is stored inside the resource Symphony record. The list contains the record number for the holders of the resource. Record Number is the Symphony record number for the holder of the resource. Operator Response: This is an internal error, contact your local representatie for assistence. 12 Error Messages

25 E E E Job Job Name (Job Number) has ABENDED# Explanation: Batchman has receied a mailbox record indication that a job has abended. Job Name is the name of the job (CPU#SCHED.JOB). Job Number is the number assigned to the job. Operator Response: Use internal policies to determine how to handle the abended job. All jobs depending on the abended job will wait until the job is rerun successfully or until it is cancelled. Abended jobs that hae the continue recoery option will not preent dependent jobs from running E Schedule Schedule Name is stuck, operator interention required Explanation: A schedule is in the STUCK state. Schedules will go stuck for different reasons: When jobs in the schedule cannot launch because they depend on a job that has abended. This is the most common reason. When operator interention is required for a reply to a prompt on one of the jobs in the schedule. If a job on which another depends cannot launch because its priority is zero. Schedule Name is the name of the schedule that is stuck. Operator Response: Use internal policies to determine how to handle the abended job. User can either cancel the job to satisfy the other job dependencies or rerun it again successfully. For prompts, replying to the actie prompt will cause a change in status. For priorities, altering the alue to any number greater than 0 will cause a change in state as well E Schedule Schedule Name has terminated with ABENDED jobs Explanation: A schedule has executed all its jobs, but some of the jobs are in the ABEND state. Operator Response: Use internal policies to determine how to handle the abended job(s) E Jobman abended. Exit Code Explanation: Batchman checks to see if Jobman its still running and notices that it has exited unexpectedly. Exit Code is Jobman s exit status code. Operator Response: See the section concerning Jobman in Tioli Workload Scheduler FAQ, in the Tioli support web page, to see if the error matches any of the errors described in the section. If the problem persists, call your local serice representatie E Too many holders of this resource. Explanation: A resource can not be allocated to a job or a schedule because the maximum number of resource holders (maximum 32) has been reached. Administrator Response: Modify the schedules and the resource definition. Split the resource into two or more resources maintaining the same number of resources between all of them. Distribute these resources between the schedules E Error starting Jobman: Error Text Explanation: Batchman is unable to start the Jobman process. Error Text describes at what step of the Jobman creation process the error occurred, and the operating system error. the local support representatie for assistance E Error opening Symphony: Error Text Explanation: Batchman was unable to open the Symphony file. Error Text contains the text of the error indicating why Batchman could not open the Symphony file. Operator Response: Make sure that a Symphony file exists with the correct file permissions and ownership in the Tioli Workload Scheduler directory. If one does not exist, take the appropriate steps to recreate it: 1. Copy a Symphony file from the backup master. 2. Start and link to the agent from the master. If the error occurs at the beginning of the production day, do the following: 1. Use the conman shut command to stop Netman on the agent. 2. Issue the StartUp command. 3. From the master, issue the link and the start commands for the agent E Error opening Intercom: Error Text Explanation: Batchman was unable to open its mailbox file, Intercom.msg. Batchman reads and processes mailbox records from this file. Error Text contains the reason why Batchman could not open the file. the local support representatie for assistance E Error opening Mailbox: Error Text Explanation: Batchman was unable to open the mailbox file, Mailbox.msg, for writing. Batchman writes mailbox records to this file and Mailman processes Chapter 5. Batchman Messages 13

26 E E them. Error Text contains the reason why Batchman could not open the file. the local support representatie for assistance. related information about the job (start time, elapsed time, date started, etc). Operator Response: representatie. Contact your local serice E Error opening courier: Error Text Explanation: Batchman was unable to open the courier file, Courier.msg, for writing. Batchman writes mailbox records to this file and Jobman processes them. Error Text contains the reason why Batchman could not open the file. the local support representatie for assistance E Error accessing Symphony: Error Text Explanation: Batchman was unable to access the Symphony file either for reading or writing. Error Text contains the reason why Batchman could not access the Symphony file. Operator Response: This is an internal error, contact the local support representatie for assistance E Error reading Intercom: Error Text Explanation: Batchman was unable to read from its mailbox file, Intercom.msg. Error Text contains the reason why Batchman could not read the file. the local support representatie for assistance E Error writing mailbox: Error Text Explanation: Batchman was unable to write its mailbox file, Intercom.msg. Batchman writes mailbox records to this file and Mailman processes them. Error Text contains the reason why Batchman could not open the file. the local support representatie for assistance E Error writing Courier: Error Text Explanation: Batchman was unable to write to the mailbox file, Courier.msg. Batchman writes maibox records for Jobman. Error Text contains the reason why Batchman could not open the file. the local support representatie for assistance E Negatie Runtime: Error Text Explanation: This message was added to get debugging information when a job, due to a bug, had a negatie alue for its run time. Error Text contains time E Error while re-installing Sinfonia Explanation: Batchman was unable to create a new Sinfonia file. Batchman creates a new Sinfonia file from the Symphony file during network synchronization processing. the local support representatie for assistance E Error opening Sinfonia Explanation: Batchman was unable to open the Sinfonia file during network synchronization processing. the local support representatie for assistance E Error accessing Sinfonia Explanation: Batchman was unable to access the Sinfonia file during network synchronization processing. the local support representatie for assistance E Error allocating memory (calloc/realloc) for internal tables. Explanation: Batchman encountered an error while trying to allocate memory for its internal CPU table. Operator Response: Check if the system has enough memory aailable. Otherwise, try to close all the applications you do not need. If the problem persists, contact E Calculated negatie elapse time for job J%ld# Explanation: This message is added to Batchman message E. The text of the combined message is: "Negatie Runtime: Operator Response: representatie E Calculated negatie elapse time for job Jnnnnn" Contact your local serice Elapsed time: %ld# Explanation: This message is added to Batchman message E. The text of the combined message is: "Negatie Runtime: Elapsed time: [time]" 14 Error Messages