Beta 48Extended Job Manager Messages and Codes Version 4 Release 3 January 30, 2009 Document Number: D48EJM43-9-E Beta Systems Software AG Alt-Moabit 90d D-10559 Berlin Tel. +49 (0)30 726 118 – 410 Fax +49 (0)30 726 118 – 810
[email protected] www.betasystems.com SAP, XMI, BC-XBP and RFC are trademarks or registered trademarks of SAP AG. AIX, IBM, MVS/ESA, TWS, z/OS, Tivoli and all IBM products mentioned in this publication are trademarks or registered trademarks of Tivoli Systems or IBM Corporation. HP-UX is a trademark of Hewlett-Packard. Sun Solaris and SunOS are trademarks of Sun Microsystems. Microsoft, Internet Explorer, MS-DOS, Windows, and Windows NT are trademarks or registered trademarks of Microsoft Corporation. Information Mapping is a registered trademark of Information Mapping, Inc. All other brand or product names mentioned in this publication may be trademarks or registered trademarks of their respective owners. © Copyright Beta Systems Software AG, 2009. All rights reserved. This manual may not be copied in part or in its entirety for distribution to third parties without the express written permission of the publisher. List of Publications January 30, 2009 Beta 48 V4.3 Messages and Codes I List of Publications Title Document No. Beta 48 Installation and System Guide Beta 48 Messages and Codes Beta 48 Extended Triggering Facility (ETF) Manual Beta 48 Manual Beta 48 SAP Manual Beta 48 Web Interface Manual BSA Installation and System Guide BSA Report Generator BSA Messages and Codes BSA Service Manager Beta 92 User's Guide Beta 92 Administrator's Guide Beta 92 Installation and System Guide Beta 92 Messages and Codes D48EJM43-7-E D48EJM43-9-E D48EJM43-E-E D48EJM43-M-E D48EJM43-S-E D48EJM43-W-E DBSA42-7-E DBSA42-8-E DBSA42-9-E DBSA42-S-E D92OMS43-3-E D92OMS43-6-E D92OMS43-7-E D92OMS43-9-E Title Document No. Beta 92 Benutzerhandbuch D92OMS43-3-D English German List of Publications II Beta 48 V4.3 Messages and Codes January 30, 2009 Table of Contents January 30, 2009 Beta 48 V4.3 Messages and Codes III Table of Contents Introduction.............................................................................................. 1 Contents..................................................................................................... 1 Finding Messages in the Manuals ............................................................. 2 Beta 48 Return Codes ............................................................................... 3 BQL Return Codes..................................................................................... 3 Message Format ........................................................................................ 4 … of UNIX/Windows and SAP Messages ............................................. 4 … of z/OS Messages ............................................................................. 6 UNIX/Windows and SAP Messages ....................................................... 7 Contents..................................................................................................... 7 200 – 299 UNIX/Windows Messages ...................................................... 8 1000 – 2399 API Messages from the SAP Interface............................. 10 2400 – 2599 Beta Function Modules Messages ................................... 24 3000 – 3099 File Transfer Messages .................................................... 36 3100 – 3199 Event Triggering Messages.............................................. 46 6200 – 9999 API Messages from the Agent .......................................... 48 z/OS Messages....................................................................................... 57 Contents................................................................................................... 57 EJM5000x – EJM5399x Process Messages ........................................... 58 EJM5400I – EJM5499I Monitor Messages............................................ 92 EJM5500x – EJM5599x ETF Messages................................................. 99 EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages...... 105 Return Codes ....................................................................................... 117 RC 0 – 2999 Job and Event Information.......................................... 117 RC 3000 – 3099 File Transfer Errors..................................................... 120 RC 3100 – 3199 Event Triggering Errors .............................................. 122 RC 4000 – 4999 Processing and Transmission Errors ......................... 123 RC 5000 – 5999 Event Submission Errors............................................ 126 Appendix: Calling for Support............................................................ 129 Contents................................................................................................. 129 Overview................................................................................................ 130 General Questions about Your Software Environment.......................... 130 Questions about the Nature of the Error................................................ 130 Batch Jobs ............................................................................................. 131 Table of Contents IV Beta 48 V4.3 Messages and Codes January 30, 2009 Online Functions.................................................................................... 131 Started Task........................................................................................... 132 Displaying Active Tasks......................................................................... 132 Providing Additional Information............................................................ 133 Sending a Dump .................................................................................... 135 Sending Your Databases....................................................................... 137 Checklist before Calling for Support ...................................................... 138 Contents Introduction January 30, 2009 Beta 48 V4.3 Messages and Codes 1 Introduction Contents Topic Page Finding Messages in the Manuals..............................................................2 Beta 48 Return Codes................................................................................3 BQL Return Codes .....................................................................................3 Message Format.........................................................................................4 … of UNIX/Windows and SAP Messages..............................................4 … of z/OS Messages..............................................................................6 In this chapter Introduction Finding Messages in the Manuals 2 Beta 48 V4.3 Messages and Codes January 30, 2009 Finding Messages in the Manuals This manual describes messages produced by the Beta 48 Extended Job Manager (EJM) and its modules, such as the router, the tracker, etc. You will find the message details in this manual or in the respective program manuals (see below). In this manual you will find these messages described in chapter "UNIX/Windows and SAP Messages". In this manual you will find the information messages for each module in chapter "z/OS Messages". The following message ranges are described in the following manuals: Message Ranges Manual UNIX/Windows and SAP Messages: 200 through 299E 1000 through 2399 2400 through 2599 3000 through 3099 3100 through 3199 6200 through 9999 UNIX/Windows Messages API Messages from the SAP interface Beta Function Module Messages File Transfer Messages Event Triggering Messages API Messages from the Agent z/OS Messages: EJM5000x through EJM5399x EJM5400I through EJM5499I EJM5500x through EJM5599x EJM5700x through EJM5999x Process Messages Monitor Messages ETF Messages Cleanup, Statistics, and Event Messages Beta 48 EJM Messages and Codes, i.e. this manual OMS0100x through OMS7999x Beta 92 Messages and Codes xxx8000x through xxx9999x (listed without a three-character prefix) BSA Messages and Codes Which messages you can find in this manual UNIX/Windows and SAP Messages z/OS Messages Message Ranges Beta 48 Return Codes Introduction January 30, 2009 Beta 48 V4.3 Messages and Codes 3 Messages can be found in the log and error files. These files can be viewed with a normal text editor or, for example, via the Web Server's GUI (Graphical User Interface). Beta 48 Return Codes For a list of all Beta 48 return codes, refer to chapter "Return Codes" on page 117. BQL Return Codes All Beta Version 3 products use the Beta Query Language (BQL) to access the database. If database actions result in an error, BQL provides information about the error condition using return and info codes. For a list of codes, refer to the appendix in BSA Messages and Codes. Messages in Log and Error Files Introduction Message Format 4 Beta 48 V4.3 Messages and Codes January 30, 2009 Message Format … of UNIX/Windows and SAP Messages All these messages are stored in a log file. The log file contains the messages that come from the agents, their service programs and transaction programs. The messages received from UNIX/Windows and SAP may look like the following example: 12/17/2008 08:03:49 GPAMONI GPA-10000: Module GPAMON has been started. [V1.2 BUILD 10] - PID=508 12/17/2008 08:03:50 GPASRVI GPA-15000: Module GPASERV (name: LOGADM) has been started. [V1.2 BUILD 10] - PID=572 12/17/2008 08:03:50 GPASRVI GPA-15000: Module GPASERV (name: B48ETP) has been started. [V1.2 BUILD 10] - PID=580 12/17/2008 08:03:50 GPASRVI GPA-15000: Module GPASERV (name: B48TRK) has been started. [V1.2 BUILD 10] - PID=552 12/17/2008 08:03:50 GPASRVI GPA-15000: Module GPASERV (name: B48ONL) has been started. [V1.2 BUILD 10] - PID=544 12/17/2008 08:03:50 GPASRVI GPA-15000: Module GPASERV (name: B48RTR) has been started. [V1.2 BUILD 10] - PID=560 12/17/2008 08:03:51 GPALOGI LOGADM service started. - PID=572 12/17/2008 08:03:51 GPATCPI GPA TCP Transport plugin started - PID=560 12/17/2008 08:03:51 GPATCPI GPA TCP Transport plugin started - PID=552 12/17/2008 08:03:53 B48ETPI B48-12070: Module B48ETP has been started. [V4.3 BUILD 6] - PID=580 Information message <Date> <Time> <Module>I [<Messagenumber>:] <Message> – PID=<pid> When you receive this type of message, no action is required. Error message <Date> <Time> <Module>E [<Messagenumber>:] <Message> – PID=<pid> If you receive an error message, you will need to take action. Overview Example of a log file Format of log records Message Format Introduction January 30, 2009 Beta 48 V4.3 Messages and Codes 5 The following table lists details of the various log record message components. Message component Description Date Date (MM/DD/YYYY) Time Time (HH:MM:SS) Module Name of the module Message number The message number (optional) Message The message text PID The process ID. [...] Values in square brackets are optional and may not appear in every log file record. The message text is written in UPPER CASE, BOLD letters. Certain messages contain portions that can vary, and these portions are indicated by lower case, italic letters. Message components Conventions used in this manual Introduction Message Format 6 Beta 48 V4.3 Messages and Codes January 30, 2009 … of z/OS Messages All z/OS messages described in this manual have a standard format: 1. Three-character prefix EJM, followed by a 2. Four-digit message identifier nnnn and a 3. One-character type code x and a 4. Message text For example: EJMnnnnx message text EJM = prefix pre nnnn = message number x = type code x There are three different type codes for the one-character type code x: E - Error The user should take action now or at a later time. I - Information No user action is required. W - Warning The user should investigate why the message was issued and may need to take action. The message text is written in UPPER CASE, BOLD letters. Certain messages contain portions that can vary, and these portions are indicated by lower case, italic letters. Overview Message format Message type codes Contents UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 7 UNIX/Windows and SAP Messages Contents Topic Page 200 – 299 UNIX/Windows Messages.......................................................8 1000 – 2399 API Messages from the SAP Interface..............................10 2400 – 2599 Beta Function Modules Messages....................................24 3000 – 3099 File Transfer Messages.....................................................36 3100 – 3199 Event Triggering Messages ..............................................46 6200 – 9999 API Messages from the Agent ..........................................48 In this chapter UNIX/Windows and SAP Messages 200 – 299 UNIX/Windows Messages 8 Beta 48 V4.3 Messages and Codes January 30, 2009 200 – 299 UNIX/Windows Messages 201: LOGON FAILED Written to: Log file. Explanation: The user logon could not be successfully performed. System Action: The user is not logged on to the system and the job failed. Operator Response: Check and re-enter the password in the Beta 48 definition database. 202: REQUIRED PRIVILEGE "ACT AS PART OF OPERATING SYSTEM" IS NOT HELD BY THE USER Written to: Log file. Explanation: The user logon could not be successfully performed because the user has not the necessary access right 'Act as part of operating system.' System Action: The user is not logged on to the system and the job failed. Operator Response: See the manual Beta 48 Installation & System Guide. Check the security settings of the user on the Windows site. 203: REQUIRED PRIVILEGE "INCREASE QUOTAS" IS NOT HELD BY THE USER Written to: Log file. Explanation: The user logon could not be successfully performed because the user has not the necessary access right 'Increase Quotas'. System Action: The user is not logged on to the system and the job failed. Operator Response: See the manual Beta 48 Installation & System Guide. Check the security settings of the user on the Windows site. Messages 200 – 299 UNIX/Windows Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 9 204: REQUIRED PRIVILEGE "REPLACE PROCESS LEVEL TOKEN" IS NOT HELD BY THE USER Written to: Log file. Explanation: The user logon could not be successfully performed because the user has not the necessary access right 'Replace Process Level token'. System Action: The user is not logged on to the system and the job is failed. Operator Response: See the manual Beta 48 Installation and System Guide. Check the security settings of the user on the Windows site. 205: START OF JOB FAILED Written to: Log file. Explanation: The job cannot be started. System Action: The job failed. Operator Response: Check the log file. UNIX/Windows and SAP Messages 1000 – 2399 API Messages from the SAP Interface 10 Beta 48 V4.3 Messages and Codes January 30, 2009 1000 – 2399 API Messages from the SAP Interface The following messages are listed: • SAP functions (1000-2999) • General messages (6201-6799) • EDF functions (9000 – 9099) • BQL communication functions (9050 – 9099) 1011/1012: ERROR OCCURRED Explanation: An error has occurred. System Action: The given function cannot be called. The connection has an undefined status. Operator Response: Check the connection between the agent and SAP and their logs. 1021/1022/1023/1024: SYSTEM EXCEPTION RAISED, CONNECTION CLOSED Explanation: A system exception has been raised because an error has occurred in SAP. System Action: Closes the connection to SAP. Operator Response: Check the SAP log. 1031: CALL RECEIVED Explanation: An error occurred while a function in SAP was being called. System Action: The function cannot be called. Operator Response: Check the TCP/IP connection between the agent and SAP. Overview SAP functions 1000 – 2399 API Messages from the SAP Interface UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 11 1041: CONNECTION CLOSED BY THE OTHER SIDE Explanation: The connection has been closed by the other side. System Action: The function cannot be called up. Operator Response: Check the TCP/IP connection to SAP. 1051: FUNCTION ALREADY EXECUTED Explanation: The function has already been executed. System Action: The function cannot be called. Operator Response: There is a problem in SAP or the agent, check the SAP log. 1061: MEMORY INSUFFICIENT Explanation: There is insufficient memory available for the function. System Action: The system retries to call the function. Operator Response: Check the available memory. 1071: VERSION MISMATCH Explanation: Version mismatch. System Action: Function cannot be called. Operator Response: Check the SAP version and the SAP system log or SAP-XMI log. 1081: A SYSTEM CALL SUCH AS RFC_PING IS EXECUTED Explanation: A system call such as RFC_PING has been executed for a connection test. System Action: The function cannot be called. Operator Response: Check the TCP/IP connection between the agent and SAP. UNIX/Windows and SAP Messages 1000 – 2399 API Messages from the SAP Interface 12 Beta 48 V4.3 Messages and Codes January 30, 2009 1091: NO DATA YET Explanation: No data is available. System Action: The system retries to find data. Operator Response: None. 1100: UNKNOWN ERROR IN RFC CONNECTION Explanation: There is an error in the RFC connection. System Action: The connection is not opened. Operator Response: Check the SAP system log or SAP-XMI log. 1101: ERROR IN RFC PROGRAM Explanation: There is an error in the RFC program. System Action: The connection is not opened. Operator Response: None. 1102: ERROR IN NETWORK & COMMUNICATION Explanation: There is an error in network and communications. System Action: The connection is not opened. Operator Response: Check the TCP/IP connection agent – SAP. 1103: SAP LOGON ERROR Explanation: A SAP logon error has occurred. System Action: The connection is not opened. Operator Response: Check the authority of the logon data. 1000 – 2399 API Messages from the SAP Interface UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 13 1104: SAP SYSTEM EXCEPTION RAISED Explanation: A SAP system exception has been raised. System Action: The connection is not opened. Operator Response: Check the SAP logs. 1105: THE CALLED FUNCTION MODULE RAISED AN EXCEPTION Explanation: The called function module raised an exception. System Action: The connection is not opened. Operator Response: Check the SAP logs. 1106: RESOURCE NOT AVAILABLE Explanation: The resource is not available, e.g. insufficient memory. System Action: The connection is not opened. Operator Response: Check the SAP logs. 1107: RFC PROTOCOL ERROR 1108: RFC INTERNAL ERROR Explanation: An internal RFC protocol error has occurred. System Action: The connection is not opened. Operator Response: Check the SAP logs. UNIX/Windows and SAP Messages 1000 – 2399 API Messages from the SAP Interface 14 Beta 48 V4.3 Messages and Codes January 30, 2009 1109: RFC REGISTERED SERVER WAS CANCELLED Explanation: The RFC registered server was cancelled. System Action: The connection is not opened. Operator Response: Check the SAP logs. 1110: SYSTEM IS BUSY, TRY LATER Explanation: The system is busy. System Action: The connection is not opened. The system automatically retries to function. Operator Response: None. 1111: INVALID RFC HANDLE Explanation: The RFC handle is invalid. Presumably the connection to SAP has been broken. System Action: The system automatically retries to function. Operator Response: None. 1299: UNSUPPORTED FUNCTION Explanation: A function that is not supported by SAP has been called (internal error). System Action: None. Operator Response: None. 1000 – 2399 API Messages from the SAP Interface UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 15 2221/2222: PRODUCT IS ALREADY LOGGED ON Explanation: The product has tried to logon to the system several times. System Action: The system automatically retries the action. Operator Response: Check whether a permanent problem has occurred. 2223: INTERFACE IS NOT SUPPORTED BY THE SYSTEM Explanation: The specified interface is not supported by SAP. System Action: The system cannot work with this interface. Operator Response: Check the system version in SAP. 2224: VERSION OF THE INTERFACE IS NOT SUPPORTED Explanation: The specified interface has a wrong version number. System Action: The system cannot work with this interface. Operator Response: Check the system version in SAP. 2225/2226: AUTHORIZATION FAILED Explanation: The authorization to execute the function is not available. System Action: The system cannot execute the specified function. Operator Response: Check the authorization in the system log and the XMI log. UNIX/Windows and SAP Messages 1000 – 2399 API Messages from the SAP Interface 16 Beta 48 V4.3 Messages and Codes January 30, 2009 2227/2228: THERE IS NO CONNECTION TO THE R/3 SYSTEM Explanation: The product is not connected to the SAP system. System Action: The system automatically retries the action. Operator Response: Check the system activities. 2229: THERE IS AN INVALID RANGE Explanation: One or more parameters are invalid (internal program error). System Action: The system automatically retries the action. Operator Response: Check the system activities. 2230: CANNOT SELECT Explanation: The SAP system cannot select some tables. System Action: The system automatically retries the action. Operator Response: Check the system logs in the SAP system concerned. 2231: R/3 XMI LOGGING MECHANISM RETURNED AN ERROR Explanation: An error has occurred in the SAP – XMI interface. System Action: The system cannot work with the SAP system. Operator Response: Check the XMI table in the SAP system. 1000 – 2399 API Messages from the SAP Interface UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 17 2232: CANNOT UPLOAD Explanation: Data cannot be sent to the SAP system. System Action: The system automatically retries the action. Operator Response: Check your SAP system. 2233: INPUT PARAMETERS ARE INVALID Explanation: The parameters entered are invalid (internal program error). System Action: The system automatically retries the action. Operator Response: Check the system activities and the SAP system log. 2234: XMI PROBLEM WHICH CANNOT BE FURTHER SPECIFIED Explanation: An error has occurred in the SAP system. Further information about the problem is not available. System Action: The system automatically retries the action. Operator Response: Check the SAP system and the IP connection. 2235: REORG GEN Explanation: A Reorg Gen error has occurred in the SAP system. System Action: The system cannot call the specified function. The system automatically retries the action. Operator Response: Check the SAP system concerned. UNIX/Windows and SAP Messages 1000 – 2399 API Messages from the SAP Interface 18 Beta 48 V4.3 Messages and Codes January 30, 2009 2236: REORG. Explanation: A reorganization error has occurred in the SAP system. System Action: The system cannot call the specified function. The system automatically retries the action. Operator Response: Check the SAP system concerned. 2237: JOBNAME IS MISSING Explanation: A job is to be started or selected but the job name is missing. System Action: The job start failed. Operator Response: Check the job and system logs. 2238: JOBID (JOB COUNT) IS MISSING Explanation: The job ID is invalid. System Action: The agent cannot find the SAP job ID and therefore cannot work with the job. Operator Response: Check the job and system logs. 2239: THE NAME OF THE EXTERNAL USER IS MISSING Explanation: An unidentified user tried to work with the SAP system. System Action: The job is not started. Operator Response: Check the job and system logs. 1000 – 2399 API Messages from the SAP Interface UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 19 2240: THE SPECIFIED JOB DOES NOT EXIST IN R/3 Explanation: In the SAP system, an action is to be started with the specified job ID. The job does not exist in the SAP system. System Action: The action cannot be executed. Operator Response: Check whether the job has been deleted in the SAP system. 2246: JOB IS NOT ACTIVE Explanation: The system expected the job to be active. System Action: None. Operator Response: None. 2248: NO JOBS WERE FOUND Explanation: The SAP system could not find any of the specified jobs. System Action: None. Operator Response: None. 2250: THE SPECIFIED JOB HAS NO STEPS Explanation: No steps could be found in the job. System Action: The system cannot start the job. Operator Response: Check the job definitions. UNIX/Windows and SAP Messages 1000 – 2399 API Messages from the SAP Interface 20 Beta 48 V4.3 Messages and Codes January 30, 2009 2251: THE JOB HAS NO LOG Explanation: The job has not created a log or the log was deleted. System Action: The system cannot read the SAP log of the job. Operator Response: Check the SAP system log. 2252: THE LOG OF THE JOB IS EMPTY Explanation: The job log is empty. System Action: The system cannot read the SAP log of the job. Operator Response: Check the SAP system log. 2254: THE STEP HAS NO SPOOL LIST Explanation: The job step has no spool list. System Action: The system cannot read the spool list. Operator Response: Check the SAP system log. 2255: NOT AUTHORIZED Explanation: The system is not authorized to execute the specified function. System Action: The system cannot execute the specified function. Operator Response: Check the system log. 1000 – 2399 API Messages from the SAP Interface UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 21 2256: STEP HAS AN INVALID SPOOLID Explanation: The spool administration of the SAP system doesn't work properly. System Action: The spool list cannot be read. Operator Response: Check the SAP system log. 2259: THE DATE AND TIME PARAMETER IS INVALID Explanation: The date and/or time parameter is invalid (internal error). System Action: None. Operator Response: None. 2266: INVALID SELECTION OPTIONS Explanation: While trying to select an SAP table, invalid selection options have been used. System Action: None. Operator Response: None. 2267: SELECTION PARAMETER IS MISSING Explanation: An attempt is being made to select an SAP table, but the selection parameter is missing. System Action: None. Operator Response: None. UNIX/Windows and SAP Messages 1000 – 2399 API Messages from the SAP Interface 22 Beta 48 V4.3 Messages and Codes January 30, 2009 2268: SELECT JOBNAME IS MISSING Explanation: An attempt is being made to select an SAP table, but the job name is missing. System Action: None. Operator Response: None. 2269: SELECT USERNAME IS MISSING Explanation: An attempt is being made to select an SAP table, but the user name is missing. System Action: None. Operator Response: None. 2270: ONE OR MORE OF THE JOB'S DATA ENTRIES CANNOT BE DELETED Explanation: The job cannot be deleted in the SAP system. System Action: None. Operator Response: Check the SAP system log and the job table. 2271: CANNOT DELETE THE LOG OF THE JOB Explanation: The log of the job cannot be deleted in the SAP system. System Action: None. Operator Response: Check the SAP system log and the job table. 1000 – 2399 API Messages from the SAP Interface UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 23 2273: COMMIT FAILED Explanation: COMMIT failed in the SAP system. System Action: None. Operator Response: Check the SAP system log. 2274: NO DELETE PRIVILEGE Explanation: The user has no deletion rights. System Action: None. Operator Response: Check the user rights in the SAP system. 2275: JOB IS RUNNING Explanation: An attempt has been made to start a job that is already running. System Action: The job cannot be started twice. Operator Response: Check whether other systems automatically start planned jobs. 2399: UNKNOWN EXCEPTION Explanation: The SAP system is reporting an unknown error. System Action: The system retries to process the function(s) concerned. Operator Response: Check the SAP system log. UNIX/Windows and SAP Messages 2400 – 2599 Beta Function Modules Messages 24 Beta 48 V4.3 Messages and Codes January 30, 2009 2400 – 2599 Beta Function Modules Messages The following error messages may appear when Beta function modules for SAP have been installed. 2401: AUTHORIZATION FAILED Written to: Log file. Explanation: You are not allowed to change the respective variant. System Action: The specified user does not have the privilege to change variants. Operator Response: Check the user access rights in the user profile. 2402: EXECUTION FAILED Written to: Log file. Explanation: A change in a panel has not been executed. System Action: The specified panel change could not be executed. Operator Response: Check the system log. 2403/2404: THE REPORT DOES NOT EXIST Written to: Log file. Explanation: The report is not available. System Action: The report specified while copying a variant does not exist. Operator Response: Check the report entries. Overview Messages 2400 – 2599 Beta Function Modules Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 25 2405: THE REPORT IS NOT SUPPLIED Written to: Log file. Explanation: A report name has not been specified. While copying a variant, a report name has not been entered. System Action: The job ends with errors. Operator Response: Check the report entries in the respective job. 2406: THE VARIANT DOES ALREADY EXIST Written to: Log file. Explanation: An error occurred while copying a variant. The specified variant already exists. System Action: The job ends with errors. Operator Response: Check the variant. 2407: THE VARIANT IS LOCKED BY THE SYSTEM Written to: Log file. Explanation: An error occurred while reading a variant. The variant is locked by the SAP system. System Action: The job ends with errors. Operator Response: Use transaction SM12 to check the log entries. UNIX/Windows and SAP Messages 2400 – 2599 Beta Function Modules Messages 26 Beta 48 V4.3 Messages and Codes January 30, 2009 2408: THE VARIANT DOES NOT EXIST Written to: Log file. Explanation: An error occurred while reading a variant. The specified variant does not exist. System Action: The job ends with errors. Operator Response: Check the variant. 2409: ILLEGAL REPORT OR VARIANT DETECTED Written to: Log file. Explanation: A wrong report or variant name has been specified. While changing some parameters, a wrong report or variant name has been found. System Action: The job ends with errors. Operator Response: Check the respective report and variant. 2410: ILLEGAL NAME OF VARIANT Written to: Log file. Explanation: An invalid variant name has been entered. System Action: The job ends with errors. Operator Response: Check the variant and its parameters. 2400 – 2599 Beta Function Modules Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 27 2411: THE SELECTIONS DO NOT MATCH Written to: Log file. Explanation: The type or length of the specified selection is incorrect. System Action: The job ends with errors. Operator Response: Compare the parameters of the variant to the ones specified in the job. 2412: ILLEGAL PARAMETER FOUND Written to: Log file. Explanation: An error occurred while reading the parameters of a variant. System Action: The job ends with errors. Operator Response: Check the parameters in the specified variant and correct the parameters in the respective job accordingly. 2413: THE VARIANT IS NOT IN CATALOG Written to: Log file. Explanation: An error occurred while reading the variant catalog. System Action: The job ends with errors. Operator Response: Check the specified variant name. 2414: INVALID PARAMETER Written to: Log file. Explanation: The job contains an invalid parameter. System Action: The job ends with an error. Operator Response: Check the specified job. UNIX/Windows and SAP Messages 2400 – 2599 Beta Function Modules Messages 28 Beta 48 V4.3 Messages and Codes January 30, 2009 2415: A JOB WITH THE SAME NAME HAS NOT YET BEEN COMPLETED Written to: Log file. Explanation: A direct input job with the same name has ended with an error. A job with the same name cannot be started. System Action: The job ends with an error. Operator Response: Check the specified job. 2430: ERROR WHILE OPENING A NEW JOB Written to: Log file. Explanation: An error occurred while entering something new into an SAP job. System Action: The creation of the new job failed. The respective job ends with errors. However, running jobs will still be monitored. Operator Response: Check the SAP system log. 2431: ERROR WHILE DEFINING A NEW STEP Written to: Log file. Explanation: An error occurred while entering a new step into an SAP job. System Action: The creation of the new job failed. The respective job ends with errors. However, running jobs will still be monitored. Operator Response: Check the SAP system log. 2400 – 2599 Beta Function Modules Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 29 2432: NO RESULT WHILE SELECTING SESSIONS Written to: Log file. Explanation: According to the selection criteria entered, no batch input maps could be found. System Action: The creation of the job failed. The respective job ends with errors. Operator Response: Check the specified selection criteria. 2433: ERROR WHILE CLOSING A JOB Written to: Log file. Explanation: An error occurred while closing and starting the job in an SAP system. System Action: The creation of the job failed. The respective job ends with errors. However, running jobs will still be monitored. Operator Response: Check the SAP system log. 2434: NO SESSION FOUND Written to: Log file. Explanation: An error occurred while reading the status of a batch input map. System Action: The batch input map status could not be read. The job status is set to 'ERROR'. Operator Response: Check the batch input map status with the help of the SAP transaction SM35. UNIX/Windows and SAP Messages 2400 – 2599 Beta Function Modules Messages 30 Beta 48 V4.3 Messages and Codes January 30, 2009 2435: CANNOT READ OLD BATCH INPUT LOG Written to: Log file. Explanation: An error occurred while reading the log of a batch input map. System Action: The log of a batch input map could not be transferred because it has been written in an old format. Operator Response: Use the SAP transaction RZ11 to check the SAP profile parameter bdc/new_protocol. 2436: BATCH INPUT LOG NAME IS MISSING Written to: Log file. Explanation: An error occurred while reading entries in the log directory. System Action: A log directory entry is not available. Operator Response: Check the SAP TemSe in CCMS. 2437: CANNOT READ BATCH INPUT LOG Written to: Log file. Explanation: An error occurred while reading the SAP TemSe log file. System Action: The log cannot be read in the SAP TemSe. Operator Response: Check the SAP TemSe in CCMS. 2400 – 2599 Beta Function Modules Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 31 2438: BATCH INPUT LOG IS EMPTY Written to: Log file. Explanation: An error occurred while reading the log of a batch input map. System Action: The log of the batch input map has no entries. Operator Response: Use the SAP transaction SM35 to check the processing of the batch input map. 2450: RUNNING DATE IS NOT GIVEN Written to: Log file. Explanation: The parameter <RUN DATE> has not been set. System Action: Mass activities could not be started. The job ends with errors. Operator Response: Check the specified job and enter a run date. 2451: RUNNING ID IS NOT GIVEN Written to: Log file. Explanation: The parameter <RUN ID> has not been set. System Action: Mass activities could not be started. The job ended with errors. Operator Response: Check the specified job and enter a run ID. 2452: JOB TYPE IS NOT GIVEN Written to: Log file. Explanation: The parameter <JOB TYPE> has not been set. System Action: Mass activities could not be started. The job ended with errors. Operator Response: Check the specified job and enter a job type. UNIX/Windows and SAP Messages 2400 – 2599 Beta Function Modules Messages 32 Beta 48 V4.3 Messages and Codes January 30, 2009 2453: ERROR WHILE PLANNING A JOB Written to: Log file. Explanation: An error occurred while planning a mass job. System Action: Mass activities could not be started. The job ended with errors. Operator Response: Check the specified job and the SAP system log. 2454: COPYING OF PARAMETERS FAILED Written to: Log file. Explanation: An error occurred while copying parameters. System Action: Mass activities could not be started. The job ended with errors. Operator Response: Check the specified job and the SAP system log. 2455: MODEL DOES NOT EXIST Written to: Log file. Explanation: The model does not exist. System Action: Mass activities could not be started. The job ended with errors. Operator Response: Check the specified job. 2456: PARAMETERS DO NOT EXIST Written to: Log file. Explanation: The parameters do not exist. System Action: Mass activities could not be started. The job ended with errors. Operator Response: Check the specified job. 2400 – 2599 Beta Function Modules Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 33 2457: PARAMETERS DO EXIST AND CANNOT BE OVERWRITTEN Written to: Log file. Explanation: The parameters do exist and therefore cannot be overwritten. System Action: Mass activities could not be started. The job ended with errors. Operator Response: Check the specified job. 2458: FUNCTION MODULE DOES NOT EXIST Written to: Log file. Explanation: The required function module does not exist. System Action: Mass activities could not be started. The job ends with errors. Operator Response: Check the specified job and the SAP system log. 2470: INFO PACKAGE DOES NOT EXIST Written to: Log file. Explanation: Technical Info Package's ID is not defined in SAP BW. System Action: Check the Info Package ID in SAP BW. Operator Response: Adjust the Info Package ID in the script. 2471: NO LOAD SELECTION (SCHEDULING) AVAILABLE FOR INFOPACKAGE Written to: Log file. Explanation: The Info Package cannot be started. System Action: The job ends with an error. Operator Response: Check the cause in SAP Business Warehouse. UNIX/Windows and SAP Messages 2400 – 2599 Beta Function Modules Messages 34 Beta 48 V4.3 Messages and Codes January 30, 2009 2472: INFOPACKAGE CURRENTLY RUNNING, NO FURTHER SCHEDULING POSSIBLE Written to: Log file. Explanation: The Info Package has already been processed. Further scheduling is currently impossible. System Action: Check the processing of the Info Package in SAP Business Warehouse. Operator Response: Check the cause in SAP Business Warehouse. 2473: INFOPACKAGE IS ALREADY SCHEDULED, NO FURTHER SCHEDULING POSSIBLE Written to: Log file. Explanation: The Info Package is already scheduled; no further scheduling is possible. System Action: Check the processing of the Info Package in SAP Business Warehouse. Operator Response: Check the cause in SAP Business Warehouse. 2474: INFOPACKAGE SELECTIONS DO NOT EXIST Written to: Log file. Explanation: The Info Package cannot be selected. System Action: The job ends with an error. Operator Response: Check the cause in SAP Business Warehouse. 2400 – 2599 Beta Function Modules Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 35 2599: UNKNOWN EXCEPTION Written to: Log file. Explanation: The SAP system reports an unknown error. System Action: The system retries to process the respective function(s). Operator Response: Check the SAP system log. UNIX/Windows and SAP Messages 3000 – 3099 File Transfer Messages 36 Beta 48 V4.3 Messages and Codes January 30, 2009 3000 – 3099 File Transfer Messages 3000: SYNTAX ERROR OCCURRED Written to: Log file and condition code of the corresponding job. Explanation: A syntax error occurred in FTPSTEP. System Action: Job is aborted. Operator Response: Check the syntax. 3001: USER NOT DEFINED IN RACF Written to: Log file and condition code of the corresponding job. Explanation: During FTP, the STC applies an enabled RACF check – (B48_FTP_RACFCHECK=YES). The user who sent the job, could not be logged in by the STC. System Action: Job is aborted. Operator Response: Check user definition in RACF. 3002: NO RACF RESOURCE DEFINED FOR GIVEN DATASET Written to: Log file and condition code of the corresponding job. Explanation: During FTP, the STC applies an enabled RACF check – (B48_FTP_RACFCHECK=YES). No RACF resource has been defined for the DATASET given in the FTPSTEP. System Action: Job is aborted. Operator Response: Check DATASET definition in RACF. Messages 3000 – 3099 File Transfer Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 37 3003: USER CANNOT READ FROM THE GIVEN DATASET Written to: Log file and condition code of the corresponding job. Explanation: During FTP, the STC applies an enabled RACF check – (B48_FTP_RACFCHECK=YES). According to RACF, the user who sent the job is not allowed to access and read the DATASET. System Action: Job is aborted. Operator Response: Check the user/dataset definition in RACF. 3004: USER CANNOT WRITE TO THE GIVEN DATASET Written to: Log file and condition code of the corresponding job. Explanation: During FTP, the STC applies an enabled RACF check – (B48_FTP_RACFCHECK=YES). According to RACF, the user who sent the job is neither allowed to access the dataset nor to write to it. System Action: Job is aborted. Operator Response: Check user/dataset definition in RACF. 3005: MEMBER DOES NOT EXIST IN GIVEN DATASET Written to: Log file and condition code of the corresponding job. Explanation: The MEMBER does not exist in the DATASET. System Action: Job is aborted. Operator Response: Check job. UNIX/Windows and SAP Messages 3000 – 3099 File Transfer Messages 38 Beta 48 V4.3 Messages and Codes January 30, 2009 3006: MEMBER DOES ALREADY EXIST IN GIVEN DATASET Written to: Log file and condition code of the corresponding job. Explanation: The member already exists in the dataset. System Action: Job is aborted. Operator Response: Check job. 3007: CANNOT ALLOCATE DATASET Written to: Log file and condition code of the corresponding job. Explanation: The DATASET could not be allocated. System Action: Job is aborted. Operator Response: Check job/dataset. 3008: CANNOT OPEN DATASET Written to: Log file and condition code of the corresponding job. Explanation: The DATASET could not be opened. System Action: Job is aborted. Operator Response: Check job/dataset. 3000 – 3099 File Transfer Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 39 3009: BINARY TRANSMISSION FAILED FOR FIXED BLOCK DATASET Written to: Log file and condition code of the corresponding job. Explanation: The DATASET has been generated in FB format (fixed block). As a rule binary file transfer should only be executed to VB datasets. A binary file transfer (method GET) to FB datasets can only be executed when the size of the UNIX/Windows files is much larger than the block size. System Action: Job is aborted. Operator Response: Check job/dataset. 3010: LINE TOO LONG Written to: Log file and condition code of the corresponding job. Explanation: A file was supposed to be transferred in TEXT mode from Unix to the host (method GET). It was detected that the maximum record length in the DATASET had been exceeded by at least one line. System Action: Job is aborted. Operator Response: Check job/dataset. 3011: ERROR WHILE WRITING Written to: Log file and condition code of the corresponding job. Explanation: An error has been detected while writing to the DATASET. System Action: Job is aborted. Operator Response: Check job/dataset. UNIX/Windows and SAP Messages 3000 – 3099 File Transfer Messages 40 Beta 48 V4.3 Messages and Codes January 30, 2009 3012: ERROR WHILE READING Written to: Log file and condition code of the corresponding job. Explanation: An error has been detected while reading the DATASET. System Action: Job is aborted. Operator Response: Check job/dataset. 3013: BAD DATASET ORGANIZATION Written to: Log file and condition code of the corresponding job. Explanation: The DATASET has a bad organization. The job expects either PS- or PO- organized DATASETS. The definition in the job does not correspond to the DATASET definition. System Action: Job is aborted. Operator Response: Check job/dataset. 3014: STC CANNOT READ FROM THE GIVEN DATASET Written to: Log file and condition code of the corresponding job. Explanation: The Beta 48 STC is not authorized to read from the given DATASET. System Action: Job is aborted. Operator Response: Check job/dataset. 3000 – 3099 File Transfer Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 41 3015: STC CANNOT WRITE TO THE GIVEN DATASET Written to: Log file and condition code of the corresponding job. Explanation: The Beta 48 STC is not authorized to write to the given DATASET. System Action: Job is aborted. Operator Response: Check job/dataset. 3016: NOT ENOUGH SPACE Written to: Log file and condition code of the corresponding job. Explanation: While writing to the DATASET it was detected that there is not enough space available. System Action: Job is aborted. Operator Response: Check job/dataset. 3017: UNKNOWN ERROR WHILE SENDING FILE TO TRACKER Written to: Log file and condition code of the corresponding job. Explanation: An unknown error occurred during data exchange with tracker. System Action: Job is aborted. Operator Response: Check job/dataset. 3018: UNKNOWN ERROR WHILE RECEIVING FILE FROM TRACKER Written to: Log file and condition code of the corresponding job. Explanation: An unknown error occurred during data exchange with Beta 48 STC. System Action: Job is aborted. Operator Response: Check job/dataset. UNIX/Windows and SAP Messages 3000 – 3099 File Transfer Messages 42 Beta 48 V4.3 Messages and Codes January 30, 2009 3050: CANNOT READ FROM GIVEN FILE Written to: Log file and condition code of the corresponding job. Explanation: It cannot be read from given file. System Action: Job is aborted. Operator Response: Check user/file. 3051: CANNOT WRITE TO GIVEN FILE Written to: Log file and condition code of the corresponding job. Explanation: It cannot be written to given file. System Action: Job is aborted. Operator Response: Check user/file. 3052: GIVEN FILE DOES NOT EXIST Written to: Log file and condition code of the corresponding job. Explanation: During file transfer with method GET it was detected that the file does not exist on the tracker. System Action: Job is aborted. Operator Response: Check user/file. 3000 – 3099 File Transfer Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 43 3053: GIVEN FILE ALREADY EXISTS Written to: Log file and condition code of the corresponding job. Explanation: During file transfer with method PUT it was detected that the file already exists on the tracker. System Action: Job is aborted. Operator Response: Check user/file. 3054: PERMISSION DENIED Written to: Log file and condition code of the corresponding job. Explanation: The user is not authorized to read the file (method GET) or to write to it (method PUT). System Action: Job is aborted. Operator Response: Check user/file. 3055: UNKNOWN ERROR Written to: Log file and condition code of the corresponding job. Explanation: An unknown error occurred during file transfer. System Action: Job is aborted. Operator Response: Check user/file/job. UNIX/Windows and SAP Messages 3000 – 3099 File Transfer Messages 44 Beta 48 V4.3 Messages and Codes January 30, 2009 3056: SYSTEM ERROR Written to: Log file and condition code of the corresponding job. Explanation: A system error has occurred. The message might come up when the size of the file to be transferred has exceeded 2 GB. System Action: The file transfer failed. Operator Response: Check the size of the file to be transferred and the log file. 3057: ERROR WHILE LOADING TRANSLATION TABLE Written to: Log file and condition code of the corresponding job. Explanation: The translation table specified in the ##FTPSTEP parameter TRANSTAB could not be found. System Action: The file transfer failed. Operator Response: Check the log file, the access rights, and the location of the translation table which has been used. 3058: CHMOD FAILED Written to: Log file and condition code of the corresponding job. Explanation: When the parameter CHMOD ends with an error, the job will end with errors. System Action: The job finished with errors. Operator Response: Check the definition of the parameter CHMOD. 3000 – 3099 File Transfer Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 45 3059: CHGRP OR CHOWN FAILED Written to: Log file and condition code of the corresponding job. Explanation: The message is issued when changing a group authorization (CHGRP) or changing a file owner (CHOWN) has failed. System Action: The job finished with errors. Operator Response: Check the authorization or the file owner definition. UNIX/Windows and SAP Messages 3100 – 3199 Event Triggering Messages 46 Beta 48 V4.3 Messages and Codes January 30, 2009 3100 – 3199 Event Triggering Messages 3100: FAIL EVENT TO TRIGGER NOT DEFINED IN EVENTSTEP Written to: Log file and condition code of the corresponding job. Explanation: No event has been triggered. System Action: The job finished normally. Operator Response: Check the definition of the event step EVENTSTEP. 3101: EVENT FILE DOES NOT EXIST, FAIL EVENT TRIGGERED Written to: Log file and condition code of the corresponding job. Explanation: The event defined in the event step EVENTSTEP as FAILEVT has been triggered. System Action: The job finished normally. Operator Response: Check whether the event has been defined. 3102: TRIGGER OKEVT FAILED Written to: Log file and condition code of the corresponding job. Explanation: No event has been triggered. System Action: The job finished normally. Operator Response: Check whether the event has been defined. Messages 3100 – 3199 Event Triggering Messages UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 47 3103: TRIGGER FAILEVT FAILED Written to: Log file and condition code of the corresponding job. Explanation: No event has been triggered. System Action: The job finished normally. Operator Response: Check whether the event has been defined. UNIX/Windows and SAP Messages 6200 – 9999 API Messages from the Agent 48 Beta 48 V4.3 Messages and Codes January 30, 2009 6200 – 9999 API Messages from the Agent 6201: NO HANDLE AVAILABLE Explanation: A file descriptor could not be initialized due to insufficient system resources. System Action: The system retries to initialize the file descriptor. Operator Response: None. 6202: NO MEMORY AVAILABLE Explanation: The program could not allocate any memory due to insufficient system resources. System Action: The system retries to allocate memory. Operator Response: Check the system memory. 6203: ERROR READING A FILE Explanation: A file could not be opened or read. System Action: The system retries the process. Operator Response: Check files and folders for their access rights. 6204: ERROR WRITING A FILE Explanation: A file could not be opened or written. System Action: The system retries the process. Operator Response: Check files and folders for their access rights. General messages 6200 – 9999 API Messages from the Agent UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 49 6205: CANNOT EXECUTE A BINARY Explanation: The program entered could not be executed. System Action: The system tries again to execute the program. Operator Response: Check the access (and execution) rights for the program. 6206: ERROR WHILE OPENING A FILE Explanation: A file could not be opened. System Action: The system tries again to open the file. Operator Response: Check files and folders for their access rights. 6207: NO RESOURCES TO CREATE A NEW PROCESS OR THREAD Explanation: The system resources are not enough to start a new process or thread. System Action: The system retries to start a new process or thread. Operator Response: Increase the system resources for the agent. We recommend that you distribute the necessary resources on several servers. 6208: LISTEN ON PORT FAILED Explanation: The program could not connect itself to a network card. System Action: The program terminates. Operator Response: Check whether the IP address (DNS name) and the port have been entered and whether the port is not already in use. UNIX/Windows and SAP Messages 6200 – 9999 API Messages from the Agent 50 Beta 48 V4.3 Messages and Codes January 30, 2009 6209: CANNOT OPEN PROCESS WITH OPEN_PROCESS (WINNT) Explanation: A new process could not be opened (only Windows NT). System Action: The system retries the process. Operator Response: None. 6210: NO PARAMETER FILE GIVEN IN THE COMMAND LINE. PROGRAM TERMINATES! Explanation: During program start the program expects a parameter file, but none has been entered. System Action: The system cannot be started. Operator Response: Enter the parameter file in the command line or in the start script. (The start script is automatically created during installation.) 6211: INCORRECT NUMBER OF CMDLINE PARAMETERS Explanation: The necessary command line parameters have not been entered while starting a program (internal error). System Action: The program terminates. Operator Response: None. 6212: INTERNAL LOOP ERROR DETECTED Explanation: An error occurred in a program loop. System Action: The program terminates. Operator Response: Restart the system. 6200 – 9999 API Messages from the Agent UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 51 6213: ERROR IN THE SELECT FUNCTION Explanation: An error occurred in the system function SELECT. System Action: The program terminates. Operator Response: Restart the system. 6214: ERROR WHILE ACCEPTING AN INCOMING CONNECTION Explanation: An error occurred in the system function ACCEPT. System Action: The system automatically retries to establish the connection. Operator Response: Check the system activities. 6215: WRONG FUNCTION PARAMETERS Explanation: A function was called with the wrong parameters (internal error). System Action: None. Operator Response: None. 6216: A PROCESS IS STILL ACTIVE Explanation: The checked process is still active. System Action: None. Operator Response: None. 6217: ERROR WHILE PROCESSING COMMANDLINE PARAMETERS Explanation: An error occurred while processing the command line parameters. System Action: None. Operator Response: None. UNIX/Windows and SAP Messages 6200 – 9999 API Messages from the Agent 52 Beta 48 V4.3 Messages and Codes January 30, 2009 6218: ERROR WHILE READING A FILE. AWAIT ANOTHER FILESIZE! Explanation: The file specified has the wrong file size. This is a critical error. System Action: The program terminates. Operator Response: Check the file system and, if necessary, contact Beta Systems Support. 6219: USER NOT FOUND Explanation: The user does not exist on the target system. System Action: Job failed. Operator Response: Check the user entries. 6220: LOGON FAILED Explanation: The user logon could not be successfully performed. System Action: The user is not logged on to the system. Operator Response: Check and reenter the password. 6221: ERROR WHILE RECEIVING DATA Explanation: An error occurred while data was being received via TCP/IP. System Action: The system retries the process. Operator Response: Check the IP connection between the Beta 48 STC and the agent, and vice versa. 6222: DEFINITION NOT PROPERLY SET Explanation: The definitions in the BQL database have not been entered correctly. System Action: The system waits for the correct definitions. Operator Response: Enter the definitions correctly and try again. 6200 – 9999 API Messages from the Agent UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 53 6223: LOGON TIMEOUT REACHED Explanation: The logon timeout has been exceeded while trying to logon to the system. System Action: The system tries to log on again. Operator Response: Check the target system. 6224: CANNOT LOAD THE TRANSLATION TABLE Explanation: While starting the program, the translation tables for ASCII – EBCDIC or EBCDIC – ASCII could not be loaded. System Action: The agent cannot be started. Operator Response: Copy the tables to the 'bin' folder of the Beta 48 agents. 6225: WRONG TRANSLATION TABLES FOUND Explanation: The translation tables that were found are corrupt. System Action: The agent cannot be started. Operator Response: Copy the tables to the 'bin' folder of the Beta 48 agents. 6226: ERROR WHILE SENDING DATA Explanation: Sending data via TCP/IP did not work. This is usually a temporary problem that the agent can handle in an appropriate way. The error is often caused by an instable network. System Action: The system retries the process. Operator Response: Check the IP connection. UNIX/Windows and SAP Messages 6200 – 9999 API Messages from the Agent 54 Beta 48 V4.3 Messages and Codes January 30, 2009 9000: CONNECT TO BETA 92 FAILED Explanation: The program could not find a connection to Beta 92 Enterprise on z/OS. System Action: The system retries. Operator Response: Check that Beta 92 is up and running. 9001: THE SPECIFIED FILE CANNOT BE SENT TO BETA 92 Explanation: The file could not be sent to Beta 92. System Action: The system retries. Operator Response: Check the file. Check that Beta 92 is up and running. 9050: CONNECTION TO BQL FAILED Explanation: An error occurred while trying to establish a connection to the BQL database. System Action: The system could not establish a connection to the BQL database. Operator Response: Check the IP connection. 9051: ERROR IN BQL COMMAND DETECTED Explanation: The BQL command ended in errors (internal program error). System Action: The system could not process the BQL command. Operator Response: Check the IP connection and the Beta 48 STC logs, then rerun the job. EDF Functions BQL communication functions 6200 – 9999 API Messages from the Agent UNIX/Windows and SAP Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 55 9052: BAD LICENSE OR INVALID TOKEN Explanation: The license file you are using is invalid or expired. You need a valid license file in order to be able to work with an agent. System Action: The agent cannot be started. Operator Response: Contact Beta Systems Order Desk (
[email protected]) and request a license file for Beta 48. UNIX/Windows and SAP Messages 6200 – 9999 API Messages from the Agent 56 Beta 48 V4.3 Messages and Codes January 30, 2009 Contents z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 57 z/OS Messages Contents Topic Page EJM5000x – EJM5399x Process Messages............................................58 EJM5400I – EJM5499I Monitor Messages ............................................92 EJM5500x – EJM5599x ETF Messages .................................................99 EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages.......105 In this chapter z/OS Messages EJM5000x – EJM5399x Process Messages 58 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5000x – EJM5399x Process Messages Process messages appear, when Beta 48 Extended Job Manager processes jobs and job status information. They are mainly produced by the B48SNAKE processes and the B48DARTH processes. A B48SNAKE process is created whenever a job arrives in Beta 48 Extended Job Manager. The B48SNAKE process receives the job, checks it, creates a database entry for this job and transfers the job to a tracker. A B48DARTH process is created whenever job status information is returned by a tracker. The B48DARTH process receives the job status information, checks it, updates the database and informs TWS, if required. The messages contain the following format: EJM5nnnx message (transaction ID) The message informs you about the stage of the process. The transaction ID refers to the z/OS transaction that routed the job or the job status information. 5nnn stands for the message number. x stands for the kind of messages, e. g. I for information, E for error, W for warning. EJM5000E B48IXLST UPDATE FOR keyword FAILED Written to: JESMSGLG. Explanation: The update of the LST parameter keyword in online option D.S.1 has failed. An invalid value has been entered. System Action: None. Operator Response: Enter a valid value and retry the update. Overview Messages EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 59 EJM5101I B48SNAKE - OPC/BATCH CLIENT ACTIVATED (transaction ID) Written to: JESMSGLG. Explanation: A B48SNAKE process has started to receive a job from TWS or JES. System Action: B48SNAKE registers the job's transaction ID, and then processes the job according to the instructions given in the header section. Operator Response: None. EJM5102I B48SNAKE - OPC/BATCH CLIENT FINISHED (transaction ID) Written to: JESMSGLG. Explanation: The B48SNAKE has terminated at the end of the job processing. System Action: None. Operator Response: None. EJM5103I B48DARTH - TCP/IP CLIENT ACTIVATED (transaction ID) Written to: JESMSGLG. Explanation: A B48DARTH process has been started to receive a job from the TCP/IP server. System Action: B48DARTH registers the job's transaction ID. Then, it tries to identify the job in the job selection database, and processes it accordingly. Operator Response: None. z/OS Messages EJM5000x – EJM5399x Process Messages 60 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5104I B48DARTH - TCP/IP CLIENT FINISHED (transaction ID) Written to: JESMSGLG. Explanation: The B48DARTH has terminated at the end of the job processing. System Action: None. Operator Response: None. EJM5107I JOB (jobname/jobid/b48jobid) IN PRE-PROCESSING STATUS EJM5108I JOB (jobname/jobid/b48jobid) SENT TO TRACKER EJM5109I JOB (jobname/jobid/b48jobid) RECEIVED FROM TRACKER EJM5110I JOB (jobname/jobid/b48jobid) STARTED (current status message) EJM5117I JOB (jobname/jobid/b48jobid) FINISHED (current status message) Written to: JESMSGLG/console. Explanation: The messages display the current job status. Each message starts with the name of the job, followed by the job ID, if necessary for a better explanation, the current status message is displayed as well. EJM5108I will only come up when the LST parameter B48_SNAKE_TRACE has been set to YES. EJM5109I will only come up when the LST parameter B48_DARTH_TRACE has been set to YES. System Action: None. Operator Response: None. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 61 EJM5111E JOB (jobname/jobid/b48jobid) FAILED AT START Written to: JESMSGLG. Explanation: The tracker cannot start the job on the SAP system or agent. System Action: None. Operator Response: Check the authorization of the user for the SAP system or the agent when this message appears. EJM5112E JOB (jobname/jobid/b48jobid) FAILED (current status message) Written to: JESMSGLG. Explanation: A syntax error occurred. System Action: None. Operator Response: Check the script. EJM5113E JOB (jobname/jobid/b48jobid) FAILED (USER NOT FOUND OR AUTHORIZED) Written to: JESMSGLG. Explanation: The user could not be found in the definition database or is not authorized to start the job. System Action: None. Operator Response: None. z/OS Messages EJM5000x – EJM5399x Process Messages 62 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5114E JOB (jobname/jobid/b48jobid) FAILED (NO CONNECTION FOUND) Written to: JESMSGLG. Explanation: A transmission error occurred between Beta 48 EJM and the tracker, SAP system, or agent. There is no connection to the SAP system or the agent in the Beta 48 database. Either the SAP system or the agent concerned is 'OFFLINE', all trackers of the system are 'OFFLINE', or no connections have been defined for this system. System Action: None. Operator Response: None. EJM5115E JOB (jobname/jobid/b48jobid) FAILED (NO CONNECTION TO ANY TRACKER) Written to: JESMSGLG. Explanation: A transmission error occurred between Beta 48 EJM and the tracker, SAP system, or agent. None of the trackers with access to the specified SAP system or agent has the status 'ONLINE.' None of the trackers defined are available. The TCP/IP connection may have been interrupted. System Action: None. Operator Response: None. EJM5116E JOB (jobname/jobid/b48jobid) FAILED (current status message) Written to: JESMSGLG. Explanation: Job was aborted on the SAP system or agent as a result of errors. System Action: None. Operator Response: None. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 63 EJM5118E JOB (jobname/jobid/b48jobid) FAILED (RECOVERY SET JOB FAILED) Written to: JESMSGLG. Explanation: While restarting the system a job with an undefined status (blank, I) has been set to 'failed.' System Action: None. Operator Response: None. EJM5118I JOB (jobname/jobid/b48jobid) FINISHED DUE TO HIGHCC highcc EJM5119I JOB (jobname/jobid/b48jobid) FINISHED DUE TO LST HIGHCC highcc EJM5120I JOB (jobname/jobid/b48jobid) FINISHED DUE TO NOERROR LISTLST Written to: JESMSGLG. Explanation: The message is issued when the respective job has been marked as a no error job (NOERROR). The following is the checking sequence for NOERROR jobs: • When the paramter HIGHCC has been coded in the job header ##HEADER, it will be used for NOERROR checking. When the job after the checking is still in error, it will be checked in the Beta 92 no error list (defined under the Beta 92 online option A.R.4). When the job after the checking is still in error, it will remain in error. • When the paramter HIGHCC has not been coded in the job header ##HEADER, the job is a TWS job and the LST parameter B48_ENABLE_UXGAP has been set to YES, the HIGHCC of B48UXGAP will be used for the checking. When the job after the checking is still in error, it will be checked in the Beta 92 no error list. When the job after the checking is still in error, it will remain in error. • When the paramter HIGHCC of B48UXGAP has not been coded, the HIGHCC entered in the LST parameter B48_DEFAULT_HIGHCC will be used. When the job after the checking is still in error, it will be checked in the Beta 92 no error list. When the job after the checking is still in error, it will remain in error. System Action: None. Operator Response: None. z/OS Messages EJM5000x – EJM5399x Process Messages 64 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5121I CALLED FROM OPC (transaction ID) Written to: JESMSGLG. Explanation: The B48SNAKE identifies TWS as the job's origin. System Action: None. Operator Response: None. EJM5122I CALLED FROM BATCH (transaction ID) Written to: JESMSGLG. Explanation: The B48SNAKE identifies JES as the batch job's origin. System Action: None. Operator Response: None. EJM5123I DATA RECEIVED (transaction ID) – DATA LENGTH(data lenth) Written to: JESMSGLG. Explanation: Either a B48SNAKE or a B48DARTH process prints out this message, after it has received data. System Action: None. Operator Response: None. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 65 EJM5124I EXTRACTED DATA (transaction ID) Written to: JESMSGLG. Explanation: Either a B48SNAKE or B48DARTH process prints out this message, before printing out the data it has received. For identification, the transaction ID of the respective job is also printed out. System Action: None. Operator Response: None. EJM5125I CONTENT OF UXOPC_PARM (transaction ID) Written to: JESMSGLG. Explanation: Either a B48SNAKE or a B48DARTH process prints out the UXOPC structure before it returns job status information to TWS. B48SNAKE returns job status information only if it cannot process the job. System Action: None. Operator Response: None. EJM5126I CALL UXPIP (transaction ID) Written to: JESMSGLG. Explanation: A B48SNAKE process calls the B48UXPIP module to extract information about CPIC users on the SAP system or agent from TWS. System Action: The B48SNAKE is waiting for a reply. Operator Response: None. z/OS Messages EJM5000x – EJM5399x Process Messages 66 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5127I UXPIP CALLED (transaction ID)- EXTRACTED USER 'user ID' Written to: JESMSGLG. Explanation: TWS has replied to a B48SNAKE process. System Action: None. Operator Response: None. EJM5128I CALL UXOPC (transaction ID) Written to: JESMSGLG. Explanation: Either a B48SNAKE or a B48DARTH process has called B48UXOPC, because the job status information changed. System Action: None. Operator Response: None. EJM5129I TRY TO CONNECT TO TRACKER (transaction ID) Written to: JESMSGLG. Explanation: A B48SNAKE or B48MONI process has tried to contact a tracker. System Action: None. Operator Response: None. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 67 EJM5130I NUMBER OF PARALLEL SNAKES HAS DECREASED - PROCESSING CONTINUES Written to: JESMSGLG. Explanation: The message is issued when the number of processes is again below 100 (see message EJM5230W) and processing can continue. System Action: Beta 48 continues processing the jobs in queue. Operator Response: None. EJM5133I BATCH PROCESSING ACTIVATED Written to: JESMSGLG of B48BCCOM. Explanation: The batch communicator has activated the batch mode. System Action: None. Operator Response: None. EJM5134I B48JOBID FOR THIS JOB IS (job ID) Written to: JESMSGLG of B48BCCOM. Explanation: This is the Beta 48 job ID of the running batch job. System Action: None. Operator Response: None. z/OS Messages EJM5000x – EJM5399x Process Messages 68 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5135I WAITING FOR END OF JOB Written to: JESMSGLG of B48BCCOM. Explanation: The batch communicator waits for the batch job to end. System Action: None. Operator Response: None. EJM5136I WAITING FOR END OF JOB NOT DESIRED Written to: JESMSGLG of B48BCCOM. Explanation: The batch communicator does not have to wait until the batch job has ended. System Action: None. Operator Response: None. EJM5137I CALLED FROM WIF (transaction ID) Written to: JESMSGLG. Explanation: The B48SNAKE identifies Beta 48/WIF as the batch job's origin. System Action: None. Operator Response: None. EJM5139I job status information Written to: DD statement EJMPRINT of a B48BCCOM job. Explanation: The message contains the job status information of a B48BCCOM job. System Action: None. Operator Response: None. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 69 EJM5140I B48PEGGY - JOB CANCEL CLIENT ACTIVATED Written to: JESMSGLG. Explanation: A B48PEGGY process has been started to send a cancel request for a job to Beta 48. System Action: None. Operator Response: None. EJM5141I B48PEGGY - JOB CANCEL CLIENT FINISHED Written to: JESMSGLG. Explanation: The B48PEGGY process has terminated at the end of the cancel processing. System Action: None. Operator Response: None. EJM5142I B48SIMON - EXTENDED JOB MONITORING CLIENT ACTIVATED Written to: JESMSGLG. Explanation: A B48SIMON process has been started to send a monitoring request for a job to Beta 48. System Action: None. Operator Response: None. z/OS Messages EJM5000x – EJM5399x Process Messages 70 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5143I B48SIMON - EXTENDED JOB MONITORING CLIENT FINISHED Written to: JESMSGLG. Explanation: The B48SIMON process has terminated at the end of the monitoring process. System Action: None. Operator Response: None. EJM5144I CANCEL REQUEST OF USER(user ID) FOR JOBID(b48jobID) SENT SUCCESSFULLY (transaction ID) Written to: JESMSGLG. Explanation: The B48SIMON process has terminated at the end of the monitoring process. System Action: None. Operator Response: None. EJM5146I USER(user ID) ATTEMPTS TO CANCEL JOBID (b48jobid) (transaction id) Written to: JESMSGLG. Explanation: The B48SIMON process has terminated at the end of the monitoring process. System Action: None. Operator Response: None. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 71 EJM5150E PROBLEM WITH JOB (job name/jobid/b48jobid), TRACKER=tracker Written to: JESMSGLG. Explanation: It has been tried to submit a job on a specific tracker but the TCP/IP connection from the Beta 48 started task to the tracker could not successfully be established. System Action: The job has not been submitted. Operator Response: Check the TCP/IP connection between the Beta 48 started task and the tracker. EJM5151E OPC COMM FAILED (exit name,RC=rc), JOB(jobname/jobid/ b48jobid) Written to: JESMSGLG. Explanation: The connection between the Beta 48 started task and TWS, formerly OPC, via the exit exit name could not be successfully established for the job job name. See the return code rc for more information. System Action: The system retries to establish the connection. Operator Response: None. EJM5201W SELECT JOBS FAILED (transaction ID) Written to: JESMSGLG. Explanation: A B48DARTH process has not found an entry for the job in the job select database. System Action: A new entry is inserted. Operator Response: None. z/OS Messages EJM5000x – EJM5399x Process Messages 72 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5202W SELECT SAPS FAILED (transaction ID) Written to: JESMSGLG. Explanation: A B48DARTH process received a job from a tracker. The B48DARTH process has not found the job's SAP or UNIX/Windows system in the definition database. System Action: The SAP or UNIX/Windows system's ASHOST name and SYSNR are inserted into the status field. Operator Response: We recommend that you predefine the SAP or UNIX/Windows system. EJM5203W UNKNOWN COMMAND (transaction ID) Written to: JESMSGLG. Explanation: A B48SNAKE process has found an unknown command in the content of a job's SYSIN card. System Action: The job may terminate. Operator Response: Check the content of the job's SYSIN card. EJM5230W MAXIMUM NUMBER OF PARALLEL SNAKE PROCESSES REACHED - WAITING Written to: JESMSGLG. Explanation: Too many processes, i.e. more than 100, have been started in Beta 48. System Action: Beta 48 is waiting until one or several processes could be terminated and the number of processes is again below 100. Operator Response: Decrease the number of processes. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 73 EJM5301E READING TRACE FLAG FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager did not recognize one of the following trace parameters in the B48LSTnn: B48_TCPIP_TRACE, B48_MONI_TRACE, B48_SNAKE_TRACE or B48_DARTH_TRACE. System Action: Beta 48 Extended Job Manager cannot start. Operator Response: Check whether all of the above listed parameters exist in the B48LSTnn. In case they exist, check whether the parameter values are correct. EJM5302E READING TCPIP STC NAME FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager did not recognize the B48_TCPIP_STC parameter in the B48LSTnn. System Action: Beta 48 Extended Job Manager cannot start. Operator Response: Check whether the B48_TCPIP_STC parameter exists in the B48LSTnn. In case it exists, check whether the parameter value is correct. EJM5303E READING TCPIP PORT FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager did not recognize the B48_TCPIP_PORT parameter in the B48LSTnn. System Action: Beta 48 Extended Job Manager cannot start. Operator Response: Check whether the B48_TCPIP_PORT parameter exists in the B48LSTnn. In case it exists, check whether the parameter value is correct. z/OS Messages EJM5000x – EJM5399x Process Messages 74 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5304E READING TCPIP ADDR FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager did not recognize the TCPIP_IPADDR parameter in the B48LSTnn. System Action: Beta 48 Extended Job Manager cannot start. Operator Response: Check whether the TCPIP_IPADDR parameter exists in the B48LSTnn. In case it exists, check whether the parameter value is correct. EJM5305E READING UXPIP FLAG FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager did not recognize the B48_ENABLE_UXPIP parameter in the B48LSTnn. System Action: Beta 48 Extended Job Manager cannot start. Operator Response: Check whether the B48_ENABLE_UXPIP parameter exists in the B48LSTnn. In case it exists, check whether the parameter value is correct. EJM5306E SYSIN CANNOT BE OPENED Written to: JESMSGLG. Explanation: The B48BCCOM module cannot read either the content or the file given in a batch job's SYSIN card. System Action: The batch job terminates with return code 8. Operator Response: Check whether the batch job's SYSIN card is correct. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 75 EJM5308E SUBSYSTEM UNAVAILABLE (subsystem ID) Written to: JESMSGLG. Explanation: The subsystem in the B48_SSID parameter in the B48LSTnn is not available. System Action: Beta 48 Extended Job Manager does not exist. Operator Response: Check whether the subsystem exists. In case it exists, check whether it is unavailable due to the z/OS system. EJM5320E OPEN PONLOP ERROR (transaction ID) Written to: JESMSGLG. Explanation: Internal BQL error. System Action: Beta 48 Extended Job Manager cannot receive or submit any batch jobs. Operator Response: Check the status of the database to find out the cause of the error. EJM5321E SELECT SOR FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager cannot access the SOR table to select data. System Action: Beta 48 Extended Job Manager cannot receive or submit any batch jobs. Operator Response: Check the status of the database to find out the cause of the error. z/OS Messages EJM5000x – EJM5399x Process Messages 76 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5322E UPDATE SOR FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager cannot access the SOR table to update data. System Action: Beta 48 Extended Job Manager cannot receive or submit any batch jobs. Operator Response: Check the status of the database to find out the cause of the error. EJM5323E SELECT JOBS FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager cannot access the JOBS table to select data. System Action: Beta 48 Extended Job Manager cannot receive or submit any batch jobs. Operator Response: Check the status of the database to find out the cause of the error. EJM5324E INSERT JOBS FAILED RC=(return code number) (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager cannot access the JOBS table to insert data. System Action: Beta 48 Extended Job Manager cannot receive or submit any batch jobs. Operator Response: Check the status of the database to find out the cause of the error. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 77 EJM5325E UPDATE JOBS FAILED (transaction ID) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager cannot access the JOBS table to update data. System Action: Beta 48 Extended Job Manager cannot receive or submit any batch jobs. Operator Response: Check the status of the database to find out the cause of the error. EJM5326E SELECT SAPS FAILED (transaction ID) Written to: JESMSGLG. Explanation: A B48SNAKE or a B48DARTH process cannot access the SAP or agent table to select data. System Action: The respective batch job cannot be submitted, and therefore, terminates. Operator Response: Check the status of the database to find out the cause of the error. EJM5327E SELECT USER FAILED (transaction ID) Written to: JESMSGLG. Explanation: A B48SNAKE process cannot access the USER table to select data. System Action: The respective batch job cannot be submitted, and therefore, terminates. Operator Response: Check the status of the database to find out the cause of the error. z/OS Messages EJM5000x – EJM5399x Process Messages 78 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5332E NO TRACKERS DEFINED (transaction ID) Written to: JESMSGLG. Explanation: The definition database does not contain any definition of trackers. System Action: Beta 48 Extended Job Manager cannot submit any jobs. Operator Response: Add the definitions of the trackers and add connections. EJM5333E SELECT CONNECTION FAILED (transaction ID) Written to: JESMSGLG. Explanation: A B48SNAKE process cannot access the CONNECT table to select data. System Action: B48SNAKE cannot submit the respective job. Operator Response: Check the status of the database to find out the cause of the error. EJM5334E NO CONNECTION TO ANY TRACKER (transaction ID) Written to: JESMSGLG. Explanation: Either no connection is defined in the definition database, or all trackers defined are unavailable. Either all trackers are inactive, or the TCP/IP connection is interrupted. System Action: The incoming batch jobs are terminated with an error code. If all trackers are unavailable and if the B48_MONI_ON parameter is set to YES in the B48LSTnn, the respective TWS workstations are also set offline. Operator Response: If no connection exists, define the connections. If all trackers are unavailable, check whether the TCP/IP connection is interrupted. In case it is active, check whether the trackers are inactive. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 79 EJM5335E ERROR IN SENDING TO TRACKER (transaction ID) Written to: JESMSGLG. Explanation: A TCP/IP error occurred while a B48SNAKE process was transferring a job to a tracker. System Action: The job terminates. Operator Response: Check whether the TCP/IP connection is interrupted. If it still exists, check whether the respective tracker is still active. EJM5336E NO OPC TRACKER SSID DEFINED (transaction ID) Written to: JESMSGLG. Explanation: The message comes up when a TWS job has been processed and the job status is to be returned to TWS in order to update the job information but in Beta 48, option S.1 a TWS tracker and/or an alternative TWS tracker have not been defined beforehand and therefore a connection to TWS could not be established. System Action: The job receives the status 'X' (which means TWS communication error) and the status messages 'OPC CONNECT ERROR' is displayed in the 'External Job Selection' panel. The job status in TWS is not updated. Operator Response: Define the respective trackers in option S.1. EJM5337E SELECT SCRIPT FAILED RC=(return code number)(transaction ID) Written to: JESMSGLG. Explanation: This message comes up when Beta 48 (program B48SNAKE) is to process a job but cannot find a script for this job in the database. System Action: The job receives the status '-' (which means job failed, script error). Return code 4027 and the status messages 'NO SCRIPT FOUND' are displayed in the 'External Job Selection' panel. Operator Response: Check whether a script is available for the job. z/OS Messages EJM5000x – EJM5399x Process Messages 80 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5338E CALCULATION OF NEW JOBID FAILED RC=(return code) (transaction ID) Written to: JESMSGLG. Explanation: The message comes up when a job ID could not be assigned to a job. The job ID is used to uniquely identify a job. System Action: The job processing is terminated. Operator Response: Contact your local Beta Systems representative. EJM5339E WQE LENGTH LESS THAN OPJOB_PARM LENGTH=length (transaction ID) Written to: JESMSGLG. Explanation: The message comes up when a WQE has an unexpected length. System Action: The job processing is terminated. Operator Response: Contact your local Beta Systems representative. EJM5340E TRACKER RECEIVES INCOMPLETE DATA (JOB: jobname) Written to: JESMSGLG. Explanation: A TCP/IP error occurred while a B48SNAKE or B48PEGGY process was transferring a job/a cancel request for a job to a tracker. System Action: The job terminates / the cancel request fails. Operator Response: Check whether the TCP/IP connection is interrupted. If it still exists, check whether the respective tracker is still active. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 81 EJM5341E MISSING DD STATEMENTS FOR EJF SPOOL Written to: JESMSGLG. Explanation: Too few SPOOLxxx DD statements have been entered in the job. Beta 48 has transferred more files into the Beta 48 database than could be read by B48BCCOM. System Action: Job ends with an error. Operator Response: Check the job and change it if necessary. EJM5342E MISSING SPOOL FILES FROM EJF Written to: JESMSGLG. Explanation: Too many SPOOLxxx DD statements have been entered in the job. Beta 48 has transferred too few files into the Beta 48 database. System Action: Job ends with an error. Operator Response: Check the job and change it if necessary. EJM5350E GOT ILLEGAL FUNCTION CODE function code number EJM5350E command length command data Written to: JESMSGLG. Explanation: The message comes up when an error occurred. command data - a text up to 80 bytes is displayed System Action: Processing continues. Operator Response: Contact your local Beta Systems representative. z/OS Messages EJM5000x – EJM5399x Process Messages 82 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5360E SELECT TRACKER FAILED rc=bql return code (transaction id) Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager cannot access the TRACKER table to select data. System Action: Beta 48 Extended Job Manager cannot receive or submit any batch jobs, cancel requests or monitoring requests. Operator Response: Check the status of the database to find out the cause of the error. EJM5361E TRACKER IS NOT ONLINE (TRACKNAM=tracker name) (transaction id) Written to: JESMSGLG. Explanation: The message comes up when Beta 48 is to process a cancel or monitoring request but the tracker for the respective job is offline. System Action: The cancel/monitoring request fails. Operator Response: Check the status of the tracker. EJM5362E TRACKER TCPIP ADDRESS IS NOT AVAILABLE (TRACKNAM=tracker name) (transaction id) Written to: JESMSGLG. Explanation: The message comes up when Beta 48 is to process a cancel or monitoring request but the TCP/IP address for this tracker is not available in the database. System Action: The cancel/monitoring request fails. Operator Response: Check the definition of the tracker in the database. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 83 EJM5363E TCPIP INIT FAILED (TRACKNAM=tracker name) (transaction id) Written to: JESMSGLG. Explanation: The message comes up when Beta 48 is to process a cancel or monitoring request but the TCP/IP connection to the tracker cannot be established. System Action: The cancel/monitoring request fails. Operator Response: Check whether the TCP/IP connection is interrupted. If it still exists, check whether the respective tracker is still active. EJM5364E TCPIP CONNECT FAILED (TRACKNAM=tracker name) (transaction id) Written to: JESMSGLG. Explanation: The message comes up when Beta 48 is to process a cancel or monitoring request but the TCP/IP connection to the tracker cannot be established. System Action: The cancel/monitoring request fails. Operator Response: Check whether the TCP/IP connection is interrupted. If it still exists, check whether the respective tracker is still active. EJM5365E USER IS NOT AUTHORIZED TO CANCEL JOBID (b48jobid) (transaction id) Written to: JESMSGLG. Explanation: The user who tried to cancel the job is not authorized. System Action: The cancel request fails. Operator Response: Only users who are authorized to start the job are also allowed to cancel it. z/OS Messages EJM5000x – EJM5399x Process Messages 84 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5366E JOB CANNOT BE CANCELED BECAUSE ITS STATUS IS status Written to: JESMSGLG. Explanation: The job that is to be canceled has a status that cannot be canceled. System Action: The cancel request fails. Operator Response: Check the current status of the job. Only jobs with status /, \, Y, S, P and R can be canceled. EJM5367E RECEIVE FAILED (JOB: b48jobid) Written to: JESMSGLG. Explanation: A TCP/IP error occurred while Beta 48 was transferring a cancel request or a monitoring request to a tracker. System Action: The cancel/monitoring request fails. Operator Response: Check whether the TCP/IP connection is interrupted. If it still exists, check whether the respective tracker is still active. EJM5368E CONFIRM TO TRACKER FAILED (JOB: b48jobid) Written to: JESMSGLG. Explanation: A TCP/IP error occurred while Beta 48 was transferring a cancel request or a monitoring request to a tracker. System Action: The cancel/monitoring request fails. Operator Response: Check whether the TCP/IP connection is interrupted. If it still exists, check whether the respective tracker is still active. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 85 EJM5369E TRACKER RECEIVES INVALID DATA (JOB: b48jobid) Written to: JESMSGLG. Explanation: A TCP/IP error occurred while Beta 48 was transferring a cancel request or a monitoring request to a tracker. System Action: The cancel/monitoring request fails. Operator Response: Check whether the TCP/IP connection is interrupted. If it still exists, check whether the respective tracker is still active. EJM5370E USER IS NOT AUTHORIZED TO REQUEST STATUS FOR JOBID Written to: JESMSGLG. Explanation: The user who tried to monitor the job is not authorized. System Action: The monitoring request fails. Operator Response: Only users who are authorized to start the job are also allowed to monitor it. EJM5371E JOB MONITORING NOT AVAILABLE FOR THIS JOB BECAUSE ITS STATUS IS status Written to: JESMSGLG. Explanation: The job that is to be monitored has a status for which monitoring is not available. System Action: The monitoring request fails. Operator Response: Check the current status of the job. Only jobs with status /, \, Y, S, P and R can be monitored. z/OS Messages EJM5000x – EJM5399x Process Messages 86 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5372E NO LICENSE AVAILABLE FOR SAP BASIS version Written to: JESMSGLG. Explanation: Your SAP release in use is not supported by Beta 48 (currently: versions higher than 710). System Action: The SAP request fails. Operator Response: Use a supported SAP release. EJM5372E JCH LICENSE INVALID OR MISSING Written to: JESMSGLG. Explanation: The Beta 48 SAP license JCH for the BW-SCH interface is invalid or missing. System Action: The SAP request fails. Operator Response: Contact Beta Systems Order Desk (
[email protected]) and request the Beta 48 SAP license JCH for the BW-SCH interface. EJM5372E SV0 LICENSE INVALID OR MISSING Written to: JESMSGLG. Explanation: The Beta 48 SAP license SV0 for the SAP basic component lower than and equal to (<=) version 700 is invalid or missing. System Action: The SAP request fails. Operator Response: Contact Beta Systems Order Desk (
[email protected]) and request the Beta 48 SAP license SV0. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 87 EJM5372E SV1 LICENSE INVALID OR MISSING Written to: JESMSGLG. Explanation: The Beta 48 SAP license SV1 for the SAP basic component lower than and equal to (<=) version 710 is invalid or missing. System Action: The SAP request fails. Operator Response: Contact Beta Systems Order Desk (
[email protected]) and request the Beta 48 SAP license SV1. EJM5380I NOERROR PROCESSING SUCCESSFULLY ENABLED Written to: JESMSGLG. Explanation: The message is issued when the STC is started, B48_NOERROR_PROCESSING=YES has been coded and the Beta 92 no error list could successfully be read. System Action: None. Operator Response: None. EJM5381I NOERROR LIST SUCCESSFULLY REFRESHED Written to: JESMSGLG. Explanation: The message is issued when the no error list has been refreshed by an operator console command, B48_NOERROR_PROCESSING=YES has been coded and the Beta 92 no error list could successfully be read. For information on the no error list refresh command, see the section "Using Beta 48 z/OS Operator Console Commands" in the manual Beta 48 Installation and System Guide. System Action: None. Operator Response: None. z/OS Messages EJM5000x – EJM5399x Process Messages 88 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5382I NOERROR PROCESSING FOR JOBNAME MASK job name mask Written to: JESMSGLG. Explanation: The message is issued along with the message EJM5380I or EJM5381I when the Beta 48 STC is started or the no error list refresh command has been entered. A list is shown containing the job name masks for which the no error processing is executed. For information on the no error list refresh command, see the section "Using Beta 48 z/OS Operator Console Commands" in the manual Beta 48 Installation and System Guide. System Action: None. Operator Response: None. EJM5383E CANNOT READ NOERROR LIST, B92SSID NOT SPECIFIED Written to: JESMSGLG. Explanation: The message is issued when the LST parameter B48_NOERROR_PROCESSING has been set to YES but the Beta 92 subsystem ID has not been defined under the Beta 48 online option S.1 in the field Beta 92 SSID. System Action: The no error list (defined under the Beta 92 online option A.R.4) could not be read. Operator Response: Define the Beta 92 subsystem ID (SSID) under the Beta 48 option S.1. EJM5384E CANNOT READ NOERROR LIST, VERSION MISMATCH (RC=rc,IRC=irc) Written to: JESMSGLG. Explanation: The message is issued when the LST parameter B48_NOERROR_PROCESSING has been set to YES but the defined Beta 92 subsystem is not a Beta 92 V4.3 system. System Action: The no error list (defined under the Beta 92 online option A.R.4) could not be read. Operator Response: Define a Beta 92 V4.3 subsystem ID (SSID) under option S.1. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 89 EJM5385E CANNOT READ NOERROR LIST FROM SSID b92ssid, WAITING… Written to: JESMSGLG. Explanation: When the Beta 48 STC is started, the no error list could not be read under the defined Beta 92 SSID because, e. g., the Beta 92 STC has not been started. The Beta 48 STC is waiting up to 10 minutes and retries to read the list every minute. System Action: The no error list (defined under the Beta 92 online option A.R.4) could not be read. Operator Response: Start the Beta 92 STC. EJM5386E CANNOT READ NOERROR LIST FROM SSID b92ssid, SHUTDOWN Written to: JESMSGLG. Explanation: After 10 unsuccessful attempts in a 1-minute interval to read the Beta 92 no error list under the defined Beta 92 subsystem ID, the start of the Beta 48 STC has been canceled. Before the start of the Beta 48 STC will be canceled, the message EJM5385E has been issued for nine times. System Action: The Beta 48 STC has not been started. Operator Response: Check whether the Beta 92 STC has been started or correct the defined Beta 92 subsystem ID under the Beta 48 online option S.1 in the field Beta 92 SSID. z/OS Messages EJM5000x – EJM5399x Process Messages 90 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5387E NOERROR PROCESSING DISABLED, REFRESH FAILED Written to: JESMSGLG. Explanation: The message is issued when the no error list refresh command has been entered but the LST parameter B48_NOERROR_PROCESSING is set to NO. For information on the no error list refresh command, see the section "Using Beta 48 z/OS Operator Console Commands" in the manual Beta 48 Installation and System Guide. System Action: No error processing is not available. Operator Response: Set the LST parameter B48_NOERROR_PROCESSING to YES and restart the Beta 48 STC. EJM5388E CANNOT READ NOERROR LIST FROM SSID b92ssid, CONNECT FAILED Written to: JESMSGLG. Explanation: The message is issued when the no error list refresh command has been entered and the LST parameter B48_NOERROR_PROCESSING is set to YES but the Beta 92 subsystem is not accessible. For information on the no error list refresh command, see the section "Using Beta 48 z/OS Operator Console Commands" in the manual Beta 48 Installation and System Guide. System Action: No error processing is not available and the defined Beta 92 subsystem cannot be found. Operator Response: Start the Beta 48 STC. EJM5000x – EJM5399x Process Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 91 EJM5389E REFRESH NOERROR LIST FAILED, USING ALREADY LOADED LIST Written to: JESMSGLG. Explanation: The message is issued when the no error list refresh command has been entered and the LST parameter B48_NOERROR_PROCESSING is set to YES but the refresh command could not be successfully completed. System Action: The no error list could not be refreshed. Operator Response: Retry to enter the modify command. For information on the no error list refresh command, see the section "Using Beta 48 z/OS Operator Console Commands" in the manual Beta 48 Installation and System Guide. z/OS Messages EJM5400I – EJM5499I Monitor Messages 92 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5400I – EJM5499I Monitor Messages Monitor messages appear, when Beta 48 Extended Job Manager is enabled to manage TWS workstations automatically. The messages are produced by the B48MONI process. The messages contain the following format: EJM5nnnI message (transaction ID) The message informs you about the stage of the monitoring process. It may contain additional tokens such as a tracker name. The transaction ID refers to the z/OS transaction that performed the monitoring action. 5nnn stands for the message number. EJM5401I B48MONI - MONITORING ACTIVATED Written to: JESMSGLG. Explanation: The B48MONI monitor module has started. System Action: None. Operator Response: None. EJM5402I B48MONI - MONITORING TERMINATED Written to: JESMSGLG. Explanation: The B48MONI monitor module has terminated. System Action: None. Operator Response: None. Overview Messages EJM5400I – EJM5499I Monitor Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 93 EJM5404I WORKSTATION (OPC workstation) IS SET TO (ONLINE/OFFLINE) Written to: JESMSGLG. Explanation: The B48MONI sets the displayed TWS workstation to the status OFFLINE or ACTIVE, depending on the availability of the trackers connected to the TWS workstation. The informational message comes up when the Beta 48 STC is in the start up or shutdown process. It informs you about what Beta 48 is processing. When the Beta 48 STC is running and the status of the trackers and TWS workstation are changed, the warning message EJM5404W will come up. System Action: None. Operator Response: None. EJM5404W WORKSTATION (OPC workstation) IS SET TO (ONLINE/OFFLINE) Written to: JESMSGLG. Explanation: The B48MONI has set the displayed TWS workstation to the status OFFLINE or ACTIVE, depending on the availability of the trackers connected to the TWS workstation. The warning message comes up when the status of the trackers and the TWS workstations connected to the tracker are altered while the Beta 48 STC is running. System Action: None. Operator Response: None. EJM5405I BQL RC=(return code) (transaction ID) Written to: JESMSGLG. Explanation: The B48MONI has either inserted or updated a TWS workstation or its connections. It receives this return code from the related BQL request. System Action: None. Operator Response: None. z/OS Messages EJM5400I – EJM5499I Monitor Messages 94 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5406I SEARCHING FOR TRACKER --- (tracker name) --- Written to: JESMSGLG. Explanation: The B48MONI tries to contact the specified tracker. System Action: None. Operator Response: None. EJM5407I TRACKER (tracker name) DIED Written to: JESMSGLG. Explanation: The B48MONI could not contact the specified tracker. System Action: Depending on the availability of other connected trackers, B48MONI may set the connected TWS workstations offline. Operator Response: None. EJM5408I TRACKER (tracker name) AWAKEN Written to: JESMSGLG. Explanation: The B48MONI has contacted this tracker. Thus, it is confirmed that the tracker is active. System Action: If any connected TWS workstation is offline, B48MONI sets it to active. Operator Response: None. EJM5400I – EJM5499I Monitor Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 95 EJM5409W TRACKER/ROUTER (tracker/router) IS DOWN Written to: JESMSGLG. Explanation: The specified router or tracker cannot be reached. The tracker is set to OFFLINE. System Action: None. Operator Response: None. EJM5410I TRACKER/ROUTER (tracker/router) IS SWITCHED Written to: JESMSGLG. Explanation: The currently active router cannot be reached. An alternative router has been located and the current routing will be handled by this tracker/router. System Action: None. Operator Response: None. EJM5411I SYSTEM (system name) DIED Written to: JESMSGLG. Explanation: The B48MONI could not contact the specified SAP system. System Action: Depending on the availability of other connected SAP systems, B48MONI may set the connected TWS workstations offline. Operator Response: None. z/OS Messages EJM5400I – EJM5499I Monitor Messages 96 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5412I SYSTEM (system name) AWAKEN Written to: JESMSGLG. Explanation: The B48MONI has contacted this SAP system. Thus, it is confirmed that the SAP system is active. System Action: If any connected TWS workstation is offline, B48MONI sets it to active. Operator Response: None. EJM5413I SEARCHING FOR SAP SYSTEM --- (SAP system name) --- Written to: JESMSGLG. Explanation: The B48MONI tries to contact the specified SAP system. System Action: None. Operator Response: None. EJM5470I MONIPAUSE: (value) Written to: JESMSGLG. Explanation: B48MONI prints out the value of the B48_MONI_PAUSE parameter in the B48LSTnn. System Action: None. Operator Response: None. EJM5400I – EJM5499I Monitor Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 97 EJM5471I MONITRACE: (value) Written to: JESMSGLG. Explanation: B48MONI prints out the value of the B48_MONI_TRACE parameter in the B48LSTnn. System Action: None. Operator Response: None. EJM5472I MONION: (value) Written to: JESMSGLG. Explanation: B48MONI prints out the value of the B48_MONI_ON parameter in the B48LSTnn. System Action: None. Operator Response: None. EJM5473I MONIUSEOPC: (value) Written to: JESMSGLG. Explanation: B48MONI prints out the value of the B48_MONI_USEOPC parameter in the B48LSTnn. System Action: None. Operator Response: None. z/OS Messages EJM5400I – EJM5499I Monitor Messages 98 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5481I MONI IS SLEEPING (number of seconds) SECONDS Written to: JESMSGLG. Explanation: The B48MONI process enters the time interval set in the B48_MONI_ON parameter. System Action: None. Operator Response: None. EJM5482I MONI IS GOING DOWN (transaction ID) Written to: JESMSGLG. Explanation: The B48MONI process is in the middle of a shut down. System Action: None. Operator Response: Do not cancel the system. EJM5500x – EJM5599x ETF Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 99 EJM5500x – EJM5599x ETF Messages EJM5500I B48ETF - ETF CLIENT ACTIVATED Written to: JESMSGLG. Explanation: A Beta 48 ETF transaction has been started to receive events from Open Systems. System Action: The system tries to submit the incoming event. Operator Response: None. EJM5501I B48ETF - ETF CLIENT FINISHED Written to: JESMSGLG. Explanation: A Beta 48 ETF transaction has been terminated. System Action: None. Operator Response: None. EJM5502E ETF LICENSE INVALID OR MISSING Written to: JESMSGLG. Explanation: The license file does not contain the Beta 48 add-on Extended Triggering Facility (ETF). System Action: The event has not been submitted. Operator Response: Contact Beta Systems Order Desk (
[email protected]) and request a license file for Beta 48 ETF. Messages z/OS Messages EJM5500x – EJM5599x ETF Messages 100 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5503E SELECT ETFSTAT FAILED Written to: JESMSGLG. Explanation: An internal selection error has occurred (in the table ETFSTAT). System Action: The event has not been submitted. Operator Response: Check the JES message log (JESMSGLG) and the log file of the tracker. EJM5504E UPDATE ETFSTAT FAILED Written to: JESMSGLG. Explanation: An internal update error has occurred (in the table ETFSTAT). System Action: The event has not been submitted. Operator Response: Check the JES message log (JESMSGLG) and the log file of the tracker. EJM5505E SELECT ETFDEF FAILED Written to: JESMSGLG. Explanation: An internal selection error has occurred (in the table ETFDEF). The return code 5002 'NOT AUTHORIZED BECAUSE NO MATCHING EVENT MASK DEFINITION FOUND' comes up when an event has been selected under Beta 48 z/OS online option 3 and the above error occurred. System Action: The event has not been submitted. Operator Response: Check the user access rights, the security function code in use, and the event mask defined under Beta 48 z/OS online option 2.7. For more information also see the Beta 48 Extended Triggering Facility (ETF) Manual. EJM5500x – EJM5599x ETF Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 101 EJM5507E DDNAME B48JLIB NOT FOUND Written to: JESMSGLG. Explanation: An event job is to be submitted but the DD name of the Beta 48 job library could not be found in the Beta 48 started task procedure. The return code 5005 "DDNAME B48JLIB NOT FOUND" comes up when an event has been selected under Beta 48 z/OS online option 3 and the job library has not been concatenated in the Beta 48 started task procedure beforehand. System Action: The event has not been submitted. Operator Response: Define the DD name of the Beta 48 job library in the Beta 48 started task procedure. EJM5508E MEMBER member name NOT FOUND RC=rc Written to: JESMSGLG. Explanation: An event job is to be submitted but the specified member could not be found in the Beta 48 job library. The return code 5007 "MEMBER NOT FOUND" comes up when an event has been selected under Beta 48 z/OS online option 3 and the member could not be found in the Beta 48 job library. System Action: The event has not been submitted. Operator Response: Specify the member in the Beta 48 job library. z/OS Messages EJM5500x – EJM5599x ETF Messages 102 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5509E ALLOCATION OF C list FAILED RC=rc Written to: JESMSGLG. Explanation: An event job is to be submitted but the specified member could not be allocated. The return code 5008 'ALLOCATION OF MEMBER IN B48JLIB FAILED' comes up when an event has been selected under Beta 48 z/OS online option 3 and the member allocation failed. System Action: The event has not been submitted. Operator Response: Check the JES message log (JESMSGLG) and the user access rights. EJM5510E MEMBER C list COULD NOT BE OPENED Written to: JESMSGLG. Explanation: An event job is to be submitted but the specified member could not be opened. The return code 5009 'MEMBER COULD NOT BE OPENED' comes up when an event has been selected under Beta 48 z/OS online option 3 and the member could not be opened. System Action: The event has not been submitted. Operator Response: Check the JES message log (JESMSGLG) and the user access rights. EJM5511E B48ETF COULD NOT ALLOCATE ENOUGH MEMORY FOR JOB BUFFER Written to: JESMSGLG. Explanation: An event job is to be submitted but not enough memory could be allocated for the job load. The return code 5010 'ALLOCATION FAILED: NOT ENOUGH MEMORY FOR JOB BUFFER' comes up when an event has been selected under Beta 48 z/OS online option 3 and no sufficient memory is available. System Action: The event has not been submitted. Operator Response: Increase the system memory used for the Beta 48 stated task. EJM5500x – EJM5599x ETF Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 103 EJM5512E PARAMETER name MISSING Written to: JESMSGLG. Explanation: An event job is to be submitted but JCL parameters have been defined in the job which have not been used while submitting the event. The return code 5011 'PARAMETER <name> MISSING' comes up when an event has been selected under Beta 48 z/OS online option 3 and not all of the parameters have been specified. System Action: The event has not been submitted. Operator Response: Check the call up of the ./b48etf command line program and correct the JCL. EJM5513E PARAMETER name IS NEVER REFERENCED IN THE JCL Written to: JESMSGLG. Explanation: A job event is to be submitted but more parameters have been found than defined in the job JCL beforehand. The return code 5013 'PARAMETER <name> NEVER REFERENCED IN JCL' comes up when an event has been selected under Beta 48 z/OS online option 3 and not all of the parameters have been specified. System Action: The event has not been submitted. Operator Response: Check the call of the ./b48etf command line program and/or the job JCL. EJM5514E INVALID JCL STATEMENT FOUND Written to: JESMSGLG. Explanation: A job event is to be submitted but an invalid parameter has been found. The return code 5012 'INVALID JCL STATEMENT FOUND (LINE <line> TOO LONG)' comes up when an event has been selected under Beta 48 z/OS online option 3 and parameters have not been correctly specified. System Action: The event has not been submitted. Operator Response: Check the JCL of the corresponding job. z/OS Messages EJM5500x – EJM5599x ETF Messages 104 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5515E INTRDR COULD NOT BE OPENED Written to: JESMSGLG. Explanation: A job event is to be submitted but the JCL could not be transferred to JES via the internal reader. The return code 8 'EVENT FAILED BECAUSE OPEN FOR INTRDR FAILED' comes up when an event has been selected under Beta 48 z/OS online option 3 and the internal reader could not be opened. System Action: The event has not been submitted. Operator Response: Check the JES message log (JESMSGLG) and the system log. EJM5550I EVENT (event name/event ID/event type) IN PRE-PROCESSING STATUS Written to: JESMSGLG. Explanation: The event event name is waiting to be submitted. System Action: The system tries to submit the event. Operator Response: None. EJM5551I EVENT (event name/event ID/event type) SUBMITTED Written to: JESMSGLG. Explanation: The event event name has been successfully submitted. System Action: None. Operator Response: None. EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 105 EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages The following messages are produced by the B48JODEL, B48STDEL, and B48ETDEL batch utilities. The messages contain the following format: EJM5nnnx message (transaction ID) The message informs you about the stage of the job cleaning, statistics or event process. It may contain additional tokens such as the retention period. The transaction ID refers to the z/OS transaction that performed the cleanup action. 5nnn stands for the message number. x stands for the kind of message, e. g. I for information, E for error etc. EJM5701I B48JODEL – CLEANUP PROCESS IS STARTING (transaction ID) Written to: JESMSGLG. Explanation: A Beta 48 cleanup process (B48JODEL) has been started. System Action: None. Operator Response: None. EJM5702I B48JODEL – CLEANUP PROCESS ENDS (transaction ID) Written to: JESMSGLG. Explanation: The B48JODEL batch utility has terminated. System Action: None. Operator Response: None. Overview Messages z/OS Messages EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages 106 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5703I JOB RETENTION PERIOD IS (retention period) DAYS Written to: EJMPRINT. Explanation: B48JODEL prints out the retention period. The retention period is determined by the DAYS parameter in the job card. System Action: None. Operator Response: None. EJM5704I ALL JOBS OLDER THAN (retention period) ARE DELETED Written to: JESMSGLG. Explanation: The B48JODEL has deleted all expired jobs. System Action: None. Operator Response: None. EJM5705I (number of jobs) JOBS DELETED Written to: ELMPRINT. Explanation: The B48JODEL prints out the number of jobs that it has deleted. System Action: None. Operator Response: None. EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 107 EJM5706I B48ETDEL/B48STDEL/B48JODEL - VERSION (version) PTFLEVEL (PTF level) Written to: EJMPRINT. Explanation: B48ETDEL, B48STDEL & B48JODEL print out its version and PTF level. System Action: None. Operator Response: None. EJM5707I TYPE: ANALYZE Written to: JESMSGLG. Explanation: B48ETDEL, B48STDEL, and B48JODEL print out the value ANALYZE of the TYPE parameter in the job card. System Action: None. Operator Response: None. EJM5708I DAYS: (value) Written to: JESMSGLG. Explanation: B48ETDEL, B48STDEL, and B48JODEL print out the value of the DAYS parameter in the job card. System Action: None. Operator Response: None. z/OS Messages EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages 108 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5709I NOPRINT: (value) Written to: JESMSGLG. Explanation: B48ETDEL, B48STDEL, and B48JODEL print out the value of the NOPRINT parameter in the job card. System Action: None. Operator Response: None. EJM5710I SSID: (value) Written to: JESMSGLG. Explanation: B48ETDEL, B48STDEL, and B48JODEL print out the subsystem ID of Beta 48 Extended Job Manager. System Action: None. Operator Response: None. EJM5711I USER: (value) Written to: JESMSGLG. Explanation: B48ETDEL, B48STDEL, and B48JODEL print out the user ID of the user that started the respective batch utility. System Action: None. Operator Response: None. EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 109 EJM5730I STATISTICS CLEANUP PROCESS STARTED Written to: JESMSGLG. Explanation: A Beta 48 cleanup process (B48STDEL) has been started. System Action: None. Operator Response: None. EJM5731I STATISTICS CLEANUP PROCESS ENDED Written to: JESMSGLG. Explanation: The B48STDEL batch utility has terminated. System Action: None. Operator Response: None. EJM5732I STATISTICS RETENTION PERIOD IS (retention period) DAYS Written to: EJMPRINT. Explanation: B48STDEL prints out the retention period. The retention period is determined by the DAYS parameter in the job card. System Action: None. Operator Response: None. z/OS Messages EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages 110 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5733I ALL STATISTICS RECORDS OLDER THAN (retention period) WILL BE SELECTED FOR DELETION Written to: JESMSGLG. Explanation: The B48STDEL is going to delete all of the selected statistics records. System Action: None. EJM5734I (number of records) STATISTICS RECORDS (are/would be) DELETED Written to: ELMPRINT. Explanation: The B48STDEL prints out the number of jobs that it has deleted or would have been deleted (analyze mode). System Action: None. Operator Response: None. EJM5735I ALL STATISTICS RECORDS OLDER THAN (retention period) ARE DELETED Written to: JESMSGLG. Explanation: The B48STDEL has deleted all expired jobs. System Action: None. EJM5750I EVENT CLEANUP PROCESS STARTED Written to: JESMSGLG. Explanation: An event cleanup process (B48ETDEL batch utility) has been started. System Action: None. Operator Response: None. EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 111 EJM5751I EVENT CLEANUP PROCESS ENDED Written to: JESMSGLG. Explanation: An event cleanup process (B48ETDEL batch utility) has terminated. System Action: None. Operator Response: None. EJM5752I EVENT RETENTION PERIOD IS (retention period) DAYS Written to: EJMPRINT. Explanation: B48ETDEL prints out the retention period. The retention period is determined by the DAYS parameter in the job card. System Action: None. Operator Response: None. EJM5753I ALL EVENTS OLDER THAN (retention period) WILL BE SELECTED FOR DELETION Written to: JESMSGLG. Explanation: The B48ETDEL will delete all of the selected events. System Action: None. Operator Response: None. z/OS Messages EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages 112 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5754I (number of events) EVENTS (are/would be) DELETED Written to: ELMPRINT. Explanation: The B48ETDEL prints out the number of jobs that it has deleted or would have been deleted (analyze mode). System Action: None. Operator Response: None. EJM5755I ALL EVENTS OLDER THAN (retention period) ARE DELETED Written to: JESMSGLG. Explanation: The B48STDEL, B48JODEL, or B48ETDEL job has deleted all old data. System Action: None. Operator Response: None. EJM5901E USER NOT AUTHORIZED Written to: JESMSGLG. Explanation: The user that started B48JODEL, B48STDEL, or B48ETDEL is not authorized to access the job select database. System Action: B48JODEL, B48STDEL, or B48ETDEL terminates. Operator Response: Check the RACF profile of the user. EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 113 EJM5902E BQL ERROR Written to: JESMSGLG. Explanation: Internal BQL error. System Action: Beta 48 Extended Job Manager cannot clean any job status, event, or statistics information. Operator Response: Check the status of the respective database to find out the cause of the error. EJM5903E BETA48 STC NOT AVAILABLE Written to: JESMSGLG. Explanation: Beta 48 Extended Job Manager is not active. System Action: B48JODEL, B48STDEL, or B48ETDEL terminates. Operator Response: Start the Beta 48 started task and rerun B48JODEL, B48STDEL, or B48ETDEL. EJM5904E UNKNOWN RETURN CODE RECEIVED Written to: JESMSGLG. Explanation: An unknown return code occurred. Beta 48 Extended Job Manager has not been properly installed. System Action: B48JODEL, B48STDEL, or B48ETDEL terminates. Operator Response: Contact Beta Systems support. Please read the Appendix 'Calling for Support' first. z/OS Messages EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages 114 Beta 48 V4.3 Messages and Codes January 30, 2009 EJM5905E NO JOBS FOUND Written to: JESMSGLG. Explanation: B48JODEL did not find any jobs to delete. System Action: B48JODEL terminates. Operator Response: None. EJM5906E NO EVENTS FOUND Written to: JESMSGLG. Explanation: B48ETDEL did not find any jobs to delete. System Action: B48ETDEL terminates. Operator Response: None. EJM5907E PARAMETER 'DAY=' MISSING Written to: JESMSGLG. Explanation: B48JODEL, B48STDEL, or B48ETDEL could not find the parameter 'DAY='. System Action: B48JODEL, B48ETDEL, or B48STDEL terminates. Operator Response: Enter the parameter 'DAY=' in the job JCL and restart the job. EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages z/OS Messages January 30, 2009 Beta 48 V4.3 Messages and Codes 115 EJM5908E VALUE OF PARAMETER (parameter) INVALID Written to: JESMSGLG. Explanation: A wrong parameter value has been entered for B48JODEL, B48STDEL, or B48ETDEL. System Action: B48JODEL, B48ETDEL, or B48STDEL terminates. Operator Response: Correct the respective parameter in the job JCL and restart the job. EJM5909E NO STATISTICS RECORDS FOUND Written to: JESMSGLG. Explanation: B48STDEL did not find any jobs to delete. System Action: B48STDEL terminates. Operator Response: None. z/OS Messages EJM5700x – EJM5999x Cleanup, Statistics, and Event Messages 116 Beta 48 V4.3 Messages and Codes January 30, 2009 RC 0 – 2999 Job and Event Information Return Codes January 30, 2009 Beta 48 V4.3 Messages and Codes 117 Return Codes RC 0 – 2999 Job and Event Information The External Job Selection Table contains all levels of the processing status found by the selection panel. To display the External Job Selection Table do the following: • In the Primary Selection Menu, select Option 1 - JOB SELECT, enter the selection criteria in the panel displayed, and press ENTER. The External Job Selection Table is displayed. If an error has occurred, the column S shows the status -. The column RC shows an error number, and the column Status Message an error message is displayed. The following tables include the return codes which are displayed in the column RC, as well as the corresponding error messages which appear in the column Status Message. RC Status Message Description 0 JOB IS FINISHED ON system The job was finished successfully. 1 JOB FAILED ON system The return code is issued when the job could not be started on the Windows target system. 4 Job Start Failed ON system In SAP no sessions can be found for Batch Input Maps with the criteria specified within the job. 8 JOB FAILED ON system At least one Batch Input Map terminated with errors. 8 JOB FAILED ON system If an SAP job is canceled while running, a message appears in the SAP system and in the job. 8 JOB FAILED ON system To find out any inconsistencies in the agent version from the z/OS system, the program version can be used in a B48BCCOM job. In case of an error, the job will end with the return code 8 which means that inconsistencies between the agent modules have occurred. Information in the External Job Selection Table Errors Error messages and return codes (RC) Return Codes RC 0 – 2999 Job and Event Information 118 Beta 48 V4.3 Messages and Codes January 30, 2009 RC Status Message Description 8 EVENT FAILED BECAUSE ALLOC FOR INTRDR FAILED When you are a Beta 48 Extended Triggering Facility (ETF) user, the return code may come up for the event type "JOB" with this error message. The allocation of the internal reader failed due to capacity load of the processor. 8 EVENT FAILED BECAUSE OPEN FOR INTRDR FAILED When you are a Beta 48 Extended Triggering Facility (ETF) user, the return code may come up for the event type "JOB" with this error message. The internal reader could not be opened due to capacity load of the processor. 16 ETF LICENSE INVALID OR MISSING The license entered for Beta 48 Extended Triggering Facility (ETF) is invalid or expired. 24 COULD NOT CONNECT TO started task The connection to the Beta 48 started task (STC) could not be established or is terminated. 127 JOB FAILED ON system The return code is issued when the job could not be started on the UNIX/Windows target system. 201 LOGIN FAILED The user logon could not be successfully performed. 222 JOB IS CANCELED ON system The return code comes up when the job has been canceled. 1000-2322 JOB START FAILED ON system The return code is issued when the job could not be started on the SAP target system. 2323 INVALID TARGET The return code is issued when the job is using a target server group which does not exist. 2324-2399 JOB START FAILED ON system The return code is issued when the job could not be started on the SAP target system. RC 0 – 2999 Job and Event Information Return Codes January 30, 2009 Beta 48 V4.3 Messages and Codes 119 RC Status Message Description 2400-2599 JOB START FAILED ON system The return code is issued from a function module when the job could not be started on the SAP target system. The job could not be started on the SAP target system because the parameters were not available for the job run. 2700 JOB FAILED ON system The return code comes up when the job execution has failed. 2701 RC OUT OF RANGE The return code is issued from a UNIX/Windows script when the returned code is higher than 4095 or lower than -127. Return Codes RC 3000 – 3099 File Transfer Errors 120 Beta 48 V4.3 Messages and Codes January 30, 2009 RC 3000 – 3099 File Transfer Errors The following return codes may occur while transferring a file or dataset to Beta 48 or Beta 92. The return codes 3000 – 3018 may appear on the z/OS system, the return codes 3050 – 3059 may appear on UNIX or Windows systems. RC Error occurred on Status Message / Description 3000 z/OS system Syntax error occurred. 3001 z/OS system User not defined in RACF. 3002 z/OS system No RACF resource defined for given dataset. 3003 z/OS system User cannot read from the given dataset. 3004 z/OS system User cannot write to the given dataset. 3005 z/OS system Member does not exist in given dataset. 3006 z/OS system Member does already exist in given dataset. 3007 z/OS system Cannot allocate dataset. 3008 z/OS system Cannot open dataset. 3009 z/OS system Binary transmission failed for fixed block dataset. 3010 z/OS system Line too long. 3011 z/OS system Error while writing. 3012 z/OS system Error while reading. 3013 z/OS system Bad dataset organization. 3014 z/OS system STC cannot read from the given dataset. 3015 z/OS system STC cannot write to the given dataset. 3016 z/OS system Not enough space. 3017 z/OS system Unknown error while sending file to tracker. 3018 z/OS system Unknown error while receiving file from tracker. 3050 UNIX/Windows Cannot read from given file. 3051 UNIX/Windows Cannot write to given file. 3052 UNIX/Windows Given file does not exist. Overview RC 3000 – 3099 File Transfer Errors Return Codes January 30, 2009 Beta 48 V4.3 Messages and Codes 121 RC Error occurred on Status Message / Description 3053 UNIX/Windows Given file already exists. 3054 UNIX/Windows Permission denied. 3055 UNIX/Windows Unknown error. 3056 UNIX/Windows System error. 3057 UNIX/Windows Cannot load the translation table. 3058 UNIX When the parameter CHMOD ends with an error, the job will end with RC 3058. 3059 UNIX CHGRP or CHOWN failed. / When the parameter CHOWN or CHGRP ends with an error, the job will end with RC 3059. The error is issued when changing a group authorization (CHGRP) or changing a file owner (CHOWN) has failed. Return Codes RC 3100 – 3199 Event Triggering Errors 122 Beta 48 V4.3 Messages and Codes January 30, 2009 RC 3100 – 3199 Event Triggering Errors The following return codes may occur while triggering events. The return codes 3100 – 3199 may appear on UNIX or Windows systems. RC Error occurred on Status Message / Description 3100 UNIX/Windows Event file does not exist / Check the existence and size of the event file and the event definition. 3101 UNIX/Windows Event file does not exist, fail event triggered / The event file does not exist or the file size is too small. A fail event has been triggered. 3102 UNIX/Windows Trigger OKEVT failed / An OKEVT event could not be triggered. Check whether the event has been defined. 3103 UNIX/Windows Trigger FAILEVT failed / A FAILEVT event could not be triggered. Check whether the event has been defined. Overview RC 4000 – 4999 Processing and Transmission Errors Return Codes January 30, 2009 Beta 48 V4.3 Messages and Codes 123 RC 4000 – 4999 Processing and Transmission Errors Error numbers 4000 to 4069 indicate processing errors in Beta 48 EJM. If a syntax error has occurred, the line number concerned will appear in the error message. Error message - LINE nn Error numbers 4070 to 4074 indicate that a transmission error has occurred between Beta 48 EJM and the tracker, SAP system, or agent. If a transmission error has occurred, check whether the tracker is available (line command T). If it is, check whether the definitions (alias, connections, user) are correct. This table includes the return codes which are displayed in the column RC, as well as the corresponding status messages which appear in the column Status Message. RC Status Message Description 4000 SCRIPT NOT FOUND An internal communication error occurred. The entire script could not be found. 4001 SYNTAX ERROR. LINE <line> The job contains a syntax error in line line. 4002 ##HEADER-STATEMENT MISSING ##HEADER marks the start of the data header. Such a mark is missing. 4003 INVALID ##END-STATEMENT An invalid ##END statement was found. 4004 STEPS NEED ##END-MARK ##END marks the end of a step. Such a mark is missing. Use it only once in each step. 4005 NO STEPS FOUND The job does not contain any step. Define at least one step. 4006 NO STEPS ALLOWED If parameters, such as JOBCOUNT=, CHAIN=, SESSION=, FICAPARM, INFOPACK and DIJNAME are used for SAP jobs, no job steps, such as ##ABAPSTEP or ##EXTSTEP, are allowed. 4007 ENTER ONLY ONE ##END More than one ##END mark has been detected. Beta 48 EJM processing errors Transmission errors Error messages and return codes (RC) Return Codes RC 4000 – 4999 Processing and Transmission Errors 124 Beta 48 V4.3 Messages and Codes January 30, 2009 RC Status Message Description 4008 parameter OUTSIDE OF ##HEADER The parameter parameter is only valid in the section indicated by the message (e.g. ##HEADER or ##ABAPSTEP). 4009 JOB HAS NO STEPS The job script contains no processing steps. 4010 parameter INVALID FOR SAP or parameter INVALID FOR AGENT The parameter parameter cannot be used for SAP jobs, only for UNIX/Windows jobs or vice versa. 4011 parameter MISSING OR EMPTY The parameter parameter has not been defined in its designated section. 4012 SET ONLY ONE parameter The parameter parameter appears more than once in its section. It can be defined only once. 4013 parameter1 NEEDS parameter2 Parameter parameter1 can only be defined in combination with parameter parameter2. Specify parameter2 also in your script. 4014 SET BOTH parameter1 AND parameter2 The parameters parameter1 and parameter2 require one another. 4015 DO NOT COMBINE parameter1 + parameter2 The parameters parameter1 and parameter2 cannot be entered at the same time. 4016 INVALID COMBINATION OF parameter1 AND parameter2 The parameter parameter1 contains a value that cannot be combined with the value in parameter parameter2. 4017 DO NOT DEFINE FTPSTEP + EXTSTEP IN SAME JOB ##FTPSTEP and ##EXTSTEP are not allowed to be specified within the same job. 4018 parameter TOO LONG - line <line> The value entered in the line concerned is longer than allowed. 4019 parameter CAN BE (value1, value2,…) The parameter parameter may only contain one of the following values: value1, value2, …. 4020 FORMAT FOR parameter IS (format) The value in parameter parameter must comply with the format indicated inside the brackets. 4021 FBID NOT CONNECTED TO SYSID The SAP system connection of the function module specified by the function module ID (FBID) has not yet been defined under option 2.6 Function Modules. RC 4000 – 4999 Processing and Transmission Errors Return Codes January 30, 2009 Beta 48 V4.3 Messages and Codes 125 RC Status Message Description 4070 SYSID IS WRONG The system alias specified does not appear in the definitions database (option 2.1 and 2.2). 4071 USER NOT FOUND OR AUTHORIZED The user could not be found in the definitions database (option 2.4), or is not authorized to start the job. 4073 NO CONNECTION FOUND There is no connection to the SAP system/agent in the Beta 48 database. Either the SAP system or agent concerned is OFFLINE, or all trackers for the system are OFFLINE, or no connections have been defined for this system (under option 2.5). 4074 NO CONNECTION TO ANY TRACKER None of the trackers with access to the SAP system or agent (defined under option 2.5) has the status ONLINE. None of the trackers defined are available. The TCP/IP connection may have been interrupted. 4095 INVALID LICENSE An invalid license has been found. Contact Beta Systems Order Desk (
[email protected]) and request a license file for Beta 48. 4100 RESTART=YES NEEDS LOGID= When RESTART=YES is coded, a log ID must have been entered. 4101 DO NOT COMBINE RESTART=NO AND LOGID= or DO NOT COMBINE RESTART=NO AND ONLYRED= When RESTART=NO is coded, a log ID cannot be processed. or When RESTART=NO is coded, the parameter ONLYRED cannot be processed. Return Codes RC 5000 – 5999 Event Submission Errors 126 Beta 48 V4.3 Messages and Codes January 30, 2009 RC 5000 – 5999 Event Submission Errors Events that cannot be started or submitted will return an error code. Displayed in the 'Event Selection' table are the selected events. The table includes the event types, the return codes displayed in the column RC, as well as the corresponding error or status messages appearing in the column Status Message. Event types can be: • JOB for all batch jobs • TSR for TWS SRSTAT events or • ALL for JOB and TSR events The following table lists all the error codes that may appear when errors occur to submitted events: Type RC Status Message Description JOB 8 EVENT FAILED BECAUSE ALLOC FOR INTRDR FAILED The allocation of the internal reader failed due to capacity load of the processor on the z/OS system. JOB 8 EVENT FAILED BECAUSE OPEN FOR INTRDR FAILED The internal reader could not be opened due to capacity load of the processor on the z/OS system. SAP 8 SAP EVENT FAILED The SAP event could not be triggered due to an error, e.g. the event does not exist. ALL 5000 TRACKER NOT FOUND OR NOT CONNECTED TO ANY EJF AGENT The tracker on which the event is submitted cannot be found in the Beta 48 database (Beta 48 z/OS option 2.3), or the tracker has not been connected to an agent (Beta 48 z/OS option 2.5). ALL 5001 USER NOT FOUND FOR THE SPECIFIED TRACKER The user submitting the event, e.g. an SAP user, could not be found in the Beta 48 database (Beta 48 z/OS option 2.4) or the tracker has not been connected to an agent (Beta 48 z/OS option 2.5). ALL 5002 NOT AUTHORIZED BECAUSE NO MATCHING EVENT MASK DEFINITION FOUND The event submission has been rejected because no matching event mask definition has been found (Beta 48 z/OS option 2.7). TSR 5003 SYSTEM OPTION RECORD NOT FOUND The system option record (SOR) cannot be selected. Event types, return codes (RC) and error messages RC 8 and 5000 – 5999 RC 5000 – 5999 Event Submission Errors Return Codes January 30, 2009 Beta 48 V4.3 Messages and Codes 127 Type RC Status Message Description TSR 5004 TWS TRACKER SSID NOT FOUND IN SYSTEM OPTION RECORD The TWS tracker SSID has not been entered. JOB 5005 DDNAME B48JLIB NOT FOUND The DDNAME B48JLIB has not been defined in the Beta 48 started task procedure – a prerequisite for the execution of job events. JOB 5006 B48JLIB COULD NOT BE OPENED The B48JLIB could not be opened. JOB 5007 MEMBER NOT FOUND The member entered for the job event could not be found in the B48JLIB. JOB 5008 ALLOCATION OF MEMBER IN B48JLIB FAILED The member entered for the job event could not be allocated. JOB 5009 MEMBER COULD NOT BE OPENED The member entered for the job event could not be opened. JOB 5010 ALLOCATION FAILED: NOT ENOUGH MEMORY FOR JOB BUFFER Insufficient memory for submission of the job event. JOB 5011 PARAMETER <parameter> MISSING The parameter <parameter> has not yet been specified. JOB 5012 INVALID JCL STATEMENT FOUND (LINE <line> TOO LONG) The line <line> entered in the JCL is much too long. JOB 5013 PARAMETER <parameter> NEVER REFERENCED IN JCL The parameter <parameter> has been entered in a command line of the program ./b48etf but the parameter has not yet been specified in the corresponding JLIB member. Return Codes RC 5000 – 5999 Event Submission Errors 128 Beta 48 V4.3 Messages and Codes January 30, 2009 Messages and Codes Appendix: Calling for Support January 30, 2009 Beta 48 V4.3 Messages and Codes 129 Appendix: Calling for Support Contents Topic Page Overview.................................................................................................130 General Questions about Your Software Environment ..........................130 Questions about the Nature of the Error ................................................130 Batch Jobs..............................................................................................131 Online Functions.....................................................................................131 Started Task ...........................................................................................132 Displaying Active Tasks..........................................................................132 Providing Additional Information.............................................................133 Sending a Dump.....................................................................................135 Sending Your Databases .......................................................................137 Checklist before Calling for Support.......................................................138 In this chapter Appendix: Calling for Support Messages and Codes 130 Beta 48 V4.3 Messages and Codes January 30, 2009 Overview If you encounter a problem with a Beta product which you feel unable to solve on your own, you can call your local Beta Systems representative or the Beta Systems hotline for assistance. You can help Beta Systems to determine the source of your problem more quickly if you have all relevant information at hand before you call for support. In the following descriptions, BETAnn stands for the name of the respective Beta product started task. For BETAnn substitute the name of your started task. In the hardcopy of this manual, you will find a form at the end of this section in which you can enter some of the required information. It is helpful to also send a filled in copy of this form if you send additional information to Beta Systems, e.g. a dump. General Questions about Your Software Environment • In which Beta product did the error occur? • Which release and PTF level of this product are installed at your site? Has the Beta product environment changed lately (e.g. have any PTFs or APARs been applied, database names changed)? • Which z/OS, JES, ISPF, RACF, VTAM, CICS, version do you use? Do you use JES2 or JES3? Which UNIX or Windows NT version do you use? Have there been any changes in any of these products lately? • Is it possible that any other software products might be involved in producing the error? Please note the installed releases of all other possibly involved products. Questions about the Nature of the Error • in a batch function? • in an online function? • under TSO, VTAM, CICS, IMS? • Beta nn started task or VTAM Dialog Facility started task? • Do the started task, the TSO users and all batch jobs use the same Beta load libraries? • Is the SVC correct? The Beta user SVC has to be copied to your system LPALIB and an IPL with CLPA has to be performed before any changes in the SVC are activated. You must also make sure that all parmlib members used by the Beta nn started tasks and batch jobs point to the correct SVC. Did the error occur: Batch Jobs Appendix: Calling for Support January 30, 2009 Beta 48 V4.3 Messages and Codes 131 Batch Jobs If the error occurred in a batch job, you should have the following information at hand: • the job log, • the SYSLOG, • if a dump was written, the dump (core dump or Dr. Watson dump). SFF dumps contain an ABEND descriptor block (ADB) which provides information on register contents at the time of the ABEND and the involved modules. See the section 'Printing the ABEND Descriptor Block' for details. Online Functions If the error occurred in an online function, you should have the following information at hand: • Is the error reproducible? • Which online function was performed at the time of the error? • In which panel (panel ID) did the error occur? Enter the command PANELID in the command line to display the panel ID. • Which messages (long messages) were displayed in the panel? • Does the error occur under any special circumstances (e.g. was the started task stopped shortly before the error occurred)? • Do the online user and the started task use the same load libraries? • Is the program loaded from • z/OS linklist? • STEPLIB? • LIBDEF service? Appendix: Calling for Support Messages and Codes 132 Beta 48 V4.3 Messages and Codes January 30, 2009 Started Task If the error occurred in a started task, you should have the following information at hand: • the started task protocol, • the SYSLOG, • Was a dump written? SFF dumps contain an ABEND descriptor block (ADB) which provides information on register contents at the time of the ABEND and the involved modules. See the section 'Printing the ABEND Descriptor Block' for details. • What were the accompanying circumstances at the time the error occurred? For example, how many online Beta product users were there? Were there any batch jobs running against the subsystem? Displaying Active Tasks If a batch job or started task do not seem to be running anymore, you can use some operator console commands to determine any active functions: – F BETAnn,TL shows active functions. – F BETAnn,ST shows SFF operating statistics. – F jobname,TL shows active batch functions. For BETAnn, enter the name of your started task, for jobname the batch job name. After you enter any of the above commands, a table with the respective information is displayed on the operator console. It is helpful if the corresponding part of the SYSLOG is available when you call. Providing Additional Information Appendix: Calling for Support January 30, 2009 Beta 48 V4.3 Messages and Codes 133 Providing Additional Information This section helps you to provide additional information about your problem for the Beta Systems support. It is easier for us to trace the error when you send us the short trace. Set LOGLEVEL=4, start a rerun and send us the following files from the logs-directory: • Log file • Error file The short trace is written in the SFF dump when you insert the SFFTRACE DD card in the started task procedure and the batch jobs. In order to find the trace table, browse the SFF dump with the command 'F TRACE 1'. The following lines contain the short trace contents. The trace table spans more than one page. It is recommended that you deactivate the short trace after taking the dump. The short trace is switched off by removing the SFFTRACE DD card from the JCL. If an SFF dump was produced, print out all ABEND descriptor blocks (ADB). SFF dumps contain at least one ADB which gives information on register contents at the time of the ABEND and the involved modules. In order to find the ADB, browse the SFFFDUMP with the command 'F ABEND 1'. The following lines contain the register contents at the time of the ABEND and at the last call of the Subsystem Function Facility. It is sufficient to print out only this page. If you browse the dump using SDSF or another program which displays control characters in the first position, the string 'ABEND' has to be searched on position 2 instead of 1. Overview Trace Information Note Printing the ABEND Descriptor Block Note Appendix: Calling for Support Messages and Codes 134 Beta 48 V4.3 Messages and Codes January 30, 2009 If an ABEND occurs under TSO in an online function, usually no dump is written. In order to trace the error, it is nevertheless useful to receive a TSO dump. The following steps must be followed in order to get a TSO dump: 1. Enter the following TSO command: ALLOC FI(SYSUDUMP) SYSOUT(x) For x substitute the SYSOUT class to which the dump should be written. 2. Activate the ISPF TEST option. To do this, select ISPF option 7 and quit the option again with PF3. 3. Select the Beta product where the error occurred and perform the same functions that led to the ABEND. 4. When the option TEST is activated, you do not receive the ISPF Primary Selection menu after the ABEND, but go into in the READY mode. 5. Press ENTER to start the writing of the dump. z/OS dumps are only written when a SYSUDUMP DD statement is inserted in the batch job or started task JCL. We recommend suppressing the processing of the dump by Abend Aid by inserting the DD statement //ABNLIGNR DD DUMMY in the JCL. TSO Dumps z/OS Dumps Sending a Dump Appendix: Calling for Support January 30, 2009 Beta 48 V4.3 Messages and Codes 135 Sending a Dump If it becomes necessary that you send a dump to determine the source of the problem, there are a few things that you can do to facilitate the analysis: • send the dump on tape or cassette and not on paper. • send us the job log of the job with which the dump was copied to tape/cassette along with the dump. • A short description of the dump should be sent containing • a short description of the problem, • the dataset name, • the type of dump (z/OS,SFF, SVC), • how it was copied (e.g. IEBGENER, XWTR, OFFLOAD) • if available, the corresponding Beta Info Reference number. • Multiple dumps should be copied to multiple files on the tape/cassette. • We recommend that you use a SYSOUT class processed by Beta 93 or Beta 92 on the SFFFDUMP DD statement in the started task procedure and the batch utilities. If it is a Beta 92 SYSOUT class, you can use the B92PRINT batch utility to copy the dump to tape or cassette (see JCL example below). • In the case of Beta 93, you can choose a distribution characteristic of the type CLIST to copy the dump to a dataset (see Beta 93 User's Guide). • You can unload a dump to tape or cassette directly from the JES spool with OFFLOAD only if you use JES2. • An SVC dump has to be formatted first with IPCS. Please print the CSA, SQA, LSQA, log records, trace table and private storage, too, when you format the dump. Call IPCS option 3 (SUBMIT) and then option 2 (SVC DUMP). Appendix: Calling for Support Messages and Codes 136 Beta 48 V4.3 Messages and Codes January 30, 2009 Please do not use any other data compression but standard Improved Data Recording Capability (IDRC). Please do not send dumps taken with Abend Aid. The dump processing with Abend Aid can be suppressed by inserting the DD statement: //ABNLIGNR DD DUMMY • in the started task or batch job JCL. We recommend the following DCB specifications for a dump: RECFM=VBM LRECL=137 BLKSIZE=32760 This example shows the writing of a dump to cassette using the Beta 92 batch utility B92PRINT: +-----------------------------------------------------------------------+ |//jobcard | |//BATPRT EXEC PGM=BST01RFF,REGION=4096K,PARM='PGM=B92PRINT' | | ... | | ... | |//SYSUT2 DD DSN=dsname,VOL=SER=xxxxxx,UNIT=CASS,DISP=(NEW,KEEP) | |// DCB=(BLKSIZE=32760,LRECL=137,RECFM=VBM), | |// LABEL=(1,SL,EXPDT=98000) | |//SYSIN DD * | |* PRINT DUMP BETA 92 | | SDATE(TODAY) | | PDATE(TODAY) | | JOBNAME(BETA92) | | JOBID(STCxxxx) | |/* | +-----------------------------------------------------------------------+ This example shows how a dump in a JES HOLD class is written to a dataset with a TSO command: OUTPUT stcname(jesid) PRINT('dsname') HOLD KEEP The dataset has to be already allocated. Otherwise a small default dataset is used. Note Example 1 - B92PRINT Example 2 - Dump JES HOLD Class Sending Your Databases Appendix: Calling for Support January 30, 2009 Beta 48 V4.3 Messages and Codes 137 A dump in a NOHOLD class can be written to tape/cassette with an external writer. +------------------------------------------------------------------------+ |//XWTR PROC | |//* | |//* TO READ ALL SYSOUT=M OUTPUT TO A SEQUENTIAL FILE (BETA.DUMP) | |//* | |//* S XWTR,,,M M=SYSOUTCLASS | |//* 222 WRITER WAITING FOR WORK | |//* P 222 | |//* | |//IEFPROC EXEC PGM=IASXWR00,REGION=4M,PARM='PA' | |//* | |//IEFRDER DD DISP=SHR,DSN=BETA.DUMP, | |// DCB=(BLKSIZE=23476,LRECL=137,BUFL=23476,BUFNO=2,RECFM=VBM)| | | | or | | | |//IEFRDER DD DISP=(NEW,KEEP),DSN=BETA.DUMP,UNIT=CASS,LABEL=(1,SL), | |// DCB=(BLKSIZE=32760,LRECL=137,BUFL=32760,BUFNO=2,RECFM=VBM)| +------------------------------------------------------------------------+ Sending Your Databases If you have any problem in your product databases, it might be of value to send a copy of the affected databases to Beta Systems. In this case, the databases should be copied to tape/cassette with an IDCAMS REPRO. The protocol of the IDCAMS REPRO should be sent along with the tape. Before you copy your databases to tape, the started task should be stopped to prevent inconsistencies between the copied files. Example 3 - Dump NOHOLD Class Appendix: Calling for Support Messages and Codes 138 Beta 48 V4.3 Messages and Codes January 30, 2009 Checklist before Calling for Support Beta product: ______________________________ PTF level: _____________________ Release: ______________________________ OS version: ______________________________ JES version (JES2 or JES3?): ___________________ z/OS version: _________________ ISPF version: ________________________________ RACF version: __________________ Other software versions: Online functions: Batch/STC functions: Which function (online option): _________________ Job log available: YES / NO Panel ID: ___________________________________ SYSLOG available: YES / NO Program name: ______________________________ TL command entered: YES / NO Program/PTF level: ___________________________ ST command entered: YES / NO Date/time: __________________________________ Error reproducible: YES / NO Checklist before Calling for Support Appendix: Calling for Support January 30, 2009 Beta 48 V4.3 Messages and Codes 139 Dump information: Problem description: __________________________ ___________________________________________ Info Ref. No.: ________________________________ Type (z/OS/SFF/SVC): ______________________ Info Ref. No.: ________________________________ Type (UNIX/Windows NT): _____________________ How was it copied (job log): _________________ Appendix: Calling for Support Messages and Codes 140 Beta 48 V4.3 Messages and Codes January 30, 2009 Comments and Suggestions January 30, 2009 Beta 48 V4.3 Messages and Codes Comments and Suggestions Please help us to provide better documentation by filling out this evaluation sheet. Are the explanations easy to understand? If not, why? Is this manual arranged in an easy-to-follow manner? If not, how could we make it better? Are the examples useful? If not, please provide examples that are more useful. Did you find any errors? On which page(s)? Please make any other suggestions here: Comments and Suggestions Beta 48 V4.3 Messages and Codes January 30, 2009 What is your opinion of Beta 48 in general? Please write your name, company, and address here: Beta Systems Software AG Alt-Moabit 90d D-10559 Berlin, Germany E-mail:
[email protected] We very much appreciate the time and attention you have given us in the effort to help us provide better service. All responses and information contained herein are the sole property of Beta Systems Software AG, which may use or distribute the responses in any way it considers appropriate without need of consent or obligation to the contributor.