Havmsa 10

IBM Data Virtualization Manager for z/OS
1.1
Messages and Codes
IBM
GC27-9136-01

Note
Before using this information and the product it supports, read the information in “Product legal
notices” on page 283.
This edition applies to Version 13 Release 1 of IBM Data Virtualization Manager for z/OS and to all subsequent releases
and modifications until otherwise indicated in new editions.
Last updated: 2023-03-30
© Copyright International Business Machines Corporation 2017, 2021.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
© Rocket Software, Inc. 2017, 2021.
Contents
About this information........................................................................................... v
How to send your comments to IBM......................................................................vii

If you have a technical problem................................................................................................................. vii
Chapter 1. Messages and codes..............................................................................1

Viewing details about an error message..................................................................................................... 3
Sorting an error message.............................................................................................................................5
Changing the severity of an error message................................................................................................. 5
Data Virtualization Manager server reason codes.......................................................................................6
Chapter 2. z/OS Connect interface codes............................................................273
Accessibility features........................................................................................ 281
Product legal notices......................................................................................... 283
iii
iv
About this information
This information supports IBM Data Virtualization Manager for z/OS (5698-DVM) and contains information
about the messages and codes issued by the product.
Purpose of this information

This document provides information about the messages and codes issued by Data Virtualization
Manager.
Who should read this information

This information is intended for application developers and system programmers.
© Copyright IBM Corp. 2017, 2021 v

vi IBM Data Virtualization Manager for z/OS: Data Virtualization Manager Messages and Codes
How to send your comments to IBM
We appreciate your input on this documentation. Please provide us with any feedback that you have,
including comments on the clarity, accuracy, or completeness of the information.
Important: If your comment regards a technical problem, see instead “If you have a technical problem”
on page vii.
Send an email to [email protected].
Include the following information:
• Your name and address
• Your email address
• Your phone or fax number
• The publication title and order number:
IBM Data Virtualization Manager for z/OS Messages and Codes
GC27-9136-00
• The topic and page number or URL of the specific information to which your comment relates
• The text of your comment.
When you send comments to IBM®, you grant IBM a nonexclusive right to use or distribute the comments
in any way appropriate without incurring any obligation to you.
IBM or any other organizations use the personal information that you supply to contact you only about the
issues that you submit.
If you have a technical problem

If you have a technical problem or question, do not use the feedback methods that are listed for sending
comments. Instead, take one or more of the following actions:
• Visit the IBM Support Portal (support.ibm.com).
• Contact your IBM service representative.
• Call IBM technical support.
© Copyright IBM Corp. 2017, 2021 vii

viii IBM Data Virtualization Manager for z/OS: Data Virtualization Manager Messages and Codes
Chapter 1. Messages and codes
These topics contain information about the messages and codes that the Data Virtualization Manager
server issues.
Types of messages
The Data Virtualization Manager server produces many useful messages during the course of its
operation. The type of message produced depends on which component is issuing the message. The
types of messages that Data Virtualization Manager issues are as follows:
ISPF
The ISPF/xDy application is the only component of the Data Virtualization Manager server that
produces ISPF messages. ISPF messages appear in the upper right hand corner of a display. These
messages are not documented in this manual. If you require additional information on an ISPF
message, use PF1 to display the long version of the message.
WTO
The main address space of the Data Virtualization Manager server produces Write-To-Operator
messages. These messages appear on the system console and in the system log. Most of the
messages produced by the Data Virtualization Manager server fall into this category.
WTP
The ISPF/xDy application and the Data Virtualization Manager DSN and Data Virtualization Manager
CAF components produce Write-To-Programmer messages. These messages appear on the user's
TSO terminal in line mode. Both the WTO and WTP type messages are included in this documentation.
Format
The Data Virtualization Manager server messages have a format that is consistent with the Data
Virtualization Manager subsystem ID format, xVZy, where x can be any alphabetic letter, and y can be
any alphanumeric character (A-Z and 0-9). The following example shows the standard makeup of a Data
Virtualization Manager message:
xDynnnns text
Where:
• x: Indicates the first letter of the Data Virtualization Manager subsystem ID.
• D: Indicates the product code.
• y: Indicates the last (fourth) alphanumeric character of the Data Virtualization Manager subsystem ID.
• nnnn: Specifies the message serial number.
• s: Indicates severity code of the message. The following values are possible:
– I: Informational message. No action required.
– W: Warning message. Processing continues, but some assumptions (perhaps erroneous) are made.
– E: Error message. Some product functionality is lost.
– S: Severe error message. The functionality of a product sub-component is lost.
– H: Hardcopy messages.
– R: Reply (WTOR) messages.
– T: Trace messages. Trace messages also appear in the Trace Browse log.
– U: Very severe error, indicating Data Virtualization Manager is probably not functioning correctly any
more.
– O: Error is related to a TSO SERVER associated with Data Virtualization Manager Web Server.
© Copyright IBM Corp. 2017, 2021 1

– N: Message is discarded
• text: The text of the message. The message can contain fixed and variable information. Fixed
information is shown in all uppercase letters. Variable information is shown in all lowercase letters.
Message variable data

Many messages in this manual contain variable information. There are two types of variable information:
• Built-in variable data
• Local variable information
Built-in variable data
Built-in variable data is drawn from information that is always available to messages. The names and
definitions of these variables are as follows:
• ad: The address from which OPSNMG (the message module) was called. The following format is used:
CSECTNAME+OFFSET
This is equivalent to cs+of, as described below:

– cs: The CSECT name of the module that called OPSNMG.
– d1: The date, in yy/mm/dd format.
– d2: The date in month, day, year format.
– jb: Jobname of the caller.
– js: The primary Job Entry Subsystem (JES).
– of: The offset within the calling module where OPSNMG was called.
– pd: The product name.
– ss: The subsystem name.
– t2: The time, in hh.mm.ss format.
By default, all numbered messages are in upper and lower case. However, you can set the following
started task parameter to convert numbered messages to upper case:
MODIFY PARM NAME(CONMSGFORMAT ) VALUE(X)
where CONMSGFORMAT specifies whether or not all Latin letters in messages will be converted to upper
case prior to routing the message to its final output destination. Setting this parameter to UPPER is
recommended when Data Virtualization Manager executes on certain non US-supported operating system
utilizing a console code page in which the lower-case Latin letters display as Katakana characters (for
example, IBM EBCDIC SBCS code pages 290 and 1030).
Note: The setting of this parameter affects all numbered messages produced by the server; even when
the message text is being routed to a destination other than the console or hardcopy log.
Numbered product messages are those which have an 8-character prefix such as xDy3253I. Most often,
numbered messages are routed to a console, but internal shunting may cause these messages, under
various conditions to be written to trace browse or some other output destination.
The values for this parameter are:
• U for Upper Case
• A for As Is
The default is A for As Is.
Local variable information
Local variable information is specific to a particular message. The definitions for local variables may be
found in the message entries themselves.
2 IBM Data Virtualization Manager for z/OS: Data Virtualization Manager Messages and Codes
Viewing details about an error message
You can view information such as severity, explanation, and action item about an error message.
Procedure
To display more information about an error message:
1. From the IBM Data Virtualization Manager for z/OS's Primary Option Menu, enter the option C AVZ
Admin.. and press ENTER
2. From the Server Management Menu, select 2 AVZ Parms and press ENTER.
3. Scroll down and find the parameter group PRODMESSAGES.
4. Type D to display the information about the group.
The information such as description, severity/parameter value of the error messages under the group
is displayed.
. . . . . . . . . . . . . . . . . . . . . . . . . .
------------------------------- Parameters --------------- Scr 1 Row 1 of 1777
LCs: D Display E Edit F Format P Print CB S Show CB
Parameter Parameter
Description Value
SEVERITY OF MESSAGE ID <SSID>0001 'U'
SEVERITY OF MESSAGE ID <SSID>0002 'S'
SEVERITY OF MESSAGE ID <SSID>0010 'H'
SEVERITY OF MESSAGE ID <SSID>0011 'W'
Command ===> Scroll ===> PAGE
• Type D next to the corresponding error message to view information such as description and action
item about the message: . In the following example, information about the error message 0194 is
displayed.
********************************* Top of Data *********************************

MESSAGE <SSID>0194W, SEF start-up procedure %1 ended with special RC (8
) - auto-enable of SEF rules bypassed - no SEF rule are enab
led
EXPLAIN The xxxxINEF start-up procedure ended with RC=8, indicating

rule enablement should be bypassed. The server will bypass
rule enablement. You can enable rules later, manually, but
until you do so, no event related processing is performed
by the SEF facility.
ACTION Determine if the warning is anticipated. If not, correct

the xxxxINEF start-up procedure and restart the server.
******************************** Bottom of Data *******************************
• Type F next to an error message to view the configured values of the message. In the following
example, information about the error message 0193 is given below.
Chapter 1. Messages and codes 3

BROWSE Parameter Information Line 0000000000 Col 001 066
********************************* Top of Data **********************************
Parameter Name <SSID>0193
Description Text SEVERITY OF MESSAGE ID <SSID>0193
Group Name PRODMESSAGES
Updatable Parameter Y
Read-Only Parameter N
Maximum Value 0
Minimum Value 0
Parameter Counter 0
Last Update Timestamp
Set During Initialization 0
Changed During Initialization 0
Set After Initialization 0
Changed After Initialization 0
Last Update Userid
Parameter Value 'W'
******************************** Bottom of Data ********************************
The following table Table 1 on page 4 describes the description of the message.
Table 1. Error Message Description

Column name Sort name Column definition
Description DESCRIPTION 1 to 50-character parameter
description
Value VALUE Parameter value
Name NAME 1 to 20-character parameter
name
Updatable UPDATABLE Value can be changed
Output only ONLY Parameter cannot be set
Minimum value MINIMUM Minimum value for numeric
parameters
Maximum value MAXIMUM Maximum value for numeric
parameters
-Init-- Set SETINIT Number of times set during
initialization
-Init-- Chg CHANGEINIT Number of times value changed
during init
-After- Set SETAFTER Number of times set after
initialization
-After- Chg CHANGEAFTER Number of times value changed
after init.
Timestamp CHANGED Last time the parameter was
changed.
Last Userid USERID Last userid that changed the
parameter.
Related concepts
Messages and codes
Sorting an error message
You can sort an error message based on the description and the parameter value in an ascending order or
a descending order.
Procedure
To sort:
1. From the IBM Data Virtualization Manager for z/OS's Primary Option Menu, select the option C AVZ
Admin. and press ENTER.
. . . . . . . . . . . . . . . . . . . . . . . . . .
Parameter Parameter
Description Value
5. To sort:
• Based on the description: type sort description desc or sort description asc to sort in a descending
order or in an ascending order, respectively.
• Based on the severity value or the parameter value: type sort value desc or sort value asc to sort in
a descending order or in an ascending order, respectively.
Changing the severity of an error message

You can change the severity of an error message by performing the following task.
Procedure
1. From the IBM Data Virtualization Manager for z/OS's Primary Option Menu, select the option C AVZ
Admin.. and press ENTER.

. . . . . . . . . . . . . . . . . . . . . . . . . .
Parameter Parameter
Description Value
5. Overwrite the parameter value and press ENTER.
Data Virtualization Manager server reason codes

The Data Virtualization Manager server produces reason codes that are used for troubleshooting TCP/IP
and DRDA related issues.
Reason codes appear in system messages and driver messages. For example, the following message
includes a reason code, which, in this case, indicates that the password is missing:
Unable to connect to DB subsystem DBAA; Return code 8, Reason code 00BAD044
The following table lists the available reason codes.
Reason codes Short description Detailed description

0X00BAD002 No query to continue Indicates an internal error has occurred where an internal
continue query command has been executed and there is not
any query currently open.
Processing: Fails and request is terminated
Action: See Server Trace for additional details of error.
0X00BAD003 Network buffer underflow Indicates that a DRDA protocol error occurred during the
request processing.
Processing: Fails and request is terminated
0X00BAD004 String conversion During Code Page Conversion from a source CCSID to a target
truncation CCSID, a string conversion error has occurred which caused a
truncation of data.
Processing: Current request may or may not continue
character substitution CCSID, a string conversion error has occurred where a character
substitution occurs.
0X00BAD006 String conversion error During Code Page Conversion from a source CCSID to a target
CCSID, a string conversion error has occurred where a character
substitution occurs.
Action: See Server Trace for additional details of error. Server
xVZyIN00 may require DEFINE CONV entries to provide Source
CCSID to Target CCSID conversions
0X00BAD007 String conversion table During Code Page Conversion from a source CCSID to a target
corrupt CCSID, the conversion table is not usable.
Processing: Current request is terminated
unknown code page CCSID, either the source or target CCSID is not valid.
0X00BAD009 Connection dead During TCP/IP processing, the TCP/IP connection has failed.
0X00BAD00A Unknown Datatype During processing of a SQL request, the DRDA protocol has
returned a column or result set data type that is not known to
the DRDA VRF code base.
0X00BAD00B Abnormal end unit of work DRDA AS has returned a DRDA code point ABNUOWRM
condition occurred indicating an abnormal unit of work was encountered by the
DB Server. For example, the reply message ABNUOWRM may
be chained to an SQLCARD data object that carries the name
of a resource involved in a deadlock that generated a relational
database rollback operation.

0X00BAD00C Permanent Agent Error DRDA AS has returned a DRDA code point which indicates the
Server is failing the request. The Server Trace will normally
report DRDA Server info in the form of Server Diagnostic
messages as the DB Server provides. One example would be
calling a Stored Procedure and the data passed to the SPC
generated an ABEND via Data Execption. Threads may also
generate a Permanent Agent Error when the DRDA VRF has
a connection open in an in-doubt state and z/OS Db2 has
terminated the thread.
Processing: Current request is terminated.
Action: See Server Trace for additional details of error. For
Terminated Threads, a new connection should be established
and commit / rollback processing should be used to insure the
connection does not enter an in-doubt state for Idle Time set in
Db2. For SPC Data Execptions ensure the data passed to Stored
Procedures is valid for the data type.
0X00BAD00D Not Authorized To Use DRDA AS has returned a DRDA code point CMDATHRM
Command indicating the currently authenticated USERID is not authorized
to issue the current command. The error may occur on Open
Query or other commands.
0X00BAD00E Command Check Error DRDA AS has returned a DRDA code point CMDCHKRM. Reply
Message indicates that the requested command encountered
an unarchitected condition for which there is no architected
message.
0X00BAD00F Command Not Supported DRDA AS has returned a DRDA code point CMDNSPRM.
Reply Message indicates that the specified command is not
recognized or not supported for the specified target object. This
reply message can be returned only in accordance with the
architected rules for DDM sub-setting.
0X00BAD010 Manager Level Conflict DRDA AS has returned a DRDA code point SQLAM or MGRLVLRM
that is not supported by the DRDA VRF code base. By default
the DRDA VRF requests SQLAM level 8 and the target DRDA AR
should indicate if the DRDA AS supports the requested SQLAM
or drops down to a supported SQLAM value. This should not
occur unless there is a mismatch in the DRDA AS and the DRDA
AR (VRF).
Processing: Current request is terminated and normally will
only occur during the initial DRDA connection.
Action: See Server Trace for additional details of error. If the
SQLAM is used on the DEFINE DATABASE be sure to use a value
supported by the DRDA AS.
0X00BAD011 Manager Dependency DRDA AS has returned a DRDA code point MGRDEPRM. Reply
Error Message indicates that a request has been made to use a
manager, but the requested manager requires specific support
from some other manager that is not present.
Processing: Current request is terminated and normally will
only occur during the initial DRDA connection.
0X00BAD012 Unexpected Server Reply DRDA AS has returned a DRDA code point PRCCNVRM.
(%s (PRCCNVCD)) Reply Message indicates that a conversational protocol error
occurred. The response displayed is the DRDA AS Server reply
code that is not expected.
0X00BAD013 Parameter Not Supported DRDA AS has returned a DRDA code point PRMNSPRM.
(%s) Reply Message indicates that the specified parameter is not
recognized or not supported for the specified command. The
response displayed is the DRDA AS Server parameter code that
is not expected/supported.
0X00BAD014 Resource Limits DRDA AS has returned a DRDA code point RSCLMTRM. Reply
Reached(%s). Diagnostic Message indicates that the requested command could not be
Info: %s completed due to insufficient target server resources. Examples
of resource limitations are as follows:
• The target agent has insufficient memory to keep track of
DCLFIL collections.
• The lock manager cannot obtain another lock.
• The communications manager send or receive buffer
overflowed.
• The target server lacks the memory or storage resource to
create the instance of the manager requested. For example,
an ACCRDB command could not create a target SQLAM
manager because of the target server resource limitations.
The message provide details on the limit reached followed by
some Diagnostic information.

0X00BAD015 Data Stream Syntax Error DRDA AS has returned a DRDA code point SYNTAXRM. Reply
(%8.8x) Message indicates that the data sent to the target agent
does not structurally conform to the requirements of the DDM
architecture. The target agent terminated parsing of the DSS
when the condition SYNERRCD specified was detected. The
DRDA AR (VDF) code base will report the syntax error in the
message.
Action: See Server Trace for additional details of error. Contact
software supplier with full trace of the error along with version
of the Db2 and any SQL that is processed. Full DRDA READ/
WRITE tracing will provide best diagnostic information.
0X00BAD017 Incorrect object length DRDA AS has returned a DRDA code point SYNTAXRM. Reply
Message indicates that the data sent to the target agent
error indicates a length error for an object.
0X00BAD018 Incorrect large object DRDA AS has returned a DRDA code point SYNTAXRM. Reply
length Message indicates that the data sent to the target agent
error indicates a length error for an large object.
0X00BAD019 Object index not DRDA AS has returned a DRDA code point SYNTAXRM. Reply
supported Message indicates that the data sent to the target agent
error indicates an index value for an object is invalid.
0X00BAD01A Required object not found DRDA AS has returned a DRDA code point SYNTAXRM. Reply
error indicates a required object was not provided in the
request.
0X00BAD01B Too many command DRDA AS has returned a DRDA code point SYNTAXRM. Reply
objects Message indicates that the data sent to the target agent
error indicates that more objects were provided in the request
than expected.
0X00BAD01C Mutually exclusive objects DRDA AS has returned a DRDA code point SYNTAXRM. Reply
present Message indicates that the data sent to the target agent
error indicates that objects were provided in the request that
mutually exclusive.
0X00BAD01D Too few command objects DRDA AS has returned a DRDA code point SYNTAXRM. Reply
error indicates that the objects were provided in the request
are less than the expected number.

0X00BAD01E Duplicate objects present DRDA AS has returned a DRDA code point SYNTAXRM. Reply
error indicates that the duplicate objects were provided in the
request.
0X00BAD01F Invalid request correlator DRDA AS has returned a DRDA code point SYNTAXRM. Reply
error indicates that the request correlator provided is not valid.
0X00BAD020 Required value not found DRDA AS has returned a DRDA code point SYNTAXRM. Reply
error indicates that a required value was not provided in the
request.
0X00BAD021 Reserved value not DRDA AS has returned a DRDA code point SYNTAXRM. Reply
allowed to be set Message indicates that the data sent to the target agent
error indicates that setting of a reserved value is not valid.
0X00BAD022 DSS continuation less DRDA AS has returned a DRDA code point SYNTAXRM. Reply
than two Message indicates that the data sent to the target agent
error indicates that the DRDA DSS continuation is not valid.
0X00BAD023 Objects not in required DRDA AS has returned a DRDA code point SYNTAXRM. Reply
order Message indicates that the data sent to the target agent
error indicates that the request objects are not provided in the
required order.
0X00BAD024 DSS chaining and DSSFMT DRDA AS has returned a DRDA code point SYNTAXRM. Reply
not correct Message indicates that the data sent to the target agent
error indicates that the DRDA DSS chaining is not valid.
0X00BAD025 Different request DRDA AS has returned a DRDA code point SYNTAXRM. Reply
correlators Message indicates that the data sent to the target agent
error indicates that the request correlator is not the expected
correlator.

0X00BAD026 Error continuation not DRDA AS has returned a DRDA code point SYNTAXRM. Reply
allowed for this command Message indicates that the data sent to the target agent
error indicates that the request has setup for continuation
which is not valid for the active command.
0X00BAD027 Mutually exclusive DRDA AS has returned a DRDA code point SYNTAXRM. Reply
parameter values Message indicates that the data sent to the target agent
specified does not structurally conform to the requirements of the DDM
error indicates that the request has sent Mutually exclusive
parameters.
0X00BAD028 Server cannot handle this DRDA AS has returned a DRDA code point SYNTAXRM. Reply
command Message indicates that the data sent to the target agent
does not structurally conform to the requirements of the
DDM architecture. The target agent terminated parsing of the
DSS when the condition SYNERRCD specified was detected.
The error indicates that the DRDA AS does not support the
requested command.
0X00BAD029 No detailed information DRDA AS has returned a DRDA code point SYNTAXRM. Reply
available Message indicates that the data sent to the target agent
error that the DRDA AR (VRF) code base does not have code
to display the SYNERRCD returned.
0X00BAD02A Target Not Supported DRDA AS has returned a DRDA code point TRGNSPRM. Reply
Message indicates that the object specified as a command
target parameter is not an object of a class that the target
server supports. This condition can arise when a target server
can address objects of classes that DDM or product extensions
to DDM cannot support. It can also arise for valid DDM classes
that the target server does not support. For example, the
TRGNSPRM is returned if the name of the object a FILNAM
(command target) parameter specifies is either not a file (for
instance, a program library) or is not of a DDM file class (for
instance, a file class the target system does not support).
0X00BAD02B Remote Database Not DRDA AS has returned a DRDA code point RDBNFNRM. Reply
Found: %s Message indicates that the target server cannot find the
specified relational database. The message provides the name
of the remote DB that could not be located on the Target DRDA
AS.
Action: Verify that the expected database exists on the DB
Server or that host IPADDR/DOMAIN and/or port used in the
DEFINE DATABASE is correct.
0X00BAD02D Failed to access database DRDA AS has returned a DRDA code point RDBNACRM.
%s Reply Message indicates that the access relational database
command (ACCRDB) was not issued prior to a command
requesting RDB services. The message provides the name of
the remote DB that failed to be accessed on the Target DRDA
AS.
0X00BAD02E Connection to application DRDA AS has returned a DRDA code point RDBAFLRM. Reply
server %s would exceed Message specifies that the relational database (RDB) failed
limit the attempted connection. The DRDA VRF code base returns
this error via the SQLCARD object that follows the RDBAFLRM
code point. The message will explain why the RDB failed the
connection.
Action: See Server Trace for additional details of error and the
SQLCODE following the error. Normally indicates the target DB
Server cannot accept any new connections.

0X00BAD02F Object not supported DRDA AS has returned a DRDA code point OBJNSPRM. Reply
Message indicates that the target server does not recognize
or support the object specified as data in an OBJDSS for
the command associated with the object. The OBJNSPRM is
also returned if an object is found in a valid collection in an
OBJDSS (such as the RECAL collection) that is not valid for that
collection.
0X00BAD030 Descriptor received does DRDA AS has returned a DRDA code point DTAMCHRM. Reply
not match associated data Message which indicates that:
• The descriptor received did not violate any Formatted Data
Object Content Architecture (FD:OCA) or (DRDA) rules and
was successfully assembled.
• The data received did not match the received descriptor. That
is, the amount of data received did not match the amount of
data expected.
0X00BAD031 Invalid data descriptor DRDA AS has returned a DRDA code point DSCINVRM. Reply
Message specifies that a target server manager was unable to
assemble a valid Formatted Data Object Content Architecture
(FD:OCA) descriptor for the data being sent. The DSCERRCD
DRDA code point specifies the reason for the error. This
reply message indicates that the FD:OCA descriptor is invalid
either because it violates FD:OCA rules or (DRDA) rules for
the construction of an FD:OCA descriptor. The DRDA code
point offsets for the parameters FDODSCOFF, FDOTRPOFF, and
FDOPRMOFF specify the descriptor components that are in
error.
0X00BAD032 Unhandled CodePoint: %s DRDA AS has returned a DRDA code point that is not know to
the DRDA VRF or is not expected at the DRDA protocol code
point currently active.
0X00BAD033 Codepoint too big DRDA AS has returned a DRDA code point that is larger than
the expected for the DRDA protocol code point currently being
processed.
0X00BAD037 SECMEC value not The authentication DRDA code point SECMEC that was returned
supported, check for or requested via the DEFINE DATABASE SECMEC(...) setting is
missing user/password not supported by either the DRDA AS or the DRDA AR code
base.
Action: See Server Trace for additional details of error. Select
a valid SECMEC setting for the DB Server or modify the DB
Server to accept the requested SECMEC value. Refer to the
documentation on the DB Server authentication methods.
0X00BAD038 DCE Informational Status The message indicates an error occurred while the DRDA AR
issued (VRF) and the DB Server were processing the authentication
request. DRDA AS has returned a DRDA code point SECCHKCD
which String codifies the security information and condition
for the SECCHKRM. The DRDA protocol documentation
provides details about the relationship between the SECCHKCD
parameter and the DRDA SVRCOD parameter in the SECCHKRM.
Action: See Server Trace for additional details of error as the
DRDA VRF code will display additional Server trace messages
during authentication errors. If the additional information does
not resolve the reason for the authentication error. Contact

0X00BAD039 DCE retryable error The message indicates an error occurred while the DRDA AR
(VRF) and the DB Server were processing the authentication
0X00BAD03A DCE non-retryable error The message indicates an error occurred while the DRDA AR
0X00BAD03B GSSAPI Informational The message indicates an error occurred while the DRDA AR
Status issued (VRF) and the DB Server were processing the authentication
0X00BAD03C GSSAPI retryable error The message indicates an error occurred while the DRDA AR
0X00BAD03D GSSAPI non-retryable The message indicates an error occurred while the DRDA AR
error (VRF) and the DB Server were processing the authentication
0X00BAD03E Local Security Service The message indicates an error occurred while the DRDA AR
Informational Status (VRF) and the DB Server were processing the authentication
issued request. DRDA AS has returned a DRDA code point SECCHKCD

0X00BAD03F Local Security Service The message indicates an error occurred while the DRDA AR
retryable error (VRF) and the DB Server were processing the authentication
0X00BAD041 SECTKN missing on The message indicates an error occurred while the DRDA AR
ACCSEC when required, or (VRF) and the DB Server were processing the authentication
it is invalid request. DRDA AS has returned a DRDA code point SECCHKCD
This message normally indicates that the encrypted token was
not found when expected or is invalid.
0X00BAD042 Password expired The message indicates an error occurred while the DRDA AR
This message indicates that the supplied password has expired.
during authentication errors. Correct the password expired
problem and retry the request. If correcting the password does
not resolve the authentication error. Contact software supplier
with full trace of the error along with version of the Db2 and
any SQL that is processed. Full DRDA READ/WRITE tracing will
provide best diagnostic information.
0X00BAD043 User / Password invalid The message indicates an error occurred while the DRDA AR
This message indicates that the supplied USERID or password
is invalid.
during authentication errors. Correct the USERID and or
password and retry the request. If correcting the request does
not resolve the authentication error. Contact software supplier
with full trace of the error along with version of the Db2 and
any SQL that is processed. Full DRDA READ/WRITE tracing will
provide best diagnostic information.
0X00BAD044 Password missing See Reason code: 0X00BAD043

0X00BAD045 Userid missing See Reason code: 0X00BAD043
0X00BAD046 User / Password invalid See Reason code: 0X00BAD043
0X00BAD047 Userid was revoked or is See Reason code: 0X00BAD043
invalid
0X00BAD048 New Password invalid
0X00BAD049 Access to Remote
Database %s failed.
Reason: %s
0X00BAD04A Commit or Rollback failed
0X00BAD04B Command cannot be DRDA AS has returned a DRDA code point PKGBPARM. Reply
completed. Bind process Message indicates that the command cannot be issued when
is active the relational database package binding process is active. The
active package binding process must complete before package
can be used for execution.
Action: See Server Trace for additional details of error. Make
sure package BIND process is complete before accessing the
DB Server.
0X00BAD04C Failed to begin the bind

process

0X00BAD04D Bind process is not active DRDA AS has returned a DRDA code point PKGBNARM. Reply
Message indicates that a BNDSQLSTT or ENDBND command
was issued when the package binding process was not active
for the specified package name.
0X00BAD053 No more available The error indicates an internal error occurred during the BIND
statements; need more of a package.
sections in package
0X00BAD055 Unknown FDOCA The descriptor received did not match the expected. Formatted
descriptor: %s Data Object Content Architecture (FD:OCA) or (DRDA) rules for
the expected descriptor.
0X00BAD059 Data length exceeds

maximum CLOB length for
database (%s)
0X00BAD05A Data length exceeds
maximum BLOB length for
database (%s)
0X00BAD05C Cursor identified in Fetch Any attempt was made to close a cursor, but the cursor
statement is not open specified is not currently being processed.
0X00BAD05F An invalid database Name

was specified
0X00BAD060 An invalid package Name DRDA AS has returned a DRDA code point VALNSPRM. Reply
was specified Message indicates that the parameter value specified is either
not recognized or not supported for the specified parameter.
The codepoint of the command parameter in error is returned
as a parameter in this message. Normally indicates an invalid
package name.
0X00BAD063 DRDA SQL Diagnostic

Record not NULL
0X00BAD064 Cancel Failed DRDA AS has returned a DRDA code point INTTKNRM. Reply
Message indicates the target SQLAM has determined that the
specified DRDA RDBINTTKN value is invalid because of one of
the following:
• The token value does not match the interrupt token value
returned to the requester on the DRDA ACCRDBRM.
• The requester is not authorized to interrupt the execution of a
DDM command.
0X00BAD067 Server does not support DRDA AS has returned a DRDA code point VALNSPRM. Reply
client's code page (IBM Message which indicates the target CCSID provided to the DB
cp-%d) Server is not supported.
a valid CCSID for the DEFINE DATABASE. If the CCSID is valid
or must be supported: Contact software supplier with full trace
of the error along with version of the Db2 and any SQL that
is processed. Full DRDA READ/WRITE tracing will provide best
diagnostic information.
0X00BAD068 Specified security DRDA AS has returned a DRDA code point SECMEC and
mechanism (%s) associated SRVCOD to indicate the selected DEFINE DATABASE
unsupported by server SECMEC(...) is not supported by the DB Server.
a supported SECMEC or modify the DB Server to support the
required SECMEC(...) if a valid SECMEC cannot be selected.
Contact software supplier with full trace of the error along with
version of the Db2 and any SQL that is processed. Full DRDA
READ/WRITE tracing will provide best diagnostic information.

0X00BAD069 The SNA protocol
is not supported.
Cancel functionality not
supported
0X00BAD06A Operation failed due to
asynchronous network
contention. Network
socket closed
0X00BAD06B CALL statement found in
explicit batch
0X00BAD06C AUTHORIZATION An attempt was made to generate or decode a Kerberos token
FAILURE: %s. REASON: that failed.
%s
Action: See Server Trace for additional details of error. Use
the Failure and Reason code to determine the Kerberos error.
Verify the Server USERID and the USERID in effect for the
connection has the RACF Kerberos segment active. Otherwise,
contact software supplier with full trace of the error along with
0X00BAD06D zEDC Requested and zEDC An attempt has been made to connect a DRDA DEFINE
is: ( %s ) (%s) DATABASE setup with a zEDC proxy and zEDC is not active for
the Server.
Action: See Server Trace for additional details of error. Ensure
zEDC is activated at Server Start-up and does not have any
errors. Otherwise, contact software supplier with full trace of
the error along with version of the Db2 and any SQL that is
processed. Full DRDA READ/WRITE tracing will provide best
diagnostic information.
0X00BAD06E %s - Access to Distributed This error is returned when Server is not authorized to access
is not authorized (%s) Distributed data sources. This message is deprecated for
current code base.
0X00BAD06F Authentication for request DRDA AS has returned a DRDA code point RDBATHRM. Reply
is not authorized to access Message specifies that the requester is not authorized to access
the specified relational the specified relational database.
database
Action: See Server Trace for additional details of error. Ensure
USERID is authorized to access the Database. Otherwise,
contact software supplier with full trace of the error along with
0X00BAD070 Package Isolation level is During package BIND the cursor isolation level was found to be
invalid invalid.
0X00C10205 RLI TRANSLATE function The requested function is not valid for DRDA connections.
unsupported for DRDA
of the Db2 and any SQL that is processed.
0X00C12201 IDENTIFY invalid in The requested function is not valid for DRDA connections which
already-connected state are in a connected state.
0X00C12202 CREATE THREAD invalid Cannot create a thread when thread is already active for the
with thread already open DRDA connection.
0X00C12203 TERMINATE THREAD Cannot terminate a thread when thread is not active for the
invalid, no active thread DRDA connection.
0X00C12204 Only an IDENTIFY request Only IDENTIFY may be issued when a connection does not
is valid without a prior exist.
connection
0X00C12205 SWITCH TO request for Cannot issue SWITCH to a DRDA SUBSYSTEM that is not already
unidentified subsystem defined.

0X00C12206 Wrong arg count for DRDA Internal call to DRDA RLI entry has incorrect parameter count.
RLI request
0X00C12217 CREATE THREAD Internal error occurred during CREATE THREAD processing.
invalid before SIGNON
completed
0X00C12221 SET_CLIENT_ID invalid Internal error occurred during CREATE THREAD processing.
before CREATE THREAD
0X00C19998 SET_CLIENT_ID WLM Internal setup processing for Work Load Management failed
setup processing failed during SET_CLIENT_ID process.
0X00C19999 DEFERRED WLM setup Internal setup processing for Work Load Management failed
processing for DRDA link during DEFERRED WLM process.
failed
0X0FF30011 DRDA RLI request failed, DRDA RLI processing failed due to the target Db2 being inactive.
target subsystem inactive
0X0FF30013 No authorization for The message indicates an error occurred while the DRDA AR
CL(DSNR) subsys.DIST (VRF) and the DB Server were processing the authentication
resource request. DRDA AS has returned a DRDA code point SECCHKCD
This message normally indicated the authentication is valid, but
the USERID is not allowed access.
0X0FF30049 DRDA RLI request failed, DRDA RLI processing failed due to the connection already being
LDU is already connected active.
0X0FF30093 TERMINATE THREAD/ Termination of Thread with open unit of work is not valid.
IDENTIFY invalid with
open unit-of-work
0X0FF3EEEE Connection setup for The connection processing for the DRDA LINK failed.
DRDA link failed
AVZ0001U desc GETMAIN failed - increase Explanation

memory size
This message indicates a problem with the parameter
string that was passed to the main started task entry
Explanation point. Execution is terminated.
Insufficient storage. The product was unable to obtain
enough storage to allocate the initial program stack. User response
Correct the error that is indicated in the error message,
User response and restart the product.
Check the abend code to determine if the region AVZ0003S CODES BEGINNING WITH var1,
size should be increased. Increase the region size if NOT var2 SHOULD NOT BE USED
necessary, and restart the product. TO SET THE %2 PARAMETER
AVZ0002S parmname IS errdesc - correction

Explanation Explanation
This message contains variables that are resolved at The product tried to initialize or re-initialize a system
run-time and emitted by the server as it processes. control block (the SSCT). The system control contained
a field with an invalid value. This error will cause
User response product initialization to terminate.
Review the messages just before and after this

User response
message to understand the context.
Check for other error messages were generated
AVZ0004S parmname IS errdesc along with the error message. If the combined
error messages are sufficient to explain the error,
Explanation take whatever corrective action is appropriate. If
the problem cannot be resolved, contact Software
Support.
string that was passed to the main started task entry
point. Execution is terminated. AVZ0008S Product cannot execute in batch,
execution terminating
User response
Explanation
Ensure that a parameter string is being passed (using
PARM=) in the started task JCL. The parameter string This message is issued if the product detects that it is
should contain at least "INIT,ssnx" where ssnx is the running in batch. The main product address space will
4 character subsystem name. Correct the error and terminate immediately.
restart the product.
AVZ0005S parmname val IS errdesc User response
The product cannot run as a batch job. The product
Explanation must execute as a started task. Install the product as a
started task, and restart the product.
string that was passed to the main started task entry AVZ0009S Execution DEQ failed - contact
point. Execution is terminated. systems programming
User response Explanation

Ensure that the execution option (the first parameter Some type of error occurred while the product
in PARM=) is INIT. This is the only valid value. Correct was releasing the execution enqueue. The execution
the error, and restart the product. enqueue is used to prevent more than one copy of
the product from using a single subsystem ID. Multiple
AVZ0006S Product not APF authorized,
copies of the product can execute concurrently so long
execution terminating
as each copy uses a different subsystem ID.
Explanation User response

This message is issued if the product detects that it is
Check the error messages associated with this
not APF authorized. The main product address space
problem. If possible, fix the problem identified by
will terminate immediately.
the error messages, and restart the product. If
User response Support.
Ensure that all of the STEPLIB data sets are APF AVZ0010H modname/funcode execution
authorized. Note that all of the data sets must be APF msgtext
authorized, not just the data set containing the product
load modules. Fix the STEPLIB data sets, and restart
Explanation
the product.
This message is used to trace product initialization. A
AVZ0007S subsys field IS errdesc
message is issued before and after the execution of
each initialization routine.
User response AVZ0015S %PX-js subsystem subsys waiting
for execution ENQ
There is no action for this message. This message is
only used for trace and debugging purposes.
Explanation
AVZ0011W STSI instruction failed with %1 -
feedback = %2 Each active copy of the product must use a different
subsystem ID. This restriction is enforced using the
product execution enqueue. The product execution
Explanation enqueue contains the current subsystem ID, so that
This message contains variables that are resolved at multiple copies of the product can execute if each
run-time and emitted by the server as it processes. copy uses a different subsystem ID. A new copy of the
subsystem (subsys) has been started and is attempting
to get the execution enqueue. The execution enqueue
User response for subsystem is already held by a copy of the product.
message to understand the context. User response
AVZ0012W CSRSI service returned RC=rcode Either cancel the newly started subsystem that is
for CPU H/W identification request waiting on the execution enqueue or stop the currently
- product validation may be active copy of the subsystem. Stopping the currently
affected. active copy of the subsystem will allow the new copy
of the subsystem to complete initialization and start
Explanation execution. The new copy of the subsystem may have
to be stopped using the ASID keyword of the CANCEL
None. command.
AVZ0016S Execution ENQ error - contact
User response systems programming
Contact Rocket Software Support.
AVZ0013S SSCT locate error - contact Explanation
systems programming Each active copy of the product must use a different
subsystem ID. This restriction is enforced using the
Explanation product execution enqueue. The product execution
enqueue contains the current subsystem ID, so that
The product tried to find the current subsystem ID in multiple copies of the product can execute if each
the subsystem control block chain. A loop was found in copy uses a different subsystem ID. The product tried
the subsystem control block chain. to obtain the execution enqueue. The ENQ macro
failed.
User response
This is a serious error that may cause other User response
components of the system to fail. If the system Check the error messages associated with this
is having other problems (such as loop errors), problem. There may be one or more ENQ/DEQ error
try to resolve the other problems before restarting messages referring to the current problem. If possible,
the product. If the product is the only component fix the problem identified by the error messages, and
experiencing any difficulty, contact Software Support. restart the product. If the problem cannot be resolved,
AVZ0014S var1: var2 var3 var4 var5 var6 var7 contact Software Support.
AVZ0017S var1 PARAMETER INVALID: var2
Explanation var3 var4 var5 var6 var7 var8.
This message contains variables that are resolved at
run-time and emitted by the server as it processes. Explanation
User response run-time and emitted by the server as it processes.

User response User response
Review the messages just before and after this Check the abend code and any related abend
message to understand the context. messages. If possible, fix the problem identified
by the error messages, and restart the product. If
AVZ0018H var1 var2
Support. Note the exact contents of the above error
Explanation message and any other error messages associated
with the product failure.
run-time and emitted by the server as it processes. AVZ0022S Second 2 characters of subsystem
name must be prodID.
User response
Explanation
message to understand the context. Each copy of the product must use a unique
subsystem ID string. The default subsystem ID is
AVZ0019I var1 var2
specified in the started task procedure or in the START
command used to start the product. In either case,
Explanation the subsystem ID string must always be exactly four
characters long, and the second two characters must
be a valid product ID pair (prodID). For example: "DB"
run-time and emitted by the server as it processes.
is for AVZ and "WS" is for HTTP-API.
User response
User response
Fix the subsystem ID string used to start the product
by modifying the product started task procedure or
AVZ0020S First character of subsystem name by changing the product start command. Restart the
must be an alphabetic character product using a valid subsystem ID string.
(A-Z).
AVZ0023S Subsystem name must be four (4)
characters long
Explanation
Each copy of the product must use a unique Explanation
Each copy of the product must use a unique
the subsystem ID string must always be exactly four
characters long, and the first characters must be one
the subsystem ID string must always be exactly four
of the alphabetic characters A-Z.
characters long.
User response
User response
by changing the product start command. Restart the
product using a valid subsystem ID string.
AVZ0021S ABEND ERROR abcode REASON
AVZ0024S Last character of subsystem name
rsncode AT modname+offset
must be alphanumeric
Explanation
Explanation
A serious abend occurred during product initialization,
Each copy of the product must use a unique
execution, or termination. The abend was not
recoverable, and the product was forced to terminate.
the subsystem ID string must always be exactly four AVZ0029S Configuration issue detected; ss
characters long. The last character can be one of the not configured for CPU var1,
alphanumeric characters A-Z or 0-9. execution continues

Fix the subsystem ID string used to start the product None.
User response
AVZ0025S %PM not prepared for execution
by feature code AVZ0030S %PM will require configuration
update in <x> days
Explanation
Explanation
run-time and emitted by the server as it processes. None.

Review the messages just before and after this Contact Rocket Software Support.
AVZ0031E %PM will require configuration
AVZ0026S ss not configured for this CPU update in <x> days.
var1, execution terminating.
Explanation
Explanation
None.
None.
User response
User response
AVZ0032S %PM configuration problem,
AVZ0027S MVS/370 not supported execution terminating.
The product checked the host system and found that None.
the host system is some version of MVS/370. The
product does not support MVS/370.
User response
User response Contact Rocket Software Support.
The product only supports z/OS®. z/OS must be AVZ0033S CONFIGURATION FROM 'var2'
installed before the product can be used. PARAM. DOES NOT SUPPORT
EXECUTION OF THIS PRODUCT -
AVZ0028S Product code pcode is invalid. TERMINATING.
None. None.

Contact Rocket Software Support. Contact Rocket Software Support.
AVZ0034S PM feature code feature not
configured.

None. This is a generic error message used to describe
a wide variety of product initialization, execution,
User response and termination errors. The message text provides
the current operation (service) and what the current
Contact Rocket Software Support. operation was trying to do, such as GETMAIN,
FREEMAIN, ATTACH, and so on.
AVZ0035S subsys requires configuration
update, execution continues.
User response
Explanation Check the error messages and the return code
associated with this problem. There may be one or
None.
more error messages referring to the current problem.
If possible, fix the problem identified by the error
User response messages, and restart the product. If the problem
cannot be resolved, contact Software Support.
AVZ0039S rout errdesc FAILED,
AVZ0036S service OF desc FAILED, RC=rcode,
ABEND=abcode, REASON
DETECTED AT addr
CODE=rsncode
Explanation
Explanation
This is a generic error message used to describe
This is a generic error message used to describe a
wide variety of product initialization, execution, and
and termination errors. The message text provides
termination errors. The message text provides the
current operation and what the current operation was
operation was trying to do, such as GETMAIN,
trying to do.
FREEMAIN, ATTACH, and so on.

Check the error messages and the return code
messages, and restart the product. If the problem
AVZ0040S cblk CONTROL BLOCK AT addr
AVZ0037E rout errdesc FAILED, RC=rcode,
msgtext
DETECTED AT addr, %SK
This message is used to describe control block errors.
Some type of service routine (rout) (operating
The error may be an invalid tag, invalid length, or some
system or product specific) failed. The error message
other error. The control block (cb) could not be used
identifies the service routine and the type of error.
because of the error.
User response
User response
Check the full text of the error message, and fix the
program that calls the application program interface, if
problem. There may be one or more error messages
necessary.
referring to the current problem. If possible, fix the
AVZ0038S service OF desc FAILED, RC=rcode, problem identified by the error messages, and restart
REASON=rsncode, DETECTED AT the product. If the problem cannot be resolved,
addr, %SK contact Software Support.
AVZ0042I %PX ver/lvl initializing User response
on processor
cpuID.model.modelno.manuf This error should only occur during product
PCCAcount flag. termination or if the main product address space is
not executing. If this error occurs at any other time,
contact Software Support. The main product address
Explanation space will have to be restarted if this error is reported.
This message is issued during early start-up and AVZ0046W Initialization procedure procedure
displays information about the hardware on which or IRXJCL ended with condition
the product is executed. This message provides code rcode - processing continues
information helpful to support personnel should some
configuration difficulty arise.
Explanation
User response IRXJCL was attached to execute the initialization
procedure. The reported non-zero condition code was
No action is required. If later messages indicate a set after execution.
configuration problem has been encountered, this
message may aid in the swift resolution of the rcode (the return code) may in this case also be a
problem. If the problem cannot be resolved, contact condition code.
IBM Software Support.
AVZ0043H msgtext
User response
Check the initialization exec for REXX-language errors
Explanation which might cause the return code to be set. It may
be impossible to distinguish between IRXJCL's return
This message is used to print out various internal code and the return code set by the procedure.
control blocks, the contents of processor registers, and
other hexadecimal information. AVZ0047I DATASPACE procedure CREATED
TIME = t2 BY %PM
User response
Explanation
If there are other messages indicating an error, use
this message in conjunction with them to determine DSPSERV system service routine was invoked at
the cause of the problem. If there is a problem and you initialization. A dataspace has been created.
are unable to resolve it, contact Software Support.
AVZ0044S errdesc FREEMAIN FAILED
User response
None required. This is an informational message.
Explanation AVZ0048E DSPSERV ERROR. RETURN CODE =
Storage release error. The product was unable to free a rcode. t2 %PM
section of storage.
Explanation
User response DSPSERV system service routine was invoked at
Check the abend code to determine the cause of initialization to create a dataspace. However, it
the error. Make any needed changes to resolve the received a non-zero return. The dataspace was not
problem, and restart the product. created.
AVZ0045S Task or exit modname can not be

executed
User response
Check the return code displayed in the message in
Explanation the Auth Assembler Services Reference, and take
appropriate action, if possible. If the problem cannot
A product macro cannot be used because the product be resolved, contact Software Support.
control blocks are inconsistent. This macro is used to
initialize a task or an exit. The task or exit will not be AVZ0049I Dataspace added to PASN list. t2
able to execute. %PM

ALESERV system service routine was invoked at Initialization of the subsystem is terminated
initialization to add this address space to a previously immediately with an S0C3 abend. Contact the
created dataspace. Software Support group.
AVZ0056E Invalid data found in csect loaded
User response at addr ivdata
Explanation
AVZ0050W var1 configuration requires an
update, certain features will During subsystem initialization, invalid data was
need modification, execution detected within a control section (csec) or table
continuing. loaded as part of the product's primary execution load
module.
Explanation ivdata represents a hex dump of the invalid data area.
None.
User response
User response Initialization of the subsystem is terminated
immediately with an S0C3 abend. Contact the
Software Support group.
AVZ0057W var1 rejected for use - var2 var3.
AVZ0053S Configuration issue: processor
model number (modelno) does
not match configured model; Explanation
execution continues.
None.
Explanation
User response
None.
User response
AVZ0058W var1 refresh required in var2 days.
AVZ0054H var1 Configuration installed until Explanation
var2 (var3 parameter).
None.
Explanation
User response
None.
User response AVZ0059S Configuration issue: H/W

processor ID var1 mismatched
Contact Rocket Software Support. configuration for var2 of past var3
hours.
AVZ0055E csect not found within %PM
primary load module
Explanation
Explanation None.
During subsystem initialization, the indicated control
section (CSECT) was missing from the product's User response
primary execution load module.
AVZ0060T LATCH SET CREATED: LS-
NAME=lsname LATCHES=lcount
LS-TOKEN=lstoken additinfo
Information written to trace when a new latch set is Interval recording encountered an internal control
created within the address space block error while creating an interval summary record.

None. The interval record in error is discarded and
summarization continues. If the problem cannot be
AVZ0061E LATCH ERROR: reqtype errdesc resolved, contact Software Support.
additinfo
AVZ0065T Interval summary %1: %2
Explanation
Explanation
An error or unexpected condition was detected in a
latch manager internal support routine This messages contains the number of interval
summary record errors found.
User response
User response
Look for related messages indicating the cause of
the error and correct the underlying problem. If the Contact Software Support.
problem cannot resolved, contact Software Support.
AVZ0066S Logon of the address space user ID
AVZ0062T LATCH operation: userID failed. Detected at addr.
LSTOKEN=lstoken
LATCHNO=latchno Explanation
LTOKEN=lstoken RQSTR=reqID
additinfo The product failed to create a security environment for
a task using the user ID of the address space.
Explanation
User response
Information written to trace when a latch is obtained,
released, or purged There may be one or more additional error messages
or abends referring to the problem. If possible, fix
the problem identified by the error messages, and
User response
restart the product. If the problem cannot be resolved,
None. contact IBM Software Support.
AVZ0063S z/OS Version must be at 1.13 or AVZ0067S LOGON of the SSLUSERID, userID,
higher. Execution terminating. failed. Detected at addr.
The product checked the host system and found that The product failed to create a security environment for
the host system is not running at z/OS 1.13 or higher. a task using the userid specified in SSLUSERID.
The product does not support z/OS levels below 1.13.
User response
User response
There may be one or more additional error messages
The product only supports z/OS 1.13 and higher. z/OS or abends referring to the problem. If possible, fix
1.13 or higher will have to be installed before the the problem identified by the error messages, and
product can be fully supported. restart the product. If the problem cannot be resolved,
contact Software Support.
AVZ0064T Interval summary operation. SMLH
at addr1 SMLG at addr2. Tag: AVZ0068T Logon of user ID userID failed.
additinfo
Explanation
Logon failed for user ID specified in Services request.

Check whether user ID is valid or if the password was This informational message identifies the number of
correct. online general purpose processors (CPs) and zIIPs
detected during product initialization.
AVZ0069W The severity level of message
cannot be changed.
User response
Explanation None. This message is for informational purposes only.
None. AVZ0083I LPAR lpar. CEC MSUs: cap1. LPAR
MSUs: cap2. Current® avg. var
User response
Explanation
This informational message identifies the LPAR and
AVZ0080E Control block cblk could not be
the capacity of the processors.
located
var is only relevant if z/OS is a VM guest.
Explanation
User response
The product tried to find one of several control blocks
during product initialization. One of the control blocks None. This message is for informational purposes only.
could not be found.
AVZ0084I Decimal float support ind available
on this processor
User response
Ensure that the version of the host (MVS™) operating Explanation
system is supported by the product. If the host
This informational message identifies whether decimal
operating system version is supported by the product,
float support is available or not (ind).
check for any other error messages referring to the
current problem. If possible, fix the problem identified
by the error messages, and restart the product. If the User response
problem cannot be resolved, or if the host operating
None. This message is for informational purposes only.
system version is not supported by the product,
contact Software Support. AVZ0090I TSOSRVACTIVE(YES) INVALID IN
PROB STATE - SIMULATED USING
AVZ0081E Unknown host operating system -
TMP IN CURRENT A/S
prodname
Explanation
Explanation
This message is issued when TSOSRVACTIVE(YES)
The product was not able to identify the host operating
has been specified as a start-up parameter, but the
system by its product name.
product is running in test mode under TSO. The
outboard facility cannot be enabled/managed without
User response being authorized to operate in supervisor state and
operating as an MVS started task.
Ensure that the version of the host (z/OS) operating
system is supported by the product. If the operating
system is supported by the product, check for User response
any other error messages that refer to the current
The outboard TSO server facility is not activated.
problem. If possible, fix the problem identified by the
Outboard TSO server facilities will be simulated using
error messages, and restart the server. If the problem
TSO/E (if available) within the current address space.
cannot be resolved or if the operating system is not
You should re-test applications developed under
supported, contact Software Support.
TSO/E when moving them to an authorized copy of
AVZ0082I count1 online CPs and count2 the subsystem, because some operations (such as
online zIIPs detected time limit processing, CPU time monitoring) cannot be
simulated properly within a test copy of the product
running in problem state.
AVZ0091E service OF desc FAILED, RC=rcode and termination errors. The message text provides
operation was trying to do.
Explanation
This is a generic error message used to describe User response
a wide variety of TSO/SRV initialization, execution,
and termination errors. The message text provides Check the error messages and the return code
the current operation (service) and what the current associated with this problem. There may be one or
operation was trying to do. more error messages referring to the current problem.
messages, and restart the product.
User response
AVZ0095S MAIN TASK TIMED OUT WHILE
WAITING TO BE POSTED BY THE
TSO/SRV SUBTASK
more additional error messages or abends referring
to the current TSO/SRV problem. If possible, fix the
problem identified by the error messages, and restart Explanation
the product.
The product main task timed out while waiting to
AVZ0092E CANCEL of server jobname be posted by the TSO/SRV subtask. The TSO/SRV
(ASID=asid) failed subtask has either terminated abnormally or is hung.
The product may or may not be able to continue
processing.
Explanation
Server address spaces which will not shutdown in a User response
normal way (e.g. a long running server task that is still
executing) are canceled. If the cancel is not accepted Check for other abends or product messages related
for any reason, this message is issued. to this one. If the problem cannot be resolved, contact
Software Support.
User response AVZ0096S TSO/SRV ABEND abcode
OCCURRED AT modname+offset
If the server address space survives product
DURING desc
termination you may attempt to cancel it manually or
possibly even force it. The fact that a server address
space (asid) remains in the system when the product Explanation
is restarted will have no harmful effect on product
This error message describes an abend that occurred
execution and can be ignored.
during TSO/SRV execute queue processing termination
AVZ0093I Waiting for TSO server termination processing (desc).
to complete
User response
Explanation There may be one or more error messages related
Inactive servers have been posted to shutdown. The to the current problem. If possible, fix the problem
termination process will wait for a short time to allow identified by the error messages, and restart the
the servers to shutdown normally. If, at the end of product. If the problem cannot be resolved, contact
this period, any servers are still active, they will be Software Support.
canceled.
AVZ0097I service OF desc FAILED, RC=rcode
User response
Explanation
During server termination, product ow found that
AVZ0094S service OF desc FAILED, RC=rcode a busy TSO server did not respond to an internal
shutdown request. An attempt to issue an MVS
CANCEL command to terminate the server failed.
Explanation
wide variety of TSO/SRV execute queue initialization

None. The transaction running in the server will None.
eventually complete. The subsequent attempt to read
from an additional TSO/SRV command will fail, and the User response
server will then terminate following a 614 abend.
None. This is an informational message only.
AVZ0101S %PM PRODUCT USAGE EXCEEDS
SPECIAL CONFIGURATION AVZ0106S Version 7 Configuration required,
LIMITS: var1 contact Software Support.
None. None.
User response:
User response Contact Rocket Software Support.
Contact Rocket Software Support. AVZ0107S Server parameter required,
AVZ0102S EXCESS USAGE - LOCATIONS:
var1, DRIVER TYPES: var2, HOST
BUSINESS SYSTEMS: var3 Explanation
None.
Explanation
None. User response
User response
AVZ0110H INITIALIZATON OF QUICKREF
Contact Rocket Software Support. INTERFACE FAILED, VERIFY
QUICKREF DSN AND INSTALL
AVZ0103H Access restricted to TCP/IP - LU STATUS
6.2 support not activated
Explanation
Explanation
This message shows that the product was unable to
None. initialize the QUICKREF interface.

Contact Rocket Software Support. If QUICKREF is installed on this system, verify that
AVZ0104H No usage parameter specified. the QUICKREF load library is either in the linklist or
Usage specific to basic is allocated via the QWREFLIB DD statement in the
administrative functions and SIS. started task JCL. If QUICKREF is not installed on the
system, remove all references to QUICKREF from the
started task JCL.
Explanation
AVZ0111S Invalid DB2® subsystem ID subsys
None.
set by LOGDB2SUBSYS parameter

An invalid Db2 subsystem was specified for logging
AVZ0105I TEST DATE var1 (var2) FOR using the LOGDB2SUBSYS parameter. The specified
CONFIGURATION, D-O-C(var3 Db2 subsystem does not exist, or has not been
var4), var5 installed and activated on the system since the
previous IPL.
Specify a valid Db2 subsystem for logging using the Specify a valid default Db2 subsystem ID via the
LOGDB2SUBSYS parameter. If logging is not desired startup DEFAULTDB2SUBSYS parameter, or specify
specify 'NONE' for LOGDB2SUBSYS. You may also 'NONE' for this parameter if Db2 should not be used.
leave LOGDB2SUBSYS unset in which case the default Product initialization continues. Note that the Db2
Db2 subsystem set for the server automatically or by subsystem need not be active (up) when the Server
the DEFAULTDB2SUBSYS parameter will be used, if is started, however, it must have been successfully
valid. Product initialization is terminated. installed and started on the system at least once prior
to server startup.
AVZ0112S Invalid default DB2
subsystem subsys set by AVZ0114W DB2 logging will not be activated
DEFAULTDB2SUBSYS parameter - requires valid default DB2
subsystem ID
Explanation
Explanation
A default Db2 subsystem ID was explicitly specified
via the DEFAULTDB2SUBSYS parameter, but does The default Db2 subsystem ID set automatically by the
not designate a valid Db2 subsystem ID. When the server (from the DSNHDECP load module) is not valid
DEFAULTDB2SUBSYS parameter is explicitly set (to and no explicit value was set for the LOGDB2SUBSYS
any value except 'NONE'), the target Db2 subsystem parameter. Since Db2 logging requires a valid default
ID is verified. The ID will fail validation if the target Db2 ID, the value 'NONE' is forced for LOGDB2SUBSYS
Db2 subsystem does not exist or has never been and Db2 logging is not activated.
successfully activated in the system since the last IPL.
User response
User response
Specify a valid Db2 subsystem ID as the default Db2
The product terminates if an explicitly specified ID is using the DEFAULTDB2SUBSYS parameter. If you do
invalid, but will allow startup to continue if it selected not wish to set a global default Db2 subsystem ID for
the default subsystem ID automatically. (The server all operations, but desire Db2 logging to be activated,
uses the default Db2 ID from the DSNHDECP load specify a valid ID for LOGDB2SUBSYS instead. Db2
module or the standard string, 'DSN ', if no explicit logging will not be activated during the current server
setting is provided for the DEFAULTDB2SUBSYS startup.
parameter). Product initialization is discontinued and
the server terminates. Specify a valid default Db2 AVZ0115E LE/370 INTERFACE MODULE
subsystem for DEFAULTDB2SUBSYS or leave the CEEPIPI CANNOT BE LOADED - IT
parameter unset to allow an automatically assigned IS REQUIRED FOR SSL SUPPORT
default value to be used.
Explanation
AVZ0113W DEFAULT DB2 SUBSYSTEM ID
(subsys) FROM DSNHDECP IS During initialization, it was determined that the MVS
INVALID, CONTINUING Language Environment® interfaces are needed for
execution of the subsystem. SSL support requires
the use of LE/370 interfaces. The interface module,
Explanation
CEEPIPI, was not found in STEPLIB or the link list.
The default Db2 subsystem ID selected automatically
by the server is not a valid Db2 subsystem ID. User response
The server has selected the Db2 subsystem ID
automatically because no value was set for the Product initialization is abandoned. To restart the
DEFAULTDB2SUBSYS parameter. The server uses the subsystem, ensure that either the LE/370 runtime
default Db2 ID from the DSNHDECP load module, or, if libraries are available in STEPLIB or the link list, or turn
DSNHDECP cannot be loaded, uses the standard value off the SSL support option.
'DSN ' as the default ID. Db2 operations which do not
AVZ0116W DB2 logging cannot be activated
explicitly send a Db2 subsystem ID will fail because
when DB2 SUBSYS default is
the default subsystem ID is invalid. In addition,
'NONE', logging deactivated
MSG0114W may be issued following this message if
Db2 logging is inhibited because of it's dependency
upon the default Db2 subsystem ID validity.

The Db2 logging feature of the product cannot be used None.
with a default Db2 subsystem setting of 'NONE'. The
DEFAULTDB2SUBSYS parameter must be set to an User response
actual Db2 subsystem ID, or left un-specified. Since
'NONE' was set ALL DB2 PROCESSING IS INHIBITED. Contact Rocket Software Support.
This message is only issued when the LOGDB2SUBSYS
AVZ0120I SEF msgtext
parameter has explicitly been set to a Db2 subsystem
ID value other than 'NONE'. The LOGDB2SUBSYS
parameter is ignored and reset to 'NONE' so that Explanation
it matches the DEFAULTDB2SUBSYS parameter. This
The product tried to initialize SEF during product
prevents Db2 logging activation. Product initialization
initialization. SEF initialization failed.
continues without activating Db2 logging.
User response
User response
Specify a valid default Db2 subsystem ID for
DEFAULTDB2SUBSYS or leave that parameter
unset (if unset, the default value is fetched
to the current SEF initialization problem. Check for
from the DSNHDECP load module). Product
open errors, such as security product related abends.
initialization continues with NONE set for both
Also, check for storage allocation errors or abends.
DEFAULTDB2SUBSYS and LOGDB2SUBSYS.
AVZ0117S type TCP/IP port number is messages, and restart the product. If the problem
invalid - type TCP/IP processing cannot be resolved, contact Software Support.
terminated
AVZ0121W SEF - service OF desc FAILED,
RC=rcode
Explanation
The TCP/IP port number specified for one of the types Explanation
of TCP/IP (type) supported by the product is invalid.
The product tried to initialize or terminate SEF
The main product address space cannot complete
during product initialization or termination. An internal
initialization if an invalid TCP/IP port number has been
service routine called during SEF initialization or
specified for any type of TCP/IP.
termination exited with a non-zero return code.

Specify a valid port number for the type of TCP/IP that
detected the invalid port number. If the type of TCP/IP
is not needed, you can also just not set the TCP/IP port
more additional error messages or abends referring to
number at all for the failing type of TCP/IP.
the current SEF initialization or termination problem.
AVZ0118S Load balancing not available - VCF Check for open errors, such as security product
feature code is required. related abends. Also, check for storage allocation
errors or abends. If possible, fix the problem identified
Explanation
None. Support.
AVZ0122S ABEND abcode REASON rsn
User response OCCURRED AT modname+offset
DURING SEF desc
AVZ0119W Logging not available - DB2 Explanation
feature code is required.
The product tried to initialize or terminate SEF
during product initialization or termination. The SEF
initialization/termination routine abended.
Check the error messages and the abend code Check for other abends or product messages related
associated with this problem. There may be one or to this one. If the problem cannot be resolved, contact
more additional error messages or abends referring to Software Support.
the current SEF initialization or termination problem.
AVZ0128S Dynamic definition of ddname
Check for open errors, such as security product
related abends. Also, check for storage allocation library failed
errors or abends. If possible, fix the problem identified
by the error messages, and restart the product. If Explanation
The mapping data set could not be defined properly to
Support.
allow for caching of map data members.
AVZ0123T SEF initialization complete
User response
Explanation
Check for other abends or product messages related
The product has completed SEF initialization. All to this one, and contact Software Support.
triggers and events will now be passed to the SEF for
AVZ0130H Initializing secur release rel
processing.
security environment
User response
Explanation
No action is required in response to this message.
This message shows that the product was able to
However, this message can be used to activate one or
successfully initialize the security environment for the
more event handling procedures.
interface between the product and ACF2 or RACF®.
AVZ0126S service OF desc FAILED, RC=rcode The message shows the security product (secur)
and release level (rel) to which the interface was
established.
Explanation
This is a generic error message used to describe User response
a wide variety of SEF execute queue initialization
and termination errors. The message text provides No action is required unless the customer is not
the current operation (service) and what the current running any security package and one was identified
operation was trying to do. or the release level is incorrect. Contact Software
Support if such an error is detected.
User response AVZ0131S subsysID SSCT chain scanning
error
more error messages referring to the current problem. Explanation
The SSCT chain was scanned by the security interface
routines looking for ACF2 or RACF. Some error exists in
the SSCT chain and the search could not be continued.
AVZ0127S MAIN TASK TIMED OUT WHILE
WAITING TO BE POSTED BY THE User response
subtask SUBTASK
Examine the SSCT chain for an invalid chain or SSCT
control blocks. If the problem cannot be resolved,
Explanation
The product main task timed out while waiting to be
AVZ0132W No security package found
posted by an SEF subtask. The SEF subtask has either
terminated abnormally or is hung. The product may or
may not be able to continue processing. Explanation
The SSCT chain was scanned by the security interface
routine looking for one of the known security
packages: RACF, CA ACF2 or CA Top Secret. No known

security product was found and the security package User response
field was set to NONE.
associated with this problem. There may be additional
User response error messages in the system log. If possible, fix
If no security package exists on your system, this is the problem identified by the error messages, and
not an error, and no further action is needed. If RACF, restart the product. If the problem cannot be resolved,
CA ACF2 or CA Top Secret is active and this message contact Software Support.
was received, contact Software Support. AVZ0136W LOGUSERID (userid) LOGON
AVZ0133E relno release unknown, release FAILED rcode1 rcode2 rsncode -
code is relno msgtext
The product attempted to recognize the release level An error occurred while attempting to verify a new
(relno) of ACF2 and did not find a release level that USERID for the logging task. This is a security
it recognized or that is supported. As of this date, all environment error.
CA-supported releases of ACF2 are supported by the This message contains two return codes; rcode1
product. represents the security module return code, and
rcode2 represents the RACF (SAF) return code.
User response
If your release of ACF2 is supported by CA, contact User response
Software Support to request that support be added for Product logging continues with the previous USERID
that release of ACF2. If the release number appears to used for logging. Correct the value in the LOGUSERID
be in error, contact Software Support for assistance. parameter.
AVZ0134W RUNAUTH USERID cache AVZ0137S ABEND abcode REASON rsn
initialization failed - sharing of OCCURRED AT modname+offset
RUNAUTH USERIDs now disabled DURING SOM desc.
During start-up, the SHARERUNAUTHACEES option An ABEND occurred during initialization or termination
was set to ON, but an error occurred while initializing of the Security Optimization Management feature.
the cached RUNAUTH userid table. This is likely due to
a GETMAIN failure.
User response
User response Check the error messages and the abend code
Product initialization continues with the more additional error messages or abends referring
SHARERUNAUTHACEES option set to OFF. Examine to the current initialization or termination problem.
the wraparound trace and console messages for an Check for security product related abends and storage
explanation of the error. If you are unable to locate the allocation errors or abends. If possible, fix the problem
reason for the failure, contact Software Support. identified by the error messages, and restart the
AVZ0135W Security routine failed attempting product. If the problem cannot be resolved, contact
to validate the LOGUSERID userID. Software Support.
RC=rcode. AVZ0138W SOM facility is not available for
pkg. Processing continues.
Explanation
The internal security service routine failed while Explanation
attempting to verify a new USERID for the logging task. Security Optimization Management (SOM) was
requested, but the security package (pkg) is not RACF.
SOM can only be enabled for RACF.
User response up manual rules, prevent all catch-up manual rules
from firing, or specify the type of catch-up processing
None. This message is for informational purposes only. for each individual rule. It follows messages 0140I and
AVZ0139W Dynamic service services are not 0141I. If more than two minutes expire while waiting
available for your reply or three invalid replies are made, the
default action of NO will be taken.
Explanation
User response
An MVS dynamic LPA service is not available.
Reply YES to cause all catch-up manual rules to
fire. Reply NO to prevent all catch-up manual rules
User response from firing. Reply MANUAL and you will be prompted
None. This message is for informational purposes only. to specify the type of catch-up processing for each
individual rule.
AVZ0140I The following catch-up rules
require a final catch-up AVZ0143R Reply 'YES' to catch-up
disposition rsname.rulename rule or 'NO' to
bypasscatch-up
Explanation
Explanation
This message is issued when there are catch-up
manual rules which did not fire during the previous This message is issued when there are catch-up
execution of the product. It is followed by message manual rules which did not fire during the previous
0141I, which documents the unfired rules. execution of the product and you selected MANUAL in
your reply to message 0142R. The name of the rule
you are being prompted for is in the format ruleset.rule
User response name. If more than two minutes expire while waiting
No action is required in response to this message. for your reply or three invalid replies are made, the
However, this message can be used to activate one or default action of NO will be taken.
AVZ0141I rule.rsname1, rule.rsname2 … User response
rule.rsname7 Reply YES to cause the rule to fire. Reply NO to prevent
catch-up firing for the rule.
Explanation AVZ0144E Invalid catch-up manual reply:
This message is issued when there are catch-up reply
manual rules which did not fire during the previous
execution of the product. It lists up to seven rules Explanation
that did not fire, using the format ruleset.rule. Multiple
messages may be issued so that all catch-up manual An invalid reply was specified to one of the catch-
rules may be listed. up manual console messages. The message causing
the error will be reissued so that you can correctly
reply. After three invalid replies for the same message,
User response default action will be taken. For a description of the
No action is required in response to this message. default action, see the explanation of the original
However, this message can be used to activate one or message.
AVZ0142R Reply 'YES' to catch-up all User response
rules, 'NO' to bypasscatch-up, Determine the proper reply from the text of the
or 'MANUAL' for rule by rule message, and reply correctly.
prompting
AVZ0145E Catch-up reply wait exceeded 2
minutes. Default used
Explanation
This message is issued when there are catch-up
manual rules which did not fire during the previous
execution of the product. It allows you to fire all catch-

Explanation time to fire. As a result, catch-up processing for the
rule will fail the next time the product is restarted.
The product waited over two minutes for a reply to one This normally occurs when the GLOBALMAX startup
of the catch-up manual messages. Since no response parameter has been exceeded and it is no longer
was made during that time, default action was taken. possible to create new global variables. Return code
93 indicates that GLOBALMAX has been exceeded.
User response Additionally, every time the TOD rule fires, the internal
global variable is updated, and return code 4 will be
None. If a reply was desired, you will need to speed displayed in this message.
your response to the message.
AVZ0146E 3 Invalid catch-up replies. Default User response
taken
Shut down the product, and allocate a larger SYSCHK1
data set. This may not be necessary if you already
Explanation have a large data set but are only using a part of it due
Three invalid replies were made to a catchup manual to a small GLOBALMAX value. Use the IDCAMS REPRO
message. Since no correct response was received, command to copy the existing database to the new
default action was taken. larger one, if necessary. Increase the value assigned
to the GLOBALMAX parameter in your initial parameter
settings, and restart the product.
User response
AVZ0150S service OF desc FAILED, RC=rcode
None. Reply as required next time.
AVZ0147E Catch-up service service for Explanation
variable varname failed, RC=rcode.
a wide variety of trace initialization and termination
Explanation errors. The message text provides the current
An internal error was encountered during catch-up operation (service) and what the current operation was
processing performing an AVZVALUE or SWSVALUE trying to do.
function.
User response
User response Check the error messages and the return code
Contact Rocket Software Support. associated with this problem. There may be one or
AVZ0148W Catch-up rule rsname.rulename If possible, fix the problem identified by the error
has changed. Catch-up bypassed. messages, and restart the product. If the problem
Explanation AVZ0151S service OF dsname FAILED,
This message is issued when a catch-up rule has been RC=rcode, REASON CODE=rsncode
modified since the last time the rule was enabled. The
rule would otherwise have fired for catch-up because Explanation
either the product or z/OS was down during the last
time the rule should have fired. Because the rule has This error message describes errors that occurred
changed, it will not fire for catch-up. during trace initialization, execution, or termination
while using the DIV (Data In Virtual) system service.
For a list of the return codes and reason codes from
User response the DIV macro see the appropriate documentation.
None.
AVZ0149E Catch-up rule rule global variable User response
write failed, RC=rcode Check the DIV return and reason codes associated
with this problem. There may be one or more error
Explanation messages referring to the current problem. If possible,
fix the problem identified by the error messages, and
This message is issued when a catch-up rule attempts restart the product. If the problem cannot be resolved,
but fails to write a global variable describing the next contact Software Support.
AVZ0152S service OF dsname FAILED, User response
CODE=rsncode There is no action required in response to this
message. This message should only be displayed once
when you install the first release of the product that
Explanation supports the upgraded data area format. You may also
This error message describes an abend that occurred see this message again if a prior version of the product
during trace initialization, execution, or termination is used after the Trace Browse data area has been
while using the DIV (Data In Virtual) system service. upgraded. The message will be deleted as soon as
The abend codes and reason codes from the DIV the Trace Browse data area upgrade is completed. The
macro are documented in the IBM manual z/OS upgrade requires about 3 minutes for every 100,000
Programming: Assembler Services Reference. messages. If this message recurs, contact Software
Support for additional assistance.
User response AVZ0156S service PASSED desc - code
Check the DIV abend and reason codes associated

with this problem. There may be one or more error Explanation
messages referring to the current problem. If possible, This is a generic error message used to describe
fix the problem identified by the error messages, and a wide variety of trace initialization and termination
restart the product. If the problem cannot be resolved, errors. The message text provides the current
contact Software Support. operation (service) and what data (valid or invalid) was
AVZ0153H ddname data set not allocated passed to the current operation.

Product has detected that a TRACE DD card is not Check the error messages and the return code
present in the JCL used to start the main product associated with this problem. There may be one or
address space. more error messages referring to the current problem.
User response cannot be resolved, contact Software Support.
Modify the JCL and specify the TRACE DD card after AVZ0160S Possible shortage of storage, bytes
validating that the necessary DIV data set is allocated. bytes required for Trace Browse
AVZ0154S Any existing Trace Browse data
discarded Explanation
This is a follow-up message to message 0150S when a
Explanation GETMAIN has failed. This message indicates the size,
Product detected this error. in bytes, of the area requested by the GETMAIN.

Contact Software Support. If the GETMAIN return code indicates insufficient
storage to complete the GETMAIN request, please
AVZ0155S Please standby - upgrading Trace increase your available storage (above the 16MB line)
Browse - all data retained by the indicated amount.
AVZ0161S Main task timed out while waiting
Explanation to be posted by the TRACE subtask
The product is upgrading the Trace Browse data
area. The Trace Browse data area must be upgraded Explanation
whenever messages from an earlier version of the
product are detected in the Trace Browse data area. The product main task timed out while waiting to be
The upgraded Trace Browse data area is compatible posted by the trace subtask. The trace subtask has
with earlier releases of the product, as required. either terminated abnormally or is hung. The product
may or may not be able to continue processing.

User response existing Ruleset dataset name. This Virtual Directory
(dir) is not initialized.
Check for other abends or messages related to
the product prior to this one, and contact Software
Support for additional assistance. User response
AVZ0162S service OF dsname Correct the inconsistency between rulesets and
FAILED, ABEND=abcode AT dataset names in all related virtual directories.
modname+offset, REASON AVZ0171S service OF dsname FAILED,
CODE=rsncode RC=rcode, REASON CODE=rsncode
This error message describes an abend that occurred This error message describes errors that occurred
during trace initialization, execution, or termination during global variable initialization, execution, or
while using the DIV (Data In Virtual) system service. termination while using the DIV (Data In Virtual)
The abend codes and reason codes from the DIV system service. For a list of the return codes and
macro are documented in the IBM manual z/OS reason codes from the DIV macro see the appropriate
Programming: Assembler Services Reference. documentation.

Check the DIV abend and reason codes associated Check the DIV return and reason codes associated
with this problem. There may be one or more error with this problem. There may be one or more error
messages referring to the current problem. If possible, messages referring to the current problem. If possible,
fix the problem identified by the error messages, and fix the problem identified by the error messages, and
restart the product. If the problem cannot be resolved, restart the product. If the problem cannot be resolved,
contact Software Support. contact Software Support.
AVZ0165I SEF msgtext AVZ0172S service OF dsname FAILED,
Explanation CODE=rsncode
SEF subtask mapping information messages.

Explanation
User response This error message describes an abend that occurred
during global variable initialization, execution, or
None at this time. termination while using the DIV (Data In Virtual)
AVZ0166E Unable to build process block for system service. For a list of the return codes and
SEF interface, RC=rcode reason codes from the DIV macro see the appropriate
documentation.
Explanation
User response
Services startup was unable to build the environment
to interface to the SEF task. The return code is given. Check the DIV abend and reason codes associated
with this problem. There may be one or more error
messages referring to the current problem. If possible,
User response fix the problem identified by the error messages, and
Check the return code and look for other error restart the product. If the problem cannot be resolved,
messages which may explain the error. contact Software Support.
AVZ0167E Ruleset rule specifies DSN AVZ0173W ddname data set not allocated
dsname, should be dsname for
VirtualDirectory dir. Explanation
The product has detected that the SYSCHK1 DD card is
Explanation not present in the JCL used to start the main product
Services startup found a Virtual Directory with a address space.
Ruleset whose dataset name did not match the
Modify the JCL, and specify an appropriate DD card Check for other abends or messages related to
after validating that the necessary DIV data set is the product prior to this one, and contact Software
allocated. Support.
AVZ0174S Any existing global variables data AVZ0178S errdesc DETECTED IN GLOBAL
discarded VARIABLE LIST
The product detected this error. While building/rebuilding the global variable AVL tree,
one of the following (errdesc) occurred: (1) an infinite
User response loop was detected in the sequential list, (2) an invalid
entry was detected in the sequential list, or (3) an
Contact Software Support. invalid offset was detected in the sequential list. The
tree rebuild is terminated at this point. The product
AVZ0175I Global variable upgrade vartext
will attempt to reconstruct the entire global variable
data set. Some global variables may be discarded.
Explanation
Prior to version 02.01.01 of the product, global User response
variables were maintained in a linked list. As of version
Report this message to Software Support. This
02.01.01, they are kept in an AVL tree structure for
situation has occurred due to a prior logic error
improved performance. This message indicates that
or storage overlay. The product should continue to
the global variable pool is being upgraded to the new
function normally after the global variable data set has
format. This message may also be issued as a result
been successfully reconstructed.
of setting the GLOBALREBUILD parameter to YES or
when the global variable database has been corrupted. AVZ0179I Global variable conversion from
version vartext version
User response
Explanation
Prior to version 02.02.00 of the product, global
AVZ0176S Duplicate global variable found,
variables were limited to 256 bytes in size. As of
name=varname
version 02.02.00, this restriction is removed. Prior to
version 03.02.00 of the product, the key size was
Explanation limited to 50 bytes. As of version 03.02.00, the key
size limit is increased to 84 bytes. This message
While building/rebuilding the global variable AVL tree,
indicates that the global variables are being converted
an attempt was made to add a node to the tree, and
to a new format.
the node already existed in the tree. The second value
is ignored, and the tree build/rebuild continues.
User response
User response None. This message is for informational purposes only.
Report this message to Software Support. This AVZ0180I GLOBAL VARIABLE CHAIN
situation has occurred due to a prior logic error. REBUILD vartext, count GLOBALS
AVZ0177S Main task timed out while waiting
to be posted by the global variable Explanation
checkpoint subtask
While doing a global variable tree rebuild, it was found
that the chained list was incomplete and needed to be
Explanation rebuilt. This message indicates the status of the chain
rebuild process.
The product main task timed out while waiting to
be posted by the global variable checkpoint subtask.
The global variable checkpoint subtask has either User response
terminated abnormally or is hung. The product may or
may not be able to to continue processing.

AVZ0181I varname BEING ADDED TO CHAIN to prevent incorrect data being saved. Changes to the
global variable database since the previous checkpoint
will be discarded.
Explanation
While doing a global variable tree rebuild, it was found User response
that the chained list was incomplete and needed to be
rebuilt. This message indicates which variables were Attempt to restart the product. If the same
reinserted back into the global variable chain. error occurs, contact Software Support, giving
them the information in this message. It may be
possible to reconstruct the database by setting the
User response
GLOBALREBUILD parameter to YES prior to restarting
None. This message is for informational purposes only. the product. If not, the global variable data set can be
recovered from a prior backup.
AVZ0182I GLOBAL VARIABLE DATABASE
BEING CONVERTED AVZ0185W GLOBALMAX VALUE OF val1 IS
TOO LOW. RESET TO val2.
Explanation
Explanation
This is the first time version 02.02.00 of the product
has processed this global variable DIV data set. The The GLOBALMAX parameter value is too low and
product is converting the global variable database would cause the global variable database to be
to the new format. The converted global variable destroyed. The value has been ignored and reset to
database will not be usable with older versions of its prior value. This scenario may have been caused by
the product unless the backward conversion utility is a failure in the product initialization REXX program or
subsequently executed. CLIST, which resulted in an attempt to use the default
GLOBALMAX value.
User response
User response
Information only. No action required.
If this error was caused by a failure in the initialization
AVZ0183S ABEND abcode OCCURRED AT REXX program or CLIST, attempt to determine the
modname+offset DURING desc cause of failure as soon as possible. You may wish
to shut down the product to prevent other problems
Explanation from occurring. The GLOBALMAX value may have been
defaulted due to such a failure. If you are really
This error message describes an abend that occurred
attempting to reduce the size of the global variable
during global variable subtask termination processing.
data set, you must stop the product, delete and
This may also occur during an AVL tree rebuild during
reallocate a new DIV data set, and then restart the
startup or when the GLOBALREBUILD parameter is set
product.
to YES.
AVZ0186S CONVERSION FAILED. INCREASE
User response GLOBALMAX BY AT LEAST minval.
There may be one or more error messages related

Explanation
to the current problem. In the case of the AVL tree
rebuild routine, the product will attempt to recover the The conversion of the SYSCHK1 database to
global variable checkpoint data set by automatically the version 03.02.00 format failed because the
rebuilding it. In all other cases, attempt to fix the GLOBALMAX value is not large enough to contain
problem identified by the error messages, and restart the converted data. The new database requires more
the product. If the problem cannot be resolved, space than the old one due to the increased key size.
contact Software Support. The database may require up to twice as much space
in the worst possible case.
AVZ0184S desc storaddr1 storaddr2 storaddr3
User response
Explanation
Shut down the product, and allocate a larger SYSCHK1
A logical error was encountered while validating data
data set. This may not be necessary if you already
prior to a global variable checkpoint. The checkpoint
have a large data set but are only using a part of it due
will be aborted, and the product will be terminated
to a small GLOBALMAX value. Use the IDCAMS REPRO
command to copy the existing database to the new User response
larger one, if necessary. Increase the value assigned
to the GLOBALMAX parameter in your initial parameter SEF service task initialization ends with an error
settings, and restart the product. Adding this value will causing the server to begin shutdown processing.
not leave any free space in the SYSCHK1 data set. You Determine the cause of the error and correct
should leave enough free space to account for growth the problem or conflict. If the problem cannot
in your system. be understood and resolved from the messages
produced, contact Software Support.
AVZ0187I OLD IN-USE BLOCK COUNT -
minval. NEW IN-USE BLOCK AVZ0191W SWI FACILITY WARNING: var1,
COUNT - val. var2 ... var9
This informational message indicates how many A configuration parameter or environmental error was
blocks of storage were being used in the SYSCHK1 detected during activation, termination, or processing
database prior to the conversion to the 03.02.00 by the System Web Interface (SWI) facility. The SWI
format and how many blocks of storage will now be facility continues operation adjusting to the reported
used following the conversion. condition.

Compare the new in-use block count to your Determine if the warning is anticipated or unexpected.
GLOBALMAX value. If this value is close to the If the warning reports an unexpected condition,
GLOBALMAX value, you may not have sufficient free correct the configuration or other problem before
space for normal operation, and you should increase restarting the server.
the size of your SYSCHK1 database as soon as AVZ0192I SWI FACILITY: var1, var2 ... var9
possible.
AVZ0188S INCOMPATIBLE SYSCHK1 Explanation
DATABASE LEVEL lvl, CANNOT BE
USED. The System Web Interface (SWI) Facility has
detected a condition that might be of interest and
reports it using this message number. The message
Explanation MIGHT indicate a configuration problem, or runtime
The SYSCHK1 database is in a format that is problem, depending upon the nature of the reported
incompatible with the current version of the product. information.
This database has probably been converted to a
format supported by a newer version of the product. User response
If a recoverable condition is reported, check the SWI
User response configuration that may contribute to the condition and
Use a version of the database that is compatible with correct prior to the next server restart.
the current version of the product. AVZ0193W SEFACTIVE = "NO" set - SEF rules
AVZ0190E SEF STARTUP ERROR: var1, will not be enabled during start-
var2 ... var9 up .
A configuration parameter or environmental error The SEFACTIVE parameter is set to "NO", so rule
was found during SEF service task initialization. The enablement will not be performed during server
problem is related in some way to the enhanced startup. You can enable rules later by manually issuing
implementation of the System Web Interface (SWI) ENABLE SEF commands against defined rulesets.
facility. Either parameters used to configure the SWI
facility conflict, or new restrictions that this version of
the Server imposes have not been met.

Determine if the warning is anticipated. If not, correct SEF continues processing of the next configuration
the SEFACTIVE start-up parameter and restart the update unless the error is severe. Correct the
server. original resource definition (e.g. "DEFINE RULESET"
or "DEFINE FILE" in the SxxxxIN00 procedure) and
AVZ0194W SEF start-up procedure ended
resubmit the request.
with special RC (8) - auto-enable
of SEF rules bypassed - no SEF AVZ0197S Critical SEF resource definition
rules are enabled. error found - server startup
aborting
Explanation
Explanation
The SxxxxINEF start-up procedure ended with RC=8,
indicating rule enablement should be bypassed. The An error was detected in a critical SEF configuration
server will bypass rule enablement. You can enable resource definition. The server will begin termination
rules later, manually, but until you do so, no event processing to avoid later problems when the SEF task
related processing is performed by the SEF facility. begins execution.

Determine if the warning is anticipated. If not, correct Check the console log for DEFINE RULESET definitions
the SxxxxINEF start-up procedure and restart the entered via the SxxxxIN00 startup procedure. Those
server. definitions which are flagged with the keyword
"INITERROR(ABORT)" and the definitions for ATH,
AVZ0195E XO DATASET ERROR: var1, var2 ... WWW-Master, and TYP rulesets are considered critical.
var9 The server will not be allowed to start if these
definitions are in error. Correct the definitions and
Explanation restart the server.
A configuration or runtime error was found while SEF AVZ0200S MODE SWITCH ROUTINE service
was processing an executable object (XO) dataset. FAILED RC=rcode
XO dataset libraries contains pre-compiled SEF rules
and HTX generation skeleton text files. They are used
Explanation
primarily to support the System Web Interface (SWI)
facility distributed with the server. The product attempted to either acquire storage for
a below the line AMODE switch routine or free the
User response storage used by a below the line AMODE switch
routine. The storage management operation (service)
SEF terminates processing of the current operation, failed.
sometimes by generating an S0C3 ABEND if the
condition is severe. If error is severe SEF may being
User response
termination of the server. Check for related messages
which may aid in problem determination. For SWI, Check if the return code or any other messages
be sure the SWICNTLDSN start-up parameter is set provide additional information about the storage
correctly. Contact Software Support, if the problem management error. Also, check if the operating system
cannot be determined or corrected. is short on storage in CSA. Start or restart the product
if the storage management problem can be resolved.
AVZ0196W SEF CONFIGURATION UPDATE Contact Software Support if the problem cannot be
var1, var2 ... var9 resolved.
Explanation AVZ0201S SSVT service FAILED RC=rcode
SEF is processing a configuration update, such as

Explanation
validating a ruleset definitions and placing the ruleset
online. A problem or warning is reported in this The product tried to either acquire storage for a SSVT
message if the configuration update is not completed control block or free the storage used by the SSVT
normally. control block. The storage management operation
(service) failed.
User response main operating system control block. The product
updated the overall count value.
Check if the return code or any other messages
provide additional information about the storage
management error. Also, check if the operating system User response
is short on storage in CSA or ECSA. Start or restart This is not an error message, and no action is required.
the product if the storage management problem can
be resolved. Contact Software Support if the problem AVZ0206E servrout errdesc FAILED, RC=rcode,
cannot be resolved. DETECTED AT addr
AVZ0202S SAST UDPATE FAILED RC=rcode

Explanation
Explanation Some type of service routine (operating system or
product specific) failed. The error message identifies
The product tried to update one of the subsystem the service routine and the type of error.
interface control blocks used by the system. The
update operation failed.
User response
User response Check the full text of the error message, and fix the
program that calls the application program interface, if
Check the error messages associated with this necessary.
problem. There may be one or more subsystem
interface error messages referring to the current AVZ0207I JSAST TABLE ENTRY FOR
problem. If possible, fix the problem identified by subsys WAS indicator FOUND
the error messages, and restart the product. If - FORCEJSASTUPDATE OPTION
the problem cannot be resolved, contact Software ACTIVE
Support.
AVZ0203S SAST PLIST STORAGE service Explanation
FAILED RC=rcode The FORCEJSASTUPDATE option is on. The
subsystem's ID was or was not found in the
Explanation JSAST table. Updates to JESNRSS and the JSAST
table will be unconditional due to the setting of
The product tried to either acquire storage for the FORCEJSASTUPDATE.
SAST update PLIST or free the storage used by
the SAST update PLIST. The storage management The indicator variable (indicator) may be either null or
operation (service) failed. "NOT".

Check if the return code or any other messages Initialization routines force execution of the JESNRSS
provide additional information about the storage Update and IEFJSBLD calls.
management error. Also, check if the product region AVZ0220I CONNECT TO REAL-TIME SMF
should be increased. Start or restart the product if INTERFACE SUCCESSFUL FOR
the storage management problem can be resolved. stream_name
Contact Software Support if the problem cannot be
resolved. Explanation:
The Real-Time interface to SMF data has been
AVZ0204W Total subsystem count was count1, successfully connected. The specified stream name is
reset to count2 now active.
User response:
Explanation No action is required. Queries for Real-Time SMF data
Many products (such as IMS) create new subsystem may now be issued.
control blocks and add them to the subsystem control AVZ0221E CONNECT OF SMF REAL-TIME
block chain. Unfortunately, these same products do INTERFACE FAILED FOR STREAM
not update the subsystem control block count field. stream_name, RC=return_code,
The product found that the actual count of subsystem REASON=reason_code, DETECTED
control blocks did not match the count value in the AT csect_name

Explanation: Explanation
An SMF Real-Time interface function failed with the
specified return code and reason code. During start-up, DFHSM(YES) was selected to initialize
DFHSM support. However, the server cannot locate a
User response: copy of the IBM-supplied DFHSM interface module,
Check the error messages and the return code ARCGIVER. This module must be available within the
associated with this problem. There may be one or link list, LPA, or the server's STEPLIB load library.
messages, and restart the product. If the problem User response
cannot be resolved, contact Technical Support to Server start-up continues, but the server resets
obtain additional assistance. the DFHSM option to NO, which prevents further
AVZ0230W SERVER'S DFHSM PENDING interactions with DFSMShsm from being undertaken.
HRECALL TABLE IS FULL - Determine why the ARCGIVER module cannot be
DFHSMDRAIN(YES) FORCED located, and make it available during server start-up.
If DFSMShsm is not installed, do not attempt to set the
DFHSM(YES) start-up option.
Explanation
AVZ0234E DFHSM INTERFACE DISABLED
More than 125 outstanding asynchronous HRECALL DUE TO STORAGE ALLOCATION
requests remain to be posted as complete by DFHSM. ERROR
The server is suspending DFHSM request processing.
It automatically set the DFHSMDRAIN product option
to YES, so that no new HRECALL requests are Explanation
scheduled until either (1) the number of pending During start-up, DFHSM(YES) was selected to initialize
HRECALL requests drops below 100 or (2) the DFHSM support. However, a storage acquisition error
DFHSMDRAIN or DFHSMSTATUS options are changed has occurred which will prevent the DFHSM interface
manually. from operating.

Check for reasons why DFHSM HRECALL processing Server start-up continues, but the DFHSM option is
may be delayed or disabled. Correct the DFHSM reset to NO, which prevents further DFHSM operations
problem, and then either wait for the server to from occurring. See preceding messages to determine
automatically set the DFHSMDRAIN(NO) option (once the actual cause of the problem.
25 requests have been completed and cleared
from the pending table) or manually change the AVZ0235I DFHSM support interface
DFHSMDRAIN parameter to NO. Before manually successfully initialized
changing DFHSMDRAIN to NO, ensure that fewer than
125 HRECALL requests remain outstanding. Explanation
AVZ0231E DFHSM INIT/TERM ROUTINE, During start-up, the DFHSM(YES) was selected to
OPINHS, ENTERED WITH INVALID enable DFHSM support. The server has pre-initialized
FUNCTION CODE: code its DFHSM support interface successfully.

During start-up or shutdown, the DFHSM service Server start-up continues. If DFHSM is not operational,
routine was entered with an invalid request code. the server may generate HRECALL requests
throughout its operation which will immediately fail.
User response If DFHSM is not actually installed, change the DFHSM
start-up parameter to NO to prevent enablement
This is a logic error. Contact Software Support for of DFHSM Support within the server. You may set
problem resolution. DFHSMSTATUS(OFFLINE) at any time to prevent the
AVZ0233E IBM-SUPPLIED DFHSM LOAD server from invoking DFHSM services until reset to
MODULE, ARCGIVER, NOT DFHSMSTATUS(ONLINE).
INSTALLED/LOCATED - DFHSM AVZ0236E ABEND DURING DFHSM
SUPPORT DISABLED service PROCESSING
- CMP=ccode,RS=rsncode, The table now has 25 free entries, and the server is
AT=modname+offset restoring normal HRECALL processing.

An abend was trapped during DFHSM processing. None. Normal HRECALL processing resumes.
Information about the abend is written to the console
log. AVZ0239I SHUTDOWN SUSPENDING FOR
UP TO sec SECONDS TO
AWAIT count1 PENDING HRECALL
User response COMPLETIONS - count2
The DFHSM interface retries, if possible, to prevent
subsystem termination or failure. Check for other Explanation
messages which might indicate the cause of the
problem. If the problem cannot be resolved, contact During shutdown processing, one or more pending
Software Support. HRECALL requests is still pending. The server will
pause to wait upon DFHSM to post these pending
AVZ0237W HRECALL PENDING FOR dsname requests complete. Shutdown processing will re-
- MWE ECB AT addr UNPOSTED - commence after pausing for DFHSM completion.
ORPHANED
User response
Explanation
None. The server waits the length of time specified by
During shutdown, an incomplete asynchronous DFHSM the DFHSMSHUTDOWNWAIT parameter for pending
HRECALL request was detected. The outstanding completions.
request will cause 352 bytes of below-the-line CSA
AVZ0240E count PENDING DFHSM REQUESTS
storage to be orphaned. This occurs because an
(AND MWE's) ORPHANED
outstanding HRECALL request causes an MWE ECB to
BECAUSE rsn
be allocated by DFHSM. The server is allowed to free
the ECB only after DFHSM has posted this ECB, which
it has not yet done; DFHSM does not automatically Explanation
free this storage when the requesting address space
During shutdown processing, one or more pending
terminates. Note that the orphaned CSA storage area
HRECALL requests MAY remain pending. However,
actually begins some number of bytes prior to the
the server is bypassing product termination-time final
ECB address given in this message (consult support
recovery, checking for these requests.
to determine the exact offset).

None. The server continues termination processing
Processing continues and the DFHSM MWE ECB
without attempting recovery/cleanup for pending
is orphaned. The server does not attempt to
HRECALL requests. Bypassing DFHSM final
remember these ECB addresses across a restart of
recovery is normally due to the parameter
the product. To prevent this condition, consider setting
DFHSMSTATUS(OFFLINE) having been explicitly set
the server's DFHSMSHUTDOWNWAIT parameter to
and left in effect during product termination. Be sure
allow a longer wait time limit for DFHSM hrecall
to restore DFHSMSTATUS(ONLINE) before product
completions during shutdown. Also, ensure that the
shutdown if DFHSM is actually online.
DFHSMSTATUS parameter has not been manually set
to OFFLINE, which inhibits waiting and cleanup of AVZ0250S service OF desc FAILED, RC=rcode
pending HRECALL requests.
AVZ0238I SERVER'S PENDING RECALL Explanation
TABLE NO LONGER FULL -
DFHSMDRAIN(NO) RESET TO NO
a wide variety of IMS initialization and termination
errors. The message text provides the current
Explanation operation (service) and what the current operation was
trying to do.
Earlier, the server had put DFHSMDRAIN(YES) into
effect because its pending HRECALL table was full.

Check the error messages and the return code Check the resource name in the error message. Set the
associated with this problem. There may be one or resource name using a product parameter.
AVZ0255H Build in-storage profile failed for
class class rcode1 rcode2 rsncode -
errmsg
AVZ0251S service PASSED desc - code Explanation
The product received a non-zero return code from a
Explanation
build in-storage profiles request for a specific class.
The message contains two return codes; rcode1
represents the security module return code, and
rcode2 represents the RACF (SAF) reason code.
operation (service) and what data (valid or invalid) was
passed to the current operation.
User response
User response Check the security error for the class. Correct the
problem, or contact your security administrator for
further assistance.
more error messages referring to the current problem. AVZ0261I Server will use default filetype
If possible, fix the problem identified by the error definitions for MIME CONTENT-
messages, and restart the product. If the problem TYPE mapping
AVZ0253S service TO desc FAILED, RC=rcode Explanation
FILETYPE table definitions were not provided explicitly
Explanation by the initialization procedure. In the absence of
ANY explicitly defined entries, the server generates a
default set of definitions.
operation (service) and what the current operation was User response
trying to do.
Normally, no action in required, and you may prefer to
use the built-in defaults provided by the server.
User response
AVZ0265E IDMS support cannot be enabled
Check the error messages and the return code - module IDMS-module-name not
associated with this problem. There may be one or found
If possible, fix the problem identified by the error Explanation:
messages, and restart the product. If the problem The CA IDMS load module was not found in the server
cannot be resolved, contact Software Support. started task JCL.
User response:
AVZ0254S IMS rsrc name missing
Add the CA IDMS load libraries into the STEPLIB of the
server started task JCL.
Explanation
AVZ0270T Access to ACI feature is not
A resource (rsrc) name needed by the IMS product configured.
feature is missing. The current operation will be
terminated. The message text contains the name of
Explanation
the missing resource.
None.
User response to the current SSL initialization problem. Check for
Contact Rocket Software Support. Also, check for storage allocation errors or abends.
AVZ0271W ACI internal service had to If possible, fix the problem identified by the error
GETMAIN buffers messages, and restart the product. If the problem
Explanation AVZ0281S SSL KEY/CERTIFICATE FILE func

ERROR, DD=ddname, RC=rcode
ACI internal services are supposed to use above
the bar buffer pools for storage. Some ACI services
were unable to obtain storage from the buffer pool Explanation
configured. As a result, it had to resort to GETMAIN The product tried to initialize SSL during product
services for buffers. initialization. SSL initialization failed because an error
occurred while accessing the server's private key or
User response certificate file.
Examine the buffer pool statistics to determine which
buffer pools need to be made larger. Also, be sure the User response
internal services are configured to appropriate buffer Check the error messages and the return code
pools. associated with this problem. There may be one or
AVZ0272I service errdesc, RC=rcode, more additional error messages or abends referring
RSN=rsncode, DETECTED AT addr to the current SSL initialization problem. Check for
Also, check for storage allocation errors or abends.
Explanation If possible, fix the problem identified by the error
ACI internal services initialization was unable to messages, and restart the product. If the problem
get large page storage for the ACI buffer pools as cannot be resolved, contact Software Support to
requested. obtain additional assistance.
AVZ0282S ABEND abcode OCCURRED AT
User response modname+offset DURING SSL desc
Allocate more storage for large pages to satisfy
the buffer pool requests. Standard page storage is Explanation
obtained instead. The product tried to initialize or terminate SSL
AVZ0273T additinfo1, additinfo2 … additinfo9 during product initialization or termination. The SSL
initialization/termination routine abended.
Explanation
User response
ACI tracing message. These messages will be
produced when ACITRACE is set to YES. Check the error messages and the abend code
User response the current SSL initialization or termination problem.
None. Check for open errors, such as security product
related abends. Also, check for storage allocation
AVZ0280S SSL msgtext errors or abends. If possible, fix the problem identified
Explanation the problem cannot be resolved, contact Software
Support.
The product tried to initialize SSL during product
initialization. SSL initialization failed. AVZ0283T SSL initialization complete

Check the error messages and the return code The product has completed SSL initialization. All
associated with this problem. There may be one or triggers and events will now be passed to the SSL for
more additional error messages or abends referring processing.

User response terminated abnormally or is hung. The product may or
may not be able to continue processing.
No action is required in response to this message.
However, this message can be used to activate one or
more event handling procedures. User response
AVZ0284S SSL user ID userID logon failed. Check for other abends or product messages related
to this one. If the problem cannot be resolved, contact
Software Support.
Explanation
AVZ0288S SSL SERVER PRIVATE KEY/
The SSL manager userid specified by the SSLUSERID CERTIFICATE FORMAT INVALID
system parameter, or the default server address space FOR ddname
userid failed logon processing during start-up.
Explanation
User response
The SSL resource manager could not initialize because
The HTTP-API initialization process is aborted. Ensure the server's private key or certificate file contains an
that the userid specified by the SSLUSERID start-up invalid key or certificate.
parameter is correct. Refer to message AVZ2107 for
more information about the failure.
User response
AVZ0285I SSL manager user ID userID
logged on to server. Check for other abends or product messages related
to this one. If the problem cannot be resolved, contact
Software Support.
Explanation
AVZ0289S SSL SUPPORT CANNOT BE
The SSL manager userid specified by SSLUSERID ENABLED - DDNAME ddname IS
system parameter has been logged on to the system. NOT ALLOCATED

HTTP-API initialization processing continues. The SSL resource manager could not initialize because
AVZ0286S service OF desc FAILED, RC=rcode the server's certificate or private key file ddname is not
allocated.
Explanation
User response
a wide variety of SEF execute queue initialization The server will terminate. Check the start-up JCL to
and termination errors. The message text provides ensure that the certificate file and/or private key files
the current operation (service) and what the current are allocated to the correct ddnames.
operation was trying to do. AVZ0290S SSL ERROR: msgtext

Check the error messages and the return code The SSL routines logged a severe error message.
If possible, fix the problem identified by the error User response
messages, and restart the product. If the problem The SSL routines logged a severe error to trace. The
cannot be resolved, contact Software Support. message is duplicated to the operator console.
AVZ0287S MAIN TASK TIMED OUT WHILE AVZ0291S SSL LDAP indicator NOT
WAITING TO BE POSTED BY THE SPECIFIED
subtask SUBTASK
Explanation
Explanation
SSL client authentication by an LDAP server was
The product main task timed out while waiting to be requested, but the name of the server or port
posted by an SSL subtask. The SSL subtask has either (indicator) number were not specified.
User response AVZ0321S Subroutine subrout at offset
offset1 in module modname is out
The server initialization process is aborted. Ensure of sequence and should be offset
that the correct server name and port number are offset2
specified with the SSLLDAPSERVER and SSLLDAPPORT
parameters.
Explanation
AVZ0292I GSK SSL SUPPORT CANNOT
BE ENABLED - SSLKEYPATH The subroutine is not defined in the correct position.
PARAMETER NOT SPECIFIED,
CHANGING TO SSLEAY SUPPORT User response
Contact Software Support to obtain assistance.
Explanation
AVZ0322S Vector and list table offsets for
The SSL resource manager could not initialize GSK subroutine subrout in module
SSL because the SSLKEYPATH parameter was not modname do not match
specified. GSK SSL requires this parameter. The
product will attempt to use SSLEAY SSL support.
Explanation
User response The offset into the vector table for the subroutine does
not match the offset defined in the list table.
The GSK SSL support will not be enabled. If possible,
SSLEAY SSL support will be used. If GSK SSL is
desired, code the SSLKEYPATH parameter and restart User response
the product. Contact Software Support to obtain assistance.
AVZ0293I A CALL TO THE SET_DUB_DEFAULT AVZ0323S Vector at offset offset in module
UNIX SYSTEM SERVICE FAILED. modname points to subrout1 but
RC=rcode RS=rsncode should point to subrout2
Product initialization received an error return code The subroutine pointed to by the list table is not the
from a call to the set_dbu_default service. one that was defined. The OPCOS% module vector
table entries do not agree with OPSBCL.
User response
Product initialization is terminated. Refer to the IBM User response
UNIX System Services Messages and Codes manual Contact Software Support to obtain assistance.
for an explanation of the return and reason codes. It
is possible that an OMVS segment was not created AVZ0324I service OF desc FAILED, RC=rcode,
for the product USERID. Refer to the the product REASON=rsncode, DETECTED AT
Server Installation Guide for more information on addr
creating the product USERID and the security that the
USERID requires. If the problem cannot be resolved, Explanation
then contact Software Support to obtain additional
assistance. An attempt was made to use zEDC services for
compression. If no zEDC engine was available or zEDC
AVZ0320S Subroutine subrout was found is not configured, this message may appear.
in modname1 but belongs in
modname2 at offset offset
User response
Explanation If zEDC compression is not required, this message may
be ignored. Otherwise, the return code and reason
The subroutine definition is in the wrong module. code will indicate the problem using zEDC.
AVZ0325I service OF desc SUCCEEDED,
User response DETECTED AT addr
Contact Software Support to obtain assistance.

Explanation and termination errors. The message text provides
A succeeded for zEDC services for compression. zEDC operation was trying to do.
services are now available for use.
User response
User response
None. associated with this problem. There may be one or
AVZ0326T additinfo1, additinfo2 ... more error messages referring to the current problem.
additinfo3, PGM=%SK If possible, fix the problem identified by the error
cannot be resolved, contact IBM Software Support.
Explanation
AVZ0337E desc service ERROR RC=rcode
A zEDC function call was made. The results are traced.
Explanation
User response
Some type of process block pool error occurred
None. during product initialization or product termination.
AVZ0334I STOP command detected during The message text provides the current operation
initialization (service) and what the current operation was trying to
do.
Explanation
User response
A STOP command has been detected by the product
during early product initialization. The initialization Check the error messages and the return code
exec (SxxxxIN00) may or may not have completed associated with this problem. There may be one or
successfully. STOP commands issued after the more error messages referring to the current problem.
completion of the initialization exec will not be If possible, fix the problem identified by the error
honored until initialization has completed. messages, and restart the product. If the problem
User response AVZ0338S INVALID desc LOCATED AT addr
TAG IS tag
AVZ0335S ESTAE service ERROR RC=rcode Explanation
The product found an invalid control block during
Explanation product termination. The control block tag (tag)
The product tried to create an ESTAE recovery contained an invalid character string.
environment. The ESTAE macro (service) failed.
User response
User response Check the error messages associated with this
Check the error messages and the return code problem. There may be one or more error messages
associated with this problem. There may be one or referring to the current problem. If possible, fix
more ESTAE error messages referring to the current the problem identified by the error messages,
problem. If possible, fix the problem identified by and restart the product. If the problem cannot
the error messages, and restart the product. If be resolved, contact Software Support to obtain
the problem cannot be resolved, contact Software additional assistance.
Support. AVZ0339E count process block(s) still in use
AVZ0336S service of desc failed, RC=rcode.
Detected at addr. stack: stkinfo. Explanation
The product uses a pool of stack control blocks to
Explanation process messages and other events. The stack blocks
This is a generic error message used to describe are obtained and released as required by a variety of
product routines. In some cases, a product routine Explanation
may fail to release a process block.
None.
User response
User response
No action is required to resolve this problem. The
product will release all of the space used by the stack Contact Rocket Software Support.
control blocks even if they appear to still be in use. AVZ0344T %PM configuration needs refresh
If the problem cannot be resolved, contact Software on this system.
Support.
AVZ0340I msgtext Explanation
None.
Explanation
This message is not an error message. The current User response
message is used to display the output from the
product initialization exec (SxxxxIN00) on the system Contact Rocket Software Support.
consoles. AVZ0345S DD allocation required in start-up
JCL for proper execution of TSO/E
User response REXX procedures.
Although the current message is not an error message,

the output from the product initialization exec is Explanation
only sent to the product consoles if the initialization The server is attempting to intercept output from a
exec terminates with a non-zero return code. The TSO/E REXX procedure but could not open the output
exec messages should be carefully checked for any data set to which TSO/E REXX routes SAY statement
error messages. Restart the product, if necessary. and other output messages are directed. The most
Contact Software Support if the problem (non-zero likely cause is that a site modification has been made
exec termination code) recurs. to IRXPARMS that specifies that TSO/E REXX should
AVZ0341T %PM feature codes are not set use a non-standard ddname for output. SYSTSPRT, the
- contact Software Support for IBM default, is assumed if the server is unable to load
assistance and check the IBM-supplied load module, IRXPARMS.

Review the messages just before and after this Ensure that the ddname indicated in the message
message to understand the context. is pre-allocated by the server's start-up JCL. (The
product-supplied sample JCL contains a SYSTSPRT
DD statement which can be used as a model for
User response pre-allocating this data set.) If a DD statement is
Contact Rocket Software Support. already present in the start-up JCL, ensure that
this ddname has not been released through the use
AVZ0342T %PM is running on an of an MVS DYNALLOC dynamic allocation request.
unconfigured CPU. This condition, if encountered while processing
the SWSxIN00 parameterization procedure, will not
Explanation result in server termination. However, any errors
encountered while executing this procedure cannot be
None. successfully reported.
AVZ0346I NETWORKBUFFERSIZE value
User response inadequate for SQLMAXCOLUMNS
Contact Rocket Software Support. value, raised to val
AVZ0343T %PM configuration will need

refresh in x days. Explanation
The NETWORKBUFFERSIZE must be adequate to
hold an SQLDA with the maximum number of

columns allowed, as specified by SQLMaxColumns. operation (service) and what the current operation was
The exact formula is: NETWORKBUFFERSIZE >= trying to do.
SQLMaxColumns * 44 + 16
User response
User response
The NETWORKBUFFERSIZE is raised to the size associated with this problem. There may be one or
computed by the above formula and then rounded to a more error messages referring to the current problem.
1K (1024) byte boundary. If possible, fix the problem identified by the error
AVZ0347I DSNREXX DB2 REXX INTERFACE cannot be resolved, contact Software Support.
NOT FOUND, ADDRESS DSNREXX
SUPPORT NOT ACTIVATED AVZ0351S service PASSED desc - code
The load module DSNREXX for REXX interface to Db2 This is a generic error message used to describe
was not found. Support for this API is not activated. a wide variety of CICS initialization and termination
Initialization continues normally. errors. The message text provides the current
operation (service) and what data (valid or invalid) was
User response passed to the current operation.
Support for ADDRESS DSNREXX is not enabled. This

User response
is not necessarily an error, unless DSNREXX support is
needed. Check the error messages and the return code
AVZ0348S Invalid registry block ivdata found
in logstream logstream
Explanation cannot be resolved, contact Software Support.
The Registry Logstream contained a block which did AVZ0352W modname is not REENTRANT
not pass validation (ivdata). The record is dropped,
and will be deleted at the next update.
Explanation
User response The product found that the EXCI options module
DFHXCOPT or its alias DFHXCOPE is not REENTRANT.
Make a copy of the next Offload dataset for this This will cause some EXCI related product parameters
logstream and send it to Software Support. to be ignored - for example the TIMEOUT parameter.
AVZ0349I regtype REGISTRY LOGSTREAM
logstream action User response
Relink the module with the RENT option.
Explanation
AVZ0353S service TO desc FAILED, RC=rcode
The Registry Logstream was created, deleted, or
connected (action) to as part of initialization.
Explanation
User response This is a generic error message used to describe
a wide variety of CICS initialization and termination
None, this is normal processing. errors. The message text provides the current
operation (service) and what the current operation was
trying to do.

wide variety of CICS® initialization and termination
cannot be resolved, contact Software Support. Follow the course of action recommended for the error
messages which preceded this error message, and if
AVZ0354S CICS rsrc NAME MISSING the product EXCI support continues to terminate due
to a fatal error condition, contact Software Support for
Explanation further assistance.
A resource (rsrc) name needed by the CICS product AVZ0358I EXCI support activated
terminated. The message text contains the name of Explanation
the missing resource.
This message is issued when the product EXCI server
has received a notification that the connection(s) to
User response the EXCI region(s) have been established successfully.
Check the resource name in the error message. Set the
resource name using a product parameter. User response
AVZ0355I CICS support terminating No action required. This is an informational message
only.
Explanation AVZ0359T msgtext
This is an informational message that is issued when
the product terminates its CICS support. If the CICS Explanation
support is being terminated due to a fatal error
condition, this message will have been preceded by This is a general purpose message that may or may not
error messages which depict the exact error condition indicate some type of EXCI error.
encountered.
User response
User response Read the message text carefully. Some messages
Follow the course of action recommended for the error produced under this message ID are actually error
messages which preceded this error message, and if messages. If the message indicates an error, check
the product CICS support continues to terminate due for any associated EXCI-produced error messages. If
to a fatal error condition, contact Software Support for the problem cannot be resolved, contact Software
further assistance. Support.
AVZ0356I CICS support activated AVZ0360S No matching CONNECTION name

rsrc for DEFINE SESSION
Explanation
Explanation
This message is issued when the product CICS server
has received a notification that the connection(s) to A DEFINE SESSION statement in the initialization exec
the CICS region(s) have been established successfully. specified a CONNECTION name for which there is no
corresponding DEFINE CONNECTION statement. The
message text contains the name of the erroneous
User response DEFINE SESSION name.
No action required. This is an informational message
only. User response
AVZ0357I EXCI support terminating Check the session name in the error message. Correct
the DEFINE SESSION statement.
Explanation AVZ0361I %1 of %2 sessions connected to
This is an informational message that is issued when %3
the product terminates its EXCI support. If the EXCI
support is being terminated due to a fatal error Explanation
condition, this message will have been preceded by
error messages which depict the exact error condition This message specifies the number of active sessions
encountered. to the specified CICS.

None. This message is for informational purposes only. An error occurred in the CSQCAPX CICS MQSERIES
API Crossing Exit for Actional Agent connector.
AVZ0362I No active session to %1
User response
Explanation
The exit should have disabled itself. Contact Rocket
This message specifies that there is currently no active Software Support..
session to the specified CICS.
AVZ0373E SDAITRUE %1
User response
Explanation
An error occurred in module SDAITRUE, the CICS
AVZ0363T Acquisition of session to %1 failed TRUE for Actional Agent connector.

Acquisition of a session failed. This may not be an The exit should have disabled itself. Contact Rocket
error. Software Support..
User response AVZ0380T ABEND IN REXXTOOLS DYNALLOC

INTERCEPT CMP=ccode,
Review the messages just before and after this RS=rsncode, SVC-99-PLIST=addr
AVZ0364I SDCITRU IS STARTED AND Explanation
ENABLED An unexpected abend has occurred within the
REXXtools dynamic allocation interception/screening
Explanation routine.
The CICS Task Related User Exit For Broker is started
and enabled in the CICS region. User response
The abend is percolated for handling by REXXtools.
User response
AVZ0381T ADD REXX VARIABLE NAME
None. This message is for informational purposes only. FAILED WITH RETURN CODE
rcode, REASON CODE rsncode FOR
AVZ0371E func ROUTINE ERROR - error
NAME varname
additinfo1, additinfo2 ... additinfo7
Explanation
Explanation
An error occurred when attempting to create a variable
An error or unexpected condition was detected in an
name for a REXX procedure. This will be followed by an
Actional support facility routine (func).
S0C3 abend.

For initialization error, the server will terminate. For
Check the variable name to be sure it is valid, or
termination time errors, server shutdown continues.
increase the workspace for this REXX procedure.
Look for related messages indicating the cause of
the error and correct the underlying problem. Contact AVZ0388I It contains additional diagnostic
Software Support if the problem cannot be found or information about the failure.
corrected.
AVZ0372E CSQCAPX %1 Explanation
This message provides information to help you
diagnose the problem.
Check the error messages and the return code The named-token return code is sent to the routine
associated with this problem. There may be one or which requested the service, and processing continues
more error messages referring to the current problem. as dictated by the routine which requested the server.
AVZ0391E func ROUTINE ERROR: error
additinfo1, additinfo2 ... additinfo7
The variable fields of the message text are: request
Explanation
request type func function that failed rc function return
code rscd function reason code An error or unexpected condition was detected in a
Services support facility routine.
AVZ0388E DYNAMIC LPA reqtype SERVICE
FAILED FOR modname.
RETURN CODE=rcode. REASON User response
CODE=rsncode. For initialization error, the server will terminate. For
Explanation Look for related messages indicating the cause of
the error and correct the underlying problem. Contact
An error occurred when attempting to use MVS
Software Support if the problem cannot be found or
dynamic LPA services, CSVDYLPA. The request type,
corrected.
return code and reason code associated with this
failure are listed in this message. AVZ0392W func ROUTINE WARNING: error
additinfo1, additinfo2 … additinfo7
User response
Explanation
associated with this problem. There may be one or An unexpected condition was detected in a Services
more error messages referring to the current problem. support facility routine.
User response
For initialization error, the server attempts to correct
AVZ0389E DYNAMIC LPA reqtype the condition and continue. Errors detected during
FUNCTION=func RC=rcode termination are bypassed.
RS=rsncode
AVZ0393S Services PARM parmname
Explanation additinfo1, additnfo2 ... additinfo7
This message is a continuation of message

Explanation
User response:
A Services configuration startup parameter is missing
No action is required.
or incorrectly set. Services will substitute a corrected
AVZ0390E NAMED-TOKEN service SERVICE value, if possible, and activate with the updated
ERROR: RC=rcode FOR LVL=tlvl, value. If no default value can be substituted, Services
NAME=tname, DATA=tdata, activation will terminate server start after issuing
POPT=topt MSG0391E.

An unexpected return code was set after a system- Check to ensure the z/Server-related parameter
managed named token service request. The service identified in the message is being set to a valid value
type, return code, token level, token name, token data, during SxxxxIN00 processing. Restart the server.
and token persistence option are displayed in the
AVZ0394S SERVICES MAILBOX CONTROL
message.
rout FAILED: HASN=asid1,
PASN=asid2, SASN=asid3,
MODE=mode, RC=rcode,
CALLER=csect, LT=ltype

During an attempt to execute a Services mailbox The pointer is rejected as invalid, and the mailbox
request, a failure in the lock or unlock (rout) request will either fail the overall request, or complete
serialization routine was encountered. The current its operation without using the rejected pointer. Check
mailbox execution request will be abandoned and for other messages which might indicate the cause
failed. In the message, the return code field will of the error, and contact Software Support for further
contain a non-zero value in byte 3 if the SETLOCK or assistance.
ENQ service failed. It will contain a non-zero value in
bytes 1 or 2 for environmental errors. AVZ0397T func ROUTINE ERROR: error
additinfo1, additinfo2 … additinfo7
The message contains three asid values: home asid
(asid1), primary asid (asid2), and secondary asid
Explanation
(asid3).
An error or unexpected condition was detected in
mode may be "PROB" or "SUP"
a Services support facility routine. This message is
written to Trace Browse to record the same condition
User response also written to the console by MSG0391E.
The current Services mailbox request is failed. Check
for other messages which might indicate the cause User response
of the error, and contact Software Support for further
For initialization error, the server will terminate. For
assistance.
AVZ0395E SERVICES MAILBOX REQUEST Look for related messages indicating the cause of
reqtype ABEND ccode (rsncode) the error and correct the underlying problem. Contact
AT modname+offset additinfo1 Software Support if the problem cannot be found or
additinfo2 additinfo3 additinfo4 corrected.
AVZ0398T func ROUTINE WARNING: error
Explanation additinfo1 additinfo2 … additinfo7
During an attempt to execute a Services mailbox
request, an ABEND failure was detected. The request Explanation
is rejected with a return code indicating that an abend
An unexpected condition was detected in a Services
occurred.
support facility routine. This message is written to
reqtype may be "SYSTEM" or "USER" Trace Browse to record the same condition also
written to the console by MSG0392W.
User response
User response
The failure is reflected to the requesting task, which
then takes whatever action is appropriate to the For initialization error, the server attempts to correct
situation. Check for other messages which might the condition and continue. Errors detected during
indicate the cause of the error, and contact Software termination are bypassed.
Support for further assistance.
AVZ0399T Services E-O-T cleanup for TCB
AVZ0396T SERVICES MAILBOX INVALID addr RC=rcode RS/CC=rsncode/
POINTER (addr/ALET/storlgth) ccode FDBK=feeback1, feedback2
DURING PKM AUTH CHECK - … feedback5
ABEND ccode (rsncode)
Explanation
Explanation
Services End of Task cleanup has been processed for
While validating a mailbox request, Services routines the ending task. The message is traced if a non-zero
detected an invalid address passed as part of the return code is set by the cleanup function, or when the
request. The ABEND was detected while attempting ZSRMBOXTRACECMTC option is on.
to examine the protect key of the storage area.
User response If possible, fix the problem identified by the error
If the message reports a non-zero return code, look cannot be resolved, contact Software Support.
for other conditions which may be inhibiting E-O-T
cleanup and correct. Or contact Software Support. AVZ0403S RRS rsrc NAME MISSING

Explanation
Explanation A resource (rsrc) name needed by the RRS product
This is a generic error message used to describe terminated. The message text contains the name of
a wide variety of RRS initialization and termination the missing resource.
operation (service) and what the current operation was
trying to do. User response
Check the resource name in the error message. Set the
User response resource name using a product parameter.
Check the error messages and the return code AVZ0404I RRS support terminating
messages, and restart the product. If the problem This is an informational message that is issued when
cannot be resolved, contact Software Support. the product terminates its RRS support. If the RRS
support is being terminated due to a fatal error
AVZ0401S service PASSED desc - code condition, this message will have been preceded by
error messages which depict the exact error condition
Explanation encountered.

a wide variety of RRS initialization and termination User response
errors. The message text provides the current Follow the course of action recommended for the error
operation (service) and what data (valid or invalid) was messages which preceded this error message, and if
passed to the current operation. the product RRS support continues to terminate due
to a fatal error condition, contact Software Support for
User response further assistance.
Check the error messages and the return code AVZ0405I RRS support activated
messages, and restart the product. If the problem This message is issued when the product RRS server
cannot be resolved, contact Software Support. has received a notification that the connection(s) to
the RRS region(s) have been established successfully.
AVZ0402S service TO desc FAILED, RC=rcode
User response
Explanation
a wide variety of RRS initialization and termination AVZ0406H msgtext
operation and what the current operation was trying Explanation
to do.
This is a general purpose message that may or may not
indicate some type of RRS error.
User response
Check the error messages and the return code User response
more error messages referring to the current problem. Read the message text carefully. Some messages
produced under this message ID are actually error

messages. If the message indicates an error, check Explanation
for any associated RRS produced error messages. If
the problem cannot be resolved, contact Software This message is issued when RRS alerts the product
Support. that the product RRS exits have become unset due to
some error condition. This causes the product to lose
AVZ0407E Failure trying to register with RRS its connection to RRS. RRS support and two-phase
commit support will not be available.
Explanation
This message is issued when the RRS Register
User response
Resource Manager call is unsuccessful. The product This indicates an error that should not occur. Contact
is unable to use RRS services, and two-phase commit Software Support.
support is disabled.
AVZ0411E TRANS: token FROM host -
REQUESTED ind1 BUT WAS
User response HEURISTICALLY ind2
Ensure that RRS is functioning correctly.
AVZ0408E ERROR SETTING RRS EXITS,
Explanation
CHECK RRS STATUS The portion of a distributed transaction that ran under
the product on z/OS was committed or rolled back
Explanation heuristically manually or by a program - but not by
the client-side transaction manager. The transaction
This message is issued when the RRS Set Exit manager has just informed the product that it wanted
Information call is unsuccessful. This usually indicates the transaction rolled back or committed. The data
that the RRS subsystem is not up and running. The involved in the transaction may now be in an
product will attempt to establish its RRS exits when it inconsistent state (partially committed and/or partially
hears from RRS that it is up and running. RRS support rolled back).
and two-phase commit support will not be available
until the product can successfully connect to RRS. ind1 indicates "COMMIT" or "BACKOUT", and ind2
indicates "COMMITTED" or "BACKED OUT"
User response
User response
Ensure that the RRS subsystem is up and running. If
the RRS subsystem is not up and running, start it. This situation may need to be corrected manually.
The data that was committed on MVS may need
AVZ0409E RRS %1 EXIT MANAGER to be backed out, and the data sources may need
UNAVAILABLE to be restored to their state before the transaction.
Note that the committed data may have already been
Explanation accessed by later programs and transactions.
This message is issued when RRS alerts the product AVZ0413E THE DB2ATTACHFACILITY
that an IBM exit manager for RRS has become PARAMETER IS NOT SET
unavailable. This causes the product to lose its TO RRSAF, RRS SUPPORT
connection to RRS immediately. The product will try TERMINATED'
to reconnect again when it hears RRS is up and
running. RRS support and two-phase commit support Explanation
will not be available until the product can successfully
reconnect to RRS. The product DB2ATTACHFACILITY must be set to use
the Recoverable Resources Attach Facility (RRSAF) for
RRS support to work properly.
User response
Ensure that the RRS subsystem is up and running. If User response
the RRS subsystem is not up and running, start it.
Modify the product parameter data set member.
AVZ0410E Product RRS exits have been unset
AVZ0414E RRS RECOVERY TABLE SIZE
EXCEEDED - TRANSACTION
ABORTED'
The RRS Recovery Table size was exceeded. A The RRS parameter was set to NO, or RRS initialization
transaction was aborted, which will be indicated in failed. Two-phase commit cannot be supported unless
another message. RRS is active.

Increase the number of entries in the RRS Check the joblog for RRS initialization error messages
Recovery Table, specified by the product parameter and correct any problems. Then, restart this server
RECTABLEENTRIES. If this parameter is not specified, with the RRS parameter set to YES.
the value defaults to 400 entries.
AVZ0421E ERROR IN TWO-PHASE indicator
AVZ0415E Incompatible supplied driver on PROCESS. RRS RETURN CODE =
client system - transaction aborted rcode
An incompatible product-supplied driver was Two-phase commit was requested for all transactions
encountered on the client system. from this task. RRS returned an error code indicating
that the commit was not successful.
User response indicator indicates "COMMIT" or "BACKOUT"
Contact Software Support.
User response
AVZ0416E ZERO COLUMNS RETURNED FROM
PREPARE - ERROR IN SYSTEM Check the return code from the RRS ATRCMIT function
in the IBM manual titled z/OS Programming: Resource
Recovery.
Explanation
AVZ0422E RRS RECOVERY TABLE COUNT
Zero columns were returned from PREPARE. This is
NEGATIVE, RESET TO ZERO
most likely due to an error in z/OS, RRS, and/or Db2.

The RRS Recovery Table entry count was found to be
Contact Software Support for the latest information
negative during XA-RECOVER processing. The entry
regarding how to bypass this problem.
count was reset to zero.
AVZ0417E RRS IS NOT ACTIVATED FOR
THIS SERVER - XA TRANSACTION User response
ABORTED.'
There may be some XA transactions that were left in
an incomplete state, leftover from a communication
Explanation
line disconnect or host system crash.
When this server was initialized, either it was not
AVZ0423T Access to data sources through
instructed to activate an RRS connection or the
Enterprise Transactions is not
initialization for connection failed.
configured.
User response
Explanation
If the initialization parameters specify that RRS is
None.
to be activated, review the messages created when
this server was initialized and correct any associated
problems. User response
AVZ0420E TWO-PHASE COMMIT SUPPORT Contact Rocket Software Support.
WAS REQUESTED, BUT RRS IS
AVZ0424E TWO-PHASE COMMIT SUPPORT
NOT ACTIVE
WAS REQUESTED, BUT THE RRS
MANAGER WAS NOT ACTIVE

RRS was requested, but RRS was not active. Check to be sure that the IBM RRS facility is active and
not generating errors.
User response AVZ0480S MQSERIES support deactivated -
Check the joblog for messages related to RRS access routines cannot be loaded.
initialization. Correct the initialization errors and
restart this server. Explanation
AVZ0425E IBM/MQSERIES/RRS SUPPORT During initialization MQSERIES access modules could
ENTRY entry IN MODULE modname not be loaded from either AVZMQSLB or STEPLIB.
MISSING
User response
Explanation
The server deactivates MQSERIES support and
An IBM/MQSeries support entry was missing from continues start- up processing. Check to ensure you
the module specified. There is an incompatibility have an AVZMQSLB DD JCL statement in the server
between the MQSeries® library provided and product start-up JCL.
MQSeries/RRS support.
AVZ0500E IBM-assigned CSR table entry
setup error, contains val, not
User response product OPVN pointer
Ensure that the library provided is the standard IBM
library. If the problem cannot be resolved, contact Explanation
Software Support.
During initialization, the product Vendor Vector Table
AVZ0426S IBM/MQSERIES/RRS SUPPORT entry contained an invalid value (val). The assigned
MODULE modname MISSING - NO fullword contains a value which does not address
TWO-PHASE COMMIT SUPPORT the product OPVN control block. The IBM-assigned,
PROVIDED entry in the table is located at decimal offset 184,
hexadecimal offset B8 of the vector table addressed
Explanation by ECVTCTBL. The fullword value at that location
contained a non-zero value that did NOT point to
The specified IBM/MQSeries support module is an already established product OPVN control block.
necessary for two-phase commit support for The product cannot initialize without establishing the
MQSeries. Processing will continue without MQSeries OPVN block pointer. The existing value in the vector
two-phase commit support. table fullword is saved and overlaid with the product
OPVN block address.
User response
User response
Check the IBM/MQSeries library, defined in the
product JCL procedure. It may be an old version. Determine who/what is responsible for creating the
invalid entry in the table, clear the word to x'00's,
AVZ0428T CREATION OF RRS PRIVATE
and restart the product. Caution should be used when
CONTEXT FAILED - CONNECTION
deciding to clear the entry. Most likely, another ISV has
TERMINATED. CALL: calltype -
inadvertently used this entry; clearing it to 0's could
R15: rcode - R0: rsncode
cause problems for some other product.
Explanation AVZ0501E service OF desc FAILED, RC=rcode
With the product RRS support active and Private

Explanation
Contexts selected, the product creates an RRS Private
Context immediately when the session connects. The This is a generic error message used to describe a
RRS calls to do this failed. variety of Server initialization and termination errors.
The message text provides the information about the
current operation.
Check the error messages and the return code None.
more error messages referring to the current problem. User response
messages, and restart the product. If the problem Contact Rocket Software Support.
AVZ0507E %1 product PC reset failed.
AVZ0502E subsys directory table entry exists.
Explanation
Explanation
None.
During initialization, the server directory table was
found to contain an entry with the same subsystem ID User response
as the one being started. Most likely, a server address
space is active on this MVS image with this subsystem Contact Rocket Software Support.
name.
AVZ0508E %1 server software PC entry
unknown.
User response
Determine if a server address space is currently Explanation
active with this subsystem name. If so, change the
None.
subsystem name and restart (if it is necessary to start
another server address space). If the problem cannot
be resolved, contact IBM Software Support.. User response
AVZ0503E No ERLY exists for DB2 %1 Contact Rocket Software Support.
AVZ0509E %1 DB2 server init error.
Explanation
None. Explanation
None.
User response
Contact Rocket Software Support. User response
AVZ0504E %1 DB2 owned by another server. Contact Rocket Software Support.
AVZ0510E %1 DB2 server %2 error.
Explanation
None. Explanation
The server main task for the named Db2 system
User response encountered an error from the common subroutine.
Either ECB WAIT or STIMER.
AVZ0505E %1 DB2 search error. User response
Explanation
AVZ0511E %1 DB2 SSCTSUSE ERROR,
None.
Explanation
User response
None.
AVZ0506E %1 server software PC reset User response
failed.

AVZ0512I %1 DB2 main task PC reset error. User response
Explanation
AVZ0518E TERMINATION WAITING ON DB2
None. STATUS TASK FOR %1

Contact Rocket Software Support. None.
AVZ0513I %1 product main task TERM PC
error User response
Explanation
AVZ0519E maximum number of server
None. address spaces are already active.
max possible %1. currently active
User response %2.

Explanation
AVZ0515E MAXIMUM NUMBER OF DB2
SUBSYSTEMS PREVIOUSLY None.
DEFINED. MAX = %1. DEFINE FOR
DB2 SSID %2 IGNORED. User response
Explanation
AVZ0520E Maximum number of DB2 systems
During initialization, the input parameter data set are all ready active. max possible
contains more Db2 subsystem statements than the %1. DB2 %3.
maximum allowable set by default or by QSMAXDB2.
Explanation
User response
The maximum number of subsystems allowed by the
All parameter statements pertaining to this Db2 server are already active.
subsystem are ignored.
AVZ0516E DUPLICATE DB2 SUBSYSTEM User response
DEFINITION FOR DB2 SSID %1
Edit the server configuration file, and reduce the
number of database definitions in the file.
Explanation
AVZ0521S DB2 subsysid STATUS TASK
During initialization, the input parameter data set ABEND abcode AT modname+offset
contains more than one DEFINE for the same Db2 DURING desc.
subsystem ID.
Explanation
User response
None.
All parameter statements within the subsequent
DEFINE for this Db2 are ignored.
User response
AVZ0517E RETURN CODE %1 FROM ALESERV
ADD OF DB2 DBM1 FOR %2 Contact Rocket Software Support.
AVZ0522W Proprietary R&&D utilities are
Explanation activated for this start-up
None.
Explanation termination errors. The message text provides the
current operation and what the current operation was
This warning indicates that private R-and-D utility trying to do.
functions are activated within the system. Customer
copies of the product should never produce this
message during start-up processing. User response
User response associated with this problem. There may be one or
If this message appears during start-up, terminate the If possible, fix the problem identified by the error
server and contact Software Support. The execution messages, and restart the product. If the problem
of internal developer utilities off-site may produce cannot be resolved, contact Software Support.
damaging side effects.
AVZ0602I IMS/OTMA server waiting OTMA
AVZ0523W E/SQA ROUTINE AT addr WILL BE INIT for IMS SSID=subsys
REBUILT DUE TO INVALID PTR OR
DATA
Explanation
Explanation This message indicates that the IMS/OTMA
Transaction Server is waiting for initialization of
This warning indicates that the special E/SQA-resident the selected IMS subsystem. This message is
SRASTC routine will be rebuilt. The existing pointer to informational and issued periodically when OTMA
the routine, or the routine itself, appears to have been support is waiting for IMS subsystem startup to occur.
damaged.
User response
User response
Determine why the IMS subsystem is unavailable.
Start-up processing clears the existing pointer and Start the IMS subsystem to allow OTMA support to
builds a new copy of the needed routine into E/SQA be enabled. If this message is issued in error, contact
storage. The storage, if any, previously anchored by Software Support.
the OPVN vendor CSR table control block is orphaned.
Contact Software Support. AVZ0603I IMS/OTMA server INIT in progress
for IMS SSID=subsysID
AVZ0600S IMS/OTMA XCF reqtype FAILED,
RC=rcode RS=rsncode IMS=imsID
Explanation
Explanation This message indicates that the IMS/OTMA
Transaction Server initialization is in progress for the
This is a generic error message used to describe selected IMS subsystem.
a wide variety of IMS/OTMA initialization and
current operation and what the current operation was User response
trying to do. None. This message is for informational purposes only.
AVZ0604I IMS/OTMA server INIT complete
User response for IMS SSID=imsID using XCF
Check the error messages and the return code member xcfID
messages, and restart the product. If the problem This message indicates that the IMS/OTMA
cannot be resolved, contact Software Support. Transaction Server initialization has been successfully
completed for the selected IMS subsystem.
User response
Explanation
a wide variety of IMS/OTMA initialization and

AVZ0605I IMS/OTMA server has detected User response
OTMA TERM for IMS
SSID=subsysID Examine the Trace Browse and JES joblog to
determine why the ABEND occurred. If the problem
Explanation
AVZ0620S SIS/XCF XCF reqtype FAILED,
This message indicates that the IMS/OTMA RC=rcode RS=rsncode SIS=ID
Transaction Server has detected IMS terminating
OTMA support. This message is issued when it has
been determined that IMS is leaving the XCF OTMA Explanation
group. This may be due to IMS termination, a /STOP This is a generic error message used to describe a
OTMA command, or OTMA abnormal termination. The wide variety of SIS/XCF initialization and termination
product IMS/OTMA server will wait for IMS to restart errors. The message text provides the current
OTMA support and continue processing OTMA request operation and what the current operation was trying
activity. to do.

None. This message is for informational purposes only. Check the error messages and the return code
AVZ0606I IMS/OTMA server TERM in associated with this problem. There may be one or
progress for IMS SSID=subsysID more error messages referring to the current problem.
This message indicates that the IMS/OTMA AVZ0621S service OF desc FAILED, RC=rcode
Transaction Server is terminating for the selected IMS
subsystem. This message is issued during product
termination. Explanation
User response wide variety of SIS/XCF initialization and termination
None. This message is for informational purposes only. operation (service) and what the current operation was
AVZ0607I IMS/OTMA server TERM complete trying to do.
for IMS SSID=subsysID
User response
Explanation Check the error messages and the return code
This message indicates that the IMS/OTMA associated with this problem. There may be one or
Transaction Server has completed termination for more error messages referring to the current problem.
the selected IMS subsystem. This message is issued If possible, fix the problem identified by the error
during product termination. messages, and restart the product. If the problem
User response AVZ0622T SIS/XCF member waiting SIS/XCF

%1 INIT for mbr=%2
AVZ0608S IMS/OTMA TPIPE TASK task Explanation
FOR CONNECTION conn ABENDED
CODE abcode This message indicates that the SIS/XCF Server is
waiting for initialization of the selected SIS subsystem.
This message is informational and issued periodically
Explanation when an SIS/XCF standard member is waiting for the
This message indicates that the IMS/OTMA SIS/XCF manager to initialize.
Transaction Pipe has ABENDED.
Determine why the SIS/XCF manager is unavailable. This message indicates that the SIS/XCF Server is
Start the SIS/XCF manager to allow SIS/XCF support terminating for the selected SIS subsystem. This
to be enabled. If this message is issued in error, message is issued during product termination.
AVZ0623I SIS/XCF %1 INIT in progress for User response
member=%2 None. This message is for informational purposes only.
AVZ0627I SIS/XCF %1 TERM complete for
Explanation
member=%2
This message indicates that the SIS/XCF Server
initialization is in progress for the selected SIS Explanation
subsystem.
This message indicates that the SIS/XCF Transaction
Server has completed termination for the selected
User response
SIS subsystem. This message is issued during product
None. This message is for informational purposes only. termination.
AVZ0624I SIS/XCF server INIT complete for
SIS SSID=sisID using XCF member User response
xcfID None. This message is for informational purposes only.
AVZ0701W ZIIPCLASS=class HAS TOO MANY
Explanation
PERIODS SPECIFIED
This message indicates that the SIS/XCF Server
initialization has been successfully completed for the Explanation
selected SIS subsystem.
This message indicates that WLM initialization found
too many matching report classes. Only six periods
User response
are allowed, and more than that matched the naming
None. This message is for informational purposes only. convention.
AVZ0625I SIS/XCF %1 instance has detected
termination of %2 instance User response
member %3 Delete the extra report classes.
AVZ0702W CLASS class1 SPECIFIES A
Explanation
ZIPCLASS NAME THAT DOES NOT
This message indicates that the SIS/XCF Transaction EXIST, class2
Server has detected SIS terminating SIS/XCF support.
This message is issued when it has been determined Explanation
that SIS is leaving the XCF OTMA group. This
may be due to SIS termination, or OTMA abnormal This message indicates that WLM initialization found a
termination. The SIS/XCF server will wait for SIS to class that referenced a ZIIPCLASS that could not be
restart SIS/XCF support and continue processing SIS found.
request activity.
User response
User response
Correct the indicated WLM Class to reference an
None. This message is for informational purposes only. existing WLM pseudo-class.
AVZ0626I SIS/XCF %1 TERM in progress for AVZ0703W ZIIPCLASS=class CONTAINS
member=%2 INVALID PARMS
Explanation
This message indicates that WLM initialization found a
ZIIPCLASS report class definition with invalid parms.

The description must contain a Pnnn percent definition AVZ0708R Reply 'GO' to update the WLM
and all but the last one must contain a Dnnnnnnn Service Definition, or 'CANCEL' to
duration. terminate server initialization

Correct the definition field of the ZIIPCLASS report This message is issued when product WLM
class definition. initialization is about to update the current WLM
service definition with the policy elements required for
AVZ0704H WLM refresh command completed
product server execution.

The WLM command has successfully completed,
Reply GO to allow the server to update the WLM
refreshing WLM data within the product.
service definition. Reply CANCEL to terminate server
initialization
User response
AVZ0709I WLM Service Definition def has
None. been updated with required
product elements
AVZ0706I product subsys requires the
following elements missing from
WLM Service type name Explanation
This message is issued when product WLM
Explanation initialization has updated the WLM service definition
(def) with the required product elements.
Product initialization detected that the current WLM
service policy does not have the all of the required
definitions for Version 7.1 of the product. Messages User response
listing the required service definition elements will
Respond to the WTOR prompts that follow this
follow this message.
message.
type may be "policy" or "definition"
AVZ0710E Invalid reply: reply. Reply 'GO' or
Consequently, name will be either a policy name or a 'CANCEL'
definition name
Explanation
User response
An invalid reply was specified to the server WLM
Respond to the WTOR prompts that follow these initialization console message.
messages.
AVZ0707I Type: PEtype, Server Parameter: User response
PEname, Value: parmname
Reply GO to cause the message to be reissued. Reply
CANCEL to terminate server initialization.
Explanation
AVZ0711E REPLY WAIT EXCEEDED 2
Generic message used by product WLM initialization to MINUTES. CANCEL ASSUMED
list elements missing from the WLM service definition.
The PE in this message's variables stands for Policy Explanation
Element
The product waited over two minutes for a reply to
parmname represents the IN00 parameter name the WLM initialization message. Since no response was
received during that time, CANCEL was assumed and
User response server initialization terminated.

User response
message.
None. If a reply was desired, you will need to speed
AVZ0712E 3 INVALID REPLIES. CANCEL AVZ0716R Enter name of Service Policy to
ASSUMED activate, 'LIST', or 'CANCEL' to
terminate server initialization
Explanation
Explanation
Three invalid replies were made to the product
WLM initialization message. Since no correct response This message is issued when product WLM
was received, CANCEL was assumed and server initialization has updated the Service Definition and
initialization terminated. needs to know which Service Policy should be
activated.
User response
User response
None. Reply as required next time.
Enter a name to activate Service Policy with that name.
AVZ0713S WLM administration user ID Reply LIST to get a list of available Policies. Reply
userID logon failed. CANCEL to terminate server initialization
Explanation AVZ0717I The following Service Policies are

available for activation
The WLM admin user ID specified by the WLMUSERID
system parameter failed logon processing during start-
Explanation
up.
User response initialization is about to list the Service Policies defined
in the current Service Definition.
The server initialization process is aborted. Ensure
that the user ID specified by the WLMUSERID start-
User response
up parameter is correct. If possible, fix the problem
identified by the error messages and restart the Respond to the WTOR prompts that follow this
product. If the problem cannot be resolved, contact message.
IBM Software Support.
AVZ0718I Policy: policyname - policydesc
AVZ0714I WLM administration userid userID
logged on to system Explanation
Generic message used by product WLM initialization to
Explanation
list Service Policies available for activation.
The WLM admin userid specified by the WLMUSERID
system parameter has been logged on to the system. User response
User response
message.
Server initialization processing continues.
AVZ0719R Reply 'GO' to activate Policy %1,
AVZ0715I WLM Service Definition definition or 'CANCEL' to terminate server
does not contain current Service initialization
Policy policy
Explanation
Explanation
This message is issued when product WLM initialization has updated the WLM service definition
initialization is has updated the WLM service definition with the named service policy.
and has determined that it does not contain the
currently active service Policy. User response
Reply GO to allow the server to activate the service
User response
policy. Reply CANCEL to terminate server initialization
Respond to the WTOR prompts that follow this 1 = policy name of WLM policy to be created
message.

AVZ0720S WLM reset to service class class timeouts are measured. If the health value increases,
failed for job jobname subsystem this is an indication that no further failures have been
subsys ASID asid detected, and the product is returning to full health.
The variable fields of the message text are: subsystem
Explanation the WLM subsystem type oper1 the old health value
oper2 the new health value reason reason description
The server WLM initialization failed to reset the service
class for the server. AVZ0725I RACF administration USERID
userID logged on to system
User response
Explanation
Look for preceding error messages in the system log.
The RACF admin USERID specified by the SERVERID
AVZ0721I WLM classify successful for
system parameter has been logged on to the system.
transaction - Service Class class
User response
Explanation
Server initialization processing continues.
The server WLM enclave classification was successful.
AVZ0726S RACF administration USERID
User response (userID) logon failed
None.
Explanation
AVZ0722I Unable to classify transaction
The RACF admin USERID specified by the SERVERID
trans for subsystem subsys
system parameter failed logon processing during start-
up.
Explanation
The server was unable to classify the named User response
transaction.
The server initialization process is aborted. Ensure
that the USERID specified by the SERVERID start-up
User response parameter is correct. If possible, fix the problem
identified by the error messages and restart the
Look for preceding error messages in the system log.
product.If the problem cannot be resolved, contact
AVZ0723I WLM enclave create successful for IBM Software Support.
Service Class class
AVZ0800I IDMS SERVER INIT IN PROGRESS
FOR CONNECTION=%1
Explanation
The server WLM enclave classification was successful. Explanation
This message indicates that the IDMS initialization is in
User response progress for the selected IDMS connection name.
None.
User response
AVZ0724I subsys WLM health changed from
subsystem%% to oper1%% oper2 None. This message is for informational purposes only.
AVZ0801I IDMS SERVER INIT COMPLETE
Explanation FOR CONNECTION=target USING
MAILBOX=connID
The WLM health value for the specified product
subsystem was changed from the first value to the
second. Explanation
This message indicates that the IDMS initialization has
User response been successfully completed for the selected IDMS
target using the defined connection (connID).
If the health value decreases, look for abends or
timeouts in the Server. Currently only ACI abends and
None. This message is for informational purposes only. Ensure that the given library is a PDS similar by
definition to the other REXX libraries. Check the
AVZ0802I CONNECTION BROKEN WITH
message and codes manuals for the abend code. Most
IDMS CONNECTION=connID
likely, either the member does not exist or the data
USING MAILBOX=jobname
set attributes are in error (sequential DSORG or the
LRECL and BLKSIZE are not compatible). If a system
Explanation 913 abend code is reported, data set access has been
disallowed by your security subsystem.
This message indicates that the IDMS connection
has been broken for the selected IDMS connection AVZ0902E Cannot find program program
(connID) ddname.

None. This message is for informational purposes only. The REXX interpreter (AVZI, AVZX, SWSI, or SWSX TSO
command processor) could not locate the specified
AVZ0900E service of ddname/cblk failed,
REXX program in the data set allocated to the
RC=rcode.
SYSEXEC ddname (for SDBI or SWSI) or in the data
set specified on the AVZX or SWSX commands.
Explanation
During compilation or execution of a REXX program, an User response
MVS service returned a non-zero error code. One of the
Ensure the program name being executed exists in one
following occurred: (1) a file failed to open or close,
of the SYSEXEC concatenated data sets (for AVZI or
(2) a failure in writing a record (WRITE or ENDREQ),
SWSI) or in the data set specified on the AVZX or
(3) storage for a control block could not be obtained or
SWSX command. Check the spelling of the program
freed, or (4) parsing of the command failed.
name.
User response AVZ0903E ERROR 43 reqtype caller, LINE

lineno: ROUTINE routine NOT
Depending on which of the above cases pertains, FOUND
take one of the following actions: (1) check for a
message indicating why the file failed to open or close
Explanation
(most likely, the SYSEXEC file name was not allocated
properly - e.g. allocated to a sequential file instead of a While compiling a REXX program, the REXX interpreter
partitioned data set); (2) if a WRITE or ENDREQ failed could not locate a routine called by the main program
message was issued, check the status of the PDS or called by one of its subroutines.
allocated in the AVZCOMP or SWSCOMP DD (it may
not be allocated properly - e.g. ran out of space); (3)
User response
if the error reported a GETMAIN, allocate or allocation
failure, you may have to increase the TSO region size Check the calling program (described in this message)
for your TSO session; or (4) check the command you to make sure that the subroutine name is spelled
issued for incorrect syntax. correctly. If spelling is correct, the missing routine
must be added to a library allocated to the SYSEXEC
AVZ0901E CANNOT OPEN member (ABEND
ddname or to the same library in which the calling
abcode AT modname+offset)
program resides.
=
Explanation
AVZ0906I No syntax errors found during
During the open processing of the REXX program
scan.
to be run, an abend occurred. The PDS member
containing the REXX source program could not be
opened because of the abend. Explanation
The compiler found no syntax errors during a AVZX
scan. This is an informational message.

User response command was invoked from within ISPF edit and the
ISPF environment could not be established.
AVZ0907S ABEND abcode OCCURRED User response
AT csect+offset OF PROGRAM
program If the AVZI command was invoked via the TSO CALL
command, you must add the parameter field with
a REXX program name (and optional arguments).
Explanation Otherwise, contact Software Support for assistance.
An abend occurred during the execution of a REXX AVZ0912E Missing REXX program name
program by the REXX interpreter (AVZI or AVZX TSO detected at - addr
command). The name of the REXX program being
executed at the time of the abend is shown in this
message. Explanation
The AVZI or AVZX TSO command was invoked without
User response a program name.
Check the line being executed at the time of the

abend. Check the abend code in the messages and User response
codes manual, and follow action stipulated there. You must specify a program name on the AVZI or AVZX
AVZ0908E PROGRAM program IS TOO LARGE TSO command. Contact Software Support.
- INPUT BUFFER OVERFLOW AVZ0913E Invalid REXX program name
detected - program
Explanation
The REXX interpreter (AVZI or AVZX TSO command) Explanation
could not successfully compile a REXX program The REXX program name specified is invalid. It must
because it is too large. be a valid PDS member name and cannot exceed eight
(8) characters in length.
User response
Split the program into smaller subroutines. This error User response
is directly related to the number and length of source Specify a valid REXX program name. If the problem
input lines in a single REXX program. cannot be resolved, contact Software Support.
AVZ0909E PROGRAM program - ARG LENGTH AVZ0914E UNKNOWN RETURN CODE FROM
(lgth) EXCEEDS MAXIMUM LENGTH PARSE ROUTINE, RC=rcode
(maxlgth)
Explanation
Explanation
An unexpected return code was received from the
The length of the argument string for the REXX internal parse routine.
program exceeds the implementation limit.
User response
User response
Contact Software Support for assistance.
Check if there are an excessive number of blanks in
the argument string. If so, remove the blanks from the AVZ0915E BATCH OR TSO CALL PARAMETER
argument string. If you need to pass long values to a STRING TOO LONG
REXX program, use global variables to pass the values.
AVZ0911E Missing REXX program name Explanation
The parameter field passed to a batch program, or
Explanation a program invoked by TSO CALL cannot exceed 100
characters.
The AVZI command was invoked using the TSO
CALL command without a parameter field (containing
the REXX program name to execute), or the @#$I
Reduce the length of the parameter string. Contact THE REXX interpreter (AVZICOMP, AVZXCOMP,
Software Support to obtain additional assistance. SWSICOMP or SWSXCOMP commands) was successful
in compiling and saving the REXX program.
AVZ0916E routine built-in function not found
- called by caller.
User response
Explanation No action is required.
A compatibility problem exists between the product AVZ0920E REBUILD FAILED FOR COMPILED
subsystem in use and the pre-compiled REXX program REXX PROGRAM - program
being re-loaded. A product built-in function that was to
be used by the pre-compiled REXX program no longer Explanation
exists.
The REXX interpreter command processor was
attempting to rebuild a REXX program from a
User response
previously compiled PDS member when the failure
Check the subsystem release levels used when the occurred.
REXX program was compiled. It may be necessary to
recompile the REXX program again under the current User response
product subsystem (AVZICOMP).
Check for other accompanying error messages. You
AVZ0917E ERROR SAVING THE COMPILED may have to delete the compiled version of the
OUTPUT IN %1 program and recompile it again, or execute the REXX
source program.
Explanation
AVZ0921W ALLOCATION OF COMPILED
An error occurred while attempting to save a pre- LIBRARY (dsname) FAILED
compiled program. This message is accompanied by
an earlier message detailing the cause of the error. Explanation
The product attempted to allocate the library with the
User response
compiled versions of REXX programs. The dynamic
Check the previous error message for possible actions. allocation failed.
AVZ0918E CANNOT WRITE EXECUTABLE
OBJECT obj.obj2 TO DS(dsname) User response
additinfo Make sure that the data set name specified in the first
panel of this application is valid. Contact the person at
Explanation your installation who is responsible for the product to
get the proper data set name.
SEF is unable to save an executable object binary
image or data area because of a runtime problem. AVZ0922W ITRACE KEYWORD NOT ALLOWED
The source rule or data file are named, along with the DURING COMPILE ONLY REQUEST
target dataset.
obj1 may indicate a ruleset or a datafile Explanation
Based on the value of obj1, obj2 may indicate a rule or Setting the initial trace value for a COMPILE ONLY
data member request is not allowed.

Check for other messages indicating the source of the Do not specify the ITRACE keyword in a COMPILE
problem and retry the request. ONLY request. The ITRACE value only has meaning
during the execution phase of REXX.
AVZ0919I Successful compile and save of
program in ddname. AVZ0923S COMPILE ALL FAILED - ERROR
READING THE DIRECTORY OF
dsname

A COMPILE ONLY request was received for an entire None. This message is for informational purposes only.
PDS, but an error was detected while reading the
AVZ0998E RUNNING program LINE lineno:
directory.
COMPILER WORK SPACE
OVERFLOW (value1 value2)
User response
Try to browse the data set using ISPF and see if the Explanation
member list directory is accessible for the PDS. If
not, contact your local DASD administrator for possible The rule or program used up all of the available REXX
data set recovery. If you are able to browse the data variable work space.
set and list its members properly, contact Software
Support. User response
AVZ0990E RUNNING program: In either case, check if the program is incorrectly
INCOMPATIBLE CONTROL BLOCKS creating too many variables. If so, correct the program,
and retry the operation. If the program is operating
correctly, the work space size may be too small. In
Explanation
the rule environment, the SEFSIZE parameter needs to
The REXX program was compiled with an older be increased, and the product must be restarted. In
version of the Product REXX interface module. The the case of a Product REXX program (SWSI command),
REXX control blocks in the compiled module are use the WORKSPACE keyword parameter to override
incompatible with the current version. the default size. For WWW rules, override the default
workspace specification by coding the WORKSPACE()
User response operand on the /*WWW header statement for the rule.
This error should only occur when executing a pre- AVZ0999E STAX calltype MACRO FAILED -
compiled, saved version of a program or rule. In that RC=rcode
case, the program or rule should be recompiled and
then re-executed. If the error occurred in any other Explanation
case, contact Software Support for assistance.
The STAX macro failed with the indicated return
AVZ0991E RUNNING program: INTERNAL code while the Product REXX compiler was trying to
ERROR DETECTED AT addr initialize or terminate execution of a REXX program.
calltype can be "ON" or "OFF"
Explanation
The REXX interface module detected an internal error. User response
Record the error message and return code. Contact
User response Software Support.
There may be other error messages related to this The STAX macro failed with the indicated return
condition. This error may be caused by a REXX code while the Product REXX compiler was trying to
workspace overflow condition. If this is the case, initialize or terminate execution of a REXX program.
refer to message 0998E for additional information.
If the problem cannot be resolved, contact Software AVZ1000I msgtext
Support.
Explanation
AVZ0997T lineno TRACE MESSAG
The product message used for REXX SAY statements.
Explanation
User response
Informational message only. This message gives the
output from the REXX TRACE command when used in None. This message is for informational purposes only.
a rule.
AVZ1004I ERROR 4 process program, LINE
lineno: PROGRAM INTERRUPTED
Explanation this message results. This is commonly caused
by forgetting the DO and END around the list of
The system halted the execution of a REXX program instructions following a WHEN.
because of some error or by user request. Unless
trapped by SIGNAL ON HALT, this message will process may be "compiling" or "running"
force the language processor to immediately cease
execution. User response
process may be "compiling" or "running" Examine the REXX program, and correct the error.
User response lineno: UNEXPECTED THEN OR
None. This message is for informational purposes only. ELSE

lineno: MACHINE RESOURCES Explanation
EXHAUSTED A THEN or an ELSE has been found that does not
match a corresponding IF or WHEN clause. This error
Explanation often occurs because of a missing END or DO...END in
part of a complex IF...THEN...ELSE construct.
While attempting to execute a REXX program,
the language processor was unable to obtain the process may be "compiling" or "running"
resources it needed to continue execution. The
following items may be the cause of this message: User response
(1) the external data queue is full or (2) all available
storage has been used. Examine the program, and correct the error.
process may be "compiling" or "running" AVZ1009I ERROR 9 process program, LINE

lineno: UNEXPECTED WHEN OR
OTHERWISE
User response
Try increasing the size of the external data queue or Explanation
the amount of storage available to the program.
A WHEN or OTHERWISE has been found outside
AVZ1006I ERROR 6 var1 var2, LINE lineno: of a SELECT construct. It may have been enclosed
UNMATCHED "/*" OR QUOTE unintentionally in a DO...END construct by leaving off
an END instruction, or an attempt may have been
Explanation made to branch to it with a SIGNAL instruction (which
cannot work because a SELECT is terminated by a
A comment string or a literal string was started but SIGNAL).
never finished. For comments, this may be detected at
the end of the program or at the end of an INTERPRET process may be "compiling" or "running"
instruction. For literal strings, this may be detected at
the end of a line. User response
Examine your program, and fix the part in error.
User response
AVZ1010I ERROR 10 process program,
Examine the rule or REXX program, and correct the LINE lineno: UNEXPECTED OR
string. UNMATCHED END
lineno: WHEN OR OTHERWISE Explanation
EXPECTED
Either there are more ENDs in the program than DOs
and SELECTS or the ENDs are wrongly placed so
Explanation they do not match the DOs and SELECTs. It may be
Within a SELECT construct, at least one WHEN useful to use trace scan to show the structure of the
construct (and possibly an OTHERWISE clause) is program; hence, making it more obvious where the
expected. If any other instruction is found (or no error is. A common mistake that causes this error is
WHEN construct is found before OTHERWISE), then attempting to jump into the middle loop using the

SIGNAL instruction. This error will also be generated AVZ1014I ERROR 14 process program,
if an END immediately follows a THEN or an ELSE. LINE lineno: INCOMPLETE DO/
process may be "compiling" or "running" SELECT/IF

Examine the line in error, and correct the REXX On reaching the end of the program (or the end of
program. the string in an INTERPRET instruction), it has been
detected that there is a DO or SELECT without a
AVZ1011I ERROR 11 process program, LINE matching END or an IF that is not followed by a THEN
lineno: CONTROL STACK FULL clause to execute.
process may be "compiling" or "running"
Explanation
An implementation limit of levels of nesting of control User response
structures (DO...END, IF...THEN...ELSE, etc.) has been
Find the unbalanced DO or SELECT, and correct it.
exceeded. The message should state the actual
restriction. This error could be due to a looping AVZ1015I ERROR 15 process program, LINE
INTERPRET instruction or due to infinite recursive lineno: INVALID HEXADECIMAL
calls. OR BINARY CONSTANT

Examine the line in error, and fix the program. Hexadecimal constants may not have leading or
trailing blanks and may only have embedded blanks
at byte boundaries. Only the digits 0 - 9 and the
lineno: CLAUSE TOO LONG
letters a-f are allowed. Binary strings may only have
blanks added at the boundaries of groups of four
Explanation binary digits. Only the digits 0 and 1 are allowed.
The error may also be caused by following a literal
There may be an implementation restriction that limits
string either by the one character symbol "x" when the
the length of the internal representation of a clause.
string is not intended to be taken as a hexadecimal
This message is generated if this limit is exceeded.
specification or by the symbol "b" when the string is
process may be "compiling" or "running" not intended to be taken as a binary specification.
Use the explicit concatenation operator, "| |", in this
User response situation to concatenate the string to the value of the
symbol.
Reduce the length of the literal and hexadecimal
strings that exceed the documented limits. If process may be "compiling" or "running"
AVZ1013I ERROR 13 process program, LINE Locate the error on the line, and correct it.
lineno: INVALID CHARACTER IN
PROGRAM
lineno: LABEL NOT FOUND
Explanation
Explanation
The program includes a character outside the literal
A SIGNAL instruction has been executed, or an event
quoted string that neither alphanumeric nor one of the
occurred for which a trap was set, and the label
acceptable special characters.
specified cannot be found in the program.
User response
User response
Examine the line in error, and correct the invalid
Correct the error, and rerun the program.
character.
AVZ1017I ERROR 17 process program, LINE process may be "compiling" or "running"
lineno: UNEXPECTED PROCEDURE
User response
Explanation Correct the REXX program, and rerun.
A PROCEDURE instruction was encountered which
was not the first instruction executed after a call
lineno: INVALID DATA ON END OF
or function invocation. A possible cause of this is
CLAUSE
dropping through into an internal routine rather than
invoking it properly.
Explanation
A clause such as SELECT or NOP is followed by some
token other than a comment.
User response
Examine the line, correct the problem, and rerun the
program.
User response
lineno: THEN EXPECTED Correct the line, and rerun the REXX program.
Explanation LINE lineno: INVALID CHARACTER
STRING
All IF and WHEN clauses in REXX must be followed by
a THEN clause. Some other clause was found when a
THEN was expected. Explanation
process may be "compiling" or "running" This error results if a literal string contains character
codes that are not valid in a particular implementation.
This might be because some characters are impossible
User response
or because the character set is extended in some way
Examine the line, and correct the error. and certain character combinations are not allowed.
AVZ1019I ERROR 19 process program, process may be "compiling" or "running"
LINE lineno: STRING OR SYMBOL
EXPECTED User response
Examine the line, and correct the error.
Explanation
Following either the keyword call or the sequence
lineno: INVALID TRACE REQUEST
SIGNAL ON or SIGNAL OFF, a literal string or a symbol
was expected but neither was found.
Explanation
The setting specified on a trace instruction or as the
argument to the trace built-in function starts with a
User response
character that does not match one of the valid trace
Add the literal string or symbol that is needed. settings. This error is also raised if an attempt is made
to request trace scan when inside any kind of control
AVZ1020I ERROR 20 process program, LINE construct.
lineno: SYMBOL EXPECTED
Explanation
User response
In the clauses END, ITERATE, LEAVE, NUMERIC,
PARSE, and PROCEDURE, a symbol can be expected. Contact Software Support to obtain additional
Either it was not present when required or some other assistance.
token was found. Alternately, DROP and the EXPOSE
option of PROCEDURE expect a list of symbols. Some
lineno: INVALID SUB-KEYWORD
other token was found.
FOUND

Explanation this error is attempting to use the SIGNAL instruction
to transfer control within or into the loop.
An unexpected token has been found in the position
in an expression where a particular sub-keyword was process may be "compiling" or "running"
expected.
process may be "compiling" or "running" User response
Fix the problem on the line, and rerun the job.
User response AVZ1029I ERROR 29 process program, LINE
Correct the line, and resubmit. lineno: ENVIRONMENT NAME IS
TOO LONG
lineno: INVALID WHOLE NUMBER
Explanation
Explanation The environment name specified by the ADDRESS
instruction is longer than permitted for the system
One of the following either did not evaluate to a whole under which REXX is running. This message should
number or is greater than the implementation limit for state the maximum length permitted.
these uses: (1) the expression for digits or fuzz in the
numeric instruction, (2) a parsing positional parameter, process may be "compiling" or "running"
(3) a repetition phrase of a DO clause, or (4) the right-
hand of the POWER("*") operator. This error is also User response
raised if a negative repetition count is found in a DO
clause. Correct the problem, and rerun the REXX program.

lineno: NAME OR STRING TOO
LONG
User response
Correct the problem on the line, and then rerun the Explanation
program.
This error results if there is an implementation limit
AVZ1027I ERROR 27 process program, LINE that is exceeded for the length of a variable name, a
lineno: INVALID DO SYNTAX label name, or a literal string.
Explanation
Some syntax error has been found in the DO User response
instruction. This might be using the TO, BY, or FOR
sub-keywords twice or when there is no control Fix the error, and rerun the REXX program.
variable specified. AVZ1031I ERROR 31 process program, LINE
process may be "compiling" or "running" lineno: NAME STARTS WITH
NUMBER OR "."
User response
Explanation
Fix the error, and rerun the job.
A value may not be assigned to a variable whose
AVZ1028I ERROR 28 process program, name starts with a numeric digit or a period (if it were
LINE lineno: INVALID LEAVE OR allowed, one could redefine numeric constants).
ITERATE
Explanation
User response
A LEAVE or ITERATE instruction was encountered in an
invalid position. Either no loop is active or the name Correct the error, and rerun the REXX program.
specified on the instruction does not match the control AVZ1033I ERROR 33 process program, LINE
variable of an active loop. Note that since internal lineno: INVALID EXPRESSION
routine calls and the INTERPRET instruction protect RESULT
DO loops, they become inactive. A common cause of
The result of an expression in an instruction was found Examine the line, fix the problem, and then rerun.
to be invalid in the particular context it was used.
This may be due to an illegal fuzz or digits value in a
lineno: UNEXPECTED "," OR ")"
numeric instruction (fuzz may not become larger than
digits).
Explanation
Either a comma has been found outside a function
User response invocation or there are too many right parentheses in
an expression.
lineno: LOGICAL VALUE NOT 0 OR User response
1
Examine the line, fix the problem, and then rerun.
Explanation AVZ1038I ERROR 38 process program, LINE
The expression in an IF, WHEN, DO WHILE, or DO lineno: INVALID TEMPLATE OR
UNTIL phrase must result in a 0 or a 1, as must any PATTERN
term operated on by a logical operator.
Explanation
Within a parsing template, either a special character
User response that is not allowed has been found or the syntax of
a variable pattern is incorrect. This error may also be
Fix the bug, and rerun the program. raised if the WITH sub-keyword is omitted in a parse
value instruction.
lineno: INVALID EXPRESSION process may be "compiling" or "running"

This is due to a grammatical error in an expression, Examine the program, fix the problem, and then rerun.
such as ending it with an operator or having two
operators adjacent with nothing in between. It may AVZ1039I ERROR 39 process program,
also be due to an expression that is missing when LINE lineno: EVALUATION STACK
one is required. A common error is to include OVERFLOW
special characters in an intended character expression
without enclosing them in quotes. Explanation
process may be "compiling" or "running" The expression is too complex to be evaluated by
the language processor. There are too many nested
User response parentheses, functions, etc. The message should state
the actual restriction.
Examine the line, fix the problem, and then rerun.
LINE lineno: UNMATCHED "(" IN User response
EXPRESSION
Examine the program, simplify the expression, and
then rerun.
Explanation
This is due to not pairing parentheses correctly within AVZ1040I ERROR 40 process program, LINE
an expression. There are more left parentheses than lineno: INCORRECT CALL TO
right parentheses. ROUTINE

Explanation processor has been unable to locate it externally. The
name has probably been typed incorrectly, or a symbol
The specified built-in or external routine does exist or literal string is adjacent to a "(" when it was meant
but has been used incorrectly. Either invalid arguments to be separated by a blank or some other operator.
were passed to the routine, the program invoked was Functions referenced in an INTERPRET statement that
not compatible with the REXX language processor, are not product built-in functions and have not been
or more than an implementation-limited number of previously referenced will also result in this error.
arguments were passed to the routine.
User response
User response
Examine the program, and correct the error.
Examine the statement calling the routine, and correct
it. AVZ1044I ERROR 44 process program,
LINE lineno: FUNCTION DID NOT
AVZ1041I ERROR 41 process program, RETURN DATA
LINE lineno: BAD ARITHMETIC
CONVERSION
Explanation
Explanation An external function has been invoked within an
expression, but even though it appeared to end
Either one of the terms involved in an arithmetic without error, it did not return data for use within the
operation is not a valid number or its exponent expression.
exceeds the implementation limit.
User response
User response
Examine the program, and correct the problem.
AVZ1042I ERROR 42 process program, LINE lineno: NO DATA SPECIFIED IN
lineno: ARITHMETIC OVERFLOW/ FUNCTION RETURN
UNDERFLOW
Explanation
Explanation
The program has been called as a function, but an
The result of an arithmetic operation requires an attempt is being made (by RETURN) to return without
exponent that is outside the range supported by the passing back any data.
implementation. This can happen during evaluation
of an expression (commonly an attempt to divide a process may be "compiling" or "running"
number by 0) or possibly during the stepping of a DO
loop control variable. User response
process may be "compiling" or "running" Examine the program, and correct the error.
User response LINE lineno: INVALID VARIABLE
Examine the program, and correct the error. REFERENCE

lineno: ROUTINE NOT FOUND Explanation
An attempt to indirectly reference a variable is invalid.
Explanation This would most likely occur on an EXPOSE or
INTERPRET instruction. For example: EXPOSE (Y)
A function that has been invoked within an expression where Y is a number.
cannot be found, or a subroutine that has been
invoked by call cannot be found. No label with process may be "compiling" or "running"
the specified name exists in the program. It is not
the name of a built-in function, and the language
Examine the program, and correct the error. The program has used the ampersand as a prefix to a
symbol. The REXX interpreter does not allow this.
LINE lineno: FAILURE IN SYSTEM process may be "compiling" or "running"
SERVICE
User response
Explanation Contact Software Support.
Some system service used by the REXX language
processor (such as stream input or output) has failed
lineno: DUPLICATE LABEL
to work correctly; hence, normal execution cannot
continue.
Explanation
The program has defined the same label name twice.
User response process may be "compiling" or "running"
User response
lineno: INTERPRETATION ERROR Change the label on one of the two statements.
Explanation lineno: FUNCTION NAME > 32
CHARACTERS
Implementations of the REXX language will normally
carry out internal self-consistency checks during
execution. This message indicates that some kind of Explanation
severe error has been detected within the language
The program has defined or referenced a function
processor or execution process.
whose name exceeds the maximum function name
process may be "compiling" or "running" length of 32 characters.
User response
Contact Software Support for further assistance. User response
AVZ1064I ERROR 64 process program, Change the function name to a shorter name.
LINE lineno: UNIMPLEMENTED
FEATURE
lineno: FUNCTION HAS TOO FEW
ARGUMENTS
Explanation
The program has used a REXX language feature Explanation
which is not supported by this version of the REXX
The program has called a function that requires more
interpreter. Code 64 is an extended error code used
arguments than specified on the function call.
only by REXX.
User response
User response
Add the necessary arguments to the function call.
Check documentation for support of the feature.
Check the documentation for the specified function.
Change the REXX program to bypass use of the
feature. AVZ1070I ERROR 70 process program, LINE
lineno: FUNCTION HAS TOO MANY
ARGUMENTS
lineno: AMPERSAND VARIABLES
UNSUPPORTED

Explanation AVZ1074I ERROR 74 process program, LINE
lineno: MAX STATEMENT COUNT
The REXX program has called a function that requires
fewer arguments than specified on the function call.
Explanation
This error should not occur.
User response process may be "compiling" or "running"
Remove the superfluous arguments to the function
call. Check the documentation for the specified User response
function. Contact Software Support for further assistance.
AVZ1071I ERROR 71 process program, LINE AVZ1075I ERROR 75 process program, LINE
lineno: CODE VERSION IS DOWN lineno: ELSE NEEDS SEMICOLON
LEVEL
Explanation
Explanation
The REXX program was compiled with a version of the
REXX interpreter which is lower than the version used process may be "compiling" or "running"
to execute the program.
process may be "compiling" or "running" User response
Contact Software Support for further assistance.
This error should only occur when executing a pre- lineno: VARIABLE VALUE TOO
compiled, saved version of a program or rule. In this LONG
case, the program or rule should be recompiled and
then re-executed. In all other cases, contact Software Explanation
The REXX program attempted to assign a value to
AVZ1072I ERROR 72 process program, LINE a variable. The string value exceeded the maximum
lineno: FUNCTION RETURNED allowed length.
UNASSIGNED STEM DATA
Explanation
User response
A REXX function written in assembler has returned
incorrect data. Shorten the string value.

lineno: CODE AREA FULL
User response
Explanation
The REXX program could not be compiled. The target
AVZ1073I ERROR 73 process program, code area is not large enough to hold the result of the
LINE lineno: RECORD REFERENCE compiled program.
EXCEEDS VARIABLE VALUE
Explanation
User response
Shorten the REXX program by dividing it into
process may be "compiling" or "running" subroutines, and store these subroutines as separate
members.
User response
AVZ1080I ERROR 80 process program, process may be "compiling" or "running"
LINE lineno: PULL FOUND EMPTY
QUEUE User response
Reduce the complexity of the structure flagged, and
Explanation retry the compile. If the problem cannot be resolved,
This error should not occur. A null string is returned contact Software Support.
instead for compatibility with older releases of Product
REXX. Contact Software Support for further assistance.
lineno: TOO MANY SYMBOLS,
process may be "compiling" or "running" SYMBOL TABLE FULL

No action is required. If this occurs during the compile phase, the program
is using too many symbols and the symbol table has
AVZ1081I ERROR 80 process program, LINE overflowed.
lineno: NOT SUPPORTED WITHIN
INTERPRET process may be "compiling" or "running"

The REXX program executed an INTERPRET Reduce the number of symbols used by the program,
instruction that contained a REXX structure not and retry the compile. If this does not solve the
supported in INTERPRET. problem, contact Software Support.
process may be "compiling" or "running" AVZ1085I ERROR 85 process program,
LINE lineno: INVALID USE OF
User response EXTENDED VARIABLE TYPE
Modify the interpreted code. If the problem cannot be

Explanation
resolved, contact Software Support.
The REXX program has attempted to use a variable in
AVZ1082I ERROR 82 process program, a manner that is not supported. This could occur if a
LINE lineno: ARRAY BOUNDARY product global variable is used as the control variable
EXCEEDED in a controlled repetitive loop (e.g. DO GLOBAL.I = 1
TO 10).
Explanation
The REXX program was attempting to store an element
of an array. The element number was larger than the User response
declared dimension of the array.
Modify the REXX program so that it does not use a
process may be "compiling" or "running" global variable as the loop control variable.

lineno: INVALID GLOBAL SYMBOL
AVZ1083I ERROR 83 process program, LINE Explanation
lineno: CODE BLOCK TOO LARGE, A Product REXX global symbol whose derived name
EVAL STACK FULL exceeds the Product REXX global variable symbol
length limit of 50 characters has been used.
Explanation
If this occurs during the compile phase, the program
is using a structure too complex for the compiler to User response
handle. This could occur if a SELECT statement has too
many WHEN clauses or if there are too many nested Check the statement in error, and determine which
control structures. symbol substitution caused the derived name of a

global variable to exceed the specified limit. Modify Explanation
the program to use a shorter derived name.
The OPTIONS statement contains options which are
AVZ1087I ERROR 87 process program, not valid. Note that unknown OPTIONS keywords are
LINE lineno: INVALID INTERNAL ignored and are not flagged as errors. Only partially
OBJECT incorrect OPTIONS keywords are flagged.
Explanation
This is an internal Product REXX error. User response
process may be "compiling" or "running" Correct the OPTIONS statement, and retry the
operation.
Please contact Software Support to obtain additional lineno: OVER maxno CLAUSES
assistance. EXECUTED IN RECOVERY EXIT

LINE lineno: INTERPRETER STACK
Explanation
ERROR A REXX program or a rule exceeded the maximum
number of clauses allowed for a SIGNAL ON syntax or
Explanation SIGNAL ON HALT recovery routine following a product
limit exceeded condition. The maximum number of
This is an internal Product REXX error. clauses allowed when recovering from a product limit
process may be "compiling" or "running" type error is indicated in the error text.
User response
Please contact Software Support to obtain additional User response
assistance. Reduce the number of clauses that are executed in the
limit failure recovery routine.
AVZ1090I var1 var2 var3 var4 var5 var6 var7
var8 var9 var1 0var11 AVZ1093E ERROR 93 process program,
LINE lineno: GLOBAL VARIABLE
Explanation WORKSPACE OVERFLOW (parmval
- wrkspc)
Message : SWS1090I REXX abend in
OPRXCMRU+x'offset'. This message is normally
accompanied by a 1049I message which relates to an Explanation
error 49 in a given rule type. A shared/permanent global variable or temporary
global variable value cannot be stored successfully.
User response This message may be issued under a number of
circumstances if a global or global-temporary variable
Check the given rule. In the case of a variable passed update/addition fails. The conditions causing this
to the given error line, make sure the variable is message to be issued are: 1) The number of global
valid. Display fields such as RULE and others in Trace variables now allocated and in-use (GLOBALUSED or
Browse. For a test situation of the given rule or REXX RXWSGVCN for temporary workspace) exceeds the
program, include a SAY statement to print the value of maximum count limit configured by the GLOBALMAX
the given variable at the of the error. If the error is not (shared/permanent variables) or GLOBALTEMPMAX
related to variables, validate the given line, and take (temporary variables) parameters. You must use
appropriate action. Parameters like BROWSEGLV could the ISPF C.3 display Note that you must use the
be used if this is a global variable rule error. See other ISPF C.3 panel display, selecting "RXWS GLVEVENT.
browse parameters and use as applicable. WORK SPACE", in order to view RXWSGVCN and
AVZ1091I ERROR 91 process program, LINE obtain the temporary workspace variable count.
lineno: INVALID OR MISPLACED 2) There is insufficient free space anywhere
OPTIONS STATEMENT within the global workspace to update or add
a variable's value. The value requires multiple
workspace segments (RXGV's) for storage and enough
free RXGV's could not be found on the free parameters. These limits may be overridden using
element chain (RXWSFCCN / GLOBALFREEAREAS), NOMAXSECONDS or MAXSECONDS=nnnn on the REXX
or there was insufficient un-allocated space at OPTIONS statement.
the end of the workspace (RXWSLN / GLOBALSIZE
minus RXWSNXFR / GLOBALNEXT). Contiguous RXGV
freespace blocks are required for allocation of
the value storage area. Note that the parameters User response
GLOBALFREEAREAS, GLOBALSIZE, and GLOBALNEXT
Determine whether this problem was caused by a
apply ONLY to the shared/permanent workspace.
looping program or whether the limits are too low. The
For the temporary workspace, you must examine
limits that affect all rules/programs can be modified
the RXWS field value using the ISPF C.3 "RXWS
by changing the xxxPARM limits (SEFMAXSECONDS
GLVEVENT. WORK SPACE" block display. No product
and/or REXXMAXSECONDS). The limits for the
parameters map these values for the temporary
individual program can be overridden by using the
workspace. The word "TEMP" is inserted into the
REXX OPTIONS statement as described in the product
message as the last word (within final parentheses)
Reference Manual.
if the TEMPORARY global workspace has overflowed.
GLVEVENT. stem and internal-use global stem AVZ1095E ERROR 95 process program,
variables are allocated within the temporary global LINE lineno: OVER maxno HOST
workspace. Otherwise, the word "TEMP" is not present COMMANDS ISSUED
in the message and it is the shared/permanent
global workspace that has overflowed. GLOBAL., and
Explanation
GLOBAL0. through GLOBAL9. stem variables are in the
shared/permanent workspace area. A rule or REXX program exceeded its host
command limits as set by SEFMAXCOMMANDS (rule)
or REXXMAXCOMMANDS (REXX program) product
parameters. These limits may be overridden using
User response NOMAXCOMMANDS or MAXCOMMANDS=nnnn on the
REXX OPTIONS statement.
You may need to analyze the contents of the
global variable database using the global variables process may be "compiling" or "running"
application, product parameters, or the ISPF
C.3 RXWS displays. Use the ISPF E.1 panel
User response
to remove unneeded permanent GLOBAL. stem
variables. Otherwise, increase the GLOBALMAX Determine whether this problem was caused by a
or GLOBALTEMPMAX start-up parameters. If looping program or whether the limits are too low. The
the workspace is too small, you may also limits that affect all rules/programs can be modified
need to (re) allocate a larger global variable by changing the xxxPARM limits (SEFMAXCOMMANDS
checkpoint DIV dataset and copy the original and/or REXXMAXCOMMANDS). The limits for the
DIV into the new one using Access Method individual program can be overridden by using the
Services REPRO. To prevent future out-of-space REXX OPTIONS statement as described in the product
hard failures, set the warning threshold percent Reference Manual.
(GLOBALWARNTHRESH or GLOBALTEMPWARNTH)
AVZ1096E ERROR 96 process program,
and interval (GLOBALWARNINTERVAL or
LINE lineno: OVER maxno "SAY"
GLOBALTEMPWARNIV) so that a threshold is
CLAUSES EXECUTED
established and reported periodically via MSG 4290.
Automate this message so that sufficient notification
is given to prevent the out-of-space hard failure limit Explanation
from being reached before the workspaces can be
A rule or REXX program exceeded its SAY/TRACE limits
expanded.
as set by SEFMAXSAYS (rule) or REXXMAXSAYS (REXX
AVZ1094E ERROR 94 process program, LINE program) product parameters. These limits may be
lineno: OVER sec SECONDS USED overridden using NOMAXSAYS or MAXSAYS=nnnn on
FOR EXECUTION the REXX OPTIONS statement.
Explanation
A rule or REXX program exceeded its wall clock
time limits as set by SEFMAXSECONDS (rule)
or REXXMAXSECONDS (REXX program) product

User response AVZ1100S RETRY LIMIT CONVERSION
ERROR - VALUE SPECIFIED = val
Determine whether this problem was caused by a
looping program or whether the limits are too low. The
limits that affect all rules/programs can be modified Explanation
by changing the xxxPARM limits (SEFMAXSAYS and/or An error was detected while trying to convert the
REXXMAXSAYS). The limits for the individual program character representation of the specified retry limit
can be overridden by using the REXX OPTIONS (val) to its integer counterpart.
statement as described in the product Reference
Manual.
User response
AVZ1097E ERROR 97 process program, LINE
lineno: OVER maxno CLAUSES Review the retry limit specification contained in the
EXECUTED error message. If the specified retry limit contains an
invalid value, correct the error, and re-invoke the DSN
command. If all attempts at correcting the specified
Explanation retry limit fail, contact Software Support for further
A rule or REXX program exceeded its clause limits as assistance.
set by SEFMAXCLAUSES (rule) or REXXMAXCLAUSES AVZ1101S TEST LEVEL CONVERSION ERROR
(REXX program) product parameters. These limits - VALUE SPECIFIED = val
may be overridden using NOMAXCLAUSES or
MAXCLAUSES=nnnn on the REXX OPTIONS statement.
Explanation
An error was detected while trying to convert the
character representation of the specified test level
User response (val), to its integer counterpart.
Determine whether this problem was caused by
a looping program or whether the limits are User response
too low. The limits that affect all rules/programs
can be modified by changing the xxxPARM limits Review the test level specification contained in the
(SEFMAXCLAUSES and/or REXXMAXCLAUSES). The error message. If the specified test level contains an
limits for the individual program can be overridden by invalid value, correct the error, and re-invoke the DSN
using the REXX OPTIONS statement as described in command. If all attempts at correcting the specified
the product Reference Manual. test level fail, contact Software Support for further
assistance.
AVZ1098I lineno TRACE MESSAG
AVZ1102S subsys NOT VALID SUBSYSTEM ID,
COMMAND TERMINATED
Explanation
Informational message only. This message gives the Explanation
output from the REXX TRACE command.
A subsystem control table that corresponded to the
subsystem name contained in the error message could
User response not be located by the SSCT chain scan logic.
AVZ1099I statement User response
If the subsystem name was specified on the SYSTEM()
Explanation command argument, review the name, and revise the
SYSTEM() specification, if necessary. If a SYSTEM()
This message is issued when the REXX compiler command line argument was not specified, the
detects a an error during compilation. The first line product-provided default value may not be appropriate
of the message lists the statement in error and the for your installation. This value was obtained from the
second line indicates where in the first line the error local copy of the DSNHDECP Db2 parameters module,
was detected. if one could be found. If a local copy of the DSNHDECP
parameters module contains an invalid value, run the
User response JCL jobstream contained in the AVZ CNTL data set
member ZAPDECP after updating the REP control card.
Review the REXX statement, and correct the error. If a local copy of the DSNHDECP parameters module
was not found, the product will attempt to use the User response
standard IBM default subsystem, DSN. For further
assistance in providing the product with the correct Determine if the product may have started and
subsystem name value, contact Software Support. terminated abnormally. If so, review the accompanying
messages in the SYSLOG. If the product did not
AVZ1104S Subsystem subsys is not a valid terminate abnormally, issue the appropriate start
DB2 subsystem command. If necessary, contact Software Support for
further assistance.
Explanation AVZ1110S CONNECTION FAILURE RC = rcode
The SSCT located for the subsystem name that was REASON = rsncode
extracted is neither a valid product SSCT nor a valid
Db2 SSCT. Explanation
The attempt to connect to the remote Db2 subsystem
User response failed.
If the subsystem name was specified on the SYSTEM()
command argument, review the name, and revise the User response
SYSTEM() specification, if necessary. If a SYSTEM()
command line argument was not specified, the Review the return code and the reason code values
product provided default value may not be appropriate contained in the error message. Compare the return
for your installation. This value was obtained from the code and reason code with those listed in the IBM
local copy of the DSNHDECP Db2 parameters module, SQL Application Programming Manual, and take the
if one could be found. If a local copy of the DSNHDECP appropriate action. If all attempts to correct the
parameters module contains an invalid value, run the problem fail, contact Software Support for further
JCL jobstream contained in the S__ CNTL data set assistance.
member ZAPDECP after updating the REP control card. AVZ1112S DISCONNECT FAILURE RC = rcode
If a local copy of the DSNHDECP parameters module REASON = rsncode
was not found, the product will attempt to use the
standard IBM default subsystem, DSN. If the problem
cannot be resolved, contact Software Support. Explanation
AVZ1105S LOAD FOR DSNECP00 FAILURE The attempt to disconnect from the remote Db2
subsystem has failed.
Explanation
User response
The attempt to load the renamed version of DSNECP00
has failed. Review the return code and the reason code values
contained in the error message. Compare the return
code and reason code with those listed in the IBM
User response SQL Application Programming Manual, and take the
Ensure that the product installation process was appropriate action. If all attempts to correct the
completed successfully. Ensure that the load library problem fail, contact Software Support for further
containing the renamed version of DSNECP00 is assistance.
accessible by the product. If all attempts to correct AVZ1113S COMMAND REJECTED - cmd CMD
the problem situation fail, contact Software Support NOT SUPPORTED UNDER DSN
for further assistance.
AVZ1106S subsys NOT OPERATIONAL, RETRY Explanation
COUNT ZERO
The subcommand specified (cmd) is not supported
under the DSN command.
Explanation
The SSCT for the product indicated that the product is User response
not currently active.
Review the command string entered. Revise the
command string, if appropriate. Re-enter the revised
command string. If the problem cannot be resolved,

AVZ1114R msgtext Explanation
The RUN subcommand requires that either the
Explanation PROGRAM parameter be specified or the PLAN and CP
Module OPDSN10 issued the current message parameters be specified.
(msgtext) as a prompt for valid subcommand input.
User response
User response Revise the subcommand string entered. If the program
Respond with an appropriate subcommand name, or to be executed is not a TSO command processor,
enter the END subcommand if processing is complete. specify only the PROGRAM() parameter. If the program
to be executed is a TSO command processor, specify
AVZ1115S ERROR ISSUING SUBCOMMAND the PLAN and CP parameters.
PROMPT - RC = rcode
AVZ1120S DSNRLI func FUNCTION FAILED.
RC = rcode REASON = rsncode
Explanation
An error occurred either issuing the subcommand Explanation
prompt or while waiting for valid subcommand input.
The RRSAF function (func) failed.
User response
User response
Review the return code and the reason code values
AVZ1117S COMMAND BUFFER SCAN ERROR - contained in the error message. Compare the return
RC = rcode code and reason code with those listed in the IBM
SQL Application Programming Manual, and take the
Explanation appropriate action. If all attempts to correct the
problem fail, contact Software Support for further
An attempt to scan the command buffer utilizing the assistance
services of IKJSCAN failed.
AVZ1121I PLEASE WAIT...CONNECTION
RETRY IN PROGRESS
User response
Review the command string entered. Revise the Explanation
command string. If the problem cannot be resolved, The remote Db2 subsystem is currently not active and
contact Software Support. a RETRY() value greater than one (1) was specified.
The connection request will be retried.
AVZ1118S RUN SUBCOMMANDS CAN NOT
HAVE A PROGRAM PARAMETER
AND A CP PARAMETER
User response
No action required.
Explanation AVZ1122I COMMAND SPUFI IGNORED,
The PROGRAM and CP parameters of the RUN VALID ISPF ENVIRONMENT MUST
subcommand are mutually exclusive. EXIST

Revise the subcommand string entered. If the program The SPUFI subcommand requires that a valid ISPF
to be executed is not a TSO command processor, environment exist.
specify only the PROGRAM() parameter. If the program
to be executed is a TSO command processor, specify User response
only the CP parameter.
Re-invoke the DSN command from within ISPF. If
AVZ1119S RUN SUBCOMMAND REQUIRES the error persists, contact Software Support to obtain
(1)PROGRAM PARAMETER OR additional assistance.
(2)PLAN AND CP PARAMETER
AVZ1123S COMMAND REJECTED, CMD NOT User response
SUPPORTED UNDER DSN
Respond with a valid TSO command name.
Explanation AVZ1130S ERROR ISSUING TSO COMMAND

PROMPT - RC = rcode
The subcommand specified is not supported under the
DSN command.
Explanation
User response An error occurred either while issuing the TSO
command prompt or while waiting for valid TSO
Review the command string entered. Revise the command input.
command string. If the error condition persists despite
correcting errors in the command string that was User response
entered, contact Software Support. Contact Software Support for further assistance.
AVZ1126S PLAN OPEN FAILURE RC = rcode AVZ1131S cmd NOT VALID COMMAND
REASON = rsncode
Explanation
Explanation
The TSO command (cmd) entered is not a valid
The attempt to open the application plan failed. command.

Review the return code and the reason code values Correct the value specified and re-enter the RUN
contained in the error message. Compare the return subcommand. If the error persists, contact Software
code and reason code with those listed in the IBM Support for further assistance.
SQL Application Programming Manual, and take the
appropriate action. If all attempts to correct the AVZ1132S cmd ENDED DUE TO ERROR
problem fail, contact Software Support for further
assistance. Explanation
AVZ1127S PLAN CLOSE FAILURE RC = rcode The DSN command (cmd) has ended due to an abend
REASON = rsncode detected in a user task.

The attempt to close the application plan failed. Correct the error condition in the program or TSO
command that was specified, and re-enter the DSN
User response command. If the error condition persists, contact
Software Support for further assistance.
Review the return code and the reason code values
contained in the error message. Compare the return AVZ1133S MODULE program NOT FOUND
code and reason code with those listed in the IBM
SQL Application Programming Manual, and take the Explanation
appropriate action. If all attempts to correct the
problem fail, contact Software Support for further The module name specified on the PROGRAM()
assistance. parameter of the RUN subcommand could not be
found.
AVZ1129R ENTER TSO COMMAND
User response
Explanation
Correct the value specified, and re-enter the RUN
Module OPDSN10 issued the current message as a subcommand. If the error persists, contact Software
prompt for a valid TSO command. Support for further assistance.
AVZ1134S UNABLE TO ESTABLISH THE STAX
EXIT

Explanation AVZ1138I SET_CLIENT_ID CALL FAILED
- DB2 NOT AT PROPER
OPDSN01 - the STAX manager was unable to establish MAINTENANCE LEVEL OR
the STAX exit. RELEASE. SUBSYSTEM: subsys

Attempt to invoke the DSN command again. If the A client requested a SET_CLIENT_ID command be
error persists, contact Software Support for further issued to Db2. This is usually invoked via the
assistance. SQLESETI client function. However, Db2 rejected the
AVZ1135S UNABLE TO TERMINATE THE STAX request. This probably is due to APAR PQ67691 (or its
EXIT equivalent) being applied.

OPDSN01 - the STAX manager was unable to This is not a serious problem. The Db2 DISPLAY
terminate the STAX exit. THREAD display just will not contain additional
information that was supplied by the client.
User response AVZ1154S COMMAND BUFFER INTERNAL
FORMAT ERROR
Attempt to invoke the DSN command again. If the
error persists, contact Software Support for further
assistance. Explanation
AVZ1136S STAX EXIT INTERNAL LOGIC During an attempt by the DSN command processor to
ERROR analyze the contents of the command buffer, it was
determined that the command buffer had the wrong
length, invalid operands, or the wrong format.
Explanation
OPDSN01 - the STAX manager determined that an User response
attempt was made either to remove the STAX exit
environment when one did not exist or to establish the Review the command string entered. Revise the
STAX exit environment when one already existed. command string, if appropriate. Re-enter the revised
command string. If the error condition persists
despite correcting errors in the command string that
User response was entered, contact Software Support for further
Contact Software Support for further assistance. assistance.
AVZ1137S ERROR EXECUTING TSO AVZ1163S COMMAND BUFFER PARSE ERROR

COMMAND RC = rcode REASON = - RC = rcode
rsncode
Explanation
Explanation The IBM TSO parse routine, IKJPARS, returned a non-
OPDSN10 detected that the command entered was a zero return code after attempting to parse the DSN
TSO command; however, an error was detected while command string.
attempting to invoke the TSO command. The above
message depicts the return code and reason code User response
values received from the product TSOEXEC service
routine. Review the accompanying TSO error messages in
the SYSLOG. Review the command string entered.
Revise the command string, if appropriate. Take action
User response recommended in the TSO messages manual. If all
Examine the TSO command entered, and correct the attempts at revised command string entry fail, contact
command string if an error was detected. If the error Software Support for further assistance.
condition persists despite correcting any command
AVZ1250I var1 var2
string errors, contact Software Support for further
assistance.
The message ID used to display parameter value The value of the ROLLBACKPOSITIVERC parameter
requested with an xxxPARM command. cannot be set to 'YES' because IGNOREPOSITIVESC
parameter is set to YES. ROLLBACKS for positive SQL
User response codes cannot be performed if they are being ignored.

User response
AVZ1251T THE VALUE OF THE parmname None. This message is informational only. If
PARAMETER WAS ROUNDED UP ROLLBACKS are required for positive SQL codes,
TO parmval BYTES then set IGNOREPOSITIVESC to 'YES', then set
ROLLBACKPOSITIVERC to 'YES'.
Explanation
AVZ1255E parmname - cannot be changed
The parameter was rounded to a 1K (1024) byte after initialization
boundary.
Explanation
User response
Many of product parameters may be changed at any
None. This message is for informational purposes only. time, but some of them can only be set once during
initialization. The parameter you attempted to change
AVZ1252T THE VALUE SPECIFIED FOR
must be set during product initialization.
THE parmname PARAMETER WAS
CHANGED FROM parmval1 TO
parmval2 User response
Update the initialization REXX exec xxxxIN00. These
Explanation changes will take effect the next time the product is
started.
The value of the parameter was changed.
AVZ1256E parmname - cannot be changed
User response
Explanation
Many of the S__ parameters may be changed at
AVZ1253T THE VALUE OF
any time; some of them can only be reset during
ROLLBACKPOSITIVERC WAS
initialization, while others are used merely for display
CHANGED TO 'NO' BECAUSE
purposes and cannot be reset at all. The parameter
IGNOREPOSITIVESC WAS SET TO
you entered may not be changed.
'YES'
User response
Explanation
Update the initialization REXX exec xxxxIN00. These
The value of the ROLLBACKPOSITIVERC parameter
changes will take effect the next time the product is
was changed to 'NO' because the IGNOREPOSITIVESC
started.
parameter was set to YES. ROLLBACKS for positive
SQL codes cannot be performed if they are being The variable fields of the message text are: parm
ignored. parameter name
AVZ1257E parmname - cannot be displayed
User response
None. This message is informational only. If Explanation
ROLLBACKS are required for positive SQL codes,
The parameter you selected cannot be displayed.
then set IGNOREPOSITIVESC to 'YES', then set
ROLLBACKPOSITIVERC to 'YES'.
User response
AVZ1254T THE VALUE OF
ROLLBACKPOSITIVERC CANNOT Check the manual to see if the parameter you
BE CHANGED TO 'YES' BECAUSE requested is spelled correctly.
IGNOREPOSTIVESC IS 'YES'

AVZ1258E desc - errmsg suffix User response
If you see this message, an internal error has occurred.
The ADDRESS AVZ processing routine found an error AVZ1264W No parameter value information is
in the parameter text string passed with the MODIFY available.
PARM command. The parameter text string is invalid.
MODIFY PARM command processing is aborted.
Explanation
User response The xxxPARM parameter you are using is not available.
The SAVZPARM command is terminated.
Validate the VALUE keyword value, correct it for errors,
and re-initiate the command. For more details on the
MODIFY PARM command, refer to your Product User's User response
Guide. The parameter you are trying to set using SAVZPARM
AVZ1259E PARAMETER parmname POINTS is not supported or not valid in this release of
TO UNINITIALIZED ENUMERATED the product. Check the parameter in the product
VALUE IN cblk AT addr documentation.
AVZ1265W WARNING: parmname
Explanation PARAMETER (val) CONTAINS
TOO FEW QUALIFIERS TO
During a parameter display operation, a product ENSURE PROPER HTTP COOKIE
parameter table entry pointed to an un-initialized field OPERATION
within a product control block. The field should be
initialized with one of the valid values enumerated for
the parameter. Explanation
The host domain name parameter contains too few
User response qualifiers (name segments separated by periods)
to ensure that Web browsers will properly store
The product parameter's value is displayed as and transmit HTTP cookies. At least three levels
"*INTERNAL-ERROR*", and processing continues. of qualification (two levels if the name ends
AVZ1262I grpdesc grpname with .com, .edu, .net, .org, .gov, .mil, or .int) are usually
required to ensure that HTTP cookies are stored and
later retransmitted properly.
Explanation
The parameter group (grp) being listed by this User response
xxxPARM command could not be found. The command
is terminated. The parameter is accepted but is always folded
to a lowercase string. The server's built-in browser-
based administration utilities require HTTP cookies for
User response proper operation. These administration utilities may
Review the xxxPARM command being executed, not function correctly using the host domain name
checking the group operand and whether or not there string now set.
is a group listing for it. Refer to the product Server AVZ1266W WARNING: parmname
Started Task Parameters Guide for the details on using PARAMETER (val) MAY CAUSE
the xxxPARM command and its group operand. INCONSISTENT OPERATION
AVZ1263E prefix-parmval-suffix USING HTTP COOKIES
This message is never meant to be seen. It is used The host domain name parameter contains a dot-
by OPPAFU to convert product parameters to printable notation format IP address. Browser anomalies may
character strings. arise that cause HTTP cookies to be stored improperly
or retransmitted incorrectly when using a dot-notation
host domain name value.
User response cannot be resolved, contact Software Support for
further assistance.
The parameter is accepted. The server's built-in
browser-based administration utilities require HTTP AVZ1290H jb parmname parmval
cookies for proper operation. These administration
utilities may not function correctly using the host Explanation
domain name string now set.
This message logs a change to the product parameters
AVZ1275S ABEND abcode IN via the ADDRESS AVZ MODIFY command. The
AUTHORIZATION ROUTINE message contains the name of the product parameter
modname+offset and its new value.

An abend occurred in the authorization checking No action is required. This message is written to the
routine. log for informational and tracking purposes only.
The variable fields of the message text are: parm
User response parameter field name parmval parameter field value
Contact Software Support for assistance. AVZ1291W Warning: parmname is an obsolete
The variable fields of the message text are: abcd parameter
abend code mod module name off module offset
AVZ1277S cblk Control block not found Explanation
This message is issued when an obsolete parameter
Explanation value is modified.
The MODIFY PARM functional routine has been passed

an invalid product control block name. User response
Refer to the product Server documentation for
User response information on this parameter. Modifying an obsolete
parameter may not have the desired effect. In many
First, check the MODIFY PARM command, correct any cases, obsolete parameters have no effect on the
errors, and rerun. If the problem persists, verify that server and are ignored. Obsolete parameters are
all of the product modules are at the same release normally removed from the product in the next
level. Also, check that the last product installation release. You should check the product initialization
was successful. If all of the above are checked exec (xxxxIN00) and remove all references to this
and the problem remains, gather all related problem obsolete parameter from it.
data (error data, SVFX level, install information), and
contact Software Support for further assistance. AVZ1292E Exit code ecode is invalid for
parmname
AVZ1281E service desc FAILED, RC=rcode,
DETECTED AT addr
Explanation
Explanation An invalid exit code has been defined in an
internal product control block that defines a product
This is a generic error message used to describe parameter table entry.
a wide variety of errors. The message text gives a
description of the current operation (service) and what
the current operation was trying to do. User response
This is an internal error. Please report this problem to
User response Software Support.
Check the error messages and the return code AVZ1293E errdesc
messages, and retry the operation. If the problem An attempt to set a product parameter has failed. The
error message describes the reason for the failure.

Review the error message, and attempt to correct the If you want to execute with security optimization
problem. active, you must stop and restart the product.
AVZ1294E desc OF process FOR PARAMETER AVZ1297T Logging processing terminated
CHANGE EVENT NOTIFICATION
FAILED WITH RC=rcode Explanation
The TERMINATELOGGING parameter was set to 'YES'
Explanation
causing all logging functions to halt. The product
A product parameter update attempt was made, continues to operate normally.
but the system was unable to properly notify an
asynchronous process of the change. The update to User response
the parameter may or may not have been made, but
in either case, the asynchronous process is now in an If you want to execute with logging active, you must
unknown state. stop and restart the product.
AVZ1298T Interval recording %1
User response
Review the error message and any others related Explanation
to the problem, and notify Software Support. Timing
Interval recording was enabled or disabled. The
errors during shutdown normally do not represent a
product continues to operate normally.
serious condition unless they occur consistently.
AVZ1295W PARM parmname AND ANY User response
DEFINE ISPFCONCAT ARE
MUTUALLY EXCLUSIVE. parmname You can reenable interval recording if the
WILL BE IGNORED. TERMINATEINTERVAL parameter is set to 'NO'.
AVZ1299T Interval recording terminated
Explanation
The xxxxIN00 EXEC specifies at least one Explanation
DEFINE ISPFCONCAT statement and the mutually
The TERMINATEINTERVAL parameter was set to 'YES'
exclusive ISPF PARM statement. All ISPF PARM
causing all interval recording to halt. The product
statements are ignored when at least one DEFINE
continues to operate normally.
ISPFCONCAT statement is specified. The following
is a complete list of the ISPF parameters that
will be ignored: EXECDSNAME, COMPEXECDSNAME, User response
ISPLLIBDSNAME, ISPMLIBDSNAME, ISPSLIBDSNAME
If you want to execute with interval recording active,
and ISPTLIBDSNAME.
you must stop and restart the product.
User response AVZ1340I echotext
Change the xxxxIN00 EXEC to specify the

Explanation
DEFINE ISPFCONCAT statements for all of the
required libraries and remove the obsolete PARM This message is simply an echo of a reply to a WTOR
NAME(ISP%LIBDSNAME) parameters. issued.
AVZ1296T Security optimization processing
terminated User response
None.
Explanation
AVZ1346E MESSAGE ID AND TEXT ARE TOO
The TERMINATESECOPT parameter was set to 'YES' LONG
causing all security optimization processing to halt.
The product continues to operate normally.
Explanation the problem cannot be resolved, contact Software
Support.
While building a WTO or WTOR parameter list, the
product detected that the combined message ID and AVZ1370H jobname rcode desccode mcscno
message text exceeds the system limits. The limit for a time msgID msgtext
WTO is 125 characters, and the limit for a WTOR is 122
characters. Explanation
This message is used to document an internally
User response generated WTO. It is written to the hardcopy log to
This could indicate an internal logic error within identify the source of the message issued.
the product. Contact Software Support for further msc represents the MCS flags
assistance.
cno represents the console number
AVZ1348E NO WTOR REPLY RECEIVED -
TIMER EXPIRED time represents a wait time if the REPLY keyword is
coded
Explanation
User response
A timeout has occurred prior to receiving the response
to a WTO/WTOR. None.
AVZ1400S TSO/E is not installed
User response
This could indicate an internal logic error within Explanation
the product. Contact Software Support for further TSO/E (IBM's program product number 5665-293) is
assistance. required to support the use of ISPF/AVZ.
AVZ1349I THE MESSAGE IDENTIFICATION
NUMBER IS wtoID User response
Verify that this product is available at your installation.
Explanation
AVZ1401S service CMD(modname) FAILED,
This message is simply an echo of the message RC=rcode
identification number returned by the WTO/WTOR to
identify the message.
Explanation
User response AVZ called TSO to execute ISPSTART and received a
non-zero return code. The ISPF initiation attempt is
None. The WTO ID can be used to DOM a highlighted aborted.
message.
AVZ1364S sysserv RETURN CODE = rcode User response
Review the message text, and check why the
Explanation request did not complete successfully. Review your
Some type of error occurred either in the system ISPF/AVZ environment, and take corrective action. If
management routines of the product or by invoking a the problem cannot be resolved, contact Software
system service (sysserv) directly. See the actual text Support.
of the message for an explanation. The error was AVZ1402S Dialog Manager service service
probably caused by a failure in an operating system error, RC=rcode
service.
Explanation
User response
A product internal routine called TSO to execute
Check if any other error messages were generated ISPSTART and got a dialog manager service error.
along with the error message above. If the combined
error messages are sufficient to explain the problem,
take whatever corrective action is appropriate. If

User response AVZ1420S service OF DIRECTED LOAD
LIBRARY (ddname) FAILED
Review the ISPF error, checking the service name RC=rcode
string for what service was invoked, and take
corrective action. For additional assistance, contact
your local S__ systems programming support group Explanation
AVZ1404S ABEND OCCURRED PROCESSING The S__ ISPF application attempted to do a
SUBROUTINE subrout IN MODULE directed load based upon a parameter setting in the
modname OPMS(ISPLLIBDSNAME).
service may be "allocation" or "deallocation"
Explanation
The product ISPF application ABENDed while User response
extracting information from constants in the Check the data set name specified in the
subroutine's prolog. aforementioned parameter. After correcting the name,
restart the Server address space.
User response AVZ1421E infotext COMMAND infotext
AVZ1405T ABEND OCCURRED PROCESSING Explanation
SUBROUTINE subrout IN MODULE The next message is not actually used by any code in
modname the product. The message is used to reserve a return
code. No action required.
Explanation
The product ISPF application ABENDed while User response
extracting information from constants in the None.
subroutine's prolog.
AVZ1423E errmsg
User response
Explanation
Product security has denied the current user access to
AVZ1406S THE ENTRY FOR SUBROUTINE Trace Browse.
subrout IN MODULE modname
POINTS TO SUBROUTINE subrout
User response
Explanation If this an undesirable situation, contact the product
systems support group to grant you the required
The ISPF application detected an error in a subroutine access.
vector table.
AVZ1424E CURRENT cmd COMMAND NOT
AUTHORIZED - errdesc
User response
Contact Software Support for further assistance. Explanation
AVZ1407T THE ENTRY FOR SUBROUTINE Authorization check failed. The use of AVZ/SWS is
subrout IN MODULE modname restricted by your installation security product.
POINTS TO SUBROUTINE subrout
User response
Explanation
Contact the person at your installation who installs and
The ISPF application detected an error in a subroutine maintains the product to obtain access authority.
vector table.
AVZ1440W ISPF LOADLIB at level lvl, but
Server LOADLIB at level lvl.
User response Processing continues.
Explanation AVZ1444S parmname PARAMETER
reqval SPECIFIED WITH
The version of the load library allocated to ISPF is at a ARCHTYPE(parmval)
different release than that of the server.
Explanation
User response
The Trace Browse/view program was invoked with
The product ISPF application continues. The invalid parameters.
inconsistency between the Server and the ISPF load
libraries should be resolved.
User response
AVZ1441S ABEND abcode IN
AUTHORIZATION ROUTINE Review the command string entered. Revise the
modname+offset command string, if appropriate. Re-enter the revised
Explanation was entered, contact Software Support for further
An abend occurred in the authorization checking assistance.
routine. AVZ1445S SYSTEM MANAGER SERVICE
service ERROR, RC=rcode
User response
Contact the person at your installation who installs and Explanation
maintains your installation security product. The product browse subroutine requested
AVZ1442S COMMAND BUFFER PARSE authorization in order to validate your request and
RC=rcode did not find the necessary control blocks for this
validation. The request is aborted.
Explanation
User response
The IBM TSO parse routine, IKJPARS, returned a
non-zero return code after attempting to parse a This message indicates a possible product ISPF
command string. The parse process for the command interface error. Gather the data, and contact your local
is terminated. systems programming support group.
AVZ1446S ISPF service service error, return
User response code = rcode
Gather the relevant problem data, and contact
your local product systems programming group for Explanation
assistance. AVZ invoked an ISPF service routine to accomplish the
AVZ1443S COMMAND BUFFER INTERNAL ISPF-related task indicated in the error message and
FORMAT ERROR received a non-zero return code.

During an attempt to analyze the contents of the Review the message text, and check why the request
command buffer, it was determined that the command did not complete successfully. Review your ISPF/AVZ
buffer had the wrong length, invalid operands, or the environment, and take corrective action. If the error
wrong format. persists, contact Software Support.
AVZ1447E Member member not found
User response
Review the command string entered. Revise the Explanation
command string, if appropriate. Re-enter the revised A BLDL failed to find the specified member.
was entered, contact Software Support for further
assistance.

Examine the data set concatenation to ensure that None. This message is for audit trail purposes only.
the proper libraries are allocated. If the error persists,
AVZ1452S ABEND abcode REASON rsn
contact Software Support for further assistance.
OCCURRED IN modname+offset
AVZ1448E func failed for member=member
RC=rcode Explanation
An abend occurred in the browse program.
Explanation
An I/O operation (func) failed while attempting to do a User response
BLDL.
Check for other errors, and correct the problem.
If unable to correct the problem, contact Software
User response
Use this message in conjunction with any other
AVZ1453S service OF desc FAILED, RC=rcode,
messages that may accompany it to resolve the
DETECTED AT addr
problem. You may also want to examine the data set
for problems. Once the problem is corrected, restart
the product. Explanation
AVZ1449E ISPF LOADLIB at version version1, This is a generic error message used to describe a
Server LOADLIB at version2, wide variety of product ISPF initialization, execution,
please correct inconsistency and termination errors. The message text provides
Explanation
The version of the load library allocated to ISPF is at a User response
different release than that of the server.
User response
The Diagnostic facility will terminate. The library If possible, fix the problem identified by the error
inconsistency should be resolved prior to invoking the messages, and restart the product. If the problem
ISPF application. cannot be resolved, contact Software Support.
AVZ1450H jobname subsysID AVZ1454S servrout errdesc FAILED,
Explanation CODE=rsncode
This message is used to provide an audit trail in Trace

Explanation
Browse when using the Trace Browse option of the
product. This is a generic error message used to describe a
wide variety of product ISPF initialization, execution,
User response and termination errors. The message text provides
the current operation and what the current operation
No action is required. This message is for audit trail (servrout) was trying to do.
purposes only.
AVZ1451H jobname subsysID ARCHIVE User response
REVIEW dsname Check the error messages and the return code
Explanation more error messages referring to the current problem.
This message is used to provide an audit trail in Trace
Browse when using the Trace Archive View function.
AVZ1455S Subsystem subsys not active
The specified subsystem is not active The product-related Db2 interface module tried to
communicate with the main product (not Db2) address
User response space. The main product address space was not
active. This error normally occurs at the start of SQL
Start the specified subsystem and then restart the application program execution.
ISPF application or choose another subsystem ID to
start the ISPF application with
User response
AVZ1456S ISPF service service error, return Ensure that the main product address space is active.
code = rcode. Unable to start ISPF Start or restart the main product address space, if
dialog. necessary. Rerun the SQL application program from
the beginning.
Explanation
AVZ1602E Product failed while SQL
AVZ invoked an ISPF service routine to start the ISPF application program executing
dialog and received a terminating return code.
Explanation
User response
The product-related Db2 interface module tried to
Review the message text, and check why the request communicate with the main product (not Db2) address
did not complete successfully. Review your ISPF/AVZ space. The main product address space was not
environment, specifically the DEFINE ISPFCONCAT active. This error normally occurs at the start of SQL
statements in the xxxxIN00 EXEC, and take corrective application program execution.
action. If the error persists, contact Software Support.
AVZ1457W Subsystem subsys not active User response
Ensure that the main product address space is active.
Explanation Start or restart the main product address space, if
necessary. Rerun the SQL application program from
The specified subsystem is not active
the beginning.
User response AVZ1603E Module DSNTIAR not properly

linked
The ISPF dialog could not find the specified
subsystem.
Explanation
AVZ1600E Module DSNACAF not properly
linked
load the address of a module needed to connect to
the actual Db2 system. The address field was zero. The
Explanation module could not be invoked, and the connection to
the actual Db2 system failed.
load the address of a module needed to connect to
the actual Db2 system. The address field was zero. The User response
module could not be invoked, and the connection to
Ensure that the product is properly installed. The load
the actual Db2 system failed.
module referred to in the error message must be
properly linked with the product module having the
User response same name. Relink the DSNITAR module, and rerun
the Db2 application program.
Ensure that the product is properly installed. The load
module referred to in the error message must be AVZ1700E service desc FAILED, RC=rcode,
properly linked with the product module having the DETECTED AT addr
same name. Relink the DSNACAF module, and rerun
the Db2 application program.
Explanation
AVZ1601E Product is not active at this time

description of the current operation (service) and what Explanation
the current operation was trying to do.
The ADDRESS SPOOL S/REXX Host Command
Environment or another routine using Sysout
User response Application Programming Interface (SAPI) common
Check the error messages and the return code routines is invoking a SubSystem (SSI) service. This
associated with this problem. There may be one or message is traced, prior to each invocation of the
more error messages referring to the current problem. IEFSSREQ SSI gateway macro.
messages, and retry the operation. If the problem User response
None. The indicated SSI function is invoked
AVZ1701E ERROR CODE queue SENDING immediately after this message is traced.
MESSAGE TO %2 QUEUE
AVZ1741T IEFSSREQ SSI return code is rcode
Explanation
Explanation
An error has occurred while attempting to send a
record to a product queue. The most likely cause An invocation of the SubSystem Interface (SSI) macro
for this message is that the queue is full - which IEFSSREQ has completed, and the resulting return
is indicated by an error code of 4. In the case of code is displayed in the message. This message is
either product load balancing queue, a queue full traced, following each SSI service request invocation
condition results in no further sessions being sent to when the SSITRACE command option is in effect.
this server by the Group Director until the pending
work on the queue has been significantly reduced. For User response
any other error code, no additional work will be sent
to this server and the server must be terminated and None. The SSI gateway interface has returned with the
restarted. IEFSSREQ return code shown in the message in R15.
AVZ1742T SSOBRETN FUNCTION-SPECIFIC
User response RETURN CODE IS rcode
Contact your local product systems programming

group for assistance. Explanation
AVZ1720E desc func FAILED, RC=rcode, An invocation of the SubSystem Interface (SSI) macro
DETECTED AT addr IEFSSREQ has completed with return code zero.
The function- specific return code is traced by this
message following each SSI service request invocation
Explanation made while the SSITRACE command option is in
This is a generic error message used to describe errors effect.
that occurred while attempting to allocate or free
(func) a product control block. Allocation failures are User response
typically an indication of insufficient virtual storage.
None. The indicated SSI function has completed with
the SSOBRETN return code shown in the message
User response
AVZ1743T WAITING FOR NEW SYSOUT FILES
Check the error messages and the return code FOR sec SECONDS
If possible, fix the problem identified by the error Explanation
messages, and retry the operation. If the problem The Sysout Application Programming Interface SSI
cannot be resolved, contact Software Support. service has been invoked with a PUTGET request that
AVZ1740T Invoking IEFSSREQ for SSI has returned an END-OF-DATA signal. The system will
function funcode - codedesc await new SYSOUT output to become available for the
indicated time period. This message is traced prior
to entered a WAIT for more SYSOUT output data to
become available.
User response The Host Command being processed will be failed with
a severe error signal.
None. A WAIT is entered for more SYSOUT output
which will expire after the indicated number of
seconds User response
AVZ1744T WAIT TIMELIMIT EXPIRED - END- Make additional workspace available for execution of
OF-DATA FOR SYSOUT the product REXX procedure. If the problem persists
and cannot be resolved by increasing the allocated
workspace, contact Software Support for assistance.
Explanation
AVZ1747T ADDRESS SPOOL ENCOUNTERED
A Sysout Application Programming Interface SSI ABEND CC=ccode, RS=rsncode
service request routine had entered a WAIT until AT modname+offset, PSW=psw,
additional SYSOUT output became available, following RETRY BY addr
receipt of an END-OF-DATA signal. The timelimit
for waiting on additional SYSOUT output to become
available has expired and the request routine will Explanation
now process the END-OF-DATA signal. This message The ADDRESS SPOOL Host Command Interface
is traced when the SSITRACE command option is in encountered an ABEND while processing the current
effect. request. The ADDRESS SPOOL host command will be
terminated with a failure signal.
User response
None. The WAIT for new SYSOUT output is terminated User response
and the procedure continues by recognizing the END- Check for other messages which may provide insight
OF-DATA signal. into the cause of the ABEND. Correct the Host
AVZ1745T NEW SYSOUT FILE NOW Command, or other conditional as applicable. If
AVAILABLE unresolved, contact Software Support for assistance.
AVZ1748T ABEND CC=ccode, RS=rsncode
Explanation AT modname+offset, PSW=psw,
ACCESSING dsect STRCT AT addr,
A Sysout Application Programming Interface SSI RETRY BY addr
service request routine had entered a WAIT until
additional SYSOUT output became available. The
primary subsystem has posted the requestor ready Explanation
and indicated the additional SYSOUT output is now The ADDRESS SPOOL JOBSTATUS command
available. This message is traced when the SSITRACE encountered an ABEND while processing the indicated
command option is in effect. Because another process extended status information DSECT. The command
or writer may select the same SYSOUT file for abandons further processing of the extended status
processing, there is no guarantee that the file will be information returned by the SSI service.
available when selection is requested.
User response
User response
Check for other messages which may provide insight
None. The WAIT for new SYSOUT output has into the cause of the ABEND. Correct the Host
completed and the procedure continues by attempting Command, or other condition as applicable. If
to select the new SYSOUT file for processing. unresolved, contact Software Support.
AVZ1746T IRXEXCOM action REQUEST AVZ1749T SSI ABEND CC=ccode, RS=rsncode
FOR varname FAILED WITH RC/ AT modname+offset, PSW=psw,
SHVRET=rcode/SHVRETval RETRY BY addr
The ADDRESS SPOOL Host Command Interface An SSI service request call to the IEFSSREQ interface
encountered an error while attempting to set, change, ABENDed. The ABEND completion code and reason
or drop (action) a variable in the S/REXX variable pool. are displayed in this message. The ABEND may be due
to some error in parameters passed on the service

request, or due to some permanent or transient User response
operating system failure.
Check for other messages which may provide insight
into the cause of the problem. Correct the Host
User response Command, or other condition as applicable. If
Check for other messages which may provide insight unresolved, contact Software Support for assistance.
into the cause of the ABEND. Correct the Host AVZ1753T SPOOL HCE SECONDARY
Command, or other condition as applicable. If ERRORrcode/rsncode: rsndesc
unresolved, contact Software Support.
AVZ1750T DDNAME ddname ALLOCATED TO Explanation
SYSOUT FILE dsname
An error has been encountered while processing
a SPOOL Host Command Environment request. A
Explanation previous error has already been logged and this error
A SYSOUT dataset has been allocated to the indicated occurred during Host Command Environment cleanup.
DDNAME. The caller may now process the SYSOUT file This message may be traced after an error, depending
using the DDNAME allocation. This message is traced on tracing options in effect while processing the
when the SSITRACE command option is in effect. If command. The request is being rejected with the
the DDNAME is "<SKIPPED>", no allocation has been original return and reason codes. This message
made for the indicate SYSOUT dataset, and processing describes the secondary error.
continues without an outstanding DDNAME allocation.
User response
User response Check for other messages which may provide insight
None. The SYSOUT allocation remains until the next into the cause of the problem. Correct the Host
SAPI request is processed, or until the environment is Command, or other condition as applicable. If
ended. unresolved, contact Software Support for assistance.
AVZ1751T DDNAME ddname DEALLOCATED AVZ1754T SPOOL CLEANUP ABEND

CC=ccode, RS=rsncode AT
modname+offset, PSW=psw,
Explanation action, RETRY RTNE AT addr
A SYSOUT dataset has been deallocated from the
DDNAME provided in the trace message. This message Explanation
traced when the SSITRACE command option is in
effect. An ADDRESS SPOOL environment cleanup routine
encountered an ABEND during resource recovery
processing. Processing to recovery resources
User response continues. One or more resources may not be
None. The SYSOUT file has been deallocated and recovered correctly.
processing continues.
AVZ1752T SPOOL HCE ERROR(rcode/ User response
rsncode): rsndesc Check for other messages which may provide insight
into the cause of the ABEND. Correct the Host
Explanation Command, or other condition as applicable. If
unresolved, contact Software Support.
An error has been encountered while processing a
SPOOL Host Command Environment request. This AVZ1755T SPOOL HCE MSGrcode/rsncode:
message may be traced after an error, depending rsndesc
on tracing options in effect while processing the
command. The request is being rejected with the Explanation
return code and reason code (in parentheses), having
the description given. An informational message traced while processing
a SPOOL Host Command Environment request. This
message may be traced after an error, depending
on tracing options in effect while processing the
command.
User response the problem cannot be resolved, contact Software
Support.
None. Processing continues.
AVZ2020S dsname FAILURE RC=rcode
AVZ1840E errdesc
Explanation
Explanation
An attempt to obtain or release storage on behalf of a
A syntax error (errdesc) has been detected while product subsystem data set (dsname) failed.
analyzing the EXECIO command.
User response
User response
Ensure that the address space requesting product
Correct the EXECIO command syntax errors, and subsystem data set services has a large enough region.
attempt to execute the REXX program again.
AVZ2021S desc CANNOT USE SUBSYS FILE
AVZ1841E errdesc, RC=rcode ALLOCATIONS
Some type of service routine (operating system or The product has detected that a system address space
product specific) failed. The error message identifies (e.g. *master*) or a TSO user has requested that a
the type of error . product subsystem data set be opened. This is not
allowed.
User response desc describes, for example, system tasks
Check the full text of the error message, and attempt
to correct the error. User response
AVZ1842E errdesc1 ddname errdesc2 The subsystem data set interface may only be used by
normal (non-system) started tasks and batch jobs.
Explanation AVZ2022S UNKNOWN SUBSYS OPEN
The ddname specified on the EXECIO command is not ENVIRONMENT ASID asid
allocated to the current job.
The error description has two parts, errdesc1 and Explanation
errdesc2. The product received an OPEN request for a
subsystem data set and is unable to determine what
User response environment the requesting address space (asid) is
running in.
Allocate the appropriate data set to the ddname, or
change the ddname. Then, rerun the REXX program.
User response
AVZ1843E ddname io FAILED, RC=rcode,
DETECTED AT addr The subsystem data set interface may only be used by
TSO server started tasks.
Explanation AVZ2023S No server block found for

USERID=jobname
Some type of error occurred during invocation of a
product I/O routine (io) associated with the EXECIO
command. Explanation
The product received an OPEN request for a
User response subsystem data set and found that the request was
not from a TSO server address space initiated as an
Check if any other error messages were generated outboard server by the product.

This is most likely an internal problem. Contact It is recommended that you modify the BLKSIZE on
Software Support for further assistance. the SYSTSIN DD card in the specified procedure to the
BLKSIZE specified.
AVZ2026S Invalid subsystem file count count
found for server jobname AVZ2032T SUBSYSTEM DATA req (reqcode)
PROCESSED FOR DDNAME
Explanation ddname - RC=rcode
The product has detected an internal error during

Explanation
close processing for a subsystem data set. The count
of open subsystem data sets for this address space The product's subsystem data set SSI intercept
has gone negative. routine has processed a request. This message traces
the interception request.
User response
User response
Gather the available problem data, and contact your
local product systems programming group for support None. This is a diagnostic message.
in this area.
AVZ2040T SRP RABND: SRVR NOT
AVZ2027S SUBSYS req cblk VALIDATION RESPONDING - ASID=asid
ERROR - ADDRESS addr ASCB=ascb TCB=tcb
The product has detected an error validating system A request for service has been made to server subtask
control blocks while processing an OPEN request (req) either inside or outside the main product address
for a product subsystem data set control block. space. The requesting task has attempted to revoke
the request due to timeout or shutdown, but the server
User response has not acknowledged. The request for service has
been forcibly revoked.
Gather the available problem data, and contact
your local product systems programming group for
User response
assistance.
Depending on the nature of the request, either
AVZ2030S ABEND abcode IN USER EXIT the requesting task or the server task TCB will be
modname+offset cancelled.
Explanation AVZ2041T SRP SFREE: RQSTR CANNOT

BE POSTED - CODE=pcode -
An abend occurred in the authorization checking ASID=asid TCB=tcb CNID=cnid
routine. TOKEN=token SMAF=addr

Contact the person at your installation who installs and A request for service has been made to a server
maintains the product security exit routine. subtask either inside or outside the main product
address space. The server task is unable to post the
AVZ2031W TSO SERVER (procedure) -
requestor task because the task has ended.
SYSTSIN BLKSIZE = blksize, USE
maxblksize
User response
Explanation The server task continues without posting the
requestor.
The BLKSIZE specified on the SYSTSIN DD card in the
TSO server started task JCL is one of the factors that AVZ2042T SRP RBIND: RC=rcode CMTC=addr
limits the length of commands that can be sent to BEFORE=word1 AFTER=word2
servers. TB=tb
This is a diagnostic message issued by the service This is a diagnostic message issued by the service
requestor/provider interface. requestor/provider interface.
word1 and word2 represent control words before and word1 and word2 represent control words before and
after image, respectively after image, respectively
tb represents a trace back point tb represents a traceback point

None. This message is for diagnostic use only. None. This message is for diagnostic use only.
AVZ2043T SRP RWAIT process: CMTC=addr AVZ2047T SRP RABND: RC=rcode CMTC=addr
BEFORE=word BEFORE=word1 AFTER=word2
TB=tb
Explanation
Explanation
This is a diagnostic message issued by the service
requestor/provider interface. This is a diagnostic message issued by the service
requestor/provider interface.
word represents a control word before image
word1 and word2 represent control words before and
User response after image, respectively
tb represents a traceback point
None. This message is for diagnostic use only.
AVZ2044T SRP RWAIT: RC=rcode CMTC=addr User response
BEFORE=word1 AFTER=word2
TB=tb None. This message is for diagnostic use only.
AVZ2048T SRP SBIND: RC=rcode
Explanation SERVER=svraddr RQSTR=reaaddr
TB=tb
Explanation
word1 and word2 represent control words before and
after image, respectively This is a diagnostic message issued by the service
tb represents a trace back point
tb represents a traceback point
User response
User response
AVZ2045T SRP RVOKE process: CMTC=addr
BEFORE=word AVZ2049T SRP SFREE: RC=rcode
SERVER=svraddr RQSTR=reqaddr
Explanation TB=tb

Explanation
word represents a control word before image
User response tb represents a traceback point

User response
AVZ2046T SRP RVOKE: RC=rcode CMTC=addr None. This message is for diagnostic use only.
BEFORE=word1 AFTER=word2
TB=tb

AVZ2050T SRP SPOST: RC=rcode AVZ2101S userID init FAILED - macro
CODE=pcode SERVER=svraddr RC=rcode
RQSTR=reqaddr TB=tb
Explanation
Explanation
The product security function processing routine
This is a diagnostic message issued by the service GETMAIN for some private storage failed. This storage
requestor/provider interface. is required for the processing of security control
blocks.
tb represents a trace back point
init represents the initialization type
User response
User response
Review the above storage GETMAIN error. Determine
AVZ2082S ss PRODUCT FAILURE DETECTED why storage is unavailable. Check for any exit that
limits usage of below-the-line private storage. Resolve
Explanation the above problems, and restart.
While processing this request, product main command AVZ2102E reqtype REQUEST FOR userID
processing function detected an abnormal shutdown FAILED - failrsn
of the product.
Explanation
User response
The product security function routine (reqtype)
Check the abend, what caused it, and how to best received a non-zero return code for the listed user ID.
restart the product. Resolve the current problem and
continue.
User response
AVZ2083W ss OUTBOARD TSO SERVER
Check the security error for the user ID. Correct the
jobname,ASID=asid FAILED
access problem, or contact your security administrator
Explanation
AVZ2103S userID rcode FAILED - RACF
The product End-Of-Memory (EOM) processing CODES rsncode text
detected the unexpected termination of an outboard
TSO server address space. The server should be
Explanation
restarted automatically by the product, providing that
the server control limits have not been modified. The product received an unknown return code from
RACF.
User response
User response
You may want to determine why the server failed.
Check the related RACF errors, and validate the
AVZ2084E service operand FAILED, RC=rcode,
return code in the RACF Messages and Codes Manual.
DETECTED AT addr
Contact your local systems programming group for
assistance.
Explanation
AVZ2104E userID init FAILED - failrsn
A CALLRTM invocation within the product End-Of-
Memory (EOM) failed. The EOM routine was attempting
Explanation
to cancel an outboard TSO server.
During LOGON command security checking, the
User response product security function routine received a non-zero
return code from the security package for the current
Check the service and return codes, and attempt userid.
to resolve the problem. If the problem cannot be
init represents the initialization type
User response AVZ2121S io FAILED,
RC=rcode, MEMBER=member,
Check the security error for the userid. Correct the DDNAME=ddname,
access problem, or contact your security administrator DSNAME=dsname
AVZ2106H userID init FOR conID AT t2 ON d2 Explanation
The product copy utility was copying members from
Explanation one PDS to another, and the copy failed.
Product security function routine issued this io represents the current I/O operation
informational message for the TSO address spaces.
init represents the initialization type User response
Check the return codes and related MVS error
User response messages. Ensure that the data sets have enough
None. This message is for informational purposes only. space. Take action as recommended for the return
codes.
AVZ2107H LOGON FAILED FOR userID. rcode1
rcode2 rsncode - errtext. AVZ2122I MEMBER member RECORD recno
LENGTH lgth IS INVALID
Explanation
Explanation
Product received a non-zero return code from a
LOGON request for an internal task. The product VB to FB conversion program found a
record with an invalid length.
The message has two return codes; rcode1 represents
the security module return code, and rcode2
represents the RACF (SAF) return code User response
Fix the invalid record, and rerun the VB to FB
User response conversion program.
Check the security error for the userid. Correct the AVZ2200E service desc FAILED RC=rcode,
access problem, or contact your security administrator DETECTED AT addr
AVZ2108E errmsg1 errmsg2 FAILED - Explanation
RC=rcode This is a generic error message used to describe
Explanation description of the current operation (service) and what
The product failed to extract the security product user
ID.
User response
User response Check the error messages and the return code
Validate the current system situation. Ensure that the more error messages referring to the current problem.
security package initialization is complete before the If possible, fix the problem identified by the error
product is started. messages, and retry the operation. If the problem
AVZ2120I MEMBER member - additinfo cannot be resolved, contact Software Support.
AVZ2300E NLS SERVICE ROUTINE (OPTRTB)
Explanation ABEND abcode, RS=rsncode AT
modname+offset
The product copy utility has started copying members
between PDSs.
Explanation
User response The NLS service routine detected an abend while
processing a request.

Check if any other error messages were generated The NLS service routine was invoked for conversion of
along with the error message above. If the combined EBCDIC pure DBCS data. An uneven number of bytes
error messages are sufficient to explain the problem, were present in the input stream.
take whatever corrective action is appropriate.
Otherwise, contact Software Support for assistance. User response
AVZ2301I NLS INVOKED WITH INVALID Handling of the current DBCS conversion is completed
FUNCTION CODE funcode by skipping the trailing, unmatched single byte.
AVZ2304I NO TRAILING SHIFT-IN
Explanation
DELIMITER BEFORE END OF DBCS
The NLS service routine was invoked with an invalid STRING - ASSUME SHIFT-IN WAS
function code (in hex). PRESENT

Check if any other error messages were generated The NLS service routine was invoked for conversion
along with the error message above. If the combined of EBCDIC mixed SBCS/DBCS string. While processing
error messages are sufficient to explain the problem, DBCS characters, the input stream was exhausted
take whatever corrective action is appropriate. before a shift-in character was found. DBCS sequences
Otherwise, contact Software Support for assistance. should always be terminated by a trailing shift-in byte.
AVZ2302I NO VALID MAPPING FOR src
CODEPOINT srccp TO output - User response
SUBSTITUTING subcp Handling of the current DBCS conversion is completed
by assuming that a shift-in character was present.
Explanation
AVZ2305I INVALID ENCODING PARAMETER
The NLS service routine was invoked for conversion of (parmname) DETECTED IN NLS E-
a DBCS character stream to/from ASCII/EBCDIC. No TO-A ENCODING ROUTINE
valid DBCS codepoint is defined for the input DBCS
code point. Explanation
src represents the source encoding, however srccp
The NLS service routine was invoked for conversion of
represents the source codepoint (in hex)
EBCDIC to ASCII. The encoding parameter is invalid.
subcp represents the substitution codepoint
User response
User response
The server assumes ISO-8859-1 SBCS EBCDIC to
The DBCS codepoint is converted to a standard ASCII conversion.
substitution character and the operation continues.
AVZ2306I DESTRUCTIVE OVERLAP
Ensure that the character stream passed to the
DETECTED IN SBCS E-TO-A OR A-
conversion routine contains only DBCS characters that
TO-EENCODING ROUTINE
have defined translation codepoint assignments. You
may need to define an ASCII/EBCDIC codepoint entry
during start-up for GAIJI codepoints or for codepoints Explanation
not built in to the system.
The NLS service routine was invoked for EBCDIC to
AVZ2303I UNEVEN BYTES IN PURE ASCII or ASCII to EBCDIC encoding of SBCS data.
DBCS STRING - byte FOUND Overlap of the input and output areas was detected.
IN TRAILING POSITION - The encoding request is aborted by deliberate
DISCARDED generation of an S0C3 abend.
User response
This is probably a logic error. Contact Software
Support.
AVZ2307I NO NLS TABLE FOUND FOR ASCII/ AVZ2310I UNSUPPORTED ESCAPE
EBCDIC MAPPING CODE tblname SEQUENCE seq FOR meth
The NLS service routine was invoked to look up an NLS The NLS service routine was invoked to decode data
EBCDIC to ASCII or ASCII TO EBCDIC translation table which contains multi-byte character sets including
(tblname). The requested table was not found. escape sequences. The escape sequence (seq)
reported in the message is not supported by the
User response server.
meth represents the character encoding method
Ensure that valid values are set for the server
ASCIIEBCDICMAPPING and CHARACTERENCODING
parameters. Check for other messages which indicate User response
whether a non-default setting was selected during
The decode routine copies the escape sequence and
processing of the current transaction. Also, check
converts it to SBCS EBCDIC.
the ISPF 5.19 display for a list of coded character
sets that are defined to the system. The server AVZ2311I UTF-8 ind NOT SUPPORTED FOR
will continue the operation using the built-in ENU NLS page - ASSUMING HOST CODE
ASCIIEBCDICMAPPING table for SBCS operations and PAGE IS "ENU"
will set the CHARACTERENCODING to ISO-8859-1.
AVZ2308I NO BUILT-IN NLS TABLE FOUND Explanation
FOR scheme (tblname)
The NLS service routine was invoked to decode or
encode a UTF-8 data stream. The server does not
Explanation support UTF-8 data streams for the selected EBCDIC
host code page (page).
The NLS service routine was invoked to encode or
decode data which contains a multi-byte character ind indicates either "decoding" or "encoding"
set algorithm. A built-in NLS character set conversion
table was not present. User response
scheme represents the character encoding scheme
The routine assumes the EBCDIC host code page is set
to ENU (IBM-1047). This may lead to incorrect results
User response when the input or output stream has been processed.
The encode/decode operation is aborted by deliberate AVZ2312I BYTE byte IS AN INVALID UTF-8
generation of an S0C3 abend. Check for reasons BYTE - SKIPPING TO NEXT BYTE
why the built-in table described in the message is OF STREAM
undefined to the system.
AVZ2309I UNPAIRED scheme DBCS LEAD- Explanation
BYTE byte SKIPPED BY DECODER
The NLS service routine was invoked to decode a
UTF-8 data stream. An invalid lead-byte value has
Explanation been found in the UTF-8 stream (x80-xBF, or xF8-xFF).
The decoder will skip over the offending byte and
The NLS service routine was invoked to decode data
ATTEMPT to re-orient at the next input byte position.
which contains a multi-byte character set algorithm. A
single byte was found which should be the first byte
of a two-byte DBCS character sequence; however, no User response
more input bytes were present.
The decode operation continues at the next input
scheme represents the character encoding scheme stream position. This may lead to additional errors or
incorrect decoding of the stream.
User response AVZ2320T DBCS conversion bypassed for
The decode routine skips the invalid DBCS lead-byte parameter parmno: rsn
and omits it from the EBCDIC result.

The DBCS Dynamic Conversion Service bypassed Correct the DEFINE PUBLISH statement to specify a
conversion of the specified parameter to graphic for userid authorized to access the particular Db2.
the reason listed. The operation will be passed on to
AVZ2405E DB2 system db2ID not defined
Db2 which will most likely issue an SQLCODE = -301
error.
Explanation
User response Db2 Streams Collector received a return code 8 and
This is a programming error in the client application. reason code 00F30006 attempting to create a CAF or
RRSAF connection to the specified Db2.
AVZ2401E db2ID conntype func ERROR,
RC=rcode REASON=rsncode User response
Correct the DEFINE PUBLISH statement
Explanation
Db2 Streams Collector received an unexpected failure AVZ2406T db2ID conntype ISSUED, RC=rcode
return code from a CAF or RRSAF function REASON=rsncode

Refer to the Db2 Messages and Codes for further Trace Streams Db2 CAF and RRSAF return codes
details on the error. Message 2402 may be issued as
well. User response
AVZ2402E db2ID : msgtext None
AVZ2407T PUBLISH SOURCE db2ID USERID
Explanation userID LOGON FAILED rcode1
Db2 Streams Collector received an unexpected failure rcode2 rsncode
return code from a CAF or RRSAF function
Explanation
User response The PUBLISH USERID specified could not be logged
Refer to the Db2 Messages and codes for further on. This message should be followed by another
details on the messages. message with the SAF error message.
The message has two return codes; rcode1 represents
AVZ2403E conntype module mismatch for
the security module return code, and rcode2
DB2 subsystem db2ID
represents the RACF (SAF) return code.
Explanation
User response
Db2 Streams Collector received a return code 4 and
The Streams routine is aborted. Ensure that the userid
reason code 00C10823 attempting to create a CAF or
specified is correct.
AVZ2408E Streams plan plan not defined TO
User response db2ID
Change the STEPLIB used by the product to point to

the highest level version of Db2
Explanation
Return code 8 Reason code 00F30040 received
AVZ2404E User ID userID does not have
attempting to open the specified plan.
authority to access DB2 db2ID
User response
Explanation
The Streams source task is aborted. Ensure that the
Db2 Streams Collector received a return code 8 and
specified plan is bound.
reason code 00F30013 attempting to create a CAF or
AVZ2409I srctype %2 Streams source task Explanation
now starting
This message emits information related to the Trace
Streams Db2 routines.
Explanation
The DEFINE PUBLISH TYPE(DB2) task is starting. User response
None
User response
AVZ2414W UNABLE TO FIND DATASET NAME
This message is for informational purposes only. FOR DDNAME ddname
AVZ2410I Streams destination task for
destination starting Explanation
Streams destination is unable to access the Dataset
Explanation name for the listed DD name, which contains XML
DEFINE PUBLISH DESTINATION task starting formatting information.

None None
AVZ2411W PUBLISH - service OF desc FAILED, AVZ2415E CANNOT SERIALIZE ON db2ID

RC=rcode QUALIFIER qualifier
The product tried to initialize or a Publish task It appears that another copy of the product is using
during product initialization or termination. An internal the same Event Publisher Db2 tables that this copy of
service routine called during Publish task initialization the product is attempting to use.
or termination exited with a non-zero return code.
User response
User response No action is required.
Check the error messages and the return code AVZ2416S Streams support not configured -
associated with this problem. There may be one or it cannot be initialized
the current Publish task initialization or termination
problem. Also, check for storage allocation errors Explanation
or abends. If possible, fix the problem identified by None.
the error messages, and restart the product. If the
problem cannot be resolved, contact Software Support
to obtain additional assistance. User response
AVZ2412I Streams tasktype task for
destination terminating AVZ2417E Invalid return from Streams rule
rulename rval
Explanation
DEFINE PUBLISH task terminating Explanation
An SEF rule (rulename) for a Streams event provided a
User response syntactically invalid return value (rval). The event was
not Published.
None
AVZ2413T data1 data2 data3 data4 data5 User response
data6 data7 data8 data9 %SK
Correct the SEF rule and retry.

AVZ2418T PUBLISH ITEM keyfield FOR Explanation
SOURCE srcID - errtext
- STATUS=scode RC=rcode A saved ODBC generated destination is requesting an
REASON=rsncode DIAG=diaginfo- unsupported protocol. The destination is ignored.
FAILED
User response
Error attempting to Publish an update for the particular AVZ2423E MACHINE machID (index) DOES
item. NOT HAVE A SAVED URL

Attempt to correct the error A saved ODBC generated TCPIP destination does not
AVZ2419T PUBLISH DESTINATION dest have a saved URL.
FAILURE errtext - STATUS=scode
RC=rcode REASON=rsncode User response
DIAG=diaginfo - WILL RETRY
Have the client process reissue the
ENABLETRANSMISSIONS ODBC call. If the problem
Error attempting to Publish an update for the particular AVZ2424E MACHINE machID (index) INVALID
item. URL errcode - detailed

Attempt to correct the error A saved ODBC generated TCPIP destination have an
AVZ2420E DB2 db2ID CONTENTION ON table invalid saved URL.
CODE -sqlcode - WILL RETRY
LATER User response
Have the client process reissue the
Explanation ENABLETRANSMISSIONS ODBC call. If problem
Timeout detected trying to access one of the Streams persists contact Software Support.
tables. AVZ2425E WORKTABLE UPDATE FOR keyfield
destination FAILED - ROW NO
User response LONGER EXISTS
None - the Streams will retry the request

Explanation
AVZ2421E DUPLICATE PUBLISH OF pkgdest
(HTX) TO destination IGNORED A deferred status for the publication of a particular
item could not be reflected into the worktable because
the row describing the item no longer exists.
Explanation
An Streams rule tried to ship the same update more User response
than once to a particular destination (pkgdest). Only
the first instance was published. Ignore if the row was deleted while the status was
outstanding. If problem persists contact Software
Support to obtain additional assistance.
User response
AVZ2426E MACHINE machID (index) DOES
Correct the SEF rule. NOT HAVE A SAVED MQ NAME
AVZ2422E MACHINE machID (index) IS
USING UNKNOWN PROTOCOL Explanation
protocol
A saved ODBC generated MQSeries destination does
not have a saved target MQ name.
Have the client process reissue the Ensure that the MQREPLYQNAME was properly defined
ENABLETRANSMISSIONS ODBC call. If problem in the MQSeries catalog.
persists contact Software Support to obtain additional
AVZ2431I jobname Streams exit exit enabled
assistance.
AVZ2427E Task task not started - not licensed Explanation
for feature.
The Streams CICS Global User Exit has been enabled
during CICS PLTPI phase three initialization.
Explanation
None. User response
User response
AVZ2432E UNRECOGNIZED MQ REPORT
MESSAGE RECEIVED ON
AVZ2428E task SOURCE TASK PARAMETER mqreplyqname (corrID)
MQREPLYQNAME mqreplyqname
IGNORED - NOT LICENSED FOR Explanation
USE
An MQSeries report message had an unrecognized
correlation ID value (corrID).
Explanation
None. User response
Ensure that the MQREPLYQNAME MQSeries Q is
User response
not used for anything other than Streams as an
Contact Rocket Software Support. MQREPLYQNAME.
AVZ2429E NON-REPORT MQ MESSAGE AVZ2433E EVENT DEFINITION BUILD FAILED
RECEIVED ON mqreplyqname FOR source event datamap
(start) - IGNORED
Explanation
Explanation
Streams source task initialization failed while
An MQSeries message other than a status report was attempting to build an event definition from the a data
received on the MQREPLYQNAME. map.
start represents the start of the text
User response
User response Ensure that the data map used in the event definition
is correct and matches the layout of the data to be
Ensure that the MQREPLYQNAME MQSeries Q is
captured. in the case of an IMS/DB map, make sure
not used for anything other than Streams as an
that a COBOL map that defines the data fields has
MQREPLYQNAME.
been successfully merged.
AVZ2430E source MQSERIES MQ FAILURE
AVZ2434W tskname tsktype DB2 EVENT
ON mqreplyqname RC=rcode
TABLE ROWNUM percent FULL
REASON=rsncode - errdesc
Explanation
Explanation
The specified publish task EVENT table,
An unexpected MQSeries failure occurred when
DTRIGGERTABLE, column name ROWNUM has a value
attempting to record report messages to the WorkFile.
that is nearing the end of its available range. It must
be reset before it runs out of available numbers in its
range. The range is 1 to 2147483647. The percent
specified in the message shows how much of that
range has been used.

User response AVZ2440I VSAM event capture enabled
Quiesce the source task or stop the product and DROP
and CREATE the proper TRIGGERTABLE. Explanation
AVZ2436S jobname error inquiring CICS VSAM event capture has been enabled by this product
system information for Streams - subsystem.
EIBRESP: respcode
User response
Explanation Informational.
The Streams PLTPI program encountered an error AVZ2441E Error in enabling VSAM event
inquiring CICS system information. capture, RC=rcode

Probable CICS error. Check the system log for errors. An error was encountered while enabling VSAM event
AVZ2437S jobname error enabling Streams capture.
exit program program for exit exit
- EIBRESP: respcode User response
Explanation
AVZ2443T VSAM caller is in key callers and
The Streams PLTPI program encountered an error only key 8 callers are supported,
enabling a Streams exit program. VSAM capture terminated.

Check that the exit program has been correctly defined Only key 8 programs are supported for VSAM capture.
to CICS.
AVZ2438S jobname error extracting GWA User response
address for Streams program
program - EIBRESP: respcode Contact Software Support.
AVZ2444E VSAM capture prefix not set, VSAM
Explanation capture not enabled
The Streams PLTPI program encountered an error

extracting the Global Work Area address for the exit Explanation
program. A capture prefix (PUBLISHVSAMPREFIX) must be
specified to capture VSAM events.
User response
Probable CICS error. Check the system log for errors. User response
AVZ2439I VSAM capture not enabled, Contact Software Support.
already being processed by AVZ2445S jobname error operation Streams
subsystem subsys exit program program - EIBRESP:
respcode
Explanation
VSAM capture is already being processed by another Explanation
product subsystem. Only one product subsystem is The Streams PLT program encountered an error
allowed to capture VSAM events. starting or stopping the user exit program.
operation indicates "STARTING" or "STOPPING"
User response
Informational.
Check that the exit program has been correctly defined Return and reason codes can be found in msg
to CICS. IDC3009I
AVZ2446I jobname enabling Streams exit AVZ2450I Unable to allocate capture file file,
program program for exit exit RC = rcode, REC = rsncode
The Streams PLTPI program is about to enable the exit An error occurred trying to allocate the VSAM capture
program. file.

None. This message is for informational purposes only. return and reason codes can found in "Authorized
Assembler Services Guide"
AVZ2447I jobname operation Streams exit
program program AVZ2451I Unable to open capture file file, RC
= rcode
Explanation
Explanation
The Streams PLT program is about to start or stop the
exit program. An error occurred trying to open the VSAM capture file.
operation indicates "STARTING" or "STOPPING"
User response
User response return code documented in "Macro Instr for Data Sets"
None. This message is for informational purposes only. AVZ2452I Capture file file is not SMS
managed, but SMS is required for
AVZ2448I jobname Streams exit program
the capture file
program operation
Explanation
Explanation
The capture file is non-sms, but SMS management is
The Streams global user exit program has been started
required for the capture file.
or stopped.
operation indicates "STARTED" or "STOPPED" User response
Alter SMS ACS rules as required to SMS manage the
User response
data set.
AVZ2453S Streams work file not allocated -
AVZ2449I Unable to create capture file file, Streams source task terminated
RC = rcode1, REC = rsncode, SSIRC
= rcode2 Explanation
The Streams global user exit is about to write an event
Explanation
record to the event file.
An error occurred trying to create the VSAM capture
file. User response
Check that the file has been correctly allocated and
represents the catalog management return code, and
defined to CICS.
rcode2 represents the SMS SSI call return code.
The variable fields of the message text are: Streams
CICS Source name
AVZ2454E tskname tsktype TASK NOT
STARTED - MQSERIES NOT ACTIVE

The specified publish task could not be started Make more space available to the WORK file. If
because MQSeries is not active. additional extents may be allocated to the WORK
file, make more space available on the volume(s) the
User response WORK file is on.
Ensure that MQSeries is active on the system and AVZ2458E SOURCE NAME tskname NOT
that the Streams initialization exec sets the MQACTIVE ACTIVE OR NOT FOUND
parameter to YES.
Explanation
AVZ2455E tskname tsktype filetype FILE,
NAME filename VERSION No active publish source task with the specified
MISMATCH, EXPECTED verno1, name has been found. The requested action was not
FOUND verno2 completed.

The specified publish task could not be started Enter an active source task name in the request.
because the file contained data with a version number
AVZ2459E UNICODE CONVERSION for
that is not supported by this release.
tblname FROM source TO target
The message contains two version numbers, verno1 NOT SUPPORTED
and verno2, which represent the expected version
number and found version number respectively
Explanation
User response Unicode conversion services on this system are not
configured to support the data conversion required by
Ensure that the proper EVENT or WORK or Db2 file is a Streams definition.
used with Streams. Most likely, a different version was
used to create the indicated file.
User response
AVZ2456W tskname tsktype WORK FILE,
Reconfigure z/OS Unicode conversions services to
DDNAME ddname percent FULL
support codepage conversions between the listed
CCSIDs (source and target).
Explanation
AVZ2460E THE ZEVRAW SPECIFICATION
The specified publish task WORK file has records that ON EVENT DEFINITION src
use the specified percent of available space. It is def REQUIRES THE RAW DATA
possible that remaining space is lower than indicated OPTION
by this message.
Explanation
User response
The event definition requested ZEVRAW formatting.
Ensure that the WORK file has sufficient free space to This require that either the raw data option be
continue normal operation. selected, or a rule is specified on the source (src) or
event definition (def).
AVZ2457E tskname tsktype WORK FILE,
DSNAME dsname COMPLETELY
FULL User response
Edit the source or the event definition to specify a rule
Explanation for event routing, or select the raw data option on the
event definition.
The specified publish task WORK file has been
completely filled up with records, and VSAM has AVZ2461S Error loading Streams program -
refused to write additional records. The Publish Source program
task has stopped.
Explanation AVZ2465I Streams native VSAM capture not
enabled
The Streams PLT program encountered an error trying
to load the named program.
Explanation
User response VSAM event capture has not been enabled by this
product subsystem.
Check that the program has been correctly defined to
CICS. Sample CICS definitions are distributed in the
CNTL library CICSCSD member. User response
The variable fields of the message text are: program Informational.
name
AVZ2466W tskname tsktype WORK FILE,
AVZ2462E EVENT DATA TOO LONG FOR DDNAME ddname EXTENDED,
source event datamap NOW percent FULL
Streams source task initialization failed while The specified publish task WORK file has records
attempting to build an event definition (event) from the that use the specified percent of available space.
a data map. The percent used has decreased, indicating that the
dataset has been extended.
User response
User response
Ensure that the data map used in the event definition
is correct and matches the layout of the data to be Ensure that the volume containing the WORK file has
captured. in the case of an IMS/DB map, make sure sufficient free space to allow any additional extension
that a COBOL map that defines the data fields has of the WORK file needed to continue normal operation.
been successfully merged.
AVZ2467E MORE THAN ONE EVENT TABLE
AVZ2463E DATA CAPTURE CHANGES NOT CANNOT BE ACTIVE FOR SOURCE
DEFINED FOR event tblqual tskname. ALL ACTIVE EVENT
tblname TABLES FOLLOW.
Streams source task initialization failed while A Streams source task has more than one Event Table
attempting to build an event definition (event) for a marked active. Only one Event Table may be marked
Db2 table. active at any time. A list of active Event Tables follows.

Ensure that the table referred by the event definition Ensure that only one Event Table is marked active.
has the DATACAPTURE attribute on.
AVZ2468E Streams source tskname, event
AVZ2464E MONITOR2 and TRACE Authority table table in map map marked
are required for user ID userID. active.
Streams Db2 IFI source task user ID requires Db2 The specified publish source task has this Event Table
SYSOPR authority to issue a START MONITOR TRACE marked active. Only one Event Table may be marked
command. active at any one time.

Ensure that the user ID specified in the Db2 IFI source Ensure that only one Event Table is marked active.
definition has been granted SYSOPR authority.

AVZ2469E Streams source tskname, event User response
table table in map map, cannot
find map map. Remove member SDPHDBUG to prevent these
messages.
Explanation AVZ2473I routine text1 text2 text3 text4
The specified Event Table for this source references

a map that cannot be found, or is not active, or not Explanation
enabled for event publishing. This message tracks the generic debugging message
issued by Streams capture process (routine)
User response initialization. The presence of the SDPHDBUG load
module in the capture process load library will
Ensure that the Event Table references active maps, cause these debug messages to be issued. To create
and that each is enabled for event publishing. SDPHDBUG, edit member ZEVDBUG from the product
AVZ2470S Streams IMS source task srcname sample library to set desired debug trace options and
not activated - RRS not enabled assemble and link as SDPHDBUG.

The Streams global IMS source task (srcname) could Remove member SDPHDBUG to prevent these
not be activated because RRS was not enabled for this messages.
Streams server. AVZ2474I routine text1 text2 text3 text4

Change the server initialization parameters to specify This message tracks the generic debugging message
RRS(YES) and restart the server. issued by Streams event capture (routine). The
AVZ2471S Streams IMS source task srcname presence of the SDPHDBUG load module in the
not activated - EVENTQ not capture process load library will cause these debug
defined messages to be issued. To create SDPHDBUG, edit
member ZEVDBUG from the product sample library to
set desired debug trace options and assemble and link
Explanation as SDPHDBUG.
The Streams IMS source task (srcname) could not
be activated because the required MQSeries event User response
repository was not correctly defined.
Remove member SDPHDBUG to prevent these
messages.
User response
AVZ2475I routine Blocksize:maxsize
Correct the DEFINE SEM_ENDPOINT specification for Blocklen:length Blockid:blkID
ZEV.EVENTQ in the server initialization parameters and
restart the server.
Explanation
AVZ2472I routine Capture successful/failed
rcode rsncode Logstream debugging message issued by Streams
event capture (routine). The presence of the
SDPHDBUG load module in the capture process load
Explanation library will cause these debug messages to be issued.
Generic debugging message issued by Streams To create SDPHDBUG, edit member ZEVDBUG from
capture processes (routine). The presence of the the product sample library to set desired debug trace
SDPHDBUG load module in the capture process load options and assemble and link as SDPHDBUG.
library will cause these debug messages to be issued.
To create SDPHDBUG, edit member ZEVDBUG from User response
the product sample library to set desired debug trace
options and assemble and link as SDPHDBUG. Remove member SDPHDBUG to prevent these
messages.
AVZ2476I routine Streamtoken: token
Logstream debugging message issued by Streams Probable CICS error. Check the system log for errors.
event capture (routine). The presence of the
AVZ2480I Streams server version ver1 does
SDPHDBUG load module in the capture process load
not match DB2 function version
library will cause these debug messages to be issued.
ver2
To create SDPHDBUG, edit member ZEVDBUG from
the product sample library to set desired debug trace
options and assemble and link as SDPHDBUG. Explanation
The Streams server that has been configured to
User response publish Db2 events does not match the version of the
Remove member SDPHDBUG to prevent these Streams Db2 wake_publish function.
messages.
User response
AVZ2477I routine text1 text2 text3 text4
Check that the correct version of the wake publish
function load module (SDD2PCRU) is in the Db2
Explanation
RUNLIB, and check that the Streams server is at the
This message tracks the generic debugging message same level.
issued by Streams event capture (routine). The
AVZ2481I jobname Streams version ver
presence of the SDPHDBUG load module in the
SFVXno date time
capture process load library will cause these debug
messages to be issued. To create SDPHDBUG, edit
member ZEVDBUG from the product sample library to Explanation
set desired debug trace options and assemble and link
Streams CICS load library maintenance level
as SDPHDBUG.
information.
User response
User response
Remove member SDPHDBUG to prevent these
None.
messages.
AVZ2482T RENDEZVOUS CALL FAILED
AVZ2478E tskname tsktype TASK NOT
- RC=rcode1 REAS=rsncode
STARTED - STRNO val TOO SMALL
- ENCLAVE RC=rcode2
FEEDBACK=(fbcodes)
Explanation
The specified publish task could not be started Explanation
because there were not enough VSAM strings
An attempt to send a message to a Tibco Rendezvous
allocated at startup.
destination failed.
User response The message contains two return codes; rcode1

represents the rendezvous interface return code, and
Ensure that the PUBLISHSTRNO value is one larger rcode2 represents the LE/370 enclave manager return
than the number of Streams SOURCE tasks. code
AVZ2479S jobname ERROR OBTAINING
CONTAINER DATA FOR container - User response
EIBRESP: respcode
Check for other messages indicating the cause of the
failure, and resolve the problem, if possible.
Explanation
AVZ2483T Streams parmname parameter not
The Streams CICS event processing adapter specified
encountered an error getting data from a channel
container.
Explanation
The file dataset name prefix was not specified. The file
cannot be allocated.

Check that the parameter is correctly specified in the This message is issued when there was a failed
server initialization exec (xxxxIN00) attempt to load the IMS data capture user exit
specified with the PUBLISHIMSUEX1 parameter.
AVZ2484T jobname Streams Name/Token Check that the correct exit program name has been
operation result for token specified and that the program has been copied to the
Streams server load library. if more than two minutes
Explanation expire while waiting for your reply or three invalid
replies are made, the default action of CANCEL will be
The Streams capture process has attempted a name/
taken.
token operation.
operation may indicate "CREATE", "RETRIEVE", or User response
"DELETE"
Reply GO to continue Streams server initialization
token may indicate "SUCCEEDED" or "FAILED" Reply CANCEL to terminate Streams server
initialization
User response
AVZ2489E Invalid Streams initialization
None reply: reply
AVZ2485I Streams DB2 FUNCTION VERSION
ver date time Explanation
An invalid reply was specified to the Streams
Explanation initialization console message. The message causing
the error will be reissued so that you can correctly
Streams Db2 exit maintenance level information
reply. After three invalid replies for the same message,
date and time indicate time and date of assemble default action will be taken. For a description of the
default action, see the explanation of the original
message.
User response
None. User response
AVZ2486I Streams source improper version Determine the proper reply from the text of the
ver found ver message, and reply correctly.
AVZ2490E Streams reply wait exceeded 2
Explanation
minutes. Default used
Streams found a record with an improper version in it.
Explanation
User response
The product waited over two minutes for a reply to the
The improper record will be deleted. Streams initialization message. Since no response was
during that time, default action was taken.
AVZ2487T PUBLISH LOGON FAILED - errmsg
User response
Explanation
None. If a reply was desired, you will need to speed
The PUBLISH LOGON failed for the following reason.
User response AVZ2491E 3 Invalid Streams replies. Default

taken
The Streams routine is aborted. Ensure that the userid
specified is correct.
Explanation
AVZ2488R REPLY 'GO' TO CONTINUE, OR
Three invalid replies were made to a Streams
'CANCEL' TO TERMINATE Streams
initialization message. Since no correct response was
Initialization
received, default action was taken.
None. Reply as required next time. Check other MQSeries activity to be sure messages or
responses have not been inadvertently discarded.
AVZ2492I Streams not active on this server
AVZ2496W TASK task LOG logstream
Explanation RECORD WITH STATUS statcode,
DEST. dest., KEY timestamp,
An attempt was made to access the Streams control CONFIRMATION ARRIVED,
task and it was not active. RECORD MISSING

If the server is intended as a Streams server, check the A Streams task received an MQSeries confirmation
IN00 initialization parameters for the server. that did not match the next record in the task
Logstream. The confirmation is discarded.
AVZ2493E Streams TASK task UNABLE TO
operation LOGSTREAM logstream,
RC=rcode, RSN=rsncode User response
Check other Logstream activity to be sure messages
Explanation have not been inadvertently discarded.
A Streams task attempted an operation on an MVS AVZ2497W Logstream operation exp
logstream and it was not successful.
Explanation
User response
A Logstream operation received a return code. This
Determine the problem from the logstream message tries to explain (exp) the return code and
function return code and reason code, and reason codes.
correct the error. These codes are documented in
SYS1.MACLIB(IXGCON) and in z/OS MVS Assembler
User response
Services Reference in IXGxxxx macros return codes.
Check other Logstream messages to determine the
AVZ2494W INVALID RECORD FOUND IN task
problem.
LOGSTREAM logstream, FOUND
STATUS scode, TO dest. KEY AVZ2498T Streams does not support Tibco
timestamp Rendezvous destinations
A Streams task found a record in its MVS logstream Tibco Rendezvous destinations are not supported.
with an invalid status (scode) and destination (dest)
name. The record is discarded. User response
Delete Tibco Rendezvous destinations.
User response
Check other Logstream activity to be sure data has not AVZ2499T Streams does not support Oracle
been corrupted with data from some other program. destinations
AVZ2495W TASK task LOG logstream MISSING Explanation

REPLY, STATUS scode, DEST. dest.,
KEY timestamp Oracle destinations are not supported.

A Streams task received an MQSeries confirmation Delete Oracle destinations.
that did not match the next record in the task
AVZ2500T source COPYWORK time1 time2
Logstream. The record is discarded.

Streams trace record. An Event has been copied from Streams trace record. An Event is being queued for
the trigger table to the Work file. sending to a destination (dest).
The message contains two time variables; time1
represents the time of the update, time2 represents User response
the time the record was copied
None
User response AVZ2506T source DOPRUNE time count
None
Explanation
AVZ2501T source RUNRULES
Streams trace record. Old Publish records (counted by
count) are being pruned from the Workfile.
Explanation
Streams trace record. The Event processor is running User response
SEF rules for records in the Work file.
None
User response AVZ2507T source WAITABIT caller sec

SECONDS
None
AVZ2502T source DYNDEST keyfield machID Explanation
index
Streams trace record. The Streams task is waiting for
more work.
Explanation
caller represents the calling subroutine
Streams trace record. An Event is being processed for
a dynamic JCA 1.5 destination. The identifiers for the User response
JCS 1.5 Adapter requestor are traced.
None
User response AVZ2508T source PREPROC dest keyfield urID
None
Explanation
AVZ2503T dest SENDPLUP-RESTART
Streams trace record. The Streams task is
preprocessing an update for transmission to a
Explanation
destination.
Streams trace record. Processing for an Event source
is being restarted to a destination (dest). User response
None
User response
AVZ2509T source PREPROC **SKIP**
None
keyfield
AVZ2504T source MQMARK
Explanation
Explanation
This message documents the streams trace record.
Streams trace record. MQSeries processing for an The Streams task preprocessor has determined that
Event source is marking the current status of update an update should NOT be sent to any destination.
records.
User response
User response
None
AVZ2510T source POSTPROC dest keyfield
AVZ2505T source SENDITEM dest keyfield rcode urID
Streams trace record. The Streams task is doing Streams trace record. The Streams capture process
postprocessing for an update. (capture) has captured an event. Data associated with
the event has been saved in a dataspace owned by the
User response Streams server.
operation represents the change type
None
AVZ2520T ENABLETRANSMISSIONS dest User response
machine
None
Explanation AVZ2541T srctsk capture EVENT BUILD
datatype operation mapname
Streams trace record. The Streams is enabling
transmissions to a dynamic destination for the JCA 1.5
interface. Explanation
Streams trace record. The Streams capture process
User response (capture) has built an event record in a dataspace
owned by the Streams server.
None
AVZ2521T DISABLETRANSMISSIONS dest
machine
User response
Explanation None
Streams trace record. The Streams is disabling AVZ2542T srctsk capture EVENT POST
transmissions to a dynamic destination for the JCA 1.5 datatype operation mapname
interface.
Explanation
User response
None (capture) has posted the source task in the Streams
server.
AVZ2530T ADDCOLUMN colname colval
Explanation
User response
Streams trace record. The Streams JCA 1.5 Adapter
interface is adding a column of Publish data. None
AVZ2543T srctsk capture EVENT BACKOUT
User response datatype operation mapname
None
Explanation
AVZ2531T ADDTOPIC topic
(capture) has backed out the data saved for an event.
Explanation
The event is discarded.
Streams trace record. The Streams JCA 1.5 Adapter
interface is adding a topic for MQ Broker processing.

None
None
AVZ2544W source CATALOG SEARCH ERROR,
AVZ2540T srctsk capture EVENT CAPTURE
RC=rcode REASON=rsncode
datatype operation mapname
ID=modID TYPE=type,
ENTRY=entry

Explanation changes) failed. The product continues to operate
without notifications.
Streams is searching the catalog for Archive data
sets using the CSI Catalog Search Interface, and
encountered an error. The entry is skipped. User response
source represents the source task name Examine any other messages accompanying this one.
If the security server you are using does not support
ENF signal 71, check with the security server product
User response vendor for more information. Otherwise, contact
Examine the VSAM catalog for errors using the Software Support for assistance with this problem.
diagnostic information provided. AVZ2608W SOM RACF new password exit is
AVZ2545E Invalid Streams service request not installed
received
Explanation
Explanation Security Optimization Management (SOM) initialization
Streams main task received an invalid service request. was unable to verify that the product's RACF new
password exit, S_ICHPWX, is installed as part of the
ICHPWX01 load module.
User response
Contact Software Support. User response
AVZ2600T ABEND ccode RS=rsncode The product continues to run. This exit detects
OCCURRED AT modname+offset. password changes that are made during logon to
FUNCTION CODE=funcode. applications other than the product. Users will still
be able to use the old password in the product until
Explanation the SOM cache entry expires. Password changes made
during the product logon are recognized without this
An ABEND occurred while processing a Security exit, and SOM signals all other product servers that
Optimization Manager request. this user's password has changed.
AVZ2620I Security optimizer entry for user
User response ID userID was expired.
The routine signals an error to the caller and
processing continues, when possible. Explanation
AVZ2606E Security optimization processing The request to expire the entry for a user ID in the
is terminated security optimization cache was successful.

Security Optimization processing was terminated due None. This message is for informational purposes only.
to an internal processing error. The product continues
to operate without the Security Optimizer. AVZ2621I Security optimization is not active

If you want to execute with the Security Optimizer, you A request to expire a Security Optimization entry could
must stop and restart the product. not be processed because Security Optimization is not
active.
AVZ2607I Security server ENF signal 71 not
available
User response
A request by Security Optimization to listen for AVZ2622I User ID userID was not located by
event notification facility signal 71 (RACF user profile the security optimizer.
A request to expire a security optimizer entry could not This message is issued when the product is activating
be processed because the user ID was not located. the support for connections to z/OS Connect.

No action is required. None. This message is for informational purposes only.
AVZ2623I Security optimizer processing AVZ2702I z/OS Connect support terminating
abended
Explanation
Explanation
This message is issued when the product is
The Security Optimizer Manager ABENDed while terminating the support for connections to z/OS
processing the expire request. Connect.

Check if any other error messages were generated None. This message is for informational purposes only.
along with the error message above. If the
AVZ2710W Zcpath Definitions found
combined error messages are sufficient to explain
the problem, take whatever corrective action is
appropriate. Otherwise, contact Software Support with Explanation
this problem.
The Zconnect facility has been disabled during product
AVZ2700E Error bb-ccc ddd Processing initialization. However at least one Zcpath definition
request. Extra Information: eee was found.

An error has occurred with the z/OS Connect interface. The Zconnect facility is still disabled. The definition(s)
The following information is provided: is(are) ignored.
• bb is a major error number, as follows: AVZ2711T Cannot start Zconnect Server %1
– 01: Storage error
– 02: Input data error Explanation
– 03: Input vectors error An error occurred during initialization of a Zconnect
facility server. Information about the specific error is
– 04: Input JSON parsing error
shown in the message.
– 05: Input JSON understanding error
– 06: Processing error User response
– 09: Miscellaneous error
depending on the definition, initialization may be
• ccc is a minor error number retried after a short interval, or the definition will be
• ddd is an error description disabled. CODE 1 = Zconnect Server definition name
2 = information 3 = optional extra information 4 =
• Extra Information: eee provides extra
optional extra information
information, if available.
AVZ2712T + Zconnect Server %1 restarting
User response after severe WOLA error
For details about the error message including possible

Explanation
corrective action, see Chapter 2, “z/OS Connect
interface codes,” on page 273. The named Zconnect Server is restarting, after it
received a severe WOLA API error. Refer to message
AVZ2701I z/OS Connect support activated
number 2713 for information about the WOLA API
error.

The Server will restart automatically after a short This message follows the 2720 message and provides
interval. CODE 1 = Zconnect Server definition name additional information about the request and field in
error.
AVZ2713T Zconnect Server %1 WOLA RCV
ANY Error %2/%3 %4
User response
Explanation See message 2720. CODE 1 = description of the
extra data. 'Zcpath:' - The ZCPATH name 'Sql stmt:'
The named Zconnect Server received a WOLA API - The SQL statement text (possibly truncated) 'Record
error when it issued a "receive any" request. The Number:' - The relative number of the result record.
return code and reason code are shown. Whether the 'Fld number/name:' - The relative number of the field
error is regarded as severe is also indicated. in error and the name of it. 'Data length:' - The length
of the nvalid data. 'Data (hex):' - The invalid data.
User response (possibly truncated) 2 = extra data 3 = extra data
If the error is severe, the server will automatically AVZ2722W END
restart after a short interval. CODE 1 = Zconnect
Server definition name 2 = return code from the WOLA
Explanation
'Receive Any' request 3 = reason code from the WOLA
'Receive Any' request 4 = optional indication of a This message follows the 2721 messages and
severe error indicates that all additional information has been
provided.
AVZ2714W Zcpath Definitions found - Not
Licensed
User response
Explanation See message 2720.
The Zconnect facility is not licensed on this system, AVZ2770T + Zconnect facility task start.
and at least one Zcpath definition was found during name: %1 tcb: %2 use: %3 + %4
initialization. These definitions will be ignored. %5 %6

The Zconnect facility is still not licensed. The Zcpath This message is issued when a Zconnect facility task
definition(s) is(are) ignored. starts. It is a trace message only.
AVZ2720W Invalid Data found whilst
processing request User response
None. CODE 1 = task name 2 = TCB address 3 = usage
Explanation information 4 = more usage information 5 = more
usage information 6 = more usage information
The Zconnect facility has encountered invalid data
whilst processing a request. This message will be AVZ2771T + Zconnect facility task end.
followed by several additional messages that provide name: %1 tcb: %2 use: %3 + %4
extra information that can be used to identify the %5 %6
invalid data.
Explanation
User response
This message is issued when a Zconnect facility task
The Zconnect facility will either return a value of 0 for ends. It is a trace message only.
the field in error to the user or an error indication.
AVZ2721W information. %1 %2 %3 User response
None. CODE 1 = task name 2 = TCB address 3 = usage
information 4 = more usage information 5 = more
usage information 6 = more usage information
AVZ2772T Zconnect Server %1 registered User response
with WOLA
None. CODE 1 = OPC3 address 2 = information 3
= information 4 = information 5 = information 6
Explanation = information 7 = information 8 = information 9 =
This message is issued when a Zconnect facility server information 10 = information 11 = information 12 =
connects to WOLA. It is a trace message only. information 13 = information
AVZ2777T Zconnect Server %1 WOLA Req:
User response %2 Rc: %3 Rs: %4
None. CODE 1 = Zconnect Server definition name

Explanation
AVZ2773T w n1: %1
This message is issued by the z/OS Connect interface
when a WOLA request gives an unexpected return
Explanation and/or reason code. It is a trace message only.
This message is issued when a Zconnect facility server
connects to WOLA. It is a trace message only. User response
None. CODE 1 = ZConnect server name 2 = WOLA
User response request name 3 = Return code 4 = Reason Code
None. CODE 1 = WOLA name 1 2 = WOLA name 2 3 = AVZ2778T Zconnect Server %1 Info: %2 %3
WOLA name 3 4 = register name %4 %5 %6 %7 %8 %9 %10 + %11
AVZ2774T Zconnect Server %1 unregistered %12 %13
from WOLA
Explanation
Explanation This message is issued while processing a request by
This message is issued when a Zconnect facility server the z/OS Connect interface. It is a trace message only.
disconnects from WOLA. It is a trace message only.
User response
User response None. CODE 1 = ZConnect server name 2 = information
None. CODE 1 = Zconnect Server definition name 3 = information 4 = information 5 = information 6
= information 7 = information 8 = information 9 =
AVZ2775T Zconnect Server %1 connid: %2 information 10 = information 11 = information 12 =
OPC3: %3 idl: %4 information 13 = information
AVZ2781T OPC3: %1 user data. type: %2 len:
Explanation %3 (%4) cs: %5
This message is issued when a new request is received
by a Zconnect server. It is a debugging message only. Explanation
This message is issued while processing a request by
User response the z/OS Connect interface. It is a trace message only.
None. CODE 1 = Zconnect Server definition name 2 =
Connection ID (12 hex characters) 3 = OPC3 Address 4 User response
= i/p data length
None. CODE 1 = OPC3 address. 2 = type (INPUT,
AVZ2776T OPC3: %1 Info: %2 %3 %4 %5 %6 RETURN, or EXCEPTION). 3 = length of data (decimal)
%7 %8 %9 %10 %11 %12 %1+ 3 4 = length of data (hex) 5 = character set (EBCDIC,
ASCII, or UTF-8).
Explanation AVZ2782T +%1 %2 %3
the z/OS Connect interface. It is a trace message only. Explanation
the z/OS Connect interface. It is a trace message only.

User response AVZ2899E DUMMY MESSAGE
None. CODE 1 = Offset of the displayed data. 2
= hex representation of the data. 3 = character Explanation
representation of the data. this is a dummy message for CQDHLI to mark the end
AVZ2783T (truncated) of the message range.

This message is issued while processing a request by None.
the z/OS Connect interface. It is a trace message only. AVZ2901E INVALID SOFTWARE
and indicates that the display of the dumped user data ENVIRONMENT
has been truncated.
Explanation
User response
The CQDHLITF program was being run in a software
None. environment that is not valid. This program requires at
AVZ2784T END least z/OS 1.13.

This message is issued while processing a request by Ensure that the environment for the program is
the z/OS Connect interface. It is a trace message only. suitable.
and indicates that the display of the dumped user data AVZ2902E INVALID HARDWARE
has finished. ENVIRONMENT

None. The CQDHLITF program was being run in a hardware
AVZ2798I %1 %2 %3 %4 %5 %6 %7 %8 %9 environment that is not valid. This program requires
%10 %11 at the hardware has at least the general instruction
extensions and parsing enhancements. A Z10 or later
machine has all the required facilities.
Explanation
a debug message for the z/OS Connect I/F facility. User response
Ensure that the environment for the program is
User response suitable.
None. CODE 1 = information 2 = information 3 = AVZ2910E PARM NAME BAD LENGTH - POS
information 4 = information 5 = information 6 = %1
information 7 = information 8 = information 9 =
information 10 = information 11 = information
Explanation
AVZ2799T %1 %2 %3 %4 %5 %6 %7 %8 %9
%10 %11 a parameter provided to the CQDHLITF program via
the JCL PARM (or equivalent) had a bad length. The
position in the PARM string where the parameter starts
Explanation is shown.
a debug message for the z/OS Connect I/F facility.
User response
User response Correct the PARM name. CODE 1 = position in PARM
None. CODE 1 = information 2 = information 3 = string.
information 4 = information 5 = information 6 = AVZ2911E PARM NAME NOT FOLLOWED BY
information 7 = information 8 = information 9 = "=" - POS %1
information 10 = information 11 = information
Explanation AVZ2920E UNABLE TO OPEN %1 FILE
(DDNAME: %2)
a parameter provided to the CQDHLITF program via
the JCL PARM (or equivalent) was not followed by an
"=" sign. The position in the PARM string where the Explanation
parameter starts is shown. The CQDHLITF program was unable to open a file. the
file name and dd name are shown. The file may not be
User response in the JCL or it may have invalid attributes.
Correct the PARM value. CODE 1 = position in PARM
string. User response
AVZ2912E PARM NAME NOT RECOGNIZED - Correct and/or supply the relevant file definition. Refer
POS %1 to the documentation for file definition information.
CODE 1 = file name. 'PRINT', 'INPUT', or 'TRACE' 2 =
dd name. The standard values are 'SYSPRINT', 'SYSIN',
Explanation or 'SYSTRACE'.
a parameter provided to the CQDHLITF program via AVZ2925E INPUT FILE LINE HAS INVALID
the JCL PARM (or equivalent) was not recognized, The SYNTAX. LINE %1
is shown.
Explanation
User response The input control file for CQDHLITF had a syntax error.
The line number of the line in error is shown.
Correct the PARM name. Refer to the documentation
for valid parameter names. CODE 1 = position in PARM
string. User response
AVZ2913E PARM VALUE INVALID LENGTH - Correct the syntax of the control file line. Refer to the
POS %1 documentation for control file syntax. CODE 1 = line
number. The line number (starting at 1)
Explanation AVZ2926E INPUT FILE LINE HAS UNKNOWN
OPTION OR INVALID VALUE. +
a parameter provided to the CQDHLITF program via LINE %1
the JCL PARM (or equivalent) had a bad length. The
is shown. Explanation
The input control file for CQDHLITF had an unknown
User response option name or an invalid value for a known option
name. The line number of the line in error is shown.
Correct the PARM value. CODE 1 = position in PARM
string.
User response
AVZ2914E PARM VALUE INVALID VALUE -
POS %1 Correct the syntax of the control file line. Refer to the
documentation for control file syntax. CODE 1 = line
number. The line number (starting at 1)
Explanation
AVZ2930E INVALID TRACE FILE RECORD
a parameter provided to the CQDHLITF program via CODE. RECORD NUMBER: %1
the JCL PARM (or equivalent) had an invalid value. The COD+ E (HEX): %2
is shown.
Explanation
User response The trace file input to CQDHLITF had an invalid record
code (Byte 1 of a record on the file). The record
Correct the PARM value. Refer to the documentation number of the record in error is shown. The record
for parameter value types. CODE 1 = position in PARM code is shown.
string.

User response AVZ2999E DUMMY MESSAGE
Check that the correct trace file has been specified. If
the error persists, contact support. CODE 1 = record Explanation
number. The record number on the trace file. 2 = this is a dummy message for CQDHLITF to mark the
hexadecimal record code value. end of the message range.
AVZ2931E INVALID TRACE FILE
EYECATCHER. RECORD NUMBER: User response
%1
None.
Explanation AVZ3000T recovery LEVEL lvl errdesc=abcode

REASON CODE=rsncode
The trace file input to CQDHLITF had an invalid eye TIME=time SEQ=seqno CPU=cpuID
catcher value. The record number of the record in error ASID=asid
is shown.
Explanation
User response
The product detected an abend error. The current
Check that the correct trace file has been specified. If message provides some information about the abend.
the error persists, contact support. CODE 1 = record This message, along with other messages, should
number. The record number on the trace file. provide a detailed description of the current abend
AVZ2940E NO STORAGE AVAILABLE error.
recovery may indicate "ESTAE", "FRR", or "ARR"
Explanation rsn may also be the text "UNKNOWN"
The CQDHLITF program was unable to obtain working
storage. User response
Check if any other error messages were generated
User response along with the error message above. If the combined
Increase the region size. error messages are sufficient to explain the problem,
AVZ2950E NO SESSIONS FOUND ON TRACE Otherwise, contact Software Support for assistance
FILE with this problem.
AVZ3001S func errdesc, ABEND abcode AT
Explanation modname+offset
The CQDHLITF program found no sessions on the trace
file. Explanation
The product ESTAE routine detected an abend in a
User response routine called by it. The message describes the abend
Check that the correct trace file has been specified. error. The product ESTAE routine will continue to
attempt recovery from the original error.
AVZ2960E NO SESSION START RECORD
FOUND FOR AT LEAST 1 SESS+
ION User response
Explanation along with the error message above. If the
The CQDHLITF program could not locate the 'session the problem, take whatever corrective action is
start' internal trace record for at least 1 session on the appropriate. Otherwise, contact Software Support with
trace file. this problem.
AVZ3002T Data at PSW PSWdata
User response
Check that the correct trace file has been specified.
Explanation is part of the mini-dump used to describe the current
abend error.
The product detected an abend error. The current
message provides some information about the abend.
This message, along with other messages, should User response
provide a detailed description of the current abend Check if any other error messages (other than the
error. mini-dump) were generated along with the error
PSWdata contains the PSW address and PSW data message above. If the combined error messages
are sufficient to explain the problem, take whatever
corrective action is appropriate. Otherwise, contact
User response Software Support for assistance with this problem.
Check if any other error messages were generated AVZ3008T ind register
take whatever corrective action is appropriate. If Explanation
the problem cannot be resolved, contact Software The product ESTAE routine detected an abend error.
Support. There is no product specific recovery for this error.
AVZ3005S ESTAE level lvl ESTAE func error The ESTAE routine tries to document the abend error
RC=rcode by displaying the failing PSW and register content
(register). This message is part of the mini-dump used
to describe the current abend error.
Explanation
ind indicates "AR/GR" or ""GR
The product ESTAE routine tried to protect itself by
issuing an ESTAE macro. The ESTAE failed with a non-
zero return code. User response
AVZ3006T PSW at time of error fPSW ILC ilc Check if any other error messages (other than the
INTC intc mini-dump) were generated along with the error
message above. If the combined error messages
Explanation corrective action is appropriate. If the problem cannot
The product ESTAE routine detected an abend error. be resolved, contact Software Support.
There is no product specific recovery for this error. The AVZ3009T modname calltype
ESTAE routine tries to document the abend error by modname+offset
displaying the failing PSW. This message is part of the
mini-dump used to describe the current abend error.
Explanation
ilc represents an instruction length code
The product ESTAE routine detected an abend error.
intc represents an interrupt code There is no product specific recovery for this error. The
ESTAE routine tries to document the abend error by
User response displaying the calling module sequence of the current
routine. This message is part of the mini-dump used to
Check if any other error messages (other than the describe the current abend error.
mini-dump) were generated along with the error
message above. If the combined error messages
are sufficient to explain the problem, take whatever User response
corrective action is appropriate. Otherwise, contact Check if any other error messages (other than the
Software Support with this problem. mini-dump) were generated along with the error
AVZ3007T Current routine name=modname message above. If the combined error messages
address=addr offset=offset are sufficient to explain the problem, take whatever
corrective action is appropriate. Otherwise, contact
Software Support for assistance with this problem.
Explanation
AVZ3010T Too many entries
The product ESTAE routine detected an abend error.
There is no product specific recovery for this error. The
ESTAE routine tries to document the abend error by
displaying the failing PSW and registers. This message

The product ESTAE routine detected an abend error. The tokenization routine detected a logic error during
While producing the module call trace (message processing of the current request.
3009T), the loop limit was reached. The product
ceases to issue calling module trace messages and User response
proceeds to other processing.
User response
Check if any other error messages (other than the take whatever corrective action is appropriate.
mini-dump) were generated along with the error Otherwise, contact your local product systems
message above. If the combined error messages programming group for help with this problem.
corrective action is appropriate. If the problem cannot AVZ3030E servrout errdesc FAILED, RC=rcode,
be resolved, contact Software Support. DETECTED AT addr
AVZ3020S INVALID STRING ADDRESS addr1, Explanation

DETECTED addr2
Some type of error occurred in one of the product
common subroutines. See the actual text of the
Explanation
message for an explanation. The error was probably
A request to the tokenization routine passed an invalid caused by a failure in an operating system service
string address. The address in the parameter list was requested by the subroutine.
less than or equal to zero.
User response
User response
Check if any other error messages were generated along with the error message above. If the
along with the error message above. If the combined combined error messages are sufficient to explain
error messages are sufficient to explain the problem, the problem, take whatever corrective action is
take whatever corrective action is appropriate. appropriate. Otherwise, contact Software Support with
Otherwise, contact your local Software Support group this problem.
for assistance with this problem.
AVZ3031E ABEND abcode IN servrout,
AVZ3021S INVALID STRING LENGTH REASON CODE=rsncode, CALLED
maxlgth, DETECTED addr BY cs
A request to the tokenization routine passed a string An abend was detected in one of the product common
length that exceeds the maximum string length subroutines. The abend code and service routine are
allowed. described in the message text. The error was probably
caused by a failure in an operating system service
User response requested by the subroutine.

User response
error messages are sufficient to explain the problem, Check if any other error messages were generated
take whatever corrective action is appropriate. along with the error message above. If the
Otherwise, contact your local product systems combined error messages are sufficient to explain
programming group for help with this problem. the problem, take whatever corrective action is
appropriate. Otherwise, contact Software Support with
AVZ3022S TOKENIZATION LOGIC ERROR,
this problem.
DETECTED addr
AVZ3032T INVALID INPUT COMMUNICATION
BUFFER PREFIX READ - blksize
An invalid buffer prefix was read in from a client None. This message is for informational purposes only.
application. The buffer prefix was either negative or
AVZ3037T DATASPACE func FAILED,
exceeded the maximum input buffer size.
NAME=dspname, RETURN
CODE=rcode, REASON CODE =
User response rsncode,CALLED BY cs
The connection to the client system is terminated. The
client application will probably report an error. Check Explanation
for any client system error messages. If the failure
continues, contact Software Support. A dataspace function failed. The return code and
reason code are displayed. The space token is
AVZ3033T DATASPACE CREATED, displayed.
NAME=dspname, CALLED BY cs
User response
Explanation
Installation limits may have caused the failure.
An MVS dataspace was created for temporary storage Examine the limits set by the installation's IEFUSI exit
of data. The space name (dspname) is displayed. to determine if they caused the failure. If the problem
User response AVZ3038T ALET CREATED, NAME=dspname,
None. This message is for informational purposes only. ALET=alet, CALLED BY cs
AVZ3034T DATASPACE DELETED,

Explanation
An ALET was created for accessing a dataspace.
Explanation The space token is displayed. The resulting ALET is
displayed.
An MVS dataspace was deleted. The space token is
displayed.
User response
None. This message is for informational purposes only. AVZ3039T ALET DELETED, NAME=dspname,
ALET=alet, CALLED BY cs
AVZ3035T DATASPACE EXTENDED,
Explanation
Explanation An ALET for accessing a dataspace was deleted.
The space token is displayed. The deleted ALET is
An MVS dataspace was extended. The storage in the displayed.
dataspace was used up and more was allocated to it.
The space token is displayed.
User response
None. This message is for informational purposes only. AVZ3040T ALESERV func FAILED,
NAME=dspname, RETURN
AVZ3036T DATASPACE RELEASED, CODE=rcode, REASON CODE =
NAME=dspname, CALLED BY cs rsncode,CALLED BY cs
Storage in an MVS dataspace was released. The An ALESERV function failed. The return code and
storage is no longer required. The space token is reason code are displayed. The space token is
displayed. displayed.

User response more error messages referring to the current problem.
Installation limits may have caused the failure. messages, and restart the product. If the problem
Examine the limits set by the installation's IEFUSI exit cannot be resolved, contact Software Support.
to determine if they caused the failure. If the problem
cannot be resolved, contact Software Support. AVZ3044S MODULE modname DELETE
FAILED, RETURN CODE=rcode
AVZ3041T ABEND abcode IN servrout,
REASON CODE=rsncode,
NAME=dspname, ALET=alet, Explanation
CALLED BY cs A module could not be deleted. The delete failed with
a non-zero return code.
Explanation
An abend was detected while manipulating a User response
dataspace. The abend code and service routine are Check the error messages and the reason code
described in the message text. The error was probably associated with this problem. There may be one or
caused by a failure in an operating system service more error messages referring to the current problem.
requested by the subroutine. The space token is If possible, fix the problem identified by the error
displayed. The ALET, if any, is displayed. messages, and restart the product. If the problem
User response AVZ3060S INVALID PC FUNCTION CODE
Check if any other error messages were generated funcode, DETECTED AT addr
error messages are sufficient to explain the problem, Explanation
the problem cannot be resolved, contact Software The product space switch PC routine has been invoked
Support. In certain recovery situations, this message with an invalid function code (funcode). This may be
may be ignored. caused by specifying an incorrect product subsystem
ID on a request when there are multiple copies of the
AVZ3042S Module modname is not product in the system at different release levels.
AMODE(31)
User response
Explanation
Verify that the request that resulted in the product
A module that had to load in AMODE(31) loaded with space switch PC routine being invoked is being issued
AMODE(24) or AMODE(64) instead. This is a serious to the correct product subsystem. If the problem
error. Many modules, including RPCs and user record cannot be resolved, contact Software Support.
exits, are only allowed to be AMODE(31).
AVZ3061E service ABEND abcode AT
modname+offset
User response
Relink the module (other changes may be needed) Explanation
using AMODE(31). Run the application again.
An abend failure occurred in the product space switch
AVZ3043S MODULE modname LOAD PC routine. The error message provides the abend
FAILED, ABEND=abcode, REASON code and abend location. This failure was probably
CODE=rsncode caused by a programming error in the calling routine or
in the space switch PC routine. This failure can also
Explanation be caused by product installation and maintenance
errors.
A module could not be loaded. The load failed with an
abend error.
User response
User response Check if any other error messages were generated
Check the error messages and the reason code error messages are sufficient to explain the problem,
associated with this problem. There may be one or take whatever corrective action is appropriate.
Otherwise, contact Software Support to obtain AVZ3071T func (funcode) SERVICE
additional assistance. errdesc ccode rsncode errloc
modname+offset creg15
AVZ3062E service desc FAILED RC=rcode,
DETECTED AT addr
Explanation
Explanation The product stacking PC function (func) has been
invoked in an invalid manner, has been invoked in an
invalid environmental state, or has abended during
execution. This is a duplicate of message 3070S but
description of the current operation (service) and what
is written to the trace.
creg15 represents control register 15, if avail, or
User response zeroes

User response
more error messages referring to the current problem. Verify that the request that resulted in the stacking
If possible, fix the problem identified by the error space switch PC routine being invoked is being issued
messages, and retry the operation. If the problem to the correct product subsystem. If the problem
cannot be resolved, contact Software Support. cannot be resolved, contact Software Support.
AVZ3063E plist action FAILED, DETECTED AT AVZ3080E operation FAILED FOR userID
addr RC=rcode AT addr
The space switch PC routine is attempting to copy A logoff to the current server address space was
(action) a parameter list (plist) passed by its caller into attempted by a user other than the one currently
storage that can be accessed in space switch mode logged on. The current server address space is
and has found that the target storage area is not large terminated, and a new one will be started.
enough.
User response
User response
If problems are encountered with servers, the product
This is an internal product error condition. Contact cancels them and restarts them. This is normal
Software Support. Software Support. product operation. Check if the current ABEND was an
independent one or if it was caused by the product,
AVZ3070S func (funcode) SERVICE and resolve the problem accordingly.
errdesc ccode rsncode errloc
modname+offset creg15 AVZ3081T TSO SERVER IN ASID asid
traceinfo1 traceinfo2 traceinfo3
Explanation traceinfo4
The product stacking PC function (func) has been

Explanation
invoked in an invalid manner, has been invoked in
an invalid environmental state, or has abended during This is a trace message issued by the subsystem data
execution. set read/write routine.
creg15 represents control register 15, if avail, or
zeroes User response
User response
AVZ3082W OUTPUT LIMIT EXCEEDED (limit
Verify that the request that resulted in the stacking LINES) - CANCEL SELF WITH S722
space switch PC routine being invoked is being issued
to the correct product subsystem. If the problem
Explanation
A TSO command running in a product TSO server
address space has exceeded the output line

limit for server commands as specified in the AVZ3086H LOGON of userID to TSO server
TSOSRVMAXLINES parameter. failed - RC=rcode1 (rcode2)
Reason=rsncode
User response
Modify the command to reduce the number of lines
Explanation
output, or increase the TSOSRVMAXOUTPUTLINES A product TSO server address space was not able
value. The TSO server will cancel itself with an S722 to LOGON the indicated client userid. The current
completion code to abort processing of the current command is bypassed.
command.
AVZ3083S Command requested more input - represents the SAF interface return code, and rcode2
command aborted represents the RACF return code

The product Servers do not support commands that Determine why the client userid logon failed, and
request additional input in subcommand mode. resubmit the command.
AVZ3087H Requestor has revoked command
User response request - cancel self with S622
Modify the command processor so that subcommand
input is not required. Explanation
AVZ3084W service OF desc FAILED, RC=rcode A product TSO server address space was not able to
bind to the requesting task while attempting to return
Explanation the results of a TSO command. The server abandons
the request and terminates additional processing of
This is a generic error message used to describe a the request by cancelling itself with a 622 completion
wide variety of errors detected by the product TSOSRV code.
subsystem interface read/write interface routine. The
message text provides the current operation (service)
User response
and what the current operation was trying to do.
Determine why the requesting task abandoned the
User response request, and resubmit. The requesting task may have
timed out while waiting for a response to the request.
associated with this problem. There may be one or AVZ3100S Invalid text insertion address -
more error messages referring to the current problem. msgno addr modname+offset
messages, and restart the product. Explanation
AVZ3085H jobname A=asid1 (asid2) TSO The product message formatting routine detected an
server terminated by request error in a data address passed to it. Because of the
invalid data address, a product message cannot be
Explanation sent. This means that some other error may have
occurred, but the error message was not sent because
A product Server address space has received a request of the current error. The invalid address is actually an
to terminate. This may occur at shutdown or when one scon. The offset is the location of the calling routine
of the parameters governing the TSO servers (MIN or that passed the invalid data.
MAX values) has been modified.
The message contains two address space identifiers User response
(asid1 and asid2), which are in decimal and
hexadecimal respectively
User response take whatever corrective action is appropriate.
Otherwise, contact Software Support for assistance
with this problem.
AVZ3101S Message number msgno not found Explanation
- modname+offset
The product message formatting routine could not
process the length part of a substitution variable
Explanation ("%()") found in a message skeleton. Because the
The product message formatting routine could not substitution variable could not be processed, a
find a message number passed to it in the product product message cannot be sent. This means that
message table. Because the message number could some other error may have occurred, but the error
not be found, a product message cannot be sent. This message was not sent because of the current error.
means that some other error may have occurred, but The error is caused by a programming error in the
the error message was not sent because of the current message table. The offset is the location of the calling
error. The error is caused by either a calling routine routine that invoked the message formatting routine.
passing an invalid message number or an error in the
message table. The offset is the location of the calling User response
routine that passed the message number that could
not be found. Ensure that the product is properly installed. Check
the message table assembly time, date, and version
number. Check if any other error messages were
User response generated along with the error message above. If the
Ensure that the product is properly installed. Check combined error messages are sufficient to explain
the message table assembly time, date, and version the problem, take whatever corrective action is
number. Check if any other error messages were appropriate. Otherwise, contact Software Support for
generated along with the error message above. assistance with this problem.
If the combined error messages are sufficient to AVZ3104S Invalid text insertion data type -
explain the problem, take whatever corrective action msgno modname+offset
is appropriate. If the problem cannot be resolved,
Explanation
AVZ3102S Invalid message text variable -
msgno varname modname+offset The product message formatting routine detected an
invalid data type value passed to it by a calling routine.
Because of the invalid data type value, a product
Explanation message cannot be sent. This means that some other
The product message formatting routine could not error may have occurred, but the error message was
process a substitution variable found in a message not sent because of the current error. The error is
skeleton. Because the substitution variable could not caused by a programming error in the calling routine.
be processed, a product message cannot be sent. This The offset is the location of the calling routine that
means that some other error may have occurred, but passed the invalid data type value.
the error message was not sent because of the current
error. The error is caused by a programming error in User response
the message table. The offset is the location of the
calling routine that invoked the message formatting Ensure that the product is properly installed. Check
routine. the message table assembly time, date, and version
number. Check if any other error messages were
generated along with the error message above.
User response If the combined error messages are sufficient to
Ensure that the product is properly installed. Check explain the problem, take whatever corrective action
the message table assembly time, date, and version is appropriate. If the problem cannot be resolved,
number. Check if any other error messages were contact Software Support.
generated along with the error message above. AVZ3105S Output message buffer overflow -
If the combined error messages are sufficient to msgno modname+offset
explain the problem, take whatever corrective action
is appropriate. If the problem cannot be resolved,
contact Software Support. Explanation
AVZ3103S Invalid text insertion data length - The product message formatting routine found that
msgno modname+offset the current message will not fit in the output buffer.
Because of the buffer overflow condition, a product
message cannot be sent. This means that some other

error may have occurred, but the error message was table error. The offset is the location of the calling
not sent because of the current error. The error routine that invoked the message formatting routine.
is caused by either a programming error in the
calling routine or a message table error. The offset User response
is the location of the calling routine that invoked the
message formatting routine. Ensure that the product is properly installed. Check
the calling module assembly time, date, and version
number. Also check the message table assembly time,
User response
date, and version number. Check if any other error
Ensure that the product is properly installed. Check messages were generated with the error message
the calling module assembly time, date, and version above. If the combined error messages are sufficient
number. Also check the message table assembly time, to explain the problem, take whatever corrective
date, and version number. Check if any other error action is appropriate. If the problem cannot be
messages were generated with the error message resolved, contact Software Support.
above. If the combined error messages are sufficient
to explain the problem, take whatever corrective AVZ3108S INVALID REPLY AREA LENGTH -
action is appropriate. If the problem cannot be length modname+offset
Explanation
AVZ3106S Invalid packed decimal for text
insertion - val modname+offset The data value entered by a user was too long for the
reply area passed by the calling routine. This error was
detected by the message formatting routine. The error
Explanation
is caused by a programming error in the calling routine.
The product message formatting routine detected that The offset is the location of the calling routine that
an invalid decimal data value (val) had been passed to invoked the message formatting routine.
it by a calling routine. Because of the invalid decimal
data value, a product message cannot be sent. This User response
means that some other error may have occurred, but
the error message was not sent because of the current Ensure that the product is properly installed. Check
error. The error is caused by a programming error in the calling module assembly time, date, and version
the calling routine. The offset is the location of the number. Check if any other error messages were
calling routine that invoked the message formatting generated with the error message above. If the
routine. combined error messages are sufficient to explain
appropriate. If the problem cannot be resolved,
User response
Ensure that the product is properly installed. Check
the calling module assembly time, date, and version AVZ3109E INTERNAL ERROR DETECTED AT
number. Check if any other error messages were OPSNMG +offset, RC = rcode
generated with the error message above. If the
combined error messages are sufficient to explain Explanation
The message formatting routine detected a serious
appropriate. If the problem cannot be resolved,
internal error. For example, a system service may have
failed with a non-zero return code, or an abend may
AVZ3107S INVALID REPLY PARAMETER - have occurred. This means that some other error may
modname+offset have occurred, but the error message was not sent
because of the current error. The error is caused by
either a programming error in the calling routine or a
Explanation
message table error.
The product message formatting routine detected that
a reply area had been passed to it for a message that is User response
not marked as a WTOR in the message table. Because
of this logical inconsistency, a product message cannot Ensure that the product is properly installed. Check
be sent. This means that some other error may have the calling module assembly time, date, and version
occurred, but the error message was not sent because number. Also check the message table assembly time,
of the current error. The error is caused by either a date, and version number. Check if any other error
programming error in the calling routine or a message messages were generated with the error message
above. If the combined error messages are sufficient Explanation
to explain the problem, take whatever corrective
action is appropriate. If the problem cannot be During a WRITE/PUT operation, the product I/O
resolved, contact Software Support. routines have been passed a record with an invalid
record size. The record size is either 0 or greater than
AVZ3110I data1 data2 data3 data4 data5 the maximum logical record size (LRECL) allowed for
data6 data7 data8 data9 data10 the indicated data set.

This message lists List Enable/Close/Force results. Attempt to determine the reason for the failure. If you
are unable to determine the reason for the failure,
User response contact Software Support for assistance.
None. This message is for informational purposes only. AVZ3122S VSAM service FAILED,
RC=rcode, fldname
AVZ3111I errdesc for dsname not found for FIELD=fldval, DDNAME=ddname,
cmd command. DSNAME=dsname
An error was encountered in processing a VSAM file A product generalized input/output processing routine
command. tried to open a VSAM data set. The VSAM OPEN
(service) failed.
User response fldname and fldval represent the ACB/RPL field name
Correct the command and reenter it. and value respectively
AVZ3119T data1 data2 data3 data4 data5

data6 data7 data8 data9 %SK
User response
Review the error message text. Determine what
Explanation caused the OPEN to fail, based on the return code.
Review the current data set for any obvious errors.
This message lists Trace Open/Close functions Correct the above problems, and restart.
AVZ3123S UNSUPPORTED obj
User response TYPE, DDNAME=ddname,
None. This message is for informational purposes only. DSNAME=dsname
AVZ3120S method service FAILED

FOR DDNAME=ddname,
Explanation
DSNAME=dsname The product generalized I/O routine has been passed a
DSORG or RECFM (obj) that is not supported.
Explanation
An attempt to open (service) the specified data set
User response
failed. Validate that the data set specified has a supported
method may be QSAM, BSAM, or BPAM data set organization (DSORG) or record format
(RECFM). If you are unable to determine the reason
for the failure, contact Software Support.
User response
AVZ3124S SHOWCAT FAILED,
Try to determine why the attempt failed. If you are RC=rcode, DDNAME=ddname,
unable to determine the reason for the failure, contact DSNAME=dsname
Software Support.
AVZ3121S RECORD SIZE size INVALID, Explanation
LRECL=lrecl, BLKSIZE=blksize,
DDNAME=ddname, A product generalized input/output processing routine
DSNAME=dsname tried to list the required message data from a data

set, but the SHOWCAT operation failed with the above User response
return code.
Review the error message text. Validate the VSAM data
set, and analyze it for integrity. Review errors with the
User response definition of the current data set. Ensure that it was
Review the error message text. Determine what properly defined and that no other errors exist with it.
caused the SHOWCAT operation to fail, based on the AVZ3128E service desc FAILED RC=rcode,
return code. Correct the above problems, and restart. DETECTED AT addr
For further assistance, contact your local product
systems programming group.
Explanation
AVZ3125S INVALID VSAM OBJECT
(obj), DDNAME=ddname, This is a generic error message used to describe a
DSNAME=dsname wide variety of I/O related errors. The message text
gives a description of the current operation (service)
and what the current operation was trying to do.
Explanation
While processing a VSAM data set , a product User response
generalized input/output processing routine found the
object (obj) to be invalid. Check the error messages and the return code
User response If possible, fix the problem identified by the error
Review the error message text. Validate the VSAM messages, and restart the product. If the problem
object and analyze it for integrity. Review errors in the cannot be resolved, contact Software Support.
definition of the current data set. Ensure that the data AVZ3129E service desc
set was properly defined and that no other errors exist
with it.
Explanation
AVZ3126E DYNAMIC ALLOCATION
FAILED, RC=rcode, ERROR This is a generic error message used to describe a
CODE=errcode, INFO wide variety of I/O related errors. The message text
CODE=rsncode, DDNAME=ddname, gives a description of the current operation (service)
DSNAME=dsname and what the current operation was trying to do.

An attempt to dynamically allocate a data set Check the error messages and the return code
failed. The error message contains the information associated with this problem. There may be one or
associated with the failed request. more error messages referring to the current problem.
User response cannot be resolved, contact Software Support.
Review the information contained in the message, and AVZ3130E DYNAMIC ALLOCATION COMMAND
attempt to correct the problem. Information on the ERROR. errmsg cmd
codes may be obtained from the documentation. If,
after reviewing this information, you are still unable to
correct the problem, contact Software Support. Explanation
AVZ3127S VSAM service FAILED, The format of a dynamic allocation/de-allocation
RC=rcode, DDNAME=ddname, command (cmd) is invalid. The message contains
DSNAME=dsname information associated with the parameter(s) in error.

A product generalized input/output processing routine Review the information contained in the message, and
could not display the check error message for the correct the command format.
current VSAM data set. The operation (service) failed.
AVZ3131E DESERV GET_ALL FAILED: Explanation
RC=rcode RSN=rsncode - ddname-
index:dsname While attempting to read a PDS(E) dataset directory,
the I/O services routines discovered that the PDS(E)
directory is empty.
Explanation
While issuing the DESERV macro to obtain directory User response
entry information, the system returned an unexpected
return code and reason code. An empty PDS(E) directory may be normal or may
represent a problem, depending on the library being
index represents the concatenation index where the accessed. If a problem results because the empty
error occurred directory is an abnormality, this informational message
may aid in resolution.
User response AVZ3135E DYNAMIC DEALLOCATION
Contact Software Support. FAILED, RC=rcode, ERROR
CODE=errcode, INFO
AVZ3132E HFS service FAILED FOR path - CODE=rsncode, DDNAME=ddname,
RC=rcode (name1), RSN=rsncode DSNAME=dsname
(name2) - desc1 / desc2
Explanation
Explanation
An attempt to dynamically free a data set failed. The
While invoking an Open Edition HFS Service for the error message contains the information associated
entity identified by path, the system returned an with the failed request.
unexpected return code and reason code.
name1 and desc1 refer to ERRNO names and User response
descriptions
Review the information contained in the message, and
name2 and desc2 refer to JERRNO names and attempt to correct the problem. Information on the
descriptions codes may be obtained from the documentation. If,
after reviewing this information, you are still unable to
User response correct the problem, contact Software Support.
Review the appropriate Open Edition manual for the AVZ3136T User record exits cannot be loaded
meaning of the return and reason codes. If the cause because DDNAME ddname is not
of the error cannot be readily determined, contact allocated. Exits: program1 and
Software Support. program2
AVZ3133E HFS service FAILED FOR path -

errdesc additinfo
Explanation
An attempt to load a user record post-read (program1)
Explanation and/or pre-write (program2) exit routine failed
because the AVZRPCLB DD statement is not allocated.
While invoking an Open Edition HFS Service for the User record exit routines must reside in the in the
entity identified by path, the server interface detected S__RPCLB library.
an error.
User response
User response
Modify the product server started task JCL to include
If the cause of the error cannot be readily determined the AVZRPCLB DD statement.
from this and other messages, contact Software
Support. AVZ3137S Load for user record exit program
program failed
AVZ3134I dsname Library directory empty
(DDN=ddname)
Explanation
An attempt to load a user record post-read and/or pre-
write exit program failed.

The user record post-read and pre-write programs Some type of error occurred in the system
must reside in a library allocated to the product management routines of the product. See the actual
AVZRPCLB DD statement. Check the joblog for related text of the message for an explanation. The error was
error messages. If the combined error messages probably caused by a failure in an operating system
are sufficient to explain the problem, take whatever service (sysserv) requested by a product system
corrective action is appropriate. If the problem cannot management routine.
be resolved, contact Software Support.
AVZ3138T User record exits cannot be used User response
because the SQL feature is not Check if any other error messages were generated
configured along with the error message above. If the combined
Explanation take whatever corrective action is appropriate.
Otherwise, contact Software Support for assistance
None. with this problem.
User response AVZ3142W Invalid data FOR func, Detected at

addr. Stack: %SK
AVZ3139T Non-zero return code from user Explanation
exit program. RC=rcode
Some type of error occurred in the system
management routines of the product. See the actual
Explanation text of the message for an explanation. This failure
was probably caused by a programming error in the
A user record exit program returned a non-zero return
calling routine or in the system management module.
code.
This failure can also be caused by product installation
and maintenance errors.
User response
The task is terminated. User response
AVZ3140W INVALID desc CODE func FOR Check if any other error messages were generated
service, DETECTED AT addr along with the error message above. If the
Explanation appropriate. Otherwise, contact Software Support with
A product routine called the system management this problem.
module with an invalid function code. This failure was
AVZ3143U DISPATCHER FAILURE DETECTED
probably caused by a programming error in the calling
AT addr
routine. This failure can also be caused by product
installation and maintenance errors.
Explanation
User response The internal product dispatcher detected a serious
error. This failure was probably caused by a
programming error in the system management
module. This failure can also be caused by product
installation and maintenance errors.
this problem. User response
AVZ3141E rsrc sysserv FAILED, RC=rcode, Check if any other error messages were generated
DETECTED AT addr along with the error message above. If the
this problem.
AVZ3144E rsrc sysserv FAILED, RC=rcode, User response
DETECTED AT routine+offset
Explanation error messages are sufficient to explain the problem,
Some type of error occurred in the system take whatever corrective action is appropriate. If
management routines of the product. See the actual the problem cannot be resolved, contact Software
text of the message for an explanation. The error was Support.
probably caused by a failure in an operating system AVZ3147T rsrc sysserv FAILED, RC=rcode,
service requested by a product system management DETECTED AT routine+offset
routine.
Explanation
User response
Some type of error occurred in the system
Check if any other error messages were generated management routines of the product. See the actual
along with the error message above. If the text of the message for an explanation. The error was
combined error messages are sufficient to explain probably caused by a failure in an operating system
the problem, take whatever corrective action is service (sysserv) requested by a product system
appropriate. Otherwise, contact Software Support with management routine.
this problem.
AVZ3145S cblk ERROR SUBSYS =subsys User response
Explanation along with the error message above. If the
The product detected a serious operating system combined error messages are sufficient to explain
control block (cblk) error. The operating system control the problem, take whatever corrective action is
block error prevented the system management routine appropriate. Otherwise, contact Software Support with
from performing some request on behalf of a caller. this problem.
This control block error may cause other system errors AVZ3148E Main product address space not
and may cause the operating system to fail. active

Check if any other error messages were generated Some routine tried to use a product facility that
along with the error message above. If the combined requires the main product address space to be active.
error messages are sufficient to explain the problem, The product facility could not be used because the
take whatever corrective action is appropriate. You main product address space is not active.
may need to IPL the system to resolve this problem.
If the problem cannot be resolved, contact Software
AVZ3146S EMERGENCY PRODUCT This may or may not be an error condition. Start or
SHUTDOWN STARTED - errdesc restart the main product address space, if necessary.
Explanation error messages are sufficient to explain the problem,
The product is shutting down because of a serious take whatever corrective action is appropriate. If
error. The message text describes the error. The error the problem cannot be resolved, contact Software
may be caused by an abend failure inside the product Support.
or by a product rate limit that has been exceeded. AVZ3149E ENFREQ reqtype CODE ecode
Also, the error may have been caused by a product FAILED, RC=rcode. STACK: %SK
programming error or by a system failure of some kind.
The product will turn itself off and disconnect itself
from the operating system. Explanation
A z/OS event notification facility request, ENFREQ,
failed. The meaning of the return code can be found
in the IBM Authorized Assembler Services manual.

If the security server you are using does not support A system management routine detected an error
ENF signal 71, check with the security server product while processing a request on behalf of a caller. The
vendor for more information. Otherwise, contact message text describes the failure. This failure may
Software Support. for assistance with this problem. have been caused by a programming error in the
calling routine or in the system management module.
AVZ3150E INVALID desc, VALUE data, This failure can also be caused by product installation
DETECTED AT addr and maintenance errors.

A system management routine detected invalid data. Check if any other error messages were generated
The error message describes the invalid data (data). along with the error message above. If the
This failure was probably caused by a programming combined error messages are sufficient to explain
error in the calling routine or in the system the problem, take whatever corrective action is
management module. This failure can also be caused appropriate. Otherwise, contact Software Support with
by product installation and maintenance errors. this problem.
User response AVZ3153E ABEND abcode IN func

modname+offset
Explanation
the problem, take whatever corrective action is A system management routine detected an abend
appropriate. Otherwise, contact Software Support with while performing a service on behalf of a caller.
this problem. The message text provides the abend code, current
operation, and abend location. This failure may have
AVZ3151H ABEND abcode IN func been caused by a programming error in the calling
modname+offset routine or in the system management module. This
failure can also be caused by product installation and
Explanation maintenance errors.
A system management routine detected an abend
while processing a message queue. The message User response
text provides the abend code, current operation,
and abend location. This failure may have been
caused by a programming error in the calling routine
or in the system management module. This failure
can also be caused by product installation and
maintenance errors. This failure will also occur Support.
when an address space containing a message queue
terminates unexpectedly. AVZ3156E rsrc MISSING AND REQUIRED FOR
sysserv, DETECTED AT addr
User response
Explanation
along with the error message above. If the combined A system management routine detected that a
error messages are sufficient to explain the problem, resource (rsrc) needed to perform a service on behalf
take whatever corrective action is appropriate. If of a user is not available. The service (sysserv) cannot
the problem cannot be resolved, contact Software be provided because of the error. The message text
Support. identifies the service requested by the user and the
missing resource.
AVZ3152W errdesc1 errdesc2 errdesc3,
DETECTED AT addr
User response
the problem, take whatever corrective action is Explanation
this problem. A GETMAIN or FREEMAIN request failed with a non-
zero return code. The error message gives the storage
AVZ3157E func ABEND abcode AT addr request type (GET or FREE), the return code, and the
location of the calling routine. This failure may have
Explanation been caused by a programming error in the calling
routine or in the storage management routine. This
An abend failure occurred when a system failure can also be caused by product installation and
management routine called an MVS service routine. maintenance errors.
The abend occurred in the MVS service routine.
The error message provides the abend code and subp represents the requested subpool
abend location. This failure was probably caused by a
programming error in the calling routine, in the system User response
management module, or possibly in the IBM service
routine. This failure can also be caused by product Check if some type of operating system problem
installation and maintenance errors. (such as storage shortage) may have caused the
problem. Check if any other error messages were
generated along with the error message above. If the
User response combined error messages are sufficient to explain
Check if any other error messages were generated the problem, take whatever corrective action is
along with the error message above. If the appropriate. Otherwise, contact Software Support with
combined error messages are sufficient to explain this problem.
the problem, take whatever corrective action is AVZ3204T modname+offset func stortype
appropriate. Otherwise, contact Software Support with spno stg1 stg2 token
this problem.
AVZ3200W INVALID SUBPOOL NUMBER=spno Explanation
REQUESTED BY modname+offset
This is a storage trace message generated by the
product storage management routine. Storage traces
Explanation are used to analyze product storage utilization and to
The storage management routine detected an invalid find storage management bugs. This is not an error
subpool number (spno) in a parameter list passed message. The message gives the calling module name,
by a caller. The subpool number is not supported calling module offset, current function (GET or FREE),
by the storage management routine. The storage storage type, subpool number (spno), storage area size
management module cannot perform the service (stg1), old storage total (stg2), and new storage total.
requested by the caller. The error message gives
the invalid subpool number and the location of the User response
calling routine. This failure may have been caused
by a programming error in the calling routine or in Check if storage trace was activated for some reason.
the storage management routine. This failure can also If storage trace is active, ignore this message.
be caused by product installation and maintenance Otherwise, storage trace has been inadvertently
errors. activated by a memory overlay. Contact Software
Support with this problem.
User response The variable fields of the message text are: mod
module name off module offset func current function
Check if any other error messages were generated stype storage type (E/CSA or E/Private) subp storage
along with the error message above. If the subpool number stg1 storage area size or amount stg2
combined error messages are sufficient to explain storage area size or amount token storage token if any
appropriate. Otherwise, contact Software Support with AVZ3205E STORAGE ROUTINE ABEND CODE
this problem. abcode AT modname+offset
AVZ3202W func ERROR RC=rcode REQUESTED

BY modname+offset, SP=subp,
Explanation
LEN=lgth, A=addr The storage management routine detected an abend
while performing a service on behalf of a caller. The
message text provides the abend code and abend

location. This failure may have been caused by a be caused by product installation and maintenance
programming error in the calling routine or in the errors.
storage management module. This failure can also
be caused by product installation and maintenance User response
errors.
User response
Check if some type of operating system problem the problem, take whatever corrective action is
(such as storage shortage) may have caused the appropriate. Otherwise, contact Software Support with
problem. Check if any other error messages were this problem.
generated along with the error message above. If the
combined error messages are sufficient to explain AVZ3208S stortype RETURNED FOR stortype
the problem, take whatever corrective action is REQUESTED BY modname+offset,
appropriate. Otherwise, contact Software Support for SP=subp, LEN=length
assistance with this problem.
Explanation
AVZ3206S SUBPOOL subp REQUIRES GLOBAL
MASTER AT modname+offset The storage management routine detected that a
request for extended storage (above the 16MB line)
was satisfied with non-extended storage (below the
Explanation
16MB line). This will only happen when the extended
The storage management routine detected a request storage area has been depleted and MVS is returning
for a subpool that can only be executed using the non-extended storage to satisfy storage requests. For
control blocks of the main product address space. example, the product is requesting ECSA storage but
However, the caller did not provide the main product MVS is returning CSA storage because ECSA has been
address space control blocks. The current storage completely allocated. This problem can also occur for
request will be rejected. This message indicates an private area storage as well.
internal error in the product. This failure may have
stortype may be E/CSA or E/Private
been caused by a programming error in the calling
routine or in the storage management module. This subp represents the subpool requested
failure can also be caused by product installation and
maintenance errors. User response
This is a very serious error and requires immediate
User response
action. If the message shows that CSA is being
Check if any other error messages were generated returned for ECSA requests, then ECSA has been
along with the error message above. If the depleted. One or more products may have to be
combined error messages are sufficient to explain terminated to release ECSA. At some point, the
the problem, take whatever corrective action is amount of ECSA allocated may have to be increased.
appropriate. Otherwise, contact Software Support with Note that the product can continue to execute in this
this problem. case. However, CSA is likely to be depleted, leading to
complete MVS system failure. If the message indicates
AVZ3207S CROSS MEMORY REQUIRES
that the problem is occurring for private area storage,
GLOBAL MASTER AT
contact Software Support with this problem.
modname+offset
AVZ3209S NO ASCB SPECIFIED FOR TCB-
Explanation LEVEL STORAGE REQUEST AT
modname+offset
The storage management routine detected a request
for a cross memory GETMAIN or FREEMAIN that
Explanation
can only be executed using the control blocks of
the main product address space. However, the caller The storage management routine detected that a cross
did not provide the main product address space memory GETMAIN or FREEMAIN with an explicitly
control blocks. The current storage request will be specified TCB association did not specify the address
rejected. This message indicates an internal error in space designation along with the request.
the product. This failure may have been caused by
a programming error in the calling routine or in the
storage management module. This failure can also
User response freeing all storage within the specified subpool (subp).
The requestor has either inadvertently specified the
Check if any other error messages were generated FREEMAIN storage address as zero, or a legitimate
along with the error message above. If the FREEPOOL request was coded incorrectly.
appropriate. Otherwise, contact Software Support with User response
this problem. The storage management routine generates an
AVZ3210S reqtype XFORM SP=subp S0C3 to abnormally end the calling procedure.
LEN=lgth A=addr FROM This is done to prevent errors which are likely to
modname+offset,failrsn occur subsequently after an entire subpool is freed
inadvertently. If the problem cannot be resolved,
Explanation
AVZ3250S service ERROR RC=rcode
The storage management routine determined that an
SRB-mode memory GETMAIN or FREEMAIN request
could not be internally converted to an appropriate Explanation
branch-entry request. Without transformation, the This message describes a variety of errors
request cannot execute in SRB-mode. encountered while using the QEDIT supervisor service.
subp represents the subpool of original request
User response
User response This problem may be caused by a failure either in
The request to get or free storage is rejected. Check the product or in the operating system. If possible,
if any other error messages were generated along fix the problem identified by the error messages, and
with the error message above. If the combined error restart the product. If the problem cannot be resolved,
messages are sufficient to explain the problem, take contact Software Support.
whatever corrective action is appropriate. Otherwise, AVZ3251I cmd msgtext
contact Software Support for assistance with this
problem.
Explanation
AVZ3211S STG OBTAINED AT addr NOT
2**reqal BOUNDARY ALIGNED This message is only issued when the product is in
REQUESTED BY modname+offset debugging mode. It echoes commands sent to the
product.
Explanation
User response
The storage management routine determined that
obtained storage was not aligned on the requested None. This message is for informational purposes only.
boundary (reqal). AVZ3252S component initialization timeout
detected
User response
The storage management routine generates an S0C3 Explanation
to abnormally end the calling procedure. This is This message is issued when the product attempted
done to prevent errors which are likely to occur to initialize full SEF (component) support, but SEF
subsequently if the incorrectly aligned storage is used. initialization did not complete in the allowed time
Contact Software Support with this problem. period. This is a serious error, and product initialization
AVZ3212S INVALID REQUEST TO FREE is terminated.
ALL SUBPOOL subp STORAGE
REQUESTED BY modname+offset User response
Explanation along with the error message above. If the combined
The storage management routine determined that a error messages are sufficient to explain the problem,
product storage FREEMAIN request has been made take whatever corrective action is appropriate. If
with a zero address. Such a request results in

the problem cannot be resolved, contact Software Explanation
Support.
The product tried to match an operator command to an
AVZ3253I prodname version prodver build existing command rule (cmd) and was unsuccessful.
buildno subsystem subsys
initialization complete
User response
Explanation Verify that the specified command is spelled correctly.
Also, verify that it exists and is enabled in the current
This is the standard message indicating that product command rule data set.
initialization is complete.
AVZ3260I Server subsystem subsys is an
ERLY subsystem
User response
No action required. Explanation
AVZ3254I component map build beginning d2 The product has been started as an ERLY subsystem
at t2 for ss for use by other (non-product) subsystems that
normally start before ordinary product subsystems. An
Explanation ERLY product subsystem can be started SUB=MSTR if
desired. It does not perform normal product work and
This message is issued when a SQL map build is uses very few system resources.
complete.
User response
Response
AVZ3273E SQL ENGINE MEMORY LIMIT
AVZ3255I component map build complete on EXCEEDED
d2 at t2 for ss
Explanation
Explanation
This message is displayed when any SQL statement or
This message is issued when a SQL map build is clause (for example - JOIN) requires a lot of memory
complete. to execute and the parameter SQLENGSTGLIMIT is not
set to a higher value to run the statement or clause
Response (JOIN clause).
None. This message is for informational purposes only. User response:

Set SQLENGSTGLIMIT to higher values.
AVZ3256S SQL map build failed due to
component AVZ3274E SQL ENGINE UNABLE TO OBTAIN
MEMORY
Explanation
Explanation
This message is issued when the SQL engine map
build process does not complete in the allowed time This message is displayed on running multiple
period (five minutes). This is a serious error, and major connection tests, load tests, or a large number of SQL
parts of the product may not function correctly. statements. In this case, the user loses the connection
and the SQL Engine fails to obtain the memory.
Response User response:

Ensure that the memory is freed and available.
along with the error message above. If the combined AVZ3300W INVALID desc CODE func FOR
error messages are sufficient to explain the problem, service, DETECTED AT addr
take whatever corrective action is appropriate. If the
problem cannot be resolved, contact IBM Software Explanation
Support.
A product routine called the SQL management module
AVZ3259E (cmd) invalid command with an invalid function code. This failure was probably
caused by a programming error in the calling routine. User response
This failure can also be caused by product installation
and maintenance errors. Examine the data set and any other messages that
may accompany this one. If you are able to resolve the
problem, restart the product.
User response
AVZ3304E Member dbrm not found in DBRM
Check if any other error messages were generated library
the problem, take whatever corrective action is Explanation
appropriate. Otherwise, contact Software Support with A BLDL for the DBRM member failed.
this problem.
AVZ3301E PLAN plan DBRM dbrm User response
TIMESTAMPS MISMATCH time1
time2 Determine why the DBRM is missing from the DBRM
library. If necessary, change the library specified in
the JCL for the main address space, and restart the
Explanation product.
The timestamp associated with the SQL statement AVZ3305E func failed for
plist does not match the timestamp in the DBRM. The MEMBER=dbrm DDNAME=ddname
exact SQL statement cannot be displayed. DSNAME=dsname RC=rcode
This message contains two timestamps; time1
represents the plist timestamp, and time2 represents Explanation
the DBRM timestamp
An I/O operation (func) failed while attempting to
access the DBRM library.
User response
Verify that the DBRM library specified in the JCL of User response
the main product library is synchronized with the
application program load library (i.e. both the load and Use this message in conjunction with any other
the DBRM were produced from the same version of messages that may accompany it to resolve the
the source). Correct any mismatch, and restart the problem. You may also want to examine the data set
product. for problems. Once the problem is corrected, restart
the product.
AVZ3302E ddname DDNAME not allocated -
SQL source not available AVZ3306E DBRM MEMBER dbrm TOO LARGE,
MAXIMUM SIZE IS count RECORDS
Explanation
Explanation
The DBRM DD statement is not present in the JCL used
to start the main product address space. The current DBRM is too large for AVZ to handle.

Add the DBRM DD statement to the JCL of the main Ensure that the DBRM actually does contain more than
product address space the maximum number of records. If it does, contact
Software Support.
AVZ3303E DBRM OPEN failed
for DDNAME=ddname AVZ3307E DBRM member dbrm is empty
DSNAME=dsname RC=rcode
Explanation
Explanation The DBRM member specified by the message does not
AVZ tried to open the DBRM library for input and contain any records.
the open operation failed. Actual SQL statement texts
must have the DBRM(s).

Verify that the data set does not contain any records. If The ability to use the assign and concatenate functions
it does not contain records, replace it with a corrected for sending lob data from the client to the server
DBRM member. If the member does contain records, is suspended. This message is issued when the
contact Software Support for assistance with this CLIENTMAXLOBSIZE parameter value is set to zero
problem. (0).
AVZ3308E DBRM MEMBER NAME dbrm DOES
NOT MATCH PROGRAM NAME User response
program None. This message is for informational purposes only.
AVZ3312T NETWORKBUFFERSIZE or MXBU
Explanation
value(s) are inadequate for the
The DBRM member name does not match the program number of columns in the SQL
name that is contained within the DBRM. statement.

It is possible that the DBRM member has been There is insufficient space in the communications
renamed. Verify that this is the problem, and correct buffer to hold the SQLDA (metadata) for the SQL
it. The DBRM member name and the program name statement. The NETWORKBUFFERSIZE and MXBU
contained within the DBRM must be identical. parameter values must be large enough to hold the
metadata for the SQL statement that references the
AVZ3309E SQL statement stno missing from most columns.
DBRM dbrm
User response
Explanation
Change NETWORKBUFFERSIZE and/or MXBU to an
The SQL statement identified by the application appropriate value.
program's plist could not be found in the
corresponding DBRM member. AVZ3313T DB2 subsystem with ASID subsys
was not found
User response
Explanation
The plist's statement number (stno) should match one
of statements in the DBRM. Verify that the application The ERLY control block for the Db2 subsystem was not
program load module and the DBRM are synchronized found.
(i.e. they were produced at same time from the same
version of the source). Correct any mismatches, and User response
restart the product.
The product was not able to find the ERLY control
AVZ3310E DBRM close FAILED block for the Db2 subsystem using the ASID. The
FOR DDNAME=ddname routine cannot proceed because of this error. This can
DSNAME=dsname RC=rcode occur when the Db2 subsystem ends with a system
04F ABEND.
Explanation
AVZ3314S DB2 subsystem with ASID subsys
AVZ tried to close the DBRM library and the close was not found
operation failed. Resources may not have been
completely released. Explanation
The ERLY control block for the Db2 subsystem was not
User response
found.
Examine the data set and any other messages that
may accompany this one. If you are able to resolve the User response
problem, restart the product.
The product was not able to find the ERLY control
AVZ3311T ASSIGN AND CONCATENATE LOB block for the Db2 subsystem using the ASID. The
REQUESTS ARE SUSPENDED
routine cannot proceed because of this error. This can User response
occur when the Db2 subsystem ends with a system
04F ABEND. Check the error messages and the return code
AVZ3315W Operational mode for DB2 more error messages referring to the current problem.
subsystem subsys could not be If possible, fix the problem identified by the error
determined messages, and restart the product.
AVZ3702H TSO/SRV started server
Explanation jobname,ASID=asid
The product is not aware of the version of Db2
executing in the Db2 subsystem and cannot determine Explanation
the operational mode.
The product has issued a START command to create a
new TSO/SRV server address space, and the address
User response space has been created.
Processing continues. Contact Software Support to
report this message. User response
AVZ3316T Operational mode for DB2 None. This message is for informational purposes only.
subsystem subsys could not be
determined AVZ3703W TSO/SRV SUBTASK UNABLE
TO SCHEDULE EXTERNAL
TSO SERVER - ABEND/POST
Explanation CODES=(abcode/pcode)
The product is not aware of the version of Db2
executing in the Db2 subsystem and cannot determine Explanation
the operational mode.
The product TSO/SRV execute queue processing
function detected an abend or error while attempting
User response to schedule a command into an external TSO server
Processing continues. Contact Software Support to address space. This message is returned to the original
report this message. requestor.
AVZ3700H TSO/SRV now using count servers -

MIN=parmval1 MAX=parmval2
User response
Gather all abend error data, and contact your local
Explanation product systems programming group for support.
The product has allocated a new server descriptor AVZ3704H TSO/SRV cancelled server
control block and will start a new TSO/SRV server jobname,ASID=asid
address space.
parmval1 represents the value of CGIMIN, and Explanation
parmval2 represents the value of CGIMAX The product has issued a CANCEL command to
eliminate a TSO/SRV server address space (asid). This
User response may occur either because of a change (reduction)
in the value of the TSOMINSERVERS parameter or
None. This message is for informational purposes only. because of a server command exceeding its execution
AVZ3701I service OF desc FAILED, RC=rcode limits.

This is a generic error message used to describe When a server command exceeds the server execution
a wide variety of errors detected by the product limits, this message is accompanied by a message
Server routine manager. The message text provides describing which limit is exceeded. Either modify the
the current operation (service) and what the current limit or correct the server command/program.
operation was trying to do. AVZ3705I Idle TSO server terminated due to
TSOMAXSERVERS

The product detected that there were currently more The transaction currently being processed by the
servers active than specified in the TSOMAXSERVERS server in question has exceeded the maximum amount
parameter and terminated the server in question of time allowed by TSOMAXCMDRUNTIME and has
because it was currently idle. caused the cancellation of the server.

None. This message is for informational purposes only. Please examine the SYSLOG for the _3710I companion
message, which will detail the command in error and
AVZ3706W Transaction aborted its approximate start time. Either correct the command
in error or increase the TSOMAXCMDRUNTIME value.
Explanation
AVZ3710I CMD TEXT = cmd ,START TIME =
This message is sent to the issuer of a TSO/SRV time
server command when the server has terminated
while executing the transaction.
Explanation
User response This is the companion message to _3709W. It details
the command which was being processed by the
Check for other messages associated with this canceled server and its approximate start time.
condition, and attempt to resolve the problem.
AVZ3707S TSO/SRV server failed during User response
initialization
Either correct the command in error or increase the
TSOMAXCMDRUNTIME specification.
Explanation
AVZ3711I Idle server terminated due
The product attempted to start a TSO/SRV server to TSOMINSERVERS or
address space. However, the address space failed TSOSRVDORMANT timeout
during initialization.
Explanation
User response
The product detected that the current number
Verify that the TSO/SRV server started task JCL is of servers is greater than the user specified
correct. JCL errors of one kind or another (e.g. data TSOMINSERVERS parameter but not greater than
set does not exist) are frequently the cause of this the user specified TSOMAXSERVERS value and that
condition. If you are unable to resolve the problem, the server has been idle longer than the user
contact Software Support. specified TSODORMANTTIMEOUT value. The product
terminated the server in question because it was
AVZ3708E Unable to find ASVT entry for
currently idle.
TSO/SRV server ASID=asid
User response
Explanation
After issuing an internal START command for a
TSO/SRV address space, the product attempted to AVZ3712W TSOMAXSERVERS value
validate the returned ASID and found it to be invalid. (parmval1) invalid. Set to
This error indicates one of the following conditions: (1) TSOMINSERVERS (parmval2).
the ASID is negative, (2) the ASID is greater than the
system MAXUSER value, or (3) the associated ASVT
Explanation
entry is currently not in use.
The product Server processing has detected that the
User response TSOMAXSERVERS value has been set to a value that is
lower than the TSOMINSERVERS value. This is invalid
This condition is extremely unlikely to occur. - the maximum number of servers can never be lower
than the minimum number of servers. The maximum
AVZ3709W TSO server canceled - max
value is changed to the minimum value.
transaction time exceeded
parmval1 represents the value of TSOMAXSERVERS, contains the abend code, current operation, and abend
and parmval2 represents the value of location.
TSOMINSERVERS
User response
User response
If the incorrect values are set via the startup along with the error message above. If the combined
exec or any other program, correct the program(s). error messages are sufficient to explain the problem,
You may also adjust the TSOMINSERVERS and take whatever corrective action is appropriate.
TSOMAXSERVERS values using the ISPF parameter
AVZ3716O Cancelled TSO server jobname
display.
stepname (ASID=asid), has not
AVZ3713I TSO/SRV server added due to terminated
excessive queue depth (qdep)
Explanation
Explanation
The product has issued a CANCEL command to
The number of requests on the TSO/SRV server terminate a TSO server. More than one (1) minute has
execute queue currently exceeds the threshold set elapsed since the CANCEL command was issued, but
by the user specified TSOSRVQUEUEADDDEPTH. The the server address space has not terminated.
number of servers is being increased by one since the
number of servers is still below the maximum number User response
of servers limit as specified by the TSOMAXSERVERS
value. First, attempt another CANCEL command using the
STEP NAME from the message. If this does not cause
the server to terminate, use the MVS FORCE command
User response
or attempt to kill the server address space using any
None. This message is for informational purposes only. other means at your disposal.
AVZ3714H TSO/SRV terminated server AVZ3717H TSO server execute queue reset
jobname,ASID=asid
Explanation
Explanation
A control command has caused the TSO/SRV execute
The product has terminated a TSO server address queue to be cleared. All pending TSO transactions
space. The server has been terminated because have been discarded.
either the current number of servers exceeds
the TSOMAXSERVERS limit, or the current number User response
of servers exceeds the TSOMINSERVERS value
and the current server has been idle more than None. This message is for informational purposes only.
TSOSRVDORMANTTIMEOUT seconds. This message
AVZ3718E TSO ADDRESS SPACE CREATION
may also occur when a control command requested
FAILED, RC = rcode, REASON CODE
server termination. The server address space may
= rsncode
not terminate immediately if it is currently running
a transaction. If the server does not terminate
voluntarily within a limited time period, the server will Explanation
be cancelled by the product.
A failure occurred in the service routine that schedules
an address space CREATE. The TSO address space will
User response not be created. The return and reason codes in the
message are from the MVS ASCRE service routine.
AVZ3715H TSO/SRV SUBTASK ABEND abcode User response
IN func modname+offset
Check the return code in the message. If the return
code is 52 or higher, this error is most likely a
Explanation
system related problem, and you should report this to
The product TSO/SRV execute queue processing your system programming staff. If necessary, set the
function detected an abend. The message text TSOSRVUSEASCRE to NO so that START commands

(rather than ASCRE) will be used to create TSO AVZ3723T TSO COMMAND COMPLETE;
outboard server address spaces. ASID=asid, ETIME=time1,
CPU=time2, I/O=count, CMD=cmd
AVZ3720T TSO EXECUTE QUEUE ADD;
QD=qdep, CMD=cmd
Explanation
Explanation This message indicates that a server has completed
execution of a command. This message is only issued
This message is actually issued by the ADDRESS TSO
when DEBUG is set ON.
| CGI processor when the DEBUG FLAG is set ON. This
message indicates that a command (cmd) is being sent The message has two time values; time1 represents
to the product Server queue. Note that queue depth time since command was sent to server in seconds,
(qdep) is displayed prior to the addition of the current and time2 represents command CPU time in hex
command. (microseconds)

None. This message is used for debugging and analysis None. This message is used for debugging and analysis
purposes only. purposes only.
AVZ3721T TSO COMMAND DISPATCH; =
QD=qdep, ASID=asid,
AVZ3724H name (userID) SENT TSO CMD cmd
QTIME=qtime, CMD=cmd
Explanation
Explanation
This message indicates that a server has received
This message indicates that a command has been
a command (cmd). The program or ruleset.rulename
removed from the TSO execute queue and has been
(name) indicates where the command originated.
sent to a product TSO server address space. This
message is only issued when DEBUG is set ON.
User response
qdep represents queue depth
qtime represents time spent on TSO execute queue in
100ths of a second AVZ3725T TSO execute processor posted by
component
User response
Explanation
None. This message is used for debugging and analysis
purposes only. This message indicates that the TSO execute
processor has received a signal from another
AVZ3722T TSO COMMAND RECEIVED;
component.
ASID=asid, ETIME=etime,
CMD=cmd
User response
Explanation None. This message is used for debugging and analysis
purposes only.
This message indicates that a server has received a
command. The delay between the time (etime) the AVZ3729T msgtext var2 var3
TSO command dispatch message is issued and the
time this message is issued is due to operating system
Explanation
scheduling factors. This message is only issued when
DEBUG is set ON. This message is for TSO debugging and trace purposes
only.
User response
User response
None. This message is used for debugging and analysis
purposes only. None. This message is for informational purposes only.
AVZ3750H SEF var1 var2
This message indicates that the product execute There was an error within the SEF rule processor.
processor has terminated.
User response
User response
This message is for informational purposes only unless message to understand the context.
it indicates that the SEF command queue has not
been allocated. In that case, you should check for any AVZ3754I SEF command syntax error: cmd
other messages that appeared on the console during
product initialization that may assist you in resolving Explanation
this problem. If you are unable to resolve the problem,
The SEF execution processor detected a command
contact Software Support for further assistance.
with invalid syntax for the ADDRESS SEF environment.
AVZ3751I SEF service OF desc FAILED, Normally, the syntax error should have been detected
RC=rcode at rule enabled or program compile time.

This is a generic error message used to describe Modify the rule or program that issued the command
a wide variety of global variable initialization and to use a valid ADDRESS SEF command.
AVZ3755E service OF PRECOMPILED DATA
current operation (service) and what the current
SET (dsname) FAILED RC=rcode

The SEF execution processor detected a request
to allocate/deallocate (service) a compiled rules
library, and the request failed. Check error messages
preceding this failure for more allocation error data.
cannot be resolved, contact Software Support. User response
AVZ3752W SEF API INITIALIZATION FAILED Check any allocation error messages that preceded
DUE TO initstep additinfo1 this message for more diagnostic information.
additinfo2 After fixing the problem, reset the parameters
SEFPRECOMPILED and SEFPRECOMPILEDDSN.
Explanation AVZ3756I SEF precompiled rules active
During SEF initialization, an error was detected
while creating API interface linkages. The message Explanation
describes the error encountered.
SEF has activated the Compiled Rules Facility. This
facility is activated by the setting of the parameter
User response SEFPRECOMPILED to ON and the parameter
SEFPRECOMPILEDDSN to a valid compiled rule library.
cannot be resolved, contact Software Support. AVZ3757I SEF var1 var2
AVZ3753W ABEND var1 AT var2+var3, SEF
COMMAND var4 ABORTED Explanation
This message indicates that a command has executed
and is returning status information. It indicates the
success or failure of the command.

This message is for informational purposes only. If Check the error messages associated with this
it indicates failure of the command, check that the problem. There may be one or more additional
parameters you have given are correct. error messages or abends referring to the current
processing problem. If possible, fix the problem
AVZ3780I func OF desc FAILED, RC=rcode
identified by the error messages, and restart the
product. If the problem cannot be resolved, contact
Explanation Software Support.
A failure occurred in the service routine that sets AVZ3783S file ddname processing ABENDED
(func) the wait timer interval (desc) for the next trace code=abcode reason=rsncode at
checkpoint. This message should be preceded by a modname+offset
message containing the return code from the MVS
STIMERM service.
Explanation
User response A problem was encountered while opening or
refreshing a product data set. The message indicates
Contact Software Support. the abend code associated with the processing
function.
AVZ3781S ABEND abcode OCCURRED AT
modname+offset - desc
User response
Explanation Check the error messages associated with this
problem. There may be one or more additional
An abend occurred during trace checkpoint
error messages or abends referring to the current
processing. The location of the abend is shown in the
abend error message. All trace checkpoint processing
identified by the error messages, and restart the
will be suspended until the main product address
product. If the problem cannot be resolved, contact
space is restarted. Note that the main product address
Software Support.
space will start to accumulate non-VIO ASM slots as if
no DIV data set had ever been allocated. The gradual AVZ3784T src DUPLICATES THE type ID IN
accumulation of ASM slots by the main product src - SKIPPED
address space could eventually cause an ASM slot
shortage.
Explanation
User response A problem was encountered while opening or
refreshing a product data set. The message
Check the error messages and the abend code indicates that a duplicate entity was detected. The
associated with this problem. There may be one or DUPLICATING entity will be ignored.
Variables in this message (src, type, and ID) refer to
to the current trace checkpoint processing problem.
the duplicating entity
Check for OPEN errors, such as security product
related abends. Also, check for storage allocation
errors or abends. If possible, fix the problem identified User response
problem. There may be one or more additional
Support.
error messages or abends referring to the current
AVZ3782S file ddname error FAILED RC=rcode processing problem. If possible, fix the problem
errdesc identified by the error messages, and refresh or
Explanation
AVZ3785H src DUPLICATES THE type ID IN
A problem was encountered while opening or
src - SKIPPED
refreshing a product data set. The message indicates
the cause of the failure.
A problem was encountered while opening or Check your initialization procedure, SWSxIN00, to be
refreshing a product data set. The message sure it defines ONE master WWW ruleset using the
indicates that a duplicate entity was detected. The "WWWCLASS(MASTER)" keyword.
DUPLICATING entity will be ignored.
AVZ3889I SEF version OPERATIONAL MODE
Variables in this message (src, type, and ID) refer to DOES NOT SUPPORT THE func
the duplicating entity FUNCTION

Check the error messages associated with this SEF rule manager received a command which it
problem. There may be one or more additional does not support when operating in the indicated
error messages or abends referring to the current operational mode.
identified by the error messages, and refresh or
User response
restart the product. Normally, this is done by manually
removing one or the other source file identified in the Correct the command, and re-issue.
message. If the problem cannot be resolved, contact
Software Support. AVZ3790I func OF desc FAILED, RC=rcode
AVZ3886E RULESET rsname additinfo1,

Explanation
additinfo2 … additinfo8
A failure occurred in the service routine that sets
Explanation (func) the wait timer interval (desc) for the next global
variable checkpoint. This message should be preceded
The SEF request is rejected because the ruleset status by a message containing the return code from the MVS
prevents execution of the request. STIMERM service.

Examine previously reported conditions to determine Contact Software Support for assistance.
the cause of the problem.
AVZ3791E func for creating global variable
AVZ3887I RULESET rsname additinfo1, backup, RC = rcode, Reason code
additinfo2 … additinfo8 = rsncode
An error occurred while processing an SEF request A failure occurred in the service routine (func)
and the status of a ruleset is effected. This message that schedules an address space create. The global
follows the original error message to warn of variable backup will not execute. The return and
additional/on-going ramifications from the error. reason codes in the message are from the MVS ASCRE
service routine.
User response
User response
The server takes the action reported in this message
in order to recover from the previously reported error Check the return code in the message. If the return
cause. code is 52 or higher, the error is most likely a system
related problem, and you should report this to your
AVZ3888E Required master WWW ruleset
system programming staff. If the problem cannot be
not defined - HTTP processing
resolved, contact Software Support for assistance.
impossible
AVZ3792I Global Variable Backup address
Explanation space procedure has been created
SEF Rule manager did not find a Master WWW ruleset

definition. The rule manager will not enable ANY WWW
rulesets.

This message is informational only. The message Correct the command, and re-issue.
indicates that the product created the global variable
AVZ3850E INTERNAL routine1 ERROR
backup address space.
DETECTED BY routine2:
CALLER(csect) RTADDR(addr) -
User response additinfo
Explanation
AVZ3800T An unknown value was found in
field field by routine. An error occurred while an internal API routine was
executing. This message reports some inconsistency
Explanation or a possible logic error.
A value was found in a control block field that cannot

User response
be validated by the SERVER API.
The API rejects the current request and continues.
User response Check for other messages which may indicate the
precipitating cause.
AVZ3851I NO EXECUTABLE OBJECT (XO)
AVZ3847W Error compiling SEF rule rule, DATASETS ARE CURRENTLY
closing */ not found where DEFINED OR IN-USE
expected.
Explanation
Explanation
This response is returned for 'LIST =XOFILES' SEF
SEF rule manager attempted to compile a REXX rule command if no executable object image (XO) datasets
with a /*%include statement that contained invalid are defined or in use. XO datasets may contain pre-
syntax. After the member name, only */ is allowed. compiled executable object images such as SEF rules
Imbedded comments inside the /*%include phrase are or HTX skeletons.
not supported.
User response
User response
None.
Correct the /*%include statement and try again.
AVZ3852I %1
AVZ3848W Error compiling SEF rule rule,
INCLUDE name memname too
Explanation
long.
Explanation command for each individual XO dataset allocated in
the system. A list of zero or more associations may
SEF rule manager attempted to compile a REXX rule follow this message.
with a /*%include statement that specified a member
name (memname) longer than 8 bytes.
User response
User response None. This is an informational message only.
Correct the /*%include statement and try again. AVZ3853I %1
AVZ3849T SEF version operational mode does

Explanation
not support the func function
Explanation command for each association with an XO dataset.
This message follows the XO dataset status message
SEF rule manager received a command which it MSG3852I.
does not support when operating in the indicated
operational mode.
None. This is an informational message only. The SEF request is rejected because the ruleset status
prevents execution of the request.
AVZ3854I %%INCLUDE processing ignored
when ISPF EDIT source being
compiled, line lineno User response
Examine previously reported conditions to determine
Explanation the cause of the problem.
A %INCLUDE statement was detected in the source AVZ3887I RULESET rsname additinfo1,
of the Product REXX program being compiled. The additinfo2 … additinfo8
procedure source is being fetched from the current
ISPF Edit session and %INCLUDE is not supported in Explanation
this environment.
An error occurred while processing an SEF request
and the status of a ruleset is effected. This message
User response
follows the original error message to warn of
The %INCLUDE statement, with its including comment additional/on-going ramifications from the error.
delimiters is not processed. The original text is
preserved in the procedure source being fetched from User response
the current edit session.
The server takes the action reported in this message
AVZ3855I %%INCLUDE statement syntax in order to recover from the previously reported error
invalid, line lineno cause.
AVZ3888E Required master WWW ruleset
Explanation
not defined - HTTP processing
A %INCLUDE statement was detected in the source impossible
of the Product REXX program being compiled, but the
statement was incomplete. /*%INCLUDE, the named Explanation
member, and */ must all be present on a single source
line. The member name must be less than or equal to SEF Rule manager did not find a Master WWW ruleset
8 bytes in length. definition. The rule manager will not enable ANY WWW
rulesets.
User response
User response
The %INCLUDE statement is rejected
Check your initialization procedure, SWSxIN00, to be
AVZ3856I %%INCLUDE member (member) sure it defines ONE master WWW ruleset using the
not found, line lineno "WWWCLASS(MASTER)" keyword.
AVZ3889I SEF version OPERATIONAL MODE
Explanation
DOES NOT SUPPORT THE func
A %INCLUDE statement was detected in the source FUNCTION
of the Product REXX program being compiled, but the
member named in the statement cannot be found in Explanation
either the library dataset where the source member
resides or in the SYSEXEC library concatenation. SEF rule manager received a command which it
does not support when operating in the indicated
operational mode.
User response
The %INCLUDE statement is rejected User response
AVZ3886E RULESET rsname additinfo1, Correct the command, and re-issue.
additinfo2 … additinfo8
AVZ3890I msgs

SEF rule manager uses this message to list formatted This message is issued in response to an SEF INDEX
control block output messages (msgs). URL command. It is the first message returned for
each active rule. The data items returned, blank
User response delimited, in this message are the ruleset name, the
rule member name, master/subord, gateway/target,
These messages contain the formatted control block count of rule process sections, and the URL match
image. criterion.
AVZ3891I output
User response
SEF rule manager issued the current message to list AVZ3896E RULESET OFFLINE rsname dsname
ruleset information to the output area. ruletype errdesc

The current message is statistical and lists the rulesets An SEF request was made that required that a ruleset
in the output area. No response is required to this be opened for processing, but the ruleset is currently
message. Check the rule output listing, and make stopped or offline.
choices accordingly.
AVZ3892I INDEX COMMAND OPERAND User response
(operand) IS NOT VALID - NO
Take action to place the ruleset online, and re-issue
ACTION TAKEN
the request. One common problem is that the ruleset
dsname no longer exists.
Explanation
AVZ3897E RULESET rsname is not defined
This message is generated if an invalid INDEX
command is passed to the ADDRESS SEF host
Explanation
command environment.
An SEF request was made that required that a ruleset
User response be opened for processing. The ruleset is not defined to
the system.
No action is taken, and the command is not processed
further.
User response
AVZ3893E SEF RULESET rsname HAVE
Check the list of defined rulesets to determine if the
INVALID RULETYPE(ruletype) -
ruleset was not properly defined or specify the correct
RULESET STOPPED/OFFLINE
ruleset name.
Explanation AVZ3898W RULESET rsname1 AND rsname2

ARE BOTH DEFINED AS
While opening a ruleset SEF, SEF detected that the MASTER WWW RULESETS -
ruleset's definition contains an invalid RULETYPE() RULESET rsname2 FLAGGED WITH
specification. STATUS(OFFLINE)

The ruleset is considered to be offline and is not When the SEF rule manager attempted to process
opened. Check for causes that might explain the the list of rulesets defined to the system, it found
invalid RULETYPE() designation for the ruleset named that more than one master WWW ruleset had been
in the message. defined. Only one ruleset can be defined with
RULETYPE(WWW) WWWCLASS(MASTER) attributes.
AVZ3895I data
User response AVZ3902E var1 var2 SECTION IN RULE var3
The second ruleset defined as a master WWW
ruleset will not be processed. It is flagged with Explanation
STATUS(OFFLINE) and stopped so that no processing The SEF rule manager did not find a matching section
of the data set will occur until the RULESET definition header table entry. The processing of the current rule
has been changed. is terminated.
AVZ3899W No SEF rulesets have been defined
User response
Explanation Ensure that the rule sections are properly coded and
When the SEF rule manager attempted to process the valid. Review the rule for obvious coding errors. Refer
list of rulesets defined to the system, it found that no to the product Server Administration Guide for more
valid rulesets had been defined. details on rule coding. Correct the above problem, and
restart.
User response AVZ3903E INVALID CRITERION crit IN
ruletype rule rulename
The current message is a rule status report message
and may not require any response. If rulesets should
be defined, check your start-up procedure for errors Explanation
which might have occurred while processing DEFINE SEF rule manager detected an invalid criterion (crit)
RULESET statements. when processing the current rule. Only a single
AVZ3900T RULE rsname.rulename FOR wildcard is allowed in the rule criterion. Rule
ruletype pc status processing is terminated.

SEF rule manager issued the current informational Check the error message text for the criterion field,
message to report the status of the current rule. The and ensure that the criterion is limited to one match
ruleset rulename is now enabled. criteria or one wildcard. Refer to the product Server
Administration Guide for more details on the firing of
pc represents primary criterion rules and the valid criteria.
AVZ3906I output
User response
The current message is a rule status report message Explanation
and does not require any response.
SEF rule manager issued the current message to list
AVZ3901E service OF operand FAILED, the rule data set index (prefix/suffix) to the output
RC=rcode area.

A configuration, authorization, runtime, or I/O error The current message is statistical and lists the rulesets
has been encountered while executing an SEF rule in the output area. No response is required to this
manager request. The request cannot be completed, message. Check the rule output listing, and make
but may be possible at a later time. The SEF ruleset choices accordingly.
involved with the request may be placed into STOPPED
or OFFLINE state. AVZ3907I SEF is not active

Examine surrounding messages to determine if SEF rule manager has detected that SEF is not active.
the SEF request failed because of insufficient
authorization on the part of the requestor to execute
the request. If the request is due to a configuration
error, you may find it necessary to correct server
startup parameters and restart the server.

User response AVZ3912E No ISPF statistics for rule
rulename in rsname.
Ensure that the product is started and SEF is active.
Contact your local product systems programming
group for assistance. Explanation
AVZ3908I INVALID SEF REQUEST TYPE SEF rule manager found no ISPF statistics for the rule
reqtype rsname rulename member in the indicated ruleset.

SEF rule manager detected an invalid SEF rule request Ensure that statistics exist for the rule in the PDS
type during rule request processing. The current directory and that ISPF statistics is turned on.
request is terminated. AVZ3913E ind Criterion syntax error lineno in
rule rulename
User response
Check the current request for any errors. Check the Explanation
request type in the error message text against the rule A syntax error was detected in a rule while attempting
sections in the product Server Administration Guide to enable it. The time criteria are syntactically
for any inconsistencies. Review the problem, and take incorrect.
corrective action.
ind may indicate "Time" or "Screen"
AVZ3909I RULE rsname.rulename IS NOT
ENABLED
User response
Explanation Check the product Server Administration Guide for the
correct syntax. Correct the rule, and re-enable it.
An attempt to disable a rule failed because the rule is
not currently enabled. AVZ3914E INCONSISTENT ind CRITERION
lineno IN RULE rulename
User response
Explanation
No action required.
A time or screen (ind) criterion was syntactically
AVZ3910I No rules enabled in Rule Set correct but inconsistent. A starting time greater than
rsname an ending time or a row range whose first row value is
larger than the second may cause this error message.
Explanation
This is an informational or status report message User response
issued by SEF rule manager. Either no rules exist or Correct the inconsistent criterion, and re-enable the
no rules are enabled in ruleset. rule.
AVZ3915E MAXIMUM OF maxno ind
User response CRITERIA EXCEEDED IN RULE
No action required. rulename
AVZ3911I RULE rsname.rulename not found

Explanation
Explanation Too many screen or time (ind) criteria were specified in
the header section of a rule.
SEF rule manager did not find the member name that
contains the current rule. The rule request is aborted.
User response
User response Reduce the number of time or screen criteria in the
rule, and re-enable the rule.
Ensure that the rule listed in the rule name field of the
error message exists, or create one before invoking the
request.
AVZ3916I TOD RULE rsname.rulename HAS AVZ3921W Rule rulename contains no
BEEN DISABLED - ALL TIME executable sections
CRITERIA HAVE EXPIRED
Explanation
Explanation
SEF rule manager found no executable sections in the
SEF rule manager disabled the current rule (TOD) after current rule.
all time criteria expired. This may or may not be an
error. User response
Review the current rule code to make sure it is
User response
executable code (e.g. RETURN SUPPRESS in PROC
The current TOD rule time criterion is not valid beyond section if this is a message rule). Without any
the last fire time. If rule was intended to go beyond the executable sections, the current rule cannot be
last fire time, ensure that the next TOD rule is created processed by the SEF manager.
with the required start/stop/interval or time criteria
desired. AVZ3922I MATCH TABLE LIST - d1 t2
AVZ3918E Error 43 reqtype program, line Explanation

lineno: routine routine not found
The SEF rule manager issued this message to list the
match table (message parameter list).
Explanation
SEF rule manager did not find the current routine. User response
User response
Review the current rule code for the correct invocation AVZ3923I MATCH TABLE AT addr PFX=prefix
and coding of a routine name. Refer to the product SFX=suffix LEN=length PRI=pcode
Server Administration Guide for calls to routines. ROOT AT root
Correct the problem, and restart.
Explanation
AVZ3919E NO VALID RULE HEADER FOUND
IN RULE rulename - errdesc SEF rule manager issued this message to list the
match table at the address shown in the message text.
Explanation
User response
SEF rule manager did not find a valid rule header in the
current rule. None. This message is for informational purposes only.
AVZ3924I Match table list empty
User response
Review the current rule code for a valid rule header. Explanation
Refer to the product Server Administration Guide for
SEF rule manager issued this message to list a match
rule header coding. Correct the problem, and restart.
table entry that is empty.
AVZ3920W Following line(s) ignored in rule
rulename: User response
Explanation
AVZ3925I seqno rsname.rulename critlvl
SEF rule manager found a line that was skipped and
NODE LVL=lvl ADR=addr1
will ignore the following lines.
LO=addr2 HI=addr3 AORL=addr4
LEN=length
User response
Review the current rule code, and eliminate any blank Explanation
lines. Correct the rule, and restart.
This message is for debugging purposes only.

User response started, SEF initialization processing will abort. After
startup, the excess rulesets are immediately placed
None. into stopped/offline status.
The variable fields of the message text are: sqno AVZ3930E RULESET rsname rsprefix errmsg1
sequential order rule ruleset.rule crit criterion level errmsg2
node nesting level addr1 address current OPTI addr2
low subtree address addr3 high subtree address addr4
address current AORL length AORL length Explanation
AVZ3926I SECTION section INVALID errdesc SEF rule manager detected that the current ruleset
ON LINE lineno high-level qualifier is a duplicate of another high-level
qualifier.
Explanation
User response
The SEF facility found an invalid section header within
the rule, so the rule could not be enabled. The current ruleset naming convention is incorrect.
Ensure that the ruleset definition complies with the
standard code for product rulesets. Refer to the
User response product Server Administration Guide for more details.
Correct the event procedure, and re-enable. AVZ3931E program dsname is too large -
AVZ3927I No match for rulename input buffer overflow
The product rule manager did not find a match for this SEF rule manager detected an input buffer overflow.
rule. The program is too large to be loaded in the current
buffer.
User response
User response
Check the current program for input size, and correct
AVZ3928E RULESET rsname rsprefix IS that, if possible. Contact your local product systems
errmsg programming group for help.
AVZ3932E service OF table FAILED, RC=rcode
Explanation
SEF rule manager checked the ruleset prefix string and Explanation
found it to be blank.
SEF rule manager could not setup the Product REXX
external routine table. The GETMAIN failed.
User response
Ensure that the ruleset prefix string is not blank. User response
Refer to the product Server Administration Guide for
information on specifying rules data sets and related Determine why the GETMAIN of the required storage
prefixes. Correct the above problem, and restart. to create the above table failed. Check any MVS
messages for their return codes. Ensure that no exits
AVZ3929E Maximum ruleset count (count) limit the acquiring of the given storage by any ASID.
exceeded Review the current error text, and correct the problem.
AVZ3933E ABEND IN CELL POOL
Explanation PROCESSING DURING func
SEF rule manager's internal list of SEF rulesets has
overflowed. Too many SEF rulesets are defined. Explanation
An abend occurred during cell pool processing
User response initiated by the SEF rule manager.
If the defined ruleset count exceeds the maximum
supported number of rulesets when the server is
User response DSORG or incompatibility in LRECL and BLKSIZE). If a
system 913 abend code is reported, data set access
If the error occurred during a GET, check the product has been disallowed by your security subsystem.
region size. If the error did not occur during a GET,
contact Software Support. AVZ3937E LISTCOMP FOR RULESET rsname
FAILED - NO RULES FOUND
AVZ3934E errdesc BE STORED IN RULESET
rsname - ERROR FOUND FOR
rsname.rulename Explanation
The LISTCOMP command for an individual ruleset
Explanation failed. No saved compile rule was found in the
compiled rule library.
SEF rule manager found the current rule header not
applicable for storage in the current ruleset.
User response
User response Ensure that the given ruleset for the LISTCOMP
command is the valid one, and re-issue the command.
Security rules can only be stored in the security ruleset
(if security rules are found). Also, non-security rules AVZ3938E RULESET- rsname UNABLE TO
cannot be stored in the security ruleset. Ensure that ACCESS COMPILED RULES
the current rule is stored in the appropriate ruleset
environment. Explanation
AVZ3935E CANNOT OPEN ddname (ABEND The COMPILE, LISTCOMP, or DELCOMP SEF command
abcode AT modname+offset) failed.

During the open processing of the compiled rule Ensure that a proper PDS was allocated to the XODSN
library, an abend occurred. keyword of the ruleset specified. Special restrictions
apply to the SWIRULE ruleset, which cannot be
User response compiled by a customer.
Ensure that the given library is a PDS, similar by AVZ3939E SEF COMPILE PROCESSING OF
definition to the other product supplied pre-compiled name FAILED
libraries. Check the message and codes manuals for
the abend code. Most likely, the member does not Explanation
exist or the data set attributes are in error (sequential
DSORG or incompatibility in LRECL and BLKSIZE). If a The COMPILE, LISTCOMP, or DELCOMP SEF command
system 913 abend code is reported, data set access failed.
has been disallowed by your security subsystem. name will be a rule name or a ruleset name
AVZ3936E cmdtype FAILED FOR
rsname.rulename - service OF User response
ddname FAILED
This message should have been accompanied by other
messages.
Explanation
AVZ3940E AUTOENABLED FAILED - name IS
The COMPILE or LISTCOMP SEF (cmdtype) command A REXX EXTERNAL ROUTINE
failed.
Explanation
User response
An AUTOENABLE command was issued for a member
Ensure that the given library is properly allocated. of a ruleset that is actually a Product REXX external
Also, ensure that the given library is a PDS, similar by routine.
definition to the other product supplied pre-compiled
libraries. Check the message and codes manuals for name will be a rule name or a ruleset name
the abend code. Most likely, the member does not
exist or the data set attributes are in error (sequential

User response AVZ3945I rsinfo
Verify your command. Re-issue the command, if
possible. Explanation
AVZ3941W SOURCE OF rulename MODIFIED SEF command LISTINST ruleset (with no rule names)
SINCE LAST COMPILE - SEF WILL produces one line for each enabled ruleset.
USE SOURCE
User response
Explanation The current message is for information purposes only
SEF had detected that a compiled version of the and lists information about the enabled ruleset in the
current rule exists. But, it detected that the source output area. No response is required to this message.
version of the rule has been modified since the last AVZ3946I TYP PROCEDURE (set member)
time the rule was compiled. SEF will use the source SET INVALID parmname VALUE OF
version of the rule for this enablement. parmval

You may want to re-compile the rule or auto-enable it, During initialization processing of a TYP event
which also automatically saves the compiled version of procedure, the REXX routine set an invalid parameter
a rule. value.
AVZ3942I NO ruletype RULES ENABLED IN
RULESET rsname User response
The current message is for information purposes only
Explanation and lists information about the enable attempt. The
This is a product SEF command LISTINST RULETYPE() TYP rule will not be enabled.
informational or status report message. No rules of the AVZ3947I TYP EXECUTION MODULE
type specified are enabled in the ruleset. modname NOT FOUND FOR
varname IN (set member)
User response
No action required. Explanation
AVZ3943I There are no rules currently During initialization processing of a TYP event
enabled procedure, an invalid load module name was specified.

SEF command LISTINST was unable to return rule or The current message is for information purposes only
ruleset statistics because there are no enabled rules. and lists information about the enable attempt. The
TYP rule will not be enabled.
User response AVZ3948W Too many sections found in rule
procedure
AVZ3944I ruleinfo Explanation
More than one process section was found in the rule.
Explanation This restriction may be removed in future releases.
SEF command LISTINST ruleset.rulename produces
one line for each enabled rule in the ruleset. User response
At the present time, only a single process section may
User response be coded within a WWW or RPC rule.
The current message is for information purposes only
and lists information about the enabled rule in the
output area. No response is required to this message.
AVZ3949I ruletype WWW RULE Explanation
rsname.rulename ALREADY
DEFINES THE URL val SEF rule manager attempted to open a data set for the
processing of /*FILE sections. The data set could not
be opened.
Explanation
A duplicate URL criterion value (val) is specified on User response
more than one WWW rule at the same administrative
level. Duplicate URL processing rules may only be Ensure that the ddname specified in the message is
activated when one of the pair resides within the allocated to a data set in the subsystem started task
master WWW ruleset and one resides in a subordinate JCL, or ensure that the correct ddname value has been
ruleset. In such a case, the master rule is always specified within the /*FILE section header.
processed before the subordinate rule, and the AVZ3953T msgtext
subordinate rule is only processed when the master
rule is a header-only, generic rule. If the master rule
contains a procedural specification, such as a REXX, Explanation
FILE, or PROGRAM section, the subordinate rule will The Web transaction invoked an ADDRESS SEF
never be processed. command for intermediate processing. The ADDRESS
ruletype may be MASTER or SUBORDINATE SEF command failed. Messages issued by the
ADDRESS SEF command are logged to the trace using
this message ID.
User response
Disable the duplicate rule before activating the current User response
rule, or change the URL criterion value in the current
rule to a unique value. Examine the messages to see why the original /*FILE
request was rejected.
AVZ3950I output
AVZ3954E MEMBER member NOT FOUND IN
DATA SET ddname
Explanation
SEF rule manager issued the current message to list Explanation
the data set statistics and status.
The indicated member was not found within the
referenced PDS data set. The file-related process is
User response terminated with a member not found error.
The current message is statistical and lists the data set
information. No response is required to this message. User response
Check the PDS output listing, and make choices
accordingly. Examine the messages to see why the original /*FILE
request was rejected.
AVZ3951E DDNAME ddname NOT ALLOCATED
AVZ3955E MEMBER member NOT FOUND IN
DATA SET ddname
Explanation
SEF rule manager attempted to open a data set for the Explanation
processing of /*FILE sections. The data set could not
be opened because the ddname is unassigned. The indicated member was not found within
referenced PDS data set. The file-related process is
terminated with a member not found error.
User response
Ensure that the ddname specified in the message is User response
allocated to a data set in the subsystem started task
JCL, or ensure that the correct ddname value has been Examine the messages to see why the original /*FILE
specified within the /*FILE section header. request was rejected.
AVZ3952E DDNAME ddname COULD NOT BE AVZ3956I FILE ddname NOW status
OPENED (rcode) additinfo

The indicated file has been placed online or offline, as SEF rule manager attempted to allocate a data set for
the message indicates. processing of /*FILE sections. The data set could not
be opened.
status may indicate ONLINE or OFFLINE
User response
User response
Ensure that the dsname specified in the message
None. The message is traced to indicate /*FILE related
exists, or ensure that the correct dsname value has
activation or deactivation of a shared PDS file.
been specified within the /*FILE section header.
AVZ3957I output
AVZ3961I DSNAME dsname DDNAME
ddname ALLOCATED
Explanation
SEF rule manager issued the current message to list Explanation
the PDS member statistics.
The indicated dsname has been allocated to the
indicated ddname.
User response
The current message is statistical and lists the PDS User response
data set member information. No response is required
None. The message is traced to indicate /*FILE related
to this message.
allocation.
AVZ3958E ABEND abcode (rsn) IN
AVZ3962I DDNAME ddname DEALLOCATED
modname+offset DURING service
PROCESSING, SOME FILES MAY
NOT BE status Explanation
The indicated ddname has been deallocated.
Explanation
An abend occurred during file open or close processing User response
at initialization or termination time. Some files may not
None. The message is traced to indicate ddname
have been processed.
deallocation.
User response AVZ3963I Generated DDNAME counter field

rollover occurred
The initialization or termination process continues.
AVZ3959I count of total shared data files now Explanation
status
The 8 byte counter field used to generate ddnames
rolled over.
Explanation
During initialization or termination, this message is User response
issued to indicate the results of file processing.
None. The message is traced to indicate a rollover of
the 8 byte counter field used to generate ddnames
User response occurred.
No action is required, unless some files remain AVZ3964E Member list not valid for
unopened at open time. sequential data sets DDNAME
ddname, DSNAME dsname
AVZ3960E DSNAME dsname could not be
allocated (rcode)
Explanation
The member list function was issued for a sequential
data set. The member list function is available only for
partitioned data sets (PDS or PDSE).
Issue the member list function only for PDS or PDSE SEF rule manager issued the current message to list
data sets. the next concatenated dataset for a single shared-file
DD name or next concatenated dataset for an SEF
AVZ3965T WARNING: OUTBOUND RESP ruleset.
DATA PRECEDES THIS FILE
REQUEST - HTTP RESP PROTOCOL concat represents the concatenation index, relative to
ELEMENTS WILL BE UNUSABLE BY 1
CLIENT
User response
Explanation The current message is statistical and lists the data set
When SWSFILE(SEND) or /*FILE was invoked to information. No response is required to this message.
transmit a file to the HTTP client, the server found Check the PDS output listing, and make choices
that output data had previously been flushed for accordingly.
transmission to the client. The server proceeds with
AVZ3968I service FAILED. RETURN CODE:
the file request after issuing this warning message.
rcode
Because the server's file routines generate HTTP
response protocol headers (such as Content-Type,
Content-Length, Expires, etc.), any data preceding Explanation
these headers will LIKELY cause some unpredictable
SEF rule manager issued the message due to a failure
result at the client. For example, the data sent by
in a system service.
the file routines may not be visible or interpreted
incorrectly (i.e. the client may attempt to process
HTML text as a GIF image), or the client may close User response
the communications session. This problem is generated due to a file processing
error. Correct the file, and re-process your request.
User response
AVZ3969I FORMAT OF SHARED FILE BLOCK
If the output which precedes the file request FAILED - INVALID IDENTIFIER val
was generated by a customer-written transaction
procedure, you can correct this condition by
Explanation
eliminating the preceding output, foregoing the
use of /*FILE or SWSFILE(SEND) within the same An invalid or unmatched identifier value (val) was
transaction, or ensuring that no SWSSEND(FLUSH) specified for an internal FMTSFILE command. Either
operation occurs. the identifier was invalid or the corresponding shared
file block no longer exists.
AVZ3966T External data queue full
User response
Explanation
The shared file block is not formatted and processing
When an SWSFILE operation outputs its results to the continues.
external data queue (QUEUE and MBRLIST functions)
and the external data queue fills before all of the AVZ3970E MATCH CRITERION MUST BEGIN
information can be written, this message is traced. WITH /set - %2.%3

The current SWSFILE operation ends with return code During event procedure enablement, a WWW rule was
28. Increase the size of the external data queue by found to be invalid because its match criterion does
specifying the QUEUESIZE() override on the /*WWW not begin with the specified string. All WWW event
header statement. procedure match criteria must begin with the event
procedure set name unless they are defined in the
AVZ3967I dsname concat master procedure set.
User response
Correct the error, and re-enable the event procedure.

The variable fields of the message text are: set name AVZ3975T RUNAUTH USERID userID -
of event procedure set USERID INVALID
AVZ3971E /*WWW STMT - errtext - %2.%3
Explanation
Explanation The RUNAUTH userid could not be logged on to the
system because the userid was invalid.
During event procedure enablement, a WWW
procedure header statement was found to be coded
incorrectly. The procedure is not enabled. User response
The session is not permitted to proceed. The Web
User response transaction is rejected by rescanning to the SYSTERM/
ERROR/500 URL, indicating a server error (with reason
code 27). Correct the WWW rule that specified the
AVZ3972E /*WWW STMT - key MAY ONLY BE invalid RUNAUTH USERID.
CODED WITHIN THE rule RULESET
AVZ3976E DPRTY OPERAND operand - rsn
- %3.%4
The DPRTY operand value was invalid for the reason
During event procedure enablement, a WWW
specified in the message.
procedure header statement was found to be coded
incorrectly. The indicated keyword may only be coded
on header statements in the master WWW ruleset. The User response
master WWW ruleset must be designated as such by
The WWW rule is not enabled. Correct the WWW rule
coding WWWCLASS(MASTER) on the DEFINE RULESET
which specified the invalid DPRTY operand, and re-
statement that defines the ruleset.
enable it.
User response AVZ3977T WWW task dispatch priority

changed from val1 by val2
The variable fields of the message text are: key Explanation
keyword that is not valid rule name or description of
The dispatching priority of the WWW transaction
master WWW ruleset
subtask has been changed because a match to a /
AVZ3973E /*REXX STMT - errtext - %2 *WWW rule that specified the DPRTY() keyword has
been made.
Explanation
User response
During event procedure enablement, a REXX section
header statement was coded incorrectly. The The WWW subtask continues using the new priority
procedure is not enabled. value.
AVZ3978T override OVERRIDE FAILED IN loc -
User response RC=rcode AT addr
Explanation
AVZ3974T RUNAUTH USERID userID - SETUP
SUCCEEDED A failure occurred while trying to override the
REXX work space or external data queue size. The
WORKSPACE or QUEUESIZE operand may be too large.
Explanation
The RUNAUTH userid has been logged on to the User response
system.
The WWW subtask is re-routed to the system error
recovery procedure, and the transaction aborted.
User response
No action is required. Processing continues.
AVZ3979E ATH LOGON rule must exit with tb represents a trace back value
'ACCEPT' if ACEE is created for
subtask User response
If the error recurs, contact Software Support.
Explanation
AVZ3983E RULESET rsname action REJECTED
An ATH logon procedure has caused the TCBSENV
BY SEF - additinfo
pointer for the current subtask to be set to a non-zero
value. If an ATH logon rule creates an ACEE block,
it must also return with a code indicating that logon Explanation
processing is complete. This prevents ACEE blocks
The indicated ruleset definition or modification
from being inadvertently orphaned or destroyed by
(action) could not be processed into the SEF
intrinsic server security processing.
configuration.

The entire logon request is rejected, and the logon
Correct the original request and resubmit.
request process is aborted with an S0C3 abend.
AVZ3984H SEF ruleset rsname SEF
AVZ3980E RUNAUTH USERID (userID) LOGON
configuration action accepted
FAILED
Explanation
Explanation
The indicated ruleset definition or modification
The RUNAUTH userID specified by the
(action) was processed by SEF and placed into the
WWWDEFAULTRUNAUTH system parameter failed
active configuration.
logon processing during start-up.
User response
User response
None
The HTTP-API initialization process is aborted.
Check to ensure that the userid specified by AVZ3985E XO DATASET dsname ERROR -
the WWWDEFAULTRUNAUTH start-up parameter is additinfo
correct. Check the joblog for related messages about
the userID.
Explanation
AVZ3981I Default RUNAUTH USERID userID An error was encountered while processing the
logged onto system indicated executable object (XO) dataset

The RUNAUTH userID specified by the None
WWWDEFAULTRUNAUTH system parameter has been
logged on to the system. AVZ3986E FILE ddname action REJECTED BY
SEF - additinfo
User response
Explanation
HTTP-API initialization processing continues.
The indicated shared file definition or modification
AVZ3982E INDEXED DELETE OF (action) could not be processed into the SEF
rsname.rulename (crit) FAILED configuration.
(TRACE=tb) - RULE NOT DELETED
User response
Explanation
Correct the original request and resubmit.
The indicated rule could not be deleted from the
indexes of the internal rule search tree. The rule is not AVZ3987H Shared file ddname SEF
deleted, but it will be disabled. configuration action accepted
crit represents the rule criterion

The indicated shared file definition or modification During event procedure enablement, a /*FILE section
(action) was completed successfully was not enabled due to the error given.

None Correct the error, and re-enable the event procedure.
AVZ3988E SEF task is terminating due AVZ3991H SEF RULESET rsname DATASET
to severe configuration or dsname IS status
environmental error with critical
resource Explanation
The indicated ruleset dataset status has changed.
Explanation
The SEF subtask will self-terminate, causing the server User response
to shut down. A critical resource is not configured
properly or an environmental error prevents access None. This message is for informational purposes only.
to the critical resource. Generally, this means that a
AVZ3992T SEF RULESET rsname DATASET
definition, OPEN error, or rule auto-enablement error
dsname IS status
has occurred for a critical shared file or an ATH, TYP, or
WWW ruleset with WWWCLASS(MASTER).
Explanation
User response The indicated ruleset dataset status has changed.
Examine preceding message to determine the
resource or definition which is missing, was undefined, User response
or which cannot be accessed. Correct the start-up
definitions pertaining to the resource and restart the
server. AVZ3993H SEF RULESET rsname DATASET
dsname WAS STOPPED. RSN: rsn
AVZ3989W SEF RULE MGR ABEND
abcode REASON rsncode
AT modname+offset WHILE Explanation
PROCESSING REQUEST plist
The indicated ruleset was stopped.

The SEF rule manager trapped and recovered from
This is an informational message. If the ruleset should
an ABEND at the location shown. The rule manager
not be stopped, then review the Trace Browse and
returns the ABEND completion code to the service
SYSLOG to determine what caused the ruleset to stop.
requestor, which must determine whether the error
is of critical importance. The invoker may ignore, AVZ3994T SEF RULESET rsname DATASET
compensate for, or escalate the error, as appropriate dsname WAS STOPPED. RSN: rsn
to the request.
Explanation
User response
The indicated ruleset was stopped.
Examine preceding and following messages to
determine the resource or definition which is missing, User response
incorrectly configured or which cannot be accessed.
Correct the SEF start-up definitions pertaining to the This is an informational message. If the ruleset should
resource and restart the server. not be stopped, then review the Trace Browse and
SYSLOG to determine what caused the ruleset to stop.
AVZ3990E /*FILE STMT - errtext
AVZ3998I data
Explanation AVZ4003H service
SEF rule manager uses this message to list formatted
control block output messages for shared files, Explanation
represented here by data. This message is used for tracing certain VTAM-related
events within the product.
User response
These messages contain the formatted control block User response
image. No action is required unless the trace messages are
AVZ4000H errtext appearing without your requesting tracing.
AVZ4004H service - luname
Explanation
This is a general purpose message for certain VTAM® Explanation
errors. This message is used for tracing certain VTAM-related
events within the product.
User response
Not every condition reported by this message is really User response
an error. Read the text of the message carefully to No action is required unless the trace messages are
determine whether an error has occurred or not. If an appearing without your requesting tracing.
error has occurred and you cannot resolve it, contact
Software Support for assistance. AVZ4005H service - lu/mode
AVZ4001H UNKNOWN service CODES - R0=R0
R15=R15 Explanation
This message is used for tracing certain VTAM-related
Explanation events within the product.
This message reports VTAM return and reason codes
(R0 and R15) that are unknown to SAVZ. User response
No action is required, unless the trace messages are
User response appearing without your requesting tracing.
This may indicate some type of internal error. It is also AVZ4006H VTAM APPLID NOT SET - LU 6.2
possible that you are running a version of VTAM that is SUPPORT NOT ACTIVATED
not yet supported by SAVZ. If the version of VTAM that
you are running DOES appear to be supported, contact Explanation
Software Support.
The local VTAM applid has not been set. VTAM
AVZ4002H UNKNOWN service CODES - processing on this copy of AVZ is impossible.
RCPR=code1 RCSC=code2
User response
Explanation
The VTAM task of the main address space shuts down.
This message appears in conjunction with the 4001H This is not an error unless you actually did specify
message. the VTAM applid in the xxxxxIN00 EXEC. Note that
code1 and code2 represent primary and secondary rpl other communication protocols may be activated even
extension codes, respectively though VTAM LU6.2 is not being used.
AVZ4007H INVALID FMH-5 CONTROL BLOCK
User response RECEIVED FROM luname
This may indicate some type of internal error. It is also
possible that you are running a version of VTAM that Explanation
is not yet supported by the product. If the version An invalid FMH-5 control block was received from
of VTAM that you are running DOES appear to be a peer LU (luname). The invalid FMH-5 block will
supported, contact Software Support..

be ignored, and the conversation will be terminated preceding ABEND event trace records GPR14 retry
immediately. register contains the true target retry address, given
control after shunting.
User response AVZ4015I count new SRBs scheduled with
This error will only occur if another product tries PRIORITY=CURRENT because no
to establish a conversation with the main product WLM enclave is joined
address. This error should be reported to whoever is
responsible for the other product. Explanation
AVZ4010T TCB MODE SWITCH ERROR: This message is issued when a change is noted
errdesc additinfo in the number of SRBs that have been scheduled
with PRIORITY=CURRENT instead of the preferred
Explanation PRIORITY=ENCLAVE option. This occurs when a task
is not joined to a WLM enclave at the time it schedules
An error was detected while switching from SRB to an SRB. The SRB is scheduled with the same priority
TCB dispatchable unit execution mode. as the scheduling task. This precludes execution of the
SRB on the zIIP co-processor.
User response
User response
The request to switch from SRB to TCB fails. The SRB
mode routine generates an S0C3 ABEND if it cannot No action is normally required. Some sites may receive
continue or continues processing in SRB mode, as these notifications with regular frequency; other sites
indicated in the message. may rarely or never receive these notifications. If you
note an increase in the number of these message,
AVZ4012T SRB MODE SWITCH ERROR:
contact Software Support for further analysis.
errdesc additinfo
AVZ4016S FRR PARAMETER UNSTACK
Explanation ERROR - rsn
An error was detected while switching from TCB to

Explanation
SRB dispatchable unit execution mode.
This message is issued when a PC routine attempts
User response to unstack and restore nested FRR parameters during
SRB-mode execution. The unstack operation has failed
The request to switch from TCB mode fails. The TCB because the state of the current FRR stack has
mode routine generates an S0C3 ABEND if it cannot changed unexpectedly.
continue, or continues processing in TCB mode, as
indicated in the message.
User response
AVZ4014T Shunting to mode execution mode
The PC routine generates an S0C3 ABEND following
prior to ABEND retry, retry GPR14
issuance of this message. Existing FRRs may receive
in ABEND traces contains retry
control and attempt to recover. The PC-call stack areas
target address
will not be recovered until check limits processing
re-activates them during periodic processing. Contact
Explanation Software Support.
A retry is being attempted following an intercepted AVZ4017T TYPE-1 LDU TERMINATION CALL
ABEND. The dispatchable unit of work is currently ERROR - failrsn additinfo
executing in a different mode (SRB or TCB) than
the retry routine expects. The server is transferring
Explanation
execution into the correct dispatch mode, before
retrying. An error was detected while terminating a Type-1
Logical Dispatchable Unit construct used for TCB/SRB
User response mode switches. The request for LDU termination is
bypassed.
This message is traced for ABEND retries only when a
shunt to a different execution mode is required, and
only when tracing pause element dispatch activity. The
The termination routine returns to the calling routine. Generic Userid (TLS) support is disabled when a DRDA
This message serves as notification of a potential backend connection is in use. The generic userID sent
logic error in End-of-Task cleanup processing since by the client is ignored for Db2 processing. It will still
the routine was entered to process LDU termination be used when creating SMF log records, etc..
for a subtask that cannot support this kind of Logical
Dispatchable Unit processing. AVZ4022T CONNECT TO DDF HOST=dom/ip,
PORT=portno, CMIDADR=addr
AVZ4018I count New SRB schedule CMID=image
(IEAMSCHD) failures encountered
Explanation
Explanation
This message is traced when a DRDA connection has
This message is issued when a change is noted in been successfully opened.
the number of SRBs that were not scheduled, due to
failures returned by the IEAMSCHD service. The cause User response
of these failures MAY be that the WLM enclave, into
which the SRB is being scheduled, is no longer valid. None
AVZ4023T calltype CALL TRACE: crlist
User response
Contact Software Support for further analysis. Explanation
AVZ4019T Session lost (hung) due to type-4 This message produces a calling routine (crlist) trace
LDU schedule failure
User response
Explanation
None
This message is traced if a TYPE-4 LDU cannot be
AVZ4024T Passticket generation failed for
constructed or scheduled to close the communication
USERID=userID, APPL=appl, with
session. The session is orphaned and remains hung
RC = rcode
until the server is recycled.

A passticket could not be generated for the indicated
Contact Software Support for further analysis.
userID and APPL name combination.
AVZ4020T DRDA processing bypassed for
connection to subsys, failrsn User response
Ensure RACF PTKTDATA class is activated and that a
Explanation
resource matching the APPL name is defined in the
This message is traced if DRDA processing is being class. The possible return codes are as follows: RC =
skipped for the connection. x'04' - Invalid passticket parameter list RC = x'08' -
No PTKTDATA profile found for the APPL name RC =
x'0C' - No task or address space ACEE found RC = x'10'
User response
- Caller is not authorized RC = x'14' - The PTKTDATA
The connection will be processing using standard class is not active
RRSAF interfaces to the target Db2 subsystem.
Contact Software Support for further analysis. AVZ4025S Metal-C function func in module
modname not found, failrsn
AVZ4021T Generic (TLS) USERID userID
ignored for DRDA connection Explanation
During initialization a Metal-c function requiring
Explanation
external visibility was not found.
This message is traced if a generic (TLS) userID has
been sent with the current SQL request message.

User response first part of the initial transmission. The initial setup
determines if the session is being opened for HTTP or
Initialization is aborted. DRDA processing in the server ODBC/JDBC connections. The leading portion of the
may ABEND unexpectedly when the missing function message will indicate if the session was for HTTP or
is invoked. Contact Software Support for assistance. ODBC/JDBC if this is known at the time of failure.
AVZ4026I DRDA modules not loaded, It will also indicate if SSL encryption is in use for
Machine below architecture-9 the session when this can be determined. The client
level, Found(lvl) IP address is always included in the message which
also contains an explanation of the failure that caused
session setup to fail.
Explanation
During initialization the installed machine instruction User response
set is examined to determine the corresponding XL
C/C++ compiler architecture level. DRDA modules are The connection to the client system is terminated. The
only provided to support machines at ARCH(9) level client application will probably report an error. Check
and above. for any client system error messages and related trace
messages reporting communications or SSL problems.
Often for a timeout, only a SELECT trace message will
User response precede this message. The SELECT completed with
The DRDA processing modules are not loaded no sockets ready to receive, which is recognized as a
and DRDA support is disabled. MSG4020T with timeout failure.
explanation "Z196 (2817-xxx) INSTRUCTION SET AVZ4040E errdesc
REQUIRED" is traced if an attempt to open a DRDA
connection is made.
Explanation
AVZ4027T ind being issued to avoid DRDA
idle thread time limit An error occurred processing a partner ACI session for
this connection.
Explanation
User response
ind indicates that 1) A ROLLBACK is being issued
automatically because the client ODBC/JDBC session The session will be terminated.
has been idle for an extended period. A ROLLBACK AVZ4041T service buffer size lgth1, address
is issued to release PREPAREd statements so that addr, length lgth2
the DRDA connection can be put into INACTIVE state
before DRDA terminates the idle connection at the
end of the IDTHOIN time limit. OR 2) , a SNDPKT Explanation
(ping) request is being issued automatically because An error occurred processing a partner ACI session for
transmission of the current response to the client is this connection.
taking longer than the DDF idle time limit. Exchanging
a SNDPKT (ping) request/response reset the idle service may indicate GET or FREE
connection time limit DRDA imposes on active but idle The message contains two length values; lgth1
connections. represents requested buffer length, and lgth2
represents returned buffer length
User response
A ROLLBACK is issued once before awaiting additional User response
client input. A SNDPKT request is issued periodically The session will be terminated.
while transmission of a large response to the client is
underway. AVZ4042E Parallel I/O ACI processing
disabled
AVZ4030T errdesc TCP/IP
Explanation
Explanation
An error occurred during initialization of ACI support
Setup of a new session failed for the reason reported for Parallel I/O processing.
in the message. Normally, the failure is due to a lost
connection or timeout while attempting to receive the
Parallel I/O processing is disabled. MapReduce is tracing information about the session.
AVZ4043T errdesc additinfo
User response
Explanation MAP REDUCE processing of this request continues.
MAP REDUCE was unable to process this VSAM data AVZ4048S BRFRSV unable to decrement
set. If the VSAM KSDS is too small, it cannot be OPDM active count. Service
subdivided for parallel processing by ACI tasks. At a name,class,service
minimum, the VSAM KSDS must have two sequence
set records. The size of such a file will depend upon Explanation
the CI size of the index, and upon how keys get
compressed in the sequence set records. Service map for ACI service not found by free server
routine Monitor ACI service to ensure that it does not
reach Maximum Active servers.
User response
We recommend disabling MapReduce for the data map User response
for this data set to eliminate the overhead of starting
and stopping unneeded ACI processing tasks. The Schedule a restart of the Server at your earliest
VSAM file will be processed by a single task, and MAP convenience.
REDUCE will not be used for this file.
AVZ4050E Invalid HTTP headers - errdesc -
AVZ4044E Map Reduce processing disabled received from TCP/IP
An error occurred during initialization of ACI support Invalid HTTP headers were received from a remote
for MAP REDUCE processing. system. The invalid HTTP headers could not be
processed.
User response
User response
MAP REDUCE processing is disabled.
AVZ4045E ACI FUNCTION func FAILED, client application will probably report an error. Check
RC=rcode errdesc for any client system error messages. If the failure
continues, contact Software Support.
Explanation
AVZ4051E SSL CONNECTION FAILED -
An error occurred processing a MAP REDUCE ACI errdesc - RECEIVED FROM TCP/IP
session.
Explanation
User response
A client application attempted to establish a
The session will be terminated. connection to the host using SSL. The connection
could not be created for some reason related to SSL
AVZ4046T errdesc additinfo processing.

An error occurred during processing of a MAP REDUCE The connection to the client system is terminated. The
request. client application will probably report an error. Check
for any client system error messages. If the failure
User response continues, contact Software Support.
MAP REDUCE processing of this request is terminated. AVZ4052T name1 (name2,additinfo) - RV=rval
RC=rcode RE=rsncode
AVZ4047T tracedesc additinfo

An Unix System Services callable service request was Contact Rocket Software Support.
issued and the results were unexpected.
AVZ4081T Insufficient storage reserve
The message contains two name values; name1 for type (storamt) detected,
represents the callable service entry point name, and connection rejected
name2 represents the callable service formal name
Explanation
User response
The storage reserve for the specified area type (LSQA,
This message is traced to indicate an expected return Private or EPrivate) has been exceeded. The current
value or return code from a USS callable service. attempt to connect to the host has been rejected.
Subsequent processing depends on the call issued. If The host session will be terminated. The storage
the problem continues, contact Software Support. reserve values are either calculated or set via product
parameters.
AVZ4053E OPTPIN timed out waiting for a
session to be passed
User response
Explanation Contact Software Support for advice on this matter.
OPTPIN was placed in posted state in anticipation of AVZ4082T Maximum connected session limit
being passed a new connection, but the new session is set to zero, server not accepting
ECB was never posted. The connection attempt is new connections
abandoned.
Explanation
User response
The maximum connected session limit
This message is trace to indicate an expected (CONCURRENTMX parameter) is currently set to ZERO.
connection was not successfully passed from the The server will not accept any new client connections.
listening task to the service task (OPTPIN). If the A limit of zero is normally set during a quiesce period,
problem continues, contact Software Support. prior to shutdown, allowing existing client connections
to complete their operations normally. Depending on
AVZ4054T No data read from socket - errdesc
the setting of QUIESCESYSTEMTYPE, existing client
- received from TCP/IP
sessions will be cancelled (IMMEDIATE) or allowed to
terminate normally (ATTRITION).
Explanation
After 10 attempts to receive data( TCP/IP read) we User response
returned with zero bytes read and no indication of any
Change the CONCURRENTMX parameter to a non-zero
kind of network error
value if new client connections should be allowed.
User response AVZ4083T SQL is not activated on the server.

client application will probably report an error. Check
Explanation
for any client system error messages. If the failure None.
continues, contact Software Support.
AVZ4080T Invalid logon attempt by User response
an unknown client detected,
connection rejected.
AVZ4084T ODBC driver connections are not
Explanation activated on the server. Session
rejected.
An attempt was made to logon by an unknown client
driver. A connection to the server can only be made by
Explanation
a valid client driver. The connection is rejected.
None.
User response AVZ4089T STORED PROCEDURE CALLS
ARE NOT SUPPORTED WHEN
Contact Rocket Software Support. USING EXTENDED CURSOR POOLS
AVZ4085T Transaction Level Security is not (EXCU=YES).
activated on the server. Session
rejected. Explanation
The product does not support stored procedure calls
Explanation when the client is connected to the server with
None. extended cursor pool support enabled (EXCU=YES).

Contact Rocket Software Support. Reconfigure the client to disable the extended cursor
pool support (EXCU=NO).
AVZ4086T Network authentication is not
enabled on this server. Session AVZ4090T Access to IMS/TM is not activated.
rejected
Explanation
Explanation None.
A client application has attempted to connect to
the host using network authentication (SECU=YES), User response
but the server is not configured to allow network
authentication. Contact Rocket Software Support.
AVZ4091T Access to IMS/TM is not enabled,
User response set the desired IMS/OTMA
and/or IMS/APPC initialization
The server rejects the connection request. parameters
AVZ4087T Access to IDMS is not activated.
Explanation
Explanation The product is not enabled for use with IMS/TM from
None. client applications. The current request to use client to
connect to IMS/TM on the host has been rejected. The
current host session will be terminated.
User response
Contact Rocket Software Support. User response
AVZ4088T Access to IDMS is not enabled, If access to IMS/TM from client applications is needed,
set the desired APPC/IDMS enable IMS by setting the appropriate IMS connectivity
initialization parameters parameters. You may use either IMS/OTMA or IMS/
APPC as the transport for communication to IMS from
Explanation the product Server address space.
The product is not enabled for use with IDMS from AVZ4092T Access to CICS is not activated.
client applications. The current request to use client to
connect to IDMS on the host has been rejected. The Explanation
None.
User response
User response
If access to IDMS from client applications is needed,
enable IDMS by setting the appropriate IDMS Contact Rocket Software Support.
connectivity parameters. You may use APPC/IDMS as AVZ4093T Maximum number of type (count)
the transport for communication to IDMS from the already connected, connection
product server address space. rejected.

None. If access to IMS/DB from client applications is
needed, enable IMS/DB by setting the DBTCL product
User response parameter to YES.
Contact Rocket Software Support. AVZ4098T No active started task copy of the
product located
AVZ4094T Access to Adabas is not activated.
Explanation
Explanation
The userid and password provided by the client
None. application can not be validated because there is no
active started task copy of the product. A started
User response task copy of the product is required for userid
and password validation if the client application is
Contact Rocket Software Support. connecting to a test copy of the product running under
TSO. This error can only occur while attempting to
AVZ4095T Access to Adabas is not enabled,
connect to a test copy of the host code running under
enable access by setting the
TSO.
ADABAS parameter value to YES

The session is not permitted to proceed. The
The product is not enabled for use with Adabas from
installation must activate a started task copy of the
client applications. The current request to use client to
product before connections to TSO copies of the
connect to Adabas on the host has been rejected. The
product will be allowed to proceed.
AVZ4099T CLIENT USERID userID1 UNEQUAL
User response TO TSO USERID userID2
If access to Adabas from client applications is needed,

enable Adabas by setting the ADABAS product
Explanation
parameter to YES. The userid provided by the client application is not the
same as the TSO userid running the test copy of the
AVZ4096T Access to VSAM is not activated.
product. The connection attempt is rejected, and the
connection is severed. This error can only occur while
Explanation attempting to connect to a test copy of the host code
running under TSO.
None.

The session is not permitted to proceed. The client
must supply a valid userid/password combination (for
AVZ4097T Access to IMS/DB is not enabled, the host) in order for the session to proceed. Change
enable access by setting the the client's userid to be the same as the TSO userid.
DBCTL parameter value to YES
AVZ4100E BIND WITH rtype rhost FAILED -
NO MATCHING errdesc
Explanation
The product is not enabled for use with IMS/DB from Explanation
client applications. The current request to use client
The bind with the remote system failed because the
to connect to IMS on the host has been rejected. The
local and remote systems could not agree on certain
AVZ-to-AVZ communication parameters.
User response a userid/password validation. This form is used for
unsuccessful userid/password validations.
The bind process has failed. No communication with
the remote system is possible. Note that it is NOT a
VTAM bind that has failed. The bind referred to by this User response
message is a n AVZ-to-AVZ bind. Retry the process. If The session is not permitted to proceed. The client
the failure continues, contact Software Support. must supply a valid userid/password combination (for
AVZ4101T Password validated for USERID the host) in order for a session to proceed. Ensure that
userID from rtype rhost the client's classification as untrusted is valid. If it is
not, use the ADDRESS AVZ MODIFY LINK command to
change its status.
Explanation
AVZ4105E Bind failed - no matching
The userID/password combination from a remote (and compression type
untrusted) client was successfully validated.
Explanation
User response
The bind with the remote system failed because
No action is required. Processing continues. the local and remote systems could not agree on a
AVZ4102T LOGON attempt failed for USERID compression type.
userID from rtype rhost
User response
Explanation The bind process has failed. No communication with
A remote client was unable to connect for one of the the remote system is possible. Note that it is NOT a
reasons: (1) the userid/password combination may not VTAM bind that has failed. The bind referred to by this
have been valid or (2) the System Event Facility (SEF) message is an AVZ-to-AVZ bind. Retry the process. If
may have rejected the logon attempt. the failure continues, contact Software Support.
AVZ4106E BIND FAILED - NO MATCHING
User response POINTER ENCODING TYPE
The session is not permitted to proceed. The client
must supply a valid userid/password combination (for Explanation
the host) in order for a session to proceed. Ensure that The bind with the remote system failed because the
the client's classification as untrusted is valid. If it is local and remote systems could not agree on a pointer
not, use the ADDRESS AVZ MODIFY LINK command encoding type.
to change its status. If the client was rejected by the
System Event Facility (SEF), the SEF ATH event logon
rule may need to be modified. User response
AVZ4103T msgtext The bind process has failed. No communication with
VTAM bind that has failed. The bind referred to by this
Explanation message is an AVZ-to-AVZ bind. Retry the process. If
This message is used to display any ACF2/RACF the failure continues, contact Software Support.
message that may have been created as a result of AVZ4107E BIND FAILED - NO MATCHING
a userid/password validation. This form is used for DATA ENCODING TYPE
successful userid/password validations.
Explanation
User response
The bind with the remote system failed because the
None. This message is for informational purposes only. local and remote systems could not agree on a data
AVZ4104T msgtext encoding type.

This message is used to display any ACF2/RACF The bind process has failed. No communication with
message that may have been created as a result of the remote system is possible. Note that it is NOT a

VTAM bind that has failed. The bind referred to by this Explanation
message is an AVZ-to-AVZ bind. Retry the process. If
the failure continues, contact Software Support. The LU 6.2 processing routine detected an invalid LU
name string. The LU name string cannot be used for
AVZ4108E BIND FAILED - NO MATCHING further processing.
APPLICATION TYPE
User response
Explanation
Report the error to Software Support. The complete
The bind with the remote system failed because the message will be needed to diagnose the problem. One
local and remote systems could not agree on an or more connection attempts may fail and have to be
application. retried.
AVZ4112T Usage restricted to oem.
User response
The bind process has failed. No communication with Explanation
VTAM bind that has failed. The bind referred to by this None.
message is an S__-to-S__ bind. Retry the process. If
the failure continues, contact Software Support. User response
AVZ4109E BIND FAILED - NO MATCHING Contact Rocket Software Support.
PROCESSING FUNCTIONS
AVZ4113T %1
Explanation
Explanation
The bind with the remote system failed because
the local and remote systems could not agree on A connection is rejected for one of the following
processing functions. reasons:
• The maximum number of concurrent users has been
User response reached.
• Some sort of virtual storage resource shortage has
The bind process has failed. No communication with
been detected. The current request to connect to the
host has been rejected.
VTAM bind that has failed. The bind referred to by this
message is an S__-to-S__ bind. Retry the process. If • A compressed buffer has been received on the
the failure continues, contact Software Support. port designated as the PIO port. PIO does not
support compressed buffers. The connection has
AVZ4110S INVALID MODE DETECTED - LU been closed.
luname ROUTINE routine
User response
Explanation
Depending on the message, either contact the person
The LU 6.2 processing routine detected an invalid responsible for administering the product server to
mode string. The mode string cannot be used for explore the possibility of raising the current maximum
further processing. user count or the product has detected that the
current virtual storage utilization is too high to
User response allow additional connections. Change to use the
standard ODBC port, or change the connection to send
Report the error to Software Support. The complete uncompressed buffers.
message will be needed to diagnose the problem. One
or more connection attempts may fail and have to be AVZ4114T Dynamic SQL is not allowed by this
retried. instance of the server
AVZ4111S INVALID LU NAME DETECTED -

ROUTINE routine Explanation
This instance of the product server is to be used for
static-only Db2 applications. The dynamic SQL request
has been rejected.
User response reduced, or (3) the load must be spread across
multiple copies of the product.
Contact the person responsible for administering the
product Server for the product Server(s) available that AVZ4119T REXX VARIABLE ERROR rcode1-
support dynamic SQL. fbcode rcode2 DURING FETCH OF
varname FOR SEF rule procedure
AVZ4115S SECONDARY USERID COUNT
(count) EXCEEDS MAXIMUM (max)
Explanation
Explanation The product REXX processor encountered a failure
during termination processing for a product REXX
The actual number of secondary userids for the exec. A REXX variable value could not be fetched
current task exceeds the maximum number of and returned to the product's internal SEF routines
supported secondary userids. Because of this during the termination process. Because a truncated
problem, the secondary userid list can not be utilized or missing value may cause critical errors within the
and the current session will be terminated. rule processing facility, the product generates an S0C3
User response: abend. The SOC3 abend forces termination of the
product REXX interpreter. It also stops the processing
AVZ4116T Access to DB2 is not activated. of the current SEF rule in which the procedure was
defined. NOTE: For SHVRET code X'01-(New/Dropped
Explanation Variable), the most likely cause of this error is an
EXIT from a subroutine of the main Product REXX
None. procedure. If the subroutine contains a PROCEDURE
{EXPOSE} statement, some or all of the server's built-
User response in variables are hidden during EXIT processing and are
not available for post-REXX-execution interrogation by
Contact Rocket Software Support. the rule facility. Ensure that the product REXX routine
AVZ4117T Connection mode is not activated. does not deliberately specify an EXIT from an internal
PROCEDURE. For other SHVRET error codes, the most
likely cause of the error is an internal server error.
Explanation
The message contains two return code values; rcode1
None. represents the SHVRET return code value as defined
in IRXSHVB control block for IRXEXCOM, and rcode2
User response represents the R15 return code from IRXEXCOM.
No action is required. fbcode represents a feedback code
AVZ4118T Insufficient virtual storage is

available to handle this session. User response
Session rejected Check the REXX exec procedure and trace log for other
messages which may indicate the precipitating cause
Explanation of the failure, and correct the problem(s). Contact
Software Support if this procedure fails to resolve the
A client application has attempted to connect to the problem.
host. Not enough virtual storage was available to
handle the session. The session was rejected and AVZ4120T REXX VARIABLE varname
terminated by the host. TRUNCATED FOR SEF RULE rule
- SIZE (size) LONGER THAN MAX
SIZE (maxsize)
User response
The server address space does not have enough Explanation
virtual storage to handle the number of connections
that are being directed to it. You can reduce The SEF rule processor encountered a failure during
the minimum storage requirements using product termination processing for a REXX procedure. The
parameters. However, this is not recommended. One termination time value assigned by REXX to a
of the following solutions is recommended: (1) the built-in server variable is larger than the defined
amount of virtual storage per connection must be maximum size allowed by the SEF facility. The
reduced, (2) the number of connections must be variable is truncated to the maximum allowable size.

Truncation, however, may cause additional, spin-off User response
error conditions to arise.
Determine what caused the abend. External interrupts
(like a job CANCEL) may cause the current rule to be
User response aborted. If an ABEND occurred in the product, contact
Check the REXX exec procedure to see if a value your local product systems programming group for
was assigned which exceeds the implementation assistance. If an abend happened within a job, treat
maximums for specific built-in variable. this error as an environmental error. Correct or ignore
the current error, as applicable to your environment.
AVZ4121W service OF desc FAILED, RC=rcode
AVZ4124W CANNOT language PROCEDURE
procname - %3 SECTIONS NOT
Explanation ENABLED
SEF message processing encountered a failure in a
product service routine. A particular instance of this Explanation
generic message may relate to a GETMAIN failure
that occurs while attempting to allocate a REXX work The SEF event processing routine detected that a TYP
space. In this case, the return code indicates the rule that is referenced by another even procedure has
return code from the storage management routine. been disabled. The event procedure cannot be run
because the TYP rule is currently disabled. Processing
of the procedure is bypassed.
User response
Check the message related to the failure, and attempt User response
to resolve the problem. In the case of a storage
allocation failure, check for related MVS and product Determine why the TYP rule is disabled, and re-enable
messages. Also, ensure that your installation has an it.
exit (e.g IEFUSI) that limits virtual storage allocation. AVZ4127E errtext FOR MESSAGE ID=msgID
If possible, correct the problem, and retry the
operation.
Explanation
AVZ4122W ABEND abcode AT modname+offset
IN LINE lineno OF rule SEF event processing found too many compound
symbols. The pattern match error is reported.
Processing for the current rule is terminated.
Explanation
SEF event processing detected an abend. The current User response
rule processing request is terminated.
Check the exceeded compound symbol value, and
adjust your rule code to it. Correct the above problem,
User response and restart.
Determine what caused the abend. External interrupts AVZ4128E RULE rule SET varname TO AN
(like a job CANCEL) may cause an abend. Determine INVALID cblk VALUE
if any product parameters limited the processing
of the current rule. Refer to the product Server
Administration Guide and the product Server Started Explanation
Task Parameters book. Contact your local product SEF event processing encountered an error in
administrator for assistance. conversion of a character to an integer. Further
AVZ4123W SEF PROCESSING OF ruletype processing is terminated.
searchID FOR jobname ABORTED cblk represents a control block field name

SEF event processing routine detected an abend. The Check the error text for the invalid input character data
current rule processing request is aborted. causing this error. Remove or modify the invalid data,
and restart.
AVZ4129E errtext FOR ruletype RULE rule
Explanation AVZ4134E rsrc sysserv FAILED, RC=rcode,
DETECTED AT addr
SEF event processing encountered too many internally
generated compound symbols (security related),
or the length of one of the internally generated Explanation
compound symbol names exceeds an internal product Some type of error occurred in a product service
limit. Further processing of this rule is terminated. routine. See the actual text of the message for an
explanation. The error was probably caused by a
User response failure in an operating system service requested by a
product service routine.
This is an internal product error condition. Report this
error condition to Software Support immediately.
User response
AVZ4130E Rule rule disabled for exceeding
firing limit of lim Check if any other error messages were generated
Explanation the problem, take whatever corrective action is
SEF event processing detected excessive firing of the appropriate. Otherwise, contact Software Support with
rule named in the message. As a result, the rule has this problem.
been disabled. AVZ4135E SEF rule processor entered by
csect for invalid event type -
User response typecode
If appropriate, increase the firing limit, and enable the
rule. Explanation
AVZ4131E Rule rule has exceeded the SEF The SEF rule processing facility was invoked with an
firing limit of lim invalid event type. This is probably an internal error.

SEF event processing detected excessive firing of the Check for other error messages that were generated
rule named in the message. The associated parameter, along with this error message. Capture a copy of the
SEFLIMITDISABLE, indicates that the rule is not to be trace records, showing the TCB address, surrounding
disabled. the time of this error, and contact Software Support.
AVZ4136E ABEND DURING cblk CONTROL
User response BLOCK LOCATE - SEF RULE
EXECUTION BYPASSED
This message is informational. No response is
required. You may wish to code a message rule that
conditionally disables the rule. Explanation
AVZ4132I User program modname not found An internal control block could not be located prior to
in library SEF event execution scheduling.

While enabling a rule specifying execution of a user Check if any other error messages were generated
load module, the system was unable to preload along with the error message above. If the
the indicated module. Enablement of the rule is combined error messages are sufficient to explain
suppressed. the problem, take whatever corrective action is
this problem.
User response
AVZ4137T ENTERPRISE AUDITING GENERIC
Verify that the module named in the rule actually
USERID userID NOT DEFINED
exists within the user program load library or within
TO HOST SECURITY SYSTEM OR
STEPLIB.
REJECTED.

Explanation for processing. The client is operating using Diffie-
Hellman key exchange and DES to encrypt the logon
Enterprise Auditing was activated on the connection authentication information.
and the client attempted to send the specified generic
user ID for authorization checking. However, the user
ID was not defined to the Host security system (ACF2, User response
RACF or Top Secret) or was invalid for some other The host rejects the logon request by the client. The
reason. host traces MSG4146T with additional information
about the decryption failure.
User response AVZ4141T LOGON credentials rejected for
The session is not permitted to proceed. The client VCF reconnect, new key exchange
must supply a valid host user ID. Contact the required
Installation Security Administrator to define or repair
the user ID. Explanation
AVZ4138T ENCRYPTION METHOD CANNOT This message is transmitted to the client when Diffie-
BE NEGOTIATED, HOST STORAGE Hellman logon credential encryption is in use for a re-
UNAVAILABLE, BIND REJECTED connecting VCF session, and the VCF security artifact
for the VCF session has expired or been invalidated.
Explanation
This message is sent to client's when the requested User response
key exchange and encryption method cannot be The host rejects the logon request by the client. The
successfully negotiated at the host due to lack of host VCF client is obliged to repeat the full Diffie-hellman
storage. key exchange, and re-transmit encrypted logon
credentials. MSG4145T is traced to provide additional
User response information about the problem encountered.
The host rejects the encryption method requested by AVZ4142T ENCRYPTION METHOD CANNOT
the client. The client may continue without encryption BE NEGOTIATED, DIFFIE-
or may terminate the session. HELLMAN MODULE NOT LOADED,
BIND REJECTED
AVZ4139T BIND ENCRYPTION METHOD
REJECTED - method additinfo
Explanation
Explanation This message is sent to client's when the requested
key exchange and encryption method cannot be
This message is traced when a client's requested successfully negotiated at the host due to absence
key exchange and encryption method cannot be of the Diffie-Hellman key exchange and decryption
successfully negotiated at the host during bind routines.
processing.
User response
User response
The host rejects the encryption method requested by
The host rejects the encryption method requested by the client. The client may continue without encryption
the client. The client may continue without encryption or may terminate the session.
or may terminate the session. MSG4138T, MSG4142T,
MSG4143T, or MSG4144T are sent to the client. AVZ4143T ENCRYPTION METHOD CANNOT
BE NEGOTIATED, DIFFIE-
AVZ4140T LOGON credentials cannot be HELLMAN KEY EXCHANGE FAILED,
decrypted BIND REJECTED
This message is sent to the client when logon This message is sent to client's when the requested
credentials cannot be decrypted. The client logon key exchange and encryption method cannot be
is rejected because the userid, password, and new successfully negotiated at the host due to failure of
password fields cannot be converted to clear text
the Diffie-Hellman key exchange routine to calculate a AVZ4148T MISSING OR INVALID
valid shared secret. PARAMETERS IN SQL CALL RULE
rsname.rulename ,failrsn
User response
The host rejects the encryption method requested by
Explanation
the client. The client may continue without encryption This message is traced when an SQL CALL RULE
or may terminate the session. cannot be processed due because not all the
parameters were supplied or the parameters were too
AVZ4144T ENCRYPTION METHOD CANNOT
long to fit in the new buffer.
BE NEGOTIATED, UNKNOWN
ENCRYPTION METHOD
REQUESTED, BIND REJECTED User response
The updates to the SQL CALL statement are discarded.
Explanation Correct the SQL CALL rule based on the reason given.
This message is sent to client's when the requested AVZ4149T Connection from ipaddr TCP/IP,
key exchange and encryption method cannot be host name host, is using
successfully negotiated at the host. The requested unsupported driver version version
encryption method is unknown to the host.
Explanation
User response
A remote client connection is using a version of the
The host rejects the encryption method requested by product driver that is not supported by the server. This
the client. The client may continue without encryption is an informational message. Transaction processing
or may terminate the session. continues.
AVZ4145T LOGON CREDENTIALS REJECTED
FOR VCID VCID, NEW KEY User response
EXCHANGE REQUIRED, failrsn
You should upgrade the application driver to a level
that is supported by the server.
Explanation
AVZ4150T desc addr size PLAN pln %SK
This message is traced when when client Diffie-
Hellman logon credential encryption is in use for a re-
Explanation
connecting VCF session, and the VCF security artifact
for the session. has expired or been invalidated. This is a trace message that is produced whenever the
TRACECURSOR parameter has been set to YES. This
User response message provides information related to the product's
SQL plist and status area.
The host rejects the logon request by the client.
The VCF client is obliged to re-inaugurate Diffie-
User response
hellman key exchange and re-transmit encrypted
logon credentials. MSG4141T is sent to the client. No action required.
AVZ4146T LOGON CREDENTIALS CANNOT BE The variable fields of the message text are: desc
DECRYPTED - failrsn control block description addr address of the control
block size size of the control block in hex pln the plan
name stack stack trace information
Explanation
This message is traced when a client's logon AVZ4151T desc addr1 size DBRM dbrm
credentials cannot be decrypted. The client logon CURSOR num1 DATA addr2 cnt
is reject because the userid, password, and new QUERY length num2 TYPE stmt
password fields cannot be rendered in clear text form. FLAGS tf %SK

This is a trace message that is produced whenever the
The host rejects the logon request by the client.
TRACECURSOR parameter has been set to YES. This
MSG4140T is sent to the client.
message is used to trace the product's cursor control

blocks. There may be multiple cursor control blocks Explanation
for each product SQL plist.
This is a trace message that is produced whenever
the TRACECURSOR parameter has been set to YES.
User response This message is used to trace the release of a product
No action required. cursor control blok.
The variable fields of the message text are: desc

control block description addr1 address of the control User response
block size size of the control block in hex dbrm the No action required.
DBRM name num1 SQL section number addr2 first
data block address cnt number of chained data blocks The variable fields of the message text are: desc
length total data row length num2 number of query control block description addr1 address of the control
columns stmt last prepared statement type tf trace block size size of the control block in hex dbrm the
flags stack stack trace information DBRM name num1 SQL section number addr2 first
data block address cnt number of chained data blocks
AVZ4152T desc addr size value1 value2 %SK length total data row length num2 number of query
columns stmt last prepared statement type tf trace
Explanation flags stack stack trace information
This is a trace message that is produced whenever the AVZ4177T SQL tracing for RPC transactions is
TRACECURSOR parameter has been set to YES. This not available
message is used to trace the product's data blocks.
There may be multiple data blocks for each product Explanation
cursor block.
SQL tracing for RPC transactions can not be performed
because the Db2 DSNACAB module could not be
User response validated.
No action required.
The variable fields of the message text are: desc User response
control block description addr address of the control The product sets the TRACERPCSQL and
block size size of the control block in hex value1 next TRACESQLERRORS parameters to 'NO'. Contact
offset value (hex) value2 last offset value (hex) stack Software Support.
stack trace information
AVZ4178W SQL tracing for RPC transactions is
AVZ4153T desc data length1 length2 col %SK not available
This is a trace message that is produced whenever SQL tracing for RPC transactions can not be performed
the TRACECURSOR parameter has been set to YES. because the Db2 DSNACAB module could not be
This message is used to trace the columns of the validated.
SQLDA. There may be multiple columns described by
the SQLDA.
User response
User response The product sets the TRACERPCSQL and
TRACESQLERRORS parameters to 'NO'. Contact
No action required. Software Support.
The variable fields of the message text are: desc AVZ4179W count New RPC tasks timed
control block description data type of data for the out before redispatch by RPC
column (integer) length1 length of the data in the concurrent execution facilty
column (hex) length2 length of the column name
(integer) col column name (up to 30 characters) stack
stack trace information Explanation
AVZ4154T desc addr1 size DBRM dbrm This message is issued when a change is noted in the
CURSOR num1 DATA addr2 cnt number (count) of suspended RPC tasks that timed out
QUERY length num2 TYPE stmt before they were re-dispatched by the RPC concurrent
FLAGS tf %SK execution facility. Tasks suspended while awaiting
their turn to execute an RPC program will re-awake Explanation
if not re-dispatched within the time period set by
the RPCSLEEPINTERVAL parameter. Tasks which re- This message is produced once every 60 seconds
awake due to a timeout may execute the RPC program, when the currently executing number of rpc's is equal
regardless the RPCMAX limit, or may bypass execution to or greater than 80 percent of the max allowable
by generating a -438 error return code. The action specified by RPCMAX parameter. The first value is the
taken is governed by the RPCSTALLACTION parameter. max number observed during the life of the server. The
second value is the observed value at the time of the
message.
User response
No action is normally required and some sites may User response
receive these notifications with regular frequency;
other sites may rarely or never receive these None. This message is for informational purposes only.
notifications. If you note an increase in the number The variable fields of the message text are: value
of time out failures, check the active tasks display current percentage of max setting / value current max
to verify that RPC programs are completing. This setting / value number concurrently executing
message could indicate that one or more in-flight RPC
programs are stalled preventing new RPC program AVZ4183I Max concurrent RPC execution
executions from being dispatched. Adjust the RPCMAX less than value percent of max
and/or RPCSLEEPINTERVAL parameter, as necessary, setting value, value
to prevent timeouts.
AVZ4180S Invalid buffer received from a Explanation
client system This message is produced when the number of
concurrently executing RPC's drops below the
Explanation percent threshold and message 4182 was previously
issued reporting that RPC executions exceeded this
This message is issued if an invalid communication threshold. The percentage of RPCMAX at which
buffer is received from a client system. The buffer reporting occurs is set by RPCMAXMSGPCENT.
should have contained a request for additional RPC
data. However, it did not contain such a request.
User response
The session fails. Retry the session. If the problem The variable fields of the message text are: value
persists, check to see if there are other messages that current max setting value number concurrently
may indicate another problem. If there are no other executing value percent of RPCMAX to report
messages, contact Software Support. (RPCMAXMSGPCENT)
AVZ4181S RPC DATA WILL NOT FIT INTO AVZ4184T ABEND CC=ccode RS=rsncode
BUFFER DETECTED AT modname+offset
BY RPC CONCURRENCY ROUTINE
routine recovery additinfo
Explanation
This message is issued if an RPC data item of some Explanation
kind will not fit into the communication buffer. This
error should never occur. An ABEND was intercepted while one of the
Concurrent RPC execution routines was in control.
Information about the ABEND is logged in this
User response message.
The session fails. Retry the session. If the problem
persists, check to see if there are other messages that User response
may indicate another problem. If there are no other
messages, contact Software Support. The RPC concurrency routines may produce additional
trace messages and/or produce an SDUMP in response
AVZ4182I percent percent of max concurrent to the ABEND. They will recover and continue, if
RPC threshold achieved, value, possible. The message may give an indication of
value the recovery action (recovery) to be taken or other
information identifying the cause of the ABEND.

AVZ4185H RPC CONCURRENCY FACILITY AVZ4188T RPCMAX TRACE SMTE CONTAINS
SDUMP REQUEST RC=rcode, INVALID TYPE code - ASSUMING
ASSOC TRACE MSGNO=msgno, ERROR/FFDC FOR CAPTURE
STATUS AREA=addr
Explanation
Explanation
The RPCMAX trace routine has been called with a trace
This message is produced after an SDUMP request is SMTE element containing an invalid code.
issued by the concurrent RPC suspend/resume facility.
code is a hex value
A critical event was traced which has the SDUMP-
requested attribute set causing the SDUMP request to
be made. User response
The code is assumed to be for a recoverable or
User response imminent error so that the SMTE is recorded as first-
failure-data capture. This is probably due to a logic
None. The message reports the return code received
error. Contact Software Support.
from the SDUMP routine. A zero return code indicates
the SDUMP was processed or scheduled. A return code AVZ4189H WARNING: count ADDITIONAL
of decimal 300 (hex X'0000012c') indicates routines type EVENTS DETECTED BY RPC
were not authorized to request the SDUMP. A return CONCURRENCY ROUTINES
codes of decimal 304 (hex x'00000130') indicates
that the MAXSDUMPRATE flow rate limit in the server
Explanation
suppressed the SDUMP because the frequency of
SDUMP requests exceeded the maximum of 5 per The RPCMAX routines have traced one or more (count)
second. Non-zero return codes from SDUMP contain detected ERROR or ABEND events which have left
the SDUMP return code in the low-order 2-bytes of the some resource only partially recovered, indicate an
fullword and for return code 8, a reason code in the imminent failure of the RPC concurrency controls, or
high-order 2-bytes of the fullword. where not detected prior to an ABEND occurrence.
The RPC Concurrent execution limit facility may
AVZ4186I Max concurrent RPC allowed
become impaired, or now is, inoperable. The system
(RPCMAX) value exceeded.
issues this console message when an ABEND is
Suspending execution of RPC.
intercepted in the RPC routines, when heuristic
checks indicate that an IMMINENT-FAILURE of the
Explanation facility is likely occurring, or when an anomaly is
detected for which only a PARTIAL-RECOVERY of
This message is produced when the number of RPCs
resources can be predicted. Events of this type
started exceeds the max concurrent RPCs allowed
are always traced unless RPCMAXTRACE has been
value specified by the RPCMAX parameter. The RPC is
set to NONE. This console message is issued, no
added to the RPC execution suspend table and placed
more frequently than once per minute, as an alert
into a wait state. When the number of concurrently
that the facility may be slowly degrading, rapidly
executing RPCs drops below the max allowed, the
failing, or has already become inoperable. ABEND-
oldest RPC in the suspend table is resumed.
INTERCEPT messages, unless very infrequent, likely
are due to logic errors within the facility; although
User response these may occur infrequently if client transaction
threads are killed manually or terminate abnormally
for reasons unrelated to RPC program processing.
AVZ4187I Max concurrent RPC allowed FAILURE-IMMINENT messages, normally are issued
(RPCMAX) value within parameter just before the facility becomes inoperable in order
setting. Execution resumes. to log information which may be useful is diagnosing
problems. PARTIAL-RECOVERY events MAY indicate
future facility failure if too many resources cannot be
Explanation
eventually recovered. However, the system is unable
This message is produced when a suspended RPC is to predictively determine, nor later confirm, whether
resumed. resources being bypassed NOW will eventually be
recovered, or will remain inoperable permanently. A
User response few, intermittent PARTIAL-RECOVERY messages with
low event counts CAN represent a more or less
normal operating condition for some system work User response
loads. RPC termination, End-Of-Task, or cancelled-
task cleanup may be lagging a bit behind mainline Check the text of the message to determine the
RPCMAX limit processing, rendering certain predictive cause of the logon failure. You may need additional
health checks unable to confirm that in-flight recovery authorization.
actions will be able to complete successfully. However, AVZ4192T service - error - errdesc
a large count of PARTIAL-RECOVERY events, issued
frequently, probably indicates that resources are not
being recovered in all cases. These event traces can be Explanation
used to determine the originating cause of a downward An error occurred while processing an ODBC request.
spiral in many cases.
type may be ABEND, FAILURE, or PARTIAL-RECOVERY User response
This error message is a generalized message to
User response identify user interface errors.
If these messages appear frequently, or for any The variable fields of the message text are: service1
message reporting FAILURE-IMMINENT events, check ODBC service being called (IMSTM, CICSEXCI)
the state of the concurrent RPC execution facility, service2 element/operation in error desc error
along with Trace Browse activity. The trace may description
indicate the cause of a building problem early enough
that it can be corrected prior to facility failure. If the AVZ4193T Access to DB2 LUW is not
facility has become or is rapidly becoming inoperable, activated.
set the RPCMAX parameter to zero, which will turn
off most processing within the facility for new RPC Explanation
execution requests. If the cause of degradation or
failure cannot be corrected contact Software Support. None.
For certain types of events, the system will generate
an SDUMP of the product address space. SDUMPs are User response
generated no more frequently than once per minute.
Retain and forward the dumps to Software Support if Contact Rocket Software Support.
the immediate cause of a problem cannot be resolved AVZ4200I host: cmd
directly.
AVZ4190E BIND WITH rtype rhost FAILED - Explanation
NO MATCHING errdesc
This message is issued as a result of a host
command being sent to the product REXX MESSAGE
Explanation environment.
This message is produced when the local system is
unable to negotiate a bind with the remote system. User response
Note that this is not a VTAM bind. It is an AVZspecific
bind. This message is informational. No response required.
The variable fields of the message text are: host
User response host environment name string (message) cmd host
command insert
The session fails. Retry the session. If the problem
persists, check to see if there are other messages that AVZ4201E BIND WITH msgtext %2 FAILED -
may indicate another problem. If there are no other NO MATCHING %3
messages, contact Software Support.
AVZ4191E msgtext Explanation
This message indicates a logon failure. The text of the
Explanation message is produced by the security package (RACF,
ACF2).
This message indicates a logon failure. The text of the
message is produced by the security package (RACF,
ACF2).

User response AVZ4260E Client processing disabled
Check the text of the message to determine the
cause of the logon failure. You may need additional Explanation
authorization. An error occurred during initialization of ACI
AVZ4233I Error sending message to external support for client program processing. Client program
data queue processing is disabled.

An error has occurred while attempting to send an Contact Software Support.
informational record to the external data queue. This AVZ4261E ACI FUNCTION func FAILED,
may be caused by a full external data queue. RC=rcode errdesc

Contact your local product systems programming An error occurred processing a client ACI session.
group for help.
AVZ4240I Load balancing resumed for %1 User response
The session will be terminated.
Explanation
AVZ4262E Server client is not activated on
This message is issued when it is detected that the server sysserv.
load balancing queue is no longer full and is once again
eligible to receive sessions from a Group Director.
Explanation
User response None.

User response
AVZ4250E msgtext
Explanation AVZ4263I Client processing is enabled.

This message is used to write out error messages
received from remote systems. Explanation
Client processing is enabled. Client initialization
User response completed successfully and the client is ready to
accept new connections.
Check the text of the message to determine the cause
of the problem.
User response
AVZ4251E INVALID ADDRESS addr PASSED
BY PROGRAM progname No action is required.
AVZ4265W Data Server Client buffer
Explanation expansion disabled due to
auxiliary storage event
This message is issued if an invalid address is detected
in the routine that copies data from a user program Explanation:
into the buffer that is sent to the remote system. The An auxiliary storage event has been signaled, where
data at the specified address could not be accessed. event is one of: warning, shortage, or critical
shortage. DS Client immediately stops expanding
shared memory object buffers.
User response
User response:
The program passing the invalid address to the Investigate the reason for the auxiliary storage
product may fail or give incorrect results. Check the shortage. Use the PAGEADD command to add auxiliary
Db2 application program, and fix it if possible. storage.
AVZ4266I Data Server Client services AVZ4272H vendor TCP/IP component FOR
resumed. SUBSYSTEM subsys status
Explanation:
An auxiliary storage event has expired or has been Explanation
relieved. DS Client will resume full services.
This message is used to indicate incomplete
User response: INTERLINK TCP/IP initialization.
AVZ4267W Data Server Client refusing new User response
requests due to auxiliary storage No action is required. When TCP/IP completes
event initialization, AVZ will complete its own TCP/IP-related
Explanation: initialization.
An auxiliary storage event has been signaled, where
AVZ4273H protvend protcomp support is
event is one of: warning, shortage, or critical shortage.
being activated
DS Client immediately stops accepting new requests.
User response: Explanation
Investigate the reason for the auxiliary storage
shortage. Use the PAGEADD command to add auxiliary This message is issued by each of the four
storage. available communication protocol tasks when the
corresponding protocol support is being activated.
AVZ4270H %1 SUBSYSTEM NAME NOT SET
Other messages are issued if support for a particular
- %1 TCP/IP SUPPORT NOT
protocol is not being made active during start-up.
ACTIVATED
User response
Explanation
The name of the OEM vendor TCP/IP subsystem has
not been set. TCP/IP processing using this copy of the AVZ4274S Non-load balancing TCP/IP port
product is not possible using the OEM vendor's TCP/IP matches normal port or SSL port,
stack. server terminating.

The TCP/IP task of the main address space shuts A non-load balanced TCP/IP port has been specified.
down. This is not an error unless you actually did However the port number is the same as the standard
specify the TCP/IP subsystem name in the xxxxIN00 TCP/IP Port or the SSL Port.
exec. Note that other communication protocols (such
as OE SOCKETS TCP/IP) may be used even when the User response
OEM Vendor TCP/IP interface is not in use.
Change the port numbers so they do not match
AVZ4271S SSL and non-SSL ports match - and restart the product. The product parameter for
TCP/IP terminated setting the SSL port is OESSLPORTNUMBER. The
product parameter for the non- load balanced port
Explanation is OENLPORTNUMBER. The product parameter for
setting the non-SSL port number is OEPORTNUMBER.
SSL processing has been requested. However, the SSL
port number is the same as the non-SSL port number. AVZ4275I parmname reached -- at least one
Interlink TCP/IP was terminated. process waiting

Change either the SSL port number or the NON- This message is issued when a target thread limit was
SSL port number, and restart the product. The reached in the prior checking interval. This means that
product parameter for setting the SSL port number some number of requests will have their processing
is ITCSSLPORTNUMBER. The product parameter for delayed until a subtask is freed by the completion
setting the non-SSL port number is ITCPORTNUMBER. of another request. This is not a serious error if it
happens infrequently. If response time complaints

occur accompanied by these messages, the limit Explanation
should be raised.
This message is issued when a change is noted in the
number (no) of new process blocks that have been
User response dynamically allocated. The message also displays the
Raise the value of the indicated parameter. total number (total) of cross memory process blocks in
the pool.
AVZ4276S no new process block dynamic
allocation failures due to unknown
reasons.
User response
If the process block pool initialization count is set too
Explanation low, there may be a few of these messages during
the early portion of execution or during the first peak
This message is issued when a change is noted in period of operation. This should be considered normal
the number (no) of process block dynamic allocation operation. If these messages persist and the size of
failures. These failures will be noted when process the process block pool continually rises, it is possible
block dynamic allocation fails for reasons other than that process blocks are not being freed and placed
storage constraints. This is a serious error. back into the pool as they should. In this case, contact
Software Support for further analysis.
User response AVZ4279I no new RESMGR E-O-T cleanup
The bypass is to pre-allocate a sufficient number of failures or stalls detected and
process blocks during product initialization via the corrected
PROCESS parameter. This number can be determined
via the product ISPF panel (AVZ Stats) C.4 and the Explanation
"High water count" value in the "PC routines process
blocks" section. Add 2 or 3 to this number, and This message is issued when a change is noted
use it as the initial PROCESS parameter value. For a in the number (no) of MVS Resource Manager end-
permanent solution, contact IBM Software Support. of-task failures or stalls that have been detected
and automatically corrected by the subsystem end-of-
AVZ4277S no new process block dynamic task SSI intercept. Missing RESMGR EOT notifications
allocation failures due to storage normally occur only for connected TSO userids that (1)
restraints. are cancelled with S622 abends (because the RESMGR
EOT intercept is not scheduled by MVS) or (2) do
Explanation not exit/reenter a dialog (such as the trace display)
between restarts of the main product address space.
This message is issued when a change is noted in Undetected EOT events may indicate a more serious
the number (no) of process block dynamic allocation problem when they occur for subtasks executing
failures. These failures will be noted when process within the main product address space.
block dynamic allocation is unable to obtain either
private storage within the product address space or
common storage within the extended common storage User response
area (ECSA). This is a serious error. No action is normally required. Some sites may receive
these notifications with regular frequency; other sites
User response may rarely or never receive these notifications. If
you note an increase in the number of RESMGR
The bypass is to pre-allocate a sufficient number of EOT failures, check the trace to locate DET events
process blocks during product initialization via the (TRACEDETACHEVENTS must be YES). Those entries
PROCESS parameter. This number can be determined which contain the text EOT or EOM are of interest.
via the product ISPF panel (AVZ Stats) C.4 and the Display the jobname and userid columns. If the failing
"High water count" value in the "PC routines process DET events are not being recorded for TSO user
blocks" section. Add 2 or 3 to this number, and address spaces, contact Software Support for further
use it as the initial PROCESS parameter value. For a analysis.
permanent solution, contact IBM Software Support.
AVZ4280T limtype TIME LIMIT EXCEEDED
AVZ4278I no new process blocks allocated. FOR userid FROM nodetype NODE
Total process block count: total node PLAN plan CNID connid TP
progname
Explanation AVZ4284S Process block pool is empty, size is
poolsize
This message is issued when a task has exceeded a
warning limit of some kind. The limit (limtype) may
have been either a CPU time limit or a wait time limit. Explanation
This message is issued when the process block pool
User response is found to be empty. This can happen if all of the
process blocks are in use or if process blocks are being
No action is required. However, an automated lost (allocated and not freed).
response to this message may be needed.
AVZ4281T limtype TIME LIMIT EXCEEDED User response
FOR userid FROM nodetype NODE
node PLAN plan CNID connid TP This is a very serious error. Terminate the main
progname product address space as soon as possible, and raise
the number of process blocks using the PROCESS
product parameter in the product initialization exec.
Explanation The number of process blocks must be at least as
This message is issued when a task has exceeded an large as the number of IMS/DRA threads plus 5. If
error limit of some kind. The limit (limtype) may have the error persists, contact Software Support for further
been either a CPU time limit or a wait time limit. assistance.
AVZ4285S no process block allocation
User response failures have been detected
No action is required. However, an automated
response to this message may be needed. Explanation
AVZ4282T limtype TIME LIMIT EXCEEDED This message is issued when a number (no) of process
FOR userid FROM nodetype NODE block allocation failures are detected. This can happen
node PLAN plan CNID connid TP if all of the process blocks are in use or if process
progname blocks are being lost (allocated and not freed).

This message is issued when a task has exceeded a This is a very serious error. Terminate the main
failure limit of some kind. The limit (limtype) may have product address space as soon as possible, and raise
been either a CPU time limit or a wait time limit. The the number of process blocks using the PROCESS
task is terminated with an abend. product parameter in the product initialization exec.
The MINIMUM number of process blocks needed is the
number of IMS/DRA threads, plus 5. Note that this is
User response the minimum number required, and it does NOT take
No action is required. However, an automated into account various volume-based request handling.
response to this message may be needed. If the error persists after increasing the PROCESS
parameter value, or if process block release errors
AVZ4283T SMAF update failed for TCB addr1 are also being reported by the subsystem, contact
CMTC entry addr2 SMAF addr3 Software Support for further assistance.
AVZ4286S OPMS UPDATE FAILED FOR A
Explanation LOGGING EXCEPTION LIMIT
This message is issued when an attempt to update
product limits in a SMAF block has failed for some Explanation
reason. The update will not be performed. This error
will normally only occur if the target task terminated This message is issued when an attempt to update
while an attempt to update the SMAF was underway. product limits in the OPMS block failed for some
reason. The update will not be performed. This error
will normally occur only if a serious internal error has
User response occurred. This error could occur if the product was
No action is required. attempting to update a limit value at the same time the
ISPF interface was also being used to update a limit
value.

This is a very serious error. If the error persists, If this message was preceded by message 4285S,
contact Software Support for further assistance. terminate the main product as soon as possible, and
raise the number of process blocks using the PROCESS
AVZ4287S no PENDING LOGGING REQUESTS
product parameter, as described for message 4285S.
FOUND FOR DATABASE subsys
If message 4285S does not precede this message or
the problem persists, contact Software Support for
Explanation further assistance.
The number (no) of pending logging requests has AVZ4290E wstype GLOBAL VARIABLE
exceeded the product limit value. This message is WORKSPACE IS percent FULL
issued to notify the operators of the system or an (count OF total BLOCKS USED).
automated operations product that the limit has been PROGRAM=progname.
exceeded.
Explanation
User response
The global (or temporary global) variable workspace,
This is a serious error. The reason for the accumulation which contains global variables, has met or exceeded
of pending requests must be determined and fixed. the warning threshold of blocks in use as defined by
Some of the possible reasons include the Db2 the GLOBALWARNTHRESH (or GLOBALTEMPWARNTH)
subsystem being down or errors accessing the Db2 product parameter. This message will also be issued
logging tables. every time a new high-water mark that is at least
5% higher than the previous high-water mark is met
AVZ4288S no pending logging requests
or exceeded. The frequency at which this message is
cleared for database subsys
issued is controlled by the GLOBALWARNINTVAL (or
GLOBALTEMPWARNIV) product parameter. Note that
Explanation the check that results in this message is only made
when a new global variable is allocated or an existing
All (no) of the pending logging requests for a database
global variable is expanded. The condition is recorded,
subsystem have been cleared and the associated
and the message will be issued on the next reference
storage has been released. This message is issued to
to a global variable. If no global variable references
notify the operators of the system or an automated
occur, you may not be warned of this condition until
operations product that the pending logging requests
the database is full.
have been released.

You may need to analyze the contents of the global (or
This is a serious error. The reason for the accumulation
temporary global) variable database using the Global
of pending requests must be determined and fixed.
Variables application, and delete unused symbols. If
Some of the possible reasons include the Db2
the global variable data set is too small, allocate
subsystem being down or errors accessing the Db2
a larger global variable DIV data set, and copy the
logging tables.
old one over to it using the access method services
AVZ4289S no SS-PC ENTRY FAILURES REPRO command. Modify the product GLOBALMAX
DETECTED, LAST: rsn AT time (or GLOBALTEMPMAX) parameter to indicate the
larger maximum number of global variable blocks.
The program or rule.ruleset name in the message
Explanation
simply represents the program running at the time
One or more (no) new failures were encountered the condition was detected or at the time a deferred
during entry processing for the product's space-switch message was issued. This program may or may
or stacking PC routine. Each new failure represents a not have caused a significant portion of the global
transaction task or user interface request which could workspace to be used.
not be processed. Usually, these failures are due to the
AVZ4291T additinfo
inability of the product to obtain stack storage from its
pool of pre-allocated cross-memory process blocks,
and this message will be immediately preceded by Explanation
message 4285S.
This trace message is used for debugging purposes
only.
None. During an attempt to access global variable pool
storage, a failure in the lock or unlock serialization
AVZ4292E POSSIBLE wstype GLOBAL routine was encountered. The current global variable
VARIABLE WORKSPACE operation will be abandoned with a failure return
INTEGRITY PROBLEM DETECTED code. The return code field will contain a non-zero
(errtype - flag). REBUILD value in byte 3 if the SETLOCK or ENQ service failed.
SCHEDULED. It will contain a non-zero value in bytes 1 or 2 for
environmental errors.
Explanation
mode can be PROB or SUP.
An abend occurred while updating critical control
blocks in either the global or temporary global variable User response
workspace. The global variable workspace will be
rebuilt at the next checkpoint interval. Until the rebuild The current global variable pool operation is failed.
is complete, attempts to access or update global Check for other messages which might indicate the
variables may possibly fail. cause of the error, and contact Software Support for
further assistance.
The error (errtype) may be SYNC or DELAYED.
AVZ4298S GLOBAL VARIABLE lock/unlock
flag represents the integrity flag byte, in hexadecimal.
RECURSION ERROR DETECTED AT
addr
User response
In most cases, no problem has actually occurred. The Explanation
rebuild will simply validate and recover all of the data.
During an attempt to access global variable pool
If the 0180I messages associated with the rebuild
storage, a failure in the lock or unlock serialization
indicate any loss of data, perform the following: (1)
routine was encountered.
print any LOGREC software records created by the
product, (2) print the relevant sections of the Trace
Browse leading up to the issuance of this message, (3) User response
record the exact text of this message, and (4) contact
The current global variable pool operation is failed.
Software Support for further assistance.
Check for other messages which might indicate the
AVZ4296S GLV subtask has terminated. cause of the error, and contact Software Support.
Zeroing workspace pointers.
AVZ4300I SEF command rejected -
subsystem subsys is not active
Explanation
During an attempt to access a global variable, it was Explanation
detected that the global variable subtask had already
The current program or routine requires the services
terminated. The workspace pointers will be zeroed to
of the main product address space. However, the main
prevent any future attempts to access this data. All
product address space is not active.
future AVZVALUE or SWSVALUE requests will result in
REXX error 48 (failure in system service).
User response
User response Start or restart the main product address space
If the product does not shut itself down automatically, AVZ4301S service - desc FAILED, RC=rcode
attempt to shut it down manually using the MVS STOP
command. If the product still does not terminate,
Explanation
attempt to CANCEL it.
AVZ4297S lock/unlock OF GLOBAL wide variety of internal errors that occur as a result of
VARIABLE POOL FAILED: calling a product system management service.
HASN=asid1, PASN=asid2,
SASN=asid3, MODE=mode,
RC=rcode, CALLER=callername

Record of all the information in the message text, and The version of the product that you are using in your
contact Software Support. TSO environment is incompatible with the version of
the product running in the main Server address space
AVZ4302S ABEND abcode, RS=rsncode related to the subsystem to which the SEF command
IN 'ADDRESS hostenv' AT has been addressed.
modname+offset, PSW=psw
User response
Explanation
Ensure that the correct product load library is
An abend occurred while the current program or allocated to your TSO environment, or address the SEF
routine was using the services of the main product request to a copy of the product that is running the a
address space. The message provides a detailed compatible version.
explanation of what type of abend occurred and at
what location it occurred. AVZ4307E SUBSYS SEF command cannot be
issued in a rule
User response
Explanation
Check the full text of the error message, and
take whatever corrective action is appropriate. For The SUBSYS SEF command cannot be issued from
further assistance with this problem, contact Software within an SEF rule environment
Support.
AVZ4303E SEF command timed out before all User response
responses received. Force this section of code to run in a server using
OPSREQ.
Explanation
AVZ4308E errdesc, RC=rcode
The SEF command timed out after waiting for
a significant period of time without receiving the Explanation
complete response from the SEF.
Some type of service routine (operating system or
product specific) failed. The error message identifies
User response
the type of error.
Ensure that the product is still active. If the product
is still active, check the status of the SEF execute User response
queue using AVZ/SWS. If there is a backlog of SEF
requests, try to determine what caused the backlog, Check the full text of the error message, and attempt
and attempt to resolve the problem. If the problem to correct the error.
cannot be resolved, contact IBM Software Support.
AVZ4319T ABEND IN 'ADDRESS SWSSEND'
AVZ4304E SEF COMMAND errdesc: cmdname CODE=ccode, REASON=rsncode AT
addr
Explanation
Explanation
An invalid SEF verb or an invalid SEF command has
been detected by the ADDRESS SEF environment An abend occurred within the ADDRESS SWSSEND
syntax checker. host environment.

Correct the syntax of the SEF command. Check for other errors that might explain the condition.
AVZ4305E AVZ/SWS version ver1 is AVZ4320H subsysid SEF CMD
incompatible with version ver2 of FROM(jobname,userid): cmd
subsystem subsys.
This message logs the use of SEF host commands to A command passed to the ADDRESS TSO or ADDRESS
the hardcopy console. The FROM keyword contains the TSOSRV environment is invalid for the reason given.
job name and user ID used for authorization purposes. The system rejects the command, with RC=-3
indicating an invalid host command environment
User response command.
No action required. This message is for information

User response
tracking only.
Determine why the command was rejected, and
AVZ4321E CURRENT verb COMMAND NOT resubmit the command.
AUTHORIZED - errmsg
AVZ4338I TSO REMOTE EXECUTION
Explanation TIMEOUT VALUE SET TO time
Product REXX SEF command authorization check

Explanation
routine found that the current user is not authorized
to execute the SEF command. Access to the EXECUTE A GETTIMEOUT command was passed to the
command is denied. ADDRESS TSO interface. This message is returned on
the external data queue as a response.
User response
User response
Check the verb string of the error message text for
the command whose access is denied. Ensure that None. The timeout value is given in 100ths of seconds.
the current user has the required access. Contact
your security systems administrator for further help, AVZ4339T environment COMMAND TIMED
if necessary. OUT
AVZ4322S ABEND abcode IN Explanation

AUTHORIZATION ROUTINE
modname+offset An ADDRESS TSO or ADDRESS CGI host command did
not complete within the allowed time. The requesting
routine is redispatched.
Explanation
An abend occurred in the authorization checking User response
routine
Determine why the host command did not complete
within the required time frame. The delay could be due
User response
to looping within the TSO/CGI command procedure or
Contact the person at your installation who installs and heavy usage of the external TSO servers.
maintains your installation security product.
AVZ4340S Subsystem subsysid inactive, must
AVZ4336E msgtext be (re)started
An SEF command was invalid or has failed for the An ADDRESS TSO or ADDRESS TSOSRV host command
reason indicated in the message. has been directed to a product subsystem that is not
currently active.
User response
User response
Correct and re-submit the SEF command.
Start or restart the product subsystem whose
AVZ4337T THE TSO COMMAND IS INVALID subsystem ID appears in the message, or correct
DUE TO errdesc the program to specify the ID of an active product
subsystem.
AVZ4341S TSO/E is not installed

TSO/E (IBM's program product number 5665-293) is Check for other error messages that were generated
required to support the use of the product. with is error message. If the combined error messages
User response corrective action is appropriate. If the problem cannot
be resolved, contact Software Support.
Verify that this product is available at your installation.
AVZ4345S TSO service error - errdesc -
AVZ4342E TSO command length (length) reason code rsncode
exceeds maximum length
(maxlength)
Explanation
Explanation An error was detected in the parameter list passed
to the product service that calls the TSO command
The length of the TSO command exceeds the service routine.
implementation limits. Note that the length of TSO
host commands sent from SEF rules to the OSF
User response
execute queue have a lower limit (256 bytes or
the BLKSIZE on the server SYSTSIN DD statement, Check if any other error messages were generated
whichever is smaller). along with the error message above. If the combined
User response take whatever corrective action is appropriate. If
Check if there are an excessive number of blanks in the Support.
TSO command string. If so, remove the blanks from
the command string. If you need to pass long values AVZ4346E Current verbaddr command not
from a rule to a server REXX program, use global authorized - errmsg
variables to pass the values.
Explanation
AVZ4343S TSO service error - errdesc
The authorization check failed. The use of ADDRESS
Explanation OSF is restricted by your installation security product.
An error occurred in the product service routine

User response
that executes TSO commands via the TSO command
service routine. Contact the person at your installation who installs and
User response AVZ4347S ABEND abcode IN
Check if any other error messages were generated AUTHORIZATION ROUTINE
along with the error message above. If the combined modname+offset
take whatever corrective action is appropriate. If Explanation
Support. An abend occurred in the authorization checking
routine.
AVZ4344S TSO service error - abcode1
abcode2 - reason code rsncode User response
Contact the person at your installation who installs and
Explanation
An abend occurred in the product service routine
that executes TSO commands via the TSO command AVZ4348S rsrcname sysserv FAILED,
service routine. RC=rcode, DETECTED AT addr
Explanation
Some type of error occurred during invocation of a
product service routine associated with the ADDRESS
TSO or ADDRESS OSF environment. The error occurred Explanation
while attempting to set up the environment for
executing a TSO command via the TSO/E command This message is issued when the product DRA control
service routine. exit receives notification of a DRA failure but is passed
an unrecognized subfunction code.
User response
User response
along with the error message above. If the No action required. The product will attempt to restore
combined error messages are sufficient to explain a connection with the IMS control region. Note that
the problem, take whatever corrective action is this error message may be followed by other, more
appropriate. Otherwise, contact Software Support with descriptive error messages as the product attempts to
this problem. reconnect to the IMS DBCTL.
AVZ4349S MESSAGE SEND TO TSO EXECUTE AVZ4352I DRA control exit invalid PAPL
QUEUE FAILED, RC=rcode, function = funcd
DETECTED AT addr
Explanation
Explanation This message is issued when the product DRA control
The product has attempted to send a command to the exit receives an unrecognized function code.
TSO server execute queue in a product Server address
space, and the attempt has failed. If the return code User response
in the message is 4, then the TSO execute queue is
full. Any one or some combination of the following No action required. The product will attempt to restore
conditions may be true: (1) there is a rule or some a connection with the IMS control region. Note that
combination of rules that is looping, (2) there is a loop this error message may be followed by other, more
in an application that is causing TSO commands to be descriptive error messages as the product attempts to
issued very frequently, (3) there are too few servers reconnect to the IMS DBCTL.
or the servers may be tied up running relatively long AVZ4353I IMS CCTL support activated
processes, or (4) the TSO execute queue may be too
small for your server workload.
Explanation
User response This message is issued when the product DRA control
exit receives a notification that the connection to the
Review the contents of the message and any IMS control region has been established successfully.
associated messages, and attempt to resolve the
problem. If the problem cannot be resolved, contact
Software Support to obtain additional assistance. User response
AVZ4350I Load for module modname failed, No action required. This is an informational message
CCTL initialization error only.
AVZ4354I IMS CCTL support terminating
Explanation
This message is issued if a module needed to initialize Explanation
the CCTL interface to IMS could not be loaded. The This is an informational message that is issued when
message contains the module name. The module is the product terminates its IMS CCTL support. If the
either missing or some other error has occurred. IMS CCTL support is being terminated due to a
fatal error condition, this message will have been
User response preceded by error messages which depict the exact
error condition encountered.
Check if any other messages were issued. Check if the
named module is in the search sequence. Note that
this problem can be resolved without restarting the User response
main product address space. Follow the course of action recommended for the error
AVZ4351I DRA control exit invalid PAPL messages that preceded this error message. If the
subfunction = sfcd product CCTL support continues to terminate due to

a fatal error condition, contact Software Support for User response
further assistance.
Check Trace Browse for any related product messages.
AVZ4355I IMS CCTL control exit resync Check the MVS system log for any related IMS
failure messages. Correct any IMS problems discovered. The
product will continue to attempt to connect to the
Explanation IMS region until a successful connection has been
established.
The IMS CCTL control exit has been unable to
successfully process a resync request during product AVZ4359I PSB psb schedule request
initialization. unsuccessful

Check the MVS system log for any IMS messages The product was unable to successfully schedule the
occurring around the time of this failure. Correct any PSB specified by the client application.
IMS problems that may have occurred. Then ABORT
the in-doubt UORs for this server. If the problem User response
continues to persist, contact Software Support for
further assistance. Check the PSB name to ensure that it is correct. If
the problem continues to persist, contact Software
AVZ4356I IMS DRA terminating due to Support for further assistance.
unknown error condition
AVZ4360I Request failed - PSB not in
scheduled state
Explanation
The IMS Data Resource Adaptor running inside of the Explanation
main product address space has terminated due to
some unknown error condition. Product IMS support The current request requires that a prior PSB schedule
will be terminated. attempt had completed successfully, and no active
thread was found for this task.
User response
User response
Check the MVS system log for any IMS messages
occurring around the time of this failure. Correct any Check the program logic in the client-side application
IMS problems that may have occurred, and restart to ensure that the "CC" message was sent prior to
the AVZ address space. If the problem continues issuing DL/I requests or the "TERM" message. If
to persist, contact Software Support for further the problem continues to persist, contact Software
assistance. Support for further assistance.
AVZ4357I Invalid request, IMS CCTL feature AVZ4362I Invalid buffer function code funcd
not enabled
Explanation
Explanation The buffer function code passed to this routine was
None. invalid. The host transaction program could not handle
the buffer function code passed by the client.
User response
User response
Verify that the host application requested by the client
AVZ4358I Request failed product not matches the current call to the host. Contact Software
identified to IMS Support for further assistance, if necessary.
AVZ4363I Previous CCTL termination failed,
Explanation initialization will use previous
The product has made one or more attempts identify session PAPLCTOK value
itself to the IMS DBCTL region, but the attempts have
failed. There is currently no active connection between
the product address space and the IMS DBCTL region.
This is an informational message that is issued during This OE Sockets task of the main address space shuts
product initialization when the CCTL initialization down. Startup continues without Services support.
routine determines that the previous CCTL termination
AVZ4376W MongoDB support services TCP/IP
did not complete successfully.
port(s) conflict with other port
number assignments - Mongo
User response terminating
No action is required. This message is for informational
purposes only. Explanation
AVZ4370T Access to Services is not The port number(s) assigned for MongoDB server
activated. support conflicts with other non-zero port number
assignments for other product support services.
Explanation
User response
None.
The MongoDB listener task will terminate and Mongo
User response support will be deactivated.
Contact Rocket Software Support. AVZ4377W MongoDB listener ports not set
- MongoDB support willnot be
AVZ4371T Services is not active on the server activated
Services is not started on the server and cannot be The port numbers for MongoDB client connections
used by client applications. The current request to use have not been set. MongoDB support, requested by
client to execute a web service is rejected. The current the MongoDB start-up parameter cannot be activated.
host session will be terminated.
User response
User response
The MongoDB listener task shuts down, and start-up
If access to Services is needed, enable Services by continues without MongoDB support.
setting the correct parameters on the server.
AVZ4378W OE sockets HTTP port
AVZ4372H WEB SERVICE %1 UNDER (WSOEPORT) conflicts with main
VIRTUAL DIRECTORY %2 HAS OE port (OEPORTNUMBER) - HTTP
BEEN %3 listener terminating
A web service has been enabled or disabled. The port number for OE Sockets HTTP and Services
access is set to the same non-zero value as the normal
User response (ODBC) port. Services HTTP listener task will terminate
and HTTP access to this server will be unavailable.
No action is required. This message is for informational
purposes only.
User response
AVZ4375W OE sockets WSOEPORT conflict
This OE Sockets task of the main address space shuts
with PIO port - zervices HTTP
down. Startup continues without HTTP and Services
listener terminating
support.
Explanation AVZ4379W OE sockets HTTP port

(WSOEPORT) unset - HTTP &&
The port number for OE Sockets Services (WSOEPORT) Services support unavailable
has been set to the same non-zero value as the
parallel I/O port.

The port number for OE Sockets HTTP and Services Verify that the userid used to start the server has
access is un-set. Services Support, requested by an OMVS segment defined. If this does not resolve
WSACTIVE option, has been reset and will not be the problem, contact Software Support for additional
available. HTTP access to the server by the Studio will assistance.
also be unavailable.
AVZ4384S Services load balancing port not
unique, server terminating
User response
This OE Sockets task of the main address space shuts Explanation
down. Startup continues without HTTP and Services
support. A load balancing Services port has been specified.
However the port number is already used by another
AVZ4380E MongoDB feature is not configured listener such as the main TCP/IP listener, SSL, or
- Mongo listener on port portno will regular Services.
not be activated.
User response
Explanation
Change the port numbers so they do not match
None. and restart the product. The product parameter
for setting the SSL port is OESSLPORTNUMBER.
User response The product parameter for the non- load
balanced port is OENLPORTNUMBER. The product
Contact Rocket Software Support. parameter for setting the non-SSL port number
is OEPORTNUMBER. The product parameter for
AVZ4381H Parallel I/O port OPEN failure
setting the Services port number is WSOEPORT. The
product parameter for setting the Services SSL port
Explanation number is WSOESSLPORT The product parameter
for setting the Services balanced port number is
An error occurred when trying to open a socket for the
WSOEBALANCEDPORT
Parallel I/O port.
AVZ4385H WS load-balanced port OPEN
User response failure
Verify that the port number is correct.

Explanation
AVZ4382H Non load-balanced port OPEN
An error occurred when trying to open a socket for a
failure
ws load-balanced port.
Explanation
User response
An error occurred when trying to open a socket for a
non load-balanced port.
AVZ4386S SSL port number required -
User response OE sockets TCP/IP processing
terminated
AVZ4383H OE sockets TCP/IP DubProcess Explanation
failed. RC=rcode. Reason
SSL processing has been requested. However, the SSL
code=rsncode.
port number has not been set or has been set to zero.
OE Sockets was terminated.
Explanation
An error occurred when trying to set the DUBPROCESS User response
option for OE Sockets processing.
Set the SSL port number in the initialization exec,
and restart the product. If this does not resolve
the problem, contact Software Support for additional to use is not valid. Dynamic VIPA support will be
assistance. disabled.
AVZ4387S PIO and ODBC ports match - OE
sockets PIO port is reset to zero User response
Either delete the Dynamic VIPA IP address or properly
Explanation specify an IP address using dotted-decimal notation.
PIO processing has been requested. However, the PIO AVZ4391I OE stack binding port portno to IP
port number is the same as the ODBC port number. address ipaddr
The OEPIOPORTNUMBER is set to zero. Parallel I/O
support will be disabled. Explanation
The Open Edition support is binding the product to the
User response
indicated port and the indicated IP address.
Change the OEPIOPORTNUMBER to be different from
the OEPORTNUMBER value. User response
AVZ4388S SSL and non-SSL ports match - OE None. This is an informational message only.
sockets SSL port is reset to zero
AVZ4392I OE stack returning invalid results
when sockets are ready
Explanation
SSL processing has been requested. However, the Explanation
SSL port number is the same as the non-SSL port
number. The OESSLPORTNUMBER is set to zero. The This message is issued when the OE main task detects
non-SSL port number will accept both SSL and non- that select() returned a zero return value even though
SSL inbound requests. there were sockets ready in the returned socket mask.
This could lead to a loop occuring in OPMAOT trying to
process a listening socket.
User response
None required. To eliminate the message, remove the User response
OESSLPORTNUMBER parameter from the initialization
exec. Cyour sales representative for instructions on
gathering documentation for this problem in IBM Open
AVZ4389S OE stack oestack can not be used Edition code.
- OE sockets TCP/IP processing
terminated AVZ4393I OE stack returning too soon from
select when no sockets are ready
Explanation
Explanation
The name of a specific OE stack was specified using
the TCPNAME product parameter. However, this OE This message is issued when the OE main task detects
stack cannot be used for some reason. OE Sockets was that select() returned sooner than expected when a
terminated. timeout value was specified and there were no sockets
ready for processing. This could lead to wasted time in
OPMAOT when there is not work to do.
User response
Correct the name of the OE stack by modifying User response
the TCPNAME product parameter. Restart the main
product address space. Contact Software Support for instructions on gathering
documentation for this problem.
AVZ4390E Invalid dynamic VIPA IP address
%1 specified AVZ4400T msgtext
Dynamic VIPA support has been configured, however This is a general purpose message that may or may not
the IP address specified for Dynamic VIPA support indicate some type of TCP/IP error.

User response AVZ4413I no MESSAGES SINCE THE LAST
ARCHIVE. CURRENT MESSAGE
Read the message text carefully. Some messages NUMBER IS seqno
messages. If the message indicates an error, check
for any associated TCP/IP produced error messages. Explanation
If you are unable to diagnose the problem, contact The number (no) of messages added to Trace Browse
Software Support. since the last Trace Browse message archived has
AVZ4401W No TCP/IP port number specified. exceeded a user-defined threshold.

This message indicates that no port number was This message may be used as a trigger for starting the
specified for the product to LISTEN for, and ACCEPT Trace Browse archive program based on the number of
inbound OE Sockets TCP/IP sessions. messages since the last archive rather than on a time
basis using the TODARCH rule.
User response AVZ4420H msgtext
Change the xxxxIN00 EXEC to specify a port number
for the OEPORTNUMBER parameter which is used Explanation
to LISTEN for, and ACCEPT all inbound OE Sockets This is a general purpose message that may or may not
TCP/IP sessions. indicate some type of ITC/IP error.
AVZ4410E service OF desc FAILED RC=rcode,
DETECTED AT addr User response
Read the message text carefully. Some messages
Explanation produced under this message ID are actually error
This is a generic error message used to describe messages. If the message indicates an error, check for
a wide variety of message processing errors. The any associated ITC/IP produced error messages. If you
message text gives a description of the current are unable to diagnose the problem, contact Software
operation (service) and what the current operation was Support.
trying to do. AVZ4421H UNKNOWN service CODES - R0=r0
R15=r15
User response
Keep all the related error details, and contact Explanation
your local product systems programming group for This message reports ITC/IP return and reason codes
assistance with this problem. (R0 and R15) that are unknown to AVZ.
AVZ4411E GLOBAL VARIABLE RULE
CHAINING DEPTH EXCEEDS User response
MAXIMUM VALUE
possible that you are running a version of ITC/IP not
Explanation yet supported by AVZ. If the version of ITC/IP that
Global variable rule chaining has exceeded the you are running DOES appear to be supported, contact
maximum value. All pending global variable rules will Software Support.
not be fired. The current operation continues. AVZ4422H UNKNOWN service CODES -
ERCD=errcd DGCD=diagcd
User response
If this situation has been caused by a recursive infinite Explanation
global variable rule loop, modify the global variable This message appears in conjunction with the 4421H
rule to avoid this situation. If this situation is not message.
due to a REXX programming error, increase the global
variable rule chaining limit (GLVCHAINMAX).
This may indicate some type of internal error. It is also Probable CICS error. Check the system log for errors.
possible that you are running a version of ITC/IP not
AVZ4453S jobname error starting client exit
yet supported by AVZ. If the version of ITC/IP that
program progname - EIBRESP:
you are running DOES appear to be supported, contact
respcd
Software Support.
AVZ4423H UNKNOWN service CODES - Explanation
ERCD=errcd DGCD=diagcd
The client PLT program encountered an error starting
the user exit program.
Explanation
This message appears in conjunction with the 4421H User response
message.
Check that the exit program has been correctly defined
to CICS.
User response
This may indicate some type of internal error. It is also AVZ4454I jobname client exit program
possible that you are running a version of ITC/IP not progname started
yet supported by AVZ. If the version of ITC/IP that
you are running DOES appear to be supported, contact Explanation
Software Support.
The client task-related user exit program has been
AVZ4450S jobname error inquiring CICS started.
system information for client -
EIBRESP: respcd User response
Explanation
AVZ4455S jobname GWA length not as
The client PLTPI program encountered an error
expected for client exit program
inquiring CICS system information.
progname - explength: explength,
returned: GWA
User response
Probable CICS error. Check the system log for errors. Explanation
AVZ4451S jobname error enabling client exit The GWA length returned by CICS for the client TRUE
program progname - EIBRESP: is not the expected length.
respcd
User response
Explanation
Check that the exit program has been correctly defined
The client PLTPI program encountered an error to CICS.
enabling a client exit program.
AVZ4456I jobname program creation date:
date
User response
Check that the exit program has been correctly defined Explanation
to CICS.
This message provides the creation date of the client
AVZ4452S jobname error extracting GWA TRUE exit program.
address for client program
progname - EIBRESP: respcd User response
Explanation
AVZ4457S jobname Program load failed -
EIBRESP: respcd
extracting the Global Work Area address for the exit
program.

The client API interface routine could not be loaded. A user-written RPC program attempted to issue an
IMS PCB call in order to schedule the program's PSB.
User response However, the program's PSB is already scheduled.
Ensure that the load module is available to the CICS

User response
region.
Correct the internal logic error in the user-written RPC
AVZ4458W jobname client exit program program, and invoke the RPC program again.
progname is already enabled
AVZ4472S PSB SCHEDULE FAILURE - PSB
Explanation NAME = psbname

Explanation
enabling the client exit program. The program is
already enabled. A user-written RPC program attempted to schedule
the program's PSB. The PSB schedule attempt has
User response failed.
Check that the PLTPI program has been correctly

User response
defined to CICS.
The PSB schedule may have failed for a variety of
AVZ4459I jobname client exit program reasons. Ensure that the PSB load module is available
program is enabled to IMS. Ensure that the databases referenced by the
PSB are available. Ensure that the PSB has not been
Explanation stopped by IMS due to an earlier error. If none of the
above conditions caused the error, check the IMS MTO
The client PLTPI program is enabled.
log and the MVS MCS console for any related error
messages. If all attempts to schedule the PSB fail,
User response contact Software Support for further assistance.
This is an informational message. No action required. AVZ4473S INVALID DL/I CALL ATTEMPT -
PSB NOT SCHEDULED
AVZ4460I jobname Program GWA address:
addr
Explanation
Explanation A user-written RPC program attempted to issue an
IMS term call in order to terminate the program's
This message provides the address of the client TRUE
PSB. However, the program's PSB was not previously
exit's Global Work Area (GWA).
scheduled.
User response
User response
Correct the internal logic error in the user-written RPC
AVZ4470S IMS CCTL FEATURE MUST BE program, and invoke the RPC program again.
ENABLED TO ISSUE DL/I CALLS
AVZ4500U desc INITIAL GETMAIN FAILED -
INCREASE STORAGE SIZE
Explanation
None. Explanation
Insufficient storage. The product was unable to obtain
User response enough storage to allocate the initial program stack.
AVZ4471S INVALID PSB SCHEDULE ATTEMPT
- PSB ALREADY SCHEDULED
Check the abend code to determine if the region size Some type of error occurred in the system
should be increased. If necessary, increase the region management routines of the product. See the actual
size, and restart the product. text of the message for an explanation. The error was
probably caused by a failure in an operating system
AVZ4501U desc UNABLE TO LOCATE THE service requested by a product system management
MASTER BLOCK routine.

A subtask was unable to locate the product control Check if any other error messages were generated
blocks and was forced to terminate. The services along with the error message above. If the combined
provided by the subtask will not be available. error messages are sufficient to explain the problem,
User response Otherwise, contact Software Support for assistance
with this problem.
associated with this problem. There may be one or AVZ4505H ABEND abcode IN service
more abend error messages referring to the current modname+offset
problem. If possible, fix the problem identified by
Explanation
problem cannot be resolved, contact Software Support
with this problem. The subtask driver routine detected an abend in
the routine called by the driver. The message text
AVZ4502H process subtask is active provides the abend code, current operation (service),
and abend location. This failure may have been caused
Explanation by a programming error in the routine that caused
the subtask exit to get control or in the subtask
This is the standard subtask initialization message.
exit routine itself. This failure can also be caused by
product installation and maintenance errors.
User response
This is not an error message, and no action is required. User response
AVZ4503S ESTAE service ERROR RC=rcode Check if any other error messages were generated
Explanation take whatever corrective action is appropriate. If
The subtask driver attempted to create an ESTAE the problem cannot be resolved, contact Software
recovery environment. The ESTAE macro failed. Support.
service may be create or delete. AVZ4506H process subtask terminating

Check the error messages and the return code This is the standard message indicating that subtask
associated with this problem. There may be one or execution is complete.
more ESTAE error messages referring to the current
problem. If possible, fix the problem identified by User response
problem cannot be resolved, contact Software Support This is not an error message and no action is required.
with this problem.
AVZ4507E SUBTASK ERROR TERMINATION:
AVZ4504E rsrc sysserv FAILED, RC=rcode, RC=rcode
DETECTED AT addr
Explanation
This message is issued when the subtask driver
module terminates due to an error.

Check if any other error messages were generated This message is issued if the product was unable to
along with the error message above. If the connect to IMS/ODBA for the Startup Table Identifier
combined error messages are sufficient to explain in the message.
Codes comes from AIBRETRN, AIBREASN, and
AIBERRXT respectively.
this problem.
AVZ4508H subtask SUBTASK: objname objval User response
Check if any other messages were issued and IMS/DB
Explanation is active. If the Startup Table does not exist, generate
This message is only issued when the product service it. The next ODBA request for this startup table
task debugging is requested using the DEBUGATMD identifier will retry this operation.
option.
AVZ4523W ERROR IN DISCONNECTING
FROM IMS/ODBA CONNECTIONS.
User response RETURN CODE: rcode, REASON
CODE: rsncode
No action required. This message is informational only.
AVZ4520W LOAD FOR MODULE modname Explanation
FAILED, ODBA INITIALIZATION
ERROR This message is issued if the product was unable to
disconnect from IMS/ODBA.
Explanation Code comes from AIBRETRN, and AIBREASN.
This message is issued if a module needed to initialize
the ODBA interface to IMS could not be loaded. The User response
message contains the module name. The module is
Check if any other messages were issued and IMS/DB
either missing or some other error has occurred.
is active. If the Startup Table does not exist, generate
it. The next ODBA request for this startup table
User response identifier will retry this operation.
Check if any other messages were issued. Check if the AVZ4524W ERROR IN DISCONNECTING FROM
named module is in the search sequence. Resolve the IMS/ODBA CONNECTION tblid.
problem and restart the server. RETURN CODE: rcode, REASON
CODE: rsncode, ERROR CODE:
AVZ4521S Unable to implant ODBA interface,
errcd
return code: rcode
Explanation
Explanation
This message is issued if the product was unable to
This message is issued if the product was unable to
connect to IMS/ODBA for the Startup Table Identifier
implant its ODBA interface routine. The return code is
in the message.
provided.
Codes come from AIBRETRN, AIBREASN, AIBERRXT.
User response
User response
Check if any other messages were issued. Call
Software Support. Check if any other messages were issued and IMS/DB
is active. If the Startup Table does not exist, generate
AVZ4522W UNABLE TO CONNECT TO IMS/ it. The next ODBA request for this startup table
ODBA FOR STARTUP TABLE ID: identifier will retry this operation.
tblid, RETURN CODE: rcode,
REASON CODE: rsncode, ERROR AVZ4525I MAXIMUM NUMBER OF
CODE: errcd SIMULTANEOUS ODBA
CONNECTIONS (max) REACHED -
no TIMES - CONNECTION DENIED
Explanation AVZ4529W ERROR IN DEALLOCATING PSB:
psb FOR STARTUP TABLE tblid
This message is issued if the product was unable to DURING ODBA/RPC CLEANUP. RC:
connect to IMS/ODBA because the maximum number rcode, RE: rsncode
of simultaneous connections was reached a number
(no) of times.
Explanation
User response This message is issued if an RPC that was using the
IMS/DB ODBA Interface terminated, left some PSBs
Raise the MAXODBACONNECT parameter. Default is 8 allocated, and product cleanup encountered an error
if it was not specified. deallocating them.
AVZ4526I no ODBA CONNECTION ENTRIES Codes come from ALERTDLI calls.
FREED
User response
Explanation
Fix the error in the RPC that caused it to terminate
This message is issued if the product ODBA without deallocating these PSBs.
Connection Entry table cleanup routine was able to
free some previously allocated entries. This message AVZ4530I IMS/DB ODBA INTERFACE
is a warning of a table full condition that will begin TERMINATED
denying connections.
Explanation
User response This message is issued when the product has
Raise the MAXODBACONNECT parameter. Default is 8 terminated the IMS/DB ODBA Interface.
if it was not specified.
AVZ4527T ODBA interface not type User response
None.
Explanation AVZ4531W ERROR TERMINATING IMS/DB
This message is issued if the product ODBA Interface ODBA INTERFACE. RC: rcode, RE:
is not either initialized or enabled. rsncode
type can be initialized or enabled.
Explanation
User response This message is issued when the product has
terminated the IMS/DB ODBA Interface.
If it has not been initialized, contact Software Support.
If it is not enabled, check initialization parameters.
User response
AVZ4528I Load for module modname failed,
ODBA interface disabled None.
AVZ4532S ODBA STARTUP TABLE MODULE -
Explanation modname - IS NOT RE-ENTRANT.
UNABLE TO MODIFY
This message is issued if a module needed to initialize
the ODBA interface to IMS could not be loaded. The
message contains the module name. The module is Explanation
either missing or some other error has occurred. This message is issued when an IMS/ODBA
Connection is requested, but the startup table module
User response is not marked re-entrant. the product cannot modify
the module with server userid if required nor merge
If IMS/ODBA support is not desired, then no action DEFINE IMSODBA parameters.
is needed. Otherwise check if other messages were
issued. Check if the named module is in the search
sequence. Resolve the problem and restart the server. User response
Re-generate the DFSxxxx0 module indicated and link it
as re-entrant.

AVZ4533S ODBA MODIFY ACTION BYPASSED User response
FOR TABLE modname
Contact Software Support for assistance.
Explanation AVZ4552T COLLECTION ID collname FOR

PLAN plan WILL USE PACKAGE
This message is issued when an IMS/ODBA Modify PROCESSING
Action is requested, but there does not seem to be any
active ODBA connection under the name requested.
Explanation
User response This informational message is issued when the Db2
collection name for the current connection has been
Re-enter the Modify command with the proper Startup determined.
Table name.
AVZ4534I req OF IMS/ODBA CONNECTION User response
FOR STARTUP TABLE modname
resolution None
AVZ4553T PACKAGE OPRXSQ dbrm SECTION
Explanation sectno1 USED FOR SECTION
sectno1 STATEMENT stmtno
This message is issued when an action on an IMS/
ODBA connection is requested. The status of the
request is displayed. If the status is "failed" look Explanation
for other messages that will indicate the return and This informational message is issued when SQL
reason codes. section number translation is done for the product
resolution can be succeeded or failed. Db2 PLAN, OPRXSQ. This message will only be issued
under the direction of Software Support.
User response Note that sectno1 represents the new OPRXSQ section
number, and sectno2 represents the original OPRXSQ
Re-enter the Modify command after dealing with the section number.
errors indicated by the other messages.
AVZ4550T OPRXSQ - USER userid User response
CONNECTED WITH UNOPTIMIZED
PLAN plan None
AVZ4554T PLAN plan DOES NOT USE
Explanation PACKAGE PROCESSING
This message is issued when a user connected with an

old unoptimized OPRXSQ Db2 Plan. Explanation
This informational message is issued when the Db2
User response plan does not have a collection name that matches the
package list.
Rebind the specified plan so it includes the optimized
packages OPRXSQA-R.
User response
AVZ4551T dbrm - UNRECOGNIZED type
PROVIDED - SECTION stmtno - None
STATEMENT sectno AVZ4555T PACKAGE OPRXSQ pkge IN
COLLECTION collname SELECTED
Explanation
This message is issued when an unrecognized Explanation
statement or section number is provided to the This informational message is issued when SQL
OPRXSQ plan translation routine. section number translation is done for the product Db2
type can be either SECTION or STATEMENT. PLAN, OPRXSQ.
None This message contains the second of each two-line
response to the TSOSRV_LIST command. Each two-
AVZ4556T PLAN plan WILL USE PACKAGE line response group shows the status of the TSO
PROCESSING server and the command being executed.

This informational message is issued to indicate that None.
the optimized packages will be used to process Db2
requests. AVZ4603I SERVER asid POSTED FOR
TERMINATION
User response
Explanation
None
The TSOSRV_STOP command has posted the server for
AVZ4557T PACKAGE OPRXSQ pkge termination.
SELECTED
User response
Explanation
None.
This informational message is issued when SQL
section number translation is done for the product Db2 AVZ4604I SERVER POSTED TO FREE TSSD AT
PLAN, OPRXSQ. addr

None The TSOSRV_FREE command has posted the server for
release of the TSSD.
The variable fields of the message text are: pack
Package name that will be used.
User response
AVZ4558T PLAN plan WILL USE DRDA
SUBSTITUTE PACKAGES None.
AVZ4605I status
Explanation
This informational message is issued when the Db2 Explanation
plan will be internally converted to the use of
The TSOSRV_QUEUE command returns information
substitute packages for DRDA connections.
using this message.

None
None.
AVZ4601I status
AVZ4606E ADDRESS SEF TSOSRV_STOP asid:
ASID NOT SERVER ADDRESS
Explanation SPACE
This message contains the first of each two-line
response to the TSOSRV_LIST command. Each two- Explanation
line response group shows the status of the TSO
An invalid hex ASID was specified on a TSOSRV_STOP
server and the command being executed.
command.

None.
Correct the ASID, and re-issue the TSOSRV_STOP
AVZ4602I cmdname command.

AVZ4607S funcd OF queue FAILED, RC=rcode User response
Batch jobs must be rerun with a larger below the line
Explanation region size. TSO users must log on with a larger region
The specified function failed within the ADDRESS SEF size, and re-issue the command.
host command environment. AVZ4680T ENCLAVE SET RC=rcode FOR CALL
CODE callcd (calltype) - failmsg
User response
Determine from the message text what function failed, Explanation
and review the return codes for the failed function. While attempting to invoke a High-Level Language
Contact your local product systems programming (HLL) subroutine via the MVS Language Environment
group assistance. CEEPIPI interface module, an error occurred. This
AVZ4608E ADDRESS SEF TSOSRV_FREE addr: message logs the error. This message may be followed
ADDRESS NOT THAT OF A TSSD by message 4681 for subroutine invocations.
failmsg is specific to a given call type.
Explanation
An invalid address was specified on the TSOSRV_FREE User response
command. The HLL subroutine is not called, and the product's
LE/370 enclave may be terminated as indicated by
User response other messages. If possible, determine the cause of
the error using other messages logged, and correct the
Correct the address, and re-issue the TSOSRV_FREE problem, or contact Software Support group.
command.
AVZ4681T ROUTINE INVOKED WAS indexcd -
AVZ4609I stats subrout
The TSOSRV_EXECSTATS command returns This message follows the 4680T message when a
information using this message. subroutine invocation was underway. The subroutine
CEEPIPI table index value and its external name are
User response reported.
None.
User response
AVZ4612H jobname HAS RESET THE TSO
SERVER COMMAND EXECUTION See message 4680T.
QUEUE AVZ4682T ROUTINE RC=rcode
REASON=rsncode ENCLAVE
Explanation FEEDBACK(feedback)
A TSOSRV_RESETQ command was issued from the

specified job. Explanation
User response: This message follows the 4681T message and reports
the subroutines return code, reason code, and the
AVZ4650E UNABLE TO OBTAIN storsize LE/370 enclave feedback codes (feedback).
BYTES BELOW THE LINE
User response
Explanation
See message 4680T.
ADDRESS LINKMVS is required to obtain storage
below the 16MB line to hold both parameters and AVZ4683T ENCLAVE MGR CANNOT REENTER
a register save area to be passed to the requested SUPERVISOR STATE
program. If this storage cannot be obtained, host
command processing is terminated.
Following a call to the LE/370 CEEPIPI routine, normal See the contents of the message and the trace
supervisor state operation of the enclave manager surrounding this condition, and correct the problem.
could not be restored. Contact Software Support with this error.
AVZ4687T ENCLAVE TERMINATED BY COBOL
User response STOP RUN - CLIENT CONNECTION
Contact Software Support. TERMINATED
AVZ4684T ENCLAVE ABENDED CONDITION

Explanation
CODE=ccode, REASON=rsncode
FOR CALL CODE callcd (calltype) - A COBOL RPC program ended with a STOP RUN
failmsg statement which caused the LE enclave to terminate.

While attempting to invoke a High-Level Language Replace the STOP RUN statement with a GOBACK
(HLL) subroutine via the MVS Language Environment statement and recompile and link the program.
CEEPIPI interface module, an abend was intercepted.
This message logs the error. This message may AVZ4700T %1 MODEL QUEUE NAME NOT SET
be followed by message 4681T for subroutine - %2 USED AS MODEL QUEUE
invocations.
Explanation
User response The name of the model queue for this qmanager
The HLL subroutine is not called, and the product's instance has not been set. The default model queue
LE/370 enclave may be terminated as indicated by will be used, if possible.
other messages. If possible, determine the cause of
the error using other messages logged, and correct the User response
problem, or contact Software Support group.
The MQ task will attempt to open the queue using the
AVZ4685T api PLIST ERROR errdesc - plistval default model queue.
(data)
AVZ4702T '%1' INPUT QUEUE NAME NOT SET
- '%1' PROCESSING TERMINATED
Explanation
While attempting to invoke a High-Level Language Explanation
(HLL) callback routine, the callback routine detected
The name of the input queue for this qmanager
a parameter list validation error. This message logs the
instance has not been set. The default input queue will
reason for the plist validation error.
be used, if possible.
User response:
An invalid plist return code is set by the API function,
User response
and return is made to the HLL program. Contact
Software Support with this error. The MQ task will attempt to open the queue using the
default input queue.
AVZ4686S msgtext
AVZ4704H UNKNOWN service CODES -
Explanation RE=rsncode RC=rcode
A severe error message was logged to the trace by

a High-Level Language (HLL) component of the main
Explanation
product. The message is also logged to the operator This message reports IBM/MQ return and reason
console using this message ID. codes that are unknown to AVZ.
User response
possible that you are running a version of IBM/MQ not

yet supported by AVZ. If the version of IBM/MQ that User response
you are running DOES appear to be supported, contact
Software Support. None. The message gives the command text that will
be presented to IDCAMS.
AVZ4706T msgtext
AVZ4753T IDCAMS RESULTS:
LASTCC=lstcc COMPCODE=ccode
Explanation REASCODE=rsncode
This is a general purpose message that may or may not
indicate some type of IBM/MQ error. Explanation
The IDCAMS utility has completed. This message
User response reports the LASTCC, completion codes, and reason
Read the message text carefully. Some messages codes.
messages. If the message indicates an error, check User response
for any associated IBM/MQ produced error messages.
If you are unable to diagnose the problem, contact None. The message reports the completion codes at
Software Support. the end of the IDCAMS request.
AVZ4750T IDCAMS SYSPRINT: msgtext AVZ4800E DYNALLOC reqtype ddname

- ABEND - COND=condcd
REASON=rcode
Explanation
The IDCAMS utility has generated SYSPRINT output. Explanation
The output line is given in the message text. IDCAMS
has been invoked using the product's S_AVZRXID A DYNALLOC request failed due to an abend.
interface.
User response
User response The request fails. Check for other messages that might
None. The message gives the text of a SYSPRINT line indicate the cause of the failure.
generated by the IDCAMS utility. AVZ4801H cmdname command (issued
AVZ4751T IDCAMS WARNING: msgtext internally) rejected - another
request request is already running
Explanation
Explanation
The IDCAMS utility has generated SYSPRINT output.
The output line is given in the message text. IDCAMS An internally generated SEF command cannot be
has been invoked using the product's AVZRXID scheduled at the present time, because the system
interface. The message is issued in response to an allows only one request of this type to be processed at
IDCxxxx message condition detected by IDCAMS. once.

None. The message gives the text of a SYSPRINT line The system rejects the request and continues to
generated by the IDCAMS utility. process the in-flight request. Normally, this message
would be issued infrequently (only in certain "race"
AVZ4752T IDCAMS SYSIN: msgtext conditions). If this message is issued frequently,
contact Software Support for advice on setting server
Explanation start-up parameters.
The IDCAMS utility is about to be invoked by the AVZ4802H ABEND CC(condcd)

AVZRXID REXX interface program. This message REASON(rsncode) IN
traces the command text that will be passed to the modname+offset WHILE
IDCAMS utility. PROCESSING cmdname
COMMAND ISSUED BY userid
An SEF command service processing subtask abended The system recalculates the BROWSEARCHIVECOUNT
while processing the indicated command. value as one-third of the BROWSEMAX value.
AVZ4806H BROWSEARCHIVECOUNT
User response parameter has been set to val
Check for other messages which might indicate the - was above maximum (maxval)
cause of this failure. allowed
AVZ4803E cmdname COMMAND FROM userid

Explanation
FAILED - RC = rcode desc ccode
Trace Browse archive support has been turned on, but
Explanation the BROWSEARCHIVECOUNT parameter was set too
high.
The SEF command service processing routine has
ended with an error. The message reports the
User response
command being processed, the requesting MVS
userid, the service return code, and any abend The system recalculates the BROWSEARCHIVECOUNT
condition code encountered. value as one-third of the BROWSEMAX value.
AVZ4807H BROWSEARCHIVECUSHION
User response parameter has been set to val
Check for other messages which might indicate the
cause of this failure. Explanation
AVZ4804E Trace Browse archiving disabled Trace Browse archive support has been turned on,
because BROWSEMAX(val) value but the BROWSEARCHIVECUSHION parameter was
is less than the minimum(minval) set too high or too low.
allowed
User response
Explanation
The system resets the BROWSEARCHIVECUSHION
Trace Browse archive support has been turned off, value as indicated which is the minimum allowed
because the trace must contain at least the minimum value.
given number of messages.
The variable fields of the message text are: value
current BROWSEARCHIVECUSHION value
User response
AVZ4808S Archive backup is under stress -
When too few messages are supported in the trace, val messages can be logged before
it can wrap around before archives of the trace can overlay
be created. This message indicates that the current
trace contains so few messages that this is likely to
occur. Increase the BROWSEMAX start-up parameter
Explanation
value to at least the minimum amount. Note that the An archive backup of the trace currently cannot
minimum given is only a rough estimate and may be be scheduled because one is already underway.
entirely insufficient to guarantee that wraparound will Wraparound trace recording has entered the final
not occur. range of messages, and a wraparound will occur
unless the previous archive completes in time for a
AVZ4805H BROWSEARCHIVECOUNT
new one to be scheduled.
parameter has been set to val
- was below minimum (minval)
allowed User response
The system continues to monitor the status,
Explanation either deleting this message when the condition is
corrected or escalating the severity if a wraparound
Trace Browse archive support has been turned on, but
actually occurs. If some process is inhibiting the
the BROWSEARCHIVECOUNT parameter was not set
completion of archive backup processing in a
or was set too low.
timely manner, correct the problem. Consider that

the trace size (BROWSEMAX) and/or the archive Explanation
control parameters (BROWSEARCHIVECOUNT and
BROWSEARCHIVECUSHION) may need to be enlarged. An internally generated SEF command was not
scheduled due to an unexpected error in the command
AVZ4809S Trace Browse in overlay mode processing interface routines.
- unarchived records are being
overwritten
User response
Explanation The SEF command is not scheduled. The command
requestor continues.
The trace log has wrapped around, and un-archived
messages are now being overwritten. This message AVZ4813I cmdname command cannot be
replaces the 4808S message if a stress condition is scheduled at this time - a similar
not relieved. request is already running

The system continues operating and monitoring An archive request has been made, but processing
conditions. This message is deleted if a new archive of the request cannot be scheduled at this time,
backup that relieves the overall stress condition can because a previous request of the same type has not
be completed; however, the overlaid records cannot be yet completed. The system allows, at most, only one
recovered. archive backup/cleanup task to run, and, at most, only
one user requested archive extract.
AVZ4810H Trace 'BACKUP ARCHIVE'
command should be externally
scheduled
User response
None. Resubmit the request once the previous request
Explanation has completed.
The BROWSEARCHIVE option is set to MESSAGE, and AVZ4814I cmdname command cannot be
the system has detected that a backup archive of the scheduled at this time - all SEF
trace should now be created. service subtasks are busy

The system issues this message and takes no other An archive request has been made, but processing of
action. You should immediately schedule an archive the request cannot be scheduled at this time, because
backup operation. a subtask is not available to service the request.
AVZ4811H Trace 'ARCHIVE BACKUP' is being

automatically requested
User response
None. Resubmit the request once a subtask is free.
Explanation AVZ4815I SEF service task, tskname,
The BROWSEARCHIVE option is set to AUTO, and the attached for cmdname - requested
trace subtask is requesting a backup-type archive of by userid-reqorigin
the selected messages.
Explanation
User response An asynchronous SEF service subtask has been
The BACKUP ARCHIVE request is scheduled by the attached for processing of a long-running command.
SEF subtask for asynchronous execution.
AVZ4812E SEF INTERFACE SET RC=rcode FOR
User response
cmdname COMMAND REQUEST None.
ISSUED BY userid
AVZ4816I Running: EFTK cbaddr
Routine:routine TCB addr USERID
userid UTYPE reqtype ECB ecb CMD
cmdname
An ARCHIVE STATUS request has been issued. This An asynchronous command procedure subtask was
message is part of the response. terminated forcibly by product shutdown. This
message is sent to the requestor as notification of the
User response shutdown.
None.
User response
AVZ4817I TRACE: CURRENTMSG msgno None.
LASTARCHIVED msgno
LASTTRIGGERED msgno DSNAME AVZ4821T Service subtask subtask forcibly
word1 CTLS word2 %6 detached at shutdown - cmdname
command sent by userid -
Explanation RC=rcode
An ARCHIVE STATUS request has been issued. This

Explanation
message is part of the response.
An asynchronous command procedure subtask has
word1 and word2 represent internal control words.
forcibly detached during shutdown because it did not
voluntarily terminate operation quickly enough.
User response
None. User response
AVZ4818E Processing of cmdname command None.
by subtask subtask terminated by
AVZ4822H 'ARCHIVE BACKUP' processor has
E-O-T - RC=rcode
been attached as an SEF service
subtask
Explanation
An asynchronous command procedure subtask has Explanation
terminated unexpectedly while processing an SEF
A backup-type archive of the Trace Browse data has
command. This message is sent to the requestor as
been requested. The processor service routine has
notification of the failure.
now been attached. Additional status and completion
messages will be logged to report the results of the
User response backup operation.
Check for other messages which indicate the cause of
the unexpected termination. User response
AVZ4819T Service subtask subtask None.
completed processing of cmdname
AVZ4823H Archive file: DSN=dsname,
command sent by userid -
FirstMsg=msgno, LastMsg=msgno,
RC=rcode
Count=count
An asynchronous command procedure subtask has
A new archive data set has been successfully created.
terminated.
This message logs the dsname, the first and last
message recorded in the archive, and the count of
User response messages.
None.
User response
AVZ4820E Processing of cmdname command
by subtask subtask terminated by None.
product shutdown - RC=rcode
AVZ4824H count messages beginning at
number msgno cannot be backed
up due to Trace wraparound

A backup-type archive of the Trace Browse data has The S_ARCHIV REXX procedure was executed while
been scheduled. The indicated range of messages performing an archive allocation or cleanup service.
(count) cannot be backed up because it has been, The REXX routine produced trace or SAY messages.
or shortly will be, overlaid by wraparound within the
The data in the message comes from SYSTSPRT.
trace.
User response
User response
The messages produced by S_ARCHIV are logged by
Processing continues. Check and adjust
this message.
the BROWSEMAX, BROWSEARCHIVECOUNT, and
BROWSEARCHIVECUSHION parameters to ensure that AVZ4828E procedure REXX PROCEDURE
the trace does not wrap around without allowing RETURNED INVALID/INCORRECT
backup operations to complete. This message is RESULT FOR ARCHIVE DATA SET
normal if you activate automatic archives against an calltype REQUEST
existing trace file that has been in use for some time.
AVZ4825H NO WORK TO DO - ARCHIVE Explanation
STARTING MESSAGE = msgno -
The S_ARCHIV REXX procedure was executed but it
ENDING MESSAGE = msgno
either did not return a result or it returned a result
that was formatted improperly. The REXX procedure is
Explanation assumed to have failed.
A backup-type archive of the Trace Browse data has
been scheduled. There are no messages that can User response
currently be backed up within the range allowed by
The current archive-related operation is terminated.
the BROWSEARCHIVECUSHION value.
AVZ4829E procedure REXX PROCEDURE
User response FAILED FOR calltype REQUEST -
ROUTINE SET RETURN CODE TO
Processing ends. Check and adjust the rcode
BROWSEMAX, BROWSEARCHIVECOUNT, and
BROWSEARCHIVECUSHION parameters to ensure that
Explanation
the trace does not wrap around without allowing
backup operations to complete, or explicitly request The S_ARCHIV REXX procedure was executed but
an ARCHIVE BACKUP, TOEND operation to bypass returned with a failure return code value set.
processing of the storage cushion value.
AVZ4826W ARCHIVE PROCESSING ABORTED User response
DUE TO SUBSYSTEM OR SEF The current archive-related operation is terminated.
TERMINATION REQUEST
AVZ4830E procedure REXX PROCEDURE
Explanation FAILED TO RETURN DATA SET
NAME FOR calltype REQUEST
An archive process is being aborted either because a
subsystem shutdown is underway or because SEF has
Explanation
requested early termination of the procedure.
The S_ARCHIV REXX procedure was executed but
User response returned without passing back an MVS data set name,
as required for the sub-function request.
Processing ends as quickly as possible. Some resource
cleanup may be deferred until subsystem restart.
User response
AVZ4827I msgdata The current archive-related operation is terminated.
AVZ4831E DYNALLOC FAILURE - RC=rcode
ERROR=errcd REASON=rsncode
desc
Explanation AVZ4835S service OF dsname FAILED,
RC=rcode, REASON CODE=rsncode
Dynamic allocation failure occurred while building an
archive of the Trace Browse. The archival process
terminates. Explanation
desc describes the DYNALLOC operation. This error message describes errors that occurred
while using the DIV (Data In Virtual) system service
(service) during archive initialization, execution, or
User response termination. For a list of the return codes and reason
Check other messages indicating the cause of the codes from the DIV macro see the appropriate
failure. documentation.
AVZ4832H Allocated: DDN=ddname,

DSN=dsname - for archive output User response
Check the DIV return and reason codes associated
Explanation with this problem. There may be one or more error
messages referring to the current problem. If possible,
A ddname allocation was made for an archive output fix the problem identified by the error messages, and
linear data set. Archive processing continues. restart the product. If the problem cannot be resolved,
User response AVZ4836S service OF dsname FAILED,
None. ABEND=abcode, REASON
CODE=rsncode
AVZ4833H LDS dsname created for cmdname
command issues by userid
Explanation
Explanation This error message describes an abend that occurred
while using the DIV (Data In Virtual) system service
An archive backup or extract procedure created a new (service) during archive initialization, execution, or
VSAM linear data set for output. The actual IDCAMS termination. The abend codes and reason codes from
definition was performed by the S_ARCHIV REXX the DIV macro are documented in the IBM manual
routine in SYSEXEC. This message logs the new cluster z/OS Programming: Assembler Services Reference.
name.
User response
User response
Check the DIV abend and reason codes associated
None. with this problem. There may be one or more error
AVZ4834S service OF desc FAILED, RC=rcode messages referring to the current problem. If possible,
fix the problem identified by the error messages, and
Explanation contact Software Support.
This is a generic error message used to describe AVZ4837S Possible shortage of storage,
a wide variety of archive data set initialization and storsize bytes required to build
termination errors. The message text provides the archive output data set
current operation (service) and what the current
operation was trying to do, such as GETMAIN,
FREEMAIN, ATTACH, and so on. Explanation
This is a follow-up message to message 4834S when a
User response GETMAIN has failed. This message indicates the size,
in bytes, of the area requested by the GETMAIN.
If possible, fix the problem identified by the error If the GETMAIN return code indicates insufficient
messages, and restart the product. If the problem storage to complete the GETMAIN request, please
cannot be resolved, contact Software Support. increase your available storage (above the 16MB line)
by the indicated amount.

AVZ4838H Deallocated: DDN=ddname, MSGSTART=msgno
DSN=dsname - for archive output MSGCOUNT=count FORUSER=user
A ddname deallocation was processed for an archive This message follows message 4840H and logs the
data set. recovery information that is being cleared.

None. None.
AVZ4839W Archive file: count invalid/overlaid AVZ4843I cmdname command from userid
messages detected during completed successfully
execution
Explanation
Explanation The SEF command service processing routine has
While the archive data set was being created, ended successfully.
messages were detected that had been overlaid or
were otherwise invalid. User response
None.
User response
AVZ4844H Archive backup of trace has
None.
successfully completed
AVZ4840H CLEARARCHIVERECOVERY
PARAMETER SET TO YES - Explanation
IN-FLIGHT ARCHIVE archtyp
INFORMATION BEING CLEARED A checkpointing-type backup of the Trace Browse has
been completed successfully.
Explanation
User response
During subsystem startup, the
CLEARARCHIVERECOVERY parameter was set. In- None.
flight recovery information will be deleted for the
AVZ4845H Trace: current message is msgno -
indicated archive type.
count messages since last archive

None. Recovery information is cleared unconditionally.
Trace Browse archiving is enabled. This message is
AVZ4841H CLEARED BACKUP RECOVERY produced just before an archive request is generated.
INFO - OUTDSN=dsname
MSGSTART=msgno User response
MSGCOUNT=count
LASTARCH=msgno None.
AVZ4846H Trace: last message archived
Explanation was msgno - last requested for
message msgno
This message follows message 4840H and logs the
recovery information that is being cleared.
Explanation
User response Trace Browse archiving in enabled. This message is
produced just before an archive request is generated.
None.
AVZ4842H CLEARED EXTRACT RECOVERY User response
INFO - OUTDSN=dsname
None.
AVZ4847I cmdname CMD NOT SCHEDULED User response
- DUPLICATE %2 CMD RECOVERY
NOT COMPLETED None.
AVZ4854E THE DIV OBJECT, dsname,
Explanation CANNOT BE MAPPED - THE
VERSION CODE (%1) IS
An SEF service request cannot be processed BACKLEVEL AND INCOMPATIBLE
because internal controls indicate another operation
is already in-flight. However, no subtask is currently
processing the request. This error can occur when Explanation
certain commands fail and require separate recovery The archive data set review request cannot be
procedures to be scheduled. For brief moments, serviced because DIV reports one size for the object
a "race" condition may occur, where the recovery but LISTCAT reports another.
command has priority.
User response
User response
Wait until the previous process is recovered. If the
condition persists, manually request recovery. AVZ4855E THE DIV OBJECT, dsname,
CANNOT BE MAPPED - THE HI-
AVZ4848H cmdname CMD NOT SCHEDULED USED-RBA code IS LESS THAN
- DUPLICATE %2 CMD RECOVERY THE DIV-ACCESS PAGE COUNT
NOT COMPLETED size RETURN VALUE
See message 4847I. This message is hard-copied for The archive data set review request cannot be
internally issued requests. serviced because DIV reports one size for the object
but LISTCAT reports another.
User response
See message 4847I. User response
AVZ4849I PARAMETERS: OPTION parval1 Contact Software Support for assistance.
COUNT parmal2 CUSHION parval3 AVZ4856E THE DIV OBJECT, dsname,
CANNOT BE MAPPED - THE DATA
Explanation SET CONTROL AREA (BOST) IS
INVALID
message is part of the response.
Explanation
The parmval values represents
BROWSEARCHIVE, BROWSEARCHIVECOUNT, and The archive data set review request cannot be
BROWSEARCHIVECUSHION values, respectively. serviced because the first page of the linear data set
object does not contain required control information.
User response
User response
None.
The probable cause of this error is that you are
AVZ4850I desc TYPE archtyp USER userid attempting to review an archive data set that is still
STARTMSG msgno MSGCOUNT being created or that was not closed properly.
count DSNAME dsname
CANNOT BE MAPPED - THE
Explanation DATA SET CONTROL AREA SIZE
An archive status request has been issued. This INFORMATION (size1/size2) DOES
message is part of the response. NOT MATCH THE DIV OPEN STATS
(size3/size4)

The archive data set review request cannot be None.
serviced because the first page of the linear data
AVZ4861I statement
set object does not contain control information that
matches the size information returned by DIV.
Explanation
Note that size1 and size3 are in bytes, which size2 and
size4 are in pages. An ARCHIVE STATUS request has been issued. This
message is part of the response. This message is
User response repeated up to eight (8) times. The server constructs
a model IDCAMS DEFINE CLUSTER statement using
The probable cause of this error is that you are configured parameters. You can review this statement
attempting to review an archive data set that is still to ensure that the configuration parameters are set
being created or that was not closed properly. correctly. The statement reported in this message is
used to define archive backup files.
CANNOT BE MAPPED - THE
DATA SET CONTROL AREA pointer User response
POINTER (ptrval) IS renALID
None.
baseptr/count
AVZ4862I statement
Explanation
Explanation
The archive data set review request cannot be
serviced because the first page of the linear data set An ARCHIVE STATUS request has been issued. This
object does not contain control information that is message is part of the response. This message is
structurally correct. repeated up to eight (8) times. The server constructs
a model IDCAMS DEFINE CLUSTER statement using
User response configured parameters. You can review this statement
to ensure that the configuration parameters are set
The probable cause of this error is that you are correctly. The statement reported in this message is
attempting to review an archive data set that is still used to define archive extract files.
being created or that was not closed properly.
AVZ4859I Archive reset command issued by User response
userid has changed last-archived
None.
message from msgno to msgno
AVZ4863I parmval1, parmval2, ... parmval5
Explanation
Explanation
An ARCHIVE RESET command has been processed.
User response message is part of the response. This message reports
the output data set allocation related parameter
None. values set for building archive backup data sets.
AVZ4860T ARCHIVE FILE: parmval's 1-5 represent the values
DSN=dsname, FIRSTMSG=msgno, of ARCHIVEDSNPREFIX. ARCHIVEDATACLASS,
LASTMSG=msgno, COUNT=count ARCHIVEMGMTCLASS, ARCHIVESTORCLASS, and
ARCHIVEDEFCLPARMS respectively.
Explanation
User response
A new archive data set has been successfully created.
This messages logs the dsname, the first and last None.
message recorded in the archive, and the count of
messages. This message is a duplicate of 4823 (used AVZ4864I parmval1, parmval2, ... parmval5
for tracing).
Explanation statement failed to be processed through the IDCAMS
utility. The SYSPRINT output of the IDCAMS utility, if
An ARCHIVE STATUS request has been issued. This any, follows this message.
message is part of the response. This message reports
the output data set allocation related parameter
values set for building archive EXTRACT data sets. User response
parmvals 1-5 represent the values The current archive-related operation is terminated.
of EXTRACTDSNPREFIX, EXTRACTDATACLASS, AVZ4868E IDCAMS SYSPRINT: msgdata
EXTRACTMGMTCLASS, EXTRACTSTORCLASS, and
EXTRACTDEFCLPARMS respectively.
Explanation
User response This message follows message 4867E when an
IDCAMS DEFINE CLUSTER or DELETE CLUSTER
None. statement failed to be processed through the IDCAMS
AVZ4865E Trace Browse archiving disabled utility. The SYSPRINT output of the IDCAMS utility
because 'ARCHIVEDSNPREFIX' (msgdata) follows this message.
parameter is not set
User response
Explanation The current archive-related operation is terminated.
Trace Browse archive support has been turned off AVZ4869E TRACE BROWSE
because the output data set name prefix parameter EXTRACTS DISABLED
ARCHIVEDSNPREFIX is not set. A data set name prefix BECAUSE 'EXTRACTDSNPREFIX'
is required. PARAMETER IS NOT SET

Note that you can review and possibly set Trace Browse extract support has been turned off
values for the following archive data set because the output data set name prefix parameter
allocation related parameters: ARCHIVEDSNPREFIX, EXTRACTDSNPREFIX is not set. A data set name prefix
ARCHIVEDATACLASS, ARCHIVEMGMTCLASS, is required.
ARCHIVESTORCLASS, and ARCHIVEDEFCLPARMS.
AVZ4866E service of archive output data set User response
failed due to failrsn
Note that you can review and possibly set
values for the following extract data set
Explanation allocation related parameters: EXTRACTDSNPREFIX,
One of the following errors occurred: (1) allocation EXTRACTDATACLASS, EXTRACTMGMTCLASS,
of a new archive backup or extract file failed, or EXTRACTSTORCLASS, and EXTRACTDEFCLPARMS.
(2) deletion during cleanup for a failed archive AVZ4870E reqtype reqfunc - ABEND -
failed. For allocation failures, the reason may be that CODE=abcode REASON=rsncode
runtime parameters used to generate IDCAMS DEFINE
CLUSTER statements are not set properly.
Explanation
User response An application programming interface request
abended.
The current archive-related operation is terminated.
AVZ4867E IDCAMS UTILITY LASTCC=lastcc User response
--- ABEND CONDITION ccode,
REASON rcode - SYSPRINT The request fails. Check for other messages that might
FOLLOWS indicate the cause of the failure.
AVZ4871S Automatic archival of Trace
Explanation suspended due to previous error
- correct problem and issue
This message follows message 4866E when an "ARCHIVE CLEANUP"
IDCAMS DEFINE CLUSTER or DELETE CLUSTER

An archive backup operation has failed with an error This keyword is not part of any AVZ command.
requiring intervention. Such a condition exists if, for
example, the IDCAMS allocation parameters are not User response
configured properly. Any new attempt to automatically
schedule an archive will likely fail until action is taken Recode the AVZ command, and rerun.
to correct the problem.
AVZ5004S The keyword keyword is missing.
User response
Explanation
Examine the console hardcopy log and the Trace
The indicated keyword is required but was not coded.
Browse to determine why the previous automatic
backup operation has failed. Correct the situation.
Once the cause of the failure has been corrected, issue User response
an ARCHIVE CLEANUP command via the SEF interface
Recode the AVZ command using the keyword, and
to reset the in-flight failure indicators. You can issue
rerun.
this command using the ISPF E.3 application.
AVZ5005S value is not a valid value for the
AVZ5000S MESSAGE NUMBER msgno IS NOT
keyword keyword.
DEFINED
Explanation
Explanation
The value you have coded is not valid value for the
This message is issued whenever an undefined
keyword.
message number is encountered.
User response
User response
Recode the value, and rerun the AVZ command.
This probably indicates an internal product error.
Contact Software Support. AVZ5006S keyword IS ONLY VALID FOR TYPE
= ktype
AVZ5001S object IS AN INVALID %PX
OBJECT
Explanation
Explanation The keyword indicated is not valid for the given value
of the type of keyword.
You have tried to DEFINE/MODIFY an unknown AVZ
object.
User response
User response Remove the erroneous keyword (or change the type),
and rerun the command.
Correct the DEFINE/MODIFY command, and rerun.
AVZ5007S LINK host already exists.
AVZ5002S cmdname is an invalid %PX
command.
Explanation
Explanation The indicated link has already been defined.
The command you have coded is unknown to Note that host is the host keyword.
ADDRESS AVZ.
User response
User response
Determine which definition is correct, and rerun.
Enter the correct AVZ command, and rerun.
AVZ5008U OPRXPC TERMINATED WITH
AVZ5003S keyword is an invalid keyword. SEVERE ERROR RC = rcode
An internal component of ADDRESS AVZ has failed. The indicated subsystem is not running. The ADDRESS
AVZ host environment command cannot be processed.
User response
User response
Start the subsystem (or use the SUBSYS command to
AVZ5009S MODIFY CONTAINS FIELDS NOT identify another subsystem), and rerun the command.
SUPPORTED BY LINK TYPE
AVZ5014S subsystem IS AN INVALID
Explanation SUBSYSTEM NAME
Explanation:
You cannot modify fields that are undefined for this
The subsystem name coded is not valid.
type of link.
User response:
User response Subsystem names must begin with an alpha (a-
z) character, and all other characters can be
Remove the keywords in error, and rerun the alphanumeric. Also, the name can only be four (4)
command. characters long.
AVZ5010E HOST = host DOES NOT EXIST AVZ5015E DATABASE subsys IS ALREADY
DEFINED
Explanation
Explanation
The link defined by the host is not yet defined;
therefore, it cannot be modified. The indicated database subsystem has already been
defined.
User response
User response
Either define the link, or remove the MODIFY.
AVZ5011S object DISPLAY FAILED WITH RC =
rcode AVZ5016E DATABASE = subsys DOES NOT
EXIST
Explanation
Explanation
The display of the object failed severely.
The database defined by name (subsys) is not yet
User response defined; therefore, it cannot be modified.
There is probably some sort of internal error. Contact

User response
Software Support.
Either define the database, or remove the MODIFY.
AVZ5012S keyword CONTAINS A QUOTE AND
QUOTES ARE NOT PERMITTED AVZ5017S parmname IS NOT A VALID
PRODUCT PARAMETER NAME
Explanation
Explanation
AVZ keywords do not require or permit quotes.
The parameter name is not a valid, recognized product
User response parameter.
Remove the quote marks, and rerun.

User response
AVZ5013S %PX SUBSYSTEM subsys IS NOT
Correct the parameter name, and rerun.
ACTIVE
AVZ5018S parmval IS NOT A VALID VALUE
FOR parmname

Explanation AVZ5023E CONNECTION conn IS ALREADY
DEFINED
The parameter value is not valid for this parameter.
Explanation
User response
The indicated connection has already been defined.
Correct the value, and rerun.
AVZ5019E subsys IS A DB2 DATABASE User response
SUBSYSTEM
Explanation AVZ5024E SESSION session IS ALREADY
DEFINED
The database subsystem can not be defined because
the subsystem is an actual Db2 subsystem.
Explanation
User response The indicated session has already been defined.
Change the database subsystem name, and rerun.
User response
AVZ5020E ANOTHER COPY OF THE PRODUCT
USES DATABASE SUBSYSTEM Determine which definition is correct, and rerun.
NAME subsys AVZ5025I DDNAME ddname IS NOT
ALLOCATED TO PRODUCT
Explanation ADDRESS SPACE
The database subsystem cannot be defined because
another copy of the product is using the database Explanation
subsystem. The indicated ddname is not allocated to the product
address space.
User response
Change the database subsystem name, and rerun. User response
AVZ5021E DATABASE SUBSYSTEM subsys The attempt to define the file fails. Add a DD
COULD NOT BE CREATED statement to the product start-up JCL for the indicated
file, and restart the product.
Explanation AVZ5026T MEASURED USAGE reqtype
COMPLETED SUCCESSFULLY
The database subsystem control blocks could not be
created.
Explanation
User response This message indicates that Measured Usage Request
completed successfully.
Fix any related errors, and rerun.
AVZ5022E ANOTHER PRODUCT USES User response
DATABASE SUBSYSTEM NAME
subsys No action required.
AVZ5027T MEASURED USAGE reqtype
Explanation REQUEST MAY HAVE FAILED,
RC=rcode
The database subsystem cannot be defined because
another product is using the database subsystem.
Explanation
User response This message indicates that Measured Usage Request
may have failed. Please check return code and request
Change the database subsystem name, and rerun. type.
No action required. This is an informational message. No action is
required. However, if diagnostic tracing has been
AVZ6000T ENTER MODULE csect
turned on at the request of Software Support, please
contact Software Support for further instructions.
Explanation
AVZ6008T RETURN FROM LINKING
This diagnostic trace message is issued to indicate that TO OPDSN10 SUBCOMMAND
control has entered a particular product module. HANDLER

This is an informational message. No action is This diagnostic trace message is issued on return from
required. However, if diagnostic tracing has been linking to OPDSN10, the subcommand handler.
call for further instructions.
User response
AVZ6003T MATCHING SSCT LOCATED FOR This is an informational message. No action is
SUBSYSTEM subsys required. However, if diagnostic tracing has been
Explanation contact Software Support for further instructions.
This diagnostic trace message is issued in response AVZ6009T PRIOR TO ATTACHING OPDSN10
to being able to locate an SSCT that matches the SUBCOMMAND HANDLER
subsystem name that was extracted.
Explanation
User response
This diagnostic trace message is issued just prior to
This is an informational message. No action is attaching OPDSN10, the subcommand handler.
User response
This is an informational message. No action is
AVZ6004T TRANSFERRING CONTROL TO
MODULE DSNECP00
Explanation
AVZ6010T RETURN FROM ATTACHING
This diagnostic trace message is issued just prior OPDSN10 SUBCOMMAND
to transferring control to the IBM-supplied DSN HANDLER
command. It has been determined that the current
DSN command session is bound for a copy of Db2
Explanation
whose connection is not being managed by the
product. This diagnostic trace message is issued on return from
attaching OPDSN10, the subcommand handler.
User response
User response
required. However, if diagnostic tracing has been This is an informational message. No action is
turned on at the request of Software Support, please required. However, if diagnostic tracing has been
contact Software Support for further instructions. turned on at the request of Software Support, please
AVZ6007T PRIOR TO LINKING TO OPDSN10
SUBCOMMAND HANDLER AVZ6011T OPDSN10 SUBCOMMAND
HANDLER DETACHED
Explanation SUCCESSFULLY
This diagnostic trace message is issued just prior to

linking to OPDSN10, the subcommand handler.

Explanation AVZ6016T VALID SUBCOMMAND subcmd
ACCEPTED
This diagnostic trace message is issued after
successfully detaching OPDSN10, the subcommand
handler. Explanation
User response determining that the subcommand entered by the user
is one of the set of valid subcommands supported by
This is an informational message. No action is module OPDSN10.
contact Software Support for further instructions. User response
AVZ6013T EXITING MODULE csect This is an informational message. No action is
This diagnostic trace message is issued just prior AVZ6017T UNRECOGNIZED SUBCOMMAND
to exiting the module named in the diagnostic trace ASSUME TSO COMMAND subcmd
message.
Explanation
User response
This is an informational message. No action is determining that the subcommand entered by the
required. However, if diagnostic tracing has been user is neither one of the set of valid subcommands
turned on at the request of Software Support, please supported by OPDSN10 nor one of the set of TSO
contact Software Support for further instructions. commands not supported by OPDSN10.
AVZ6014T OPDSN10 STAX EXIT
SUCCESSFULLY ESTABLISHED User response
Explanation required. However, if diagnostic tracing has been
This diagnostic trace message is issued after turned on at the request of Software Support, please
successfully establishing the STAX exit for module contact Software Support for further instructions.
OPDSN10. AVZ6018T PRIOR TO LINKING TO TSO
COMMAND subcmd
User response
This is an informational message. No action is Explanation
required. However, if diagnostic tracing has been This diagnostic trace message is issued just prior
turned on at the request of Software Support, please to linking to the TSO command specified as a DSN
contact Software Support for further instructions. subcommand.
AVZ6015T OPDSN10 STAX EXIT
SUCCESSFULLY REMOVED User response
Explanation required. However, if diagnostic tracing has been
This diagnostic trace message is issued after turned on at the request of Software Support, please
successfully removing the STAX exit for module contact Software Support for further instructions.
OPDSN10. AVZ6019T RETURN FROM LINKING TO TSO
COMMAND subcmd
User response
required. However, if diagnostic tracing has been This diagnostic trace message is issued on return
turned on at the request of Software Support, please from linking to the TSO command specified as a DSN
contact Software Support for further instructions. subcommand.
This is an informational message. No action is This diagnostic trace message is issued after
required. However, if diagnostic tracing has been successfully allocating the data set specified on the
turned on at the request of Software Support, please LIBRARY() parameter of the RUN subcommand.
AVZ6020T PRIOR TO ATTACHING TSO User response
COMMAND subcmd This is an informational message. No action is
Explanation turned on at the request of Software Support, please
This diagnostic trace message is issued just prior
to attaching the TSO command specified as a DSN AVZ6024T SUCCESSFULLY DEALLOCATED
subcommand. DATA SET dsname

This is an informational message. No action is This diagnostic trace message is issued upon
required. However, if diagnostic tracing has been successfully deallocating the data set specified on the
turned on at the request of Software Support, please LIBRARY() parameter of the RUN subcommand.
AVZ6021T RETURN FROM ATTACHING TSO User response
COMMAND subcmd This is an informational message. No action is
Explanation turned on at the request of Software Support, please
This diagnostic trace message is issued on return
from attaching the TSO command specified as a DSN AVZ6025T RUN SUBCOMMAND BUFFER
subcommand. PARSED SUCCESSFULLY

This is an informational message. No action is This diagnostic trace message is issued after
required. However, if diagnostic tracing has been successfully parsing the RUN subcommand buffer.
contact Software Support for further instructions. User response
AVZ6022T SUCCESSFUL DETACH TSO This is an informational message. No action is
COMMAND cmdname required. However, if diagnostic tracing has been
This diagnostic trace message is issued after AVZ6026T LIBRARY : dsname
successfully detaching the TSO command specified as
a DSN subcommand. Explanation
This diagnostic trace message is issued in order to
User response
present the interpreted library specification.
required. However, if diagnostic tracing has been User response
contact Software Support for further instructions. This is an informational message. No action is
AVZ6023T SUCCESSFULLY ALLOCATED DATA turned on at the request of Software Support, please
SET dsname contact Software Support for further instructions.
AVZ6027T PLANID : planname

This diagnostic trace message is issued in order to This diagnostic trace message is issued prior to
present the interpreted plan specification. processing the Db2 identify request.

This is an informational message. No action is This is an informational message. No action is
required. However, if diagnostic tracing has been required. However, if diagnostic tracing has been
turned on at the request of Software Support, please turned on at the request of Software Support, please
contact Software Support for further instructions. contact Software Support for further instructions.
AVZ6028T PROGRAM : progname AVZ6032T AFTER IDENTIFY DB2 CALL
===========================
Explanation =
This diagnostic trace message is issued in order to

Explanation
present the interpreted program specification.
User response processing the Db2 identify request.

User response
turned on at the request of Software Support, please This is an informational message. No action is
contact Software Support for further instructions. required. However, if diagnostic tracing has been
AVZ6029T CP : indicator contact Software Support for further instructions.
Explanation AVZ6033T BEFORE CREATE THREAD DB2

CALL ======================
This diagnostic trace message is issued in order
to present a YES/NO value (indicated by indicator)
Explanation
depicting whether the CP parameter was or was not
specified. This diagnostic trace message is issued prior to
processing the Db2 create thread request.
User response
User response
required. However, if diagnostic tracing has been This is an informational message. No action is
turned on at the request of Software Support, please required. However, if diagnostic tracing has been
contact Software Support for further instructions. turned on at the request of Software Support, please
AVZ6030T PARMS : indicator
AVZ6034T AFTER CREATE THREAD DB2 CALL
Explanation =======================
This diagnostic trace message is issued in order

Explanation
to present a YES/NO value (indicated by indicator)
depicting whether the PARMS() parameter was or was This diagnostic trace message is issued after
not specified. processing the Db2 create thread request.

This is an informational message. No action is This is an informational message. No action is
required. However, if diagnostic tracing has been required. However, if diagnostic tracing has been
turned on at the request of Software Support, please turned on at the request of Software Support, please
contact Software Support for further instructions. contact Software Support for further instructions.
AVZ6031T BEFORE IDENTIFY DB2 CALL AVZ6037T BEFORE TERMINATE DB2 CALL
=========================== ==========================
Explanation AVZ6041T APPLICATION PROGRAM FAILED
WITH ABEND CODE abcode
This diagnostic trace message is issued prior to
processing the terminate Db2 request.
Explanation
User response This diagnostic trace message is issued if the
application program fails with any type of abend code.
This is an informational message. No action is This message is generated both when the application
required. However, if diagnostic tracing has been program is attached and when it is linked to.
User response
AVZ6038T AFTER TERMINATE DB2 CALL
=========================== This is an informational message. No action is
This diagnostic trace message is issued after AVZ6042T RRSAF func function RC rcode
processing the terminate Db2 request. Reason rsncode was converted to
RC 0 Reason 0.
User response
required. However, if diagnostic tracing has been This message is issued when the product has ignored
turned on at the request of Software Support, please certain error reason codes from RRSAF function calls.
AVZ6039T PRIOR TO LINKING TO PROGRAM User response
progname
required. However, if this action contributes to thread
Explanation errors later in the process, please contact Software
This diagnostic trace message is issued just prior to Support for further instructions.
linking to the program specified on the PROGRAM() AVZ6500S ABEND abcode RS=rsncode
parameter of the RUN subcommand. OCCURRED AT modname+offset
DURING DMF func entityid
User response
required. However, if diagnostic tracing has been An ABEND occurred while processing a Data Mapping
turned on at the request of Software Support, please Facility (DMF) request.
AVZ6040T RETURN FROM LINKING TO User response
PROGRAM progname
The routine signals an error to the caller and
processing continues, when possible.
Explanation
AVZ6501W DMF operation WARNING: rsn item
This diagnostic trace message is issued on return from
linking to the program specified on the PROGRAM()
parameter of the RUN subcommand. Explanation
A correctable condition was encountered while
User response processing a Data Mapping Facility (DMF) request.
This is an informational message. No action is item represents the item being processed at the time
required. However, if diagnostic tracing has been of warning detection.

The routine issues this warning message and A DMF IMPORT request has successfully processed an
processes the requested function. The warning MAY XML data map definition, but is not requested to save
indicate a condition which requires attention. it. The data map will be discarded.
AVZ6502S DMF operation ERROR: rsn item
User response
Explanation This message is issued for each datamap parsed from
an XML document, if the new/changed data map is
An un-correctable condition was encountered while not to be saved or replaced in the map library. This
processing a Data Mapping Facility (DMF) request. messages indicates that the XML document is valid.
item represents the item being processed at the time
AVZ6506T Required map map for conversion
or error detection.
of EXCI to ACI missing

The routine issues this error message and concludes
The specified map is missing from DMF. This map
processing of the requested function. Correct the
is required to dynamically create the ACI server
condition and re-run the request. For STOW error's
definition for the EXCI to ACI conversion
check the dataset space allocation for sufficient
space and sufficient directory block allocations. If the
dataset is a Services Metadata or Microflow dataset User response
you can use the parameter WSALLOC in PRODZSERV to
Use the product ISPF option "D.I" to initialize the maps
override the default allocation values.
required by the product.
AVZ6503I DMF IMPORT var MAP member
AVZ6507T Unable to create server
FROM source additinfo
serverconnection for CICS
connection connection
Explanation
A DMF IMPORT request has successfully imported an Explanation
XML data map definition and has saved the new or
Unable to create an ACI server for EXCI to
changed datamap into the mapping library.
ACI conversion for the specified CICS connection
var is an indicator that can be "SAVED" or "REPLACED". (connection).

This message is issued for each new or changed This message is issued for each CICS connection that
datamap successfully imported from an XML map is to be converted to use ACI. Probable cause is a
definition document. GETMAIN error. Check Trace Browse and the Joblog
for further messages and contact Software Support.
AVZ6504I DMF import has refreshed in-
storage data maps AVZ6509I DMF PROCESSING COMPLETE
A DMF IMPORT request has refreshed the in-storage A DMF request has completed processing. This will
data map images following import of new or changed be the last message related to the current DMF
data maps. command.

This message is issued after all new or changed This message is issued when a DMF command has
datamaps have seem saved during XML import completed processing. It is used to identify the last of
processing. a series of related DMF messages.
AVZ6505I DMF import parsed map map from
source
AVZ6520H DMF Data-In-Virtual cache is AVZ6523H Existing DMF DIV cache being
being initialized for revision level discarded due to window
lvl support relocation problem
During initialization the Data Mapping Facility (DMF) During initialization the Data Mapping Facility
determined that it's data-in-virtual cache is empty, (DMF) found the DIV linear dataset cache dataset
contains errors, or is formatted for operation at (@#$MAPL) could not be placed online because a
a different revision level. The DIV object is being problem occurred while attempting to relocate maps
initialized or re-initialized for use at the current and map pointers within the DIV windows. The cache
software support revision level. must be discarded and re-loaded in order to remove
the erroneous/problematic information.
User response
User response
This DMF DIV data-in-virtual cache will be initialized
for use and placed online. DMF cached data maps will be discarded and the DIV
dataset re-initialized. DMF will reload data maps into
AVZ6521H Existing DMF DIV cache at revision the cache as these are read into storage from the
level lvl must be re-initialized at @#$MAPP PDS library.
current level
AVZ6524H Existing DMF DIV cache being
Explanation discarded due to unknown object
type (%1)
During initialization the Data Mapping Facility
(DMF) found the DIV linear dataset cache dataset
Explanation
(@#$MAPL) contained information formatted for an
older/different revision level than the server software During initialization the Data Mapping Facility
now supports. The cache must be discarded and re- (DMF) found the DIV linear dataset cache dataset
loaded in order to switch to the current software (@#$MAPL) contains a DMF block area in which
support revision level. garbage or an unknown element block resides. The
cache must be discarded and re-loaded in order to
User response remove the corrupted data block.
DMF cached data maps will be discarded and the DIV

User response
dataset re-initialized at the new support level. DMF
will reload data maps into the cache, as these are read DMF cached data maps will be discarded and the DIV
into storage from the @#$MAPP PDS library. dataset re-initialized. DMF will reload data maps into
the cache as these are read into storage from the
AVZ6522H Existing DMF DIV cache being @#$MAPP PDS library.
discarded due to incomplete
update at last LDS expansion AVZ6525S DMF DIV cache routine %1
invoked within invalid x-mem
Explanation environment
During initialization the Data Mapping Facility

Explanation
(DMF) found the DIV linear dataset cache dataset
(@#$MAPL) could not be placed online because a While processing, a DMF service routine was invoked
DIV expansion operation failed to complete properly within a cross-memory environment which it does
during the prior start-up. The cache must be discarded not support. The DMF service request cannot be
and re-loaded in order to remove any incompletely completed.
allocated logical window areas.
User response
User response
For some service requests, the routine aborts by
DMF cached data maps will be discarded and the DIV generating an S0C3 ABEND. Other service routines
dataset re-initialized. DMF will reload data maps into return an error to the caller, which will likely cause
the cache as these are read into storage from the the originating procedure to fail or ABEND. Contact
@#$MAPP PDS library. Software Support.

AVZ6526S Free of DMF block in DIV cache Explanation
failed - address of block (%1) is
not %2 The command used to invoke the system function was
coded incorrectly. unbalanced parentheses were found
in the input command, which consequently could not
Explanation be understood and processed.
While processing, a request to remove a dmf data
area from DIV cache, a validation error was detected. User response
the data area is not considered valid for the reason
indicated. Reenter the corrected command.
AVZ7001I Syntax error: unmatched
User response quotation mark or apostroph
The removal routine returns an error to the caller,

which may result in failure within the procedure being Explanation
executed. Contact Software Support. The command used to invoke the system function was
AVZ6527H Existing dmf div cache being coded incorrectly. a literal string was not enclosed
discarded. an invalid %1 OBJect within matching quotation marks or apostrophes.
chain was found by %2.
User response
Explanation Reenter the corrected command.
During initialization the data mapping facility AVZ7002I Syntax error: insufficient storage
(dmf) found the DIV linear dataset cache dataset for parsing the command (rsncode)
(@#$MAPL) contains an invalid control block chain.
the cache must be discarded and re-loaded in order to
remove the corrupted data block. Explanation
The command used to invoke the system function
User response could not be parsed because insufficient storage exists
for the command parser.
DMF cached data maps will be discarded and the div
dataset re-initialized. dmf will reload data maps into
the cache as these are read into storage from the User response
@#$MAPP pds library. If the reason code is "1", increase the storage size
of the region, and re-submit the command request.
AVZ6528H Too many virtual directories -
If reason code is "2", ensure that the command was
dataset %1 not processed for path
correctly entered. If the problem cannot be resolved,
%2
Explanation AVZ7003I Syntax error: invalid hex literal
During a refresh of in-storage maps by the data

mapping Facility (dmf), more than 200 individual Explanation
virtual directory datasets were defined. the system The command used to invoke the system function
can process no more than 200 individual datasets could not be parsed because it contains an incorrectly
allocated as virtual directories. formatted hexadecimal literal. the hex literal contains
more than eight (8) hex digits or contains an invalid
User response digit.
The virtual directory definition entry is skipped and the

indicated virtual directory dataset is not placed online User response
Reenter the corrected command.
AVZ7000I Syntax error: unmatched
parenthesis AVZ7004I Syntax error: extraneous or
undefined input at token
The command used to invoke the system function Reenter the corrected command.
could not be parsed because it contains extraneous,
AVZ7009I Syntax error: operand of keyword
undefined operands or duplicate keyword operands.
is invalid or missing
User response
Explanation
The operand coded for the indicated keyword is not
AVZ7005I Syntax error: positional param. valid or was omitted.
parmno of parmname - errdesc
User response
Explanation
The command used to invoke the system function
AVZ7010I Syntax error: errdesc
could not be parsed because it contains an error in
a positional parameter. the full text of the message
explains which parameter number and what portion Explanation
of the command contains the error. the message also
The input was invalid for the reason (errdesc) indicated
contains an explanation as to why the parameter is
in the message.
invalid.

AVZ7050T Variable varname (val) set to "%3"
AVZ7006I Syntax error: required keyword
keyword - missing
Explanation
Explanation This message is used to trace the variable values that
have been parsed from an inbound http transaction
The required keyword was not entered on the
header.
command line.

None.
AVZ7101T Error 01 @(lineno/offset) - too
AVZ7007I Syntax error: required keyword
many nexted html extension
missing - must be on
delimiter pairs on this source line.
Explanation
Explanation
A required keyword was not entered on the command
A syntax error was detected while a text file was
line.
scanned for HTML extension statements. The source
file line number and offset within the line where the
User response error was found is noted in the message.
User response
AVZ7008I keyword
Examine the source file, and correct the html
extension statement syntax error.
Explanation
The variable fields of the message text are: lineno line
This message lists the keywords from which a choice
number in source file where error found loff offset in
must be made.
source line where error detected

AVZ7102T Error 02 @(lineno/offset) - un- User response
matched <%% delimiter in source
line. Examine the source file, and correct the html
Explanation AVZ7106T Error 06 @(lineno/offset) - invalid

token or label precedes statement
A syntax error was detected while a text file was operation keyword.
scanned for HTML extension statements. the source
error was found is noted in the message. Explanation
User response scanned for HTML extension statements. the source
Examine the source file, and correct the html error was found is noted in the message.
AVZ7103T Error 03 @(lineno/offset) - too User response
many tokens, or tokens invalid IN
statement. Examine the source file, and correct the html
Explanation AVZ7107T Error 07 @(lineno/offset) - invalid

statement label syntax.
file line number and offset within the line where the Explanation
error was found is noted in the message. A syntax error was detected while a text file was
User response file line number and offset within the line where the
error was found is noted in the message.
User response
AVZ7104T Error 04 @(lineno/offset) - un-
identified or invalid html extension Examine the source file, and correct the html
statement. extension statement syntax error.
AVZ7108T Error 08 @(lineno/offset) - too
Explanation many operands for statement
type.
User response
AVZ7105T Error 05 @(lineno/offset) - this
statement type must be on a LINE Examine the source file, and correct the html
with no other non-blank text. extension statement syntax error.
AVZ7109T Error 09 @(lineno/offset) - too few
Explanation operands for statement type.

scanned for HTML extension statements. the source Explanation
file line number and offset within the line where the A syntax error was detected while a text file was
error was found is noted in the message. scanned for HTML extension statements. the source
Examine the source file, and correct the html error was found is noted in the message.
AVZ7110T Error 10 @(lineno/offset) - invalid
User response
exit statement operand value. Examine the source file, and correct the HTML
Explanation AVZ7114T Error 14 @(lineno/offset) - number
A syntax error was detected while a text file was of nested if/endif statement pairs
scanned for HTML extension statements. the source exceeds compiler maximum.
Examine the source file, and correct the HTML file line number and offset within the line where the
extension statement syntax error. error was found is noted in the message.

keyword specified - not advance or
User response
no advance. Examine the source file, and correct the HTML
Explanation AVZ7115T Error 15 @(lineno/offset) - else
A syntax error was detected while a text file was without preceding if statement.
Examine the source file, and correct the HTML error was found is noted in the message.
User response
condition name for if statement Examine the source file, and correct the HTML
operand two. extension statement syntax error.
AVZ7116T Error 16 @(lineno/offset) -
Explanation duplicate else statements for
A syntax error was detected while a text file was current if/endif pair.
AVZ7113T Error 13 @(lineno/offset) - variable
User response
name symbol too long - maximum Examine the source file, and correct the HTML
name size is 50 characters. extension statement syntax error.

AVZ7117T Error 17 @(lineno/offset) - endif User response
not preceded by if statement.
Examine the source file, and correct the HTML
Explanation
AVZ7121T Error 21 @(lineno/offset) - number
A syntax error was detected while a text file was of leave statements exceeds
scanned for HTML extension statements. the source compiler maximums.
Explanation
User response A syntax error was detected while a text file was
nested do/enddo groups exceeds User response
compiler maximum nesting levels.
Explanation
A syntax error was detected while a text file was duplicate do statement label name
scanned for HTML extension statements. the source defined.
Explanation
statement should only appear User response
within do/enddo statement group.
Explanation
AVZ7123T Error 23 @(lineno/offset) - label
A syntax error was detected while a text file was not defined in source file
AVZ7120T Error 20 @(lineno/offset) - label User response
name not defined by any
preceding do statement. Examine the source file, and correct the HTML
Explanation AVZ7124T Error 24 @(lineno/offset) -

compiler maximum for label
A syntax error was detected while a text file was names within a source file
scanned for HTML extension statements. the source exceeded.
Explanation AVZ7128T Error 28 @(lineno/offset) - one
or more do statements has no
A syntax error was detected while a text file was matching enddo.
AVZ7125T Error 25 @(lineno/offset) - one or User response
more referenced statement labels
are undefined in source file. Examine the source file, and correct the HTML
Explanation AVZ7129T ERROR 29 @(lineno/offset) -
ADDITIONAL ERRORS WERE
A syntax error was detected while a text file was DETECTED IN SOURCE FILE -
scanned for HTML extension statements. the source FIRST 5 REPORTED.
Explanation
compiler area overflow - source User response
fIle too complex.
Explanation
AVZ7130T ERROR 30 @(lineno/offset)
A syntax error was detected while a text file was - INVALID SWSINFO()
scanned for HTML extension statements. the source PSEUDO=FUNCTION OPERAND
file line number and offset within the line where the VALUE.
Explanation
User response
Examine the source file, and correct the HTML scanned for HTML extension statements. The source
extension statement syntax error. file line number and offset within the line where the
AVZ7127T Error 27 @(lineno/offset) - one error was found is noted in the message.
or more if statements has no
matching endif. User response
Explanation extension statement syntax error.
A syntax error was detected while a text file was AVZ7131T ERROR 31 @(lineno/offset)
scanned for HTML extension statements. the source - HTXINDEX. STEM SYNTAX
file line number and offset within the line where the INVALID.
Explanation
User response
Examine the source file, and correct the HTML scanned for HTML extension statements. The source

AVZ7132T ERROR 32 @(lineno/offset) - FOR
User response
'HTXINDEX.LABEL' - THE 'LABEL' Examine the source file, and correct the HTML
NAME IS NOT DEFINED. extension statement syntax error.
AVZ7136T ERROR 36 @(lineno/offset) - AN
Explanation UNMATCHED /RULE STATEMENT
A syntax error was detected while a text file was WAS ENCOUNTERED.
AVZ7133T ERROR 33 @(lineno/offset) -
User response
INVALID SWSPARM() PSEUDO- Examine the source file, and correct the HTML
FUNCTIONOPERAND VALUE. extension statement syntax error.
Explanation STORAGE ALLOCATION FAILURE
A syntax error was detected while a text file was DURING RULE PROCESSING.
User response
INVALID TOUPPER() PSEDUO- Examine the source file, and correct the HTML
FUNCTIONOPERAND VALUE. extension statement syntax error.
AVZ7138T ERROR 38 @(lineno/offset) - ONE
Explanation OR MORE RULE STATEMENTS HAS
A syntax error was detected while a text file was NO MATCHING /RULE.
User response
NESTED RULE STATEMENTS ARE Examine the source file, and correct the HTML
NOT ALLOWED. extension statement syntax error.
AVZ7139T ERROR 39 @(lineno/offset) User response
- ENABLEMENT FAILED FOR
EMBEDDED RULE. Examine the source file, and correct the HTML
Explanation AVZ7143T ERROR 43 @(lineno/offset) -

EMBEDDED RULES CANNOT BE
A syntax error was detected while a text file was EMPTY.
User response scanned for HTML extension statements. The source
AVZ7140T ERROR 40 @(lineno/offset) - / User response
*FILE SECTIONS ARE NOT
ALLOWED WITHIN EMBEDDED Examine the source file, and correct the HTML
RULES. extension statement syntax error.
Explanation TARGET OF ASSIGNMENT MUST
BE L-VALUE.
error was found is noted in the message. The target
Examine the source file, and correct the HTML of an assignment statement must be a valid L-Value
extension statement syntax error. (either a variable name or a complex expression that
AVZ7141T ERROR 41 @(lineno/offset) - can evaluate at runtime to the name of a variable).
DATE(?) OPERAND INVALID OR
NOT SPECIFIED. User response
Explanation extension statement syntax error.
A syntax error was detected in the DATE(?) HTML AVZ7145T ERROR 45 @(lineno/offset) -
extension function. Refer to the documentation for the IMS AUTO-HTML VARIABLE
correct options. REFERENCE IS BADLY FORMED

Examine the source file, and correct the HTML A syntax error was detected while a text file was
extension statement syntax error. scanned for HTML extension statements. The source
AVZ7142T ERROR 42 @(lineno/offset) - file line number and offset within the line where the
TIME(?) OPERAND INVALID OR error was found is noted in the message. A reference
NOT SPECIFIED. to an IMS Auto-HTML facility runtime variable
(SWSSETFO, SWSFOCUS, SWSINMAP, or SWSCNVID)
contains additional/extraneous characters.
Explanation
A syntax error was detected in the TIME(?) HTML User response
extension function. Refer to the documentation for the
correct options. Examine the source file, and correct the HTML

AVZ7146T ERROR 46 @(lineno/offset) - ! User response
OPTIONS STATEMENT INVALID
extension statement syntax error. If the HTML
Explanation extension file was generated by the IMS Auto-HTML
A syntax error was detected while processing an ! facility, re-extract the MFS source map and re-
OPTIONS statement within the HTX source file. The generate the HTML file.
line number and offset within the line where the AVZ7150T /*UTILITY STMT - errtext (funcode)
error was found is noted in the message. A more
complex message indicating the exact error found in
the !OPTIONS statement may be present in the trace. Explanation
During event procedure enablement, a /*UTILITY
User response section was not enabled due to the error given.

extension statement syntax error. User response
AVZ7147T ERROR 47 @(lineno/offset) - ! Correct the error, and re-enable the event procedure.
OPTIONS STATEMENT OUT OF The variable fields of the message text are: text error
ORDER text funcc function code
AVZ7151T /*UTILITY STMT - errmsg -
Explanation statement
A syntax error was detected while processing an !
OPTIONS statement within the HTX source file. Explanation
Runtime !OPTIONS must appear before any other HTX
executable or insert statement within the source file. During execution of a /*UTILITY statement, the
statement was determined to be invalid or non-
executable.
User response
Examine the source file, and correct the HTML User response
If the statement text is invalid, correct the statement
AVZ7148T ERROR 48 @(lineno/offset) - text. Otherwise, contact Software Support.
INVALID ENVIRONMENT FOR
STATEMENT AVZ7152T UTILITY FUNCTION funcode NOT
ENABLED. ASSOCIATED MODULE
(modname) NOT FOUND IN THE
Explanation %3 LIBRARY.
A syntax error was detected while processing a
statement. Some statements are only valid in either Explanation
the HTTP Web Server or Data Virtualization Manager
server. This statement was encountered in an While attempting to enable a utility function, the
incorrect environment. module associated with the function was not found in
the S__RPCLB library.
User response
User response
extension statement syntax error. The associated vendor library must be concatenated
with the S__RPCLB library.
IMSATTR STATEMENTS NO AVZ7153T ACCESS TO UTILITY ROUTINES IS
LONGER SUPPORTED NOT AUTHORIZED.
A syntax error was detected while processing a Your license code does not authorize you to execute
statement. The deprecated IMSATTR statement is no utility routines.
longer supported by this version of the server.
User response STMT NOT ALLOWED IN THIS
FILE.
AVZ7160T LINE lineno - HTML EVALUATION Explanation
ERROR (errdesc) - additinfo
A runtime error was detected while a text file was
being processed by the HTML extension processor.
Explanation The source file line number where the error was
While processing file information that contains HTML detected is noted in the message. Note that an HTX
extensions, evaluation of a statement failed. executable RESCAN statement may also generate
this error because RESCAN is only allowed where
embedded rules are authorized.
User response
Examine the source file to determine why the error User response
occurred.
The server aborts processing of the current file and
AVZ7161E ABEND abcode, REASON rsncode generates an error message output page (HTML or text
DURING HTX PROCESSING form). The HTML expansion request fails, with RC=16.
Remove the rule or RESCAN statement that caused
Explanation this condition to be raised, or authorize execution
of embedded rules within this file. You authorize
While processing HTML extension processing, an embedded rule execution by (1) requesting the file via
abend occurred. the /*FILE process section or via /*WWW PATH() (from
the HFS) and (2) specifying the RULE(YES) keyword
User response for /*FILE.
Examine the source file to determine why the error AVZ7165T RUNTIME ERROR (LINE lineno)
occurred. Check for other messages that may indicate - ASSIGNMENT STMT FAILED -
the cause of the error. errdesc - lval
AVZ7162E var
Explanation
Explanation A runtime error was detected while a text file was
being processed by the HTML extension processor.
This message is used internally by OPHTXPR to build The source file line number where the error was
abend error reporting pages (HTML or text form). detected is noted in the message. A variable
assignment statement failed for the reason indicated
User response in the message.
None. This message is for internal use only.

User response
AVZ7163E ABEND abcode, REASON rsncode
DURING OPHTXPR ABEND If the message indicates that the LValue (lval) must be
RECOVERY a global variable, ensure that the original assignment
statement refers only to a global variable. These
include GLOBAL., GLVEVENT., or .GLVSTATE. variables.
Explanation Otherwise, check for other messages that might
While attempting to recover from a previous abend, indicate the cause of failure.
the second-level abend intercept was entered in AVZ7166T <%RULE%> EXECUTION MUST
OPHTXPR. NOT DRIVE RECURSIVE
<%RULE%> EXECUTION
User response
Examine the source file to determine why the abend Explanation
occurred. Check for other messages that may indicate A runtime error was detected while a text file was
the cause of the error. being processed by the HTML extension processor.
AVZ7164T RUNTIME ERROR (LINE lineno) - The HTML extension processor is about to execute
EMBEDDED RULES AND RESCAN an embedded rule, but an embedded <%RULE%>

execution is already underway. This type of recursion the HTTP response code to 500 (server error) and the
is not allowed. error code to 61.
AVZ7170T LINE lineno - EXIT OPTION, option,
User response IGNORED BECAUSE <%RULE%>
The current (nested) <%RULE%> section is bypassed, PROCESSING NOT ENABLED
and HTML extension processing of the file is aborted.
Explanation
AVZ7167E ABEND abcode, REASON rsncode
DURING HTX PROCESSING OF While processing file information that contains
EMBEDDED ruletype RULE HTML extensions, an <%EXIT%> statement with the
indicated option was executed. The option is being
Explanation ignored because HTML extension processing was
requested via an interface that does not support the
While processing HTML extensions, an abend occurred execution of embedded rules.
while executing an embedded rule.
User response
User response
The EXIT option is ignored.
Examine the source file to determine why the error
occurred. Check for other messages that may indicate AVZ7171T LINE lineno - !OPTIONS statement
the cause of the error. - errdesc
AVZ7168T LINE lineno - EXIT-FLUSH

Explanation
STATEMENT EXECUTED - RESCAN
AND NEW RULE MATCHES While parsing an !OPTIONS statement a syntax error
DISABLED was found. This message is traced to provide a
detailed reason for the failure. HTX processing of the
Explanation file fails with error code 46.
While processing file information that contains HTML

User response
extensions, an <%EXIT FLUSH%> statement was
executed. This causes immediate exit from HTML Correct the !OPTIONS statement and retry
extension file tailoring and also sets controls so that
additional RESCAN or rule matches are inhibited. AVZ7172T ERROR 72 @(lineno/offset) -
RESULTSET OPERAND INVALID OR
NOT SPECIFIED.
User response
The server will flush (complete) the transaction Explanation
without delay.
A syntax error was detected in the RESULTSET HTML
AVZ7169T LINE lineno - RESCAN STATEMENT extension function. Only values of 1 or 2 are supported
OPERAND INVALID - reason - at this time.
VALUE=value
User response
Explanation
While processing file information that contains extension statement syntax error.
HTML extensions, a <%RESCAN x%> statement was
executed. The RESCAN URL operand is invalid for AVZ7178T diagtext
the reason reported. If the RESCAN URL value was
partially validated, it appears in the message (value); Explanation
if it was not partially validated, the value string will be
This message is used to dump out various internal
null.
work areas into the trace. It is triggered by setting a
diagnostic parameter or control.
User response
The server uses the value SYSTEM/ERROR/500 as a
replacement for the invalid RESCAN URL. It also sets
User response refreshing the data map after the HTML generation is
complete.
If there are other messages indicating an error, use
this message in conjunction with them to determine AVZ7183E /*EXECIMS STMT - errtext
the cause of the problem.
AVZ7179E DATA MAPPING - map FIELD field Explanation
IS TOO LONG During event procedure enablement, a /*EXECIMS
section was not enabled due to the error given.
Explanation
During processing of a data map, a field was defined User response
that was too long for processing. Fields of 3074 bytes Correct the error, and re-enable the event procedure.
are currently the longest fields allowed.
AVZ7184T /*EXECIMS STMT - errmsg -
statement
User response
Recreate the map with shorter fields, or disable this Explanation
field.
During execution of an /*EXECIMS statement, the
AVZ7180E /*EXECSQL STMT - errtext statement was determined to be invalid or non-
executable.
Explanation
During event procedure enablement, a /*SQL section User response
was not enabled due to the error given. If the IMS statement text is invalid, correct the IMS
statement text. Otherwise, contact Software Support
User response with this problem.
Correct the error, and re-enable the event procedure. AVZ7185E UNABLE TO OBTAIN INPUT
STORAGE WORK AREA. LENGTH
AVZ7181T /*EXECSQL STMT - errmsg - %1
statement
Explanation
Explanation
While processing an input request, there was
During execution of an /*EXECSQL statement, the insufficient storage to build the input message based
SQL statement was determined to be invalid or non- upon the the product Mapping Facility definition of the
executable. input map.

If the SQL statement text is invalid, correct the SQL This may be caused by an error in the map definition.
statement text. If the problem cannot be resolved, The input map may contain a field with an erroneous
contact Software Support. offset or length. The total length of the input message
AVZ7182T HTML MEMBER NAME MISSING OR cannot exceed 32,702 bytes.
INVALID. DATA MAP: map, HTML AVZ7186E REQUIRED HTML VARIABLE
MEMBER: memname MISSING. NAME=varname
During execution of an output file SEND, the HTML While processing an input URL, the /*EXECIMS expects
member name was not specified in the data map or certain query variables: SWSINMAP, SWSCNVID and
the HTML member name was invalid. PFKIN. One or more of these variables was missing.

The error is reported as a system error aux on the This may be caused by an error in the coding of
Web browser. This problem may be correctable by the HTML. The SWSINMAP variable contains the

input map name required to process this URL. The AVZ7191T /*TSOSRV STMT - errmsg - cmdtext
SWSCNVID variable contains the conversation id
required to process conversational IMS transactions.
Explanation
The PFKIN variable contains the interrupt key (ENTER,
PF01...PF24). During execution of an /*TSOSRV statement, the TSO
command statement was determined to be invalid or
AVZ7187E /*EXECCICS STMT - errtext
non-executable.

During event procedure enablement, an /*EXECCICS
If the TSO command text is invalid, correct the
command statement text. If the problem cannot be
User response
AVZ7192T /*TSOSRV STMT - errmsg - cmdtext
AVZ7188T /*EXECCICS STMT - errmsg - Explanation
statement
During execution of an /*TSOSRV statement, the TSO
command statement was determined to be invalid or
Explanation non-executable.
During execution of an /*EXECCICS statement, the
statement was determined to be invalid or non- User response
executable.
If the TSO command text is invalid, correct the
command statement text. If the problem cannot be
User response resolved, contact Software Support.
If the CICS statement text is invalid, correct the CICS AVZ7195E rsname.rulename, /*PROGRAM
statement text. Otherwise, contact Software Support STMT - errtext
with this problem.
AVZ7189T TEMPORARY MAP map USED FOR Explanation
HTML FILE SELECTION
During event procedure enablement, a /*PROGRAM
Explanation
During execution of an output file SEND, the output User response
file name was selected from the temporary map name.
Permanent maps will arbitrarily use the file associated
with the SWSAHTML ddname. AVZ7200T HTTP-RECV: operdesc

For the /*EXECIMS and /*EXECCICS rule sections, an Issued if TRACEURLREAD option is on, this message
HTML file output from the HTML data set name indicates that the reception of an inbound HTTP
stored within the specified map name will be selected. request is being processed and indicates the progress,
This information is provided for auditing and control so far.
purposes. No action may be required.
AVZ7190E /*TSOSRV STMT - errtext User response
None. This message indicates processing performed
Explanation during HTTP request receive operations.
During event procedure enablement, a /*TSOSRV AVZ7201T HTTP-RECV: RECEIVED reclength,
section was not enabled due to the error given. TOTAL totlength
User response
Issued if TRACEURLREAD option is on, this message A pending SSL connection could not be accepted by
indicates that the reception of an inbound HTTP the server due to a validation failure or a failure within
request is being processed and indicates the progress. the SSL connection handling engine. This error reports
the failure.
User response Note that there are two return codes in the message.
rcd1 represents the SSL acceptance return code, and
rcd2 represents the LE/370 enclave manager return
during HTTP request receive operations.
code.
AVZ7202T HTTP-RECV: HTTP REQUEST
feedback contains the LE/370 enclave termination
HEADERS - LENGTH length,
feedback codes.
DELIMITER dlmtr
User response
Explanation
Issued if TRACEURLREAD option is on, this message
termination, and resolve the problem, if possible.
indicates that the reception of an inbound HTTP
request is being processed and indicates the progress, AVZ7206T SSL READ FAILED RC=rcd1
so far. REAS=rsncode - ENCLAVE RC=rcd3
FEEDBACK=(feedback)
User response
Explanation
during HTTP request receive operations. A RECEIVE request on an SSL connection failed due
to a validation failure or a failure within the SSL
AVZ7203T HTTP-RECV: HTTP CONTENT-
connection engine. This error reports the failure.
LENGTH: clval
Note that the message contains two return codes,
rcd1 represents the SSL read return code, and rcd2
Explanation
represents the LE/370 enclave manager return code.
feedback contains the LE/370 enclave termination
feedback codes.
request is being traced.

termination, and resolve the problem, if possible.
AVZ7207T SSL WRITE FAILED RC=rcd1
AVZ7204T VARIABLE WWW.varname NOT
REAS=rsncode - ENCLAVE RC=rcd2
BUILT - reason
FEEDBACK=(feedback)
Explanation
Explanation
A WWW. event variable was not built during URL
A SEND request on an SSL connection failed due to a
parsing for the reason indicated.
validation failure or a failure within the SSL connection
engine. This error reports the failure.
User response
Note that the message contains two return codes;
Correct the HTML input form used to transmit the rcd1 represents the SSL read return code, and rcd2
inbound data, and re-submit. represents the LE/370 enclave manager return code.
AVZ7205T SSL ACCEPT FAILED - RC=rcd1 feedback contains the LE/370 enclave termination
REAS=rsncode - ENCLAVE RC=rcd2 feedback codes.
FEEDBACK=feedback)

Check for other messages indicating the cause of the A attempt to establish an SSL connection failed due
termination, and resolve the problem, if possible. to a validation failure or a failure within the SSL
connection handling engine. This error reports the
AVZ7208T SSL CLOSE FAILED RC=rcd1 failure.
REAS=rsncode - ENCLAVE RC=rcd2
FEEDBACK=(feedback) Note that the message contains two return codes; rcd1
represents the SSL acceptance return code, and rcd2
represents the LE/370 enclave manager return code.
Explanation
feedback represents the LE/370 enclave termination
A CLOSE request on an SSL connection failed due to a
feedback codes.
validation failure or a failure within the SSL connection
engine. This error reports the failure.
User response
Note that the message contains two return codes;
rcd1 represents the SSL close return code, and rcd2 Check for other messages indicating the cause of the
represents the LE/370 enclave manager return code. termination, and resolve the problem, if possible.
feeback contains the LE/370 enclave termination AVZ7212T RELEASE OF SPECIALLY SIZED
feedback codes. watype AT addr1 FOR OPPR AT
addr2 FAILED WITH RC=rcode
User response
Explanation
termination, and resolve the problem, if possible. During end-of-transaction cleanup, an oversized SEF
work area could not be freed and has been orphaned.
AVZ7209T var1, var2 … var5 The oversized work area had been allocated during
execution of the previous transaction through the use
Explanation of the WORKSIZE() of QUEUESIZE() keywords of a
WWW rule. Oversized areas are only freed when thread
The message is used to issue various warning
reuse is in effect, since they are otherwise released by
messages when unusual conditions are detected
end of task processing.
during the parse of an inbound HTTP request.
The message contains two addresses; addr1
represents the SEF work area address, and addr2
User response
represents the owning process block address.
None.
AVZ7210T SERVER VARIABLE varname User response
SKIPPED BY GLVSTATE. Check for other messages indicating the cause of
PROCESSING the termination, and resolve the problem, if possible.
Contact Software Support if this error cannot be
Explanation resolved locally.
The indicated inbound HTML query variable or HTTP AVZ7213T SSL READ: desc
cookie variable was not processed as expected to re-
create a GLVSTATE. information set. Explanation
User response
Processing of the inbound HTTP request continues; request is being traced. This message is generated by
however, subsequent processing of the transaction the SSL receive routines.
may encounter problems in the absence of the
GLVSTATE. set. User response
AVZ7211T SSL CONNECT FAILED - RC=rcd1 None. This message indicates processing performed
REAS=rsncode - ENCLAVE RC=rcd2 during HTTP request receive operations.
FEEDBACK=(feedback)
AVZ7214T MAXIMUM NUMBER OF QUERY
VARIABLES(maxno) EXCEEDED -
INBOUND REQUEST CANNOT BE Explanation
PARSED
Explanation request is being traced.
This message indicates that the inbound HTTP request
contains more query variable name/value pairs than User response
the server is able to parse. The maximum number of
variables that can effectively be handled is given in the None. This message indicates processing performed
message. during HTTP request receive operations.
AVZ7218T HTTP-RECV: HTTP CONTENT
User response CHUNK LENGTH: val
The server aborts parsing of the current HTTP request
and responds with an HTTP 400 status message, Explanation
indicating that the inbound request message is invalid. Issued if TRACEURLREAD option is on, this message
In order to correct the problem, you will need to indicates that the reception of an inbound HTTP
redesign your application so that it transmits fewer request is being traced.
query variables with any single inbound request.
AVZ7215T CANNOT DECODE DBCS QUERY User response
DATA data
Explanation
AVZ7230T WEB BUFFER FLUSH ATTEMPTED
This message indicates that the inbound HTTP request IN X-MEM MODE BY
contains an ASCII encoded string (data) that could not modname+offset
be decoded by the server and converted to EBCDIC.
Explanation
User response
A Web transaction program has issued a flush request
The query data is set to include only the portion of to transmit outbound response buffers. The caller is
the string that could be converted to EBCDIC. Set operating in cross-memory mode, and the request
the DECODETRACE parameter to YES, and rerun the cannot be serviced. The buffer flush request is
transaction. Contact Software Support if you cannot ignored.
determine the reason (invalid ISO-2022-JP or Shift-
JIS encoding) for the failure.
User response
AVZ7216T SSL ACCEPT LEFT count
UNCONSUMED LOOK-AHEAD Check for other messages that might indicate the
BYTES - REJECTING SESSION cause of the error.
AVZ7231T SWSSEND REQUESTS EXCEPT
Explanation PURGE OR FLUSH ARE INVALID
FOLLOWING SWSFILE(SEND)
This message indicates that the SSL accept processing REQUEST
completed normally, except that some (count)
received bytes were unconsumed from the look-ahead
receive buffer during acceptance processing. Since Explanation
SSL Accept processing involves real-time certificate A Web transaction program has issued a request to
and key negotiation, no look-ahead bytes should have buffer additional outbound response data, but this
remained. request follows completion of an SWSFILE(SEND)
operation. Because SWSFILE(SEND) has generated
User response HTTP response headers specifying total response size,
no additional data can be output unless the file-send
This is probably due to a logic error in the server. request is first purged from the output buffers or
Contact Software Support. flushed to the client.
AVZ7217T HTTP-RECV: HTTP TRANSFER-
ENCODING: val

User response Connection: Close header to guard against problems
that might be associated with sending the incorrect
Check for other messages that might indicate the message body length value.
cause of the error, and correct the problem.
AVZ7232T HTTP RESPONSE BUFFER LIMIT User response
(limit) EXCEEDED - SWSSEND
WILL ISSUE USER ABEND X'722' Ensure that the user-generated Content-Length HTTP
header does not include the length of the user-
generated HTTP headers and correctly represents the
Explanation length of the data being transmitted.
The total number of concurrently held output buffers AVZ7250E OPISTBRU FUNCTION
for a single HTTP response has exceeded the TERMINATED: rsn
MAXHTTPRESPBUFFERS limit. This may be due
to a runaway transaction procedure or simply to
unexpectedly large output. Explanation
A product display function was invoked improperly
User response
The SWSSEND API routine issues a user abend X'722' User response
to begin cancellation of the Web transaction subtask. Correct the invocation parameter list, and re-run.
If your program is expected to generate excessive
output, raise the MAXHTTPRESPBUFFERS limit. AVZ7251T UNKNOWN OR INVALID COOKIE
FOUND. errdesc : cookie
AVZ7233T HTTP RESPONSE BYTE LIMIT
(limit) EXCEEDED - SWSSEND
WILL ISSUE USER ABEND Explanation
X'722'(1826) During execution of OPISTBRU, an unrecognizable or
unknown cookie was received.
Explanation
The total number of bytes output as part User response
of a single HTTP response has exceeded the None. This is a warning message. The unknown cookie
MAXHTTPRESPBYTES limit. This may be due to is ignored, and the product defaults are used.
a runaway transaction procedure or simply to
unexpectedly large output. AVZ7252T ONE OR MORE INVALID COOKIE
VALUE FOUND. cfield : val
User response
Explanation
The SWSSEND API routine issues an user abend
X'722' to begin cancellation of the Web transaction During execution of OPISTBRU, one or more cookie
subtask. If your program is expected to generate fields were defaulted because the value of the cookie
excessive output, raise the MAXHTTPRESPBYTES field was invalid.
limit.
AVZ7240T USER-SPECIFIED CONTENT- User response
LENGTH DIFFERENT THAN None. This is a warning message. The invalid cookie
CALCULATED LENGTH. USER field is ignored, and the product default for the field is
LENGTH = length, CALCULATED used.
LENGTH = length
AVZ7253T INVALID COOKIE FORMAT count
INVALID VARIABLES FOUND:
Explanation value
A Web transaction program has created a Content-
Length HTTP header with a length that is different than Explanation
the calculated length of the data being transmitted.
The product Server will use the content length During execution of OPISTBRU, the stated number of
specified by the user. If persistent session support cookie fields were defaulted because the cookie field
(KEEPALIVE) is enabled, the server will generate a was of invalid format. A 7252T message is issued for
each invalid cookie field prior to the issuing of this Explanation
message.
The subsystem name coded is not valid.
User response
User response
None. This is a warning message. The invalid cookie
field(s) are ignored, and the product default(s) for the Subsystem names must be four characters long and
field(s) are used. must begin with the correct product ID. The fourth
character can be any character in the range A-Z.
AVZ7254T TIMESTAMP UNRECOGNIZABLE IN
RFC1123, RFC850 OR ANSI C AVZ7302I Parser routine (OPSXPR) failed
ASCTIME() FORMAT time with RC=rcode
While parsing an HTTP request or response header, A host command statement was invalid because the
the timestamp value could not be parsed to yield a general text parsing routines failed without returning a
valid timestamp. This may be a browser dependency reason for the failure.
beyond the server's control.
User response
User response Contact Software Support.
None. The server assumes no value is specified for the AVZ7303S object IS AN INVALID OBJECT FOR
corresponding request or response header. verb
AVZ7255T VALUE OF varname IS
IMPROPERLY ENCODED: reason Explanation
You have entered an invalid command / object
Explanation combination for the verb from the SAVZ statement.
While parsing an HTTP request, an SWSECRET_
query value was detected. The server cannot decrypt User response
the information for the reason indicated. Note that
query variables sent out to a browser before a Correct the command, and rerun.
product restart become stale and cannot be decrypted AVZ7304I operand KEYWORD MUST BE
following a restart. SPECIFIED FOR verb entity
STATEMENT
User response
None. The server rejects the badly formed or Explanation
invalid query variable and subsequently rejects the A host command statement was invalid because an
transaction with a 400 (bad request) HTTP status operand that is required for this type of command
message. statement was omitted.
AVZ7300I Invalid command syntax:
syntaxerr User response
Correct the command statement, and re-submit.
Explanation
AVZ7305I operand KEYWORD MUST reason -
A host command statement was invalid or could not SHOULD BE opertype
be parsed for the reason indicated. The error was
detected during initial command syntax scanning.
Explanation
User response A host command statement was invalid because an
operand value was invalid.
Correct the command statement and re-submit.
AVZ7301S subsys is an invalid subsystem User response
name

AVZ7306I EITHER operand OR operand Explanation
KEYWORD MUST BE SPECIFIED
FOR verb entity STATEMENT The command you have coded is unknown.

A host command statement was invalid because Enter a correct command, and rerun.
neither of the indicated operands was coded. At least AVZ7311S cmdname subsystem subsys is not
one is required. active

Correct the command statement, and re-submit. The indicated subsystem is not running. The address
AVZ7307I operand KEYWORD INVALID FOR SAVZ function cannot continue.
verb entity STATEMENT
User response
Explanation Start the subsystem (or use the SUBSYS command to
A host command statement was invalid because an identify another subsystem), and rerun the command.
operand was coded that is not valid for the command AVZ7312S verb entity STATEMENT FAILED
statement type. WITH RC = rcode

Correct the command statement, and re-submit. The requested operation failed severely.
AVZ7308I ONLY operand KEYWORD
ALLOWED FOR verb entity User response
STATEMENT
There is probably some sort of internal error. Contact
Software Support.
Explanation
AVZ7313S Authorization check failed for verb
A host command statement was invalid because an entity statement
operand was coded that cannot be used for this type
of command. Code only the single keyword operand
indicated. Explanation
A host command statement authorization check
User response routine found that the current user is not authorized
to execute the command statement. Access to execute
Correct the command statement, and re-submit. the statement is denied.
AVZ7309I operand KEYWORD MUST BE value
additinfo User response
Check the variables of the error message text for the
Explanation command statement whose access is denied. Ensure
A host command statement was invalid because an that the current user has the required access. Contact
operand was not valid. The allowed format for the your security systems administrator for further help, if
keyword operand is given. necessary.
AVZ7314S parmname is not a valid product
User response parameter name

Explanation
AVZ7310S cmdname IS AN INVALID cmdtype
COMMAND The parameter name is not a valid, recognized product
parameter.
Correct the parameter name, and rerun. The attempt to define the file fails. Add a DD
statement to the product start-up JCL for the indicated
AVZ7315S parmval is not a valid value for
file, and restart the product.
parmname
AVZ7320I DSNAME(dsname) MUST BE A
Explanation PDS(E) DATA SET
The parameter value is not valid for this parameter.

Explanation
User response The indicated data set is not a PDS or PDSE data set.
Correct the value, and rerun.

User response
AVZ7316E entity value does not exist The attempt to define the file or ruleset fails. Change
the DSNAME() keyword to correct the error.
Explanation
AVZ7321I RULESET indicator NOT rsname
The entity defined by name is not yet defined;
therefore, it cannot be modified.
Explanation
User response The indicated ruleset definition was processed.
indicator indicates whether a ruleset was DEFINED or
Either define the entity or remove the MODIFY.
MODIFIED.
AVZ7317E entity value is already defined
User response
Explanation
This message logs definitions of or changes to SEF
The indicated entry has already been defined. ruleset definitions.
AVZ7322H jobname HAS QUEUED
User response RULESET(rsname) indicator FOR
Determine which definition is correct, and rerun. PROCESSING BY SEF
AVZ7318S INVALID UPDATE ATTEMPT FOR Explanation

entity
The job or user indicated issued a critical configuration
change command that was successfully scheduled for
Explanation
processing by the SEF task. The SEF task will indicate
An invalid update attempt has been detected. the outcome of the request.
indicator indicates definition or modification.
User response
Remove the keywords in error, and rerun the User response
command.
Information only. This message is sent to the hardcopy
AVZ7319I DDNAME ddname is not allocated console log.
to product address space
AVZ7323H SUPERVISOR STATE REQUIRED
FOR verb entity COMMAND
Explanation
The indicated ddname is not allocated to the product Explanation
address space.
The indicated command can only be processed by
a real started-task copy of the product because
supervisor state is required to perform the indicated
action.

User response AVZ7328E operand VALUE val INVALID
- errdesc FOR verb entity
Information only. This message is sent to the hardcopy STATEMENT
console log.
AVZ7324I operand KEYWORD CONTAINS Explanation
INVALID CHARACTER(S) AT
OFFSET offset OF THE STRING A host command statement was invalid because the
specified parameters is invalid
Explanation
User response
A host command statement was invalid because
an operand was not valid. An invalid character or Correct the command statement, and re-submit.
combination of characters was found at the indicated AVZ7329S Not configured for verb entity
offset within the operand string. statement.

Correct the command statement, and re-submit. None.
AVZ7325E operand IS INVALID IN
COMBINATION WITH operand FOR User response
verb entity STATEMENT
Explanation AVZ7330S rsname RULESET DEFINITION

REJECTED - additinfo
A host command statement was invalid because the
specified parameters conflict.
Explanation
User response The ruleset definition is invalid because of the
indicated condition. The definition is discarded.
AVZ7326E operand MUST BE SPECIFIED IN User response
COMBINATION WITH operand FOR
verb entity STATEMENT Correct the ruleset definition and restart the server
AVZ7331S rsname SHARED FILE DEFINITION
Explanation REJECTED - additinfo
A host command statement was invalid because a

required parameter was not specified Explanation
The file definition is invalid because of the indicated
User response condition. The definition is discarded.

User response
AVZ7327E operand VALUE MUST BE errdesc
THAN operand FOR verb entity Correct the shared file definition and restart the server
STATEMENT AVZ7333T Authorization check failed for verb
entity statement
Explanation
A host command statement was invalid because the Explanation
specified parameters conflict. A host command statement authorization check
routine found that the current user is not authorized
User response to execute the command statement. Access to execute
the statement is denied.
Check the variables of the error message text for the Remove the update attempt for the variable.
command statement whose access is denied. Ensure
AVZ7404T GLVSTATE.setname MUST BE
that the current user has the required access. Contact
ACTIVE BEFORE UPDATE TO
your security systems administrator for further help, if
varname
necessary.
AVZ7400T varname INVALID GLVSTATE. Explanation
VARIABLE - rsn additinfo
The indicated variable does not belong to an active
named state information set. The GLVSTATE. group has
Explanation
expired or has never been created.
The indicated variable is not a valid GLVSTATE. prefix
variable. See information on the automated state User response
management facility for information on proper variable
name formats. Create the set before attempting to set the variable.
AVZ7405T varname REQUIRES A NUMERIC
User response VALUE - FOUND val
Correct the variable name, and rerun the exec or
program. Explanation
AVZ7401T setname DOES NOT EXIST AND The indicated variable requires a numeric value in
CANNOT BE service order to update its value.

An attempt to perform a control operation on a named Correct the variable specification, and rerun the exec
state information set failed because the set is not or program.
known to the system.
AVZ7406T varname ADJUSTED FROM val TO
MINIMUM VALUE OF minval for %4
User response
The current request is ignored. Explanation
AVZ7402T val IS NOT A VALID VALUE FOR The indicated variable was adjusted because the value
THE varname VARIABLE being set was lower than the minimum. The minimum
value is used, instead.
Explanation
User response
The value indicated is not a valid value type for the
variable identified. Correct the variable specification, and rerun the exec
or program.
User response AVZ7407T varname1 IN varname2 MUST BE
ALPHAMERIC, BEGIN ALPHA OR
Correct the variable value, and rerun the exec or
AN INTEGER 0-N
program.
AVZ7403T setname IS A READ-ONLY Explanation
VARIABLE AND CANNOT BE
UPDATED The indicated variable is not valid for use as a
GLVSTATE. user-assigned name. In GLVSTATE.name,
name must be less than eight (8) bytes in
Explanation
length, begin alphabetic, and consist of only letters
The update attempt for the named state information and numbers. The read-only variables, GLVEVENT.0
set failed because the indicated variable is read-only. through GLVEVENT.n, are also valid but do not
designate a named state variable set.

Correct the variable specification, and rerun the exec During Web transaction initialization, an HTML query
or program. variable or HTTP request header cookie was found
with a name beginning with SWSSTATE_xxxxxxxx or
AVZ7408T qualifier ALREADY EXISTS SWSTOKEN_xxxxxxxx. All query variables and cookies
with names in this form are reserved for automated
Explanation processing of state information.
The indicated GLVSTATE.name group already exists.
An attempt was made to assign NEW to the control User response
variable. Such an attempt is taken as an unconditional The server bypasses built-in handling for this
create-set request for a set that must not previously variable, which may result in improper sessions state
exist. management activities. A variable in this form is also
rejected if the xxxxxxxx portion is invalid. To be valid,
User response the customer-assigned name must be 1 to 8 bytes in
length; begin with an alphabetic character; and contain
The NEW create-set request is rejected with an error.
only alphabetic characters, the digits 0 through 9, and
Interrogate GLVSTATE.name before issuing a request if
the underbar character.
a previously created set might exist.
AVZ7412T varname BYPASSED BY ASMF
AVZ7409T ++++++ reqtype varname
- DUPLICATE GLVSTATE.setname
Diagnostic WWST Trace ++++++
SET ALREADY EXISTS
An internal-use diagnostic trace is being produced.
During Web transaction initialization, an HTML query
Various internal state-related control blocks will be
variable and/or HTTP request header cookie that
formatted and written to Trace Browse.
contains built-in management information for a
GLVSTATE. information set was found. Information for
User response this GLVSTATE. set has already been received from
another query variable or cookie within this inbound
None. For use by Software Support.
request.
AVZ7410T SERVER TOKEN CREATE/DELETE
SERVICE FAILED RC=rcode - User response
GLVSTATE.setname UPDATE WILL
FAIL The server bypasses built-in handling for this
variable and uses only the first GLVSTATE. restoration
information. Note that this can occur if you include
Explanation the same GLVSTATE.xxxxxxxx information in both an
An internal service failed to create/delete a server HTML form field and an HTTP cookie or if the browser
token needed to manage a GLVSTATE. variable set. transmits two HTTP cookies with the same name.
The current GLVSTATE. update request will be failed in
AVZ7413T VARIABLE varname DOES NOT
one of two ways: (1) as though the update were to an
CONTAIN A VALID SERVER TOKEN
invalid variable field name or (2) as a HALT error. The
ID - rsn
failure method depends on the type of update.

During Web transaction initialization, an HTML query
Check for other messages related to this failure, and
variable or HTTP request header cookie was found
with a name beginning with SWSTOKEN_xxxxxxxx.
AVZ7411T REQUEST VARIABLE varname All query variables and cookies with names of this
INVALID AUTOMATED STATE form are reserved for built-in GLVSTATE. processing.
TRANSPORT - rsn However, the contents of this element did not contain
the expected displayable, hexadecimal, 24-byte token
id value that was expected.
User response However, a server-side token could not be retrieved
due to an internal error, and this GLVSTATE. set is
The erroneous information is not used, the inbound being bypassed.
query or cookie information is ignored, and no
GLVSTATE. information set is created.
User response
AVZ7414T varname VARIABLE DOES NOT
CONTAIN VALID INFORMATION TO This could be due to a storage shortage or other
RECONSTRUCT GLVSTATE.setname problem. The state information is handled as though
- rsn the token has expired.
AVZ7417T AUTOMATED STATE MGMT
Explanation MODULE (OPASMF) - INVALID
PLIST plist
During Web transaction initialization, an HTML cookie
variable was found with a name beginning with
SWSSTATE_. The value data, however, does not appear Explanation
to be formatted as expected for restoration of a The automated state management routine, OPASMF,
GLVSTATE. set. Note that this can occur for incorrect was invoked with an invalid parameter list (plist).
length information, bad encoding of the data, or some
other input anomaly.
User response
User response The module generates an S0C3 abend to terminate the
request. Contact Software Support.
The erroneous information is not used, the inbound
cookie information is ignored, and no GLVSTATE. AVZ7418T 'GLVSTATE.setname' MUST EXIST
information set is created for this variable. BEFORE UPDATE TO varname
AVZ7415T SERVER TOKEN ID

(tknid) REUSED IMPROPERLY Explanation
FOR GLVSTATE.setname1/ The indicated GLVSTATE. collection does not exist. It
GLVSTATE.setname2 SETS must be created before the update to any collection
member can be performed.
Explanation The GLVSTATE associated setname may also be an
During Web transaction initialization, an HTML query index number.
variable or HTTP request header cookie was found
with a name beginning with SWSSTATE_xxxxxxxx. User response
All query variables and cookies with names of this
form are reserved for built-in GLVSTATE. processing. Create the set before attempting to set the variable.
However, the contents of this element contained an AVZ7419T UPDATE TO csym NOT ALLOWED
indication that a token id had been improperly re-used. FOR GLVSTATE.collection
COLLECTION WITH STATUS=status
User response
This is a logic error. The server generates an S0C3 Explanation
abend. Contact Software Support for assistance. The indicated GLVSTATE. collection is currently flagged
AVZ7416T GLVSTATE.setname NOT as being in a status that does not allow updates.
RECONSTRUCTED FOR Change the collection to ACTIVE status either by
TOKENID=tknid DUE TO ERROR resetting it or by deleting and re-creating it.
errdesc
User response
Explanation The current request is rejected.
During Web transaction initialization, an HTML query AVZ7420T UPDATE TO 'csym' NOT ALLOWED
variable or HTTP request header cookie was found BECAUSE val EXCEEDS CURRENT
with a name beginning with SWSTOKEN_xxxxxxxx. SUBKEY COUNT OF count
All query variables and cookies with names of this
form are reserved for built-in GLVSTATE. processing.

The number of keyed values within the set is lower The indicated GLVSTATE. variable value that was being
than the key-index value specified by the symbolic assigned was truncated because only lengths up the
reference. Key-index references may not be used to size given are supported.
create new keyed value pairs.
User response
User response
The current request is ignored.
The current request is rejected.
The variable fields of the message text are: csym
The variable fields of the message text are: csym collection symbol being updated field field usage size
collection symbol being updated value key index value maximum size for this field
in symbolic reference num current number of keys
defined AVZ7425T UPDATE OF 'csym' IGNORED
- TOKEN WITH ID=tknid HAS
AVZ7421T UPDATE TO 'csym' IGNORED ALREADY EXPIRED
BECAUSE GLVSTATE.collection IS
A typeset TYPE SET WHICH DOES Explanation
NOT USE HTTP COOKIES
The indicated GLVSTATE. variable value update failed
because the indicated token has already expired.
Explanation
The indicated GLVSTATE. collection does not use HTTP User response
cookies as a transport mechanism. The current update
is ignored because it does not apply to non-cookie- The current request is rejected with an error.
based information sets.
collection symbol being updated token token id for
User response which update required
The current request is ignored. AVZ7426T setname HAS BEEN RESET
collection symbol being updated collect collection Explanation
name value current set type value
The indicated GLVSTATE. information set has been
AVZ7422T UPDATE TO 'csym' IGNORED reset.
BECAUSE GLVSTATE.collection IS A
value TYPE SET WHICH DOES NOT User response
USE SERVER-SIDE TOKENS
None. The request completes normally.
Explanation AVZ7427T NO "SET-COOKIE:" SENT FOR
GLVSTATE.setname - COOKIE
The indicated GLVSTATE. collection does not use
WOULD EXCEED 4K MAX. SIZE
tokens as an indirect storage mechanism. The current
update is ignored because it does not apply to non-
token-based information sets. Explanation
The indicated GLVSTATE. information set has not
User response been used to generate an outbound HTTP Set-cookie:
response because the total length of the value data,
The current request is ignored.
once encoded, exceeds the maximum 4k allowed by
The variable fields of the message text are: csym the Netscape cookie specification for the size of the
collection symbol being updated collect collection name/value pair.
name value current set type value
AVZ7423T VALUE ASSIGNED TO 'csym' User response
TRUNCATED BECAUSE field The indicated state set is bypassed.
MAXIMUM LENGTH IS size
AVZ7428T ERROR WHILE BUILDING AVZ7502S msgtext
SET-COOKIE: RESPONSE FOR
GLVSTATE.setname - RC=rcode Explanation
This is a generic message used for severe level
Explanation
messages from RPC programs using the SWSWTO
An error was encountered while building an outbound function.
Set-cookie: response header for the indicated state
information set. User response
None.
User response
Buffer flush processing continues. AVZ7503H msgtext
AVZ7429T VARIABLE varname CONTAINS Explanation

INVALID SERVER TOKENID ID
WHICH MAY BE SPOOF ATTEMPT This is a generic message used for hardcopy level
(ID=tknid) messages from RPC programs using the SWSWTO
function.
Explanation
User response
An error was encountered while attempting to restore
saved state information using a server-side token none.
id. The characteristics of the error encountered MAY
AVZ8000E Java™ JVM feature is not
indicate an attempt to spoof a server token id value,
configured.
although this is by no means certain. If the error
occurs frequently, you may wish to investigate this
possibility further. Explanation
None.
User response
The server token id is handled as though it designates User response
an expired token from which no application data
values can be restored.
AVZ8002E Unable to get the JVM Profile List
AVZ7500I msgtext
from the Local Registry.
This is a generic message used for informational level
Unable to get the JVM Profile List from the Local
Registry.
function.
User response
User response
Make sure the Registry is defined to the product.
None.
AVZ8003E Unable to build JVM Profile List.
AVZ7501W msgtext
Explanation
Explanation
Unable to build JVM Profile List.
This is a generic message used for warning level
function. User response
User response
AVZ8004E Unable to allocate latch for JVM
None. profile.

Explanation AVZ8904W errdesc additinfo
Unable to build JVM Profile List.
Explanation
User response A correctable error was detected while terminating a
task runtime environment for C-language main product
Contact Software Support. routines.
AVZ8900E errdesc additinfo
User response
Explanation The runtime environment is terminated if the error is
An error was encountered while attempting to initialize correctable. Otherwise, the termination request will
a task runtime environment for C-language main fail with a more severe error.
product routines. AVZ8905E errdesc additinfo

The runtime environment is not initialized. Check for While terminating the C-language runtime
other messages that might indicate the cause of the environment, an error was encountered. Termination
failure, and contact Software Support. processing continues but may leave allocated
AVZ8901T tracedesc additinfo resources orphaned.

While initializing the C-language runtime environment, Termination processing continues.
statistical tracing is enabled. This message is used to AVZ9000H modname/funcode execution
trace out information about the environment. msgtext

Initialization processing continues. This message is used to trace product termination. A
AVZ8902W errdesc additinfo message is issued before and after the execution of
each termination routine.
Explanation
User response
A correctable error was detected while initializing a
task runtime environment for C-language main product There is no action for this message. This message is
routines. only used for trace and debugging purposes.
AVZ9001I Subsystem subsys termination
User response complete
The runtime environment is initialized after the error is
corrected. Explanation
AVZ8903T tracedesc additinfo This is the standard product termination complete
message.
Explanation
User response
While terminating the C-language runtime
environment, statistical tracing is enabled. This No action is required.
message is used to trace out information about the AVZ9002E Subsystem subsys termination
environment. incomplete

Termination processing continues. Product execution has terminated. However, one or
more errors were detected during product termination.
As a consequence, normal product termination was Explanation
not possible.
a wide variety of internal errors. The message
User response text provides a description of the current operation
Check for any error messages issued during (service) and what the current operation was
termination. If possible, fix the problem identified attempting to do, such as GETMAIN, FREEMAIN, and
by the error messages, and restart the product. If so on.
Support. Please note the exact contents of the User response
above error message and any other error messages
associated with the product termination error. Check the error messages and the return code
AVZ9008S ABEND ERROR abcode-rsncode AT more error messages referring to the current problem.
modname+offset If possible, fix the problem identified by the error
messages, and retry the operation. If the problem
A serious abend occurred during product initialization, AVZ9505I errdesc

execution, or termination. The abend was not
recoverable, and the product was forced to terminate. Explanation
This is a generic informational message used to clarify
User response a wide variety of internal errors. The message text
Check the abend code and any related abend provides further info for the current operation and
messages. If possible, fix the problem identified what the current operation was attempting to do.
the problem cannot be resolved, contact Software User response
Support. Note the exact contents of the above error
message and any other error messages associated Check the error messages and the return code
with the product failure. associated with this problem. There may be one or
AVZ9100T INVALID COMBINATION OF ./ If possible, fix the problem identified by the error
or ../ in pathname messages, and retry the operation. If the problem
Explanation AVZ9506S service OF desc FAILED, RC=rcode,
An HFS pathname string was rejected because it DETECTED AT addr
contains an invalid combination of ./, ../, or other
characters that are not resolvable at runtime. Explanation
User response a wide variety of internal errors. The message
If the PATH() operand of the matched-to WWW rule text provides a description of the current operation
contains a wildcard(*), this may indicate an attempt (service) and what the current operation was
by a client to refer to an HFS sub-directory to which attempting to do, such as GETMAIN, FREEMAIN, and
access should not be granted. This message can also so on.
result from an incorrect combination of specifications
for the server DOCUMENTROOT start-up parameter, User response
the HFSROOT() parameter on a DEFINE RULESET
statement, and/or the PATH() parameter on the WWW Check the error messages and the return code
rule definition. The transaction is rejected with a 404 associated with this problem. There may be one or
(file not found) error status. more error messages referring to the current problem.
AVZ9504E service OF desc FAILED, RC=rcode, messages, and retry the operation. If the problem
DETECTED AT addr cannot be resolved, contact Software Support.
AVZ9507E DATA SET dsname DOES
NOT EXIST - LOCATE OF

dsname FAILED, RC=rcode, cannot be resolved, contact Software Support to
REASON=rsncode obtain additional assistance.
AVZ9511E service OF desc FAILED, RC=rcode,
Explanation RS=rsncode, DETECTED AT addr
A failure occurred during a LOCATE of a data set. The
return and reason codes in the message are from the Explanation
LOCATE routine.
a wide variety of internal errors. The message
User response text provides a description of the current operation
Check the error messages and the return code (service) and what the current operation was
associated with this problem. There may be one or attempting to do, such as GETMAIN, FREEMAIN, and
more error messages referring to the current problem. so on.
messages, and retry the operation. If the problem User response
AVZ9508E OBTAIN OF FORMAT1 DSCB FOR associated with this problem. There may be one or
DSNAME dsname VOLUME Vid more error messages referring to the current problem.
FAILED, RC = rcode, REASON CODE If possible, fix the problem identified by the error
= rsncode messages, and retry the operation. If the problem
Explanation AVZ9513E Unknown I/O reqcd, diaginfo
A failure occurred during an OBTAIN of a data set. The
return and reason codes in the message are from the Explanation
OBTAIN FORMAT1 DSCB routine.
An unknown service request code has been detected
by the server I/O routines. The request cannot be
User response processed and an internal ABEND will be generated
Check the error messages and the return code to log a symptom record in LOGREC. A general error
associated with this problem. There may be one or return code will be reflected to the caller.
messages, and retry the operation. If the problem
Check for other error messages associated with the
cannot be resolved, contact Software Support to
problem. There may be one or more error messages
obtain additional assistance.
referring to the current problem or to the component
AVZ9509E OBTAIN OF FORMAT1 DSCB FOR or feature issuing the request. If the problem cannot
DSNAME dsname VOLUME Vid be resolved, contact Software Support to obtain
FAILED BECAUSE DATA SET IS additional assistance.
MIGRATED
AVZ9990I msgtext
Explanation
Explanation
A failure occurred during an OBTAIN of a data set. The
This is a generic message used to format information
data set volser is set to MIGRAT, indicating the data
relating to abends detected by the product. The abend
set has been migrated offline.
module, abend offset, abend code, and registers at
the time of abend are all formatted for debugging
User response purposes. In the case of internal errors, the reason for
Check the error messages and the return code the internal abend is also indicated.
Record all of the information, and report the problem
messages, and retry the operation. For some server
to Software Support.
functions, you may need to manually recall the data
set before retrying the operation. If the problem
AVZ9998S TEXTMERGE (MSGID=M998) AVZ9999S msgtext
PROCESSING FAILURE
REASON=rsncode Explanation
This message is for internal product testing.
Explanation
Invalid parameters were passed to the message send User response
routine for a special textmerge function call. This is
likely due to a logic error on the part of the calling No action is required.
routine.
User response
Contact Software Support with this problem

Chapter 2. z/OS Connect interface codes
z/OS Connect interface codes can be returned in a request.
When an error occurs, the JSON response is as follows:
{
"Errmsg": "AVZ2700E Error bb-ccc ddd Processing request. Extra information: eee",
"Result": -99bbccc
}
where:
• AVZ is the message prefix, as set by a Data Virtualization Manager server region startup parameter
• bb is a major error number. See “Code categories” on page 273.
• ccc is a minor error number
• ddd is a short description of the error
• Extra Information: eee provides extra information, if available.
Note: Extra Information: eee appears only if extra information is available.
The Result number will be a negative number from -9901001 to -9909005. The number has the major
and minor error codes in it.
Code categories
The major error codes group the error codes based on processing phases. The following table lists the
major error code categories:
Table 2. Code categories

Code category Description
01 Storage error
02 Input data error
Note: There are no minor error codes associated with this category. These
messages appear as 02-000.
03 Input vectors error

04 Input JSON parsing error
05 Input JSON interpretation error
06 Processing error
09 Miscellaneous error
Error codes
The tables in this section list the possible errors codes and messages. Corrective action is provided where
available. When considering corrective action, note the following points:
• The Data Virtualization Manager server region parameters can be changed. While the region is running,
permanent changes will require changes to be made to the AVZIN00 member.
• The Data Virtualization Manager server region must be restarted after making changes to the JCL and/or
the AVZIN00 member.
Note that with the Data Virtualization Manager service provider in use, the user does not provide the
JSON input directly, but rather the service provider will build the input JSON string from the parameters
provided by the user. However, the Data Virtualization Manager server interface does not see the original

parameters, just the JSON string. Errors related to JSON parsing could reflect something wrong in the
original data, or an error in the service provider. Each case would need to be examined individually.
Also, when interpreting the input, some errors may not make sense for the same reason.
The following tables list the possible errors codes, messages, and corrective action, if available. The
tables also indicate if Extra information is provided with the error message.
Table 3. Storage errors (01)

Error code Message Description or corrective action Extra
information
01-001 No storage for control block (1) No storage for the OPC3 control
block
01-002 No storage for input No storage for the input data etc.
Table 4. Input data error (02)

information
02-000 Unable to receive input data.
Note: There are no minor error codes associated with the input data error.
Table 5. Input vectors error (03)

information
03-001 No room left for vector Offset in I/P
03-002 Length in vector header too short Offset in I/P
03-003 Found first vector code but not first Offset in I/P
vector
03-004 First vector bad length Offset in I/P
03-005 First vector bad data Offset in I/P
03-006 Found last vector code but not last Offset in I/P
vector
03-007 Last vector bad length Offset in I/P
03-008 Last vector bad data Offset in I/P
03-009 Uid vector already seen Offset in I/P
03-010 Uid vector bad length Offset in I/P
03-011 Uid vector bad data Offset in I/P
03-012 Http verb vector already seen Offset in I/P
03-013 Http verb vector bad length Offset in I/P
03-014 Http verb vector bad data Offset in I/P
03-015 Passticket vector already seen Offset in I/P
03-016 Passticket vector bad length Offset in I/P
03-017 Passticket vector bad data Offset in I/P
Table 5. Input vectors error (03) (continued)
information
03-018 Req values vector already seen Offset in I/P
03-019 Req values vector bad length Offset in I/P
03-020 Req values vector bad data Offset in I/P
03-021 Refr url vector already seen Offset in I/P
03-022 Refr url vector bad length Offset in I/P
03-023 Refr url vector bad data Offset in I/P
03-024 Sp cap l vector already seen Offset in I/P
03-025 Sp cap l vector bad length Offset in I/P
03-026 Sp cap l vector bad data Offset in I/P
03-027 Req name vector already seen Offset in I/P
03-028 Req name vector bad length Offset in I/P
03-029 Req name vector bad data Offset in I/P
03-030 Lst ip @ vector already seen Offset in I/P
03-031 Lst ip @ vector bad data Offset in I/P
03-032 Usr ip @ vector already seen Offset in I/P
03-033 Usr ip @ vector bad data Offset in I/P
Table 6. Input JSON parsing errors (04)

information
04-001 No data (or all white space) Offset in I/P
04-002 No opening { Offset in I/P
04-003 Trailing data after } Offset in I/P
04-004 Unexpected end-data Offset in I/P
04-005 No space in storage area Offset in I/P
04-006 Too much nesting Offset in I/P
04-007 Unrecognized json node Offset in I/P
04-021 Object - eod after { Offset in I/P
04-022 Object - expected : Offset in I/P
04-023 Object - no data after : Offset in I/P
04-024 Object - no data after value Offset in I/P
04-025 Object - no data after , Offset in I/P
04-026 Object - expected , or } Offset in I/P
04-027 Object - null name Offset in I/P
Chapter 2. z/OS Connect interface codes 275

Table 6. Input JSON parsing errors (04) (continued)
information
04-028 Object - expected " after , Offset in I/P
04-029 Object - duplicate name Offset in I/P
04-031 Array - eod after [ Offset in I/P
04-032 Array - no data after value Offset in I/P
04-033 Array - no data after , Offset in I/P
04-034 Array - expected , or ] Offset in I/P
04-035 Array - found ] after , Offset in I/P
04-041 Word - unrecognized Offset in I/P
04-051 String - no data Offset in I/P
04-052 String - no closing quote Offset in I/P
04-053 String - no character after \ Offset in I/P
04-054 String - no xxxx after \u Offset in I/P
04-055 String - invalid xxxx after \u Offset in I/P
04-056 String - unrec character after \ Offset in I/P
04-057 String - bad 2-byte sequence Offset in I/P
04-060 String - > 4-byte sequence Offset in I/P
04-061 String - control character found Offset in I/P
04-071 Number - nothing after - Offset in I/P
04-072 Number - no integer part or too large Offset in I/P
04-073 Number - nothing after . Offset in I/P
04-074 Number - no fraction part or too long Offset in I/P
04-075 Number - nothing after e Offset in I/P
04-076 Number - nothing after exponent Offset in I/P
sign
04-077 Number - exponent value missing or Offset in I/P
too long
04-078 Number - exponent too large Offset in I/P
04-079 Number - leading zeros Offset in I/P
04-090 Value - character after value is Offset in I/P
invalid
04-099 unknown json parsing error Offset in I/P
Table 7. Input JSON interpretation errors (05)
information
05-001 Root node is not an object Field name
05-002 Request object not found Field name
05-003 Request is not an object Field name
05-004 Duplicate field found in request Field name
object
05-005 Unknown field found in request Field name
object
05-006 Field operation not found Field name
05-007 Field fields not found Field name
05-008 Field operation found Field name
05-009 Field fields found Field name
05-010 Not a json value Field name
05-011 Not a json string Field name
05-012 Not a json number Field name
05-013 Not an integer Field name
05-014 Bad value (e.g. not in range or Field name
unknown)
05-020 Field fields has children Field name
05-021 Field fields is not an object Field name
05-022 Field fields child is not a json value Field name
05-031 Field operation invalid length (1) Field name
05-032 Field operation has blanks in the Field name
value
05-033 Field operation invalid length (2) Field name
05-034 Field operation first character is not / Field name
05-035 Field operation has less than 3 segs Field name
05-036 Field operation has a bad virt dir Field name
name
05-037 Field operation has a bad web Field name
service name
05-038 Field operation has a bad operation Field name
name
05-061 Lookup operation - virt dir not found Field name
05-062 Lookup operation - virt dir not auth Field name
05-063 Lookup operation - web service not Field name
found

Table 7. Input JSON interpretation errors (05) (continued)
information
05-064 Lookup operation - web service not Field name
auth
05-065 Lookup operation - operation name Field name
not found
05-066 Lookup operation - operation name Field name
not auth
05-067 Lookup operation - call not Field name
supported
05-068 Lookup operation - not select Field name
05-069 Lookup operation - sql statement too Field name
long
05-070 Lookup operation - sql statement Field name
map not found
05-071 Lookup operation - input map not Field name
found
05-072 Lookup operation - return map not Field name
found
05-073 Lookup operation - more than 1 Field name
schema name field
05-074 Lookup operation - schema name Field name
field can be null
05-081 Input field - field not found (no Field name
default)
05-082 Input field - field already used Field name
05-083 Input field - field not used Field name
05-084 Input field - null & null value is not Field name
allowed
05-085 Input field - string expected Field name
05-086 Input field - number expected Field name
05-087 Input field - number is not an integer Field name
05-088 Input field - string expected Field name
05-089 Input field - number expected Field name
05-090 Input field - invalid hex string Field name
05-091 Input field - invalid date Field name
05-092 Input field - invalid time Field name
05-093 Input field - invalid timestamp Field name
05-095 Input field - tgt hex float length not Field name
4/8/16
Table 7. Input JSON interpretation errors (05) (continued)
information
05-096 Input field - tgt bin float length not Field name
4/8/16
05-097 Input field - tgt dec float length not Field name
8/16
05-098 Input field - character lob not Field name
supported
05-099 Input field - binary lob not supported Field name
05-100 Input field - graphic lob not Field name
supported
05-101 Input field - unknown internal format Field name
05-111 Input field - ccsid not supported Field name
05-112 Return field - ccsid not supported Field name
05-120 SQL verb/HTTP verb mismatch Field name
Table 8. Request processing error (06)

information
06-001 No space in return area
06-002 No space in work area
06-003 Communications data return error
06-004 Unknown/not found provider
06-005 No space in field area
06-006 Unable to log user on
06-007 Unsupported return field format
06-008 An abend occurred during request
processing
06-009 Request has timed out
06-010 No staging storage
06-011 No default for schema name
06-012 Sql statement overflow
06-013 Didnt find schema name parameter
marker
06-014 Null or blank schema name
06-015 Overflow when converting single
quotes to double quotes
06-020 Input sqlda overflow
06-030 No data for subs point

Table 8. Request processing error (06) (continued)
information
06-040 Not internal character set
06-050 Cmbu build failed (internal)
06-051 Sqlb build failed (internal)
06-052 Ret fields # mismatch
06-053 Ret field data type mismatch
06-054 Ret field has invalid data
06-060 Processing error
06-090 Binary input not supported yet
Table 9. Miscellaneous error (09)

information
09-001 Request has timed out Timed out.
The request has taken too long to
process. There is a parameter that
nominates the maximum time that
a request can take, and this time
has been exceeded. Either increase
the allowed time or ensure that the
request does not take too long.
09-002 Server inactive The server has been set as inactive.

An administrator has set the server
as inactive.
09-003 Server retry after error The server is retrying after a

communications error.
The request can be resent after
waiting a few seconds.
09-004 Communications error The communications between z/OS

Connect and the Data Virtualization
Manager server region has failed.
(Hard WOLA Error)
09-005 Server or region is terminating The Data Virtualization Manager
server is shutting down.
Accessibility features
Accessibility features help a user who has a physical disability, such as restricted mobility or limited
vision, to use a software product successfully.
The major accessibility features in this product enable users to perform the following activities:
• Use assistive technologies such as screen readers and screen magnifier software. Consult the assistive
technology documentation for specific information when using it to access z/OS interfaces.
• Customize display attributes such as color, contrast, and font size.
• Operate specific or equivalent features by using only the keyboard. Refer to the following publications
for information about accessing ISPF interfaces:
– z/OS ISPF User's Guide, Volume 1
– z/OS TSO/E Primer
– z/OS TSO/E User's Guide
These guides describe how to use the ISPF interface, including the use of keyboard shortcuts or
function keys (PF keys), include the default settings for the PF keys, and explain how to modify their
functions.

Product legal notices
This information was developed for products and services offered in the U.S.A.
This material may be available from IBM in other languages. However, you may be required to own a copy
of the product or product version in that language in order to access it.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not give you any license to these patents. You can
send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Director of Licensing

IBM Corporation
North Castle Drive

Armonk, NY 10504-1785
U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.
The licensed program described in this information and all licensed material available for it are provided
by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or
any equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for the operating platform
for which the sample programs are written. These examples have not been thoroughly tested under
all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at
"Copyright and trademark information" at http://www.ibm.com/legal/copytrade.html.
Adobe and the Adobe logo are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States, and/or other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.
Linux® is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the Unites States,
other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, and service names may be trademarks or service marks of others.
Terms and conditions for product documentation
Permissions for the use of these publications are granted subject to the following terms and conditions:
Applicability: These terms and conditions are in addition to any terms of use for the IBM website.
Personal use: You may reproduce these publications for your personal, noncommercial use provided that
all proprietary notices are preserved. You may not distribute, display or make derivative work of these
publications, or any portion thereof, without the express consent of IBM.
Commercial use: You may reproduce, distribute and display these publications solely within your
enterprise provided that all proprietary notices are preserved. You may not make derivative works of
these publications, or reproduce, distribute or display these publications or any portion thereof outside
your enterprise, without the express consent of IBM.
Rights: Except as expressly granted in this permission, no other permissions, licenses or rights are
granted, either express or implied, to the publications or any information, data, software or other
intellectual property contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use
of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not
being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable
laws and regulations, including all United States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS
ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT,
AND FITNESS FOR A PARTICULAR PURPOSE.
Privacy policy considerations
IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies
or other technologies to collect product usage information, to help improve the end user experience,
to tailor interactions with the end user or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings can help enable you
to collect personally identifiable information. If this Software Offering uses cookies to collect personally
identifiable information, specific information about this offering’s use of cookies is set forth below.
This Software Offering does not use cookies or other technologies to collect personally identifiable
information.
If the configurations deployed for this Software Offering provide you as customer the ability to collect
personally identifiable information from end users via cookies and other technologies, you should seek
your own legal advice about any laws applicable to such data collection, including any requirements for
notice and consent.
For more information about the use of various technologies, including cookies, for these purposes,
see IBM’s Privacy Policy at http://www.ibm.com/privacy and the section titled "Cookies, Web Beacons,
and Other Technologies" in IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details. Also,
see the "IBM Software Products and Software-as-a-Service Privacy Statement" at http://www.ibm.com/
software/info/product-privacy.
Product legal notices 285

IBM®
GC27-9136-01

Havmsa 10

Uploaded by

Copyright:

Available Formats

Havmsa 10

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Havmsa 10

Uploaded by

Copyright:

Available Formats

IBM Data Virtualization Manager for z/OS

Messages and Codes

About this information........................................................................................... v

How to send your comments to IBM......................................................................vii

Chapter 1. Messages and codes..............................................................................1

Chapter 2. z/OS Connect interface codes............................................................273

Accessibility features........................................................................................ 281

Product legal notices......................................................................................... 283

Purpose of this information

Who should read this information

© Copyright IBM Corp. 2017, 2021 v

If you have a technical problem

© Copyright IBM Corp. 2017, 2021 vii

© Copyright IBM Corp. 2017, 2021 1

Message variable data

This is equivalent to cs+of, as described below:

MODIFY PARM NAME(CONMSGFORMAT ) VALUE(X)

********************************* Top of Data *********************************

EXPLAIN The xxxxINEF start-up procedure ended with RC=8, indicating

ACTION Determine if the warning is anticipated. If not, correct

Chapter 1. Messages and codes 3

Table 1. Error Message Description

Changing the severity of an error message

Chapter 1. Messages and codes 5

5. Overwrite the parameter value and press ENTER.

Data Virtualization Manager server reason codes

Unable to connect to DB subsystem DBAA; Return code 8, Reason code 00BAD044

The following table lists the available reason codes.

Reason codes Short description Detailed description

Chapter 1. Messages and codes 7

Chapter 1. Messages and codes 9

Chapter 1. Messages and codes 11

Chapter 1. Messages and codes 13

Chapter 1. Messages and codes 15

Chapter 1. Messages and codes 17

Chapter 1. Messages and codes 19

0X00BAD044 Password missing See Reason code: 0X00BAD043

0X00BAD04C Failed to begin the bind

Chapter 1. Messages and codes 21

0X00BAD059 Data length exceeds

0X00BAD05F An invalid database Name

0X00BAD063 DRDA SQL Diagnostic

Chapter 1. Messages and codes 23

Chapter 1. Messages and codes 25

AVZ0001U desc GETMAIN failed - increase Explanation

Chapter 1. Messages and codes 27

Review the messages just before and after this

User response Explanation

Explanation User response

Chapter 1. Messages and codes 29

User response Explanation

User response User response

User response User response

Chapter 1. Messages and codes 31

User response User response

AVZ0045S Task or exit modname can not be

Chapter 1. Messages and codes 33

User response AVZ0059S Configuration issue: H/W

User response User response

* Top of Data *