Open Data Analytics for z/OS : IBM Open Data Analytics for ... · Open Data Analytics for z/OS Version 1 Release 1 System Messages IBM GC27-9415-00

Open Data Analytics for z/OSVersion 1 Release 1

System Messages

IBM

GC27-9415-00

Note

Before using this information and the product it supports, read the information in “Notices” on page265.

This edition applies to Version 1 Release 1 of IBM® Open Data Analytics for z/OS® (5655-OD1) and to all subsequentreleases and modifications until otherwise indicated in new editions.

Last updated: 2020-06-19© Copyright International Business Machines Corporation 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.© Rocket Software, Inc. 2019.

Contents

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

How to send your comments to IBM......................................................................viiIf you have a technical problem.................................................................................................................vii

Summary of changes for IBM Open Data Analytics for z/OS System Messages........ ix

Chapter 1. Data Service server messages............................................................... 1

Chapter 2. Data Service server reason codes...................................................... 235

Chapter 3. IBM Open Data Analytics for z/OS system messages.......................... 257

Accessibility......................................................................................................263

Notices..............................................................................................................265Trademarks..............................................................................................................................................266

Index................................................................................................................ 267

iii

iv

About this information

This information supports IBM Open Data Analytics for z/OS (5655-OD1).

Purpose of this information

This information describes how to interpret and respond to messages issued by IBM Open Data Analyticsfor z/OS.

Who should read this information

This information is intended for z/OS system programmers, system administrators, and system operatorswho are responsible for installing, customizing, operating, and maintaining IBM Open Data Analytics forz/OS.

© Copyright IBM Corp. 2019 v

vi Open Data Analytics for z/OS : IBM Open Data Analytics for z/OS V1.1.0 System Messages

How to send your comments to IBM

We invite you to submit comments about the z/OS product documentation. Your valuable feedback helpsto ensure accurate and high-quality information.

Important: If your comment regards a technical question or problem, see instead “If you have a technicalproblem” on page vii.

Submit your feedback by using the appropriate method for your type of comment or question:Feedback on z/OS function

If your comment or question is about z/OS itself, submit a request through the IBM RFE Community(www.ibm.com/developerworks/rfe/).

Feedback on IBM Knowledge Center functionIf your comment or question is about the IBM Knowledge Center functionality, for example searchcapabilities or how to arrange the browser view, send a detailed email to IBM Knowledge CenterSupport at [email protected].

Feedback on the z/OS product documentation and contentIf your comment is about the information that is provided in the z/OS product documentation library,send a detailed email to [email protected]. We welcome any feedback that you have, includingcomments on the clarity, accuracy, or completeness of the information.

To help us better process your submission, include the following information:

• Your name, company/university/institution name, and email address• The following deliverable title and order number: Open Data Analytics for z/OS System Messages,

GC27-9415-00• The section title 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 commentsin 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 theissues that you submit.

If you have a technical problemIf you have a technical problem or question, do not use the feedback methods that are provided forsending documentation comments. Instead, take one or more of the following actions:

• Go to the IBM Support Portal (support.ibm.com).• Contact your IBM service representative.• Call IBM technical support.

© Copyright IBM Corp. 2019 vii

http://www.ibm.com/developerworks/rfe/

http://www.ibm.com/developerworks/rfe/

mailto:[email protected]

mailto:[email protected]

http://support.ibm.com

viii Open Data Analytics for z/OS : IBM Open Data Analytics for z/OS V1.1.0 System Messages

Summary of changes for IBM Open Data Analytics for z/OSSystem Messages

The following changes are made to Version 1 Release 1.

March 2020

• New messages:

– AZK5541I (replaces AZK5541E)– AZK5542E– AZK5543I– AZK5544E– AZK5545I– AZK5546I– AZK5547E– AZK5548I– AZK5549E– AZK5550I

September 2019

• New messages:

– AZK5540E– AZK5541E

March 2019

• The system messages were moved from Installation and Customization Guide to this new SystemMessages guide.

© Copyright IBM Corp. 2019 ix

x Open Data Analytics for z/OS : IBM Open Data Analytics for z/OS V1.1.0 System Messages

Chapter 1. Data Service server messagesThese topics contain information about the messages and codes that the Data Service server issues.

Types of messages

The Data Service server produces many useful messages during the course of its operation. The type ofmessage produced depends on which component is issuing the message. The types of messages thatData Service issues are as follows:

ISPFThe ISPF/xDy application is the only component of the Data Service server that produces ISPFmessages. ISPF messages appear in the upper right hand corner of a display. These messages are notdocumented in this manual. If you require additional information on an ISPF message, use PF1 todisplay the long version of the message.

WTOThe main address space of the Data Service server produces Write-To-Operator messages. Thesemessages appear on the system console and in the system log. Most of the messages produced bythe Data Service server fall into this category.

WTPThe ISPF/xDy application and the Data Service DSN and Data Service CAF components produce Write-To-Programmer messages. These messages appear on the user's TSO terminal in line mode. Both theWTO and WTP type messages are included in this documentation.

Format

The Data Service server messages have a format that is consistent with the Data Service subsystem IDformat, xZKy, where x can be any alphabetic letter, and y can be any alphanumeric character (A-Z and0-9). The following example shows the standard makeup of a Data Service message:

xDynnnns text

Where:

• x: Indicates the first letter of the Data Service subsystem ID.• D: Indicates the product code.• y: Indicates the last (fourth) alphanumeric character of the Data Service 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 Service is probably not functioning correctly any more.– O: Error is related to a TSO SERVER associated with Data Service Web Server.– N: Message is discarded

• text: The text of the message. The message can contain fixed and variable information. Fixedinformation is shown in all uppercase letters. Variable information is shown in all lowercase letters.

© Copyright IBM Corp. 2019 1

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 anddefinitions 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 followingstarted 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 uppercase prior to routing the message to its final output destination. Setting this parameter to UPPER isrecommended when Data Service executes on certain non US-supported operating system utilizing aconsole code page in which the lower-case Latin letters display as Katakana characters (for example, IBMEBCDIC SBCS code pages 290 and 1030).

Note: The setting of this parameter affects all numbered messages produced by the server; even whenthe 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, undervarious 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 befound in the message entries themselves.

AZK0001U desc GETMAIN failed - increasememory size

Explanation

Insufficient storage. The product was unable to obtainenough storage to allocate the initial program stack.

2 Open Data Analytics for z/OS : IBM Open Data Analytics for z/OS V1.1.0 System Messages

User response

Check the abend code to determine if the region sizeshould be increased. Increase the region size ifnecessary, and restart the product.

AZK0002S parmname IS errdesc - correction

Explanation

This message indicates a problem with the parameterstring that was passed to the main started task entrypoint. Execution is terminated.

User response

Correct the error that is indicated in the errormessage, and restart the product.

AZK0003S CODES BEGINNING WITH var1,NOT var2 SHOULD NOT BE USEDTO SET THE %2 PARAMETER

Explanation

This message contains variables that are resolved atrun-time and emitted by the server as it processes.

User response

Review the messages just before and after thismessage to understand the context.

AZK0004S parmname IS errdesc

Explanation


User response

Ensure that a parameter string is being passed (usingPARM=) in the started task JCL. The parameter stringshould contain at least "INIT,ssnx" where ssnx is the 4character subsystem name. Correct the error andrestart the product.

AZK0005S parmname val IS errdesc

Explanation


User response

Ensure that the execution option (the first parameterin PARM=) is INIT. This is the only valid value. Correctthe error, and restart the product.

AZK0006S Product not APF authorized,execution terminating

Explanation

This message is issued if the product detects that it isnot APF authorized. The main product address spacewill terminate immediately.

User response

Ensure that all of the STEPLIB data sets are APFauthorized. Note that all of the data sets must be APFauthorized, not just the data set containing the productload modules. Fix the STEPLIB data sets, and restartthe product.

AZK0007S subsys field IS errdesc

Explanation

The product tried to initialize or re-initialize a systemcontrol block (the SSCT). The system controlcontained a field with an invalid value. This error willcause product initialization to terminate.

User response

Check for other error messages were generated alongwith the error message. If the combined errormessages are sufficient to explain the error, takewhatever corrective action is appropriate. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0008S Product cannot execute in batch,execution terminating

Explanation

This message is issued if the product detects that it isrunning in batch. The main product address space willterminate immediately.

User response

The product cannot run as a batch job. The productmust execute as a started task. Install the product as astarted task, and restart the product.

AZK0009S Execution DEQ failed - contactsystems programming

Explanation

Some type of error occurred while the product wasreleasing the execution enqueue. The executionenqueue is used to prevent more than one copy of theproduct from using a single subsystem ID. Multiple

Chapter 1. Data Service server messages 3

copies of the product can execute concurrently so longas each copy uses a different subsystem ID.

User response

Check the error messages associated with thisproblem. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0010H modname/funcode executionmsgtext

Explanation

This message is used to trace product initialization. Amessage is issued before and after the execution ofeach initialization routine.

User response

There is no action for this message. This message isonly used for trace and debugging purposes.

AZK0011W STSI instruction failed with %1 -feedback = %2

Explanation


User response


AZK0012W CSRSI service returned RC=rcodefor CPU H/W identification request- product validation may beaffected.

Explanation

None.

User response

Contact IBM Software Support.

AZK0013S SSCT locate error - contactsystems programming

Explanation

The product tried to find the current subsystem ID inthe subsystem control block chain. A loop was foundin the subsystem control block chain.

User response

This is a serious error that may cause othercomponents of the system to fail. If the system ishaving other problems (such as loop errors), try toresolve the other problems before restarting theproduct. If the product is the only componentexperiencing any difficulty, contact Software Support.

AZK0014S var1: var2 var3 var4 var5 var6 var7

Explanation


User response


AZK0015S %PX-js subsystem subsys waitingfor execution ENQ

Explanation

Each active copy of the product must use a differentsubsystem ID. This restriction is enforced using theproduct execution enqueue. The product executionenqueue contains the current subsystem ID, so thatmultiple copies of the product can execute if eachcopy uses a different subsystem ID. A new copy of thesubsystem (subsys) has been started and isattempting to get the execution enqueue. Theexecution enqueue for subsystem is already held by acopy of the product.

User response

Either cancel the newly started subsystem that iswaiting on the execution enqueue or stop the currentlyactive copy of the subsystem. Stopping the currentlyactive copy of the subsystem will allow the new copyof the subsystem to complete initialization and startexecution. The new copy of the subsystem may haveto be stopped using the ASID keyword of the CANCELcommand.

AZK0016S Execution ENQ error - contactsystems programming

Explanation

Each active copy of the product must use a differentsubsystem ID. This restriction is enforced using theproduct execution enqueue. The product executionenqueue contains the current subsystem ID, so thatmultiple copies of the product can execute if eachcopy uses a different subsystem ID. The product triedto obtain the execution enqueue. The ENQ macrofailed.


User response

Check the error messages associated with thisproblem. There may be one or more ENQ/DEQ errormessages referring to the current problem. If possible,fix the problem identified by the error messages, andrestart the product. If the problem cannot be resolved,contact Software Support.

AZK0017S var1 PARAMETER INVALID: var2var3 var4 var5 var6 var7 var8.

Explanation


User response


AZK0018H var1 var2

Explanation


User response


AZK0019I var1 var2

Explanation


User response


AZK0020S First character of subsystem namemust be an alphabetic character(A-Z).

Explanation

Each copy of the product must use a uniquesubsystem ID string. The default subsystem ID isspecified in the started task procedure or in the STARTcommand used to start the product. In either case, thesubsystem ID string must always be exactly fourcharacters long, and the first characters must be oneof the alphabetic characters A-Z.

User response

Fix the subsystem ID string used to start the productby modifying the product started task procedure or bychanging the product start command. Restart theproduct using a valid subsystem ID string.

AZK0021S ABEND ERROR abcode REASONrsncode AT modname+offset

Explanation

A serious abend occurred during product initialization,execution, or termination. The abend was notrecoverable, and the product was forced to terminate.

User response

Check the abend code and any related abendmessages. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport. Note the exact contents of the above errormessage and any other error messages associatedwith the product failure.

AZK0022S Second 2 characters of subsystemname must be prodID.

Explanation

Each copy of the product must use a uniquesubsystem ID string. The default subsystem ID isspecified in the started task procedure or in the STARTcommand used to start the product. In either case, thesubsystem ID string must always be exactly fourcharacters long, and the second two characters mustbe a valid product ID pair (prodID). For example: "DB"is for AZK and "WS" is for HTTP-API.

User response


AZK0023S Subsystem name must be four (4)characters long

Explanation

Each copy of the product must use a uniquesubsystem ID string. The default subsystem ID isspecified in the started task procedure or in the STARTcommand used to start the product. In either case, thesubsystem ID string must always be exactly fourcharacters long.


User response


AZK0024S Last character of subsystem namemust be alphanumeric

Explanation

Each copy of the product must use a uniquesubsystem ID string. The default subsystem ID isspecified in the started task procedure or in the STARTcommand used to start the product. In either case, thesubsystem ID string must always be exactly fourcharacters long. The last character can be one of thealphanumeric characters A-Z or 0-9.

User response


AZK0025S %PM not prepared for executionby feature code

Explanation


User response


AZK0026S ss not configured for this CPUvar1, execution terminating.

Explanation

None.

User response


AZK0027S MVS/370 not supported

Explanation

The product checked the host system and found thatthe host system is some version of MVS/370. Theproduct does not support MVS/370.

User response

The product only supports z/OS. z/OS must beinstalled before the product can be used.

AZK0028S Product code pcode is invalid.

Explanation

None.

User response


AZK0029S Configuration issue detected; ssnot configured for CPU var1,execution continues

Explanation

None.

User response


AZK0030S %PM will require configurationupdate in <x> days

Explanation

None.

User response


AZK0031E %PM will require configurationupdate in <x> days.

Explanation

None.

User response


AZK0032S %PM configuration problem,execution terminating.

Explanation

None.

User response


AZK0033S CONFIGURATION FROM 'var2'PARAM. DOES NOT SUPPORT


EXECUTION OF THIS PRODUCT -TERMINATING.

Explanation

None.

User response


AZK0034S PM feature code feature notconfigured.

Explanation

None.

User response


AZK0035S subsys requires configurationupdate, execution continues.

Explanation

None.

User response


AZK0036S service OF desc FAILED, RC=rcode,DETECTED AT addr

Explanation

This is a generic error message used to describe awide variety of product initialization, execution, andtermination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do, such as GETMAIN,FREEMAIN, ATTACH, and so on.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and restart the product. If the problemcannot be resolved, contact Software Support.

AZK0037E rout errdesc FAILED, RC=rcode,DETECTED AT addr, %SK

Explanation

Some type of service routine (rout) (operating systemor product specific) failed. The error messageidentifies the service routine and the type of error.

User response

Check the full text of the error message, and fix theprogram that calls the application program interface, ifnecessary.

AZK0038S service OF desc FAILED, RC=rcode,REASON=rsncode, DETECTED ATaddr, %SK

Explanation

This is a generic error message used to describe awide variety of product initialization, execution, andtermination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do, such as GETMAIN,FREEMAIN, ATTACH, and so on.

User response


AZK0039S rout errdesc FAILED,ABEND=abcode, REASONCODE=rsncode

Explanation

This is a generic error message used to describe awide variety of product initialization, execution, andtermination errors. The message text provides thecurrent operation and what the current operation wastrying to do.

User response


AZK0040S cblk CONTROL BLOCK AT addrmsgtext


Explanation

This message is used to describe control block errors.The error may be an invalid tag, invalid length, or someother error. The control block (cb) could not be usedbecause of the error.

User response

Check the error messages associated with thisproblem. There may be one or more error messagesreferring to the current problem. If possible, fix theproblem identified by the error messages, and restartthe product. If the problem cannot be resolved,contact Software Support.

AZK0042I %PX ver/lvl initializing onprocessorcpuID.model.modelno.manufPCCAcount flag.

Explanation

This message is issued during early start-up anddisplays information about the hardware on which theproduct is executed. This message providesinformation helpful to support personnel should someconfiguration difficulty arise.

User response

No action is required. If later messages indicate aconfiguration problem has been encountered, thismessage may aid in the swift resolution of theproblem. If the problem cannot be resolved, contactIBM Software Support.

AZK0043H msgtext

Explanation

This message is used to print out various internalcontrol blocks, the contents of processor registers,and other hexadecimal information.

User response

If there are other messages indicating an error, usethis message in conjunction with them to determinethe cause of the problem. If there is a problem and youare unable to resolve it, contact Software Support.

AZK0044S errdesc FREEMAIN FAILED

Explanation

Storage release error. The product was unable to freea section of storage.

User response

Check the abend code to determine the cause of theerror. Make any needed changes to resolve theproblem, and restart the product.

AZK0045S Task or exit modname can not beexecuted

Explanation

A product macro cannot be used because the productcontrol blocks are inconsistent. This macro is used toinitialize a task or an exit. The task or exit will not beable to execute.

User response

This error should only occur during producttermination or if the main product address space is notexecuting. If this error occurs at any other time,contact Software Support. The main product addressspace will have to be restarted if this error is reported.

AZK0046W Initialization procedure procedureor IRXJCL ended with conditioncode rcode - processing continues

Explanation

IRXJCL was attached to execute the initializationprocedure. The reported non-zero condition code wasset after execution.

rcode (the return code) may in this case also be acondition code.

User response

Check the initialization exec for REXX-language errorswhich might cause the return code to be set. It may beimpossible to distinguish between IRXJCL's returncode and the return code set by the procedure.

AZK0047I DATASPACE procedure CREATEDTIME = t2 BY %PM

Explanation

DSPSERV system service routine was invoked atinitialization. A dataspace has been created.

User response

None required. This is an informational message.

AZK0048E DSPSERV ERROR. RETURN CODE =rcode. t2 %PM


Explanation

DSPSERV system service routine was invoked atinitialization to create a dataspace. However, itreceived a non-zero return. The dataspace was notcreated.

User response

Check the return code displayed in the message in theAuth Assembler Services Reference, and takeappropriate action, if possible. If the problem cannotbe resolved, contact Software Support.

AZK0049I Dataspace added to PASN list. t2%PM

Explanation

ALESERV system service routine was invoked atinitialization to add this address space to a previouslycreated dataspace.

User response


AZK0050W var1 configuration requires anupdate, certain features will needmodification, executioncontinuing.

Explanation

None.

User response


AZK0053S Configuration issue: processormodel number (modelno) does notmatch configured model;execution continues.

Explanation

None.

User response


AZK0054H var1 Configuration installed untilvar2 (var3 parameter).

Explanation

None.

User response


AZK0055E csect not found within %PMprimary load module

Explanation

During subsystem initialization, the indicated controlsection (CSECT) was missing from the product'sprimary execution load module.

User response

Initialization of the subsystem is terminatedimmediately with an S0C3 abend. Contact theSoftware Support group.

AZK0056E Invalid data found in csect loadedat addr ivdata

Explanation

During subsystem initialization, invalid data wasdetected within a control section (csec) or table loadedas part of the product's primary execution loadmodule.

ivdata represents a hex dump of the invalid data area.

User response

Initialization of the subsystem is terminatedimmediately with an S0C3 abend. Contact theSoftware Support group.

AZK0057W var1 rejected for use - var2 var3.

Explanation

None.

User response


AZK0058W var1 refresh required in var2 days.

Explanation

None.

User response


AZK0059S Configuration issue: H/Wprocessor ID var1 mismatchedconfiguration for var2 of past var3hours.


Explanation

None.

User response


AZK0060T LATCH SET CREATED: LS-NAME=lsname LATCHES=lcountLS-TOKEN=lstoken additinfo

Explanation

Information written to trace when a new latch set iscreated within the address space

User response

None.

AZK0061E LATCH ERROR: reqtype errdescadditinfo

Explanation

An error or unexpected condition was detected in alatch manager internal support routine

User response

Look for related messages indicating the cause of theerror and correct the underlying problem. If theproblem cannot resolved, contact Software Support.

AZK0062T LATCH operation:LSTOKEN=lstokenLATCHNO=latchnoLTOKEN=lstoken RQSTR=reqIDadditinfo

Explanation

Information written to trace when a latch is obtained,released, or purged

User response

None.

AZK0063S z/OS Version must be at 1.13 orhigher. Execution terminating.

Explanation

The product checked the host system and found thatthe host system is not running at z/OS 1.13 or higher.The product does not support z/OS levels below 1.13.

User response

The product only supports z/OS 1.13 and higher. z/OS1.13 or higher will have to be installed before theproduct can be fully supported.

AZK0064T Interval summary operation. SMLHat addr1 SMLG at addr2. Tag:additinfo

Explanation

Interval recording encountered an internal controlblock error while creating an interval summary record.

User response

The interval record in error is discarded andsummarization continues. If the problem cannot beresolved, contact Software Support.

AZK0065T Interval summary %1: %2

Explanation

This messages contains the number of intervalsummary record errors found.

User response

Contact Software Support.

AZK0066S Logon of the address space userID userID failed. Detected at addr.

Explanation

The product failed to create a security environment fora task using the user ID of the address space.

User response

There may be one or more additional error messagesor abends referring to the problem. If possible, fix theproblem identified by the error messages, and restartthe product. If the problem cannot be resolved,contact IBM Software Support.

AZK0067S LOGON of the SSLUSERID, userID,failed. Detected at addr.

Explanation

The product failed to create a security environment fora task using the userid specified in SSLUSERID.

User response

There may be one or more additional error messagesor abends referring to the problem. If possible, fix theproblem identified by the error messages, and restart


the product. If the problem cannot be resolved,contact Software Support.

AZK0068T Logon of user ID userID failed.

Explanation

Logon failed for user ID specified in Services request.

User response

Check whether user ID is valid or if the password wascorrect.

AZK0069W The severity level of messagecannot be changed.

Explanation

None.

User response


AZK0080E Control block cblk could not belocated

Explanation

The product tried to find one of several control blocksduring product initialization. One of the control blockscould not be found.

User response

Ensure that the version of the host (MVS™) operatingsystem is supported by the product. If the hostoperating system version is supported by the product,check for any other error messages referring to thecurrent problem. If possible, fix the problem identifiedby the error messages, and restart the product. If theproblem cannot be resolved, or if the host operatingsystem version is not supported by the product,contact Software Support.

AZK0081E Unknown host operating system -prodname

Explanation

The product was not able to identify the host operatingsystem by its product name.

User response

Ensure that the version of the host (z/OS) operatingsystem is supported by the product. If the operatingsystem is supported by the product, check for anyother error messages that refer to the currentproblem. If possible, fix the problem identified by the

error messages, and restart the server. If the problemcannot be resolved or if the operating system is notsupported, contact Software Support.

AZK0082I count1 online CPs and count2online zIIPs detected

Explanation

This informational message identifies the number ofonline general purpose processors (CPs) and zIIPsdetected during product initialization.

User response

None. This message is for informational purposes only.

AZK0083I LPAR lpar. CEC MSUs: cap1. LPARMSUs: cap2. Current® avg. var

Explanation

This informational message identifies the LPAR andthe capacity of the processors.

var is only relevant if z/OS is a VM guest.

User response


AZK0084I Decimal float support ind availableon this processor

Explanation

This informational message identifies whether decimalfloat support is available or not (ind).

User response


AZK0090I TSOSRVACTIVE(YES) INVALID INPROB STATE - SIMULATED USINGTMP IN CURRENT A/S

Explanation

This message is issued when TSOSRVACTIVE(YES) hasbeen specified as a start-up parameter, but theproduct is running in test mode under TSO. Theoutboard facility cannot be enabled/managed withoutbeing authorized to operate in supervisor state andoperating as an MVS started task.

User response

The outboard TSO server facility is not activated.Outboard TSO server facilities will be simulated usingTSO/E (if available) within the current address space.You should re-test applications developed under


TSO/E when moving them to an authorized copy of thesubsystem, because some operations (such as timelimit processing, CPU time monitoring) cannot besimulated properly within a test copy of the productrunning in problem state.

AZK0091E service OF desc FAILED, RC=rcode

Explanation

This is a generic error message used to describe awide variety of TSO/SRV initialization, execution, andtermination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current TSO/SRV problem. If possible, fix theproblem identified by the error messages, and restartthe product.

AZK0092E CANCEL of server jobname(ASID=asid) failed

Explanation

Server address spaces which will not shutdown in anormal way (e.g. a long running server task that is stillexecuting) are canceled. If the cancel is not acceptedfor any reason, this message is issued.

User response

If the server address space survives producttermination you may attempt to cancel it manually orpossibly even force it. The fact that a server addressspace (asid) remains in the system when the productis restarted will have no harmful effect on productexecution and can be ignored.

AZK0093I Waiting for TSO server terminationto complete

Explanation

Inactive servers have been posted to shutdown. Thetermination process will wait for a short time to allowthe servers to shutdown normally. If, at the end of thisperiod, any servers are still active, they will becanceled.

User response


AZK0094S service OF desc FAILED, RC=rcode

Explanation

This is a generic error message used to describe awide variety of TSO/SRV execute queue initializationand termination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and restart the product.

AZK0095S MAIN TASK TIMED OUT WHILEWAITING TO BE POSTED BY THETSO/SRV SUBTASK

Explanation

The product main task timed out while waiting to beposted by the TSO/SRV subtask. The TSO/SRV subtaskhas either terminated abnormally or is hung. Theproduct may or may not be able to continueprocessing.

User response

Check for other abends or product messages relatedto this one. If the problem cannot be resolved, contactSoftware Support.

AZK0096S TSO/SRV ABEND abcodeOCCURRED AT modname+offsetDURING desc

Explanation

This error message describes an abend that occurredduring TSO/SRV execute queue processing terminationprocessing (desc).

User response

There may be one or more error messages related tothe current problem. If possible, fix the problemidentified by the error messages, and restart theproduct. If the problem cannot be resolved, contactSoftware Support.

AZK0097I service OF desc FAILED, RC=rcode

Explanation

During server termination, product ow found that abusy TSO server did not respond to an internalshutdown request. An attempt to issue an MVSCANCEL command to terminate the server failed.


User response

None. The transaction running in the server willeventually complete. The subsequent attempt to readfrom an additional TSO/SRV command will fail, and theserver will then terminate following a 614 abend.

AZK0101S %PM PRODUCT USAGE EXCEEDSSPECIAL CONFIGURATIONLIMITS: var1

Explanation

None.

User response


AZK0102S EXCESS USAGE - LOCATIONS:var1, DRIVER TYPES: var2, HOSTBUSINESS SYSTEMS: var3

Explanation

None.

User response


AZK0103H Access restricted to TCP/IP - LU6.2 support not activated

Explanation

None.

User response


AZK0104H No usage parameter specified.Usage specific to basicadministrative functions and SIS.

Explanation

None.

User response


AZK0105I TEST DATE var1 (var2) FORCONFIGURATION, D-O-C(var3var4), var5

Explanation

None.

User response

None. This is an informational message only.

AZK0106S Version 7 Configuration required,contact Software Support.

Explanation

None.

User response:Contact IBM Software Support.

AZK0107S Server parameter required,contact Software Support.

Explanation

None.

User response


AZK0110H INITIALIZATON OF QUICKREFINTERFACE FAILED, VERIFYQUICKREF DSN AND INSTALLSTATUS

Explanation

This message shows that the product was unable toinitialize the QUICKREF interface.

User response

If QUICKREF is installed on this system, verify that theQUICKREF load library is either in the linklist or isallocated via the QWREFLIB DD statement in thestarted task JCL. If QUICKREF is not installed on thesystem, remove all references to QUICKREF from thestarted task JCL.

AZK0111S Invalid DB2® subsystem ID subsysset by LOGDB2SUBSYS parameter

Explanation

An invalid Db2 subsystem was specified for loggingusing the LOGDB2SUBSYS parameter. The specifiedDb2 subsystem does not exist, or has not beeninstalled and activated on the system since theprevious IPL.

User response

Specify a valid Db2 subsystem for logging using theLOGDB2SUBSYS parameter. If logging is not desiredspecify 'NONE' for LOGDB2SUBSYS. You may alsoleave LOGDB2SUBSYS unset in which case the defaultDb2 subsystem set for the server automatically or by


the DEFAULTDB2SUBSYS parameter will be used, ifvalid. Product initialization is terminated.

AZK0112S Invalid default DB2 subsystemsubsys set byDEFAULTDB2SUBSYS parameter

Explanation

A default Db2 subsystem ID was explicitly specifiedvia the DEFAULTDB2SUBSYS parameter, but does notdesignate a valid Db2 subsystem ID. When theDEFAULTDB2SUBSYS parameter is explicitly set (toany value except 'NONE'), the target Db2 subsystemID is verified. The ID will fail validation if the targetDb2 subsystem does not exist or has never beensuccessfully activated in the system since the last IPL.

User response

The product terminates if an explicitly specified ID isinvalid, but will allow startup to continue if it selectedthe default subsystem ID automatically. (The serveruses the default Db2 ID from the DSNHDECP loadmodule or the standard string, 'DSN ', if no explicitsetting is provided for the DEFAULTDB2SUBSYSparameter). Product initialization is discontinued andthe server terminates. Specify a valid default Db2subsystem for DEFAULTDB2SUBSYS or leave theparameter unset to allow an automatically assigneddefault value to be used.

AZK0113W DEFAULT DB2 SUBSYSTEM ID(subsys) FROM DSNHDECP ISINVALID, CONTINUING

Explanation

The default Db2 subsystem ID selected automaticallyby the server is not a valid Db2 subsystem ID. Theserver has selected the Db2 subsystem IDautomatically because no value was set for theDEFAULTDB2SUBSYS parameter. The server uses thedefault Db2 ID from the DSNHDECP load module, or, ifDSNHDECP cannot be loaded, uses the standard value'DSN ' as the default ID. Db2 operations which do notexplicitly send a Db2 subsystem ID will fail becausethe default subsystem ID is invalid. In addition,MSG0114W may be issued following this message ifDb2 logging is inhibited because of it's dependencyupon the default Db2 subsystem ID validity.

User response

Specify a valid default Db2 subsystem ID via thestartup DEFAULTDB2SUBSYS parameter, or specify'NONE' for this parameter if Db2 should not be used.Product initialization continues. Note that the Db2subsystem need not be active (up) when the Server is

started, however, it must have been successfullyinstalled and started on the system at least once priorto server startup.

AZK0114W DB2 logging will not be activated -requires valid default DB2subsystem ID

Explanation

The default Db2 subsystem ID set automatically by theserver (from the DSNHDECP load module) is not validand no explicit value was set for the LOGDB2SUBSYSparameter. Since Db2 logging requires a valid defaultDb2 ID, the value 'NONE' is forced for LOGDB2SUBSYSand Db2 logging is not activated.

User response

Specify a valid Db2 subsystem ID as the default Db2using the DEFAULTDB2SUBSYS parameter. If you donot wish to set a global default Db2 subsystem ID forall operations, but desire Db2 logging to be activated,specify a valid ID for LOGDB2SUBSYS instead. DB2logging will not be activated during the current serverstartup.

AZK0115E LE/370 INTERFACE MODULECEEPIPI CANNOT BE LOADED - ITIS REQUIRED FOR SSL SUPPORT

Explanation

During initialization, it was determined that the MVSLanguage Environment® interfaces are needed forexecution of the subsystem. SSL support requires theuse of LE/370 interfaces. The interface module,CEEPIPI, was not found in STEPLIB or the link list.

User response

Product initialization is abandoned. To restart thesubsystem, ensure that either the LE/370 runtimelibraries are available in STEPLIB or the link list, orturn off the SSL support option.

AZK0116W DB2 logging cannot be activatedwhen DB2 SUBSYS default is'NONE', logging deactivated

Explanation

The Db2 logging feature of the product cannot be usedwith a default Db2 subsystem setting of 'NONE'. TheDEFAULTDB2SUBSYS parameter must be set to anactual Db2 subsystem ID, or left un-specified. Since'NONE' was set ALL DB2 PROCESSING IS INHIBITED.This message is only issued when the LOGDB2SUBSYSparameter has explicitly been set to a Db2 subsystemID value other than 'NONE'. The LOGDB2SUBSYS


parameter is ignored and reset to 'NONE' so that itmatches the DEFAULTDB2SUBSYS parameter. Thisprevents Db2 logging activation. Product initializationcontinues without activating Db2 logging.

User response

Specify a valid default Db2 subsystem ID forDEFAULTDB2SUBSYS or leave that parameter unset (ifunset, the default value is fetched from theDSNHDECP load module). Product initializationcontinues with NONE set for bothDEFAULTDB2SUBSYS and LOGDB2SUBSYS.

AZK0117S type TCP/IP port number is invalid- type TCP/IP processingterminated

Explanation

The TCP/IP port number specified for one of the typesof TCP/IP (type) supported by the product is invalid.The main product address space cannot completeinitialization if an invalid TCP/IP port number has beenspecified for any type of TCP/IP.

User response

Specify a valid port number for the type of TCP/IP thatdetected the invalid port number. If the type of TCP/IPis not needed, you can also just not set the TCP/IP portnumber at all for the failing type of TCP/IP.

AZK0118S Load balancing not available - VCFfeature code is required.

Explanation

None.

User response


AZK0119W Logging not available - DB2feature code is required.

Explanation

None.

User response


AZK0120I SEF msgtext

Explanation

The product tried to initialize SEF during productinitialization. SEF initialization failed.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current SEF initialization problem. Check for openerrors, such as security product related abends. Also,check for storage allocation errors or abends. Ifpossible, fix the problem identified by the errormessages, and restart the product. If the problemcannot be resolved, contact Software Support.

AZK0121W SEF - service OF desc FAILED,RC=rcode

Explanation

The product tried to initialize or terminate SEF duringproduct initialization or termination. An internalservice routine called during SEF initialization ortermination exited with a non-zero return code.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current SEF initialization or termination problem.Check for open errors, such as security product relatedabends. Also, check for storage allocation errors orabends. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0122S ABEND abcode REASON rsnOCCURRED AT modname+offsetDURING SEF desc

Explanation

The product tried to initialize or terminate SEF duringproduct initialization or termination. The SEFinitialization/termination routine abended.

User response

Check the error messages and the abend codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current SEF initialization or termination problem.Check for open errors, such as security product relatedabends. Also, check for storage allocation errors orabends. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0123T SEF initialization complete


Explanation

The product has completed SEF initialization. Alltriggers and events will now be passed to the SEF forprocessing.

User response

No action is required in response to this message.However, this message can be used to activate one ormore event handling procedures.


Explanation

This is a generic error message used to describe awide variety of SEF execute queue initialization andtermination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do.

User response


AZK0127S MAIN TASK TIMED OUT WHILEWAITING TO BE POSTED BY THEsubtask SUBTASK

Explanation

The product main task timed out while waiting to beposted by an SEF subtask. The SEF subtask has eitherterminated abnormally or is hung. The product may ormay not be able to continue processing.

User response


AZK0128S Dynamic definition of ddnamelibrary failed

Explanation

The mapping data set could not be defined properly toallow for caching of map data members.

User response

Check for other abends or product messages relatedto this one, and contact Software Support.

AZK0130H Initializing secur release relsecurity environment

Explanation

This message shows that the product was able tosuccessfully initialize the security environment for theinterface between the product and ACF2 or RACF®.The message shows the security product (secur) andrelease level (rel) to which the interface wasestablished.

User response

No action is required unless the customer is notrunning any security package and one was identified orthe release level is incorrect. Contact SoftwareSupport if such an error is detected.

AZK0131S subsysID SSCT chain scanningerror

Explanation

The SSCT chain was scanned by the security interfaceroutines looking for ACF2 or RACF. Some error existsin the SSCT chain and the search could not becontinued.

User response

Examine the SSCT chain for an invalid chain or SSCTcontrol blocks. If the problem cannot be resolved,contact Software Support.

AZK0132W No security package found

Explanation

The SSCT chain was scanned by the security interfaceroutine looking for one of the known securitypackages: RACF, CA ACF2 or CA Top Secret. No knownsecurity product was found and the security packagefield was set to NONE.

User response

If no security package exists on your system, this isnot an error, and no further action is needed. If RACF,CA ACF2 or CA Top Secret is active and this messagewas received, contact Software Support.

AZK0133E relno release unknown, releasecode is relno

Explanation

The product attempted to recognize the release level(relno) of ACF2 and did not find a release level that itrecognized or that is supported. As of this date, all CA-


supported releases of ACF2 are supported by theproduct.

User response

If your release of ACF2 is supported by CA, contactSoftware Support to request that support be added forthat release of ACF2. If the release number appears tobe in error, contact Software Support for assistance.

AZK0134W RUNAUTH USERID cacheinitialization failed - sharing ofRUNAUTH USERIDs now disabled

Explanation

During start-up, the SHARERUNAUTHACEES optionwas set to ON, but an error occurred while initializingthe cached RUNAUTH userid table. This is likely due toa GETMAIN failure.

User response

Product initialization continues with theSHARERUNAUTHACEES option set to OFF. Examinethe wraparound trace and console messages for anexplanation of the error. If you are unable to locate thereason for the failure, contact Software Support.

AZK0135W Security routine failed attemptingto validate the LOGUSERID userID.RC=rcode.

Explanation

The internal security service routine failed whileattempting to verify a new USERID for the logging task.

User response

Check the error messages and the return codeassociated with this problem. There may be additionalerror messages in the system log. If possible, fix theproblem identified by the error messages, and restartthe product. If the problem cannot be resolved,contact Software Support.

AZK0136W LOGUSERID (userid) LOGONFAILED rcode1 rcode2 rsncode -msgtext

Explanation

An error occurred while attempting to verify a newUSERID for the logging task. This is a securityenvironment error.

This message contains two return codes; rcode1represents the security module return code, andrcode2 represents the RACF (SAF) return code.

User response

Product logging continues with the previous USERIDused for logging. Correct the value in the LOGUSERIDparameter.

AZK0137S ABEND abcode REASON rsnOCCURRED AT modname+offsetDURING SOM desc.

Explanation

An ABEND occurred during initialization or terminationof the Security Optimization Management feature.

User response

Check the error messages and the abend codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current initialization or termination problem. Checkfor security product related abends and storageallocation errors or abends. If possible, fix the problemidentified by the error messages, and restart theproduct. If the problem cannot be resolved, contactSoftware Support.

AZK0138W SOM facility is not available forpkg. Processing continues.

Explanation

Security Optimization Management (SOM) wasrequested, but the security package (pkg) is not RACF.SOM can only be enabled for RACF.

User response


AZK0139W Dynamic service services are notavailable

Explanation

An MVS dynamic LPA service is not available.

User response


AZK0140I The following catch-up rulesrequire a final catch-updisposition

Explanation

This message is issued when there are catch-upmanual rules which did not fire during the previousexecution of the product. It is followed by message0141I, which documents the unfired rules.


User response


AZK0141I rule.rsname1, rule.rsname2 …rule.rsname7

Explanation

This message is issued when there are catch-upmanual rules which did not fire during the previousexecution of the product. It lists up to seven rules thatdid not fire, using the format ruleset.rule. Multiplemessages may be issued so that all catch-up manualrules may be listed.

User response


AZK0142R Reply 'YES' to catch-up all rules,'NO' to bypasscatch-up, or'MANUAL' for rule by ruleprompting

Explanation

This message is issued when there are catch-upmanual rules which did not fire during the previousexecution of the product. It allows you to fire all catch-up manual rules, prevent all catch-up manual rulesfrom firing, or specify the type of catch-up processingfor each individual rule. It follows messages 0140Iand 0141I. If more than two minutes expire whilewaiting for your reply or three invalid replies are made,the default action of NO will be taken.

User response

Reply YES to cause all catch-up manual rules to fire.Reply NO to prevent all catch-up manual rules fromfiring. Reply MANUAL and you will be prompted tospecify the type of catch-up processing for eachindividual rule.

AZK0143R Reply 'YES' to catch-uprsname.rulename rule or 'NO' tobypasscatch-up

Explanation

This message is issued when there are catch-upmanual rules which did not fire during the previousexecution of the product and you selected MANUAL inyour reply to message 0142R. The name of the ruleyou are being prompted for is in the format ruleset.rulename. If more than two minutes expire while waiting

for your reply or three invalid replies are made, thedefault action of NO will be taken.

User response

Reply YES to cause the rule to fire. Reply NO toprevent catch-up firing for the rule.

AZK0144E Invalid catch-up manual reply:reply

Explanation

An invalid reply was specified to one of the catch-upmanual console messages. The message causing theerror will be reissued so that you can correctly reply.After three invalid replies for the same message,default action will be taken. For a description of thedefault action, see the explanation of the originalmessage.

User response

Determine the proper reply from the text of themessage, and reply correctly.

AZK0145E Catch-up reply wait exceeded 2minutes. Default used

Explanation

The product waited over two minutes for a reply to oneof the catch-up manual messages. Since no responsewas made during that time, default action was taken.

User response

None. If a reply was desired, you will need to speedyour response to the message.

AZK0146E 3 Invalid catch-up replies. Defaulttaken

Explanation

Three invalid replies were made to a catchup manualmessage. Since no correct response was received,default action was taken.

User response

None. Reply as required next time.

AZK0147E Catch-up service service forvariable varname failed, RC=rcode.

Explanation

An internal error was encountered during catch-upprocessing performing an AZKVALUE or SWSVALUEfunction.


User response


AZK0148W Catch-up rule rsname.rulenamehas changed. Catch-up bypassed.

Explanation

This message is issued when a catch-up rule has beenmodified since the last time the rule was enabled. Therule would otherwise have fired for catch-up becauseeither the product or z/OS was down during the lasttime the rule should have fired. Because the rule haschanged, it will not fire for catch-up.

User response

None.

AZK0149E Catch-up rule rule global variablewrite failed, RC=rcode

Explanation

This message is issued when a catch-up rule attemptsbut fails to write a global variable describing the nexttime to fire. As a result, catch-up processing for therule will fail the next time the product is restarted. Thisnormally occurs when the GLOBALMAX startupparameter has been exceeded and it is no longerpossible to create new global variables. Return code93 indicates that GLOBALMAX has been exceeded.Additionally, every time the TOD rule fires, the internalglobal variable is updated, and return code 4 will bedisplayed in this message.

User response

Shut down the product, and allocate a larger SYSCHK1data set. This may not be necessary if you alreadyhave a large data set but are only using a part of it dueto a small GLOBALMAX value. Use the IDCAMS REPROcommand to copy the existing database to the newlarger one, if necessary. Increase the value assigned tothe GLOBALMAX parameter in your initial parametersettings, and restart the product.


Explanation

This is a generic error message used to describe awide variety of trace initialization and terminationerrors. The message text provides the currentoperation (service) and what the current operation wastrying to do.

User response


AZK0151S service OF dsname FAILED,RC=rcode, REASON CODE=rsncode

Explanation

This error message describes errors that occurredduring trace initialization, execution, or terminationwhile using the DIV (Data In Virtual) system service.For a list of the return codes and reason codes fromthe DIV macro see the appropriate IBMdocumentation.

User response

Check the DIV return and reason codes associatedwith this problem. There may be one or more errormessages referring to the current problem. If possible,fix the problem identified by the error messages, andrestart the product. If the problem cannot be resolved,contact Software Support.

AZK0152S service OF dsname FAILED,ABEND=abcode, REASONCODE=rsncode

Explanation

This error message describes an abend that occurredduring trace initialization, execution, or terminationwhile using the DIV (Data In Virtual) system service.The abend codes and reason codes from the DIVmacro are documented in the IBM manual z/OSProgramming: Assembler Services Reference.

User response

Check the DIV abend and reason codes associatedwith this problem. There may be one or more errormessages referring to the current problem. If possible,fix the problem identified by the error messages, andrestart the product. If the problem cannot be resolved,contact Software Support.

AZK0153H ddname data set not allocated

Explanation

Product has detected that a TRACE DD card is notpresent in the JCL used to start the main productaddress space.


User response

Modify the JCL and specify the TRACE DD card aftervalidating that the necessary DIV data set is allocated.

AZK0154S Any existing Trace Browse datadiscarded

Explanation

Product detected this error.

User response


AZK0155S Please standby - upgrading TraceBrowse - all data retained

Explanation

The product is upgrading the Trace Browse data area.The Trace Browse data area must be upgradedwhenever messages from an earlier version of theproduct are detected in the Trace Browse data area.The upgraded Trace Browse data area is compatiblewith earlier releases of the product, as required.

User response

There is no action required in response to thismessage. This message should only be displayed oncewhen you install the first release of the product thatsupports the upgraded data area format. You may alsosee this message again if a prior version of the productis used after the Trace Browse data area has beenupgraded. The message will be deleted as soon as theTrace Browse data area upgrade is completed. Theupgrade requires about 3 minutes for every 100,000messages. If this message recurs, contact SoftwareSupport for additional assistance.

AZK0156S service PASSED desc - code

Explanation

This is a generic error message used to describe awide variety of trace initialization and terminationerrors. The message text provides the currentoperation (service) and what data (valid or invalid) waspassed to the current operation.

User response


AZK0160S Possible shortage of storage, bytesbytes required for Trace Browse

Explanation

This is a follow-up message to message 0150S when aGETMAIN has failed. This message indicates the size,in bytes, of the area requested by the GETMAIN.

User response

If the GETMAIN return code indicates insufficientstorage to complete the GETMAIN request, pleaseincrease your available storage (above the 16MB line)by the indicated amount.

AZK0161S Main task timed out while waitingto be posted by the TRACE subtask

Explanation

The product main task timed out while waiting to beposted by the trace subtask. The trace subtask haseither terminated abnormally or is hung. The productmay or may not be able to continue processing.

User response

Check for other abends or messages related to theproduct prior to this one, and contact SoftwareSupport for additional assistance.

AZK0162S service OF dsname FAILED,ABEND=abcode AT modname+offset, REASON CODE=rsncode

Explanation

This error message describes an abend that occurredduring trace initialization, execution, or terminationwhile using the DIV (Data In Virtual) system service.The abend codes and reason codes from the DIVmacro are documented in the IBM manual z/OSProgramming: Assembler Services Reference.

User response


AZK0165I SEF msgtext

Explanation

SEF subtask mapping information messages.


User response

None at this time.

AZK0166E Unable to build process block forSEF interface, RC=rcode

Explanation

Services startup was unable to build the environmentto interface to the SEF task. The return code is given.

User response

Check the return code and look for other errormessages which may explain the error.

AZK0167E Ruleset rule specifies DSNdsname, should be dsname forVirtualDirectory dir.

Explanation

Services startup found a Virtual Directory with aRuleset whose dataset name did not match theexisting Ruleset dataset name. This Virtual Directory(dir) is not initialized.

User response

Correct the inconsistency between rulesets anddataset names in all related virtual directories.


Explanation

This error message describes errors that occurredduring global variable initialization, execution, ortermination while using the DIV (Data In Virtual)system service. For a list of the return codes andreason codes from the DIV macro see the appropriateIBM documentation.

User response



Explanation

This error message describes an abend that occurredduring global variable initialization, execution, ortermination while using the DIV (Data In Virtual)system service. For a list of the return codes andreason codes from the DIV macro see the appropriateIBM documentation.

User response


AZK0173W ddname data set not allocated

Explanation

The product has detected that either a SYSCHK1 or aSYSCHK2 DD card is not present in the JCL used tostart the main product address space.

User response

Modify the JCL, and specify an appropriate DD cardafter validating that the necessary DIV data set isallocated.

AZK0174S Any existing global variables datadiscarded

Explanation

The product detected this error.

User response


AZK0175I Global variable upgrade vartext

Explanation

Prior to version 02.01.01 of the product, globalvariables were maintained in a linked list. As of version02.01.01, they are kept in an AVL tree structure forimproved performance. This message indicates thatthe global variable pool is being upgraded to the newformat. This message may also be issued as a result ofsetting the GLOBALREBUILD parameter to YES orwhen the global variable database has been corrupted.

User response



AZK0176S Duplicate global variable found,name=varname

Explanation

While building/rebuilding the global variable AVL tree,an attempt was made to add a node to the tree, andthe node already existed in the tree. The second valueis ignored, and the tree build/rebuild continues.

User response

Report this message to Software Support. Thissituation has occurred due to a prior logic error.

AZK0177S Main task timed out while waitingto be posted by the global variablecheckpoint subtask

Explanation

The product main task timed out while waiting to beposted by the global variable checkpoint subtask. Theglobal variable checkpoint subtask has eitherterminated abnormally or is hung. The product may ormay not be able to to continue processing.

User response

Check for other abends or messages related to theproduct prior to this one, and contact SoftwareSupport.

AZK0178S errdesc DETECTED IN GLOBALVARIABLE LIST

Explanation

While building/rebuilding the global variable AVL tree,one of the following (errdesc) occurred: (1) an infiniteloop was detected in the sequential list, (2) an invalidentry was detected in the sequential list, or (3) aninvalid offset was detected in the sequential list. Thetree rebuild is terminated at this point. The productwill attempt to reconstruct the entire global variabledata set. Some global variables may be discarded.

User response

Report this message to Software Support. Thissituation has occurred due to a prior logic error orstorage overlay. The product should continue tofunction normally after the global variable data set hasbeen successfully reconstructed.

AZK0179I Global variable conversion fromversion vartext version

Explanation

Prior to version 02.02.00 of the product, globalvariables were limited to 256 bytes in size. As ofversion 02.02.00, this restriction is removed. Prior toversion 03.02.00 of the product, the key size waslimited to 50 bytes. As of version 03.02.00, the keysize limit is increased to 84 bytes. This messageindicates that the global variables are being convertedto a new format.

User response


AZK0180I GLOBAL VARIABLE CHAINREBUILD vartext, count GLOBALS

Explanation

While doing a global variable tree rebuild, it was foundthat the chained list was incomplete and needed to berebuilt. This message indicates the status of the chainrebuild process.

User response


AZK0181I varname BEING ADDED TO CHAIN

Explanation

While doing a global variable tree rebuild, it was foundthat the chained list was incomplete and needed to berebuilt. This message indicates which variables werereinserted back into the global variable chain.

User response


AZK0182I GLOBAL VARIABLE DATABASEBEING CONVERTED

Explanation

This is the first time version 02.02.00 of the producthas processed this global variable DIV data set. Theproduct is converting the global variable database tothe new format. The converted global variabledatabase will not be usable with older versions of theproduct unless the backward conversion utility issubsequently executed.

User response

Information only. No action required.

AZK0183S ABEND abcode OCCURRED ATmodname+offset DURING desc


Explanation

This error message describes an abend that occurredduring global variable subtask termination processing.This may also occur during an AVL tree rebuild duringstartup or when the GLOBALREBUILD parameter is setto YES.

User response

There may be one or more error messages related tothe current problem. In the case of the AVL treerebuild routine, the product will attempt to recover theglobal variable checkpoint data set by automaticallyrebuilding it. In all other cases, attempt to fix theproblem identified by the error messages, and restartthe product. If the problem cannot be resolved,contact Software Support.

AZK0184S desc storaddr1 storaddr2storaddr3

Explanation

A logical error was encountered while validating dataprior to a global variable checkpoint. The checkpointwill be aborted, and the product will be terminated toprevent incorrect data being saved. Changes to theglobal variable database since the previous checkpointwill be discarded.

User response

Attempt to restart the product. If the same erroroccurs, contact Software Support, giving them theinformation in this message. It may be possible toreconstruct the database by setting theGLOBALREBUILD parameter to YES prior to restartingthe product. If not, the global variable data set can berecovered from a prior backup.

AZK0185W GLOBALMAX VALUE OF val1 ISTOO LOW. RESET TO val2.

Explanation

The GLOBALMAX parameter value is too low andwould cause the global variable database to bedestroyed. The value has been ignored and reset to itsprior value. This scenario may have been caused by afailure in the product initialization REXX program orCLIST, which resulted in an attempt to use the defaultGLOBALMAX value.

User response

If this error was caused by a failure in the initializationREXX program or CLIST, attempt to determine thecause of failure as soon as possible. You may wish toshut down the product to prevent other problems from

occurring. The GLOBALMAX value may have beendefaulted due to such a failure. If you are reallyattempting to reduce the size of the global variabledata set, you must stop the product, delete andreallocate a new DIV data set, and then restart theproduct.

AZK0186S CONVERSION FAILED. INCREASEGLOBALMAX BY AT LEAST minval.

Explanation

The conversion of the SYSCHK1 database to theversion 03.02.00 format failed because theGLOBALMAX value is not large enough to contain theconverted data. The new database requires morespace than the old one due to the increased key size.The database may require up to twice as much spacein the worst possible case.

User response

Shut down the product, and allocate a larger SYSCHK1data set. This may not be necessary if you alreadyhave a large data set but are only using a part of it dueto a small GLOBALMAX value. Use the IDCAMS REPROcommand to copy the existing database to the newlarger one, if necessary. Increase the value assigned tothe GLOBALMAX parameter in your initial parametersettings, and restart the product. Adding this value willnot leave any free space in the SYSCHK1 data set. Youshould leave enough free space to account for growthin your system.

AZK0187I OLD IN-USE BLOCK COUNT -minval. NEW IN-USE BLOCKCOUNT - val.

Explanation

This informational message indicates how manyblocks of storage were being used in the SYSCHK1database prior to the conversion to the 03.02.00format and how many blocks of storage will now beused following the conversion.

User response

Compare the new in-use block count to yourGLOBALMAX value. If this value is close to theGLOBALMAX value, you may not have sufficient freespace for normal operation, and you should increasethe size of your SYSCHK1 database as soon aspossible.

AZK0188S INCOMPATIBLE SYSCHK1DATABASE LEVEL lvl, CANNOT BEUSED.


Explanation

The SYSCHK1 database is in a format that isincompatible with the current version of the product.This database has probably been converted to aformat supported by a newer version of the product.

User response

Use a version of the database that is compatible withthe current version of the product.

AZK0190E SEF STARTUP ERROR: var1,var2 ... var9

Explanation

A configuration parameter or environmental error wasfound during SEF service task initialization. Theproblem is related in some way to the enhancedimplementation of the System Web Interface (SWI)facility. Either parameters used to configure the SWIfacility conflict, or new restrictions that this version ofthe Server imposes have not been met.

User response

SEF service task initialization ends with an errorcausing the server to begin shutdown processing.Determine the cause of the error and correct theproblem or conflict. If the problem cannot beunderstood and resolved from the messagesproduced, contact Software Support.

AZK0191W SWI FACILITY WARNING: var1,var2 ... var9

Explanation

A configuration parameter or environmental error wasdetected during activation, termination, or processingby the System Web Interface (SWI) facility. The SWIfacility continues operation adjusting to the reportedcondition.

User response

Determine if the warning is anticipated or unexpected.If the warning reports an unexpected condition,correct the configuration or other problem beforerestarting the server.

AZK0192I SWI FACILITY: var1, var2 ... var9

Explanation

The System Web Interface (SWI) Facility has detecteda condition that might be of interest and reports itusing this message number. The message MIGHTindicate a configuration problem, or runtime problem,

depending upon the nature of the reportedinformation.

User response

If a recoverable condition is reported, check the SWIconfiguration that may contribute to the condition andcorrect prior to the next server restart.

AZK0193W SEFACTIVE = "NO" set - SEF ruleswill not be enabled during start-up .

Explanation

The SEFACTIVE parameter is set to "NO", so ruleenablement will not be performed during serverstartup. You can enable rules later by manually issuingENABLE SEF commands against defined rulesets.

User response

Determine if the warning is anticipated. If not, correctthe SEFACTIVE start-up parameter and restart theserver.

AZK0194W SEF start-up procedure endedwith special RC (8) - auto-enableof SEF rules bypassed - no SEFrules are enabled.

Explanation

The SxxxxINEF start-up procedure ended with RC=8,indicating rule enablement should be bypassed. Theserver will bypass rule enablement. You can enablerules later, manually, but until you do so, no eventrelated processing is performed by the SEF facility.

User response

Determine if the warning is anticipated. If not, correctthe SxxxxINEF start-up procedure and restart theserver.

AZK0195E XO DATASET ERROR: var1, var2 ...var9

Explanation

A configuration or runtime error was found while SEFwas processing an executable object (XO) dataset. XOdataset libraries contains pre-compiled SEF rules andHTX generation skeleton text files. They are usedprimarily to support the System Web Interface (SWI)facility distributed with the server.

User response

SEF terminates processing of the current operation,sometimes by generating an S0C3 ABEND if the


condition is severe. If error is severe SEF may beingtermination of the server. Check for related messageswhich may aid in problem determination. For SWI, besure the SWICNTLDSN start-up parameter is setcorrectly. Contact Software Support, if the problemcannot be determined or corrected.

AZK0196W SEF CONFIGURATION UPDATEvar1, var2 ... var9

Explanation

SEF is processing a configuration update, such asvalidating a ruleset definitions and placing the rulesetonline. A problem or warning is reported in thismessage if the configuration update is not completednormally.

User response

SEF continues processing of the next configurationupdate unless the error is severe. Correct the originalresource definition (e.g. "DEFINE RULESET" or"DEFINE FILE" in the SxxxxIN00 procedure) andresubmit the request.

AZK0197S Critical SEF resource definitionerror found - server startupaborting

Explanation

An error was detected in a critical SEF configurationresource definition. The server will begin terminationprocessing to avoid later problems when the SEF taskbegins execution.

User response

Check the console log for DEFINE RULESET definitionsentered via the SxxxxIN00 startup procedure. Thosedefinitions which are flagged with the keyword"INITERROR(ABORT)" and the definitions for ATH,WWW-Master, and TYP rulesets are consideredcritical. The server will not be allowed to start if thesedefinitions are in error. Correct the definitions andrestart the server.

AZK0200S MODE SWITCH ROUTINE serviceFAILED RC=rcode

Explanation

The product attempted to either acquire storage for abelow the line AMODE switch routine or free thestorage used by a below the line AMODE switchroutine. The storage management operation (service)failed.

User response

Check if the return code or any other messagesprovide additional information about the storagemanagement error. Also, check if the operating systemis short on storage in CSA. Start or restart the productif the storage management problem can be resolved.Contact Software Support if the problem cannot beresolved.

AZK0201S SSVT service FAILED RC=rcode

Explanation

The product tried to either acquire storage for a SSVTcontrol block or free the storage used by the SSVTcontrol block. The storage management operation(service) failed.

User response

Check if the return code or any other messagesprovide additional information about the storagemanagement error. Also, check if the operating systemis short on storage in CSA or ECSA. Start or restart theproduct if the storage management problem can beresolved. Contact Software Support if the problemcannot be resolved.

AZK0202S SAST UDPATE FAILED RC=rcode

Explanation

The product tried to update one of the subsysteminterface control blocks used by the system. Theupdate operation failed.

User response

Check the error messages associated with thisproblem. There may be one or more subsysteminterface error messages referring to the currentproblem. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0203S SAST PLIST STORAGE serviceFAILED RC=rcode

Explanation

The product tried to either acquire storage for theSAST update PLIST or free the storage used by theSAST update PLIST. The storage managementoperation (service) failed.

User response

Check if the return code or any other messagesprovide additional information about the storage


management error. Also, check if the product regionshould be increased. Start or restart the product if thestorage management problem can be resolved.Contact Software Support if the problem cannot beresolved.

AZK0204W Total subsystem count wascount1, reset to count2

Explanation

Many products (such as IMS) create new subsystemcontrol blocks and add them to the subsystem controlblock chain. Unfortunately, these same products donot update the subsystem control block count field.The product found that the actual count of subsystemcontrol blocks did not match the count value in themain operating system control block. The productupdated the overall count value.

User response

This is not an error message, and no action is required.

AZK0206E servrout errdesc FAILED,RC=rcode, DETECTED AT addr

Explanation

Some type of service routine (operating system orproduct specific) failed. The error message identifiesthe service routine and the type of error.

User response

Check the full text of the error message, and fix theprogram that calls the application program interface, ifnecessary.

AZK0207I JSAST TABLE ENTRY FOR subsysWAS indicator FOUND -FORCEJSASTUPDATE OPTIONACTIVE

Explanation

The FORCEJSASTUPDATE option is on. Thesubsystem's ID was or was not found in the JSASTtable. Updates to JESNRSS and the JSAST table will beunconditional due to the setting ofFORCEJSASTUPDATE.

The indicator variable (indicator) may be either null or"NOT".

User response

Initialization routines force execution of the JESNRSSUpdate and IEFJSBLD calls.

AZK0230W SERVER'S DFHSM PENDINGHRECALL TABLE IS FULL -DFHSMDRAIN(YES) FORCED

Explanation

More than 125 outstanding asynchronous HRECALLrequests remain to be posted as complete by DFHSM.The server is suspending DFHSM request processing.It automatically set the DFHSMDRAIN product optionto YES, so that no new HRECALL requests arescheduled until either (1) the number of pendingHRECALL requests drops below 100 or (2) theDFHSMDRAIN or DFHSMSTATUS options are changedmanually.

User response

Check for reasons why DFHSM HRECALL processingmay be delayed or disabled. Correct the DFHSMproblem, and then either wait for the server toautomatically set the DFHSMDRAIN(NO) option (once25 requests have been completed and cleared fromthe pending table) or manually change theDFHSMDRAIN parameter to NO. Before manuallychanging DFHSMDRAIN to NO, ensure that fewer than125 HRECALL requests remain outstanding.

AZK0231E DFHSM INIT/TERM ROUTINE,OPINHS, ENTERED WITH INVALIDFUNCTION CODE: code

Explanation

During start-up or shutdown, the DFHSM serviceroutine was entered with an invalid request code.

User response

This is a logic error. Contact Software Support forproblem resolution.

AZK0233E IBM-SUPPLIED DFHSM LOADMODULE, ARCGIVER, NOTINSTALLED/LOCATED - DFHSMSUPPORT DISABLED

Explanation

During start-up, DFHSM(YES) was selected to initializeDFHSM support. However, the server cannot locate acopy of the IBM-supplied DFHSM interface module,ARCGIVER. This module must be available within thelink list, LPA, or the server's STEPLIB load library.

User response

Server start-up continues, but the server resets theDFHSM option to NO, which prevents furtherinteractions with DFSMShsm from being undertaken.


Determine why the ARCGIVER module cannot belocated, and make it available during server start-up. IfDFSMShsm is not installed, do not attempt to set theDFHSM(YES) start-up option.

AZK0234E DFHSM INTERFACE DISABLEDDUE TO STORAGE ALLOCATIONERROR

Explanation

During start-up, DFHSM(YES) was selected to initializeDFHSM support. However, a storage acquisition errorhas occurred which will prevent the DFHSM interfacefrom operating.

User response

Server start-up continues, but the DFHSM option isreset to NO, which prevents further DFHSM operationsfrom occurring. See preceding messages to determinethe actual cause of the problem.

AZK0235I DFHSM support interfacesuccessfully initialized

Explanation

During start-up, the DFHSM(YES) was selected toenable DFHSM support. The server has pre-initializedits DFHSM support interface successfully.

User response

Server start-up continues. If DFHSM is not operational,the server may generate HRECALL requeststhroughout its operation which will immediately fail. IfDFHSM is not actually installed, change the DFHSMstart-up parameter to NO to prevent enablement ofDFHSM Support within the server. You may setDFHSMSTATUS(OFFLINE) at any time to prevent theserver from invoking DFHSM services until reset toDFHSMSTATUS(ONLINE).

AZK0236E ABEND DURING DFHSM servicePROCESSING -CMP=ccode,RS=rsncode,AT=modname+offset

Explanation

An abend was trapped during DFHSM processing.Information about the abend is written to the consolelog.

User response

The DFHSM interface retries, if possible, to preventsubsystem termination or failure. Check for othermessages which might indicate the cause of the

problem. If the problem cannot be resolved, contactSoftware Support.

AZK0237W HRECALL PENDING FOR dsname -MWE ECB AT addr UNPOSTED -ORPHANED

Explanation

During shutdown, an incomplete asynchronousDFHSM HRECALL request was detected. Theoutstanding request will cause 352 bytes of below-the-line CSA storage to be orphaned. This occursbecause an outstanding HRECALL request causes anMWE ECB to be allocated by DFHSM. The server isallowed to free the ECB only after DFHSM has postedthis ECB, which it has not yet done; DFHSM does notautomatically free this storage when the requestingaddress space terminates. Note that the orphanedCSA storage area actually begins some number ofbytes prior to the ECB address given in this message(consult IBM to determine the exact offset).

User response

Processing continues and the DFHSM MWE ECB isorphaned. The server does not attempt to rememberthese ECB addresses across a restart of the product.To prevent this condition, consider setting the server'sDFHSMSHUTDOWNWAIT parameter to allow a longerwait time limit for DFHSM hrecall completions duringshutdown. Also, ensure that the DFHSMSTATUSparameter has not been manually set to OFFLINE,which inhibits waiting and cleanup of pendingHRECALL requests.

AZK0238I SERVER'S PENDING RECALLTABLE NO LONGER FULL -DFHSMDRAIN(NO) RESET TO NO

Explanation

Earlier, the server had put DFHSMDRAIN(YES) intoeffect because its pending HRECALL table was full.The table now has 25 free entries, and the server isrestoring normal HRECALL processing.

User response

None. Normal HRECALL processing resumes.

AZK0239I SHUTDOWN SUSPENDING FOR UPTO sec SECONDS TO AWAITcount1 PENDING HRECALLCOMPLETIONS - count2

Explanation

During shutdown processing, one or more pendingHRECALL requests is still pending. The server will


pause to wait upon DFHSM to post these pendingrequests complete. Shutdown processing will re-commence after pausing for DFHSM completion.

User response

None. The server waits the length of time specified bythe DFHSMSHUTDOWNWAIT parameter for pendingcompletions.

AZK0240E count PENDING DFHSMREQUESTS (AND MWE's)ORPHANED BECAUSE rsn

Explanation

During shutdown processing, one or more pendingHRECALL requests MAY remain pending. However, theserver is bypassing product termination-time finalrecovery, checking for these requests.

User response

None. The server continues termination processingwithout attempting recovery/cleanup for pendingHRECALL requests. Bypassing DFHSM final recovery isnormally due to the parameterDFHSMSTATUS(OFFLINE) having been explicitly setand left in effect during product termination. Be sureto restore DFHSMSTATUS(ONLINE) before productshutdown if DFHSM is actually online.


Explanation

This is a generic error message used to describe awide variety of IMS initialization and terminationerrors. The message text provides the currentoperation (service) and what the current operation wastrying to do.

User response



Explanation

This is a generic error message used to describe awide variety of IMS initialization and terminationerrors. The message text provides the currentoperation (service) and what data (valid or invalid) waspassed to the current operation.

User response


AZK0253S service TO desc FAILED, RC=rcode

Explanation

This is a generic error message used to describe awide variety of IMS initialization and terminationerrors. The message text provides the currentoperation (service) and what the current operation wastrying to do.

User response


AZK0254S IMS rsrc name missing

Explanation

A resource (rsrc) name needed by the IMS productfeature is missing. The current operation will beterminated. The message text contains the name ofthe missing resource.

User response

Check the resource name in the error message. Set theresource name using a product parameter.

AZK0255H Build in-storage profile failed forclass class rcode1 rcode2 rsncode -errmsg

Explanation

The product received a non-zero return code from abuild in-storage profiles request for a specific class.

The message contains two return codes; rcode1represents the security module return code, andrcode2 represents the RACF (SAF) reason code.

User response

Check the security error for the class. Correct theproblem, or contact your security administrator forfurther assistance.


AZK0261I Server will use default filetypedefinitions for MIME CONTENT-TYPE mapping

Explanation

FILETYPE table definitions were not provided explicitlyby the initialization procedure. In the absence of ANYexplicitly defined entries, the server generates adefault set of definitions.

User response

Normally, no action in required, and you may prefer touse the built-in defaults provided by the server.

AZK0265E IDMS support cannot be enabled -module IDMS-module-name notfound

Explanation:The CA IDMS load module was not found in the serverstarted task JCL.

User response:Add the CA IDMS load libraries into the STEPLIB of theserver started task JCL.

AZK0270T Access to ACI feature is notconfigured.

Explanation

None.

User response


AZK0271W ACI internal service had toGETMAIN buffers

Explanation

ACI internal services are supposed to use above thebar buffer pools for storage. Some ACI services wereunable to obtain storage from the buffer poolconfigured. As a result, it had to resort to GETMAINservices for buffers.

User response

Examine the buffer pool statistics to determine whichbuffer pools need to be made larger. Also, be sure theinternal services are configured to appropriate bufferpools.

AZK0272I service errdesc, RC=rcode,RSN=rsncode, DETECTED AT addr

Explanation

ACI internal services initialization was unable to getlarge page storage for the ACI buffer pools asrequested.

User response

Allocate more storage for large pages to satisfy thebuffer pool requests. Standard page storage isobtained instead.

AZK0273T additinfo1, additinfo2 … additinfo9

Explanation

ACI tracing message. These messages will beproduced when ACITRACE is set to YES.

User response

None.

AZK0280S SSL msgtext

Explanation

The product tried to initialize SSL during productinitialization. SSL initialization failed.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current SSL initialization problem. Check for openerrors, such as security product related abends. Also,check for storage allocation errors or abends. Ifpossible, fix the problem identified by the errormessages, and restart the product. If the problemcannot be resolved, contact Software Support.

AZK0281S SSL KEY/CERTIFICATE FILE funcERROR, DD=ddname, RC=rcode

Explanation

The product tried to initialize SSL during productinitialization. SSL initialization failed because an erroroccurred while accessing the server's private key orcertificate file.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current SSL initialization problem. Check for openerrors, such as security product related abends. Also,check for storage allocation errors or abends. Ifpossible, fix the problem identified by the error


messages, and restart the product. If the problemcannot be resolved, contact Software Support toobtain additional assistance.

AZK0282S ABEND abcode OCCURRED ATmodname+offset DURING SSL desc

Explanation

The product tried to initialize or terminate SSL duringproduct initialization or termination. The SSLinitialization/termination routine abended.

User response

Check the error messages and the abend codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current SSL initialization or termination problem.Check for open errors, such as security product relatedabends. Also, check for storage allocation errors orabends. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0283T SSL initialization complete

Explanation

The product has completed SSL initialization. Alltriggers and events will now be passed to the SSL forprocessing.

User response


AZK0284S SSL user ID userID logon failed.

Explanation

The SSL manager userid specified by the SSLUSERIDsystem parameter, or the default server address spaceuserid failed logon processing during start-up.

User response

The HTTP-API initialization process is aborted. Ensurethat the userid specified by the SSLUSERID start-upparameter is correct. Refer to message AZK2107 formore information about the failure.

AZK0285I SSL manager user ID userIDlogged on to server.

Explanation

The SSL manager userid specified by SSLUSERIDsystem parameter has been logged on to the system.

User response

HTTP-API initialization processing continues.


Explanation

This is a generic error message used to describe awide variety of SEF execute queue initialization andtermination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do.

User response


AZK0287S MAIN TASK TIMED OUT WHILEWAITING TO BE POSTED BY THEsubtask SUBTASK

Explanation

The product main task timed out while waiting to beposted by an SSL subtask. The SSL subtask has eitherterminated abnormally or is hung. The product may ormay not be able to continue processing.

User response


AZK0288S SSL SERVER PRIVATE KEY/CERTIFICATE FORMAT INVALIDFOR ddname

Explanation

The SSL resource manager could not initialize becausethe server's private key or certificate file contains aninvalid key or certificate.

User response



AZK0289S SSL SUPPORT CANNOT BEENABLED - DDNAME ddname ISNOT ALLOCATED

Explanation

The SSL resource manager could not initialize becausethe server's certificate or private key file ddname is notallocated.

User response

The server will terminate. Check the start-up JCL toensure that the certificate file and/or private key filesare allocated to the correct ddnames.

AZK0290S SSL ERROR: msgtext

Explanation

The SSL routines logged a severe error message.

User response

The SSL routines logged a severe error to trace. Themessage is duplicated to the operator console.

AZK0291S SSL LDAP indicator NOTSPECIFIED

Explanation

SSL client authentication by an LDAP server wasrequested, but the name of the server or port(indicator) number were not specified.

User response

The server initialization process is aborted. Ensure thatthe correct server name and port number are specifiedwith the SSLLDAPSERVER and SSLLDAPPORTparameters.

AZK0292I GSK SSL SUPPORT CANNOT BEENABLED - SSLKEYPATHPARAMETER NOT SPECIFIED,CHANGING TO SSLEAY SUPPORT

Explanation

The SSL resource manager could not initialize GSK SSLbecause the SSLKEYPATH parameter was notspecified. GSK SSL requires this parameter. Theproduct will attempt to use SSLEAY SSL support.

User response

The GSK SSL support will not be enabled. If possible,SSLEAY SSL support will be used. If GSK SSL isdesired, code the SSLKEYPATH parameter and restartthe product.

AZK0293I A CALL TO THESET_DUB_DEFAULT UNIX SYSTEMSERVICE FAILED. RC=rcodeRS=rsncode

Explanation

Product initialization received an error return codefrom a call to the set_dbu_default service.

User response

Product initialization is terminated. Refer to the IBMUNIX System Services Messages and Codes manualfor an explanation of the return and reason codes. It ispossible that an OMVS segment was not created forthe product USERID. Refer to the the product ServerInstallation Guide for more information on creating theproduct USERID and the security that the USERIDrequires. If the problem cannot be resolved, thencontact Software Support to obtain additionalassistance.

AZK0320S Subroutine subrout was found inmodname1 but belongs inmodname2 at offset offset

Explanation

The subroutine definition is in the wrong module.

User response

Contact Software Support to obtain assistance.

AZK0321S Subroutine subrout at offsetoffset1 in module modname is outof sequence and should be offsetoffset2

Explanation

The subroutine is not defined in the correct position.

User response


AZK0322S Vector and list table offsets forsubroutine subrout in modulemodname do not match

Explanation

The offset into the vector table for the subroutine doesnot match the offset defined in the list table.

User response



AZK0323S Vector at offset offset in modulemodname points to subrout1 butshould point to subrout2

Explanation

The subroutine pointed to by the list table is not theone that was defined. The OPCOS% module vectortable entries do not agree with OPSBCL.

User response


AZK0324I service OF desc FAILED, RC=rcode,REASON=rsncode, DETECTED ATaddr

Explanation

An attempt was made to use zEDC services forcompression. If no zEDC engine was available or zEDCis not configured, this message may appear.

User response

If zEDC compression is not required, this messagemay be ignored. Otherwise, the return code andreason code will indicate the problem using zEDC.

AZK0325I service OF desc SUCCEEDED,DETECTED AT addr

Explanation

A succeeded for zEDC services for compression. zEDCservices are now available for use.

User response

None.

AZK0326T additinfo1, additinfo2 ...additinfo3, PGM=%SK

Explanation

A zEDC function call was made. The results are traced.

User response

None.

AZK0334I STOP command detected duringinitialization

Explanation

A STOP command has been detected by the productduring early product initialization. The initializationexec (SxxxxIN00) may or may not have completed

successfully. STOP commands issued after thecompletion of the initialization exec will not behonored until initialization has completed.

User response


AZK0335S ESTAE service ERROR RC=rcode

Explanation

The product tried to create an ESTAE recoveryenvironment. The ESTAE macro (service) failed.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore ESTAE error messages referring to the currentproblem. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0336S service of desc failed, RC=rcode.Detected at addr. stack: stkinfo.

Explanation

This is a generic error message used to describe awide variety of product initialization, execution, andtermination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and restart the product. If the problemcannot be resolved, contact IBM Software Support.

AZK0337E desc service ERROR RC=rcode

Explanation

Some type of process block pool error occurred duringproduct initialization or product termination. Themessage text provides the current operation (service)and what the current operation was trying to do.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the error


messages, and restart the product. If the problemcannot be resolved, contact Software Support.

AZK0338S INVALID desc LOCATED AT addrTAG IS tag

Explanation

The product found an invalid control block duringproduct termination. The control block tag (tag)contained an invalid character string.

User response

Check the error messages associated with thisproblem. There may be one or more error messagesreferring to the current problem. If possible, fix theproblem identified by the error messages, and restartthe product. If the problem cannot be resolved,contact Software Support to obtain additionalassistance.

AZK0339E count process block(s) still in use

Explanation

The product uses a pool of stack control blocks toprocess messages and other events. The stack blocksare obtained and released as required by a variety ofproduct routines. In some cases, a product routinemay fail to release a process block.

User response

No action is required to resolve this problem. Theproduct will release all of the space used by the stackcontrol blocks even if they appear to still be in use. Ifthe problem cannot be resolved, contact SoftwareSupport.

AZK0340I msgtext

Explanation

This message is not an error message. The currentmessage is used to display the output from theproduct initialization exec (SxxxxIN00) on the systemconsoles.

User response

Although the current message is not an error message,the output from the product initialization exec is onlysent to the product consoles if the initialization execterminates with a non-zero return code. The execmessages should be carefully checked for any errormessages. Restart the product, if necessary. ContactSoftware Support if the problem (non-zero exectermination code) recurs.

AZK0341T %PM feature codes are not set -contact Software Support forassistance

Explanation


User response


AZK0342T %PM is running on anunconfigured CPU.

Explanation

None.

User response


AZK0343T %PM configuration will needrefresh in x days.

Explanation

None.

User response


AZK0344T %PM configuration needs refreshon this system.

Explanation

None.

User response


AZK0345S DD allocation required in start-upJCL for proper execution of TSO/EREXX procedures.

Explanation

The server is attempting to intercept output from aTSO/E REXX procedure but could not open the outputdata set to which TSO/E REXX routes SAY statementand other output messages are directed. The mostlikely cause is that a site modification has been madeto IRXPARMS that specifies that TSO/E REXX shoulduse a non-standard ddname for output. SYSTSPRT, theIBM default, is assumed if the server is unable to loadand check the IBM-supplied load module, IRXPARMS.


User response

Ensure that the ddname indicated in the message ispre-allocated by the server's start-up JCL. (Theproduct-supplied sample JCL contains a SYSTSPRT DDstatement which can be used as a model for pre-allocating this data set.) If a DD statement is alreadypresent in the start-up JCL, ensure that this ddnamehas not been released through the use of an MVSDYNALLOC dynamic allocation request. This condition,if encountered while processing the SWSxIN00parameterization procedure, will not result in servertermination. However, any errors encountered whileexecuting this procedure cannot be successfullyreported.

AZK0346I NETWORKBUFFERSIZE valueinadequate for SQLMAXCOLUMNSvalue, raised to val

Explanation

The NETWORKBUFFERSIZE must be adequate to holdan SQLDA with the maximum number of columnsallowed, as specified by SQLMaxColumns. The exactformula is: NETWORKBUFFERSIZE >=SQLMaxColumns * 44 + 16

User response

The NETWORKBUFFERSIZE is raised to the sizecomputed by the above formula and then rounded to a1K (1024) byte boundary.

AZK0347I DSNREXX DB2 REXX INTERFACENOT FOUND, ADDRESS DSNREXXSUPPORT NOT ACTIVATED

Explanation

The load module DSNREXX for REXX interface to Db2was not found. Support for this API is not activated.Initialization continues normally.

User response

Support for ADDRESS DSNREXX is not enabled. This isnot necessarily an error, unless DSNREXX support isneeded.

AZK0348S Invalid registry block ivdata foundin logstream logstream

Explanation

The Registry Logstream contained a block which didnot pass validation (ivdata). The record is dropped,and will be deleted at the next update.

User response

Make a copy of the next Offload dataset for thislogstream and send it to Software Support.

AZK0349I regtype REGISTRY LOGSTREAMlogstream action

Explanation

The Registry Logstream was created, deleted, orconnected (action) to as part of initialization.

User response

None, this is normal processing.


Explanation

This is a generic error message used to describe awide variety of CICS® initialization and terminationerrors. The message text provides the currentoperation (service) and what the current operation wastrying to do.

User response



Explanation

This is a generic error message used to describe awide variety of CICS initialization and terminationerrors. The message text provides the currentoperation (service) and what data (valid or invalid) waspassed to the current operation.

User response


AZK0352W modname is not REENTRANT

Explanation

The product found that the EXCI options moduleDFHXCOPT or its alias DFHXCOPE is not REENTRANT.


This will cause some EXCI related product parametersto be ignored - for example the TIMEOUT parameter.

User response

Relink the module with the RENT option.


Explanation

This is a generic error message used to describe awide variety of CICS initialization and terminationerrors. The message text provides the currentoperation (service) and what the current operation wastrying to do.

User response


AZK0354S CICS rsrc NAME MISSING

Explanation

A resource (rsrc) name needed by the CICS productfeature is missing. The current operation will beterminated. The message text contains the name ofthe missing resource.

User response


AZK0355I CICS support terminating

Explanation

This is an informational message that is issued whenthe product terminates its CICS support. If the CICSsupport is being terminated due to a fatal errorcondition, this message will have been preceded byerror messages which depict the exact error conditionencountered.

User response

Follow the course of action recommended for the errormessages which preceded this error message, and ifthe product CICS support continues to terminate dueto a fatal error condition, contact Software Support forfurther assistance.

AZK0356I CICS support activated

Explanation

This message is issued when the product CICS serverhas received a notification that the connection(s) tothe CICS region(s) have been established successfully.

User response

No action required. This is an informational messageonly.

AZK0357I EXCI support terminating

Explanation

This is an informational message that is issued whenthe product terminates its EXCI support. If the EXCIsupport is being terminated due to a fatal errorcondition, this message will have been preceded byerror messages which depict the exact error conditionencountered.

User response

Follow the course of action recommended for the errormessages which preceded this error message, and ifthe product EXCI support continues to terminate dueto a fatal error condition, contact Software Support forfurther assistance.

AZK0358I EXCI support activated

Explanation

This message is issued when the product EXCI serverhas received a notification that the connection(s) tothe EXCI region(s) have been established successfully.

User response


AZK0359T msgtext

Explanation

This is a general purpose message that may or may notindicate some type of EXCI error.

User response

Read the message text carefully. Some messagesproduced under this message ID are actually errormessages. If the message indicates an error, check forany associated EXCI-produced error messages. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0360S No matching CONNECTION namersrc for DEFINE SESSION


Explanation

A DEFINE SESSION statement in the initialization execspecified a CONNECTION name for which there is nocorresponding DEFINE CONNECTION statement. Themessage text contains the name of the erroneousDEFINE SESSION name.

User response

Check the session name in the error message. Correctthe DEFINE SESSION statement.

AZK0361I %1 of %2 sessions connected to%3

Explanation

This message specifies the number of active sessionsto the specified CICS.

User response


AZK0362I No active session to %1

Explanation

This message specifies that there is currently no activesession to the specified CICS.

User response


AZK0363T Acquisition of session to %1 failed

Explanation

Acquisition of a session failed. This may not be anerror.

User response


AZK0364I SDCITRU IS STARTED ANDENABLED

Explanation

The CICS Task Related User Exit For Broker is startedand enabled in the CICS region.

User response


AZK0371E func ROUTINE ERROR - erroradditinfo1, additinfo2 ... additinfo7

Explanation

An error or unexpected condition was detected in anActional support facility routine (func).

User response

For initialization error, the server will terminate. Fortermination time errors, server shutdown continues.Look for related messages indicating the cause of theerror and correct the underlying problem. ContactSoftware Support if the problem cannot be found orcorrected.

AZK0372E CSQCAPX %1

Explanation

An error occurred in the CSQCAPX CICS MQSERIESAPI Crossing Exit for Actional Agent connector.

User response

The exit should have disabled itself. Contact IBMSoftware Support.

AZK0373E SDAITRUE %1

Explanation

An error occurred in module SDAITRUE, the CICSTRUE for Actional Agent connector.

User response

The exit should have disabled itself. Contact IBMSoftware Support.

AZK0380T ABEND IN REXXTOOLS DYNALLOCINTERCEPT CMP=ccode,RS=rsncode, SVC-99-PLIST=addr

Explanation

An unexpected abend has occurred within theREXXtools dynamic allocation interception/screeningroutine.

User response

The abend is percolated for handling by REXXtools.

AZK0381T ADD REXX VARIABLE NAMEFAILED WITH RETURN CODErcode, REASON CODE rsncode FORNAME varname

Explanation

An error occurred when attempting to create a variablename for a REXX procedure. This will be followed byan S0C3 abend.


User response

Check the variable name to be sure it is valid, orincrease the workspace for this REXX procedure.

AZK0388I It contains additional diagnosticinformation about the failure.

Explanation

This message provides information to help youdiagnose the problem.

User response


The variable fields of the message text are: requestrequest type func function that failed rc functionreturn code rscd function reason code

AZK0388E DYNAMIC LPA reqtype SERVICEFAILED FOR modname. RETURNCODE=rcode. REASONCODE=rsncode.

Explanation

An error occurred when attempting to use MVSdynamic LPA services, CSVDYLPA. The request type,return code and reason code associated with thisfailure are listed in this message.

User response


AZK0389E DYNAMIC LPA reqtypeFUNCTION=func RC=rcodeRS=rsncode

Explanation

This message is a continuation of message

User response:No action is required.

AZK0390E NAMED-TOKEN service SERVICEERROR: RC=rcode FOR LVL=tlvl,NAME=tname, DATA=tdata,POPT=topt

Explanation

An unexpected return code was set after a system-managed named token service request. The servicetype, return code, token level, token name, token data,and token persistence option are displayed in themessage.

User response

The named-token return code is sent to the routinewhich requested the service, and processing continuesas dictated by the routine which requested the server.

AZK0391E func ROUTINE ERROR: erroradditinfo1, additinfo2 ... additinfo7

Explanation

An error or unexpected condition was detected in aServices support facility routine.

User response


AZK0392W func ROUTINE WARNING: erroradditinfo1, additinfo2 … additinfo7

Explanation

An unexpected condition was detected in a Servicessupport facility routine.

User response

For initialization error, the server attempts to correctthe condition and continue. Errors detected duringtermination are bypassed.

AZK0393S Services PARM parmnameadditinfo1, additnfo2 ... additinfo7

Explanation

A Services configuration startup parameter is missingor incorrectly set. Services will substitute a correctedvalue, if possible, and activate with the updated value.If no default value can be substituted, Servicesactivation will terminate server start after issuingMSG0391E.


User response

Check to ensure the z/Server-related parameteridentified in the message is being set to a valid valueduring SxxxxIN00 processing. Restart the server.

AZK0394S SERVICES MAILBOX CONTROLrout FAILED: HASN=asid1,PASN=asid2, SASN=asid3,MODE=mode, RC=rcode,CALLER=csect, LT=ltype

Explanation

During an attempt to execute a Services mailboxrequest, a failure in the lock or unlock (rout)serialization routine was encountered. The currentmailbox execution request will be abandoned andfailed. In the message, the return code field willcontain a non-zero value in byte 3 if the SETLOCK orENQ service failed. It will contain a non-zero value inbytes 1 or 2 for environmental errors.

The message contains three asid values: home asid(asid1), primary asid (asid2), and secondary asid(asid3).

mode may be "PROB" or "SUP"

User response

The current Services mailbox request is failed. Checkfor other messages which might indicate the cause ofthe error, and contact Software Support for furtherassistance.

AZK0395E SERVICES MAILBOX REQUESTreqtype ABEND ccode (rsncode) ATmodname+offset additinfo1additinfo2 additinfo3 additinfo4

Explanation

During an attempt to execute a Services mailboxrequest, an ABEND failure was detected. The requestis rejected with a return code indicating that an abendoccurred.

reqtype may be "SYSTEM" or "USER"

User response

The failure is reflected to the requesting task, whichthen takes whatever action is appropriate to thesituation. Check for other messages which mightindicate the cause of the error, and contact SoftwareSupport for further assistance.

AZK0396T SERVICES MAILBOX INVALIDPOINTER (addr/ALET/storlgth)DURING PKM AUTH CHECK -ABEND ccode (rsncode)

Explanation

While validating a mailbox request, Services routinesdetected an invalid address passed as part of therequest. The ABEND was detected while attempting toexamine the protect key of the storage area.

User response

The pointer is rejected as invalid, and the mailboxrequest will either fail the overall request, or completeits operation without using the rejected pointer. Checkfor other messages which might indicate the cause ofthe error, and contact Software Support for furtherassistance.

AZK0397T func ROUTINE ERROR: erroradditinfo1, additinfo2 … additinfo7

Explanation

An error or unexpected condition was detected in aServices support facility routine. This message iswritten to Trace Browse to record the same conditionalso written to the console by MSG0391E.

User response


AZK0398T func ROUTINE WARNING: erroradditinfo1 additinfo2 … additinfo7

Explanation

An unexpected condition was detected in a Servicessupport facility routine. This message is written toTrace Browse to record the same condition alsowritten to the console by MSG0392W.

User response

For initialization error, the server attempts to correctthe condition and continue. Errors detected duringtermination are bypassed.

AZK0399T Services E-O-T cleanup for TCBaddr RC=rcode RS/CC=rsncode/ccode FDBK=feeback1, feedback2… feedback5

Explanation

Services End of Task cleanup has been processed forthe ending task. The message is traced if a non-zero


return code is set by the cleanup function, or when theZSRMBOXTRACECMTC option is on.

User response

If the message reports a non-zero return code, look forother conditions which may be inhibiting E-O-Tcleanup and correct. Or contact Software Support.


Explanation

This is a generic error message used to describe awide variety of RRS initialization and terminationerrors. The message text provides the currentoperation (service) and what the current operation wastrying to do.

User response



Explanation

This is a generic error message used to describe awide variety of RRS initialization and terminationerrors. The message text provides the currentoperation (service) and what data (valid or invalid) waspassed to the current operation.

User response



Explanation

This is a generic error message used to describe awide variety of RRS initialization and terminationerrors. The message text provides the currentoperation and what the current operation was trying todo.

User response

Check the error messages and the return codeassociated with this problem. There may be one or

more error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and restart the product. If the problemcannot be resolved, contact Software Support.

AZK0403S RRS rsrc NAME MISSING

Explanation

A resource (rsrc) name needed by the RRS productfeature is missing. The current operation will beterminated. The message text contains the name ofthe missing resource.

User response


AZK0404I RRS support terminating

Explanation

This is an informational message that is issued whenthe product terminates its RRS support. If the RRSsupport is being terminated due to a fatal errorcondition, this message will have been preceded byerror messages which depict the exact error conditionencountered.

User response

Follow the course of action recommended for the errormessages which preceded this error message, and ifthe product RRS support continues to terminate due toa fatal error condition, contact Software Support forfurther assistance.

AZK0405I RRS support activated

Explanation

This message is issued when the product RRS serverhas received a notification that the connection(s) tothe RRS region(s) have been established successfully.

User response


AZK0406H msgtext

Explanation

This is a general purpose message that may or may notindicate some type of RRS error.

User response

Read the message text carefully. Some messagesproduced under this message ID are actually error


messages. If the message indicates an error, check forany associated RRS produced error messages. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0407E Failure trying to register with RRS

Explanation

This message is issued when the RRS RegisterResource Manager call is unsuccessful. The product isunable to use RRS services, and two-phase commitsupport is disabled.

User response

Ensure that RRS is functioning correctly.

AZK0408E ERROR SETTING RRS EXITS,CHECK RRS STATUS

Explanation

This message is issued when the RRS Set ExitInformation call is unsuccessful. This usually indicatesthat the RRS subsystem is not up and running. Theproduct will attempt to establish its RRS exits when ithears from RRS that it is up and running. RRS supportand two-phase commit support will not be availableuntil the product can successfully connect to RRS.

User response

Ensure that the RRS subsystem is up and running. Ifthe RRS subsystem is not up and running, start it.

AZK0409E RRS %1 EXIT MANAGERUNAVAILABLE

Explanation

This message is issued when RRS alerts the productthat an IBM exit manager for RRS has becomeunavailable. This causes the product to lose itsconnection to RRS immediately. The product will try toreconnect again when it hears RRS is up and running.RRS support and two-phase commit support will notbe available until the product can successfullyreconnect to RRS.

User response

Ensure that the RRS subsystem is up and running. Ifthe RRS subsystem is not up and running, start it.

AZK0410E Product RRS exits have been unset

Explanation

This message is issued when RRS alerts the productthat the product RRS exits have become unset due to

some error condition. This causes the product to loseits connection to RRS. RRS support and two-phasecommit support will not be available.

User response

This indicates an error that should not occur. ContactSoftware Support.

AZK0411E TRANS: token FROM host -REQUESTED ind1 BUT WASHEURISTICALLY ind2

Explanation

The portion of a distributed transaction that ran underthe product on z/OS was committed or rolled backheuristically manually or by a program - but not by theclient-side transaction manager. The transactionmanager has just informed the product that it wantedthe transaction rolled back or committed. The datainvolved in the transaction may now be in aninconsistent state (partially committed and/or partiallyrolled back).

ind1 indicates "COMMIT" or "BACKOUT", and ind2indicates "COMMITTED" or "BACKED OUT"

User response

This situation may need to be corrected manually. Thedata that was committed on MVS may need to bebacked out, and the data sources may need to berestored to their state before the transaction. Notethat the committed data may have already beenaccessed by later programs and transactions.

AZK0413E THE DB2ATTACHFACILITYPARAMETER IS NOT SET TORRSAF, RRS SUPPORTTERMINATED'

Explanation

The product DB2ATTACHFACILITY must be set to usethe Recoverable Resources Attach Facility (RRSAF) forRRS support to work properly.

User response

Modify the product parameter data set member.

AZK0414E RRS RECOVERY TABLE SIZEEXCEEDED - TRANSACTIONABORTED'

Explanation

The RRS Recovery Table size was exceeded. Atransaction was aborted, which will be indicated inanother message.


User response

Increase the number of entries in the RRS RecoveryTable, specified by the product parameterRECTABLEENTRIES. If this parameter is not specified,the value defaults to 400 entries.

AZK0415E Incompatible supplied driver onclient system - transactionaborted

Explanation

An incompatible product-supplied driver wasencountered on the client system.

User response


AZK0416E ZERO COLUMNS RETURNED FROMPREPARE - ERROR IN SYSTEM

Explanation

Zero columns were returned from PREPARE. This ismost likely due to an error in z/OS, RRS, and/or Db2.

User response

Contact Software Support for the latest informationregarding how to bypass this problem.

AZK0417E RRS IS NOT ACTIVATED FOR THISSERVER - XA TRANSACTIONABORTED.'

Explanation

When this server was initialized, either it was notinstructed to activate an RRS connection or theinitialization for connection failed.

User response

If the initialization parameters specify that RRS is to beactivated, review the messages created when thisserver was initialized and correct any associatedproblems.

AZK0420E TWO-PHASE COMMIT SUPPORTWAS REQUESTED, BUT RRS ISNOT ACTIVE

Explanation

The RRS parameter was set to NO, or RRS initializationfailed. Two-phase commit cannot be supported unlessRRS is active.

User response

Check the joblog for RRS initialization error messagesand correct any problems. Then, restart this serverwith the RRS parameter set to YES.

AZK0421E ERROR IN TWO-PHASE indicatorPROCESS. RRS RETURN CODE =rcode

Explanation

Two-phase commit was requested for all transactionsfrom this task. RRS returned an error code indicatingthat the commit was not successful.

indicator indicates "COMMIT" or "BACKOUT"

User response

Check the return code from the RRS ATRCMIT functionin the IBM manual titled z/OS Programming: ResourceRecovery.

AZK0422E RRS RECOVERY TABLE COUNTNEGATIVE, RESET TO ZERO

Explanation

The RRS Recovery Table entry count was found to benegative during XA-RECOVER processing. The entrycount was reset to zero.

User response

There may be some XA transactions that were left inan incomplete state, leftover from a communicationline disconnect or host system crash.

AZK0423T Access to data sources throughEnterprise Transactions is notconfigured.

Explanation

None.

User response


AZK0424E TWO-PHASE COMMIT SUPPORTWAS REQUESTED, BUT THE RRSMANAGER WAS NOT ACTIVE

Explanation

RRS was requested, but RRS was not active.


User response

Check the joblog for messages related to RRSinitialization. Correct the initialization errors andrestart this server.

AZK0425E IBM/MQSERIES/RRS SUPPORTENTRY entry IN MODULE modnameMISSING

Explanation

An IBM/MQSeries support entry was missing from themodule specified. There is an incompatibility betweenthe MQSeries® library provided and productMQSeries/RRS support.

User response

Ensure that the library provided is the standard IBMlibrary. If the problem cannot be resolved, contactSoftware Support.

AZK0426S IBM/MQSERIES/RRS SUPPORTMODULE modname MISSING - NOTWO-PHASE COMMIT SUPPORTPROVIDED

Explanation

The specified IBM/MQSeries support module isnecessary for two-phase commit support forMQSeries. Processing will continue without MQSeriestwo-phase commit support.

User response

Check the IBM/MQSeries library, defined in theproduct JCL procedure. It may be an old version.

AZK0428T CREATION OF RRS PRIVATECONTEXT FAILED - CONNECTIONTERMINATED. CALL: calltype -R15: rcode - R0: rsncode

Explanation

With the product RRS support active and PrivateContexts selected, the product creates an RRS PrivateContext immediately when the session connects. TheRRS calls to do this failed.

User response

Check to be sure that the IBM RRS facility is active andnot generating errors.

AZK0480S MQSERIES support deactivated -access routines cannot be loaded.

Explanation

During initialization MQSERIES access modules couldnot be loaded from either AZKMQSLB or STEPLIB.

User response

The server deactivates MQSERIES support andcontinues start- up processing. Check to ensure youhave an AZKMQSLB DD JCL statement in the serverstart-up JCL.

AZK0500E IBM-assigned CSR table entrysetup error, contains val, notproduct OPVN pointer

Explanation

During initialization, the product Vendor Vector Tableentry contained an invalid value (val). The assignedfullword contains a value which does not address theproduct OPVN control block. The IBM-assigned, entryin the table is located at decimal offset 184,hexadecimal offset B8 of the vector table addressedby ECVTCTBL. The fullword value at that locationcontained a non-zero value that did NOT point to analready established product OPVN control block. Theproduct cannot initialize without establishing theOPVN block pointer. The existing value in the vectortable fullword is saved and overlaid with the productOPVN block address.

User response

Determine who/what is responsible for creating theinvalid entry in the table, clear the word to x'00's, andrestart the product. Caution should be used whendeciding to clear the entry. Most likely, another ISVhas inadvertently used this entry; clearing it to 0'scould cause problems for some other product.

AZK0501E service OF desc FAILED, RC=rcode

Explanation

This is a generic error message used to describe avariety of Server initialization and termination errors.The message text provides the information about thecurrent operation.

User response


AZK0502E subsys directory table entry exists.


Explanation

During initialization, the server directory table wasfound to contain an entry with the same subsystem IDas the one being started. Most likely, a server addressspace is active on this MVS image with this subsystemname.

User response

Determine if a server address space is currently activewith this subsystem name. If so, change thesubsystem name and restart (if it is necessary to startanother server address space). If the problem cannotbe resolved, contact IBM Software Support..

AZK0503E No ERLY exists for DB2 %1

Explanation

None.

User response


AZK0504E %1 DB2 owned by another server.

Explanation

None.

User response


AZK0505E %1 DB2 search error.

Explanation

None.

User response


AZK0506E %1 server software PC resetfailed.

Explanation

None.

User response


AZK0507E %1 product PC reset failed.

Explanation

None.

User response


AZK0508E %1 server software PC entryunknown.

Explanation

None.

User response


AZK0509E %1 DB2 server init error.

Explanation

None.

User response


AZK0510E %1 DB2 server %2 error.

Explanation

The server main task for the named Db2 systemencountered an error from the common subroutine.Either ECB WAIT or STIMER.

User response


AZK0511E %1 DB2 SSCTSUSE ERROR,

Explanation

None.

User response


AZK0512I %1 DB2 main task PC reset error.

Explanation

None.

User response


AZK0513I %1 product main task TERM PCerror

Explanation

None.


User response


AZK0515E MAXIMUM NUMBER OF DB2SUBSYSTEMS PREVIOUSLYDEFINED. MAX = %1. DEFINE FORDB2 SSID %2 IGNORED.

Explanation

During initialization, the input parameter data setcontains more Db2 subsystem statements than themaximum allowable set by default or by QSMAXDB2.

User response

All parameter statements pertaining to this Db2subsystem are ignored.

AZK0516E DUPLICATE DB2 SUBSYSTEMDEFINITION FOR DB2 SSID %1

Explanation

During initialization, the input parameter data setcontains more than one DEFINE for the same Db2subsystem ID.

User response

All parameter statements within the subsequentDEFINE for this Db2 are ignored.

AZK0517E RETURN CODE %1 FROM ALESERVADD OF DB2 DBM1 FOR %2

Explanation

None.

User response


AZK0518E TERMINATION WAITING ON DB2STATUS TASK FOR %1

Explanation

None.

User response


AZK0519E maximum number of serveraddress spaces are already active.max possible %1. currently active%2.

Explanation

None.

User response


AZK0520E Maximum number of DB2 systemsare all ready active. max possible%1. DB2 %3.

Explanation

The maximum number of subsystems allowed by theserver are already active.

User response

Edit the server configuration file, and reduce thenumber of database definitions in the file.

AZK0521S DB2 subsysid STATUS TASKABEND abcode AT modname+offset DURING desc.

Explanation

None.

User response


AZK0522W Proprietary R&&D utilities areactivated for this start-up

Explanation

This warning indicates that private R-and-D utilityfunctions are activated within the system. Customercopies of the product should never produce thismessage during start-up processing.

User response

If this message appears during start-up, terminate theserver and contact Software Support. The execution ofinternal developer utilities off-site may producedamaging side effects.

AZK0523W E/SQA ROUTINE AT addr WILL BEREBUILT DUE TO INVALID PTR ORDATA

Explanation

This warning indicates that the special E/SQA-residentSRASTC routine will be rebuilt. The existing pointer tothe routine, or the routine itself, appears to have beendamaged.


User response

Start-up processing clears the existing pointer andbuilds a new copy of the needed routine into E/SQAstorage. The storage, if any, previously anchored bythe OPVN vendor CSR table control block is orphaned.Contact Software Support.

AZK0600S IMS/OTMA XCF reqtype FAILED,RC=rcode RS=rsncode IMS=imsID

Explanation

This is a generic error message used to describe awide variety of IMS/OTMA initialization andtermination errors. The message text provides thecurrent operation and what the current operation wastrying to do.

User response



Explanation

This is a generic error message used to describe awide variety of IMS/OTMA initialization andtermination errors. The message text provides thecurrent operation and what the current operation wastrying to do.

User response


AZK0602I IMS/OTMA server waiting OTMAINIT for IMS SSID=subsys

Explanation

This message indicates that the IMS/OTMATransaction Server is waiting for initialization of theselected IMS subsystem. This message isinformational and issued periodically when OTMAsupport is waiting for IMS subsystem startup to occur.

User response

Determine why the IMS subsystem is unavailable.Start the IMS subsystem to allow OTMA support to beenabled. If this message is issued in error, contactSoftware Support.

AZK0603I IMS/OTMA server INIT in progressfor IMS SSID=subsysID

Explanation

This message indicates that the IMS/OTMATransaction Server initialization is in progress for theselected IMS subsystem.

User response


AZK0604I IMS/OTMA server INIT completefor IMS SSID=imsID using XCFmember xcfID

Explanation

This message indicates that the IMS/OTMATransaction Server initialization has been successfullycompleted for the selected IMS subsystem.

User response


AZK0605I IMS/OTMA server has detectedOTMA TERM for IMSSSID=subsysID

Explanation

This message indicates that the IMS/OTMATransaction Server has detected IMS terminatingOTMA support. This message is issued when it hasbeen determined that IMS is leaving the XCF OTMAgroup. This may be due to IMS termination, a /STOPOTMA command, or OTMA abnormal termination. Theproduct IMS/OTMA server will wait for IMS to restartOTMA support and continue processing OTMA requestactivity.

User response


AZK0606I IMS/OTMA server TERM inprogress for IMS SSID=subsysID

Explanation

This message indicates that the IMS/OTMATransaction Server is terminating for the selected IMS


subsystem. This message is issued during producttermination.

User response


AZK0607I IMS/OTMA server TERM completefor IMS SSID=subsysID

Explanation

This message indicates that the IMS/OTMATransaction Server has completed termination for theselected IMS subsystem. This message is issuedduring product termination.

User response


AZK0608S IMS/OTMA TPIPE TASK task FORCONNECTION conn ABENDEDCODE abcode

Explanation

This message indicates that the IMS/OTMATransaction Pipe has ABENDED.

User response

Examine the Trace Browse and JES JOBLOG todetermine why the ABEND occurred. If the problemcannot be resolved, contact Software Support.

AZK0620S SIS/XCF XCF reqtype FAILED,RC=rcode RS=rsncode SIS=ID

Explanation

This is a generic error message used to describe awide variety of SIS/XCF initialization and terminationerrors. The message text provides the currentoperation and what the current operation was trying todo.

User response



Explanation

This is a generic error message used to describe awide variety of SIS/XCF initialization and terminationerrors. The message text provides the currentoperation (service) and what the current operation wastrying to do.

User response


AZK0622T SIS/XCF member waiting SIS/XCF%1 INIT for mbr=%2

Explanation

This message indicates that the SIS/XCF Server iswaiting for initialization of the selected SIS subsystem.This message is informational and issued periodicallywhen an SIS/XCF standard member is waiting for theSIS/XCF manager to initialize.

User response

Determine why the SIS/XCF manager is unavailable.Start the SIS/XCF manager to allow SIS/XCF supportto be enabled. If this message is issued in error,contact Software Support.

AZK0623I SIS/XCF %1 INIT in progress formember=%2

Explanation

This message indicates that the SIS/XCF Serverinitialization is in progress for the selected SISsubsystem.

User response


AZK0624I SIS/XCF server INIT complete forSIS SSID=sisID using XCF memberxcfID

Explanation

This message indicates that the SIS/XCF Serverinitialization has been successfully completed for theselected SIS subsystem.

User response



AZK0625I SIS/XCF %1 instance has detectedtermination of %2 instancemember %3

Explanation

This message indicates that the SIS/XCF TransactionServer has detected SIS terminating SIS/XCF support.This message is issued when it has been determinedthat SIS is leaving the XCF OTMA group. This may bedue to SIS termination, or OTMA abnormaltermination. The SIS/XCF server will wait for SIS torestart SIS/XCF support and continue processing SISrequest activity.

User response


AZK0626I SIS/XCF %1 TERM in progress formember=%2

Explanation

This message indicates that the SIS/XCF Server isterminating for the selected SIS subsystem. Thismessage is issued during product termination.

User response


AZK0627I SIS/XCF %1 TERM complete formember=%2

Explanation

This message indicates that the SIS/XCF TransactionServer has completed termination for the selected SISsubsystem. This message is issued during producttermination.

User response


AZK0701W ZIIPCLASS=class HAS TOO MANYPERIODS SPECIFIED

Explanation

This message indicates that WLM initialization foundtoo many matching report classes. Only six periods areallowed, and more than that matched the namingconvention.

User response

Delete the extra report classes.

AZK0702W CLASS class1 SPECIFIES AZIPCLASS NAME THAT DOES NOTEXIST, class2

Explanation

This message indicates that WLM initialization found aclass that referenced a ZIIPCLASS that could not befound.

User response

Correct the indicated WLM Class to reference anexisting WLM pseudo-class.

AZK0703W ZIIPCLASS=class CONTAINSINVALID PARMS

Explanation

This message indicates that WLM initialization found aZIIPCLASS report class definition with invalid parms.The description must contain a Pnnn percent definitionand all but the last one must contain a Dnnnnnnnduration.

User response

Correct the definition field of the ZIIPCLASS reportclass definition.

AZK0704H WLM refresh command completed

Explanation

The WLM command has successfully completed,refreshing WLM data within the product.

User response

None.

AZK0706I product subsys requires thefollowing elements missing fromWLM Service type name

Explanation

Product initialization detected that the current WLMservice policy does not have the all of the requireddefinitions for Version 7.1 of the product. Messageslisting the required service definition elements willfollow this message.

type may be "policy" or "definition"

Consequently, name will be either a policy name or adefinition name


User response

Respond to the WTOR prompts that follow thesemessages.

AZK0707I Type: PEtype, Server Parameter:PEname, Value: parmname

Explanation

Generic message used by product WLM initialization tolist elements missing from the WLM service definition.

The PE in this message's variables stands for PolicyElement

parmname represents the IN00 parameter name

User response

Respond to the WTOR prompts that follow thismessage.

AZK0708R Reply 'GO' to update the WLMService Definition, or 'CANCEL' toterminate server initialization

Explanation

This message is issued when product WLMinitialization is about to update the current WLMservice definition with the policy elements required forproduct server execution.

User response

Reply GO to allow the server to update the WLMservice definition. Reply CANCEL to terminate serverinitialization

AZK0709I WLM Service Definition def hasbeen updated with requiredproduct elements

Explanation

This message is issued when product WLMinitialization has updated the WLM service definition(def) with the required product elements.

User response


AZK0710E Invalid reply: reply. Reply 'GO' or'CANCEL'

Explanation

An invalid reply was specified to the server WLMinitialization console message.

User response

Reply GO to cause the message to be reissued. ReplyCANCEL to terminate server initialization.

AZK0711E REPLY WAIT EXCEEDED 2MINUTES. CANCEL ASSUMED

Explanation

The product waited over two minutes for a reply to theWLM initialization message. Since no response wasreceived during that time, CANCEL was assumed andserver initialization terminated.

User response


AZK0712E 3 INVALID REPLIES. CANCELASSUMED

Explanation

Three invalid replies were made to the product WLMinitialization message. Since no correct response wasreceived, CANCEL was assumed and serverinitialization terminated.

User response


AZK0713S WLM administration user IDuserID logon failed.

Explanation

The WLM admin user ID specified by the WLMUSERIDsystem parameter failed logon processing during start-up.

User response

The server initialization process is aborted. Ensure thatthe user ID specified by the WLMUSERID start-upparameter is correct. If possible, fix the problemidentified by the error messages and restart theproduct. If the problem cannot be resolved, contactIBM Software Support.

AZK0714I WLM administration userid userIDlogged on to system

Explanation

The WLM admin userid specified by the WLMUSERIDsystem parameter has been logged on to the system.


User response

Server initialization processing continues.

AZK0715I WLM Service Definition definitiondoes not contain current ServicePolicy policy

Explanation

This message is issued when product WLMinitialization is has updated the WLM service definitionand has determined that it does not contain thecurrently active service Policy.

User response


AZK0716R Enter name of Service Policy toactivate, 'LIST', or 'CANCEL' toterminate server initialization

Explanation

This message is issued when product WLMinitialization has updated the Service Definition andneeds to know which Service Policy should beactivated.

User response

Enter a name to activate Service Policy with that name.Reply LIST to get a list of available Policies. ReplyCANCEL to terminate server initialization

AZK0717I The following Service Policies areavailable for activation

Explanation

This message is issued when product WLMinitialization is about to list the Service Policies definedin the current Service Definition.

User response


AZK0718I Policy: policyname - policydesc

Explanation

Generic message used by product WLM initialization tolist Service Policies available for activation.

User response


AZK0719R Reply 'GO' to activate Policy %1,or 'CANCEL' to terminate serverinitialization

Explanation

This message is issued when product WLMinitialization has updated the WLM service definitionwith the named service policy.

User response

Reply GO to allow the server to activate the servicepolicy. Reply CANCEL to terminate server initialization1 = policy name of WLM policy to be created

AZK0720S WLM reset to service class classfailed for job jobname subsystemsubsys ASID asid

Explanation

The server WLM initialization failed to reset the serviceclass for the server.

User response

Look for preceding error messages in the system log.

AZK0721I WLM classify successful fortransaction - Service Class class

Explanation

The server WLM enclave classification was successful.

User response

None.

AZK0722I Unable to classify transactiontrans for subsystem subsys

Explanation

The server was unable to classify the namedtransaction.

User response

Look for preceding error messages in the system log.

AZK0723I WLM enclave create successful forService Class class

Explanation

The server WLM enclave classification was successful.

User response

None.


AZK0724I subsys WLM health changed fromsubsystem%% to oper1%% oper2

Explanation

The WLM health value for the specified productsubsystem was changed from the first value to thesecond.

User response

If the health value decreases, look for abends ortimeouts in the Server. Currently only ACI abends andtimeouts are measured. If the health value increases,this is an indication that no further failures have beendetected, and the product is returning to full health.

The variable fields of the message text are: subsystemthe WLM subsystem type oper1 the old health valueoper2 the new health value reason reason description

AZK0725I RACF administration USERIDuserID logged on to system

Explanation

The RACF admin USERID specified by the SERVERIDsystem parameter has been logged on to the system.

User response

Server initialization processing continues.

AZK0726S RACF administration USERID(userID) logon failed

Explanation

The RACF admin USERID specified by the SERVERIDsystem parameter failed logon processing during start-up.

User response

The server initialization process is aborted. Ensure thatthe USERID specified by the SERVERID start-upparameter is correct. If possible, fix the problemidentified by the error messages and restart theproduct.If the problem cannot be resolved, contactIBM Software Support.

AZK0800I IDMS SERVER INIT IN PROGRESSFOR CONNECTION=%1

Explanation

This message indicates that the IDMS initialization is inprogress for the selected IDMS connection name.

User response


AZK0801I IDMS SERVER INIT COMPLETEFOR CONNECTION=target USINGMAILBOX=connID

Explanation

This message indicates that the IDMS initialization hasbeen successfully completed for the selected IDMStarget using the defined connection (connID).

User response


AZK0802I CONNECTION BROKEN WITHIDMS CONNECTION=connIDUSING MAILBOX=jobname

Explanation

This message indicates that the IDMS connection hasbeen broken for the selected IDMS connection(connID)

User response


AZK0900E service of ddname/cblk failed,RC=rcode.

Explanation

During compilation or execution of a REXX program, anMVS service returned a non-zero error code. One ofthe following occurred: (1) a file failed to open orclose, (2) a failure in writing a record (WRITE orENDREQ), (3) storage for a control block could not beobtained or freed, or (4) parsing of the commandfailed.

User response

Depending on which of the above cases pertains, takeone of the following actions: (1) check for a messageindicating why the file failed to open or close (mostlikely, the SYSEXEC file name was not allocatedproperly - e.g. allocated to a sequential file instead of apartitioned data set); (2) if a WRITE or ENDREQ failedmessage was issued, check the status of the PDSallocated in the AZKCOMP or SWSCOMP DD (it may notbe allocated properly - e.g. ran out of space); (3) if theerror reported a GETMAIN, allocate or allocationfailure, you may have to increase the TSO region sizefor your TSO session; or (4) check the command youissued for incorrect syntax.


AZK0901E CANNOT OPEN member (ABENDabcode AT modname+offset)

Explanation

During the open processing of the REXX program to berun, an abend occurred. The PDS member containingthe REXX source program could not be openedbecause of the abend.

User response

Ensure that the given library is a PDS similar bydefinition to the other REXX libraries. Check the IBMmessage and codes manuals for the abend code. Mostlikely, either the member does not exist or the data setattributes are in error (sequential DSORG or the LRECLand BLKSIZE are not compatible). If a system 913abend code is reported, data set access has beendisallowed by your security subsystem.

AZK0902E Cannot find program programddname.

Explanation

The REXX interpreter (AZKI, AZKX, SWSI, or SWSXTSO command processor) could not locate thespecified REXX program in the data set allocated tothe SYSEXEC ddname (for SDBI or SWSI) or in the dataset specified on the AZKX or SWSX commands.

User response

Ensure the program name being executed exists in oneof the SYSEXEC concatenated data sets (for AZKI orSWSI) or in the data set specified on the AZKX orSWSX command. Check the spelling of the programname.

AZK0903E ERROR 43 reqtype caller, LINElineno: ROUTINE routine NOTFOUND

Explanation

While compiling a REXX program, the REXX interpretercould not locate a routine called by the main programor called by one of its subroutines.

User response

Check the calling program (described in this message)to make sure that the subroutine name is spelledcorrectly. If spelling is correct, the missing routinemust be added to a library allocated to the SYSEXECddname or to the same library in which the callingprogram resides.

=

AZK0906I No syntax errors found duringscan.

Explanation

The compiler found no syntax errors during a AZKXscan. This is an informational message.

User response

No action is required.

AZK0907S ABEND abcode OCCURRED ATcsect+offset OF PROGRAMprogram

Explanation

An abend occurred during the execution of a REXXprogram by the REXX interpreter (AZKI or AZKX TSOcommand). The name of the REXX program beingexecuted at the time of the abend is shown in thismessage.

User response

Check the line being executed at the time of theabend. Check the abend code in the IBM messagesand codes manual, and follow action stipulated there.

AZK0908E PROGRAM program IS TOO LARGE- INPUT BUFFER OVERFLOW

Explanation

The REXX interpreter (AZKI or AZKX TSO command)could not successfully compile a REXX programbecause it is too large.

User response

Split the program into smaller subroutines. This erroris directly related to the number and length of sourceinput lines in a single REXX program.

AZK0909E PROGRAM program - ARG LENGTH(lgth) EXCEEDS MAXIMUMLENGTH (maxlgth)

Explanation

The length of the argument string for the REXXprogram exceeds the implementation limit.

User response

Check if there are an excessive number of blanks inthe argument string. If so, remove the blanks from theargument string. If you need to pass long values to aREXX program, use global variables to pass the values.


AZK0911E Missing REXX program name

Explanation

The AZKI command was invoked using the TSO CALLcommand without a parameter field (containing theREXX program name to execute), or the @#$Icommand was invoked from within ISPF edit and theISPF environment could not be established.

User response

If the AZKI command was invoked via the TSO CALLcommand, you must add the parameter field with aREXX program name (and optional arguments).Otherwise, contact Software Support for assistance.

AZK0912E Missing REXX program namedetected at - addr

Explanation

The AZKI or AZKX TSO command was invoked withouta program name.

User response

You must specify a program name on the AZKI orAZKX TSO command. Contact Software Support.

AZK0913E Invalid REXX program namedetected - program

Explanation

The REXX program name specified is invalid. It mustbe a valid PDS member name and cannot exceed eight(8) characters in length.

User response

Specify a valid REXX program name. If the problemcannot be resolved, contact Software Support.

AZK0914E UNKNOWN RETURN CODE FROMPARSE ROUTINE, RC=rcode

Explanation

An unexpected return code was received from theinternal parse routine.

User response

Contact Software Support for assistance.

AZK0915E BATCH OR TSO CALL PARAMETERSTRING TOO LONG

Explanation

The parameter field passed to a batch program, or aprogram invoked by TSO CALL cannot exceed 100characters.

User response

Reduce the length of the parameter string. ContactSoftware Support to obtain additional assistance.

AZK0916E routine built-in function not found- called by caller.

Explanation

A compatibility problem exists between the productsubsystem in use and the pre-compiled REXX programbeing re-loaded. A product built-in function that wasto be used by the pre-compiled REXX program nolonger exists.

User response

Check the subsystem release levels used when theREXX program was compiled. It may be necessary torecompile the REXX program again under the currentproduct subsystem (AZKICOMP).

AZK0917E ERROR SAVING THE COMPILEDOUTPUT IN %1

Explanation

An error occurred while attempting to save a pre-compiled program. This message is accompanied byan earlier message detailing the cause of the error.

User response

Check the previous error message for possible actions.

AZK0918E CANNOT WRITE EXECUTABLEOBJECT obj.obj2 TO DS(dsname)additinfo

Explanation

SEF is unable to save an executable object binaryimage or data area because of a runtime problem. Thesource rule or data file are named, along with thetarget dataset.

obj1 may indicate a ruleset or a datafile

Based on the value of obj1, obj2 may indicate a rule ordata member

User response

Check for other messages indicating the source of theproblem and retry the request.


AZK0919I Successful compile and save ofprogram in ddname.

Explanation

THE REXX interpreter (AZKICOMP, AZKXCOMP,SWSICOMP or SWSXCOMP commands) was successfulin compiling and saving the REXX program.

User response


AZK0920E REBUILD FAILED FOR COMPILEDREXX PROGRAM - program

Explanation

The REXX interpreter command processor wasattempting to rebuild a REXX program from apreviously compiled PDS member when the failureoccurred.

User response

Check for other accompanying error messages. Youmay have to delete the compiled version of theprogram and recompile it again, or execute the REXXsource program.

AZK0921W ALLOCATION OF COMPILEDLIBRARY (dsname) FAILED

Explanation

The product attempted to allocate the library with thecompiled versions of REXX programs. The dynamicallocation failed.

User response

Make sure that the data set name specified in the firstpanel of this application is valid. Contact the person atyour installation who is responsible for the product toget the proper data set name.

AZK0922W ITRACE KEYWORD NOT ALLOWEDDURING COMPILE ONLY REQUEST

Explanation

Setting the initial trace value for a COMPILE ONLYrequest is not allowed.

User response

Do not specify the ITRACE keyword in a COMPILEONLY request. The ITRACE value only has meaningduring the execution phase of REXX.

AZK0923S COMPILE ALL FAILED - ERRORREADING THE DIRECTORY OFdsname

Explanation

A COMPILE ONLY request was received for an entirePDS, but an error was detected while reading thedirectory.

User response

Try to browse the data set using ISPF and see if themember list directory is accessible for the PDS. If not,contact your local DASD administrator for possibledata set recovery. If you are able to browse the dataset and list its members properly, contact SoftwareSupport.

AZK0990E RUNNING program:INCOMPATIBLE CONTROL BLOCKS

Explanation

The REXX program was compiled with an older versionof the Product REXX interface module. The REXXcontrol blocks in the compiled module areincompatible with the current version.

User response

This error should only occur when executing a pre-compiled, saved version of a program or rule. In thatcase, the program or rule should be recompiled andthen re-executed. If the error occurred in any othercase, contact Software Support for assistance.

AZK0991E RUNNING program: INTERNALERROR DETECTED AT addr

Explanation

The REXX interface module detected an internal error.

User response

There may be other error messages related to thiscondition. This error may be caused by a REXXworkspace overflow condition. If this is the case, referto message 0998E for additional information. If theproblem cannot be resolved, contact SoftwareSupport.

AZK0997T lineno TRACE MESSAG

Explanation

Informational message only. This message gives theoutput from the REXX TRACE command when used ina rule.


User response


AZK0998E RUNNING program LINE lineno:COMPILER WORK SPACEOVERFLOW (value1 value2)

Explanation

The rule or program used up all of the available REXXvariable work space.

User response

In either case, check if the program is incorrectlycreating too many variables. If so, correct theprogram, and retry the operation. If the program isoperating correctly, the work space size may be toosmall. In the rule environment, the SEFSIZE parameterneeds to be increased, and the product must berestarted. In the case of a Product REXX program(SWSI command), use the WORKSPACE keywordparameter to override the default size. For WWW rules,override the default workspace specification by codingthe WORKSPACE() operand on the /*WWW headerstatement for the rule.

AZK0999E STAX calltype MACRO FAILED -RC=rcode

Explanation

The STAX macro failed with the indicated return codewhile the Product REXX compiler was trying toinitialize or terminate execution of a REXX program.

calltype can be "ON" or "OFF"

User response

Record the error message and return code. ContactSoftware Support.

The STAX macro failed with the indicated return codewhile the Product REXX compiler was trying toinitialize or terminate execution of a REXX program.

AZK1000I msgtext

Explanation

The product message used for REXX SAY statements.

User response


AZK1004I ERROR 4 process program, LINElineno: PROGRAM INTERRUPTED

Explanation

The system halted the execution of a REXX programbecause of some error or by user request. Unlesstrapped by SIGNAL ON HALT, this message will forcethe language processor to immediately ceaseexecution.

process may be "compiling" or "running"

User response


AZK1005I ERROR 5 process program, LINElineno: MACHINE RESOURCESEXHAUSTED

Explanation

While attempting to execute a REXX program, thelanguage processor was unable to obtain theresources it needed to continue execution. Thefollowing items may be the cause of this message: (1)the external data queue is full or (2) all availablestorage has been used.


User response

Try increasing the size of the external data queue orthe amount of storage available to the program.

AZK1006I ERROR 6 var1 var2, LINE lineno:UNMATCHED "/*" OR QUOTE

Explanation

A comment string or a literal string was started butnever finished. For comments, this may be detected atthe end of the program or at the end of an INTERPRETinstruction. For literal strings, this may be detected atthe end of a line.

User response

Examine the rule or REXX program, and correct thestring.

AZK1007I ERROR 7 process program, LINElineno: WHEN OR OTHERWISEEXPECTED

Explanation

Within a SELECT construct, at least one WHENconstruct (and possibly an OTHERWISE clause) isexpected. If any other instruction is found (or noWHEN construct is found before OTHERWISE), thenthis message results. This is commonly caused by


forgetting the DO and END around the list ofinstructions following a WHEN.


User response

Examine the REXX program, and correct the error.

AZK1008I ERROR 8 process program, LINElineno: UNEXPECTED THEN ORELSE

Explanation

A THEN or an ELSE has been found that does notmatch a corresponding IF or WHEN clause. This erroroften occurs because of a missing END or DO...END inpart of a complex IF...THEN...ELSE construct.


User response

Examine the program, and correct the error.

AZK1009I ERROR 9 process program, LINElineno: UNEXPECTED WHEN OROTHERWISE

Explanation

A WHEN or OTHERWISE has been found outside of aSELECT construct. It may have been enclosedunintentionally in a DO...END construct by leaving offan END instruction, or an attempt may have beenmade to branch to it with a SIGNAL instruction (whichcannot work because a SELECT is terminated by aSIGNAL).


User response

Examine your program, and fix the part in error.

AZK1010I ERROR 10 process program, LINElineno: UNEXPECTED ORUNMATCHED END

Explanation

Either there are more ENDs in the program than DOsand SELECTS or the ENDs are wrongly placed so theydo not match the DOs and SELECTs. It may be usefulto use trace scan to show the structure of the program;hence, making it more obvious where the error is. Acommon mistake that causes this error is attemptingto jump into the middle loop using the SIGNALinstruction. This error will also be generated if an ENDimmediately follows a THEN or an ELSE.


User response

Examine the line in error, and correct the REXXprogram.

AZK1011I ERROR 11 process program, LINElineno: CONTROL STACK FULL

Explanation

An implementation limit of levels of nesting of controlstructures (DO...END, IF...THEN...ELSE, etc.) has beenexceeded. The message should state the actualrestriction. This error could be due to a loopingINTERPRET instruction or due to infinite recursivecalls.

User response

Examine the line in error, and fix the program.

AZK1012I ERROR 12 process program, LINElineno: CLAUSE TOO LONG

Explanation

There may be an implementation restriction that limitsthe length of the internal representation of a clause.This message is generated if this limit is exceeded.


User response

Reduce the length of the literal and hexadecimalstrings that exceed the documented limits. If theproblem cannot be resolved, contact SoftwareSupport.

AZK1013I ERROR 13 process program, LINElineno: INVALID CHARACTER INPROGRAM

Explanation

The program includes a character outside the literalquoted string that neither alphanumeric nor one of theacceptable special characters.


User response

Examine the line in error, and correct the invalidcharacter.

AZK1014I ERROR 14 process program, LINElineno: INCOMPLETE DO/SELECT/IF


Explanation

On reaching the end of the program (or the end of thestring in an INTERPRET instruction), it has beendetected that there is a DO or SELECT without amatching END or an IF that is not followed by a THENclause to execute.


User response

Find the unbalanced DO or SELECT, and correct it.

AZK1015I ERROR 15 process program, LINElineno: INVALID HEXADECIMALOR BINARY CONSTANT

Explanation

Hexadecimal constants may not have leading ortrailing blanks and may only have embedded blanks atbyte boundaries. Only the digits 0 - 9 and the letters a-f are allowed. Binary strings may only have blanksadded at the boundaries of groups of four binary digits.Only the digits 0 and 1 are allowed. The error may alsobe caused by following a literal string either by the onecharacter symbol "x" when the string is not intendedto be taken as a hexadecimal specification or by thesymbol "b" when the string is not intended to be takenas a binary specification. Use the explicitconcatenation operator, "| |", in this situation toconcatenate the string to the value of the symbol.


User response

Locate the error on the line, and correct it.

AZK1016I ERROR 16 process program, LINElineno: LABEL NOT FOUND

Explanation

A SIGNAL instruction has been executed, or an eventoccurred for which a trap was set, and the labelspecified cannot be found in the program.


User response

Correct the error, and rerun the program.

AZK1017I ERROR 17 process program, LINElineno: UNEXPECTED PROCEDURE

Explanation

A PROCEDURE instruction was encountered which wasnot the first instruction executed after a call or

function invocation. A possible cause of this isdropping through into an internal routine rather thaninvoking it properly.


User response

Examine the line, correct the problem, and rerun theprogram.

AZK1018I ERROR 18 process program, LINElineno: THEN EXPECTED

Explanation

All IF and WHEN clauses in REXX must be followed bya THEN clause. Some other clause was found when aTHEN was expected.


User response

Examine the line, and correct the error.

AZK1019I ERROR 19 process program, LINElineno: STRING OR SYMBOLEXPECTED

Explanation

Following either the keyword call or the sequenceSIGNAL ON or SIGNAL OFF, a literal string or a symbolwas expected but neither was found.


User response

Add the literal string or symbol that is needed.

AZK1020I ERROR 20 process program, LINElineno: SYMBOL EXPECTED

Explanation

In the clauses END, ITERATE, LEAVE, NUMERIC,PARSE, and PROCEDURE, a symbol can be expected.Either it was not present when required or some othertoken was found. Alternately, DROP and the EXPOSEoption of PROCEDURE expect a list of symbols. Someother token was found.


User response

Correct the REXX program, and rerun.

AZK1021I ERROR 21 process program, LINElineno: INVALID DATA ON END OFCLAUSE


Explanation

A clause such as SELECT or NOP is followed by sometoken other than a comment.


User response

Correct the line, and rerun the REXX program.

AZK1022I ERROR 22 process program, LINElineno: INVALID CHARACTERSTRING

Explanation

This error results if a literal string contains charactercodes that are not valid in a particular implementation.This might be because some characters are impossibleor because the character set is extended in some wayand certain character combinations are not allowed.


User response

Examine the line, and correct the error.

AZK1024I ERROR 24 process program, LINElineno: INVALID TRACE REQUEST

Explanation

The setting specified on a trace instruction or as theargument to the trace built-in function starts with acharacter that does not match one of the valid tracesettings. This error is also raised if an attempt is madeto request trace scan when inside any kind of controlconstruct.


User response

Contact Software Support to obtain additionalassistance.

AZK1025I ERROR 25 process program, LINElineno: INVALID SUB-KEYWORDFOUND

Explanation

An unexpected token has been found in the position inan expression where a particular sub-keyword wasexpected.


User response

Correct the line, and resubmit.

AZK1026I ERROR 26 process program, LINElineno: INVALID WHOLE NUMBER

Explanation

One of the following either did not evaluate to a wholenumber or is greater than the implementation limit forthese uses: (1) the expression for digits or fuzz in thenumeric instruction, (2) a parsing positionalparameter, (3) a repetition phrase of a DO clause, or(4) the right-hand of the POWER("*") operator. Thiserror is also raised if a negative repetition count isfound in a DO clause.


User response

Fix it, mix it, and rerun it.

AZK1027I ERROR 27 process program, LINElineno: INVALID DO SYNTAX

Explanation

Some syntax error has been found in the DOinstruction. This might be using the TO, BY, or FORsub-keywords twice or when there is no controlvariable specified.


User response

Fix the error, and rerun the job.

AZK1028I ERROR 28 process program, LINElineno: INVALID LEAVE ORITERATE

Explanation

A LEAVE or ITERATE instruction was encountered inan invalid position. Either no loop is active or the namespecified on the instruction does not match the controlvariable of an active loop. Note that since internalroutine calls and the INTERPRET instruction protectDO loops, they become inactive. A common cause ofthis error is attempting to use the SIGNAL instructionto transfer control within or into the loop.


User response

Fix the problem on the line, and rerun the job.

AZK1029I ERROR 29 process program, LINElineno: ENVIRONMENT NAME ISTOO LONG


Explanation

The environment name specified by the ADDRESSinstruction is longer than permitted for the systemunder which REXX is running. This message shouldstate the maximum length permitted.


User response

Correct the problem, and rerun the REXX program.

AZK1030I ERROR 30 process program, LINElineno: NAME OR STRING TOOLONG

Explanation

This error results if there is an implementation limitthat is exceeded for the length of a variable name, alabel name, or a literal string.


User response

Fix the error, and rerun the REXX program.

AZK1031I ERROR 31 process program, LINElineno: NAME STARTS WITHNUMBER OR "."

Explanation

A value may not be assigned to a variable whose namestarts with a numeric digit or a period (if it wereallowed, one could redefine numeric constants).


User response

Correct the error, and rerun the REXX program.

AZK1033I ERROR 33 process program, LINElineno: INVALID EXPRESSIONRESULT

Explanation

The result of an expression in an instruction was foundto be invalid in the particular context it was used. Thismay be due to an illegal fuzz or digits value in anumeric instruction (fuzz may not become larger thandigits).


User response


AZK1034I ERROR 34 process program, LINElineno: LOGICAL VALUE NOT 0 OR1

Explanation

The expression in an IF, WHEN, DO WHILE, or DOUNTIL phrase must result in a 0 or a 1, as must anyterm operated on by a logical operator.


User response

Fix the bug, and rerun the program.

AZK1035I ERROR 35 process program, LINElineno: INVALID EXPRESSION

Explanation

This is due to a grammatical error in an expression,such as ending it with an operator or having twooperators adjacent with nothing in between. It mayalso be due to an expression that is missing when oneis required. A common error is to include specialcharacters in an intended character expressionwithout enclosing them in quotes.


User response

Examine the line, fix the problem, and then rerun.

AZK1036I ERROR 36 process program, LINElineno: UNMATCHED "(" INEXPRESSION

Explanation

This is due to not pairing parentheses correctly withinan expression. There are more left parentheses thanright parentheses.


User response


AZK1037I ERROR 37 process program, LINElineno: UNEXPECTED "," OR ")"

Explanation

Either a comma has been found outside a functioninvocation or there are too many right parentheses inan expression.



User response


AZK1038I ERROR 38 process program, LINElineno: INVALID TEMPLATE ORPATTERN

Explanation

Within a parsing template, either a special characterthat is not allowed has been found or the syntax of avariable pattern is incorrect. This error may also beraised if the WITH sub-keyword is omitted in a parsevalue instruction.


User response

Examine the program, fix the problem, and then rerun.

AZK1039I ERROR 39 process program, LINElineno: EVALUATION STACKOVERFLOW

Explanation

The expression is too complex to be evaluated by thelanguage processor. There are too many nestedparentheses, functions, etc. The message should statethe actual restriction.


User response

Examine the program, simplify the expression, andthen rerun.

AZK1040I ERROR 40 process program, LINElineno: INCORRECT CALL TOROUTINE

Explanation

The specified built-in or external routine does exist buthas been used incorrectly. Either invalid argumentswere passed to the routine, the program invoked wasnot compatible with the REXX language processor, ormore than an implementation-limited number ofarguments were passed to the routine.


User response

Examine the statement calling the routine, and correctit.

AZK1041I ERROR 41 process program, LINElineno: BAD ARITHMETICCONVERSION

Explanation

Either one of the terms involved in an arithmeticoperation is not a valid number or its exponentexceeds the implementation limit.


User response

Examine the program, and correct the problem.

AZK1042I ERROR 42 process program, LINElineno: ARITHMETIC OVERFLOW/UNDERFLOW

Explanation

The result of an arithmetic operation requires anexponent that is outside the range supported by theimplementation. This can happen during evaluation ofan expression (commonly an attempt to divide anumber by 0) or possibly during the stepping of a DOloop control variable.


User response


AZK1043I ERROR 43 process program, LINElineno: ROUTINE NOT FOUND

Explanation

A function that has been invoked within an expressioncannot be found, or a subroutine that has beeninvoked by call cannot be found. No label with thespecified name exists in the program. It is not thename of a built-in function, and the languageprocessor has been unable to locate it externally. Thename has probably been typed incorrectly, or a symbolor literal string is adjacent to a "(" when it was meantto be separated by a blank or some other operator.Functions referenced in an INTERPRET statement thatare not product built-in functions and have not beenpreviously referenced will also result in this error.


User response


AZK1044I ERROR 44 process program, LINElineno: FUNCTION DID NOTRETURN DATA


Explanation

An external function has been invoked within anexpression, but even though it appeared to endwithout error, it did not return data for use within theexpression.


User response


AZK1045I ERROR 45 process program, LINElineno: NO DATA SPECIFIED INFUNCTION RETURN

Explanation

The program has been called as a function, but anattempt is being made (by RETURN) to return withoutpassing back any data.


User response


AZK1046I ERROR 46 process program, LINElineno: INVALID VARIABLEREFERENCE

Explanation

An attempt to indirectly reference a variable is invalid.This would most likely occur on an EXPOSE orINTERPRET instruction. For example: EXPOSE (Y)where Y is a number.


User response


AZK1048I ERROR 48 process program, LINElineno: FAILURE IN SYSTEMSERVICE

Explanation

Some system service used by the REXX languageprocessor (such as stream input or output) has failedto work correctly; hence, normal execution cannotcontinue.


User response


AZK1049I ERROR 49 process program, LINElineno: INTERPRETATION ERROR

Explanation

Implementations of the REXX language will normallycarry out internal self-consistency checks duringexecution. This message indicates that some kind ofsevere error has been detected within the languageprocessor or execution process.


User response

Contact Software Support for further assistance.

AZK1064I ERROR 64 process program, LINElineno: UNIMPLEMENTEDFEATURE

Explanation

The program has used a REXX language feature whichis not supported by this version of the REXXinterpreter. Code 64 is an extended error code usedonly by REXX.


User response

Check documentation for support of the feature.Change the REXX program to bypass use of thefeature.

AZK1066I ERROR 66 process program, LINElineno: AMPERSAND VARIABLESUNSUPPORTED

Explanation

The program has used the ampersand as a prefix to asymbol. The REXX interpreter does not allow this.


User response


AZK1067I ERROR 67 process program, LINElineno: DUPLICATE LABEL

Explanation

The program has defined the same label name twice.


User response

Change the label on one of the two statements.


AZK1068I ERROR 68 process program, LINElineno: FUNCTION NAME > 32CHARACTERS

Explanation

The program has defined or referenced a functionwhose name exceeds the maximum function namelength of 32 characters.


User response

Change the function name to a shorter name.

AZK1069I ERROR 69 process program, LINElineno: FUNCTION HAS TOO FEWARGUMENTS

Explanation

The program has called a function that requires morearguments than specified on the function call.


User response

Add the necessary arguments to the function call.Check the documentation for the specified function.

AZK1070I ERROR 70 process program, LINElineno: FUNCTION HAS TOO MANYARGUMENTS

Explanation

The REXX program has called a function that requiresfewer arguments than specified on the function call.


User response

Remove the superfluous arguments to the functioncall. Check the documentation for the specifiedfunction.

AZK1071I ERROR 71 process program, LINElineno: CODE VERSION IS DOWNLEVEL

Explanation

The REXX program was compiled with a version of theREXX interpreter which is lower than the version usedto execute the program.


User response

This error should only occur when executing a pre-compiled, saved version of a program or rule. In thiscase, the program or rule should be recompiled andthen re-executed. In all other cases, contact SoftwareSupport for further assistance.

AZK1072I ERROR 72 process program, LINElineno: FUNCTION RETURNEDUNASSIGNED STEM DATA

Explanation

A REXX function written in assembler has returnedincorrect data.


User response


AZK1073I ERROR 73 process program, LINElineno: RECORD REFERENCEEXCEEDS VARIABLE VALUE

Explanation

This error should not occur.


User response


AZK1074I ERROR 74 process program, LINElineno: MAX STATEMENT COUNT

Explanation



User response


AZK1075I ERROR 75 process program, LINElineno: ELSE NEEDS SEMICOLON

Explanation



User response



AZK1076I ERROR 76 process program, LINElineno: VARIABLE VALUE TOOLONG

Explanation

The REXX program attempted to assign a value to avariable. The string value exceeded the maximumallowed length.


User response

Shorten the string value.

AZK1077I ERROR 77 process program, LINElineno: CODE AREA FULL

Explanation

The REXX program could not be compiled. The targetcode area is not large enough to hold the result of thecompiled program.


User response

Shorten the REXX program by dividing it intosubroutines, and store these subroutines as separatemembers.

AZK1080I ERROR 80 process program, LINElineno: PULL FOUND EMPTYQUEUE

Explanation

This error should not occur. A null string is returnedinstead for compatibility with older releases of ProductREXX. Contact Software Support for furtherassistance.


User response


AZK1081I ERROR 80 process program, LINElineno: NOT SUPPORTED WITHININTERPRET

Explanation

The REXX program executed an INTERPRETinstruction that contained a REXX structure notsupported in INTERPRET.


User response

Modify the interpreted code. If the problem cannot beresolved, contact Software Support.

AZK1082I ERROR 82 process program, LINElineno: ARRAY BOUNDARYEXCEEDED

Explanation

The REXX program was attempting to store an elementof an array. The element number was larger than thedeclared dimension of the array.


User response


AZK1083I ERROR 83 process program, LINElineno: CODE BLOCK TOO LARGE,EVAL STACK FULL

Explanation

If this occurs during the compile phase, the program isusing a structure too complex for the compiler tohandle. This could occur if a SELECT statement has toomany WHEN clauses or if there are too many nestedcontrol structures.


User response

Reduce the complexity of the structure flagged, andretry the compile. If the problem cannot be resolved,contact Software Support.

AZK1084I ERROR 84 process program, LINElineno: TOO MANY SYMBOLS,SYMBOL TABLE FULL

Explanation

If this occurs during the compile phase, the program isusing too many symbols and the symbol table hasoverflowed.


User response

Reduce the number of symbols used by the program,and retry the compile. If this does not solve theproblem, contact Software Support.

AZK1085I ERROR 85 process program, LINElineno: INVALID USE OFEXTENDED VARIABLE TYPE


Explanation

The REXX program has attempted to use a variable in amanner that is not supported. This could occur if aproduct global variable is used as the control variablein a controlled repetitive loop (e.g. DO GLOBAL.I = 1TO 10).


User response

Modify the REXX program so that it does not use aglobal variable as the loop control variable.

AZK1086I ERROR 86 process program, LINElineno: INVALID GLOBAL SYMBOL

Explanation

A Product REXX global symbol whose derived nameexceeds the Product REXX global variable symbollength limit of 50 characters has been used.


User response

Check the statement in error, and determine whichsymbol substitution caused the derived name of aglobal variable to exceed the specified limit. Modifythe program to use a shorter derived name.

AZK1087I ERROR 87 process program, LINElineno: INVALID INTERNALOBJECT

Explanation

This is an internal Product REXX error.


User response

Please contact Software Support to obtain additionalassistance.

AZK1088I ERROR 88 process program, LINElineno: INTERPRETER STACKERROR

Explanation

This is an internal Product REXX error.


User response

Please contact Software Support to obtain additionalassistance.

AZK1090I var1 var2 var3 var4 var5 var6 var7var8 var9 var1 0var11

Explanation

Message : SWS1090I REXX abend in OPRXCMRU+x'offset'. This message is normally accompanied by a1049I message which relates to an error 49 in a givenrule type.

User response

Check the given rule. In the case of a variable passedto the given error line, make sure the variable is valid.Display fields such as RULE and others in TraceBrowse. For a test situation of the given rule or REXXprogram, include a SAY statement to print the value ofthe given variable at the of the error. If the error is notrelated to variables, validate the given line, and takeappropriate action. Parameters like BROWSEGLVcould be used if this is a global variable rule error. Seeother browse parameters and use as applicable.

AZK1091I ERROR 91 process program, LINElineno: INVALID OR MISPLACEDOPTIONS STATEMENT

Explanation

The OPTIONS statement contains options which arenot valid. Note that unknown OPTIONS keywords areignored and are not flagged as errors. Only partiallyincorrect OPTIONS keywords are flagged.


User response

Correct the OPTIONS statement, and retry theoperation.

AZK1092I ERROR 92 process program, LINElineno: OVER maxno CLAUSESEXECUTED IN RECOVERY EXIT

Explanation

A REXX program or a rule exceeded the maximumnumber of clauses allowed for a SIGNAL ON syntax orSIGNAL ON HALT recovery routine following a productlimit exceeded condition. The maximum number ofclauses allowed when recovering from a product limittype error is indicated in the error text.


User response

Reduce the number of clauses that are executed in thelimit failure recovery routine.


AZK1093E ERROR 93 process program, LINElineno: GLOBAL VARIABLEWORKSPACE OVERFLOW (parmval- wrkspc)

Explanation

A shared/permanent global variable or temporaryglobal variable value cannot be stored successfully.This message may be issued under a number ofcircumstances if a global or global-temporary variableupdate/addition fails. The conditions causing thismessage to be issued are: 1) The number of globalvariables now allocated and in-use (GLOBALUSED orRXWSGVCN for temporary workspace) exceeds themaximum count limit configured by the GLOBALMAX(shared/permanent variables) or GLOBALTEMPMAX(temporary variables) parameters. You must use theISPF C.3 display Note that you must use the ISPF C.3panel display, selecting "RXWS GLVEVENT. WORKSPACE", in order to view RXWSGVCN and obtain thetemporary workspace variable count. 2) There isinsufficient free space anywhere within the globalworkspace to update or add a variable's value. Thevalue requires multiple workspace segments (RXGV's)for storage and enough free RXGV's could not be foundon the free element chain (RXWSFCCN /GLOBALFREEAREAS), or there was insufficient un-allocated space at the end of the workspace(RXWSLN / GLOBALSIZE minus RXWSNXFR /GLOBALNEXT). Contiguous RXGV freespace blocks arerequired for allocation of the value storage area. Notethat the parameters GLOBALFREEAREAS,GLOBALSIZE, and GLOBALNEXT apply ONLY to theshared/permanent workspace. For the temporaryworkspace, you must examine the RXWS field valueusing the ISPF C.3 "RXWS GLVEVENT. WORK SPACE"block display. No product parameters map thesevalues for the temporary workspace. The word "TEMP"is inserted into the message as the last word (withinfinal parentheses) if the TEMPORARY globalworkspace has overflowed. GLVEVENT. stem andinternal-use global stem variables are allocated withinthe temporary global workspace. Otherwise, the word"TEMP" is not present in the message and it is theshared/permanent global workspace that hasoverflowed. GLOBAL., and GLOBAL0. throughGLOBAL9. stem variables are in the shared/permanentworkspace area.


User response

You may need to analyze the contents of the globalvariable database using the global variablesapplication, product parameters, or the ISPF C.3RXWS displays. Use the ISPF E.1 panel to remove

unneeded permanent GLOBAL. stem variables.Otherwise, increase the GLOBALMAX orGLOBALTEMPMAX start-up parameters. If theworkspace is too small, you may also need to (re)allocate a larger global variable checkpoint DIVdataset and copy the original DIV into the new oneusing Access Method Services REPRO. To preventfuture out-of-space hard failures, set the warningthreshold percent (GLOBALWARNTHRESH orGLOBALTEMPWARNTH) and interval(GLOBALWARNINTERVAL or GLOBALTEMPWARNIV)so that a threshold is established and reportedperiodically via MSG 4290. Automate this message sothat sufficient notification is given to prevent the out-of-space hard failure limit from being reached beforethe workspaces can be expanded.

AZK1094E ERROR 94 process program, LINElineno: OVER sec SECONDS USEDFOR EXECUTION

Explanation

A rule or REXX program exceeded its wall clock timelimits as set by SEFMAXSECONDS (rule) orREXXMAXSECONDS (REXX program) productparameters. These limits may be overridden usingNOMAXSECONDS or MAXSECONDS=nnnn on the REXXOPTIONS statement.


User response

Determine whether this problem was caused by alooping program or whether the limits are too low. Thelimits that affect all rules/programs can be modified bychanging the xxxPARM limits (SEFMAXSECONDSand/or REXXMAXSECONDS). The limits for theindividual program can be overridden by using theREXX OPTIONS statement as described in the productReference Manual.

AZK1095E ERROR 95 process program, LINElineno: OVER maxno HOSTCOMMANDS ISSUED

Explanation

A rule or REXX program exceeded its host commandlimits as set by SEFMAXCOMMANDS (rule) orREXXMAXCOMMANDS (REXX program) productparameters. These limits may be overridden usingNOMAXCOMMANDS or MAXCOMMANDS=nnnn on theREXX OPTIONS statement.



User response

Determine whether this problem was caused by alooping program or whether the limits are too low. Thelimits that affect all rules/programs can be modified bychanging the xxxPARM limits (SEFMAXCOMMANDSand/or REXXMAXCOMMANDS). The limits for theindividual program can be overridden by using theREXX OPTIONS statement as described in the productReference Manual.

AZK1096E ERROR 96 process program, LINElineno: OVER maxno "SAY"CLAUSES EXECUTED

Explanation

A rule or REXX program exceeded its SAY/TRACElimits as set by SEFMAXSAYS (rule) or REXXMAXSAYS(REXX program) product parameters. These limits maybe overridden using NOMAXSAYS or MAXSAYS=nnnnon the REXX OPTIONS statement.


User response

Determine whether this problem was caused by alooping program or whether the limits are too low. Thelimits that affect all rules/programs can be modified bychanging the xxxPARM limits (SEFMAXSAYS and/orREXXMAXSAYS). The limits for the individual programcan be overridden by using the REXX OPTIONSstatement as described in the product ReferenceManual.

AZK1097E ERROR 97 process program, LINElineno: OVER maxno CLAUSESEXECUTED

Explanation

A rule or REXX program exceeded its clause limits asset by SEFMAXCLAUSES (rule) or REXXMAXCLAUSES(REXX program) product parameters. These limits maybe overridden using NOMAXCLAUSES orMAXCLAUSES=nnnn on the REXX OPTIONS statement.


User response

Determine whether this problem was caused by alooping program or whether the limits are too low. Thelimits that affect all rules/programs can be modified bychanging the xxxPARM limits (SEFMAXCLAUSESand/or REXXMAXCLAUSES). The limits for theindividual program can be overridden by using theREXX OPTIONS statement as described in the productReference Manual.

AZK1098I lineno TRACE MESSAG

Explanation

Informational message only. This message gives theoutput from the REXX TRACE command.

User response


AZK1099I statement

Explanation

This message is issued when the REXX compilerdetects a an error during compilation. The first line ofthe message lists the statement in error and thesecond line indicates where in the first line the errorwas detected.

User response

Review the REXX statement, and correct the error.

AZK1100S RETRY LIMIT CONVERSIONERROR - VALUE SPECIFIED = val

Explanation

An error was detected while trying to convert thecharacter representation of the specified retry limit(val) to its integer counterpart.

User response

Review the retry limit specification contained in theerror message. If the specified retry limit contains aninvalid value, correct the error, and re-invoke the DSNcommand. If all attempts at correcting the specifiedretry limit fail, contact Software Support for furtherassistance.

AZK1101S TEST LEVEL CONVERSION ERROR- VALUE SPECIFIED = val

Explanation

An error was detected while trying to convert thecharacter representation of the specified test level(val), to its integer counterpart.

User response

Review the test level specification contained in theerror message. If the specified test level contains aninvalid value, correct the error, and re-invoke the DSNcommand. If all attempts at correcting the specifiedtest level fail, contact Software Support for furtherassistance.


AZK1102S subsys NOT VALID SUBSYSTEMID, COMMAND TERMINATED

Explanation

A subsystem control table that corresponded to thesubsystem name contained in the error message couldnot be located by the SSCT chain scan logic.

User response

If the subsystem name was specified on the SYSTEM()command argument, review the name, and revise theSYSTEM() specification, if necessary. If a SYSTEM()command line argument was not specified, theproduct-provided default value may not beappropriate for your installation. This value wasobtained from the local copy of the DSNHDECP Db2parameters module, if one could be found. If a localcopy of the DSNHDECP parameters module containsan invalid value, run the JCL jobstream contained inthe AZK CNTL data set member ZAPDECP afterupdating the REP control card. If a local copy of theDSNHDECP parameters module was not found, theproduct will attempt to use the standard IBM defaultsubsystem, DSN. For further assistance in providingthe product with the correct subsystem name value,contact Software Support.

AZK1104S Subsystem subsys is not a validDB2 subsystem

Explanation

The SSCT located for the subsystem name that wasextracted is neither a valid product SSCT nor a validDB2 SSCT.

User response

If the subsystem name was specified on the SYSTEM()command argument, review the name, and revise theSYSTEM() specification, if necessary. If a SYSTEM()command line argument was not specified, theproduct provided default value may not be appropriatefor your installation. This value was obtained from thelocal copy of the DSNHDECP Db2 parameters module,if one could be found. If a local copy of the DSNHDECPparameters module contains an invalid value, run theJCL jobstream contained in the S__ CNTL data setmember ZAPDECP after updating the REP control card.If a local copy of the DSNHDECP parameters modulewas not found, the product will attempt to use thestandard IBM default subsystem, DSN. If the problemcannot be resolved, contact Software Support.

AZK1105S LOAD FOR DSNECP00 FAILURE

Explanation

The attempt to load the renamed version ofDSNECP00 has failed.

User response

Ensure that the product installation process wascompleted successfully. Ensure that the load librarycontaining the renamed version of DSNECP00 isaccessible by the product. If all attempts to correctthe problem situation fail, contact Software Supportfor further assistance.

AZK1106S subsys NOT OPERATIONAL, RETRYCOUNT ZERO

Explanation

The SSCT for the product indicated that the product isnot currently active.

User response

Determine if the product may have started andterminated abnormally. If so, review theaccompanying messages in the SYSLOG. If the productdid not terminate abnormally, issue the appropriatestart command. If necessary, contact SoftwareSupport for further assistance.

AZK1110S CONNECTION FAILURE RC = rcodeREASON = rsncode

Explanation

The attempt to connect to the remote Db2 subsystemfailed.

User response

Review the return code and the reason code valuescontained in the error message. Compare the returncode and reason code with those listed in the IBM SQLApplication Programming Manual, and take theappropriate action. If all attempts to correct theproblem fail, contact Software Support for furtherassistance.

AZK1112S DISCONNECT FAILURE RC = rcodeREASON = rsncode

Explanation

The attempt to disconnect from the remote Db2subsystem has failed.

User response

Review the return code and the reason code valuescontained in the error message. Compare the return


code and reason code with those listed in the IBM SQLApplication Programming Manual, and take theappropriate action. If all attempts to correct theproblem fail, contact Software Support for furtherassistance.

AZK1113S COMMAND REJECTED - cmd CMDNOT SUPPORTED UNDER DSN

Explanation

The subcommand specified (cmd) is not supportedunder the DSN command.

User response

Review the command string entered. Revise thecommand string, if appropriate. Re-enter the revisedcommand string. If the problem cannot be resolved,contact Software Support.

AZK1114R msgtext

Explanation

Module OPDSN10 issued the current message(msgtext) as a prompt for valid subcommand input.

User response

Respond with an appropriate subcommand name, orenter the END subcommand if processing is complete.

AZK1115S ERROR ISSUING SUBCOMMANDPROMPT - RC = rcode

Explanation

An error occurred either issuing the subcommandprompt or while waiting for valid subcommand input.

User response


AZK1117S COMMAND BUFFER SCAN ERROR -RC = rcode

Explanation

An attempt to scan the command buffer utilizing theservices of IKJSCAN failed.

User response

Review the command string entered. Revise thecommand string, if appropriate. Re-enter the revisedcommand string. If the problem cannot be resolved,contact Software Support.

AZK1118S RUN SUBCOMMANDS CAN NOTHAVE A PROGRAM PARAMETERAND A CP PARAMETER

Explanation

The PROGRAM and CP parameters of the RUNsubcommand are mutually exclusive.

User response

Revise the subcommand string entered. If the programto be executed is not a TSO command processor,specify only the PROGRAM() parameter. If the programto be executed is a TSO command processor, specifyonly the CP parameter.

AZK1119S RUN SUBCOMMAND REQUIRES(1)PROGRAM PARAMETER OR(2)PLAN AND CP PARAMETER

Explanation

The RUN subcommand requires that either thePROGRAM parameter be specified or the PLAN and CPparameters be specified.

User response

Revise the subcommand string entered. If the programto be executed is not a TSO command processor,specify only the PROGRAM() parameter. If the programto be executed is a TSO command processor, specifythe PLAN and CP parameters.

AZK1120S DSNRLI func FUNCTION FAILED.RC = rcode REASON = rsncode

Explanation

The RRSAF function (func) failed.

User response

Review the return code and the reason code valuescontained in the error message. Compare the returncode and reason code with those listed in the IBM SQLApplication Programming Manual, and take theappropriate action. If all attempts to correct theproblem fail, contact Software Support for furtherassistance

AZK1121I PLEASE WAIT...CONNECTIONRETRY IN PROGRESS

Explanation

The remote Db2 subsystem is currently not active anda RETRY() value greater than one (1) was specified.The connection request will be retried.


User response

No action required.

AZK1122I COMMAND SPUFI IGNORED,VALID ISPF ENVIRONMENT MUSTEXIST

Explanation

The SPUFI subcommand requires that a valid ISPFenvironment exist.

User response

Re-invoke the DSN command from within ISPF. If theerror persists, contact Software Support to obtainadditional assistance.

AZK1123S COMMAND REJECTED, CMD NOTSUPPORTED UNDER DSN

Explanation

The subcommand specified is not supported under theDSN command.

User response

Review the command string entered. Revise thecommand string, if appropriate. Re-enter the revisedcommand string. If the error condition persists despitecorrecting errors in the command string that wasentered, contact Software Support.

AZK1126S PLAN OPEN FAILURE RC = rcodeREASON = rsncode

Explanation

The attempt to open the application plan failed.

User response


AZK1127S PLAN CLOSE FAILURE RC = rcodeREASON = rsncode

Explanation

The attempt to close the application plan failed.

User response


AZK1129R ENTER TSO COMMAND

Explanation

Module OPDSN10 issued the current message as aprompt for a valid TSO command.

User response

Respond with a valid TSO command name.

AZK1130S ERROR ISSUING TSO COMMANDPROMPT - RC = rcode

Explanation

An error occurred either while issuing the TSOcommand prompt or while waiting for valid TSOcommand input.

User response


AZK1131S cmd NOT VALID COMMAND

Explanation

The TSO command (cmd) entered is not a validcommand.

User response

Correct the value specified and re-enter the RUNsubcommand. If the error persists, contact SoftwareSupport for further assistance.

AZK1132S cmd ENDED DUE TO ERROR

Explanation

The DSN command (cmd) has ended due to an abenddetected in a user task.

User response

Correct the error condition in the program or TSOcommand that was specified, and re-enter the DSNcommand. If the error condition persists, contactSoftware Support for further assistance.

AZK1133S MODULE program NOT FOUND


Explanation

The module name specified on the PROGRAM()parameter of the RUN subcommand could not befound.

User response

Correct the value specified, and re-enter the RUNsubcommand. If the error persists, contact SoftwareSupport for further assistance.

AZK1134S UNABLE TO ESTABLISH THE STAXEXIT

Explanation

OPDSN01 - the STAX manager was unable to establishthe STAX exit.

User response

Attempt to invoke the DSN command again. If theerror persists, contact Software Support for furtherassistance.

AZK1135S UNABLE TO TERMINATE THE STAXEXIT

Explanation

OPDSN01 - the STAX manager was unable toterminate the STAX exit.

User response

Attempt to invoke the DSN command again. If theerror persists, contact Software Support for furtherassistance.

AZK1136S STAX EXIT INTERNAL LOGICERROR

Explanation

OPDSN01 - the STAX manager determined that anattempt was made either to remove the STAX exitenvironment when one did not exist or to establish theSTAX exit environment when one already existed.

User response


AZK1137S ERROR EXECUTING TSOCOMMAND RC = rcode REASON =rsncode

Explanation

OPDSN10 detected that the command entered was aTSO command; however, an error was detected while

attempting to invoke the TSO command. The abovemessage depicts the return code and reason codevalues received from the product TSOEXEC serviceroutine.

User response

Examine the TSO command entered, and correct thecommand string if an error was detected. If the errorcondition persists despite correcting any commandstring errors, contact Software Support for furtherassistance.

AZK1138I SET_CLIENT_ID CALL FAILED -DB2 NOT AT PROPERMAINTENANCE LEVEL ORRELEASE. SUBSYSTEM: subsys

Explanation

A client requested a SET_CLIENT_ID command beissued to Db2. This is usually invoked via theSQLESETI client function. However, Db2 rejected therequest. This probably is due to APAR PQ67691 (or itsequivalent) being applied.

User response

This is not a serious problem. The Db2 DISPLAYTHREAD display just will not contain additionalinformation that was supplied by the client.

AZK1154S COMMAND BUFFER INTERNALFORMAT ERROR

Explanation

During an attempt by the DSN command processor toanalyze the contents of the command buffer, it wasdetermined that the command buffer had the wronglength, invalid operands, or the wrong format.

User response

Review the command string entered. Revise thecommand string, if appropriate. Re-enter the revisedcommand string. If the error condition persists despitecorrecting errors in the command string that wasentered, contact Software Support for furtherassistance.

AZK1163S COMMAND BUFFER PARSE ERROR- RC = rcode

Explanation

The IBM TSO parse routine, IKJPARS, returned a non-zero return code after attempting to parse the DSNcommand string.


User response

Review the accompanying TSO error messages in theSYSLOG. Review the command string entered. Revisethe command string, if appropriate. Take actionrecommended in the TSO messages manual. If allattempts at revised command string entry fail, contactSoftware Support for further assistance.

AZK1250I var1 var2

Explanation

The message ID used to display parameter valuerequested with an xxxPARM command.

User response


AZK1251T THE VALUE OF THE parmnamePARAMETER WAS ROUNDED UPTO parmval BYTES

Explanation

The parameter was rounded to a 1K (1024) byteboundary.

User response


AZK1252T THE VALUE SPECIFIED FOR THEparmname PARAMETER WASCHANGED FROM parmval1 TOparmval2

Explanation

The value of the parameter was changed.

User response


AZK1253T THE VALUE OFROLLBACKPOSITIVERC WASCHANGED TO 'NO' BECAUSEIGNOREPOSITIVESC WAS SET TO'YES'

Explanation

The value of the ROLLBACKPOSITIVERC parameterwas changed to 'NO' because the IGNOREPOSITIVESCparameter was set to YES. ROLLBACKS for positiveSQL codes cannot be performed if they are beingignored.

User response

None. This message is informational only. IfROLLBACKS are required for positive SQL codes, thenset IGNOREPOSITIVESC to 'YES', then setROLLBACKPOSITIVERC to 'YES'.

AZK1254T THE VALUE OFROLLBACKPOSITIVERC CANNOTBE CHANGED TO 'YES' BECAUSEIGNOREPOSTIVESC IS 'YES'

Explanation

The value of the ROLLBACKPOSITIVERC parametercannot be set to 'YES' because IGNOREPOSITIVESCparameter is set to YES. ROLLBACKS for positive SQLcodes cannot be performed if they are being ignored.

User response

None. This message is informational only. IfROLLBACKS are required for positive SQL codes, thenset IGNOREPOSITIVESC to 'YES', then setROLLBACKPOSITIVERC to 'YES'.

AZK1255E parmname - cannot be changedafter initialization

Explanation

Many of product parameters may be changed at anytime, but some of them can only be set once duringinitialization. The parameter you attempted to changemust be set during product initialization.

User response

Update the initialization REXX exec xxxxIN00. Thesechanges will take effect the next time the product isstarted.

AZK1256E parmname - cannot be changed

Explanation

Many of the S__ parameters may be changed at anytime; some of them can only be reset duringinitialization, while others are used merely for displaypurposes and cannot be reset at all. The parameteryou entered may not be changed.

User response

Update the initialization REXX exec xxxxIN00. Thesechanges will take effect the next time the product isstarted.

The variable fields of the message text are: parmparameter name

AZK1257E parmname - cannot be displayed


Explanation

The parameter you selected cannot be displayed.

User response

Check the manual to see if the parameter yourequested is spelled correctly.

AZK1258E desc - errmsg suffix

Explanation

The ADDRESS AZK processing routine found an errorin the parameter text string passed with the MODIFYPARM command. The parameter text string is invalid.MODIFY PARM command processing is aborted.

User response

Validate the VALUE keyword value, correct it for errors,and re-initiate the command. For more details on theMODIFY PARM command, refer to your Product User'sGuide.

AZK1259E PARAMETER parmname POINTSTO UNINITIALIZED ENUMERATEDVALUE IN cblk AT addr

Explanation

During a parameter display operation, a productparameter table entry pointed to an un-initialized fieldwithin a product control block. The field should beinitialized with one of the valid values enumerated forthe parameter.

User response

The product parameter's value is displayed as"*INTERNAL-ERROR*", and processing continues.

AZK1262I grpdesc grpname

Explanation

The parameter group (grp) being listed by thisxxxPARM command could not be found. The commandis terminated.

User response

Review the xxxPARM command being executed,checking the group operand and whether or not thereis a group listing for it. Refer to the product ServerStarted Task Parameters Guide for the details on usingthe xxxPARM command and its group operand.

AZK1263E prefix-parmval-suffix

Explanation

This message is never meant to be seen. It is used byOPPAFU to convert product parameters to printablecharacter strings.

User response

If you see this message, an internal error hasoccurred. Contact Software Support.

AZK1264W No parameter value information isavailable.

Explanation

The xxxPARM parameter you are using is not available.The SAZKPARM command is terminated.

User response

The parameter you are trying to set using SAZKPARMis not supported or not valid in this release of theproduct. Check the parameter in the productdocumentation.

AZK1265W WARNING: parmnamePARAMETER (val) CONTAINS TOOFEW QUALIFIERS TO ENSUREPROPER HTTP COOKIEOPERATION

Explanation

The host domain name parameter contains too fewqualifiers (name segments separated by periods) toensure that Web browsers will properly store andtransmit HTTP cookies. At least three levels ofqualification (two levels if the name endswith .com, .edu, .net, .org, .gov, .mil, or .int) are usuallyrequired to ensure that HTTP cookies are stored andlater retransmitted properly.

User response

The parameter is accepted but is always folded to alowercase string. The server's built-in browser-basedadministration utilities require HTTP cookies forproper operation. These administration utilities maynot function correctly using the host domain namestring now set.

AZK1266W WARNING: parmnamePARAMETER (val) MAY CAUSEINCONSISTENT OPERATIONUSING HTTP COOKIES

Explanation

The host domain name parameter contains a dot-notation format IP address. Browser anomalies may


arise that cause HTTP cookies to be stored improperlyor retransmitted incorrectly when using a dot-notationhost domain name value.

User response

The parameter is accepted. The server's built-inbrowser-based administration utilities require HTTPcookies for proper operation. These administrationutilities may not function correctly using the hostdomain name string now set.

AZK1275S ABEND abcode INAUTHORIZATION ROUTINEmodname+offset

Explanation

An abend occurred in the authorization checkingroutine.

User response


The variable fields of the message text are: abcdabend code mod module name off module offset

AZK1277S cblk Control block not found

Explanation

The MODIFY PARM functional routine has been passedan invalid product control block name.

User response

First, check the MODIFY PARM command, correct anyerrors, and rerun. If the problem persists, verify thatall of the product modules are at the same releaselevel. Also, check that the last product installation wassuccessful. If all of the above are checked and theproblem remains, gather all related problem data(error data, SVFX level, install information), andcontact Software Support for further assistance.

AZK1281E service desc FAILED, RC=rcode,DETECTED AT addr

Explanation

This is a generic error message used to describe awide variety of errors. The message text gives adescription of the current operation (service) and whatthe current operation was trying to do.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore error messages referring to the current problem.

If possible, fix the problem identified by the errormessages, and retry the operation. If the problemcannot be resolved, contact Software Support forfurther assistance.

AZK1290H jb parmname parmval

Explanation

This message logs a change to the product parametersvia the ADDRESS AZK MODIFY command. Themessage contains the name of the product parameterand its new value.

User response

No action is required. This message is written to thelog for informational and tracking purposes only.

The variable fields of the message text are: parmparameter field name parmval parameter field value

AZK1291W Warning: parmname is an obsoleteparameter

Explanation

This message is issued when an obsolete parametervalue is modified.

User response

Refer to the product Server documentation forinformation on this parameter. Modifying an obsoleteparameter may not have the desired effect. In manycases, obsolete parameters have no effect on theserver and are ignored. Obsolete parameters arenormally removed from the product in the nextrelease. You should check the product initializationexec (xxxxIN00) and remove all references to thisobsolete parameter from it.

AZK1292E Exit code ecode is invalid forparmname

Explanation

An invalid exit code has been defined in an internalproduct control block that defines a productparameter table entry.

User response

This is an internal error. Please report this problem toSoftware Support.

AZK1293E errdesc


Explanation

An attempt to set a product parameter has failed. Theerror message describes the reason for the failure.

User response

Review the error message, and attempt to correct theproblem.

AZK1294E desc OF process FOR PARAMETERCHANGE EVENT NOTIFICATIONFAILED WITH RC=rcode

Explanation

A product parameter update attempt was made, butthe system was unable to properly notify anasynchronous process of the change. The update tothe parameter may or may not have been made, but ineither case, the asynchronous process is now in anunknown state.

User response

Review the error message and any others related tothe problem, and notify Software Support. Timingerrors during shutdown normally do not represent aserious condition unless they occur consistently.

AZK1295W PARM parmname AND ANYDEFINE ISPFCONCAT AREMUTUALLY EXCLUSIVE.parmname WILL BE IGNORED.

Explanation

The xxxxIN00 EXEC specifies at least one DEFINEISPFCONCAT statement and the mutually exclusiveISPF PARM statement. All ISPF PARM statements areignored when at least one DEFINE ISPFCONCATstatement is specified. The following is a complete listof the ISPF parameters that will be ignored:EXECDSNAME, COMPEXECDSNAME, ISPLLIBDSNAME,ISPMLIBDSNAME, ISPSLIBDSNAME andISPTLIBDSNAME.

User response

Change the xxxxIN00 EXEC to specify the DEFINEISPFCONCAT statements for all of the requiredlibraries and remove the obsolete PARM NAME(ISP%LIBDSNAME) parameters.

AZK1296T Security optimization processingterminated

Explanation

The TERMINATESECOPT parameter was set to 'YES'causing all security optimization processing to halt.The product continues to operate normally.

User response

If you want to execute with security optimizationactive, you must stop and restart the product.

AZK1297T Logging processing terminated

Explanation

The TERMINATELOGGING parameter was set to 'YES'causing all logging functions to halt. The productcontinues to operate normally.

User response

If you want to execute with logging active, you muststop and restart the product.

AZK1298T Interval recording %1

Explanation

Interval recording was enabled or disabled. Theproduct continues to operate normally.

User response

You can reenable interval recording if theTERMINATEINTERVAL parameter is set to 'NO'.

AZK1299T Interval recording terminated

Explanation

The TERMINATEINTERVAL parameter was set to 'YES'causing all interval recording to halt. The productcontinues to operate normally.

User response

If you want to execute with interval recording active,you must stop and restart the product.

AZK1340I echotext

Explanation

This message is simply an echo of a reply to a WTORissued.

User response

None.

AZK1346E MESSAGE ID AND TEXT ARE TOOLONG


Explanation

While building a WTO or WTOR parameter list, theproduct detected that the combined message ID andmessage text exceeds the system limits. The limit for aWTO is 125 characters, and the limit for a WTOR is122 characters.

User response

This could indicate an internal logic error within theproduct. Contact Software Support for furtherassistance.

AZK1348E NO WTOR REPLY RECEIVED -TIMER EXPIRED

Explanation

A timeout has occurred prior to receiving the responseto a WTO/WTOR.

User response

This could indicate an internal logic error within theproduct. Contact Software Support for furtherassistance.

AZK1349I THE MESSAGE IDENTIFICATIONNUMBER IS wtoID

Explanation

This message is simply an echo of the messageidentification number returned by the WTO/WTOR toidentify the message.

User response

None. The WTO ID can be used to DOM a highlightedmessage.

AZK1364S sysserv RETURN CODE = rcode

Explanation

Some type of error occurred either in the systemmanagement routines of the product or by invoking asystem service (sysserv) directly. See the actual text ofthe message for an explanation. The error wasprobably caused by a failure in an operating systemservice.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate. If theproblem cannot be resolved, contact SoftwareSupport.

AZK1370H jobname rcode desccode mcscnotime msgID msgtext

Explanation

This message is used to document an internallygenerated WTO. It is written to the hardcopy log toidentify the source of the message issued.

msc represents the MCS flags

cno represents the console number

time represents a wait time if the REPLY keyword iscoded

User response

None.

AZK1400S TSO/E is not installed

Explanation

TSO/E (IBM's program product number 5665-293) isrequired to support the use of ISPF/AZK.

User response

Verify that this product is available at your installation.

AZK1401S service CMD(modname) FAILED,RC=rcode

Explanation

AZK called TSO to execute ISPSTART and received anon-zero return code. The ISPF initiation attempt isaborted.

User response

Review the message text, and check why the requestdid not complete successfully. Review your ISPF/AZKenvironment, and take corrective action. If theproblem cannot be resolved, contact SoftwareSupport.

AZK1402S Dialog Manager service serviceerror, RC=rcode

Explanation

A product internal routine called TSO to executeISPSTART and got a dialog manager service error.

User response

Review the ISPF error, checking the service namestring for what service was invoked, and takecorrective action. For additional assistance, contactyour local S__ systems programming support group


AZK1404S ABEND OCCURRED PROCESSINGSUBROUTINE subrout IN MODULEmodname

Explanation

The product ISPF application ABENDed whileextracting information from constants in thesubroutine's prolog.

User response


AZK1405T ABEND OCCURRED PROCESSINGSUBROUTINE subrout IN MODULEmodname

Explanation

The product ISPF application ABENDed whileextracting information from constants in thesubroutine's prolog.

User response


AZK1406S THE ENTRY FOR SUBROUTINEsubrout IN MODULE modnamePOINTS TO SUBROUTINE subrout

Explanation

The ISPF application detected an error in a subroutinevector table.

User response


AZK1407T THE ENTRY FOR SUBROUTINEsubrout IN MODULE modnamePOINTS TO SUBROUTINE subrout

Explanation

The ISPF application detected an error in a subroutinevector table.

User response


AZK1420S service OF DIRECTED LOADLIBRARY (ddname) FAILEDRC=rcode

Explanation

The S__ ISPF application attempted to do a directedload based upon a parameter setting in theOPMS(ISPLLIBDSNAME).

service may be "allocation" or "deallocation"

User response

Check the data set name specified in theaforementioned parameter. After correcting the name,restart the Server address space.

AZK1421E infotext COMMAND infotext

Explanation

The next message is not actually used by any code inthe product. The message is used to reserve a returncode. No action required.

User response

None.

AZK1423E errmsg

Explanation

Product security has denied the current user access toTrace Browse.

User response

If this an undesirable situation, contact the productsystems support group to grant you the requiredaccess.

AZK1424E CURRENT cmd COMMAND NOTAUTHORIZED - errdesc

Explanation

Authorization check failed. The use of AZK/SWS isrestricted by your installation security product.

User response

Contact the person at your installation who installsand maintains the product to obtain access authority.

AZK1440W ISPF LOADLIB at level lvl, butServer LOADLIB at level lvl.Processing continues.

Explanation

The version of the load library allocated to ISPF is at adifferent release than that of the server.


User response

The product ISPF application continues. Theinconsistency between the Server and the ISPF loadlibraries should be resolved.


Explanation


User response

Contact the person at your installation who installsand maintains your installation security product.

AZK1442S COMMAND BUFFER PARSERC=rcode

Explanation

The IBM TSO parse routine, IKJPARS, returned a non-zero return code after attempting to parse a commandstring. The parse process for the command isterminated.

User response

Gather the relevant problem data, and contact yourlocal product systems programming group forassistance.

AZK1443S COMMAND BUFFER INTERNALFORMAT ERROR

Explanation

During an attempt to analyze the contents of thecommand buffer, it was determined that the commandbuffer had the wrong length, invalid operands, or thewrong format.

User response


AZK1444S parmname PARAMETER reqvalSPECIFIED WITHARCHTYPE(parmval)

Explanation

The Trace Browse/view program was invoked withinvalid parameters.

User response


AZK1445S SYSTEM MANAGER SERVICEservice ERROR, RC=rcode

Explanation

The product browse subroutine requestedauthorization in order to validate your request and didnot find the necessary control blocks for thisvalidation. The request is aborted.

User response

This message indicates a possible product ISPFinterface error. Gather the data, and contact your localsystems programming support group.

AZK1446S ISPF service service error, returncode = rcode

Explanation

AZK invoked an ISPF service routine to accomplish theISPF-related task indicated in the error message andreceived a non-zero return code.

User response

Review the message text, and check why the requestdid not complete successfully. Review your ISPF/AZKenvironment, and take corrective action. If the errorpersists, contact Software Support.

AZK1447E Member member not found

Explanation

A BLDL failed to find the specified member.

User response

Examine the data set concatenation to ensure that theproper libraries are allocated. If the error persists,contact Software Support for further assistance.

AZK1448E func failed for member=memberRC=rcode


Explanation

An I/O operation (func) failed while attempting to do aBLDL.

User response

Use this message in conjunction with any othermessages that may accompany it to resolve theproblem. You may also want to examine the data setfor problems. Once the problem is corrected, restartthe product.

AZK1449E ISPF LOADLIB at version version1,Server LOADLIB at version2,please correct inconsistency

Explanation

The version of the load library allocated to ISPF is at adifferent release than that of the server.

User response

The Diagnostic facility will terminate. The libraryinconsistency should be resolved prior to invoking theISPF application.

AZK1450H jobname subsysID

Explanation

This message is used to provide an audit trail in TraceBrowse when using the Trace Browse option of theproduct.

User response

No action is required. This message is for audit trailpurposes only.

AZK1451H jobname subsysID ARCHIVEREVIEW dsname

Explanation

This message is used to provide an audit trail in TraceBrowse when using the Trace Archive View function.

User response

None. This message is for audit trail purposes only.

AZK1452S ABEND abcode REASON rsnOCCURRED IN modname+offset

Explanation

An abend occurred in the browse program.

User response

Check for other errors, and correct the problem. Ifunable to correct the problem, contact SoftwareSupport for further assistance.


Explanation

This is a generic error message used to describe awide variety of product ISPF initialization, execution,and termination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do.

User response


AZK1454S servrout errdesc FAILED,ABEND=abcode, REASONCODE=rsncode

Explanation

This is a generic error message used to describe awide variety of product ISPF initialization, execution,and termination errors. The message text provides thecurrent operation and what the current operation(servrout) was trying to do.

User response


AZK1455S Subsystem subsys not active

Explanation

The specified subsystem is not active

User response

Start the specified subsystem and then restart theISPF application or choose another subsystem ID tostart the ISPF application with


AZK1456S ISPF service service error, returncode = rcode. Unable to start ISPFdialog.

Explanation

AZK invoked an ISPF service routine to start the ISPFdialog and received a terminating return code.

User response

Review the message text, and check why the requestdid not complete successfully. Review your ISPF/AZKenvironment, specifically the DEFINE ISPFCONCATstatements in the xxxxIN00 EXEC, and take correctiveaction. If the error persists, contact Software Support.

AZK1457W Subsystem subsys not active

Explanation

The specified subsystem is not active

User response

The ISPF dialog could not find the specifiedsubsystem.

AZK1600E Module DSNACAF not properlylinked

Explanation

The product-related Db2 interface module tried toload the address of a module needed to connect to theactual Db2 system. The address field was zero. Themodule could not be invoked, and the connection tothe actual Db2 system failed.

User response

Ensure that the product is properly installed. The loadmodule referred to in the error message must beproperly linked with the product module having thesame name. Relink the DSNACAF module, and rerunthe Db2 application program.

AZK1601E Product is not active at this time

Explanation

The product-related Db2 interface module tried tocommunicate with the main product (not Db2) addressspace. The main product address space was notactive. This error normally occurs at the start of SQLapplication program execution.

User response

Ensure that the main product address space is active.Start or restart the main product address space, if

necessary. Rerun the SQL application program fromthe beginning.

AZK1602E Product failed while SQLapplication program executing

Explanation

The product-related Db2 interface module tried tocommunicate with the main product (not Db2) addressspace. The main product address space was notactive. This error normally occurs at the start of SQLapplication program execution.

User response

Ensure that the main product address space is active.Start or restart the main product address space, ifnecessary. Rerun the SQL application program fromthe beginning.

AZK1603E Module DSNTIAR not properlylinked

Explanation

The product-related Db2 interface module tried toload the address of a module needed to connect to theactual Db2 system. The address field was zero. Themodule could not be invoked, and the connection tothe actual Db2 system failed.

User response

Ensure that the product is properly installed. The loadmodule referred to in the error message must beproperly linked with the product module having thesame name. Relink the DSNITAR module, and rerunthe Db2 application program.

AZK1700E service desc FAILED, RC=rcode,DETECTED AT addr

Explanation


User response

Check the error messages and the return codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and retry the operation. If the problemcannot be resolved, contact Software Support.

AZK1701E ERROR CODE queue SENDINGMESSAGE TO %2 QUEUE


Explanation

An error has occurred while attempting to send arecord to a product queue. The most likely cause forthis message is that the queue is full - which isindicated by an error code of 4. In the case of eitherproduct load balancing queue, a queue full conditionresults in no further sessions being sent to this serverby the Group Director until the pending work on thequeue has been significantly reduced. For any othererror code, no additional work will be sent to thisserver and the server must be terminated andrestarted.

User response

Contact your local product systems programminggroup for assistance.

AZK1720E desc func FAILED, RC=rcode,DETECTED AT addr

Explanation

This is a generic error message used to describe errorsthat occurred while attempting to allocate or free(func) a product control block. Allocation failures aretypically an indication of insufficient virtual storage.

User response


AZK1740T Invoking IEFSSREQ for SSIfunction funcode - codedesc

Explanation

The ADDRESS SPOOL S/REXX Host CommandEnvironment or another routine using SysoutApplication Programming Interface (SAPI) commonroutines is invoking a SubSystem (SSI) service. Thismessage is traced, prior to each invocation of theIEFSSREQ SSI gateway macro.

User response

None. The indicated SSI function is invokedimmediately after this message is traced.

AZK1741T IEFSSREQ SSI return code is rcode

Explanation

An invocation of the SubSystem Interface (SSI) macroIEFSSREQ has completed, and the resulting return

code is displayed in the message. This message istraced, following each SSI service request invocationwhen the SSITRACE command option is in effect.

User response

None. The SSI gateway interface has returned with theIEFSSREQ return code shown in the message in R15.

AZK1742T SSOBRETN FUNCTION-SPECIFICRETURN CODE IS rcode

Explanation

An invocation of the SubSystem Interface (SSI) macroIEFSSREQ has completed with return code zero. Thefunction- specific return code is traced by thismessage following each SSI service request invocationmade while the SSITRACE command option is ineffect.

User response

None. The indicated SSI function has completed withthe SSOBRETN return code shown in the message

AZK1743T WAITING FOR NEW SYSOUTFILES FOR sec SECONDS

Explanation

The Sysout Application Programming Interface SSIservice has been invoked with a PUTGET request thathas returned an END-OF-DATA signal. The system willawait new SYSOUT output to become available for theindicated time period. This message is traced prior toentered a WAIT for more SYSOUT output data tobecome available.

User response

None. A WAIT is entered for more SYSOUT outputwhich will expire after the indicated number ofseconds

AZK1744T WAIT TIMELIMIT EXPIRED - END-OF-DATA FOR SYSOUT

Explanation

A Sysout Application Programming Interface SSIservice request routine had entered a WAIT untiladditional SYSOUT output became available, followingreceipt of an END-OF-DATA signal. The timelimit forwaiting on additional SYSOUT output to becomeavailable has expired and the request routine will nowprocess the END-OF-DATA signal. This message istraced when the SSITRACE command option is ineffect.


User response

None. The WAIT for new SYSOUT output is terminatedand the procedure continues by recognizing the END-OF-DATA signal.

AZK1745T NEW SYSOUT FILE NOWAVAILABLE

Explanation

A Sysout Application Programming Interface SSIservice request routine had entered a WAIT untiladditional SYSOUT output became available. Theprimary subsystem has posted the requestor readyand indicated the additional SYSOUT output is nowavailable. This message is traced when the SSITRACEcommand option is in effect. Because another processor writer may select the same SYSOUT file forprocessing, there is no guarantee that the file will beavailable when selection is requested.

User response

None. The WAIT for new SYSOUT output hascompleted and the procedure continues by attemptingto select the new SYSOUT file for processing.

AZK1746T IRXEXCOM action REQUEST FORvarname FAILED WITH RC/SHVRET=rcode/SHVRETval

Explanation

The ADDRESS SPOOL Host Command Interfaceencountered an error while attempting to set, change,or drop (action) a variable in the S/REXX variable pool.The Host Command being processed will be failed witha severe error signal.

User response

Make additional workspace available for execution ofthe product REXX procedure. If the problem persistsand cannot be resolved by increasing the allocatedworkspace, contact Software Support for assistance.

AZK1747T ADDRESS SPOOL ENCOUNTEREDABEND CC=ccode, RS=rsncode ATmodname+offset, PSW=psw,RETRY BY addr

Explanation

The ADDRESS SPOOL Host Command Interfaceencountered an ABEND while processing the currentrequest. The ADDRESS SPOOL host command will beterminated with a failure signal.

User response

Check for other messages which may provide insightinto the cause of the ABEND. Correct the HostCommand, or other conditional as applicable. Ifunresolved, contact Software Support for assistance.

AZK1748T ABEND CC=ccode, RS=rsncode ATmodname+offset, PSW=psw,ACCESSING dsect STRCT AT addr,RETRY BY addr

Explanation

The ADDRESS SPOOL JOBSTATUS commandencountered an ABEND while processing the indicatedextended status information DSECT. The commandabandons further processing of the extended statusinformation returned by the SSI service.

User response

Check for other messages which may provide insightinto the cause of the ABEND. Correct the HostCommand, or other condition as applicable. Ifunresolved, contact Software Support.

AZK1749T SSI ABEND CC=ccode, RS=rsncodeAT modname+offset, PSW=psw,RETRY BY addr

Explanation

An SSI service request call to the IEFSSREQ interfaceABENDed. The ABEND completion code and reasonare displayed in this message. The ABEND may be dueto some error in parameters passed on the servicerequest, or due to some permanent or transientoperating system failure.

User response


AZK1750T DDNAME ddname ALLOCATED TOSYSOUT FILE dsname

Explanation

A SYSOUT dataset has been allocated to the indicatedDDNAME. The caller may now process the SYSOUT fileusing the DDNAME allocation. This message is tracedwhen the SSITRACE command option is in effect. Ifthe DDNAME is "<SKIPPED>", no allocation has beenmade for the indicate SYSOUT dataset, and processingcontinues without an outstanding DDNAME allocation.


User response

None. The SYSOUT allocation remains until the nextSAPI request is processed, or until the environment isended.

AZK1751T DDNAME ddname DEALLOCATED

Explanation

A SYSOUT dataset has been deallocated from theDDNAME provided in the trace message. This messagetraced when the SSITRACE command option is ineffect.

User response

None. The SYSOUT file has been deallocated andprocessing continues.

AZK1752T SPOOL HCE ERROR(rcode/rsncode): rsndesc

Explanation

An error has been encountered while processing aSPOOL Host Command Environment request. Thismessage may be traced after an error, depending ontracing options in effect while processing thecommand. The request is being rejected with thereturn code and reason code (in parentheses), havingthe description given.

User response

Check for other messages which may provide insightinto the cause of the problem. Correct the HostCommand, or other condition as applicable. Ifunresolved, contact Software Support for assistance.

AZK1753T SPOOL HCE SECONDARYERRORrcode/rsncode: rsndesc

Explanation

An error has been encountered while processing aSPOOL Host Command Environment request. Aprevious error has already been logged and this erroroccurred during Host Command Environment cleanup.This message may be traced after an error, dependingon tracing options in effect while processing thecommand. The request is being rejected with theoriginal return and reason codes. This messagedescribes the secondary error.

User response

Check for other messages which may provide insightinto the cause of the problem. Correct the HostCommand, or other condition as applicable. Ifunresolved, contact Software Support for assistance.

AZK1754T SPOOL CLEANUP ABENDCC=ccode, RS=rsncode ATmodname+offset, PSW=psw,action, RETRY RTNE AT addr

Explanation

An ADDRESS SPOOL environment cleanup routineencountered an ABEND during resource recoveryprocessing. Processing to recovery resourcescontinues. One or more resources may not berecovered correctly.

User response


AZK1755T SPOOL HCE MSGrcode/rsncode:rsndesc

Explanation

An informational message traced while processing aSPOOL Host Command Environment request. Thismessage may be traced after an error, depending ontracing options in effect while processing thecommand.

User response

None. Processing continues.

AZK1840E errdesc

Explanation

A syntax error (errdesc) has been detected whileanalyzing the EXECIO command.

User response

Correct the EXECIO command syntax errors, andattempt to execute the REXX program again.

AZK1841E errdesc, RC=rcode

Explanation

Some type of service routine (operating system orproduct specific) failed. The error message identifiesthe type of error .

User response

Check the full text of the error message, and attemptto correct the error.

AZK1842E errdesc1 ddname errdesc2


Explanation

The ddname specified on the EXECIO command is notallocated to the current job.

The error description has two parts, errdesc1 anderrdesc2.

User response

Allocate the appropriate data set to the ddname, orchange the ddname. Then, rerun the REXX program.

AZK1843E ddname io FAILED, RC=rcode,DETECTED AT addr

Explanation

Some type of error occurred during invocation of aproduct I/O routine (io) associated with the EXECIOcommand.

User response


AZK2020S dsname FAILURE RC=rcode

Explanation

An attempt to obtain or release storage on behalf of aproduct subsystem data set (dsname) failed.

User response

Ensure that the address space requesting productsubsystem data set services has a large enoughregion.

AZK2021S desc CANNOT USE SUBSYS FILEALLOCATIONS

Explanation

The product has detected that a system address space(e.g. *master*) or a TSO user has requested that aproduct subsystem data set be opened. This is notallowed.

desc describes, for example, system tasks

User response

The subsystem data set interface may only be used bynormal (non-system) started tasks and batch jobs.

AZK2022S UNKNOWN SUBSYS OPENENVIRONMENT ASID asid

Explanation

The product received an OPEN request for asubsystem data set and is unable to determine whatenvironment the requesting address space (asid) isrunning in.

User response

The subsystem data set interface may only be used byTSO server started tasks.

AZK2023S No server block found forUSERID=jobname

Explanation

The product received an OPEN request for asubsystem data set and found that the request wasnot from a TSO server address space initiated as anoutboard server by the product.

User response

This is most likely an internal problem. ContactSoftware Support for further assistance.

AZK2026S Invalid subsystem file count countfound for server jobname

Explanation

The product has detected an internal error duringclose processing for a subsystem data set. The countof open subsystem data sets for this address spacehas gone negative.

User response

Gather the available problem data, and contact yourlocal product systems programming group for supportin this area.

AZK2027S SUBSYS req cblk VALIDATIONERROR - ADDRESS addr

Explanation

The product has detected an error validating systemcontrol blocks while processing an OPEN request (req)for a product subsystem data set control block.

User response

Gather the available problem data, and contact yourlocal product systems programming group forassistance.


AZK2030S ABEND abcode IN USER EXITmodname+offset

Explanation


User response

Contact the person at your installation who installsand maintains the product security exit routine.

AZK2031W TSO SERVER (procedure) -SYSTSIN BLKSIZE = blksize, USEmaxblksize

Explanation

The BLKSIZE specified on the SYSTSIN DD card in theTSO server started task JCL is one of the factors thatlimits the length of commands that can be sent toservers.

User response

It is recommended that you modify the BLKSIZE onthe SYSTSIN DD card in the specified procedure to theBLKSIZE specified.

AZK2032T SUBSYSTEM DATA req (reqcode)PROCESSED FOR DDNAMEddname - RC=rcode

Explanation

The product's subsystem data set SSI interceptroutine has processed a request. This message tracesthe interception request.

User response

None. This is a diagnostic message.

AZK2040T SRP RABND: SRVR NOTRESPONDING - ASID=asidASCB=ascb TCB=tcb

Explanation

A request for service has been made to server subtaskeither inside or outside the main product addressspace. The requesting task has attempted to revokethe request due to timeout or shutdown, but the serverhas not acknowledged. The request for service hasbeen forcibly revoked.

User response

Depending on the nature of the request, either therequesting task or the server task TCB will becancelled.

AZK2041T SRP SFREE: RQSTR CANNOT BEPOSTED - CODE=pcode -ASID=asid TCB=tcb CNID=cnidTOKEN=token SMAF=addr

Explanation

A request for service has been made to a serversubtask either inside or outside the main productaddress space. The server task is unable to post therequestor task because the task has ended.

User response

The server task continues without posting therequestor.

AZK2042T SRP RBIND: RC=rcode CMTC=addrBEFORE=word1 AFTER=word2TB=tb

Explanation

This is a diagnostic message issued by the servicerequestor/provider interface.

word1 and word2 represent control words before andafter image, respectively

tb represents a trace back point

User response

None. This message is for diagnostic use only.

AZK2043T SRP RWAIT process: CMTC=addrBEFORE=word

Explanation


word represents a control word before image

User response


AZK2044T SRP RWAIT: RC=rcode CMTC=addrBEFORE=word1 AFTER=word2TB=tb

Explanation





User response


AZK2045T SRP RVOKE process: CMTC=addrBEFORE=word

Explanation


word represents a control word before image

User response


AZK2046T SRP RVOKE: RC=rcode CMTC=addrBEFORE=word1 AFTER=word2TB=tb

Explanation



tb represents a traceback point

User response


AZK2047T SRP RABND: RC=rcode CMTC=addrBEFORE=word1 AFTER=word2TB=tb

Explanation




User response


AZK2048T SRP SBIND: RC=rcodeSERVER=svraddr RQSTR=reaaddrTB=tb

Explanation



User response


AZK2049T SRP SFREE: RC=rcodeSERVER=svraddr RQSTR=reqaddrTB=tb

Explanation



User response


AZK2050T SRP SPOST: RC=rcodeCODE=pcode SERVER=svraddrRQSTR=reqaddr TB=tb

Explanation



User response


AZK2082S ss PRODUCT FAILURE DETECTED

Explanation

While processing this request, product main commandprocessing function detected an abnormal shutdownof the product.

User response

Check the abend, what caused it, and how to bestrestart the product. Resolve the current problem andcontinue.

AZK2083W ss OUTBOARD TSO SERVERjobname,ASID=asid FAILED

Explanation

The product End-Of-Memory (EOM) processingdetected the unexpected termination of an outboardTSO server address space. The server should be


restarted automatically by the product, providing thatthe server control limits have not been modified.

User response

You may want to determine why the server failed.

AZK2084E service operand FAILED, RC=rcode,DETECTED AT addr

Explanation

A CALLRTM invocation within the product End-Of-Memory (EOM) failed. The EOM routine was attemptingto cancel an outboard TSO server.

User response

Check the service and return codes, and attempt toresolve the problem. If the problem cannot beresolved, contact Software Support.

AZK2101S userID init FAILED - macroRC=rcode

Explanation

The product security function processing routineGETMAIN for some private storage failed. This storageis required for the processing of security controlblocks.

init represents the initialization type

User response

Review the above storage GETMAIN error. Determinewhy storage is unavailable. Check for any exit thatlimits usage of below-the-line private storage. Resolvethe above problems, and restart.

AZK2102E reqtype REQUEST FOR userIDFAILED - failrsn

Explanation

The product security function routine (reqtype)received a non-zero return code for the listed user ID.

User response

Check the security error for the user ID. Correct theaccess problem, or contact your security administratorfor further assistance.

AZK2103S userID rcode FAILED - RACFCODES rsncode text

Explanation

The product received an unknown return code fromRACF.

User response

Check the related RACF errors, and validate the returncode in the RACF Messages and Codes Manual.Contact your local systems programming group forassistance.

AZK2104E userID init FAILED - failrsn

Explanation

During LOGON command security checking, theproduct security function routine received a non-zeroreturn code from the security package for the currentuserid.


User response

Check the security error for the userid. Correct theaccess problem, or contact your security administratorfor further assistance.

AZK2106H userID init FOR conID AT t2 ON d2

Explanation

Product security function routine issued thisinformational message for the TSO address spaces.


User response


AZK2107H LOGON FAILED FOR userID. rcode1rcode2 rsncode - errtext.

Explanation

Product received a non-zero return code from aLOGON request for an internal task.

The message has two return codes; rcode1 representsthe security module return code, and rcode2represents the RACF (SAF) return code

User response

Check the security error for the userid. Correct theaccess problem, or contact your security administratorfor further assistance.

AZK2108E errmsg1 errmsg2 FAILED -RC=rcode

Explanation

The product failed to extract the security product userID.


User response

Validate the current system situation. Ensure that thesecurity package initialization is complete before theproduct is started.

AZK2120I MEMBER member - additinfo

Explanation

The product copy utility has started copying membersbetween PDSs.

User response


AZK2121S io FAILED, RC=rcode,MEMBER=member,DDNAME=ddname,DSNAME=dsname

Explanation

The product copy utility was copying members fromone PDS to another, and the copy failed.

io represents the current I/O operation

User response

Check the return codes and related MVS errormessages. Ensure that the data sets have enoughspace. Take action as recommended for the returncodes.

AZK2122I MEMBER member RECORD recnoLENGTH lgth IS INVALID

Explanation

The product VB to FB conversion program found arecord with an invalid length.

User response

Fix the invalid record, and rerun the VB to FBconversion program.

AZK2200E service desc FAILED RC=rcode,DETECTED AT addr

Explanation


User response


AZK2300E NLS SERVICE ROUTINE (OPTRTB)ABEND abcode, RS=rsncode ATmodname+offset

Explanation

The NLS service routine detected an abend whileprocessing a request.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact Software Support for assistance.

AZK2301I NLS INVOKED WITH INVALIDFUNCTION CODE funcode

Explanation

The NLS service routine was invoked with an invalidfunction code (in hex).

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact Software Support for assistance.

AZK2302I NO VALID MAPPING FOR srcCODEPOINT srccp TO output -SUBSTITUTING subcp

Explanation

The NLS service routine was invoked for conversion ofa DBCS character stream to/from ASCII/EBCDIC. Novalid DBCS codepoint is defined for the input DBCScode point.

src represents the source encoding, however srccprepresents the source codepoint (in hex)

subcp represents the substitution codepoint

User response

The DBCS codepoint is converted to a standardsubstitution character and the operation continues.


Ensure that the character stream passed to theconversion routine contains only DBCS characters thathave defined translation codepoint assignments. Youmay need to define an ASCII/EBCDIC codepoint entryduring start-up for GAIJI codepoints or for codepointsnot built in to the system.

AZK2303I UNEVEN BYTES IN PURE DBCSSTRING - byte FOUND INTRAILING POSITION -DISCARDED

Explanation

The NLS service routine was invoked for conversion ofEBCDIC pure DBCS data. An uneven number of byteswere present in the input stream.

User response

Handling of the current DBCS conversion is completedby skipping the trailing, unmatched single byte.

AZK2304I NO TRAILING SHIFT-INDELIMITER BEFORE END OF DBCSSTRING - ASSUME SHIFT-IN WASPRESENT

Explanation

The NLS service routine was invoked for conversion ofEBCDIC mixed SBCS/DBCS string. While processingDBCS characters, the input stream was exhaustedbefore a shift-in character was found. DBCSsequences should always be terminated by a trailingshift-in byte.

User response

Handling of the current DBCS conversion is completedby assuming that a shift-in character was present.

AZK2305I INVALID ENCODING PARAMETER(parmname) DETECTED IN NLS E-TO-A ENCODING ROUTINE

Explanation

The NLS service routine was invoked for conversion ofEBCDIC to ASCII. The encoding parameter is invalid.

User response

The server assumes ISO-8859-1 SBCS EBCDIC toASCII conversion.

AZK2306I DESTRUCTIVE OVERLAPDETECTED IN SBCS E-TO-A OR A-TO-EENCODING ROUTINE

Explanation

The NLS service routine was invoked for EBCDIC toASCII or ASCII to EBCDIC encoding of SBCS data.Overlap of the input and output areas was detected.The encoding request is aborted by deliberategeneration of an S0C3 abend.

User response

This is probably a logic error. Contact SoftwareSupport.

AZK2307I NO NLS TABLE FOUND FOR ASCII/EBCDIC MAPPING CODE tblname

Explanation

The NLS service routine was invoked to look up an NLSEBCDIC to ASCII or ASCII TO EBCDIC translation table(tblname). The requested table was not found.

User response

Ensure that valid values are set for the serverASCIIEBCDICMAPPING and CHARACTERENCODINGparameters. Check for other messages which indicatewhether a non-default setting was selected duringprocessing of the current transaction. Also, check theISPF 5.19 display for a list of coded character sets thatare defined to the system. The server will continue theoperation using the built-in ENUASCIIEBCDICMAPPING table for SBCS operations andwill set the CHARACTERENCODING to ISO-8859-1.

AZK2308I NO BUILT-IN NLS TABLE FOUNDFOR scheme (tblname)

Explanation

The NLS service routine was invoked to encode ordecode data which contains a multi-byte character setalgorithm. A built-in NLS character set conversiontable was not present.

scheme represents the character encoding scheme

User response

The encode/decode operation is aborted by deliberategeneration of an S0C3 abend. Check for reasons whythe built-in table described in the message isundefined to the system.

AZK2309I UNPAIRED scheme DBCS LEAD-BYTE byte SKIPPED BY DECODER

Explanation

The NLS service routine was invoked to decode datawhich contains a multi-byte character set algorithm. A


single byte was found which should be the first byte ofa two-byte DBCS character sequence; however, nomore input bytes were present.

scheme represents the character encoding scheme

User response

The decode routine skips the invalid DBCS lead-byteand omits it from the EBCDIC result.

AZK2310I UNSUPPORTED ESCAPESEQUENCE seq FOR meth

Explanation

The NLS service routine was invoked to decode datawhich contains multi-byte character sets includingescape sequences. The escape sequence (seq)reported in the message is not supported by theserver.

meth represents the character encoding method

User response

The decode routine copies the escape sequence andconverts it to SBCS EBCDIC.

AZK2311I UTF-8 ind NOT SUPPORTED FORNLS page - ASSUMING HOST CODEPAGE IS "ENU"

Explanation

The NLS service routine was invoked to decode orencode a UTF-8 data stream. The server does notsupport UTF-8 data streams for the selected EBCDIChost code page (page).

ind indicates either "decoding" or "encoding"

User response

The routine assumes the EBCDIC host code page is setto ENU (IBM-1047). This may lead to incorrect resultswhen the input or output stream has been processed.

AZK2312I BYTE byte IS AN INVALID UTF-8BYTE - SKIPPING TO NEXT BYTEOF STREAM

Explanation

The NLS service routine was invoked to decode aUTF-8 data stream. An invalid lead-byte value hasbeen found in the UTF-8 stream (x80-xBF, or xF8-xFF).The decoder will skip over the offending byte andATTEMPT to re-orient at the next input byte position.

User response

The decode operation continues at the next inputstream position. This may lead to additional errors orincorrect decoding of the stream.

AZK2320T DBCS conversion bypassed forparameter parmno: rsn

Explanation

The DBCS Dynamic Conversion Service bypassedconversion of the specified parameter to graphic forthe reason listed. The operation will be passed on toDb2 which will most likely issue an SQLCODE = -301error.

User response

This is a programming error in the client application.

AZK2401E db2ID conntype func ERROR,RC=rcode REASON=rsncode

Explanation

Db2 Streams Collector received an unexpected failurereturn code from a CAF or RRSAF function

User response

Refer to the Db2 Messages and Codes for furtherdetails on the error. Message 2402 may be issued aswell.

AZK2402E db2ID : msgtext

Explanation

Db2 Streams Collector received an unexpected failurereturn code from a CAF or RRSAF function

User response

Refer to the Db2 Messages and codes for furtherdetails on the messages.

AZK2403E conntype module mismatch forDB2 subsystem db2ID

Explanation

Db2 Streams Collector received a return code 4 andreason code 00C10823 attempting to create a CAF orRRSAF connection to the specified Db2.

User response

Change the STEPLIB used by the product to point tothe highest level version of Db2


AZK2404E User ID userID does not haveauthority to access DB2 db2ID

Explanation

Db2 Streams Collector received a return code 8 andreason code 00F30013 attempting to create a CAF orRRSAF connection to the specified Db2.

User response

Correct the DEFINE PUBLISH statement to specify auserid authorized to access the particular Db2.

AZK2405E DB2 system db2ID not defined

Explanation

Db2 Streams Collector received a return code 8 andreason code 00F30006 attempting to create a CAF orRRSAF connection to the specified Db2.

User response

Correct the DEFINE PUBLISH statement

AZK2406T db2ID conntype ISSUED, RC=rcodeREASON=rsncode

Explanation

Trace Streams Db2 CAF and RRSAF return codes

User response

None

AZK2407T PUBLISH SOURCE db2ID USERIDuserID LOGON FAILED rcode1rcode2 rsncode

Explanation

The PUBLISH USERID specified could not be loggedon. This message should be followed by anothermessage with the SAF error message.

The message has two return codes; rcode1 representsthe security module return code, and rcode2represents the RACF (SAF) return code.

User response

The Streams routine is aborted. Ensure that the useridspecified is correct.

AZK2408E Streams plan plan not defined TOdb2ID

Explanation

Return code 8 Reason code 00F30040 receivedattempting to open the specified plan.

User response

The Streams source task is aborted. Ensure that thespecified plan is bound.

AZK2409I srctype %2 Streams source tasknow starting

Explanation

The DEFINE PUBLISH TYPE(DB2) task is starting.

User response

This message is for informational purposes only.

AZK2410I Streams destination task fordestination starting

Explanation

DEFINE PUBLISH DESTINATION task starting

User response

None

AZK2411W PUBLISH - service OF desc FAILED,RC=rcode

Explanation

The product tried to initialize or a Publish task duringproduct initialization or termination. An internalservice routine called during Publish task initializationor termination exited with a non-zero return code.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current Publish task initialization or terminationproblem. Also, check for storage allocation errors orabends. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact Software Supportto obtain additional assistance.

AZK2412I Streams tasktype task fordestination terminating

Explanation

DEFINE PUBLISH task terminating


User response

None

AZK2413T data1 data2 data3 data4 data5data6 data7 data8 data9 %SK

Explanation

This message emits information related to the TraceStreams Db2 routines.

User response

None

AZK2414W UNABLE TO FIND DATASET NAMEFOR DDNAME ddname

Explanation

Streams destination is unable to access the Datasetname for the listed DD name, which contains XMLformatting information.

User response

None

AZK2415E CANNOT SERIALIZE ON db2IDQUALIFIER qualifier

Explanation

It appears that another copy of the product is usingthe same Event Publisher Db2 tables that this copy ofthe product is attempting to use.

User response


AZK2416S Streams support not configured -it cannot be initialized

Explanation

None.

User response


AZK2417E Invalid return from Streams rulerulename rval

Explanation

An SEF rule (rulename) for a Streams event provided asyntactically invalid return value (rval). The event wasnot Published.

User response

Correct the SEF rule and retry.

AZK2418T PUBLISH ITEM keyfield FORSOURCE srcID - errtext -STATUS=scode RC=rcodeREASON=rsncode DIAG=diaginfo-FAILED

Explanation

Error attempting to Publish an update for theparticular item.

User response

Attempt to correct the error

AZK2419T PUBLISH DESTINATION destFAILURE errtext - STATUS=scodeRC=rcode REASON=rsncodeDIAG=diaginfo - WILL RETRY

Explanation

Error attempting to Publish an update for theparticular item.

User response

Attempt to correct the error

AZK2420E DB2 db2ID CONTENTION ON tableCODE -sqlcode - WILL RETRYLATER

Explanation

Timeout detected trying to access one of the Streamstables.

User response

None - the Streams will retry the request

AZK2421E DUPLICATE PUBLISH OF pkgdest(HTX) TO destination IGNORED

Explanation

An Streams rule tried to ship the same update morethan once to a particular destination (pkgdest). Onlythe first instance was published.

User response

Correct the SEF rule.

AZK2422E MACHINE machID (index) ISUSING UNKNOWN PROTOCOLprotocol


Explanation

A saved ODBC generated destination is requesting anunsupported protocol. The destination is ignored.

User response


AZK2423E MACHINE machID (index) DOESNOT HAVE A SAVED URL

Explanation

A saved ODBC generated TCPIP destination does nothave a saved URL.

User response

Have the client process reissue theENABLETRANSMISSIONS ODBC call. If the problemcannot be resolved, contact Software Support.

AZK2424E MACHINE machID (index) INVALIDURL errcode - detailed

Explanation

A saved ODBC generated TCPIP destination have aninvalid saved URL.

User response

Have the client process reissue theENABLETRANSMISSIONS ODBC call. If problempersists contact Software Support.

AZK2425E WORKTABLE UPDATE FOR keyfielddestination FAILED - ROW NOLONGER EXISTS

Explanation

A deferred status for the publication of a particularitem could not be reflected into the worktable becausethe row describing the item no longer exists.

User response

Ignore if the row was deleted while the status wasoutstanding. If problem persists contact SoftwareSupport to obtain additional assistance.

AZK2426E MACHINE machID (index) DOESNOT HAVE A SAVED MQ NAME

Explanation

A saved ODBC generated MQSeries destination doesnot have a saved target MQ name.

User response

Have the client process reissue theENABLETRANSMISSIONS ODBC call. If problempersists contact Software Support to obtain additionalassistance.

AZK2427E Task task not started - notlicensed for feature.

Explanation

None.

User response


AZK2428E task SOURCE TASK PARAMETERMQREPLYQNAME mqreplyqnameIGNORED - NOT LICENSED FORUSE

Explanation

None.

User response


AZK2429E NON-REPORT MQ MESSAGERECEIVED ON mqreplyqname(start) - IGNORED

Explanation

An MQSeries message other than a status report wasreceived on the MQREPLYQNAME.

start represents the start of the text

User response

Ensure that the MQREPLYQNAME MQSeries Q is notused for anything other than Streams as anMQREPLYQNAME.

AZK2430E source MQSERIES MQ FAILURE ONmqreplyqname RC=rcodeREASON=rsncode - errdesc

Explanation

An unexpected MQSeries failure occurred whenattempting to record report messages to the WorkFile.

User response

Ensure that the MQREPLYQNAME was properlydefined in the MQSeries catalog.

AZK2431I jobname Streams exit exit enabled


Explanation

The Streams CICS Global User Exit has been enabledduring CICS PLTPI phase three initialization.

User response


AZK2432E UNRECOGNIZED MQ REPORTMESSAGE RECEIVED ONmqreplyqname (corrID)

Explanation

An MQSeries report message had an unrecognizedcorrelation ID value (corrID).

User response

Ensure that the MQREPLYQNAME MQSeries Q is notused for anything other than Streams as anMQREPLYQNAME.

AZK2433E EVENT DEFINITION BUILD FAILEDFOR source event datamap

Explanation

Streams source task initialization failed whileattempting to build an event definition from the a datamap.

User response

Ensure that the data map used in the event definitionis correct and matches the layout of the data to becaptured. in the case of an IMS/DB map, make surethat a COBOL map that defines the data fields hasbeen successfully merged.

AZK2434W tskname tsktype DB2 EVENTTABLE ROWNUM percent FULL

Explanation

The specified publish task EVENT table,DTRIGGERTABLE, column name ROWNUM has a valuethat is nearing the end of its available range. It mustbe reset before it runs out of available numbers in itsrange. The range is 1 to 2147483647. The percentspecified in the message shows how much of thatrange has been used.

User response

Quiesce the source task or stop the product and DROPand CREATE the proper TRIGGERTABLE.

AZK2436S jobname error inquiring CICSsystem information for Streams -EIBRESP: respcode

Explanation

The Streams PLTPI program encountered an errorinquiring CICS system information.

User response

Probable CICS error. Check the system log for errors.

AZK2437S jobname error enabling Streamsexit program program for exit exit -EIBRESP: respcode

Explanation

The Streams PLTPI program encountered an errorenabling a Streams exit program.

User response

Check that the exit program has been correctly definedto CICS.

AZK2438S jobname error extracting GWAaddress for Streams programprogram - EIBRESP: respcode

Explanation

The Streams PLTPI program encountered an errorextracting the Global Work Area address for the exitprogram.

User response


AZK2439I VSAM capture not enabled,already being processed bysubsystem subsys

Explanation

VSAM capture is already being processed by anotherproduct subsystem. Only one product subsystem isallowed to capture VSAM events.

User response

Informational.

AZK2440I VSAM event capture enabled

Explanation

VSAM event capture has been enabled by this productsubsystem.


User response

Informational.

AZK2441E Error in enabling VSAM eventcapture, RC=rcode

Explanation

An error was encountered while enabling VSAM eventcapture.

User response


AZK2443T VSAM caller is in key callers andonly key 8 callers are supported,VSAM capture terminated.

Explanation

Only key 8 programs are supported for VSAM capture.

User response


AZK2444E VSAM capture prefix not set, VSAMcapture not enabled

Explanation

A capture prefix (PUBLISHVSAMPREFIX) must bespecified to capture VSAM events.

User response


AZK2445S jobname error operation Streamsexit program program - EIBRESP:respcode

Explanation

The Streams PLT program encountered an errorstarting or stopping the user exit program.

operation indicates "STARTING" or "STOPPING"

User response


AZK2446I jobname enabling Streams exitprogram program for exit exit

Explanation

The Streams PLTPI program is about to enable the exitprogram.

User response


AZK2447I jobname operation Streams exitprogram program

Explanation

The Streams PLT program is about to start or stop theexit program.

operation indicates "STARTING" or "STOPPING"

User response


AZK2448I jobname Streams exit programprogram operation

Explanation

The Streams global user exit program has been startedor stopped.

operation indicates "STARTED" or "STOPPED"

User response


AZK2449I Unable to create capture file file,RC = rcode1, REC = rsncode, SSIRC= rcode2

Explanation

An error occurred trying to create the VSAM capturefile.

The message contains two return codes; rcode1represents the catalog management return code, andrcode2 represents the SMS SSI call return code.

User response

Return and reason codes can be found in msgIDC3009I

AZK2450I Unable to allocate capture file file,RC = rcode, REC = rsncode

Explanation

An error occurred trying to allocate the VSAM capturefile.

User response

return and reason codes can found in "AuthorizedAssembler Services Guide"


AZK2451I Unable to open capture file file, RC= rcode

Explanation

An error occurred trying to open the VSAM capture file.

User response

return code documented in "Macro Instr for Data Sets"

AZK2452I Capture file file is not SMSmanaged, but SMS is required forthe capture file

Explanation

The capture file is non-sms, but SMS management isrequired for the capture file.

User response

Alter SMS ACS rules as required to SMS manage thedata set.

AZK2453S Streams work file not allocated -Streams source task terminated

Explanation

The Streams global user exit is about to write an eventrecord to the event file.

User response

Check that the file has been correctly allocated anddefined to CICS.

The variable fields of the message text are: StreamsCICS Source name

AZK2454E tskname tsktype TASK NOTSTARTED - MQSERIES NOTACTIVE

Explanation

The specified publish task could not be startedbecause MQSeries is not active.

User response

Ensure that MQSeries is active on the system and thatthe Streams initialization exec sets the MQACTIVEparameter to YES.

AZK2455E tskname tsktype filetype FILE,NAME filename VERSIONMISMATCH, EXPECTED verno1,FOUND verno2

Explanation

The specified publish task could not be startedbecause the file contained data with a version numberthat is not supported by this release.

The message contains two version numbers, verno1and verno2, which represent the expected versionnumber and found version number respectively

User response

Ensure that the proper EVENT or WORK or Db2 file isused with Streams. Most likely, a different version wasused to create the indicated file.

AZK2456W tskname tsktype WORK FILE,DDNAME ddname percent FULL

Explanation

The specified publish task WORK file has records thatuse the specified percent of available space. It ispossible that remaining space is lower than indicatedby this message.

User response

Ensure that the WORK file has sufficient free space tocontinue normal operation.

AZK2457E tskname tsktype WORK FILE,DSNAME dsname COMPLETELYFULL

Explanation

The specified publish task WORK file has beencompletely filled up with records, and VSAM hasrefused to write additional records. The Publish Sourcetask has stopped.

User response

Make more space available to the WORK file. Ifadditional extents may be allocated to the WORK file,make more space available on the volume(s) theWORK file is on.

AZK2458E SOURCE NAME tskname NOTACTIVE OR NOT FOUND

Explanation

No active publish source task with the specified namehas been found. The requested action was notcompleted.

User response

Enter an active source task name in the request.


AZK2459E UNICODE CONVERSION fortblname FROM source TO targetNOT SUPPORTED

Explanation

Unicode conversion services on this system are notconfigured to support the data conversion required bya Streams definition.

User response

Reconfigure z/OS Unicode conversions services tosupport codepage conversions between the listedCCSIDs (source and target).

AZK2460E THE ZEVRAW SPECIFICATION ONEVENT DEFINITION src defREQUIRES THE RAW DATAOPTION

Explanation

The event definition requested ZEVRAW formatting.This require that either the raw data option beselected, or a rule is specified on the source (src) orevent definition (def).

User response

Edit the source or the event definition to specify a rulefor event routing, or select the raw data option on theevent definition.

AZK2461S Error loading Streams program -program

Explanation

The Streams PLT program encountered an error tryingto load the named program.

User response

Check that the program has been correctly defined toCICS. Sample CICS definitions are distributed in theCNTL library CICSCSD member.

The variable fields of the message text are: programname

AZK2462E EVENT DATA TOO LONG FORsource event datamap

Explanation

Streams source task initialization failed whileattempting to build an event definition (event) from thea data map.

User response

Ensure that the data map used in the event definitionis correct and matches the layout of the data to becaptured. in the case of an IMS/DB map, make surethat a COBOL map that defines the data fields hasbeen successfully merged.

AZK2463E DATA CAPTURE CHANGES NOTDEFINED FOR event tblqualtblname

Explanation

Streams source task initialization failed whileattempting to build an event definition (event) for aDb2 table.

User response

Ensure that the table referred by the event definitionhas the DATACAPTURE attribute on.

AZK2464E MONITOR2 and TRACE Authorityare required for user ID userID.

Explanation

Streams Db2 IFI source task user ID requires Db2SYSOPR authority to issue a START MONITOR TRACEcommand.

User response

Ensure that the user ID specified in the Db2 IFI sourcedefinition has been granted SYSOPR authority.

AZK2465I Streams native VSAM capture notenabled

Explanation

VSAM event capture has not been enabled by thisproduct subsystem.

User response

Informational.

AZK2466W tskname tsktype WORK FILE,DDNAME ddname EXTENDED,NOW percent FULL

Explanation

The specified publish task WORK file has records thatuse the specified percent of available space. Thepercent used has decreased, indicating that thedataset has been extended.


User response

Ensure that the volume containing the WORK file hassufficient free space to allow any additional extensionof the WORK file needed to continue normal operation.

AZK2467E MORE THAN ONE EVENT TABLECANNOT BE ACTIVE FOR SOURCEtskname. ALL ACTIVE EVENTTABLES FOLLOW.

Explanation

A Streams source task has more than one Event Tablemarked active. Only one Event Table may be markedactive at any time. A list of active Event Tables follows.

User response

Ensure that only one Event Table is marked active.

AZK2468E Streams source tskname, eventtable table in map map markedactive.

Explanation

The specified publish source task has this Event Tablemarked active. Only one Event Table may be markedactive at any one time.

User response

Ensure that only one Event Table is marked active.

AZK2469E Streams source tskname, eventtable table in map map, cannotfind map map.

Explanation

The specified Event Table for this source references amap that cannot be found, or is not active, or notenabled for event publishing.

User response

Ensure that the Event Table references active maps,and that each is enabled for event publishing.

AZK2470S Streams IMS source task srcnamenot activated - RRS not enabled

Explanation

The Streams global IMS source task (srcname) couldnot be activated because RRS was not enabled for thisStreams server.

User response

Change the server initialization parameters to specifyRRS(YES) and restart the server.

AZK2471S Streams IMS source task srcnamenot activated - EVENTQ notdefined

Explanation

The Streams IMS source task (srcname) could not beactivated because the required MQSeries eventrepository was not correctly defined.

User response

Correct the DEFINE SEM_ENDPOINT specification forZEV.EVENTQ in the server initialization parameters andrestart the server.

AZK2472I routine Capture successful/failedrcode rsncode

Explanation

Generic debugging message issued by Streamscapture processes (routine). The presence of theSDPHDBUG load module in the capture process loadlibrary will cause these debug messages to be issued.To create SDPHDBUG, edit member ZEVDBUG fromthe product sample library to set desired debug traceoptions and assemble and link as SDPHDBUG.

User response

Remove member SDPHDBUG to prevent thesemessages.

AZK2473I routine text1 text2 text3 text4

Explanation

This message tracks the generic debugging messageissued by Streams capture process (routine)initialization. The presence of the SDPHDBUG loadmodule in the capture process load library will causethese debug messages to be issued. To createSDPHDBUG, edit member ZEVDBUG from the productsample library to set desired debug trace options andassemble and link as SDPHDBUG.

User response




Explanation

This message tracks the generic debugging messageissued by Streams event capture (routine). Thepresence of the SDPHDBUG load module in thecapture process load library will cause these debugmessages to be issued. To create SDPHDBUG, editmember ZEVDBUG from the product sample library toset desired debug trace options and assemble and linkas SDPHDBUG.

User response


AZK2475I routine Blocksize:maxsizeBlocklen:length Blockid:blkID

Explanation

Logstream debugging message issued by Streamsevent capture (routine). The presence of theSDPHDBUG load module in the capture process loadlibrary will cause these debug messages to be issued.To create SDPHDBUG, edit member ZEVDBUG fromthe product sample library to set desired debug traceoptions and assemble and link as SDPHDBUG.

User response


AZK2476I routine Streamtoken: token

Explanation

Logstream debugging message issued by Streamsevent capture (routine). The presence of theSDPHDBUG load module in the capture process loadlibrary will cause these debug messages to be issued.To create SDPHDBUG, edit member ZEVDBUG fromthe product sample library to set desired debug traceoptions and assemble and link as SDPHDBUG.

User response



Explanation

This message tracks the generic debugging messageissued by Streams event capture (routine). Thepresence of the SDPHDBUG load module in thecapture process load library will cause these debugmessages to be issued. To create SDPHDBUG, editmember ZEVDBUG from the product sample library to

set desired debug trace options and assemble and linkas SDPHDBUG.

User response


AZK2478E tskname tsktype TASK NOTSTARTED - STRNO val TOO SMALL

Explanation

The specified publish task could not be startedbecause there were not enough VSAM stringsallocated at startup.

User response

Ensure that the PUBLISHSTRNO value is one largerthan the number of Streams SOURCE tasks.

AZK2479S jobname ERROR OBTAININGCONTAINER DATA FOR container -EIBRESP: respcode

Explanation

The Streams CICS event processing adapterencountered an error getting data from a channelcontainer.

User response


AZK2480I Streams server version ver1 doesnot match DB2 function versionver2

Explanation

The Streams server that has been configured topublish Db2 events does not match the version of theStreams Db2 wake_publish function.

User response

Check that the correct version of the wake publishfunction load module (SDD2PCRU) is in the Db2RUNLIB, and check that the Streams server is at thesame level.

AZK2481I jobname Streams version verSFVXno date time

Explanation

Streams CICS load library maintenance levelinformation.


User response

None.

AZK2482T RENDEZVOUS CALL FAILED -RC=rcode1 REAS=rsncode -ENCLAVE RC=rcode2FEEDBACK=(fbcodes)

Explanation

An attempt to send a message to a Tibco Rendezvousdestination failed.

The message contains two return codes; rcode1represents the rendezvous interface return code, andrcode2 represents the LE/370 enclave manager returncode

User response

Check for other messages indicating the cause of thefailure, and resolve the problem, if possible.

AZK2483T Streams parmname parameter notspecified

Explanation

The file dataset name prefix was not specified. The filecannot be allocated.

User response

Check that the parameter is correctly specified in theserver initialization exec (xxxxIN00)

AZK2484T jobname Streams Name/Tokenoperation result for token

Explanation

The Streams capture process has attempted a name/token operation.

operation may indicate "CREATE", "RETRIEVE", or"DELETE"

token may indicate "SUCCEEDED" or "FAILED"

User response

None

AZK2485I Streams DB2 FUNCTION VERSIONver date time

Explanation

Streams Db2 exit maintenance level information

date and time indicate time and date of assemble

User response

None.

AZK2486I Streams source improper versionver found ver

Explanation

Streams found a record with an improper version in it.

User response

The improper record will be deleted.

AZK2487T PUBLISH LOGON FAILED - errmsg

Explanation

The PUBLISH LOGON failed for the following reason.

User response

The Streams routine is aborted. Ensure that the useridspecified is correct.

AZK2488R REPLY 'GO' TO CONTINUE, OR'CANCEL' TO TERMINATE StreamsInitialization

Explanation

This message is issued when there was a failedattempt to load the IMS data capture user exitspecified with the PUBLISHIMSUEX1 parameter.Check that the correct exit program name has beenspecified and that the program has been copied to theStreams server load library. if more than two minutesexpire while waiting for your reply or three invalidreplies are made, the default action of CANCEL will betaken.

User response

Reply GO to continue Streams server initializationReply CANCEL to terminate Streams serverinitialization

AZK2489E Invalid Streams initializationreply: reply

Explanation

An invalid reply was specified to the Streamsinitialization console message. The message causingthe error will be reissued so that you can correctlyreply. After three invalid replies for the same message,default action will be taken. For a description of thedefault action, see the explanation of the originalmessage.


User response

Determine the proper reply from the text of themessage, and reply correctly.

AZK2490E Streams reply wait exceeded 2minutes. Default used

Explanation

The product waited over two minutes for a reply to theStreams initialization message. Since no response wasduring that time, default action was taken.

User response


AZK2491E 3 Invalid Streams replies. Defaulttaken

Explanation

Three invalid replies were made to a Streamsinitialization message. Since no correct response wasreceived, default action was taken.

User response


AZK2492I Streams not active on this server

Explanation

An attempt was made to access the Streams controltask and it was not active.

User response

If the server is intended as a Streams server, check theIN00 initialization parameters for the server.

AZK2493E Streams TASK task UNABLE TOoperation LOGSTREAM logstream,RC=rcode, RSN=rsncode

Explanation

A Streams task attempted an operation on an MVSlogstream and it was not successful.

User response

Determine the problem from the logstream functionreturn code and reason code, and correct the error.These codes are documented inSYS1.MACLIB(IXGCON) and in z/OS MVS AssemblerServices Reference in IXGxxxx macros return codes.

AZK2494W INVALID RECORD FOUND IN taskLOGSTREAM logstream, FOUNDSTATUS scode, TO dest. KEYtimestamp

Explanation

A Streams task found a record in its MVS logstreamwith an invalid status (scode) and destination (dest)name. The record is discarded.

User response

Check other Logstream activity to be sure data has notbeen corrupted with data from some other program.

AZK2495W TASK task LOG logstreamMISSING REPLY, STATUS scode,DEST. dest., KEY timestamp

Explanation

A Streams task received an MQSeries confirmationthat did not match the next record in the taskLogstream. The record is discarded.

User response

Check other MQSeries activity to be sure messages orresponses have not been inadvertently discarded.

AZK2496W TASK task LOG logstream RECORDWITH STATUS statcode, DEST.dest., KEY timestamp,CONFIRMATION ARRIVED,RECORD MISSING

Explanation

A Streams task received an MQSeries confirmationthat did not match the next record in the taskLogstream. The confirmation is discarded.

User response

Check other Logstream activity to be sure messageshave not been inadvertently discarded.

AZK2497W Logstream operation exp

Explanation

A Logstream operation received a return code. Thismessage tries to explain (exp) the return code andreason codes.

User response

Check other Logstream messages to determine theproblem.


AZK2498T Streams does not support TibcoRendezvous destinations

Explanation

Tibco Rendezvous destinations are not supported.

User response

Delete Tibco Rendezvous destinations.

AZK2499T Streams does not support Oracledestinations

Explanation

Oracle destinations are not supported.

User response

Delete Oracle destinations.

AZK2500T source COPYWORK time1 time2

Explanation

Streams trace record. An Event has been copied fromthe trigger table to the Work file.

The message contains two time variables; time1represents the time of the update, time2 representsthe time the record was copied

User response

None

AZK2501T source RUNRULES

Explanation

Streams trace record. The Event processor is runningSEF rules for records in the Work file.

User response

None

AZK2502T source DYNDEST keyfield machIDindex

Explanation

Streams trace record. An Event is being processed fora dynamic JCA 1.5 destination. The identifiers for theJCS 1.5 Adapter requestor are traced.

User response

None

AZK2503T dest SENDPLUP-RESTART

Explanation

Streams trace record. Processing for an Event sourceis being restarted to a destination (dest).

User response

None

AZK2504T source MQMARK

Explanation

Streams trace record. MQSeries processing for anEvent source is marking the current status of updaterecords.

User response

None

AZK2505T source SENDITEM dest keyfield

Explanation

Streams trace record. An Event is being queued forsending to a destination (dest).

User response

None

AZK2506T source DOPRUNE time count

Explanation

Streams trace record. Old Publish records (counted bycount) are being pruned from the Workfile.

User response

None

AZK2507T source WAITABIT caller secSECONDS

Explanation

Streams trace record. The Streams task is waiting formore work.

caller represents the calling subroutine

User response

None

AZK2508T source PREPROC dest keyfield urID


Explanation

Streams trace record. The Streams task ispreprocessing an update for transmission to adestination.

User response

None

AZK2509T source PREPROC **SKIP**keyfield

Explanation

This message documents the streams trace record.The Streams task preprocessor has determined thatan update should NOT be sent to any destination.

User response


AZK2510T source POSTPROC dest keyfieldrcode urID

Explanation

Streams trace record. The Streams task is doingpostprocessing for an update.

User response

None

AZK2520T ENABLETRANSMISSIONS destmachine

Explanation

Streams trace record. The Streams is enablingtransmissions to a dynamic destination for the JCA 1.5interface.

User response

None

AZK2521T DISABLETRANSMISSIONS destmachine

Explanation

Streams trace record. The Streams is disablingtransmissions to a dynamic destination for the JCA 1.5interface.

User response

None

AZK2530T ADDCOLUMN colname colval

Explanation

Streams trace record. The Streams JCA 1.5 Adapterinterface is adding a column of Publish data.

User response

None

AZK2531T ADDTOPIC topic

Explanation

Streams trace record. The Streams JCA 1.5 Adapterinterface is adding a topic for MQ Broker processing.

User response

None

AZK2540T srctsk capture EVENT CAPTUREdatatype operation mapname

Explanation

Streams trace record. The Streams capture process(capture) has captured an event. Data associated withthe event has been saved in a dataspace owned by theStreams server.

operation represents the change type

User response

None

AZK2541T srctsk capture EVENT BUILDdatatype operation mapname

Explanation

Streams trace record. The Streams capture process(capture) has built an event record in a dataspaceowned by the Streams server.


User response

None

AZK2542T srctsk capture EVENT POSTdatatype operation mapname

Explanation

Streams trace record. The Streams capture process(capture) has posted the source task in the Streamsserver.



User response

None

AZK2543T srctsk capture EVENT BACKOUTdatatype operation mapname

Explanation

Streams trace record. The Streams capture process(capture) has backed out the data saved for an event.The event is discarded.


User response

None

AZK2544W source CATALOG SEARCH ERROR,RC=rcode REASON=rsncodeID=modID TYPE=type,ENTRY=entry

Explanation

Streams is searching the catalog for Archive data setsusing the CSI Catalog Search Interface, andencountered an error. The entry is skipped.

source represents the source task name

User response

Examine the VSAM catalog for errors using thediagnostic information provided.

AZK2545E Invalid Streams service requestreceived

Explanation

Streams main task received an invalid service request.

User response


AZK2600T ABEND ccode RS=rsncodeOCCURRED AT modname+offset.FUNCTION CODE=funcode.

Explanation

An ABEND occurred while processing a SecurityOptimization Manager request.

User response

The routine signals an error to the caller andprocessing continues, when possible.

AZK2606E Security optimization processingis terminated

Explanation

Security Optimization processing was terminated dueto an internal processing error. The product continuesto operate without the Security Optimizer.

User response

If you want to execute with the Security Optimizer, youmust stop and restart the product.

AZK2607I Security server ENF signal 71 notavailable

Explanation

A request by Security Optimization to listen for eventnotification facility signal 71 (RACF user profilechanges) failed. The product continues to operatewithout notifications.

User response

Examine any other messages accompanying this one.If the security server you are using does not supportENF signal 71, check with the security server productvendor for more information. Otherwise, contactSoftware Support for assistance with this problem.

AZK2608W SOM RACF new password exit isnot installed

Explanation

Security Optimization Management (SOM) initializationwas unable to verify that the product's RACF newpassword exit, S_ICHPWX, is installed as part of theICHPWX01 load module.

User response

The product continues to run. This exit detectspassword changes that are made during logon toapplications other than the product. Users will still beable to use the old password in the product until theSOM cache entry expires. Password changes madeduring the product logon are recognized without thisexit, and SOM signals all other product servers thatthis user's password has changed.

AZK2620I Security optimizer entry for userID userID was expired.

Explanation

The request to expire the entry for a user ID in thesecurity optimization cache was successful.


User response


AZK2621I Security optimization is not active

Explanation

A request to expire a Security Optimization entry couldnot be processed because Security Optimization is notactive.

User response


AZK2622I User ID userID was not located bythe security optimizer.

Explanation

A request to expire a security optimizer entry could notbe processed because the user ID was not located.

User response


AZK2623I Security optimizer processingabended

Explanation

The Security Optimizer Manager ABENDed whileprocessing the expire request.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact Software Support with thisproblem.

AZK2700E Error bb-ccc ddd Processingrequest. Extra Information: eee

Explanation

An error has occurred with the z/OS Connect interface.The following information is provided:

• bb is a major error number, as follows:

– 01: Storage error– 02: I/P data error– 03: I/P vectors error– 04: I/P JSON parsing– 05: I/P JSON understanding– 06: Processing error

– 09: Miscellaneous error• ccc is a minor error number• ddd is an error description• Extra Information: eee provides extra

information, if available.

User response


AZK3000T recovery LEVEL lvl errdesc=abcodeREASON CODE=rsncodeTIME=time SEQ=seqno CPU=cpuIDASID=asid

Explanation

The product detected an abend error. The currentmessage provides some information about the abend.This message, along with other messages, shouldprovide a detailed description of the current abenderror.

recovery may indicate "ESTAE", "FRR", or "ARR"

rsn may also be the text "UNKNOWN"

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact Software Support for assistancewith this problem.

AZK3001S func errdesc, ABEND abcode ATmodname+offset

Explanation

The product ESTAE routine detected an abend in aroutine called by it. The message describes the abenderror. The product ESTAE routine will continue toattempt recovery from the original error.

User response


AZK3002T Data at PSW PSWdata


Explanation

The product detected an abend error. The currentmessage provides some information about the abend.This message, along with other messages, shouldprovide a detailed description of the current abenderror.

PSWdata contains the PSW address and PSW data

User response


AZK3005S ESTAE level lvl ESTAE func errorRC=rcode

Explanation

The product ESTAE routine tried to protect itself byissuing an ESTAE macro. The ESTAE failed with a non-zero return code.

AZK3006T PSW at time of error fPSW ILC ilcINTC intc

Explanation

The product ESTAE routine detected an abend error.There is no product specific recovery for this error. TheESTAE routine tries to document the abend error bydisplaying the failing PSW. This message is part of themini-dump used to describe the current abend error.

ilc represents an instruction length code

intc represents an interrupt code

User response

Check if any other error messages (other than themini-dump) were generated along with the errormessage above. If the combined error messages aresufficient to explain the problem, take whatevercorrective action is appropriate. Otherwise, contactSoftware Support with this problem.

AZK3007T Current routine name=modnameaddress=addr offset=offset

Explanation

The product ESTAE routine detected an abend error.There is no product specific recovery for this error. TheESTAE routine tries to document the abend error bydisplaying the failing PSW and registers. This message

is part of the mini-dump used to describe the currentabend error.

User response

Check if any other error messages (other than themini-dump) were generated along with the errormessage above. If the combined error messages aresufficient to explain the problem, take whatevercorrective action is appropriate. Otherwise, contactSoftware Support for assistance with this problem.

AZK3008T ind register

Explanation

The product ESTAE routine detected an abend error.There is no product specific recovery for this error. TheESTAE routine tries to document the abend error bydisplaying the failing PSW and register content(register). This message is part of the mini-dump usedto describe the current abend error.

ind indicates "AR/GR" or ""GR

User response

Check if any other error messages (other than themini-dump) were generated along with the errormessage above. If the combined error messages aresufficient to explain the problem, take whatevercorrective action is appropriate. If the problem cannotbe resolved, contact Software Support.

AZK3009T modname calltype modname+offset

Explanation

The product ESTAE routine detected an abend error.There is no product specific recovery for this error. TheESTAE routine tries to document the abend error bydisplaying the calling module sequence of the currentroutine. This message is part of the mini-dump used todescribe the current abend error.

User response

Check if any other error messages (other than themini-dump) were generated along with the errormessage above. If the combined error messages aresufficient to explain the problem, take whatevercorrective action is appropriate. Otherwise, contactSoftware Support for assistance with this problem.

AZK3010T Too many entries

Explanation

The product ESTAE routine detected an abend error.While producing the module call trace (message


3009T), the loop limit was reached. The productceases to issue calling module trace messages andproceeds to other processing.

User response

Check if any other error messages (other than themini-dump) were generated along with the errormessage above. If the combined error messages aresufficient to explain the problem, take whatevercorrective action is appropriate. If the problem cannotbe resolved, contact Software Support.

AZK3020S INVALID STRING ADDRESS addr1,DETECTED addr2

Explanation

A request to the tokenization routine passed an invalidstring address. The address in the parameter list wasless than or equal to zero.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact your local Software Support groupfor assistance with this problem.

AZK3021S INVALID STRING LENGTHmaxlgth, DETECTED addr

Explanation

A request to the tokenization routine passed a stringlength that exceeds the maximum string lengthallowed.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact your local product systemsprogramming group for help with this problem.

AZK3022S TOKENIZATION LOGIC ERROR,DETECTED addr

Explanation

The tokenization routine detected a logic error duringprocessing of the current request.

User response

Check if any other error messages were generatedalong with the error message above. If the combined

error messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact your local product systemsprogramming group for help with this problem.

AZK3030E servrout errdesc FAILED,RC=rcode, DETECTED AT addr

Explanation

Some type of error occurred in one of the productcommon subroutines. See the actual text of themessage for an explanation. The error was probablycaused by a failure in an operating system servicerequested by the subroutine.

User response


AZK3031E ABEND abcode IN servrout,REASON CODE=rsncode, CALLEDBY cs

Explanation

An abend was detected in one of the product commonsubroutines. The abend code and service routine aredescribed in the message text. The error was probablycaused by a failure in an operating system servicerequested by the subroutine.

User response


AZK3032T INVALID INPUT COMMUNICATIONBUFFER PREFIX READ - blksize

Explanation

An invalid buffer prefix was read in from a clientapplication. The buffer prefix was either negative orexceeded the maximum input buffer size.

User response

The connection to the client system is terminated. Theclient application will probably report an error. Check


for any client system error messages. If the failurecontinues, contact Software Support.

AZK3033T DATASPACE CREATED,NAME=dspname, CALLED BY cs

Explanation

An MVS dataspace was created for temporary storageof data. The space name (dspname) is displayed.

User response


AZK3034T DATASPACE DELETED,NAME=dspname, CALLED BY cs

Explanation

An MVS dataspace was deleted. The space token isdisplayed.

User response


AZK3035T DATASPACE EXTENDED,NAME=dspname, CALLED BY cs

Explanation

An MVS dataspace was extended. The storage in thedataspace was used up and more was allocated to it.The space token is displayed.

User response


AZK3036T DATASPACE RELEASED,NAME=dspname, CALLED BY cs

Explanation

Storage in an MVS dataspace was released. Thestorage is no longer required. The space token isdisplayed.

User response


AZK3037T DATASPACE func FAILED,NAME=dspname, RETURNCODE=rcode, REASON CODE =rsncode,CALLED BY cs

Explanation

A dataspace function failed. The return code andreason code are displayed. The space token isdisplayed.

User response

Installation limits may have caused the failure.Examine the limits set by the installation's IEFUSI exitto determine if they caused the failure. If the problemcannot be resolved, contact Software Support.

AZK3038T ALET CREATED, NAME=dspname,ALET=alet, CALLED BY cs

Explanation

An ALET was created for accessing a dataspace. Thespace token is displayed. The resulting ALET isdisplayed.

User response


AZK3039T ALET DELETED, NAME=dspname,ALET=alet, CALLED BY cs

Explanation

An ALET for accessing a dataspace was deleted. Thespace token is displayed. The deleted ALET isdisplayed.

User response


AZK3040T ALESERV func FAILED,NAME=dspname, RETURNCODE=rcode, REASON CODE =rsncode,CALLED BY cs

Explanation

An ALESERV function failed. The return code andreason code are displayed. The space token isdisplayed.

User response

Installation limits may have caused the failure.Examine the limits set by the installation's IEFUSI exitto determine if they caused the failure. If the problemcannot be resolved, contact Software Support.

AZK3041T ABEND abcode IN servrout,REASON CODE=rsncode,NAME=dspname, ALET=alet,CALLED BY cs


Explanation

An abend was detected while manipulating adataspace. The abend code and service routine aredescribed in the message text. The error was probablycaused by a failure in an operating system servicerequested by the subroutine. The space token isdisplayed. The ALET, if any, is displayed.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate. If theproblem cannot be resolved, contact SoftwareSupport. In certain recovery situations, this messagemay be ignored.

AZK3042S Module modname is notAMODE(31)

Explanation

A module that had to load in AMODE(31) loaded withAMODE(24) or AMODE(64) instead. This is a seriouserror. Many modules, including RPCs and user recordexits, are only allowed to be AMODE(31).

User response

Relink the module (other changes may be needed)using AMODE(31). Run the application again.

AZK3043S MODULE modname LOAD FAILED,ABEND=abcode, REASONCODE=rsncode

Explanation

A module could not be loaded. The load failed with anabend error.

User response

Check the error messages and the reason codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and restart the product. If the problemcannot be resolved, contact Software Support.

AZK3044S MODULE modname DELETEFAILED, RETURN CODE=rcode

Explanation

A module could not be deleted. The delete failed witha non-zero return code.

User response

Check the error messages and the reason codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and restart the product. If the problemcannot be resolved, contact Software Support.

AZK3060S INVALID PC FUNCTION CODEfuncode, DETECTED AT addr

Explanation

The product space switch PC routine has been invokedwith an invalid function code (funcode). This may becaused by specifying an incorrect product subsystemID on a request when there are multiple copies of theproduct in the system at different release levels.

User response

Verify that the request that resulted in the productspace switch PC routine being invoked is being issuedto the correct product subsystem. If the problemcannot be resolved, contact Software Support.

AZK3061E service ABEND abcode ATmodname+offset

Explanation

An abend failure occurred in the product space switchPC routine. The error message provides the abendcode and abend location. This failure was probablycaused by a programming error in the calling routine orin the space switch PC routine. This failure can also becaused by product installation and maintenanceerrors.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact Software Support to obtainadditional assistance.


Explanation



User response


AZK3063E plist action FAILED, DETECTED ATaddr

Explanation

The space switch PC routine is attempting to copy(action) a parameter list (plist) passed by its caller intostorage that can be accessed in space switch modeand has found that the target storage area is not largeenough.

User response

This is an internal product error condition. ContactSoftware Support. Software Support.

AZK3070S func (funcode) SERVICE errdescccode rsncode errloc modname+offset creg15

Explanation

The product stacking PC function (func) has beeninvoked in an invalid manner, has been invoked in aninvalid environmental state, or has abended duringexecution.

creg15 represents control register 15, if avail, orzeroes

User response

Verify that the request that resulted in the stackingspace switch PC routine being invoked is being issuedto the correct product subsystem. If the problemcannot be resolved, contact Software Support.

AZK3071T func (funcode) SERVICE errdescccode rsncode errloc modname+offset creg15

Explanation

The product stacking PC function (func) has beeninvoked in an invalid manner, has been invoked in aninvalid environmental state, or has abended duringexecution. This is a duplicate of message 3070S but iswritten to the trace.

creg15 represents control register 15, if avail, orzeroes

User response

Verify that the request that resulted in the stackingspace switch PC routine being invoked is being issuedto the correct product subsystem. If the problemcannot be resolved, contact Software Support.

AZK3080E operation FAILED FOR userIDRC=rcode AT addr

Explanation

A logoff to the current server address space wasattempted by a user other than the one currentlylogged on. The current server address space isterminated, and a new one will be started.

User response

If problems are encountered with servers, the productcancels them and restarts them. This is normalproduct operation. Check if the current ABEND was anindependent one or if it was caused by the product,and resolve the problem accordingly.

AZK3081T TSO SERVER IN ASID asidtraceinfo1 traceinfo2 traceinfo3traceinfo4

Explanation

This is a trace message issued by the subsystem dataset read/write routine.

User response


AZK3082W OUTPUT LIMIT EXCEEDED (limitLINES) - CANCEL SELF WITH S722

Explanation

A TSO command running in a product TSO serveraddress space has exceeded the output line limit forserver commands as specified in theTSOSRVMAXLINES parameter.

User response

Modify the command to reduce the number of linesoutput, or increase the TSOSRVMAXOUTPUTLINESvalue. The TSO server will cancel itself with an S722completion code to abort processing of the currentcommand.

AZK3083S Command requested more input -command aborted


Explanation

The product Servers do not support commands thatrequest additional input in subcommand mode.

User response

Modify the command processor so that subcommandinput is not required.

AZK3084W service OF desc FAILED, RC=rcode

Explanation

This is a generic error message used to describe awide variety of errors detected by the product TSOSRVsubsystem interface read/write interface routine. Themessage text provides the current operation (service)and what the current operation was trying to do.

User response


AZK3085H jobname A=asid1 (asid2) TSOserver terminated by request

Explanation

A product Server address space has received a requestto terminate. This may occur at shutdown or when oneof the parameters governing the TSO servers (MIN orMAX values) has been modified.

The message contains two address space identifiers(asid1 and asid2), which are in decimal andhexadecimal respectively

User response


AZK3086H LOGON of userID to TSO serverfailed - RC=rcode1 (rcode2)Reason=rsncode

Explanation

A product TSO server address space was not able toLOGON the indicated client userid. The currentcommand is bypassed.

The message contains two return codes; rcode1represents the SAF interface return code, and rcode2represents the RACF return code

User response

Determine why the client userid logon failed, andresubmit the command.

AZK3087H Requestor has revoked commandrequest - cancel self with S622

Explanation

A product TSO server address space was not able tobind to the requesting task while attempting to returnthe results of a TSO command. The server abandonsthe request and terminates additional processing ofthe request by cancelling itself with a 622 completioncode.

User response

Determine why the requesting task abandoned therequest, and resubmit. The requesting task may havetimed out while waiting for a response to the request.

AZK3100S Invalid text insertion address -msgno addr modname+offset

Explanation

The product message formatting routine detected anerror in a data address passed to it. Because of theinvalid data address, a product message cannot besent. This means that some other error may haveoccurred, but the error message was not sent becauseof the current error. The invalid address is actually anscon. The offset is the location of the calling routinethat passed the invalid data.

User response


AZK3101S Message number msgno not found- modname+offset

Explanation

The product message formatting routine could not finda message number passed to it in the productmessage table. Because the message number couldnot be found, a product message cannot be sent. Thismeans that some other error may have occurred, butthe error message was not sent because of the currenterror. The error is caused by either a calling routinepassing an invalid message number or an error in themessage table. The offset is the location of the calling


routine that passed the message number that couldnot be found.

User response

Ensure that the product is properly installed. Checkthe message table assembly time, date, and versionnumber. Check if any other error messages weregenerated along with the error message above. If thecombined error messages are sufficient to explain theproblem, take whatever corrective action isappropriate. If the problem cannot be resolved,contact Software Support.

AZK3102S Invalid message text variable -msgno varname modname+offset

Explanation

The product message formatting routine could notprocess a substitution variable found in a messageskeleton. Because the substitution variable could notbe processed, a product message cannot be sent. Thismeans that some other error may have occurred, butthe error message was not sent because of the currenterror. The error is caused by a programming error inthe message table. The offset is the location of thecalling routine that invoked the message formattingroutine.

User response


AZK3103S Invalid text insertion data length -msgno modname+offset

Explanation

The product message formatting routine could notprocess the length part of a substitution variable ("%()") found in a message skeleton. Because thesubstitution variable could not be processed, aproduct message cannot be sent. This means thatsome other error may have occurred, but the errormessage was not sent because of the current error.The error is caused by a programming error in themessage table. The offset is the location of the callingroutine that invoked the message formatting routine.

User response

Ensure that the product is properly installed. Checkthe message table assembly time, date, and versionnumber. Check if any other error messages weregenerated along with the error message above. If thecombined error messages are sufficient to explain theproblem, take whatever corrective action isappropriate. Otherwise, contact Software Support forassistance with this problem.

AZK3104S Invalid text insertion data type -msgno modname+offset

Explanation

The product message formatting routine detected aninvalid data type value passed to it by a calling routine.Because of the invalid data type value, a productmessage cannot be sent. This means that some othererror may have occurred, but the error message wasnot sent because of the current error. The error iscaused by a programming error in the calling routine.The offset is the location of the calling routine thatpassed the invalid data type value.

User response


AZK3105S Output message buffer overflow -msgno modname+offset

Explanation

The product message formatting routine found thatthe current message will not fit in the output buffer.Because of the buffer overflow condition, a productmessage cannot be sent. This means that some othererror may have occurred, but the error message wasnot sent because of the current error. The error iscaused by either a programming error in the callingroutine or a message table error. The offset is thelocation of the calling routine that invoked themessage formatting routine.

User response

Ensure that the product is properly installed. Checkthe calling module assembly time, date, and versionnumber. Also check the message table assembly time,date, and version number. Check if any other errormessages were generated with the error message


above. If the combined error messages are sufficientto explain the problem, take whatever correctiveaction is appropriate. If the problem cannot beresolved, contact Software Support.

AZK3106S Invalid packed decimal for textinsertion - val modname+offset

Explanation

The product message formatting routine detected thatan invalid decimal data value (val) had been passed toit by a calling routine. Because of the invalid decimaldata value, a product message cannot be sent. Thismeans that some other error may have occurred, butthe error message was not sent because of the currenterror. The error is caused by a programming error inthe calling routine. The offset is the location of thecalling routine that invoked the message formattingroutine.

User response

Ensure that the product is properly installed. Checkthe calling module assembly time, date, and versionnumber. Check if any other error messages weregenerated with the error message above. If thecombined error messages are sufficient to explain theproblem, take whatever corrective action isappropriate. If the problem cannot be resolved,contact Software Support.

AZK3107S INVALID REPLY PARAMETER -modname+offset

Explanation

The product message formatting routine detected thata reply area had been passed to it for a message thatis not marked as a WTOR in the message table.Because of this logical inconsistency, a productmessage cannot be sent. This means that some othererror may have occurred, but the error message wasnot sent because of the current error. The error iscaused by either a programming error in the callingroutine or a message table error. The offset is thelocation of the calling routine that invoked themessage formatting routine.

User response

Ensure that the product is properly installed. Checkthe calling module assembly time, date, and versionnumber. Also check the message table assembly time,date, and version number. Check if any other errormessages were generated with the error messageabove. If the combined error messages are sufficientto explain the problem, take whatever corrective

action is appropriate. If the problem cannot beresolved, contact Software Support.

AZK3108S INVALID REPLY AREA LENGTH -length modname+offset

Explanation

The data value entered by a user was too long for thereply area passed by the calling routine. This error wasdetected by the message formatting routine. The erroris caused by a programming error in the callingroutine. The offset is the location of the calling routinethat invoked the message formatting routine.

User response

Ensure that the product is properly installed. Checkthe calling module assembly time, date, and versionnumber. Check if any other error messages weregenerated with the error message above. If thecombined error messages are sufficient to explain theproblem, take whatever corrective action isappropriate. If the problem cannot be resolved,contact Software Support.

AZK3109E INTERNAL ERROR DETECTED ATOPSNMG +offset, RC = rcode

Explanation

The message formatting routine detected a seriousinternal error. For example, a system service may havefailed with a non-zero return code, or an abend mayhave occurred. This means that some other error mayhave occurred, but the error message was not sentbecause of the current error. The error is caused byeither a programming error in the calling routine or amessage table error.

User response

Ensure that the product is properly installed. Checkthe calling module assembly time, date, and versionnumber. Also check the message table assembly time,date, and version number. Check if any other errormessages were generated with the error messageabove. If the combined error messages are sufficientto explain the problem, take whatever correctiveaction is appropriate. If the problem cannot beresolved, contact Software Support.

AZK3110I data1 data2 data3 data4 data5data6 data7 data8 data9 data10

Explanation

This message lists List Enable/Close/Force results.


User response


AZK3111I errdesc for dsname not found forcmd command.

Explanation

An error was encountered in processing a VSAM filecommand.

User response

Correct the command and reenter it.

AZK3119T data1 data2 data3 data4 data5data6 data7 data8 data9 %SK

Explanation

This message lists Trace Open/Close functions

User response


AZK3120S method service FAILED FORDDNAME=ddname,DSNAME=dsname

Explanation

An attempt to open (service) the specified data setfailed.

method may be QSAM, BSAM, or BPAM

User response

Try to determine why the attempt failed. If you areunable to determine the reason for the failure, contactSoftware Support.

AZK3121S RECORD SIZE size INVALID,LRECL=lrecl, BLKSIZE=blksize,DDNAME=ddname,DSNAME=dsname

Explanation

During a WRITE/PUT operation, the product I/Oroutines have been passed a record with an invalidrecord size. The record size is either 0 or greater thanthe maximum logical record size (LRECL) allowed forthe indicated data set.

User response

Attempt to determine the reason for the failure. If youare unable to determine the reason for the failure,contact Software Support for assistance.

AZK3122S VSAM service FAILED, RC=rcode,fldname FIELD=fldval,DDNAME=ddname,DSNAME=dsname

Explanation

A product generalized input/output processing routinetried to open a VSAM data set. The VSAM OPEN(service) failed.

fldname and fldval represent the ACB/RPL field nameand value respectively

User response

Review the error message text. Determine whatcaused the OPEN to fail, based on the return code.Review the current data set for any obvious errors.Correct the above problems, and restart.

AZK3123S UNSUPPORTED obj TYPE,DDNAME=ddname,DSNAME=dsname

Explanation

The product generalized I/O routine has been passed aDSORG or RECFM (obj) that is not supported.

User response

Validate that the data set specified has a supporteddata set organization (DSORG) or record format(RECFM). If you are unable to determine the reason forthe failure, contact Software Support.

AZK3124S SHOWCAT FAILED, RC=rcode,DDNAME=ddname,DSNAME=dsname

Explanation

A product generalized input/output processing routinetried to list the required message data from a data set,but the SHOWCAT operation failed with the abovereturn code.

User response

Review the error message text. Determine whatcaused the SHOWCAT operation to fail, based on thereturn code. Correct the above problems, and restart.For further assistance, contact your local productsystems programming group.

AZK3125S INVALID VSAM OBJECT (obj),DDNAME=ddname,DSNAME=dsname


Explanation

While processing a VSAM data set , a productgeneralized input/output processing routine found theobject (obj) to be invalid.

User response

Review the error message text. Validate the VSAMobject and analyze it for integrity. Review errors in thedefinition of the current data set. Ensure that the dataset was properly defined and that no other errors existwith it.

AZK3126E DYNAMIC ALLOCATION FAILED,RC=rcode, ERROR CODE=errcode,INFO CODE=rsncode,DDNAME=ddname,DSNAME=dsname

Explanation

An attempt to dynamically allocate a data set failed.The error message contains the informationassociated with the failed request.

User response

Review the information contained in the message, andattempt to correct the problem. Information on thecodes may be obtained from the IBM documentation.If, after reviewing this information, you are still unableto correct the problem, contact Software Support.

AZK3127S VSAM service FAILED, RC=rcode,DDNAME=ddname,DSNAME=dsname

Explanation

A product generalized input/output processing routinecould not display the check error message for thecurrent VSAM data set. The operation (service) failed.

User response

Review the error message text. Validate the VSAM dataset, and analyze it for integrity. Review errors with thedefinition of the current data set. Ensure that it wasproperly defined and that no other errors exist with it.


Explanation

This is a generic error message used to describe awide variety of I/O related errors. The message textgives a description of the current operation (service)and what the current operation was trying to do.

User response


AZK3129E service desc

Explanation

This is a generic error message used to describe awide variety of I/O related errors. The message textgives a description of the current operation (service)and what the current operation was trying to do.

User response


AZK3130E DYNAMIC ALLOCATIONCOMMAND ERROR. errmsg cmd

Explanation

The format of a dynamic allocation/de-allocationcommand (cmd) is invalid. The message containsinformation associated with the parameter(s) in error.

User response

Review the information contained in the message, andcorrect the command format.

AZK3131E DESERV GET_ALL FAILED:RC=rcode RSN=rsncode - ddname-index:dsname

Explanation

While issuing the DESERV macro to obtain directoryentry information, the system returned an unexpectedreturn code and reason code.

index represents the concatenation index where theerror occurred

User response


AZK3132E HFS service FAILED FOR path -RC=rcode (name1), RSN=rsncode(name2) - desc1 / desc2


Explanation

While invoking an Open Edition HFS Service for theentity identified by path, the system returned anunexpected return code and reason code.

name1 and desc1 refer to ERRNO names anddescriptions

name2 and desc2 refer to JERRNO names anddescriptions

User response

Review the appropriate Open Edition manual for themeaning of the return and reason codes. If the causeof the error cannot be readily determined, contactSoftware Support.

AZK3133E HFS service FAILED FOR path -errdesc additinfo

Explanation

While invoking an Open Edition HFS Service for theentity identified by path, the server interface detectedan error.

User response

If the cause of the error cannot be readily determinedfrom this and other messages, contact SoftwareSupport.

AZK3134I dsname Library directory empty(DDN=ddname)

Explanation

While attempting to read a PDS(E) dataset directory,the I/O services routines discovered that the PDS(E)directory is empty.

User response

An empty PDS(E) directory may be normal or mayrepresent a problem, depending on the library beingaccessed. If a problem results because the emptydirectory is an abnormality, this informationalmessage may aid in resolution.

AZK3135E DYNAMIC DEALLOCATIONFAILED, RC=rcode, ERRORCODE=errcode, INFOCODE=rsncode, DDNAME=ddname,DSNAME=dsname

Explanation

An attempt to dynamically free a data set failed. Theerror message contains the information associatedwith the failed request.

User response

Review the information contained in the message, andattempt to correct the problem. Information on thecodes may be obtained from the IBM documentation.If, after reviewing this information, you are still unableto correct the problem, contact Software Support.

AZK3136T User record exits cannot be loadedbecause DDNAME ddname is notallocated. Exits: program1 andprogram2

Explanation

An attempt to load a user record post-read (program1)and/or pre-write (program2) exit routine failedbecause the AZKRPCLB DD statement is not allocated.User record exit routines must reside in the in theS__RPCLB library.

User response

Modify the product server started task JCL to includethe AZKRPCLB DD statement.

AZK3137S Load for user record exit programprogram failed

Explanation

An attempt to load a user record post-read and/or pre-write exit program failed.

User response

The user record post-read and pre-write programsmust reside in a library allocated to the productAZKRPCLB DD statement. Check the JOBLOG forrelated error messages. If the combined errormessages are sufficient to explain the problem, takewhatever corrective action is appropriate. If theproblem cannot be resolved, contact SoftwareSupport.

AZK3138T User record exits cannot be usedbecause the SQL feature is notconfigured

Explanation

None.

User response


AZK3139T Non-zero return code from userexit program. RC=rcode


Explanation

A user record exit program returned a non-zero returncode.

User response

The task is terminated.

AZK3140W INVALID desc CODE func FORservice, DETECTED AT addr

Explanation

A product routine called the system managementmodule with an invalid function code. This failure wasprobably caused by a programming error in the callingroutine. This failure can also be caused by productinstallation and maintenance errors.

User response


AZK3141E rsrc sysserv FAILED, RC=rcode,DETECTED AT addr

Explanation

Some type of error occurred in the systemmanagement routines of the product. See the actualtext of the message for an explanation. The error wasprobably caused by a failure in an operating systemservice (sysserv) requested by a product systemmanagement routine.

User response


AZK3142W Invalid data FOR func, Detected ataddr. Stack: %SK

Explanation

Some type of error occurred in the systemmanagement routines of the product. See the actualtext of the message for an explanation. This failurewas probably caused by a programming error in thecalling routine or in the system management module.

This failure can also be caused by product installationand maintenance errors.

User response


AZK3143U DISPATCHER FAILURE DETECTEDAT addr

Explanation

The internal product dispatcher detected a seriouserror. This failure was probably caused by aprogramming error in the system managementmodule. This failure can also be caused by productinstallation and maintenance errors.

User response


AZK3144E rsrc sysserv FAILED, RC=rcode,DETECTED AT routine+offset

Explanation

Some type of error occurred in the systemmanagement routines of the product. See the actualtext of the message for an explanation. The error wasprobably caused by a failure in an operating systemservice requested by a product system managementroutine.

User response


AZK3145S cblk ERROR SUBSYS =subsys

Explanation

The product detected a serious operating systemcontrol block (cblk) error. The operating systemcontrol block error prevented the system management


routine from performing some request on behalf of acaller. This control block error may cause other systemerrors and may cause the operating system to fail.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate. Youmay need to IPL the system to resolve this problem. Ifthe problem cannot be resolved, contact SoftwareSupport.

AZK3146S EMERGENCY PRODUCTSHUTDOWN STARTED - errdesc

Explanation

The product is shutting down because of a seriouserror. The message text describes the error. The errormay be caused by an abend failure inside the productor by a product rate limit that has been exceeded.Also, the error may have been caused by a productprogramming error or by a system failure of some kind.The product will turn itself off and disconnect itselffrom the operating system.

User response


AZK3147T rsrc sysserv FAILED, RC=rcode,DETECTED AT routine+offset

Explanation

Some type of error occurred in the systemmanagement routines of the product. See the actualtext of the message for an explanation. The error wasprobably caused by a failure in an operating systemservice (sysserv) requested by a product systemmanagement routine.

User response


AZK3148E Main product address space notactive

Explanation

Some routine tried to use a product facility thatrequires the main product address space to be active.The product facility could not be used because themain product address space is not active.

User response

This may or may not be an error condition. Start orrestart the main product address space, if necessary.Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate. If theproblem cannot be resolved, contact SoftwareSupport.

AZK3149E ENFREQ reqtype CODE ecodeFAILED, RC=rcode. STACK: %SK

Explanation

A z/OS event notification facility request, ENFREQ,failed. The meaning of the return code can be found inthe IBM Authorized Assembler Services manual.

User response

If the security server you are using does not supportENF signal 71, check with the security server productvendor for more information. Otherwise, contactSoftware Support. for assistance with this problem.

AZK3150E INVALID desc, VALUE data,DETECTED AT addr

Explanation

A system management routine detected invalid data.The error message describes the invalid data (data).This failure was probably caused by a programmingerror in the calling routine or in the systemmanagement module. This failure can also be causedby product installation and maintenance errors.

User response


AZK3151H ABEND abcode IN func modname+offset


Explanation

A system management routine detected an abendwhile processing a message queue. The message textprovides the abend code, current operation, andabend location. This failure may have been caused bya programming error in the calling routine or in thesystem management module. This failure can also becaused by product installation and maintenanceerrors. This failure will also occur when an addressspace containing a message queue terminatesunexpectedly.

User response


AZK3152W errdesc1 errdesc2 errdesc3,DETECTED AT addr

Explanation

A system management routine detected an error whileprocessing a request on behalf of a caller. Themessage text describes the failure. This failure mayhave been caused by a programming error in thecalling routine or in the system management module.This failure can also be caused by product installationand maintenance errors.

User response


AZK3153E ABEND abcode IN func modname+offset

Explanation

A system management routine detected an abendwhile performing a service on behalf of a caller. Themessage text provides the abend code, currentoperation, and abend location. This failure may havebeen caused by a programming error in the callingroutine or in the system management module. Thisfailure can also be caused by product installation andmaintenance errors.

User response


AZK3156E rsrc MISSING AND REQUIRED FORsysserv, DETECTED AT addr

Explanation

A system management routine detected that aresource (rsrc) needed to perform a service on behalfof a user is not available. The service (sysserv) cannotbe provided because of the error. The message textidentifies the service requested by the user and themissing resource.

User response


AZK3157E func ABEND abcode AT addr

Explanation

An abend failure occurred when a systemmanagement routine called an MVS service routine.The abend occurred in the MVS service routine. Theerror message provides the abend code and abendlocation. This failure was probably caused by aprogramming error in the calling routine, in the systemmanagement module, or possibly in the IBM serviceroutine. This failure can also be caused by productinstallation and maintenance errors.

User response


AZK3200W INVALID SUBPOOL NUMBER=spnoREQUESTED BY modname+offset

Explanation

The storage management routine detected an invalidsubpool number (spno) in a parameter list passed by acaller. The subpool number is not supported by the


storage management routine. The storagemanagement module cannot perform the servicerequested by the caller. The error message gives theinvalid subpool number and the location of the callingroutine. This failure may have been caused by aprogramming error in the calling routine or in thestorage management routine. This failure can also becaused by product installation and maintenanceerrors.

User response


AZK3202W func ERROR RC=rcode REQUESTEDBY modname+offset, SP=subp,LEN=lgth, A=addr

Explanation

A GETMAIN or FREEMAIN request failed with a non-zero return code. The error message gives the storagerequest type (GET or FREE), the return code, and thelocation of the calling routine. This failure may havebeen caused by a programming error in the callingroutine or in the storage management routine. Thisfailure can also be caused by product installation andmaintenance errors.

subp represents the requested subpool

User response

Check if some type of operating system problem (suchas storage shortage) may have caused the problem.Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact Software Support with thisproblem.

AZK3204T modname+offset func stortypespno stg1 stg2 token

Explanation

This is a storage trace message generated by theproduct storage management routine. Storage tracesare used to analyze product storage utilization and tofind storage management bugs. This is not an errormessage. The message gives the calling module name,calling module offset, current function (GET or FREE),storage type, subpool number (spno), storage area

size (stg1), old storage total (stg2), and new storagetotal.

User response

Check if storage trace was activated for some reason.If storage trace is active, ignore this message.Otherwise, storage trace has been inadvertentlyactivated by a memory overlay. Contact SoftwareSupport with this problem.

The variable fields of the message text are: modmodule name off module offset func current functionstype storage type (E/CSA or E/Private) subp storagesubpool number stg1 storage area size or amount stg2storage area size or amount token storage token if any

AZK3205E STORAGE ROUTINE ABEND CODEabcode AT modname+offset

Explanation

The storage management routine detected an abendwhile performing a service on behalf of a caller. Themessage text provides the abend code and abendlocation. This failure may have been caused by aprogramming error in the calling routine or in thestorage management module. This failure can also becaused by product installation and maintenanceerrors.

User response

Check if some type of operating system problem (suchas storage shortage) may have caused the problem.Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.Otherwise, contact Software Support for assistancewith this problem.

AZK3206S SUBPOOL subp REQUIRESGLOBAL MASTER AT modname+offset

Explanation

The storage management routine detected a requestfor a subpool that can only be executed using thecontrol blocks of the main product address space.However, the caller did not provide the main productaddress space control blocks. The current storagerequest will be rejected. This message indicates aninternal error in the product. This failure may havebeen caused by a programming error in the callingroutine or in the storage management module. Thisfailure can also be caused by product installation andmaintenance errors.


User response


AZK3207S CROSS MEMORY REQUIRESGLOBAL MASTER AT modname+offset

Explanation

The storage management routine detected a requestfor a cross memory GETMAIN or FREEMAIN that canonly be executed using the control blocks of the mainproduct address space. However, the caller did notprovide the main product address space controlblocks. The current storage request will be rejected.This message indicates an internal error in theproduct. This failure may have been caused by aprogramming error in the calling routine or in thestorage management module. This failure can also becaused by product installation and maintenanceerrors.

User response


AZK3208S stortype RETURNED FOR stortypeREQUESTED BY modname+offset,SP=subp, LEN=length

Explanation

The storage management routine detected that arequest for extended storage (above the 16MB line)was satisfied with non-extended storage (below the16MB line). This will only happen when the extendedstorage area has been depleted and MVS is returningnon-extended storage to satisfy storage requests. Forexample, the product is requesting ECSA storage butMVS is returning CSA storage because ECSA has beencompletely allocated. This problem can also occur forprivate area storage as well.

stortype may be E/CSA or E/Private

subp represents the subpool requested

User response

This is a very serious error and requires immediateaction. If the message shows that CSA is beingreturned for ECSA requests, then ECSA has beendepleted. One or more products may have to beterminated to release ECSA. At some point, theamount of ECSA allocated may have to be increased.Note that the product can continue to execute in thiscase. However, CSA is likely to be depleted, leading tocomplete MVS system failure. If the message indicatesthat the problem is occurring for private area storage,contact Software Support with this problem.

AZK3209S NO ASCB SPECIFIED FOR TCB-LEVEL STORAGE REQUEST ATmodname+offset

Explanation

The storage management routine detected that across memory GETMAIN or FREEMAIN with anexplicitly specified TCB association did not specify theaddress space designation along with the request.

User response


AZK3210S reqtype XFORM SP=subp LEN=lgthA=addr FROM modname+offset,failrsn

Explanation

The storage management routine determined that anSRB-mode memory GETMAIN or FREEMAIN requestcould not be internally converted to an appropriatebranch-entry request. Without transformation, therequest cannot execute in SRB-mode.

subp represents the subpool of original request

User response

The request to get or free storage is rejected. Check ifany other error messages were generated along withthe error message above. If the combined errormessages are sufficient to explain the problem, takewhatever corrective action is appropriate. Otherwise,contact Software Support for assistance with thisproblem.

AZK3211S STG OBTAINED AT addr NOT2**reqal BOUNDARY ALIGNEDREQUESTED BY modname+offset


Explanation

The storage management routine determined thatobtained storage was not aligned on the requestedboundary (reqal).

User response

The storage management routine generates an S0C3to abnormally end the calling procedure. This is doneto prevent errors which are likely to occursubsequently if the incorrectly aligned storage is used.Contact Software Support with this problem.

AZK3212S INVALID REQUEST TO FREE ALLSUBPOOL subp STORAGEREQUESTED BY modname+offset

Explanation

The storage management routine determined that aproduct storage FREEMAIN request has been madewith a zero address. Such a request results in freeingall storage within the specified subpool (subp). Therequestor has either inadvertently specified theFREEMAIN storage address as zero, or a legitimateFREEPOOL request was coded incorrectly.

User response

The storage management routine generates an S0C3to abnormally end the calling procedure. This is doneto prevent errors which are likely to occursubsequently after an entire subpool is freedinadvertently. If the problem cannot be resolved,contact Software Support.

AZK3250S service ERROR RC=rcode

Explanation

This message describes a variety of errorsencountered while using the QEDIT supervisor service.

User response

This problem may be caused by a failure either in theproduct or in the operating system. If possible, fix theproblem identified by the error messages, and restartthe product. If the problem cannot be resolved,contact Software Support.

AZK3251I cmd msgtext

Explanation

This message is only issued when the product is indebugging mode. It echoes commands sent to theproduct.

User response


AZK3252S component initialization timeoutdetected

Explanation

This message is issued when the product attempted toinitialize full SEF (component) support, but SEFinitialization did not complete in the allowed timeperiod. This is a serious error, and product initializationis terminated.

User response


AZK3253I prodname version prodver buildbuildno subsystem subsysinitialization complete

Explanation

This is the standard message indicating that productinitialization is complete.

User response

No action required.

AZK3254I component map build beginning d2at t2 for ss

Explanation

This message is issued when a SQL map build iscomplete.

Response


AZK3255I component map build complete ond2 at t2 for ss

Explanation

This message is issued when a SQL map build iscomplete.

Response



AZK3256S SQL map build failed due tocomponent

Explanation

This message is issued when the SQL engine mapbuild process does not complete in the allowed timeperiod (five minutes). This is a serious error, and majorparts of the product may not function correctly.

Response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate. If theproblem cannot be resolved, contact IBM SoftwareSupport.

AZK3259E (cmd) invalid command

Explanation

The product tried to match an operator command toan existing command rule (cmd) and wasunsuccessful.

User response

Verify that the specified command is spelled correctly.Also, verify that it exists and is enabled in the currentcommand rule data set.

AZK3260I Server subsystem subsys is anERLY subsystem

Explanation

The product has been started as an ERLY subsystemfor use by other (non-product) subsystems thatnormally start before ordinary product subsystems. AnERLY product subsystem can be started SUB=MSTR ifdesired. It does not perform normal product work anduses very few system resources.

User response


AZK3300W INVALID desc CODE func FORservice, DETECTED AT addr

Explanation

A product routine called the SQL management modulewith an invalid function code. This failure was probablycaused by a programming error in the calling routine.This failure can also be caused by product installationand maintenance errors.

User response


AZK3301E PLAN plan DBRM dbrmTIMESTAMPS MISMATCH time1time2

Explanation

The timestamp associated with the SQL statementplist does not match the timestamp in the DBRM. Theexact SQL statement cannot be displayed.

This message contains two timestamps; time1represents the plist timestamp, and time2 representsthe DBRM timestamp

User response

Verify that the DBRM library specified in the JCL of themain product library is synchronized with theapplication program load library (i.e. both the load andthe DBRM were produced from the same version of thesource). Correct any mismatch, and restart theproduct.

AZK3302E ddname DDNAME not allocated -SQL source not available

Explanation

The DBRM DD statement is not present in the JCL usedto start the main product address space.

User response

Add the DBRM DD statement to the JCL of the mainproduct address space

AZK3303E DBRM OPEN failed forDDNAME=ddnameDSNAME=dsname RC=rcode

Explanation

AZK tried to open the DBRM library for input and theopen operation failed. Actual SQL statement textsmust have the DBRM(s).

User response

Examine the data set and any other messages thatmay accompany this one. If you are able to resolve theproblem, restart the product.


AZK3304E Member dbrm not found in DBRMlibrary

Explanation

A BLDL for the DBRM member failed.

User response

Determine why the DBRM is missing from the DBRMlibrary. If necessary, change the library specified in theJCL for the main address space, and restart theproduct.

AZK3305E func failed for MEMBER=dbrmDDNAME=ddnameDSNAME=dsname RC=rcode

Explanation

An I/O operation (func) failed while attempting toaccess the DBRM library.

User response

Use this message in conjunction with any othermessages that may accompany it to resolve theproblem. You may also want to examine the data setfor problems. Once the problem is corrected, restartthe product.

AZK3306E DBRM MEMBER dbrm TOO LARGE,MAXIMUM SIZE IS countRECORDS

Explanation

The current DBRM is too large for AZK to handle.

User response

Ensure that the DBRM actually does contain more thanthe maximum number of records. If it does, contactSoftware Support.

AZK3307E DBRM member dbrm is empty

Explanation

The DBRM member specified by the message does notcontain any records.

User response

Verify that the data set does not contain any records. Ifit does not contain records, replace it with a correctedDBRM member. If the member does contain records,contact Software Support for assistance with thisproblem.

AZK3308E DBRM MEMBER NAME dbrm DOESNOT MATCH PROGRAM NAMEprogram

Explanation

The DBRM member name does not match the programname that is contained within the DBRM.

User response

It is possible that the DBRM member has beenrenamed. Verify that this is the problem, and correct it.The DBRM member name and the program namecontained within the DBRM must be identical.

AZK3309E SQL statement stno missing fromDBRM dbrm

Explanation

The SQL statement identified by the applicationprogram's plist could not be found in thecorresponding DBRM member.

User response

The plist's statement number (stno) should match oneof statements in the DBRM. Verify that the applicationprogram load module and the DBRM are synchronized(i.e. they were produced at same time from the sameversion of the source). Correct any mismatches, andrestart the product.

AZK3310E DBRM close FAILED FORDDNAME=ddnameDSNAME=dsname RC=rcode

Explanation

AZK tried to close the DBRM library and the closeoperation failed. Resources may not have beencompletely released.

User response

Examine the data set and any other messages thatmay accompany this one. If you are able to resolve theproblem, restart the product.

AZK3311T ASSIGN AND CONCATENATE LOBREQUESTS ARE SUSPENDED

Explanation

The ability to use the assign and concatenate functionsfor sending lob data from the client to the server issuspended. This message is issued when theCLIENTMAXLOBSIZE parameter value is set to zero(0).


User response


AZK3312T NETWORKBUFFERSIZE or MXBUvalue(s) are inadequate for thenumber of columns in the SQLstatement.

Explanation

There is insufficient space in the communicationsbuffer to hold the SQLDA (metadata) for the SQLstatement. The NETWORKBUFFERSIZE and MXBUparameter values must be large enough to hold themetadata for the SQL statement that references themost columns.

User response

Change NETWORKBUFFERSIZE and/or MXBU to anappropriate value.

AZK3313T DB2 subsystem with ASID subsyswas not found

Explanation

The ERLY control block for the Db2 subsystem was notfound.

User response

The product was not able to find the ERLY controlblock for the Db2 subsystem using the ASID. Theroutine cannot proceed because of this error. This canoccur when the Db2 subsystem ends with a system04F ABEND.

AZK3314S DB2 subsystem with ASID subsyswas not found

Explanation

The ERLY control block for the Db2 subsystem was notfound.

User response

The product was not able to find the ERLY controlblock for the Db2 subsystem using the ASID. Theroutine cannot proceed because of this error. This canoccur when the Db2 subsystem ends with a system04F ABEND.

AZK3315W Operational mode for DB2subsystem subsys could not bedetermined

Explanation

The product is not aware of the version of Db2executing in the Db2 subsystem and cannot determinethe operational mode.

User response

Processing continues. Contact Software Support toreport this message.

AZK3316T Operational mode for DB2subsystem subsys could not bedetermined

Explanation

The product is not aware of the version of Db2executing in the Db2 subsystem and cannot determinethe operational mode.

User response

Processing continues. Contact Software Support toreport this message.

AZK3700H TSO/SRV now using count servers- MIN=parmval1 MAX=parmval2

Explanation

The product has allocated a new server descriptorcontrol block and will start a new TSO/SRV serveraddress space.

parmval1 represents the value of CGIMIN, andparmval2 represents the value of CGIMAX

User response


AZK3701I service OF desc FAILED, RC=rcode

Explanation

This is a generic error message used to describe awide variety of errors detected by the product Serverroutine manager. The message text provides thecurrent operation (service) and what the currentoperation was trying to do.

User response


AZK3702H TSO/SRV started serverjobname,ASID=asid


Explanation

The product has issued a START command to create anew TSO/SRV server address space, and the addressspace has been created.

User response


AZK3703W TSO/SRV SUBTASK UNABLE TOSCHEDULE EXTERNAL TSOSERVER - ABEND/POSTCODES=(abcode/pcode)

Explanation

The product TSO/SRV execute queue processingfunction detected an abend or error while attemptingto schedule a command into an external TSO serveraddress space. This message is returned to theoriginal requestor.

User response

Gather all abend error data, and contact your localproduct systems programming group for support.

AZK3704H TSO/SRV cancelled serverjobname,ASID=asid

Explanation

The product has issued a CANCEL command toeliminate a TSO/SRV server address space (asid). Thismay occur either because of a change (reduction) inthe value of the TSOMINSERVERS parameter orbecause of a server command exceeding its executionlimits.

User response

When a server command exceeds the server executionlimits, this message is accompanied by a messagedescribing which limit is exceeded. Either modify thelimit or correct the server command/program.

AZK3705I Idle TSO server terminated due toTSOMAXSERVERS

Explanation

The product detected that there were currently moreservers active than specified in the TSOMAXSERVERSparameter and terminated the server in questionbecause it was currently idle.

User response


AZK3706W Transaction aborted

Explanation

This message is sent to the issuer of a TSO/SRV servercommand when the server has terminated whileexecuting the transaction.

User response

Check for other messages associated with thiscondition, and attempt to resolve the problem.

AZK3707S TSO/SRV server failed duringinitialization

Explanation

The product attempted to start a TSO/SRV serveraddress space. However, the address space failedduring initialization.

User response

Verify that the TSO/SRV server started task JCL iscorrect. JCL errors of one kind or another (e.g. data setdoes not exist) are frequently the cause of thiscondition. If you are unable to resolve the problem,contact Software Support.

AZK3708E Unable to find ASVT entry forTSO/SRV server ASID=asid

Explanation

After issuing an internal START command for aTSO/SRV address space, the product attempted tovalidate the returned ASID and found it to be invalid.This error indicates one of the following conditions: (1)the ASID is negative, (2) the ASID is greater than thesystem MAXUSER value, or (3) the associated ASVTentry is currently not in use.

User response

This condition is extremely unlikely to occur.

AZK3709W TSO server canceled - maxtransaction time exceeded

Explanation

The transaction currently being processed by theserver in question has exceeded the maximum amountof time allowed by TSOMAXCMDRUNTIME and hascaused the cancellation of the server.

User response

Please examine the SYSLOG for the _3710Icompanion message, which will detail the command in


error and its approximate start time. Either correct thecommand in error or increase theTSOMAXCMDRUNTIME value.

AZK3710I CMD TEXT = cmd ,START TIME =time

Explanation

This is the companion message to _3709W. It detailsthe command which was being processed by thecanceled server and its approximate start time.

User response

Either correct the command in error or increase theTSOMAXCMDRUNTIME specification.

AZK3711I Idle server terminated due toTSOMINSERVERS orTSOSRVDORMANT timeout

Explanation

The product detected that the current number ofservers is greater than the user specifiedTSOMINSERVERS parameter but not greater than theuser specified TSOMAXSERVERS value and that theserver has been idle longer than the user specifiedTSODORMANTTIMEOUT value. The productterminated the server in question because it wascurrently idle.

User response


AZK3712W TSOMAXSERVERS value(parmval1) invalid. Set toTSOMINSERVERS (parmval2).

Explanation

The product Server processing has detected that theTSOMAXSERVERS value has been set to a value that islower than the TSOMINSERVERS value. This is invalid -the maximum number of servers can never be lowerthan the minimum number of servers. The maximumvalue is changed to the minimum value.

parmval1 represents the value of TSOMAXSERVERS,and parmval2 represents the value ofTSOMINSERVERS

User response

If the incorrect values are set via the startup exec orany other program, correct the program(s). You mayalso adjust the TSOMINSERVERS andTSOMAXSERVERS values using the ISPF parameterdisplay.

AZK3713I TSO/SRV server added due toexcessive queue depth (qdep)

Explanation

The number of requests on the TSO/SRV serverexecute queue currently exceeds the threshold set bythe user specified TSOSRVQUEUEADDDEPTH. Thenumber of servers is being increased by one since thenumber of servers is still below the maximum numberof servers limit as specified by the TSOMAXSERVERSvalue.

User response


AZK3714H TSO/SRV terminated serverjobname,ASID=asid

Explanation

The product has terminated a TSO server addressspace. The server has been terminated because eitherthe current number of servers exceeds theTSOMAXSERVERS limit, or the current number ofservers exceeds the TSOMINSERVERS value and thecurrent server has been idle more thanTSOSRVDORMANTTIMEOUT seconds. This messagemay also occur when a control command requestedserver termination. The server address space may notterminate immediately if it is currently running atransaction. If the server does not terminatevoluntarily within a limited time period, the server willbe cancelled by the product.

User response


AZK3715H TSO/SRV SUBTASK ABEND abcodeIN func modname+offset

Explanation

The product TSO/SRV execute queue processingfunction detected an abend. The message textcontains the abend code, current operation, and abendlocation.

User response

Check if any other error messages were generatedalong with the error message above. If the combinederror messages are sufficient to explain the problem,take whatever corrective action is appropriate.

AZK3716O Cancelled TSO server jobnamestepname (ASID=asid), has notterminated


Explanation

The product has issued a CANCEL command toterminate a TSO server. More than one (1) minute haselapsed since the CANCEL command was issued, butthe server address space has not terminated.

User response

First, attempt another CANCEL command using theSTEP NAME from the message. If this does not causethe server to terminate, use the MVS FORCE commandor attempt to kill the server address space using anyother means at your disposal.

AZK3717H TSO server execute queue reset

Explanation

A control command has caused the TSO/SRV executequeue to be cleared. All pending TSO transactionshave been discarded.

User response


AZK3718E TSO ADDRESS SPACE CREATIONFAILED, RC = rcode, REASONCODE = rsncode

Explanation

A failure occurred in the service routine that schedulesan address space CREATE. The TSO address space willnot be created. The return and reason codes in themessage are from the MVS ASCRE service routine.

User response

Check the return code in the message. If the returncode is 52 or higher, this error is most likely a systemrelated problem, and you should report this to yoursystem programming staff. If necessary, set theTSOSRVUSEASCRE to NO so that START commands(rather than ASCRE) will be used to create TSOoutboard server address spaces.

AZK3720T TSO EXECUTE QUEUE ADD;QD=qdep, CMD=cmd

Explanation

This message is actually issued by the ADDRESS TSO |CGI processor when the DEBUG FLAG is set ON. Thismessage indicates that a command (cmd) is being sentto the product Server queue. Note that queue depth(qdep) is displayed prior to the addition of the currentcommand.

User response

None. This message is used for debugging and analysispurposes only.

AZK3721T TSO COMMAND DISPATCH;QD=qdep, ASID=asid,QTIME=qtime, CMD=cmd

Explanation

This message indicates that a command has beenremoved from the TSO execute queue and has beensent to a product TSO server address space. Thismessage is only issued when DEBUG is set ON.

qdep represents queue depth

qtime represents time spent on TSO execute queue in100ths of a second

User response


AZK3722T TSO COMMAND RECEIVED;ASID=asid, ETIME=etime,CMD=cmd

Explanation

This message indicates that a server has received acommand. The delay between the time (etime) theTSO command dispatch message is issued and thetime this message is issued is due to operating systemscheduling factors. This message is only issued whenDEBUG is set ON.

User response


AZK3723T TSO COMMAND COMPLETE;ASID=asid, ETIME=time1,CPU=time2, I/O=count, CMD=cmd

Explanation

This message indicates that a server has completedexecution of a command. This message is only issuedwhen DEBUG is set ON.

The message has two time values; time1 representstime since command was sent to server in seconds,and time2 represents command CPU time in hex(microseconds)


User response


=

AZK3724H name (userID) SENT TSO CMD cmd

Explanation

This message indicates that a server has received acommand (cmd). The program or ruleset.rulename(name) indicates where the command originated.

User response


AZK3725T TSO execute processor posted bycomponent

Explanation

This message indicates that the TSO executeprocessor has received a signal from anothercomponent.

User response


AZK3729T msgtext var2 var3

Explanation

This message is for TSO debugging and trace purposesonly.

User response


AZK3750H SEF var1 var2

Explanation

This message indicates that the product executeprocessor has terminated.

User response

This message is for informational purposes only unlessit indicates that the SEF command queue has not beenallocated. In that case, you should check for any othermessages that appeared on the console duringproduct initialization that may assist you in resolvingthis problem. If you are unable to resolve the problem,contact Software Support for further assistance.

AZK3751I SEF service OF desc FAILED,RC=rcode

Explanation

This is a generic error message used to describe awide variety of global variable initialization andtermination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do.

User response


AZK3752W SEF API INITIALIZATION FAILEDDUE TO initstep additinfo1additinfo2

Explanation

During SEF initialization, an error was detected whilecreating API interface linkages. The messagedescribes the error encountered.

User response


AZK3753W ABEND var1 AT var2+var3, SEFCOMMAND var4 ABORTED

Explanation

There was an error within the SEF rule processor.

User response


AZK3754I SEF command syntax error: cmd

Explanation

The SEF execution processor detected a commandwith invalid syntax for the ADDRESS SEF environment.Normally, the syntax error should have been detectedat rule enabled or program compile time.

User response

Modify the rule or program that issued the commandto use a valid ADDRESS SEF command.


AZK3755E service OF PRECOMPILED DATASET (dsname) FAILED RC=rcode

Explanation

The SEF execution processor detected a request toallocate/deallocate (service) a compiled rules library,and the request failed. Check error messagespreceding this failure for more allocation error data.

User response

Check any allocation error messages that precededthis message for more diagnostic information. Afterfixing the problem, reset the parametersSEFPRECOMPILED and SEFPRECOMPILEDDSN.

AZK3756I SEF precompiled rules active

Explanation

SEF has activated the Compiled Rules Facility. Thisfacility is activated by the setting of the parameterSEFPRECOMPILED to ON and the parameterSEFPRECOMPILEDDSN to a valid compiled rule library.

User response


AZK3757I SEF var1 var2

Explanation

This message indicates that a command has executedand is returning status information. It indicates thesuccess or failure of the command.

User response

This message is for informational purposes only. If itindicates failure of the command, check that theparameters you have given are correct.

AZK3780I func OF desc FAILED, RC=rcode

Explanation

A failure occurred in the service routine that sets (func)the wait timer interval (desc) for the next tracecheckpoint. This message should be preceded by amessage containing the return code from the MVSSTIMERM service.

User response


AZK3781S ABEND abcode OCCURRED ATmodname+offset - desc

Explanation

An abend occurred during trace checkpointprocessing. The location of the abend is shown in theabend error message. All trace checkpoint processingwill be suspended until the main product addressspace is restarted. Note that the main product addressspace will start to accumulate non-VIO ASM slots as ifno DIV data set had ever been allocated. The gradualaccumulation of ASM slots by the main productaddress space could eventually cause an ASM slotshortage.

User response

Check the error messages and the abend codeassociated with this problem. There may be one ormore additional error messages or abends referring tothe current trace checkpoint processing problem.Check for OPEN errors, such as security productrelated abends. Also, check for storage allocationerrors or abends. If possible, fix the problem identifiedby the error messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport.

AZK3782S file ddname error FAILED RC=rcodeerrdesc

Explanation

A problem was encountered while opening orrefreshing a product data set. The message indicatesthe cause of the failure.

User response

Check the error messages associated with thisproblem. There may be one or more additional errormessages or abends referring to the currentprocessing problem. If possible, fix the problemidentified by the error messages, and restart theproduct. If the problem cannot be resolved, contactSoftware Support.

AZK3783S file ddname processing ABENDEDcode=abcode reason=rsncode atmodname+offset

Explanation

A problem was encountered while opening orrefreshing a product data set. The message indicatesthe abend code associated with the processingfunction.

User response

Check the error messages associated with thisproblem. There may be one or more additional error


messages or abends referring to the currentprocessing problem. If possible, fix the problemidentified by the error messages, and restart theproduct. If the problem cannot be resolved, contactSoftware Support.

AZK3784T src DUPLICATES THE type ID INsrc - SKIPPED

Explanation

A problem was encountered while opening orrefreshing a product data set. The message indicatesthat a duplicate entity was detected. TheDUPLICATING entity will be ignored.

Variables in this message (src, type, and ID) refer tothe duplicating entity

User response

Check the error messages associated with thisproblem. There may be one or more additional errormessages or abends referring to the currentprocessing problem. If possible, fix the problemidentified by the error messages, and refresh or restartthe product. If the problem cannot be resolved,contact Software Support.

AZK3785H src DUPLICATES THE type ID INsrc - SKIPPED

Explanation

A problem was encountered while opening orrefreshing a product data set. The message indicatesthat a duplicate entity was detected. TheDUPLICATING entity will be ignored.

Variables in this message (src, type, and ID) refer tothe duplicating entity

User response

Check the error messages associated with thisproblem. There may be one or more additional errormessages or abends referring to the currentprocessing problem. If possible, fix the problemidentified by the error messages, and refresh or restartthe product. Normally, this is done by manuallyremoving one or the other source file identified in themessage. If the problem cannot be resolved, contactSoftware Support.

AZK3886E RULESET rsname additinfo1,additinfo2 … additinfo8

Explanation

The SEF request is rejected because the ruleset statusprevents execution of the request.

User response

Examine previously reported conditions to determinethe cause of the problem.

AZK3887I RULESET rsname additinfo1,additinfo2 … additinfo8

Explanation

An error occurred while processing an SEF request andthe status of a ruleset is effected. This messagefollows the original error message to warn ofadditional/on-going ramifications from the error.

User response

The server takes the action reported in this message inorder to recover from the previously reported errorcause.

AZK3888E Required master WWW ruleset notdefined - HTTP processingimpossible

Explanation

SEF Rule manager did not find a Master WWW rulesetdefinition. The rule manager will not enable ANY WWWrulesets.

User response

Check your initialization procedure, SWSxIN00, to besure it defines ONE master WWW ruleset using the"WWWCLASS(MASTER)" keyword.

AZK3889I SEF version OPERATIONAL MODEDOES NOT SUPPORT THE funcFUNCTION

Explanation

SEF rule manager received a command which it doesnot support when operating in the indicatedoperational mode.

User response

Correct the command, and re-issue.

AZK3790I func OF desc FAILED, RC=rcode

Explanation

A failure occurred in the service routine that sets (func)the wait timer interval (desc) for the next globalvariable checkpoint. This message should be precededby a message containing the return code from the MVSSTIMERM service.


User response


AZK3791E func for creating global variablebackup, RC = rcode, Reason code =rsncode

Explanation

A failure occurred in the service routine (func) thatschedules an address space create. The globalvariable backup will not execute. The return andreason codes in the message are from the MVS ASCREservice routine.

User response

Check the return code in the message. If the returncode is 52 or higher, the error is most likely a systemrelated problem, and you should report this to yoursystem programming staff. If the problem cannot beresolved, contact Software Support for assistance.

AZK3792I Global Variable Backup addressspace procedure has been created

Explanation

This message is informational only. The messageindicates that the product created the global variablebackup address space.

User response


AZK3800T An unknown value was found infield field by routine.

Explanation

A value was found in a control block field that cannotbe validated by the SERVER API.

User response


AZK3847W Error compiling SEF rule rule,closing */ not found whereexpected.

Explanation

SEF rule manager attempted to compile a REXX rulewith a /*%include statement that contained invalidsyntax. After the member name, only */ is allowed.Imbedded comments inside the /*%include phraseare not supported.

User response

Correct the /*%include statement and try again.

AZK3848W Error compiling SEF rule rule,INCLUDE name memname toolong.

Explanation

SEF rule manager attempted to compile a REXX rulewith a /*%include statement that specified a membername (memname) longer than 8 bytes.

User response

Correct the /*%include statement and try again.

AZK3849T SEF version operational mode doesnot support the func function

Explanation


User response


AZK3850E INTERNAL routine1 ERRORDETECTED BY routine2:CALLER(csect) RTADDR(addr) -additinfo

Explanation

An error occurred while an internal API routine wasexecuting. This message reports some inconsistencyor a possible logic error.

User response

The API rejects the current request and continues.Check for other messages which may indicate theprecipitating cause.

AZK3851I NO EXECUTABLE OBJECT (XO)DATASETS ARE CURRENTLYDEFINED OR IN-USE

Explanation

This response is returned for 'LIST =XOFILES' SEFcommand if no executable object image (XO) datasetsare defined or in use. XO datasets may contain pre-compiled executable object images such as SEF rulesor HTX skeletons.


User response

None.

AZK3852I %1

Explanation

This response is returned for 'LIST =XOFILES' SEFcommand for each individual XO dataset allocated inthe system. A list of zero or more associations mayfollow this message.

User response


AZK3853I %1

Explanation

This response is returned for 'LIST =XOFILES' SEFcommand for each association with an XO dataset.This message follows the XO dataset status messageMSG3852I.

User response


AZK3854I %%INCLUDE processing ignoredwhen ISPF EDIT source beingcompiled, line lineno

Explanation

A %INCLUDE statement was detected in the source ofthe Product REXX program being compiled. Theprocedure source is being fetched from the currentISPF Edit session and %INCLUDE is not supported inthis environment.

User response

The %INCLUDE statement, with its including commentdelimiters is not processed. The original text ispreserved in the procedure source being fetched fromthe current edit session.

AZK3855I %%INCLUDE statement syntaxinvalid, line lineno

Explanation

A %INCLUDE statement was detected in the source ofthe Product REXX program being compiled, but thestatement was incomplete. /*%INCLUDE, the namedmember, and */ must all be present on a single sourceline. The member name must be less than or equal to8 bytes in length.

User response

The %INCLUDE statement is rejected

AZK3856I %%INCLUDE member (member)not found, line lineno

Explanation

A %INCLUDE statement was detected in the source ofthe Product REXX program being compiled, but themember named in the statement cannot be found ineither the library dataset where the source memberresides or in the SYSEXEC library concatenation.

User response

The %INCLUDE statement is rejected

AZK3886E RULESET rsname additinfo1,additinfo2 … additinfo8

Explanation

The SEF request is rejected because the ruleset statusprevents execution of the request.

User response

Examine previously reported conditions to determinethe cause of the problem.

AZK3887I RULESET rsname additinfo1,additinfo2 … additinfo8

Explanation

An error occurred while processing an SEF request andthe status of a ruleset is effected. This messagefollows the original error message to warn ofadditional/on-going ramifications from the error.

User response

The server takes the action reported in this message inorder to recover from the previously reported errorcause.

AZK3888E Required master WWW ruleset notdefined - HTTP processingimpossible

Explanation

SEF Rule manager did not find a Master WWW rulesetdefinition. The rule manager will not enable ANY WWWrulesets.


User response

Check your initialization procedure, SWSxIN00, to besure it defines ONE master WWW ruleset using the"WWWCLASS(MASTER)" keyword.

AZK3889I SEF version OPERATIONAL MODEDOES NOT SUPPORT THE funcFUNCTION

Explanation


User response


AZK3890I msgs

Explanation

SEF rule manager uses this message to list formattedcontrol block output messages (msgs).

User response

These messages contain the formatted control blockimage.

AZK3891I output

Explanation

SEF rule manager issued the current message to listruleset information to the output area.

User response

The current message is statistical and lists the rulesetsin the output area. No response is required to thismessage. Check the rule output listing, and makechoices accordingly.

AZK3892I INDEX COMMAND OPERAND(operand) IS NOT VALID - NOACTION TAKEN

Explanation

This message is generated if an invalid INDEXcommand is passed to the ADDRESS SEF hostcommand environment.

User response

No action is taken, and the command is not processedfurther.

AZK3893E SEF RULESET rsname HAVEINVALID RULETYPE(ruletype) -RULESET STOPPED/OFFLINE

Explanation

While opening a ruleset SEF, SEF detected that theruleset's definition contains an invalid RULETYPE()specification.

User response

The ruleset is considered to be offline and is notopened. Check for causes that might explain theinvalid RULETYPE() designation for the ruleset namedin the message.

AZK3895I data

Explanation

This message is issued in response to an SEF INDEXURL command. It is the first message returned foreach active rule. The data items returned, blankdelimited, in this message are the ruleset name, therule member name, master/subord, gateway/target,count of rule process sections, and the URL matchcriterion.

User response


AZK3896E RULESET OFFLINE rsname dsnameruletype errdesc

Explanation

An SEF request was made that required that a rulesetbe opened for processing, but the ruleset is currentlystopped or offline.

User response

Take action to place the ruleset online, and re-issuethe request. One common problem is that the rulesetdsname no longer exists.

AZK3897E RULESET rsname is not defined

Explanation

An SEF request was made that required that a rulesetbe opened for processing. The ruleset is not defined tothe system.

User response

Check the list of defined rulesets to determine if theruleset was not properly defined or specify the correctruleset name.


AZK3898W RULESET rsname1 AND rsname2ARE BOTH DEFINED AS MASTERWWW RULESETS - RULESETrsname2 FLAGGED WITHSTATUS(OFFLINE)

Explanation

When the SEF rule manager attempted to process thelist of rulesets defined to the system, it found thatmore than one master WWW ruleset had been defined.Only one ruleset can be defined withRULETYPE(WWW) WWWCLASS(MASTER) attributes.

User response

The second ruleset defined as a master WWW rulesetwill not be processed. It is flagged withSTATUS(OFFLINE) and stopped so that no processingof the data set will occur until the RULESET definitionhas been changed.

AZK3899W No SEF rulesets have been defined

Explanation

When the SEF rule manager attempted to process thelist of rulesets defined to the system, it found that novalid rulesets had been defined.

User response

The current message is a rule status report messageand may not require any response. If rulesets shouldbe defined, check your start-up procedure for errorswhich might have occurred while processing DEFINERULESET statements.

AZK3900T RULE rsname.rulename FORruletype pc status

Explanation

SEF rule manager issued the current informationalmessage to report the status of the current rule. Theruleset rulename is now enabled.

pc represents primary criterion

User response

The current message is a rule status report messageand does not require any response.

AZK3901E service OF operand FAILED,RC=rcode

Explanation

A configuration, authorization, runtime, or I/O errorhas been encountered while executing an SEF rule

manager request. The request cannot be completed,but may be possible at a later time. The SEF rulesetinvolved with the request may be placed into STOPPEDor OFFLINE state.

User response

Examine surrounding messages to determine if theSEF request failed because of insufficientauthorization on the part of the requestor to executethe request. If the request is due to a configurationerror, you may find it necessary to correct serverstartup parameters and restart the server.

AZK3902E var1 var2 SECTION IN RULE var3

Explanation

The SEF rule manager did not find a matching sectionheader table entry. The processing of the current ruleis terminated.

User response

Ensure that the rule sections are properly coded andvalid. Review the rule for obvious coding errors. Referto the product Server Administration Guide for moredetails on rule coding. Correct the above problem, andrestart.

AZK3903E INVALID CRITERION crit INruletype rule rulename

Explanation

SEF rule manager detected an invalid criterion (crit)when processing the current rule. Only a singlewildcard is allowed in the rule criterion. Ruleprocessing is terminated.

User response

Check the error message text for the criterion field,and ensure that the criterion is limited to one matchcriteria or one wildcard. Refer to the product ServerAdministration Guide for more details on the firing ofrules and the valid criteria.

AZK3906I output

Explanation

SEF rule manager issued the current message to listthe rule data set index (prefix/suffix) to the outputarea.

User response

The current message is statistical and lists the rulesetsin the output area. No response is required to this


message. Check the rule output listing, and makechoices accordingly.

AZK3907I SEF is not active

Explanation

SEF rule manager has detected that SEF is not active.

User response

Ensure that the product is started and SEF is active.Contact your local product systems programminggroup for assistance.

AZK3908I INVALID SEF REQUEST TYPEreqtype rsname rulename

Explanation

SEF rule manager detected an invalid SEF rule requesttype during rule request processing. The currentrequest is terminated.

User response

Check the current request for any errors. Check therequest type in the error message text against the rulesections in the product Server Administration Guidefor any inconsistencies. Review the problem, and takecorrective action.

AZK3909I RULE rsname.rulename IS NOTENABLED

Explanation

An attempt to disable a rule failed because the rule isnot currently enabled.

User response

No action required.

AZK3910I No rules enabled in Rule Setrsname

Explanation

This is an informational or status report messageissued by SEF rule manager. Either no rules exist or norules are enabled in ruleset.

User response

No action required.

AZK3911I RULE rsname.rulename not found

Explanation

SEF rule manager did not find the member name thatcontains the current rule. The rule request is aborted.

User response

Ensure that the rule listed in the rule name field of theerror message exists, or create one before invoking therequest.

AZK3912E No ISPF statistics for rulerulename in rsname.

Explanation

SEF rule manager found no ISPF statistics for the rulemember in the indicated ruleset.

User response

Ensure that statistics exist for the rule in the PDSdirectory and that ISPF statistics is turned on.

AZK3913E ind Criterion syntax error lineno inrule rulename

Explanation

A syntax error was detected in a rule while attemptingto enable it. The time criteria are syntacticallyincorrect.

ind may indicate "Time" or "Screen"

User response

Check the product Server Administration Guide for thecorrect syntax. Correct the rule, and re-enable it.

AZK3914E INCONSISTENT ind CRITERIONlineno IN RULE rulename

Explanation

A time or screen (ind) criterion was syntacticallycorrect but inconsistent. A starting time greater thanan ending time or a row range whose first row value islarger than the second may cause this error message.

User response

Correct the inconsistent criterion, and re-enable therule.

AZK3915E MAXIMUM OF maxno indCRITERIA EXCEEDED IN RULErulename


Explanation

Too many screen or time (ind) criteria were specifiedin the header section of a rule.

User response

Reduce the number of time or screen criteria in therule, and re-enable the rule.

AZK3916I TOD RULE rsname.rulename HASBEEN DISABLED - ALL TIMECRITERIA HAVE EXPIRED

Explanation

SEF rule manager disabled the current rule (TOD) afterall time criteria expired. This may or may not be anerror.

User response

The current TOD rule time criterion is not valid beyondthe last fire time. If rule was intended to go beyond thelast fire time, ensure that the next TOD rule is createdwith the required start/stop/interval or time criteriadesired.

AZK3918E Error 43 reqtype program, linelineno: routine routine not found

Explanation

SEF rule manager did not find the current routine.

User response

Review the current rule code for the correct invocationand coding of a routine name. Refer to the productServer Administration Guide for calls to routines.Correct the problem, and restart.

AZK3919E NO VALID RULE HEADER FOUNDIN RULE rulename - errdesc

Explanation

SEF rule manager did not find a valid rule header in thecurrent rule.

User response

Review the current rule code for a valid rule header.Refer to the product Server Administration Guide forrule header coding. Correct the problem, and restart.

AZK3920W Following line(s) ignored in rulerulename:

Explanation

SEF rule manager found a line that was skipped andwill ignore the following lines.

User response

Review the current rule code, and eliminate any blanklines. Correct the rule, and restart.

AZK3921W Rule rulename contains noexecutable sections

Explanation

SEF rule manager found no executable sections in thecurrent rule.

User response

Review the current rule code to make sure it isexecutable code (e.g. RETURN SUPPRESS in PROCsection if this is a message rule). Without anyexecutable sections, the current rule cannot beprocessed by the SEF manager.

AZK3922I MATCH TABLE LIST - d1 t2

Explanation

The SEF rule manager issued this message to list thematch table (message parameter list).

User response


AZK3923I MATCH TABLE AT addr PFX=prefixSFX=suffix LEN=length PRI=pcodeROOT AT root

Explanation

SEF rule manager issued this message to list thematch table at the address shown in the message text.

User response


AZK3924I Match table list empty

Explanation

SEF rule manager issued this message to list a matchtable entry that is empty.

User response



AZK3925I seqno rsname.rulename critlvlNODE LVL=lvl ADR=addr1LO=addr2 HI=addr3 AORL=addr4LEN=length

Explanation

This message is for debugging purposes only.

User response

None.

The variable fields of the message text are: sqnosequential order rule ruleset.rule crit criterion levelnode nesting level addr1 address current OPTI addr2low subtree address addr3 high subtree address addr4address current AORL length AORL length

AZK3926I SECTION section INVALID errdescON LINE lineno

Explanation

The SEF facility found an invalid section header withinthe rule, so the rule could not be enabled.

User response

Correct the event procedure, and re-enable.

AZK3927I No match for rulename

Explanation

The product rule manager did not find a match for thisrule.

User response


AZK3928E RULESET rsname rsprefix ISerrmsg

Explanation

SEF rule manager checked the ruleset prefix string andfound it to be blank.

User response

Ensure that the ruleset prefix string is not blank. Referto the product Server Administration Guide forinformation on specifying rules data sets and relatedprefixes. Correct the above problem, and restart.

AZK3929E Maximum ruleset count (count)exceeded

Explanation

SEF rule manager's internal list of SEF rulesets hasoverflowed. Too many SEF rulesets are defined.

User response

If the defined ruleset count exceeds the maximumsupported number of rulesets when the server isstarted, SEF initialization processing will abort. Afterstartup, the excess rulesets are immediately placedinto stopped/offline status.

AZK3930E RULESET rsname rsprefix errmsg1errmsg2

Explanation

SEF rule manager detected that the current rulesethigh-level qualifier is a duplicate of another high-levelqualifier.

User response

The current ruleset naming convention is incorrect.Ensure that the ruleset definition complies with thestandard code for product rulesets. Refer to theproduct Server Administration Guide for more details.

AZK3931E program dsname is too large -input buffer overflow

Explanation

SEF rule manager detected an input buffer overflow.The program is too large to be loaded in the currentbuffer.

User response

Check the current program for input size, and correctthat, if possible. Contact your local product systemsprogramming group for help.

AZK3932E service OF table FAILED, RC=rcode

Explanation

SEF rule manager could not setup the Product REXXexternal routine table. The GETMAIN failed.

User response

Determine why the GETMAIN of the required storageto create the above table failed. Check any MVSmessages for their return codes. Ensure that no exitslimit the acquiring of the given storage by any ASID.Review the current error text, and correct the problem.

AZK3933E ABEND IN CELL POOLPROCESSING DURING func


Explanation

An abend occurred during cell pool processinginitiated by the SEF rule manager.

User response

If the error occurred during a GET, check the productregion size. If the error did not occur during a GET,contact Software Support.

AZK3934E errdesc BE STORED IN RULESETrsname - ERROR FOUND FORrsname.rulename

Explanation

SEF rule manager found the current rule header notapplicable for storage in the current ruleset.

User response

Security rules can only be stored in the security ruleset(if security rules are found). Also, non-security rulescannot be stored in the security ruleset. Ensure thatthe current rule is stored in the appropriate rulesetenvironment.

AZK3935E CANNOT OPEN ddname (ABENDabcode AT modname+offset)

Explanation

During the open processing of the compiled rulelibrary, an abend occurred.

User response

Ensure that the given library is a PDS, similar bydefinition to the other product supplied pre-compiledlibraries. Check IBM message and codes manuals forthe abend code. Most likely, the member does notexist or the data set attributes are in error (sequentialDSORG or incompatibility in LRECL and BLKSIZE). If asystem 913 abend code is reported, data set accesshas been disallowed by your security subsystem.

AZK3936E cmdtype FAILED FORrsname.rulename - service OFddname FAILED

Explanation

The COMPILE or LISTCOMP SEF (cmdtype) commandfailed.

User response

Ensure that the given library is properly allocated.Also, ensure that the given library is a PDS, similar bydefinition to the other product supplied pre-compiled

libraries. Check IBM message and codes manuals forthe abend code. Most likely, the member does notexist or the data set attributes are in error (sequentialDSORG or incompatibility in LRECL and BLKSIZE). If asystem 913 abend code is reported, data set accesshas been disallowed by your security subsystem.

AZK3937E LISTCOMP FOR RULESET rsnameFAILED - NO RULES FOUND

Explanation

The LISTCOMP command for an individual rulesetfailed. No saved compile rule was found in thecompiled rule library.

User response

Ensure that the given ruleset for the LISTCOMPcommand is the valid one, and re-issue the command.

AZK3938E RULESET- rsname UNABLE TOACCESS COMPILED RULES

Explanation

The COMPILE, LISTCOMP, or DELCOMP SEF commandfailed.

User response

Ensure that a proper PDS was allocated to the XODSNkeyword of the ruleset specified. Special restrictionsapply to the SWIRULE ruleset, which cannot becompiled by a customer.

AZK3939E SEF COMPILE PROCESSING OFname FAILED

Explanation

The COMPILE, LISTCOMP, or DELCOMP SEF commandfailed.

name will be a rule name or a ruleset name

User response

This message should have been accompanied by othermessages.

AZK3940E AUTOENABLED FAILED - name ISA REXX EXTERNAL ROUTINE

Explanation

An AUTOENABLE command was issued for a memberof a ruleset that is actually a Product REXX externalroutine.

name will be a rule name or a ruleset name


User response

Verify your command. Re-issue the command, ifpossible.

AZK3941W SOURCE OF rulename MODIFIEDSINCE LAST COMPILE - SEF WILLUSE SOURCE

Explanation

SEF had detected that a compiled version of thecurrent rule exists. But, it detected that the sourceversion of the rule has been modified since the lasttime the rule was compiled. SEF will use the sourceversion of the rule for this enablement.

User response

You may want to re-compile the rule or auto-enable it,which also automatically saves the compiled version ofa rule.

AZK3942I NO ruletype RULES ENABLED INRULESET rsname

Explanation

This is a product SEF command LISTINST RULETYPE()informational or status report message. No rules of thetype specified are enabled in the ruleset.

User response

No action required.

AZK3943I There are no rules currentlyenabled

Explanation

SEF command LISTINST was unable to return rule orruleset statistics because there are no enabled rules.

User response


AZK3944I ruleinfo

Explanation

SEF command LISTINST ruleset.rulename producesone line for each enabled rule in the ruleset.

User response

The current message is for information purposes onlyand lists information about the enabled rule in theoutput area. No response is required to this message.

AZK3945I rsinfo

Explanation

SEF command LISTINST ruleset (with no rule names)produces one line for each enabled ruleset.

User response

The current message is for information purposes onlyand lists information about the enabled ruleset in theoutput area. No response is required to this message.

AZK3946I TYP PROCEDURE (set member)SET INVALID parmname VALUE OFparmval

Explanation

During initialization processing of a TYP eventprocedure, the REXX routine set an invalid parametervalue.

User response

The current message is for information purposes onlyand lists information about the enable attempt. TheTYP rule will not be enabled.

AZK3947I TYP EXECUTION MODULEmodname NOT FOUND FORvarname IN (set member)

Explanation

During initialization processing of a TYP eventprocedure, an invalid load module name was specified.

User response

The current message is for information purposes onlyand lists information about the enable attempt. TheTYP rule will not be enabled.

AZK3948W Too many sections found in ruleprocedure

Explanation

More than one process section was found in the rule.This restriction may be removed in future releases.

User response

At the present time, only a single process section maybe coded within a WWW or RPC rule.

AZK3949I ruletype WWW RULErsname.rulename ALREADYDEFINES THE URL val


Explanation

A duplicate URL criterion value (val) is specified onmore than one WWW rule at the same administrativelevel. Duplicate URL processing rules may only beactivated when one of the pair resides within themaster WWW ruleset and one resides in a subordinateruleset. In such a case, the master rule is alwaysprocessed before the subordinate rule, and thesubordinate rule is only processed when the masterrule is a header-only, generic rule. If the master rulecontains a procedural specification, such as a REXX,FILE, or PROGRAM section, the subordinate rule willnever be processed.

ruletype may be MASTER or SUBORDINATE

User response

Disable the duplicate rule before activating the currentrule, or change the URL criterion value in the currentrule to a unique value.

AZK3950I output

Explanation

SEF rule manager issued the current message to listthe data set statistics and status.

User response

The current message is statistical and lists the data setinformation. No response is required to this message.Check the PDS output listing, and make choicesaccordingly.

AZK3951E DDNAME ddname NOT ALLOCATED

Explanation

SEF rule manager attempted to open a data set for theprocessing of /*FILE sections. The data set could notbe opened because the ddname is unassigned.

User response

Ensure that the ddname specified in the message isallocated to a data set in the subsystem started taskJCL, or ensure that the correct ddname value has beenspecified within the /*FILE section header.

AZK3952E DDNAME ddname COULD NOT BEOPENED (rcode) additinfo

Explanation

SEF rule manager attempted to open a data set for theprocessing of /*FILE sections. The data set could notbe opened.

User response

Ensure that the ddname specified in the message isallocated to a data set in the subsystem started taskJCL, or ensure that the correct ddname value has beenspecified within the /*FILE section header.

AZK3953T msgtext

Explanation

The Web transaction invoked an ADDRESS SEFcommand for intermediate processing. The ADDRESSSEF command failed. Messages issued by theADDRESS SEF command are logged to the trace usingthis message ID.

User response

Examine the messages to see why the original /*FILErequest was rejected.

AZK3954E MEMBER member NOT FOUND INDATA SET ddname

Explanation

The indicated member was not found within thereferenced PDS data set. The file-related process isterminated with a member not found error.

User response


AZK3955E MEMBER member NOT FOUND INDATA SET ddname

Explanation

The indicated member was not found withinreferenced PDS data set. The file-related process isterminated with a member not found error.

User response


AZK3956I FILE ddname NOW status

Explanation

The indicated file has been placed online or offline, asthe message indicates.

status may indicate ONLINE or OFFLINE


User response

None. The message is traced to indicate /*FILE relatedactivation or deactivation of a shared PDS file.

AZK3957I output

Explanation

SEF rule manager issued the current message to listthe PDS member statistics.

User response

The current message is statistical and lists the PDSdata set member information. No response is requiredto this message.

AZK3958E ABEND abcode (rsn) IN modname+offset DURING servicePROCESSING, SOME FILES MAYNOT BE status

Explanation

An abend occurred during file open or close processingat initialization or termination time. Some files may nothave been processed.

User response

The initialization or termination process continues.

AZK3959I count of total shared data filesnow status

Explanation

During initialization or termination, this message isissued to indicate the results of file processing.

User response

No action is required, unless some files remainunopened at open time.

AZK3960E DSNAME dsname could not beallocated (rcode)

Explanation

SEF rule manager attempted to allocate a data set forprocessing of /*FILE sections. The data set could notbe opened.

User response

Ensure that the dsname specified in the messageexists, or ensure that the correct dsname value hasbeen specified within the /*FILE section header.

AZK3961I DSNAME dsname DDNAMEddname ALLOCATED

Explanation

The indicated dsname has been allocated to theindicated ddname.

User response

None. The message is traced to indicate /*FILE relatedallocation.

AZK3962I DDNAME ddname DEALLOCATED

Explanation

The indicated ddname has been deallocated.

User response

None. The message is traced to indicate ddnamedeallocation.

AZK3963I Generated DDNAME counter fieldrollover occurred

Explanation

The 8 byte counter field used to generate ddnamesrolled over.

User response

None. The message is traced to indicate a rollover ofthe 8 byte counter field used to generate ddnamesoccurred.

AZK3964E Member list not valid forsequential data sets DDNAMEddname, DSNAME dsname

Explanation

The member list function was issued for a sequentialdata set. The member list function is available only forpartitioned data sets (PDS or PDSE).

User response

Issue the member list function only for PDS or PDSEdata sets.

AZK3965T WARNING: OUTBOUND RESPDATA PRECEDES THIS FILEREQUEST - HTTP RESP PROTOCOLELEMENTS WILL BE UNUSABLE BYCLIENT


Explanation

When SWSFILE(SEND) or /*FILE was invoked totransmit a file to the HTTP client, the server found thatoutput data had previously been flushed fortransmission to the client. The server proceeds withthe file request after issuing this warning message.Because the server's file routines generate HTTPresponse protocol headers (such as Content-Type,Content-Length, Expires, etc.), any data precedingthese headers will LIKELY cause some unpredictableresult at the client. For example, the data sent by thefile routines may not be visible or interpretedincorrectly (i.e. the client may attempt to processHTML text as a GIF image), or the client may close thecommunications session.

User response

If the output which precedes the file request wasgenerated by a customer-written transactionprocedure, you can correct this condition byeliminating the preceding output, foregoing the useof /*FILE or SWSFILE(SEND) within the sametransaction, or ensuring that no SWSSEND(FLUSH)operation occurs.

AZK3966T External data queue full

Explanation

When an SWSFILE operation outputs its results to theexternal data queue (QUEUE and MBRLIST functions)and the external data queue fills before all of theinformation can be written, this message is traced.

User response

The current SWSFILE operation ends with return code28. Increase the size of the external data queue byspecifying the QUEUESIZE() override on the /*WWWheader statement.

AZK3967I dsname concat

Explanation

SEF rule manager issued the current message to listthe next concatenated dataset for a single shared-fileDD name or next concatenated dataset for an SEFruleset.

concat represents the concatenation index, relative to1

User response

The current message is statistical and lists the data setinformation. No response is required to this message.Check the PDS output listing, and make choicesaccordingly.

AZK3968I service FAILED. RETURN CODE:rcode

Explanation

SEF rule manager issued the message due to a failurein a system service.

User response

This problem is generated due to a file processingerror. Correct the file, and re-process your request.

AZK3969I FORMAT OF SHARED FILE BLOCKFAILED - INVALID IDENTIFIER val

Explanation

An invalid or unmatched identifier value (val) wasspecified for an internal FMTSFILE command. Eitherthe identifier was invalid or the corresponding sharedfile block no longer exists.

User response

The shared file block is not formatted and processingcontinues.

AZK3970E MATCH CRITERION MUST BEGINWITH /set - %2.%3

Explanation

During event procedure enablement, a WWW rule wasfound to be invalid because its match criterion doesnot begin with the specified string. All WWW eventprocedure match criteria must begin with the eventprocedure set name unless they are defined in themaster procedure set.

User response

Correct the error, and re-enable the event procedure.

The variable fields of the message text are: set nameof event procedure set

AZK3971E /*WWW STMT - errtext - %2.%3

Explanation

During event procedure enablement, a WWWprocedure header statement was found to be codedincorrectly. The procedure is not enabled.

User response


AZK3972E /*WWW STMT - key MAY ONLY BECODED WITHIN THE rule RULESET- %3.%4


Explanation

During event procedure enablement, a WWWprocedure header statement was found to be codedincorrectly. The indicated keyword may only be codedon header statements in the master WWW ruleset. Themaster WWW ruleset must be designated as such bycoding WWWCLASS(MASTER) on the DEFINE RULESETstatement that defines the ruleset.

User response


The variable fields of the message text are: keykeyword that is not valid rule name or description ofmaster WWW ruleset

AZK3973E /*REXX STMT - errtext - %2

Explanation

During event procedure enablement, a REXX sectionheader statement was coded incorrectly. Theprocedure is not enabled.

User response


AZK3974T RUNAUTH USERID userID - SETUPSUCCEEDED

Explanation

The RUNAUTH userid has been logged on to thesystem.

User response

No action is required. Processing continues.

AZK3975T RUNAUTH USERID userID -USERID INVALID

Explanation

The RUNAUTH userid could not be logged on to thesystem because the userid was invalid.

User response

The session is not permitted to proceed. The Webtransaction is rejected by rescanning to the SYSTERM/ERROR/500 URL, indicating a server error (with reasoncode 27). Correct the WWW rule that specified theinvalid RUNAUTH USERID.

AZK3976E DPRTY OPERAND operand - rsn

Explanation

The DPRTY operand value was invalid for the reasonspecified in the message.

User response

The WWW rule is not enabled. Correct the WWW rulewhich specified the invalid DPRTY operand, and re-enable it.

AZK3977T WWW task dispatch prioritychanged from val1 by val2

Explanation

The dispatching priority of the WWW transactionsubtask has been changed because a match to a /*WWW rule that specified the DPRTY() keyword hasbeen made.

User response

The WWW subtask continues using the new priorityvalue.

AZK3978T override OVERRIDE FAILED IN loc -RC=rcode AT addr

Explanation

A failure occurred while trying to override the REXXwork space or external data queue size. TheWORKSPACE or QUEUESIZE operand may be too large.

User response

The WWW subtask is re-routed to the system errorrecovery procedure, and the transaction aborted.

AZK3979E ATH LOGON rule must exit with'ACCEPT' if ACEE is created forsubtask

Explanation

An ATH logon procedure has caused the TCBSENVpointer for the current subtask to be set to a non-zerovalue. If an ATH logon rule creates an ACEE block, itmust also return with a code indicating that logonprocessing is complete. This prevents ACEE blocksfrom being inadvertently orphaned or destroyed byintrinsic server security processing.

User response

The entire logon request is rejected, and the logonrequest process is aborted with an S0C3 abend.

AZK3980E RUNAUTH USERID (userID) LOGONFAILED


Explanation

The RUNAUTH userID specified by theWWWDEFAULTRUNAUTH system parameter failedlogon processing during start-up.

User response

The HTTP-API initialization process is aborted. Checkto ensure that the userid specified by theWWWDEFAULTRUNAUTH start-up parameter iscorrect. Check the JOBLOG for related messagesabout the userID.

AZK3981I Default RUNAUTH USERID userIDlogged onto system

Explanation

The RUNAUTH userID specified by theWWWDEFAULTRUNAUTH system parameter has beenlogged on to the system.

User response

HTTP-API initialization processing continues.

AZK3982E INDEXED DELETE OFrsname.rulename (crit) FAILED(TRACE=tb) - RULE NOT DELETED

Explanation

The indicated rule could not be deleted from theindexes of the internal rule search tree. The rule is notdeleted, but it will be disabled.

crit represents the rule criterion

tb represents a trace back value

User response

If the error recurs, contact Software Support.

AZK3983E RULESET rsname action REJECTEDBY SEF - additinfo

Explanation

The indicated ruleset definition or modification(action) could not be processed into the SEFconfiguration.

User response

Correct the original request and resubmit.

AZK3984H SEF ruleset rsname SEFconfiguration action accepted

Explanation

The indicated ruleset definition or modification(action) was processed by SEF and placed into theactive configuration.

User response

None

AZK3985E XO DATASET dsname ERROR -additinfo

Explanation

An error was encountered while processing theindicated executable object (XO) dataset

User response

None

AZK3986E FILE ddname action REJECTED BYSEF - additinfo

Explanation

The indicated shared file definition or modification(action) could not be processed into the SEFconfiguration.

User response

Correct the original request and resubmit.

AZK3987H Shared file ddname SEFconfiguration action accepted

Explanation

The indicated shared file definition or modification(action) was completed successfully

User response

None

AZK3988E SEF task is terminating due tosevere configuration orenvironmental error with criticalresource

Explanation

The SEF subtask will self-terminate, causing the serverto shut down. A critical resource is not configuredproperly or an environmental error prevents access tothe critical resource. Generally, this means that adefinition, OPEN error, or rule auto-enablement errorhas occurred for a critical shared file or an ATH, TYP, orWWW ruleset with WWWCLASS(MASTER).


User response

Examine preceding message to determine theresource or definition which is missing, was undefined,or which cannot be accessed. Correct the start-updefinitions pertaining to the resource and restart theserver.

AZK3989W SEF RULE MGR ABEND abcodeREASON rsncode AT modname+offset WHILE PROCESSINGREQUEST plist

Explanation

The SEF rule manager trapped and recovered from anABEND at the location shown. The rule managerreturns the ABEND completion code to the servicerequestor, which must determine whether the error isof critical importance. The invoker may ignore,compensate for, or escalate the error, as appropriateto the request.

User response

Examine preceding and following messages todetermine the resource or definition which is missing,incorrectly configured or which cannot be accessed.Correct the SEF start-up definitions pertaining to theresource and restart the server.

AZK3990E /*FILE STMT - errtext

Explanation

During event procedure enablement, a /*FILE sectionwas not enabled due to the error given.

User response


AZK3991H SEF RULESET rsname DATASETdsname IS status

Explanation

The indicated ruleset dataset status has changed.

User response


AZK3992T SEF RULESET rsname DATASETdsname IS status

Explanation

The indicated ruleset dataset status has changed.

User response


AZK3993H SEF RULESET rsname DATASETdsname WAS STOPPED. RSN: rsn

Explanation

The indicated ruleset was stopped.

User response

This is an informational message. If the ruleset shouldnot be stopped, then review the Trace Browse andSYSLOG to determine what caused the ruleset to stop.

AZK3994T SEF RULESET rsname DATASETdsname WAS STOPPED. RSN: rsn

Explanation

The indicated ruleset was stopped.

User response

This is an informational message. If the ruleset shouldnot be stopped, then review the Trace Browse andSYSLOG to determine what caused the ruleset to stop.

AZK3998I data

Explanation

SEF rule manager uses this message to list formattedcontrol block output messages for shared files,represented here by data.

User response

These messages contain the formatted control blockimage.

AZK4000H errtext

Explanation

This is a general purpose message for certain VTAM®

errors.

User response

Not every condition reported by this message is reallyan error. Read the text of the message carefully todetermine whether an error has occurred or not. If anerror has occurred and you cannot resolve it, contactSoftware Support for assistance.

AZK4001H UNKNOWN service CODES - R0=R0R15=R15


Explanation

This message reports VTAM return and reason codes(R0 and R15) that are unknown to SAZK.

User response

This may indicate some type of internal error. It is alsopossible that you are running a version of VTAM that isnot yet supported by SAZK. If the version of VTAM thatyou are running DOES appear to be supported, contactSoftware Support.

AZK4002H UNKNOWN service CODES -RCPR=code1 RCSC=code2

Explanation

This message appears in conjunction with the 4001Hmessage.

code1 and code2 represent primary and secondary rplextension codes, respectively

User response

This may indicate some type of internal error. It is alsopossible that you are running a version of VTAM that isnot yet supported by the product. If the version ofVTAM that you are running DOES appear to besupported, contact Software Support..

AZK4003H service

Explanation

This message is used for tracing certain VTAM-relatedevents within the product.

User response

No action is required unless the trace messages areappearing without your requesting tracing.

AZK4004H service - luname

Explanation


User response

No action is required unless the trace messages areappearing without your requesting tracing.

AZK4005H service - lu/mode

Explanation


User response

No action is required, unless the trace messages areappearing without your requesting tracing.

AZK4006H VTAM APPLID NOT SET - LU 6.2SUPPORT NOT ACTIVATED

Explanation

The local VTAM applid has not been set. VTAMprocessing on this copy of AZK is impossible.

User response

The VTAM task of the main address space shuts down.This is not an error unless you actually did specify theVTAM applid in the xxxxxIN00 EXEC. Note that othercommunication protocols may be activated eventhough VTAM LU6.2 is not being used.

AZK4007H INVALID FMH-5 CONTROL BLOCKRECEIVED FROM luname

Explanation

An invalid FMH-5 control block was received from apeer LU (luname). The invalid FMH-5 block will beignored, and the conversation will be terminatedimmediately.

User response

This error will only occur if another product tries toestablish a conversation with the main productaddress. This error should be reported to whoever isresponsible for the other product.

AZK4010T TCB MODE SWITCH ERROR:errdesc additinfo

Explanation

An error was detected while switching from SRB toTCB dispatchable unit execution mode.

User response

The request to switch from SRB to TCB fails. The SRBmode routine generates an S0C3 ABEND if it cannotcontinue or continues processing in SRB mode, asindicated in the message.

AZK4012T SRB MODE SWITCH ERROR:errdesc additinfo

Explanation

An error was detected while switching from TCB toSRB dispatchable unit execution mode.


User response

The request to switch from TCB mode fails. The TCBmode routine generates an S0C3 ABEND if it cannotcontinue, or continues processing in TCB mode, asindicated in the message.

AZK4014T Shunting to mode execution modeprior to ABEND retry, retry GPR14in ABEND traces contains retrytarget address

Explanation

A retry is being attempted following an interceptedABEND. The dispatchable unit of work is currentlyexecuting in a different mode (SRB or TCB) than theretry routine expects. The server is transferringexecution into the correct dispatch mode, beforeretrying.

User response

This message is traced for ABEND retries only when ashunt to a different execution mode is required, andonly when tracing pause element dispatch activity. Thepreceding ABEND event trace records GPR14 retryregister contains the true target retry address, givencontrol after shunting.

AZK4015I count new SRBs scheduled withPRIORITY=CURRENT because noWLM enclave is joined

Explanation

This message is issued when a change is noted in thenumber of SRBs that have been scheduled withPRIORITY=CURRENT instead of the preferredPRIORITY=ENCLAVE option. This occurs when a taskis not joined to a WLM enclave at the time it schedulesan SRB. The SRB is scheduled with the same priorityas the scheduling task. This precludes execution of theSRB on the zIIP co-processor.

User response

No action is normally required. Some sites may receivethese notifications with regular frequency; other sitesmay rarely or never receive these notifications. If younote an increase in the number of these message,contact Software Support for further analysis.

AZK4016S FRR PARAMETER UNSTACKERROR - rsn

Explanation

This message is issued when a PC routine attempts tounstack and restore nested FRR parameters duringSRB-mode execution. The unstack operation has failed

because the state of the current FRR stack haschanged unexpectedly.

User response

The PC routine generates an S0C3 ABEND followingissuance of this message. Existing FRRs may receivecontrol and attempt to recover. The PC-call stackareas will not be recovered until check limitsprocessing re-activates them during periodicprocessing. Contact Software Support.

AZK4017T TYPE-1 LDU TERMINATION CALLERROR - failrsn additinfo

Explanation

An error was detected while terminating a Type-1Logical Dispatchable Unit construct used for TCB/SRBmode switches. The request for LDU termination isbypassed.

User response

The termination routine returns to the calling routine.This message serves as notification of a potential logicerror in End-of-Task cleanup processing since theroutine was entered to process LDU termination for asubtask that cannot support this kind of LogicalDispatchable Unit processing.

AZK4018I count New SRB schedule(IEAMSCHD) failures encountered

Explanation

This message is issued when a change is noted in thenumber of SRBs that were not scheduled, due tofailures returned by the IEAMSCHD service. The causeof these failures MAY be that the WLM enclave, intowhich the SRB is being scheduled, is no longer valid.

User response

Contact Software Support for further analysis.

AZK4019T Session lost (hung) due to type-4LDU schedule failure

Explanation

This message is traced if a TYPE-4 LDU cannot beconstructed or scheduled to close the communicationsession. The session is orphaned and remains hunguntil the server is recycled.

User response

Contact Software Support for further analysis.


AZK4020T DRDA processing bypassed forconnection to subsys, failrsn

Explanation

This message is traced if DRDA processing is beingskipped for the connection.

User response

The connection will be processing using standardRRSAF interfaces to the target Db2 subsystem.Contact Software Support for further analysis.

AZK4021T Generic (TLS) USERID userIDignored for DRDA connection

Explanation

This message is traced if a generic (TLS) userID hasbeen sent with the current SQL request message.

User response

Generic Userid (TLS) support is disabled when a DRDAbackend connection is in use. The generic userID sentby the client is ignored for Db2 processing. It will stillbe used when creating SMF log records, etc..

AZK4022T CONNECT TO DDF HOST=dom/ip,PORT=portno, CMIDADR=addrCMID=image

Explanation

This message is traced when a DRDA connection hasbeen successfully opened.

User response

None

AZK4023T calltype CALL TRACE: crlist

Explanation

This message produces a calling routine (crlist) trace

User response

None

AZK4024T Passticket generation failed forUSERID=userID, APPL=appl, withRC = rcode

Explanation

A passticket could not be generated for the indicateduserID and APPL name combination.

User response

Ensure RACF PTKTDATA class is activated and that aresource matching the APPL name is defined in theclass. The possible return codes are as follows: RC =x'04' - Invalid passticket parameter list RC = x'08' - NoPTKTDATA profile found for the APPL name RC = x'0C'- No task or address space ACEE found RC = x'10' -Caller is not authorized RC = x'14' - The PTKTDATAclass is not active

AZK4025S Metal-C function func in modulemodname not found, failrsn

Explanation

During initialization a Metal-c function requiringexternal visibility was not found.

User response

Initialization is aborted. DRDA processing in the servermay ABEND unexpectedly when the missing functionis invoked. Contact Software Support for assistance.

AZK4026I DRDA modules not loaded,Machine below architecture-9level, Found(lvl)

Explanation

During initialization the installed machine instructionset is examined to determine the corresponding XLC/C++ compiler architecture level. DRDA modules areonly provided to support machines at ARCH(9) leveland above.

User response

The DRDA processing modules are not loaded andDRDA support is disabled. MSG4020T withexplanation "Z196 (2817-xxx) INSTRUCTION SETREQUIRED" is traced if an attempt to open a DRDAconnection is made.

AZK4027T ind being issued to avoid DRDAidle thread time limit

Explanation

ind indicates that 1) A ROLLBACK is being issuedautomatically because the client ODBC/JDBC sessionhas been idle for an extended period. A ROLLBACK isissued to release PREPAREd statements so that theDRDA connection can be put into INACTIVE statebefore DRDA terminates the idle connection at the endof the IDTHOIN time limit. OR 2) , a SNDPKT (ping)request is being issued automatically becausetransmission of the current response to the client istaking longer than the DDF idle time limit. Exchanginga SNDPKT (ping) request/response reset the idle


connection time limit DRDA imposes on active but idleconnections.

User response

A ROLLBACK is issued once before awaiting additionalclient input. A SNDPKT request is issued periodicallywhile transmission of a large response to the client isunderway.

AZK4030T errdesc TCP/IP

Explanation

Setup of a new session failed for the reason reportedin the message. Normally, the failure is due to a lostconnection or timeout while attempting to receive thefirst part of the initial transmission. The initial setupdetermines if the session is being opened for HTTP orODBC/JDBC connections. The leading portion of themessage will indicate if the session was for HTTP orODBC/JDBC if this is known at the time of failure. Itwill also indicate if SSL encryption is in use for thesession when this can be determined. The client IPaddress is always included in the message which alsocontains an explanation of the failure that causedsession setup to fail.

User response

The connection to the client system is terminated. Theclient application will probably report an error. Checkfor any client system error messages and related tracemessages reporting communications or SSL problems.Often for a timeout, only a SELECT trace message willprecede this message. The SELECT completed with nosockets ready to receive, which is recognized as atimeout failure.

AZK4040E errdesc

Explanation

An error occurred processing a partner ACI session forthis connection.

User response

The session will be terminated.

AZK4041T service buffer size lgth1, addressaddr, length lgth2

Explanation

An error occurred processing a partner ACI session forthis connection.

service may indicate GET or FREE

The message contains two length values; lgth1represents requested buffer length, and lgth2represents returned buffer length

User response


AZK4042E Parallel I/O ACI processingdisabled

Explanation

An error occurred during initialization of ACI supportfor Parallel I/O processing.

User response

Parallel I/O processing is disabled.

AZK4043T errdesc additinfo

Explanation

MAP REDUCE was unable to process this VSAM dataset. If the VSAM KSDS is too small, it cannot besubdivided for parallel processing by ACI tasks. At aminimum, the VSAM KSDS must have two sequenceset records. The size of such a file will depend uponthe CI size of the index, and upon how keys getcompressed in the sequence set records.

User response

We recommend disabling MapReduce for the data mapfor this data set to eliminate the overhead of startingand stopping unneeded ACI processing tasks. TheVSAM file will be processed by a single task, and MAPREDUCE will not be used for this file.

AZK4044E Map Reduce processing disabled

Explanation

An error occurred during initialization of ACI supportfor MAP REDUCE processing.

User response

MAP REDUCE processing is disabled.

AZK4045E ACI FUNCTION func FAILED,RC=rcode errdesc

Explanation

An error occurred processing a MAP REDUCE ACIsession.


User response


AZK4046T errdesc additinfo

Explanation

An error occurred during processing of a MAP REDUCErequest.

User response

MAP REDUCE processing of this request is terminated.

AZK4047T tracedesc additinfo

Explanation

MapReduce is tracing information about the session.

User response

MAP REDUCE processing of this request continues.

AZK4048S BRFRSV unable to decrementOPDM active count. Servicename,class,service

Explanation

Service map for ACI service not found by free serverroutine Monitor ACI service to ensure that it does notreach Maximum Active servers.

User response

Schedule a restart of the Server at your earliestconvenience.

AZK4050E Invalid HTTP headers - errdesc -received from TCP/IP

Explanation

Invalid HTTP headers were received from a remotesystem. The invalid HTTP headers could not beprocessed.

User response

The connection to the client system is terminated. Theclient application will probably report an error. Checkfor any client system error messages. If the failurecontinues, contact Software Support.

AZK4051E SSL CONNECTION FAILED -errdesc - RECEIVED FROM TCP/IP

Explanation

A client application attempted to establish aconnection to the host using SSL. The connectioncould not be created for some reason related to SSLprocessing.

User response


AZK4052T name1 (name2,additinfo) - RV=rvalRC=rcode RE=rsncode

Explanation

An Unix System Services callable service request wasissued and the results were unexpected.

The message contains two name values; name1represents the callable service entry point name, andname2 represents the callable service formal name

User response

This message is traced to indicate an expected returnvalue or return code from a USS callable service.Subsequent processing depends on the call issued. Ifthe problem continues, contact Software Support.

AZK4053E OPTPIN timed out waiting for asession to be passed

Explanation

OPTPIN was placed in posted state in anticipation ofbeing passed a new connection, but the new sessionECB was never posted. The connection attempt isabandoned.

User response

This message is trace to indicate an expectedconnection was not successfully passed from thelistening task to the service task (OPTPIN). If theproblem continues, contact Software Support.

AZK4054T No data read from socket - errdesc- received from TCP/IP

Explanation

After 10 attempts to receive data( TCP/IP read) wereturned with zero bytes read and no indication of anykind of network error


User response


AZK4080T Invalid logon attempt by anunknown client detected,connection rejected.

Explanation

An attempt was made to logon by an unknown clientdriver. A connection to the server can only be made bya valid client driver. The connection is rejected.

User response


AZK4081T Insufficient storage reserve fortype (storamt) detected,connection rejected

Explanation

The storage reserve for the specified area type (LSQA,Private or EPrivate) has been exceeded. The currentattempt to connect to the host has been rejected. Thehost session will be terminated. The storage reservevalues are either calculated or set via productparameters.

User response

Contact Software Support for advice on this matter.

AZK4082T Maximum connected session limitis set to zero, server not acceptingnew connections

Explanation

The maximum connected session limit(CONCURRENTMX parameter) is currently set to ZERO.The server will not accept any new client connections.A limit of zero is normally set during a quiesce period,prior to shutdown, allowing existing client connectionsto complete their operations normally. Depending onthe setting of QUIESCESYSTEMTYPE, existing clientsessions will be cancelled (IMMEDIATE) or allowed toterminate normally (ATTRITION).

User response

Change the CONCURRENTMX parameter to a non-zerovalue if new client connections should be allowed.

AZK4083T SQL is not activated on the server.

Explanation

None.

User response


AZK4084T ODBC driver connections are notactivated on the server. Sessionrejected.

Explanation

None.

User response


AZK4085T Transaction Level Security is notactivated on the server. Sessionrejected.

Explanation

None.

User response


AZK4086T Network authentication is notenabled on this server. Sessionrejected

Explanation

A client application has attempted to connect to thehost using network authentication (SECU=YES), butthe server is not configured to allow networkauthentication.

User response

The server rejects the connection request.

AZK4087T Access to IDMS is not activated.

Explanation

None.

User response


AZK4088T Access to IDMS is not enabled, setthe desired APPC/IDMSinitialization parameters


Explanation

The product is not enabled for use with IDMS fromclient applications. The current request to use client toconnect to IDMS on the host has been rejected. Thecurrent host session will be terminated.

User response

If access to IDMS from client applications is needed,enable IDMS by setting the appropriate IDMSconnectivity parameters. You may use APPC/IDMS asthe transport for communication to IDMS from theproduct server address space.

AZK4089T STORED PROCEDURE CALLS ARENOT SUPPORTED WHEN USINGEXTENDED CURSOR POOLS(EXCU=YES).

Explanation

The product does not support stored procedure callswhen the client is connected to the server withextended cursor pool support enabled (EXCU=YES).

User response

Reconfigure the client to disable the extended cursorpool support (EXCU=NO).

AZK4090T Access to IMS/TM is not activated.

Explanation

None.

User response


AZK4091T Access to IMS/TM is not enabled,set the desired IMS/OTMA and/orIMS/APPC initializationparameters

Explanation

The product is not enabled for use with IMS/TM fromclient applications. The current request to use client toconnect to IMS/TM on the host has been rejected. Thecurrent host session will be terminated.

User response

If access to IMS/TM from client applications isneeded, enable IMS by setting the appropriate IMSconnectivity parameters. You may use either IMS/OTMA or IMS/APPC as the transport forcommunication to IMS from the product Serveraddress space.

AZK4092T Access to CICS is not activated.

Explanation

None.

User response


AZK4093T Maximum number of type (count)already connected, connectionrejected.

Explanation

None.

User response


AZK4094T Access to Adabas is not activated.

Explanation

None.

User response


AZK4095T Access to Adabas is not enabled,enable access by setting theADABAS parameter value to YES

Explanation

The product is not enabled for use with Adabas fromclient applications. The current request to use client toconnect to Adabas on the host has been rejected. Thecurrent host session will be terminated.

User response

If access to Adabas from client applications is needed,enable Adabas by setting the ADABAS productparameter to YES.

AZK4096T Access to VSAM is not activated.

Explanation

None.

User response


AZK4097T Access to IMS/DB is not enabled,enable access by setting theDBCTL parameter value to YES


Explanation

The product is not enabled for use with IMS/DB fromclient applications. The current request to use client toconnect to IMS on the host has been rejected. Thecurrent host session will be terminated.

User response

If access to IMS/DB from client applications is needed,enable IMS/DB by setting the DBTCL productparameter to YES.

AZK4098T No active started task copy of theproduct located

Explanation

The userid and password provided by the clientapplication can not be validated because there is noactive started task copy of the product. A started taskcopy of the product is required for userid andpassword validation if the client application isconnecting to a test copy of the product running underTSO. This error can only occur while attempting toconnect to a test copy of the host code running underTSO.

User response

The session is not permitted to proceed. Theinstallation must activate a started task copy of theproduct before connections to TSO copies of theproduct will be allowed to proceed.

AZK4099T CLIENT USERID userID1 UNEQUALTO TSO USERID userID2

Explanation

The userid provided by the client application is not thesame as the TSO userid running the test copy of theproduct. The connection attempt is rejected, and theconnection is severed. This error can only occur whileattempting to connect to a test copy of the host coderunning under TSO.

User response

The session is not permitted to proceed. The clientmust supply a valid userid/password combination (forthe host) in order for the session to proceed. Changethe client's userid to be the same as the TSO userid.

AZK4100E BIND WITH rtype rhost FAILED -NO MATCHING errdesc

Explanation

The bind with the remote system failed because thelocal and remote systems could not agree on certainAZK-to-AZK communication parameters.

User response

The bind process has failed. No communication withthe remote system is possible. Note that it is NOT aVTAM bind that has failed. The bind referred to by thismessage is a n AZK-to-AZK bind. Retry the process. Ifthe failure continues, contact Software Support.

AZK4101T Password validated for USERIDuserID from rtype rhost

Explanation

The userID/password combination from a remote (anduntrusted) client was successfully validated.

User response

No action is required. Processing continues.

AZK4102T LOGON attempt failed for USERIDuserID from rtype rhost

Explanation

A remote client was unable to connect for one of thereasons: (1) the userid/password combination may nothave been valid or (2) the System Event Facility (SEF)may have rejected the logon attempt.

User response

The session is not permitted to proceed. The clientmust supply a valid userid/password combination (forthe host) in order for a session to proceed. Ensure thatthe client's classification as untrusted is valid. If it isnot, use the ADDRESS AZK MODIFY LINK command tochange its status. If the client was rejected by theSystem Event Facility (SEF), the SEF ATH event logonrule may need to be modified.

AZK4103T msgtext

Explanation

This message is used to display any ACF2/RACFmessage that may have been created as a result of auserid/password validation. This form is used forsuccessful userid/password validations.

User response


AZK4104T msgtext


Explanation

This message is used to display any ACF2/RACFmessage that may have been created as a result of auserid/password validation. This form is used forunsuccessful userid/password validations.

User response

The session is not permitted to proceed. The clientmust supply a valid userid/password combination (forthe host) in order for a session to proceed. Ensure thatthe client's classification as untrusted is valid. If it isnot, use the ADDRESS AZK MODIFY LINK command tochange its status.

AZK4105E Bind failed - no matchingcompression type

Explanation

The bind with the remote system failed because thelocal and remote systems could not agree on acompression type.

User response

The bind process has failed. No communication withthe remote system is possible. Note that it is NOT aVTAM bind that has failed. The bind referred to by thismessage is an AZK-to-AZK bind. Retry the process. Ifthe failure continues, contact Software Support.

AZK4106E BIND FAILED - NO MATCHINGPOINTER ENCODING TYPE

Explanation

The bind with the remote system failed because thelocal and remote systems could not agree on a pointerencoding type.

User response


AZK4107E BIND FAILED - NO MATCHINGDATA ENCODING TYPE

Explanation

The bind with the remote system failed because thelocal and remote systems could not agree on a dataencoding type.

User response


AZK4108E BIND FAILED - NO MATCHINGAPPLICATION TYPE

Explanation

The bind with the remote system failed because thelocal and remote systems could not agree on anapplication.

User response

The bind process has failed. No communication withthe remote system is possible. Note that it is NOT aVTAM bind that has failed. The bind referred to by thismessage is an S__-to-S__ bind. Retry the process. Ifthe failure continues, contact Software Support.

AZK4109E BIND FAILED - NO MATCHINGPROCESSING FUNCTIONS

Explanation

The bind with the remote system failed because thelocal and remote systems could not agree onprocessing functions.

User response

The bind process has failed. No communication withthe remote system is possible. Note that it is NOT aVTAM bind that has failed. The bind referred to by thismessage is an S__-to-S__ bind. Retry the process. Ifthe failure continues, contact Software Support.

AZK4110S INVALID MODE DETECTED - LUluname ROUTINE routine

Explanation

The LU 6.2 processing routine detected an invalidmode string. The mode string cannot be used forfurther processing.

User response

Report the error to Software Support. The completemessage will be needed to diagnose the problem. Oneor more connection attempts may fail and have to beretried.

AZK4111S INVALID LU NAME DETECTED -ROUTINE routine


Explanation

The LU 6.2 processing routine detected an invalid LUname string. The LU name string cannot be used forfurther processing.

User response

Report the error to Software Support. The completemessage will be needed to diagnose the problem. Oneor more connection attempts may fail and have to beretried.

AZK4112T Usage restricted to oem.

Explanation

None.

User response


AZK4113T %1

Explanation

A connection is rejected for one of the followingreasons:

• The maximum number of concurrent users has beenreached.

• Some sort of virtual storage resource shortage hasbeen detected. The current request to connect to thehost has been rejected.

• A compressed buffer has been received on the portdesignated as the PIO port. PIO does not supportcompressed buffers. The connection has beenclosed.

User response

Depending on the message, either contact the personresponsible for administering the product server toexplore the possibility of raising the current maximumuser count or the product has detected that thecurrent virtual storage utilization is too high to allowadditional connections. Change to use the standardODBC port, or change the connection to senduncompressed buffers.

AZK4114T Dynamic SQL is not allowed by thisinstance of the server

Explanation

This instance of the product server is to be used forstatic-only Db2 applications. The dynamic SQL requesthas been rejected.

User response

Contact the person responsible for administering theproduct Server for the product Server(s) available thatsupport dynamic SQL.

AZK4115S SECONDARY USERID COUNT(count) EXCEEDS MAXIMUM (max)

Explanation

The actual number of secondary userids for thecurrent task exceeds the maximum number ofsupported secondary userids. Because of thisproblem, the secondary userid list can not be utilizedand the current session will be terminated.

User response:

AZK4116T Access to DB2 is not activated.

Explanation

None.

User response


AZK4117T Connection mode is not activated.

Explanation

None.

User response


AZK4118T Insufficient virtual storage isavailable to handle this session.Session rejected

Explanation

A client application has attempted to connect to thehost. Not enough virtual storage was available tohandle the session. The session was rejected andterminated by the host.

User response

The server address space does not have enough virtualstorage to handle the number of connections that arebeing directed to it. You can reduce the minimumstorage requirements using product parameters.However, this is not recommended. One of thefollowing solutions is recommended: (1) the amount ofvirtual storage per connection must be reduced, (2)the number of connections must be reduced, or (3) theload must be spread across multiple copies of theproduct.


AZK4119T REXX VARIABLE ERROR rcode1-fbcode rcode2 DURING FETCH OFvarname FOR SEF rule procedure

Explanation

The product REXX processor encountered a failureduring termination processing for a product REXXexec. A REXX variable value could not be fetched andreturned to the product's internal SEF routines duringthe termination process. Because a truncated ormissing value may cause critical errors within the ruleprocessing facility, the product generates an S0C3abend. The SOC3 abend forces termination of theproduct REXX interpreter. It also stops the processingof the current SEF rule in which the procedure wasdefined. NOTE: For SHVRET code X'01-(New/DroppedVariable), the most likely cause of this error is an EXITfrom a subroutine of the main Product REXXprocedure. If the subroutine contains a PROCEDURE{EXPOSE} statement, some or all of the server's built-in variables are hidden during EXIT processing and arenot available for post-REXX-execution interrogation bythe rule facility. Ensure that the product REXX routinedoes not deliberately specify an EXIT from an internalPROCEDURE. For other SHVRET error codes, the mostlikely cause of the error is an internal server error.

The message contains two return code values; rcode1represents the SHVRET return code value as defined inIRXSHVB control block for IRXEXCOM, and rcode2represents the R15 return code from IRXEXCOM.

fbcode represents a feedback code

User response

Check the REXX exec procedure and trace log for othermessages which may indicate the precipitating causeof the failure, and correct the problem(s). ContactSoftware Support if this procedure fails to resolve theproblem.

AZK4120T REXX VARIABLE varnameTRUNCATED FOR SEF RULE rule -SIZE (size) LONGER THAN MAXSIZE (maxsize)

Explanation

The SEF rule processor encountered a failure duringtermination processing for a REXX procedure. Thetermination time value assigned by REXX to a built-inserver variable is larger than the defined maximumsize allowed by the SEF facility. The variable istruncated to the maximum allowable size. Truncation,however, may cause additional, spin-off errorconditions to arise.

User response

Check the REXX exec procedure to see if a value wasassigned which exceeds the implementationmaximums for specific built-in variable.

AZK4121W service OF desc FAILED, RC=rcode

Explanation

SEF message processing encountered a failure in aproduct service routine. A particular instance of thisgeneric message may relate to a GETMAIN failure thatoccurs while attempting to allocate a REXX workspace. In this case, the return code indicates thereturn code from the storage management routine.

User response

Check the message related to the failure, and attemptto resolve the problem. In the case of a storageallocation failure, check for related MVS and productmessages. Also, ensure that your installation has anexit (e.g IEFUSI) that limits virtual storage allocation.If possible, correct the problem, and retry theoperation.

AZK4122W ABEND abcode AT modname+offset IN LINE lineno OF rule

Explanation

SEF event processing detected an abend. The currentrule processing request is terminated.

User response

Determine what caused the abend. External interrupts(like a job CANCEL) may cause an abend. Determine ifany product parameters limited the processing of thecurrent rule. Refer to the product ServerAdministration Guide and the product Server StartedTask Parameters book. Contact your local productadministrator for assistance.

AZK4123W SEF PROCESSING OF ruletypesearchID FOR jobname ABORTED

Explanation

SEF event processing routine detected an abend. Thecurrent rule processing request is aborted.

User response

Determine what caused the abend. External interrupts(like a job CANCEL) may cause the current rule to beaborted. If an ABEND occurred in the product, contactyour local product systems programming group forassistance. If an abend happened within a job, treat


this error as an environmental error. Correct or ignorethe current error, as applicable to your environment.

AZK4124W CANNOT language PROCEDUREprocname - %3 SECTIONS NOTENABLED

Explanation

The SEF event processing routine detected that a TYPrule that is referenced by another even procedure hasbeen disabled. The event procedure cannot be runbecause the TYP rule is currently disabled. Processingof the procedure is bypassed.

User response

Determine why the TYP rule is disabled, and re-enableit.

AZK4127E errtext FOR MESSAGE ID=msgID

Explanation

SEF event processing found too many compoundsymbols. The pattern match error is reported.Processing for the current rule is terminated.

User response

Check the exceeded compound symbol value, andadjust your rule code to it. Correct the above problem,and restart.

AZK4128E RULE rule SET varname TO ANINVALID cblk VALUE

Explanation

SEF event processing encountered an error inconversion of a character to an integer. Furtherprocessing is terminated.

cblk represents a control block field name

User response

Check the error text for the invalid input character datacausing this error. Remove or modify the invalid data,and restart.

AZK4129E errtext FOR ruletype RULE rule

Explanation

SEF event processing encountered too many internallygenerated compound symbols (security related), orthe length of one of the internally generatedcompound symbol names exceeds an internal productlimit. Further processing of this rule is terminated.

User response

This is an internal product error condition. Report thiserror condition to Software Support immediately.

AZK4130E Rule rule disabled for exceedingfiring limit of lim

Explanation

SEF event processing detected excessive firing of therule named in the message. As a result, the rule hasbeen disabled.

User response

If appropriate, increase the firing limit, and enable therule.

AZK4131E Rule rule has exceeded the SEFfiring limit of lim

Explanation

SEF event processing detected excessive firing of therule named in the message. The associated parameter,SEFLIMITDISABLE, indicates that the rule is not to bedisabled.

User response

This message is informational. No response isrequired. You may wish to code a message rule thatconditionally disables the rule.

AZK4132I User program modname not foundin library

Explanation

While enabling a rule specifying execution of a userload module, the system was unable to preload theindicated module. Enablement of the rule issuppressed.

User response

Verify that the module named in the rule actuallyexists within the user program load library or withinSTEPLIB.


Explanation

Some type of error occurred in a product serviceroutine. See the actual text of the message for anexplanation. The error was probably caused by afailure in an operating system service requested by aproduct service routine.


User response


AZK4135E SEF rule processor entered bycsect for invalid event type -typecode

Explanation

The SEF rule processing facility was invoked with aninvalid event type. This is probably an internal error.

User response

Check for other error messages that were generatedalong with this error message. Capture a copy of thetrace records, showing the TCB address, surroundingthe time of this error, and contact Software Support.

AZK4136E ABEND DURING cblk CONTROLBLOCK LOCATE - SEF RULEEXECUTION BYPASSED

Explanation

An internal control block could not be located prior toSEF event execution scheduling.

User response


AZK4137T ENTERPRISE AUDITING GENERICUSERID userID NOT DEFINED TOHOST SECURITY SYSTEM ORREJECTED.

Explanation

Enterprise Auditing was activated on the connectionand the client attempted to send the specified genericuser ID for authorization checking. However, the userID was not defined to the Host security system (ACF2,RACF or Top Secret) or was invalid for some otherreason.

User response

The session is not permitted to proceed. The clientmust supply a valid host user ID. Contact the

Installation Security Administrator to define or repairthe user ID.

AZK4138T ENCRYPTION METHOD CANNOTBE NEGOTIATED, HOST STORAGEUNAVAILABLE, BIND REJECTED

Explanation

This message is sent to client's when the requestedkey exchange and encryption method cannot besuccessfully negotiated at the host due to lack of hoststorage.

User response

The host rejects the encryption method requested bythe client. The client may continue without encryptionor may terminate the session.

AZK4139T BIND ENCRYPTION METHODREJECTED - method additinfo

Explanation

This message is traced when a client's requested keyexchange and encryption method cannot besuccessfully negotiated at the host during bindprocessing.

User response

The host rejects the encryption method requested bythe client. The client may continue without encryptionor may terminate the session. MSG4138T, MSG4142T,MSG4143T, or MSG4144T are sent to the client.

AZK4140T LOGON credentials cannot bedecrypted

Explanation

This message is sent to the client when logoncredentials cannot be decrypted. The client logon isrejected because the userid, password, and newpassword fields cannot be converted to clear text forprocessing. The client is operating using Diffie-Hellman key exchange and DES to encrypt the logonauthentication information.

User response

The host rejects the logon request by the client. Thehost traces MSG4146T with additional informationabout the decryption failure.

AZK4141T LOGON credentials rejected forVCF reconnect, new key exchangerequired


Explanation

This message is transmitted to the client when Diffie-Hellman logon credential encryption is in use for a re-connecting VCF session, and the VCF security artifactfor the VCF session has expired or been invalidated.

User response

The host rejects the logon request by the client. TheVCF client is obliged to repeat the full Diffie-hellmankey exchange, and re-transmit encrypted logoncredentials. MSG4145T is traced to provide additionalinformation about the problem encountered.

AZK4142T ENCRYPTION METHOD CANNOTBE NEGOTIATED, DIFFIE-HELLMAN MODULE NOT LOADED,BIND REJECTED

Explanation

This message is sent to client's when the requestedkey exchange and encryption method cannot besuccessfully negotiated at the host due to absence ofthe Diffie-Hellman key exchange and decryptionroutines.

User response


AZK4143T ENCRYPTION METHOD CANNOTBE NEGOTIATED, DIFFIE-HELLMAN KEY EXCHANGE FAILED,BIND REJECTED

Explanation

This message is sent to client's when the requestedkey exchange and encryption method cannot besuccessfully negotiated at the host due to failure ofthe Diffie-Hellman key exchange routine to calculate avalid shared secret.

User response


AZK4144T ENCRYPTION METHOD CANNOTBE NEGOTIATED, UNKNOWNENCRYPTION METHODREQUESTED, BIND REJECTED

Explanation

This message is sent to client's when the requestedkey exchange and encryption method cannot besuccessfully negotiated at the host. The requestedencryption method is unknown to the host.

User response


AZK4145T LOGON CREDENTIALS REJECTEDFOR VCID VCID, NEW KEYEXCHANGE REQUIRED, failrsn

Explanation

This message is traced when when client Diffie-Hellman logon credential encryption is in use for a re-connecting VCF session, and the VCF security artifactfor the session. has expired or been invalidated.

User response

The host rejects the logon request by the client. TheVCF client is obliged to re-inaugurate Diffie-hellmankey exchange and re-transmit encrypted logoncredentials. MSG4141T is sent to the client.

AZK4146T LOGON CREDENTIALS CANNOT BEDECRYPTED - failrsn

Explanation

This message is traced when a client's logoncredentials cannot be decrypted. The client logon isreject because the userid, password, and newpassword fields cannot be rendered in clear text form.

User response

The host rejects the logon request by the client.MSG4140T is sent to the client.

AZK4148T MISSING OR INVALIDPARAMETERS IN SQL CALL RULErsname.rulename ,failrsn

Explanation

This message is traced when an SQL CALL RULEcannot be processed due because not all theparameters were supplied or the parameters were toolong to fit in the new buffer.

User response

The updates to the SQL CALL statement are discarded.Correct the SQL CALL rule based on the reason given.


AZK4149T Connection from ipaddr TCP/IP,host name host, is usingunsupported driver version version

Explanation

A remote client connection is using a version of theproduct driver that is not supported by the server. Thisis an informational message. Transaction processingcontinues.

User response

You should upgrade the application driver to a levelthat is supported by the server.

AZK4150T desc addr size PLAN pln %SK

Explanation

This is a trace message that is produced whenever theTRACECURSOR parameter has been set to YES. Thismessage provides information related to the product'sSQL plist and status area.

User response

No action required.

The variable fields of the message text are: desccontrol block description addr address of the controlblock size size of the control block in hex pln the planname stack stack trace information

AZK4151T desc addr1 size DBRM dbrmCURSOR num1 DATA addr2 cntQUERY length num2 TYPE stmtFLAGS tf %SK

Explanation

This is a trace message that is produced whenever theTRACECURSOR parameter has been set to YES. Thismessage is used to trace the product's cursor controlblocks. There may be multiple cursor control blocksfor each product SQL plist.

User response

No action required.

The variable fields of the message text are: desccontrol block description addr1 address of the controlblock size size of the control block in hex dbrm theDBRM name num1 SQL section number addr2 firstdata block address cnt number of chained data blockslength total data row length num2 number of querycolumns stmt last prepared statement type tf traceflags stack stack trace information

AZK4152T desc addr size value1 value2 %SK

Explanation

This is a trace message that is produced whenever theTRACECURSOR parameter has been set to YES. Thismessage is used to trace the product's data blocks.There may be multiple data blocks for each productcursor block.

User response

No action required.

The variable fields of the message text are: desccontrol block description addr address of the controlblock size size of the control block in hex value1 nextoffset value (hex) value2 last offset value (hex) stackstack trace information

AZK4153T desc data length1 length2 col %SK

Explanation

This is a trace message that is produced whenever theTRACECURSOR parameter has been set to YES. Thismessage is used to trace the columns of the SQLDA.There may be multiple columns described by theSQLDA.

User response

No action required.

The variable fields of the message text are: desccontrol block description data type of data for thecolumn (integer) length1 length of the data in thecolumn (hex) length2 length of the column name(integer) col column name (up to 30 characters) stackstack trace information

AZK4154T desc addr1 size DBRM dbrmCURSOR num1 DATA addr2 cntQUERY length num2 TYPE stmtFLAGS tf %SK

Explanation

This is a trace message that is produced whenever theTRACECURSOR parameter has been set to YES. Thismessage is used to trace the release of a productcursor control blok.

User response

No action required.

The variable fields of the message text are: desccontrol block description addr1 address of the controlblock size size of the control block in hex dbrm theDBRM name num1 SQL section number addr2 firstdata block address cnt number of chained data blockslength total data row length num2 number of query


columns stmt last prepared statement type tf traceflags stack stack trace information

AZK4177T SQL tracing for RPC transactions isnot available

Explanation

SQL tracing for RPC transactions can not be performedbecause the Db2 DSNACAB module could not bevalidated.

User response

The product sets the TRACERPCSQL andTRACESQLERRORS parameters to 'NO'. ContactSoftware Support.

AZK4178W SQL tracing for RPC transactions isnot available

Explanation

SQL tracing for RPC transactions can not be performedbecause the Db2 DSNACAB module could not bevalidated.

User response

The product sets the TRACERPCSQL andTRACESQLERRORS parameters to 'NO'. ContactSoftware Support.

AZK4179W count New RPC tasks timed outbefore redispatch by RPCconcurrent execution facilty

Explanation

This message is issued when a change is noted in thenumber (count) of suspended RPC tasks that timed outbefore they were re-dispatched by the RPC concurrentexecution facility. Tasks suspended while awaitingtheir turn to execute an RPC program will re-awake ifnot re-dispatched within the time period set by theRPCSLEEPINTERVAL parameter. Tasks which re-awake due to a timeout may execute the RPC program,regardless the RPCMAX limit, or may bypass executionby generating a -438 error return code. The actiontaken is governed by the RPCSTALLACTIONparameter.

User response

No action is normally required and some sites mayreceive these notifications with regular frequency;other sites may rarely or never receive thesenotifications. If you note an increase in the number oftime out failures, check the active tasks display toverify that RPC programs are completing. This

message could indicate that one or more in-flight RPCprograms are stalled preventing new RPC programexecutions from being dispatched. Adjust the RPCMAXand/or RPCSLEEPINTERVAL parameter, as necessary,to prevent timeouts.

AZK4180S Invalid buffer received from aclient system

Explanation

This message is issued if an invalid communicationbuffer is received from a client system. The buffershould have contained a request for additional RPCdata. However, it did not contain such a request.

User response

The session fails. Retry the session. If the problempersists, check to see if there are other messages thatmay indicate another problem. If there are no othermessages, contact Software Support.

AZK4181S RPC DATA WILL NOT FIT INTOBUFFER

Explanation

This message is issued if an RPC data item of somekind will not fit into the communication buffer. Thiserror should never occur.

User response


AZK4182I percent percent of max concurrentRPC threshold achieved, value,value

Explanation

This message is produced once every 60 secondswhen the currently executing number of rpc's is equalto or greater than 80 percent of the max allowablespecified by RPCMAX parameter. The first value is themax number observed during the life of the server. Thesecond value is the observed value at the time of themessage.

User response


The variable fields of the message text are: valuecurrent percentage of max setting / value current maxsetting / value number concurrently executing


AZK4183I Max concurrent RPC executionless than value percent of maxsetting value, value

Explanation

This message is produced when the number ofconcurrently executing RPC's drops below the percentthreshold and message 4182 was previously issuedreporting that RPC executions exceeded thisthreshold. The percentage of RPCMAX at whichreporting occurs is set by RPCMAXMSGPCENT.

User response


The variable fields of the message text are: valuecurrent max setting value number concurrentlyexecuting value percent of RPCMAX to report(RPCMAXMSGPCENT)

AZK4184T ABEND CC=ccode RS=rsncodeDETECTED AT modname+offset BYRPC CONCURRENCY ROUTINEroutine recovery additinfo

Explanation

An ABEND was intercepted while one of theConcurrent RPC execution routines was in control.Information about the ABEND is logged in thismessage.

User response

The RPC concurrency routines may produce additionaltrace messages and/or produce an SDUMP in responseto the ABEND. They will recover and continue, ifpossible. The message may give an indication of therecovery action (recovery) to be taken or otherinformation identifying the cause of the ABEND.

AZK4185H RPC CONCURRENCY FACILITYSDUMP REQUEST RC=rcode,ASSOC TRACE MSGNO=msgno,STATUS AREA=addr

Explanation

This message is produced after an SDUMP request isissued by the concurrent RPC suspend/resume facility.A critical event was traced which has the SDUMP-requested attribute set causing the SDUMP request tobe made.

User response

None. The message reports the return code receivedfrom the SDUMP routine. A zero return code indicates

the SDUMP was processed or scheduled. A returncode of decimal 300 (hex X'0000012c') indicatesroutines were not authorized to request the SDUMP. Areturn codes of decimal 304 (hex x'00000130')indicates that the MAXSDUMPRATE flow rate limit inthe server suppressed the SDUMP because thefrequency of SDUMP requests exceeded the maximumof 5 per second. Non-zero return codes from SDUMPcontain the SDUMP return code in the low-order 2-bytes of the fullword and for return code 8, a reasoncode in the high-order 2-bytes of the fullword.

AZK4186I Max concurrent RPC allowed(RPCMAX) value exceeded.Suspending execution of RPC.

Explanation

This message is produced when the number of RPCsstarted exceeds the max concurrent RPCs allowedvalue specified by the RPCMAX parameter. The RPC isadded to the RPC execution suspend table and placedinto a wait state. When the number of concurrentlyexecuting RPCs drops below the max allowed, theoldest RPC in the suspend table is resumed.

User response


AZK4187I Max concurrent RPC allowed(RPCMAX) value within parametersetting. Execution resumes.

Explanation

This message is produced when a suspended RPC isresumed.

User response


AZK4188T RPCMAX TRACE SMTE CONTAINSINVALID TYPE code - ASSUMINGERROR/FFDC FOR CAPTURE

Explanation

The RPCMAX trace routine has been called with a traceSMTE element containing an invalid code.

code is a hex value

User response

The code is assumed to be for a recoverable orimminent error so that the SMTE is recorded as first-failure-data capture. This is probably due to a logicerror. Contact Software Support.


AZK4189H WARNING: count ADDITIONALtype EVENTS DETECTED BY RPCCONCURRENCY ROUTINES

Explanation

The RPCMAX routines have traced one or more (count)detected ERROR or ABEND events which have leftsome resource only partially recovered, indicate animminent failure of the RPC concurrency controls, orwhere not detected prior to an ABEND occurrence. TheRPC Concurrent execution limit facility may becomeimpaired, or now is, inoperable. The system issues thisconsole message when an ABEND is intercepted in theRPC routines, when heuristic checks indicate that anIMMINENT-FAILURE of the facility is likely occurring,or when an anomaly is detected for which only aPARTIAL-RECOVERY of resources can be predicted.Events of this type are always traced unlessRPCMAXTRACE has been set to NONE. This consolemessage is issued, no more frequently than once perminute, as an alert that the facility may be slowlydegrading, rapidly failing, or has already becomeinoperable. ABEND-INTERCEPT messages, unless veryinfrequent, likely are due to logic errors within thefacility; although these may occur infrequently if clienttransaction threads are killed manually or terminateabnormally for reasons unrelated to RPC programprocessing. FAILURE-IMMINENT messages, normallyare issued just before the facility becomes inoperablein order to log information which may be useful isdiagnosing problems. PARTIAL-RECOVERY eventsMAY indicate future facility failure if too manyresources cannot be eventually recovered. However,the system is unable to predictively determine, norlater confirm, whether resources being bypassed NOWwill eventually be recovered, or will remain inoperablepermanently. A few, intermittent PARTIAL-RECOVERYmessages with low event counts CAN represent amore or less normal operating condition for somesystem work loads. RPC termination, End-Of-Task, orcancelled-task cleanup may be lagging a bit behindmainline RPCMAX limit processing, rendering certainpredictive health checks unable to confirm that in-flight recovery actions will be able to completesuccessfully. However, a large count of PARTIAL-RECOVERY events, issued frequently, probablyindicates that resources are not being recovered in allcases. These event traces can be used to determinethe originating cause of a downward spiral in manycases.

type may be ABEND, FAILURE, or PARTIAL-RECOVERY

User response

If these messages appear frequently, or for anymessage reporting FAILURE-IMMINENT events, check

the state of the concurrent RPC execution facility,along with Trace Browse activity. The trace mayindicate the cause of a building problem early enoughthat it can be corrected prior to facility failure. If thefacility has become or is rapidly becoming inoperable,set the RPCMAX parameter to zero, which will turn offmost processing within the facility for new RPCexecution requests. If the cause of degradation orfailure cannot be corrected contact Software Support.For certain types of events, the system will generatean SDUMP of the product address space. SDUMPs aregenerated no more frequently than once per minute.Retain and forward the dumps to Software Support ifthe immediate cause of a problem cannot be resolveddirectly.

AZK4190E BIND WITH rtype rhost FAILED -NO MATCHING errdesc

Explanation

This message is produced when the local system isunable to negotiate a bind with the remote system.Note that this is not a VTAM bind. It is an AZKspecificbind.

User response


AZK4191E msgtext

Explanation

This message indicates a logon failure. The text of themessage is produced by the security package (RACF,ACF2).

User response

Check the text of the message to determine the causeof the logon failure. You may need additionalauthorization.

AZK4192T service - error - errdesc

Explanation

An error occurred while processing an ODBC request.

User response

This error message is a generalized message toidentify user interface errors.

The variable fields of the message text are: service1ODBC service being called (IMSTM, CICSEXCI)


service2 element/operation in error desc errordescription

AZK4193T Access to DB2 LUW is notactivated.

Explanation

None.

User response


AZK4200I host: cmd

Explanation

This message is issued as a result of a host commandbeing sent to the product REXX MESSAGEenvironment.

User response

This message is informational. No response required.

The variable fields of the message text are: host hostenvironment name string (message) cmd hostcommand insert

AZK4201E BIND WITH msgtext %2 FAILED -NO MATCHING %3

Explanation

This message indicates a logon failure. The text of themessage is produced by the security package (RACF,ACF2).

User response

Check the text of the message to determine the causeof the logon failure. You may need additionalauthorization.

AZK4233I Error sending message to externaldata queue

Explanation

An error has occurred while attempting to send aninformational record to the external data queue. Thismay be caused by a full external data queue.

User response

Contact your local product systems programminggroup for help.

AZK4240I Load balancing resumed for %1

Explanation

This message is issued when it is detected that theload balancing queue is no longer full and is onceagain eligible to receive sessions from a GroupDirector.

User response


AZK4250E msgtext

Explanation

This message is used to write out error messagesreceived from remote systems.

User response

Check the text of the message to determine the causeof the problem.

AZK4251E INVALID ADDRESS addr PASSEDBY PROGRAM progname

Explanation

This message is issued if an invalid address isdetected in the routine that copies data from a userprogram into the buffer that is sent to the remotesystem. The data at the specified address could not beaccessed.

User response

The program passing the invalid address to theproduct may fail or give incorrect results. Check theDb2 application program, and fix it if possible.

AZK4260E Client processing disabled

Explanation

An error occurred during initialization of ACI supportfor client program processing. Client programprocessing is disabled.

User response


AZK4261E ACI FUNCTION func FAILED,RC=rcode errdesc

Explanation

An error occurred processing a client ACI session.

User response



AZK4262E Server client is not activated onserver sysserv.

Explanation

None.

User response


AZK4263I Client processing is enabled.

Explanation

Client processing is enabled. Client initializationcompleted successfully and the client is ready toaccept new connections.

User response


AZK4265W Data Server Client bufferexpansion disabled due toauxiliary storage event

Explanation:An auxiliary storage event has been signaled, whereevent is one of: warning, shortage, or critical shortage.DS Client immediately stops expanding sharedmemory object buffers.

User response:Investigate the reason for the auxiliary storageshortage. Use the PAGEADD command to add auxiliarystorage.

AZK4266I Data Server Client servicesresumed.

Explanation:An auxiliary storage event has expired or has beenrelieved. DS Client will resume full services.

User response:No action is required.

AZK4267W Data Server Client refusing newrequests due to auxiliary storageevent

Explanation:An auxiliary storage event has been signaled, whereevent is one of: warning, shortage, or critical shortage.DS Client immediately stops accepting new requests.

User response:Investigate the reason for the auxiliary storageshortage. Use the PAGEADD command to add auxiliarystorage.

AZK4270H %1 SUBSYSTEM NAME NOT SET -%1 TCP/IP SUPPORT NOTACTIVATED

Explanation

The name of the OEM vendor TCP/IP subsystem hasnot been set. TCP/IP processing using this copy of theproduct is not possible using the OEM vendor's TCP/IPstack.

User response

The TCP/IP task of the main address space shutsdown. This is not an error unless you actually didspecify the TCP/IP subsystem name in the xxxxIN00exec. Note that other communication protocols (suchas OE SOCKETS TCP/IP) may be used even when theOEM Vendor TCP/IP interface is not in use.

AZK4271S SSL and non-SSL ports match -TCP/IP terminated

Explanation

SSL processing has been requested. However, the SSLport number is the same as the non-SSL port number.Interlink TCP/IP was terminated.

User response

Change either the SSL port number or the NON-SSLport number, and restart the product. The productparameter for setting the SSL port number isITCSSLPORTNUMBER. The product parameter forsetting the non-SSL port number is ITCPORTNUMBER.

AZK4272H vendor TCP/IP component FORSUBSYSTEM subsys status

Explanation

This message is used to indicate incompleteINTERLINK TCP/IP initialization.

User response

No action is required. When TCP/IP completesinitialization, AZK will complete its own TCP/IP-relatedinitialization.

AZK4273H protvend protcomp support isbeing activated

Explanation

This message is issued by each of the four availablecommunication protocol tasks when thecorresponding protocol support is being activated.


Other messages are issued if support for a particularprotocol is not being made active during start-up.

User response


AZK4274S Non-load balancing TCP/IP portmatches normal port or SSL port,server terminating.

Explanation

A non-load balanced TCP/IP port has been specified.However the port number is the same as the standardTCP/IP Port or the SSL Port.

User response

Change the port numbers so they do not match andrestart the product. The product parameter for settingthe SSL port is OESSLPORTNUMBER. The productparameter for the non- load balanced port isOENLPORTNUMBER. The product parameter forsetting the non-SSL port number is OEPORTNUMBER.

AZK4275I parmname reached -- at least oneprocess waiting

Explanation

This message is issued when a target thread limit wasreached in the prior checking interval. This means thatsome number of requests will have their processingdelayed until a subtask is freed by the completion ofanother request. This is not a serious error if ithappens infrequently. If response time complaintsoccur accompanied by these messages, the limitshould be raised.

User response

Raise the value of the indicated parameter.

AZK4276S no new process block dynamicallocation failures due to unknownreasons.

Explanation

This message is issued when a change is noted in thenumber (no) of process block dynamic allocationfailures. These failures will be noted when processblock dynamic allocation fails for reasons other thanstorage constraints. This is a serious error.

User response

The bypass is to pre-allocate a sufficient number ofprocess blocks during product initialization via thePROCESS parameter. This number can be determined

via the product ISPF panel (AZK Stats) C.4 and the"High water count" value in the "PC routines processblocks" section. Add 2 or 3 to this number, and use itas the initial PROCESS parameter value. For apermanent solution, contact IBM Software Support.

AZK4277S no new process block dynamicallocation failures due to storagerestraints.

Explanation

This message is issued when a change is noted in thenumber (no) of process block dynamic allocationfailures. These failures will be noted when processblock dynamic allocation is unable to obtain eitherprivate storage within the product address space orcommon storage within the extended common storagearea (ECSA). This is a serious error.

User response

The bypass is to pre-allocate a sufficient number ofprocess blocks during product initialization via thePROCESS parameter. This number can be determinedvia the product ISPF panel (AZK Stats) C.4 and the"High water count" value in the "PC routines processblocks" section. Add 2 or 3 to this number, and use itas the initial PROCESS parameter value. For apermanent solution, contact IBM Software Support.

AZK4278I no new process blocks allocated.Total process block count: total

Explanation

This message is issued when a change is noted in thenumber (no) of new process blocks that have beendynamically allocated. The message also displays thetotal number (total) of cross memory process blocks inthe pool.

User response

If the process block pool initialization count is set toolow, there may be a few of these messages during theearly portion of execution or during the first peakperiod of operation. This should be considered normaloperation. If these messages persist and the size ofthe process block pool continually rises, it is possiblethat process blocks are not being freed and placedback into the pool as they should. In this case, contactSoftware Support for further analysis.

AZK4279I no new RESMGR E-O-T cleanupfailures or stalls detected andcorrected


Explanation

This message is issued when a change is noted in thenumber (no) of MVS Resource Manager end-of-taskfailures or stalls that have been detected andautomatically corrected by the subsystem end-of-taskSSI intercept. Missing RESMGR EOT notificationsnormally occur only for connected TSO userids that (1)are cancelled with S622 abends (because the RESMGREOT intercept is not scheduled by MVS) or (2) do notexit/reenter a dialog (such as the trace display)between restarts of the main product address space.Undetected EOT events may indicate a more seriousproblem when they occur for subtasks executingwithin the main product address space.

User response

No action is normally required. Some sites may receivethese notifications with regular frequency; other sitesmay rarely or never receive these notifications. If younote an increase in the number of RESMGR EOTfailures, check the trace to locate DET events(TRACEDETACHEVENTS must be YES). Those entrieswhich contain the text EOT or EOM are of interest.Display the jobname and userid columns. If the failingDET events are not being recorded for TSO useraddress spaces, contact Software Support for furtheranalysis.

AZK4280T limtype TIME LIMIT EXCEEDEDFOR userid FROM nodetype NODEnode PLAN plan CNID connid TPprogname

Explanation

This message is issued when a task has exceeded awarning limit of some kind. The limit (limtype) mayhave been either a CPU time limit or a wait time limit.

User response

No action is required. However, an automatedresponse to this message may be needed.


Explanation

This message is issued when a task has exceeded anerror limit of some kind. The limit (limtype) may havebeen either a CPU time limit or a wait time limit.

User response



Explanation

This message is issued when a task has exceeded afailure limit of some kind. The limit (limtype) may havebeen either a CPU time limit or a wait time limit. Thetask is terminated with an abend.

User response


AZK4283T SMAF update failed for TCB addr1CMTC entry addr2 SMAF addr3

Explanation

This message is issued when an attempt to updateproduct limits in a SMAF block has failed for somereason. The update will not be performed. This errorwill normally only occur if the target task terminatedwhile an attempt to update the SMAF was underway.

User response


AZK4284S Process block pool is empty, sizeis poolsize

Explanation

This message is issued when the process block pool isfound to be empty. This can happen if all of theprocess blocks are in use or if process blocks are beinglost (allocated and not freed).

User response

This is a very serious error. Terminate the mainproduct address space as soon as possible, and raisethe number of process blocks using the PROCESSproduct parameter in the product initialization exec.The number of process blocks must be at least aslarge as the number of IMS/DRA threads plus 5. If theerror persists, contact Software Support for furtherassistance.

AZK4285S no process block allocationfailures have been detected


Explanation

This message is issued when a number (no) of processblock allocation failures are detected. This can happenif all of the process blocks are in use or if processblocks are being lost (allocated and not freed).

User response

This is a very serious error. Terminate the mainproduct address space as soon as possible, and raisethe number of process blocks using the PROCESSproduct parameter in the product initialization exec.The MINIMUM number of process blocks needed isthe number of IMS/DRA threads, plus 5. Note that thisis the minimum number required, and it does NOT takeinto account various volume-based request handling.If the error persists after increasing the PROCESSparameter value, or if process block release errors arealso being reported by the subsystem, contactSoftware Support for further assistance.

AZK4286S OPMS UPDATE FAILED FOR ALOGGING EXCEPTION LIMIT

Explanation

This message is issued when an attempt to updateproduct limits in the OPMS block failed for somereason. The update will not be performed. This errorwill normally occur only if a serious internal error hasoccurred. This error could occur if the product wasattempting to update a limit value at the same time theISPF interface was also being used to update a limitvalue.

User response

This is a very serious error. If the error persists,contact Software Support for further assistance.

AZK4287S no PENDING LOGGING REQUESTSFOUND FOR DATABASE subsys

Explanation

The number (no) of pending logging requests hasexceeded the product limit value. This message isissued to notify the operators of the system or anautomated operations product that the limit has beenexceeded.

User response

This is a serious error. The reason for the accumulationof pending requests must be determined and fixed.Some of the possible reasons include the Db2subsystem being down or errors accessing the Db2logging tables.

AZK4288S no pending logging requestscleared for database subsys

Explanation

All (no) of the pending logging requests for a databasesubsystem have been cleared and the associatedstorage has been released. This message is issued tonotify the operators of the system or an automatedoperations product that the pending logging requestshave been released.

User response

This is a serious error. The reason for the accumulationof pending requests must be determined and fixed.Some of the possible reasons include the Db2subsystem being down or errors accessing the Db2logging tables.

AZK4289S no SS-PC ENTRY FAILURESDETECTED, LAST: rsn AT time

Explanation

One or more (no) new failures were encounteredduring entry processing for the product's space-switchor stacking PC routine. Each new failure represents atransaction task or user interface request which couldnot be processed. Usually, these failures are due tothe inability of the product to obtain stack storagefrom its pool of pre-allocated cross-memory processblocks, and this message will be immediatelypreceded by message 4285S.

User response

If this message was preceded by message 4285S,terminate the main product as soon as possible, andraise the number of process blocks using the PROCESSproduct parameter, as described for message 4285S.If message 4285S does not precede this message orthe problem persists, contact Software Support forfurther assistance.

AZK4290E wstype GLOBAL VARIABLEWORKSPACE IS percent FULL(count OF total BLOCKS USED).PROGRAM=progname.

Explanation

The global (or temporary global) variable workspace,which contains global variables, has met or exceededthe warning threshold of blocks in use as defined bythe GLOBALWARNTHRESH (or GLOBALTEMPWARNTH)product parameter. This message will also be issuedevery time a new high-water mark that is at least 5%higher than the previous high-water mark is met orexceeded. The frequency at which this message is


issued is controlled by the GLOBALWARNINTVAL (orGLOBALTEMPWARNIV) product parameter. Note thatthe check that results in this message is only madewhen a new global variable is allocated or an existingglobal variable is expanded. The condition is recorded,and the message will be issued on the next referenceto a global variable. If no global variable referencesoccur, you may not be warned of this condition untilthe database is full.

User response

You may need to analyze the contents of the global (ortemporary global) variable database using the GlobalVariables application, and delete unused symbols. Ifthe global variable data set is too small, allocate alarger global variable DIV data set, and copy the oldone over to it using the access method services REPROcommand. Modify the product GLOBALMAX (orGLOBALTEMPMAX) parameter to indicate the largermaximum number of global variable blocks. Theprogram or rule.ruleset name in the message simplyrepresents the program running at the time thecondition was detected or at the time a deferredmessage was issued. This program may or may nothave caused a significant portion of the globalworkspace to be used.

AZK4291T additinfo

Explanation

This trace message is used for debugging purposesonly.

User response

None.

AZK4292E POSSIBLE wstype GLOBALVARIABLE WORKSPACEINTEGRITY PROBLEM DETECTED(errtype - flag). REBUILDSCHEDULED.

Explanation

An abend occurred while updating critical controlblocks in either the global or temporary global variableworkspace. The global variable workspace will berebuilt at the next checkpoint interval. Until the rebuildis complete, attempts to access or update globalvariables may possibly fail.

The error (errtype) may be SYNC or DELAYED.

flag represents the integrity flag byte, in hexadecimal.

User response

In most cases, no problem has actually occurred. Therebuild will simply validate and recover all of the data.If the 0180I messages associated with the rebuildindicate any loss of data, perform the following: (1)print any LOGREC software records created by theproduct, (2) print the relevant sections of the TraceBrowse leading up to the issuance of this message, (3)record the exact text of this message, and (4) contactSoftware Support for further assistance.

AZK4296S GLV subtask has terminated.Zeroing workspace pointers.

Explanation

During an attempt to access a global variable, it wasdetected that the global variable subtask had alreadyterminated. The workspace pointers will be zeroed toprevent any future attempts to access this data. Allfuture AZKVALUE or SWSVALUE requests will result inREXX error 48 (failure in system service).

User response

If the product does not shut itself down automatically,attempt to shut it down manually using the MVS STOPcommand. If the product still does not terminate,attempt to CANCEL it.

AZK4297S lock/unlock OF GLOBAL VARIABLEPOOL FAILED: HASN=asid1,PASN=asid2, SASN=asid3,MODE=mode, RC=rcode,CALLER=callername

Explanation

During an attempt to access global variable poolstorage, a failure in the lock or unlock serializationroutine was encountered. The current global variableoperation will be abandoned with a failure return code.The return code field will contain a non-zero value inbyte 3 if the SETLOCK or ENQ service failed. It willcontain a non-zero value in bytes 1 or 2 forenvironmental errors.

mode can be PROB or SUP.

User response

The current global variable pool operation is failed.Check for other messages which might indicate thecause of the error, and contact Software Support forfurther assistance.

AZK4298S GLOBAL VARIABLE lock/unlockRECURSION ERROR DETECTED ATaddr


Explanation

During an attempt to access global variable poolstorage, a failure in the lock or unlock serializationroutine was encountered.

User response

The current global variable pool operation is failed.Check for other messages which might indicate thecause of the error, and contact Software Support.

AZK4300I SEF command rejected -subsystem subsys is not active

Explanation

The current program or routine requires the services ofthe main product address space. However, the mainproduct address space is not active.

User response

Start or restart the main product address space

AZK4301S service - desc FAILED, RC=rcode

Explanation

This is a generic error message used to describe awide variety of internal errors that occur as a result ofcalling a product system management service.

User response

Record of all the information in the message text, andcontact Software Support.

AZK4302S ABEND abcode, RS=rsncode IN'ADDRESS hostenv' AT modname+offset, PSW=psw

Explanation

An abend occurred while the current program orroutine was using the services of the main productaddress space. The message provides a detailedexplanation of what type of abend occurred and atwhat location it occurred.

User response

Check the full text of the error message, and takewhatever corrective action is appropriate. For furtherassistance with this problem, contact SoftwareSupport.

AZK4303E SEF command timed out before allresponses received.

Explanation

The SEF command timed out after waiting for asignificant period of time without receiving thecomplete response from the SEF.

User response

Ensure that the product is still active. If the product isstill active, check the status of the SEF execute queueusing AZK/SWS. If there is a backlog of SEF requests,try to determine what caused the backlog, andattempt to resolve the problem. If the problem cannotbe resolved, contact IBM Software Support.

AZK4304E SEF COMMAND errdesc: cmdname

Explanation

An invalid SEF verb or an invalid SEF command hasbeen detected by the ADDRESS SEF environmentsyntax checker.

User response

Correct the syntax of the SEF command.

AZK4305E AZK/SWS version ver1 isincompatible with version ver2 ofsubsystem subsys.

Explanation

The version of the product that you are using in yourTSO environment is incompatible with the version ofthe product running in the main Server address spacerelated to the subsystem to which the SEF commandhas been addressed.

User response

Ensure that the correct product load library isallocated to your TSO environment, or address the SEFrequest to a copy of the product that is running the acompatible version.

AZK4307E SUBSYS SEF command cannot beissued in a rule

Explanation

The SUBSYS SEF command cannot be issued fromwithin an SEF rule environment

User response

Force this section of code to run in a server usingOPSREQ.

AZK4308E errdesc, RC=rcode


Explanation

Some type of service routine (operating system orproduct specific) failed. The error message identifiesthe type of error.

User response

Check the full text of the error message, and attemptto correct the error.

AZK4319T ABEND IN 'ADDRESS SWSSEND'CODE=ccode, REASON=rsncode ATaddr

Explanation

An abend occurred within the ADDRESS SWSSENDhost environment.

User response

Check for other errors that might explain the condition.

AZK4320H subsysid SEF CMDFROM(jobname,userid): cmd

Explanation

This message logs the use of SEF host commands tothe hardcopy console. The FROM keyword containsthe job name and user ID used for authorizationpurposes.

User response

No action required. This message is for informationtracking only.

AZK4321E CURRENT verb COMMAND NOTAUTHORIZED - errmsg

Explanation

Product REXX SEF command authorization checkroutine found that the current user is not authorized toexecute the SEF command. Access to the EXECUTEcommand is denied.

User response

Check the verb string of the error message text for thecommand whose access is denied. Ensure that thecurrent user has the required access. Contact yoursecurity systems administrator for further help, ifnecessary.


Explanation

An abend occurred in the authorization checkingroutine

User response


AZK4336E msgtext

Explanation

An SEF command was invalid or has failed for thereason indicated in the message.

User response

Correct and re-submit the SEF command.

AZK4337T THE TSO COMMAND IS INVALIDDUE TO errdesc

Explanation

A command passed to the ADDRESS TSO or ADDRESSTSOSRV environment is invalid for the reason given.The system rejects the command, with RC=-3indicating an invalid host command environmentcommand.

User response

Determine why the command was rejected, andresubmit the command.

AZK4338I TSO REMOTE EXECUTIONTIMEOUT VALUE SET TO time

Explanation

A GETTIMEOUT command was passed to theADDRESS TSO interface. This message is returned onthe external data queue as a response.

User response

None. The timeout value is given in 100ths of seconds.

AZK4339T environment COMMAND TIMEDOUT

Explanation

An ADDRESS TSO or ADDRESS CGI host command didnot complete within the allowed time. The requestingroutine is redispatched.


User response

Determine why the host command did not completewithin the required time frame. The delay could be dueto looping within the TSO/CGI command procedure orheavy usage of the external TSO servers.

AZK4340S Subsystem subsysid inactive, mustbe (re)started

Explanation

An ADDRESS TSO or ADDRESS TSOSRV host commandhas been directed to a product subsystem that is notcurrently active.

User response

Start or restart the product subsystem whosesubsystem ID appears in the message, or correct theprogram to specify the ID of an active productsubsystem.

AZK4341S TSO/E is not installed

Explanation

TSO/E (IBM's program product number 5665-293) isrequired to support the use of the product.

User response

Verify that this product is available at your installation.

AZK4342E TSO command length (length)exceeds maximum length(maxlength)

Explanation

The length of the TSO command exceeds theimplementation limits. Note that the length of TSOhost commands sent from SEF rules to the OSFexecute queue have a lower limit (256 bytes or theBLKSIZE on the server SYSTSIN DD statement,whichever is smaller).

User response

Check if there are an excessive number of blanks inthe TSO command string. If so, remove the blanksfrom the command string. If you need to pass longvalues from a rule to a server REXX program, useglobal variables to pass the values.

AZK4343S TSO service error - errdesc

Explanation

An error occurred in the product service routine thatexecutes TSO commands via the TSO commandservice routine.

User response


AZK4344S TSO service error - abcode1abcode2 - reason code rsncode

Explanation

An abend occurred in the product service routine thatexecutes TSO commands via the TSO commandservice routine.

User response

Check for other error messages that were generatedwith is error message. If the combined error messagesare sufficient to explain the problem, take whatevercorrective action is appropriate. If the problem cannotbe resolved, contact Software Support.

AZK4345S TSO service error - errdesc -reason code rsncode

Explanation

An error was detected in the parameter list passed tothe product service that calls the TSO commandservice routine.

User response


AZK4346E Current verbaddr command notauthorized - errmsg

Explanation

The authorization check failed. The use of ADDRESSOSF is restricted by your installation security product.


User response



Explanation


User response


AZK4348S rsrcname sysserv FAILED,RC=rcode, DETECTED AT addr

Explanation

Some type of error occurred during invocation of aproduct service routine associated with the ADDRESSTSO or ADDRESS OSF environment. The error occurredwhile attempting to set up the environment forexecuting a TSO command via the TSO/E commandservice routine.

User response


AZK4349S MESSAGE SEND TO TSO EXECUTEQUEUE FAILED, RC=rcode,DETECTED AT addr

Explanation

The product has attempted to send a command to theTSO server execute queue in a product Server addressspace, and the attempt has failed. If the return code inthe message is 4, then the TSO execute queue is full.Any one or some combination of the followingconditions may be true: (1) there is a rule or somecombination of rules that is looping, (2) there is a loopin an application that is causing TSO commands to beissued very frequently, (3) there are too few servers orthe servers may be tied up running relatively longprocesses, or (4) the TSO execute queue may be toosmall for your server workload.

User response

Review the contents of the message and anyassociated messages, and attempt to resolve theproblem. If the problem cannot be resolved, contactSoftware Support to obtain additional assistance.

AZK4350I Load for module modname failed,CCTL initialization error

Explanation

This message is issued if a module needed to initializethe CCTL interface to IMS could not be loaded. Themessage contains the module name. The module iseither missing or some other error has occurred.

User response

Check if any other messages were issued. Check if thenamed module is in the search sequence. Note thatthis problem can be resolved without restarting themain product address space.

AZK4351I DRA control exit invalid PAPLsubfunction = sfcd

Explanation

This message is issued when the product DRA controlexit receives notification of a DRA failure but is passedan unrecognized subfunction code.

User response

No action required. The product will attempt to restorea connection with the IMS control region. Note thatthis error message may be followed by other, moredescriptive error messages as the product attempts toreconnect to the IMS DBCTL.

AZK4352I DRA control exit invalid PAPLfunction = funcd

Explanation

This message is issued when the product DRA controlexit receives an unrecognized function code.

User response

No action required. The product will attempt to restorea connection with the IMS control region. Note thatthis error message may be followed by other, moredescriptive error messages as the product attempts toreconnect to the IMS DBCTL.

AZK4353I IMS CCTL support activated


Explanation

This message is issued when the product DRA controlexit receives a notification that the connection to theIMS control region has been established successfully.

User response


AZK4354I IMS CCTL support terminating

Explanation

This is an informational message that is issued whenthe product terminates its IMS CCTL support. If theIMS CCTL support is being terminated due to a fatalerror condition, this message will have been precededby error messages which depict the exact errorcondition encountered.

User response

Follow the course of action recommended for the errormessages that preceded this error message. If theproduct CCTL support continues to terminate due to afatal error condition, contact Software Support forfurther assistance.

AZK4355I IMS CCTL control exit resyncfailure

Explanation

The IMS CCTL control exit has been unable tosuccessfully process a resync request during productinitialization.

User response

Check the MVS system log for any IMS messagesoccurring around the time of this failure. Correct anyIMS problems that may have occurred. Then ABORTthe in-doubt UORs for this server. If the problemcontinues to persist, contact Software Support forfurther assistance.

AZK4356I IMS DRA terminating due tounknown error condition

Explanation

The IMS Data Resource Adaptor running inside of themain product address space has terminated due tosome unknown error condition. Product IMS supportwill be terminated.

User response

Check the MVS system log for any IMS messagesoccurring around the time of this failure. Correct anyIMS problems that may have occurred, and restart theAZK address space. If the problem continues topersist, contact Software Support for furtherassistance.

AZK4357I Invalid request, IMS CCTL featurenot enabled

Explanation

None.

User response


AZK4358I Request failed product notidentified to IMS

Explanation

The product has made one or more attempts identifyitself to the IMS DBCTL region, but the attempts havefailed. There is currently no active connection betweenthe product address space and the IMS DBCTL region.

User response

Check Trace Browse for any related productmessages. Check the MVS system log for any relatedIMS messages. Correct any IMS problems discovered.The product will continue to attempt to connect to theIMS region until a successful connection has beenestablished.

AZK4359I PSB psb schedule requestunsuccessful

Explanation

The product was unable to successfully schedule thePSB specified by the client application.

User response

Check the PSB name to ensure that it is correct. If theproblem continues to persist, contact SoftwareSupport for further assistance.

AZK4360I Request failed - PSB not inscheduled state

Explanation

The current request requires that a prior PSB scheduleattempt had completed successfully, and no activethread was found for this task.


User response

Check the program logic in the client-side applicationto ensure that the "CC" message was sent prior toissuing DL/I requests or the "TERM" message. If theproblem continues to persist, contact SoftwareSupport for further assistance.

AZK4362I Invalid buffer function code funcd

Explanation

The buffer function code passed to this routine wasinvalid. The host transaction program could not handlethe buffer function code passed by the client.

User response

Verify that the host application requested by the clientmatches the current call to the host. Contact SoftwareSupport for further assistance, if necessary.

AZK4363I Previous CCTL termination failed,initialization will use previoussession PAPLCTOK value

Explanation

This is an informational message that is issued duringproduct initialization when the CCTL initializationroutine determines that the previous CCTL terminationdid not complete successfully.

User response

No action is required. This message is forinformational purposes only.

AZK4370T Access to Services is notactivated.

Explanation

None.

User response


AZK4371T Services is not active on the server

Explanation

Services is not started on the server and cannot beused by client applications. The current request to useclient to execute a web service is rejected. The currenthost session will be terminated.

User response

If access to Services is needed, enable Services bysetting the correct parameters on the server.

AZK4372H WEB SERVICE %1 UNDERVIRTUAL DIRECTORY %2 HASBEEN %3

Explanation

A web service has been enabled or disabled.

User response

No action is required. This message is forinformational purposes only.

AZK4375W OE sockets WSOEPORT conflictwith PIO port - zervices HTTPlistener terminating

Explanation

The port number for OE Sockets Services (WSOEPORT)has been set to the same non-zero value as theparallel I/O port.

User response

This OE Sockets task of the main address space shutsdown. Startup continues without Services support.

AZK4376W MongoDB support services TCP/IPport(s) conflict with other portnumber assignments - Mongoterminating

Explanation

The port number(s) assigned for MongoDB serversupport conflicts with other non-zero port numberassignments for other product support services.

User response

The MongoDB listener task will terminate and Mongosupport will be deactivated.

AZK4377W MongoDB listener ports not set -MongoDB support willnot beactivated

Explanation

The port numbers for MongoDB client connectionshave not been set. MongoDB support, requested bythe MongoDB start-up parameter cannot be activated.

User response

The MongoDB listener task shuts down, and start-upcontinues without MongoDB support.

AZK4378W OE sockets HTTP port(WSOEPORT) conflicts with main


OE port (OEPORTNUMBER) - HTTPlistener terminating

Explanation

The port number for OE Sockets HTTP and Servicesaccess is set to the same non-zero value as the normal(ODBC) port. Services HTTP listener task will terminateand HTTP access to this server will be unavailable.

User response

This OE Sockets task of the main address space shutsdown. Startup continues without HTTP and Servicessupport.

AZK4379W OE sockets HTTP port(WSOEPORT) unset - HTTP &&Services support unavailable

Explanation

The port number for OE Sockets HTTP and Servicesaccess is un-set. Services Support, requested byWSACTIVE option, has been reset and will not beavailable. HTTP access to the server by the Studio willalso be unavailable.

User response

This OE Sockets task of the main address space shutsdown. Startup continues without HTTP and Servicessupport.

AZK4380E MongoDB feature is not configured- Mongo listener on port portno willnot be activated.

Explanation

None.

User response


AZK4381H Parallel I/O port OPEN failure

Explanation

An error occurred when trying to open a socket for theParallel I/O port.

User response

Verify that the port number is correct.

AZK4382H Non load-balanced port OPENfailure

Explanation

An error occurred when trying to open a socket for anon load-balanced port.

User response


AZK4383H OE sockets TCP/IP DubProcessfailed. RC=rcode. Reasoncode=rsncode.

Explanation

An error occurred when trying to set the DUBPROCESSoption for OE Sockets processing.

User response

Verify that the userid used to start the server has anOMVS segment defined. If this does not resolve theproblem, contact Software Support for additionalassistance.

AZK4384S Services load balancing port notunique, server terminating

Explanation

A load balancing Services port has been specified.However the port number is already used by anotherlistener such as the main TCP/IP listener, SSL, orregular Services.

User response

Change the port numbers so they do not match andrestart the product. The product parameter for settingthe SSL port is OESSLPORTNUMBER. The productparameter for the non- load balanced port isOENLPORTNUMBER. The product parameter forsetting the non-SSL port number is OEPORTNUMBER.The product parameter for setting the Services portnumber is WSOEPORT. The product parameter forsetting the Services SSL port number isWSOESSLPORT The product parameter for setting theServices balanced port number isWSOEBALANCEDPORT

AZK4385H WS load-balanced port OPENfailure

Explanation

An error occurred when trying to open a socket for aws load-balanced port.

User response



AZK4386S SSL port number required - OEsockets TCP/IP processingterminated

Explanation

SSL processing has been requested. However, the SSLport number has not been set or has been set to zero.OE Sockets was terminated.

User response

Set the SSL port number in the initialization exec, andrestart the product. If this does not resolve theproblem, contact Software Support for additionalassistance.

AZK4387S PIO and ODBC ports match - OEsockets PIO port is reset to zero

Explanation

PIO processing has been requested. However, the PIOport number is the same as the ODBC port number.The OEPIOPORTNUMBER is set to zero. Parallel I/Osupport will be disabled.

User response

Change the OEPIOPORTNUMBER to be different fromthe OEPORTNUMBER value.

AZK4388S SSL and non-SSL ports match - OEsockets SSL port is reset to zero

Explanation

SSL processing has been requested. However, the SSLport number is the same as the non-SSL port number.The OESSLPORTNUMBER is set to zero. The non-SSLport number will accept both SSL and non-SSLinbound requests.

User response

None required. To eliminate the message, remove theOESSLPORTNUMBER parameter from the initializationexec.

AZK4389S OE stack oestack can not be used -OE sockets TCP/IP processingterminated

Explanation

The name of a specific OE stack was specified usingthe TCPNAME product parameter. However, this OEstack cannot be used for some reason. OE Socketswas terminated.

User response

Correct the name of the OE stack by modifying theTCPNAME product parameter. Restart the mainproduct address space.

AZK4390E Invalid dynamic VIPA IP address%1 specified

Explanation

Dynamic VIPA support has been configured, howeverthe IP address specified for Dynamic VIPA support touse is not valid. Dynamic VIPA support will bedisabled.

User response

Either delete the Dynamic VIPA IP address or properlyspecify an IP address using dotted-decimal notation.

AZK4391I OE stack binding port portno to IPaddress ipaddr

Explanation

The Open Edition support is binding the product to theindicated port and the indicated IP address.

User response


AZK4392I OE stack returning invalid resultswhen sockets are ready

Explanation

This message is issued when the OE main task detectsthat select() returned a zero return value even thoughthere were sockets ready in the returned socket mask.This could lead to a loop occuring in OPMAOT trying toprocess a listening socket.

User response

Cyour sales representative for instructions ongathering documentation for this problem in IBM OpenEdition code.

AZK4393I OE stack returning too soon fromselect when no sockets are ready

Explanation

This message is issued when the OE main task detectsthat select() returned sooner than expected when atimeout value was specified and there were no socketsready for processing. This could lead to wasted time inOPMAOT when there is not work to do.


User response

Contact Software Support for instructions on gatheringdocumentation for this problem.

AZK4400T msgtext

Explanation

This is a general purpose message that may or may notindicate some type of TCP/IP error.

User response

Read the message text carefully. Some messagesproduced under this message ID are actually errormessages. If the message indicates an error, check forany associated TCP/IP produced error messages. Ifyou are unable to diagnose the problem, contactSoftware Support.

AZK4401W No TCP/IP port number specified.

Explanation

This message indicates that no port number wasspecified for the product to LISTEN for, and ACCEPTinbound OE Sockets TCP/IP sessions.

User response

Change the xxxxIN00 EXEC to specify a port numberfor the OEPORTNUMBER parameter which is used toLISTEN for, and ACCEPT all inbound OE SocketsTCP/IP sessions.

AZK4410E service OF desc FAILED RC=rcode,DETECTED AT addr

Explanation

This is a generic error message used to describe awide variety of message processing errors. Themessage text gives a description of the currentoperation (service) and what the current operation wastrying to do.

User response

Keep all the related error details, and contact yourlocal product systems programming group forassistance with this problem.

AZK4411E GLOBAL VARIABLE RULECHAINING DEPTH EXCEEDSMAXIMUM VALUE

Explanation

Global variable rule chaining has exceeded themaximum value. All pending global variable rules willnot be fired. The current operation continues.

User response

If this situation has been caused by a recursive infiniteglobal variable rule loop, modify the global variablerule to avoid this situation. If this situation is not dueto a REXX programming error, increase the globalvariable rule chaining limit (GLVCHAINMAX).

AZK4413I no MESSAGES SINCE THE LASTARCHIVE. CURRENT MESSAGENUMBER IS seqno

Explanation

The number (no) of messages added to Trace Browsesince the last Trace Browse message archived hasexceeded a user-defined threshold.

User response

This message may be used as a trigger for starting theTrace Browse archive program based on the number ofmessages since the last archive rather than on a timebasis using the TODARCH rule.

AZK4420H msgtext

Explanation

This is a general purpose message that may or may notindicate some type of ITC/IP error.

User response

Read the message text carefully. Some messagesproduced under this message ID are actually errormessages. If the message indicates an error, check forany associated ITC/IP produced error messages. Ifyou are unable to diagnose the problem, contactSoftware Support.

AZK4421H UNKNOWN service CODES - R0=r0R15=r15

Explanation

This message reports ITC/IP return and reason codes(R0 and R15) that are unknown to AZK.

User response

This may indicate some type of internal error. It is alsopossible that you are running a version of ITC/IP notyet supported by AZK. If the version of ITC/IP that you


are running DOES appear to be supported, contactSoftware Support.

AZK4422H UNKNOWN service CODES -ERCD=errcd DGCD=diagcd

Explanation


User response

This may indicate some type of internal error. It is alsopossible that you are running a version of ITC/IP notyet supported by AZK. If the version of ITC/IP that youare running DOES appear to be supported, contactSoftware Support.

AZK4423H UNKNOWN service CODES -ERCD=errcd DGCD=diagcd

Explanation


User response

This may indicate some type of internal error. It is alsopossible that you are running a version of ITC/IP notyet supported by AZK. If the version of ITC/IP that youare running DOES appear to be supported, contactSoftware Support.

AZK4450S jobname error inquiring CICSsystem information for client -EIBRESP: respcd

Explanation

The client PLTPI program encountered an errorinquiring CICS system information.

User response


AZK4451S jobname error enabling client exitprogram progname - EIBRESP:respcd

Explanation

The client PLTPI program encountered an errorenabling a client exit program.

User response


AZK4452S jobname error extracting GWAaddress for client programprogname - EIBRESP: respcd

Explanation

The client PLTPI program encountered an errorextracting the Global Work Area address for the exitprogram.

User response


AZK4453S jobname error starting client exitprogram progname - EIBRESP:respcd

Explanation

The client PLT program encountered an error startingthe user exit program.

User response


AZK4454I jobname client exit programprogname started

Explanation

The client task-related user exit program has beenstarted.

User response


AZK4455S jobname GWA length not asexpected for client exit programprogname - explength: explength,returned: GWA

Explanation

The GWA length returned by CICS for the client TRUEis not the expected length.

User response


AZK4456I jobname program creation date:date


Explanation

This message provides the creation date of the clientTRUE exit program.

User response


AZK4457S jobname Program load failed -EIBRESP: respcd

Explanation

The client API interface routine could not be loaded.

User response

Ensure that the load module is available to the CICSregion.

AZK4458W jobname client exit programprogname is already enabled

Explanation

The client PLTPI program encountered an errorenabling the client exit program. The program isalready enabled.

User response

Check that the PLTPI program has been correctlydefined to CICS.

AZK4459I jobname client exit programprogram is enabled

Explanation

The client PLTPI program is enabled.

User response

This is an informational message. No action required.

AZK4460I jobname Program GWA address:addr

Explanation

This message provides the address of the client TRUEexit's Global Work Area (GWA).

User response


AZK4470S IMS CCTL FEATURE MUST BEENABLED TO ISSUE DL/I CALLS

Explanation

None.

User response


AZK4471S INVALID PSB SCHEDULE ATTEMPT- PSB ALREADY SCHEDULED

Explanation

A user-written RPC program attempted to issue anIMS PCB call in order to schedule the program's PSB.However, the program's PSB is already scheduled.

User response

Correct the internal logic error in the user-written RPCprogram, and invoke the RPC program again.

AZK4472S PSB SCHEDULE FAILURE - PSBNAME = psbname

Explanation

A user-written RPC program attempted to schedulethe program's PSB. The PSB schedule attempt hasfailed.

User response

The PSB schedule may have failed for a variety ofreasons. Ensure that the PSB load module is availableto IMS. Ensure that the databases referenced by thePSB are available. Ensure that the PSB has not beenstopped by IMS due to an earlier error. If none of theabove conditions caused the error, check the IMS MTOlog and the MVS MCS console for any related errormessages. If all attempts to schedule the PSB fail,contact Software Support for further assistance.

AZK4473S INVALID DL/I CALL ATTEMPT -PSB NOT SCHEDULED

Explanation

A user-written RPC program attempted to issue anIMS term call in order to terminate the program's PSB.However, the program's PSB was not previouslyscheduled.

User response

Correct the internal logic error in the user-written RPCprogram, and invoke the RPC program again.

AZK4500U desc INITIAL GETMAIN FAILED -INCREASE STORAGE SIZE


Explanation

Insufficient storage. The product was unable to obtainenough storage to allocate the initial program stack.

User response

Check the abend code to determine if the region sizeshould be increased. If necessary, increase the regionsize, and restart the product.

AZK4501U desc UNABLE TO LOCATE THEMASTER BLOCK

Explanation

A subtask was unable to locate the product controlblocks and was forced to terminate. The servicesprovided by the subtask will not be available.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore abend error messages referring to the currentproblem. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact Software Supportwith this problem.

AZK4502H process subtask is active

Explanation

This is the standard subtask initialization message.

User response

This is not an error message, and no action is required.

AZK4503S ESTAE service ERROR RC=rcode

Explanation

The subtask driver attempted to create an ESTAErecovery environment. The ESTAE macro failed.

service may be create or delete.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore ESTAE error messages referring to the currentproblem. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact Software Supportwith this problem.


Explanation

Some type of error occurred in the systemmanagement routines of the product. See the actualtext of the message for an explanation. The error wasprobably caused by a failure in an operating systemservice requested by a product system managementroutine.

User response


AZK4505H ABEND abcode IN servicemodname+offset

Explanation

The subtask driver routine detected an abend in theroutine called by the driver. The message text providesthe abend code, current operation (service), and abendlocation. This failure may have been caused by aprogramming error in the routine that caused thesubtask exit to get control or in the subtask exitroutine itself. This failure can also be caused byproduct installation and maintenance errors.

User response


AZK4506H process subtask terminating

Explanation

This is the standard message indicating that subtaskexecution is complete.

User response

This is not an error message and no action is required.

AZK4507E SUBTASK ERROR TERMINATION:RC=rcode

Explanation

This message is issued when the subtask drivermodule terminates due to an error.


User response


AZK4508H subtask SUBTASK: objname objval

Explanation

This message is only issued when the product servicetask debugging is requested using the DEBUGATMDoption.

User response

No action required. This message is informational only.

AZK4520W LOAD FOR MODULE modnameFAILED, ODBA INITIALIZATIONERROR

Explanation

This message is issued if a module needed to initializethe ODBA interface to IMS could not be loaded. Themessage contains the module name. The module iseither missing or some other error has occurred.

User response

Check if any other messages were issued. Check if thenamed module is in the search sequence. Resolve theproblem and restart the server.

AZK4521S Unable to implant ODBA interface,return code: rcode

Explanation

This message is issued if the product was unable toimplant its ODBA interface routine. The return code isprovided.

User response

Check if any other messages were issued. CallSoftware Support.

AZK4522W UNABLE TO CONNECT TO IMS/ODBA FOR STARTUP TABLE ID:tblid, RETURN CODE: rcode,REASON CODE: rsncode, ERRORCODE: errcd

Explanation

This message is issued if the product was unable toconnect to IMS/ODBA for the Startup Table Identifierin the message.

Codes comes from AIBRETRN, AIBREASN, andAIBERRXT respectively.

User response

Check if any other messages were issued and IMS/DBis active. If the Startup Table does not exist, generateit. The next ODBA request for this startup tableidentifier will retry this operation.

AZK4523W ERROR IN DISCONNECTING FROMIMS/ODBA CONNECTIONS.RETURN CODE: rcode, REASONCODE: rsncode

Explanation

This message is issued if the product was unable todisconnect from IMS/ODBA.

Code comes from AIBRETRN, and AIBREASN.

User response


AZK4524W ERROR IN DISCONNECTING FROMIMS/ODBA CONNECTION tblid.RETURN CODE: rcode, REASONCODE: rsncode, ERROR CODE:errcd

Explanation

This message is issued if the product was unable toconnect to IMS/ODBA for the Startup Table Identifierin the message.

Codes come from AIBRETRN, AIBREASN, AIBERRXT.

User response


AZK4525I MAXIMUM NUMBER OFSIMULTANEOUS ODBACONNECTIONS (max) REACHED -no TIMES - CONNECTION DENIED


Explanation

This message is issued if the product was unable toconnect to IMS/ODBA because the maximum numberof simultaneous connections was reached a number(no) of times.

User response

Raise the MAXODBACONNECT parameter. Default is 8if it was not specified.

AZK4526I no ODBA CONNECTION ENTRIESFREED

Explanation

This message is issued if the product ODBAConnection Entry table cleanup routine was able tofree some previously allocated entries. This messageis a warning of a table full condition that will begindenying connections.

User response

Raise the MAXODBACONNECT parameter. Default is 8if it was not specified.

AZK4527T ODBA interface not type

Explanation

This message is issued if the product ODBA Interfaceis not either initialized or enabled.

type can be initialized or enabled.

User response

If it has not been initialized, contact Software Support.If it is not enabled, check initialization parameters.

AZK4528I Load for module modname failed,ODBA interface disabled

Explanation

This message is issued if a module needed to initializethe ODBA interface to IMS could not be loaded. Themessage contains the module name. The module iseither missing or some other error has occurred.

User response

If IMS/ODBA support is not desired, then no action isneeded. Otherwise check if other messages wereissued. Check if the named module is in the searchsequence. Resolve the problem and restart the server.

AZK4529W ERROR IN DEALLOCATING PSB:psb FOR STARTUP TABLE tblid

DURING ODBA/RPC CLEANUP. RC:rcode, RE: rsncode

Explanation

This message is issued if an RPC that was using theIMS/DB ODBA Interface terminated, left some PSBsallocated, and product cleanup encountered an errordeallocating them.

Codes come from ALERTDLI calls.

User response

Fix the error in the RPC that caused it to terminatewithout deallocating these PSBs.

AZK4530I IMS/DB ODBA INTERFACETERMINATED

Explanation

This message is issued when the product hasterminated the IMS/DB ODBA Interface.

User response

None.

AZK4531W ERROR TERMINATING IMS/DBODBA INTERFACE. RC: rcode, RE:rsncode

Explanation

This message is issued when the product hasterminated the IMS/DB ODBA Interface.

User response

None.

AZK4532S ODBA STARTUP TABLE MODULE -modname - IS NOT RE-ENTRANT.UNABLE TO MODIFY

Explanation

This message is issued when an IMS/ODBAConnection is requested, but the startup table moduleis not marked re-entrant. the product cannot modifythe module with server userid if required nor mergeDEFINE IMSODBA parameters.

User response

Re-generate the DFSxxxx0 module indicated and linkit as re-entrant.

AZK4533S ODBA MODIFY ACTION BYPASSEDFOR TABLE modname


Explanation

This message is issued when an IMS/ODBA ModifyAction is requested, but there does not seem to be anyactive ODBA connection under the name requested.

User response

Re-enter the Modify command with the proper StartupTable name.

AZK4534I req OF IMS/ODBA CONNECTIONFOR STARTUP TABLE modnameresolution

Explanation

This message is issued when an action on an IMS/ODBA connection is requested. The status of therequest is displayed. If the status is "failed" look forother messages that will indicate the return andreason codes.

resolution can be succeeded or failed.

User response

Re-enter the Modify command after dealing with theerrors indicated by the other messages.

AZK4550T OPRXSQ - USER useridCONNECTED WITH UNOPTIMIZEDPLAN plan

Explanation

This message is issued when a user connected with anold unoptimized OPRXSQ Db2 Plan.

User response

Rebind the specified plan so it includes the optimizedpackages OPRXSQA-R.

AZK4551T dbrm - UNRECOGNIZED typePROVIDED - SECTION stmtno -STATEMENT sectno

Explanation

This message is issued when an unrecognizedstatement or section number is provided to theOPRXSQ plan translation routine.

type can be either SECTION or STATEMENT.

User response


AZK4552T COLLECTION ID collname FORPLAN plan WILL USE PACKAGEPROCESSING

Explanation

This informational message is issued when the Db2collection name for the current connection has beendetermined.

User response

None

AZK4553T PACKAGE OPRXSQ dbrm SECTIONsectno1 USED FOR SECTIONsectno1 STATEMENT stmtno

Explanation

This informational message is issued when SQLsection number translation is done for the product Db2PLAN, OPRXSQ. This message will only be issuedunder the direction of Software Support.

Note that sectno1 represents the new OPRXSQ sectionnumber, and sectno2 represents the original OPRXSQsection number.

User response

None

AZK4554T PLAN plan DOES NOT USEPACKAGE PROCESSING

Explanation

This informational message is issued when the Db2plan does not have a collection name that matches thepackage list.

User response

None

AZK4555T PACKAGE OPRXSQ pkge INCOLLECTION collname SELECTED

Explanation

This informational message is issued when SQLsection number translation is done for the product Db2PLAN, OPRXSQ.

User response

None

AZK4556T PLAN plan WILL USE PACKAGEPROCESSING


Explanation

This informational message is issued to indicate thatthe optimized packages will be used to process Db2requests.

User response

None

AZK4557T PACKAGE OPRXSQ pkgeSELECTED

Explanation

This informational message is issued when SQLsection number translation is done for the product Db2PLAN, OPRXSQ.

User response

None

The variable fields of the message text are: packPackage name that will be used.

AZK4558T PLAN plan WILL USE DRDASUBSTITUTE PACKAGES

Explanation

This informational message is issued when the Db2plan will be internally converted to the use ofsubstitute packages for DRDA connections.

User response

None

AZK4601I status

Explanation

This message contains the first of each two-lineresponse to the TSOSRV_LIST command. Each two-line response group shows the status of the TSOserver and the command being executed.

User response

None.

AZK4602I cmdname

Explanation

This message contains the second of each two-lineresponse to the TSOSRV_LIST command. Each two-line response group shows the status of the TSOserver and the command being executed.

User response

None.

AZK4603I SERVER asid POSTED FORTERMINATION

Explanation

The TSOSRV_STOP command has posted the serverfor termination.

User response

None.

AZK4604I SERVER POSTED TO FREE TSSDAT addr

Explanation

The TSOSRV_FREE command has posted the serverfor release of the TSSD.

User response

None.

AZK4605I status

Explanation

The TSOSRV_QUEUE command returns informationusing this message.

User response

None.

AZK4606E ADDRESS SEF TSOSRV_STOP asid:ASID NOT SERVER ADDRESSSPACE

Explanation

An invalid hex ASID was specified on a TSOSRV_STOPcommand.

User response

Correct the ASID, and re-issue the TSOSRV_STOPcommand.

AZK4607S funcd OF queue FAILED, RC=rcode

Explanation

The specified function failed within the ADDRESS SEFhost command environment.


User response

Determine from the message text what function failed,and review the return codes for the failed function.Contact your local product systems programminggroup assistance.

AZK4608E ADDRESS SEF TSOSRV_FREEaddr: ADDRESS NOT THAT OF ATSSD

Explanation

An invalid address was specified on the TSOSRV_FREEcommand.

User response

Correct the address, and re-issue the TSOSRV_FREEcommand.

AZK4609I stats

Explanation

The TSOSRV_EXECSTATS command returnsinformation using this message.

User response

None.

AZK4612H jobname HAS RESET THE TSOSERVER COMMAND EXECUTIONQUEUE

Explanation

A TSOSRV_RESETQ command was issued from thespecified job.

User response:

AZK4650E UNABLE TO OBTAIN storsizeBYTES BELOW THE LINE

Explanation

ADDRESS LINKMVS is required to obtain storagebelow the 16MB line to hold both parameters and aregister save area to be passed to the requestedprogram. If this storage cannot be obtained, hostcommand processing is terminated.

User response

Batch jobs must be rerun with a larger below the lineregion size. TSO users must log on with a larger regionsize, and re-issue the command.

AZK4680T ENCLAVE SET RC=rcode FOR CALLCODE callcd (calltype) - failmsg

Explanation

While attempting to invoke a High-Level Language(HLL) subroutine via the MVS Language EnvironmentCEEPIPI interface module, an error occurred. Thismessage logs the error. This message may be followedby message 4681 for subroutine invocations.

failmsg is specific to a given call type.

User response

The HLL subroutine is not called, and the product'sLE/370 enclave may be terminated as indicated byother messages. If possible, determine the cause ofthe error using other messages logged, and correct theproblem, or contact Software Support group.

AZK4681T ROUTINE INVOKED WAS indexcd -subrout

Explanation

This message follows the 4680T message when asubroutine invocation was underway. The subroutineCEEPIPI table index value and its external name arereported.

User response

See message 4680T.

AZK4682T ROUTINE RC=rcodeREASON=rsncode ENCLAVEFEEDBACK(feedback)

Explanation

This message follows the 4681T message and reportsthe subroutines return code, reason code, and theLE/370 enclave feedback codes (feedback).

User response

See message 4680T.

AZK4683T ENCLAVE MGR CANNOT REENTERSUPERVISOR STATE

Explanation

Following a call to the LE/370 CEEPIPI routine, normalsupervisor state operation of the enclave managercould not be restored.

User response


AZK4684T ENCLAVE ABENDED CONDITIONCODE=ccode, REASON=rsncode


FOR CALL CODE callcd (calltype) -failmsg

Explanation

While attempting to invoke a High-Level Language(HLL) subroutine via the MVS Language EnvironmentCEEPIPI interface module, an abend was intercepted.This message logs the error. This message may befollowed by message 4681T for subroutineinvocations.

User response

The HLL subroutine is not called, and the product'sLE/370 enclave may be terminated as indicated byother messages. If possible, determine the cause ofthe error using other messages logged, and correct theproblem, or contact Software Support group.

AZK4685T api PLIST ERROR errdesc - plistval(data)

Explanation

While attempting to invoke a High-Level Language(HLL) callback routine, the callback routine detected aparameter list validation error. This message logs thereason for the plist validation error.

User response:An invalid plist return code is set by the API function,and return is made to the HLL program. ContactSoftware Support with this error.

AZK4686S msgtext

Explanation

A severe error message was logged to the trace by aHigh-Level Language (HLL) component of the mainproduct. The message is also logged to the operatorconsole using this message ID.

User response

See the contents of the message and the tracesurrounding this condition, and correct the problem.Contact Software Support with this error.

AZK4687T ENCLAVE TERMINATED BY COBOLSTOP RUN - CLIENT CONNECTIONTERMINATED

Explanation

A COBOL RPC program ended with a STOP RUNstatement which caused the LE enclave to terminate.

User response

Replace the STOP RUN statement with a GOBACKstatement and recompile and link the program.

AZK4700T %1 MODEL QUEUE NAME NOT SET- %2 USED AS MODEL QUEUE

Explanation

The name of the model queue for this qmanagerinstance has not been set. The default model queuewill be used, if possible.

User response

The MQ task will attempt to open the queue using thedefault model queue.

AZK4702T '%1' INPUT QUEUE NAME NOT SET- '%1' PROCESSING TERMINATED

Explanation

The name of the input queue for this qmanagerinstance has not been set. The default input queue willbe used, if possible.

User response

The MQ task will attempt to open the queue using thedefault input queue.

AZK4704H UNKNOWN service CODES -RE=rsncode RC=rcode

Explanation

This message reports IBM/MQ return and reasoncodes that are unknown to AZK.

User response

This may indicate some type of internal error. It is alsopossible that you are running a version of IBM/MQ notyet supported by AZK. If the version of IBM/MQ thatyou are running DOES appear to be supported, contactSoftware Support.

AZK4706T msgtext

Explanation

This is a general purpose message that may or may notindicate some type of IBM/MQ error.

User response

Read the message text carefully. Some messagesproduced under this message ID are actually errormessages. If the message indicates an error, check forany associated IBM/MQ produced error messages. If


you are unable to diagnose the problem, contactSoftware Support.

AZK4750T IDCAMS SYSPRINT: msgtext

Explanation

The IDCAMS utility has generated SYSPRINT output.The output line is given in the message text. IDCAMShas been invoked using the product's S_AZKRXIDinterface.

User response

None. The message gives the text of a SYSPRINT linegenerated by the IDCAMS utility.

AZK4751T IDCAMS WARNING: msgtext

Explanation

The IDCAMS utility has generated SYSPRINT output.The output line is given in the message text. IDCAMShas been invoked using the product's AZKRXIDinterface. The message is issued in response to anIDCxxxx message condition detected by IDCAMS.

User response

None. The message gives the text of a SYSPRINT linegenerated by the IDCAMS utility.

AZK4752T IDCAMS SYSIN: msgtext

Explanation

The IDCAMS utility is about to be invoked by theAZKRXID REXX interface program. This messagetraces the command text that will be passed to theIDCAMS utility.

User response

None. The message gives the command text that willbe presented to IDCAMS.

AZK4753T IDCAMS RESULTS: LASTCC=lstccCOMPCODE=ccodeREASCODE=rsncode

Explanation

The IDCAMS utility has completed. This messagereports the LASTCC, completion codes, and reasoncodes.

User response

None. The message reports the completion codes atthe end of the IDCAMS request.

AZK4800E DYNALLOC reqtype ddname -ABEND - COND=condcdREASON=rcode

Explanation

A DYNALLOC request failed due to an abend.

User response

The request fails. Check for other messages that mightindicate the cause of the failure.

AZK4801H cmdname command (issuedinternally) rejected - anotherrequest request is already running

Explanation

An internally generated SEF command cannot bescheduled at the present time, because the systemallows only one request of this type to be processed atonce.

User response

The system rejects the request and continues toprocess the in-flight request. Normally, this messagewould be issued infrequently (only in certain "race"conditions). If this message is issued frequently,contact Software Support for advice on setting serverstart-up parameters.

AZK4802H ABEND CC(condcd)REASON(rsncode) IN modname+offset WHILE PROCESSINGcmdname COMMAND ISSUED BYuserid

Explanation

An SEF command service processing subtask abendedwhile processing the indicated command.

User response

Check for other messages which might indicate thecause of this failure.

AZK4803E cmdname COMMAND FROM useridFAILED - RC = rcode desc ccode

Explanation

The SEF command service processing routine hasended with an error. The message reports thecommand being processed, the requesting MVSuserid, the service return code, and any abendcondition code encountered.


User response

Check for other messages which might indicate thecause of this failure.

AZK4804E Trace Browse archiving disabledbecause BROWSEMAX(val) valueis less than the minimum(minval)allowed

Explanation

Trace Browse archive support has been turned off,because the trace must contain at least the minimumgiven number of messages.

User response

When too few messages are supported in the trace, itcan wrap around before archives of the trace can becreated. This message indicates that the current tracecontains so few messages that this is likely to occur.Increase the BROWSEMAX start-up parameter valueto at least the minimum amount. Note that theminimum given is only a rough estimate and may beentirely insufficient to guarantee that wraparound willnot occur.

AZK4805H BROWSEARCHIVECOUNTparameter has been set to val -was below minimum (minval)allowed

Explanation

Trace Browse archive support has been turned on, butthe BROWSEARCHIVECOUNT parameter was not setor was set too low.

User response

The system recalculates the BROWSEARCHIVECOUNTvalue as one-third of the BROWSEMAX value.

AZK4806H BROWSEARCHIVECOUNTparameter has been set to val -was above maximum (maxval)allowed

Explanation

Trace Browse archive support has been turned on, butthe BROWSEARCHIVECOUNT parameter was set toohigh.

User response

The system recalculates the BROWSEARCHIVECOUNTvalue as one-third of the BROWSEMAX value.

AZK4807H BROWSEARCHIVECUSHIONparameter has been set to val

Explanation

Trace Browse archive support has been turned on, butthe BROWSEARCHIVECUSHION parameter was settoo high or too low.

User response

The system resets the BROWSEARCHIVECUSHIONvalue as indicated which is the minimum allowedvalue.

The variable fields of the message text are: valuecurrent BROWSEARCHIVECUSHION value

AZK4808S Archive backup is under stress -val messages can be logged beforeoverlay

Explanation

An archive backup of the trace currently cannot bescheduled because one is already underway.Wraparound trace recording has entered the finalrange of messages, and a wraparound will occurunless the previous archive completes in time for anew one to be scheduled.

User response

The system continues to monitor the status, eitherdeleting this message when the condition is correctedor escalating the severity if a wraparound actuallyoccurs. If some process is inhibiting the completion ofarchive backup processing in a timely manner, correctthe problem. Consider that the trace size(BROWSEMAX) and/or the archive control parameters(BROWSEARCHIVECOUNT andBROWSEARCHIVECUSHION) may need to be enlarged.

AZK4809S Trace Browse in overlay mode -unarchived records are beingoverwritten

Explanation

The trace log has wrapped around, and un-archivedmessages are now being overwritten. This messagereplaces the 4808S message if a stress condition isnot relieved.

User response

The system continues operating and monitoringconditions. This message is deleted if a new archivebackup that relieves the overall stress condition can


be completed; however, the overlaid records cannotbe recovered.

AZK4810H Trace 'BACKUP ARCHIVE'command should be externallyscheduled

Explanation

The BROWSEARCHIVE option is set to MESSAGE, andthe system has detected that a backup archive of thetrace should now be created.

User response

The system issues this message and takes no otheraction. You should immediately schedule an archivebackup operation.

AZK4811H Trace 'ARCHIVE BACKUP' is beingautomatically requested

Explanation

The BROWSEARCHIVE option is set to AUTO, and thetrace subtask is requesting a backup-type archive ofthe selected messages.

User response

The BACKUP ARCHIVE request is scheduled by theSEF subtask for asynchronous execution.

AZK4812E SEF INTERFACE SET RC=rcodeFOR cmdname COMMANDREQUEST ISSUED BY userid

Explanation

An internally generated SEF command was notscheduled due to an unexpected error in the commandprocessing interface routines.

User response

The SEF command is not scheduled. The commandrequestor continues.

AZK4813I cmdname command cannot bescheduled at this time - a similarrequest is already running

Explanation

An archive request has been made, but processing ofthe request cannot be scheduled at this time, becausea previous request of the same type has not yetcompleted. The system allows, at most, only onearchive backup/cleanup task to run, and, at most, onlyone user requested archive extract.

User response

None. Resubmit the request once the previous requesthas completed.

AZK4814I cmdname command cannot bescheduled at this time - all SEFservice subtasks are busy

Explanation

An archive request has been made, but processing ofthe request cannot be scheduled at this time, becausea subtask is not available to service the request.

User response

None. Resubmit the request once a subtask is free.

AZK4815I SEF service task, tskname,attached for cmdname - requestedby userid-reqorigin

Explanation

An asynchronous SEF service subtask has beenattached for processing of a long-running command.

User response

None.

AZK4816I Running: EFTK cbaddrRoutine:routine TCB addr USERIDuserid UTYPE reqtype ECB ecb CMDcmdname

Explanation

An ARCHIVE STATUS request has been issued. Thismessage is part of the response.

User response

None.

AZK4817I TRACE: CURRENTMSG msgnoLASTARCHIVED msgnoLASTTRIGGERED msgno DSNAMEword1 CTLS word2 %6

Explanation


word1 and word2 represent internal control words.

User response

None.


AZK4818E Processing of cmdname commandby subtask subtask terminated byE-O-T - RC=rcode

Explanation

An asynchronous command procedure subtask hasterminated unexpectedly while processing an SEFcommand. This message is sent to the requestor asnotification of the failure.

User response

Check for other messages which indicate the cause ofthe unexpected termination.

AZK4819T Service subtask subtaskcompleted processing of cmdnamecommand sent by userid -RC=rcode

Explanation

An asynchronous command procedure subtask hasterminated.

User response

None.

AZK4820E Processing of cmdname commandby subtask subtask terminated byproduct shutdown - RC=rcode

Explanation

An asynchronous command procedure subtask wasterminated forcibly by product shutdown. Thismessage is sent to the requestor as notification of theshutdown.

User response

None.

AZK4821T Service subtask subtask forciblydetached at shutdown - cmdnamecommand sent by userid -RC=rcode

Explanation

An asynchronous command procedure subtask hasforcibly detached during shutdown because it did notvoluntarily terminate operation quickly enough.

User response

None.

AZK4822H 'ARCHIVE BACKUP' processor hasbeen attached as an SEF servicesubtask

Explanation

A backup-type archive of the Trace Browse data hasbeen requested. The processor service routine hasnow been attached. Additional status and completionmessages will be logged to report the results of thebackup operation.

User response

None.

AZK4823H Archive file: DSN=dsname,FirstMsg=msgno, LastMsg=msgno,Count=count

Explanation

A new archive data set has been successfully created.This message logs the dsname, the first and lastmessage recorded in the archive, and the count ofmessages.

User response

None.

AZK4824H count messages beginning atnumber msgno cannot be backedup due to Trace wraparound

Explanation

A backup-type archive of the Trace Browse data hasbeen scheduled. The indicated range of messages(count) cannot be backed up because it has been, orshortly will be, overlaid by wraparound within thetrace.

User response

Processing continues. Check and adjust theBROWSEMAX, BROWSEARCHIVECOUNT, andBROWSEARCHIVECUSHION parameters to ensure thatthe trace does not wrap around without allowingbackup operations to complete. This message isnormal if you activate automatic archives against anexisting trace file that has been in use for some time.

AZK4825H NO WORK TO DO - ARCHIVESTARTING MESSAGE = msgno -ENDING MESSAGE = msgno


Explanation

A backup-type archive of the Trace Browse data hasbeen scheduled. There are no messages that cancurrently be backed up within the range allowed by theBROWSEARCHIVECUSHION value.

User response

Processing ends. Check and adjust the BROWSEMAX,BROWSEARCHIVECOUNT, andBROWSEARCHIVECUSHION parameters to ensure thatthe trace does not wrap around without allowingbackup operations to complete, or explicitly requestan ARCHIVE BACKUP, TOEND operation to bypassprocessing of the storage cushion value.

AZK4826W ARCHIVE PROCESSING ABORTEDDUE TO SUBSYSTEM OR SEFTERMINATION REQUEST

Explanation

An archive process is being aborted either because asubsystem shutdown is underway or because SEF hasrequested early termination of the procedure.

User response

Processing ends as quickly as possible. Some resourcecleanup may be deferred until subsystem restart.

AZK4827I msgdata

Explanation

The S_ARCHIV REXX procedure was executed whileperforming an archive allocation or cleanup service.The REXX routine produced trace or SAY messages.

The data in the message comes from SYSTSPRT.

User response

The messages produced by S_ARCHIV are logged bythis message.

AZK4828E procedure REXX PROCEDURERETURNED INVALID/INCORRECTRESULT FOR ARCHIVE DATA SETcalltype REQUEST

Explanation

The S_ARCHIV REXX procedure was executed but iteither did not return a result or it returned a result thatwas formatted improperly. The REXX procedure isassumed to have failed.

User response

The current archive-related operation is terminated.

AZK4829E procedure REXX PROCEDUREFAILED FOR calltype REQUEST -ROUTINE SET RETURN CODE TOrcode

Explanation

The S_ARCHIV REXX procedure was executed butreturned with a failure return code value set.

User response


AZK4830E procedure REXX PROCEDUREFAILED TO RETURN DATA SETNAME FOR calltype REQUEST

Explanation

The S_ARCHIV REXX procedure was executed butreturned without passing back an MVS data set name,as required for the sub-function request.

User response


AZK4831E DYNALLOC FAILURE - RC=rcodeERROR=errcd REASON=rsncodedesc

Explanation

Dynamic allocation failure occurred while building anarchive of the Trace Browse. The archival processterminates.

desc describes the DYNALLOC operation.

User response

Check other messages indicating the cause of thefailure.

AZK4832H Allocated: DDN=ddname,DSN=dsname - for archive output

Explanation

A ddname allocation was made for an archive outputlinear data set. Archive processing continues.

User response

None.

AZK4833H LDS dsname created for cmdnamecommand issues by userid


Explanation

An archive backup or extract procedure created a newVSAM linear data set for output. The actual IDCAMSdefinition was performed by the S_ARCHIV REXXroutine in SYSEXEC. This message logs the new clustername.

User response

None.


Explanation

This is a generic error message used to describe awide variety of archive data set initialization andtermination errors. The message text provides thecurrent operation (service) and what the currentoperation was trying to do, such as GETMAIN,FREEMAIN, ATTACH, and so on.

User response



Explanation

This error message describes errors that occurredwhile using the DIV (Data In Virtual) system service(service) during archive initialization, execution, ortermination. For a list of the return codes and reasoncodes from the DIV macro see the appropriate IBMdocumentation.

User response



Explanation

This error message describes an abend that occurredwhile using the DIV (Data In Virtual) system service

(service) during archive initialization, execution, ortermination. The abend codes and reason codes fromthe DIV macro are documented in the IBM manualz/OS Programming: Assembler Services Reference.

User response


AZK4837S Possible shortage of storage,storsize bytes required to buildarchive output data set

Explanation

This is a follow-up message to message 4834S when aGETMAIN has failed. This message indicates the size,in bytes, of the area requested by the GETMAIN.

User response

If the GETMAIN return code indicates insufficientstorage to complete the GETMAIN request, pleaseincrease your available storage (above the 16MB line)by the indicated amount.

AZK4838H Deallocated: DDN=ddname,DSN=dsname - for archive output

Explanation

A ddname deallocation was processed for an archivedata set.

User response

None.

AZK4839W Archive file: count invalid/overlaidmessages detected duringexecution

Explanation

While the archive data set was being created,messages were detected that had been overlaid orwere otherwise invalid.

User response

None.

AZK4840H CLEARARCHIVERECOVERYPARAMETER SET TO YES - IN-FLIGHT ARCHIVE archtypINFORMATION BEING CLEARED


Explanation

During subsystem startup, theCLEARARCHIVERECOVERY parameter was set. In-flight recovery information will be deleted for theindicated archive type.

User response

None. Recovery information is cleared unconditionally.

AZK4841H CLEARED BACKUP RECOVERYINFO - OUTDSN=dsnameMSGSTART=msgnoMSGCOUNT=countLASTARCH=msgno

Explanation

This message follows message 4840H and logs therecovery information that is being cleared.

User response

None.

AZK4842H CLEARED EXTRACT RECOVERYINFO - OUTDSN=dsnameMSGSTART=msgnoMSGCOUNT=count FORUSER=user

Explanation

This message follows message 4840H and logs therecovery information that is being cleared.

User response

None.

AZK4843I cmdname command from useridcompleted successfully

Explanation

The SEF command service processing routine hasended successfully.

User response

None.

AZK4844H Archive backup of trace hassuccessfully completed

Explanation

A checkpointing-type backup of the Trace Browse hasbeen completed successfully.

User response

None.

AZK4845H Trace: current message is msgno -count messages since last archive

Explanation

Trace Browse archiving is enabled. This message isproduced just before an archive request is generated.

User response

None.

AZK4846H Trace: last message archived wasmsgno - last requested formessage msgno

Explanation

Trace Browse archiving in enabled. This message isproduced just before an archive request is generated.

User response

None.

AZK4847I cmdname CMD NOT SCHEDULED -DUPLICATE %2 CMD RECOVERYNOT COMPLETED

Explanation

An SEF service request cannot be processed becauseinternal controls indicate another operation is alreadyin-flight. However, no subtask is currently processingthe request. This error can occur when certaincommands fail and require separate recoveryprocedures to be scheduled. For brief moments, a"race" condition may occur, where the recoverycommand has priority.

User response

Wait until the previous process is recovered. If thecondition persists, manually request recovery.

AZK4848H cmdname CMD NOT SCHEDULED -DUPLICATE %2 CMD RECOVERYNOT COMPLETED

Explanation

See message 4847I. This message is hard-copied forinternally issued requests.

User response

See message 4847I.


AZK4849I PARAMETERS: OPTION parval1COUNT parmal2 CUSHION parval3

Explanation


The parmval values represents BROWSEARCHIVE,BROWSEARCHIVECOUNT, andBROWSEARCHIVECUSHION values, respectively.

User response

None.

AZK4850I desc TYPE archtyp USER useridSTARTMSG msgno MSGCOUNTcount DSNAME dsname

Explanation

An archive status request has been issued. Thismessage is part of the response.

User response

None.

AZK4854E THE DIV OBJECT, dsname,CANNOT BE MAPPED - THEVERSION CODE (%1) ISBACKLEVEL AND INCOMPATIBLE

Explanation

The archive data set review request cannot beserviced because DIV reports one size for the objectbut LISTCAT reports another.

User response


AZK4855E THE DIV OBJECT, dsname,CANNOT BE MAPPED - THE HI-USED-RBA code IS LESS THANTHE DIV-ACCESS PAGE COUNTsize RETURN VALUE

Explanation

The archive data set review request cannot beserviced because DIV reports one size for the objectbut LISTCAT reports another.

User response


AZK4856E THE DIV OBJECT, dsname,CANNOT BE MAPPED - THE DATA

SET CONTROL AREA (BOST) ISINVALID

Explanation

The archive data set review request cannot beserviced because the first page of the linear data setobject does not contain required control information.

User response

The probable cause of this error is that you areattempting to review an archive data set that is stillbeing created or that was not closed properly.

AZK4857E THE DIV OBJECT, dsname,CANNOT BE MAPPED - THE DATASET CONTROL AREA SIZEINFORMATION (size1/size2) DOESNOT MATCH THE DIV OPEN STATS(size3/size4)

Explanation

The archive data set review request cannot beserviced because the first page of the linear data setobject does not contain control information thatmatches the size information returned by DIV.

Note that size1 and size3 are in bytes, which size2 andsize4 are in pages.

User response


AZK4858E THE DIV OBJECT, dsname,CANNOT BE MAPPED - THE DATASET CONTROL AREA pointerPOINTER (ptrval) IS renALIDbaseptr/count

Explanation

The archive data set review request cannot beserviced because the first page of the linear data setobject does not contain control information that isstructurally correct.

User response


AZK4859I Archive reset command issued byuserid has changed last-archivedmessage from msgno to msgno


Explanation

An ARCHIVE RESET command has been processed.

User response

None.

AZK4860T ARCHIVE FILE: DSN=dsname,FIRSTMSG=msgno,LASTMSG=msgno, COUNT=count

Explanation

A new archive data set has been successfully created.This messages logs the dsname, the first and lastmessage recorded in the archive, and the count ofmessages. This message is a duplicate of 4823 (usedfor tracing).

User response

None.

AZK4861I statement

Explanation

An ARCHIVE STATUS request has been issued. Thismessage is part of the response. This message isrepeated up to eight (8) times. The server constructs amodel IDCAMS DEFINE CLUSTER statement usingconfigured parameters. You can review this statementto ensure that the configuration parameters are setcorrectly. The statement reported in this message isused to define archive backup files.

User response

None.

AZK4862I statement

Explanation

An ARCHIVE STATUS request has been issued. Thismessage is part of the response. This message isrepeated up to eight (8) times. The server constructs amodel IDCAMS DEFINE CLUSTER statement usingconfigured parameters. You can review this statementto ensure that the configuration parameters are setcorrectly. The statement reported in this message isused to define archive extract files.

User response

None.

AZK4863I parmval1, parmval2, ... parmval5

Explanation

An ARCHIVE STATUS request has been issued. Thismessage is part of the response. This message reportsthe output data set allocation related parametervalues set for building archive backup data sets.

parmval's 1-5 represent the values ofARCHIVEDSNPREFIX. ARCHIVEDATACLASS,ARCHIVEMGMTCLASS, ARCHIVESTORCLASS, andARCHIVEDEFCLPARMS respectively.

User response

None.

AZK4864I parmval1, parmval2, ... parmval5

Explanation

An ARCHIVE STATUS request has been issued. Thismessage is part of the response. This message reportsthe output data set allocation related parametervalues set for building archive EXTRACT data sets.

parmvals 1-5 represent the values ofEXTRACTDSNPREFIX, EXTRACTDATACLASS,EXTRACTMGMTCLASS, EXTRACTSTORCLASS, andEXTRACTDEFCLPARMS respectively.

User response

None.

AZK4865E Trace Browse archiving disabledbecause 'ARCHIVEDSNPREFIX'parameter is not set

Explanation

Trace Browse archive support has been turned offbecause the output data set name prefix parameterARCHIVEDSNPREFIX is not set. A data set name prefixis required.

User response

Note that you can review and possibly set values forthe following archive data set allocation relatedparameters: ARCHIVEDSNPREFIX,ARCHIVEDATACLASS, ARCHIVEMGMTCLASS,ARCHIVESTORCLASS, and ARCHIVEDEFCLPARMS.

AZK4866E service of archive output data setfailed due to failrsn

Explanation

One of the following errors occurred: (1) allocation of anew archive backup or extract file failed, or (2)deletion during cleanup for a failed archive failed. Forallocation failures, the reason may be that runtime


parameters used to generate IDCAMS DEFINECLUSTER statements are not set properly.

User response


AZK4867E IDCAMS UTILITY LASTCC=lastcc--- ABEND CONDITION ccode,REASON rcode - SYSPRINTFOLLOWS

Explanation

This message follows message 4866E when anIDCAMS DEFINE CLUSTER or DELETE CLUSTERstatement failed to be processed through the IDCAMSutility. The SYSPRINT output of the IDCAMS utility, ifany, follows this message.

User response


AZK4868E IDCAMS SYSPRINT: msgdata

Explanation

This message follows message 4867E when anIDCAMS DEFINE CLUSTER or DELETE CLUSTERstatement failed to be processed through the IDCAMSutility. The SYSPRINT output of the IDCAMS utility(msgdata) follows this message.

User response


AZK4869E TRACE BROWSE EXTRACTSDISABLED BECAUSE'EXTRACTDSNPREFIX'PARAMETER IS NOT SET

Explanation

Trace Browse extract support has been turned offbecause the output data set name prefix parameterEXTRACTDSNPREFIX is not set. A data set name prefixis required.

User response

Note that you can review and possibly set values forthe following extract data set allocation relatedparameters: EXTRACTDSNPREFIX,EXTRACTDATACLASS, EXTRACTMGMTCLASS,EXTRACTSTORCLASS, and EXTRACTDEFCLPARMS.

AZK4870E reqtype reqfunc - ABEND -CODE=abcode REASON=rsncode

Explanation

An application programming interface requestabended.

User response

The request fails. Check for other messages that mightindicate the cause of the failure.

AZK4871S Automatic archival of Tracesuspended due to previous error -correct problem and issue"ARCHIVE CLEANUP"

Explanation

An archive backup operation has failed with an errorrequiring intervention. Such a condition exists if, forexample, the IDCAMS allocation parameters are notconfigured properly. Any new attempt to automaticallyschedule an archive will likely fail until action is takento correct the problem.

User response

Examine the console hardcopy log and the TraceBrowse to determine why the previous automaticbackup operation has failed. Correct the situation.Once the cause of the failure has been corrected, issuean ARCHIVE CLEANUP command via the SEF interfaceto reset the in-flight failure indicators. You can issuethis command using the ISPF E.3 application.

AZK5000S MESSAGE NUMBER msgno IS NOTDEFINED

Explanation

This message is issued whenever an undefinedmessage number is encountered.

User response

This probably indicates an internal product error.Contact Software Support.

AZK5001S object IS AN INVALID %PXOBJECT

Explanation

You have tried to DEFINE/MODIFY an unknown AZKobject.

User response

Correct the DEFINE/MODIFY command, and rerun.

AZK5002S cmdname is an invalid %PXcommand.


Explanation

The command you have coded is unknown toADDRESS AZK.

User response

Enter the correct AZK command, and rerun.

AZK5003S keyword is an invalid keyword.

Explanation

This keyword is not part of any AZK command.

User response

Recode the AZK command, and rerun.

AZK5004S The keyword keyword is missing.

Explanation

The indicated keyword is required but was not coded.

User response

Recode the AZK command using the keyword, andrerun.

AZK5005S value is not a valid value for thekeyword keyword.

Explanation

The value you have coded is not valid value for thekeyword.

User response

Recode the value, and rerun the AZK command.

AZK5006S keyword IS ONLY VALID FOR TYPE= ktype

Explanation

The keyword indicated is not valid for the given valueof the type of keyword.

User response

Remove the erroneous keyword (or change the type),and rerun the command.

AZK5007S LINK host already exists.

Explanation

The indicated link has already been defined.

Note that host is the host keyword.

User response

Determine which definition is correct, and rerun.

AZK5008U OPRXPC TERMINATED WITHSEVERE ERROR RC = rcode

Explanation

An internal component of ADDRESS AZK has failed.

User response


AZK5009S MODIFY CONTAINS FIELDS NOTSUPPORTED BY LINK TYPE

Explanation

You cannot modify fields that are undefined for thistype of link.

User response

Remove the keywords in error, and rerun thecommand.

AZK5010E HOST = host DOES NOT EXIST

Explanation

The link defined by the host is not yet defined;therefore, it cannot be modified.

User response

Either define the link, or remove the MODIFY.

AZK5011S object DISPLAY FAILED WITH RC =rcode

Explanation

The display of the object failed severely.

User response

There is probably some sort of internal error. ContactSoftware Support.

AZK5012S keyword CONTAINS A QUOTE ANDQUOTES ARE NOT PERMITTED

Explanation

AZK keywords do not require or permit quotes.

User response

Remove the quote marks, and rerun.


AZK5013S %PX SUBSYSTEM subsys IS NOTACTIVE

Explanation

The indicated subsystem is not running. The ADDRESSAZK host environment command cannot be processed.

User response

Start the subsystem (or use the SUBSYS command toidentify another subsystem), and rerun the command.

AZK5014S subsys IS AN INVALID TEM NAME

Explanation

The tem name coded is not valid.

User response

tem names must begin with an alpha (a-z) character,and all other characters can be alphanumeric. Also,the name can only be four (4) characters long.

AZK5015E DATABASE subsys IS ALREADYDEFINED

Explanation

The indicated database subsystem has already beendefined.

User response


AZK5016E DATABASE = subsys DOES NOTEXIST

Explanation

The database defined by name (subsys) is not yetdefined; therefore, it cannot be modified.

User response

Either define the database, or remove the MODIFY.

AZK5017S parmname IS NOT A VALIDPRODUCT PARAMETER NAME

Explanation

The parameter name is not a valid, recognized productparameter.

User response

Correct the parameter name, and rerun.

AZK5018S parmval IS NOT A VALID VALUEFOR parmname

Explanation

The parameter value is not valid for this parameter.

User response

Correct the value, and rerun.

AZK5019E subsys IS A DB2 DATABASESUBSYSTEM

Explanation

The database subsystem can not be defined becausethe subsystem is an actual Db2 subsystem.

User response

Change the database subsystem name, and rerun.

AZK5020E ANOTHER COPY OF THE PRODUCTUSES DATABASE SUBSYSTEMNAME subsys

Explanation

The database subsystem cannot be defined becauseanother copy of the product is using the databasesubsystem.

User response


AZK5021E DATABASE SUBSYSTEM subsysCOULD NOT BE CREATED

Explanation

The database subsystem control blocks could not becreated.

User response

Fix any related errors, and rerun.

AZK5022E ANOTHER PRODUCT USESDATABASE SUBSYSTEM NAMEsubsys

Explanation

The database subsystem cannot be defined becauseanother product is using the database subsystem.

User response



AZK5023E CONNECTION conn IS ALREADYDEFINED

Explanation

The indicated connection has already been defined.

User response


AZK5024E SESSION session IS ALREADYDEFINED

Explanation

The indicated session has already been defined.

User response


AZK5025I DDNAME ddname IS NOTALLOCATED TO PRODUCTADDRESS SPACE

Explanation

The indicated ddname is not allocated to the productaddress space.

User response

The attempt to define the file fails. Add a DDstatement to the product start-up JCL for the indicatedfile, and restart the product.

AZK5026T MEASURED USAGE reqtypeCOMPLETED SUCCESSFULLY

Explanation

This message indicates that Measured Usage Requestcompleted successfully.

User response

No action required.

AZK5027T MEASURED USAGE reqtypeREQUEST MAY HAVE FAILED,RC=rcode

Explanation

This message indicates that Measured Usage Requestmay have failed. Please check return code and requesttype.

User response

No action required.

AZK6000T ENTER MODULE csect

Explanation

This diagnostic trace message is issued to indicatethat control has entered a particular product module.

User response

This is an informational message. No action isrequired. However, if diagnostic tracing has beenturned on at the request of Software Support, pleasecall for further instructions.

AZK6003T MATCHING SSCT LOCATED FORSUBSYSTEM subsys

Explanation

This diagnostic trace message is issued in response tobeing able to locate an SSCT that matches thesubsystem name that was extracted.

User response

This is an informational message. No action isrequired. However, if diagnostic tracing has beenturned on at the request of Software Support, pleasecontact Software Support for further instructions.

AZK6004T TRANSFERRING CONTROL TOMODULE DSNECP00

Explanation

This diagnostic trace message is issued just prior totransferring control to the IBM-supplied DSNcommand. It has been determined that the currentDSN command session is bound for a copy of Db2whose connection is not being managed by theproduct.

User response


AZK6007T PRIOR TO LINKING TO OPDSN10SUBCOMMAND HANDLER

Explanation

This diagnostic trace message is issued just prior tolinking to OPDSN10, the subcommand handler.

User response

This is an informational message. No action isrequired. However, if diagnostic tracing has been


turned on at the request of Software Support, pleasecontact Software Support for further instructions.

AZK6008T RETURN FROM LINKING TOOPDSN10 SUBCOMMANDHANDLER

Explanation

This diagnostic trace message is issued on return fromlinking to OPDSN10, the subcommand handler.

User response


AZK6009T PRIOR TO ATTACHING OPDSN10SUBCOMMAND HANDLER

Explanation

This diagnostic trace message is issued just prior toattaching OPDSN10, the subcommand handler.

User response


AZK6010T RETURN FROM ATTACHINGOPDSN10 SUBCOMMANDHANDLER

Explanation

This diagnostic trace message is issued on return fromattaching OPDSN10, the subcommand handler.

User response


AZK6011T OPDSN10 SUBCOMMANDHANDLER DETACHEDSUCCESSFULLY

Explanation

This diagnostic trace message is issued aftersuccessfully detaching OPDSN10, the subcommandhandler.

User response


AZK6013T EXITING MODULE csect

Explanation

This diagnostic trace message is issued just prior toexiting the module named in the diagnostic tracemessage.

User response


AZK6014T OPDSN10 STAX EXITSUCCESSFULLY ESTABLISHED

Explanation

This diagnostic trace message is issued aftersuccessfully establishing the STAX exit for moduleOPDSN10.

User response


AZK6015T OPDSN10 STAX EXITSUCCESSFULLY REMOVED

Explanation

This diagnostic trace message is issued aftersuccessfully removing the STAX exit for moduleOPDSN10.

User response


AZK6016T VALID SUBCOMMAND subcmdACCEPTED

Explanation

This diagnostic trace message is issued afterdetermining that the subcommand entered by the user


is one of the set of valid subcommands supported bymodule OPDSN10.

User response


AZK6017T UNRECOGNIZED SUBCOMMANDASSUME TSO COMMAND subcmd

Explanation

This diagnostic trace message is issued afterdetermining that the subcommand entered by the useris neither one of the set of valid subcommandssupported by OPDSN10 nor one of the set of TSOcommands not supported by OPDSN10.

User response


AZK6018T PRIOR TO LINKING TO TSOCOMMAND subcmd

Explanation

This diagnostic trace message is issued just prior tolinking to the TSO command specified as a DSNsubcommand.

User response


AZK6019T RETURN FROM LINKING TO TSOCOMMAND subcmd

Explanation

This diagnostic trace message is issued on return fromlinking to the TSO command specified as a DSNsubcommand.

User response


AZK6020T PRIOR TO ATTACHING TSOCOMMAND subcmd

Explanation

This diagnostic trace message is issued just prior toattaching the TSO command specified as a DSNsubcommand.

User response


AZK6021T RETURN FROM ATTACHING TSOCOMMAND subcmd

Explanation

This diagnostic trace message is issued on return fromattaching the TSO command specified as a DSNsubcommand.

User response


AZK6022T SUCCESSFUL DETACH TSOCOMMAND cmdname

Explanation

This diagnostic trace message is issued aftersuccessfully detaching the TSO command specified asa DSN subcommand.

User response


AZK6023T SUCCESSFULLY ALLOCATED DATASET dsname

Explanation

This diagnostic trace message is issued aftersuccessfully allocating the data set specified on theLIBRARY() parameter of the RUN subcommand.

User response




AZK6024T SUCCESSFULLY DEALLOCATEDDATA SET dsname

Explanation

This diagnostic trace message is issued uponsuccessfully deallocating the data set specified on theLIBRARY() parameter of the RUN subcommand.

User response


AZK6025T RUN SUBCOMMAND BUFFERPARSED SUCCESSFULLY

Explanation

This diagnostic trace message is issued aftersuccessfully parsing the RUN subcommand buffer.

User response


AZK6026T LIBRARY : dsname

Explanation

This diagnostic trace message is issued in order topresent the interpreted library specification.

User response


AZK6027T PLANID : planname

Explanation

This diagnostic trace message is issued in order topresent the interpreted plan specification.

User response


AZK6028T PROGRAM : progname

Explanation

This diagnostic trace message is issued in order topresent the interpreted program specification.

User response


AZK6029T CP : indicator

Explanation

This diagnostic trace message is issued in order topresent a YES/NO value (indicated by indicator)depicting whether the CP parameter was or was notspecified.

User response


AZK6030T PARMS : indicator

Explanation

This diagnostic trace message is issued in order topresent a YES/NO value (indicated by indicator)depicting whether the PARMS() parameter was or wasnot specified.

User response


AZK6031T BEFORE IDENTIFY DB2 CALL===========================

Explanation

This diagnostic trace message is issued prior toprocessing the Db2 identify request.

User response



AZK6032T AFTER IDENTIFY DB2 CALL============================

Explanation

This diagnostic trace message is issued afterprocessing the Db2 identify request.

User response


AZK6033T BEFORE CREATE THREAD DB2CALL ======================

Explanation

This diagnostic trace message is issued prior toprocessing the Db2 create thread request.

User response


AZK6034T AFTER CREATE THREAD DB2 CALL=======================

Explanation

This diagnostic trace message is issued afterprocessing the Db2 create thread request.

User response


AZK6037T BEFORE TERMINATE DB2 CALL==========================

Explanation

This diagnostic trace message is issued prior toprocessing the terminate Db2 request.

User response


AZK6038T AFTER TERMINATE DB2 CALL===========================

Explanation

This diagnostic trace message is issued afterprocessing the terminate Db2 request.

User response


AZK6039T PRIOR TO LINKING TO PROGRAMprogname

Explanation

This diagnostic trace message is issued just prior tolinking to the program specified on the PROGRAM()parameter of the RUN subcommand.

User response


AZK6040T RETURN FROM LINKING TOPROGRAM progname

Explanation

This diagnostic trace message is issued on return fromlinking to the program specified on the PROGRAM()parameter of the RUN subcommand.

User response


AZK6041T APPLICATION PROGRAM FAILEDWITH ABEND CODE abcode

Explanation

This diagnostic trace message is issued if theapplication program fails with any type of abend code.This message is generated both when the applicationprogram is attached and when it is linked to.

User response




AZK6042T RRSAF func function RC rcodeReason rsncode was converted toRC 0 Reason 0.

Explanation

This message is issued when the product has ignoredcertain error reason codes from RRSAF function calls.

User response

This is an informational message. No action isrequired. However, if this action contributes to threaderrors later in the process, please contact SoftwareSupport for further instructions.

AZK6500S ABEND abcode RS=rsncodeOCCURRED AT modname+offsetDURING DMF func entityid

Explanation

An ABEND occurred while processing a Data MappingFacility (DMF) request.

User response

The routine signals an error to the caller andprocessing continues, when possible.

AZK6501W DMF operation WARNING: rsn item

Explanation

A correctable condition was encountered whileprocessing a Data Mapping Facility (DMF) request.

item represents the item being processed at the timeof warning detection.

User response

The routine issues this warning message andprocesses the requested function. The warning MAYindicate a condition which requires attention.

AZK6502S DMF operation ERROR: rsn item

Explanation

An un-correctable condition was encountered whileprocessing a Data Mapping Facility (DMF) request.

item represents the item being processed at the timeor error detection.

User response

The routine issues this error message and concludesprocessing of the requested function. Correct thecondition and re-run the request. For STOW error'scheck the dataset space allocation for sufficient spaceand sufficient directory block allocations. If thedataset is a Services Metadata or Microflow datasetyou can use the parameter WSALLOC in PRODZSERVto override the default allocation values.

AZK6503I DMF IMPORT var MAP memberFROM source additinfo

Explanation

A DMF IMPORT request has successfully imported anXML data map definition and has saved the new orchanged datamap into the mapping library.

var is an indicator that can be "SAVED" or"REPLACED".

User response

This message is issued for each new or changeddatamap successfully imported from an XML mapdefinition document.

AZK6504I DMF import has refreshed in-storage data maps

Explanation

A DMF IMPORT request has refreshed the in-storagedata map images following import of new or changeddata maps.

User response

This message is issued after all new or changeddatamaps have seem saved during XML importprocessing.

AZK6505I DMF import parsed map map fromsource

Explanation

A DMF IMPORT request has successfully processed anXML data map definition, but is not requested to saveit. The data map will be discarded.

User response

This message is issued for each datamap parsed froman XML document, if the new/changed data map is notto be saved or replaced in the map library. Thismessages indicates that the XML document is valid.

AZK6506T Required map map for conversionof EXCI to ACI missing


Explanation

The specified map is missing from DMF. This map isrequired to dynamically create the ACI serverdefinition for the EXCI to ACI conversion

User response

Use the product ISPF option "D.I" to initialize themaps required by the product.

AZK6507T Unable to create serverserverconnection for CICSconnection connection

Explanation

Unable to create an ACI server for EXCI to ACIconversion for the specified CICS connection(connection).

User response

This message is issued for each CICS connection thatis to be converted to use ACI. Probable cause is aGETMAIN error. Check Trace Browse and the Joblogfor further messages and contact Software Support.

AZK6509I DMF PROCESSING COMPLETE

Explanation

A DMF request has completed processing. This will bethe last message related to the current DMFcommand.

User response

This message is issued when a DMF command hascompleted processing. It is used to identify the last ofa series of related DMF messages.

AZK6520H DMF Data-In-Virtual cache isbeing initialized for revision levellvl support

Explanation

During initialization the Data Mapping Facility (DMF)determined that it's data-in-virtual cache is empty,contains errors, or is formatted for operation at adifferent revision level. The DIV object is beinginitialized or re-initialized for use at the currentsoftware support revision level.

User response

This DMF DIV data-in-virtual cache will be initializedfor use and placed online.

AZK6521H Existing DMF DIV cache at revisionlevel lvl must be re-initialized atcurrent level

Explanation

During initialization the Data Mapping Facility (DMF)found the DIV linear dataset cache dataset (@#$MAPL) contained information formatted for an older/different revision level than the server software nowsupports. The cache must be discarded and re-loadedin order to switch to the current software supportrevision level.

User response

DMF cached data maps will be discarded and the DIVdataset re-initialized at the new support level. DMFwill reload data maps into the cache, as these are readinto storage from the @#$MAPP PDS library.

AZK6522H Existing DMF DIV cache beingdiscarded due to incompleteupdate at last LDS expansion

Explanation

During initialization the Data Mapping Facility (DMF)found the DIV linear dataset cache dataset (@#$MAPL) could not be placed online because a DIVexpansion operation failed to complete properlyduring the prior start-up. The cache must be discardedand re-loaded in order to remove any incompletelyallocated logical window areas.

User response

DMF cached data maps will be discarded and the DIVdataset re-initialized. DMF will reload data maps intothe cache as these are read into storage from the @#$MAPP PDS library.

AZK6523H Existing DMF DIV cache beingdiscarded due to windowrelocation problem

Explanation

During initialization the Data Mapping Facility (DMF)found the DIV linear dataset cache dataset (@#$MAPL) could not be placed online because a problemoccurred while attempting to relocate maps and mappointers within the DIV windows. The cache must bediscarded and re-loaded in order to remove theerroneous/problematic information.

User response

DMF cached data maps will be discarded and the DIVdataset re-initialized. DMF will reload data maps into


the cache as these are read into storage from the @#$MAPP PDS library.

AZK6524H Existing DMF DIV cache beingdiscarded due to unknown objecttype (%1)

Explanation

During initialization the Data Mapping Facility (DMF)found the DIV linear dataset cache dataset (@#$MAPL) contains a DMF block area in which garbage oran unknown element block resides. The cache must bediscarded and re-loaded in order to remove thecorrupted data block.

User response

DMF cached data maps will be discarded and the DIVdataset re-initialized. DMF will reload data maps intothe cache as these are read into storage from the @#$MAPP PDS library.

AZK6525S DMF DIV cache routine %1invoked within invalid x-memenvironment

Explanation

While processing, a DMF service routine was invokedwithin a cross-memory environment which it does notsupport. The DMF service request cannot becompleted.

User response

For some service requests, the routine aborts bygenerating an S0C3 ABEND. Other service routinesreturn an error to the caller, which will likely cause theoriginating procedure to fail or ABEND. ContactSoftware Support.

AZK6526S Free of DMF block in DIV cachefailed - address of block (%1) isnot %2

Explanation

While processing, a request to remove a dmf data areafrom DIV cache, a validation error was detected. thedata area is not considered valid for the reasonindicated.

User response

The removal routine returns an error to the caller,which may result in failure within the procedure beingexecuted. Contact Software Support.

AZK6527H Existing dmf div cache beingdiscarded. an invalid %1 OBJectchain was found by %2.

Explanation

During initialization the data mapping facility (dmf)found the DIV linear dataset cache dataset (@#$MAPL) contains an invalid control block chain. thecache must be discarded and re-loaded in order toremove the corrupted data block.

User response

DMF cached data maps will be discarded and the divdataset re-initialized. dmf will reload data maps intothe cache as these are read into storage from the @#$MAPP pds library.

AZK6528H Too many virtual directories -dataset %1 not processed for path%2

Explanation

During a refresh of in-storage maps by the datamapping Facility (dmf), more than 200 individualvirtual directory datasets were defined. the systemcan process no more than 200 individual datasetsallocated as virtual directories.

User response

The virtual directory definition entry is skipped and theindicated virtual directory dataset is not placed online

AZK7000I Syntax error: unmatchedparenthesis

Explanation

The command used to invoke the system function wascoded incorrectly. unbalanced parentheses werefound in the input command, which consequentlycould not be understood and processed.

User response

Reenter the corrected command.

AZK7001I Syntax error: unmatchedquotation mark or apostroph

Explanation

The command used to invoke the system function wascoded incorrectly. a literal string was not enclosedwithin matching quotation marks or apostrophes.


User response


AZK7002I Syntax error: insufficient storagefor parsing the command (rsncode)

Explanation

The command used to invoke the system functioncould not be parsed because insufficient storageexists for the command parser.

User response

If the reason code is "1", increase the storage size ofthe region, and re-submit the command request. Ifreason code is "2", ensure that the command wascorrectly entered. If the problem cannot be resolved,contact Software Support.

AZK7003I Syntax error: invalid hex literal

Explanation

The command used to invoke the system functioncould not be parsed because it contains an incorrectlyformatted hexadecimal literal. the hex literal containsmore than eight (8) hex digits or contains an invaliddigit.

User response


AZK7004I Syntax error: extraneous orundefined input at token

Explanation

The command used to invoke the system functioncould not be parsed because it contains extraneous,undefined operands or duplicate keyword operands.

User response


AZK7005I Syntax error: positional param.parmno of parmname - errdesc

Explanation

The command used to invoke the system functioncould not be parsed because it contains an error in apositional parameter. the full text of the messageexplains which parameter number and what portion ofthe command contains the error. the message alsocontains an explanation as to why the parameter isinvalid.

User response


AZK7006I Syntax error: required keywordkeyword - missing

Explanation

The required keyword was not entered on thecommand line.

User response


AZK7007I Syntax error: required keywordmissing - must be on

Explanation

A required keyword was not entered on the commandline.

User response


AZK7008I keyword

Explanation

This message lists the keywords from which a choicemust be made.

User response


AZK7009I Syntax error: operand of keywordis invalid or missing

Explanation

The operand coded for the indicated keyword is notvalid or was omitted.

User response


AZK7010I Syntax error: errdesc

Explanation

The input was invalid for the reason (errdesc) indicatedin the message.

User response


AZK7050T Variable varname (val) set to "%3"


Explanation

This message is used to trace the variable values thathave been parsed from an inbound http transactionheader.

User response

None.

AZK7101T Error 01 @(lineno/offset) - toomany nexted html extensiondelimiter pairs on this source line.

Explanation

A syntax error was detected while a text file wasscanned for HTML extension statements. The sourcefile line number and offset within the line where theerror was found is noted in the message.

User response

Examine the source file, and correct the htmlextension statement syntax error.

The variable fields of the message text are: lineno linenumber in source file where error found loff offset insource line where error detected

AZK7102T Error 02 @(lineno/offset) - un-matched <%% delimiter in sourceline.

Explanation

A syntax error was detected while a text file wasscanned for HTML extension statements. the sourcefile line number and offset within the line where theerror was found is noted in the message.

User response


AZK7103T Error 03 @(lineno/offset) - toomany tokens, or tokens invalid INstatement.

Explanation


User response


AZK7104T Error 04 @(lineno/offset) - un-identified or invalid htmlextension statement.

Explanation


User response


AZK7105T Error 05 @(lineno/offset) - thisstatement type must be on a LINEwith no other non-blank text.

Explanation


User response


AZK7106T Error 06 @(lineno/offset) - invalidtoken or label precedes statementoperation keyword.

Explanation


User response


AZK7107T Error 07 @(lineno/offset) - invalidstatement label syntax.

Explanation



User response


AZK7108T Error 08 @(lineno/offset) - toomany operands for statementtype.

Explanation


User response


AZK7109T Error 09 @(lineno/offset) - too fewoperands for statement type.

Explanation


User response


AZK7110T Error 10 @(lineno/offset) - invalidexit statement operand value.

Explanation


User response

Examine the source file, and correct the HTMLextension statement syntax error.

AZK7111T Error 11 @(lineno/offset) - invalidkeyword specified - not advanceor no advance.

Explanation


User response


AZK7112T Error 12 @(lineno/offset) - invalidcondition name for if statementoperand two.

Explanation


User response


AZK7113T Error 13 @(lineno/offset) - variablename symbol too long - maximumname size is 50 characters.

Explanation


User response


AZK7114T Error 14 @(lineno/offset) - numberof nested if/endif statement pairsexceeds compiler maximum.

Explanation


User response


AZK7115T Error 15 @(lineno/offset) - elsewithout preceding if statement.

Explanation

A syntax error was detected while a text file wasscanned for HTML extension statements. the source


file line number and offset within the line where theerror was found is noted in the message.

User response


AZK7116T Error 16 @(lineno/offset) -duplicate else statements forcurrent if/endif pair.

Explanation


User response


AZK7117T Error 17 @(lineno/offset) - endifnot preceded by if statement.

Explanation


User response


AZK7118T Error 18 @(lineno/offset) - nesteddo/enddo groups exceedscompiler maximum nesting levels.

Explanation


User response


AZK7119T Error 19 @(lineno/offset) -statement should only appearwithin do/enddo statement group.

Explanation


User response


AZK7120T Error 20 @(lineno/offset) - labelname not defined by anypreceding do statement.

Explanation


User response


AZK7121T Error 21 @(lineno/offset) - numberof leave statements exceedscompiler maximums.

Explanation


User response


AZK7122T Error 22 @(lineno/offset) -duplicate do statement label namedefined.

Explanation


User response



AZK7123T Error 23 @(lineno/offset) - labelnot defined in source file

Explanation


User response


AZK7124T Error 24 @(lineno/offset) -compiler maximum for labelnames within a source fileexceeded.

Explanation


User response


AZK7125T Error 25 @(lineno/offset) - one ormore referenced statement labelsare undefined in source file.

Explanation


User response


AZK7126T Error 26 @(lineno/offset) -compiler area overflow - sourcefIle too complex.

Explanation


User response


AZK7127T Error 27 @(lineno/offset) - one ormore if statements has nomatching endif.

Explanation


User response


AZK7128T Error 28 @(lineno/offset) - one ormore do statements has nomatching enddo.

Explanation


User response


AZK7129T ERROR 29 @(lineno/offset) -ADDITIONAL ERRORS WEREDETECTED IN SOURCE FILE -FIRST 5 REPORTED.

Explanation


User response


AZK7130T ERROR 30 @(lineno/offset) -INVALID SWSINFO()PSEUDO=FUNCTION OPERANDVALUE.


Explanation


User response


AZK7131T ERROR 31 @(lineno/offset) -HTXINDEX. STEM SYNTAXINVALID.

Explanation


User response


AZK7132T ERROR 32 @(lineno/offset) - FOR'HTXINDEX.LABEL' - THE 'LABEL'NAME IS NOT DEFINED.

Explanation


User response


AZK7133T ERROR 33 @(lineno/offset) -INVALID SWSPARM() PSEUDO-FUNCTIONOPERAND VALUE.

Explanation


User response


AZK7134T ERROR 34 @(lineno/offset) -INVALID TOUPPER() PSEDUO-FUNCTIONOPERAND VALUE.

Explanation


User response


AZK7135T ERROR 35 @(lineno/offset) -NESTED RULE STATEMENTS ARENOT ALLOWED.

Explanation


User response


AZK7136T ERROR 36 @(lineno/offset) - ANUNMATCHED /RULE STATEMENTWAS ENCOUNTERED.

Explanation


User response


AZK7137T ERROR 37 @(lineno/offset) -STORAGE ALLOCATION FAILUREDURING RULE PROCESSING.

Explanation



User response


AZK7138T ERROR 38 @(lineno/offset) - ONEOR MORE RULE STATEMENTS HASNO MATCHING /RULE.

Explanation


User response


AZK7139T ERROR 39 @(lineno/offset) -ENABLEMENT FAILED FOREMBEDDED RULE.

Explanation


User response


AZK7140T ERROR 40 @(lineno/offset) - /*FILE SECTIONS ARE NOTALLOWED WITHIN EMBEDDEDRULES.

Explanation


User response


AZK7141T ERROR 41 @(lineno/offset) -DATE(?) OPERAND INVALID ORNOT SPECIFIED.

Explanation

A syntax error was detected in the DATE(?) HTMLextension function. Refer to the documentation for thecorrect options.

User response


AZK7142T ERROR 42 @(lineno/offset) -TIME(?) OPERAND INVALID ORNOT SPECIFIED.

Explanation

A syntax error was detected in the TIME(?) HTMLextension function. Refer to the documentation for thecorrect options.

User response


AZK7143T ERROR 43 @(lineno/offset) -EMBEDDED RULES CANNOT BEEMPTY.

Explanation


User response


AZK7144T ERROR 44 @(lineno/offset) -TARGET OF ASSIGNMENT MUSTBE L-VALUE.

Explanation

A syntax error was detected while a text file wasscanned for HTML extension statements. The sourcefile line number and offset within the line where theerror was found is noted in the message. The target ofan assignment statement must be a valid L-Value(either a variable name or a complex expression thatcan evaluate at runtime to the name of a variable).

User response



AZK7145T ERROR 45 @(lineno/offset) - IMSAUTO-HTML VARIABLEREFERENCE IS BADLY FORMED

Explanation

A syntax error was detected while a text file wasscanned for HTML extension statements. The sourcefile line number and offset within the line where theerror was found is noted in the message. A referenceto an IMS Auto-HTML facility runtime variable(SWSSETFO, SWSFOCUS, SWSINMAP, or SWSCNVID)contains additional/extraneous characters.

User response


AZK7146T ERROR 46 @(lineno/offset) - !OPTIONS STATEMENT INVALID

Explanation

A syntax error was detected while processing an !OPTIONS statement within the HTX source file. Theline number and offset within the line where the errorwas found is noted in the message. A more complexmessage indicating the exact error found in the !OPTIONS statement may be present in the trace.

User response


AZK7147T ERROR 47 @(lineno/offset) - !OPTIONS STATEMENT OUT OFORDER

Explanation

A syntax error was detected while processing an !OPTIONS statement within the HTX source file.Runtime !OPTIONS must appear before any other HTXexecutable or insert statement within the source file.

User response


AZK7148T ERROR 48 @(lineno/offset) -INVALID ENVIRONMENT FORSTATEMENT

Explanation

A syntax error was detected while processing astatement. Some statements are only valid in either

the HTTP Web Server or Data Service server. Thisstatement was encountered in an incorrectenvironment.

User response


AZK7149T ERROR 49 @(lineno/offset) -IMSATTR STATEMENTS NOLONGER SUPPORTED

Explanation

A syntax error was detected while processing astatement. The deprecated IMSATTR statement is nolonger supported by this version of the server.

User response

Examine the source file, and correct the HTMLextension statement syntax error. If the HTMLextension file was generated by the IMS Auto-HTMLfacility, re-extract the MFS source map and re-generate the HTML file.

AZK7150T /*UTILITY STMT - errtext (funcode)

Explanation

During event procedure enablement, a /*UTILITYsection was not enabled due to the error given.

User response


The variable fields of the message text are: text errortext funcc function code

AZK7151T /*UTILITY STMT - errmsg -statement

Explanation

During execution of a /*UTILITY statement, thestatement was determined to be invalid or non-executable.

User response

If the statement text is invalid, correct the statementtext. Otherwise, contact Software Support.

AZK7152T UTILITY FUNCTION funcode NOTENABLED. ASSOCIATED MODULE(modname) NOT FOUND IN THE%3 LIBRARY.


Explanation

While attempting to enable a utility function, themodule associated with the function was not found inthe S__RPCLB library.

User response

The associated vendor library must be concatenatedwith the S__RPCLB library.

AZK7153T ACCESS TO UTILITY ROUTINES ISNOT AUTHORIZED.

Explanation

Your license code does not authorize you to executeutility routines.

User response


AZK7160T LINE lineno - HTML EVALUATIONERROR (errdesc) - additinfo

Explanation

While processing file information that contains HTMLextensions, evaluation of a statement failed.

User response

Examine the source file to determine why the erroroccurred.

AZK7161E ABEND abcode, REASON rsncodeDURING HTX PROCESSING

Explanation

While processing HTML extension processing, anabend occurred.

User response

Examine the source file to determine why the erroroccurred. Check for other messages that may indicatethe cause of the error.

AZK7162E var

Explanation

This message is used internally by OPHTXPR to buildabend error reporting pages (HTML or text form).

User response

None. This message is for internal use only.

AZK7163E ABEND abcode, REASON rsncodeDURING OPHTXPR ABENDRECOVERY

Explanation

While attempting to recover from a previous abend,the second-level abend intercept was entered inOPHTXPR.

User response

Examine the source file to determine why the abendoccurred. Check for other messages that may indicatethe cause of the error.

AZK7164T RUNTIME ERROR (LINE lineno) -EMBEDDED RULES AND RESCANSTMT NOT ALLOWED IN THISFILE.

Explanation

A runtime error was detected while a text file wasbeing processed by the HTML extension processor.The source file line number where the error wasdetected is noted in the message. Note that an HTXexecutable RESCAN statement may also generate thiserror because RESCAN is only allowed whereembedded rules are authorized.

User response

The server aborts processing of the current file andgenerates an error message output page (HTML or textform). The HTML expansion request fails, with RC=16.Remove the rule or RESCAN statement that causedthis condition to be raised, or authorize execution ofembedded rules within this file. You authorizeembedded rule execution by (1) requesting the file viathe /*FILE process section or via /*WWW PATH() (fromthe HFS) and (2) specifying the RULE(YES) keywordfor /*FILE.

AZK7165T RUNTIME ERROR (LINE lineno) -ASSIGNMENT STMT FAILED -errdesc - lval

Explanation

A runtime error was detected while a text file wasbeing processed by the HTML extension processor.The source file line number where the error wasdetected is noted in the message. A variableassignment statement failed for the reason indicatedin the message.


User response

If the message indicates that the LValue (lval) must bea global variable, ensure that the original assignmentstatement refers only to a global variable. Theseinclude GLOBAL., GLVEVENT., or .GLVSTATE.variables. Otherwise, check for other messages thatmight indicate the cause of failure.

AZK7166T <%RULE%> EXECUTION MUSTNOT DRIVE RECURSIVE <%RULE%> EXECUTION

Explanation

A runtime error was detected while a text file wasbeing processed by the HTML extension processor.The HTML extension processor is about to execute anembedded rule, but an embedded <%RULE%>execution is already underway. This type of recursionis not allowed.

User response

The current (nested) <%RULE%> section is bypassed,and HTML extension processing of the file is aborted.

AZK7167E ABEND abcode, REASON rsncodeDURING HTX PROCESSING OFEMBEDDED ruletype RULE

Explanation

While processing HTML extensions, an abend occurredwhile executing an embedded rule.

User response

Examine the source file to determine why the erroroccurred. Check for other messages that may indicatethe cause of the error.

AZK7168T LINE lineno - EXIT-FLUSHSTATEMENT EXECUTED - RESCANAND NEW RULE MATCHESDISABLED

Explanation

While processing file information that contains HTMLextensions, an <%EXIT FLUSH%> statement wasexecuted. This causes immediate exit from HTMLextension file tailoring and also sets controls so thatadditional RESCAN or rule matches are inhibited.

User response

The server will flush (complete) the transactionwithout delay.

AZK7169T LINE lineno - RESCAN STATEMENTOPERAND INVALID - reason -VALUE=value

Explanation

While processing file information that contains HTMLextensions, a <%RESCAN x%> statement wasexecuted. The RESCAN URL operand is invalid for thereason reported. If the RESCAN URL value waspartially validated, it appears in the message (value); ifit was not partially validated, the value string will benull.

User response

The server uses the value SYSTEM/ERROR/500 as areplacement for the invalid RESCAN URL. It also setsthe HTTP response code to 500 (server error) and theerror code to 61.

AZK7170T LINE lineno - EXIT OPTION, option,IGNORED BECAUSE <%RULE%>PROCESSING NOT ENABLED

Explanation

While processing file information that contains HTMLextensions, an <%EXIT%> statement with theindicated option was executed. The option is beingignored because HTML extension processing wasrequested via an interface that does not support theexecution of embedded rules.

User response

The EXIT option is ignored.

AZK7171T LINE lineno - !OPTIONS statement- errdesc

Explanation

While parsing an !OPTIONS statement a syntax errorwas found. This message is traced to provide adetailed reason for the failure. HTX processing of thefile fails with error code 46.

User response

Correct the !OPTIONS statement and retry

AZK7172T ERROR 72 @(lineno/offset) -RESULTSET OPERAND INVALIDOR NOT SPECIFIED.


Explanation

A syntax error was detected in the RESULTSET HTMLextension function. Only values of 1 or 2 are supportedat this time.

User response


AZK7178T diagtext

Explanation

This message is used to dump out various internalwork areas into the trace. It is triggered by setting adiagnostic parameter or control.

User response

If there are other messages indicating an error, usethis message in conjunction with them to determinethe cause of the problem.

AZK7179E DATA MAPPING - map FIELD fieldIS TOO LONG

Explanation

During processing of a data map, a field was definedthat was too long for processing. Fields of 3074 bytesare currently the longest fields allowed.

User response

Recreate the map with shorter fields, or disable thisfield.

AZK7180E /*EXECSQL STMT - errtext

Explanation

During event procedure enablement, a /*SQL sectionwas not enabled due to the error given.

User response


AZK7181T /*EXECSQL STMT - errmsg -statement

Explanation

During execution of an /*EXECSQL statement, the SQLstatement was determined to be invalid or non-executable.

User response

If the SQL statement text is invalid, correct the SQLstatement text. If the problem cannot be resolved,contact Software Support.

AZK7182T HTML MEMBER NAME MISSING ORINVALID. DATA MAP: map, HTMLMEMBER: memname

Explanation

During execution of an output file SEND, the HTMLmember name was not specified in the data map orthe HTML member name was invalid.

User response

The error is reported as a system error aux on the Webbrowser. This problem may be correctable byrefreshing the data map after the HTML generation iscomplete.

AZK7183E /*EXECIMS STMT - errtext

Explanation

During event procedure enablement, a /*EXECIMSsection was not enabled due to the error given.

User response


AZK7184T /*EXECIMS STMT - errmsg -statement

Explanation

During execution of an /*EXECIMS statement, thestatement was determined to be invalid or non-executable.

User response

If the IMS statement text is invalid, correct the IMSstatement text. Otherwise, contact Software Supportwith this problem.

AZK7185E UNABLE TO OBTAIN INPUTSTORAGE WORK AREA. LENGTH%1

Explanation

While processing an input request, there wasinsufficient storage to build the input message basedupon the the product Mapping Facility definition of theinput map.


User response

This may be caused by an error in the map definition.The input map may contain a field with an erroneousoffset or length. The total length of the input messagecannot exceed 32,702 bytes.

AZK7186E REQUIRED HTML VARIABLEMISSING. NAME=varname

Explanation

While processing an input URL, the /*EXECIMS expectscertain query variables: SWSINMAP, SWSCNVID andPFKIN. One or more of these variables was missing.

User response

This may be caused by an error in the coding of theHTML. The SWSINMAP variable contains the input mapname required to process this URL. The SWSCNVIDvariable contains the conversation id required toprocess conversational IMS transactions. The PFKINvariable contains the interrupt key (ENTER,PF01...PF24).

AZK7187E /*EXECCICS STMT - errtext

Explanation

During event procedure enablement, an /*EXECCICSsection was not enabled due to the error given.

User response


AZK7188T /*EXECCICS STMT - errmsg -statement

Explanation

During execution of an /*EXECCICS statement, thestatement was determined to be invalid or non-executable.

User response

If the CICS statement text is invalid, correct the CICSstatement text. Otherwise, contact Software Supportwith this problem.

AZK7189T TEMPORARY MAP map USED FORHTML FILE SELECTION

Explanation

During execution of an output file SEND, the output filename was selected from the temporary map name.Permanent maps will arbitrarily use the file associatedwith the SWSAHTML ddname.

User response

For the /*EXECIMS and /*EXECCICS rule sections, anHTML file output from the HTML data set name storedwithin the specified map name will be selected. Thisinformation is provided for auditing and controlpurposes. No action may be required.

AZK7190E /*TSOSRV STMT - errtext

Explanation

During event procedure enablement, a /*TSOSRVsection was not enabled due to the error given.

User response


AZK7191T /*TSOSRV STMT - errmsg -cmdtext

Explanation

During execution of an /*TSOSRV statement, the TSOcommand statement was determined to be invalid ornon-executable.

User response

If the TSO command text is invalid, correct thecommand statement text. If the problem cannot beresolved, contact Software Support.

AZK7192T /*TSOSRV STMT - errmsg -cmdtext

Explanation

During execution of an /*TSOSRV statement, the TSOcommand statement was determined to be invalid ornon-executable.

User response

If the TSO command text is invalid, correct thecommand statement text. If the problem cannot beresolved, contact Software Support.

AZK7195E rsname.rulename, /*PROGRAMSTMT - errtext

Explanation

During event procedure enablement, a /*PROGRAMsection was not enabled due to the error given.

User response


AZK7200T HTTP-RECV: operdesc


Explanation

Issued if TRACEURLREAD option is on, this messageindicates that the reception of an inbound HTTPrequest is being processed and indicates the progress,so far.

User response

None. This message indicates processing performedduring HTTP request receive operations.

AZK7201T HTTP-RECV: RECEIVED reclength,TOTAL totlength

Explanation

Issued if TRACEURLREAD option is on, this messageindicates that the reception of an inbound HTTPrequest is being processed and indicates the progress.

User response


AZK7202T HTTP-RECV: HTTP REQUESTHEADERS - LENGTH length,DELIMITER dlmtr

Explanation

Issued if TRACEURLREAD option is on, this messageindicates that the reception of an inbound HTTPrequest is being processed and indicates the progress,so far.

User response


AZK7203T HTTP-RECV: HTTP CONTENT-LENGTH: clval

Explanation

Issued if TRACEURLREAD option is on, this messageindicates that the reception of an inbound HTTPrequest is being traced.

User response


AZK7204T VARIABLE WWW.varname NOTBUILT - reason

Explanation

A WWW. event variable was not built during URLparsing for the reason indicated.

User response

Correct the HTML input form used to transmit theinbound data, and re-submit.

AZK7205T SSL ACCEPT FAILED - RC=rcd1REAS=rsncode - ENCLAVE RC=rcd2FEEDBACK=feedback)

Explanation

A pending SSL connection could not be accepted bythe server due to a validation failure or a failure withinthe SSL connection handling engine. This error reportsthe failure.

Note that there are two return codes in the message.rcd1 represents the SSL acceptance return code, andrcd2 represents the LE/370 enclave manager returncode.

feedback contains the LE/370 enclave terminationfeedback codes.

User response

Check for other messages indicating the cause of thetermination, and resolve the problem, if possible.

AZK7206T SSL READ FAILED RC=rcd1REAS=rsncode - ENCLAVE RC=rcd3FEEDBACK=(feedback)

Explanation

A RECEIVE request on an SSL connection failed due toa validation failure or a failure within the SSLconnection engine. This error reports the failure.

Note that the message contains two return codes, rcd1represents the SSL read return code, and rcd2represents the LE/370 enclave manager return code.


User response


AZK7207T SSL WRITE FAILED RC=rcd1REAS=rsncode - ENCLAVE RC=rcd2FEEDBACK=(feedback)


Explanation

A SEND request on an SSL connection failed due to avalidation failure or a failure within the SSL connectionengine. This error reports the failure.

Note that the message contains two return codes;rcd1 represents the SSL read return code, and rcd2represents the LE/370 enclave manager return code.


User response


AZK7208T SSL CLOSE FAILED RC=rcd1REAS=rsncode - ENCLAVE RC=rcd2FEEDBACK=(feedback)

Explanation

A CLOSE request on an SSL connection failed due to avalidation failure or a failure within the SSL connectionengine. This error reports the failure.

Note that the message contains two return codes;rcd1 represents the SSL close return code, and rcd2represents the LE/370 enclave manager return code.

feeback contains the LE/370 enclave terminationfeedback codes.

User response


AZK7209T var1, var2 … var5

Explanation

The message is used to issue various warningmessages when unusual conditions are detectedduring the parse of an inbound HTTP request.

User response

None.

AZK7210T SERVER VARIABLE varnameSKIPPED BY GLVSTATE.PROCESSING

Explanation

The indicated inbound HTML query variable or HTTPcookie variable was not processed as expected to re-create a GLVSTATE. information set.

User response

Processing of the inbound HTTP request continues;however, subsequent processing of the transactionmay encounter problems in the absence of theGLVSTATE. set.

AZK7211T SSL CONNECT FAILED - RC=rcd1REAS=rsncode - ENCLAVE RC=rcd2FEEDBACK=(feedback)

Explanation

A attempt to establish an SSL connection failed due toa validation failure or a failure within the SSLconnection handling engine. This error reports thefailure.

Note that the message contains two return codes;rcd1 represents the SSL acceptance return code, andrcd2 represents the LE/370 enclave manager returncode.

feedback represents the LE/370 enclave terminationfeedback codes.

User response


AZK7212T RELEASE OF SPECIALLY SIZEDwatype AT addr1 FOR OPPR ATaddr2 FAILED WITH RC=rcode

Explanation

During end-of-transaction cleanup, an oversized SEFwork area could not be freed and has been orphaned.The oversized work area had been allocated duringexecution of the previous transaction through the useof the WORKSIZE() of QUEUESIZE() keywords of aWWW rule. Oversized areas are only freed whenthread reuse is in effect, since they are otherwisereleased by end of task processing.

The message contains two addresses; addr1represents the SEF work area address, and addr2represents the owning process block address.

User response

Check for other messages indicating the cause of thetermination, and resolve the problem, if possible.Contact Software Support if this error cannot beresolved locally.

AZK7213T SSL READ: desc


Explanation

Issued if TRACEURLREAD option is on, this messageindicates that the reception of an inbound HTTPrequest is being traced. This message is generated bythe SSL receive routines.

User response


AZK7214T MAXIMUM NUMBER OF QUERYVARIABLES(maxno) EXCEEDED -INBOUND REQUEST CANNOT BEPARSED

Explanation

This message indicates that the inbound HTTP requestcontains more query variable name/value pairs thanthe server is able to parse. The maximum number ofvariables that can effectively be handled is given in themessage.

User response

The server aborts parsing of the current HTTP requestand responds with an HTTP 400 status message,indicating that the inbound request message is invalid.In order to correct the problem, you will need toredesign your application so that it transmits fewerquery variables with any single inbound request.

AZK7215T CANNOT DECODE DBCS QUERYDATA data

Explanation

This message indicates that the inbound HTTP requestcontains an ASCII encoded string (data) that could notbe decoded by the server and converted to EBCDIC.

User response

The query data is set to include only the portion of thestring that could be converted to EBCDIC. Set theDECODETRACE parameter to YES, and rerun thetransaction. Contact Software Support if you cannotdetermine the reason (invalid ISO-2022-JP or Shift-JIS encoding) for the failure.

AZK7216T SSL ACCEPT LEFT countUNCONSUMED LOOK-AHEADBYTES - REJECTING SESSION

Explanation

This message indicates that the SSL accept processingcompleted normally, except that some (count)received bytes were unconsumed from the look-ahead

receive buffer during acceptance processing. SinceSSL Accept processing involves real-time certificateand key negotiation, no look-ahead bytes should haveremained.

User response

This is probably due to a logic error in the server.Contact Software Support.

AZK7217T HTTP-RECV: HTTP TRANSFER-ENCODING: val

Explanation


User response


AZK7218T HTTP-RECV: HTTP CONTENTCHUNK LENGTH: val

Explanation


User response


AZK7230T WEB BUFFER FLUSH ATTEMPTEDIN X-MEM MODE BY modname+offset

Explanation

A Web transaction program has issued a flush requestto transmit outbound response buffers. The caller isoperating in cross-memory mode, and the requestcannot be serviced. The buffer flush request isignored.

User response

Check for other messages that might indicate thecause of the error.

AZK7231T SWSSEND REQUESTS EXCEPTPURGE OR FLUSH ARE INVALIDFOLLOWING SWSFILE(SEND)REQUEST


Explanation

A Web transaction program has issued a request tobuffer additional outbound response data, but thisrequest follows completion of an SWSFILE(SEND)operation. Because SWSFILE(SEND) has generatedHTTP response headers specifying total response size,no additional data can be output unless the file-sendrequest is first purged from the output buffers orflushed to the client.

User response

Check for other messages that might indicate thecause of the error, and correct the problem.

AZK7232T HTTP RESPONSE BUFFER LIMIT(limit) EXCEEDED - SWSSENDWILL ISSUE USER ABEND X'722'

Explanation

The total number of concurrently held output buffersfor a single HTTP response has exceeded theMAXHTTPRESPBUFFERS limit. This may be due to arunaway transaction procedure or simply tounexpectedly large output.

User response

The SWSSEND API routine issues a user abend X'722'to begin cancellation of the Web transaction subtask.If your program is expected to generate excessiveoutput, raise the MAXHTTPRESPBUFFERS limit.

AZK7233T HTTP RESPONSE BYTE LIMIT(limit) EXCEEDED - SWSSENDWILL ISSUE USER ABENDX'722'(1826)

Explanation

The total number of bytes output as part of a singleHTTP response has exceeded theMAXHTTPRESPBYTES limit. This may be due to arunaway transaction procedure or simply tounexpectedly large output.

User response

The SWSSEND API routine issues an user abendX'722' to begin cancellation of the Web transactionsubtask. If your program is expected to generateexcessive output, raise the MAXHTTPRESPBYTESlimit.

AZK7240T USER-SPECIFIED CONTENT-LENGTH DIFFERENT THANCALCULATED LENGTH. USERLENGTH = length, CALCULATEDLENGTH = length

Explanation

A Web transaction program has created a Content-Length HTTP header with a length that is different thanthe calculated length of the data being transmitted.The product Server will use the content lengthspecified by the user. If persistent session support(KEEPALIVE) is enabled, the server will generate aConnection: Close header to guard against problemsthat might be associated with sending the incorrectmessage body length value.

User response

Ensure that the user-generated Content-Length HTTPheader does not include the length of the user-generated HTTP headers and correctly represents thelength of the data being transmitted.

AZK7250E OPISTBRU FUNCTIONTERMINATED: rsn

Explanation

A product display function was invoked improperly

User response

Correct the invocation parameter list, and re-run.

AZK7251T UNKNOWN OR INVALID COOKIEFOUND. errdesc : cookie

Explanation

During execution of OPISTBRU, an unrecognizable orunknown cookie was received.

User response

None. This is a warning message. The unknown cookieis ignored, and the product defaults are used.

AZK7252T ONE OR MORE INVALID COOKIEVALUE FOUND. cfield : val

Explanation

During execution of OPISTBRU, one or more cookiefields were defaulted because the value of the cookiefield was invalid.

User response

None. This is a warning message. The invalid cookiefield is ignored, and the product default for the field isused.

AZK7253T INVALID COOKIE FORMAT countINVALID VARIABLES FOUND:value


Explanation

During execution of OPISTBRU, the stated number ofcookie fields were defaulted because the cookie fieldwas of invalid format. A 7252T message is issued foreach invalid cookie field prior to the issuing of thismessage.

User response

None. This is a warning message. The invalid cookiefield(s) are ignored, and the product default(s) for thefield(s) are used.

AZK7254T TIMESTAMP UNRECOGNIZABLEIN RFC1123, RFC850 OR ANSI CASCTIME() FORMAT time

Explanation

While parsing an HTTP request or response header,the timestamp value could not be parsed to yield avalid timestamp. This may be a browser dependencybeyond the server's control.

User response

None. The server assumes no value is specified for thecorresponding request or response header.

AZK7255T VALUE OF varname ISIMPROPERLY ENCODED: reason

Explanation

While parsing an HTTP request, an SWSECRET_ queryvalue was detected. The server cannot decrypt theinformation for the reason indicated. Note that queryvariables sent out to a browser before a productrestart become stale and cannot be decryptedfollowing a restart.

User response

None. The server rejects the badly formed or invalidquery variable and subsequently rejects thetransaction with a 400 (bad request) HTTP statusmessage.

AZK7300I Invalid command syntax:syntaxerr

Explanation

A host command statement was invalid or could not beparsed for the reason indicated. The error wasdetected during initial command syntax scanning.

User response

Correct the command statement and re-submit.

AZK7301S subsys is an invalid subsystemname

Explanation

The subsystem name coded is not valid.

User response

Subsystem names must be four characters long andmust begin with the correct product ID. The fourthcharacter can be any character in the range A-Z.

AZK7302I Parser routine (OPSXPR) failedwith RC=rcode

Explanation

A host command statement was invalid because thegeneral text parsing routines failed without returning areason for the failure.

User response


AZK7303S object IS AN INVALID OBJECT FORverb

Explanation

You have entered an invalid command / objectcombination for the verb from the SAZK statement.

User response

Correct the command, and rerun.

AZK7304I operand KEYWORD MUST BESPECIFIED FOR verb entitySTATEMENT

Explanation

A host command statement was invalid because anoperand that is required for this type of commandstatement was omitted.

User response

Correct the command statement, and re-submit.

AZK7305I operand KEYWORD MUST reason -SHOULD BE opertype

Explanation

A host command statement was invalid because anoperand value was invalid.


User response


AZK7306I EITHER operand OR operandKEYWORD MUST BE SPECIFIEDFOR verb entity STATEMENT

Explanation

A host command statement was invalid becauseneither of the indicated operands was coded. At leastone is required.

User response


AZK7307I operand KEYWORD INVALID FORverb entity STATEMENT

Explanation

A host command statement was invalid because anoperand was coded that is not valid for the commandstatement type.

User response


AZK7308I ONLY operand KEYWORDALLOWED FOR verb entitySTATEMENT

Explanation

A host command statement was invalid because anoperand was coded that cannot be used for this typeof command. Code only the single keyword operandindicated.

User response


AZK7309I operand KEYWORD MUST BE valueadditinfo

Explanation

A host command statement was invalid because anoperand was not valid. The allowed format for thekeyword operand is given.

User response


AZK7310S cmdname IS AN INVALID cmdtypeCOMMAND

Explanation

The command you have coded is unknown.

User response

Enter a correct command, and rerun.

AZK7311S cmdname subsystem subsys is notactive

Explanation

The indicated subsystem is not running. The addressSAZK function cannot continue.

User response

Start the subsystem (or use the SUBSYS command toidentify another subsystem), and rerun the command.

AZK7312S verb entity STATEMENT FAILEDWITH RC = rcode

Explanation

The requested operation failed severely.

User response

There is probably some sort of internal error. ContactSoftware Support.

AZK7313S Authorization check failed for verbentity statement

Explanation

A host command statement authorization checkroutine found that the current user is not authorized toexecute the command statement. Access to executethe statement is denied.

User response

Check the variables of the error message text for thecommand statement whose access is denied. Ensurethat the current user has the required access. Contactyour security systems administrator for further help, ifnecessary.

AZK7314S parmname is not a valid productparameter name

Explanation

The parameter name is not a valid, recognized productparameter.

User response

Correct the parameter name, and rerun.


AZK7315S parmval is not a valid value forparmname

Explanation

The parameter value is not valid for this parameter.

User response

Correct the value, and rerun.

AZK7316E entity value does not exist

Explanation

The entity defined by name is not yet defined;therefore, it cannot be modified.

User response

Either define the entity or remove the MODIFY.

AZK7317E entity value is already defined

Explanation

The indicated entry has already been defined.

User response


AZK7318S INVALID UPDATE ATTEMPT FORentity

Explanation

An invalid update attempt has been detected.

User response

Remove the keywords in error, and rerun thecommand.

AZK7319I DDNAME ddname is not allocatedto product address space

Explanation

The indicated ddname is not allocated to the productaddress space.

User response

The attempt to define the file fails. Add a DDstatement to the product start-up JCL for the indicatedfile, and restart the product.

AZK7320I DSNAME(dsname) MUST BE APDS(E) DATA SET

Explanation

The indicated data set is not a PDS or PDSE data set.

User response

The attempt to define the file or ruleset fails. Changethe DSNAME() keyword to correct the error.

AZK7321I RULESET indicator NOT rsname

Explanation

The indicated ruleset definition was processed.

indicator indicates whether a ruleset was DEFINED orMODIFIED.

User response

This message logs definitions of or changes to SEFruleset definitions.

AZK7322H jobname HAS QUEUEDRULESET(rsname) indicator FORPROCESSING BY SEF

Explanation

The job or user indicated issued a critical configurationchange command that was successfully scheduled forprocessing by the SEF task. The SEF task will indicatethe outcome of the request.

indicator indicates definition or modification.

User response

Information only. This message is sent to the hardcopyconsole log.

AZK7323H SUPERVISOR STATE REQUIREDFOR verb entity COMMAND

Explanation

The indicated command can only be processed by areal started-task copy of the product becausesupervisor state is required to perform the indicatedaction.

User response

Information only. This message is sent to the hardcopyconsole log.

AZK7324I operand KEYWORD CONTAINSINVALID CHARACTER(S) ATOFFSET offset OF THE STRING


Explanation

A host command statement was invalid because anoperand was not valid. An invalid character orcombination of characters was found at the indicatedoffset within the operand string.

User response


AZK7325E operand IS INVALID INCOMBINATION WITH operand FORverb entity STATEMENT

Explanation

A host command statement was invalid because thespecified parameters conflict.

User response


AZK7326E operand MUST BE SPECIFIED INCOMBINATION WITH operand FORverb entity STATEMENT

Explanation

A host command statement was invalid because arequired parameter was not specified

User response


AZK7327E operand VALUE MUST BE errdescTHAN operand FOR verb entitySTATEMENT

Explanation

A host command statement was invalid because thespecified parameters conflict.

User response


AZK7328E operand VALUE val INVALID -errdesc FOR verb entitySTATEMENT

Explanation

A host command statement was invalid because thespecified parameters is invalid

User response


AZK7329S Not configured for verb entitystatement.

Explanation

None.

User response


AZK7330S rsname RULESET DEFINITIONREJECTED - additinfo

Explanation

The ruleset definition is invalid because of theindicated condition. The definition is discarded.

User response

Correct the ruleset definition and restart the server

AZK7331S rsname SHARED FILE DEFINITIONREJECTED - additinfo

Explanation

The file definition is invalid because of the indicatedcondition. The definition is discarded.

User response

Correct the shared file definition and restart the server

AZK7333T Authorization check failed for verbentity statement

Explanation

A host command statement authorization checkroutine found that the current user is not authorized toexecute the command statement. Access to executethe statement is denied.

User response

Check the variables of the error message text for thecommand statement whose access is denied. Ensurethat the current user has the required access. Contactyour security systems administrator for further help, ifnecessary.

AZK7400T varname INVALID GLVSTATE.VARIABLE - rsn additinfo

Explanation

The indicated variable is not a valid GLVSTATE. prefixvariable. See information on the automated state


management facility for information on proper variablename formats.

User response

Correct the variable name, and rerun the exec orprogram.

AZK7401T setname DOES NOT EXIST ANDCANNOT BE service

Explanation

An attempt to perform a control operation on a namedstate information set failed because the set is notknown to the system.

User response

The current request is ignored.

AZK7402T val IS NOT A VALID VALUE FORTHE varname VARIABLE

Explanation

The value indicated is not a valid value type for thevariable identified.

User response

Correct the variable value, and rerun the exec orprogram.

AZK7403T setname IS A READ-ONLYVARIABLE AND CANNOT BEUPDATED

Explanation

The update attempt for the named state informationset failed because the indicated variable is read-only.

User response

Remove the update attempt for the variable.

AZK7404T GLVSTATE.setname MUST BEACTIVE BEFORE UPDATE TOvarname

Explanation

The indicated variable does not belong to an activenamed state information set. The GLVSTATE. grouphas expired or has never been created.

User response

Create the set before attempting to set the variable.

AZK7405T varname REQUIRES A NUMERICVALUE - FOUND val

Explanation

The indicated variable requires a numeric value inorder to update its value.

User response

Correct the variable specification, and rerun the execor program.

AZK7406T varname ADJUSTED FROM val TOMINIMUM VALUE OF minval for %4

Explanation

The indicated variable was adjusted because the valuebeing set was lower than the minimum. The minimumvalue is used, instead.

User response


AZK7407T varname1 IN varname2 MUST BEALPHAMERIC, BEGIN ALPHA ORAN INTEGER 0-N

Explanation

The indicated variable is not valid for use as aGLVSTATE. user-assigned name. In GLVSTATE.name,name must be less than eight (8) bytes in length, beginalphabetic, and consist of only letters and numbers.The read-only variables, GLVEVENT.0 throughGLVEVENT.n, are also valid but do not designate anamed state variable set.

User response


AZK7408T qualifier ALREADY EXISTS

Explanation

The indicated GLVSTATE.name group already exists.An attempt was made to assign NEW to the controlvariable. Such an attempt is taken as an unconditionalcreate-set request for a set that must not previouslyexist.

User response

The NEW create-set request is rejected with an error.Interrogate GLVSTATE.name before issuing a requestif a previously created set might exist.


AZK7409T ++++++ reqtype varnameDiagnostic WWST Trace ++++++

Explanation

An internal-use diagnostic trace is being produced.Various internal state-related control blocks will beformatted and written to Trace Browse.

User response

None. For use by Software Support.

AZK7410T SERVER TOKEN CREATE/DELETESERVICE FAILED RC=rcode -GLVSTATE.setname UPDATE WILLFAIL

Explanation

An internal service failed to create/delete a servertoken needed to manage a GLVSTATE. variable set.The current GLVSTATE. update request will be failed inone of two ways: (1) as though the update were to aninvalid variable field name or (2) as a HALT error. Thefailure method depends on the type of update.

User response

Check for other messages related to this failure, andcontact Software Support.

AZK7411T REQUEST VARIABLE varnameINVALID AUTOMATED STATETRANSPORT - rsn

Explanation

During Web transaction initialization, an HTML queryvariable or HTTP request header cookie was foundwith a name beginning with SWSSTATE_xxxxxxxx orSWSTOKEN_xxxxxxxx. All query variables and cookieswith names in this form are reserved for automatedprocessing of state information.

User response

The server bypasses built-in handling for this variable,which may result in improper sessions statemanagement activities. A variable in this form is alsorejected if the xxxxxxxx portion is invalid. To be valid,the customer-assigned name must be 1 to 8 bytes inlength; begin with an alphabetic character; and containonly alphabetic characters, the digits 0 through 9, andthe underbar character.

AZK7412T varname BYPASSED BY ASMF -DUPLICATE GLVSTATE.setnameSET ALREADY EXISTS

Explanation

During Web transaction initialization, an HTML queryvariable and/or HTTP request header cookie thatcontains built-in management information for aGLVSTATE. information set was found. Information forthis GLVSTATE. set has already been received fromanother query variable or cookie within this inboundrequest.

User response

The server bypasses built-in handling for this variableand uses only the first GLVSTATE. restorationinformation. Note that this can occur if you include thesame GLVSTATE.xxxxxxxx information in both anHTML form field and an HTTP cookie or if the browsertransmits two HTTP cookies with the same name.

AZK7413T VARIABLE varname DOES NOTCONTAIN A VALID SERVER TOKENID - rsn

Explanation

During Web transaction initialization, an HTML queryvariable or HTTP request header cookie was foundwith a name beginning with SWSTOKEN_xxxxxxxx. Allquery variables and cookies with names of this formare reserved for built-in GLVSTATE. processing.However, the contents of this element did not containthe expected displayable, hexadecimal, 24-byte tokenid value that was expected.

User response

The erroneous information is not used, the inboundquery or cookie information is ignored, and noGLVSTATE. information set is created.

AZK7414T varname VARIABLE DOES NOTCONTAIN VALID INFORMATIONTO RECONSTRUCTGLVSTATE.setname - rsn

Explanation

During Web transaction initialization, an HTML cookievariable was found with a name beginning withSWSSTATE_. The value data, however, does notappear to be formatted as expected for restoration of aGLVSTATE. set. Note that this can occur for incorrectlength information, bad encoding of the data, or someother input anomaly.

User response

The erroneous information is not used, the inboundcookie information is ignored, and no GLVSTATE.information set is created for this variable.


AZK7415T SERVER TOKEN ID (tknid) REUSEDIMPROPERLY FORGLVSTATE.setname1/GLVSTATE.setname2 SETS

Explanation

During Web transaction initialization, an HTML queryvariable or HTTP request header cookie was foundwith a name beginning with SWSSTATE_xxxxxxxx. Allquery variables and cookies with names of this formare reserved for built-in GLVSTATE. processing.However, the contents of this element contained anindication that a token id had been improperly re-used.

User response

This is a logic error. The server generates an S0C3abend. Contact Software Support for assistance.

AZK7416T GLVSTATE.setname NOTRECONSTRUCTED FORTOKENID=tknid DUE TO ERRORerrdesc

Explanation

During Web transaction initialization, an HTML queryvariable or HTTP request header cookie was foundwith a name beginning with SWSTOKEN_xxxxxxxx. Allquery variables and cookies with names of this formare reserved for built-in GLVSTATE. processing.However, a server-side token could not be retrieveddue to an internal error, and this GLVSTATE. set isbeing bypassed.

User response

This could be due to a storage shortage or otherproblem. The state information is handled as thoughthe token has expired.

AZK7417T AUTOMATED STATE MGMTMODULE (OPASMF) - INVALIDPLIST plist

Explanation

The automated state management routine, OPASMF,was invoked with an invalid parameter list (plist).

User response

The module generates an S0C3 abend to terminate therequest. Contact Software Support.

AZK7418T 'GLVSTATE.setname' MUST EXISTBEFORE UPDATE TO varname

Explanation

The indicated GLVSTATE. collection does not exist. Itmust be created before the update to any collectionmember can be performed.

The GLVSTATE associated setname may also be anindex number.

User response

Create the set before attempting to set the variable.

AZK7419T UPDATE TO csym NOT ALLOWEDFOR GLVSTATE.collectionCOLLECTION WITHSTATUS=status

Explanation

The indicated GLVSTATE. collection is currentlyflagged as being in a status that does not allowupdates. Change the collection to ACTIVE status eitherby resetting it or by deleting and re-creating it.

User response

The current request is rejected.

AZK7420T UPDATE TO 'csym' NOT ALLOWEDBECAUSE val EXCEEDS CURRENTSUBKEY COUNT OF count

Explanation

The number of keyed values within the set is lowerthan the key-index value specified by the symbolicreference. Key-index references may not be used tocreate new keyed value pairs.

User response

The current request is rejected.

The variable fields of the message text are: csymcollection symbol being updated value key index valuein symbolic reference num current number of keysdefined

AZK7421T UPDATE TO 'csym' IGNOREDBECAUSE GLVSTATE.collection ISA typeset TYPE SET WHICH DOESNOT USE HTTP COOKIES

Explanation

The indicated GLVSTATE. collection does not useHTTP cookies as a transport mechanism. The currentupdate is ignored because it does not apply to non-cookie-based information sets.


User response


The variable fields of the message text are: csymcollection symbol being updated collect collectionname value current set type value

AZK7422T UPDATE TO 'csym' IGNOREDBECAUSE GLVSTATE.collection ISA value TYPE SET WHICH DOESNOT USE SERVER-SIDE TOKENS

Explanation

The indicated GLVSTATE. collection does not usetokens as an indirect storage mechanism. The currentupdate is ignored because it does not apply to non-token-based information sets.

User response


The variable fields of the message text are: csymcollection symbol being updated collect collectionname value current set type value

AZK7423T VALUE ASSIGNED TO 'csym'TRUNCATED BECAUSE fieldMAXIMUM LENGTH IS size

Explanation

The indicated GLVSTATE. variable value that was beingassigned was truncated because only lengths up thesize given are supported.

User response


The variable fields of the message text are: csymcollection symbol being updated field field usage sizemaximum size for this field

AZK7425T UPDATE OF 'csym' IGNORED -TOKEN WITH ID=tknid HASALREADY EXPIRED

Explanation

The indicated GLVSTATE. variable value update failedbecause the indicated token has already expired.

User response

The current request is rejected with an error.

The variable fields of the message text are: csymcollection symbol being updated token token id forwhich update required

AZK7426T setname HAS BEEN RESET

Explanation

The indicated GLVSTATE. information set has beenreset.

User response

None. The request completes normally.

AZK7427T NO "SET-COOKIE:" SENT FORGLVSTATE.setname - COOKIEWOULD EXCEED 4K MAX. SIZE

Explanation

The indicated GLVSTATE. information set has not beenused to generate an outbound HTTP Set-cookie:response because the total length of the value data,once encoded, exceeds the maximum 4k allowed bythe Netscape cookie specification for the size of thename/value pair.

User response

The indicated state set is bypassed.

AZK7428T ERROR WHILE BUILDING SET-COOKIE: RESPONSE FORGLVSTATE.setname - RC=rcode

Explanation

An error was encountered while building an outboundSet-cookie: response header for the indicated stateinformation set.

User response

Buffer flush processing continues.

AZK7429T VARIABLE varname CONTAINSINVALID SERVER TOKENID IDWHICH MAY BE SPOOF ATTEMPT(ID=tknid)

Explanation

An error was encountered while attempting to restoresaved state information using a server-side token id.The characteristics of the error encountered MAYindicate an attempt to spoof a server token id value,although this is by no means certain. If the erroroccurs frequently, you may wish to investigate thispossibility further.


User response

The server token id is handled as though it designatesan expired token from which no application datavalues can be restored.

AZK7500I msgtext

Explanation

This is a generic message used for informational levelmessages from RPC programs using the SWSWTOfunction.

User response

None.

AZK7501W msgtext

Explanation

This is a generic message used for warning levelmessages from RPC programs using the SWSWTOfunction.

User response

None.

AZK7502S msgtext

Explanation

This is a generic message used for severe levelmessages from RPC programs using the SWSWTOfunction.

User response

None.

AZK7503H msgtext

Explanation

This is a generic message used for hardcopy levelmessages from RPC programs using the SWSWTOfunction.

User response

none.

AZK8000E Java™ JVM feature is notconfigured.

Explanation

None.

User response


AZK8002E Unable to get the JVM Profile Listfrom the Local Registry.

Explanation

Unable to get the JVM Profile List from the LocalRegistry.

User response

Make sure the Registry is defined to the product.

AZK8003E Unable to build JVM Profile List.

Explanation

Unable to build JVM Profile List.

User response


AZK8004E Unable to allocate latch for JVMprofile.

Explanation

Unable to build JVM Profile List.

User response


AZK8900E errdesc additinfo

Explanation

An error was encountered while attempting to initializea task runtime environment for C-language mainproduct routines.

User response

The runtime environment is not initialized. Check forother messages that might indicate the cause of thefailure, and contact Software Support.


Explanation

While initializing the C-language runtime environment,statistical tracing is enabled. This message is used totrace out information about the environment.

User response

Initialization processing continues.


AZK8902W errdesc additinfo

Explanation

A correctable error was detected while initializing atask runtime environment for C-language mainproduct routines.

User response

The runtime environment is initialized after the error iscorrected.


Explanation

While terminating the C-language runtimeenvironment, statistical tracing is enabled. Thismessage is used to trace out information about theenvironment.

User response

Termination processing continues.

AZK8904W errdesc additinfo

Explanation

A correctable error was detected while terminating atask runtime environment for C-language mainproduct routines.

User response

The runtime environment is terminated if the error iscorrectable. Otherwise, the termination request willfail with a more severe error.

AZK8905E errdesc additinfo

Explanation

While terminating the C-language runtimeenvironment, an error was encountered. Terminationprocessing continues but may leave allocatedresources orphaned.

User response

Termination processing continues.

AZK9000H modname/funcode executionmsgtext

Explanation

This message is used to trace product termination. Amessage is issued before and after the execution ofeach termination routine.

User response

There is no action for this message. This message isonly used for trace and debugging purposes.

AZK9001I Subsystem subsys terminationcomplete

Explanation

This is the standard product termination completemessage.

User response


AZK9002E Subsystem subsys terminationincomplete

Explanation

Product execution has terminated. However, one ormore errors were detected during product termination.As a consequence, normal product termination wasnot possible.

User response

Check for any error messages issued duringtermination. If possible, fix the problem identified bythe error messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport. Please note the exact contents of the aboveerror message and any other error messagesassociated with the product termination error.

AZK9008S ABEND ERROR abcode-rsncode ATmodname+offset

Explanation

A serious abend occurred during product initialization,execution, or termination. The abend was notrecoverable, and the product was forced to terminate.

User response

Check the abend code and any related abendmessages. If possible, fix the problem identified by theerror messages, and restart the product. If theproblem cannot be resolved, contact SoftwareSupport. Note the exact contents of the above errormessage and any other error messages associatedwith the product failure.

AZK9100T INVALID COMBINATION OF ./or ../ in pathname


Explanation

An HFS pathname string was rejected because itcontains an invalid combination of ./, ../, or othercharacters that are not resolvable at runtime.

User response

If the PATH() operand of the matched-to WWW rulecontains a wildcard(*), this may indicate an attempt bya client to refer to an HFS sub-directory to whichaccess should not be granted. This message can alsoresult from an incorrect combination of specificationsfor the server DOCUMENTROOT start-up parameter,the HFSROOT() parameter on a DEFINE RULESETstatement, and/or the PATH() parameter on the WWWrule definition. The transaction is rejected with a 404(file not found) error status.

AZK9504E service OF desc FAILED, RC=rcode,DETECTED AT addr

Explanation

This is a generic error message used to describe awide variety of internal errors. The message textprovides a description of the current operation(service) and what the current operation wasattempting to do, such as GETMAIN, FREEMAIN, andso on.

User response


AZK9505I errdesc

Explanation

This is a generic informational message used to clarifya wide variety of internal errors. The message textprovides further info for the current operation andwhat the current operation was attempting to do.

User response



Explanation


User response


AZK9507E DATA SET dsname DOES NOTEXIST - LOCATE OF dsnameFAILED, RC=rcode,REASON=rsncode

Explanation

A failure occurred during a LOCATE of a data set. Thereturn and reason codes in the message are from theLOCATE routine.

User response


AZK9508E OBTAIN OF FORMAT1 DSCB FORDSNAME dsname VOLUME VidFAILED, RC = rcode, REASONCODE = rsncode

Explanation

A failure occurred during an OBTAIN of a data set. Thereturn and reason codes in the message are from theOBTAIN FORMAT1 DSCB routine.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and retry the operation. If the problemcannot be resolved, contact Software Support toobtain additional assistance.

AZK9509E OBTAIN OF FORMAT1 DSCB FORDSNAME dsname VOLUME Vid


FAILED BECAUSE DATA SET ISMIGRATED

Explanation

A failure occurred during an OBTAIN of a data set. Thedata set volser is set to MIGRAT, indicating the dataset has been migrated offline.

User response

Check the error messages and the return codeassociated with this problem. There may be one ormore error messages referring to the current problem.If possible, fix the problem identified by the errormessages, and retry the operation. For some serverfunctions, you may need to manually recall the dataset before retrying the operation. If the problemcannot be resolved, contact Software Support toobtain additional assistance.

AZK9511E service OF desc FAILED, RC=rcode,RS=rsncode, DETECTED AT addr

Explanation


User response


AZK9513E Unknown I/O reqcd, diaginfo

Explanation

An unknown service request code has been detectedby the server I/O routines. The request cannot beprocessed and an internal ABEND will be generated tolog a symptom record in LOGREC. A general errorreturn code will be reflected to the caller.

User response

Check for other error messages associated with theproblem. There may be one or more error messagesreferring to the current problem or to the componentor feature issuing the request. If the problem cannotbe resolved, contact Software Support to obtainadditional assistance.

AZK9990I msgtext

Explanation

This is a generic message used to format informationrelating to abends detected by the product. The abendmodule, abend offset, abend code, and registers at thetime of abend are all formatted for debuggingpurposes. In the case of internal errors, the reason forthe internal abend is also indicated.

User response

Record all of the information, and report the problemto Software Support.

AZK9998S TEXTMERGE (MSGID=M998)PROCESSING FAILUREREASON=rsncode

Explanation

Invalid parameters were passed to the message sendroutine for a special textmerge function call. This islikely due to a logic error on the part of the callingroutine.

User response

Contact Software Support with this problem

AZK9999S msgtext

Explanation

This message is for internal product testing.

User response



Chapter 2. Data Service server reason codesThe Data Service server produces reason codes that are used for troubleshooting TCP/IP and DRDArelated issues.

Reason codes appear in system messages and driver messages. For example, the following messageincludes 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 internalcontinue query command has been executed and there is notany 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 therequest processing.

Processing: Fails and request is terminated


0X00BAD004 String conversiontruncation

During Code Page Conversion from a source CCSID to a targetCCSID, a string conversion error has occurred which caused atruncation of data.

Processing: Current request may or may not continue


0X00BAD005 String conversioncharacter substitution

During Code Page Conversion from a source CCSID to a targetCCSID, a string conversion error has occurred where a charactersubstitution occurs.



0X00BAD006 String conversion error During Code Page Conversion from a source CCSID to a targetCCSID, a string conversion error has occurred where a charactersubstitution occurs.


Action: See Server Trace for additional details of error. ServerxZKyIN00 may require DEFINE CONV entries to provide SourceCCSID to Target CCSID conversions

0X00BAD007 String conversion tablecorrupt

During Code Page Conversion from a source CCSID to a targetCCSID, the conversion table is not usable.

Processing: Current request is terminated




0X00BAD008 String conversionunknown code page

During Code Page Conversion from a source CCSID to a targetCCSID, 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 hasreturned a column or result set data type that is not known tothe DRDA VRF code base.



0X00BAD00B Abnormal end unit of workcondition occurred

DRDA AS has returned a DRDA code point ABNUOWRMindicating an abnormal unit of work was encountered by the DBServer. For example, the reply message ABNUOWRM may bechained to an SQLCARD data object that carries the name of aresource involved in a deadlock that generated a relationaldatabase rollback operation.



0X00BAD00C Permanent Agent Error DRDA AS has returned a DRDA code point which indicates theServer is failing the request. The Server Trace will normallyreport DRDA Server info in the form of Server Diagnosticmessages as the DB Server provides. One example would becalling a Stored Procedure and the data passed to the SPCgenerated an ABEND via Data Execption. Threads may alsogenerate a Permanent Agent Error when the DRDA VRF has aconnection open in an in-doubt state and z/OS Db2 hasterminated the thread.

Processing: Current request is terminated.

Action: See Server Trace for additional details of error. ForTerminated Threads, a new connection should be establishedand commit / rollback processing should be used to insure theconnection does not enter an in-doubt state for Idle Time set inDb2. For SPC Data Execptions ensure the data passed to StoredProcedures is valid for the data type.

0X00BAD00D Not Authorized To UseCommand

DRDA AS has returned a DRDA code point CMDATHRMindicating the currently authenticated USERID is not authorizedto issue the current command. The error may occur on OpenQuery or other commands.





0X00BAD00E Command Check Error DRDA AS has returned a DRDA code point CMDCHKRM. ReplyMessage indicates that the requested command encounteredan unarchitected condition for which there is no architectedmessage.



0X00BAD00F Command Not Supported DRDA AS has returned a DRDA code point CMDNSPRM. ReplyMessage indicates that the specified command is notrecognized or not supported for the specified target object. Thisreply message can be returned only in accordance with thearchitected rules for DDM sub-setting.



0X00BAD010 Manager Level Conflict DRDA AS has returned a DRDA code point SQLAM orMGRLVLRM that is not supported by the DRDA VRF code base.By default the DRDA VRF requests SQLAM level 8 and the targetDRDA AR should indicate if the DRDA AS supports therequested SQLAM or drops down to a supported SQLAM value.This should not occur unless there is a mismatch in the DRDAAS and the DRDA AR (VRF).

Processing: Current request is terminated and normally willonly occur during the initial DRDA connection.

Action: See Server Trace for additional details of error. If theSQLAM is used on the DEFINE DATABASE be sure to use a valuesupported by the DRDA AS.

0X00BAD011 Manager DependencyError

DRDA AS has returned a DRDA code point MGRDEPRM. ReplyMessage indicates that a request has been made to use amanager, but the requested manager requires specific supportfrom some other manager that is not present.

Processing: Current request is terminated and normally willonly occur during the initial DRDA connection.


0X00BAD012 Unexpected Server Reply(%s (PRCCNVCD))

DRDA AS has returned a DRDA code point PRCCNVRM. ReplyMessage indicates that a conversational protocol erroroccurred. The response displayed is the DRDA AS Server replycode that is not expected.



0X00BAD013 Parameter Not Supported(%s)

DRDA AS has returned a DRDA code point PRMNSPRM. ReplyMessage indicates that the specified parameter is notrecognized or not supported for the specified command. Theresponse displayed is the DRDA AS Server parameter code thatis not expected/supported.



Chapter 2. Data Service server reason codes 237


0X00BAD014 Resource LimitsReached(%s). DiagnosticInfo: %s

DRDA AS has returned a DRDA code point RSCLMTRM. ReplyMessage indicates that the requested command could not becompleted due to insufficient target server resources. Examplesof resource limitations are as follows:

• The target agent has insufficient memory to keep track ofDCLFIL 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 SQLAMmanager because of the target server resource limitations.

The message provide details on the limit reached followed bysome Diagnostic information.



0X00BAD015 Data Stream Syntax Error(%8.8x)

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. TheDRDA AR (VDF) code base will report the syntax error in themessage.


Action: See Server Trace for additional details of error. Contactsoftware supplier with full trace of the error along with versionof 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. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates a length error for an object.





0X00BAD018 Incorrect large objectlength

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates a length error for an large object.



0X00BAD019 Object index notsupported

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates an index value for an object is invalid.



0X00BAD01A Required object not found DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the requirements of theDDM architecture. The target agent terminated parsing of theDSS when the condition SYNERRCD specified was detected. Theerror indicates a required object was not provided in therequest.



0X00BAD01B Too many commandobjects

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that more objects were provided in the requestthan expected.





0X00BAD01C Mutually exclusive objectspresent

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that objects were provided in the request thatmutually exclusive.



0X00BAD01D Too few command objects DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the objects were provided in the request areless than the expected number.



0X00BAD01E Duplicate objects present DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the duplicate objects were provided in therequest.



0X00BAD01F Invalid request correlator DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the request correlator provided is not valid.





0X00BAD020 Required value not found DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that a required request was not provided in therequest.



0X00BAD021 Reserved value notallowed to be set

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that setting of a reserved value is not valid.



0X00BAD022 DSS continuation lessthan two

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the DRDA DSS continuation is not valid.



0X00BAD023 Objects not in requiredorder

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the request objects are not provided in therequired order.





0X00BAD024 DSS chaining and DSSFMTnot correct

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the DRDA DSS chaining is not valid.



0X00BAD025 Different requestcorrelators

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the request correlator is not the expectedcorrelator.



0X00BAD026 Error continuation notallowed for this command

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the request has setup for continuationwhich is not valid for the active command.



0X00BAD027 Mutually exclusiveparameter valuesspecified

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the request has sent Mutually exclusiveparameters.





0X00BAD028 Server cannot handle thiscommand

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror indicates that the DRDA AS does not support therequested command.



0X00BAD029 No detailed informationavailable

DRDA AS has returned a DRDA code point SYNTAXRM. ReplyMessage indicates that the data sent to the target agent doesnot structurally conform to the requirements of the DDMarchitecture. The target agent terminated parsing of the DSSwhen the condition SYNERRCD specified was detected. Theerror that the DRDA AR (VRF) code base does not have code todisplay the SYNERRCD returned.



0X00BAD02A Target Not Supported DRDA AS has returned a DRDA code point TRGNSPRM. ReplyMessage indicates that the object specified as a commandtarget parameter is not an object of a class that the targetserver supports. This condition can arise when a target servercan address objects of classes that DDM or product extensionsto DDM cannot support. It can also arise for valid DDM classesthat the target server does not support. For example, theTRGNSPRM is returned if the name of the object a FILNAM(command target) parameter specifies is either not a file (forinstance, a program library) or is not of a DDM file class (forinstance, a file class the target system does not support).



0X00BAD02B Remote Database NotFound: %s

DRDA AS has returned a DRDA code point RDBNFNRM. ReplyMessage indicates that the target server cannot find thespecified relational database. The message provides the nameof the remote DB that could not be located on the Target DRDAAS.


Action: Verify that the expected database exists on the DBServer or that host IPADDR/DOMAIN and/or port used in theDEFINE DATABASE is correct.



0X00BAD02D Failed to access database%s

DRDA AS has returned a DRDA code point RDBNACRM. ReplyMessage indicates that the access relational databasecommand (ACCRDB) was not issued prior to a commandrequesting RDB services. The message provides the name ofthe remote DB that failed to be accessed on the Target DRDAAS.



0X00BAD02E Connection to applicationserver %s would exceedlimit

DRDA AS has returned a DRDA code point RDBAFLRM. ReplyMessage specifies that the relational database (RDB) failed theattempted connection. The DRDA VRF code base returns thiserror via the SQLCARD object that follows the RDBAFLRM codepoint. The message will explain why the RDB failed theconnection.


Action: See Server Trace for additional details of error and theSQLCODE following the error. Normally indicates the target DBServer cannot accept any new connections.

0X00BAD02F Object not supported DRDA AS has returned a DRDA code point OBJNSPRM. ReplyMessage indicates that the target server does not recognize orsupport the object specified as data in an OBJDSS for thecommand associated with the object. The OBJNSPRM is alsoreturned if an object is found in a valid collection in an OBJDSS(such as the RECAL collection) that is not valid for thatcollection.



0X00BAD030 Descriptor received doesnot match associated data

DRDA AS has returned a DRDA code point DTAMCHRM. ReplyMessage which indicates that:

• The descriptor received did not violate any Formatted DataObject Content Architecture (FD:OCA) or (DRDA) rules andwas successfully assembled.

• The data received did not match the received descriptor. Thatis, the amount of data received did not match the amount ofdata expected.





0X00BAD031 Invalid data descriptor DRDA AS has returned a DRDA code point DSCINVRM. ReplyMessage specifies that a target server manager was unable toassemble a valid Formatted Data Object Content Architecture(FD:OCA) descriptor for the data being sent. The DSCERRCDDRDA code point specifies the reason for the error. This replymessage indicates that the FD:OCA descriptor is invalid eitherbecause it violates FD:OCA rules or (DRDA) rules for theconstruction of an FD:OCA descriptor. The DRDA code pointoffsets for the parameters FDODSCOFF, FDOTRPOFF, andFDOPRMOFF specify the descriptor components that are inerror.



0X00BAD032 Unhandled CodePoint: %s DRDA AS has returned a DRDA code point that is not know tothe DRDA VRF or is not expected at the DRDA protocol codepoint currently active.



0X00BAD033 Codepoint too big DRDA AS has returned a DRDA code point that is larger than theexpected for the DRDA protocol code point currently beingprocessed.



0X00BAD037 SECMEC value notsupported, check formissing user/password

The authentication DRDA code point SECMEC that was returnedor requested via the DEFINE DATABASE SECMEC(...) setting isnot supported by either the DRDA AS or the DRDA AR codebase.


Action: See Server Trace for additional details of error. Select avalid SECMEC setting for the DB Server or modify the DB Serverto accept the requested SECMEC value. Refer to IBMdocumentation on the DB Server authentication methods.



0X00BAD038 DCE Informational Statusissued

The message indicates an error occurred while the DRDA AR(VRF) and the DB Server were processing the authenticationrequest. DRDA AS has returned a DRDA code point SECCHKCDwhich String codifies the security information and condition forthe SECCHKRM. The DRDA protocol documentation providesdetails about the relationship between the SECCHKCDparameter and the DRDA SVRCOD parameter in the SECCHKRM.


Action: See Server Trace for additional details of error as theDRDA VRF code will display additional Server trace messagesduring authentication errors. If the additional information doesnot resolve the reason for the authentication error. Contactsoftware supplier with full trace of the error along with versionof the Db2 and any SQL that is processed. Full DRDA READ/WRITE tracing will provide best diagnostic information.

0X00BAD039 DCE retryable error The message indicates an error occurred while the DRDA AR(VRF) and the DB Server were processing the authenticationrequest. DRDA AS has returned a DRDA code point SECCHKCDwhich String codifies the security information and condition forthe SECCHKRM. The DRDA protocol documentation providesdetails about the relationship between the SECCHKCDparameter and the DRDA SVRCOD parameter in the SECCHKRM.



0X00BAD03A DCE non-retryable error The message indicates an error occurred while the DRDA AR(VRF) and the DB Server were processing the authenticationrequest. DRDA AS has returned a DRDA code point SECCHKCDwhich String codifies the security information and condition forthe SECCHKRM. The DRDA protocol documentation providesdetails about the relationship between the SECCHKCDparameter and the DRDA SVRCOD parameter in the SECCHKRM.





0X00BAD03B GSSAPI InformationalStatus issued




0X00BAD03C GSSAPI retryable error The message indicates an error occurred while the DRDA AR(VRF) and the DB Server were processing the authenticationrequest. DRDA AS has returned a DRDA code point SECCHKCDwhich String codifies the security information and condition forthe SECCHKRM. The DRDA protocol documentation providesdetails about the relationship between the SECCHKCDparameter and the DRDA SVRCOD parameter in the SECCHKRM.



0X00BAD03D GSSAPI non-retryableerror






0X00BAD03E Local Security ServiceInformational Statusissued




0X00BAD03F Local Security Serviceretryable error




0X00BAD041 SECTKN missing onACCSEC when required, orit is invalid

The message indicates an error occurred while the DRDA AR(VRF) and the DB Server were processing the authenticationrequest. DRDA AS has returned a DRDA code point SECCHKCDwhich String codifies the security information and condition forthe SECCHKRM. The DRDA protocol documentation providesdetails about the relationship between the SECCHKCDparameter and the DRDA SVRCOD parameter in the SECCHKRM.This message normally indicates that the encrypted token wasnot found when expected or is invalid.





0X00BAD042 Password expired The message indicates an error occurred while the DRDA AR(VRF) and the DB Server were processing the authenticationrequest. DRDA AS has returned a DRDA code point SECCHKCDwhich String codifies the security information and condition forthe SECCHKRM. The DRDA protocol documentation providesdetails about the relationship between the SECCHKCDparameter and the DRDA SVRCOD parameter in the SECCHKRM.This message indicates that the supplied password has expired.


Action: See Server Trace for additional details of error as theDRDA VRF code will display additional Server trace messagesduring authentication errors. Correct the password expiredproblem and retry the request. If correcting the password doesnot resolve the authentication error. Contact software supplierwith full trace of the error along with version of the Db2 and anySQL that is processed. Full DRDA READ/WRITE tracing willprovide best diagnostic information.

0X00BAD043 User / Password invalid The message indicates an error occurred while the DRDA AR(VRF) and the DB Server were processing the authenticationrequest. DRDA AS has returned a DRDA code point SECCHKCDwhich String codifies the security information and condition forthe SECCHKRM. The DRDA protocol documentation providesdetails about the relationship between the SECCHKCDparameter and the DRDA SVRCOD parameter in the SECCHKRM.This message indicates that the supplied USERID or passwordis invalid.


Action: See Server Trace for additional details of error as theDRDA VRF code will display additional Server trace messagesduring authentication errors. Correct the USERID and orpassword and retry the request. If correcting the request doesnot resolve the authentication error. Contact software supplierwith full trace of the error along with version of the Db2 and anySQL that is processed. Full DRDA READ/WRITE tracing willprovide 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 isinvalid

See Reason code: 0X00BAD043

0X00BAD048 New Password invalid

0X00BAD049 Access to RemoteDatabase %s failed.Reason: %s

0X00BAD04A Commit or Rollback failed



0X00BAD04B Command cannot becompleted. Bind processis active

DRDA AS has returned a DRDA code point PKGBPARM. ReplyMessage indicates that the command cannot be issued whenthe relational database package binding process is active. Theactive package binding process must complete before packagecan be used for execution.


Action: See Server Trace for additional details of error. Makesure package BIND process is complete before accessing theDB Server.

0X00BAD04C Failed to begin the bindprocess

0X00BAD04D Bind process is not active DRDA AS has returned a DRDA code point PKGBNARM. ReplyMessage indicates that a BNDSQLSTT or ENDBND commandwas issued when the package binding process was not activefor the specified package name.



0X00BAD053 No more availablestatements; need moresections in package

The error indicates an internal error occurred during the BINDof a package.



0X00BAD055 Unknown FDOCAdescriptor: %s

The descriptor received did not match the expected. FormattedData Object Content Architecture (FD:OCA) or (DRDA) rules forthe expected descriptor.



0X00BAD059 Data length exceedsmaximum CLOB length fordatabase (%s)

0X00BAD05A Data length exceedsmaximum BLOB length fordatabase (%s)



0X00BAD05C Cursor identified in Fetchstatement is not open

Any attempt was made to close a cursor, but the cursorspecified is not currently being processed.



0X00BAD05F An invalid database Namewas specified

0X00BAD060 An invalid package Namewas specified

DRDA AS has returned a DRDA code point VALNSPRM. ReplyMessage indicates that the parameter value specified is eithernot recognized or not supported for the specified parameter.The codepoint of the command parameter in error is returnedas a parameter in this message. Normally indicates an invalidpackage name.



0X00BAD063 DRDA SQL DiagnosticRecord not NULL

0X00BAD064 Cancel Failed DRDA AS has returned a DRDA code point INTTKNRM. ReplyMessage indicates the target SQLAM has determined that thespecified DRDA RDBINTTKN value is invalid because of one ofthe following:

• The token value does not match the interrupt token valuereturned to the requester on the DRDA ACCRDBRM.

• The requester is not authorized to interrupt the execution of aDDM command.



0X00BAD067 Server does not supportclient's code page (IBMcp-%d)

DRDA AS has returned a DRDA code point VALNSPRM. ReplyMessage which indicates the target CCSID provided to the DBServer is not supported.


Action: See Server Trace for additional details of error. Select avalid CCSID for the DEFINE DATABASE. If the CCSID is valid ormust be supported: Contact software supplier with full trace ofthe error along with version of the Db2 and any SQL that isprocessed. Full DRDA READ/WRITE tracing will provide bestdiagnostic information.



0X00BAD068 Specified securitymechanism (%s)unsupported by server

DRDA AS has returned a DRDA code point SECMEC andassociated SRVCOD to indicate the selected DEFINE DATABASESECMEC(...) is not supported by the DB Server.


Action: See Server Trace for additional details of error. Select asupported SECMEC or modify the DB Server to support therequired SECMEC(...) if a valid SECMEC cannot be selected.Contact software supplier with full trace of the error along withversion of the Db2 and any SQL that is processed. Full DRDAREAD/WRITE tracing will provide best diagnostic information.

0X00BAD069 The SNA protocol is notsupported. Cancelfunctionality notsupported

0X00BAD06A Operation failed due toasynchronous networkcontention. Networksocket closed

0X00BAD06B CALL statement found inexplicit batch

0X00BAD06C AUTHORIZATIONFAILURE: %s. REASON:%s

An attempt was made to generate or decode a Kerberos tokenthat failed.


Action: See Server Trace for additional details of error. Use theFailure and Reason code to determine the Kerberos error. Verifythe Server USERID and the USERID in effect for the connectionhas the RACF Kerberos segment active. Otherwise, contactsoftware supplier with full trace of the error along with versionof the Db2 and any SQL that is processed. Full DRDA READ/WRITE tracing will provide best diagnostic information.

0X00BAD06D zEDC Requested andzEDC is: ( %s ) (%s)

An attempt has been made to connect a DRDA DEFINEDATABASE setup with a zEDC proxy and zEDC is not active forthe Server.


Action: See Server Trace for additional details of error. EnsurezEDC is activated at Server Start-up and does not have anyerrors. Otherwise, contact software supplier with full trace ofthe error along with version of the Db2 and any SQL that isprocessed. Full DRDA READ/WRITE tracing will provide bestdiagnostic information.

0X00BAD06E %s - Access to Distributedis not authorized (%s)

This error is returned when Server is not authorized to accessDistributed data sources. This message is deprecated forcurrent code base.



0X00BAD06F Authentication for requestis not authorized toaccess the specifiedrelational database

DRDA AS has returned a DRDA code point RDBATHRM. ReplyMessage specifies that the requester is not authorized to accessthe specified relational database.


Action: See Server Trace for additional details of error. EnsureUSERID is authorized to access the Database. Otherwise,contact software supplier with full trace of the error along withversion of the Db2 and any SQL that is processed. Full DRDAREAD/WRITE tracing will provide best diagnostic information.

0X00BAD070 Package Isolation level isinvalid

During package BIND the cursor isolation level was found to beinvalid.



0X00C10205 RLI TRANSLATE functionunsupported for DRDA

The requested function is not valid for DRDA connections.


Action: See Server Trace for additional details of error. Contactsoftware supplier with full trace of the error along with versionof the Db2 and any SQL that is processed.

0X00C12201 IDENTIFY invalid inalready-connected state

The requested function is not valid for DRDA connections whichare in a connected state.



0X00C12202 CREATE THREAD invalidwith thread already open

Cannot create a thread when thread is already active for theDRDA connection.



0X00C12203 TERMINATE THREADinvalid, no active thread

Cannot terminate a thread when thread is not active for theDRDA connection.





0X00C12204 Only IDENTIFY requestvalid without prior

Cannot issue IDENTIFY when DRDA connection is not alreadyactive.



0X00C12205 SWITCH TO request forunidentified subsystem

Cannot issue SWITCH to a DRDA SUBSYSTEM that is notalready defined.



0X00C12206 Wrong arg count for DRDARLI request

Internal call to DRDA RLI entry has incorrect parameter count.



0X00C12217 CREATE THREAD invalidbefore SIGNONcompleted

Internal error occurred during CREATE THREAD processing.



0X00C12221 SET_CLIENT_ID invalidbefore CREATE THREAD

Internal error occurred during CREATE THREAD processing.



0X00C19998 SET_CLIENT_ID WLMsetup processing failed

Internal setup processing for Work Load Management failedduring SET_CLIENT_ID process.



0X00C19999 DEFERRED WLM setupprocessing for DRDA linkfailed

Internal setup processing for Work Load Management failedduring DEFERRED WLM process.





0X0FF30011 DRDA RLI request failed,target subsystem inactive

DRDA RLI processing failed due to the target Db2 beinginactive.



0X0FF30013 No authorization forCL(DSNR) subsys.DISTresource

The message indicates an error occurred while the DRDA AR(VRF) and the DB Server were processing the authenticationrequest. DRDA AS has returned a DRDA code point SECCHKCDwhich String codifies the security information and condition forthe SECCHKRM. The DRDA protocol documentation providesdetails about the relationship between the SECCHKCDparameter and the DRDA SVRCOD parameter in the SECCHKRM.This message normally indicated the authentication is valid, butthe USERID is not allowed access.



0X0FF30049 DRDA RLI request failed,LDU is already connected

DRDA RLI processing failed due to the connection already beingactive.



0X0FF30093 TERMINATE THREAD/IDENTIFY invalid withopen unit-of-work

Termination of Thread with open unit of work is not valid.



0X0FF3EEEE Connection setup forDRDA link failed

The connection processing for the DRDA LINK failed.





Chapter 3. IBM Open Data Analytics for z/OS systemmessages

All messages are prefixed with BPXM023I, unless SPARKID has READ access to BPX.CONSOLE in theFACILITY resource class.

AZK5500I STARTING SPARK MASTER TASK

Explanation:The Spark master task is starting.

AZK5501I STOPPING SPARK MASTER TASK

Explanation:The Spark master task is stopping.

AZK5502I STARTING SPARK WORKER TASKFOR MASTER hostname:port

ExplanationThe Spark worker task is starting for the master at thehost name and port that specified.

Where:hostname

Specifies the master host name.port

Specifies the master port.

AZK5503I STOPPING SPARK WORKER TASK

Explanation:The Spark worker task is stopping.

AZK5504I MODIFY COMMAND NOTSUPPORTED. NO FUNCTIONPERFORMED.

Explanation:The MODIFY command is not supported and nofunction is performed.

AZK5505E parmName MUST BE SPECIFIEDOR envvar MUST BE SET

ExplanationYou must either specify a parmName or set envvar inorder for the command to be processed.

Where:parmName

Specifies the name of the parameter.envvar

Specifies the environment variable.

AZK5506E ERROR STOPPING SPARKWORKER TASK FOR MASTER

Explanation:An error occurred while the system attempted to stopthe Spark worker task for the master. The worker taskwas not stopped.

AZK5507E START OF SPARK MASTER TASKFAILED

Explanation:The starting of the Spark master task failed.

AZK5508I SPARK MASTER IS NOT ACTIVEFOR hostname:port WITHPROCESS ID pidvalue

ExplanationThe Spark master for hostname:port with the processID pidvalue is not active. The Spark master must beactive before the Spark worker task can start.

Where:hostname

Specifies the master host name.port

Specifies the master port.pidvalue

Specifies the process ID value.

Before starting the Spark worker, the Spark master'sprocess ID (pidvalue) file is used to determine if aSpark master process is alive. If automation isconfigured, the file that is specified bySPARK_ZOS_MASTER_LOG is used to determine if theSpark master is alive at the master host, master port,and the process ID (pidvalue) specified in the log file.

AZK5509E SPARK MASTER MUST BE ACTIVEPRIOR TO STARTING SPARKWORKER TASK

Explanation:The Spark master must be active before you start theSpark worker task.

AZK5510E START OF SPARK WORKER TASKFAILED

Explanation:The start of the Spark worker task failed.

AZK5511I ONLY ONE WORKER INSTANCESUPPORTED.


SPARK_WORKER_INSTANCESENVVAR DEPRECATED.

Explanation:Only one worker instance is supported at a time. Theenvironment variable, SPARK_WORKER_INSTANCES, isdeprecated.

AZK5512E INCORRECT NUMBER FORMAT INenvvar ENVIRONMENT VARIABLE.VALUE = value

ExplanationAn incorrect number format was used in thespecification of the environment variable.

Where:ennvar

Specifies the environment variable.value

The value that is specified incorrectly in theenvironment variable.

AZK5513E NO VALUE FOUND FOR MSTRHOSTOR MSTRPORT ANDSPARK_ZOS_MASTER_LOG WASNOT SET.

Explanation:No value was found for either or both of the MSTRHOSTor MSTRPORT parameters on the command. Thesystem attempted to retrieve the values that arespecified by SPARK_ZOS_MASTER_LOG, but theenvironment variable was not set in the Spark workertask procedure.

AZK5514E fileName MUST CONTAIN INFOMESSAGE WITH item.sparkConfDir/log4j.properties FILE MUSTHAVE log4j.rootCategory SETTO DEBUG, INFO, OR ALL. VALUEFORlog4j.appender.console.target MUST CORRESPOND TOSETTING IN MASTERPROCEDURE.

ExplanationThe file, fileName, must contain item in an INFO typemessage. INFO type messages are printed to the filewhen sparkConfDir/log4j.properties has thelog4j.rootCategory parameter set to eitherDEBUG, INFO, or ALL. The value that is specified forlog4j.appender.console.target mustcorrespond to the setting that is specified in themaster procedure so that messages are written to thefile.

Where:

fileNameSpecifies the name of the file.

itemSpecifies the item that was expected to be foundin the INFO message.

sparkConfDirThe Spark configuration directory.

AZK5515E envvar ENVIRONMENT VARIABLEMUST BE SET.

ExplanationThe environment variable that is specified must be set.

Where:envvar

Specifies the environment variable.

AZK5516E dirname DIRECTORY MUST EXIST.

ExplanationThe directory name that is specified must exist.

Where:dirname

Specifies the directory name that must exist.

AZK5517E name MUST BE A DIRECTORY.

ExplanationThe name that is specified must be a directory.

nameSpecifies the name that must be a directory.

AZK5518E fileName FILE MUST EXIST

ExplanationThe file that is specified must exist.


AZK5519E name MUST BE A FILE

ExplanationThe name that is specified must be a file.

Where:name

Specifies the name that must be a file.

AZK5520E fileName FILE EXISTS. IFANOTHER TASK IS NOT RUNNING,DELETE THE FILE AND TRY THEREQUEST AGAIN


ExplanationThe file that is specified exists, which can indicate thatanother task of the same type is running. If anothertask of the same type is not running, delete the file andtry the request again.

Where:fileName

Specifies the name of the file.

AZK5521E ERROR CHECKING FOR RUNNINGPROCESS processID

ExplanationAn error occurred while checking for a running processwith the specified process ID.

Where:processID

Specifies the process ID that is being checked toverify it is running.

AZK5522E parmName PARAMETER ALREADYSPECIFIED

ExplanationThe parameter is already specified.

Where:parmName

Specifies the name of the parameter.

AZK5523E parmName PARAMETERREQUIRED

ExplanationThe parameter that is specified is required.

Where:parmName


AZK5524E NUMBER FORMAT EXCEPTION INPARAMETER = parmName WITHVALUE = value

ExplanationA number format exception was found in the specifiedparameter.

Where:parmName

Specifies the name of the parameter.value

Specifies the value with the number formatexception.

AZK5525E INCORRECT PARAMETER FORMATFOUND. CONTACT IBM SERVICE.

Explanation:The parameter was specified in the incorrect format.

AZK5526E parmName PARAMETER NOTALLOWED

ExplanationThe parameter that is specified is not allowed.

Where:parmName


AZK5527E REQUIRED PARAMETERparmName NOT SPECIFIED

ExplanationA required parameter is not specified.

Where:parmName

Specifies the name of the parameter that isrequired.

AZK5528I ONLY ONE SPARK MASTERALLOWED PER CLUSTER

Explanation:Only one Spark master is allowed per cluster. One isalready running.

AZK5529I ONLY ONE SPARK WORKERALLOWED PER CLUSTER

Explanation:Only one Spark worker is allowed per cluster. One isalready running.

AZK5530E SPARK MASTER MIGHT ALREADYBE RUNNING WITH PROCESSID=processID. STOP THE STARTEDTASK OR PROCESS FOR THESPARK MASTER. IF ONE IS NOTRUNNING, DELETE FILE fileNameAND TRY THE REQUEST AGAIN.

ExplanationThe Spark master might already be running with thespecified process ID. If there is an active started taskor process on the system for the Spark master, stop it.Otherwise, delete the specified file and try the requestagain.

Where:processID

Specifies the process ID that is being used.fileName


Chapter 3. IBM Open Data Analytics for z/OS system messages 259

AZK5531E SPARK WORKER MIGHT ALREADYBE RUNNING WITH PROCESSID=processID. STOP THE STARTEDTASK OR PROCESS FOR THESPARK WORKER. IF ONE IS NOTRUNNING, DELETE FILE fileNameAND TRY THE REQUEST AGAIN.

ExplanationThe Spark worker might already be running with thespecified process ID. If there is an active started taskor process on the system for the Spark worker, stop it.Otherwise, delete the specified file and try the requestagain.

Where:processID

Specifies the process ID that is being used.fileName


AZK5532I MAXIMUM NUMBER OF SPARKMASTER TASKS MIGHT ALREADYBE RUNNING.

Explanation:The maximum number of Spark master tasks mightalready be running.

AZK5533I MAXIMUM NUMBER OF SPARKWORKER TASKS MIGHT ALREADYBE RUNNING.

Explanation:The maximum number of Spark worker tasks mightalready be running.

AZK5534E numberAllowed SPARK MASTERSOR WORKERS ALLOWED PERCLUSTER. STOP THE STARTEDTASKS OR PROCESSES FOR THESPARK MASTERS OR WORKERSOR DO NOT ATTEMPT TO STARTMORE THAN ARE CONFIGURED. IFONE OR MORE ARE NOTRUNNING, DELETE FILES SIMILARTO fileName AND TRY THEREQUEST AGAIN.

ExplanationThe number of Spark masters or workers allowed percluster is numberAllowed. You must stop the startedtasks or processes for the Spark masters or workers.Do not attempt to start more tasks than areconfigured. If one or more tasks are not running,delete the specified file and try the request again.

Where:

numberAllowedSpecifies the number of tasks or processes thatare allowed per cluster.


AZK5535I SPARK MASTER MUST BE ACTIVEBEFORE WORKER CAN START.WAITING AND RETRYING.

Explanation:The Spark master must be active before the workercan start. The system waits and tries restarting theworker for a period of time to allow the master time tostart.

AZK5536E MAXIMUM RETRIES REACHED.TRY THE REQUEST AGAIN AFTERTHE SPARK MASTER HASSTARTED.

Explanation:While waiting for the Spark master to start, the Sparkworker task has attempted to start for the maximumnumber of retries. After the Spark master is started, trythe request again.

AZK5537E UNABLE TO READ FROMDIRECTORY dirname

ExplanationThe system is unable to read from the specifieddirectory.

Where:dirname

Specifies the name of the directory.

AZK5538E UNABLE TO WRITE TO FILEfileName

ExplanationThe system is unable to write to the specified file.

Where:fileName


AZK5539E UNABLE TO DELETE FILE fileName

ExplanationThe system is unable to delete the specified file.

Where:fileName


AZK5540E MASTER TASK AND WORKERTASK MUST BE STARTED BY THESAME USER. MASTER TASK WAS


STARTED BY xxxxxxxx ANDWORKER TASK IS BEINGSTARTED BY yyyyyyyy.

Explanation:When the worker is starting, the system looks in thePID file created when the master started to ensure themaster identified by the master's log file is active. Ifthe master and the worker are not started by the sameuser and the user starting the worker does not haveUID(0), the operation will fail. To avoid this failure,start the master and the worker with the same user.

AZK5541I ONLY ONE SPARK HISTORYSERVER ALLOWED PER CLUSTER

Explanation:Only one History Server instance is supported at atime. AZK5542E accompanies this message.

AZK5542E SPARK HISTORY SERVER MIGHTALREADY BE RUNNING WITHPROCESS ID=%s. STOP THESTARTED TASK OR PROCESS FORTHE SPARK HISTORY SERVER. IFONE IS NOT RUNNING, DELETEFILE %s AND TRY THE REQUESTAGAIN.

Explanation:Only one History Server instance is supported at atime. A user might have started history server for thiscluster already, or started it with $SPARK_HOME/sbin/start-history-server.sh. Or the file indicated may be olddata that is giving a false indication that the historyserver is running.

AZK5543I STARTING SPARK HISTORYSERVER TASK

Explanation:The Spark History Server task is starting.

AZK5544E START OF SPARK HISTORYSERVER FAILED

Explanation:The starting of the Spark History Server task failed.See other SYSLOG messages and job output for othermessages indicating the cause of the problem.

AZK5545I STOPPING SPARK HISTORYSERVER TASK

Explanation:The Spark History Server task is stopping.

AZK5546I ONLY ONE SPARK SHUFFLESERVICE ALLOWED PER CLUSTER

Explanation:Only one Shuffle service instance is supported at atime. AZK5547E accompanies this message.

AZK5547E SPARK SHUFFLE SERVICE MIGHTALREADY BE RUNNING WITHPROCESS ID=%s. STOP THESTARTED TASK OR PROCESS FORTHE SPARK SHUFFLE SERVICE. IFONE IS NOT RUNNING, DELETEFILE %s AND TRY THE REQUESTAGAIN.

Explanation:Only one Shuffle service instance is supported at atime. A user might have started history server for thiscluster already, or started it with $SPARK_HOME/sbin/start-shuffle-service.sh. Or the file indicated may beold data that is giving a false indication that the Shuffleservice is running.

AZK5548I STARTING SPARK SHUFFLESERVICE TASK

Explanation:The Spark Shuffle service task is starting.

AZK5549E START OF SPARK SHUFFLESERVICE FAILED

Explanation:The starting of the Spark Shuffle service task failed.See other SYSLOG messages and job output for othermessages indicating the cause of the problem.

AZK5550I STOPPING SPARK SHUFFLESERVICE TASK

Explanation:The Spark Shuffle service task is stopping.

Chapter 3. IBM Open Data Analytics for z/OS system messages 261


Accessibility

The publications for IBM Open Data Analytics for z/OS are available in IBM Knowledge Center and AdobePortable Document Format (PDF) and comply with accessibility standards. If you experience difficultieswhen you use any of the information, notify IBM through one of the comment methods described in “Howto send your comments to IBM” on page vii.



Notices

This information was developed for products and services offered in the U.S.A. or elsewhere.

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 inyour area. Any reference to an IBM product, program, or service is not intended to state or imply that onlythat IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property right may be used instead. However, it is theuser'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 thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress 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 periodicallymade 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 thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe 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 withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

Site CounselIBM Corporation2455 South RoadPoughkeepsie, NY 12601-5400USA


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 providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, orany equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

COPYRIGHT LICENSE:

This information might contain sample application programs in source language, which illustrateprogramming techniques on various operating platforms. You may copy, modify, and distribute thesesample programs in any form without payment to IBM, for the purposes of developing, using, marketingor distributing application programs conforming to the application programming interface for theoperating platform for which the sample programs are written. These examples have not been thoroughlytested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, orfunction of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBMshall not be liable for any damages arising out of your use of the sample programs.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at"Copyright and trademark information" (www.ibm.com/legal/copytrade.shtml).

Rocket is a registered trademark of Rocket Software, Inc.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle, itsaffiliates, or both.

UNIX is a registered trademark of The Open Group in the United States, other countries, or both.

Linux® is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Index

Aaccessibility

contact IBM 263

Cconversion CCSID 235

Ffeedback vii

Mmessages

IBM Open Data Analytics for z/OS 257

NNotices 265

Ssending to IBM

reader comments viisummary of changes for IBM Open Data Analytics for z/OSSystem Messages ix

UUnicode 235

Index 267


IBM®

GC27-9415-00

Documents

Open Data Analytics for z/OS : IBM Open Data Analytics for ... · Open Data Analytics for z/OS Version 1 Release 1 System Messages IBM GC27-9415-00