zServer Messages and Diagnostics - Micro Focus...zServer Messages and Diagnostics Introduction This document provides a description of messages issued by z/Server including possible

zServer Messages and Diagnostics

Micro FocusThe Lawn22-30 Old Bath RoadNewbury, Berkshire RG14 1QNUKhttp://www.microfocus.com

Copyright © Micro Focus . All rights reserved.

MICRO FOCUS, the Micro Focus logo and are trademarks or registered trademarks of MicroFocus IP Development Limited or its subsidiaries or affiliated companies in the UnitedStates, United Kingdom and other countries.

All other marks are the property of their respective owners.

2014-10-15

ii

Contents

zServer Messages and Diagnostics ................................................................. 4Introduction ......................................................................................................................... 4

Message format ........................................................................................................4Error message example ........................................................................................... 5Warning message example ...................................................................................... 6Information message example ................................................................................. 6Messages and GTF ..................................................................................................6

Messages ............................................................................................................................6API - Application Programming Interface ................................................................. 6BND - IEWBIND (Binder) Interface .........................................................................11CSI - Catalog Search Interface ...............................................................................12DSC - Holder Task Configuration ........................................................................... 25DYN - Dynamic Allocation ...................................................................................... 28EMC - Extended MCS Interface ............................................................................. 28HLD - Holder Task Interface ................................................................................... 33IPC - Command Task ............................................................................................. 48JES - Job Entry Subsystem Interface .....................................................................58LIC - License Interface ........................................................................................... 60MAL - Email Interface .............................................................................................63REC - Recovery Exception Handler ....................................................................... 65REX - REXX Interface ............................................................................................ 70SJB - Started Job ................................................................................................... 83SLR - TSO Scheduler Interface ..............................................................................86SPR - Standard Pool Routine ...............................................................................113SRV - Server Interface ......................................................................................... 116SSI - Subsystem Interface Routine ...................................................................... 118STA - Started Task Interface .................................................................................120TAU - Eclipse Client Interface ...............................................................................121UNI - Unicode code conversion services ............................................................. 154XML - XML System Parser Interface .................................................................... 157CEA TSO/E Address Space Services ..................................................................162ABEND Code U2222 ............................................................................................174Language Environment abends ........................................................................... 174

Troubleshooting ...............................................................................................................174Holder ...................................................................................................................174Scheduler ............................................................................................................. 175User server ...........................................................................................................177Trace level ............................................................................................................ 178Required information for SupportLine .................................................................. 178

Contents | 3

zServer Messages and Diagnostics

IntroductionThis document provides a description of messages issued by z/Server including possible correctiveactions. Every message has an 8-character identification and an associated message text.

Troubleshooting often requires knowledge of configuration settings, such as the name of the holder task,the scheduler task, and the user server task(s). Please see the z/Server Installation Guide for details aboutthese settings.

Most messages only appear in the JESx job log in different DD names and not in the z/OS hardcopy log.True hardcopy log messages are marked.

Message formatThe message identification has the form: pfxnnnns, where:

pfx The z/Server component prefix (facility ID)

The following facility IDs exist:

ID z/Server component

API Application programming interface (TCPIP)

BND IEWBND (Binder) interface

CSI Catalog search interface

DSC Holder task configuration

DYN Dynamic allocation

EMC Extended MCS interface

HLD Holder task interface

IPC Command task

JES Job entry subsystem interface

LIC License interface

MAL Email interface

REC Recovery exception handler

REX REXX command environment

SJB Started job interface

SLR TSO scheduler interface

SPR Standard pool routine

SRV Server interface

SSI Interface to z/OS SSI

STA Started task interface

TAU Eclipse client interface

4 | zServer Messages and Diagnostics

ID z/Server component

UNI Unicode conversion services

USS UNIX Interface

XML XML system parser interface

ZCA CEA TSO/E address space services

nnnn The message number for the component, for example, 0051. The message numbers are uniquewithin a component.

s The message severity:

I Information

W Warning

E Error

S Severe error

Informational messages are normally used for tracing or debugging purposes. Errors apply to theassociated service and are typically caused by incorrect arguments. Severe errors may require z/Server tobe restarted.

The message description provides information to identify the cause of the problem. Many messagescontain placeholders ([mmm], where mmm is a consecutive number; for example, [002] is the secondplaceholder). These placeholders are replaced with specific values in the actual message.

The message description may contain messages, return and reason codes, etc. passed from invokedservices (for example, the XML system parser or the security product). In these cases, the IBM manual tobe consulted for details of the problem is given.

With very few exceptions, the first placeholder ([001]) of each message is the timestamp when themessage was issued (hh:mm:ss.ttt):

hh hour

mm minutes

ss seconds

ttt milliseconds

The explanation for any message states whether the message is issued only at a certain IPTRACE level.The message will be issued at that trace level and higher. Trace levels include all messages from lowertrace levels.

Error message exampleError messages have severity E or S. There are three general classes of error:

• Errors caused by incorrect user input, such as incorrect password (SLR0071E) or filter did not find anydata sets (CSI0051E). Such errors can be rectified by correcting the input and retrying the action. Someof these error messages can only occur due to incorrect input to the set of z/Server APIs, typically froman Eclipse client.

• Errors that indicate problems in the configuration file, such as EMC0011E (port is not available). Sucherrors may be corrected by changing the configuration (a task for the system administrator), althoughthey can also indicate some other error that needs to be investigated (also a task for the systemadministrator).

• Errors that indicate an internal z/Server error, such as API0007E (error during call to EZASOKET). If themessage information provided does not help to identify the problem, please contact SupportLine.

zServer Messages and Diagnostics | 5

As an example, the CSI0051E message is issued by the CSI facility (CSI prefix) and has a severity of E(=error).

The message is shown as follows in this book:

CSI0051E [001] No data sets for filter [002] found

This message has two placeholders: [001] and [002]. The placeholders are replaced with the timestampand the associated filter. An actual CSI0051E error message would look like this:

CSI0051E 07:48:53.935 No data sets for filter SYS2 found

The two placeholders have been replaced with the time (07:48) and the filter (SYS2) that could not beresolved. In this case, using a filter that covers available data sets would prevent the error message.

Warning message exampleWarning messages have severity W. Such messages are normally written to the associated JESx DDname; see below. Warnings normally indicate that some standard action has been taken. If this action ordefault is not required or wanted, change the appropriate setting.

TAU0019W 09:14:05.443 Environment-Variable REATTACH was not specified, using defaults ! TAU0019W 09:14:05.651 Environment-Variable CCSID was not specified, using defaults ! TAU0019W 09:14:05.652 Environment-Variable TSOE_JOB_CLASS was not specified, using defaults ! TAU0019W 09:14:05.652 Environment-Variable TSOE_SCHED_TAB was not specified, using defaults ! LIC0007W 09:14:05.659 This server may only be used through a licensed client.

Information message exampleInformation messages have severity I. Such messages are normally written to the associated JESx DD name; see below.

SLR0111I 09:14:05.998 TSO/E-Scheduler Init/Term-Routine called with function START SLR0001I 09:14:06.170 TSO-Scheduler initialization HLD0030I 09:14:06.188 User administration ended with RC 00000000 (hex)

Messages and GTFFor debugging purposes, we recommend you start GTF and trace user records x'3E8'.

Note, however, that as a result, there will be significantly fewer messages written to the JESx spool. Mostmessages will be written to GTF only, regardless of the IPTRACE level being set. Using only the messagesremaining in the hardcopy log and the JESx job log, it may get difficult to follow what happens within z/Server.

Messages

API - Application Programming InterfaceAll API messages are issued by TAURIP03. It is used as an interface for all TCPIP communication.Standard return codes are described in the table below. This interface is called using z/Server API calls,both internally and externally.


Return Code Meaning

00 Function completed successfully.

-4 Invalid parameter list or last parameter not 'I' or 'T' ortimeout < 0.

-8 Connection closed.

-12 Timeout during receive.

-20 Program is not running in a server environment.

-24 Invalid parameter list.

-28 Function not allowed in a server environment.

-36 Only 1 TCB allowed in a non-LE environment

-40 Invalid value for compress.

-44 Invalid value for dump.

-48 Invalid value for version set.

-100*n Name/token pair not found for non-LE environment; n isthe return code from macro IEANTRT.

>0 Original error number from EZASOKET call.

API0001IAPI0001I hh:mm:ss.ttt Before call IP03 starting call in [002] environment. Function code: [003] Task area: [004] [005]

Explanation: [002] is either server or client.

[003] is described in SC31-8788 z/OS Communications Server IP Sockets ApplicationProgramming Interface Guide and Reference.

[004] is the address of the task area.

[005] is global (if [002] is server), otherwise local (if [002] is client)

Issued by: TAURIP03

User reponse: None.

API0002IAPI0002I hh:mm:ss.ttt After call IP03 ending call. RC is: [002].

Explanation: This is an informational message due to IPTRACE level 4 being set.

Issued by: TAURIP03

User response: None.

API0007EAPI0007E hh:mm:ss.ttt Error during call to EZASOKET. Function : [002] Reason code: [003]

Explanation: This message is issued when IPTRACE level 4 is set. See SC31-8788 z/OSCommunications Server IP Sockets Application Programming Interface Guideand Reference for details about the function used and the returned error.


Issued by: TAURIP03

System administratorresponse:

Determine why the error occurred. If necessary, contact SupportLine.

API0008IAPI0008I hh:mm:ss.ttt Timeout for SELECT is [002] seconds and [003] microseconds.


Issued by: TAURIP03


API0009EAPI0009E hh:mm:ss.ttt For function PeekMsg the sixth parameter must be 'P'.

Explanation: This message is issued in response to an API call.

Issued by: TAURIP03

User response: Correct the calling program.

API0010IAPI0010I hh:mm:ss.ttt Using static z/Server environment for client processing at address [002].


Issued by: TAURIP03


API0011IAPI0011I hh:mm:ss.ttt Message flags: [002] 1... .... Message is encrypted .1.. .... Message is from a dialog ...1 .... Message has no IP-Header


Issued by: TAURIP03


API0015IAPI0015I hh:mm:ss.ttt Before call [002] descriptor in hex [003].


[002] is one of the functions described in SC31-8788 z/OS Communications Server IPSockets Application Programming Interface Guide and Reference: INITAPI, SOCKET,CONNECT, CLOSE, TERMAPI, WRITE, RECV, SELECT, SO_LINGER,GETTASKAREA, GETHOSTID, SETTIMEOUT, SETBUFFERSIZE,SETCOMPRESSION or TAKESOCKET.

Issued by: TAURIP03



API0054SAPI0054S hh:mm:ss.ttt Terminating subtask with dump.

Explanation: The subtask terminates and writes a dump.


Determine why the subtask terminated. If necessary, contactSupportLine.

API0065IAPI0065I hh:mm:ss.ttt After call to [002] RC: [003] ERRNO: [004]


[002] is one of the functions described in SC31-8788 z/OS Communications Server IPSockets Application Programming Interface Guide and Reference: INITAPI, SOCKET,CONNECT, CLOSE, TERMAPI, WRITE, RECV, SELECT, SO_LINGER,GETTASKAREA, GETHOSTID, SETTIMEOUT, SETBUFFERSIZE,SETCOMPRESSION or TAKESOCKET.

Issued by: TAURIP03


API0069EAPI0069E hh:mm:ss.ttt Function code [002] is not supported.


Issued by: TAURIP03

User response: Use a supported function code.

API0072WAPI0072W hh:mm:ss.ttt Connection is closed and no data is available


Issued by: TAURIP03


API0076IAPI0076I hh:mm:ss.ttt Flushing input Buffer. [002] Bytes available.

Explanation: [002] is number of bytes available.

Issued by: TAURIP03


API0099IAPI0099I ====================================================== [001]===============================================================


Explanation: This is a separator line for the output. It is issued when IPTRACE level 4 is set.

[001] can have the values Socket Communication Area, Data received, Data written,ECB-Table-Entry and Data received after expand.

Issued by: TAURIP03


API0106WAPI0106W hh:mm:ss.ttt Negative length for receiving [002] bytes specified. Multiple reads are forced until specified length is reached.

Explanation: This is an informational message due to IPTRACE level 4 being set. Also, it hasmeaning for API calls only.

Issued by: TAURIP03


API0107EAPI0107E hh:mm:ss.ttt Function code [002] is not allowed in a server environment.


Issued by: TAURIP03

User response: Correct the program.

API0108WAPI0108W hh:mm:ss.ttt Delimiter >>[002]<< (hex) is specified. Multiple reads are forced until specified delimiter is found.

Explanation: This is an informational message due to IPTRACE level 4 being set. Also, it hasmeaning for API calls only.

Issued by: TAURIP03


API0109IAPI0109I hh:mm:ss.ttt Input message area for client allocated at [002] Output message area for client allocated at [003] Work message area for client allocated at [004] Each area is [005] bytes long


Issued by: TAURIP03


API0110IAPI0110I hh:mm:ss.ttt Change buffer size for client.

Explanation: This is an informational message.


Issued by: TAURIP03


API0111IAPI0111I hh:mm:ss.ttt Name of IP stack to be addressed changed to [002].

Explanation: This is an informational message due to IPTRACE level 4 being set. It is issued whenthe TAU utility is used (z/OS driver).

Issued by: TAURIP03


BND - IEWBIND (Binder) InterfaceAll BND messages are issued by TAURIP49. z/Server uses the IEWBIND service to process load modules(for details, see SA22-7644-xx: MVS Program Management: Advanced Facilities). This interface is calledusing z/Server API calls.

BND0001EBND0001E hh:mm:ss.ttt Error during call of IEWBIND with function [002] Return code was: [003] (hex) Reason code was: [004] (hex)

Explanation: The IEWBIND call failed.

Issued by: TAURIP49

User response: See SA22-7644-xx: MVS Program Management: Advanced Facilities to determine whythe call failed.

BND0002IBND0002I hh:mm:ss.ttt Binder utility called with command [002] For dataset [003] And member [004] Class [005] Section [006]


Issued by: TAURIP49


BND0003IBND0003I hh:mm:ss.ttt Binder utility ended with RC [002].


Issued by: TAURIP49


BND0004EBND0004E hh:mm:ss.ttt Buffer with [002] bytes is too small for the binder interface. A minimum of [003] bytes are required.


Explanation: Self-explanatory.

Issued by: TAURIP49

System administrator response: Increase the buffer size; see BUFFERSIZE/BUFFERUNIT in the z/Server Installation Guide.

BND0005EBND0005E hh:mm:ss.ttt Unknown class [002] for binder utility.


Issued by: TAURIP49

User response: Use a defined class. If necessary, contact SupportLine.

BND0006IBND0006I =========================================================== Header for Class : [002] and Section [003]====================================================================


[002] is the binder class name from the link listing.

[003] is the section name from the link listing.

Issued by: TAURIP49


CSI - Catalog Search Interfacez/Server uses the IGGCSI00 service to access the catalog (for details, see SC26-7409-xx: z/OS DFSMSManaging Catalogs). Many z/Server API calls involving data set filters result in the use of this interface.

CSI0001ECSI0001E hh:mm:ss.ttt Error during call of IGGCSI00. Return code: [002] (hex) Reason code: [003] (hex) see DFSMS Managing Catalogs for more information

Explanation: The IGGCSI00 service failed. Refer to message IDC3009I in SA22-7636-xx:MVS System Messages Volume 6 (GOS - IEA) for information on the returnand reason codes.

Issued by: TAURIP22


Determine why the service failed. If necessary, contact SupportLine.

CSI0002ICSI0002I ===================================================== [002]==============================================================


Issued by: TAURIP22



CSI0003ECSI0003E hh:mm:ss.ttt Invalid entry type [002] found.

Explanation: The entry type described by [002] is invalid.

Issued by: TAURIP22


Determine why an invalid entry type was used. If necessary, contactSupportLine.

CSI0004ICSI0004I hh:mm:ss.ttt Entry [002] of type [003] found.


Issued by: TAURIP22


CSI0005ICSI0005I hh:mm:ss.ttt Data for entry (hex): [002]


Issued by: TAURIP22


CSI0006ICSI0006I hh:mm:ss.ttt Catalog utility called with command [002] Data set filter: [003] Member filter: [004] Catalog flags: [005] (hex) 1... .... recall if data set is migrated .1.. .... return userdata with member list ..1. .... wait for until recall of data set is complete ...1 .... filter for MEMLIST specified .... 1... member for GETDATA specified .... .1.. create ENQ .... ..1. create DEQ


Issued by: TAURIP22


CSI0007ICSI0007I hh:mm:ss.ttt [002] Entries found


Issued by: TAURIP22



CSI0008ECSI0008E hh:mm:ss.ttt Dynalloc failed for DDname [002] Verb : [003] S99RC : [004] S99ERROR : [005] S99INFO : [006] S99ERSN : [007] Dataset : [008]

Explanation: The requested data set could not be allocated.

Issued by: TAURIP28, TAURIP35, TAURIP48, TAURIP49


See SA22-7608-xx: MVS Programming Authorized Assembler ServicesGuide (DYNALLOC macro) for details on the returned information. Ifnecessary, contact SupportLine.

CSI0009ICSI0009I hh:mm:ss.ttt DSCB for data set [002]


Issued by: TAURIP15


CSI0010ECSI0010E hh:mm:ss.ttt Empty data set filter is not allowed.


Issued by: TAURIP22

User response: Specify the correct filter.

CSI0011ICSI0011I hh:mm:ss.ttt Memlist utility called with data set [002].

Explanation: This is an informational message due to IPTRACE level 4 being set. It is issued inresponse to an API call.

Issued by: TAURIP28


CSI0012ECSI0012E hh:mm:ss.ttt Member list valid only for partitioned data sets.


Issued by: TAURIP22

User response: Perform the function against a member of a PO data set.

CSI0013ECSI0013E hh:mm:ss.ttt Obtain of DSCB information of data set [002] failed RC [003].


Explanation: Data set information could not be retrieved.

Issued by: TAURIP15


See SC26-7400-xx: DFSMSdfp Advanced Services under Return Codesfrom OBTAIN (Reading by Data Set Name). If necessary, contactSupportLine.

CSI0014WCSI0014W hh:mm:ss.ttt DSCB information or member list for data set [002] is not available because data set is migrated.


Issued by: TAURIP15


CSI0015ICSI0015I =========================================================== DSEB with length [001]====================================================================


Issued by: TAURIP28


CSI0016ECSI0016E hh:mm:ss.ttt HSM function [002] for data set [003] failed with RC [004]. See message ARC11xx for return codes.

Explanation: ARCHRCAL macro call failed.

Issued by: TAURIP31


See SC35-0420-xx: DFSMShsm Managing Your Own Data for details onthe return code. If necessary, contact SupportLine.

CSI0017ICSI0017I hh:mm:ss.ttt Recall utility called for data set [002].


Issued by: TAURIP31


CSI0018ICSI0018I hh:mm:ss.ttt Catalog utility ended with RC [002].


Issued by: TAURIP22



CSI0019ICSI0019E hh:mm:ss.ttt For command [002] the data set type must be A and DSORG must be PO or PS.


Issued by: TAURIP22

User response: Use the correct data set type.

CSI0020ECSI0020E hh:mm:ss.ttt For command [002] the record format must be F or V.


Issued by: TAURIP22

User response: Use the correct record format.

CSI0021ECSI0021E hh:mm:ss.ttt A member must be specified for a partitioned data set.


Issued by: TAURIP22

User response: Specify the appropriate member.

CSI0022ECSI0022E hh:mm:ss.ttt Do not specify a member name for a sequential data set.


Issued by: TAURIP22

User response: Do not specify a member.

CSI0023ECSI0023E hh:mm:ss.ttt Data set/member [002] is in use.


Issued by: TAURIP35

User response: Wait until data set/member becomes available.

CSI0024ECSI0024E hh:mm:ss.ttt Buffer size [002] (hex) is too small to hold all data. Read terminated after [003] records.


Issued by: TAURIP35, TAURIP45, TAURIP48, TAURIP49

System administrator response: Increase buffer size; see BUFFERSIZE/BUFFERUNIT in the z/ServerInstallation Guide.


CSI0025ECSI0025E hh:mm:ss.ttt Data set open for function [002] was not successful.


Issued by: TAURIP35, TAURIP48

System administrator response: Determine why OPEN failed. If necessary, contact SupportLine.

CSI0026ICSI0026I hh:mm:ss.ttt GetData/PutData utility called with command [002]. for Data set [003] Member [004] CCSID [005]




CSI0027ICSI0027I hh:mm:ss.ttt GetData/PutData utility ended with RC [002].




CSI0028ICSI0028I hh:mm:ss.ttt Data for PutData at address [002] with length [003] LRECL is [004]. RECFM is [005].


Issued by: TAURIP35


CSI0029ECSI0029E hh:mm:ss.ttt Length for PutData is invalid. Length must be a multiple of [002].


Issued by: TAURIP35

User response: Use the correct length for PutData.

CSI0030WCSI0030W hh:mm:ss.ttt Command task is busy. Enqueue/dequeue not possible. Please retry in a few moments.


Explanation: Enqueue and dequeue system services are issued by the CMDTASK in either thescheduler or a user server. That task was busy with another command when therequest came in.

Issued by: TAURIP35

User response: If this message was issued in response to an API call, retry the request. Otherwise,check why the command task does not respond. If necessary, contact SupportLine.

CSI0031ICSI0031I hh:mm:ss.ttt Racroute REQUEST=AUTH failed with RC: [002], RSN: [003]

Explanation: This message is issued due to IPTRACE level 4 being set. SeeSA22-7692-xx: Security Server RACROUTE Macro Reference.

Issued by: TAURIP22


Determine why the request failed. If necessary, contact SupportLine.

CSI0032ICSI0032I hh:mm:ss.ttt [002] records successfully written.


Issued by: TAURIP35


CSI0033ECSI0033E hh:mm:ss.ttt Attribute FIXED is not allowed for variable record length.


Issued by: TAURIP22

User response: Use the correct attributes for variable record lengths.

CSI0034ICSI0034I hh:mm:ss.ttt Dequeue successful.


Issued by: TAURIP35


CSI0035ECSI0035E hh:mm:ss.ttt Request for shared access to data set [002] failed because resource is in exclusive use by [003]


Issued by: TAURIP28

User response: Wait until [003] has given up exclusive use of the requested data set.


CSI0036ECSI0036E hh:mm:ss.ttt GQSCAN macro failed with RC [002]

Explanation: See SA22-7610-xx: MVS Programming: Authorized Assembler ServicesReference, Volume 2 (EDT-IXG) for the return code. RC=8 usually means thatthe resource to be freed via operator command was not held in the first place.

Issued by: TAURIP28


Determine why GQSCAN failed. If necessary, contact SupportLine.

CSI0037ECSI0037E hh:mm:ss.ttt [002] access for data set [003] not permitted.


Issued by: TAURIP22

User response: Ask the RACF administrator in your installation for the required access privileges.

CSI0038ECSI0038E hh:mm:ss.ttt Data set [002] not migrated. Recall not allowed.


Issued by: TAURIP22


CSI0039ECSI0039E hh:mm:ss.ttt Requested data set unavailable. The data set isallocated to another job and its usage attribute conflicts with this request.


Issued by: TAURIP35, TAURIP48, TAURIP49

User response: Wait until the data set becomes available.

CSI0040ICSI0040I hh:mm:ss.ttt HSM function [002] for data set [003] ended successfully.


Issued by: TAURIP31


CSI0041ICSI0041I hh:mm:ss.ttt HSM function [002] for data set [003] successfully queued. Nowait was specified.



Issued by: TAURIP31


CSI0042ECSI0042E hh:mm:ss.ttt Data set to submit must be defined with fixed length 80. RECFM=F/FB and LRECL=80


Issued by: TAURIP22

User response: Either reallocate the data set to be submitted from or use a data set with the correctattributes: RECFM=F/FB and LRECL=80.

CSI0043ICSI0043I hh:mm:ss.ttt Job with jobid [002] submitted.


Issued by: TAURIP35


CSI0044ECSI0044E hh:mm:ss.ttt ISPF packed format is not supported


Issued by: TAURIP35

User response: Use a data set that does not use ISPF packed format.

CSI0045ECSI0045E hh:mm:ss.ttt Invalid token [002] in compressed record found.


Issued by: TAURIP45


CSI0046ECSI0046E hh:mm:ss.ttt LRECL of uncompressed record ([002] bytes) is greater than LRECL with ([003] bytes).


Issued by: TAURIP45

User response: Determine why an uncompressed record is shorter than its compressed version.

CSI0047ECSI0047E hh:mm:ss.ttt Binder information is only allowed for data sets with RECFM U



Issued by: TAURIP22

User response: Do not use this function for data sets that are not allocated with RECFM=U.

CSI0048ECSI0048E hh:mm:ss.ttt Length of JCL or REXX is invalid. Length is zero or not a multiple of 80.


Issued by: TAURIP22

User response: Either reallocate the data set or use a data set with the correct attributes.

CSI0049ICSI0049I hh:mm:ss.ttt Job with jobid [002] successfully submitted.


Issued by: TAURIP22


CSI0050ECSI0050E hh:mm:ss.ttt For PUTJCL an ACEE is required at the CB level for userid [002]. You must activate task level security in the IP header.


Issued by: TAURIP12

User response: Activate task level security in the IP header of the calling program.

CSI0051ECSI0051E hh:mm:ss.ttt No data sets found for filter [002].


Issued by: TAURIP22

User response: If necessary, correct the filter specification.

CSI0052ECSI0052E hh:mm:ss.ttt Generic filter is not allowed for command [002].


Issued by: TAURIP22

User response: Correct the filter specification.

CSI0053ECSI0053E hh:mm:ss.ttt Entry [002] is returned with error code [003].



Issued by: TAURIP22


CSI0054ICSI0054I hh:mm:ss.ttt Find utility called for member [002]. Function flags: [003]


Issued by: TAURIP91


CSI0055ECSI0055E hh:mm:ss.ttt No data sets specified for command [002]


Issued by: TAURIP91

User response: Specify a data set.

CSI0056ECSI0056E hh:mm:ss.ttt DESERV function [002] ended with RC [003] and RSN [004].

Explanation: DESERV macro call failed; see SC26-7410-xx: DFSMS Using Data Sets for details onthe return code.

Issued by: TAURIP91

User response: Determine why the macro call failed.

CSI0057ECSI0057W hh:mm:ss.ttt Member [002] not found.


Issued by: TAURIP91

User response: Specify an existing member of this data set.

CSI0058ECSI0058E hh:mm:ss.ttt Data set [002] is migrated. Command [003] not possible.


Issued by: TAURIP22

User response: Do not use function [003] on a migrated data set.

CSI0059ECSI0059E hh:mm:ss.ttt Data set saved, but at least one record was truncated to [002] bytes.



Issued by: TAURIP35

User response: Validate the data set definition.

CSI0060ECSI0060E hh:mm:ss.ttt An invalid filter key was provided. Filter was : [002]


Issued by: TAURIP22

User response: Validate the filter key; the filter key should comply with MVS data set namingconventions.

CSI0061ICSI0061I hh:mm:ss.ttt Encrypting data to BASE64


Issued by: TAURIP35


CSI0062ICSI0062I hh:mm:ss.ttt Decrypting data from BASE64


Issued by: TAURIP35


CSI0063ECSI0063E hh:mm:ss.ttt Encrypt/decrypt for BASE64 failed.


Issued by: TAURIP35

User response: Determine why de- or encryption failed.

CSI0064ECSI0064E hh:mm:ss.ttt Dequeue for Dataset/Member [002] failed.

Explanation: This message is issued if a dequeue for major name SPFEDIT and minor name [002]fails. This message does not force an error.

Issued by: TAURIP35

User response: Determine why the dequeue failed. There might be no preceding enqueue.

CSI0065ECSI0065E hh:mm:ss.ttt Dequeue failed with RC [002]. Possible reason Enqueue does not exists Enqueue was not made from Server [003] and user [004]


Explanation: This message is issued if a dequeue of a resource was not successful. This messagedoes not force an error.

Issued by: TAURIP35

User response: Determine why the dequeue failed. There might be no preceding enqueues.

CSI0066ICSI0066I hh:mm:ss.ttt z/Server STOW routine called with function [002] for member [003] and data set [004]

Explanation: This is an informational message due to IPTRACE level 5 being set. This message isonly written if the z/Server is customized to maintain ISPF statistics.

Issued by: TAURSTOW


CSI0067ICSI0067I hh:mm:ss.ttt [002] ISPF statistics

Explanation: This is an informational message due to IPTRACE level 5 being set. This message isonly written if the z/Server is customized to maintain ISPF statistics. [002] may beCREATE or UPDATE.

Issued by: TAURSTOW


CSI0069ICSI0069I hh:mm:ss.ttt ----------------------------------------------------- Current user data -----------------------------------------------------

Explanation: This is an informational message due to IPTRACE level 5 being set. This message isonly written if the z/Server is customized to maintain ISPF statistics.

Issued by: TAURSTOW


CSI0070ICSI0070I hh:mm:ss.ttt ----------------------------------------------------- New directory entry -----------------------------------------------------

Explanation: This is an informational message due to IPTRACE level 5 being set. This message isonly written if the z/Server is customized to maintain ISPF statistics. After this messagethe new directory entry is written in dump format.

Issued by: TAURSTOW


CSI0071ECSI0071E hh:mm:ss.ttt Stow macro failed with RC [002] Reason [003] Member : [004] Dataset : [005]


Explanation: This message is written if z/Server is customized to maintain ISPF statistics. Theupdate of a directory entry failed. See DFSMS Macro Instructions for Data SetsSC26-7408-xx for more information.

Issued by: TAURSTOW

User response: Set the trace level to 6 and try to recreate the problem. Contact SupportLine.

CSI0072ICSI0072I hh:mm:ss.ttt DIRDATA [002] contains invalid hex values.


Issued by: TAURSTOW

User response:

DSC - Holder Task ConfigurationAll DSC messages are issued by TAUHOLD when the configuration file for the holder task IVPHOLDcontains invalid statements. They are found in DD statement SYSTSPRT of the holder task.

DSC0001EDSC0001E Name required for variable [001]

Explanation: Variable [001] is one of the following: SVC_PGM, DSP_NAME orCON_NAME.


Correct the statement in error.

DSC0002EDSC0002E Name of [001] is greater than 8 bytes.

Explanation: Variable [001] is one of the following: SVC_PGM, DSP_NAME orCON_NAME.



DSC0003EDSC0003E Value required for variable [001]

Explanation: Variable [001] is one of the following: SVC_NO, CON_QLIMIT, DSP_SIZE,DSP_PORT_LOW, DSP_PORT_High or DSP_MAX_SERV.



DSC0004EDSC0004E Value for variable [001] is not numeric

Explanation: Variable [001] is one of the following: SVC_NO, CON_QLIMIT, DSP_SIZE,DSP_PORT_LOW, DSP_PORT_High or DSP_MAX_SERV.




DSC0005EDSC0005E Value of [001] not between [002] and [003]

Explanation: Valid combinations for [001], [002] and [003] are:

[001] [002] [003]

SVC_NO 200 255

CON_QLIMIT 100 999

DSP_SIZE 1 1000

DSP_PORT_LOW 1 64000

DSP_PORT_High 1 64000

DSP_MAX_SERV 1 20



DSC0008EDSC0008E Name required for variable [001]

Explanation: Variable [001] is one of the following: DSP_TOKEN or CON_TOKEN.

System administrator response: Correct the statement in error.

DSC0009EDSC0009E Name of [001] is greater than 16 bytes

Explanation: Variable [001] is one of the following: DSP_TOKEN or CON_TOKEN.


DSC0020EDSC0020E DSP_PORT_HIGH is smaller than DSP_PORT_LOW



DSC0022EDSC0022E Scheduler name <Server.x> has more than 8 chars



DSC0023WDSC0023W Parameter IPTRACE not a positive integer. IPTRACE ignored.




DSC0024WDSC0024W Parameter DELAY not a positive integer. Default used.



DSC0025WDSC0025W Parameter DELAY out of range. Default used.



DSC0026WDSC0026W Maximum number of schedulers started. Further scheduler names ignored.


System administrator response: Correct the SERVER.x statement. The holder task starts.

DSC0027EDSC0027E DSP_MAX_SERV should be at least [001]. Unable to start requested schedulers.

Explanation: The number of schedulers specified via Server.x statements exceeds thenumber of schedulers allowed for this holder task. Start-up is terminated.


Increase the value for DSP_MAX_SRV to at least [001].

DSC0099IDSC0099I Configuration of z/Server holder task [001].

Explanation: The value of [001] can be:

• Started• ended with RC [002]

System administrator response: None.

DSC0100EDSC0100E Error during interpretation of configuration file. RC [001]


System administrator response: Determine why the error occurred.

DSC0101IDSC0101I Line [001]




DSC0102IDSC0102I Config [001]



DSC0200EDSC0200E Invalid value for [001] (not YES or NO)

Explanation: Variable [001] is one of the following: DSP_CREATE, SVC_INSTALL,CON_INSTALL or ADD_SERVER.



DYN - Dynamic Allocation

DYN0006EDYN0006E hh:mm:ss.ttt Dynalloc failed with RC [002]. Error-Code : [003] Info-Code : [004] Message : [005]

Explanation: This message is written if a dynalloc SVC99 has failed.

User response: See the Authorized Assembler Services Guide SA22-7608-xx for more information.Contact SupportLine and provide all the available output. If possible, try to recreate theproblem with trace level 6.

Issued by: TAURIP85

DYN0007EDYN0007E hh:mm:ss.ttt Call to DAIRFAIL routine IKJEFF18 failed with RC [002]

Explanation: A call to the DAIRFAIL routine to analyze return codes from dynamic allocation (SVC99) has failed.

Issued by: TAURIP85

User response: See TSO/E Programming Services SA22-7789-xx for more information. ContactSupportLine and provide all available output. If possible, try to recreate the problem withtrace level 6.

EMC - Extended MCS Interfacez/Server establishes an EMCS console to issue commands to the operating system z/OS. Commandresponses received through this interface are parsed. If problems are detected, they are reported viamessages with the EMC prefix.


EMC0001EEMC0001E hh:mm:ss.ttt [002] for EMCS console failed Major-Name : [003] Minor-Name : [004]


Issued by: TAURIP56

System administrator response: Determine why the EMCS console failed. If necessary, contactSupportLine.

EMC0002IEMC0002I hh:mm:ss.ttt Command for EMCS console is [002]


Issued by: TAURIP56


EMC0003EEMC0003E hh:mm:ss.ttt SVC failed for function [002] with RC [003] (hex).

Explanation: Function [002] (low-order byte):

X'01' RACROUTE

X'02' SSICALL

X'03' CMD for ECMD

X'04' Internal start

X'06' Activate EMCS Console

X'07' Deactivate EMCS Console

X'08' Command without CART

X'10' Command with CART

X'18' Send command to console

X'20' Get next message

X'40' Get next command response

X'80' Get response with CART (command and response token)

X'E0' Get response from EMCS

Return code [003]:

0-250 RACF return code

252 Callers’ address space is not authorized to call this SVC

253 No task level security environment to delete

254 R1 does not point to a valid TAURACFA control block on entry to SVCroutine


255 Address Space has no ACEE

256 Invalid function code

257 Console buffer is too small

Issued by: TAURIP56

Systemadministratorresponse:

Determine why the call failed. If necessary, contact SupportLine.

EMC0004EEMC0004E hh:mm:ss.ttt Function [002] for EMCS console failed with IPSCA_CONSRC was : [003] (hex) IPSCA_CONSRE was : [004] (hex)

Explanation: Self-explanatory. For [002] function (low-order byte), see EMC0003E.

Issued by: TAURIP56

System administrator response: Check why the EMCS console failed.

EMC0005IEMC0005I hh:mm:ss.ttt Response for EMCS console is [002]


Issued by: TAURIP56


EMC0006EEMC0006E hh:mm:ss.ttt EMCS console was not activated.


Issued by: TAURIP56

System administrator response: Determine why the console was not activated. If necessary, contactSupportLine.

EMC0007EEMC0007E hh:mm:ss.ttt [002] is not a valid function for interface EMCS


Issued by: TAURIP56

System administrator response: Determine why an invalid function was used. If necessary, contactSupportLine.

EMC0008IEMC0008I hh:mm:ss.ttt Waiting for console response.


Issued by: TAURIP56



EMC0009IEMC0009I hh:mm:ss.ttt Routine for EMCS console invoked with function [002] (hex)


Issued by: TAURIP56


EMC0010WEMC0010W hh:mm:ss.ttt Portcheck for port [002] skipped because EMCS console was not activated.

Explanation: An EMCS console is needed to issue commands and see commandresponses. The port check function requires that a TCPIP command isissued.

Issued by: TAURIP17


Check why no EMCS console was activated.

EMC0011EEMC0011E hh:mm:ss.ttt Port [002] is not available

Explanation: z/Server has determined that the requested port [002] is not available for theincoming request. When port check is active (PORTCHECK=1 in the schedulerconfiguration) there is a DISPLAY NETSTAT command for this port visible inhardcopy log that may give an indication why.

Issued by: TAURIP17


Determine why the port is not available. Check the hardcopy log, scheduler and/orholder configuration file (PORT parameter).

EMC0012EEMC0012E hh:mm:ss.ttt Console buffer of size [002] KB is too small to hold command response. Increase size of buffer.


Issued by: TAURIP56


Increase size of buffer in the configuration file (see BUFFERSIZE/BUFFERUNIT in the z/Server Installation Guide).

EMC0013IEMC0013I hh:mm:ss.ttt No REXX exec or LE-enabled program for postprocessing specified


Issued by: TAURIP56



EMC0014EEMC0014E hh:mm:ss.ttt REXX exec or program flag is invalid >>[002]<< Specify X'01' for REXX or X'02' for LE-enabled program


Issued by: TAURIP56

User response: Specify X'01' if you want to call a REXX exec or X'02' if an LE-enabled program is to becalled.

EMC0015IEMC0015I hh:mm:ss.ttt Using [002] [003] for postprocessing of command response


Issued by: TAURIP56


EMC0016IEMC0016I hh:mm:ss.ttt Calling [002] for postprocessing of command response


Issued by: TAURIP56


EMC0017IEMC0017I hh:mm:ss.ttt [002] ended with RC [003]


Issued by: TAURIP56


EMC0018IEMC0018I hh:mm:ss.ttt Using CART [002] as command and response token


Issued by: TAURIP56


EMC0019IEMC0019I hh:mm:ss.ttt Using area at address [002] for response


Issued by: TAURIP56



EMC0020IEMC0020I hh:mm:ss.ttt Internal console buffer allocated at address [002]


Issued by: TAURIP56


EMC0021IEMC0021I hh:mm:ss.ttt Internal console buffer at address [002] released.


Issued by: TAURIP56


EMC0022EEMC0022E hh:mm:ss.ttt Operator command has an invalid length of [002] (hex).Operator command must be greater than zero and less than 126


Issued by: TAURIP56

System administrator response: Use a valid operator command.

EMC0023EEMC0023E hh:mm:ss.ttt Portcheck unsuccessful because console utility failed with RC [002]This may be a temporary problem for RC=8 (ENQ failed).


Issued by: TAURIP17

System administrator response: Determine why the console utility failed. If necessary, contactSupportLine.

HLD - Holder Task InterfaceHolder task messages provide information about the resources owned by the holder task (mainly dataspace and SVC routine responses).

HLD0001IHLD0001I hh:mm:ss.ttt [002] holder task [003] startup

Explanation: This is an informational message sent to the operator console.

[002] Name of the task

[003] Version/release/modification level

Issued by: TAURHOLD



HLD0002IHLD0002I hh:mm:ss.ttt [002] holder task ready for commands

Explanation: This message is sent to the operator console and can be automated. The holderaddress space is now up and running.

[002] Name of the task

Issued by: TAURHOLD


HLD0003IHLD0003I hh:mm:ss.ttt Creating dataspace Name : [002] Size : [003] blocks Storagekey : [004]


Issued by: TAURHOLD


HLD0004IHLD0004I hh:mm:ss.ttt Writing name/token pair [002] DSPALET : [003] DSPORIGIN : [004] DSPBLOCK : [005] DSPFLAGS : [006]


Issued by: TAURHOLD


HLD0005IHLD0005I hh:mm:ss.ttt Deleting alet


Issued by: TAURHOLD


HLD0006IHLD0006I hh:mm:ss.ttt Deleting name/token pair


Issued by: TAURHOLD


HLD0007IHLD0007I hh:mm:ss.ttt Deleting dataspace



Issued by: TAURHOLD


HLD0008EHLD0008E hh:mm:ss.ttt Function [002] failed with RC [003] and reason code [004]

Explanation: Function [002] failed.

Issued by: TAURHOLD


• If the function is DSPSERV or ALESERV, see SA22-7609-xx: MVS Programming:Authorized Assembler Services Reference, Volume 1 (ALE-DYN) for the returnand reason codes.

• If the function is SVCUPDTE, see SA22-7612-xx: MVS Programming: AuthorizedAssembler Services Reference, Volume 4 (SET-WTO) for the return and reasoncodes.

• If the function is MCSOPER, see SA22-7611-xx: MVS Programming: AuthorizedAssembler Services Reference, Volume 3 (LLA-SDU) for the return and reasoncodes.

• If the function is IEANTCR or IEANTDL, see SA22-7610-xx: MVS Programming:Authorized Assembler Services Reference, Volume 2 (EDT-IXG) for the return andreason codes.

HLD0009IHLD0009I hh:mm:ss.ttt TSO environment successfully created A (command processor parameter list): [002]


Issued by: TAURHOLD


HLD0010EHLD0010E hh:mm:ss.ttt Creation of TSO environment failed Return code : [002] Reason code : [003] Abend code : [004]

Explanation: The IKJTSOEV service failed; see SA22-7789-xx: TSO/E ProgrammingServices for details.

Issued by: TAURHOLD


Determine why it failed. If necessary, contact SupportLine.

HLD0011IHLD0011I hh:mm:ss.ttt Dataspace additional parameters Collect statistics : [002]

Explanation: This message refers to deprecated functionality.


System administrator response: Contact SupportLine.

HLD0012IHLD0012I hh:mm:ss.ttt Creating partition [002] at address [003]



HLD0013EHLD0013E hh:mm:ss.ttt SVC Routine [002] could not be loaded. System completion code : [003] Return code : [004]

Explanation: LOAD of the SVC routine named [002] failed.

Issued by: TAURHOLD


Determine why the routine could not be loaded. If necessary, contactSupportLine.

HLD0014EHLD0014E hh:mm:ss.ttt ENQ failed: Another copy of TAURHOLD is currently installing the same SVC

Explanation: Establishing the SVC routine is serialized by an internal ENQ. That ENQ is heldin the system. This is due to another holder task implementing or havingimplemented the same SVC number.

Issued by: TAURHOLD


Check which routine is installing the same SVC. If necessary, use a differentSVC number.

HLD0015EHLD0015E hh:mm:ss.ttt Install of SVC [002] failed with RC [003]

Explanation: SVCUPDTE failed; see SA22-7612-xx: MVS Programming: AuthorizedAssembler Services Reference, Volume 4 (SET-WTO) for the return andreason codes.

Issued by: TAURHOLD


Determine why SVCUPDTE failed. If necessary, contact SupportLine.

HLD0016WHLD0016W hh:mm:ss.ttt SVC [002] with current entry address [003] will be replaced with new entry address [004]. Waiting for console reply


Issued by: TAURHOLD

System administrator response: Respond to the message on the console.


HLD0017EHLD0017E hh:mm:ss.ttt Delete of SVC [002] failed with RC [003]

Explanation: SVCUPDTE failed to delete the SVC routine from the system at termination; seeSA22-7612-xx: MVS Programming: Authorized Assembler Services Reference,Volume 4 (SET-WTO) for the return and reason codes.


Determine why SVCUPDTE failed. If necessary, contact SupportLine.

HLD0018IHLD0018I ------------------------------------------------------------------ Installing user SVC [001] ------------------------------------------------------------------


Issued by: TAURHOLD


HLD0019IHLD0019I hh:mm:ss.ttt User SVC [002] successfully installed. Program: [003] EPA: [004]


Issued by: TAURHOLD


HLD0020IHLD0020I hh:mm:ss.ttt Console reply was [002]


Issued by: TAURHOLD


HLD0021IHLD0021I ------------------------------------------------------------------ Creating SCOPE=COMMON data space [001] ------------------------------------------------------------------


Issued by: TAURHOLD


HLD0022IHLD0022I ------------------------------------------------------------------ Creating EMCS console [001] ------------------------------------------------------------------



Issued by: TAURHOLD


HLD0024IHLD0024I hh:mm:ss.ttt Activation for EMCS console [002] successful ID : [003] CSA : [004] Message : [005] ALET : [006]


Issued by: TAURHOLD


HLD0025IHLD0025I hh:mm:ss.ttt Function [002] ended successfully

Explanation: This is an informational message. Function [002] can be one of the following:

• Create Dataspace• Create Alet• Create Name/Token• Delete Alet• Delete Dataspace• Delete Name/Token

Issued by: TAURHOLD


HLD0026IHLD0026I ------------------------------------------------------------------ Cleanup user SVC ------------------------------------------------------------------


Issued by: TAURHOLD, TAURIP86


HLD0027IHLD0027I ------------------------------------------------------------------ Cleanup data space ------------------------------------------------------------------


Issued by: TAURHOLD



HLD0028IHLD0028I ------------------------------------------------------------------ Cleanup console ------------------------------------------------------------------


Issued by: TAURHOLD


HLD0029IHLD0029I hh:mm:ss.ttt User administration called with function >>[002]<< P3 : [003] Flag is : [004] 1... .... called from holder task .1.. .... use data space

Explanation: This is an informational message due to IPTRACE level 4 being set. [004] can have thefollowing values:

x'80' Called from holder task

x'40' Use data space.

Issued by: TAURIP27


HLD0030IHLD0030I hh:mm:ss.ttt User administration ended with RC [002] (hex)


The return code RC is one of the following:

RC Meaning

8 Function INIT not valid.

C Data space size not big enough.

14 Invalid function.

64 Scheduler port range outside defined portrange.

65 Scheduler port range overlaps anotherserver's port range.

66 Scheduler already in table. Scheduler is notadded.

68 Table is full.

6C Scheduler not found.

70 User not found.

72 User already in table.

76 User table is full.

7A CRP is outside table.


RC Meaning

7E User server is not a started job. Timeout isignored.

82 Port not found.

86 User administration not via data space.

8A Port is not locked. UNLOCK ignored.

8E Scheduler is locked.

92 Asid not found.

96 No free floating license available.

9E Resource table is full.

A2 Entry not found in resource table.

A6 No entry found for user server.

AA Portrange of server is overlapping withportrange of another server.

nnn For function code 9 this is not a return code,but rather internal information.

Issued by: TAURIP27


HLD0031IHLD0031I hh:mm:ss.ttt User data on entry


Issued by: TAURIP27


HLD0032IHLD0032I hh:mm:ss.ttt User data on exit


Issued by: TAURIP27


HLD0033IHLD0033I hh:mm:ss.ttt Server Information Lowest port over all servers : [002] Highest port over all servers : [003] Maximum numbers of servers : [004]


Issued by: TAURHOLD



HLD0034IHLD0034I hh:mm:ss.ttt [002] holder task shutdown

Explanation: This is an informational message issued to the operator console.

[002] Name of the address space

Issued by: TAURHOLD


HLD0035IHLD0035I hh:mm:ss.ttt Initializing data space for user administration


Issued by: TAURHOLD


HLD0036EHLD0036E hh:mm:ss.ttt Unexpected RC [002] from user administration

Explanation: Return code [002] can be one of the following:

8 INIT function not valid. INIT is allowed from holder task if a data space isused, or from a server if local storage should be used

C Size of data space or size of local area is not large enough to hold allrequired tables

14 Invalid function

Issued by: TAURHOLD


Determine what caused the unexpected return code. If necessary, contactSupportLine.

HLD0038EHLD0038E hh:mm:ss.ttt Dataspace too small for user administration Specify at least [002] blocks for DSP_SIZE


Issued by: TAURHOLD

System administrator response: Increase the DSP_SIZE parameter in the configuration file to at leastthe value [002].

HLD0039IHLD0039I hh:mm:ss.ttt Table for internal user administration allocated Size : [002] bytes Address : [003]


Issued by: TAURIP27



HLD0040EHLD0040E hh:mm:ss.ttt Command [002] invalid for z/Server holder task

Explanation: The command issued for the holder task TAURHLD was invalid. This message is issuedto the operator console.

Issued by: TAURHOLD

User response: Use a valid command.

HLD0041IHLD0041I hh:mm:ss.ttt Calling command REXX exec IPCMDHLD


Issued by: TAURHOLD


HLD0042IHLD0042I hh:mm:ss.ttt Command REXX exec IPCMDHLD ended with RC [002]


Issued by: TAURHOLD


HLD0043IHLD0043I hh:mm:ss.ttt Answer from REXX exec IPCMDHLD is :


Issued by: TAURHOLD


HLD0044IHLD0044I hh:mm:ss.ttt z/Server holder task received command [002]


Issued by: TAURHOLD


HLD0045EHLD0045E hh:mm:ss.ttt Command [002] for z/Server holder task contains invalid syntax.

Explanation: This is an error message sent to the operator console.

Issued by: TAURHOLD

System administrator response: Use the correct syntax for the command.


HLD0046EHLD0046E hh:mm:ss.ttt Scheduler [002] does not exist.


Issued by: TAURHOLD

System administrator response: Use an existing scheduler task name for the command.

HLD0047IHLD0047I hh:mm:ss.ttt Stopping [002] user server for scheduler [003]


Issued by: TAURHOLD


HLD0048IHLD0048I ------------------------------------------------------------------Starting server ------------------------------------------------------------------


Issued by: TAURHOLD


HLD0049IHLD0049I hh:mm:ss.ttt Starting server [002]


Issued by: TAURHOLD


HLD0050IHLD0050I ------------------------------------------------------------------ Stopping server ------------------------------------------------------------------


Issued by: TAURHOLD


HLD0051IHLD0051I hh:mm:ss.ttt Stopping server [002]


Issued by: TAURHOLD



HLD0052IHLD0052I hh:mm:ss.ttt Stopping user server for user [002] and scheduler [003] with jobid [004] and asid [005]


Issued by: TAURHOLD


HLD0053EHLD0053E hh:mm:ss.ttt Scheduler [002] already in table. ADD not processed.


Issued by: TAURHOLD

User response: Determine why scheduler [002] is already defined. If necessary, contact SupportLine.Issue a MODIFY <holder>,STOP,SCHED=[002] command to clear the scheduler fromthe user administration control structures.

HLD0054IHLD0054I hh:mm:ss.ttt Canceling user server for user [002] and scheduler [003] with jobid [004] and asid [005]


Issued by: TAURHOLD


HLD0055EHLD0055E hh:mm:ss.ttt Port [002] not within port range of z/Server holder task

Explanation: This is an error message sent to the operator console. The scheduler isconfigured to use ports that the associated holder address space is notconfigured to use.

Issued by: TAURHOLD


Correct the configuration file(s).

HLD0056EHLD0056E hh:mm:ss.ttt No user server running on port [002]

Explanation: This is an error message sent to the operator console in response to astop command for a specific port.

Issued by: TAURHOLD


Correct the command.


HLD0057WHLD0057W hh:mm:ss.ttt Scheduler [002] did not respond to STOP command. Scheduler will be canceled.

Explanation: This is a warning sent to the operator console. The scheduler to beterminated did not terminate after receiving the stop command. The holdertask will now use a cancel command to attempt termination.

Issued by: TAURHOLD


None.

HLD0058EHLD0058E z/Server holder task DD statement DSPPRT missing.

Explanation: This is an error message sent to the operator console. The requestedcommand response can only be shown when the DD statement DSPPRT isspecified in the holder task startup JCL.

Issued by: TAURDSP


Add the DSPPRT DD statement and restart the holder task.

HLD0059EHLD0059E z/Server holder task oncode : [001] at location [002]


Issued by: TAURDSP


Determine why the holder task encountered an error. If necessary,contact SupportLine.

HLD0060IHLD0060I hh:mm:ss.ttt Data space information printed to DD statement DSPPRT.


Issued by: TAURHOLD


HLD0061EHLD0061E hh:mm:ss.ttt Data space information failed with RC [002].

Explanation: This is an error message sent to the operator console. [002] can be one ofthe following:

08 Invalid function

12 Name/token pair not found

Issued by: TAURHOLD


Determine why the failure occurred. If necessary, contact SupportLine.


HLD0062IHLD0062I hh:mm:ss.ttt [002] ports found for STOP


Issued by: TAURHOLD


HLD0063IHLD0063I hh:mm:ss.ttt Scheduler [002] locked


Issued by: TAURIP27


HLD0064IHLD0064I hh:mm:ss.ttt Scheduler [002] unlocked


Issued by: TAURIP27


HLD0065IHLD0065I hh:mm:ss.ttt [002] Schedulers locked


Issued by: TAURHOLD


HLD0066IHLD0066I hh:mm:ss.ttt [002] Schedulers unlocked


Issued by: TAURHOLD


HLD0067EHLD0067E hh:mm:ss.ttt ASID [002] not associated with a user server. STOP command ignored.


Issued by: TAURHOLD


Determine why a STOP command was issued against an address spacethat is not a user server. If necessary, contact SupportLine.


HLD0068EHLD0068E hh:mm:ss.ttt Maximum count of [002] schedulers reached. Scheduler [003] not started. Increase value for DSP_MAX_SERV


Issued by: TAURHOLD


Increase the value for DSP_MAX_SRV in the holder configuration andrestart the holder task.

HLD0069IHLD0069I hh:mm:ss.ttt Holder task configuration Size data space specified....: [002] Blocks Size data space required.....: [003] Blocks Delay........................: [004] seconds Trace-Level..................: [005] Modify limit.................: [006] Size RESTAB in blocks........: [007] Max. # of entries in RESTAB..: [008] Reply........................: [009]

Explanation: This is an informational message due to IPTRACE level 4 being set. The messageshows the global configuration variables for the holder task.

Issued by: TAURHOLD


HLD0070IHLD0070I hh:mm:ss.ttt User [002] added to floating licensing.

Explanation: This is an informational message due to IPTRACE level 5 being set. The message isissued if the z/Server licence key contains floating licence information and a new user isadded to the floating licence table.

Issued by: TAUIP27


HLD0071IHLD0071I hh:mm:ss.ttt User [002] removed from floating licensing.

Explanation: This is an informational message due to IPTRACE level 5 being set. The message isissued if the z/Server licence key contains floating licence information and a user isremoved from the floating licence table.

Issued by: TAUIP27


HLD0072EHLD0072E hh:mm:ss.ttt No free floating licens for user [002]

Explanation: This message is issued if the z/Server license key contains floating license informationand all floating licenses are used up.


Issued by: TAURIP27

User response: A new license key is required to allow more parallel users.

HLD0073WHLD0073W Listener port [002] outside the defined portrange of holder [003]

Explanation: This message is issued if z/Server is started and the listener port PORT [002] isnot in the portrange [DSP_PORT_LOW,DSP_PORT_HIGH] of the holder task.

Issued by: TAURIP27


This does not indicate an error but the issue should be resolved.

HLD0074EHLD0074E Port range [002] – [003] is overlapping with portrange [004] – [005] of scheduler [006]

Explanation: This message is issued if a scheduler is started and the port rangeoverlaps with the port range of scheduler [006].

Issued by: TAURIP27


Ensure that the port ranges do not overlap.

HLD2001WHLD2001W SVC not available. Reply O to override or C to cancel

Explanation: When attempting to establish the SVC for this holder task, the operating systemdetected that the SVC number is already in use.

Issued by: TAURHOLD


Check the configuration file for the holder task to see if the correct SVC numberwas specified for this holder task. If not, reply C to cancel startup and specify againthe SVC number in the configuration file. Reply O to unconditionally use thespecified SVC number.

IPC - Command Task

IPC0001WIPC0001W hh:mm:ss.ttt PPT invalid syntax

Explanation: This refers to a deprecated parameter.

Issued by: TAURIP04


IPC0002WIPC0002W hh:mm:ss.ttt PPT does not exist



Issued by: TAURIP04


IPC0003WIPC0003W hh:mm:ss.ttt Invalid length for module name specified

Explanation: This message is sent to the operator console.

Issued by: TAURIP04


Determine why an invalid length was specified. If necessary, contactSupportLine.

IPC0004WIPC0004W hh:mm:ss.ttt Module [002] not in PPT


Issued by: TAURIP04


IPC0005IIPC0005I hh:mm:ss.ttt Task [002] scheduled for delete request of [003]


Issued by: TAURIP04


IPC0006WIPC0006W hh:mm:ss.ttt Could not delete PPT for program [002] because task [003] is terminated.


Issued by: TAURIP04


IPC0007WIPC0007W hh:mm:ss.ttt Could not delete PPT for program [002] because task [003] is busy.


Issued by: TAURIP04


IPC0040IIPC0040I hh:mm:ss.ttt z/Server command task is initializing.


Issued by: TAURIP04



IPC0042IIPC0042I hh:mm:ss.ttt Address of Communication event control block : [002] Address of Command input buffer : [003] Token : [004]


Issued by: TAURIP04


IPC0043IIPC0043I hh:mm:ss.ttt Command task invoked with [002] command


Issued by: TAURIP04


IPC0044IIPC0044I hh:mm:ss.ttt Data for command : -> [002]<-


Issued by: TAURIP04


IPC0052IIPC0052I hh:mm:ss.ttt shutdown

Explanation: This message is sent to the operator console.

Issued by: TAURIP04


IPC0061IIPC0061I hh:mm:ss.ttt Command [002] unknown

Explanation: The command issued is unknown.

Issued by: IPCMD, IPCMDTSO, TAURIP04


IPC0062IIPC0062E hh:mm:ss.ttt Invalid syntax for command KILL

Explanation: The wrong syntax was used.

Issued by: IPCMD

User response: Enter the correct syntax F <scheduler | user server>,KILL,TASK=nnn


IPC0063IIPC0063I hh:mm:ss.ttt Requested task number does not exist


Issued by: IPCMD


IPC0064IIPC0064I hh:mm:ss.ttt Scheduling [002] request to maintask IP address : [003] Port : [004]


Issued by: TAURIP04 (at trace level 5), TAURIP77 (at trace level 0)


IPC0065EIPC0065E hh:mm:ss.ttt Invalid syntax for command TRACE


Issued by: IPCMD

User response: Enter the correct syntax F <holder | scheduler | user server>,TRACE,LEVEL=n withn=[0..6]

IPC0066IIPC0066I hh:mm:ss.ttt Trace level changed to [002]

Explanation: Self-explanatory. [002] can be one of the values 0 to 6.

Issued by: TAURIP04


IPC0067IIPC0067E hh:mm:ss.ttt Invalid syntax for command REATTACH


Issued by: IPCMD

User response: Enter the correct syntax F <scheduler | user server>,REATTACH,TASK={nnn | ALL}

IPC0068IIPC0068I hh:mm:ss.ttt Checking availability of port [002]




IPC0069EIPC0069E hh:mm:ss.ttt Port [002] is not available Port in use by : [003] Connection ID : [004] State : [005]



Determine why the port is in use by [003]. If necessary, contactSupportLine.

IPC0070EIPC0070E hh:mm:ss.ttt Call to netstat was not succesful

Explanation: See DD statement SYSTSPRNT for more information.


Determine why the call to NETSTAT was unsuccessful. If necessary,contact SupportLine.

IPC0071IIPC0071I hh:mm:ss.ttt Using command exit [002]


Issued by: TAURIP04


IPC0072EIPC0072E hh:mm:ss.ttt Invalid syntax for command TSO


Issued by: IPCMDTSO

System administrator response: Use the correct command syntax.

IPC0073IIPC0073I hh:mm:ss.ttt Calling command exit [002] with data [003]


Issued by: TAURIP04


IPC0074IIPC0074I hh:mm:ss.ttt Using command REXX exec [002]


Issued by: TAURIP04



IPC0075IIPC0075I hh:mm:ss.ttt Calling command REXX exec [002]


Issued by: TAURIP04


IPC0076IIPC0076I hh:mm:ss.ttt Command REXX exec [002] ended with RC [003]

Explanation: This is an informational message due to IPTRACE level 4 being set. [002] is the nameof the REXX exec being executed, and [003] is the return code set by that exec.

Issued by: TAURIP04


IPC0077EIPC0077E hh:mm:ss.ttt Call to IP03 ended with RC [002]

Explanation: The general IP communication module TAURIP03 returned an error [002].See the section API - Application Programming Interface for an explanationof RC.

Issued by: TAURIP77


Determine why an error was returned. If necessary, contact SupportLine.

IPC0078EIPC0078E hh:mm:ss.ttt Invalid syntax for command COMPRESS


Issued by: IPCMD

System administrator response: Use the correct command syntax.

IPC0079IIPC0079I hh:mm:ss.ttt Compress level changed to [002]


Issued by: TAURIP04


IPC0080IIPC0080I hh:mm:ss.ttt ---------------------------------------------------- Addr : [002] Size : [003] TCB : [004] Name : [005] ----------------------------------------------------


Issued by: TAURIP04



IPC0081EIPC0081E hh:mm:ss.ttt Invalid syntax for command RECOVERY


Issued by: IPCMD

User response: Use the correct syntax.

IPC0082IIPC0082I hh:mm:ss.ttt Recovery changed to [002]


Issued by: TAURIP04


IPC0083EIPC0083E hh:mm:ss.ttt Invalid syntax for command REFRESH


Issued by: IPCMD

User response: Enter the correct syntax: F <scheduler | user server>,REFRESH,PGM=nn (nn =[02..99])

IPC0084IIPC0084I hh:mm:ss.ttt Answer from REXX exec [002] is :


Issued by: TAURIP04


IPC0085EIPC0085E hh:mm:ss.ttt Invalid syntax for command DUMP


Issued by: IPCMD

User response: Use the correct syntax:

F <scheduler | user server>,DUMP,AREA=ALL

F<scheduler | user server>, DUMP,ADDR=x,LEN=y

F <scheduler | user server>, DUMP,SVCD

F <scheduler | user server>, DUMP,CONFIG

IPC0086WIPC0086W hh:mm:ss.ttt VSMLOC for address [002] and length [003] failed with RC : [004] For RC=4


Storage not allocated in PVT Storage overlaps free space Storage overlaps other subpools

Explanation: Self-explanatory. See SA22-7612-xx MVS Programming: AuthorizedAssembler Services Reference, Volume 4 (SET-WTO) for an explanation of[004].

Issued by: TAURIP04



IPC0087EIPC0087E hh:mm:ss.ttt Invalid syntax for command REXX f taskname,rexx,[ts!te!ht,rt,hi],subtask=[nn!all]


Issued by: IPCMD

User response: Use the correct syntax:

F <scheduler | user server>,REXX,[TS | TE | HT | RT | HI],SUBTASK=[nn | ALLl]

IPC0088EIPC0088E hh:mm:ss.ttt SVC dump not possible, because user server was not configured to use a SVC routine.

Explanation: This refers to deprecated functionality.

Issued by: TAURIP04


IPC0090IIPC0090I ------------------------------------------------------------------ Initial configuration settings at address [001] ------------------------------------------------------------------


Issued by: TAURIP04


IPC0091IIPC0091I [001]


Issued by: TAURIP04


IPC0092EIPC0092E hh:mm:ss.ttt Invalid syntax for command DISPLAY



Issued by: IPCMD


IPC0093EIPC0093E hh:mm:ss.ttt GQSCAN failed with RC [002]

Explanation: This is an informational message issued to the operator console. SeeSA22-7610-xx: MVS Programming: Authorized Assembler Services Reference,Volume 2 (EDT-IXG) for an explanation of the return code [002].

Issued by: TAURIP04



IPC0094IIPC0094I S= [001] [002] [003]


Issued by: TAURIP04


IPC0095IIPC0095I SysName JobName Asid TCBAddr EXC/SHR Status


Issued by: TAURIP04


IPC0096IIPC0096I hh:mm:ss.ttt [002] [003] [004] [005] [006]


Issued by: TAURIP04


IPC0097EIPC0097E hh:mm:ss.ttt Invalid syntax for command DEQ


Issued by: IPCMD


IPC0098IIPC0098I hh:mm:ss.ttt Current virtual storage map for server [002] printed to ddname CMDTASK.


Explanation: This is an informational message issued to the operator console in response toa request to print the current virtual storage map. [002] is either the name of ascheduler or of a user server.

Issued by: TAURIP04


See DD statement CMDTASK in the job log for the storage map.

IPC0099IIPC0099I hh:mm:ss.ttt Resource [002] not held by [003]


Issued by: TAURIP04

System administrator response: Determine why resource [002] is not held by [003].

IPC0100EIPC0100E hh:mm:ss.ttt Invalid slave command [002]. No action peformed.


Issued by: TAURIP04


IPC0101IIPC0101I hh:mm:ss.ttt Slave command [002] received.


Issued by: TAURIP04


IPC0102IIPC0101I hh:mm:ss.ttt Modify limit is [002].

Explanation: This is an informational message due to IPTRACE level 5 being set. This messageshows the setting of the configuration variable MODIFY_LIMIT of the holder task.

Issued by: TAURIP04


IPC0104IIPC0104I hh:mm:ss.ttt Waiting [002] milliseconds for command task.

Explanation: This is an informational message due to IPTRACE level 5 being set. This message isissued if a remote enqueue or dequeue was requested, and the command task is busy.

Issued by: TAURIP38


IPC0105WIPC0105W hh:mm:ss.ttt Command task for server [002] is terminating.


Explanation: The command task is closing and will not accept any more commands.

Issued by: TAURIP04


JES - Job Entry Subsystem InterfaceThe z/Server API calls to the JES interface are used to process spool data sets.

JES0001IJES0001I hh:mm:ss.ttt JES Utility called with command [002]




JES0002IJES0002I hh:mm:ss.ttt JES utility ended with RC [002]


Returncode:

16 Invalid function

20 SSI call failed

24 No filter specified

28 DYNALLOC failed, see LE message file for more information

32 Data set open failed

36 Buffer too small to hold XML document



JES0003EJES0003E hh:mm:ss.ttt SSI call for function code [002] failed with RC [003] SSOBRETN is ............. : [004] Reason is ............. : [005]

Explanation: IEFSSREQ failed. See SA22-7642-xx: MVS Using the Subsystem Interface for details.Keep in mind that the function code, return code, SSOBRETN and Reason code areshown here as hexadecimal values, while the referenced book shows them as decimalvalues. SSOBRETN [004] and Reason [005] are the return code and reason codereturned by the invoked service.

[002] Function code can be:

1 (X'01') Process JES SYSOUT data sets

11 (X'0B') Validation/Conversion

15 (X'0F') Verify subsystem function

20 (X'14') Request job ID


21 (X'15') Return job ID

54 (X'36') Request subsystem version information

70 (X'46') Scheduler Facilities services

71 (X'47') JES JOB information

75 (X'4B') Notify user message service

79 (X'4F') SYSOUT Application Program Interface (SAPI)

80 (X'50') Extended Status Function Call

82 (X'52') JES properties

[003] RC: IEFSSREQ invocation return code. A non-zero return code indicates that apassed parameter was not valid, for example, 8 = subsystem exists but is not active).



IEFSSREQ macro error. Determine why it failed. If necessary, contact SupportLine.

JES0004EJES0004E hh:mm:ss.ttt No filter specified for function [002]



User response: Specify a filter.

JES0005EJES0005E hh:mm:ss.ttt Dynalloc failed for DDname [002] Verb code : [003] S99RC : [004] S99ERROR : [005] S99INFO : [006] S99ERSN : [007] Data set : [008]

Explanation: The requested data set could not be allocated. See SA22-7608-xx: MVSProgramming: Authorized Assembler Services Guide for details on thereturned information.



Determine why DYNALLOC failed. If necessary, contact SupportLine.

JES0006EJES0006E hh:mm:ss.ttt Open of data set [002] was not successful.




Determine why the data set was not opened successfully. If necessary,contact SupportLine.


JES0007EJES0007E hh:mm:ss.ttt Buffer with size of [002] (hex) too small to hold all data. Read terminated after [003] records.



System administrator response: Increase the buffer size.

JES0008IJES0008I hh:mm:ss.ttt [002] work units (JOES) deleted.


Issued by: TAURIP42


JES0009IJES0009I hh:mm:ss.ttt Cancel command [002] accepted and routed to console.


Issued by: TAURIP42


JES0010IJES0010I hh:mm:ss.ttt Stop command for job [002] accepted.


Issued by: TAURIP42


JES0013EJES0013E hh:mm:ss.ttt [002] cannot be canceled. CANCEL command only allowed for jobs.

Explanation: A user tried to cancel an STC or TSU address space.

Issued by: TAURIP42

User response: Cancel not allowed for STC or TSU address spaces.

LIC - License InterfaceThe use of z/Server requires a valid license. The license interface performs the associated processing.

LIC0001ELIC0001E hh:mm:ss.ttt License key [002] not valid. Reason : [003]

Explanation: Self-explanatory. This message is issued to the operator console.


Reason code:

1 License contains non-hexadecimal character

2 Invalid delimiter (not '-')

3 Byte 8 of Key-2 is not 0 or 1

4 Invalid date in key part 3

5 License key expired

6 Part 2 must be binary 0 or 1

Issued by: TAURIP88


Update the configuration with the correct license key (LICENCE_KEYparameter).

LIC0002WLIC0002W hh:mm:ss.ttt This server is licensed for a specific LPAR


Issued by: TAURIP88

System administrator response: Ensure that the server runs on the licensed LPAR.

LIC0003ILIC0003I hh:mm:ss.ttt Value after decrypt [002]

Explanation: This is an informational message due to IPTRACE level 4 being set and refers todeprecated functionality.


LIC0004WLIC0004W hh:mm:ss.ttt License key expires in [002] days.


Issued by: TAURIP88

System administrator response: Renew the license.

LIC0005ELIC0005E hh:mm:ss.ttt License key expired. Server stopped.


Issued by: TAURIP00

System administrator response: Renew the license.

LIC0006ELIC0006E hh:mm:ss.ttt Feature for command [002] not licensed.


Issued by: TAURIP78


System administrator response: Extend the license for the appropriate facility that supports thecommand.

LIC0007WLIC0007W hh:mm:ss.ttt This server may only be used through a licensed client.


Issued by: TAURIP88

User response: Use a licensed client.

LIC0008ELIC0008E hh:mm:ss.ttt This server requires a version 2 header. You must specify COMPAT=2 for startup


Issued by: TAURIP88


LIC0009ILIC0009I hh:mm:ss.ttt License flag 2 is : [002]


Issued by: TAURIP88


LIC0010ELIC0010E hh:mm:ss.ttt License violation: This server accepts requests from an eclipse client only.


Issued by: TAURIP73

User response: Use an Eclipse client.

LIC0011ILIC0011I hh:mm:ss.ttt Changing limited to eclipse key information from client to scheduler. Old value : [002] New value : [003]

Explanation: This is an informational message due to trace level 5 being set andrefers to deprecated functionality.

Issued by: TAURIP78


Contact SupportLine.

LIC0012ELIC0012E hh:mm:ss.ttt This server is not licensed to use the CEA TSOE address space manager.


Explanation: The used license key does not allow the use of the CEA TSOEaddress space manager.

Issued by: TAURIP88


Apply a valid license key.

LIC0013ILIC0013I hh:mm:ss.ttt This server is licensed for [002] parallel users.

Explanation: This is an informational message and indicates that the used license key islimited to [002] parallel users. The number of floating licenses in use can bedetermined using the command F <holder>,DISPLAY,DSP,FORMAT.

Issued by: TAURIP88


None

MAL - Email Interfacez/Server can send emails to make the administrator aware of problems that happened. This is donethrough the email interface.

MAL0001EMAL0001E hh:mm:ss.ttt Unable to open DD [002]. RC : [003]


Issued by: TAURIP55

User response: Determine why the data set with the DD [002] could not be opened.

MAL0002EMAL0002E hh:mm:ss.ttt I/O error on internal reader. RC : [002]


Issued by: TAURIP55

User response: Determine why the I/O error occurred.

MAL0003EMAL0003E hh:mm:ss.ttt Invalid function >>[002]<< for email interface


Issued by: TAURIP55

User response: Determine why an invalid function was used.

MAL0004EMAL0004E hh:mm:ss.ttt email interface disabled due to previous error


Issued by: TAURIP55



MAL0006IMAL0006I hh:mm:ss.ttt [002] Lines with [003] bytes for email at address [004] allocated.


Issued by: TAURIP55


MAL0007IMAL0007I hh:mm:ss.ttt email interface invoked with function >>[002]<<


Issued by: TAURIP55


MAL0008IMAL0008I hh:mm:ss.ttt Initializing email interface


Issued by: TAURIP55


MAL0009IMAL0009I hh:mm:ss.ttt Email interface successfully initialized DCB header address : [002] DCB Email address : [003] Threshold : [004] Bundle message count : [005] Class : [006] Writer : [007]


Issued by: TAURIP55


MAL0010IMAL0010I hh:mm:ss.ttt Sending email


Issued by: TAURIP55


MAL0011EMAL0011E hh:mm:ss.ttt Error during close of DD [002]. RC : [003]



Issued by: TAURIP55

User response: Determine why an error occurred.

MAL0012EMAL0012E hh:mm:ss.ttt [002] with major [003] and minor [004] ended with RC [005] (hex). Email interface is now disabled.


Issued by: TAURIP55

User response: Determine why the problem occurred.

MAL0013EMAL0013E hh:mm:ss.ttt Dynalloc failed for DDname [002] S99RC : [003] S99INFO : [004] S99ERROR : [005] S99ERSN : [006]

Explanation: Self-explanatory. See SA22-7608-xx: MVS Programming: Authorized AssemblerServices Guide for information on [002] - [006].

Issued by: TAURIP55

User response: Determine why DYNALLOC failed.

MAL0014IMAL0014I hh:mm:ss.ttt Terminating email interface


Issued by: TAURIP55


REC - Recovery Exception HandlerThe Recovery Exception Handler performs the clean-up processing of Language Environment exceptionsto ensure orderly task termination. This processing involves tasks such as closing open DCBs and otherheld resources for the associated job (task). It is also invoked for normal end of task (stop command).

REC0001EREC0001E hh:mm:ss.ttt Recovery exception handler was invoked. CIB flag 5 : [002] CIB flag 6 : [003] Token : [004] (hex)


The two CIB (Language Environment Condition Information Block) flags have thefollowing meanings:

CIB Flag 5 (CEL events)

1... .... ABEND caused


.1.. .... Program check caused

..1. .... Condition management raised TIU (Termination Imminent due toUnhandled condition)

...1 .... New condition result from a promote

.... 1... Signalled condition

.... .1.. Attention interrupt caused

CIB Flag 6 (CEL actions)

1... .... ABEND reason code valid

.1.. .... Math routine condition

..1. .... Resume allowed

...1 .... MRC type 1

.... 1... Enable only pass (no conditional pass)

.... .1.. Hcursor pointing to owning SF

.... ..1. Doing post SF0 scan

.... ...1 All members informed of condition



Determine why recovery was invoked. If necessary, contact SupportLine.

REC0002EREC0002E hh:mm:ss.ttt Move cursor behind BALR in subtask was not successful.

Explanation: In language environment recovery scenarios, the "cursor" (next instruction to beexecuted) can be set to a specific instruction, in this case behind a BALRinstruction. This action failed.


Determine why recovery was invoked. If necessary, contact SupportLine.

REC0003EREC0003E hh:mm:ss.ttt Error in program [002] at offset [003] Original message : [004]



System administrator response: Internal error. Send the appropriate logs to SupportLine.

REC0004IREC0004I hh:mm:ss.ttt Checking for open files


Issued by: TAURIP36



REC0005IREC0005I hh:mm:ss.ttt DCB found


Issued by: TAURIP36


REC0006IREC0006I hh:mm:ss.ttt Open DCB found for DDname [002] and data set [003]

Explanation: This message indicates that data set [003] was still open under DD name [002] whenthe error occurred and will be closed.

Issued by: TAURIP36


REC0007IREC0007I hh:mm:ss.ttt DCB closed. RC [002]


Issued by: TAURIP36


REC0008IREC0008I hh:mm:ss.ttt TIU or promote call. No activities.

Explanation: This message indicates that LE has given control to the z/Server program for retry.



REC0009EREC0009E hh:mm:ss.ttt Resume is not allowed. Subtask will terminate.

Explanation: In language environment terminology, resume is the retry option for (E)STAEroutines. In this case, retry is not allowed, so LE enforces percolation andterminates the subtask.

Issued by: TAURIP36


Determine why an error occurred. If necessary, contact SupportLine.

REC0010EREC0010W hh:mm:ss.ttt Member not found in data set.


Issued by: TAURIP36


User response: Specify a valid member.

REC0011EREC0011E hh:mm:ss.ttt Data set or member already open for output by another user or job.

Explanation: This message indicates an abend S213-30. See SA22-7626-xx: MVS System Codes.

Issued by: TAURIP36

User response: Use a unique member name that is not in use by anyone else.

REC0012EREC0012E hh:mm:ss.ttt Data set opened for output used all available space.

Explanation: This message indicates an abend SD37-4. See SA22-7626-xx: MVS System Codes.

Issued by: TAURIP36

User response: Reallocate the data set with larger space attributes and recreate the data set.

REC0013EREC0013E hh:mm:ss.ttt Insufficient access authority.

Explanation: This message indicates an abend S913-38. See message ICH408I inJESYSMSG for details.

Issued by: TAURIP36

System administrator response: Provide the necessary access authority.

REC0014WREC0014W hh:mm:ss.ttt Subtask not recovered. Error percolated to LE recovery.

Explanation: This message is issued to the operator console. z/Server is not attemptingto retry the error.



Determine why an error occurred. If necessary, contact SupportLine.

REC0015IREC0015I hh:mm:ss.ttt Cleanup for TSOE scheduler started


Issued by: TAURIP36


REC0016IREC0016I hh:mm:ss.ttt Extra buffer at address [002] freed.


Issued by: TAURIP36



REC0017IREC0017I hh:mm:ss.ttt XML image at address [002] freed.


Issued by: TAURIP36


REC0018IREC0018I hh:mm:ss.ttt Deleting ACEE for user [002] and TCB [003]


Issued by: TAURIP36


REC0019IREC0019I hh:mm:ss.ttt Checking for ACEE


Issued by: TAURIP36


REC0020SREC0020S hh:mm:ss.ttt Critical error during data space processing. Server is terminating.

Explanation: A system abend S067 has occurred. z/Server assumes that the data spacewas lost.

Issued by: TAURIP36


Check if the holder task is still running. If the holder task is running, contactSupportLine and provide the joblogs of all z/Server tasks.

REC0021SREC0021S hh:mm:ss.ttt Critical error during SVC processing. Server is terminating.

Explanation: An error occured when the SVC routine TAURAUTH was running. z/Server nowassumes that SVC routine TAURAUTH is lost.

Issued by: TAURIP36


Check if the holder task is still running. If the holder task is running, contactSupportLine and provide the joblogs of all z/Server tasks and any system dumpthat may have occured.

REC0022IREC0022I hh:mm:ss.ttt Condition token [002] hex ignored.


Explanation: The z/Server recovery was invoked with an LE condition token [002]that is ignored.

Issued by: TAURIP36

System administrator response: None

REC0023IREC0023I hh:mm:ss.ttt Cleanup resource table for Data set : [002] Member : [003]

Explanation: The z/Server recovery was invoked and the recovery routine detectedan ENQ for data set [002] and member [003].

Issued by: TAURIP36


None

REC0024EREC0024E hh:mm:ss.ttt Sequential data set for FINDMEM not allowed.

Explanation: A FINDMEM was issued and the user data set list contains a sequential data set.

Issued by: TAURIP36

User response: Remove the sequential data set from the data set list.

REX - REXX Interface

REX0001EREX0001E hh:mm:ss.ttt Error in variable access routine IRXEXCOM Variable : [002] Access : [003] Response : [004]

Explanation: The IRXEXCOM function failed; see SA22-7790-xx: TSO/E REXXReference for the meaning of [004].

Issued by: TAURIP70



REX0002IREX0002I hh:mm:ss.ttt Before call of variable access routine IRXEXCOM Variable : [002] Access : [003] SHVVALA : [004] (hex) SHVBUFL : [005] (hex) SHVVALL : [006] (hex) ENVBLOCK : [007] (hex)


Issued by: TAURIP70



REX0003IREX0003I hh:mm:ss.ttt After call of variable access routine IRXEXCOM SHVRET : [002] (hex) SHVVALL : [003] (hex) RC : [004] (hex)


Issued by: TAURIP70


REX0004IREX0004I hh:mm:ss.ttt Host command environment zComm called with command [002] Using environment at address : [003] Using environment from subtask : [004]


Issued by: TAURIP30


REX0005EREX0005E hh:mm:ss.ttt Variable [002] not numeric.



User response: Specify a numeric value for [002].

REX0006EREX0006E hh:mm:ss.ttt Variable [002] contains invalid IP address.


Issued by: TAURIP30

User response: Specify a valid IP address for variable [002].

REX0007IREX0007I hh:mm:ss.ttt Address of REXX environment block is [002] Userfield : [003]


Issued by: TAURIP25


REX0008EREX0008E hh:mm:ss.ttt Call to IRXINIT with function [002] failed. RC : [003] (hex) RC : [004] (hex)


Explanation: The IRXINIT function [002] failed; see SA22-7790-xx: TSO/E REXXReference.

Issued by: TAURIP25


Determine why the call to IRXINIT failed. If necessary, contactSupportLine.

REX0009EREX0009E hh:mm:ss.ttt Call to IRXSUBCM with function [002] failed with RC [003] (hex)

Explanation: The IRXSUBCM function failed; see SA22-7790-xx: TSO/E REXX Reference.

[002] IRXSUBCM function

[003] IRXSUBCM return code

Issued by: TAURIP25

User response: Determine why the function failed. If necessary, contact SupportLine.

REX0010EREX0010E hh:mm:ss.ttt Call to ISPEXEC with function [002] failed with RC [003] (hex)

Explanation: The ISPEXEC function failed; see SA22-7790-xx: TSO/E REXX Reference.

[002] ISPEXEC function

[003] ISPEXEC return code

User response: Determine why the call to ISPEXEC failed. If necessary, contact SupportLine.

REX0011EREX0011E Call to ISPLINK with function [002] failed with RC [003] (hex)

Explanation: The ISPLINK function failed; see SA22-7790-xx: TSO/E REXX Reference.

[002] ISPLINK function

[003] ISPLINK return code

Issued by: TAURIP25

User response: Determine why ISPLINK failed. If necessary, contact SupportLine.

REX0012IREX0012I hh:mm:ss.ttt ISPF environment is not available or address of TLD0 could not be found

Explanation: During startup of the user server, z/Server tests the availability of an ISPF environment.There is no ISPF environment available.

Issued by: TAURIP25



REX0013WREX0013W hh:mm:ss.ttt A TSO/E environment already exists. An additional dynamic environment is not created.

Explanation: During startup of the scheduler or user server, z/Server tests the availability of a TSOenvironment. Because of the way the address space is started, no additional TSOenvironment needs to be created.

Issued by: TAURIP25


REX0014IREX0014I hh:mm:ss.ttt TSO environment successfully created A (command processor parameter list) : [002]


Issued by: TAURIP25


REX0015EREX0015E hh:mm:ss.ttt Creation of TSO-Environment failed RC : [002] RSN : [003] Abend code : [004]

Explanation: The IKJTSOEV service failed; see SA22-7789-xx: TSO/E Programming Services.

Issued by: TAURIP25

User response: Determine why IKJTSOEV failed. If necessary, contact SupportLine.

REX0016WREX0016W hh:mm:ss.ttt Variable [002] was not specified. Default value is assumed.


Issued by: TAURIP70


REX0017EREX0017E Acronym for host command environment is invalid. Either the environment is not available or is damaged.This may happen if a reusable environment was not terminated.

Explanation: The acronym ZCOMM is not specified in a control block.


Determine why the control block acronym is not where it is supposed to be. Ifnecessary, contact SupportLine.


REX0018EREX0018E Reusable host command environment terminated because communication area was invalid. Command for host command environment zComm was not executed.



REX0019SREX0019S hh:mm:ss.ttt Host command environment not initialized. You must initialize a static environment for a TSO address space.



REX0020IREX0020I hh:mm:ss.ttt Initializing static z/Server environment for client processing.



REX0021IREX0021I hh:mm:ss.ttt Terminating static z/Server Environment for client processing.



REX0022EREX0022E hh:mm:ss.ttt Call to IRXEXCOM failed with RC [002] (hex).

Explanation: The IRXEXCOM function failed; see SA22-7790-xx: TSO/E REXX Reference.

Issued by: TAURIP70

User response: Determine why the call to IRXEXCOM failed. If necessary, contact SupportLine.

REX0023SREX0023S hh:mm:ss.ttt User field of environment block is zero. Invalid environment. Information for subtask is not available.

Explanation: Self explanatory. This is probably caused by a storage overlay.

Issued by: TAURIP30


Obtain an SVC dump of the address space using the z/OS DUMP commandand send it to SupportLine along with the job log(s).

REX0024IREX0024I hh:mm:ss.ttt Initialize z/Server for [002] parallel REXX environment


Explanation: This is an informational message. [002] is the configuration variable value namedMULTI_REXX.

Issued by: TAURIP25


REX0025EREX0025E hh:mm:ss.ttt z/Server is configured for single REXX environment but more than one subtask was found.

Explanation: MULTI_REXX is set to 0 in the configuration file, indicating a single REXXenvironment. NUMTCB was set to a value other than 1, contradicting theMULTI_REXX setting.

Issued by: TAURIP30


Correct the configuration (see MULTI_REXX in the z/Server InstallationGuide).

REX0026IREX0026I hh:mm:ss.ttt ISPF is available. Address of TLD1 : [002] Address of TLD0 : [003]


Issued by: TAURIP69


REX0027IREX0027I hh:mm:ss.ttt Host command environment ended with RC [002]


Issued by: TAURIP30


REX0028IREX0028I hh:mm:ss.ttt ========================================================= ISPF [002] =========================================================

Explanation: This is an informational message due to IPTRACE level 5 being set. [002] is the ISPFcontrol block being printed.

Issued by: TAURIP71


REX0029EREX0029E hh:mm:ss.ttt Invalid acronym for control block [002] at address [003]

Explanation: The expected acronym is not specified in the control block [002].


Issued by: TAURIP71


This may be an internal error. Obtain a dump using the z/OS DUMPcommand and send it to SupportLine along with the job log(s).

REX0030EREX0030E hh:mm:ss.ttt ISPF table [002] not found


Issued by: TAURIP71

User response: Determine why table [002] was not found. If necessary, contact SupportLine.

REX0031IREX0031I hh:mm:ss.ttt Reading table [002] from row [003] to row [004]


Issued by: TAURIP71


REX0032EREX0032E hh:mm:ss.ttt Specified value for TBFROW [002] or TBTROW [003] is invalid or outside the bounds of table [004] with [005] lines.


Issued by: TAURIP71

User response: Specify valid values for TBFROW and TBTROW.

REX0033IREX0033I hh:mm:ss.ttt Var : [002] Text : [003]

Explanation: This is an informational message listing variable names and their content.

Issued by: TAURIP71


REX0034IREX0034I hh:mm:ss.ttt Row [002] of table [003] contains [004] savenames.

Explanation: This is an informational message due to IPTRACE level 4 being set. Save names areadditional columns in one row.

Issued by: TAURIP71


REX0035EREX0035E hh:mm:ss.ttt CRP [002] for table [003] is invalid.



Issued by: TAURIP71

User response: Specify a valid current row pointer.

REX0036IREX0036I hh:mm:ss.ttt CRP for table [002] is set to line [003]


Issued by: TAURIP71


REX0037IREX0037I hh:mm:ss.ttt RDA for row [002] at address [003] with EYE [004]

Explanation: This message is issued in response to an API call. RDA is an ISPF control block, andeye denotes the control block acronym.

Issued by: TAURIP71


REX0038IREX0038I hh:mm:ss.ttt Creating a non-reentrant REXX environment for TSO/E and ISPF

Explanation: This is an informational message indicating that the configuration parameterMULTI_REXX is set to a value greater than 0.

Issued by: TAURIP25


REX0039IREX0039I hh:mm:ss.ttt Creating a reentrant REXX environment for REXX

Explanation: This is an informational message indicating that the configuration parameterMULTI_REXX is set to a value greater than 0.

Issued by: TAURIP25


REX0040IREX0040I hh:mm:ss.ttt Host command environment [002] added on environment block [003].


Issued by: TAURIP25


REX0041IREX0041I hh:mm:ss.ttt First 40 bytes of data : [002]



Issued by: TAURIP70


REX0042EREX0042E hh:mm:ss.ttt No search argument found for table [002].


Issued by: TAURIP71

User response: Specify a valid search argument.

REX0043IREX0043I hh:mm:ss.ttt Number of entries in SAWA [002]

Explanation: This is an informational message due to IPTRACE level 5 being set. SAWA is an ISPFcontrol block.

Issued by: TAURIP71


REX0044IREX0044I hh:mm:ss.ttt SAWA entry Length of value for compare : [002] Address of value for compare : [003] Operator for compare : [004] Index of varname : [005]


Issued by: TAURIP71


REX0045IREX0045I hh:mm:ss.ttt Number of matching rows for TBSCAN was [002]


Issued by: TAURIP71


REX0046IREX0046I hh:mm:ss.ttt Row match for TBSCAN


Issued by: TAURIP71


REX0047IREX0047I hh:mm:ss.ttt Table [002] not found using TLD1, trying TLD0.



Issued by: TAURIP71


REX0048EREX0048E hh:mm:ss.ttt Invalid severity [002] for command LOGMSG.


Issued by: TAURIP14

User response: Specify a valid severity for the LOGMSG command.

REX0049EREX0049E hh:mm:ss.ttt More than 9 slots defined.

Explanation: This message is issued in response to an API call. It indicates an LErestriction.

Issued by: TAURIP14


REX0050EREX0050E hh:mm:ss.ttt Value for slot [002] greater than 80 bytes.


User response: Determine why this value was specified. If necessary, contact SupportLine.

REX0051EREX0051E hh:mm:ss.ttt Invalid format [002] for slot [003].


Issued by: TAURIP14

User response: Specify a valid format.

REX0052EREX0052E hh:mm:ss.ttt Invalid options [002] specified for LOGMSG.


Issued by: TAURIP14

User response: Specify a valid option.

REX0053IREX0053I hh:mm:ss.ttt ========================================================= [002] =========================================================

Explanation: This is an informational message. [002] is the title of the dump.


Issued by: TAURIP79


REX0054EREX0054E hh:mm:ss.ttt Call to IRXEXEC failed with RC [002] (hex).

Explanation: The IRXEXEC function failed; see SA22-7790-xx: TSO/E REXXReference.

Issued by: TAURIP79


Determine why IRXEXEC failed. If necessary, contact SupportLine.

REX0055IREX0055I hh:mm:ss.ttt Internal REXX executor called with flag [002]

Explanation: This is an informational message due to IPTRACE level 5 being set. [002] describes theREXX exec to be executed (attribute NO/RENT).

Issued by: TAURIP79


REX0056IREX0056I hh:mm:ss.ttt Searching for DSECT : [002]


Issued by: TAURIP89


REX0057EREX0057E hh:mm:ss.ttt DSECT [002] not found


Issued by: TAURIP89

User response: Determine why the DSECT was not found. If necessary, contact SupportLine.

REX0058IREX0058I hh:mm:ss.ttt Number of DSECTs in table : [002] ----------------------------------------------------


Issued by: TAURIP89


REX0059IREX0059I hh:mm:ss.ttt [002] [003] [004] [005]



[002] Variable name

[003] Variable length

[004] Variable type

[005] Variable content

Issued by: TAURIP89


REX0060IREX0060I hh:mm:ss.ttt [002] variables in DSECT [003]


Issued by: TAURIP89


REX0062EREX0062E hh:mm:ss.ttt Address for DSECT [002] and length [003] invalid RC from VSMLOC : [004] Storage not allocated in PVT Storage overlaps free space Storage overlaps other subpools

Explanation: This message is issued in response to an API call. The address to be mapped byDSECT [002] is not a valid storage address. This is validated using the z/OS VSMLOCservice. See SA22-7612-xx: MVS Programming: Authorized Assembler ServicesReference, Volume 4 (SET-WTO) for the return code [004] from the VSMLOC service.

Issued by: TAURIP89

User response: Determine why an invalid storage address was specified to be mapped. If necessary,contact SupportLine.

REX0063IREX0063I hh:mm:ss.ttt DSECT utility called with function [002]


Issued by: TAURIP89


REX0064IREX0064I hh:mm:ss.ttt Varpool utility called with function [002]


Issued by: TAURIP90



REX0065EREX0065E hh:mm:ss.ttt Call to SPR failed with RC [002]

Explanation: SPR is the standard pool routine. The return codes can be:

8 Variable not found

12 Invalid function

16 Variable pool is full

20 Variable pool not defined

24 Enqueue for VPUT failed

Issued by: TAURIP90



REX0066WREX0066W hh:mm:ss.ttt Variable [002] scope [003] not found

Explanation: This is an informational message due to IPTRACE level 1 being set. It isissued in response to an API call.

Issued by: TAURIP90


Determine why the variable wasn't found. If necessary, contact SupportLine.

REX0067IREX0067I hh:mm:ss.ttt Varpool utility ended with RC [002]


Issued by: TAURIP90


REX0068IREX0068I hh:mm:ss.ttt Call to IRXIC for subtask [002] with command [003] and environment[004] ended with RC [005] (hex)


Issued by: TAURIP04


REX0069EREX0069E hh:mm:ss.ttt Reentrant REXX environment does not exist.


Issued by: TAURIP01


System administrator response: Determine why a re-entrant REXX environment was expected. Ifnecessary, contact SupportLine.

REX0070IREX0070I hh:mm:ss.ttt Call to IRXEXCOM ended with RC [002]



REX0071EREX0071E hh:mm:ss.ttt Enqueue for [002] [003] failed with RC [004]

Explanation: Self-explanatory. [002] is the major name of the ENQ, [003] the minorname.

Issued by: TAURIP14


Determine why the ENQ failed. If necessary, contact SupportLine.

REX0072EREX0072E hh:mm:ss.ttt Command task is busy. Enqueue/Dequeue not possible. Please retry in a few moments.

Explanation: The command task can only execute one command at a time. Currently itis busy for another request.

Issued by: TAURIP14


Retry the request. If the message persists, contact SupportLine.

SJB - Started JobThese messages are issued when a user server runs as a started job.

SJB0001ESJB0001E hh:mm:ss.ttt Configuration parameter TSOE_SJOB_NAME must be specified if a user server should start as a started task.


Issued by: TAURIP18

System administrator response: Correct the configuration (see TSOE_SJOB_NAME in the z/ServerInstallation Guide).

SJB0002ESJB0002E hh:mm:ss.ttt Start command for user server [002] failed with return code [003]


Return code:

252 Calling address space user is not authorized to use this user SVC.


253 No task level security environment to delete.

254 R1 does not point to a valid TAURACFA control block on entry to SVCroutine.

255 Address Space has no ACEE (Accessor Environment Element).

256 Invalid function code.

257 Console buffer is too small.

Issued by: TAURIP53


Determine why the START command failed. If necessary, contact SupportLine.

SJB0003ESJB0003E hh:mm:ss.ttt A user server can only be started through a z/Server scheduler.


Issued by: TAURIP83

System administrator response: Do not start a user server manually; let the scheduler issue the startcommand.

SJB0004ISJB0004I hh:mm:ss.ttt Internal start command [002] RC : [003] ASID : [004]


Issued by: TAURIP53


SJB0005ESJB0005E hh:mm:ss.ttt User server not started. Unable to find JOBID for started task. ASID : [002] RSN : [003]

Explanation: After starting a user server, the scheduler waits for the user server to report itselfready. The user server did not report itself ready, so the scheduler checks systemcontrol blocks to see if the user server address space started correctly but cannotfind the job name. Reason is the reason code from LOCASCB; see SA22-7611-xx:MVS Programming: Authorized Assembler Services Reference, Volume 3 (LLA-SDU). This happens typically when there was a JCL error or another startupproblem for the user server.

Issued by: TAURIP53


Determine why the user server did not report itself ready. If necessary, contactSupportLine.


SJB0006ISJB0006I hh:mm:ss.ttt Generated start command for user server : [002]


Issued by: TAURIP53


SJB0007ESJB0007E hh:mm:ss.ttt Unable to get jobname for ASID [002]

Explanation: During startup, a z/Server was not able to resolve the jobname for ASID[002].

Issued by: TAURIP27


Restart z/Server with trace level 5. If the problem persists, contactSupportLine.

SJB0008ISJB0008I hh:mm:ss.ttt Checking ASID [002] for server [003]

Explanation: This is an informational message. During startup of a z/Server, a duplicateentry was found in the data space. z/Server will check if the entry can bereused or the new started z/Server is duplicated.

Issued by: TAURIP27


None.

SJB0009WSJB0009W hh:mm:ss.ttt Entry for server [002] with ASID [003] will be reused for ASID [004]

Explanation: During startup of a z/Server, a duplicate entry was found in the data space. z/Server will check the entry in the data space. Because the entry in the data spaceis no longer valid, the entry is reused for the new started z/Server. This situationmay happen if a z/Server is canceled and was not able to delete its entry in thedata space.

Issued by: TAURIP27


None.

SJB0010ESJB0010E hh:mm:ss.ttt Entry for server [002] with ASID [003] already active. Startup will be terminated

Explanation: During startup of a z/Server, a duplicate entry was found in the data space. z/Server will check the entry in the data space. Because the entry in the data spaceis valid, the startup of the new started z/Server is terminated. This situation may


happen if a z/Server with the same name is started twice in the scope of the sameholder task.

Issued by: TAURIP27


Check why the STC is started twice.

SJB0011ESJB0011E hh:mm:ss.ttt Portrange for server [002] changed. Entry cannot be reused.

Explanation: During startup of a z/Server, a duplicate entry was found in the data space. z/Serverwill check the entry in the data space. Because the entry in the data space is no longervalid, the entry can be reused for the new started z/Server. Because the portrangechanged since the last startup, the entry cannot be reused and the startup of the newz/Server is terminated. This situation may happen if a z/Server is canceled and wasnot able to delete its entry in the data space.

Issued by: TAURIP27


Issue the command F <holder>,STOP,SCHED=<scheduler> with <scheduler> thename specified in [002] to delete the entry in the data space.

SLR - TSO Scheduler InterfaceThese messages are produced when the scheduler TAURISPF is defined as a class 1 or class 2 scheduler.

SLR0001ISLR0001I hh:mm:ss.ttt TSO/E scheduler initialization


Issued by: TAURIP74


SLR0002ISLR0002I hh:mm:ss.ttt TSO/E scheduler termination



SLR0003ISLR0003I hh:mm:ss.ttt Stopping user server [002]


Issued by: TAURIP78


SLR0004ISLR0004I hh:mm:ss.ttt Stop of user server was unsuccessful. RC [002]




Determine why the stop command for the user server did not succeed. Ifnecessary, contact SupportLine.

SLR0005ESLR0005E hh:mm:ss.ttt User area 1 is not defined. Define area and restart server



SLR0006ESLR0006E hh:mm:ss.ttt User area 1 is too small for [TSOPORTS) ports. User area 1 must have at least [002] bytes.



SLR0007ISLR0007I hh:mm:ss.ttt Routing message for user [002] to port [003] Message length : [004]


Issued by: TAURIP78


SLR0008ESLR0008E hh:mm:ss.ttt Unexpected return code [002] (hex)

Explanation: An unexpected return code was received in response to an API call.

Issued by: TAURIP78

User response: Determine why an unexpected return code was received. If necessary, contactSupportLine.

SLR0009ESLR0009E hh:mm:ss.ttt ACEE for TCB is not available or userid of TCB is not the same as specified in input message



SLR0010ESLR0010E hh:mm:ss.ttt User table is full. Increase size of User area 1




SLR0011ESLR0011E hh:mm:ss.ttt Asid for job already exists on this lpar.



SLR0012ESLR0012E hh:mm:ss.ttt Job data set could not be opened



SLR0013ESLR0013E hh:mm:ss.ttt I/O error during read of Job data set



SLR0014ESLR0014E hh:mm:ss.ttt User server [002] for user [003] already exists with jobid [004]. User server not started.


Issued by: TAURIP53


SLR0015ESLR0015E hh:mm:ss.ttt TSO/E server [002] for user [003] submitted more than [004] times. Limit reached.



SLR0016ESLR0016E hh:mm:ss.ttt Server was marked unusable in a prior error


System administrator response: Restart the user server or scheduler after correcting the originalproblem.

SLR0017ESLR0017E hh:mm:ss.ttt Variable in JCL is invalid




SLR0018ISLR0018I hh:mm:ss.ttt TSO/E server [002] for user [003] submitted



SLR0019ISLR0019I hh:mm:ss.ttt TSO/E scheduler initialization completed. Delay after submit : [002] ms Jobclass : [003] MSGCLASS : [004] First port : [005] Last port : [006] Cleanup user jobs : [007]

Explanation: This is an informational message. [007] can have the values yes or no.

Issued by: TAURIP74


SLR0020SSLR0020S hh:mm:ss.ttt TSO/E server [002] with JOBID [003] for user [004] had a JCL error. Dispatcher is marked unusable.



SLR0021SSLR0021S hh:mm:ss.ttt TSO/E server [002] with JOBID [003] for user [004] is duplicate. Dispatcher is marked unusable.



SLR0022SSLR0022S hh:mm:ss.ttt More than one active job [002] for user [003] found. Dispatcher is marked unusable.



SLR0023ISLR0023I hh:mm:ss.ttt TSO/E server [002] with JOBID [003] for user [004] submitted.


Issued by: TAURIP53



SLR0024ESLR0024E hh:mm:ss.ttt TSO/E server [002] with JOBID [003] for user [004] is not executing. Reason [005]



SLR0025ESLR0025E hh:mm:ss.ttt User [002] not found. Stop command ignored.

Explanation: The user was not found in the user administration, so the requested stopcommand is not issued.

Issued by: TAURIP53


Check the entries in the user administration and determine why the specifieduser server is not running.

SLR0026ISLR0026I hh:mm:ss.ttt Stop command for user [002] accepted.


Issued by: TAURIP53


SLR0027WSLR0027W hh:mm:ss.ttt Job [002] ID [003] system [004] phase [005]



SLR0028ESLR0028E hh:mm:ss.ttt TSO/E server for user [002] is not running. Please connect first.

Explanation: No user server for user [002] could be found in user administration. Either the userserver was addressed invalidly in an API call or the user server had terminatedunexpectedly.

Issued by: TAURIP78

User response: Determine why the addressed user server could not be found in user administration.

SLR0029WSLR0029W hh:mm:ss.ttt Job [002] ID [003] canceled




SLR0030ISLR0030I hh:mm:ss.ttt Retrieving status for job [002] and user [003]

Explanation: This is an informational message due to IPTRACE level 4 being setand refers to deprecated functionality.

Issued by: TAURIP78



SLR0031SSLR0031S hh:mm:ss.ttt Job [002] for user [003] not found. Please reconnect for resubmit.



SLR0032ESLR0032E hh:mm:ss.ttt Job [002] for user [003] not ready. Please check Job status and wait.



SLR0033ESLR0033E hh:mm:ss.ttt Job [002] for user [003] finished. Port entry cleared. Contact your administrator.



SLR0034ESLR0034E hh:mm:ss.ttt Enqueue for internal reader failed. Please contact your System administrator.

Explanation: Probably due to a previous error, the ENQ governing the use of the internalreader was not freed.

Issued by: TAURIP12


Obtain a dump using the dump command and send it to SupportLine alongwith the job log(s).

SLR0035ISLR0035I hh:mm:ss.ttt Job [002] ID [003] system [004] phase [005]


Issued by: TAURIP78



SLR0036ISLR0036I hh:mm:ss.ttt [002] [003] [004] [005] [006] [007]

Explanation: This is an informational message due to IPTRACE level 4 being set. The placeholdervalues denote:

002 Job name

003 Job ID

004 Job phase

005 Last command used

006 Timestamp of record in user administration

007 Port

Issued by: TAURIP27


SLR0037ISLR0037I Time format : MMDDHHMMSS Phase : 01-0D Not Running Last-Command : I Initialized 0E Running E Error 0F-1B Finished S Submit P Stop D Delete entry ====================================================================== JobName JOBId userId phase Last command time Port ======================================================================


Issued by: TAURIP27


SLR0038WSLR0038W hh:mm:ss.ttt User [002] not found. Delete command ignored.

Explanation: The delete command specified a user ID that is not available in the useradministration control structures. The delete command is ignored.

Issued by: TAURIP77


Specify a valid user ID.

SLR0039ISLR0039W hh:mm:ss.ttt User [002] deleted.


Issued by: TAURIP77



SLR0040ISLR0040I ====================================================================== Server Statistics ======================================================================


Issued by: TAURIP77


SLR0041ISLR0041I Submit count [001] times Stop count [002] times Communicate count [003] times Error count 004] times


Issued by: TAURIP77


SLR0042ISLR0042I ------------------------------------------------------------------ Server configuration Environment variable Value ------------------------------------------------------------------ TSOE_DELAY_AFTER_SUBMIT : [001] TSOE_JOB_CLASS : [002] TSOE_FIRST_PORT : [003] TSOE_LAST_PORT : [004] TSOE_CLEANUP : [005] TSOE_PORTCHECK : [006]


Issued by: TAURIP77


SLR0043ISLR0043I hh:mm:ss.ttt [002] for address space ended. RC [003]

Explanation: This is an informational message due to IPTRACE level 4 being set andrefers to deprecated functionality.



SLR0044ISLR0044I hh:mm:ss.ttt Dequeue for major name [002] and minor name [003]

Explanation: This is an informational message. The named resource is about to be dequeued.




SLR0045ESLR0045E hh:mm:ss.ttt Dequeue failed. RC [002]

Explanation: A DEQ failed. [002] can be:

>0 Original return code from DEQ macro; see SA22-7609-xx: MVSProgramming: Authorized Assembler Services Reference, Volume 1(ALE-DYN)

-4 Invalid function

-8 Invalid type

-12 Invalid scope

-16 Invalid length for minor name



Determine why the DEQ failed. If necessary, contact SupportLine.

SLR0046ISLR0046I hh:mm:ss.ttt Dequeue successful




SLR0047ISLR0047I ====================================================================== Initiator Information ======================================================================


Issued by: TAURIP77


SLR0048ISLR0048I Class : [001] Dedicated initiators : [002] Allocated initiators : [003] Used initatiors : [004]


Issued by: TAURIP77



SLR0049ISLR0049I hh:mm:ss.ttt Job prefix : [002] Job search string : [003] Scheduler table : [004] Parallel user servers allowed : [005] Handle ISPF statistics : [006]


Issued by: TAURIP74


SLR0050ESLR0050E hh:mm:ss.ttt No console defined. Checking of ports or initiators will be disabled.


Issued by: TAURIP18


SLR0051ESLR0051E hh:mm:ss.ttt [002] Ports defined, but only [003] initiators are dedicated to class [004]. Startup of server terminated.



SLR0052ESLR0052E hh:mm:ss.ttt All [002] initiators are in use. User server for [003] not submitted.


Issued by: TAURIP53


SLR0053WSLR0053W hh:mm:ss.ttt More than 80% of [002] initiators are in use.



SLR0054ISLR0054I TSOE_Initcheck..................................: [001]




SLR0055ESLR0055E hh:mm:ss.ttt Port [002] is not available.

Explanation: The required port is not available for either a user server or scheduler to start. Thismessage is issued to the operator console. More information can be found in one ofthe DD statements T000000x in job log. If the port check function is active, thecommand response to a NETSTAT command will be visible in hardcopy log.

Issued by: TAURIP53


Determine why the port is not available. If it is used by another product, change theport range of the server in both the scheduler and the holder configuration file.

SLR0056ESLR0056E hh:mm:ss.ttt Invalid console command for initiator check. Startup of server terminated.



SLR0057ISLR0057I hh:mm:ss.ttt Submit count for user [002] set to [003]



SLR0058ISLR0058I hh:mm:ss.ttt Message was not routed due to <ROUTEMSG>N</ROUTEMSG>



SLR0059ESLR0059E hh:mm:ss.ttt Error in XML document. Not all elements for PUTVAR or DELVAR specified. PUTVAR requires VARTYPE, VARNAME and VARTEXT DELVAR requires VARTYPE and VARNAME


User response: Correct the XML document sent.

SLR0060ESLR0060E hh:mm:ss.ttt Variable for JOB not found. Check message SPR0007E




SLR0061ESLR0061E hh:mm:ss.ttt Logon not valid. Userid and/or password missing.


User response: Repeat the logon with a correct user ID and password.

SLR0062ESLR0062E hh:mm:ss.ttt [002] for Userid [003] was not successful. Reason : [004] hex.

Explanation: This message is issued if a RACINIT or RACROUTE with REQUEST=VERIFYwas not successful. [002] contains the API command used, for instance VERIFYLOGON. [003] contains the user ID. Refer to SA22-7692-xx RACROUTE MacroReference for the meaning of [004].

Issued by: TAURIP78


Determine why RACINIT or RACROUTE failed.

SLR0063ESLR0063E hh:mm:ss.ttt Password/newPassword for Userid [002] is invalid. Password must be hexadecimal Password may have a length of 16 bytes Password must be DES encrypted


Issued by: TAURIP75

User response: Use a valid XML document with correct length and valid characters.

SLR0064ISLR0064I hh:mm:ss.ttt Password hexadecimal : [002] Password encrypted : [003] Password decrypted : [004]

Explanation: This is an informational message due to IPTRACE level 4 being set and refers todeprecated functionality.


SLR0065ESLR0065E hh:mm:ss.ttt Input message for TSO/E scheduler must be an XML document


User response: Specify a valid XML document.

SLR0066ESLR0066E hh:mm:ss.ttt An XML document for a TSOE/E scheduler must start with the root element <TSOSCHED>




SLR0067ESLR0067E hh:mm:ss.ttt Attributes missing for element <ROUTEMSG>


Issued by: TAURIP78

User response: Specify a correct <ROUTEMSG> element.

SLR0068ISLR0068I hh:mm:ss.ttt Calling program [002] with command [003]




SLR0069ESLR0069E hh:mm:ss.ttt Stop or logoff command for user [002] unsuccessful. RSN : [003]



SLR0070ISLR0070I hh:mm:ss.ttt Verify for userid [002] successful


Issued by: TAURIP78


SLR0071ESLR0071E hh:mm:ss.ttt Verify for userid [002] unsuccessful. RSN [003]

Explanation: The security check failed; see SA22-7692-xx: Security Server RACROUTE MacroReference for details.

The hexadecimal reason code can be:

04 The user profile is not defined to RACF

08 The password is not authorized

0C The password has expired

10 The new password is not valid

14 The user is not defined to the group

Issued by: TAURIP78



Determine why the security check failed. If necessary, contact SupportLine.

SLR0072ESLR0072E hh:mm:ss.ttt Changed password invalid. Specify Userid, old password and new password.


User response: Retry the password word with all required values: User ID, old password, newpassword.

SLR0073ESLR0073E hh:mm:ss.ttt Password change for userid [002] unsuccessful. RSN [003]

Explanation: Self-explanatory. [003] is the RACF reason code.

Issued by: TAURIP78


Determine why the password change was unsuccessful. If necessary,contact SupportLine.

SLR0074ISLR0074I hh:mm:ss.ttt Password change for userid [002] successful


Issued by: TAURIP78


SLR0077ISLR0077I hh:mm:ss.ttt Wait for [002] ms done.

Explanation: This is an informational message in response to an API call.

Issued by: TAURIP78


SLR0078ESLR0078E hh:mm:ss.ttt Command [002] for server [003] not processed. RSN : [004]


Issued by: TAURIP78


SLR0079ESLR0079E hh:mm:ss.ttt Unexpected return code [002] from user administration

Explanation: See message HLD0030I for an explanation of the return code.


Issued by: TAURIP53, TAURCEA


Determine why the return code was issued. If necessary, contactSupportLine.

SLR0080ESLR0080E hh:mm:ss.ttt This server only accepts messages routed from a TSO/E scheduler


Issued by: TAURIP73

System administrator response: Correct the configuration; see ROUTE_ONLY in the z/ServerInstallation Guide.

SLR0081ISLR0081I hh:mm:ss.ttt User server policy is: [002]


Issued by: TAURIP74


SLR0082ESLR0082E hh:mm:ss.ttt Invalid value for TSOE_U_POLICY. Valid values are: 0 : Start user server with a job 1 : Start user server with a started job 2 : Start user server ISPF client gateway 4 : Start user server with a started task


Issued by: TAURIP18


SLR0083ISLR0083I hh:mm:ss.ttt User server control utility called with command [002]

Explanation: This is an informational message due to IPTRACE level 4 being set. [002] is one of thefollowing: LOGON, LOGOFF, ADDUSRV, RESTART, VERIFY.

Issued by: TAURIP53


SLR0084ESLR0084E hh:mm:ss.ttt No response from user server [002] for [003] seconds. Connection terminated due to timeout.

Explanation: A command was issued to the user server [002] that did not send back aresponse within the DIALOG_TIMEOUT configuration parameter.

Issued by: TAURIP78


Either retry the connection or specify a higher value for DIALOG-TIMEOUT.


SLR0085ESLR0085E hh:mm:ss.ttt If more than one user server is allowed the policy must be a started job or CEA. TSOE_U_POLICY=1 or TSOE_U_POLICY=8


Issued by: TAURIP18


SLR0086ISLR0086I hh:mm:ss.ttt [002] user servers found for userid [003]


Issued by: TAURIP27


SLR0087ESLR0087E hh:mm:ss.ttt Maximum number of user servers for user [002] reached.

Explanation: The maximum number of user servers is determined by the port range specifiedusing TSOE_FIRST_PORT and TSOE_LAST_PORT. Each user server will get aport assigned in that range. No more ports are left.

Issued by: TAURIP53


Increase the port range by increasing TSOE_FIRST_PORT andTSOE_LAST_PORT in the scheduler configuration and DSP_PORT_LOW andDSP_PORT_HIGH in the holder configuration, if necessary. Restart the scheduleror both the scheduler and the holder task.

SLR0088ESLR0088E hh:mm:ss.ttt User table is full. Increase portrange for server.

Explanation: The maximum number of user servers is determined by the port range specifiedusing TSOE_FIRST_PORT and TSOE_LAST_PORT. Each user server will get aport assigned in that range. No more entries are left in the user table.

Issued by: TAURIP27


Increase the port range by increasing TSOE_FIRST_PORT andTSOE_LAST_PORT in the scheduler configuration and DSP_PORT_LOW andDSP_PORT_HIGH in the holder configuration, if necessary. Restart the scheduleror both the scheduler and the holder task.

SLR0089ESLR0089E hh:mm:ss.ttt Command ADDUSRV is only allowed for policy started jobs.


Issued by: TAURIP53



SLR0090ESLR0090E hh:mm:ss.ttt Timeout or Timeout_Action are not allowed for a TSO/E scheduler. Startup aborted.

Explanation: TIMEOUT_ACTION is a deprecated keyword.

Issued by: TAURIP18


Correct the configuration; a scheduler configuration file must notcontain the parameter TIMEOUT.

SLR0091ESLR0091E hh:mm:ss.ttt For Timeout_Action = STOP the user administration must be in a common access data space

Explanation: TIMEOUT_ACTION is a deprecated keyword.

Issued by: TAURIP18

System administrator response: Remove the keyword from the configuration file.

SLR0092ESLR0092E hh:mm:ss.ttt User servers with TIMEOUT_ACTION=STOP must be started with POLICY=1 (Started task). Timeout is ignored.

Explanation: The original message referred to deprecated functionality. Today, a user server canno longer terminate if it is not recognized in the user administration controlstructures. The user server issuing this message has somehow disappeared fromthe user administration control structures and so cannot terminate. This messageis issued to the operator console.

Issued by: TAURIP27


Determine why the user server is not present in the user administration controlstructures. If necessary, contact SupportLine.

SLR0093ESLR0093E hh:mm:ss.ttt Bad RC [002] from user administration for set timeout. Timeout is ignored. User server continues with bad performance


Issued by: TAURIP00


SLR0094ESLR0094E hh:mm:ss.ttt User server [002] for user [003] is no longer active due to timeout.


Issued by: TAURIP78



SLR0095ESLR0095E hh:mm:ss.ttt Restart of user server for [002] on port [003] failed with RC [004].

Explanation: When (re)starting the user server, a failure was encountered. RC [004] can be:

4 ASCB NOT FOUND

8 VAB NOT FOUND

C CAUB NOT FOUND

10 JOBNAME NOT VALID

ASCB, VAB and CAUB are z/OS control block names.

Issued by: TAURIP78


Determine why the restart failed. If necessary, contact SupportLine.

SLR0096ESLR0096E hh:mm:ss.ttt Restart for port [002] not possible. No timeout entry found.

Explanation: A user server is requested to be started at port [002]. Restarting a user server isonly possible if there is a so-called timeout entry (STCTIMEO) in the useradministration control structures. No such entry was found.

Issued by: TAURIP78


Determine why there is no timeout entry or start a user server instead ofrestarting it.

SLR0097ESLR0097E hh:mm:ss.ttt No port for RESTART specified.

Explanation: This message is issued in response to an API call. Restart without a port specificationis only possible when there is exactly one user server running for a user. In all othercases the port number must be specified, too.

User response: Specify a port number for the RESTART command.

SLR0098ESLR0098E hh:mm:ss.ttt Port for RESTART not numeric or has more than 5 digits.

Explanation: This message is issued in response to an API call. The specified port is invalid.

User response: Specify a valid port number.

SLR0099ESLR0099E hh:mm:ss.ttt [002] XML document does not contain a valid command for a TSO/E scheduler


Issued by: TAURIP78


User response: Specify a correct XML document.

SLR0100ESLR0100E hh:mm:ss.ttt Size of extra buffer with [002] bytes is too small to hold all output from XML document.


Issued by: TAURIP78


SLR0101ISLR0101I hh:mm:ss.ttt Extra buffer for multiple XML images allocated at address [002]


Issued by: TAURIP78


SLR0102WSLR0102W hh:mm:ss.ttt User administration not in a dataspace. Command ignored.

Explanation: This message is issued to the operator console and refers todeprecated functionality.

Issued by: TAURIP27


SLR0103ESLR0103E hh:mm:ss.ttt If more than one user server is running ROUTEMSG requires the specification of a PORT

Explanation: This message is issued in response to an API call. Restart without a port specificationis only possible when there is exactly one user server running for a user. In all othercases the port number must be specified, too.

Issued by: TAURIP78

User response: Specify a port number for the RESTART command.

SLR0104ESLR0104E hh:mm:ss.ttt No user server on port [002] found for user [003]

Explanation: This message is issued in response to an API call if either the specified port or thespecified user is not found in the user administration control structures.

Issued by: TAURIP78

User response: Use the GETPORT command to get all active ports for a user. Then issue the commandspecifying the appropriate port.


SLR0105ESLR0105E hh:mm:ss.ttt User server on port [002] belongs to user [003] and is invalid for [004]

Explanation: This message is issued in response to an API call with invalid parameters. The userserver [003] listens on port [002], while the API call assumes that port [002] belongs touser server [004] according to the user administration control structures.

Issued by: TAURIP78

User response: Use a valid port / user server combination.

SLR0106ESLR0106E hh:mm:ss.ttt A deferred LOGON is only allowed for started jobs.


Issued by: TAURIP78


SLR0107ISLR0107I hh:mm:ss.ttt Deferred LOGON for user [002] successful


Issued by: TAURIP53


SLR0108ESLR0108E hh:mm:ss.ttt Load of XML exit [002] failed. MSG : [003]

Explanation: This message is issued in response to an API call. The specified XML exitprogram to be used for parsing could not be loaded. [003] is the original LEerror message.

Issued by: TAURIP78


Check that the specified XML exit program is contained in an accessible loadlibrary; if necessary, contact SupportLine.

SLR0109ISLR0109I hh:mm:ss.ttt Calling XML exit [002]


Issued by: TAURIP78


SLR0110ISLR0110I hh:mm:ss.ttt XML exit [002] ended. RC [003]



Issued by: TAURIP78


SLR0111ISLR0111I hh:mm:ss.ttt TSO/E scheduler initialization/termination routine called with function [002]


Issued by: TAURIP74


SLR0112ESLR0112E hh:mm:ss.ttt Initialization/termination exit for TSO/E scheduler failed for function [002]. RC [003]

Explanation: The exit failed, so the user server is not started. This message is issued tothe operator console. See message HLD0030I for an explanation of the returncode [003].

Issued by: TAURIP74


Determine why the exit failed. If necessary, contact SupportLine.

SLR0113ISLR0113I hh:mm:ss.ttt [002] for port [003] and user [004] successful.

Explanation: This is an informational message. [002] is the server command issued to the userserver [004] on port [003].

Issued by: TAURIP78


SLR0114ESLR0114E hh:mm:ss.ttt Load of command exit [002] for [003] failed. MSG : [004]

Explanation: This message is issued in response to an API call. The specified program to beused as a command exit could not be loaded. [003] is the command to beexecuted, [004] is the original LE error message.

Issued by: TAURIP78


Check that the named program is contained in an accessible load library; ifnecessary, contact SupportLine.

SLR0115ISLR0115I hh:mm:ss.ttt Calling command exit [002] for [003] at address [004]


Issued by: TAURIP78



SLR0116ISLR0116I hh:mm:ss.ttt Command exit [002] ended. RC [003]


Issued by: TAURIP78


SLR0117ESLR0117E hh:mm:ss.ttt Command [002] not executed due to command exit

Explanation: A command exit prevented the command [002] from being executed.

Issued by: TAURIP78

User response: If tracing is active, check the return code from the command exit. Otherwise, reproducethe problem with tracing active.

SLR0118ESLR0118E hh:mm:ss.ttt Deletion of [002] failed RSN : [003]

Explanation: The specified program [002] failed to be deleted. The reason code fromCEERELES is [003]; see SA22-7561-xx: Language EnvironmentProgramming Guide

Issued by: TAURIP78


Determine why CEERELES failed. If necessary, contact SupportLine.

SLR0119ESLR0119E hh:mm:ss.ttt Command [002] is only allowed for a class 2 scheduler.


Issued by: TAURIP78

System administrator response: Correct the configuration; see TSOE_SCHEDULER in the z/ServerInstallation Guide.

SLR0120ESLR0120E hh:mm:ss.ttt No more than 10 slaves allowed.


Issued by: TAURIP18


SLR0121ESLR0121E hh:mm:ss.ttt Dataspace required to initiate slaves.


Issued by: TAURIP18



SLR0122ESLR0122E hh:mm:ss.ttt Slaves only allowed for a class 1 scheduler.


Issued by: TAURIP18


SLR0123ESLR0123E hh:mm:ss.ttt A slave is required to execute command [002] but no slaves are defined.


Issued by: TAURIP78


SLR0124ESLR0124E hh:mm:ss.ttt No configuration file for slaves defined.


Issued by: TAURIP18


SLR0125ESLR0125E hh:mm:ss.ttt Only a master server can create slaves.


Issued by: TAURIP18


SLR0126ISLR0126I hh:mm:ss.ttt Routing message for command [002] to slave on port [003] Length of message : [004]

Explanation: This is an informational message due to IPTRACE level 4 being setand refers to deprecated functionality.

Issued by: TAURIP78



SLR0127ESLR0127E hh:mm:ss.ttt Slaves are only allowed if a server is a started task


Issued by: TAURIP18



SLR0128ESLR0128E hh:mm:ss.ttt No proc for slaves defined


Issued by: TAURIP18


SLR0129ESLR0129E hh:mm:ss.ttt KILL is not allowed for jobs.


Issued by: TAURIP78


SLR0130ESLR0130E hh:mm:ss.ttt User server for user [002] and port [003] has an invalid combination for timeout and jobid.

Explanation: Part of this message refers to deprecated functionality. Either the user serveraddress space was not started with the parameter TSOE_USER=1 or the userserver did not set the READY flag in the user administration control structures.

Issued by: TAURIP53


Check whether the configuration file for user servers contains TSOE_USER=1 orwhy the READY flag wasn't set.

SLR0131ESLR0131E hh:mm:ss.ttt User server did not signal READY after a wait period of 10 X [002] ms. Command was not routed to the user server.

Explanation: This message is normally issued when the user server has not marked itself readyyet in the user administration control structures. After the named amount ofmilliseconds (configuration parameter TSO_DELAY_SUBMIT) the scheduler informsthe client of this and asks the client to retry later.

Issued by: TAURIP78


Determine why the user server did not signal itself ready. This may be due to toomuch CPU load on the z/OS system or wrong WLM settings for user servers.

SLR0132ESLR0132E hh:mm:ss.ttt TSOE_DELAY_SUBMIT must be at least 1000 ms for a policy uneven JOB.

Explanation: The configuration parameter TSO_DELAY_SUBMIT must be at least1000.


Issued by: TAURIP18


Define at least TSOE_DELAY_SUBMIT=1000 in the configuration.

SLR0134ESLR0134E hh:mm:ss.ttt User server with jobid [002] for user [003] was stopped without logoff. Port entry is cleared


Issued by: TAURIP78


Determine if the user server had other problems before this message was issued.If necessary, contact SupportLine. The clearing of the port entry may mean thatthe user server is then unable to terminate itself because its entry in the useradministration control structures is gone (msgSLR0092E).

SLR0135SSLR0135S hh:mm:ss.ttt Port [002] for z/Server scheduler [003] locked because port was not available.

Explanation: This message is issued to the operator console.

Issued by: TAURIP27


Determine why the port has become unavailable. If necessary,contact SupportLine.

SLR0136ISLR0136I hh:mm:ss.ttt Port [002] for z/Server scheduler [003] is now unlocked and available for use.


Issued by: TAURIP77


SLR0137ESLR0137E hh:mm:ss.ttt Port [002] for z/Server scheduler [003] is not locked.

Explanation: The port specified in the unlock command is not locked and cannotbe unlocked.

Issued by: TAURIP77

System administrator response: Specify a locked port.

SLR0139ESLR0139E hh:mm:ss.ttt Port [002] for unlock is not within portrange of scheduler [003].

Explanation: The port specified in the unlock command is not in the port range belongingto the scheduler addressed and cannot be unlocked.

Issued by: TAURIP77



Specify the command to the scheduler that owns the port.

SLR0140ESLR0140E hh:mm:ss.ttt Scheduler [002] is locked. Start of user server is disabled.

Explanation: This message is issued to the operator console in response to a lockoperator command.

Issued by: TAURIP27


Determine why the scheduler is locked. If necessary, unlock it.

SLR0141ESLR0141E hh:mm:ss.ttt Unable to resolve port for ASID [002]

Explanation: During startup, the user server attempts to resolve its port using the useradministration control structures, which was unsuccessful.

Issued by: TAURIP18


Determine why the port could not be resolved. If necessary, contactSupportLine.

SLR0142ISLR0142I hh:mm:ss.ttt Asid [002] is using port [003]


Issued by: TAURIP18


SLR0143ISLR0143I hh:mm:ss.ttt Resolving port for ASID [002] using data space


Issued by: TAURIP18


SLR0144ESLR0144E hh:mm:ss.ttt Limited server can only be stopped or started through a holder task

Explanation: An operator tried to stop a scheduler with stop command. The scheduler isdefined as limited (LIMITED_SERVER=1).

Issued by: TAURIP04


Use F <holder>,STOP,SCHED=<scheduler>instead.


SLR0145ESLR0145E hh:mm:ss.ttt User server is running without a corresponding entry in the user administration. This server is not adminstered and therefore was terminated.

Explanation: A running user server had no entry in the user administration. Becausethis situation is not consistent, the running user server is terminated.

Issued by: TAURIP27


None.

SLR0146ISLR0146I hh:mm:ss.ttt Call to REXX [002] ended. RC [003] (hex)


Issued by: TAURIP78


SLR0148ESLR0148E hh:mm:ss.ttt POST CEATASK can only be used in a user server started with policy 8 (CEA)

Explanation: A client had sent a message with the POST CEATASK request, but the user serverdoes not belong to a scheduler started with TSOE_U_POLICY=8.

Issued by: TAURIP78

User response: Connect to a scheduler that allows the function "Launch ISPF".

SLR0149ESLR0148E hh:mm:ss.ttt POST CEATASK not processed because CEATASK is already busy.

Explanation: A client had sent an INITIALIZE_CEA_DIALOG request, but CEATASK is already busy.

Issued by: TAURIP78

User response: INITIALIZE_CEA_DIALOG can only be sent once. Contact SupportLine.

SLR0150ESLR0148E hh:mm:ss.ttt Givesocket for CEATASK failed Return code ...... : [002] (hex) Reason code .......: [003] (hex)

Explanation: A client had sent an INITIALIZE_CEA_DIALOG request, but the GIVESOCKET requestfor CEATASK failed.

Issued by: TAURIP78

User response: Restart the user server address space with trace level 6 set in the configuration file. Ifthe error persists, contact SupportLine and provide the trace output.


SLR0155ESLR0155E hh:mm:ss.ttt Initialization of the CEA dialog is only allowed for a user server with policy 8.

Explanation: The client requested an initialization for a CEA dialog, but the owningscheduler was not started with policy=8 (CEA).

Issued by: TAURIP73


Start the scheduler with policy=8 (CEA).

SPR - Standard Pool RoutineThe standard pool routine processes variables similar to the ISPF dialog manager.

SPR0001ISPR0001I hh:mm:ss.ttt Standard pool routine called with Function : [002] Variable type : [003] Variable name : [004] Variable content : [005]


Issued by: TAURIP20


SPR0002ESPR0002E hh:mm:ss.ttt Standard pool routine called with invalid Function. Function : [002]

Explanation: Self-explanatory. Valid functions are:

VPUT Write variable

VGET Read variable

VDEL Delete variable

User response: Specify a valid function.

SPR0003ESPR0003E hh:mm:ss.ttt Variable pool is too small to hold all variables. Current size is [002]


Issued by: TAURIP20

User response: Increase the size of the variable pool. See VPOOLSIZE in the z/Server InstallationGuide.

SPR0004ISPR0004I hh:mm:ss.ttt Variable found in pool at entry [002] FindFlag : [003]


Address : [004] Entry length : [005]

Explanation: This is an informational message due to IPTRACE level 4 being set. Find flag [003] canbe:

X'01' Variable found

X'02' Variable contains the same content

X'04' The length of the content is equal

Issued by: TAURIP20


SPR0005ISPR0005I hh:mm:ss.ttt Variable [002] found for substitution


Issued by: TAURIP20


SPR0006ISPR0006I hh:mm:ss.ttt Variable [002] contains [003]


Issued by: TAURIP19


SPR0007ESPR0007E hh:mm:ss.ttt Variable [002] not found in variable pool


Issued by: TAURIP19

User response: Specify a valid variable name.

SPR0008WSPR0008W hh:mm:ss.ttt Result after substitution [002] bytes greater than input buffer. Result is truncated.


Issued by: TAURIP19


SPR0009ESPR0009E hh:mm:ss.ttt No variable pool defined.


Issued by: TAURIP20


User response: Define a variable pool using the VPOOLSIZE configuration parameter.

SPR0010SSPR0010S hh:mm:ss.ttt Enqueue for variable pool failed. Please contactyour System administrator.


Issued by: TAURIP20

System administrator response: Determine why the enqueue failed. If necessary, contact SupportLine.

SPR0011ISPR0011I Address of pool : [001] Size : [002] Freespace : [003] Bytes Number of variables : [004] Bytes Variable pool information =========================== Pool content ======================== Type Name Content =================================================================

Explanation: The pool statistics are returned.

Issued by: TAURIP77


SPR0012ISPR00012I hh:mm:ss.ttt Variable pool not defined.

Explanation: The variable pool used is not defined.

Issued by: TAURIP77

User response: Use an existing variable pool.

SPR0013ISPR00013I [001] [002] [003]

Explanation: The type ([001]), name ([002]), and content ([003]) of the variable are listed.

Issued by: TAURIP77


SPR0014ISPR00014I hh:mm:ss.ttt Datastream before substitution. Length : [002]


Issued by: TAURIP19



SPR0015ISPR00015I hh:mm:ss.ttt Datastream after substitution. Length : [002]


Issued by: TAURIP19


SPR0016ISPR00016I [001]

Explanation: The VGET content is listed.

Issued by: TAURIP75


SRV - Server InterfaceThese message are issued for both scheduler and user server.

SRV0001ISRV0001I hh:mm:ss.ttt z/Server SRVTASK is initializing


Issued by: TAURIP16


SRV0002ISRV0002I hh:mm:ss.ttt SRVTASK was posted.


Issued by: TAURIP16


SRV0003ESRV0003E hh:mm:ss.ttt Subtask [002] TCB [003] consumed more than [004] ms of CPU time. Subtask will be terminated.

Explanation: The service task can in certain circumstances check the CPU consumption foranother subtask. If the value specified by TASK-RUNAWAY is reached orexceeded, the service task will terminate the subtask to prevent CPU loops.

Issued by: TAURIP16


Check the REXX or program running in that subtask for loops. If none were found,increase TASK_RUNAWAY if necessary or turn it off altogether.


SRV0004WSRV0004W hh:mm:ss.ttt CPU consumption check is disabled. Possible loops are not detected.

Explanation: The service task can in certain circumstances check the CPU consumption foranother subtask. The configuration parameter TASK-RUNAWAY determines ifthe check is disabled or running.

Issued by: TAURIP16


Specify TASK_RUNAWAY to enable the check. Otherwise this is aninformational message.

SRV0005ISRV0005I hh:mm:ss.ttt Using service exit [002]


Issued by: TAURIP16


SRV0006ISRV0006I hh:mm:ss.ttt Calling service exit [002]


Issued by: TAURIP16


SRV0007ISRV0007I hh:mm:ss.ttt Checking for outstanding messages and command responses from EMCS console [002]


Issued by: TAURIP16


SRV0008ISRV0008I hh:mm:ss.ttt Calling initial REXX [002]


Issued by: TAURIP16


SRV0009ISRV0009I hh:mm:ss.ttt Initial REXX [002] ended. RC [003]


Issued by: TAURIP16



SRV0010ISRV0010I hh:mm:ss.ttt ----------------------------------------------------- Check for locked ports -----------------------------------------------------

Explanation: This is an informational message due to IPTRACE level 5 being set. The service taskchecks for locked ports in the user administration.

Issued by: TAURIP06


SRV0011ESRV0011E hh:mm:ss.ttt Port [002] for server [003] remains locked

Explanation: SRVTASK detected a locked port. It has checked the port, which is still in use..The port remains locked.

Issued by: TAURIP06


Check DDNAME SYSTSPRT of scheduler [003] and check who is using theport.Or issue a D,TCPIP,,N,ALLCONN,PORT=[002] command.

SRV0012ISRV0012I hh:mm:ss.ttt Port [002] for server [003] unlocked

Explanation: SRVTASK detected a locked port. It checked the port, and it is nolonger in use. The port is unlocked.

Issued by: TAURIP06


None.

SRV0013ISRV0013I hh:mm:ss.ttt Delay interval is [002] seconds.

Explanation: This is an informational message due to IPTRACE level 4 being set. The messageshows the setting of the configuration variable SERVICE_WAIT.

Issued by: TAURIP06


SSI - Subsystem Interface RoutineThese messages are issued by the interface routine to the z/OS subsystem interface (SSI).

SSI0001ISSI0001I hh:mm:ss.ttt SSI call Type : [002] SVC RC : [003] SSI RC : [004] SSI RSN1 : [005] SSI RSNI2 : [006]




SSI0002ISSI0002I hh:mm:ss.ttt Pointer to output (STATJOBF) : [002] Number of matching jobs : [003]




SSI0003ISSI0003I hh:mm:ss.ttt Pointer to next SJQE : [002] Pointer to SJQE sysout : [003]



SSI0004ISSI0004I hh:mm:ss.ttt Section length/type/modifier [002]/[003]/[004]



SSI0005ISSI0005I hh:mm:ss.ttt ========================================================= Storage for SSOB =========================================================



SSI0006ISSI0006I hh:mm:ss.ttt ========================================================= Storage for SSST =========================================================



SSI0007ISSI0007I hh:mm:ss.ttt ========================================================= JQE terse section =========================================================




SSI0008ISSI0008I ======================================================================= Storage for [001] =======================================================================




SSI0009ISSI0009I ======================================================================= Storage for section len : [001] type : [002] modifier : [003] =======================================================================




STA - Started Task Interface

STA0001ESTA0001E hh:mm:ss.ttt Invalid value [002] for environment variable TSOE_SCHED_TAB. Valid values are : 0 : Table is in task storage 1 : Table is in shared storage (common data space)

Explanation: This message refers to deprecated parameters.


Issued by: TAURIP18

STA0002ESTA0002E hh:mm:ss.ttt Invalid function [002] for scheduler table routine



STA0003ISTA0003I hh:mm:ss.ttt TSO/E scheduler table routine called with function [002]





STA0004ESTA0004E hh:mm:ss.ttt Name of name/token pair is not specified


Issued by: TAURIP18

System administrator response: Check the configuration files and specify TSOE_DSP_TOKENappropriately.

STA0005ESTA0005E hh:mm:ss.ttt Read of name/token pair [002] failed with RC [003] (hex).

Explanation: The search for a token failed; see SA22-7610-xx:MVS Programming:Authorized Assembler Services Reference, Volume 2 (EDT-IXG) for details onthe return code (IEANTRT service).

Issued by: TAURIP18


Determine why the search failed. If necessary, contact SupportLine.

STA0006ISTA0006I hh:mm:ss.ttt Value of name/token pair [002] DSPALET : [003] DSPORIGIN : [004] DSPBLOCK : [005] DSPFLAGS : [006]


Issued by: TAURIP18


STA0007ESTA0007E hh:mm:ss.ttt Name of name/token pair for console is not specified.



STA0008ESTA0008E hh:mm:ss.ttt Failed to resolve port for JOBID [002].

Explanation: A user server was started and the required entry was not found in the useradministration.

Issued by: TAURIP83

User response: Contact SupportLine.

TAU - Eclipse Client Interface


TAU0001ITAU0001I [001] [002] [003] startup [004]


[001] Product name

[002] Job name

[003] Version level

[004] Date and time


Issued by: TAURIP02

TAU0002ITAU0002I hh:mm:ss.ttt Address of handler communication area : [002]



TAU0003ITAU0003I hh:mm:ss.ttt Address of server communication area: [002]


Issued by: TAURIP02


TAU0004ITAU0004I hh:mm:ss.ttt Socket server is using the following values Maximum number of subtasks : [002] Maximum number of sockets : [003] Listening on port : [004] Timeout for IPWAIT : [005] seconds Name of IP stack : [006] PPT : [007] Dump if API fails : [008] MULTI_ REXX : [009]


Issued by: TAURIP02


TAU0005ITAU0005I hh:mm:ss.ttt Address of subtask storage table : [002] A(ECB wait list for subtask) : [003] A(ECB post list for subtask) : [004]


Issued by: TAURIP02



TAU0006ITAU0006I hh:mm:ss.ttt Client [002] connected on port [003] desc [004]

Explanation: This is an informational message. [004] is the IP descriptor.

Issued by: TAURIP00


TAU0007ETAU0007E hh:mm:ss.ttt Error during EZASOKET processing Function : [002] RSN : [003]

Explanation: See SC31-8788-xx: IP Sockets Application Programming Interface Guideand Reference for details.



Determine why the EZASOCKET call failed. If necessary, contactSupportLine.

TAU0008ITAU0008I hh:mm:ss.ttt Subtask [002] for z/Server is initializing


Issued by: TAURIP02


TAU0009ETAU0009E hh:mm:ss.ttt No free ECB available. Waiting for next free ECB.

Explanation: There is no subtask available for handling the incoming request.

Issued by: TAURIP00


If this message is issued frequently, increase NUMTCB in the schedulerconfiguration file. Otherwise retry later. If necessary, contact SupportLine.

TAU0010ITAU0010I hh:mm:ss.ttt Subtask [002] started A(TCB): [003] A(ECB) : [004]


Issued by: TAURIP00


TAU0011ITAU0011I hh:mm:ss.ttt Subtask [002] posted A(TCB): [003] A(ECB) : [004]


Issued by: TAURIP00



TAU0012ETAU0012E hh:mm:ss.ttt Timeout for takesocket after [002] seconds


Issued by: TAURIP00

User response: This can happen if IP traffic is very high. Retry the request.

TAU0013ITAU0013I hh:mm:ss.ttt Client IDs are [002] and [003]



TAU0014ITAU0014I hh:mm:ss.ttt Detaching subtask [002]. TCB [003] with ECB [004]


Issued by: TAURIP00


TAU0015ITAU0015I hh:mm:ss.ttt Before call [002]




TAU0016ITAU0016I hh:mm:ss.ttt [002] bytes received



TAU0017ITAU0017I hh:mm:ss.ttt About to send [002] bytes to client



TAU0018ITAU0018I hh:mm:ss.ttt There are [002] bytes available for receive.




TAU0019WTAU0019W hh:mm:ss.ttt Environment variable [002] was not specified, using defaults.


Issued by: TAURIP18

System administrator response: Verify that the default is sufficient. Otherwise, correct theconfiguration file.

TAU0020ETAU0020E hh:mm:ss.ttt Configuration parameter [002] value >>[002]<< has invalid length or is not numeric.


Issued by: TAURIP18

System administrator response: Correct the configuration file for parameter [003].

TAU0021ITAU0021I hh:mm:ss.ttt Converting message from ASCII to EBCDIC



TAU0022ITAU0022I hh:mm:ss.ttt Converting message from EBCDIC to ASCII



TAU0023ITAU0023I hh:mm:ss.ttt Subtask for z/Server activated


Issued by: TAURIP01


TAU0024ITAU0024I hh:mm:ss.ttt Highest socket number assigned to server is [002]


Issued by: TAURIP00


TAU0025ITAU0025I hh:mm:ss.ttt Subtask input message area at [002] Subtask output message area at [003]


Subtask work message area at [004] Each area is [005] bytes long Subtask PIMA area at [006] PIMA area is [007] bytes long Subtask ECI table at [008]


Issued by: TAURIP02


TAU0026WTAU0026W hh:mm:ss.ttt Command >>[002]<< invalid.


Issued by: TAURIP73


Determine why an invalid command was issued. If necessary, contactSupportLine.

TAU0027ETAU0027E hh:mm:ss.ttt Deletion of module [002] was not successful RSN : [003]

Explanation: See SA22-7606-xx: MVS Programming: Assembler Services Reference,Volume 1 (ABEND-HSPSERV) for [003], which is the original DELETEreturn code.

Issued by: TAURIP01


Determine why DELETE failed. If necessary, contact SupportLine.

TAU0028WTAU0028W hh:mm:ss.ttt Subtask [002] event has completed with completion code [003]

Explanation: The task with the name [002] was posted with post code [003], which is either a returncode or an ABEND code.

Issued by: TAURIP00


TAU0029ITAU0029I hh:mm:ss.ttt Load of module [002] was successful Entry point [003]




TAU0030ETAU0030E hh:mm:ss.ttt Load of module [002] was not successful System abend : [003] RSN : [004]


Explanation: See SA22-7626-xx: MVS System Codes for details of the original LOADfailure.

Issued by: TAURIP01


Determine why the ABEND occurred. If necessary, contact SupportLine.

TAU0031ETAU0031E hh:mm:ss.ttt Detach for subtask [002] was not successful. RC [003]

Explanation: See SA22-7606-xx: MVS Programming: Assembler Services Reference,Volume 1 (ABEND-HSPSERV) for [003], which is the original DETACH returncode. This is normally the value 4. The DETACH completed successfully, butmay be accompanied by a detach ABEND code.

Issued by: TAURIP00


If necessary, contact SupportLine.

TAU0032ETAU0032E hh:mm:ss.ttt IP stack not found. Waiting [002] seconds before retry.

Explanation: The named IP stack could not be found.

Issued by: TAURIP00


Verify the IPNAME parameter in the configuration file. If necessary,contact SupportLine.

TAU0033ETAU0033E hh:mm:ss.ttt Unexpected error in [002]. Server will be terminated

Explanation: Service [002] failed. If the service was EZASMI: See SC31-8788-xx: IPSockets Application Programming Interface Guide and Reference fordetails.

Issued by: TAURIP00


If necessary, contact SupportLine.

TAU0035ETAU0035E hh:mm:ss.ttt No valid method for receive is specified.


Issued by: TAURIP73

User response: Specify a valid receive method in the IP header.

TAU0036ITAU0036I hh:mm:ss.ttt Using method 1 for receive for [002] bytes




TAU0037ITAU0037I hh:mm:ss.ttt Using method 2 for receive until encountering [002]



TAU0038ITAU0038I hh:mm:ss.ttt Using method 3 for receive (single receive)



TAU0039ITAU0039I hh:mm:ss.ttt Socket server information Domain name local host : [002] IP address current host : [003] VIPA for internal usage : [004] IP address VIPA : [005]


Issued by: TAURIP00


TAU0040ETAU0040E hh:mm:ss.ttt Server startup terminated by [002]


Issued by: TAURIP00


TAU0042ITAU0042I hh:mm:ss.ttt Converting ASCII (UTF-8) header to EBCDIC header


Issued by: TAURIP73


TAU0043ETAU0043E hh:mm:ss.ttt IP ASCII data length or CCSID in ASCII header is not numeric


Issued by: TAURIP73

User response: Specify a valid data length in the IP header.


TAU0044ETAU0044E hh:mm:ss.ttt Error converting ASCII header to EBCDIC header. See message UNI001E.

Explanation: This message is issued in response to an API call using ASCII headers. ASCIIheaders need to be converted to EBCDIC headers. During this process a problemoccurred which is described in message UNI001E. UNI001E is found in theT000000x task that handled this API call.

Issued by: TAURIP73


Verify that the correct CCSID is used both in the scheduler and user serverconfiguration files and that they match the CCSID specified in the client. Ifnecessary, contact SupportLine.

TAU0045ITAU0045I hh:mm:ss.ttt Using method 4 for receive (via application)



TAU0046ITAU0046I hh:mm:ss.ttt Address of program property table (PPT): [002]


Issued by: TAURIP02


TAU0047STAU0047S hh:mm:ss.ttt PPT overflow : All [002] entries in use. Request terminated.


Issued by: TAURIP01


TAU0048WTAU0048W hh:mm:ss.ttt Client closed connection before all data was received. Message may be incomplete.


User response: Determine why the client closed the connection.

TAU0049WTAU0049W hh:mm:ss.ttt Timeout occurred before all data was received. Message may be incomplete.


Issued by: TAURIP01


User response: Determine why a timeout occurred.

TAU0050ETAU0050E hh:mm:ss.ttt Input message of length [002] bytes is greater than input buffer of [003] bytes. Increase BUFFERSIZE and restart server.


Issued by: TAURIP73

System administrator response: Verify the configuration file; see BUFFERSIZE/BUFFERUNIT in the z/Server Installation Guide.

TAU0051WTAU0051W hh:mm:ss.ttt Shutdown server


Issued by: TAURIP00


TAU0052ITAU0052I hh:mm:ss.ttt Setting length in header to [002]


Issued by: TAURIP01


TAU0053ITAU0053I hh:mm:ss.ttt Shutdown subtask


Issued by: TAURIP01


TAU0054STAU0054S hh:mm:ss.ttt Terminating subtask with dump


Issued by: TAURIP06

System administrator response: Contact SupportLine and provide the dump and all logs.

TAU0055ITAU0055I hh:mm:ss.ttt Entry point for program [002] disabled.


Issued by: TAURIP00



TAU0056ITAU0056I hh:mm:ss.ttt ISPF available : [002] Size of user area1 : [003] bytes Size of user area2 : [004] bytes Address of user area1 : [005] Address of user area2 : [006] Timeout for server : [007] minutes Reattach after abend : [008] 0 = No Serialize : [008]


Issued by: TAURIP02


TAU0057ETAU0057I hh:mm:ss.ttt TSO environment successfully created A(Command processor parameter list) : [002]



TAU0058ETAU0058E hh:mm:ss.ttt Creation of TSO environment failed RC : [002] RSN : [003] Abend code : [004]



Determine why the creation of the TSO-Environment failed. Ifnecessary, contact SupportLine.

TAU0059ITAU0059I hh:mm:ss.ttt [002] ended with RC [003]


Issued by: TAURIP01


TAU0060ITAU0060I hh:mm:ss.ttt Size of send/receive buffer : [002]/[003] PIMA size : [004] CICS EXCI support : [005] CICS EXCI applid : [006] Portcheck : [007] TSO/E scheduler : [008]


Issued by: TAURIP02



TAU0061ITAU0061I hh:mm:ss.ttt Variable pool size : [002] bytes A(variable pool) : [003] Use SVC : [004] SVC [005] Maximum number of user servers : [006] TSO/E user server : [007]


Issued by: TAURIP02


TAU0063STAU0063S hh:mm:ss.ttt Maxerr reached for program [002]. Program is disabled


Issued by: TAURIP01


TAU0064WTAU0064W hh:mm:ss.ttt Write length is zero. No data written.


Issued by: TAURIP01

User response: Determine if this is intentional behavior. If not, correct the write operation.

TAU0065ITAU0065I hh:mm:ss.ttt After call [002]. RC : [003] ERRNO : [004]




TAU0066ITAU0066I hh:mm:ss.ttt Address of IP global data area : [002]


Issued by: TAURIP00


TAU0067ITAU0067I hh:mm:ss.ttt startup completed for [002] for [003] and ASID [004]

Explanation: [002] is the name of the scheduler or user server which has just been started. [003]specifies JES2 or JES3 and [004] is the address space number.




TAU0068ITAU0068I hh:mm:ss.ttt New date : [002]




TAU0069ETAU0069E hh:mm:ss.ttt Function code [002] is not supported.


Issued by: TAURIP06


TAU0070ITAU0070I hh:mm:ss.ttt Deletion of module [002] completed with RC [003].


Issued by: TAURIP01


TAU0071ITAU0071I hh:mm:ss.ttt Kill request for task [002] received.

Explanation: This message is issued in response to an API call. [002] is the name of the task.

Issued by: TAURIP00


TAU0072WTAU0072W hh:mm:ss.ttt Connection is closed and no data is available




TAU0073STAU0073S hh:mm:ss.ttt Access Denied to $IPSERV [002]


Issued by: TAURIP01



TAU0074ITAU0074I hh:mm:ss.ttt Security : [002] Length of Header : [003] bytes Action for no free task : [004]


Issued by: TAURIP02


TAU0075WTAU0075W hh:mm:ss.ttt Access allowed to $IPSERV [002] because security is disabled


Issued by: TAURIP11


TAU0076ITAU0076I hh:mm:ss.ttt Flushing input buffer. [002] bytes available.


Issued by: TAURIP06


TAU0077ITAU0077I hh:mm:ss.ttt SVC for task level security invoked Function : [002] Userid : [003] SVC RC : [004] SAF RC : [005] RACF RC : [006] RACF RSN : [007]

Explanation: See SA22-7692-xx: Security Server RACROUTE Macro Reference for the functioncalled.

Issued by: TAURIP59


TAU0078ETAU0078E hh:mm:ss.ttt Creation of task level security was unsuccessful Return code was : [002]

Explanation: Return code [002] can be:

256 Invalid function code

300 User ID missing

304 Password missing

308 New password missing


400 Not TSO/E Scheduler

Issued by: TAURIP01


Determine why task level security could not be established successfully. Ifnecessary contact SupportLine.

TAU0079ETAU0079E hh:mm:ss.ttt SVC [002] not installed. Startup terminated.


Issued by: TAURIP02

System administrator response: Determine why the SVC routine could not be installed. If necessary,contact SupportLine.

TAU0080ETAU0080E hh:mm:ss.ttt Load of module [002] was unsuccessful. System completion code : [003] RSN : [004]


Issued by: TAURIP51


TAU0081ETAU0081E hh:mm:ss.ttt Unable to open internal reader. RC : [002]//READER DD SYSOUT=(*,INTRDR)


Issued by: TAURIP12


Determine why the internal reader could not be opened. Check forallocation of the DD statement in the scheduler procedure (TAURISPF):

TAU0082ETAU0082E hh:mm:ss.ttt I/O error on Internal reader. RC : [002]//READER DD SYSOUT=(*,INTRDR)


Issued by: TAURIP12


Determine why the I/O error on the internal reader occurred. Check forallocation of the DD statement in the scheduler procedure (TAURISPF):

TAU0083WTAU0083W hh:mm:ss.ttt A TSO/E environment already exists. An additional dynamic environment is not created.


Explanation: During startup, a scheduler or user server tests the availability of a TSO environment.That TSO environment is usually already available due to the way schedulers and userservers are started.


TAU0084ETAU0084E hh:mm:ss.ttt No or invalid method for calling exec [002]


Issued by: TAURIP01

User response: Specify a valid method for calling a REXX exec.

TAU0085ETAU0085E hh:mm:ss.ttt ISPF environment is not available. Unable to call exec [002]

Explanation: This message is issued in response to an API call which specified invocation ofa REXX exec. The REXX exec needs an ISPF environment which is notavailable.

Issued by: TAURIP01


Determine either why no ISPF environment is available or correct the API call.If necessary, contact SupportLine.

TAU0086ITAU0086I hh:mm:ss.ttt Timeout reached

Explanation: The user server has been inactive for the amount of time specified by the TIMEOUTvalue in the user server configuration and will now terminate.

Issued by: TAURIP00


TAU0087ITAU0087I hh:mm:ss.ttt Timeout for read : [002] microseconds Clear buffer : [003] Private exception handler : [004] Name of exception handler : [005] Service wait time : [006] ms Task loop time : [007] ms Console wait time : [008] ms Console buffer size : [009] KB

Explanation: This is an informational message listing certain configuration settings.

Issued by: TAURIP02


TAU0088STAU0088S hh:mm:ss.ttt All subtasks failed. Server terminated abnormally


Explanation: This message is issued when a scheduler is started with REATTACH=0 and allsubtasks have failed. The scheduler terminates.

Issued by: TAURIP00


Change the configuration file to either specify REATTACH=1 or increase thenumber of subtasks (NUMTCB). Determine why all the subtasks had failed. Ifnecessary, contact SupportLine.

TAU0089ETAU0089E hh:mm:ss.ttt XML parse is only valid with method 3 for receive


Issued by: TAURIP73

User response: Change the receive method in the programmed IP header to 3.

TAU0090WTAU0090W hh:mm:ss.ttt PIMA size must be at least [002]. Size changed.


Issued by: TAURIP18


TAU0091ETAU0091E hh:mm:ss.ttt XML support is not activated. Specify PIMASIZE for activation.


Issued by: TAURIP73


TAU0092ITAU0092I hh:mm:ss.ttt Invoking initialization exit [002]


Issued by: TAURIP00


TAU0093ITAU0093I hh:mm:ss.ttt Invoking termination exit [002]


Issued by: TAURIP00



TAU0099ITAU0099I =============================================================== [[001]] ===============================================================

Explanation: This is a heading line for several informations.

Issued by: TAURIP00, TAURIP06, TAURIP63, TAURIP73, TAURIP78 (trace level 0); TAURIP01,TAURIP06 (trace level 3); TAURIP21 (trace level 4); TAURIP63 (trace level 5);


TAU0100ETAU0100E hh:mm:ss.ttt A CICS applid must be specified if ECI support isactivated. ECI support disabled


Issued by: TAURIP18


TAU0101ITAU0101I hh:mm:ss.ttt Entry to enqueue/dequeue routine Function : [002] E=Enqueue D=Dequeue X=Remote Enq Y=Remote Deq Type : [003] E=Exclusive S=Shared N=None Scope : [004] 1=Step 2=System 3=Systems Major name : [005] Minor name : [006] Retry count : [007] Wait time : [008] ms


Issued by: TAURIP38


TAU0102ITAU0102I hh:mm:ss.ttt Exit from enqueue/dequeue routine. RC [002]


Issued by: TAURIP38


TAU0103WTAU0103W hh:mm:ss.ttt Resource not available. RC [002] from ENQ Waiting for [003] ms. Major name : [004] Minor name : [005]


Issued by: TAURIP38


User response: None, z/Server automatically retries the request.

TAU0104ITAU0104I hh:mm:ss.ttt Retry limit [002] reached. Resource is marked disabled and will not be used.

Explanation: This is an informational message in response to an API call. The retry limit is set by theclient code.

Issued by: TAURIP38


TAU0105ETAU0105E hh:mm:ss.ttt Enqueue of internal reader failed.

Explanation: z/Server serializes the internal reader using the ENQ ZSERVER/INTRDR. Whenthat ENQ cannot be obtained, some problem in the past prevented the ENQ frombeing released.


Determine why the internal reader could not be enqueued. If necessary, contactSupportLine. Restart the scheduler or user server.

TAU0106WTAU0106W hh:mm:ss.ttt Negative length for receive specified [002] bytesMultiple reads are forced until specified length is reached.



TAU0107ITAU0107I hh:mm:ss.ttt Registration of exception handler >>[002]<< successful.

Explanation: This is an informational message. [002] is the module acting as an exception handler.



TAU0108ETAU0108E hh:mm:ss.ttt Registration of exception handler >>[002]<< failed with token [003]. Continue without exception handler.

Explanation: This message is issued in response to an API call. [003] is an ECBaddress.

Issued by: TAURIP01


Determine why [002] could not be established as an exception handler. Ifnecessary contact SupportLine.


TAU0109WTAU0109W hh:mm:ss.ttt Invalid value specified for TIMEOUT_ACTION. Use only N = Normal or S = Shutdown Value changed to N


Issued by: TAURIP18


TAU0111ITAU0111I hh:mm:ss.ttt Reattach request for task [002] received.


Issued by: TAURIP00


TAU0112ITAU0112I hh:mm:ss.ttt Activating EMCS console with name [002]


Issued by: TAURIP02


TAU0113ETAU0113E hh:mm:ss.ttt Activation of EMCS console failed with RC [002] CA_CONSRC : [003] (hex) CA_CONSRE : [004] (hex) Console deactivated

Explanation: See SA22-7611-xx: MVS Programming: Authorized Assembler ServicesReference, Volume 3 (LLA-SDU), macro MCSOPER for details.

Issued by: TAURIP02


Determine why the EMCS console could not be activated. If necessary,contact SupportLine.

TAU0114ITAU0114I hh:mm:ss.ttt Deactivating EMCS console with name [002]


Issued by: TAURIP00


TAU0115ETAU0115E hh:mm:ss.ttt Deactivation of EMCS console failed with RC [002] CA_CONSRC : [003] (hex) CA_CONSRE : [004] (hex)


Explanation: See SA22-7611-xx: MVS Programming: Authorized Assembler ServicesReference, Volume 3 (LLA-SDU). IPSCA_CONSRC and IPSCA_CONSREare the original MCSOPER return and reason codes.

Issued by: TAURIP00


Determine why the EMCS console deactivation failed. If necessary contactSupportLine.

TAU0116ITAU0116I hh:mm:ss.ttt Activating of EMCS console [002] successful. Console ID : [003] Console Alet : [004]


Issued by: TAURIP02


TAU0117ETAU0117E hh:mm:ss.ttt Getting next message from EMCS console ended with CA_CONSRC : [002] (hex) CA_CONSRE : [003] (hex)

Explanation: See SA22-7611-xx: MVS Programming: Authorized Assembler ServicesReference, Volume 3 (LLA-SDU). IPSCA_CONSRC and IPSCA_CONSRE arethe original MCSOPMSG return and reason codes.


Determine why MCSOPMSG failed. If necessary, contact SupportLine.

TAU0118ITAU0118I hh:mm:ss.ttt Address of EMCS buffer : [002]


Issued by: TAURIP02


TAU0119ETAU0119E hh:mm:ss.ttt No console defined. Commands CCALL and XCALL are not supported.


Issued by: TAURIP01


TAU0120ETAU0120E hh:mm:ss.ttt Console command failed with RC [002] Hex.


Issued by: TAURIP01



Determine why the console command failed. If necessary, contactSupportLine.

TAU0121ETAU0121E hh:mm:ss.ttt Required configuration parameter [002] was not specified Server startup is terminated


Issued by: TAURIP18


Define the required parameters in the configuration file for the scheduleror user server. Refer to the z/Server Installation Guide and Reference.

TAU0122WTAU0122W hh:mm:ss.ttt No user SVC is used for authorized functions. Server must run in an authorized environment.


Issued by: TAURIP02


TAU0123STAU0123S hh:mm:ss.ttt Jobstep is not APF authorized. Startup terminated


Issued by: TAURIP02


TAU0124ETAU0124E hh:mm:ss.ttt No response from server.

Explanation: This message is issued in response to an API call requesting execution of acommand or REXX exec. When the executing program/command does notprovide a response by design, this is not an error.

Issued by: TAURIP01


Determine why the scheduler or user server did not respond, if a response wasexpected. If necessary, contact SupportLine.

TAU0125ITAU0125I hh:mm:ss.ttt Additional BELOWHEAP of [002] bytes created. Heapid is [003].


Issued by: TAURIP02



TAU0126ITAU0126I hh:mm:ss.ttt BELOWHEAP for subtask allocated at [002]


Issued by: TAURIP02


TAU0127ETAU0127E hh:mm:ss.ttt No program for HTTP request defined. HTTP request ignored.


Issued by: TAURIP73

User response: Define a program to accept HTTP requests.

TAU0128ETAU0128E hh:mm:ss.ttt Value [002] for compression is invalid. The valid values are: 0 ==> no compression 1 ==> compress send buffer before send 2 ==> expand receive buffer after receive 3 ==> both


Issued by: TAURIP18

User response: Specify a valid compression value.

TAU0129ETAU0129E hh:mm:ss.ttt Invalid value for COMPAT : [002] Value must be 1 or 2 1 ==> use 48 Byte header (compatibility to version 1) 2 ==> use 100 Byte header (default )


Issued by: TAURIP18


TAU0130ETAU0130E hh:mm:ss.ttt DDName [002] not found. Startup terminated.


Issued by: TAURIP02

System administrator response: Verify that DDNAME [002] is available in the startup procedure. Ifnecessary, contact SupportLine.

TAU0131ITAU0131I hh:mm:ss.ttt XMLCA for subtask allocated at [002] TS for subtask allocated at [003]


Explanation: This is an informational message. XMLCA is the CML communication area, TS istemporary storage (a working area).

Issued by: TAURIP02


TAU0132ETAU0132E hh:mm:ss.ttt Invalid version [002] in ASCII header found. This server is running with version [003]


Issued by: TAURIP73


TAU0133ETAU0133E hh:mm:ss.ttt VIPA [002] could not be resolved


Issued by: TAURIP02

System administrator response: Determine why the configured VIPA could not be resolved. Ifnecessary, contact SupportLine.

TAU0134ITAU0134I hh:mm:ss.ttt Server is [002]


Issued by: TAURIP02


TAU0135STAU0135S hh:mm:ss.ttt Permission denied. [002] not authorized to use port [003].


Issued by: TAURIP00


Determine why port [003] could not be used. Check the hardcopy log forthe NETSTAT responses to the commands issued by z/Server. Ifnecessary, contact SupportLine.

TAU0136SIPS0136S hh:mm:ss.ttt The address is in a timed wait because a LINGER delay from a previous close or another process is using the port. This error can also occur if the port specified in the bind call has been configured as RESERVED on a port reservation statement in the TCP/IP profile

Explanation: The port ("address") could not be bound because TCPIP did not allow it. This maybe due to a LINGER delay from a previous close of a connection. Or anotherprocess might be using the port.


Issued by: TAURIP00


Determine why the port ("address") is not available. Check the hardcopy log for theNETSTAT responses to the commands issued by z/Server. Check that the port isnot reserved to another address space permanently. If necessary, contactSupportLine.

TAU0137ITAU0137I hh:mm:ss.ttt Create slaves : [002] Config for slaves : [003] Proc for slaves : [004]



TAU0138ETAU0138E hh:mm:ss.ttt Invalid value [002] for MULTI_REXX


Issued by: TAURIP18


TAU0139ETAU0139E hh:mm:ss.ttt SVC with function code [002] failed with RC [003]

Explanation: Function [002] (low-order byte 000000xx):

X'01' RACROUTE

X'02' SSICALL

X'03' CMD for ECMD

X'04' Internal start

X'06' Activate EMCS Console

X'07' Deactivate EMCS Console

X'08' Command without CART

X'10' Command with CART

X'18' Send command to console

X'20' Get next message

X'40' Get next command response

X'80' Get response with CART (command and response token)

X'E0' Get response from EMCS

Function [002] (byte 0000xx00):

x'08' Terminate the address space - a return code of 8 is expected.

Return code [003]:

0-250 RACF return code.


252 Callers’ address space is not authorized to call this SVC.

253 No task level security environment to delete.

254 R1 does not point to a valid TAURACFA control block on entry to SVCroutine.

255 Address Space has no ACEE.

256 Invalid function code.

257 Console buffer is too small.


Determine why the SVC failed. If necessary, contact SupportLine.

TAU0140ETAU0140E hh:mm:ss.ttt Message has invalid length. A minimum length of [002] bytes is required for version [003].


Issued by: TAURIP73

User response: User a valid length.

TAU0141ITAU0141I hh:mm:ss.ttt z/Server MAINTASK ready for clients


Issued by: TAURIP00


TAU0142ITAU0142I hh:mm:ss.ttt z/Server SUBTASK ready for clients


Issued by: TAURIP01


TAU0143STAU0143S hh:mm:ss.ttt An OMVS process initialization failure has occurred. A valid OMVS RACF segment may be missing or contain invalid specifications.


Issued by: TAURIP00


Check the RACF OMVS segment of the user associated with the application.Check if the RACF OMVS segment is defined. Check if the UID is defined, andcheck if a proper HOME directory is defined. If necessary, contactSupportLine.


TAU0144WIPS0144W hh:mm:ss.ttt Configuration parameter [002] is no longer supported.


Issued by: TAURIP18

System administrator response: Remove parameter [002] from the configuration file.

TAU0145ITAU0145I hh:mm:ss.ttt BASE64 utility called with function [002]


Issued by: TAURIP47


TAU0146ITAU0146I ------------------------------------------------------------------ BASE64 Input address : [001] Length : [002] ------------------------------------------------------------------


Issued by: TAURIP47


TAU0147ITAU0147I ------------------------------------------------------------------ BASE64 Output address : [001] Length : [002] ------------------------------------------------------------------


Issued by: TAURIP47


TAU0148EIPS0148E hh:mm:ss.ttt Storage needed for [002] subtasks with a buffer size of [003] is greater than 2GB.

Explanation: The combination of buffer size and number of subtasks (BUFFERSIZE/BUFFERUNIT and NUMTCB) specified in the scheduler configuration file resultsin the need for an address space that would be larger than 2GB.

Issued by: TAURGDA


Reduce one or more of the three parameters to fit within the limits of aconventional z/OS address space.

TAU0149ETAU0149E hh:mm:ss.ttt Storage needed for [002] subtasks with a buffer size of [003] is greater than private region with [004] bytes.


Explanation: The combination of buffer size and number of subtasks (BUFFERSIZE/BUFFERUNIT and NUMTCB) specified in the scheduler configuration file resultsin the need for an address space that would be larger than 2GB.

Issued by: TAURGDA


Reduce one or more of the three parameters to fit within the limits of aconventional z/OS address space.

TAU0150ITAU0150I hh:mm:ss.ttt About [002] bytes of private region used. Maximum would be [003] bytes


Issued by: TAURGDA


TAU0151ITAU0151I hh:mm:ss.ttt New userid of ACEE for TCB [002] is [003]

Explanation: This is an informational message due to IPTRACE level 5 being set. If it is issued for ascheduler, then the working task T000000x had the identity switch; if it is issued for auser server, then the identity switch occurred between the first and second step.

Issued by: TAURIP02


TAU0152ITAU0152I hh:mm:ss.ttt Flags for send : [002]


Issued by: TAURIP02


TAU0153ITAU0153I hh:mm:ss.ttt Address of z/Server statistic area is [002]


Issued by: TAURIP02


TAU0154STAU0154S hh:mm:ss.ttt Current z/OS Release [002] is not supported.

Explanation: This z/OS release is not supported. Functionality needed to run z/Server ismissing. z/Server terminates.

Issued by: TAURLOGN


Migrate to a supported operating system (z/OS 1.10 or higher).


TAU0155WTAU0155W hh:mm:ss.ttt Current z/OS Release [002] is not supported but may work.

Explanation: This z/OS release is not supported.


Run z/Server unsupported and at your own risk. Migrate to a supportedoperating system (z/OS 1.10 or higher).

TAU0156ETAU0156E hh:mm:ss.ttt Command task is busy. ENQ/DEQ not done.

Explanation: The command task is busy servicing other requests. The API-requested ENQ or DEQwas not executed.

Issued by: TAURIP02

User response: Retry the ENQ or DEQ request to ensure data integrity.

TAU0157ITAU0157I hh:mm:ss.ttt Post command task for remote ENQ/DEQ

Explanation: This is an informational message due to IPTRACE level 5 being set. A remoteENQ/DEQ is issued by the CMDTASK on behalf of one of the working tasks T000000x.

Issued by: TAURIP39


TAU0158ITAU0158I hh:mm:ss.ttt Wait for completion of initialization of service task

Explanation: This is an informational message due to IPTRACE level 5 being set. The LISTENERtask is waiting for the initialization of the service task (SRVTASK). The maximum time towait is defined using the configuration variable ECB_TIMEOUT. If SRVTASK could notbe initialized until ECB_TIMEOUT has elapsed, message TAU0176E is issued. Startupis terminated.

Issued by: TAURIPLI


TAU0159ITAU0159I hh:mm:ss.ttt Wait for completion of initialization of message task

Explanation: The LISTENER task is waiting for the initialization of the message task (MSGTASK).The maximum time to wait is defined using the configuration variable ECB_TIMEOUT. IfMSGTASK could not be initialized until ECB_TIMEOUT has elapsed, messageTAU0176E is issued. Startup is terminated.

Issued by: TAURIPLI


TAU0160ITAU0160I hh:mm:ss.ttt Listener posted


Explanation: This is an informational message. LISTENER task was posted by either CMDTASK,SRVTASK or MSGTASK.

Issued by: TAURIPLI


TAU0161STAU0161S hh:mm:ss.ttt Failed to read named/token pair in task exit routine

Explanation: The task exit routine was unable to read the name/token pair ZCOMMCA.The task exit routine is invoked if a z/Server subtask ended abnormally.

Issued by: TAURETXR


Set trace level to 5 and reproduce the problem. Contact SupportLine.

TAU0162STAU0161S hh:mm:ss.ttt Subtask [002] attached more than [003] times. Due to possible loop, server is terminating. Please check reason for frequent reattach

Explanation: If a subtask terminates abnormally, z/Server reattaches the subtask. If the subtaskis attached more than 21 times, z/Server assumes a loop and terminates. There isa CEEDUMP written for every abnormal end of a subtask. The name of thesubtask affected is provided in [002].

Issued by: TAURIPLI


Try to find the reason for abnormal termination. Contact SupportLine and provideall joblogs and dumps.

TAU0163STAU0163S hh:mm:ss.ttt Insufficient storage for [002] TCB. Startup terminated.

Explanation: This message is issued if a CEEGTST request during initialization was notsuccessful. Startup of the scheduler is terminated with RC=88.

Issued by: TAURIP02


Increase the REGION size of the STC or do one of the following actions until themessage disappears.

• Reduce the value of NUMTCB (# of worker tasks)• Reduce the value of BUFFERSIZE

TAU0164ITAU0164I hh:mm:ss.ttt Before calling SR_EXIT [002] as header exit.

Explanation: This is an informational message due to IPTRACE level 5 being set. If a send/receiveexit is defined in the configuration file (SR_EXIT=), this message indicates theinvocation of the exit with [002] as a header exit.

Issued by: TAURIP73



TAU0165ITAU0165I hh:mm:ss.ttt After call SR_EXIT [002] RC was [003].

Explanation: This is an informational message due to IPTRACE level 5 being set. If a send/receiveexit is defined in the configuration file (SR_EXIT=) this message indicates thetermination of the exit.

Issued by: TAURIP73


TAU0166ITAU0166I hh:mm:ss.ttt Generating passticket for userid [002] and application [003].


Issued by: TAURIP59


TAU0167ETAU0167E hh:mm:ss.ttt Generating passticket failed with RC [002] hex.

Explanation: Call to RCVTPTGN failed. Possible return codes are:

X’08’ No PTKTDATA profile found for the application

X’0C’ No task or address space ACEE found, and the ACEE pointer was notspecified on the input parameter list

X’10’ Caller is not authorized

X’14’ The RACF PTKTDATA class is not active

Issued by: TAURIP59


Check RC and correct the problem.

TAU0168ITAU0168I hh:mm:ss.ttt Passticket [002] successfully generated.


Issued by: TAURIP59


TAU0169WTAU0169W hh:mm:ss.ttt Port [002] is in status TIMEWT. Waiting [003] ms before retry.

Explanation: This message is issued if the configuration variable PORTCHECK is set to one. Duringport check the scheduler determined that port [002] is in a TIMEWAIT state. This mayhappen if the address space is restarted immediately after a shutdown. The scheduleraddress space will wait one second and check the port again. If the port is still in aTIMEWAIT state after 10 attempts, startup is terminated with message TAU0136S.


Issued by: TAURIP17


Issue the operator command D TCPIP,<tcpname>,N,ALLCONN,PORT=<port> anddetermine why the port is in use. Wait until the port is available to be bound again. Ifthe scheduler address space terminated, restart the scheduler. If a user server couldnot be started, retry the failing operation.

TAU0171ETAU0171E hh:mm:ss.ttt All subtasks busy. Request not processed.

Explanation: The LISTENER task received a message from the client but all worker tasks arebusy and the server was configured with NOFTASK=M.

Issued by: TAURIPLI


If this message occurs in a scheduler, increase the number of worker tasks(configuration variable NUMTCB). If this message occurs in a user server with anISPF environment, check why the worker task is busy. This message may appearto indicate a possible loop.

TAU0172ETAU0172E hh:mm:ss.ttt User SVC could not be resolved through data space. Startup terminated.

Explanation: The user administration was called with the function "read header". The callended with a return code greater than zero.

Issued by: TAURIP18


Make sure the holder task is started. Restart the scheduler with trace level of5. If the problem persists, contact SupportLine.

TAU0173ITAU0173I hh:mm:ss.ttt Waiting [002] hundredth of one second.

Explanation: This is an informational message due to IPTRACE level 6 being set. This message iswritten if z/Server goes into a delay for varying reasons.

Issued by: TAURIP62


TAU0174ITAU0174I hh:mm:ss.ttt Using EXIT at [002] and ECB at [003] after wait.

Explanation: This is an informational message due to IPTRACE level 6 being set. This message iswritten if z/Server is waiting for an ECB. In addition, a timer exit was established that willpost another ECB if a timeout occurs.

Issued by: TAURIP62


TAU0176ETAU0176E hh:mm:ss.ttt [002] did not signal READY within [003] ms Startup terminated.


Explanation: z/Server was waiting [003] ms for initialization of task [002] (for instanceCMDTASK) but the subtask did not signal READY. Because z/Server is notoperational in this case, the startup is terminated.

Issued by: TAURIPLI


The timeout may be increased with the configuration variable ECB_TIMEOUT. Inmost cases, this is a performance problem. If the problem cannot be solved, startthe server with trace level 5. Contact SupportLine.

TAU0177ITAU0177I hh:mm:ss.ttt Cancel timer request with ID [002].

Explanation: This is an informational message due to IPTRACE level 6 being set. This message iswritten if z/Server is waiting for an ECB. In addition, a timer exit was established that willpost another ECB if a timeout occurs. If the first ECB is posted before the second, thetimer request for the second ECB is cancelled.

Issued by: TAURIP62


TAU0178ETAU0178E hh:mm:ss.ttt Call to STIMER was unsuccessful RC [002] (hex).

Explanation: Seting a timer interval was unsuccessful.

Issued by: TAURIP62

System administrator response: Contact SupportLine and provide all output.

TAU0179ITAU0179I hh:mm:ss.ttt Timer established with ID [002].


Issued by: TAURIP62


TAU0182ITAU0182I [001] termination completed for [002]

Explanation: This informational message is issued if a worker task has terminated.

Issued by: TAURIP00


TAU0183ETAU0183E hh:mm:ss.ttt RACROUTE class check for [002] failed. Startup terminated.

Explanation: This message is issued if the RACF class JESSPOOL or $IPSERV was not foundduring initialization of a scheduler.

Issued by: TAURIP02

User response: This message does not necessarily indicate an error. None.


TAU0187ITAU0187I hh:mm:ss.ttt Subtask [002] for z/Server is terminating. RC [003] in hex

Explanation: This message is issued during shutdown and indicates the termination of the subtaskdefined in slot 002.

Issued by: TAURIP01 and TAURIPLI


TAU0192ETAU0192E hh:mm:ss.ttt TCP/IP image [002] not usable. Reason : [003] (hex).

Explanation: The name of the IP stack (IPNAME) specified in the configuration file is notusable. Reason [003] is the reason code:

08 Image not found

40 Image is terminating

20 Image is down

10 Image is stopped or is stopping

Issued by: TAURIPLI


Check name of image or reason code.

TAU0195ETAU0195E hh:mm:ss.ttt Infrastructure is gone. Holder not available. Server will be terminated

Explanation: This message indicates that the holder task is no longer available. None of theschedulers and user servers using this holder address space can work any longerbecause the infrastructure needed is gone. All schedulers and user servers areterminated. Existence of the holder and its infrastructure is verified with each Ipmessage received from a client or when the SRVTASK wakes up.

Issued by: TAURIPLI/TAURIP16


Check why the holder task was lost. If needed, contact SupportLine and provide alljoblog from all z/Server address spaces.

UNI - Unicode code conversion servicesz/Server uses the Unicode conversion services to perform code page conversions. For details, seeSA22-7649-xx: Unicode Services User's Guide and Reference.

UNI0001IUNI0001I hh:mm:ss.ttt Unicode character conversion from CCSID [002] to CCSID [003] A(Input) : [004] A(Output) : [005] Input length : [006]


Explanation: This is an informational message due to IPTRACE level 4 being set. [002] is the sourcecode page, [003] is the target code page.

Issued by: TAURIP60


UNI0002IUNI0002I hh:mm:ss.ttt Unicode character conversion ended with RC [002] and RSN [003].

Explanation: This is an informational message due to IPTRACE level 4 being set. See SA22-7649-xx: Unicode Services User's Guide and Reference for the return and reason code.

Issued by: TAURIP60


UNI0003IUNI0003I ------------------------------------------------------------------ Result after conversion Old length : [001] New length : [002] ------------------------------------------------------------------


Issued by: TAURIP60


UNI0004WUNI0004W hh:mm:ss.ttt Unicode character conversion not processed because CCSID of source is equal to CCSID of target.




UNI0005EUNI0005E hh:mm:ss.ttt Dynamic CCSID for z/Server in ASCII header is not numeric. Value is [002]


Issued by: TAURIP73


UNI0006WUNI0006W hh:mm:ss.ttt Change CCSID for z/Server requested Current z/Server CCSID : [002] Requested z/Server CCSID : [003] Requested client CCSID : [004] Flags : [005] .... ...1 Message has ASCII-Header .... ..1. Copepage translation for send requested


.... .1.. Copepage translation for receive requested ...1 .... Change Codepage for z/Server requested

Explanation: This is an informational message due to IPTRACE level 1 being set. It indicates that thecurrent code page of the z/Server is changed from value [002] to value [003].

Issued by: TAURIP73

User response: To avoid unnecessary code page conversions, ensure that the client and z/Server codepages match. The z/Server code page is set in each configuration file using theparameter CCSID.

UNI0007EUNI0007E hh:mm:ss.ttt Codepage translation from CCSID [002] to CCSID [003] failed with RC [004] and reason [005]

Explanation: See SA22-7649-xx: Unicode Services User's Guide and Reference for thereturn and reason code.



Determine why the code page translation failed. If necessary, contactSupportLine.

UNI0008WUNI0008W hh:mm:ss.ttt Change to an unsupported CCSID for z/Server requested and accepted. Using UTF-8 for parser Current z/Server CCSID : [002] Requested z/Server CCSID : [003] Requested client CCSID : [004] Flags : [005] .... ...1 Message has ASCII-Header .... ..1. Copepage translation for send requested .... .1.. Copepage translation for receive requested .... 1... No substitution chars are used. Service fails ...1 .... Change Codepage for z/Server requested ..1. .... Codepage for z/Server unsupported .1.. .... Codepage for z/Server ASCII for num. value 0-9 1... .... Codepage for z/Server ASCII is DBCSExplanation: This is an informational message due to IPTRACE level 1 being set. Despite being unsupported, the requested code page was set.

Explanation: This is an informational message due to IPTRACE level 1 being set. Despite beingunsupported, the requested code page was set.

Issued by: TAURIP73

User response: To avoid unnecessary code page conversions, ensure that the client and z/Server codepages match. The z/Server code page is set in each configuration file using theparameter CCSID.

UNI0009WUNI0009W hh:mm:ss.ttt Unicode character conversion not processed because an unsupported CCSID for the z/Server was specified.



Verify that the configuration files (scheduler and user server) specify avalid code page - parameter CCSID.


UNI0010WUNI0010W hh:mm:ss.ttt Unicode character conversion not processed due to a client request.



UNI0011WUNI0011W hh:mm:ss.ttt Unicode character conversion not processed because length of XML document is zero.



UNI0012EUNI0012E hh:mm:ss.ttt Variable substitution for input message is only allowed if a valid z/Server codepage is specified.


Issued by: TAURIP73

User response: Specify a valid code page.

UNI0013IUNI0013I ------------------------------------------------------------------ Data before conversion ------------------------------------------------------------------


Issued by: TAURIP60


XML - XML System Parser Interfacez/Server uses the XML system parser functionality (that can run on specialty engines) for parsing XMLformatted documents. Any return and reason codes displayed were originally issued by the XML systemparser. For details, see SA23-1350-xx: z/OS XML System Services User's Guide and Reference.

XML is also used for communication inside z/Server. This means that XML errors may be produced inunexpected situations. The logon parameters (user ID and password) are passed as an XML document tothe validation routine, and a user ID that is too long (more than eight characters) results in an XML0003Eerror message.

XML0001EXML0001E hh:mm:ss.ttt XML Call to [002] ended. RC : [003] and reason [004]

Explanation: An XML system parser interface function call failed.

[002] XML System Parser Interface function name

[003] Return code


[004] Reason code

Some common reason codes and their possible cause:

1300 Buffer too small

3030 Incorrect data set characteristics (not RECFM=F[B], LRECL=80)

3063 The processed document is not XML

Issued by: TAURIP63


Determine why the interface call failed. If necessary, contact SupportLine.

XML0002IXML0002I hh:mm:ss.ttt Unknown XML record type : [002]


Issued by: TAURIP75


XML0003EXML0003E hh:mm:ss.ttt Attribute value [002] with length [003] is too long for attribute [004]


Issued by: TAURIP75

User response: Correct the XML document.

XML0004EXML0004E hh:mm:ss.ttt Value [002] for elememt [003] is not numeric


Issued by: TAURIP75


XML0005EXML0005E hh:mm:ss.ttt Unknown attribute [002] for element [003]


Issued by: TAURIP75


XML0006IXML0006I hh:mm:ss.ttt z/Server is using CCSID [002]


Issued by: TAURIP02



XML0007EXML0007E hh:mm:ss.ttt Invalid value [002] for attribute [003].


Issued by: TAURIP75


XML0008EXML0008E hh:mm:ss.ttt Attributes required for command [002].


Issued by: TAURIP75


XML0009IXML0009I hh:mm:ss.ttt New XML image at address [002].


Issued by: TAURIP75


XML0010IXML0010I hh:mm:ss.ttt XML interface called with function [002] and CCSID [003]


Issued by: TAURIP63

XML0011IXML0011I hh:mm:ss.ttt XML interface ended. RC : [002] RSN : [003]


Issued by: TAURIP63


XML0012IXML0012I hh:mm:ss.ttt Offset to XML input area where parser stopped : [002]


Issued by: TAURIP63


XML0013EXML0013E hh:mm:ss.ttt Maximum number of [002] XML images exceeded.



Issued by: TAURIP75

System administrator response: Internal restriction; contact SupportLine.

XML0014EXML0014E hh:mm:ss.ttt For USRENQ or USRDEQ a PORT must be specified.


Issued by: TAURIP78

User response: Specify the port in the USRENQ/USRDEQ request.

XML0015EXML0015E hh:mm:ss.ttt Port [002] does not belong to user [003].


Issued by: TAURIP78

User response: Correct the port number.

XML0016EXML0016E hh:mm:ss.ttt Value for attribute [002] must have a length of [003]


Issued by: TAURIP75


XML0017IXML0017I hh:mm:ss.ttt XML query information Version : [002] Autodetect value : [003] Autodetect CCSID : [004] Specified CCSID : [005] Length of decl : [006] Flag 1 : [007] 1... .... standalone flag .1.. .... with byte order mark flag Flag 2 : [008] 1... .... standalone specified .1.. .... encoding specified ..1. .... version specified


Issued by: TAURIP63


XML0018IXML0018I hh:mm:ss.ttt Initialzing z/OS XML parser with CCSID [002]



Issued by: TAURIP63


XML0019EXML0019E hh:mm:ss.ttt Invalid codepage [002] for z/Server specified. CCSID is only valid if this is a scheduler and CCSID of client is UTF-8 The codepage is also invalid if this is a scheduler, but the scheduler functionality is skipped in this request.

Explanation: The code page CCSID specified in the configuration is not supported by thez/OS XML parser. The startup of the server is stopped.



Check the code page CCSID specified in the configuration file. Change it to acode page CCSID supported by z/Server.

XML0020EXML0020E hh:mm:ss.ttt Invalid length [002] for attribute [003]


Issued by: TAURIP75

User response: Specify a valid length.

XML0022EXML0022E hh:mm:ss.ttt [002] is not a valid command.

Explanation: A scheduler received an invalid command through an API request.

Issued by: TAURIP75


XML0023EXML0023E hh:mm:ss.ttt Attribute [002] invalid for command [003].

Explanation: A scheduler received an invalid attribute through an API request.

Issued by: TAURIP75


XML0024EXML0024E hh:mm:ss.ttt Missing required attributes for command [003].

Explanation: A scheduler received command [003] with missing attributes through an API request.

Issued by: TAURIP75


XML0025EXML0025E hh:mm:ss.ttt Value [002] for attribute [003] is not numeric.


Explanation: A scheduler received a non-numeric value for an attribute that requires a numeric valuethrough an API request.

Issued by: TAURIP75


XML0026EXML0026E hh:mm:ss.ttt Length of bitstring for attribute [002] not 8 bytes.

Explanation: A scheduler received a bitstring value for an attribute with a length unequal to 8 throughan API request.

Issued by: TAURIP75


XML0028WXML0028W hh:mm:ss.ttt Interpretation of XML document stopped at end of element [002].

Explanation: This is an informational message due to IPTRACE level 1 being set. The interpretationwas stopped when element [002] is closed.

Issued by: TAURIP75

User response: None

CEA TSO/E Address Space Services

ZCA0001EZCA0001E hh:mm:ss.ttt XML A logon procedure is required for policy CEA.

Explanation: A scheduler was defined with policy 8 and the configuration variableCEA_LOGONPROC was not specified.

Issued by: TAURIP18

Issued under: Independent of any trace level

User response: None

System administrator response: Specify a valid logon procedure.

ZCA0002IZCA0002I hh:mm:ss.ttt CEA TSO/E address space services Account............. : [002] Group............... : [003] Logon procedure..... : [004] Charset............. : [005] Codepage............ : [006] Screen size......... : [007] X [008] Region size......... : [009]

Explanation: This message shows all configuration parameters for a schedulerdefined with policy 8.

Issued by: TAURIP74



User response: None


ZCA0006EZCA0006E hh:mm:ss.ttt Call to CEASAPIT with function [002] ended RC : [003] RSN : [004] Diag1 : [005] Diag2 : [006] Diag3 : [007] Diag4 : [008]

Explanation: A call to DLL CEASAPIT/CEATsoRequest failed.

Possible functions are:

• CEATSOSTART• CEATSOENDS• CEATSIQUERY• CEATSOATTN• CEATSOPING• CEATSOQUERYAPP

Issued by: TAURCEA


User response: None

System administrator response: See SA22-7613-xx callable services for HLL for more information

ZCA0010IZCA0010I hh:mm:ss.ttt Values for new TSO/E address space area Userid : [002] Asid : [003] MessageQueueID : [004] Stoken : [005] Index : [006]

Explanation: This message is issued for a successful CEATSOSTART and showsthe same values as the CEA command f cea,diag,sesstable

Issued by: TAURCEA

Issued under: Trace level 4 or higher

User response: None


ZCA0011EZCA0011E hh:mm:ss.ttt Values error in callable service : [002] RC : [003] RSN : [004]


Explanation: This message is issued if a call to a UNIX message queue service failed.

Possible services are:

• BPX1QRC - Receive from a message queue• BPX1QSN - Send to a message queue• BPX1QCT - Control operation• BPX1QGT - Create/find a message queue

Issued by: TAURMSQ


User response: None


If you are not able to find the reason, contact SupportLine and provide allavailable output. If possible, try to recreate the problem with trace level 6.

ZCA0012IZCA0012I hh:mm:ss.ttt [002] bytes received from message queue

Explanation: This message is issued after a successful read of a UNIX messagequeue service failed.

[002] Contains the amount of bytes.

Issued by: TAURMSQ


User response: None


ZCA0013IZCA0012I hh:mm:ss.ttt Sending [002] bytes to message queue Queue ID...... [003] (hex) Message type.. [004] (hex)

Explanation: This message is issued after a successful write to a UNIX messagequeue.

[002] Contains the amount of bytes

[003] Contains the queue ID

[004] Contains the message type

Issued by: TAURMSQ


User response: None


None


ZCA0014IZCA0014I hh:mm:ss.ttt Information for message queue [002] Messages on queue : [003] Maximum bytes allowed : [004] Time of last send : [005] Time of last receive : [006]

Explanation: This message is issued in response to a USSQMSGQ (Unix messagequeue query) command.


[003] The number of messages on the queue

[004] The maximum number of bytes allowed

[005] The time of the last message sent

[006] The time of the last message received

Issued by: TAURMSQ


User response: None


None

ZCA0015EZCA0015E hh:mm:ss.ttt Abend during CEA processing. ECB is [002]

Explanation: This message is written when the ATTACH of subtask TAURC64 failed.[002] contains the ECB for the abended subtask

Issued by: TAURCEA


User response: None


Contact SupportLine and provide all available output. If possible, try torecreate the problem with trace level 6

ZCA0016EZCA0016E hh:mm:ss.ttt Start of TSO address space was unsuccessful. Unable to get CAUB_JOBID. ASID : [002] RSN : [003]

Explanation: This message is written when z/Server was not able to get the JOBID after aCEA TSO/E address space was successfully created. In most cases, thereason for this message is a JCL error.

Issued by: TAURCEA


User response: None



Check the logon procedure. If you are not able to find the reason, contactSupportLine and provide all available output. If possible, try to recreate theproblem with trace level 6.

ZCA0018IZCA0018I hh:mm:ss.ttt CEA interface called with function [002]

Explanation: This message is written if module TAURCEA was called. Functionsare the same as in message ZCA006E

Issued by: TAURCEA

Issued under: Trace Level 5 or higher

User response: None


ZCA0019IZCA0018I hh:mm:ss.ttt CEA interface ended. RC : [002]

Explanation: This message is written after call to module TAURCEA

Possible return codes:

00 - Call successful

08 - Invalid function

12 - Call to CEATsorequest failed

16 - Call to BPX. API failed

20 - Abend in subtask for CEA processing

40 - Creation of security environment for CEA failed

44 - Invalid screen size

Issued by: TAURCEA


User response: None


ZCA0022EZCA0022E hh:mm:ss.ttt Account information is required scheduler of type CEA.

Explanation: A scheduler was defined with policy 8 and the configuration variableCEA_ACCOUNT was not specified.

Issued by: TAURIP18


User response: None

System administrator response: Specify ACCOUNT information


ZCA0024IZCA0024I hh:mm:ss.ttt Reading message queue Queue ID...... [002] (hex) Message type.. [003] (hex) Read count.... [004] Flags......... [005]

Explanation: This message is written for a read request of a USS message queuee.


[003] Contains the message type

[004] Contains the # of requested reads

[005] Contains the read flags

X’00000000’ Wait for next message

X’00000001’ Do not wait for next message

Issued by: TAURMSQ


User response: None


None

ZCA0025IZCA0025I hh:mm:ss.ttt USS message queue utility called with function [002]

Explanation: This message is written if module TAURMSQ was called. Possiblefunctions are Read/Write/Query/Create/Delete/Gettoken.

Issued by: TAURMSQ


User response: None


ZCA0027EZCA0027E hh:mm:ss.ttt Creation of task level security for CEA failed UserID : [002] SAF RC : [003] (hex) RACF RC : [004] (hex) RACF RSN : [005] (hex)

Explanation: This message is issued after the creation of an ACEE for CEA failed

Issued by: TAURCEA


User response: None


See SA22-7692-xx: Security server RACROUTE macro reference. If youare not able to solve the problem, contact SupportLine and provide alloutput. Try to recreate the problem with trace level 6.


ZCA0028IZCA0028I hh:mm:ss.ttt Ping for application identifier [002]

Explanation: This message is issued from the command task if a scheduler is defined withpolicy 8 (CEA). The command task will ping the application ID from [002] inorder to keep the CEA userid server alive. If the user servers are not pinged,CEA will terminate the user servers after an idle time of 15 minutes.

Issued by: TAURIP16


User response: None


None

ZCA0029WZCA0029W hh:mm:ss.ttt TSU session for user [002] and ASID [003] no longer exists. Entry in user administration cleared.

Explanation: This message is issued from the command task if a scheduler is definedwithpolicy 8 (CEA). The command detected an inactive CEA user server. Thecommand task will clear the entry.

Issued by: TAURIP16


User response: None


This is normal if a SERVICE_WAIT of more than 15 minutes is specified. In thiscase, CEA will terminate the user server after 15 minutes idle time. Thescheduler will cleanup the entry one minute later. If a SERVICE_WAIT of lessthan 14 minutes is specified, the user server should never end without a logoff.

ZCA0030IZCA0030I hh:mm:ss.ttt ---------------------------------------------------- CEA request structure ----------------------------------------------------

Explanation: This message is the header information before the CEA requeststructure is dumped. This information is only required if SupportLine iscontacted to solve problems with CEA.

Issued by: TAURCEA


User response: None


None.

ZCA0031IZCA0031I hh:mm:ss.ttt Query TSU session for user [002] and ASID [003]


Explanation: This message is issued from the command task if a scheduler isdefined with policy 8 (CEA). The command checks if a CEA user serverdefined in the scheduler is still active.

Issued by: TAURIP16


User response: None


None.

ZCA0032EZCA0032E hh:mm:ss.ttt Send to client ended. RC : [002] (hex).

Explanation: This message is issued if the client has initialized a CEA dialog and a sendto the client was unsuccessful.

Issued by: TAURQCEA


User response: None


If you are not able to solve the problem, contact SupportLine and provide alloutput. Try to recreate the problem with trace level 6.

ZCA0033EZCA0033E hh:mm:ss.ttt Receive from client ended. RC : [002] (hex).

Explanation: This message is issued if the client has initialized a CEA dialog and areceive from the client was unsuccessful.

Issued by: TAURQCEA


User response: None


If you are not able to solve the problem, contact SupportLine and provide alloutput. Try to recreate the problem with trace level 6

ZCA0034IZCA0034I hh:mm:ss.ttt Using alternate screen size [002] X [003] from LOGON.

Explanation: This message is issued if the client sent a CEA logon request andspecified the ROWS and COLUMNS attribute.

Issued by: TAURCEA


User response: None


ZCA0035EZCA0035E hh:mm:ss.ttt Invalid request for CEATASK. Only R,W,Q allowed.


Explanation: This message is issued if the client has initialized a CEA dialog and aninvalid request was sent to the scheduler.

Issued by: TAURQCEA


User response: None


Contact SupportLine and provide all output. Try to recreate the problemwith trace level 6

ZCA0036IZCA0036I hh:mm:ss.ttt CEA message queue handler terminated.

Explanation: This message is issued if the client has initialized a CEA dialog andthe CEA dialog was terminated due to logoff.

Issued by: TAURQCEA


User response: None


ZCA0038EZCA0038E hh:mm:ss.ttt Invalid screen size [002] X [003] Only 24x80, 32x80, 43x80, 27x132 and 62x160 allowed

Explanation: This message is issued if an invalid screen size for a CEA user serverwas specified.

Issued by: TAURCEA


User response: Use a valid screen size


ZCA0039IZCA0039I hh:mm:ss.ttt Initial command..... : [002]

Explanation: This message prints the content of the configuration variableCEA_INIT_CMD.

Issued by: TAURIP74


User response: None


ZCA0040IZCA0040I hh:mm:ss.ttt Before call to CEA initial command [002] via TAURUCA


Explanation: This message is issued from subtask CEAISPF when a CEA dialog isinitialized before the defined initial command is invoked. This messageindicates the beginning of a CEA dialog.

Issued by: TAURIP07


User response: None


None

ZCA0041IZCA0041I hh:mm:ss.ttt After call to CEA initial command [002] via TAURUCA

Explanation: This message is issued from subtask CEAISPF after a CEA dialog wasinitialized and the defined initial command terminated. This messageindicates the end of a CEA dialog.

Issued by: TAURIP07


User response: None


None

ZCA0042IZCA0042I hh:mm:ss.ttt CEAISPF READY for initialization

Explanation: This message is issued from subtask CEAISPF and indicates that thesubtask is now READY for the initialization of a CEA dialog.

Issued by: TAURIP07


User response: None


ZCA0043IZCA0043I hh:mm:ss.ttt Initializing z/Server for CEA

Explanation: This message is issued if a user server for CEA is started.

Issued by: TAURUCA


User response: None


ZCA0044IZCA0044I hh:mm:ss.ttt Terminating z/Server for CEA

Explanation: This message is issued if a user server for CEA is terminated.

Issued by: TAURUCA



User response: None


ZCA0045IZCA0045I hh:mm:ss.ttt Before call to CEA initial command [002] for [003]

Explanation: This message is issued if the CEA initial REXX is issued. [003]contains the reason for the initialization and may be:

• for initialization• for split screen

Issued by: TAURUCA


User response: None


None

ZCA0046IZCA0046I hh:mm:ss.ttt After call to CEA initial command [002] for [003]

Explanation: This message is issued if the CEA initial REXX is terminated. [003]contains the reason for the termination and may be:

• for initialization• for split screen

Issued by: TAURUCA


User response: None


None

ZCA0047EZCA0047E hh:mm:ss.ttt Underlying z/OS level must be at least z/OS 1.13 when a scheduler of type CEA is started.

Explanation: This message is issued if the scheduler with policy 8 is started andz/OS 1.13 or higher is not available.

Issued by: TAURIP18


User response: None


ZCA0048IZCA0047E hh:mm:ss.ttt CEA Screen count for initial command [002] is [003]


Explanation: This message is issued if the CEA initial REXX is activated andtraces the logical screen count.

Issued by: TAURUCA


User response: None


ZCA0050IZCA0050I hh:mm:ss.ttt LOGOFF request for CEA received

Explanation: This message is issued if the CEA dialog is terminated due to a logoffcommand.

Issued by: TAURQCEA


User response: None


ZCA0051EZCA0051E hh:mm:ss.ttt Invalid internal command received.

Explanation: The client sent an invalid internal command to the CEA dialog.

Issued by: TAURQCEA


User response: None


Contact SupportLine and provide all output. Try to recreate theproblem with trace level 6.

ZCA0052IZCA0052I hh:mm:ss.ttt Internal command [002] specified.

Explanation: The client sent a valid internal command to the CEA dialog.

Issued by: TAURQCEA


User response: None


ZCA0053IZCA0053I Application ID...... : [001] Ping application ID. : [002]

Explanation: This message shows configuration parameters for a schedulerdefined with policy 8.

Issued by: TAURIP74

Issued under: Independent of any trace levelAbend Codes


User response: None


ZRM0001EZRM0001E hh:mm:ss.ttt Enqueue of resource was made with userid [002] Dequeue not allowed for userid [003]

Explanation: Userid 0003 tried to issue a dequeue of a resource that was enqueued (owned) byuserid 002.

Issued by: TAURIP35

User response: Contact userid 002 if the resource should be freed.

ABEND Code U2222z/Server has one (user) ABEND code: u2222 with different reason codes.

Reason Code 1Abendu2222 reason code 1 is issued whenever a user server was terminated without first stopping one ormore REXX environments that are still running at the time of termination. In that case, task control blocks(TCBs) that are left hanging will not terminate on their own, causing the address space to hang duringtermination. In that case, the address space will need to be canceled.

This usually happens when an ISPF application encounters a problem and does not send a goodexplanation to the client or is now in an undefined state. It can also happen when a command was issuedin the user server that is listed in the installation’s IKJTSOxx parmlib member under PLATCMD orPLATPGM. z/Server does not tolerate commands executed under the platform TCB as it requires MVSservices for task termination (clean-up).

To prevent subsequent abnormal end problems, z/Server terminates all tasks that should not be runninganymore using reason code 1.

Language Environment abendsFor an explanation of these abends (U4012, U4034, U4036, U4038, U4039,U4041, U4042, U4043, U4080,U4082, U4083, U4084, U4085, U4086, U4087, U4088, U4089, U4091, U4092, U4093, U4094 and U4095),see SA22-7566: Language Environment Run-Time Messages.

TroubleshootingIf the user and system administrator responses do not help to correct the problem, the appropriate log filesand dumps should be sent to SupportLine. The log files are found as JESx output data sets.

HolderA standard holder address space job log consists of the following DD names (example from JES2/SDSF):

NP DDNAME StepName ProcStep CrDate-CrTime O-Grp-N DSID Owner SYSTSPRT TAURHLDP mm/dd/jjjj hh:mm:ss 102 TAUUSR MAINTASK TAURHLDP mm/dd/jjjj hh:mm:ss 105 TAUUSR JESYSMSG mm/dd/jjjj hh:mm:ss 4 TAUUSR JESMSGLG mm/dd/jjjj hh:mm:ss 2 TAUUSR JESJCL JES2 mm/dd/jjjj hh:mm:ss 3 TAUUSR


The JESYSMSG, JESMSGLG and JESJCL DD names are the standard names used by JES2.

MAINTASKThis DD statement contains the messages issued by MAINTASK running in the holder address space.During startup the configuration parameters used are shown. MAINTASK initialized successfully when thismessage is issued:

HLD0002I hh:mm:ss.ttt z/Server for Taurus holder task ready for commands

After startup, it will contain command responses for modify commands directed at the holder.

SYSTSPRINTThis DD statement contains the messages issued by the holder task configuration component, prefixedDSC. If the holder address space terminates at startup, this is the first place to look for problems.

DSPPRTThis DD statement contains the output issued in response to a

F <holder>,DISPLAY,DSP,[FORMAT | DUMP]

command.

SchedulerA standard holder address space job log consists of the following DD names (example from JES2/SDSF):

NP DDNAME StepName ProcStep CrDate-CrTime O-Grp-N DSID Owner ZCOTSPRT TAURISPP mm/dd/jjjj hh:mm:ss 104 TAUUSR T0000005 TAURISPP mm/dd/jjjj hh:mm:ss 112 TAUUSR T0000004 TAURISPP mm/dd/jjjj hh:mm:ss 109 TAUUSR T0000003 TAURISPP mm/dd/jjjj hh:mm:ss 113 TAUUSR T0000002 TAURISPP mm/dd/jjjj hh:mm:ss 111 TAUUSR T0000001 TAURISPP mm/dd/jjjj hh:mm:ss 110 TAUUSR SYSTSPRT TAURISPP mm/dd/jjjj hh:mm:ss 103 TAUUSR SRVTASK TAURISPP mm/dd/jjjj hh:mm:ss 107 TAUUSR MAINTASK TAURISPP mm/dd/jjjj hh:mm:ss 106 TAUUSR LISTENER TAURISPP mm/dd/jjjj hh:mm:ss 105 TAUUSR MSGTASK TAURISPP mm/dd/jjjj hh:mm:ss 104 TAUUSR JESYSMSG mm/dd/jjjj hh:mm:ss 4 TAUUSR JESMSGLG mm/dd/jjjj hh:mm:ss 2 TAUUSR JESJCL JES2 mm/dd/jjjj hh:mm:ss 3 TAUUSR CMDTASK TAURISPP mm/dd/jjjj hh:mm:ss 108 TAUUSR


MAINTASKThis DD statement contains the messages issued by MAINTASK running in the scheduler address space.It shows the important configuration during initialiazation and addresses for important control blocks, allwritten during startup of the address space.

LISTENERThis DD statement contains the messages issued by LISTENER running in the scheduler address space. Itshows the important configuration settings and addresses for important control blocks. LISTENER issuccessfully initialized when this message is issued:

TAU0141I hh:mm:ss.ttt z/Server listener READY for clients


After startup, LISTENER shows which worker task T000000x was posted to fulfil the client request and theIP address of the client.

MSGTASKThis DD statement contains the messages issued by MSGTASK running in the scheduler address space.MSGTASK can be used to queue an input message for a scheduler to a USS message queue. A queuedmessage is not processed immediately but rather written to a USS message queue. The QID and aresponse token are returned to the client. The client can read the result at any time. The queue id of ascheduler can be determined through the dataspace space.

CMDTASKThis DD statement contains the messages issued by the command task running in the scheduler addressspace. During startup, important control block addresses, configuration parameters used, command exitnames and the name of the command REXX exec are listed. The command task successfully initializedwhen this message is issued:

TAU0107I hh:mm:ss.ttt Registration for exception handler >>TAURIP86<< successful.

After startup, it will contain command responses for modify commands directed at the scheduler.

SRVTASKThis DD statement contains the messages issued by the service task running in the scheduler addressspace. During startup, important control block addresses and configuration parameters used are listed. Theservice task successfully initialized when this message is issued:

TAU0107I hh:mm:ss.ttt Registration for exception handler >> TAURIP86<< successful.

T000000xThe DD statements named T0000001 to T000000n with n=NUMTCB from the scheduler configurationcontain the messages issued by the numbered working task running in the scheduler address space.These tasks get woken up by the main task to fulfil the requests coming in from clients.

During startup, important control block addresses and configuration parameters used are listed. Theworker task successfully initialized when this message is issued:

TAU0142I hh:mm:ss.ttt z/Server subtask READY for clients

After startup, it shows which client the worker task was active for. First it acknowledges that it was activatedand then it lists what it was activated for. A typical example would look like this:

TAU0023I hh:mm:ss.ttt Subtask for z/Server activated SLR0107I hh:mm:ss.ttt Deferred LOGON for user userid successful

SYSTSPRTThis DD statement always contains

IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED

ZCOTSPRTThis DD statement contains messages issued by REXX.


User serverDetermine the name of the user server that had a problem. That name consists of the TSOE_JOBPREFIXparameter from the configuration file, followed by the TSO user ID. Depending on the activity of the client,there may be more than one STC job log with the same name, but different JES job IDs.

A standard user server job log consists of the following DD names (example from JES2/SDSF):

NP DDNAME StepName ProcStep CrDate-CrTime O-Grp-N DSID Owner ZCOTSPRT IVPISPF mm/dd/jjjj hh:mm:ss 7 106 TAUUSR T0000001 IVPISPF mm/dd/jjjj hh:mm:ss 2 113 userid SYSTSPRT IVPISPF mm/dd/jjjj hh:mm:ss 7 105 TAUUSR SYSPRINT IVPISPF mm/dd/jjjj hh:mm:ss 5 111 userid SYSPRINT IVPISPF mm/dd/jjjj hh:mm:ss 8 116 userid SRVTASK IVPISPF mm/dd/jjjj hh:mm:ss 4 115 userid MAINTASK IVPISPF mm/dd/jjjj hh:mm:ss 3 112 userid LISTENER IVPISPF mm/dd/jjjj hh:mm:ss 3 105 userid JESYSMSG mm/dd/jjjj hh:mm:ss 7 4 TAUUSR JESMSGLG mm/dd/jjjj hh:mm:ss 7 2 TAUUSR JESJCL JES2 mm/dd/jjjj hh:mm:ss 7 3 TAUUSR ISPLOG IVPISPF mm/dd/jjjj hh:mm:ss 7 103 TAUUSR CMDTASK IVPISPF mm/dd/jjjj hh:mm:ss 6 114 userid


MAINTASKSame as scheduler.

LISTENERSame as scheduler.

CMDTASKThis DD statement contains the messages issued by the command task running in the user server addressspace. During startup, important control block addresses and used configuration parameters are listed. Thecommand task successfully initialized when this message is issued:


After startup, it will contain command responses for modify commands directed at the scheduler.

SRVTASKThis DD statement contains the messages issued by the service task running in the user server addressspace. During startup, important control block addresses and configuration parameters used are listed. Theservice task successfully initialized when this message is issued:


T0000001The DD statement T0000001 contains the messages issued by worker task number one running in theuser server address space. This task gets woken up by the main task to fulfil the requests coming in fromclients.

If the parameter NUMTCB in the user server configuration is bigger than one, there is more than oneworker task.


During startup, important control block addresses and configuration parameters used are listed. Theworker task successfully initialized when this message is issued:

TAU0142I hh:mm:ss.ttt z/Server Subtask READY for clients

After startup it shows which client the worker task was active for. First it acknowledges that it was activatedand then it lists what it was activated for. A typical example would look like this:

TAU0023I hh:mm:ss.ttt Subtask for z/Server activated TAU0059I hh:mm:ss.ttt TAUZCAPP ended. RC : 00000000

SYSTSPRTThis DD statement contains the output from any REXX exec run in the user server address space. Forinstance, this can be trace output.

ZCOTSPRTThis DD statement contains messages issued by REXX when the so-called ZCOM environment gotaddressed by the REXX exec running.

SYSPRINTThe two SYSPRINT DD statements contain the output from the IEBCOPY operation that copies the ISPFprofile, one during startup, the other during shutdown, assuming that the provided samples for IVPINIT1/2were used.

ISPLOGThis is the ISPF transaction log showing the ISPF commands issued in this user server address space.

Trace levelThe trace level of an address space specifies how many messages are written to the JESx spool to detailthe code paths taken for debugging purposes.

The trace level for all three types of address spaces is specified using the configuration parameterIPTRACE and by default is set to zero. This means that only required messages are written to job log tofollow the operation of z/Server to minimize the amount of output generated on the JESx spool.

The IPTRACE level can be dynamically changed using the command

F <holder|scheduler|userserver>,TRACE,LEVEL=x

with x a number from zero to six.

If a problem occurs, most of the time it will be necessary to increase the trace level to a higher setting,generating more messages that can serve as a debugging aid for SupportLine, reproduce the problem andthen dynamically decrease the trace level again.

Be aware that trace levels five and six can generate a huge amount of data, depending on the amount ofwork done in z/Server and the number of users. Indiscriminate use of the higher trace levels can lead tosevere JESx spool shortages.

Required information for SupportLineIn case of problems that cannot be solved by using the documentation provided in this book and looking upthe relevant messages, return and reason codes in the IBM documentation, please provide the following:1. A problem description that includes what the client has done in which order, so SupportLine has a

chance to try and reproduce the problem.2. The full job logs of all address spaces involved in the problem (scheduler job log, all user servers' job

logs - this can be more than one).


3. Any dump that occurred (system dump, CEEDUMP, so-called ZCOMDUMP).4. Preferably all configuration parameters specified for holder, scheduler and user server.


Documents

zServer Messages and Diagnostics - Micro Focus...zServer Messages and Diagnostics Introduction This document provides a description of messages issued by z/Server including possible