z/Server Messages and Diagnostics · Errors that indicate an internal z/Server error, such as API0007E (error during call to ... 13 ... API0065I [001] After call [002] RC: [003] ERRNO:

z/Server Messages and

Diagnostics

z/Server Messages and Diagnostics

Page: 2

Micro Focus

The Lawn

22-30 Old Bath Road

Newbury, Berkshire RG14 1QN

UK

http://www.microfocus.com

http://www.microfocus.com/


Page: 3

Copyright © 2011-2012 Micro Focus. All rights reserved.

MICRO FOCUS and the Micro Focus logo are trademarks or registered

trademarks of Micro Focus or its subsidiaries or affiliated

companies in the United States, United Kingdom and other countries.

All other marks are the property of their respective owners.


Page: 4

Contents

1 Introduction .............................................................................................................................................................. 8

1.1 Message format ................................................................................................................................................ 8

1.2 Error message example ............................................................................................................................... 10

1.3 Warning message example .......................................................................................................................... 10

1.4 Information message example .................................................................................................................... 12

2 Problem reporting ................................................................................................................................................. 13

3 List of messages ..................................................................................................................................................... 14

3.1 API - Application Programming Interface ................................................................................................ 14

3.2 BND - IEWBIND (Binder) Interface ........................................................................................................ 16

3.3 CSI - Catalog Search Interface ................................................................................................................... 17

3.4 DSC - Holder Task Configuration ............................................................................................................ 26

3.5 EMC - Extended Master Console Interface ............................................................................................ 28

3.6 HLD - Holder Task Interface ..................................................................................................................... 32

3.7 IPC - Command Task ................................................................................................................................... 39

3.8 JES - Job Entry System Interface ................................................................................................................ 45

3.9 LIC - License Interface ................................................................................................................................. 48

3.10 REC - Recovery Exception Handler ....................................................................................................... 50

3.11 REX - REXX Interface ............................................................................................................................... 53

3.12 SJB - Started Job .......................................................................................................................................... 64

3.13 SLR - TSO Scheduler Interface ................................................................................................................ 65

3.14 SPR - Standard Pool Routine .................................................................................................................... 87

3.15 SRV - Server Interface ............................................................................................................................... 90

3.16 STA - Started Task Interface .................................................................................................................... 91

3.17 TAU – Eclipse Client Interface ................................................................................................................ 92

3.18 UNI - Unicode code conversion services .......................................................................................... 112


Page: 5

3.19 XML - XML System Parser Interface .................................................................................................. 114

4 Troubleshooting ................................................................................................................................................. 118

4.1 Common steps ............................................................................................................................................ 118

4.1.1 Invoke SDSF ......................................................................................................................................... 118

4.1.2 Specify the filter .................................................................................................................................. 118

4.2 User Server case ........................................................................................................................................ 118

4.2.1 Specify the appropriate jobname prefix ........................................................................................ 118

4.2.2 Enter command ................................................................................................................................... 120

4.2.3 Select the appropriate job ................................................................................................................ 120

4.2.4 Select the required DDNAME ........................................................................................................ 120

4.3 ISPF Scheduler case .................................................................................................................................... 120

4.3.1 Specify the appropriate jobname prefix ........................................................................................ 120

4.3.2 Enter command ................................................................................................................................... 121

4.3.3 Select the appropriate job ................................................................................................................ 121

4.3.4 Select the required DDNAME ........................................................................................................ 121

4.3.5 Extract from the selected log file ................................................................................................... 122

4.4 Setting the trace level ................................................................................................................................ 127

4.5 Gathering information for the Micro Focus SupportLine ................................................................. 127

5 z/Server commands ........................................................................................................................................... 130

5.1 Display the configuration .......................................................................................................................... 130

5.2 Display Dataspace Information ............................................................................................................... 133

5.3 Set the Trace Level Dynamically............................................................................................................. 134

5.4 Server output files ...................................................................................................................................... 137

6 Bibliography ......................................................................................................................................................... 139

6.1 Associated manufacturer publications ................................................................................................... 139

6.2 Associated Enterprise Developer+ publications ................................................................................. 141

7 Appendix 1 - Understanding the trace output ............................................................................................ 142


Page: 6

7.1 Main task....................................................................................................................................................... 142

7.1.1 Initialization .......................................................................................................................................... 142

7.2 User task ...................................................................................................................................................... 167

7.2.1 Initialization .......................................................................................................................................... 168

7.2.2 Termination ......................................................................................................................................... 170

7.3 Command task ............................................................................................................................................ 170

8 Appendix 2 - z/Server Message Driver ......................................................................................................... 175

8.1 Scenario1 - Invoking a REXX Exec (detailed description) ............................................................... 175

8.1.1 Invocation XML ................................................................................................................................... 175

8.1.2 Invoked REXX exec (TESTRX) ....................................................................................................... 175

8.1.3 Invocation sequence .......................................................................................................................... 176

8.2 Scenario 2 - Invoking commands ............................................................................................................ 191

8.2.1 Invocation XML ................................................................................................................................... 192

8.2.2 FullConv output .................................................................................................................................. 192

8.3 Scenario 3 - Simulating an error ............................................................................................................. 193

8.3.1 Invocation XML ................................................................................................................................... 194

8.3.2 FullConv output .................................................................................................................................. 194

8.4 Scenario 4 - Forcing an abend (abnormal end) ................................................................................... 195

8.4.1 Invocation XML ................................................................................................................................... 195

8.4.2 FullConv output .................................................................................................................................. 195

9 Appendix 3 - Debugging scenarios ................................................................................................................. 197

9.1 Scenario 1 - Error returned by an invoked service ........................................................................... 197

9.1.1 JES0003E message investigation ...................................................................................................... 197

9.1.2 REC0001E message investigation ................................................................................................... 198

9.2 Scenario 2 - Parsing error ........................................................................................................................ 198

9.3 Scenario 3 - Catalog error ....................................................................................................................... 198

9.4 Scenario 4 - RACF validation error ....................................................................................................... 199


Page: 7


Page: 8

1 Introduction

This document provides a description of messages and possible corrective messages displayed by

z/Server.

z/Server displays various messages for many situations. Every message has an 8-character

identification and an associated text explanation.

Troubleshooting often requires knowledge of configuration settings, such as the name of the Holder

task, the Scheduler task, and the user server job. Refer to the z/Server Installation Guide for details

of these settings.

1.1 Message format

The 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

BND IEWBND (Binder) Interface

CSI Catalog Search Interface

EMC Extended Master Console Interface

HLD Holder task Interface

IPC Command Task

JES Job Entry System Interface

LIC License Interface

REC Recovery Facility

REX REXX Command Environment

SJB Started Job Interface


Page: 9

ID z/Server component

SLR TSO Scheduler Interface

SPR Standard Pool Routine

SRV Server Interface

STA Started Task Interface

TAU Eclipse Client Interface

UNI Unicode Conversion Services

XML XML System Parser Interface

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

unique only within the component.

s The message severity:

I Information

W Warning

E Error

S Severe error

Information messages are normally only used for tracing or debugging purposes. Errors normally

apply only to the associated service and are typically caused by incorrect arguments. Severe errors

normally concern z/Server and may require it to be restarted.

The associated message description provides detailed information that normally serves to identify

the cause of the message. Many of the message descriptions in this document contain placeholders

([mmm], where mmm is a running number; for example, [002] is the second placeholder) that are

replaced with the specific values.

The message description may contain messages, return codes, etc. passed from invoked services (for

example, the XML System Parser, Language Environment). In such cases, you should consult the

appropriate IBM manuals for details of the problem.

With very few exceptions, the first placeholder ([001]) of each message is the timestamp when the

message was issued (hh:mm:ss.ttt):

hh hour

mm minute

ss seconds

ttt milliseconds


Page: 10

1.2 Error message example

Error messages have severity E or S. Such issued messages are normally displayed on the desktop.

There are three general classes of error:

Errors caused by incorrect user input, such as incorrect password (SLR0071E) or filter did

not find any datasets (CSI0051E). Such errors can be rectified by correcting the input and

retrying the action.

Errors that indicate problems in the configuration file, such as EMC0011E (port is not

available). Such errors may be able to be rectified by correcting the configuration (a task for

the system administrator) although they can also indicate some other error that needs to be

investigated (also a task for the system administrator).

Errors that indicate an internal z/Server error, such as API0007E (error during call to

EZASOKET). Although z/Server is programmed fail-safe, errors may still occur. If the error

message information provided does not help identify the problem, please contact the support

hotline.

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

(=error).

The following message is displayed in the message table (column two):

CSI0051E [001] No datasets for filter [002] found

It has two placeholders: [001] and [002]. The placeholders are replaced with the timestamp and the

associated filter. An actual CSI0051E error message would look like this:

CSI0051E 07:48:53.935 No datasets for filter SOFXX found

The two placeholders have been replaced with the time (07:48) and the filter (SOFXX) that could

not be resolved. In this case, you could correct the error could by specifying a correct filter.

1.3 Warning message example

Warning messages have severity W. Such messages are normally written to the trace file, see Figure

1. Warnings normally indicate that some standard action has been taken; if this action or default is

not required, change the appropriate setting.

Note: Tracing must be activated to make the appropriate entry in the configuration file, for example,

IPTRACE=4.

TAU0019W 14:26:34.271 Environment-Variable REATTACH was not specified,

using defaults


Page: 11

TAU0019W 14:26:34.303 Environment-Variable CCSID was not specified,

using defaults

TAU0019W 14:26:34.303 Environment-Variable TSOE_SCHED_TAB was not

specified, using defaults

STA0006I 14:26:34.303 Value of Name/Token-Pair TAURSERZ

DSPALET : 01FF001C

DSPORIGIN : 00000000

DSPBLOCK : 0000000A

DSPFLAGS : 00000000

LIC0009I 14:26:34.309 Licence Flag 2 is : 7F

LIC0007W 14:26:34.365 This server may only be used through a licensed

client.

TAU0001I z/Server ZSOFAR V2R0M01 startup Sunday , 19 Aug 2012

14:26:34.36

REX0013W 14:26:34.371 A TSO/E-Environment already exists.

An additional dynamic Environment is not created.

Figure 1: Example trace output with warnings


Page: 12

1.4 Information message example

Information messages have severity I. Such messages are normally written in the trace file, see Figure

2.

Note: Tracing must be activated to make the appropriate entry in the configuration file, for example,

IPTRACE=4.

TAU0008I 09:22:51.31 Socket-Server-Subtask is initializing

TAU0025I 09:22:51.38 Inp-Msg-Area for subtask allocated at 22C36B20

Out-Msg-Area for subtask allocated at 22D36B28

Each area is 1048576 Bytes long

TAU0023I 09:22:59.99 Socket-Server-Subtask is awakened

TAU0015I 09:22:59.99 Socket-Trace TAKESOCKET

TAU0015I 09:23:00.50 Socket-Trace RECV

HDL0099I

=======================================================================

Data received

=======================================================================

Address Offset Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 7

22C36B20 00000000 C3C1D3D3 40404040 F1404040 C9D7F3D7 C7D44040 40404040

404040

22C36B40 00000020 40404040 40404040 40404040 00000058

TAU0015I 09:23:00.56 Socket-Trace RECV

HDL0099I

=======================================================================

Figure 2: Example trace output for information messages


Page: 13

2 Problem reporting

If you cannot solve the problem after following the troubleshooting measures described in this

document, the problem should be reported to the Micro Focus SupportLine using the procedure

described in chapter 4 .


Page: 14

3 List of messages

The following sections describe the z/Server messages, grouped for each facility and sorted

according to message number within the facility.

3.1 API - Application Programming Interface

All these messages are output by the TAURIP03 program. This program is used as API performs all

IP calls.

API0001I [001] Before call IP03 starting call in [002] environment

Function code: [003]

Task area: [004] [005]

Explanation: This is an informational message.

API0002I [001] After Call IP03 ending call. Rc is: [002]


API0007E [001] Error during call to EZASOKET

Function: [002]

Reason code: [003]

Explanation: See TCP/IP for MVS: API Reference for details.

User response: Contact the system administrator.

System administrator response: Check the logs; if necessary, contact the Micro Focus

SupportLine.

API0008I [001] Timeout for SELECT is [002] seconds and [003] microseconds.


API0009E [001] For function PeekMsg the sixth Parameter must be 'P'.

Explanation: Self-explanatory.

User response: Correct the CALL in the program.

System administrator response: None.API0010I [001] Using static z/Server environment for

client processing at address [002]



Page: 15

API0015I [001] Before call [002] descriptor in hex [003]


API0054S [001] Terminating subtask with dump




SupportLine.

API0065I [001] After call [002] RC: [003] ERRNO: [004]


API0069E [001] Function code [002] is not supported.


User response: Correct the program.

System administrator response: None.

API0072W [001] Connection is closed and no data are availableExplanation: Self-explanatory.

API0099I [001] ============

Explanation: This is a separator line for the list output.

API0106W [001] Negative length for receiving [002] Bytes specified. Multiple reads are forced

until specified length is reached!


API0107E [001] Function code [002] is not allowed in a server environment


User response: Correct the program.

System administrator response: None.API0108W [001] Delimiter [002] (hex) is specified.

Multiple reads are forced, until specified delimiter is found.


API0109I [001] 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


Page: 16


API0110I [001] Buffer size of client changed.


API0111I [001] Name of IP stack to be addressed changed to [002]


3.2 BND - IEWBIND (Binder) Interface

z/Server uses the IEWBIND service to process load modules (for details, see MVS Program

Management Advanced Features, form number SA22-7644-xx).

BND0001E [001] Error during call of IEWBIND with function [002]

Return code was: [003] hex

Reason code was: [004] hex

Explanation: The IEWBIND call failed Bibliography

Function: The IEWBIND function, for example, STARTD.

Return code: The IEWBIND function return code.

Reason code: The IEWBIND function reason code.



SupportLine.BND0002I [001] Binder Utility called with cmd [002]

for Dataset [003]

Member [004]

Class [005]

Section [006]


BND0003I [001] Binder Utility ended with RC [002]


BND0004E [001] Buffer with [002] bytes is to small for the binder interface. A minimum of [003]

bytes is required.Explanation: Self-explanatory.



Page: 17

System administrator response: Increase buffer size BUFFERSIZE and BUFFERUNIT

configuration parameters.

BND0005E [001] Unknown class [002] for binder utility.




SupportLine.

BND0006I [001] [002] and section [003]


3.3 CSI - Catalog Search Interface

z/Server uses the IGGCSI00 service to access the catalog (for details, see z/OS DFSMS Managing

Catalogs, form number SC26-7409-xx).

CSI0001E [001] Error during call of IGGCSI00

Return code is: [002] (hex)

Reason code is: [003] (hex)

Explanation: The IGGCSI00 service failed. Refer to message IDC3009I in the MVS System

Messages manual for more information on the return and reason codes.



SupportLine.

CSI0002I [001] ============


CSI0003E [001] Invalid entry type [002] found




SupportLine.

CSI0004I [001] Entry [002] from type [003] found



Page: 18

CSI0005I [001] Data for entry in hexadecimal: [002]


CSI0006I Catalog Utility called with command [002]

Dataset filter: [003]

Member filter: [004]

Catalog Flags: [005] (hex)

1... .... recall if dataset is migrated

.1.. .... return user data with member list

..1. .... wait for until recall of dataset is complete

...1 .... filter for MEMLIST specified

.... 1... member for GETDATA specified

.... .1.. create ENQ

.... ..1. create DEQ


CSI0007I [001] Entries found


CSI0008E [001] DYNALLOC failed for DDNAME [002]

Verb code: [003]

S99RC: [004]

S99ERROR: [005]

S99INFO: [006]

S99ERSN: [007]

Dataset: [008]

Explanation: The requested dataset could not be allocated. Consult the MVS Programming

Authorized Assembler Services Guide (DYNALLOC macro) for details of the returned information

(S99RC, etc.)



SupportLine.

CSI0009I [001] DSCB for DATASET [002]


CSI0010E [001] Empty dataset filter is not allowed


Page: 19


User response: Specify the correct filter.

CSI0011I [001] Member List utility called with dataset [002]


CSI0012E [001] Member valid for only datasets with DSORG=PO


User response: Perform a function on a member of a PO dataset.

CSI0013E [001] Obtain for DSCB information of dataset [002] failed with RC [003]




SupportLine.

CSI0014W [001] DSCB information or member for dataset [002] is not available because

dataset is migrated


CSI0015I [001] DSEB with length [001]


CSI0016E [001] HSM function [002] for dataset [003] failed with RC [004]

Explanation: ARCHRCAL macro call failed; consult ARC11xx for details of the return code.



SupportLine.

CSI0017I [001] Recall Utility called with dataset [002]


CSI0018I [001] Catalog Utility ended with RC [002]


CSI0019E [001] For command [002] the dataset type must be A and DSORG must be PO or

PS


Page: 20




SupportLine.

CSI0020E [001] For command [002] the record format must be F or V




SupportLine.

CSI0021E [001] A member must be specified for a partitioned dataset


User response: Specify the appropriate member.

CSI0022E [001] A member name must not be specified for a sequential dataset


User response: Do not specify a member.

CSI0023E [001] Dataset/member [002] is in use


User response: Wait until dataset/member becomes free.

CSI0024E [001] Buffer with size of [002] (hex) too small to hold all data. Read terminated after

[003] records.



System administrator response: Increase buffer size BUFFERSIZE and BUFFERUNIT

configuration parameters.

CSI0025E [001] Open of dataset for function [002] was not successful


User response: Retry later; if the problem continues, contact the system administrator.


Page: 21


SupportLine.

CSI0026I [001] GetData/PutData utility called with command [002] for dataset [003] and

member [004] and CCSID [005]


CSI0027I [001] GetData/PutData utility ended with RC [002]


CSI0028I [001] Data for PutData at address [002] with length [003] LRECL [004] RECFM

[005]


CSI0029E [001] Length for PutData is invalid. Length must be a multiple of [002]




SupportLine.

CSI0030W [001] Command task is busy. Enqueue/dequeue not possible.




SupportLine.

CSI0031I [001] RACROUTE REQUEST=AUTH failed with return code: [002] and reason:

[003]


CSI0032I [001] [002] records written successfully


CSI0033E [001] Fixed attribute is not allowed for variable record length




Page: 22


SupportLine.

CSI0034I [001] Dequeue scheduled to command task


CSI0035E [001] Request for shared access for Dataset [002]

failed because resource is in use exclusive by [003]




SupportLine.

CSI0036E [001] GQSCAN macro failed with RC [002]




SupportLine.

CSI0037E [001] [002] access for dataset [003] not permitted




SupportLine.

CSI0038E [001] Dataset [002] not migrated. Recall not allowed




SupportLine.

CSI0039E [001] Requested dataset unavailable The dataset is allocated to another job and its

usage attribute conflicts with this request.



Page: 23

User response: Wait until dataset becomes free.

CSI0040I [001] HSM function [002] for dataset [003] ended successful


CSI0041I [001] HSM function [002] for dataset [003] successful queued. Nowait was specified.


CSI0042E [001] Submit dataset must be defined with fixed length 80 (RECFM=F/FB and

LRECL=80)


User response: Either reallocate submit dataset or use dataset with the correct attributes:

RECFM=F/FB and LRECL=80.

CSI0043I [001] Job with Jobid [002] submitted


CSI0044E [001] ISPF packed format is not supported


User response: Use a dataset that does not have ISPF packed format.

CSI0045E [001] Invalid token [002] in compressed record found




SupportLine.

CSI0046E [001] LRECL of uncompressed record with [002] bytes is greater than LRECL with

[003] bytes


User response: Dataset is probably corrupt; recreate the dataset.

CSI0047E [001] Binder information is only allowed for datasets with RECFM=U


User response: Do not use this function for datasets that do not have RECFM=U.

CSI0048E [001] Length of JCL or REXX is invalid. Length is zero or not a multiple of 80.


Page: 24


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

CSI0049I [001] Job with jobid [002] submitted successfully


CSI0050E [001] For PUTJCL an ACEE for userid [002] is required on the TCB

Explanation: You must activate task level security in the IP header.



SupportLine.

CSI0051E [001] No datasets for filter [002] found


User response: If necessary, correct the filter specification.

CSI0052E [001] Generic filter is not allowed for command [002]


User response: Correct the filter specification.

CSI0053E [001] Entry [002] returned with error code [003]




SupportLine.

CSI0054I [001] Find utility called for member [002].

Function flags:[003]


CSI0055E [001] No datasets specified for command [002]


User response: Specify a dataset.

CSI0056E [001] DESERV macro with function [002] ended with RC [003] and reason [004]

Explanation: DESERV macro call failed Bibliography for details of the return code.


Page: 25



SupportLine.

CSI0057W [001] Member [002] not found



CSI0058E [001] Dataset [002] is migrated. Command [003] not possible.


User response: Do not use this function on a migrated dataset.

CSI0059E [001] Dataset saved but at least one record was truncated to [002] bytes


User response: Validate the dataset definition; if necessary, contact the system administrator.


SupportLine.

CSI0060E [001] An invalid filter key was provided.

Filter was: [002]


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

conventions.

CSI0061I [001] Encrypting data to BASE64


CSI0062I [001] Decrypting data from BASE64


CSI0063E [001] Encrypt/Decrypt for BASE64 failed. See message log for more information.




SupportLine.


Page: 26

3.4 DSC - Holder Task Configuration

These messages are issued when the configuration file for the holder task IVPHOLD contains invalid

statements.

DSC0001 E Name required for Variable [001]

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

System administrator response: Correct the statement in error.

DSC0002 E Name for [001] is greater than 8 Bytes

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


DSC0003 E 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.


DSC0004 E 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.


DSC0005 E Value for Variable [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


DSC0008 E Name required for Variable [001]


Page: 27

Explanation: Variable [001] is one of the following: Dsp_Token or Con_Token


DSC0009 E Name for [001] is greater than 16 Bytes

Explanation: Variable [001] is one of the following: Dsp_Token or Con_Token


DSC0020 E DSP_PORT_HIGH is not greater than DSP_PORT_LOW



DSC0022 E Servername <Server.x> has more than 8 chars



DSC0023 Parameter IPTRACE not a whole number. IPTRACE ignored



DSC0024 Parameter DELAY not a whole number. Default used



DSC0025 Parameter DELAY out of range. Default used



DSC0026 W Max. of 7 Servers reached. No further servers started


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

DSC0027 E Dsp_Max_Serv should be at least [001] Unable to start all requested servers

Explanation: The number of schedulers specified via Server.x statements exceeds the number of

schedulers allowed for this holder task. Startup is terminated.

System administrator response: Increase the value for DSP_MAX_SRV to at least [001].


Page: 28

DSC0099 I Config of zServer Holder-Task started


DSC0099 I Config of zServer Holder-Task ended with RC [001]


DSC0100 E Error during Interpret Config-File RC [001]


DSC0101 I Line [001]


DSC0102 I Config [001]


DSC0200 E 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.


3.5 EMC - Extended Master Console Interface

These messages are used only when CONSOLE=1 is defined in the configuration, and they are

output by the TAURIP56 Console Utility.

EMC0001E [001] [002] for Extended-Master-Console failed

Major name: [003]

Minor name: [004]




SupportLine.

EMC0002I [001] Command for extended master console [002]


EMC0003E [001] SVC failed for function [002] with RC [003] (hex)


Page: 29



Function (low-order byte):

X'01' RACROUTE

X'02' SSICALL

X'03' CMD for ECMD

X'04' Internal start

X'06' Activate Extended Master Console

X'07' Deactivate Extended Master 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

X'E0' Get response from master console

Return code:

0-250 RACF 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 SVC routine

255 Address Space has no ACEE

256 Invalid function code

257 Console buffer is too small


Page: 30


SupportLine.

EMC0004E [001] Function [002] for extended master console failed with

IPSCA_CONSRC: [003] (hex)

IPSCA_CONSRE: [004] (hex)


Function (low-order byte), see EMC0003E.


System administrator response: Check the extended master console.

EMC0005I [001] Response from extended master console is [002] lines


EMC0006E [001] Extended master console was not activated



System administrator response: Activate the extended master console.

EMC0007E [001] [002] is not a valid function for interface ECMS




SupportLine.

EMC0008I [001] Waiting for [002] milliseconds


EMC0009I [001] Routine for extended master console invoked with function [002] (hex)


EMC0010W [001] Port check for port [002] skipped because extended master console was not

activated




Page: 31

System administrator response: Activate the extended master console.

EMC0011E [001] Port [002] is not available



System administrator response: Check configuration file (PORT parameter).

EMC0012E [001] Console buffer with size of [002] KB is too small to hold command response



System administrator response: Increase size of buffer in the configuration file (BUFFERSIZE /

BUFFERUNIT parameters).

EMC0013I [001] No REXX or LE program for postprocessing specified


EMC0014E [001] REXX or program flag is invalid [002]

Explanation: Specify X'01' for REXX or X'02' for an LE program.



SupportLine.

EMC0015I [001] [002] [003] used for postprocessing a command response


EMC0016I [001] Call [002] for postprocessing of command response


EMC0017I [001] [002] ended with RC [003]


EMC0018I [001] Using cart [002] for command and response


EMC0019I [001] Using area at address [002] for response


EMC0020I [001] Internal console buffer allocated at address [002]


Page: 32


EMC0021I [001] Internal console buffer at address [002] released


EMC0022E [001] Console command has invalid length of [002] (hex)

Console command length must be greater than zero and less than 126.




SupportLine.

EMC0023E [001] Portcheck unsuccessful because console utility failed

Explanation: This may be a temporary problem for RC=8 (ENQ).



SupportLine.

3.6 HLD - Holder Task Interface

Holder task messages provide information about the data space and the SVC.

HLD0001I [001] [002] holder task [003] startup


HLD0002I [001] [002] holder task ready for commands


HLD0003I [001] Creating data space

Data space name: [002]

Data space size: [003] blocks

Data space storage key: [004]


HLD0004I [001] Writing name-token pair [002]

DSPALET: [003]

DSPORIGIN: [004]


Page: 33

DSPBLOCK: [005]

DSPFLAGS: [006]


HLD0005I [001] Deleting ALET


HLD0006I [001] Deleting name-token pair


HLD0007I [001] Deleting data space


HLD0008E [001] Function [002] failed with RC [003] and Reason [004]

=========================================================

Function RC/RS from Macro

=========================================================

Create/Delete Dataspace DSPSERV

Create/Delete Alet ALESERV

Delete User-SVC SVCUPDTE

Activate/Deactivate Console MSCOPER

Create Name/Token IEANTCR

Delete Name/Token IEANTDL

See Assembler-Services-Reference for more information

Explanation:

Self-explanatory.


System administrator response: Check the appropriate IBM documentation for the return and

reason code.

HLD0009I [001] TSO environment created successfully.

A (Command Processor Parameter List): [002]


Page: 34


HLD0010E [001] Creation of TSO environment failed

Return code: [002]

Reason code: [003]

Abend code: [004]

Explanation: The IKJTSOEV service failed REX0015E for details.

User response: Retry later or contact the system administrator if the problem continues.


SupportLine.

HLD0011I [001] Data space additional parameters

Collect statistics: [002]


HLD0012I [001] Creating partition [002] at address [003]


HLD0013E [001] SVC routine [002] could not be loaded.

System completion code: [003]

Return code: [004]

Explanation: LOAD or DELETE of the SVC routine failed Bibliography for details



SupportLine.

HLD0014E [001] ENQ failed: another copy of IPSHOLD is currently installing the same SVC


User response: Retry later or contact the system administrator if the problem continues.

System administrator response: Check who is using the SVC. If necessary use a different SVC

number.

HLD0015E [001] Install of SVC [002] failed with RC [003]

Explanation: Self-explanatory; SVCUPDTE failed Bibliography for details



Page: 35


SupportLine.

HLD0016W [001] SVC [002] with current entry address [003] will be replaced with new entry

address [004]. Waiting for console reply.


HLD0018I [001] Installing user SVC


HLD0019I [001] User SVC [002] installed successfully.

Program: [003] entry-point address: [004]


HLD0020I [001] Console reply was [002]


HLD0021I [001] Creating a common data space


HLD0022I Creating EMCS-Console [001]


HLD0024I [001] Activate for master console [002] successful

Console ID: [003]

Console CSA: [004]

Console Message ECB: [005]

Console ALET: [006]


HLD0025I [001] Function [002] ended successfully


HLD0026I [001] Cleanup user SVC


HLD0027I [001] Cleanup data space



Page: 36

HLD0028I [001] Cleanup console


HLD0029I [001] User administration called with function [002].

Flag: [003]

1... .... called from holder task

.1.. .... use data space


HLD0030I [001] User administration ended with RC [002] (hex)


HLD0031I [001] User data on entry


HLD0032I [001] User data on exit


HLD0033I [001] Server information

Lowest port over all servers: [002]

Highest port over all servers: [003]

Maximum numbers of servers: [004]


HLD0034I [001] [002] Holder task shutdown


HLD0035I [001] Initializing data space for user administration


HLD0036E [001] Unexpected RC [002] from user administration


Return code:

08 Init function not valid. Init is allowed from holder task if a data space is used or from a server

if local storage should be used

12 Size of data space or size of local area is not large enough to hold all required tables

20 Invalid function


Page: 37



SupportLine.

HLD0038E [001] Data space too small for user administration

Specify at least [002] blocks for DSP_SIZE



System administrator response: Change the configuration file (DSP_SIZE parameter).

HLD0039I [001] Table allocated for internal user administration

Size: [002] bytes

Address: [003]


HLD0040E [001] Command [002] invalid for z/Server Holder-Task.

Explanation: The command issued against the holder task TAURHLD was invalid.

User response: Use a valid command.

HLD0041I [001] Calling Command-Rexx IPCMDHLD


HLD0042I [001] Command-Rexx IPCMDHLD endet with RC [002]


HLD0043I [001] Answer from REXX IPCMDHLD is :


HLD0044I [001] z/Server Holder-Task received command [002]

Explanation: The command [002] was issued against the holder task. This is an informational

message.

HLD0045E [001] Command [002] for z/Server Holder-Task contains invalid syntax.


HLD0046E [001] Scheduler [002] does not exist.


HLD0047I [001] Stopping [002] user server for scheduler [003]


Page: 38


HLD0048I -----------------------------------------------------------

Starting Server

-----------------------------------------------------------


HLD0049I [001] Starting server [002]


HLD0050I -----------------------------------------------------------

Stopping Server

-----------------------------------------------------------


HLD0051I [001] Stopping server [002]


HLD0052I [001] Stopping user server for user [002] and scheduler [003] with jobid [004] and asid

[005]


HLD0053E [001] Scheduler [002] already in table. ADD not processed.


HLD0054I [001] Force user server for user [002] and scheduler [003] with jobid [004] and asid [005]


HLD0063I [001] Scheduler [002] locked


HLD0064I [001] Scheduler [002] unlocked


HLD0065I [001] [002] schedulers locked


HLD0066I [001] [002] schedulers unlocked


Page: 39


HLD0067E [001] ASID [002] not associated with a user server. STOP command ignored.


HLD0068E [001] Max. count of [002] schedulers reached.

Scheduler [003] not started.

Increase value for DSP_MAX_SERV


System administrator response: In the holder task configuration, increase the value for

DSP_MAX_SERV.

HLD0069I [001] Holder-Task configuration

Delay......... : [002] seconds

Trace-Level....: [003]


HLD2001W SVC not available O=Override,C=Cancel

Explanation: When the SVC routine was established, z/Server detected that the SVC number is

already in use. It may have been left from a previous unclean shutdown of the holder task. It may

also be that the specified SVC number is in use by another product unrelated to z/Server.

System administrator response: Reply to this message either by forcing the use of the specified

SVC number (O=Override) or cancel startup of the holder task by specifying C.

3.7 IPC - Command Task

Messages used for the Command Task command processing.

IPC0001W [001] PPT invalid syntax




SupportLine.

IPC0002W [001] PPT does not exist



Page: 40



SupportLine.

IPC0003W [001] Invalid length specified for module name




SupportLine.

IPC0004W [001] Module [002] not in PPT



System administrator response: Include the specified module in the PPT.

IPC0005I [001] Task [002] scheduled for delete request of [003]


IPC0006W [001] Could not delete PPT for program [002] because task [003] has completed




SupportLine.

IPC0007W [001] Could not delete PPT for program [002] because task [003] is busy


User response: Wait until resource becomes free.

IPC0040I [001] z/Server command task is initializing


IPC0042I [001] Address of Communication Event Control Block: [002]

Address of Command input buffer: [003]

Token: [004]



Page: 41

IPC0043I [001] Command task invoked with [002] command


IPC0044I [001] Data for command: [002]


IPC0052I [001] Shutdown


IPC0061I [001] Command [002] unknown, no action performed


IPC0062I [001] Kill invalid syntax


User response: Enter the correct syntax f <servername>,kill,task=nnn

IPC0063I [001] Requested task number does not exist


IPC0064I [001] Scheduling [002] request to main task

IP address: [003]

Port: [004]


IPC0065E [001] Trace invalid syntax, not f servname,trace,level=0-6


User response: Enter the correct syntax f <servername>,trace,level=0-6

IPC0066I [001] Trace level changed to [002]


IPC0067E [001] Invalid reattach syntax


User response: Enter the correct syntax f <servername>,reattach,task={nnn|all}

IPC0068I [001] Checking whether port [002] is available



Page: 42

IPC0069E [001] Port [002] is not available

Port being used by: [003]

Connection ID: [004]

State: [005]


User response: Wait until the port becomes available; if the problem continues, contact the

system administrator.

System administrator response: Change configuration file (PORT parameter). Check the logs; if

necessary, contact the Micro Focus SupportLine.

IPC0070E [001] Call to Netstat was not successful

See SYSTSPRT for more information




SupportLine.

IPC0071I [001] Using command exit [002]


IPC0072E [001] Invalid RDz command syntax




SupportLine.IPC0073I [001] Calling command exit [002] with data [003]


IPC0074I [001] Using REXX command [002]


IPC0075I [001] Calling REXX command [002]


IPC0076I [001] REXX command [002] ended with RC [003]



Page: 43

IPC0077E [001] Call to IP03 ended with RC [002]




SupportLine.

IPC0079I [001] Compress level changed to [002]


IPC0080I [001] Address: [002]

Size: [003]

TCB :[004]

Name: [005]


IPC0081E [001] Invalid recovery syntax


User response: Enter the correct syntax.

IPC0082I [001] Recovery changed to [002]


IPC0083E [001] Invalid REFRESH syntax


User response: Enter the correct syntax: f <servername>,refresh,pgm=nn (nn = 02-99)

IPC0084I [001] Response from REXX: [002]


IPC0085E [001] Invalid dump syntax


User response: Enter the correct syntax:

f <servername>,dump,area=all

f <servername>,dump,addr=…,len=…

f <servername>,dump,svcd

f <servername>,dump,config


Page: 44

IPC0086W [001] 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




SupportLine.

IPC0087E [001] Invalid REXX syntax


User response: Enter the correct syntax.

f <taskname>,rexx,[ts|te|ht,rt,hi],subtask=[nn|all]

IPC0088E [001] SVC dump not possible because user server was not configured for a user

SVC.



System administrator response: Change configuration file SVC_NO parameter.

IPC0090I [001] Initial configuration settings at address [002]


IPC0091I [001]


IPC0094I S= [001] [002] [003]

Explanation: This is a command response for a f servername,display,grs command.

IPC0095I SysName JobName Asid TCBAddr EXC/SHR Status


IPC0096I [001] [002] [003] [004] [005] [006]


IPC0097E [001] Invalid syntax for DEQ command


Page: 45


User response: Specify the command correctly.

IPC0098I [001] Current Virtual-Storage-Map for server [002] printed to ddname

CMDTASK.Explanation: This is an informational message.

IPC0099I [001] Resource [002] not held by [003]

Explanation: This is a command response. The queried resource is not held by this scheduler or

user server.

3.8 JES - Job Entry System Interface

The JES Interface is used to process SYSOUT.

JES0001I [001] JES Utility called with command [002]


JES0002I [001] JES Utility ended with RC [002]



Page: 46

Return code:

16 Invalid function

20 SSI call failed

24 No filter specified

28 Dynalloc failed, see LE message file for more information

32 Dataset open failed

36 Buffer too small to hold XML document

JES0003E [001] SSI call for function code [002] failed with RC [003]

SSOBRETN: [004]

Reason: [005]

Functíon code:

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

RC: IEFSSREQ invocation return code. A non-zero return code indicates that a passed parameter

was not valid, for example, 8 = subsystem exists but is not active).

SSOBRETN and Reason are the return code and reason code returned by the invoked service.

SSOBRETN for function 80:


Page: 47

4 The search arguments, though syntactically valid, cannot be used (for example, specifying a

volume serial in STATVOL that is not being used as a SPOOL volume).

8 Logic error in one of the search arguments.

12 The request type in STATTYPE is not valid.

Explanation: IEFSSREQ failed.


System administrator response: IEFSSREQ macro error. Check the logs; if necessary, contact

the Micro Focus SupportLine.

JES0004E [001] No filter specified for function [002]


User response: Specify a filter. If necessary, contact the system administrator.


SupportLine.

JES0005E [001] DYNALLOC failed for DDNAME [002]

Verb code: [003]

S99RC: [004]

S99ERROR: [005]

S99INFO: [006]

S99ERSN: [007]

Dataset: [008]

Explanation: The requested dataset could not be allocated. Consult the MVS Programming

Authorized Assembler Services Guide (DYNALLOC macro) for details of the returned information

(S99RC, etc.).



SupportLine.

JES0006E [001] Open of dataset [002] failed




SupportLine.


Page: 48

JES0007E [001] Buffer sized [002] (hex) too small to hold all data Read terminated after [003]

records



System administrator response: Increase the buffer size.

JES0008I [001] [002] work units (JOES) deleted


JES0009I [001] Cancel command [002] accepted and routed to console


JES0010I [001] Stop command for job [002] accepted


3.9 LIC - License Interface

The use of z/Server requires a valid license. The License Interface performs the associated

processing.

LIC0001E [001] License key [002] not valid Reason is: [003]


User response: Request the system administrator to update the configuration with the correct

license key.

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


Page: 49

System administrator response: Update the configuration with the correct license key

(LICENCE_KEY parameter).

LIC0002W [001] This server is licensed for a specific LPAR



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

LIC0003I [001] Value after decrypt [002]


LIC0004W [001] License key expires in [002] days


User response: Request the system administrator to renew the license.

System administrator response: Renew the license.

LIC0005E [001] License key expired. Server stopped


User response: Request the system administrator to renew the license.

System administrator response: Renew the license.

LIC0006E [001] Feature for command [002] not licensed


User response: Request the system administrator to extend the license.

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

command.

LIC0007W [001] This server may only be used through a licensed client


User response: Use a licensed client.

LIC0008E [001] This server requires a version 2 header

You must specify COMPAT=2 for startup.




Page: 50

System administrator response: Correct the configuration file with COMPAT=2.

LIC0009I [001] License flag 2 is: [002]


LIC0010E [001] Licence violation: This server accepts only requests from an Eclipse client.


User response: Use an authorized client.

LIC0011I [001] Changing limited to authorized key information from client to scheduler

Old value was: [002]

New value is: [003]


3.10 REC - Recovery Exception Handler

The Recovery Exception Handler performs the clean-up processing of a Language Environment

exception to ensure an orderly job (task) termination. This processing involves tasks such as closing

open DCBs and other held resources for the associated job (task).

REC0001E [001] Recovery Exception Handler was invoked.

CIB-Flag-5: [002]

CIB-Flag-6: [003]

Explanation:

The two CIB (Language Environment Condition Information Block) flags have the following

meanings:

CIB Flag 5 (CEL events)

1 Abend caused

1 Program check caused

1 Condition management raised TIU (Termination Imminent due to Unhandled condition)

1 New condition result from a promote

1 Condition signaled

1 Attention interrupt caused

CIB Flag 6 (CEL actions)


Page: 51

1 Abend reason code valid

1 Math routine condition

1 Resume allowed

1 MRC type 1

1 Enable only pass

1 Hcursor pointing to owning SF

1 Doing post SF0 scan

1 All members informed of condition

This message is issued when IPTRACE level is greater or equal to 5.



SupportLine.

REC0003E [001] Error in program [002] at offset [003]

Original message was: [004]



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

SupportLine.

REC0004I [001] Checking for open files


REC0005I [001] DCB found


REC0006I [001] Open DCB found for DDName [002] and dataset [003]


REC0007I [001] DCB closed. RC was [002]


REC0008I [001] TIU or Promote call. No activities


Page: 52


REC0009E [001] Resume is not allowed. Subtask will terminate.




SupportLine.

REC0010W [001] Member not found


User response: Specify a correct member.

REC0011E [001] Data set or member already open for output by another user or job

Explanation: Self-explanatory (S213-30).

User response: Retry later.

REC0012E [001] Data set opened for output used all available space

Explanation: Self-explanatory (SD37-4).

User response: Reallocate the dataset with larger space attributes.

REC0013E [001] Insufficient access authority

Explanation: Self-explanatory (S913-38). For more Information, see message ICH408I in

JESYSMSG.



SupportLine.

REC0014W [001] Subtask not recovered. Error perculated to Language Environment.




SupportLine.

REC0015I [001] Cleanup for TSOE scheduler started



Page: 53

REC0016I [001] Extra buffer at address [002] freed


REC0017I [001] XML image at address [002] freed


REC0018I [001] Deleting ACEE for User [002] on TCB [003]


REC0019I [001] Checking for ACEE


3.11 REX - REXX Interface

z/Server uses various REXX services to process REXX execs (for details, see TSO/E REXX

Reference, form number SA22-7790-xx).

REX0001E [001] Error in variable access routine IRXEXCOM

Variable: [002]

Access: [003] <SHVCODE>

Response: [004] <SHVRET>

Explanation: The IRXEXCOM function failed TSO/E REXX Reference for details of the

returned information.



SupportLine.

REX0002I [001] Before calling variable access routine IRXEXCOM

Variable: [002]

Access: [003]

SHVVALA: [004] (hex)

SHVBUFL: [005] (hex)

SHVVALL: [006] (hex)

ENVBLOCK: [007] (hex)


REX0003I [001] After calling variable access routine IRXEXCOM

SHVRET: [002] (hex)


Page: 54

SHVVALL: [003] (hex)

RC: [004] (hex)


REX0004I [001] Host Command Environment (zComm) called with command [002]

Environment at address: [003]

Environment from subtask: [004]


REX0005E [001] Variable [002] not numeric


[002] The name of the variable



SupportLine.

REX0006E [001] Variable [002] contains invalid IP address


[002] The name of the variable



SupportLine.

REX0007I [001] Address of REXX Environment Block is [002]

User field: [003]


REX0008E [001] Call to IRXINIT with function [002] failed

Return code: [003] (hex)

Reason code: [004] (hex)

Explanation: The IRXINIT function failed TSO/E REXX Reference for details of the returned

information.

[002] IRXINIT function



Page: 55


SupportLine.

REX0009E [001] Call to IRXSUBCM with function [002] failed with RC [003] (hex)

Explanation: The IRXSUBCM function failed TSO/E REXX Reference for details of the returned

information.

[002] IRXSUBCM function

[003] IRXSUBCM return code



SupportLine.

REX0010E [001] Call to ISPEXEC with function [002] failed with RC [003] (hex)

Explanation: The ISPEXEC function failed z/OS ISPF Services Guide for meaning of the return

code.

[002] ISPEXEC function

[003] ISPEXEC return code



SupportLine.

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

Explanation: The ISPLINK function failed z/OS ISPF Services Guide for meaning of the return

code.

[002] ISPLINK function

[003] ISPLINK return code



SupportLine.

REX0012I [001] ISPF environment is not available or address of TLD0 could not be found



Page: 56

REX0013W [001] TSO/E environment already exists.

Additional dynamic environment is not created.




SupportLine.

REX0014I [001] TSO environment created successfully

(Command Processor Parameter List): [002]


REX0015E [001] Creation of TSO environment failed

Return code: [002]

Reason code: [003]

Abend code: [004]

Explanation: The IKJTSOEV service failed Bibliography for details of the reason code and

Abend code.

Return code:

8 TSO/E environment initialized, but could not initialize a REXX language processor

environment

16 The request for initialization was ignored because a TSO/E environment is being initialized or

has been initialized already at the request of another task in the same address space as the

calling program.

20 The request for initialization was ignored because the address space of the calling program

contains multiple job step control blocks (JSCBs). An application cannot use the TSO/E

environment service if it attached multiple job step tasks in its address space.

24 The request for initialization was ignored because the TSO/E environment service was

invoked from a TSO/E TMP and Service Routines environment.

32 The request for initialization was ignored because the caller is in cross-memory mode or

holding a lock.


Page: 57

36 TSO/E environment initialization unsuccessful.

40 TSO/E environment initialization unsuccessful. The TCB key of the caller's TCB does not

match the TCB key of the first non-system jobstep TCB in the address space.



SupportLine.

REX0016W [001] Variable [002] was not specified. Default value is assumed




SupportLine.

REX0017E [001] Eyecatcher for host command environment is invalid. Either the environment

is not available or damaged. This may happen if a reusable environment was not terminated.

Explanation: Self-explanatory; ZCOMM not specified as eyecatcher.



SupportLine.

REX0018E [001] Reusable Host Command Environment terminated because communication

area was invalid. Command for Host Command Environment (zComm) was not executed.




SupportLine.

REX0019S [001] Host Command Environment not initialized. You must initialize a static

environment for a TSO address space.



System administrator response: Contact the Micro Focus SupportLine.

REX0020I [001] Initializing a static z/Server environment for client processing


Page: 58


REX0021I [001] Terminating the static z/Server environment for client processing


REX0022E [001] Call to IRXEXCOM failed with RC [002] (hex)

Explanation: The IRXEXCOM function failed TSO/E REXX Reference for details of the

returned information.

[002] return code



SupportLine.

REX0023S [001] User field of environment block is zero. Invalid environment. Information for

subtask is not available.

Explanation: This is probably caused by storage being overwritten.


System administrator response: If the error can be reproduced, obtain a GTF trace and a SVC

dump of the address space. If the error cannot be reproduced, obtain a SVC dump and send it to

Micro Focus SupportLine.

REX0024I [001] Initialize z/Server for a [002] parallel REXX environment


REX0025E [001] z/Server is customized for a single REXX environment but more than one

subtask was found



System administrator response: Correct the configuration ( MULTI_REXX parameter).

REX0026I [001] ISPF is available

Address of TLD1: [002]

Address of TLD0: [003]


REX0027I [001] Host Command Environment ended with RC [002]


Page: 59


REX0028I [001] ISPF [002]


REX0029E [001] Invalid eyecatcher for control block [002] at address [003]

Explanation: Self-explanatory; TLD not specified as eyecatcher.


System administrator response: Possible internal error, contact the Micro Focus SupportLine.

REX0030E [001] ISPF table [002] not found




SupportLine.

REX0031I [001] Reading table [002] from row [003] to row [004]


REX0032E [001] Specified value for TBFROW [002] or TBTROW [003] is invalid or outside the

bounds of table [004] with [005] rows.




SupportLine.

REX0033I [001] Variable: [002]

Text: [003]


REX0034I [001] Row [002] of table [003] contains [004] savenames


REX0035E [001] CRP [002] for table [003] is invalid

Explanation: Self-explanatory; the CRP (current row pointer) lies outside the table bounds.



Page: 60


SupportLine.

REX0036I [001] CRP for table [002] is set to row [003]


REX0037I [001] RDA for row [002] at address [003] with EYE [004]


REX0038I [001] Creating a non-reentrant REXX environment for TSO/E and ISPF


REX0039I [001] Creating a reentrant REXX environment for REXX


REX0040I [001] Host Command Environment [002] added to environment block [003]


REX0041I [001] First 40 bytes of data: [002]


REX0042E [001] No search argument found for table [002]

Explanation: Self-explanatory; either no search argument specified or its eyecatcher is not

"SAWA".



SupportLine.

REX0043I [001] Number of entries in SAWA [002]


REX0044I [001] SAWA

Entry length of value for compare: [002]

Address of value for compare: [003]

Operator for compare: [004]

Index of variable name: [005]


REX0045I [001] Number of rows that match TBSCAN was [002]


Page: 61


REX0046I [001] Row match for TBSCAN


REX0047I [001] Table [002] not found via TLD1, trying TLD0


REX0048E [001] Invalid severity [002] for LogMsg command

Explanation: Self-explanatory; severity not I, W, E, S or U.



SupportLine.

REX0049E [001] More than 9 slots defined

Explanation: Self-explanatory; internal program restriction.



REX0050E [001] Value for slot [002] greater than 80 bytes




SupportLine.

REX0051E [001] Invalid format [002] for slot [003]

Explanation: Self-explanatory; format not A (ASIS), X (hexadecimal) or T (TIMESTAMP).



SupportLine.

REX0052E [001] Invalid options [002] specified for LogMsg

Explanation: Self-explanatory. Options > 255.



Page: 62


SupportLine.

REX0053I [001] [002]


REX0054E [001] Call to IRXEXEC failed with RC [002] (hex)

Explanation: The IRXEXEC function failed TSO/E REXX Reference for meaning of the return

code.

[002] IRXEXEC return code



SupportLine.

REX0055I [001] Internal REXX executor called with flag [002]


REX0056I [001] Searching for DSECT: [002]


REX0057E [001] DSECT [002] not found




SupportLine.

REX0058I [001] Number of DSECTs in table: [002]


REX0059I [001] [002] [003] [004] [005]


REX0060I [001] [002] variables in DSECT [003]


REX0062E [001] Address for DSECT [002] and length [003] invalid RC from VSMLOC: [004]

For RC=4

Storage not allocated in PVT


Page: 63

Storage overlaps free space

Storage overlaps other subpools


User response: Used address must be in private storage.


REX0063I [001] DSECT Utility called with function [002]


REX0064I [001] Varpool Utility called with function [002]


REX0065E [001] Call to SPR failed with RC [002]

Explanation: Standard Pool Routine (SPR) call failed.

Return code:

8 Variable not found

12 Invalid function

16 Variable pool is full

20 Variable pool not defined

24 Enqueue for VPUT failed



SupportLine.

REX0066W [001] Variable [002] scope [003] not found




SupportLine.

REX0067I [001] Varpool Utility ended with RC [002]



Page: 64

REX0068I [001] Call to IRXIC for subtask [002] with command [003] and environment [004]

ended with RC [005] (hex)


REX0069E [001] Reentrant REXX environment does not exist.

The LE Callable Service CEEMSG returned the feedback code:

CEE0454S The message number 70 could not be found for facility ID REX.




SupportLine.

3.12 SJB - Started Job

Messages produced when the User Server runs as started jobs.

SJB0001E [001] If a user server should be started as a started job, the environment variable

TSOE_SJOB_NAME must be specified



System administrator response: Correct the configuration ( TSOE_SJOB_NAME parameter).

SJB0002E [001] Start command for user server [002] <user> 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 SVC routine.

255 Address Space has no ACEE (Accessor Environment Element)


257 Console buffer is too small



Page: 65


SupportLine.

SJB0003E [001] A user server can only be started through a z/Server




SupportLine.

SJB0004I [001] Internal start command [002]

RC was: [003]

ASID is: [004]

Explanation: This is an informational message. [002] is the <MGCR_DATA>.

SJB0005E [001] Start of user server was not successful. Unable to get CAUB_JOBID for

started job.

ASID: [002]

Reason: [003]

Explanation: Either ASCB (Address Space Control Block) or the VAB (Virtual Storage Address

Block) could not be obtained, or the Start job name could not be found. The problem is caused by

the started task being aborted immediately after it is started, for example, because of a JCL error or

RACF violation.

ASID Address Space ID

Reason The LOCASCB macro reason Bibliography for details of the return code.



SupportLine.

SJB0006I [001] Generated start command for user server: [002]

Explanation: This is an informational message. [002] is the <start command>.

3.13 SLR - TSO Scheduler Interface

Messages produced when the server is defined as a Class 1 or Class 2 scheduler.

SLR0001I [001] TSO Scheduler initialization


Page: 66


SLR0002I [001] TSO Scheduler termination


SLR0003I [001] Stopping user server [002]


SLR0004I [001] Stop of user server was not successful; RC [002]


System administrator response: Correct the configuration ( USERAREA1 parameter).

SLR0006E [001] User-Area-1 too small for (TSOPORTS) ports

User-Area-1 must have a length of at least [002] bytes




SLR0007I [001] Routing message for user [002] to port [003]

Length of message: [004]


SLR0008E [001] Unexpected Return Code [002] (hex)


Return code (decimal):

4 Invalid parameter list or last parameter not 'I' or 'T' or timeout < 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 one TCB allowed for non-LE environment


Page: 67

40 Invalid compress value

44 Invalid dump value

48 Invalid set version

100*n Named/token pair not found for non-LE environment multiplied by the return code from

IEANRTR

400 The request is rejected because the system could not find the requested name/token



SupportLine.

SLR0009E [001] ACEE for TCB is not available or TCB userid is not the same as specified in

the input message




SupportLine.

SLR0010E [001] User table is full. Increase size of User-Area-1




SLR0012E [001] Job dataset could not be opened



System administrator response: Check whether DD:TSOEJOB exists in the startup JCL.

SLR0013E [001] I/O error during read of Job dataset




SupportLine.


Page: 68

SLR0014E [001] TSO/E Server [002] for user [003] already exists with Jobid [004]. Submit

denied



System administrator response: None

SLR0015E [001] TSO/E Server [002] for user [003] submitted more than [004] times. Limit

reached.



System administrator response: Check why the user server cannot be started; correct the

problem and reset the counter.

SLR0016E [001] Server was marked unusable in a prior error




SupportLine.

SLR0018I [001] TSO/E Server [002] for user [003] submitted


SLR0019I [001] TSO/E Scheduler initialization completed

Delay after Submit: [002] milliseconds

Job class: [003]

Job message class: [004]

First port: [005]

Last port: [006]

Cleanup user jobs: [007]


SLR0020S [001] TSO/E Server [002] with JobID [003] for user [004] had a JCL error.

Dispatcher is marked unusable.




Page: 69

System administrator response: Correct the JCL.

SLR0021S [001] TSO/E Server [002] with JobID [003] for user [004] is duplicate. Dispatcher is

marked unusable.



System administrator response: Stop User-Server Check and delete entry in the User-Admin

table.

SLR0022S [001] More than one active job [002] for user [003] found. Dispatcher is marked

unusable.



System administrator response: Stop User-Server Check and delete entry in the User-Admin

table.

SLR0023I [001] TSO/E Server [002] with JobID [003] for user [004] submitted


SLR0025E [001] User [002] not found. Stop Command ignored


User response: Specify a correct UserID.

SLR0026I [001] Stop Command for user [002] accepted


SLR0027W [001] Job [002] Id [003] System [004] Phase [005]

Explanation: Trace-message that describes the status of a JOB

User response: NONE

SLR0028E [001] TSO/E Server for user [002] is not running



System administrator response: Start the TSO/E Server.

SLR0029W [001] Job [002] Id [003] cancelled


Page: 70


SLR0030I [001] Retrieving status for job [002] and user [003]


SLR0031S [001] Job [002] for user [003] not found.



System administrator response: Reconnect for resubmit.

SLR0032E [001] Job [002] for user [003] not ready



System administrator response: Check job status and wait.

SLR0033E [001] Job [002] for user [003] finished

Explanation: Port entry cleared.


System administrator response: A User-Server has terminated unexpectedly and the entry in

the user administration was cleared. Check why User-Server terminated and correct the problem.

SLR0034E [001] Enqueue for Internal Reader failed



System administrator response: Due to a previous abend, the resource was not freed. Produce

an SVC-Dump and send it with the complete server-output to the Micro Focus SupportLine.

SLR0035I [001] Job [002] Id [003] System [004] Phase [005]


SLR0036I [001] [002] [003] [004] [005] [006] [007]


SLR0037I [001] Time format : MMDDHHMMSS

Phase:

01-0D Not Running Last-Cmd: I Initialized


Page: 71

0E Running E Error

0F-1B Finished S Submit

P Stop

D Delete Entry

JobName JobId UserId Phase LastCmd Time Port


SLR0038W [001] User [002] not found

Explanation: Delete command ignored.

User response: Specify a correct UserID.

SLR0039W [001] User [002] deleted


SLR0040I [001] Server statistics


SLR0041I

Submit Count ......... [001] times

Stop Count ......... [002] times

Communicate Count ......... [003] times

Error Count ......... [004] times


SLR0042I Server configuration

TSOE_Delay_After_Submit: [001]

TSOE_Job_Class: [002]

TSOE_First_Port: [003]

TSOE_Last_Port: [004]

TSOE_Cleanup: [005]

TSOE_Portcheck: [006]


SLR0043I [001] [002] for address space ended with RC [003]


SLR0044I [001] Dequeue for major name [002] and minor name [003]



Page: 72

SLR0045E [001] Dequeue failed with RC [002]


Return code:

>0 Original return code from DEQ macro ( Bibliography for details of the return code)

-4 Invalid function

-8 Invalid type

-12 Invalid scope

-16 Invalid length for minor name


System administrator response: Check whether the associated ENQ was made.

SLR0046I [001] Dequeue successful


SLR0047I Initiator information


SLR0048I Class: [001]

Dedicated initiators: [002]

Allocated initiators: [003]

Used initiators: [004]


SLR0049I [001]

Job-Prefix : [002]

Job-Search-String : [003]

Scheduler-Table : [004]

Max. parallel USR-Serv. : [005]

No of Slaves : [006]


SLR0050E [001] No console defined


Page: 73

Explanation: Checking of ports or initiators is disabled.


System administrator response: Define an appropriate console.

SLR0051E [001] [002] Ports defined, but only [003] initiators are dedicated to class [004].

Startup of server terminated.


User response: Retry later or contact the system administrator.

System administrator response: Start further appropriate initiators.

SLR0052E [001] All [002] Initiators are in use. User server for [003] not submitted.


User response: Retry later or contact the system administrator.

System administrator response: Start further appropriate initiators.

SLR0053W [001] More than 80% of [002] initiators are in use


SLR0054I TSOE_Initcheck: [001]


SLR0055E SLR0055E [001] Port [002] is not available. See LE-Message for further Information.


User response: See LE messages for further information. If necessary, contact the system

administrator.

System administrator response: Check who is using the port. If the port is used by another

product, change the port range of the server.

SLR0057I [001] Submit count for user [002] set to [003]


SLR0058I [001] Message was not routed due to <ROUTEMSG>N</ROUTEMSG>



Page: 74

SLR0059E [001] Error in XML document Not all elements for PUTVAR or DELVAR specified.

PUTVAR requires VARTYPE, VARNAME and VARTEXT.

DELVAR requires VARTYPE and VARNAME.



System administrator response: Correct the XML document.

SLR0060E [001] Variable for JOB not found



System administrator response: Check for a SPR0007E message. JCL contains a variable that

was not found in the variable pool. Message SPR007E contains the variable name.

SLR0061E [001] Logon not valid Userid and/or password missing


User response: Repeat the logon with the correct Userid and password.

SLR0062E [001] Logon for userid [002] was not successful


User response: Check the LE message file for more information and react accordingly.

SLR0063E [001] Password / new password for userid [002] is invalid.

Password must be specified as hexadecimal.

Password may have a length of 16 bytes.

Password must be DES encrypted.




SupportLine.

SLR0064I [001] Password: [002] (hex)

Password encrypted: [003]

Password decrypted: [004]


SLR0065E [001] Input message for TSO/E Scheduler must be an XML document


Page: 75


User response: Specify an XML document.

SLR0066E [001] An XML document for a TSO/E Scheduler must start with the root element

<TSOSCHED>


User response: Specify a correct XML document.

SLR0067E [001] Attributes missing for element <ROUTEMSG>


User response: Specify a correct <ROUTEMSG> element.

SLR0068I [001] Calling program [002] with command [003]


SLR0069E [001] Stop or Logoff command for user [002] not successful

Reason code: [003]




SupportLine.

SLR0070I [001] Verify for userid [002] successful


SLR0071E [001] Verify for userid [002] not successful Reason [003] (hex)

Explanation: RACF (security) check failed.

Reason code (hexadecimal):

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


Page: 76

For more details RACINIT macro.

User response: If the problem cannot be resolved, contact the system administrator.


SupportLine.

SLR0072E [001] Change password not valid Userid, old password and new password must be

specified


User response: Repeat the change password with all required values.

SLR0073E [001] Change password for userid [002] not successful

Reason [003]




SupportLine.

SLR0074I [001] Change password for userid [002] successful


SLR0075I [001] Start processing initial XML document


SLR0076I [001] End of processing for initial XML document


SLR0077I [001] Wait for [002] milliseconds completed


SLR0078E [001] Command [002] for server [003] not processed

Reason: [004]


Before a message is sent to the User-Server a so-called Health Check of the User-Server is

performed. This message is issued if the Health Check failed. The following reasons are possible:

Job not found


Page: 77

Job waiting for execution

Job on output queue



SupportLine.

SLR0079E [001] Unexpected return code [002] from user administration


Return code:

08 Function init not valid. Init is allowed from holder task if a dataspace is used or from a

server if local storage should be used.

12 Size of dataspace or size of local area is not big enough to hold all required tables

20 Invalid function

100 Port range of server outside the defined port range over all servers

101 Port range of server is overlapping with the port range of another server

102 Server already in table. server is not added

104 Server table is full

108 Server not found in table

112 User not found in table

114 User already in table

118 User table for server is full

122 CRP outside Table

126 User server not a started job. timeout ignored

130 Port not found in table

134 User administration not in a dataspace

nnn for function code 9



Page: 78


SupportLine.

SLR0080E [001] This server only accepts messages routed from a TSO/E Scheduler



System administrator response: Correct the configuration ROUTE_ONLY parameter.

SLR0081I [001] User server policy is: [002]


SLR0082E [001] Invalid value for TSOE_U_POLICY


Valid values:

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


System administrator response: Correct the configuration TSOE_U_POLICY parameter.

SLR0083I [001] User server control utility called with command [002]


SLR0084E [001] User server [002] did not respond for [003] seconds. Connection terminated

due to timeout.


User response: Retry the action. If the problem continues, contact the system administrator.

System administrator response: Correct the configuration TSOE_U_POLICY parameter.

SLR0085E [001] If more than one user server is allowed, the policy must be started job or CEA

TSOE_U_POLICY=1 or TSOE_U_POLICY=8



Page: 79


System administrator response: An ADDUSRV command was issued. Change POLICY if more

than one User-Server is required.

SLR0086I [001] [002] user servers found for userid [003]


SLR0087E [001] Maximum number of allowed user servers [002] reached


User response: Retry later or, if necessary, contact the system administrator.

System administrator response: Increase the number of user servers.

SLR0088E [001] User table is full. Increase port range for server


User response: Retry later or, if necessary, contact the system administrator.

System administrator response: Increase the number of ports TSOE_FIRST_PORT and

TSOE_LAST_PORT parameters.

SLR0089E [001] Command ADDUSRV is allowed only for policy started jobs




SupportLine.

SLR0090E [001] Timeout or Timeout action not allowed for a TSO/E scheduler Startup

aborted



System administrator response: Correct the configuration TSOE_SCHEDULER or

TSOE_USER parameter.

SLR0091E [001] For Timeout_Action = STOP the user administration must be in a common

data space




Page: 80


SupportLine.

SLR0092E [001] User servers with Timeout_Action=STOP must be started with POLICY=1

(Started Jobs). Timeout is ignored. User server continues but with bad performance.




SupportLine.

SLR0093E [001] Bad RC [002] from user administration for set timeout Timeout is ignored.

User server continues but with bad performance




SupportLine.

SLR0094E [001] User server [002] for user [003] is no longer active due to timeout



System administrator response: Restart the user server. Check the logs; if necessary, contact

the Micro Focus SupportLine.

SLR0095E [001] Restart of user server for [002] on port [003] failed with RC [004]




SLR0096E [001] Restart for port [002] not possible No timeout entry found



System administrator response: Correct the configuration TIMEOUT parameter.

SLR0097E [001] No port for RESTART specified



Page: 81

User response: Specify a port number for the RESTART command.


System administrator response: Specify the correct port number for the RESTART command.

SLR0099E [001] XML document does not contain a valid command for a z/Server TSO/E

Scheduler


User response: Specify a correct XML document.

SLR0100E [001] Size of extra buffer with [002] bytes is too small to hold all output from XML

document



System administrator response: Change the configuration PIMASIZE parameter.

SLR0101I [001] Extra buffer for multiple XML images allocated at address [002]


SLR0102W [001] User administration not in a data space Command ignored


SLR0103E [001] More than one user server running ROUTEMSG requires the specification of a

port


User response: Specify a port; contact the system administrator.

System administrator response: Correct the configuration PORT parameter.

SLR0104E [001] No user server on port [002] found for user [003]

Explanation: Some commands require the specification of a port, for example, ROUTEMSG and

KILL. This message is issued if the specified port is not found.

User response: USE GETPORT to get all active Ports for a user, before issuing a ROUTEMSG

administrator.

System administrator response: Check whether the port has been assigned. If not, this is a user

error, otherwise contact the Micro Focus SupportLine.

SLR0105E [001] User server on port [002] belongs to user [003] and is invalid for [004]


Page: 82

Explanation: Some commands require the specification of a port, for example, ROUTEMSG and

KILL. This message is issued if the specified port is assigned but not by this user.

User response: Use GETPORT to get all active ports for a user, before issuing a ROUTEMSG.


SLR0106E [001] Deferred LOGON is allowed only for started jobs



System administrator response: Change POLICY if a deferred LOGON is required.

SLR0107I [001] Deferred LOGON for user [002] successful


SLR0108E [001] Load of XML exit [002] failed

Message: [003]



System administrator response: Check that the XML exit program is contained in an accessible

load library: if necessary, contact the Micro Focus SupportLine.

SLR0109I [001] Calling XML exit [002]


SLR0110I [001] XML exit [002] ended with RC [003]


SLR0111I [001] TSO/E Scheduler initialization/termination routine called with function [002]


SLR0112E [001] Initialization/termination exit for TSO/E Scheduler failed for function [002]

with RC [003]

Explanation: TSO/E Scheduler failed. Return codes:

008 init function not valid. Init is allowed from holder task if a dataspace is used or from

a server if local storage should be used

012 Size of dataspace or size of local area is not big enough to hold all required tables


Page: 83

020 Invalid function

100 Port range of server outside the defined port range over all servers

101 Port range of server is overlapping with the port range of another server

102 Server already in table; server is not added

104 Server table is full

108 Server not found in table

112 User not found in table

114 User already in table

118 User table for server is full

122 CRP outside table

126 User server not a started job; timeout ignored

130 Port not found in table

134 User administration not in a dataspace



SupportLine.

SLR0113I [001] [002] for port [003] and user [004] successful


SLR0014E [001] User server [002] for user [003]already exists with Jobid [004]. User server not

started.



System administrator response: Check that the initialization/termination exit program is

contained in an accessible load library, if necessary, contact the Micro Focus SupportLine.

SLR0115I [001] Call command exit [002] for [003] at address [004]


Page: 84


SLR0116I [001] Command exit [002] ended with RC [003]


SLR0117E [001] Command [002] not executed due to command exit


User response: Check the RC of the command exit.


SLR0118E [001] Delete of [002] failed, reason: [003]

Explanation: CEERELES failed, see the Bibliography for details of the return code.



SupportLine.

SLR0119E [001] Command [002] is allowed only for a class 2 scheduler



System administrator response: Correct the configuration TSOE_SCHEDULER parameter.

SLR0120E [001] Not more than 10 slaves allowed




SLR0121E [001] Data space required to initiate slaves



System administrator response: Correct the configuration DSP_INSTALL parameter.

SLR0122E [001] Slaves only allowed for a class 1 scheduler




Page: 85

System administrator response: Change Scheduler Class if this server should use slaves,

SLR0123E [001] A slave is required to execute command [002] but no slaves are defined



System administrator response: Define an appropriate data space.

SLR0124E [001] No configuration file for slaves defined



System administrator response: Define an appropriate slave configuration file.

SLR0125E [001] Only a master server can create slaves



System administrator response: Change Server Type to Master in the startup JCL.

SLR0126I [001] Routing message for command [002] to slave on port [003]

Length of message: [004]


SLR0127E [001] Slaves are allowed only if a server is a started task



System administrator response: A Server cannot be started with SUBMIT if slaves are used,

SLR0128E [001] No procedure for slaves defined



System administrator response: TSOE_SLVPROC not specified in the configuration.

SLR0129E [001] KILL is not allowed for jobs



Page: 86

SLR0130E [001] User server for user [002] and port [003] has an invalid combination for

timeout and jobid

Possible reason: User server was not marked as a user server TSOE_USER=1

User server did not set the READY flag due to an abend.



System administrator response: Check whether the configuration of a User-Server contains

TSOE_USER=1

SLR0131E [001] User server did not signal READY after a wait period of 10 X [002]

milliseconds. Command was not routed to the user server.



SLR0132E [001] TSOE_DELAY_SUBMIT must be at least 1000 milliseconds for a policy uneven

JOB



System administrator response: Define at least TSOE_DELAY_SUBMIT=1000 in the

configuration.

SLR0134E [001] User server with jobid [002] for user [003] was dirty stopped without logoff.

Port-Entry is cleared!


User response: Do not stop the user server without first logging off.

SLR0135S [001] Port [002] for z/Server scheduler [003] locked because port was not available.

Explanation: The port [002] was not available to the scheduler [003] because TCPIP returned a

response of "the port is in use and has the state LISTEN" on a query.

System administrator response: Check which address space is listening on port [002] using the

netstat command. If that port is in use by a different application, then either check for a

configuration problem for the holder/scheduler task and correct the port ranges or check why a

different application is now using this port.


Page: 87

If the address space listening on port [002] is a user server, then that user server is apparently still

running and needs to get terminated. After it was terminated, the port can be unlocked by using the

command f scheduler,tso,unlock,port=[002]

SLR0140E [001] Scheduler [002] is locked. Start of User-Server is disabled.


SLR0141E [001] Unable to resolve Port for ASID [002]


SLR0142I [001] Asid [002] is using Port [003]


SLR0143I [001] Resolving Port for ASID [002] via dataspace

Der LE-Callable-Service : CEEMSG lieferte den Feedbackcode

CEE0458S The message repository USLVMSGT could not be located.


3.14 SPR - Standard Pool Routine

The Standard Pool Routine processes variables in a similar way to the processing of ISPF Dialog

Manager profile pool variables.

SJB0001E [001] If a user server should be started as a started job, the environment variable

TSOE_SJOB_NAME must be specified

SPR0001I [001] Standard Pool Routine called with function: [002]

Variable type: [003]

Variable name: [004]

Variable content: [005]


SPR0002E [001] Standard Pool Routine called with invalid function : [002]


Valid function:

VPUT Write variable

VGET Read variable


Page: 88

VDEL Delete variable

User response: Specify a correct function.


SPR0003E [001] Variable pool is too small to hold all variables. Current size is [002]


User response: Increase the size of the variable pool.


SPR0004I [001] Variable found in pool at entry [002]

Find flag is [003]

Entry address is [004]

Entry length is [005]


Find flag:

X'01' Variable found

X'02' Variable contains the same content

X'04' The length of the content is equal

SPR0004I [001] Variable found in pool at entry [002]

Find flag is [003]

Entry address is [004]

Entry length is [005]

SPR0005I [001] Variable [002] found for substitution


SPR0006I [001] Variable [002] contains [003]

Explanation: The variable content is returned.

SPR0007E [001] Variable [002] not found in the variable pool


User response: Specify a correct variable name.



Page: 89

SPR0008W [001] Result after substitution in [002] bytes greater than in the input buffer

Explanation: The variable is truncated.

SPR0009E [001] No variable pool defined


User response: Define a variable pool with the VPOOLSIZE environment variable.


SPR0001S [001] Enqueue for variable pool failed


User response: Contact your system administrator.


SupportLine.

SPR00011I

Pool address: [001]

Pool size: [002]

Pool free space: [003]

Number of variables: [004]

Explanation: This is an informational message. The pool statistics are returned.

SPR00012I [001] Variable pool not defined

Explanation: This is an informational message. The pool statistics are listed.

SPR00013I

[001] <VTYPE>

[002]<VNAME>

[003]<VTXT>

Explanation: This is an informational message. The variable type, name, and content are listed.

SPR00014I [001] Data stream before substitution Length: [002]

Explanation: This is an informational message. The data stream length before substitution is listed.

SPR00015I [001] Data stream after substitution Length: [002]

Explanation: This is an informational message. The data stream length after substitution is listed.

SPR00016I [001]


Page: 90

Explanation: This is an informational message. The VGET content is listed.

3.15 SRV - Server Interface

SRV0001I [001] z/Server service task is initializing


SRV0002I [001] Service task awakened


SRV0003E [001] Subtask [002] with TCB [003] consumed more than [004] milliseconds CPU

time. Subtask will be killed. Check TASK_RUNAWAY value if there was no loop.



System administrator response: The subtask is probably in a loop. Check running REXX or

Program an increase TASK_RUNAWAY if necessary.

SRV0004W [001] CPU consumption check is disabled. Any loops are not detected


SRV0005I [001] Using service exit [002]


SRV0006I [001] Calling service exit [002]


SRV0007I [001] Checking for any outstanding messages and command responses from the

extended master console [002]


SRV0008I [001] Calling initial REXX [002]


SRV0009I [001] Initial REXX [002] ended with RC [003]



Page: 91

3.16 STA - Started Task Interface

STA0001E [001] 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)



System administrator response: Update the configuration file with a correct value for

TSOE_SCHED_TAB.

STA0003I [001] TSO/E Scheduler table routine called with function [002]


STA0004E [001] Name for named-token pair is not specified




SupportLine.

STA0005E [001] Read of named-token pair [002] failed with RC [003] (hex)

Explanation: The search for a token failed Bibliography for details of the return code

(IEANTRT service).



SupportLine.

STA0006I [001] Value of named-token pair [002]

DSPALET: [003]

DSPORIGIN: [004]

DSPBLOCK: [005]

DSPFLAGS: [006]


STA0007E [001] Name of named-token pair for console is not specified


Page: 92




SupportLine.

3.17 TAU – Eclipse Client Interface

Messages from the z/Server nucleus.

TAU0001I [001] [002] [003] startup [004]


TAU0002I [001] Address of handler communication area: [002]


TAU0003I [001] Address of server communication area: [002]


TAU0004I [001] 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

IP name: [006]

PPT: [007]

Dump if API fails: [008]

Multiple REXX environments: [009]


TAU0005I [001] Address of subtask storage table: [002]

A(ECB list for wait in subtask): [003]

A(ECB list for post in subtask): [004]


TAU0006I [001] Client [002] connected on port [003] Desc [004]



Page: 93

TAU0007E [001] Error during call to EZASOKET

Function: [002]

Reason code: [003]

Explanation: See TCP/IP for MVS: API Reference for reason code details.



SupportLine.

TAU0008I [001] Subtask [002] for z/Server is initializing


TAU0009E [001] No free ECB available. Waiting for next free ECB.


User response: Retry later; if necessary, contact the system administrator.

TAU0010I [001] Subtask [002] started A(TCB): [003] A(ECB): [004]


TAU0011I [001] Subtask [002] posted A(TCB): [003] A(ECB): [004]


TAU0012E [001] Timeout for Takesocket after [002] seconds


User response: This could happen if IP traffic is very high. Retry the request.


TAU0013I [001] Client ID is [002] and [003]


TAU0014I [001] Detaching subtask [002] for TCB [003] with ECB [004]


TAU0015I [001] Before call [002]


TAU0016I [001] Received [002] bytes



Page: 94

TAU0017I [001] About to send [002] bytes to client


TAU0018I [001] There are [002] bytes available for receive


TAU0019W [001] Environment variable [002] was not specified, defaults used


User response: Validate that the default is appropriate; if not, contact the system administrator.

System administrator response: Correct the configuration file.

TAU0020E [001] Value [002] for environment variable [003] has invalid length or is not numeric



System administrator response: Correct the configuration file.

TAU0021I [001] Converting message from ASCII to EBCDIC


TAU0022I [001] Converting message from EBCDIC to ASCII


TAU0023I [001] Subtask for z/Server activated


TAU0024I [001] Highest socket number assigned to server is [002]


TAU0025I [001] Input message area for subtask allocated at [002]

Output message area for subtask allocated at [003]

Work message area for subtask allocated at [004]

Each area is [005] bytes long

PIMA for subtask allocated at [006]

PIMA area is [007] bytes long

ECI table for subtask allocated at [008]


TAU0026W [001] Command [002] was invalid. No action performed.


Page: 95




SupportLine.

TAU0027E [001] Delete of module [002] was not successful

Reason code: [003]


DELETE return code:

4 The requested module was not in storage, or an attempt was made to delete a system

module by an unauthorized caller.



SupportLine.

TAU0028W [001] Subtask [002] event has completed with completion code [003]


TAU0029I [001] Load of module [002] was successful; entry-point address [003]


TAU0030E [001] Load of module [002] was not successful.

Abend code: [003]

Reason code: [004]

Explanation: See the bibliography for details of the LOAD abend code and reason code.



SupportLine.

TAU0031E [001] Detach for subtask [002] was not successful RC [003]



DETACH return code:


Page: 96

4 An incomplete subtask was detached with STAE=YES specified; DETACH processing

successfully completed.


SupportLine.

TAU0032E [001] No TCPIP IMAGE found Waiting [002] seconds before retry


User response: If the problem persists, contact the system administrator.


SupportLine.

TAU0033E [001] Unexpected error in [002] Server will be terminated

Explanation: EZASMI service failed Bibliography.



SupportLine.

TAU0034E [001] Message has invalid length. A message must start with a 48-byte message

header.



System administrator response: Validate the configuration file COMPAT parameter.

TAU0035E [001] No valid receive method specified


User response: Specify a valid Receive method in the IP header.


TAU0036I [001] Using receive method 1 until [002] bytes received


TAU0037I [001] Using receive method 2 until delimiter [002] is found


TAU0038I [001] Using receive method 3, single receive


Page: 97


TAU0039I [001] Socket server information

Domain name local host: [002]

IP address current host: [003]

VIPA for internal usage: [004]

IP address VIPA: [005]


TAU0040E [001] Server startup terminated by [002]




SupportLine.

TAU0041I [001] CmdTask [002] started A(TCB): [003] A(ECB): [004]


TAU0042I [001] Converting ASCII (UTF-8) header to EBCDIC header


TAU0043E [001] IP-ASCII data length or CCSID in ASCII header is not numeric


User response: Specify a valid data length in the IP header.


TAU0044E [001] Error converting ASCII header to EBCDIC header

See Message UNI001E.



System administrator response: Check that translation for CCSID is defined.

TAU0045I [001] Using receive method 4, receive via application


TAU0046I [001] Address of Program Property Table (PPT): [002]


Page: 98


TAU0047S [001] PPT overflow, all [002] entries in use Request terminated




TAU0048W 001] Client closed connection before all data was received. Message may be

incomplete.


TAU0049W [001] Timeout occurred before all data was received. Message may be incomplete.


TAU0050E [001] Input message length with [002] bytes is greater than input buffer with [003]

bytes. Increase the buffer size and restart server.



System administrator response: Verify the configuration file BUFFERSIZE and BUFFERUNIT

parameters.

TAU0051W [001] Shutdown server


TAU0052I [001] Updating length field in header to [002]


TAU0053I [001] Shutdown subtask


TAU0054S [001] Terminating subtask with dump




TAU0055I [001] Entry point for program [002] disabled



Page: 99

TAU0056I [001] ISPF available: [002]

Size of User-Area-1: [003] bytes

Size of User-Area-2: [004] bytes

Address of User-Area-1: [005]

Address of User-Area-2: [006]

Timeout for server: [007] minutes

Reattach after Abend: [008], 0 = No


TAU0057I [001] TSO environment created successfully

Address(Command Processor Parameter List): [002]


TAU0059I [001] [002] ended with RC [003]


TAU0060I [001] Size send/receive buffer: [002] [003]

Maximum error count: [004]

PIMA size: [005]

CICS EXCI support: [006]

CICS EXCI Applid: [007]

Port check: [008]

TSO/E Scheduler: [009]


TAU0061I [001] Size of variable pool: [002] bytes

Address of variable pool: [003]

Use SVC: [004] SVC [005]

Maximum number of user servers: [006]

TSO/E user server: [007]


TAU0062E [001] Maxerr > 0 only valid with PPT=1. Maxerr changed to no limit = 0



System administrator response: Define PPT=1 in the configuration file.

TAU0063S [001] Maxerr reached for program [002]. Program is disabled.


Page: 100

Explanation: The specified program has too many errors. The program is disabled.



TAU0064W [001] Length for write is zero. No data written.


TAU0065I [001] After call [002] RC: [003] Error number: [004]


TAU0066I [001] Address of EZA global data area: [002]


TAU0067I [001] Startup completed for [002] for [003] and ASID [004]


TAU0068I [001] New date: [002]


TAU0069E [001] Function code [002] (hex) is not supported

Explanation: IP socket function call failure.

Valid function codes:Val

X'07' Send+Receive

X'09' Flush input buffer

X'15' Send

X'1B' Receive

User response: Correct function call for TAURIP03 Programming-Reference for more

information.


TAU0070I 001] Delete of module [002] completed with RC [003]


TAU0071I [001] Kill request for task [002] received


Page: 101


TAU0072W [001] Connection is closed and no data is available


TAU0073S [001] Access denied to $IPSERV [002]



System administrator response: Permit access

TAU0074I [001] Security: [002]

Header length: [003] bytes


TAU0075W [001] Access allowed to $IPSERV [002] because security is disabled



System administrator response: Verify the configuration file SECURITY parameter.

TAU0076I [001] Flushing input buffer. [002] bytes available


TAU0077I [001] SVC for task level security invoked

Function: [002]

Userid: [003]

SVC RC: [004]

SAF RC: [005]

RACF RC: [006]

RACF reason: [007]


TAU0078E [001] Create for task level security was not successful

Return code: [002]


Return code:



Page: 102

300 Userid missing

304 Password missing

308 New password missing

400 Not TSO/E Scheduler



SupportLine.

TAU0079E [001] SVC [002] not installed. Startup terminated



System administrator response: Install the SVC.

TAU0080E [001] Load of module [002] was not successful.

System completion code: [003].

Reason code: [004]


LOAD abend code and reason code Bibliography



SupportLine.

TAU0081E [001] Unable to open Internal Reader Return code: [002]



System administrator response: Check that the reader is allocated in the Startup JCL:

// READER DD SYSOUT=(*,INTRDR) .

TAU0082E [001] IO error on Internal Reader Return code: [002]




Page: 103

System administrator response: as for TAU0081E.

TAU0083W [001] A TSO/E environment already exists An additional dynamic environment is not

created


TAU0084E [001] None or invalid invoking method specified for exec [002]




SupportLine.

TAU0085E [001] ISPF environment is not available. Unable to invoke exec [002]



System administrator response: Verify the configuration file.

TAU0086I [001] Timeout reached


TAU0087I [001]

Timeout for read: [002] microsec

Clear buffer: [003]

Own exception handler: [004]

Exception handler name: [005]

Service wait time: [006] millisec

Task runaway time: [007] millisec

Console wait time: [008] millisec

Console buffer size: [009] KB


TAU0088S [001] All subtasks are dead. Server terminates abnormally

Explanation: This message is issued if a server is started with REATTACH=0 and all subtasks fail

successively and no further subtask is available.



Page: 104

System administrator response: Check the logs for the cause. Set either REATTACH=1 or

increase the number of subtasks.

TAU0089E [001] XML parse is valid only with receive method 3


User response: Change Receive method in IP header to 3.


TAU0090W [001] PIMASIZE must be at least [002]. Size changed.


User response: If necessary, contact the system administrator.

System administrator response: Specify an appropriate PIMASIZE size in the Scheduler

configuration file.

TAU0091E [001] XML support is not activated. Specify PIMASIZE for activation.

Explanation: Specify PIMASIZE to activate XML support.


System administrator response: Specify an appropriate PIMASIZE size in the Scheduler

configuration file.

TAU0092I [001] Invoking initialization exit [002]


TAU0093I [001] Invoking termination exit [002]


TAU0099I [001]=============


TAU0100E [001] A CICS Applid must be specified if ECI support is activated ECI support

disabled



System administrator response: Define CICS_EXCI in the configuration file


Page: 105

TAU0101I [001] Entry to Routine Enq-Deq 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] millisecondsExplanation: This is an informational message.

TAU0102I [001] Exit to Enq-Deq routine RC was [002]


TAU0103W [001] Resource not available, RC from ENQ was [002]

Waiting for [003] milliseconds.

Major name: [004]

Minor name: [005]



TAU0104I [001] Limit for retry of [002] reached.

Resource is marked disabled and will not be used.


TAU0105E [001] Enqueue for Internal Reader failed




SupportLine.

TAU0106W [001] Negative receive-length for [002] bytes specified Multiple reads are forced

until specified length is reached.


TAU0107I [001] Registration for exception handler [002] successful



Page: 106

TAU0108E [001] Registration for exception handler [002] failed with token [003]. Continue

without exception handler.




SupportLine.

TAU0109W [001] Invalid value specified for TIMEOUT_ACTION Use only N = Normal or S =

Shutdown. Value changed to N.


TAU0110I [001] SrvTask [002] started A(TCB): [003] A(ECB): [004]


TAU0111I [001] Reattach request for task [002] received


TAU0112I [001] Activating extended master console with name [002]


TAU0113E [001] Activation of extended master console failed with RC [002]



Console deactivated




SupportLine.

TAU0114I [001] Deactivating extended master console with name [002]


TAU0115E [001] Deactivation of extended master console failed with RC [002]






Page: 107


SupportLine.

TAU0116I [001] Activating extended master console with name [002] successful.

Console ID: [003]

Console ALET: [004]


TAU0117E [001] Get next message from extended master console ended.






SupportLine.

TAU0118I [001] Address of extended console buffer: [002]


TAU0119E [001] No console defined Commands CCALL and XCALL are not supported



System administrator response: Define an appropriate console.

TAU0120E [001] Console command failed with RC [002] (hex)




SupportLine.

TAU0121E [001] Required environment variable [002] was not specified. Server startup

aborted.




SupportLine.


Page: 108

TAU0122W [001] No User SVC is used for authorized functions Server must run in an

authorized environment.


TAU0123S [001] Jobstep is not APF authorized. Startup terminated.



System administrator response: Run the program from an APF authorized library.

TAU0124E [001] No response from server




SupportLine.

TAU0125I [001] Additional heap (below the line) with [002] bytes created. Heap ID [003]


TAU0126I [001] Heap below the line for subtask allocated at [002]


TAU0127E [001] No program for HTTP request defined HTTP request ignored



System administrator response: Check the logs. Define a program to accept HTTP requests.

TAU0128E [001] Value [002] for compression is invalid. Valid values are:

0 ==> no compression

1 ==> compress send buffer before send

2 ==> expand receive buffer after receive

3 ==> both


User response: Specify a correct compression value.


Page: 109

TAU0129E [001] 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)



System administrator response: Verify the configuration file COMPAT parameter.

TAU0130E [001] DDNAME [002] not found. Startup aborted.




SupportLine.

TAU0131I [001] XMLCA for subtask allocated at [002]

TS for subtask allocated at [003]


TAU0132E [001] Invalid version [002] in ASCII header found. This server is running with version

[003].




SupportLine.

TAU0133E [001] VIPA [002] could not be resolved




SupportLine.

TAU0134I [001] Server is [002]


TAU0135S [001] Permission denied [002] not authorized to use port [003]



Page: 110

TAU0136S [001] The address is in a timed wait because a LINGER delay from a previous close

or another process is using the address. 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.




SupportLine.

TAU0137I [001] Create slaves: [002]

Configuration for slaves: [003]

Procedure for slaves: [004]


TAU0138E [001] Invalid value [002] for MULTI_REXX

0: No extra environment for any subtask

1: Extra environment for every subtask

2: Extra environment for command and service task



System administrator response: Verify the configuration file MULTI_REXX parameter.

TAU0139E [001] SVC with function code [002] failed with RC [003]


User response: Contact the system administrator EMC0003E for details


SupportLine.

TAU0140E [001] Message has invalid length. A minimum length of [002] bytes is required for

version [003].




SupportLine.

TAU0141I [001] z/Server main task ready for client's


Page: 111


TAU0142I [001] z/Server Subtask READY for client's


TAU0143S This indicates an z/OS UNIX process initialisation failure.

This is usually an indication that a proper OMVS RACF segment is not defined for the user ID

associated with the application.

The RACF OMVS segment may not be defined or may contain error such as an improper HOME()

directory specification.



System administrator response: 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, check if a

proper HOME directory is defined. If necessary, contact the Micro Focus SupportLine.

IPS0144W [001] Config parameter [002] is no longer supported.



System administrator response: Remove the parameter [002] from the configuration file.

TAU0145I [001] BASE64 utility called with function [002]


TAU0146I --------------------------------------------------

BASE64 Input Address : [001] Length : [002]

--------------------------------------------------


TAU0147I --------------------------------------------------

BASE64 Output Address : [001] Length : [002]

--------------------------------------------------


TAU0148E [001] Storage needed for [002] subtask with a buffer size of [003] is greater than 2GB.



Page: 112

System administrator response: Change the NUMTASK parameter in the configuration file to a

lower value.

TAU0149E [001] Storage needed for [002] subtask with a buffer size of [003] is greater than private

region with [004]

Bytes.


System administrator response: Change the NUMTASK parameter in the configuration file to a

lower value.

TAU0150I [001] Approximately [002] bytes private region used.

Max. is [003] bytes


TAU0151I [001] New userid of ACEE for TCB [002] is [003]


TAU0152I [001] Flags for send : [002]


TAU0153I [001] Address of z/Server statistic area is [002]

Explanation: Self-explanatory.IPS0156E [001] Command task is busy. ENQ/DEQ not performed.


IPS0157I [001] Post command task for remote ENQ/DEQ


3.18 UNI - Unicode code conversion services

z/Server uses the Unicode code conversion services to perform code page conversions. For details,

see z/OS Support for Unicode: Unicode Services, form number SA22-7649-xx.

UNI0001I [001] Unicode character conversion from CCSID [002] to CCSID [003]


[002] Source code page

[003] Target page

UNI0002I [001] Unicode character conversion ended with RC [002] and Reason [003]


Page: 113


[002] Return code

[003] Reason code

User response: For an explanation of the return codes and the reason codes Support for

Unicode(TM): Using Conversion Services.

UNI0003I Result after conversion OldLen: [001] NewLen: [002]


[001] Old length

[002] New length

UNI0004W [001] Unicode character conversion not processed because CCSID of source is

equal to CCSID of target


UNI0005E [001] Dynamic CCSID for z/Server in ASCII-Header is not numeric.

Value is [002]




UNI0006W [001] 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 request

.... .1.. Copepage translation for receive requested

...1 .... Change Codepage for z/Server requested

Explanation: This is a warning message which indicates that the current code page of the z/Server

is changed from the value under “Current z/Server CCSID” to the value under “Requeseted

z/Server CCSID”.


Page: 114

3.19 XML - XML System Parser Interface

z/Server uses the high-performance XML System Parser for parsing XML-format files. Any return

codes and result codes displayed are those issued by the XML System Parser. For details, see z/OS

XML System Services User's Guide and Reference, form number SA23-1350-xx.

z/Server makes wide use of XML for internal communication. This means, XML errors may be

produced in unexpected situations, for example, the logon parameters (userid and password) are

passed as an ‘XML document’ to the validation routine, and a userid that is too long (more than

eight characters) produces the XML0003E error message.

XML0001E [001] XML Call to [002] ended with RC [003] and Reason [004]

Example: XML Call to GLX1PRS ended with RC 0000000C and Reason 00003030

Explanation: An XML System Parser Interface function call failed.

[002] The name of the XML System Parser Interface function, e.g. GLX1PRS

[003] The function return code

[004] The function reason code z/OS XML System Services User's Guide and Reference for

an explanation of the reason codes.

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

User response: Correct the error (refer to the reason code); if necessary, contact the system

administrator.


SupportLine.

XML0002I [001] Unknown XML record type: [002]


XML0003E [001] Attribute value [002] with length [003] is too long for attribute [004]



Page: 115

User response: Correct the XML document; if necessary, contact the system administrator.


SupportLine.

XML0004E [001] Value [002] for element [003] is not numeric




SupportLine.

XML0005E [001] Unknown attribute [002] for element [003]




SupportLine.

XML0006I [001] z/Server is using CCSID [002]


XML0007E [001] Invalid value [002] for attribute [003]




SupportLine.

XML0008E [001] Attributes required for command [002]




SupportLine.

XML0009I [001] New XML image at address [002]


XML0010I [001] XML Parser called with function [002]


Page: 116


XML0011I [001] XML Parser ended with RC [002] and Reason [003]


XML0012I [001] Offset to XML input area where parser stopped: [002]


XML0013E [001] Maximum number of [002] XML images exceeded



System administrator response: Internal restriction; contact the Micro Focus SupportLine.

XML0014E [001] A port must be specified for USRENQ or USRDEQ




SupportLine.

XML0015E [001] Port [002] does not belong to user [003]


User response: Correct the port number; if necessary, contact the system administrator.


SupportLine.

XML0016E [001] Value for attribute [002] must have a length of [003]




SupportLine.

XML0017I [001] XML-Query-Information

Version: [002]

Autodetect value: [003]

Autodetect CCSID: [004]

Specified CCSID: [005]

Length of decl: [006]


Page: 117

Flag 1: [007]

1... .... standalone flag

.1.. .... with byte order mark flag

Flag 2: [008]

1... .... standalone specified

.1.. .... encoding specified

..1. .... version specified


XML0018I [001] Initialzing z/OS XML parser with CCSID [002]


XML0019E [001] Invalid codepage [002] for z/Server specified.

Explanation: The code page CCSID specified in the configuration is not supported by the z/Server.

The startup of the server is stopped.


System administrator response: Check the code page CCSID specified in the configuration file.

Change it to a code page CCSID supported by the z/Server.


Page: 118

4 Troubleshooting

If the user and system administrator responses do not help to correct the problem, you should send

the appropriate log files to the Micro Focus SupportLine.

The following sections describe the required steps, depending on where the problem occurred.

4.1 Common steps

4.1.1 Invoke SDSF

Invoke SDSF (or some similar product) to access the JES output.

4.1.2 Specify the filter

Click Filter to open the panel to specify the jobname filter.

Select Prefix of jobname (enter 2 in the input field), and press ENTER.

4.2 User Server case

4.2.1 Specify the appropriate jobname prefix

The TSOE_JOBPREFIX parameter in the configuration file specifies the prefix added to the userid,

to generate the jobname. For example, TSOE_JOBPREFIX=Z generates ZSOFAR as a jobname for

userid SOFAR.


Page: 119


Page: 120

4.2.2 Enter command

To obtain the job status, type ST at the Command Input prompt.

4.2.3 Select the appropriate job

To obtain the dataset list for the selected job, type ? in the NP column.

4.2.4 Select the required DDNAME

To select the required DDNAME, type s in the NP column.

4.3 ISPF Scheduler case

4.3.1 Specify the appropriate jobname prefix

If necessary, contact the system administrator for details of the name of the ISPF Scheduler; in this

case, TAUR*.


Page: 121

4.3.2 Enter command

To obtain the job status, type ST at the Command Input prompt.

4.3.3 Select the appropriate job

To obtain the dataset list for the selected job (in this case TAURISPZ), type ? in the NP column.

4.3.4 Select the required DDNAME

To select the required DDNAME, type s in the NP column.


Page: 122

4.3.5 Extract from the selected log file

The following output is for the error message CSI0051E with IPTRACE=5.

TAU0077I 14:45:46.188 SVC for Task-Level-Security invoked

Function : Create without Password on TCBSENV

Userid : SOFAR

SVC Rc : 00000000

SAF Rc : 00000000

RACF Rc : 00000000

RACF Reason : 00000000

CSI0006I 14:45:46.188 Catalog Utility called with cmd LISTDSI

Dataset filter : XYZ*.*

Member filter :

Catalog Flags : 00 (hex)


.1.. .... return userdata with member list

..1. .... wait for until recall of dataset is

complete



Page: 123




CSI0002I

=======================================================================

Input and Result from IGGCSI00

=======================================================================

Address Offset Word 1 Word 2 Word 3 Word 4 Word 5 Word 6

Word 7

238BD200 00000000 E7E8E95C 4B5C4040 40404040 40404040 40404040 40404040

404040

238BD220 00000020 40404040 40404040 40404040 40404040 40404040 40404040

404040

238BD240 00000040 40404040 40404040 40404040 40404040 40404040 40404040

404040

238BD260 00000060 40404040 40404040 40404040 40404040 40404040 40404040

404040

238BD280 00000080 40404040 C1C2C3C7 C8D9E4E7 40404040 40404040 404040C6

0005C5

238BD2A0 000000A0 C540E5D6 D3E2C5D9 4040C5D5 E3E8D7C5 4040C4E2 C3D9C4E3

F240C4

238BD2C0 000000C0 40404040 40404040 40404040 40404040 40404040 40404040

404040

238BD2E0 000000E0 40404040 40404040 4040


Word 7

238BD330 00000000 0000FA0E 0000003C 00000040 000640F0 C3C1E3C1 D3D6C74B

E9F1F1

238BD350 00000020 E3C5D940 40404040 40404040 40404040 40404040 40404040

404040


Page: 124

CSI0004I 14:45:46.203 Entry CATALOG.Z110.MASTER

from t

CSI0007I 14:45:46.203 0 Entries found

CSI0051E 14:45:46.203 No data sets for filter XYZ*.*

CSI0018I 14:45:46.203 Catalog Utility ended with RC 00000048


Function : Delete from TCBSENV

Userid : SOFAR

SVC Rc : 00000000

SAF Rc : 00000000

RACF Rc : 00000000


UNI0004W 14:45:46.203 UniCode Character-Conversion not processed because

CCSID

API0001I 14:45:46.205 Before Call IP03 Start-Call in Server -

Environment

Function-Code : 2A

Task-Area : 238BC0B4 Global

API0099I

=======================================================================

Data written

=======================================================================


Word 7

28950028 00000000 000000CC 4CD4E2C7 40C6C1C3 C9C47E7F C3E2C97F 40D4E2C7

D5D67E


Page: 125

28950048 00000020 7F40E2C5 E5C5D9C9 E3E87E7F C57F6E40 F1F47AF4 F57AF4F6

4BF2F0

28950068 00000040 8481A381 40A285A3 A2408696 99408689 93A38599 40E7E8E9

5C4B5C

28950088 00000060 40404040 40404040 40404040 40404040 40404040 40404040

404040

289500A8 00000080 40408696 A4958440 40404040 40404040 40404040 40404040

404040

289500C8 000000A0 40404040 40404040 40404040 40404040 40404040 40404040

404040

289500E8 000000C0 40404040 40404C61 D4E2C76E

API0015I 14:45:46.206 Before Call WRITE Descriptor in hex

0000

API0065I 14:45:46.207 After Call WRITE RC : 000000CC ERRNO :

000000

API0002I 14:45:46.207 After Call IP03 End-Call. Rc is : 00000000


Environment

Function-Code : 02


API0015I 14:45:46.207 Before Call CLOSE Descriptor in hex

0000

API0065I 14:45:46.262 After Call CLOSE RC : 00000000 ERRNO :

000000


TAU0023I 14:47:50.379 Subtask for z/Server activated


Environment

Function-Code : 01



Page: 126

API0015I 14:47:50.411 Before Call TAKESOCKET Descriptor in hex

0000

API0065I 14:47:50.411 After Call TAKESOCKET RC : 00000000 ERRNO :

000000



Page: 127

4.4 Setting the trace level

The z/Server trace is the most important source of information to determine the cause of a

problem. The default trace level is specified in the configuration file (IPTRACE parameter) and can

have the following settings:

0 No messages written

1 Only W, E and S severity messages are written to the LE message file

2 Information messages are also written to the LE message file

3 All send and receive data is also written to the LE message file

4 All calls to EZASOKET are also written to the LE message file

5 Full trace

where each level includes all previous levels, this means IPTRACE=2 causes I, W, E and S severity

messages to be written to the LE message file.

The trace level can also be set dynamically from SDSF.

4.5 Gathering information for the Micro Focus SupportLine

This section describes the steps you must perform to gather debugging information to send to the

Micro Focus SupportLine. You may also be requested to supply further information.

The following example is a message that may need to be reported to the SupportLine. In this case, a

System Completion Code 0Cx indicates an unexpected program interruption.

REC00003E 13:56:08.322 Error in Pgm TAURIP27 at Offset 00000C7C

Original Message was : CEE3204S The system detected a protection

exception (System Completion Code=0C4).

The preferred format in which you should send z/Server job output information to the support

hotline is as a GTF trace.

To produce a GTF trace, perform the following steps:

Step 1: Start the IVPGTF started task.

The IVPGTF started task is delivered with the z/Server installation. It should be found in the

PROCLIB concatenation.

The started task should be started with the command:

s ivpgtf.<qual>

<qual> is a qualifier of your choice by which the started task can be addressed later.


Page: 128

When the IVPGTF started task was started, all job output for the running z/Server tasks (holder

task, scheduler task and user server) is written to the output dataset defined with DD IEFRDER in

the IVPGTF started task.

Step 2: Reproduce the error situation.

Step 3: Stop the IVPGTF started task.

Stop the IVPGTF started task with the command:

p ivpgtf.<qual>

After the IVPGTF started task is stopped, the dataset allocated with DD IEFRDER should contain

the gathered job output.

Step 4: Produce an XMIT file from the dataset allocated with DD IEFRDER of the IVPGTF started

task.

You can use the following sample JCL to produce the XMIT file:

//XMIT1 EXEC PGM=IKJEFT01

//SYSPRINT DD SYSOUT=*

//SYSTSPRT DD SYSOUT=*

//SYSTSIN DD *

XMIT ADCD.IBMUSER DATASET('IBMUSER.GTFTRACE.IVPGTF.D120903.T125828') +

OUTDSNAME('IBMUSER.GTFTRACE.IVPGTF.XMIT')

/*

Step 5: FTP the XMIT file in binary format into your local file system and send it to the z/Server

system administrator.

Alternatively, the information needed by the SupportLine can be produced with the following steps.

(Use this procedure only if the error situation cannot be reproduced.)

Step 1: Allocate the job output dataset (RECFM=FB, LRECL=132) under ISPF 3.2:


Page: 129

Ensure that sufficient space is allocated (Space unit, Primary quantity, Secondary quantity, possibly

the Record length (for Space units = RECORDS)).

Tip: If Space Units is specified as KB (kilobytes), MB (megabytes), BYTES or RECORDS, the

allocated space is calculated directly.

Step 2: Go to SDSF.

Step 3: Enter the command:

PT ODSN file.OUT * MOD

at the command line, where file is the name of the file allocated in step1.

Step 4: Open the aborted task (server name) with the S line command, and type:

PT

PT CLOSE

at the command line.

Step 5: Receive the generated file per FTP, in ASCII format as a local file, and then send it to the

z/Server system administrator.


Page: 130

5 z/Server commands

z/Server provides a number of modify commands that can be useful for debugging. z/Server console

commands are invoked with the ‘f’ modify command followed by the z/Server task name, the

environment name, the command and any required optional command parameters.

The following environment/commands are of direct interest for troubleshooting and described in

this section:

DUMP,CONFIG Dump the configuration

TRACE,LEVEL Set dynamically the specified trace level

Other environment/commands not directly related to troubleshooting are described in the z/Server

Installation Guide:

TSO,DISPLAY Display active users (USER=ALL), statistics (STATS) or the content of the

variable pools (VPOOL)

DUMP Dump selected storage areas

REXX Perform certain REXX intermediate commands

RECOVERY Create CEEDUMP, SYSUDUMP or SYSABEND dump

REFRESH Load (refresh) a new version of a load module

5.1 Display the configuration

The DUMP,CONFIG environment/command dumps the configuration for the selected server:

/F <servername>,DUMP,CONFIG

To obtain the dataset list for the selected job (in this case, TAURISPZ), type ? in the NP column.

Enter /F <servername>,DUMP,CONFIG.


Page: 131

To display the associated output, type S in the NP column for DDNAME:CMDTASK.

Typical command output with the configuration (bold) is shown below:

SDSF OUTPUT DISPLAY TAURISPZ STC04854 DSID 107 LINE 66 COLUMNS

02- 81

Display Filter View Print Options Help

------------------------------------------------------------------------

-------

SDSF OUTPUT DISPLAY TAURISPZ STC04854 DSID 107 LINE 103 COLUMNS

02- 81

COMMAND INPUT ===> SCROLL

===> PAGE

IPC0075I 06:05:38.930 Calling Command-Rexx IPCMD

IPC0076I 06:05:38.934 Command-Rexx IPCMD endet with RC 0

IPC0043I 06:05:38.934 Command-Task invoked with MODIFY command

IPC0044I 06:05:38.934 Data for Command : -> DUMP,CONFIG<-


Page: 132

IPC0084I 06:05:38.934 Answer from REXX IPCMD is :


Word 7

1FB513A8 00000000 D4D6C4C9 C6E84040 C4E4D4D7 40404040 C3D6D5C6 C9C70004

1FB511

1FB513C8 00000020 1FB5113C 00000000 00000000 00000000 00000000 00000000

000000

1FB513E8 00000040 00000000 00000000 00000000 00000000 00000000 00000000

000000

1FB51408 00000060 00000000 00000000 00000000 00000000 00000000 00000000

000000

IPC0090I ----------------------------------------------------------------

-------

Initial configuration settings at address 1EE598C0

----------------------------------------------------------------

-------

IPC0091I _CEE_ENVFILE=DD:IPCONFIG

IPC0091I LICENCE_KEY=ABCC1079D3295E29-81B7B37DE8C430CF-8592E737DA50272C

IPC0091I BUFFERSIZE=10

IPC0091I BUFFERUNIT=M

IPC0091I DMPONAPI=0

IPC0091I IPNAME=TCPIP

IPC0091I IPTRACE=1

IPC0091I PORT=1421

IPC0091I NUMTCB=5

IPC0091I PORTCHECK=1

IPC0091I SVC_NO=242

IPC0091I MULTI_REXX=1


Page: 133

IPC0091I TSOE_SCHEDULER=1

IPC0091I TSOE_FIRST_PORT=1425

IPC0091I TSOE_LAST_PORT=1450

IPC0091I TSOE_CLEANUP=1

IPC0091I TSOE_JOBPREFIX=Z

IPC0091I TSOE_MSGCLASS=X

IPC0091I TSOE_JOBSEARCH=SOF

IPC0091I TSOE_SJOB_NAME=IVPUSRZ

IPC0091I TSOE_DSP_TOKEN=TAURSERZ

IPC0091I TSOE_MAXUSRV=5

IPC0091I INITIAL_REXX=TAUINIT

IPC0091I ZCOMTYPE=M

******************************** BOTTOM OF DATA

********************************

Figure 3: Typical command output with the configuration

5.2 Display Dataspace Information

The holder task allocates and manages a common access dataspace (CADS). With this command the

information in this dataspace can be displayed:

f <holder>,display,dsp,[format|dump]

In order to use this command, the holder task must contain the DD statement

//DSPPRT DD SYSOUT=*,LRECL=255

The output for the fomatted display can be found in DSPPRT. If necessary, one needs to scroll to the

extreme right to see the full output.


Page: 134

5.3 Set the Trace Level Dynamically

The TRACE,LEVEL environment/command sets the specified trace level:

F <holder | scheduler | user server>,TRACE,LEVEL=n

Where n is the trace level to be set (0,...5)

DDname CMDTASK (for scheduler and user server) or MAINTASK (for the holder task) show

confirmation:

IPC0066I 12:27:46.579 Trace level changed to 4

Example of log output for trace level 1:


The following is an example of log output for trace level 4 for the same CSI0051E error:



Environment

Function-Code : 01

Task-Area : 20FC10B4 Global


0000


000000



Environment

Function-Code : 37


API0008I 07:54:16.165 Timeout for SELECT is 20 seconds and


Page: 135

API0015I 07:54:16.165 Before Call SELECT Descriptor in hex

0000

API0065I 07:54:16.239 After Call SELECT RC : 00000001 ERRNO :

000000

API0015I 07:54:16.239 Before Call RECV Descriptor in hex

0000

API0065I 07:54:16.239 After Call RECV RC : 00000064 ERRNO :

000000

API0099I

=======================================================================

Data received

=======================================================================


Word 7

2BB69028 00000000 24243245 58454331 50474D44 554D4D59 534F4641 52202020

202020

2BB69048 00000020 20204343 31313431 30303030 30313436 6E756C6C 20204536

324443

2BB69068 00000040 35393139 46302020 20202020 20202020 20202020 20202020

202020

2BB69088 00000060 20202020

…

CSI0006I 07:54:16.254 Catalog Utility called with cmd LISTDSI

Dataset filter : XYZ*.*

Member filter :

Catalog Flags : 00 (hex)


.1.. .... return userdata with member list


Page: 136

..1. .... wait for until recall of dataset is

complete





CSI0007I 07:54:16.265 0 Entries found


CSI0018I 07:54:16.265 Catalog Utility ended with RC 00000048


Function : Delete from TCBSENV

Userid : SOFAR

SVC Rc : 00000000

SAF Rc : 00000000

RACF Rc : 00000000


...


0000

API0065I 07:54:16.270 After Call WRITE RC : 000000CC ERRNO :

000000



Environment

Function-Code : 02



Page: 137


0000


000000


Figure 4: Typical trace output

Troubleshooting note: The actual service that failed is shown with the CSI0006I message (LISTDSI

XYZ*.*=) and the CSI0005I message (0 Entries found).

5.4 Server output files

The servers write logging information to various output files. These files can provide useful

troubleshooting information.

To obtain a list of output files, type ? in the NP column for the associated server.

To display the content of an associated file, type S in the NP column for the associated DDNAME.

The following table shows the type of content for each file:

DDNAME Content

JESMSGLG JES message log


Page: 138

JESJCL Server JCL

JESYSMSG JES system messages

SYSTSPRT REXX output

ZCOTSPRT Performed z/Server commands

MAINTASK LE message file for main task

CMDTASK LE message file for command task

SRVTASK LE message file for service task

Tnnnnnn LE message file for user task n

Table 1: Server output files


Page: 139

6 Bibliography

APIs and services indicate their status in the form of return code, result code, feedback code, etc. If

z/Server receives an unexpected return code (normally non-zero), it normally logs this information

(provided logging is enabled). You must consult manuals provided by the associated software

publisher (normally IBM) to determine the meanings of such codes.

This Bibliography section lists the most important manufacturer manuals with their form number.

Because such manuals are updated regularly (usually for each new z/OS release), the publication

release number is not shown. Remember to use the appropriate publication for the operational

z/OS release.

Note: The publication names change sometimes; the shown name is valid at the time of publication

of this document.

6.1 Associated manufacturer publications

Publication name Form

number

Facility Component

z/OS XML System Services User's

Guide and Reference

SA23-1350 XML XML parser (GXL1CTL,

GXL1INI, GXL1PRS)

MVS Program Management

Advanced Features

SA22-7644 BND Program Binder (IEWBIND)

z/OS DFSMS Managing Catalogs SC26-7409 CSI Catalog Search

Interface program

(IGGCSI00)

z/OS TSO/E REXX Reference SA22-7790 REX REXX services (IRXEXCOM,

IRXINIT, IRXSUBCM, IRXEXEC,

IRXIC)

z/OS TSO/E Programming Services SA22-7789 IKJTSOEV

MVS Programming Authorized

Assembler Services Guide

SA22-7608 CSI,

EMC

DYNALLOC, GQSCAN,

MCSOPER, etc.

MVS Programming: Assembler

Services Reference, Volume 1

SA22-7606 DELETE, DETACH macros

MVS Programming: Authorized SA22-7610 Token services (IEANTxx)


Page: 140


number

Facility Component

Assembler Services Reference

(Volume 2)

MVS Programming: Authorized


(Volume 3)

SA22-7611 LOCASCB macro

MVS Programming: Authorized


(Volume 4)

SA22-7612 SVCUPDTE macro

MVS Programming Extended

Addressability Guide

SA22-7614 HLD Data space

z/OS Communications Server: IP

Sockets API Guide and Reference

SC31-8788 API EZASMI, EZASOKET

MVS System Messages Volume 2 SA22-7632 - ARC11xx error codes

MVS System Messages Volume 6 SA22-7636 CSI IGGCSI00 reason codes

(IDC3009I message)

MVS Using the Subsystem Interface SA22-7642 SSI IEFSSREQ

MVS System Codes SA22-7626 - General system error codes

z/OS Language Environment Run-

Time Messages

SA22-7566 - Language Environment messages

z/OS Language Environment

Programming Guide

SA22-7561 - CEERELES macro

z/OS DFSMShsm Managing Your

Own Data

SC35-0420 - ARCHRCAL macro

SDSF Operation and Customization SA22-7670 - SDSF usage

z/OS Security Server, RACROUTE

Macro Reference

SA22-7692 - RACINIT, RACROUTE macros

z/OS DFSMS Macro Instructions for

Data Sets

SC26-7408 - DESERV macro

z/OS ISPF Services Guide SC34-4819 - ISPEXEC, ISPLINK


Page: 141


number

Facility Component

z/OS Support for Unicode: Unicode

Services

SA22-7649 - Code conversion (CUNLCNV)

Table 2: List of associated manufacturer (IBM) publications

6.2 Associated Enterprise Developer+ publications

The Enterprise Developer+ publications shown in Table 3 describe, among other things, the setup

and configuration file parameters for z/Server.

Publication name Component

z/Server Installation Guide z/Server

Workflow Manager Messages and Troubleshooting Guide client

Workflow Manager Configuration Guide client

Table 3: List of associated Enterprise Developer+ publications


Page: 142

7 Appendix 1 - Understanding the trace output

The trace output (configuration option IPTRACE=5) is the most important starting point for

troubleshooting when you cannot locate the source of the problem using the error messages

displayed.

Although the trace output depends on many factors, such as the installation settings, problem

situation, etc., this appendix will cover the general details. Because the presence or absence of

messages can indicate problem situations, a typical trace is described in detail.

Note: The text ( debugging) indicates that this information is primarily provided for debugging

purposes and, as such, has only very limited interest for the user.

7.1 Main task

The main task trace (DDNAME: MAINTASK) is divided into three parts:

Initialization

Processing

Termination

Whereas the initialization and termination phases have a standard format, the processing phase

obviously depends on the services performed, and so although it is not explained in further detail

here, the associated messages are described in other sections of this document.

7.1.1 Initialization

The initialization phase covers the startup of the main task.

TAU0019W 09:22:25.180 Environment-Variable REATTACH was not specified, using defaults !

TAU0019W 09:22:25.213 Environment-Variable CCSID was not specified, using defaults !

TAU0019W 09:22:25.213 Environment-Variable TSOE_JOB_CLASS was not specified, using defaults

!

TAU0019W 09:22:25.213 Environment-Variable TSOE_SCHED_TAB was not specified, using defaults

!

The optional TAU0019W message block indicates those configuration variables for which the default

values are used. As long as the default values are appropriate, these warnings can be ignored;

otherwise, the configuration file must be changed.


Page: 143

STA0006I 09:22:25.213 Value of Name/Token-Pair TAURSERZ

DSPALET : 01FF001C

DSPORIGIN : 00000000

DSPBLOCK : 0000000A

DSPFLAGS : 00000000


Page: 144

The STA0006I message provides information about the created data space.

DSPALET: data space address

DSPORIGIN: data space origin

DSPBLOCK: number of data space blocks (each 4K)

DSPFLAGS: data space attribute flags

LIC0009I 09:22:25.215 Licence Flag 2 is : 7F

The LIC0009I message provides information about the license. Bits set in the low-order half-byte of

the flag indicate the z/Server services that can be used; in this case, xF = all services.

LIC0007W 09:22:25.218 This server may only be used through a licensed

client.

The LIC0007W message warns that the z/Server can only be used by a licensed client; this is the

normal case.

TAU0001I z/Server TAURISPZ V2R0M01 startup Monday , 27 Aug 2012

09:22:25.21

The TAU0001I message logs the actual start of the z/Server with information about the name of the

started task (TAURISPZ) and its version (V2R0M01). The displayed version must match the installed

version.

REX0013W 09:22:25.221 A TSO/E-Environment already exists.

A additional dynamic Environment is not created.

The REX0013W message warns that no second TSO environment is created; this is the normal case.

REX0024I 09:22:25.224 Initialize z/Server for a complete parallel REXX

environment

The REX0024I message logs the initialization of a parallel REXX environment. Each REXX procedure

must run under its own environment ( MULTI_REXX configuration parameter). If this message

does not appear, just one REXX (non-reentrant) environment is allocated for all REXX procedures

and subtasks.

REX0007I 09:22:25.224 Address of REXX Environment Block is 1EE08C90


Page: 145

Userfield is : 1F02CD80

REX0040I 09:22:25.224 Host-Command-Environment ZCOMM added on env.

Block 00000000.

REX0012I 09:22:25.224 ISPF environment is not available or address of

TLD0 could not be found.

Rexx Environment Table IRXANCHR


Word 7 Word 8 * Storage Content * .

1EE030A0 00000000 C9D9E7C1 D5C3C8D9 F0F1F0F0 00000191 00000003 00000028

00000001 00000000 *IRXANCHR0100...j................*

1EE030C0 00000020 FFFFFFFF 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1EE030E0 00000040 00000000 00000000 1EE08C90 00000001 00000000 00000000

00000000 00000000 *.........?......................*

1EE03100 00000060 1EE03110 008FF020 40000000 00000000 FFFFFFFF 00000000

00000000 00000000 *.?....0. .......................*

1EE03120 00000080 00000000 00000000 00000000 00000000 00000000 00000000

*..... *

The above message block logs the initialization of the REXX Environment Block. The REX0040I

message specifies where the host command environment (ZCOMM) is added, 0 = global. The

REX0012I message indicates the unavailability of ISPF (ISPF is not multitasking).

The logged REXX Environment Table is provided for debugging.

TAU0112I 09:22:25.224 Activating extended Master-Console with Name ADCD0060

TAU0116I 09:22:25.226 Activating extended Master-Console with Name ADCD0060 successful.

Console-Id is : 0200000A

Console-Alert is : 01020038

The above message block logs the activation of an extended master console. The generated name

(ADCD0060) is unique.

The Console ALET specifies the address of the associated data space ( debugging).


Page: 146

TAU0005I 09:22:25.226 Address of Subtask-Storage-Table : 1F02CD80

A(ECB-List for Wait in Subtask) : 1F02CD58

A(ECB-List for POST in Subtask) : 1F02CD6C

The TAU0005I message provides information about the subtask storage table ( debugging).

TAU0134I 09:22:25.226 Server is Master

The TAU0134I message indicates that the server is a master (slave server is not currently

supported).

XML0006I 09:22:25.226 z/Server is using CCSID 1141

The XML0006I message specifies the associated codepage (1141 = Europe).

TAU0003I 09:22:25.228 Address of Server-Communication-Area : 1F02AB78

TAU0046I 09:22:25.228 Address of Program-Property-Table PPT : 1F02BB80

TAU0118I 09:22:25.228 Address of Extended-Console-Buffer : 1F02FC20

TAU0004I 09:22:25.228 Socket-Server is using the following values

Max. no. of Subtask : 5

Max. no. of Sockets : 120

Listening on Port : 1421

Timeout for IPWAIT : 120 seconds

IP-Name : TCPIP

PPT : 0

Dump if API fails : 0

Multiple REXX environm. : Yes

TAU0056I 09:22:25.228 ISPF available : N

Size of User-Area-1 : 5000 Bytes

Size of User-Area-2 : 0 Bytes


Page: 147

Address of User-Area-1 : 1F02D888

Address of User-Area-2 : 00000000

Timeout for Server : 0 Minutes

Reattach after Abend : 1 0 = No

TAU0087I 09:22:25.229

Timeout for Read : 999999 Microsec

Clear-Buffer : 0

Own-Exception-Handler : 1

Exception-Handler-name : TAURIP36

Service-Waittime : 3600000 Millisec

Task-Runaway-Time : 0 Millisec

Console-Waittime : 100 Millisec

Console-Buffersize : 100 KB

TAU0074I 09:22:25.229 Security : 0

Header Length : 100 Bytes

TAU0060I 09:22:25.229 Size Send/Receive buffer : 10 M

Max-Error-Count : 0

PIMA-Size : 500000

CICS-EXCI-Support : 0

CICS-EXCI-Applid :

Portcheck : 1

TSO/E-Scheduler : 1

TAU0061I 09:22:25.229

Size of Variable-Pool : 4096 Bytes


Page: 148

Addr of Variable-Pool : 1F02EC18

Use SVC : Yes SVC 242

Max. no. of USR-Servers : 5

TSO/E User-Server : 0

TAU0137I 09:22:25.229 Create slaves : No

Config for slaves :

Proc for slaves :

The above message block logs various (but not all) configuration parameters.

USS0011I 09:22:25.229 Values for USS

Dubprocess : No

The USS0011I message provides information about USS (UNIX System Services) support.

TAU0067I z/Server startup completed for TAURISPZ for JES2 and ASID 0060

The TAU0067I message indicates the end of the master task initialization with details of the server

name (here TAURISPZ), the supported Job Entry System (here JES2) and the Address Space ID

(ASID).

EMC0009I 09:22:25.232 Routine for Extended-Master-Console invoked with function C0 (Hex)

EMC0002I 09:22:25.234 Command for Extended-Master-Console is

D TCPIP,,N,CONN,PORT=01421

EMC0013I 09:22:25.234 No Rexx or LE-Pgm for postprocessing specified

EMC0020I 09:22:25.234 Internal Console-Buffer allocated at Address 1F048C28

The above message block logs the use of the extended master console. The EMC0013I message

specifies the user program that performs postprocessor processing (not present in this case). The

EMC0020I message specifies the address of the buffer where the answer is located ( debugging).


Page: 149

TAU0101I 09:22:25.234 Entry to Routine Enq-Deq-Routine

Function : E E=Enqueue D=Dequeue

Type : E E=Exclusive S=Shared N=None

Scope : 1 1=Step 2=System 3=Systems

Major-Name : RDZ

Minor-Name : EMCS

Retry-Count : 3

Waittime : 1000 milliseconds

TAU0102I 09:22:25.234 Exit to Routine Enq-Deq-Routine RC was

0

The above message block logs the start of an enqueue/dequeue sequence. Enque-ing is used to lock

resources that cannot be used in parallel. The Function (E) indicates that an enqueue is made. The

Major-Name/Minor-Name pair identifies the resource. A non-zero return code (TAU0102I message)

for an enqueue indicates that the specified resource is being held by another user; the Retry-Count

and the Waittime is the maximum wait time until the resource becomes available.

EMC0018I 09:22:25.234 Using Cart 00000001008D55D0 for Command and

Response

EMC0019I 09:22:25.234 Using Area at Address 1F02FC20 for Response

EMC0008I 09:22:25.235 Waiting for 100 milliseconds.



1F02FC20 00000000 00000004 000000BD 002E0004 800100F4 00E440C5 E9E9F2F5

F0F0C940 D5C5E3E2 *...............4.U EZZ2500I NETS*

1F02FC40 00000020 E3C1E340 C3E240E5 F1D9F1F0 40E3C3D7 C9D740F7 F8F80050

00044001 00F400E4 *TAT CS V1R10 TCPIP 788.&.. ..4.U*

1F02FC60 00000040 40E4E2C5 D940C9C4 4040C3D6 D5D54040 404040D3 D6C3C1D3

40E2D6C3 D2C5E340 * USER ID CONN LOCAL SOCKET *

1F02FC80 00000060 40404040 40404040 4040C6D6 D9C5C9C7 D540E2D6 C3D2C5E3

40404040 40404040 * FOREIGN SOCKET *


Page: 150

1F02FCA0 00000080 40E2E3C1 E3C50023 00042001 00F400E4 40F040D6 C640F040

D9C5C3D6 D9C4E240 * STATE.......4.U 0 OF 0 RECORDS *

1F02FCC0 000000A0 C4C9E2D7 D3C1E8C5 C4001C00 04300100 F400E440 C5D5C440

D6C640E3 C8C540D9 *DISPLAYED.......4.U END OF THE R*

1F02FCE0 000000C0 C5D7D6D9 E3

*EPORT. *

EMC0005I 09:22:25.336 Response from Extended-Master-Console is

4 Lines

EZZ2500I NETSTAT CS V1R10 TCPIP 788.&

USER ID CONN LOCAL SOCKET FOREIGN SOCKET

STATE.?

0 OF 0 RECORDS DISPLAYED..

END OF THE REPORT..



1F048C28 00000000 00000004 000000BD 002E4040 40404040 404040C5 E9E9F2F5

F0F0C940 D5C5E3E2 *.......... EZZ2500I NETS*

1F048C48 00000020 E3C1E340 C3E240E5 F1D9F1F0 40E3C3D7 C9D740F7 F8F80050

40404040 40404040 *TAT CS V1R10 TCPIP 788.& *

1F048C68 00000040 40E4E2C5 D940C9C4 4040C3D6 D5D54040 404040D3 D6C3C1D3

40E2D6C3 D2C5E340 * USER ID CONN LOCAL SOCKET *

1F048C88 00000060 40404040 40404040 4040C6D6 D9C5C9C7 D540E2D6 C3D2C5E3

40404040 40404040 * FOREIGN SOCKET *

1F048CA8 00000080 40E2E3C1 E3C50023 40404040 40404040 40F040D6 C640F040

D9C5C3D6 D9C4E240 * STATE.. 0 OF 0 RECORDS *

1F048CC8 000000A0 C4C9E2D7 D3C1E8C5 C4001C40 40404040 40404040 C5D5C440

D6C640E3 C8C540D9 *DISPLAYED.. END OF THE R*

1F048CE8 000000C0 C5D7D6D9 E3 *EPORT.*

The above message block logs an extended master console usage, which being non-reentrant, must

be enclosed within an ENQ/DEQ block. Increase the console wait time if it is too small. The

EMC0005I message logs the formatted message in the displayed storage.


Page: 151


Function : D E=Enqueue D=Dequeue



Major-Name : RDZ

Minor-Name : EMCS

Retry-Count : 3



0

The above message block logs the end of an enqueue/dequeue sequence. The Function (D) indicates

that a dequeue is made, in particular, for the enqueue started at 09:22:25.234.

A non-zero return code (TAU0102I message) for a dequeue indicates that the specified resource

could not be released (this is an error situation).

EMC0021I 09:22:25.336 Internal Console-Buffer at Address 1F048C28

released.

This message corresponds to the EMC message issued at 09:22:25.234.

TAU0066I 09:22:25.336 Address of EZA-Global-Data-Area : 1F009770

TAU0010I 09:22:25.336 Subtask 1 started A(TCB) : 008BFA30 A(ECB) : 1F02CD80

TAU0010I 09:22:25.336 Subtask 2 started A(TCB) : 008BF7A0 A(ECB) : 1F02CF10

TAU0010I 09:22:25.336 Subtask 3 started A(TCB) : 008BF510 A(ECB) : 1F02D0A0

TAU0010I 09:22:25.336 Subtask 4 started A(TCB) : 008BF280 A(ECB) : 1F02D230

TAU0010I 09:22:25.336 Subtask 5 started A(TCB) : 008BBE88 A(ECB) : 1F02D3C0

TAU0041I 09:22:25.336 CmdTask 6 started A(TCB) : 008BBCF0 A(ECB) : 1F02D550

TAU0110I 09:22:25.336 SrvTask 7 started A(TCB) : 008BBA60 A(ECB) : 1F02D6E0

TAU0024I 09:22:25.341 Highest socket Number assigned to Server is 119


Page: 152

The above message block is used for simplify debugging; the addresses of the associated TCBs and

ECBs are listed.

TAU0039I 09:22:25.342 Socket-Server Information

Domain Name local host :

svaratnl................

IP-Address current host : 192.168.9.72

VIPA for internal usage :

IP-Address VIPA :

The TAU0039I message logs a get named host.

SLR0111I 09:22:25.342 TSO/E-Scheduler Init/Term-Routine called with

function START

SLR0001I 09:22:25.349 TSO-Scheduler initialization

The above message block logs a scheduler initialization.

HLD0029I 09:22:25.349 User administration called with function >> Add

Server <<

Flag is : 40

1.. .... called from holder task

.1.. .... use dataspace

HLD0030I 09:22:25.535 User administration ended with RC 00000000 (hex)

The above message block requests user administration. If the return code (HLD0030I message) is

greater than 4, the server is not stopped (data space is already reserved).

SLR0019I 09:22:25.535 TSOE-Scheduler initialization completed.

Delay after Submit : 1000

milliseconds

Job-Class : .

Job-MsgClass : X


Page: 153

First Port : 1425

Last Port : 1450

Cleanup-User-Jobs : 1

SLR0049I 09:22:25.535

Job-Prefix : Z

Job-Search-String : ZSOF*

Scheduler-Table : Shared-Storage

Inital XML document DSN : << not used

Inital XML document MEM : << not used, now init

rexx

Max. parallel USR-Serv. : 5

No of Slaves : 0

SLR0081I 09:22:25.535 User server policy is : Started Job

The above message block logs configuration parameters for a scheduler initialization.

SPR0001I 09:22:26.128 Standard-Pool-Routine called with

Function : VPUT

Var-Typ : SYS

Var-Name : JPREFIX

Var-Content : Z


Function : E E=Enqueue D=Dequeue



Major-Name : TAU


Page: 154

Minor-Name : VPOOL

Retry-Count : 3



0


Function : D E=Enqueue D=Dequeue



Major-Name : TAU

Minor-Name : VPOOL

Retry-Count : 3



0

The above message block logs a standard pool use. The standard pool is conceptually similar to the

similar ISPF profile but being not multitasking capable, ENQ/DEQ is required.

The SPR0001I message specifies the function (VPUT; other possible functions are VDEL and VDEL),

the type (SYS; another possible type is USER), the variable name (JPREFIX) and its content (Z).

JES0001I 09:22:26.128 JES Utility called with cmd XUSTOP

SSI0008I

=======================================================================

Storage for SSOB

=======================================================================




Page: 155

1F00B8B0 00000000 E2E2D6C2 001C0050 008FCD7C 00000000 1F00B8CC 00000000

00000000 *SSOB...&...?................. *

SSI0008I

=======================================================================

Storage for STAT

=======================================================================



1F00B8CC 00000000 01C8E2E3 C1E30701 06000000 01000000 7F46A000 7F46A018

20000000 0000E9E2 *.HSTAT.........."...".........ZS*

1F00B8EC 00000020 D6C65C40 40400000 00000000 00000000 00000000 00000000

00000000 00000000 *OF* ..........................*

1F00B90C 00000040 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B92C 00000060 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B94C 00000080 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B96C 000000A0 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B98C 000000C0 00000000 00000000 00000000 00000000 00000000 7F46A230

00000003 00000000 *....................".s.........*

1F00B9AC 000000E0 00000000 00349A7E 00000000 00000000 00000000 00000000

00000000 00000000 *.......=........................*

1F00B9CC 00000100 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B9EC 00000120 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA0C 00000140 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*


Page: 156

1F00BA2C 00000160 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA4C 00000180 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA6C 000001A0 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA8C 000001C0 00000000 00000000

*......... *

The above message block logs the invocation of the JES Utility; in this case, call the XUSTOP

command.

SSI0002I 09:22:26.147 Pointer Output (STATJOBF) : 7F46A230

No of jobs that match : 00000003

SSI0008I

=======================================================================

Storage for SJQE

=======================================================================



7F46A230 00000000 E2D1D8C5 001C0000 7F46A138 00000000 D1C5E2F2 00000000

00000000 *SJQE....".?.....JES2......... *

SSI0008I

=======================================================================

Storage for Sec.

=======================================================================



7F46A24C 00000000 00DA0000

*..... *


Page: 157

SSI0009I

=======================================================================

Storage for Section Len : 00A8 Type : 01 Modifier : 00

=======================================================================



7F46A250 00000000 00A80100 E9E2D6C6 C1D94040 E2E3C3F0 F4F7F8F7 E2E3C3F0

F4F7F8F7 E2E3C340 *.y..ZSOFAR STC04787STC04787STC *

7F46A270 00000020 40404040 D5F14040 40404040 D5F14040 40404040 D5F14040

40404040 40404040 * N1 N1 N1 *

7F46A290 00000040 40404040 D5F14040 40404040 40404040 40404040 E3C1E4E4

E2D94040 00000000 * N1 TAUUSR ....*

7F46A2B0 00000060 00000000 40404040 40404040 40404040 40404040 40404040

40404040 40404040 *.... *

7F46A2D0 00000080 40404040 40401401 01010020 41000000 00000033 000012B3

4040F04B F0F5F1F6 * .................. 0.0516*

7F46A2F0 000000A0 00000000 00000000 *......... *

SSI0009I

=======================================================================

Storage for Section Len : 002E Type : 02 Modifier : 00

=======================================================================



7F46A2F8 00000000 002E0200 00000000 CA0BDCAD 0003D006 00000000 00000008

00010000 40404040 *..............?............. *

7F46A318 00000020 40404040 00010001 0000003C 0000 * *

SSI0008I

=======================================================================

Storage for SJQE


Page: 158

=======================================================================



7F46A138 00000000 E2D1D8C5 001C0000 7F46A040 00000000 D1C5E2F2 00000000

00000000 *SJQE....".. ....JES2......... *

SSI0008I

=======================================================================

Storage for Sec.

=======================================================================



7F46A154 00000000 00DA0000

*..... *

SSI0009I

=======================================================================


=======================================================================





7F46A178 00000020 40404040 D5F14040 40404040 D5F14040 40404040 D5F14040

40404040 40404040 * N1 N1 N1 *

7F46A198 00000040 40404040 D5F14040 40404040 40404040 40404040 E3C1E4E4

E2D94040 00000000 * N1 TAUUSR ....*

7F46A1B8 00000060 00000000 40404040 40404040 40404040 40404040 40404040

40404040 40404040 *.... *

7F46A1D8 00000080 40404040 40401401 01010020 41000000 00000032 000012B0

4040F04B F0F5F1F6 * .................. 0.0516*


Page: 159

7F46A1F8 000000A0 00000000 00000000

*......... *

SSI0009I

=======================================================================


=======================================================================



7F46A200 00000000 002E0200 00000000 CA0BDAC9 00083B06 00000000 00000008

00010000 40404040 *...........I................ *

7F46A220 00000020 40404040 00010001 00000038 0000

* ........... *

SSI0008I

=======================================================================

Storage for SJQE

=======================================================================



7F46A040 00000000 E2D1D8C5 001C0000 00000000 00000000 D1C5E2F2 00000000

00000000 *SJQE............JES2......... *

SSI0008I

=======================================================================

Storage for Sec.

=======================================================================



7F46A05C 00000000 00DA0000 *..... *


Page: 160

SSI0009I

=======================================================================


=======================================================================





7F46A080 00000020 40404040 D5F14040 40404040 D5F14040 40404040 D5F14040

40404040 40404040 * N1 N1 N1 *

7F46A0A0 00000040 40404040 D5F14040 40404040 40404040 40404040 E3C1E4E4

E2D94040 00000000 * N1 TAUUSR ....*

7F46A0C0 00000060 00000000 40404040 40404040 40404040 40404040 40404040

40404040 40404040 *.... *

7F46A0E0 00000080 40404040 40401401 01010020 41000000 00000030 000012A9

4040F04B F0F5F1F6 * .................z 0.0516*

7F46A100 000000A0 00000000 00000000 *......... *

SSI0009I

=======================================================================


=======================================================================



7F46A108 00000000 002E0200 00000000 CA0AF769 0107D506 00000000 00000008

00010000 40404040 *..........7...N............. *

7F46A128 00000020 40404040 00010001 00000020 0000

* ........... *

JES0002I 09:22:26.147 JES Utility ended with RC 00000000


Page: 161

The above message block logs the received information (in this case, 3 jobs were found, SSI0002I

message,) and confirms the completion of the JES Utility request (JES0002I message).

TAU0141I 09:22:26.147 z/Server Maintask READY for client's

TAU0006I 09:34:37.136 Client 192.168.9.72 connected on port

18385 Desc 1

The above message block indicates that the z/Server is ready to accept work (TAU0141I message).

TAU0051W 09:34:37.136 Shutdown Server

SLR0111I 09:34:37.136 TSO/E-Scheduler Init/Term-Routine called with

function STOP

JES0001I 09:34:37.140 JES Utility called with cmd XUSTOP

SSI0008I

=======================================================================

Storage for SSOB

=======================================================================



1F00B8B0 00000000 E2E2D6C2 001C0050 008FCD7C 00000000 1F00B8CC 00000000

00000000 *SSOB...&...?................. *

SSI0008I

=======================================================================

Storage for STAT

=======================================================================



1F00B8CC 00000000 01C8E2E3 C1E30701 06000000 01000000 7F455000 7F455018

20000000 0000E9E2 *.HSTAT..........".&.".&.......ZS*

1F00B8EC 00000020 D6C65C40 40400000 00000000 00000000 00000000 00000000

00000000 00000000 *OF* ..........................*


Page: 162

1F00B90C 00000040 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B92C 00000060 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B94C 00000080 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B96C 000000A0 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B98C 000000C0 00000000 00000000 00000000 00000000 00000000 7F455230

00000003 00000000 *...................."...........*

1F00B9AC 000000E0 00000000 0030B5DF 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B9CC 00000100 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00B9EC 00000120 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA0C 00000140 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA2C 00000160 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA4C 00000180 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA6C 000001A0 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1F00BA8C 000001C0 00000000 00000000

*......... *

SSI0002I 09:34:37.143 Pointer Output (STATJOBF) : 7F455230

No of jobs that match : 00000003

SSI0008I

=======================================================================

Storage for SJQE


Page: 163

=======================================================================



7F455230 00000000 E2D1D8C5 001C0000 7F455138 00000000 D1C5E2F2 00000000

00000000 *SJQE....".......JES2......... *

SSI0008I

=======================================================================

Storage for Sec.

=======================================================================



7F45524C 00000000 00DA0000

*..... *

SSI0009I

=======================================================================


=======================================================================



7F455250 00000000 00A80100 E9E2D6C6 C1D94040 E2E3C3F0 F4F7F8F7 E2E3C3F0


7F455270 00000020 40404040 D5F14040 40404040 D5F14040 40404040 D5F14040

40404040 40404040 * N1 N1 N1 *

7F455290 00000040 40404040 D5F14040 40404040 40404040 40404040 E3C1E4E4

E2D94040 00000000 * N1 TAUUSR ....*

7F4552B0 00000060 00000000 40404040 40404040 40404040 40404040 40404040

40404040 40404040 *.... *

7F4552D0 00000080 40404040 40401401 01010020 41000000 00000033 000012B3

4040F04B F0F5F1F6 * .................. 0.0516*


Page: 164

7F4552F0 000000A0 00000000 00000000 *......... *

SSI0009I

=======================================================================


=======================================================================



7F4552F8 00000000 002E0200 00000000 CA0BDCAD 0003D006 00000000 00000008

00010000 40404040 *..............?............. *

7F455318 00000020 40404040 00010001 0000003C 0000* .......... *

SSI0008I

=======================================================================

Storage for SJQE

=======================================================================



7F455138 00000000 E2D1D8C5 001C0000 7F455040 00000000 D1C5E2F2 00000000

00000000 *SJQE....".& ....JES2......... *

SSI0008I

=======================================================================

Storage for Sec.

=======================================================================



7F455154 00000000 00DA0000

*..... *

SSI0009I

=======================================================================


Page: 165


=======================================================================





7F455178 00000020 40404040 D5F14040 40404040 D5F14040 40404040 D5F14040

40404040 40404040 * N1 N1 N1 *

7F455198 00000040 40404040 D5F14040 40404040 40404040 40404040 E3C1E4E4

E2D94040 00000000 * N1 TAUUSR ....*

7F4551B8 00000060 00000000 40404040 40404040 40404040 40404040 40404040

40404040 40404040 *.... *

7F4551D8 00000080 40404040 40401401 01010020 41000000 00000032 000012B0

4040F04B F0F5F1F6 * .................. 0.0516*

7F4551F8 000000A0 00000000 00000000 *......... *

SSI0009I

=======================================================================


=======================================================================



7F455200 00000000 002E0200 00000000 CA0BDAC9 00083B06 00000000 00000008

00010000 40404040 *...........I................ *

7F455220 00000020 40404040 00010001 00000038 0000 * *

SSI0008I

=======================================================================

Storage for SJQE

=======================================================================


Page: 166



7F455040 00000000 E2D1D8C5 001C0000 00000000 00000000 D1C5E2F2 00000000

00000000 *SJQE............JES2......... *

SSI0008I

=======================================================================

Storage for Sec.

=======================================================================



7F45505C 00000000 00DA0000 *..... *

SSI0009I

=======================================================================


=======================================================================





7F455080 00000020 40404040 D5F14040 40404040 D5F14040 40404040 D5F14040

40404040 40404040 * N1 N1 N1 *

7F4550A0 00000040 40404040 D5F14040 40404040 40404040 40404040 E3C1E4E4

E2D94040 00000000 * N1 TAUUSR ....*

7F4550C0 00000060 00000000 40404040 40404040 40404040 40404040 40404040

40404040 40404040 *.... *

7F4550E0 00000080 40404040 40401401 01010020 41000000 00000030 000012A9

4040F04B F0F5F1F6 * .................z 0.0516*

7F455100 000000A0 00000000 00000000 *......... *


Page: 167

SSI0009I

=======================================================================


=======================================================================



7F455108 00000000 002E0200 00000000 CA0AF769 0107D506 00000000 00000008

00010000 40404040 *..........7...N............. *

7F455128 00000020 40404040 00010001 00000020 0000 * ... *

JES0002I 09:34:37.144 JES Utility ended with RC 00000000

The above message block logs the stop from the command task (XUSTOP command).

HLD0029I 09:34:37.144 User administration called with function >> Delete

Server <<

Flag is : 40

1... .... called from holder

task



TAU0114I 09:34:37.145 Deactivating extended Master-Console with Name

ADCD0060

The above message block logs the termination of the main task.

7.2 User task

The user task trace (DDNAME: Tnnnnnnn, where n is the user task number) is divided into three

parts:

Initialization

Processing

Termination


Page: 168

Whereas the initialization and termination phases have a standard format, the processing phase

obviously depends on the services performed, and so although it is not explained in further detail

here, the associated messages are described in the associated sections of this document.

7.2.1 Initialization

The initialization phase concerns the startup of the associated user task.

TAU0008I 09:22:26.169 Subtask 1 for z/Server is initializing

The TAU0008I message specifies the initialization of the user subtask with the shown number (1).

Each user subtask has its own unique subtask number.

XML0010I 09:22:26.411 XML-Interface called with function Init

TAU0015I 09:22:26.413 Before Call GLX1INI

TAU0065I 09:22:26.413 After Call GLX1INI RC : 00000000 ERRNO :

00000000

XML0011I 09:22:26.413 XML-Interface ended with RC 00000000 and Reason

00000000

The above message block logs the initialization of the XML System Service parser with the status of

the invoked GLX1INI service. A return code (RC) greater than 4 indicates an error situation (

z/OS XML System Services User's Guide and Reference).

TAU0025I 09:22:26.413 Inp-Msg-Area for subtask allocated at 29D58028

Out-Msg-Area for subtask allocated at 2A759028

Wrk-Msg-Area for subtask allocated at 2B15A028


PIMA for subtask allocated at 21004B60

PIMA area is 500000 Bytes long

ECI-Table for subtask allocated at 00000000

>>cics

TAU0131I 09:22:26.413 XMLCA for subtask allocated at 20FE9B48 >>

ctl area (debug


Page: 169

TS for subtask allocated at 20FE9B48 >>

temp stor

TAU0118I 09:22:26.414 Address of Extended-Console-Buffer : 2107EC88

TAU0125I 09:22:26.414 Additional Heap (below the Line) with 00001000

bytes created. Heapid is 20FC590C.

TAU0126I 09:22:26.414 Heap below for subtask allocated at 0008B028

The above message block specifies the storage areas allocated for the various subtask buffers, DCBs,

etc.( debugging).

UNI0001I 09:22:26.414 UniCode Character-Conversion from CCSID

1141 to CCSID 1208

UNI0002I 09:22:26.476 UniCode Character-Conversion endet with RC

00000000 and Reason 00000000.

See z/OS Support for Unicode(TM): Using Conversion

Services for details.

UNI0003I ----------------------------------------------------------------

--------

Result after Conversion OldLen : 00000008 NewLen : 00000008

----------------------------------------------------------------

--------



20FE9B8C 00000000 7A436F6D 6D313233 *:.?__.... *

The above message block logs the invocation of Unicode Conversion Services for code conversion.

A return code (RC) greater than 4 indicates an error situation ( z/OS Support for Unicode:

Unicode Services). The storage content shown after conversion should be readable, if not, an

incorrect codepage (CCSID configuration) has been specified.

Some common CCSIDs: 1047 (USA), 1141 (Europe), 1208 (UTF-8).

Note: The length after conversion may be longer for a conversion to UTF-8 (when the converted

text contains accented characters, etc.).


Page: 170

TAU0107I 09:22:26.476 Registration for exception-handler >> TAURIP36<<

successful.

The TAU0107I message logs the successful registration of the exception handler.

TAU0142I 09:22:26.476 z/Server Subtask READY for clients

The TAU0142I message logs the readiness of the user task to accept work and indicates the end of

the initialization phase.

7.2.2 Termination

The termination phase concerns the shutdown of the associated user task.

TAU0053I 09:34:37.148 Shutdown Subtask

The TAU0053I message marks the start of the termination.

XML0010I 09:34:37.148 XML-Interface called with function Term

TAU0015I 09:34:37.149 Before Call GLX1TRM

TAU0065I 09:34:37.149 After Call GLX1TRM RC : 00000000 ERRNO :

00000000


00000000

The above message block logs the termination of the XML System Service parser with the status of

the invoked GLX1TRM service. A return code (RC) greater than 4 indicates an error situation (

z/OS XML System Services User's Guide and Reference).

REC0001E 09:34:37.149 Recovery-Exception-Handler was invoked.

CIB-Flag-5 : 02

CIB-Flag-6 : 25

The REC0001E message logs the invocation of the recovery exception handler.

7.3 Command task

The command task trace (DDNAME: CMDTASK) logs the invocation of commands.


Page: 171

Many of the messages are the same as for other traces and so are not described again here.

IPC0040I 09:22:25.341 z/Server Command-Task is initializing





00000000


00000000

TAU0025I 09:22:26.203 Inp-Msg-Area for subtask allocated at 26111028

Out-Msg-Area for subtask allocated at 26B12028

Wrk-Msg-Area for subtask allocated at 27513028


PIMA for subtask allocated at 1FB83058



TAU0131I 09:22:26.203 XMLCA for subtask allocated at 1FB68040

TS for subtask allocated at 1FB68040

TAU0118I 09:22:26.203 Address of Extended-Console-Buffer : 1FBFD180


bytes created. Heapid is 1FB45784.

TAU0126I 09:22:26.203 Heap below for subtask allocated at 00089028

REX0038I 09:22:26.203 Creating a non-reentrant REXX environment for

TSO/E and ISPF

REX0007I 09:22:26.386 Address of REXX Environment Block is 2430DC90

Userfield is : 1F02D550


Page: 172

REX0039I 09:22:26.386 Creating a reentrant REXX environment for REXX

REX0007I 09:22:26.387 Address of REXX Environment Block is 27F38C90

Userfield is : 1F02D550

REX0040I 09:22:26.387 Host-Command-Environment ZCOMM added on env.

Block 27F38C90.


1141 to CCSID 1208


00000000 and Reason 00000000.



UNI0003I ----------------------------------------------------------------

--------


----------------------------------------------------------------

--------



1FB68084 00000000 7A436F6D 6D313233

*:.?__.... *

IPC0071I 09:22:26.390 Using Command-Exit TAURIP77

IPC0074I 09:22:26.391 Using Command-Rexx IPCMDTSO

IPC0042I 09:22:26.391 Address of Communication-Event-Control-Block :

00FB89DC

Address of Command-Input-Buffer :

00F569F0

Token :

00000000

TAU0107I 09:22:26.391 Registration for exception-handler >> TAURIP86<<

successful.


Page: 173

IPC0075I 09:34:37.086 Calling Command-Rexx IPCMD

IPC0076I 09:34:37.095 Command-Rexx IPCMD endet with RC 0

IPC0043I 09:34:37.095 Command-Task invoked with STOP command

IPC0044I 09:34:37.095 Data for Command : -> <-

IPC0084I 09:34:37.095 Answer from REXX IPCMD is :



1FB483A8 00000000 E2E3D6D7 40404040 C3C9C26D E2E4C2C3 D4C4812C 1FB48130

1FB48138 1FB48134 *STOP CIB_SUBCMDa...a...a...a.*

1FB483C8 00000020 1FB4813C 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *..a.............................*

1FB483E8 00000040 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

1FB48408 00000060 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

IPC0064I 09:34:37.096 Scheduling CIB_SUBC Request to Maintask

IP-Address : 192.168.9.72

Port : 1421


Environment

Function-Code : 32

Task-Area : 1FB482F0 Global

API0015I 09:34:37.098 Before Call SOCKET Descriptor in hex

0000

API0065I 09:34:37.135 After Call SOCKET RC : 00000000 ERRNO :

00000000

API0015I 09:34:37.135 Before Call CONNECT Descriptor in hex

0000


Page: 174

API0065I 09:34:37.136 After Call CONNECT RC : 00000000 ERRNO :

00000000



Environment

Function-Code : 02

Task-Area : 1FB482F0 Global


0000


00000000


IPC0052I z/Server shutdown


CIB-Flag-5 : 02

CIB-Flag-6 : 25


Page: 175

8 Appendix 2 - z/Server Message Driver

To simplify the testing and debugging of z/Server, you can use the Message Driver ISPF application to

run test cases for API services. The Message Driver can often also be used for troubleshooting to

recreate complex fault situations and client faults that occur randomly. Because the Message Driver

is a very powerful tool with many features, consult the z/Server Programming Reference for further

details.

This appendix provides several simple scenarios to illustrate typical use situations.

8.1 Scenario1 - Invoking a REXX Exec (detailed description)

This simple scenario invokes a REXX exec that uses the PUTMSG z/Server command.

8.1.1 Invocation XML

The invocation XML document consists of a TSO/E scheduler message (<TSOSCHED> root

message) containing a <ROUTEMSG> element that specifies the message to be routed to the user

server ( z/Server Programming Reference).

Example:

<TSOSCHED>

<ROUTEMSG CMD="EXEC" PGM="TESTRX" PORT="1425" XML="N"></ROUTEMSG>

</TSOSCHED>

The example invocation XML document contains the following tags:

CMD "EXEC" a REXX exec is to be performed

PGM "TESTRX" the name of the REXX exec to be performed

PORT "1425" the port to be used by the TSO/E scheduler

the TSOE_FIRST_PORT and TSOE_LAST_PORT

configuration parameters specify the permitted port range

XML "N" do not set bit 2 of the field socket header

8.1.2 Invoked REXX exec (TESTRX)

/* REXX */


Page: 176

zCOMM.OUTMSG = "Response from TESTRX" DATE() TIME()

ADDRESS ZCOMM "PutMsg"

EXIT 0

The invoked REXX exec must be contained in the SYSEXEC concatenation of the PROCLIB started

task member for the user server (z/Server Installation and System Configuration Guide).

Note: The XML and REXX libraries must be PO datasets with RECFM=F or FB and LRECL=80.

8.1.3 Invocation sequence

1. Message driver invocation is invoked from the ISPF Command Shell (normally Option 6 from

the ISPF Primary Option Menu) with the ex <hlq>.rexx(tau) command.


Page: 177

The z/Server Host Driver main screen is then displayed:

2. Complete the required Host-Driver fields, in particular, the Ip-Addr (the IP address of the

required end point), the TCPName ( configuration file IPNAME parameter), the port

number ( configuration file PORT parameter), and the name of the message dataset that

contains the test XML, in this case 'SOFAR.FB.XML(HDTEST1)'.


Page: 178

3. Enter the appropriate license key in the LICT field, which is the third input field on the

Header Token-2, option 3, LICT line. Note: This is a hidden field.

4. Create a data space. Place the cursor on the Dataspace action bar entry and press ENTER.

5. Enter the appropriate user server name in the TokenName field of the popup screen.

6. Press END (PF3).

The response is displayed immediately, which should be the form shown below.


Page: 179

Dataspace Size in Bytes : 40.960

in Blocks : 10

First Port over all Servers : 1.420

Last Port over all Servers : 1.500

No of Ports over all Servers : 80

Current no of Servers : 1

Address of Server-Area : 100

Size of Server-Area : 2.560

Address of User-Area : 2.660

Size of User-Area : 20.160

Max. Severs allowed : 20

-------------------------------------------------------------------------

-------

Information for Server : TAURISPZ

-------------------------------------------------------------------------

-------

Servers first Port : 1.425

Servers last Port : 1.450

Servers no of Ports : 25

Addr of servers user table : 3.920

Servers first CRP : 6

Servers last CRP : 31

Servers current user count : 1

-------------------------------------------------------------------------

-------


Page: 180

Flag-1 (F1) Flag-2 (F2) Flag-3 (F3)

1... .... Verified 1... .... Timeout 1... .... ENQ

.1.. .... Logon .1.. .... Main Ready

..1. .... Sub Ready

-------------------------------------------------------------------------

------

Userid JobName JobId SYS Port L F1 F2 F3 JP CRP Ip-Addr-Client

Ip/Port

-------------------------------------------------------------------------

-------

........ ........ ........ .... 01425 D 00 00 00 00 0006

........ ........ ........ .... 01426 D 00 00 00 00 0007

SOFJK ZSOFJK STC05182 ADCD 01427 M 00 60 00 00 0008 192.168.9.72

192.168

........ ........ ........ .... 01428 D 00 00 00 00 0009

........ ........ ........ .... 01429 D 00 00 00 00 000A

........ ........ ........ .... 01430 D 00 00 00 00 000B

........ ........ ........ .... 01431 I 00 00 00 00 000C

........ ........ ........ .... 01432 I 00 00 00 00 000D

The lower part of the output shows the defined ports (01425:…) and any user servers currently

running, in this case, ZSOFJK on port 01427.

7. Log on to the user server. Place the cursor on the Logon action bar entry and press ENTER.


Page: 181

8. Type your password in the Password field of the popup screen.

9. Press ENTER (PF3).


Answer from Server for Message 1 is 204 Bytes long.

===================================================================


Page: 182

00000000 000000CC 4CD4E2C7 40C6C1C3 C9C47E7F *...ö<MSG FACID="*

00000010 E2D3D97F 40D4E2C7 D5D67E7F F0F0F2F3 *SLR" MSGNO="0023*

00000020 7F40E2C5 E5C5D9C9 E3E87E7F C97F6E40 *" SEVERITY="I"> *

00000030 F0F77AF3 F27AF0F9 4BF2F1F6 40E3E2D6 *07:32:09.216 TSO*

00000040 C560E285 99A58599 40E9E2D6 C6C1D940 *E-Server ZSOFAR *

00000050 4040A689 A38840D1 9682C9C4 40E2E3C3 * with JobID STC*

00000060 F0F5F2F3 F1408696 9940E4A2 859940E2 *05231 for User S*

00000070 D6C6C1D9 40404040 A2A48294 89A3A385 *OFAR submitte*

00000080 844B4040 40404040 40404040 40404040 *d. *

00000090 40404040 40404040 40404040 40404040 * *

000000A0 40404040 40404040 40404040 40404040 * *

000000B0 40404040 40404040 40404040 40404040 * *

000000C0 40404040 40404C61 D4E2C76E * </MSG> *

This output contains the JobID of the user server, in this case STC05231.

10. Finally, execute the XML with the Full Conversion function: place the cursor on the FullConv

action bar entry and press ENTER.

Notes:

FullConv corresponds to the individual actions: Select, Receive, Write and Close.

Other commands may need to be performed before invoking, for example, the AdduSrv (Add

User server) command when ISPF dialog support is required.


Page: 183

The response is displayed immediately and obviously depends on the action performed.

The trace list for the FullConv action is displayed.


===================================================================

00000000 0000002C D985A297 9695A285 40869996 *....Response fro*

00000010 9440E3C5 E2E3D9E7 40F540E2 859740F2 *m TESTRX 5 Sep 2*

00000020 F0F1F240 F0F77AF3 F47AF3F6 *012 07:34:36 *

This output shows the issued message:

Response from TESTRX 5 Sep 2012 07:34:36

11. Log off to terminate the user server: on the Logoff action bar entry, press ENTER.


Page: 184



===================================================================

00000000 0000007C 4CD4E2C7 40C6C1C3 C9C47E7F *...@<MSG FACID="*

00000010 E2D3D97F 40D4E2C7 D5D67E7F F0F0F2F6 *SLR" MSGNO="0026*

00000020 7F40E2C5 E5C5D9C9 E3E87E7F C97F6E40 *" SEVERITY="I"> *

00000030 F0F77AF3 F87AF2F0 4BF9F3F9 40E2A396 *07:38:20.939 Sto*

00000040 9760C396 94948195 84408696 9940E4A2 *p-Command for Us*

00000050 859940E2 D6C6C1D9 40404040 81838385 *er SOFAR acce*

00000060 97A38584 4B404040 40404040 40404040 *pted. *

00000070 40404040 40404C61 D4E2C76E * </MSG> *

The output shows that a Stop command for the logged-on user SOFAR has been passed to z/Server.


Page: 185

If NOTIFY is specified in the user server JCL, the following message is displayed on completion of

the user server:

07.38.23 STC05231 $HASP165 ZSOFAR ENDED AT N1 MAXCC=0 CN(INTERNAL)

User server trace output for trace level 4.





00000000


00000000

TAU0025I 07:32:08.396 Inp-Msg-Area for subtask allocated at 2571C028

Out-Msg-Area for subtask allocated at 2611D028

Wrk-Msg-Area for subtask allocated at 26B1E028


PIMA for subtask allocated at 210CAB60



TAU0131I 07:32:08.396 XMLCA for subtask allocated at 210AFB48

TS for subtask allocated at 210AFB48


bytes created. Heapid is 2108B6CC.

TAU0126I 07:32:08.396 Heap below for subtask allocated at 0009F028


1141 to CCSID 1208


Page: 186


00000000 and Reason 00000000.



UNI0003I ----------------------------------------------------------------

--------


----------------------------------------------------------------

--------



210AFB8C 00000000 7A436F6D 6D313233 *:.?__.... *

HLD0029I 07:32:08.400 User administration called with function >> Set

Subtask RDY<<

Flag is : 40

1... .... called from holder

task




A108E670 00000000 40404040 40404040 2108E5EC 00000000 40404040 40404040

40404040 40404040 * ..V..... *

2108E690 00000020 A108E5E8 40404040 0000145E 41C5C4C3 00000000 40404040

00000EA8 41C3C5C5 *..VY ...;.EDC.... ...y.CEE*

2108E6B0 00000040 00000000 40404040 40404040 40404040 40404040 40404040

00000000 00000000 *.... ........*

2108E6D0 00000060 00000000 00000010 2108A050 40404040 40404040 40404040

40404040 40404040 *...........& *

2108E6F0 00000080 40404040 40404040 40404040 40404040 40404040 40404040

00000000 00000000 * ........*


Page: 187

2108E710 000000A0 00000000 00000000 00000000 00000000 00000080 00000000

C4C47AC9 D7C3D6D5 *........................DD:IPCON*

2108E730 000000C0 C6C9C700 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *FIG.............................*

2108E750 000000E0 00000000 00000000 00000000 00000000 00000000 00000000

00000000 *............................. *



A108E670 00000000 E2D6C6C1 D9404040 E9E2D6C6 C1D94040 00000000 00000000

C1C4C3C4 00000000 *SOFAR ZSOFAR ........ADCD....*

2108E690 00000020 00000000 C0A80948 E3C1E4D9 C9E2D7E9 00000000 00000000

058D0000 00000000 *.....y..TAURISPZ................*

2108E6B0 00000040 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

2108E6D0 00000060 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

2108E6F0 00000080 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

2108E710 000000A0 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 *................................*

2108E730 000000C0 00000000 00000000 00000000 00000000 00000000 00000591

35F25234 0006F0F1 *.......................j.2....01*

2108E750 000000E0 F4F2F5C1 C0A80948 00600000 00000000 00000000 00000000

00000000 *425A.y...-................... *


TAU0142I 07:32:08.403 z/Server Subtask READY for client's



Environment

Function-Code : 01

Task-Area : 2108E0B4 Global


Page: 188


0000


00000000



Environment

Function-Code : 37



0 microseconds.


0000


00000000


0000


00000000

API0099I

========================================================================

Data received

========================================================================



2571C028 00000000 C5E7C5C3 40404040 F3080200 E3C5E2E3 D9E74040 E3C1E4E4

E2D94040 40404040 *EXEC 3...TESTRX TAUUSR *

2571C048 00000020 40404040 40404040 40404040 00000154 C5F6F2C4 C3C2F6F4

F4F4F5F9 F1F9C6F0 * ....E62DCB64445919F0*


Page: 189

2571C068 00000040 40404040 40404040 40404040 40404040 40404040 40404040

40404040 40404040 * *

2571C088 00000060 40404040

* . *



Environment

Function-Code : 36



0 microseconds.


0000


00000000


0000


00000000

API0099I

========================================================================

Data received

========================================================================



2571C028 00000000 C5E7C5C3 40404040 F3080200 E3C5E2E3 D9E74040 E3C1E4E4

E2D94040 40404040 *EXEC 3...TESTRX TAUUSR *

2571C048 00000020 40404040 40404040 40404040 00000154 C5F6F2C4 C3C2F6F4

F4F4F5F9 F1F9C6F0 * ....E62DCB64445919F0*


Page: 190

2571C068 00000040 40404040 40404040 40404040 40404040 40404040 40404040

40404040 40404040 * *

2571C088 00000060 40404040 4CE3E2D6 E2C3C8C5 C46E4040 40404040 40404040

40404040 40404040 * <TSOSCHED> *

2571C0A8 00000080 40404040 40404040 40404040 40404040 40404040 40404040

40404040 40404040 * *

2571C0C8 000000A0 40404040 40404040 40404040 40404040 40404040 4040404C

D9D6E4E3 C5D4E2C7 * <ROUTEMSG*

2571C0E8 000000C0 40C3D4C4 7E7FC5E7 C5C37F40 D7C7D47E 7FE3C5E2 E3D9E77F

40D7D6D9 E37E7FF1 * CMD="EXEC" PGM="TESTRX" PORT="1*

2571C108 000000E0 F4F2F57F 40E7D4D3 7E7FD57F 6E4C61D9 D6E4E3C5 D4E2C76E

40404040 40404040 *425" XML="N"></ROUTEMSG> *

2571C128 00000100 40404040 4C61E3E2 D6E2C3C8 C5C46E40 40404040 40404040

40404040 40404040 * </TSOSCHED> *

2571C148 00000120 40404040 40404040 40404040 40404040 40404040 40404040

40404040 40404040 * *

2571C168 00000140 40404040 40404040 40404040 40404040 40404040 *

. *


TAU0059I 07:34:36.197 TESTRX endet with RC 00000000


Environment

Function-Code : 2A


API0099I

========================================================================

Data written

========================================================================




Page: 191

2611D028 00000000 0000002C D985A297 9695A285 40869996 9440E3C5 E2E3D9E7

40F540E2 859740F2 *....Response from TESTRX 5 Sep 2*

2611D048 00000020 F0F1F240 F0F77AF3 F47AF3F6

*012 07:34:36. *


0000

API0065I 07:34:36.197 After Call WRITE RC : 0000002C ERRNO :

00000000



Environment

Function-Code : 02



0000


00000000


TAU0053I 07:38:21.128 Shutdown Subtask

XML0010I 07:38:21.128 XML-Interface called with function Term

TAU0015I 07:38:21.131 Before Call GLX1TRM

TAU0065I 07:38:21.131 After Call GLX1TRM RC : 00000000 ERRNO :

00000000


00000000

8.2 Scenario 2 - Invoking commands

This scenario submits a job and fetches job information.


Page: 192

In this case, the issued commands (SUBMIT and JSTATUS) are issued directly from the invoked

XML. Because the invocation procedure is the same as that for Scenario 1 (Dataspace, Logon,

FullConv) it is not discussed further; only the invocation XML and the FullConv output are shown.


<TSOSCHED>

<SUBMIT MEMBER="ABR14">SOFAR.JCL</SUBMIT>

<JSTATUS JOBNAME="SOFAR*"></JSTATUS>

</TSOSCHED>

8.2.2 FullConv output

Answer from Server for Message 1 is 5.800 Bytes long.

===================================================================

00000000 000016A8 4CD1C5E2 C9D5C6D6 40D1C5E2 *...y<JESINFO JES*

00000010 7E7FD1C5 E2F27F6E 4CD1D6C2 6E4CD5C1 *="JES2"><JOB><NA*

00000020 D4C56EE2 D6C6C1D9 F9F9404C 61D5C1D4 *ME>SOFAR99 </NAM*

00000030 C56E4CC9 C46ED1D6 C2F0F5F2 F6F04C61 *E><ID>JOB05260</*

00000040 C9C46E4C D6E6D5C5 D96EE2D6 C6C1D940 *ID><OWNER>SOFAR *

00000050 40404C61 D6E6D5C5 D96E4CE2 E8E26E40 * </OWNER><SYS> *

00000060 40404040 4040404C 61E2E8E2 6E4CD7C8 * </SYS><PH*

00000070 C1E2C56E F1F44C61 D7C8C1E2 C56E4CE3 *ASE>14</PHASE><T*

00000080 E8D76EC2 81A38388 40919682 40404040 *YP>Batch job *

00000090 40404040 4040404C 61E3E8D7 6E4CC3D3 * </TYP><CL*

000000A0 C1E2E26E C1404040 40404040 4C61C3D3 *ASS>A </CL*

000000B0 C1E2E26E 4CD7D9C9 D66EF14C 61D7D9C9 *ASS><PRIO>1</PRI*

000000C0 D66E4CD7 D6E26EF1 F5F14C61 D7D6E26E *O><POS>151</POS>*


Page: 193

000000D0 4CC3C3C9 D5C6D66E D1D6C240 C5D5C4C5 *<CCINFO>JOB ENDE*

000000E0 C440D5D6 D9D4C1D3 D3E84040 4C61C3C3 *D NORMALLY </CC*

000000F0 C9D5C6D6 6E4CC3C3 6EF04C61 C3C36E4C *INFO><CC>0</CC><*

00000100 E2D6E4E3 6E4C61E2 D6E4E36E 4C61D1D6 *SOUT></SOUT></JO*

00000110 C26E4CD1 D6C26E4C D5C1D4C5 6EE2D6C6 *B><JOB><NAME>SOF*

00000120 C1D94040 404C61D5 C1D4C56E 4CC9C46E *AR </NAME><ID>*

00000130 E3E2E4F0 F5F2F2F5 4C61C9C4 6E4CD6E6 *TSU05225</ID><OW*

00000140 D5C5D96E E2D6C6C1 D9404040 4C61D6E6 *NER>SOFAR </OW*

00000150 D5C5D96E 4CE2E8E2 6E404040 40404040 *NER><SYS> *

00000160 404C61E2 E8E26E4C D7C8C1E2 C56EF1F4 * </SYS><PHASE>14*

00000170 4C61D7C8 C1E2C56E 4CE3E8D7 6EE38994 *</PHASE><TYP>Tim*

00000180 8540A288 81998995 8740A4A2 85994040 *e sharing user *

00000190 404C61E3 E8D76E4C C3D3C1E2 E26EE3E2 * </TYP><CLASS>TS*

000001A0 E4404040 40404C61 C3D3C1E2 E26E4CD7 *U </CLASS><P*

000001B0 D9C9D66E F14C61D7 D9C9D66E 4CD7D6E2 *RIO>1</PRIO><POS*

000001C0 6EF1F3F7 4C61D7D6 E26E4CC3 C3C9D5C6 *>137</POS><CCINF*

000001D0 D66ED1D6 C240C1C2 C5D5C4C5 C4404040 *O>JOB ABENDED *

000001E0 40404040 40404C61 C3C3C9D5 C6D66E4C * </CCINFO><*

000001F0 C3C36EE2 F6F2F24C 61C3C36E 4CE2D6E4 *CC>S622</CC><SOU*

.Note: The output shown is truncated.

8.3 Scenario 3 - Simulating an error

This scenario shows how you can use the message driver to simulate an error; in particular, the

XML0003E error:

XML0003E [001] Attribute value [002] with length [003] is too long for attribute [004]


Page: 194

You can do this by specifying a 9-character member name (the maximum permitted member name is

8 characters).


<TSOSCHED>

-- Simulate error comment

<GETDATA MEMBER="A12345678">SOFAR.JCL</GETDATA>

</TSOSCHED>

The invocation XML also shows how you can specify a comment (introduced with "--").



===================================================================

00000000 000000C5 4CD4E2C7 40C6C1C3 C9C47E7F *...E<MSG FACID="*

00000010 E7D4D37F 40D4E2C7 D5D67E7F F0F0F0F3 *XML" MSGNO="0003*

00000020 7F40E2C5 E5C5D9C9 E3E87E7F C57F6E40 *" SEVERITY="E"> *

00000030 F0F67AF5 F47AF3F7 4BF3F6F0 40C1A3A3 *06:54:37.360 Att*

00000040 998982A4 A38560E5 8193A485 40C1F1F2 *ribute-Value A12*

00000050 F3F4F5F6 F7F840A6 89A38840 D3859587 *345678 with Leng*

00000060 A3884040 40404040 40404040 4040F940 *th 9 *

00000070 40404040 40404040 40404040 4089A240 * is *

00000080 A3964093 96958740 86969940 C1A3A399 *to long for Attr*

00000090 8982A4A3 8540D4C5 D4C2C5D9 40404040 *ibute MEMBER *

000000A0 40404040 40404040 40404040 40404040 * *


Page: 195

000000B0 40404040 40404040 40404040 4040404C * <*

000000C0 61D4E2C7 6E */MSG> *

Note that the error message is not returned directly, but rather as a <MSG> XML element:

<MSG FACID="XML" MSGNO="0003" SEVERITY="E"> 06:54:37.360 Attribute-Value

A12345678 with Length 9 is to long for Attribute MEMBER<MSG>

Message number = <FACID><MSGNO><SEVERITY> = XML0003E

[0001] = 06:54:37.360

[0002] = A12345678

[0003] = 9

[0004] = MEMBER

8.4 Scenario 4 - Forcing an abend (abnormal end)

This scenario shows how you can use the message driver to force an abend. Use the Language

Environment CEE3DMP function to produce a dump (DD: ZCOMDUMP).


<TSOSCHED>

<ABEND/>

</TSOSCHED>



===================================================================

00000000 0000015A 4CD4E2C7 40C6C1C3 C9C47E7F *...!<MSG FACID="*

00000010 D9C5C37F 40D4E2C7 D5D67E7F F0F0F0F3 *REC" MSGNO="0003*


Page: 196

00000020 7F40E2C5 E5C5D9C9 E3E87E7F C57F6E40 *" SEVERITY="E"> *

00000030 F0F87AF2 F07AF5F5 4BF5F9F1 40C59999 *08:20:55.591 Err*

00000040 96994089 9540D787 9440E3C1 E4D9C9D7 *or in Pgm TAURIP*

00000050 F7F84081 A340D686 86A285A3 40F0F0F0 *78 at Offset 000*

00000060 F0F1F0C6 F8404040 40404040 40404040 *010F8 *

00000070 404040D6 99898789 95819340 D485A2A2 * Original Mess*

00000080 81878540 A681A240 7A40C3C5 C5F3F2F0 *age was : CEE320*

00000090 F1E240E3 888540A2 A8A2A385 94408485 *1S The system de*

000000A0 A38583A3 85844081 95409697 859981A3 *tected an operat*

000000B0 89969540 85A78385 97A38996 95404DE2 *ion exception (S*

000000C0 A8A2A385 9440C396 94979385 A3899695 *ystem Completion*

000000D0 40C39684 857EF0C3 F15D4B40 40404040 * Code=0C1). *

000000E0 40404040 40404040 40404040 40404040 * *

000000F0 40404040 40404040 40404040 40404040 * *

00000100 40404040 40404040 40404040 40404040 * *

00000110 40404040 40404040 40404040 40404040 * *

00000120 40404040 40404040 40404040 40404040 * *

00000130 40404040 40404040 40404040 40404040 * *

00000140 40404040 40404040 40404040 40404040 * *

00000150 40404040 4C61D4E2 C76E * </MSG> *


Page: 197

9 Appendix 3 - Debugging scenarios

Although the range of possible error situations is large, there are some general techniques that you

can use for debugging. They are described in this section, using actual scenarios.

9.1 Scenario 1 - Error returned by an invoked service

Internally, z/Server uses many z/OS services; for example, IEFSSREQ and DYNALLOC. Such services

return error codes and often reason codes in error situations. In such situations, z/Server generates

its own error messages that include the return code (and reason code) passed back by the invoked

service. To clarify the error situation, consult the message codes for the associated service, using the

information detailed in the bibliography.

This scenario describes troubleshooting associated with the JES0003E error message. Note the

timestamps of the two error messages (REC0001E and JES0003E); the REC0001E message was

issued after the JES0003E message and so is a secondary error. This means you should investigate

the JES0003E first.


CIB-Flag-5 : 02

CIB-Flag-6 : 25

Message from Server : SVMX1SS1 DDName : MAINTASK

JES0003E 20:04:53.823 SSI call for function code 0050 failed with RC

00000000

SSOBRETN is: 00000008

Reason is: 2C

Message from Server : SVMX1SS1 DDName : T0000001

9.1.1 JES0003E message investigation

Detailed explanations of the JES facility messages are described for the IEFSSREQ in the "MVS Using

the Subsystem Interface" manual, listed in the bibliography.

Function code 0050 Extended Status Function Call

RC 00000000 IEFSSREQ call successful

SSOBRETN 00000008 This indicates a logic error with the specific error in the reason field

Reason 2C The jobname is invalid

Solution: Consult the logs to determine the jobname. If this information is not available because the

trace level is too low, increase the trace level (IPTRACE = 5) and try to recreate the problem.

callto:0050

callto:00000000

callto:00000008

callto:0050

callto:00000000

callto:00000008


Page: 198

9.1.2 REC0001E message investigation

In this case, it is a secondary message and does not need to be investigated further.

The set CIB flags have the following significance.

CIB Flag 5: Condition signaled

CIB Flag 6: Resume allowed, enable only pass, all members informed of condition.

9.2 Scenario 2 - Parsing error

The XML0001E error message is issued by the z/OS XML System Service. In particular, the

returned GXL1PRS placeholder identifies the issuing component. The return code (00000008)

and the reason code (00001300) displayed identify the cause z/OS XML System Services User's

Guide and Reference. (1300 XRSN_BUFFER_INBUF_SMALL The input buffer size is too

small.).

XML0001E 10:48:55.647 XML-Call to GXL1PRS ended with RC: 00000008 and Reason 00001300

Solution: Increase the XML buffer size (configuration PIMASIZE parameter).

9.3 Scenario 3 - Catalog error

The CSI0051E error message is issued by the IGGCSI00 function. For this message, the actual

reason code is the low-order 8 bits, namely, X'7A' (= decimal 122). The message IDC3009I provides

the explanation for this reason code. In this case, "The master catalog connector record was not

found for the named catalog".

CSI0001E 14:21:26.887 Error during call of IGGCSI00

Return code is: 00000004 hex

Reason code is: C6E21E7A hex

Solution: This solution is taken verbatim from the MVS System Messages Volume 6 (GOS - IEA)

manual: "Enter the access method services LISTCAT command to display the entries in the master

catalog. If the user catalog is not listed, enter the access method services IMPORT CONNECT

command to connect the catalog. If the user catalog data set name is listed, ensure that the entry is

for a user catalog."

callto:00000008

callto:00000008

callto:00000008

callto:00001300


Page: 199

9.4 Scenario 4 - RACF validation error

The SLR0071E error message is issued by the z/Server TSO/E function when the RACF security

facility failed the userid validation request. The following error trace messages illustrate three typical

error situations:

SLR0071E 14:40:21.543 Verify for Userid SOFARX not successful. Reason

00000004

SLR0071E 09:29:54.069 Verify for Userid SOFJK not successful. Reason

00000008

SLR0071E 14:11:37.043 Verify for Userid SOFBN not successful. Reason

0000000C

Solution: The three verify requests failed for the following reasons:

SOFARX is not defined to RACF (reason code 4)

The password entered for SOFJK is not authorized (that is, was incorrect) (reason code 8)

The password entered for SOFBN has expired (reason code 12)

Documents

z/Server Messages and Diagnostics · Errors that indicate an internal z/Server error, such as API0007E (error during call to ... 13 ... API0065I [001] After call [002] RC: [003] ERRNO: