CICS TS for z/OS 4.2: CICS Messages and Codes Vol 2publibfi.dhe.ibm.com/epubs/pdf/dfhgae01.pdf · CICS Transaction Server messages and abend code descriptions (with the exception

CICS Transaction Server for z/OSVersion 4 Release 2

CICS Messages and Codes Vol 2

GC34-7176-01

NoteBefore using this information and the product it supports, read the information in Notices on page 895.

This edition applies to Version 4 Release 2 of CICS Transaction Server for z/OS (product number 5655-S97) and toall subsequent releases and modifications until otherwise indicated in new editions.

Copyright IBM Corporation 1977, 2012.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . vWhat this manual is about. . . . . . . . . . vWho this manual is for . . . . . . . . . . . vWhat you need to know to understand this manual vHow to use this manual . . . . . . . . . . vOnline messages and Codes . . . . . . . . . v

Changes in CICS Transaction Serverfor z/OS, Version 4 Release 2 . . . . . vii

Chapter 1. AXM server environmentmessages . . . . . . . . . . . . . . 1REQTEXT . . . . . . . . . . . . . . . 1

AXM error recovery messages . . . . . . . 1AXM event management messages . . . . . . 2AXM stack (LIFO) storage messages . . . . . 2AXM lock management messages . . . . . . 3AXM operating system interface messages . . . 3AXM storage page pool management messages. . 3AXM resource tracking messages . . . . . . 4AXM server connection and system servicesmessages . . . . . . . . . . . . . . 4AXM subsystem initialization messages . . . . 8AXM system region messages . . . . . . . 9AXM trace and print file management messages 10AXM address lookup (WHERE) messages . . . 10AXM cross-memory interface messages . . . . 11

Chapter 2. Transaction abend codes . . 13AAxx abend codes . . . . . . . . . . . . 14ABxx abend codes . . . . . . . . . . . . 26ACxx abend codes . . . . . . . . . . . . 42ADxx abend codes . . . . . . . . . . . . 67AExx abend codes . . . . . . . . . . . . 81AFxx abend codes . . . . . . . . . . . . 102AGxx abend code . . . . . . . . . . . . 109AIxx abend codes . . . . . . . . . . . . 110AJxx abend codes . . . . . . . . . . . . 127AKxx abend codes . . . . . . . . . . . 130ALxx abend codes. . . . . . . . . . . . 136AMxx abend codes . . . . . . . . . . . 139ANxx abend codes . . . . . . . . . . . 142AOxx abend codes . . . . . . . . . . . 143APxx abend codes . . . . . . . . . . . . 143ARxx abend codes. . . . . . . . . . . . 156ASxx abend codes . . . . . . . . . . . . 162ATxx abend codes . . . . . . . . . . . . 176AUxx abend codes . . . . . . . . . . . 190AWxx abend codes . . . . . . . . . . . 190AXxx abend codes. . . . . . . . . . . . 197AZxx abend codes. . . . . . . . . . . . 205

Chapter 3. System abend and dumpcodes. . . . . . . . . . . . . . . 225

CICS system dump codes . . . . . . . . . 225DHxx (IMS) abend codes . . . . . . . . . 22601xx (translator) abend codes . . . . . . . . 22602xx (DFHPD670) abend codes . . . . . . . 22703xx (DFHCSDUP) abend codes . . . . . . . 22704xx (external CICS interface) abend codes . . . 23005xx CICS JVM Interface abend codes . . . . . 2334xxx LE/370 abend codes . . . . . . . . . 233

Chapter 4. DFH messages - DFHN toDFHZ . . . . . . . . . . . . . . . 235CICS DFH message Identifiers. . . . . . . . 235

DFHnnnn identifiers . . . . . . . . . . 235DFHccnnnn identifiers . . . . . . . . . 236Action codes . . . . . . . . . . . . 238Severity codes . . . . . . . . . . . . 239

Format of message information . . . . . . . 239XMEOUT parameters. . . . . . . . . . 241Route codes . . . . . . . . . . . . . 241Message editing . . . . . . . . . . . 242Console message reformatting . . . . . . . 242Terminal identifiers . . . . . . . . . . 242Abend code inserts . . . . . . . . . . 242Dumps . . . . . . . . . . . . . . 242Terminology. . . . . . . . . . . . . 242

Katakana terminal devices . . . . . . . . . 243MVS user abend codes . . . . . . . . . . 243DFHNCnnnn messages . . . . . . . . . . 245DFHNQnnnn messages . . . . . . . . . . 261DFHOTnnnn messages . . . . . . . . . . 264DFHPAnnnn messages . . . . . . . . . . 266DFHPCnnnn messages . . . . . . . . . . 278DFHPDnnnn messages . . . . . . . . . . 278DFHPGnnnn messages . . . . . . . . . . 283DFHPInnnn messages . . . . . . . . . . 289DFHPRnnnn messages . . . . . . . . . . 369DFHPSnnnn messages . . . . . . . . . . 370DFHPTnnnn messages . . . . . . . . . . 371DFHRDnnnn messages . . . . . . . . . . 372DFHREGxx EJBROLE generator utility messages 376DFHRLnnnn messages . . . . . . . . . . 377DFHRMnnnn messages . . . . . . . . . . 382DFHRPnnnn messages . . . . . . . . . . 408DFHRSnnnn messages . . . . . . . . . . 478DFHRTnnnn messages . . . . . . . . . . 494DFHRUnnnn message . . . . . . . . . . 499DFHRXnnnn messages . . . . . . . . . . 499DFHRZnnnn messages . . . . . . . . . . 502DFHSHnnnn messages . . . . . . . . . . 504DFHSInnnn messages . . . . . . . . . . 507DFHSJnnnn messages . . . . . . . . . . 519DFHSKnnnn messages . . . . . . . . . . 539DFHSMnnnn messages . . . . . . . . . . 540DFHSNnnnn messages . . . . . . . . . . 547DFHSOnnnn messages . . . . . . . . . . 555

Copyright IBM Corp. 1977, 2012 iii

DFHSRnnnn messages . . . . . . . . . . 566DFHSTnnnn messages . . . . . . . . . . 569DFHSZnnnn messages . . . . . . . . . . 577DFHTCnnnn messages . . . . . . . . . . 589DFHTDnnnn messages . . . . . . . . . . 598DFHTFnnnn messages . . . . . . . . . . 611DFHTInnnn messages . . . . . . . . . . 612DFHTMnnnn messages . . . . . . . . . . 613DFHTOnnnn messages . . . . . . . . . . 616DFHTPnnnn messages . . . . . . . . . . 621DFHTRnnnn messages . . . . . . . . . . 628DFHTSnnnn messages . . . . . . . . . . 639DFHUPnnnn messages . . . . . . . . . . 646DFHUSnnnn messages . . . . . . . . . . 647DFHW2nnnn messages . . . . . . . . . . 650DFHWBnnnn messages . . . . . . . . . . 656DFHWUnnnn messages . . . . . . . . . . 680DFHXAnnnn messages . . . . . . . . . . 690DFHXCnnnn messages . . . . . . . . . . 696DFHXGnnnn messages . . . . . . . . . . 708

DFHXMnnnn messages . . . . . . . . . . 722DFHXOnnnn messages . . . . . . . . . . 732DFHXQnnnn messages . . . . . . . . . . 734DFHXSnnnn messages . . . . . . . . . . 752DFHZCnnnn messages . . . . . . . . . . 761DFHZEnnnn messages . . . . . . . . . . 892DFHZNnnnn messages . . . . . . . . . . 892

Notices . . . . . . . . . . . . . . 895Trademarks . . . . . . . . . . . . . . 896

Bibliography. . . . . . . . . . . . 897CICS books for CICS Transaction Server for z/OS 897CICSPlex SM books for CICS Transaction Serverfor z/OS . . . . . . . . . . . . . . . 898Other CICS publications . . . . . . . . . . 898

Accessibility . . . . . . . . . . . . 899

iv CICS TS for z/OS 4.2: CICS Messages and Codes Vol 2

Preface

What this manual is aboutThis manual contains messages unique to CICS Transaction Server Version 4Release 2 and is intended for use as a quick reference. It is closely linked with theCICS Problem Determination Guide which you can consult if a message indicates thatthere is a CICS problem. For information about problem determination, seeProblem determination overview in Problem Determination.

This manual is volume 2 of the CICS messages and codes. It explains the format ofDFH messages and contains CICS messages that are prefixed DFHNC to DFHZN.It also contains the AXM server environment messages, transaction abend codes,and system abend codes. To look up messages that are prefixed DFH01 to DFHMV,see CICS messages and codes overview in Messages and Codes Vol 1.

Who this manual is forThis manual is for anybody who needs to understand and respond to CICSmessages, including system operators, system programmers, and certain terminalusers.

What you need to know to understand this manualYou can refer to this manual for the meaning of a message without understandingthe manual as a whole. Your understanding of CICS Transaction Server Version 4Release 2, however, will be enhanced by a knowledge of the types of messageCICS produces, the different places it sends messages, and the different audiencesit intends to reach.

How to use this manualWhen you are using CICS as a system operator or terminal user, or scanning aqueue containing CICS messages, use this manual as a reference. If you want tosuggest a change to the contents of a message or an abend code, please contactyour IBM branch instead of raising an RCF.

Online messages and CodesCICS Transaction Server messages and abend code descriptions (with the exceptionof AXM messages, a small number of numeric abends and Transaction DumpCodes) are available online using the CICS transaction CMAC. For guidance onusing CMAC, see CICS supplied transactions descriptions in CICS SuppliedTransactions.

Copyright IBM Corp. 1977, 2012 v
http://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.doc/dfhs1/topics/dfhs1_overview.htmlhttp://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.messages.doc/cics_mc/dfhg4_overview.htmlhttp://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topics/com.ibm.cics.ts.systemprogramming.doc/topics/dfha7_cst_descriptions.htmlhttp://publib.boulder.ibm.com/infocenter/cicsts/v4r2/topics/com.ibm.cics.ts.systemprogramming.doc/topics/dfha7_cst_descriptions.html

vi CICS TS for z/OS 4.2: CICS Messages and Codes Vol 2

Changes in CICS Transaction Server for z/OS, Version 4Release 2

For information about changes that have been made in this release, please refer toWhat's New in the information center, or the following publications:v CICS Transaction Server for z/OS What's Newv CICS Transaction Server for z/OS Upgrading from CICS TS Version 4.1v CICS Transaction Server for z/OS Upgrading from CICS TS Version 3.2v CICS Transaction Server for z/OS Upgrading from CICS TS Version 3.1

Any technical changes that are made to the text after release are indicated by avertical bar (|) to the left of each new or changed line of information.

Copyright IBM Corp. 1977, 2012 vii

viii CICS TS for z/OS 4.2: CICS Messages and Codes Vol 2

Chapter 1. AXM server environment messages

The following messages are issued by the authorized cross-memory (AXM) serverenvironment, which is a package of run-time services used by the Named countersequence number server, CICS coupling facility (CF) data tables and the CICSshared temporary storage (TS) queue pool server. See the CICS System DefinitionGuide for more information about AXM and the CICS TS queue pool server.

Note:

1. AXM messages are not issued by a CICS region and hence do not use the CICSmessage domain. They cannot be viewed with the CMAC transaction,suppressed with the XMEOUT user exit, or changed with the message editingutility.

2. These messages are normally displayed in mixed case English. If your terminalscannot display lowercase English characters, see the CICS Customization Guidefor guidance on converting the messages to uppercase.

REQTEXT

AXM error recovery messages

AXMER0001 ABEND xxx-rr occurred at address, dataword1 word2 word3.

Explanation: The AXM error recovery routine hasintercepted an abend in a task running under an AXMserver region TCB. The abend code is shown as threehexadecimal digits for a system completion code orfour decimal digits for a user completion code. Thedata consists of the twelve bytes around the PSWaddress as provided by MVS in the SDWA.

System action: The error recovery routine will firstcall AXMWH which attempts to identify the moduleand procedure in which the abend occurred and writesout a further message if successful. After this, ifrecovery is allowed, the error recovery routineterminates the affected AXM internal task and resumesnormal processing, otherwise it percolates the error,causing the server region to be abnormally terminated.

The system will normally produce a symptom dumpmessage on the job log, and a full dump may beproduced if an appropriate DD statement (SYSUDUMP,SYSMDUMP or SYSABEND) is present in the serverregion JCL.

User response: Look up the completion code toidentify the cause of the abend.

Module: AXMER

Destination: Console and print file

AXMER0002 TRAP occurred at offset offset inprocname.

Explanation: An internal logic error in a serverresulted in a TRAP macro being executed at thespecified location.

The system will normally produce a symptom dumpmessage on the job log, and a full dump may beproduced if an appropriate DD statement (SYSUDUMP,SYSMDUMP or SYSABEND) is present in the serverregion JCL.

System action: The AXM task is abnormallyterminated.

User response: This probably indicates a logic error inserver code, or an attempt to use some internalcomponent of the server outside its correct context.

If the procedure name in the message begins withAXM, this probably indicates that the server codewhich called it has passed inconsistent parameters,such as an invalid address when releasing mainstorage.

Module: AXMER


Copyright IBM Corp. 1977, 2012 1

AXM event management messages

AXMEV0001 AXM only supports operating systemWAIT on MVS.

Explanation: An attempt has been made to issue anoperating system WAIT within an AXM server, but theserver is not running on MVS. In this case, the MVSPOST exit mechanism used by AXM is unavailable andoperating system waits cannot be supported.

System action: The program is abnormally terminated.

User response: None.

Module: AXMEV

Destination: Console

AXMEV0003 The AXM POST exit could not becreated because AXM system servicesare not available.

Explanation: AXM server region initialization neededto define the MVS POST exit used by AXM foroperating system waits, but AXM system services werenot available within the current MVS image.

System action: The server region is terminated withreturn code 8.

User response: Start up AXM system services firstthen restart the server region. AXM system services arenormally started at IPL using a subsystem definition inIEASSNxx specifying AXM as the subsystem name andAXMSI as the initialization routine. They can also bestarted up without an IPL by defining the subsystemdynamically using the SETSSI command.

Module: AXMEV


AXMEV0004 The AXM POST exit could not becreated, return code was rc.

Explanation: The MVS POST exit used by AXM foroperating system waits could not be created becausethe AXM system services routine gave a non-zeroreturn code. The only known reason for this is that

AXM system services have been withdrawn, whichshould not be possible in a production environment.



Module: AXMEV


AXMEV0005I The AXM POST exit had already beencreated for this address space.

Explanation: During server initialization, AXM systemservices found that the MVS POST exit used by AXMfor operating system waits had already been created forthis address space. AXM therefore bypassed trying tocreate the same POST exit again as this would haveresulted in an abend 702-04.

This can occur when a previous server execution in thesame address space was terminated abnormally.

System action: Processing continues


Module: AXMEV


AXMEV0006I The AXM POST exit could not bedeleted, return code was rc.

Explanation: The MVS POST exit used by AXM foroperating system waits could not be deleted becausethe AXM system services routine gave a non-zeroreturn code. The only known reason for this is thatAXM system services have been withdrawn, whichshould not be possible in a production environment.

System action: Processing continues.


Module: AXMEV

Destination: Console.

AXM stack (LIFO) storage messages

AXMLF0001S LIFO storage cannot be set up becausethe PRV size exceeds 4K.

Explanation: AXM initialization has detected that thetotal link-edited size of the pseudo-register vector(PRV) for the server application load module exceedsthe maximum size of 4096 supported by AXM. ThePRV contains task-related variables used by AXMresource management plus any task-related data areasdefined by server code using the Assembler DXDoperation code or Q-type address constants.

System action: The server is abnormally terminated.

User response: The server programmer needs todecrease the size of task-related variables defined in thePRV. When a large amount of task-related informationneeds to be stored, it is better to store the informationin some separately acquired storage area (such as AXMheap storage) and put only a pointer to it in the PRV.

Module: AXMLF


AXMEV0001 AXMLF0001S

2 CICS TS for z/OS 4.2: CICS Messages and Codes Vol 2

AXM lock management messages

AXMLK0001 Lock at address is already owned forshared use by this task.

Explanation: An AXM server program attempted toacquire exclusive ownership of an AXM lock whichwas already in shared ownership for the current task.This is not allowed, as the task cannot wait for itself.

System action: The AXM lock request is rejected.

User response: The server programmer needs tomodify the program logic. It could for example use anAXM lock PROMOTE to convert the shared lock to anexclusive lock.

Module: AXMLK


AXMLK0002 function failed because lock at address isnot owned by this task.

Explanation: An AXM server program tried to release,demote or promote an AXM lock but the lock was notowned by the current AXM task.

System action: The AXM lock request is rejected.

User response: The server program logic is in error.

Module: AXMLK


AXM operating system interface messages

AXMOS0001I The main procedure entry point isname at address address.

Explanation: This message is written to the print fileduring AXM initialization to indicate the name andentry point address of the server main procedure. Thisis primarily for debugging purposes.



Module: AXMOS

Destination: Print file

AXMOS0002 The main procedure is missing, or theEND statement does not name the entrypoint.

Explanation: The AXM server load module which isbeing executed does not contain a procedure which hasbeen identified as the AXM main procedure.


User response: Check that the main procedure wascorrectly included in the link edit. If it was, make surethat its entry point name was correctly specified on theEND statement and that it was assembled using AXMmacros with the macro AXMSET appearing before theMODULE statement and the option ENVIRON=AXMspecified on the MODULE statement.

Module: AXMOS

Destination: Console and SYSPRINT

AXM storage page pool management messages

AXMPG0001I The main free area above 16M was ataddress xxxxxx, size nnnnK.

Explanation: This message is written to the print fileduring AXM initialization to indicate the size of thelargest area of 31-bit addressable private region storageavailable at that time.



Module: AXMPG


AXMPG0002I The main free area below 16M was ataddress xxxxxx1, size nnnnK.

Explanation: This message is written to the print fileduring AXM initialization to indicate the size of thelargest area of 24-bit addressable private region storageavailable at that time.



Module: AXMPG


AXMPG0003I Storage page pool areaname created,address xxxxxx, size nnnnK.

Explanation: This message is written to the print fileduring AXM initialization to show the size and addressof each storage page pool as it is created. Once this hasbeen done, most AXM storage requests are allocatedfrom this page pool rather than with MVS GETMAIN.



Module: AXMPG


AXMLK0001 AXMPG0003I

Chapter 1. AXM server environment messages 3

AXMPG0004I Usage statistics for storage page poolareaname:

Explanation: This message shows statistics for thenamed storage page pool (since the most recentstatistics reset, if any). It is automatically written to theprint file at AXM region termination, and may also berequested at other times by the server.

The detailed message layout is as follows:

Size In Use Max Used Free Min FreenK nK nK nK nK

100% n% n% n% n%Gets Frees Retries Fails

n n n n

Each of the storage statistics is shown in two forms, asa number of kilobytes and as a percentage of the totalsize.

The individual fields have the following meanings:

Size Total size of the storage pool.

In Use The amount of storage which is currently inuse.

Max UsedThe highest amount of storage which has beenin use.

Free The amount of storage within the pool whichis current free.

Min FreeThe lowest amount of storage which has beenfree.

Gets The number of requests to obtain storagewithin the pool.

Frees The number of requests to release storagewithin the pool.

Retries The number of times that a storage requestinitially failed and was retried after mergingany adjacent small free areas to form largerareas.

Fails The number of times that a storage requestwas unable to obtain the requested amount ofstorage even after a retry.



Module: AXMPG


AXM resource tracking messages

AXMRS0001 Tidy-up routine at address failed to freeresource tracking cell.

Explanation: A server routine established an AXMresource tracking element specifying that a procedurewas to be called to release the resource if the task wasterminated without releasing the resource. The AXMtask is now terminating, and the procedure identifiedin the tracking element was called, but the resourcetracking element was still in existence when it returned.The entry point address of the relevant procedure isindicated in the message.

System action: The tracking element is released on theassumption that the resource has now been deleted,and AXM task termination continues.

User response: The server programmer needs toensure that the procedure to release the resource alsofrees the resource tracking element.

Module: AXMRS


AXM server connection and system services messages

AXMSC0011I AXM system services initialization isin progress.

Explanation: AXM system services are being startedup, normally as a result of being called by the AXMsubsystem initialization routine.



Module: AXMSC


AXMSC0012I AXM system services initializationhas completed.

Explanation: AXM system services are now fullyavailable in the current MVS image.

System action: AXM cross-memory server connectionrequests and requests for the POST exit system serviceswill now be accepted.


Module: AXMSC


AXMSC0013 AXM system services have already beeninitialized.

Explanation: An attempt was made to set up AXM

AXMPG0004I AXMSC0013


system services again when they are already active inthe current MVS image.

System action: The attempt is ignored.


Module: AXMSC


AXMSC0021I AXM system services termination is inprogress.

Explanation: AXM system services are beingwithdrawn. This is only possible if they were initializedusing the AXM system region program AXMSR insteadof being set up via subsystem initialization.

System action: The AXM system services program calltable is deleted and all entry points in the AXM systemservices anchor are replaced with dummy routineswhich return an indication that the service are notavailable.

User response: Note that the results of attempting tocall any AXM system service around this time areunpredictable. AXM system services should never bewithdrawn in a production environment at any timewhen it is possible that they could be in use.

Module: AXMSC


AXMSC0022I AXM system services termination hascompleted.

Explanation: AXM system services have been closeddown for this MVS image.

System action: AXM system services are no longeravailable.


Module: AXMSC


AXMSC0031I Connection to server prefix.name hasbeen opened.

Explanation: The current region has established anAXM connection to the AXM server prefix.name.



Module: AXMSC


AXMSC0032 Connection to server prefix.name failedbecause the server was not found.

Explanation: The current region tried to establish anAXM connection to the AXM server prefix.name butcould not do so because there is no active server of thatname enabled for AXM connections.

System action: The connection attempt is rejected withreturn code 8, reason code 32.

User response: Ensure that the server is started andthat its name was specified correctly.

Module: AXMSC


AXMSC0033 Connection to server prefix.name wasrejected by the security system.

Explanation: The current region tried to establish anAXM connection to the AXM server prefix.name but therequest was rejected by the security system.

System action: The connection attempt is rejected withreturn code 8, reason code 33.

User response: See the previous AXM message givingdetails of the results of the security check.

Module: AXMSC


AXMSC0034 Connection to server prefix.name failedbecause all AXM connections are in use.

Explanation: The current region tried to establish anAXM connection to the AXM server prefix.name but themaximum number of AXM connections supportedwithin an MVS image (currently 4096) has beenreached.

System action: The connection is rejected with returncode 8, reason code 34.

User response: If you anticipate a need for more than4096 AXM server connections within a single MVSimage, you will need assistance from IBM. See the CICSProblem Determination Guide for guidance on how toproceed.

Module: AXMSC


AXMSC0035 Connection to server prefix.name failedbecause request limit reqs exceeds 9999.

Explanation: The current region tried to establish anAXM connection to the AXM server prefix.name but theconnection parameter specifying the maximum numberof concurrent requests to be supported exceeds 9999.


AXMSC0021I AXMSC0035


User response: Check whether the server interfaceprogram is specifying the correct value for themaximum number of concurrent requests.

Module: AXMSC


AXMSC0036 Connection to server prefix.name wasrejected by the server.

Explanation: The current region tried to establish anAXM connection to the AXM server prefix.name but theserver-defined connection exit rejected the request.


User response: The reason for the rejection dependson the server code, but this typically occurs if theserver is preparing to close down or has insufficientresources to accept another connection.

Module: AXMSC


AXMSC0037 Connection to server prefix.name failedbecause the server is terminating.

Explanation: The current region tried to establish anAXM connection to the AXM server prefix.name but theserver entered termination processing while theconnection request was in progress.

System action: The connection is rejected with returncode 8, reason code 37. The instance of the server thatwas being terminated will no longer be visible to anynew connection attempts.

User response: Retry the connection when the serverhas been restarted.

Module: AXMSC


AXMSC0038 Connection to server prefix.name failedbecause this address space is alreadyconnected to it.

Explanation: The current region tried to establish anAXM connection to the AXM server prefix.name but italready has a connection to the same server region.AXM does not support multiple connections from thesame region to the same server region.



Module: AXMSC


AXMSC0041I Connection to server prefix.name hasbeen closed.

Explanation: An AXM connection from the currentregion to the named server has been terminated, eitheras a result of being explicitly closed by this region or asa result of the termination of the MVS TCB whichoriginally established the connection.



Module: AXMSC


AXMSC0042 Connection close failed for tokenxxxxxxxx, reason is n.

Explanation: An attempt was made to close an AXMconnection explicitly but the specified connection tokendid not refer to an active connection owned by thecurrent region, or the connection could not be closedfor some other reason.

The reason code indicates which validity check failedwithin procedure AXMSCCLS. Reason code 9 indicatesthat a request issued via the connection has not yetcompleted. Any other reason code probably indicatesan incorrect token.

System action: The attempt is rejected with returncode 8, reason code 42.

User response: Check that the connection closerequest is specifying the correct connection token andthat there are no incomplete requests for theconnection.

Module: AXMSC


AXMSC0051I Server prefix.name is now enabled forconnections.

Explanation: This AXM server has completedinitialization and is now available for connections fromother address spaces.



Module: AXMSC


AXMSC0052 Server prefix.name cannot be enabledbecause it is already active in anotheraddress space.

Explanation: Only one instance of a given AXM servername can be active in an MVS image at a time.

System action: The attempt to enable the server

AXMSC0036 AXMSC0052


interface is rejected with return code 8, reason code 52.


Module: AXMSC


AXMSC0053 Server prefix.name cannot be enabledbecause caller is not APF authorized.

Explanation: AXM requires that an AXM server regionmust be running APF authorized in order to be allowedto enable its server interface.

System action: The attempt to enable the serverinterface is rejected with return code 8, reason code 53.

User response: Ensure that the server program isexecuted from an APF authorized library and islink-edited with AC(1).

Module: AXMSC


AXMSC0054 Server prefix.name cannot be enabledbecause the security system rejected therequest.

Explanation: The security system detected that theserver region userid was not correctly authorized to actas an AXM server with the specified server name.

System action: The attempt to enable the serverinterface is rejected with return code 8, reason code 54.

User response: See the previous AXM message givingdetails of the results of the security check.

Module: AXMSC


AXMSC0061I Server prefix.name is now disabled forconnections.

Explanation: This AXM server is terminating and isno longer available for connections from other addressspaces. This occurs either when the server explicitlydisables its interface or when the server job step taskterminates.



Module: AXMSC


AXMSC0062 Server disable failed for token xxxxxxxx,reason is n.

Explanation: An attempt to disable the serverinterface failed because the specified server interfacetoken did not correctly identify an active serverinterface established by the current address space.

The reason code provides an internal indication ofwhich validity check failed within procedureAXMSCDIS. All reason codes probably indicate anincorrect token.

System action: The attempt to disable the serverinterface is rejected with return code 8, reason code 62.If the server interface is still enabled, it will be disabledautomatically when the job step task terminates.

User response: As the server interface token is storedinternally by AXM, the only known possible reason forthis message is storage overwriting within the serverregion.

Module: AXMSC


AXMSC0063 Server prefix.name cannot be disabledbecause caller is not APF authorized.

Explanation: AXM requires that an AXM server regionmust be running APF authorized in order to be allowedto disable its server interface.

System action: The attempt to disable the serverinterface is rejected with return code 8, reason code 63.

User response: Ensure that the server program isexecuted from an APF authorized library and islink-edited with AC(1).

Module: AXMSC


AXMSC0071 Server name prefix.name has incorrectsyntax for access checks.

Explanation: The security checking routine hasdetected that the AXM server name specified on aconnection request or on a server enable request is notin the correct form, for example because either theprefix or name is blank. This means that the securitycheck cannot be performed.

System action: A return code is set to indicate that thesecurity check failed.

User response: Check that the server prefix and nameare specified correctly. The prefix is normally definedby the server, but the name may be set from auser-specified server parameter.

Module: AXMSC


AXMSC0072 level access authorization was denied forFACILITY facility.

Explanation: The external security manager hasindicated that the current region is not authorized forthe required level of access to the specified facility.

AXMSC0053 AXMSC0072



User response: Check whether the userid for theregion has been authorized to access the specifiedfacility resource name.

Module: AXMSC


AXMSC0073 level access authorization is unavailablefor FACILITY facility.

Explanation: The external security manager hasindicated that it is unable to determine whether thecurrent region is authorized for the required level ofaccess to the specified facility. This message is onlyissued if it is not possible for the security routine todetermine whether security checking is actuallyrequired. In cases where it is obvious that no securitycheck is required (for example because no externalsecurity manager is installed), access is grantedanyway.


User response: Check whether the external securitymanager is available and whether the securitydefinitions for the specified facility have been provided.

Module: AXMSC


AXMSC0074 RACROUTE REQUEST=AUTH gaveR15=xxxxxxxx, SAFPRRET=xxxxxxxx,SAFPRREA=xxxxxxxx.

Explanation: This message provides additional detailsabout the results of a security check in any case whereaccess is not granted. See the documentation of theRACROUTE macro for further information.



Module: AXMSC


AXMSC0075 RACROUTE REQUEST=STAT gaveR15=xxxxxxxx, SAFPRRET=xxxxxxxx,

SAFPRREA=xxxxxxxx.

Explanation: This message provides additional detailsabout the results of a security check in any case whereaccess is not granted. See the documentation of theRACROUTE macro for further information.



Module: AXMSC


AXMSC0991I Creating new AXM system servicesanchor at address.

Explanation: This message is issued during AXMsystem services initialization to enable the systemservices anchor to be located if necessary for diagnosticpurposes.

System action: AXM system services initializationprocessing continues.


Module: AXMSC


AXMSC0992I Deleting old AXM system servicesanchor at address.

Explanation: This message is issued during AXMsystem services initialization if AXM system serviceswere previously active but had been terminated (whichis not possible in normal production environment). Theold system services anchor is retained after AXMtermination because it contains the system LX to beused if AXM is restarted. This message gives theaddress of the old system services anchor for diagnosticpurposes.

System action: AXM system services initializationprocessing continues.


Module: AXMSC


AXM subsystem initialization messages

AXMSI0001I AXM subsystem initialization is inprogress.

Explanation: The AXM subsystem initializationprogram has been started in order to initialize AXMsystem services.

System action: AXM system services will be loadedand initialized.


Module: AXMSI


AXMSC0073 AXMSI0001I


AXMSI0002I AXM subsystem initialization hascompleted.

Explanation: The AXM subsystem initializationprogram has completed execution.

System action: The program returns control to MVS.


Module: AXMSI


AXMSI0003 AXM subsystem initialization returncode retcode, reason code rsncode.

Explanation: The AXM subsystem initializationroutine has not completed normally. This messageindicates the final return code and reason code. This isnormally the return code from AXM system servicesinitialization.

System action: The subsystem initialization routinereturns control to MVS.

User response: See the previous AXM message

describing the cause of the problem. The reason codewill normally be the number of an error messageissued by AXMSC.

Module: AXMSI


AXMSI0004 AXM subsystem initialization can onlyrun in Master Scheduler address space.

Explanation: An attempt has been made to invoke theAXM subsystem initialization program AXMSI in someother way than as an MVS subsystem initializationprogram running in the Master Scheduler region (ASID0001).

System action: The subsystem initialization programis abnormally terminated.


Module: AXMSI


AXM system region messages

AXMSR0001I AXM system region initialization is inprogress.

Explanation: An AXM system region is being started.This is used to initialize AXM system services in atesting environment for development purposes, andallows AXM system services to be closed down andrestarted without an IPL.



Module: AXMSR


AXMSR0002I AXM system region initialization hascompleted.

Explanation: AXM system services have beensuccessfully initialized from the AXM system region.


User response: The system region may be closeddown again using the MVS STOP command but thisshould only be done when it is certain that no AXMservices are being used within the MVS image.

Module: AXMSR


AXMSR0003I AXM system region termination is inprogress.

Explanation: The operator has requested termination

of the AXM system region using the MVS STOPcommand.

System action: AXM system services are terminated.


Module: AXMSR


AXMSR0004I AXM system region termination hascompleted.

Explanation: The AXM system region has completedtermination.

System action: Control is returned to MVS and the jobstep ends.


Module: AXMSR


AXMSR0011 AXM system region can only run underMVS/ESA.

Explanation: An attempt was made to execute theAXM system region program AXMSR in a non-MVSenvironment.

System action: The system region program terminates.


Module: AXMSR

AXMSI0002I AXMSR0011



AXMSR0012 AXM system region program AXMSRneeds to be APF authorized.

Explanation: An attempt was made to execute theAXM system region program AXMSR without APFauthorization.


User response: Ensure that the module AXMSR isstored in an APF-authorized library and is link-editedwith AC(1).

Module: AXMSR


AXMSR0013 AXM system region LOAD for namefailed with completion code xxx-nn.

Explanation: The attempt to LOAD the systemservices module (AXMSC) failed.


User response: See the description of the systemcompletion code xxx in MVS/ESA System Codes for thereason that the LOAD failed.

Module: AXMSR


AXMSR0021 AXM system region does not supportthis command: text

Explanation: An attempt was made to issue acommand to the AXM system region using the MVSMODIFY command. The AXM system region onlysupports the MVS STOP command, and does notsupport commands entered via MODIFY.

System action: The command is ignored.

User response: If the intention was to close down thesystem region, use the MVS STOP command instead.

Module: AXMSR


AXMSR0022I AXM system region STOP commandhas been accepted.

Explanation: An operator has issued a STOPcommand to close down the AXM system region.

System action: AXM system services will beterminated.


Module: AXMSR


AXM trace and print file management messages

AXMTR0001 The ddname print file could not beopened.

Explanation: The AXM trace and print file with thespecified ddname (usually AXMPRINT or SYSPRINT)could not be opened during AXM initialization.

System action: Print file output requests will beignored.

User response: Ensure that the appropriate DD

statement is present. The default ddname isAXMPRINT, but this may be overridden to SYSPRINTby an AXMTRDEF definition within the server code ifthe server does not need to reserve the nameSYSPRINT for any other purpose.

Module: AXMTR


AXM address lookup (WHERE) messages

AXMWH0001I Address address is at +offset in modtypemodule modname.

Explanation: This message may be produced after anabend or TRAP message to identify the modulecontaining the error address, if the module is known toMVS. The information about the module and type isobtained using the MVS macros CSVQUERY orNUCLKUP.



Module: AXMWH


AXMWH0002I Address address is at +offset inprocedure procname.

Explanation: This message may be produced after anabend or TRAP message to identify the procedurecontaining the error address, if the storage is within aknown module and a standard SAVE sequenceincluding a procedure identifier appears at some pointbefore the error address.



Module: AXMWH


AXMSR0012 AXMWH0002I


AXM cross-memory interface messages

AXMXM0011 Server prefix.name cannot be enabledbecause AXM system services are notavailable.

Explanation: An attempt has been made to enable aserver interface but AXM system services have not beeninitialized within this MVS image.

System action: The server enable request is rejected.

User response: Ensure that AXM system services arestarted then start the server again.

Module: AXMXM


AXMXM0012 Enable failed for server prefix.name,return code retcode, reason rsncode.

Explanation: The server interface could not beenabled. The specific reason will have been indicatedby an earlier AXMSC message.

System action: The server enable request is rejected.


Module: AXMXM


AXMXM0021 ABEND xxx-rr occurred at address, dataword1 word2 word3.

Explanation: The ARR routine for an AXMcross-memory program call routine has intercepted anabend in a cross-memory mode AXM task and haspassed the associated SDWA to a task in the serveraddress space to issue the appropriate diagnosticmessages. The abend code is shown as threehexadecimal digits for a system completion code orfour decimal digits for a user completion code. Thedata consists of the twelve bytes around the PSWaddress as provided by MVS in the SDWA.

System action: The ARR will already have completedprocessing when this message is issued, as the messageis written out by the server region. If recovery isallowed, the ARR terminates the affected AXM internaltask, in which case the return code from thecross-memory request will consist of the completioncode in the usual MVS format but with the high-orderbit set to indicate an abend. If recovery is not allowed,the ARR percolates the error, passing the abend to therequesting region.

The diagnostic routine which writes this message willcall AXMWH which attempts to identify the moduleand procedure in which the abend occurred and writesout a further message if successful. It then releases theMVS SDWA. Server execution is not directly affected byan abend in cross-memory mode.

User response: Look up the completion code toidentify the cause of the abend.

Module: AXMXM


AXMXM0022 TRAP occurred at offset offset inprocname.

Explanation: An internal logic error in a servermodule or invalid parameters on a server requestresulted in a TRAP macro being executed at thespecified location in cross-memory mode.

The system will normally produce a symptom dumpmessage on the job log, and a full dump of theconnected region may be produced if an appropriateDD statement (SYSUDUMP, SYSMDUMP orSYSABEND) is present in the JCL for the connectedregion.

System action: The AXM task is abnormallyterminated.

User response: This probably indicates a logic error inserver code, or an attempt to use some internalcomponent of the server outside its correct context.

If the procedure name in the message begins withAXM, this probably indicates that the server codewhich called it has passed inconsistent parameters,such as an invalid address when releasing mainstorage.

Module: AXMXM


AXMXM0011 AXMXM0022


Chapter 2. Transaction abend codes

When abnormal conditions occur, CICS can send a message to the CSMT transientdata destination containing the transaction ID, the program name and the abendcode.

Here is an example:DFHAC2236: date time applid Transaction tranid abend primary abcode in program program nameterm termid backout successful { batchid = }batchid. message

Alternatively, the application can intercept abends by including an active EXECCICS HANDLE ABEND command. The actual abend code can be determined byissuing the EXEC CICS ASSIGN command with the ABCODE option.

The transaction identification code tranid usually consists of the 4 charactersdefined to CICS. However, when a transaction is initiated by using a light pen, anoperator identification (OPID) card reader, or 3270 PA or PF keys (specified in theTASKREQ= operand), CICS creates an internal transaction identification in theform of a 1-byte 3270 attention identification (AID) code followed by 3 bytes ofX'FF'.

The code that may actually appear in the message in place of the internally-createdtransaction identification will be *xx*, where xx is the character translation of the3270 AID code. To prevent ambiguity, the user should avoid using these codes astransaction identifiers.

The keys, the light pen (LPA), and OPID, and their corresponding printed AIDcodes are given in the following list:

PF1 *F1* PF13 *C1* LPA *7E*PF2 *F2* PF14 *C2* OPID *E6*PF3 *F3* PF15 *C3* PA1 *6C*PF4 *F4* PF16 *C4* PA2 *6E*PF5 *F5* PF17 *C5* PA3 *6B*PF6 *F6* PF18 *C6*PF7 *F7* PF19 *C7*PF8 *F8* PF20 *C8*PF9 *F9* PF21 *C9*PF10 *7A* PF22 *4A*PF11 *7B* PF23 *4B*PF12 *7C* PF24 *4C*

An abend code indicates the cause of an error that may have been originated byCICS or by a user program. For most of the abend codes described, a CICStransaction dump is provided at abnormal termination.

All CICS transaction abend codes abcode are 4-character alphanumeric codes of theform Axxy, where:

Aack 'M'is the IBM-assigned designation of a CICS transaction abend.

Copyright IBM Corp. 1977, 2012 13

xx is the 2-character code assigned by CICS to identify the module thatdetected an error.

y is the 1-character alphanumeric code assigned by CICS.

Format of information

For each transaction abend code, the following information is given:v An explanation of events leading to or following the message.v The action that has been or will be taken by CICS (system action).v The action recommended for the user (console or terminal operator).v The module or modules that can determine that the message should be sent (not

necessarily the module or modules that can issue the macro to write themessage.)

AAxx abend codes

AACA

Explanation: An invalid error code has been passed tothe DFHTFP or DFHACP programs.

System action: CICS terminates the task abnormallywith a dump.

User response: Notify the system programmer.

Module: DFHTFP,DFHACP

AAL1

Explanation: DFHALP was processing a request thatdeadlocked. The most likely reason for the abend isthat an ALLOCATE QUEUE request has beensuspended because there are no contention-winninglinks available.

AAL1 is issued for non time-out related deadlocks, forinstance the task may have been cancelled.

AAL8 is issued for stall purges and deadlock time-outs.

System action: CICS terminates the task abnormally. Adump is taken.

User response: Ensure that there are enoughcontention-winning sessions available to satisfy theALLOCATE QUEUE request.

If you are running with modegroups, ensure that thereare contention-winning sessions available to satisfy theALLOCATE request in that modegroup.

Module: DFHALP

AAL2

Explanation: Either an incorrect response (other thanPURGED) was returned from the suspend of theallocated task, or an incorrect response was returnedfrom the resume.

System action: The transaction is abnormallyterminated with a dump.

User response: Check the return code from theresume or the suspend to determine the cause of theerror.

Module: DFHALP

AAL3

Explanation: The task has been purged before aGETMAIN request to the storage manager (SM)domain was able to complete successfully. The task thatfirst detected the purged condition provides anexception trace.

System action: The task is abnormally terminatedwith a CICS transaction dump.

User response: Investigate the reason why the taskwas purged. It was purged either by the masterterminal operator or as a result of a deadlock timeout.

Module: DFHALP

AAL4

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the storage manager (SM) domain. The domainthat detected the original error provides an exceptiontrace, a console message, and possibly a system dump(depending on the options specified in the dump table).


User response: See the related message produced bythe domain that detected the original error.

Module: DFHALP

AACA AAL4


AAL6

Explanation: An error (INVALID, DISASTER orEXCEPTION response) has occurred on a call toSIGNOFF_TERMINAL_USER by DFHALP duringsign-off for a surrogate terminal session running CRTE.The domain that detected the original error provides anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).



Module: DFHALP

AAL7

Explanation: An error (INVALID, DISASTER orEXCEPTION response) has occurred on a call toschedule a remote terminal delete by DFHALP duringsign-off for a surrogate terminal session running CRTE.The domain that detected the original error provides anexception trace, a console message and, possibly, asystem dump (depending on the options specified inthe dump table).



Module: DFHALP

AAL8

Explanation: DFHALP was processing a request thatdeadlocked. The most likely reason for the abend isthat an ALLOCATE QUEUE request has beensuspended because there are no contention-winninglinks available.

AAL1 is issued for non time-out related deadlocks.

AAL8 is issued for stall purges and deadlock time-outs.

System action: CICS terminates the task abnormally. Atransaction or system dump is not taken unless thetransaction dump table has been modified for AAL8.

User response: Ensure that there are enoughcontention-winning sessions available to satisfy theALLOCATE QUEUE request.

If you are running with modegroups, ensure that thereare contention-winning sessions available to satisfy theALLOCATE request in that modegroup.

It might be necessary to increase the deadlock timeout(DTIMEOUT) value for the transaction to prevent thisabend from recurring.

If you require a transaction or system dump for this

abend then add AAL8 to the transaction dump table.

Module: DFHALP

AALA

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Atomservice Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).


User response: Inform the system programmer.Examine the trace and the dump to identify the pointof error.

Module: DFHAMW2

AALC

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the JVM server resource manager. The domainthat detected the original error provides a trace entryand possibly a system dump (depending on the optionsspecified in the dump table).



Module: DFHAMSJ

AALM

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the log manager (LM) domain. The domain thatdetected the original error provides an exception trace,a console message, and possibly a system dump(depending on the options specified in the dump table).



Module: DFHAMLM

AALN

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the TD manager. The domain that detected theoriginal error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).

AAL6 AALN

Chapter 2. Transaction abend codes 15



Module: DFHAMTD

AALO

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the CICS/DB2 table manager DFHD2TM. Thedomain that detected the original error provides a traceentry and possibly a system dump (depending on theoptions specified in the dump table).



Module: DFHAMD2

AALP

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Program Manager. The domain that detectedthe original error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module: DFHAMPG

AALQ

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Business Application Manager. The domainthat detected the original error provides a trace entryand possibly a system dump (depending on the optionsspecified in the dump table).



Module: DFHAMBA

AALR

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Temporary Storage Manager. The domainthat detected the original error provides a trace entryand possibly a system dump (depending on the optionsspecified in the dump table).



Module: DFHAMBA

AALS

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Global Enqueue Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).



Module: DFHAMBA

AALT

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Internet Inter-Orb Protocol Manager. Thedomain that detected the original error provides a traceentry and possibly a system dump (depending on theoptions specified in the dump table).



Module: DFHAMOP

AALU

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Sockets Domain Manager. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).


AALO AALU



Module: DFHAMSO

AALV

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Enterprise Java Domain. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).



Module: DFHAMEJ

AALW

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Web Domain. The domain that detected theoriginal error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module: DFHAMWB

AALX

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Pipeline Manager. The domain that detectedthe original error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module: DFHAMPI

AALY

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the ISC/IP Domain. The domain that detectedthe original error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module: DFHAMIS

AALZ

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Document Handler. The domain thatdetected the original error provides a trace entry andpossibly a system dump (depending on the optionsspecified in the dump table).



Module: DFHAMDH

AAM1

Explanation: DFHXMCL has returned an unexpectedresponse during the install of a transaction class. Thiscan be caused by the task being purged during theinstall.

System action: The transaction is abnormallyterminated with a CICS transaction dump.

If an error has occurred, at the time the error isdetected, CICS issues a DFHXMnnnn console message,records an exception trace entry and takes a systemdump.

User response: Determine why the task has failed. Ifthere is a system dump, use it together with the traceentry and the console message to resolve the problem.If there is no system dump, the task has been purgedeither by the master terminal operator or as a result ofdeadlock timeout.

Module: DFHAMP

AALV AAM1


AAM2

Explanation: DFHXMXD has returned an unexpectedresponse during the install of a transaction definition.This can be caused by the task being purged during theinstall.


If an error has occurred, at the time the error isdetected, CICS issues a DFHXMnnnn console message,records an exception trace entry and takes a systemdump.

User response: Determine why the task has failed. Ifthere is a system dump, use it together with the traceentry and the console message to resolve the problem.If there is no system dump, the task has been purgedeither by the master terminal operator or as a result ofdeadlock timeout.

Module: DFHAMP

AAM3

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Loader Domain. The domain that detectedthe original error provides a trace entry and possibly asystem dump (depending on the options specified inthe dump table).



Module: DFHAMLD

AAM4

Explanation: An error (INVALID, DISASTER orunexpected EXCEPTION response) has occurred on acall to the Resource Lifecycle Manager. The domainthat detected the original error provides a trace entryand possibly a system dump (depending on the optionsspecified in the dump table).



Module: DFHAMRL

AAMA

Explanation: There is an internal logic error inDFHAMP.


User response: You need further assistance from IBMto resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.

Module: DFHAMP

AAMC

Explanation: The task was purged before a GETMAINrequest to the storage manager domain was able tocomplete successfully.


User response: Investigate the reason the task waspurged. It was purged either by the master terminaloperator or as a result of deadlock timeout.

Module: DFHAMP

AAMD

Explanation: An unexpected return code has beenreceived from DFHDMP. This is due to an internal logicerror.



Module: DFHAMP

AAMF

Explanation: An unexpected return code has beenreceived following a call to the kernel (KE) domain.This might be due to an internal logic error.



Module: DFHAMP

AAMH

Explanation: An unexpected return code has beenreceived following a call to DFHFCMT. This might bedue to an internal logic error.


AAM2 AAMH



Module: DFHAMP

AAMI

Explanation: An unexpected return code has beenreceived following a call to DFHFCRL. This might bedue to an internal logic error.

System action: CICS terminates the task abnormallywith a dump. You need further assistance from IBM toresolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.

User response:

Module: DFHAMP

AAMJ

Explanation: While installing a file, using RDO, a callwas made to DFHFCFS to enable the file. Anirrecoverable error was returned from DFHFCFS.


At the time the error is detected, CICS writes amessage to the console, records an exception trace entryand takes a system dump.


Module: DFHAMP

AAMK

Explanation: While installing a file, using RDO, a callwas made to DFHFCDN. An irrecoverable error wasreturned from DFHFCDN.

System action: The task is abnormally terminatedwith a CICS transaction dump. At the time the error isdetected, CICS writes a message to the console, recordsan exception trace entry, and takes a system dump.

User response: Inform the system programmer,Examine the trace and dump to identify the point oferror.

Module: DFHAMP

AAMN

Explanation: There has been an unexpected returncode from a call to DFHPRPT. This might be due to aninternal logic error.


User response: You need further assistance from IBM

to resolve this problem. See Part 4 of the CICS ProblemDetermination Guide for guidance on how to proceed.

Module: DFHAMP

AAMO

Explanation: An invalid return code was returnedfrom DFHTOR, the CICS terminal object resolutionprogram.



Module: DFHAMP

AAMP

Explanation: An unexpected return code has beenreceived from DFHPUP. This might be due to aninternal logic error.



Module: DFHAMP

AAMQ

Explanation: An attempt has been made to install apartner using RDO. However, the partner resourcemanager (PRM) is unavailable having failed to initializeduring CICS initialization.


User response: If you need to use the PRM, correctthe problem which prevented the PRM frominitializing, and restart CICS.

Module: DFHAMP

AAMS

Explanation: There has been an unexpected returncode following a GETMAIN request to the storagemanager. This is due to an internal logic error.



Module: DFHAMP

AAMI AAMS


AAMT

Explanation: There is an internal logic error inDFHAMP due to an unexpected return code fromDFHTMP.



Module: DFHAMP

AAMZ

Explanation: An unexpected return code has beenreceived from DFHZCP. This is due to an internal logicerror.



Module: DFHAMP

AAO2

Explanation: CPI Communications has detected anunexpected response from DFHLUC.


User response: This is a CICS internal logic error.

A level 2 CICS trace for 'CP' of the transactiondocuments the course of events prior to this error (suchas the modules called and their parameters). The level2 trace also provides details of the error itself.

You need further assistance from IBM to resolve thisproblem. See Part 4 of the CICS Problem DeterminationGuide for guidance on how to proceed.

Module: DFHCPCBA

AAO3

Explanation: The CPI interface detected that a call wasmade to a CPI Communications function without CPICommunications being initialized. This implies that CPICommunications initialization failed while CICS wasinitializing.

System action: The transaction is abnormallyterminated with a CICS transaction dump. Anexception trace entry is also written when this eventoccurs.

User response: Check the console listing to determinethe reason why CPI Communications failed to initialize

during CICS initialization. Correct the problem andrestart CICS.

If the console listing indicates that CPICommunications initialized successfully, you needfurther assistance to resolve the problem. Collect theconsole listing, the traces and the transaction dump.See Part 4 of the CICS Problem Determination Guide forguidance on how to proceed.

Module: DFHCPI

AAO4

Explanation: DFHZARL, or a module called byDFHZARL, has detected a logic error. This error isalmost certainly caused by the module receiving invaliddata or indicators from z/OS Communications Server.

System action: Before returning to the CPICommunications layer, DFHZARL calls DFHZNAC toclean up the session and put out messages on theCSNE log. CPI Communications abnormally terminatesthe transaction with a CICS transaction dump, andproduces an exception trace entry.

User response: Check the CSNE log to determine thetype of error. You may need further assistance fromIBM to fully resolve this problem. See Part 4 of theCICS Problem Determination Guide for guidance on howto proceed.

Module: DFHCPCLR

AAO5

Explanation: The task was purged before a GETMAINrequest to the storage manager (SM) domain was ableto complete successfully. The domain that first detectedthe purged condition provides an exception trace.


User response: Investigate the reason why the taskwas purged. It was purged either by the masterterminal operator or as a result of deadlock timeout.

Module: DFHCPCBA, DFHCPCBI, DFHCPCBS

AAO7

Explanation: The CPI Communications syncpointrequest handler has been passed an invalid DFHLUCparameter list. This is a CICS internal logic error.


User response: A level 2 trace for 'CP' of thetransaction shows the course of events before this erroroccurred (such as the modules called and theirparameters) plus details of the error itself. You needfurther assistance from IBM to resolve this problem. SeePart 4 of the CICS Problem Determination Guide for

AAMT AAO7


guidance on how to proceed.

Module: DFHCPSRH

AAO8

Explanation: The CPI Communications syncpointrequest handler has been passed an invalidconversation control block (CPC). This is a CICSinternal logic error.


User response: A level 2 trace for 'CP' of thetransaction shows the course of events before this erroroccurred (such as the modules called and theirparameters) plus details of the error itself. You needfurther assistance from IBM to resolve this problem. SeePart 4 of the CICS Problem Determination Guide forguidance on how to proceed.

Module: DFHCPSRH

AAO9

Explanation: A task has been purged either as a resultof a purge from the master terminal operator via theCEMT transaction, or by the task being timed out afterwaiting for longer than the DTIMOUT (deadlocktimeout) value specified for the transaction.


User response: Investigate why the task was purged.

If the task was purged by the master terminal operator,this may have been in an attempt to clear the systemwhich appeared to be deadlocked for some reason.

If the task was timed out automatically as a result ofthe DTIMOUT value being exceeded, this may be dueto insufficient main storage being available for thenumber of tasks in the system. If the amount of mainstorage cannot be increased, the number of tasks in thesystem should be reduced to avoid short-on-storagesituations. Another possibility would be to increase thevalue of the DTIMOUT option for the transaction.

Module: DFHCPCLR

AAOA

Explanation: An application has issued a CPI verbwhich CICS does not support. The entry pointreferenced in the application program was resolved inthe link edit stub, but the function requested could notbe resolved when control passed to CICS.

There are two possible reasons for thisv You have linkedited your application program with a

CPI stub which supports more function than thisrelease of CICS.

v The linkedit stub has been corrupted.

System action: The transaction is abnormallyterminated with a CICS transaction dump. Anexception trace entry is also written.

User response: At the time of the error, generalregister 0 points to an 8-byte character string whichshould match the name of the issued CPI call. Use thetrace or the dump to verify that this character string isthe name of a CPI function which is supported.

If the character string is not an intelligible characterstring, the stub has probably been corrupted.

Module: DFHCPI

AAOB

Explanation: An application has issued a CPI verbwhich specifies more than eight parameters.

System action: The transaction is abnormallyterminated with a CICS transaction dump and anexception trace entry is also written.

User response: Change your application program sothat the correct number of parameters is specified onthe CPI call.

Module: DFHCPI

AAOC

Explanation: CPI Communications is invoked with aninvalid number of parameters for call


User response: The exception trace point producedwith this abend contains the incorrectly issued CPICommunications verb name. Use this to determinewhere the application program was in error and amendit accordingly.

The SAA CPI Communications Reference manual,SC26-4399, provides a detailed description of all theCPI Communications verbs and how they should becalled.

Module: DFHCPARH

AAOD




Module: DFHCPCBI

AAO8 AAOD


AAOE




Module: DFHCPCBA

AAOF




Module: DFHCPCBS

AAOG

Explanation: During the processing of CMACCP(accept conversation), CPI Communications detectedthat the application was attached with an unsupportedsync level.


User response: This condition is caused by a back-endCPI Communications transaction being attached with async level that is not CM_NONE (0) or CM_CONFIRM(1).

Change the front-end transaction, (that is, the initiatorof the conversation in the other system) so that itdefines the sync level correctly.

Module: DFHCPCBA

AAOH

Explanation: Journaling of data sent on a CPIcommunications mapped conversation has failed. Thiscondition is caused by a nonzero response from theCICS log manager.

Register 12 addresses the current TCA and fieldTCAJCAAD and register 4 address the JCA. The logmanager request is contained in JCATR2 and theresponse code is in JCAJCRC.

Possible request codes are

X8001 - WRITEX8003 - PUT

Possible response codes are

X01 - IDERROR - Journal identification errorX02 - INVREQ - Invalid requestX03 - STATERR - Status errorX05 - NOTOPEN - Journal not openX06 - LERROR - Journal record length errorX07 - IOERROR - I/O error.

The address of the TIOA is contained in register 8 andits data length is in TIOATDL.

Analysis:

Register Label Description

R4=@JCA TCZARQPJ JCAJCRC is nonzero.


User response: Use the dump to ascertain why thejournal or log record could not be written correctly. If ajournal record length error is indicated, TIOATDL mayhave been corrupted.

Module: DFHCPCOJ

AAOI

Explanation: The journaling of data received on a CPICommunications mapped conversation has failed.

Register 12 addresses the current TCA and fieldTCAJCAAD and register 4 address the JCA. The CICSlog manager request is contained in JCATR2 and theresponse code is in JCAJCRC.

Possible request codes are

X8001 - WRITEX8003 - PUT

Possible response codes are

X01 - IDERROR - Journal identification errorX02 - INVREQ - Invalid requestX03 - STATERR - Status errorX05 - NOTOPEN - Journal not openX06 - LERROR - Journal record length errorX07 - IOERROR - I/O error

The address of the TIOA is contained in register 8 andits data length is in TIOATDL.

Analysis:

Register Label Description

R4=@JCA TCZARQPJ JCAJCRC is nonzero.


User response: This condition is caused by an invalidresponse from the log manager. Use the dump to

AAOE AAOI


ascertain why the journal or log record could not bewritten correctly. If a journal record length error isindicated, TIOATDL may have been corrupted.

Module: DFHCPCRI, DFHCPCRW

AAOJ

Explanation: CPI Communications has detected anunexpected response from one of its internal routines.



A level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error. For example, themodules called and their parameters. The level 2 tracealso provides details of the error itself.


Module: DFHCPIC

AAOK

Explanation: CPI Communications has detected anunexpected call to one of its internal routines.



A level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error, for example, themodules called and their parameters. The level 2 tracealso provides details of the error itself.


Module: DFHCPIC

AAOL

Explanation: CPI Communications has made aninvalid call to DFHLUC.



A level 2 trace for 'CP' of the transaction shows thecourse of events prior to this error, for example, themodules called and their parameters. The level 2 tracealso provides details of the error itself.


Module: DFHCPCLR

AAOM

Explanation: The CPI Communications and theDFHZUSR state machines are out of synchronization.





Module: DFHCPCLR, DFHCPSRH

AAON

Explanation: CPI Communications has detected anunexpected response from DFHLUC.





Module: DFHCPCLR, DFHCPCLC

AAOO

Explanation: CPI Communications has been invokedwith an invalid first parameter. The first parametershould be the code of the function to be performed.This is a CICS internal logic error.


User response: A level 2 trace for 'CP' of thetransaction shows the course of events before this erroroccurred (such as the modules called and theirparameters) plus details of the error itself.


Module: DFHCPARH

AAOJ AAOO


AAOP

Explanation: The CPI Communications state machinehas been requested to perform a state transition requestthat is considered to be an 'impossible' situation. (TheSAA CPI Communications Reference manual, (SC26-4399)documents all these situations.)

There are two possible causes of this error

v The CPC (conversation control block) has beenoverwritten in such a way that the conversation statehas been altered, or

v There is an error in the CPI Communications statemachine.

Sys

Documents

CICS TS for z/OS 4.2: CICS Messages and Codes Vol 2publibfi.dhe.ibm.com/epubs/pdf/dfhgae01.pdf · CICS Transaction Server messages and abend code descriptions (with the exception