Upload
musecz
View
647
Download
32
Embed Size (px)
Citation preview
8/10/2019 Beta 48 V43 Messages and Codes.pdf
1/148
Beta 48
Extended Job Manager
Messages and Codes
Version 4 Release 3
January 30, 2009
Document Number:D48EJM43-9-E
Beta SystemsSoftware AG
Alt-Moabit 90dD-10559 Berlin
Tel. +49 (0)30 726 118 410Fax +49 (0)30 726 118 810
8/10/2019 Beta 48 V43 Messages and Codes.pdf
2/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
3/148
List of Publications
January 30, 2009 Beta48 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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
4/148
List of Publications
II Beta 48 V4.3 Messages and Codes January 30, 2009
8/10/2019 Beta 48 V43 Messages and Codes.pdf
5/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
6/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
7/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
8/148
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 andCodes
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
9/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
10/148
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
I [:]
PID=
When you receive this type of message, no action is required.
Error message
E [:]
PID=
If you receive an error message, you will need to take action.
Overview
Example of a log file
Format of log records
8/10/2019 Beta 48 V43 Messages and Codes.pdf
11/148
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, BOLDletters.
Certain messages contain portions that can vary, and these portions are
indicated by lower case, italicletters.
Message components
Conventions used in this
manual
8/10/2019 Beta 48 V43 Messages and Codes.pdf
12/148
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 codex and a
4. Message text
For example:
EJMnnnnxmessage text EJM = prefixpre
nnnn= message number
x = type code x
There are three different type codes for the one-character type codex:
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, BOLDletters. Certain
messages contain portions that can vary, and these portions are indicated
by lower case, italicletters.
Overview
Message format
Message type codes
8/10/2019 Beta 48 V43 Messages and Codes.pdf
13/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
14/148
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 hasnot 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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
15/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
16/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
17/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
18/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
19/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
20/148
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 tofunction.
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
21/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
22/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
23/148
8/10/2019 Beta 48 V43 Messages and Codes.pdf
24/148
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 thejob.
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
25/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
26/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
27/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
28/148
8/10/2019 Beta 48 V43 Messages and Codes.pdf
29/148
8/10/2019 Beta 48 V43 Messages and Codes.pdf
30/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
31/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
32/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
33/148
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 CATALOGWritten 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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
34/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
35/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
36/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
37/148
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 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 GIVENWritten to:
Log file.
Explanation:
The parameter 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 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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
38/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
39/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
40/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
41/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
42/148
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 forthe DATASET given in the FTPSTEP.
System Action:
Job is aborted.
Operator Response:
Check DATASET definition in RACF.
Messages
8/10/2019 Beta 48 V43 Messages and Codes.pdf
43/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
44/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
45/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
46/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
47/148
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 TRACKERWritten 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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
48/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
49/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
50/148
8/10/2019 Beta 48 V43 Messages and Codes.pdf
51/148
8/10/2019 Beta 48 V43 Messages and Codes.pdf
52/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
53/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
54/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
55/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
56/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
57/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
58/148
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, andvice 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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
59/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
60/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
61/148
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.
mailto:[email protected]:[email protected]8/10/2019 Beta 48 V43 Messages and Codes.pdf
62/148
UNIX/Windows and SAP Messages 6200 9999 API Messages from the Agent
56 Beta 48 V4.3 Messages and Codes January 30, 2009
8/10/2019 Beta 48 V43 Messages and Codes.pdf
63/148
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
8/10/2019 Beta 48 V43 Messages and Codes.pdf
64/148
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:
EJM5nnnxmessage (transaction ID)
The message informs you about the stage of the process.
The transaction IDrefers to the z/OS transaction that routed the job or
the job status information.
5nnnstands 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 keywordFAILED
Written to:
JESMSGLG.
Explanation:
The update of the LST parameter keywordin online option D.S.1has
failed. An invalid value has been entered.
System Action:
None.
Operator Response:
Enter a valid value and retry the update.
Overview
Messages
8/10/2019 Beta 48 V43 Messages and Codes.pdf
65/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
66/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
67/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
68/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
69/148
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 forNOERROR 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 notbeen 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 notbeen 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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
70/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
71/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
72/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
73/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
74/148
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.
EJM5139Ijob 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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
75/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
76/148
8/10/2019 Beta 48 V43 Messages and Codes.pdf
77/148
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 namecould not be successfully established for the jobjob
name. See the return code rcfor 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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
78/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
79/148
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.
8/10/2019 Beta 48 V43 Messages and Codes.pdf
80/148
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_IPADDRparameter 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.