messages and codes · 2018. 6. 11. · erz001004e cobol runtime was not able to find program...

TXSeries for Multiplatforms

Messages and CodesVersion 7.1

GC34-7073-00

��

NoteBefore using this information and the product it supports, be sure to read the general information under “Notices” on page925.

Order publications through your IBM representative or through the IBM branch office serving your locality.

© Copyright International Business Machines Corporation 2001, 2009.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this book . . . . . . . . . . . vWho should read this book . . . . . . . . . vDocument organization . . . . . . . . . . . vRelated information . . . . . . . . . . . . vConventions used in this book . . . . . . . . vHow to send your comments . . . . . . . . vii

Chapter 1. ERZxxx messages . . . . . 1

Chapter 2. BHG... . . . . . . . . . . 575

Chapter 3. CICS Toolkit message andcodes. . . . . . . . . . . . . . . 743CICS Toolkit messages . . . . . . . . . . 743

0x502c5017: Collating Language ″%s″ Isdifferent Than One Already Installed ″%s″... . . 8060x5c102017: tmxa_SetRMIAutoClose is obsolete-- use tmxa_SetRMIOptions instead. . . . . . 8060x5c1c1457: Applid %d byte%s too long:recovery compromised . . . . . . . . . 8060x5c1c1837: %s to XID conversion failed: %k 8070x5c2c0c17: Aborting %s. . . . . . . . . 8070x5c301017: Recording heuristic damage for %s 8070x5c380c17: Rollback assumed for %s . . . . 8080x5c381017: Rollback assumed for %s . . . . 8080x5c3c0c17: Heuristic outcome performed on%s. . . . . . . . . . . . . . . . . 8080x5c3c0c27: Recovery of %z may becompromised. . . . . . . . . . . . . 8090x5c3c1c17: Terminating recovery scan for RM%d. . . . . . . . . . . . . . . . . 8090x5c401417: Recording heuristic damage for %s 8100x5c541017: Truncating transaction identifierwhen constructing XID -- recoverycompromised. . . . . . . . . . . . . 8100x5c541027: Truncating application identifierwhen constructing XID -- recoverycompromised. . . . . . . . . . . . . 810

0x64048c67: PPC Service Not Initialized . . . 8110x640c6417: unknown/unexpected transactionstate %d returned by tran-service for tid: %#x . 8110x640c7017: Inserting Conversation with aNULL Attributes Structure . . . . . . . . 8110x640c8017: duplicate sna conv found . . . . 8120x64e41c17: new exec LU (%s) listed throughold admin interface: %u . . . . . . . . . 8120x64e42017: . . . . . . . . . . . . . 8120x64e45017: . . . . . . . . . . . . . 8130x64e46c27: trdce_BindingImport FAILED (%k) 8130x64e49027: New RPC failed (%k). Trying oldRPC... . . . . . . . . . . . . . . . 8130x64e49037: failed to chmod file %s, errno: %d 8130x64e49427: . . . . . . . . . . . . . 8140x64e49437: Invalid remoteluProfilePriority(%lu). Exported profile will have defaultpriority value. . . . . . . . . . . . . 8140x64e49817: . . . . . . . . . . . . . 8140x64e49c17: . . . . . . . . . . . . . 8140x68044487: Illegal sync level: %i . . . . . . 8140x68044497: Illegal security level: %i. . . . . 8150x680448b7: . . . . . . . . . . . . . 8150x680448c7: . . . . . . . . . . . . . 8150x6804f8c7: Unable to initialize ppc services . . 815

Status codes . . . . . . . . . . . . . . 816Abort codes . . . . . . . . . . . . . . 897

Chapter 4. SARPC messages . . . . 907

Notices . . . . . . . . . . . . . . 925

Trademarks and service marks . . . . 927

© Copyright IBM Corp. 2001, 2009 iii

iv TXSeries for Multiplatforms: Messages and Codes

About this book

This book lists CICS® messages and codes. The information can be used todetermine the cause of CICS problems.

Who should read this bookThis book is for system administrators, terminal users, system programmers andanybody else who needs to understand and respond to CICS messages and codes.

To use this book, you need to have a general understanding of CICS. You alsoneed more detailed knowledge about the part of CICS to which the messagepertains.

Document organizationThis document has the following organization:v CICS messages describes messages issued by CICS.v CICS codes describes CICS abend codes.

The printed version of this book is available in two formats (HTML and PDF).

Related informationFor further information on the topics discussed in this manual, see the TXSeries forMultiplatforms Version 7.1 Information Center.

Conventions used in this bookTXSeries® for Multiplatforms documentation uses the following typographical andkeying conventions.

Table 1. Conventions that are used in this book

Convention Meaning

Bold Indicates values that you must use literally, such as commands,functions, and resource definition attributes and their values. Whenreferring to graphical user interfaces (GUIs), bold also indicatesmenus, menu items, labels, buttons, icons, and folders.

Monospace Indicates text that you must enter at a command prompt.Monospace also indicates screen text and code examples.

Italics Indicates variable values that you must provide (for example, yousupply the name of a file for file_name). Italics also indicatesemphasis and the titles of books.

< > Encloses the names of keys on the keyboard.

<Ctrl-x> Where x is the name of a key, indicates a control-character sequence.For example, <Ctrl-c> means hold down the Ctrl key while youpress the c key.

<Return> Refers to the key labeled with the word Return, the word Enter, orthe left arrow.

© Copyright IBM Corp. 2001, 2009 v

Table 1. Conventions that are used in this book (continued)

Convention Meaning

% Represents the UNIX® command-shell prompt for a command thatdoes not require root privileges.

# Represents the UNIX command-shell prompt for a command thatrequires root privileges.

C:\> Represents the Windows® command prompt.

> When used to describe a menu, shows a series of menu selections.For example, ″Select File > New″ means ″From the File menu, selectthe New command.″

Entering commands When instructed to “enter” or “issue” a command, type thecommand and then press <Return>. For example, the instruction“Enter the ls command” means type ls at a command prompt andthen press <Return>.

[ ] Encloses optional items in syntax descriptions.

{ } Encloses lists from which you must choose an item in syntaxdescriptions.

| Separates items in a list of choices enclosed in { } (braces) in syntaxdescriptions.

... Ellipses in syntax descriptions indicate that you can repeat thepreceding item one or more times. Ellipses in examples indicate thatinformation was omitted from the example for the sake of brevity.

IN In function descriptions, indicates parameters whose values areused to pass data to the function. These parameters are not used toreturn modified data to the calling routine. (Do not include the INdeclaration in your code.)

OUT In function descriptions, indicates parameters whose values areused to return modified data to the calling routine. Theseparameters are not used to pass data to the function. (Do notinclude the OUT declaration in your code.)

INOUT In function descriptions, indicates parameters whose values arepassed to the function, modified by the function, and returned tothe calling routine. These parameters serve as both IN and OUTparameters. (Do not include the INOUT declaration in your code.)

$CICS Indicates the full path name of the location in which the CICSproduct is installed; for example, /usr/lpp/cics on AIX®. If the CICSenvironment variable is set to the product path name, you can usethe examples exactly as shown in this book; otherwise, you mustreplace all instances of $CICS with the CICS product path name.

CICS on OpenSystems

Refers collectively to the CICS product for all supported UNIXplatforms.

TXSeries forMultiplatforms

Refers collectively to the CICS for AIX, CICS for HP-UX, CICS forSolaris, and CICS for Windows products.

CICS Refers generically to the CICS for AIX, CICS for HP-UX, CICS forSolaris, and CICS for Windows products. Other CICS products inthe CICS Family are distinguished by their operating system (forexample, IBM® mainframe-based CICS for the z/OS platform).

vi TXSeries for Multiplatforms: Messages and Codes

How to send your commentsYour feedback is important in helping to provide the most accurate and highestquality information. If you have any comments about this book or any otherTXSeries for Multiplatforms documentation, send your comments by e-mail [email protected]. Be sure to include the name of the book, the documentnumber of the book, the version of TXSeries for Multiplatforms, and, if applicable,the specific location of the information you are commenting on (for example, apage number or table number).

About this book vii

viii TXSeries for Multiplatforms: Messages and Codes

Chapter 1. ERZxxx messages

ERZ001001E Exception raised in CICS applicationserver code

Explanation: An unexpected exception was caught inthe CICS application server code, during the executionof a transaction program.

System action: CICS abnormally terminates thetransaction. The application server continues, and isavailable to run further transactions.

User response: If the problem persists, there is noalternative but to call your support organization.

Destination:

CSMT

ERZ001002E Abnormal termination U0101. CICS wasunable to attach shared memory.

Explanation: CICS was unable to attach the RegionPool shared memory. This can occur on UNIX if theaccess permissions to the CICS shared memorysegments have been altered or if the data segmentshared memory identifier has been overwritten.

System action: CICS abnormally terminates theregion.

User response: On UNIX ask the system administratorto check for inconsistencies in the CICS shared memorysegments using the ipcs command; these segmentsmust have read and write permissions for the user’cics’ who must be a member of the user group ’cics’. Ifthe problem cannot be identified, call your supportorganization.

Destination:

console.msg

ERZ001003E An error in a COBOL transactionprogram caused the COBOL run timesystem to generate the previous errormessage

Explanation: CICS has detected that an error in aCOBOL transaction program caused a COBOL run timesystem error to occur during the execution of theprogram. The COBOL run time system has alreadywritten an error message to console.msg.

System action: CICS abnormally terminates thetransaction.

User response: Look in console.msg and find theCOBOL run time system error number and errormessage (which immediately precede this message). Forfurther information about the error, look up the error

number in the COBOL Error Messages manual. Correctthe error in your COBOL transaction program beforeattempting to run the program again.

Destination:

console.msg

ERZ001004E COBOL runtime was not able to findprogram ’Tobedetermined’ for Transaction’Tobedetermined’

Explanation: CICS has received a a message fromCOBOL runtime that it is not able to find the programneither in CICS PD nor on the path specified byCOBDIR. This program was invoked using cobol CALLstatement.

System action: CICS abnormally terminates thetransaction with AEI0.

User response: Put the program on the path specifiedin COBDIR or create a PD entry for it.

Destination:

console.msg

ERZ001005I COBOL RTS will try to load program’Tobedetermined’ invoked using CALLstatement

Explanation: CICS has verified that this program hasno PD entry. It now enables COBOL RTS to load it byRTS rules.

System action: none

User response: none

Destination:

console.msg

ERZ001006E COBOL program ’Tobedetermined’ notfound

Explanation: There is valid PD Entry for this programbut this file is not there on filesytem.


User response: Put the program on the path specifiedin PD entry.

Destination:

console.msg

© Copyright IBM Corp. 2001, 2009 1

ERZ001007E Unsucessful load of COBOL program’Tobedetermined’

Explanation: COBOL RTS failed to register program.Image of program is corrupted.


User response: Check the program image.

Destination:

console.msg

ERZ001016E A fatal error occurred while executingan IBM COBOL program

Explanation: A fatal error occurred while executing aprogram written in IBM COBOL.

System action: An A012 abend is raised.

User response: The console.msg file includes amessage returned by the IBM COBOL run-time. Usethis message to diagnose the problem in the user code.

Destination:

stderr

ERZ001017I Starting Animator

Explanation: CICS is about to start Animator on thetty that displays this message.

System action: None.

User response: None.

Destination:

stderr

ERZ001018E A fatal error occurred while executingan IBM PL/I program

Explanation: A fatal error occurred while executing aprogram written in IBM PL/I.

System action: An A013 abend is raised.

User response: The console.msg file includes amessage returned by the IBM PL/I run-time. Use thismessage to diagnose the problem is user code.

Destination:

stderr

ERZ001019I Override version of cicsprCOBOL hasbeen detected and will be used

Explanation: CICS has detected that a second versionof its MF COBOL language method, cicsprCOBOL, hasbeen placed in the regions bin directory. CICS uses thisversion in preference to the default version.

System action: None. This message is for informationonly.


Destination:

stderr

ERZ001020E An error has occurred while initializinga CICS Java Program

Explanation: CICS encountered a problem whilesetting up the environment to run a CICS JavaApplication Program.

System action: CICS abends the transaction withabend code A014

User response: Determine the cause of the error ifpossible, and rectify. There is possibly additionalinformation in console.msg, for example a Javaexception message, that indicates the cause of theproblem.

Destination:

console.msg

ERZ001021E CICS is unable to load a libraryrequired for CICS JAVA SUPPORT.

Explanation: There are Java Native Libraries that areneeded by CICS to run Java Applications. One of thesehas failed to load.

System action: CICS abends the transaction withabend code A014

User response: Determine the cause of the error ifpossible, and rectify. There is possibly additionalinformation in console.msg, for example a Javaexception message, that indicates the cause of theproblem.

Destination:

console.msg

ERZ001022W CICS is unable to merge the CICS Javaproperties file with the Java SystemProperties

Explanation: During initialisation of the environmentfor a CICS Java program, CICS merges the userproperties file, ’region.properties’ in the regiondirectory, with the Java System properties. Thismessage indicates that the merge has failed.

System action: The transaction continues.

User response: Determine whether this causes aproblem with your applications. If so, try to determinethe cause of the error from additional information inconsole.msg, and rectify if possible.

Destination:

ERZ001007E • ERZ001022W

2 TXSeries for Multiplatforms: Messages and Codes

console.msg

ERZ001023W Argument value ’ArgumentValue’ forCICS Java Option ’ArgumentName’ isinvalid

Explanation: CICS is processing the value of the’CICS_JAVA_OPTIONS’ environment variable whileinitializing the environment to run a CICS Javaprogram. The value shown in the message is not avalid value for the option indicated.


User response: Determine whether this causes aproblem with your application. If so, correct the valueof ’CICS_JAVA_OPTIONS’ and restart CICS.

Destination:

CSMT

ERZ001024W CICS is unable to complete processingof ’CICS_JAVA_OPTIONS’ as themaximum number of properties,’MaxProperties’, has been exceeded

Explanation: CICS is processing the value of the’CICS_JAVA_OPTIONS’ environment variable whileinitializing the environment to run a CICS Javaprogram. The maximum number of options that can beset has been exceeded. The maximum permitted isshown in the message.

System action: No further options are processed, butthe transaction continues.


Destination:

CSMT

ERZ001025E Insufficient memory available toinitialize the environment for a CICSJava program

Explanation: While initializing the environment to runa CICS Java application program, CICS was unable toobtain sufficient memory from the system.

System action: The transaction is abnormallyterminated with abend code A014.

User response: Retry when the system is less busy, orshut down some processes to free system memory.

Destination:

console.msg

ERZ001026W Unexpected argument ’ArgumentName’found while processing’CICS_JAVA_OPTIONS’

Explanation: CICS is processing the value of the’CICS_JAVA_OPTIONS’ environment variable whileinitializing the environment to run a CICS Javaprogram. The argument shown in the message is notrecognised.

System action: No further options are processed, butthe transaction continues.


Destination:

CSMT

ERZ001027W Incorrect format for environmentvariable ’CICS_JAVA_OPTIONS’

Explanation: CICS is processing the value of the’CICS_JAVA_OPTIONS’ environment variable whileinitializing the environment to run a CICS Javaprogram. The format of the variable is incorrect.

System action: CICS stops further processing of’CICS_JAVA_OPTIONS’ and continues to run thetransaction.


Destination:

CSMT

ERZ001028E Load of Java library failed with errornumber ’errorNumber’; error text’errorMessage’

Explanation: CICS cannot load a Java library for thereason defined by the operating system error numbererrorMessage. If more information is available from theoperating system regarding the failure, it is logged asone or more subsequent ERZ5803E messages.

System action: The transaction is abnormallyterminated.

User response: Use the error code in this message andinformation from accompanying messages to determinethe cause of the problem. Ensure that the library isinstalled correctly, with the correct permissions.

Destination:

console.msg

ERZ001023W • ERZ001028E

Chapter 1. ERZxxx messages 3

ERZ001029E CICS could not find the entry pointname ’entryPointName’; error’errorNumber’; text ’errorMessage’

Explanation: CICS cannot locate the entry point ’%1s’in a loaded shared library.


User response: Use the error code and text from themessage to determine the cause of the problem.

Destination:

console.msg

ERZ001030E CICS could not attach to the JavaVirtual Machine; error ’errorNumber’

Explanation: CICS cannot attach to the Java VirtualMachine which is part of the initialization process forrunning a CICS Java Application. The Java NativeInterface command that has failed is’AttachCurrentThread’.


User response: Use the error code to determine thecause of the problem.

Destination:

console.msg

ERZ001031E CICS could not create a Java VirtualMachine; error ’errorNumber’

Explanation: CICS cannot create a Java VirtualMachine, which is part of the initialization process forrunning a CICS Java Application. The Java NativeInterface command that has failed is’JNI_CreateJavaVM’.


User response: Use the error code to determine thecause of the problem.

Destination:

console.msg

ERZ001032E The Java Virtual Machine has requestedprocess termination

Explanation: While a CICS Java program wasexecuting, the Java Virtual Machine, which runs insidea CICS Application Server, has requested the process beterminated.


User response: Examine the console.msg for

additional messages to determine the cause of theproblem.

Destination:

console.msg

ERZ001033E Unable to find the JDK on the machine

Explanation: Either JDK is not as the default path i.e./usr/java130 or environment variable JAVA_HOMEincorrectly set.


User response: Install supported JDK, if it alreadyexists then correct JAVA_HOME variable to reflectlocation of installation.

Destination:

console.msg

ERZ001034E CICS IIOP ORB initialization has failed.

Explanation: The java orb was unsuccessful ininitializing.

System action: The CICS java orb is terminated

User response: Please verify classpaths and your javasettings. Looks at log and console files for terminationcause. JAVA_HOME variable.

Destination:

console.msg

ERZ001035E Abnormal Termination A014: CICS IIOPORB Init Error.

Explanation: CICS has discovered an internal error.

System action: CICS terminates the listener andapplication server.

User response: Perform necessary changes asindicated by pervious messages in log/console files.

Destination:

console.msg

ERZ001036E Java Exception encountered (asdescribed below):

Explanation: CICS has encountered an exception fromJava while initializing the java orb.

System action: CICS terminates the listener andapplication server.

User response: Perform necessary changes asindicated by pervious messages in log/console files.

Destination:

console.msg

ERZ001029E • ERZ001036E


ERZ001037E Exception occurred while loading theCOBOL language program

Explanation: CICS has encountered an exceptionwhile loading the COBOL Languageprogram,cicsprCBMFNT.

System action: CICS abnormally terminates thetransaction with APCT.

User response: Ensure that Micro Focus NetExpressCobol is installed and functioning correctly.

Destination:

console

ERZ001038W CBL_DEBUG_START returned an error.Program ’programName.’ will run withoutanimating.

Explanation: The CICS application server could notattach to the COBOL animator (debugger) when usingCBL_DEBUG_START.

System action: Processing continues.

User response: Before you run the cicsanimsrvprogram from the debugging window, ensure that theCOBANIMSRV environment variable is set to theCOBANIMSRV ID that is configured through CADB.Ensure also that the other COBOL environment (forexample, COBDIR) has been correctly set.

Destination:

console

ERZ001039E Abnormal termination A167:Inconsistency detected in logical unit ofwork control structures

Explanation: The data structures used to drive atransaction are inconsistent. They might have beendeleted due to asynchronous abort or they could havebeen corrupted.

System action: CICS terminates the application serverprocess with code A167. The transaction running at thispoint in time will abend.

User response: If required, resubmit the transaction.See the additional error messages produced for furtherinformation. Retry the transaction call IBM Support ifthe problem persists.

Destination:

console

ERZ001040W Unable to write CICSAppProbe outputfile ’fileNameerrno’,errno ’fileNameerrno’

Explanation: CICS attempted to create and then writeto output file, but the command failed with an error.

System action: CICS will disable CICSAppProbefacility.

User response: Check if you have the necessarypermissions to create and write to the file in thespecified directory. Check also that the file system isnot full. If this fails, then check errno for moreinformation.

Destination:

console

ERZ001041E CICSAppProbe facility is now disabled

Explanation: CICSAppProbe facility has beendisabled.

System action: CICS has found an invalid conditionand disabled CICSAppProbe facility.

User response: Examine previous messages todetermine the cause of the problem and takeappropriate action.

Destination:

console

ERZ002001E Usage: cicscvt fileName

Explanation: You entered the cicscvt commandincorrectly.

System action: The cicscvt command terminates.

User response: Enter the cicscvt command using thecorrect syntax, as shown in the message.

Destination:

stderr

ERZ002002E Unable to initialize a parserenvironment

Explanation: The cicscvt command was attempting toobtain memory for the parser. Insufficient memory wasavailable.

System action: The cicscvt command terminates withexit code 1 and does not produce any convertedtemplate files.

User response: Try again when the system is less busyand has more memory available.

Destination:

stderr

ERZ002003E Unsuccessful open of input file’fileName’. ’errorMessage’

Explanation: The file you requested cicscvt to processwas unable to be opened for the reason given by theoperating system as ’errorMessage’.

ERZ001037E • ERZ002003E



User response: Check that the ’fileName’ given is avalid readable file. For further information consult theoperating system documentation for the fopen()function. Once the ’fileName’ is corrected, retry thecicscvt command.

Destination:

stderr

ERZ002004E Unsuccessful memory allocation tocreate conversion template

Explanation: The cicscvt command cannot allocateany more memory from the operating system for theconversion templates.


User response: Try again when the system is less busyand has more memory available.

Destination:

stderr

ERZ002005E Cannot register exception handler

Explanation: The cicscvt command needs to run withan exception handler, but a signal call to attach it gavean unexpected response. This indicates an internalerror.


User response: Contact your support organization.

Destination:

stderr

ERZ002010E Unsuccessful open of output file’fileName’. ’errorMessage’

Explanation: The cicscvt command was unable toopen the output file, errorMessage, for the reason givenby the operating system as ’errorMessage’.


User response: Check that the output file ’fileName’does not exist and that the current working directoryhas write permissions. For further information consultthe operating system documentation for the fopen()function.

Destination:

stderr

ERZ002011I DFHCNV macro translation ended.errorCountd errors, warningCountdwarnings.

Explanation: The cicscvt command detected the statednumber of errors and warnings during map translation.

System action: If an error or warning was detectedduring translation, the cicscvt command terminateswith exit code 1; otherwise, it terminates with exit code0.

User response: None

Destination:

stderr

ERZ002015E Unsuccessful write to output file’fileName’. ’errorMessage’

Explanation: The cicscvt command was unable towrite to the output file, errorMessage, for the reasongiven by the operating system as ’errorMessage’.

System action: The cicscvt command terminates withexit code 1 and possibly produces partially convertedtemplate files.

User response: Check that there is enough space onthe disk for the files produced and retry. For furtherinformation consult the operating systemdocumentation for the function fprintf().

Destination:

stderr

ERZ002020E lineNumber: The ICTL directive isinvalid. A comma-separated list for thestart, continuation and end columnnumbers is required.

Explanation: The ICTL directive requires acomma-separated list of 1, 2, or 3 numbers to set thestart, continuation, and end columns for the inputsource file to cicscvt program.

System action: The line containing the ICTL directiveis ignored by cicscvt, and the cicscvt commandcontinues to process the rest of the input file. Thecicscvt command terminates with exit code 1.

User response: Edit the input file to correct the ICTLdirective at the given lineNumber, and retry the cicscvtcommand.

Destination:

stderr

ERZ002004E • ERZ002020E


ERZ002021E lineNumber: Invalid character ’character’in continuation line

Explanation: The continuation line contained withinthe file you specified to cicscvt did not contain spacesbetween the start column and continuation columns(defaults 1 and 16 respectively).

System action: The cicscvt command ignores the lineat lineNumber and processes the rest of the file. Thecicscvt command terminates with exit code 1.

User response: Correct the continuation line that isspecified at line lineNumber of your input file, and retrythe cicscvt command.

Destination:

stderr

ERZ002022E lineNumber: Invalid character ’character’in label

Explanation: The file you requested cicscvt to processcontained an invalid label at line lineNumber. A labelmust begin with a letter and only contain letters anddigits.

System action: The cicscvt command ignores the labeland continues to process the rest of the input file. Thecicscvt command terminates with exit code 1.

User response: Edit the input file to change the labelspecified at line lineNumber such that it only containsletters and numbers and that the first character is aletter, and retry the translation.

Destination:

stderr

ERZ002023W lineNumber: Label ’label’ is too long.Label truncated to ’truncatedLabel’.

Explanation: You have a DFHCNV macro label withinyour input file at line lineNumber that has more than 63characters.

System action: The cicscvt command truncates thelabel and continues to process the rest of the input file.The cicscvt command terminates with exit code 1.

User response: Edit the input file to shorten the labelat the lineNumberpecified, and retry the cicscvtcommand.

Destination:

stderr

ERZ002024W lineNumber: No DFHCNV macro found.The line will be ignored.

Explanation: You have entered a record in your filethat does not have a DFHCNV macro. Each record

must contain a DFHCNV macro, optionally precededby a label.

System action: The cicscvt command ignores the lineand continues to process the rest of the input file. Thecicscvt command terminates with exit code 1.

User response: Edit the input file either to remove therecord or to add a valid macro, and retry the cicscvtcommand.

Destination:

stderr

ERZ002025W lineNumber: Unknown word ’macroType’in place of a macro name

Explanation: The cicscvt command does not recognizethe word that appears in the operation field (that is, asthe first non-blanks after any label) on the given line ofyour input file. The only valid contents of that positionare: ICTL, TITLE, the macro name DFHCNV, andEND.

System action: The cicscvt command ignores the linecontaining the unknown operation and continues toprocess the rest of the input file. The cicscvt commandterminates with exit code 1.

User response: Edit the input file either to remove orto correct the invalid line, and retry the cicscvtcommand. Refer to the TXSeries Infocenter for moredetail.

Destination:

stderr

ERZ002026E lineNumber: Invalid character ’character’in DFHCNV macro

Explanation: The input file you requested cicscvt toprocess contains an invalid ’character’ on linelineNumber. The only valid characters outside stringsare letters, digits, =, ,, (, and ).


User response: Edit the input file to correct the invalidcharacter, and retry the cicscvt command.

Destination:

stderr

ERZ002027E lineNumber: No closing quote in string

Explanation: The closing quote for a string must occurbefore the end of the record. ’lineNumber’ is the numberof the line that lacks a closing quote.


ERZ002021E • ERZ002027E


User response: Edit the input file to add a closingquote to the string, and retry the cicscvt command.

Destination:

stderr

ERZ002028W lineNumber: Invalid single in string

Explanation: You must use in your input file to get asingle in a string.


User response: Edit the input file to correct the singlein the string, and retry the cicscvt command.

Destination:

stderr

ERZ002029E lineNumber: DFHCNV macro options’optionName1’ and ’optionName2’ conflict

Explanation: The input file you requested cicscvt toprocess contains options to a DFHCNV macro that aremutually exclusive.


User response: Edit the input file to remove one of theconflicting DFHCNV macro options, and retry thecicscvt command. Refer to the TXSeries Infocenter formore detail.

Destination:

stderr

ERZ002030W Conversion template file is empty

Explanation: The input file you requested cicscvt toprocess did not contain anything.

System action: The cicscvt command terminatesnormally.

User response: Run the cicscvt command again, usinga valid input file.

Destination:

stderr

ERZ002039W lineNumber: DFHCNV TYPE=FINALmacro is missing

Explanation: The cicscvt command expected to find aDFHCNV TYPE=FINAL statement on the given line,but was unable to find one. Every file that needs to betranslated by cicscvt must have a DFHCNVTYPE=FINAL as the last line in the file.

System action: The cicscvt command processes the

files requested and terminates with exit code 1.

User response: Edit the input file to add a DFHCNVTYPE=FINAL statement, and retry the cicscvtcommand.

Destination:

stderr

ERZ002040W lineNumber: Duplicate option’optionName’. The last options argumentspecified is used.

Explanation: The specified option has been specifiedmore than once for this DFHCNV macro. The lastoptions argument specified is used. All other values areignored.

System action: The cicscvt command ignores the firstoccurrences of the DFHCNV macros duplicated optionsand continues to process the rest of the input file.

User response: Edit the input file to remove theduplicate options in the DFHCNV macro statement andretry the command.

Destination:

stderr

ERZ002041W lineNumber: Option ’optionName’ isinvalid for DFHCNV macro type’macroType’

Explanation: The cicscvt command has encounteredan option that is not valid for the DFHCNV macrostatement of the specified type.

System action: The cicscvt command ignores theoption for the DFHCNV macro statement andcontinues to process the rest of the input file.

User response: Edit the input file to remove theinvalid option and retry the command.

Destination:

stderr

ERZ002042W lineNumber: The CDEPAGE option inDFHCNV TYPE=ENTRY statement isignored

Explanation: The cicscvt command does not supportthe CDEPAGE option for DFHCNV TYPE=ENTRYmacro statement. To specify the client and server codepages, use the options CLINTCP and SRVERCPrespectively.

System action: The cicscvt command ignores theDFHCNV macro statement and continues to processthe rest of the input file.

User response: Edit the input file to remove theCDEPAGE option and replace it with CLINTCP andSRVERCP options, if required, and retry the command.

ERZ002028W • ERZ002042W


Destination:

stderr

ERZ002043E lineNumber: The DFHCNV macrostatement contains invalid DATA

Explanation: The cicscvt command has encounteredinvalid data for the DATA option for DFHCNVTYPE=SELECT macro.

System action: The cicscvt command ignores theDFHCNV macro option and continues to process therest of the input file.

User response: Edit the input file to correct theargument to the DATA option and retry the command.

Destination:

stderr

ERZ002044E lineNumber: The length of a token stringin the DFHCNV macro statement is toolong

Explanation: The cicscvt command encountered atoken or string that was too long. Usually this is causedby a missing delimiter such as a closing quote in aquoted string.

System action: The cicscvt command terminates.

User response: Edit the input file to check that thereare no long words and that quoted string areterminated correctly. Then retry the command.

Destination:

stderr

ERZ002045E CICS has detected a signatureinconsistency in the conversion template’resourceName’ being released. Expectedsignature ’expectedSignature’.

Explanation: CICS detected a signature inconsistencyin the conversion template for resource, ’resourceName’,and was unable to release the template from the TaskShared Pool. This is likely to be caused by a user’sapplication program that has corrupted the Task SharedPool, in which case a symptom record is written to thesymrecs file.

System action: None

User response: Observe any messages that precedethis message and consider restarting the region as soonas possible to clear up any Task Shared Pool memoryproblems. If the symptoms still persist, contact yoursupport organization.

Destination:

stderr

ERZ002046E Unsuccessful attempt to releaseconversion template for resource’resourceName’ of class ’className’ frommemory

Explanation: CICS was unable to release theconversion template for resource, ’resourceName’, ofclass, ’className’, from the Task Shared pool. This islikely to be caused by a user’s application program thathas corrupted the Task Shared Pool, in which case asymptom record is written to the symrecs file.

System action: None


Destination:

CSMT

ERZ002047E CICS has detected a signatureinconsistency in the conversion template’resourceName’ being accessed. Expectedsignature ’expectedSignature’.

Explanation: CICS detected an inconsistency in theconversion template data contained in the Task SharedPool. This is likely to be caused by a user’s applicationprogram that has corrupted the Task Shared Pool, inwhich case a symptom record is written to the symrecsfile.

System action: None


Destination:

CSMT

ERZ002051E lineNumber: Missing ’typeintro’ introducerin DFHCNV macro

Explanation: The file you requested cicscvt to processdid not have the keyword ’typeintro’ introducerspecified in the DFHCNV macro on line lineNumber.Each DFHCNV macro must have the ’typeintro’introducer specified.

System action: The cicscvt command ignores thestatement and continues to process the rest of the file.The cicscvt command terminates with exit code 1.

User response: Edit the input file to add the ’typeintro’introducer to the DFHCNV macro, and retry thecommand.

Destination:

ERZ002043E • ERZ002051E


stderr

ERZ002053W lineNumber: DFHCNV macro option’optionName’ is ignored

Explanation: A DFHCNV macro option encounteredby cicscvt was ignored because one or more otheroptions override the ignored option.

System action: The cicscvt command ignores theoption and associated parameter, and continues toprocess the rest of the input file.

User response: Edit the input file to remove theredundant option and retry the command.

Destination:

stderr

ERZ002054E lineNumber: The DFHCNV macro doesnot contain the mandatory option’optionName’

Explanation: The file you requested cicscvt to processdid not have the required ’optionName’ specified in theDFHCNV macro on line ’lineNumber’. This option mustbe specified for the DFHCNV macro at line lineNumber.

System action: The cicscvt command ignores thestatement line and continues to process the rest of thefile. This can possibly lead to many error messagesbeing produced, especially if the ignored statementcontains the DFHCNV macro TYPE=ENTRY/SELECT.

User response: Edit the input file to add the missingoption to the DFHCNV macro, and retry the command.

Destination:

stderr

ERZ002055E lineNumber: Invalid DFHCNV macrooption ’optionName’ was specified

Explanation: The file you requested cicscvt to processhad an invalid ’optionName’ specified at line lineNumber.

System action: The cicscvt command ignores theinvalid operand and continues to process the rest of theinput file.

User response: Edit the input file to remove or correctthe invalid option and retry the command.

Destination:

stderr

ERZ002056E lineNumber: DFHCNV macro option’optionName’ has invalid hexadecimaldata

Explanation: The DFHCNV macro option ’optionName’contains incorrect hexadecimal data on line lineNumber.There is possibly an odd number of hexadecimal digits

or a digit that is not within the hexadecimal range.

System action: The cicscvt command ignores thestatement and continues to process the rest of the file.

User response: Edit the input file to correct thehexadecimal data associated with the ’optionName’ andretry the command.

Destination:

stderr

ERZ002058E lineNumber: Resource definition’resourceName’ already defined

Explanation: The resource definition ’resourceName’ forDFHCNV TYPE=ENTRY macro has already beenspecified in the input file.

System action: The cicscvt command ignores theoption and its arguments, and continues to process therest of the file.

User response: Edit the input file to change theresource name so that is unique, and retry thecommand.

Destination:

stderr

ERZ002064W lineNumber: The DFHCNV macrospecifies DATATYP=USERDATA butUSREXIT has previously been set to NO

Explanation: To be able to use the user-replaceableconversion DFHUCNV module, as implied byDFHCNV DATATYP=USERDATA, you must supply aUSREXIT option value of YES.

System action: The cicscvt command ignores theoption DATATYP=USERDATA and continues to processthe rest of the input file. At run-time, the user-exit isnot called to convert the user data.

User response: If the user-exit is to be invoked atrun-time, edit the input file to change the USREXIToption for the current resource name to YES.

Destination:

stderr

ERZ002065E lineNumber: Invalid value ’optionValue’for option ’optionName’ in DFHCNVmacro

Explanation: The file you requested cicscvt to processhad a DFHCNV macro option that had an invalid valueat line lineNumber.

System action: The cicscvt command ignores theinvalid option and continues to process the rest of theinput file.

User response: Edit the input file to change the value

ERZ002053W • ERZ002065E


of the option specified and retry the command. Consultthe TXSeries Infocenter and its following sections forvalues expected for the option.

Destination:

stderr

ERZ002066E lineNumber: Invalid argument’argumentValue’ for option ’optionName’ inDFHCNV macro

Explanation: The file you requested cicscvt to processhad a DFHCNV macro option that had an invalidargument at line lineNumber.

System action: The cicscvt command ignores theinvalid option and continues to process the rest of theinput file.

User response: Edit the input file to change theargument to the option specified, then retry thecommand. Consult the TXSeries Infocenter forarguments expected for the option specified.

Destination:

stderr

ERZ002067E lineNumber: Unexpected DFHCNVTYPE=KEY macro. This macro is onlyvalid for resource type FC.

Explanation: The DFHCNV TYPE=KEY macro canonly be defined in the input file for the resource typeFC. The macro cannot be used in definitions whoseresource type is TS, TD, IC or PC.


User response: Edit the input file to remove theDFHCNV TYPE=KEY macro statement, or change theresource type of the current resource type to FC, andretry the command.

Destination:

stderr

ERZ002068E lineNumber: Unexpected DFHCNV macrostatement. The first DFHCNV macroshould be TYPE=INITIAL.

Explanation: The DFHCNV TYPE=INITIAL macromust be the first DFHCNV macro statement in thesource file to establish the beginning of the conversiontable.


User response: Edit the input file to add the DFHCNVTYPE=INITIAL macro statement as the first DFHCNV

macro statement in the file, and retry the command.

Destination:

stderr

ERZ002069E lineNumber: Unexpected DFHCNV macrostatement encountered. Expected to haveTYPE=ENTRY specified.

Explanation: The input file did not have a DFHCNVTYPE=ENTRY macro to identify the current resource.cicscvt encountered an unexpected DFHCNV macro,(typically with TYPE=KEY/SELECT/FIELD) at a pointwhere no resource had been defined. To define eachconversion template, there must be a valid DFHCNVTYPE=ENTRY macro before any resource-specificmacros.


User response: Edit the input file to add the DFHCNVTYPE=ENTRY macro statement for the resource that isbeing defined at line lineNumber and retry thecommand.

Destination:

stderr

ERZ002070E lineNumber: Unexpected DFHCNV macrostatement. Expected to haveTYPE=SELECT or TYPE=KEY specified.

Explanation: The input file to cicscvt had noconversion template select or key template macros,DFHCNV TYPE=SELECT or TYPE=KEY, defined forthe current resource type. There must be at least oneDFHCNV TYPE=SELECT or TYPE=KEY macro after aresource-type initialization DFHCNV TYPE=ENTRYmacro.

System action: The cicscvt command ignores theDFHCNV macro statement and continue to process therest of the input file. If there are any further resourcetype TYPE=FIELD macros that do not have aTYPE=SELECT macro defined before, then each ofthese produces this message.

User response: Edit the input file to add the DFHCNVTYPE=SELECT or TYPE=KEY macro statement for theresource that is being defined at line lineNumber andretry the command.

Destination:

stderr

ERZ002066E • ERZ002070E


ERZ002071E lineNumber: Unexpected DFHCNV macrostatement. Expected to haveTYPE=FIELD specified.

Explanation: The input file lacks the optionLAST=YES on the only, or the last consecutive,DFHCNV TYPE=FIELD macro following either aDFHCNV TYPE=KEY macro or a DFHCNVTYPE=SELECT macro. There must be a LAST=YESoption in each such group within a conversiontemplate, and and it must be on the last TYPE=FIELDmacro in the group.


User response: Edit the input file to include aDFHCNV TYPE=FIELD,...,LAST=YES macro statementfor the set of conversions that is being defined at orbefore line lineNumber and retry the command.

Destination:

stderr

ERZ002072E lineNumber: Unexpected DFHCNV macrostatement. Expected to haveTYPE=SELECT specified.

Explanation: There must be a DFHCNVTYPE=SELECT macro defined for the current resourcetype. The previous DFHCNV TYPE=SELECT macrodefinition in the file for the same resource was not thedefault definition. A default TYPE=SELECT macro isrequired to finish a resource type conversion template.


User response: Edit the input file to add the DFHCNVTYPE=SELECT macro statement for the resource that isbeing defined at line lineNumber, or correct any error inthe preceding macro statements, and retry thecommand.

Destination:

stderr

ERZ002073E lineNumber: Unexpected DFHCNV macrooption. Expected to haveOPTION=DEFAULT specified.

Explanation: The current resource ENTRY hasUSREXIT=YES specified. With USREXIT=YES specified,OPTION=COMPARE is not allowed in any of theDFHCNV TYPE=SELECT statements for that resource.


User response: Edit the input file to change the

DFHCNV TYPE=SELECT macro so that it has theOPTION=DEFAULT and retry the command.

Destination:

stderr

ERZ002074E lineNumber: DFHCNV macro statementbefore TYPE=INITIAL or afterTYPE=FINAL is ignored

Explanation: There is a DFHCNV macro statementeither before the DFHCNV TYPE=INITIAL or after theDFHCNV TYPE=FINAL macros. These macrostatements are invalid and are ignored by cicscvt.

System action: The cicscvt command ignores theDFHCNV macro statement and continue to process therest of the input file.

User response: Edit the input file to remove anyDFHCNV macro statements before and after the macrosDFHCNV TYPE=INITIAL and DFHCNV TYPE=FINAL,respectively.

Destination:

stderr

ERZ002075E lineNumber: The DFHCNV TYPE=FINALstatement is not expected

Explanation: There is a DFHCNV TYPE=FINALmacro statement before the definition of a conversiontemplate has been completed.

System action: The cicscvt command terminates thetranslation prematurely.

User response: Edit the input file to remove theDFHCNV TYPE=FINAL macro or to change the currentconversion template so that it has been completelydefined.

Destination:

stderr

ERZ002076W lineNumber: The option ’optionName’ hasbeen assigned the DEFAULThexadecimal value value

Explanation: A DFHCNV macro option has beenomitted, although its value is required, so cicscvtassigned the option a default value.

System action: The cicscvt command continues toprocess the rest of the input file.

User response: Edit the input file to assign a value tothe ’optionName’ and retry the command.

Destination:

stderr

ERZ002071E • ERZ002076W


ERZ002077E lineNumber: Unexpected DFHCNVTYPE=INITIAL statement. Only oneDFHCNV TYPE=INITIAL statement canbe specified in a conversion templatefile.

Explanation: There is more than one DFHCNVTYPE=INITIAL macro statement for the conversiontemplate.

System action: The cicscvt command terminates thetranslation prematurely.

User response: Edit the input file to remove theduplicate DFHCNV TYPE=INITIAL macros, and retrythe command.

Destination:

stderr

ERZ002078W lineNumber: Unexpected end ofDFHCNV macro statement

Explanation: More macro options were expectedwhere the end of line appears. Typically, this warningis generated if a macro statement terminates with acomma.


User response: Edit the input file to terminate theDFHCNV macro correctly and retry the command.

Destination:

stderr

ERZ002079E lineNumber: Missing left parenthesis inDFHCNV macro statement

Explanation: A list for a DFHCNV macro option wasnot enclosed by parentheses. All lists must be enclosedby parentheses.


User response: Edit the input file to add theparentheses around the list of arguments and retry thecommand.

Destination:

stderr

ERZ002080E lineNumber: Missing right parenthesis inDFHCNV macro statement

Explanation: A list for a DFHCNV macro option wasnot terminated by a right parenthesis. All lists must beenclosed by matching parentheses.

System action: The cicscvt command ignores the

DFHCNV macro statement and continues to processthe rest of the input file.

User response: Edit the input file to place parenthesesaround the list of arguments and retry the command.

Destination:

stderr

ERZ002081E lineNumber: Missing comma in DFHCNVmacro statement

Explanation: The DFHCNV macro contained somemacro options, or a list of arguments to an option, notseparated by commas.


User response: Edit the input file to add the missingcomma to the DFHCNV macro, and retry thecommand.

Destination:

stderr

ERZ002082E lineNumber: Missing equal sign inDFHCNV macro statement

Explanation: A macro option did not have a precedingequals sign at line ’lineNumber’ in the input file.

System action: The cicscvt command ignores theoperand and continues to process the rest of the inputfile.

User response: Edit the input file to add the missingequals sign to the DFHCNV macro, and retry thecommand.

Destination:

stderr

ERZ002083E lineNumber: The DFHCNV macrokeyword ’keyword’ has an invalidargument ’argumentValue’

Explanation: A DFHCNV macro keyword did nothave a valid argument on line lineNumber. For thekeyword TYPE, valid arguments are INITIAL, ENTRY,KEY, SELECT and FIELD.


User response: Edit the input file to change theDFHCNV macro’s keyword argument to one ofINITIAL, ENTRY, KEY, SELECT or FIELD and re-try.

Destination:

stderr

ERZ002077E • ERZ002083E


ERZ002086I The compiled template for resource’resourceName’ of type ’resourceType’ hasbeen written to ’fileName’

Explanation: The cicscvt command has successfullyproduced, from your input file, a file containing thecompiled data conversion template for the specifiedresource.

System action: The cicscvt command continues toprocess the rest of the input file if more resource typespecifications exist. Otherwise it terminates.

User response: None

Destination:

stderr

ERZ002087W lineNumber: The DFHCNV macro hasboth DATA and XDATA optionsspecified. The value associated with theoption XDATA is ignored.

Explanation: The cicscvt command encountered boththe DATA and XDATA options specified in theDFHCNV macro. The data associated with the XDATAoption is ignored.

System action: The cicscvt command ignores thevalue associated with the XDATA option and continuesto process the rest of the input file.

User response: Edit the input file to remove one of theoptions DATA and XDATA and retry the command.

Destination:

stderr

ERZ002089E Unsuccessful memory allocation to loadconversion template information

Explanation: CICS was unable to load a conversiontemplate into memory as there was a memory shortage.

System action: This results in no conversion takingplace.

User response: Try again when the system has morememory available. If the problem persists, contact yoursupport organization.

Destination:

CSMT

ERZ002090E The resource ’resourceName’ in class’className’ is not defined in the runtimedatabase

Explanation: CICS tried to load the resource namesconversion template file, but found that it was notdefined in the runtime database.

System action: This results in no conversion takingplace.

User response: Update the runtime database so thatthe resource name is defined in the runtime database.

Destination:

CSMT

ERZ002091E The conversion template filename forresource name ’resourceName’ is too long

Explanation: CICS attempted to get the resourceconversion template file, but found that the completepathname was too long.

System action: The template is not retrieved and noconversion takes place.

User response: Install the conversion template filehigher up in the directory structure. Contact yoursupport organization.

Destination:

CSMT

ERZ002092E Unsuccessful open of conversiontemplate file ’fileName’. ’errorMessage’

Explanation: CICS was unable to open the specifiedfile for reading for the reason given by the operatingsystem as ’errorMessage’.

System action: CICS was unable to retrieve thetemplate and so no conversion is done.

User response: Check that the permissions are validfor reading on the conversion template file specified.Retry, and if this does not work then contact yoursupport organization.

Destination:

CSMT

ERZ002093E Unsuccessful attempt to read conversiontemplate file ’fileName’. ’errorMessage’

Explanation: CICS was unable to read in theconversion template file for the reason given by theoperating system as ’errorMessage’. This is possibly dueto corruption in the file that is being read.

System action: CICS was unable to retrieve theconversion template and so no conversion is done.

User response: Replace the conversion template filewith a recompiled version using cicscvt. If this messagestill persists, contact your support organization.

Destination:

CSMT

ERZ002086I • ERZ002093E


ERZ002094E The conversion template file ’fileName’ isincompatible with the current CICSrun-time system

Explanation: The version of cicscvt used to create theconversion template file ’fileName’ does not match thecurrent version of the CICS runtime system.

System action: CICS was unable to retrieve theconversion template and so no conversion is done.

User response: Replace the conversion template filewith a recompiled version using cicscvt. If this messagestill persists, contact your support organization.

Destination:

CSMT

ERZ002095E The conversion template file ’fileName’ isfor a different resource type

Explanation: CICS was unable to use the conversiontemplate file ’fileName’ as this file was defined to beused by a different resource type. This can happen if aconversion template file has been incorrectly installedor renamed.

System action: CICS was unable to retrieve the correctconversion template and so no conversion is done.

User response: Install the correct template, producedby cicscvt, for that resource type.

Destination:

CSMT

ERZ002096E The conversion template file ’fileName’ isfor resource name ’resourceName1’ andnot ’resourceName2’

Explanation: CICS was unable to use the conversiontemplate file ’fileName’ as this file was defined to beused by a different resource. This can happen if aconversion template file has been incorrectly installedor renamed.


User response: Install the correct template, producedby cicscvt, for that resource type and name.

Destination:

CSMT

ERZ002097E CICS has detected a signatureinconsistency when trying to load theconversion template ’fileName’. Expectedsignature ’signature’.

Explanation: CICS detected an inconsistency in thedata contained within the conversion template file. This

is likely to be caused by corruption of the conversiontemplate file.


User response: Install the correct template, producedby cicscvt, for that resource type and name. If theproblem persists, contact your support organization.

Destination:

CSMT

ERZ002098W lineNumber: The argument to theDFHCNV macro option ’optionName’ hasbeen truncated to ’truncatedOption’

Explanation: The cicscvt command has encounteredan argument to a DFHCNV macro option that is toolong, and so has truncated it to ’truncatedOption’.

System action: The cicscvt command truncates thename and continues to process the input file.

User response: Edit the input file to truncate theargument to the DFHCNV macro option and retry thecommand.

Destination:

stderr

ERZ002099W lineNumber: Hexadecimal value’optionValue’ for option ’optionName’exceeds boundary conditions. TheDEFAULT hexadecimal value’defaultValue’ has been assigned.

Explanation: The cicscvt command encountered aDFHCNV macro ’optionName’ that was assigned ahexadecimal value that was either too big or too small,and so cicscvt assigned the option a default value.

System action: The cicscvt command continues toprocess the rest of the input file.

User response: Edit the input file to assign a value tothe ’optionValue’ that is within boundary limits asspecified in the TXSeries Infocenter and retry thecommand.

Destination:

stderr

ERZ003001W Variable in RIDFLD option is shorterthan KEYLENGTH value

Explanation: The command level interpretertransaction (CECI) is checking the syntax of a filecontrol command, and the command specifies a CECIuser variable for the RIDFLD option which is shorterthan the value of the KEYLENGTH option.

System action: If there are no other errors during theCECI command syntax checking phase, then the phase

ERZ002094E • ERZ003001W


is completed successfully, and you are able to executethe command. During command execution, if thecommand updates the value in the user variablespecified for the RIDFLD option, then the value istruncated to the length of the user variable.

User response: Increase the size of the user variable sothat the length is equal to the value specified for theKEYLENGTH option.

Destination:

CECI user terminal

ERZ003002W PF/PA key undefined

Explanation: The user pressed a PF or PA key whoseaction is currently undefined.

System action: CECI waits for valid input.

User response: Use only the supported keys.

Destination:

CECI user terminal

ERZ003003W Invalid numeric value ignored

Explanation: A numeric value has been badlyspecified and has been ignored. It is possibly out ofrange or possibly contains invalid characters.

System action: If there are no other errors during theCECI command syntax checking phase, then the phaseis completed successfully, and you are able to executethe command. During command execution, if thecommand updates the value in the user variablespecified, then the value is truncated to the length ofthe user variable.

User response: Correct the value as appropriate.

Destination:

CECI user terminal

ERZ003004W Invalid hex characters ignored

Explanation: Invalid hexadecimal digits have beentyped in a hexadecimal input field. The invalid hexpairs are ignored.

System action: If there are no other errors during theCECI command syntax checking phase, then the phaseis completed successfully, and you are able to executethe command.


Destination:

CECI user terminal

ERZ003005W Invalid negative value ignored

Explanation: The length field for a variable has beenbadly specified, and has been ignored.

System action: If there are no other errors during theCECI command syntax checking phase, then the phaseis completed successfully, and you are able to executethe command. During command execution, if thecommand updates the value in the user variablespecified, then the value is truncated to the length ofthe user variable.


Destination:

CECI user terminal

ERZ003007E Invalid name

Explanation: Invalid characters have been entered inname field. Names are restricted to alphanumericvalues.


User response: Correct the name as appropriate.

Destination:

CECI user terminal

ERZ003008E Duplicate name

Explanation: This message indicates that the variablename being defined already exists.


User response: Correct the name as appropriate.

Destination:

CECI user terminal

ERZ003009E Variable does not exist or is null

Explanation: A variable name being used does notexist, or has no contents.


User response: Create the variable with the necessaryvalue.

Destination:

CECI user terminal

ERZ003010E Variable cannot be created

Explanation: A variable name being used does notexist, and there is insufficient space to create it.


User response: Delete any unused variables and retry.

ERZ003002W • ERZ003010E


Destination:

CECI user terminal

ERZ003011E RIDFLD must be a variable forbrowsing

Explanation: The command level interpretertransaction (CECI) is checking the syntax of a filecontrol browse command, and the command specifies aliteral value for the RIDFLD option.


User response: Specify a user variable for the RIDFLDoption and retry.

Destination:

CECI user terminal

ERZ003012E Variable in FROM option is shorter thanlength value

Explanation: The command level interpretertransaction (CECI) is checking the syntax of acommand which specifes a FROM option using a uservariable, with an explicit LENGTH or FLENGTHoption. The size of the user variable is shorter than thatrequested by the explicit length option.

System action: CECI waits for valid input changingthe size of the user variable or the length option.

User response: Increase the size of the user variable sothat the length is equal to or greater than the valuespecified for the length option. Alternatively, reduce thesize given in the length option.

Destination:

CECI user terminal

ERZ004001I Usage: cicstran [-PDdesv] [-c number][-g locale] [-l language] [-O outputfile ][-q APOST | QUOTE] file

Explanation: You entered the cicstran commandincorrectly.

System action: The cicstran command terminates withexit code 2. No further messages are produced. Notranslated output files are produced.

User response: Retry the command using validsyntax, as shown in the message.

Destination:

stderr

ERZ004002I Usage: cicstcl [-adesvp] [-c number] [-glocale] [-l Language][-q{APOST|QUOTE}] [-x ″ExternalCmd″] [-X ″External Cmd″] File

Explanation: You entered the cicstcl commandincorrectly.

System action: The cicstcl command terminates withexit code 2. No further messages are produced. Notranslated/compiled output files are produced.

User response: Retry the command using validsyntax, as shown in the message.

Destination:

stderr

ERZ004004W Translator flag ’flagName’ ignored.

Explanation: You specified a valid flag for cicstran orcicstcl under incorrect circumstances. For example, aflag that you entered can be valid for one language butnot for the language you specified.

System action: The cicstran or cicstcl commandignores the specified flag and continues the translation.

User response: No immediate response is required.Retry the command with valid flags if you do not wishto see this warning.

Destination:

stderr

ERZ004005E Unsuccessful open of input file’fileName’; error code errorCode

Explanation: The file you requested cicstran or cicstclto process was unable to be opened for the reasondefined by the operating system error code.

System action: The cicstran or cicstcl commandterminates with exit code 2. No translated output filesare produced.

User response: Check that the file you entered is validand has the correct read permissions and retry. If theproblem persists contact your support organization

Destination:

stderr

ERZ004006E [ Missing quote or incorrect column forEXEC command string continuation.

Explanation: The EXEC command you entered in theapplication source file contains a quote or doublequote, followed by a newline character before column73.

System action: The cicstran or cicstcl commandterminates with exit value 1. The translated output ispossibly not compilable.

User response: Edit the input application source file tocorrect the continuation line command specified at theline number and retry.

Destination:

ERZ003011E • ERZ004006E


stderr

ERZ004007E Unsuccessful close of input file’fileName’; error code errorCode.

Explanation: The file you requested cicstran or cicstclto process was unable to be closed for the reasondefined by the operating system error code.

System action: The cicstran or cicstcl commandterminates with exit code 2. The translated output ispossibly not compilable.

User response: Check that there is enough space lefton the disk and try the translation again. If the problemstill persists contact your support organization.

Destination:

stderr

ERZ004008E Unsuccessful open of output file’fileName’; error code errorCode.

Explanation: The output file produced by cicstran wasunable to be opened for the reason defined by theoperating system error code.

System action: The cicstran or cicstcl commandterminates immediately with value 2 withoutproducing a translated output file.

User response: Check the environment (for example,the disk space available) and retry. If the problem stillpersists, contact your support organization.

Destination:

stderr

ERZ004009E [ ’lineno:’ macro cannot contain a newline character.

Explanation: You have a newline character betweenthe parentheses of the argument to the specified DFHmacro in your input application file.

System action: The cicstran or cicstcl commandterminates with exit value 1. The translated output isnot compilable.

User response: Remove the newline character in theDFH macro in the application source file and retry.

Destination:

stderr

ERZ004010E Unsuccessful close of output file’fileName’; error code errorCode.

Explanation: The output file produced by eithercicstran or cicstcl was unable to be closed for thereason defined by the operating system error code.

System action: The cicstran or cicstcl commandterminates immediately with value 2, producing a

non-compilable translated output.

User response: Check the environment (for example,the disk space available) and retry. If the problem stillpersists, contact your support organization.

Destination:

stderr

ERZ004011E Unsuccessful attempt to set locale to’localeName’.

Explanation: The locale you specified to cicstran usingthe -g option is not valid.

System action: The cicstran or cicstcl commandterminates immediately with exit value 2, withoutproducing a translated output file.

User response: Retry the command with a valid -goption.

Destination:

stderr

ERZ004012E Unsuccessful write to output file’fileName’; error code errorCode.

Explanation: The cicstran or cicstcl command wasunable to write to file fileName for the reason definedby the operating system error code.

System action: The cicstran or cicstcl commandterminates immediately with exit value 2 and possiblyproduces a non-compilable, partially translated outputfile.

User response: Use the operating systemdocumentation to find the meaning of the return codefrom the function fwrite().

Destination:

stderr

ERZ004013E Unsuccessful read of input applicationfile ’fileName’; error code errorCode.

Explanation: The file you requested cicstran or cicstclto process was not able to be read for the reasondefined by the operating system error code.

System action: The cicstran or cicstcl commandterminates immediately with exit value 2 and possiblyproduces a non-compilable, partially translated outputfile.

User response: Use the operating systemdocumentation to find the meaning of the return codefrom the function fread().

Destination:

stderr

ERZ004007E • ERZ004013E


ERZ004014E The CICS translator cannot find thesupport module for programminglanguage ’loadmodule’, or the supportmodule is invalid

Explanation: The language module you supplied tocicstran or cicstcl using the -l option was unable to beloaded. cicstran and cicstcl support the C and COBOLlanguages for CICS. The cicstran translator dynamicallyloads a support module for a programming languagewhen requested (using the cicstran -l option [default-lCOBOL]). If the cicstran translator cannot find thesupport module for a language, or the support moduledoes not exist, or has an invalid internal format, thencicstran generates this message. The support module ispossibly missing because CICS does not support theprogramming language, the operating environment setup is incorrect, or the load module is incorrectlyformatted.

System action: The cicstran or cicstcl commandterminates immediately with exit value 2, and producesno translated output files.

User response: Check that the language you requestedis valid and try again. If the problem persists thencontact your support organization.

Destination:

stderr

ERZ004015E Unsuccessful attempt to initialize atranslator environment.

Explanation: The cicstran or cicstcl command wasunable to set up an internal translation facilitiesenvironment. Insufficient memory was available.

System action: This message can be produced from anumber of facilities of CICS, including cicstran andcicstcl, and CICS transactions such as CECI and CECS.The action taken by the system can differ according tothe facility being run. cicstran or cicstcl terminatesimmediately with exit value 2, and does not produce atranslated output file.

User response: In most cases try again later when thesystem has more memory available. If the problempersists, contact your support organization.

Destination:

stderr

ERZ004016E Unsuccessful memory allocation fortranslator cross-reference storage; errorcode errorCode

Explanation: Your request for a cross-reference fileproduced by the cicstran translator was unsuccessfuldue to shortage of memory.

System action: The cicstran or cicstcl commandterminates immediately with exit value 2 and possibly

produces a non-compilable, partially translated outputfile.

User response: Try again later when the system hasmore memory available. If the problem persists, contactyour support organization.

Destination:

stderr

ERZ004017E [ Continuation character or literalexpected.

Explanation: The cicstran or cicstcl commandencountered a string literal in your COBOL applicationprogram that did not have either the closing quotes ora continuation character.

System action: The cicstran or cicstcl commanddisplays this message and tries to translate the rest ofthe file. A non-compilable translated file is produced.

User response: Edit the input application source file tocorrect the line that is indicated.

Destination:

stderr

ERZ004019E Unsuccessful attempt to specify time inoutput listing files. No listing file willbe produced.

Explanation: The time text string obtained from theoperating system was too big for the CICS internalbuffer.

System action: The cicstran command continues totranslate the application source file but does notproduce a listing or cross-reference file as requested.


Destination:

stderr

ERZ004020E [ Command ’lineno:’ not recognized.

Explanation: A command has been encountered that isnot recognized. This message can be produced from anumber of facilities of CICS, including cicstran andcicstcl, and CICS transactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues with the translation but terminates withvalue 1 and produces a non-compilable, partiallytranslated output file. The CICS transaction CECIdisplays the error but does not let you execute thecommand.

User response: If you are using cicstran or cicstcl thenyou must edit the input source application program tocorrect the command at the given line and retry thetranslation. If you are using the CICS transactions suchas CECI, CEMT or CECS then you must amend the

ERZ004014E • ERZ004020E


command by overtyping and retry.

Destination:

stderr

ERZ004021W [ Invalid command introducer ’lineno:’specified.

Explanation: A command introducer, that is akeyword which introduces a command for exampleEXEC, was encountered that was not recognized. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICStransactions such as CECI and CECS.

System action: cicstran or cicstcl continues totranslate and terminates with exit value 0. A compilabletranslated file is produced, but the warning messagemust be considered.

User response: If you are using cicstran or cicstcl thenyou must edit the input application source file andcorrect the command introducer at the specified linenumber and retry the translation.

Destination:

stderr

ERZ004022E [ Command ’lineno:’ is not valid forenvironment or language.

Explanation: A command was encountered that is notsupported in your environment or your applicationsprogramming language. This message can be producedfrom a number of facilities of CICS, including cicstranand cicstcl, and CICS transactions such as CECI andCECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile but terminates with exit value 1. A non-compilabletranslated output file is produced. The CICS transactionCECI displays the error, but does not let you executethe command. The CICS transaction CECS simplydisplays the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andremove/change the command indicated by the linenumber and retry the translation. If this command isabsolutely required then you must change the languageof the source application program to one that acceptsthe required command. If you are using the CICStransactions CECI or CECS then you must change thecommand so that it is valid and retry.

Destination:

stderr

ERZ004023E [ Invalid command option ’lineno:’.

Explanation: A command option was encountered thatis not valid for the command being analysed. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICStransactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile but terminates with exit value 1. A non-compilable,partially translated output file is produced. The CICStransaction CECI displays the error but does not letyou execute the command. The CICS transaction CECSsimply displays the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andremove/change the command option indicated by theline number and retry the translation. If you are usingthe CICS transactions CECI or CECS then you mustchange the command option so that it is valid andretry.

Destination:

stderr

ERZ004024E [ Command requires the option, ’lineno:’,when ’]’ has been specified.

Explanation: A command option, ’]’ was specifiedwhich requires another command option ’lineno:’ forthe command to be valid. This message can beproduced from a number of facilities of CICS, includingcicstran and cicstcl, and CICS transactions such asCECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd/remove the appropriate command optionindicated at the line number specified and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must change the command option sothat it is valid and retry.

Destination:

stderr

ERZ004025E [ Command requires the option: ’lineno:’.

Explanation: A command option ’lineno:’ is requiredfor the command to be valid. This message can beproduced from a number of facilities of CICS, includingcicstran and cicstcl, and CICS transactions such asCECI and CECS.

ERZ004021W • ERZ004025E



User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the command option indicated at the line numberspecified, and retry the translation. If you are using theCICS transactions CECI or CECS then you must changethe command option so that it is valid and retry.

Destination:

stderr

ERZ004026E [ Command options ’lineno:’ and ’]’conflict.

Explanation: The command has mutually exclusiveoptions specified for the particular command. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICStransactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile but terminates with exit value 1. A non-compilable,partially translated output file is produced. The CICStransaction CECI displays the error but does not letyou execute the command. The CICS transaction CECSsimply display the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andremove one of the command options indicated, at theline number specified, and retry the translation. If youare using the CICS transactions CECI or CECS thenyou must change the command option so that it isvalid and retry.

Destination:

stderr

ERZ004027E [ Command option ’lineno:’ unexpected:only valid if ’]’ specified.

Explanation: An unexpected option, ’lineno:’, wasencountered that is valid for the command only if ’]’ isspecified. This message can be produced from anumber of facilities of CICS, including cicstran andcicstcl, and CICS transactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile but terminates with exit value 1. A non-compilable,partially translated output file is produced. The CICStransaction CECI displays the error, but does not letyou execute the command. The CICS transaction CECSsimply displays the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the command option indicated at the line numberspecified, and retry the translation. If you are using theCICS transactions CECI or CECS then you must changethe command option so that it is valid and retry.

Destination:

stderr

ERZ004028E [ Command option ’lineno:’ hasunmatched parenthesis.

Explanation: The command option, ’lineno:’, has amissing opening or closing parenthesis for its requiredargument. This message can be produced from anumber of facilities of CICS, including cicstran andcicstcl, and CICS transactions such as CECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the missing left/right parenthesis to the commandoption indicated, at the line number specified, and retrythe translation. If you are using the CICS transactionsCECI or CECS then you must correct the missingparenthesis for the command option so that it is validand retry.

Destination:

stderr

ERZ004029E [ Option ’lineno:’ is not valid for theenvironment or language.

Explanation: The option, ’lineno:’, is not a valid optionfor the specified command in your environment or thelanguage of your input application program. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICStransactions such as CECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andremove the command option indicated at the linenumber specified, and retry the translation. If you areusing the CICS transactions CECI or CECS then you

ERZ004026E • ERZ004029E


must remove the command option so that it is validand retry.

Destination:

stderr

ERZ004030W [ No argument for command option’lineno:’ expected.

Explanation: An argument was specified for acommand option that expects no arguments. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICStransactions such as CECI and CECS.

System action: cicstran and cicstcl ignore theargument associated with the specified option, continueto translate the rest of the input application file, andterminate with exit value 0. A compilable translatedoutput file is produced. The CICS transaction CECIdisplays the warning and lets you execute thecommand. The CICS transaction CECS simply displaysthe warning.

User response: If you are executing cicstran or cicstclthen you can edit the input application source file,remove the command option’s argument at the linenumber specified, and retry the translation. If you areusing the CICS transactions CECI or CECS then youcan change the command option so that it is valid andretry.

Destination:

stderr

ERZ004031E [ Option ’lineno:’ expected DATA-VALUEargument.

Explanation: The option, ’lineno:’, had a missingargument that needs to be a data value. This messagecan be produced from a number of facilities of CICS,including cicstran and cicstcl, and CICS transactionssuch as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile but terminates with exit value 1. A non-compilable,partly translated output file is produced. The CICStransaction CECI displays the error but does not letyou execute the command. The CICS transaction CECSsimply displays the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the data value argument to the command optionindicated, at the line number specified, and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must add the data value argumentto the command option so that it is valid and retry.

Destination:

stderr

ERZ004032E [ Option ’lineno:’ expected NAMEargument.

Explanation: The option, ’lineno:’, had a missingargument that needs to be a name. This message can beproduced from a number of facilities of CICS, includingcicstran and cicstcl, and CICS transactions such asCECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the name argument to the command optionindicated, at the line number specified, and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must add the name argument to thecommand option so that it is valid and retry.

Destination:

stderr

ERZ004033E [ Option ’lineno:’ expected DATA-AREAargument.

Explanation: The option, ’lineno:’, had a missingargument that needs to be a data area. This messagecan be produced from a number of facilities of CICS,including cicstran and cicstcl, and CICS transactionssuch as CECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the data area argument to the command optionindicated at the line number specified, and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must add the data area to thecommand option so that it is valid and retry.

Destination:

stderr

ERZ004034E [ Option ’lineno:’ expected PTR-VALUEargument.

Explanation: The option, ’lineno:’, had a missingargument that needs to be a pointer value. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICS

ERZ004030W • ERZ004034E


transactions such as CECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the pointer value argument to the command optionindicated at the line number specified, and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must add the pointer valueargument to the command option so that it is valid andretry.

Destination:

stderr

ERZ004035E [ Option ’lineno:’ expected PTR-REFargument.

Explanation: The option, ’lineno:’, had a missingargument that needs to be a pointer reference. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICStransactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile, but terminates with exit value 1. A non-compilable,partially translated output file is produced. The CICStransaction CECI displays the error but does not letyou execute the command. The CICS transaction CECSsimply displays the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the pointer reference argument to the commandoption indicated at the line number specified, and retrythe translation. If you are using the CICS transactionsCECI or CECS then you must add the pointer referenceargument to the command option so that it is valid andretry.

Destination:

stderr

ERZ004036E [ Option ’lineno:’ expected CVDAargument.

Explanation: The option, ’lineno:’, had a missingargument that needs to be a CVDA. This message canbe produced from a number of facilities of CICS,including cicstran and cicstcl, and CICS transactionssuch as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile but terminates with exit value 1. A non-compilable,

partially translated output file is produced. The CICStransaction CECI displays the error but does not letyou execute the command. The CICS transaction CECSsimply displays the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the CVDA argument to the command optionindicated at the line number specified, and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must add the CVDA argument to thecommand option so that it is valid and retry.

Destination:

stderr

ERZ004037E [ Option ’lineno:’ expected LABELargument.

Explanation: The option, ’lineno:’, had a missingargument that needs to be a label. This message can beproduced from a number of facilities of CICS, includingcicstran and cicstcl, and CICS transactions such asCECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd the label argument to the command optionindicated at the line number specified, and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must add the label argument to thecommand option so that it is valid and retry.

Destination:

stderr

ERZ004038E [ Option ’lineno:’ expected HHMMSSargument.

Explanation: The option, ’lineno:’, had a missingargument that needs to be in HHMMSS format. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICStransactions such as CECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file and

ERZ004035E • ERZ004038E


add the HHMMSS argument to the command optionindicated at the line number specified, and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must add the HHMMSS argument tothe command option so that it is valid and retry.

Destination:

stderr

ERZ004039W [ argument ’lineno:’ for macro ’]’ is notsupported.

Explanation: The CVDA ’lineno:’ for the ’]’ macro isvalid but is not supported for this version of CICS.

System action: The cicstran or cicstcl commandsubstitutes the correct value for the CVDA in the DFHmacro and continues to translate the input applicationfile, terminating with exit value 0. A compilabletranslated output file is produced, but as the warningindicates, the CVDA value is not supported by CICS.

User response: You must edit the input applicationsource file and remove or change the DFH macroargument indicated at the line number specified, andretry the translation.

Destination:

stderr

ERZ004040E [ Argument ’lineno:’ for macro ’]’ isinvalid.

Explanation: See the message. The CVDA ’lineno:’ forthe DFH ’]’ is an invalid CVDA and is not supported.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile but terminates with exit value 1. A non-compilabletranslated output file is produced.

User response: You must edit the input applicationsource file and remove or change the DFH macroargument indicated at the line number specified, andretry the translation.

Destination:

stderr

ERZ004041W [ ’lineno:’ is ambiguous. CICS assumes’]’.

Explanation: You specified ’lineno:’ on the commandon the line specified in the input file. This is ashortened version of a required option, ’]’, but it is alsoa shortened version of another option. CICS assumesthat you intended ’]’ for further analysis. This messagecan be produced from a number of facilities, includingcicstran and cicstcl, and CICS transactions such asCECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the input application file with the

specified command option as a substitute. If thecommand option CICS assumed is correct, then thecicstran or cicstcl command terminates with exit value0. A compilable translated output file is produced. Ifthe assumed command option is wrong, then furthererrors occur and the cicstran or cicstcl commandterminates with exit value 1. The CICS transactionCECI displays the warning and tries to execute thecommand. The CICS transaction CECS simply displaysthe warning.

User response: If you are executing cicstran or cicstcl,edit the input application source file to remove theambiguity in the command option on the line specifiedand retry the translation. If you are using the CICStransactions CECI or CECS then you can change thecommand option to be more specific and retry.

Destination:

stderr

ERZ004042E [ ’lineno:’ Macro requires (.

Explanation: The DFH ’lineno:’ has a missing openingparenthesis for its required argument.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile but terminates with exit value 1. A non-compilable,partially translated source file is produced.

User response: You must edit the input applicationsource file and add the argument’s opening parenthesisto the DFH macro argument indicated at the linenumber specified, and retry the translation.

Destination:

stderr

ERZ004043E [ Unexpected end of application sourcefile ’lineno:’

Explanation: You did not terminate one or more of thefollowing: a CICS statement; a statement enclosed inquotes; a comment statement; or an argument withoutthe closing parenthesis and the cicstran or cicstclreached the end of the file.

System action: The cicstran or cicstcl commandterminates with exit value 1 and produces anon-compilable translated output file.

User response: Edit the input application source file tocorrect the file accordingly and retry the translation.

Destination:

stderr

ERZ004039W • ERZ004043E


ERZ004045E [ Option ’lineno:’ expected DATA AREAnot string literal

Explanation: The argument specified with the ’lineno:’was a string literal and not a data area as was expectedfor that option. This message can be produced from anumber of facilities of CICS, including cicstran andcicstcl, and CICS transactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile, but terminates with exit value 1. A non-compilable,partially translated output file is produced. The CICStransaction CECI displays the error but does not letyou execute the command. The CICS transaction CECSsimply displays the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andremove one of the command options indicated, at theline number specified, and retry the translation. If youare using the CICS transactions CECI or CECS thenyou must change the command option so that it has adata area argument and retry.

Destination:

stderr

ERZ004046I Running the pre-translation -x step:’commandName’

Explanation: This is an information message to tellyou that the cicstcl pre-translation step is about to beexecuted.

System action: The cicstcl command executes thepre-translation step.

User response: None

Destination:

stderr

ERZ004047I Running the translation step:’commandName’

Explanation: This is an information message to tellyou that the cicstcl is about to invoke the translatorcicstran with the arguments specified.

System action: The cicstcl command executes thetranslation step.

User response: None

Destination:

stderr

ERZ004048I Running the post-translation -X step:’commandName’

Explanation: This is an information message to tellyou that the cicstcl post-translation step is about to beexecuted.

System action: The program cicstcl executes thepost-translation step.

User response: None

Destination:

stderr

ERZ004049I Running the compile and link step:’commandName’

Explanation: This is an information message to tellyou that the cicstcl is about to invoke the compile andlink steps.

System action: The cicstcl command executes thecompile and link step.

User response: None

Destination:

stderr

ERZ004050E Application path, ’pathName’, is too long

Explanation: The application pathname you specifiedto either cicstran or cicstcl was too long.

System action: The cicstran or cicstcl commandterminates immediately with exit value 2. No translatedoutput file is produced.

User response: Retry the command with a shorterpath name.

Destination:

stderr

ERZ004051W [ Option ’lineno:’ already specified.

Explanation: The command ’lineno:’ was alreadyspecified in the command and is therefore ignored.Only the first option is used. Therefore if you have adifferent argument associated with the repeated option,this is not used. This message can be produced from anumber of facilities of CICS, including cicstran andcicstcl, and CICS transactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile and terminates with exit value 0. A compilabletranslated output file is produced. The CICS transactionCECI displays the warning and lets you execute thecommand. The CICS transaction CECS simply displaysthe warning.

User response: If you are executing cicstran or cicstcl

ERZ004045E • ERZ004051W


then you must edit the input application source file andremove one of the command options indicated, at theline number specified, and retry the translation. If youare using the CICS transactions CECI or CECS thenyou must change the command option so that it isvalid and retry.

Destination:

stderr

ERZ004052E [ Command or DFH macro too long.

Explanation: The command or DFH macro did notterminate or the command contains unmatched quotes.

System action: The cicstran or cicstcl command writesthe untranslated command to the output file andcontinues to process the rest of the file.

User response: Edit the input application source file toterminate the command or DFH macro correctly, andretry the translation.

Destination:

stderr

ERZ004054E Unexpected Token FollowingPROCEDURE DIVISION

Explanation: You followed a PROCEDURE DIVISIONstatement in COBOL with a token that was notexpected. The translator expects to see either a USINGstatement or PERIOD directly after recognizing thePROCEDURE DIVISION Token.

System action: The cicstran or cicstcl commandterminates immediately with exit value 1. Anon-compilable translated output is produced.

User response: Edit the application source file tocorrect the PROCEDURE DIVISION statement in yourinput COBOL application program.

Destination:

stderr

ERZ004055E [ The command set ’lineno:’ specified isnot supported.

Explanation: A command set introducer was specifiedthat is not supported by CICS.

System action: The cicstran or cicstcl command doesnot translate the command set specified and continuesto translate the rest of the input file. A non-compilabletranslated output is produced.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andcorrect the command set introducer as indicated, at theline number specified, and retry the translation. If youare using the CICS transactions CECI or CECS then

you must change the command set introducer so that itis valid, and retry.

Destination:

stderr

ERZ004056W [ Option ’lineno:’ for command ignored.

Explanation: The ’lineno:’ for the command wasignored. This is possibly due to options that areallowed for compatibility purposes but are not actuallysupported by CICS. This message can be producedfrom a number of facilities, including cicstran andcicstcl, and CICS transactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the rest of the input applicationfile, while ignoring the option, and terminates with exitvalue 0. A compilable translated output file isproduced. The CICS transaction CECI displays thewarning and lets you execute the command. The CICStransaction CECS simply displays the warning.

User response: If you are executing cicstran or cicstclthen you can edit the input application source file andremove the option indicated, at the line numberspecified, and retry the translation. If you are using theCICS transactions CECI or CECS then you can removethe command option so that it is valid and retry.

Destination:

stderr

ERZ004057W [ Command is ambiguous, ’lineno:’ hasbeen assumed.

Explanation: A command that is ambiguous and canbe matched to another command has been encountered.CICS therefore assumes the ’lineno:’ for further analysis.This is possibly not the command you want to beanalysed. This message can be produced from anumber of facilities, including cicstran and cicstcl, andCICS transactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the input application file with thespecified command as a substitute. If CICS assumedthe correct command then cicstran or cicstcl terminateswith exit value 0. A compilable translated output file isproduced. If the assumed command is wrong, thenfurther errors occur and the cicstran or cicstclterminate with exit value 1. The CICS transaction CECIdisplays the warning and tries to execute thecommand. The CICS transaction CECS simply displaysthe warning.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andbe more specific about the command indicated, at theline number specified, and retry the translation. If youare using the CICS transactions CECI or CECS thenyou can change the command to be more specific andretry.

ERZ004052E • ERZ004057W


Destination:

stderr

ERZ004058E [ Option ’lineno:’ expected DATA AREAnot numeric value.

Explanation: The argument specified with the ’lineno:’was a numeric value and not a data area as wasexpected for that option. This message can be producedfrom a number of facilities, including cicstran andcicstcl, and CICS transactions such as CECI and CECS.

System action: The cicstran or cicstcl commandcontinues to translate the input application file butterminates with exit value 1. A non-compilable,partially translated output file is produced. The CICStransaction CECI displays the error but does not letyou execute the command. The CICS transaction CECSsimply displays the error.

User response: If you are executing cicstran or cicstclthen you must edit the input application source file andchange the argument of the option indicated to a dataarea and retry the translation. If you are using the CICStransactions CECI or CECS then you must change thecommand option’s argument type so that it is a dataarea argument and retry.

Destination:

stderr

ERZ004059W [ Command options ’lineno:’ and ’]’conflict, ’optionName’ assumed.

Explanation: The command has mutually exclusiveoptions specified and therefore CICS assumes’optionName’ for further analysis. This message can beproduced from a number of facilities, including cicstranand cicstcl, and CICS transactions such as CECI andCECS.

System action: The cicstran or cicstcl commandcontinues to translate the input application file with theassumed command and terminates with exit value 0. Acompilable translated output file is produced. The CICStransaction CECI displays the warning and does not letyou execute the command. The CICS transaction CECSsimply displays the warning.

User response: If you are executing cicstran or cicstclthen you can edit the input application source file andcorrect the command options indicated, at the linenumber specified, and retry the translation. If you areusing the CICS transactions CECI or CECS then youcan change the command option so that it is valid andretry. Edit the application source file and correct thecommand.

Destination:

stderr

ERZ004060I cicstran translation ended: errorCountuerror(s), warnCountu warning(s).

Explanation: This is an information message tellingyou how many errors and warnings were found bycicstran or cicstcl during translation.

System action: The cicstran command finishedtranslating. If there is an error in the file, then apartially translated, non-compilable file is produced. Ifthere are no errors, then a translated and compilablefile is produced. The cicstcl command continues to thecompilation stage if there were no errors.

User response: If there is an error check the inputapplication source file.

Destination:

stderr

ERZ004061W Argument for flag option -c cannothandle less than minLinePerPage.Assumed minLinePerPage lines of codeper page

Explanation: You entered a value to cicstran or cicstclfor the number of lines per page option, -c, for a listingor cross-reference file that is less than the minimumvalue. Therefore cicstran or cicstcl assumes theminimum value, minLinePerPage, for the number oflines per page in the output listing and cross-referencefiles.

System action: The cicstran or cicstcl commandignores the value associated with the specified -c flagand defaults to the minimum value. This value ispurely governed by the headers contained within theoutput listing file.

User response: Increase the value of the -c, lines perpage, option on the command line when invokingcicstran or cicstcl.

Destination:

stderr

ERZ004063E Unsuccessful memory allocation togenerate translated code.

Explanation: Your request for a translation by thecicstran or cicstcl translator was unsuccessful due toshortage of memory.

System action: The cicstran or cicstcl commandterminates immediately with exit value 2. Anon-compilable, partially translated output file ispossibly produced.

User response: Try again later when the system hasmore memory available. If the problem persists, contactyour support organization.

Destination:

ERZ004058E • ERZ004063E


stderr

ERZ004065W Argument for flag option -c cannothandle more than maxLinePerPage.Assumed maxLinePerPage lines of codeper page

Explanation: You entered a value to the programcicstran or cicstcl for the number of lines per pageoption, -c, for a listing or cross-reference file thatexceeds the maximum value. Therefore cicstran orcicstcl assumes the maximum value, maxLinePerPage,for the number of lines per page in the output listingand cross-reference files.

System action: The cicstran or cicstcl commandignores the value associated with the specified -c flagand defaults to the maximum value.

User response: Decrease the value of the -c, lines perpage, option on the command line when invokingcicstran or cicstcl.

Destination:

stderr

ERZ004066E [ Number of options for command ’]’exceeded ’lineno:’.

Explanation: A number of commands have a limit onthe number of options that can be handled. Thismessage expresses that the maximum number ofoptions for the command specified was exceeded. Thismessage can be produced from a number of facilities ofCICS, including cicstran and cicstcl, and CICStransactions such as CECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andchange the number of options so that it is below thelimit specified and retry the translation. If you areusing the CICS transactions CECI or CECS then youmust change the command number of options andretry.

Destination:

stderr

ERZ004067I Pre-translation -x step finished with exitcode: ’exitCode’

Explanation: Information message to tell you the exitcode of the command executed prior to the translationstage of cicstcl.

System action: The cicstcl command continues totranslate the input application file and, if successful,continues to the compile and link stage.

User response: If the exit code displayed is not therequired exit code then interrupt cicstcl with a Ctrl-Cand re-enter the corrected command.

Destination:

stderr

ERZ004068I Post-translation -X step finished withexit code: ’exitCode’

Explanation: Information message to tell you the exitcode of the command executed after the translationstage and before the compile stage of cicstcl.

System action: The cicstcl command continues toexecute the compile and link step.

User response: If the exit code displayed is not therequired exit code then interrupt cicstcl with a Ctrl-Cand re-enter the corrected command.

Destination:

stderr

ERZ004069E [ Command requires the option, ’lineno:’,when both ’]’ and ’optionName’ havebeen specified.

Explanation: The command option ’lineno:’ is requiredwhen the options ’]’ and ’optionName’ have both beenspecified in the command. This message can beproduced from a number of facilities of CICS, includingcicstran and cicstcl, and CICS transactions such asCECI and CECS.


User response: If you are executing cicstran or cicstclthen you must edit the input application source file andadd/remove the appropriate command optionindicated at the line number specified and retry thetranslation. If you are using the CICS transactions CECIor CECS then you must change the command option sothat it is valid and retry.

Destination:

stderr

ERZ004065W • ERZ004069E


ERZ004070W Option ’optionName’ must not specify avalue, value ignored.

Explanation: You entered a browse command on theterminal (using the ’NEXT’ keyword) along with thename of a resource to browse. This makes no sense.

System action: CICS continues processing as if theresource name had not been entered.

User response: Either retry the command withoutspecifying a resource name, or retry the commandusing a resource name but without the ’NEXT’keyword.

Destination:

stderr

ERZ004071E RIDFLD must be a fullword variable,type F, for RBA or RRN.

Explanation: You entered a read, write or deletecommand on the terminal with the RBA or RRN option(implying an ESDS or RRDS file) and specified aconstant RIDFLD. This is not allowed.

System action: CICS waits for you to enter a variablefor the RIDFLD option or remove the RBA or RRNoption.

User response: If the file you are using is ESDS orRRDS, then specify a fullword variable for the RIDFLD(which can be defined by pressing PF5). If you areusing a KSDS file then remove the RBA or RRN option,as these are not valid for this type of file.

Destination:

stderr

ERZ004072W Unsuccessful open of copybook’fileName’.

Explanation: The cicstran or cicstcl command wasunable to locate and open the specified copybook.

System action: The cicstran or cicstcl commandcontinues translation.

User response: If the specified copybook containsCICS statements ensure that it is pre-translated andthat it is either in the path specified in the COPYstatement or in the path specified by the COBCPYenvironment variable.

Destination:

stderr

ERZ004073W Error processing copybook ’fileName’.

Explanation: The cicstran or cicstcl command detectedan error while processing the specified copybook.

System action: The cicstran or cicstcl commandcontinues translation.

User response: Re-translate the specified copybook.

Destination:

stderr

ERZ004074W Program does not begin with anIdentification Division.

Explanation: The file translated did not contain anIdentification Division. It cannot be a complete COBOLprogram, but is possibly valid as a COPY book.

System action: The translator continues to translateany EXEC CICS commands but does not insert anyprologue or epilogue.

User response: None, if the file is designed to be usedas a COPY book.

Destination:

stderr

ERZ004075E Usage : argv[0] <cobolfile

Explanation: Wrong usage of cicscobinsert command.

System action: The cicscobinsert command failsreturning 1.

User response: Check usage and try again.

Destination:

stderr

ERZ004076E File ’Input’ could not be opened, errorreturned was ’%2$d’

Explanation: File compiled does not exist.


User response: Check the meaning of the errornumber when returned from the fopen() call, check filename and try again.

Destination:

stderr

ERZ004077E Error writing data into disk, errorreturned was ’Tobedetermined’

Explanation: Was unable to write temporary file intodisk.


User response: Check the meaning of the errornumber when returned from the fopen() call. Retry thecommand.

Destination:

stderr

ERZ004070W • ERZ004077E


ERZ004078E Error writing data into disk, errorreturned was ’Tobedetermined’

Explanation: Was unable to write temporary file intodisk.


User response: Check the meaning of the errornumber when returned from the fprintf() call. Retry thecommand.

Destination:

stderr

ERZ004079E File ’fileName’ could not be removed,error returned was ’%2$d’

Explanation: This message is output during acicscobinsert command if the input file was unable tobe removed.

System action: The command fails.

User response: Check the meaning of the errornumber when returned from the remove() call. Retrythe command.

Destination:

stderr

ERZ004080W Ignoring the -O option.. Assuming thedefault output file...

Explanation: cicstran could not find any output filestring, though the output option is specified.

System action: cicstran assume the default output file

User response: user needs to verify whether theoutput file is mentioned. Retry the command.

Destination:

stderr

ERZ004081E Invalid CICS option ’option’ specified.

Explanation: Invalid CICS option was specified

System action: compilation aborts

User response: Correct the CICS options andrecompile

Destination:

ERZ005001I Usage: cicsmap [-m mapname] [-a] [-e][-f codeSet] [-p|-s] [-r] [-x]fileName[.bms]

Explanation: You entered the cicsmap commandincorrectly.

System action: The cicsmap command terminates.

User response: Enter the cicsmap command using thecorrect syntax, as shown in the message. See theTXSeries Infocenter for more information.

Destination:

stderr

ERZ005002E Cannot convert between codesets’codeSet’ and ’currentCodeSet’.

Explanation: You cannot convert data between thecodesets specified. The ’codeSet’ is either specifiedexplicitly by the -f option or implicitly by the -e option.


User response: Check that you have specified a validcodeset and that a converter exists to convert from thatcodeset to the codeset of your locale. Enter thecommand again, using a valid codeset. See the TXSeriesInfocenter for more information.

Destination:

stderr

ERZ005003E You must specify exactly one fileargument.

Explanation: You entered the cicsmap command, butyou specified either zero or more than one filearguments.


User response: Enter the command again, but specifyonly one file argument. See the TXSeries Infocenter formore information.

Destination:

stderr

ERZ005004E Filename ’fileName’ has an incorrectformat.

Explanation: You entered the cicsmap command, butyou specified a file name with an incorrect suffix, orthe filename was too long or otherwise incorrectlyformed. Basic Mapping Support (BMS) file names musthave a .bms suffix and cicsmap defaults this for you ifyou specify a file name without a suffix.


User response: Retry the cicsmap command with avalid BMS file name.

Destination:

stderr

ERZ004078E • ERZ005004E


ERZ005005E Cannot open input file ’fileName’.Reason was: ’errorMessage’.

Explanation: CICS cannot open the specified file forreading.


User response: Retry the cicsmap command, using thecorrect file name.

Destination:

stderr

ERZ005006E Unsuccessful memory allocation. BasicMapping Support (BMS) maptranslation abnormally terminated.

Explanation: cicsmap has run out of memory.


User response: Try again when the system is lessbusy.

Destination:

stderr

ERZ005007E Unsuccessful attempt to set the locale.

Explanation: cicsmap cannot set the locale from theenvironment.


User response: The locale is taken from theenvironment of the user which called cicsmap. Thelocale categories within the locale can be modified by anumber of environment variables. Ensure that each ofthese environment variables specifies a valid locale andthen retry.

Destination:

stderr

ERZ005008E Unrecoverable syntax error on linelineNumber.

Explanation: cicsmap detected an unrecoverablesyntax error on the given line, when translating theBasic Mapping Support (BMS) map.


User response: Correct the syntax error, and retry thecicsmap command.

Destination:

stderr

ERZ005009E Cannot specify both -a and -s options.

Explanation: cicsmap has been invoked with mutuallyexclusive options.


User response: Retry the cicsmap command, using thecorrect option.

Destination:

stderr

ERZ005010E Cannot open output file ’fileName’.Reason was: ’errorMessage’.

Explanation: cicsmap cannot open the specified filefor writing.


User response: If the specified file exists, then removeit. If not, check that you have write permission in thecurrent directory.

Destination:

stderr

ERZ005011I Basic Mapping Support (BMS) maptranslation ended. errorCountd errors,warningCountd warnings.

Explanation: CICS detected the specified number oferrors and warnings during map translation.


User response: None

Destination:

stderr

ERZ005012E Physical or Logical map not generated.

Explanation: Some errors have been detected in yourBasic Mapping Support (BMS) map and so the physicalor logical map has not generated.


User response: Correct the errors and retry thecicsmap command.

Destination:

stderr

ERZ005013I Physical map generated to ’fileName’.

Explanation: cicsmap generated the physical mapwith the specified filename.


User response: None

ERZ005005E • ERZ005013I


Destination:

stderr

ERZ005014I Logical map generated to ’fileName’.

Explanation: cicsmap generated the logical map withthe specified file name.


User response: None

Destination:

stderr

ERZ005015E Cannot write to output file ’fileName’.Reason was: ’errorMessage’.

Explanation: cicsmap detected an error when writingto the specified file.


User response: The reason for the error is given.Correct the error and retry the cicsmap command.

Destination:

stderr

ERZ005016E DFHMDI parameters exceed physicalmap limits on line lineNumber.

Explanation: The map SIZE or number of fieldsexceeds the physical map limit.

System action: The cicsmap command continuesprocessing.

User response: Reduce the size of the map, and retrythe cicsmap command.

Destination:

stderr

ERZ005017W Field on line lineNumber overlapsanother field.

Explanation: A map field overlaps another field.

System action: The cicsmap command continuesprocessing.

User response: Reposition the field, and retry thecicsmap command.

Destination:

stderr

ERZ005019E Line lineNumber contains invalidcharacters for the current code set.

Explanation: The line contains illegal multibytesequences.

System action: cicsmap ignores the line and continuesprocessing.

User response: Correct the line, and retry the cicsmapcommand.

Destination:

stderr

ERZ005020E The ICTL directive is not valid on linelineNumber.

Explanation: The ICTL directive requires 1, 2, or 3comma separated numbers to set the start,continuation, and end columns.

System action: cicsmap ignores the ICTL directive andcontinues processing.

User response: Correct the ICTL directive, and retrythe cicsmap command.

Destination:

stderr

ERZ005021E Continuation not valid on linelineNumber. Line ignored.

Explanation: The continuation line did not containblanks between the start column and continuationcolumns, which are columns 1 and 16 unless they havebeen reset by the ICTL directive.


User response: Correct the continuation line, and retrythe cicsmap command.

Destination:

stderr

ERZ005022E Invalid character ’characterValue’ in labelon line lineNumber.

Explanation: Labels must begin with a letter andcontain only letters and digits.

System action: cicsmap ignores the label andcontinues processing.

User response: Correct the label, and retry thecicsmap command.

Destination:

stderr

ERZ005014I • ERZ005022E


ERZ005023W Field label ’labelValue’ too long on linelineNumber. Label truncated tocharacterCount characters.

Explanation: Basic Mapping Support (BMS) field orgroup labels must be less than thirty-one characterslong.

System action: cicsmap truncates the label andcontinues processing.


Destination:

stderr

ERZ005024W No macro found on line lineNumber.

Explanation: Each record must contain a BasicMapping Support (BMS) macro, optionally preceded bya label.


User response: Correct the line, and retry the cicsmapcommand.

Destination:

stderr

ERZ005025W Unknown operation code ’opCode’ online lineNumber. Line ignored.

Explanation: cicsmap detected an invalid operationcode on the given line. The only valid operation codesare: TITLE, DFHMSD, DFHMDI, DFHMDF, and END.


User response: Correct the operation code, and retrythe cicsmap command.

Destination:

stderr

ERZ005026E Invalid character ’characterValue’ on linelineNumber.

Explanation: cicsmap detected an invalid character onthe given line. The only valid characters outside stringsare letters, digits, =, ,, (, and ).


User response: Correct the invalid character, and retrythe cicsmap command.

Destination:

stderr

ERZ005027E No closing quote in string on linelineNumber.

Explanation: The closing quote for a string must occurbefore the end of the record.


User response: Add a closing quote to the string, andretry the cicsmap command.

Destination:

stderr

ERZ005028W Invalid single in string on linelineNumber.

Explanation: Use to get a single in a string.

System action: cicsmap accepts the ampersand andcontinues processing.

User response: Although cicsmap handles the singleampersand, the ampersands should be doubled up toproduce a map which can be ported to other CICSsystems.

Destination:

stderr

ERZ005029E String is too long on line lineNumber.

Explanation: A token which is too long has beenfound. This is probably be an INITIAL string thatcontains more characters than are permitted.


User response: Check the length of all strings in thebms map and retry the cicsmap command.

Destination:

stderr

ERZ005030E = expected after ’operandValue’ on linelineNumber.

Explanation: cicsmap detected an operand that is notfollowed by an = character. The operand must befollowed by =.

System action: cicsmap ignores the operand andcontinues processing.

User response: Add an = after the operand, and retrythe cicsmap command.

Destination:

stderr

ERZ005023W • ERZ005030E


ERZ005031E Comma expected after ’operandValue’ online lineNumber.

Explanation: cicsmap detected an operand that is notfollowed by a comma. The operand must be followedby a comma.


User response: Add a comma after the operand, andretry the cicsmap command.

Destination:

stderr

ERZ005032E Missing ) after ’operandValue’ on linelineNumber.

Explanation: cicsmap detected that there is nomatching ) for a list operand that started with (.


User response: Add a ) after the operand, and retrythe cicsmap command.

Destination:

stderr

ERZ005033E DFHMSD operand ’operandValue’ is notvalid on line lineNumber.

Explanation: The specified operand on the given lineis not valid for the DFHMSD macro.


User response: Correct the operand, and retry thecicsmap command.

Destination:

stderr

ERZ005034E DFHMDI operand ’operandValue’ is notvalid on line lineNumber.

Explanation: The specified operand on the given lineis not valid for the DFHMDI macro.



Destination:

stderr

ERZ005035E DFHMDF operand ’operandValue’ is notvalid on line lineNumber.

Explanation: The specified operand on the given lineis not valid for the DFHMDF macro.



Destination:

stderr

ERZ005036E DFHMSD macro missing on linelineNumber.

Explanation: cicsmap expected to find a DFHMSDmacro on the given line, but could not find one.

System action: cicsmap terminates.

User response: Add a DFHMSD macro and retry thecicsmap command.

Destination:

stderr

ERZ005037E DFHMDI macro missing on linelineNumber.

Explanation: cicsmap expected to find a DFHMDImacro on the given line, but could not find one.


User response: Add a DFHMDI macro, and retry thecicsmap command.

Destination:

stderr

ERZ005038W Unrecognized data after mapsetdefinition on line lineNumber.

Explanation: cicsmap could not recognize the dataafter the mapset definition.


User response: Correct the data, and retry the cicsmapcommand.

Destination:

stderr

ERZ005039W DFHMSD TYPE=FINAL missing on linelineNumber.

Explanation: cicsmap expected to find a DFHMSDTYPE=FINAL statement on the given line, but wasunable to find one.

ERZ005031E • ERZ005039W



User response: Add a DFHMSD TYPE=FINALstatement, and retry the cicsmap command.

Destination:

stderr

ERZ005040E Invalid number ’number’ in operandValueoperand on line lineNumber.

Explanation: cicsmap detected a number containing anon-numeric value.

System action: cicsmap ignores the operand, andcontinues processing.

User response: Correct the number, and retry thecicsmap command.

Destination:

stderr

ERZ005041E Invalid name ’name’ in ’operandValue’operand on line lineNumber.

Explanation: cicsmap detected a name containing anumeric first character on the specified line. Namesmust begin with a letter.


User response: Correct the name, and retry thecicsmap command.

Destination:

stderr

ERZ005044E ATTRB parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after ATTRB= isnot valid.

System action: cicsmap ignores the parameter, andcontinues processing.

User response: Correct the parameter, and retry thecicsmap command.

Destination:

stderr

ERZ005045E BASE parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after BASE= isnot valid.



Destination:

stderr

ERZ005046E CASE parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after CASE= isnot valid.



Destination:

stderr

ERZ005047E COLOR parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after COLOR=is not valid.



Destination:

stderr

ERZ005048E COLUMN parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter afterCOLUMN= is not valid.



Destination:

stderr

ERZ005049E CTRL parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after CTRL= isnot valid.



Destination:

ERZ005040E • ERZ005049E


stderr

ERZ005050E DSATTS or MAPATTS parameter’parameterValue’ on line lineNumber is notvalid.

Explanation: The specified parameter after DSATTS=or MAPATTS= is not valid.



Destination:

stderr

ERZ005051E EXTATT parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after EXTATT=is not valid.



Destination:

stderr

ERZ005052E FIELDS parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after FIELDS= isnot valid.



Destination:

stderr

ERZ005053E GRPNAME parameter ’parameterValue’on line lineNumber is not valid.

Explanation: The specified parameter afterGRPNAME= is not valid.



Destination:

stderr

ERZ005054E HILIGHT parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after HILIGHT=is not valid.



Destination:

stderr

ERZ005055E INITIAL, GINIT, or XINIT parameter’parameterValue’ on line lineNumber is notvalid.

Explanation: The specified parameter after INITIAL=,GINIT=, or XINIT= is not valid.



Destination:

stderr

ERZ005056E DFHMDF JUSTIFY parameter’parameterValue’ on line lineNumber is notvalid.

Explanation: The specified parameter appearing afterJUSTIFY= is not valid.



Destination:

stderr

ERZ005057E DFHMDI JUSTIFY parameter’parameterValue’ on line lineNumber is notvalid.

Explanation: The specified parameter after JUSTIFY=is not valid.



Destination:

stderr

ERZ005050E • ERZ005057E


ERZ005058E LANG parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after LANG= isnot valid.



Destination:

stderr

ERZ005059E LENGTH parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after LENGTH=is not valid.



Destination:

stderr

ERZ005060E LINE parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after LINE= isnot valid.



Destination:

stderr

ERZ005061E MODE parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after MODE= isnot valid.



Destination:

stderr

ERZ005062E OCCURS parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after OCCURS=is not valid.



Destination:

stderr

ERZ005063E OUTLINE parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after OUTLINE=is not valid.



Destination:

stderr

ERZ005064E PICIN or PICOUT parameter’parameterValue’ on line lineNumber is notvalid.

Explanation: The specified parameter after PICIN= orPICOUT= is not valid.



Destination:

stderr

ERZ005065E POS parameter on line lineNumber is notvalid.

Explanation: The specified parameter after POS= isnot valid.



Destination:

stderr

ERZ005058E • ERZ005065E


ERZ005066E PS parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after PS= is notvalid.



Destination:

stderr

ERZ005067E SIZE parameter on line lineNumber is notvalid.

Explanation: The specified parameter after SIZE= isnot valid.



Destination:

stderr

ERZ005068E SOSI parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after SOSI= isnot valid.



Destination:

stderr

ERZ005069E STORAGE parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter afterSTORAGE= is not valid.



Destination:

stderr

ERZ005070E SUFFIX parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after SUFFIX= isnot valid.



Destination:

stderr

ERZ005071E TERM parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after TERM= isnot valid.



Destination:

stderr

ERZ005072E TIOAPFX parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after TIOAPFX=is not valid.



Destination:

stderr

ERZ005073E TRANSP parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after TRANSP=is not valid.



Destination:

stderr

ERZ005066E • ERZ005073E


ERZ005074E TYPE parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after TYPE= isnot valid.



Destination:

stderr

ERZ005075E VALIDN parameter ’parameterValue’ online lineNumber is not valid.

Explanation: The specified parameter after VALIDN=is not valid.



Destination:

stderr

ERZ005076W SUFFIX parameter ’parameterValue’ online lineNumber is non numeric.

Explanation: The specified parameter after SUFFIX= isnot numeric.

System action: cicsmap accepts the parameter, andcontinues processing.

User response: Use of a non-numeric parameter canconflict with suffixes generated automatically by theTERM option. To avoid any possibility of conflict, use anumeric suffix, and retry the cicsmap command.

Destination:

stderr

ERZ005077W SUFFIX parameter ’parameterValue’ online lineNumber has been truncated.

Explanation: The specified parameter after SUFFIX= ismore than one-character long.

System action: cicsmap truncates the parameter toone character and continues processing.

User response: Change the SUFFIX parameter to asingle character to avoid this message.

Destination:

stderr

ERZ005078W Label ’labelValue’ too long on linelineNumber. Label truncated tocharacterCount characters.

Explanation: Basic Mapping Support (BMS) labelsmust be less than eight characters long.

System action: cicsmap truncates the label andcontinues processing.


Destination:

stderr

ERZ005079E DATA parameter ’parameterValue’ on linelineNumber is not valid.

Explanation: The specified parameter after DATA= isnot valid.



Destination:

stderr

ERZ005080W ’parameterName’ parameter’parameterValue’ on line lineNumber isduplicated.

Explanation: The specified list operand contains aduplicate parameter; for example,ATTRB=(PROT,IC,PROT).


User response: Remove the duplicate parameter, andretry the cicsmap command.

Destination:

stderr

ERZ005081W ’parameterName’ parameters’parameterValue1’ and ’parameterValue2’ online lineNumber cannot be used together.

Explanation: The specified parameters for the givenoperand are mutually exclusive.


User response: Remove one parameter, and retry thecicsmap command.

Destination:

stderr

ERZ005074E • ERZ005081W


ERZ005082W ’optionName’ option on line lineNumberalready specified.

Explanation: The specified option has already beengiven.

System action: cicsmap ignores the duplicate option,and continues processing.

User response: Remove the duplicate option, andretry the cicsmap command.

Destination:

stderr

ERZ005090E DFHMSD or DFHMDI macro on linelineNumber must be labelled.

Explanation: DFHMSD and DFHMDI macros must belabelled.

System action: cicsmap continues processing.

User response: Add a label, and retry the cicsmapcommand.

Destination:

stderr

ERZ005091E Label ’labelValue’ is duplicated on linelineNumber.

Explanation: The specified label already exists.


User response: Change the label, and retry thecicsmap command.

Destination:

stderr

ERZ005093W BASE and STORAGE operands on linelineNumber cannot be used together.

Explanation: The BASE and STORAGE operands aremutually exclusive.

System action: cicsmap uses the first operandspecified, and continues processing.

User response: Remove either the BASE or STORAGEoperand, and retry the cicsmap command.

Destination:

stderr

ERZ005094W SUFFIX operand on line lineNumberoverridden by TERM option.

Explanation: The TERM and SUFFIX operands aremutually exclusive.

System action: cicsmap uses the TERM operand,

ignores the SUFFIX operand, and continues processing.

User response: Remove either the TERM or SUFFIXoperand, and retry the cicsmap command.

Destination:

stderr

ERZ005095W GRPNAME and OCCURS operands online lineNumber cannot be used together.

Explanation: The GRPNAME and OCCURS operandsare mutually exclusive.


User response: Remove either the GRPNAME orOCCURS operand, and retry the cicsmap command.

Destination:

stderr

ERZ005097W PICIN or PICOUT on line lineNumbercan only be used with LANG=COBOLor LANG=PLI.

Explanation: The PICIN and PICOUT operands areonly valid for LANG=COBOL or LANG=PLI.

System action: cicsmap ignores the PICIN or PICOUToperand, and continues processing.

User response: Remove the PICIN or PICOUToperand, or set LANG=COBOL or LANG=PLI, andretry the cicsmap command.

Destination:

stderr

ERZ005098W INITIAL, GINIT, and XINIT operandson line lineNumber cannot be usedtogether.

Explanation: The INITIAL, GINIT, and XINITparameters are mutually exclusive.


User response: Remove either the INITIAL, GINIT, orXINIT operand, and retry the cicsmap command.

Destination:

stderr

ERZ005100W TIOAPFX=YES must be specified online lineNumber.

Explanation: CICS on Open Systems and CICS forWindows NT require that TIOAPFX=YES is alwaysspecified.


ERZ005082W • ERZ005100W


User response: Add TIOAPFX=YES, and retry thecicsmap command.

Destination:

stderr

ERZ005102W Extended attribute ’attributeName’ is notspecified in MAPATTS on linelineNumber.

Explanation: Extended attributes specified inDFHMDF macros must be specified in MAPATTS,implied by EXTATT or by specifying extended attributein the DFHMSD or DFHMDI macro.


User response: Add an extended attribute toMAPATTS, and retry the cicsmap command.

Destination:

stderr

ERZ005103W DSATTS parameter ’parameterName’ isnot specified in MAPATTS on linelineNumber - ’parameterName’ ignored.

Explanation: All DSATTS parameters must bespecified in MAPATTS or implied by specifying theextended attribute in the DFHMSD or DFHMDI macro.


User response: Add the DSATTS parameter toMAPATTS, and retry the cicsmap command.

Destination:

stderr

ERZ005110E SIZE operand must be specified on linelineNumber.

Explanation: SIZE defaults to (0,0) which is invalid, soyou must specify SIZE.


User response: Add a SIZE operand, and retry thecicsmap command.

Destination:

stderr

ERZ005111E SIZE parameter is out of range on linelineNumber.

Explanation: The minimum map size is (1,1) and themaximum map size is (240, 240). The specified mapsize is outside this range.


User response: Retry with values for rows and

columns in the range 1 to 240 and retry the cicsmapcommand.

Destination:

stderr

ERZ005112W The total number of fields in the mapexceeds 1023 on line lineNumber.

Explanation: The maximum number of fields in a mapis 1023. The map contains more than 1023 fields.


User response: Reduce the number of fields on themap, and retry the cicsmap command.

Destination:

stderr

ERZ005113W The total length of initial data in themap exceeds 2560 characters on linelineNumber.

Explanation: The maximum total length of all initialdata in a map is 2560 bytes. The number of charactersin the map exceeds this maximum.


User response: Reduce the amount of initial data onthe map, and retry the cicsmap command.

Destination:

stderr

ERZ005114E The ’parameterName’ parameter is out ofrange on line lineNumber.

Explanation: The value of the LINE or COLUMNparameter must be in the range 1 to 240 (inclusive).The actual value is outside this range.


User response: Change the value of the specifiedparameter, and retry the cicsmap command.

Destination:

stderr

ERZ005120E POS operand must be specified on linelineNumber.

Explanation: POS defaults to (0, 0) which is invalid.Therefore, you must specify POS.


User response: Add the POS operand, and retry thecicsmap command.

Destination:

stderr

ERZ005102W • ERZ005120E


ERZ005121E POS operand is outside map boundaryon line lineNumber.

Explanation: POS must specify a position within thespecified map SIZE. The current value is outside themap boundary.


User response: Correct the POS or SIZE operand, andretry the cicsmap command.

Destination:

stderr

ERZ005122E LENGTH zero or not specified on linelineNumber.

Explanation: The default LENGTH is 0, which isinvalid. Therefore, you must specify LENGTH.


User response: Add a LENGTH operand, and retrythe cicsmap command.

Destination:

stderr

ERZ005123E Field exceeds map boundary on linelineNumber.

Explanation: The end of a field is outside the map.


User response: Correct the POS, SIZE or LENGTHoperand, and retry the cicsmap command.

Destination:

stderr

ERZ005124W INITIAL data exceeds field length online lineNumber. The data is truncated.

Explanation: The length of INITIAL, GINIT, or XINITdata exceeds the field length specified by LENGTH. Forunnamed fields which contain MBCS characters, theinitial data is truncated only if the display width ofMBCS characters (regardless the number of bytes percharacter) exceeds the LENGTH value.


User response: Correct the value of the LENGTH,INITIAL, GINIT, or XINIT operand, and retry thecicsmap command.

Destination:

stderr

ERZ005125E XINIT contains invalid or odd numberof hexadecimal characters on linelineNumber.

Explanation: XINIT must contain an even number ofhexadecimal characters. Valid hexadecimal charactersare 0-9 and A-F.


User response: Correct the value of the XINIToperand, and retry the cicsmap command.

Destination:

stderr

ERZ005126E XINIT parameter specifies invalidcharacters for the current codeset.

Explanation: The Multi Byte Character Set (MBCS)string formed from the XINIT operand is not valid.


User response: Correct the value of the XINIToperand, and check whether you need to run thecicsmap -e command.

Destination:

stderr

ERZ005127E GRPNAME operand specified onunnamed field on line lineNumber.

Explanation: Fields defined with the GRPNAMEoperand must be labelled.


User response: Add a label, and retry the cicsmapcommand.

Destination:

stderr

ERZ005128E OCCURS operand operandName on linelineNumber less than 1 or greater than1023.

Explanation: The value of the OCCURS parameter isout of range.


User response: Correct the OCCURS operand, andretry the cicsmap command.

Destination:

stderr

ERZ005121E • ERZ005128E


ERZ005129E PICTURE character ’characterValue’ online lineNumber is not valid.

Explanation: The valid PICTURE characters are: A B EP S V X Z 9 0 / , . + - $ ( ) CR DB for COBOL and A BE F G H I K M P R S T V X Y Z 1 2 3 6 7 8 9 / , . + - *$ ( ) CR DB for PL/I.


User response: Correct the PICIN or PICOUToperand, and retry the cicsmap command.

Destination:

stderr

ERZ005130W Field exceeds line boundary on linelineNumber.

Explanation: The end of a field exceeds line boundaryon the same line.


User response: Correct the POS or LENGTH operand,and retry the cicsmap command.

Destination:

stderr

ERZ005131W ’operandName’ operand on linelineNumber is not supported.

Explanation: CICS on Open Systems and CICS forWindows NT do not support the TRANSP operand.


User response: Remove the unsupported operand,and retry the cicsmap command.

Destination:

stderr

ERZ005132W DSATTS or MAPATTS operand’operandName’ on line lineNumber is notsupported.

Explanation: CICS on Open Systems and CICS forWindows NT do not support the operand.


User response: Remove the unsupported operand,and retry the cicsmap command.

Destination:

stderr

ERZ005133E Field in group ’groupName’ on linelineNumber is not consecutive.

Explanation: Fields in a group must be consecutiveentries in a map definition.


User response: Make all fields in a group consecutive,and retry the cicsmap command.

Destination:

stderr

ERZ005134E Field in group ’groupName’ on linelineNumber is not in ascending order.

Explanation: Fields in a group must be defined inascending order of screen position.


User response: Reorder the group elements in themap so that they are in ascending order, and retry thecicsmap command.

Destination:

stderr

ERZ005135E The length of the field on linelineNumber exceeds the maximum of 256.

Explanation: The length of the field exceeds theallowed maximum of 256 bytes.


User response: Check the LENGTH and any PICIN orPICOUT operands and ensure that the length of thefield is no more than 256 bytes long. Then retry thecicsmap command.

Destination:

stderr

ERZ005136W The ATTRB option on line lineNumberhas been ignored.

Explanation: The ATTRB option can be specified onlyon the first field in a group.


User response: Remove the ATTRB operand, and retrythe cicsmap command.

Destination:

stderr

ERZ005129E • ERZ005136W


ERZ005137E The lengths of the PICIN and PICOUTvalues on line lineNumber do not match.

Explanation: The lengths of the values of the PICINand PICOUT operands differ.


User response: Check the values of the PICIN andPICOUT operands and make them the same length.Retry the cicsmap command.

Destination:

stderr

ERZ005138E The LENGTH option on line lineNumberdoes not match the length of thePICIN/PICOUT value.

Explanation: The value supplied in the LENGTHoperand differs from the length of the value of thePICIN or PICOUT operand for this field.


User response: Amend either the LENGTH or thepicture operands, and retry the cicsmap command.

Destination:

stderr

ERZ005139W The DET attribute on line lineNumber isnot supported.

Explanation: CICS on Open Systems and CICS forWindows NT do not support the detectable (DET)attribute.


User response: Remove the DET attribute, and retrythe cicsmap command.

Destination:

stderr

ERZ005140E FOLD parameter on line lineNumber isinvalid.

Explanation: An invalid value has been specified forthe FOLD operand.


User response: Correct the value to the operand andretry the cicsmap command.

Destination:

stderr

ERZ005141W FOLD operand on line lineNumber mayonly be specified on C maps.

Explanation: FOLD is only valid in DFHMDI macroswith LANG=C.


User response: Remove the FOLD operand and retrythe cicsmap command.

Destination:

stderr

ERZ005142W The FIELDS=NO option on linelineNumber is not supported.

Explanation: CICS on Open Systems and CICS forWindows NT do not support the FIELDS=NO option.


User response: Remove the FIELDS=NO operand andretry the cicsmap command.

Destination:

stderr

ERZ005143W No fields have been specified for themap on line lineNumber.

Explanation: The map is not followed by anyDFHMDF lines specifying FIELDS.


User response: Add some fields to the map and retrythe cicsmap command.

Destination:

stderr

ERZ005144W The DATA=BLOCK option on linelineNumber is not supported.

Explanation: CICS on Open Systems and CICS forWindows NT do not support the DATA=BLOCKoption.


User response: Remove the DATA=BLOCK operandor specify DATA=FIELD and retry the cicsmapcommand.

Destination:

stderr

ERZ005145W No length specified on lineTobedetermined. Length Tobedeterminedassumed.

Destination:

ERZ005137E • ERZ005145W


ERZ005146E The LENGTH option on lineTobedetermined should be equal or greaterthan the length of the PICIN/PICOUTvalue.

Explanation:

System action:

User response:

Destination:

ERZ006001E The specified message catalog ’fileName’cannot be opened

Explanation: The specified message catalog ’fileName’cannot be opened.

System action: cicssda exits.

User response: Check access permissions to themessage catalog.

Destination:

stderr

ERZ006002E cicssda cannot find message numbermessageNumber in set catalogNumber

Explanation: This message is issued when message’messageNumber’ cannot be found.

System action: None

User response: Investigate contents of messagecatalog.

Destination:

Any dialog for which a text string cannot be found.

ERZ006004E Unsuccessful paste operation; illegalpaste position.

Explanation: Generated from the Paste, Move andReplicate options on the Edit menu, when the chosenposition causes the new fields to overlap existing fieldsor interrupt a field group, or causes a pasted group toinclude non-group fields.

System action: cicssda does not perform the Paste,Move or Replicate action.

User response: Repeat the operation at anotherposition.

Destination:

Error panel dialog

ERZ006005E Unsuccessful paste of group name’groupName’; duplicate field name’fieldName’.

Explanation: Generated from the Paste option of the

Edit menu when pasting a group causes duplicate fieldname(s) in the current map.

System action: cicssda does not perform the Pasteaction.

User response: Paste group into new, empty map;change field name(s) and remove the group name; cutor copy group to clipboard and attempt to paste it intooriginal map again.

Destination:

Error panel dialog

ERZ006006E Unsuccessful paste operation; duplicategroup name ’groupName’.

Explanation: Generated from the Paste option of theEdit menu when pasting a group causes a duplicategroup name in the current map.

System action: cicssda does not perform the Pasteaction.

User response: Paste group into new, empty map;change group name; cut or copy group to clipboardand attempt to paste it into original map again.

Destination:

Error panel dialog

ERZ006007E Unable to apply group name’groupName’; some selected fields areunnamed.

Explanation: Generated from the field details dialogwhen applying a group name to selected fields, andsome of the fields are unnamed.

System action: cicssda does not perform the Applyaction.

User response: Set field names before grouping fields.

Destination:

Error panel dialog

ERZ006008E Unable to apply group name’groupName’; selected fields are notcontiguous.

Explanation: Generated from the field details dialogwhen applying a group name to selected fields, and thefields are not contiguous.


User response: Select contiguous fields.

Destination:

Error panel dialog

ERZ005146E • ERZ006008E


ERZ006009E You cannot remove field name’fieldName’; field belongs to group’groupName’.

Explanation: Generated from the field details dialogwhen applying a null field name to a field whichbelongs to a group.


User response: Ungroup fields before removing fieldnames.

Destination:

Error panel dialog

ERZ006010E Unable to apply field name ’fieldName’;duplicate field name.

Explanation: Generated from the field details dialogswhen applying a field name which is not unique withinthe current map.


User response: Choose another name.

Destination:

Error panel dialog

ERZ006011E Unable to ungroup fields; insufficientspace for attribute bytes.

Explanation: Generated from the field details dialogwhen applying a null group name to a group, andungrouping cannot be accomplished because theaddition of attribute bytes to the second andsubsequent members of the group causes theungrouped fields to overlap.


User response: Move group fields apart beforeungrouping.

Destination:

Error panel dialog

ERZ006012E Unable to change field type to INPUT;insufficient space for stopper field.

Explanation: Generated from the field details dialogwhen applying field type INPUT to field which doesnot have enough space at the end to add thetwo-character stopper.


User response: Make room for the two-characterstopper before changing field type to INPUT.

Destination:

Error panel dialog

ERZ006013E Unable to apply group name’groupName’; duplicate group name.

Explanation: Generated from the field details dialogwhen applying a group name which is duplicated inthe unselected fields in the current map.


User response: Choose another group name.

Destination:

Error panel dialog

ERZ006014E Unable to apply panel name ’panelName’;duplicate panel name.

Explanation: Generated from the panel name entrydialog (via the view menu) or the panel details dialogafter an attempt to enter a panel name which is thesame as another panel name in the panel group.

System action: cicssda forces entry of unique panelname or cancels the Apply action.

User response: Choose another group name.

Destination:

Panel name entry dialog

ERZ006015E Unsuccessful open of file ’fileName’;reason is ’reasonString’.

Explanation: Generated from the file open dialog (orcommand line parameter) when opening a file. The filewas unable to be opened for the reason specified in themessage.

System action: cicssda does not open the file.

User response: Check the reason why the file wasunable to be opened and fix the problem appropriately.

Destination:

Error panel dialog

ERZ006016E Unsuccessful close of file ’fileName’

Explanation: Generated from the file save dialogwhen saving BMS file (or from file open dialog whenclosing BMS file).

System action: cicssda does not perform the Closeaction.

User response: Check file access permissions.

Destination:

Error panel dialog

ERZ006009E • ERZ006016E


ERZ006017E Invalid panel dimensions: rows x columnsmust both be in the range 1 to 240.

Explanation: You have specified an invalid value forthe rows or columns of the panel. The minimum panelsize is 1 x 1 and the maximum panel size is 240 x 240.

System action: The panel size is not changed.

User response: Retry with values for rows andcolumns in the range 1 to 240.

Destination:

Error panel dialog

ERZ006018E ’fileName’ is not a regular file

Explanation: The given name is not a regular file andcannot be opened for reading.

System action: cicssda does not perform the openaction.

User response: Select a regular file to open.

Destination:

Error panel dialog.

ERZ006019E No unprotected or input fields in panel

Explanation: Cannot tab around panel in test modewith no data entry fields.

System action: cicssda does not perform the tabaction.

User response: Define some unprotected or inputfields.

Destination:

Error Panel dialog

ERZ006020E You cannot enter non-numeric data innumeric field

Explanation: You cannot enter non-numeric data innumeric field.


User response: Either enter numeric data, or removeNUM attribute from the field.

Destination:

Error Panel dialog

ERZ006021E Unable to print to file; enter destinationfile for printing

Explanation: You have selected Print to file withoutspecifying a file name.

System action: cicssda does not perform the Printoperation.

User response: Enter a valid file name in print dialog.

Destination:

Error Panel dialog

ERZ006022E Unable to apply PICTURE string’pictureString’; character ’characterValue’ isnot valid

Explanation: Generated from the field details dialogwhen applying a PICTURE string that contains aninvalid character.


User response: Correct the PICIN or PICOUT string,and re-select apply button.

Destination:

Error Panel dialog

ERZ006023E PICTURE string ’pictureString’ does notmatch field length fieldLength

Explanation: Generated from the field details dialogwhen applying a PICTURE string that does not matchthe field length.


User response: Correct the PICIN or PICOUT string,and re-select apply button.

Destination:

Error panel dialog

ERZ006024E Unable to apply OCCURS andGRPNAME to same field

Explanation: Generated from the field details dialog,cannot specify OCCURS and GRPNAME for the samefield.


User response: Set Occurs or Group Name (not both)and repeat the apply action.

Destination:

Error panel dialog

ERZ006025E Panel size cannot be reduced to rows xcolumns; some fields would be outsidepanel.

Explanation: Generated from the panel details dialogwhen applying a reduction in panel size to less thanthe rectangle that encloses all existing fields.

ERZ006017E • ERZ006025E



User response: Delete fields or retry with larger valuefor rows or columns.

Destination:

Error panel dialog

ERZ006026E ’fileName’ is a subdirectory; please selecta file.

Explanation: You have attempted to ’open’ asubdirectory instead of a BMS source file.

System action: cicssda does not perform the Openaction.

User response: Retry with a BMS source file.

Destination:

Error panel dialog

ERZ006027E Unable to generate file ’fileName’; unableto execute ’commandString’.

Explanation: Generated from the Generate Mapdialog, the CICS executable cicsmap was unable to bestarted.

System action: cicssda does not perform the Generateaction.

User response: Make sure that the system executablecicsmap is in a directory specified in the environmentvariable PATH and has correct access permissions.

Destination:

Error panel dialog

ERZ006028W Unsuccessful open of default BMS file’fileName’

Explanation: cicssda was unable to open default BMSsource file.

System action: cicssda does not open the default BMSsource file; defaults for panel group, panel and fielddetails are used instead.

User response: Make sure that the default BMS filespecified in .Xdefaults.defaultBMS file exists and hascorrect permissions.

Destination:

stderr

ERZ006029E You cannot set field type INPUT togroup fields

Explanation: You attempted to apply field typeINPUT to group fields but members of a group cannotbe input fields.


User response: Either ungroup fields or set field typeto AUTOSKIP, UNPROTECTED, or PROTECTED.

Destination:

Error panel dialog

ERZ006030E cicssda cannot create font set’baseFontNameList’

Explanation: cicssda is unable to create a font set,bound to the current locale, from the specifiedbaseFontNameList. The missing character sets arereported in subsequent ERZ0632I messages.

System action: cicssda terminates.

User response: Check why the character sets listed insubsequent ERZ0632I messages are missing (check fontpath) or specify a font set appropriate to your localevia the -fn fontName command-line argument.

Destination:

stderr

ERZ006031W Some character sets are missing for fontset ’baseFontNameList’

Explanation: Some of the character sets needed by thespecified font set are missing. The missing charactersets are reported in subsequent ERZ0632I messages.

System action: cicssda continues, but characters thatrequire any of the missing character sets are displayedas a default character (typically the space character).

User response: Check why the character sets listed insubsequent ERZ0632I messages are missing (check fontpath) or specify a font set appropriate to your localevia the -fn font command-line argument.

Destination:

stderr

ERZ006032I Missing character set: ’characterSet’

Explanation: The specified character set required bythe font set was not found.

System action: cicssda terminates or continues,depending on whether the previous message wasERZ0630E or ERZ0631W.

User response: See ERZ0630E or ERZ0631W.

Destination:

stderr

ERZ006026E • ERZ006032I


ERZ006033E Font set ’fontSet’ contains avariable-width font ’fontName’

Explanation: cicssda requires fixed-width fonts. Thespecified font within the specified font set is notfixed-width.


User response: Check that the font set specified on thecommand line or in the resource file contains onlyfixed-width fonts.

Destination:

stderr

ERZ006034E cicssda cannot open X11 Input Method

Explanation: cicssda cannot open an X11 InputMethod to handle input in the current locale.


User response: Check that the X11 input method isinstalled for the current locale.

Destination:

stderr

ERZ006035E cicssda does not have a common inputstyle for locale

Explanation: cicssda does not support any of the X11input method’s input styles. At least one common inputstyle must be supported by cicssda and the inputmethod for the locale.


User response: Try setting the environment variable$XMODIFIERS to use a different input method for thelocale.

Destination:

stderr

ERZ006036E cicssda cannot create an X11 InputContext

Explanation: cicssda cannot create an X11 InputContext for the input method.


User response: Try setting the environment variable$XMODIFIERS to use a different input method for thelocale.

Destination:

stderr

ERZ006037E cicssda cannot convert field at row ’row’column ’column’ to PS=8

Explanation: cicssda cannot convert the specified fieldto PS=8 because it contains single-width characters.

System action: cicssda does not apply PS=8 to thespecified field.

User response: Delete all single-width characters fromthe field and try again.

Destination:

stderr

ERZ006038W Initial value on line ’lineNumber’inconsistent with PS=8

Explanation: The specified initial value containssingle-width characters, which are not allowed in PS=8fields.

System action: cicssda changes the field to SOSI=YES,which allows mixed single and double widthcharacters.

User response: None

Destination:

stderr

ERZ006039W Width of Initial value on line’lineNumber’ exceeds LENGTH

Explanation: When the specified initial value isexpanded to account for SO/SI taking position, thedisplay width of the field exceeds LENGTH.

System action: cicssda increases LENGTH.

User response: None

Destination:

stderr

ERZ006040W LENGTH of PS=8 field on line’lineNumber’ is not even

Explanation: PS=8 fields can only containdouble-width characters, so their LENGTH mustalways be even.

System action: cicssda decreases LENGTH to make iteven.

User response: None

Destination:

stderr

ERZ006033E • ERZ006040W


ERZ006041W cicssda cannot determine the wide spacecharacter for the locale

Explanation: In multi-byte locales, cicssda needs touse wide spaces to pad PS=8 fields. cicssda cannotdetermine the appropriate wide space character for thelocale.

System action: cicssda continues, although PS=8 fieldsare possibly not handled properly.

User response: Exit cicssda and specify the widespace as the value of the resource Cicssda.WideSpace inyour .Xdefaults file.

Destination:

stderr

ERZ006042E Unable to apply name ’name’; it hasalready been specified.

Explanation: You cannot enter a name which hasalready been defined as a field name or panel name inthe panel group.


User response: Choose another name.

Destination:

Error panel dialog

ERZ006043E The ’parameter’ parameter is out of range

Explanation: You have specified an invalid value forLINE or COLUMN. The minimum size is 1 and themaximum size is 240.


User response: Retry with values for LINE andCOLUMN in the range 1 to 240.

Destination:

Error panel dialog

ERZ006044E Value for the OCCURS parameter mustbe in the range 1 to 1023.

Explanation: The value of the OCCURS parameter isout of range.


User response: Retry with value for OCCURS in therange 1 to 1023.

Destination:

Error panel dialog

ERZ006098E No online help facility is available

Explanation: You have requested help, but cicssda isunable to display help by using InfoExplorer.

System action: No help information is displayed.

User response: cicssda requires InfoExplorer todisplay the help information, so check that InfoExploreris available on your machine.

Destination:

Error panel dialog

ERZ006099E Usage: cicssda optionString fileName

Explanation: You entered the cicssda commandincorrectly.

System action: The cicssda command terminates.

User response: Enter the cicssda command using thecorrect syntax, as shown in the message.

Destination:

stderr

ERZ007001E The Interval Control Element (ICE)queue is inconsistent: queue head(address address) has a previous ICE(address address)

Explanation: The CICS self-consistency checkingmechanism detected an error in the ICE queue.


User response: Because the Interval Control datastructures are held in the Region Pool it is unlikely thatthe invalid data has been produced by applicationcode. Save any dump file produced for use by yoursupport organization. If the problem persists, contactyour support organization.

Destination:

console.msg

ERZ007002E CICS cannot register Lock upcallsroutine

Explanation: CICS made an unsuccessful attempt toregister an internal function, and therefore CICS didnot register the internal prepare and abort functions.


User response: Resubmit the transaction. If theproblem persists, CICS possibly ran out of memory.This is possibly due to a transaction that is looping insome way that causes CICS to acquire substantialamounts of Region Pool memory on its behalf. Checkthat the value of the MaxRegionPool attribute in the

ERZ006041W • ERZ007002E


Region Definition is sufficiently large. Perform animmediate shutdown of the region, increase the value,and restart the region.

Destination:

CSMT

ERZ007003E Transaction ’transId’ could not betriggered because it does not exist,during a write operation to TransientData (TD) queue ’TDQname’

Explanation: The specified trigger transaction forTransient Data (TD) queue ’TDQname’ was not able tobe started because no definition for it exists in theTransaction Definitions.


User response: See the following messages for furtherdetails.

Destination:

CSMT

ERZ007004E CICS could not access the regiondatabase

Explanation: CICS has made an unsuccessful attemptto access the region database.


User response: Resubmit the transaction. If theproblem persists, CICS possibly ran out of memory.This is possibly due to a transaction that is looping insome way that causes CICS to acquire substantialamounts of Region Pool memory on its behalf. Checkthat the value of the MaxRegionPool attribute in theRegion Definition is sufficiently large. Perform animmediate shutdown of the region, increase the value,and restart the region.

Destination:

CSMT

ERZ007005E CICS cannot obtain memory to create anInterval Control Element (ICE)

Explanation: CICS made an unsuccessful attempt tocreate an ICE, due to a memory allocation problem.


User response: Resubmit the transaction. If theproblem persists, CICS possibly ran out of memory.This is possibly due to a transaction that is looping insome way that causes CICS to acquire substantialamounts of Region Pool memory on its behalf. Checkthat the value of the MaxRegionPool attribute in the

Region Definition is sufficiently large. Perform animmediate shutdown of the region, increase the value,and restart the region.

Destination:

CSMT

ERZ007006E CICS is unable to delete an item fromthe Locked Resource list

Explanation: Because of an internal problem, CICSwas not able to delete the details of the locked resourcefrom the list of all locked resources.


User response: Resubmit the transaction. If theproblem persists, and you want to investigate it, checkthat the next CICS self-consistency check of the regionis successful. If this indicates a problem, take a systemdump and contact your support organization.

Destination:

CSMT

ERZ007007E CICS is unable to create a TIDE

Explanation: Whilst processing a protected intervalcontrol request, CICS was not able to create theTransaction Id Element (TIDE) holding internal dataabout the request.


User response: Resubmit the transaction. If theproblem persists, CICS possibly ran out of memory.This is possibly due to a transaction that is looping insome way that causes CICS to acquie substantialamounts of Region Pool memory on its behalf. Checkthat the value of the MaxRegionPool attribute in theRegion Definition is sufficiently large. If it is not,perform an immediate shutdown of the region, increasethe value, and restart the region.

Destination:

CSMT

ERZ007008E CICS is unable to delete an ICE

Explanation: Because of an internal problem, CICSwas not able to delete the internal data held about aninterval control request.

System action: CICS continues processing

User response: Because the Interval Control datastructures are held in the Region Pool, this problem isunlikely to be caused by application code. It is morelikely to be caused by an inconsistency in the CICSinternal data structures. Check that the next CICSself-consistency check of the region is successful. If the

ERZ007003E • ERZ007008E


problem reoccurs, save any dump file produced andcontact your support organization.

Destination:

CSMT

ERZ007009W Unable to run asynchronous transaction’transId’ on inactive terminal ’terminalId’

Explanation: CICS tried to run anasynchronously-started transaction on a terminal thatwas logged off.

System action: CICS continues processing, andattempts to resubmit the transaction when the terminalis logged on.

User response: Sign on to the terminal, and thetransaction runs.

Destination:

console.msg

ERZ007010E Error obtaining data for terminal’terminalId’ for asynchronous running oftransaction ’transId’

Explanation: Whilst attempting to run an intervalcontrol request on terminal ’terminalId’, CICS was notable to obtain the terminal’s details.

System action: CICS continues processing, but doesnot submit the asynchronous transaction.

User response: Check that the terminal required forthe asynchronous start is in the database. Sign on to theterminal.

Destination:

console.msg

ERZ007011E Transaction ’transId’ not startedasynchronously

Explanation: CICS was unable to start anasynchronous transaction that is not attached to aterminal. The scheduler was unable to schedule therequest.

System action: CICS continues processing, but doesnot start the asynchronous transaction.

User response: Check the console log for any othermessages that possibly indicate why the transactionwas rejected. If there are none, check that thetransaction is correctly defined and then resubmit. Ifthe the problem persists contact your supportorganization.

Destination:

console.msg

ERZ007012E Unable to queue transaction ’transId’ onterminal ’terminalId’

Explanation: CICS made an unsuccessful attempt tostart a transaction on the named terminal.

System action: CICS continues processing, but doesnot start the transaction ’transId’.

User response: Check that a cicsterm is running forthe named terminal. If not, sign on to the terminal.

Destination:

console.msg

ERZ007013E Unable to obtain memory to create anInterval Control Element (ICE)

Explanation: CICS was not able to obtain the memoryrequired to create an ICE.


User response: Resubmit the transaction. If theproblem persists, CICS possibly ran out of memory.This is possibly due to a transaction that is looping insome way that causes CICS to acquire substantialamounts of Region Pool memory on its behalf. Checkthat the value of the MaxRegionPool attribute in theRegion Definition is sufficiently large. If it is not,perform an immediate shutdown of the region, increasethe value, and restart the region.

Destination:

CSMT

ERZ007014E Transaction ’transId’ could not betriggered because principal facility’terminalId’ does not exist, during a writeoperation to Transient Data (TD) queue’TDQname’

Explanation: The trigger transaction for Transient Data(TD) queue ’TDQname’ was not able to be startedbecause no definition for the specified facility’terminalId’ exists in the Terminal Definitions.

System action: See the following messages for furtherdetails.

User response: See the following messages for furtherdetails.

Destination:

CSMT

ERZ007015E Unable to obtain memory to create aDelay Context

Explanation: CICS was not able to obtain memory forthe data required to allow an EXEC CICS DELAY callto delay a task.

ERZ007009W • ERZ007015E




Destination:

CSMT

ERZ007016E Unable to delete Waiting Task data

Explanation: While processing a wait for a resourcethat has either timed out, or the lock has becomeavailable, CICS was not able to delete the informationabout the waiting task.

System action: CICS continues processing.

User response: Because the Interval Control datastructures are held in the Region Pool, the problemencountered freeing the data structures is unlikely to becaused by application code. It is more likely to becaused by an inconsistency in the CICS internal datastructures. If you want to investigate this problem,check that the next CICS self-consistency check of theregion is successful. If the problem reoccurs, save anydump file produced and contact your supportorganization.

Destination:

CSMT

ERZ007019E Unable to restart a triggered transaction

Explanation: A triggered transaction ended withoutremoving all of the records from its Transient DataQueue. Interval Control attempted to re-start thetransaction, but was unable to do so.


User response: If you want to investigate thisproblem, examine previous error messages for evidenceof an earlier problem, such as insufficient memory foran operation. Check previous messages for possiblereasons why this transaction was not able to be run.Check that the next CICS self-consistency check of theregion is successful. If the problem reoccurs, save anydump file produced and contact your supportorganization.

Destination:

console.msg

ERZ007020E Unable to create a transaction IDelement (TIDE)

Explanation: CICS was not able to create a TIDE.


User response: Resubmit the transaction. If theproblem persists, CICS possibly ran out of memory.This is possibly due to a transaction that is looping insome way that causes CICS to acquire substantialamounts of Region Pool memory on its behalf. Checkthat the value of the MaxRegionPool attribute in theRegion Definition is sufficiently large. Perform animmediate shutdown of the region, increase the value,and restart the region.

Destination:

CSMT

ERZ007021E Unable to unlock resources at syncpoint

Explanation: At syncpoint, CICS attempts to releaseall the locks held by a transaction. Because of aninternal error, it was unable to do so.


User response: Because the Interval Control datastructures are held in the Region Pool, the problemencountered freeing the data structures is unlikely to becaused by application code. It is more likely to becaused by an inconsistency in the CICS internal datastructures. Check that the next CICS self-consistencycheck of the region is successful. If the problemreoccurs, save any dump file produced and contactyour support organization.

Destination:

CSMT

ERZ007022E Unable to unlock resources attransaction end

Explanation: At transaction end, CICS attempts torelease all the locks held by a transaction. Because of aninternal error, it was unable to do so.


User response: Because the Interval Control datastructures are held in the Region Pool, the problemencountered freeing the data structures is unlikely to becaused by application code. It is more likely to becaused by an inconsistency in the CICS internal datastructures. Check that the next CICS self-consistencycheck of the region is successful. If the problemreoccurs, save any dump file produced and contactyour support organization.

Destination:

CSMT

ERZ007016E • ERZ007022E


ERZ007024E Attempt to delete a Temporary Storage(TS) queue returned ERZ_ABEND

Explanation: Interval Control attempted to delete aTSQ used for an Interval Control Element (ICE). It wasunable to do so, because the Temporary Storage deleteoperation abnormally terminated.


User response: Check that Temporary Storage isavailable. If it is not, consider restarting the file server.

Destination:

CSMT

ERZ007028E Lock Resource structure (at addressaddress) has inconsistent signature;expected ’expectedSignature’ actual’actualSignature’

Explanation: Self-consistency checking by CICS hasdetected an inconsistent signature string in the LockResource structure whose address is given.

System action: CICS self-consistency checkingcontinues.

User response: Because the Interval Control datastructures are held in the Region Pool it is unlikely thatthe invalid data has been produced by applicationcode. Consider shutting the region down if any furthererrors are reported. Save any dump file produced foruse by your support organization. If the problempersists contact your support organization.

Destination:

console.msg

ERZ007030W Cannot collect statistics for IntervalControl

Explanation: CICS was not able to find an entry in theCommunications Definitions for the local system.


User response: If you want statistics to be collectedfor Interval Control, you must have an entry for thelocal system in the region’s Region Definitions. Shutdown the region, add the entry for the local system inthe Region Definitions and restart the region.

Destination:

CSMT

ERZ007031E Unable to set an alarm for an ENQ

Explanation: CICS detected an unexpected return codewhen attempting to set an alarm.


User response: Resubmit the transaction. If theproblem persists CICS possibly ran out of memory.This is possibly due to a transaction that is looping insome way that causes CICS to acquire substantialamounts of Region Pool memory on its behalf. Checkthat the value of the MaxRegionPool attribute in theRegion Definition is sufficiently large. If it is not,perform an immediate shutdown of the region, increasethe value, and restart the region. If the problem persistsand you want to investigate it, check that the value ofthe DeadlockTimeout attribute in the RegionDefinitions is valid. If you cannot find the problem,check that the next CICS self-consistency check of theregion is successful.

Destination:

CSMT

ERZ007032E Unable to set an alarm

Explanation: CICS detected an unexpected return codewhen attempting to set an alarm.

System action: CICS abnormally terminates the server.

User response: CICS possibly ran out of memory. Thisis possibly due to a transaction that is looping in someway that causes CICS to acquire substantial amounts ofRegion Pool memory on its behalf. Check that the valueof the MaxRegionPool attribute in the RegionDefinition is sufficiently large. If it is not, perform animmediate shutdown of the region, increase the value,and restart the region. If you cannot find the problem,check that the next CICS self-consistency check of theregion is successful.

Destination:

CSMT

ERZ007033E Unable to access Temporary Storage

Explanation: CICS detected an unexpected return codewhen attempting to read from or write to temporarystorage.

System action: CICS continues processing. However,Interval Control is only available if Temporary Storageis available.

User response: Check that Temporary Storage isavailable. Check the error logs for previous messagesthat might indicate the cause of this problem.

Destination:

CSMT

ERZ007034E The request to run a transaction isinvalid

Explanation: CICS detected an invalid attempt to starta transaction. This is possibly because you attempted tostart a CICS-private transaction, or because a

ERZ007024E • ERZ007034E


transaction was started at an inappropriate phase ofregion operation, or on an invalid terminal, or thetransaction definitions (TD) did not allow thetransaction to be run via the START command.


User response: Ensure that the START command isvalid. Check that the value of the InvocationModeattribute in the Transaction Definition for thetransaction you want to START is appropriate.

Destination:

CSMT

ERZ007035E The Wait Task structure (at addressaddress) has inconsistent signature;expected ’expectedSignature’ actual’actualSignature’

Explanation: Self-consistency checking by CICS hasdetected an inconsistent signature string in the WaitTask structure whose address is given.



Destination:

console.msg

ERZ007036E The Interval Control Element (ICE)queue is inconsistent: Unexpectedexpiry time of head of queue

Explanation: The self-consistency checking mechanismof CICS detected an error in the ICE queue.



Destination:

console.msg

ERZ007037E Interval Control Element (ICE) (addressaddress) has inconsistent signature -expected ’expectedSignature’ actual’actualSignature’

Explanation: The self-consistency checking mechanismin CICS. detected an error in an element in the ICEqueue.



Destination:

console.msg

ERZ007038E Interval Control Element (ICE) queueinconsistent: ICE address is followed byaddress instead of address



User response: Because the Interval Control datastructures are held in the Region Pool it is unlikely thatthe invalid data has been produced by applicationcode. Save any dump file produced for use by yoursupport organization. If the problem persists contactyour support organization.

Destination:

console.msg

ERZ007039E Interval Control Element (ICE) queueinconsistent: ICE address is preceded byaddress instead of address




Destination:

console.msg

ERZ007035E • ERZ007039E


ERZ007040E Interval Control Element (ICE) addresshas inconsistent hash links: its reqId’reqId’ has a different hash value to thereqId ’reqId’ of the next ICE address




Destination:

console.msg

ERZ007041E Interval Control Element (ICE) addresshas inconsistent hash links: its reqId’reqId’ has a different hash value to thereqId ’reqId’ of the previous ICE address




Destination:

console.msg

ERZ007042E Interval Control Element (ICE) addresshas an expiry time inconsistent withthat of other ICEs in the queue

Explanation: The self-consistency checking mechanismof CICS detected an error in the ICE queue. CICSrelocates the ICE in the queue.



Destination:

console.msg

ERZ007043E Unable to obtain memory to create aLock Record (LR)

Explanation: CICS was not able to obtain the memoryrequired to create an ICE.


User response: Resubmit the transaction. If theproblem persists, CICS possibly ran out of memory.This is possibly due to a transaction that is looping insome way that causes CICS to acquire substantialamounts of Region Pool memory on its behalf. Checkthat the value of the MaxRegionPool attribute in theRegion Definition is sufficiently large. If it is not,increase the value, and restart the region.

Destination:

CSMT

ERZ007044E Recovery of Interval Control Element’TSQname’ was unsuccessful due to anI/O error

Explanation: CICS was not able to recover an IntervalControl Element because it was unable to read thecorresponding Temporary Storage Queue.


User response: Check that Temporary Storage isavailable. Restart the file server if necessary. Performinga cold start avoids this problem, but causes recoveryinformation to be lost.

Destination:

console.msg

ERZ007045E Recovery of Interval Control ElementTSQname was unsuccessful due to baddata

Explanation: CICS was not able to recover IntervalControl Element because the corresponding TemporaryStorage Queue contained unrecognized data.


User response: Examine previous messages forproblems that might affect Temporary Storage. Restartthe file server if necessary. Performing a cold startavoids this problem, but causes recovery information tobe lost.

Destination:

console.msg

ERZ007040E • ERZ007045E


ERZ007046E Recovery of Interval Control ElementTSQname was unsuccessful

Explanation: CICS recovered an Interval ControlElement but was unable to add it to the ICE queue.This must be due to an internal inconsistency.


User response: Because the Interval Control datastructures are held in the Region Pool it is unlikely thatthe invalid data has been produced by applicationcode. It is more likely to be caused by an inconsistencyin the CICS internal data structures. Performing a coldstart avoids this problem, but causes recoveryinformation to be lost.

Destination:

console.msg

ERZ007047E Unable to schedule the blocked ICErecovery transaction

Explanation: CICS was not able to schedule theCICS-private transaction that updates recovered startsin the event of the file server not being available. Thismust be due to an internal inconsistency.


User response: During auto start, CICS has attemptedto recover Interval Control Elements (ICEs), but isunable to do so because Temporary Storage isunavailable. Therefore, it attempts to schedule atransaction that recovers the blocked requests. Thisattempt to schedule the transaction has failed. If youwant to investigate this problem, check that the valueof the MaxRegionPool attribute in the RegionDefinition is sufficiently large. If it is not, increase itand restart the region. Check that the value of theCUBSDelayMinutes attribute in the Region Definitionsis reasonable: between 1 and 5999. Performing a coldstart avoids this problem, but causes recoveryinformation to be lost.

Destination:

console.msg

ERZ007048E Invalid attempt to route triggeredtransaction ’transId’ for Transient Dataqueue ’TDQname’

Explanation: The definition of a transaction that hasbeen specified as the trigger transaction for a transientdata queue indicates that the transaction is to be routedto another system. This is invalid.


User response: Consider changing the transaction

definitions (TD) so that the transaction has a blankRemoteSysId. Alternatively, you can change thetransient data definitions (TDD) so that theTriggeredTransId contains the name of a transactionthat is run locally.

Destination:

CSMT

ERZ007049W Asynchronously-started transaction’transId’ terminated abnormally.Temporary Storage Queue ’TSQName’should be deleted.

Explanation: The asynchronously-started transactionhas terminated abnormally because the applicationserver in which it was running was unexpectedlyterminated. CICS has been unable to delete the TSqueue associated with the transaction.

System action: CICS continues.

User response: Delete the TS Queue associated withthe transaction. This can be done by using theCICS-supplied transaction CECI. Failure to delete theTS Queue can result in the asynchronous start beingrecovered if the region is warm started.

Destination:

console.msg

ERZ007050W Triggered transaction ’transId’ forTransient Data Queue ’TDQname’ hasencountered problems

Explanation: The triggered transaction hasencountered a problem. Previous messages possiblyindicate the source of the problem.


User response: Examine previous messages for thesource of the problem and take action accordingly.

Destination:

console.msg

ERZ007051W Asynchronously-started transaction’transId’ has encountered problems

Explanation: The asynchronously-started transactionhas encountered a problem. Previous messages possiblyindicate the source of the problem.


User response: Examine previous messages for thesource of the problem and take action accordingly.

Destination:

console.msg

ERZ007046E • ERZ007051W


ERZ007052W Transaction ’transId’ has not run.Temporary Storage Queue ’TSQName’ forAsynchronously-started transaction’transId’ should be deleted.

Explanation: The asynchronously-started transactionhas not run and CICS has been unable to delete the TSqueue associated with the transaction. Other consolemessages possibly indicate the cause of the problem. Ifthere are no other related messages, failure are possiblydue to problems in Transaction Definition (TD).


User response: Check the Transaction Definition (TD)for possible errors. Delete the TS Queue associated withthe transaction. This can be done by using theCICS-supplied transaction CECI. Failure to delete theTS Queue can result in the asynchronous start beingrecovered if the region is warm started.

Destination:

console.msg

ERZ007053E The reqid ’reqId’ does not exist

Explanation: Attempt to delete the reqid has failed asit does not exist.


User response: The TS Queue was possibly alreadydeleted or the TSQ definition is possibly incorrect.

Destination:

console.msg

ERZ007054I Temporary Storage queue of name’TSQname’ already exists

Explanation: CICS detected that a temporary storagefile of this name already exists when attempting towrite to temporary storage.


User response: Check the Reqid used and alter it toavoid conflicts with names of temporary storagequeues.

Destination:

CSMT

ERZ007055E Unable to schedule the ICE canceltransaction

Explanation: CICS was not able to schedule theCICS-private transaction that cancels starts.


User response: This attempt to schedule thetransaction responsible for cancelling STARTS has

failed. If you want to investigate this problem, checkthat the value of the MaxRegionPool attribute in theRegion Definition is sufficiently large. If it is not,increase it and restart the region.

Destination:

console.msg

ERZ007056E Unable to locate Transaction Definitionfor transaction ’transId’

Explanation: CICS was not able to schedule theCICS-private transaction identified in the messagebecause the Transaction Definition was not able to belocated.


User response: This attempt to schedule the internaltransaction ’transId’ has failed. If you want toinvestigate this problem, check that the ’transId’transaction is present in the region’s TransactionDefinitions. Use the definitions from another region toverify the definition does not differ from the defaultdefinition for this transaction.

Destination:

console.msg

ERZ007057E Unable to queue transaction ’transId’ onterminal ’terminalId’, transactiondestination sysid is ’SysId’, terminalRemoteSysId ’SysId’.

Explanation: CICS made an unsuccessful attempt tostart a transaction on the named terminal. Thetransaction was directed to start on terminal terminalId,at that time the terminal had a RemoteSysId of SysId.The terminal RemoteSysId is now SysId. This messageis usually driven by common client applications with aprinter that have terminated before a transaction canrun on the printer. If the terminals RemoteSysId is nowNULL then the terminal is active locally.

System action: CICS continues processing, but doesnot start the transaction ’transId’.

User response: Check that a cicsterm or cicstermp isrunning for the named terminal. If not, sign on to theterminal.

Destination:

console.msg

ERZ007058E Unable to obtain memory to create aWait Context

Explanation: CICS was not able to obtain memory forthe data required to allow an EXEC CICS POST call todelay a task.

ERZ007052W • ERZ007058E




Destination:

CSMT

ERZ007059E Excpection ’EXCEPTIONtext’ in handpost thread.

Explanation: CICS encountered an unexpectedexpection (EXCEPTIONtext) while processing handposts


User response: Contact support

Destination:

console.msg

ERZ010001E Unable to run region ’regionName’because it is locked

Explanation: CICS cannot start the region ’regionName’because a lock file already exists. This indicates eitherthat the region with this name is already running, orthat the region is not running and the lock file remainsdue to the termination of the region in an uncontrolledmanner.

System action: CICS startup terminates.

User response: If cicsgpid shows that a region of thegiven name is running already, you cannot start it. Ifthere is no region running but a lock file exists, usecicsrlck to remove the lock. When using cicsrlck,ensure that you only remove the lock file for the region’regionName’.

Destination:

console.msg

ERZ010002E Unable to find the lock file for region’regionName’

Explanation: CICS was not able to find the lock filefor the named region. CICS creates the lock file atregion startup and deletes it at region shutdown. Thiserror suggests that the named region is not running.

System action: cicsgpid terminates.

User response: Check that you supplied the correctregion name.

Destination:

stderr

ERZ010003I CICS is performing region abnormaltermination in process ’processName’

Explanation: CICS is abnormally terminating theregion due to a CICS internal error.

System action: CICS abnormally terminates theregion, and produces a system dump.

User response: Examine previous error messages todetermine the cause of the problem.

Destination:

console.msg

ERZ010004I CICS will use AuthenticationService:nameService

Explanation: CICS uses the name service facilitiessupplied by nameService for its clients to locate theirservers and uses authentication service facilitiessupplied by authenticationService.

System action: CICS continues to run start up.


Destination:

console.msg

ERZ010005E Unable to find startup or shutdownprogram ’programName’

Explanation: CICS cannot find the program’programName’ listed in the program list for startup orshutdown.

System action: If this error occurs during startup, thenCICS abnormally terminates the region. If it occurs atshutdown, region shutdown processing continues.

User response: Check that the entries in the programlist and the Program Definitions (PD) are consistent.Use program names, not transaction names in thestartup or shutdown program lists.

Destination:

console.msg

ERZ010006E Unable to run startup program’programName’ because of insufficientauthorization

Explanation: The program programName cannot be runbecause it has inappropriate security permissions.

System action: If this error occurs during startup, thenCICS abnormally terminates the region. If it occurs at

ERZ007059E • ERZ010006E


shutdown, region shutdown processing continues.

User response: Change the security permissions forthe program. Ensure that it has read and executepermission for user cics.

Destination:

console.msg

ERZ010007I About to run shutdown phasephaseNumber programs

Explanation: CICS shutdown processing is runningthe programs in the shutdown program list for phasephaseNumber of shutdown.

System action: CICS continues to shut down.

User response: None

Destination:

console.msg

ERZ010008W Unable to read the region restart file,operating system error numbererrorNumber

Explanation: CICS uses the restart file to recoverinformation saved during a previous run of the region.CICS was not able to read data from the restart file.

System action: CICS continues to run start up.

User response: Check the access permissions for theregion directory and the region restart file. Ensure thatthey have read and write permissions for user cics. Theregion restart file was possibly truncated due to anoperating system problem. If you suspect that this isthe case, check the integrity of the filesystem. Seemessage ERZ1092E following this one for furtherdetails. If the content of ERZ1092E gives insufficientinformation about why the error occurred use theoperating system error number errorNumber to obtainmore information.

Destination:

console.msg

ERZ010009I Unable to remove the lock file becauseregion ’regionName’ is still runningprocess ’processInformation’

Explanation: CICS attempted to remove a region lockfile using cicsrlck, but the named region is running.’processInformation’ is the process identification numberfor the region process.

System action: cicsrlck terminates.

User response: Ensure that the named region is theregion whose lock file you wish to remove. In certainrare circumstances, another process can be assigned thesame process ID that the region ran with. In thissituation, you can use the -f flag to force removal.

Destination:

stderr

ERZ010010W Removing the lock file region for’regionName’ although it is still runningprocess ’processName’

Explanation: cicsrlck removed the lock file for thenamed region even though there appears to be aprocess running for the region. cicsrlck removed thelock because you specified the force flag -f.’processName’ is the process identification number forthe region process.


User response: Check whether the process running isfor the region. If it is, shut down the regionimmediately, because the region is able to be startedagain, causing data to be overwritten.

Destination:

stderr

ERZ010011E CICS cannot create region lock file’fileName’ for region ’regionName’,operating system error numbererrorNumber

Explanation: The CICS process was not able to createthe lock file for the named region.

System action: CICS terminates.

User response: Check that the directory for the namedregion has the required permissions. Ensure that it isowned by user cics and that it has read, write andexecute permissions for its owner. Check that the filesystem is not full. See message ERZ1092E followingthis one for further details. If the content of ERZ1092Egives insufficient information about why the erroroccurred use the operating system error numbererrorNumber to obtain more information.

Destination:

console.msg

ERZ010012I CICS is performing an immediateshutdown of region ’regionName’

Explanation: A request to shut down the regionimmediately has been received.

System action: The region commences an immediateshutdown.

User response: None

Destination:

console.msg

ERZ010007I • ERZ010012I


ERZ010013I CICS has removed the lock file forregion ’regionName’

Explanation: cicsrlck has removed the lock file for thenamed region.

System action: None

User response: None

Destination:

stderr

ERZ010014E Cannot read lock file for region’regionName’ because of operating systemerror errorNumber

Explanation: cicsgpid was not able to read the lockfile for region ’regionName’.


User response: Check that the region directory isavailable and that the permissions for the region lockfile are appropriate.

Destination:

stderr

ERZ010015E Cannot remove lock file for region’regionName’ because of operating systemerror errorNumber

Explanation: cicsrlck was not able to remove theregion lock file.


User response: Check that the permissions for theregion directory and the region lock file are correct.Ensure that they are owned by user cics and have read,write and execute permissions for their owner.

Destination:

stderr

ERZ010016W Could not open restart file for region’regionName’, operating system errornumber errorNumber

Explanation: CICS was unable to open the regionrestart file.

System action: CICS logs this message and continues.

User response: Check that the permissions for theregion directory and the region restart file are correct.Ensure that they are owned by user cics and have read,write and execute permissions for their owner. Seemessage ERZ1092E following this one for furtherdetails. If the content of ERZ1092E gives insufficientinformation about why the error occurred use theoperating system error number errorNumber to obtainmore information.

Destination:

console.msg

ERZ010017I CICS is performing a normal shutdownof region ’regionName’

Explanation: A request to shutdown the regionnormally has been received.

System action: The region commences a normalshutdown.

User response: None

Destination:

console.msg

ERZ010018E Unable to allocate a unique identifierfor process ’processName’

Explanation: CICS was not able to create aregion-wide unique identifier for the named process.


User response: If the problem persists, save any dumpproduced and contact your support organization.

Destination:

console.msg

ERZ010019W Cannot start Application Server

Explanation: CICS was unable to start an ApplicationServer. This is possibly because there are already alarge number of processes running.

System action: The transaction that was to be run inthe server is placed on the queue and is run when aserver becomes available.

User response: Check the system log for further errordetails. If the system is heavily loaded, reduce the loadby stopping some processes or by restricting themaximum number of Application Servers by updatingthe value of the attribute MaxServer in the RegionDefinitions. Check whether the region has beeninstalled correctly and that the processes have executepermission for the cics user. If the cause of the problemcannot be found, contact your support organization.

Destination:

console.msg

ERZ010020I *** CICS startup is complete ***

Explanation: The region is now ready for use.


User response: None

Destination:

ERZ010013I • ERZ010020I


console.msg

ERZ010023E Cannot attach or detach shared memorysegment, error code errorCode

Explanation: CICS made an unsuccessful attempt toattach or detach shared memory. The Data Segmentshared memory identifier was possibly overwritten.There is possibly inconsistency in either CICS oroperating system data structures.


User response: Save any dump produced and contactyour support organization.

Destination:

console.msg

ERZ010024E Invalid invocation of process’processName’

Explanation: An attempt was made to start an internalCICS process ’processName’. The process cannot be usedin this way.

System action: CICS terminates the process.

User response: Do not invoke this process directly.Refer to the CICS documentation for details of how tostart a CICS region.

Destination:

stderr

ERZ010025W Unable to write to restart file for regionregionName, operating system errornumber errorNumber

Explanation: CICS was unable to write to the restartfile, varDir/cics_regions/regionName/region_restart forthe reason given by the operating system error codeerrorNumber. On Windows NT you can find the driveletter of the disk containing the cics_regions directoryby using the cicsname regions command.

System action: CICS logs this message and continues.

User response: Check that the region directory is stillavailable, and that the restart file has appropriatepermissions. Check that the file system is not full. Seemessage ERZ1092E following this message for furtherdetails. If the content of ERZ1092E gives insufficientinformation refer to operating system documentationfor further information about the operating systemerror number errorNumber. Perform a normal shutdownfollowed by a warm start.

Destination:

console.msg

ERZ010026I Usage: cicsrlck [-f] [-a | -r regionName]

Explanation: You invoked cicsrlck with invalidarguments.


User response: Retry the command with the correctsyntax. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ010027E Could not generate a list of availablelock files

Explanation: cicsrlck made an unsuccessful attempt toaccess each region directory and determine if a lock filewas present.


User response: Check the availability and accesspermissions for the region directories invarDir/cics_regions. On Windows NT you can find thedrive letter of the disk containing the cics_regionsdirectory by using the cicsname regions command.Ensure that each is owned by user cics and has read,write and execute permissions for its owner.

Destination:

stderr

ERZ010029E Unable to access the directory’directoryName’

Explanation: cicssrccreate was unable to access thedirectory. The directory must exist, be owned by usercics and have read, write and execute permissions forits owner.

System action: cicssrccreate exits.

User response: If the directory does not exist theproduct has not been installed successfully.

Destination:

stderr

ERZ010030I CICS self consistency checking started.

Explanation: CICS has started to check the integrity ofthe region. This check takes place at time intervalscontrolled by the Region Definition (RD) entry.

System action: CICS self consistency checking begins.

User response: None

Destination:

console.msg

ERZ010023E • ERZ010030I


ERZ010031I Usage: cicsgpid [-r regionName]

Explanation: The command was invoked with invalidarguments.


User response: Retry the command with the correctsyntax. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ010032E Could not write process identifier tostandard output

Explanation: cicsgpid encountered an error displayingthe process identifier of the region.


User response: Check that the standard output of thecicsgpid command is directed to a valid destination. Ifthe destination is a file, check that it is possible to writeto that file.

Destination:

stderr

ERZ010033E Unable to obtain region definitioninformation

Explanation: CICS detected an internal error accessingthe region database. CICS possibly ran out of RegionPool memory.



Destination:

console.msg

ERZ010034E Unable to complete access to regioninformation

Explanation: CICS detected an internal error. Unableto update region database. CICS possibly ran out ofRegion Pool memory.



Destination:

console.msg

ERZ010035I Waiting for user tasks to complete

Explanation: Entering the phase 2 of normalshutdown, CICS waits for all user tasks to complete.

System action: CICS waits until no user tasks arerunning.

User response: Terminate all user tasks. If you cannotstop a task directly, or you are unsure which tasks arestill running, use CEMT to list running tasks and theterminals they are running on. If the tasks cannot becompleted then CEMT can be used to purge them.

Destination:

console.msg

ERZ010038E Recovery Server has terminatedabnormally

Explanation: The Recovery Manager has detected thata Recovery Server completed with an abnormal returncode.

System action: CICS shuts the region downimmediately.

User response: Examine the error log for earliermessages that possibly indicate the cause of theproblem. If problems persist, contact your supportorganization.

Destination:

console.msg

ERZ010039E Unable to start process ’processPath’

Explanation: CICS was not able to start one of one ofits internal processes. See message ERZ1092E followingthis one for further details.

System action: If CICS is trying to start a newapplication server (message ERZ1019W appears shortlyafter this message), the start fails and the transaction isplaced on the queue. Otherwise, CICS shuts the regiondown immediately.

User response: Check that the operating system iscapable of starting new processes. If the system isheavily loaded, reduce the load by stopping someprocesses or by restricting the maximum number ofApplication Servers by updating the value of theattribute MaxServer in the Region Definitions. Checkwhether the region has been installed correctly and thatthe processes have execute permission for the cics user.If the cause of the problem cannot be found, contactyour support organization.

Destination:

console.msg

ERZ010031I • ERZ010039E


ERZ010040I CICS control process ’processName’terminated

Explanation: One of the CICS control processesterminated. If the termination was unexpectedadditional messages are output.

System action: If the termination was unexpected andthe process was not an Application Server (cicsas), theregion abnormally terminates.

User response: If additional messages indicate that theprocess ended abnormally they possibly also givepossible causes of the problem.

Destination:

console.msg

ERZ010041I CICS has received a region stop requestduring region shutdown

Explanation: CICS was performing a region shutdownwhen it received a request to terminate the region.

System action: CICS immediately stops any shutdownprocessing and attempts to end all region processesimmediately.

User response: Wait until message ERZ1043I orERZ10122E appears. If the message does not appearafter three minutes, the region is cancelled. If thishappens run the cicsnotify program to free any regionresources before you attempt to restart the region.

Destination:

console.msg

ERZ010042E Invalid combination of MinServer(servers) and MaxServer (servers)attributes

Explanation: The minimum number of servers isgreater than the maximum number or the maximumnumber is zero. The maximum must equal or exceedthe minimum value and must be greater than zero.

System action: If this error occurs during startup,CICS terminates. Otherwise CICS continues to run withunchanged values.

User response: Change the value of MinServer,MaxServer, or both. If this occurs at startup alter theRegion Definition (RD) values or startup overrides.

Destination:

console.msg

ERZ010043I Shutdown of CICS region ’regionName’is complete

Explanation: The shutdown of a CICS region iscomplete.


User response: None

Destination:

console.msg

ERZ010044E Unable to find the CICS version

Explanation: cicssrccreate uses cicsname to determinethe version. cicsname returned an error.


User response: Examine previous messages forpossible indications of the problem. Check that theproduct has been installed correctly.

Destination:

stderr

ERZ010045I Signal signalNumberd received andignored by process ’processName’

Explanation: The named process received anunexpected, but not fatal, signal. For instance, signal 19is SIGCONT that is controlled entirely by the operatingsystem. It is usually sent to continue stopped processes.During a region shutdown sequence this signal ispossibly issued to a CICS process as part of the normalsystem action for ending a process.

System action: CICS ignores the signal, and continues.

User response: Refer to your operating systemdocumentation to determine the meaning of the signal.For AIX this information is found in the AIX BaseOperating System and Extensions Technical Reference,Volume 2.

Destination:

console.msg

ERZ010048I Application Server serverId terminated

Explanation: The identified Application Server hasterminated and is no longer available for use.


User response: None

Destination:

console.msg

ERZ010049E Unable to schedule the CLAMtransaction

Explanation: CICS made an unsuccessful attempt tosubmit the internal CICS transaction, CLAM, to runasynchronously. CICS possibly ran out of Region Poolmemory.


ERZ010040I • ERZ010049E



Destination:

console.msg

ERZ010052W Recovery Server has terminatedabnormally

Explanation: The Recovery Manager has detected thata Recovery Server completed with an abnormal returncode during a normal or immediate shutdown. This isthe expected behavior when the logical unit of workbeing resolved by the Recovery Server remainsunresolved.

System action: Shutdown continues.

User response: None

Destination:

console.msg

ERZ010053E Unable to start a thread

Explanation: CICS detected an error when trying tostart a thread to perform an operation.


User response: See message ERZ1092E following thisone for further details.

Destination:

console.msg

ERZ010054I CICS self consistency checkingcompleted

Explanation: CICS has successfully completed a checkof the integrity of the region. No fatal inconsistencieswere found.

System action: The region continues.

User response: None

Destination:

console.msg

ERZ010055E Could not allocate a Common WorkArea (CWA) from task shared memory

Explanation: During initialization, CICS was not ableto obtain the shared memory for the CWA. This ispossibly because there is insufficient memory allocatedfor the task shared pool.


User response: Check that the MaxTSHPool value in

the Region Definition is sufficiently large. Increase thevalue, and cold start the region.

Destination:

console.msg

ERZ010056E Region abnormally terminated duringregion shutdown processing.

Explanation: A problem occurred during CICS regionshutdown, and the region is now terminatingabnormally.


User response: Examine previous messages for thecause of the problem.

Destination:

console.msg

ERZ010057I Performing request to terminateApplication Server serverId

Explanation: A request has been made to terminate anapplication server. This is normally associated with arequest to purge a task, or when the Application Servertimed out having not been used for theServerIdleLimit period defined in the RegionDefinition (RD). It can also occur when the TransactionScheduler detects that an Application Server wasunsuccessful during processing of a request to run atransaction.

System action: CICS terminates the ApplicationServer.

User response: If this message appears very regularlythen the RD value of ServerIdleLimit was possibly setto too small a value. This causes degradation inperformance if Application Servers are constantly beingcreated and terminated.

Destination:

console.msg

ERZ010061E Unable to initialize ’processName’ process

Explanation: CICS was not able to initialize aninternal process.

System action: If the process is an Application Server(cicsas), then CICS attempts to continue normaloperation. Otherwise CICS abnormally terminates theregion.

User response: Check previous messages for possiblecauses of this error.

Destination:

console.msg

ERZ010052W • ERZ010061E


ERZ010062E Unable to allocate region memory

Explanation: CICS was not able to allocate region poolstorage.

System action: If CICS is trying to start a newapplication server (message ERZ1019W appears afterthis message), the start fails and the transaction isplaced on the queue. Otherwise, CICS abnormallyterminates the region.


Destination:

console.msg

ERZ010063I Running startup program ’programName’

Explanation: CICS is about to run the named startupprogram.

System action: CICS runs the program.

User response: None

Destination:

console.msg

ERZ010064E Unable to attach region shared memoryor task shared memory

Explanation: During initialization of a CICS process,CICS was not able to attach the required memory.There is possibly an inconsistency in CICS data.


User response: A user transaction possibly caused thisproblem. If you want to investigate further, see if aparticular transaction is associated with the problem.

Destination:

console.msg

ERZ010065E Unable to create CICS Log Daemonprocess

Explanation: CICS was not able to create the LogDaemon process.


User response: Check that the system is not tooheavily loaded, and that CICS has been installedcorrectly.

Destination:

console.msg

ERZ010066E Unable to create CICS RecoveryManager process

Explanation: CICS was not able to create the RecoveryManager process.



Destination:

console.msg

ERZ010067E Unable to create CICS ApplicationManager process

Explanation: CICS was not able to create theApplication Manager process.



Destination:

console.msg

ERZ010068E Process initialization unable to findrequired details for process processId

Explanation: CICS was not able to find the detailsrequired to initialize the given internal process.


User response: The process cannot find an entry foritself in an initialization table. This is possibly due toinconsistency in CICS internal data. Attempt to start theregion again, and if the problem persists, contact yoursupport organization.

Destination:

console.msg

ERZ010069E Usage: cicssrcdestroy [-r regionName |-s SFSserverName | -gppcgwyServerName]

Explanation: cicssrcdestroy was run with incorrectparameters. One (and only one) of the three optionsmust be supplied.

System action: cicssrcdestroy exits.

User response: Run cicssrcdestroy with correctparameters.

Destination:

ERZ010062E • ERZ010069E


stderr

ERZ010070E Unable to initialize Task Control Area(TCA)

Explanation: CICS detected an error while initializingthe TCA for a process. CICS possibly ran out of RegionPool memory.

System action: If the process in which this problemoccurs is one of the critical region processes then CICSabnormally terminates the region. If the process beinginitialized is an Application Server then just thatprocess is abnormally terminated.

User response: Look for earlier messages for the causeof this problem.

Destination:

console.msg

ERZ010071E Unable to create CICS Interval Controlprocess

Explanation: CICS was not able to create the IntervalControl process.


User response: Check that CICS has been installedcorrectly, and that the system is not too heavily loaded.

Destination:

console.msg

ERZ010072I Deleting subsystem and notify method’subsystemName’

Explanation: cicssrcdestroy is about to delete an entryfor the subsystem and notify method ’subsystemName’.

System action: cicssrcdestroy continues.

User response: None

Destination:

stderr

ERZ010073E Unable to start the transaction ’transId’

Explanation: CICS detected an error when attemptingto run the CICS private transaction ’transId’.


User response: Examine previous messages forpossible causes of this error.

Destination:

console.msg

ERZ010074E Signature of RCA inconsistent: expected’expectedSignature’ actual ’actualSignature’

Explanation: The data in the region’s data area hasbeen found to be inconsistent during CICS selfconsistency checking.


User response: Save any dump file produced. If theproblem persists contact your support organization.

Destination:

console.msg

ERZ010075E Exception exceptionName caught

Explanation: CICS detected an unexpected exceptionalcondition.

System action: If the exception is detected in anApplication Server (cicsas) the process is terminatedand CICS continues. CICS abnormally terminates theregion if the exception is detected in any other process.

User response: Check any messages before this onefor possible causes of the error. Save any dump fileproduced. If the problem persists contact your supportorganization.

Destination:

console.msg

ERZ010077E Usage: cics [-r regionName][overrideAttributes]

Explanation: CICS was unable to start because ofincorrect command-line parameters.


User response: Retry the command with the correctsyntax to start CICS.

Destination:

console.msg

ERZ010081E Error reading region database for region’regionName’

Explanation: The main CICS process was not able toread the region database details.


User response: Check that the region directory hasappropriate access permissions. Ensure that it is ownedby user cics and has read, write and executepermissions for its owner. If not, the region waspossibly not imported successfully.

Destination:

console.msg

ERZ010070E • ERZ010081E


ERZ010082E Unable to allocate memory for startup orshutdown program ’programName’

Explanation: CICS attempted to run the namedprogram but was unable to allocate sufficient memoryto do so.

System action: If this error occurs during startup,CICS abnormally terminates the region. Otherwiseshutdown continues.


Destination:

console.msg

ERZ010083E Startup or shutdown program’programName’ abnormally terminated

Explanation: During startup or shutdown processingCICS attempted to run the named program from thestartup or shutdown program list. This programabnormally terminated.


User response: There is possibly a problem with theprogram. If the problem happened during startup,remove the program from the startup program list andrestart the region. Check that the program is the correctone, and also that it is suitable to be run as a startup orshutdown program. One way of testing that theprogram is suitable is to run it using EXEC CICSSTART without a TERMID option.

Destination:

console.msg

ERZ010084E Startup or shutdown program’programName’ ended with ABENDCANCEL or ABEND ABCODE CANCEL

Explanation: During startup or shutdown processingCICS attempted to run the named program from thestartup or shutdown program list. This programterminated.


User response: There is possibly a problem with theprogram. If the problem happened during startup,remove the program from the startup program list andrestart the region. Check that the program is the correctone, and also that it is suitable to be run as a startup orshutdown program.

Destination:

console.msg

ERZ010085E Default region directory not found

Explanation: No region name was specified to thecicsrlck or cicsgpid command so the default regionname was used The directory containing the regionconfiguration for this default region was not able to befound.

System action: The program terminates.

User response: If the default region name is not theregion required, retry the command specifying therequired name using -r regionName. Otherwise, checkthat the default region has been correctly installed andthat the region directory exists. Check that the accesspermissions for the directory are appropriate. Ensurethat it is owned by user cics and has read, write, andexecute permissions for its owner.

Destination:

stderr

ERZ010086E Region directory for region ’regionName’not found or not accessible.

Explanation: cicsrlck, cicsgpid or CICS main processwas not able to find or access the named region.


User response: Check that the region named exists.On Windows NT you can find the drive letter of thedisk containing the cics_regions directory by using thecicsname regions command. Check that the accesspermissions for the directory are appropriate.

Destination:

stderr

ERZ010087E Region forcibly terminated duringregion abnormal termination processing

Explanation: While the region was performing anabnormal termination, CICS detected another abnormaltermination.

System action: CICS forcibly terminates all regionprocesses.

User response: Examine previous messages forpossible causes of the problem.

Destination:

console.msg

ERZ010088E Process ’processId’ could not access theRegion Pool during a system abnormaltermination

Explanation: During abnormal termination of a regionCICS was not able to access region memory.

ERZ010082E • ERZ010088E


System action: If this error does not occur in the mainCICS controlling process, CICS continues the regionabnormal termination process. Otherwise, CICS forciblyterminates all region processes.


Destination:

console.msg

ERZ010089E Application Server serverId PIDAppSerPID ended unexpectedly

Explanation: The Application Manager (cicsam)process detected the unexpected end of the ApplicationServer serverId with PID AppSerPID.



Destination:

console.msg

ERZ010090E Process cannot access region memory

Explanation: CICS cannot access the region memoryneeded to run the process.

System action: CICS attempts to continue running.

User response: Examine previous messages forpossible causes of the problem. If previous messagesindicate that this problem has occurred duringabnormal termination, no action needs to be taken.Otherwise this message possibly indicates aninconsistency in either CICS or operating system datastructures. Request an immediate shutdown of theregion. Save any dump produced and contact yoursupport organization.

Destination:

console.msg

ERZ010092E errorMessage

Explanation: An underlying error was detected.

System action: See the preceding message for theaction that is taken.

User response: Use the contents of this message andthe details of the previous message to decide on theresponse.

Destination:

console.msg

ERZ010093E The transaction ’transId’ failed

Explanation: A CICS private transaction failed. Theregion cannot startup without the transactioncompleting.


User response: Examine preceding messages todetermine the cause of this problem.

Destination:

console.msg

ERZ010096E Unable to delete subsystem’subsystemName’

Explanation: cicssrcdestroy encountered an errordeleting an entry for the named subsystem.

System action: cicssrcdestroy exits.

User response: Look at the previous messages for thecause of the error.

Destination:

stderr

ERZ010098E One of the region processes,’processName’, terminated abnormally

Explanation: One of the CICS region processesterminated abnormally.


User response: Examine previous messages forpossible causes of this problem.

Destination:

console.msg

ERZ010099W Unable to close the restart file for region’regionName’, operating system errornumber errorNumber

Explanation: CICS detected an error when attemptingto close the restart file. See message ERZ1092Efollowing this one for further details.


User response: Check that the directory for the namedregion has the required permissions. Ensure that it isowned by user cics and has read, write and executepermissions for its owner. Check that the file system isnot full. If the content of ERZ1092E gives insufficientinformation use the operating system error numbererrorNumber to obtain more information.

Destination:

console.msg

ERZ010089E • ERZ010099W


ERZ010100I The requested shutdown will beperformed when startup is complete

Explanation: CICS has received a request to terminatethe region while it is still performing startup. Itcontinues with startup, and shut down the region assoon as startup is complete.

System action: CICS continues startup.

User response: Wait until startup is complete. Theregion then shuts down.

Destination:

console.msg

ERZ010101E Process Name is inconsistent: expected’expectedSignature’ actual ’actualSignature’

Explanation: CICS self consistency checking detected aproblem. The name of the current process in the taskarea is incorrect.

System action: CICS continues normal operation.

User response: This problem is possibly caused by atransaction that has overwritten CICS internal data.Shut down the region as soon as possible. If the valueof the attribute SafetyLevel in the Region Definitions(RD) is set to ″none″, set it to ″normal″. If you want toinvestigate this problem, set the value of the attributeIntrospectInterval in the RD to 1 and restart the region.Try to determine which transaction is causing theproblem.

Destination:

console.msg

ERZ010102E Process count (processCount) does notequal number of processes in list(processActual)

Explanation: The maintained count of Process IDs wasfound to be different from the actual number of ProcessID structures during CICS self-consistency checking.The maintained count has now been set to the actualnumber of structures.

System action: CICS corrects the problem andcontinues operation.

User response: There is an inconsistency with CICSinternal data structures. Shut down the region as soonas possible. If the value of the attribute SafetyLevel inthe Region Definitions (RD) is set to none, set it tonormal and restart the region. If the problem persiststhen it is probably not caused by a user transaction. Ifyou want to investigate it, set the value of the attributeIntrospectInterval in the RD to 1 and restart the region.

Destination:

console.msg

ERZ010103E Region name regionName is too long

Explanation: The region name is too long, use ashorter name.


User response: Use the correct region name. If youdid not specify a region name because you wanted touse a default region, ensure the default region has ashorter name.

Destination:

console.msg

ERZ010104E Unable to set permission of regionmessage log ’fileName’, operating systemerror number errorNumber

Explanation: CICS attempts to set the permissions ofthe region message log file to an appropriate value. Itwas unable to perform this operation. See messageERZ1092E following this one for further details.

System action: CICS startup continues.

User response: Check that the region directory isaccessible and has write permission for the user ’cics’.If not, correct the region directory’s permissions andrestart the region. Check that there is sufficient freespace in the filesystem containing the region directory.

Destination:

console.msg

ERZ010105W The region environment file is missing

Explanation: The environment file in the regiondirectory is missing.


User response: If environment settings are required,create this file. An example environment file isprovided with the default region.

Destination:

console.msg

ERZ010106E Error errorCode occurred when changingthe file permissions of the regionmessage log

Explanation: CICS attempts to set the permissions ofthe region message log file to an appropriate value. Itwas unable to perform this operation, because theoperating system error with code errorCode occurred.

System action: CICS startup continues.

User response: Check that the region directory isaccessible and has write permission for the user ’cics’.If not, correct the region directory’s permissions andrestart the region.

ERZ010100I • ERZ010106E


Destination:

console.msg

ERZ010107W Line lineNumber of the regionenvironment file is invalid

Explanation: There is a syntax error in the regionenvironment file.

System action: CICS attempts to read the next line inthe environment file and continues startup.

User response: Correct the line in the environmentfile. If the value is required for region operation, shutdown the region and restart it. The CICS environmentfile must contain only comment lines that have a ’#’ inthe first column, blank lines, and lines in the form’name=value’.

Destination:

console.msg

ERZ010109I Running shutdown program’programName’, from shutdown programlist 1

Explanation: CICS is about to run the shutdownprogram named.

System action: CICS continues phase 1 of shutdown.

User response: None

Destination:

console.msg

ERZ010110I Running shutdown programprogramName, from shutdown programlist 2

Explanation: CICS is about to run the shutdownprogram named.

System action: CICS continues phase 2 of shutdown.

User response: None

Destination:

console.msg

ERZ010111E Usage: cicssrccreate [ -I ] [-r regionName| -s SFSserverName -n serverId -uuserId | -g ppcgwyServerName -nserverId -u userId]

Explanation: cicssrccreate was run with incorrectparameters. One (and only one) of the three optionsmust be supplied.


User response: Run cicssrccreate with correctparameters.

Destination:

stderr

ERZ010112E Unable to locate the CICS productdirectory ’productDirectory’

Explanation: cicssrccreate was unable to find thelocation of the CICS product directory. The CICSproduct has not been successfully installed.


User response: Install the CICS product.

Destination:

stderr

ERZ010113E Region directory ’directoryName’ does notexist

Explanation: cicssrccreate was called to create asubsystem entry for a region which has not beensuccessfully created on the current machine.


User response: Create the region before runningcicssrccreate.

Destination:

stderr

ERZ010114I Creating subsystem ’subsystemName’ forregion ’regionName’

Explanation: cicssrccreate is about to create asubsystem entry ’subsystemName’ for the region’regionName’.

System action: cicssrccreate continues.

User response: None

Destination:

stderr

ERZ010115E Unable to create subsystem’subsystemName’

Explanation: cicssrccreate encountered an errorcreating an entry for the named subsystem.


User response: Look at the previous message for thecause of the error.

Destination:

stderr

ERZ010107W • ERZ010115E


ERZ010116E Region lock file found but not theassociated process for id processName

Explanation: cicsgpid discovered an existing regionlock file which contained a process id. However, onexamination no process for that pid was able to befound. This situation has probably arisen because theregion was terminated unexpectedly during normaloperation. It did not have time to remove the regionlock file.


User response: Remove the region lock file usingcicsrlck.

Destination:

stderr

ERZ010117I CICS is performing a cold start

Explanation: CICS is performing a cold start eitherbecause it was requested or because the region is beingused for the first time.


User response: None

Destination:

console.msg

ERZ010118I CICS is performing an auto start

Explanation: CICS is performing an auto start.


User response: None

Destination:

console.msg

ERZ010119E Not enough memory to set up theenvironment from the regionenvironment file

Explanation: CICS is unable to obtain enough memoryto set up the environment as required.


User response: This message possibly means that theenvironment file is too large. Check that everythingdefined in the environment file is required. If the sizeof the environment file cannot be reduced, increase thevalue of the attribute MaxRegionPool in the RegionDefinition.

Destination:

console.msg

ERZ010120I Completed processing startup orshutdown program list

Explanation: CICS has completed processing one ofthe startup or shutdown program lists.

System action: CICS continues startup or shutdown.

User response: None

Destination:

console.msg

ERZ010121E Unable to perform operation due to atransient error

Explanation: A transient error occurred repeatedlywhile attempting an action.


User response: See message ERZ5723I for furtherinformation.

Destination:

console.msg

ERZ010122E The region has been forcibly terminated

Explanation: CICS has encountered a problem duringregion termination which prevents completion of thenormal termination actions.

System action: CICS forcibly terminates all regionprocesses and removes the region lock file.

User response: Examine previous messages for thecause of the problem.

Destination:

console.msg

ERZ010123E Unable to set the locale or opencatalogue for process ’processName’

Explanation: CICS was unable to set the locale or wasunable to open the message catalogue in the currentlocale.


User response: Check that the locale is definedcorrectly, and that there is a message catalogueavailable for the locale. The locale is taken from theenvironment of the user which requested the operation.The locale categories within the locale can be modifiedby a number of environment variables. Ensure theseenvironment variables contain a valid locale.

Destination:

console.msg

ERZ010116E • ERZ010123E


ERZ010124E Unable to save locale for the process’processName’

Explanation: Was not able to save locale.


User response: CICS possibly ran out of memory.Check that the Region Definition (RD) valueMaxRegionPool is sufficiently large. Increase the value,and restart the region.

Destination:

console.msg

ERZ010125E Unable to obtain locale of the process’processName’

Explanation: CICS was unable to obtain the locale ofthe current process.


User response: The locale is taken from theenvironment of the user which requested the operation.On UNIX the locale categories within the locale can bemodified by a number of environment variables.Ensure these environment variables contain a validlocale.

Destination:

console.msg

ERZ010128E Region ’regionName’ forcibly terminatedafter detection of an unexpected exit

Explanation: The CICS region ’regionName’ terminatedabnormally, not as a result of a system or userrequested shutdown and without completing thenormal shutdown procedure.

System action: Any remaining processes associatedwith the region are terminated and the region lock fileis removed.

User response: Check the previous messages to see ifthere is some reason for the region to have terminatedunexpectedly.

Destination:

console.msg

ERZ010129I CICS startup id: ’regionStartupId’

Explanation: This message logs the unique identifierfor this instantiation of the region. The startupidentifier is used for labelling Open File Descriptors(OFD) on the SFS, and is displayed on the console sothat the system administrator can identify any openOFDs which do not relate to this instantiation of theregion.


User response: None

Destination:

console.msg

ERZ010130I Creating subsystem ’subsystemName’

Explanation: cicssrccreate is about to create asubsystem entry for the subsystem ’subsystemName’.


User response: None

Destination:

stderr

ERZ010131W Subsystem ’subsystemName’, alreadyexists

Explanation: cicssrccreate is not creating an entry forthe subsystem ’subsystemName’ because one alreadyexists.


User response: If you wish to force the creation of theentry for the subsystem ’subsystemName’, destroy thecurrent one using cicsdestroy and retry this operation.

Destination:

stderr

ERZ010132E Usage: cicsclck [-r regionName]

Explanation: cicsclck was invoked with invalidarguments.

System action: cicsclck exits.

User response: Retry the command with the correctsyntax.

Destination:

stderr

ERZ010133E Insufficient authority to createsubsystem ’subsystemName’

Explanation: You do not have sufficient authority torun cicssrccreate.

System action: cicssrccreate terminates.

User response: If you are running on an AIX platformensure that you have read and execute accesspermission for the commands mknotify, rmnotify, andmkssys. Otherwise ensure that you have read andexecute permission for the cicsmkssys command.

Destination:

stderr

ERZ010124E • ERZ010133E


ERZ010134E Insufficient authority to destroysubsystem ’subsystemName’

Explanation: You do not have sufficient authority torun cicssrcdestroy.

System action: cicssrcdestroy terminates.

User response: If you are running on an AIX platformensure that you have read and execute accesspermission for the command rmssys. Otherwise ensurethat you have read and execute permission for thecicsrmssys command.

Destination:

stderr

ERZ010135I CICS region ’regionName’ is beingstarted with locale categories ’localeName’

Explanation: The region ’regionName’ has been startedin locale ’localeName’. The locale is taken from theenvironment of the user associated with the regionprocess. The locale consists of a number of categories.On UNIX, these categories can be modified by usingenvironment variables.


User response: None

Destination:

console.msg

ERZ010136I Creating CICS process ’processName’

Explanation: The CICS process ’processName’ is beingcreated.


User response: None

Destination:

console.msg

ERZ010137I The CICS initialization transaction hasstarted

Explanation: The CICS private transaction thatperforms transactional work at system startup hasbegun.


User response: None

Destination:

console.msg

ERZ010138I The CICS initialization transaction hasended

Explanation: The CICS private transaction thatperforms transactional work at system startup hasended.


User response: None

Destination:

console.msg

ERZ010139I The CICS termination transaction hasstarted

Explanation: The CICS private transaction thatperforms transactional work at system shutdown hasstarted.

System action: CICS continues shutdown.

User response: None

Destination:

console.msg

ERZ010140I The CICS termination transaction hasended

Explanation: The CICS private transaction thatperforms transactional work at system shutdown hasended.


User response: None

Destination:

console.msg

ERZ010141I Application manager now startingMinServer servers

Explanation: The application manager has beenstarted and is now bringing up the number ofapplication servers specified by the value of theMinServer attribute in the Region Definitions.


User response: None

Destination:

console.msg

ERZ010144I Application server serverId started

Explanation: Application server serverId has startedrunning.


User response: None

ERZ010134E • ERZ010144I


Destination:

console.msg

ERZ010145E Unable to create /var/cics_regions/’regionName’/region_lock

Explanation: The CICS command was not able tocreate the lock file for the named region.

System action: The CICS command terminates with anon-zero exit status.

User response: Ensure that the region exists, is ownedby user cics and has read, write and executepermissions for its owner. Ensure that the file system isnot full.

Destination:

stderr

ERZ010146E Cannot create ’fileName’ for region’regionName’

Explanation: CICS was not able to create a lock filefor the named region. A region lock file cannot becreated whilst the region is running or while a majorconfiguration change is being made.

System action: the command terminates.

User response: Retry the command when the regionhas been shut down or when configuration changes arecomplete. Use the contents of the lock file to discoverwhat is happening. A value of ’999999’ in the lock fileindicates that configuration is taking place, any othervalue indicates that a region is running. If the regionlock file exists and no-one is running a region orconfiguring it, cicsrlck can be used to remove theregion lock file. If the lock file does not exist a moreserious problem has occurred. Check that the directoryfor the named region has the required permissions.Ensure that it is owned by user cics and has read, writeand execute permissions for its owner. Ensure that thefile system is not full.

Destination:

console.msg

ERZ010147I Waiting for Application Servers tocomplete

Explanation: CICS is waiting for any remainingApplication Servers to complete before finally shuttingdown the region.

System action: CICS continues shutdown. If after 5minutes on normal shutdown and 2 minutes onimmediate shutdown, the Application Servers have notcompleted, any remaining ones is forcibly terminatedand region shutdown continues.

User response: None

Destination:

console.msg

ERZ010148E CICS self consistency checking failed

Explanation: When checking the integrity of theregion, CICS discovered an inconsistency. Please referto the preceding messages for more details.


User response: If after following the guidelines givenby the preceding messages the problem still persistssave the system dump and contact your supportorganization.

Destination:

console.msg

ERZ010149E User identifier for user name ’userName’could not be found

Explanation: cicssrccreate was unable to obtain theuser identifier for the given user name.


User response: The given user name must exist beforecicssrccreate can be used. Create the user and retry thecommand.

Destination:

stderr

ERZ010150E Directory ’directoryName’ is notaccessible by user ’userName’, or it doesnot exist

Explanation: Either directoryName is not readable,writeable and executable by userName, or directoryNamedoes not exist.


User response: Ensure that directoryName exists andthat userName has read, write and execute permissionsto it.

Destination:

stderr

ERZ010151W Cold start forced as previous cold startdid not complete

Explanation: An auto start was requested but theprevious cold start did not complete. As a result a coldstart is forced.


User response: None

Destination:

ERZ010145E • ERZ010151W


console.msg

ERZ010152I Usage: cicsnotify {-? | subsystemName}

Explanation: This is the usage message for thecicsnotify command.

System action: cicsnotify exits.

User response: None. See the TXSeries Infocenter formore information.

Destination:

stderr

ERZ010153I Application Servers are now beingforcibly terminated

Explanation: CICS is about to forcibly terminate anyApplication Servers that have not yet completed.


User response: None

Destination:

console.msg

ERZ010154I Waiting for Application Manager tocomplete

Explanation: CICS has terminated all of theApplication Servers and is now waiting for theApplication Manager to complete.

System action: CICS continues shutdown. If after 2minutes the Application Manager has not completed itis forcibly terminated and region shutdown continues.

User response: None

Destination:

console.msg

ERZ010155I Application Manager is now beingforcibly terminated

Explanation: CICS is about to forcibly terminate theApplication Manager.


User response: None

Destination:

console.msg

ERZ010156I About to schedule the CICS terminationtransaction

Explanation: CICS is about to schedule the transactionthat performs transactional work during shutdown.

System action: CICS waits for up to 15 minutes for

the termination transaction to be started. The waitoccurs only if there is not an Application Serveravailable to run the transaction. If the transaction is notscheduled immediately message ERZ10139I appears. Ifafter 15 minutes the transaction has not been startedshutdown continues without the transaction havingrun.

User response: An Application Server can be madeavailable by terminating a running transaction.

Destination:

console.msg

ERZ010157W Invalid value for ’registerName’ pool baseregister - defaulting to 0x’registerValue’

Explanation: The value of the ’registerName’ pool baseattribute in the Region Definitions was not valid.

System action: CICS takes the default value for thatregister, and continues processing.

User response: If you do not want to use the defaultvalue change it to a valid one. See TXSeries Infocenter.

Destination:

console.msg

ERZ010158I Taking override for ’registerName’ poolbase register to be 0x’registerOverride’

Explanation: CICS is using the RegionPoolBase orTaskSharedPoolBase attribute specified in the RegionDefinitions.


User response: None

Destination:

console.msg

ERZ010159W Override for ’registerName’ pool baseregister not valid on this platform

Explanation: CICS has detected that you havechanged the value for attribute ’registerName’ in RegionDefinitions (RD), but this attribute is used on AIXplatforms only.

System action: CICS ignores the override andcontinues processing.

User response: Do not specify this attribute in the RD.See TXSeries Infocenter.

Destination:

console.msg

ERZ010152I • ERZ010159W


ERZ010160I Creating CICS process ’processName’ forlistener ’listenerName’

Explanation: The CICS process ’processName’ is beingcreated for the protocol listener ’listenerName’.


User response: None

Destination:

console.msg

ERZ010161E Access to Listener Definition record’listenerName’ was unsuccessful

Explanation: CICS cannot access the ListenerDefinitions (LD) for protocol listener ’listenerName’.


User response: Examine surrounding messages in themessage file for possible causes.

Destination:

console.msg

ERZ010162E Unable to create CICS process’processName’ for listener ’listenerName’

Explanation: CICS was not able to create the process’processName’ for the protocol listener ’listenerName’.


User response: Check that CICS has been installedcorrectly. If the system is heavily loaded, reduce theload by stopping some processes or by restricting themaximum number of Application Servers by updatingthe value of the attribute MaxServer in the RegionDefinition.

Destination:

console.msg

ERZ010163I Waiting for listener ’listenerName’ toinitialize

Explanation: CICS is waiting for initialization of thelistener identified by the protocol listener ’listenerName’.

System action: None

User response: None

Destination:

console.msg

ERZ010164W SNA Listener Definition ’listenerName’ignored

Explanation: CICS has initiated the SNA listener fromthe first SNA protocol Listener Definition. A furtherSNA Listener Definition ’listenerName’ exists which hasbeen ignored.


User response: Delete multiple SNA ListenerDefinitions to eliminate this startup message. Theresource definition can be deleted by using thecicsdelete command. Refer to TXSeries Infocenter formore information.

Destination:

console.msg

ERZ010165I CICS control process ’processName’terminated abnormally

Explanation: One of the CICS control processesterminated abnormally. Preceding messages possiblyindicate the cause of the abnormal termination.

System action: If the process that is terminatingabnormally is not an application server, the region alsoterminates abnormally.

User response: Examine preceding messages toidentify the cause of the abnormal termination.

Destination:

console.msg

ERZ010166I About to set the DB2INSTANCEenvironment variable to ’instanceName’.

Explanation: The value of the environment variableDB2INSTANCE is set to the value of theRDBMSInstance attribute in the Region Definition(RD).


User response: None

Destination:

console.msg

ERZ010167I Region ’Region’ has been configured tosupport a Structured File Server(SFS).

Explanation: Region ’Region’ supports an SFS filesystem.


User response: None

Destination:

console.msg

ERZ010160I • ERZ010167I


ERZ010168I Region ’Region’ has been configured tosupport a Database 2 FileSystem

Explanation: Region ’Region’ supports a Database 2FileSystem.


User response: None

Destination:

console.msg

ERZ010169E Unable to create CICS Listener Managerprocess

Explanation: CICS was not able to create the ListenerManager process.



Destination:

console.msg

ERZ010170I Listener manager now starting recoverylisteners

Explanation: The Listener Manager has been startedand is now starting any listeners which have beendefined to start before recovery.


User response: None

Destination:

console.msg

ERZ010171I Listener manager started ListenerCountrecovery listeners

Explanation: The Listener Manager has startedListenerCount recovery listeners.


User response: None

Destination:

console.msg

ERZ010172I Listener manager now startingnon-recovery listeners

Explanation: The Listener Manager has been startedand is now starting any listeners which have beendefined to start following recovery.


User response: None

Destination:

console.msg

ERZ010173I Listener manager started listenerCountnon-recovery listeners

Explanation: The Listener Manager has startedlistenerCount non-recovery listeners.


User response: None

Destination:

console.msg

ERZ010174E CICS listener ’listenerName’ process’processName’ ended unexpectedly

Explanation: The Listener Manager (cicslm) processdetected the unexpected end of the identified CICSlistener process.



Destination:

console.msg

ERZ010175I CICS listener ’listenerName’ process’processName’ terminated

Explanation: The identified CICS listener process hasterminated and is no longer available for use.


User response: None

Destination:

console.msg

ERZ010176E Listener child process (pid=childPid)terminated unexpectedly

Explanation: The Listener Manager process (cicslm)detected the unexpected termination of a listener childprocess with pid childPid.


User response: Examine previous messages andsymptom records for possible causes of the problem.

Destination:

console.msg

ERZ010168I • ERZ010176E


ERZ010177I Listener child process (pid=childPid)terminated

Explanation: The Listener Manager process (cicslm)detected the termination of a listener child process withpid childPid. The process is unavailable for further use.



Destination:

console.msg

ERZ010178E Unable to allocate region memory whenattempting to start a listener process

Explanation: The Listener Manager process (cicslm)failed to allocate region pool storage when attemptingto start a listener process.


User response: Examine previous messages andsymptom records for possible causes of the problem.Consider increasing the size of the region pool.

Destination:

console.msg

ERZ010179E The Listener Manager received aninvalid request type (RequestType)

Explanation: The Listener Manager process (cicslm)has received an invalid request with value ofRequestType. This is an internal error.

System action: CICS terminates the region.

User response: Save the console output and anydump produced and contact your support organization.

Destination:

console.msg

ERZ010180E Unable to find region ’regionName’

Explanation: The CICS command tried to do somework in varDir/cics_region/’regionName’ but wasunable to find the directory.

System action: The command terminates abnormally.

User response: Ensure that the region exists, is ownedby user cics and has read, write and executepermissions for its owner. Ensure also that you haveinstalled CICS correctly. If you did not specify a regionwith the command, ensure that the cics default regionexists. On Windows NT you can find the drive letter ofthe disk containing the cics_regions directory by usingthe cicsname regions command.

Destination:

stderr

ERZ010181E Unable to write file ’fileName’, errno’errno’

Explanation: The cics command attempted to createand then write to file ’fileName’, but the commandfailed with errno ’errno’.


User response: Check you have the necessarypermissions to create and write to the file in the regionsdirectory. Check also that the file system is not full. Ifthis fails then check errno for more information. Thenretry the command.

Destination:

stderr

ERZ010182E Unable to close file ’fileName’

Explanation: CICS tried to close the file ’fileName’ butwas unable to do so. This is possibly because the filehas been corrupted or because a spurious signalinterrupted the process.


User response: Try the command again. If theproblem persists check the installation of the CICSsystem.

Destination:

stderr

ERZ010183E This copy of CICS is not licensed and isshutting down, reason code: reasonCode

Explanation: The CICS License Manager has not beenable to find a valid license for this copy of CICS. Thismeans that CICS cannot continue to execute and mustshut down immediately.

System action: The region terminates abnormally.

User response: Check the message log for furthermessages indicating the nature of the problem. If this isan Evaluation copy of CICS, then it is only licensed fora limited period. Contact your support organization ifyou require help with licensing this system. If this is aProduction copy of CICS, ensure that the Productionlicense is enrolled. Refer to documentation for furtherinformation.

Destination:

console.msg

ERZ010177I • ERZ010183E


ERZ010184I Region ’Region’ has been configured tosupport an Oracle database as itsFileSystem

Explanation: Region ’Region’ has been configured tomap file control and queue management to an Oracledatabase.


User response: None

Destination:

console.msg

ERZ010185E The region has been configured to useDB2 as its FileSystem but CICS couldnot determine the database instance

Explanation: The CICS regions has been configured touse DB2 for its file and queue management but boththe DB2INSTANCE environment variable and theRDBMSInstance field in the RD stanza are empty. CICScannot determine which database instance is to be usedfor its file system.

System action: CICS abnormally ends the region.

User response: Determine which database instance isto be used for the CICS file control and queuemanagement and set this value in the RDBMSInstancefield in the RD stanza or in the DB2INSTANCEenvironment variable.

Destination:

console.msg

ERZ010186I The region will use DB2 instance’instanceName’

Explanation: The CICS regions has been configured touse DB2 for its file and queue management and hasdetermined from the DB2INSTANCE environmentvariable, that the DB2 instance to use is ’instanceName’.


User response: Check that CICS is using the correctDB2 instance.

Destination:

console.msg

ERZ010187I About to set the ORACLE_SIDenvironment variable to ’instanceName’.

Explanation: The value of the environment variableORACLE_SID is set to the value of theRDBMSInstance attribute in the Region Definition(RD).


User response: None

Destination:

console.msg

ERZ010188E The region has been configured to useOracle as its FileSystem but CICS couldnot determine the database instance

Explanation: The CICS regions has been configured touse Oracle for its file and queue management but boththe ORACLE_SID environment variable and theRDBMSInstance field in the RD stanza are empty. CICScannot determine which database instance is to be usedfor its file system.


User response: Determine which database instance isto be used for the CICS file control and queuemanagement and set this value in the RDBMSInstancefield in the RD stanza or in the ORACLE_SIDenvironment variable.

Destination:

console.msg

ERZ010189I The region will use variable’variableName’ defined as ’variableSetting’

Explanation: The CICS regions has been configured touse Oracle for its file and queue management and hasdetermined from the environment that ’variableName’ isdefined as ’variableSetting’.


User response: Check that CICS is using the correctvalue for ’variableName’.

Destination:

console.msg

ERZ010190I CICS Release Number versionNumberRevision Level revisionLevel

Explanation: The CICS region is starting, using codefrom CICS release versionNumber which is at revisionlevel revisionLevel.

User response: None

Destination:

console.msg

ERZ010191E The region has been configured to useOracle as its FileSystem but CICS couldnot determine the value forORACLE_HOME

Explanation: The CICS region has been configured touse Oracle for its file and queue management but theORACLE_HOME environment variable was not

ERZ010184I • ERZ010191E


defined. CICS cannot determine which database is to beused for its file system.


User response: Determine which database home is tobe used for the CICS file control and queuemanagement, then export the ORACLE_HOMEenvironment variable or define ORACLE_HOME in theCICS region’s environment file.

Destination:

console.msg

ERZ010192W LU0 Listener Definition ’listenerName’ignored

Explanation: CICS has initiated the LU0 listener fromthe first LU0 protocol Listener Definition. A furtherLU0 Listener Definition ’listenerName’ exists which hasbeen ignored.


User response: Delete multiple LU0 ListenerDefinitions to eliminate this startup message. Theresource definition can be deleted by using thecicsdelete command. Refer to TXSeries Infocenter formore information.

Destination:

console.msg

ERZ010193W IIOP Listener Definition ’listenerName’ignored

Explanation: An IIOP Listener Definition’listenerName’ exists which has been ignored, because anIIOP Listener has already been started.


User response: Delete this Listener Definition toeliminate this startup message. Only one IIOP Listenerand one IIOP SSL supported Listener definition canexist within a CICS region. The resource definition canbe deleted by using the cicsdelete command. Refer toTXSeries Infocenter for more information.

Destination:

console.msg

ERZ010194E IIOP Listener Definition error

Explanation: CICS has initiated an IIOP listener withSSL support from an IIOP protocol Listener Definition,but is unable to find a IIOP Listener Definition withoutSSL support.

System action: CICS abnormally terminates the regionwith abend code U1037.

User response: If you require IIOP with SSL support,you must also define an IIOP Listener without SSL

support. The resource definition can be added by usingthe cicsdelete command. Refer to TXSeries Infocenterfor more information.

Destination:

console.msg

ERZ010195E IIOP Listener Definition ’listenerName’ignored

Explanation: CICS has detected an IIOP protocolListener Definition, but this listener type is notsupported for this operating system. Listener Definition’listenerName’ has been ignored.


User response: Delete this Listener Definition toeliminate this startup message. The resource definitioncan be deleted by using the cicsdelete command. Referto TXSeries Infocenter for more information.

Destination:

console.msg

ERZ010196E IIOP SSL Listener Definition’listenerName’ ignored

Explanation: CICS has detected an IIOP protocolListener Definition which requires SSL support, but thisis not supported for this operating system. ListenerDefinition ’listenerName’ has been ignored.


User response: Delete this Listener Definition toeliminate this startup message. The resource definitioncan be deleted by using the cicsdelete command. Referto TXSeries Infocenter for more information.

Destination:

console.msg

ERZ010197E IIOP SSL Listener cannot be supportedwith IIOP version 1.0

Explanation: An IIOP SSL Listener Definition isdefined but the IIOP version for generated objectreferences is set to 1.0. IIOP version 1.0 does notsupport transmission of security component identifiersand is therefore unable to negotiate the use of SSL onIIOP flows. If an IIOP SSL Listener is required, theRegion Definition attribute IIOPObjrefsVersion mustbe set to ″1.1″ to enable security component identifiersupport on IIOP flows.


User response: Define the IIOP version for generatedobject references to ″1.1″ if you require an IIOP SSLListener. Refer to TXSeries Infocenter for moreinformation.

ERZ010192W • ERZ010197E


Destination:

console.msg

ERZ010198E IIOP work load managed SSLconfiguration error

Explanation: An IIOP work load managed SSL port isdefined but no IIOP SSL Listener has been defined forthis region. The Region Definition attributeIIOPGroupSSLPort defines the IIOP work loadmanaged SSL port.


User response: Define an IIOP SSL Listener if youintend to support an IIOP work load managed SSLconfiguration. Refer to TXSeries Infocenter for moreinformation. Otherwise, unset the Region Definitionattribute IIOPGroupSSLPort.

Destination:

console.msg

ERZ010199I CICS Interim Fix ’interimfixes’ detected

Explanation: The Interim Fix that is listed in themessage is installed.

User response: None

Destination:

console

ERZ010200I CICS observed an increase in the size ofthe data segment for application serverserverId. The current data segment size isMemSizeCur

Explanation: Memory usage for a given applicationserver has increased.

System action:

User response: Examine previous messages, symptomrecords and running applications for possible causes ofthe problem.

Destination:

console

ERZ010201I Monitoring of the data segment isenabled for application server processeswithServerMemCheckInterval=’ServerMemCheckInterval’andServerMemCheckLimit=’ServerMemCheckLimit’

Explanation: Memory growth monitoring is switchedon.

System action:

User response: None

Destination:

console

ERZ010203I Region is configured to use EAMmodule for authentication

Explanation: The region configuration shows that anExternal Authentication Module should be loaded byCICS to perform user authentication.



Destination:

console.msg

ERZ010204E Peer listener listenerName failed toautoinstall

Explanation: The listener could not be autoinstalled.


User response: See previous messages for possibleautoinstall failure reasons.

Destination:

console.msg

ERZ010205I CICS diagnostic patch ’diagpatch’detected

Explanation: The diagnostic patch that is listed in themessage is installed.

System action:

User response: None

Destination:

console

ERZ010206W Supported JDK Version is not installedin this machine

Explanation: JDK Version supported for this release isnot installed on this machine.

System action:

User response: Check whether JDK Version installedon this machine and the Supported Java Version forthis release of CICS matches.If not install the JDKversion specified in the CICS Supported OperatingEnvironment Page.

Destination:

console

ERZ010198E • ERZ010206W


ERZ010207I CICS region running on host ’HostName’has been configured for WLMenvironment″

Explanation: Region has been configured to take partin WLM on the particular host name

System action:

User response:

Destination:

console

ERZ010208E Format error:The value’RDAttributeValueRDAttributeName’assigned to the attribute’RDAttributeValueRDAttributeName’cannot be parsed

Explanation: The value ’RDAttributeValue’ set to thespecified ’RDAttribute’ is invalid

System action: Region fails to inform correctinformation to WLM. This might affect the overallWLM performance. Many Abends may occur on AORside.

User response: Assign the correct value in the RDstanza

Destination:

console

ERZ010209E CICS region failed to contact’cicswlmlsnr’ on host ’HostNameerrorcode’,reason code ’HostNameerrorcode’

Explanation: CICS fails to communicate to WLM. iftwo or more cicscp stop commands are issued withinsmall time interval, it results in this error. As part ofthis some tra nsactions may abend. If thiscommunication does not happen, WLM still believesthat this AOR is still running and many communicationrelated abends will occur in COR side too.

System action: CICS region fails to communicate withWLM listener. Additional communication related errorswill be logged in the respective COR’s console.

User response: Ensure WLM listener (cicswlmlsnr) isrunning through cicswlm command and ensure TCP/IPaddress and port specified in RD are correct.

Destination:

console

ERZ010210W CICS region timed-out waiting forresponse from ’cicswlmlsnr’ ’HostName’

Explanation: In normal region shutdown the region(AOR) sends a message to WLM indicating that it isshutting down and awaits for an acknowledgement

(No such acknowledge is flow from WLM in case ofimmediate shutdown). The said response from WLMlistener to CICS region (AOR) is to minimize thenumber of transaction abends or communication failures during normal shutdown of CICS region.

System action: CICS Continues

User response: Ensure WLM listener (cicswlmlsnr) isrunning

Destination:

console

ERZ010211W The RD stanza attribute’RDAttributeName’ value =’Value’ cannotexceed the attribute ’RDAttributeName’value =’Value’

Explanation: CICS region RD stanza attributeWLMMaxServer/WLMMinServer value cannot exceedregion attribute MaxServer/MinServer respectively. Inthis case the WLMMaxServer/ WLMMinServer will bereset to 0/0 respectively.

System action: CICS region throws an error message.

User response: Ensure WLMMaxServer/WLMMinServer does not exceed the value specified inthe correspondng MaxServer/MinServer values.

Destination:

console

ERZ010212E Recovery failed for application serverserverId

Explanation: The Application Manager (cicsam)process detected that recovery failed for a applicationserver serverId.

System action: Shutdowns the region.


Destination:

console.msg

ERZ010213I Protocol sequence ’protocolsequence’ issupported

Explanation: none

System action:

User response: none

Destination:

console.msg

ERZ010207I • ERZ010213I


ERZ011001E Access to terminal record for terminal’termId’ was unsuccessful.

Explanation: CICS cannot access the TerminalDefinitions (WD) record for terminal ’termId’.

System action: The transaction terminates with abendcode A11W.


Destination:

CSMT

ERZ011002E Storage allocation request from TaskPrivate Pool was unsuccessful.

Explanation: CICS is short of Task Private storage anda storage allocation request was unable to be satisfied.

System action: The transaction is terminated withabend code A11M.

User response: Try running the transaction again. Ifthe transaction is still unsuccessful, this is possiblybecause another transaction is using a lot of storage.Ask the System Administrator to check for any suchtransactions.

Destination:

CSMT

ERZ011003I Processing terminal installation requestfor netname ’netName’ from user’userName’ on host ’hostName’.

Explanation: CICS has started to install the terminalwith netname ’netName’ on behalf of user ’userName’.

System action: Terminal installation continues.

User response: None

Destination:

CSMT

ERZ011004I Processing terminal installation requestfor device type ’deviceType’ from user’userName’ on host ’hostName’ usingdevice ’devId’.

Explanation: CICS has started to autoinstall a terminalwith device type ’deviceType’ on behalf of user’userName’.

System action: Terminal installation continues.

User response: None

Destination:

CSMT

ERZ011005I Terminal ’termId’ does not exist.

Explanation: A request to stop a transaction onterminal ’termId’ was rejected because the terminal doesnot exist. The terminal was uninstalled after the requestto stop the transaction was made, but before therequest was scheduled.

System action: CICS ignores the stop request.

User response: None

Destination:

CSMT

ERZ011006E Terminal process does not support sizespecified in terminal definition’deviceName’

Explanation: The terminal process attempting toconnect to the region does not support the terminal sizeincluded in the selected terminal definition.

System action: The install fails.

User response: Either use a more recent level of theterminal executable or connect to the region using adifferent model identifier or netname.

Destination:

CSMT

ERZ011007I Terminal ’termId’ installation completefor user ’userName’, netname ’netName’.

Explanation: A terminal defined in the TerminalDefinitions (WD) has connected to the region andsuccessfully installed.

System action: CICS can communicate with theterminal.

User response: None

Destination:

CSMT

ERZ011008W Terminal ’termId’ was unable to saveterminal details to Temporary StorageQueue (TSQ) ’TSQname’.

Explanation: Terminal ’termId’ was successfullyinstalled, but was unable to save its details to TSQ’TSQname’ to enable the terminal definition to berecovered in the event of abnormal shutdown. This canpossibly occur if terminals are installed while CICS ischecking that existing terminals are still active. If this isthe case, the problem is likely to affect only terminalinstallations performed within the next few moments.

System action: The installation completes successfully,but the terminal is not recovered if an abnormalshutdown occurs.

ERZ011001E • ERZ011008W


User response: Check that the file server is available,and the file used for recoverable TSQs exists on theserver. If recovery of the terminal is required, sign theterminal off and attempt the connection again after ashort delay.

Destination:

CSMT

ERZ011009E Unable to autoinstall terminal for devicetype ’deviceType’.

Explanation: A terminal has connected to the regionand made an unsuccessful attempt to autoinstall.

System action: The installation operation terminatesabnormally.

User response: Examine the previous messages todetermine why the autoinstall was unsuccessful.

Destination:

CSMT

ERZ011010I Terminal ’termId’ autoinstall completefor user ’userName’, netname ’netName’,model ’modelId’.

Explanation: A terminal has connected to the regionand was successfully autoinstalled.


User response: None

Destination:

CSMT

ERZ011011E Uninstall of terminal ’termId’ wasunsuccessful.

Explanation: A terminal has disconnected from theregion but the uninstall was unsuccessful.

System action: The transaction terminates abnormally.CICS ceases to communicate with the terminal.

User response: Examine previous messages todetermine why the terminal was unable to be installed.

Destination:

CSMT

ERZ011012I Terminal ’termId’ with netname ’netName’has been uninstalled.

Explanation: A terminal has disconnected from theregion.

System action: CICS ceases to communicate with theterminal. The terminal client terminates.

User response: None

Destination:

CSMT

ERZ011013E Initialization for terminal ’termId’ wasunsuccessful.

Explanation: CICS was unable to initialize the CICSterminal component.

System action: CICS terminates abnormally the regionwith code U1101.

User response: Examine previous messages to see ifregion is short of storage.

Destination:

CSMT

ERZ011014E Storage allocation request from TaskShared Pool was unsuccessful.

Explanation: CICS is short of Task Shared storage anda storage allocation request was unable to be satisfied.

System action: If this occurs during regioninitialization, then the region terminates abnormally;otherwise the transaction continues, but the terminalinitialization operation was unsuccessful.


Destination:

CSMT

ERZ011015E Failure in Remote Procedure Call toinstalling terminal: ’errorText’.

Explanation: CICS has processed a request to install aterminal but a failure has occurred when responding tothe terminal process that made the request. The reasonfor the failure is given in ’errorText’.

System action: Terminal installation terminatesabnormally.

User response: Check the reason for the failurespecified in ’errorText’ and correct the problem. If thefailure was caused by an communication timeout, tryagain when the system is less busy. If the problempersists, please report details to your supportorganization.

Destination:

CSMT

ERZ011009E • ERZ011015E


ERZ011016E Terminal ’termId’ with netname ’netName’is out of service.

Explanation: The user has tried to install a terminalwith netname ’netName’, but its Terminal Definition(WD) is marked as out of service.

System action: Terminal installation terminates withabend code A11T.

User response: Try installing using another netnameor use the CEMT transaction to set the terminal back inservice.

Destination:

CSMT

ERZ011017E No terminal model for device type’deviceType’.

Explanation: A terminal with TERM=’deviceType’ hasattempted to autoinstall, but was unsuccessful becausethere are no terminal models defined in the TerminalDefinitions (WD) with DevType=’deviceType’. Thedevice type is obtained from the -m option on thecicsterm command, from the CICSTERM or TERMenvironment variables.

System action: Autoinstall terminates with abend codeA11N.

User response: Retry the command specifying adevice type that matches the DevType entry in theTerminal Definitions (WD), or add an entry to the WDto match the device type specified. See the TXSeriesInfocenter for more information.

Destination:

CSMT

ERZ011018I Processing terminal autoinstall requestfrom user ’userName’ on host ’hostName’.

Explanation: CICS has started to autoinstall a terminalon behalf of user ’userName’.

System action: Terminal autoinstall continues.

User response: None

Destination:

CSMT

ERZ011019E ... ’termId’ not recovered.

Explanation: CICS is performing an automatic startand cannot recover the Terminal Definition (WD) forterminal ’termId’ from a Temporary Storage Queue.

System action: CICS automatic start continues, but theterminal is not recovered.

User response: Check that the file server is available,

and the file used for recoverable TSQs exists on theserver.

Destination:

CSMT

ERZ011020E Unable to generate unique netname forterminal autoinstall.

Explanation: A terminal has connected to the regionand attempted to autoinstall, but was unsuccessfulbecause CICS was unable to generate a uniquenetname. This is only likely to occur when a very largenumber of terminals are defined in the TerminalDefinitions (WD) or have autoinstalled to the region.

System action: Autoinstall terminates abnormally.

User response: Examine the WD and use CEMTinquire terminal to determine how many terminals areconnected to the region. Delete any unwanteddefinitions and try again.

Destination:

CSMT

ERZ011021E Terminal installation for netname’netName’ was unsuccessful.

Explanation: A terminal has connected to the regionbut was unable to be installed using netname’netName’.

System action: Terminal installation terminatesabnormally.

User response: Examine the previous messages in themessage file to determine why the installation wasunsuccessful.

Destination:

CSMT

ERZ011022E Netname ’netName’ does not exist in theTerminal Definitions (WD).

Explanation: A terminal has connected to the regionbut was unable to be installed using netname ’netName’because there is no terminal definition with netname’netName’ in the WD.

System action: Terminal installation terminates withabend code A11F.

User response: Add an entry to the WD or install theterminal using a terminal definition already defined inthe WD.

Destination:

CSMT

ERZ011016E • ERZ011022E


ERZ011023E Terminal ’termId’ with netname ’netName’defines an autoinstalled or surrogateterminal.

Explanation: A terminal has connected to the regionbut was unable to be installed using netname ’netName’because this netname is in use by an autoinstalledterminal or by a surrogate terminal.


User response: Install using a different netname orinvestigate why the netname is being used by anautoinstalled terminal or surrogate terminal.

Destination:

CSMT

ERZ011024E Terminal ’termId’ with netname ’netName’is a remote terminal.

Explanation: A terminal has connected to the regionbut was unable to be installed using netname ’netName’because the Terminal Definition (WD) for this netnamedefines a remote terminal.


User response: Install using a different netname ormodify the WD to define the termid as a local terminal.

Destination:

CSMT

ERZ011025E Terminal ’termId’ with netname ’netName’is a printer.

Explanation: A terminal has connected to the regionbut was unable to be installed using netname ’netName’because the Terminal Definition (WD) for this netnamedefines a printer.

System action: Terminal installation is terminatedwith abend code A11P.

User response: Retry the command specifying thenetname of a WD entry that defines a terminal orchange the WD entry for this netname to define aterminal instead of a printer.

Destination:

CSMT

ERZ011026E Terminal ’termId’ with netname ’netName’is already installed.

Explanation: A terminal has connected to the regionbut was unable to be installed using netname ’netName’because a terminal is already installed using thisnetname.

System action: Terminal installation terminates withabend code A11B.

User response: Install using either a differentnetname, no netname, or a model name.

Destination:

CSMT

ERZ011027E Terminal ’termId’ with netname ’netName’is in use by a transaction that is beingpurged.

Explanation: A terminal has connected to the regionbut was unable to be installed using netname ’netName’because a terminal is already installed using thisnetname. However, the transaction using this terminalwas requested to complete.

System action: Terminal installation terminates withabend code A11B.

User response: Allow time for the transaction tocomplete and then try again.

Destination:

CSMT

ERZ011028E CICS was unable to run autoinstalluser-exit program.

Explanation: A terminal autoinstall or uninstalloperation cannot run the autoinstall user-exit program.

System action: Autoinstall/uninstall terminates withabend code A11U.

User response: Check that the CICS privatetransaction CHAT is defined in the TransactionDefinitions (TD), and that the corresponding programis defined in the Program Definitions (PD), exists at thepathname specified and is executable by CICS.

Destination:

CSMT

ERZ011029E Bad terminal model ’modelName’ hasbeen selected.

Explanation: The autoinstall user-exit program hasselected a terminal model that was not in the listsupplied to it.

System action: Terminal installation terminates withabend code A11U.

User response: If this installation of CICS has replacedthe autoinstall user-exit program, check the programfor coding errors; otherwise report the problem to yoursupport organization.

Destination:

CSMT

ERZ011023E • ERZ011029E


ERZ011030E Terminal model ’modelName’ has beendeleted from Terminal Definitions(WD).

Explanation: The terminal model ’modelName’ selectedby the autoinstall user-exit program was deleted fromthe Terminal Definitions (WD).

System action: Terminal autoinstall terminates withabend code A11U.

User response: Try again. Someone possibly deletedthe terminal model ’modelName’ from the TerminalDefinitions (WD) while you were attempting toautoinstall.

Destination:

CSMT

ERZ011031E Sense code ’senseCode’ received fromterminal ’termId’.

Explanation: The terminal has received a bad 3270data stream and has returned a sense code to theregion.

System action: CICS continues processing. Theterminal rejects the remainder of the data stream.

User response: Check that the datastream sent toterminal does not contain any unsupported or illegal3270 commands and that all buffer addresses are inrange of the screen size.

Destination:

CSMT

ERZ011032E Terminal autoinstall rejected byuser-exit program.

Explanation: A terminal has connected to the regionand attempted to autoinstall, but was rejected by theautoinstall user-exit program.

System action: Terminal autoinstall terminatesabnormally.

User response: If this installation of CICS has replacedthe autoinstall user-exit program, investigate why theautoinstall was rejected; otherwise report the problemto your support organization.

Destination:

CSMT

ERZ011035E Terminal ’termId’ is set to rejectAutomatic Transaction Initiation (ATI)requests.

Explanation: A request to run an ATI job on terminal’termId’ was rejected because the terminal is set to rejectATI requests.

System action: CICS continues without running thetransaction.

User response: Either use CEMT to enable theterminal to initiate ATI requests, or run the transactionagainst another terminal.

Destination:

CSMT

ERZ011036E Terminal ’termId’ is not installed.

Explanation: CICS tried to start an AutomaticTransaction Initiation (ATI) job but was unsuccessfulbecause terminal ’termId’ is defined in the TerminalDefinitions (WD), but was not installed.

System action: CICS continues and runs thetransaction when the terminal is installed.

User response: Install the terminal, and the ATIrequest runs.

Destination:

CSMT

ERZ011037E CICS could not contact terminal ’termId’.

Explanation: CICS tried to start an AutomaticTransaction Initiation (ATI) job but was unsuccessfulbecause it was unable to communicate with terminal’termId’.


User response: Use CEMT to purge the terminal andthen reinstall it.

Destination:

CSMT

ERZ011038E CICS was unable to start transaction’transId’ against terminal ’termId’ for user’userId’ .

Explanation: An Automatic Transaction Initiation(ATI) request for transaction ’transId’ on terminal’termId’ was rejected.


User response: Examine the previous messages in themessage file for more information about this condition.

Destination:

CSMT

ERZ011030E • ERZ011038E


ERZ011039W CICS was unable to write its terminaldetails to the Temporary Storage Queue’TSQname’ for terminal ’termId’.

Explanation: Terminal ’termId’ has successfullyinstalled, but was unable to save its details to the firstrecord of the Temporary Storage Queue (TSQ)’TSQname’. This record is normally used to enable theterminal definition to be recovered following abnormalshutdown.

System action: The installation completes successfully,but the wrong terminal details are recovered followingabnormal shutdown.

User response: Check that the file server is available,and the file used for recoverable TSQs exists on theserver.

Destination:

CSMT

ERZ011040W CICS was unable to delete TemporaryStorage Queue ’TSQname’ whenuninstalling terminal ’termId’.

Explanation: A terminal has successfully uninstalled,but was unable to delete the Temporary Storage Queue(TSQ) ’TSQname’ that holds details allowing theterminal definition to be recovered following abnormalshutdown.

System action: The uninstall completes successfully,but if the TSQ exists, the system attempts to recoverthe terminal definition following abnormal shutdown.

User response: Check that the file server is available,and the file used for recoverable TSQs exists on theserver.

Destination:

CSMT

ERZ011042E Storage allocation request from RegionPool was unsuccessful.

Explanation: CICS is short of Region storage and astorage allocation request was unable to be satisfied.

System action: If this occurs during regioninitialization, then the region terminates abnormally;otherwise the transaction continues, but the terminalinitialization operation was unsuccessful.


Destination:

CSMT

ERZ011043I Terminal recovered after region restart.

Explanation: CICS was autostarted and hassuccessfully reattached to your terminal. The terminalis again ready for use.

System action: None

User response: None

Destination:

stderr

ERZ011044I Attempting to recover terminal ’termId’...

Explanation: CICS is performing an auto-start and isattempting to reattach the specified terminal. If theterminal no longer exists, there is a short delay untilthe attempt to contact it times out.

System action: CICS attempts to contact the terminal.

User response: None

Destination:

CSMT

ERZ011045I ... ’termId’ recovered successfully.

Explanation: CICS is performing an automatic startand has successfully reattached the terminal.

System action: Automatic start continues.

User response: None

Destination:

CSMT

ERZ011046W ... ’termId’ timed-out -- terminal notrecovered.

Explanation: CICS is performing an automatic startand has not received any response from the terminal.

System action: The terminal is not recovered.Automatic start continues.

User response: None

Destination:

CSMT

ERZ011047W ... ’termId’ data unavailable -- recoverypostponed.

Explanation: CICS is performing an automatic startand cannot access the Temporary Storage Queuecontaining the terminal recovery data. Terminalrecovery is postponed until an Automatic TransactionInitiation (ATI) request is processed for the terminal.

System action: Terminal recovery is postponed.Automatic start continues.

ERZ011039W • ERZ011047W


User response: None

Destination:

CSMT

ERZ011050I Usage: cicslterm [-?] [-r regionName] [-nnetName] [-m modelId] [-t transaction][-A animatortty] [-T animatorTERM] [-hhostList]

Explanation: cicsterm was invoked with incorrectarguments. This message gives a summary of theoptions available. It can also be produced by giving the-? option.

System action: cicsterm terminates.

User response: Invoke cicsterm with correctparameters. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ011051I Usage: cicstermp [-?] -r regionName -nnetName [-f font] [-M paperType] [-pprinterType] [-P printCommand] [-R] [-sfontSize] [-t transaction] [-h hostList][-S]

Explanation: cicstermp was invoked with incorrectarguments. This message gives a summary of theoptions available. It can also be produced by giving the-? option.

System action: cicstermp terminates

User response: Invoke cicstermp with correctparameters. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ011052E Illegal option -optionName.

Explanation: The option -optionName is not valid.

System action: cicsterm/cicstermp terminates.

User response: Issue the command with correctparameters as shown in the following usage message.

Destination:

stderr

ERZ011053E cicstermp requires both -n netName and-r regionName parameters.

Explanation: cicstermp was invoked withoutspecifying the mandatory parameters -n netName and-r regionName.

System action: cicstermp terminates.

User response: Invoke cicstermp with both the -n and-r options. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ011054E Display area is too small for menu.

Explanation: cicsterm requires a minimum screendepth of 12 lines to display the region menu.


User response: Increase the size of the display area.

Destination:

stderr

ERZ011055E Could not read 3270keys file ’keysFile’while processing ’topKeysFile’.

Explanation: cicsterm was processing the 3270keys file’topKeysFile’ but either was unable to read the 3270keysfile ’keysFile’ or opening that file exceeded themaximum file nesting limit.


User response: Check that the file exists and isreadable; also ensure that no ″load″ statement in thisfile (or in previous files that were possibly loaded fromkeys file) specifies a file that was already loaded, asthis recursion causes the maximum nesting depth to beexceeded.

Destination:

stderr

ERZ011056E Unrecognized keyword ’keyword’ in3270keys file.

Explanation: cicsterm is processing the 3270keys file(or one loaded from it) and has encountered thekeyword ’keyword’ that is not valid. Valid keywords are:bind, load, print, if and else.

System action: cicsterm terminates

User response: Correct the 3270keys file containingthe unrecognized keyword.

Destination:

stderr

ERZ011057E Unrecognized binding ’name’ in3270keys file.

Explanation: cicsterm is processing the 3270keys file(or one loaded from it) and has encountered thekeyword bind, followed by the binding ’name’ that isnot a valid binding name. Valid bindings include:delete, down, eraseeof, enter and high_prot.

ERZ011050I • ERZ011057E



User response: Correct the 3270keys file containingthe unrecognized binding.

Destination:

stderr

ERZ011058E The option -option requires an argument.

Explanation: A required argument was not suppliedfor the option -’option’.


User response: Add the required argument.

Destination:

stderr

ERZ011059E cicslterm initialization was unsuccessful.

Explanation: cicsterm or cicstermp was unable toinitialize due to memory allocation or operating systemcall failure.


User response: Ensure that cicssetupclients was runand that there is a valid keytab file invarDir/cics_clients.

Destination:

stderr

ERZ011060I Searching for available regions. Pleasewait.

Explanation: cicsterm is waiting for a list of regionsbefore it displays the region menu.

System action: cicsterm continues to search foravailable regions.

User response: Wait until the region menu appears oran error message is issued.

Destination:

stderr

ERZ011061E No regions available.

Explanation: cicsterm was unable to find anyavailable regions.


User response: Ensure that at least one region isrunning and check the region startup messages to see ifany problems were encountered trying to register theregion with the nameservice.

Destination:

stderr

ERZ011062I Connecting to region ’regionName’.

Explanation: cicsterm or cicstermp has started toconnect to region ’regionName’.

System action: cicsterm/cicstermp continuesconnecting to the region.

User response: Wait until connection is successful oruntil an error message is issued.

Destination:

stderr

ERZ011063E Connection to region ’regionName’ wasunsuccessful - ’reason’.

Explanation: cicsterm was attempting to contact theregion ’regionName’, but was unsuccessful for the givenreason.


User response: Ensure that the region exists and isrunning.

Destination:

stderr

ERZ011064I Unrecognized color ’color’ in 3270keysfile.

Explanation: cicsterm is processing the 3270keys file(or one loaded from it) and has encountered a bindingthat it expects to be followed by a color. However’color’ is not a valid color. Valid colors are: black, blue,brown, cyan, green, magenta, red and white.

System action: cicsterm continues using the defaultcolor.

User response: Correct the 3270keys file containingthe unrecognized color.

Destination:

stderr

ERZ011065I No help available about ’subject’.

Explanation: cicsterm has received a request from theattached CICS transaction to display help on the subject’subject’, but cicsterm cannot obtain the requested helpfrom the information subsystem.

System action: cicsterm continues processing.

User response: Check that the CICS informationsubsystem is installed on the machine runningcicsterm.

Destination:

stderr

ERZ011058E • ERZ011065I


ERZ011066E Transaction ’transId’ rejected - ’reason’.

Explanation: The transaction ’transId’ was submittedto the Transaction Scheduler (TS), but the TS rejectedthe request for the reason given in ’reason’.

System action: CICS does not run the transaction. Theterminal is ready to submit another transaction.

User response: Check that you entered the correcttransaction name. Check that transaction ’transId’ iscorrectly defined in the Transaction Definitions (TD).Also check other messages for signs of problems withthe TS.

Destination:

stderr

ERZ011067E The transaction ’transId’ has terminatedwith abend code ’abendCode’.

Explanation: The transaction ’transId’ has terminatedabnormally.

System action: The transaction terminates abnormally.If the transaction that abended was the CHATtransaction, then the terminal installation fails and theterminal is not connected to CICS. If any othertransaction abends, the terminal is ready to submitanother transaction.

User response: Check CICS documentation or thetransaction documentation for the meaning of theabnormal termination code.

Destination:

stderr

ERZ011068E Cannot list available Regions - ’reason’.

Explanation: cicsterm is unable to get a list ofavailable regions from the name service for the reasongiven in ’reason’.


User response: Ensure that you have the requiredpermissions.

Destination:

stderr

ERZ011070I cicslterm terminated (region shutdown).

Explanation: cicsterm or cicstermp has terminatedbecause the region is being shut down.

System action: CICS continues to shut down;cicsterm/cicstermp terminates.

User response: Wait for the region to be restarted orconnect to another region.

Destination:

stderr

ERZ011071I cicslterm terminated (terminaloutservice).

Explanation: cicsterm or cicstermp has terminatedbecause the terminal was set out of service.


User response: Ask the System Administrator to putthe terminal back into service, or install as a differentterminal.

Destination:

stderr

ERZ011072I cicslterm terminated (networkcredentials expired).

Explanation: cicsterm or cicstermp has terminatedbecause the network credentials have expired.


User response: Refresh your credentials and theninvoke another cicsterm or cicstermp. If this fails checkthat there is a valid keytab file in varDir/cics_clients. Ifthere is not a valid keytab file, run the cicssetupclientscommand.

Destination:

stderr

ERZ011073W Region name is too long - truncated to’regionName’.

Explanation: cicsterm or cicstermp has truncated yourregion name because it contained too many characters.

System action: cicsterm/cicstermp attempts toconnect to ’regionName’.

User response: Invoke cicsterm or cicstermpspecifying a valid region name.

Destination:

stderr

ERZ011074W Netname is too long - truncated to’netName’.

Explanation: cicsterm or cicstermp has truncated yournetname because it contained too many characters.

System action: cicsterm/cicstermp attempts to installyour terminal with netname ’netName’.

User response: Invoke cicsterm or cicstermp with avalid netname.

Destination:

stderr

ERZ011066E • ERZ011074W


ERZ011077E The printer options -f, -M, -R and -s canonly be used if POSTSCRIPT isspecified for option -p.

Explanation: cicstermp was invoked with mutuallyexclusive options.


User response: Invoke cicstermp with correct options.See the TXSeries Infocenter for more information.

Destination:

stderr

ERZ011080E Print command ’printCommand’ wasunsuccessful.

Explanation: cicstermp tried to print its temporary fileusing ’printCommand’, but it was unable to execute thecommand.

System action: cicstermp continues without printingthe file.

User response: If you have specified your own printcommand using the -P option of cicstermp, check thatthe program exists, is on the current path and isexecutable.

Destination:

stderr

ERZ011081E Print command ’printCommand’terminated abnormally.

Explanation: cicstermp tried to print its temporary fileusing the command ’printCommand’, but the commandterminated abnormally.

System action: cicstermp continues; however, the filewas possibly not printed.

User response: If you have specified your own printcommand using the -P option of cicstermp, check thatthe command is correct and returns an exit code of zerowhen it succeeds. Also check that the print spooler (ifany) specified by the print command ’printCommand’ iscurrently operational.

Destination:

stderr

ERZ011082E Unable to access print spool file’fileName’.

Explanation: cicstermp tried to append print data tothe temporary file ’fileName’, but was unsuccessful.

System action: cicstermp continues; however, theprint data was not appended.

User response: Check that the directory of the file’fileName’ has permissions that allow file creation and

that the file system is not full.

Destination:

stderr

ERZ011083I Installed as printer ’termId’, netname’netName’.

Explanation: cicstermp was installed as a printerusing the specified termid and netname.

System action: cicstermp continues.

User response: None

Destination:

stderr

ERZ011088E Install of hard-coded terminal definitionfor netname ’netName’ already inprogress

Explanation: A previous request to install ahard-coded terminal definition has not yet completed.This is possibly due to multiple requests to install thesame definition being submitted, by typing cicstermfollowed by ctrl-C. cicsterm does not pass ctrl-Crequests from the CICS client to the server until aftercicsterm has successfully completed. This is generally asymptom of a performance problem.

System action: CICS terminates the CICS-privatetransaction CHAT as another CHAT is already inprogress.

User response: Investigate why the terminal user isgetting slow responses. Check that CICS is running bysubmitting a transaction from an already installedterminal. Check that autoinstall is functioning correctly.In particular, check that there are no resourceconstraints for the machine, that no CICS system limitswere hit, that there are no unexpected long runningtasks and examine the console log for unusualmessages that can possibly indicate either a CICSsystem problem or a problem with the user’s terminal.

Destination:

console.msg

ERZ011099E Unexpected exception ’exceptionName’received.

Explanation: cicsterm or cicstermp received anunexpected exception and has terminated.


User response: Please report details of this problem toyour support organization.

Destination:

stderr

ERZ011077E • ERZ011099E


ERZ011100E Printer with netname ’netName’ is aterminal.

Explanation: A printer has connected to the region butwas unable to be installed using netname ’netName’because the Terminal Definition (WD) for this netnamedefines a terminal.

System action: Terminal installation is terminatedwith abend code A11P.

User response: Retry the command specifying thenetname of a WD entry that defines a printer or changethe WD entry for this netname to define a printerinstead of a terminal.

Destination:

CSMT

ERZ011101E Invalid key code.

Explanation: cicsterm has detected an error whilereceiving a key code from the operating system.


User response: Retry the command. If the problempersists contact your support organization.

Destination:

stderr

ERZ011102I Searching for regions on ’machineName’

Explanation: cicsterm is attempting to find CICSregions. The terminal is now searching on machine’machineName’.

System action: cicsterm continues.

User response: No reponse is necessary.

Destination:

stderr

ERZ011103W Failed to contact CICS RPC listener on’machineName’: ’reason’

Explanation: cicsterm is attempting to find CICSregions.

System action: cicsterm continues but does not listany CICS regions from machine ’machineName’.

User response: Check that the processes are allstarted.

Destination:

stderr

ERZ011104I Warnings displayed. Hit enter tocontinue

Explanation: cicsterm has displayed warnings relatingto attempts to locate CICS regions on one or moremachines. These messages are displayed until the userhits Enter.

System action: cicsterm continues after Enter is hit.

User response: Respond to the warnings displayedand then hit Enter.

Destination:

stderr

ERZ012000I Sign-on is complete

Explanation: CICS verified the userid and passwordgiven to the CESN transaction.

System action: CICS verifies further transactionssubmitted at the terminal against your security keys.

User response: None. This message is for informationonly.

Destination:

terminal

ERZ012001I Sign-off is complete

Explanation: On completion of the CESF transaction,CICS has successfully signed you off the system.

System action: If the routing transaction is not ineffect, the CICS terminal terminates shortly afterdisplaying the message. If the routing transaction is ineffect, CICS verifies further transactions submitted fromthe terminal against the security keys in effect beforethe routing transaction was submitted.


Destination:

terminal

ERZ012002I Signon at netname ’netName’ by user’userName’ is complete




Destination:

console.msg

ERZ011100E • ERZ012002I


ERZ012003E Invalid sign-on attempt

Explanation: You attempted to sign-on, but either theuserid or password is invalid.

System action: CICS continues to verify furthertransactions against the security keys associated withthe userid used for the terminal autoinstall. For CICSon Windows NT via the IBM Clients or cicslterm thatis the default userid.

User response: Invoke CESN again and supply thecorrect userid and password.

Destination:

terminal

ERZ012004I Sign-on is complete. Password has beenchanged.

Explanation: CICS verified the userid and passwordgiven to the CESN transaction. CICS also responded toa request to change the signon password.

System action: CICS verifies further transactionssubmitted at the terminal against your security keys.All new signon attempts require the use of the newpassword.


Destination:

terminal

ERZ012005I Signon at netname ’netName’ by user’userName’ is complete. Password hasbeen changed.




Destination:

console.msg

ERZ012007W Sign-off is complete. GOODNIGHTignored when using routing transaction.

Explanation: You signed off from the system to whichthe sign-off transaction was routed. CICS ignores theGOODNIGHT option in this case.

System action: CICS verifies further transactionssubmitted from your terminal against the security keysin effect before the routing transaction was submitted.

User response: CANCEL the routing session andsign-off from the local system using CESF if you wish

to terminate your CICS session.

Destination:

terminal

ERZ012008I You have cancelled your sign-onrequest. Sign-on is terminated.

Explanation: You have pressed PF3, and consequentlyCESN has been successfully terminated.

System action: CICS awaits further transactionrequests.


Destination:

terminal

ERZ013001I Usage: ’cicstfmt’ [-h ″[!]hookIds″][-m″[!]moduleIds″][-o outFile][-f fileName |[-r regionName][-s a|b | [-u userId] [-ntraceSeqNo | -p [traceSeqNos]]]]

Explanation: You specified the -? option for cicstfmt.This message gives the required syntax for cicstfmt.

System action: None

User response: None. For more information about thecicstfmt command, see the TXSeries Infocenter.

Destination:

stderr

ERZ013002E Invalid Arguments: Usage: cicstfmt [-h″[!]hookIds″][-m ″[!]moduleIds″][-ooutFile][-f fileName | [-r regionName][-sa|b | [-u userId] [-n traceSeqNo | -p[traceSeqNos]]]] | [-?]

Explanation: The arguments you supplied to cicstfmtwere incorrect.

System action: cicstfmt terminates with a non-zeroreturn code.

User response: Retry the cicstfmt command using thecorrect syntax, as shown in the message. For moreinformation about the cicstfmt command, see theTXSeries Infocenter.

Destination:

stderr

ERZ013003E Trace file ’fileName’ does not exist

Explanation: cicstfmt was unable to find the giventrace file.


ERZ012003E • ERZ013003E


User response: Ensure that the specified trace fileexists. You possibly gave incorrect command lineoptions, or a trace file possibly does not exist.

Destination:

stderr

ERZ013004E Unable to obtain the user trace file foruser ’userId’, on region ’regionName’

Explanation: cicstfmt was unable to find the detailsfor the user specified with the -u option or theTraceFile attribute in the User Definition (UD) entry forthe specified user is blank.


User response: Check that the user identifier is valid,and that the TraceFile attribute in the UD entry for theuser is not blank.

Destination:

stderr

ERZ013005E Unable to obtain region definitions forregion ’regionName’

Explanation: The cicstfmt command was unable toobtain the region definitions for the given (ordefaulted) region. If you did not specify the -r optionthen the default region, as specified by theCICSREGION environment variable, has not been setup correctly.


User response: Retry the command with a validregion name specified by the -r option or correct theCICSREGION environment variable.

Destination:

stderr

ERZ013006E Unable to obtain the default regionname

Explanation: The cicstfmt command was unable toobtain the name of the default region from theCICSREGION environment variable.


User response: Set the CICSREGION environmentvariable to the name of the default region.Alternatively, retry the command specifying the nameof a valid region with the -r option.

Destination:

stderr

ERZ013008I In region ’regionName’ the following usertrace files for user ’userId’ exist:

Explanation: This message is followed by a list of usertrace files.

System action: None

User response: Retry the cicstfmt command with the-u and the -n options.

Destination:

stderr

ERZ013009E User ’userId’ does not have any usertrace files available for region’regionName’

Explanation: There are no user trace files available forprocessing.

System action: None

User response: None

Destination:

stderr

ERZ013010I Do you really want to remove the tracefiles for region ’regionName’ (Yes/No)?

Explanation: This message is prompting you toconfirm your request to remove the trace files.

System action: None

User response: Enter Yes or No.

Destination:

stderr

ERZ013011I Usage: cicstracefilter [-h″[!]hookIds″][-m″[!]moduleIds″]

Explanation: This is the usage information producedby cicstracefilter in response to the -? option. For moreinformation about the cicstracefilter command, see theTXSeries Infocenter.

System action: None

User response: None

Destination:

stderr

ERZ013012W An invalid option ’optionName’ has beenspecified

Explanation: You specified an option optionName thatis not recognized by cicstracefilter.

System action: The option is ignored andcicstracefilter continues.

ERZ013004E • ERZ013012W


User response: Retry the command with validoptions, if necessary. Usage information can beobtained by entering the command cicstracefilter -? orsee the TXSeries Infocenter for more information.

Destination:

stderr

ERZ013013W An invalid parameter ’parameterName’has been specified

Explanation: You specified a parameter parameterNamethat is not recognized by cicstracefilter.

System action: The parameter is ignored andcicstracefilter continues.

User response: Retry the command with validparameters, if necessary. Usage information can beobtained by entering the command cicstracefilter -? orsee the TXSeries Infocenter for more information.

Destination:

stderr

ERZ013014E A hook identifier, ’hookId’, has beenspecified that is larger than themaximum (FFF)

Explanation: You specified a hook identifier, hookId, inthe argument to the -h option that is larger than themaximum permitted hook identifier.

System action: The cicstracefilter commandterminates.

User response: Retry the command with a valid list ofhook identifiers.

Destination:

stderr

ERZ013015E Syntax error in list of hook identifiers

Explanation: You supplied a list of hook identifiers asthe argument to the -h option, but the list is not in thecorrect format. The list consists of a list of hookidentifiers separated by commas, each hook identifierconsisting of three hexadecimal digits. A range of hookidentifiers can also be specified by separating two hookidentifiers by a ’-’ character.



Destination:

stderr

ERZ013016E Invalid range in list of hook identifiers

Explanation: You supplied a list of hook identifiers asthe argument to the -h option, but a range of hookidentifiers in the list is not in the correct format. Arange of hook identifiers is specified by separating twohook identifiers by a ’-’ character with the lower hookidentifier first.



Destination:

stderr

ERZ013017E The hook identifier ’hookId’ contains aninvalid hexadecimal digit

Explanation: The valid hexadecimal digits are ’0’through ’9’, ’A’ through ’F’ and ’a’ through ’f’. Thehook identifier hookId contains a character that is not inthis set.



Destination:

stderr

ERZ013018E A module identifier, moduleId, has beenspecified that is larger than themaximum permitted (999)

Explanation: You specified a module identifier,moduleId, in the argument to the -m option that is largerthan the maximum permitted module identifier.


User response: Retry the command with a valid list ofmodule identifiers.

Destination:

stderr

ERZ013019E The module identifier ’moduleId’contains an invalid decimal digit

Explanation: The module identifier moduleId containsa character that is not a valid decimal digit.


User response: Retry the command with a valid list ofmodule identifiers.

Destination:

ERZ013013W • ERZ013019E


stderr

ERZ013020W Module name ’moduleName’ does notmatch the name of any CICS module

Explanation: The module name, ’moduleName’, doesnot match any of the CICS module names.

System action: cicstracefilter continues.

User response: If necessary, retry the cicstracefiltercommand specifying a valid module name.

Destination:

stderr

ERZ013021E Unable to read data from stdin at offsetbyteOffset (error code errorCode)

Explanation: An error occurred while reading datafrom standard input. The error code returned by ferrorwas errorCode. The input file is possibly not a validCICS trace or dump file, or it is possibly corrupted ortruncated. Trace entries were possibly already writtento standard output, in which case the output can beformatted by using the cicstfmt command.

System action: cicstracefilter terminates.

User response: Check that the file system is not fulland, if necessary, recreate the trace or dump file. If theproblem persists, please contact your supportorganization.

Destination:

stderr

ERZ013022E An invalid hook type, hookType, wasencountered in stdin at offset byteOffset -hook identifier ’hookId’

Explanation: An error occurred while processing datafrom standard input. Hook type hookType is not valid.The valid hook types are 0 and 8. The input file ispossibly not a valid CICS trace or dump file, or it ispossibly corrupted. Trace entries were possibly alreadywritten to standard output, in which case the outputcan be formatted by using the cicstfmt command.


User response: If necessary, recreate the trace or dumpfile. If the problem persists, please contact your supportorganization.

Destination:

stderr

ERZ013023E Unable to write data to standard output(error code errorCode)

Explanation: An error occurred while writing tostandard output. The error code returned by ferror waserrorCode.


User response: Check that there is sufficient space inthe file system and that you have the necessarypermissions to write the file. If the problem persists,please contact your support organization.

Destination:

stderr

ERZ013024I The following user trace files for user’userId’ exist:

Explanation: This message is followed by a list of usertrace files.

System action: None

User response: Retry the cicstfmt command with the-u and the -n options.

Destination:

stderr

ERZ013025I Usage: cicstfmt [-h ″[!]hookIds″][-m″[!]moduleIds″][-o outFile][-f fileName |[-r regionName][-s a|b | [-u userId] [-ntraceSeqNo | -p [traceSeqNos]]]] | [-?]

Explanation: This is the usage message for thecicstfmt command.

System action: The command terminates.


Destination:

stderr

ERZ013026E Entry ’userId’ not found for permanentdatabase class ’databaseName.’

Explanation: cicsftmt tried to read a record from the’databaseName.’ stanza file, looking for resource ’userId’,but failed to do so.

System action: The command can continue orterminate, depending on the severity of the problem.

User response: Check that the stanza file exists, andhas the correct permissions to enable cics to read fromit. Check that this file has not been corrupted.

Destination:

stderr

ERZ013020W • ERZ013026E


ERZ013027E Unable to access directory ’directory’,errno ’errno.’

Explanation: CICS tried to look at the contents of thespecified directory but was unable to do so.


User response: Ensure that the relevant directoryexists and has the necessary access permissions. Checkerrno for futher information.

Destination:

stderr

ERZ013028E Unable to access trace file ’traceFile’,errno ’errno.’

Explanation: cicstfmt was unable to access the giventrace file. This was possibly in an attempt to read it orto delete it.

System action: Depending on why the file was beingaccessed, the command can choose either to ignore thefile and continue, or to terminate.

User response: You possibly need to do nothing. Ifyou believe the file is supposed to exist then check itdoes, and check that its permissions enable you todelete it. More information can be found by usingerrno.

Destination:

stderr

ERZ013029E Not enough memory for operation

Explanation: cicstfmt tried to access some memory forits own working storage but was unable to do so.


User response: Ensure your machine has enoughmemory installed. Check also that you have adequatepaging space. See the TXSeries Infocenter for moreinformation on system resources.

Destination:

stderr

ERZ013030E Unable to find CICS data

Explanation: cicstfmt encountered a problem whileobtaining information about the CICS system installedon your machine.

System action: cicstfmt terminates with a non-zerostatus.

User response: Ensure that CICS is installed correctly.

Destination:

stderr

ERZ013031E Region name ’regionName’ is greater than8 characters long

Explanation: A region name must be 8 characters orless.

System action: The command abnormally terminateswith a non-zero error status.

User response: Enter again with the correct regionname.

Destination:

stderr

ERZ014001E ’userid’ is not authorized to run ’transId’from ’termId’.

Explanation: The user ’userid’ has invoked atransaction ’transId’ at terminal ’termId’, or transaction’transId’ was invoked with no associated useridentification for terminal ’termId’. The userpermissions or terminal permissions do not permit thetransaction to run.

System action: The transaction ’transId’ is not started.Abend code A146 is displayed (via message ERZ1416E)at ’termId’.

User response: Ensure the Resource Security Level(RSL) key (RSLKeyList) and the Transaction SecurityLevel (TSL) key (TSLKeyList) attributes in the UserDefinition for the user ’userid’ permit access to thetransaction ’transId’. If no user identifier is associatedwith the transaction then ensure the Resource SecurityLevel (RSL) key (RSLKeyList) and the TransactionSecurity Level (TSL) key (TSLKeyList) attributes in theTerminal Definition for the terminal ’termId’ permitaccess to the transaction ’transId’. Resubmit thetransaction request.

Destination:

console.msg

ERZ014002E ’exceptionText’ exception detected.

Explanation: An abnormal condition was raised andcaught while running in CICS code.

System action: The CICS process is terminated. If theprocess was an application server then any task it wasrunning is terminated with abend code A142. If theprocess was a CICS control process then the region isabnormally terminated with code U1401.

User response: This is a CICS internal problem. Saveany dump file produced. If the region was terminated,then restart the region (ensuring the region isconfigured to produce a dump if the problem recurs).Contact your support organization.

Destination:

console.msg

ERZ013027E • ERZ014002E


ERZ014003E Unable to initialize process processId asan application server.

Explanation: CICS has detected an unrecoverableerror during application server startup.

System action: The new application server beingstarted is terminated.

User response: This problem is most likely caused byCICS being short of region pool storage. Look forstorage errors reported in console.msg and correctthese. If the problem persists, contact your supportorganization.

Destination:

console.msg

ERZ014004E Unable to allocate storage forTransaction Work Area (TWA) intransaction ’transId’. Requested size islength bytes.

Explanation: CICS was unable to satisfy the storageallocation request of length bytes for the TransactionWork Area (TWA) in transaction ’transId’.

System action: The transaction ’transId’ is not started.If the transaction was submitted from a terminal thenabend code A143 is displayed (via message ERZ1416E)at that terminal.

User response: Other messages in CSMT orconsole.msg indicate the underlying cause of thisproblem. If the cause of the problem is shortage ofregion storage for CICS control blocks then correctthese problems. If the transaction has inherited aCOMMAREA from the previous transaction then thistakes up task private storage. Otherwise, reconfigurethe TWASize attribute in the Transaction Definition torequire less storage. Resubmit the transaction request.

Destination:

console.msg

ERZ014005E Unable to execute transaction ’transId’.No initial program defined.

Explanation: The transaction ’transId’ cannot beexecuted because no initial program is specified in theTransaction Definition.


User response: The transaction is not executablebecause there is no initial program specified in theProgName attribute in the Transaction Definition.Correct the Transaction Definition to specify the nameof the initial program and resubmit the transaction.

Destination:

console.msg

ERZ014007E Incorrect Task Control Area (TCA)signature found at ’address’; expected’expectedSignature’ actual ’actualSignature’.

Explanation: The CICS self-consistency checking hasdetected a Task Control Area (TCA) in the TCA chainwith an incorrect signature.


User response: This is a CICS internal problem. If theSysDump attribute in the Region Definition is set to’yes’ then a region dump file is produced. Save this file.Restart the region (ensuring the region is configured toproduce a dump if the problem recurs). Contact yoursupport organization.

Destination:

console.msg

ERZ014008E Unable to allocate storage for theCOMMAREA in transaction ’transId’.Requested size is length bytes.

Explanation: CICS was unable to satisfy the storageallocation request of length bytes for the COMMAREAin transaction ’transId’.


User response: Other messages in CSMT orconsole.msg indicate the underlying cause of thisproblem. If the cause of the problem is shortage ofregion storage for CICS control blocks then correctthese problems and retry the transaction. Otherwise,redesign your transaction to use less storage for theCOMMAREA and resubmit the transaction.

Destination:

console.msg

ERZ014009I Unable to free storage for theCOMMAREA in transaction ’transId’running at ’termId’.

Explanation: CICS was unable to free the storage usedto hold the COMMAREA saved by the previoustransaction run at ’termId’.

System action: CICS processing continues.

User response: This message is logged for informationonly and has no effect on the running of the transaction’transId’. It can possibly indicate an internal CICSproblem, and other messages in console.msg or CSMTcan provide further information. It does mean thatsome storage acquired on behalf of a transaction

ERZ014003E • ERZ014009I


previously run at ’termId’ was unable to be freed andthis storage remains allocated until the region is shutdown. If the problem persists, contact your supportorganization.

Destination:

console.msg

ERZ014010E Unable to initialize communications toremote system to run transaction’transId’.

Explanation: CICS received a request from a remotesystem to run the transaction ’transId’ and was unableto establish a conversation with that remote system.

System action: The transaction ’transId’ is not started.

User response: This problem is caused by failure ofthe communications links to the remote system,problems in the CICS communications software or aninvalid CICS Region Definition. Look forcommunication errors reported in console.msg orCSMT and correct these. If the problem persists, contactyour support organization.

Destination:

console.msg

ERZ014011E Unable to allocate a communicationssession with remote system ’sysId’ to runtransaction ’transId’.

Explanation: CICS has received a transaction requestas a result of an EXEC CICS START specifying aterminal identifier that is configured as the identifier ofa connected system. An attempt to allocate a sessionwith the specified system was unsuccessful.

System action: The transaction ’transId’ is not started.

User response: This problem is caused by failure ofthe communication links to the remote system orproblems in the CICS communications software. Lookfor communication errors reported in console.msg orCSMT and correct these. If the problem persists, contactyour support organization.

Destination:

console.msg

ERZ014012E CICS was unable to obtain a databaseentry for terminal ’termId’ duringinitialization of transaction ’transId’.

Explanation: The record describing the user’s terminalwas unable to be retrieved from the runtime regiondatabase.

System action: The transaction ’transId’ is not started.Abend code A141 is written to console.msg, anddisplayed at ’termId’ if the terminal is still available.

User response: Use CEMT from another terminal toinquire on the Terminal Definition for ’termId’. If youare using a permanently connected terminal (asopposed to autoinstalled) and it does not exist thencontact your System Administrator to add a TerminalDefinition for ’termId’ and resubmit the transaction. Ifthe Terminal Definition does exist, or if you are usingan autoinstalled terminal, then the terminal waspossibly purged by, for instance, CEMT SETTERMINAL OUTSERVICE. Otherwise, this indicates aninternal CICS problem. Retry the transaction and if theproblem persists, contact your support organization.

Destination:

console.msg

ERZ014013E Terminal status does not permit ’transId’to be run at ’termId’.

Explanation: The attribute settings in the TerminalDefinition for ’termId’ do not permit the transaction tobe run in the way requested. This error is produced ifthe OutService attribute in the Terminal Definition isset to yes; if the transaction request was initiated froma terminal and the CanStartTTIs attribute in theTerminal Definition is set to no, or if the request isinitiated as an Automatic Task Initiation (ATI) (eitherlocally or remotely) and the CanStartATIs attribute isset to no.


User response: Correct the terminal attributes topermit the transaction to be run in the mode requestedand resubmit the transaction.

Destination:

console.msg

ERZ014014E Unable to initialize terminal ’termId’ asprincipal facility for transaction ’transId’.

Explanation: CICS was unable to initialize theterminal ’termId’ for use during the initialization oftransaction ’transId’.


User response: Other messages (ERZ062xxx) in CSMTor console.msg indicate the underlying cause of thisproblem. Once corrected, resubmit the transactionrequest.

Destination:

console.msg

ERZ014010E • ERZ014014E


ERZ014015E CICS was unable to save initial inputdata from terminal ’termId’ duringinitialization of transaction ’transId’.

Explanation: The user data sent with the transactionrequest for ’transId’ was unable to be written to theterminal input/output area (TIOA) of terminal ’termId’.


User response: Other messages (ERZ062xxx) in CSMTor console.msg indicate the underlying cause of thisproblem. Once corrected, resubmit the transactionrequest.

Destination:

console.msg

ERZ014016E Transaction ’transId’, Abend ’abendCode’,at ’termId’.

Explanation: The transaction ’transId’ running at theterminal where this message is displayed wasabnormally terminated with code ’abendCode’. If thetransaction is not associated with a terminal then ’????’is substituted for ’termId’.

System action: The transaction ’transId’ is abnormallyterminated.

User response: ’abendCode’ is the abnormaltermination code that caused the transaction to beterminated. If the code is not one used for abnormalterminations initiated by CICS then it is a user codegenerated by an EXEC CICS ABEND ABCODE(’abendCode’). Correct the problem and resubmit thetransaction. If the transaction was abended A147 whileit was being debugged via CEDF the debug terminalcan remain locked; use CEMT commands to put thedebug terminal out of service and reacquire it.

Destination:

console.msg and the terminal that invoked thetransaction.

ERZ014017E Unable to allocate storage for the ExecInterface Block (EIB) in transaction’transId’. Requested size is length bytes.

Explanation: CICS was unable to satisfy the storageallocation request of length bytes for the Exec InterfaceBlock (EIB) during the initialization of transaction’transId’.


User response: Other messages in CSMT orconsole.msg indicate the underlying cause of this

problem. If the cause of the problem is shortage ofregion storage for CICS control blocks then correctthese problems. Retry the transaction request and, if theproblem persists, contact your support organization.

Destination:

console.msg

ERZ014019E Unable to remove details of currenttransaction ’transId’ to permit executionof ’newTransId’.

Explanation: CICS received a request to replace thecurrent transaction ’transId’ with the new transaction’newTransId’ and was unable to remove details heldabout the current transaction.

System action: The new transaction ’newTransId’ is notstarted and the current transaction is abended withcode A145.

User response: This is a CICS internal problemspecific to the environment created by the CRTEtransaction. Other messages in CSMT or console.msgindicate the underlying cause of this problem. Restartthe CRTE session and resubmit the transaction. If theproblem persists, contact your support organization.

Destination:

console.msg

ERZ014020E CICS was unable to obtain a databaseentry for transaction ’transId’.

Explanation: The record describing the transaction’transId’ was unable to be retrieved from the runtimeregion database or written back to the database.


User response: The most likely cause of this error isthe Transaction Definition being deleted by the SystemAdministrator while the transaction was being started.Use CEMT to inquire on the Transaction Definition for’transId’. If it does not exist then contact your SystemAdministrator to add the definition for ’transId’ andresubmit the transaction. If the Transaction Definitiondoes exist then this indicates an internal CICS problem.Retry the transaction and, if the problem persists,contact your support organization.

Destination:

console.msg

ERZ014015E • ERZ014020E


ERZ014021E Autoinstall of device ’deviceId’ wasunsuccessful.

Explanation: An attempt to autoinstall a terminaldefinition from device ’deviceId’ was unsuccessful.

System action: The terminal is not installed into theregion.

User response: Other messages in CSMT orconsole.msg indicate the underlying cause of thisproblem. Once the cause of these is corrected theautoinstall can be retried.

Destination:

console.msg

ERZ014022I Exception ’exceptiontext’ caught duringtermination of transaction ’transId’ at’termId’.

Explanation: An abnormal condition was raised andcaught during the termination of the transaction’transId’ running at the terminal ’termId’.

System action: CICS continues with the termination ofthe transaction.

User response: This message is logged for informationonly and has no effect on the running of the transaction’transId’. It can possibly indicate an internal CICSproblem, and other messages in console.msg or CSMTcan provide further information. If the problempersists, contact your support organization.

Destination:

console.msg

ERZ014024E An attempt to attach the region memoryin process with id processId wasunsuccessful.

Explanation: CICS made an unsuccessful attempt toattach to the shared memory segment of the region.

System action: CICS abnormally terminates the regionwith code U1403.

User response: If the process detecting the problemwas an application server (cicsas) then it is possiblethat the problem is caused by user code that hascorrupted internal CICS data structures. Examine theuse of static memory in any transaction running at thetime of failure. Retry the failed transactions once theyare checked. If the process was a CICS control processthen this indicates a CICS internal problem. If theSysDump attribute in the Region Definition is set toyes then a region dump file is produced. Save thisdump file. Restart the region (ensuring the region isconfigured to produce a dump if the problem recurs).Contact your support organization.

Destination:

console.msg

ERZ014025E Unable to set region locale fortransaction ’transId’. Region localecategories were ’localeName’.

Explanation: CICS received a request to run thetransaction ’transId’ and was unable to set the locale ofthe application server to the region locale.


User response: The locale for the transaction is takenfrom the environment of the user who submitted thetransaction request. If the requested locale cannot beset, or is not supplied, then the application server is setto the region locale to run the transaction. Therequested locale categories within the locale can bemodified by a number of environment variables.Ensure that each of these environment variablescontains a valid locale for the machine where thetransaction request is to be run and retry thetransaction request.

Destination:

console.msg

ERZ014026I Unable to save locale duringinitialization of transaction ’transId’.

Explanation: The locale for the transaction ’transId’was unable to be saved in the CICS region pool.

System action: The transaction ’transId’ is startedusing the region locale.

User response: This message is logged for informationonly and has no effect on the running of transaction’transId’, except that the region locale is used instead ofthe requested locale. This problem is most likely causedby CICS being short of region pool storage. It canpossibly indicate an internal CICS problem, and othermessages in console.msg or CSMT can provide furtherinformation. If the problem persists, contact yoursupport organization.

Destination:

console.msg

ERZ014027I Unable to set requested locale duringinitialization of transaction ’transId’ orhaving problems with the messagecatalog. Requested locale categorieswere ’localeName’.

Explanation: CICS received a request to run thetransaction ’transId’ and was unable to set the locale ofthe application server to the requested locale or wasunable to access the message catalog.

ERZ014021E • ERZ014027I


System action: The transaction ’transId’ is startedusing the region locale.

User response: This message is logged for informationonly and has no effect on the running of transaction’transId’, except that the region locale is used instead ofthe requested locale. The requested locale for thetransaction is taken from the environment of the userwho submitted the transaction request. The localecategories within the locale can be modified by anumber of environment variables. Ensure that each ofthese environment variables contain a valid locale forthe machine where the transaction request is to be runand retry the transaction request.

Destination:

console.msg

ERZ014028E Transaction ’transId’ was unsuccessful inthe invocation mode check and couldnot be started.

Explanation: This error message is produced if thesecurity check on the way in which the transaction wasinvoked is unsuccessful. This check is based on theTransaction Definition, the way in which thetransaction was started (either user requested,Automatic Task Initiation (ATI) or triggered task), theprincipal facility for the task (either input/outputterminal, output terminal, communications link ornone) and the current CICS phase.


User response: Other messages in CSMT orconsole.msg indicate the underlying cause of thisproblem. Check that the InvocationMode attribute inthe Transaction Definition for ’transId’ permits thetransaction to be run in the way requested. Once thecause of the error is corrected the transaction requestcan be retried.

Destination:

console.msg

ERZ014029W Application server ended normally, butlog daemon wasn’t notified.

Explanation: The process that ended was still using alog file. This is not supposed to occur.

System action: The system notifies the log daemonthat the log file is no longer in use.

User response: It appeared to cics that the processthat last shut down was an application server thatended normally, that is to say with an exit code of 0.This is not the case. Check what transaction, if any wasrunning when the process shut down, and that it isbehaving correctly.

Destination:

console.msg

ERZ014030W Short-on-storage for user exit 15(UE014015) parameter list.

Explanation: A request to obtain storage in which tobuild a parameter list for user exit 15 (UE014015) failed.

System action: Processing continues as if user exit 15(UE014015) is inactive.

User response: Produce a SNAP dump and investigatestorage usage in the CICS region; consider increasingthe amounts of storage available to CICS using regiondefinition parameters.

Destination:

CSMT

ERZ014031E Unable to allocate storage for user exit25 (UE014025) parameter list, whilerouting transaction ’transId’.


System action: The transaction ’transId’ is not started.If the transaction was submitted from a terminal thenabend code A143 is displayed (via message ERZ1416E)at that terminal. Other processing continues.

User response: Produce a SNAP dump and investigatestorage usage in the CICS region; consider increasingthe amounts of storage available to CICS using regiondefinition parameters.

Destination:

console.msg

ERZ014032E A null program name has been returnedby user exit 25 (UE014025), whilerouting transaction ’transId’.

Explanation: This error message is produced if thedynamic transaction routing user exit (UE014025)returns a null program name in its parameter list fieldUE_dyrprog.


User response: Ensure that your dynamic transactionrouting user exit does not return a null program name,even if the transaction is to be routed remotely. Alteryour user exit and retry the dynamic transaction.Another cause of the problem is possibly that theProgName field in the Transaction Definitions is nulland user exit 25 (UE014025) has let the program namedefault to this.

ERZ014028E • ERZ014032E


Destination:

console.msg

ERZ014033E User exit 25 (UE014025) has returned areturn code of UE_Term_Abend, whilerouting transaction ’transId’.

Explanation: This error message is produced if thedynamic transaction routing user exit (UE014025)returns a return code of UE_Term_Abend.


User response: Identify why your user exit hasreturned UE_Term_Abend. It was possibly produced byyour user exit for a valid reason such as all remotesystems being unavailable. If you wish the dynamictransaction to be routed ensure that your user exitreturns UE_Normal.

Destination:

console.msg

ERZ014034E User exit 25 (UE014025) is not active,and dynamic transaction ’transId’ hasbeen started.

Explanation: This error message is produced if thedynamic transaction routing user exit (UE014025) is notactive and a dynamic transaction is started.


User response: If you are using dynamic transactionrouting ensure that you have written a dynamictransaction routing program. Also ensure that the userexit program is associated with the exit point, by usingUserExitNumber attribute in the Program Definitions.If you have tried associating a program with thedynamic routing user exit, check the console messagesduring region start-up to ensure that the program wassuccessfully loaded. You are advised to restart CICSonce you have discovered why your dynamictransaction routing program is not active.

Destination:

console.msg

ERZ014035W User exit 25 (UE014025) requested toterminate transaction ’transId’ without anabend.

Explanation: This error message is produced if thedynamic transaction routing user exit (UE014025) doesnot return a recognized return code, or returnsUE_Terminate.

System action: Processing of transaction ’transId’ stopsnormally. Other processing continues.

User response: Ensure that your dynamic transactionrouting program returns a valid return code. IfUE_Terminate was returned, check why your dynamictransaction user exit has returned this value. It waspossibly produced by your user exit for a valid reasonsuch as all remote systems being unavailable. If youwish the dynamic transaction to be routed, ensure thatyour user exit returns UE_Normal.

Destination:

console.msg

ERZ014036E Unable to force purge process processIdas it is XA registered (XID xId).

Explanation: CICS was unsuccessful in attempting toforce purge the transaction running in the specifiedprocess. The main thread has ignored both a request toforce purge and an asynchronous thread cancel. TheXID with which the transaction is registered is as given.

System action: The attempt to force purge thetransaction is abandoned.

User response: You can choose to forcibly terminatethe process indicated in the message. However, if anyrecoverable resources were updated, this can result in aCICS region termination to avoid corruption of userdata. Investigate the status of all resources used by the’hung’ transaction in order to determine whether thereis a non-CICS resource that can be prompted intoaction. Ensure that the Transaction Definitions for thetransaction has the attributes Timeout andDeadLockTimeout set to non-zero values. Use the XIDto determine the state of the transaction and/or to alterthat state in the database.

Destination:

console.msg

ERZ014037W Transaction ’transId’ rejected -transaction disabled.

Explanation: CICS attempted to run the transaction’transId’, but was unable to, either because thetransaction was disabled, or the limit on the number ofqueued and active transactions, for the class ’transId’belongs to, was reached. The class is specified by theTClass: parameter in the Transaction Definitions. Themaximum number of tasks allowed is one less than thetotal of the positional entries, in the Region Definitionsparameters ClassMaxTasks and ClassMaxTaskLim, forthe transaction class specified.

System action: The transaction is not run.

User response: Enable the transaction if it is disabled(using cicsupdate or CEMT). If the class limit wasreached, wait until some of the running tasks havefinished, and resubmit the transaction. If you want to

ERZ014033E • ERZ014037W


raise the class limit, increase the ClassMaxTasks orClassMaxTaskLim parameters, or set ClassMaxTaskLimto 0 for the transaction class (which means no limit isplaced on the number of tasks). You can also movesome transactions to a different class.

Destination:

The user’s screen.

ERZ014038W Transaction ’transId’ running as tasktaskId has used userCPU milliseconds ofuser space CPU

Explanation: The task has exceeded its maximumallowed user space CPU. There is a possible programloop in the task, or the maximum allowed user spaceCPU usage for this task is set too low. See theMaxTaskCPU attribute in the Transaction Definitions orthe MaxTaskCPU in the Region Definitions.

System action: The task continues. The user spaceCPU usage for the task is reset to zero.

User response: Check that the MaxTaskCPU attributesare set correctly. Check the task for a possible infiniteor runaway program loop.

Destination:

console.msg

ERZ014039E Transaction ’transId’ running as tasktaskId has used userCPU milliseconds ofuser space CPU

Explanation: The task has exceeded its maximumallowed user space CPU. There is a possible programloop in the task, or the maximum allowed user spaceCPU usage for this task is set too low. See theMaxTaskCPU attribute in the Transaction Definitions orthe MaxTaskCPU in the Region Definitions.

System action: The task is abnormally terminate withabend code AICA.

User response: Check that the MaxTaskCPU attributesare set correctly. Check the task for a possible infiniteor runaway program loop.

Destination:

console.msg

ERZ014040E First abend ’AbendStr’ occurred fortransaction ’Tranid’ in program’ProgName’

Explanation: Current transaction got its first abend inthe specified program.

System action: Refer to the information for thespecific abend.

User response: Refer to the information for thespecific abend.

Destination:

console

ERZ014041E Forcepurge cannot be done now.

Explanation: When the forcepurge request is receivedthe application server was holding a critical lock for along time

System action: The Task will not be forcepurged

User response: This message might indicate a hangsituation. If the region is not responding, contact yoursupport representative.

Destination:

console.msg

ERZ014045I Forcepurge received, proceeding fortermination.

Explanation: Forcepurge request has been receivedand honored.

System action: Force purge the task and terminate theapplication server.

User response: None

Destination:

console.msg

ERZ014046I Forcepurge event received, reason code:reason originator :originator.

Explanation: Forcepurge request has been received.

System action: CICS will make an attempt to forcepurge the task.

User response: None

Destination:

console.msg





Destination:

ERZ014038W • ERZ014047E


console

ERZ014048E Forcepurge:Task could not beterminated, exiting process

Explanation: The current task can not be terminatedas it could be in a non-cancelable blocking call.

System action: CICS terminates the application serverprocess with exit code 199.


Destination:

console

ERZ014049I Task:’taskno’ got terminated which wasinitiated from RemoteRegion:’remoteRegion’ on RemoteProcessId:’remoteProcessIdd’ RemoteTask:’remoteTasknumber’ RemoteTransaction:’remoteTran’ that started at’starttime’ linked at ’linktime’

Explanation: An abnormal condition was raised andcaught during the termination of the task ’taskno’.

System action: CICS continues with the termination ofthe task.

User response: This message is logged for informationonly. Refer to CRTI.out to get more information. If theproblem persists, contact your support organization.

Destination:

console.msg

ERZ015001E CICS self-consistency checking hasdetected an inconsistency in theProgram Control internal data structures

Explanation: The CICS self-consistency checkingdetected an error in the Program Control internal datastructures, in the Region Pool, that hold informationabout programs running at each logical level. This errorwas unable to be corrected.

System action: The region continues or terminatesabnormally if the inconsistency is serious (with abendcode U1501).

User response: Because the Program Control datastructures are held in the Region Pool it is unlikely thatthe invalid data was produced by application code.Consider shutting the region down if any further errorsare reported. Save any dump file produced for use byyour support organization. If the problem persists,contact your support organization.

Destination:

console.msg

ERZ015002E User ’userId’ is not authorized to runprogram ’prpgramName’

Explanation: The named user attempted to run aprogram to which the user does not have securityaccess.

System action: CICS returns the NOTAUTH conditionto the application and the transaction continues.

User response: Request a change to the securitypermissions for the Program Definition entry (PD), oruse another program.

Destination:

console.msg

ERZ015003E Transaction ’transId’ attempted to run aprogram with an empty name

Explanation: CICS attempted to EXEC CICS LINK orEXEC CICS XCTL to a program where the programname has no characters.

System action: CICS returns the PGMIDERR conditionto the application and the transaction continues.

User response: Correct the program belonging to thetransaction that is in error.

Destination:

CSMT

ERZ015004E CICS is unable to allocate storage tohold a COMMAREA during an EXECCICS RETURN

Explanation: CICS is unable to allocate storage fromthe Task-Shared Pool for a COMMAREA to be passedto another transaction via an EXEC CICS RETURN.

System action: CICS terminates the transaction withabend code A156, but the region continues.

User response: Because memory in the Task-SharedPool is continually being acquired and freed byrunning transactions, resubmission of this transactioncan possibly be successful. If this problem persistswhen you resubmit the transaction, check whether anytransaction is using large amounts of Task-Sharedstorage. Finally, consider increasing the size of theTask-Shared Pool by restarting the region with anoverride for the value of the MaxTSHPool attribute inthe Region Definition (RD).

Destination:

CSMT

ERZ014048E • ERZ015004E


ERZ015005E CICS is unable to allocate Region Poolstorage for Program Control datastructures

Explanation: CICS is unable to allocate storage fromthe Region Pool, to hold the control informationrequired for running a new program.

System action: CICS abnormally terminates thetransaction, but the region continues.

User response: Because memory in the Region Pool iscontinually being acquired and freed by CICS on behalfof running transactions, resubmission of thistransaction can possibly be successful. If this problempersists when you resubmit the transaction, checkwhether it is looping in some way that causes CICS toacquire substantial amounts of Region Pool memory onits behalf; for example, check the depth of EXEC CICSLINKs in the program, as Region Pool memory isrequired for each logical level. Finally, considerincreasing the size of the Region Pool by restarting theregion with an override for the value of theMaxRegionPool attribute in the Region Definition(RD).

Destination:

CSMT

ERZ015006W Abnormal Termination ’abendCode’,Program ’programName’, Transaction’transId’, Terminal ’termId’

Explanation: CICS abnormally terminates the namedtransaction, with top-level program pgmid, being runat the named terminal.

System action: CICS abnormally terminates thetransaction. The region continues.

User response: Investigate the cause of the abnormaltermination using the CICS Problem DeterminationGuide. Also consider using any dump file created forthe transaction.

Destination:

CSMT

ERZ015007E Abnormal Termination U1507. CICS isunable to free Program Control storage

Explanation: CICS is unable to free Region Poolstorage allocated for Program Control data structures.These data structures hold information about programsrunning at each logical level.


User response: Because the Program Control datastructures are held in the Region Pool, the problemencountered freeing the data structures is unlikely to becaused by application code. It is more likely to be

caused by an inconsistency in the CICS internal datastructures. If the problem recurs, save any dump fileproduced and contact your support organization.

Destination:

console.msg

ERZ015008E CICS is unable to unload a program

Explanation: CICS was unable to unload a programpreviously loaded by an application server.

System action: CICS abnormally terminates thetransaction and the application server in which it wasrunning (with abend code A155).

User response: Check the symptom record file for anyoperating system specific failure. The problem can alsobe caused by incorrect application code, so check forthis in the transaction that failed.

Destination:

CSMT

ERZ015009W Unable to free all CICS Program Controlstorage

Explanation: CICS was unable to clean up all memoryused for Program Control data structures from theRegion Pool by an application server. These datastructures hold information about programs running ateach logical level. This error occurs during applicationserver termination.

System action: The application server is terminated.

User response: If any further problems are reportedby the CICS self-consistency checking transaction, saveany dump files produced. If the problem recurs, contactyour support organization.

Destination:

console.msg

ERZ015010E Unable to free Program Control storage

Explanation: CICS is unable to release someTask-Private Pool storage allocated for Program Controldata structures. These data structures hold informationabout programs running at each logical level.

System action: CICS abnormally terminates thetransaction and the application server in which it wasrunning (with abend code A152).

User response: This problem is unlikely to be causedby application code. If the problem recurs, save anydump file produced and contact your supportorganization.

Destination:

CSMT

ERZ015005E • ERZ015010E


ERZ015011E Unable to lock a database entry

Explanation: CICS is unable to lock a database entryfor the program definition of a program being run. Thiswas due to lack of space in the Region Pool.

System action: CICS abnormally terminates thetransaction and the application server running thetransaction (with abend code A154).

User response: Because memory in the Region Pool iscontinually being acquired and freed by CICS on behalfof running transactions, resubmission of thistransaction can possibly be successful. If this problempersists when you resubmit the transaction, checkwhether it is looping in some way that causes CICS toacquire substantial amounts of Region Pool memory onits behalf; for example, check the depth of EXEC CICSLINKs in the program, as Region Pool memory isrequired for each logical level. Finally, considerincreasing the size of the Region Pool by restarting theregion with an override for the value of theMaxRegionPool attribute in the Region Definition(RD).

Destination:

CSMT

ERZ015012E Abnormal Termination U1512. CICS isunable to delta a Program Definitiondatabase entry

Explanation: CICS is unable to delta a ProgramDefinition database record after locking it. This is likelyto be caused by an inconsistency in the CICS internaldata structures.


User response: Any CICS internal data structureinconsistencies are unlikely to be caused by applicationcode, since they are held in the Region Pool. Save anydump file produced and contact your supportorganization.

Destination:

console.msg

ERZ015014E Abnormal termination U1514. CICS isunable to attach Region Pool

Explanation: CICS was unable to attach sharedmemory used for the Region Pool after returning fromapplication code. Region Pool memory is protectedwhile running application code, by detaching it.


User response: This error can occur if shared memorysegments are removed accidentally. Otherwise, it can becaused by a CICS internal problem. In this case, save

any dump file produced and contact your supportorganization.

Destination:

console.msg

ERZ015015E CICS is unable to find a database entryfor the principal facility

Explanation: CICS was unable to find the databaserecord for the principal facility, during an EXEC CICSRETURN TRANSID COMMAREA command.

System action: CICS abnormally terminates thetransaction and the application server in which it wasrunning with abend code A15F.

User response: Save any dump file produced. Thiserror is likely to be caused by a CICS inconsistency,rather than incorrect applications. If the problem recurs,contact your support organization.

Destination:

CSMT

ERZ015016E Abnormal termination U1516. CICS isunable to update the principal facilitydatabase record

Explanation: CICS was unable to update the databaserecord for the principal facility, during an EXEC CICSRETURN TRANSID COMMAREA command. This islikely to be caused by an inconsistency in the CICSinternal data structures.



Destination:

console.msg

ERZ015017E Unsuccessful system check of lastloaded program

Explanation: CICS perform checks after loading eachapplication program used by a transaction. CICS wasunable to obtain information about the last programloaded.

System action: CICS abnormally terminates thetransaction with abend code APCT.

User response: Try resubmission of the transaction. Ifthe problem recurs, inspect the symptom record file forany operating system specific error. Check thetransaction for very deep EXEC CICS LINK levels, asmemory is required for loading each level. If the

ERZ015011E • ERZ015017E


problem persists, save any dump file produced andcontact your support organization.

Destination:

ERZ015018W Abnormal Termination ’abendCode’,Transaction ’transId’, Program’programName’

Explanation: CICS abnormally terminates the namedtransaction, with top-level program pgmid.


User response: Investigate the cause of the abnormaltermination using the CICS Problem DeterminationGuide. Also consider using any dump file created forthe transaction.

Destination:

CSMT

ERZ015019E A Program Control structure has aninvalid signature, should be:’expectedSignature’ is: ’actualSignature’, forTask Control Area at: TCAaddress

Explanation: The CICS self-consistency checkingdetected an error in the Program Control internal datastructures, in the Region Pool, that hold informationabout programs running at each logical level. This errorwas unable to be corrected.

System action: The region continues.

User response: Because the Program Control datastructures are held in the Region Pool it is unlikely thatthe invalid data was produced by application code.Consider shutting the region down if any further errorsare reported. Save any dump file produced for use byyour support organization. If the problem persists,contact your support organization.

Destination:

console.msg

ERZ015020E Count of Program Control structures:count1, in Task Control Area (at:TCAaddress) differs from actual number:count2

Explanation: The periodic consistency checkperformed by CICS on the Program Control structuresdetects an error that CICS was unable to correct. Thesedata structures hold information about programsrunning at each logical level.

System action: The CICS region is abnormallyterminated with abend code U1501.

User response: Because the Program Control datastructures are held in the Region Pool it is unlikely thatthe invalid data was produced by application code.

Save any dump file produced for use by your supportorganization. If the problem persists, contact yoursupport organization.

Destination:

console.msg

ERZ015021E An EXEC CICS LINK specified a NULLSYSID

Explanation: The EXEC CICS LINK SYSID optionmust specify the name of the system where thelinked-to program resides with up to four characters;CICS has instead found a NULL or empty string.

System action: The SYSIDERR condition is raised andthe transaction continues.

User response: Correct the program or handle thecondition as appropriate.

Destination:

CSMT

ERZ015022E Program ’programPathName’ not found

Explanation: CICS attempts to load a program but cannot find it.

System action: The transaction is abnormallyterminated (with abend code APCT).

User response: Install the program in the correctplace.

Destination:

CSMT

ERZ015027E Unexpected Exception - exception stringis: ’exceptionString’

Explanation: An exception is caught while running inCICS code. Possible causes of the exception are aninvalid argument on an EXEC CICS command or aCICS internal problem.

System action: The transaction and application serverrunning the transaction are abnormally terminated(with abend code A158).

User response: Inspect the symptom record file forsymptom records that indicate why the exceptionoccurred. Investigate the abend using appropriatedebugging tools (for example: CEDF, ANIMATOR). Ifthe exception appears to occur on a particular EXECCICS command, and some form of address exception isindicated, carefully check all arguments specified onthe EXEC CICS command and correct the program ifnecessary. Otherwise, this is probably a CICS internalproblem. Save any dump file produced. If the problempersists, contact your support organization.

Destination:

ERZ015018W • ERZ015027E


CSMT

ERZ015028W Exception in user application code(programName) - exception string is:’exceptionString’

Explanation: An exception is caught while running inapplication code.

System action: The user application code is unloadedfrom the task. The transaction is abnormally terminated(with abend code ASRA).

User response: Investigate the causes of the ASRAusing appropriate debugging tools (for example: CEDF,ANIMATOR).

Destination:

CSMT

ERZ015029E CICS is unable to allocate storage tohold a COMMAREA during XCTL

Explanation: CICS is unable to allocate storage for aCOMMAREA from the Task-Private Pool to be passedto another program during an EXEC CICS XCTL.


User response: Resubmission of the transaction canpossibly work. If not, determine if the transaction isusing excessive amounts of Task-Private Pool (Getmain)storage and correct this.

Destination:

CSMT

ERZ015030E Unable to redirect debugger IO toterminal ’termId’, errno errorNumber″

Explanation: CICS is unable to redirect the debuggerIO to the specified terminal. The given terminal wasunable to be opened as a file.

System action: CICS terminates the transaction withabend code A159.

User response: Look up the error number in errno.hand investigate the cause.

Destination:

CSMT

ERZ015031E Program ’programName’ in Transaction’transId’ has a Remote System Identifierwhen it is not valid to have one

Explanation: CICS attempted to run a program thathas a Remote System Identifier (RemoteSysId) definedin its database Program Definition entry (PD) whenRemoteSysId is not allowed (for example, the firstprogram of a transaction).

System action: The program is not run and thecondition PGMIDERR is raised.

User response: Check the Program Definition entry(PD) and Transaction Definition entry (TD) are correct.

Destination:

console.msg

ERZ015032E Transaction ’transId’ attempts to runprogram ’programName’ which isdisabled

Explanation: CICS attempts to run a program whosedatabase entry is marked as disabled.

System action: If this is the first program in thetransaction, CICS does not start that transaction. If not,CICS returns the PGMIDERR condition to the callingprogram.

User response: Reenable the program and run thetransaction again.

Destination:

console.msg

ERZ015033E Transaction ’transId’ attempts to runprogram ’programName’ which is notdefined in the database

Explanation: CICS attempts to run a program that isnot defined.

System action: If this is the first program in thetransaction, CICS does not start that transaction. If not,CICS returns the PGMIDERR condition to the callingprogram.

User response: Check the Transaction Definition entry(TD), Program Definition entry (PD) and anyapplication program used in the transaction with EXECCICS LINK or EXEC CICS XCTL commands for errors.

Destination:

CSMT

ERZ015034E CICS is unable to allocate Task-PrivatePool storage for Program Control datastructures

Explanation: CICS is unable to allocate storage fromthe Task-Private Pool, to hold the control informationrequired for running a new program.


User response: Resubmission of the transaction canpossibly work. If not, determine if the transaction isusing excessive amounts of Task-Private Pool (Getmain)storage and correct this.

Destination:

ERZ015028W • ERZ015034E


CSMT

ERZ015035E The load of language support program’fileName’ fails″

Explanation: CICS attempts to load a languagesupport program but fails. Language support programsare used by CICS to run application code written indifferent programming languages.

System action: If the attempt to load the C languagesupport program fails, the region is terminated withabend code U1517. If the attempt to load anotherlanguage support program fails, the transaction isterminated with abend code A15A.

User response: Look up any error number in errno.hand investigate the cause using the symptom records, ifany are available. Check the program being loaded is avalid executable and is accessible. This error can alsooccur if a component of the program is not available,for example, if an Acu COBOL installation is not in/opt/acu which is where CICS expects to find it, thenAcu COBOL program loads will fail. Considerreinstalling the program. Also check the transaction forvery deep levels of EXEC CICS LINKs. If the problemcannot be solved and persists, then save any dump fileproduced and contact your support organization.

Destination:

console.msg

ERZ015036E Cannot complete Resource DefinitionOnline (RDO) command for program’programName’

Explanation: CICS cannot delete the details of thenamed program in all of the region’s ApplicationServers.


User response: Examine the CICS message files forfurther information relating to this message. If thedelete system RDO command failed because of ashortage of task private storage, retry the RDO at alater time, when the system is more lightly loaded.Also consider simplifying your transactions, so thatthey use less task private storage. If the RDO commandfailed because of a shortage of region storage, retry theRDO command at a later time, when the region isrunning fewer transactions. Further consider increasingthe amount of region storage available to your regionby amending the MaxRegionPool attribute of theRegion Definition (RD). If the problem persists, or theRDO command has had no perceivable effect, considerperforming an automatic start of your region, since theApplication Servers are possibly in an inconsistentstate.

Destination:

console.msg

ERZ015037E Exception caught for user exit(’userExitName’) ″

Explanation: The attempt to invoke or execute a CICSuser exit was unsuccessful.


User response: There are two possible causes. Eitherthe attempt to invoke the user exit program wasunsuccessful (signal 4) or there was a processingexception in the user exit program (signal 11). Examinethe RCA user exit table and TCA user exit table in adump to determine the status of the user exit; examinetrace to determine the parameters passed to the userexit and consider inserting debugging information inthe user exit program (user exit workarea can be usedfor this). Ensure that the rules for writing user exitprograms were followed.

Destination:

console.msg

ERZ015038W PD stanza for Program ’programName’has an invalid UserExitNumber’userExitNumber’ ″

Explanation: An invalid value was specified for theuser exit number

System action: CICS installs the PD stanza entry; butno user exit is activated

User response: Uninstall the PD stanza, alter theUserExitNumber to a valid value and reinstall the PDstanza entry into the run-time. This results in the userexit being activated for any new Application Servers. Itis, however, advisable to shut down and restart theCICS region when changes are made to the PD stanzafor exit programs.

Destination:

console.msg

ERZ015039W PD stanza - Program ’programName’ foruser exit ’userExitNumber’(’userExitName’)defined as remote″

Explanation: The user exit program MUST be definedas local on this CICS region


User response: Uninstall the PD stanza, alter the PDstanza and reinstall the PD stanza entry into therun-time. This results in the user exit being activatedfor any new Application Servers. It is, however,advisable to shutdown and restart the CICS regionwhen changes are made to the PD stanza for exitprograms.

Destination:

ERZ015035E • ERZ015039W


console.msg

ERZ015040W PD stanza - Program ’programName’ foruser exit ’userExitNumber’(’userExitName’)not a C program or does not exist″

Explanation: Either the program is not a C programor the Path is invalid.


User response: Ensure that the program exists in thespecified library and is a C program. Uninstall the PDstanza, alter the PD stanza and reinstall the PD stanzaentry into the run-time. This results in the user exitbeing activated for any new Application Servers. It is,however, advisable to shutdown and restart the CICSregion when changes are made to the PD stanza forexit programs.

Destination:

console.msg

ERZ015041W Processing request to replace program’programName’ with ’programName2’ foruser exit ’userExitNumber’(’userExitName’)″

Explanation: The user exit is already active for theCICS region. Only one program can be associated witha user exit at this release of CICS.

System action: CICS replaces the user exit programfor all new Application Servers; any existingApplication Server continues to use the previous userexit program.

User response: Determine whether this is by accidentor by intent.

Destination:

console.msg

ERZ015042W Program ’programName’ now associatedwith user exit ’userExitNumber’(’userExitName’)

Explanation: The user exit is activated for the CICSregion.

System action: If this is during CICS regioninitialization then the program is now activated at thisuser exit in all Application Servers; if during run-timethen the program is activated at this user exit for allnew Application Servers, but any existing ApplicationServers are reactivated for the program associated withthis user exit when the Application Server wasinitialized.

User response: None

Destination:

console.msg

ERZ015043W Attempt to associate program’programName’ with user exit’userExitNumber’ failed.″

Explanation: Refer to previous messages for anexplanation.

System action: The user exit is not activated for theCICS region.

User response: None

Destination:

console.msg

ERZ015044W Program ’programName’ no longerassociated with user exit’userExitNumber’(’userExitName’) ″

Explanation: The user exit is de-actived for the CICSregion.

System action: The PD stanza for the programassociated with the user exit is uninstalled.

User response: None

Destination:

console.msg

ERZ015045W Attempt to load program ’programName’for user exit’userExitNumber’(’userExitName’) failed″

Explanation: The program associated with the userexit failed to load when initializing a new ApplicationServer.

System action: The user exit is de-activated for theregion.

User response: Refer to previous ERZ5802 messagesfor further information. Ensure that the program existsin the library that was specified on the Path in the PDstanza for the program. Ensure that the guidelines fornaming the entry point for the application werefollowed for this platform. If the user exit program wasnot compiled by using the supplied sample makefile,compare the makefiles to ensure that there are nosignificant differences that are able to cause a loadfailure. It is advisable to shutdown and restart the CICSregion when changes are made to the PD stanza forexit programs.

Destination:

console.msg

ERZ015040W • ERZ015045W


ERZ015046E Unable to allocate storage for user exit50 (UE015050) parameter list.

Explanation: A request to obtain storage in that tobuild a parameter list for user exit 50 (UE015050) failed.


User response: Produce a SNAP dump and investigatestorage usage in the CICS region; consider increasingthe amounts of storage available to CICS using theregion definition parameters.

Destination:

console.msg

ERZ015047W User exit 50 (UE015050) has returned anunrecognized return code, whileattempting to route a link request forprogram ’programName’.

Explanation: This error message is produced if thedynamic Distributed Program Link (DPL) user exit(UE015050) does not return a recognized return code.

System action: The link request made for program’programName’ stops normally. Other processingcontinues.

User response: Ensure that your dynamic DPL userexit program returns a valid return code.

Destination:

console.msg

ERZ015048W User exit ’userExitNumber’(’userExitName’) has an incorrect versionof the ’userExitStructure’ user exitstructure. The user exit has beendisabled.

Explanation: A user exit structure referenced by theuser exit program has an incorrect version number,when compared to the version number used by CICS.This means that the structure used by the user exit waschanged since the user exit program was compiled. Theversion number test is performed by the user exitprogram and this message is only issued if the user exitprogram returned either UE_SpecificVersion orUE_HeaderVersion. The user exit is disabled for thisapplication server.

System action: The user exits default action is taken,and the user exit is disabled.

User response: Obtain the latest version of cicsue.h.This contains both the user exit specific and standardstructures. Ensure that the user exit is compiled byusing the latest version of cicsue.h. Check any fieldsused by the user exit program that are contained in astructure that has changed. A changed version numberindicates that the structure has changed since the

previous version. If cicsue.h was not updated since theuser exit program was compiled, check that the userexit program is returning either UE_SpecificVersion orUE_HeaderVersion for the correct reason.

Destination:

console.msg

ERZ015049E Cannot get the default Programdefinition. Autoinstall for program’Tobedetermined’ failed.

Explanation: The default entry that is in the PD stanzafile is either missing or has an error. The attempt toautoinstall this program cannot continue.

System action: The program is not installed, andcontrol is returned to the caller with an error response.

User response: Check whether the default entry existsin the Program Definitions (PD). Reinitialize the userexit, either by using the EXEC CICS SET SYSTEMPROGAUTOEXIT api, or by restarting the CICS region.

Destination:

console

ERZ015050E Cannot add an entry to the runtimedatabase. Autoinstall for program’programName’ failed.

Explanation: Cannot add the runtime programdefinition entry. Autoinstall of the program returnswith an error.

System action: CICS raises the PGMIDERR condition.

User response: Look for earlier messages that mightexplain the cause of this error, then take appropriateaction..

Destination:

console

ERZ015051E CICS cannot allocate region poolstorage. Autoinstall for program’Tobedetermined’ failed.

Explanation: cannot allocate storage from the regionpool for the default program definition (PD).

System action: The program autoinstall does notcontinue because the default PD entry is not available.

User response: Because memory in the region pool iscontinually being acquired and freed by CICS on behalfof running transactions,resubmission of this transactionmight be successful.If this problem remains when youresubmit the transaction,check whether any transactionis looping in some way that causes CICS to acquirelarge amounts of Region Pool memory on itsbehalf.Consider increasing the size of the Region Poolby restarting the region with an override for the value

ERZ015046E • ERZ015051E


of the MaxRegionPool attribute in the RegionDefinition (RD).

Destination:

console

ERZ015052E CICS is unable to allocate storage tohold a CHANNEL during an EXECCICS RETURNTRANSID(’Tobedetermined’)

Explanation: CICS is unable to allocate storage fromthe Task-Shared Pool for a CHANNEL to be passed toanother transaction via an EXEC CICS RETURN.


User response: Because memory in the Task-SharedPool is continually being acquired and freed byrunning transactions, resubmission of this transactioncan possibly be successful. If this problem persistswhen you resubmit the transaction, check whether anytransaction is using large amounts of Task-Sharedstorage. Finally, consider increasing the size of theTask-Shared Pool by restarting the region with anoverride for the value of the MaxTSHPool attribute inthe Region Definition (RD).

Destination:

CSMT

ERZ015053W CICSAppProbe configuration file’fileName’ is missing

Explanation: The configuration file required forCICSAppProbe facility is missing.

System action: CICSAppProbe facility will bedisabled.

User response: Check if the CICSAppProbe.cfg fle ispresent in the region directory . If present, check thepermissions. Required file permissions are -rw-rw----and owner group are cics:cics.

Destination:

console

ERZ015054E CICSAppProbe facility is now disabled

Explanation: CICSAppProbe facility has beendisabled.

System action: CICS has found an invalid conditionand disabled CICSAppProbe facility.


Destination:

console

ERZ015055W Invalid option’optionNamelineNumberfileName’ found inline ’optionNamelineNumberfileName’ ofCICSAppProbe configuration file’optionNamelineNumberfileName’

Explanation: There is a syntax error in one of theoptions specified in CICSAppProbe configuration file.

System action: CICS attempts to read the next line inthe configuration file and continues.

User response: Correct the invalid option in theconfiguration file. Refer to documentation for furtherinformation.

Destination:

console

ERZ015056W Invalid value’valueoptionNamelineNumberfileName’found for option’valueoptionNamelineNumberfileName’ inline ’valueoptionNamelineNumberfileName’of CICSAppProbe configuration file’valueoptionNamelineNumberfileName’,hence setting default value

Explanation: One of the options in CICSAppProbeconfiguration file has an invalid value.

System action: CICS assumes the default value for theoption and continues.

User response: Correct the invalid value for theoption in the configuration file. Refer to documentationfor further information.

Destination:

console

ERZ015057W Invalid value’valueoptionNamelineNumberfileName’found for option’valueoptionNamelineNumberfileName’ inline ’valueoptionNamelineNumberfileName’of CICSAppProbe configuration file’valueoptionNamelineNumberfileName’,hence ignoring the value

Explanation: One of the options in CICSAppProbeconfiguration file has an invalid value.

System action: CICS ignores this invalid value for theoption and continues with other valid values for theoption.

User response: Correct the invalid value for theoption in the configuration file. Refer to documentationfor further information.

Destination:

console

ERZ015052E • ERZ015057W


ERZ015058W Unable to allocate ’memorySizefileNamed’bytes of memory for ring buffer asrequested in CICSAppProbeconfiguration file ’memorySizefileName’

Explanation: CICS is unable to allocate the memoryfor ring buffer as requested in CICSAppProbeconfiguration file.


User response: Retry at a later time.

Destination:

console

ERZ015059W Unable to write CICSAppProbe outputfile ’fileNameerrno’,errno ’fileNameerrno’

Explanation: CICS attempted to create and then writeto output file,but the command failed with an error.


User response: Check if you have the necessarypermissions to create and write to the file in thespecified directory. Check also that the file system isnot full. If this fails, then check errno for moreinformation.

Destination:

console

ERZ015060I CICSAppProbe facility is enabled.Settings are based on the configurationfile ’fileName’

Explanation: CICSAppProbe facility is enabled.Settings are based on the configuration file.



Destination:

console

ERZ016001E Abnormal termination U1601:Inconsistency detected in logical unit ofwork control structures

Explanation: The data structures used to drivesyncpoint processing are inconsistent.

System action: CICS terminates the region with codeU1601.

User response: Where this problem occurs duringnormal operation of a region, it can be cleared byauto-starting CICS. If the problem occurs during autostart following normal shutdown, perform a cold start.

Contact your support organization if the problempersists.

Destination:

console.msg

ERZ016002W Unsuccessful memory allocation forlogical unit of work control information

Explanation: CICS is unable to acquire Region Poolstorage for the data structures that control syncpointprocessing.

System action: CICS continues, but this message islikely to be followed by another that abnormallyterminates the task or region.

User response: When convenient, stop and auto startCICS with an increased Region Pool size by overridingthe MaxRegionPool attribute (RD) on the commandline. Do the same for the permanent database by usingcicsupdate.

Destination:

CSMT

ERZ016003W Unsuccessful memory allocation forlogical unit of work checkpointinformation

Explanation: The system was unable to acquiresufficient Task Private storage to hold the checkpointinformation for logical units of work.

System action: Checkpoint information is not logged,but CICS continues. If CICS suffers an immediateshutdown, recovery time is impaired. Log Serviceresource usage increases.

User response: Restart CICS (auto-start) when it isconvenient to do so. This action restores optimumrecovery performance and enables some Log Serviceresources to become available.

Destination:

console.msg

ERZ016004E Abnormal termination A164: Unable tostart a new logical unit of work

Explanation: CICS is unable to start a new logical unitof work. This message is preceded by another messageindicating the reason.

System action: The affected transaction is terminatedwith abend code A164. The application server is alsoterminated in order to reduce the possibility of furthertransactions being affected by this problem.

User response: Resubmit the affected transaction.Look at the preceding error messages to see whetherother user responses are advised.

Destination:

ERZ015058W • ERZ016004E


CSMT

ERZ016005E Abnormal termination A165: CICSinternal error

Explanation: CICS has detected an internal error thathas prevented a logical unit of work from starting orcontinuing.

System action: CICS continues after terminating theaffected transaction with abnormal termination codeA165 and terminating the relevant application serverprocess.

User response: Resubmit the affected transaction. Ifthe problem persists, contact your support organization.

Destination:

CSMT

ERZ016006E Abnormal termination U1606: Invalidinformation recovered from system log

Explanation: CICS has obtained invalid informationfrom the system log and is unable to complete recoveryprocessing.

System action: CICS is terminated with code U1606.

User response: See message ERZ2407E.

Destination:

console.msg

ERZ016007E Abnormal termination A16Y: Problemduring SYNCPOINT

Explanation: A problem was detected during aSYNCPOINT that renders the CICS Application Serverprocess unusable.

System action: CICS terminates the affectedApplication Server with code A16Y, backing out anyrecoverable work already performed. CICS alsoterminates the application server involved in order torelease resources and allow other tasks to continue.

User response: Resubmit the affected transaction.

Destination:

console.msg

ERZ016009E Abnormal termination A163:Unsuccessful memory allocation forlogical unit of work control information

Explanation: CICS is unable to acquire Region Poolstorage for the data structures needed to process anactive logical unit of work.

System action: CICS terminates the affectedtransaction with code A163, backing out anyrecoverable work already performed. CICS alsoterminates the application server involved in order to

release resources and allow other tasks to continue.

User response: Resubmit the affected transaction. Ifthe problem persists, stop and auto start CICS with anincreased Region Pool size by overriding theMaxRegionPool attribute (RD) on the command line.Do the same for the permanent database usingcicsupdate.

Destination:

CSMT

ERZ016010E Abnormal termination U1610:Unsuccessful memory allocation forlogical unit of work control information

Explanation: During system startup, CICS is unable toacquire sufficient Region Pool storage for the datastructures needed to process logical units of work.

System action: CICS is terminated with abend codeU1610.

User response: Restart CICS with an increased RegionPool size. This can be done by overriding theMaxRegionPool attribute (RD) on the command lineand using cicsupdate to update the permanentdatabase.

Destination:

console.msg

ERZ016011E Abnormal termination U1611: Unable torecover CICS resources correctly

Explanation: CICS is unable to recover CICS resourcesto the correct state. This message is preceded byanother message indicating the reason, which waspossibly sent to destination CSMT.


User response: See the preceding error message foradvice.

Destination:

console.msg

ERZ016012E Abnormal termination U1612: Theeffects of a committed transaction couldnot be re-applied during restart

Explanation: During recovery processing at systemstartup, the effects of a committed transaction wereunable to be reapplied. This message is preceded byanother message indicating the reason, which waspossibly sent to destination CSMT.


User response: See the preceding error message foradvice.

ERZ016005E • ERZ016012E


Destination:

console.msg

ERZ016014E Abnormal termination U1614: Unable torelease Region Pool storage

Explanation: CICS is attempting to release a block ofRegion Pool storage but is unsuccessful.

System action: CICS terminates with abnormaltermination code U1614.

User response: Restart CICS. If the problem persists,contact your support organization.

Destination:

console.msg

ERZ016016E CICS self-consistency checking hasdetected some missing data

Explanation: CICS has detected an error in the RegionControl Area (RCA) that cannot be corrected.

System action: CICS terminates the Region.


Destination:

console.msg

ERZ016017E CICS self-consistency checking hasdetected an unexpected signature’actualSignature’ in a memory structure ataddress structureAddress (expectedsignature is ’expectedSignature’)

Explanation: CICS has detected a signature fieldcontaining invalid data. This message is produced onlyfor memory structures obtained from the region pool sothis problem is not likely to be caused either by useraction or by user transactions.



Destination:

console.msg

ERZ016018E CICS self-consistency checking hasdetected inconsistent data in the UniqueApplication Identity Pool

Explanation: CICS has detected at least oneinconsistency in the Unique Application Identity Pool.Previous messages detail the inconsistencies detected.



Destination:

console.msg

ERZ016021E CICS self-consistency checking hasfound actualCountu transaction structuresattached to the control block located atstructureAddress (expected number isexpectedCountu)

Explanation: CICS has detected a mismatch between acounter field in a control block and the number ofelements that are attached.



Destination:

console.msg

ERZ016025E Abnormal termination U1625: RemoteProcedure Call (RPC) protocol ’protocol’is invalid; Reason ’reason’

Explanation: CICS is unable to start because theRemote Procedure Call (RPC) runtime system hasrejected a request from CICS to use the named protocol.


User response: Verify that the RPC subsystem iscorrectly installed. Contact your support organizationfor further information.

Destination:

console.msg

ERZ016026E Abnormal termination A16Z: Unable toinitialize application server

Explanation: CICS is unable to complete theinitialization of an application server. This message ispossibly preceded by a warning message describing theproblem in more detail.

System action: CICS terminates the application serverwith code A16Z.

User response: None. If this problem persists and iscausing response delays, contact your supportorganization.

Destination:

console.msg

ERZ016030W Unsuccessful memory allocation fromtask-private storage

Explanation: CICS is attempting to acquire a bufferfrom task-private storage, but is unable to do sobecause there is insufficient memory available. At the

ERZ016014E • ERZ016030W


time this message is produced, CICS is performingrecovery processing or server initialization and no usertransactions are permitted to run. This means that all ofthe task private storage pool (which is of fixed size)must be available to CICS for its own use.

System action: CICS continues, but it is likely thatadditional messages follow and that the region orserver is terminated.

User response: Cold start CICS and report theproblem to your support organization.

Destination:

console.msg

ERZ016033E Abnormal termination U1633: Unable toreprepare a logical unit of work

Explanation: CICS has encountered an internalproblem while attempting to reprepare a logical unit ofwork. Recovery processing cannot continue.



Destination:

console.msg

ERZ016035W Unable to initialize TransactionalRemote Procedure Call (TRPC) service

Explanation: CICS is unable to initialize theTransactional Remote Procedure Call (TRPC) service ina CICS server process.

System action: CICS continues but quickly terminateseither the application server process involved or theregion if the process is a recovery process. Furthermessages are produced.


Destination:

console.msg

ERZ016036W Unexpected problem reading system logduring recovery

Explanation: CICS encountered a problem reading thesystem log during recovery processing.

System action: CICS continues but quickly terminatesthe region. Further messages are produced.


Destination:

CSMT

ERZ016039E Abnormal termination U1639:Transactional Remote Procedure Call(TRPC) service could not be initialised.

Explanation: CICS is unable to initialize theTransactional Remote Procedure Call (TRPC) service ina CICS server process.



Destination:

console.msg

ERZ016044E Abnormal termination U1644: Unable toregister External XA-compliant ResourceManager with the Transaction Manager

Explanation: CICS is unable to register anXA-compliant resource manager with the TransactionManager XA Service because of an internal problem inthe Transaction Manager XA Service code.

System action: The application server is abnormallyterminated with code U1644.

User response: There is a limit to the number ofXA-compliant resource managers that can be registeredwith the Transaction Manager XA Service. Try reducingthe number registered to see if this is the cause of theproblem. If the problem persists, or if you need toregister so many XA-compliant resource managers,contact your support organization.

Destination:

console.msg

ERZ016045E Abnormal termination U1645: Unable toinitialize the Transaction Manager XAService

Explanation: CICS is unable to initialize theTransaction Manager XA Service due to an internalproblem in the Transaction Manager Service code.


User response: This is an internal problem to CICS.Contact your support organization.

Destination:

console.msg

ERZ016046E Abnormal termination U1646: Unable tofind or access an External ResourceManager’s XA Support file

Explanation: CICS cannot locate, or does not havesufficient permissions to access, an XA Support module

ERZ016033E • ERZ016046E


for an External Resource Manager.


User response: Check that all SwitchLoadFileattributes in the XAD database definitions refer to realfiles and that these files are readable and executable bythe userid cics. If any attributes are incorrect modifythem using the Resource Definitions Online (RDO)commands cicsget, cicsdelete and cicsadd, orcicsupdate. If the file access permissions are incorrect,correct them and restart the transaction.

Destination:

console.msg

ERZ016047E Abnormal termination U1647: Unable toload an External Resource Manager XASupport file

Explanation: CICS is unable to load an ExternalResource Manager’s XA Support file into theapplication server.


User response: Check that you have built the switchload file correctly. Rebuild it to make sure. If theproblem persists, contact your support organization

Destination:

console.msg

ERZ016048E Abnormal termination A16E: Unable toallocate storage for registration of anExternal Resource Manager

Explanation: CICS is unable to allocate Region Poolstorage for the registration of an External ResourceManager.

System action: The application server is abnormallyterminated with code A16E.

User response: When convenient, stop and auto startCICS with an increased Region Pool size by overridingthe MaxRegionPool attribute (RD) on the commandline. Do the same for the permanent database usingcicsupdate.

Destination:

console.msg

ERZ016049E Abnormal termination A162: Unable tostart a new Logical Unit of Work

Explanation: CICS is unable to start a new logical unitof work in a particular application server. A new logicalunit of work was obtained from the TransactionManager, but it was already abnormally ended beforeCICS made it ready for use.

System action: The application server is abnormallyterminated with code A162.

User response: Check that all Structured File Serversand Distributed Transaction Processing (DTP) clientsare still running. Restart any that have failed. If theproblem persists, contact your support organization.

Destination:

CSMT

ERZ016050W Logical unit of work for transaction’transId’ has been backed out;Distributed Transaction Service (TRAN)reason ’abendReason’

Explanation: A logical unit of work for transaction’transId’ was backed out by CICS. This message isproduced only when the logical unit of work is backedout and there is no commit in progress. The message isnot produced when CEMT TASK PURGE orFORCEPURGE is used on the transaction as in this casemessage ERZ1663W is produced instead. It canpossibly be caused by the failure of CICS Toolkitcomponents, such as Structured File Servers or LOGservers, or by the failure of other DistributedTransaction Processing (DTP) clients, such as relationaldatabase managers, during the logical unit of work.Note that this message is produced whenever EXECCICS SYNCPOINT ROLLBACK is issued as a normalaction by a CICS application program.

System action: CICS continues, but it is likely thatfurther messages follow to terminate the transaction.

User response: Check that all Structured File Servers,log servers and Distributed Transaction Processing(DTP) clients are still running. Restart any that havefailed. If the problem is anything other than one ofthose categorized as a ’Client-Specified Abort’ and theproblem persists, contact your support organization.

Destination:

CSMT

ERZ016051E Abnormal termination U1651: Exception’exceptionText’ caught

Explanation: CICS has detected an unexpected fatalexception.

System action: CICS terminates the region with abendcode U1651.

User response: This is an internal problem in CICSthat cannot be caused by the user. If the problempersists, contact your support organization.

Destination:

console.msg

ERZ016047E • ERZ016051E


ERZ016052W Initiating abnormal termination oflogical unit of work ’tid’(GTID=’globalTid’, LUWID=’LUWid’,Transaction=’transId’, TermId=’termId’,UserId=’userId’)

Explanation: CICS is initiating the abnormaltermination of logical unit of work ’tid’. Generally thisarises because of a CEMT TASK PURGE orFORCEPURGE operation is being carried out on thelogical unit of work, but it can possibly also be causedby internal errors in CICS or by errors in userapplication code that cause the transaction to endabnormally (without an explicit syncpoint).

System action: CICS abnormally terminates the logicalunit of work.

User response: None. Other messages indicate thereason why the logical unit of work is beingabnormally terminated.

Destination:

CSMT

ERZ016053W Initiating forced backout of logical unitof work ’tid’ (GTID=’globalTid’,LUWID=’LUWid’, Transaction=’transId’,TermId=’termId’, UserId=’userId’)

Explanation: CICS is performing a CEMT SET TASKFORCEPURGE on a transaction that is in syncpoint,but where the outcome of the syncpoint is in doubt.The transaction is specified in the TransactionDefinition (TD) database with an InDoubt attribute ofWAIT_BACKOUT. CICS is therefore forcing the logicalunit of work to backout, before ending the associatedtransaction. If the transaction is distributed and otherparts of it commit heuristic damage occurs.

System action: Logical unit of work ’tid’ is forciblybacked out.

User response: None

Destination:

CSMT

ERZ016054W Initiating forced finish of logical unit ofwork ’tid’ (GTID=’globalTid’,LUWID=’LUWid’, Transaction=’transId’,TermId=’termId’, UserId=’userId’)

Explanation: CICS is performing a CEMT SET TASKFORCEPURGE on a transaction that is still in syncpointeven though the local outcome of the syncpoint isknown. In this situation, CICS forcibly finishes theidentified logical unit of work. Once the logical unit ofwork is finished it is not possible to detect and reportheuristic damage (situations in which parts of adistributed transaction have committed and other partshave backed out).

System action: The logical unit of work is forciblyfinished. Ability to detect and report on heuristicdamage affecting the associated transaction is lost.

User response: None

Destination:

CSMT

ERZ016055E Abnormal termination U1655: Unable toterminate logical unit of work ’tid’(GTID=’globalTid’, LUWID=’LUWid’,Transaction=’transId’, TermId=’termId’,UserId=’userId’)

Explanation: CICS is unable to terminate logical unitof work ’tid’, because although the logical unit of workis in syncpoint, it is not in doubt and is not in a statewhere it can be forcibly finished.

System action: This is an internal error condition soCICS terminates the region with abend code U1655.

User response: Auto start your region. If the problempersists, contact your support organization.

Destination:

CSMT

ERZ016056W Heuristic damage detected for logicalunit of work ’tid’ (GTID=’globalTid’,LUWID=’LUWid’, Transaction=’transId’,TermId=’termId’, UserId=’userId’)

Explanation: CICS has detected heuristic damageaffecting the logical unit of work ’tid’. This means thatsome parts (logical units of work) of the transactionhave committed while other parts have backed out.

System action: None

User response: Depending on the transaction involvedyou can possibly be prepared to ignore this situation.Instead you can restore the state of database entriesand CICS resources manually so as to fully commit orfully backout the changes made by the transaction.

Destination:

CSMT

ERZ016057W Cannot obtain global transactionidentifier for logical unit of work ’tid’(Transaction=’transId’, TermId=’termId’,UserId=’userId’), reason reason

Explanation: CICS is unable to obtain a globaltransaction identifier for the specified logical unit ofwork.

System action: CICS continues, but if heuristicdamage occurs for the logical unit of work, or if itsoutcome is forced (for example by using CEMT SETTASK FORCEPURGE on the associated transaction),

ERZ016052W • ERZ016057W


then CICS is unable to display the global transactionidentifier in the warning messages produced.

User response: None. This problem makes it muchmore difficult to identify other logical units of workinvolved in the distributed transaction and so canpossibly affect your ability to take remedial action ifthis becomes necessary. If this problem occurspersistently, contact your support organization.

Destination:

CSMT

ERZ016058W Initiating forced commit of logical unitof work ’tid’ (GTID=’globalTid’,LUWID=’LUWid’, Transaction=’transId’,TermId=’termId’, UserId=’userId’)

Explanation: CICS is performing a CEMT SET TASKFORCEPURGE on a transaction that is in syncpoint,but where the outcome of the syncpoint is in doubt.The transaction is specified in the TransactionDefinition (TD) database with an InDoubt attribute ofWAIT_COMMIT. CICS is therefore forcing the logicalunit of work to commit before ending the associatedtransaction. If the transaction is distributed and otherparts of it backout then heuristic damage occurs.

System action: Logical unit of work ’tid’ is forciblycommitted and the associated transaction is thenabnormally terminated (another message accompaniesthe abnormal termination).

User response: None

Destination:

CSMT

ERZ016061I Application server serverId is repreparinglogical unit of work ’tid’

Explanation: CICS application server serverId isattempting to reprepare logical unit of work ’tid’.

System action: None

User response: None

Destination:

console.msg

ERZ016063W Logical unit of work for transaction’transId’ has been forcibly backed out

Explanation: A logical unit of work for transaction’transId’ was backed out by CICS. This can happeneither in response to a CEMT SET TASK FORCEPURGEcommand, or during abnormal termination of the task.

System action: CICS continues, but further messagesfollow to terminate the transaction.

User response: None

Destination:

CSMT

ERZ016064I Application manager is waiting forapplication servers to replay log records

Explanation: The CICS application manager is waitingfor the application servers it has started to replay therelevant prepare records thereby repreparingthemselves.

System action: None

User response: None

Destination:

console.msg

ERZ016065I Application server serverId has resolvedits transactions

Explanation: CICS application server serverId hasresolved its transactions and is now signallingcompletion to the application manager.

System action: None

User response: None

Destination:

console.msg

ERZ016070W Unable to release storage buffer ataddress bufferAddress

Explanation: An error occurred while attempting torelease task private storage; the storage was notsuccessfully deallocated.

System action: CICS is already processing an error(see accompanying messages) and so the error handlingbeing performed is continued.

User response: Check the CSMT log or console.msgfile for associated information. If other messagesindicate that the problem is an internal error in CICS,contact your support organization.

Destination:

console.msg

ERZ016071E Abnormal termination U1671: Unable torelease task private storage buffer

Explanation: An error occurred while attempting torelease task private storage; the storage was notsuccessfully deallocated.


User response: Check the CSMT log or console.msgfile for associated information. If other messagesindicate that the problem is an internal error in CICS,

ERZ016058W • ERZ016071E


contact your support organization.

Destination:

console.msg

ERZ016072E Abnormal termination U1672:Application Server terminatedunexpectedly during recoverable work

Explanation: CICS has detected the unexpectedtermination of an application server that wasprocessing unfinished recoverable work. This canpossibly be caused by a CICS internal error, or theprocess was possibly terminated by a SystemAdministrator. It can possibly also be caused by atransaction that is coded to terminate processes.


User response: Check the CSMT log or console.msgfile for associated information. If other messagesindicate that the problem is an internal error in CICS,contact your support organization. Restart the region. Ifyou suspect an internal problem with CICS, first makesure that the region is configured to produce a dump.

Destination:

console.msg

ERZ016073I Application server serverId is repreparinglogical unit of work ’tid’ for transaction’transId’, user ’userId’

Explanation: CICS application server serverId isattempting to reprepare logical unit of work ’tid’ thatwas originally transaction ’transId’ run for user ’userId’.

System action: None

User response: None

Destination:

console.msg

ERZ016074W A transaction has been rolled backbecause the prepare phase timed outduring syncpoint processing. CICS maybe temporarily overloaded

Explanation: A transaction was rolled back becausethe prepare phase timed out during syncpointprocessing. This can be caused by a heavily loadedsystem or by a failure during syncpoint of a componentin a distributed Logical Unit of Work.

System action: A transaction was rolled back.

User response: Refer to other messages that wereissued to console.msg. Check all components in thelogical unit of work for a failure. If the problem isbelieved to be due to system loading, then retry thetransaction when system load has reduced and consult

the sections on performance in the CICS AdministrationGuide for information about how to monitor andbalance system load.

Destination:

console.msg

ERZ016075E Abnormal termination U1675: Unable toattach shared memory, reason reason

Explanation: CICS is unable to attach shared memoryto the finished function registered with the DistributedTransaction Service (TRAN).

System action: CICS terminates the region withabnormal termination code U1675.

User response: None. If the problem persists, contactyour support organization.

Destination:

console.msg

ERZ016076E Unable to allocate storage for user exit51 (UE016051) parameter list.



User response: Produce a SNAP dump and investigatestorage usage in the CICS region; consider increasingthe amounts of storage available to CICS using theregion definition parameters.

Destination:

console.msg

ERZ016077W User exit 51 (UE016051) has returned anunrecognized return code.

Explanation: This error message is produced if theSyncpoint user exit (UE016051) does not return arecognized return code.

System action: The syncpoint request continuesnormally.

User response: Ensure that your Syncpoint user exitprogram returns a valid return code.

Destination:

console.msg

ERZ016078E An error has occurred loading theProduct Definitions

Explanation: This error message is produced when afailure has occurred while CICS was trying to load theProduct Definitions.

ERZ016072E • ERZ016078E


System action: CICS abnormally terminates with codeU1678.

User response: Examine preceeding messages todiagnose the problem.

Destination:

console.msg

ERZ016079I DB2 loaded as filesystem

Explanation: CICS has successfully loaded DB2 foruse as its filesystem.



Destination:

console.msg

ERZ016080I SFS loaded as filesystem

Explanation: CICS has successfully loaded SFS for useas its filesystem.



Destination:

console.msg

ERZ016081E Unsuccessful load of DB2 as filesystemwith return code returnCode

Explanation: This error message is produced when afailure has occurred while CICS was trying to load theDB2 as the filesystem.



Destination:

console.msg

ERZ016082E Unsuccessful load of SFS as filesystemwith return code returnCode

Explanation: This error message is produced when afailure has occurred while CICS was trying to load theSFS as the filesystem.



Destination:

console.msg

ERZ016083E Filesystem switch file for DB2 could notbe found

Explanation: This error message is produced when theswitchload file is missing.


User response: On UNIX the file is called cicsswdb2.On Windows NT the file is called cicsswdb2.dll. CICSexpects to find the file in directory prodDir/bin. Ensurethat it is there.

Destination:

console.msg

ERZ016084E Filesystem switch file for SFS could notbe found



User response: On UNIX the file is called cicsswsfs.On Windows NT the file is called cicsswsfs.dll. CICSexpects to find the file in directory prodDir/bin. Ensurethat it is there.

Destination:

console.msg

ERZ016086E Unsuccessful load of Oracle asfilesystem with return code returnCode

Explanation: This error message is produced when afailure has occurred while CICS was trying to loadOracle as the filesystem.



Destination:

console.msg

ERZ016087E Filesystem switch file for Oracle couldnot be found



User response: On UNIX the file is called cicsswora.CICS expects to find the file in directory prodDir/bin.Ensure that it is there.

Destination:

ERZ016079I • ERZ016087E


console.msg

ERZ016088I Oracle loaded as filesystem

Explanation: CICS has successfully loaded Oracle foruse as its filesystem.



Destination:

console.msg

ERZ016095E CICS self-consistency checking hasdetected inconsistent data in the UniqueListener Identity Pool

Explanation: CICS has detected at least oneinconsistency in the Unique Listener Identity Pool.Previous messages detail the inconsistencies detected.



Destination:

console.msg

ERZ016098E Server side transaction support is onlypossible with an SFS file system

Explanation: The Region Definitions attributeServerSideTran was set to yes but the facility is notsupported with the file system specified by theFileSystemType attribute.

System action: CICS startup processing continues, butthe region does not use server-side transaction support.

User response: Alter the Region Definitions attributeServerSideTran and restart the CICS region.

Destination:

console.msg


Explanation: The data structures used to drive atransaction are inconsistent. One of the reasons for thisinconsistency could be an asynchronous abort duringthe transaction run.

System action: CICS terminates the application serverwith code A167. The transaction running at this pointin time will fail.

User response: If required, resubmit the transaction.See the additional error messages produced for furtherinformation. Retry the transaction and call IBM Serviceif the problem persists.

Destination:

console.msg

ERZ016100I Application manager is waiting forapplication server serverId to replay logrecords

Explanation: One of the CICS application managerthread is waiting for the application server it hasstarted to replay the relevant prepare records therebyrepreparing themselves.

System action: None

User response: None

Destination:

console

ERZ017001E The CICS Action Table contains invaliddata

Explanation: The table holding information aboutactive ABEND, Attention IDentifier (AID), andcondition handlers, in the Region Pool, contains invaliddata.

System action: The transaction and the applicationserver in which it is running are both terminated withabend code A171, but the CICS region continues.

User response: Because the Action Table is held in theRegion Pool it is unlikely that the invalid data wasproduced by application code. It is possible that thereare further inconsistencies in the Region Pool; CICSself-consistency checking transaction usually detectsthis. If the transaction produces a dump file, save it forpossible use by your support organization. If theproblem persists, contact your support organization.

Destination:

CSMT

ERZ017002W Unexpected Attention IDentifier (AID)specified - value: AIDvalue

Explanation: The named AID is specified on an EXECCICS HANDLE AID. CICS does not support this AID.

System action: The transaction continues and CICSinterprets the command as if the AID was not specified.

User response: Correct the program.

Destination:

console.msg

ERZ017003W Unexpected condition specified - value:AIDvalue

Explanation: The given condition was specified on anEXEC CICS HANDLE CONDITION or EXEC CICS

ERZ016088I • ERZ017003W


IGNORE CONDITION command. CICS does notsupport this condition.

System action: The transaction continues and CICSinterprets the command as if the condition was notspecified.

User response: Correct the program.

Destination:

console.msg

ERZ017005E No memory available for Action Table

Explanation: CICS was unable to acquire storage tocreate a new Action Table from the Region Pool. Thistable holds information about active ABEND, AttentionIDentifier (AID), and condition handlers.


User response: Because memory in the Region Pool iscontinually being acquired and freed by CICS on behalfof running transactions, resubmission of thistransaction can possibly be successful. If this problempersists when you resubmit the transaction, checkwhether it is looping in some way that causes CICS toacquire substantial amounts of Region Pool memory onits behalf; for example, check the depth of EXEC CICSLINKs in the program, as an Action Table is built foreach logical level. Finally, consider increasing the sizeof the Region Pool by restarting the region with anoverride for the value of the MaxRegionPool attributein the Region Definition (RD).

Destination:

CSMT

ERZ017006E Program ’programName’ issued too manyEXEC CICS POP HANDLE commands

Explanation: The named application program issuedmore EXEC CICS POP HANDLE commands thanEXEC CICS PUSH HANDLE commands.

System action: CICS returns an INVREQ condition tothe application and the transaction continues.

User response: Correct the named program.

Destination:

console.msg

ERZ017007E The stack of Action Tables has invaliddata

Explanation: The stack of tables holding informationregarding active ABEND, Attention IDentifier (AID), orcondition handlers for the transaction at each logicallevel contains invalid data.

System action: The transaction and the application

server in which it is running are both terminated withabend code A177, but the CICS region continues.

User response: Because the Action Tables are held inthe Region Pool it is unlikely that the invalid data wasproduced by application code. It is possible that thereare further inconsistencies in the Region Pool; CICSself-consistency checking transaction usually detectsthis. If the transaction produces a dump file, save it forpossible use by your support organization. If theproblem persists, contact your support organization.

Destination:

CSMT

ERZ017008E Invalid program ’programName1’specified as an ABEND handler byprogram ’programName2’

Explanation: An EXEC CICS HANDLE ABENDPROGRAM command specified an invalid program asthe ABEND handler. The program is invalid because itis not defined in the Program Definition (PD) database,or it is disabled, or it has a remote system identifierattribute in the Program Definition database entry.

System action: CICS returns the PGMIDERR conditionto the application and the transaction continues.

User response: Correct the Program Definition orenable the program, as appropriate.

Destination:

console.msg

ERZ017009E No memory available for AttentionIDentifier (AID) handling table

Explanation: CICS was unable to acquire storage tocreate a new table for storing AIDs handlers from theRegion Pool. This occurred during an EXEC CICSHANDLE AID command.


User response: Because memory in the Region Pool iscontinually being acquired and freed by CICS on behalfof running transactions, resubmission of thistransaction can possibly be successful. If this problempersists when you resubmit the transaction, checkwhether it is looping in some way that causes CICS toacquire substantial amounts of Region Pool memory onits behalf; for example, check the depth of EXEC CICSLINKs in the program, as Region Pool storage isrequired for each logical level. Finally, considerincreasing the size of the Region Pool by restarting theregion with an override for the value of theMaxRegionPool attribute in the Region Definition(RD).

Destination:

ERZ017005E • ERZ017009E


CSMT

ERZ017010E No memory available for conditionhandling table

Explanation: CICS was unable to acquire storage tocreate a new table for storing condition handlers fromthe Region Pool. This occurred during either an EXECCICS HANDLE CONDITION or an EXEC CICSIGNORE CONDITION command.

System action: The transaction and the applicationserver in which it is running are both abnormallyterminated with abend code A17A, but the CICS regioncontinues.

User response: Because memory in the Region Pool iscontinually being acquired and freed by CICS on behalfof running transactions, resubmission of thistransaction can possibly be successful. If this problempersists when you resubmit the transaction, checkwhether it is looping in some way that causes CICS toacquire substantial amounts of Region Pool memory onits behalf; for example, check the depth of EXEC CICSLINKs in the program, as Region Pool storage isrequired for each logical level. Finally, considerincreasing the size of the Region Pool by restarting theregion with an override for the value of theMaxRegionPool attribute in the Region Definition(RD).

Destination:

CSMT

ERZ017011E Program ’programName’ issued an EXECCICS HANDLE ABEND RESETcommand without previously issuing anEXEC CICS HANDLE ABENDcommand

Explanation: See message.

System action: CICS terminates the transaction withan abend code of APCT.

User response: Check the program and correct it.

Destination:

CSMT

ERZ017012E Program ’programName’ received anunexpected condition conditionNumber

Explanation: A program received a condition that isnot a CICS condition.


User response: If the transaction produces a dumpfile, save it for possible use by your supportorganization. If the problem persists, contact yoursupport organization.

Destination:

CSMT

ERZ017013E Transaction abnormally terminated dueto error in condition handling

Explanation: A program issued an EXEC CICSHANDLE ABEND RESET command without anyprevious HANDLE ABEND command, or the programencountered an unexpected condition. Earlier logmessage ERZ1711E or ERZ1712E contains more details.


User response: Take the action for either ERZ1711E orERZ1712E, depending on which message was loggedearlier.

Destination:

CSMT

ERZ017014E Access denied to program’programName1’, specified as an ABENDhandler by user ’userId’ in program’programName2’

Explanation: An EXEC CICS HANDLE ABENDPROGRAM command specified a program to which theuser does not have security access.

System action: CICS returns the NOTAUTH conditionto the application and the transaction continues.

User response: Request a change to the securitypermissions, or use another abend handler program.

Destination:

console.msg

ERZ017015E Abnormal termination U1701. CICS wasunable to allocate storage for lookuptables

Explanation: During system startup, CICS was unableto allocate Region Pool storage for its internal datastructures.

System action: CICS shuts down the Region.

User response: Increase the size of the Region Pool byrestarting the region with an override for the value ofthe MaxRegionPool attribute in the Region Definition(RD). If the problem persists, contact your supportorganization.

Destination:

console.msg

ERZ017010E • ERZ017015E


ERZ017016E Abnormal termination A178. CICS wasunable to lock a handle abend programdatabase entry due to lack of storage

Explanation: During an EXEC CICS HANDLEABEND PROGRAM command, CICS was unable tolock a handle abend program database entry due tolack of space in the Region Pool.


User response: Because memory in the Region Pool iscontinually being acquired and freed by CICS on behalfof running transactions, resubmission of thistransaction can possibly be successful. If this problempersists when you resubmit the transaction, checkwhether it is looping in some way that causes CICS toacquire substantial amounts of Region Pool memory onits behalf; for example, check the depth of EXEC CICSLINKs in the program, as storage is required for eachlogical level. Finally, consider increasing the size of theRegion Pool by restarting the region with an overridefor the value of the MaxRegionPool attribute in theRegion Definition (RD).

Destination:

CSMT

ERZ018001E Port portNumber is already in use byanother application

Explanation: An attempt to bind to an already boundTCP/IP port portNumber was attempted. TCP/IP allowsonly one server at a time to bind to any particular port.

System action: The cicsteld server terminates.

User response: Invoke cicsteld with the -P optionspecifying a different, unused port number. Use theoperating system netstat command to list port numbersbeing used.

Destination:

stderr

ERZ018002E Port portNumber is reserved

Explanation: An attempt to bind to a TCP/IP portportNumber, which is marked as reserved, has occurred.This is usually a port number less than 1024.


User response: Invoke cicsteld with the -P optionspecifying a different, unused port number. Use theoperating system netstat command to list port numbersbeing used.

Destination:

stderr

ERZ018003I Usage: cicsteld [-r regionName] [-PportNumber] [-l locale] [-e emulation] [-tinitialTransaction] [-c clientCodePage][-s serverCodePage] [-n netName] [-hhostList] [-v]

Explanation: You have invoked cicsteld with invalidoptions.

System action: The cicsteld server exits.

User response: Correct the parameters passed tocicsteld.

Destination:

stderr

ERZ018004I Checking current user identity

Explanation: cicsteld is attempting to check the useridentity already set up before cicsteld was called.

System action: The cicsteld checks the user identityand then, if it is valid, attempts to connect to theselected CICS region.

User response: Wait for the check to complete. If thecheck fails, check current identity or use the -p optionto pass the identity.

Destination:

Telnet client display.

ERZ018005E This telnet client is unable to support3270 emulation

Explanation: The telnet client attempting to connectwith the cicsteld server is unable to emulate any of theknown 3270 terminal types or does not specify whattype of terminals it supports.


User response: Select an appropriate telnet client thatis capable of emulating a 3270 data stream terminal.

Destination:

stderr

ERZ018006E Transaction ’transId’ not submitted --’errorString’

Explanation: The submission of the transaction’transId’ was unsuccessful, returning the supplied errordetails.

System action: The transaction specified does not run.

User response: Check that you entered the correcttransaction name. If so, check that the TransactionDefinitions (TD) in the region database includes thetransaction. If the ’errorString’ indicates that acommunications failure occurred, check that the CICSregion is still running. If the CICS region has

ERZ017016E • ERZ018006E


terminated, end the telnet session and invoke another.

Destination:


ERZ018007W Option ’optionName’ exceeds maximumallowable length of maxLength and hasbeen truncated

Explanation: An option was supplied to the cicsteldthat exceeded the maximum length allowed for thatoption - maxLength.

System action: The option is truncated to themaximum allowed and the cicsteld continuesinitialization.

User response: Restrict the length of the suppliedoption so that it does not exceed the maximumallowable length.

Destination:

stderr

ERZ018009E No port number specified and noservice found

Explanation: cicsteld was invoked from the commandline with no port number specified and no entry forcicsteld was found in the TCP/IP services file. OnUNIX this file is located in directory /etc. On WindowsNT this file is located in direcotry %SystemRoot%system32driversetc.

System action: The cicsteld server is terminated.

User response: Restart cicsteld with a port number orask your system administrator to add an entry forcicsteld to the services file.

Destination:

stderr

ERZ018010E Invalid port number

Explanation: cicsteld was invoked from the commandline with a port number that is larger than 65535 orsmaller than 0 and so is invalid for a TCP/IP socketsport.

System action: The cicsteld server is terminated.

User response: Restart cicsteld with a port number inthe range 0-65535

Destination:

stderr

ERZ018011E No CICS regions available

Explanation: cicsteld is unable to find any availableCICS regions.

System action: The cicsteld server is terminated afterdisplaying this message and the user pressing a key.

User response: Restart cicsteld when a CICS region isavailable.

Destination:


ERZ018012E Connect to region ’regionName’ wasunsuccessful -- ’errorString’

Explanation: The requested region ’regionName’ cannotbe contacted.


User response: Ensure that the region exists and isrunning.

Destination:


ERZ018013E Unsuccessful autoinstall of this terminal-- ’errorString’

Explanation: cicsteld has attempted to autoinstall thisterminal but has received an error.


User response: Check that a terminal model isavailable for the terminal type supplied on the -eoption of cicsteld or obtained from the environmentvariable TERM.

Destination:


ERZ018014I Searching for available regions

Explanation: cicsteld is searching for available CICSregions to display a selection menu. The cicsteld cantake several seconds before it obtains this informationand displays the region menu.

System action: cicsteld continues to search foravailable regions.

User response: Wait for display of the availableregions menu.

Destination:

stderr

ERZ018007W • ERZ018014I


ERZ018015I Connecting to region ’regionName’

Explanation: cicsteld is attempting to contact andconnect to the region ’regionName’.

System action: The cicsteld server connects to thenamed CICS region.

User response: Wait for the connection to be set up.

Destination:


ERZ018017E Telnet client unable to support optionsrequired

Explanation: The client is unable to support thecommunications protocol required by the cicsteld.


User response: Select an appropriate telnet client thatis capable of emulating a 3270 data stream terminal.

Destination:

stderr

ERZ018018E Connection to telnet client closedunexpectedly

Explanation: The client has terminated the connectionto the cicsteld unexpectedly.


User response: Check the telnet client is functioningcorrectly.

Destination:

stderr

ERZ018019E Initialization was unsuccessful

Explanation: The cicsteld did not successfullyinitialize due to memory allocation or system callproblem.


User response: Report problem to your supportorganization.

Destination:

stderr

ERZ018020I cicsteld terminated, region shut down

Explanation: The region that this cicsteld wasconnected to was shut down.


User response: Wait for the region to be restarted orrestart the cicsteld and select a different region ifavailable.

Destination:


ERZ018021I cicsteld terminated, terminal out ofservice

Explanation: Your terminal is marked as out ofservice.

System action: None

User response: Ask the Administrator to reinstateyour hard terminal and then reinvoke cicsteld.

Destination:


ERZ018022E Invalid selection, position cursor onselected region

Explanation: You have placed the cursor on a line thatdoes not have a region. Reposition the cursor on theline displaying the region you wish to connect to.

System action: None

User response: Move cursor to the row displaying theregion of your choice.

Destination:


ERZ018023I cicsteld terminated, network credentialshave expired

Explanation: The login context for this cicsteldprocess has expired. Further communication to theCICS region cannot take place.

System action: None

User response: Restart cicsteld. This acquires a newlogin context.

Destination:


ERZ018025I cicsteld terminated, signal or exceptiondetected

Explanation: cicsteld encountered an unexpectedsignal or exception.


User response: Try running the cicsteld again. If theproblem recurs, contact your support organization.

Destination:


ERZ018015I • ERZ018025I


ERZ018026E Conversion between codepages’codePage1’ and ’codePage2’ not supported

Explanation: The cicsteld did not successfullyinitialize because conversion between the codepage’codePage1’ and codepage ’codePage2’ is not supported.


User response: Check that you are supplying validcodepages to cicsteld and that it is possible to convertbetween the two codepages.

Destination:

stderr

ERZ018027E Connect to region ’regionName’ wasunsuccessful -- ’%2$s’

Explanation: There was an unexpected error whileattempting to connect to the requested region’regionName’.


User response: Ensure that the region exists and isrunning. Ensure that you have run cicssetupclients. Ifthe region is available and the problem recurs, contactyour support organization.

Destination:


ERZ018029E Port portNumber : bind failure - bindreturned errorNumber

Explanation: An attempt to bind to port portNumberwas rejected with an unrecognized error codeerrorNumber.


User response: Consult your telnet documentation todiscover the meaning of errorNumber and correct thecondition. If the error persists, contact your supportorganization.

Destination:

stderr

ERZ018030E cicsteld has experienced an internal pipefailure

Explanation: cicsteld has received an unexpectedresult from a call to read data from one of its internalpipes.


User response: Restart cicsteld. If the error persists,contact your support organization.

Destination:

stderr


Explanation: cicsteld is attempting to find CICSregions. The terminal is now searching on machine’machineName’.

System action: cicsteld continues.

User response: No reponse is necessary.

Destination:

stderr


Explanation: cicsteld is attempting to find CICSregions.

System action: cicsteld continues but does not list anyCICS regions from machine ’machineName’.

User response: Check that the processes are allstarted.

Destination:

stderr


Explanation: cicsteld has displayed warnings relatingto attempts to locate CICS regions on one or moremachines. These messages are displayed until the userhits Enter.

System action: cicsteld continues after Enter is hit.


Destination:

stderr

ERZ019001E Execution Diagnostic Facility (EDF)could not update the TerminalDefinition for terminal ’termId’.

Explanation: EDF attempted to alter EDF controlinformation in the database entry for the namedterminal but was unable to update the TerminalDefinition in the runtime database.

System action: EDF continues in the current mode ofexecution as the mode was unable to be changed. Anytransaction currently running on the specified terminalcontinues.

User response: Examine the CICS message files asCICS possibly wrote other messages that indicate whythe attempt to update the runtime database wasunsuccessful.

ERZ018026E • ERZ019001E


Destination:

CSMT

ERZ019002E Execution Diagnostic Facility (EDF)could not update the System Definitionfor system ’sysId’.

Explanation: EDF attempted to alter EDF controlinformation in the database entry for the named systembut was unable to update System Definition in theruntime database.

System action: EDF continues in the current mode ofexecution as the mode was unable to be changed. Anytransaction currently attached from the specified systemcontinues.

User response: Examine the CICS message files asCICS possibly wrote other messages that indicate whythe attempt to update the runtime database wasunsuccessful.

Destination:

CSMT

ERZ019003E Execution Diagnostic Facility (EDF)could not read the command-linearguments from terminal ’termId’.

Explanation: The CEDF transaction attempted to readcommand-line arguments from the principal facility butwas unsuccessful.

System action: EDF continues in the current mode ofexecution as the mode was unable to be changed. Anytransaction currently being debugged continues.

User response: Examine the CICS message files asCICS possibly wrote other messages that indicate whythe attempt to read the command-line arguments wasunsuccessful. Try running the CEDF transaction again.

Destination:

CSMT

ERZ019004E Execution Diagnostic Facility (EDF)could not allocate region storage.

Explanation: An attempt to allocate storage from theRegion Pool to contain EDF control information wasunsuccessful. As memory in the Region Pool iscontinually being acquired and freed by CICS on behalfof running transactions, this is possibly a transientproblem that can occur when CICS is heavily loaded.

System action: CICS terminates the application serverwith an abend code of A194. The CICS regioncontinues.

User response: Try turning EDF on and then runningthe transaction again. If this problem persists when youresubmit the transaction, check whether it is looping insome way that causes CICS to acquire substantial

amounts of Region Pool memory on its behalf; forexample, check the depth of EXEC CICS LINKs in theprogram, as Region Pool memory is required for eachlogical level. Finally, consider increasing the size of theRegion Pool by restarting the region with an overridefor the value of the MaxRegionPool attribute in theRegion Definition (RD).

Destination:

CSMT

ERZ019005E Execution Diagnostic Facility (EDF)could not read a message from the CICSmessage catalog.

Explanation: An attempt to read an EDF messagefrom the CICS message catalog was unsuccessful.

System action: CICS terminates the application serverwith an abend code of A195. The CICS regioncontinues.

User response: Check that the CICS message catalogfor the region is accessible and has the requiredpermissions. Refer to operating system documentationfor further information about the use of catalogs.

Destination:

CSMT

ERZ019006E Execution Diagnostic Facility (EDF)could not display a screen on terminal’termId’ while debugging tasktaskNumber. EDF has been turned off.

Explanation: An attempt to write an EDF screen to thedebug terminal was unsuccessful.

System action: EDF terminates. The transactioncontinues but is no longer debugged by EDF.

User response: Examine the CICS message files todetermine if the debug terminal is unavailable. If theterminal is out of service, then set the terminal back inservice. If the terminal is in service, ensure that theterminal and the connection to it are available. Tryturning EDF on and then running the transaction again.

Destination:

CSMT

ERZ019007E Execution Diagnostic Facility (EDF)could not allocate task-private storagewhile debugging task taskNumber. EDFhas been turned off.

Explanation: An attempt to allocate storage from theTask-Private Pool in order to display an EDF screen onthe debug terminal was unsuccessful.


ERZ019002E • ERZ019007E


User response: Try turning EDF back on and thenrunning the transaction again. If this problem persistswhen you resubmit the transaction, determine if thetransaction is using excessive amounts of Task-PrivatePool (GETMAIN) storage and correct this.

Destination:

CSMT

ERZ019008E Execution Diagnostic Facility (EDF)could not create a display map areawhile debugging task taskNumber. EDFhas been turned off.

Explanation: An attempt to create part of an EDF mapin order to display an EDF screen on the debugterminal was unsuccessful. The most probable cause ofthis problem is that CICS is short of Task-Private Pool(GETMAIN) storage.



Destination:

CSMT

ERZ019009E Execution Diagnostic Facility (EDF)could not create a display field whiledebugging task taskNumber. EDF hasbeen turned off.

Explanation: An attempt to create a field in part of anEDF map in order to display an EDF screen on thedebug terminal was unsuccessful. The most probablecause of this problem is that CICS is short ofTask-Private Pool (GETMAIN) storage.



Destination:

CSMT

ERZ019010E Execution Diagnostic Facility (EDF)could not free Task-Private storagewhile debugging task taskNumber.

Explanation: An attempt to free storage that EDF hasallocated from the Task-Private Pool was unsuccessful.The most probable cause of this problem is that there is

inconsistency in CICS internal memory pointers, inwhich case the transaction is abnormally terminated.

System action: If the attempt to free the storage wasunsuccessful because CICS internal memory pointersare inconsistent then the transaction is abnormallyterminated. Otherwise, EDF and the transactioncontinue.

User response: Examine the CICS message files todetermine why the storage was not freed. If thetransaction was abnormally terminated use thetransaction dump to investigate this problem. It ispossible that user application code is writing to astorage area allocated to CICS internal use. Check theuse made of pointers to GETMAIN storage in yourapplication. If other messages indicate that the problemis a software error in CICS then save any dump fileproduced and contact your support organization.

Destination:

CSMT

ERZ019011E Execution Diagnostic Facility (EDF)could not read from terminal ’termId’while debugging task taskNumber. EDFhas been turned off.

Explanation: An attempt to read user input to an EDFscreen displayed on the debug terminal wasunsuccessful.


User response: Examine the CICS message files todetermine if the debug terminal is unavailable. If theterminal is out of service, then set the terminal back inservice. If the terminal is in service, ensure that theterminal and the connection to it are available. If theemulator process for the debug terminal is stillrunning, try turning EDF on and then running thetransaction again.

Destination:

CSMT

ERZ019012E Execution Diagnostic Facility (EDF)could not refresh a display map whiledebugging task taskNumber. EDF hasbeen turned off.

Explanation: An attempt to refresh an EDF map fieldin order to display an updated EDF screen on thedebug terminal was unsuccessful.


User response: Examine the CICS message files asCICS possibly wrote other messages that indicate whythe attempt to refresh the map was unsuccessful. If thetransaction was abnormally terminated use the

ERZ019008E • ERZ019012E


transaction dump to investigate this problem. It ispossible that user application code is writing to astorage area allocated to CICS internal use. Check theuse made of pointers to GETMAIN storage in yourapplication. If other messages indicate that the problemis a software error in CICS then save any dump fileproduced and contact your support organization.

Destination:

CSMT

ERZ019013E Execution Diagnostic Facility (EDF)could not access the Terminal Definitionfor terminal ’termId’.

Explanation: EDF attempted to alter EDF controlinformation in the database entry for the namedterminal but was unable to access the TerminalDefinition in the runtime database.

System action: CICS terminates the application serverwith an abend code of A19D. The CICS regioncontinues.

User response: Examine the CICS message files asCICS possibly wrote other messages that indicate whythe attempt to access the runtime database wasunsuccessful.

Destination:

CSMT

ERZ019014E Execution Diagnostic Facility (EDF)could not access the System Definitionfor system ’sysId’.

Explanation: EDF attempted to alter EDF controlinformation in the database entry for the named systembut was unable to access the System Definition in theruntime database.

System action: CICS terminates the application serverwith an abend code of A19E. The CICS regioncontinues.

User response: Examine the CICS message files asCICS possibly wrote other messages that indicate whythe attempt to access the runtime database wasunsuccessful.

Destination:

CSMT

ERZ019015E Execution Diagnostic Facility (EDF)could not access the runtime databaseentry for resource ’resourceName’.

Explanation: EDF attempted to access the runtimedatabase entry for the named terminal or system butwas unable to access the resource in the runtimedatabase.

System action: EDF terminates and the transaction is

no longer debugged by EDF. The CICS regioncontinues, but there is possibly a serious problem withthe runtime database.

User response: Examine the CICS message files asCICS possibly wrote other messages that indicate whythe attempt to access the runtime database wasunsuccessful. There is possibly a serious problem withthe runtime database that can require restarting theregion.

Destination:

CSMT

ERZ019016E Execution Diagnostic Facility (EDF)could not communicate with terminal’termId’ while debugging tasktaskNumber. EDF has been turned off.

Explanation: EDF attempted to communicate with thedebug terminal but was unsuccessful.

System action: EDF terminates. The transactioncontinues but is not debugged by EDF.

User response: Examine the CICS message files todetermine if the debug terminal is unavailable. If theterminal is out of service, then set the terminal back inservice. If the terminal is in service, ensure that theterminal and the connection to it are available. If theemulator process for the debug terminal is stillrunning, try turning EDF on and then running thetransaction again.

Destination:

CSMT

ERZ019017E Execution Diagnostic Facility transaction(CEDF) could not display a message onterminal ’termId’.

Explanation: An attempt to write a CEDF message tothe debug terminal was unsuccessful.

System action: The CEDF transaction continues.

User response: Examine the CICS message files todetermine if the debug terminal is unavailable. If theterminal is out of service, then set the terminal back inservice. If the terminal is in service, ensure that theterminal and the connection to it are available. If theemulator process for the debug terminal is stillrunning, try running the CEDF transaction again.

Destination:

CSMT

ERZ019019E Security violation: User ’userId’ onterminal ’termId’ tried to debugtransaction ’transId’ but was deniedaccess. EDF has been turned off.

Explanation: User userId attempted to debug

ERZ019013E • ERZ019019E


transaction termId from the terminal transId but aTransaction Security Level (TSL) or Resource SecurityLevel (RSL) check failed. CICS performs TSL validationto verify that the debug user (the user who is runningCEDF), has sufficient authorization to debug thetransaction and, if so, subsequent RSL validation isperformed for both the user who is running thetransaction and the debug user. One of these securitychecks failed.

System action: EDF terminates and displays a″Security violation″ message on the debug user’sscreen. The user transaction continues.

User response: If the debug user is allowed to debugthe transaction, check that both the CEDF transactionand the transaction to be debugged have the samevalues for both the TSLCheck and RSLCheckattributes in the Transaction Definitions (TD). Alsocheck that both transactions have TSLKey and RSLKeyattribute values that are defined in the correspondingTSLKeyList and RSLKeyList for the debug user in theUser Definitions (UD).

Destination:

CSMT

ERZ020001E CICS has been unsuccessful incommunicating with the cicsterm whiletrying to display help usingInfoExplorer

Explanation: You requested help, but CICS was notable to communicate with the cicsterm to display helpby using InfoExplorer.

System action: No help information is displayed. Thetransaction continues.

User response: Check the connection between CICSand the display. Check that the emulator process andthe application servers are still running. Then tryrunning the transaction again.

Destination:

console.msg, CSMT

ERZ020002E CICS has been unsuccessful incommunicating with the terminal whiletrying to display help using BMS

Explanation: You requested help, but CICS wasunable to communicate with the terminal to displayhelp using a BMS map.

System action: No help information is displayed. Thetransaction continues.

User response: Check the connection between CICSand the terminal. Check that the terminal is in service.If not, use the CEMT transaction to set the terminalback in service.

Destination:

console.msg, CSMT

ERZ020003E CICS has been unable to run the helpprogram. Press ENTER to continue.

Explanation: Help has been requested but CICS hasbeen unable to run the program which displays help(DFHINFO).

System action: Help is not displayed but otherprocessing continues.

User response: Check the preceding messages (on theapplication owning region) for details of why the helpprogram, DFHINFO, did not succeed and then followthe actions for those messages.

Destination:


ERZ021002E Unsuccessful close of file ’fileName’

Explanation: CICS detected an error when closing afile.

System action: CICS raises the IOERR or ILLOGICcondition.

User response: Check the message files for any errorsreported by the file server. Check the File Definitions(FD) entry for the file.

Destination:

CSMT

ERZ021004E Unable to open file ’fileName’

Explanation: CICS detected an error when attemptingto open a file.

System action: CICS raises the IOERR or ILLOGICcondition. The file is marked as CLOSED andUNENABLED.

User response: Check the message files for any errorsreported by the file server. Check the File Definitions(FD) entry for the file.

Destination:

CSMT

ERZ021005E Task timed out while waiting for file’fileName’ to be opened

Explanation: While waiting for another task to openthe file, the DeadLockTimeout value (specified in theTransaction Definition) for this task was exceeded, sothe task timed out.

System action: The task is abended with the code’AKCS’.

User response: Check the message files for any errorsreported by the file server, which possibly indicate a

ERZ020001E • ERZ021005E


reason for reduced response time. Resubmit thetransaction.

Destination:

CSMT

ERZ021006E Unable to obtain the Task Control Area(TCA)

Explanation: A CICS internal function was not able tolocate the TCA.


User response: This is an internal error. Contact yoursupport organization.

Destination:

console.msg

ERZ021009E File ’fileName’ is not CLOSED andDISABLED, CICS cannot delete it

Explanation: An attempt was made to delete a filewhen it is not CLOSED and DISABLED.


User response: It is not possible to delete a file whenit is not CLOSED and DISABLED. First CLOSE andDISABLE the file then try again.

Destination:

CSMT

ERZ021010E Unsuccessful memory allocation for filecontrol information

Explanation: CICS was attempting to obtain memoryfor file control information from the Region Pool.Insufficient memory was available.

System action: The transaction is abnormallyterminated with the code A21M.

User response: This is possibly a transient problemthat occurs when CICS is heavily loaded. Resubmit thetransaction. If the problem persists, you possibly needto reconfigure the size of the Region Pool and restartCICS.

Destination:

CSMT

ERZ021011E Unsuccessful memory allocation for filecontrol information

Explanation: CICS was attempting to obtain memoryfor file control information from the Task-Shared Pool.Insufficient memory was available.

System action: The transaction is abnormallyterminated with the code A21M.

User response: This is possibly a transient problemthat occurs when CICS is heavily loaded. Resubmit thetransaction. If the problem persists, you possibly needto reconfigure the size of the Task-Shared Pool andrestart CICS.

Destination:

CSMT

ERZ021012E Unable to restore File Definitions (FD)entry to region database

Explanation: CICS was not able to restore an FD entryto the region database.

System action: CICS abnormally terminates thetransaction with code A21R.

User response: This is an internal CICS error. Contactyour support organization.

Destination:

CSMT or console.msg

ERZ021013E Unable to find a File Definitions (FD)entry in the region database

Explanation: CICS was not able to locate an FD entryin the region database.

System action: CICS abnormally terminates thetransaction with code A21S.

User response: This is an internal CICS error. Contactyour support organization.

Destination:

CSMT or console.msg

ERZ021014I Unable to obtain File Definition (FD)entry ’fileName’ from the region database

Explanation: CICS was not able to retrieve an FDentry from the region database. It was probablydeleted.


User response: None

Destination:

CSMT

ERZ021031E CICS self-consistency checking hasdetected an inconsistency in the CICSinternal data structures - details are inthe next message

Explanation: CICS detected an inconsistency in itsinternal data structures.


ERZ021006E • ERZ021031E


User response: Try to identify whether a usertransaction overwrote the data. Otherwise contact yoursupport organization.

Destination:

console.msg

ERZ021032E Corrupt signature detected in FRTE(address address); expected’expectedSignature’ actual ’actualSignature’

Explanation: CICS detected an inconsistency in itsinternal data structures.



Destination:

console.msg

ERZ021033E FRTEcountu FRTEs exist (in structureaddress address) for closed and disabledfile

Explanation: The structure whose address is shownhas one or more FRTEs for a closed/disabled file.



Destination:

console.msg

ERZ021034E Maintained count of FRTEs FRTEcountudifferent from the actual number ofFRTEs actualFRTEnumberu. (Address ofculprit structure address)

Explanation: The structure whose address is shownhas a mismatched count of FRTEs.



Destination:

console.msg

ERZ021035E Corrupt signature detected in FileControl Module data structure (addressaddress, occurring in TCA addressTCAaddress); expected ’expectedSignature’actual ’actualSignature’

Explanation: The indicated File Control structure hasa corrupt signature.



Destination:

console.msg

ERZ021050W CICS has ignored request to makeUPDATABLE file ’fileName’NOTREADABLE

Explanation: Request to make an UPDATABLE file (asdefined in the File Definitions (FD) database)NOTREADABLE was ignored. The file remainsREADABLE.

System action: CICS makes the file readable andcontinues normally.

User response: If you need to make the fileNOTREADABLE then ensure it is firstNOTUPDATABLE.

Destination:

CSMT

ERZ021051W CICS has ignored request to makeBROWSABLE file ’fileName’NOTREADABLE

Explanation: Request to make a BROWSABLE fileNOTREADABLE was ignored. The file remainsREADABLE.

System action: CICS makes the file readable andcontinues normally.

User response: If you need to make the fileNOTREADABLE then ensure it is firstNOTBROWSABLE.

Destination:

CSMT

ERZ021052I Opening files ...

Explanation: CICS has started opening all the filesthat are defined as open and enabled.

System action: CICS is continuing to initialize.

User response: Wait until initialization is complete.

ERZ021032E • ERZ021052I


Destination:

console.msg

ERZ021053I ... file opening completed

Explanation: CICS has finished opening all the filesthat are defined as open and enabled.

System action: CICS is continuing to initialize.

User response: Wait until initialization is complete.

Destination:

console.msg

ERZ021054W Unsuccessful memory deallocation offile buffer

Explanation: An error occurred while CICS wasattempting to release a memory buffer used during thelast file operation.

System action: This message is logged but processingcontinues.

User response: Check the CSMT log or console.msgfile for associated information. If other messagesindicate that the problem is a software error in CICSthen contact your support organization.

Destination:

CSMT





Destination:

console

ERZ022001I Processing transient data queues ...

Explanation: CICS has started processing TD queues.

System action: CICS performs TD initialization.


Destination:

console.msg

ERZ022002I Transient data definitions validated

Explanation: CICS startup processing has finished TDqueue validation.



Destination:

console.msg

ERZ022003E Abnormal termination U2203: SystemTransient Data (TD) queue ’TDQname’cannot be logically recoverable.

Explanation: The DestType and RecoveryTypeattributes of the Transient Data Definitions (TDD) entryfor the named queue required for CICS error-logging,or for use by a CICS-private transaction, contain invalidvalues.

System action: CICS terminates the region with anabnormal termination code U2203.

User response: Correct the invalid TDD entry for thenamed queue and reinstall it.

Destination:

console.msg

ERZ022004E Local system identifier specified forread operation on remote Transient Data(TD) queue ’TDQname’.

Explanation: The SYSID option was employed on aREADQ TD call with the local system id supplied asthe SYSID. Normally a local read is performed;however, in this case, that is not possible because thenamed queue is defined as remote in the TransientData Definitions (TDD).

System action: CICS raises an AEY9 abend.

User response: As appropriate to the programexecuting the READQ TD call. This possibly requireschanging the queue named in the program, changingthe TDD entry or handling the abend.

Destination:

CSMT

ERZ022005E Local sysid specified for write operationon remote Transient Data (TD) queue’TDQname’.

Explanation: The SYSID option was employed on aWRITEQ TD call with the local system id supplied asthe SYSID. Normally a local write is performed;however, in this case, that is not possible because the

ERZ021053I • ERZ022005E


named queue is defined as remote in the TransientData Definitions (TDD).


User response: As appropriate to the programexecuting the WRITEQ TD call. This possibly requireschanging the queue named in the program, changingthe TDD entry or handling the abend.

Destination:

CSMT

ERZ022006E Local sysid specified for deleteoperation on remote Transient Data (TD)queue ’TDQname’.

Explanation: The SYSID option was employed on aDELETEQ TD call with the local system id supplied asthe SYSID. Normally a local delete is performed;however, in this case, that is not possible because thenamed queue is defined as remote in the TransientData Definitions (TDD).


User response: As appropriate to the programexecuting the DELETEQ TD call. This possibly requireschanging the queue named in the program, changingthe TDD entry or handling the abend.

Destination:

CSMT

ERZ022009W Loop detected in indirect Transient Data(TD) queue destinations, queue’TDQname’ deleted.

Explanation: CICS has traced through a chain ofindirect queue names and has found that the chainloops back on itself.

System action: CICS deletes the offending queuedefinition, and continues startup.

User response: Modify the IndirectQueueId attributeof the offending queue or of one of the queues towhich it indirectly refers.

Destination:

console.msg

ERZ022010W Undefined indirect Transient Data (TD)queue destination ’TDQname1’, queue’TDQname2’ deleted.

Explanation: The IndirectQueueId attribute of aqueue does not identify a queue in the Transient DataDefinitions (TDD).

System action: CICS deletes the offending queuedefinition, and continues startup.

User response: Modify the IndirectQueueId attribute

of the offending queue to identify a real queue, or adda definition for the undefined queue.

Destination:

console.msg

ERZ022011E Error opening file storing physicallyrecoverable intrapartition queue data.

Explanation: The file server returned an error whenattempting to open the physically recoverable queuedata file.

System action: CICS generates an A22B abend.

User response: Look at previous messages to see ifthere is a problem with the file server. If the file serverseems to be working correctly, you can use file serveradministration commands to interrogate the status ofthe file and its index. Find the server, file and indexnames in the PhysicalTDQServer, PhysicalTDQFile,and PhysicalTDQIndex attributes of the RegionDefinition. Until the file is available again you cannotrun any transaction using physically recoverable TDQs.

Destination:

console.msg

ERZ022012E Error opening file storing logicallyrecoverable intrapartition queue data.

Explanation: The file server returned an error whenattempting to open the logically recoverable queue datafile.


User response: Look at previous messages to see ifthere is a problem with the file server. If the file serverseems to be working correctly, you can use file serveradministration commands to interrogate the status ofthe file and its index. Find the server, file and indexnames in the LogicalTDQServer, LogicalTDQFile, andLogicalTDQIndex attributes of the Region Definition.Until the file is available again you cannot run anytransaction using logically recoverable TDQs.

Destination:

console.msg

ERZ022013E Error opening file storingnon-recoverable intrapartition queuedata.

Explanation: The file server returned an error whenattempting to open the non-recoverable queue data file.


User response: Look at previous messages to see ifthere is a problem with the file server. If the file serverseems to be working correctly, you can use file serveradministration commands to interrogate the status of

ERZ022006E • ERZ022013E


the file, and its index. Find the server, file and indexnames in the NonRecTDQServer, NonRecTDQFile,and NonRecTDQIndex attributes of the RegionDefinition. Until the file is available again you cannotrun any transaction using non-recoverable TDQs.

Destination:

console.msg

ERZ022014E System error errorNumber opening file’fileName’ storing data for extrapartitionTransient Data (TD) queue ’TDQname’.

Explanation: CICS was not able to open the file usedto store data for the indicated queue. CICS shows theerror number returned from the open call. This erroronly occurs when reading or writing an extrapartitionTransient Data (TD) queue.

System action: CICS disables the queue, and raises theIOERR condition.

User response: Check the error number and takesuitable corrective action. The most likely errors areeither that the file access permissions are incorrect orthat the filename supplied in the queue definition isincorrect. If you cannot correct the problem, contactyour support organization.

Destination:

console.msg

ERZ022015E file server error reading recordrecordNumber from intrapartitionTransient Data (TD) queue ’TDQname’.

Explanation: The file server returned an error whenreading a record from a data queue.

System action: CICS raises the IOERR condition. Notethat CICS abnormally terminates the region if thequeue is a mandatory system queue.

User response: Check the file server to ensure that thefile contains correctly formatted data. A previouslylogged message possibly identifies the file server error.

Destination:

CSMT

ERZ022016E file server error writing recordrecordNumber to intrapartition TransientData (TD) queue ’TDQname’.

Explanation: The file server returned an error whenwriting a record to a data queue.

System action: CICS raises the IOERR condition.

User response: Check the file server to ensure that thefile contains correctly formatted data. A previouslylogged message possibly identifies the file server error.

Destination:

CSMT

ERZ022017E Error deleting records from TransientData (TD) queue ’TDQname’.

Explanation: The file server returned an error whendeleting records from a data queue as part of an EXECCICS DELETEQ TD command.

System action: CICS terminates the transaction withabend code A22A.

User response: Check the file server to ensure that thefile contains correctly formatted data. Previous errormessages possibly indicate the source of the error.

Destination:

CSMT

ERZ022018E Storage allocation failure duringTransient Data (TD) queue syncpoint.

Explanation: CICS was unable to perform syncpointprocessing because of an unsuccessful attempt to obtainstorage from the Region Pool for the assembly ofsystem log data.

System action: CICS abnormally terminates syncpointprocessing, and continues processing.

User response: You possibly need to reconfigure thesize of the Region Pool and restart CICS.

Destination:

console.msg

ERZ022022E Recovery was unsuccessful, logicallyrecoverable Transient Data (TD) queue’TDQname’ not found in Transient DataDefinitions (TDD).

Explanation: A system log record contains a queuename which does not identify a TD queue defined inthe TDD.

System action: CICS ignores the record, and continuesrecovery processing.

User response: Check whether the queue is supposedto be defined. If the queue name is not meaningful,check that the system log is correctly formatted.

Destination:

console.msg

ERZ022023E Recovery was unsuccessful, TransientData (TD) queue system log dataincorrectly formatted.

Explanation: During TD queue initialization, CICSfound that either the checkpoint data, or the repreparedata read from the system log, was incorrectlyformatted.

ERZ022014E • ERZ022023E



User response: Check that the system log file isreadable and correctly formatted.

Destination:

console.msg

ERZ022024E Corrupt signature detected in TransientData Module data structure, expected’expectedSignature’ actual ’actualSignature’.

Explanation: During self-consistency checking, CICSfound errors in the configuration of a Transient Dataqueue.

System action: The message is logged and CICSself-consistency checking continues.

User response: Attempt to identify whether atransaction overwrote the data. If not, contact yoursupport organization.

Destination:

console.msg

ERZ022025E Transient Data (TD) queue inconsistency- ’TDQname’ start pointer value1 exceedsend pointer value2.

Explanation: During recovery or self-consistencychecking, CICS found a queue’s start and end pointersto be inconsistent. The record identified by the startpointer comes after the record identified by the endpointer in the queue record sequence.

System action: If the problem is found duringself-consistency checking, CICS disables the queue, andcontinues processing. If the problem is found duringrecovery, region restart is abnormally terminated.

User response: If the message was generated duringself-consistency checking then try to determine if a usertransaction has caused the memory corruption. If themessage was generated during recovery processing,this possibly indicates that the file containing theTransient Data queue records has been corrupted. If anuncorrupted copy of the file is not available, a coldstart of the region is possibly necessary. Contact yoursupport organization for further assistance.

Destination:

console.msg

ERZ022027E Transient Data (TD) queue ’TDQname’has invalid private data area signature.

Explanation: During self-consistency checking, CICSfound the specified TD queue’s data area to have beencorrupted.

System action: CICS continues self-consistencychecking.

User response: Try to identify if a user transaction hasoverwritten the data. If not contact your supportorganization.

Destination:

console.msg

ERZ022028E Invalid attempt to delete anextrapartition Transient Data (TD) queue’TDQname’.

Explanation: The queue identifier supplied in anEXEC CICS DELETEQ TD call, identified anextrapartition TD queue. CICS cannot delete data fromsuch queues.

System action: CICS abnormally terminates thetransaction with code A229.

User response: Check the program or the queuedefinition to ensure that the queue name is correctlyidentified, and that the queue type is supposed to beextrapartition.

Destination:

CSMT

ERZ022029W Unsuccessful attempt at lockingphysically recoverable Transient Data(TD) queue ’TDQname’ during syncpointprocessing.

Explanation: This message is generated duringsyncpoint processing for a physically recoverable TDqueue. It indicates either that an unsuccessful storageallocation request prevented the task from waiting toobtain the lock or that a lock wait timed out. Previousmessages possibly indicate the source of the problem.Syncpoint processing is performed for physicallyrecoverable queues to confirm that the latest reader ofthe queue has indeed processed the last record read. Ifthis error occurs then the last record read from thequeue is possibly presented again for reading in theevent of a subsequent system crash.

System action: The syncpoint is continued. In theevent of a subsequent region crash the last record readfrom the queue is possibly presented again for reading.

User response: Have the system administrator checkfor the cause of the timeout or allocation failure. Atimeout is possibly due to a deadlock or excessive timedelay caused by the operation of some othertransaction on the queue. A storage failure possiblyrequires the Region Pool to be increased and CICS tobe restarted.

Destination:

console.msg

ERZ022024E • ERZ022029W


ERZ022030E Transaction ’transId’ timed out waitingfor lock on Transient Data (TD) queue’TDQname’.

Explanation: This message is generated whenperforming an AKCS abend after an attempt to obtain alock on the indicated TD queue timed out. The timeoutperiod is determined from the DeadLockTimeoutattribute of the indicated transaction. This messageprobably indicates that the TD queue is deadlocked.

System action: CICS abends the task with an AKCSabend.

User response: Have the system administrator checkall transactions which employ the TD queue indicatedin the message to identify whether there is a realdeadlock or merely an exceptionally long time delay inprocessing the queue by one of the transactions or bythe file server storing the queue data. If the problem ismerely one of timing then the DeadLockTimeoutattribute of transactions which use the TDQ possiblyneeds to be increased.

Destination:

CSMT

ERZ022031E Abnormal termination U2231: Nodefinition supplied for system TransientData (TD) queue ’TDQname’.

Explanation: No definition has been installed for oneof the required system queues. This is possibly due toan omission or an error in its definition.


User response: Check the definition of the queue inthe Transient Data definitions (TDD) database. If thequeue is indirect, also check the definition of the queueit identifies in IndirectQueueId.

Destination:

console.msg

ERZ022032E Unsuccessful recording operation onrecoverable Transient Data (TD) queue’TDQname’.

Explanation: Logging of recoverable data queueoperations requires allocation of storage from theRegion Pool. This attempt was unsuccessful.

System action: During normal operation, CICSterminates the transaction with abend code A222.During restart, CICS abnormally terminates the region.

User response: This indicates a memory allocationfailure. You possibly need to increase the size of theregion pool and restart CICS.

Destination:

console.msg

ERZ022033E Unsuccessful buffer storage allocationfor storage of Transient Data (TD) forqueue ’TDQname’

Explanation: This can occur when the SET option isused in an EXEC CICS READQ TD call or whenperforming a write to an intrapartition TD queue. Inthe case of a READQ operation, CICS was not able toallocate a buffer for return of the queue data. Whenperforming a WRITEQ operation, CICS was not able toallocate a buffer for formatting the data before passingit to the file server.


User response: This indicates a memory allocationfailure. You possibly need to increase the size of theTask-Shared pool and restart CICS.

Destination:

console.msg

ERZ022034E Invalid attempt to read from disabledTransient Data (TD) queue ’TDQname’.

Explanation: CICS has tried to read from a disabledqueue.

System action: CICS abnormally terminates thetransaction with code ATDD.

User response: Check the queue to see why it isdisabled,. It is possible that a previous operation hasencountered an error that resulted in the queue beingdisabled; check the message logs for previous errors.

Destination:

CSMT

ERZ022035E Attempt to write to disabled TransientData (TD) queue ’TDQname’.

Explanation: CICS has attempted to write to adisabled queue.


User response: Check the queue to see why it isdisabled. It is possible that a previous operation hasencountered an error that resulted in the queue beingdisabled; check the message logs for previous errors.

Destination:

CSMT

ERZ022030E • ERZ022035E


ERZ022036E Attempt to delete disabled TransientData (TD) queue ’TDQname’.

Explanation: CICS has attempted to delete a disabledqueue.


User response: Check the queue to see why it isdisabled. It is possible that a previous operation hasencountered an error that resulted in the queue beingdisabled; check the message logs for previous errors.

Destination:

CSMT

ERZ022038E Abnormal termination U2238: SystemTransient Data (TD) queue ’TDQname’cannot be physically recoverable.

Explanation: The DestType and RecoveryTypeattributes in the Transient Data Definitions (TDD) entryfor a queue required for CICS error-logging, or for useby a CICS-private transaction, are invalid.


User response: Correct the invalid TDD entry andreinstall it.

Destination:

console.msg

ERZ022039E Abnormal termination U2239: SystemTransient Data (TD) queue ’TDQname’cannot be remote.

Explanation: The DestType attribute in the TransientData Definitions (TDD) entry for a queue required forCICS error-logging, or for use by a CICS-privatetransaction, is invalid.



Destination:

console.msg

ERZ022040E System error errorCode reading recordrecordNumber from extrapartitionTransient Data (TD) queue ’TDQname’.

Explanation: CICS returned an error when reading arecord from a queue’s data file.


User response: Check the error number and take the

appropriate action. The most likely errors are eitherthat the file access permissions are incorrect or that thefilename supplied in the queue definition is incorrect. Ifyou cannot solve the problem, contact your supportorganization.

Destination:

CSMT

ERZ022041E System error errorCode writing recordrecordNumber to extrapartition TransientData (TD) queue ’TDQname’.

Explanation: CICS detected an error when writing arecord to a queue’s data file.

System action: CICS raises the IOERR or NOSPACEcondition.

User response: Check the error number and takeappropriate action. The most likely errors are eitherthat the file access permissions are incorrect or that thefilename supplied in the queue definition is incorrect. Ifyou cannot solve the problem, contact your supportorganization.

Destination:

CSMT

ERZ022042E Abnormal termination U2242: SystemTransient Data (TD) queue ’TDQname’cannot be indirect.




Destination:

console.msg

ERZ022043E Abnormal termination U2243: SystemTransient Data (TD) queue ’TDQname’cannot be non-recoverable intrapartition.

Explanation: The DestType and RecoveryTypeattributes in the Transient Data Definitions (TDD) entryfor a queue required for CICS error-logging, or for useby a CICS-supplied transaction, are invalid.



Destination:

ERZ022036E • ERZ022043E


console.msg

ERZ022045W No definition supplied for systemTransient Data (TD) queue ’TDQname’.

Explanation: There is no Transient Data Definitions(TDD) entry for a non-mandatory queue used by aCICS-private transaction.

System action: CICS ignores the omission, andcontinues the startup process.

User response: Consider installing the missing queuein the TDD.

Destination:

console.msg

ERZ022046E Unable to trigger transaction ’transId’ forqueue ’TDQname’ as the specifiedfacility, ’facilityId’, is not defined.

Explanation: CICS was not able to trigger atransaction as the facility to run the transaction on isnot defined.


User response: Check that the trigger facilitydefinition for the queue is correct. If the FacilityType isterminal, check that a definition for a terminal facilityIdexists, and if it is system, check that a definition for asystem facilityId exists.

Destination:

CSMT

ERZ022047E Unable to trigger a transaction for queue’TDQname’ as the specified transaction,’transId’, is not defined.

Explanation: CICS was not able to trigger atransaction as the transaction is not defined.

System action: CICS continues syncpoint processing.

User response: Consider installing the transaction.

Destination:

CSMT

ERZ022048E Unable to trigger a transaction for queue’TDQname’ as the transaction, ’transId’,cannot be shipped to a remote system.

Explanation: CICS was not able to trigger atransaction as it cannot be shipped to a remote system.



Destination:

CSMT

ERZ022049E Unable to trigger a transaction for queue’TDQname’ as the combination oftransaction ’transId’ and terminal ’termId’is invalid.

Explanation: CICS was not able to trigger atransaction as the combination of transaction andterminal is invalid. Check the message logs for othermessages regarding this transaction.


User response: Consider changing the transaction thatis triggered by this queue.

Destination:

CSMT

ERZ022051E Abnormal termination U2251: errorclosing non-recoverable intrapartitionTransient Data (TD) queue file handle.

Explanation: During startup, the file server returnedan error when closing the handle for the file used tostore non-recoverable intrapartition queue data. CICSpurges this file during a cold start or auto-startfollowing abnormal shutdown. This error possiblyindicates that the file is incorrectly formatted or thatthe file server is unavailable.


User response: Check that the file server isfunctioning correctly and that the file is formattedcorrectly. Previously logged messages possibly indicatethe nature of the file server error.

Destination:

console.msg

ERZ022054W Transient Data (TD) queue system logrecord identifies non-existent queue’TDQname’.

Explanation: A TD queue log record, written to thesystem log, identifies a queue that is not defined in theTransient Data Definitions (TDD). CICS possibly wrotethe record to the log either as part of a checkpointlogging all intrapartition queue read/write pointers, orto log read/write pointers for a specific physicallyrecoverable queue following a read, write, or deleteoperation.

System action: CICS continues the startup procedure.

User response: Ensure that the queue was not deletedfrom the Transient Data Definitions (TDD) database bymistake. Previous error messages generated duringstartup possibly indicate why the queue is missing.

Destination:

console.msg

ERZ022045W • ERZ022054W


ERZ022055W Transient Data (TD) queue system logrecord type does not match the queuetype ’TDQname’.

Explanation: A TD queue system log record, writtento the system log, identifies a queue with the samename but a different DestType or RecoveryType fromthe one defined in the Transient Data Definitions(TDD). CICS possibly wrote the record to the log, aspart of a checkpoint logging all intrapartition queueread/write pointers.

System action: CICS ignores the logged data, andcontinues its startup process.

User response: Ensure that queue has not beenmodified in the TDD database by mistake.

Destination:

console.msg

ERZ022057W Triggered Transient Data (TD) queue’TDQname’ not found at completion oftriggered task.

Explanation: A triggered transaction has exited andCICS was not able to re-enable triggering for theassociated Transient Data (TD) queue because CICSwas not able to find the queue. This can arise throughnormal operation, if CICS deletes the queue while thetriggered transaction is running. However, the runtimeTransient Data Definitions (TDD) entry is possiblyformatted incorrectly.


User response: Check that the queue is deactivated. IfCICS deactivated the queue because of an error,previous messages possibly indicate the reason.

Destination:

console.msg

ERZ022058E Error obtaining access to Transient Data(TD) queue ’TDQname’.

Explanation: If this happens during normal operation,CICS was not able to obtain access to the named queueprior to performing a read, write, or delete operationon it. CICS was not able to record the fact that thequeue has been accessed. This probably indicates anunsuccessful allocation request from the Region Pool.You can confirm this by searching for other errormessages preceding this one.

System action: CICS abnormally terminates (withcode A221) the transaction attempting to perform theoperation.

User response: Investigate the error logs for relatedmessages and, if the problem is unsuccessful memoryallocation, then increase the Region Pool allocation andrestart CICS.

Destination:

CSMT

ERZ022059E Unsuccessfully obtained file serverhandle for operation on Transient Data(TD) queue ’TDQname’.

Explanation: For files used to store intrapartition TDqueue data, CICS must obtain file handles when atransaction first operates on a queue. This error arises ifCICS cannot obtain a file handle. See previousmessages for details of the file server error.


User response: This possibly indicates an unsuccessfulattempt to acquire Region Pool memory. You possiblyneed to increase the size of the Region Pool and restartCICS.

Destination:

console.msg

ERZ022060E Log service error logging operation onphysically recoverable Transient Data(TD) queue ’TDQname’.

Explanation: CICS must log all operations onphysically recoverable TD queues as they areperformed. CICS issues this message if it cannot writethe log data. CICS possibly did not perform the queueoperation correctly, and is possibly unable to recoverthe queue.

System action: CICS disables the queue, andterminates the transaction with abend code A228.

User response: Other messages possibly indicate thenature of the log service error. Check the error logs andpossibly the log server to ensure that its data iscorrectly formatted.

Destination:

console.msg

ERZ022064E Abnormal termination U2264: Systemlog record corrupted for physicallyrecoverable Transient Data (TD) queue’TDQname’.

Explanation: CICS found that the system log recordidentifying the queue read/write pointers for thenamed queue is incorrectly formatted.

System action: CICS abnormally terminates startup.

User response: Identify the source of the error in thesystem log data. If you cannot recover or repair thedata, you possibly need to cold start CICS.

Destination:

console.msg

ERZ022055W • ERZ022064E


ERZ022065E Abnormal termination U2265:Checkpoint record identifyingread/write pointers for intrapartitionTransient Data (TD) queue ’TDQname’incorrectly formatted.

Explanation: CICS found that the shutdowncheckpoint record identifying the queue read/writepointers for the named queue is incorrectly formatted.


User response: Identify the source of the error in theshutdown data. If you cannot recover or repair thedata, you possibly need to cold start CICS.

Destination:

console.msg

ERZ022067E Unsuccessful attempt allocating storagewhen deleting Transient Data (TD)queue ’TDQname’.

Explanation: CICS generates this error when anunsuccessful attempt is made to acquire memory fromthe Region Pool during a DELETEQ TD operation.Storage is allocated when waiting on a queue lock andwhen recording operations on a recoverable queue.

System action: CICS abends the task with an A223abend.

User response: Consider reconfiguring the system toincrease the amount of Region Pool storage availableand restarting CICS.

Destination:

console.msg

ERZ022068E Unsuccessful storage allocation attemptwhen allocating buffer during write ofTransient Data (TD) for queue’TDQname’.

Explanation: This can occur when writing data to anintrapartition queue. It indicates that CICS was not ableto allocate a buffer from the Region Pool formanipulation of the user-supplied data into the formatrequired by the file server file storing the intrapartitionqueue data.


User response: You possibly need to increase the sizeof the Region Pool and restart CICS.

Destination:

console.msg

ERZ022069E Abnormal termination U2269: SystemTransient Data (TD) queue ’TDQname’cannot be extrapartition input.




Destination:

console.msg

ERZ022070E Abnormal termination U2270: SystemTransient Data (TD) queue ’TDQname’cannot be extrapartition output.




Destination:

console.msg

ERZ022071E Unsuccessful storage allocation forTransient Data (TD) queue.

Explanation: When CICS performed either an EXECCICS READQ TD or EXEC CICS WRITEQ TDoperation, it was not able to allocate a buffer forstorage of TD queue data.

System action: The message is logged, and the task isabnormally terminated with code A223.

User response: You possibly need to increase the sizeof the Task-Shared Pool and restart CICS.

Destination:

console.msg

ERZ022072E Unsuccessful attempt at obtaining a fileserver handle for a Transient Data (TD)queue operation.

Explanation: When CICS attempted an EXEC CICSREADQ TD or EXEC CICS WRITEQ TD operation onan intrapartition TD queue, it detected an error whileobtaining a file handle for the file used to store TDqueue data.

ERZ022065E • ERZ022072E



User response: Check the message logs for previouserrors that possibly identify the nature of the file servererror.

Destination:

console.msg

ERZ022074E Abnormal termination U2274:Unsuccessful storage allocation whenprocessing a system log record forTransient Data (TD) queue ’TDQname’.

Explanation: CICS detected this error duringauto-start processing following a system abnormaltermination. CICS cannot allocate storage from theRegion Pool to hold physically recoverable queue datarecovered from the system log. CICS requires thisstorage temporarily, during startup, when building upa picture of the state of the system at the time of theabnormal termination.

System action: CICS terminates startup with abendcode U2274.

User response: You possibly need to increase the sizeof the Region Pool and restart CICS. Alternatively, youcan request a cold start.

Destination:

console.msg

ERZ022076E System error errorCode closing filestoring data for extrapartition TransientData (TD) queue ’TDQname’.

Explanation: CICS detected an error when closing thefile used to store data for the indicated queue. CICSshows the error number returned from the close call.This error can occur when a transaction finishes.


User response: Check the error number and takesuitable corrective action. The most likely errors areeither that the file access permissions are incorrect orthat the filename supplied in the queue definition isincorrect. If you cannot solve the problem, contact yoursupport organization.

Destination:

console.msg

ERZ022077E Unsuccessful storage allocation whenobtaining a file descriptor for operationon Transient Data (TD) queue’TDQname’.

Explanation: CICS was unsuccessful when trying toallocate memory from the Region Pool for an operating

system file handle to use for operations on anextrapartition TD queue.


User response: This indicates a memory allocationfailure. You possibly need to increase the size of theRegion Pool and restart CICS.

Destination:

console.msg

ERZ022080E Unexpected end of file reading recordrecordNumber from extrapartitionTransient Data (TD) queue ’TDQname’.

Explanation: CICS detected the end of the queue datafile part-way through reading a record from the file.This error indicates a format error in the queue data, asopposed to the queue empty condition. If the queue isempty when the read commences, CICS raises aQZERO condition. This error arises because the queueis not empty but, for example, the last record in a fixedlength record queue is too short, or the last record in abyte-terminated record queue is not followed by theterminator byte.


User response: Check the return code and takeappropriate action.

Destination:

CSMT

ERZ022081E Record at position ’recordNumber’, indata file for Transient Data (TD) queue’TDQname’, exceeds maximum recordsize.

Explanation: CICS generates this error when readingan extrapartition Transient Data (TD) queue whoseRecordType attribute is line-oriented, null-terminated,byte-terminated, or variable-length. The first three casesindicate that CICS read the maximum number of bytesthat can be represented in a 32-bit field without theappropriate terminator byte being found. The last caseindicates that the length count preceding the record inthe data file is invalid. All cases signify that the filedata format is in error and that CICS regards this as anI/O error.


User response: Check the return code and takeappropriate action.

Destination:

CSMT

ERZ022074E • ERZ022081E


ERZ022082E System error errorCode. Only wrotebytesWritten out of recordLength bytes toextrapartition Transient Data (TD) queue’TDQname’ for record recordNumber.

Explanation: CICS generates this error if it cannotwrite a complete record to an extrapartition TD queueon disk. The disk where the file resides is probably full.The associated system error code identifies the error inmore detail.

System action: CICS raises the IOERR condition, butdoes not disable the queue. CICS does not advance theread pointer for the queue. This means that asubsequent write to the queue starts at the same pointin the data file (as indicated by the third parameter inthe message).

User response: Allocate more disk space to the diskpartition storing the queue data file.

Destination:

CSMT

ERZ022083E Unsuccessful preparation for commit orabnormal termination during transactionreplay.

Explanation: CICS generates this error duringabnormal termination recovery when repreparing atransaction. CICS was not able to register callbackfunctions to be run after committing or abnormallyterminating the outstanding Transient Data (TD) queueoperations.


User response: The error is probably due to a memoryallocation failure. You must check for related messagesand respond accordingly.

Destination:

console.msg

ERZ022087E Abnormal termination U2287:Unsuccessful attempt at freeing logicallyrecoverable intrapartition Transient Data(TD) queue file handle.

Explanation: The file server returned an error whenattempting to free the file handle of the file storinglogically recoverable TD queue data.


User response: Check that the file server is correctlyinitialized. Previous messages generated possiblyindicate the nature of the file server error.

Destination:

console.msg

ERZ022088E Abnormal termination U2288:Unsuccessful attempt at freeingphysically recoverable intrapartitionTransient Data (TD) queue file handle.

Explanation: The file server returned an error whenattempting to free the file handle of the file storingphysically recoverable TD queue data.



Destination:

console.msg

ERZ022089E Abnormal termination U2289:Unsuccessful attempt at freeingnon-recoverable intrapartition TransientData (TD) queue file handle.

Explanation: The file server returned an error whenattempting to free the file handle of the file storingnon-recoverable TD queue data.



Destination:

console.msg

ERZ022090E Unsuccessful attempt at triggeringtransaction ’transId’, during a writeoperation to Transient Data (TD) queue’TDQname’.

Explanation: CICS was not able to trigger atransaction after writing to a TD queue.


User response: Check the message logs for previouserrors to ascertain why the transaction was not able tobe started.

Destination:

CSMT

ERZ022091E Unsuccessful attempt at triggeringtransaction ’transId’ during startup, forTransient Data (TD) queue ’TDQname’.

Explanation: CICS was not able to trigger atransaction during an auto-start following normalshutdown or an auto-start following an abnormalshutdown.

System action: CICS continues the startup process.

ERZ022082E • ERZ022091E


User response: Check the message logs for previouserrors to ascertain why the transaction was unable tobe started.

Destination:

CSMT

ERZ022094E Attempt to flush disabled TransientData (TD) queue ’TDQname’.

Explanation: CICS cannot flush an extrapartition TDqueue that has been disabled.

System action: CICS abnormally terminates thetransaction with the abend code ATTD

User response: Check to see why the queue isdisabled; it is possible that a previous operationencountered an error that resulted in the queue beingdisabled. Check the message logs for previous errors.

Destination:

CSMT

ERZ022095E System error errorCode flushing data inTransient Data (TD) queue ’TDQname’.

Explanation: CICS was unsuccessful when flushingdata to the file used for storing the namedextrapartition TD queue.

System action: Processing continues; however, othermessages are possibly be generated as a result of thisone.

User response: Check the return code and takeappropriate action. It is possible that the disk partitionstoring the queue data file is full. Allocate more diskspace to the disk partition storing the queue data file.

Destination:

CSMT

ERZ022096E System error errorCode flushing data inTransient Data (TD) queue ’TDQname’.

Explanation: CICS was unsuccessful when flushingdata to the file used for storing the namedextrapartition TD queue.

System action: The IOERR condition is raised.

User response: Check the system error number andtake appropriate action. It is possible that the diskpartition storing the queue data file is full; if so,allocate more disk space to the disk partition storingthe queue data file.

Destination:

CSMT

ERZ022097E Error errorCode occurred changing filepermissions of data file ’fileName’ forextrapartition Transient Data (TD) queue’TDQname’.

Explanation: CICS was unsuccessful when attemptingto change the file access permissions for the file storingextrapartition TD queue data.

System action: The named queue is disabled and theIOERR condition is raised.

User response: It is probable that CICS does not havewrite permission to the file containing the TD queuedata.

Destination:

console.msg

ERZ022098I Replay record for Transient Data (TD)queue ’TDQname’ is missing fromdatabase or is of wrong type.

Explanation: Acceptable inconsistency found duringreplay.



Destination:

console.msg

ERZ022099E Failed to open file server file storingdata for intrapartition queue ’TDQname’.

Explanation: This message is generated whenperforming an A22B abend following an unsuccessfulintrapartition TDQ operation. It indicates that the fileused to store data for the intrapartition queue inquestion was unable to be opened or had an incorrectformat.


User response: Check for related messages detailingthe server problem. The file server is possiblytemporarily unavailable or the file configurationpossibly needs to be changed.

Destination:

console.msg

ERZ022100E Incorrect file organization for filestoring physically recoverableintrapartition Transient Data (TD) queuedata

Explanation: The file server file specified for storageof physically recoverable TD queue records does nothave a clustered file organization.


ERZ022094E • ERZ022100E


User response: Use file server administration tools toremove the file used for storing physically recoverableTD queues (the file used can be determined from theRegion Definition (RD)) and create a new file with aclustered file organization. If the error persists contactyour support organization.

Destination:

console.msg

ERZ022101E Incorrect file organization for filestoring logically recoverableintrapartition Transient Data (TD) queuedata

Explanation: The file server file specified for storageof logically recoverable Transient Data (TD) queuerecords does not have a clustered file organization.


User response: Use file server administration tools toremove the file used for storing logically recoverableTD queues (the file used can be determined from theRegion Definition (RD)) and create a new file with aclustered file organization. If the error persists contactyour support organization.

Destination:

console.msg

ERZ022102E Incorrect file organization for filestoring non-recoverable intrapartitionqueue data

Explanation: The file server file specified for storageof non-recoverable Transient Data (TD) queue recordsdoes not have a clustered file organization.


User response: Use file server administration tools toremove the file used for storing non-recoverable TDqueues (the file used can be determined from theRegion Definition (RD)) and create a new file with aclustered file organization. If the error persists contactyour support organization.

Destination:

console.msg

ERZ022104E Incorrect record format for file storingphysically recoverable intrapartitionTransient Data (TD) queue data.

Explanation: The file server file specified for storageof physically recoverable TD queue records does nothave variable length record format.


User response: Use file server administration tools toremove the file used for storing physically recoverable

TD queues (the file used can be determined from theRegion Definition (RD)) and create a new file with avariable length record format. If the error persistscontact your support organization.

Destination:

console.msg

ERZ022105E Incorrect record format for file storinglogically recoverable intrapartitionqueue data.

Explanation: The file server file specified for storageof logically recoverable Transient Data (TD) queuerecords does not variable length record format.


User response: Use file server administration tools toremove the file used for storing logically recoverableTD queues (the file used can be determined from theRegion Definition (RD)) and create a new file with avariable length record format. If the error persistscontact your support organization.

Destination:

console.msg

ERZ022106E Incorrect record format for file storingnon-recoverable intrapartition queuedata.

Explanation: The file server file specified for storageof non-recoverable Transient Data (TD) queue recordsdoes not have variable length record format.


User response: Use file server administration tools toremove the file used for storing non-recoverable TDqueues (the file used can be determined from theRegion Definition (RD)) and create a new file with avariable length record format. If the error persistscontact your support organization.

Destination:

console.msg

ERZ022107E Incorrect key specification for filestoring physically recoverableintrapartition Transient Data (TD)queues.

Explanation: The file server file specified for storageof physically recoverable TD queue records does nothave the correct key specification.


User response: Use file server administration tools toremove the file used for storing physically recoverableTD queues (the file used can be determined from theRegion Definition (RD)) and create a new file with the

ERZ022101E • ERZ022107E


correct key specification. If the error persists contactyour support organization.

Destination:

console.msg

ERZ022108E Incorrect key specification for filestoring logically recoverableintrapartition Transient Data (TD)queues.

Explanation: The file server file specified for storageof logically recoverable Transient Data (TD) queuerecords does not have the correct key specification


User response: Use file server administration tools toremove the file used for storing logically recoverableTD queues (the file used can be determined from theRegion Definition (RD)) and create a new file with thecorrect key specification. If the error persists contactyour support organization.

Destination:

console.msg

ERZ022109E Incorrect key specification for filestoring non-recoverable intrapartitionTransient Data (TD) queues.

Explanation: The file server file specified for storageof non-recoverable Transient Data (TD) queue recordsdoes not have the correct key specification.


User response: Use file server administration tools toremove the file used for storing non-recoverable TDqueues (the file used can be determined from theRegion Definition (RD)) and create a new file with thecorrect key specification. If the error persists contactyour support organization.

Destination:

console.msg

ERZ022110E CICS self-consistency checking hasdetected an inconsistency in the CICSinternal data structures - details are inthe next message

Explanation: CICS has detected an inconsistency in itsinternal data structures.

System action: Self-consistency checking continues.

User response: Try to determine whether a usertransaction has overwritten the data. If this is not thecase contact your support organization.

Destination:

console.msg

ERZ022111E CICS cannot delete the extrapartitionTransient Data (TD) queue ’TDQname’ asit is not closed and disabled

Explanation: An attempt was made to delete a queuewhen it is not closed and disabled.


User response: Close and disable the queue usingCEMT or the EXEC CICS SET TDQUEUE interface.

Destination:

CSMT

ERZ022112E CICS cannot delete the intrapartitionTransient Data (TD) queue ’TDQname’ asit is not disabled.

Explanation: An attempt was made to delete a queuewhen it is not disabled.


User response: Disable the queue using CEMT or theEXEC CICS SET TDQUEUE interface.

Destination:

CSMT

ERZ022113I Transient Data queues processed!

Explanation: CICS has finished processing TD queues.

System action: CICS has finished TD initialization.


Destination:

console.msg

ERZ022114E CICS cannot add indirect TD queue’indirectQueue’ because the referencedqueue ’TDQname’ is undefined

Explanation: You cannot add an indirect transient dataqueue which references an undefined transient dataqueue. The undefined queue is named in theIndirectQueueId attribute of the TD queue’s definition.

System action: CICS has not added the new indirectTD queue.

User response: Define the referenced queue first, thenadd the indirect queue.

Destination:

console.msg

ERZ022108E • ERZ022114E


ERZ022115E CICS cannot delete TD queue’TDQname’ because there arequeueCountu other indirect TD queuesthat reference it

Explanation: You cannot delete a transient data queuewhich is referenced by an indirect transient data queue.First you must delete all the indirect TD queues thatreference it, then you can delete this queue.

System action: CICS has not deleted the TD queue.

User response: If you really want to delete this TDqueue, then delete all the indirect TD queues thatreference this queue, or else make them reference otherTD queues instead.

Destination:

console.msg

ERZ022116E CICS cannot delete TD queue’TDQname’ because it is a system TDqueue

Explanation: You cannot delete a transient data queuewhich is CICS system transient data queue. This queueis necessary for CICS to function correctly.


User response: Do not delete this TD queue.

Destination:

console.msg

ERZ022117E CICS cannot delete TD queue’TDQname’ because it is not empty

Explanation: You cannot delete a transient data queuewhich still has items on it.


User response: To be able to delete the queue,perform the following steps: re-enable the queue, deletethe items from the queue, and disable it again. You canempty the queue by reading all the items on it.

Destination:

console.msg

ERZ022118E CICS cannot install remote TD queue’TDQname’ because its RemoteSysId’sysId’ is the local sysid or is blank

Explanation: CICS cannot install this Transient Dataqueue because it has a destination type (DestType) ofremote and a remote system id (RemoteSysId) whichmatches the local sysid or is blank. The local sysid canbe found in the LocalSysId attribute in the RegionDefinition.

System action: The TD queue has not been installed.

User response: To make the TD queue local, changethe queue’s DestType to be intrapartition,extrapartition or indirect. In that case the RemoteSysIdis ignored. To make the TD queue remote, change itsRemoteSysId to be the sysid of another CICS region.

Destination:

console.msg

ERZ022119E Unable to open file ’fileName’ to performrecovery processing for Transient Dataqueues

Explanation: CICS cannot obtain the data needed forrecovery processing of Transient Data queues, as it isunable to open the file containing the data.

System action: The region is abnormally terminated.

User response: Examine accompanying messages todetermine why the file cannot be opened. If the file isdamaged, a backup copy of the file can possibly bemade available. If the problem cannot be resolved, acold start is required.

Destination:

console.msg

ERZ022120E Unsuccessful buffer storage allocationfor recovery of Transient Data queues

Explanation: CICS was unable to allocate sufficientstorage from the task private storage pool, whenattempting to recover Transient Data during an autostart after a region failure.


User response: Increase the size of the task privatestorage pool by increasing the value for theMaxTaskPrivatePool region attribute, and retry theauto start. Alternatively, perform a cold start.

Destination:

console.msg

ERZ022121E Unable to read data from file ’fileName’to recover Transient Data queues

Explanation: CICS was unable to obtain data from thefile containing Transient Data recovery information, sois unable to recover Transient Data queues.


User response: Examine accompanying messages todetermine the nature of the problem with the file. If theproblem cannot be rectified, a cold start is required.

Destination:

console.msg

ERZ022115E • ERZ022121E


ERZ022122E Unable to recover Logically RecoverableTransient Data queues

Explanation: CICS was unable to obtain theinformation needed to restore Logically RecoverableTransient Data during region restart after region failure.The information is stored in the filesystem, in the fileused to store Logically Recoverable Transient Dataqueue records. If the information cannot be retrievedfrom this file during emergency restart, CICS is unableto restore internal data necessary for Transient Data, sothe region does not start.



Destination:

console.msg

ERZ022123E Unable to recover PhysicallyRecoverable Transient Data queues

Explanation: CICS was unable to obtain theinformation needed to restore Physically RecoverableTransient Data during region restart after region failure.The information is stored in the filesystem, in the fileused to store Physically Recoverable Transient Dataqueue records. If the information cannot be retrievedfrom this file during emergency restart, CICS is unableto restore internal data necessary for Transient Data, sothe region does not start.



Destination:

console.msg

ERZ022124E Abnormal Termination U2224: Recoveryof Transient Data Queues failed

Explanation: CICS was unable to recover datarequired to provide Transient Data queues. This data isstored in the files which contain Transient Data queuerecords. The region is unable to continue withoutrecovery of this data.

System action: Region startup is abnormallyterminated

User response: Examine accompanying messages todetermine the nature of the problem. If the problemcannot be rectified, a cold start is required.

Destination:

console.msg

ERZ022125I Recovery of Transient Data queues iscomplete

Explanation: CICS has completed recovery processingfor Transient Data queues.

System action: None

User response: None

Destination:

console.msg

ERZ022126E CICS is unable to save recoveryinformation for Transient Data queue’TDQname’

Explanation: CICS is unable to save information aboutoperations on recoverable Transient Data queues attransaction syncpoint. If the transaction completes,CICS is possibly unable to recover the queue after asubsequent failure.


User response: Other messages indicate the cause ofthe problem. The recovery information is written to thefilesystem, so there is possibly a filesystem errorreported before this error.

Destination:

console.msg

ERZ022127E Unsuccessful buffer storage allocationfor saving Transient Data queuerecovery information

Explanation: CICS is unable to allocate sufficient taskprivate storage to process recovery information for atransient data queue. Such information must be storedin order to guarantee correct recovery of Transient Dataqueues after a system failure.


User response: Increase the amount of task privatestorage available to the transaction by increasing thevalue of the MaxTaskPrivatePool region attribute.Restart the region and resubmit the transaction.

Destination:

console.msg

ERZ022128E Unable to update recovery informationfor Transient Data queue ’TDQname’ infile ’fileName’

Explanation: CICS is unable to update an existing filerecord with information to provide recovery of thetransient data queue.

ERZ022122E • ERZ022128E



User response: Other messages indicate the cause ofthe error, perhaps a file system error. Correct theproblem and resubmit the transaction.

Destination:

console.msg

ERZ022129E Unable to write recovery information forTransient Data queue ’TDQname’ to file’fileName’

Explanation: CICS is unable to write a new file recordcontaining information to provide recovery of thetransient data queue.



Destination:

console.msg

ERZ022130E Read of file ’fileName’ for recovery ofTransient Data queues failed withtimeout condition

Explanation: A read operation for recovery ofTransient Data queues did not complete within thetransaction DeadLockTimeout value. This can becaused by a lock held on the file by an unresolvedtransaction.

System action: The region is abnormally terminatedwith abend code U2224.

User response: Determine the cause of the timeouterror. Use file server administration commands toidentify inflight transactions which are holding locks onthe file, and if necessary force the transactions with thetkadmin command, if the file server is SFS, or listindoubt transactions with prompting, if the file serveris DB2. Note that if the file server is SFS, these locksare automatically dropped when the time specified bythe IdleTimeout attribute in the SFS Definitions (SSD)has expired; CICS can then be restarted. If the timeoutis not caused by a retained lock, it can possibly besolved by increasing the DeadLockTimeout value forthe Initialization transaction, CAIN, which performs therecovery processing. If the problem cannot be solved, acold start of the region is possibly necessary.

Destination:

console.msg

ERZ022131W Unable to save recovery information forPhysically Recoverable Transient DataQueues during syncpoint processing.

Explanation: This message is generated duringsyncpoint processing for physically recoverable TDqueues. Syncpoint processing is performed forphysically recoverable queues to confirm that the latestreader of the queue has indeed processed the lastrecord read. If this error occurs then the last recordread from the queue can possibly be presented againfor reading in the event of a subsequent system crash.

System action: The syncpoint is continued. In theevent of a subsequent region crash the last record readfrom the queue can possibly be presented again forreading if the queue has not been read by a differenttask in the meantime.

User response: Have the system administrator checkfor the cause of the failure. The recovery information isstored in the filesystem, so there are possibly messagesindicating a filesystem problem.

Destination:

console.msg

ERZ022132W During a cold start, CICS is unable toopen and empty the files that storeTransient Data Queue data

Explanation: During a cold start of the CICS region,the files that store Transient Data Queue data in thefilesystem need to be emptied to keep the CICS andfilesystem information consistent. This messageindicates that there has been some error in opening andemptying these files.

System action: The region start continues. Furtherattempts are made by CICS to empty the files ifTransient Data queues are accessed.

User response: Examine other messages to determinethe cause of the error and correct it if possible. If adatabase is being used as the filesystem for TransientData queues, and CICS attempts to empty the filesduring a user task that subsequently abends, the CICSand filesystem data is inconsistent. To rectify such asituation, the problem that is preventing the files frombeing opened and emptied must first be solved, thenthe region must either be cold started or be shut downwith an immediate shutdown and auto started to forcerecovery of the queues.

Destination:

console.msg

ERZ022133W A error occurred while removingobsolete records from Transient DataQueue ’queueName’

Explanation: During a warm start of the CICS region,an error occurred while trying to remove redundant

ERZ022129E • ERZ022133W


records from the specified Transient Data Queue.

System action: The region start continues.

User response: Examine other messages to determinethe cause of the error and correct it if possible.

Destination:

console.msg

ERZ022134W CICS-private Transient Data QueuePurge transaction (CTDP): interval ofTDPurgeInterval is too low, IntervalUsedminutes used instead.

Explanation: The region’s TDPurgeInterval attributevalue TDPurgeInterval is too low. CICS-private TransientData Queue Purge transaction (CTDP) has used theminimum interval permitted.


User response: Increase the value of theTDPurgeInterval attribute in your region’s permanentdatabase Region Definitions using Resource DefinitionOnline (RDO).

Destination:

console.msg

ERZ022135W Unsuccessful attempt to rescheduleCICS-private Transient Data QueuePurge Transaction (CTDP).

Explanation: The CICS-private Transient Data QueuePurge (CTDP) transaction cannot reschedule itself to atthe next scheduled time.

System action: The current CTDQ transactioncontinues processing, but CTDQ is not run againduring this instantiation of the region.

User response: Restart the region at the earliestpossible opportunity.

Destination:

console.msg

ERZ022136W Unsuccessful attempt to startCICS-private Transient Data QueuePurge transaction (CTDP).

Explanation: CICS detected an error when attemptingto start the Transient Data Queue Purge transaction,CTDP.

System action: CICS continues but CTDP is not in thisregion instantiation.

User response: Check the file access permissions forrunning CTDP, and check that a valid permanentdatabase Transaction Definition (TD) entry exists forCTDP. Restart the region at the earliest possible

opportunity so that TD Queue purging can beperformed.

Destination:

console.msg

ERZ022137I Purging transient data queues (CTDP).

Explanation: CICS is purging deleted TD queueentries.

System action: CICS is purges deleted TD queueentries.


Destination:

console.msg





Destination:

console

ERZ022139E System error errorCode while takingbackup of file storing data forextrapartition Transient Data (TD) queue’TDQname’.

Explanation: CICS detected an error when taking thebackup of the file used to store data for the indicatedqueue. While backing up the TDQ Extrapartition Filecics renames the existing file to filename.timestampCICS shows the error number returned from therename call.

System action: CICS does not proceed ahead with thebackup and continues to write the record in current EPTDQ File.

User response: Check the error number and takesuitable corrective action. The most likely error is thatthe file access permissions are incorrect If you cannotsolve the problem, contact your support organization.

Destination:

ERZ022134W • ERZ022139E


console.msg

ERZ022140E Unable to open CSMT backup file (File:’fileName’ Error: ’errorNumber’)

Explanation: The specified file was unable to beopened.

System action: The command returns with an error.

User response: Check the file exists.

Destination:

stderr

ERZ023001I Temporary Storage Queue Aging: Queue’queueName’ deleted

Explanation: Confirmation that the queue ’queueName’has been purged by the CICS-private TemporaryStorage Queue Aging transaction (CAGE).

System action: CAGE continues processing.

User response: None

Destination:

CSMT

ERZ023002W Temporary Storage Queue Aging:Unsuccessful attempt to delete queue’queueName’

Explanation: Temporary Storage Queue Agingtransaction (CAGE) detected an error when attemptingto purge the queue ’queueName’. The problem affectsjust the one queue and so CAGE allows queue aging tocontinue after producing this diagnostic.

System action: The queue ’queueName’ is not deletedand CAGE continues queue aging of other queues.CAGE makes further attempts to delete this queue thenext time that CAGE runs.

User response: Refer to any previous messagesrelating to the attempt to delete this queue.

Destination:

CSMT

ERZ023003E Temporary Storage (TS): Queue name’queueName’ is too long

Explanation: Temporary Storage (TS) queue name’queueName’ exceeds the maximum allowed length of 8bytes.

System action: If the error occurs during regionstartup then CICS does not install the invalid TStemplate, but processing continues. If the error occursduring a Resource Definition Online (RDO) sessionthen the RDO operation is terminated.

User response: Reduce length of queue name’queueName’.

Destination:

stderr and console.msg

ERZ023004E CICS-private Temporary Storage Queueaging transaction (CAGE) alreadyrunning; Quitting...

Explanation: The CICS-private Temporary StorageQueue aging transaction (CAGE) is already running atthe moment; this instance of the transaction is notneeded.

System action: CICS terminates subsequent (duplicate)invocations of CAGE.

User response: Investigate why an earlier invocationof this transaction is apparently already running.

Destination:

console.msg

ERZ023005E Temporary Storage (TS): Error writingitem itemNumber to queue ’queueName’

Explanation: A Temporary Storage (TS) write orrewrite operation on the TS queue ’queueName’ wasunsuccessful.

System action: If this message has been producedwhile processing a CICS Temporary Storage API, thenan IOERR condition is returned. Otherwise refer to theSystem Actions of any subsequent messages.

User response: If this message has been producedwhile processing a CICS Temporary Storage API, yourprogram specifies how the IOERR condition is handled.Otherwise refer to the User Responses of anysubsequent messages.

Destination:

console.msg

ERZ023006E Temporary Storage (TS): Error readingitem itemNumber from queue ’queueName’

Explanation: A Temporary Storage (TS) read operationon the TS queue ’queueName’ was unsuccessful.



Destination:

ERZ022140E • ERZ023006E


console.msg

ERZ023007E Temporary Storage (TS): Error deletingitem(s) from queue ’queueName’

Explanation: Temporary Storage (TS) was unable toremove item(s) from the queue when deleting thequeue ’queueName’.

System action: CICS marks the queue as deleted andassumes that its resources were purged. If this messagehas been produced while processing a CICS TemporaryStorage API, then an IOERR condition is returned.Otherwise refer to the System Actions of anysubsequent messages.


Destination:

console.msg

ERZ023010E Temporary Storage (TS): File server error

Explanation: CICS detected an error when attemptingto obtain a file handle for use by Temporary Storage.


User response: If this message has been producedwhile processing a CICS Temporary Storage API, yourprogram specifies how the IOERR condition is handled.Otherwise refer to the User Responses of anysubsequent messages. Refer to any previous messagesdetailing what file system error has occurred.

Destination:

console.msg

ERZ023011W Unsuccessful attempt to startCICS-private Temporary Storage Agingtransaction (CAGE)

Explanation: CICS detected an error when attemptingto start the Temporary Storage Aging transaction,CAGE.

System action: CICS continues but CAGE is not runin this region instantiation.

User response: Check the file access permissions forrunning CAGE, and check that a valid permanentdatabase Transaction Definition (TD) entry exists forCAGE. Restart the region at the earliest possibleopportunity so that TS queue aging can be performed.

Destination:

console.msg

ERZ023012E Abnormal termination U2312:Unsuccessful allocation of Region Poolmemory for Temporary Storage (TS)

Explanation: CICS is unable to allocate enoughmemory, from the Region Pool, to initialize TemporaryStorage (TS).


User response: You can increase the size of the RegionPool available by restarting the region and overridingthe MaxRegionPool attribute, with a larger value, onthe command line.

Destination:

console.msg

ERZ023013W CICS-private Temporary Storage Agingtransaction (CAGE): Queue age limit ofTSQageLimit is too low, ageLimitUsed daysused instead.

Explanation: The region’s TSQAgeLimit attributevalue TSQageLimit is too low. CICS-private TemporaryStorage Aging transaction (CAGE) has used theminimum age limit permitted.


User response: Increase the value of theTSQAgeLimit attribute in your region’s permanentdatabase Region Definitions using Resource DefinitionOnline (RDO).

Destination:

console.msg

ERZ023014E Temporary Storage (TS): Queue Name’queueName’ has Remote Name’remoteName’ of different length

Explanation: Queue name length is different from thelength of its remote name. Both names must be of thesame length.

System action: The queue is removed from theruntime database.

User response: Update the permanent database entryfor ’queueName’ and make the remote name of thequeue the same length as the queue’s name or deletethe queue and add a new one with a name whoselength is the same as that of the remote name.

Destination:

console.msg

ERZ023007E • ERZ023014E


ERZ023015E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) Logical Unit ofWork (LUW) Chain at addresscorruptLUWaddress in TCA at TCAaddress.

Explanation: CICS self-consistency checking hasdetected that the chain of queues involved in thecurrent LUW for the transaction has been overwrittenby invalid data.


User response: Restart the region. If CICSself-consistency checking continues to detectinconsistencies contact your support organization.

Destination:

console.msg

ERZ023016E CICS self-consistency checking hasdetected a Signature inconsistency:expected ’expectedSignature’ found’actualSignature’ at addresssignatureAddress

Explanation: CICS self-consistency checking hasdetected that the signature ’actualSignature’ isinconsistent with that expected ’expectedSignature’.


User response: Restart the region at the earliestpossible opportunity. If CICS self-consistency checkingcontinues to detect inconsistencies contact your supportorganization.

Destination:

console.msg

ERZ023017I Processing temporary storage queues ...

Explanation: CICS is now performing startupprocessing of temporary storage queues. This stepoccurs after log file processing has been completed andhence after queues have been recovered from the log.


User response: None

Destination:

console.msg

ERZ023018E CICS self-consistency checking hasdetected a zero length TemporaryStorage (TS) SET buffer at addressbufferAddress in the TCA at TCAaddress

Explanation: CICS self-consistency checking hasdetected that the Temporary Storage (TS) SET bufferlength stored at address bufferAddress has been

overwritten with an invalid value of 0.


User response: Restart the region at the earliestpossible opportunity. If CICS self-consistency checkingcontinues to detect inconsistencies contact your supportorganization.

Destination:

console.msg

ERZ023019E Abnormal termination U2319:Temporary Storage (TS) initializationcould not rewrite the Temporary Storage(TS) runtime database entry for queue’queueName’

Explanation: CICS was not able to rewrite the runtimedatabase TS entry ’queueName’.


User response: Refer to any previous messagesindicating why the runtime database entry ’queueName’was not able to be updated.

Destination:

console.msg

ERZ023020E Temporary Storage (TS): Unsuccessfulcheckpoint - unable to allocate RegionPool memory

Explanation: CICS was not able to checkpoint theTemporary Storage (TS) state information because itwas unable to allocate Region Pool memory.

System action: The system log does not checkpointsuccessfully. CICS can possibly take significantly longerto perform recovery processing during startup.

User response: Refer to any previous messagesindicating why the Region Pool memory was not ableto be allocated. You can increase the size of the RegionPool available by restarting the region and overridingthe MaxRegionPool attribute, with a larger value, onthe command line.

Destination:

console.msg

ERZ023021W Unsuccessful attempt to rescheduleCICS-private Temporary Storage Agingtransaction (CAGE)

Explanation: The CICS-private Temporary StorageAging transaction (CAGE) transaction cannotreschedule itself to run the following midnight.

System action: The current CAGE transactioncontinues processing, but CAGE is not run againduring this instantiation of the region.

ERZ023015E • ERZ023021W


User response: Restart the region at the earliestpossible opportunity.

Destination:

console.msg

ERZ023022E Temporary Storage (TS): NOSPACEcondition on MAIN queue ’queueName’

Explanation: CICS raised a NOSPACE condition forthe Main (TS) queue ’queueName’.

System action: CICS periodically retries the operationthat resulted in NOSPACE until sufficient spacebecomes available and the operation succeeds or thetransaction’s deadlock timeout is reached. If thetransaction’s deadlock timeout is reached then thetransaction is abnormally terminated with code AKCS(or AEIR).

User response: Delete any MAIN TS queues that areno longer required. Try to identify particulartransactions using large amounts of Task-Shared Poolstorage. Try to run these at times of low system activity,or reduce their storage requirements. If manytransactions are affected, reduce the number ofapplication servers running. Alternatively increase thesize of your Task-Shared Pool by changing the value ofthe MaxTSHPool attribute in the Region Definitions.

Destination:

CSMT

ERZ023023E Temporary Storage (TS): NOSPACEcondition on Auxiliary queue’queueName’

Explanation: CICS raised a NOSPACE condition forthe Auxiliary (TS) queue ’queueName’.

System action: CICS periodically retries the operationthat resulted in NOSPACE until sufficient spacebecomes available and the operation succeeds or untilthe transaction’s deadlock timeout is reached. If thetransaction’s deadlock timeout is reached then thetransaction is terminated with abend code AKCS.

User response: Delete any Auxiliary TS queues thatare no longer required. Try to identify particulartransactions using large amounts of File Space. Try torun these at times of low system activity, or reducetheir storage requirements. If many transactions areaffected, reduce the number of application serversrunning.

Destination:

CSMT

ERZ023024I Temporary Storage (TS): NOSPACEcondition resolved on queue ’queueName’

Explanation: CICS resolved the NOSPACE conditionfor the queue ’queueName’.


User response: None

Destination:

CSMT

ERZ023025W Temporary Storage (TS): Invaliddatabase entry ’resourceName’ removedfrom runtime database

Explanation: During initialization, CICS has foundand deleted an invalid Temporary Storage (TS) entryfrom the runtime database. A message has already beengenerated that indicates why the entry is consideredinvalid.

System action: The invalid entry is deleted from theruntime database.

User response: Refer to the previous messagedetailing why the entry is considered invalid.

Destination:

console.msg

ERZ023026E Temporary Storage (TS): Vetoed attemptto insert entry ’resourceName’ sinceRemoteName ’remoteName’ does not havethe same length

Explanation: CICS has vetoed the insertion of aTemporary Storage (TS) entry into the runtime databasebecause the queue name length is different from thelength of its remote name. The names must be of thesame length.

System action: The TS queue entry is not added to theruntime database.

User response: Retry with the TS queue’s name andits RemoteName attribute having the same length.

Destination:

console.msg

ERZ023027W Temporary Storage (TS):Non-recoverable queue ’resourceName’not restored following abnormaltermination of a region

Explanation: CICS has vetoed the addition of theTemporary Storage (TS) entry ’resourceName’ into theruntime database because non-recoverable queues arenot restored on region startup following an abnormaltermination.

ERZ023022E • ERZ023027W


System action: The entry ’resourceName’ is not addedto the runtime database.

User response: None

Destination:

console.msg

ERZ023028I Temporary Storage queues have beenprocessed!

Explanation: CICS startup processing of temporarystorage queues has now finished.

System action: None

User response: None

Destination:

console.msg

ERZ023029E Abnormal termination U2329:Temporary Storage (TS) initialization isunable to restore queue ’queueName’

Explanation: CICS cannot insert a runtime databaseentry ’queueName’ during Temporary Storage (TS)restoration of queues from the system log.


User response: Restart the region. If the errorcontinues to occur then COLD start the region.

Destination:

console.msg

ERZ023030E Temporary Storage (TS): Cannot openFile Server ’serverName’, Filename’fileName’, Index ’indexName’

Explanation: CICS was unable to obtain a file handlefor the specified file.


User response: If this message has been producedwhile processing a CICS Temporary Storage API, yourprogram specifies how the IOERR condition is handled.Check that the file server ’serverName’ is running andthat the file name ’fileName’ and index name indexNameare configured on that server.

Destination:

console.msg

ERZ023031E Unsuccessful TS queue recovery -unable to allocate Region Pool memory

Explanation: CICS was unable to restore recoverableTemporary Storage (TS) queues because it was not ableto allocate Region Pool memory.


User response: Refer to any previous messagesindicating why the Region Pool memory was not ableto be allocated. You can increase the size of the RegionPool available by restarting the region and overridingthe MaxRegionPool attribute, with a larger value, onthe command line.

Destination:

console.msg

ERZ023032E Unable to uninstall Temporary StorageQueue ’queueName’ as it is not adefinition template

Explanation: An attempt to uninstall the TemporaryStorage (TS) Queue ’queueName’ failed because it is aderived queue (created by an EXEC CICS WRITEQ TScommand), not a definition template.

System action: The TS Queue remains installed in theregion.

User response: Ensure the correct TS Queue isspecified. To remove a TS Queue from the region usethe EXEC CICS DELETEQ TS command.

Destination:

console.msg

ERZ023033E Unable to uninstall Temporary StorageQueue definition ’queueName’ as there isan underlying queue which containsdata

Explanation: An attempt to uninstall TemporaryStorage (TS) Queue definition ’queueName’ failedbecause a TS Queue containing data exists with thesame name. The definition cannot be removed from theregion until the Queue is deleted.

System action: The TS Queue definition remainsinstalled in the region.

User response: Ensure the correct TS Queue isspecified. Remove the TQ Queue data with the EXECCICS DELETEQ TS command, then retry the uninstallof the definition.

Destination:

console.msg

ERZ023028I • ERZ023033E


ERZ023034E Abnormal termination U2334:Temporary Storage (TS) checkpointbuffer size inconsistency

Explanation: The size of the Temporary Storage (TS)checkpoint buffer, read from the system log, has beenoverwritten. It is the wrong size.


User response: Cold Start the region.

Destination:

console.msg

ERZ023036E Temporary Storage (TS): Unsuccessfulattempt to empty file - Server’serverName’, File ’fileName’

Explanation: CICS was not able to empty the file’fileName’ when trying to open it.


User response: If this message has been producedwhile processing a CICS Temporary Storage API, yourprogram specifies how the IOERR condition is handled.Check that the file server ’serverName’ is running andthat the file name ’fileName’ is configured on thatserver. Refer to any previous messages detailing errorsin opening or emptying the file. You possibly need tomanually resolve in-doubt transactions, and retry thecold start.

Destination:

console.msg

ERZ023038W Temporary Storage (TS): Detectedinconsistency between the checkpointdata and existing data for queue’queueName’

Explanation: During startup, when processing thesystem log CICS attempted to restore the state of queue’queueName’ from checkpoint data. The existing queuedata was found to be inconsistent with that in thesystem log and the queue data was overridden withthat in the system log.


User response: None

Destination:

console.msg

ERZ023040I Temporary Storage (TS): No queuesfound, so no TS queues to be recovered

Explanation: CICS was not able to find anyTemporary Storage (TS) entries defined after startupand system log checkpoint processing, or duringshutdown.

System action: CICS does not know about any TSqueues and therefore does not recover or setuprecovery data for Temporary Storage.

User response: None

Destination:

console.msg

ERZ023041E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) template’templateName’ at address templateAddress:Unknown Status value statusValue

Explanation: CICS Temporary Storage (TS) selfconsistency checking has found a TS queue templatetemplateName whose Status attribute value, statusValue,is invalid.

System action: CICS recovers the inconsistent Statusattribute value to TEMPLATE and continuesself-consistency checking.

User response: Shutdown and restart CICS as soonpossible, because the integrity of the system can nolonger be assured.

Destination:

console.msg

ERZ023042E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue runtimedatabase entry ’queueName’ at addressentryAddress: Unknown Status valuestatusValue

Explanation: CICS Temporary Storage (TS) selfconsistency checking has found a TS queue queueNameruntime database entry whose Status attribute value,statusValue, is invalid.


User response: Restart the CICS region.

Destination:

console.msg

ERZ023034E • ERZ023042E


ERZ023043E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue’queueName’: Pointer actualPointer,recovered to expectedPointer

Explanation: CICS Temporary Storage (TS) selfconsistency checking has found an internal pointer tobe inconsistent with its expected value.

System action: CICS recovers the inconsistent pointerand continues self-consistency checking.

User response: Shutdown and restart CICS as soon aspossible, because the integrity of the system can nolonger be assured.

Destination:

console.msg

ERZ023044E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue’queueName’: Item count actualCount,recovered to expectedCount

Explanation: CICS Temporary Storage (TS) selfconsistency checking has found the main TemporaryStorage queue’s item count inconsistent with thenumber of items in the queue.

System action: CICS recovers the queue’s item countto the number of items in the queue and continuesself-consistency checking.


Destination:

console.msg

ERZ023045E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue’queueName’: Item numberactualItemNumber, recovered toexpectedItemNumber

Explanation: CICS Temporary Storage (TS) selfconsistency checking has found a main TemporaryStorage queue’s item number inconsistent with itsposition in the queue.

System action: CICS recovers the queue’s itemnumber to match its position in the queue andcontinues self-consistency checking.


Destination:

console.msg

ERZ023046E Temporary Storage (TS): Unable to writeto Auxiliary queue ’queueName’

Explanation: CICS detected an unexpected return codefrom CICS file support and was unable to write to theauxiliary queue ’queueName’.

System action: CICS can abnormally terminate thetransaction with code A23F.

User response: Delete the named queue from CICSand abnormally terminate any transactions using thequeue. Refer to any file support messages thatpreceded this message.

Destination:

console.msg

ERZ023047E Temporary Storage (TS): Unable to readAuxiliary queue ’queueName’

Explanation: CICS detected an unexpected return codefrom CICS file support and was unable to read fromthe auxiliary queue ’queueName’.

System action: CICS can abnormally terminate thetransaction with code A23G.

User response: Delete the named queue from CICSand abnormally terminate any transactions using thequeue. Refer to any file support messages thatpreceded this message.

Destination:

console.msg

ERZ023048E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue’queueName’: Auxiliary queue containsMain queue data

Explanation: CICS self-consistency checking has foundan auxiliary Temporary Storage (TS) queue containingmain TS queue data.


User response: Restart the CICS region.

Destination:

console.msg

ERZ023049E Unable to access Temporary Storage (TS)

Explanation: CICS was unable to provide access toauxiliary Temporary Storage (TS) queues. This ispossibly caused by an unexpected response from CICSfile support while trying to open a file for auxiliaryqueues.

ERZ023043E • ERZ023049E


System action: CICS abnormally terminates thetransaction with code A23E.

User response: Refer to the preceding message(s) thatdetail why CICS was unable to access auxiliary TSqueues.

Destination:

console.msg

ERZ023050E Invalid Temporary Storage (TS) Fileserver configuration - Server’serverName’, File ’fileName’, Index’indexName’

Explanation: The File server ’serverName’ configurationfor auxiliary Temporary Storage (TS) file ’fileName’ isnot ″keyed access″ and CICS cannot use it for TSprocessing.

System action: Temporary Storage queues areunavailable until you correct this problem.

User response: Correct the configuration of the File’fileName’ to ″keyed access″.

Destination:

console.msg

ERZ023051E Temporary Storage (TS): Unable todelete Auxiliary queue ’queueName’

Explanation: CICS detected an unexpected return codefrom CICS file support and was unable to delete theauxiliary queue ’queueName’.

System action: CICS can abnormally terminate thetransaction with code A23T.

User response: Abnormally terminate any transactionsusing the queue. Refer to any file support messagesthat preceded this message.

Destination:

console.msg

ERZ023052E CICS self-consistency checking hasdetected an inconsistent TemporaryStorage (TS) SET buffer length ofbufferSize, at address bufferAddress in theTCA at TCAaddress

Explanation: CICS self-consistency checking hasdetected an invalid SET buffer length bufferSize. It issupposed to be zero because there is no SET buffer. TheSET buffer length has been recovered to 0.


User response: Shutdown and restart CICS as soon aspossible. If CICS self-consistency checking continues todetect inconsistencies contact your supportorganization.

Destination:

console.msg

ERZ023053E CICS self-consistency checking hasdetected an inconsistent TemporaryStorage (TS) count of LUW blocksLUWcountu that is different from actualnumber of blocks actualLUWcountu inTCA at TCAaddress

Explanation: CICS self-consistency checking has founda mismatch between maintained count of LUWs andactual number of LUWs.



Destination:

console.msg

ERZ023054E CICS self-consistency checking hasdetected an invalid Temporary Storage(TS) internal address invalidAddress inqueue entry at queueEntryAddress

Explanation: CICS self-consistency checking has foundan invalid address to the Temporary Storage (TS)private management data on queue entry atqueueEntryAddress.



Destination:

console.msg

ERZ023056E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue’queueName’: Unknown queue typequeueType in private data at addressdataAddress

Explanation: CICS self-consistency checking has foundan unknown Temporary Storage (TS) queue type in itsinternal management data.



Destination:

ERZ023050E • ERZ023056E


console.msg

ERZ023057E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue’queueName’: Queue is Indoubt but is notRecoverable in private data at addressdataAddress

Explanation: CICS self-consistency checking has foundan inconsistency in the state of the Temporary Storage(TS) queue ’queueName’. It is not a recoverable queueyet its state is INDOUBT.



Destination:

console.msg

ERZ023058E CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue’queueName’: Unknown queue ActionqueueAction in private data at addressdataAddress

Explanation: CICS self-consistency checking has foundan unknown Temporary Storage (TS) queue actionqueueAction in its internal management data.



Destination:

console.msg

ERZ023061E CICS self-consistency checking hasdetected an invalid Temporary Storage(TS) SET Buffer address bufferAddress inTCA at [TCAaddress]: Recovered it toNULL and SET buffer size to zero

Explanation: CICS self-consistency checking has foundan invalid SET Buffer memory pointer. It is recoveredto NULL and the SET buffer length set to zero.



Destination:

console.msg

ERZ023062E Abnormal Termination U2362: Unable toaccess Auxiliary Temporary Storage (TS)queues

Explanation: CICS was unable to provide access toauxiliary Temporary Storage (TS) queues.


User response: Refer to the preceding message(s) thatdetail why CICS was unable to access auxiliary TSqueues. Restarting the auxiliary TS queue File Server(s)can enable access to TS queues. If the problem persistsit is likely that the configuration of the TS queue FileServer(s) is suspect.

Destination:

console.msg

ERZ023063I CICS has successfully deleted anAuxiliary Temporary Storage (TS) queueby suppressing a deadlock timeout

Explanation: The file server timed out a request toaccess the file which contains Temporary Storage (TS)queues. CICS was able to suppress this error bylogically deleting the queue.

System action: CICS has successfully deleted thequeue. This can result in inefficient use of disk space.

User response: CICS continues normally. If disk spacebecomes short, then cold starting CICS possibly freessome disk space.

Destination:

console.msg

ERZ023064E The Temporary Storage (TS) file’fileName’ on server ’serverName’ has aninvalid definition

Explanation: One of the system files that containtemporary storage queues has an invalid definition.When you configure a file server for a region, CICScreates these files. The definition of these files must bethat which CICS creates. The only SFS attribute whichyou can configure is the maximum number of recordsin the file.

System action: Temporary Storage queues areunavailable until you correct the problem.

User response: Recreate the system file server file thatis in error. You can do this by configuring your fileserver for your region.

Destination:

console.msg

ERZ023057E • ERZ023064E


ERZ023065I CICS has successfully deleted anAuxiliary Temporary Storage (TS) queueby suppressing a communications error

Explanation: CICS received a communications errorfrom the file server when attempting to access the filewhich contains Temporary Storage (TS) queues. CICSwas able to suppress this error by logically deleting thequeue.

System action: CICS has successfully deleted thequeue. This can result in inefficient use of disk space.

User response: CICS continues normally. If disk spacebecomes short, then cold starting CICS possibly freessome disk space.

Destination:

console.msg

ERZ023070E Unable to open file ’fileName’ to performrecovery processing for RecoverableTemporary Storage queues

Explanation: CICS cannot obtain the data needed forrecovery processing of Temporary Storage queues, as itis unable to open the file containing the data.


User response: Examine accompanying messages todetermine why the file cannot be opened. If the file isdamaged, a backup copy of the file can possibly bemade available. If the problem cannot be resolved, acold start is required.

Destination:

console.msg

ERZ023071E Unsuccessful buffer storage allocationfor recovery of Temporary Storagequeues

Explanation: CICS was unable to allocate sufficientstorage from the task private storage pool, whenattempting to recover Temporary Storage during anauto start after a region failure.


User response: Increase the size of the task privatestorage pool by increasing the value for theMaxTaskPrivatePool attribute in the RegionDefinitions, and retry the auto start. Alternatively,perform a cold start.

Destination:

console.msg

ERZ023072E Abnormal Termination U2372: Recoveryof Temporary Storage Queues failed

Explanation: CICS was unable to recover datarequired to provide Temporary Storage queues. Thisdata is stored in the files which contain TemporaryStorage queue records. The region is unable to continuewithout recovery of this data.

System action: Region startup is abnormallyterminated

User response: Examine accompanying messages todetermine the nature of the problem. If the problemcannot be rectified, a cold start is required.

Destination:

console.msg

ERZ023073E Unable to read data from file ’fileName’to recover Temporary Storage queues

Explanation: CICS was unable to obtain data from thefile containing Transient Data recovery information, sois unable to recover Temporary Storage queues.



Destination:

console.msg

ERZ023074I Recovery of Temporary Storage queuesis complete

Explanation: CICS has completed recovery processingfor Temporary Storage queues.

System action: None

User response: None

Destination:

console.msg

ERZ023075E CICS is unable to save recoveryinformation for Temporary Storagequeue ’TSQname’

Explanation: CICS is unable to save information aboutoperations on recoverable Temporary Storage queues attransaction syncpoint. If the transaction were allowedto complete, CICS is possibly unable to recover thequeue after a subsequent failure.

System action: The Logical Unit of Work is rolledback.

User response: Other messages indicate the cause ofthe problem. The recovery information is written to the

ERZ023065I • ERZ023075E


filesystem, so there is possibly a filesystem errorreported before this error.

Destination:

console.msg

ERZ023076E Unable to store recovery information forCICS queues

Explanation: CICS is unable to save information to thefile system to enable recovery of Temporary Storage orTransient Data queues after a system failure.



Destination:

console.msg

ERZ023077E Read of file ’fileName’ for recovery ofTemporary Storage queues failed withtimeout condition

Explanation: A read operation for recovery ofTemporary Storage queues did not complete within thetransaction DeadLockTimeout value. This can becaused by a lock held on the file by an unresolvedtransaction.

System action: The region is abnormally terminatedwith abend code U2372.

User response: Determine the cause of the timeouterror. Use file server administration commands toidentify inflight transactions which are holding locks onthe file, and, if necessary, force the transactions with thetkadmin command, if the file server is SFS, or listindoubt transactions with prompting if the file serveris DB2. Note that if the file server is SFS, these locksare automatically dropped when the time specified bythe IdleTimeout attribute in the SFS Definitions (SSD)has expired; CICS can then be restarted. If the timeoutis not caused by a retained lock, it can possibly besolved by increasing the DeadLockTimeout value forthe Initialization transaction, CAIN, which performs therecovery processing. If the problem cannot be solved, acold start of the region is possibly necessary.

Destination:

console.msg

ERZ023090E Temporary Storage (TS): Unsuccessfulattempt to allocate Region Pool memory

Explanation: CICS was unable to allocate Region Poolmemory during a Temporary Storage (TS) queueoperation.

System action: CICS does not perform the requested

operation, your transaction can abnormally terminate.

User response: Refer to any previous messagesindicating why the Region Pool memory was unable tobe allocated. You can increase the size of the RegionPool available by restarting the region and overridingthe MaxRegionPool attribute, with a larger value, onthe command line.

Destination:

console.msg

ERZ023091E Temporary Storage (TS): Unsuccessfulattempt to allocate Task-Private Storage

Explanation: CICS was unable to allocate Task-PrivateStorage during a Temporary Storage (TS) queueoperation.

System action: CICS does not perform the requestedoperation, your transaction can abnormally terminate.

User response: Refer to any previous messagesindicating why the Task-Private storage was unable tobe allocated. You can reduce the amount ofTask-Private Storage used by your transaction byreducing your use of GETMAIN.

Destination:

console.msg

ERZ023092E Temporary Storage (TS): Unsuccessfulattempt to allocate Task-Shared Poolmemory

Explanation: CICS was unable to allocate Task-SharedPool memory during a Temporary Storage (TS) queueoperation.


User response: Refer to any previous messagesindicating why the Task-Shared Pool memory wasunable to be allocated. You can reduce the amount ofTask-Shared Pool memory used by your transaction byreducing your use of MAIN TS queues.

Destination:

console.msg

ERZ023093E Temporary Storage (TS): Unsuccessfulattempt to register a Logical Unit ofWork (LUW)

Explanation: CICS was unable to register a LogicalUnit of Work (LUW) for your transaction during anoperation on Temporary Storage (TS).


User response: Refer to any previous messages

ERZ023076E • ERZ023093E


indicating why the registration of the LUW did notsucceed.

Destination:

console.msg

ERZ023094W Unsuccessful memory deallocation ofTemporary Storage buffer

Explanation: An error occurred while CICS wasattempting to release a memory buffer used byTemporary Storage.

System action: This message is logged but processingcontinues.

User response: Check the CSMT log or console.msgfile, for associated information. If other messagesindicate that the problem is a software error in CICSthen contact your support organization.

Destination:

CSMT

ERZ023097E Temporary Storage (TS): Auxiliaryqueues currently not available

Explanation: The Temporary Storage (TS) Fileserver(s) is not available, or the file containing the TSqueues cannot be accessed. This can be caused by alock retained on the file by an unresolved transaction.

System action: CICS does not perform the requestedTemporary Storage operation.

User response: Restart the TS queue File server(s), orinvestigate why CICS is unable to access File server,and then retry the operation. Retained locks on the filecan be listed by File server administration commands.

Destination:

console.msg

ERZ023098E Temporary Storage (TS) timed out

Explanation: CICS has timed out a TS queue lock orNOSPACE condition.

System action: CICS does not perform the requestedoperation. CICS abnormally terminates the transactionthat has timed out with code AKCS in order to avoid apotential deadlock situation.

User response: Increase the value of the transaction’sDeadLockTimeout attribute in the TransactionDefinitions (TD) entry or investigate which transactionhas locked the resource or is using the most temporarystorage.

Destination:

console.msg or CSMT

ERZ023099E Abnormal termination A23S:Unsuccessful Temporary Storage (TS)space allocation

Explanation: CICS detected a memory allocation errorduring a TS queue operation.

System action: CICS does not perform the requestedoperation. CICS terminates the transaction with abendcode A23S.

User response: If a single transaction causes CICS togenerate this error on several occasions, the transactionis probably in error. If so, you can use the CICSProblem Determination Guide to solve this problem.Otherwise, look at other messages in the message fileto identify which storage pool is affected, and changethe memory configuration attributes defined in theRegion Definitions (RD) entry.

Destination:

console.msg

ERZ023100E File operation for recoverable TemporaryStorage queue failed as File server hasbeen recycled

Explanation: The connection to the File server forTemporary Storage was temporarily lost. This hascaused the connection to the file to be invalidated. It isrevalidated by CICS on the next request to that file.


User response: Resubmit the transaction. Ifcommunication errors continue, refer to other messagesto try to determine the cause and correct it.

Destination:

console.msg

ERZ023101E Transaction timed out waiting forTemporary Storage file to be opened byanother task

Explanation: The DeadLockTimeout value for thetransaction was exceeded while waiting for anothertransaction to finish opening a file for auxiliaryTemporary Storage queues.

System action: The transaction is abnormallyterminated with code AKCS.

User response: Examine other messages for a problemin opening the file. Resubmit the transaction. If thisproblem persists when there is no problem with thefile, it can be solved by increasing the value of theDeadLockTimeout attribute in the TransactionDefinition.

Destination:

console.msg

ERZ023094W • ERZ023101E


ERZ023102E CICS is unable to save information forSTART requests in the filesystem

Explanation: During normal shutdown processing,CICS saves information for unexpired START requestsin the filesystem, for use when the region is restarted.This message indicates that CICS was unable to storethat information for START requests issued without thePROTECT option, so these requests were unable to berecreated on a normal region restart.


User response: Examine other messages to determinethe cause of the error and correct it. Restart the regionand resubmit the START requests if required.

Destination:

console.msg

ERZ023103E CICS is unable to restore informationfor START requests as the file fornon-recoverable Temporary Storage isunavailable

Explanation: During auto restart of the CICS regionafter a normal shutdown, CICS retrieves informationfor START requests issued without the PROTECToption from the filesystem. This message indicates thatCICS was unable to retrieve the information as therequired file is not available. The file that contains theinformation is the file used for non-recoverableTemporary Storage Queues, specified by theNonRecTSQFile attribute in the Region Definitions.

System action: The region restart is terminated;restoration of the information is retried on a subsequentauto start of the region.

User response: Examine accompanying message todetermine why the file is not available. Make the fileavailable and auto start the region.

Destination:

console.msg

ERZ023104E CICS is unable to restore informationfor START requests from TemporaryStorage Queue ’queueName’

Explanation: During auto restart of the CICS regionafter a normal shutdown, CICS retrieves informationfor START requests issued without the PROTECToption from the filesystem. This message indicates thatCICS was unable to retrieve the information because ofan error.

System action: The region restart continues.Unexpired START requests which were stored in thenamed Temporary Storage Queue are lost.

User response: Examine other messages to determinethe cause of the error and correct it if possible.

Resubmit the START requests if required.

Destination:

console.msg

ERZ023105W During a cold start, CICS is unable toopen and empty the files that storeTemporary Storage Queue data

Explanation: During a cold start of the CICS region,the files that store Temporary Storage Queue data inthe filesystem need to be emptied to keep the CICS andfilesystem information consistent. This messageindicates that there has been some error in opening andemptying these files.

System action: The region start continues. Furtherattempts are made by CICS to empty the files ifTemporary Storage queues are accessed.

User response: Examine other messages to determinethe cause of the error and correct it if possible. If adatabase is being used as the filesystem for TemporaryStorage queues, and CICS attempts to empty the filesduring a user task that subsequently abends, the CICSand filesystem data is inconsistent. To rectify such asituation, the problem that is preventing the files frombeing opened and emptied must first be solved, thenthe region can either be cold started, or be shut downwith an immediate shutdown, and auto started to forcerecovery of the queues.

Destination:

console.msg

ERZ023106E Abnormal termination ASRA. Attemptto read into Region Pool memory.

Explanation: The transaction has attempted a READQTS operation using an INTO buffer which specifies anaddress in Region Pool memory.

System action: CICS terminates the transaction withabend code ASRA.

User response: Check that the address specified in theINTO option refers to memory accessible by theprogram and that the LENGTH does not overrun theend of that memory.

Destination:

CSMT

ERZ023107W CICS self-consistency checking hasdetected an inconsistency in theTemporary Storage (TS) queue’queueName’: Last accessed time is greaterthan the current time.

Explanation: CICS Temporary Storage (TS) selfconsistency checking has found that the queue’s lastaccess time occured in the future.

ERZ023102E • ERZ023107W


System action: CICS sets the last accessed time to thecurrent time and continues self-consistency checking.


Destination:

console.msg





Destination:

console

ERZ024005E Abnormal termination A245. Unable toopen log ’logFileName’, reason errorString.

Explanation: CICS is unable to open the specified logfile.

System action: CICS terminates the Application Serverwith abend code A245. Other Application Servers arenot affected and the region remains available.

User response: Use information in ’errorString’ todetermine the cause of the error. Check the permissionsfor the CICS region log directory to ensure that useridcics has both read and write access. Also, check thatthere are no rogue Application Servers persisting froma previous invocation of the region. If there are, killthem.

Destination:

console.msg

ERZ024006E Abnormal termination U2406. Unable toguarantee recovery of log ’logFileName’,reason errorString.

Explanation: CICS is unable to write a restart recordto log file ’logFileName’. If the region continues, thisproblem can possibly prevent CICS recovery algorithmsfrom working correctly.


User response: Verify that the CICS region logdirectory exists and that sufficient storage has been

allocated to it. If the problem persists cold start CICS.

Destination:

console.msg

ERZ024007E Abnormal termination U2407. Unable torecover CICS resources from log’logFileName’.

Explanation:

There are the following reasons for this message:

v CICS has read an empty restart record for the masterlog file. This occurs if, for example, CICS is autostarted following the deletion of the region masterlog.

v CICS is unable to determine the position in log file’logFileName’ at which to begin recovery processing.A restart position is always set by CICS when itcreates a log file so this problem suggests amalfunction in CICS logging.

v CICS is unable to read a log record at the restartposition in log ’logFileName’. This error suggests thatthe restart position for log file ’logFileName’ has beenoverwritten with invalid data.

v CICS has read a record at the restart position in thelog file but it was the wrong size or containedinvalid data.


User response: Check that the log files exist in theCICS region log directory varDir/cics_regions/regionName/log. There is one master log file for theregion and a log file for each of the Application Serverswhich were active when the region was last stopped.The log files are named CICS_ML_regionName.controlfor the master log andCICS_AS_applicationServerId.control for theApplication Server logs. If any of the log files are notpresent, then, if the filesystem hosting the CICS regionlog directory is configured to provide mirroring, switchto the mirrored version containing the log files andauto start CICS. Otherwise you need to cold start yourCICS region.

Destination:

console.msg

ERZ024009E Abnormal termination U2409. ErrorerrorNumber reading log file’logFileName’.

Explanation: An attempt to read the log file’logFileName’ was unsuccessful.


User response: If the filesystem hosting the CICSregion log directory is configured to provide mirroring

ERZ023108E • ERZ024009E


switch to the mirrored version containing log’logFileName’ and auto start CICS. Otherwise cold startCICS.

Destination:

console.msg

ERZ024011E Abnormal termination U2411.Unexpected recovery problem readingfrom log ’logFileName’.

Explanation: CICS is attempting to read a start ofcheckpoint record from the specified log but hasretrieved some other record instead.


User response: If the filesystem hosting the CICSregion log directory is configured to provide mirroringswitch to the mirrored version containing log’logFileName’ and auto start CICS. Otherwise cold startCICS.

Destination:

console.msg

ERZ024013E Abnormal termination U2413.Unexpected problem recoveringresources from log file ’logFileName’,reason errorString.

Explanation: This can possibly be due to CICS beingunable to open a log ″cursor″ in log ’logFileName’ forreason ’errorString’. This operation attempts to establisha context for subsequent reads by selecting a subset ofthe log records to be retrieved, a position in the log anda direction. Alternatively, CICS is possibly unable tochange the position of a log cursor in log ’logFileName’for reason ’errorString’. Both of these problems preventthe retrieval from the log of records required to recoverCICS resources correctly.


User response: This message indicates an unexpectedproblem with the log component. If the filesystemhosting the CICS region log directory is configured toprovide mirroring switch to the mirrored versioncontaining log ’logFileName’ and auto start If theproblem persists contact your support organization.

Destination:

console.msg

ERZ024016E Abnormal termination U2416. The logcomponent has an internal problem andhas initiated an immediate terminationof CICS (Request=’logRequest’).

Explanation: The log component has an internal

problem from which it is unable to recover. It hasrequested CICS to terminate the region immediately.


User response: Cold start CICS. If the problempersists or occurs frequently, contact your supportorganization.

Destination:

console.msg

ERZ024019E Abnormal termination U2419. Unable torecover CICS resources - missingcheckpoint data for module moduleId.

Explanation: This message indicates an unexpectedproblem with the CICS log component. CICS hasrecovered the last successful checkpoint written to thelog, but is unable to find the checkpoint data requiredby module moduleId.


User response: If the filesystem hosting the CICSregion log directory is configured to provide mirroringswitch to the mirrored version containing the CICSregion log files and auto start CICS. Otherwise coldstart CICS. If the problem persists, contact your supportorganization.

Destination:

console.msg

ERZ024020W Unable to close log ’logFileName’ duringprocess exit, reason errorString

Explanation: CICS is unable to close log ’logFileName’during Application Server termination (or during logdaemon exit).


User response: You can ignore this message since thelog files are closed by the operating system when theprocesses terminate. However, it possibly indicates aproblem with the underlying file system being used bythe log component. If the problem persists, contactyour support organization.

Destination:

console.msg

ERZ024021W CICS self consistency checking:checkpoint counter value ofcheckpointCounteru exceedsCheckpointInterval valuecheckpointIntervalu in Region Record.Reconciled - counter set toCheckpointInterval.

ERZ024011E • ERZ024021W


Explanation: CICS has detected that the checkpointcounter is out of range. The counter has been reset tothe checkpoint interval specified for the region by theCheckpointInterval attribute in the Region Definitions.


User response: None. If this problem happensfrequently, contact your support organization.

Destination:

console.msg

ERZ024022E CICS self consistency checking:unexpected signature ’signatureFound’detected in a memory structure ataddress structureAddress. (Expectedsignature is ’expectedSignature’.)

Explanation: CICS has detected a signature fieldcontaining invalid data in the Region Pool storage. Thisproblem is not likely to be caused by either user actionor user transactions.

System action: CICS is abnormally terminated.Further messages are produced by CICS.

User response: Refer to the abnormal terminationmessage produced by CICS after this message.

Destination:

console.msg

ERZ024023W CICS self consistency checking: count ofnumber of registered modules has valuemoduleCountu which exceeds expectedmaximum of RegMaxu. Reconciled -count set to maximum.

Explanation: CICS has detected that the count ofregistered modules for journaling has exceeded itsmaximum value.


User response: None. If this problem happensfrequently, contact your support organization.

Destination:

console.msg

ERZ024024E CICS self consistency checking:unexpected module identifier moduleIdencountered at element moduleAddressuin the table of modules registered forjournaling

Explanation: CICS has detected an unexpectedmodule identifier in its table of modules registered forjournaling. This table is allocated out of the RegionPool so this is not a problem likely to be caused byuser action or user transactions.

System action: CICS is abnormally terminated.

Further messages are produced by CICS.


Destination:

console.msg

ERZ024025E CICS self consistency checking: counterof Application Server logs in use hasvalue ’inUseCounteru’ which differs fromthe expected count of’numberLogsFoundu’.

Explanation: CICS has detected a mismatch between acounter and the actual number of objects existing. Asthese objects are allocated out of the Region Pool, it isnot likely that this problem is caused by user action oruser transactions.

System action: CICS is abnormally terminated.Further messages are produced by CICS.


Destination:

console.msg

ERZ024030E Abnormal termination U2430. Unable tofind log needed for recovery.

Explanation: CICS is unable to find a log for aApplication Server that it has started. The list of logsavailable for use in recovery processing is maintainedin region memory and is retrieved from the CICSmaster log during initial recovery processing. Thismessage is produced when the CICS ApplicationManager (cicsam process) attempts to read from a lognot present in the list. This does not happen unless aninternal problem exists or unless Region Pool memoryhas been overwritten.


User response: Auto start CICS. If the problempersists report it to your support organization.Alternatively, cold start CICS.

Destination:

console.msg

ERZ024050E Abnormal termination U2450. Unable toopen master log file ’logFileName’, reasonerrorString.

Explanation: CICS detected an unrecoverable errorwhen attempting to open the master log file’logFileName’.


ERZ024022E • ERZ024050E


User response: Check using the file system commandsthat the master log files exist in the log file directory.The master log consists of a control file,CICS_ML_regionName.control and one or more extentfiles, CICS_ML_regionName.extent.extentNumber. Ifthey exist, verify that there are no rogue processes (cics,cicsld, cicsrm) persisting from a previous invocation ofthe region. If there are any, kill them. If the problempersists contact your support organization.

Destination:

console.msg

ERZ024051E Abnormal termination U2451. Unable towrite to log ’logFileName’, reasonerrorString.

Explanation: CICS is unable to write to log file’logFileName’.


User response: Use the information in ’errorString’ todetermine what caused the error. If it indicates thatthere is no space available, allocate additional space tothe CICS region log directory containing ’logFileName’.Auto start CICS to continue. For other error conditions,if the filesystem hosting the CICS region log directoryis configured to provide mirroring switch to themirrored version containing log ’logFileName’ and autostart CICS. Otherwise cold start CICS.

Destination:

console.msg

ERZ024052E NOSPACE condition has arisen on userjournal journalId

Explanation: CICS is unable to write to user journaljournalId because there is insufficient space available inthe file system where it resides. The current DiskA orDiskB attribute in the Journal Definitions (JD) for thejournal determines the pathname of the file used bythat journal.

System action: CICS suspends the transaction for awhile and then retries the write operation.

User response: Either wait for space to becomeavailable, or initiate action to free some journal storagein the same file system. The latter can involve using theEXEC CICS SET JOURNALNUM CLOSE or ADVANCEcommands to close existing journals to CICS so thatthey can be moved offline to free some space in theassociated file systems.

Destination:

console.msg

ERZ024053I NOSPACE condition resolved on userjournal fileName

Explanation: CICS detected a NOSPACE conditionwhen writing to the user journal fileName. Thecondition has now been corrected.


User response: None

Destination:

console.msg

ERZ024054E Abnormal termination U2454.Unsuccessful memory allocation forreading the system log, reasonerrorNumber.

Explanation: CICS is attempting to obtain memoryfrom the Region Pool for reading the system log.Insufficient memory is available.

System action: CICS recovery processing cannotcontinue. CICS terminates the region with abend codeU2454.

User response: Auto start CICS with an increasedRegion Pool size by overriding the MaxRegionPoolattribute in the Region Definition on the command line.Do the same for the permanent database by usingcicsupdate.

Destination:

console.msg

ERZ024055E Abnormal termination U2455.Unsuccessful memory allocation for logarchive control information, reasonerrorNumber.

Explanation: CICS is attempting to obtain memory forlog archive control information from the Region Pool.Insufficient memory is available.


User response: Auto start CICS with an increasedRegion Pool size by overriding the MaxRegionPoolattribute in the Region Definition on the command line.Do the same for the permanent database by usingcicsupdate.

Destination:

console.msg

ERZ024056E Abnormal termination U2456.Unsuccessful memory allocation forCICScheckpoint data, reasonerrorNumber.

Explanation: CICS is attempting to obtain Task Shared

ERZ024051E • ERZ024056E


Pool memory for a start of checkpoint buffer to containlog management data. Insufficient memory is available.


User response: Auto start CICS with an increasedTask Shared Pool size by overriding the MaxTSHPoolattribute in the Region Definition on the command line.Do the same for the permanent database by usingcicsupdate.

Destination:

console.msg

ERZ024057E Abnormal termination U2457. Unable towrite log data to permanent storage,reason errorString.

Explanation: CICS writes some log data into bufferedstorage to improve performance. It also attempts towrite log data direct to permanent storage (storagewhich survives a system crash) forcing all earlierbuffered data to become permanent too. This messageis produced when the log component is unable to makedata permanent when requested to do so by CICS.


User response: Refer to the file system documentationfor information concerning the error code. If theproblem persists either cold start CICS or contact yoursupport organization.

Destination:

console.msg

ERZ024058W Unsuccessful checkpoint for CICSmodule moduleId, reason errorNumber

Explanation: CICS was unable to collect checkpointinformation from the specified internal module.

System action: CICS terminates the checkpointoperation and continues processing. The attempt tocheckpoint is unsuccessful, so it is not possible todiscard log records which are otherwise summarizedby the checkpoint data. In consequence, log filescontinue to grow and this affects both Log Serviceperformance and CICS recovery time. It also increasesthe use of Log Service resources which becomes aproblem if there are insufficient resources available.

User response: Restart CICS when convenient, usingeither auto start or cold start. If the problem persistscontact your support organization.

Destination:

console.msg

ERZ024060E Abnormal termination U2460. Recoveryprocessing is incomplete as CICS isunable to open Application Server log’logFileName’, reason errorString.

Explanation:

CICS is unable to open Application Server log file’logFileName’ during recovery processing. The CICSApplication Manager obtains the list of ApplicationServer log files needing recovery from the CICS masterlog, and stores this list in memory obtained from theRegion Pool. Possible causes of this problem thereforeinclude:

v Region Pool memory has been overwritten withinvalid data (either before the list is written to theLog Service, or after the list has been retrieved fromthe Log Service)

v Log Service data has been overwritten with invaliddata

v Other users of the Log Service have deleted the logfile

v The Log Service has been cold started since yourregion was started

v Another process has the log file opened already.

It is unlikely that misbehaving user transactions cancause this problem.

System action: CICS stops further recovery processingand terminates the region with abend code U2460.

User response: Refer to the Log Servicedocumentation for information concerning the log errorcode. If the log error code indicates that the file isalready open, verify that there are no rogue ApplicationServers persisting from a previous invocation of theregion. If there are, kill them and restart CICS. If thelog error code indicates that the file does not existverify that no other users have deleted the log file. Ifso, cold start CICS. For other log error codes either coldstart CICS or, if the file system being used by the logdirectory is being mirrored, switch to the mirroredversion and auto start CICS. If the problem persistscontact your support organization.

Destination:

console.msg

ERZ024061W Unable to close log ’logFileName’, ReasonerrorString

Explanation: CICS was unable to close log’logFileName’. The log file handle obtained from the LogService by CICS for operations on this file remainsvalid. This means that unnecessary Log Serviceresources are retained by the region and this canpotentially degrade performance.


User response: If this problem is happening

ERZ024057E • ERZ024061W


frequently and if you are concerned that there is someperformance degradation, auto start CICS to free theexcess resources.

Destination:

console.msg

ERZ024062E Abnormal termination A24S.Unsuccessful memory allocation for logrecord.

Explanation: CICS is attempting to obtain memoryfrom the Region Pool for a log record. Insufficientmemory is available.

System action: The CICS Application Server whichfailed to obtain memory is terminated with abend codeA24S as it is unable to make the log record permanent.

User response: When convenient to do so, auto startCICS with an increased Region Pool size by overridingthe MaxRegionPool attribute in the Region Definitionon the command line. Do the same for the permanentdatabase (using cicsupdate).

Destination:

console.msg

ERZ024063E Abnormal termination U2463.Unsuccessful memory allocation for logcontrol information, reason errorNumber.

Explanation: CICS is attempting to obtain memoryfrom the Region Pool for a log control list element.Insufficient memory is available.


User response: Auto start CICS with an increasedRegion Pool size by overriding the MaxRegionPoolattribute in the Region Definition on the command line.Do the same for the permanent database (usingcicsupdate).

Destination:

console.msg

ERZ024065W Unable to discard obsolete records fromlog file ’logFileName’, reason errorString

Explanation: CICS is unable to set the archive tail forlog ’logFileName’. This operation normally causes logrecords that are no longer needed by CICS to bediscarded from the log. As the operation has beenunsuccessful, the log component is likely to be usingmore disk space than it otherwise needs. This canadversely affect performance if the problem occursfrequently or persists for some time on a heavily usedlog.


User response: No immediate action is necessary, butthis condition

Destination:

console.msg

ERZ024066E Abnormal termination U2498.Transaction could not write to systemlog, reason errorString.

Explanation: CICS detected an unrecoverable errorwhile attempting to write to the system log.


User response: Look up the error code in the LogService documentation. If it indicates that there is nospace available, use Log Administration commands toadd additional space to the Log Service volume wherethe system log resides. Auto start CICS to continue. Forother error conditions, if your Log Service is configuredto provide mirrored volumes, switch to the mirroredvolume containing the CICS master log (defined byattribute CLogName in RD) and auto start CICS. (Referto the Log Service documentation for information abouthow to do this.) Otherwise, terminate the Log Serviceand restart it in recover mode before performing anauto start of CICS (refer to the Log Servicedocumentation for information about how to do this),or cold start the Log Service and then CICS. If theproblem persists contact your support organization.

Destination:

console.msg

ERZ024067E Abnormal termination U2467. Cannotinitialize server log, reason errorString.

Explanation: CICS was unable to initialize the logwhile attempting to start a CICS process. This isusually because the access permissions on the logdirectory /var/cics_regions/<region-name>/log or onthe files in the directory are insufficient.


User response: Check (and correct) the permissions onthe log directory and/or files. If the problem persists,call your support organization.

Destination:

console.msg

ERZ024070E Abnormal termination U2470.Unsuccessful memory allocation for userjournal control information, reasonerrorNumber.

Explanation: CICS is attempting to open a userjournal defined with InitialOpenFlag=yes in the

ERZ024062E • ERZ024070E


Journal Definitions (JD). It is unable to create and inserta TDQ run time database entry corresponding to theuser journal being opened because there is insufficientmemory in the Region Pool.


User response: Auto start CICS with an increasedRegion Pool size by overriding the MaxRegionPoolattribute in the Region Definition on the command line.Do the same for the permanent database usingcicsupdate.

Destination:

console.msg

ERZ024071E Invalid attempt to change definition ofjournal ’journalId’ in the run timedatabase

Explanation: CICS has vetoed an attempt to delete oralter the definition of a journal in the run time databasebecause the journal is still in use. Similarly,amendments are vetoed if the current destination isaltered, for the same reason. Note also that the ’openstatus’ of a journal can be altered via the EXEC CICSSET JOURNALNUM command only.

System action: None

User response: Retry the cicsdelete or cicsupdaterequest after closing the journal or changing the currentdestination (EXEC CICS SET JOURNALNUMcommand) as appropriate.

Destination:

CSMT

ERZ024072E Abnormal termination A24M.Unsuccessful memory allocation whileopening journal ’journalId’.

Explanation: CICS failed to obtain memory whileattempting to open user journal ’journalId’. CICS isunable to create and insert a TDQ run time databaseentry corresponding to the user journal because there isinsufficient memory in the Region Pool.

System action: The transaction is terminated withabend code A24M.

User response: Retry the request later. If this problemhappens frequently, increase the size of the Region Poolby overriding the MaxRegionPool attribute in theRegion Definition on the command line. Do the samefor the permanent database using cicsupdate.

Destination:

CSMT

ERZ024074E Abnormal termination A24F. Unable tosave changes made to the run timedatabase record of journal ’journalKey’,reason errorNumber.

Explanation: CICS is attempting to save changes madeto the specified journal’s run time database record, butis unable to do so.

System action: CICS terminates the transaction withabend code A24F.

User response: If the CICS error code indicatesinsufficient memory, retry when more memory isavailable. If this problem happens frequently, increasethe size of the Region Pool by overriding theMaxRegionPool attribute in the Region Definition onthe command line. Do the same for the permanentdatabase using cicsupdate.

Destination:

CSMT

ERZ024075E Abnormal termination U2475. Unable towrite to crucial user journal ’journalId’,reason errorNumberd.

Explanation: CICS is attempting to write to userjournal ’journalId’ which is designated as a ″crucial″journal. CICS is unable to write to this journal. Possiblecauses include deadlock timeout, insufficient space onthe relevant file system and bad destination pathspecified in the Journal Definition (JD).


User response: Check that the destination paths(attributes DiskA and DiskB) specified in the JD bothexist. If not, create any missing directories or correctthe destination paths as appropriate and restart yourregion. Also check the permissions on all directories inthese paths to ensure that userid cics has write access.For the specified journal, check that there is spaceavailable in the file system containing the currentdestination of that journal.

Destination:

console.msg

ERZ024076E Abnormal termination A248. Unable towrite to user journal ’journalId’, reasonerrorNumber.

Explanation: CICS is attempting to write tonon-crucial user journal ’journalId’, but is unable to doso. Possible causes include deadlock timeout,insufficient space on the relevant file system and baddestination path specified in the Journal Definition (JD).

System action: The transaction is terminated withabend code A248.

ERZ024071E • ERZ024076E


User response: Check that the destination paths(attributes DiskA and DiskB) specified in the JD bothexist. If not, create any missing directories or correctthe destination paths as appropriate (using RDOcommands such as cicsget, cicsdelete, cicsadd andcicsupdate to change both the run time and permanentdatabase definitions). Also check the permissions on alldirectories in these paths to ensure that userid cics haswrite access. For the specified journal, check that thereis space available in the file system containing thecurrent destination of the journal.

Destination:

CSMT

ERZ024080I Application Manager has finished withmaster log file

Explanation: The CICS Application Manager hascompleted processing the log files.

System action: None

User response: None

Destination:

console.msg

ERZ024081I CICS log daemon ready

Explanation: The CICS log daemon process is nolonger waiting for access to the master log file. It isnow ready to perform logging.

System action: None

User response: None

Destination:

console.msg

ERZ024083I Log daemon is waiting for access tomaster log file

Explanation: The CICS log daemon process is waitingfor access to the master log file. Only one process canopen the file at a time, and the Recovery Managerprocess must finish with the file before it can beopened by the log daemon.

System action: None

User response: None

Destination:

console.msg

ERZ024085I Application Manager is determiningrecovery requirements

Explanation: The CICS Application Manager isstarting to process the master log file. During this workit restores the state of CICS resources from the last

checkpoint written to this log file and it builds up a listof Application Server log files which need furtherprocessing.

System action: None

User response: None

Destination:

console.msg

ERZ024086I Application Manager has determinedrecovery requirements

Explanation: The CICS Application Manager processhas finished processing the master log file and now hasa complete list of further log files to be processed.

System action: None

User response: None

Destination:

console.msg

ERZ024087I Application Manager is opening logfiles used previously

Explanation: The CICS Application Manager isopening those Application Server log files which werepreviously in use by CICS.

System action: None

User response: None

Destination:

console.msg

ERZ024088I Application Server is playing back workthat took place after the last checkpoint

Explanation: The CICS Application Server is restoringthe state of CICS resources which changed after the lastcheckpoint was written.

System action: None

User response: None

Destination:

console.msg

ERZ024089I Checkpointing started

Explanation: CICS is commencing a checkpointdetailing the state of all recoverable resources. It iswritten to the master log file.

System action: None

User response: None

Destination:

console.msg

ERZ024080I • ERZ024089I


ERZ024090I Checkpointing completed

Explanation: CICS has completed a checkpoint.

System action: None

User response: None

Destination:

console.msg

ERZ024097E Abnormal termination U2497. Exception’exceptionName’ caught.

Explanation: CICS detected an unexpected fatalexception.


User response: Restart your region. If the problempersists investigate whether any particular transactionsappear to cause this problem and contact your supportorganization.

Destination:

console.msg

ERZ024098E Abnormal termination AKCS; write tojournal journalId has timed out

Explanation: CICS has timed out while attempting towrite to user journal ’journalId’.

System action: CICS does not perform the requestedoperation. CICS terminates the transaction with abendcode AKCS in order to avoid a potential deadlocksituation.

User response: Increase the value of theDeadLockTimeout attribute in the TransactionDefinitions (TD) entry and investigate whichtransactions have taken the most space in the filesystem being used by user journals. If any transactionsare found which are using unwarranted amounts ofuser journal storage or extrapartition transient dataqueue storage, disable the relevant journal or transientdata queue and archive and delete the correspondingfile. You possibly also need to purge the tasks runningany such transactions.

Destination:

CSMT

ERZ024100E Cannot advance (switch destination filesfor) an unopened journal ’journalId’

Explanation: CICS received a request to switch filesfor a journal that is not opened. The journal must be inthe open state before it can be advanced. The purposeof advancing a journal is to allow the journal contentsto be moved offline for processing by user programs. Ifthe journal is in a closed state the relevant journal file

is already available to user programs without needingto advance the journal first.

System action: CICS does not perform the requestedoperation. It returns ILLOGIC.

User response: None

Destination:

CSMT

ERZ024101W Journal ’journalId’ cannot be closedbecause it is not open

Explanation: CICS received a request to close ajournal that is not open. The journal must be in theopen state before it can be closed.


User response: None

Destination:

CSMT

ERZ024102W Journal ’journalId’ cannot be openedbecause it is not closed

Explanation: CICS received a request to open ajournal that is not closed. The journal must be in theclosed state before it can be opened.


User response: None

Destination:

CSMT

ERZ024103E Cannot delete Transient Data (TD)Queue ’TDQname’ for Journal ’journalId’,reason errorNumber

Explanation: CICS was unable to delete the TD Queuededicated to journal ’journalId’. This message usuallymeans that the TD Queue is in use (for example, awrite request is possibly in progress) and so cannot bedeleted.

System action: CICS does not perform the requestedoperation. It returns IOERR.

User response: Check that the error code has thismeaning and if so retry until you succeed.

Destination:

CSMT

ERZ024090I • ERZ024103E


ERZ024104E Cannot obtain exclusive access toTransient Data (TD) Queue ’TDQname’dedicated to journal ’journalId’, reasonerrorNumber

Explanation: CICS was unable to obtain exclusiveaccess to the TD Queue underlying journal ’journalId’.


User response: If the reason for this error isinsufficient memory, increase the Region Pool size byoverriding the MaxRegionPool attribute in the RegionDefinition on the command line. Do the same for thepermanent database using cicsupdate and retry. If theproblem persists contact your support organization.

Destination:

CSMT

ERZ024105E Cannot save changes to run timedatabase entry for Transient Data (TD)Queue ’TDQname’, Journal ’journalId’,reason errorNumber

Explanation: CICS was unable to save the updatedrun time database record of TD Queue ’TDQname’underlying journal ’journalId’.


User response: If the reason for this error isinsufficient memory, increase the Region Pool size byoverriding the MaxRegionPool attribute in the RegionDefinition on the command line. Do the same for thepermanent database using cicsupdate and retry. If theproblem persists contact your support organization.

Destination:

CSMT

ERZ024106E Journal ’journalId’ cannot be openedbecause the Transient Data (TD) Queue’TDQname’ already exists

Explanation: CICS was unable to open journal’journalId’ because the TD Queue for this journal(’TDQname’) already exists. In order to open a journal,CICS expects to create a run time database record forthe TD Queue to be used exclusively by the journal.CICS reserves TD Queue names CJ01-CJ99 for thispurpose.

System action: CICS does not open the journal. Thejournal stays closed. CICS returns INVREQ.

User response: If the presence of the existing TDQ isinadvertent, use RDO commands to remove or renamethe TDQ in the run time database. Retry the journalcommand.

Destination:

CSMT

ERZ024107W Run-time database definition of journal’journalId’ not installed because there isan invalid attribute combination in thedatabase entry

Explanation:

CICS has detected either

v that both destinations (DiskA, DiskB attributes) ofjournal ’journalId’ are the same (a journal must haveDiskA different from DiskB so that the journaldestination can be switched when required), or

v that both destination states (DiskAStatus,DiskBStatus attributes) are the same (one journalmust be current and the other one must be ready).

System action: CICS continues, but does not insert thejournal definition into the run time database.

User response: Change the destinations (databaseattributes DiskA and DiskB) associated with journal’journalId’ so that they are different. Ensure that all thenecessary directories exist and that userid cics haswrite permission to each. Check also that attributesDiskAStatus and DiskBStatus are different. Use RDOcommands to effect any run time database changesrequired. For example use cicsget, cicsdelete andcicsadd.

Destination:

CSMT

ERZ024108E Cannot change destination of openjournal ’journalId’

Explanation: CICS has rejected a request to change thedestination of journal ’journalId’ because it is open.

System action: CICS does not perform the requestedaction on the journal. It returns INVREQ and continues.

User response: Close the journal and retry.

Destination:

CSMT

ERZ024109W Run-time database definition of journal’journalId’ was not installed becausepathname ’pathName’ specified forattribute ’attributeName’ in databaseentry cannot be accessed

Explanation: CICS has detected that a pathnamespecified in the database entry (DiskA or DiskBattribute) for journal ’journalId’ is not accessible byCICS.

System action: CICS continues, but does not insert thejournal definition for journal ’journalId’ into the runtime database.

ERZ024104E • ERZ024109W


User response: Check the DiskA and DiskB attributesof the specified journal. These values cannot be emptystrings but must be pathnames writable by CICS.Check that the directories exist and that user cics hasread, write and execute permissions for each. Correctany insufficient permissions on the pathnamesspecified. Then re-install the run time database entry,for example using cicsget, cicsdelete and cicsadd.

Destination:

CSMT

ERZ024110E Journal ’journalId’ cannot be deletedbecause it is not closed

Explanation: CICS received a request to delete ajournal that is open. The journal must be closed beforeit can be deleted.

System action: CICS does not perform the requestedoperation.

User response: Close the journal and retry.

Destination:

CSMT

ERZ024111I ’numberOfJournals’ user journal(s)successfully opened: ’listOfJournals’

Explanation: CICS has finished user journalinitialization. The names of the journals marked to beopened at startup and successfully opened aredisplayed.

System action: None

User response: None

Destination:

console.msg

ERZ024112E Unable to save changes made to the runtime database record of journal’journalKey’

Explanation: CICS is attempting to save changes madeto the specified journal’s run time database record, butis unable to do so.

System action: CICS continues, but does not performthe requested operation on the user journal.

User response: If the CICS error code indicatesinsufficient memory, retry when more memory isavailable. If this problem happens frequently, increasethe size of the Region Pool by overriding theMaxRegionPool attribute in the Region Definition onthe command line. Do the same for the permanentdatabase using cicsupdate.

Destination:

CSMT

ERZ024113E Journal data corrupted

Explanation: The self consistency checking in CICSdetected that the journal fields were not correct.


User response: Refer to the abnormal terminationmessage produced by CICS after this message. Retrythe operation. If the problem persists, contact yoursupport organization.

Destination:

console.msg

ERZ024114W No user journals opened

Explanation: CICS has finished user journalinitialization. There are no journals marked to beopened at startup which were successfully opened.

System action: None

User response: None

Destination:

console.msg

ERZ024115W Cannot access master log as log daemonprocess has terminated

Explanation: CICS has made an attempt to access themaster log during shutdown after the log daemonprocess cicsld has terminated.

System action: Shutdown of the CICS regioncontinues.

User response: None

Destination:

console.msg

ERZ024116W The log directory is running short ofstorage

Explanation: CICS has detected that the log directoryis running low on available storage because there isinsufficient space available in the file system where itresides. The pathname of the log directory isvarDir/cics_regions/regionName/log.

System action: CICS continues to monitor thiscondition and continues to issue this messageperiodically while the shortage exists. If the logdirectory fills completely, CICS terminates the regionwith abend code U2451 or U2498.

User response: Increase the storage available to thefile system.

Destination:

console.msg

ERZ024110E • ERZ024116W


ERZ024117W Unable to free internal structures for log’logFileName’ following abnormaltermination of Application Server,reason errorString

Explanation: CICS is unable to free up the internalcontrol blocks for log ’logFileName’ following theabnormal termination of an Application Server.


User response: You can ignore this message since thelog control blocks are deallocated when CICS is nextstopped. However, it possibly indicates an internalproblem with the log component, and, if the problempersists, contact your support organization.

Destination:

console.msg

ERZ024118I Application Server serverId is playingback work that took place after the lastcheckpoint

Explanation: The CICS Application Server is restoringthe state of CICS resources which changed after the lastcheckpoint was written.

System action: None

User response: None

Destination:

console

ERZ025001E Unsuccessful open of file:’serverName’/’fileName’, index: ’indexName’,SFS code - errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to open the specified file.

System action: CICS has not opened the file. Thetransaction continues. CICS can possibly generatefurther messages as a result of this error.

User response: Check that the SFS ’serverName’ isrunning. Check that the resource definitions for the fileare consistent with the configuration of SFS. Refer toSFS documentation for further information concerningthe SFS error code.

Destination:

CSMT

ERZ025002E Close of file: ’serverName’/’fileName’,index: ’indexName’ was unsuccessful, SFScode - errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to close a File Descriptor forthe specified file.

System action: The transaction continues. CICS can

possibly generate further messages as a result of thiserror.

User response: Check that SFS ’serverName’ is running.Refer to SFS documentation for further informationconcerning the SFS error code.

Destination:

CSMT

ERZ025005E Rewrite of file: ’serverName’/’fileName’,index: ’indexName’, was unsuccessful,SFS code - errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to rewrite a modified recordto the specified file.

System action: CICS has not rewritten the record. Thetransaction continues.

User response: Check that the SFS ’serverName’ is stillrunning. Refer to SFS documentation for furtherinformation concerning the SFS error code.

Destination:

CSMT

ERZ025006E Delete from file: ’serverName’/’fileName’,index: ’indexName’ was unsuccessful, SFScode - errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to delete a record from thespecified file.

System action: CICS has not deleted the record fromthe file. The transaction continues.


Destination:

CSMT

ERZ025008E Attempt to obtain information for file:’serverName’/’fileName’ and index:’indexName’ was unsuccessful, SFS Code- errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred while obtaining information concerning thespecified file and index.

System action: The transaction continues. CICS canpossibly generate further messages as a result of thiserror.

User response: Check that the SFS ’serverName’ isrunning. Check that the resource definitions for file’fileName’ and index ’indexName’ are consistent with theconfiguration of SFS. Refer to SFS documentation forfurther information concerning the SFS error code.

ERZ024117W • ERZ025008E


Destination:

CSMT

ERZ025009E Abnormal termination A25M: Failed toobtain memory for file controlinformation.


System action: The transaction abnormally terminates.

User response: This is possibly a transient problemthat can occur when CICS is heavily loaded. Resubmitthe transaction. If the problem persists, you possiblyneed to reconfigure the size of the Region Pool andrestart CICS.

Destination:

CSMT

ERZ025011E Select range in file: ’serverName’/’fileName’, index: ’indexName’ wasunsuccessful, SFS Code - errorCode’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to select records in thespecified file and index.



Destination:

CSMT

ERZ025012E Close of file: ’serverName’/’fileName’ wasunsuccessful, SFS code - errorCode’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to close a File Descriptor forthe specified file.


User response: Check that the SFS ’serverName’ is stillrunning. Refer to SFS documentation for furtherinformation concerning the SFS error code. An error onclosing the file can indicate that there are inflighttransactions which are holding locks on the file. If thefile is one that is used to store CICS queue data, thiscan cause a problem during region restart. Suchtransactions can be identified by filesystemadministration commands and, if necessary, the

transactions can be forced with the tkadmin command.Note that these locks are automatically dropped whenthe time specified by the IdleTimeout attribute in theSFS Definitions (SSD) has expired.

Destination:

CSMT

ERZ025013E Could not get information about index’indexName’ for file: ’serverName’/’fileName’, SFS code - errorCode’errorString’.

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to obtain information aboutthe specified file and index.


User response: Check that the SFS ’serverName’ isrunning. Check that the resource definitions for the fileare consistent with the configuration of SFS. Inparticular, check that the SFS file ’serverName’/’fileName’does have an index ’indexName’. Refer to SFSdocumentation for further information concerning theSFS error code.

Destination:

CSMT

ERZ025014E Unlock of File: ’serverName’/’fileName’,index: ’indexName’ was unsuccessful, SFScode - errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to unlock a record in thespecified file.

System action: The specified record was possibly notunlocked. The transaction continues. CICS can possiblygenerate further messages as a result of this error.


Destination:

CSMT

ERZ025016E Get ESN for File: ’serverName’/’fileName’Failed, SFS Code - errorCode ’errorString’

Explanation: When CICS inserts records into an ESDSfile, it first inserts the record and then obtains the EntrySequence Number (ESN) of the inserted record fromthe Structured File Server (SFS). The operation to obtainthis ESN was unsuccessful for the reason indicated.

System action: If the file is recoverable, the

ERZ025009E • ERZ025016E


transaction is abnormally terminated. Hence theinserted record is removed from the file. If the file isnot recoverable the transaction continues, althoughCICS possibly generates further messages or errorconditions as a result of this failure. In this latter case,CICS does not attempt to remove the inserted record,and a condition code can later be raised.

User response: If the file is non-recoverable, considerthe effects of the presence of the record whose ESN wasnot able to be obtained. Consult the SFS documentationfor further information concerning the error code. Thecauses of the failure are likely to be internal errorswithin either CICS or SFS; contact your supportorganization for additional information.

Destination:

CSMT

ERZ025017E Attempt to obtain duplicate keyinformation for file:’serverName’/’fileName’, index ’indexName’was unsuccessful, SFS Code - errorCode’errorString’

Explanation: CICS is in the process of deleting arecord from a file which is being accessed via an indexwhich permits duplicate keys. The Structured FileServer (SFS) reported an error while attempting todetect whether other records with the same key as thedeleted record also exist.

System action: The transaction continues. CICS canpossibly generate further messages as a result of thiserror. The record is deleted.

User response: The causes of the failure are likely tobe internal errors within either CICS or SFS; contactyour support organization for additional information.

Destination:

CSMT

ERZ025018E Inconsistent index information for file:’serverName’/’fileName’, index ’indexName’,field ’fieldName’

Explanation: The Structured File Server (SFS) indexspecification for the file refers to a segment for whichinformation cannot be retrieved. The SFS file and indexinformation are not consistent.



Destination:

CSMT

ERZ025020E Select position in file: ’serverName’/’fileName’, index: ’indexName’, for key:’keyValue’ was unsuccessful, SFS code -errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to select a record with theindicated key value in the specified file.


User response: Check that the SFS ’serverName’ isrunning. Refer to SFS documentation for furtherinformation concerning the SFS error code.

Destination:

CSMT

ERZ025021E Select position in file: ’serverName’/’fileName’, index: ’indexName’, for RRN:RRNd was unsuccessful, SFS Code -errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to select a record in aRelative File.



Destination:

CSMT

ERZ025022E Select position in file: ’serverName’/’fileName’, index: ’indexName’, for ESN:’ESN’ was unsuccessful, SFS code -errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to select a record in an EntrySequenced File.



Destination:

CSMT

ERZ025017E • ERZ025022E


ERZ025024E Read for delete in file: ’serverName’/’fileName’, index: ’indexName’ wasunsuccessful, SFS code - errorCode’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to obtain a record with theintention of deleting it.

System action: The record has not been deleted. Thetransaction continues. CICS can possibly generatefurther messages as a result of this error.


Destination:

CSMT

ERZ025026E Read record from file: ’serverName’/’fileName’, Index: ’indexName’ Failed, SFSCode - errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to read a record from thespecified file.



Destination:

CSMT

ERZ025027E Write record to file: ’serverName’/’fileName’, for index: ’indexName’ wasunsuccessful, SFS code - errorCode’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to write a record to the file.


User response: Check that the SFS ’serverName’ isrunning. Ensure that the SFS has sufficient processingthreads. Refer to SFS documentation for furtherinformation concerning the SFS error code.

Destination:

CSMT

ERZ025028E Write of record to relative file:’serverName’/ ’fileName’, for RRN: RRNdwas unsuccessful, SFS code - errorCode’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to write a record to theindicated Relative file.



Destination:

CSMT

ERZ025029E Write of record to entry sequenced file:’serverName’/ ’fileName’ was unsuccessful,SFS code - errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to write a record to theindicated entry sequenced file.



Destination:

CSMT

ERZ025030E Browse of file: ’serverName’/’fileName’,index: ’indexName’, key: ’keyValue’ wasunsuccessful due to earlier error

Explanation: CICS has detected an error when startinga browse in a clustered file. An error messagepreviously written to the message file possibly givesadditional information.


User response: Consult other messages recentlywritten to the message file for more detailed diagnosticinformation.

Destination:

CSMT

ERZ025024E • ERZ025030E


ERZ025031E Browse of file: ’serverName’/’fileName’,RRN: RRNd was unsuccessful due to anearlier error

Explanation: CICS has detected an error when startinga browse in a relative file. An error message previouslywritten to the message file possibly gives additionalinformation.



Destination:

CSMT

ERZ025032E Browse of file: ’serverName’/’fileName’,RBA: RBAd was unsuccessful due to anearlier error

Explanation: CICS has detected an error when startinga browse in an entry-sequenced file. An error messagepreviously written to the message file possibly givesadditional information.



Destination:

CSMT

ERZ025033E Browse of file at first record:’serverName’/’fileName’, index: ’indexName’was unsuccessful due to an earlier error

Explanation: CICS has detected an error when startinga browse at the first record in a file. An error messagepreviously written to the message file possibly givesadditional information.



Destination:

CSMT

ERZ025034E Browse of file at last record:’serverName’/’fileName’, index: ’indexName’was unsuccessful due to an earlier error

Explanation: CICS has detected an error when startinga browse at the last record in a file. An error messagepreviously written to the message file possibly givesadditional information.



Destination:

CSMT

ERZ025035E A Record with an invalid RBA has beenwritten to a non-transactional file:’serverName’/ ’fileName’, an attempt torepair the file has was unsuccessful, andhence the file may now contain invaliddata.

Explanation: A record was written to anon-transactional Entry Sequenced file, and either theresulting ESN was too large to be returned in thesupplied 32 bit RBA field or the ESN was not able to beobtained. An attempt to repair the file by deleting therecord was unsuccessful. Hence the file now possiblycontains an invalid record that is visible via anyalternate indexes.


User response: Contact system administrator. The filecan possibly be repaired by using SFS tools. Recurrenceof the problem can possibly be avoided by limiting thenumber of records in such files.

Destination:

CSMT

ERZ025041E Data structure inconsistency has beendetected for file: ’serverName’/’fileName’

Explanation: CICS self-consistency checking hasdetected an inconsistency in the CICS internal datastructures.

System action: After further self-consistency checking,CICS abnormally terminates.

User response: Determine the cause of theinconsistency in the internal data structures. It ispossible that these have been overwritten by defectiveapplication programs. It is also possible that an internalCICS error has caused this inconsistency.

ERZ025031E • ERZ025041E


Destination:

CSMT

ERZ025042E Invalid variable length recordspecification for file’serverName’/’fileName’

Explanation: The file definition declared to theStructured File Server (SFS) either has more than onevariable length field, or the variable length field is notthe last field in the record.


User response: Consult the TXSeries Infocenter fordetails of the SFS file structures that are supported byCICS. Either alter the CICS file definition to referencean SFS file whose structure is supported by CICS oradjust the SFS file definition.

Destination:

CSMT

ERZ025043E A variable length field has been foundindex ’indexName’ for file’serverName’/’fileName’

Explanation: The file definition declared on theStructured File Server has defined an index using avariable length field. CICS does not support suchindexes.


User response: Consult the TXSeries Infocenter fordetails of the SFS file structures that are supported byCICS. Either alter the CICS file definition to referencean SFS file whose structure is supported by CICS oradjust the SFS file definition. It is possible that this filehas other indexes that do not use variable length fields,and hence CICS can possibly be configured to accessthe files via such indexes.

Destination:

CSMT

ERZ025044E Record length recordLengthd too large forfile ’serverName’/’fileName’, Index:’indexName’.

Explanation: The Structured File Server (SFS) filedefinition has a record length greater than 32767.


User response: Consult the TXSeries Infocenter fordetails of the SFS file structures that are supported by

CICS. Either alter the CICS file definition to referencean SFS file whose structure is supported by CICS oradjust the SFS file definition.

Destination:

CSMT

ERZ025046E Variable field found in relative recordfile definition ’serverName’/’fileName’

Explanation: CICS supports only fixed length Relativefiles.


User response: Consult the TXSeries Infocenter forinformation concerning the SFS file structures that aresupported by CICS. Either alter the CICS file definitionto reference an SFS file whose structure is supported byCICS or adjust the SFS file definition.

Destination:

CSMT

ERZ025047W An Open File Descriptor has been leftopen on the SFS for file’serverName’/’fileName’, index ’indexName’

Explanation: CICS was unable to close a StructuredFile Server (SFS) Open File Descriptor (OFD). This waspossibly caused by a prior abnormal termination of aCICS process or by an inability to acquire sufficientRegion Pool memory to perform the requiredprocessing.

System action: Processing continues. Futuretransactions will possibly be unable to acquire exclusiveaccess to resources that held by the unterminated OFD.

User response: Use SFS administration facilities toidentify and terminate the OFD. A label is present onthe OFD which contains the CICS startup identifier.This identifier consists of the CICS region name andthe region startup time.

Destination:

console.msg

ERZ025050E SFS ’serverName’ is unavailable

Explanation: CICS has been unable to access aStructured File Server (SFS). This server has previouslybeen usable. The cause is possibly that the server hasan insufficient number of processing threads to enableit to service the number of simultaneous requests it isreceiving.


ERZ025042E • ERZ025050E


User response: Use SFS diagnostic procedures todetermine the nature of the problem. The SFS possiblyneeds to be restarted, possibly with a larger number ofthreads. CICS is then able to resume its use of theserver.

Destination:

CSMT

ERZ025051I SFS ’serverName’ is now available, file’fileName’ can now be accessed.

Explanation: The indicated Structured File Server hadpreviously become unavailable, and hence the specifiedfile was not able to be accessed. CICS has now beenable to access the server and has reopened the file.


User response: None

Destination:

CSMT

ERZ025052E File handle for file ’serverName’/’fileName’invalid

Explanation: It is not possible to access the specifiedfile because of the indicated Structured File Server(SFS) error. The cause is possibly that the server has aninsufficient number of processing threads to enable it toservice the number of simultaneous requests it isreceiving.

System action: The transaction continues. CICS canpossibly generate further messages as a result of thiserror. Use of the file continues to give errors until theSFS is again available.

User response: Use SFS diagnostic procedures todetermine the nature of the problem. The SFS possiblyneeds to be restarted, possibly with a larger number ofthreads. CICS is then able to resume its use of theserver.

Destination:

CSMT

ERZ025053E An abnormal return code, ’returnCode’,has been returned by the SFS serverside transaction support

Explanation: The call to sfs_ServerTransactionBeginfailed

System action: The CICS region terminatesimmediately.

User response: Investigate the reasons for this returncode as specified in the documentation.

Destination:

stderr

ERZ025054E An abnormal return code, ’returnCode’,has been returned by the SFS serverside transaction commit

Explanation: The call to sfs_ServerTransactionCommitfailed



Destination:

CSMT

ERZ025055E An abnormal return code, ’returnCode’,has been returned by the SFS serverside transaction backout

Explanation: The call to functionsfs_ServerTransactionAbort failed.



Destination:

CSMT

ERZ025092E Key comparison for file:’serverName’/’fileName’, Index: ’indexName’Failed, SFS Code - errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to compare two key values.



Destination:

CSMT

ERZ025093E Empty of file: ’serverName’/’fileName’ wasunsuccessful, SFS Code - errorCode’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to empty a file during a fileopen operation.

System action: The transaction continues. CICS canpossibly generate further messages as a result of thiserror. The file has not been emptied.

User response: Check that the SFS ’serverName’ isrunning. Check that there are no other users of the file.

ERZ025051I • ERZ025093E


It is possible that the file has been opened by thecurrent CICS region, using a different File Controlaccess path. It is possible that another CICS region isaccessing the file. It is possible that an off-lineapplication program is using the file. Anotherpossibility is that a process that was previously usingthe file has abnormally terminated. In this latter case,the SFS administration interface permits the Open FileDescriptors for the file to be identified, and, whereappropriate, terminated. Refer to SFS documentationfor further information concerning the SFS error code.

Destination:

CSMT

ERZ025094E Invalid segment number segmentNumberfor file: ’serverName’/’fileName’, index’indexName’

Explanation: The SFS index specification for the filerefers to a segment number which does not exist. TheSFS file and index information are not consistent.



Destination:

CSMT

ERZ025095E Unsuccessful reopen of file handle forfile: ’serverName’/’fileName’, index:’indexName’, SFS code - errorCode’errorString’

Explanation: A previously open Structured File Server(SFS) file was not able to be reopened. The file possiblyneeds to be reopened for one of two reasons: SFS hasbecome available after previously becoming unavailableand so the file needs to be reopened, or SFS hasterminated an Open File Descriptor for the file and soit needs to be reopened.

System action: CICS has not reopened the file. Thetransaction continues. CICS can possibly generatefurther messages as a result of this error.

User response: Refer to SFS documentation for furtherinformation concerning the SFS error code.

Destination:

CSMT

ERZ025096I File handle reopened for file:’serverName’/’fileName’, index: ’indexName’

Explanation: The indicated Structured File Server(SFS) had previously terminated an Open FileDescriptor. The file has now been reopened.

System action: The transaction continues

User response: None

Destination:

CSMT

ERZ025097E Select record for deletion in file:’serverName’/’fileName’, index: ’indexName’key ’keyValue’ was unsuccessful, SFSCode - ’errorCode’ ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to select a record with theintention of deleting it.


User response: Refer to SFS documentation for furtherinformation concerning the SFS error code.

Destination:

CSMT

ERZ025098E CICS abnormal termination A25E: wasunable to get an RBA for recoverablefile ’serverName’/’fileName’; SFS Code -errorCode ’errorString’

Explanation: CICS has encountered a problem whenattempting to obtain the RBA of a record that it isinserting to a Structured File Server (SFS) file.

System action: The transaction terminates with codeA25E. CICS does not insert the record.

User response: Refer to SFS documentation forinformation concerning the SFS error code.

Destination:

CSMT

ERZ025099W Index ’indexName’ for file’serverName’/’fileName’ contains an NLSfield: generic operations should not beused

Explanation: The Structured File Server (SFS) does notsupport generic key operations on NLS data. CICS FileControl generic key operations are not reliable whenapplied to such indexes.

System action: None

User response: Consult TXSeries Infocenter for details

ERZ025094E • ERZ025099W


of the file structures that are supported by CICS. Eitheralter the CICS file definition to reference an SFS filewhose structure is supported by CICS or adjust the SFSfile definition.

Destination:

CSMT

ERZ025100W Unsuccessful attempt at labelling OpenFile Descriptor for file’serverName’/’fileName’, index ’indexName’;SFS code - errorCode ’errorString’

Explanation: An unsuccessful attempt was made tolabel an Open File Descriptor (OFD). The OFD labelwas intended to help identify which OFDs were usedon your CICS region, so that in the event of the regionabnormally terminating any OFDs left on theStructured File Server (SFS) were able to be determinedand removed by using SFS administration facilities.

System action: Processing continues. CICS continuesto use the file.

User response: None

Destination:

CSMT

ERZ025101E Abnormal termination A25L: Failed toretain transactional lock for file’serverName’/’fileName’, index ’indexName’;SFS code - errorCode ’errorString’

Explanation: CICS was unsuccessful in retaining atransactional lock for the named file.



Destination:

CSMT

ERZ025103W Unable to use the SFS as the transactionhas been terminated

Explanation: CICS was not able to perform anoperation on the structured file system, as thetransaction that was being used has beenasynchronously terminated.

System action: CICS terminates the transaction.

User response: Something other than CICS has causedthe transaction to terminate. If this persistently occurs,investigate the cause. The most likely culprit is the SFS,but communications errors are also possibly the cause.CICS continues to run normally, however.

Destination:

CSMT

ERZ025104E SFS batch call number ’callNumber’ wasunsuccessful with SFS code ’errorCode’ -’errorString’.

Explanation: CICS has detected an error whenattempting to perform a sequence of batched SFS writesor updates.


User response: Refer to SFS documentation for theSFS error code. Check that the SFS is running andlistening for RPCs. Otherwise refer to earlier messagesgenerated to determine the cause of the problem.

Destination:

console.msg

ERZ025105E Request to allocate storage for SFS batchcall was unsuccessful.

Explanation: CICS was unable to satisfy a storageallocation request.


User response: Release storage by reducing the loadon the machine.

Destination:

console.msg

ERZ025106W Close of OFD ’OFDnumber’ wasunsuccessful; SFS code - ’errorCode’

Explanation: A Structured File Server (SFS) problemhas occurred when attempting to close a File Descriptorfor the specified file.

System action: The transaction continues. CICS canpossibly generate further messages as a result of thiswarning.

User response: Check that the SFS is running. Refer toSFS documentation for further information concerningthe SFS code.

Destination:

CSMT

ERZ025107W Allocation of numPages page(s) of diskspace was unsuccessful for file:’serverName’/’fileName’, SFS Code -errorCode ’errorString’

Explanation: A Structured File Server (SFS) error hasoccurred when attempting to allocate space for a file

ERZ025100W • ERZ025107W


during an file open operation.

System action: The transaction continues. The filespace has not been allocated.

User response: Check that there is enough space onthe SFS volume associated with this file.

Destination:

CSMT

ERZ026001E Search string is missing

Explanation: You entered a find command without asearch string.

System action: CEBR waits for valid input.

User response: Retry the command with search string,or enter any other valid command.

Destination:

CEBR user terminal

ERZ026002E No string to find

Explanation: You requested a repeated find bypressing the PF6 key, but you have not previouslyrequested a find.


User response: Enter some other command.

Destination:

CEBR user terminal

ERZ026003E Line number is missing.

Explanation: You did not specify a line number forthe LINE command.


User response: Retry the command with a valid linenumber, or enter any other valid command.

Destination:

CEBR user terminal

ERZ026004E Line number is too large.

Explanation: You requested a line number thatexceeds the number of records in the TemporaryStorage queue being browsed.


User response: Retry the command with a valid linenumber, or enter any other valid command.

Destination:

CEBR user terminal

ERZ026005E Column number is missing.

Explanation: You did not specify a column numberfor the COLUMN command.


User response: Retry the command with a validcolumn number, or enter any other valid command.

Destination:

CEBR user terminal

ERZ026006E Column number is too large.

Explanation: You requested a column number thatexceeds the number of columns of data found in theTemporary Storage queue being browsed.


User response: Retry the command with a validcolumn number, or enter any other valid command.

Destination:

CEBR user terminal

ERZ026007E Unable to purge temporary storagequeue. Response Code ’responseText’(responseCode)

Explanation: CEBR attempted to purge data from thetemporary storage (TS) queue but was not successful.CEBR has issued an EXEC CICS DELETE QUEUE TScommand, which has not succeeded. The messageindicates the condition code that was returned by CICSin the EIB.

System action: CICS has not purged the TS queue.CEBR waits for further input.

User response: Determine the cause of problem andcorrect it. Additional diagnostics were possibly writtento console.msg. If the TS queue is an auxiliary queuethen check that the Structured File Server is running.

Destination:

CEBR user terminal

ERZ026008E Terminal name is missing.

Explanation: You did not specify a terminal identifierfor the TERMINAL command.


User response: Retry the command with a validterminal identifier, or enter any other valid command.

Destination:

CEBR user terminal

ERZ026001E • ERZ026008E


ERZ026009E Queue name is missing.

Explanation: You did not specify a temporary storagequeue name for the QUEUE command.


User response: Retry the command with a validqueue name, or enter any other valid command.

Destination:

CEBR user terminal

ERZ026010E Name of transient data queue ismissing.″

Explanation: You did not specify a transient dataqueue name for the GET or PUT command.


User response: Retry the command with a validqueue name, or issue any other valid command.

Destination:

CEBR user terminal

ERZ026011E Unable to read transient data queue.Response Code ’responseText’(responseCode)

Explanation: CEBR was attempting to execute a GETcommand but was not able to read from a transientdata (TD) queue. CEBR issued an EXEC CICS READQTD command, which has not succeeded. The messageindicates the condition code that was returned by CICSin the EIB.

System action: It is possible that CEBR partiallycompleted the GET command. The current TS queuepossibly now contains additional records. CEBR nowwaits for further input.

User response: Determine the cause of the problem.Further diagnostics can possibly have been written toconsole.msg. Check that specified TD queue exists, thatit is valid to read from it and that access to it isauthorized. If the queue was an intra-partition TDqueue, check that the file server is still running. Correctany problems and re-issue the GET command, or issueany other valid command.

Destination:

CEBR user terminal

ERZ026012E Unable to write transient data queue.Response Code ’responseText’(responseCode)

Explanation: CEBR was attempting to execute a PUTcommand but was unable to write data to the transientdata (TD) queue. CEBR has issued an EXEC CICSWRITEQ TD command, which has not succeeded. The

message indicates the condition code that was returnedby CICS in the EIB.

System action: It is possible that CEBR partiallycompleted the PUT command, and the TD queuepossibly now contains additional records. CEBR waitsfor further input.

User response: Determine the cause of the problem.Further diagnostics are possibly written to console.msg.Check that specified TD queue exists, that it is valid towrite to it and that access to it is authorized. If thequeue was an intra-partition TD queue, check that thefile server is still running. Correct any problems andre-issue the PUT command, or issue any other validcommand.

Destination:

CEBR user terminal

ERZ026013E Command is not known. Please re-enter.

Explanation: You have specified a command that isnot recognized.


User response: Issue a valid command.

Destination:

CEBR user terminal

ERZ026014E Line command requires a positiveinteger.

Explanation: You have supplied an argument to theLINE command that is not a positive integer.


User response: Retry the command with a validargument, or issue any other valid command.

Destination:

CEBR user terminal

ERZ026015E Column command requires a positiveinteger.

Explanation: You have supplied an argument to theCOLUMN command that is not a positive integer.


User response: Retry the command with a validargument, or issue any other valid command.

Destination:

CEBR user terminal

ERZ026009E • ERZ026015E


ERZ026016E Hexadecimal queue name is too long.

Explanation: You attempted to specify a queue nameas a hexadecimal string but the string specified was toolong. Each pair of hexadecimal digits correspond to onecharacter of the queue name. The maximum length of atemporary storage queue name is 8 characters andhence for such queues the maximum number ofhexadecimal digits is 16. The maximum length of atransient data queue name is 4 characters and hence forthese queues the maximum number of hexadecimaldigits is 8.



Destination:

CEBR user terminal

ERZ026017E Queue specified contains an invalid hexdigit.

Explanation: You attempted to specify a queue nameas a hexadecimal string but you used an invalidhexadecimal format. Only the digits 0 to 9 and theletters A to F can be used. The name must be delimitedby apostrophes.



Destination:

CEBR user terminal

ERZ026018I Browse has ended normally. Ready fornext transaction.

Explanation: Message displayed when CEBRterminates.

System action: CICS awaits the submission of the nexttransaction.

User response: Submit another transaction.

Destination:

CEBR user terminal

ERZ026019I String was not found.

Explanation: CEBR did not find a record containingthe string specified.


User response: None

Destination:

CEBR user terminal

ERZ026021I Temporary storage queue ’queueName’ isempty.

Explanation: CEBR displays this message when thecurrent TS queue is empty.

System action: None

User response: None

Destination:

CEBR user terminal

ERZ026023E Command with invalid parameter wasignored

Explanation: You have either supplied a parameter toa command where none was expected, or you havesupplied more than one parameter for a command thatrequires a single parameter. The commands that expectno parameter are TOP, BOTTOM, PURGE, CANCELand QUIT. The commands that expect one parameterare FIND, QUEUE, TERM, LINE, COLUMN, GET andPUT.

System action: CEBR did not execute the command.CEBR waits for valid input.

User response: Retry the command without theextraneous parameter, or issue any other validcommand.

Destination:

CEBR user terminal

ERZ026024E Unable to read temporary storage queue.Response Code ’responseText’(responseCode)

Explanation: CEBR was attempting to execute a PUTcommand but was unable to read data from thetemporary storage (TS) queue. CEBR has issued anEXEC CICS READQ TS command, which has notsucceeded. The message indicates the condition codethat was returned.

System action: Some records were possibly written tothe transient data queue specified in the PUTcommand. CEBR now waits for further input.

User response: Determine the cause of the problem.Further diagnostics were possibly written toconsole.msg. If the queue was an auxiliary TS queue,check that the file server is still running. Correct anyproblems and retry the PUT command, or issue anyother valid command.

Destination:

CEBR user terminal

ERZ026016E • ERZ026024E


ERZ026025E Unable to write temporary storagequeue. Response Code ’responseText’(responseCode)

Explanation: CEBR was attempting to execute a GETcommand but was unable to write data to thetemporary storage (TS) queue. CEBR has issued anEXEC CICS WRITEQ TS command, which has notsucceeded. The message indicates the condition codethat was returned.

System action: It is possible that CEBR wrote somerecords to the TS queue. CEBR waits for valid input.

User response: Determine the cause of the problem.Further diagnostics were possibly written toconsole.msg. If the queue was an auxiliary TS queue,check that the file server is still running. Correct anyproblems and retry the GET command, or issue anyother valid command.

Destination:

CEBR user terminal

ERZ026026W ’ignoredCharacters’ ignored

Explanation: You entered a FIND command butcharacters were found after the character that delimitsthe FIND string.

System action: CEBR executes the FIND commandhaving excluded the superfluous string from the search.

User response: None

Destination:

CEBR user terminal

ERZ026027E Character Queue name is too long

Explanation: You entered a queue name that is toolong for the type of queue. Temporary storage queuenames must not be longer than 8 characters. Transientdata queue names must not be longer than 4 characters.

System action: CEBR did not carry out the command.CEBR waits for valid input.

User response: Retry the command with a validqueue name, or issue any other valid command.

Destination:

CEBR user terminal

ERZ026028E Quote to end hexadecimal string ismissing

Explanation: You entered a queue name inhexadecimal format, but the quote indicating the end ofthe hexadecimal string was not found.


User response: Re-enter the hexadecimal queue with

the correct syntax, or enter any other valid command.

Destination:

CEBR user terminal

ERZ026031E Unrecognized input. Please try again.

Explanation: You entered a command that is notsupported by CEBR.



Destination:

CEBR user terminal

ERZ026032W Too many command arguments;superfluous arguments ignored.

Explanation: You have either supplied a parameter toa command where none was expected, or you havesupplied more than one parameter for a command therequires a single parameter. The commands that expectno parameter are TOP, BOTTOM, PURGE, CANCELand QUIT. The commands that expect one parameterare FIND, QUEUE, TERM, LINE, COLUMN, GET andPUT.

System action: CEBR executes the command ignoringall superfluous arguments.


Destination:

CEBR user terminal

ERZ026033E Find terminated abnormally.

Explanation: A Find (or Find Next) was executed, butwhile attempting to read a record from the TemporaryStorage queue an unknown error occurred.

System action: The Find is halted and control isreturned back to the user.


Destination:

CEBR user terminal

ERZ026034E Error attempting to read queue’queueName’. Response Code’responseText’ (responseCode)

Explanation: While attempting to read a line from aTS queue a serious error occurred. Browsing of thequeue is halted and the repeat lines are cleared.

System action: Viewing of the current queue is haltedand the repeat lines on the screen are cleared.

User response: Attempt to re-read the queue, or issueanother valid command.

ERZ026025E • ERZ026034E


Destination:

CEBR user terminal

ERZ027001E Remote system ’sysId’ cannot be found

Explanation:

A Communications Definition (CD) entry called sysIdwas not able to be found. This CD entry has beenrequested either in the SYSID option of an EXEC CICScommand or in the RemoteSysId attribute of thedefinition for a resource requested by the transaction.Possible causes of this error include:

v A CD entry called sysId, which specifies the locationof the remote system, has not been defined.

v A CD entry that specifies the location of the remotesystem has been defined, but it is not called sysId.

v A CD entry called sysId has been defined in the CICSpermanent database but this definition has not beenadded to your region’s runtime database.

System action: CICS returns the SYSIDERR conditioncode to your transaction.

User response:

1. Determine whether CD entry sysId is defined in thepermanent database using the following command(where regionName is the name of your region):

cicsget -r <regionName> -c cd sysId

If the CD entry does exist, use the cicsinstallcommand to add it to your region’s runtimedatabase. cicsinstall is described in the TXSeriesInfocenter

2. If the CD entry does not exist, list the CD entriesdefined in your region using the:

cicsget -r <regionName> -c cd -l

command. Then use the:

cicsget -r <regionName> -c cd <name>

command, where <name> is the name of a CDentry, to display each CD entry. If you discover aCD entry for the remote system is already defined,change the application program or resourcedefinition to use the name of this CD entry as theSYSID.

3. If no CD entry is defined for the remote systemthen you need to add one called sysId to yourregion. This is described in the TXSeries Infocenter

Rerun the request once any necessary corrections havebeen made.

Destination:

CSMT

ERZ027002E Communications errorprimaryCode/secondaryCode on connectionto system ’sysId’

Explanation: CICS detected a communications errorwhile processing an EXEC CICS command inconjunction with the remote system configured inCommunications Definition (CD) entry sysId. The typeof error detected is described by error codeprimaryCode/secondaryCode.

System action: CICS abnormally terminates theintersystem request for the EXEC CICS command.Further messages can be logged.

User response: Refer to the TXSeries Infocenter, whichdescribes what the error code primaryCode/secondaryCode means and how to correct the problem.

Destination:

CSMT

ERZ027003E CICS cannot execute DL/I requestreceived from system ’sysId’

Explanation: A request to execute a DL/I function hasbeen received from system ’sysId’. This CICS systemdoes not support the DL/I Application ProgrammingInterface (API), so cannot satisfy the request.

System action: CICS abnormally terminates thefunction shipping mirror transaction.

User response: Use the procedures appropriate to theremote system to ensure that it does not attempt tofunction ship DL/I requests to CICS. This can includemodifying the remote transaction and the remotesystem’s resource definitions.

Destination:

CSMT

ERZ027004E System ’sysId’ is not in service

Explanation: CICS cannot send a remote EXEC CICSrequest to system ’sysId’ because the InService attributeof the Communications Definition (CD) for ’sysId’ is setto no.

System action: CICS returns the SYSIDERR conditioncode to your program.

User response: Set the system back in service bysetting the InService attribute of the CD for the systemto yes, then retry the transaction. The system can be setback in service while the region is running using thecommand CECI SET CONNECTION(sysId)INSERVICE.

Destination:

CSMT

ERZ027001E • ERZ027004E


ERZ027005W System ’sysId’ rejected initialization data

Explanation: The remote system configured inCommunications Definition (CD) entry ’sysId’ rejectedthe function shipping initialization data which specifiesthe local code page and byte order.

System action: CICS retries the function shippingrequest without the initialization data. The remotesystem assumes defaults for the code page and byteorder.

User response: If the remote system is CICS, prepare acommunications trace showing the initialization datasent to the remote system and contact your supportorganization. Otherwise, determine if the default codepage and byte order used by the remote system areappropriate for your network. If so, ignore this messageand continue processing. If not, determine if a versionof CICS which supports the function shippinginitialization data is available for the remote system.

Destination:

CSMT

ERZ027006E Conversion template is inconsistentwith application data for resource’resourceName’ and type resourceType

Explanation:

The conversion template for resource ’resourceName’and type resourceType specifies either a select orconversion offset which is larger than the amount ofapplication data that the function shipping mirrortransaction is converting. The type is as follows

v 0 - File Definition (FD)

v 1 - Transient Data Definition (TDD)

v 2 - Temporary Storage Definition (TSD)

v 3 - Transaction Definition (TD)


v 5 - Program Definition (PD)


User response: Examine your transaction and theconversion template for the resource being accessed toensure that they are consistent with each other. Inparticular, ensure that select and conversion offsetsspecify valid offsets which are less than the size of theapplication data that your transaction is functionshipping.

Destination:

CSMT

ERZ027007W The function shipping mirrortransaction received an error (errorCode)while executing a START NOCHECKrequest.

Explanation: The function shipping mirror transactionhas executed a START NOCHECK request and hasreceived an error of ’errorCode’ as a result. The state ofthe intersystems link is such that the error responsecannot be returned to the requesting system.

System action: If the request was for a protectedresource, the CICS function shipping mirror transactionabnormally terminates.

User response: Refer to the EIBRESP code ’errorCode’in the TXSeries Infocenter. Examine the CICS messagefiles for any additional information.

Destination:

CSMT

ERZ027008E A backout of the current Logical Unit ofWork (LUW) is required

Explanation: The function shipping request cannotproceed because the LUW which it is part of has beenbacked out.


User response: Examine the CICS message files foradditional information that can help to determine whythe LUW was abnormally terminated. Use theprocedures appropriate to any remote systems withwhich the transaction has performed intersystemcommunication, to obtain any additional information.

Destination:

CSMT

ERZ027009E Rollback was received from system’sysId’, in response to a CICS synclevel 1commit request.

Explanation: Your CICS application has been usingsynclevel 1 to process remote function shippedresources. The application took a syncpoint, eitherimplicitly or explicitly, and this has caused all localresources and synclevel 2 partner systems to becommitted. However, when a commit message was sentto a synclevel 1 partner system, the system voted tobackout.

System action: CICS continues the synclevel 1 commitprocessing, with the intention of committing as manysynclevel 1 resources as possible. The transaction isabnormally terminated when the synclevel 1 processingis complete.

User response: Use the procedures appropriate to theremote system sysId to obtain additional information

ERZ027005W • ERZ027009E


that can help to determine why the remote resourcevoted to roll back. Perform any necessary recoveryprocedures.

Destination:

CSMT

ERZ027010E Communications failure during a CICSsynclevel 1 commit request.

Explanation: Your CICS application has been usingsynclevel 1 to process remote function shippedresources. The application took a syncpoint, eitherimplicitly or explicitly, and this has caused all localresources and synclevel 2 partner systems to becommitted. However the commit message failed to besent to one or more synclevel 1 partner systems.

System action: CICS continues the synclevel 1 commitprocessing, with the intention of committing as manysynclevel 1 resources as possible. The transaction isabnormally terminated when the synclevel 1 processingis complete.

User response: Check for earlier messages thatindicate the names of the remote partner systems andthe reasons for the communications failures.

Destination:

CSMT

ERZ027011E Remote command request to system sysIdis requestLength bytes long which exceedsthe maximum length of maxLength bytes

Explanation: CICS is unable to proceed with a remoteEXEC CICS command request to the system configuredin Communications Definition (CD) entry sysId becausethe amount of data that must be transmitted,requestLength, exceeds the maximum amount of datathat can be sent as part of a single request. The datarequired for such a request contains the user datapassed on the request plus a description of the EXECCICS command specified by the application. Thenumber of bytes required to describe an EXEC CICScommand varies depending on the type of request andthe number of options specified. Aim to keep the userdata under 32500 bytes long.

System action: CICS returns the LENGERR conditionto the application. Further messages can be logged.

User response: Alter the application so that it sendsless data on a single EXEC CICS command request. Ifyour application needs to send large amounts of datato the remote system consider using DistributedTransaction Processing (DTP) for a better solution.

Destination:

CSMT

ERZ027012E Unexpected communications indicatorindicatorNumber received from mirrortransaction ’transId’ in system ’sysId’

Explanation:

CICS is unable to continue with a function shippingrequest because it received an unexpectedcommunications indicator, indicatorNumber, from themirror transaction transId. transId is running on thesystem configured in Communications Definition (CD)entry sysId. The communications indicators are asfollows:

5 No indicator was received (when one wasexpected).

6 A Change Direction (CD) indicator wasreceived.

7 A Confirm (RQD2) indicator was received.

8 A Confirm (RQD2) and Change Direction (CD)indicator was received.

9 A Confirm (RQD2) and Conditional EndBracket (CEB) indicator was received.

10 A syncpoint indicator was received.

11 A syncpoint and Change Direction (CD)indicator was received.

12 A syncpoint and Conditional End Bracket(CEB) indicator was received.

13 A Conditional End Bracket (CEB) indicatorwas received.


User response: Check the definition of transactiontransId in the remote system invokes the CICS mirrorprogram. Verify that the remote system and theconnection to it are functioning normally byperforming other intersystem communication functions(such as transaction routing) to the remote system. Ifthe problem persists, prepare a communications traceshowing the data received from the remote system andcontact your support organization.

Destination:

CSMT

ERZ027013E The function shipping mirrortransaction ’transId’ cannot be startedfrom a terminal

Explanation: You have started the function shippingmirror transaction by entering the transaction code’transId’ at a terminal. The function shipping mirrortransaction can only be started by a remote system.


User response: Do not attempt to start the functionshipping mirror transaction from a terminal.

ERZ027010E • ERZ027013E


Destination:

CSMT

ERZ027014E A conversion template for resource’resourceName’ and type resourceType isnot defined

Explanation:

The resource definition for ’resourceName’ and typeresourceType has the attribute TemplateDefined set toyes, but a conversion template for that resource cannotbe found. This is a configuration error as theTemplateDefined must be set to yes only if you havedefined and installed a conversion template for theresource. The type, resourceType, is as follows.

v 0 - File Definition (FD)

v 1 - Transient Data Definition (TDD)

v 2 - Temporary Storage Definition (TSD)



v 5 - Program Definition (PD)

Data conversion templates are used by CICS to convertapplication data that is sent between CICS regionswhich are using different code pages. Data conversionis performed by the mirror transaction. Therefore,conversion templates are normally only required in theregion where the resource resides. However, if arequest is daisy-chained through a number of CICSregions, the data conversion template can be placed inan intermediate region. This moves the data conversionfrom the resource owning region to the intermediateregion. For more information on data conversion, seethe TXSeries Infocenter.


User response: If conversion is not required for theresource set the attribute TemplateDefined to no forthe resource definition and retry the transaction. Ifconversion is required, define a conversion template forthe resource and make it available to the CICS regionusing cicscvt.

Destination:

CSMT

ERZ027015E Cannot allocate storage

Explanation: CICS attempted to allocate task privatestorage when encoding or decoding a message to besent to or received from a remote system, but wasunsuccessful.


User response: Consider simplifying yourtransactions, such that they use less task private storageor increase the amount of task private storage available.

Refer to the TXSeries Infocenter for more information.

Destination:

CSMT

ERZ027016E Incorrectly formatted message received

Explanation: CICS was not able to decode a messagereceived from a remote system while function shipping.


User response: Ensure that the remote system is notexecuting a Distributed Transaction Processing (DTP)transaction. If it is, modify the transaction and/or itsresource definitions, so that it does not execute as thefunction shipping mirror transaction, or does notallocate conversations to the function shipping mirrortransaction. If this is not the case, verify that the remotesystem and the connection to it are functioningnormally by performing other intersystemcommunication functions (such as transaction routing)to the remote system. If the problem persists, prepare acommunications trace showing the data received fromthe remote system and contact your supportorganization.

Destination:

CSMT

ERZ027017E Data conversion routine for resourceTyperesource, ’resourceName’, is unavailable.The server code page is ’serverCodePage’(’serverShortCode’). The code pagereceived from remote system, ’sysId’, was’receivedCodePage’. The client code pageis ’clientCodePage’ (’clientShortCode’)

Explanation: CICS is unable to perform dataconversion for a function shipping request receivedfrom the remote system defined in CommunicationsDefinitions (CD) entry sysId because iconv conversionroutines for the requested code pages are not available.Data conversion has been attempted because resourceresourceName has TemplateDefined=yes in its resourcedefinition and a conversion template is available. (Referto the TXSeries Infocenter for more information onconversion templates.) The conversion template isgenerated from DFHCNV macros using cicscvt. Thesemacros specify the shortcode for this local CICS region(SRVERCP=serverShortCode) and a default shortcode forthe remote system (CLINTCP=clientShortCode). Theremote system can also send its own short code, whichoverrides clientShortCode. (This can be sent with therequest, or if the remote system is an IBM CICS client,it can be sent with the client install request handled bythe CCIN transaction.) CICS translates the shortcodesinto code page names. So serverShortCode andclientShortCode become serverCodePage andclientCodePage respectively. (If a shortcode is notrecognized by CICS, it uses the shortcode as the codepage name.) It then calls iconv to perform the data

ERZ027014E • ERZ027017E


conversion. This message is produced because iconv isunable to locate the conversion routines that convertbetween code pages serverCodePage and receivedCodePageor code pages serverCodePage and clientCodePage.


User response: Determine whether data conversion isrequired for this resource. If it is not then setTemplateDefined=no in the resourceType entry forresourceName. Examine the shortcodes defined in theDFHCNV macros. Check that they are being mapped tothe expected code pages. Alter the shortcodes in theDFHCNV macros if they are not correct. For moreinformation on shortcodes and the DFHCNV macrosrefer to the TXSeries Infocenter. Ensure that the dataconversion routines required by your region arecorrectly installed on the machine. Refer to youroperating system documentation on the iconv utilityfor information on supported data conversion routines.Some operating systems allow you to generate youown conversion routines using the genxlt utility. Ifgenxlt is available, and the operating system does notprovide the conversion routines you need, then createand install the required routines on your machine.When the data conversion configuration is correct,rerun the intersystem request.

Destination:

CSMT

ERZ027018E Converting from code page ’codePage1’ tocode page ’codePage2’ was unsuccessful

Explanation:

Data for a function shipping request was not able to beconverted between code page ’codePage1’ and codepage ’codePage2’ because:

v there is an error in the conversion routine or

v characters in the data are invalid for code pagecodePage1 or

v characters in the data are not defined in code pagecodePage2.


User response: Ensure the data being sent or receivedas part of the function shipping request is valid forcode pages codePage1 and codePage2. If not, youpossibly need to use the function shipping userconversion exit (DFHUCNV) to convert the data. Referto the TXSeries Infocenter for more information. Ensurethe conversion routines for code pages codePage1 andcodePage2 are correctly installed. Some operatingsystems allow you to define you own conversionroutines using the genxlt utility. If the conversionroutine is user-defined then ensure it is correct. Consultthe operating system documentation on iconv andgenxlt for further details. If you are unable to solve thisproblem yourself, contact your support organization.

Destination:

CSMT

ERZ027021E Unexpected Function Shipping Error

Explanation: The function shipping mirror transactionhas failed due to lack of system resources.


User response: Examine the CICS message files foradditional information relating to this message.Consider retrying the transaction when the system ismore lightly loaded. If the problem persists, contactyour support organization.

Destination:

CSMT

ERZ027022E CICS self-consistency checking hasdetected an inconsistency in the CICSinternal data structures

Explanation: An inconsistency in the CICS run-timecopy of the user conversion templates has beendetected.

System action: The region continues, but the functionshipping is possibly unsuccessful.

User response: If the inconsistency is such that thefunction shipping mirror transaction is unable toconvert application data, restart the region. Also contactyour support organization.

Destination:

console.msg

ERZ027024E The mirror transaction ’transId’ isunknown on system ’sysId’

Explanation:

The intersystem request to run the mirror transactiontransId on the remote system configured inCommunications Definition (CD) entry sysId wasunsuccessful because transId is not recognized as amirror transaction by the remote system. The mirrortransaction is started in the remote system by FunctionShipping, Asynchronous Processing and DistributedProgram Link (DPL) requests. By default, CICS uses theCPMI mirror transaction. This can be changed on DPLrequests

v using the TransId attribute of the local ProgramDefinitions (PD) entry for the linked-to program or

v using the TRANSID option of the EXEC CICS LINKcommand.

System action: The TERMERR condition code isreturned to the transaction.

User response: Check that the transaction specified issupported by the remote system and, if required,change your local application to use a transaction that

ERZ027018E • ERZ027024E


the remote system supports. Check that the remotesystem is correctly configured and running. Rerun thelocal transaction.

Destination:

CSMT

ERZ027025E SYNCONRETURN is not allowed whena mirror task is already running

Explanation: The SYNCONRETURN option has beenspecified in a Distributed Program Link (DPL) request,but the requesting program is already in conversationwith a mirror task (that is, a logical unit-of-work(LUW) is in progress) in the remote system. The mirrortask can be a previous DPL request or a FunctionShipping command.

System action: The INVREQ condition code isreturned to the transaction.

User response: Correct the local program so that asyncpoint is taken before the DPL SYNCONRETURNrequest, or remove the SYNCONRETURN option fromthe LINK request.

Destination:

CSMT

ERZ027026E Change of mirror transaction to’newTransId’ is not allowed; ’oldTransId’ isstill running

Explanation: ’newTransId’ has been specified, either asthe TRANSID option, or in the TransId attribute of theProgram Definition (PD), in a Distributed Program Link(DPL) request. However, the requesting program isalready in conversation with a mirror task (that is, alogical unit-of-work (LUW) is in progress) in theremote region with TRANSID ’oldTransId’. The mirrortask can be a previous DPL request or a FunctionShipping command.

System action: The INVREQ condition code isreturned to the transaction.

User response: Remove the TRANSID option from theDPL request, or the TransId attribute from the PD, sothat the DPL request runs under the TransId of theexisting mirror task (or change it to be the sameexplicitly). Alternatively, take a syncpoint before theDPL request, to complete the previous mirror task.

Destination:

CSMT

ERZ027027E A DPL mirror transaction cannot replyto a syncpoint request received on aDTP conversation with system ’sysId’

Explanation: The current program was started as theresult of a Distributed Program Link (DPL) request

which did not specify the SYNCONRETURN option. Ithas started a Distributed Transaction Processing (DTP)conversation with another system ’sysId’. The programthat originated the DPL request is the only one whichis allowed to issue syncpoint or backout commands.


User response: Correct the programs so that theoriginator of the DPL request is the only one that issuessyncpoints, or use the SYNCONRETURN option.

Destination:

CSMT

ERZ027028E Unauthorized to run mirror transaction’transId’ on remote system ’sysId’ for user’userId’

Explanation:

A function shipping request was unsuccessful becauseeither the local CICS region or the user userId does nothave sufficient authority to access:

v the remote system,

v the PPC gateway (if applicable),

v the mirror transaction transId or

v the resources requested in the function shippingrequest.

Possible reasons for this include:

v on a SNA connection using a PPC gateway theRuntimeProtection attribute in the Region Definition(RD) entry for your region is different from theProtectionLevel attribute of your PPC gateway.

v on a TCP connection the RuntimeProtection attributein the RD entry for your region is different from theRuntimeProtection in the remote region’s RD entry.

v the remote system is expecting your local region tosend the user’s userid with the function shippingrequest. However, the OutboundUserIds attribute inthe Communications Definition (CD) entry sysId isset to not_sent. CICS sends the userid only ifOutboundUserIds=sent.

v the security configuration in the remote system doesnot allow the local system, or the user userId, toaccess either the mirror transaction transId or theresources specified in the function shipping request.

System action: The NOTAUTH condition is returnedto the transaction.

User response: If the user is supposed to haveauthority to access the resources on the remote systemthen check the security configuration in the localregion, remote system and, if applicable, PPC gatewayto determine why the request was unsuccessful. Referto the TXSeries Infocenter for information onconfiguring intersystem security. Correct the source ofthe problem and rerun the transaction.

ERZ027025E • ERZ027028E


Destination:

CSMT

ERZ027029E An intersystem request has abnormallyterminated with abend code ’abendCode’

Explanation: An intersystem request has abnormallyterminated. A symptom record (symrec) describing theproblem has been created and further messages can belogged.

System action: CICS abnormally terminates thetransaction with abend code abendCode.

User response: Follow the instructions given for theabend code abendCode and any additional messageslogged. If you can not solve the problem yourself, savethe CSMT log, console.msg file and the symrec file andcontact your support organization.

Destination:

CSMT

ERZ027030E Communications errorprimaryCode/secondaryCode on connectionto system ’sysId’ occurred during remotecommand command

Explanation: CICS detected a communications errorwhile processing an EXEC CICS command inconjunction with the remote system configured inCommunications Definition (CD) entry ’sysId’. The typeof error detected is described by error codeprimaryCode/secondaryCode.

System action: CICS abnormally terminates theintersystem request for the EXEC CICS command.Further messages can be logged.

User response: Refer to the TXSeries Infocenter, whichdescribes what the error code primaryCode/secondaryCode means and how to correct the problem.

Destination:

CSMT

ERZ027031E Unknown type of packet duringchannels communication over IPIC’PacketType’/’RetCode’

Explanation:

System action:

User response:

Destination:

console.msg

ERZ027032E Abort Message (IS07) received

Explanation:

System action: Transaction is aborted.

User response: Please resubmit the transaction. Ifproblem persists, contact your support rep.

Destination:

console.msg

ERZ027033E Error in importing container data to theapplication Retval = ’RetVal’

Explanation:

System action:

User response:

Destination:

console.msg

ERZ028001E The connection to the remote system’sysId’ cannot be started.Communications errorprimaryCode/secondaryCode

Explanation: CICS is unable to connect to the remotesystem configured in Communications Definition (CD)entry ’sysId’. The error is described by the return codesprimaryCode/secondaryCode.


User response: Ensure that the remote system and theconnection to it are available. See the TXSeriesInfocenter for information about the primary andsecondary return codes.

Destination:

CSMT

ERZ028002E Communications errorprimaryCode/secondaryCode detected whilecommunicating with the remote system’sysId’

Explanation: CICS received an error duringcommunications with the remote system configured inCommunications Definition (CD) entry ’sysId’. Theerror is described by the return codesprimaryCode/secondaryCode. Additional information canpossibly also be logged in a symptom record (symrec).


User response: Use the primary and secondary returncodes (primaryCode and secondaryCode respectively) todetermine the cause of the communications error. Seethe TXSeries Infocenter for information about the return

ERZ027029E • ERZ028002E


codes and the action to take.

Destination:

CSMT

ERZ028003E The Terminal Definition for terminal’termId’ on system ’sysId’ is notshippable

Explanation: A Terminal Definition (WD) entry for theterminal ’termId’ does not exist on the local system andcannot be requested from the remote system defined inCommunications Definition (CD) entry ’sysId’ becausethe terminal is defined on the remote system as notshippable.


User response: If you wish the remote system to shipterminal definitions, configure the terminal definition inthe remote system as shippable. If the remote system isCICS on Open Systems or CICS for Windows NT,version 4, set the IsShippable attribute in the relevantremote Terminal Definition (WD) entry to yes andre-install the definition. If the remote system is notCICS on Open Systems or CICS for Windows NT,version 4, consult the appropriate documentation forthe system to determine how to configure the terminaldefinition as shippable. If you do not wish to shipterminal definitions from the remote system, thencreate and install a Terminal Definition (WD) entry onyour local CICS region for the remote terminal. Formore information about defining terminals asshippable, refer to the TXSeries Infocenter.

Destination:

CSMT

ERZ028004E Transaction ’transId’, started by terminal’termId’ is part of a transaction routingloop

Explanation: CICS has routed transaction ’transId’ to aremote system and the remote system then routed thisrequest back to CICS. CICS does not continue with therequest because there is a problem with the definitionof transaction ’transId’, either in the local system or inthe remote system, which means that if CICS sends thetransaction request to the remote system system again,the remote system probably routes it back to CICS. Thisis called a transaction routing loop.


User response: If you are running the CICStransaction CRTE, ensure that you are not routing atransaction from the remote system back to the localsystem (doing so creates a loop). If the transaction isdefined as remote (see the RemoteSysId attribute in thelocal Transaction definitions (TD) entry) check thetransaction’s definition on the remote system. Ensure

that this definition does not define the transaction as aremote transaction back onto this local region (thuscreating a loop). If the remote system is CICS on OpenSystems or CICS for Windows NT, version 4, you cando this by checking the RemoteSysId attribute in therelevant TD entry on the remote system. If the remotesystem is not CICS on Open Systems or CICS forWindows NT, version 4, consult the appropriatedocumentation to find out how transactions are definedfor that system.

Destination:

CSMT

ERZ028005E Remote system ’sysId’ is unavailable torun the transaction ’transId’

Explanation:

Transaction ’transId’ is defined to be remote but thetransaction cannot be started because:

v The Communications Definition (CD) entry sysId isnot defined to your region.

v CD entry sysId is configured with attributeInService=no. This means it is out of service andunavailable for intersystem requests.

v The remote system configured in CD entry sysId cannot be contacted. This is possibly because it is notrunning or the network is unavailable or the remotesystem’s location is incorrectly configured in CDentry sysId.

v There is a problem with the configuration in yourregion which is preventing intersystem requests fromusing CD entry sysId.


User response: Examine the CICS message files(CSMT and console.msg) to determine why the remotesystem is unavailable and follow the instructions forthese messages.

Destination:


ERZ028006E Transaction ’transId’, running on system’sysId’ abnormally terminated

Explanation: Routed transaction ’transId’ abnormallyterminated on remote system configured inCommunications Definition (CD) entry ’sysId’.

System action: CICS abnormally terminates the localtransaction. The region continues.

User response: Use the procedures that areappropriate for the remote system to determine thereason for the abnormal termination of the transaction.

Destination:

CSMT

ERZ028003E • ERZ028006E


ERZ028007E The connection to the remote system’sysId’ has failed. Communications errorprimaryCode/secondaryCode

Explanation: Communications with the remote systemconfigured in Communications Definition (CD) entrysysId has stopped because of network failure or remotesystem shutdown.


User response: Ensure that the remote system and theconnection to it are available. If you require moredetailed information about the cause of this error, referto the TXSeries Infocenter for details of the primaryand secondary return codes (primaryCode andsecondaryCode respectively).

Destination:

CSMT

ERZ028008E A communications error occurred whileCICS was running transaction ’transId’routed from remote system ’sysId’

Explanation: The remote system configured inCommunications Definition (CD) entry ’sysId’ hasrequested that transaction ’transId’ is run on this localCICS region. However, while CICS was either startingtransaction ’transId’ or running transaction ’transId’, itdetected a communications error with the remotesystem.


User response: Refer to previous messages associatedwith this transaction in the CSMT log for further detailsabout the communications error. Follow the instructionsfor these messages.

Destination:

CSMT

ERZ028009E A communications error occurred duringtransaction routing of ’transId’ to theremote system ’sysId’.

Explanation: During routing of the transaction’transId’ to the remote system configured inCommunications Definition (CD) entry ’sysId’, acommunications error was detected.


User response: Refer to previous messages associatedwith this transaction in the CSMT for further detailsabout the communications error and for informationabout the action to take.

Destination:

CSMT

ERZ028010E The relay transaction on system ’sysId’has abnormally terminated whileexecuting transaction ’transId’

Explanation:

The conversation between local transaction transId anda transaction running on the remote system defined inCommunications Definition (CD) entry sysId hasabnormally terminated. Possible reasons include:

v Transaction transId is communicating with a terminalattached to the remote system and the CICS relaytransaction running on the remote system to controlthe terminal has abnormally terminated. This occursif the local transaction transId has sent a datastreamcontaining control commands (such as PRINT) thatthe remote terminal does not support.

v Transaction transId is communicating with aDistributed Transaction Processing (DTP) programthat has either abnormally terminated or called theEXEC CICS ISSUE ABEND command.


User response:

v If transaction transId is a terminal transaction whichhas been started by a transaction routing requestfrom the remote system, examine the messages in theremote system to discover why the relay transactionabnormally terminated. Follow the instructions forthese messages.

v If transaction transId is a DTP back end programwhich was started by a DTP front end program, alterthe Transaction Definitions (TD) entry for transId soIsBackEndDTP=yes.

v If transaction transId is a terminal transaction whichhas been started by a DTP front end program, alterthe DTP front end program so it starts a back endDTP program rather than transaction transId.

Once the necessary corrections have been made to theconfiguration and applications, rerun the request.

Destination:

CSMT

ERZ028011E The principal facility for the relaytransaction running transaction ’transId’is not a terminal.

Explanation: The relay transaction was startedwithout a terminal as its principal facility. The relaytransaction is a CICS-private transaction that providesthe communication mechanism between the terminaland the remote transaction ’transId’ that you areattempting to run.

System action: CICS abnormally terminates the

ERZ028007E • ERZ028011E


transaction. The region continues.

User response: Ensure that the transaction ’transId’ isbeing started from a terminal and not by anothertransaction executing ATI commands to start thetransaction.

Destination:

CSMT

ERZ028012E The transaction ’transId’ was unable torun on system ’sysId’. Communicationserror primaryCode/secondaryCode.

Explanation: The transaction ’transId’ was not able tobe started on the remote system configured inCommunications Definition (CD) entry ’sysId’ becausetransaction ’transId’ is not defined on that remotesystem.


User response: If the Transaction Definition (TD) entryfor the transaction ’transId’ has the attributeRemoteName set, check that its value is the correctname for the transaction on the remote system. Ifrequired, correct the RemoteName attribute andre-install the TD entry into the local region. If theRemoteName attribute is correct, verify that thetransaction with the name specified by the attribute isavailable on the remote system. If the RemoteNameattribute is not set, verify that the transaction with thename ’transId’ is available on the remote system. Seethe TXSeries Infocenter for information about theprimary and secondary return codes.

Destination:

CSMT

ERZ028013E Request received from system ’sysId’ toship a definition for terminal ’termId’which is not shippable

Explanation: A request to ship a terminal definitionfor terminal ’termId’ has been received from the remotesystem configured in Communications Definition (CD)entry ’sysId’. The terminal definition cannot be shippedbecause its Terminal Definition (WD) entry hasIsShippable=no. This means the terminal definitionmust not be sent to a remote system.


User response: Confirm that it is desirable for thelocal system to ship a terminal definition for theterminal ’termId’. If it is, set the IsShippable attributeof the WD entry for the terminal to yes. If it is notdesirable to ship the terminal definition for terminal’termId’ from the local system, consider adding adefinition of the terminal on the remote system. If theremote system is CICS on Open Systems or CICS for

Windows NT, version 4, this can be achieved by addinga WD entry for the terminal, with the RemoteSysIdattribute set to the name of a CommunicationsDefinition (CD) entry that defines a connection to thelocal region. Otherwise consult the appropriatedocumentation for the remote system to find out howto add the terminal definition.

Destination:

CSMT

ERZ028014E Transformer number number could notallocate storage

Explanation: CICS is unable to allocate task privatestorage for a message that is to be sent to or receivedfrom a remote system. If the transformer number is 1or 3, the storage is being allocated while encoding amessage to be sent to a remote system. If thetransformer number is 2 or 4, the storage is beingallocated while decoding a message received from aremote system.


User response: Retry the transaction when the systemis more lightly loaded or simplify the transaction sothat it uses less task private storage. Alternatively,increase the size of the task private storage pool. This isconfigured in the Region Definition (RD) entry attributeMaxTaskPrivatePool.

Destination:

CSMT

ERZ028015E Transformer number number received anincorrectly formatted message

Explanation: CICS was not able to decode a messagereceived from a remote system while transactionrouting. If the transformer number is 2, the messagewas received from a remote terminal owning region. Ifthe transformer number is 4, the message was receivedfrom a remote application owning region.


User response: If this message is displayed in theapplication owning system, verify that the remotesystem is not attempting to start a backend DistributedTransaction Processing (DTP) transaction whose localTransaction Definition (TD) entry has the attributeIsBackEndDTP set to no. If the remote system isrunning a DTP transaction then set IsBackEndDTP toyes. If this message is displayed in the terminal owningregion, verify that the remote transaction is not a backend DTP transaction. If neither of the above is the case,verify that the remote system and the connection to itare functioning normally, by performing other ISCfunctions (such as Function Shipping) to the remotesystem. If the problem persists, prepare a

ERZ028012E • ERZ028015E


communications trace showing the data received fromthe remote system and contact your supportorganization.

Destination:

CSMT

ERZ028016E Terminal Definition (WD) for terminal’termId’ is being used by anotherterminal

Explanation: CICS is unable to continue with atransaction routing request for terminal ’termId’ becausethis terminal is already in use by another transaction.This is possibly because there are two terminals withthe same name (termid), possibly owned by differentconnected CICS regions, that are running transactionson your local region.


User response: Retry the transaction. If the problempersists, consider trying to make the terminal nameunique within your connected CICS regions. This canbe achieved by modifying the program that providesthe terminal name. If the terminal owning region isCICS on Open Systems or CICS for Windows NT,version 4, this is the DFHCHATX program.Alternatively, consider creating a local WD entry for theremote terminal, specifying the RemoteName andRemoteSysId attributes so the terminal runs with adifferent name in the local region.

Destination:

CSMT


Explanation: The terminal datastream was not able tobe converted from the code page ’codePage1’ to the codepage ’codePage2’. This conversion is carried out whenencoding or decoding data that is about to be sent to,or has been received from a remote system.


User response: Ensure that the transaction is notsending terminal data which contains characters thatare not part of the character set specified by the codepage ’codePage1’. Further ensure that the transaction isnot sending terminal data which cannot be convertedfrom the code page ’codePage1’ to the code page’codePage2’. Consult the operating systemdocumentation for further details. If neither of theabove is the case, then contact your supportorganization.

Destination:

CSMT

ERZ028018E An operation on the terminal ’termId’was unsuccessful

Explanation:

A terminal related error occurred during one of thefollowing situations:

v CICS was attempting to receive data from or senddata to the terminal ’termId’

v CICS was attempting to attach the terminal ’termId’to a task


User response: Look in the CSMT and console.msg foradditional messages (of the form ERZ062nnns) givingmore information as to why the terminal operation wasunsuccessful. If the problem persists, then contact yoursupport organization.

Destination:

CSMT

ERZ028020E Transaction ’transId’ cannot install aTCTUA received from system ’sysId’ inthe Terminal Definition (WD) forterminal ’termId’

Explanation: A Terminal Control Table User Area(TCTUA) has been received whose length differs fromthe TCTUA length specified in the local WD entry forthe terminal.


User response: Consider altering the TCTUALenattribute of the local system’s WD entry for theterminal and the TCTUA length of the remote terminaldefinition so that they match. If this message isdisplayed in the transaction owning region, alsoconsider deleting the local terminal definition andallowing the remote system to ship terminal definitions.

Destination:

CSMT

ERZ028021E The nominated next transaction ’transId’could not be started

Explanation: CICS was not able to start the nexttransaction in a pseudo-conversation sequence oftransactions.


User response: Verify that the nominated transactionis defined by examining the entries in the TransactionDefinitions (TD).

Destination:

ERZ028016E • ERZ028021E


CSMT

ERZ028023E Unexpected message received fromsystem ’sysId’

Explanation: CICS received an unexpected messagefrom the remote system. This has placed theconversation with the remote system in such a statethat the transaction routing session cannot continue.


User response: If this message is displayed in theapplication owning region, verify that the remotesystem is not attempting to start a back end DistributedTransaction Processing (DTP) transaction whose localTransaction Definition (TD) entry has the attributeIsBackEndDTP set to no. If the remote system isrunning a DTP transaction, set IsBackEndDTP to yesin the local Transaction Definition (TD) entry. If thismessage is displayed in the terminal owning region,verify that the remote transaction is not a backend DTPtransaction. If neither of the above is the case, checkthat the transaction is not sending an invaliddatastream, and verify that the remote system and theconnection to it are functioning normally, byperforming other ISC functions (such as FunctionShipping) to the remote system. If the problem stillpersists, prepare a communications trace showing thedata received from the remote system and contact yoursupport organization.

Destination:

CSMT

ERZ028025E Cannot start transaction ’transId’ fromsystem ’sysId’ on the terminal ’termId’

Explanation: CICS received a request from the remotesystem configured in Communications Definition (CD)entry ’sysId’ to start the transaction ’transId’ using theterminal ’termId’. CICS is unable to proceed with therequest because the RemoteSysId attribute on theTerminal Definition (WD) entry for ’termId’ is notspecified so the terminal is defined as local.


User response:

v If you require the terminal ’termId’ to be defined aslocal to this CICS system, ensure that the remotesystem ’sysId’ ships a terminal name that is uniquewithin your connected CICS systems. If the remotesystem is CICS on Open Systems or CICS forWindows NT, version 4, this can be done bymodifying its DFHCHATX program. For moreinformation on DFHCHATX, refer to the TXSeriesInfocenter. If the remote system is not CICS on OpenSystems or CICS for Windows NT, version 4, refer tothe appropriate documentation for that system’s user

exit program that provides the terminal name.Alternatively, consider creating a local WD entry forthe terminal that is shipped from the remote system,specifying RemoteName=termId andRemoteSysId=sysId, so that the remote terminal hasa different name when it is using transactions on thelocal region.

v If the terminal ’termId’ does not need to be definedas local to this CICS region, alter the RemoteNameattribute on the terminal’s WD entry so that itspecifies the name of the Communications Definition(CD) entry for the connection to the remote system.

Refer to the TXSeries Infocenter for more informationon shipped terminals.

Destination:

CSMT

ERZ028027E Unable to route transaction ’transId’ tolocal system ’sysId’

Explanation: In the Transaction Definition (TD) entryfor transaction ’transId’ the RemoteSysId attributenames the local system. The local system’s name isspecified in the LocalSysId attribute of the RegionDefinition (RD) entry.


User response: If you wish to run the transaction’transId’ locally, do not specify anything on theRemoteSysId attribute in the TD entry. Otherwise,specify a RemoteSysId attribute in the transaction’s TDentry which is the name of a Communication Definition(CD) for a remote CICS system.

Destination:

CSMT

ERZ028029E Unsuccessful link to transaction routingUser Exit ’programName’, whentransaction routing to system ’sysId’

Explanation: CICS was not able to link to thetransaction routing User Conversion Program’programName’ when transaction routing to a remotesystem. (The default transaction routing UserConversion Program is DFHTRUC.)


User response:

1. Ensure that the Program Definition (PD) entry for’programName’ exists and that the EnableStatusattribute is set to enabled.

2. Check that the PathName attribute in the PD entryis correct (refer to the TXSeries Infocenter for moreinformation on PathName).

ERZ028023E • ERZ028029E


3. Ensure that the program specified by the PathNameattribute in the PD entry exists and is executable.

For more information on DFHTRUC refer to theTXSeries Infocenter.

Destination:

console.msg

ERZ028030E The transaction ’transId’ is unknown onthe remote system ’sysId’

Explanation: An attempt was made to run thetransaction ’transId’ on the remote system configured inCommunications Definition (CD) entry ’sysId’. This wasunsuccessful as the transaction is not defined on theremote system.


User response:

Verify that the transaction name ’transId’ is correct.

v If you wish to run transaction ’transId’ locally, setRemoteSysId=″″ in the Transaction Definition (TD)entry ’transId’.

v If you wish to run the transaction remotely, set theRemoteSysId attribute of TD entry ’transId’ to thename of a Communications Definition (CD) entrythat defines the location of the remote system onwhich you wish to run the transaction. Check thatthe transaction specified on the RemoteNameattribute in TD entry ’transId’ is available on theremote system. (If the RemoteName attribute isblank (″″), check transaction ’transId’ is available onthe remote system.)

Destination:


ERZ028031E Cannot start transaction ’transId’ on theremote system ’sysId’ because the remotesystem is out of service

Explanation: Transaction ’transId’ is defined to beremote but the transaction cannot be started becausethe remote system is out of service.


User response: Verify that the remote system issupposed to be in service. If it is, put the system backin service by setting the InService attribute of theCommunication Definition (CD) entry ’sysId’ for theremote system to yes. Re-install the CD entry andre-submit the transaction.

Destination:

CSMT

ERZ028032E Cannot install terminal definition forterminal ’termId’ shipped from system’sysId’

Explanation: CICS was not able to install a terminaldefinition for terminal ’termId’ that has been requestedfrom the system configured in CommunicationsDefinition (CD) entry ’sysId’.


User response: Consider retrying the transaction whensystem ’sysId’ is more lightly loaded. Considerincreasing the size of the task shared memory pool andthe region memory pool. This can be achieved byincreasing the values given in the MaxTSHPool andMaxRegionPool attributes of the Region Definition(RD). CICS can possibly log additional messages whichgive further information about why the operation wasunsuccessful. If the problem persists, contact yoursupport organization.

Destination:

console.msg

ERZ028033E Transaction ’transId’ cannot be run onremote system ’sysId’ because the remotesystem is unknown to CICS.

Explanation: CICS is unable to run the remotetransaction ’transId’ because the Transaction Definition(TD) entry for the transaction has the RemoteSysIdattribute set to ’sysId’ which is not the name of aCommunications Definition (CD) entry. The CD entrydefines which system to which the transaction is to berouted.


User response:

Either:

v Alter TD entry ’transId’ so the RemoteSysId attributeis set to the name of a CD entry which defines thelocation of the remote system.

v Create a CD entry called ’sysId’ which defines thelocation of the remote system.

v Alter TD entry ’transId’ so the RemoteSysId attributeis set to ″″, which means the transaction runs on thelocal CICS region.

Once all updated definitions are installed in yourregion, re-submit the transaction.

Destination:

CSMT

ERZ028030E • ERZ028033E


ERZ028034E Attempt to free COMMAREA at addressaddress failed. This is not a valid storagearea address.

Explanation: The COMMAREA passed to theTransaction Routing User Conversion Program(DFHTRUC) has been corrupted. It is likely that theCOMMAREA at address address has already beenprocessed by another FREEMAIN call.


User response: Investigate the use of FREEMAIN ofCOMMAREAs in DFHTRUC.

Destination:

CSMT

ERZ028035E Attempt to free TCTUA at addressaddress failed. This is not a valid storagearea address.

Explanation: The terminal user area (TCTUA) passedto the Transaction Routing User Conversion Program(DFHTRUC) has been corrupted. It is likely that theTCTUA at address address has already been processedby another FREEMAIN call.


User response: Investigate the use of FREEMAIN ofTCTUAs in DFHTRUC.

Destination:

CSMT

ERZ028036E Serious storage problem encounteredwith region storage.

Explanation: CICS is unable to get storage in which tobuild a list of remote system identifiers to which theTerminal Definition (TD) has been shipped. This islikely to be just one manifestation of a much moreserious problem.


User response: Look on the console for associatedmessages and take the actions recommended to resolvethe problem.

Destination:

CSMT

ERZ028038E Unexpected communications errorprimaryCode/secondaryCode onconversation with system ’sysId’ whilerunning transaction ’transId’

Explanation: CICS detected an unexpected conditionwhile communicating with the remote systemconfigured in Communications Definition (CD) entry’sysId’ and is therefore unable to continue with the

transaction transId. If the local CICS system is theterminal owning region, then ’transId’ is the name ofthe remote transaction running on the applicationowning region ’sysId’. If the local CICS system is theapplication owning region, then ’transId’ the name ofthe local transaction which has been transaction routedfrom the terminal owning region ’sysId’ to the localCICS system.

System action: CICS abnormally terminates thetransaction with code A28M.

User response: Refer to the TXSeries Infocenter fordetails of the return codes and the action to take.Ensure that the versions of software used by your CICSregion are compatible. Also check that the softwarerunning on the remote system is compatible with yourlocal CICS region. If the remote system is connected toyour CICS region via a PPC Gateway and a SystemsNetwork Architecture (SNA) network then check thatthe version of the PPC gateway is compatible with theversions of CICS used by your local region. If you findthat the software used by the communicating systemsis incompatible then install the correct versions. Try thetransaction again. If the problem persists, contact yoursupport organization.

Destination:

CSMT

ERZ028039I Terminal ’termId’ no longercommunicating; netname ’netName’.

Explanation: A terminal can no longer be contacted bythe region.

System action: The region no longer tries tocommunicate with the terminal and frees up thenetname for future use by another terminal program.

User response: None

Destination:

CSMT

ERZ028040E Transaction ’transId’ cannot be onwardrouted as it is defined as dynamic in anintermediate system.

Explanation: A dynamic transaction can only bestarted in the terminal owning system. A dynamictransaction cannot exist on an intermediate system.

System action:

User response: Ensure that dynamic transactions areonly invoked in the terminal owning system. Ensurethat the local transaction definition does not specifythat the transaction is dynamic.

Destination:

console.msg

ERZ028034E • ERZ028040E


ERZ028041E Intersystem request received fortransaction ’transId’ was unsuccessfulbecause the TD entry is configuredincorrectly for this type of request.

Explanation: CICS is unable to accept an intersystemrequest for transaction ’transId’ because the TransactionDefinition (TD) entry is incompatible with the receivedrequest. The received request indicates that the remotesystem issued either a function ship, DistributedProgram Link (DPL) or Distributed TransactionProcessing (DTP) request.

System action: The intersystem request fails. Furthermessages can possibly be logged and the requestterminated abnormally.

User response: Check the type of intersystem requestis compatible with the TD entry ’transId’. If the requestwas for DPL and the user program specifies aTRANSID for transaction ’transId’, check that this namedoes not conflict with the name of an already definednon-DPL transaction. If the request was for functionship or DPL, ensure the TD entry has the attributeProgram set to DFHMIRS. If the request was DTP,ensure the TD entry has the attribute IsBackEndDTPset to yes.

Destination:

CSMT





Destination:

console


Explanation:

Data for a function shipping request was not able to beconverted between code page ’codePage1’ and codepage ’codePage2’ because:





User response: Ensure the data being sent or receivedas part of the function shipping request is valid forcode pages codePage1 and codePage2. If not, youpossibly need to use the function shipping userconversion exit (DFHUCNV) to convert the data. Referto the TXSeries Infocenter for more information. Ensurethe conversion routines for code pages codePage1 andcodePage2 are correctly installed. Some operatingsystems allow you to define you own conversionroutines using the genxlt utility. If the conversionroutine is user-defined then ensure it is correct. Consultthe operating system documentation on iconv andgenxlt for further details. If you are unable to solve thisproblem yourself, contact your support organization.

Destination:

CSMT

ERZ028044E Incorrectly formatted message received

Explanation: CICS was not able to decode a messagereceived from a remote system while function shipping.


User response: Ensure that the remote system is notexecuting a Distributed Transaction Processing (DTP)transaction. If it is, modify the transaction and/or itsresource definitions, so that it does not execute as thefunction shipping mirror transaction, or does notallocate conversations to the function shipping mirrortransaction. If this is not the case, verify that the remotesystem and the connection to it are functioningnormally by performing other intersystemcommunication functions (such as transaction routing)to the remote system. If the problem persists, prepare acommunications trace showing the data received fromthe remote system and contact your supportorganization.

Destination:

CSMT

ERZ029001E DTP conversation convId with sysId fortransId abnormally terminated withEIBERRCD code ’errorCode’.

Explanation: Transaction transId has received anabnormal response errorCode from system sysId for theDistributed Transaction Processing (DTP) conversationconvId. This can possibly be caused by the remoteprogram terminating before closing down theconversation or calling EXEC CICS ISSUE ABEND.Alternatively, there is possibly a problem with theconfiguration in the network or remote system which is

ERZ028041E • ERZ029001E


preventing the remote program from starting. Themeaning of errorCode is described in TXSeriesInfocenter. Further information on the errorCode can befound under ″15a00007/errorCode″ in TXSeriesInfocenter. For example, if errorCode is ’080f6051’, lookfor the description of error code ″15a00007/80f6051″.The DTP conversation can no longer be used and theapplication must issue a FREE command for theconversation.

System action: CICS sets the errorCode in theEIBERRCD field of the EXEC interface block (EIB) andreturns TERMERR condition code to the applicationprogram.

User response: Use the information in TXSeriesInfocenter to determine the meaning of errorCode andthe action to take. Also look for error messages in theremote system that also describe any changes requiredto the remote system. Once the cause of the problemhas been removed, rerun the transaction.

Destination:

CSMT

ERZ029002E Unsuccessful memory allocationrequest.″

Explanation: A Distributed Transaction Processing(DTP) command was unable to obtain sufficient taskprivate storage to continue.

System action: CICS abnormally terminates thetransaction with code A29B.

User response: Run the transaction again. If theproblem persists, increase the size of the task privatepool by changing the value of the MaxTaskPrivatePoolattribute in your region’s Region Definition (RD) entryand restart CICS.

Destination:

CSMT

ERZ029004E transId used an unrecognized SYSID’sysId’ on an ALLOCATE command.

Explanation: Transaction transId specified SYSID’sysId’ on the SYSID parameter of the ALLOCATEcommand but this SYSID is not the name of aCommunications Definition (CD) entry. Without a CDentry, CICS does not know which remote system tocontact.

System action: CICS returns the SYSIDERR conditioncode to the application program.

User response:

Either modify the application program to use the nameof a CD entry on the SYSID parameter of theALLOCATE command or add a new CD entry for theSYSID used by the application program. If you needmore information:

v TXSeries Infocenter

v TXSeries Infocenter

Destination:

CSMT

ERZ029005E transId issued commandName onconversation convId which is in stateconversationState.

Explanation: Transaction transId issued the commandcommandName on a Distributed Transaction Processing(DTP) conversation convId. This was unsuccessfulbecause the conversation’s state conversationState doesnot permit the command to be issued. This is causedby a programming error in the application program.

System action: CICS abnormally terminates thetransaction with code ATCV.

User response: Correct the application program usingthe information in TXSeries Infocenter that explainshow to write DTP programs. TXSeries Infocenterdescribes which commands are allowed in eachconversation state and the commands to issue tochange the conversation to the state required by yourapplication.

Destination:

CSMT

ERZ029006E transId used ISSUE PREPARE onconversation convId which is atsynchronization level syncLevel.

Explanation: Transaction transId made a call to theISSUE PREPARE command that was unsuccessfulbecause the conversation convId was not asynchronization level 2 (syncpoint) conversation. This isan application programming error because ISSUEPREPARE is used to send a syncpoint request to aremote system and so is permitted only on asynchronization level 2 conversation.

System action: CICS returns the INVREQ conditioncode to the application program.

User response: Modify the application program sothat either it no longer uses the ISSUE PREPAREcommand or it starts using a synchronization level 2conversation. The synchronization level of aconversation is set by the SYNCLEVEL parameter ofthe CONNECT PROCESS. The TXSeries Infocenterdescribes how to write programs that usesynchronization level 2 conversations. The TXSeriesInfocenter describes the CONNECT PROCESS andISSUE PREPARE commands.

Destination:

CSMT

ERZ029002E • ERZ029006E


ERZ029007E transId did not pass a conversationidentifier on a commandName command.

Explanation: The commandName command issued bythe transaction transId was unsuccessful because it didnot have a CONVID parameter specified and itsprincipal facility is not a Distributed TransactionProcessing (DTP) conversation. For example, this errormessage possibly occurs if a DTP backend program isinvoked from a terminal.


User response: Check that transId was startedcorrectly. If it was, modify the application program so itspecifies the conversation identifier for the DTPconversation using the CONVID option of thecommandName command. The conversation identifiermust be extracted from the EIBRSRCE field of theEXEC Interface Block (EIB) structure returned by thesuccessful EXEC CICS ALLOCATE command. Furtherinformation on the conversation identifier can be foundin the TXSeries Infocenter.

Destination:

CSMT

ERZ029008E Unexpected communications errorprimaryCode/secondaryCode for transId onconversation convId to system sysIdwhile processing the commandNamecommand.

Explanation: CICS detected an unexpected conditionwhile processing the commandName command and isunable to continue with the transaction transId. TheTXSeries Infocenter describes the communications errorcodes that appear in this message and the actions totake to resolve them.

System action: CICS abnormally terminates thetransaction with code A29C.

User response: Ensure that the versions of softwareused by your CICS region are compatible. Also checkthat the software running on the remote system iscompatible with your local CICS region. If the remotesystem is connected to your CICS region via a PPCGateway Server and a Systems Network Architecture(SNA) network, check that the version of the PPCGateway Server is compatible with the versions ofCICS used by your local region. If you find that thesoftware used by the communicating systems isincompatible, install the correct versions. Try thetransaction again. If the problem persists, contact yoursupport organization.

Destination:

CSMT

ERZ029009E transId called ISSUE PREPARE onconversation convId which is in stateconversationState.

Explanation: Transaction transId issued the commandISSUE PREPARE on a Distributed TransactionProcessing (DTP) conversation convId. This wasunsuccessful because the conversation’s stateconversationState does not permit the command to beissued. This is caused by a programming error in theapplication program.


User response: Correct the application program usingthe information in the TXSeries Infocenter, whichexplains how to write 2 DTP programs that usesynchronization level 2 conversations. The TXSeriesInfocenter describes which commands are allowed ineach conversation state and the commands to issue tochange the conversation to the state required by yourapplication.

Destination:

CSMT

ERZ029010E transId called commandName onsynchronization level 0 conversationconvId.

Explanation: Transaction transId issued a SENDcommand using the CONFIRM option on conversationconvId when the synchronization level of thisconversation is 0 (none). This is an applicationprogramming error because CICS requires thesynchronization level of the conversation to be 1(confirm) or 2 (syncpoint) if the CONFIRM option ofthe SEND command is to be used.


User response: Modify the application program sothat either it no longer uses the CONFIRM option ofthe SEND command or it starts using a synchronizationlevel 1 or 2 conversation. The synchronization level of aconversation is set by the SYNCLEVEL parameter ofthe CONNECT PROCESS. The TXSeries Infocenterdescribes how to write Distributed TransactionProcessing (DTP) programs. The TXSeries Infocenterdescribes the SEND command.

Destination:

CSMT

ERZ029011W transId issued the RETURN commandwhile conversation convId is in stateconversationState.

Explanation: Transaction transId has issued a RETURNcommand which causes the transaction to rollbackbecause Distributed Transaction Processing (DTP)

ERZ029007E • ERZ029011W


conversation convId is in state conversationState. Thismeans that CICS cannot send a syncpoint request to theremote system on that conversation. This is anapplication programming error.

System action: CICS abnormally terminates thetransaction with code A30A.

User response: Correct the application program usingthe information in the TXSeries Infocenter that explainshow to write DTP programs that use synchronizationlevel 2 conversations. The TXSeries Infocenter describeswhich commands are allowed in each conversationstate and the commands to issue to change theconversation to the state required by your application.

Destination:

CSMT

ERZ029012E transId received transaction routing orfunction shipping data from systemsysId on conversation convId.

Explanation: CICS received data from system sysIdwhich is flagged as transaction routing or functionshipping data. (The Generalized Data Stream (GDS) IDis 0x12F2 rather than 0x12FF.) This indicates there is amismatch between the local transaction transId and theremote program it is communicating with onconversation convId. The local transaction can be aDistributed Transaction Processing (DTP) program thathas requested a program on the remote system and theremote system has misinterpreted this as a transactionrouting or a function shipping request. Alternatively,the remote system possibly issued a transaction routingor function shipping request that the local regionmistakenly interpreted as a request to start a backendDTP program.

System action: CICS abnormally terminates thetransaction with code A29D.

User response: Look at the transaction transId. If it isnot a DTP program, ensure that the IsBackEndDTPattribute of the Transaction Definition (TD) entry fortransId is set to no. If transId is a DTP program thatstarts the conversation convId with system sysId, checkthat the program requested on the PROCNAMEparameter of the CONNECT PROCESS command is setup on the remote system as a DTP backend program.Finally, if transId was invoked by an intersystemrequest from the remote system, determine how it wasstarted. It is possible that transId is defined in systemsysId as a remote transaction and it has been invokedfrom a terminal connected to system sysId. If this is thecase, request that the definition for transId is eitherremoved from system sysId, or altered so thattransaction routing requests for transId are not sent tothe local region.

Destination:

CSMT

ERZ029013E transId specified synchronization levelsyncLevel on a CONNECT PROCESScommand for conversation convId.

Explanation: Transaction transId specified anunsupported synchronization level syncLevel on theSYNCLEVEL parameter of a CONNECT PROCESScommand. CICS supports synchronization levels of 0(None), 1 (Confirm) and 2 (Syncpoint). The CONNECTPROCESS command was issued on conversation convId.


User response: Correct the application program torequest a valid synchronization level on the CONNECTPROCESS command. Further information on theCONNECT PROCESS command can be found inTXSeries Infocenter.

Destination:

CSMT

ERZ029014E transId specified null PIP data on aCONNECT PROCESS command forconversation convId.

Explanation: transId specified a null for the PIPLISTparameter of the CONNECT PROCESS command. Thisis an application programming error. The PIPLISTparameter allows an application to send ProcessInitialization Parameter (PIP) data to a remote program.An application must either omit the PIPLIST andPIPLENGTH parameters from the CONNECTPROCESS command or pass valid PIP data and thelength of this PIP data in the PIPLIST and PIPLENGTHparameters respectively.


User response: Modify the application program to usethe PIPLIST and PIPLENGTH parameters of theCONNECT PROCESS command correctly. TXSeriesInfocenter describe the CONNECT PROCESScommand.

Destination:

CSMT

ERZ029015E transId did not pass a transaction nameon a CONNECT PROCESS commandfor conversation convId.

Explanation: Transaction transId specified a null forthe PROCNAME parameter of the CONNECTPROCESS command. This is an applicationprogramming error. The PROCNAME parameterspecifies the transaction name of the program on theremote system that transId is to communicate with.CICS needs the transaction name to send a request tothe remote system to start the remote program.

ERZ029012E • ERZ029015E



User response: Modify the application program tospecify correctly the transaction name of the programthat is to be started on the remote system. TXSeriesInfocenter describe the PROCNAME parameter of theCONNECT PROCESS command.

Destination:

CSMT

ERZ029016E transId passed dataLength bytes to thecommandName command on conversationconvId.

Explanation: transId issued a commandName commandon conversation convId which specified the length ofdata to be sent as dataLength. This is an applicationprogramming error as CICS does not allow more than32767 bytes to be sent on a DTP conversation in asingle commandName command.

System action: CICS returns the LENGERR conditioncode to the application program.

User response: Modify the application program sothat it sends data in blocks that are not greater than32767 bytes long. The TXSeries Infocenter describeshow to send data on DTP conversations.

Destination:

CSMT

ERZ029017E transId specified an unrecognizedconversation identifier convId on thecommandName command.

Explanation: The conversation identifier convIdspecified on the CONVID parameter of thecommandName command is not the identifier of a DTPconversation owned by the transaction transId. This isan application programming error.

System action: CICS returns the NOTALLOCcondition code to the application program.

User response: Correct the application program sothat it passes a valid conversation identifier to CICS. Ifthe application program started the conversation usingan ALLOCATE command the conversation identifiercan be extracted from the EIBRSRCE field in the EXECInterface Block (EIB) structure returned by thesuccessful ALLOCATE command. If the applicationprogram was started with the DTP conversation as itsprincipal facility, the conversation identifier can beobtained using the ASSIGN FACILITY command. TheTXSeries Infocenter describes how to obtain theconversation identifier for DTP programs. The TXSeriesInfocenter describes the ASSIGN FACILITY command.

Destination:

CSMT

ERZ029019E transId specified PROCLENGTH lengthon a CONNECT PROCESS commandfor conversation convId.

Explanation: Transaction transId passed anunsupported length length on the PROCLENGTHparameter of a CONNECT PROCESS command. Thetransaction name specified on the CONNECTPROCESS command is the name of the program in theremote system that transId is to communicate with.CICS supports transaction names that are between 1and 32 bytes long. The CONNECT PROCESS commandwas issued on conversation convId.


User response: First check that the applicationprogram is specifying the correct length for the remotetransaction name. Modify the application if this isincorrect. If the length of the remote transaction nameis defined to be greater than 32 bytes long, it must bechanged in the remote system so that its length issupported by CICS. Then the local application programmust be modified to use this new remote transactionname on the CONNECT PROCESS command. TheTXSeries Infocenter describe the CONNECT PROCESScommand.

Destination:

CSMT

ERZ029020E transId issued a commandName commandon synchronization level 2 conversationconvId.

Explanation: Transaction transId issued thecommandName command on a synchronization level 2(syncpoint) conversation. This is an applicationprogramming error as commandName closes down theconversation and prevent CICS from sending syncpointmessages to the remote system when the nextSYNCPOINT or RETURN command is issued by theapplication. This can possibly leave recoverableresources in an inconsistent state if a failure occurs. Theproper way to close down a synchronization level 2conversation is to issue a SEND LAST command andthen a SYNCPOINT command. This enables bothsystems to commit the updates made by yourapplication before the conversation is closed down.Alternatively, if your application is in the middle oferror processing and does not want the changes itmade to be committed, the application must call theISSUE ABEND command and then the SYNCPOINTROLLBACK command. Then all the recoverablechanges made by the application are rolled back(undone).


User response:

ERZ029016E • ERZ029020E


Modify your application program in one of thefollowing ways:

v Change the conversation synchronization level to be0 (none) or 1 (confirm). The synchronization level ofthe conversation is specified in the SYNCLEVELparameter of the CONNECT PROCESS command.

v Change the logic that closes down the conversationto use the SEND LAST and SYNCPOINT commands.

v Change the logic that closes down the conversationto use the ISSUE ABEND and SYNCPOINTROLLBACK commands.

The TXSeries Infocenter describes how to write DTPprograms.

Destination:

CSMT

ERZ029021E CICS abnormally terminated transId dueto communications errorprimaryCode/secondaryCode onconversation convId that occurred duringthe commandName command.

Explanation: Transaction transId is being abnormallyterminated due to a communications error detected onconversation convId which makes it impossible tocontinue with the transaction.

System action: CICS abnormally terminates thetransaction with code A29A.

User response: The TXSeries Infocenter describes thecommunications error codes that appear in thismessage and the actions to take to resolve them. Thiserror can be transient, so rerun the transaction to see ifthe problem has gone away. If the problem persists,however, and you need more help resolving it, contactyour support organization.

Destination:

CSMT

ERZ029022E Unexpected synchronization levelsyncLevel detected while starting abackend DTP program ’transId’ fromsystem ’systemName’.

Explanation: CICS was starting a backend DistributedTransaction Processing (DTP) program when it detectedan unexpected synchronization level value. CICScannot proceed with the transaction.


User response: Ensure that the versions of softwareused by your CICS region are compatible. Also checkthat the software running on the remote system iscompatible with your local CICS region. If the remotesystem is connected to your CICS region via a PPCGateway Server and a Systems Network Architecture

(SNA) network, check that the version of the PPCGateway Server is compatible with the versions ofCICS used by your local region. If you find that thesoftware used by the communicating systems isincompatible, install the correct versions. Retry thetransaction. If the problem persists, contact yoursupport organization.

Destination:

CSMT

ERZ029023E The transaction has abnormallyterminated with code A29C.

Explanation: CICS was starting a backend DistributedTransaction Processing (DTP) program when it detectedan unexpected synchronization level value. CICScannot proceed with the transaction.


User response: Search for message ERZ2922E in theCSMT log as this gives details of the synchronizationlevel value, DTP transaction name and originatingsystem. Refer to the description of message ERZ2922Efor information on how to correct the problem.

Destination:

CSMT

ERZ029024E transId specified PIP data lengthdataLength on a CONNECT PROCESScommand for conversation convId.

Explanation: transId specified a value of dataLength inthe PIPLENGTH parameter of the CONNECTPROCESS command. This is an applicationprogramming error as the PIPLENGTH parameter mustreflect the length of the Process Initialization Parameter(PIP) data specified in the PIPLIST parameter. Theminimum length for PIP data is 4.


User response: Modify the application program to usethe PIPLIST and PIPLENGTH parameters of theCONNECT PROCESS command correctly. The TXSeriesInfocenter describe the CONNECT PROCESScommand.

Destination:

CSMT

ERZ029025E transId passed PIP data that does notmatch PIP length length on a CONNECTPROCESS command for conversationconvId.

Explanation: Transaction transId specified a value oflength in the PIPLENGTH parameter of the CONNECT

ERZ029021E • ERZ029025E


PROCESS command. This does not correspond to thelengths specified in the fields of the ProcessInitialization Parameter (PIP) data passed on thePIPLIST parameter of the CONNECT PROCESScommand. This is an application programming error asthe PIPLENGTH parameter must reflect the length ofthe Process Initialization Parameter (PIP) data specifiedin the PIPLIST parameter.



Destination:

CSMT

ERZ029026E transId passed PIP data that containsinvalid length fields on a CONNECTPROCESS command for conversationconvId.

Explanation: Transaction transId specified ProcessInitialization Parameter (PIP) data on the PIPLISTparameter of the CONNECT PROCESS commandwhich contains one or more length fields which are notbetween 4 and 32767. This is an applicationprogramming error.



Destination:

CSMT

ERZ029027E The modename ’modeName’ used bytransId is unrecognized by system sysId.

Explanation:

Transaction transId requested a DTP conversation withthe remote system configured in CommunicationsDefinition (CD) entry sysId. However, this request wasunsuccessful as either the local SNA product or theremote system is not configured with the modenameused for the request. The modename was specified inthe PROFILE option of the EXEC CICS ALLOCATESYSID(sysId) PROFILE(modeName) command. Thisproblem can possibly be caused because:

v The modename has been specified incorrectly by theapplication.

v The CD entry sysId is not configured with the correctremote system information in the RemoteLUName,RemoteNetworkName and SNAConnectNameattributes.

v The local SNA product does not have the modenamemodeName defined.

v The local SNA product does not have the remotesystem correctly defined.

v The remote system does not have the modenamemodeName defined.

v The definition of modename modeName in the localSNA product is inconsistent with the definition ofthis modename in the remote system.

System action: CICS returns the SYSIDERR conditioncode to the application program on the EXEC CICSCONNECT PROCESS command.

User response:

Examine CD entry sysId and the SNA configuration inyour local SNA product and the remote system. You arelooking for inconsistencies within this configuration.Ensure that:

v The modename used in the application is correctlyconfigured in both the local SNA product and theremote system.

v CD entry sysId specifies the correct remote system.Check the settings of the RemoteLUName,RemoteNetworkName and SNAConnectNameattributes.

v The configuration in the local SNA product for theremote system is correct and complete. Take specialcare that any partner LU aliases defined correctlymap to the name of the remote system. Also checkthat where partner LU aliases are required, they aredefined.

Once any necessary corrections have been made, rerunthe request. The TXSeries Infocenter provides moreinformation on the use of modenames by CICS. TheTXSeries Infocenter describes the EXEC CICSALLOCATE command.

Destination:

CSMT

ERZ029028E transId is unable to contact system sysId.

Explanation: Transaction transId requested a DTPconversation with system sysId. However, this requestwas unsuccessful as system sysId is currentlyunavailable.

System action: CICS returns the SYSIDERR conditioncode to the application program.

User response: The sysId given in the message is thename of the Communications Definition (CD) entry forthe remote system. Look at this CD entry to find outthe full name of the remote system that is unavailable.

ERZ029026E • ERZ029028E


Check that this is the name of a valid system. If it isnot, correct the CD entry and retry transId. If the CDentry is correct, investigate why the remote system isdown. If you find that the remote system is available,check that the network is available and, if appropriate,also ensure that PPC Gateway Server and SNA productare running. Once the remote system and theintermediate network are available retry transactiontransId. The TXSeries Infocenter provides moreinformation on detecting the causes ofintercommunication failures.

Destination:

CSMT

ERZ029029E transId is unable to use synchronizationlevel syncLevel on a conversation tosystem sysId.

Explanation: Transaction transId requested a DTPconversation with system sysId. However, this requestwas unsuccessful as the communications method usedto contact system sysId does not supportsynchronization level syncLevel.


User response:

There are 2 possible causes for this error.

v The communications method does not support thesynchronization level requested by transId. If this isthe case, modify the application program to use asynchronization level that is supported.

v There is possibly be a temporary failure that iscausing the synchronization level to be unavailable.For example, if the transaction is usingsynchronization level 2 (syncpoint) across SNA andthe PPC Gateway Server is unable to exchange lognames with the remote system, synchronization level2 are unavailable to the remote system until theexchange log names problem is resolved. Use theerror messages from the PPC Gateway Server andthe information in the TXSeries Infocenter to resolvethe exchange log names problem.

Correct the problem and retry the request.

Destination:

CSMT

ERZ029030I transId rolled back due to receipt ofcommunications error errorCode onconversation convId to system sysId.

Explanation: Transaction transId issued a SYNCPOINTor RETURN command which resulted in thetransaction rolling back. The cause of this rollback ispossibly the communications error errorCode which wasreceived on the synchronization level 2 conversation

convId just before the SYNCPOINT or RETURNcommand was issued. CICS was unable to report thecommunications error to the application as theapplication did not issue an EXEC CICS command onthis conversation between receipt of thecommunications error and the SYNCPOINT orRETURN command. errorCode is the value that was tohave been returned to the application in the EIBERRCDfield of the EXEC Interface Block (EIB). The TXSeriesInfocenter documents the meaning of all validEIBERRCD codes.

System action: CICS rolls back (backs out) therecoverable work done by the transaction.

User response: No action is required, this message isfor information only.

Destination:

CSMT

ERZ029031E transId sent data using the commandNamecommand on conversation convId whichis in state conversationState.

Explanation: Transaction transId issued thecommandName command with the FROM option on aDistributed Transaction Processing (DTP) conversationconvId. The FROM option requests CICS to send dataon the conversation. The commandName command wasunsuccessful because the state conversationState does notpermit CICS to send data. This is a programming errorin the application program.

System action: CICS abnormally terminates thetransaction with code ATCV.

User response: Correct the application program usingthe information in the TXSeries Infocenter that explainshow to write DTP programs. The TXSeries Infocenterdescribes which commands are allowed in eachconversation state and the commands to issue tochange the conversation to the state required by yourapplication.

Destination:

CSMT

ERZ030001I CD entry sysId has been set up for thelocal region

Explanation: CICS has added a CommunicationsDefinition (CD) entry for the local region as part ofregion initialization. The SYSID for this CD entry, sysId,is defined in the LocalSysId attribute of the RegionDefinition (RD).


User response: None

Destination:

console.msg

ERZ029029E • ERZ030001I


ERZ030002W The local SYSID for this region is null

Explanation: The LocalSysId attribute of the RegionDefinition (RD) entry is null (″″). This means thatintersystem requests can not be issued by transactionsrunning on your region. In addition, your region willnot be able to receive intersystem requests.

System action: CICS continues processing. However,all intersystem requests will fail.

User response: If your transactions are to issueintersystem requests set the LocalSysId attribute of theRD entry. This must be between 1 and 4 characterslong. Once the LocalSysId attribute of the RD entry isconfigured restart your region so that the new valuecan take effect.

Destination:

console.msg

ERZ030003W A CD entry for the local SYSID ’sysId’exists and is being ignored

Explanation: The Communications Definition (CD)entry ’sysId’ has the same name as your region’s localSYSID defined in the Region Definition (RD) entryattribute LocalSysId.

System action: CICS continues processing. CD entry’sysId’ will be ignored and is not available forintersystem communication.

User response:

If CD entry sysId is required for intersystem requestsmodify either the LocalSysId attribute of the RD, or thename of the CD entry so that these two values aredifferent.

Note: If you modify the LocalSysId attribute, you mustrestart your CICS region before this value willtake effect. If you modify the name of the CDentry ensure that the updated CD entry isinstalled in your CICS region. The TXSeriesInfocenter describes how to make changes to CDentries.

Destination:

console.msg

ERZ030004I Using LUname as the default SNA localLU name

Explanation: CICS will use LUname as its default localLogical Unit (LU) name. The local LU name is thename that remote systems use to contact your regionacross a Systems Network Architecture (SNA) network.This LU name is normally defined in theLocalLUName attribute of the Region Definition (RD).If, however, LocalLUName=″″, CICS will use the regionname as the default local LU name.


User response: None

Destination:

console.msg

ERZ030005W The default SNA local LU name LUnamecontains unsupported characters

Explanation:

The default local Logical Unit (LU) name for this regionLUname contains characters that are not supported bythe Systems Network Architecture (SNA). The LU namemust be no more than eight characters long. The firstcharacter of this field must be an upper case alphabeticcharacter (A-Z) and the subsequent characters must beeither upper case alphabetic characters or numeric (0-9).For example, the following values are valid for thelocal LU name:

v ″A″

v ″CICS1″

v ″OPENCICS″

v ″MYLU″

and the following values are invalid.

″9″ Begins with a number

″1CICS″Begins with a number

″OPENcics″Contains lower case alphabetic characters

″MY-LU″Contains the unsupported character ’-’

System action: CICS continues processing. SNAintersystem requests will fail.

User response: Modify the LocalLUName attribute ofthe RD so that it contains a valid SNA LU name. Thenrestart your region so that the new local LU name takeseffect.

Destination:

console.msg

ERZ030006I PPC gateway GDname will use LUnameas the SNA local LU name

Explanation: The PPC gateway defined in GatewayDefinition (GD) GDname will use local Logical Unit(LU) name LUname for your region whencommunicating with remote systems across a SystemsNetwork Architecture (SNA) network. The local LUname is the name that these remote systems use tocontact your region. It is defined in theGatewayLUName attribute of the GD. IfGatewayLUName=″″ the PPC gateway will use thevalue in the LocalLUName attribute of the Region

ERZ030002W • ERZ030006I


Definition (RD). (If LocalLUName=″″ it will default tothe name of your region.)


User response: None

Destination:

console.msg

ERZ030007E An inconsistency has been detected in aCICS internal data structure


System action: The region continues, but intersystemscommunication can possibly be unsuccessful.

User response: Restart your region. If the conditionpersists, perform a system dump and contact yoursupport organization.

Destination:

console.msg

ERZ030008E Communications errorprimaryCode/secondaryCode preventsintersystem request for transaction’transId’ from starting

Explanation: CICS was unable to start transactiontransId. This transaction was requested by a remotesystem as part of an intersystem request. The errorcodes primaryCode/secondaryCode describe the reason forthe failure.


User response: Look for additional messages thatexplain the cause of the error and follow theinstructions associated with these messages. TheTXSeries Infocenter provides information about thecommunications error codes primaryCode/secondaryCode.

Destination:

console.msg

ERZ030010W Unsuccessful syncpoint for transactiontransactionNumber - the transaction isrolled back

Explanation: A participant of transactiontransactionNumber, has requested a backout, or hasabnormally terminated, in response to a syncpointrequest. It is also possible that the local transaction wasforcibly terminated during syncpoint processing. Theparticipant was possibly a synclevel syncpoint PPCconversation, a Structured File System (SFS) server, oran XA database server. If the local transaction executedan explicit syncpoint (using EXEC CICS SYNCPOINT),the local transaction, and all of its participants are

rolled back. If CICS executed an implicit (end oftransaction) syncpoint, the local transaction, and all ofits participants are abnormally terminated.

System action: The transaction abnormally terminates,or is rolled back.

User response: Investigate the transaction participants,using procedures appropriate to each, in order todetermine which of them requested the backout, orabnormally terminated, and why it did so.

Destination:

CSMT

ERZ030011W Unsuccessful syncpoint for transactiontransactionNumber - some processingbacked out

Explanation: CICS has detected heuristic damagewhen performing syncpoint processing for transactiontransactionNumber. This means that some participants ofthe transaction have been committed, while others havebeen backed out. The participants involved can besynclevel syncpoint PPC conversations, Structured FileSystem (SFS) servers, or XA database servers.


User response: Use the procedures appropriate to theparticipant systems to determine why heuristic damagewas reported. The participant systems possibly requiremanual intervention to synchronize resources that havebeen either rolled back or committed.

Destination:

CSMT

ERZ030013W Unsuccessful syncpoint for transactiontransactionNumber. PPC error codeerrorCode (errorString)

Explanation: A PPC error was reported when the localtransaction executed a syncpoint or syncpoint rollback.


User response: Examine the CICS message files foradditional information on why the syncpoint orsyncpoint rollback was unsuccessful. If your transactionis executing Distributed Transaction Processing (DTP)commands and the message indicates that PPCdetected a state error on one of its conversations,examine your transaction and ensure that all of itssynclevel syncpoint conversations are in theappropriate state to execute a syncpoint.

Destination:

CSMT

ERZ030007E • ERZ030013W


ERZ030018W The LD entry ’LDname’ referenced byCD entry sysId is not configured forTCP/IP

Explanation: Communications Definition (CD) entrysysId has ConnectionType=cics_tcp andListenerName=LDname. The ListenerName attributemust therefore be configured with the name of aListener Definition (LD) entry which has Protocol=TCP.However, LD entry LDname does not haveProtocol=TCP configured.

System action: Intersystem requests using CD entrysysId will fail.

User response:

Examine the CD entry sysId. If the ConnectionType iscics_tcp, either:

v Alter LD entry LDname so that Protocol=TCP andthe other attributes are correctly configured for CICSfamily TCP/IP.

or

v Alter CD entry LDname so that the ListenerNameattribute is set to the name of a CICS family TCP/IPLD entry.

The TXSeries Infocenter describes the LD and CDentries required for CICS family TCP/IP support andhow to install these entries in your CICS region.

Destination:

console.msg

ERZ030019W The LD entry ’LDname’ referenced byCD entry sysId does not exist

Explanation: Communications Definition (CD) entrysysId has ListenerName=LDname. This attribute mustbe configured with the name of a Listener Definition(LD) entry which has Protocol=TCP. However, LDentry LDname is not configured in your region.

System action: Intersystem requests using CD entrysysId will fail.

User response:


v Configure a CICS family TCP/IP LD entry calledLDname in your region.

or

v Alter CD entry sysId so that the ListenerNameattribute is set to the name of a CICS family TCP/IPLD entry.

The TXSeries Infocenter describes the LD and CDentries required for CICS family TCP/IP support andhow to install these entries in your CICS region.

Destination:

console.msg

ERZ030020E Unable to add a PPC alias ’alias’ of typealiasType and name ’DCEname’ for CDentry sysId. The error code was errorCode(errorString).

Explanation: CICS issued a PPC function call toconfigure PPC with details of the remote systemdescribed in Communications Definition (CD) ’sysId’.However this failed with the error code errorCode.

System action: The current intersystem request fails.Further messages can be logged.

User response: Check that the versions of PPC andCICS installed on your machine are compatible. If theyare not compatible install the correct versions. If youcan not solve this problem contact your supportorganization.

Destination:

console.msg

ERZ030021E The GD entry ’GDname’ referenced byCD entry sysId does not exist

Explanation: An intersystems request wasunsuccessful because the Systems Network Architecture(SNA) Communications Definition (CD) entry sysIdreferences the Gateway Definition (GD) entry GDnamein the GatewayName attribute. However, the GD entryGDname does not exist. CICS requires the GD entry tocontact the PPC gateway and to authenticate requestsfrom the PPC gateway.

System action: The current intersystem request fails.

User response:

Examine the CD entry sysId. If a PPC gateway is notrequired to contact the remote system defined in CDentry sysId, set the GatewayName attribute to ″″. If aPPC gateway is required to contact the remote system:

v Determine the name of the PPC gateway to be used.

v View each of the GD entries defined in your regionto determine whether your region has a GD entry forthis PPC gateway.

v If there is a GD entry for the PPC Gateway check ithas been installed into the region. (Is theActivateOnStartup attribute set to Yes?)

v If a GD entry for the PPC gateway does exist in yourregion, modify the GatewayName attribute for theCD entry sysId to be the name of the GD entry forthe PPC gateway.

v If a GD entry does not exist in your region create aGD entry called GDname.

Ensure all updated CD and GD entries are installed inyour region. The TXSeries Infocenter describes the GD

ERZ030018W • ERZ030021E


and CD entries required for SNA communications andhow to install these entries in your CICS region.

Destination:

console.msg

ERZ030022E Unable to allocate storage for incomingdata

Explanation: CICS attempted to allocate task privatestorage for a message received as part of an intersystemrequest, but this was unsuccessful.


User response: Consider re-running the transaction ata later time when the system is more lightly loaded. Ifthis is a recurring problem also consider simplifyingyour transactions, so that they use less task privatestorage.

Destination:

console.msg

ERZ030023E Communications errorprimaryCode/secondaryCode on connectionto system ’sysId’

Explanation: Communications errorprimaryCode/secondaryCode was detected whilecommunicating with the remote system ’sysId’


User response: Ensure the remote system and theconnection to it are available. The TXSeries Infocentercontains information about the communications errorcodes primaryCode/secondaryCode.

Destination:

CSMT

ERZ030024E Intersystem request for transactiontransId was unsuccessful becauseconnection sysId is out of service

Explanation: CICS is unable to proceed with anintersystem request because the CommunicationsDefinition (CD) entry sysId has the InService attributeset to no. This makes the CD entry unavailable for allintersystem requests regardless of whether they areissued locally or received from a remote system.

System action: The intersystem request fails. Furthermessages can be logged. The connection remains out ofservice.

User response: Verify that the connection is supposedto be out of service. If it is not supposed to be out ofservice, set the connection in service. This can beachieved while the CICS region is running, using theEXEC CICS SET CONNECTION command. However,when the region is restarted, the state of the connection

will depend on the InService attribute of theCommunication Definition (CD) entry sysId. Therefore,to make the connection default to be in servicewhenever its CD entry is installed, you must set theInService attribute to yes.

Destination:

console.msg

ERZ030025E Intersystem request for transactiontransId was unsuccessful because thelocal SYSID for this region is null

Explanation: The LocalSysId attribute of your CICSregion’s Region Definition (RD) entry is null (″″).Therefore CICS is unable to continue with the currentintersystem request issued by transaction transId.

System action: The intersystem request fails. Furthererror messages can be logged.

User response: Set the LocalSysId attribute of the RDentry to a 1-4 character local SYSID. This name must bedifferent from the name (SYSID) of all CommunicationDefinition (CD) entries used by the transactions in yourregion. Once the LocalSysId attribute of the RD entryis configured restart your region so that the new valuecan take effect.

Destination:

console.msg

ERZ030026W CD entry sysId has the RemoteLUNameattribute set to the local region nameLUname

Explanation:

The Communications Definition (CD) entry sysId hasthe RemoteLUName attribute set to one or thefollowing local names:

v The local Logical Unit (LU) name for the region. Thisis configured in the LocalLUName attribute of thelocal Region Definition (RD).

v The local region name. This is the region’s APPLID.

v The LU name used by a PPC gateway. This isconfigured in the GatewayLUName attribute of aGateway Definition (GD) entry.

v The LU name used for CICS family TCP/IP which isderived from the TCP/IP address and port numberdefined by the TCPAddress and TCPServiceattributes of a Listener Definition (LD) entry.

If this CD entry is used by an intersystem request, therequest will be routed back to the local region by thenetwork.


User response: If this CD entry is supposed to bedefined to route requests back to the local region, noaction is required. If, however, this CD entry is required

ERZ030022E • ERZ030026W


to contact a remote system, modify the CD entry sothat the RemoteLUName attribute is set to the name ofthe remote system. Then ensure that this updated CDentry is installed in your region. The TXSeriesInfocenter describes how to configure CD entries. Italso describes how to alter existing CD entries in yourCICS region.

Destination:

console.msg

ERZ030027E Intersystem request for transactiontransId was unsuccessful because CDentry ’sysId’ does not exist

Explanation: An intersystem request was unsuccessfulbecause the Communications Definition (CD) entrysysId associated with the request is no longer installedin your region. The CD entry was possibly deleted bythe CICS command cicsdelete or it was possiblyuninstalled by the CCIN transaction either at therequest of the remote system, or because the connectionto the remote system has failed.

System action: The intersystem request fails. Furthermessages can be logged.

User response: Look at the CSMT, CCIN andconsole.msg logs for additional messages that indicatehow the CD entry was removed. If the CD entry wasdeleted using the cicsdelete command, determine whysomeone has removed the CD entry. If the CD entrymust still be defined in your region, use the cicsadd torecreate it before rerunning transaction transId. If theCD entry was deleted by CCIN, reconnect the remotesystem so a new CD entry is installed in your region,and rerun transaction transId.

Destination:

CSMT or console.msg

ERZ030028E A PD entry for program ’programName’does not exist

Explanation: CICS is unable to execute theCICS-supplied program ’programName’ because theProgram Definition (PD) entry for this program is notinstalled in the region.


User response: Install an appropriate PD entry for theprogram and resubmit the transaction.

Destination:

console.msg

ERZ030029E Program ’programName’ is defined asremote

Explanation: CICS is unable to execute theCICS-supplied program ’programName’ because theRemoteSysId attribute of its Program Definition (PD)entry is not ″″ and this CICS-supplied program is notallowed to be defined as running on a remote system.


User response: Modify the PD entry programName sothat RemoteSysId=″″ and install the updated PD entryin your region. Then resubmit the transaction.

Destination:

console.msg

ERZ030030E Intersystem request received fromunknown system ’systemName’. The LUname and network name of this systemare ’LUname’ and ’networkName’respectively

Explanation: CICS has received an intersystem requestfrom system systemName. The Logical Unit (LU) nameof this system is LUname and the network name of thissystem is networkName. The intersystem request hasfailed because CICS does not have a CommunicationsDefinition (CD) entry with the RemoteLUNameattribute set to LUname and, if networkName is notblank, the RemoteNetworkName attribute set tonetworkName. CICS requires a CD entry for the remotesystem when it receives an intersystem request in orderto perform proper security checking and dataconversion.

System action: CICS abnormally terminates theintersystem request.

User response: Determine whether your CICS regionis supposed to accept intersystem requests from thisremote system. If not contact the owner of the remotesystem to find out why the remote system is sendingrequests to your region. If the remote system ispermitted to send requests to your CICS region createand install a CD entry for this remote system. TheTXSeries Infocenter describes how to configure CDentries. It also describes how to alter existing CDentries in your CICS region.

Destination:

console.msg

ERZ030031E The attributeName attribute in entryTypeentry entryName is null

Explanation: The required attribute attributeName inentryType entry entryName is null. Intersystems requestsusing this entry can fail.


ERZ030027E • ERZ030031E


User response: Delete the invalid entry from yourregion and re-install it with correct attributes. TheTXSeries Infocenter describes how to configureentryType entries. It also describes how to alter existingentryType entries in your CICS region.

Destination:

console.msg

ERZ030032E The attributeName attribute’attributeValue’ in entryType entryentryName contains unsupportedcharacters

Explanation:

The attributeName attribute in entryType entry entryNamecontains characters that are not supported by theSystems Network Architecture (SNA). This field mustbe no more than eight characters long. The firstcharacter of this field must be an upper case alphabeticcharacter (A-Z) and the subsequent characters must beeither upper case alphabetic characters or numeric (0-9).For example, the following values are valid for theattributeName attribute:

v ″A″

v ″CICS1″

v ″OPENCICS″

v ″MYNET″

and the following values are invalid.

″9″ Begins with a number

″1CICS″Begins with a number

″OPENcics″Contains lower case alphabetic characters

″MY-NET″Contains an unsupported character


User response: Delete the entryName entry from yourregion and re-install it with correct attributes. TheTXSeries Infocenter describes how to alter these entriesand install them in your region.

Destination:

console.msg

ERZ030033W The GD entry ’GDname’ referenced byCD entry sysId does not exist

Explanation: Communications Definition (CD) entrysysId references the Gateway Definition (GD) entryGDname in the GatewayName attribute. However, theGD entry GDname does not exist. CICS requires the GDentry to contact the PPC gateway and to authenticaterequests from the PPC gateway.

System action: Intersystem requests that use CD entrysysId will fail.

User response:

Examine the CD entry sysId. If a PPC gateway is notrequired to contact the remote system defined in CDentry sysId set the GatewayName attribute to ″″ andConnectionType=local_sna. If a PPC gateway isrequired to contact the remote system:

v Determine the name of the PPC gateway to be used.

v View each of the GD entries defined in your regionto determine whether your region has a GD entry forthis PPC gateway.

v If there is a GD entry for the PPC Gateway check ithas been installed into the region. (Is theActivateOnStartup attribute set to Yes?)

v If a GD entry for the PPC gateway does exist in yourregion, modify the GatewayName attribute for theCD entry sysId to be the name of the GD entry forthe PPC gateway.

v If a GD entry does not exist in your region create aGD entry called GDname.

Ensure all updated CD and GD entries are installed inyour region. The TXSeries Infocenter describes the GDand CD entries required for SNA communications. Italso describes how to alter existing entries in yourCICS region.

Destination:

console.msg

ERZ030034E Intersystem request for transactiontransId was unsuccessful because it usedthe local SYSID sysId

Explanation:

CICS is unable to continue with the intersystem requestfor transaction transId because either:

v Transaction transId issued an intersystem requestwhich specified a SYSID of sysId. This is the localSYSID that is configured in the LocalSysId attributeof your region’s Region Definition (RD) entry. Usingthe local SYSID on this type of intersystem request isnot supported.

v A remote system using a Logical Unit (LU) name (orAPPLID) of ″ ″ (8 spaces) has made an intersystemrequest to your region.

System action: CICS abnormally terminates theintersystem request. Further messages can be logged.

User response:

Examine transaction transId.

v If it is issuing an intersystem request using SYSIDsysId, modify either the SYSID used on theintersystem request, or the LocalSysId attribute ofyour region’s RD entry, so that the transaction

ERZ030032E • ERZ030034E


requests a SYSID which is both different from thelocal SYSID and is the the name of aCommunications Definition (CD) entry that identifiesthe required remote system. The TXSeries Infocenterdescribes how to configure CD entries. It alsodescribes how alter existing entries in your CICSregion database.

v If transaction transId has been started by a remotesystem called ″ ″ then alter the name of the remotesystem.

Once all necessary updates have been made to yourregion and the remote system then rerun the request.

Destination:

CSMT

ERZ030035E Intersystem request received from SNAsystem ’systemName’ was unsuccessfulbecause CD entry sysId is not configuredfor this type of connection.

Explanation: CICS is unable to accept a local SNAintersystem request from remote system systemNamebecause the Communication Definition (CD) entry sysIdis not configured with ConnectionType=local_sna.


User response: Either add a new CD entry or alter CDentry sysId so your CICS region is configured with aCD entry for remote system systemName which hasConnectionType=local_sna. Ensure this CD entry isinstalled in your region. Then rerun the intersystemrequest. The TXSeries Infocenter describes how tocreate and install local SNA CD entries in your CICSregion.

Destination:

console.msg

ERZ030036E Intersystem request received via PPCfrom system ’systemName’ wasunsuccessful because CD entry sysId isnot configured for this type ofconnection.

Explanation: CICS is unable to accept an intersystemrequest from remote system systemName because theCommunication Definition (CD) entry sysId is notconfigured correctly. The intersystem request was eitherreceived from a remote region using TCP or it wasreceived from a PPC gateway. This means that CDentry sysId must either be configured so thatConnectionType=ppc_tcp or it must be configured sothat ConnectionType=ppc_gateway and GatewayNameis set to the name of a Gateway Definition (GD) entry.


User response: Either add a new CD entry or alter CDentry sysId so your CICS region is configured with aCD entry for remote system systemName that has thecorrect attributes for the connection it is using. Ensurethis CD entry is installed in your region. Then rerunthe intersystem request. The TXSeries Infocenterdescribes how to create and install CD entries in yourCICS region.

Destination:

console.msg

ERZ030037E Intersystem request received via CICSTCP/IP from system ’systemName’ wasunsuccessful because CD entry sysId isnot configured for this type ofconnection.

Explanation: CICS is unable to accept a request fromsystem systemName because the CommunicationsDefinition (CD) entry, sysId, is not configured withConnectionType=cics_tcp.


User response: Either add a new CD entry or alter CDentry sysId so your CICS region is configured with aCD entry for remote system systemName that has thecorrect attributes for the connection it is using. Ensurethis CD entry is installed in your region. Then rerunthe intersystem request. The TXSeries Infocenterdescribes how to create and install CD entries in yourCICS region.

Destination:

console.msg

ERZ030044E The PPC code errorCode, indicating theamount of data received from a remotesystem was unexpected

Explanation: During a receive from a remote system,the PPC code indicating the amount of PPC datareceived errorCode was not recognized by CICS. Acomplete list of possible codes can be found in fileprodDir/include/ppc/ppc.h under the type’ppc_whatDataReceived_t’.


User response: Ensure that the versions of softwareused by your CICS region are compatible. Also checkthat the software running on the remote system iscompatible with your local CICS region. If the remotesystem is connected to your CICS region via a PPCGateway and a Systems Network Architecture (SNA)network check that the version of the PPC gateway iscompatible with the versions of CICS used by yourlocal region. If you find that the software used by thecommunicating systems is incompatible install thecorrect versions. Try the transaction again. If theproblem persists, contact your support organization.

ERZ030035E • ERZ030044E


Destination:

CSMT

ERZ030046E The communications function’functionName’ failed withcommunications errorprimaryCode/secondaryCode

Explanation: Communications errorprimaryCode/secondaryCode was received from theinternal CICS function call to ’functionName’.


User response: Ensure that the versions of softwareused by your CICS region are compatible. Also checkthat the software running on the remote system iscompatible with your local CICS region. If the remotesystem is connected to your CICS region via a PPCGateway and a Systems Network Architecture (SNA)network check that the version of the PPC gateway iscompatible with the versions of CICS used by yourlocal region. If you find that the software used by thecommunicating systems is incompatible install thecorrect versions. The TXSeries Infocenter providesinformation about the communications error codesfunctionName/primaryCode. Try the transaction again. Ifthe problem persists, contact your support organization.

Destination:

console.msg or CSMT

ERZ030047W Unexpected communications errorprimaryCode/secondaryCode

Explanation: CICS detected an unexpectedcommunications error during the freeing of aconversation.


User response: Ensure that the versions of softwareused by your CICS region are compatible. Also checkthat the software running on the remote system iscompatible with your local CICS region. If the remotesystem is connected to your CICS region via a PPCGateway and a Systems Network Architecture (SNA)network check that the version of the PPC gateway iscompatible with the versions of CICS used by yourlocal region. If you find that the software used by thecommunicating systems is incompatible install thecorrect versions. The TXSeries Infocenter providesinformation about the communications error codesprimaryCode/secondaryCode. Try the transaction again. Ifthe problem persists, contact your support organization.

Destination:

CSMT

ERZ030048E Unexpected communications errorprimaryCode/secondaryCode

Explanation: CICS detected an unexpectedcommunications error.


User response: Ensure that the versions of softwareused by your CICS region are compatible. Also checkthat the software running on the remote system iscompatible with your local CICS region. If the remotesystem is connected to your CICS region via a PPCGateway and a Systems Network Architecture (SNA)network check that the version of the PPC gateway iscompatible with the versions of CICS used by yourlocal region. If you find that the software used by thecommunicating systems is incompatible install thecorrect versions. The TXSeries Infocenter providesinformation about the communications error codesprimaryCode/secondaryCode. Try the transaction again. Ifthe problem persists, contact your support organization.

Destination:

CSMT

ERZ030049E Unexpected Data Flow Control (DFC)indicator errorCode during receive

Explanation: An unexpected Data Flow Control (DFC)indicator errorCode was received from a remote systemduring a receive.


User response: Ensure that the versions of softwareused by your CICS region are compatible. Also checkthat the software running on the remote system iscompatible with your local CICS region. If the remotesystem is connected to your CICS region via a PPCGateway and a Systems Network Architecture (SNA)network check that the version of the PPC gateway iscompatible with the versions of CICS used by yourlocal region. If you find that the software used by thecommunicating systems is incompatible install thecorrect versions. Try the transaction again. If theproblem persists, contact your support organization.

Destination:

CSMT

ERZ030051W Unable to validate the passwordreceived with userid ’userId’ from system’sysId’. Using the region default userid’defaultUserId’ instead

Explanation: A request was received from the remotesystem defined in Communications Definition (CD)entry sysId. However, the userid and password sentwith the request was not able to be validated. This canpossibly be because the userid is not defined to theregion or because the password is incorrect for theuserid.

ERZ030046E • ERZ030051W


System action: CICS assigns userid defaultUserId,which is defined in the DefaultUserId attribute of theRegion Definition (RD) entry, to the request. IfdefaultUserId is authorized to execute the request, therequest continues. Otherwise, the request will fail witha security violation.

User response: Verify that the userid, userId is definedto the region in the User Definitions (UD) and thepassword associated with the userid is correct.

Destination:

CSMT

ERZ030053I Using a default local code page of’localCodePage’ which has a CICSshortcode of ’shortCode’

Explanation: CICS is running with a default local codepage of ’localCodePage’. A code page identifies thehexadecimal codes used to represent characters. Forexample, the letter ’A’ is represented by 0x41 in theASCII code page, ISO8859-1, and as 0xC1 in theEBCDIC code page, IBM-037. The region’s local codepage defines how characters are represented locally. Atransaction running in the region will use the defaultlocal code page, localCodePage, unless it was started bya cicsterm or cicsteld terminal. Transactions started bythese terminals use the code page associated with theterminal’s locale as the local code page. Code pageinformation is important when CICS is communicatingwith remote systems as it affects data conversion. Dataconversion can possibly be required if a remote systemis using a different code page from the local region.Refer to the TXSeries Infocenter for information aboutCICS data conversion. CICS extracts the default localcode page, localCodePage, from the operating system. Itsvalue is derived from the locale setting of the localmachine. Refer to the operating system documentationfor information about the locales and code pagesavailable on your machine. Code page localCodePage isequivalent to the CICS Family shortcode, shortCode.Shortcodes are used to specify code pages in theDFHCNV macros They are also used to send code pageinformation between CICS systems. Refer to theTXSeries Infocenter for more information aboutshortcodes.


User response: None

Destination:

console.msg

ERZ030054E The LD entry ’LDname’ referenced byCD entry sysId does not exist

Explanation: An intersystems request wasunsuccessful because the Transmission ControlProtocol/Internet Protocol (TCP/IP) CommunicationsDefinition (CD) entry sysId references the Listener

Definition (LD) entry LDname in the ListenerNameattribute. However, the LD entry LDname does notexist. CICS requires the LD entry to contact the remotesystem.

System action: The current intersystem request fails.

User response: Examine the LD entries defined inyour region. If LD entry LDname is defined, ensureActivateOnStartup=yes and the entry is defined inboth the permanent and runtime database. Then restartyour region as LD entries are only activated at regionstartup. Messages will appear in the console.msg logduring startup which indicate that a listener process isbeing started for the LD entry. If LD entry LDname isnot defined, but another suitable LD entry withProtocol=TCP is defined, alter CD entry sysId so theListenerName points to this LD entry. If no suitable LDentry is defined in your region, add an LD entry calledLDname and restart your region. The TXSeriesInfocenter describes how to configure CD and LDentries.

Destination:

console.msg

ERZ030055E GD entry GDentry is using the samelocal LU name, LUname, as GD entrymatchingGDentry

Explanation: Gateway Definition (GD) entry GDentryis configured to use the same SNA local Logical Unit(LU) name as GD entry matchingGDentry. This meantan intersystem request using GD entry GDentry wasunsuccessful because your SNA product only allowsone operating system process to use a particular localLU name. The local LU name is configured in theGatewayLUName attribute of the GD entry. TheTXSeries Infocenter describes the local LU namesrequired by your region.


User response:

Alter your region configuration so that each GD entryis configured with a different LU name. If you changethe LU name configured in a GD entry, or if youremove a GD entry, make sure the configuration for theoriginal local LU name has been removed from the PPCgateway server by either:

v using the ppcadmin delete luentry command or

v stopping and cold starting the PPC gateway serveror

v stopping and destroying the PPC gateway server.

In addition, if you remove a GD entry, make sure thereare no Communications Definitions (CD) entriesreferencing the GD entry in the GatewayNameattribute. The TXSeries Infocenter has more informationon using PPC gateways.

ERZ030053I • ERZ030055E


Destination:

console.msg

ERZ030056W No SNA LD entry defined for CD entry’sysId’

Explanation: The Communications Definition (CD)entry sysId has ConnectionType=local_sna whichmeans the connection must use the CICS local SNAsupport. However, intersystem requests that use thisCD entry will fail because a Listener Definition (LD)entry with Protocol=SNA is not defined in the region.


User response: Add a LD entry with Protocol=SNA toyour region database and restart your region to activatethis new entry. The TXSeries Infocenter describes howto add LD entries.

Destination:

console.msg

ERZ030057W Ignoring attributeName attribute’attributeValue’ in CD entry sysId as theConnectionType is connectionType

Explanation: The Communications Definition (CD)entry sysId has ConnectionType set to connectionType.This type of connection expects attribute attributeNameto be set to blank (″″). However, in this CD entry,attribute attributeName is set to attributeValue. Thiscondition does not make the CD entry unusable. Awarning message has been produced as this canpossibly indicate that the ConnectionType attribute isincorrectly set.


User response: Examine all of the attribute settings inthis CD entry and correct them so they are consistentwith the ConnectionType. The TXSeries Infocenterdescribes how to configure CD entries. It also describeshow to update CD entries.

Destination:

console.msg

ERZ030058W The attributeName attribute in entryTypeentry entryName is null

Explanation: The attribute attributeName in entryTypeentry entryName is null. Intersystems requests using thisentry can fail.


User response: Check that the attribute is not requiredby any of the intersystem requests that use the entry. Ifthe attribute is required, delete the invalid entry fromyour region and re-install it with correct attributes. TheTXSeries Infocenter describes how to configureentryType entries. It also describes how to update

entryType entries in your region.

Destination:

console.msg

ERZ030059E GD entry GDentry is using the samelocal LU name, LUname, as the localSNA support

Explanation: The PPC gateway defined in GatewayDefinition (GD) entry GDentry is configured to use thesame SNA local Logical Unit (LU) name as the region’slocal SNA support. This will not work as your SNAproduct only allows one process to use a particularlocal LU.

System action: CICS continues processing. However,configuring this PPC gateway can fail. In addition,inbound intersystem requests through this PPCgateway or through local SNA can fail.

User response:

Determine whether your region is supposed to useboth local SNA and a PPC gateway. If local SNA is notrequired:

v Shutdown your region.

v Remove the Listener Definition (LD) entry which hasProtocol=SNA.

v Restart your region.

If the PPC gateway is not required:

v Remove the GD entry GDentry from your region.

v Remove the configuration for local LU LUname fromthe PPC gateway server by either:

– using the ppcadmin delete luentry command or

– stopping and cold starting the PPC gatewayserver or

– stopping and destroying the PPC gateway server.

If both local SNA and the PPC gateway are required:

v Define another local LU in your SNA product.

v Set up each form of communication to use a differentlocal LU. Either:

– Shutdown your region.

– Set Region Definition (RD) attributeLocalLUName to the name of this new local LUname.

– Set attribute GatewayLUName in GD entryGDentry to LUname.

– Restart your region.

or

v Set attribute GatewayLUName in GD entry GDentryto the name of this new local LU name.

v Set Region Definition (RD) attribute LocalLUNameto LUname.

ERZ030056W • ERZ030059E


v Remove the configuration for local LU LUname fromthe PPC gateway server by either:

– using the ppcadmin delete luentry command or

– stopping and cold starting the PPC gatewayserver.

The TXSeries Infocenter has more information on usingPPC gateways and local SNA.

Destination:

console.msg

ERZ030060I PPC gateway configuration has started

Explanation: Information about the region is beingpassed to each of the PPC gateways defined in theGateway Definitions (GD).

System action: CICS passes information about theregion to each PPC gateway that is configured in theGD. Once CICS has configured all the PPC gateways itwrites message ERZ3061I.

User response: None

Destination:

console.msg

ERZ030061I PPC gateway configuration has ended

Explanation: CICS has completed configuring the PPCgateways that are defined in the Gateway Definitions(GD). This message is written whether theconfiguration is successful or not.


User response: None

Destination:

console.msg

ERZ030062I Configuring PPC gateway ’GDname’with details of the region

Explanation: Information about the region is beingpassed to the PPC gateway described in GatewayDefinition (GD) entry GDname. This information will beused by the PPC gateway to pass intersystem requestsfrom remote SNA system to the region.

System action:

CICS passes:

v the SNA Logical Unit (LU) name configured in theLocalLUName attribute of the Region Definition(RD) and

to the PPC gateway described in the GD entry GDname.

User response: None

Destination:

console.msg

ERZ030063I Configuring PPC gateway ’GDname’with details of local transactions

Explanation: The identifiers of transactions that havean IBM Communications Server for AIX LU6.2Transaction Program Name profile specified in theTransaction Definition (TD) attribute TPNSNAProfileare being passed to the PPC gateway described byGateway Definition (GD) entry GDname. CICStransaction identifiers are only used by the AIX PPCgateway. They are required to receive inboundintersystem requests from remote SNA systems usingIBM Communications Server for AIX. If the PPCgateway is not an AIX PPC gateway, CICS will stoppassing transaction identifiers after the first call to thePPC gateway. This message is written whether thereare any TD entries that have TPNSNAProfile set to aprofile name or not.

System action: CICS examines each TD entry in theregion database. If the TPNSNAProfile attribute is setto the name of an IBM Communications Server for AIXLU6.2 Transaction Program Name profile (rather than″″) the name of this profile and the transactionidentifier is passed to the PPC gateway defined in theGD entry ’GDname’. This process stops after the firstcall to the PPC gateway if the PPC gateway informsCICS that it is not an AIX PPC gateway.

User response: None

Destination:

console.msg

ERZ030064I Configuring PPC gateway ’GDname’ hasended

Explanation: CICS has finished configuring the PPCgateway that is defined by Gateway Definition (GD)entry ’GDname’. This message is written whether theconfiguration is successful or not.


User response: None

Destination:

console.msg

ERZ030065I Configuring PPC gateways withtransaction ’transId’ has started

Explanation: A new Transaction Definition (TD) entryfor transaction ’transId’ has been installed in the CICSregion. This TD entry has the name of an IBMCommunications Server for AIX LU6.2 TransactionProgram Name profile in the TPNSNAProfile attribute.CICS will therefore attempt to contact all PPC gatewaysdefined in the Gateway Definitions (GD) to informthem of this new CICS transaction.

ERZ030060I • ERZ030065I


System action: CICS passes the transaction identifierand the name of the AIX SNA Server/6000 LU6.2Transaction Program Name profile to each PPCgateway defined in the Gateway Definitions (GD). Ifthe PPC gateway is an AIX PPC gateway, it will informIBM Communications Server for AIX that it wishes toreceive requests for the transaction identifier. If the PPCgateway is not AIX it will do nothing as only IBMCommunications Server for AIX requires configurationinformation about CICS transactions. Once CICS hasconfigured all the PPC gateways defined in the GD itdisplays message ERZ3067I.

User response: None

Destination:

console.msg

ERZ030066I Configuring PPC gateway ’GDname’with transaction ’transId’

Explanation: A new Transaction Definition (TD) entryfor transaction ’transId’ has been installed in the CICSregion. This TD entry has the name of an IBMCommunications Server for AIX LU6.2 TransactionProgram Name profile in the TPNSNAProfile attribute.CICS is about to pass the IBM Communications Serverfor AIX LU6.2 Transaction Program Name profile nameand the transaction identifier transId to the PPCgateway defined in the Gateway Definition (GD) entryGDname.

System action: CICS passes the transaction identifierand the name of the IBM Communications Server forAIX LU6.2 Transaction Program Name profile to thePPC gateway defined in the Gateway Definition (GD)entry GDname. If the PPC gateway is an AIX PPCgateway, it will inform IBM Communications Server forAIX that it wishes to receive requests for thetransaction identifier. If the PPC gateway is not AIX itwill do nothing as only IBM Communications Serverfor AIX requires configuration information about CICStransactions.

User response: None

Destination:

console.msg

ERZ030067I Configuring PPC gateways withtransaction ’transId’ has ended

Explanation: CICS has completed configuring the PPCgateways that are defined in the Gateway Definitions(GD) with details of transaction transId. This message isdisplayed whether the configuration is successful ornot.


User response: None

Destination:

console.msg

ERZ030068I Deleting transaction ’transId’ from PPCgateways has started

Explanation: A Transaction Definition (TD) entry forCICS transaction ’transId’ has been deleted from theCICS region. This TD entry had the name of an IBMCommunications Server for AIX LU6.2 TransactionProgram Name profile in the TPNSNAProfile attribute.CICS will therefore attempt to contact all PPC gatewaysdefined in the Gateway Definitions (GD) to informthem that this CICS transaction has been deleted.

System action: CICS passes the transaction identifiertransId to each PPC gateway defined in the GatewayDefinitions (GD). If the PPC gateway is an AIX PPCgateway, it will inform IBM Communications Server forAIX that it no longer wishes to receive requests for thetransaction identifier. If the PPC gateway is not AIX itwill do nothing as only IBM Communications Serverfor AIX requires configuration information about CICStransactions. Once CICS has contacted all the PPCgateways defined in the Gateway Definitions (GD) itdisplays message ERZ3070I.

User response: None

Destination:

console.msg

ERZ030069I Deleting transaction ’transId’ from PPCgateway ’GDname’

Explanation: A Transaction Definition (TD) entry fortransaction ’transId’ has been installed in the CICSregion. This TD entry has the name of an IBMCommunications Server for AIX LU6.2 TransactionProgram Name profile in the TPNSNAProfile attribute.CICS is about to pass transId to the PPC gatewaydefined in the Gateway Definition (GD) entry GDname.

System action: CICS passes the transaction identifierto the PPC gateway defined in the Gateway Definition(GD) entry transId. If the PPC gateway is an AIX PPCgateway, it will inform AIX SNA Server/6000 that it nolonger wishes to receive requests for the transactionidentifier. If the PPC gateway is not an AIX PPCgateway it will do nothing as only IBMCommunications Server for AIX requires configurationinformation about CICS transactions.

User response: None

Destination:

console.msg

ERZ030070I Deleting transaction ’transId’ from PPCgateways has ended

Explanation: CICS has finished deleting transaction’transId’ from all the PPC gateways defined in the

ERZ030066I • ERZ030070I


Gateway Definitions (GD). This message is displayedwhether the deletion is successful or not.


User response: None

Destination:

console.msg

ERZ030071E Unable to contact PPC gateway GDnameregistered at ’CDSname’

Explanation:

CICS issued a configuration call to the PPC gatewaydefined in Gateway Definition (GD) entry GDname.However, the PPC gateway did not respond. Possiblereasons include:

v The PPC gateway is not running.

v The PPC gateway is running but is not listening forrequests. (For example, the PPC gateway is shuttingdown.)

System action: CICS stops configuring this PPCgateway. Some or all SNA intersystem requests that aresupposed to use this PPC gateway can fail until CICSsuccessfully completes this configuration.

User response:

v Check that the PPC gateway is running. The ps -ef |grep ppcgwy command will display all the PPCgateways running on a particular machine. Ifnecessary start the PPC gateway.

v If the PPC gateway was running, check the PPCgateway’s message log for error or shutdownmessages. If you find error messages you do notexpect, investigate the causes of these errors. If youfind that the PPC gateway is shutting down, wait forthe shutdown to complete and restart the PPCgateway.

Once you have ensured the GD entry is correct and thePPC gateway is running, retry the PPC gatewayconfiguration either by:

v restarting your CICS region or

v running the CGWY transaction (see the TXSeriesInfocenter

Destination:

console.msg

ERZ030072E Unauthorized to contact PPC gatewayGDname registered at ’CDSname’

Explanation: CICS issued a configuration request tothe PPC gateway defined in Gateway Definition (GD)entry GDname. However, the PPC gateway rejected thisrequest as your CICS region does not have the correctpermissions to use this PPC gateway.

System action: CICS stops configuring this PPC

gateway. Some or all SNA intersystem requests throughthis PPC gateway will fail until CICS completes thisconfiguration.

User response: Check that the PPC gateway definedin GD entry GDname is the correct PPC gateway foryour region. Modify the GD entry if it does not containthe correct values. Once you are sure that your regionnow has access to the PPC gateway, either restart yourregion or run the CGWY transaction so that yourregion configures the PPC gateway.

Destination:

console.msg

ERZ030073E PPC gateway GDname registered at’CDSname’ does not recognizeconfiguration calls

Explanation:

CICS issued a configuration call to the PPC gatewaydefined in Gateway Definition (GD) entry GDname.However, the PPC gateway does not recognize theconfiguration call and so returned an error code.Possible reasons include:

v The PPC gateway was in the process of initializingor shutting down when CICS made the configurationcall.

v The PPC gateway is running with a level of softwarethat is incompatible with the software being used byyour CICS region.

System action: CICS stops configuring this PPCgateway. Some or all SNA intersystem requests throughthis PPC gateway will fail until CICS successfullyconfigures it.

User response: Check that the PPC gateway definedin GD entry GDname is the correct PPC gateway foryour region. If required, modify the GD entry so that itspecifies the correct PPC gateway. Check that thesoftware level of the PPC gateway is compatible withyour CICS region. If it is not, install the correct levels ofsoftware. Once you are sure that your region isconfigured to use a PPC gateway running at the correctlevel of software either restart your region or run theCGWY transaction to configure the PPC gateway. TheTXSeries Infocenter explains how to set up and runyour PPC gateway. It also describes how to use theCGWY transaction. If you need further help in solvingthis problem, contact your support organization.

Destination:

console.msg

ERZ030074E Unable to configure PPC gateway’GDname’ registered at ’CDSname’. PPCstatus code is ’errorString’ (errorCode)

Explanation: CICS issued a configuration call to thePPC gateway defined in Gateway Definition (GD) entry

ERZ030071E • ERZ030074E


GDname. However, the PPC gateway was unable toperform the request and returned an error codeerrorCode. This error code has a description oferrorString. The errorString indicates where the erroroccurred.

System action: CICS stops configuring this PPCgateway. Some or all SNA intersystem requests throughthis PPC gateway will fail until CICS successfullyconfigures it.

User response:

Use the value of errorString as a guide and check that

v the PPC gateway defined in GD entry GDname is thecorrect PPC gateway for your region. If required,modify the GD entry so that it specifies the correctPPC gateway.

v your SNA product is running

v your PPC gateway is correctly set up and running

v the software level of the PPC gateway is compatiblewith your CICS region. If it is not, install the correctlevels of software.

In addition, check the PPC gateway’s message file asthe PPC gateway possibly logged an error message.PPC gateway messages and their meaning aredescribed in the TXSeries Infocenter. Once you havecorrected the problem, either restart your region, or runthe CGWY transaction to configure the PPC gateway.The TXSeries Infocenter explains how to set up and runyour PPC gateway. It also describes how to use theCGWY transaction. If you need further help in solvingthis problem, contact your support organization.

Destination:

console.msg

ERZ030075E Unable to configure transaction(s)’transIdList’ using a TPNSNAProfile of’SNAprofile’ in PPC gateway GDnameregistered at CDSname

Explanation:

CICS issued a configuration call to the PPC gatewaydefined in Gateway Definition (GD) entry GDname.This call passed information about your region’stransactions to the PPC gateway to enable the PPCgateway to receive requests for these transactions fromremote System Network Architecture (SNA) systems.However, the PPC gateway was unable to register thetransactions transIdList with IBM CommunicationsServer for AIX for one of the following reasons.

v IBM Communications Server for AIX is not running.

v The profile SNAprofile has the characters DEFAULTin its name.

v The profile SNAprofile is not correctly defined in IBMCommunications Server for AIX.

v The GatewayLUName attribute of the GD entryGDname is ″″ and there is a Listener Definition (LD)entry with the Protocol attribute set to SNA installedin your region.

v There is another process, such as a PPC gateway,which is registered with IBM Communications Serverfor AIX and is using the local SNA Logical Unit (LU)name defined in the GatewayLUName attribute ofthe GD entry GDname. (If GatewayLUName=″″, itdefaults to the LU name configured in theLocalLUName attribute of your region’s RegionDefinition (RD)).

System action: CICS processing continues. Inboundintersystem requests for these transactions from remoteSNA systems can fail.

User response: Check that IBM CommunicationsServer for AIX is running. If it is not, restart it. ThePPC gateway is supposed to register with IBMCommunications Server for AIX automatically. If thisdoes not occur and requests for transactions listed intransIdList from remote SNA systems fail either restartyour region or run the CGWY transaction to configurethe PPC gateway. Check that the profile SNAprofile iscorrectly defined to IBM Communications Server forAIX. Issue the verifysna -R command to ensure thatthis profile is copies into IBM Communications Serverfor AIX’s runtime database. Check that there is onlyone copy of the PPC gateway named in GD entryGDname running. The command ps -ef | grep ppcgwywill list all the PPC gateways running on a particularmachine. Look for instances of the PPC gateway thatare using the name defined in the GatewayCDSNameattribute of GD entry GDname. If more than one copyof this PPC gateway is running, use the AIX commandkill -9 to stop all of these PPC gateways and, restart anew copy of the PPC gateway. Once the PPC gatewayhas started, either restart your CICS region or run theCGWY transaction to configure the PPC gateway. TheTXSeries Infocenter explains how to set up and runyour PPC gateway. It also describes how to configureIBM Communications Server for AIX profiles.

Destination:

console.msg

ERZ030076E Unable to configure transaction(s)’transIdList’ using a TPNSNAProfile of’SNAprofile’ at PPC gateway ’GDname’(’CDSname’). PPC status code is’errorString’ (errorCode)

Explanation: CICS issued a configuration call to thePPC gateway defined in Communications Definition(CD) entry GDname with information about CICStransactions transIdList. However, this call failed witherror code errorCode. The message text associated withthis error code is errorString.

System action: CICS continues processing. Inboundintersystem requests for these transactions from remote

ERZ030075E • ERZ030076E


SNA systems can possibly fail.

User response: Check that the PPC gateway definedin GD entry transIdList is the correct PPC gateway foryour region. Modify the GD entry if it does not containthe correct values. Check that the software level of thePPC gateway is compatible with your CICS region. If itis not, install the correct levels of software and restartboth the PPC gateway and the CICS region. If the PPCgateway is at the correct software level it is possiblethat the PPC gateway was either not set up correctly ornot running when CICS issued the configuration call.Ensure that the PPC gateway is running correctly andrestart your CICS region to re-drive the PPC gatewayconfiguration. When you have solved the problemeither restart you CICS region or run the CGWYtransaction to configure the PPC gateway. The TXSeriesInfocenter explains how to set up and run your PPCgateway. It also describes how to run the CGWYtransaction.

Destination:

console.msg

ERZ030077I Deleting details of local region fromPPC gateway ’GDname’ has started

Explanation: The Gateway Definition (GD) entryGDname has been deleted from the region database.CICS has started removing details of your region fromthis PPC gateway so that the PPC gateway will nolonger send intersystem requests to your region.

System action: CICS makes a configuration call to thePPC gateway that was defined in GD entry GDname.

User response: None

Destination:

console.msg

ERZ030078I Deleting details of local region fromPPC gateway ’GDname’ has ended

Explanation: CICS has finished removing details ofyour region from the PPC gateway defined in GatewayDefinition (GD) entry GDname. This message isdisplayed whether the deletion is successfully or not.


User response: None

Destination:

console.msg

ERZ030079E Unable to delete transaction(s)’transIdList’ from PPC gateway ’GDname’

Explanation: CICS issued a configuration call to thePPC gateway defined in Gateway Definition (GD) entryGDname. However, the PPC gateway was unable toperform the request. Details of the transactions listed in

transIdList can remain configured in the PPC gatewayuntil your region reconfigures the PPC gateway (eitherwhen your region is restarted or the CGWY transactionis run). This does not affect intersystemscommunication. If, however, you add a TD entry forany of the transactions listed in transIdList before thePPC gateway is reconfigured the resultingconfiguration calls made to the PPC gateway can fail.


User response: This error does not affect the operationof your region and PPC gateway. Action is onlyrequired if you are to add a TD entry for any of thetransactions listed in transIdList, in which case run theCGWY transaction to reconfigure the PPC gateway. Ifthis fails refer to the messages produced by CGWY.

Destination:

console.msg

ERZ030080E Unable to delete transaction(s)’transIdList’ from PPC gateway ’GDname’.PPC status code is ’errorString’ (errorCode)

Explanation: CICS issued a configuration call to thePPC gateway defined in Gateway Definition (GD) entryGDname. However, the PPC gateway was unable toperform the request and returned an error codeerrorCode. This error code has a description oferrorString. The errorString indicates where the erroroccurred. Details of the transactions listed in transIdListcan remain configured in the PPC gateway until yourregion reconfigures the PPC gateway (either when yourregion is restarted or the CGWY transaction is run).This does not affect intersystems communication. If,however, you add a TD entry for any of thetransactions listed in transIdList before the PPC gatewayis reconfigured the resulting configuration calls made tothe PPC gateway can fail.


User response: This error does not affect the operationof your region and PPC gateway. Action is onlyrequired if you are to add a TD entry for any of thetransactions listed in transIdList in which case run theCGWY transaction to reconfigure the PPC gateway. Ifthis fails refer to the messages produced by CGWY.

Destination:

console.msg

ERZ030081E Unable to configure PPC gateways

Explanation: CICS is unable to configure the PPCgateways defined in the Gateway Definitions (GD)because the CGWY transaction will not start.


User response:

Check that there is a Transaction Definition (TD) entry

ERZ030077I • ERZ030081E


for the CGWY transaction installed in your region.Make sure the attributes of this TD entry are as follows:

v ActivateOnStartup = yes

v ProgName = ″″

v RSLKey = private

v TSLKey = 1

v RSLCheck = none

v TSLCheck = internal

v EnableStatus = enabled

v IsBackEndDTP = no

v RemoteSysId = ″″

v RemoteName = ″″

v InvocationMode =no_facility|any_start|at_normal_running

When the TD entry for CGWY is correct and if yourCICS region is using one or more PPC gateways usethe EXEC CICS START TRANSID(″CGWY″)command to retry the CGWY transaction. If theproblem persists contact your support organization.

Destination:

console.msg

ERZ030090W TCP/IP host name hostName in CD entrysysId maps to more than one TCP/IPaddress, using address ’address’

Explanation: Communications Definition (CD) entrysysId has RemoteTCPAddress set to hostName. Thishost name maps to more than one TCP/IP networkadapter address. CICS will use the first networkadapter address extracted as the address of the remotesystem. This is address.


User response: Examine address address. If this is thecorrect network address for the remote system then nofurther action is required. If this address is not thecorrect address for the remote system then alter CDentry sysId so that RemoteTCPAddress is set to thecorrect address. The TXSeries Infocenter describes howto configure CD entries for CICS family TCP/IP. It alsodescribes how to alter CD entries in your region.

Destination:

console.msg

ERZ030091E Unable to resolve RemoteTCPAddress’address’ in CD entry sysId

Explanation: The TCP/IP name service is unable toconvert the value of address in the RemoteTCPAddressattribute in Communications Definition (CD) entrysysId into a TCP/IP network adapter address. This ispossibly because address is specified in an incorrectformat, or address is a host name which is not definedin the TCP/IP name service.

System action: CD entry sysId is marked as invalidand is unavailable for intersystem requests.

User response: Alter CD sysId so that theRemoteTCPAddress attribute specifies a correctnetwork adapter address. The TXSeries Infocenterdescribes how to configure CD entries for CICS familyTCP/IP connections. It also describes how to alter CDentries in your region.

Destination:

console.msg

ERZ030092E Unable to contact TCP/IP name serviceto resolve RemoteTCPAddress ’hostName’in CD entry sysId

Explanation: Communications Definition (CD) entrysysId has RemoteTCPAddress set to hostName. CICS isunable to convert this TCP/IP hostname into a TCP/IPnetwork adapter address because it can not contact theTCP/IP name server. This is possibly because the nameserver is unavailable or the local machine is notcorrectly configured to contact the name server.

System action: CD entry sysId is marked as invalidand is unavailable for intersystem requests.

User response: Using your operating systeminformation, ensure the TCP/IP name service isavailable to the local machine. Delete and then add CDentry sysId to your region so CICS accesses the TCP/IPname service to extract the network adapter address.Refer to the TXSeries Infocenter for information onmanaging CD entries in your region.

Destination:

console.msg

ERZ030093E Unable to resolve RemoteTCPAddress’address’ in CD entry sysId

Explanation: CICS has detected an internal errorwhich is preventing it from initializingCommunications Definition (CD) entry sysId.

System action: CD entry sysId is marked as invalid.Further error messages can be logged.

User response: Examine the console.msg file formessages describing why CICS can not initialize CDentry sysId. Follow the instructions for these messages.

Destination:

console.msg

ERZ030094E Intersystem request for transactiontransId was unsuccessful because CDentry sysId contains incorrect attributes

Explanation: CICS is unable to continue with anintersystem request for transaction transId because theattributes in Communications Definition (CD) entry

ERZ030090W • ERZ030094E


sysId are not correct. CICS has already reported theexact cause of the problem during region initialization.

System action: The intersystem request isunsuccessful. Further messages can be logged.

User response: Examine the console.msg file as thiswill contain the messages describing which attributes inCD entry sysId are not correct. Follow the instructionsassociated with these messages and rerun theintersystem request.

Destination:

console.msg

ERZ030095E DTP request issued by transId is notsupported on CICS family TCP/IPconnection sysId

Explanation: CICS is unable to continue with aDistributed Transaction Processing (DTP) request fortransaction transId because Communications Definition(CD) entry sysId is configured withConnectionType=cics_tcp and DTP is not supported onCICS family TCP/IP connections.


User response:


v If this transaction is issuing an EXEC CICSALLOCATE SYSID(sysId) command, alter transactiontransId to specify a CD entry in the SYSID optionwhich is not configured withConnectionType=cics_tcp.

v If transaction transId was started by a transactionrouting request sent from the remote system, alterthe IsBackEndDTP attribute in the TransactionDefinition (TD) entry for transId soIsBackEndDTP=no.

v If transaction transId was started by a DTPtransaction in remote system sysId, alter the remotetransaction to use a connection which is not CICSfamily TCP/IP.

The TXSeries Infocenter describes the EXEC CICSALLOCATE command. It also describes the differenttypes of connections supported by CICS and how toalter resource definitions in your region. Once thenecessary changes have been made and the updatedprograms and definitions have been installed in yourregion, rerun the request.

Destination:

console.msg

ERZ030096E DTP request issued by transId is notsupported on connection to CICS ClientsysId

Explanation: CICS is unable to continue with aDistributed Transaction Processing (DTP) request issuedby transaction transId because the remote systemconfigured in Communications Definition (CD) entrysysId is an CICS Clients which does not support DTP.


User response:


v If this transaction is issuing an EXEC CICSALLOCATE SYSID(sysId) command, alter transactiontransId to specify a CD entry in the SYSID optionwhich is not configured as a connection to an CICSClients. The TXSeries Infocenter

v If transaction transId was started by a request froman CICS Clients terminal, alter the IsBackEndDTPattribute in the Transaction Definition (TD) entry fortransId so IsBackEndDTP=no. The TXSeriesInfocenter describes how to alter resource definitionsin your region.

Once the necessary changes have been made and theupdated programs and definitions have been installedin your region, rerun the request.

Destination:

console.msg

ERZ030097W Unable to locate GD entry using localLU ’localLUname’ for remote system’remoteLUname’

Explanation: CICS has received an intersystem requestfrom a remote system called remoteLUname via a PPCgateway server. This PPC gateway server is using theLogical Unit (LU) name localLUname as this region’slocal LU name. However, CICS does not have aGateway Definitions (GD) entry that is configured withlocalLUname as the local LU name.


User response: Add a GD entry for your PPC gatewayserver to your CICS region, specifyingGatewayLUName=localLUname. The name of this GDentry must be the same as the value of theGatewayName attribute of the CommunicationsDefinition (CD) entry for remote system remoteLUname.Once the resource definitions are correct, rerun theintersystem request. If you require further information,see the TXSeries Infocenter.

Destination:

console.msg

ERZ030095E • ERZ030097W


ERZ030098E The LD entry ’LDname’ referenced byCD entry sysId is not configured forTCP/IP

Explanation: An intersystem request is usingCommunications Definition (CD) entry sysId. This CDentry has ConnectionType=cics_tcp andListenerName=LDname. The ListenerName attributemust therefore be configured with the name of aListener Definition (LD) entry which has Protocol=TCP.However, LD entry LDname does not haveProtocol=TCP configured.


User response:


v Alter LD entry LDname so that Protocol=TCP andthe other attributes are correctly configured for CICSfamily TCP/IP.

or

v Alter CD entry LDname so that the ListenerNameattribute is set to the name of a CICS family TCP/IPLD entry.

The TXSeries Infocenter describes the LD and CDentries required for CICS family TCP/IP support. Italso describes how to install these entries in your CICSregion.

Destination:

console.msg

ERZ030099E Unable to accept an intersystem requestfrom remote system ’remoteLUname’because CD entry sysId is not configuredwith a GD entry using local LU’localLUname’

Explanation:

CICS has received a request from remote systemremoteLUname via a PPC gateway server. However, theCommunications Definition (CD) entry, sysId, forremote system remoteLUname does not have theGatewayName attribute set up correctly. Either:

v The GatewayName attribute is null (″″).

v The GatewayName attribute is not set to the name ofa Gateway Definition (GD) entry.

v The GD entry specified by the GatewayNameattribute is not configured with localLUname as thelocal LU name.


User response:

If CICS appears to be using the wrong CD entry, look

at the CD entry that CICS was supposed to use, as thisis incorrectly configured. Check theConnectionType=ppc_gateway and theRemoteLUName, SNAConnectName andRemoteNetworkName attributes are correct. Examinethe GatewayName attribute in the CD entry.

v If it is null (″″), add a GD entry for your PPCGateway server to your CICS region, specifyingGatewayLUName=localLUname. Then alter theGatewayName attribute in CD entry sysId to be thename of this new GD entry.

v If it is set to the name of a GD entry, ensure thisentry has GatewayLUName=localLUname and thisentry is installed in your region.

Otherwise, if CD entry sysId is the expected CD entry,examine the GatewayName attribute in the CD entry.

v If it is null (″″), add a GD entry for your PPCGateway server to your CICS region, specifyingGatewayLUName=localLUname. Then alter theGatewayName attribute in CD entry sysId to be thename of this new GD entry.

v If it is set to the name of a GD entry, ensure thisentry has GatewayLUName=localLUname and thisentry is installed in your region.

The TXSeries Infocenter describes how to configure CDand GD entries for SNA connections that use a PPCGateway server. It also describes how to modify CDentries and install GD entries in your CICS region.Rerun the intersystem request once the changes havebeen made to the resource definitions.

Destination:

console.msg

ERZ030100E Local LU name ’localLU’ or Partner LUname ’partnerLU’ used on intersystemrequest to system sysId is incorrect

Explanation: An intersystem request was made to theremote system configured in CommunicationsDefinition (CD) entry sysId. However, this request wasunsuccessful because either the local logical unit (LU)name localLU or the partner LU name partnerLUcontains invalid characters. The partner LU namepartnerLU is configured in either the RemoteLUNameor the SNAConnectName attributes of CD entry sysId.The local LU name localLU is either the region’s name(APPLID) or it is configured in the LocalLUNameattribute of the Region Definition (RD) entry for yourregion.


User response: Correct the configuration of CD entrysysId so the local and partner LU names used arecorrect. If you require further information, see theTXSeries Infocenter.

ERZ030098E • ERZ030100E


Destination:

console.msg

ERZ030101E Local LU name ’localLU’ or Partner LUname ’partnerLU’ used on intersystemrequest to system sysId through gatewayGDname is incorrect

Explanation:

An intersystem request was made to the remote systemconfigured in Communications Definition (CD) entrysysId. This CD entry has ConnectionType=ppc_gatewayand GatewayName=GDname which means theintersystem request was supposed to be passed to thePPC gateway server configured in Gateway Definitions(GD) entry GDname. However, the intersystems requestwas unsuccessful because either:

v the local logical unit (LU) name localLU containsinvalid characters, or

v the partner LU name partnerLU contains invalidcharacters, or

v the partner LU name partnerLU is longer than eightcharacters, or

v the PPC gateway server has not been configuredwith information about your CICS region, or

v there are two copies of your PPC gateway serverrunning, or

v the local LU name localLU can not be used by thePPC gateway server because another operatingsystem process is already using it. This process canbe a CICS region using local SNA or another PPCGateway server.

The partner LU name, partnerLU, is configured in eitherthe RemoteLUName or the SNAConnectNameattribute of CD entry sysId. The local LU name, localLU,is configured in the GatewayLUName attribute of theGateway Definition (GD) entry GDname. (If thisattribute is ″″ it defaults to the LocalLUName attributeof the Region Definition (RD) entry for your region.)


User response:

Check the localLU and partnerLU LU names containcorrect characters. Correct the CICS configuration ifnecessary. The TXSeries Infocenter describes how toalter CD, GD and RD entries. If localLU and partnerLUare correct, use the:

$ cicsget -r <regionName> -c gd GDname

command to display GD entry GDname. TheGatewayCDSName attribute will be configured withthe name of the PPC gateway server. The TXSeriesInfocenter attribute maps to the name of the PPC

gateway server. Log on to the machine where the PPCgateway server configured in GD entry GDname issupposed to run. Use the:

$ ps -ef | grep ppcgwy

command to list the PPC gateway servers running. Ifmore than one copy of the PPC gateway serverconfigured in GD entry GDname is running then usethe cicsppcgwyshut command to shut one of themdown. Then shut the other one down using the kill -9<processId> command where <processId> is theoperating system process identifier (pid) of the PPCgateway server process. Finally restart your PPCgateway server. Check that all the PPC gateway serversrunning have the correct CICS regions configured. Usethe ppcadmin list luentries command to display theconfiguration in each PPC gateway server. (See theTXSeries Infocenter for information on this command.)There must be one luentry for each GD entry. If a PPCgateway server is missing information about a CICSregion then run the CGWY transaction on that CICSregion. The TXSeries Infocenter describes how to dothis. Look at the configuration of all the regionsrunning on on the same machine as the PPC gatewayserver. (The cicslist command will list all of the CICSregions defined on the machine.) Check the setting ofthe RD entry attribute LocalLUName and theGatewayLUName attributes of all the GD entriesconfigured in these regions. These local LU namevalues must be different from localLU. If they are not,then you need to rearrange the local LU names used onthe machine. The TXSeries Infocenter describes the localLU names required by your region. It also describeshow to alter GD and RD entries. If there are no errorsin the LU names used by your CICS regions and PPCgateway servers then you must look for a SNAapplication that is using local LU name localLU. It isnot possible to share local LU names between SNAapplication and a CICS region. So when you locate thisSNA application, change the local LU name it is using.

Note: If you change the local LU name used by CICS,a PPC gateway or a SNA application, ensure thatthe configuration on all remote SNA systems thatcommunicate with the local LU name is alsoupdated. Otherwise these remote SNA systemswill no longer be able to connect to yourregion/application.

Destination:

console.msg

ERZ030102E An intersystem request has abnormallyterminated with abend code ’abendCode’

Explanation: CICS detected an unexpected conditionwhile processing an intersystem request. A symptomrecord (symrec) has been created and further messagescan be logged. These will provide additionalinformation about the cause of the problem.

ERZ030101E • ERZ030102E


System action: CICS abnormally terminates theintersystem request with abend code abendCode.

User response: Follow the instructions given for theabend code abendCode and any additional messageslogged by CICS. If you can not solve the problemyourself, save the CSMT log, console.msg file and thesymrec file and contact your support organization.

Destination:

console.msg or CSMT

ERZ030103E entryType entry ’entryName’ is unusablebecause server-side transactions areenabled

Explanation: entryType entry entryName is requestingsupport for PPC communications. However, the regionis running with ServerSideTran=yes in the RegionDefinition (RD) entry. This attribute enables server-sidetransactions in the SFS Server which means the regionis unable to support PPC communications.

System action: The entryType entry entryName ismarked as unavailable for intersystem requests.

User response: If you wish the CICS region to supportintersystem requests using PPC communications thenrestart your CICS region with ServerSideTran=no.Alternatively, remove entryType entry ’entryName’ fromyour region’s definitions.

Destination:

console.msg


Explanation:

CICS control data for a Intersystem Communication(ISC) request was not able to be converted betweencode page ’codePage1’ and code page ’codePage2’because:





User response: Ensure the conversion routines forcode pages codePage1 and codePage2 are correctlyinstalled. Consult the operating system documentationon iconv and genxlt for further details. If you areunable to solve this problem yourself, contact yoursupport organization.

Destination:

CSMT

ERZ030106E XPRecv TIMEOUT with timeout value%d and TermID %s

Explanation:

System action:

User response:

Destination:

ERZ031001E The principal facility for CRTE must bea terminal

Explanation: The CRTE transaction cannot be startedwithout a terminal as its principal facility.


User response: Ensure that the transaction is beingstarted from a terminal, and not by another transactionexecuting ATI commands that start the transaction.

Destination:

CSMT

ERZ031002E Cannot obtain the National LanguageSupport (NLS) CANCEL keyword

Explanation: CRTE was not able to retrieve theCANCEL keyword from the NLS message catalogue foryour locale.


User response: Verify that a CICS NLS messagecatalogue exists for the locale of your region. As aninterim solution, you can type the word ’CANCEL’ inEnglish to terminate the transaction routing session.

Destination:

console.msg

ERZ031003W Invalid transaction identifier ’transId’ -please resubmit

Explanation: The transaction ’transId’ is not known onthe remote system.


User response: Verify that the transaction name youhave entered is correct, and that it is available on thesystem you are transaction routing to.

Destination:


ERZ031004I Routing session to system ’sysId’terminated

Explanation: CICS has terminated the transactionrouting session to system ’sysId’.


ERZ030103E • ERZ031004I


User response: Enter your next transaction. All furthertransactions are executed on the local system.

Destination:


ERZ031005E Incorrect syntax - Correct syntax isCRTE SYSID {=sysId|(sysId)}

Explanation: You attempted to start the CRTEtransaction using an incorrect syntax.

System action: CICS terminates the CRTE transaction.

User response: Re-enter the CRTE transaction usingthe correct syntax.

Destination:


ERZ031006E Incorrect syntax - Correct syntax isTPNxxxxx or CANCEL

Explanation: You attempted to run the CRTEtransaction using an incorrect syntax.


User response: To start a transaction on the remotesystem, enter a valid transaction identifier. To terminatethe transaction routing session to the remote system,enter CANCEL. In particular, you cannot starttransactions by using a PF key.

Destination:


ERZ031007E Remote system ’sysId’ cannot be found

Explanation: A Communications Definition (CD) entryfor the remote system ’sysId’ was not able to be found.


User response: Verify that you have entered thecorrect system name when invoking CRTE. Also verifythat a Communications Definition (CD) entry for thesystem exists.

Destination:


ERZ031008E Routing session terminated becauseCICS has lost the connection to system’sysId’

Explanation: The CRTE session cannot continuebecause CICS has detected a communications error onthe connection to the remote system.


User response: Ensure the remote system and theconnection to it are available. Further information on

the reason for the error can be obtained by examiningthe CICS message logs and by referring to TXSeriesInfocenter.

Destination:


ERZ031009I Routing session to system ’sysId’ started

Explanation: CICS has started the transaction routingsession to the remote system ’sysId’. All furthertransactions are executed on the remote system.


User response: Clear the screen and enter the name ofthe transaction to be started. To terminate the routingsession, clear the screen and enter CANCEL.

Destination:


ERZ031010E System ’sysId’ is not available

Explanation: The transaction cannot be startedbecause the remote system, or the connection to it, areunavailable.


User response: Ensure that the remote system and theconnection to it are available. Further information onwhy the system is unavailable can be obtained byexamining the CICS message logs and by referring toTXSeries Infocenter.

Destination:


ERZ031015E Terminal definition is not shippable

Explanation: A request to ship a terminal definitionhas been received from the remote system. Theterminal definition cannot be shipped because itsTerminal Definition (WD) entry is marked asunshippable.


User response: Confirm that it is desirable for thelocal system to ship a terminal definition for theterminal. If it is, then set the IsShippable attribute ofthe WD entry for the terminal to yes. If it is notdesirable to ship terminal definitions from the localsystem, consider adding a definition of the terminal onthe remote system. If the remote system is CICS onOpen Systems or CICS for Windows NT, version 4, thiscan be achieved by adding a WD entry for terminal,with the RemoteSysId attribute set to the name of thelocal system. Otherwise consult the appropriatedocumentation for that system.

Destination:

ERZ031005E • ERZ031015E



ERZ031016W The remote transaction has abnormallyterminated

Explanation: The transaction that you are executingon the remote system has abnormally terminated.


User response: Use the procedures that areappropriate for the remote system to determine thereason for the abnormal termination of the transaction.Further transactions that you enter continue to berouted to the remote system.

Destination:


ERZ031017E Routing session terminated because of atransaction routing error

Explanation: CICS cannot continue execution of therouting session because of an error while transactionrouting.


User response: Examine the CICS message logs toobtain additional information on the reasons for theerror.

Destination:


ERZ031018E Unable to route to the local system’sysId’

Explanation: You have specified a remote system thatis the same as the name of the local system.


User response: Re-enter CRTE, specifying a remotesystem for which a Communications Definition (CD)entry exists.

Destination:


ERZ031019E System ’sysId’ is not in service

Explanation: The system you have specified is not inservice.


User response: Verify that the system is supposed tobe in service, then set the system back in service bysetting the InService attribute of the CommunicationDefinition (CD) entry for the system to yes. Thenre-submit the CRTE transaction.

Destination:


ERZ031020W There is a problem communicating withsystem ’sysId’

Explanation: CRTE is not known to the remotesystem.


User response: Verify that communication to theremote system is correctly configured and that theconnection is active.

Destination:


ERZ032001E The CICS-private transaction whichschedules remote transaction initiationrequests was unable to attach to system’sysId’ because of communications error’primaryCode’/’secondaryCode’.

Explanation: The attempt to schedule a remotetransaction initiation request on system ’sysId’ wasunsuccessful due to failure to allocate a session to thatsystem.

System action: The CICS-private transaction isabnormally terminated on this system. The request toschedule the transaction is lost. Other processingcontinues.

User response: The message indicates the reason forthe failure, which can result from loss of connectivity tothe remote system or a resource definition problem.Refer to the TXSeries Infocenter for further informationconcerning error codes ’primaryCode’ and’secondaryCode’. Check the error logs of the remotesystem to determine whether there are any relevantmessages. Determine the cause of the problem and takeappropriate remedial action before retrying the failingrequest.

Destination:

CSMT

ERZ032002E The CICS-private transaction whichschedules remote transaction initiationrequests received communications error’primaryCode’/’secondaryCode’ from system’sysId’.

Explanation: The CICS-private transaction whichschedules remote transaction initiation requestsreceived a communications error during a conversationwith system ’sysId’. This can result from loss ofconnectivity to that system.


ERZ031016W • ERZ032002E


User response: Refer to the TXSeries Infocenter forfurther information concerning error codes’primaryCode’ and ’secondaryCode’. Check the error logsof the remote system to determine whether there areany relevant messages. Determine the cause of theproblem and take appropriate remedial action beforeretrying the failing request.

Destination:

CSMT

ERZ032003E Transaction ’transId’ not executed onterminal ’termId’ on system ’sysId’.Schedule request failed on that system.

Explanation: A request was made to schedule a taskon remote system ’sysId’. The request was not able tobe executed.


User response: Check the system definition tables ofthe remote system to determine why schedule requestsare not honored.

Destination:

CSMT

ERZ032004E Transaction ’transId’ not executed onterminal ’termId’ on system ’sysId’.

Explanation: The CICS-private transaction whichschedules remote transaction initiation requests hasabnormally terminated on system ’sysId’.


User response: Check the error logs of system ’sysId’to determine the reason for the abend on that system.

Destination:

CSMT

ERZ032005E System identifier for terminal ’termId’cannot be determined.

Explanation: A request was made on this system toschedule a transaction for a remote terminal, which hasa system identifier of NULL or a system identifier of asystem which is not defined.

System action: The CICS-private transaction whichschedules remote transaction initiation requests isabnormally terminated on this system. The request toschedule the transaction is lost. Other processingcontinues.

User response: Correct the CICS region definitions tobe consistent.

Destination:

CSMT

ERZ032006E Message from system ’sysId’ garbled.

Explanation: The CICS-private transaction whichschedules remote transaction initiation requests hasreceived an unintelligible message.

System action: The conversation to the remote systemis abnormally terminated. The CICS-private transactionon this system is abnormally terminated. Otherprocessing continues.

User response: If this problem occurs repeatedly,determine the details of remote requester from theremote system identified in this message. Inform theadministrator of that system of the problem with arequest to prevent this from re-occurring. Ensure thatthe problem is not a consequence of the CICS-privatetransaction being invoked from an application programon that system.

Destination:

CSMT

ERZ032007E Transaction ’transId’ not executed onterminal ’termId’ on system ’sysId’.Terminal invalid on that system.

Explanation: A request was made to schedule a taskon remote system ’sysId’. The request was not able tobe executed because terminal ’termId’ is not defined onsystem ’sysId’.

System action: Other processing continues. Therequest to schedule the transaction is lost.

User response: Ensure that terminal ’termId’ andtransaction ’transId’ are defined on system ’sysId’.

Destination:

CSMT

ERZ032008E CICS-private transaction received anunknown message from system ’sysId’.

Explanation: transaction received a message that wasnot expected and is not supported.

System action: The transaction is abnormallyterminated on this system. Other processing continues.

User response: If this problem occurs repeatedly,determine the details of remote requester from theremote system identified in this message. Inform theadministrator of that system about the problem with arequest to prevent this from re-occurring. Ensure thatthe problem is not a consequence of the CICS-private

ERZ032003E • ERZ032008E


transaction being invoked from an application programon that system.

Destination:

CSMT

ERZ032009E Request from System ’sysId’ to initiatetransaction ’transId’ on that system onterminal ’termId’ was not executed.Transaction is not defined correctly onthis system.

Explanation: A transaction ’transId’ was scheduled onsystem ’sysId’ against a terminal ’termId’ residing locallyon this system. Because the request was to run thetransaction ’transId’ on system ’sysId’, the transactionmust be routed back to that system. However, the localdefinition of the transaction ’transId’ is not correct. Adefinition is required on this system defining thetransaction ’transId’ as remote on system ’sysId’.

System action: Other processing continues.

User response: Ensure that terminal ’termId’ andtransaction ’transId’ are defined correctly on bothsystems. In particular, ensure that there is a transactiondefinition for transaction routing the request back tosystem ’sysId’ from this system. The RemoteSysIdattribute in the TD for ’transId’ must be ’sysId’.

Destination:

CSMT

ERZ032010E Transaction ’transId’ not executed onterminal ’termId’ on system ’sysId’.Remote system is quiescing.

Explanation: A request was made to schedule atransaction on a remote system ’sysId’. The request wasnot able to be executed because the remote system isquiescing.

System action: The request to schedule the transactionis lost. Other processing continues.

User response: Wait until the remote system is back inservice before sending any more requests to it.

Destination:

CSMT

ERZ032012E Failed to initialize iconv descriptors.

Explanation: A CICS-private transaction hasattempted unsuccessfully to initialize code pageconversion (which is used to perform ASCII/EBCDICtranslation). As a result intercommunication fails.

System action: The CICS-private transaction isabnormally terminated. Other processing continues.

User response: There is a serious problem with thenational language support (NLS) environment of the

operating system. A required code page descriptor ispossibly not installed. A preceding message indicateswhich one is missing. If the required NLS environmentcannot be installed then the CICS system must berestarted with a locale which is supported on thesystem.

Destination:

CSMT

ERZ032013E ASCII/EBCDIC conversion has failed.

Explanation: CICS-private transaction has been unableto perform an ASCII/EBCDIC conversion.

System action: The transaction is abnormallyterminated. Other processing continues.

User response: Investigate the remote terminaldefinitions and transaction definitions to determinewhether they are valid. If an invalid definition is foundthen correct it else contact your support organization.

Destination:

CSMT

ERZ032014E Terminal definition for Terminal ’termId’specifies a remote system identifierwhich is the same as the local system.

Explanation: A request to initiate a transaction for aremote terminal cannot be processed as the terminaldefinition is inconsistent.

System action: The transaction is abnormallyterminated. The request to schedule the transaction islost. Other processing continues.

User response: Correct the terminal definition.

Destination:

CSMT

ERZ032021E Transaction ’transId’ not executed onterminal ’termId’ on system ’sysId’.Transaction is not defined correctly onthat system.

Explanation: A transaction ’transId’ was scheduled onthis system against a terminal ’termId’ residing on theremote system ’sysId’. Because the request was to runthe transaction ’transId’ locally, the transaction must berouted back to this system to run. However, thedefinition of the transaction ’transId’ on system ’sysId’ isnot correct. A definition is required on system ’sysId’defining ’transId’ as residing on this system.

System action: The transaction is not scheduled. Otherprocessing continues.

User response: Ensure that terminal ’termId’ andtransaction ’transId’ are defined correctly on bothsystems. In particular, ensure that there is a transaction

ERZ032009E • ERZ032021E


definition for routing transaction ’transId’ back to thissystem from the remote system ’sysId’.

Destination:

CSMT

ERZ032022E Request from System ’sysId’ to initiatetransaction ’transId’ on that system onterminal ’termId’ was not executed.Terminal invalid on this system.

Explanation: A request was received from remotesystem ’sysId’ to initiate transaction ’transId’ on system’sysId’ on terminal ’termId’. The request was not able tobe honored because terminal ’termId’ is not defined inthis system.


User response: Ensure that terminal ’termId’ andtransaction ’transId’ are defined on both systems.

Destination:

CSMT

ERZ032024E Unable to obtain database entry forsystem ’sysId’.

Explanation: The connection definition has beenremoved from the runtime system. This is most likelyto be an operational error.


User response: Investigate how the connectiondefinition has been removed.

Destination:

CSMT

ERZ032025E Unable to obtain database entry forterminal ’termId’.

Explanation: The terminal definition has beenremoved from the runtime system. This is most likelyto be an operational error.


User response: Investigate how the terminal definitionhas been removed.

Destination:

CSMT

ERZ032026E Unsuccessful attempt to start theCICS-private remote schedulingtransaction (CRSR).

Explanation: CICS detected that the CICS-privatetransaction CRSR was not defined in the region’sdatabase.

System action: START requests that are for remotely

defined terminals are never processed. Other processingcontinues.

User response: Ensure that the CICS-privatetransaction definitions are the same as the defaultdefinitions for the CICS-private transaction CRSR andrestart the region.

Destination:

CSMT

ERZ032027I Communications with remote system’sysId’ failed; remote terminal STARTrequests not being transmitted.

Explanation: This is an informational message. Itinforms CICS users that START requests for remoteterminals on the specified system are not being sentsince the remote system is out of service. Requestsremain queued until the remote system is back inservice.

System action: START requests for remote terminalson the given sysid are queued on this system.

User response: Make arrangements to get remotesystem sysId back in service.

Destination:

CSMT

ERZ032028I Communications with remote system’sysId’ succeeded; sending remoteterminal START requests.

Explanation: A previously out of service system isnow in service. START requests for remote terminals onthat system are now being sent to it.

System action: START requests for terminals on thespecified system are now sent.

User response: None

Destination:

CSMT

ERZ032029I Unsupported message type(’messageType’) requested

Explanation: A request to ship an unsupportedmessage type to the partner CICS system has beenreceived.

System action: No action is taken for this request.Other processing continues.

User response: None

Destination:

CSMT

ERZ032022E • ERZ032029I


ERZ032030E Request from System ’sysId’ to initiatetransaction ’transId’ on that system onterminal ’termId’ was not executed.Transaction was dynamic on this system.

Explanation: A request was received from system’sysId’ to initiate transaction ’transId’ on that system onterminal ’termId’. The request was not able to behonored because transaction ’transId’ is defined asbeing dynamic on this system.


User response: Ensure that dynamic transactions arenot invoked on an intermediate system. Ensure that thelocal transaction definition does not specify that thetransaction is dynamic.

Destination:

CSMT

ERZ032031E The CICS-private transaction CRSR wasinvoked incorrectly

Explanation: The CICS-private transaction whichschedules remote transaction initiation requests wasinvoked incorrectly - for example, by an applicationissuing an EXEC CICS START TRANSID(CRSR).


User response: Establish how the CRSR transactionwas invoked. CRSR is a CICS-private transaction thatmust only ever be started by CICS. Ensure that theInvocationMode specified in the Transaction Definition(TD) for the CRSR transaction has not been changedfrom the default value, (this can possibly allowapplications to start the transaction illegally).

Destination:

CSMT

ERZ033001E Transaction ’transId’ rejected -’errorString’.

Explanation: The transaction ’transId’ was submittedto the Transaction Scheduler (TS), but the TS rejectedthe request for the reason given in ’errorString’.


User response: Check that you specified the correcttransaction name. Check that transaction ’transId’ iscorrectly defined in the Transaction Definitions (TD).Also check other messages for signs of problems withthe TS.

Destination:

stderr

ERZ034001E Region name ’regionName’ is too long

Explanation: Your Resource Definition Online (RDO)operation is unsuccessful because the region name thatyou specified is too long.

System action: The RDO operation terminates.

User response: Retry the RDO operation, specifying ashorter region name.

Destination:

stderr

ERZ034002E Unsuccessful Region Pool memoryallocation when inserting runtimedatabase entry ’resourceName’ into classclassName

Explanation: CICS was attempting to obtain sufficientRegion Pool memory to insert the runtime databaseentry. Insufficient Region Pool memory was available.

System action: The entry is not inserted into theruntime database.

User response: You can temporarily increase the sizeof the Region Pool available by restarting the regionand overriding the MaxRegionPool attribute, with alarger value, on the command line.

Destination:

console.msg and stderr

ERZ034003E Unsuccessful Region Pool memorydeallocation when inserting runtimedatabase entry ’resourceName’ into classclassName

Explanation: CICS was unable to release Region Poolmemory used during an attempt to insert an entry intothe runtime database.

System action: The entry is still inserted into theruntime database unless indicated otherwise by anothermessage. The Region Pool memory that has not beenreleased is released when the region is restarted.

User response: There is a serious problem with yourregion. Restart the region at the earliest opportunity. Ifthe problem persists, contact your support organization.

Destination:

console.msg and stderr

ERZ034004E Abnormal termination U3406. Invalidruntime database hash table sizespecified for class className

Explanation: The value in RD stanza ClassTableSizeattribute for class className is invalid.


ERZ032030E • ERZ034004E


User response: You can restart the region overridingthe ClassTableSize attribute, with valid values, on thecommand line. For a permanent solution, update theClassTableSize attribute values in the RD resourcedefinition stanza file. using cicsupdate.

Destination:

stderr

ERZ034005E Abnormal termination U3405. Cannotallocate Region Pool memory for regiondatabase

Explanation: CICS is unable to allocate enoughmemory, from the Region Pool, to initialize the runtimedatabase.


User response: You can temporarily increase the sizeof the Region pool available by restarting the regionand overriding the MaxRegionPool attribute, with alarger value, on the command line.

Destination:

stderr

ERZ034006E Unable to setup communications withregion. Runtime database request notsent.

Explanation: Your Resource Definition Online (RDO)operation has made an unsuccessful attempt to set upcommunications with a region. The RDO request hasnot been sent to the region, and CICS has therefore notperformed this operation on the runtime database.

System action: The runtime database RDO operationterminates.

User response: Check that the region is availablebefore retrying the RDO command.

Destination:

stderr

ERZ034007E Unable to communicate with region.Runtime database request not sent.

Explanation: Your Resource Definition Online (RDO)operation has made an unsuccessful attempt tocommunicate with a region. The RDO request has notbeen sent to the region, and CICS has therefore notperformed this operation on the runtime database.


User response: Retry the RDO runtime operation. If itcontinues to fail, contact your support organization.

Destination:

stderr

ERZ034008E Unable to communicate with region.Runtime database request already sent.

Explanation: Your Resource Definition Online (RDO)operation has made an unsuccessful attempt tocommunicate with the region, but has already sent theRDO request to the region. CICS possibly performedthe runtime database operation.


User response: Messages in the regions console.msgpossibly indicate the cause of the failure. Retry theRDO runtime operation.

Destination:

stderr

ERZ034009E Runtime database request rejected byregion

Explanation: CICS has vetoed the runtime databaseoperation. Messages in the region’s console.msgindicate why the operation has been vetoed.

System action: The Resource Definition Online (RDO)runtime database operation terminates.

User response: Check the region’s console.msg for thereason why the operation was vetoed and respondaccordingly.

Destination:

stderr

ERZ034010E Unsuccessful update to permanentdatabase entry ’resourceName’ in classclassName

Explanation: CICS detected error(s) in the updatesrequested to the permanent database entry. Messagesindicating the error(s) encountered have already beenwritten to stderr.

System action: The Resource Definition Online (RDO)operation terminates.

User response: As indicated by the previousmessage(s) detailing the errors in the update request.

Destination:

stderr

ERZ034011E Unsuccessful attempt to accesspermanent database entry ’resourceName’in class className; error code errorNumber

Explanation: The Resource Definition Online (RDO)operation was unsuccessful when accessing thepermanent database stanza files for the reason defined

ERZ034005E • ERZ034011E


by the operating system as error code errorNumber.


User response: Refer to operating systemdocumentation for the error code.

Destination:

stderr

ERZ034012E Invalid server name ’serverName’

Explanation: The server name serverName mustconform to the CICS naming conventions for Servers.This is /.:/cics/sfs/serverName for Structured FileServers (SFS) and /.:/cics/ppc/gateway/gatewayNamefor PPC Gateways.

System action: CICS does not perform the CICSdatabase operation.

User response: Correct the input and retry thedatabase operation.

Destination:

stderr

ERZ034013W Permanent database entry ’resourceName’already exists in class ’className’

Explanation: You attempted to insert an entry thatalready exists in the permanent database.

System action: The entry is not inserted into thepermanent database and the Resource Definition Online(RDO) operation terminates.

User response: Select a new key or delete the existingentry resourceName, as appropriate, and perform theinsert again. The insert was possibly unsuccessfulbecause another user inserted an entry with the samekey.

Destination:

stderr

ERZ034015W Permanent database entry ’resourceName’in class className is flagged aspermanent. Amendment not allowed.

Explanation: You attempted to amend a permanentdatabase entry whose Permanent attribute has thevalue yes. Such database entries cannot be amended.

System action: The permanent database entry is notamended.

User response: Perform an amendment to the entrythat modifies its Permanent attribute to no. You canmake simultaneous and/or further amendments to thatentry until the Permanent attribute is amended back toyes. Perform such modifications with care.

Destination:

stderr

ERZ034016W Permanent database entry ’resourceName’in class className flagged as permanent.Deletion not allowed.

Explanation: You attempted to delete a permanentdatabase entry whose Permanent attribute has thevalue yes. Such database entries cannot be deleted.

System action: The permanent database entry is notdeleted.

User response: If you want to delete the entry, youmust first modify the entry’s Permanent attribute tono.

Destination:

stderr

ERZ034017E Unable to auto start. Incomplete ormissing runtime database recoveryimage

Explanation: CICS has detected a missing run-timedatabase recovery image stanza (.auto) file.

System action: Startup of the region is terminated.

User response: Either cold start the region or recoverthe run-time database recovery image from a backupand attempt the automatic start again.

Destination:

stderr

ERZ034018E You are not authorized to operate on theruntime database class className

Explanation: You attempted to perform an operationon a runtime database class’s recovery image that youdo not have authority to operate on. The file accessrights to the runtime database recovery image stanzafile, administered by the operating system, do notallow you access.

System action: The operation terminates. The runtimedatabase operation has not been performed.

User response: Login as a user with sufficient accessto perform updates to the class’s run-time databaserecovery image.

Destination:

stderr

ERZ034020E You are not authorized to operate on thepermanent database class className

Explanation: You attempted to perform an operationon a permanent database class’s stanza file that you donot have authority to operate on. The file group accessrights of the stanza file do not allow you access.

ERZ034012E • ERZ034020E


System action: The operation terminates. Thepermanent database request has not been performed.

User response: Login as a user with sufficient groupaccess to perform updates to the class in the permanentdatabase. Group access is required because any accessto the database class stanza file possibly requiresreinstatement of a backup file that was created andthus owned by another administrator.

Destination:

stderr

ERZ034021E Runtime database initializationunsuccessful

Explanation: CICS detected error(s) duringinitialization of the runtime database. Other errormessages explain why the initialization wasunsuccessful.


User response: As indicated by the message(s)detailing the errors during database initialization. Ifthese are errors in the stanza entry(s) you must coldstart the region.

Destination:

console.msg

ERZ034023E Unable to setup access to stanza file’filePath’; error code ’errorNumber’

Explanation: CICS cannot set up the file ownershipand access rights to the stanza file filePath. The errorgiven by the operating system as errorNumber specifiesthe reason for the failure.

System action: If the error occurs during regionstartup, CICS terminates the startup procedure. If theerror occurs during a Resource Definition Online (RDO)session, CICS terminates the current RDO operation.

User response: On UNIX refer to the operating systemdocumentation on chown() and chmod(). On WindowsNT refer to the operating system documentation onsetting file access permissions.

Destination:


ERZ034024E Abnormal termination U3410:Permanent database stanza file ’filePath’does not exist

Explanation: CICS cannot find the permanentdatabase stanza file filePath.


User response: Recover the permanent databasestanza file from a backup.

Destination:

console.msg

ERZ034025E Unable to access stanza file ’filePath’

Explanation: CICS detected an error when attemptingto access the stanza file filePath. This message follows adetailed message indicating the actual error thatoccurred.


User response: As indicated by the precedingmessage(s) detailing the error detected.

Destination:


ERZ034026E Unable to access stanza file ’filePath’;error code errorNumber

Explanation: CICS detected an error when attemptingto access the stanza file filePath. The operating systemgives the error as errorNumber.


User response: As indicated by the operating systemin the error code. If the file is a permanent databaseclass’s stanza file it can be restored from a backup. Ifthe file is a temporary or backup stanza file usedduring database operation then the operation can beretried.

Destination:


ERZ034027E Unable to recover stanza file ’filePath’

Explanation: CICS detected an error when attemptingto recover the stanza file filePath. This message followsa detailed message indicating the actual error thatoccurred.


User response: As indicated by the precedingmessage(s) detailing the error detected.

Destination:


ERZ034021E • ERZ034027E


ERZ034028E Unable to remove temporary stanza file’filePath’; error code errorNumber

Explanation: CICS detected an error when attemptingto remove the stanza file filePath. The operating systemgives the error as errorNumber.


User response: Refer to the operating systemdocumentation for remove(). The temporary stanza fileis removed by the next successful operation on thestanza.

Destination:


ERZ034029E Unable to close stanza file ’filePath’;error code errorNumber

Explanation: CICS detected an error when attemptingto close the stanza file filePath. The operating systemgives the error as errorNumber.

System action: If this error occurs during startup,CICS terminates the startup procedure. If the erroroccurs during a Resource Definition Online (RDO)session, CICS terminates the current RDO operation.

User response: Refer to the operating systemdocumentation for fclose().

Destination:


ERZ034030E Unable to obtain exclusive lock onstanza file ’filePath’; error codeerrorNumber

Explanation: CICS was unable to complete anexclusive lock on the stanza file filePath.


User response: Refer to the operating systemdocumentation for fcntl().

Destination:


ERZ034031E Abnormal termination U3410: Unable toobtain region pathname

Explanation: CICS was unable to determine thepathname for the region.


User response: Retry the operation. If the errorcontinues to occur, contact your support organization.

Destination:

stderr

ERZ034032E Abnormal termination U3410: Runtimedatabase recovery image initializationunsuccessful for class className

Explanation: CICS detected an error when initializingthe region’s run-time database recovery image for theclass className. Other error messages explain whyCICS is unable to initialize the run-time databaserecovery image.


User response: As indicated by preceding message(s)detailing the error(s) detected.

Destination:

console.msg

ERZ034033E Abnormal termination U3410: Unable toobtain region name

Explanation: CICS was unable to determine the nameof the region.


User response: Retry the operation. If the errorcontinues to occur, contact your support organization.

Destination:

stderr

ERZ034034W Runtime recovery image alreadycontains a ’resourceName’ entry for classclassName

Explanation: CICS region’s runtime database recoveryimage already contains the entry. The runtime databaseand its recovery image are out of synchronization forthis entry.

System action: The runtime database request isperformed, but the recovery image is not updated.

User response: To get the runtime database and itsrecovery image back into synchronization delete therecord from the runtime database and then add again.

Destination:

stderr

ERZ034028E • ERZ034034W


ERZ034035E Abnormal termination U3410: Runtimedatabase recovery image path bufferexceeded

Explanation: The size of the CICS internal buffer usedto build up pathnames during initialization of theruntime database recovery image has been exceeded.


User response: Re-install the region so that itspathname is shorter.

Destination:

console.msg

ERZ034036E Unsuccessful truncation of file ’filePath’;error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when truncating thestanza or temporary file filePath for the permanent orruntime database recovery image. A subsequentmessage identifies the file or database and databaseclass affected.

System action: If this error occurs during regionstartup, CICS abnormally terminates region. If the erroroccurs during a Resource Definition Online (RDO)session, CICS terminates the current RDO operation.

User response: CICS resilience ensures that any stanzaaffected is recovered next time an operation isperformed on that stanza where the truncation failed.Refer to the operating system documentation forftruncate().

Destination:


ERZ034038E Invalid data detected in database stanzaentry ’resourceName’ for class className

Explanation: CICS detected a data conversion errorwhen reading the permanent database entry in thestanza file for class className. Messages indicating theerror(s) detected have already been written to stderr orconsole.msg.

System action: If this error occurs during startup,CICS abnormally terminates the region. If the erroroccurs during a Resource Definition Online (RDO)session, CICS terminates the current RDO operation.

User response: As indicated by the previous messagesdetailing the errors encountered.

Destination:


ERZ034039E Cannot convert value ’attributeValue’ forattribute ’attributeName’ into a number

Explanation: CICS cannot convert the attribute valueattributeValue into a valid number. If the error isdetected in a CICS database stanza file, rather than userinput, further messages are generated identifying thedatabase stanza entry containing the invalid value.


User response: If the error is in a CICS database entry,edit the stanza entry identified by subsequent messagesto correct the attribute value. If necessary, recover thedatabase stanza from a backup. If the error occurredwhen entering an RDO operation, correct the input andretry the command.

Destination:


ERZ034040E Attribute ’attributeName’: Invalid value’attributeValue’

Explanation: CICS detected an invalid data valueattributeValue for the attribute attributeName. If the erroris detected in a CICS database stanza file, rather thanuser input, further messages are generated identifyingthe database stanza entry containing the invalid value.



Destination:


ERZ034042E Attribute ’attributeName’: String valuestarting ’attributeValue’ is too long

Explanation: The attribute value attributeValue islonger than the maximum string value length allowedfor that attribute. If the error is detected in a CICSdatabase stanza file, rather than user input, furthermessages are generated identifying the database stanzaentry containing the invalid value.


ERZ034035E • ERZ034042E



Destination:


ERZ034043E Attribute ’attributeName’: String value’attributeValue’ has missing end quotes

Explanation: The attribute’s string value attributeValuedoes not have end quotes. If the error is detected in aCICS database stanza file, rather than user input,further messages are generated identifying the databasestanza entry containing the invalid value.



Destination:


ERZ034044E Attribute ’attributeName’: Unexpectedquote ’characterValue’ found in stringvalue

Explanation: The attribute’s string value contains anunexpected quote character. If the error is detected in aCICS database stanza file, rather than user input, thenfurther messages are generated identifying the databasestanza entry containing the invalid value.


User response: If the error is in a CICS database entryedit the stanza entry identified by subsequent messagesand correct the attribute value. If necessary, recover thedatabase stanza from a backup. If the error occurredwhen entering an RDO operation, correct the input andretry the command.

Destination:


ERZ034045E The stanza entry key ’stanzaKey’ isembedded within another stanza entryin database class className

Explanation: CICS has unexpectedly encountered astanza key stanzaKey when scanning the attributes for astanza record in the class. This condition occurs eitherbecause the blank separator line between two stanzarecords in the class is missing, or because a ’:’ (ratherthan an ’=’) has been encountered after an attributename. Further messages are generated identifying thedatabase stanza entry containing the unexpected key.

System action: CICS ignores the key and continuesconverting the remaining attributes to check for furthererrors. If the error occurred during startup, CICSabnormally terminates the region. If the error occursduring a Resource Definition Online (RDO) session,CICS terminates the current RDO operation.

User response: If the error is in a CICS database entry,edit the stanza entry identified by subsequent messagesto add the missing blank line between the stanzaentries. If necessary, recover the database stanza from abackup.

Destination:


ERZ034047E Attribute ’attributeName’: ValueattributeValue out of range (minimumminimumValue, maximum maximumValue)

Explanation: The attribute value attributeValue is toobig or too small for the attribute. The allowableminimum value minimumValue and maximum valuemaximumValue are given. If the error is detected in aCICS database stanza file, rather than user input,further messages are generated identifying the databasestanza entry containing the invalid value.



Destination:


ERZ034048E Attribute ’attributeName’: ValueattributeValue out of range (minimumminimumValue, maximum maximumValue)

Explanation: The attribute value attributeValue is toobig or too small for the attribute. The allowableminimum value minimumValue and maximum value

ERZ034043E • ERZ034048E


maximumValue are given. If the error is detected in aCICS database stanza file, rather than user input,further messages are generated identifying the databasestanza entry containing the invalid value.



Destination:


ERZ034049W Attribute ’attributeName’: Unexpecteddata ’data’ ignored

Explanation: The attribute value contains unexpecteddata. If the error is detected in a CICS database stanzafile, rather than user input, further messages aregenerated identifying the database stanza entrycontaining the invalid value.

System action: If this error occurs during startup,CICS continues to bring up the region. If the erroroccurs during a Resource Definition Online (RDO)session, CICS terminates the current RDO operation.


Destination:


ERZ034050E Attribute ’attributeName’: Value’attributeValue’ is an invalid key for classclassName

Explanation: The attribute value attributeValue is usedas a key for the database class className. The value isan invalid key for that class. If the error is detected in aCICS database stanza file, rather than user input,further messages are generated identifying the databasestanza entry containing the invalid value.


User response: If the error is in a CICS database entry,edit the stanza entry identified by subsequent messagesto correct the attribute value. If necessary, recover the

database stanza from a backup. If the error occurredwhen entering an RDO operation, correct the input andretry the command.

Destination:


ERZ034051E Vetoed attempt to insert or alter runtimedatabase entry ’resourceName’ in classclassName

Explanation: An attempt to insert or commit anupdate to an entry, in the run-time database, has beenvetoed. Previous message(s) have been generateddetailing the error(s) in the entry.

System action: The insert or update operation has notbeen performed.

User response: Take the actions indicated by theprevious messages detailing the errors encountered andretry the insert operation.

Destination:

console.msg

ERZ034052E Attribute ’attributeName’: Non-ASCIIcharacter encountered

Explanation: The attribute’s string value containsunexpected non-ASCII data. Only ASCII characters areallowed in this attribute’s string value. If the error isdetected in a CICS database stanza file, rather than userinput, further messages are generated identifying thedatabase stanza entry containing the invalid value.



Destination:


ERZ034055E Attribute ’attributeName’: No room inCICS internal buffer

Explanation: CICS found insufficient buffer spaceavailable to accommodate data for the attribute’attributeName’, when converting the data from internalto external (stanza) format.

System action: If this error occurs in a region, CICSabnormally terminates the region. If the error occursduring a Resource Definition Online (RDO) session,CICS terminates the current RDO operation.

ERZ034049W • ERZ034055E


User response: Retry the operation. If this errorcontinues to occur contact, your support organization.

Destination:


ERZ034057E Unsuccessful Region Pool memoryallocation when updating runtimedatabase usage count for entry’resourceName’ in class ’className’

Explanation: CICS was unable to update the usagecount of the given database entry because the CICSRegion Pool does not have sufficient memory available.

System action: The runtime database operation fails.

User response: You can increase the size of the Regionpool available by restarting the region and overridingthe MaxRegionPool attribute, with a larger value, onthe command line.

Destination:

console.msg

ERZ034058E Unsuccessful Region Pool memoryallocation when saving a copy ofruntime database entry ’resourceName’ inclass ’className’

Explanation: CICS was unable to take a copy of thegiven database entry because the CICS Region Pooldoes not have sufficient memory available.

System action: The runtime database operation fails.

User response: You can increase the size of the Regionpool available by restarting the region and overridingthe MaxRegionPool attribute, with a larger value, onthe command line.

Destination:

console.msg

ERZ034059E Unsuccessful Region Pool memorydeallocation when accessing runtimedatabase

Explanation: CICS was unable to release Region Poolmemory used during an attempt to access the runtimedatabase.

System action: CICS possibly continues processing,but there is a serious problem with the runtimedatabase.

User response: There is a serious problem with yourregion. Restart the region at the earliest opportunity.

Destination:

console.msg

ERZ034060E Invalid request to run the CICS-privatetransaction CURD

Explanation: The CICS-private transaction namedCURD, used to control communications between CICSregions and RDO, cannot be started from a terminal.

System action: CICS abnormally terminates thetransaction with abend code A341.

User response: Do not attempt to run the CURDtransaction.

Destination:

CSMT

ERZ034061E Invalid data in Resource DefinitionOnline (RDO) request to CICS-privatetransaction CURD

Explanation: The CICS-private transaction namedCURD, used to control communications between CICSregions and RDO, received invalid data from RDO.

System action: CICS abnormally terminates thetransaction without performing the requested RDOoperation on the runtime database.

User response: Use CEMT to check that theconfiguration of the CURD transaction and itscorresponding program are correct. Fix any errors andretry the operation. If you cannot solve the problem,contact your support organization.

Destination:

stderr

ERZ034062E Unable to create a pipe for RegionDefinition Online (RDO) to regioncommunications; error code’errorNumber’

Explanation: Your Resource Definition Online (RDO)operation has made an unsuccessful attempt to createthe operating system pipes for communications with aregion. The RDO request has not been sent to theregion, and CICS has therefore not performed thisoperation on the runtime database.


User response: Check that the region is available andrefer to the operating system documentation for pipe()before retrying the RDO operation.

Destination:

stderr

ERZ034057E • ERZ034062E


ERZ034064E Unable to remove backup stanza file’filePath’; error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when attempting toremove the given stanza file.


User response: Refer to the operating systemdocumentation for remove(). The temporary stanza fileis removed by the next successful operation on thestanza.

Destination:


ERZ034065E Your file access permissions do notallow you to execute ’fileName’

Explanation: You are not in the set of users who areallowed execute access to the file fileName. Subsequentmessages indicate the CICS operation that has failed.

System action: The current CICS operation fails.

User response: Log in as a user whose accesspermission allows execution of the file fileName. If youhave execute access to the file, check the region’sinstallation, in particular the file’s ownership, groupand access permissions.

Destination:

stderr

ERZ034066E Abnormal termination U3466 - Unableto cleanup runtime database onabnormal termination of a task

Explanation: CICS was unable to clean up the runtimedatabase data for the task that is terminating. This isprobably due to internal data corruption.



Destination:

console.msg

ERZ034067E Unable to execlp() the program ’fileName’used for Region Definition Online(RDO) to region communications; errorcode ’errorNumber’

Explanation: Your Resource Definition Online (RDO)operation has made an unsuccessful attempt to execlpthe program fileName that is used in communicationswith a region. The RDO request has not been sent to

the region, and CICS has therefore not performed thisoperation on the runtime database.


User response: Refer to the operating systemdocumentation for execlp().

Destination:

stderr

ERZ034068E Abnormal termination A342.CICS-private transaction CURD couldnot communicate with ResourceDefinition Online (RDO)

Explanation: The CICS-private transaction CURD,used in CICS region to RDO communications, made anunsuccessful attempt to communicate with RDO.

System action: CICS abnormally terminates theCICS-private transaction CURD.

User response: Retry the RDO operation; if theoperation continues to fail, use CEMT to check that theconfiguration of the CURD transaction and itscorresponding program are correct. Fix any errors andretry the operation. If you cannot solve the problem,contact your support organization.

Destination:

CSMT

ERZ034069E CICS self-consistency checking hasdetected an inconsistency in the internaldatabase control structure for classclassName

Explanation: Self-consistency checking by CICS hasdetected that the runtime database internal controlstructure for the database class className isinconsistent.


User response: Restart the region at the earliestpossible opportunity. If CICS self-consistency checkingcontinues to detect inconsistencies, contact yoursupport organization.

Destination:

console.msg

ERZ034070E CICS self-consistency checking hasdetected zero table entries for runtimedatabase class className in controlstructure at address ’address’

Explanation: Self-consistency checking by CICS hasdetected that the runtime database internal controlstructure, at the address given, contains no table

ERZ034064E • ERZ034070E


entries. This is inconsistent with the expect minimumof one.



Destination:

console.msg

ERZ034071E Unable to obtain read or shared lock onstanza file ’fileName’; error codeerrorNumber

Explanation: CICS was unable to complete a read orshared lock on the stanza file fileName.


User response: Refer to the operating systemdocumentation for fcntl().

Destination:


ERZ034073E Unable to close a stanza file; error codeerrorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when attempting toclose a stanza file.


User response: Refer to the operating systemdocumentation for fclose().

Destination:


ERZ034074E Unable to write to stanza file ’filePath’;error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when attempting towrite, flush data, to the stanza file filePath.


User response: Refer to the operating systemdocumentation for fflush(). CICS resilience ensures that,if the file where the fflush() failed is a permanent

database or runtime database recovery image stanzafile, it is recovered next time an operation is performedon that stanza.

Destination:


ERZ034075E Unable to find the end of a stanza file;error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when seeking the endof a stanza file.

System action: If this error occurs during regionstartup, CICS abnormally terminates the region. If theerror occurs during a Resource Definition Online (RDO)session, CICS terminates the current RDO operation.

User response: Refer to the operating systemdocumentation for fseek().

Destination:


ERZ034076E Unable to find the start position of astanza file; error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when seeking the startof a stanza file.


User response: Refer to the operating systemdocumentation for fseek().

Destination:


ERZ034077E Unsuccessful write to a stanza file; errorcode errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when writing to astanza file.


User response: Refer to the operating systemdocumentation for fwrite().

Destination:


ERZ034071E • ERZ034077E


ERZ034078E CICS self-consistency checking hasdetected a Signature inconsistency:expected ’expectedSignature’ found’actualSignature’ at address address

Explanation: Self-consistency checking by CICS hasdetected that the signature actualSignature at addressaddress is inconsistent with the expected signatureexpectedSignature



Destination:

console.msg

ERZ034079E Unable to rename stanza file’fromFilePath’ to ’toFilePath’; error codeerrorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when attempting torename fromFilePath to toFilePath.


User response: Refer to the operating systemdocumentation for rename().

Destination:


ERZ034080E CICS path buffer too small to hold pathof runtime database recovery imagestanza for class className

Explanation: A path buffer in CICS is too small tohold the full path name of the runtime databaserecovery image stanza file for the class className. Thestanza file is the stanza file itself, a backup of thestanza file, or a temporary backup of the stanza file.



Destination:

console.msg

ERZ034081E Unable to obtain the current position ina stanza file; error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when attempting toobtain the current position in a stanza file.


User response: Refer to the operating systemdocumentation for fgetpos().

Destination:


ERZ034082E CICS path buffer too small to hold pathof database stanza for class className

Explanation: A path buffer in CICS is too small tohold the full path name of the permanent databasestanza file for class className. The stanza file is thestanza file itself, a backup of the stanza file, or atemporary backup of the stanza file.



Destination:


ERZ034083E Unsuccessful attempt to updatepermanent database entry ’resourceName’in class className; your updated entry isout-of-date

Explanation: You or your operation attempted toupdate a permanent database entry using data that isbased on an out-of-date version of the entryresourceName. This is because someone else has updatedthe entry since Resource Definition Online (RDO) readthe entry that you are attempting to apply the updatesto.

System action: CICS does not amend the entry; thecurrent entry is returned.

User response: Attempt the operation again.

Destination:

stderr

ERZ034078E • ERZ034083E


ERZ034084W Attribute ’attributeName’ not supportedin database class className

Explanation: The attribute attributeName is notrecognized for the CICS database class className.

System action: CICS ignores the named attribute andcontinues handling any remaining attributes.

User response: If the error is in a permanent databaseentry, edit the stanza entry identified by subsequentmessages to remove or correct the attribute. Ifnecessary, recover the database stanza from a backup. Ifthe error occurred when entering an ResourceDefinition Online (RDO) operation, correct the inputand retry the command.

Destination:


ERZ034085E Invalid database key ’resourceName’ fordatabase class className

Explanation: The database entry key resourceName isinvalid for the CICS database class className.


User response: If the error is in a permanent databaseentry edit the stanza entry identified by subsequentmessages and correct the key. If necessary, recover thepermanent database stanza from a backup. If the erroroccurred when entering an Resource Definition Online(RDO) operation, correct the input and retry thecommand.

Destination:


ERZ034086E Attribute ’attributeName’: No dataspecified

Explanation: CICS found no value for the attributeattributeName.

System action: CICS ignores the attribute andcontinues handling any remaining attributes to checkfor further errors. The operation ultimately fails.


Destination:


ERZ034087W Permanent database entry ’resourceName’not found in class className

Explanation: CICS was unable to locate the permanentdatabase entry resourceName in the stanza file for theclass className.

System action: CICS terminates the current resourceDefinition Online (RDO) operation.

User response: Use RDO to add the given entry orcorrect your RDO request.

Destination:

stderr

ERZ034089E Stanza file ’fileName’ is empty, does nothave the mandatory default stanza

Explanation: CICS found that the database stanza filefileName is empty. Every stanza file must contain adefault stanza.

System action: If this error occurs during startup,CICS abnormally terminates region. If the error occursduring a Resource Definition Online (RDO) session,CICS terminates the current RDO operation.

User response: Edit the stanza file and add a defaultentry or recover the database stanza from a backup.

Destination:


ERZ034090E CICS database key too long for classclassName; the key is longer than themaximum of maximumKeyLength bytes

Explanation: The key is longer than the givenmaximum length maximumKeyLength for the databaseclass className.

System action: CICS does not perform the requesteddatabase operation. Further messages indicate whatdatabase operation has failed.

User response: If the error is in a permanent databaseentry, edit the stanza entry and correct the invalid key.If necessary, recover the database stanza from a backup.If the error occurred when entering an ResourceDefinition Online (RDO) operation, correct the inputand retry the command. If the error is in a runtimedatabase request, perform the appropriate actionspecified by subsequent messages indicating whatdatabase operation failed.

Destination:


ERZ034084W • ERZ034090E


ERZ034092E Resource Definition Online (RDO) isunable to communicate with region’regionName’: CICS-private transactionCURD has abnormally terminated withcode ’abendCode’

Explanation: Your RDO operation has lostcommunications with the region regionName, becausethe CICS-private transaction CURD has abnormallyterminated with the abend code abendCode.


User response: Perform any appropriate actionindicated by the abend code abendCode and retry theRDO operation.

Destination:

stderr

ERZ034094E Unable to communicate with region’regionName’: errorMessage

Explanation: Your Resource Definition Online (RDO)operation is unable to communicate with the regionregionName due to the transaction scheduler errorerrorMessage. The transaction scheduler’s error messageerrorMessage is given.


User response: Perform appropriate action dependenton the transaction scheduler error errorMessage andretry the RDO operation. Check that thecicssetupclients command has been run on this system.

Destination:

stderr

ERZ034095E Unable to communicate with region:unsuccessful attempt to allocate memoryfor the communications buffer

Explanation: Your Resource Definition Online (RDO)operation is unable to communicate with the region,because it is unable to allocate sufficient memory for aninternal communications buffer.


User response: Retry the RDO operation when themachine is less loaded.

Destination:

stderr

ERZ034096E Invalid server name ’resourceName’

Explanation: The Server name resourceName must be aname starting with /.:.


User response: Correct the input and retry thedatabase operation.

Destination:

stderr

ERZ034097E Database stanza entry ’resourceName’ forclass className, requires the missingattribute ’attributeName’

Explanation: CICS cannot find the attributeattributeName in the stanza file entry resourceName forthe class className.


User response: Edit the stanza file and add themissing attribute attributeName or recover the databasestanza from a backup.

Destination:


ERZ034098E The default entry for database classclassName is missing or contains errors

Explanation: The default database entry in the class’sstanza file is missing or contains errors that have beendetailed by previous messages. Every stanza file mustcontain a default stanza.


User response: If the default entry is missing, edit thestanza file and add the missing default entry or, ifnecessary, recover the database stanza from a backup.Otherwise, correct the default entry as indicated byprevious error messages.

Destination:


ERZ034099W Unsuccessful attempt to insert entry intoruntime database: an entry with key’resourceName’ already exists in classclassName

Explanation: CICS cannot insert the given entry intothe runtime database class because an entry with thesame key already exists.

System action: The runtime database entry is notinserted.

User response: If you wish to insert this new entry,you must delete the duplicate entry from the runtimedatabase first.

ERZ034092E • ERZ034099W


Destination:

console.msg

ERZ034100E Unsuccessful creation of runtimedatabase recovery image directory’filePath’; error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when attempting tocreate the given runtime database recovery imagedirectory filePath.


User response: Refer to the operating systemdocumentation for mkdir().

Destination:

console.msg

ERZ034101E Unsuccessful creation of runtimedatabase recovery image directory’filePath’; already exists, but is not adirectory

Explanation: CICS is unable to create the runtimedatabase recovery image directory filePath, because thepath already exists and is not a directory.


User response: Remove or move the file with thesame path as the runtime database recovery imagedirectory CICS is attempting to create, and cold startthe region.

Destination:

console.msg

ERZ034102E Unsuccessful creation of runtimedatabase recovery image stanza ’filePath’;already exists, but is not a file

Explanation: CICS is unable to create the runtimedatabase recovery image stanza file filePath, because thepath already exists and is not a file.


User response: Remove or move the directory withthe same path as the runtime database recovery imagestanza CICS is attempting to create, and cold start theregion.

Destination:

console.msg

ERZ034103E Unsuccessful creation of runtimedatabase recovery image stanza ’filePath’;error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when attempting tocreate the given runtime database recovery imagestanza file filePath. A region’s runtime databaserecovery image stanzas are created on a cold start.


User response: Refer to the operating systemdocumentation for creat() and write(). Having resolvedthe error retry a cold start of your region.

Destination:

console.msg

ERZ034104E Unsuccessful deletion entry’resourceName’ from runtime databaserecovery image class className

Explanation: CICS is unable to delete the entryresourceName from the runtime database recoveryimage. Messages indicating the error(s) encounteredhave already been written to stderr.


User response: As indicated by the previousmessage(s) detailing the errors in the deletion request.

Destination:

stderr

ERZ034105E Unsuccessful insertion of entry’resourceName’ into runtime databaserecovery image class className

Explanation: CICS is unable to insert the entryresourceName into the runtime database recovery image.Messages indicating the error(s) encountered havealready been written to stderr.


User response: As indicated by the previousmessage(s) detailing the errors in the deletion request.

Destination:

stderr

ERZ034106E Unsuccessful creation of schema stanzafile ’filePath’; error code errorNumber

Explanation: CICS detected an error given by theoperating system as errorNumber when attempting tocreate the given schema stanza file filePath.

ERZ034100E • ERZ034106E



User response: Refer to the operating systemdocumentation for creat() and write().

Destination:

console.msg

ERZ034107E Unable to remove backup file ’fileName’;error code errorNumber

Explanation: CICS is unable to delete a backup filefileName from the runtime database recovery duringcold start. The error code errorNumber was returned bythe operating system from the function remove().


User response: Refer to the operating systemdocumentation for remove() to find why CICS wasunable to remove file ’fileName’. After resolving theproblem retry the request to cold start your region.

Destination:

stderr

ERZ034108I Loading region runtime database ...

Explanation: CICS is loading the runtime database foryour region.

System action: CICS starts loading the runtimedatabase for the region.

User response: None

Destination:

console.msg

ERZ034109I ... region runtime database loaded!

Explanation: CICS has completed loading the runtimedatabase for your region.

System action: CICS continues starting the region.

User response: None

Destination:

console.msg

ERZ034110W Data items ’superfluousDataItems’ wereignored for attribute ’attributeName’. Youcan only specify correctValueCount valuesfor this attribute.

Explanation: You can only specify correctValueCountvalues for the attribute that was in error.

System action: CICS has ignored the superfluous dataitems for this attribute.

User response: Retry with the correct number ofvalues.

Destination:

stderr

ERZ034111E Version stamp in stanza for classclassName is not at the correct level

Explanation: When a patch (Program Temporary Fix)or new version is installed, the migration processautomatically increases the version number which islocated in the default stanza of every resourcedefinition file. This message appears if the versionnumber is incorrect or missing It possibly means thatsome error occurred while the patch or new versionwas being migrated. (See the TXSeries Infocenter formore on version stamps and default stanzas.)


User response: Recreate and rerun the migrationscript for this resource class. You can use the -o optionof the cicsmigrate command to ensure that error andwarning messages are stored in a log file. Serious errorsare reported to stderr. Check both for errors andwarnings. See the TXSeries Infocenter for more oncreating and running the migration script.

Destination:


ERZ034112E Attribute name ’oldAttribute’ in classclassName needs to be replaced by thenew name ’newAttribute’

Explanation: CICS has encountered the attribute nameoldAttribute in a stanza file for database class className.This attribute has been renamed to newAttribute and thenew name must be used in the stanza.

System action: CICS ignores the entry for thisattribute. If an entry for the new attribute name is notpresent in the stanza, CICS possibly terminates theregion.

User response: Edit the stanza file and replace the oldname oldAttribute with the new name newAttribute.

Destination:

console.msg

ERZ034113W Attribute name ’oldAttribute’ in classclassName has been replaced by the newname ’newAttribute’

Explanation: A command was entered specifying anattribute name, oldAttribute, which has been changed tonewAttribute.

ERZ034107E • ERZ034113W


System action: CICS accepts the input for the oldname as if it were for the new name, and continuesprocessing the command.

User response: Use the new attribute name on furthercommands.

Destination:

stderr

ERZ034114E Unsuccessful attempt to uninstall entry’entryName’ from the Runtime Database.Entry is marked as in use.

Explanation: An attempt was made to uninstall anentry from the Runtime Database. The request wasrejected as the entry is currently in use.

System action: The entry is not removed from theRuntime Database.

User response: Retry the command when the entry isno longer in use.

Destination:

console.msg

ERZ034116E Unable to access runtime databasestanza file for class className.

Explanation: You attempted to perform an operationon a runtime database class’s recovery image stanza filewhich was unable to be found.

System action: The operation terminates. The runtimedatabase operation has not been performed.

User response: Verify that the operation you areattempting to perform is valid at the current time, andthat the stanza file is supposed to exist. If the file issupposed to exist, then verify that it has not beendeleted and that the path leading to the file isaccessible.

Destination:

stderr

ERZ034117E Unable to access permanent databasestanza file for class className.

Explanation: You attempted to perform an operationon a permanent database class’s stanza file that wasunable to be found.

System action: The operation terminates. Thepermanent database request has not been performed.

User response: Verify that the operation you areattempting to perform is valid at the current time, andthat the stanza file is supposed to exist. If the file issupposed to exist, then verify that it has not beendeleted and that the path leading to the file isaccessible.

Destination:

stderr

ERZ035001I Usage: cicsppcgwycreate { -? | [-v] [-I]serverName [-m modelId][[attributeName=attributeValue]...] }

Explanation: This is the usage message for thecicsppcgwycreate command.

System action: The command terminates returning thevalue 0.

User response: See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ035003E Unable to create server ’serverName’

Explanation: The command you have entered wasunable to create a new PPC gateway named’serverName’. Accompanying messages identify thecause of the problem.

System action: The command terminates abnormally,returning the value 1.

User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem, and retry the command. If necessary, specifythe -I flag to ignore errors.

Destination:

stderr

ERZ035005E Unable to execute ’programName’

Explanation: The command you have entered wasunable to execute ’programName’.


User response: Check that programName is in adirectory specified by your PATH environmentvariable, and that you have permission to execute it.Correct the problem and retry the command.

Destination:

stderr

ERZ035006E You must be logged in as root user

Explanation: The command you have enteredperforms actions that require root authority.


User response: Login as the root user and retry thecommand.

ERZ034114E • ERZ035006E


Destination:

stderr

ERZ035007I Server ’serverName’ has been added toGSD

Explanation: An entry was added to the GatewayServer Definitions (GSD) for PPC gateway ’serverName’.


User response: None

Destination:

stderr

ERZ035008I Server ’serverName’ has been added as asubsystem

Explanation: A subsystem was created for the PPCgateway ’serverName’.


User response: None

Destination:

stderr

ERZ035009E Server ’serverName’ entry already existsin GSD

Explanation: An entry for PPC gateway ’serverName’already exists in the Gateway Server Definitions (GSD).


User response: Either use the cicsppcgwydestroycommand to remove all the server details, or retry thecommand specifying the -I flag to ignore errors.

Destination:

stderr

ERZ035010W Server ’serverName’ entry already existsin GSD

Explanation: An entry for PPC gateway ’serverName’already exists in the Gateway Server Definitions (GSD)but, since the command was invoked with the -I flag(ignore errors), the command redefines the existingentry using any overrides you have specified.


User response: None

Destination:

stderr

ERZ035011E Unable to add server ’serverName’ toGSD

Explanation: The details of PPC gateway ’serverName’were unable to be added to the Gateway ServerDefinitions (GSD). Accompanying messages identify thecause of the problem. However, the most likely cause isthat there is already an entry for a PPC gateway of thisname.


User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem and retry the command. If necessary, specifythe -I flag to ignore errors.

Destination:

stderr

ERZ035012W Unable to add a subsystem definitionfor PPC gateway ’serverName’

Explanation: Subsystem names used for PPCgateways must be unique. A subsystem definition forPPC gateway ’serverName’ was not added because thereis already a PPC gateway subsystem whose ShortNameis the same as the ShortName specified. Because youhave specified the -I flag to ignore errors the existingsubsystem definition is modified.


User response: If the name of the PPC gateway’serverName’ associated with the ShortName has notchanged then no action is necessary. However, if thePPC gateway name is different destroy the server andretry command or override ShortName with a validone.

Destination:

stderr

ERZ035013E Unable to add a subsystem definitionfor PPC gateway ’serverName’

Explanation: The command you have entered wasunable to add the details for PPC gateway ’serverName’as a subsystem. Accompanying messages identify thecause of the problem. An entry for your PPC gatewaywas not created.



Destination:

stderr

ERZ035007I • ERZ035013E


ERZ035014E A server name was not supplied

Explanation: The command you have entered requiresa PPC gateway name (for example,/.:/cics/ppc/gateway/opencics), which was notsupplied.


User response: Retry the command specifying a validPPC gateway name.

Destination:

stderr

ERZ035015E The value in environment variableERZ_SvJsYmPw is incorrect

Explanation: You have exported the environmentvariable ERZ_SvJsYmPw. This is invalid sinceERZ_SvJsYmPw is a private CICS environment variableand must not be used.


User response: Make sure that ERZ_SvJsYmPw is notset in your environment and retry the command.

Destination:

stderr

ERZ035016W Unable to remove ’directoryName’

Explanation: The command you have entered triedbut failed to delete the directory ’directoryName’ and itscontents. Accompanying messages identify the cause ofthe problem. This message indicates that the commandhas not managed to clean up and that files were notremoved.


User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem and retry the command. On UNIX you candelete the directory and its contents using the rm -rfcommand. If necessary, specify the -I flag to ignoreerrors. On Windows NT you can delete the directoryand its contents using the rd -s.

Destination:

stderr

ERZ035017I Removed ’directoryName’

Explanation: The directory ’directoryName’ wasdeleted, due to errors when creating a new PPCgateway. Accompanying messages identify the cause ofthe problem.



Destination:

stderr

ERZ035018E Unable to find ’entryName’ in GSD

Explanation: The PPC gateway details for ’entryName’was unable to be retrieved from the Gateway ServerDefinitions (GSD). Accompanying messages identify thecause of the problem.


User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem and retry the command.

Destination:

stderr

ERZ035019W Unable to add server ’serverName’ toGSD

Explanation: The details of PPC gateway ’serverName’was unable to be added to the Gateway ServerDefinitions (GSD). The most likely reason for this isthat there is already an entry for a PPC gateway of thisname. As you have specified the -I flag (ignore errors),the command continues, using the existing GSD entry.


User response: None

Destination:

stderr

ERZ035020E Unable to get server ’serverName’ fromGSD

Explanation: The details of PPC gateway ’serverName’was unable to be retrieved from the Gateway ServerDefinitions (GSD). Accompanying messages identify thecause of the problem.


User response: Use messages to determine the causeof the problem. Correct the problem and retry thecommand.

Destination:

stderr

ERZ035014E • ERZ035020E


ERZ035021I Usage: cicsppcgwylock { -? | { { -l | -u |-t } serverName } }

Explanation: This is the usage message for thecicsppcgwylock command.



Destination:

stderr

ERZ035022I Usage: cicsppcgwyshut { -? | [-f] [-c]serverName }

Explanation: This is the usage message for thecicsppcgwyshut command.



Destination:

stderr

ERZ035023E Server ’serverName’ is not running

Explanation: The PPC gateway ’serverName’ is notrunning so the command was unable to be executed.The PPC gateway writes its messages to a file calledmsg under the varDir/cics_servers directory structurein a sub-directory based upon its name (for example fora server named /.:/cics/ppc/gateway/opencics the fullpath of the message file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use the PPC gateway messages todetermine why the server is not running. If necessary,correct the problem and retry the command.

Destination:

stderr

ERZ035024E Unable to shut down server ’serverName’

Explanation: The PPC gateway ’serverName’ wasunable to be shut down. Accompanying messagesidentify the cause of the problem. The PPC gatewaywrites its messages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/ppc/gateway/opencics the fullpath of the message file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use accompanying CICS and servermessages to determine the cause of the problem.Correct the problem and retry the command.

Destination:

stderr

ERZ035025E The request to stop server ’serverName’was unsuccessful

Explanation: The command you have entered made arequest to stop the subsystem running PPC gateway’serverName’. This request did not succeed.Accompanying messages identify the cause of theproblem.


User response: If after examining the accompanyingmessages you are unable to determine the cause of theproblem, retry the command first using the -f flag(immediate shutdown) and, if that is unsuccessful, the-c flag (cancel subsystem).

Destination:

stderr

ERZ035026I The lock has been removed for server’serverName’

Explanation: The lock, which indicates that PPCgateway ’serverName’ is running, was removed.


User response: None

Destination:

stderr

ERZ035027I Usage: cicsppcgwynotify { -? |subsystemName }

Explanation: This is the usage message for thecicsppcgwynotify command.



Destination:

stderr

ERZ035028E The subsystem ’subsystemName’ hasreturned unexpectedly

Explanation: The subsystem ’subsystemName’ hasterminated unexpectedly and the cicsppcgwynotifycommand, which is handling this event, was unable to

ERZ035021I • ERZ035028E


reference the PPC gateway’s name. The most likelyreason for this is that a PPC gateway was destroyedwhile it was still running. The PPC gateway writes itsmessages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/ppc/gateway/opencics the fullpath of the message file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: If you think that the PPC gateway isstill supposed to be active, first use the subsystemname, which has the format cicsppcgwy.ShortName, toidentify which server was running in that subsystem.For example, you can use cicsget -c gsd -l to give thename of each server and cicsget -c gsd serverName togive the corresponding ShortName. Then use the PPCgateway messages to determine why the server is notrunning.

Destination:

stderr

ERZ035029E Server ’serverName’ was forciblyterminated after detection of anunexpected exit

Explanation: The PPC gateway ’serverName’terminated abnormally, not as a result of a system oruser requested shutdown, and without completing thenormal shutdown procedure. The PPC gateway writesits messages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/ppc/gateway/opencics the fullpath of the message file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use the messages from the PPCgateway and from the operating system to determinewhy the server is not running. Correct the problem andrestart the PPC gateway. If the problem persists contactyour support organization.

Destination:

stderr

ERZ035030I Authorization for server ’serverName’ hasbeen set to ’authorizationLevel’

Explanation: The authorization level of a PPCgateway indicates whether or not the server AccessControl Lists (ACLs) are checked. A value of 0 indicatesthat authorization is disabled and that ACLs are notchecked. A value of 1 indicates that ACLs are checked.


User response: None

Destination:

stderr

ERZ035031W Unable to update details of server’serverName’

Explanation: The command you have entered wasunable to change PPC gateway ’serverName’. However,as you specified the -I flag (ignore errors) on thecommand you entered, the existing details are used.Accompanying messages identify the cause of theproblem.


User response: If the details of the PPC gateway’serverName’ do not need to be modified then no actionis necessary. However, if the PPC gateway details aredifferent, use accompanying messages to determine thecause of the problem. Correct the problem and retry thecommand.

Destination:

stderr

ERZ035032E Unable to remove ’primaryRestartFile’ or’backupRestartFile’ for server ’serverName’

Explanation: When trying to cold start PPC gateway’serverName’ the command you have entered wasunable to delete the restart files that are used on anautomatic start. It is not possible to cold start a PPCgateway while either the ’primaryRestartFile’ or the’backupRestartFile’ exist. Accompanying messagesidentify the cause of the problem.


User response: This message indicates that the serverwas run and contains recoverable data that is lost on acold start. If you really want to cold start, then use theaccompanying messages to determine the cause of theproblem. Correct the problem and retry the command.

Destination:

stderr

ERZ035034E Server ’serverName’ was unable to reador write to logical volume ’volumeName’using Id ’userId’

Explanation: The PPC gateway ’serverName’ keeps allits logging information on the operating system logicalvolume ’volumeName’. In order for the PPC gateway tofunction correctly it needs to be able to read and writeto this volume. It was unsuccessful. The most likelycause of this problem is that the logical volume is notowned by ’userId’.

ERZ035029E • ERZ035034E



User response: Investigate why ’userId’ is unable toread or write to ’volumeName’. Correct the problem andretry the command. On UNIX, if the ’volumeName’ isnot owned by ’userId’ then use the operating systemcommand chown to change its ownership. OnWindows NT, consult the operating systemdocumentation on taking ownership of files.

Destination:

stderr

ERZ035036E Server ’serverName’ is already running

Explanation: The command you have entered isattempting to start a PPC gateway named ’serverName’.However, there is already a server of this namerunning.


User response: Shut down the existing PPC gatewayand retry the command.

Destination:

stderr

ERZ035037E The request to start server ’serverName’was unsuccessful

Explanation: The command you have entered made arequest to start PPC gateway ’serverName’. This requestwas unsuccessful. Accompanying messages identify thecause of the problem.



Destination:

stderr

ERZ035038I Subsystem ’subsystemName’ has beeninitialized

Explanation: The subsystem ’subsystemName’ wassuccessfully initialized and a PPC gateway was started.


User response: None

Destination:

stderr

ERZ035039I Waiting for subsystem ’subsystemName’to become active

Explanation: The subsystem ’subsystemName’ wasstarted. This message is issued while the command youhave entered waits for it to become active.


User response: None

Destination:

stderr

ERZ035040E Timed out waiting for subsystem’subsystemName’ to respond

Explanation: The subsystem ’subsystemName’ has notresponded within the time limit allowed by thecommand. The PPC gateway writes its messages to afile called msg under the varDir/cics_servers directorystructure in a sub-directory based upon its name (forexample for a server named /.:/cics/ppc/gateway/opencics the full path of the message file isvarDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg). If the msg file does not exist check that theppcgwy code is actually installed.


User response: Use the PPC gateway messages todetermine why the server is not running.

Destination:

stderr

ERZ035041E Timed out waiting for server’serverName’ to start

Explanation: The PPC gateway ’serverName’ has notresponded to Remote Procedure Calls (RPCs) withinthe time limit allowed by the command. If you wereauto starting the server (the default action), thismessage does not necessarily indicate that there is aproblem since the PPC gateway can have a largeamount of data to recover that can possibly take longerthan the timeout defined. The PPC gateway writes itsmessages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/ppc/gateway/opencics the fullpath of the message file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use the PPC gateway messages todetermine if there is a problem. If there is a problem,shut down the server (using, for example thecicsppcgwyshut command), correct the problem andretry the command. If the ppcgwy process is using a

ERZ035036E • ERZ035041E


large amount of processing time (use an operatingsystem command, for example ps, to find out thisinformation) then the PPC gateway is almost certainlystill recovering data; continue to wait for the server tobecome active. Once the server has initialized it writesa message. If the problem persists either cold start thePPC gateway, ’serverName’, in which case all itsrecoverable information is lost, or contact your supportorganization.

Destination:

stderr

ERZ035042I Server ’serverName’ is responding toRPCs

Explanation: The PPC gateway ’serverName’ isresponding to Remote Procedure Calls (RPCs). Thismeans that the server is ready to process requests.


User response: None

Destination:

stderr

ERZ035046I Usage: cicsppcgwy { -? | [-I] [-v] [-ttraceMask] [[-T traceDestination]...][serverName][[attributeName=attributeValue]...] }

Explanation: This is the usage message for thecicsppcgwy command. The server name must bespecified on a cold start. For an automatic start thecommand uses the contents of environment variableCICS_PPCGWY_SERVER.



Destination:

stderr

ERZ035047E Server ’serverName’ with log volume’volumeName’ could not be enabled

Explanation: PPC gateway ’serverName’ was not ableto be enabled for full operations, using the commandppcadmin enable server. Accompanying messagesidentify the cause of the problem. The PPC gatewaywrites its messages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/ppc/gateway/opencics the fullpath of the message file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use the accompanying messages fromCICS and from the PPC gateway to determine thecause of the problem. Correct the problem and retry thecommand.

Destination:

stderr

ERZ035048I Server ’serverName’ has been enabledsuccessfully

Explanation: The PPC gateway ’serverName’ wasenabled for full operations.


User response: None

Destination:

stderr

ERZ035049E Server ’serverName’ could not be changedto multi-user mode

Explanation: PPC gateway ’serverName’ was unable tobe changed from single-user mode to multi-user mode,using the tkadmin clear exclusiveauthority command.Accompanying messages identify the cause of theproblem. The PPC gateway writes its messages to a filecalled msg under the varDir/cics_servers directorystructure in a sub-directory based upon its name (forexample for a server named /.:/cics/ppc/gateway/opencics the full path of the message file isvarDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use the accompanying messages fromCICS and from the PPC gateway to determine thecause of the problem. Shut down the server (using, forexample the cicsppcgwyshut command), correct theproblem and retry command.

Destination:

stderr

ERZ035050I Server ’serverName’ has been startedsuccessfully

Explanation: PPC gateway ’serverName’ was startedsuccessfully and is ready for use.


User response: None

Destination:

stderr

ERZ035042I • ERZ035050I


ERZ035051E No server name has been specified

Explanation: When a PPC gateway is cold started aserver name must be specified explicitly. The contentsof the environment variable $CICS_PPCGWY_SERVERare not used.


User response: Retry the command specifying thename of a PPC gateway.

Destination:

stderr

ERZ035052W The subsystem ’subsystemName’ forserver ’serverName’ cannot be found

Explanation: The command you have entered wasunable to find the subsystem entry ’subsystemName’ forPPC gateway ’serverName’ and has assumed that it wasalready deleted. Accompanying messages can possiblyidentify the cause of the problem.


User response: If the subsystem does not exist then noaction is needed. If the subsystem exists correct anyproblems and retry the command or you can encounterproblems later if you create a new PPC gateway withthe same ShortName as server ’serverName’.

Destination:

stderr

ERZ035053E The server ’serverName’ could not bedestroyed

Explanation: The command you have entered wasunable to destroy the PPC gateway ’serverName’completely. Accompanying messages identify the causeof the problem.


User response: Use accompanying messages todetermine the cause of the problem. If necessary,correct the problem and retry the command.

Destination:

stderr

ERZ035054I The subsystem entry for server’serverName’ has been removed

Explanation: The subsystem details of PPC gateway’serverName’ were deleted.


User response: None

Destination:

stderr

ERZ035055W The subsystem entry for server’serverName’ has not been removed

Explanation: The subsystem entry for server’serverName’ was not removed because it is associatedwith a different server. Accompanying messages givemore information about the problem.


User response: None

Destination:

stderr

ERZ035056W Server ’serverName’ was not found inGSD

Explanation: There is no entry for PPC gateway’serverName’ in the Gateway Server Definitions (GSD).This is not a problem because the command you haveentered is attempting to destroy the server.


User response: None

Destination:

stderr

ERZ035057I Server ’serverName’ has been removedfrom GSD

Explanation: PPC gateway ’serverName’ was deletedfrom the Gateway Server Definitions (GSD).


User response: None

Destination:

stderr

ERZ035058W Restart file ’fileName’ could not be found

Explanation: The PPC gateway restart file ’fileName’does not exist. Since the command you have entered isattempting to destroy a PPC gateway this is not aproblem. The most likely causes of this are either thatyou are destroying a server that was already destroyedor that you are destroying a server that was neverstarted.


User response: None

Destination:

stderr

ERZ035051E • ERZ035058W


ERZ035059W Restart file ’fileName’ could not beremoved

Explanation: The PPC gateway restart file ’fileName’was unable to be deleted. Since the command you haveentered is attempting to destroy a PPC gateway this isnot a serious problem. If at a later stage you wish tocreate a new PPC gateway with the same name as theone you have just destroyed, you encounter problemsbecause restart file ’fileName’ does not match the newserver.


User response: Check the existence and accesspermissions for the file. If necessary, log on withsufficient authority and delete the file.

Destination:

stderr

ERZ035060I Restart file ’fileName’ has been removed

Explanation: The command you have entered hasdeleted PPC gateway restart file ’fileName’.


User response: None

Destination:

stderr

ERZ035061I Usage: cicsppcgwydestroy { -? | [-v]serverName }

Explanation: This is the usage message for thecicsppcgwydestroy command.



Destination:

stderr

ERZ035062E Unable to destroy active server’serverName’

Explanation: The command you have entered hasattempted to destroy PPC gateway ’serverName’. Thiswas unsuccessful because the server is currentlyrunning.


User response: Ensure that you are destroying thecorrect PPC gateway. If the server name is correct shutit down (using, for example the cicsppcgwyshutcommand) and retry the command.

Destination:

stderr

ERZ035063E Logical volume ’volumeName’ does notexist

Explanation: A PPC gateway requires logical volume’volumeName’ in order to log recoverable information.This logical volume does not exist. Accompanyingmessages give more information about the cause of thethe problem.


User response: Create logical volume ’volumeName’and retry the command. If the logical volume wascreated on a volume group other than the defaultgroup, then the environment variableCICS_PPCGWY_VG needs to be exported to referencethis new volume group. e.g : if the logical volume wascreated on vg01, then export CICS_PPCGWY_VG=vg01before retrying the command.

Destination:

stderr

ERZ035065W Server directory ’directoryName’ could notbe removed

Explanation: The PPC gateway directory’directoryName’ and its contents were unable to bedeleted. Since the command you have entered isattempting to destroy a PPC gateway this is not aproblem.


User response: No action is necessary, but if you wishto clean up, log on with sufficient authority and deletedirectory ’directoryName’ (using, for example the rm -rfcommand).

Destination:

stderr

ERZ035066I Usage: cicssmitppcgwy { -s serverName| -e } processId

Explanation: This is the usage message for thecicssmitppcgwy command. Do not run this commandfrom the command line; it is to be invoked only by thesystem administration interface.


User response: If you do not know which commandto use, please refer to the CICS documentation.

Destination:

stderr

ERZ035059W • ERZ035066I


ERZ035067E Unable to save name of PPC gateway’serverName’ into ’fileName’

Explanation: The command tried to write the name ofthe PPC gateway ’serverName’ into file ’fileName’ butwas unsuccessful.


User response: Check that you have permission tocreate ’fileName’ and that the file system is not full.Correct the problem and retry the command.

Destination:

stderr

ERZ035068E You have not selected a PPC gateway

Explanation: You have not selected a PPC gateway towork with.


User response: Select a working PPC gateway andretry the command.

Destination:

stderr

ERZ035069E Server name must be specified on a coldstart

Explanation: You have tried to cold start a PPCgateway, without specifying a server name. On a coldstart all of the the PPC gateway’s recoverableinformation is lost so, to help ensure that the ″wrong″server is not cold started, the server name must bespecified.


User response: Retry the command with the servername coded.

Destination:

stderr

ERZ035070E Usage: cicsppcgwyupdate { -nnewServerName -o oldServerName [-ppassword] [-v] [-I][[attributeName=attributeValue]...] }

Explanation: This is the usage message for thecicsppcgwyupdate command. Do not run thiscommand from the command line; it is to be andinvoked only by the system administration interface.


User response: If you do not know which command

to use, please refer to the CICS documentation.

Destination:

stderr

ERZ035071E Unable to update details of server’serverName’

Explanation: The command you have entered wasunable to change PPC gateway ’serverName’.Accompanying messages identify the cause of theproblem.



Destination:

stderr

ERZ035072W Server ’serverName’ has already been run

Explanation: The command you have entered is goingto modify the details of PPC gateway ’serverName’. Thisaction means that any of the PPC gateway’s recoverableinformation is lost and, once updated, the server needsto be cold started.


User response: None

Destination:

stderr

ERZ035073E Server ’serverName’ has already been run

Explanation: The command you have enteredattempted to modify the details of PPC gateway’serverName’. This server was previously run; if thecommand is allowed to continue, all of the PPCgateway’s recoverable information is lost.


User response: If you still want to modify the detailsof the PPC gateway retry the command using the -Iflag to ignore errors.

Destination:

stderr

ERZ035074E Unable to rename server ’oldServerName’as ’newServerName’ as ’newServerName’already exists

Explanation: The command you have enteredattempted rename PPC gateway ’oldServerName’ as

ERZ035067E • ERZ035074E


’newServerName’. Because PPC gateway ’newServerName’is defined in the Gateway Server Definitions (GSD),allowing this operation to continue causes PPCgateway ’newServerName’ to lose all of its recoverableinformation.


User response: If you still want to modify the detailsof the PPC gateway retry the command using the -Iflag to ignore errors.

Destination:

stderr

ERZ035075W Resource ’resourceName’ was notrecognized from the default GatewayServer Definition (GSD).

Explanation: The resource specified, was not found inthe default Gateway Server Definition (GSD).

System action: Processing continues using the defaultvalues.

User response: Check that the default entry exists inthe Gateway Server Definitions (GSD). Retry thecommand specifing the correct resource.

Destination:

stderr

ERZ035078E Usage: cicsppcgwydbadmin -s server {-P| [[attribute=<value>]...]}

Explanation: This is the usage message forcicsppcgwydbadmin . The command is not expected tobe run from the command line as it is a CICS internalfunction.

System action: The command terminates with a returncode of 1.

User response: Do not run the cicsppcgwydbadmincommand from the command line.

Destination:

stderr


Explanation: cicsppc tried to access some memory forits own working storage but was unable to do so.


User response: Ensure your machine has enoughmemory installed. Check also that you have adequatepaging space. See the Planning and Installation Guidefor more information on system resources.

Destination:

stderr

ERZ035080E Unable to add ’environmentString’ to theenvironment

Explanation: The command you entered tried to add’environmentString’ to its environment but failed to doso.


User response: Check your system is not fully loaded,as this often is the result of a lack of processingmemory. Check also that you have installed yoursystem correctly.

Destination:

stderr

ERZ035081I Waiting for server ’serverName’ toinitialize.

Explanation: The server ’serverName’ was startedasynchronously and this message is issued while thecommand you have entered waits for it complete thefirst stage of its initialisation.


User response: None

Destination:

stderr

ERZ035082E PPC gateway operation ’opCode’ failedwith error (errorCode) ErrorText

Explanation: While executing cicppcgwy, a CICSToolkit error occurred that prevents the operation fromcompleting succesfully.

System action: The command halts its attempt tocreate the current PPC file and skip to the next stage.

User response: Use the error code and text in themessage to identify the cause of the failure and correctthe error.

Destination:

stderr

ERZ036003E You must be logged on as root on UNIXor as Administrator on Windows NT

Explanation: You attempted to run a command withinsufficient authority. On UNIX you must be logged onas root. On Windows NT you must be logged on to auserid that is a member of the cicsgroup orAdministrators groups.

System action: The command abnormally terminatesreturning the value 1.

User response: Log on correctly and retry thecommand.

Destination:

ERZ035075W • ERZ036003E


stderr

ERZ036007E Unable to start server ’serverName’

Explanation: The Server ’serverName’ was unable to bestarted.


User response: Use accompanying messages todetermine the cause of problem. Correct the problemand retry the command.

Destination:

stderr

ERZ036008E Unable to access server definitions aslocked with file ’fileName’

Explanation: A CICS administration command wasentered that must secure a server definitions lock.However, the lock for this server was already taken byanother user. This can possibly mean that the server iscurrently running, or some other command or processis administering the server definitions, or the lock wastaken by a command or process that subsequentlyterminated abnormally, leaving the lock (this happensif, for example, the machine is shut down while theserver is running or while administration commandsare in progress).

System action: The command exits returning thevalue 1.

User response: If there are other CICS administrationcommands in progress then wait for them to finish andretry the command. Otherwise remove the lock filespecified in the message text and retry the command.

Destination:

stderr

ERZ036009W Waiting for lock

Explanation: A server command requires a server lockto be taken - however, the lock is already being held byanother user.

System action: The command loops until the lock canbe taken.

User response: None

Destination:

stderr

ERZ036034E Unable to execute ’executableName’

Explanation: The command was unable to execute’executableName’.

System action: Command abnormally terminatesreturning the value 1.

User response: Check that the executable is in adirectory that is named in your PATH variable, andthat you have permission to execute it.

Destination:

stderr

ERZ036050E Unable to contact host ’hostName’

Explanation: An operation to be executed on remotemachine ’hostName’ failed because the machine wasunable to be contacted.


User response: Determine cause of communicationfailure, reestablish contact with machine and retrycommand.

Destination:

stderr

ERZ036052W Lock file ’fileName’ was not found

Explanation: The lock file ’fileName’, used for lockinga server, cannot be removed during an unlockprocedure.


User response: The file was not supposed to bepresent, though this does not prevent processing fromcontinuing. The server is left in an unlocked state.

Destination:

stderr

ERZ036053E Unable to create lock file ’fileName’

Explanation: The lock file ’fileName’, used for lockinga server, cannot be created. Accompanying messagesidentify the exact cause of the problem.


User response:

Check both that you have permission to create files inthe following directories (and their sub-directories) andthat they are available:

v /var/cics_servers/SSD

v /var/cics_servers/GSD

See accompanying messages for further information.Correct the problem and retry the command.

Destination:

stderr

ERZ036007E • ERZ036053E


ERZ036054E Unable to remove lock file ’fileName’

Explanation: The lock file ’fileName’, used for lockinga server, cannot be removed during a lock or unlockprocedure. Accompanying messages identify the exactcause of the problem.


User response:

Check that you have permission to remove files in thefollowing directories (and their sub-directories) andthat they are available:

v /var/cics_servers/SSD

v /var/cics_servers/GSD

See accompanying messages for further information.Correct the problem and retry the command.

Destination:

stderr

ERZ036060W Subsystem definition for ShortName’shortName’ is already used by server’serverName’

Explanation: The ShortName attribute of a servermust be unique because it is used to generate thesubsystem definition name. ’shortName’ is already usedby server ’serverName’.


User response: Specify a unique ShortName valueand retry the command.

Destination:

stderr

ERZ036083E Unable to create directory ’directoryName’

Explanation: It was not possible to create serverdirectory ’directoryName’.


User response: Check the existence and permissionson all the directories named in the path of the directorybeing created. You as an administrator must be ingroup cics, and group cics must have read and executepermission on all parent directories, and also writepermission to /var/cics_servers and to/var/cics_servers/SSD (GSD if the command applies toa PPC gateway rather than a SFS) and itssub-directories. See accompanying messages for furtherinformation. Correct the problem, and retry thecommand.

Destination:

stderr

ERZ036084E Unable to change access permissions ondirectory ’directoryName’

Explanation: A CICS command is unable to changethe access permissions on directory ’directoryName’.Either the directory does not exist, or you do not havethe required privileges to change its ownership.


User response: Check the existence and permissionson all the directories named in the path of the directorybeing created. You, as an administrator, must be ingroup cics, and group cics must have read and executepermission on all parent directories, and also writepermission to /var/cics_servers and to/var/cics_servers/SSD (GSD if the command applies toa PPC gateway rather than a SFS) and itssub-directories. See accompanying messages for furtherinformation. Correct the problem, and retry thecommand.

Destination:

stderr

ERZ036126I Directory ’directoryName’ created

Explanation: The directory ’directoryName’ wascreated.


User response: None

Destination:

stderr

ERZ036139E Internal error in function ’functionName’

Explanation: An internal error has occurred in thespecified function.



Destination:

stderr

ERZ036140E The server ’serverName’ cannot bereached.

Explanation: The server does not exist.


User response: Ensure you are trying to use a serverthat exists. Check previous messages for any othererrors.

Destination:

ERZ036054E • ERZ036140E


stderr

ERZ036141E Usage: cicspingserver serverName

Explanation: You entered the cicspingservercommand incorrectly.


User response: Retry the command using the correctsyntax.

Destination:

stderr

ERZ036146W Unable to access details on user ’userId’

Explanation: The command you entered was unableto access details on user ’userId’. This was probablybecause the user does not exist. Previous messagesidentify the exact problem.


User response: None

Destination:

stderr

ERZ036147E Unable to access details on user ’userId’



User response: Ensure that user ’userId’ exists andretry the command.

Destination:

stderr

ERZ036148W Directory ’directoryName’ is notaccessible by user ’userId’ or does notexist

Explanation: Either ’directoryName’ is not readable,writable and executable by ’userId’ or does not exist.


User response: None

Destination:

stderr

ERZ036149E Directory ’directoryName’ is notaccessible by user ’userId’ or does notexist

Explanation: Either ’directoryName’ is not readable,writable and executable by ’userId’ or it does not exist.


User response: Ensure ’directoryName’ exists and isreadable, writable and executable by ’userId’.

Destination:

stderr

ERZ036150E Unable to change ownership of keytabfile ’fileName’ to user ’userId’

Explanation: An attempt at changing the owner of’fileName’ to ’userId’ was unsuccessful. Previousmessages identify the exact problem.


User response: Previous messages identify theproblem.

Destination:

stderr

ERZ036152E Server ’serverName’ started, but has notbeen initialized

Explanation: The Server ’serverName’ was started butwas unable to be initialized.


User response: Use any previous messages to helpidentify the problem. The server must be shut downand restarted before it can be used.

Destination:

stderr

ERZ036156E Unsuccessful attempt at changing ownerof ’fileName’ to ’userId’

Explanation: At attempt at changing the ownership offile or directory ’fileName’ to user ’userId’ wasunsuccessful.


User response: Make sure ’fileName’ exists and is localto the machine (it cannot be a mounted directory).Retry the command.

Destination:

stderr

ERZ036141E • ERZ036156E


ERZ036157E Subsystem definition ’subsystemName’cannot be found

Explanation: A subsystem definition for’subsystemName’ was not found. The most likely reasonfor this is that the server name was entered incorrectly,or the subsystem definition was prematurely deleted.Accompanying messages identify the exact cause of theproblem.


User response: Use accompanying to determine thecause of the problem. Correct the problem and retry thecommand.

Destination:

stderr

ERZ036169E Usage: cicsdefaultservers { -? | [ -s | -c |-p ] }

Explanation: You entered the cicsdefaultserverscommand incorrectly.


User response: Retry the command using the correctsyntax. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ036170E Unable to install server definitions’fileName’

Explanation: The cicsdefaultservers commandattempted to install a default version of the file’fileName’ but the copy failed.

System action: The command attempts to continue,but a failure return code is given on commandcompletion.

User response: Check to see if the specified file exists.If the file already exists no further action from thiscommand is required but to ensure no other commandsfail check the access permissions on the file. If the filedoes not exist check that you have permission to writeto the directory and retry the command.

Destination:

stderr

ERZ036171I The following server definitions mayneed migrating ’fileName’

Explanation: The cicsdefaultservers commandattempted to install new versions of the default serverdefinitions but they already exist. Some migration ispossibly necessary to upgrade the existing server

definitions to the current CICS release.

System action: The command terminates normallyreturning the value 0.

User response: If you have not already done so,migrate the specified stanza files using the cicsmigratemigration tool.

Destination:

stderr

ERZ036188I Usage: cicsdefaultservers { -? | [ -s | -c |-p ] }

Explanation: This is the usage message for thecicsdefaultservers command.



Destination:

stderr

ERZ036191E Both ’primaryRestartFile’ and’backupRestartFile’ are missing for server’serverName’

Explanation: The server restart files were unable to befound.


User response: On an auto start of a server at leastone of the restart files must be available. If neitherrestart file is available, you need to cold start(initialize).

Destination:

stderr

ERZ036192W Restart file ’restartFileName’ is missingfor server ’serverName’

Explanation: The restart file ’restartFileName’ for server’serverName’ was unable to be found.

System action: Processing continues using the otherrestart file.

User response: None. The other restart file is rebuiltduring server startup.

Destination:

stderr

ERZ036157E • ERZ036192W


ERZ036195W The archives directory ’directoryName’ forserver ’serverName’ does not exist

Explanation: The archives directory for the serverdoes not exist but is rebuilt.

System action: Processing continues and rebuilds thearchive directory.

User response: None. The archive directory is rebuilt.

Destination:

stderr

ERZ036196E The archives directory ’directoryName’ forserver ’serverName’ does not exist

Explanation: The archives directory for the serverdoes not exist.

System action: The command abnormally terminatesreturning the value 1

User response: Retry the command specifying the -Iflag (ignore errors), which causes the directory to berebuilt.

Destination:

stderr

ERZ036198I Restart files located for server’serverName’

Explanation: The restart files for the server werelocated.


User response: None

Destination:

stderr

ERZ036200I Archives directory located for server’serverName’

Explanation: The archives directory for the serverwere located.


User response: None

Destination:

stderr

ERZ036202E Server ’serverName’ is already running

Explanation: The attempted operation failed because aServer of the same name is already running


User response: If necessary, shut down the server of

the same name and restart the server.

Destination:

stderr

ERZ036203E Unable to create logical volume’volumeName’ for server ’serverName’

Explanation: The command you have entered wasunable to create logical volume ’volumeName’ on anoperating system logical volume. Accompanyingmessages identify the exact cause of the problem.


User response: Use the accompanying CICS andserver messages to determine the cause of the problem.Correct the problem and retry the command.

Destination:

stderr

ERZ036204I Created logical volume ’volumeName’ forserver ’serverName’

Explanation: The command you have entered hassuccessfully created logical volume ’volumeName’ on anoperating system logical volume. This is used by server’serverName’ for logging.


User response: None

Destination:

stderr

ERZ036205E Unable to initialize logical volume’volumeName’ for logging by server’serverName’

Explanation: The Server ’serverName’ unsuccessfullyattempted to initialize logical volume ’volumeName’ sothat it can be used to store log data, using the tkadmininit logvol command. Accompanying messages identifythe exact cause of the problem. The server writes itsmessages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aSFS named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg and for a PPC gateway named/.:/cics/ppc/gateway/opencics the full path of themessage file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use accompanying CICS and servermessages to determine the cause of the problem. OnWindows NT you can find the drive letter of the disk

ERZ036195W • ERZ036205E


containing the msg file by using the cicsnameserversdir command. Shut down the server (using, forexample either the cicssfsshut or cicsppcgwyshutcommand), correct the problem and retry thecommand.

Destination:

stderr

ERZ036206I Initialized logical volume ’volumeName’initialized for logging by server’serverName’

Explanation: Logical volume ’volumeName’ wassuccessfully initialized and can be used to store logdata for server ’serverName’.


User response: None

Destination:

stderr

ERZ036207E Unable to create log file ’logFileName’ forserver ’serverName’

Explanation: When trying to create log file’logFileName’ so it can be used to store the recoverabledata generated by server ’serverName’, using thetkadmin create logfile command, the command youhave entered has encountered a problem.Accompanying messages identify the exact cause of theproblem. The server writes its messages to a file calledmsg under the varDir/cics_servers directory structurein a sub-directory based upon its name (for example fora SFS named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg and for a PPC gateway named/.:/cics/ppc/gateway/opencics the full path of themessage file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use accompanying CICS and servermessages to determine the cause of the problem. OnWindows NT you can find the drive letter of the diskcontaining the msg file by using the cicsnameserversdir command. Shut down the server (using, forexample either the cicssfsshut or cicsppcgwyshutcommand), correct the problem and retry thecommand.

Destination:

stderr

ERZ036208I Created log file ’logFileName’ for server’serverName’

Explanation: The command you have entered hassuccessfully created log file ’logFileName’ so it can beused to store the recoverable data generated by server’serverName’.


User response: None

Destination:

stderr

ERZ036209E Unable to access logical volume’volumeName’ for server ’serverName’

Explanation: The command you have entered isunable to obtain information about logical volume’volumeName’ which stores log data for server’serverName’, using the tkadmin query logvolcommand. The most likely reason for this is that youare trying to auto start a server that was never started.The server writes its messages to a file called msgunder the varDir/cics_servers directory structure in asub-directory based upon its name (for example for aSFS named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg and for a PPC gateway named/.:/cics/ppc/gateway/opencics the full path of themessage file is varDir/cics_servers/GSD/cics/ppc/gateway/opencics/msg).


User response: Use accompanying CICS and servermessages to determine the cause of the problem. OnWindows NT you can find the drive letter of the diskcontaining the msg file by using the cicsnameserversdir command. Shut down the server (using, forexample, either the cicssfsshut or cicsppcgwyshutcommand), correct the problem and retry thecommand.

Destination:

stderr

ERZ036210I Server ’serverName’ has been initialized

Explanation: Server ’serverName’ is ready to processrequests.


User response: None

Destination:

stderr

ERZ036206I • ERZ036210I


ERZ036211E Unable to query media archive settingfor server ’serverName’

Explanation: The command you have entered isunable to query the media archive setting of server’serverName’, using the tkadmin query mediaarchivingcommand. The server writes its messages to a filecalled msg under the varDir/cics_servers directorystructure in a sub-directory based upon its name (forexample for a SFS named /.:/cics/sfs/default the fullpath of the message file is varDir/cics_servers/SSD/cics/sfs/default/msg)


User response: Use accompanying CICS and servermessages to determine the cause of the problem. OnWindows NT you can find the drive letter of the diskcontaining the msg file by using the cicsnameserversdir command. Shut down the server (using, forexample, the cicssfsshut command), correct theproblem and retry the command.

Destination:

stderr

ERZ036212E Unable to enable media archiving forserver ’serverName’

Explanation: The command you have entered wasunable to enable the archiving of log records for server’serverName’, using the tkadmin enable mediaarchivingcommand. The server writes its messages to a filecalled msg under the varDir/cics_servers directorystructure in a sub-directory based upon its name (forexample for a SFS named /.:/cics/sfs/default the fullpath of the message file is varDir/cics_servers/SSD/cics/sfs/default/msg)


User response: Use accompanying CICS and servermessages to determine the cause of the problem. OnWindows NT you can find the drive letter of the diskcontaining the msg file by using the cicsnameserversdir command. Shut down the server (using, forexample the cicssfsshut command), correct the problemand retry the command.

Destination:

stderr

ERZ036213I Enabled media archiving for server’serverName’

Explanation: Server ’serverName’ archives log records.


User response: None

Destination:

stderr

ERZ036214W Need to backup server ’serverName’ formedia archiving to be effective

Explanation: Media archiving was just enabled on aserver that previously ran with it disabled. However,until the server is subsequently backed up (by usingthe tkadmin backup command) we do not have animage to restore to.


User response: Back up the server.

Destination:

stderr

ERZ036215E Unable to disable media archiving forserver ’serverName’

Explanation: The command you have entered wasunable to stop the archiving of log records for server’serverName’, using the tkadmin disablemediaarchiving command. The server writes itsmessages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aSFS named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg)


User response: Use accompanying CICS and servermessages to determine the cause of the problem. OnWindows NT you can find the drive letter of the diskcontaining the msg file by using the cicsnameserversdir command. Shut down the server (using, forexample, the cicssfsshut command), correct theproblem and retry the command.

Destination:

stderr

ERZ036216I Disabled media archiving for server’serverName’

Explanation: Server ’serverName’ not archives logrecords.


User response: None

Destination:

stderr

ERZ036211E • ERZ036216I


ERZ036217E The RPC error message is ’errorMessage’and RPC return code is ’returnCode’

Explanation: While attempting to communicate with aserver an error occurred that prevented the operationfrom completing successfully.


User response: Ensure you are trying to use a serverthat exists. Check previous messages for any othererrors.

Destination:

stderr

ERZ036218E Usage: cicsgetbindingstring serverName

Explanation: The program must be called with exactlyone parameter.


User response: Issue the command specifying thename of the server for which the binding string isrequired.

Destination:

stderr

ERZ036219E Unable to find server ’serverName’

Explanation: cicsgetbindingstring was unable to findbinding information for server ’serverName’.


User response: Check that the server is running.

Destination:

stderr

ERZ036220I Usage: cicsgetbindingstring serverName

Explanation: This is the usage message for thecicsgetbindingstring command.

System action: The command completed returning thevalue 0.


Destination:

stderr

ERZ036221E Unable to read file ’fileName’, errno’errorNumber’

Explanation: The cicsdefaultservers commandattempted to read the file ’fileName’, but the commandfailed.


User response: Check you have the necessarypermissions to read the file. Check also that the file isnot corrupted. This error can possibly indicate thatCICS is not installed properly.

Destination:

stderr

ERZ036222W Unable to change details of file’fileName’, errno ’errorNumber’

Explanation: An attempt at changing the owner of’fileName’ to user ’errorNumber’ failed.

System action: The command can terminateabnormally.

User response: Examine the value of errno todetermine what the exact problem is.

Destination:

stderr


Explanation: CICS tried to allocate some memory fora process but was unable to do so.


User response: Ensure your machine has enoughmemory installed. Check also that your paging space isadequate. See the Planning and Installation Guide formore information on system resources.

Destination:

stderr

ERZ036224E Unable to close file ’fileName’

Explanation: CICS tried to close the file ’fileName’ butwas unable to do so. This is possibly because the filewas corrupted or because a spurious signal interruptedthe process.


User response: Try the command again. If theproblem persists check the installation of the CICSsystem.

Destination:

stderr

ERZ036225E Server operation ’opCode’ failed witherror (errorCode) ErrorText

Explanation: While attempting to commincate with aserver an error occurred that prevented the operationfrom compleing succesfully.

ERZ036217E • ERZ036225E


System action: The error is returned to the callingcommand.


Destination:

stderr

ERZ036226E An RPC operation ’opCode’ failed witherror (errorCode) ErrorText

Explanation: While attempting to communicate with aserver error occurred that prevented the operation fromcompleting successfully.

System action: The error is returned to the callingcommand.


Destination:

stderr

ERZ036227E Unable to locate the Server ’serverName’

Explanation: The current command was unable tolocate the server identified using the Cell DirectoryServices (CDS).

System action: If an error occurred, an additionalerror message is logged with exact details of the failure.

User response: Verify that the server exists.

Destination:

stderr

ERZ036228E Unable to locate the Server ’serverName’

Explanation: The current command was unable tolocate the server in the End-Point database.

System action: If an error occurred, then an additionalerror message is logged with exact details of the failure.

User response: Verify that the server exists.

Destination:

stderr

ERZ036229E Server ’serverName’ contacted but servernot fully operational

Explanation: The current command was able tocontact the server identified in the message, but iffailed to verify that the server is fully operational.

System action: The command cannot continue.

User response: Verify that the server is running and

has fully completed its initialisation. When initialisationis fully complete reissue the command.

Destination:

stderr

ERZ036230E Log file ’logfileName’ on server’serverName’ could not be enabled.

Explanation: Log file ’logfileName’ on the server (SFS)’serverName’ was not able to be enabled. The log file isused to store the recoverable data generated by theserver. Accompanying messages identify the cause ofthe problem.


User response: Use the accompanying CICS and SFSmessages to determine the cause of the problem.

Destination:

stderr

ERZ036231I Log file ’logfileName’ on server’serverName’ has been enabled.

Explanation: Log file ’logfileName’ was enabled tostore the recoverable data generated by the server’serverName’.


User response: None

Destination:

stderr

ERZ036232E Logical volumes on server ’serverName’could not be recovered.

Explanation: Server ’serverName’ unsuccessfullyattempted to bring its data volumes up to date withinformation from its log file. Accompanying messagesidentify the cause of the problem.


User response: Use accompanying CICS and servermessages to determine the cause of the problem.

Destination:

stderr

ERZ036233I Logical volumes on server ’serverName’have been recovered.

Explanation: The Structured File Server’s (SFS) datavolumes were updated with the information in theserver’s log file.


ERZ036226E • ERZ036233I


User response: None

Destination:

stderr

ERZ036234E Unable to create directory ’dirName’

Explanation: The command you entered tried to createthe specified directory but was unable to do so.


User response: Check that the directory specified is ina directory that you have permission to write to. Checkalso that there is space in the file system.

Destination:

stderr

ERZ037001E Usage: cicssfsimport -i schemaFileName-s serverName [-I] [-f fileName [-xindexName ...] ...]

Explanation: The command was invoked withincorrect arguments.

System action: The command exits with return code 1.

User response: Ensure the command is called withcorrect arguments.

Destination:

stderr

ERZ037002W Schema file ’schemaFileName’ does notcontain any details on file ’fileName’

Explanation: There is no stanza entry for fileName inthe schema file.

System action: The cicssfsimport command continues.

User response: Specify a file that does exist in theschema file.

Destination:

stderr

ERZ037003W Schema file ’schemaFileName’ does notcontain details of index ’indexName’ forfile ’fileName’

Explanation: The entry for fileName in the schema fileschemaFileName contains no details of index indexName.

System action: The cicssfsimport command continues.

User response: Specify an index for file fileName thatexists in schemaFileName.

Destination:

stderr

ERZ037004E Destination file ’fileName’ does not havewrite permission.

Explanation: You have tried to write to destination file’fileName’, but CALF has found that the file’spermissions do not allow you to do so.

System action: CALF continues.

User response: Make sure that the destination file iswriteable. You can use the command EXEC CICS SETFILE(fileName) ADDABLE to do this.

Destination:

stderr

ERZ037005E Destination file and source file do notmatch.

Explanation: CALF has detected that the source anddestination files are both local but have inconsistent fileformats. This is possibly because one file containsvariable record lengths but the other contains fixedrecord lengths, one file is KSDS, the other is RRDS orbecause the record lengths of the two files do notmatch.


User response: You are not able to import databetween these files as they are currently defined. Checkto see if one file is of variable length and the other offixed length. Check that they are both of the same type,(both KSDS, both RRDS or both ESDS files). Check alsothe record lengths of the two files are the same. If oneof these values is different across source anddestination files you need to redefine the destinationfile to be the same as the source file.

Destination:

stderr

ERZ037007E Source record length shorter thandestination record length.

Explanation: CALF has detected that the source file isremote and a record was read from it whose length isless than the record length of the fixed record lengthdestination file. The PAD field from the CALFtransaction was not set to ’Y’.

System action: CALF abnormally terminates withA373.

User response: You either have to redefine the recordlength of the destination file to be the same as that ofthe source file or enable padding to occur by setting thePAD field to ’Y’.

Destination:

stderr

ERZ036234E • ERZ037007E


ERZ037008E Source record length longer thandestination record length.

Explanation: The source file is remote and a recordwas retrieved whose record length is longer than therecord length of the destination file.


User response: You must define the record length ofthe destination file to be consistent with that of thesource file.

Destination:

stderr

ERZ037009E Source key does not match embeddedkey in destination.

Explanation: CALF has detected that the key retrievedfrom a source record (which is used as the RIDFLD in adestination record) does not match the embedded keyin the destination record.


User response: CALF is not able to write the record.Ensure that the source and destination files havecompatible definitions.

Destination:

stderr

ERZ037010I Copy has completed successfully -’recordCount’ record(s) copied.

Explanation: CALF has successfully copied all recordsfrom the source file to the destination file.


User response: You can press PF3 to end the CALFsession and continue with other CICS work, or pressPF2 to import a new file.

Destination:

stderr

ERZ037011E Unsuccessful attempt at opening file’fileName’.

Explanation: CALF was unable to open file ’fileName’.This is possibly because the file was not defined in theruntime database, or you are not authorized to use thefile. Further information is possibly available in one ofthe CICS message files.


User response: Check that the file is defined in theFile Definitions. Check also the Structured File ServerAccess Control List (SFS ACL) for the file gives you the

necessary permissions to read the file. Check the CICSmessage files for more information.

Destination:

stderr

ERZ037012E The value entered for SYNCPOINT isnot a valid number.

Explanation: CALF has detected that you haveentered a SYNCPOINT value that is not a validnumber. This field can contain only digits ranging fromzero to nine.


User response: Retry the transaction, specifying avalid number, such that it only consists of digitsranging from zero to nine.

Destination:

stderr

ERZ037013E The source and destination files havenot been opened successfully yet.

Explanation: You have tried to import the source file(using function key PF9 before you have opened thefiles using PF5.


User response: Ensure you use PF5 to open the filesbefore you use PF9 to import the source file. It is notenough to open the files manually using for exampleCECI SET FILE(fileName) OPEN; when CALF does thisit also performs extensive checking on both files.

Destination:

stderr

ERZ037014E Error reading from file ’fileName’.Response Code ’responseText’(responseCode)

Explanation: CALF has encountered an error whiletrying to read a record from the source file. Furtherinformation is possibly available in one of the CICSmessage files.


User response: Check the CICS message files forfurther guidance on resolving the problem.

Destination:

stderr

ERZ037008E • ERZ037014E


ERZ037015E Key already exists in the destinationfile.

Explanation: The destination file’s index is defined asunique and an attempt was made to write a record to itwith the same key as an existing record.


User response: Either set the DUPREC field to ’Y’ andtry again or allow duplicates on the index of the SFSfile being written to. If neither of these options issuitable, you must abandon the import.

Destination:

stderr

ERZ037016E The source file ’fileName’ is notbrowsable.

Explanation: CALF has detected that you do not havethe necessary permissions to browse the source filefileName.


User response: Ensure that the file is browsable, byissuing the command CECI SET FILE(fileName)BROWSABLE.

Destination:

stderr

ERZ037017E Value of DUPREC and PAD must be Yor N.

Explanation: CALF has detected that you have set thevalue of the PAD or DUPREC field to be somethingother than ’Y’ (for ’YES’) and ’N’ (for ’NO’).


User response: Ensure that the values in the PAD andDUPREC fields contain only the characters ’Y’ or ’N’.

Destination:

stderr

ERZ037018E Destination file must be local.

Explanation: The file used as the destination is aremote file. Only a local file can be used as thedestination.


User response: Ensure that the file you wish to importdata to resides on your local machine.

Destination:

stderr

ERZ037019E Error writing to file ’fileName’. ResponseCode ’responseText’ (responseCode)

Explanation: CALF has encountered an error whiletrying to write a record to the destination file. Furtherinformation is possibly available in one of the CICSmessage files.


User response: Check the CICS message files forinformation regarding the state of the source file andthe Structured File Server (SFS).

Destination:

stderr

ERZ037020E File ’fileName’ already exists on server’serverName’.

Explanation: The file ’fileName’ was already created onthe server ’serverName’.

System action: cicssfsimport exits with return code 3.

User response: You can either supply the -I flag to thecicssfsimport command, which ignores errors, or youcan use the Structured File Server (SFS) administrationcommand to destroy the file if you want to recreate it.

Destination:

stderr

ERZ037021W File ’fileName’ already exists on server’serverName’.

Explanation: The file ’fileName’ was already created onthe server ’serverName’.


User response: If you believe that the file on theserver is the wrong one you can use the Structured FileServer (SFS) administration command to destroy thefile.

Destination:

stderr

ERZ037022W Could not create index ’indexName’ forfile ’fileName’.

Explanation: The index ’indexName’ was unable to becreated for file ’fileName’.


User response: Check previous messages for anyStructured File Server (SFS) errors detailing why theindex was unable to be created.

Destination:

stderr

ERZ037015E • ERZ037022W


ERZ037027E Cannot read schema file ’fileName’

Explanation: The schema file specified with the -ioption was not found, or was found but is empty, orwas found but is not readable by cicssfsimport.


User response: Check that the schema file exists andis not empty. Ensure that the file has the correctpermissions to allow read access. Retry the commandusing the correct relative or absolute path of theschema file.

Destination:

stderr

ERZ037030E An unsuccessful attempt was made tochange the Access Control List (ACL)for the SFS file ’fileName’

Explanation: cicssfsimport was unsuccessful whenattempting to modify the ACL for the SFS file fileName.


User response: Further messages identify the problem.Check the cicssfsimport trace file for furtherinformation. Ensure that the SFS is running and thatyou have sufficient authority to modify the ACLcontrolling access to the file. You possibly have to alterthe ACL by hand; the permissions required for the’any_other’ and ’unauthenticated’ ACL entry type are’ADEIQRU’.

Destination:

stderr

ERZ037031W Invalid PF or PA key pressed.

Explanation: You have pressed an undefined programfunction (PF) or program attention (PA) key.

System action: CICS ignores the keystroke.

User response: Use a valid PF or PA key. Valid keysare displayed at the bottom of the screen. You can alsouse the enter key.

Destination:

stderr

ERZ037032I CALF has ended normally. Ready fornext transaction.

Explanation: This is the message displayed whenCALF terminates.



Destination:

CALF user terminal

ERZ037033E Source and destination files areidentical.

Explanation: CALF has detected that the source anddestination file names you have used are the same, andthat the source file is local, (the source file IS thedestination file).

System action: CICS waits for new source/destinationfile names.

User response: Ensure that if the source file is localthen the name of the destination file you use isdifferent from it.

Destination:

CALF user terminal

ERZ037034E Base name and file server are identicalfor local files.

Explanation: CALF has detected that the SFS filesystem and SFS file name is identical for local sourceand destination files.

System action: CICS waits for new input.

User response: Ensure that if the source file is local,then the SFS base name and SFS file system name isdifferent for this file and the destination file.

Destination:

CALF user terminal

ERZ037035E Could not obtain details of SFS server’serverName’

Explanation: The Structured File Server (SFS) server’serverName’ was unable to be found in the SFS ServerDefinitions.

System action: The command exits with return code 5

User response: Check that the SFS server exists in theserver definitions. See any earlier messages for possiblecauses of the problem.

Destination:

stderr

ERZ037038E You must specify a Primary Index Name

Explanation: You must specify a value for the’Primary Index Name’ attribute.

System action: The command exits.

User response: Specify a value for the ’Primary IndexName’ attribute.

Destination:

stderr

ERZ037027E • ERZ037038E


ERZ037039E You must specify Field Names forPrimary Index on file ’fileName’

Explanation: You must specify a value for the ’FieldNames for Primary Index’ attribute.


User response: Specify a value for the ’Field Namesfor Primary Index’ attribute.

Destination:

stderr

ERZ037040I Both files have been openedsuccessfully.

Explanation: You requested that the two files specifiedwere to be opened. The command completedsuccessfully and the files were opened.


User response: To transfer the data from the sourcefile to the destination file press the PF9 key.

Destination:

stderr

ERZ037041E At least one filename must be specified.

Explanation: You pressed the PF5 key, Open Files, butdid not specify any files to open.


User response: Specify the file(s) you wish to openand retry the open command.

Destination:

stderr

ERZ037055E Cannot save schema ’schemaFileName’ infile ’fileName’

Explanation: The schema file ’schemaFileName’ wasunable to be written into file ’fileName’.


User response: Check that you have permission tocreate the file ’fileName’. See accompanying operatingsystem error messages for further information. Correctthe problem and retry the command.

Destination:

stderr

ERZ037056I Usage: cicssmitschema {-sschemaFileName | -e} processId

Explanation: You entered the cicssmitschemacommand incorrectly.



Destination:

stderr

ERZ037057E You have not selected a schema file

Explanation: You have not yet selected a schema file.


User response: Select a schema file before retrying theoperation.

Destination:

stderr

ERZ037058W Secondary index ’indexName’ alreadyexists on file ’fileName’.

Explanation: The cicssfsimport command hasencountered an index that is already defined on file’fileName’.

System action: The cicssfsimport command continueswithout adding index ’indexName’ to file ’fileName’.

User response: This situation possibly arose becauseyou are attempting to define a number of indexes(including existing ones) on an existing file. Ignore themessage if this is the case, as cicssfsimport continuesand defines other indexes you have specified. Or,repeat the command with a new index name or anotherfile name.

Destination:

stderr

ERZ037059I Usage: cicssfsimport -i schemaFileName-s serverName [-I] [-f fileName [-xindexName ...] ...]

Explanation: This is the usage message for thecicssfsimport command.

System action: The command exits with return code 0.

User response: None

Destination:

stderr

ERZ037039E • ERZ037059I


ERZ037061W Decimal field name ’fieldName’ of file’fileName’ - field length must be 18 bytes

Explanation: The cicssfsimport command hasencountered a decimal field with an explicit length setto a value other than 18 bytes. The length of a decimalfield must be 18.

System action: The length was set to 18 bytes, and thecicssfsimport command continues.

User response: None

Destination:

stderr

ERZ037062E Index ’indexName’ in file ’fileName’contains field name ’fieldName’ which isnot a name defined in fields Field 1 toField 20

Explanation: The cicssfsimport command hasencountered a primary or secondary index field namethat is not one of the names supplied as a name forField 1 to Field 20.

System action: The cicssfsimport command continuesto check the rest of the fields and then terminatesabnormally returning the value of 1.

User response: Correct the primary index field namesto match those names given to Field 1 to Field 20 thatyou want to form the index.

Destination:

stderr

ERZ037063E File ’fileName’ - more than one PrimaryIndex Field Name supplied for aRelative file

Explanation: The cicssfsimport command wassupplied with more than one primary index field namefor a relative file. Relative files only have one primaryindex field.

System action: The cicssfsimport commandterminates abnormally returning the value of 1.

User response: Correct the primary index field names.Only one can be supplied, and this must be anunsignedInt32 field.

Destination:

stderr

ERZ037064E Primary Index Field Name’indexFieldName’ of file ’fileName’ is not afield type of unsignedInt32

Explanation: The cicssfsimport command hasencountered a primary index field for a relative file thatis not a field type of unsignedInt32.


User response: Correct the field type for the primaryindex field selected to be unsignedInt32 or selectanother primary index field that has a type ofunsignedInt32.

Destination:

stderr

ERZ037065E Secondary Index ’indexNumber’ of file’fileName’, no field name given

Explanation: The cicssfsimport command hasencountered a secondary index with no field namesupplied.


User response: Correct the secondary index bysupplying a field name that forms the index.

Destination:

stderr

ERZ037066E Schema File already exists

Explanation: The cicsscdcreate command attempted tocreate the empty schema file with the specified name,but a file with that name already exists.

System action: The cicsscdcreate command terminatesabnormally.

User response: Reexecute the command specifying anew schema file name or remove the existing file if it isno longer required.

Destination:

stderr

ERZ037067I Usage: cicsscdcreate { -? | -fschemaFileName}

Explanation: You entered the command incorrectly.


User response: Respecify the command correctly.

Destination:

stderr

ERZ037068I programName talking to: ’serverName’

Explanation: Indicates which server cicssdt is going totalk to.


User response: None

Destination:

ERZ037061W • ERZ037068I


stderr

ERZ037069I Version [versionNumber]

Explanation: The cicssdt version number.


User response: None

Destination:

stderr

ERZ037070I Contacting resourceName ...

Explanation: Displayed while cicssdt tries to contactthe SFS.


User response: None

Destination:

stderr

ERZ037071E Failed to open file ’fileName’

Explanation: The cicssdt program was unable to openthe specified file.

System action: cicssdt terminates.

User response: Rerun cicssdt.

Destination:

stderr

ERZ037072I Exit to command prompt. Use Ctrl-D orexit to return ...

Explanation: The user has used the ! command to exitcicssdt.


User response: None

Destination:

stderr

ERZ037073I Exiting on error ...

Explanation: The -e option was used to invoke cicssdtand an error was detected.


User response: None

Destination:

stderr

ERZ037074W Unrecognized command ’commandName’ignored

Explanation: An unrecognized command was caughtin an cicssdt script.


User response: None

Destination:

stderr

ERZ037075E Command ’commandName’ notrecognized. Try ’help’.

Explanation: An unrecognized command was caught.


User response: None

Destination:

stderr

ERZ037076E A valid resourceName must be providedwith the ’optionName’ flag

Explanation: An invalid or non-existent option wasprovided with the ’optionName’ flag.


User response: None

Destination:

stderr

ERZ037077E You must provide a resourceName eitherthrough the ’-s’ flag or by setting theenvironment variablesCICS_XDT_SERVER orCICS_SFS_SERVER

Explanation: No server was provided so cicssdt wasunable to start.


User response: None

Destination:

stderr

ERZ037078E Usage: programName [-s resourceName] [-iinputFileName] [-o outputFileName] [-e][-r] [-c commandName ...]

Explanation: The program was invoked incorrectly.


User response: Reinvoke the program correctly.

Destination:

ERZ037069I • ERZ037078E


stderr

ERZ037079W [Reached EOF in input file]

Explanation: The end of an input file wasencountered.

System action: Processing continues in interactivemode.

User response: None

Destination:

stderr

ERZ037080E There is no available help for command’commandName’

Explanation: There is no help text for the specifiedcommand.


User response: Specify a valid command.

Destination:

stderr

ERZ037081I [SFS Diagnostic Tool - Help] Validcommands are: help (or ?)commandName - setopen - list l - createfileName - read fileName, (withdelete/update) - write fileName - emptyfileName - delete fileName - freefileName - addindex fileName -delindex fileName - info fileName -server serverName - qtosQSAMfileName - stof SFSfileName -ftos SFSfileName - ! (ksh) - quit

Explanation: Main online help panel.


User response: None

Destination:

stderr

ERZ037082I [Command: create fileName] Thiscommand creates a new file. Eachcharacteristic of the new file isprompted for as needed. If no input ismade at the prompt a sensible default isusually taken. However, the record FieldName and Index Field Name use anempty entry to indicate there are nomore fields. If ’q!’ is entered at anyprompt the command is terminated.

Explanation: Online help for the create command.


User response: None

Destination:

stderr

ERZ037083I [Command: write fileName] Thiscommand inserts new records into anexisting SFS file. A shorthand format isrecognized for large records: ’A>>32’will fill the remainder of the field with32 ’A’s.

Explanation: Online help for the write command.


User response: None

Destination:

stderr

ERZ037084I [Command: read fileName] Read recordsfrom an SFS file. If the key is to betaken as a string it must be specified inthe following format: ’$Angus’,($stringName). You can delete or updatethe record you have just read. Theupdate input behaves the same as awrite. If nothing is entered for a fieldduring an update the field is leftunaltered.

Explanation: Online help for the read command.


User response: None

Destination:

stderr

ERZ037085I [Command: list l searchString] Thiscommand lists all the files on thecurrent server cicssdt is talking to. If the’l’, (long), flag is used more informationis given on each file. A search string canbe used with or without the long flag tolist only certain files, (’l l cicstdq’).

Explanation: Online help for the list command.


User response: None

Destination:

stderr

ERZ037079W • ERZ037085I


ERZ037086I [Command: delete fileName] Thiscommand deletes the specified file onthe current server cicssdt is talking to.The ’setopen’ verb need not be used forthis command as delete will temporarilyturn on an exclusive open.

Explanation: Online help for the delete command.


User response: None

Destination:

stderr

ERZ037087I [Command: addindex fileName] Thiscommand adds a secondary index to thespecified file. The ’setopen’ verb neednot be used for this command asaddindex will temporarily turn on anexclusive open. Excluded keys arecurrently not supported. If ’q!’ isentered at any prompt the command isterminated.

Explanation: Online help for the addindex command.


User response: None

Destination:

stderr

ERZ037088I [Command: delindex fileName] Thiscommand deletes a secondary index onthe specified file. The ’setopen’ verbneed not be used for this command asdelindex will temporarily turn on anexclusive open. If ’q!’ is entered at anyprompt the command is terminated.

Explanation: Online help for the delindex command.


User response: None

Destination:

stderr

ERZ037089I [Command: empty fileName] Thiscommand empties the specified file.There are two types of empty available;the Exclusive empty and the Sharedempty. The Exclusive is recommendedas it is quicker and cleans the wholefile. However, if the file is already openthe Shared empty will have to be used.

Explanation: Online help for the empty command.


User response: None

Destination:

stderr

ERZ037090I [Command: info fileName] Thiscommand gives detailed informationabout the specified file. It will alsoshow all the current Open FileDescriptors against it.

Explanation: Online help for the info command.


User response: None

Destination:

stderr

ERZ037091I [Command: free fileName] Thiscommand attempts to close all the openOFDs on the specified file. (WARNING:Take care with this command).

Explanation: Online help for the free command.


User response: None

Destination:

stderr

ERZ037092I [Command: server serverName] Thiscommand changes the current server tothe new one specified. The completeserver name must be given.

Explanation: Online help for the server command.


User response: None

Destination:

stderr

ERZ037093I [Command: qtos QSAMfileName] Thiscommand takes a QSAM file and copiesthe records into an SFS file. The SFSfile must already exist.

Explanation: Online help for the qtos command.


User response: None

Destination:

stderr

ERZ037086I • ERZ037093I


ERZ037094I [Command: stof SFSfileName] Thiscommand takes an SFS file and dumpsit to a flat file. Any type of SFS filewith any record format can be dumped.The file can be reloaded using ″ftos″.

Explanation: Online help for the stof command.


User response: None

Destination:

stderr

ERZ037095I [Command: ftos SFSfileName] Thiscommand takes an SFS file and loads itfrom a flat file. The file must have beenpreviously created from the ’stof’command.

Explanation: Online help for the ftos command.


User response: None

Destination:

stderr

ERZ037096I [Command: help (or ?) commandName]This command gives general commandhelp or specific help for the specifiedcommand.

Explanation: Online help for the help command.


User response: None

Destination:

stderr

ERZ037097I [Command: !] Escapes to the commandprompt. Use Ctrl-D or exit to return tothe application.

Explanation: Online help for the ! command.


User response: None

Destination:

stderr

ERZ037098I [Command: setopen] This command setsthe characteristics of cicssdt commandsthat involve opening files. If aTransactional open is set cicssdt willmanage a client transaction for you. Thelock mode used during a ’read’ can alsobe changed using this command.

Explanation: Online help for the setopen command.


User response: None

Destination:

stderr

ERZ037099I [Command: quit] Exits the application.If ’quit’ is not used at the end of a inputscript, control will return to thecommand prompt.

Explanation: Online help for the quit command.


User response: None

Destination:

stderr

ERZ037100E TRPC initialization failed. Look forcommunication errors

Explanation: A TRPC initialization call failed.


User response: Check server is up and runningcorrectly.

Destination:

stderr

ERZ037102W (Server unavailable or non-existent)

Explanation: The cicssdt program was unable tocontact the specified SFS.


User response: Check the server is running and wascorrectly specified.

Destination:

stderr

ERZ037103I (Server OK)

Explanation: The specified server responded.


User response: None

Destination:

stderr

ERZ037094I • ERZ037103I


ERZ037104W [Command terminated. No FilenameGiven]

Explanation: No filename was supplied to thecommand.


User response: Reissue the command with a validfilename.

Destination:

stderr

ERZ037105W [Command terminated. No Server NameGiven]

Explanation: No server name was supplied to thecommand.


User response: Reissue the command with a validserver name.

Destination:

stderr

ERZ037106E Failed to list files (Server: ’serverName’Error: ’SFSerror’)

Explanation: The call to the SFS failed.


User response: Check the SFS is still running.

Destination:

stderr

ERZ037107I No files found on server

Explanation: No files were found on the SFS.


User response: None

Destination:

stderr

ERZ037108E Failed to get OFD info (Server:’serverName’ File: ’fileName’ Error:’SFSerror’)




Destination:

stderr

ERZ037109I [OFDs Left Untouched]

Explanation: The user requested that no OFDs were tobe closed.


User response: None

Destination:

stderr

ERZ037110E Failed to add index (Server: ’serverName’File: ’fileName’ Error: ’SFSerror’)




Destination:

stderr

ERZ037111W [Nothing Entered. Index LeftUntouched]

Explanation: The user specified no index to delete.


User response: None

Destination:

stderr

ERZ037112E Failed to delete index (Server:’serverName’ File: ’fileName’ Error:’SFSerror’)




Destination:

stderr

ERZ037113E Failed to open log file (Server:’serverName’ File: ’fileName’ Error:’errorNumber’)

Explanation: The open call failed to create a new logfile.


User response: Check the file does not already exist.

Destination:

stderr

ERZ037104W • ERZ037113E


ERZ037114E Failed to open QSAM definition file(Server: ’serverName’ File: ’fileName’ Error:’errorNumber’)

Explanation: The open call failed on the cicssdtQSAM definition file.



Destination:

stderr

ERZ037115E Failed to open QSAM DFHCNVtemplate (Server: ’serverName’ File:’fileName’ Error: ’errorNumber’)

Explanation: The open called failed on the QSAMDFHCNV template file.



Destination:

stderr

ERZ037116E Failed to open default code pages(Server: ’serverName’ Error: ’errorNumber’)

Explanation: The code page conversion call failed toopen at least one of the specified code pages.


User response: Check that the code pages arespecified correctly.

Destination:

stderr

ERZ037117E Failed to find default code pages(Server: ’serverName’ File: ’fileName’)

Explanation: No default code pages were able to befound in the DFHCNV template file.


User response: Check the file contains validinformation.

Destination:

stderr

ERZ037118E Bad length header read for QSAMrecord (Server: ’serverName’ File:’fileName’ Record No.: ’recordNumber’Expected Length: ’expectedLength’ ActualLength: ’actualLength’)

Explanation: An invalid record header was found inthe QSAM file.



Destination:

stderr

ERZ037119E Bad variable length for QSAM record(Server: ’serverName’ File: ’fileName’Record No.: ’recordNumber’ Length:’recordLength’)

Explanation: An invalid record length was read. Therecord length must be greater than zero.



Destination:

stderr

ERZ037120E Bad record read from QSAM file(Server: ’serverName’ File: ’fileName’Record No.: ’recordNumber’ ExpectedLength: ’expectedLength’ Actual Length:’actualLength’)

Explanation: An record of incorrect length was foundin the QSAM file.



Destination:

stderr

ERZ037121E QSAM record is too small for key(Server: ’serverName’ File: ’fileName’Record No.: ’recordNumber’ KeyOffset+Length: ’keyLength’ RecordLength: ’recordLength’)

Explanation: The record read was not long enough tocontain the designated key.



Destination:

stderr

ERZ037122E QSAM record is too small for data(Server: ’serverName’ File: ’fileName’Record No.: ’recordNumber’ DataPosition: ’dataOffset’ Record Length:’recordLength’)

ERZ037114E • ERZ037122E


Explanation: The record read was not long enough forthe data offset.



Destination:

stderr

ERZ037123E QSAM record is too big for the SFSrecord (Server: ’serverName’ File:’fileName’ Record No.: ’recordNumber’ SFSRecord Length: ’SFSrecordLength’ QSAMRecord Length: ’QSAMrecordLength’)

Explanation: The record read was bigger than the SFSrecord size.


User response: Use an SFS file with larger records.

Destination:

stderr

ERZ037124E QSAM record size does not match theSFS record. Record sizes must match forfixed length SFS files. (Server:’serverName’ File: ’fileName’ Record No.:’recordNumber’ SFS Record Length:’SFSrecordLength’ QSAM Record Length:’QSAMrecordLength’)

Explanation: The record read did not match the theSFS record size.


User response: Make sure the fixed record sizesmatch.

Destination:

stderr

ERZ037125E QSAM record size is smaller than thefixed SFS portion. Record sizes must beat least as big as the fixed portion of theSFS record. (Server: ’serverName’ File:’fileName’ Record No.: ’recordNumber’ SFSRecord Length: ’SFSrecordLength’ QSAMRecord Length: ’QSAMrecordLength’)

Explanation: The record read was smaller than thefixed portion of the SFS record.


User response: Make sure the fixed record sizesmatch.

Destination:

stderr

ERZ037126E Failed to add record to SFS file (Server:’serverName’ File: ’fileName’ Error:’SFSerror’ Record No.: ’recordNumber’)




Destination:

stderr

ERZ037127E Failed to open QSAM file (Server:’serverName’ File: ’fileName’ Error:’errorNumber’)

Explanation: The open call failed on the specifiedQSAM file.



Destination:

stderr

ERZ037128I Type in new letter to change value. JustENTER to leave as is ...

Explanation: Advice text for the setopen command.


User response: None

Destination:

stderr

ERZ037129E Failed to open file (Server: ’serverName’File: ’fileName’ Error: ’SFSerror’)




Destination:

stderr

ERZ037130E Failed to get file info (Server:’serverName’ File: ’fileName’ Error:’SFSerror’)




Destination:

stderr

ERZ037123E • ERZ037130E


ERZ037131E Failed to get file index info (Server:’serverName’ File: ’fileName’ Error:’SFSerror’)




Destination:

stderr

ERZ037132E Failed to close file (Server: ’serverName’File: ’fileName’ Error: ’SFSerror’)




Destination:

stderr

ERZ037133E Memory allocation failed (Server:’serverName’ File: ’fileName’ Error:’errorNumber’)

Explanation: A memory allocation (malloc) call failed.


User response: Check the operating system hasavailable memory.

Destination:

stderr

ERZ037134E Failed to add record (Server: ’serverName’File: ’fileName’ Error: ’SFSerror’)




Destination:

stderr

ERZ037135E Failed to create file, (no fields provided)(Server: ’serverName’ File: ’fileName’)

Explanation: No fields were provided for the filerecord specification.


User response: Reissue the command and provide atleast one field.

Destination:

stderr

ERZ037136E Failed to create file, (max records iszero) (Server: ’serverName’ File: ’fileName’)

Explanation: The maximum number of records for thefile was given as zero.


User response: Reissue the command and provide amaximum number of records.

Destination:

stderr

ERZ037137E Failed to create file (Server: ’serverName’File: ’fileName’ Error: ’SFSerror’)




Destination:

stderr

ERZ037138E Failed to set key range (Server:’serverName’ File: ’fileName’ Error:’SFSerror’)




Destination:

stderr

ERZ037139E Failed to read record (Server:’serverName’ File: ’fileName’ Error:’SFSerror’)




Destination:

stderr

ERZ037140E Failed to delete record (Server:’serverName’ File: ’fileName’ Error:’SFSerror’)




Destination:

stderr

ERZ037131E • ERZ037140E


ERZ037141E Failed to update record (Server:’serverName’ File: ’fileName’ Error:’SFSerror’)




Destination:

stderr

ERZ037142E Failed to delete file (Server: ’serverName’File: ’fileName’ Error: ’SFSerror’)




Destination:

stderr

ERZ037143E Failed to empty file (Server: ’serverName’File: ’fileName’ Error: ’SFSerror’)




Destination:

stderr

ERZ037144E Failed to open flat file (Server:’serverName’ File: ’fileName’ Error:’errorNumber’)

Explanation: The cicssdt program was unable to openthe specified flat file.



Destination:

stderr

ERZ037145E Failed to read record (Server:’serverName’ File: ’fileName’ Error:’SFSerror’ Record Number:’recordNumber’)

Explanation: The specified record number was unableto be read.



Destination:

stderr

ERZ037146E Failed to write complete record (Server:’serverName’ File: ’fileName’ Error:’errorNumber’ Record Number:’recordNumber’ Record Length:’recordLength’ Length Written:’lengthWritten’)

Explanation: The specified record was unable to bewritten.


User response: Check the flat file is not corrupt.

Destination:

stderr

ERZ037147E Failed to read record length (Server:’serverName’ File: ’fileName’ Error:’errorNumber’ Record Number:’recordNumber’)

Explanation: The specified record length was unableto be read.



Destination:

stderr

ERZ037148E Bad record length in record header(Server: ’serverName’ File: ’fileName’ Error:’errorNumber’ Record Number:’recordNumber’ Length Read: ’lengthRead’)

Explanation: The specified record header containedinvalid length information.



Destination:

stderr

ERZ037149E Failed to read complete record (Server:’serverName’ File: ’fileName’ Error:’errorNumber’ Record Number:’recordNumber’ Record Length:’recordLength’ Length Read: ’lengthRead’)

Explanation: The specified record was unable to beread.



ERZ037141E • ERZ037149E


Destination:

stderr

ERZ037150E Record too big for SFS record (Server:’serverName’ File: ’fileName’ Error:’errorNumber’ Record Number:’recordNumber’ SFS Record Length:’SFSrecordLength’ Flatfile Record Length:’flatFileRecordLength’)

Explanation: The specified record is too big for thetarget SFS record.



Destination:

stderr

ERZ037151E Record size is smaller than SFS fixedrecord size (Server: ’serverName’ File:’fileName’ Error: ’errorNumber’ RecordNumber: ’recordNumber’ SFS FixedRecord Length: ’SFSfixedRecordLength’Flatfile Record Length:’flatFileRecordLength’)

Explanation: The specified record is too small for thetarget SFS record.



Destination:

stderr

ERZ037152E Record size does not match SFS recordsize (Server: ’serverName’ File: ’fileName’Error: ’errorNumber’ Record Number:’recordNumber’ SFS Record Length:’SFSrecordLength’ Flatfile Record Length:’flatFileRecordLength’)

Explanation: The specified record does not match thefixed SFS record.



Destination:

stderr

ERZ037153E Failed to add record to SFS file (Server:’serverName’ File: ’fileName’ Error:’SFSerror’ Record Number:’recordNumber’)




Destination:

stderr

ERZ037154E Failed to open code pages

Explanation: The iconv_open call failed.

System action: The program returns with an error.

User response: Ensure that code page translation issupported from IBM-037 to ISO8859-1. Translate tablesmust be prepared in advance.

Destination:

stderr

ERZ037155E Unexpected length ’lengthRead’ read atrecord ’recordNumber’

Explanation: The cicsnetdata program failed to readthe segment length and flag bytes from the input.


User response: Ensure that the input is in netdataformat.

Destination:

stderr

ERZ037156E Bad netdata segment length’segmentLength’ at record ’recordNumber’

Explanation: The segment length is too small, itcannot be less than 3.



Destination:

stderr

ERZ037157E Excessive netdata segment length’segmentLength’ at record ’recordNumber’

Explanation: The segment length is too big for thebuffer.



ERZ037150E • ERZ037157E


Destination:

stderr

ERZ037158E Length error at record ’recordNumber’

Explanation: The data length read did not match thelength given in the segment length byte.



Destination:

stderr

ERZ037159E Control record eye-catcher is not ’INMR’at record ’recordNumber’

Explanation: The flag byte was set for a netdatacontrol record, but the beginning of the record did notcontain ″INMR″ in EBCDIC.



Destination:

stderr

ERZ037160I Control record: ’controlRecord’

Explanation: Identifies the control record, whosecontents follow.


User response: None

Destination:

stderr

ERZ037161W Data buffered at the end of file

Explanation: The end of the input was found. One ormore segments of data are still buffered. The input wasexpected to end with a last-segment of an INMR06record.



Destination:

stderr

ERZ037162I Input records: ’inputRecordCount’ -Control records: ’controlRecordCount’ -Output records: ’outputRecordCount’

Explanation: Record counts. Control records are notadded to the output.


User response: None

Destination:

stderr

ERZ037163E Data conversion incomplete at record’recordNumber’

Explanation: EBCDIC to ASCII conversion failedbecause the output buffer was too short to hold theresult.


User response: None

Destination:

stderr

ERZ037164I Description: ’netdataUnitDescription’

Explanation: Describes a unit in a netdata controlrecord.


User response: None

Destination:

stderr

ERZ037165W Unexpected unit key ’unitKey’ at record’recordNumber’

Explanation: A unit in a netdata control record wasnot recognized. The key is given in hexadecimal.



Destination:

stderr

ERZ037166W Bad description type ’descriptionType’ intable

Explanation: Internal error in cicsnetdata: the controlrecord unit was unable to be formatted.



ERZ037158E • ERZ037166W


Destination:

stderr

ERZ037167I File number ’fileNumber’

Explanation: Control record INMR02 carries the filenumber within a multiple file netdata stream. Thecicsnetdata program only supports one file. Multiplefiles are not separated.


User response: None

Destination:

stderr

ERZ037168W File ’fileName’ already exists

Explanation: The specified file already exists.


User response: Decide whether or not the file is to beoverwritten at the next prompt.

Destination:

stderr

ERZ037169E File ’fileName’ has been destroyed, pleaseretry command after correcting values.

Explanation: The file fileName was half created when avalue was detected as being in error. This value mustbe corrected by using the cicsupdate command andthen retrying the cicssfsimport command.


User response: Check the values in the schema fileand update these where they are incorrect, using thecicsupdate command. Retry the cicssfsimportcommand.

Destination:

stderr

ERZ037170E File ’fileName’ could not be destroyed.

Explanation: The file fileName was unable to bedestroyed. Please see SFS messages.


User response: Check SFS messages for moreinformation.

Destination:

stderr

ERZ037171W Unable to connect to database (SQLError: ’SQLError’)

Explanation: The cicsddt program was unable tocontact the specified database.


User response: Check the database is running andwas correctly specified.

Destination:

stderr

ERZ037172I (Database OK)

Explanation: The specified database responded.


User response: None

Destination:

stderr

ERZ037173W [Command terminated. No DatabaseName Given]

Explanation: No database name was supplied to thecommand.


User response: Reissue the command with a validdatabase name.

Destination:

stderr

ERZ037174W [Command terminated. No User NameGiven]

Explanation: No database user was supplied to thecommand.


User response: Reissue the command with a validdatabase user.

Destination:

stderr

ERZ037175E Failed to list tables (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying tolist the database tables.


User response: Check the database is running.

Destination:

stderr

ERZ037167I • ERZ037175E


ERZ037176I No tables found on database

Explanation: No tables were found on the currentdatabase.


User response: None

Destination:

stderr

ERZ037177E Failed to add index (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying toadd the secondary index.



Destination:

stderr

ERZ037178E Failed to delete index (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying todelete the secondary index.



Destination:

stderr

ERZ037179E Failed to open log file (File: ’fileName’Error: ’errorNumber’)

Explanation: The open call failed to create a new logfile.


User response: Check the file does not already exist.

Destination:

stderr

ERZ037180E Failed to open QSAM definition file(File: ’fileName’ Error: ’errorNumber’)

Explanation: The open call failed on the QSAMdefinition file.



Destination:

stderr

ERZ037181E Failed to open QSAM DFHCNVtemplate (File: ’fileName’ Error:’errorNumber’)

Explanation: The open call failed on the QSAMDFHCNV template file.



Destination:

stderr

ERZ037182E Failed to open default code pages (Error:’errorNumber’)

Explanation: The code page conversion call failed toopen at least one of the specified code pages.


User response: Check that the code pages arespecified correctly.

Destination:

stderr

ERZ037183E Failed to find default code pages (File:’fileName’)

Explanation: No default code pages were able to befound in the DFHCNV template file.



Destination:

stderr

ERZ037184E Failed to set up sqlda (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying toPREPARE or DESCRIBE an SQL Data Area.



Destination:

stderr

ERZ037185E Bad length header read for QSAMrecord (File: ’fileName’ Record No.:’recordNumber’ Expected Length:’expectedLength’ Actual Length:’actualLength’)

Explanation: An invalid record header was found inthe QSAM file.

ERZ037176I • ERZ037185E




Destination:

stderr

ERZ037186E Bad variable length for QSAM record(File: ’fileName’ Record No.:’recordNumber’ Length: ’recordLength’)

Explanation: An invalid record length was read. Therecord length must be greater than zero.



Destination:

stderr

ERZ037187E Bad record read from QSAM file (File:’fileName’ Record No.: ’recordNumber’Expected Length: ’expectedLength’ ActualLength: ’actualLength’)

Explanation: An record of incorrect length was foundin the QSAM file.



Destination:

stderr

ERZ037188E QSAM record is too small for key (File:’fileName’ Record No.: ’recordNumber’ KeyOffset+Length: ’keyLength’ RecordLength: ’recordLength’)

Explanation: The record read was not long enough tocontain the designated key.



Destination:

stderr

ERZ037189E QSAM record is too small for data (File:’fileName’ Record No.: ’recordNumber’Data Position: ’dataOffset’ Record Length:’recordLength’)

Explanation: The record read was not long enough forthe data offset.



Destination:

stderr

ERZ037190E QSAM record is too big for the databaserecord (File: ’fileName’ Record No.:’recordNumber’ SFS Record Length:’databaseRecordLength’ QSAM RecordLength: ’QSAMrecordLength’)

Explanation: The record read was bigger than thedatabase row size.


User response: Use a database table with larger rows.

Destination:

stderr

ERZ037191E Failed to insert row into table (SQLError: ’SQLError’)

Explanation: An SQL error occurred while trying toinsert a new row.



Destination:

stderr

ERZ037192E Failed to open QSAM file (File:’fileName’ Error: ’errorNumber’)

Explanation: The open call failed on the specifiedQSAM file.



Destination:

stderr

ERZ037193E Table ’tableName’ is not owned by CICSor contains illegal column types forCICS use

Explanation: The specified table is not owned by theuser cics or it contains non-character column types.


User response: Check the table has the correctattributes.

Destination:

stderr

ERZ037186E • ERZ037193E


ERZ037194E Failed to get table information (SQLError: ’SQLError’)

Explanation: An SQL error occurred while trying togain table information.



Destination:

stderr

ERZ037195E Failed to create table because nocolumns were provided

Explanation: No columns were provided to create thenew table.


User response: Run the command again providing atleast one column.

Destination:

stderr

ERZ037196E Failed to create table (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying tocreate the table.



Destination:

stderr

ERZ037197E Failed to read from table (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying toread from the table.



Destination:

stderr

ERZ037198E Failed to delete from table (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying todelete from the table.



Destination:

stderr

ERZ037199E Failed to delete table (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying todelete the table.



Destination:

stderr

ERZ037200E Failed to empty table (SQL Error:’SQLError’)

Explanation: An SQL error occurred while trying toempty the table.



Destination:

stderr

ERZ037201E Failed to open flat file (File: ’fileName’Error: ’errorNumber’)

Explanation: The specified flat file was unable to beopened.



Destination:

stderr

ERZ037202E Failed to read record (Error: ’SQLerror’Record Number: ’rowNumber’)

Explanation: The specified row number was unable tobe read.


User response: Check the table contains validinformation.

Destination:

stderr

ERZ037203E Failed to write complete row (File:’fileName’ Error: ’errorNumber’ RowNumber: ’rowNumber’ Row Length:’rowLength’ Length Written:’lengthWritten’)

Explanation: The specified row was unable to bewritten.


User response: Check the flat file is not corrupt.

ERZ037194E • ERZ037203E


Destination:

stderr

ERZ037204E Failed to read record length (File:’fileName’ Error: ’errorNumber’ RecordNumber: ’recordNumber’)

Explanation: The specified record length was unableto be read.



Destination:

stderr

ERZ037205E Bad record length in record header (File:’fileName’ Error: ’errorNumber’ RecordNumber: ’recordNumber’ Length Read:’lengthRead’)

Explanation: The specified record header containedinvalid length information.



Destination:

stderr

ERZ037206E Failed to read complete record (File:’fileName’ Error: ’errorNumber’ RecordNumber: ’recordNumber’ Record Length:’recordLength’ Length Read: ’lengthRead’)

Explanation: The specified record was unable to beread.



Destination:

stderr

ERZ037207E Record too big for database record (File:’fileName’ Error: ’errorNumber’ RecordNumber: ’recordNumber’ Database RecordLength: ’databaseRecordLength’ FlatfileRecord Length: ’flatFileRecordLength’)

Explanation: The specified record is too big for thetarget database record.



Destination:

stderr

ERZ037208I [DB2 Diagnostic Tool - Help] Validcommands are: help (or ?)commandName - list l - createtableName - read tableName - writetableName - empty tableName - deletetableName - addindex tableName -delindex tableName - info tableName -database dbName - user userName -qtod QSAMfileName - dtof tableName -ftod tableName - ! (ksh) - quit



User response: None

Destination:

stderr

ERZ037209I [Command: create tableName] Thiscommand creates a new table. Eachcharacteristic of the new file isprompted for as needed. If no input ismade at the prompt a sensible default isusually taken. If ’q!’ is entered at anyprompt the command is terminated.

Explanation: Online help for the create command.


User response: None

Destination:

stderr

ERZ037210I [Command: write tableName] Thiscommand inserts new rows into anexisting table. A shorthand format isrecognized for large records: ’A>>32’will fill the remainder of the field with32 ’A’s.

Explanation: Online help for the write command.


User response: None

Destination:

stderr

ERZ037211I [Command: read tableName] Readrecords from a table. If the key is to betaken as a number it must be specifiedin the following format: #<Number>,(#9). Hexadecimal keys can also bespecified using a prefix of 0x.

ERZ037204E • ERZ037211I


Explanation: Online help for the read command.


User response: None

Destination:

stderr

ERZ037212I [Command: list l searchString] Thiscommand lists all the tables on thecurrent database. If the ’l’, (long), flag isused more information is given on eachtable. A search string can be used withor without the long flag to list onlycertain tables, (’l l CICS’).

Explanation: Online help for the list command.


User response: None

Destination:

stderr

ERZ037213I [Command: delete tableName] Thiscommand deletes the specified table onthe current database.

Explanation: Online help for the delete command.


User response: None

Destination:

stderr

ERZ037214I [Command: addindex tableName] Thiscommand adds a secondary index to thespecified table. If ’q!’ is entered at anyprompt the command is terminated.

Explanation: Online help for the addindex command.


User response: None

Destination:

stderr

ERZ037215I [Command: delindex tableName] Thiscommand deletes a secondary index onthe specified table.

Explanation: Online help for the delindex command.


User response: None

Destination:

stderr

ERZ037216I [Command: empty tableName] Thiscommand empties the specified table.

Explanation: Online help for the empty command.


User response: None

Destination:

stderr

ERZ037217I [Command: info tableName] Thiscommand gives detailed informationabout the specified table.

Explanation: Online help for the info command.


User response: None

Destination:

stderr

ERZ037218I [Command: database dbName] Thiscommand attempts to change to a newdatabase. If the attempt fails control isreturned to the original database.

Explanation: Online help for the database command.


User response: None

Destination:

stderr

ERZ037219I [Command: user userName] Thiscommand attempts to change the currentdatabase user. If the attempt failscontrol is returned to the original user.

Explanation: Online help for the user command.


User response: None

Destination:

stderr

ERZ037220I [Command: qtod QSAMfileName] Thiscommand takes a QSAM file and copiesthe records into a database table. Thetable must already exist.

Explanation: Online help for the qtod command.


User response: None

Destination:

ERZ037212I • ERZ037220I


stderr

ERZ037221I [Command: dtof tableName] Thiscommand takes a database table anddumps it to a flat file. The file can bereloaded using ’ftod’.

Explanation: Online help for the dtof command.


User response: None

Destination:

stderr

ERZ037222I [Command: ftod tableName] Thiscommand takes a database table andloads it from a flat file. The file musthave been previously created from the’dtof’ command.

Explanation: Online help for the ftod command.


User response: None

Destination:

stderr

ERZ037224E You must provide a database eitherthrough the ’-s’ flag or by setting theenvironment variablesCICS_XDT_SERVER or DB2DBDFT

Explanation: No database was provided, so theapplication was unable to start.

System action: The application terminates.

User response: None

Destination:

stderr

ERZ037225E Tables containing columns of typeBLOB are not supported for thiscommand

Explanation: Invalid action was attempted on a tablecontaining a column of type BLOB.

System action: The command returns with an error

User response: Retry with a valid table

Destination:

stderr

ERZ037226W (Bind to database failed (SQL Error:’SQLError’)

Explanation: The application was unable to bind tothe specified database.


User response: Check the database is running andwas correctly specified.

Destination:

stderr

ERZ037227I [Oracle Diagnostic Tool - Help] Validcommands are: help (or ?)commandName - list l - createtableName - read tableName - writetableName - empty tableName - deletetableName - addindex tableName -delindex tableName - info tableName -user userName - qtod QSAMfileName -dtof tableName - ftod tableName - !(ksh) - quit



User response: None

Destination:

stderr

ERZ037228E You must provide a user/passwordeither through the ’-u’ flag or by settingthe environment variableCICS_XDT_USERPASS

Explanation: No user/password was provided, socicsodt was unable to start.

System action: cicsodt terminates.

User response: None

Destination:

stderr

ERZ037229E Usage: programName [-u user/password][-i inputFileName] [-o outputFileName][-e] [-r] [-c commandName ...]

Explanation: The program was invoked incorrectly.

System action: cicsodt terminates.

User response: Reinvoke the program correctly.

Destination:

stderr

ERZ037221I • ERZ037229E


ERZ037230E Failed to write record ’recordNumber’

Explanation: The cicsnetdata program failed to writethe specified record number to the output file.


User response: Ensure there is enough space on thefilesystem for the output file.

Destination:

stderr

ERZ037401E Cannot run the db2 command. Checkthe PATH environment variable

Explanation: The PATH is not properly set to includethe directory containing the db2 executable.

System action: Exit with return code 1.

User response: Ensure that the PATH environmentvariable is set to include all the directories required torun db2.

Destination:

stderr

ERZ037402E Schema file ’schemaFileName’ is eitherempty or contains invalid type names

Explanation: The schema file schemaFileName does notcontain any valid schemas. If the schema file is notempty, then it must contain an error in the names ofone of the types. This second situation occurs only ifthe schema file is edited by hand, since SMIT (on AIX)and the Administration Utility (on Windows NT)ensure that only valid types are placed into the schemafile.


User response: Check to ensure that the specifiedschema file is not empty. If it is not empty, ensure thatthe type specifications of the fields defined in theschema are valid.

Destination:

stderr

ERZ037403E The existing file is not of type ’fileType’as specified in the schema

Explanation: The database contains a file with thesame name as that specified in the schema. The filetype of the existing file is not the same as the filetypespecified in the schema.


User response: Respecify the filetype in the schema tobe consistent with the filetype of the existing file orchange the name of the schema such that its name isdifferent from that of the existing file.

Destination:

stderr

ERZ037404E Schema contains a CICS-reserved fieldname ’fieldName’

Explanation: The schema contains a field with aFieldName equal to RRN, RBA or TIMESTA. Thesefield names are reserved for use by CICS and cannot beused to name user-specified fields.


User response: Respecify the schema such that noneof the fields have a FieldName of RRN, RBA orTIMESTA.

Destination:

stderr

ERZ037405E Variable field length ’variableFieldLength’exceeds the DB2 limit of 32700

Explanation: The variable field length specified in theschema exceeds the maximum allowed in DB2.


User response: Respecify the variable field length tobe less than or equal to 32700.

Destination:

stderr

ERZ037406E Variable field has an invalid length of’variableFieldLength’

Explanation: variable field length is zero or negative


User response: Specify a positive variable field length.

Destination:

stderr

ERZ037407I Successfully created file ’fileName’ ondatabase ’databaseName’

Explanation: The file fileName was successfully createdon database databaseName. This means that all the fieldsspecified in the schema with the same name as fileNamewere created with the names, types, and (optionally)field lengths supplied, under user name CICS.Consequently, the fully resolved name of the table isCICS.fileName.

System action: Continues to process your command.


Destination:

stderr

ERZ037230E • ERZ037407I


ERZ037408W Index name ’actualIndexName’(’specifiedIndexName’ in the schema) onfile ’fileName’ already exists on thedatabase

Explanation: The index actualIndexName already existson the database. The name in brackets specifies theindex name that was originally specified in the schema.Database indexes are required to have a name that isunique across the database. Indexes are renamedduring table creation so that they have a unique name.The unique name is created by concatenating the filename with the index number. The Primary index for afile is given index number 0. Secondary indexes aregiven index numbers 1 to 9, and secondary indexnumber 10 is given index ’number’ ’A’.

System action: If the -I flag was set on the commandline, then processing continues, otherwise the commandexits with return code 1.

User response: Check that the index specifiedconforms with the definition in the schema file. If itdoes not, then remove it using the db2 ″DROPINDEX...″ command, then rerun cicsdb2import tocreate an index with the desired definition.

Destination:

stderr

ERZ037409E Implicit connection is not enabled: theDB2DBDFT environment variable is notset.

Explanation: The database alias was not supplied onthe command line and implicit connection to thedatabase was attempted. This was not possible sincethe default database was not specified in theenvironment variable DB2DBDFT.


User response: Either specify the desired database onthe command line using the -d option, or set theenvironment variable DB2DBDFT.

Destination:

stderr

ERZ037410E Schema ’schemaName’ does not containany field definitions

Explanation: The schema schemaName exists but doesnot contain any field definitions.


User response: Add field definitions to the schema, orremove it.

Destination:

stderr

ERZ037411I Connected to database ’databaseName’

Explanation: A connection was established to thedatabase databaseName. This connection is required inorder to create files and indexes. The connection to thisdatabase is maintained while the cicsdb2importcommand is running. All files and indexes specified inthe schema and on the command line are created onthis database.



Destination:

stderr

ERZ037412E You do not have sufficient authority toaccess schema files

Explanation: The user who issued the cicsdb2importcommand does not have the correct access permissionsfor the schema files.

System action: Exit with return code 1 .

User response: On UNIX log on as root. On WindowsNT log on as a user that is a member of the cicsgroupor Administrators groups. Retry the command.

Destination:

stderr

ERZ037413I Successfully added index’uniqueIndexName’ (’originalIndexName’ inthe schema) for file ’fileName’

Explanation: The schema contains an indexdescription with the name originalIndexName; this indexdefinition was successfully added to the file fileName.Since database indexes must be unique across an entiredatabase, cicsdb2import generates a unique name,uniqueIndexName, and creates the index with that name,rather than the name specified in the schema.



Destination:

stderr

ERZ037414I The schema definition for file ’fileName’is consistent with that of the existingfile

Explanation: There is a file fileName with the samename as that defined in the schema already existing onthe database. Its field names are the same as those inthe schema. The field types are not checked forconsistency between the schema definition and theexisting file.


ERZ037408W • ERZ037414I



Destination:

stderr

ERZ037415E The schema definition of index’indexName’ contains a field name’fieldName’ which does not exist

Explanation: The schema description of the indexindexName contains a nonexistent field name fieldNamein the IndexFieldNames (PrimaryIndexFieldNames inthe case of a primary index) section of the schema.


User response: Update the definition of the index inthe schema to contain only field names that are alsodefined in the same schema.

Destination:

stderr

ERZ037416I Starting to create file ’fileName’ ondatabase ’databaseName’

Explanation: The command cicsdb2import has begunto process the schema that describes the file fileName;an attempt is made to create the file on databasedatabaseName.



Destination:

stderr

ERZ037420E SQL error returned, sqlcode ’sqlcode’

Explanation: A SQL API call to list the databasedirectory failed.


User response: Examine the value of sqlcode todetermine the cause of the failure.

Destination:

stderr

ERZ037460E You do not have sufficientauthorizations on database’databaseName’ to create tables

Explanation: The user has neither of theauthorizations (SYSADM or DBADM) nor CREATETABprivilege on the database. At least one of theseprivileges is required for cicsdb2import to runsuccessfully.


User response: Rerun cicsdb2import when logged in

as a user who has the authority or privilege to createtables on the database. Alternatively supplycicsdb2import with the username and password of auser who does have these privileges by specifying the -uuserName flag and the -p password flag.

Destination:

stderr

ERZ037470I No secondary indexes will be createdfor file ’fileName’ since it is of typerelative

Explanation: Secondary indexes cannot be created onfiles of type relative. No attempt is made to check forsecondary indexes on a schema for a file of typerelative. Consequently no further warnings are issued.



Destination:

stderr

ERZ037471E Usage: cicsdb2import -i schemafile [-ddatabase] [-u user -p password] [-I] [-ffile [-x index ... ] ] ...

Explanation: cicsdb2import was invoked incorrectly.

System action: Exit with return code 1 (incorrectusage).

User response: Ensure the command is called withcorrect arguments

Destination:

stderr

ERZ037472W Schema file ’schemaFile’ does not containa valid schema for ’fileName’

Explanation: The specified schema file does notcontain a description schema for ’schemaFile’, or thestanza is invalid. If the schema file does contain aschema for schemaFile, then this message can arise if afield in that schema was given an invalid type.


User response: Specify a filename for which a schemawas written or, if the schema does exist, check it forinvalid types.

Destination:

stderr

ERZ037415E • ERZ037472W


ERZ037473W Schema file ’schemaFileName’ does notcontain details of index ’indexName’ forfile ’fileName’

Explanation: The schema file schemaFileName exists,and contains a schema for file fileName; however theschema for file fileName does not contain a specificationof index indexName.

System action:

User response:

Destination:

stderr

ERZ037474E File ’fileName’ already exists on database’databaseName’

Explanation: An attempt is being made either tocreate file fileName or to add indexes to it. The filefileName already exists on the database databaseName.

System action: If the ’-I’ (ignore error) flag is set,continue processing. If it is not set, exit with returncode 1.

User response: If the user wishes only to create newindexes, rerun the command with the ’-I’ (ignore error)flag set.

Destination:

stderr

ERZ037476W Could not create index ’uniqueIndexName’(’schemaIndexName’ in the schema) forfile ’fileName’

Explanation: cicsdb2import was unable to create thespecified index. This can arise if the fields that composethe index are not consecutive or if the index alreadyexists on the database.


User response: Ensure that the fields that comprisethe index are consecutive.

Destination:

stderr

ERZ037477E Command line argument’commandOption’ re-specified

Explanation: A command line option, other than ’-f’or ’-x’, was specified more than once. Most of thecommand line options ( ’-d’, ’-u’, ’-p’, ’-i’ and ’-I’) mustnot be specified more than once.

System action: Exit with return code 1 (usage error).

User response: Ensure that command line options(other than ’-f’ and ’-x’) are specified only once.

Destination:

stderr

ERZ037478E The ’commandOption’ option requires amandatory argument

Explanation: The command line option must be givenan argument. With the exception if the ’-I’ option, everycommand line option must be given an argument.


User response: Rerun the command ensuring that allflags with mandatory arguments have their argumentsspecified.

Destination:

stderr

ERZ037479E Invalid command line option’commandOption’

Explanation: An unknown command line option wasspecified.


User response: Ensure that only the allowedcommand line options are used.

Destination:

stderr

ERZ037480E The ’commandOption’ option must bespecified with this command

Explanation: A mandatory option was not specified.


User response: Ensure that all mandatory options aregiven on the command line.

Destination:

stderr

ERZ037481E Cannot read schema file ’schemaFileName’

Explanation: The specified schema file does not existor is not readable by this user.


User response: Ensure that the specified schema fileexists and can be read by this user.

Destination:

stderr

ERZ037482E Unable to find definition for database’databaseName’

Explanation: A database was specified that cannot befound.

ERZ037473W • ERZ037482E


System action: Exit with return code 1.TRANSLATION_GUIDELINES None.

User response: Ensure that the specified databaseexists.

Destination:

stderr

ERZ037483E DB2 command on database’databaseName’ issued the followingmessage: ’db2Message’

Explanation: A DB2 command failed.


User response: Examine the message returned by DB2and follow the action indicated for that message asspecified in the Messages and Problem DeterminationGuide for DB2.

Destination:

stderr

ERZ037484E Command could not complete

Explanation: cicsdb2import received a signal thatprevented it from completing the processing requested.The full list of signals that cause processing to stop inthis way is: 1 (HUP), 2 (INT), 3 (QUIT), 8 (FPE), 10(BUS), 11 (SEGV), 15 (TERM).

System action: Exits with return code 1.


Destination:

stderr

ERZ037486I Usage: cicsdb2import -i schemafile [-ddatabase] [-u user -p password] [-I] [-ffile [-x index ... ] ] ...

Explanation: The user has requested usageinformation for cicsdb2import using the ’-?’ option.



Destination:

stderr

ERZ037487E Unable to connect to database.

Explanation: An attempt was made to connect to adatabase. This did not succeed.

System action: Issue message ERZ37483E to show themessages issued by DB2, then exit with return code 1.

User response: Follow the instructions for messagenumber ERZ37483E.

Destination:

stderr

ERZ037489E Field mismatch between schema’schemaName’ and existing file ’fileName’

Explanation: There is a difference between the fieldnames specified in schema schemaName and the fieldnames discovered in an existing file fileName.


User response: Either change the name of the schemaso that it is different from any existing filename, oralter the schema definition so that it is consistent withthe existing file.

Destination:

stderr

ERZ037490I Enter database password for user’userName’:

Explanation: The ’-u’ option was used to specify theuser name but the password was not supplied via the’-p’ option. Since it is mandatory to supply thepassword if the username is supplied, this messageprompts the user to enter their password.

System action: Wait for the password to be entered.The password is not echoed back to the screen.

User response: Enter the password for user userName.

Destination:

stderr

ERZ037491E Could not determine codeset width touse with nlsString field

Explanation: The system defined value for themaximum width of a character in the current localewas found to be zero. This value (MB_CUR_MAX) isset based on the currently defined locale.


User response: Check the currently defined locale. OnUNIX, check that the locale set by the LANGenvironment variable is valid.

Destination:

stderr

ERZ037492E Field name ’fieldName’ of index’indexName’ on file ’fileName’ either doesnot exist or is not consecutive with itspredecessor

Explanation: The column names that comprise anindex must be consecutive. This means that they mustbe in the same order as the column names that definethe file itself, and that each field specified must be

ERZ037483E • ERZ037492E


adjacent to its predecessor. This message is generatedwhen the index contains the name of a column that isnot in the same sequence as the columns of the fileitself, or when a column name in the index does notexist.

System action: The index indexName is not created.Processing continues.

User response: Ensure that all indexes are definedwith field names that are consecutive.

Destination:

stderr

ERZ037493E Width of zero was specified forfixed-length field ’fieldName’

Explanation: Field fieldName was assigned a fieldlength of zero. Fixed length fields of type string or typebyteArray require a fieldlength to be supplied, whichmust be greater than 0.


User response: Ensure that all fields of type string ortype byteArray have their FieldLength set to 1 orgreater.

Destination:

stderr

ERZ037494W Decimal field ’fieldName’ had illegallength of ’fieldLength’; setting thefieldlength to ’mandatoryDecimalLength’

Explanation: A decimal field must have a field lengthof mandatoryDecimalLength, which is 18. A decimal fieldin the schema being processed was given a field lengthdifferent from mandatoryDecimalLength.

System action: Set the FieldLength of the fieldfieldName to 18, and continue.

User response: To avoid this warning message, set thefield length of each decimal field in the schema to 18.

Destination:

stderr

ERZ037495W Invalid field type ’fieldType’

Explanation: The schema being processed contains afield with an invalid field type fieldType.


User response: Ensure that all fields have a valid fieldtype. Schema manipulation via SMIT on AIX and theAdministration Utility on Windows NT ensure that allfield types are valid.

Destination:

stderr

ERZ037496E Unable to save database id’databaseName’ into file ’fileName’.

Explanation: The write of the DB2 database (DB2)name ’databaseName’ to file ’fileName’ was unsuccessful.


User response: Check that you have permission tocreate ’fileName’. On UNIX Check that the file system,/temp, is not full. On Windows NT, check that thedrive and directory defined in the TEMP environmentvariable are not full. If either either environment is full,correct the problem and retry the command.

Destination:

stderr

ERZ037497E Usage: cicssmitdb2 { -s serverName | -e} processId.

Explanation: This is the usage message for the CICSprivate command cicssmitdb2. This command is not tobe run from the command line.


User response: None

Destination:

stderr

ERZ037498E You have not selected a DB2 database.

Explanation: You have not selected a DB2 database(DB2).


User response: Select a DB2 database and retry theoperation.

Destination:

stderr

ERZ037499I Usage: cicssmitdb2 { -s serverName | -e} processId.

Explanation: This is the usage message for the CICSprivate command cicssmitdb2. This command is not tobe run from the command line.


User response: None

Destination:

stderr

ERZ037493E • ERZ037499I


ERZ037501E Cannot run the sqlplus command.Check the PATH environment variable

Explanation: The PATH is not properly set to includethe directory containing the sqlplus executable.


User response: Ensure that the PATH environmentvariable is set to include all the directories required torun sqlplus.

Destination:

stderr

ERZ037502E Usage: cicsoraimport -i schemafile [-uuser[/password]] [-I] [-f file [-x index ... ]] ... [-t tableSpace]

Explanation: cicsoraimport was invoked incorrectly.

System action: Exit with return code 1 (incorrectusage).

User response: Ensure the command is called withcorrect arguments

Destination:

stderr

ERZ037503E Oracle command on database’databaseName’ issued the followingmessage: ’oracleMessage’

Explanation: An Oracle command failed.


User response: Examine the message returned byOracle and follow the action indicated for that messageas specified in the Messages and Codes Manual forOracle.

Destination:

stderr

ERZ037504I Usage: cicsoraimport -i schemafile [-uuser[/password]] [-I] [-f file [-x index ... ]] ... [-t tableSpace]

Explanation: The user has requested usageinformation for cicsoraimport using the ’-?’ option.



Destination:

stderr

ERZ037505W Fieldname ’fieldName’ too long - beingtruncated to ’truncatedFieldName.’

Explanation: The fieldname specified in the schemadefinition for cicsdb2import was too long and wastruncated.

System action: The command truncates the fieldnameand continues.


Destination:

stderr

ERZ038001E Usage: cicssfs { -? | [-t traceMask] [[-TtraceDestination]...] [-a | -nlv] [-I][serverName][[attributeName=attributeValue]...] }

Explanation: You entered the cicssfs commandincorrectly.


User response: Retry the command specifying correctparameters. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ038003E Region ’regionName’ does not exist, isrunning, or is already being configured.Configuration is not possible.

Explanation: The Structured File Server (SFS) cannotbe configured for a region while the region is runningor while SFS is being configured by another user.


User response: If the region is running and theconfiguration change must be made then shutdown theregion. If another user is performing configuration forthe region then retry the command when thatconfiguration is complete. If there is neither a regionrunning or another user performing configuration thensee the message output just before this one for furtherdetails.

Destination:

stderr

ERZ038004I Configuring SFS for recoverableauxiliary TSQs for region ’regionName’

Explanation: The command is creating Structured FileServer (SFS) files for the region’s recoverable auxiliaryTemporary Storage Queues (TSQs).


ERZ037501E • ERZ038004I


User response: None

Destination:

stderr

ERZ038005I Configuring SFS for non-recoverableauxiliary TSQs for region ’regionName’

Explanation: The command is creating Structured FileServer (SFS) files for the region’s non-recoverableauxiliary Temporary Storage Queues (TSQs).


User response: None

Destination:

stderr


Explanation: The command encountered a problemrunning ’programName’.


User response: Refer to other messages displayed orin stderr. Check that CICS is installed correctly. Checkthat the program exists, is owned by user cics and hasread, write and execute permissions for its owner.

Destination:

stderr

ERZ038007I Configuring SFS for logicallyrecoverable TDQs for region’regionName’

Explanation: The command is creating Structured FileServer (SFS) files for the region’s logically recoverableTransient Data Queues (TDQs).


User response: None

Destination:

stderr

ERZ038008I Configuring SFS for physicallyrecoverable TDQs for region’regionName’

Explanation: The command is creating Structured FileServer (SFS) files for the region’s physically recoverableTransient Data Queues (TDQs).


User response: None

Destination:

stderr

ERZ038009W Unable to update details of server’serverName’

Explanation: The command you have entered wasunable to change the SFS ’serverName’. However, sincethe command was invoked with the -I flag to ignoreerrors, the existing details are used. Accompanyingmessages identify the cause of the problem.


User response: If the details of the SFS server’serverName’ do not need to be modified then no actionis necessary. However, if the SFS server details aredifferent use accompanying messages to determine thecause of the problem. Correct the problem and retry thecommand.

Destination:

stderr

ERZ038010I Configuring SFS for non-recoverableTDQs for region ’regionName’

Explanation: The command is creating Structured FileServer (SFS) files for the region’s non-recoverableTransient Data Queues (TDQs).


User response: None

Destination:

stderr

ERZ038011I Configuring SFS for protectedLocally-Queueing requests for region’regionName’

Explanation: The command is creating Structured FileServer (SFS) files for the region’s ProtectedLocally-Queueing requests.


User response: None

Destination:

stderr

ERZ038012I Configuring SFS for unprotectedLocally-Queueing requests for region’regionName’

Explanation: The command is creating Structured FileServer (SFS) files for the region’s UnprotectedLocally-Queueing requests.


User response: None

Destination:

stderr

ERZ038005I • ERZ038012I


ERZ038016E Timed out waiting for server’serverName’ to start

Explanation: The Structured File Server (SFS)’serverName’ has not responded to Remote Procedurecalls (RPCs) within the time limit allowed by thecommand. If you were auto starting the server (thedefault action) this message does not necessarilyindicate that there is a problem as the SFS can have alarge amount of data to recover that can possibly takelonger than the timeout defined. The SFS writes itsprogress messages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.


User response: Use the SFS messages to determine ifthere is a problem. If there is, shut down the server(using, for example the cicssfsshut command), correctthe problem and retry the command. If the sfs processis using a large amount of system CPU, then the SFS isalmost certainly still recovering data; continue to waitfor the server to become active. Once the server hasinitialized it writes a message. If the problem persistscold start SFS ’serverName’ (all data is lost) and restoredata from backup.

Destination:

stderr

ERZ038019E Unable to obtain region definition forregion ’regionName’.

Explanation: The region definition does not exist forregion ’regionName’.

System action: The command terminates abnormallyreturning the value 1.

User response: Add the region definition using thecicsdefault command.

Destination:

stderr

ERZ038020E Unable to obtain server definition forserver ’serverName’

Explanation: The Structured File Server (SFS)definition does not exist for server ’serverName’. Inorder to resolve certain attribue values the commandrequires access to the SSD definition file.


User response: Add the server definition using thecicssfscreate command. Alternatively, the serverpossibly exists on a remote machine that cannot bereached.

Destination:

stderr

ERZ038022E Logical volume ’volumeName’ does notexist

Explanation: A Structured File Server (SFS) requireslogical volume ’volumeName’ in order to log recoverableinformation. It does not exist. Accompanying messagesgive more information about the cause of the theproblem.


User response: Create logical volume ’volumeName’and retry the command.

Destination:

stderr

ERZ038023W Unable to create logical volume’volumeName’

Explanation: Logical volume ’volumeName’ was notable to be created. Accompanying messages identify thecause of the problem. The SFS writes its messages to afile called msg under the varDir/cics_servers directorystructure in a sub-directory based upon its name (forexample for a server named /.:/cics/sfs/default thefull path of the message file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you canfind the drive letter of the disk containing the msg fileby using the cicsname serversdir command.


User response: Use the accompanying CICS and SFSmessages to determine the cause of the problem.Correct the problem and retry the command.

Destination:

stderr

ERZ038024I Logical volume ’volumeName’ for server’serverName’ has been created.

Explanation: The command you have entered hassuccessfully created logical volume ’volumeName’. Thisis used by Structured File Server (SFS) ’serverName’ tostore data.


User response: None

Destination:

ERZ038016E • ERZ038024I


stderr

ERZ038025E Unable to add volume ’volumeName’ toserver ’serverName’

Explanation: The attempt to add volume ’volumeName’to Structured File Server (SFS) ’serverName’ wasunsuccessful.


User response:

Destination:

stderr

ERZ038026E Unable to create TSQ using file’fileName’ on server ’serverName’

Explanation: There was an error creating theTemporary Storage Queue (TSQ) ’fileName’ onStructured File Server (SFS) ’serverName’.


User response: Refer to preceding messages, fromsfsadmin, for the reason why the TSQ was unable to becreated. If the preceding message gives the details onan already existing file on the Structured File Server(SFS) then the file cannot be created because onealready exists. You can ignore this step and continuewith subsequent configuration steps by retrying therequest with ″Ignore Errors″ selected (-I flag oncommand).

Destination:

stderr

ERZ038027E Unable to create TDQ using file’fileName’ on server ’serverName’.

Explanation: There is an error creating the TransientData Queue (TDQ) needed by the Structured FileServer (SFS) ’serverName’ for storing data.


User response: Refer to preceding messages, fromsfsadmin, for the reason why the TSQ was unable to becreated. If the preceding message gives the details onan already existing file on the Structured File Server(SFS) then the file cannot be created because onealready exists. You can ignore this step and continuewith subsequent configuration steps by retrying therequest with ″Ignore Errors″ selected (-I flag oncommand).

Destination:

stderr

ERZ038028E Unable to create Local Queue using file’fileName’ on server ’serverName’.

Explanation: An attempt to create a Local Queue (LQ)on the Structured File Server (SFS) ’serverName’ wasunsuccessful.


User response: Refer to preceding messages, fromsfsadmin, for the reason why the LQ was unable to becreated. If the preceding message gives the details onan already existing file on the SFS then the file cannotbe created because one already exists. You can ignorethis step and continue with subsequent configurationsteps by retrying the request with ″Ignore Errors″selected (-I flag on command).

Destination:

stderr

ERZ038029E Unable to update region definition.

Explanation: The command was unable to update theregion definition.


User response: Check that you have read, write andexecute permissions for the region directory and thatthe file system is not full.

Destination:

stderr

ERZ038030I Configuration completed successfully.

Explanation: There were no problems reported duringconfiguration.


User response: None

Destination:

stderr

ERZ038031E Usage: cicssfscreate { -? | [-v] [-I] [-mmodelId] serverName[[attributeName=attributeValue]...] }

Explanation: You entered the cicssfscreate commandincorrectly.


User response: Retry the command with correctparameters. See the TXSeries Infocenter for moreinformation.

Destination:

ERZ038025E • ERZ038031E


stderr

ERZ038032E Usage: cicssfsdestroy { -? | [-v] [-I]serverName }

Explanation: You entered the cicssfsdestroy commandincorrectly.


User response: Retry the command with correctparameters. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ038034E Unable to create server ’serverName’

Explanation: The command you have entered wasunable to create a new Structured File Server (SFS)named ’serverName’. Accompanying messages identifythe exact cause of the problem.


User response: Use accompanying messages todetermine the cause of the problem. If necessary,certain errors can be ignored if the command is runwith the -I flag (ignore errors).

Destination:

stderr

ERZ038035E Unable to destroy server ’serverName’

Explanation: The command you have entered wasunable to completely destroy the Structured File Server(SFS) ’serverName’. Accompanying messages identify theexact cause of the problem.



Destination:

stderr

ERZ038037I Server ’serverName’ added to SSD

Explanation: An entry was added to the StructuredFile Server (SFS) Server Definitions (SSD) for SFS’serverName’.


User response: None

Destination:

stderr

ERZ038038I Server ’serverName’ added as asubsystem

Explanation: A subsystem was created for theStructured File Server (SFS) ’serverName’.


User response: None

Destination:

stderr

ERZ038039I The subsystem for server ’serverName’has been removed

Explanation: The details of Structured File Server(SFS) ’serverName’ were deleted.


User response: None

Destination:

stderr

ERZ038041W File ’fileName’ already exists on server’serverName’

Explanation: The file ’fileName’ already exists onStructured File Server (SFS) ’serverName’.

System action: Processing continues, but othermessages can be produced as a result of this error thatcan possibly cause the command to terminate. If thecicssfsconf command is invoked without the -q flaginformation about the existing file is displayed.

User response: If necessary, consider destroying theexisting file by using the SFS administration commandsfsadmin.

Destination:

stderr

ERZ038050E Server ’serverName’ entry already existsin SSD.

Explanation: An entry for Structured File Server (SFS)’serverName’ already exists in the SFS Server Definitions(SSD).


User response: Either use the cicssfsdestroy commandto remove all the server details, or retry the commandspecifying the -I (ignore errors) option.

Destination:

stderr

ERZ038032E • ERZ038050E


ERZ038051E Unable to add server ’serverName’ toSSD

Explanation: The details of Structured File Server(SFS) ’serverName’ were unable to be added to the SFSServer Definitions (SSD). Accompanying messagesidentify the exact cause of the problem. However, themost likely cause is that there is already an entry for aSFS of this name.


User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem and retry command. Certain errors can beignored if the command is run with the -I flag (ignoreerrors).

Destination:

stderr

ERZ038052E Unable to add entry ’serverName’ as asubsystem

Explanation: The command you have entered wasunable to add the subsystem details for Structured FileServer (SFS) ’serverName’. Accompanying messagesidentify the exact cause of the problem. An entry foryour SFS was not created.


User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem and retry command. Certain errors can beignored if the command is run with the -I flag (ignoreerrors).

Destination:

stderr

ERZ038053W Server ’serverName’ entry already existsin SSD

Explanation: An entry for Structured File Server (SFS)’serverName’ already exists in the SFS Server Definitions(SSD). But as the command was invoked with the -Iflag (ignore errors) the command redefines the existingentry using any overrides you have specified.


User response: None

Destination:

stderr

ERZ038054E Unable to find ’entryName’ in SSD

Explanation: The Structured File Server (SFS) detailsfor ’entryName’ were unable to be retrieved from theSFS Server Definitions (SSD). Accompanying messagesidentify the exact cause of the problem.



Destination:

stderr

ERZ038060E Waiting for lock.

Explanation: A Structured File Server (SFS) commandrequires an SFS lock to be taken; however, the lock isalready being held by another process.

System action: The command loops until the lock isreleased or timeout occurs.

User response: Use the cicssfslock command torelease the lock.

Destination:

stderr

ERZ038061E The server ’serverName’ is currentlybeing administered by another process.

Explanation: Only one process at a time canadminister the server.


User response: Wait until the server has finishedbeing administered by the other process. Retry thetransaction.

Destination:

stderr

ERZ038062W Unable to find the subsystem definitionfor server ’serverName’.

Explanation: The command you have entered wasunable to find a subsystem definition for StructuredFile Server (SFS) ’serverName’. The definition waspossibly already deleted. Accompanying messagesidentify the cause of the problem.


User response: Check that the correct server namewas specified. Check accompanying messages todetermine whether the subsystem exists. Retry thecommand.

Destination:

ERZ038051E • ERZ038062W


stderr

ERZ038063I Server ’serverName’ has been removedfrom SSD.

Explanation: Structured File Server (SFS) ’serverName’was deleted from the SFS Server Definitions (SSD).


User response: None

Destination:

stderr

ERZ038065I Releasing lock for server ’serverName’.

Explanation: The lock, which indicates that StructuredFile Server (SFS) ’serverName’ is running, was removed.


User response: None

Destination:

stderr

ERZ038070W Unable to add a subsystem definitionfor server ’serverName’.

Explanation: Subsystem names used for eachStructured File Server (SFS) must be unique. Asubsystem name for SFS ’serverName’ was not added asthe ShortName defined already exists. As you have runthe command with the -I flag (ignore errors) theexisting subsystem definition is modified.


User response: If the name of the SFS ’serverName’associated with the ShortName has not changed thenno action is necessary. However, if the SFS name isdifferent destroy the server and retry the command oroverride ShortName with a valid one.

Destination:

stderr

ERZ038071W Subsystem definition for server’serverName’ has not been removed.

Explanation: The command you have entered tried todelete a subsystem definition that is associated with adifferent server. The definition was not deleted.Accompanying messages give more information aboutthe problem.


User response: Check that the server name is correct.Retry the command specifying the correct server.

Destination:

stderr

ERZ038072E Server ’serverName’ unable to read/writeto logical volume ’volumeName’ using Id’userId’.

Explanation: The Structured File Server (SFS)’serverName’ keeps essential information on theoperating system logical volume ’volumeName’. In orderfor the SFS to function correctly it needs to be able toread and write to this volume. The most likely cause ofthis problem is that the logical volume is not owned by’userId’.


User response: Investigate why ’userId’ is unable toread/write to ’volumeName’. Correct the problem andretry the command. On UNIX, if the problem is that’volumeName’ is not owned by ’userId’ use the operatingsystem command chown to change its ownership.

Destination:

stderr

ERZ038073E Unable to create logical volume’volumeName’ for server ’serverName’.

Explanation: The command you have entered wasunable to create logical volume ’volumeName’. Thelogical volume is required by Structured File Server(SFS) ’serverName’ to store data. Accompanyingmessages identify the exact cause of the problem. TheSFS writes its messages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.


User response: Use both the accompanying and theSFS messages to determine the cause of the problem.Shut down the server (using, for example, thecicssfsshut command) correct the problem and retrythe command.

Destination:

stderr

ERZ038076E Unable to shutdown server ’serverName’.

Explanation: The Structured File Server (SFS)’serverName’ was unable to be shut down. The SFSwrites its messages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you can find the drive

ERZ038063I • ERZ038076E


letter of the disk containing the msg file by using thecicsname serversdir command.


User response: Use accompanying and servermessages to determine the cause of the problem, if theyexist. Correct the problem and retry the command.

Destination:

stderr

ERZ038151E You do not have sufficient authority torun this command.

Explanation: You attempted to run a command withinsufficient authority. On UNIX you must be logged onas root. On Windows NT you must be logged on witha userid with Administrator and cicsgroup authority.


User response: Login correctly and retry thecommand.

Destination:

stderr

ERZ038152E The request to start server ’serverName’was unsuccessful.

Explanation: The command you have entered made arequest to start Structured File Server (SFS)’serverName’. This request was unsuccessful.Accompanying messages identify the exact cause of theproblem.



Destination:

stderr

ERZ038153E Usage: cicssfsshut { -? | [-f] [-c]serverName }

Explanation: You entered the cicssfsshut commandincorrectly.


User response: Retry the command with validparameters. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ038154E The request to stop server ’serverName’was unsuccessful.

Explanation: The command you have entered has senta request to stop the subsystem running Structured FileServer (SFS) ’serverName’. This request did not succeed.Accompanying messages identify the exact cause of theproblem.


User response: If after examining the accompanyingmessages you are unable to determine the cause of theproblem retry the command, first using the -f flag(immediate shutdown) and, if that is unsuccessful, the-c flag (cancel the subsystem).

Destination:

stderr

ERZ038155E Unable to execute ’executableName’.

Explanation: The command you have entered wasunable to execute ’executableName’.


User response: Check that ’executableName’ is availableon your PATH environment variable and that you havepermission to execute it. Correct the problem and retrythe command.

Destination:

stderr

ERZ038156E Server ’serverName’ is not running.

Explanation: The Structured File Server (SFS)’serverName’ is not running, so the command wasunable to be executed. The SFS writes its messages to afile called msg under the varDir/cics_servers directorystructure in a sub-directory based upon its name (forexample for a server named /.:/cics/sfs/default thefull path of the message file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you canfind the drive letter of the disk containing the msg fileby using the cicsname serversdir command.


User response: Check that the server name is correct.Use the SFS messages to determine why the server isnot running.

Destination:

stderr

ERZ038151E • ERZ038156E


ERZ038163E Server ’serverName’ was forciblyterminated after detection of anunexpected exit.

Explanation: The Structured File Server (SFS)’serverName’ terminated abnormally, without completingthe normal shutdown procedure. The SFS writes itsmessages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.


User response: Use the SFS and the operating systemmessages to determine why the server has terminatedabnormally. Correct the problem and restart the SFS.

Destination:

SFS message log

ERZ038165E Unable to write ’serverName’ to ’fileName’.

Explanation: The write of the Structured File Server(SFS) name ’serverName’ to file ’fileName’ wasunsuccessful.


User response: Check that you have permission tocreate ’fileName’. Check that the file system, /temp, isnot full. Correct the problem and retry the command.

Destination:

stderr

ERZ038166I Usage: cicssmitsfs { -s serverName | -e }processId.

Explanation: This is the usage message for the CICSprivate command cicssmitsfs. This command is not tobe run from the command line.


User response: None

Destination:

stderr

ERZ038167E You have not selected an SFS.

Explanation: You have not selected a Structured FileServer (SFS).


User response: Select an SFS and retry the operation.

Destination:

stderr

ERZ038169E Usage: cicssfsupdate { -n newServer -ooldServer [-p password] [-v] [-I][[attributeName=attributeValue]...] }

Explanation: This is the usage message for the CICSprivate command cicssfsupdate. This command is notto be run from the command line.


User response: None

Destination:

stderr

ERZ038170E Unable to update details of server’serverName’.

Explanation: The CICS private commandcicssfsupdate was unable to change Structured FileServer (SFS) ’serverName’. Accompanying messagesidentify the cause of the problem.



Destination:

stderr

ERZ038171E Server ’serverName’ is running.

Explanation: The details of Structured File Server(SFS) ’serverName’ cannot be updated because the serveris running.


User response: Shut down the server and retry thecommand.

Destination:

stderr

ERZ038172E Server ’serverName’ has already beenrun.

Explanation: The Structured File Server (SFS)’serverName’ details cannot be modified because theserver has already been run and possibly contains datathat can be lost if the server is modified.


ERZ038163E • ERZ038172E


User response: The server cannot be modified if it hasbeen run. You can force the change by specifying the -Iflag (ignore errors) to the command, but this results inthe destruction of the current server and the creation ofa new server with the modified attributes.

Destination:

stderr

ERZ038173W Server ’serverName’ has already beenrun.

Explanation: The forced changing of Structured FileServer (SFS) ’serverName’ that was run results in thedestruction of the current server and the creation of anew server with the modified attributes. Any existingdata in for this SFS is lost.

System action: Processing continues, all data storedon the SFS is lost.

User response: None

Destination:

stderr

ERZ038174E Usage: cicssfsconf { -? | [-I] [-q] {-R wcregionNameDefaultFileServer=serverName | wcregionName | {ra|na|lr|pr|nr|lqp|lquregionName[[attributeName=attributeValue]...] }}

Explanation: You entered the cicssfsconf commandincorrectly.



Destination:

stderr

ERZ038175E Server ’serverName’ cannot beconfigured.

Explanation: The Structured File Server (SFS) was notconfigured with the desired files.


User response: Check that the SFS server is running.Check for previous messages, if any, to determine thecause of the problem.

Destination:

stderr

ERZ038176I Adding TSQ file ’fileName’ to server’serverName’, volume ’volumeName’.

Explanation: The Temporary Storage Queue (TSQ) file’fileName’ is being added to the Structured File Server(SFS).


User response: None

Destination:

stderr

ERZ038177I Adding TDQ file ’fileName’ to server’serverName’, volume ’volumeName’.

Explanation: The Transient Data Queue (TDQ) file’fileName’ is being added to the Structured File Server(SFS).


User response: None

Destination:

stderr

ERZ038178I Adding Local Queueing file ’fileName’ toserver ’serverName’, volume ’volumeName’.

Explanation: The Local Queueing file ’fileName’ isbeing added to the Structured File Server (SFS).


User response: None

Destination:

stderr

ERZ038179E Unable to create TSQ ’queueId’ on server’serverName’.

Explanation: Temporary Storage Queue (TSQ) file’queueId’ was unable to be created on Structured FileServer (SFS) ’serverName’.


User response: Refer to preceding messages, from theSFS administration command sfsadmin, for the reasonwhy the TSQ was unable to be created.

Destination:

stderr

ERZ038180W Unable to create TDQ ’queueId’ on server’serverName’.

Explanation: Transient Data Queue (TDQ) ’queueId’was unable to be created on the Structured File Server

ERZ038173W • ERZ038180W


(SFS) ’serverName’. The command was run with the -Iflag to ignore errors.


User response: Refer to preceding messages, from theSFS administration command sfsadmin, for the reasonwhy the TDQ was unable to be created.

Destination:

stderr

ERZ038181W Unable to create Local Queue ’queueId’on server ’serverName’.

Explanation: The Local Queue ’queueId’ was unable tobe created on the Structured File Server (SFS)’serverName’. The command was run with the -I flag toignore errors.


User response: Refer to preceding messages, fromsfsadmin, for the reason why the Local Queue wasunable to be created.

Destination:

stderr

ERZ038182I Server ’serverName’ started successfully.

Explanation: The Structured File Server (SFS)’serverName’ started successfully.


User response: None

Destination:

stderr

ERZ038183I Usage: cicssfslock { -? | [ -l | -u | -t ]serverName }

Explanation: This is the usage message for thecicssfslock command.



Destination:

stderr

ERZ038186E Usage: cicssfsnotify subsystemName

Explanation: This is the usage message forcicssfsnotify. This command is not to be entered fromthe command line.


User response: None

Destination:

stderr

ERZ038187I Usage: cicssfsshut { -? | [-f] [-c]serverName }

Explanation: This is the usage message forcicssfsshut.



Destination:

stderr

ERZ038188E Subsystem entry ’subsystemName’ for theserver ’serverName’ was not found.

Explanation: A subsystem entry for serverName wasnot found.


User response: The server name was enteredincorrectly, or the subsystem entry was prematurelydeleted. Correct the problem and retry the command.

Destination:

stderr

ERZ038189W Directory ’directoryName’ cannot bedeleted.

Explanation: The named directory cannot be deleted.This is probably due to the presence of user files in thedirectory that CICS has not created, and therefore doesnot remove.


User response: There is no need to take any action.However, in order to conserve disk resources, it isrecommended that the files are identified and removed.The directory identified here can then be removed.

Destination:

stderr

ERZ038191E Server ’serverName’ is already running.

Explanation: The command you have entered isattempting to start a Structured File Server (SFS) named’serverName’. However, there is already a server of thisname running.


User response: If necessary, shut down the server ofthe same name and retry the command.

ERZ038181W • ERZ038191E


Destination:

stderr

ERZ038194I Usage: cicssfscreate { -? | [-v] [-I] [-mmodelId] serverName[[attributeName=attributeValue]...] }

Explanation: This is the usage message for thecicssfscreate command.



Destination:

stderr

ERZ038195I Directory ’directoryName’ has beendeleted.

Explanation: The directory ’directoryName’ wasremoved, due to errors in the creation of the specifiedStructured File Server (SFS).


User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem and retry the command. If necessary specifythe -I flag to ignore errors.

Destination:

stderr

ERZ038196W Directory ’directoryName’ cannot bedeleted.

Explanation: The command you have enteredunsuccessfully tried to delete the directory’directoryName’ and its contents. Accompanyingmessages identify the cause of the problem. Thismessage indicates that the command has not deleted allthe files in the directory.


User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem (for instance, you can delete the directorymanually). On UNIX use the command rm -rf. OnWindows NT use the rmdir /s. Retry the command.

Destination:

stderr

ERZ038197E A server name was not supplied.

Explanation: The command you have entered requiresthe name of a Structured File Server (SFS), for example,/.:/cics/sfs/default.


User response: Retry the command specifying a validSFS name.

Destination:

stderr

ERZ038202E Usage: cicssfslock { -? | [ -l | -u | -t ]serverName }

Explanation: You entered the cicssfslock commandincorrectly.



Destination:

stderr

ERZ038207E Logical volumes on server ’serverName’could not be recovered.

Explanation: Structured File Server (SFS) ’serverName’unsuccessfully attempted to bring its data volumes upto date with information from its log file, using thecommand tkadmin recover lvols. Accompanyingmessages identify the cause of the problem. The SFSwrites its messages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.


User response: Use accompanying CICS and servermessages to determine the cause of the problem. Shutdown the server (using, for example the cicssfsshutcommand), correct the problem and retry thecommand.

Destination:

stderr

ERZ038194I • ERZ038207E


ERZ038208E Server ’serverName’ could not beenabled.

Explanation: The command was not able to enableStructured File Server (SFS) ’serverName’ for fulloperations, using the sfsadmin enable servercommand. Accompanying messages identify the causeof the problem. The SFS writes its messages to a filecalled msg under the varDir/cics_servers directorystructure in a sub-directory based upon its name (forexample for a server named /.:/cics/sfs/default thefull path of the message file is varDir/cics_servers/SSD/cics/sfs/default/msg). n Windows NT you canfind the drive letter of the disk containing the msg fileby using the cicsname serversdir command.



Destination:

stderr

ERZ038209E Logical volume ’volumeName’ for server’serverName’ could not be enabled.

Explanation: Structured File Server (SFS) ’serverName’was unable to make logical volume ’volumeName’ byusing the tkadmin enable lvol command. The logicalvolume is used to store the data for the server. The SFSwrites its messages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.



Destination:

stderr

ERZ038213W Server ’serverName’ could not be changedto multi-user mode.

Explanation: The Structured File Server (SFS)’serverName’ was unable to be changed from single-usermode to multi-user mode by using the tkadmin clearexclusiveauthority command. Accompanying messages

identify the cause of the problem. The SFS writes itsmessages to a file called msg under thevarDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.



Destination:

stderr

ERZ038214I Authorization for server ’serverName’ hasbeen set to ’authorizationLevel’

Explanation: The authorization level of a StructuredFile Server (SFS) indicates whether or not the serverAccess Control Lists (ACLs) are checked. A value of 0indicates that authorization is disabled and that ACLsare not checked. A value of 1 indicates that ACLs arechecked.


User response: None

Destination:

stderr

ERZ038215E Unable to remove ’primaryRestartFile’ or’backupRestartFile’ for server ’serverName’.

Explanation: When trying to cold start Structured FileServer (SFS) ’serverName’ the restart files that are usedon an auto start were unable to be deleted. The serverhas already been run and possibly contains recoverabledata that can be lost on a cold start. It is not possible tocold start an SFS while either the ’primaryRestartFile’ orthe ’backupRestartFile’ exist. Accompanying messagesidentify the cause of the problem.


User response: Use the accompanying messages todetermine the cause of the problem. Correct theproblem and retry the command.

Destination:

stderr

ERZ038208E • ERZ038215E


ERZ038216I Subsystem ’subsystemName’ has beeninitialized.

Explanation: The subsystem ’subsystemName’ wassuccessfully initialized and a Structured File Server(SFS) was started.


User response: None

Destination:

stderr

ERZ038217I Waiting for subsystem ’subsystemName’to become active.

Explanation: The subsystem ’subsystemName’ wasstarted asynchronously and this message is issuedwhile the command you have entered waits for it tobecome active.


User response: None

Destination:

stderr

ERZ038218E Timed out waiting for subsystem’subsystemName’ respond.

Explanation: The subsystem ’subsystemName’ has notstarted within the time limit allowed by the command.The SFS writes its messages to a file called msg underthe varDir/cics_servers directory structure in asub-directory based upon its name (for example for aserver named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). n Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.


User response: Use the Structured File Server (SFS)messages to determine why the server is not running.

Destination:

stderr

ERZ038219I Server ’serverName’ is responding toRPCs.

Explanation: The Structured File Server (SFS)’serverName’ is responding to Remote Procedure Calls(RPCs). The server is ready to process requests.


User response: None

Destination:

stderr

ERZ038220E Log file ’logfileName’ on server’serverName’ could not be enabled.

Explanation: Log file ’logfileName’ on Structured FileServer (SFS) ’serverName’ was not able to be enabled byusing the tkadmin enable logfile command. The logfile is used to store the recoverable data generated bythe SFS. Accompanying messages identify the cause ofthe problem. The SFS writes its messages to a file calledmsg under the varDir/cics_servers directory structurein a sub-directory based upon its name (for example fora server named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). On Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.


User response: Use the accompanying CICS and SFSmessages to determine the cause of the problem. Shutdown the server (using, for example the cicssfsshutcommand), correct the problem and retry thecommand.

Destination:

stderr

ERZ038221I Log file ’logfileName’ on server’serverName’ has been enabled.

Explanation: Log file ’logfileName’ was enabled tostore the recoverable data generated by Structured FileServer (SFS) ’serverName’.


User response: None

Destination:

stderr

ERZ038222I Logical volumes on server ’serverName’have been recovered.

Explanation: The Structured File Server’s (SFS) datavolumes were updated with the information in theserver’s log file.


User response: None

Destination:

stderr

ERZ038216I • ERZ038222I


ERZ038223I SFS Logical volume ’volumeName’ hasbeen created for server ’serverName’.

Explanation: Logical volume ’volumeName’ wascreated for Structured File Server (SFS) ’serverName’using operating system logical volume created by user.The Logical volume uses the operating system logicalvolume as its backing store and takes on all of itsphysical characteristics.


User response: None

Destination:

stderr

ERZ038224I Logical volume ’volumeName’ on server’serverName’ has been enabled.

Explanation: Structured File Server’s (SFS) logicalvolume ’volumeName’ was made accessible for I/O.Logical volume is used to store the data for the SFS.


User response: None

Destination:

stderr

ERZ038225E SFS Logical volume ’volumeName’ couldnot be created for server ’serverName’.

Explanation: The logical volume ’volumeName’ was notable to be created for Structured File Server (SFS)’serverName’ using the command MapLVol. Theoperating system logical volume failed to be mapped toa logical volume. Accompanying messages identify thecause of the problem.


User response: Use the accompanying CICS and SFSmessages to determine the cause of the problem. Shutdown the server using, for example the cicssfsshutcommand), correct the problem and retry thecommand.

Destination:

stderr

ERZ038226I Logical volume ’volumeName’ has beenadded to server ’serverName’.

Explanation: The logical volume ’volumeName’ wasassociated with Structured File Server (SFS)’serverName’.


User response: None

Destination:

stderr

ERZ038227E ’entryName’ could not be found in SSD.

Explanation: The Structured File Server (SFS) detailsfor ’entryName’ was unable to be retrieved from the SFSServer Definitions (SSD). Accompanying messagesidentify the cause of the problem.



Destination:

stderr

ERZ038228I Server ’serverName’ has been enabled.

Explanation: The Structured File Server (SFS)’serverName’ was enabled for full operations.


User response: None

Destination:

stderr

ERZ038231E No server name has been specified.

Explanation: When a Structured File Server (SFS) iscold started a server name must be explicitly specified.The value of the environment variableCICS_SFS_SERVER is not used.


User response: Retry the command specifying a nameof a SFS.

Destination:

stderr

ERZ038232I Usage: cicssfs { -? | [-t traceMask] [[-TtraceDestination]...] [-a | -nlv] [-I][serverName][[attributeName=attributeValue]...]}.

Explanation: This is the usage message for the cicssfscommand. The server name must be specified on a coldstart. For an auto start the command uses the contentsof environment variable CICS_SFS_SERVER.



Destination:

ERZ038223I • ERZ038232I


stderr

ERZ038233I Cold start of server ’serverName’requested, all data will be destroyed

Explanation: The user has asked for a cold start of aStructured File Server. This causes any data held onthat server to be destroyed.

System action: Start continues

User response: None

Destination:

stderr

ERZ038234I To continue cold start type ’continue’and press enter:

Explanation: The user has asked for a cold start of aStructured File Server. This causes any data held onthat server to be destroyed. A confirmation of thisaction is required before the start continues. Replying″continue″ enables the start to proceed; any otherresponse halts the process.

System action: The process waits for the user to typea response.

User response: ″continue″

Destination:

stderr

ERZ038235I Reply was ’responseString’, cold start ofserver ’serverName’ halted.

Explanation: The user had asked for a cold start of astructured file server, but, as the response to messageERZ38234 was not ″continue″, the start was halted.

System action: The process returns to the systemmanagement panel.

User response: None

Destination:

stderr

ERZ038236I Reply was ’responseString’, cold start ofserver ’serverName’ continuing.

Explanation: The user had asked for a cold start of astructured file server, and the response to messageERZ38234 was continue so the start is continuing.

System action: The cold start continues.

User response: None

Destination:

stderr

ERZ038237I Region ’regionName’ being reset to workwith Structured File Server ’serverName’.

Explanation: The region is reset and configured forSFS ’serverName’.


User response: None

Destination:

stderr

ERZ038238E ’serverName’ is not a valid StructuredFile Server name.

Explanation: The -R option was specified on acicssfsconf command, but the server name supplied,’serverName’, is not valid. The server name must beginwith /.:/.


User response: Issue the command with the name of avalid SFS Server.

Destination:

stderr

ERZ038239E Supply a value for DefaultFileServer.

Explanation: With the -R option the DefaultFileServerattribute must be set on the command line. The nextmessage provides the command syntax. On AIX if thecommand is issued from the SMIT panel, when ″ResetFile Server to SFS?″ is set to ″Yes″, the ″SFS serverstoring CICS Queue Data″ must be modified to specifythe SFS required for configuration.


User response: Issue the command with the name of avalid SFS Server.

Destination:

stderr

ERZ038240W Resource ’resourceName’ was notrecognized from the default SFS ServerDefinition (SSD).

Explanation: The resource specified was not found inthe default SFS Server Definition (SSD).

System action: Processing continues using the defaultvalues.

User response: Check that the default entry exists inthe SFS Server Definitions (SSD). Retry the commandspecifing the correct resource.

Destination:

stderr

ERZ038233I • ERZ038240W


ERZ038243E Unable to locate server ’serverName’

Explanation: CICS attempts to locate a server bysearching for the server on the current machine. CICSis unable to locate the server ’serverName’.


User response: Check that the SFS server is runningon the current machine.

Destination:

stderr

ERZ038244E Process ’programName’ forciblyterminated

Explanation: The process was forcibly terminatedfrom an external signal. The SFS writes its messages toa file called msg under the varDir/cics_serversdirectory structure in a sub-directory based upon itsname. On Windows NT you can find the drive letter ofthe disk containing the msg file by using the cicsnameserversdir command.


User response: Use the accompanying CICS and SFSmessages to determine the cause of the problem.

Destination:

stderr


Explanation: cicssfs tried to access some memory forits own working storage but was unable to do so.



Destination:

stderr

ERZ038246I Usage: cicssfsupdate { -n newServer -ooldServer [-p password] [-v] [-I][[attributeName=attributeValue]...] }

Explanation: This is the usage message for the CICSprivate command cicssfsupdate. This command is notto be run from the command line.


User response: None

Destination:

stderr

ERZ038247E At least one of the operation options{wc,ra,na,lr,pr,nr,lqp,lqu} must be chosen

Explanation: The command line your enter mustspecify at least one of the operation options identifiedin the message.


User response: Consult the usage message and reissuethe command correctly.

Destination:

stderr

ERZ038248E When ’wc’ specified you cannot selectany other operation options

Explanation: On the ’cicssfsconf’ command you haveselected that all files be created to hold the regionsqueues by specifying the ’wc’ option, but you alsoselected at least one other queue type explicitly. Youmust either select all queues by speciying the ’wc’option, or select the queues you require by specifying acompination of (ra,na,lr,pr,nr,lqp,lqu).


User response: Respecify the command selecting onlythe required parameters.

Destination:

stderr

ERZ038249E You must specify a region name

Explanation: The command your entered must specifyat least one of the operation options identified in themessage.


User response: Consult the usage message and reissuethe command correctly.

Destination:

stderr

ERZ038250E You cannot specify any attributeoverrides when ’wc’ option specified

Explanation: You have selected that all queues becreated without changing (wc) any values, but youhave specified extra options on the command line tothe command.


User response: If you require to specify attributeoverrides on the command then reissue the commandspecifying the queue types individually(ra,na,lr,pr,nr,lqp,lqu). Otherwise reissue the commandwithout the extra options that you specified.

Destination:

ERZ038243E • ERZ038250E


stderr

ERZ038251E The ’-R’ option may only be specifiedwhen the ’wc’ option is slected

Explanation: The ’-R’ option to reset the FileServervalues in the region definitions can be specified onlywhen the ’wc’ option is selected to configure all queuesfor the region.


User response: Respecify the command be eitherremoving the ’-R’ option or my changing the queusselector attribute to ’wc’.

Destination:

stderr

ERZ038252E Failed to update all region definitions tonew values

Explanation: You requeted to reset the RegionDefinitions to use the SFS Server for its user files andqueueing files. An error occurred while updating thedatabase.


User response: A previously logged message detailsthe exact nature of the failure. Use this message tocorrect the problem and reissue the command.

Destination:

stderr

ERZ038253W Failed to update all region definitions tonew values

Explanation: You requeted to reset the RegionDefinitions to use the SFS Server for its user files andqueueing files. An error occurred while updating thedatabase.

System action: The command continues, but some ofthe values in the CICS region database possibly need tobe reset manually to ensure that the SFS Server is used.

User response: Previously logged messages detail theexact nature of the failure. Use these messages tocorrect the problem and reissue the command.

Destination:

stderr

ERZ038254E Failed to parse attribute ’attribute’,current value ’value’

Explanation: While executing cicssfsconf, thecommand attempted to interpret the expanded valuefor the attribute identified in the message, but thisattempt failed.

System action: The command halts its attempt to

create the current SFS file and skips to the next stage.

User response: Verify the value identified in themessage is correct and reissue the command.

Destination:

stderr

ERZ038255E SFS operation ’opCode’ failed with error(errorCode) ErrorText

Explanation: While executing cicssfsconf, a CICSToolkit error occurred that prevent the operation fromcompleting succesfully.

System action: The command halts its attempt tocreate the current SFS file and skips to the next stage.


Destination:

stderr

ERZ038257I Usage: cicsmakelv { -? | [-I] -v<volumeName> -s <volumeSize> -p<path>

Explanation: You entered the cicsmakelv commandincorrectly.


User response: Retry the command with validparameters.

Destination:

stderr

ERZ038258E Logical volume with name ’volumeName’already exists

Explanation: You attempted to create a Logicalvolume with the name specified in the message, but alogical volume with that name already exists.

System action: The operation fails with anunsuccessful return code.

User response: If the volume truely no-longer existsthen rerun the command with the ’-I’ option to forcethe redefinition of the Logiocal Volume.

Destination:

stderr

ERZ038259E Logical volume with name ’volumeName’,Path ’volumePath’ already exists

Explanation: You attempted to create a Logicalvolume with the name specified in the message, but a

ERZ038251E • ERZ038259E


fully defined logical volume with that name alreadyexists.


User response: If you wish to redefine the logicalvolume then remove the logical volume and reexecutethe command.

Destination:

stderr

ERZ038260E Error occurred updating Logical Volumelocation information

Explanation: While attempt to update theadministration information for a logcial volume anerror occurred.


User response: Verifty that the current userid hassufficient privelages to perform administration task onthe machine. Also verify the machines registry containsno errors.

Destination:

stderr

ERZ038261E Failed to create data file ’volumePath’ forvolume ’volumeName’

Explanation: The command attempted to create a fileto hold the data associated with the logical volumeidentified in the message but the attempt failed.


User response: Ensure that there is enough room forthe file to be created and reexeute the command.

Destination:

stderr

ERZ038262E Failed to write byteCount bytes to file’fileName’

Explanation: An attempt to write a number of bytes tothe file identified in the message failed. CICS initialisesthe file specified with null characters written in anumber of iterations. Each iteration writes byteCountbytes to the end of the file. The default size for a PPCgateway file is 4194304. The default size for SFS files is67108864.


User response: Verify that the path to the fileidentified in the message exists and that the currentuserid has sufficient privelages to create the file. Also

verify the there is sufficient storage available to createthe file.

Destination:

stderr

ERZ038263E Logical Volume ’volumeName’ does notexist

Explanation: You requested to perform an operationon the logical Volume identified in the message, but theLogical Volume definition was unable to be found.


User response: Verify the name of the logical volumeis correct.

Destination:

stderr

ERZ038264W Failed to remove file ’fileName’

Explanation: The command attempted to delete thefile identified in the message but the attempt failed.

System action: The command continues.

User response: If the file identified in the message stillexists, then verify that it is not still in use by any otherprocesses and then remove it.

Destination:

stderr

ERZ038265W Failed to open file ’fileName’, SFS error’errorString’

Explanation: cicsdestroy attempted to open the fileidentified in the message in order to delete it but theattempt failed.

System action: The file is ignored and cicsdeletecontinues processing.

User response: If the file identified in the message stillexists, then verify that it is not still in use by any otherprocesses and then remove it.

Destination:

stderr

ERZ038266W Failed to remove file ’fileName’, SFSerror ’errorString’

Explanation: cicsdestroy attempted to delete the fileidentified in the message but the attempt failed.

System action: The file is ignored and cicsdeletecontinues processing.

User response: If the file identified in the message stillexists, then verify that it is not still in use by any other

ERZ038260E • ERZ038266W


processes and then remove it.

Destination:

stderr

ERZ038267I Deleting CICS file ’fileName’

Explanation: cicsdestroy is about to delete the namedSFS file.



Destination:

stderr

ERZ038268E Failed to expand file ’fileName’

Explanation: The command you entered attempted tointerpret the expanded value for the attribute identifiedin the message, but this attempt failed.

System action: The command ends with a non zeroreturn code.

User response: Verify the value identified in themessage is correct and reissue the command. If this isokay, check that CICS is installed correctly.

Destination:

stderr

ERZ038269I Usage: cicsremovelv { -? | -v<volumeName>}

Explanation: You entered the cicsremovelv commandincorrectly.


User response: Retry the command with validparameters.

Destination:

stderr

ERZ038270W Redefining logical volume with name’volumeName’, New Path ’volumePath’

Explanation: You attempted to create a Logicalvolume with the name specified in the message. Anentry for this logical volume already exists in theregistry but the volume itself no longer exists.

System action: The command continues, the logicalvolume is created and the entry in the registry isredefined.


Destination:

stderr

ERZ038271W Logical volume with name ’volumeName’,Path ’volumePath’ already exists

Explanation: You attempted to create a Logicalvolume with the name specified in the message, but afully defined logical volume with that name alreadyexists. If the logical volume is already in use by anotherserver, then one of the servers using the logical volumemust be reconfigured to use a different logical volume.

System action: The operation continues and uses theexisting logical volume.

User response: If the logical volume is in use then oneof the servers using the logical volume must bereconfigured to use a different logical volume.

Destination:

stderr

ERZ038272I Waiting for server ’serverName’ toinitialise.

Explanation: The server ’serverName’ was startedasynchronously and this message is issued while thecommand you have entered waits for it complete thefirst stage of its initialisation.


User response: None

Destination:

stderr

ERZ038273E Region RuntimeProtection’regionRuntimeProtection’ is insufficient toaccess server ’serverName’

Explanation: The value of the RuntimeProtectionattribute to none in the Region definitions disables thesending of authenticated RPC’s to the SFS Server. Thevalue of the ProtectionLevel level in the SFS Serverdefinitions is set such that only clients usingauthenticated RPCs are allowed to communicate withthe server.

System action: Processing halts.

User response: Change the RuntimeProtectionattribute in the region definitions to enable the sendingof authenticated RPC’s to the SFS Server and ifnecessary also increase the Protection Level attributesassociated with the queueing files that are created uponthat server.

Destination:

stderr

ERZ038267I • ERZ038273E


ERZ038274E Unable to add ’environmentString’ to theenvironment

Explanation: The command you entered tried to add’environmentString’ to its environment but failed to doso.


User response: Check your system is not fully loaded,as this often is the result of a lack of processingmemory. Check also that you have installed yoursystem correctly.

Destination:

stderr

ERZ038275E Unable to remove ’primaryRestartFile’ or’backupRestartFile’ for server ’serverName’,errno ’errno’.

Explanation: When trying to cold start Structured FileServer (SFS) ’serverName’ the restart files that are usedon an auto start were unable to be deleted. The serverhas already been run and possibly contains recoverabledata that can be lost on a cold start. It is not possible tocold start an SFS while either the ’primaryRestartFile’ orthe ’backupRestartFile’ exist. Accompanying messagesidentify the cause of the problem.


User response: Use the accompanying messages todetermine the cause of the problem. Correct theproblem and retry the command.

Destination:

stderr

ERZ038276E Timed out waiting for subsystem’subsystemName’ respond.

Explanation: The subsystem ’subsystemName’ has notstopped within the time limit allowed by thecommand. The SFS writes its messages to a file calledmsg under the varDir/cics_servers directory structurein a sub-directory based upon its name (for example fora server named /.:/cics/sfs/default the full path of themessage file is varDir/cics_servers/SSD/cics/sfs/default/msg). n Windows NT you can find the driveletter of the disk containing the msg file by using thecicsname serversdir command.


User response: Use the Structured File Server (SFS)messages to determine why the server is notresponding.

Destination:

stderr

ERZ038277E Failed to remove file ’fileName’

Explanation: The command attempted to delete thefile identified in the message but the attempt failed.The most likely causes are that you have insufficentprivilage to remove the file or that the file is still inuse.


User response: If the file is still in use then, stop theserver are rerun the command, otherwise check thepermissions on the file and rerun the command.

Destination:

stderr

ERZ038278E cicssfsconf failed because SFS ServerName ’serverName’ could not beexpanded

Explanation: cicssfsconf could not expand SFS servername to the format /.:/cics/sfs/<server name=″″> asexpected by CICS. This is a rare error,possibly a failureto allocate memory,which could be due to resourceunavailability on the machine.


User response: Check your machine for any longrunning sessions or other resource hogging programs.Stop them and retry. Also, look for any errors prior tothis in the error logs

Destination:

stderr

ERZ038279E Either runtime stanza entry or bothrestart files are missing for the SFSserver ’ServerName’

Explanation: The command attempted to warm startthe SFS, but failed. Either the restart files or theruntime stanza entry for the SFS server is missing, dueto which SFS can not be warm started. As the SFSneeds to be cold started save the data before coldstarting the SFS.

System action: The command terminates wth an error.

User response: Start the SFS server withStartType=Cold option.

Destination:

stderr

ERZ039004E Insufficient storage to initialize theCICS scheduler

Explanation: During region initialization the schedulerwas unable to obtain sufficient storage from the RegionPool to initialize correctly.

System action: CICS abnormally terminates.

ERZ038274E • ERZ039004E


User response: Restart CICS with an increased RegionPool size by overriding the MaxRegionPool attribute(RD) on the command line. Do the same for thepermanent database (using cicsupdate).

Destination:

console.msg

ERZ039005W Transaction ’transId’ rejected due toinsufficient storage

Explanation: CICS cannot accept the request to run atransaction as there is insufficient storage available inthe region.


User response: Resubmit the transaction request whensome storage is made available. This can be achievedby using CEMT to purge unwanted tasks that arealready in the region.

Destination:

console.msg

ERZ039006W Application server serverId terminatingdue to insufficient storage

Explanation: CICS is terminating the applicationserver as there is insufficient storage available in theregion.

System action: CICS continues. If, as a result of theserver terminating, there are fewer than MinServersleft running, an attempt is made to start another one.

User response: None

Destination:

console.msg

ERZ039007W Unable to produce a list of transactionsdue to insufficient storage

Explanation: A request was issued to produce a list oftransactions in the region, probably via CEMT.However, the list cannot be produced as there isinsufficient storage available in the region.

System action: CICS continues. The list of tasks is notproduced.

User response: None

Destination:

console.msg

ERZ039008E Self consistency check failure intransaction scheduler

Explanation: Data held in region storage by thetransaction scheduler has been found to be inconsistentduring CICS self consistency checking.


User response: Because the corrupted data is held inregion storage, it is unlikely that application code hascaused the problem. Save any dump file produced foruse by your support organization. If the problempersists, obtain a dump (see the TXSeries Infocenter)and contact your support organization.

Destination:

console.msg

ERZ041001E RPC call to the name space failed.

Explanation: A crucial RPC call failed. This preventsthe RPC Listener from further processing. MessageERZ4102E gives further indication of the cause of thefailure.

System action: The RPC Listener process terminates.This can possibly result in abnormal termination of theregion.

User response: Check message ERZ4102E for cause ofthe failure.

Destination:

console.msg

ERZ041002E RPC failure message: ’errorMessage’.

Explanation: Reported message ″’errorMessage’″ whenthe RPC call failed.

System action: See the preceding message for theaction that is taken.

User response: The reported message indicates thesource of the problem.

Destination:

console.msg

ERZ041007E The ’cicsrl’ process has already beenstarted for this region

Explanation: The Distributed Computing Environmenthas indicated to CICS that a ’cicsrl’ process alreadyexists for this region.

System action: The ’cicsrl’ process that wasattempting to initialize is terminated. This results in theabnormal termination of the region.

User response: Ensure that the ’cicsrl’ process is notalready running for this region.

Destination:

console.msg

ERZ039005W • ERZ041007E


ERZ041008E The transaction name ’transId’ isunknown to CICS

Explanation:

CICS has received an intersystem request for atransaction ’transId’, which contains characters that arenot supported by CICS for user transactions. Yourregion recognizes the following transactions:-

v User transactions that have a Transaction Definition(TD) installed

v Four CICS private transactions (which are used forcertain function shipping requests), called 0x01, 0x02,0x03, and 0x05.

System action: The transaction from the remotesystem is rejected

User response: Establish which remote system sentthe intersystem request. Arrange for the program orsystem configuration on that remote system to bechanged so that the remote system only sends yourCICS system transactions that your CICS systemrecognizes.

Destination:

console.msg

ERZ041009E Unable to schedule request fortransaction ’transId’ because PPCcommunications are not supported withserver-side transactions

Explanation: CICS has received an intersystem requestfor transaction transId either from a PPC Gatewayserver or from a PPC TCP/IP connection. However,CICS is unable to accept this requests because theregion is running with ServerSideTran=yes in theRegion Definition (RD) entry. This attribute enablesserver-side transactions in the SFS Server, which meansthe region is unable to support PPC communications.

System action: CICS rejects the incoming request.

User response: If you wish the CICS region to supportintersystem requests using PPC communications thenrestart your CICS region with ServerSideTran=no.Alternatively, investigate why the intersystem requestwas sent to your region and alter the configuration inthe remote system or PPC gateway server to preventanother request from being sent.

Destination:

console.msg

ERZ041010E RPC server register interface requestfailed.

Explanation: CICS is unable to register the RPCinterface for use when accepting intersystemcommunication requests from IBM CICS Clients.

Message ERZ4102E gives further indication of the causeof the failure.

System action: The application server processcontinues processing, but the intersystem request isterminated.

User response: Check message ERZ4102E for cause ofthe failure.

Destination:

console.msg

ERZ041012E CICS Client RPC request terminatedwith error: ’errorMessage’.

Explanation: A CICS Clients issued a RPC request torun a transaction, but the request was unable to beprocessed due to the reported error.

System action: The request is rejected.

User response: The reported message indicates thesource of the problem. Check the console log and thesymrecs file for further error diganostics. Correct theerrors before attempting to resubmit the request.

Destination:

CSMT

ERZ041013E CICS Client RPC request failed witherror: ’errorMessage’.

Explanation: A CICS Clients issued a RPC request to arunning transaction with user input data, but therequest was unable to be processed due to the reportederror.

System action: The request is rejected and an errorpassed to the running transaction.

User response: The reported message indicates thesource of the problem. Check the console log and thesymrecs file for further error diganostics.

Destination:

CSMT

ERZ041014E Exception ’exceptionName’ caughtprocessing RPC request from CICSclient

Explanation: CICS detected an unexpected exceptioncondition when processing a RPC request from a CICSClients.

System action: The request is rejected. If the exceptionwas detected in an Application Server (cicsas), theprocess is terminated and CICS continues.

User response: Check any messages before this onefor possible causes of the error. If the problem persistscontact your support organization.

Destination:

ERZ041008E • ERZ041014E


console.msg

ERZ041015E CICS Client RPC request failed witherror: ’errorMessage’.

Explanation: CICS issued a RPC request to a CICSClients with user output data, but the request wasunable to be processed due to the reported error.

System action: The request is rejected and an errorpassed to the running transaction.

User response: The reported message indicates thesource of the problem. Check the console log and thesymrecs file for further error diagnostics.

Destination:

CSMT

ERZ041016I CICS Client ’applId’ no longercommunicating: CD entry: ’sysId’.

Explanation: A CICS client can no longer be contactedby the region.

System action: The region no longer tries tocommunicate with the CICS Client and frees up theapplid for future use by another CICS Client.


Destination:

CSMT

ERZ041017W RPC Server Got invalid request’requesttype’ from cicscp client

Explanation: RPC server receives an invalid requestfrom cicscp. The respective cicscp request may not beprocessed properly.

System action: cicsrl ignores the request and cicscpmight give an error

User response: If such errors occur frequently, pleasecontact Support Team with relevant data.

Destination:

Console file

ERZ042001E Storage allocation request fromTask-Private Pool was unsuccessful

Explanation: CICS is short of Task-Private storage anda storage allocation request for an CICS Clientsterminal install or uninstall operation was unable to besatisfied.

System action: The CICS Clients terminal request isnot performed. CICS abnormally terminates the CTINtransaction with code A42A.

User response: Check for any transactions using largeamounts of storage. Retry the operation. If it is still

unsuccessful, refer to any previous messages written tothe CSMT log and console.msg file that indicate whyTask-Private storage was unable to be allocated.

Destination:

CSMT

ERZ042002E Network failure detected on connectionto client system ’sysId’ (’applId’)

Explanation: The connection to CICS Clients ’sysId’has failed during a terminal install request. Theterminal can not be installed.

System action: CICS abnormally terminates the CTINtransaction with abend code A42D.

User response: Ensure that the CICS system and theconnection to it are available before retrying therequest.

Destination:

CSMT

ERZ042003E CICS-private transaction was invokedincorrectly

Explanation: A CICS-private transaction that can onlybe invoked by an CICS Clients was started by anothermode of invocation.

System action: CICS abnormally terminates thetransaction with code A42B.

User response: Check that the attributeInvocationMode in the Transaction Definition iscorrect. Refer to the TXSeries Infocenter for moreinformation.

Destination:

CSMT

ERZ042004E An invalid request was received fromclient system ’sysId’ (’applId’)

Explanation: An invalid terminal install or uninstallrequest was received from CICS Clients ’sysId’.

System action: CICS abnormally terminates the CTINtransaction with code A42B.

User response: Examine previous messages in theCSMT log for possible causes. If the problem persists,check that the version of the CICS Clients product iscompatible with the version of CICS.

Destination:

CSMT

ERZ041015E • ERZ042004E



Explanation: The CICS Clients request was unable tobe converted from the code page ’codePage1’ to the codepage ’codePage2’. This conversion is carried out whenencoding or decoding data that is about to be sent to,or was received from an CICS Clients.

System action: The CICS Clients terminal request isnot performed.

User response: There is a serious problem with thenational language support (NLS) environment of theCICS system. If a required code page descriptor is notinstalled, a preceding message indicates which one ismissing (see the operating system documentation forfurther information). If this is not the case, contact yoursupport organization.

Destination:

CSMT

ERZ042006I Processing terminal autoinstall requestfrom client system ’sysId’ (’applId’);terminal type is ’deviceType’

Explanation: CICS has started to autoinstall a terminalwith device type ’deviceType’ on behalf of CICS Clients’sysId’.

System action: Terminal autoinstall continues.

User response: None

Destination:

CSMT

ERZ042007E Unable to autoinstall terminal fromclient system ’sysId’ (’applId’); terminaltype is ’deviceType’

Explanation: A CICS Clients has connected to theregion and made an unsuccessful attempt to autoinstalla terminal.

System action: The CICS Clients terminal installrequest is not performed.

User response: Examine previous messages in theCSMT log to determine the reason why the autoinstallwas unsuccessful.

Destination:

CSMT

ERZ042008I Processing terminal install request fromclient system ’sysId’ (’applId’); terminalNETNAME is ’netname’

Explanation: CICS has started to install the predefinedterminal with NETNAME ’netname’ on behalf of CICSClients ’sysId’.

System action: Terminal install continues.

User response: None

Destination:

CSMT

ERZ042009E Unable to install terminal for clientsystem ’sysId’ (’applId’); terminalNETNAME is ’netname’

Explanation: A CICS Clients has connected to theregion and attempted to install a predefined terminalusing NETNAME ’netname’, but this was unsuccessful.


User response: Examine previous messages in theCSMT log to determine the reason why the install wasunsuccessful.

Destination:

CSMT

ERZ042010E Error generating terminal installresponse message for client system’sysId’ (’applId’)

Explanation: An error occurred when generating theresponse message to a CICS Clients terminal installrequest.


User response: Examine previous messages in theCSMT log file to determine the reason why the installwas unsuccessful. If the problem persists, contact yoursupport organization.

Destination:

CSMT

ERZ042011E NETNAME ’netname’ does not exist inthe Terminal Definitions (WD)

Explanation: A CICS Clients has connected to theregion and attempted to install a predefined terminalusing NETNAME ’netname’, but this was unsuccessfulbecause NETNAME ’netname’ is not defined in the WD.


User response: Add an entry to the WD for theNETNAME or try to install the terminal using aNETNAME already defined in the WD.

Destination:

CSMT

ERZ042005E • ERZ042011E


ERZ042012E Terminal ’termId’ with NETNAME’netname’ defines an autoinstalled ortransaction routed terminal

Explanation: A CICS Clients has connected to theregion and attempted to install a predefined terminalusing NETNAME ’netname’, but was unsuccessfulbecause this NETNAME is in use by an autoinstalledterminal or a transaction routed terminal.


User response: Try to install using a differentNETNAME or investigate why the NETNAME is beingused by an autoinstalled terminal or transaction routedterminal.

Destination:

CSMT

ERZ042013E Terminal ’termId’ with NETNAME’netname’ is not defined for client system’sysId’ (’applId’)

Explanation: A CICS Clients has connected to theregion and attempted to install a predefined terminalusing NETNAME ’netname’, but was unsuccessfulbecause the Terminal Definition (WD) for thisNETNAME defines a remote terminal for anothersystem or CICS Clients.


User response: Install using a different NETNAME ormodify the WD to define a terminal either as belongingto this CICS Clients or as a local terminal.

Destination:

CSMT

ERZ042014E Terminal ’termId’ with NETNAME’netname’ is out of service

Explanation: A CICS Clients terminal has attempted toinstall with NETNAME ’netname’, but the TerminalDefinition (WD) entry termId is marked out of service.


User response: Try installing using anotherNETNAME or use the CEMT transaction to set theterminal back in service.

Destination:

CSMT

ERZ042015E Access to WD entry for terminal ’termId’was unsuccessful

Explanation: CICS cannot access the TerminalDefinitions (WD) entry for terminal ’termId’.

System action: The CICS Clients terminal request isnot performed.


Destination:

CSMT

ERZ042016E Terminal ’termId’ with NETNAME’netname’ is already installed

Explanation: A CICS Clients has connected to theregion and attempted to install a predefined terminalusing NETNAME ’netname’, but was unsuccessfulbecause a terminal is already installed using thisNETNAME.


User response: Install the terminal using a differentNETNAME, or do not specify a NETNAME, so that itis autoinstalled.

Destination:

CSMT

ERZ042017I Terminal ’termId’ install is complete forclient system ’sysId’ (’applId’); terminalNETNAME ’netname’

Explanation: A CICS Clients terminal defined in theTerminal Definitions (WD) is successfully installed.


User response: None

Destination:

CSMT

ERZ042018E No terminal model for device type’deviceType’

Explanation: A terminal has attempted to autoinstallwith device type ’deviceType’, but was unsuccessfulbecause there are no terminal models defined in theTerminal Definitions (WD) with DevType=’deviceType’.

System action: The CICS Clients terminal autoinstallrequest is not performed.

User response: Install using another device type thatmatches a DevType entry in the Terminal Definitions(WD), or add an entry to the WD that matches therequested device type.

ERZ042012E • ERZ042018E


Destination:

CSMT

ERZ042019E Unable to generate unique Terminal IDfor terminal autoinstall

Explanation: A CICS Clients has connected to theregion and attempted to autoinstall a terminal, but wasunsuccessful since CICS was unable to generate aunique Terminal ID. This is only likely to occur when avery large number of terminals are defined in theTerminal Definitions (WD) or have autoinstalled to theregion.


User response: Examine the WD and use CEMTINQUIRE TERMINAL to determine how manyterminals are connected to the region. Delete anyunnecessary definitions and try again.

Destination:

CSMT

ERZ042020E Autoinstall user exit program returnedduplicate terminal ’termId’ fromNETNAME ’netname’

Explanation: A CICS Clients terminal has connected tothe region and attempted to autoinstall, but wasunsuccessful because the autoinstall user exit programhas generated a terminal name that already exists.


User response: If you have replaced the autoinstalluser exit program, investigate why a duplicate namewas returned; otherwise report the problem to yoursupport organization.

Destination:

CSMT

ERZ042021I Terminal ’termId’ autoinstall is completefor client system ’sysId’ (’applId’);terminal NETNAME is ’netname’,terminal model is ’model’

Explanation: A CICS Clients terminal is successfullyautoinstalled.


User response: None

Destination:

CSMT

ERZ042022I Retrying insertion with new key name

Explanation: CICS has tried to create a TerminalDefinition (WD) entry with a generated terminalidentifier, but has found that this identifier alreadyexists.

System action: CICS tries to create the terminal againwith a new identifier.

User response: None

Destination:

console.msg

ERZ042023E Unable to run the terminal autoinstalluser exit program

Explanation: A CICS Clients terminal autoinstall oruninstall operation cannot successfully run theautoinstall user exit program.

System action: The CICS Clients terminalautoinstall/uninstall request is not performed.

User response: Check that the CICS-privatetransaction CHAT is defined in the TransactionDefinitions (TD); that the corresponding program isdefined in the Program Definitions (PD); that thetransaction program exists at the pathname specified;and that the program has the correct file permissions. Ifthese are all correct, check the program for codingerrors. If you have not replaced the user exit program,report the problem to your support organization.

Destination:

CSMT

ERZ042024E Terminal autoinstall rejected by userexit program

Explanation: A CICS Clients terminal has connected tothe region and attempted to autoinstall, but wasrejected by the terminal autoinstall user exit program.


User response: If you have replaced the autoinstalluser exit program, investigate why the autoinstall wasrejected; otherwise report the problem to your supportorganization.

Destination:

CSMT

ERZ042025E Invalid terminal model ’modelId’ selectedby user exit program

Explanation: The terminal autoinstall user exitprogram has selected a terminal model that was not inthe list supplied to it.

ERZ042019E • ERZ042025E



User response: If you have replaced the autoinstalluser exit program, check the program for coding errors;otherwise report the problem to your supportorganization.

Destination:

CSMT

ERZ042026E Terminal model ’modelId’ has beendeleted from the Terminal Definitions(WD)

Explanation: The terminal model ’modelId’ selected bythe terminal autoinstall user exit program was deletedfrom the Terminal Definitions (WD).


User response: Try again. Someone possibly deletedthe terminal model ’modelId’ from the TerminalDefinitions (WD) while you were attempting toautoinstall an CICS Clients terminal.

Destination:

CSMT

ERZ042027E Terminal ’termId’ is not a valid clientterminal

Explanation: An uninstall request for terminal ’termId’was received from an CICS Clients that does not ownthe terminal.

System action: The CICS Clients terminal uninstallrequest is not performed.

User response: This is an error either in CICS or inthe CICS Clients product. If the problem persists,contact your support organization.

Destination:

CSMT

ERZ042028I Terminal ’termId’ with NETNAME’netname’ has been uninstalled.

Explanation: A CICS Clients terminal has uninstalledand terminated its connection with the region.

System action: CICS ceases to communicate with theCICS Clients terminal.

User response: None

Destination:

CSMT

ERZ042029E Uninstall of terminal ’termId’ wasunsuccessful

Explanation: A CICS Clients has requested a terminaluninstall from the region, but the uninstall wasunsuccessful.

System action: The CICS Clients terminal uninstallrequest is not performed.

User response: Examine previous messages todetermine why the uninstall was unsuccessful. Refer tothe TXSeries Infocenter for more information ondeleting terminals.

Destination:

CSMT

ERZ042036E Requested APPLID ’applId’ alreadyexists in CD entry ’sysId’

Explanation: A remote system has requested to useAPPLID applId when communicating with the localregion. However, this APPLID is already in use by aremote system that is using Communications Definition(CD) entry sysId.

System action: CICS returns a response to the remotesystem indicating that a CD entry already exists for theAPPLID. A new CD entry for the remote system is notadded to the region.

User response: Change the remote system to requestanother APPLID, or change the RemoteLUNameattribute for CD entry sysId.

Destination:

CSMT

ERZ042037E APPLID ’applId’ requested byDFHCCINX already exists in CD entry’sysId’

Explanation: CICS is installing a newCommunications Definitions (CD) entry for an CICSClients. The autoinstall program, DFHCCINX,requested APPLID applId for this CICS Clients.However, CICS is unable to install a CD entry with thisAPPLID because the APPLID used by an CICS Clientsmust be unique within the local CICS region andAPPLID applId is currently configured in CD entrysysId.

System action: The autoinstall request is backed out.This includes calling DFHCCINX again, this timespecifying the action as UNINSTALL.

User response: Change DFHCCINX to return anotherAPPLID or change the matching RemoteLUNameand/or SNAConnectName attributes in CD entry sysIdto a different value. For more information onDFHCCINX, refer to the TXSeries Infocenter.

Destination:

ERZ042026E • ERZ042037E


CSMT

ERZ042038E SYSID ’sysId’ requested by DFHCCINXalready exists in the CD

Explanation: The SYSID sysId returned by theautoinstall program DFHCCINX is the same as theSYSID (key) of an existing Communications Definition(CD) entry.

System action: CICS calls DFHCCINX indicating thatthe CD entry is being deleted. A new CD entry is notadded for the remote system.

User response: Change DFHCCINX to return anotherSYSID or to use the SYSID passed to it by CICS.Alternatively change the SYSID for CD entry sysId. Formore information on DFHCCINX, refer to the TXSeriesInfocenter.

Destination:

CSMT

ERZ042039E Communications errorprimaryCode/secondaryCode detected byCCIN transaction

Explanation: The CICS to CICS install transaction,CCIN, detected a communications error with theremote system.

System action: CICS abnormally terminates the CCINtransaction.

User response: Ensure that the remote system is stillavailable and restart it if necessary. Refer to TXSeriesInfocenter for further information on the error codesprimaryCode/secondaryCode.

Destination:

CSMT

ERZ042040E Unable to generate unique SYSID for anautoinstalled CD entry

Explanation: A remote system has requested aconnection to the region. However, CICS was unable toautoinstall a CD entry for the remote system because itcan not generate a unique SYSID for the CD entry. Thisis only likely to occur when a very large number ofremote systems and terminals are defined in theCommunications Definitions (CD) and TerminalDefinitions (WD).

System action: CICS sends a response to the remotesystem indicating it is busy and that the remote systemcan try to reconnect later.

User response: Examine the CD and WD and useCEMT INQUIRE TERMINAL to determine how manyterminals are connected to the region. Delete anyunnecessary definitions and retry the connectionrequest from the remote system.

Destination:

CSMT

ERZ042041E Invalid terminal name ’termId’ returnedby user exit program

Explanation: The terminal autoinstall user exitprogram has returned an invalid terminal name.


User response: If you have replaced the autoinstalluser exit program, check the program for coding errors;otherwise report the problem to your supportorganization.

Destination:

CSMT

ERZ042042E Removal of CD entry for remote system’applId’ is not allowed from system’sysId’

Explanation: The remote system defined inCommunications Definition (CD) entry sysId scheduleda CCIN transaction and requested that CICS removethe CD entry for system applId. This is not allowed. Aremote system can only request the removal of its ownCD entry.

System action: CICS does not remove the CD entry.

User response: Check the remote system is correctlyconfigured. If the problem persists, contact yoursupport organization.

Destination:

CSMT

ERZ042043I Waiting for tasks to finish with CDentry ’sysId’ for remote system ’LUname’

Explanation: CICS is uninstalling (deleting) CD entrysysId, either because the remote system LUnamerequested it or because the connection to the remotesystem has failed. CICS is waiting while outstandingintersystem requests from the remote system complete.

System action: CICS retries the uninstall.

User response: None

Destination:

CSMT

ERZ042044E Could not delete CD entry ’sysId’ forremote system ’LUname’

Explanation: The remote system LUname isuninstalling, either due to a request from the remotesystem, or because communications to the remotesystem have failed. CICS has waited for the tasks using

ERZ042038E • ERZ042044E


Communications Definition (CD) entry sysId tocomplete, but this has not happened. CICS is thereforeunable to delete the CD entry. If the remote system iscommunicating with your region using a SystemsNetwork Architecture (SNA) connection then CICSreuses CD entry sysId when the remote systemreconnects. If the remote system is communicating withyour region using CICS family TCP/IP support, thenCICS creates a new CD entry client when the remotesystem reconnects. CD entry sysId remains in theregion, unused and unusable, until the region isrestarted. This, in itself, does not cause problems inyour region. However, the CD entry is using regionstorage so, if this message occurs frequently, othertransactions can possibly fail due to lack of storage.

System action: CICS cannot delete the CD entry forthe remote system. The CCIN transaction completes.

User response: If this message occurs frequently, alterthe applications that are using the CD entry so they usethe CD entry for as short a time as possible.

Destination:

CSMT

ERZ042050E The CCIN transaction has abnormallyterminated with abend code ’abendCode’

Explanation:

The CICS to CICS install transaction, CCIN, hasabnormally terminated. This can be because:

v CCIN was invoked incorrectly.

v CCIN was unable to acquire sufficient storage toprocess the request.

v The remote system has sent unrecognized data toCICS.

v The connection between the remote system and CICSfailed.

v The user exit DFHCCINX abnormally terminated.

A symptom record (symrec) is created and furthermessages can be logged to CSMT. These provideadditional information about the cause of the problem.

System action: CICS abnormally terminates the CCINtransaction with abend code abendCode.

User response: Follow the instructions given for theabend code abendCode and any additional messageslogged to CSMT. If you can not solve the problemyourself, save the CSMT log, console.msg file and thesymrec file and contact your support organization.

Destination:

CSMT

ERZ042051E DFHCCINX abnormally terminatedduring the autoinstall of CD entry ’sysId’for remote system ’LUname’

Explanation: The CICS-supplied program, DFHCCINXabnormally terminated while processing an autoinstallrequest for remote system LUname. If you are using thesupplied version of DFHCCINX it means that either theCCIN Transient Data Definition (TDD) entry for CCINis missing, or the program was compiled with adifferent parameter structure than the one used byCICS.

System action: CICS abnormally terminates the CCINtransaction and the CD entry is not installed in theregion. Additional messages are logged indicating theabend code used by DFHCCINX.

User response: Examine the logic for programDFHCCINX to determine why it abnormallyterminated. Correct the cause of the error and retry theconnection request from the remote system.

Destination:

CSMT

ERZ042052W DFHCCINX abnormally terminatedduring the delete of autoinstalled CDentry ’sysId’

Explanation: The CICS-supplied program, DFHCCINXabnormally terminated while processing a delete ofCommunications Definitions (CD) entry sysId. If youare using the supplied version of DFHCCINX it meansthat either the CCIN Transient Data Definition (TDD)entry for CCIN is missing, or the program wascompiled with a different parameter structure than theone used by CICS.


User response: If DFHCCINX maintains any dataabout autoinstalled CD entries, this data is nowpossibly inconsistent. Examine the logic for DFHCCINXto determine if the program abend has affected yourregion.

Destination:

CSMT

ERZ042053E Unable to link to program DFHCCINXfor the autoinstall of CD entry ’sysId’ forremote system ’LUname’

Explanation: There is an error in the ProgramDefinition (PD) entry for the DFHCCINX program. Thismeans CICS is unable to process the autoinstall of aCommunications Definition (CD) entry for remotesystem LUname.

System action: CICS abnormally terminates the CCINtransaction and a CD entry is not installed. CICS sendsa response to the remote system indicating that it is

ERZ042050E • ERZ042053E


busy and the remote system can retry the connectionrequest later. Additional messages can be logged thatdescribe the problem with the PD entry.

User response: Correct the PD entry for DFHCCINXand install it in your region. Then retry the connectionrequest from the remote system. Refer to the TXSeriesInfocenter for more information on DFHCCINX and itsPD entry.

Destination:

CSMT

ERZ042054I DFHCCINX has vetoed the autoinstallof CD entry ’sysId’ which hasRemoteLUName set to ’LUname’

Explanation: The DFHCCINX program was called tovalidate the autoinstall of Communications Definition(CD) entry sysId. It returned a response indicating thatCICS is not supposed to autoinstall this CD entry.

System action: CICS does not perform the autoinstallrequest. A response is send to the remote systemindicating that the autoinstall request was cancelled.

User response:

If the remote system is not allowed to contact yourCICS region, no further action is required. If the remotesystem is able to contact the local region, either:

v Alter the DFHCCINX program to allow this remotesystem to connect to your region. The TXSeriesInfocenter describes how to configure, write andinstall a new version of the DFHCCINX program.

or

v If the remote system is a CICS region, define a CDentry for it. Then DFHCCINX is not called. TheTXSeries Infocenter

Once you have made the necessary changes to yourregion, retry the connection request from the remotesystem.

Destination:

CSMT

ERZ042055I The code page for autoinstall of CDentry ’sysId’ which has RemoteLUNameset to ’LUname’ is invalid. The code pagereceived from the remote system was’receivedCodePage’, the default code pageis ’defaultCodePage’ and the local codepage is ’localCodePage’

Explanation:

The DFHCCINX program indicates that the code pagefor autoinstalled Communications Definition (CD) entrysysId is not supported by the local system. If your

region is using the supplied version of DFHCCINX, itmeans that:

v the code page specified in the RemoteCodePageTRattribute of the default Communications Definition(CD) entry ″″ is ″″ and

v data conversion routines are not available forconversion between the local code page and the codepage, if any, received from the remote system.

No data conversion can be performed for transactionrouting requests sent between the local region and theremote system.

System action: CICS installs a CD entry for the remotesystem in the region. The RemoteCodePageTRattribute for this CD entry is set to the local code pageso no data conversion is performed. CICS sends a badresponse to the remote system indicating the code pageis invalid.

User response: If your region is using the suppliedversion of DFHCCINX, modify theRemoteCodePageTR attribute in the default CD entry″″ to a code page that is suitable for the remote system.Disconnect the remote system from your region touninstall the remote system’s CD entry. When theremote system reconnects, it uses the new value inRemoteCodePageTR as the remote system’s code page.If your region is not using the supplied version ofDFHCCINX, examine the code for your region’sDFHCCINX to determine why it returnedCICS_CCINX_RETURNCODE_BADCP. For moreinformation on DFHCCINX refer to the TXSeriesInfocenter.

Destination:

CSMT

ERZ042056W CD entry sysId for EBCDIC systemLUname is configured with ASCII codepage ’codePage’

Explanation: CICS has opened a connection to remotesystem LUname using the information inCommunications Definition (CD) entry sysId. Thisremote system uses EBCDIC code pages for transactionrouting. However, CD entry sysId is configured with anASCII code page codePage in attributeRemoteCodePageTR. CICS is not able to correctlyinterpret transaction routing data received from thisremote system.

System action: The connection is acquired. However,transaction routing requests on this connection fail.

User response: Alter the RemoteCodePageTRattribute in CD entry sysId so that it specifies the sameEBCDIC code page as defined for the connection inremote system LUname. The TXSeries Infocenterattribute and describes how to update the CD entry.

Destination:

ERZ042054I • ERZ042056W


console.msg

ERZ042057E SYSID ’sysId’ requested by DFHCCINXalready exists in the WD

Explanation: The SYSID sysId returned by theautoinstall program DFHCCINX is the same as theTERMID (key) of an existing Terminal Definition (WD)entry.

System action: CICS calls DFHCCINX indicating thatthe CD entry is being deleted. A new CD entry is notadded for the remote system.

User response: Change DFHCCINX to return anotherSYSID or to use the SYSID passed to it by CICS.Alternatively change the TERMID for WD entry sysId.

Destination:

CSMT

ERZ042058E A CICS Client has requested APPLIDapplId which is defined in server CDentry sysId

Explanation: An CICS Clients is using APPLID applIdthat matches the attributes of CommunicationsDefinitions (CD) entry sysId. However, CD entry sysIdis defined for a remote CICS region (server). CICS isunable to install a CD entry for the CICS Clientsbecause it cannot distinguish between requests for theremote CICS region and the CICS Clients.

System action: CICS sends a response to the CICSClients indicating that it can not accept the connectionrequest.

User response: Examine CD entry sysId. If this CDentry defines a remote CICS region that is able toconnect to your region then alter the APPLID used bythe CICS Clients. Alternatively, delete CD entry sysIdfrom your region and the CICS Clients is then able toconnect using APPLID applId.

Destination:

CSMT

ERZ042059E Remote CICS region, LUname, has thesame name as the CICS client using CDentry sysId

Explanation: An CICS Clients is using APPLIDLUname and Communications Definitions (CD) entrysysId. This APPLID is the name of a remote CICSregion (server) that is trying to autoinstall a CD entryin the local region. CICS is unable to install a CD entryfor the remote CICS region as it cannot distinguishbetween requests for the remote CICS region and theCICS Clients.

System action: CICS sends a response to the remoteCICS region indicating that it can not accept theconnection request.

User response:

Alter the APPLID used by the CICS Clients. Then theremote CICS region can connect to your region.

Note: If you are unable to identify the CICS Clientsthat is using APPLID LUname and you wish theremote region to connect to your region ratherthat the CICS Clients then define a CD entry forthe remote CICS region and delete CD entrysysId. Then the next time the CICS Clientsconnects to your region, the request fails. Theowner of the failing CICS Clients then reportsthe error or changes the CICS Clients’s APPLID.

Destination:

CSMT

ERZ042060E Communications errorprimaryCode/secondaryCode detected byCTIN transaction

Explanation: The CICS Clients terminal installtransaction, CTIN, detected a communications errorwith the client system.

System action: CICS abnormally terminates the CTINtransaction.

User response: Ensure that the client system is stillavailable and restart it if necessary. Refer to theTXSeries Infocenter for further information on the errorcodes primaryCode/secondaryCode.

Destination:

CSMT

ERZ042061E RemoteLUName attribute remoteLUnamein CD entry sysId is not the name ofremote system remoteSystem

Explanation:

CICS has opened a connection to a remote systemusing the information in Communications Definition(CD) entry sysId. However, CICS is unable tocommunicate with this remote system as theRemoteLUName attribute in the CD entry defined thename of the remote system as remoteLUname whereasthe remote system is actually called remoteSystem. Thisis possibly because:

v The location of the remote system configured in CDentry sysId is incorrect.

v The remote system is CICS OS/2 and was justupgraded from version 2 to version 3. This upgradechanges the name of the CICS OS/2 system.

v The name of the remote system is incorrectlyconfigured in CD entry sysId.

System action: CICS closes the connection to theremote system. Further messages can be logged.

User response:

ERZ042057E • ERZ042061E


Examine CD entry sysId and either:

v Alter CD entry sysId so that RemoteLUName is setto remoteSystem.

or

v Alter the RemoteTCPAddress, RemoteTCPPort andListenerName attributes in CD entry sysId to containthe location of remote system remoteLUname.

Install the updated CD entry into your region andrerun the connection request. The TXSeries Infocenterdescribes how to update CD entries in your region.

Destination:

console.msg

ERZ042062W RemoteCodePageTR attributeremoteCodePageTR in CD entry sysId isnot the same as code pagereceivedCodePage received from remotesystem remoteSystem

Explanation: CICS is opening a connection to remotesystem remoteSystem using the information inCommunications Definition (CD) entry sysId. However,remote system remoteSystem is reporting its code pageas receivedCodePage whereas the RemoteCodePageTRattribute in CD entry sysId is remoteCodePageTR. Thismeans transaction routing data conversion can possiblyfail on this connection.

System action: The connection is acquired. However,transaction routing requests on this connection canpossibly fail.

User response: Alter the RemoteCodePageTRattribute in CD entry remoteCodePageTR so that itspecifies code page receivedCodePage. The TXSeriesInfocenter attribute and describes how to update theCD entry.

Destination:

console.msg

ERZ042063E RemoteLUName attribute remoteLUnamein CD entry sysId is not the name ofremote system remoteSystem

Explanation:

CICS has received a connection request from a remotesystem using the TCP/IP address and port configuredin Communications Definition (CD) entry sysId.However, CICS is unable to communicate with thisremote system as the RemoteLUName attribute in theCD entry defined the name of the remote system asremoteLUname whereas the remote system is actuallycalled remoteSystem. This is possibly because:

v The location of the remote system configured in CDentry sysId is incorrect.

v The remote system is CICS OS/2 and was justupgraded from version 2 to version 3. This upgradechanges the name of the CICS OS/2 system.

v The remote system is CICS OS/2 version 2 and it isusing multiple TCP/IP network adapters. This canalter the name of the remote system each time itattaches.

v The name of the remote system is incorrectlyconfigured in CD entry sysId.

System action: CICS closes the connection to theremote system. Further messages can be logged.

User response:

Examine CD entry sysId and either

v Alter CD entry sysId so that RemoteLUName is setto remoteSystem.

or

v Alter the RemoteTCPAddress, RemoteTCPPort andListenerName attributes in CD entry sysId to containthe location of remote system remoteLUname.

or

v Delete CD entry sysId. When the remote system nextconnects, CICS autoinstalls a new CD entry for it.

Once your have made changes to the configurationrerun the connection request. The TXSeries Infocenterdescribes how to update CD entries in your region.

Destination:

console.msg

ERZ042064E Cannot autoinstall terminal withNETNAME ’netname’ - already in use

Explanation: A CICS Clients has connected to theregion and attempted to autoinstall a terminal usingNETNAME ’netname’, but was unsuccessful because aterminal is already installed using this NETNAME.


User response: Install the terminal using a differentNETNAME, or do not specify a NETNAME, so thatCICS generates a unique one for it.

Destination:

CSMT

ERZ042065I The password option, passwordOption,requested by DFHCCINX for client sysIdwill be ignored

Explanation: The CICS supplied program DFHCCINXis called each time an IBM CICS Client connects to theregion. This program is able to specify the attributes ofthe Communications Definition (CD) entry that is

ERZ042062W • ERZ042065I


auto-installed by CICS for the client. One of theattributes DFHCCINX can specify is how passwordssent by the client are managed by CICS. In this case,the value, passwordOption, specified by DFHCCINX forclient sysId is ignored because the value for theRemoteSysSecurity attribute that was also requestedby DFHCCINX was not verify. Password managementcan only be controlled if RemoteSysSecurity=verify.The passwordOption value is specified in theRemoteSysSecurity field of the COMMAREA returnedby DFHCCINX. The correct values for this field aredefined in the header file for this program calledcics_ccinx.h.

System action: CICS continues processing. The CDentry is successfully auto_installed.

User response: No action is required. This message isfor information only.

Destination:

CSMT

ERZ043001W The OutboundUserIds field in CD entry’sysId’ is incorrect

Explanation: The OutboundUserIds attribute in theCommunications Definition (CD) entry, sysId, isinconsistent with the configuration in either the remotesystem or your SNA services. The OutboundUserIdsattribute determines whether CICS sends userids withoutbound intersystem requests. This message occurs ifOutboundUserIds=sent and the remote system is notconfigured to receive userids. Refer to the TXSeriesInfocenter for more information.

System action: CICS sends the intersystem requestwithout a userid.

User response: Examine the configuration in theremote system, your SNA services and CD entry sysIdand alter it so it is consistent and provides enoughsecurity information for the intersystem request toexecute on the remote system.

Destination:

CSMT

ERZ043002E Remote transaction ’transId’ was notaccepted by the remote server within thetimeout specified in CD entry ’sysId’

Explanation: The remote transaction transId did notstart on the remote CICS region or PPC Gateway serverwithin the timeout specified by the AllocateTimeoutattribute of the Communications Definition (CD) entrysysId.

System action: CICS abnormally terminates theintersystem request. Further messages can possibly belogged.

User response:

Examine the message files on the remote system and onthe local system to obtain further information as towhy the remote transaction did not start within thetimeout period. If the remote transaction was unable tobe started because the remote system does not haveenough application servers, increase the number ofavailable Application Servers in the remote system byeither:

v amending the MaxServer attribute in the remotesystem’s Region Definition (RD) entry).

v using the CEMT SET TCLASS MAXSERVERScommand on the remote system.

Alternatively, consider increasing the value of theAllocateTimeout attribute in the CD entry. If you needfurther information, see the TXSeries Infocenter.

Destination:

CSMT

ERZ043003E An unexpected error (’errorCode’)occurred during intersystemscommunication to system ’sysId’.

Explanation: An attempt has been made to flowinvalid data during intersystems communication.


User response: Refer to the errorCode for the cause ofthe problem.

Destination:

CSMT

ERZ043004E An unexpected error (’errorCode’)occurred during intersystemscommunication to system ’sysId’

Explanation: An error was detected whilecommunicating with the remote system sysId.

System action: CICS abnormally terminates thetransaction with abend code A43B.

User response: Ensure the remote system and theconnection to it are available.

Destination:

CSMT

ERZ043005E An inconsistency has been detected in aCICS internal data structure


System action: The region continues, but intersystemscommunication can possibly be unsuccessful.

User response: Restart your region. If the condition

ERZ043001W • ERZ043005E


persists, perform a system dump and contact yoursupport organization.

Destination:

console.msg

ERZ043006I Communications switch layersuccessfully initialized.

Explanation: Communications switch layersuccessfully initialized.


User response: None

Destination:

console.msg

ERZ043007E The remote system ’sysId’ is not knownlocally

Explanation: An attempt has been made to contact asystem that is not known locally. This is because theLocalSysId is null, or the sysId is the LocalSysId, or theRemoteLUName is the same as the local region nameor the PPC Gateway has been restarted since the regionstarted.

System action: CICS abnormally terminates thetransaction with A43D.

User response: Make any of the corrections to theRegion Definitions (RD) and CommunicationDefinitions (CD) as described above and then restartthe region.

Destination:

CSMT

ERZ043008E An asynchronous backout occurredduring intersystems communicationwith system ’sysId’

Explanation:

The transaction was backed out by a remote server orapplication while it was communicating with theremote system defined in Communications Definition(CD) entry ’sysId’. Possible reasons for this include:

v The transaction on the remote region was forcepurged or abnormally terminated.

v A remote SFS server experienced an error or wasterminated prematurely.

v A PPC Gateway server experienced an error or wasterminated prematurely.

v The transaction is communicating with anapplication that issued a tran_Abort call. This is notpermitted while the distributed logical unit of work(LUW) is using a PPC Gateway server or a PPCTCP/IP connection.

v The Remote Procedure Call (RPC) mechanism isunavailable.

System action: CICS abnormally terminates thetransaction with abend code A43E. All synchronizationlevel 2 conversations are abnormally terminated.

User response: Examine the messages produced by allthe applications and servers involved in the distributedLUW. This includes PPC gateway Servers, StructuredFile Servers (SFS) and CICS on Open Systems regions.If any of these has reported errors, correct the cause ofthese errors and rerun the transaction. Look forincorrect parameters being passed to CICS, timeoutsexpiring or, if your application includes a remote CICSapplication, then ensure it is not issuing a tran_Abortcommand. Rerun the transaction once it has beencorrected.

Destination:

CSMT

ERZ043009E Local SNA must be initialized beforetransaction transId can use CD entrysysId

Explanation:

Transaction transId made an intersystem request thatspecified Communications Definition (CD) entry sysId.This CD entry is configured withConnectionType=local_sna, which means theconnection is to use Local SNA support. However, theLocal SNA support is unavailable either because:

v a Listener Definition (LD) entry with Protocol=SNAis not defined, or

v the SNA product used by your region is not installedor configured correctly.


User response:

v Check that an appropriate SNA product is installedon your machine.

v Check this SNA product is correctly configured. TheTXSeries Infocenter

v Ensure that a LD entry exists that has Protocol=SNA.The TXSeries Infocenter describes how to configureLocal SNA support.

Once Local SNA is configured, ensure that the LocalSNA support activated successfully during regioninitialization. Then rerun the request.

Destination:

console.msg

ERZ043006I • ERZ043009E


ERZ043010E Modename modeName configured in TDentry transId is unavailable forconnecting to remote system sysId

Explanation:

Transaction transId issued an intersystem request to theremote system configured in CommunicationsDefinition (CD) entry sysId. However, this request wasunsuccessful because the modename modeNameconfigured in the SNAModeName attribute ofTransaction Definitions (TD) entry transId is notcorrectly defined in either the local SNA product or theremote system. This problem can be caused because:

v The modename has been specified incorrectly in TDentry transId.






v The modename is SNASVCMG or CPSVCMG and socannot be used by CICS transactions.


User response:


v The modename modeName used in the TD entrytransId is correctly configured in both the local SNAproduct and the remote system.



Once any necessary corrections have been made, rerunthe request. The TXSeries Infocenter provides moreinformation on the use of modenames by CICS.

Destination:

CSMT

ERZ043011E Modename modeName is unavailable forconnecting to remote system sysId

Explanation:

An intersystem request was made to the remote systemconfigured in Communications Definition (CD) entrysysId. However, this request was unsuccessful becausethe modename modeName configured in theDefaultSNAModeName attribute of this CD entry isnot correctly defined in either the local SNA product orthe remote system. This problem can be causedbecause:

v The modename has been specified incorrectly in theCD entry.

v The CD entry is not configured with the correctremote system information in the RemoteLUName,RemoteNetworkName and SNAConnectNameattributes.





v The modename is SNASVCMG or CPSVCMG and socannot be used by CICS transactions.


User response:


v The modename used in the CD entry is correctlyconfigured in both the local SNA product and theremote system.

v The CD entry specifies the correct remote system.Check the settings of the RemoteLUName,RemoteNetworkName and SNAConnectNameattributes.


Once any necessary corrections have been made, rerunthe request. The TXSeries Infocenter provides moreinformation on the use of modenames by CICS.

ERZ043010E • ERZ043011E


Destination:

CSMT

ERZ043012E Default modename configured in localSNA product is unavailable forconnecting to remote system sysId

Explanation:

An intersystem request was made to the remote systemconfigured in Communications Definition (CD) entrysysId. However, this request was unsuccessful becausethe default modename is not correctly configured ineither the local SNA product or the remote system. Thisproblem can be caused because:



v The local SNA product does not have a defaultmodename defined or does not support thedefinition of a default modename.

v The remote system does not have the local SNAproduct’s default modename defined.

v The definition of this modename in the local SNAproduct is inconsistent with the definition of themodename in the remote system.

v The default modename is SNASVCMG or CPSVCMGand so cannot be used by CICS transactions.


User response:

Examine CD entry sysId and the SNA configuration inboth your local SNA product and the remote system.You are looking for inconsistencies within thisconfiguration. Ensure that:



Once you are sure the correct remote system is beingcontacted, look at the setting of the default modenamein your SNA product. Refer to the TXSeries Infocenterfor information about how this is configured. Makesure it is set to a modename that can be used to contactmost, if not all, of the remote systems used by yourregion. If the default modename for your SNA productis not recognized by the remote system configured in

CD entry sysId, set the DefaultSNAModeName in CDentry sysId to a modename that is configured in boththe remote system and the local SNA product. Onceany necessary corrections have been made, rerun therequest.

Destination:

CSMT

ERZ043014E Transaction transId issued an intersystemrequest to system sysId when a backoutwas required

Explanation: CICS is unable to proceed with anintersystem request to the remote system configured inCommunications Definition (CD) entry sysId becausethe transaction that issued the request, transId, is inbackout required state. Backout required state(sometimes referred to as rollback required state) occurswhen a transaction receives a backout request from aremote system or when a synchronization level 2intersystem request is abnormally terminated. (Refer tothe TXSeries Infocenter for an explanation of whensynchronization level 2 intersystem requests are usedand their implications.) When a transaction is inBackout required state it can not start newsynchronization level 2 intersystem requests. Inaddition, all Distributed Transaction Processing (DTP)synchronization level 2 conversations controlled by thetransaction switch to rollback state, which effectivelyprevents work on these conversations. (Refer to theTXSeries Infocenter for information on the DTPcommands and resulting conversation states.) TheBackout required state is cleared when a transactionissues an EXEC CICS SYNCPOINT ROLLBACKcommand. This backs out changes to recoverableresources and allow synchronization level 2 requests toproceed. (The TXSeries Infocenter describes the EXECCICS SYNCPOINT ROLLBACK command.)


User response: Look for additional messages writtento the CSMT log for transaction transId. These can helpyou identify which intersystem request issued by thetransaction was unsuccessful. Examine the applicationcode for transaction transId. Try to locate theintersystem request that caused the transaction to enterbackout required state. Correct the error processingassociated with this intersystem request so that EXECCICS SYNCPOINT ROLLBACK is issued whenever anerror occurs that puts the transaction into backoutrequired state.

Destination:

CSMT

ERZ043012E • ERZ043014E


ERZ043015I The default modename for the region is’modeName’

Explanation: CICS has read the modename modeNamefrom the CICS_SNA_DEFAULT_MODE environmentvariable. This modename has been truncated to 10characters.



Destination:

console.msg

ERZ043016W The ’modeName’ modename should notbe used by CICS transactions

Explanation: The modeName modename is a reservedSNA modename used by SNA service transactions. Itmust not be used by CICS transactions, as this canimpact the management of the SNA network. SomeSNA products prohibit the use of this modename.

System action: CICS continues processing. Subsequentintersystem requests using this modename can possiblybe unsuccessful.

User response: Change the configuration in your CICSregion to ensure that the modenames used by yourtransactions are not the reserved SNA modenames,SNASVCMG or CPSVCMG. The TXSeries Infocenterdescribes how to configure modenames in CICS.

Destination:

console.msg or CSMT

ERZ043017E The ’modeName’ modename specified inCICS_SNA_DEFAULT_MODE isunavailable for connecting to remotesystem sysId

Explanation:

An intersystem request was made to the remote systemconfigured in Communications Definition (CD) entrysysId. However, this request was unsuccessful becausethe default modename modeName specified in theCICS_SNA_DEFAULT_MODE environment variable isnot correctly configured in either the local SNA productor the remote system. This problem can be causedbecause:

v The CD entry modeName is not configured with thecorrect remote system information in theRemoteLUName, RemoteNetworkName andSNAConnectName attributes.


v The remote system does not have this defaultmodename defined.

v The definition of this modename in the local SNAproduct is inconsistent with the definition of themodename in the remote system.

v The default modename is SNASVCMG or CPSVCMGand so cannot be used by CICS transactions.


User response:

Examine CD entry modeName and the SNAconfiguration in both your local SNA product and theremote system. You are looking for inconsistencieswithin this configuration. Ensure that:

v CD entry modeName specifies the correct remotesystem. Check the settings of the RemoteLUName,RemoteNetworkName and SNAConnectNameattributes.


Once you are sure the correct remote system is beingcontacted, check that the default mode name isconsistently defined both in your local SNA productand in the remote system. If the default modename foryour SNA product is not recognized by the remotesystem configured in CD entry modeName you canchoose to change the default modename or set theDefaultSNAModeName in CD entry sysId to amodename that is configured in both the remotesystem and the local SNA product. The TXSeriesInfocenter has more information on the modenamesused by CICS transactions. Once any necessarycorrections have been made, rerun the request.

Destination:

CSMT

ERZ045001I Unsuccessful Resource Security Level(RSL) access for resource ’resourceName’,class ’className’, userid ’userId’,transaction id ’transId’

Explanation: User ’userId’ is attempting to accessresource ’resourceName’ in resource class ’className’from within transaction ’transId’. Probably the user’userId’, or the transaction ’transId’, does not have therequired RSL key to access this resource. Alternatively,in a multiregion environment, the communications linkpossibly does not have the required RSL key to accessthis resource.

System action: The program determines how CICShandles this error.

User response: Check that the RSL key for the userid,the transaction, and the communications link, if

ERZ043015I • ERZ045001I


applicable, match the RSL Key for the resource beingaccessed.

Destination:

CSMT

ERZ045002W No such resource ’resourceName’, class’className’

Explanation: A transaction attempted to access aresource that does not exist.


User response: The transaction program determineshow CICS handles this error. Check transactionprograms for resource names that have beenwithdrawn from the region’s definitions.

Destination:

CSMT

ERZ045003E A transaction (’transId’) attempted tostart with an invalidStartType/FacilityType combination

Explanation: A transaction was unable to be startedbecause the way in which it was started, or the facilityit was started against, conflicts with the start methodsor the facility values specified in the InvocationModeattribute of the transaction definition.

System action: The transaction is not started.

User response: Check the InvocationMode of thetransaction definition to ensure that transaction isconfigured with the appropriate StartType andFacilityType for its operating environment. TheTXSeries Infocenter provides guidance on setting atransaction’s InvocationMode. Some of the CICSsupplied transactions can be started only by particularmethods or against particular facilities. Do not changethe InvocationMode attributes of the CICS suppliedtransactions.

Destination:

console.msg

ERZ045004E Unsuccessful Transaction Security Level(TSL) access for user ’userId’, transaction’transId’

Explanation: User ’userId’ attempted to run transaction’transId’. The user probably does not have the requiredTSL key to run this transaction. Alternatively, in amulti-region environment, the communications linkpossibly does not have the required TSL key to run thistransaction.

System action: CICS prevents access to the namedtransaction.

User response: Check that the TSL key for the userid,

and the communications link in a multi-regionenvironment, match the TSL Key for the transaction.

Destination:

CSMT

ERZ045005E A transaction attempted to start at aninappropriate execution phase in theregion

Explanation: CICS operates in a number of executionphases. A transaction definition defines the executionphases a transaction can run in and CICS sets anappropriate indication of which execution phase theregion is currently operating at. A transaction cannotstart if the region is not executing in a phase definedby the transaction’s definition.

System action: The transaction is not started.

User response: Check that the set of execution phasesdefined for a transaction is suitable for the executionphase that the region is in when the transaction isstarted. The TXSeries Infocenter provides guidance onresource definition attributes and how to modifyexisting definitions.

Destination:

console.msg

ERZ045006W User identity ’userId’ is not defined inthis Region. PUBLIC access granted

Explanation: User identity ’userId’, supplied whenCICS scheduled a Transaction Security Level (TSL)check, is not defined in the User Definitions for theregion. In the case where this message is issued due toa shipped or routed transaction, if the link is definedwith RemoteSysSecurity=local and there is noLinkUserId, then tasks run as the default userid, butthe security is determined by the TSLKeyMask andRSLKeyMask attributes in the CommunicationsDefinitions, and not related to the DefaultUserId keys.

System action: CICS generates a warning message toindicate a possible security problem and grants publicaccess.

User response: A User Definitions entry for this useridentifier can be created if more specific access controlsare required. The TXSeries Infocenter providesguidance on resource definition attributes and how tomodify existing definitions.

Destination:

CSMT

ERZ045002W • ERZ045006W


ERZ045011E U4511: External Security Manager couldnot be loaded

Explanation: CICS did not load the External SecurityManager correctly.


User response:

Suitable actions include checking that:

v the Region Definitions identify the location andname of the ESM module correctly

v the identified directory and file exist

v the directory and file permissions for the module fileare correct

v the ESM module has been compiled and linkedcorrectly

Destination:

console.msg

ERZ045012E U4512: External Security Manager (ESM)initialization error, return codereturnCode

Explanation: CICS loaded the ESM module, butreturned error returnCode when running the ESM entryfunction.


User response: Check error code returnCode in thesource and documentation for the ESM to identify thenature of this problem.

Destination:

console.msg

ERZ045013E External Security Manager (ESM)Resource Security Level (RSL) checkunsuccessful

Explanation: The ESM callback function, used toperform resource security checking returned an errorcode.

System action: CICS abnormally terminates theapplication server.

User response: Check the source and documentationfor the ESM to identify the nature of this problem.

Destination:

console.msg

ERZ045014E External Security Manager (ESM)Transaction Security Level (TSL) checkunsuccessful

Explanation: The ESM callback function, used toperform transaction security checking, returned anerror code.

System action: CICS abnormally terminates theapplication server.

User response: Check the source and documentationfor the ESM to identify the nature of this problem.

Destination:

console.msg

ERZ045016E CICS was unable to authenticate user’userId’ at terminal ’termId’

Explanation: User ’userId’ operating from principalfacility ’termId’ attempted to sign on to the region.

System action: The sign on attempt does not succeed.CICS logs the error and prevents the user fromaccessing the region as user identity ’userId’.

User response: Check with user ’userId’ (if he or sheexists) about this sign on attempt as there was possiblyan attempt to breach the security of the region bysomeone masquerading as user ’userId’.

Destination:

console.msg

ERZ045077I Validating transaction security levels

Explanation: CICS is starting a check forinconsistencies in the RD and TD databases.


User response: None

Destination:

console.msg

ERZ045078I Finished validating transaction securitylevels

Explanation: CICS has finished checking forinconsistencies in the RD and TD databases.


User response: None

Destination:

console.msg

ERZ045011E • ERZ045078I


ERZ045079W User Definition ’userId’ has same nameas region. Internal security for this userwill allow only TSL/RSL public access.

Explanation: The User Definition ’userId’ has beendefined with a key which is the same as the name ofthe CICS region. This can have unpredictable resultsand is not advised. The user is allowed access only toresources with public RSL/TSL keys.

System action: The RSLKeyList and TSLKeyListattributes for that user are changed to public.

User response: Consider changing the key for thatUser Definition.

Destination:

console.msg

ERZ045080W Transaction ’transId’ will use internalsecurity for resources whose type ismarked internal in the RD database

Explanation: There is a conflict of security parametersin the Region Definitions (RD) and TransactionDefinitions (TD) for the region. Transaction ’transId’ isconfigured in the Transaction Definitions to useexternal security. One or more of the Region Definitionattributes FileRSLCheck, TransientDataRSLCheck,TemporaryStorageRSLCheck, JournalRSLCheck,ProgramRSLCheck or TransactionRSLCheck specifythat external security is not to be used.

System action: CICS uses internal security as requiredby the Region Definitions even though external securityhas been selected in the TD database.

User response: Consider whether the regionconfiguration is correct.

Destination:

console.msg

ERZ045081W Transaction ’transId’ will use internalsecurity for transaction ’transId’

Explanation: There is a conflict of security parametersin the Region Definitions (RD). CICS uses internalsecurity checking when RSLCheck or TSLCheck isexternal, but ESMLoad=no in the RD database.


User response: None

Destination:

console.msg

ERZ045082E CICS has run out of storage

Explanation: CICS has failed to allocate storage andcannot continue.

System action: The region abnormally terminates.

User response: Check the values of theMaxRegionPool, MaxTaskPrivatePool andMaxTSHPool region database attributes. Increase thesevalues and try again.

Destination:

console.msg

ERZ045083E The principal ’principalName’ that wasspecified for user ’userName’ is too long.This user is ignored.

Explanation: The principal that was specified on thePrincipal attribute of a user definition is too long. CICSexpands the principal to a global name starting /.../.This fully qualified principal must be no longer than256 bytes.

System action: If this message is produced duringinitialization, this user is ignored. It is not recognizedby CICS. If this message is produced while adding auser by using cicsadd, then the addition fails.

User response: Shorten the user’s principal to a validlength and try again.

Destination:

console.msg

ERZ045084E The principal ’principalName’ that wasspecified for user ’userName’ isincorrectly specified. This user isignored.

Explanation: The principal that was specified on thePrincipal attribute of a user definition is bad. Principalsthat start with a / must begin with either /.:/ for thelocal cell or /.../ for a global name.


User response: Correct the user’s principal and tryagain.

Destination:

console.msg

ERZ045085E The principal ’principalName’ that wasspecified for user ’userName’ is alsospecified for user ’userName’. This user’userName’ is ignored.

Explanation: The user that is being added has the

ERZ045079W • ERZ045085E


same principal as another user already defined to CICS.All users must have different principals.


User response: Create a new principal for this userand try again.

Destination:

console.msg

ERZ045109I CICS has added the principal’principalName’ with its account. The keytable file ’fileName’ has also been added.

Explanation: cicssetupclients has added the principal,account and key table file it needs for the CICSterminal.

System action: cicssetupclients continues processing.

User response: None. This message is output forinformation only.

Destination:

stderr

ERZ045113E CICS could not change the groupownership of the key table file ’fileName’to cicsterm

Explanation: cicssetupclients attempted to change thegroup ownership of the named file to the groupcicsterm, but failed.

System action: cicssetupclients stops immediately.

User response: Use the message output by chgrp tocorrect the problem and try again.

Destination:

stderr

ERZ045117W User identity for the LinkUserId ’userId’is not defined in this Region. PUBLICaccess granted for the link.

Explanation: User identity for the LinkUserId ’userId’,supplied when CICS scheduled a Transaction SecurityLevel (TSL) check, is not defined in the UserDefinitions for the region. This can be valid, forexample, due to a shipped or routed transaction.

System action: CICS generates a warning message toindicate a possible security problem and grants publicaccess for the link.

User response: The LinkUserId is specified on theremote system’s Communications Definitions. A UserDefinitions entry for this user identifier can be createdif more specific access controls are required for the link.

The TXSeries Infocenter provides guidance on resourcedefinition attributes and how to modify existingdefinitions. If you wish the RSLKeyMask andTSLKeyMask to be used to determine the link securityinstead of the LinkUserId, set LinkUserId=″″ in theCommunications Definitions for the remote system.

Destination:

console.msg

ERZ045120W The database entry for the default CICSuser ’userId’ is being deleted

Explanation: A request was made to delete the user’userId’ from the CICS runtime database. This user isdefined as being the default user for this region. Anyclient requests received by the scheduler that do notcome from a user who has an entry in the CICSRuntime Database are rejected.

System action: The delete of the user from thedatabase continues.

User response: If client requests are made from usersthat have no matching entry in the CICS RuntimeDatabase, add an entry for the CICS Default user backinto the Database.

Destination:

console.msg

ERZ045121E Error trying to change user’s password

Explanation: You have tried to change your password,but there was an error with a call.

System action: The attempt to change password isabnormally terminated. Your password is not changed.

User response: Check that you have supplied thecorrect current password for the user. Check also thatthe new password is valid and that you are authorizedto change the password.

Destination:

console.msg

ERZ045133E Unable to update /etc/inittab

Explanation: cicssetupclients made a call to mkitab toupdate /etc/inittab in order to cause $CICS/etc/rc.cicsto be run at system restart. This call failed. The entry isnecessary to ensure that the 3270 terminal subsystemused by cicsterm is initialized.

System action: cicssetupclients exits without updating/etc/inittab.

User response: Correct any problems indicated bymkitab. Then run cicssetupclients again using the -moption. Alternatively run $CICS/etc/rc.cics each timethat the machine is restarted.

Destination:

ERZ045109I • ERZ045133E


stderr

ERZ045134E Unable to change user’s CICS password

Explanation: The user has tried to change his or herCICS password using the CESN transaction but CICSwas unable to change the password stored in itsdatabase.

System action: The attempt to change the password isabnormally terminated. The password is not changed.

User response: Check that the file system holding theregion’s definitions is not full. Then retry the operation.

Destination:

console.msg

ERZ045135E New password is not a valid CICSpassword

Explanation: The user has tried to change his or herCICS password using the CESN transaction but CICSwas unable to encrypt the supplied password.

System action: The attempt to change the password isabnormally terminated. The password is not changed.

User response: Check that the new password is notlonger than 8 characters. Then retry the operation.

Destination:

console.msg

ERZ045136E Attempt to change CICS password leftdatabase inconsistent

Explanation: The user has tried to change their CICSpassword using the CESN transaction but CICSencountered difficulties in updating its database. Thepermanent database entry for the user in the region’sUser Definitions (UD) and the corresponding warmstart database entry were possibly altered to contain thenew password, but this change has not been made forthe active system.

System action: The attempt to change the password isabnormally terminated. The password is not changednow but can possibly be changed when the region isrestarted either with a warm or a cold start.

User response: Check that the file system holding theregion’s definitions is not full. Then retry the operation.If the operation again fails it is possibly necessary toreset the password by using cicsupdate before theregion is next restarted.

Destination:

console.msg

ERZ045138I CICS has added the entry ’rccics’ to theinittab

Explanation: An entry has been added to the inittabto load the kernal extensions for CICS 3270 Supportand CICS IPC on system restart.


User response: None

Destination:

stderr

ERZ045140E U4540: External Authentication Managercould not be loaded

Explanation: CICS did not load the ExternalAuthentication Manager correctly or CICS was unableto find EAM Module in the specified path.


User response: Suitable actions include checking that:The Region Definitions identify the location and nameof the EAM module correctly The identified directoryand file exist The directory and file permissions for themodule file are correct The EAM module has beencompiled and linked correctly

Destination:

ERZ046001E Invalid command line option’optionName’

Explanation: You entered the specified option’optionName’. This option is invalid.

System action: The command abnormally terminateswith a non-zero error status. It also generates aninformation message that gives the syntax of thecommand being run.


Destination:

stderr

ERZ046002E Unable to access region ’regionName’

Explanation: The region name ’regionName’ that youentered cannot be accessed. Either the region namespecified is invalid or the region does not exist.


User response: Check that the region name is correct.If it is, check that the region directory has appropriatepermissions. You must have read, write, and executepermissions on the region directory.

Destination:

ERZ045134E • ERZ046002E


stderr

ERZ046003E You must specify the class option -cclassName

Explanation: You did not specify the mandatory -cclassName option, where className is the name of aresource class.


User response: Retry the command, specifying -cclassName.

Destination:

stderr

ERZ046004E No such resource class

Explanation: The class name you entered is not thename of a valid resource class.


User response: Retry the command with the name ofa valid resource class.

Destination:

stderr

ERZ046005E Entry ’entryName’ not found forpermanent database class ’className’

Explanation: The command cannot find the requiredentry in the permanent database. You are probablyproviding an incorrect key value or invalid region.


User response: Check whether the resource exists. Ifnot, retry the command with correct parameters.

Destination:

stderr

ERZ046006E Entry ’entryName’ not found for databaseclass ’className’

Explanation: The command cannot find the requiredentry in the database. You are probably providing anincorrect key value or invalid region.


User response: Check whether the resource exists. Ifnot, retry the command with correct parameters.

Destination:

stderr

ERZ046007E Invalid password supplied forCICSPassword attribute

Explanation: An invalid password for theCICSPassword attribute was supplied to cicsadd,cicsupdate, cicsupdateclass or cicsmigrateclass.Passwords must not contain more than 8 characters.


User response: Retry the command supplying a validpassword.

Destination:

stderr

ERZ046008E Cannot un-install entry ’entryName’

Explanation: The cicsdelete command cannotuninstall the entry ’entryName’ as it has not beeninstalled or is marked as in use.

System action: The command, cicsdelete with the -Ror -B option, abnormally terminates with a non-zeroerror status.

User response: Check that you specified the entryname correctly. If not, retry the command with thecorrect entry name. Check for related messages in theregion error log and console.

Destination:

stderr

ERZ046009E You cannot add an entry to class’className’

Explanation: You are not allowed to use cicsadd toadd entries of class monitor and region.


User response: Do not try this again.

Destination:

stderr

ERZ046010E You cannot delete entry of class’className’

Explanation: You are not allowed to delete entries ofclass monitor and region.



Destination:

stderr

ERZ046003E • ERZ046010E


ERZ046011E You must specify either the -a or -goption

Explanation: The -a or -g option is required for thecommand.


User response: Retry the command with the correctoption.

Destination:

stderr

ERZ046012E Invalid Resource Definition Online(RDO) program name ’programName’

Explanation: The ’programName’ that you have enteredis linked to the RDO programs.


User response: Enter correct program name. Theprogram link was presumably created on site. If this isnot the case, contact your support organization.

Destination:

stderr

ERZ046013E Unable to obtain the default entry forpermanent database class ’className’

Explanation: The command was unable to retrieve thedefault entry for the class specified. Either thecommand was unable to read the permanent stanza file(check for more detailed messages output by thecommand), or the default entry does not exist. Thepresence of a default entry is mandatory for this class,and so permanent database operations for this classcannot be performed.


User response: Check the permanent database forinconsistency; repair, or restore from a backup.

Destination:

stderr

ERZ046014E You cannot set up a startup image entryfor class ’className’

Explanation: You are only allowed to usecicssetuprunimage to setup run images for entries ofclass region, SFS and PPC Gateway server.



Destination:

stderr

ERZ046015E Addition, deletion or renaming of thedefault entry is not permitted

Explanation: A default database entry has a key thatis a string of zero length. Such a key is usuallyexpressed by two adjacent quotation marks. Forexample the command cicsget -r regionName -c fd ″″retrieves the default entry for the File Definitions. Thedefault database entries are created when the regiondatabase is created and cannot subsequently be deletedor added.



Destination:

stderr

ERZ046016E The ’className’ record may not beactivated

Explanation: The region or monitor permanentdatabase entry cannot be installed using ResourceDefinition Online (RDO).



Destination:

stderr

ERZ046017E The -f option is mandatory with a classof scd

Explanation: The -f option is required for thecommand when the class is Structured File Server (SFS)Schema Files (scd).


User response: Retry the command with the correctoption.

Destination:

stderr

ERZ046018E The -’optionName’ option is invalid witha class of ’className’

Explanation: The named option must not be specifiedwith this particular class.


User response: Retry the command with the correctoptions.

ERZ046011E • ERZ046018E


Destination:

stderr

ERZ046019E The -’optionName’ option requires amandatory argument

Explanation: The named option was specified withoutthe required option argument.


User response: Retry the command with the correctoption argument.

Destination:

stderr

ERZ046020E Could not access SFS Schema file’pathName’; error errorNumber

Explanation: A cicsadd command for the class scd(Structured File Server schemas) was issued with aschema file path that was unable to be accessed. Theoperating system error is given.


User response: Look up the ’errorNumber’ given inoperating system documentation to find out why theschema file was unable to be accessed. When theproblem is resolved, retry the command.

Destination:

stderr

ERZ046021E Unsuccessful renaming of ’oldEntryName’to ’newEntryName’, old entry cannot bedeleted

Explanation: The renaming of a permanent databaseentry was unsuccessful because the old entry wasunable to be removed.

System action: The new entry is created and the oldentry still exists. The command abnormally terminateswith a non-zero error status.

User response: Refer to previous messages detailingwhy the old entry was unable to be deleted. Removethe appropriate old or new entry using ResourceDefinition Online (RDO) as applicable, retrying theoperation if the new one is removed.

Destination:

stderr

ERZ046025E ALL is not defaulted for DISCARD, SETor PERFORM commands

Explanation: You entered an incomplete CEMTDISCARD, CEMT SET or CEMT PERFORM command.

System action: CICS displays the appropriate CEMTpanel.

User response: Enter the correct CEMT DISCARD,CEMT SET or CEMT PERFORM command.

Destination:

Message Panel or Response Area of CEMT Panel.

ERZ046026E Commands other than INQUIRE are notexecuted if they contain errors

Explanation: There is an error in the CEMT commandthat you entered. The error is described byaccompanying messages. The command is notexecuted.

System action: CICS does not execute the CEMTDISCARD, SET or PERFORM command.

User response: Enter the correct CEMT DISCARD,CEMT SET or CEMT PERFORM command.

Destination:


ERZ046027E ’fieldName’ value, ’value’, is invalid andhas been ignored

Explanation: You have entered an invalid value’value’.


User response: Correct your invalid changes.

Destination:


ERZ046028I THERE ARE NO MESSAGES

Explanation: Placed in the Information Area of aCEMT panel when there are no messages.


User response: None

Destination:


ERZ046019E • ERZ046028I



Explanation: The operating system command mkdirwas unsuccessful.


User response: Check whether the directory alreadyexists and that there is enough space in the filesystem.Consult the operating system documentation.

Destination:

stderr

ERZ046031E Unable to create symbolic link’linkName’ for ’fileName’

Explanation: The system command ln wasunsuccessful trying to link ’linkName’ to ’fileName’. Theerror occurred during cicsexport.


User response: Check the file permissions, and thatthere is enough space in the file system. Consult theoperating system documentation.

Destination:

stderr

ERZ046032E Unable to access the CICS internalinventory list

Explanation: The CICS internal inventory list does notexist.


User response: Check that the CICS installation wassuccessful. If the problem persists, contact your supportorganization.

Destination:

stderr

ERZ046033E The CICS internal inventory list hasinconsistent data

Explanation: The contents of CICS internal inventoryare invalid and cannot be used check region archives.



Destination:

stderr

ERZ046036E The -’optionName’ option must bespecified with this command

Explanation: The -’optionName’ option is mandatoryfor this command.


User response: Retry the command, supplying theoption.

Destination:

stderr

ERZ046037I Specified region ’regionName’ alreadyexists

Explanation: The region ’regionName’ exists invarDir/cics_regions. This message is only forinformation. An existing region cannot be overwrittenwithout also supplying the force flag (-F). On WindowsNT you can find the drive letter of the disk containingthe cics_regions directory by using the cicsnameregions command.

System action: None

User response: None

Destination:

stderr

ERZ046038E Unable to read the CICS internalinventory list

Explanation: The CICS internal inventory list is notreadable by the current user.


User response: Check that the CICS installation wassuccessful. If problem persists, contact your supportorganization.

Destination:

stderr

ERZ046039W Linked file ’fileName’ does not exist

Explanation: A symbolic link ’fileName’ cannot beresolved. This does not prevent a region from beingcreated.


User response: The link can be resolved manually ifrequired.

Destination:

stderr

ERZ046029E • ERZ046039W


ERZ046040I Restoring ’fileName’ from back-up

Explanation: The file ’fileName’, which is a symboliclink, is being replaced by a copy of the original file.This message is for information only.


User response: None

Destination:

stderr

ERZ046041W ’linkName’ does not exist - restoring’fileName’ from back-up

Explanation: The symbolic link ’linkName’ cannot beresolved, so it is being replaced by a copy of theoriginal file.


User response: None

Destination:

stderr

ERZ046042W ’fileName’ does not exist - link ’linkName’cannot be resolved

Explanation: The link cannot be resolved.


User response: None

Destination:

stderr

ERZ046043E ’fileName’ does not exist - link ’linkName’cannot be resolved

Explanation: The link cannot be resolved, and theregion is not created.


User response: Resolve links, or run the program inanother mode.

Destination:

stderr

ERZ046044I ’linkName’ is a symbolic link to ’fileName’

Explanation: This message is produced by cicsimportand cicsdefault in verbose mode (-v) to indicate that’linkName’ is a symbolic link to file ’fileName’.


User response: None

Destination:

stderr

ERZ046045I Creating region ’regionName’ fromarchive of default region’defaultRegionName’

Explanation: This message is produced by cicsdefaultto indicate that the region ’regionName’ is being createdfrom an archive of the default region’defaultRegionName’.


User response: None

Destination:

stderr

ERZ046046E Could not locate archive of defaultregion

Explanation: cicsdefault or cicsmigrate cannot findthe archive of the default region.


User response: Check that the CICS installation wassuccessful. Restore from backup if possible.

Destination:

stderr

ERZ046047E Region ’regionName’ is locked -command not allowed

Explanation: cicsdefault or cicsimport was requestedto overwrite an existing region, and the existing regionis locked for execution. cicsdefault and cicsimport donot allow overwriting of a locked region.


User response: Check that the specified region isrunning. If the region is running and you still want torun cicsdefault or cicsimport then shut the regiondown and retry this command. If the region is notrunning then use the cicsrlck command to remove thelock file and retry this command.

Destination:

stderr

ERZ046049E Region ’regionName’ already exists

Explanation: cicsdefault or cicsimport was requestedto create a region that already exists.


User response: Create a different region, or if youwant to overwrite the existing region then retry the

ERZ046040I • ERZ046049E


command with the -F flag. The use of the -F flagdestroys region definitions for the existing region andother related information, so you can possibly lose datathat you wish to keep.

Destination:

stderr

ERZ046050E Cannot find region to export

Explanation: No region name is specified and cannotfind default region.


User response: Specify region name, or restore defaultregion.

Destination:

stderr

ERZ046051E ’fileName’ does not exist in the archive

Explanation: The required file ’fileName’ cannot befound in the region archive.



Destination:

stderr

ERZ046052E Absolute paths not permitted in theregion archive file

Explanation: The region archive file contains absolute(rather than relative) pathnames.


User response: Recreate an appropriate archive.

Destination:

stderr

ERZ046053E Option -’optionName’ has invalidargument ’argumentValue’

Explanation: You are specifying an invalid argument,’argumentValue’, for the command option -’optionName’.


User response: Retry the command specifying validargument.

Destination:

stderr

ERZ046054E Group ’groupName’ is invalid

Explanation: You are specifying a group that is notvalid for your userid.


User response: Specify a valid group, or alter useridpermissions.

Destination:

stderr

ERZ046055E All links in the archive could not beresolved - program abnormallyterminating

Explanation: One or more links cannot be resolved.The region is not created.


User response: Run the program again in a differentmode, or restore files so as to resolve links.

Destination:

stderr

ERZ046056E Command line option -’optionName’re-specified

Explanation: You are specifying option -’optionName’more than once.


User response: Retry the command correctly.

Destination:

stderr

ERZ046057W Class ’className’ specified more thanonce

Explanation: The class ’className’ is specified morethan once on the command line.


User response: None

Destination:

stderr

ERZ046050E • ERZ046057W


ERZ046059E Command line option ’optionName’expects a value

Explanation: It is incorrect to specify the commandline option ’optionName’ without also providing a value.



Destination:

stderr

ERZ046060E Command line option ’optionName’ isinvalid

Explanation: The option ’optionName’ is not a validoption.



Destination:

stderr

ERZ046061E Archive file ’fileName’ does not exist oris not readable

Explanation: The archive file ’fileName’ does not exist,or it cannot be read.


User response: Retry the command specifying a validarchive file, or make specified file available.

Destination:

stderr

ERZ046062E Renaming of resources in the run-timeis not permitted

Explanation: An attempt was made to rename aresource in the run-time. This is valid only within thepermanent database environment via ResourceDefinition Online (RDO) interface.


User response: If renaming of the resource is required,then you can only accomplish this within thepermanent database environment.

Destination:

stderr

ERZ046063E You have insufficient privilege to runthe ’programName’ program

Explanation: You are not running the named ResourceDefinition Online (RDO) program as a user withsufficient privileges.


User response: Login as a user with suitableprivileges before executing this command.

Destination:

stderr

ERZ046065E File ’fileName’ cannot be updated

Explanation: This command updates the keytab file,’fileName’, in order to add the automatically generatedregion server password. The file cannot be updated.


User response: Ensure file exists and is writable, andretry the command. If the problem persists contact yoursupport organization.

Destination:

stderr

ERZ046069I Subsystem definition for region’regionName’ already exists

Explanation: The subsystem definition for region’regionName’ already exists, and no attempt is made tocreate it. This message is for information only.


User response: None

Destination:

stderr

ERZ046073E Unable to update the keytab file withthe region ’regionName’ password

Explanation: The keytab file cannot be updated withthe region ’regionName’ password.


User response: Further error messages identify theproblem. Ensure that the name server is running, andthat you have write permission to the file.

Destination:

stderr

ERZ046059E • ERZ046073E


ERZ046080E Force flag must be specified

Explanation: An existing region cannot be overwrittenunless the -F option is specified.


User response: Enter again with the -F option, orspecify a different region.

Destination:

stderr





Destination:

stderr

ERZ046083E Unable to delete entity from the registry,return code is returnCode

Explanation: cicsdestroy was unable to delete anentity from the CDS registry whilst attempting todestroy a region. The entity that was unable to bedeleted is either the region principal, the region accountor the region password entry in the keytab file.

System action: The command terminates, returningthe value 1.

User response: Further messages identify the problem.Check the cicsdestroy trace file for further information.Ensure that the CDS server is running, and that youhave sufficient authority to delete the entity. Performthe deletion by hand.

Destination:

stderr

ERZ046087W Unable to access region definitions (RD)

Explanation: cicsdestroy was unable to access theregion definitions (RD). The cicsdestroy command usesthe region definitions (RD) to determine the SFS andLOG data to be destroyed, so this file must be availablein order to destroy the region-owned SFS and LOGdata.

System action: The command continues, but thedeletion of any region-owned SFS and LOG data is notperformed.

User response: Check if any region-owned SFS and

LOG data exists. If data does exist, perform thedeletion by hand.

Destination:

stderr

ERZ046089E Unable to delete file ’fileName’ on SFSserver ’serverName’, return code isreturnCode

Explanation: cicsdestroy was unable to delete thenamed SFS file on the named SFS while attempting todestroy a region.


User response: Further messages identify the problem.Check the cicsdestroy trace file for further information.Ensure that the SFS is running, that the file exists, andthat you have sufficient authority to delete the file.Perform the deletion by hand.

Destination:

stderr

ERZ046090I Usage: cicsdefault -r regionName {-?| [-ggroupName] [-v] [-F]}

Explanation: This is the usage message for thecicsdefault command.


User response: If the command was specifiedincorrectly then retry with valid parameters. You mustbe logged in as root on UNIX or as a user withAdministrator and cicsgroup authority on WindowsNT. See the TXSeries Infocenter for more information.

Destination:

stderr

ERZ046091I Usage: cicsadd {-?|-c className [-rregionName] [-P|-B] [-f fileName] [-mmodelId] resourceName[[attributeName=attributeValue]...]}

Explanation: This is the usage message for the cicsaddcommand.


User response: If the command was specifiedincorrectly then retry with valid parameters. See theTXSeries Infocenter for more information.

Destination:

stderr

ERZ046080E • ERZ046091I


ERZ046092I Usage: cicsdelete {-?|-c className [-rregionName] [-P|-R|-B] [-f fileName]resourceName [resourceName...]}

Explanation: This is the usage message for thecicsdelete command.



Destination:

stderr

ERZ046093I Usage: cicsget {-?|-c className [-rregionName] [-f fileName] {-l|-s[resourceName]|[resourceName]}}

Explanation: This is the usage message for the cicsgetcommand.



Destination:

stderr

ERZ046094I Usage: cicsinstall {-?|[-v] [-rregionName] {-a | -g groupName[groupName...] }}

Explanation: This is the usage message for thecicsinstall command.


User response: Retry the command, if appropriate. Seethe TXSeries Infocenter for more information.

Destination:

stderr

ERZ046095I Usage: cicsdestroy {-?| -r regionName[-I] [-s [-u userId[/passWd]]]}

Explanation: This is the usage message for thecicsdestroy command.



Destination:

stderr

ERZ046096I Usage: cicsupdate {-?|-c className [-rregionName] [-P|-R|-B] [-f fileName][resourceName][[attributeName=attributeValue]...]}

Explanation: This is the usage message for thecicsupdate command.



Destination:

stderr

ERZ046097I Permanent database request for’resourceName’ succeeded, thoughrun-time request was unsuccessful

Explanation: This message indicates that only yourpermanent database operation succeeded. Yourequested that the operation be performed on both thepermanent and the run-time database, but the run-timedatabase operation was unsuccessful.

System action: None

User response: Other messages indicate why therun-time request was unsuccessful. Retry the commandwhen appropriate.

Destination:

stderr

ERZ046098I Usage: cicsexport {-?| [-r regionName][-o outFile] [-t temporaryWorkspace] [-lclassName...]}

Explanation: This is the usage message for thecicsexport command.

System action: Command terminates.

User response: If the command was specifiedincorrectly then retry with valid parameters. It ispossible that you have specified an option of zerolength. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ046099I Usage: cicsimport {-?| -r regionName [-ggroupName] [-i inFile] [-l m|o] [-v] [-F][-o] [-B]}

Explanation: This is the usage message for thecicsimport command.

System action: The command exits with a non zeroreturn code.

ERZ046092I • ERZ046099I


User response: If command is specified incorrectlythen retry with valid parameters. Check that you havenot given zero length strings as input. You must belogged in as root on UNIX or as a user withAdministrator and cicsgroup authority on WindowsNT. See the TXSeries Infocenter for more information.

Destination:

stderr

ERZ046101I Usage: cicssetuprunimage -c className[-r regionName] [-a] [-e] [-s]resourceName[[attributeName=attributeValue]...]

Explanation: This is the usage message for thecicssetuprunimage command.

System action: Program exits.

User response: If the command was specifiedincorrectly then retry with valid parameters.

Destination:

stderr

ERZ046104E Cannot find TRPC path name for region’regionName’

Explanation: The command being run was unable toobtain the TRPC path of the region.


User response: Run the command again specifying thecorrect region name using the -r option. Alternatively,ensure that the default region is set to the correctregion, if the region can be defaulted, and run thecommand again. Also, ensure that the region directoryis accessible.

Destination:

stderr

ERZ046105E Cannot find region directory for region’regionName’

Explanation: The command being run was unable toobtain the path of the region directory.


User response: Run the command again specifying thecorrect region name using the -r option. Alternatively,ensure that the default region is set to the correctregion, if the region can be defaulted, and run thecommand again. If the command being run is notcicsimport, ensure also that the region directory isaccessible.

Destination:

stderr

ERZ046106E Do not have permission to destroyregion ’regionName’

Explanation: cicsdestroy cannot access the regiondirectory.


User response: Ensure that you have access to theregion being destroyed and then repeat the command.

Destination:

stderr

ERZ046107I Operation failed with message’errorMessage’

Explanation: An operation failed with the message’errorMessage’. Following messages give further detailsof the problem.

System action: See following messages.

User response: See following messages.

Destination:

stderr

ERZ046108W Cannot find SFS file ’fileName’

Explanation: While trying to delete SFS files, thecicsdestroy command was unable to find the namedfile. This is usually because the region’s SFS files werenot created on the SFS, or because the SFS files werealready deleted from the server.

System action: cicsdestroy continues trying to deletethe other SFS files.

User response: None

Destination:

stderr

ERZ046110E Unsuccessful attempt to add entry’resourceName’ to permanent databaseclass ’className’

Explanation: Your attempt to add the entryresourceName to the permanent database class classNamewas unsuccessful.

System action: The command terminates with anon-zero error status.

User response: As indicated by the previousmessage(s) detailing why the add request wasunsuccessful.

Destination:

stderr

ERZ046101I • ERZ046110E


ERZ046111E Unsuccessful attempt to update entry’resourceName’ in permanent databaseclass ’className’

Explanation: Your attempt to update the entryresourceName in the permanent database class classNamewas unsuccessful.


User response: As indicated by the previousmessage(s) detailing why the update request wasunsuccessful.

Destination:

stderr

ERZ046112E Unsuccessful attempt to delete entry’resourceName’ from permanent databaseclass ’className’

Explanation: Your attempt to delete the entryresourceName in the permanent database class classNamewas unsuccessful.


User response: As indicated by the previousmessage(s) detailing why the delete request wasunsuccessful.

Destination:

stderr

ERZ046113E Your attempt to add ’resourceName’ isincomplete

Explanation: Your attempt to add ’resourceName’ isincomplete because of an unsuccessful attempt to add itto the CICS permanent or runtime database. Theaddition of ’resourceName’ involves further operationsas well as adding it to the CICS database. Thesesubsequent operations were not performed.


User response: You possibly partially added’resourceName’ to CICS. Either correct the errorindicated by previous message(s) and retry theoperation specifying the -I flag to ignore errors ordelete ’resourceName’ and start again.

Destination:

stderr

ERZ046114I Run-time database request for’resourceName’ succeeded, thoughpermanent request was unsuccessful

Explanation: This message indicates that only yourrun-time database operation succeeded. You requestedthat the operation be performed on both the permanentand the run-time database, but the permanent databaseoperation was unsuccessful.

System action: None

User response: Other messages indicate why thepermanent request was unsuccessful. Retry thecommand when appropriate.

Destination:

stderr

ERZ046115E Region ’regionName’ is still running

Explanation: cicsdestroy was unable to destroy theregion regionName because it was unable to obtain theregion lock. This means that either the region wasrunning, another process was performing regionconfiguration, or the region lock file was not removedwhen the region terminated.

System action: cicsdestroy exits

User response: Repeat the command after a fewminutes and check that no other process is performingregion configuration. Examine the value in the″region_lock″ file in the region directory. If the region isstill running the file contains the processid of the maincics process. If the region is still running, shut it downbefore attempting to remove it. If there is no processrunning, remove the lock file using the cicsrlckcommand and retry the cicsdestroy command.

Destination:

stderr

ERZ046117I Deleting Structured File Server (SFS)data for the region ’regionName’

Explanation: This message is produced by cicsdestroyto indicate that the Structured File Server (SFS) data forthe region ’regionName’ is being deleted from the SFSsused by the region ’regionName’.


User response: None

Destination:

stderr

ERZ046111E • ERZ046117I


ERZ046119I Deleting subsystem definition for theregion ’regionName’

Explanation: This message is produced by cicsdestroyto indicate that the subsystem definition for the region’regionName’ is being deleted.


User response: None

Destination:

stderr

ERZ046120I Deleting files and directories for theregion ’regionName’

Explanation: This informational message is producedby cicsdestroy to indicate that the directoryvarDir/cics_regions/regionName is being deleted. OnWindows NT you can find the drive letter of the diskcontaining the cics_regions directory by using thecicsname regions command.


User response: None

Destination:

stderr

ERZ046121E Unable to remove the directory structurefor region ’regionName’

Explanation: This error message is produced bycicsdestroy and is issued when the command to deletethe region file structure under varDir/cics_regionsfailed. The command possibly partly completed, and itis possibly necessary to remove any remaining files byhand.

System action: The cicsdestroy command exitsabnormally.

User response: Remove any remaining files undervarDir/cics_regions/’regionName’. On Windows NT youcan find the drive letter of the disk containing thecics_regions directory by using the cicsname regionscommand.

Destination:

stderr

ERZ046122E Unable to remove the region entry from’CDSprofile’, return code is ’returnCode’

Explanation: cicsdestroy was unable to remove theentry for the region from the specified CDS profile.

System action: The command continues, but theregion entry possibly remains in the specified CDSprofile.

User response: Check the cicsdestroy trace file for

further information. Ensure that the CDS name serveris running, and that you have sufficient authority toaccess the profile. Perform the deletion by hand.

Destination:

stderr

ERZ046123E Region name ’regionName’ is reserved byCICS

Explanation: The region name ’regionName’ that youentered is reserved by CICS.


User response: Choose another name for your region.

Destination:

stderr

ERZ046124E ’regionName’ rejected - CICS region namemay not contain a ’.’

Explanation: The region name ’regionName’ that youentered contained a period (.). This syntax is illegal forCICS region names.


User response: Choose another name for your regionthat does not contain a ’.’.

Destination:

stderr

ERZ046125W No resources installed for group(s)specified

Explanation: You attempted to install a resource groupor groups into the CICS runtime database but noresources were installed. Either no resources werefound in the permanent database for the groupsspecified or the resources found were unable to beinstalled. Failure to install a resource can possibly becaused by the resource already existing in the runtimedatabase or by incorrect data in the resource definition.

System action: The command terminates normally.

User response: Check for other messages from thecicsinstall command. If no other messages were issuedthis indicates that no resources were found for thegroups specified. If you were expecting resources to befound check the spelling of the group names specifiedon the command with those specified in the permanentdatabase. If other messages were issued check theirexplanations and look for further information on theCICS console.

Destination:

stderr

ERZ046119I • ERZ046125W


ERZ046126W No resources installed which specify’ActivateOnStartup=yes’

Explanation: You attempted to install all resourcesthat have the ’ActivateOnStartup’ flag set into theRuntime database but no resources were installed.Either no resources were found in the permanentdatabase with this flag set or none of the resourcesfound were able to be installed. Failure to install aresource can possibly be caused by the resource alreadyexisting in the runtime database or by incorrect data inthe resource definition.

System action: The command terminates normally.

User response: Check for other messages from thecicsinstall command. If no other messages were issuedthis indicates that no resources were found with the’ActivateOnStartup’ flag set. If other messages wereissued check their explanations and look for furtherinformation on the CICS console.

Destination:

stderr

ERZ046127E File operation failed while readingstanza file

Explanation: While attempting to read a stanza file anundefined I/O error occurred.

System action: The command terminates abnormally.Any changes made to the stanza file are backed outduring the next database operation on the stanza file.

User response: Check that the filesystem on which thestanza file resides is not full and retry the command. Ifthe problem persists check for warning messages in thesystem error log and console.

Destination:

stderr

ERZ046128E File operation failed while writing tostanza file

Explanation: While attempting to write to a stanza filean undefined I/O error occurred.



Destination:

stderr

ERZ046129E Memory get request for ’byteCount’ bytesfailed

Explanation: The current program executed a requestto the operating system to get ’byteCount’ bytes ofmemory. The request failed with not enough memory.

System action: The command terminates abnormally.If changes were being made to a stanza file, they arebacked out during the next database operation on thestanza file.

User response: If the system was heavily loaded, waituntil the load decreases and rerun the command. If theproblem persists check for error messages in the systemerror log and console.

Destination:

stderr

ERZ046130E File operation failed while closingstanza file

Explanation: While attempting to close the stanza filean undefined I/O error occurred.



Destination:

stderr

ERZ046131E Illegal condition detected in CICSinternal function

Explanation: While running a CICS RDO Commandan internal error occurred.


User response: Retry the command. If the problempersists check for warning messages in the system errorlog and console.

Destination:

stderr

ERZ046132E ’-r’ option is not valid when updatingclasses SSD, GSD or SCD

Explanation: You have specified the -r option alongwith a server database class. The region name is not avalid option while updating the SSD, GSD or SCDschemas.


ERZ046126W • ERZ046132E



Destination:

stderr

ERZ046133E ’-r’ option must be specified for class’className’

Explanation: You have not specified a region name.


User response: Retry the command specifying aregion name.

Destination:

stderr

ERZ046134E Unrecognized class ’className’ specified

Explanation: The class you specified for the -c optionis not a valid database class.


User response: Check the syntax of the command andretry the command specifying a valid CICS databaseclass.

Destination:

stderr

ERZ046135E Stanza file for class ’className’ does notcontain attribute ’attributeName’

Explanation: The attribute you specified, using the -boption, does not exist in the stanza file for class’className’.

System action: Processing of the cicsupdateclasscommand terminates abnormally.

User response: Check you have specified the attributeon the -b option correctly, and retry the command.

Destination:

stderr

ERZ046136E Unable to convert option ’option’ tonumerical form

Explanation: While using the -lt, or -gt flags on thecicsupdateclass command you have specified an optionthat cannot be converted to a long integer.


User response: Check the number that you havespecified for the relevant flag and retry the commandspecifying a valid integer.

Destination:

stderr

ERZ046137E Bad value ’attributeValue’ for attribute’attributeName’, in class ’className’, forstanza with key ’resourceName’

Explanation: On the cicsupdateclass command youhave specified to update the value of attribute’attributeName’, if the value is less than (-lt) or greaterthan (-gt) a specified value. While attempting toconvert the value in the stanza file to a long integer anerror occurred.


User response: Check the value of the attributespecified by ’className’, ’attributeName’, ’resourceName’and verify that it is a numerical value.

Destination:

stderr

ERZ046138I Usage: cicsupdateclass {-?|[-rregionName] [-w] -c className -aattributeName [-n newValue | -bfromAttribute] [[-lt | -gt | -eq ]oldValue] [-k resourceName] [-ffileName]}

Explanation: This is the usage message for thecicsupdateclass command.

System action: Program terminates.

User response: If command was specified incorrectlythen retry with valid parameters. See the TXSeriesInfocenter for more information.

Destination:

stderr

ERZ046139I Usage: cicsmigrateclass {-?|[-rregionName] [-w] -c className [-aattributeName {-n newAttribute | -d |-u renameAttribute}] [-f fileName]}

Explanation: This is the usage message for thecicsmigrateclass command.



Destination:

stderr

ERZ046133E • ERZ046139I


ERZ046140I Usage: cicscopystanza {-?|[[-w] -ssourceRegion] -t targetRegion -cclassName -k resourceName}

Explanation: This is the usage message for thecicscopystanza command.



Destination:

stderr

ERZ046141I Usage: cicsmigrate {-?|[ -r regionName |-s | -c | -p | -m ] -g fileName -ologFileName}

Explanation: This is the usage message for thecicsmigrate script.



Destination:

stderr

ERZ046142I No database migration to be done forclass ’className’

Explanation: No updates are needed for the class’className’ to migrate to the present release.


User response: none

Destination:

stderr

ERZ046143I Script output file and log file cannot bethe same file

Explanation: On specifying the cicsmigrate commandyou have specified the same name for both the log fileand the script file.


User response: Retry the command specifying distinctnames for the log file and the script file.

Destination:

stderr

ERZ046144I Unable to write to file ’logFileName’

Explanation: The script was unable to write to the logfile you specified.


User response: Check the permissions on the log fileyou specified and on the parent directory. Retry thecommand with a valid log file.

Destination:

stderr

ERZ046145I Unable to write to file ’scriptFileName’

Explanation: cicsmigrate was unable to write to thescript file you specified.


User response: Check the permissions on the scriptfile you specified and on the parent directory. Retry thecommand with a valid script name.

Destination:

stderr

ERZ046148I No regions to select

Explanation: No regions were found in the CICSregion directory.

System action: The select command returns failure.

User response: If there are regions defined, check thedirectory exists and its access permissions. If thedirectory is a mounted filesystem, ensure that it ismounted correctly.

Destination:

stderr

ERZ046149E Unable to create the archive file’fileName’

Explanation: The cicsexport command attempted tocreate the archive file ’fileName’ but was unable tocreate or write to the file.

System action: The command terminates with a returncode of 1.

User response: Check that the filename specifiedpoints to a valid file. Check that the filesystem onwhich the file resides is not full and, if the file alreadyexists, check that it is not a special file such as adirectory or a device. If the filesystem is remotelymounted from another machine, check that theexported filesystem honors super-user access from thecurrent machine.

Destination:

stderr

ERZ046140I • ERZ046149E


ERZ046150I No resources were found for the class’className’ in region ’regionName’

Explanation: You attempted to generate a list of allresources defined in a region for a particular class. Noresources were found.


User response: Verify the select specified the correctregion and if in error retry the command specifying thecorrect region.

Destination:

stderr

ERZ046151I Usage: cicslist { -? | [-r regionName] -cclassName [-f fileName] [-d]}

Explanation: This is the usage message for the cicslistscript.


User response: If command was specified incorrectly,retry the command with valid parameters.

Destination:

stderr

ERZ046152I No servers defined for class ’class’

Explanation: You attempted to generate a list of allservers defined for a class but none were found.


User response: Check by viewing the server stanzafile that server definitions exist, and check thepermissions on the stanza file.

Destination:

stderr

ERZ046153I No schemas defined in the file ’fileName’

Explanation: You attempted to generate a list of allthe schemas defined in a file but none were found.


User response: Check by viewing the schema file thatdefinitions exist, and check the permissions on theschema file.

Destination:

stderr

ERZ046156E Cannot execute ’programName’

Explanation: The script was unable to execute’programName’.


User response: Check that the program is in adirectory that is specified in your PATH environmentvariable, and that you have permission to execute it.

Destination:

stderr

ERZ046157E Cannot destroy server ’serverName’ -server running

Explanation: The server details cannot be destroyedbecause the lock file for the server exists - this impliesthe server is running.


User response: The server cannot be destroyed if it isrunning, so perform a shutdown first. It is possible thatdue to a previous system fault the server is not runningbut the lock file was left. If this is the case, remove thelock file by using cicsloglock.

Destination:

stderr

ERZ046158W Subsystem definition ’subsystemName’could not be found

Explanation: The subsystem definition’subsystemName’ cannot be found, though the commandrun assumes that it exists.


User response: The definition was supposed to exist,though this does not prevent processing fromcontinuing.

Destination:

stderr

ERZ046159I The subsystem definition for server’serverName’ has been removed

Explanation: The subsystem definition for server’serverName’ was removed.


User response: None

Destination:

stderr

ERZ046161W The restart file ’restartFileName’ couldnot be found

Explanation: The restart file ’restartFileName’, whichcontains the restart string for the server, cannot befound during a destroy operation.

ERZ046150I • ERZ046161W



User response: None. The file was supposed to exist,but does not prevent processing from continuing.

Destination:

stderr

ERZ046163E Could not create list of regions tomigrate

Explanation: The command cicslist was used togenerate a list of CICS regions to be migrated on themachine; this command was unsuccessful. It possiblyindicates that there are no regions defined on themachine.

System action: The command possibly continues tomigrate other resources.

User response: If there are no regions to be migratedfor the machine, no action is required. If there areregions that require migration, examine the migrationlogfile for further information on failure of the cicslistcommand, and retain the logfile for use by yoursupport organization.

Destination:

stderr

ERZ046164E Migration of region ’regionName’ wasunsuccessful

Explanation: The CICS region ’regionName’ was notsuccessfully migrated.


User response: Examine the output for related errormessages to determine the cause of failure.

Destination:

stderr

ERZ046168E Could not create list of SFS servers tomigrate

Explanation: The command cicsget was issued togenerate a list of SFS servers to be migrated for themachine; this command was unsuccessful. It possiblyindicates that there are no SFS servers defined on themachine, or that they were already migrated.


User response: If there are no SFS servers to bemigrated for the machine, no action is required. If thereare SFS servers that require migration, examine themigration logfile for further information on failure ofthe cicsget command, and retain the logfile for use byyour support organization.

Destination:

stderr

ERZ046169E Migration of SFS server ’serverName’ wasunsuccessful

Explanation: The command was unable to migrate theSFS ’serverName’.


User response: Examine the output for related errormessages to determine the cause of failure.

Destination:

stderr

ERZ046171E No subsystem definition for region’regionName’ on this machine

Explanation: The region ’regionName’ that is beingmigrated does not have a valid subsystem definition.This means that the region is not complete on thismachine and needs to be deleted and properly definedafter migration of the machine is complete. Thispossibly indicates that a previous attempt to delete theregion was incomplete.


User response: Check that the region name is valid. Ifthe region is required, delete it and redefine it whenmigration of the machine is complete.

Destination:

stderr

ERZ046174W Old CDS directories not deleted

Explanation: The command was unable to delete theold CDS directories after creating new ones formigration.


User response: Examine the migration log file forrelated CDS messages. The absence of these directoriesdoes not cause a problem to the migrated system, butthis warning can possibly indicate an error with CDS.

Destination:

stderr

ERZ046181W commandName has successfully deletedthe CDS entities

Explanation: This information message is displayedwhen the deletion of the Cell Directory Services (CDS)directories and objects successfully completes.


User response: None

ERZ046163E • ERZ046181W


Destination:

stderr

ERZ046182I Usage: cicsmigratelevel {-?| [-rregionName] -c className}

Explanation: This is the usage message for thecicsmigratelevel command.

System action: Command exits.

User response: If the command was specifiedincorrectly then retry with valid parameters.

Destination:

stderr

ERZ046183E Cannot create lock file for server’serverName’

Explanation: The lock file used for locking the servercannot be created.


User response: Check that directoriesvarDir/cics_servers/SSD and varDir/cics_servers/GSDare available and that you have permission to createfiles in them. On Windows NT you can find the driveletter of the disk containing the cics_servers directoryby using the cicsname serversdir command. Seeaccompanying operating system error messages forfurther information. Correct the problem and retry thecommand.

Destination:

stderr

ERZ046184E Cannot perform migration - server’serverName’ running

Explanation: The migration cannot be performedbecause the lock file for the server exists - this impliesthe server is running.


User response: Migration cannot take place if theserver is running, so perform a shutdown first. It ispossible that due to a previous system fault the serveris not running but the lock file still exists. If this is thecase, remove the lock file by using cicsloglock.

Destination:

stderr

ERZ046185E Cannot read entry from server databasefor server ’serverName’

Explanation: The server details for entry ’serverName’cannot be retrieved from the server database.Accompanying ERZ034xxx and ERZ082xxx messagesidentify the problem.


User response: Use messages to determine the causeof the problem. Correct the problem, and retry thecommand.

Destination:

stderr

ERZ046186E Unable to access details on user orgroup ’userId’

Explanation: CICS was unable to access details onuser or group userId. This was probably because theuser or group does not exist. Previous messagesidentify the exact problem.


User response: Ensure that user or group userId existsand then rerun the command. If it does not exist thenensure CICS is installed correctly.

Destination:

stderr

ERZ046187E Unsuccessful attempt at changing ownerof files in server directory ’directoryName’for server ’serverName’

Explanation: An attempt at changing the ownership ofa file in the server directory directoryName wasunsuccessful.


User response: Check that the directoriesvarDir/cics_servers/SSD and varDir/cics_servers/GSDare available and that you have permission to createfiles in them. See accompanying operating system errormessages for further information. On Windows NT youcan find the drive letter of the disk containing thecics_servers directory by using the cicsname serversdircommand. Correct the problem and retry the command.

Destination:

stderr

ERZ046188E Cannot perform migration

Explanation: The migration was unable to be carriedout. Accompanying messages identify the problem.


ERZ046182I • ERZ046188E



Destination:

stderr

ERZ046189E Cannot create subsystem definition’subsystemName’ for server ’serverName’

Explanation: It was not possible to create a subsystemdefinition ’subsystemName’ during migration.



Destination:

stderr

ERZ046190W Unable to delete CDS entity ’CDSname’,return code is ’returnCode’

Explanation: cicsdestroy was unable to delete thenamed CDS object or directory.

System action: The command continues, but the CDSobject or directory is not deleted.

User response: Further messages identify the problem.Check the cicsdestroy trace file for further information.Ensure that the CDS name server is running, and thatyou have sufficient authority to delete the entity.Perform the deletion by hand.

Destination:

stderr

ERZ046191W Unable to delete entity from the registry,return code is returnCode

Explanation: cicsdestroy was unable to delete anentity from the CDS registry whilst attempting todestroy a region. The entity that was unable to bedeleted is either the region principal, the region accountor the region password entry in the keytab file.


User response: Further messages identify the problem.Check the cicsdestroy trace file for further information.Ensure that the CDS server is running, and that youhave sufficient authority to delete the entity. Performthe deletion by hand.

Destination:

stderr

ERZ046192W Cannot perform migration



User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem, and retry the command.

Destination:

stderr

ERZ046193E Migration of database for server’serverName’ was unsuccessful


System action: The command terminates, returningthe value 1.

User response: Use accompanying messages todetermine the cause of the problem. Correct theproblem, and retry the command.

Destination:

stderr

ERZ046194E The ’-f’ option must be specified forclass SCD

Explanation: cicsupdateclass, cicsmigrateclass orcicsgetattribute was unable to read or update the SCDstanza as instructed, because you did not specify thefilename of the SCD stanza using the -f option.


User response: Retry the command specifying thefilename of the SCD stanza.

Destination:

stderr

ERZ046195E The ’-f’ option is not valid for class’className’

Explanation: You have specified the -f option alongwith a resource class other than SCD. The -f filenameoption is not a valid option with this class.



Destination:

stderr

ERZ046189E • ERZ046195E


ERZ046196E Region ’regionName’ already exists

Explanation: The cics migration script attempted tocreate a region that already exists. This region name isreserved for use by CICS migration.


User response: If this region was created during aprevious run of the CICS migration script, destroy thisregion directory by using the rm -rf command.Otherwise, if this region name contains specialcharacters that are not allowed in the CICS permanentregion database, either use cicsdestroy to destroy theregion, or cicsexport or cicsimport to rename yourregion. If this fails, then you must remove this regionusing rm -rf, with the appropriate permissions, in orderto proceed with cics migration, and retry running yourcics migration script.

Destination:

stderr

ERZ046198E Unable to access stanza file ’stanzaFile’

Explanation: cicsmigrate with the -c option, attemptedto migrate the default SFS schema, which was notfound.

System action: the cicsmigrate command abnormallyterminates.

User response: As you do not have a default SCDschema file in the default SCD server directory tomigrate, do not run cicsmigrate with the -c option. Ifyou have other SCD schema files that you wish tomigrate, run the cicsmigrateclass command, using the-c scd and -f options.

Destination:

stderr

ERZ046201E Insufficient space to complete the copy.The file system is more than 94 percentfull.

Explanation: The migration script attempted to createa temporary directory into which to copy the defaultstanzas for migration. The creation completedsuccessfully, but the copy failed because the file systemis full and there is not enough space to complete thecopy. The file system needs to be purged.

System action: The command exits with a non-zeroreturn code.

User response: Investigate the cause of the failure.The varDir/cics_regions file system needs to bemaintained and purged.

Destination:

stderr

ERZ046202E The copy of the default stanzas to thetemporary directory failed

Explanation: The migration script attempted to createa temporary directory into which to copy the newstanzas for migration. The creation completedsuccessfully, but the copy failed.


User response: Investigate the cause of the failure. Ifthe varDir/cics_regions file system is full, CICS issupposed to detect it as a separate error, but check itanyway to make sure.

Destination:

stderr

ERZ046203I Usage: cicsmigrategateways {-?| -rregionName [-w]}

Explanation: This is the usage message for thecicsmigrategateways command.


User response: If command was specified incorrectlythen retry with valid parameters.

Destination:

stderr

ERZ046204E Cannot find database subdirectory forregion ’regionName’

Explanation: The command being run was unable toobtain the path of the database subdirectory for theregion.


User response: Run the command again specifying thecorrect region name if using the -r option. Ensure alsothat the database subdirectory is accessible.

Destination:

stderr

ERZ046205E The -l option is no longer a valid optionfor the cicsmigrate command

Explanation: The cicsmigrate command no longeraccepts the -l option. This is because there are nolonger any log servers to migrate for CICS on OpenSystems.


User response: Run the command again specifyinganother command-line option if required.

Destination:

ERZ046196E • ERZ046205E


stderr

ERZ046206E The stanza file ’stanzaFile’ does not exist,or cannot be read, or is not executable

Explanation: CICS was unable to access the stanza fileshown. Information is required from the stanza formigration of a region log or an SFS.

System action: See the message following this one.

User response: See the message following this one.

Destination:

stderr and stdout

ERZ046207E The attribute ’attributeName’ for logserver ’logServer’ could not be obtainedfrom the stanza file ’stanzaFile’

Explanation: The attribute is required so that aclserver can be started in place of the log server formigration. Either the stanza file does not exist, cannotbe read or does not contain the attribute. This ispossibly because the log server definition was deleted.

System action: The log server is not started, and anymigration step that requires the server fails.

User response: If the log server definitions still existand the problem is corrected, the migration steps thathave failed can be run again if required.

Destination:

stderr and stdout

ERZ046208E The userid ’userId’ of server ’serverName’has no home directory

Explanation: The home directory of the serverscontain vital information for their migration. Withoutthis information a server cannot be migrated.

System action: The migration step that requires thedirectory fails.

User response: The failed migration steps cannot berestarted. If this results in the failure to migrate an SFS,the next start of the SFS must be a cold start. If thisresults in the failure to migrate a region logfile, thenext start of the region must be a cold start.

Destination:

stderr and stdout

ERZ046209E Restart file ’restartFileName’ for server’serverName’ does not exist, is empty oris not readable

Explanation: The restart file is required so that aclserver can be started in place of the log server formigration.

System action: The log server is not started and any

migration step that requires the server fails.

User response: If the problem can be corrected, anymigration step that fails can be run again. If theproblem cannot be corrected, the failed migration stepscannot be run again. If this results in the failure tomigrate an SFS server, the next start of the SFS must becold. If this results in the failure to migrate a regionlogfile, the next start of the region must be cold.

Destination:

stderr and stdout

ERZ046210E Subsystem ’subsystemName’ does notexist

Explanation: The subsystem definition is required tostart a clserver, in the place of a log server. It wassupposed to exist for the equivalent log server, but wasdeleted.

System action: CICS is unable to start a clserver isplace of a log server. As a result the stage of migrationthat requires this server to be running is halted.

User response: None. The stage of migration that hasfailed cannot be run again.

Destination:

stderr and stdout

ERZ046211E CICS was unable to change the entry forsubsystem ’subsystemName’

Explanation: CICS was attempting to change thesubsystem entry so that it was able to be used to start aclserver in the place of a log server, but the attemptfailed.


User response: None. The stage of migration that hasfailed cannot be run again.

Destination:

stderr and stdout

ERZ046212I Starting clserver ’serverName’

Explanation: The clserver is being started in place ofthe equivalent log server.

System action: Migration continues.

User response: None

Destination:

stderr and stdout

ERZ046206E • ERZ046212I


ERZ046213E Start of clserver ’serverName’ failed

Explanation: CICS was attempting to start a clserverin the place of a log server, but the clserver failed tostart.


User response: See the previous message for the causeof the error. If the error is corrected, the stage ofmigration that failed as a result of the failure can berun again.

Destination:

stderr and stdout

ERZ046214I Waiting for clserver ’serverName’ toinitialize

Explanation: CICS is waiting for the clserver toinitialize.

System action: When the server has initialized,migration continues.

User response: None

Destination:

stderr and stdout

ERZ046215I Stopping clserver ’serverName’

Explanation: CICS is stopping the clserver as it is nolonger required for the stage of migration being run.


User response: None

Destination:

stderr and stdout

ERZ046216I Clserver ’serverName’ started successfully

Explanation: CICS has successfully started theclserver.


User response: None

Destination:

stderr and stdout

ERZ046217I Dumping logfile for SFS server’serverName’

Explanation: CICS is about to attempt to dump thelogfile of the SFS. This is the first stage of SFSmigration.

System action: The logfile is dumped.

User response: None

Destination:

stderr and stdout

ERZ046218I Logfile for SFS server ’serverName’ hasalready been dumped

Explanation: CICS has detected that this stage ofmigration for this server was successfully completedpreviously.

System action: The migration of this SFS progresses tothe next stage.

User response: None

Destination:

stderr and stdout

ERZ046219E SFS Server ’serverName’ not found instanza file ’stanzaFile’

Explanation: CICS attempted to obtain informationrelating to the server from the stanza file, but thestanza contained no record of the server. The serverdefinition must be deleted from the stanza after thefirst attempt to migrate this server.

System action: Migration of the server is halted.

User response: If the migration of the server isrequired and the problem can be corrected, themigration of the server can be run again.

Destination:

stderr and stdout

ERZ046220E The attribute ’attributeName’ for SFSserver ’serverName’ could not beobtained from the stanza file ’stanzaFile’

Explanation: The attribute is required so that the SFScan be migrated. Either the stanza file does not exist,cannot be read or does not contain the attribute.

System action: Migration of the server is halted.

User response: If the migration of the server isrequired and the problem can be corrected, themigration of the server can be run again.

Destination:

stderr and stdout

ERZ046221E Home directory ’directoryName’ for user’userId’ does not have read, write andexecute permission

Explanation: The userid of an SFS does not have therequired access to its home directory.

System action: Migration of the SFS is halted.

ERZ046213E • ERZ046221E


User response: Give user ’userId’ read, write andexecute permission for directory ’directoryName’ andrun this stage of migration again.

Destination:

stderr and stdout

ERZ046222E CICS cannot start clserver ’serverName’ tomigrate SFS server ’serverName’

Explanation: Migration of the SFS requires theclserver, but the clserver was unable to be started.


User response: Earlier messages indicate the cause ofthe problem. If these problems are corrected, this stageof migration can be run again.

Destination:

stderr and stdout

ERZ046223E Dump of logfile to file ’dumpFile’ forSFS server ’serverName’ failed. See’outFile’.

Explanation: CICS was attempting to dump the logfileof the SFS into ’dumpFile’ during the first stage of SFSmigration, but this failed.

System action: The output of the dump command iswritten to ’outFile’ in the directory,varDir/cics_servers/SSD and migration of the SFS ishalted.

User response: Examine ’outFile’ for the cause of theproblem. If this is corrected, this stage of migration canbe run again.

Destination:

stderr and stdout

ERZ046224I Restoring logfile for SFS server’serverName’

Explanation: CICS is about to attempt to restore thelogfile of the SFS. This is the second and final stage ofSFS migration.

System action: Migration of the SFS continues.

User response: None

Destination:

stderr and stdout

ERZ046225I Logfile for SFS server ’serverName’already restored

Explanation: CICS has detected that this stage ofmigration for the server was previously successfullycompleted. As this is the final stage of migration,migration of the server is complete.


User response: None

Destination:

stderr and stdout

ERZ046226E Dump or restart file for server’serverName’ does not exist

Explanation: CICS requires that these files exist in thehome directory of the server to continue migration ofthe SFS. Either a file was deleted or the server wassuccessfully migrated previously.


User response: If migration of the SFS was not donebefore and is required, the problem can be corrected byrunning SFS migration again.

Destination:

stderr and stdout

ERZ046227E Archive directory ’directoryName’ forserver ’serverName’ could not be created

Explanation: The directory is required for migration ofthe SFS.


User response: If migration of the SFS is required,create the directory and run SFS migration again.

Destination:

stderr and stdout

ERZ046228I Starting volume server to restore logfilefor server ’serverName’

Explanation: A volume server is required for SFSmigration, it is being started.

System action: CICS waits for up to 3 minutes for theserver to initialize.

User response: None

Destination:

stderr and stdout

ERZ046229E CICS is unable to generate a name forthe volume server

Explanation: CICS issued the rpcutil command inorder to generate a name to be used for the volumeserver. This command failed.

System action: Migration of the SFS being migrated ishalted.

User response: See preceding message for details ofthe error. If the error is corrected and migration of the

ERZ046222E • ERZ046229E


SFS is required, run SFS migration again.

Destination:

stderr and stdout

ERZ046230E CICS is unable to start the volumeserver. See ’outFile’.

Explanation: The volume server required to completeSFS migration failed to start.

System action: The output of the volume server iswritten to ’outFile’. Migration of the SFS being migratedis halted.

User response: Examine ’outFile’ for the cause of theproblem. If the error is corrected, and migration of theSFS is required, run SFS server migration again.

Destination:

stderr and stdout

ERZ046231E An error occurred in mapping logicalvolume ’volumeName’. See ’outFile’.

Explanation: CICS received an error when attemptingto map the logical volume of the SFS being migrated.

System action: The output of the command issued iswritten to ’outFile’. Migration of the SFS being migratedis halted.

User response: Examine ’outFile’ for the cause of theproblem. If the error is corrected, and migration of theSFS is required, run SFS migration again.

Destination:

stderr and stdout

ERZ046232E Log Server ’serverName’ not found instanza file ’stanzaFile’

Explanation: CICS was attempting to obtaininformation relating to the log server from the stanzafile. However, the definition of the server ’serverName’does not exist in the stanza file.

System action: CICS is unable to start a clserver isplace of the log server. As a result the stage ofmigration that requires this server to be running ishalted.

User response: If the server no longer exists, the stageof migration that has failed cannot be run again.However, if the log server is defined on anothermachine, the clserver must be started on the remotemachine. SFS migration can then be run again.

Destination:

stderr and stdout

ERZ046233E An error occurred while restoring thelogfile for server ’serverName’. See’outFile’.

Explanation: CICS failed to complete the second andfinal stage of SFS migration. This stage restores thelogfile of the SFS, from the dump file created duringthe first stage of SFS migration, back into the logvolume.

System action: The output of the restore command iswritten to ’outFile’ in the directory,varDir/cics_servers/SSD, and migration of the SFS ishalted.

User response: Examine ’outFile’ for the cause of theproblem. If the error is corrected and migration of theSFS is required, run SFS migration again.

Destination:

stderr and stdout

ERZ046234I Logfile successfully restored for server’serverName’

Explanation: The logfile of the SFS was successfullyrestored to the log volume.

System action: Migration of the SFS completes.

User response: None

Destination:

stderr and stdout

ERZ046235I Converting log data for CICS region’regionName’

Explanation: CICS is about to convert the log data forregion ’regionName’ to the format used with the latestlevel of the CICS product.


User response: None

Destination:

stderr and stdout

ERZ046236E The attribute ’attributeName’ for region’regionName’ could not be obtained fromthe stanza file ’stanzaFile’

Explanation: The attribute is required for migration ofthe region log data, but it was unable to be read fromthe stanza file.

System action: Migration of the region log data ishalted.

User response: If migration of the log data is requiredand the problem can be corrected, migration of theregion can be restarted.

Destination:

ERZ046230E • ERZ046236E


stderr and stdout

ERZ046237E CICS cannot start clserver ’serverName’ tomigrate region ’regionName’

Explanation: Migration of the region log data requiresthe clserver, but the clserver was unable to be started.


User response: Earlier messages indicate the cause ofthe problem. If these problems are corrected, this stageof migration can be run again.

Destination:

stderr and stdout

ERZ046238I Starting logfile conversion stage 1 forregion ’regionName’

Explanation: CICS is starting the first of 2 stagesrequired to migrate the region log data.


User response: None

Destination:

stderr and stdout

ERZ046239I Starting logfile conversion stage 2 forregion ’regionName’

Explanation: CICS is starting the second and last stagerequired to migrate the region log data.


User response: None

Destination:

stderr and stdout

ERZ046240I Logfile for region ’regionName’successfully converted

Explanation: CICS has successfully migrated the logdata for region ’regionName’.


User response: None

Destination:

stderr and stdout

ERZ046241E Logfile conversion stage 2 for region’regionName’ failed, reason: ’errorMessage’

Explanation: The second stage of region log datamigration, for region ’regionName’, failed for the reasonshown in ’errorMessage’.


User response: If migration of the log data is requiredand the problem can be corrected, migration of theregion can be run again.

Destination:

stderr and stdout

ERZ046242E Logfile conversion stage 1 for region’regionName’ failed, reason: ’errorMessage’

Explanation: The first stage of region log datamigration, for region ’regionName’, failed for the reasonshown in ’errorMessage’.


User response: If migration of the log data is requiredand the problem can be corrected, migration of theregion can be run again.

Destination:

stderr and stdout

ERZ046243I No SFS servers to migrate

Explanation: A request was made to migrate SFSservers. However, no record of any previously startedservers can be found.

System action: Migration proceeds to the next stage.

User response: If this is unexpected, earlier messagesshow the cause of the problem. If the problem can becorrected, SFS server migration can be run again.

Destination:

stderr and stdout

ERZ046244I Starting migration of SFS server’serverName’

Explanation: CICS is about to start the migration ofthe SFS ’serverName’.


User response: None

Destination:

stderr and stdout

ERZ046245E Migration of SFS server ’serverName’failed

Explanation: CICS failed to migrate server’serverName’.

System action: Migration of the server halted.Migration proceeds to the next stage.

ERZ046237E • ERZ046245E


User response: Refer to previous messages for thecause of the problem.

Destination:

stderr and stdout

ERZ046246I Migration of SFS server ’serverName’successfully completed

Explanation: CICS successfully migrated SFS’serverName’.

System action: Migration proceeds to the next stage ofmigration.

User response: Once migration is complete, the SFScan be warm started.

Destination:

stderr and stdout

ERZ046247I Dump of logfile data for SFS server’serverName’ successful

Explanation: CICS has successfully dumped the logfiledata of the SFS ’serverName’. This is the first of twostages required to migrate the log data of the SFS.

System action: Migration of the SFS continues to stage2.

User response: None

Destination:

stderr and stdout

ERZ046248W Restart files exist, the logfile for server’serverName’ has previously beendumped

Explanation: CICS has detected that the homedirectory of the server already contains the files restartand restart.bak. This indicates that the SFS was alreadymigrated, independently of the CICS migrationprocedure.

System action: The migration of this SFS is halted andmust not be run again.

User response: None

Destination:

stderr and stdout

ERZ046249I Generating the migration script. Thismay take several minutes

Explanation: The cicsmigrate command is creating themigration script and adding migration commands intothis script. If you have many regions and servers, thisprocess takes several minutes to complete. Expect thisto take at least 5 to 10 minutes, although this estimatedepends on machine size and usage.


User response: None

Destination:

stderr

ERZ046250W ’fileName’ does not exist in the archive



User response: Check that the CICS installation wassuccessful. If you were running the cicsimportcommand, prior to migrating your regions for a newlevel of CICS, then ensure that the cicsmigrate updatesyour region to add the missing file. If the problempersists, contact your support organization.

Destination:

stderr

ERZ046251I Usage: cicsgetattribute {-?|[-rregionName] -c className -kresourceName [-a attributeName] [-ffileName]}

Explanation: This is the usage message for thecicsgetattribute command.


User response: If command was specified incorrectly,retry the command with valid parameters.

Destination:

stderr

ERZ046252E Unable to retrieve value of attribute’attribute’

Explanation: The command attempted to get the valueof the attribute ’attribute’ from the stanza file for thespecified resource and class but was unable to find thedefinition.


User response: If command or the attribute wasspecified incorrectly, retry the command with validparameters.

Destination:

stderr


Explanation: CICS was unable to execute’programName’. Either the program is not in a directoryspecified in the PATH environment variable or the userrunning the migration does not have permission toexecute it.

ERZ046246I • ERZ046253E


System action: CICS is unable to start a clserver inplace of the log server. As a result the stage ofmigration that requires this server to be running ishalted.

User response: Check the paths in the environmentvariable PATH. Ensure that $CICS/bin appearssomewhere in this path. Correct the problem and runagain the stage of migration that failed.

Destination:

stderr and stdout

ERZ046254E clserver ’serverName’ failed to initialize

Explanation: CICS attempted to start the clserver’serverName’, but the server failed to initialize correctly.This server is required for migration.

System action: The failed clserver is stopped and thestage of migration that requires this server to berunning is halted.

User response: See previous message for possiblecauses of the error. If none are obvious, it was possiblycaused by CICS stopping the server. If the error iscorrected, the stage of migration that failed as a resultof the failure can be run again.

Destination:

stderr and stdout

ERZ046255I The keytab file for region ’regionName’may be corrupted. Check before runningthe region.

Explanation: The rgy_edit ktlist command on thekeytab file for region ’regionName’ was unable to findor access the keytab file. This indicates possiblecorruption of the keytab file. It can also be caused bywrong permissions on the file.


User response: Ensure that the name server isrunning, and that you have write permission to the file.Run rgy_edit domain account ktlist -fkeytabFileName.

Destination:

stderr

ERZ046256I Invalid database key for database classclassName

Explanation: The database entry key is invalid for theCICS database class className.


User response: If the error is in a permanent databaseentry edit the stanza entry identified by subsequentmessages and correct the key. If necessary, recover the

permanent database stanza from a backup. If the erroroccurred when entering an Resource Definition Online(RDO) operation, correct the input and reenter thecommand.

Destination:

stderr

ERZ046272E Unable to delete table ’tableName’ onDB2 server ’aliasName’, return code isreturnCode

Explanation: cicsdestroy was unable to delete thenamed DB2 table on the named DB2 server whileattempting to destroy a region.


User response: Further messages identify the problem.Check the cicsdestroy trace file for further information.Ensure that DB2 is running, that the table exists, andthat you have sufficient authority to delete the table.Perform the deletion by hand.

Destination:

stderr

ERZ046273I Deleting DATABASE/2 (DB2) data forthe region ’regionName’

Explanation: This message is produced by cicsdestroyto indicate that DATABASE/2 (DB2) data for the region’regionName’ is being deleted from the DB2 server usedby the region ’regionName’.


User response: None

Destination:

stderr

ERZ046274I File System used by region ’regionName’cannot be identified

Explanation: cicsdestroy was unable to identify thetype of file system used by the region ’regionName’,possibly because the region directory was alreadyremoved.


User response: Remove unwanted files using cicsadministration commands such as cicssdt for SFS.

Destination:

stderr

ERZ046254E • ERZ046274I


ERZ046278E DATABASE/2 (DB2) data cannot bedeleted for region ’regionName’

Explanation: DATABASE/2 (DB2) is unusable on thissystem. Either the DB2 processes are missing orcorrupt, or the ’db2’ command cannot be found.

System action: The command continues destroyingthe region. The DATABASE/2 (DB2) region data is stillpresent.

User response: Check that DATABASE/2 (DB2) isrunning correctly, and that the necessary DB2 paths arein your PATH environment variable.

Destination:

stderr




User response: If the system was heavily loaded, waituntil the load decreases and run the command again. Ifthe problem persists check for error messages in thesystem error log and console.

Destination:

stderr

ERZ046280E Unexpected option ’option’ specified oncommand line.

Explanation: The option identified in the message wasincorrectly specified on the command line to theexecuting program. The program does not accept thisoption as a parameter.


User response: Consult the usage message producedby the program and respecify the options correctly.

Destination:

stderr

ERZ046281E Unexpected argument ’arguments’specified on command line.

Explanation: The argument identified in the messagewas incorrectly specified on the command line to theexecuting program. The program does not accept thisargument as a parameter.


User response: Consult the usage message producedby the program and respecify the arguments correctly.

Destination:

stderr

ERZ046282E Option -option has already beenspecified.

Explanation: The option identified in the message wasspecified twice in the command line to the executingprogram.


User response: Remove the extra options specifiedand attempt to reexecute the command.

Destination:

stderr

ERZ046283E Option -option must have a matchingargument.

Explanation: The option identified in the messagerequires a matching argument.


User response: Respecify the command specifying theargument required by the command. If an argumentwas specified but begins with a ’-’ it was possiblyinterpreted as an option; in this case, use a double ’-’ toensure it is treated as an argument.

Destination:

stderr

ERZ046284E The option -option must be specified.

Explanation: The option identified in the messagemust be specified.


User response: Respecify the command specifying themissing option with any appropriate arguments.

Destination:

stderr

ERZ046285E At least one of the following optionsmust be specified ’optionList’.

Explanation: At least one of the options from theabove list must be specified.


User response: Respecify the command specifying therequired option with any appropriate arguments.

Destination:

stderr

ERZ046278E • ERZ046285E


ERZ046286E At least optionNumb of the followingoptions must be specified ’optionList’

Explanation: At least optionNumb of the options fromthe above list must be specified.


User response: Respecify the command specifying therequired options with any appropriate arguments.

Destination:

stderr

ERZ046287E Only one of the following options maybe specified ’optionList’

Explanation: Only one of the options from the abovelist can be specified.


User response: Respecify the command specifyingonly one on the options from the above list.

Destination:

stderr

ERZ046288E A maximum of optionNumb options maybe specified from ’optionList’

Explanation: A maximum of optionNumb options canbe specified from the above list.


User response: Respecify the command specifyingonly the required options with any appropriatearguments.

Destination:

stderr


Explanation: The command you entered encountereda problem while obtaining information about the CICSsystem installed on your machine.

System action: The command terminates with anon-zero status.

User response: Ensure that you have installed CICScorrectly.

Destination:

stderr

ERZ046290E ’commandName’ was unable to open file’fileName’, errno ’errorNumber.’

Explanation: ’commandName’ was unable to open thespecified file for the reason given.


User response: Ensure that you have installed CICScorrectly. Check the value of errno for moreinformation on the problem.

Destination:

stderr

ERZ046291E Unable to access directory ’directory’,errno ’errorNumber.’

Explanation: The command you entered attempted toalter permissions on directory ’directory’ but was unableto do so.


User response: Check the directory permissions, alsothe value of errno for more information on theproblem.

Destination:

stderr

ERZ046292E Unable to get the current directory,errno ’errorNumber.’

Explanation: The command you entered tried to findout which directory you are in but was unable to do so.


User response: Check that you have installed CICScorrectly. Check the value of errno for moreinformation on the problem.

Destination:

stderr

ERZ046295I Successfully deleted exsisting principal’principal’

Explanation: The command detected that a principalalready existed for CICS. To ensure that all informationis recreated successfully, the existing principal wassuccessfully deleted. This principal is recreated in thenext stage of the operation.


User response: This message is for information only.

Destination:

stderr

ERZ046286E • ERZ046295I


ERZ046296W Unable to get details for security group’cicsterm’

Explanation: The command attempted to retrievedetails for the security group ’cicsterm’, but the inquirefailed.


User response: The group ’cicsterm’ is normallycreated during product installation and configuration.The lack of the group can mean that some part ofconfiguration is incomplete. The command continues,but youare responsible for setting the protectioncontrols on the keytab file that is created.

Destination:

stderr




User response: The group ’cicsterm’ is normallycreated during product installation and configuration.The lack of the group can mean that some part ofconfiguration is incomplete. If you have deliberatelydeleted this security group then rerun this commandwith ’Ignore Errors’ options to bypass this error. If youdo this, then you are responsible for setting the securityon the keytab file.

Destination:

stderr

ERZ046298W Unable to modify the group ownershipfor the file ’fileName’

Explanation: The command attempted to modify thegroup ownership for the file identified in the messagebut the attempt failed.

System action: The command continues, but thegroup ownership of the file is unchanged and canpossibly need to be modified to enable clients access tothe file.

User response: Investigate the cause of the error andmanually change the group owner of the file to be thegroup ’cicsterm’.

Destination:

stderr

ERZ046299E Unable to modify the group ownershipfor the file ’fileName’



User response: Investigate the cause of the errror andcorrect it. If you wish to set the group owner of the filemanually then rerun the command specifying the’IgnoreErrors’ flag and then set the file ownership byhand.

Destination:

stderr

ERZ046302E Problem using region ’regionName’

Explanation: CICS encountered a problem accessingdetails about region ’regionName’.

System action: The command terminates with anabnormal return code.

User response: Ensure that the region exists and isproperly configured. If it does, ensure that you haveinstalled CICS correctly.

Destination:

stderr

ERZ046309W Unable to change the ownership of file’fileName’ for region ’regionName’ to’userId’:’groupId’

Explanation: Unsuccessful attempt to change theownership of file ’fileName’ in region ’regionName’. Thisis possibly because the region file system directory ismounted from another machine. It is also possiblybecause the userid or groupid of the original owner ofthe file does not exist on this machine.

System action: The command continues creating theregion. The region is possibly unusable until youmanually change the ownership of this file or directory.

User response: Change the ownership of the file to’userId’:’groupId’. Use the operating system commandchown.

Destination:

stderr

ERZ046321E Unable to get information on file ordirectory ’directoryName’

Explanation: The command you entered tried toobtain information on the specified directory but wasunable to do so.

System action: The command abnormally terminates.

ERZ046296W • ERZ046321E


User response: Check the directory exists and isreadable.

Destination:

stderr

ERZ046322E Could not find stanza definition forregion ’regionName’

Explanation: The command you entered tried toretrieve information from the CICS system just createdbut was unable to do so.

System action: The command abnormally terminates.The directory structure for the CICS system is created,but the CICS subsystem is not.

User response: Check that the input file for the CICSsystem you are trying to create is not corrupt. Checkthat the directory structure for the region you aretrying to import was created correctly and, morespecifically, that the RD.stanza file is intact. Run thecommand again using the -F (force) option.

Destination:

stderr

ERZ046323E Could not modify stanza definition forserver ’regionName’

Explanation: The command you entered tried to alterthe region stanza definitions in line with the ’-S’ or ’-D’option you gave it, but was unable to do so.

System action: The command abnormally terminates.The directory structure for the CICS system is created,but the CICS subsystem is not.

User response: Check that the input file for the CICSsystem you are trying to create is not corrupt. Checkthat the directory structure for the region you aretrying to import was created correctly and, morespecifically, that the RD.stanza file is intact. Run thecommand again using the -F’ (force) option.

Destination:

stderr

ERZ046326E Error opening temporary file ’fileName’,error number ’errorNumber’

Explanation: cicsimport tried to open a working filebut was unable to do so.


User response: Check that you have sufficientpermissions to write to the regions directory and thatthere is enough space in the file system. Refer to theerror number for more information.

Destination:

stderr

ERZ046327E Unable to write to temporary file’fileName’, error number ’errorNumber’

Explanation: cicsimport tried to write to a workingfile but was unable to do so.


User response: Check that you have sufficientpermissions to write to the regions directory and thatthere is enough space in the file system. Refer to theerror number for more information.

Destination:

stderr

ERZ046328W Unable to obtain details of user number’userNumber’, assuming user ’cics’

Explanation: cicsimport tried to get details on theuser number specified but was unable to do so.

System action: The command continues and assumesthw owning userid is ’cics’

User response: Check that the user exists. Check alsothat you have installed the product according to thedocumentation.

Destination:

stderr

ERZ046329W Unable to obtain details of groupnumber ’groupNumber’, assuming group’cics’

Explanation: cicsimport tried to get details on thegroup number specified but was unable to do so.

System action: The command continues and assumesthw owning group is ’cics’

User response: Check that the group exists. Checkalso that you have installed the product according tothe documentation.

Destination:

stderr

ERZ046330W Error opening temporary file ’fileName’,error number ’errorNumber’

Explanation: cicsimport tried to open a working filebut was unable to do so.

System action: The command continues, but you canpossibly encounter problems later on with ownership.

User response: Check that the import file was createdcorrectly. This error can possibly cause problems lateron if you are importing a file between differentmachines.

Destination:

ERZ046322E • ERZ046330W


stderr





Destination:

stderr

ERZ046332W Unable to change to directory ’dirName’,errno ’errorNumber’

Explanation: The command you entered tried tochange directory to ’dirName’ but was unable to do so.

System action: The command continues but creates allfiles in the current directory.

User response: Check that you have permission towrite to the directory specified. Check also that there isspace in the file system.

Destination:

stderr

ERZ046335E Option ’-l’ not supported underWindows NT

Explanation: You specified the ’-l’ option of cicsexportor cicsimport but this is not supported under WindowsNT.


User response: Run the command again without the’-l’ option.

Destination:

stderr

ERZ046336W Unable to get machine name

Explanation: cicsdestroy needed the host name ofyour machine in order to determine which SFS files todelete. It was unable to get that information.

System action: The command continues if you havespecified the -I option, but your SFS data is not deleted.

User response: This most likely indicates an operatingsystem error. Check that your machine was set up withthe correct name. You possibly need to alter theDefaultFileServer attribute of your regions definitionsfile to explicitly state the name of your machine.

Destination:

stderr

ERZ046337W Failed to parse attribute ’attribute’,current value ’value’

Explanation: While executing cicsdestroy, thecommand attempted to interpret the expanded valuefor the attribute identified in the message, but thisattempt failed.

System action: The command halts its attempt todelete the region’s SFS files and skips to the next stage.

User response: Verify the value identified in themessage is correct and reissue the command.

Destination:

stderr

ERZ046338I Successfully exported region’regionName’

Explanation: cicsexport successfully made a copy ofthe named region.

System action: The command ends successfully.


Destination:

stderr

ERZ046339I Successfully imported region’regionName’

Explanation: cicsimport successfully created a newregion from the specified archive region.

System action: The command ends successfully.


Destination:

stderr

ERZ046341E Cannot find region ’regionName’ todestroy

Explanation: Your attempt to destroy the namedregion failed because the command was unable to findit.


User response: Ensure you gave the correct regionname.

Destination:

stderr

ERZ046331E • ERZ046341E


ERZ046342W Unable to alter permissions of directory’directoryName’, errno ’errorNumber.’

Explanation: The command you entered tried to alterthe permissions of directory ’directoryName’ but wasunable to do so.


User response: Check that the directory exists andthat you have sufficient priviledge to access it. Use theerror number for more information.

Destination:

stderr

ERZ046343E transactionName unable to open messagefile ’fileName’ for region ’regionName’

Explanation: The LogViewer transactiontransactionName was unable to open the log file for theregion named

System action: The transaction ends abnormally

User response: Check that the message file named inthe message exists, and that you have permission toaccess it

Destination:

Terminal

ERZ046344E transactionName cannot be run on thisterminal

Explanation: The LogViewer transactiontransactionName is not supported on this type ofterminal, and cannot be run


User response: Use a terminal with a TermType valueof 145 (0x91) in the WD definition

Destination:

Terminal

ERZ046345E transactionName failed to completeinitialization successfully

Explanation: The LogViewer transactiontransactionName encountered an error duringinitialization, and cannot continue This error is shownwhen an internal CICS error occurs, and indicates amore serious problem with CICS


User response: Check the error logs for indications ofother CICS errors

Destination:

Terminal

ERZ046346E transactionName unable to re-openmessage file ’fileName’ for region’regionName’

Explanation: The LogViewer transactiontransactionName was unable to reopen the log file forthe region named during the Refresh operation


User response: Check that the message file named inthe message exists, and that you have permission toaccess it

Destination:

Terminal

ERZ046347E transactionName unable initialize regionresources for region ’regionName.’

Explanation: The LogViewer transactiontransactionName was unable to initialize the regionresources it required for the named region. It is likelythat a more serious problem with CICS has alreadyoccurred.


User response: Check the error logs for indications ofother CICS errors

Destination:

Terminal

ERZ046348I Creating region ’regionName’ fromarchive ’archiveName’

Explanation: This message is produced by cicsimportto indicate that the region ’regionName’ is being createdfrom archive file ’archiveName’.


User response: None

Destination:

stderr

ERZ046349I Usage: cicsexport {-?| [-r regionName][-o outFile]}

Explanation: This is the usage message for thecicsexport command.


User response: If the command was specifiedincorrectly then retry with valid parameters. It ispossible that you have specified an option of zerolength. See the TXSeries Infocenter for moreinformation.

Destination:

stderr

ERZ046342W • ERZ046349I


ERZ046350E ’regionName’ rejected - CICS region namemay not contain a ’badCharacter’

Explanation: The region name ’regionName’ that youentered contained a bad character. This syntax is illegalfor CICS region names.


User response: Choose another name for your regionthat does not contain the bad character.

Destination:

stderr

ERZ046351I Deleting Oracle data for the region’regionName’

Explanation: This message is produced by cicsdestroyto indicate that CICS file control data mapped ontoOracle for the region ’regionName’ is being deleted fromthe Oracle server used by the region ’regionName’.


User response: None

Destination:

stderr

ERZ046354E The cicsdestroy command failed tocomplete successfully.

Explanation: cicsdestroy ended with a non zero returncode. Previous error messages indicate the cause offailure.

System action: The cicsdestroy command ends.

User response: Check the User Response given for theprevious error messages. Rerun cicsdestroy using the -Ioption.

Destination:

stderr

ERZ046355E The imported stanzas are not at thecurrent machine migration level.

Explanation: The region’s RD stanza, and the SFSserver’s SSD stanza, if it exists, must be at the currentmachine migration level.


User response: Bring the stanzas up to the machinemigration level and retry.

Destination:

stderr

ERZ046356E Could not access subkeys for’RegistryKey’ (error code: ’ErrorCode’).

Explanation: During migration, the subkeys for the’RegistryKey’ was unable to be accessed in the registry.The ’ErrorCode’ can be used to determine the cause ofthe error.


User response: Note the registry key whose subkeyswere unable to be accessed.

Destination:

stderr

ERZ046357E Could not access values for ’RegistryKey’(error code: ’ErrorCode’).

Explanation: During migration, the values for the key’RegistryKey’ was unable to be accessed in the registry.The ’ErrorCode’ can be used to determine the cause ofthe error.


User response: Note the registry key whose valueswere unable to be accessed.

Destination:

stderr

ERZ046358E Could not migrate the key ’RegistryKey’since it already exists.

Explanation: During migration, duplicate keys werefound in the old and new registry entries.

System action: Processing continues. Old keys are leftin the registry.

User response: Note the registry key that was unableto be migrated.

Destination:

stderr

ERZ046359E Could not set value ’RegistryValue’ inkey ’RegistryKey’ (error code: ’ErrorCode’).

Explanation: During migration, the value for the key’RegistryKey’ was unable to be set in the registry. The’ErrorCode’ can be used to determine the cause of theerror.

System action: Processing continues. The particularkey to which this value belongs is deleted in the newregistry entry.

User response: Note the registry key and the valuethat failed.

Destination:

stderr

ERZ046350E • ERZ046359E


ERZ046360E Could not close key: ’RegistryKey’ (errorcode: ’ErrorCode’).

Explanation: During migration, the key ’RegistryKey’was unable to be closed in the registry. The ’ErrorCode’can be used to determine the cause of the error.



Destination:

stderr

ERZ046361E Could not create key: ’RegistryKey’ (errorcode: ’ErrorCode’).

Explanation: During migration, the key ’RegistryKey’was unable to be created in the registry. The ’ErrorCode’can be used to determine the cause of the error.


User response: Note the registry key that was unableto be created.

Destination:

stderr

ERZ046362E Could not open key: ’RegistryKey’ (errorcode: ’ErrorCode’).

Explanation: During migration, the key ’RegistryKey’was unable to be accessed in the registry. The’ErrorCode’ can be used to determine the cause of theerror.


User response: Note the registry key that was unableto be accessed.

Destination:

stderr

ERZ046363E Could not delete key: ’RegistryKey’ (errorcode: ’ErrorCode’).

Explanation: During migration, the key ’RegistryKey’was unable to be deleted from the registry. The’ErrorCode’ can be used to determine the cause of theerror.


User response: Note the registry key that was unableto be deleted.

Destination:

stderr

ERZ046364I Could not open key: ’RegistryKey’. Noneed to migrate information.

Explanation: During migration, the old key’RegistryKey’ was not found. This means that nomigration of registry needs to be done.

System action: Processing stops.


Destination:

stderr

ERZ046365E Error: no 2 regions or SFS servers canhave the same name.

Explanation: During migration, either 2 SFS servers or2 regions with the same name were found i.e. there is asimilar entry in the old as well as the new registry key.

System action: Processing continues. That particularentry is not migrated.

User response: Note the error that occurred.

Destination:

stderr

ERZ046366I Key ’RegistryKey’ already exists.

Explanation: During migration, information isdisplayed about keys that already exist for the new keyin the registry.



Destination:

stderr

ERZ046367I Migrating key ’RegistryKey’...

Explanation: During migration, the keys beingmigrated are displayed.



Destination:

stderr

ERZ046368I Migrating value ’RegistryValue’...

Explanation: During migration, the values of keysbeing migrated are displayed.



Destination:

stderr

ERZ046360E • ERZ046368I


ERZ046369E Registry migration failed.

Explanation: Indicates the migration process failed.


User response: Check previous error messages forfailures. Contact Service giving the full output of themigration command.

Destination:

stderr

ERZ046370E Registry migration partially successful.

Explanation: Some of the keys and their values werenot migrated.


User response: Check previous error messages forfailures. Contact Service giving the full output of themigration command.

Destination:

stderr

ERZ046371I Registry migration successful.

Explanation: Registry migration was successful.

System action: System is in a consistent state.


Destination:

stderr

ERZ046372E Unexpected error occurred.

Explanation: This is possibly an error in the CICScode.


User response: Contact Service.

Destination:

stderr

ERZ046373I Invoke ’cicsmigrate <region_name>’ foreach CICS region.

Explanation: This message provides the syntax forcicsmigrate.cmd.



Destination:

stderr

ERZ046374I Migrating the NT registry.

Explanation: This message indicates the phase ofmigration being performed.



Destination:

stderr

ERZ046375I Migrating CICS resources.




Destination:

stderr

ERZ046376E Error ’ERROR_LEVEL’ getting regiondirectory information.

Explanation: cicsmigrate.cmd was unable to find thelocation of the CICS region directory.

System action: Only items independent of a particularregion are migrated.

User response: Contact service.

Destination:

stderr

ERZ046377E Error ’ERROR_LEVEL’ getting SFSschema directory information.

Explanation: cicsmigrate.cmd was unable to find thelocation of the SFS schema directory.

System action: Migration cannot continue.


Destination:

stderr

ERZ046378E Unrecognised migration level. Migrationcannot continue.

Explanation: cicsmigrate.cmd was unable todetermine the migration level of region being migrated.

System action: Migration cannot continue.


Destination:

stderr

ERZ046369E • ERZ046378E


ERZ046379I Migrating region ’regionName’ frommigration level ’migration_level’.




Destination:

stderr

ERZ046380I Updating the migration version stampin each region stanza entry.


System action: Each stanza entry is updated to thenew migration level.


Destination:

stderr

ERZ046381I Updating the ClassTableSize.


System action: The ClassTableSize is updated.


Destination:

stderr

ERZ046382I Creating a temporary region.


System action: A temporary region is created for useduring migration. It is deleted at the end of themigration process.


Destination:

stderr

ERZ046383I Updating the ’resourceName’ in region’regionName’.

Explanation: Resource ’resourceName’ is beingupdated in region ’regionName’

System action: The definition of ’resourceName’ isupdated in the region being migrated.


Destination:

stderr

ERZ046384E Creating the ’resourceName’ in region’regionName’.

Explanation: Resource ’resourceName’ is being createdin region ’regionName’

System action: The new resource is created in theregion being migrated.


Destination:

stderr

ERZ046385I Deleting the temporary region.


System action: The temporary region, used during themigration, is removed.


Destination:

stderr

ERZ046386E Region ’regionName’ is already atmigration level ’migration_level’.

Explanation: The region specified was found alreadyto be at the target migration level.

System action: The region is not changed.

User response: Run cicsmigrate.cmd if other regionsneed to be migrated.

Destination:

stderr

ERZ046387E No region specified.

Explanation: cicsmigrate.cmd was invoked without aregion name.

System action: Only items independent of a particularregion are migrated.

User response: Run cicsmigrate.cmd again, butspecify the name of a region you wish to migrate.

Destination:

stderr

ERZ046388I Updating the migration version stampin cics_servers stanzas.



ERZ046379I • ERZ046388I



Destination:

stderr

ERZ046389E Invalid link or file ’File’ under theregion ’%2$s’

Explanation: When files under a region is actually alink to nonexisting file, cicsexport had complained withERZ046002E - Unable to access the region<symboliclink=″″>. It was very difficult to spot out theoriginal cause of the problem. Now the new messagesays the there exists a link (File) under the region (RegionName). But the file referred by the link does notexist.″


User response: needs to check where the link pointsto, or whether the file referred by the link exists or not.Either case the link should point to a valid existing fileor it should be a valid file/directory under the region

Destination:

stderr

ERZ047001I CICS is out of Task Private Storage intransaction ’transId’ on terminal ’termId’

Explanation: The Application Server runningtransaction ’transId’ on terminal ’termId’ has exhaustedits pool of task private storage. A GETMAIN call hasfailed to satisfy a storage request.

System action: CICS raises the NOSTG conditionagainst the transaction. A user defined conditionhandler is invoked if one has been defined. If nohandler is defined for the NOSTG or ERROR conditionthen the transaction is terminated abnormally.

User response: Try to reduce the use of GETMAIN intransaction ’transId’.

Destination:

CSMT

ERZ047002I CICS is out of Task Private Storage intransaction ’transId’ executing as abackground task

Explanation: The Application Server runningtransaction ’transId’ has exhausted its pool of taskprivate storage. A GETMAIN call has failed to satisfy astorage request. The transaction was executing as abackground ATI task, or a back-end communicationstransaction (for DTP, function shipping or transactionrouting).

System action: CICS raises the NOSTG conditionagainst the transaction. A user defined conditionhandler is invoked if one has been defined. If nohandler is defined for the NOSTG or ERROR condition

then the transaction is terminated abnormally.

User response: Try to reduce the use of GETMAIN intransaction ’transId’.

Destination:

CSMT

ERZ047003E Transaction ’transId’ on terminal ’termId’,attempted to free storage at addressaddress. This address is not a validstorage address

Explanation: Transaction ’transId’ executed aFREEMAIN call for a storage address which was notacquired by performing a GETMAIN. The invalidstorage address is address. Invalid addresses are storageaddresses which do not point at storage areas allocatedby a GETMAIN call or which have already beenprocessed by another FREEMAIN call.

System action: CICS raises an A47B abend codeagainst the transaction. A user defined abnormaltermination handler is invoked if one has been defined.If no handler is defined then the transaction isterminated abnormally .

User response: Investigate the use of FREEMAIN inthe programs associated with transaction ’transId’.Addresses passed to FREEMAIN must point at storageallocated by a GETMAIN call.

Destination:

CSMT

ERZ047004E Transaction ’transId’ executing as abackground task, attempted to freestorage at address address. This addressis not a valid storage address

Explanation: Transaction ’transId’ executed aFREEMAIN call for a storage address which was notacquired by performing a GETMAIN. The invalidstorage address is address. Invalid addresses are storageaddresses which do not point at storage areas allocatedby a GETMAIN call or which have already beenprocessed by another FREEMAIN call. The transactionwas executing as a background ATI task, or a back-endcommunications transaction (for DTP, function shippingor transaction routing).

System action: CICS raises an A47B abend codeagainst the transaction. A user defined abnormaltermination handler is invoked if one has been defined.If no handler is defined then the transaction isterminated abnormally .

User response: Investigate the use of FREEMAIN inthe programs associated with transaction ’transId’.Addresses passed to FREEMAIN must point at storageallocated by a GETMAIN call.

Destination:

ERZ046389E • ERZ047004E


CSMT

ERZ047005I CICS is no longer out of Task PrivateStorage in transaction ’transId’ onterminal ’termId’

Explanation: The Application Server runningtransaction ’transId’ returned some task private storageto an empty task private storage pool. This can possiblyallow subsequent GETMAIN calls in transaction’transId’ to succeed.

System action: The Application Server continues.

User response: None

Destination:

CSMT

ERZ047006I CICS is no longer out of Task PrivateStorage in transaction ’transId’ executingas a background task

Explanation: The Application Server runningtransaction ’transId’ returned some task private storageto an empty task private storage pool. This can possiblyallow subsequent GETMAIN calls in transaction’transId’ to succeed. The transaction was executing as abackground ATI task, or a back-end communicationstransaction (for DTP, function shipping or transactionrouting).

System action: The Application Server continues.

User response: None

Destination:

CSMT

ERZ047007E CICS has detected a storageinconsistency in transaction ’transId’ onterminal ’termId’. The inconsistency is instorage area address1 at address address2

Explanation: A transaction program has overrun astorage area allocated by a GETMAIN call. The storagearea begins at address address1 and the inconsistencyoccurs at address address2.

System action: CICS raises an A47C abend codeagainst the transaction. A user defined abnormaltermination handler is invoked if one has been defined.If no handler is defined then the transaction isterminated abnormally .

User response: If the definition of transaction ’transId’indicates that a transaction dump is taken use thedump file to investigate the problem. If no dump isproduced change the Transaction Definition to force thetransaction to produce a dump if it is terminatedabnormally. The probable cause is that application codethat copies data from some storage area to theGETMAIN allocated area is copying too much.

Destination:

CSMT

ERZ047008E CICS cannot initialize Task PrivateStorage

Explanation: CICS attempted to initialize Task Privatestorage, but was unsuccessful. This error indicates aproblem in underlying system software.

System action: CICS abnormally terminates theApplication Server.


Destination:

console.msg

ERZ047009E CICS has detected a storageinconsistency in transaction ’transId’executing as a background task. Theinconsistency is in storage area address1at address address2

Explanation: A transaction program has overrun astorage area allocated by a GETMAIN call. The storagearea begins at address address1 and the inconsistencyoccurs at address address2. The transaction wasexecuting as a background ATI task, or a back-endcommunications transaction (for DTP, function shippingor transaction routing).

System action: CICS raises an A47C abend codeagainst the transaction. A user defined abnormaltermination handler is invoked if one has been defined.If no handler is defined then the transaction isterminated abnormally .

User response: If the definition of transaction ’transId’indicates that a transaction dump is taken use thedump file to investigate the problem. If no dump isproduced change the Transaction Definition to force thetransaction to produce a dump if it is terminatedabnormally. The probable cause is that application codethat copies data from some storage area to theGETMAIN allocated area is copying too much.

Destination:

CSMT

ERZ047010E CICS has detected a storageinconsistency in storage area address1 ataddress address2

Explanation: CICS has overrun a storage areaallocated by a GETMAIN call. The storage area beginsat address address1 and the inconsistency occurs ataddress address2.

System action: CICS raises an internal error code. Thiserror can possibly result in an Application Server or theregion being terminated abnormally.

ERZ047005I • ERZ047010E


User response: Use transaction or region dumps toinvestigate this problem. It is possible that userapplication code is writing to a storage area allocatedto CICS internal use. Check the use made of pointers toGETMAIN storage in your application. If the problempersists contact your support organization.

Destination:

console.msg

ERZ047011E CICS raised an unexpected error intransaction ’transId’ on terminal ’termId’

Explanation: CICS was unable to allocate, or release,the control block controlling a GETMAIN request.

System action: CICS raises a NOSTG condition orA47D abend code against the transaction, depending onthe underlying cause. A user defined condition handleror abnormal termination handler is invoked if one hasbeen defined. If no handler is defined then thetransaction is terminated abnormally.

User response: Other messages in CSMT orconsole.msg indicate the underlying cause of thisproblem. If the cause of the problem is storage shortagefor CICS control blocks, retry the transaction. If thecondition persists and affects many transactions, restartthe region with an expanded Region Pool size, byadjusting the value for the MaxRegionPool attribute inthe Region Definition or by using CICS start upparameters. If other messages indicate that the problemis a software error in CICS, contact your supportorganization.

Destination:

CSMT

ERZ047012E CICS raised an unexpected error intransaction ’transId’ executing as abackground task

Explanation: CICS was unable to allocate, or release,the control block controlling a GETMAIN request. Thetransaction was executing as a background ATI task, ora back-end communications transaction (for DTP,function shipping or transaction routing).

System action: CICS raises a NOSTG condition orA47D abend code against the transaction, depending onthe underlying cause. A user defined condition handleror abnormal termination handler is invoked if one hasbeen defined. If no handler is defined then thetransaction is terminated abnormally.

User response: Other messages in CSMT orconsole.msg indicate the underlying cause of thisproblem. If the cause of the problem is storage shortagefor CICS control blocks, retry the transaction. If thecondition persists and affects many transactions, restartthe region with an expanded Region Pool size, byadjusting the value for the MaxRegionPool attribute inthe Region Definition or by using CICS start up

parameters. If other messages indicate that the problemis a software error in CICS, contact your supportorganization.

Destination:

CSMT

ERZ047013E CICS raised an unexpected storage error

Explanation: CICS was unable to allocate, or release,the control block controlling a task private storage areaused internally by CICS.

System action: CICS abnormally terminates theApplication Server or CICS control process which isaffected. If a CICS control process is affected CICSabnormally terminates the region.

User response: Other messages in console.msgindicate the underlying cause of this problem. If thecause of the problem is storage shortage for CICScontrol blocks then some transactions possibly did notstart. Retry transactions. If the condition persists restartthe region with an expanded Region Pool size, byadjusting the value for the MaxRegionPool attribute inthe Region Definition or by using CICS start upparameters. If other messages indicate that the problemis a software error in CICS, contact your supportorganization.

Destination:

console.msg

ERZ047014W CICS has detected a storageinconsistency in transaction ’transId’ onterminal ’termId’. The inconsistency is instorage area address1 at address address2


System action: None

User response: The probable cause is that applicationcode that copies data from some storage area to theGETMAIN allocated area is copying too much.

Destination:

CSMT

ERZ047015W CICS has detected a storageinconsistency in transaction ’transId’executing as a background task. Theinconsistency is in storage area address1at address address2

Explanation: A transaction program has overrun astorage area allocated by a GETMAIN call. The storagearea begins at address address1 and the inconsistencyoccurs at address address2. The transaction was

ERZ047011E • ERZ047015W


executing as a background ATI task, or as a back-endcommunications transaction (for DTP, function shippingor transaction routing).

System action: None

User response: The probable cause is that applicationcode that copies data from some storage area to theGETMAIN allocated area is copying too much.

Destination:

CSMT

ERZ047016W CICS has detected a storageinconsistency in storage area address1 ataddress address2


System action: None

User response: It is possible that user application codeis writing to a storage area allocated to CICS internaluse. Check the use made of pointers to GETMAINstorage in your application.

Destination:

CSMT

ERZ047019W CICS cannot update theGETMAIN/FREEMAIN abend statisticfor transaction ’transId’

Explanation: CICS was unable to increment thenumber of storage abends statistic field in a transactionrecord.

System action: The CICS Application Servercontinues.

User response: The statistics handling failure is due toan error in CICS; contact your support organization.

Destination:

CSMT

ERZ047020I CICS is out of Task Private Storage

Explanation: A CICS Application Server has exhaustedits pool of task private storage while servicing a requestfrom internal CICS software.

System action: CICS abnormally terminates anApplication Server or CICS control process. This errorcan possibly result in CICS abnormally terminating theregion.

User response: This error can cause a transaction orprogram to fail. Retry failed transactions. Check yourtransactions’ use of GETMAIN storage. It is possiblethat certain transactions are allocating areas of storage

that exceed their requirements. It may be possible toreduce a transaction’s use of task private storage. If thecondition persists, contact your support organization.

Destination:

console.msg

ERZ047021E An internal CICS function attempted tofree storage at address address. Thisaddress is not a valid storage address

Explanation: An internal CICS function has attemptedto free task private storage which it never acquired orhas already freed.

System action: CICS raises an error on the callingfunction, which can result in an abend condition beingraised.

User response: This error indicates a problem in CICSsoftware. Contact your support organization.

Destination:

console.msg

ERZ047022I CICS is no longer out of Task PrivateStorage

Explanation: A CICS Application Server has returnedtask private storage to an empty task private storagepool.

System action: The Application Server or CICS controlprocess continues.

User response: None

Destination:

console.msg

ERZ048001I CICS is under stress. CICS is short onTask Shared storage

Explanation: CICS breached the configured taskshared pool storage threshold. CICS is using the lastfew percent of this pool, and CICS is under stress.

System action: CICS can suspend tasks pendingavailability of task shared storage.

User response: Shut down the CICS region andreconfigure the task shared storage pool size(MaxTSHPool) and threshold (TaskShPoolThreshold)attribute values in the Region Definitions or byoverriding the Region Definitions on the CICScommand line.

Destination:

console.msg

ERZ047016W • ERZ048001I


ERZ048002I CICS is under stress. CICS is short onRun Time Support storage

Explanation: CICS breached the configured run timestorage pool threshold. CICS is using the last fewpercent of this pool, and CICS is under stress.

System action: CICS can terminate tasks abnormallyor can terminate the region due to insufficient storagein the region pool.

User response: Shut down the CICS region andreconfigure the run time storage pool size(MaxRegionPool) and threshold(RegionPoolThreshold) attribute values defined in theRegion Definitions or by overriding the RegionDefinitions on the CICS command line.

Destination:

console.msg

ERZ048003E Transaction ’transId’ on terminal ’termId’,attempted to free task shared storage ataddress address. This address is invalid

Explanation: The transaction ’transId’ attempted tofree some task shared storage at the address address.This address is invalid as it is not the beginning of astorage area allocated from the task shared pool.

System action: CICS abnormally terminates theapplication server or CICS control process. If a CICScontrol process is terminated CICS can abnormallyterminate the region. If an abnormal termination israised on an application server a user defined abnormaltermination handler is executed if one is defined.

User response: Check the use of the GETMAINSHARED call and subsequent FREEMAIN calls intransaction ’transId’. If shared storage is acquired byGETMAIN then, when it is released, the storageaddress returned by GETMAIN must be passed toFREEMAIN. Retry failed transactions once they havebeen checked. If the condition persists it possiblyindicate a software problem in CICS. In this instancecontact your support organization.

Destination:

console.msg

ERZ048004E Transaction ’transId’ on terminal ’termId’attempted to free run time supportstorage at address address. This addressis invalid

Explanation: Transaction ’transId’ attempted to freesome run time support storage at address address. Thisaddress is invalid as it is not the beginning of a storagearea allocated from the region pool.

System action: CICS abnormally terminates theapplication server or CICS control process. If a CICScontrol process is terminated CICS can abnormally

terminate the region. If an abnormal termination israised on an application server a user defined abnormaltermination handler is executed if one is defined.

User response: This message indicates a softwareproblem in CICS. Contact your support organization.

Destination:

console.msg

ERZ048005I CICS is no longer short on task sharedstorage

Explanation: CICS has released enough task sharedstorage so that the task shared pool is no longer understress. Suspended tasks now continue.



Destination:

console.msg

ERZ048006I CICS is no longer short on run timesupport storage

Explanation: CICS has released enough storage so thatthe region pool is no longer under stress.


User response: None

Destination:

console.msg

ERZ048007E U4801: CICS self-consistency checkinghas detected an unrecoverable error

Explanation: CICS found inconsistencies in the regionpool control structures. The console.msg log containsone or more messages prior to this one, indicating thenature of the problem.


User response: This message indicates a softwareproblem in CICS. If the Region Definitions SysDumpattribute is set to yes a region dump file is produced.Restart the region (ensuring that the the region isconfigured to take a dump if the problem recurs).Contact your support organization.

Destination:

console.msg

ERZ048002I • ERZ048007E


ERZ048008E U4802: CICS detected an unrecoverableerror freeing region pool storage

Explanation: Either CICS is attempting to free regionpool storage it has already freed, or a severeinconsistency in the region storage managementstructures has occurred. The console.msg log alsocontains one of the messages ERZ4804E, ERZ4836E, orERZ4846E indicating the address that causes the error.


User response: This message indicates a softwareproblem in CICS. If the Region Definitions SysDumpattribute is set to yes a region dump file is produced.Restart the region (ensuring that the the region isconfigured to take a dump if the problem recurs).Contact your support organization.

Destination:

console.msg

ERZ048010E U4803: CICS did not initialize taskshared pool storage

Explanation: CICS storage initialization detected anunrecoverable error during region start-up. Theproblem is possibly due to invalid task shared poolconfiguration parameters in the Region Definition. Thetask shared pool size must be between the systemimposed limits on the minimum and maximum sizes ofshared memory segments. The problem is possibly dueto insufficient memory, or else the system-imposedlimit on the number of shared memory segments waspossibly reached.

System action: CICS abnormally terminates the regionduring start-up.

User response: Check that the values for task sharedpool configuration are correct in the Region Definitions.The TXSeries Infocenter provides guidance on regionattributes. Check also that none of the system’s limitson shared memory segments have been exceeded.Restart the region with new task shared pool values inthe Region Definition or by overriding the RegionDefinition on the CICS command line.

Destination:

console.msg

ERZ048012E U4803: CICS did not initialize regionpool storage.

Explanation: CICS storage initialization detected anunrecoverable error during region start-up. Theproblem is possibly due to invalid region poolconfiguration parameters in the Region Definition. Theregion pool size must be between the system imposedlimits on the minimum and maximum sizes of sharedmemory segments. The problem is possibly due toinsufficient memory, or else the system-imposed limit

on the number of shared memory segments waspossibly reached.

System action: CICS abnormally terminates the regionduring start-up.

User response: Check that the values for region poolconfiguration are correct in the Region Definitions. TheTXSeries Infocenter provides guidance on regionattributes. Check also that none of the system’s limitson shared memory segments have been exceeded.Restart the region with new region pool values in theRegion Definition or by overriding the RegionDefinition on the CICS command line.

Destination:

console.msg

ERZ048013W Transaction ’transId’ on terminal ’termId’made an unauthorized attempt to loador release program ’programName’

Explanation: The transaction ’transId’ is attempting touse the LOAD PROGRAM or RELEASE PROGRAMcall for map or table ’programName’. The transactionuser does not have the correct combination of RSL keysto perform this operation.

System action: The LOAD PROGRAM or RELEASEPROGRAM call is rejected and an error conditionraised. If a user condition handler is defined then CICSpasses control to the handler. If no handler is definedthen CICS terminates the transaction abnormally.

User response: Arrange for the transaction user tohave RSL keys that allow access to ’programName’ if thisis required.

Destination:

console.msg

ERZ048014I Out of CICS region pool storage.

Explanation: CICS cannot allocate any more storagefrom the region pool. CICS is not able to satisfyrequests for control block storage.

System action: CICS can begin to abend tasks duelack of region pool storage. The region can possiblyabnormally terminate.

User response: If this is a persistent condition youneed to reconfigure the values for the region pool inthe Region Definitions. The TXSeries Infocenterprovides guidance on region attributes. Restart theregion with new region pool values in the RegionDefinitions or by overriding the Region Definitions onthe command line using the -a option of the startsrc orcicsstartsrc command.

Destination:

console.msg

ERZ048008E • ERZ048014I


ERZ048015E A48A: Transaction ’transId’ on terminal’termId’ is out of CICS task shared poolstorage

Explanation: CICS suspends transactions in a queue ifno task shared pool storage is available to satisfy arequest. The leading member of the queue is eventuallytimed out waiting for storage. Transaction ’transId’ isthe current head of the wait queue and is abnormallyterminated because it cannot acquire task sharedstorage.


User response: Retry the transaction. If this is apersistent problem affecting many transactions considerreconfiguring the size of the task shared pool. TheTXSeries Infocenter provides guidance on regionattributes. Restart the region with new task shared poolvalues in the Region Definitions or by overriding theRegion Definitions on the command line.

Destination:

console.msg

ERZ048016E A48B: Unexpected failure in CICSstorage control for transaction ’transId’on terminal ’termId’

Explanation: CICS did not successfully allocate or freea control block in the region pool. This indicates asoftware problem in CICS.

System action: CICS raises an abnormal terminationcondition on transaction ’transId’. A user abnormaltermination handler is invoked if defined. If no handleris defined then CICS abnormally terminates thetransaction.


Destination:

console.msg

ERZ048017E CICS self-consistency checking detectedone or more inconsistencies

Explanation: The self-consistency checking has foundone or more inconsistencies in the control blocks anddata areas concerned with the task shared pool. Theconsole.msg log contains one or more messages, priorto this one, indicating the nature of the inconsistencies.

System action: CICS recovers from theseinconsistencies and the region continues. However, theinconsistencies were caused by software overwritingareas in the task shared pool and some transactions canpossibly terminate abnormally.

User response: The other messages logged containaddress information. This information can be used to

analyze system or transaction dumps. Dump analysiscan possibly indicate which transactions or programsare overwriting the task shared pool areas. A possiblecause is a program that uses GETMAIN SHARED toallocate task shared storage. If these programs writedata buffers of a greater size than the area allocated byGETMAIN then other task shared pool allocations canbe overwritten. Other inconsistencies can be caused byusing LOAD PROGRAM to load a BMS map or a tableinto storage and writing into this area if an addresswas returned in the SET option. If the problem persistscontact your support organization.

Destination:

console.msg

ERZ048020E CICS has overwritten the RegionControl Area (RCA) signature

Explanation: CICS has overwritten the region storagemanagement area in the RCA. This management area isthe anchor point for the region pool data blocks thatrecord allocations in the region pool. This error is notrecoverable.

System action: CICS raises an abnormal terminationcode U4801, and abnormally terminates the region. (Seemessage ERZ4807E).

User response: This type of inconsistency indicates asoftware problem in CICS. Produce a system dump andsend it to your support organization.

Destination:

console.msg

ERZ048021E CICS has overwritten the region pooldata block signature at address address

Explanation: CICS has overwritten the region pooldata block at address address. A pool data block recordsthe details of an allocation in the region pool. This erroris not recoverable.



Destination:

console.msg

ERZ048022E CICS has overwritten the region pooldata block terminator signature ataddress address

Explanation: CICS has overwritten the region pooldata block at address address. A pool data block records

ERZ048015E • ERZ048022E


the details of an allocation in the region pool. This erroris not recoverable.



Destination:

console.msg

ERZ048023E CICS has overwritten the region pooldata block chain at address address.

Explanation: CICS has broken the region pool datablock chain at address address stated in the message.This chain records all allocations in the CICS regionpool. This error is not recoverable.



Destination:

console.msg

ERZ048024E A region pool storage area has beenoverwritten by a data overrun at addressaddress (User Area at: userDataAddress,Region Pool Data Block at:dataBlockAddress)

Explanation: A region pool storage area allocated to aCICS internal function has been overwritten by codewriting beyond the end of the allocation. Address’address’ indicates where the inconsistency wasdetected, address ’userDataAddress’ is the start of theallocated storage area and address ’dataBlockAddress’ isthe region pool data block that records the details ofthis allocation. This error is not recoverable.



Destination:

console.msg

ERZ048025E CICS region pool data block chainshorter than expected (Expected:expectedValue, Actual: actualValue).Recovered - expected count set to actualcount

Explanation: The chain of pool data blocks for theregion pool had fewer elements than the master countin the Region Control Area (RCA). This indicates that aregion pool data block chain pointer has beenoverwritten. Effectively some part of the region pool isno longer accessible to CICS storage control. The erroris not severe enough to cause CICS to abnormallyterminate the region but some transactions can possiblystart to fail. The master count is reset to the number ofblocks actually found in the chain.

System action: CICS resets the master count in theRCA and the region continues.

User response: This type of inconsistency indicates asoftware problem in CICS. Contact your supportorganization.

Destination:

console.msg

ERZ048026E CICS has overwritten a task shared pooldata block signature at address address

Explanation: CICS has overwritten the task sharedpool data block at address address. This error is notrecoverable.



Destination:

console.msg

ERZ048027E A task shared pool storage area hasbeen overwritten by a data overrun ataddress address (User Area at:userDataAddress, Task Shared Pool DataBlock at: dataBlockAddress) - recovered

Explanation: A task shared storage area has beenoverwritten by code writing beyond the end of theallocation at address address. The base address of thestorage allocation is at address userDataAddress and thecontrol block managing this area is at addressdataBlockAddress. This error is recoverable. However,some transactions can possibly abnormally terminatedue to this inconsistency.

System action: CICS resets the allocation terminationsignature so that CICS can continue.

ERZ048023E • ERZ048027E


User response: The information in this message can beused to analyze system or transaction dumps. Dumpanalysis can possibly indicate which transactions orprograms are overwriting the task shared pool areas. Apossible cause is a program that uses GETMAINSHARED to allocate task shared storage. If theseprograms write data buffers of a greater size than thearea allocated by GETMAIN then other task sharedpool allocations can be overwritten. Otherinconsistencies can be caused by using LOADPROGRAM to load a BMS map or a table into storageand writing into this area if an address was returned inthe SET option. If the problem persists contact yoursupport organization.

Destination:

console.msg

ERZ048028E CICS task shared pool data block chainshorter than expected (Expected:expectedValue, Actual: actualValue).Recovered - expected count set to actualcount

Explanation: The chain of pool data blocks for thetask shared pool had fewer elements than the mastercount in the Region Control Area (RCA). This indicatesthat a task shared pool data block chain pointer hasbeen overwritten. Effectively some part of the taskshared pool is no longer accessible to CICS storagecontrol. The error is not severe enough to cause CICSto abnormally terminate the region but sometransactions can possibly start to fail. The master countis reset to the number of blocks actually found in thechain.

System action: CICS resets the master count in theRCA and the region continues.


Destination:

console.msg

ERZ048029E CICS has overwritten the LOADPROGRAM data block signature ataddress address

Explanation: CICS has overwritten the managementstructure controlling a LOADed map or table at addressaddress. This error is not recoverable.



Destination:

console.msg

ERZ048030E CICS has overwritten the LOADPROGRAM data block chain in HashBucket bucketAddress, Address address

Explanation: CICS has overwritten or broken theLOAD PROGRAM management data chain in hashbucket bucketAddress at address address. This error is notrecoverable.



Destination:

console.msg

ERZ048031E CICS self-consistency checking foundan inconsistency in BMS map ’mapName’at task shared storage address address,managed by LOAD PROGRAM datablock at address dataBlockAddress.

Explanation: The physical map ’mapName’ has beenoverwritten in some way and cannot be used.

System action: CICS marks the map image asdisabled. CICS continues processing but some currentlyrunning transactions can possibly abnormally terminatedue to this inconsistency. CICS raises a PGMIDERRcondition against any new transactions requesting themap.

User response: Use CEMT SET PROGRAM(...)NEWCOPY ENABLED to force a reload of the image atthe first opportunity. A transaction or system dump canbe used to investigate which transactions or programsare overwriting the task shared storage containing themap. The likely cause is that a program is writing datausing an address returned from a LOADPROGRAM(’mapName’) SET(<pointer>) call. Writingdata to the address returned from this LOADPROGRAM call causes inconsistencies in the map (ortable storage) allocated for ’mapName’.

Destination:

console.msg

ERZ048032E CICS LOAD PROGRAM data blockchain in Hash Bucket address was shorterthan expected (Expected: expectedValue,Actual: actualValue). Recovered -expected count set to actual count

Explanation: A chain of data blocks associated withmaps and tables had fewer elements than the mastercount in the corresponding address hash bucket. This

ERZ048028E • ERZ048032E


indicates that data block chain pointer has beenoverwritten. This effectively means that CICS does nothave full access to all loaded maps or tables in hashbucket address. This inconsistency is not severe enoughto cause CICS to abnormally terminate the region.However, some storage stress in the task shared poolcan possibly occur and consequently some transactionscan possibly be abnormally terminated.

System action: CICS resets the master count in hashbucket address and the region continues.


Destination:

console.msg

ERZ048033E Transaction ’transId’ executing as abackground task, made an invalidattempt to free task shared storage ataddress address

Explanation: Transaction ’transId’ attempted to freetask shared storage at address address. The address isinvalid as it is not at the beginning of a task sharedpool allocation. The transaction was executing as abackground ATI task, or a back-end communicationstransaction (for DTP, function shipping or transactionrouting).

System action: CICS abnormally terminates theapplication server or CICS control process. If a CICScontrol process is terminated CICS can possiblyabnormally terminate the region. If an abnormaltermination is raised on an application server a userdefined abnormal termination handler is executed ifone is defined.

User response: Check the use of the GETMAINSHARED call and subsequent FREEMAIN calls intransaction ’transId’. If shared storage is acquired byGETMAIN then, when it is released, the storageaddress returned by GETMAIN must be passed toFREEMAIN. Retry failed transactions once they havebeen checked. If the condition persists it can possiblyindicate a software problem in CICS. In this instancecontact your support organization.

Destination:

console.msg

ERZ048034E CICS made an attempt to free taskshared storage at address address. Thisaddress is invalid

Explanation: CICS software attempted to free sometask shared storage at address address. The address isinvalid as it is not at the beginning of a task sharedpool allocation.

System action: CICS abnormally terminates the

application server or CICS control process. If a CICScontrol process is terminated CICS can possiblyabnormally terminate the region.

User response: This error indicates a softwareproblem in CICS. Contact your support organization.

Destination:

console.msg

ERZ048035E Transaction ’transId’ executing as abackground task, made an attempt tofree region pool storage at addressaddress. This address is invalid

Explanation: Transaction ’transId’ attempted to freesome region pool storage at address address. Thisaddress is invalid as it is not the beginning of a storagearea allocated from the region pool. The transactionwas executing as a background ATI task, or a back-endcommunications transaction (for DTP, function shippingor transaction routing).

System action: CICS abnormally terminates theapplication server or CICS control process. If a CICScontrol process is terminated CICS can possiblyabnormally terminate the region.


Destination:

console.msg

ERZ048036E CICS made an attempt to free regionpool storage at address address. Thisaddress is invalid

Explanation: CICS software attempted to free someregion pool storage at address address. The address isinvalid as it is not at the beginning of a region poolallocation.

System action: CICS abnormally terminates theapplication server or CICS control process. If a CICScontrol process is terminated CICS can possiblyabnormally terminate the region.


Destination:

console.msg

ERZ048037W Transaction ’transId’ executing as abackground task, made an unauthorizedattempt to load or release program’programName’

Explanation: The transaction ’transId’ is attempting touse the LOAD PROGRAM or RELEASE PROGRAMcall for map or table ’programName’. The transactionuser does not have the correct combination of RSL keys

ERZ048033E • ERZ048037W


to perform this operation. The transaction wasexecuting as a background ATI task, or a back-endcommunications transaction (for DTP, function shippingor transaction routing).

System action: The LOAD PROGRAM or RELEASEPROGRAM call is rejected and an error conditionraised. If a user condition handler is defined then CICSpasses control to the handler. If no handler is definedthen CICS abnormally terminates the transaction.

User response: Arrange for the transaction user tohave RSL keys that allow access to ’programName’ if thisis required.

Destination:

console.msg

ERZ048038E A48A: Transaction ’transId’ executing asa background task, is out of CICS taskshared storage.

Explanation: CICS suspends transactions in a queue ifno task shared pool storage is available to satisfy arequest. The leading member of the queue is eventuallytimed out waiting for storage. Transaction ’transId’ isthe current head of the wait queue and is abnormallyterminated because it cannot acquire task sharedstorage. The transaction was executing as a backgroundATI task, or a back-end communications transaction(for DTP, function shipping or transaction routing).


User response: Retry the transaction. If this is apersistent problem affecting many transactions considerreconfiguring the size of the task shared pool. TheTXSeries Infocenter provides guidance on regionattributes. Restart the region with new task shared poolvalues in the Region Definitions or by overriding theRegion Definitions on the CICS command line.

Destination:

console.msg

ERZ048039E A48A: A CICS control process is out ofCICS task shared storage.

Explanation: CICS suspends processes or transactionsin a queue if no task shared pool storage is available tosatisfy a request. The leading member of the queue iseventually timed out waiting for storage. A CICScontrol process is the current head of the wait queueand is abnormally terminated because it cannot acquiretask shared storage.

System action: CICS abnormally terminates theprocess. This can possibly cause CICS to abnormallyterminate the region.

User response: If this is a persistent problem considerreconfiguring the size of the task shared pool. The

TXSeries Infocenter provides guidance on regionattributes. Restart the region with new task shared poolvalues in the Region Definitions or by overriding theRegion Definitions on the CICS command line.

Destination:

console.msg

ERZ048040E A48B: Unexpected failure in CICSstorage control for transaction ’transId’,executing as a background task.

Explanation: CICS did not successfully allocate or freea control block in the region pool. This indicates asoftware problem in CICS. The transaction wasexecuting as a background ATI task, or a back-endcommunications transaction (for DTP, function shippingor transaction routing).

System action: CICS raises an abnormal terminationcondition on transaction ’transId’. A user abnormaltermination handler is invoked if defined. If no handleris defined then CICS abnormally terminates thetransaction.


Destination:

console.msg

ERZ048041E A48B: Unexpected failure in CICSstorage control.

Explanation: CICS did not successfully allocate or freea control block in the region pool. This indicates asoftware problem in CICS.

System action: CICS abnormally terminates thecurrent process and region.


Destination:

console.msg

ERZ048042I Region Pool initialized at address:poolAddress

Explanation: The CICS Region Pool storage area hasbeen successfully initialized. The base address of theRegion Pool is poolAddress.

System action: CICS initializes the Region Pool.

User response: None

Destination:

console.msg

ERZ048038E • ERZ048042I


ERZ048043I Task Shared Pool initialized at address:poolAddress

Explanation: The CICS Task Shared storage area hasbeen successfully initialized. The base address of theTask Shared Pool is poolAddress.

System action: CICS initializes the Task Shared Pool.

User response: None

Destination:

console.msg

ERZ048044I Task Shared Pool is under stress.Purging unused map/table areas.

Explanation: CICS breached the configured taskshared pool storage threshold or received a ″no storagecondition″ from the low level storage manager. CICSattempts to reclaim storage in the Task Shared Pool sothat storage requests can be completed.

System action: CICS removes any unused BMS mapsor application tables from the Task Shared Pool.

User response: This message indicates that the TaskShared Pool is possibly underconfigured for the needsof the region. Shut down the CICS region andreconfigure the task shared storage pool size(MaxTSHPool) and threshold (TaskShPoolThreshold)attribute values in the Region Definitions or byoverriding the Region Definitions on the CICScommand line.

Destination:

console.msg

ERZ048045I Purging of unused map/table areascompleted. purgedCount maps/tablespurged.

Explanation: CICS completed storage reclamation inthe task shared pool and removed purgedCountmaps/tables from the pool.

System action: None

User response: None

Destination:

console.msg

ERZ048046E A region pool storage area has beenoverwritten by a data overrun at addressaddress (User Area at: userDataAddress,Region Pool Data Block at:dataBlockAddress)

Explanation: CICS has detected a storageinconsistency while attempting to reallocate, ordeallocate a region pool storage area allocated to aCICS internal function. CICS has determined that the

storage area has been overwritten by code writingbeyond the end of the allocation. Address ’address’indicates where the inconsistency was detected, address’userDataAddress’ is the start of the allocated storagearea and address ’dataBlockAddress’ is the region pooldata block that records the details of this allocation.

System action: CICS abnormally terminates theapplication server or CICS control process. If a CICScontrol process is terminated CICS can possiblyabnormally terminate the region. If an abnormaltermination is raised on an application server a userdefined abnormal termination handler is executed ifone is defined.


Destination:

console.msg

ERZ048047E A task shared pool storage area hasbeen overwritten by a data overrun ataddress address (User Area at:userDataAddress, Task Shared Pool DataBlock at: dataBlockAddress).

Explanation: CICS has detected a storageinconsistency while attempting to deallocate, orreallocate a task shared storage area. CICS hasdetermined that the storage area has been overwrittenby code writing beyond the end of the allocation ataddress address. The base address of the storageallocation is at address userDataAddress and the controlblock managing this area is at address dataBlockAddress.

System action: CICS continues, but does not releasethe inconsistent storage, so that further analysis of theinconsistency can be performed. Some transactions canpossibly be abnormally terminated as a result of thisinconsistency.

User response: The information in this message can beused to analyze system, SNAP, or transaction dumps.Dump analysis can possibly indicate which transactionsor programs are overwriting the task shared pool areas.A possible cause is a program that uses GETMAINSHARED to allocate task shared storage. If theseprograms write data buffers of a greater size than thearea allocated by GETMAIN then other task sharedpool allocations can be overwritten. Otherinconsistencies can be caused by using LOADPROGRAM to load a BMS map or a table into storageand writing into this area if an address was returned inthe SET option. As this storage cannot be released,there is less storage available to both CICS and yourapplications. This can ultimately result in performancedegradation that can only be rectified by restartingyour CICS region. If the problem persists contact yoursupport organization.

Destination:

ERZ048043I • ERZ048047E


console.msg

ERZ049001E Syntax error ’Tobedetermined’

Explanation: To be determined

System action: To be determined

User response: To be determined

Destination:

stderr

ERZ049002E Invalid process type ’Tobedetermined’




Destination:

stderr

ERZ049003E Invalid debug class ’Tobedetermined’




Destination:

stderr

ERZ049004E Invalid trace level ’Tobedetermined’




Destination:

stderr

ERZ049005E Invalid component ’Tobedetermined’




Destination:

stderr

ERZ049006E Invalid module ’Tobedetermined’




Destination:

stderr

ERZ049007E Operation ’Tobedetermined’ on file’Tobedetermined’ failed with errno’Tobedetermined’




Destination:

stderr

ERZ049008I Dump file ’Tobedetermined’ has beencreated




Destination:

stderr

ERZ049010E A memory allocation request failed




Destination:

stderr

ERZ049011I Trace parameter ’Tobedetermined’ has beenset to ’Tobedetermined’




Destination:

stderr

ERZ049012W The trace event listener thread is exiting




Destination:

stderr

ERZ049001E • ERZ049012W


ERZ049013I Trace event ’Tobedetermined’ has beenreceived




Destination:

stderr

ERZ049014I The dump index is ’Tobedetermined’




Destination:

stderr

ERZ049015E Failed to attach shared memory ID’Tobedetermined’, errno=’Tobedetermined’




Destination:

stderr

ERZ049016I User trace has been turned on




Destination:

stderr

ERZ049017I User trace has been turned off




Destination:

stderr

ERZ049018E You must be the Unix root user or theNT Administrator to run this program




Destination:

stderr

ERZ049019E The command-line syntax is incorrect




Destination:

stderr

ERZ049020E An unexpected internal error hasoccurred




Destination:

stderr

ERZ049021E A CICS region name must be provided




Destination:

stderr

ERZ049022E Failed to establish a connection to CICSregion ’Tobedetermined’




Destination:

stderr

ERZ049023E CICS region ’Tobedetermined’ does notappear to be active




Destination:

stderr

ERZ049013I • ERZ049023E


ERZ049024E An input file name must be provided




Destination:

stderr

ERZ049025E The input file name ’Tobedetermined’ hasan unexpected format




Destination:

stderr

ERZ049026W An incomplete record was detected infile ’Tobedetermined’




Destination:

stderr

ERZ049027E Could not find a trace record in file’Tobedetermined’




Destination:

stderr

ERZ049028E Failed to create a shared memorysegment, errno=’Tobedetermined’




Destination:

stderr

ERZ049029I Trace initialization has begun




Destination:

stderr

ERZ049030I Trace parameters have been restored foran auto-start




Destination:

stderr

ERZ049031W Auto-start failed, use cold-start traceparameters instead




Destination:

stderr

ERZ049032I CICS is using shared memory ID’Tobedetermined’ for trace




Destination:

stderr

ERZ049033I Trace initialization has completed




Destination:

stderr

ERZ049034E Invalid switch ’Tobedetermined’ detectedin the CICS trace definition

Explanation: An invalid switch or key was detected inthe CICSTRACE environment setting or in theRD.stanza.

System action: Sets the key to default value

User response: Make changes in CICSTRACE andretry

Destination:

stderr

ERZ049024E • ERZ049034E


ERZ049035E Switch ’Tobedetermined’ requires anargument in the CICS trace definition

Explanation: The switch/key was not followed by arequired argument.

System action: Resets value of switch to default value.

User response: Add argument in CICSTRACEenvironment setting or within RD.stanza

Destination:

stderr

ERZ049036E The value provided for ’Tobedetermined’is too long




Destination:

stderr

ERZ049037E Invalid setting ’Tobedetermined’ forparameter ’Tobedetermined’




Destination:

stderr

ERZ049038E A failure occured writing to the restartfile




Destination:

stderr

ERZ049039I Formatting output from file’Tobedetermined’

System action: None

User response: None

Destination:

stderr

ERZ049040I Formatting complete

System action: None

User response: None

Destination:

stderr

ERZ049041I Usage: Tobedetermined [-o outputdirectory] InputFiles [-?]

System action: None

User response: None

Destination:

stderr

ERZ049042W ’Tobedetermined’ not found″

System action: The command returns a warningmessage

User response: Using the input unformatted trace filewith the correct name, path, and permissions, retry thecommand. If you need help on syntax, type thecommand cicstfmt.

Destination:

stderr

ERZ049043E ’Tobedetermined’ is not a trace file. Headertoo short

System action: Processing continues with the nexttrace file, if any.

User response: Ensure that the specified unformattedinput trace file contains valid information.

Destination:

stderr

ERZ049044W Invalid Trace Header in ’Tobedetermined’



Destination:

stderr

ERZ049045W ’Tobedetermined’ bytes skipped in’Tobedetermined’


User response: Ensure that the specified unformattedinput trace file contains valid information

Destination:

ERZ049035E • ERZ049045W


stderr

ERZ049046E Offset=’Tobedetermined’, magic number’Tobedetermined’, expected ’Tobedetermined’

System action: Processing continues with the nexttrace file, if any.


Destination:

stderr

ERZ050001E CICS is unable to re-attach sharedmemory.

Explanation: CICS made an unsuccessful attempt toattach shared memory. An earlier message possiblyprovides more details.


User response: Restart the region. If the problemrecurs, restart the region with Monitoring disabled. Ifthe problem persists, contact your support organization.

Destination:

CSMT

ERZ050002W CICS is unable to initialize the TCAstructure and therefore disablesMonitoring.

Explanation: There was insufficient memory in theTask-Private Pool to allocate the TCA structure forMonitoring.

System action: CICS continues with Monitoringdisabled for this task.

User response: Retry the transaction. If the erroroccurs repeatedly, increase the Task-Private Pool size orsimplify the user program’s private memory usage.Also try running the transaction with Monitoringdisabled.

Destination:

CSMT

ERZ050003I CICS Monitoring successfullyinitialized.

Explanation: CICS has successfully completed theMonitoring initialization.


User response: None

Destination:

console.msg

ERZ050004W Monitoring write was unsuccessful.

Explanation: CICS was unable to write to thePerformance Monitoring Extra-partition Transient DataQueue. More details are possibly provided by an earliermessage.

System action: CICS continues with Monitoringdisabled for this task.

User response: For further guidance in resolving theproblem, refer to any previous messages reporting theunsuccessful result of the write. If the problem persists,contact your support organization.

Destination:

CSMT

ERZ050006W User Event Monitoring Point (EMP)Initialization was unsuccessful withUser Load Module (ULM) response coderesponseCode.

Explanation: The User EMP CICS_EMP_Init functionreturned an unsuccessful result and has requested thatCICS disable the User Load Module (ULM) for theremainder of the task. The ULM response codeassociated with the failure is ’responseCode’.

System action: The transaction continues with UserLoad Module (ULM) disabled.

User response: This message can be safely ignored.However you must determine if this results from afailure either in the transaction or in the ULM. If socorrect the failure as necessary. If the ULM needscorrection it is necessary to restart the region in orderto use the replacement ULM. Run with Monitoringdisabled until the problem is corrected. See theTXSeries Infocenter for information about CICS UserExits.

Destination:

CSMT

ERZ050007W User Event Monitoring Point (EMP)EnterAPI function was unsuccessfulwith User Load Module (ULM) responsecode responseCode.

Explanation: The User EMP CICS_EMP_EnterAPIfunction returned an unsuccessful result and requestedthat CICS disable the User Load Module (ULM) for theremainder of the task. The ULM response codeassociated with the failure is responseCode.

System action: The transaction continues with theUser Load Module (ULM) disabled.

User response: This message can be safely ignored.However you must determine if this results from afailure either in the transaction or in the ULM. If socorrect the failure as necessary. If the ULM needs

ERZ049046E • ERZ050007W


correction it is necessary to restart the region in orderto use the replacement ULM. See the TXSeriesInfocenter for information about CICS User Exits.

Destination:

CSMT

ERZ050008W User Event Monitoring Point (EMP)WriteRecord function was unsuccessfulwith User Load Module (ULM) responsecode responseCode.

Explanation: The User EMP CICS_EMP_WriteRecordfunction returned an unsuccessful result, and hasrequested that CICS disable the ULM for the remainderof the task. The ULM response code associated with thefailure is responseCode.


User response: This message can be safely ignored.However you must determine if this results from afailure either in the transaction or in the ULM. If socorrect the failure as necessary. If the ULM needscorrection it is necessary to restart the region in orderto use the replacement ULM. See the TXSeriesInfocenter for information about CICS User Exits.

Destination:

CSMT

ERZ050009W User Event Monitoring Point (EMP)ReStart function was unsuccessful withUser Load Module (ULM) response coderesponseCode.

Explanation: The User EMP CICS_EMP_ReStartfunction returned an unsuccessful result, and hasrequested that CICS disable the ULM for the remainderof the task. The ULM response code associated with thefailure is responseCode.



Destination:

CSMT

ERZ050010W A User Event Monitoring Point (EMP)function disabled Monitoring with UserLoad Module (ULM) response coderesponseCode.

Explanation: One of the User EMP functionsrequested that CICS disable Monitoring for theremainder of this task. The ULM response codereported is responseCode.

System action: The transaction continues withMonitoring disabled.


Destination:

CSMT

ERZ050011W Unknown group name ’groupName’ inMonitoring Exclude/Include attribute.

Explanation: CICS detected an unknown group namewhen parsing the Include or Exclude attribute in theMonitor Definitions (MD).

System action: CICS continues, ignoring this Monitorgroup ID.

User response: Correct the invalid entry in theInclude or Exclude attribute. See the TXSeriesInfocenter for information about the attributes and for alist of valid values.

Destination:

CSMT

ERZ050012W Unknown field identifier ’fieldId’ inMonitoring Exclude/Include attribute.

Explanation: CICS detected an unknown field IDwhen parsing the Include or Exclude attribute in theMonitor Definitions (MD).

System action: CICS continues, ignoring this Monitorfield.

User response: Correct the invalid entry in theInclude or Exclude attribute. See the TXSeriesInfocenter for information about the attributes and for alist of valid values.

Destination:

CSMT

ERZ050008W • ERZ050012W


ERZ050013W Unable to load the User EventMonitoring Point (EMP).

Explanation: CICS made an unsuccessful attempt atloading the User Event Monitoring Point (EMP).

System action: CICS continues with User EventMonitoring disabled for the Application Server.

User response: Ensure that EMP module specified bythe UserMonitorModule attribute of the MonitoringDefinitions (MD), has been correctly specified, and thatCICS has permission to access it. Also ensure that themodule has been correctly compiled and linked. See theTXSeries Infocenter for information about theUserMonitorModule attribute.

Destination:

CSMT

ERZ050014W CICS cannot find the Monitoring TDQueue ’queueName’ in Transient DataDefinitions (TDD).

Explanation: CICS Monitoring was unable find theentry for the queue specified by the TDQ attribute inthe Monitoring Definitions (MD), in the Transient DataDefinitions (TDD).

System action: CICS continues with Monitoringdisabled for the region.

User response: Ensure that the queue specified by theTDQ attribute of the Monitoring Definitions (MD) iscorrect. If not, correct it and cold start the region. If it iscorrectly specified, add the appropriate queuedefinition to the Transient Data Definitions (TDD) andthen cold start the region. See the TXSeries Infocenterattribute.

Destination:

CSMT

ERZ050015W TD Queue ’queueName’ is not anextra-partition queue - CICS disablesMonitoring.

Explanation: The specified TD queue to whichmonitoring records are to be written is not anextra-partition queue.


User response: Ensure that the queue specified by theTDQ attribute of the Monitoring Definitions (MD) iscorrect. It must be an extra-partition queue. Ifnecessary, correct it and cold start the region. If it isincorrectly specified, add the appropriate queuedefinition to the Transient Data Definitions (TDD) andthen cold start the region. See the TXSeries Infocenterattribute.

Destination:

CSMT

ERZ050016I The Monitoring Transient Data (TD)queue has not been defined.

Explanation: You have not specified the TransientData (TD) queue to which the CICS monitoring recordsare to be written. Monitoring can still be enabled, butno attempt is made by CICS to write the monitoringrecords to a TD queue.


User response: If you do not require monitoringrecords to be written to a TD queue then do nothing. Ifyou do require monitoring records to be written to aTD queue, update the TDQ attribute in the MonitoringDefinitions (MD), so that it specifies an appropriateTransient Data (TD) queue name, then restart theregion, specifying a COLD start. See the TXSeriesInfocenter attribute.

Destination:

CSMT

ERZ050017W Cannot read system/user clock - CICSdisables Monitoring.

Explanation: CICS is unable to obtain the system timeinformation.

System action: The transaction continues withMonitoring disabled for the remainder of the task.

User response: If Monitoring is required, tryrerunning the transaction. If the problem persists,contact your support organization.

Destination:

CSMT

ERZ050022W Unexpected return code: returnCode, fromMonitoring User Load Module (ULM)function ’functionName’. Error code:errorCode.

Explanation: The Monitoring ULM function returnedan unsuccessful result and has requested that CICSdisable User Monitoring for the remainder of the task.

System action: CICS continues with User Monitoringdisabled for the task.

User response: This message can be safely ignored.However, determine the cause of the failure in theULM and correct the failure as necessary. If you makechanges to the ULM you need to restart the region inorder to use the replacement ULM. If the ULM needsto be corrected, the region possibly needs to berestarted, using the replacement ULM. See the TXSeriesInfocenter for information about CICS User Exits.

Destination:

ERZ050013W • ERZ050022W


CSMT

ERZ050023W CICS cannot read MD PermanentDatabase record.

Explanation: CICS was unable to obtain theMonitoring definitions from the MD PermanentDatabase.

System action: CICS continues with Monitoringdisabled for this region.

User response: Ensure Monitoring definitions existand are correct. If not, correct and restart the region,specifying cold start.

Destination:

CSMT

ERZ050024W CICS cannot read TD Queue On-LineDatabase record ’queueName’.

Explanation: Earlier messages were possibly issued inconnection with this problem.


User response: For further guidance in resolving theproblem, refer to any previous messages reporting theunsuccessful result. If the problem persists, contactyour support organization.

Destination:

CSMT

ERZ050025W CICS cannot allocate memory forMonitoring TD Queue record.

Explanation: There is insufficient memory in theTask-Private Pool for the Monitoring TD Queue record.

System action: CICS continues with Monitoringdisabled for the task.

User response: Restart the region. If problem persists,reduce transaction memory usage or increase theTask-Private Pool and once again restart the region.

Destination:

CSMT

ERZ050027W TD Queue ’queueName’ is not an outputqueue - CICS disables Monitoring.

Explanation: The specified TD queue to whichmonitoring records are to be written is not an outputqueue.


User response: Ensure that the queue specified by theTDQ attribute of the Monitoring Definitions (MD) is a

correct output queue. If not, correct it and cold start theregion. If it is correctly specified, add the appropriatequeue definition to the Transient Data Definitions(TDD) and then cold start the region. See the TXSeriesInfocenter attribute.

Destination:

CSMT

ERZ050028W TD Queue ’queueName’ does not havevariable length records - CICS disablesMonitoring.

Explanation: The specified TD queue to whichmonitoring records are to be written is not defined tohave variable length records.


User response: Ensure that the queue specified by theTDQ attribute of the Monitoring Definitions (MD) hasvariable length records. If not, correct it and cold startthe region. If it is correctly specified, add theappropriate queue definition to the Transient DataDefinitions (TDD) and then cold start the region. Seethe TXSeries Infocenter attribute.

Destination:

CSMT

ERZ050029W TD Queue record size too big recordSize -CICS disables User Monitoring.

Explanation: The specified TD queue record size(system plus user) is greater than allowed(USHRT_MAX).

System action: CICS continues with User Monitoringdisabled for the region.

User response: Reduce the amount of user datawritten by the User Load Module (ULM) or reduce thenumber of system fields reported.

Destination:

CSMT

ERZ050030E CICS is unable to release monitoringrecord storage in the Task-Private Pool.

Explanation: CICS was unable to release the storageused to hold the monitoring record.

System action: CICS terminates the task abnormally.

User response: It is likely that the transaction hascaused a data inconsistency in the Task-Private Pool.Check the User Event Monitoring Point (EMP) and, ifnecessary, correct the User Event Monitoring Point(EMP) function. In order to use the replacement ULM,you need to restart the region.

Destination:

ERZ050023W • ERZ050030E


CSMT

ERZ050031W TD Queue ’queueName’ does not haveMaxSize set to 0. - CICS disables UserMonitoring.

Explanation: The specified TD queue to whichmonitoring records are to be written does not haveMaxSize value 0.

System action: CICS continues with User Monitoringdisabled for the region.

User response: Ensure that the queue specified by theTDQ attribute of the Monitoring Definitions (MD) hasMaxSize set to 0. Correct it and cold start the region. Ifit is correctly specified, add the appropriate queuedefinition to the Transient Data Definitions (TDD) andthen cold start the region. See the TXSeries Infocenterattribute.

Destination:

CSMT

ERZ050035I CICS monitoring transaction foradministration console initialisedsuccessfully on port ’Tobedetermined’.

Explanation: CICS has successfully initialised thetransaction for administration console.


User response: None

Destination:

console

ERZ050036I CICS monitoring transaction foradministration console enabled.

Explanation: Monitoring through administrationconsole has been enabled for the region.


User response: None

Destination:

console

ERZ050037I CICS monitoring transaction foradministration console disabled.

Explanation: Monitoring through administrationconsole has been disabled for the region.

System action: CICS continues with monitoringthrough administration console disabled.

User response: None

Destination:

console

ERZ050038E CICS monitoring transaction foradministration console failed. Reason’Tobedetermined’.

Explanation: CICS has detected a failure in themonitoring transaction for administration console forthe reason specified in ’Tobedetermined’.

System action: CICS monitoring transaction foradministration console terminates.

User response: Correct any error indicated by’Tobedetermined’.

Destination:

console

ERZ051001E Unsuccessful memory allocation forstatistics information.

Explanation: CICS was attempting to obtain memoryfor statistics information from the Task-Private Pool.Insufficient memory was available.

System action: After further processing the transactionabnormally terminates.

User response: Reduce the quantity of GETMAINstorage used by your transaction. If the problempersists, contact your support organization.

Destination:

CSMT

ERZ051002E Unable to write to the statistics file’fileName’.

Explanation: CICS made an unsuccessful attempt towrite to the statistics file ’fileName’.


User response: As a result of this error the statisticsfile can possibly contain inconsistent data. Remove thefile before generating another statistics collection. Alsoensure that there is sufficient space available on thefilesystem to write the statistics data. If the problempersists, contact your support organization.

Destination:

CSMT

ERZ051004E Unable to initialize the statistics file.

Explanation: CICS was unable to initialize thestatistics file, because it was unable to be opened.


User response: Ensure that the directory in which thestatistics file is situated exists. Also ensure that CICS

ERZ050031W • ERZ051004E


has permission to write to the statistics file. If theproblem exists, contact your support organization.

Destination:

console.msg

ERZ051005E Unable to open the statistics file’fileName’.

Explanation: CICS made an unsuccessful attempt toopen the statistics file ’fileName’.

System action: The statistics collection is not made.The transaction continues. CICS can possibly generatefurther messages as a result of this error.

User response: Ensure that the directory in which thestatistics file is situated exists. Also ensure that CICShas permission to write to the statistics file. If theproblem exists, contact your support organization.

Destination:

CSMT

ERZ052001I Dump Sequence Number reset.

Explanation: CICS has reset the Dump SequenceNumber to zero. CICS uses this number to name dumpfiles. Therefore CICS can possibly overwrite filesalready in the dump sub-directories, whose names areof the form XXXX0001 and YYYY0002, for example.


User response: Copy the dump directory,sub-directories, and contents to another directory. Thisensures that CICS does not overwrite dump filesalready existing in the sub-directories.

Destination:

console.msg

ERZ052003W Unable to use all the dump directorynames due to lack of memory.

Explanation: Either there are more sub-directoriesthan CICS can support, or the sub-directory names aretoo long to include all the sub-directories as possiblesites for dump files.

System action: CICS ignores some sub-directories.

User response: Shorten the dump sub-directory namesto attempt to include them as possible sites for dumpfiles. Alternatively, reduce the number of dumpdirectories.

Destination:

console.msg

ERZ052004I Dump to ’dumpsetName’ started.

Explanation: A dump was requested, and CICS iscreating a dump by the given name.

System action: CICS creates the named dump, andgenerates message ERZ5207I on successful completionof the dump.

User response: Check the dump. For information,please see the TXSeries Infocenter.

Destination:

console.msg

ERZ052006I Shutdown Dump in progress.

Explanation: A shutdown command has been issuedand the region is configured to produce a dump onshutdown.

System action: CICS produces a dump and terminatesthe region.


Destination:

console.msg

ERZ052007I Dump to ’dumpsetName’ completed.

Explanation: CICS has created the specified dump.



Destination:

console.msg

ERZ052008W Out of space for dump file in directory’directoryName’.

Explanation: When writing to the specified directory,CICS detected an out of disk space status.

System action: CICS continues producing the dumpwith a new file and directory.

User response: Check the disk space available in thespecified directory and, if necessary, create some morespace.

Destination:

console.msg

ERZ052011W Unable to access dump directory entry’entryName’.

Explanation: The specified dump sub-directory doesnot exist or is not a directory.

ERZ051005E • ERZ052011W


System action: CICS attempts to use the next availabledump directory. It ignores the sub-directory until thesub-directory is accessible.

User response: Change the access permissions andtype of the dump directory entry, if it exists. If theentry does not exist, create it with the required accesspermissions.

Destination:

console.msg

ERZ052012W Unsuccessful attempt to access coredump sub-directory ’directoryName’.

Explanation: The core dump sub-directory does notexist or is not a directory.

System action: CICS disables core dumps until thecore dump sub-directory is accessible.

User response: Check the core dump sub-directory asspecified by the value of the CoreDumpName attributein the Region Definition. Check the availability of thecore dump sub-directory. If the sub-directory does notexist, create it with read, write and execute permissionsfor user ’cics’.

Destination:

console.msg

ERZ052013I Dump dumpNumber - dumpCount coredump(s) created.

Explanation: CICS displays the number of core dumpsproduced for a dump.



Destination:

console.msg

ERZ052014W Dump ’dumpNamedumpNumber’ : Attemptno. attemptNumber failed to create a coredump, error errorCode

Explanation: CICS failed to create the specified coredump on the numbered attempt.


User response: Check the core dump sub-directory asspecified by the value of the CoreDumpName attributein the Region Definition. Check the availability of thecore dump sub-directory. If the sub-directory does notexist, create it with read, write and execute permissionsfor user ’cics’. Further information can be obtainedfrom the error number supplied.

Destination:

console.msg

ERZ052015W Dump directory ’directoryName’ hasinvalid permissions; expecting’permissions’.

Explanation: An entry under the dump directory is adirectory but has incorrect permissions.

System action: CICS ignores the dump sub-directory.

User response: Correct the access permissions on thedump sub-directory.

Destination:

console.msg

ERZ052016W Unexpected error code (errorCode) whenattempting to access dump directory’directoryName’.

Explanation: CICS detected an unexpected accesserror.

System action: CICS ignores the dump sub-directory.

User response: If the problem persists, contact yoursupport organization.

Destination:

console.msg

ERZ052017W Disk quota limit reached in directory’directoryName’.

Explanation: When writing to the specified directory,CICS reached the disk space quota limit.

System action: CICS continues to produce the dumpwith a new file.

User response: Check the disk space quota allocation.If possible, create a new directory. Otherwise, deletesomething from the directory.

Destination:

console.msg

ERZ052018E Cannot access region dump directory orsub-directory ’directoryName’.

Explanation: The dump directory specified in theDumpName attribute of the Region Definitions (RD) isin error; or no sub-directories exist in the region dumpdirectory.

System action: CICS disables all dumps.

User response: Ensure the dump directory exists andthat it has the correct permissions. Also ensure that anydump directory created contains subdirectories intowhich the dumps can be placed. CICS uses thesub-directories, under the dump directory, in collatingsequence. Ensure the subdirectories have read, writeand execute permission for user cics.

Destination:

ERZ052012W • ERZ052018E


console.msg

ERZ052020E Unable to access region dump directory’directoryName’ - system error ’errorCode’.Unable to produce dump output

Explanation: CICS cannot access the region dumpdirectory.


User response: Check the cause of this error. Ensurethe dump directory exists and that it has the correctpermissions. Also ensure that any dump directorycreated contains subdirectories into which the dumpscan be placed. In a similar manner to the root dumpdirectory ensure the subdirectories have read, write andexecute permission for user ’cics’.

Destination:

console.msg

ERZ052021E CICS is unable to provide a dump dueto insufficient system capability

Explanation: A dump has been requested but thesystem is not sufficiently initialized to perform aformatted dump.

System action: CICS terminates the region.

User response: Check the previous system messages.If you cannot solve the problem, contact your supportorganization.

Destination:

console.msg

ERZ052022E Abnormal termination AKCS; unable toclose the dump file due to a transienterror.

Explanation: CICS has timed out while attempting toclose the dump file after a dump.

System action: CICS does not perform the requestedoperation. CICS terminates the transaction with abendcode AKCS in order to avoid a potential deadlocksituation.

User response: Check the availability of the dumpdirectory. If the problem occurs repeatedly contact yoursupport organization.

Destination:

console.msg

ERZ052023E Unable to write data to the dump file.

Explanation: CICS has detected an error whileattempting to write to the dump file.

System action: CICS does not perform write the datato the dump file. The dump continues.

User response: Check the availability of the dumpdirectory. If the problem occurs repeatedly contact yoursupport organization.

Destination:

console.msg

ERZ052024E Unable to perform dump of area ’areaId’,exception ’exceptionName’ caught.

Explanation: Part of the system dump was unable tobe performed because of inconsistency in CICS internaldata.

System action: The dump continues.

User response: Check next CICS internal consistencycheck for possible indications of the problem. Contactyour support organization.

Destination:

console.msg

ERZ052025I Dumping initialized with these optionsset to YES ’dumpOptions’.

Explanation: Dump support has been initialized. Anydump options which were set to YES in the RegionDefinitions (RD) are listed.

System action: Startup continues.

User response: None

Destination:

console.msg

ERZ052026E Unable to perform full dump of internaltoolkit data, exception ’exceptionName’caught.

Explanation: Part of the system dump was unable tobe performed because of inconsistency in CICS Toolkitinternal data.


User response: Check any CICS Toolkit data whichwas dumped and check the results of the next CICSinternal consistency check for possible indications ofthe problem. Contact your support organization.

Destination:

console.msg

ERZ052027I Length of data dumped truncated to’INFDU_MAX_FLENGTH’.

Explanation: A request to dump data specified alength greater than the maximum; the length of datadumped is truncated to the maximum.


ERZ052020E • ERZ052027I


User response: If you require to dump greater thanthe maximum length of data then this must be done inseparate dump requests each specifying a length notgreater than the maximum.

Destination:

CSMT

ERZ052028W Storage not allocated for parameter lists- user exit 17 (UE052017).

Explanation: Either a dump was requested duringvery early task initialization, before storage allocatedfor the header parameter list or a request to obtainstorage in which to build a specific parameter list foruser exit 17 (UE052017) failed.

System action: The dump continues as if user exit 17(UE052017) is inactive.

User response: Take a SNAP dump and investigatestorage usage in the CICS region; consider increasingthe amounts of storage available to CICS via regiondefinition parameters.

Destination:

CSMT

ERZ052029E CICS is unable to suspend a processduring a dump due to insufficientstorage

Explanation: During a system dump, an active processhas been requested to wait until the dump has finished.However, there is not enough storage available in theregion storage pool to do this.


User response: Increase the Region Definition valueMaxRegionPool and restart the region.

Destination:

console.msg

ERZ052030E Usage: Tobedetermined [ -? ] RegionName

Explanation: The command was issued without aparameter.

System action: Terminates the command.

User response: Enter a valid region name.

Destination:

ERZ052031E Region Tobedetermined is not running

Explanation: The command was unable to find theprocess of the CICS region.

System action: Terminates the command

User response: Verify whether the region is runningand a region lock file exists.

Destination:

ERZ052032I Dump successfully initiated

Explanation: Dump was successfully initiated. Referto the console file for more information.

System action: NONE

User response: Refer to the console file for moreinformation.

Destination:

ERZ052033I Running this command might bring theregion to an inconsistent state. Do youwant to continue [N]:

Explanation: If you run this command on a workingregion, it would bring the region to an inconsistentstate.

System action: NONE

User response: This command must only be usedwhen the region is in a hung state or whenrecommended by your IBM support representative.

Destination:

ERZ052034E The region ’regionName’ does not exist

Explanation: This message is output when cicsedumpprocesses the command and detects that the regiondoes not exist.

System action: The command is not processed.

User response: None

Destination:

stderr

ERZ053001W Unable to cancel the CICS-privatetransaction responsible for automaticstatistics collection

Explanation: CICS encountered a problem whenprocessing your command to reschedule the automaticstatistics collection facility. More details are possiblyprovided by an earlier message.

System action: Processing of your commandcontinues.

User response: Refer to the associated message forguidance on resolving the problem.

Destination:

console.msg

ERZ052028W • ERZ053001W


ERZ053002I CICS statistics initialization is complete.Interval recording is active, for aninterval of intervalHours hours,intervalMinutes minutes andintervalSeconds seconds. The end-of-daytime is set to EODhours hours,EODminutes minutes and EODsecondsseconds.

Explanation: CICS has initialized the automaticstatistics collection facility. Statistics are recorded andthen reset at the end of each interval. The intervalduration is intervalHours, intervalMinutes andintervalSeconds. The final collection of the day(end-of-day) are made EODhours, EODminutes andEODseconds after midnight.

System action: CICS initialization continues.

User response: None

Destination:

console.msg

ERZ053003I CICS statistics initialization is complete.The interval duration is set tointervalHours hours, intervalMinutesminutes and intervalSeconds seconds,with interval recording inactive. Theend-of-day time is set to EODhourshours, EODminutes minutes andEODseconds seconds.

Explanation: CICS has initialized the automaticstatistics collection facility. Statistics are be recorded atthe end of each interval. If interval recording isactivated, the interval duration is be intervalHours,intervalMinutes and intervalSeconds. The final collectionof the day (end-of-day) is made EODhours, EODminutesand EODseconds after midnight.


User response: None

Destination:

console.msg

ERZ053004I Statistics interval set to intervalHourshours, intervalMinutes minutes andintervalSeconds seconds″

Explanation: CICS has successfully processed yourrequest to alter the statistics interval duration. Statisticsare now be recorded using an interval of intervalHours,intervalMinutes and intervalSeconds, provided intervalrecording is active.


User response: None

Destination:

console.msg

ERZ053005I Statistics end-of-day set to EODhourshours, EODminutes minutes andEODseconds seconds

Explanation: CICS has successfully processed yourrequest to alter the time at which the final statisticscollection of the day (end-of-day) is made. Theend-of-day collection is now made at EODhours,EODminutes and EODseconds after midnight.


User response: None

Destination:

console.msg

ERZ053006E Unsolicited statistics could not becollected

Explanation: Statistics for a resource about to bedeleted (unsolicited statistics) were unable to becollected due to an error while collecting the statistics.More details are possibly provided by an earliermessage.

System action: CICS has not written the statistics. Theregion continues but is possibly unable to process anyfurther requests to collect statistics, until the problemhas been resolved.


Destination:

CSMT

ERZ053007W The request to schedule automaticstatistics collection was unsuccessful

Explanation: CICS encountered a problem whenprocessing your command to reschedule the automaticstatistics collection facility. This was due to anunsuccessful request to asynchronously start theCICS-private transaction responsible for the automaticcollection of statistics. More details are possiblyprovided by an earlier message.

System action: The region continues, but automaticstatistics collections is not made until the facility isreactivated.

User response: Refer to the associated message forguidance on resolving the problem. Once the problemhas been resolved, you can reactivate the automaticstatistics collection facility by altering the nextcollection time, using the SET STATISTICS command.

Destination:

console.msg

ERZ053002I • ERZ053007W


ERZ053008E The end-of-day statistics could not becollected

Explanation: CICS was unable to make the finalstatistics collection of the day (end-of-day) due to anerror when collecting the statistics. More details arepossibly provided by an earlier message.

System action: CICS has not written the statistics. Theregion continues but is possibly unable to process anyfurther requests to collect statistics until the problemhas been resolved.


Destination:

CSMT

ERZ053009E Interval statistics could not be collected

Explanation: CICS was unable to make an intervalstatistics collection, due to an error when collecting thestatistics. More details are possibly provided by anearlier message.

System action: CICS has not written the statistics. Theregion continues but is possibly unable to process anyfurther requests to collect statistics until the problemhas been resolved.


Destination:

CSMT

ERZ053010E Unable to save configuration to therestart file

Explanation: CICS was unable to save the statisticsrestart configuration to the region restart file. Moredetails are possibly provided by an earlier message.


User response: Remove the CICS restart file andrestart the region, specifying a COLD start. Refer to theassociated message for further guidance on resolvingthe problem. If the problem persists, contact yoursupport organization.

Destination:

console.msg

ERZ053011E Request statistics could not be collected

Explanation: CICS was unable to process your requestto perform a statistics collection, due to an error whencollecting the statistics. More details are possiblyprovided by an earlier message.

System action: CICS has not written the statistics. The

region continues but is possibly unable to process anyfurther requests to collect statistics until the problemhas been resolved.


Destination:

CSMT

ERZ053012E Unable to obtain AUTO startinformation, defaulting to a COLD startfor statistics initialization

Explanation: CICS was unable to obtain the statisticsconfiguration information from the restart file. Statisticsare initialized as per a COLD start. More details arepossibly provided by an earlier message.



Destination:

console.msg

ERZ053013I Statistics interval recording has beenactivated

Explanation: CICS has successfully processed yourrequest to activate statistics interval recording. Statisticsare now recorded at the end of each interval.


User response: None

Destination:

console.msg

ERZ053014I Statistics interval recording has beendeactivated

Explanation: CICS has successfully processed yourrequest to stop statistics interval recording. Statistics areno longer be recorded at the end of each interval, untilinterval recording is reactivated.


User response: None

Destination:

console.msg

ERZ053015I Re-starting the automatic statisticscollection facility

Explanation: The CICS automatic statistics collectionfacility was not active. This is possibly due to aproblem earlier in the region. CICS is restarting thefacility.

ERZ053008E • ERZ053015I


System action: The automatic collection of statistics isrestarted. The region continues.

User response: None

Destination:

console.msg

ERZ054001E Usage: ’cicsdfmt’ [ [[ -r regionName ] [fileName ]] | directoryName | fileName| [ -p [ -r regionName ] [dumpFileName ]] ] | -?

Explanation:

Invalid arguments were given to cicsdfmt. Validarguments are

-r regionNamespecifies the region to use

fileNamenames a particular file to format

directoryNamelists dump files in directoryName

-p purge all the dump files

-p dumpFileNamepurge the specified dumpFileName dump files

System action: None

User response: Check the syntax supplied to cicsdfmtand retry the command. See the TXSeries Infocenter.

Destination:

stderr

ERZ054002E Invalid region ’regionName’

Explanation: The region name given is not known toCICS.

System action: None

User response: Correct region name and retry thecommand.

Destination:

stderr

ERZ054003E Invalid dump file ’fileName’ - entercicsdfmt -r regionName to list validdump files

Explanation: cicsdfmt cannot find a dump file named’fileName’ to be formatted. The name of the dump filemust be specified without the suffix ″.dmpnn″.cicsdfmt has searched either the specified region’sdump directory, or the current directory and the parentof the current directory and the default region’sdirectory.

System action: None

User response: Check that you have specified a validdump file name without the suffix. Enter the commandcicsdfmt -r regionName to list the valid dump files.Retry the command specifying the name of a validdump file. See the TXSeries Infocenter.

Destination:

stderr

ERZ054004E No dump files found in directory’directoryName’

Explanation: The directory ’directoryName’ contains nodump files.

System action: None

User response: Ensure that the directory supplied wasindeed the directory where the dumps were writtenand if, this is correct, contact the system administratorto determine the current destination of dump files.

Destination:

stderr

ERZ054005E Error while reading dump file ’fileName’

Explanation: An error has occurred while formattingthe named dump file.

System action: None

User response: Since one of the dump files beingprocessed was found to be in error, reproduce thedump or obtain assistance to determine the nature ofthe error and attempt possible correction.

Destination:

stderr

ERZ054006I The following files are available forformatting:

Explanation: A list of dump files which can beformatted follows this message.

System action: None

User response: None

Destination:

stderr

ERZ054007E No region name given

Explanation: You have entered the -r option withoutspecifying a region name.

System action: None

User response: Correct the command line argumentsand retry.

Destination:

ERZ054001E • ERZ054007E


stderr

ERZ054008E Problem encountered with’programName’ executable

Explanation: A program that has been called hasfailed.

System action: None

User response: Ensure the executable exists, check thepath that is used to access the required executable, andcheck that there is enough space on the filesystem.Examine error output to see if a previous erroroccurred. This possibly indicates a CICS internal error.

Destination:

stderr

ERZ054009E Unable to read the dump formattemplate file, ’templateFile’

Explanation: The dump formatting program has beenunable to read the dump format template file.

System action: None

User response: Ensure the dump formatting templatehas been installed and has read permission.

Destination:

stderr

ERZ054010I Do you really want to remove the dumpfiles?

Explanation: Asks you if you want to remove thedump files.

System action: None

User response: Enter either ’yes’ or ’no’.

Destination:

stderr

ERZ054011E File ’fileName’ in the path name does notexist

Explanation: cicsdfmt cannot find the dump filenamed ’fileName’ to be removed. cicsdfmt has eithersearched the specified region’s dump directory, or thecurrent directory and the parent of the current directoryand the default region’s directory.

System action: None

User response: Check for valid file names and retrythe command.

Destination:

stderr

ERZ054012E Unable to find a default region

Explanation: cicsdfmt encountered a problem whileobtaining the name of the default region.

System action: cicsdfmt terminates with a non-zerostatus.

User response: Ensure that the default region is set upcorrectly with the right access permissions. The defaultregion is the name in the environment variableCICSREGION. If you prefer to use a region other thanthe default, run cicsdfmt again specifying the regionname using the -r option.

Destination:

stderr


Explanation: cicsdfmt encountered a problem whileobtaining information about the CICS system installedon your machine.

System action: cicsdfmt terminates with a non-zerostatus.


Destination:

stderr

ERZ054014E Entry ’databaseEntry’ not found forpermanent database class ’databaseName.’

Explanation: cicsdtmt tried to read a record from the’databaseName.’ stanza file, looking for resource’databaseEntry’, but failed to do so.


User response: Check that the stanza file exists, andhas the correct permissions to enable cics to read fromit. Check that this file has not been corrupted.

Destination:

stderr

ERZ054015E Directory ’dirName’ not found

Explanation: cicsdtmt tried to access dump directory’dirName’ but was unable to.


User response: Check that the directory exists and isreadable. Check that you have installed your cicsregion correctly.

Destination:

stderr

ERZ054008E • ERZ054015E



Explanation: cicsdfmt tried to access some memoryfor its own working storage but was unable to do so.



Destination:

stderr

ERZ054017E Unable to remove file ’fileName’, error’errno’

Explanation: cicsdfmt tried to remove file ’fileName’but was unable to do so.

System action: The command continues, but does notremove the file.

User response: Check you have the necessarypermissions to remove the file. Check the value oferrno for more information.

Destination:

stderr





Destination:

stderr

ERZ054019E No dump files found in directoriesunder ’directoryName’

Explanation: The directory ’directoryName’ contains nodump files.

System action: None

User response: Ensure that the directory supplied wasindeed the directory where the dumps were writtenand if, this is correct, contact the system administratorto determine the current destination of dump files.

Destination:

stderr

ERZ054020E Problem using region ’regionName’

Explanation: CICS encountered a problem accessingdetails about region ’regionName’.

System action: The command terminates with anabnormal return code.

User response: Ensure that the region exists and isproperly configured. If it does, ensure that you haveinstalled CICS correctly.

Destination:

stderr

ERZ055001E Usage: cicssfmt [[-c categoryName[,..]] [-sstartTime] [-e endTime] [-l pageLength][-w pageWidth] [-h] [-i] fileName1fileName2 ...] | [-?]

Explanation: Your command specified the -?parameter or contained incorrect syntax.

System action: The sample application cicssfmtterminates.

User response: Retry the command using the correctsyntax, as shown in the message.

Destination:

stderr

ERZ055002E The sample application cicssfmtdetected an unsuccessful open/close ofthe statistics file ’fileName’.

Explanation: The sample application cicssfmt wasunable to open or close the file you requested cicssfmtto process.

System action: The sample application cicssfmtabnormally terminates.

User response: Check the name of the file and thepermissions and retry the command.

Destination:

stderr

ERZ055003E The sample application cicssfmtdetected an unsuccessful read attemptfor the statistics file ’fileName’.

Explanation: The sample application cicssfmt detecteda read error for the file you requested for processing.


User response: Check the name of the file andwhether CICS reported any errors when writing to thisfile. If the name is incorrect, retry the command withthe correct file name.

Destination:

ERZ054016E • ERZ055003E


stderr

ERZ055004E The sample application cicssfmtunexpectedly detected End Of File(EOF) for statistics file ’fileName’.

Explanation: The file you requested cicssfmt toprocess terminated abnormally.


User response: Ensure that the file ’fileName’, is avalid CICS statistics file. Examine the CICS messagelogs to determine whether CICS reported any errorswhen generating this file,

Destination:

stderr

ERZ055005E End time (-e option) is earlier than starttime (-s option).

Explanation: Your specified end time is earlier thanyour specified start time. The end time must be laterthan the start time.


User response: Retry the command specifying validstart and end times.

Destination:

stderr

ERZ055006E Unknown category type ’categoryName’specified for -c flag.

Explanation: The category that you have specified isnot supported by cicssfmt.


User response: Retry the command specifying asupported category type.

Destination:

stderr

ERZ055007E You specified an invalid pagelength forthe -l option.

Explanation: Your specified page length is invalid.You must specify a positive number for the pagelength.


User response: Retry the command specifying apositive number for page length.

Destination:

stderr

ERZ055008E You specified an invalid pagewidth forthe -w option.

Explanation: Your specified page width is invalid. Youmust specify a positive number (50 or greater) for thepage width.


User response: Retry the command specifying apositive number (50 or greater) for page width.

Destination:

stderr

ERZ055009E You incorrectly specified the timeformat for the -s or -e option. It must beexpressed as yymmddhhmmss.

Explanation: Your specified time is not of the correctformat. You must specify the time in the formatyymmddhhmmss.


User response: Retry the command specifying time inthe format yymmddhhmmss.

Destination:

stderr

ERZ055010E Unsuccessful memory allocationdetected.

Explanation: Insufficient memory was available whencicssfmt tried to perform a malloc call.


User response: Check available memory space. Tryending unnecessary sessions to release memory, orinstall additional memory. If the problem persistscontact your support organization.

Destination:

stderr

ERZ055011E The sample application cicssfmt doesnot produce Summary Statistics for’categoryName’ category.

Explanation: You selected the option for a SummaryReport and also the categoryName category. These arenot compatible.


ERZ055004E • ERZ055011E


User response: Retry the command specifying a validcategory.

Destination:

stderr

ERZ055012W The sample application cicssfmt isunable to find the record within theperiod specified by thestarttime/endtime in file ’fileName’.

Explanation: The sample application cicssfmt wasunable to find the record within the specified period inthe statistics file.

System action: The sample application cicssfmtformats the entire statistics file.


Destination:

stderr

ERZ055013E You have not specified any files to beformatted.

Explanation: You must specify at least one filename.


User response: Retry the command specifying at leastone statistics file name.

Destination:

stderr

ERZ055014E The pagewidth is insufficient to displaythe statistics data.

Explanation: The page width that you specified wastoo small for the sample application cicssfmt to displaythe statistics data.


User response: Retry you request, specifying a largerpage width, via the -w option.

Destination:

stderr

ERZ055015W The statistics file ’fileName’ is empty.

Explanation: The file you requested cicssfmt toprocess was empty.

System action: The sample application cicssfmtcontinues.

User response: Ensure that the file ’fileName’, is avalid CICS statistics file. Also ensure that a CICSstatistics collection was made and written to the

statistics file ’fileName’. If so, examine the CICS messagelogs to determine whether CICS reported any errorswhen generating this file,

Destination:

stderr

ERZ056001E CICS condition variable wakeup listspecifies a non-existent process

Explanation: The list of sleeping process identifiersassociated with a given condition variable includes theidentifier of a process that is no longer in existence.This is an error because the process does not normallydisappear while it is sleeping waiting on the condition.

System action: If a single process wakeup is beingperformed the process identifier in question is removedfrom the list of sleeping process identifiers and a newprocess is chosen for wakeup. If a multiple processwakeup is being performed then the process identifieris discarded and wakeup of the remaining sleepingprocesses continues.

User response: The system administrator needs toinvestigate the disappearance of the sleeping process.Other error messages preceding or following thismessage possibly give information about a processdeath. Note that other than for some forcepurge andabnormal application server termination conditions, thedeath of the process is not supposed to be caused byCICS itself as the process is supposed to be sleeping onthe condition. It was possibly killed by a user from thecommand line, by a user’s application program, or byan erroneous transaction program.

Destination:

console.msg

ERZ056002E Unexpected signal signalNumber caught

Explanation: Another process or user sent a signalthat this process did not expect.

System action: The process takes the system defaultaction (core dump).

User response: Determine why the signal is beingsent; it was possibly sent by a user from the commandline.

Destination:

stderr

ERZ056003E Unsuccessful attempt to allocate storageto perform a wait on a condition

Explanation: Insufficient storage was available whenallocating Region-Pool memory used to queue aprocess that is attempting to wait on a condition.

System action: The waiting process is abnormallyterminated with code A561.

ERZ055012W • ERZ056003E


User response: The error arises because CICS has runout of available Region-Pool storage. Have the systemadministrator investigate reconfiguring the system tomake more memory available.

Destination:

console.msg

ERZ056005E CICS self-consistency checking detecteda Signature inconsistency: expected’expectedSignature’ found ’actualSignature’at address signatureAddress

Explanation: CICS self-consistency checking hasdetected that the signature actualSignature isinconsistent with that expected expectedSignature


User response: Restart the region at the earliestpossible opportunity. If CICS self-consistency checkingcontinues to detect inconsistencies, then this is aninternal software error; contact your supportorganization.

Destination:

console.msg

ERZ056006E CICS self-consistency checking detectedan inconsistency in an unique identitypool’s state: maximum pool size poolSize,high water mark highWaterMark, takeindex takeIndex

Explanation: When performing self-consistencychecking CICS detected that internal management dataon the state of a unique identity pool has becomecorrupt. highWaterMark cannot be greater than poolSizeand takeIndex cannot be greater than highWaterMark.



Destination:

console.msg

ERZ056007E CICS self-consistency checking detectedan inconsistency in an unique identitypool’s state: pool table pointer is NULL

Explanation: When performing self-consistencychecking CICS detected that internal management dataon the state of an unique identity pool has becomecorrupt. The pointer to the table containing the uniqueidentity states cannot be NULL.



Destination:

console.msg

ERZ056008E CICS self-consistency checking detectedan inconsistency in an unique identitypool’s state: Id poolId is in use, but highwater mark is highWaterMark

Explanation: When performing self-consistencychecking CICS detected that internal management dataon the state of an unique identity pool has becomecorrupt. Ids greater than or equal to highWaterMarkcannot be in use yet.



Destination:

console.msg

ERZ056012E Unsuccessful attempt at getting systemhostname

Explanation: An unsuccessful attempt was made toget the name of the host system using the unamecommand.

System action: Processing continues; however, furthermessages can be generated as a result of this error.

User response: As this problem indicates a problemwithin CICS it is extremely important that you save alldiagnostic information and contact your supportorganization.

Destination:

CSMT, stderr

ERZ056014E A CICS internal buffer has overflowed

Explanation: An internal buffer used to expand stringshas overflowed.

System action: Processing continues; however, othermessages can be generated as a result of this error.

User response: As this problem indicates a problemwithin CICS it is extremely important that you save alldiagnostic information and contact your supportorganization.

Destination:

ERZ056005E • ERZ056014E


CSMT, stderr

ERZ056015E Default region name is too long

Explanation: When trying to determine a workingregion name, if one was not explicitly selected, thedefault region name was found to be too long. Allregion names must be made up of 8 or less characters.

System action: No working region is determined.

User response: Either select a correct working CICSregion name or establish a new working region nameby updating the environment variable CICSREGION.

Destination:

stderr

ERZ056016E Default region not found

Explanation: When trying to determine a workingregion name, no region directory was found.

System action: No working region is determined.

User response: Either select a correct working CICSregion name, create a new region, or update theenvironment variable CICSREGION so that a defaultregion exists with the correct access permissions.

Destination:

stderr

ERZ056017E Unable to access default region

Explanation: The access permissions on the defaultregion directory are such that you do not havesufficient authority to use the region.

System action: The selected command does notexecute.

User response: If the default region is a valid workingregion, check that the directory for the default one hasthe required permissions. Ensure that it is owned byuser cics and has read, write, and execute permissionsfor its owner. Otherwise, either select a correct workingCICS region name or establish a new working regionname by updating the environment variableCICSREGION.

Destination:

stderr

ERZ056018E Unexpected error while obtainingdefault region name

Explanation: There was a CICS internal error.

System action: The selected command does notexecute.

User response: As this problem indicates a problemwith CICS default processing please save all diagnostic

information and contact your support organization. Tobypass the problem either select a correct workingCICS region name or establish a new working regionname by updating the environment variableCICSREGION.

Destination:

stderr

ERZ056020E Unable to set locale as ’localeName’

Explanation: CICS was unsuccessful in setting localeeither because the catalog does not exist or because itwas unable to be found.

System action: The request is abnormally terminated.

User response: On UNIX the locale categories withinthe locale can be modified by a number of environmentvariables. Ensure that each of these environmentvariables contains a valid locale for the machine wherethe operation is to be done (such as LANG=En_US)and then retry.

Destination:

stderr

ERZ056055E Abnormal termination U5655: A crucialmutual exclusion lock at addresslockAddress is held by a terminatedprocess

Explanation: In order to maintain integrity of datastructures CICS uses a mutual exclusion lockingscheme; a process has terminated without releasing itsexclusive hold on a resource lock.

System action: The region is abnormally terminatedwith code U5655.

User response: Refer to preceding and subsequentmessages for an indication of why this happened.Additionally, the system administrator needs toinvestigate the disappearance of the process. Forexample, a force purge of a transaction has this effect.

Destination:

console.msg

ERZ056056E CICS self-consistency checking detectedan inconsistency in a unique identitypool’s state: range start RangeStart isgreater than range end RangeEnd

Explanation: When performing self-consistencychecking, CICS detected that internal management dataon the state of a unique identity pool has becomecorrupt. RangeStart must be less than or equal toRangeEnd.


User response: Restart the region at the earliest

ERZ056015E • ERZ056056E


possible opportunity. If CICS self-consistency checkingcontinues to detect inconsistencies, then this is aninternal software error; contact your supportorganization.

Destination:

console.msg

ERZ056057E CICS self-consistency checking detectedan inconsistency in a unique identitypool’s state: range start RangeStart andrange end RangeEnd conflict with eithercurrent pool size PoolSize or poolhighwater mark HighWaterMark

Explanation: When performing self-consistencychecking, CICS detected that internal management dataon the state of a unique identity pool has becomecorrupt. PoolSize and HighWaterMark must never exceedthe difference between RangeEnd and RangeStart.



Destination:

console.msg

ERZ056058W No valid protocol sequence found inRPC_SUPPORTED_PROTSEQS,usingthe default values

Explanation: In the environment variableRPC_SUPPORTED_PROTSEQS no valid protocolsequence is mentioned. Hence the protocol sequencementioned in RPC_SUPPORTED_PROTSEQS is ignoredand default protocol sequences are used.

System action:

User response: Restart the region after setting thevalid protocol sequences inRPC_SUPPORTED_PROTSEQS.

Destination:

console.msg

ERZ056059I Protocol sequence ’protocolsequence’ issupported

Explanation: none

System action:

User response: none

Destination:

console.msg

ERZ057001E Cannot access message catalog’catalogName’ for message ’messageId’

Explanation: CICS was unable to retrieve the messagetext from the message catalog ’catalogName’. Note thatthe Message Sequence Number (MSN) associated withthis message is the MSN for the original message.


User response: If this is the first time CICS is beingrun, then ensure that the operating system permits asufficient number of open files per process. Otherwise,check that an accessible CICS message catalog exists ina directory named in your environment variableNLSPATH. On UNIX, a possible additional cause is thatthe environment variable LANG is not valid.

Destination:

console.msg

ERZ057002E CICS internal error: Unsuccessfulcondition ’conditionName’ for function’functionName’ on line lineNumber in file’fileName’ of module moduleNumber

Explanation: CICS internal validation has detected acondition ’conditionName’ for function ’functionName’that is not supposed to occur.

System action: CICS generates one of the followingmessages: ERZ5703E, ERZ5704E, ERZ5705E, ERZ5706E,or ERZ5707E.

User response: Refer to next message.

Destination:

console.msg, CSMT, stderr

ERZ057003E CICS internal error: Abnormallyterminating process with exit code’returnCode’

Explanation: CICS detected an unsuccessful conditionwithin the CICS internal code.

System action: CICS abnormally terminates therelevant process with abnormal termination code A57A.If the condition was detected while processing anapplication then the application server terminates andCICS attempts to continue. Otherwise, the regionterminates.

User response: As this indicates a problem with CICSit is important that you save all diagnostic information,especially dumps, and contact your supportorganization.

Destination:

CSMT

ERZ056057E • ERZ057003E


ERZ057004E CICS internal error: Abnormallyterminating transaction with exit code’returnCode’

Explanation: CICS detected an unsuccessful conditionin the internal code of one of its transactions.

System action: CICS abnormally terminates thetransaction with abnormal termination code A57A.

User response: As this problem indicates a problemwith a CICS supplied transaction it is important thatyou save all diagnostic information, especially dumps,and contact your support organization.

Destination:

stderr

ERZ057005E CICS internal error: Abnormallyterminating region with exit code’returnCode’

Explanation: CICS detected an unsuccessful conditionwithin the CICS internal code.

System action: CICS abnormally terminates the regionwith abnormal termination code U5701.

User response: As this problem indicates a problemwith CICS it is important that you save all diagnosticinformation, especially dumps, and contact yoursupport organization.

Destination:

console.msg

ERZ057006E CICS internal error: Abnormallyterminating threaded utility

Explanation: CICS detected an unsuccessful conditionin the internal code of one of its threaded utilities.

System action: CICS abnormally terminates thethreaded utility with code 99.

User response: As this problem indicates a problemwith a CICS threaded utility it is important that yousave all diagnostic information and contact yoursupport organization.

Destination:

stderr

ERZ057007E CICS internal error: Abnormallyterminating utility

Explanation: CICS detected an unsuccessful conditionin the internal code of one of its utilities.

System action: CICS abnormally terminates the utilitywith code 99.

User response: As this problem indicates a problemwith a CICS utility it is important that you save all

diagnostic information and contact your supportorganization.

Destination:

stderr

ERZ057010E Unable to display message ’messageId’ asit is corrupted in catalog ’catalogName’

Explanation: The message text CICS retrieved fromthe message catalog ’catalogName’ was not prefixed by″ERZ″. Note that the Message Sequence Number (MSN)associated with this message is the MSN for theoriginal message.


User response: Check the operating system error logto confirm that there are no disk problems. Otherwise,as this problem is not supposed to occur, reinstall theCICS Machine Readable Information (MRI) for yourlanguage.

Destination:

console.msg

ERZ057017E Not enough memory available to initiateerror handling

Explanation: CICS was unable to allocate the memoryrequired for error processing.


User response: Increase the size of the Region poolmemory, as defined in the Region Definitions (RD), byoverriding the attribute in the region startup commandline and restart the region.

Destination:

stderr

ERZ057020E Inconsistent signature string

Explanation: CICS self-consistency checking hasdetected an inconsistency in one of its internal datastructures


User response: Check the system dump for signs ofan inconsistency. Contact your support organization.

Destination:

console.msg

ERZ057004E • ERZ057020E


ERZ057021E Buffer OVERFLOW while processingmessage ’messageId’ - supplied sizelengthu, required size sizeu

Explanation: CICS message processing facility hasoverwritten a buffer.

System action: CICS abnormally terminates thecurrent execution environment: in the runtime, thewhole region is terminated; elsewhere, the currentprocess is terminated.

User response: The message catalog is possiblycorrupted. Reinstall the CICS Machine ReadableInformation (MRI) for your language. If the problempersists, contact your support organization.

Destination:

console.msg, stderr

ERZ057022W Failed to complete write to file ’fileName’with error number errorNumber

Explanation: CICS was unable to flush symptomrecord from an output buffer to file ’fileName’.


User response: Ensure that the file system for file’fileName’ is not full. For further information check theoperating system documentation for a description oferror number errorNumber.

Destination:

stderr

ERZ057023I Transaction ’transId’ timed out onterminal ’termId’ due to a prolongedtransient error condition

Explanation: CICS has encountered an error conditionthat was supposed to be temporary. After severalretries of the operation the condition has not cleared.


User response: Examine following messages todetermine the cause of the error.

Destination:

console.msg, stderr

ERZ057024I Utility/program timed out due to aprolonged transient error condition

Explanation: CICS has encountered an error conditionthat was supposed to be temporary. After severalretries of the operation the condition has not cleared.

System action: The utility/program is abnormallyterminated.

User response: Examine following messages to

determine the cause of the error.

Destination:

stderr

ERZ057025W Failed to open the symptom record file’fileName’ with error number errorNumber

Explanation: CICS was unable to open the file towhich symptom records are written.

System action: CICS attempts to write the symptomrecord to standard error. Another attempt is made toopen the file the next time that a symptom record hasto be written.

User response: Ensure that file ’fileName’ exists andthat it has the correct access permissions. Check theoperating system documentation for a description oferror number errorNumber.

Destination:

stderr

ERZ057026W Failed writing symptom record to file’fileName’ with error number errorNumber

Explanation: CICS was unable to perform a bufferedwrite to file ’fileName’, where symptom records arewritten.


User response: Ensure that the file system for file’fileName’ is not full. For further information check theoperating system documentation for a description oferror number errorNumber.

Destination:

stderr

ERZ057027E Not enough memory available to savelocale

Explanation: CICS was unable to obtain regionmemory while attempting to save locale information.


User response: Increase the size of the Region poolmemory, as defined in the Region Definitions (RD), byoverriding the attribute in the region startup commandline and restart the region.

Destination:

stderr

ERZ057021E • ERZ057027E


ERZ057028W Failed to duplicate standard error witherror number errorNumber

Explanation: CICS was unable to obtain a duplicatefile descriptor or a file stream for the duplicatestandard error (stderr).

System action: CICS continues, using unduplicatedstandard error. If Animator is used CICS messageswritten to standard error are displayed on theAnimator panel and are not written to the stderrdestination.

User response: Refer to the operating systemdocumentation for a description of error numbererrorNumber. Correct the problem and restart the region.

Destination:

stderr

ERZ057029E Failed to open message catalog

Explanation: CICS was unable to open the messagecatalog cics.cat.

System action: If the catalog was being opened for atask, the task is terminated. If it was being opened for aregion, the region is abnormally terminated.

User response: Check that there is a CICS messagecatalog in a directory defined by the environmentvariable NLSPATH and the the user cics has permissionto read it. On UNIX, also check that the environmentvariable LANG is correct.

Destination:

console.msg, CSMT

ERZ057030E Failed to set locale LC_ALL to’localeName’

Explanation: CICS was unable to change locale.

System action: The region or the task is terminated.

User response: The locale is taken from theenvironment of the user that started the region orsubmitted the transaction request. The locale categorieswithin the locale can be modified by a number ofenvironment variables. Ensure these environmentvariables contain a valid locale for the machine wherethe operation is to be done and then retry.

Destination:

console.msg, CSMT

ERZ057031E Unable to format message ’messageId’

Explanation: CICS retrieved the named message fromthe message catalog but was unable to format themessage. It is likely that the message catalog beingused is out of date. Note that the Message SequenceNumber (MSN) associated with this message

(ERZ5731E) is the MSN for the original message thatCICS failed to format.


User response: Reinstall the CICS Machine ReadableInformation (MRI) for your language. If the problempersists, consult your support organization: there is amismatch between the message as defined in themessage catalog and the variable-replacementarguments supplied in the CICS code.

Destination:

console.msg

ERZ057032E Buffer OVERFLOW while processinginternal text - supplied size lengthu,required size sizeu

Explanation: CICS message processing facility hasoverwritten a buffer.

System action: CICS abnormally terminates thecurrent execution environment: in the runtime, thewhole region is terminated; elsewhere, the currentprocess is terminated.

User response: The message catalog is possiblycorrupted. Reinstall the CICS Machine ReadableInformation (MRI) for your language. If the problempersists, contact your support organization.

Destination:

console.msg, stderr

ERZ057033E CICS is unable to attach shared memory.

Explanation: CICS made an unsuccessful attempt toattach shared memory. An earlier message providesmore details.


User response: Restart the region. If the problemrecurs, restart the region again with Monitoringdisabled. If the problem persists, contact your supportorganization.

Destination:

CSMT

ERZ057034I Previous console file is **consoleFileName **

Explanation: CICS has started a new console file. Theprevious console file has exceeded the limit set in theRegion Definition (RD) attribute MaxConsoleSize. IfMaxConsoleSize is set to 0, then the region starts a newconsole only at region start time. Otherwise the regionstarts a new console when MaxConsoleSize is exceeded.


ERZ057028W • ERZ057034I



Destination:

console.msg

ERZ057035I Next console file is ** consoleFileName **

Explanation: CICS has started a new console file. Theprevious console file has exceeded the limit set in theRegion Definition (RD) attribute MaxConsoleSize. IfMaxConsoleSize is set to 0, then the region starts a newconsole only at region start time. Otherwise the regionstarts a new console when MaxConsoleSize is exceeded.



Destination:

console.msg

ERZ057036E Failed to start new console ’newFileName’file, continuing to use ’oldFileName’

Explanation: CICS has failed to start a new consolefile when the Region Definition (RD) attributeMaxConsoleSize was exceeded.

System action: CICS continues to use the existingconsole file. CICS tries to start a new console file whena further MaxConsoleSize characters are written to theconsole file.

User response: Check the file system where theconsole files are stored is not full.

Destination:

console.msg

ERZ058999E COBDIR must be set in the shellenvironment before cicsanimsrv is run.

Explanation: COBDIR environment variable was notset in the shell..

System action: cicsanimsrv cannot continue.

User response: Set the COBDIR environment variableto the directory in which COBOL is installed, thenrerun cicsanimsrv.

Destination:

console

ERZ060001E CICS did not allocate a shared memorysegment for the CICS Region Pool. Theerror number returned was errorNumber

Explanation: CICS common storage controlinitialization received an error from the operatingsystem while trying to initialize a storage pool for useby the region. The error occurred while acquiringshared memory for use as the CICS Region Pool.

System action: CICS does not initialize the requestedstorage pool for use. CICS abnormally terminates theregion.

User response: A symptom record is written to thesymrecs file for this error. Use the PRCS error codeinformation in the symptom record and operatingsystem documentation to identify the problem. Sharedmemory segments must be sized between the systemimposed limits. CICS defines the pool size it requires inthe MaxRegionPool attribute of the Region Definitions.The size of pool defined must be less than themaximum shared memory segment size imposed bythe system as CICS requires private storage areas ontop of the space defined for the Region Pool Anotherpossible cause is that operating system has exhaustedits system wide limit on memory. On UNIX, use theoperating system tool ipcs -m to investigate this causeand reduce the overall number of shared memorysegments used by your system.

Destination:

console.msg

ERZ060002E CICS did not allocate a shared memorysegment for the CICS Shared Pool. Theerror number returned was errorNumber

Explanation: CICS common storage controlinitialization received an error from the operatingsystem while trying to initialize a storage pool for useby the region. The error occurred while acquiringshared memory for use as the CICS Task Shared Pool.

System action: CICS does not initialize the requestedstorage pool for use. CICS abnormally terminates theregion.

User response: A symptom record is written to thesymrecs file for this error. Use the PRCS error codeinformation in the symptom record and operatingsystem documentation to identify the problem. Sharedmemory segments must be sized between the systemimposed limits. CICS defines the pool size it requires inthe MaxTSHPool attribute of the Region Definitions.The size of pool defined must be less than themaximum shared memory segment size imposed bythe system as CICS requires private storage areas ontop of the space defined for the Pool Another possiblecause is that operating system has exhausted its systemwide limit on memory. On UNIX, use the operatingsystem tool ipcs -m to investigate this cause and reducethe overall number of shared memory segments usedby your system.

Destination:

console.msg

ERZ057035I • ERZ060002E


ERZ060003E CICS did not allocate memory for aCICS Task Private Pool

Explanation: CICS common storage controlinitialization received an error from the operatingsystem sbrk system call while trying to initialize astorage pool for use by an Application Server or theregion. The error occurred while acquiring storage foruse as a CICS Task Private Pool.

System action: CICS does not initialize the requestedstorage pool for use. If an Application Server made therequest, the task is terminated abnormally. If a CICScontrol process issued the request, CICS abnormallyterminates the region.

User response: A symptom record is written to thesymrecs file for this error. Use the PRCS error codeinformation in the symptom record and operatingsystem documentation to identify the problem withsbrk.

Destination:

console.msg

ERZ060004E CICS did not initialize a storage poolfor use

Explanation: CICS received an error code from thememory management system software. This hasprevented a storage pool from being initialized.

System action: CICS does not initialize a storage pool.Other console messages indicate which storage pool isin error. CICS abnormally terminates the ApplicationServer or region depending on whether the condition isdetected in an Application Server process or in a CICScontrol process.


Destination:

console.msg

ERZ060005E CICS did not complete a storage controlrequest

Explanation: CICS received an error code from thememory management system software. This causes astorage allocate, deallocate or reallocate request to fail.

System action: CICS does not complete the storagerequest. The subsequent state of an Application Serveror CICS control process is defined by the code thatcalled CICS storage control. Other messages at theconsole or CSMT indicate the state of the system ortransaction.


Destination:

console.msg

ERZ060006E CICS did not initialize a storage pool.There are no more storage pool handlesavailable

Explanation: All CICS storage pools are active andCICS cannot initialize any more storage pools for useby the region.

System action: CICS does not satisfy the storageinitialization request. The requesting task is terminatedabnormally. CICS possibly abnormally terminate theregion.

User response: This condition indicates a CICSsoftware error. Contact your support organization.

Destination:

console.msg

ERZ060007W CICS did not remove a shared memorysegment from the system

Explanation: CICS received an error from anoperating system call. The error occurred whileterminating the Region Pool or Task Shared Poolduring a region shutdown.

System action: The CICS region shutdown continues.

User response: A symptom record is written to thesymrecs file for this error. Use the PRCS error codeinformation in the symptom record and operatingsystem documentation to identify the problem. One ormore of the shared memory segments used by CICS arepossibly still defined to the operating system. On UNIXuse the operating system commands ipcs -m and ipcrmto determine the shared memory identity to remove.

Destination:

console.msg

ERZ060008E CICS did not connect to the sharedmemory segment containing the CICSRegion Pool

Explanation: CICS received an error from anoperating system call. The error occurred whileattaching the Region Pool shared memory segment tothe calling task.


User response:

A symptom record is written to the symrecs file for thiserror. Use the PRCS error code information in thesymptom record and operating system documentationto identify the problem. The probable cause is thatother software is using the attach address used by CICSfor the Region Pool shared memory segment. Thisusage interferes with the operation of CICS. If this isthe case change the configuration of the other softwareproduct to prevent interference with the use of this

ERZ060003E • ERZ060008E


address by CICS. The address used for the Region Poolis given by message ERZ4842I output to console.msgduring region start up. Another possible reason for thiserror is that the permissions associated with the sharedmemory segment were modified by another program.On UNIX use the operating system command ipcs -mto examine the permissions of shared memorysegments. On UNIX the shared memory segments usedby CICS need to have the following permissions:

MODE --rw------- OWNER cics GROUP cics

Destination:

console.msg

ERZ060009E CICS did not connect to the sharedmemory segment containing the CICSTask Shared Pool

Explanation: CICS received an error from anoperating system call. The error occurred whileattaching the Task Shared Pool shared memory segmentto the calling task.


User response:

A symptom record is written to the symrecs file for thiserror. Use the PRCS error code information in thesymptom record and operating system documentationto identify the problem. The probable cause is thatother software is using the attach address used by CICSfor the Task Shared Pool shared memory segment. Thisusage interferes with the operation of CICS. If this isthe case change the configuration of the other softwareproduct to prevent interference with the use of thisaddress by CICS. The address used for the Task SharedPool is given by message ERZ4843I output toconsole.msg during region start up. Another possiblereason for this error is that the permissions associatedwith the shared memory segment were modified byanother program. On UNIX use the operating systemcommand ipcs -m to examine the permissions ofshared memory segments. On UNIX the sharedmemory segments used by CICS need to have thefollowing permissions:

MODE --rw------- OWNER cics GROUP cics

Destination:

console.msg

ERZ060010W Guard Page create failed for Taskprivate pool, reason code errorNumber

Explanation: CICS received an warning from anoperating system call. The warning occurred whileattempting to create guard page.

System action: Region continues without guard pagearound Task Private pool.

User response: Investigate the reason code to checkwhy the Guard Page failed.

Destination:

console.msg

ERZ061001I Automatic Transaction Initiation (ATI)request for remote system ’sysId’ hasbeen locally queued

Explanation: The Automatic Transaction Initiation(ATI) you requested was not able to be started on theremote system and has therefore been successfullyadded to the local queue of ATIs ready to be triedagain.

System action: The ATI request is locally queued.

User response: Try to get the remote system requiredback into operation.

Destination:

CSMT

ERZ061002I A locally queued Automatic TransactionInitiation (ATI) request has beentransmitted to remote system ’sysId’

Explanation: An Automatic Transaction Initiation(ATI) request that was locally queued has beensuccessfully transmitted to the remote system and hasbeen removed from the local queue.

System action: The ATI request is removed from thelocal queue.

User response: None

Destination:

CSMT

ERZ061003I CICS starting to purge locally queuedAutomatic Transaction Initiation (ATI)requests

Explanation: The CICS-private transaction responsiblefor purging Automatic Transaction Initiation (ATI)requests from the local queue has begun.

System action: CICS continues to purge those ATIsthat are in the local queue that exceed theCARPDelayHours period as defined in the region’sRegion Definition (RD).

User response: None

Destination:

CSMT

ERZ060009E • ERZ061003I


ERZ061004I CICS completed purging locally queuedAutomatic Transaction Initiation (ATI)requests

Explanation: The CICS-private transaction responsiblefor purging Automatic Transaction Initiation (ATI)requests from the local queue has finished.

System action: The CICS-private transactionresponsible for purging Automatic TransactionInitiation (ATI) requests from the local queueterminates.

User response: None

Destination:

CSMT

ERZ061005E Unsuccessful memory allocation toqueue Automatic Transaction Initiation(ATI) request for remote system ’sysId’

Explanation: CICS was attempting to obtain memoryfrom the Task-Private Pool for local queueing of anAutomatic Transaction Initiation (ATI) request, butinsufficient memory was available.

System action: CICS does not queue the ATI requestand a SYSIDERR is returned to the caller. If any of theATI requests are PROTECTED then the followingsyncpoint is rolled back.

User response: Refer to any previous messagesindicating why the Task-Private storage was not able tobe allocated. You can reduce the amount ofTask-Private Storage used by your transaction byreducing your use of GETMAIN.

Destination:

CSMT

ERZ061006I CICS has purged a locally queuedAutomatic Transaction Initiation (ATI)request for sysid ’sysId’

Explanation: An Automatic Transaction Initiation(ATI) request has been removed from the local ATIqueue because the ATI request has exceeded the purgedelay time limit defined by the CARPDelayHoursattribute in the region’s Region Definition (RD).

System action: The ATI request is deleted from theATI local queue.

User response: Try to get the remote system on lineand re-submit the ATI.

Destination:

CSMT

ERZ061007W The CICS-private transaction forpurging Automatic TransactionInitiation (ATI) requests is alreadyrunning

Explanation: An attempt was made to execute theCICS-private transaction for purging AutomaticTransaction Initiation (ATI) requests from the localqueue, when the CICS-private transaction is alreadyrunning.

System action: The CICS-private transaction requestedlast terminates without doing anything.

User response: None

Destination:

CSMT

ERZ061008W The CICS-private transaction fortransmitting locally queued AutomaticTransaction Initiation (ATI) requests isalready running

Explanation: An attempt was made to execute theCICS-private transaction for transmitting AutomaticTransaction Initiation (ATI) locally queued requests,when the CICS-private transaction is already running.

System action: The CICS-private transaction requestedlast terminates without doing anything.

User response: None

Destination:

CSMT

ERZ061009E CICS detected an inconsistent signaturein local queue entry - expected’expectedSignature’

Explanation: CICS detected an error with anAutomatic Transaction Initiation (ATI) entry in the localqueueing file. This is possibly true if the file serverentry has been corrupted or if there is a record in thelocal queueing file that is not a local queueing request.

System action: CICS ignores the entry and deletes theentry from the file.

User response: Ensure that the files specified for localqueueing in the Region Definitions (RD) are uniqueand that records are not being written to the localqueueing files by other means.

Destination:

CSMT

ERZ061004I • ERZ061009E


ERZ061010W Unsuccessful memory allocation toexecute CICS-private transaction totransmit locally queued AutomaticTransaction Initiation (ATI) requests

Explanation: The CICS-private transaction wasattempting to obtain memory for transmitting locallyqueued Automatic Transaction Initiation (ATI) requests.Insufficient Task-Private memory was available.

System action: The CICS-private transaction does nottransmit an ATI and reschedules itself to be executed ata later time.


Destination:

CSMT

ERZ061011E CICS was unsuccessful in reading localqueueing information - local queueingis not available

Explanation: The CICS local queueing facilityencountered an error condition when accessing a fileserver file.

System action: The CICS local queueing facility forAutomatic Transaction Initiation (ATI) requests are notavailable while the problem with the file serverpersists. Therefore no new requests can be queued andalready queued requests remain queued until theproblem is resolved.

User response: Messages are logged before thismessage giving specific details of the failure. Follow theprocedures for the preceding message(s).

Destination:

CSMT

ERZ061013E Unsuccessful open of local queue file’serverName’/’fileName’ index ’indexName’

Explanation: The CICS local queueing facility wasunable to open the file server file ’fileName’ on theserver ’serverName’.

System action: CICS local queueing facility forAutomatic Transaction Initiation (ATI) requests are notavailable. SYSIDERR is returned to your program if anattempt to locally queue an ATI is made. It is alsopossible that you are using an unsupported protectionlevel.

User response: Check that the file server ’serverName’is running and that the resource definitions for the’fileName’ and ’indexName’ are consistent with theconfiguration of the file server.

Destination:

CSMT

ERZ061015E Unsuccessful attempt to local queueAutomatic Transaction Initiation (ATI).Too many ATI requests are queued.

Explanation: CICS was unable to local queue anAutomatic Transaction Initiation (ATI) request becausethe limit of 9999 queued ATI’s has been reached.

System action: CICS does not local queue the ATIrequest and returns to the caller a SYSIDERR error.

User response: Do not use the CICS local queueingfacility until other ATI requests are function shippedallowing for further requests to be queued. If thismessage keeps reappearing then contact your supportorganization.

Destination:

CSMT

ERZ061016I CICS is vetoing a syncpoint for a localqueue Automatic Transaction Initiation(ATI) request since a START PROTECTNOCHECK was unsuccessful for thisLogical Unit of Work (LUW)

Explanation: CICS was unsuccessful at locallyqueueing a START PROTECT NOCHECK AutomaticTransaction Initiation (ATI) request and has set up abackout veto for the Logical Unit of Work (LUW).

System action: The syncpoint does not succeed andthe ATI is not queued. A previous message indicateswhy the ATI was not queued.

User response: See the previous message to see whythe ATI was not queued and thus veto the syncpoint.

Destination:

CSMT

ERZ061017E Abnormal termination A61A:Unsuccessful register of local queueveto

Explanation: CICS was attempting to obtain memoryfor vetoing a protected Automatic Transaction Initiation(ATI) request, from the Task-Private Pool. Insufficientmemory was available.

System action: The transaction abnormally terminateswith the A61A code. The ATI request is not locallyqueued.

User response: Refer to any previous messagesindicating why the Task-Private storage was not able tobe be allocated. You can reduce the amount ofTask-Private Storage used by your transaction byreducing your use of GETMAIN.

ERZ061010W • ERZ061017E


Destination:

CSMT

ERZ061018E Local Queuing file server file name’fileName’ is incorrectly configured

Explanation: The file server configuration for the localqueueing file ’fileName’ has an incorrect file or keydefinition. CICS cannot use it for local queueingpurposes.

System action: The CICS local queueing facility doesnot work. Any Automatic Transaction Initiation (ATI)requests that go to local queueing are not queued.

User response: Correct the configuration of the file’fileName’. You can do this by reconfiguring your fileserver for the region. Local queueing becomes availableafter you do this.

Destination:

CSMT

ERZ061019W A START NOCHECK request fortransaction ’transId’ could not be sent tosystem ’sysId’

Explanation: A START NOCHECK request has beenmade for system ’sysId’, but the remote system is notavailable and the transaction cannot be locally queued.


User response: Refer to the CICS message files forfurther information on why the START was not able tobe sent. If you do not require START to be locallyqueued, you can ignore this message. If you are using alocal Transaction Definition (TD) of a remotetransaction, consider defining the LocalQ attribute ofthe TD to ″yes″. If you are using the SYSID option,consider creating a local TD entry for the remotetransaction. If it is important that your transaction isnotified immediately of delivery of the request then donot use the NOCHECK option.

Destination:

CSMT

ERZ061020E Unsuccessful attempt to startCICS-private local queueing transaction’transId’

Explanation: CICS detected that the CICS-privatetransaction ’transId’ was not defined in the region’sdatabase.

System action: The Automatic Transaction Initiation(ATI) request is not locally queued.

User response: Ensure that the CICS-privatetransaction definitions are the same as the defaultdefinitions for the CICS-private transaction and restartthe region.

Destination:

CSMT

ERZ061021E The CICS-private transaction ’transId’must not be defined as a remotetransaction

Explanation: The CICS-private transaction ’transId’ hasbeen defined as being remote in the region database.This MUST NOT be the case.

System action: The Automatic Transaction Initiation(ATI) request is not locally queued. Local queueing forAutomatic Transaction Initiation (ATI) requests is notavailable.

User response: Ensure that the CICS-privatetransaction definitions are the same as the defaultdefinitions for the CICS-private transaction and restartthe region.

Destination:

CSMT

ERZ061022E Unsuccessful memory allocation forstarting CICS-private transaction’transId’

Explanation: CICS was attempting to obtain memoryto schedule the CICS-private transaction ’transId’.Insufficient Task-Private memory pool was available.

System action: The Automatic Transaction Initiation(ATI) request is not locally queued. Local queueing forAutomatic Transaction Initiation (ATI) requests are notavailable.


Destination:

CSMT

ERZ061023E CICS Local Queueing (LQ) facility iscurrently not available

Explanation: CICS-private transaction for localqueueing cannot access the file server local queue filesbecause the server is not there or not available.

System action: The Automatic Transaction Initiation(ATI) request are not locally queued. Local queueingfor Automatic Transaction Initiation (ATI) requests arenot available.

User response: Restart the file server.

Destination:

CSMT

ERZ061018E • ERZ061023E


ERZ061024E Abnormal termination AKCS; Write toLocal Queue (LQ) file timed out

Explanation: CICS has timed out while attempting towrite to a local queue file.

System action: The Automatic Transaction Initiation(ATI) request has failed to be locally queued. CICSabnormally terminates the transaction with code AKCSin order to avoid a potential deadlock situation.

User response: Increase the value of theDeadLockTimeout attribute in the TransactionDefinitions (TD) entry or investigate which transactionhas taken the most space in the filesystem being usedby the local queue.

Destination:

CSMT

ERZ061025E CICS-private transaction was unable topurge a locally queued AutomaticTransaction Initiation (ATI) request forremote sysid ’sysId’

Explanation: An Automatic Transaction Initiation(ATI) ATI request was transmitted, but the request wasnot removed from the local queue file record.

System action: The ATI request has been sent to theremote system, but has not been deleted from the localqueue file. A further attempt can be made tore-transmit the request.

User response: Check that the file server is running.

Destination:

CSMT

ERZ061026I Processing local queues that correspondto asynchronous processing requests ...

Explanation: This is an informational message whichis produced when a CICS region is started. Thismessage is produced before CICS attempts to find anyoutstanding locally queued transactions.


User response: None

Destination:

console.msg

ERZ061027I Local queues have been processed

Explanation: This is an informational message whichis produced when a CICS region is started. Thismessage is produced after CICS has attempted to findany outstanding locally queued transactions.


User response: None

Destination:

console.msg





Destination:

console

ERZ062002E Abnormal termination ABMB. Thecursor position ’cursorPosition’ is invalidfor this screen size ’screenSize’.

Explanation: The cursor position requested by aSEND TEXT, SEND MAP or SEND CONTROLcommand is outside the screen area of the terminalrunning the transaction.

System action: CICS terminates the transaction withabend code ABMB.

User response: If you are using a map with a terminalsize greater than one supported by CICS, correct andreinstall your map. If this problem is caused by aSEND CONTROL command, correct the program andrerun your transaction.

Destination:

CSMT

ERZ062003E Abnormal termination ABMI. Map’mapName’ in mapset ’mapSetName’ is notan input map.

Explanation: The map specified on an EXEC CICSRECEIVE command was not of type IN or INOUT.

System action: CICS terminates the transaction withabend code ABMI.

User response: Define the map as an IN or INOUTmap, or use a different map.

Destination:

CSMT

ERZ061024E • ERZ062003E


ERZ062004E Abnormal termination ABMO. Map’mapName’ in mapset ’mapSetName’ is notan output map.

Explanation: The map specified on an EXEC CICSSEND command was not of type OUT or INOUT.

System action: CICS terminates the transaction withabend code ABMO.

User response: Define the map as an OUT or INOUTmap, or use a different map.

Destination:

CSMT

ERZ062005E Abnormal termination ASRA. Addressis out of bounds.

Explanation: A program passed a NULL address toCICS.


User response: Correct the program that passes theNULL address.

Destination:

CSMT

ERZ062006E Abnormal termination APCT. Cannotload mapset ’mapSetName’.

Explanation: CICS cannot locate the mapset specifiedby a Basic Mapping Support (BMS) command.

System action: CICS terminates the transaction withabend code APCT.

User response: Check the program to ensure that themapset name is spelled correctly. If so, ensure that themapset is defined in the Program Definitions (PD) andexists in the region database.

Destination:

CSMT

ERZ062007E Abnormal termination ABM3. BasicMapping Support (BMS) operationrequested by a non-terminal transaction.

Explanation: A non-terminal transaction, such as anAutomatic Transaction Initiation (ATI) transaction withno terminal specification, requested a BMS operation.

System action: CICS terminates the transaction withabend code ABM3.

User response: Either remove the BMS commandsfrom the transaction, or initiate the transaction from aterminal.

Destination:

CSMT

ERZ062010E Abnormal termination A62C. BasicMapping Support (BMS) operationrequested for a non BMS terminal type.

Explanation: CICS was requested to perform a BMSmap operation on a terminal that does not supportBMS operations.

System action: CICS terminates the transaction withabend code A62C.

User response: Run the transaction on a terminal thatdoes support BMS operations.

Destination:

CSMT

ERZ062012E Abnormal termination U6201. Errorfreeing the terminal i/o area (TIOA).

Explanation: CICS cannot free the memory allocatedfor the terminal i/o area in the Task Shared Pool.


User response: Check your program to see that it isnot incorrectly writing to, or freeing memory in theTask Shared Pool. When you have validated yourprogram, rerun the transaction. If the problem persists,it is possibly due to some other transaction writing tomemory in the Task Shared Pool.

Destination:

console.msg

ERZ062013E CICS self consistency checking forTIOA signature cannot be carried out;the TIOA address in the TCA addressTCAaddress is null.″

Explanation: Self-consistency checking detected anerror in the TCA. This message can possibly indicate aserious inconsistency in the CICS system.

System action: CICS self consistency checkingcontinues.

User response: It is advisable to restart the region andmonitor any unsuccessful self consistency checks. If theerror persists contact your support organization.

Destination:

console.msg

ERZ062014E Unsuccessful self consistency check forthe mapset at address ’mapSetAddress’:either it is NULL or it is corrupt.

Explanation: The data structure for the mapset at thesupplied address is incorrectly formatted.

ERZ062004E • ERZ062014E


System action: CICS self consistency checkingcontinues.

User response: Verify that the mapset was compiledwith a version of cicsmap compatible with the CICSregion and check that the PD PathName points to avalid mapset.

Destination:

console.msg

ERZ062015E Terminates with abend code A62F.Unable to allocate storage for a terminaloperation.

Explanation: CICS cannot allocate sufficient storage inone of the Task Private, Task Shared or Region Pools.

System action: CICS terminates the transaction withabend code A62F.

User response: Try running the transaction again. Ifthe condition occurs again, it is possibly due to a heavyload on CICS or because some transaction is using alarge amount of memory.

Destination:

CSMT

ERZ062016E Terminates with abend code A62G.CICS is unable to update the principalfacility database record.

Explanation: CICS was unable to update the databaserecord for the principal facility. This is likely to becaused by an inconsistency in the CICS internal datastructures.

System action: CICS terminates the transaction withabend code A62G.


Destination:

CSMT

ERZ062017E Abnormal termination A62H. Unable toregister function for syncpointing.

Explanation: CICS is unable to register a function tobe called at a syncpoint

System action: CICS terminates the transaction withabend code A62H.

User response: Examine surrounding messages forfurther information about this problem.

Destination:

CSMT

ERZ062019E Abnormal termination A62J. Cannotconvert a field in the Basic MappingSupport (BMS) map to upper case.

Explanation: CICS cannot convert data in Case=Mixedfield in a BMS map to upper case.

System action: CICS terminates the transaction withabend code A62J.

User response: Correct the data that the transactionwas trying to convert.

Destination:

CSMT

ERZ062020E CICS self consistency checking hasdetected an invalid TIOA signature;expected ’expectedSignature’ found’actualSignature’ in the TIOA atTIOAaddress in the TCA at TCAaddress.

Explanation: The signature of the terminal i/o area(TIOA) in the Region-Pool is corrupt. This message canpossibly indicate a serious inconsistency in the CICSsystem.


User response: It is advisable to restart the region andmonitor any unsuccessful self consistency checks. If theerror persists contact your support organization.

Destination:

console.msg

ERZ062021E A terminal error has occurred during aBMS operation.

Explanation: The transaction was unable tocommunicate with the terminal.

System action: The transaction is terminated withabend code ATNI.

User response: Check that the emulator process andthe application servers are still running. Then tryrunning the transaction again.

Destination:

CSMT

ERZ062024E Abnormal termination ABM0. Cannotlocate map ’mapName’ in the mapset’mapSetName’.

Explanation: CICS cannot locate the given map in thesupplied mapset.

System action: CICS terminates the transaction withabend code ABM0.

User response: Check the mapset to see that it was

ERZ062015E • ERZ062024E


properly defined and that it contains the expected map.

Destination:

CSMT

ERZ062025E Mapset has an invalid format.

Explanation: A mapset has an incorrect format andcannot be loaded.

System action: CICS terminates the transaction withabend code ABMM.

User response: Check the mapset entry in theprogram definitions(PD). Ensure that the file in the PDPathName is a properly generated mapset.

Destination:

CSMT

ERZ062026E Mapset generated with incorrect versionof cicsmap.

Explanation: A mapset was generated with a versionof cicsmap that differs from the version of CICS.


User response: Ensure that the version of cicsmapprogram matches the version of CICS. Recompile andinstall the mapset using the correct version of cicsmap

Destination:

CSMT

ERZ062027E Abnormal termination ABMM. Invalidmapset ’mapSetName’ has been specified.

Explanation: The program specified an invalidmapset.


User response: Verify that the mapset was compiledwith a version of cicsmap compatible with the CICSregion and check that the PD PathName points to avalid mapset.

Destination:

CSMT

ERZ062028E Abnormal termination ASRA. Attemptto read into Region Pool storage.

Explanation: The transaction attempted a RECEIVE orCONVERSE operation using an INTO buffer thatspecifies an address in Region Pool memory.


User response: Check that the address specified in the

INTO option refers to memory accessible by theprogram and that the LENGTH or FLENGTH optionsdo not overrun the end of that memory.

Destination:

CSMT

ERZ063001E No SNA Listener Definition could beaccessed on starting SNA listener

Explanation: The SNA listener has attempted to locatea SNA Listener Definition (LD) entry but one waseither not available or was unable to be accessed.

System action: CICS does not accept incoming localSNA intersystem requests.

User response: Check that there is a SNA LD entrydefined in your region and that there is aLocalLUName defined in the Region Definition (RD)entry.

Destination:

console.msg

ERZ063002E Unable to schedule incomingintersystem request for transaction’transId’ from system ’name’ due tocommunications errorprimaryCode/secondaryCode

Explanation: CICS is unable to schedule thetransaction transId requested by remote system name, sothe request was rejected. The reason the request wasunable to be scheduled is described byprimaryCode/secondaryCode. These communications errorcodes are explained in the TXSeries Infocenter.

System action: The incoming intersystem request isabnormally terminated.

User response: Read the description for the error codeprimaryCode/secondaryCode in the TXSeries Infocenterand follow the instructions for the error code.

Destination:

console.msg

ERZ063003E Unable to schedule incomingintersystem request for transaction’transId’ due to communications errorprimaryCode/secondaryCode

Explanation: CICS is unable to schedule thetransaction transId, so the request was rejected. Thereason the request was unable to be scheduled isdescribed by primaryCode/secondaryCode. Thesecommunications error codes are explained in theTXSeries Infocenter.

System action: The incoming intersystem request isabnormally terminated.

ERZ062025E • ERZ063003E


User response: Read the description for the error codeprimaryCode/secondaryCode in the TXSeries Infocenterand follow the instructions for the error code.

Destination:

console.msg

ERZ063004E Unsuccessful Region Pool memoryallocation when scheduling transaction’transId’ from ’applId’

Explanation: CICS was attempting to obtain sufficientRegion Pool memory to schedule transaction ’transId’received by InterSystem Communication (ISC) requestfrom ’applId’. Insufficient Region Pool memeory wasavailable.

System action: The incoming conversation isabnormally terminated.

User response: You can increase the size of the RegionPool available by restarting the region and overridingthe MaxRegionPool attribute, with a larger value, onthe command line.

Destination:

console.msg

ERZ063005E Unsuccessful attempt to start a listenerthread

Explanation: An attempt to start a listener thread wasunsuccessful. Threads are used within a SNA listenerprocess to handle incoming local SNA intersystemrequests. The most likely reason a thread fails to start isthat there is insufficient memory available in thesystem to start the thread.

System action: CICS can possibly not accept incomingintersystem requests using local SNA.

User response: Reduce the load of the system byrunning fewer programs. If the error occurred afterlistener startup consider resubmitting the intersystemrequest when the system is more lightly loaded.

Destination:

console.msg

ERZ063006I CICS listener ’listenerName’ process’cicssl’ started for local LU ’localLUname’

Explanation: The start of a ’cicssl’ listener process wassuccessful.

System action: CICS accepts InterSystemCommunication requests from other systems usinglocal SNA services.

User response: None

Destination:

console.msg

ERZ063007E CICS listener ’listenerName’ process’cicssl’ start was unsuccessful

Explanation: The start of a ’cicssl’ listener process thataccepts InterSystem Communication requests from localSNA services was unsuccessful. Earlier messages give areason for the unsuccessful start.

System action: CICS does not accept connectionrequests from local SNA services.

User response: Check earlier messages for a reasonwhy the listener process start was unsuccessful.

Destination:

console.msg

ERZ063008E Abnormal termination U6301 in listener’listenerName’: Exception ’exceptionText’caught

Explanation: CICS has detected an unexpected fatalexception in the local SNA listener process’listenerName’.

System action:

CICS terminates the local SNA listener process withabend code U6301. Incoming local SNA InterSystemCommunication (ISC) requests can possibly beterminated. Further system action is defined by theActionOnExit attribute for the Listener Definition ofthe failing SNA listener:

v The ActionOnExit attribute is not set or isend_region then the region is terminated.

v The ActionOnExit attribute is ignore, then the failureis ignored and the region continues running withoutthe SNA listener. CICS does not accept furtherconnection requests from local SNA services.

v The ActionOnExit attribute is restart, then the failingSNA listener is restarted.

User response: This is an internal problem in CICSthat cannot be caused by the user. If the problempersists, contact your support organization.

Destination:

console.msg

ERZ063010I The local SNA thread pool has beeninitialized with a threshold of threshold

Explanation: The local SNA thread pool is located inthe CICS local SNA listener process (cicssl). It is agroup of threads used to issue SNA requests on behalfof the CICS application servers. The number of threadsin this pool is controlled by theCICS_SNA_THREAD_POOL_SIZE environmentvariable, which has a default value of 10, a minimumvalue of 6, and a maximum value of 200.


ERZ063004E • ERZ063010I



Destination:

console.msg

ERZ063011I The local SNA thread pool is nowempty

Explanation: The local SNA thread pool is located inthe CICS local SNA listener process (cicssl). It is agroup of threads used to issue SNA requests on behalfof the CICS application servers. The number of threadsin this pool has now dropped to zero. This means thelocal SNA listener no longer issues requests on behalfof application servers.



Destination:

console.msg

ERZ063012W The local SNA thread pool containsnumberOfThreads threads and is understress; the threshold is set to threshold

Explanation: The local SNA thread pool is located inthe CICS local SNA listener process (cicssl). It is agroup of threads used to issue SNA requests on behalfof the CICS application servers. CICS has detected thatall the threads in this pool are busy processing SNArequests. So the next application server to issue a SNArequest can possibly be delayed until one of these SNArequests completes. The threshold for the local SNAthread pool, threshold, is the number of threads CICSleaves running in the local SNA listener when thenumber of local SNA requests falls, leaving somethreads idle. It is controlled by theCICS_SNA_THREAD_POOL_SIZE environmentvariable. CICS_SNA_THREAD_POOL_SIZE can be setto a value between 6 and 200 inclusively. If thisenvironment variable is not set, the local SNA threadpool threshold defaults to 10.

System action: CICS creates additional threads tohandle the current work load. These threads terminatewhen the number of SNA requests subsides.

User response: If this message occurs frequently,consider increasing the size of the local SNA threadpool by setting CICS_SNA_THREAD_POOL_SIZE inyour region’s varDir/cics_regions/<region>/environment file. This enables CICS to keep a largerpool of threads ready to process local SNA requests.

Destination:

console.msg

ERZ063013E Unable to allocate Task-Private storagefor incoming intersystem request

Explanation: CICS has received a local SNAintersystem request but is unable to schedule theassociated transaction because the SNA listener process(cicssl) can not acquire sufficient Task-Private memory.


User response: If this problem occurs frequently, tryincreasing the size of the Task-Private pool. This isconfigured in the MaxTaskPrivatePool attribute of theRegion Definition (RD) entry.

Destination:

console.msg

ERZ064001E An invalid ECI request was receivedfrom terminal ’termId’

Explanation: The ECI mirror transaction was invokedincorrectly or the data received from the ECIapplication was invalid.

System action: The ECI request is terminated with anerror and the ECI mirror transaction terminates.

User response: This message can occur if the ECImirror transaction is invoked directly at a CICSterminal. If this message occurs when running an ECIapplication, contact your support organization.

Destination:

CSMT

ERZ064002E ECI Mirror Transaction ’transId’, Abend’abendCode’, at ’termId’

Explanation: The ECI mirror transaction ’transId’started from terminal ’termId’ was abnormallyterminated with code ’abendCode’.

System action: Any recoverable resources used by theECI mirror transaction are rolled back and thetransaction is terminated.

User response: ’abendCode’ is the abnormaltermination code that caused the ECI mirror transactionto be terminated. If the code is not one used forabnormal terminations initiated by CICS then it is auser code generated by an EXEC CICS ABENDABCODE (’abendCode’). Correct the problem andresubmit the ECI request.

Destination:

CSMT

ERZ063011I • ERZ064002E


ERZ064003E ECI Mirror Transaction ’transId’terminated with error ’abendCode’, at’termId’

Explanation: The ECI mirror transaction ’transId’started from terminal ’termId’ was terminated. Errorcode ’abendCode’ indicates the reason for termination.

System action: Any recoverable resources used by theECI mirror transaction are rolled back and thetransaction is terminated.

User response: ’abendCode’ is an ECI error codeindicating the reason for the termination of the ECImirror transaction. Refer to the CICS Family:Client/Server Programming manual for a description ofthese codes. Correct the problem and resubmit the ECIrequest.

Destination:

CSMT

ERZ065001E Usage: cicsmfmt [ -? ] fileName

Explanation: Either the arguments you supplied tocicsmfmt were incorrect, or you requested the cicsmfmtusage message via the -? option.

System action: The cicsmfmt program terminates.

User response: Retry your command using the correctsyntax, as shown in the message.

Destination:

stderr

ERZ065002E Unable to open the monitoring data file’fileName’

Explanation: The file you requested cicsmfmt toprocess was unable to be opened.


User response: Make sure that the fileName yourequested cicsmfmt to process was specified correctly,and ensure that it exists.

Destination:

stderr

ERZ065003E Monitoring data file ’fileName’ - readerror

Explanation: The cicsmfmt program detected an errorwhile it was reading from the monitoring data file thatyou specified.


User response: Ensure that you specified the name ofa valid monitoring file, and that you have sufficientpermission to read it. If the problem persists, check tosee whether CICS reported any errors when your

monitoring data file was generated. If errors werereported, resolve them and create a new monitoringfile, before retrying the cicsmfmt command.

Destination:

stderr

ERZ065004E Monitoring data file ’fileName’ -unexpected end of file

Explanation: The file that you specified ended with anincomplete monitoring record.


User response: Ensure that you specified the name ofa valid monitoring file. If the problem persists, check tosee whether CICS reported any errors when yourmonitoring data file was generated. If errors werereported, resolve them and create a new monitoringfile, before retrying the cicsmfmt command.

Destination:

stderr

ERZ065005E Monitoring data file ’fileName’ - invalidmonitoring queue

Explanation: The format of the file that you specifieddoes not match that expected of a monitoring transientdata queue.


User response: Ensure that you specified the name ofa valid monitoring file. If the problem persists, check tosee whether CICS reported any errors when yourmonitoring data file was generated. If errors werereported, resolve them and create a new monitoringfile, before retrying the cicsmfmt command.

Destination:

stderr

ERZ067014I Created directory ’dirName’

Explanation: This information is logged to verify thatthe directory named in the message was createdsuccessfully.

System action: Execution of the command continues.


Destination:

stderr

ERZ067018W Unable to add membership for currentidentity ’identity’ to cics_admin group.

Explanation: After the command has successfullycreated the groups required by CICS, the commandattempts to add the users identity to the membership

ERZ064003E • ERZ067018W


list of the group cics_admin. This failed.

System action: The command continues, although thisprincipal possibly lacks the authority to complete allremaining operations.

User response: Examine following error messages formore detailed information on what error occurred andhow to correct the error.

Destination:

stderr

ERZ067019E Unable to add membership for currentidentity ’identity’ to cics_admin group.

Explanation: After the command has successfullycreate the groups required by CICS, the commandattempts to add the users identity to the membershiplist of the group cics_admin. This failed.

System action: The command halts with a nonzeroreturn code.

User response: Examine following error messages formore detailed information on what error occurred andhow to correct the error.

Destination:

stderr

ERZ067020I Principal identity has been made amember of group cics_admin

Explanation: The current identity of the user wasmade a member of the group cics_admin.



Destination:

stderr

ERZ067026E The group ’groupName’ does not exist.Over-riding of ACLs is not permitted.

Explanation: You requested that the Access ControlLists (ACLs) on each directory be over-ridden.


User response: Retry this command without the -ooption, and when it completes adjust the ACLs for thedirectories that the command created to your needs,ensuring that the CDS servers have the necessaryACLs.

Destination:

stderr

ERZ067030E Request for numBytes bytes of memoryfailed.

Explanation: The program executing requested amemory allocation of the number of bytes in themessage from the operating system but the requestfailed.

System action: Execution of the command halts.

User response: If the system was heavily loaded, waituntil the load decreases and run the command again. Ifthe problem persists check for error messages in thesystem error log and console.

Destination:

stderr

ERZ067032I Usage: cicssetupclients [-?] | [-I] [-v] [-d| -m]

Explanation: You either asked for help on theparameters to cicssetupclients or else you specified aparameter incorrectly. The -? option requests this help.The -I option specifies that cicssetupclients is to ignoreany non fatal errors that it finds. The -v option specifiesthat cicssetupclients is to be verbose in outputting itsmessages. The -m option (only valid on AIX) specifiesthat cicssetupclients is only to perform steps necessaryto update /etc/inittab to run rc.cics on system restart.

System action: cicssetupclients prints this help andexits immediately.

User response: Run cicssetupclients with validoptions.

Destination:

stderr

ERZ067033E You must be logged in as root on UNIXor as Administrator on Windows NT torun this command

Explanation: You attempted to run cicssetupclientswhen logged in with insufficient authority. On UNIXyou must be logged on as root. On Windows NT youmust be logged on with a userid with Administratorand cicsgroup authority.

System action: cicssetupclients exits immediately.

User response: Log in correctly and retry thecommand.

Destination:

stderr

ERZ067019E • ERZ067033E


ERZ067038E Failed to install CICS kernel extensionsfor this machine

Explanation: The command attempted to install theCICS kernel extensions but an error occurred duringthis process.


User response: A preceding message was alreadylogged containing details of the specific error. Correctthe problem and reexecute the command.

Destination:

stderr

ERZ067039W Failed to install CICS kernel extensionsfor this machine

Explanation: The command attempted to install theCICS kernel extensions but an error occurred duringthis process.

System action: The command continues, but thekernel extensions for this machine are possibly in anunknown state.


Destination:

stderr

ERZ067040I Completed installation of CICS kernelextensions for this machine

Explanation: The installation of the CICS kernelextensions is completed for this machine. Any errorswere previously logged.



Destination:

stderr

ERZ067041E Failed to configure inittab toautomatically load kernel extensions

Explanation: The command attempted to update theinittab on your machine to automatically load the CICSkernel extensions when the machine is started but thisattempt failed.



Destination:

stderr

ERZ067042W Failed to configure inittab toautomatically load kernel extensions

Explanation: The command attempted to update theinittab on your machine to automatically load the CICSkernel extensions when the machine is started but thisattempt failed.

System action: The command continues, but theinittab entries associated with the CICS kernelextensions are possibly in an unknown state.


Destination:

stderr

ERZ067043I Completed updating inittab toautomatically load CICS kernelextensions

Explanation: The modification of inittab toautomatically load the CICS kernel extensions whenthis machine is started was completed. Any errors werepreviously logged.



Destination:

stderr

ERZ067044E Failed to generate machine unique id

Explanation: Each machine must have a unique idthat CICS uses to form a unique principal name for themachine. An error occurred and the unique id wasunable to be formed.


User response: An previous message was alreadylogged with details of the specific error that occurred.Use the earlier message to diagnose the problem andreexecute the command.

Destination:

stderr

ERZ067045I Generated unique machine id ’id’

Explanation: Each machine must have a unique idthat CICS uses to form a unique principal name for themachine.



ERZ067038E • ERZ067045I


Destination:

stderr

ERZ067047I Successfully deleted existing clientprincipal ’principal’

Explanation: The command detected that a clientprincipal already existed for this machine. In order toensure all information is recreated successfully, theexisting principal was successfully deleted. Thisprincipal is recreated in the next stage of the operation.



Destination:

stderr

ERZ067049E Failed to remove old keytab file’fileName’

Explanation: Each machine must have a keytab file tocontain the password for its client principal. Thecommand detected that this file already exists andtherefore attempted to remove the file before create anew one. This attempt failed.


User response: Verify that the file does indeed exists.If it does verify that the permission are such that thefile can be deleted by the command. If not eithermodify the permissions or remove the file manuallyand attempt to reexecute the command.

Destination:

stderr

ERZ067050I Successfully removed old keytab file’fileName’

Explanation: Each machine must have a keytab file tocontain the password for its client principal. Thecommand detected that this file already exists andtherefore removed the file before attempting to create anew one.



Destination:

stderr

ERZ067053E Failed to add keytab entry for principal’principal’ to file ’fileName’

Explanation: The command attempted to add an entryin the file identified for the identified principal. Thisattempt failed.


User response: A previous message containing aspecific error code was possibly already logged. Usethe message to diagnose why the command failed andreexecute the command.

Destination:

stderr

ERZ067054I Entry created in keytab file ’fileName’ forprincipal ’principal’

Explanation: An keytab entry was added to the file inthe message for the principal identified.



Destination:

stderr

ERZ067055E Failed to generate unique machineidentifier - invalid string (string)

Explanation: While creating an unique identifier forthe machine an error occurred and the command wasunable to parse the string generated. The invalid stringis logged in the message.


User response: Verify that all the required processesare running and available and that no other errorconditions exist on the machine and attempt toreexecute the command.

Destination:

stderr

ERZ067057W Failed to set permissions for keytab file’fileName’

Explanation: The command attempted to modify thesecurity permissions for the file identified in themessage but the attempt failed.

System action: The command continues, but thesecurity permissions for the file are left unchanged.

User response: Investigate the cause of the error andmanually change the permissions on the file to ensureit can only be read or modified by those with sufficientauthority.

Destination:

stderr

ERZ067047I • ERZ067057W


ERZ067058E Failed to set permissions for keytab file’fileName’

Explanation: The command attempted to modify thesecurity permissions for the file identified in themessage but the attempt failed.


User response: Investigate the cause of the error andcorrect it. If you wish to set the permissions manuallythen rerun the command specifying the ’IgnoreErrors’flag and then set the file permissions by hand.

Destination:

stderr

ERZ067059E Unable to get details for security group’cicsterm’



User response: The group ’cicsterm’ is normallycreated during product installation and configuration.The lack of the group can mean that some part ofconfiguration is incomplete. If you have deliberatelydeleted this security group then rerun this commandwith ’Ignore Errors’ options to bypass this error. If youdo this, then you are responsible for setting the securityon the keytab file.

Destination:

stderr




User response: The group ’cicsterm’ is normallycreated during product installation and configuration.The lack of the group can mean that some part ofconfiguration is incomplete. The command continues,but you are responsible for setting the protectioncontrols on the keytab file that is created.

Destination:

stderr

ERZ067061W Unable to modify the group ownershipfor the file ’fileName’


System action: The command continues, but thegroup ownership of the file is left unchanged andpossibly needs to be modified to enable clients accessto the file.

User response: Investigate the cause of the error andmanually change the group owner of the file to be thegroup ’cicsterm’.

Destination:

stderr

ERZ067062E Unable to modify the group ownershipfor the file ’fileName’



User response: Investigate the cause of the error andcorrect it. If you wish to set the group owner of the filemanually then rerun the command specifying the’IgnoreErrors’ flag and then set the file ownership byhand.

Destination:

stderr

ERZ067063W Unable to grant Account Controlpermission to group cics_admin

Explanation: The command attempted to give thegroup ’cics_admin’ sufficient privilage to add anddelete users, but this operation was unsuccessfull.


User response: If the problem is not corrected thatCICS commands , must be run as a user with sufficientprivilage to create accouts, such as ’celladmin’. Tocorrect the problem use the error code in the previouslylogged message to correct the faliure,

Destination:

stderr

ERZ067064I Granted Account Control permission togroup cics_admin

Explanation: The command successfully granted thegroup ’cics_admin’ permission to add and deleteprincipals. This permission is required when runningsome of the CICS administration commands.

ERZ067058E • ERZ067064I




Destination:

stderr

ERZ082006E Delete from file: ’filename’, index: ’index’was unsuccessful, SQL code:SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to delete a record from the specified file.

System action: CICS has not deleted the record fromthe file. The transaction continues.

User response: Check that the database is stillrunning. Refer to Database 2 or Oracle documentationfor further information concerning the error code.

Destination:

CSMT

ERZ082007E Update of file: ’filename’, index: ’index’was unsuccessful, SQL code:SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to update a record from the specified file.

System action: CICS has not updated the record fromthe file. The transaction continues.


Destination:

CSMT

ERZ082008E Attempt to obtain information for file:’filename’ and index: ’index’ from’database’ system table ’tablename’ wasunsuccessful, SQL Code: SQLErrorCode’SQLErrorText’

Explanation: A database error has occurred whileobtaining information concerning the specified file andindex.

System action: The transaction continues, but CICScan possibly generate further messages as a result ofthis error.

User response: Check that the database is stillrunning. Check that the resource definitions for file’filename’ and index ’index’ are consistent with theconfiguration of the database. Refer to Database 2 orOracle documentation for further informationconcerning the SQL error code.

Destination:

CSMT

ERZ082009E Abnormal termination A82M: Failed toobtain memory for file controlinformation.



User response: This is possibly a transitory problemthat can occur when CICS is heavily loaded. Resubmitthe transaction. If the problem persists, considerreconfiguring the size of the Region Pool and restartingCICS.

Destination:

CSMT

ERZ082011E Select range in file: ’filename’, index:’index’ was unsuccessful, SQL Code:SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to select records in the specified file andindex.



Destination:

CSMT

ERZ082016E Abnormal termination A82E: Failed toobtain the maximum current RBA forESDS file ’filename’, index ’index’; SQLcode: SQLErrorCode ’SQLErrorText’

Explanation: In certain situations, CICS must query anESDS file in order to obtain the current maximum RBAvalue. The operation to obtain this value wasunsuccessful for the reason indicated.



Destination:

CSMT

ERZ082020E Select position in file: ’filename’, index:’index’, for key: ’key’ was unsuccessful,SQL code: value ’SQLErrorCode’

Explanation: A database error has occurred when

ERZ082006E • ERZ082020E


attempting to select a record with the indicated keyvalue in the specified file.


User response: Check that the database is running.Refer to Database 2 or Oracle documentation forfurther information concerning the error code.

Destination:

CSMT

ERZ082021E Select position in file: ’filename’, index:’index’, for RRN: RRNd wasunsuccessful, SQL Code: SQLErrorCode’SQLErrorText’

Explanation: A database error has occurred whenattempting to select a record from a RRDS File.



Destination:

CSMT

ERZ082022E Select position in file: ’filename’, index:’index’, for RBA: RBAd was unsuccessful,SQL code: SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to select a record in an ESDS File.



Destination:

CSMT

ERZ082024E Read for delete in file: ’filename’, index:’index’ was unsuccessful, SQL code:SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to obtain a record with the intention ofdeleting it.

System action: The record was not deleted. Thetransaction continues, but CICS can possibly generatefurther messages as a result of this error.

User response: Check that the database is running.

Check that the resource definitions for the file areconsistent with the configuration of the database. Referto Database 2 or Oracle documentation for furtherinformation concerning the error code.

Destination:

CSMT

ERZ082027E Write record to file: ’filename’, for index:’index’ was unsuccessful, SQL code:SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to write a record to the file.



Destination:

CSMT

ERZ082028E Write of record to RRDS file: ’filename’,for RRN: RRNd was unsuccessful, SQLcode: SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred onattempting to write a record to the indicated RRDS file.



Destination:

CSMT

ERZ082029E Write of record to ESDS file: ’filename’was unsuccessful, SQL code:SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to write a record to the indicated ESDS file.



Destination:

CSMT

ERZ082021E • ERZ082029E


ERZ082030E Browse of file: ’filename’, index: ’index’,key: ’key’ was unsuccessful, SQL code:value ’SQLErrorCode’

Explanation: A database error has occurred whenattempting to start a browse with the indicated keyvalue in the specified file.



Destination:

CSMT

ERZ082031E Browse of file: ’filename’, index: ’index’,for RRN: RRNd was unsuccessful, SQLCode: SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to start a browse in a RRDS file.



Destination:

CSMT

ERZ082032E Browse of file: ’filename’, index: ’index’,for RBA: RBAd was unsuccessful, SQLCode: SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to start a browse in an ESDS file.



Destination:

CSMT

ERZ082033E Browse of file at first record: ’filename’,index: ’index’ was unsuccessful, SQLCode: SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to start a browse at the first record in a file.

System action: The transaction continues, but CICS

can possibly generate further messages as a result ofthis error.


Destination:

CSMT

ERZ082034E Browse of file at last record: ’filename’,index: ’index’ was unsuccessful, SQLCode: SQLErrorCode ’SQLErrorText’

Explanation: A database error has occurred whenattempting to start a browse at the last record in a file.



Destination:

CSMT

ERZ082035E Abnormal termination A82C: Filecontrol SQL resources are exhausted.

Explanation: CICS was attempting to start a newbrowse or perform a new read-update but ApplicationServer SQL resources are exhausted.


User response: Please refer to CICS documentationthat describes the limitations on the number ofconcurrent browses and read-updates when mappingFile Control to SQL. A system limit was breached andthe application requires rework.

Destination:

CSMT

ERZ082041E Data structure inconsistency has beendetected for file: ’filename’


System action: After further self-consistency checking,CICS abnormally terminates.

User response: Determine the cause of theinconsistency in the internal data structures. It ispossible that these were overwritten by defectiveapplication programs. It is also possible that an internalCICS error caused this inconsistency.

Destination:

CSMT

ERZ082030E • ERZ082041E


ERZ082042E Invalid variable length recordspecification for file ’database’/’filename’

Explanation: The file definition declared to thedatabase either has more than one variable length field,or the variable length field is not the last field in therecord.


User response: Consult the TXSeries Infocenter fordetails of the SQL file structures that are supported byCICS. Either alter the CICS file definition to referencean SQL file whose structure is supported by CICS oradjust the SQL file definition.

Destination:

CSMT

ERZ082043E A variable length field has been foundin index ’index’ for file’database’/’filename’

Explanation: The index definition in the database hasa variable length field. CICS does not support suchindexes.


User response: Consult the TXSeries Infocenter fordetails of the SQL file structures that are supported byCICS. Either alter the CICS file definition to referencean SQL file whose structure is supported by CICS oradjust the SQL file definition. It is possible that this filehas other indexes that do not use variable length fields,and hence CICS can be configured to access the filesvia such indexes.

Destination:

CSMT

ERZ082044E Record length Recordd too large for file’length’/’database’, Index: ’filename’.

Explanation: The SQL file definition has a recordlength greater than 32767.



Destination:

CSMT

ERZ082046I Variable field found in relative recordfile definition ’database’/’filename’

Explanation: This message is for information only.CICS is opening an RRDS file that has a variable lengthrecord definition.


User response: Consult the TXSeries Infocenter forinformation on accessing files with records longer than4005 bytes when using Database 2 to support CICS filesand queues.

Destination:

CSMT

ERZ082093E Attempt to empty file: ’tablename’ andindex: ’index’ from ’database’ wasunsuccessful, SQL Code: SQLErrorCode’SQLErrorText’

Explanation: A database error has occurred whenattempting to empty a file during a file open operation.

System action: The transaction continues, but CICScan possibly generate further messages as a result ofthis error. The file was not emptied.

User response: Check that the database is stillrunning. Check that there are no other users of the file.It is possible that the file was opened by the currentCICS region, using a different File Control access path.It is possible that another CICS region is accessing thefile. It is possible that an off-line application program isusing the file. Refer to SQL documentation for furtherinformation concerning the SQL error code.

Destination:

CSMT

ERZ082099W Index ’file’ for file ’index’/’database’contains an NLS field: genericoperations should not be used

Explanation: CICS File Control generic key operationsare not reliable when applied to such indexes.


User response: Consult the TXSeries Infocenter fordetails of the file structures that are supported by CICS.Either alter the CICS file definition to reference an SQLfile whose structure is supported by CICS or adjust theSQL file definition.

Destination:

CSMT

ERZ082042E • ERZ082099W


ERZ082101E Abnormal termination A82L: Failed toretain lock for file ’filename’, index’index’; SQL code: SQLErrorCode’SQLErrorText’

Explanation: CICS was unsuccessful in retaining alock for the named file.



Destination:

CSMT

ERZ082200E A column with an invalid type has beenfound for file ’database’/’filename’ withindex ’index’

Explanation: The table definition in the databasecontains a column with a type not supported by CICS.



Destination:

CSMT

ERZ082201E Attempt to access file: ’tablename’ withindex: ’index’ from ’database’ wasunsuccessful, SQL Code: SQLErrorCode’SQLErrorText’

Explanation: An SQL error has occurred whileaccessing the specified file and index.


User response: Check that the database is running.Check that the resource definitions for file ’index’ andindex ’database’ are consistent with the databaseconfiguration. Refer to Database 2 or Oracledocumentation for further information concerning theSQL error code.

Destination:

CSMT

ERZ082202E Abnormal termination U8202. Database2 deferred bind was unsuccessful, SQLerror code ’sqlcode’, Bind return code’bindcode’

Explanation: A Database 2 deferred bind operationfailed. The sqlcode returned by the RDBMS is reportedby this message, the associated RDBMS error text isprovided in a symrec. Follow the RDBMS proceduresfor the reported RDBMS message. In addition, checkthe bind operation log file, which is placed in theRegion’s data directory.


User response: CICS must be restarted once theRDBMS failure is remedied.

Destination:

console.msg

ERZ082300E SQL error in ’sqlstring’ for file ’filename’,index ’index’; SQL code: SQLErrorCode’SQLErrorText’

Explanation: An SQL error has occurred whileprocessing a CICS File Control SQL command againstthe specified file and index.


User response: Check that the database is running.Check that the resource definitions for file ’filename’and index ’index’ are consistent with the databaseconfiguration. Refer to Database 2 or Oracledocumentation for further information concerning theSQL error code.

Destination:

CSMT

ERZ082301E Reversal of browse operation on file:’filename’, index: ’index’ wasunsuccessful, SQL Code: SQLErrorCode’SQLErrorText’

Explanation: A database error has occurred whenattempting to reverse a browse against a file.



Destination:

CSMT

ERZ082101E • ERZ082301E


ERZ082302E A non-contiguous field has been foundin index ’index’ for file’database’/’filename’

Explanation: The index definition in the database doesnot consist of contiguous fields. When using a databaseas the file manager, CICS only supports indexes withcontiguous key fields.


User response: Consult the TXSeries Infocenter fordetails of the SQL file structures that are supported byCICS. Either alter the CICS file definition to referencean SQL file whose structure is supported by CICS oradjust the SQL file definition. It is possible that this filehas other indexes that do not use non-contiguousfields, and hence CICS can be configured to access thefiles via such indexes.

Destination:

CSMT

ERZ082303E SQL error when initialising collation forthis locale; SQL code: SQLErrorCode’SQLErrorText’

Explanation: An SQL error has occurred whiledetermining the collation sequence for this locale.

System action: Processing continues, but CICS canpossibly generate further messages as a result of thiserror. If this error occurs, but other SQL initialisationactivities are successful, then transactions that runagainst this server can possibly exhibit differentcollation behavior. Specifically, where collation isperformed against data that is NLS-aware, i.e. whereCICS is accessing tables that have character columnsthat are not defined for bit data, data is returnedaccording to the binary collation sequence rather thanaccording to the NLS codepage.

User response: Check that the database is running.Refer to Database 2 or Oracle documentation forfurther information concerning the SQL error code.

Destination:

CSMT

ERZ082304W Application Server serverid will use theDB2 binary collation sequence only forFile Control operations

Explanation: An SQL error has occurred whiledetermining the collation sequence for this locale. Thiserror is reported in CSMT.out.


User response: Check CSMT.out for the specific SQLerror.

Destination:

console.msg

ERZ082305E File ’filename’ has an incorrect ’column’column definition

Explanation: An incorrect column definition for anRBA or RRN column was found. These columns mustbe defined as CHAR(4) NOT NULL FOR BIT DATA forDatabase 2 and as RAW(4) NOT NULL for Oracle.



Destination:

CSMT

ERZ085002E The ’optionName’ option has beenspecified more than once

Explanation: You have specified the command lineoption ’optionName’ more than the permitted number oftimes.

System action: The cicsivp command terminates witha non-zero return code.


Destination:

stderr

ERZ085003E The usage of the ’optionName’ option isinvalid

Explanation: You have incorrectly specified anargument that is either not a valid option or thatrequires a parameter.

System action: The cicsivp command issues usagemessage ERZ8505I before terminating with a non-zeroreturn code.


Destination:

stderr

ERZ085004E The region name ’regionName’ is too long

Explanation: You have specified a region name that itis not possible to have as all region names are made upof 8 or less characters.

ERZ082302E • ERZ085004E



User response: Retry the command with a validregion name.

Destination:

stderr

ERZ085005I Usage: cicsivp {-? | -r regionName [-llanguage] [-s serverName] [-vvolumeName]}

Explanation: You invoked cicsivp with invalidarguments.

System action: The cicsivp command terminates.


Destination:

stderr

ERZ085006E Cannot find the CICS command’commandName’

Explanation: The command ’commandName’ does notreside in a directory pointed to by the environmentvariable PATH.

System action: The cicsivp command terminates.

User response: Redefine the environment variablePATH so that it references the CICS bin directory.

Destination:

stderr

ERZ085007I Please wait, initializing......

Explanation: The cicsivp command is preparing toupdate the resource definition files.

System action: The cicsivp command continues.

User response: None

Destination:

stderr

ERZ085008I ’percentComplete’ percent completed:added the resource ’resourceName’ toclass ’className’

Explanation: The cicsivp command has completed’percentComplete’ percent, and is continuing.



Destination:

stderr

ERZ085009I The cicsivp ended with a return code of’returnCode’.

Explanation: The cicsivp command has ended withreturn code ’returnCode’.

System action: The cicsivp command ends.

User response: If there was an error during theexecution of cicsivp, then the return code is non-zero.Read the previous message for more information.

Destination:

stderr

ERZ085010E Cannot add resource ’resourceName’ toresource definition file for class’className’.

Explanation: The cicsivp command has tried to addthe resource ’resourceName’ to class ’className’ but wasunsuccessful because a non-IVP entry already exists orbecause the cicsivp command failed.

System action: The cicsivp command terminates

User response: Remove the resource entry that iscausing the problem and run cicsivp again. See theTXSeries Infocenter. If the resource entry for thatresource does not exist then contact your supportorganization.

Destination:

stderr

ERZ085011I Now updating the stanza files

Explanation: The cicsivp command is updating theresource definition file.


User response: None

Destination:

stderr

ERZ085012I The cicsivp command has beeninterrupted

Explanation: The cicsivp command stopped withSIGINT.

System action: The cicsivp command stopped. Toinstall the Installation Verification Programs please runthe command again.


Destination:

stderr

ERZ085005I • ERZ085012I


ERZ085013I Successfully added resource’resourceName’ to class ’className’

Explanation: The cicsivp command successfully addedthe resource ’resourceName’ to class ’className’, and iscontinuing.



Destination:

stderr

ERZ085014E cicsivp does not support theprogramming language ’Language’

Explanation: You have specified a programminglanguage not supported by cicsivp.


User response: Retry the command with a validprogramming language, the default is C. Validprogramming languages are defined by cicstcl.

Destination:

stderr

ERZ085015W cicsivp failed to find directory’IVPSourcePath’

Explanation: The directory IVPSourcePath was notfound.


User response: Check that the Installation VerificationPrograms are installed.

Destination:

stderr

ERZ085016I Permanent database request for’resourceName’ succeeded, thoughrun-time request was unsuccessful

Explanation: This message indicates that only yourpermanent database operation succeeded. Yourequested that the operation be performed on both thepermanent and the run-time database, but the run-timedatabase operation was unsuccessful.

System action: None

User response: Other messages indicate why therun-time request was unsuccessful. Retry the commandwhen appropriate.

Destination:

stderr

ERZ085018E The usage of the ’optionName1’ optionwith the ’%2$s’ option is invalid

Explanation: You have incorrectly specified twoargumentments only one of which is valid.



Destination:

stderr

ERZ085019W The ’-u’ option will be ignored.

Explanation: The File System used by the Region doesnot need the UserData to create a file.

System action: The cicsivp command continuesprocessing.


Destination:

stderr

ERZ085020E The ’-u’ option must be supplied for anOracle file server.

Explanation: The Oracle server used by the Regionmust be given the UserID option.


User response: Retry the command with the requiredoption.

Destination:

stderr

ERZ085021E cicsivp can not communicate with server’serverName’.

Explanation: The server ’serverName’ was unable to becontacted. The server is possibly not running. Theuser’s environment is possibly set incorrectly.


User response: Ensure you are trying to use a serverthat exists and is running.

Destination:

stderr

ERZ085013I • ERZ085021E


ERZ085022E cicsivp can not find stanza entry forserver ’serverName’.

Explanation: The server ’serverName’ is not defined inthe SSD stanza file. The server was not created.


User response: Make sure that the server does existand is correctly defined in the SSD.stanza file.

Destination:

stderr

ERZ086001E Template file ’fileName’ cannot beopened

Explanation: The template file specified either doesnot exist or its file permissions do not allow access tothe file.

System action: The formatting utility terminates.

User response: If this problem persists, contact yoursupport organization.

Destination:

stderr

ERZ086002E No formatting has been performed.Errors were detected during translationof the template file ’fileName’.

Explanation: The first step of the formatting process isto translate the template file into an internalrepresentation. This was unable to proceed because thetemplate file contained syntax errors. Details of theerrors preceded this message.



Destination:

stderr

ERZ086003E Output file ’fileName’ cannot be opened

Explanation: Either the filename specified is aninvalid one or the file already exists and its filepermissions do not allow write access.


User response: Specify an alternative valid filename orcorrect the file permissions of the output file youspecified.

Destination:

stderr

ERZ086004E Data file ’fileName’ cannot be opened

Explanation: The trace or dump data file specifiedeither does not exist or its file permissions do not allowread access.


User response: Specify an alternative valid filename orcorrect the file permissions of the data file youspecified.

Destination:

stderr

ERZ086005E Unable to read all the data from thedata file ’fileName’. File Position: ’irec’Hook Id: ’hookId’

Explanation: An error occurred while reading datafrom the trace or dump data file. The data file ispossibly corrupted.


User response: Recreate the trace or dump data file. Ifthe problem persists, contact your support organization.

Destination:

stderr

ERZ086006E Unable to read padding data from thedata file ’fileName’. File Position:’filePosition’ Hook Id: ’hookId’




Destination:

stderr

ERZ086007E Unable to read a timestamp from thedata file ’dataFn’. File Position:’filePosition’ Hook Id: ’hookId’




Destination:

stderr

ERZ085022E • ERZ086007E


ERZ086008E An error was detected during formattingof the data file ’fileName’. File Position:’filePosition’ Hook Id: ’hookId’

Explanation: An error occurred during formatting.



Destination:

stderr

ERZ086009E Unsuccessful attempt to set the locale

Explanation: CICSRPT cannot set the locale from theenvironment.


User response: Check the locale settings in yourenvironment and correct any invalid options.

Destination:

stderr

ERZ086010E Cannot find the definition of theUNDEFINED Hook Id ’hookId’

Explanation: Either the definition of the UNDEFINEDHook Id does not exist in the template file or theinternal representation of the template file is invalid.



Destination:

stderr

ERZ086011E A call to an undefined macro wasencountered. Macro name: ’macroName’.

Explanation: Either the definition of the macrospecified does not exist in the template file or theinternal representation of the template file is invalid.

System action: CICSRPT continues processing.


Destination:

stderr

ERZ086012E An invalid Hook type was encounteredin the input data file ’dataFn’. FilePosition: ’filePosition’ Hook Id: ’hookId’

Explanation: An error occurred while reading datafrom the trace or dump data file. It is possibly not avalid CICS trace or dump data file.



Destination:

stderr

ERZ086013E Cannot find the definition of theDEFAULT Hook Id ’hookId’

Explanation: Either the definition of the DEFAULTHook Id does not exist in the template file or theinternal representation of the template file is invalid.



Destination:

stderr

ERZ086020E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Incorrect hook templatedefinition.

Explanation: A Hook Id definition in the template filebeing used is incorrect. This is usually due to syntaxerrors found in its formatting statements.



Destination:

stderr

ERZ086021E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Incorrect formattingcommand definition.

Explanation: A formatting command definition in thetemplate file being used is incorrect.



Destination:

stderr

ERZ086022E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Incorrect switch statementdefinition.

Explanation: The definition of a switch statement inthe template file being used is incorrect. The location ofthe error is in the message.


ERZ086008E • ERZ086022E



Destination:

stderr

ERZ086023E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Incorrect LOOP statementdefinition.

Explanation: The definition of a LOOP statement inthe template file being used is incorrect. Details of theerror precede this message.



Destination:

stderr

ERZ086024E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Incorrect expressionstatement definition.

Explanation: The definition of an expression statementin the template file being used is incorrect. Details ofthe error precede this message.



Destination:

stderr

ERZ086025E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Incorrect macro declarationstatement definition.

Explanation: The definition of a macro declarationstatement in the template file being used is incorrect.Details of the error precede this message.



Destination:

stderr

ERZ086026E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Incorrect macro callarguments list definition.

Explanation: The definition of the arguments list of amacro call statement in the template file being used isincorrect. Details of the error precede this message.



Destination:

stderr

ERZ086027E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Incorrect BITFLAGSstatement definition.

Explanation: The definition of a BITFLAGS statementin the template file being used is incorrect. Details ofthe error precede this message.



Destination:

stderr

ERZ086030E [Error errorNo] ’errorMsg’ line lineNo near’errorSource’ - Unsupported format code.

Explanation: Either a format code was encounteredthat is not supported by the CICSRPT translator or aninvalid format code was used together with a variable.In the latter case only D, B, X or U format codes can beused.



Destination:

stderr

ERZ086040E *** ABNORMALLY TERMINATING:Too many errors. ***

Explanation: The CICSRPT translator has encounteredtoo many errors. Formatting was not performed.



Destination:

stderr

ERZ086041E *** ABNORMALLY TERMINATING:Assert failed at line lineNo of file’Filename’ ***

Explanation: An internal processing error wasencountered and CICSRPT cannot continue.



ERZ086023E • ERZ086041E


Destination:

stderr

ERZ086042E Cannot open stdin

Explanation: The formatting utility was unable toopen the stdin stream to read data passed between twoformatting processes.


User response: Retry the operation. If the problempersists, contact your support organization.

Destination:

stderr

ERZ086043E Unable to read trace data from the datafile for hook Id: ’hookId’

Explanation: An error occurred while reading fromthe trace data file. The data file is possibly corrupted.


User response: Recreate the trace data file. If theproblem persists, contact your support organization.

Destination:

stderr

ERZ086044E Unable to read padding data from thedata file for hook Id: ’hookId’




Destination:

stderr

ERZ086045E Unable to read timestamp data from thedata file for hook Id: ’hookId’




Destination:

stderr

ERZ086046E An error was detected during formattingof hook Id: ’hookId’

Explanation: An error occurred during formatting.The input file is possibly corrupted.



Destination:

stderr

ERZ086047E Invalid hook type hookType wasencountered in the input data file. HookId: ’hookId’

Explanation: An error occurred while reading datafrom the trace data file. It is possibly corrupted.



Destination:

stderr

ERZ086048E No space left on output file system.Format terminating.″

Explanation: The system error ENOSPC occurredwhilst formatting the data.


User response: Create more space in the outputdirectory and run the format command again.

Destination:

stderr

ERZ096002I cicscp command completed successfully

Explanation: The cicscp command was completedsuccessfully.

System action: None

User response: None

Destination:

stderr

ERZ096003E cicscp command failed

Explanation: The cicscp command was attempted butfailed.

System action: The program exits with a value of 5.Previous messages give more information about thefailure.

User response: None

ERZ086042E • ERZ096003E


Destination:

stderr

ERZ096004E An error was encountered during theprocessing of the cicscp command

Explanation: An error was detected by cicscp.

System action: The program exits with a value of 6.Previous messages give more information about thefailure.

User response: None

Destination:

stderr

ERZ096005E You must be logged in as root on UNIXor as Administrator on Windows NT torun cicscp

Explanation: You attempted to run cicscp whenlogged in with insufficient authority. On UNIX youmust be logged on as root. On Windows NT you mustbe logged on with a userid with Administrator andcicsgroup authority.

System action: The program exits with a value of 1.

User response: Log on correctly.

Destination:

stderr

ERZ096016E cicscp: option ’optionCharacter’ requires avalue

Explanation: This message is output when the usercalls cicscp and specifies an option that must have avalue but omits a value.

System action: The command exits with the value 4.

User response: Retry the command adding a value forthe option.

Destination:

stderr

ERZ096017E cicscp: unexpected option’optionCharacter’

Explanation: This message is output when the usercalls cicscp and specifies an option that cicscp does notrecognize.

System action: The command exits with the value 3.


Destination:

stderr

ERZ096028E Unexpected extra arguments’extraArguments’ for cicscp command

Explanation: This message is output when a cicscpcommand detects that more arguments were suppliedthan it was expecting.

System action: An error is returned and the commandfails.

User response: Correct the command and retry.

Destination:

stderr

ERZ096030E No object specified

Explanation: This message is output when cicscpprocesses a command that only specifies one word,which is taken as the command.


User response: Enter the correct command.

Destination:

stderr

ERZ096031E Unknown command ’commandName’

Explanation: This message is output when cicscpprocesses a command that it does not recognize.



Destination:

stderr

ERZ096032E Unknown object ’objectName’

Explanation: This message is output when cicscpprocesses a command for an object that it does notrecognize.



Destination:

stderr

ERZ096033E Too few arguments to cicscp.

Explanation: This message is output when cicscp isgiven a single argument that is not ’-?’



Destination:

stderr

ERZ096004E • ERZ096033E


ERZ096034E cicscp failed to allocate storage forcommand

Explanation: This message is output when cicscp isgiven a very long line and the system fails to allocatesufficient storage to hold the line.


User response: Enter a shorter command.

Destination:

stderr

ERZ096035E Error ’errorNumber’ returned whenreading stdin

Explanation: This message is output when cicscpdetects an error reading a command from the standardinput stream.


User response: Retry the command.

Destination:

stderr

ERZ096038E The length of the Control Point Name islimited to 8 characters

Explanation: This message is displayed if cicscpdetects that a value is supplied for the SNA ControlPoint Name that is greater than 8 characters in length.

System action: None

User response: Choose a shorter Control Point Name.

Destination:

stderr

ERZ096039E Unrecognized SNA Link Station Type:’linkStationType’

Explanation: This message is displayed if cicscp failsto recognize the value specified for the -y option oneither a ’create sna’ command or a ’create sna_link’command.

System action: None

User response: Choose a different Link Station Type.

Destination:

stderr

ERZ096040E Internal cicscp error detected:’errorNumber’

Explanation: This message is displayed if cicscpdetects an internal problem with the operation of cicscpitself.

System action: None

User response: Retry the command. If the problempersists, contact your support organization.

Destination:

stderr

ERZ096041E The -d, -w, -x and -y options aremandatory

Explanation: This message is displayed if cicscpdetects that one or more of the mandatory options werenot specified on a ’create sna’ command.

System action: None

User response: Specify all the mandatory options.

Destination:

stderr

ERZ096042I Creating the SNA configuration

Explanation: This message is output at the beginningof the configuration of SNA if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096043I SNA successfully configured

Explanation: This message is output when the SNAconfiguration is completed successfully, if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096044I Destroying the SNA configuration

Explanation: This message is output when the SNAconfiguration is being destroyed, if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096034E • ERZ096044I


ERZ096045I SNA configuration successfullydestroyed

Explanation: This message is output when the SNAconfiguration is successfully destroyed, if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096046I SNA is not configured on this machine

Explanation: This message is output when the userissues a cicscp destroy sna command and SNA is notconfigured. It is only output if the verbose (-v) optionis specified.

System action: The command succeeds.

User response: None

Destination:

stderr

ERZ096047I Starting the SNA configuration

Explanation: This message is output when the SNAconfiguration is being started, if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096048I SNA configuration successfully started

Explanation: This message is output when the SNAconfiguration is successfully started, if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096049E SNA must be configured before it canbe started

Explanation: This message is output when cicscpdetects that the user has attempted to start SNA beforeit is configured. Because sensible defaults cannot bechosen for the options necessary to create a SNAconfiguration, it cannot be created implicitly.

System action: None

User response: None

Destination:

stderr

ERZ096050I SNA is already running

Explanation: This message is output during theprocessing of a ’start sna’ command if cicscp detectsthat SNA is already running.

System action: None

User response: None

Destination:

stderr

ERZ096051I Stopping SNA

Explanation: This message is output when SNA isbeing stopped, if the verbose output flag (-v) isspecified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096052I SNA configuration successfully stopped

Explanation: This message is output when the SNAconfiguration is successfully stopped, if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096053I SNA is not running

Explanation: This message is output when a stop snacommand is processed but SNA is not running. It isonly output if the verbose output flag (-v) is specifiedto cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096055E The cicscp command ’commandNameobjectName’ is not supported

Explanation: This message is output when cicscpdetects a command that is not supported.

ERZ096045I • ERZ096055E


System action: An error is returned.

User response: Enter a supported command.

Destination:

stderr

ERZ096056I Creating SNA link

Explanation: This message is output at the beginningof the configuration of a SNA link if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096057I SNA link successfully configured

Explanation: This message is output when the SNAlink configuration is completed successfully, if theverbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096058E The Link Station Type must be supplied

Explanation: This message is displayed if cicscpdetects that the create sna_link command was invokedwithout the Link Station Type argument.

System action: None

User response: Specify at least the type of the link.

Destination:

stderr

ERZ096059E The cicscp command was incorrect

Explanation: This message is displayed if cicscpdetects a syntax error in a command. Previousmessages give a more precise description of the error.

System action: None

User response: Correct the command in error.

Destination:

stderr

ERZ096060I Processing a destroy sna_link command

Explanation: This message is output at the beginningof the destruction of a SNA link if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096061I SNA link successfully destroyed

Explanation: This message is output when thedestruction of the SNA link is completed successfully, ifthe verbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096062E You must specify both the Link StationName and the Link Station Type

Explanation: For a ’destroy sna_link’ command, eitherthe reserved name ’all’ must be specified, or both aLink Station Name and a Link Station Type must bespecified.

System action: None


Destination:

stderr

ERZ096063I cicscp command terminated

Explanation: This message is output if the userchooses not to continue with a command after beingprompted for confirmation.

System action: None

User response: None

Destination:

stderr

ERZ096064I Creating CICS COBOL support

Explanation: This message is output at the beginningof a create cobol command if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

ERZ096056I • ERZ096064I


stderr

ERZ096065I CICS COBOL support successfullydestroyed

Explanation: This message is output at the end of adestroy cobol command if the command was successfuland if the verbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096066E CICS COBOL support alreadyconfigured

Explanation: This message is output during a createcobol command if the CICS COBOL support is alreadyconfigured.

System action: The cicscp command fails.

User response: Destroy the existing CICS COBOLconfiguration and retry the create command.

Destination:

stderr

ERZ096067I CICS COBOL support successfullycreated

Explanation: This message is output at the end of acreate cobol command if the command was successfuland if the verbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096068E CICS COBOL support file ’fileName’could not be removed, error returnedwas ’errorNumber’

Explanation: This message is output during a destroycobol command if the file containing the CICS COBOLsupport cannot be removed.


User response: Check if any regions are running thatcan be using this file and terminate them. Retry thecommand.

Destination:

stderr

ERZ096069I CICS COBOL support is not configuredon this machine

Explanation: This message is output during a destroycobol command if CICS COBOL support is notconfigured on the machine and if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096070I Destroying CICS COBOL support

Explanation: This message is output at the beginningof a destroy cobol command if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096071I Creating a telnet server

Explanation: This message is output at the beginningof a ’create telnet_server’ command if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096072I The telnet server ’serverName’ wascreated successfully

Explanation: This message is output at the end of a’create telnet_server’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096073E The telnet server name must besupplied

Explanation: This message is output during theprocessing of a telnet_server command if the servername is not supplied.

System action: None

ERZ096065I • ERZ096073E


User response: Resubmit the command, specifying theserver name.

Destination:

stderr

ERZ096074E cicscp failed to allocate storage foroption

Explanation: This message is output when cicscp isgiven a very long option and the system fails toallocate sufficient storage to hold the option.


User response: Enter a shorter option.

Destination:

stderr

ERZ096075E cicscp failed to find telnet_server model’modelName’

Explanation: This message is output when cicscpprocesses a ’create telnet_server’ command including amodel and fails to find that model.


User response: Enter a model that does exist orcompletely specify the required telnet server.

Destination:

stderr

ERZ096076E telnet_server ’serverName’ already existsbut appears incorrect

Explanation: This message is output when cicscpprocesses a ’create telnet_server’ command and findsan existing, but incorrect, configuration for the namedserver.


User response: Destroy the configuration of the serverand then attempt the create command again.

Destination:

stderr

ERZ096077E telnet_server ’serverName’ already exists

Explanation: This message is output when cicscpprocesses a ’create telnet_server’ command and findsan existing configuration for the named server.



Destination:

stderr

ERZ096080E The telnet_server ’serverName’ does notexist

Explanation: This message is output when cicscpprocesses a ’destroy telnet_server’ command anddetects that the telnet_server does not exist.


User response: None

Destination:

stderr

ERZ096081I Processing a destroy telnet_servercommand

Explanation: This message is output at the beginningof a ’destroy telnet_server’ command if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096082I The telnet server ’serverName’ wasdestroyed successfully

Explanation: This message is output at the end of a’destroy telnet_server’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified.

System action: None

User response: None

Destination:

stderr

ERZ096083E cicscp failed to allocate storage

Explanation: This message is output when cicscp failsto allocate general storage (not storage mentioned inone of the other ″failed to allocate″ messages).


User response: Retry the command. If you are in along interactive session with cicscp, try ending thesession and submitting the command on the commandline.

Destination:

stderr

ERZ096074E • ERZ096083E


ERZ096084I Processing a create ppcgwy_servercommand

Explanation: This message is output at the beginningof a ’create ppcgwy_server’ command if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096085I The PPC gateway server ’serverName’was created successfully

Explanation: This message is output at the end of a’create ppcgwy_server’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096086I Processing a destroy ppcgwy_servercommand

Explanation: This message is output at the beginningof a ’destroy ppcgwy_server’ command if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096087I The PPC gateway server ’gatewayName’was destroyed successfully

Explanation: This message is output at the end of a’destroy ppcgwy_server’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096088I Processing a start ppcgwy_servercommand

Explanation: This message is output at the beginningof the processing of a ’start ppcgwy_server’ command,if the verbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096089I PPC gateway server ’serverName’successfully started

Explanation: This message is output when the PPCgateway server is successfully started, if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096090I Processing a stop ppcgwy_servercommand

Explanation: This message is output at the beginningof the processing of a ’stop ppcgwy_server’ command,if the verbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096091I PPC gateway server ’serverName’successfully stopped

Explanation: This message is output when the PPCgateway server is successfully stopped, if the verboseoutput flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096092E The PPC gateway server name must besupplied

Explanation: This message is output during theprocessing of a ppcgwy_server command if the servername is not supplied.

System action: None

User response: Resubmit the command, specifying aserver name.

Destination:

stderr

ERZ096084I • ERZ096092E


ERZ096093W SNA is not configured on this machine

Explanation: This message is output during theprocessing of a ’create ppcgwy_server’ command ifSNA is not configured on the machine.

System action: The server is configured.

User response: SNA must be configured before theserver can be started.

Destination:

stderr

ERZ096094W SNA configured incorrectly on thismachine

Explanation: This message is output during theprocessing of a ’create ppcgwy_server’ command ifSNA is not configured correctly on the machine.

System action: The server is configured.

User response: SNA must be configured correctlybefore the server can be started.

Destination:

stderr

ERZ096095E ppcgwy_server ’serverName’ alreadyexists but appears incorrect

Explanation: This message is output when cicscpprocesses a ’create ppcgwy_server’ command and findsan existing, but incorrect, configuration for the namedserver.



Destination:

stderr

ERZ096096E ppcgwy_server ’serverName’ alreadyexists

Explanation: This message is output during a ’createppcgwy_server’ command if the server is alreadyconfigured.


User response: Destroy the existing PPC gatewayserver configuration and retry the create command.

Destination:

stderr

ERZ096097E stanza override must be of the formattributeName=attributeValue

Explanation: This message is output if cicscp fails toparse a string of stanza file attribute overrides.


User response: Correct the syntax and retry thecommand.

Destination:

stderr

ERZ096098E The PPC gateway server ’serverName’does not exist

Explanation: This message is output when cicscpprocesses a ’destroy ppcgwy_server’ command anddetects that the ppcgwy_server does not exist.


User response: None

Destination:

stderr

ERZ096099I The PPC gateway server ’serverName’ isalready running

Explanation: This message is output during theprocessing of a ’start ppcgwy_server’ command ifcicscp detects that the server is already running.

System action: None

User response: None

Destination:

stderr

ERZ096100E The PPC gateway server ’serverName’ isnot configured on this machine

Explanation: This message is output during a ’stopppcgwy_server’ command if the named PPC gatewayserver is not configured on the machine.

System action: None

User response: Specify the correct server.

Destination:

stderr

ERZ096101I The PPC gateway server ’serverName’ isnot running

Explanation: This message is output when a ’stopppcgwy_server’ command is processed but the PPCgateway server is not running. It is only output if theverbose output flag (-v) is specified to cicscp.

ERZ096093W • ERZ096101I


System action: None

User response: None

Destination:

stderr

ERZ096103I Creating an SFS server

Explanation: This message is output at the beginningof a ’create sfs_server’ command if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096104E The SFS server name must be supplied

Explanation: This message is output during theprocessing of a sfs_server command if the server nameis not supplied.

System action: None

User response: Resubmit the command, specifying aserver name.

Destination:

stderr

ERZ096105E The SFS server ’serverName’ alreadyexists but appears incorrect

Explanation: This message is output when cicscpprocesses a ’create sfs_server’ command or a createregion command and finds an existing, but incorrect,configuration for the named server.



Destination:

stderr

ERZ096106E The SFS server ’serverName’ alreadyexists

Explanation: This message is output during a createsfs_server command if the server is already configured.


User response: Destroy the existing SFS serverconfiguration and retry the create command.

Destination:

stderr

ERZ096107I The SFS server ’serverName’ was createdsuccessfully

Explanation: This message is output at the end of a’create sfs_server’ command if the command completedsuccessfully and if the verbose output flag (-v) isspecified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096108I Processing a destroy sfs_servercommand

Explanation: This message is output at the beginningof a ’destroy sfs_server’ command if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096109E The SFS server ’serverName’ does notexist

Explanation: This message is output when cicscpprocesses a ’destroy sfs_server’ command and detectsthat the server does not exist.


User response: None

Destination:

stderr

ERZ096110I The SFS server ’serverName’ wasdestroyed successfully

Explanation: This message is output at the end of a’destroy sfs_server’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096111I Processing a start sfs_server command

Explanation: This message is output at the beginningof the processing of a ’start sfs_server’ command, if theverbose output flag (-v) is specified to cicscp.

ERZ096103I • ERZ096111I


System action: None

User response: None

Destination:

stderr

ERZ096112I The SFS server ’serverName’ is running

Explanation: This message is output during theprocessing of a ’start sfs_server’ command if cicscpdetects that the server is already running.

System action: None

User response: None

Destination:

stderr

ERZ096113I SFS server ’serverName’ successfullystarted

Explanation: This message is output when the SFSserver is successfully started, if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096114I Stopping an SFS server

Explanation: This message is output at the beginningof the processing of a ’stop sfs_server’ command, if theverbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096115I SFS server ’serverName’ successfullystopped

Explanation: This message is output when the SFSserver is successfully stopped, if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096116E The SFS server ’serverName’ is notconfigured on this machine

Explanation: This message is output during a ’stopsfs_server’ command if the named SFS server is notconfigured on the machine.

System action: None

User response: Specify the correct server.

Destination:

stderr

ERZ096117I The SFS server ’serverName’ is notrunning

Explanation: This message is output when a ’stopsfs_server’ command is processed but the SFS server isnot running. It is only output if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096118I Creating a region

Explanation: This message is output at the beginningof a ’create region’ command if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096119E The region ’regionName’ already existsbut appears incorrect

Explanation: This message is output when cicscpprocesses a ’create region’ command and finds anexisting, but incorrect, configuration for the namedregion.


User response: Destroy the configuration of the regionand then attempt the create command again.

Destination:

stderr

ERZ096120E The region ’regionName’ already exists

Explanation: This message is output during a ’createregion’ command if the region is already configured.


ERZ096112I • ERZ096120E


User response: Destroy the existing regionconfiguration and retry the create command.

Destination:

stderr

ERZ096121I The region ’regionName’ was createdsuccessfully

Explanation: This message is output at the end of a’create region’ command if the command completedsuccessfully and if the verbose output flag (-v) isspecified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096122I Processing a ’start region’ command

Explanation: This message is output at the beginningof the processing of a ’start region’ command, if theverbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096123E The region name must be supplied

Explanation: This message is output during theprocessing of a region command if the region name isnot supplied.

System action: None

User response: Resubmit the command, specifying aregion name.

Destination:

stderr

ERZ096124E Unrecognized value for the -d option:’distributedServers’

Explanation: This message is output during theprocessing of a ’start region’ command if the value forthe -d option is not correct.

System action: None

User response: Resubmit the command, specifying acorrect value for the -d option.

Destination:

stderr

ERZ096125I The region ’regionName’ is alreadyrunning

Explanation: This message is output during theprocessing of a ’start region’ command if cicscp detectsthat the region is already running.

System action: None

User response: None

Destination:

stderr

ERZ096126I Region ’regionName’ successfully started

Explanation: This message is output when the regionis successfully started, if the verbose output flag (-v) isspecified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096127I Processing a destroy region command

Explanation: This message is output at the beginningof a ’destroy region’ command if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096128I The region ’regionName’ was destroyedsuccessfully

Explanation: This message is output at the end of a’destroy region’ command if the command completedsuccessfully and if the verbose output flag (-v) isspecified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096130E The region ’regionName’ does not exist

Explanation: This message is output when cicscpprocesses a ’destroy region’ command and detects thatthe region does not exist.


User response: None

ERZ096121I • ERZ096130E


Destination:

stderr

ERZ096131I Processing a ’stop region’ command

Explanation: This message is output at the beginningof the processing of a ’stop region’ command, if theverbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096132E The region ’regionName’ is notconfigured on this machine

Explanation: This message is output during a ’stopregion’ command if the named region is not configuredon the machine.

System action: None

User response: Specify the correct region.

Destination:

stderr

ERZ096134I Region ’regionName’ successfully stopped

Explanation: This message is output when the regionis successfully stopped, if the verbose output flag (-v) isspecified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096135I The region ’regionName’ is not running

Explanation: This message is output when a ’stopregion’ command is processed but the region is notrunning. It is only output if the verbose output flag (-v)is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096136E Only one of -c and -f can be specified

Explanation: This message is output when a ’stopregion’ command is processed and both the -c and -foptions are specified. The options are mutuallyexclusive.

System action: None

User response: Choose one of the options to specify.

Destination:

stderr

ERZ096137E SNA is not configured on this machine

Explanation: This message is output during theprocessing of a ’start ppcgwy_server’ command if SNAis not configured on the machine.

System action: The server is not started.

User response: SNA must be configured before theserver can be started.

Destination:

stderr

ERZ096138E SNA configured incorrectly on thismachine

Explanation: This message is output during theprocessing of a ’start ppcgwy_server’ command if SNAis not configured correctly on the machine.

System action: The server is not started.

User response: SNA must be configured correctlybefore the server can be started.

Destination:

stderr

ERZ096139E The reserved name ’all’ is not valid forthe create command

Explanation: This message is output during theprocessing of a cicscp create command if the reservedname all is specified.


User response: Choose a different name or a differentcommand.

Destination:

stderr

ERZ096140I Destroying SFS server ’serverName’

Explanation: This message is output during theprocessing of a ’destroy sfs_server’ command once thecommand is validated and the server name extracted. Itis only output if the verbose (-v) flag is specified tocicscp.

System action: None

User response: None

Destination:

ERZ096131I • ERZ096140I


stderr

ERZ096141I Starting SFS server ’serverName’

Explanation: This message is output during theprocessing of a ’start sfs_server’ command once thecommand is validated and the server name extracted. Itis only output if the verbose (-v) flag is specified tocicscp.

System action: None

User response: None

Destination:

stderr

ERZ096142I All SFS servers destroyed successfully

Explanation: This message is output at the end of a’destroy sfs_server all’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096143I All SFS servers started successfully

Explanation: This message is output at the end of a’start sfs_server all’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096144I All SFS servers stopped successfully

Explanation: This message is output at the end of a’stop sfs_server all’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096145I Stopping SFS server ’serverName’

Explanation: This message is output during theprocessing of a ’stop sfs_server’ command once thecommand is validated and the server name extracted. Itis only output if the verbose (-v) flag is specified tocicscp.

System action: None

User response: None

Destination:

stderr

ERZ096146I Destroying PPC gateway server’serverName’

Explanation: This message is output during theprocessing of a ’destroy ppcgwy_server’ command oncethe command is validated and the server nameextracted. It is only output if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096147I All PPC gateway servers destroyedsuccessfully

Explanation: This message is output at the end of a’destroy ppcgwy_server all’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096148I Starting PPC gateway server ’serverName’

Explanation: This message is output during theprocessing of a ’start ppcgwy_server’ command oncethe command is validated and the server nameextracted. It is only output if the verbose (-v) flag isspecified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096141I • ERZ096148I


ERZ096149I All PPC gateway servers startedsuccessfully

Explanation: This message is output at the end of a’start ppcgwy_server all’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096150I All PPC gateway servers stoppedsuccessfully

Explanation: This message is output at the end of a’stop ppcgwy_server all’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096151I Stopping PPC gateway server’serverName’

Explanation: This message is output during theprocessing of a ’stop ppcgwy_server’ command oncethe command is validated and the server nameextracted. It is only output if the verbose (-v) flag isspecified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096152I Destroying telnet server ’serverName’

Explanation: This message is output during theprocessing of a ’stop telnet_server’ command once thecommand is validated and the server name extracted. Itis only output if the verbose (-v) flag is specified tocicscp.

System action: None

User response: None

Destination:

stderr

ERZ096153I All telnet servers destroyed successfully

Explanation: This message is output at the end of a’destroy telnet_server all’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096154I Destroying SNA link ’linkStationName’

Explanation: This message is output during theprocessing of a ’destroy sna_link’ command once thecommand is parsed. It is only output if the verbose (-v)flag is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096155I All SNA links successfully destroyed

Explanation: This message is output when thedestruction of the SNA link is completed successfully, ifthe verbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096156I Destroying region ’regionName’

Explanation: This message is output during theprocessing of a ’destroy region’ command once theregion name is extracted from the command. It is onlyoutput if the verbose output flag (-v) is specified tocicscp.

System action: None

User response: None

Destination:

stderr

ERZ096157I All regions destroyed successfully

Explanation: This message is output at the end of a’destroy region all’ command if the commandcompleted successfully and if the verbose output flag(-v) is specified to cicscp.

System action: None

ERZ096149I • ERZ096157I


User response: None

Destination:

stderr

ERZ096158I The region ’regionName’ is starting

Explanation: This message is output during theprocessing of a ’status region’ command once theregion name is extracted. It is only output if theverbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096159I All regions successfully started

Explanation: This message is output when a ’startregion all’ command completes successfully. It is onlyoutput if the verbose output flag (-v) is specified tocicscp.

System action: None

User response: None

Destination:

stderr

ERZ096160I Stopping region ’regionName’

Explanation: This message is output during theprocessing of a ’stop region’ command when the regionname is known. It is only output if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096161I All regions successfully stopped

Explanation: This message is output when a ’stopregion all’ command is successfully completed, if theverbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096162E ’create’ command not supported forobject ’all’

Explanation: This message is output when a ’createall’ command is read by cicscp.

System action: None

User response: Submit another command.

Destination:

stderr

ERZ096163I cicscp has assigned port number’portNumberserverName’ to telnet server’portNumberserverName’

Explanation: This message is output if no portnumber is specified with a create telnet_servercommand and cicscp assigns one to the server.

System action: None

User response: None

Destination:

stderr

ERZ096164E The ’function’ of ’stream’ failed with errornumber ’errorNumber’

Explanation: This message is output if cicscp detectsan error when manipulating the standard I/O streamsduring the creation of a sub-process.


User response: Retry the command. If it still fails thena system resource limit was possibly reached. Consultthe operating system documentation for theappropriate function and check the conditions for theerrorNumber value.

Destination:

stderr

ERZ096166E cicscp failed to execute the program’programName’, error number is’errorNumber’

Explanation: This message is output if cicscp detectsan error when executing the program.


User response: Consult the operating systemdocumentation for the execvp() function and check theconditions for the errorNumber value.

Destination:

stderr

ERZ096158I • ERZ096166E


ERZ096167E Both -a <alias> and -o <instance name>must be specified

Explanation: This message is output during theprocessing of a ’create region’ command if cicscpdetects one of the options that are mandatory to createa region using DB2 as the file system without the otherone.


User response: Specify both of the mandatory optionsfor use with DB2.

Destination:

stderr

ERZ096170E cicscp failed to open the specified logfile, error number is ’errorNumber’

Explanation: This message is output if cicscp detectsan error when attempting to open the log file specifiedon the command line.


User response: Specify a different directory for the logfile. If it still fails then a user resource limit or a systemresource limit was possibly reached.

Destination:

stderr

ERZ096171E cicscp has failed to set upCICSDB2PASSWD environmentvariable, error is ’errorNumber’

Explanation: This message is output when cicscp failsto set the CICSDB2PASSWD environment variable.


User response: None

Destination:

stderr

ERZ096172E DB2-related options missing whenimporting a region with a DB2 fileserver

Explanation: This message is output when cicscpdetects that the Infile used with the -i option of the’cicscp create region’ command represents a region thatwas configured to use DB2 as the file server but the’cicscp create region’ command does not have theoptions that are mandatory for a region using DB2 asthe file server.


User response: Supply the necessary DB2-relatedoptions to the ’cicscp create region’ command.

Destination:

stderr

ERZ096173I Permanent database stanza files forservers created

Explanation: This message is output when cicscpdetects that one or all of the default stanza files for theSSD, GSD and SCD classes were missing and had tocreate default stanza files for these classes. Thismessage normally follows an error message reportingwhich class file was missing.

System action: The missing files are created, and thecommand continues.

User response: None

Destination:

stderr

ERZ096175E Environment variable ORACLE_SID notset

Explanation: The Oracle database instanceenvironment variable is not set. Hence it is not possibleto get connected to Oracle.


User response: Set the ORACLE_SID environmentvariable, then retry the command.

Destination:

stderr

ERZ096176I The Version is ’buffer’

Explanation: This message prints CICS Versioninformation

System action: Nothing.

User response: Nothing

Destination:

stderr

ERZ096177E The CICS version file (’buffer’) ismissing

Explanation: This message will be printed if cicsversion file is missing

System action: Version will not be printed

User response: Contact Support Team

Destination:

stderr

ERZ096167E • ERZ096177E


ERZ096178I The region ’buffer’ has been stopped

Explanation: This message prints cics region status asstopped



Destination:

ERZ096180E Error while fetching status of all ’buffer’

Explanation: This message is printed when an errorencountered while cicscp status all is issued



Destination:

stderr

ERZ096181I The region ’regionName’ is stopping

Explanation: This message is output during theprocessing of a ’status region’ command and if theregion is really stopping. It is only output if theverbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096182I The region ’regionName’ is recovering

Explanation: This message is output during theprocessing of a ’status region’ command and if theregion is performing recovery. It is only output if theverbose output flag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096183W cicscp encountered RPC timeout(’regionName’)

Explanation: This message is output during theprocessing of a ’cicscp start/status’ command and ifrpc timeout. It is only output if the verbose output flag(-v) is specified to cicscp.

System action: None

User response: Check whether region’s cicsrl processis running Or a transaction can be submitted via RPCchannel. If the both test are ok and the rpc timeoutpersists, please contact Support Team.

Destination:

stderr

ERZ096184E cicscp encountered genericerror(cics/system=regionName/%2$d)

Explanation: This message is output during theprocessing of a ’cicscp’ command. Cause may begeneric. If the problem encounters, please contactSupport Team. It is only output if the verbose outputflag (-v) is specified to cicscp.

System action: None

User response: None

Destination:

stderr

ERZ096185E Invalid argument ’InvalidArgument’ forcicscp command

Explanation: This message is output when a cicscpcommand detects that invalid argument was suppliedthan it was expecting.

System action: An error is returned and the commandfails.

User response: Correct the command and retry.

Destination:

stderr

ERZ100001I Usage: cicsterm [-?] [-r regionName] [-nnetName] [-m modelId] [-t transId] [-A[animatorTTY] [-T animatorTERM]] [-hhostList]

Explanation: cicsterm was invoked with incorrectarguments. This message gives a summary of theoptions available. It can also be also produced bygiving the -? option.


User response: Invoke cicsterm with correctparameters.

Destination:

stderr

ERZ100002I Usage: cicstermp [-?] -r regionName -nnetName [-f font] [-M paperType] [-pprinterType] [-P printCommand] [-R] [-sfontSize] [-t transaction] [-h hostList][-S]

Explanation: cicstermp was invoked with incorrectarguments. This message gives a summary of theoptions available. It can also be also produced bygiving the -? option.

ERZ096178I • ERZ100002I


System action: cicstermp terminates

User response: Invoke cicstermp with correctparameters.

Destination:

stderr

ERZ100003E Invalid option -optionName

Explanation: The option -optionName is not valid.


User response: Issue the command with correctparameters as shown in the following usage message.

Destination:

stderr

ERZ100004E The option -optionName requires anargument

Explanation: A required argument was not suppliedfor the option -’optionName’. Note that the -A option isrequired unless the DISPLAY environment variable isset to the name of a valid X server.


User response: Add the required argument.

Destination:

stderr

ERZ100005E cicstermp requires both -n netName and-r regionName arguments.

Explanation: cicstermp was invoked withoutspecifying the mandatory parameters -n netName and-r regionName.


User response: Invoke cicstermp with both the -n and-r options.

Destination:

stderr

ERZ100006E Incompatible options ’-n’ and ’-m’supplied to cicsterm.

Explanation: cicsterm was invoked with both the -mand -n options. Only one of these can be specified.


User response: Remove one of the options -m or -n.

Destination:

stderr

ERZ100007W Region name is too long - truncated to’regionName’.

Explanation: cicsterm or cicstermp has truncated yourregion name because it contained too many characters.

System action: cicsterm/cicstermp attempts toconnect to ’regionName’.

User response: Invoke cicsterm or cicstermp with avalid region name.

Destination:

stderr

ERZ100008W Netname is too long - truncated to’netName’.

Explanation: cicsterm or cicstermp has truncated yournetname because it contained too many characters.

System action: cicsterm/cicstermp attempts to installyour terminal with netname ’netName’.

User response: Invoke cicsterm or cicstermp with avalid netname.

Destination:

stderr

ERZ100009E file ’fileName’, line lineNumber: cannotload file ’fileToLoad’. Hit Enter tocontinue.

Explanation: An error occurred at line lineNumberduring the processing of the key mapping file ’fileName’while attempting to load file ’fileToLoad’.


User response: Check that the file ’fileToLoad’ existsand can be accessed by cicsterm.

Destination:

stderr

ERZ100010E file ’fileName’, line lineNumber: syntaxerror near ’tokenInError’. Hit Enter tocontinue.

Explanation: An error occurred at line lineNumberduring the processing of the key mapping file’fileName’. The problem was related to the token’tokenInError’.


User response: Fix line lineNumber of file ’fileName’.

Destination:

stderr

ERZ100003E • ERZ100010E


ERZ100011I Searching for available regions. Pleasewait.

Explanation: cicsterm is looking for a list of regionsbefore it displays the region menu.

System action: cicsterm continues to search foravailable regions.

User response: Wait until the region menu appears oran error message is issued.

Destination:

stderr

ERZ100012E No Regions available.

Explanation: cicsterm was unable to find anyavailable regions.


User response: Ensure that at least one region isrunning and check the region startup messages to see ifany problems were encountered trying to register theregion with the nameservice.

Destination:

stderr

ERZ100013E Invalid selection, position cursor onselected region.

Explanation: You have placed the cursor on a line thatdoes not have a region. Reposition the cursor on theline displaying the region you wish to connect to.


User response: Move cursor to the row displaying theregion of your choice.

Destination:

stderr

ERZ100014E Failed to initialize: errorText.

Explanation: cicsterm was unable to initialize for thereason specified by ’errorText’.


User response: Correct any error indicated by’errorText’. Check that cicssetupclients was run on thismachine and that the user has access tovarDir/cics_clients/*.key. (Usually the user must be amember of the cicsterm group.)

Destination:

stderr

ERZ100015E Failed to add terminal: errorText.

Explanation: cicsterm was unable to add a terminal tothe region for the reason specified by ’errorText’.


User response: Correct any error indicated by’errorText’. Check that the region specified is correct andthat the region is active. Also check that the device typeor netname specified on the cicsterm command wasvalid for the region.

Destination:

stderr

ERZ100016E Failed to get event from region: errorText.

Explanation: cicsterm experienced an error whilewaiting for data from the region.


User response: Correct any error indicated by’errorText’. If the problem persists, please report detailsto your support organization.

Destination:

stderr

ERZ100017E Memory allocation error.

Explanation: cicsterm was unable to allocate memoryneeded for its internal processing.


User response: Close other processes to free memoryor wait until the system is less busy.

Destination:

stderr

ERZ100018I Entering subshell. Type ’exit’ to returnto cicsterm.

Explanation: The user has requested that cicstermstarts a subshell process to allow system commands tobe processed. Control is passed to this process until it isended.

System action: cicsterm resumes when the subshell iscompleted.

User response: The subshell is available for use. Aftercompleting tasks using the subshell, type ’exit’ andreturn to cicsterm.

Destination:

stderr

ERZ100011I • ERZ100018I


ERZ100019E Failed to open tty: errorCode.

Explanation: cicsterm attempted to open /dev/tty forits display but received error ’errorCode’ from open().


User response: If the problem persists, please reportdetails to your support organization.

Destination:

stderr

ERZ100020E Failed to start child thread.

Explanation: cicsterm failed while trying to create oneof its threads of execution.


User response: Close other processes to free memoryor wait until the system is less busy. If the problempersists, please report details to your supportorganization.

Destination:

stderr

ERZ100021I Connecting to region ’regionName’.

Explanation: cicsterm has started to connect to region’regionName’.

System action: cicsterm continues connecting to theregion.

User response: Wait until connection is successful oran error message is issued.

Destination:

stderr

ERZ100022E Failed to initialize 3270 screenmanagement: reasonCode.

Explanation: cicsterm was unable to initialize itsinternal screen and keyboard management subsystem.A reason code is specified by reasonCode.


User response: Check that there is enough memoryavailable for cicsterm. Check that the CICS 3270display subsystem is correctly configured. In particular,on UNIX, check that rc.cics was run after the machinewas last started. Also check that a valid key mappingfile is present (either $HOME/.3270keys or/etc/3270.keys) and can be accessed by cicsterm. If theproblem persists, please report details to your supportorganization.

Destination:

stderr

ERZ100023E Failed to resize terminal.

Explanation: The terminal definition selected for useby cicsterm is for a display size other than 24*80.cicsterm experienced an error while allocating extrastorage required to handle the larger display.


User response: Specify a different netname or devtypeon the cicsterm command line, close other processes tofree memory or wait until the system is less busy.

Destination:

stderr

ERZ100024E Error received from 3270 displaysubsystem.

Explanation: cicsterm experienced an error attemptingto read from or write to its internal 3270 displayhandling functions.


User response: If the problem persists, please reportdetails to your support organization.

Destination:

stderr

ERZ100025E Transaction ’transId’ rejected - ’reason’.

Explanation: The transaction ’transId’ was submittedto the Transaction Scheduler (TS), but the TS rejectedthe request for the reason given in ’reason’.


User response: Check that you entered the correcttransaction name. Check that transaction ’transId’ iscorrectly defined in the Transaction Definitions (TD).Also check other messages for signs of problems withthe TS.

Destination:

stderr

ERZ100026E Failed to display help.

Explanation: A request for help was made using PF1,but cicsterm was unable to access and display theinformation.

System action: cicsterm continues but no help isdisplayed.

User response: Check that the CICS help files arecorrectly installed. If the underlying help system hasdisplayed any messages, ensure that it is also correctlyinstalled.

Destination:

ERZ100019E • ERZ100026E


stderr

ERZ100027E Failed to start subshell - SHELL notdefined in environment.

Explanation: A request was made to enter a subshell.However the environment variable SHELL was notdefined.

System action: cicsterm continues but the subshell isnot started.

User response: Exit cicsterm and set the value of theSHELL environment variable to specify the fullyqualified name of a shell executable. Start cicstermagain and retry the operation.

Destination:

stderr

ERZ100028E Failed to start subshell - start processfailed.

Explanation: A request was made to enter a subshell.However the attempt to start a new process failed.


User response: Check that there is enough memoryavailable to start a new process.

Destination:

stderr

ERZ100029E Failed to start subshell - internal failure.

Explanation: A request was made to enter a subshell,but an unexpected error has occurred within cicsterm.



Destination:

stderr

ERZ100030E Terminating signal ’signal’ received.

Explanation: cicsterm received an unexpected signalthat terminated the process.



Destination:

stderr

ERZ100031E Unexpected exception ’exception’received.

Explanation: cicsterm received an unexpectedexception and has terminated.


User response: If this terminating signal was notinitiated by the user, please report details of thisproblem to your support organization.

Destination:

stderr

ERZ100032E Maximum number of terminals alreadyactive.

Explanation: cicsterm cannot open another terminalwithin the current process.



Destination:

stderr

ERZ100033E Specified region cannot be reached.

Explanation: The region specified by the -r option wasnot found when cicsterm attempted to connect to it.


User response: Check that the region name wascorrectly specified and that the region is currentlyactive.

Destination:

stderr

ERZ100034E Unexpected error deleting terminal fromregion.

Explanation: cicsterm experienced an error whileattempting to delete the terminal from the region.

System action: cicsterm finishes terminating.

User response: If the problem persists, please contactyour support organization.

Destination:

stderr

ERZ100035I cicsterm terminated (region shutdown).

Explanation: cicsterm has terminated because theregion is being shut down.

System action: CICS continues to shut down; cicstermterminates.

ERZ100027E • ERZ100035I


User response: Wait for the region to be restarted orconnect to another region.

Destination:

stderr

ERZ100036I cicsterm terminated (terminaloutservice).

Explanation: cicsterm has terminated because theterminal was set out of service.


User response: Ask the System Administrator to putthe terminal back into service, or install as a differentterminal.

Destination:

stderr

ERZ100037E cicsterm terminated (network credentialsexpired).

Explanation: cicsterm has terminated because thenetwork credentials have expired.


User response: Refresh your credentials and theninvoke another cicsterm. If this fails, check that there isa valid keytab file in varDir/cics_clients. If there is not,run cicssetupclients.

Destination:

stderr

ERZ100038E cicsterm cannot be started within asubshell.

Explanation: cicsterm cannot be started from within ashell that was itself started from another invocation ofcicsterm.


User response: Exit from the current shell and returnto the previous invocation of cicsterm.

Destination:

stderr

ERZ100039I cicsterm terminated by user.

Explanation: cicsterm was terminated by a user actionsuch as entering Ctrl-C from the keyboard.


User response: None

Destination:

stderr

ERZ100040E Invalid terminal type: ’termType’.

Explanation: The TERM environment variable isincorrectly set. cicsterm is unable to initialize screenmanagement for the terminal type specified by thisvariable.


User response: Ensure that TERM is set to the nameof a valid terminal type.

Destination:

stderr

ERZ100041E No terminal type specified.

Explanation: cicsterm is unable to initialize screenmanagement for the terminal because the TERMenvironment variable is not set.


User response: Ensure that TERM is set to the nameof a valid terminal type.

Destination:

stderr


Explanation: cicsterm is attempting to find CICSregions. The terminal is now searching on machine’machineName’.


User response: No response is necessary.

Destination:

stderr


Explanation: cicsterm is attempting to find CICSregions.

System action: cicsterm continues but does not listany CICS regions from machine ’machineName’.

User response: Check that the cicsterm -h parameteris not set.

Destination:

stderr


Explanation: cicsterm has displayed warnings relatingto attempts to locate CICS regions on one or moremachines. These messages are displayed until the userhits Enter.

ERZ100036I • ERZ100044I


System action: cicsterm continues after Enter is hit.


Destination:

stderr

ERZ101001E XFH Initialization failure.

Explanation: While the External File Handler wasinitializing, an error occurred that preventedinitialization from continuing.

System action: Control returns to the application, butthe operation that requested initialization to beperformed is not done and an error code is returned.

User response: Attempt to rectify the problem byconsulting further messages in the Log File.

Destination:

log

ERZ101002E Failure to get number bytes of memory

Explanation: The External File Manager made arequest to the operating system to get number bytes ofmemory, but the request failed.

System action: Control returns to the application, butthe operation being performed is done and an errorcode is returned to the application.

User response: This error is most likely caused by anexcessively loaded system, and rerunning theapplication can possibly be successful. If the error doesreoccur, investigate any process or user limits in forcefor the session running the application.

Destination:

log

ERZ101003E The Statement CACHE is full

Explanation: The XFH maintains a limited set ofCURSORs that it uses to perform database operations.Under certain conditions a CURSOR is locked awaitinga second part to the operation. If the situation arisessuch that all CURSORs are locked, no further fileoperations can be performed.

System action: The operation returns a bad returncode to the application and the operation is notexecuted.

User response: Consult the documentation on how toexamine the Statement CACHE performance.

Destination:

log

ERZ101004E Failed to connect to database’databaseName’.″

Explanation: The External File Handler failed toconnect to the database ’databaseName’.

System action: An error is returned to the application,and no file system requests can be performed until asuccessful connect is performed. A second error canalso possibly be logged detailing the exact nature of thefailure.

User response: Check for any other message in the logfile that indicates insufficient authority or some othersecurity failure. If no other messages are logged, checkthat the database name specified is correct and that thedatabase is running.

Destination:

log

ERZ101005E Dynamic SQL failure.

Explanation: While executing a command a failureoccurred.

System action: An error is returned to the application,and a second message can possibly be logged detailingthe specific error.

User response: Check for any other message in the logfile that indicates the exact nature of the problem andrectify it.

Destination:

log

ERZ101006E Certain operations are not permitted viathe SQL File Handler for CICS

Explanation: The application executed an operationthat is not implemented by the CICS External FileHandler for SQL.

System action: An error is returned to the application.

User response: Rewrite the application to remove thecall.

Destination:

log

ERZ101007E The create file command failed.

Explanation: During an openfile request, the file wasfound not to exist and an attempt to create the file wasmade. This attempt failed.

System action: An error is returned to the application.The file is not created.

User response: Check for any other message in the logfile that indicates the exact nature of the problem andrectify it. If you must examine the exact structure of the

ERZ101001E • ERZ101007E


file being created or the statement that was executed,rerun the application with CICS Product Trace on.

Destination:

log

ERZ101008E The commit command failed.

Explanation: After an updatable operation an implicitcommit was performed but the commit failed.

System action: An error is returned to the application.The operation being performed was not completed.

User response: Check for any other message in log filethat indicates the exact nature of the problem andrectify it.

Destination:

log

ERZ101009E SQL Error: ’sqlText’

Explanation: While executing an SQL statement afailure occurred.

System action: An error code is returned to theapplication. This message is logged giving the SQLError text associated with this error.

User response: Using the error code returned and theSQL Error Message displayed, take the action necessaryto rectify the problem.

Destination:

log

ERZ101010E Bad field definition for RBA or RRN

Explanation: While opening a file, the record structurefor the table was verified and the definition of the firstfield did not match that required for Relative or RecordSequential file definitions.

System action: An error code is returned to theapplication.

User response: Verify the table structure and verifythat the table is a Relative or Record Sequential file.Check the log file for other messages that describe theerror in more detail.

Destination:

log

ERZ101011E Column Name columnName, Lengthcolumnlength, columnType SQL Type

Explanation: An error occurred while examining acolumn. This message is issued in conjunction withother messages to help identify the column in error.


User response: Use the information in the message toidentify what caused the error.

Destination:

log

ERZ101012E Illegal variable column detected atposition columnNumber in recorddefinition

Explanation: While opening a file, the record structurefor the table was verified and a variable length columnwas detected out of place. Only one variable lengthcolumn can be defined for a record, and it must be thelast column in the record definition.


User response: Verify the record definition for thetable and correct the definition.

Destination:

log

ERZ101013E Illegal column type detected, at positioncolumnNumber, in record definition

Explanation: CICS File Control on SQL supports onlya limited set of SQL Data Types. When opening a filean illegal data type was detected in the recorddefinition.



Destination:

log

ERZ101014E Bad SQL record definition at columncolumnNumber

Explanation: While verifying the SQL recorddefinition, a problem was encountered.

System action: An error code was returned to theapplication.


Destination:

log

ERZ101015E Database column columnNumber toolarge for application definition

Explanation: While verifying the SQL recorddefinition, a column length mismatch was detectedbetween the application defintion of the record and the

ERZ101008E • ERZ101015E


record definition in the database. A field boundarydefined by the application does not exist in the SQLrecord definition.


User response: Verify the record definition for the filein the application with the definition of the databasetable, and resolve the mismatch.

Destination:

log

ERZ101016E Bad Operation Code received by XFH(opCode)

Explanation: The XFH received a request to performan operation it does not support, or it received aninvalid Operation Code.


User response: Verify that no unsupported operationsare requested by the COBOL application and correctthem if necessary.

Destination:

log

ERZ101017E Maximum of fileNumber empty filesalready open with exclusive locks.

Explanation: There is a maximum of fileNumber emptyfiles opened with exclusive locks at any one time.


User response: Ensure that there is never more thanfileNumber files open with an exclusive tablesimultaneously.

Destination:

log

ERZ101018E Execution of External File Handlerhalted.

Explanation: The External File Handler encounteredan error situation.


User response: Consult preceding messages describingthe cause of the error and rectify any problems. Foradditional information, examine the log file for anyrelated messages.

Destination:

log

ERZ101019E Internal Error.

Explanation: The External File Handler encounteredan internal error.


User response: Consult preceding messages describingthe cause of the error and rectify any problems. Foradditional information, examine the log file for anyrelated messages.

Destination:

log

ERZ101020E Failed to re-establish exclusive file lockfor file fileName.

Explanation: When an exclusive lock is held againstan empty table, the lock is lost when a COMMIToperation is performed. It is therefore necessary for theExternal File Handler to reestablish the exclusive filelock after the COMMIT. The External File Handler wasattempting to do this but failed.

System action: The application is terminated.

User response: Consult preceding messages describingthe error in more detail and if necessary rectify anyproblems. For additional information, examine the logfile for any related messages.

Destination:

log

ERZ101021E Failure preparing SQL operations forfile ’fileName’

Explanation: The External File Handler was buildingthe SQL definitions required to operate on the filespecified but encountered an error.


User response: Consult preceding messages describingthe error in more detail and if necessary rectify anyproblems. For additional information, examine the logfile for any related messages.

Destination:

log

ERZ101022E SQL failure emptying file ’fileName’ ofrecords.

Explanation: When a file was being opened anattempt was made to delete all the records in the file,but this attempt failed.


User response: Consult preceding messages describingthe error in more detail and if necessary rectify anyproblems. For additional information, examine the log

ERZ101016E • ERZ101022E


file for any related messages.

Destination:

log

ERZ101023E File ’fileName’ does not exist.

Explanation: During the operation of the External FileHandler, a file that was supposed to exist was notfound.


User response: Verify that the file does not exist andrecreate the file if necessary.

Destination:

log

ERZ101024W Unable to get exclusive lock on tabletableName.

Explanation: During the operation of the External FileHandler, an attempt was made to take an exclusivetable lock on the table specified, but the attempt failed.


User response: Verify the reason for the failure usingthe diagnostic information produced using anypreceding messages, and rectify any problem.

Destination:

log

ERZ101025E Fatal Error occurred during XFHOperation. (’errorDescription’)TRANSLATION_GUIDELINE: none

Explanation: During the operation of the External FileHandler, an error occurred that was unable to behandled.


User response: Examine any related messages andtake the necessary action to correct the cuase of theerror.

Destination:

stderr

ERZ101026E Bad File Handle filEhandle passed toXFH. TRANSLATION_GUIDELINE:none

Explanation: A call was made to the XFH passing aninvalid file handle.


User response: Verify the application to ensure thatonly file handles returned from an open call are usedon subsequent calls to the XFH.

Destination:

log

ERZ101027E Data too large for internal buffer

Explanation: During the operation of the External FileHandler, an error occurred that caused an overflow onan internal buffer.


User response: Report the error to your supportrepresentative.

Destination:

log

ERZ102002I Configuring ’databaseName’ for region’regionName’.

Explanation: Database is being configured for theregion. This includes creation of tables for the CICSregion.


User response: None

Destination:

stderr

ERZ102003E Region ’regionName’ is running or isalready being configured. Configurationis not possible.

Explanation: DB2 cannot be configured for a regionwhile the region is running, or while it is beingconfigured by another user.


User response: If the region is running and aconfiguration change must be made then shutdown theregion. If another user is performing configuration forthe region then retry the command when thatconfiguration is complete.

Destination:

stderr

ERZ102004I Configuring ’databaseName’ table’tableName’ for recoverable auxiliaryTSQs for region ’regionName’

Explanation: The command is creating tables for theregion’s recoverable auxiliary Temporary StorageQueues (TSQs).


User response: None

Destination:

ERZ101023E • ERZ102004I


stderr

ERZ102005I Configuring ’databaseName’ table’tableName’ for non-recoverable auxiliaryTSQs for region ’regionName’

Explanation: The command is creating tables for theregion’s non-recoverable auxiliary Temporary StorageQueues (TSQs).


User response: None

Destination:

stderr


Explanation: The command encountered a problemrunning ’programName’.


User response: Refer to other messages displayed orin stderr. Check that CICS is installed correctly. Checkthat the program exists, is owned by user cics and hasread, write and execute permissions for its owner.

Destination:

stderr

ERZ102007I Configuring ’databaseName’ table’tableName’ for logically recoverableTDQs for region ’regionName’

Explanation: The command is creating Database tablesfor the region’s logically recoverable Transient DataQueues (TDQs).


User response: None

Destination:

stderr

ERZ102008I Configuring ’databaseName’ table’tableName’ for physically recoverableTDQs for region ’regionName’

Explanation: The command is creating Database tablesfor the region’s physically recoverable Transient DataQueues (TDQs).


User response: None

Destination:

stderr

ERZ102010I Configuring ’databaseName’ fornon-recoverable TDQs for region’regionName’

Explanation: The command is creating Database tablesfor the region’s non-recoverable Transient Data Queues(TDQs).


User response: None

Destination:

stderr

ERZ102011I Configuring ’databaseName’ table’tableName’ for protectedLocally-Queueing requests for region’regionName’

Explanation: The command is creating Database tablesfor the region’s Protected Locally-Queueing requests.


User response: None

Destination:

stderr

ERZ102012I Configuring ’databaseName’ table’tableName’ for unprotectedLocally-Queueing requests for region’regionName’

Explanation: The command is creating Database tablesfor the region’s Unprotected Locally-Queueing requests.


User response: None

Destination:

stderr

ERZ102013W NOTE: The created queue will betreated as recoverable.

Explanation: The user has requested a non-recoverablequeue. Because non-recoverable queues are notsupported by the DB2 file system, the queue is treatedas recoverable.


User response: Users that are dependent onnon-recoverable file semantics are recommended tomaintain such queues on a SFS supporting CICS region.

Destination:

stderr

ERZ102005I • ERZ102013W


ERZ102014W NOTE: The created queue will betreated as logically recoverable.

Explanation: The user has requested a physicallyrecoverable queue. Because physically recoverablequeues are not supported by the DB2 file system, thequeue is treated as logically recoverable.


User response: Users that are dependent on physicallyrecoverable queue semantics are recommended tomaintain such queues on a SFS supporting CICS region.

Destination:

stderr

ERZ102015W All unprotected STARTs are beinginternally protected.

Explanation: The user has requested a DB2 table forlocally queued Unprotected STARTs. DB2 acts as theresource manager for starts. All STARTs are written torecoverable queues.


User response: As it is not possible to store locallyqueued STARTs remotely. Users who are dependent onlocal unprotected STARTs must retain a local SFS serverto maintain these queues.

Destination:

stderr

ERZ102016I The product definition (XAD) created is’XAname’.

Explanation: The user has ’XAname’, system definedproduct definition (XAD).



Destination:

stderr

ERZ102020E You must be logged in as root on UNIXor as Administrator on Windows NT torun the ’programName’ command

Explanation: You attempted to run cicsdb2conf whenlogged on with insufficient authority. On UNIX youmust be logged on as root. On Windows NT you mustbe logged on with a userid with Administrator andcicsgroup authority.


User response: Log on correctly and retry thecommand.

Destination:

stderr

ERZ102023W Could not open log file ’logFile’.

Explanation: ’logFile’ was unable to be opened forwriting the configuration information.

System action: Command continues.

User response: Check the path and permissions on thepath and file.

Destination:

stderr

ERZ102024E Cannot bind to DB2 ’aliasName’, SQLreturn code <’SQLreturn’>.

Explanation: The connection to DB2 succeeded, butthe attempt to bind was unsuccessful. The return codeindicates the cause of the problem.


User response: Check the SQL return code to diagnoseand correct the problem.

Destination:

stderr

ERZ102025E Cannot connect to Oracle,’databaseInstance’, SQL return code<’SQLreturn’>.

Explanation: The attempt to connect to the Oracleinstance was unsuccessful. The return code indicatesthe cause of the problem.



Destination:

stderr

ERZ102026E Unable to create TSQ using table’fileName’.

Explanation: There was an error creating theTemporary Storage Queue (TSQ) ’fileName’ on DB2.

System action: The command abnormally terminatesunless you specified the ’-I’ option.

User response: Refer to preceding messages, fromcicsdb2conf, for the reason why the TSQ was unable tobe created. If the preceding message gives the detailson an already existing table on DB2 then the tablecannot be created because one already exists. You canignore this step and continue with subsequentconfiguration steps by retrying the request with ″Ignore

ERZ102014W • ERZ102026E


Errors″ selected (-I flag on command).

Destination:

stderr

ERZ102027E Unable to create TDQ using table’fileName’.

Explanation: There is an error creating the TransientData Queue (TDQ) ’fileName’ on DB2.

System action: The command abnormally terminatesunless you specified the ’-I’ option.

User response: Refer to preceding messages, fromcicsdb2conf, for the reason why the TSQ was unable tobe created. If the preceding message gives the detailson an already existing table on DB2 then the tablecannot be created because one already exists. You canignore this step and continue with subsequentconfiguration steps by retrying the command with″Ignore Errors″ selected (-I flag on command).

Destination:

stderr

ERZ102028E Unable to create Local Queue usingtable ’fileName’.

Explanation: An attempt to create a Local Queue (LQ)on DB2 was unsuccessful. The DB2 error code indicatesthe cause of the problem.

System action: The command continues if the -Ioption is set; otherwise, the command terminates.

User response: Refer to preceding messages, fromcicsdb2conf, for the reason why the TSQ was unable tobe created. If the preceding message gives the detailson an already existing table on DB2 then the tablecannot be created because one already exists. You canignore this step and continue with subsequentconfiguration steps by retrying the request with ″IgnoreErrors″ selected (-I flag on command).

Destination:

stderr

ERZ102029E Unable to update region definition.

Explanation: The command was unable to update theregion definition.


User response: Check the region definitions and retrythe command.

Destination:

stderr

ERZ102030I Configuration completed successfully.

Explanation: There were no problems reported duringconfiguration.


User response: None

Destination:

stderr

ERZ102031E To configure DB2 for CICS both anInstance Name and Alias Name must bespecified.

Explanation: Instance Name and Alias Name are bothmandatory on the cicsdb2conf command.


User response: Set both Instance Name and AliasName and retry the command.

Destination:

stderr

ERZ102033I Create system defined ’XA’ XAdefinition for region ’regionName’.

Explanation: User requested ’XA’, system defined XAdefinition.


User response: None

Destination:

stderr

ERZ102034E Creation of XA definition for region’regionName’ was unsuccessful.

Explanation: Region product definition (XAD) wasunable to be added to the CICS resource definitions.Other messages can indicate the source of the problem.


User response: Check that the region specified exists.Check that the access permissions for the directory/var/cics_regions/<region> are appropriate. Ensurethat it is owned by user cics and has read, write andexecute permissions for its owner.

Destination:

stderr

ERZ102027E • ERZ102034E


ERZ102035I Update the region definitions (RD) forregion ’regionName’ for ’databaseName’configuration.

Explanation: Update of the RD definitions is inprogress.


User response: None

Destination:

stderr

ERZ102036E Update of the region definitions (RD)for region ’regionName’ was unsuccessful.

Explanation: The region definition (RD) was unable tobe added to the CICS resource definition. Othermessages can indicate the source of the problem.



Destination:

stderr

ERZ102037I The FileServer attribute in the filedefinitions (FD) for region ’regionName’will not be changed.

Explanation: The -f option on the cicsdb2confcommand was set to NULL. The FileServer attribute inthe file definition (FD) is not changed.


User response: None

Destination:

stderr

ERZ102038I Update of file definitions (FD) forregion ’regionName’ for ’databaseName’configuration.

Explanation: Update of the file definitions (FD) is inprogress.


User response: None

Destination:

stderr

ERZ102039E Update of the file definitions (FD) forregion ’regionName’ was unsuccessful.

Explanation: The file definition (FD) was unable to beadded to the CICS resource definition. Other messagescan indicate the source of the problem.


User response: Check that the specified file exists.Check that the access permissions for the file areappropriate. Ensure that it is owned by user cics andhas read, write permissions for it’s owner.

Destination:

stderr

ERZ102040E Usage: cicsdb2conf [-I] [-m] -rregionName [-l logFileName] {-C -iinstanceName -a aliasName [-f] [-g][-n|-s] [-u userName[,password]]|[-S][-N][-D][-P][-T][-L][-Q] [-ttablespace]}

Explanation: You entered the cicsdb2conf commandincorrectly.



Destination:

stderr

ERZ102041W Object ’fileName’ already exists

Explanation: Table ’fileName’ already exists on DB2.

System action: Processing continues, but othermessages are produced as a result of this error that cancause the command to terminate.

User response: If necessary you can destroy theexisting object using the database administrationcommands.

Destination:

stderr

ERZ102042E Cannot find the specified region.

Explanation: cicsdb2conf was unable to find or accessthe named region.



Destination:

ERZ102035I • ERZ102042E


stderr

ERZ102043E DB2 Alias ’aliasName’, is not defined inthe Product Definition file (XAD).

Explanation: The program expects to find ’aliasName’in the XAOpen string in Product Definitions file (XAD).The Alias Name in the XAOpen string and theDefaultFileServer in the Region Definitions (RD) mustmatch.


User response: Check that the region is successfullyconfigured for DB2 and the product definitions file(XAD) is not corrupted.

Destination:

stderr

ERZ102044E Environment variable ’databaseInstance’ isnot set

Explanation: The appropriate database instancevariable was not set, cicsdb2conf/cicsoraconf cannotaccess database resources.


User response: export DB2INSTANCE=<instance id>before invoking cicsdb2conf.

Destination:

stderr

ERZ102045E Could not access user information for’userId’

Explanation: The DB2INSTANCE owner id <userid>does not exist.


User response: Set up the DB2 instance owner id asdetailed in the DB2 Installation and Operation Guide.

Destination:

stderr

ERZ102046E Cannot ’SQLstatement’, SQL return code<’SQLreturn’>.

Explanation: The shown SQL statement wasunsuccessful. The return code indicates the cause of theproblem.



Destination:

stderr

ERZ102047W Cannot expand file ’fileName’

Explanation: cicsdestroy attempted to delete cics datayou have on DB2, but was unable to get the full nameof the DB2 file to delete.

System action: The command continues, but thenamed file possibly needs to be deleted by hand.

User response: Once cicsdestroy has completed, checkfor remaining DB2 files and delete them manually. Thiswarning possibly indicates a problem with your CICSinstallation.

Destination:

stderr

ERZ102048E Failed to create table ’tableName’

Explanation: An SQL error occurred while trying tocreate the table.



Destination:

stderr

ERZ102049E Failed to add index ’indexName’

Explanation: An SQL error occurred while trying toadd the index.



Destination:

stderr

ERZ102050E Unable to get CICS information

Explanation: cicsdb2conf was unable to getinformation on your cics region.

System action: The command terminatesunsuccessfully.

User response: Check that you have installed cicscorrectly. Check that your region is defined correctlyand that you have permissions to read it.

Destination:

stderr

ERZ102051E Unable to allocate ’memorySize’ bytes ofstorage

Explanation: cicsdb2conf was unable to allocate theamount of memory shown.

ERZ102043E • ERZ102051E


System action: The command terminatesunsuccessfully.

User response: Check that you have sufficientresources on your machine to perform the requestedaction.

Destination:

stderr

ERZ102052E Usage: cicsoraconf [-I] [-m] -rregionName [-l logFileName]{-C|-S|-N|-D|-P|-T|-L|-Q} [-iinstance] [-f] [-g] [-s] -uuserName[/password] [-xuserName/password] [-t tableSpace]

Explanation: You entered the cicsoraconf commandincorrectly.



Destination:

stderr

ERZ102053E To configure ORACLE for CICS specifythe instance ($ORACLE_SID)

Explanation: Instance Name and Alias Name are bothmandatory on the cicsdb2conf command.


User response: Set both Instance Name and AliasName and retry the command.

Destination:

stderr

ERZ102054W An Oracle request failed because:’errorMessage’

Explanation: The program issued and SQL commandthat returned an error code. The text describing theerror is contained in this message. This can be anacceptable error such as the failure of a table createbecause it was created previously, or a more seriouserror such as insufficient space to create the table.

System action: The command either fails or runs tocompletion, depending on which SQL command failedand the -I invocation parameter.

User response: Determine if the error was acceptablegiven the circumstances in which the program was run.If the error was not acceptable then refer to the Oracledocumentation to determine the correct course ofaction.

Destination:

stderr

ERZ102055E An Oracle administration userid mustbe specified

Explanation: A userid with Oracle administrationauthority must be specified via the -u parameter on thecicsoraconf command. This id is required to allowcicsoraconf to configure the Oracle tables that are usedby CICS for its queue management.

System action: The cicsoraconf command isterminated.

User response: Determine the Oracle administration idto use and reinvoke the cicsoraconf command with the-u parameter specifying the Oracle administrationuserid. You also need the password, which can bespecified as part of the -u parameter or via theCICSORAPASSWORD environment variable; otherwise,you are prompted for it.

Destination:

stderr

ERZ102056E A password is mandatory when a useridis specified on the -x parameter

Explanation: The -x parameter was specified on thecicsoraconf command but only a userid was specified.A password is mandatory if a userid is specified.

System action: The cicsoraconf command isterminated.

User response: Determine the Oracle password for thespecified userid and rerun the cicsoraconf specifyingthe password.

Destination:

stderr

ERZ102057I Creating the Oracle table

Explanation: The cicsoraconf utility is creating theOracle table for the cics file as indicated in the previousmessage.

System action: The cicsoraconf command continues.

User response: None

Destination:

stderr

ERZ102058I Creating the Oracle table index

Explanation: The cicsoraconf utility is creating theOracle table index for the cics file as indicated in theprevious message.

System action: The cicsoraconf command continues.

ERZ102052E • ERZ102058I


User response: None

Destination:

stderr

ERZ102059E Cannot connect to DB2, SQL return code’SQLreturn’.

Explanation: The attempt to connect to DB2 wasunsuccessful. The return code indicates the cause of theproblem.



Destination:

stderr

ERZ102060W DB2 warning - SQLstatement, SQL returncode <’SQLreturn’>.

Explanation: The shown SQL statement wasunsuccessful but processing continues. The return codeindicates the cause of the problem.

System action: The command continues but canpossibly result in abnormal termination returning thevalue 1.


Destination:

stderr

ERZ102061I Modifying entry ’EntryName’ in databasemanager configuration file.

Explanation: CICS requires certain database managerparameters to be set. Trying to configure theseparameters in the database. Database needs to berestarted for the changes to be effective.



Destination:

stderr

ERZ102062E Failed to configure entry ’EntryName’ indatabase manager configuration file.

Explanation: Main reasons for the failure are databaseconnection failure or preexisting invalid value. Forfurther explaination look at the other messages.

System action: The command continues if the -Ioption is set; otherwise, the command terminates.

User response: Refer to the preceding messages andcorrect the problem.

Destination:

stderr

ERZ102063W User ’UserID’ does not have dbadmauthority.

Explanation: User connected to the database doesnothave dbadm authority.

System action:

User response: authority should be granted to theuser by connecting to the database.

Destination:

stderr

ERZ104001W Invalid PF or PA key pressed

Explanation: You have pressed an undefined programfunction (PF) or program attention (PA) key.

System action: CICS ignores the keystroke.

User response: Use a valid PF or PA key. Valid keysare displayed at the bottom of the screen. You can alsouse the enter key.

Destination:

CDCN user terminal

ERZ104002I CDCN has ended normally. Ready fornext transaction.

Explanation: This is the message displayed whenCDCN terminates.



Destination:

CDCN user terminal

ERZ104003E You must specify a display name for thedebugging information

Explanation: You have not specified the name of anoutput display for the debugging information to bedisplayed on.

System action: CDCN waits for input of the name ofan X-windows display.

User response: Specify the name of a validX-windows display in the DISPLAY field of the BMSmap before retrying the operation.

Destination:

CDCN user terminal

ERZ102059E • ERZ104003E


ERZ104004E Terminal identifier ’termId’ is invalid

Explanation: You did not specify a valid terminalidentifier for the TERMID option.

System action: CDCN waits for input of a validterminal identifier.

User response: Specify a valid, existing terminalidentifier in the TERMID field of the BMS map beforeretrying the operation. You can leave the TERMIDoption blank, in which case the terminal identifier ofthe current, CDCN user terminal is used.

Destination:

CDCN user terminal

ERZ104005E System identifier ’sysId’ is invalid

Explanation: You specified an invalid system identifierfor the SYSID option.

System action: CDCN waits for input of a validsystem identifier.

User response: Specify a valid, existing systemidentifier in the SYSID field of the BMS map beforeretrying the operation. You can choose to leave theSYSID option blank and not configure debugging for asystem identifier.

Destination:

CDCN user terminal

ERZ104006E Transaction identifier ’transId’ is invalid

Explanation: You specified an invalid transactionidentifier for the TRANSID option.

System action: CDCN waits for input of a validtransaction identifier.

User response: Specify a valid, existing transactionidentifier in the TRANSID field of the BMS map beforeretrying the operation. You can choose to leave theTRANSID option blank and not configure debuggingfor a transaction identifier.

Destination:

CDCN user terminal

ERZ104007E Program identifier ’programName’ isinvalid

Explanation: You specified an invalid programidentifier for the PROGRAM option.

System action: CDCN waits for input of a validprogram identifier.

User response: Specify a valid, existing programidentifier in the PROGRAM field of the BMS mapbefore retrying the operation. You can choose to leavethe PROGRAM option blank and not configure

debugging for a program identifier.

Destination:

CDCN user terminal

ERZ104008E Invalid input ’invalidInput’ detected

Explanation: You have supplied invalid input asindicated. The problem can be an invalid option,specifying the same option more than once, specifyingmutually exclusive options (ON and OFF together),specifying an invalid parameter to an option wherenone was expected, or specifying more than oneparameter for a command that requires a singleparameter. The options that expect one parameter areTERMID, SYSID, TRANSID, PROGRAM and DISPLAY.The options that expect no parameter are ON or OFF.

System action: CDCN did not execute the command.CDCN waits for valid input.

User response: Enter valid input data.

Destination:

CDCN user terminal

ERZ104009E Debugger uninstalled or installedincorrectly

Explanation: You attempted to use CDCN to debug aCICS transaction, but CICS has detected a problemstarting the debugger. This can be because it is notinstalled or was installed incorrectly.

System action: The transaction runs without debug.

User response: Ensure that the debugger is installedcorrectly. In particular ensure that the xldb executableis in /usr/lpp/xldb/bin, and has execute permissionsset on it.

Destination:

CDCN user terminal

ERZ104010I Successfully configured debugging onfor ’resources’

Explanation: CDCN/CADB has successfullyconfigured debugging on for the specified resources.

System action: Transactions run using the aboveresources are debugged.


Destination:

console.msg

ERZ104004E • ERZ104010I


ERZ104011I Successfully configured debugging offfor ’resources’

Explanation: CDCN/CADB has successfullyconfigured debugging off for the specified resources.

System action: Transactions run using the aboveresources are no longer debugged.


Destination:

console.msg

ERZ104012I Successfully configured debugging onfor terminal ’termId’

Explanation: The debugging configuration for thenamed terminal was successful. CDCN was able toinitialize the debugging process.

System action: CDCN terminates if the requestedconfiguration is successful for all specified resources,otherwise it continues. The next transaction to be runon the named terminal is debugged, providing that allthe relevant security checks are satisfied.


Destination:

CDCN user terminal

ERZ104013E Attempt to configure debugging on forterminal ’termId’ was unsuccessful

Explanation: CICS has tried to configure debuggingon for the named terminal, but startup of thedebugging process was not successful. One possibilityis that the ’exec’ of the debugging process did notsucceed. Another is that the debugging processencountered a problem and so returned a bad responsecode to CICS. A third possibility is that because CICSonly waits a specific time interval for the debuggingprocess to start, it is possible that the debuggingprocess did not start within the allowed time period.

System action: The CICS region and the CICSapplication server continue. A debugging process wasnot started, so a transaction initiated on the namedterminal is not debugged unless debugging isconfigured for that transaction, or associated program.

User response: Investigate the reason that the start ofthe debugging process did not succeed. Ensure that theprograms required in order to perform debugging arecorrectly installed. If the debugging process does finallystart, it is possible that CICS gave up waiting too soon.If the machine is heavily loaded and response times areslow, consider attempting to configure debugging againwhen response times improve.

Destination:

CDCN user terminal

ERZ104014E CDCN could not update the TerminalDefinition for terminal ’termId’

Explanation: CDCN attempted to alter debuggingconfiguration information in the database entry for thenamed terminal but was unable to update the TerminalDefinition in the runtime database.

System action: The debugging configuration for thenamed terminal is not changed. CDCN terminates.

User response: Examine the CICS message files asCICS possibly wrote other messages that indicate whythe attempt to update the runtime database wasunsuccessful. If appropriate, repeat the attempt toconfigure debugging.

Destination:

CDCN user terminal

ERZ104015E CDCN could not update theCommunication Definition for system’sysId’

Explanation: CDCN attempted to alter debuggingconfiguration information in the database entry for thenamed system but was unable to update theCommunication Definition in the runtime database.

System action: The debugging configuration for thenamed system is not changed. CDCN terminates.


Destination:

CDCN user terminal

ERZ104016E CDCN could not update the TransactionDefinition for transaction ’transId’

Explanation: CDCN attempted to alter debuggingconfiguration information in the database entry for thenamed transaction but was unable to update theTransaction Definition in the runtime database.

System action: The debugging configuration for thenamed transaction is not changed. CDCN terminates.


Destination:

CDCN user terminal

ERZ104011I • ERZ104016E


ERZ104017E CDCN could not update the ProgramDefinition for program ’programName’

Explanation: CDCN attempted to alter debuggingconfiguration information in the database entry for thenamed program but was unable to update the ProgramDefinition in the runtime database.

System action: The debugging configuration for thenamed program is not changed. CDCN terminates.


Destination:

CDCN user terminal

ERZ104018I Successfully configured debugging onfor system ’sysId’

Explanation: The debugging configuration for thenamed system was successful. CDCN was able toinitialize the debugging process.

System action: CDCN terminates if the requestedconfiguration is successful for all specified resources,otherwise it continues. The next transaction request tobe run that originated from the named system isdebugged, providing that all the relevant securitychecks are satisfied.


Destination:

CDCN user terminal

ERZ104019E Display identifier ’displayId’ is invalid

Explanation: You specified an invalid displayidentifier for the DISPLAY option.

System action: CDCN waits for input of a validdisplay identifier.

User response: Specify a valid display identifier in theDISPLAY field of the BMS map before retrying theoperation. You must specify a value for the DISPLAYoption when you configure debugging on.

Destination:

CDCN user terminal

ERZ104020E CDCN cannot configure debugging forremote terminal ’termId’

Explanation: You specified a remote terminal for theTERMID option but CDCN can only configuredebugging for local terminals.

System action: CDCN waits for input of a valid, localterminal identifier.

User response: Specify a valid terminal identifier inthe TERMID field of the BMS map before retrying theoperation. To debug transactions run against terminalsthat are not local, specify the system identifier of theremote system that originates the inbound transactionrequests in the SYSID field of the BMS map beforeretrying the operation.

Destination:

CDCN user terminal

ERZ104021E CDCN cannot configure debugging forlocal system ’sysId’

Explanation: You specified the local system for theSYSID option but CDCN can only configure debuggingfor remote systems.

System action: CDCN waits for input of a valid,remote system identifier.

User response: Specify a valid system identifier in theSYSID field of the BMS map before retrying theoperation. To debug transactions originated on the localsystem, specify the terminal identifier of the localterminal that originates the transaction requests in theTERMID field of the BMS map before retrying theoperation. Alternatively, CDCN can be used toconfigure debugging for individual transactions andprograms using the TRANSID and PROGRAM fieldsrespectively.

Destination:

CDCN user terminal

ERZ104022W CDCN not supported. Ready for nexttransaction.

Explanation: The CDCN transaction can onlyconfigure debugging using xldb for AIX, so valid use ofCDCN is limited to a CICS for AIX system. Use ofCDCN on a CICS region other than a CICS for AIXregion results in the above message. CDCN then exitsbecause it cannot configure debugging for the region.



Destination:

CDCN user terminal

ERZ104023E Attempt to display help wasunsuccessful

Explanation: CDCN was not able to display the helprequested.

System action: CDCN continues.

User response: Examine the CICS message files asCICS possibly wrote other messages that indicate why

ERZ104017E • ERZ104023E


the attempt to display help was unsuccessful.

Destination:

CDCN user terminal

ERZ104024E CDCN cannot configure debugging for aremote terminal

Explanation: An attempt was made to start CDCNother than directly from a local terminal, but CDCNcan only be invoked directly from a terminal that islocal to the CICS region.

System action: CDCN terminates abnormally.

User response: Invoke CDCN directly from a cicstermthat is on the same system as the CICS region.

Destination:

CDCN user terminal

ERZ104025E CDCN could not access the TerminalDefinition for ’termId’

Explanation: CDCN encountered an error while tryingto obtain information about the named terminal fromthe region database. Further information is possiblyavailable in one of the CICS message files.

System action: CDCN waits for input of a validterminal identifier.

User response: Ensure that the terminal definition isinstalled correctly in the region database. Refer to anyassociated messages in the CICS symptom records andconsole.msg files for further guidance on resolving theproblem. You can leave the TERMID option blank, inwhich case the terminal identifier of the current, CDCNuser terminal is used.

Destination:

CSMT

ERZ104026E CDCN could not receive any commandline options

Explanation: CDCN tried unsuccessfully to receiveany options specified when CDCN was invoked. This ispossibly due to your cicsterm session being unavailableto CICS. Further information is possibly available inone of the CICS message files.


User response: Check that the cicsterm session inwhich CDCN is running is still active. Check that thescreen is properly connected and configured. Refer toany associated messages in the CICS symptom recordsand console.msg files for further guidance on resolvingthe problem.

Destination:

CSMT

ERZ104027E CDCN could not read a message fromthe CICS message catalog

Explanation: An attempt to read a CDCN messagefrom the CICS message catalog was unsuccessful.


User response: Check that the CICS message catalogfor the region is accessible and has the requiredpermissions. Refer to operating system documentationfor further information about the use of catalogs.

Destination:

CSMT

ERZ104028E CDCN could not access theCommunication Definition for ’sysId’

Explanation: CDCN encountered an error while tryingto obtain information about the named system from theregion database. Further information is possiblyavailable in one of the CICS message files.

System action: CDCN waits for input of a validsystem identifier.

User response: Ensure that the system definition isinstalled correctly in the region database. Do notspecify the local system. Refer to any associatedmessages in the CICS symptom records andconsole.msg files for further guidance on resolving theproblem. You can choose to leave the SYSID optionblank and not configure debugging for a systemidentifier.

Destination:

CSMT

ERZ104029E CDCN could not access the TransactionDefinition for ’transId’

Explanation: CDCN encountered an error while tryingto obtain information about the named transaction fromthe region database. Further information is possiblyavailable in one of the CICS message files.


User response: Ensure that the transaction definitionis installed correctly in the region database. Refer toany associated messages in the CICS symptom recordsand console.msg files for further guidance on resolvingthe problem. You can choose to leave the TRANSIDoption blank and not configure debugging for atransaction identifier.

Destination:

CSMT

ERZ104024E • ERZ104029E


ERZ104030E CDCN cannot configure debugging for aremote transaction″

Explanation: An attempt was made to use CDCN toconfigure debugging for a remote transaction, butCDCN can only configure debugging for a transactionthat is local to the CICS region.


User response: Specify a local, existing transactionidentifier in the TRANSID field of the BMS map beforeretrying the operation. You can choose to leave theTRANSID option blank and not configure debuggingfor a transaction identifier.

Destination:

CDCN user terminal

ERZ104031E CDCN could not access the ProgramDefinition for ’programName’

Explanation: CDCN encountered an error while tryingto obtain information about the named program fromthe region database. Further information is possiblyavailable in one of the CICS message files.


User response: Ensure that the program definition isinstalled correctly in the region database. Refer to anyassociated messages in the CICS symptom records andconsole.msg files for further guidance on resolving theproblem. You can choose to leave the PROGRAMoption blank and not configure debugging for aprogram identifier.

Destination:

CSMT

ERZ104032E Unsuccessful memory allocation fordebugging control information

Explanation: An attempt to allocate storage from theRegion Pool to contain debugging control informationwas unsuccessful. As memory in the Region Pool iscontinually being acquired and freed by CICS on behalfof running transactions, this is possibly a transientproblem that can occur when CICS is heavily loaded.

System action: The CICS region and the CICSapplication server continue. The debugging process isnot attached to any transactions or programs run in theapplication server until CICS successfully allocates theregion storage it requires.

User response: Try running the transaction again. Ifthis problem persists when you resubmit thetransaction, check whether it is looping in some waythat causes CICS to acquire substantial amounts ofRegion Pool memory on its behalf.

Destination:

CSMT

ERZ104033E Unsuccessful open of pipe ’fileName’,operating system code errorCode

Explanation: An attempt to open a named pipe usedto communicate with the debugging process wasunsuccessful. CICS uses named pipes to sendcommands to the debugging process, and also toreceive responses back from the debugging process.CICS opens the pipes when it is about to send acommand to the debugging process. As this open wasunsuccessful, the command is not sent to thedebugging process.

System action: The CICS region and the CICSapplication server continue. The state of the debuggingprocess is not changed, but CICS assumes that it hasdied and so does not issue any further commands to it.

User response: Investigate the reason that the ’open’system call did not succeed. Refer to the errno.h systemheader file for an explanation of the operating systemerror code value. Ensure that the named pipe exists andhas the correct permissions for CICS to access the pipe.

Destination:

CSMT

ERZ104034E Unsuccessful write to pipe ’fileName’,operating system code errorCode

Explanation: An attempt to write to a named pipeused to communicate with the debugging process wasunsuccessful. CICS uses named pipes to sendcommands to the debugging process. As this write wasunsuccessful, the command is not sent to thedebugging process.

System action: The CICS region and the CICSapplication server continue. The state of the debuggingprocess is not changed, but CICS assumes that it hasdied and so does not issue any further commands to it.

User response: Investigate the reason that the ’write’system call did not succeed. Refer to the errno.h systemheader file for an explanation of the operating systemerror code value. Ensure that the named pipe exists andhas the correct permissions for CICS to access the pipe.CICS can only write to a pipe if the debugging processhas opened the same pipe for reading, so check that thedebugging process is active and can also access thepipe.

Destination:

CSMT

ERZ104030E • ERZ104034E


ERZ104035E Timeout period expired before responseread from pipe ’fileName’

Explanation: A read from a named pipe used toreceive responses from the debugging process did notreturn a response within the timeout period. CICS usesnamed pipes to send commands to the debuggingprocess, and also to receive responses back from thedebugging process. As CICS did not receive a responsein the allowed time, CICS assumes that the debuggingprocess has died.

System action: The CICS region and the CICSapplication server continue. The state of the debuggingprocess is not known, but CICS assumes that it hasdied and so does not issue any further commands to it.

User response: Investigate the reason that the ’read’system call did not succeed. Ensure that the namedpipe exists and has the correct permissions for CICS toaccess the pipe. CICS can only read a response from thepipe if the debugging process has opened the samepipe for writing and has written to the pipe, so checkthat the debugging process is active and can also accessthe pipe.

Destination:

CSMT

ERZ104036E Error response received on pipe’fileName’

Explanation: A read from a named pipe used toreceive responses from the debugging process returneda bad response. CICS uses named pipes to sendcommands to the debugging process, and also toreceive responses back from the debugging process. Asthis response indicates that the command wasunsuccessful, CICS assumes that the state of thedebugging process has not changed, except in the caseof a terminate command when CICS always assumesthat the debugger has died.

System action: The CICS region and the CICSapplication server continue. The state of the debuggingprocess is not changed.

User response: Refer to any further message thatindicates the reason for the bad response.

Destination:

CSMT

ERZ104037E Illegal command commandId issuedwhile debugging process in statedebugState

Explanation: CICS has tried to send a command to thedebugging process that is not consistent with thecurrent state of the debugging process. It is possiblethat the debugging process is already in the staterequested by CICS, in which case the command ismerely a duplicate, or it is possible that the command

is illegal for the particular state of the debuggingprocess.

System action: The CICS region and the CICSapplication server continue. The state of the debuggingprocess is not changed.

User response: Providing that CICS and thedebugging process can continue, it is possible that nofurther action is necessary. If there is a problem, refer toany associated messages in the CICS symptom recordsand console.msg files for further guidance on resolvingthe problem.

Destination:

CSMT

ERZ104038I Successfully configured debugging offfor terminal ’termId’

Explanation: The debugging configuration for thenamed terminal was successful. CDCN was able toterminate the debugging process.

System action: CDCN terminates if the requestedconfiguration is entirely successful, otherwise itcontinues. The next transaction to be run on the namedterminal is not debugged.


Destination:

CDCN user terminal

ERZ104039I Successfully configured debugging offfor system ’termId’

Explanation: The debugging configuration for thenamed system was successful. CDCN was able toterminate the debugging process.

System action: CDCN terminates if the requestedconfiguration is successful for all specified resources,otherwise it continues. The next transaction to be runthat originated from the named system is notdebugged.


Destination:

CDCN user terminal

ERZ104040I Successfully configured debugging offfor transaction ’transId’

Explanation: The debugging configuration for thenamed transaction was successful. CDCN was able toterminate the debugging process.

System action: CDCN terminates if the requestedconfiguration is successful for all specified resources,otherwise it continues. The next invocation of thetransaction is not debugged.

ERZ104035E • ERZ104040I



Destination:

CDCN user terminal

ERZ104041I Successfully configured debugging offfor program ’programName’

Explanation: The debugging configuration for thenamed program was successful. CDCN was able toterminate the debugging process.

System action: CDCN terminates if the requestedconfiguration is successful for all specified resources,otherwise it continues. The next invocation of theprogram is not debugged.


Destination:

CDCN user terminal

ERZ104042W Debugging is not configured on againstterminal ’termId’

Explanation: Debugging is not configured on for thenamed terminal, or was already configured off for thenamed terminal. This request to configure debuggingoff for the terminal is therefore rejected.

System action: This is merely a warning so CDCNcontinues.

User response: This is merely a warning, so it ispossible that no further action is necessary. If thewrong terminal identifier was input, specify a valid,existing terminal identifier for which debugging wasconfigured on before retrying the operation.

Destination:

CDCN user terminal

ERZ104043W Debugging is not configured on againstsystem ’sysId’

Explanation: Debugging is not configured on for thenamed system, or was already configured off for thenamed system. This request to configure debugging offfor the system is therefore rejected.


User response: This is merely a warning, so it ispossible that no further action is necessary. If thewrong system identifier was input, specify a valid,existing system identifier for which debugging isconfigured on before retrying the operation.

Destination:

CDCN user terminal

ERZ104044W Debugging is not configured on againsttransaction ’transId’

Explanation: Debugging is not configured on for thenamed transaction, or was already configured off forthe named transaction. This request to configuredebugging off for the transaction is therefore rejected.


User response: This is merely a warning, so it ispossible that no further action is necessary. If thewrong transaction identifier was input, specify a valid,existing transaction identifier for which debugging isconfigured on before retrying the operation.

Destination:

CDCN user terminal

ERZ104045W Debugging is not configured on againstprogram ’programName’

Explanation: Debugging is not configured on for thenamed program, or was already configured off for thenamed program. This request to configure debuggingoff for the program is therefore rejected.


User response: This is merely a warning, so it ispossible that no further action is necessary. If thewrong program identifier was input, specify a valid,existing program identifier for which debugging isconfigured on before retrying the operation.

Destination:

CDCN user terminal

ERZ104046E A debugging session is shown as activeagainst terminal ’termId’

Explanation: Debugging is not configured for thenamed terminal, and a debugging session is alreadyactive, or is starting up. This request to configuredebugging for the terminal is therefore rejected.Debugging can only be configured on or off, usingCDCN, when the debugging process is no longerattached to the application server.

System action: The state of the debugging session isnot changed.

User response: In order to configure debugging usingCDCN, you must wait until the debugging process hasdetached from the application server when thetransaction being debugged ends.

Destination:

CDCN user terminal

ERZ104041I • ERZ104046E


ERZ104047E A debugging session is shown as activeagainst system ’sysId’

Explanation: Debugging is already configured for thenamed system, and a debugging session is alreadyactive, or is starting up. This request to configuredebugging for the system is therefore rejected.Debugging can only be configured on or off, usingCDCN, when the debugging process is no longerattached to the application server.



Destination:

CDCN user terminal

ERZ104048E A debugging session is shown as activeagainst transaction ’transId’

Explanation: Debugging is already configured for thenamed transaction, and a debugging session is alreadyactive, or is starting up. This request to configuredebugging for the transaction is therefore rejected.Debugging can only be configured on or off, usingCDCN, when the debugging process is no longerattached to the application server.



Destination:

CDCN user terminal

ERZ104049E A debugging session is shown as activeagainst program ’programName’

Explanation: Debugging is already configured for thenamed program, and a debugging session is alreadyactive, or is starting up. This request to configuredebugging for the program is therefore rejected.Debugging can only be configured on or off, usingCDCN, when the debugging process is no longerattached to the application server.



Destination:

CDCN user terminal

ERZ104050W Attempt to configure debugging off forterminal ’termId’ was unsuccessful

Explanation: CICS has tried to configure debuggingoff for the named terminal, but termination of thedebug process was not successful. One possibility isthat the debug process encountered a problem and soreturned a bad response code to CICS. Anotherpossibility is that because CICS only waits a specifictime interval for the debug process to terminate, it ispossible that the debug process did not respond withinthe allowed time period.

System action: The CICS region and the CICSapplication server continue. The debug process waspossibly not terminated. However, CICS assumes that ithas died and so does not issue any further commandsto it.

User response: Investigate the reason that thetermination of the debug process did not succeed.Examine CICS message ERZ104070E, as this indicatesthe process identifier of the debug process. If thisprocess identifier still appears in the list of activeprocesses, kill it manually. The two named pipes usedby CICS to communicate with the process need to beremoved manually if they still exist. The names of thepipes are of the form /tmp/cicsc.<PID> and/tmp/cicsr.<PID> where <PID> is the process identifierof the debug process.

Destination:

CDCN user terminal

ERZ104051W Attempt to configure debugging off forsystem ’sysId’ was unsuccessful

Explanation: CICS has tried to configure debuggingoff for the named system, but termination of the debugprocess was not successful. One possibility is that thedebug process encountered a problem and so returneda bad response code to CICS. Another possibility is thatbecause CICS only waits a specific time interval for thedebug process to terminate, it is possible that the debugprocess did not respond within the allowed timeperiod.


User response: Investigate the reason that thetermination of the debug process did not succeed.Examine CICS message ERZ104070E, as this indicatesthe process identifier of the debug process. If thisprocess identifier still appears in the list of activeprocesses, kill it manually. The two named pipes usedby CICS to communicate with the process need to beremoved manually if they still exist. The names of the

ERZ104047E • ERZ104051W


pipes are of the form /tmp/cicsc.<PID> and/tmp/cicsr.<PID> where <PID> is the process identifierof the debug process.

Destination:

CDCN user terminal

ERZ104052W Attempt to configure debugging off fortransaction ’transId’ was unsuccessful

Explanation: CICS has tried to configure debuggingoff for the named transaction, but termination of thedebug process was not successful. One possibility isthat the debug process encountered a problem and soreturned a bad response code to CICS. Anotherpossibility is that because CICS only waits a specifictime interval for the debug process to terminate, it ispossible that the debug process did not respond withinthe allowed time period.


User response: Investigate the reason that thetermination of the debug process did not succeed.Examine CICS message ERZ104070E, as this indicatesthe process identifier of the debug process. If thisprocess identifier still appears in the list of activeprocesses, kill it manually. The two named pipes usedby CICS to communicate with the process need to beremoved manually if they still exist. The names of thepipes are of the form /tmp/cicsc.<PID> and/tmp/cicsr.<PID> where <PID> is the process identifierof the debug process.

Destination:

CDCN user terminal

ERZ104053W Attempt to configure debugging off forprogram ’programName’ was unsuccessful

Explanation: CICS has tried to configure debuggingoff for the named program, but termination of thedebug process was not successful. One possibility isthat the debug process encountered a problem and soreturned a bad response code to CICS. Anotherpossibility is that because CICS only waits a specifictime interval for the debug process to terminate, it ispossible that the debug process did not respond withinthe allowed time period.


User response: Investigate the reason that thetermination of the debug process did not succeed.Examine CICS message ERZ104070E, as this indicates

the process identifier of the debug process. If thisprocess identifier still appears in the list of activeprocesses, kill it manually. The two named pipes usedby CICS to communicate with the process need to beremoved manually if they still exist. The names of thepipes are of the form /tmp/cicsc.<PID> and/tmp/cicsr.<PID> where <PID> is the process identifierof the debug process.

Destination:

CDCN user terminal

ERZ104054W Debugging is not allowed. Ready fornext transaction.

Explanation: The value of the AllowDebuggingattribute in the Region Definitions (RD) is set to no, sosymbolic debugging cannot be used in this region.CDCN exits because it cannot configure debugging forthe region.



Destination:

CDCN user terminal

ERZ104055I Successfully configured debugging onfor transaction ’transId’

Explanation: The debugging configuration for thenamed transaction was successful. CDCN was able toinitialize the debugging process.

System action: CDCN terminates if the requestedconfiguration is successful for all specified resources,otherwise it continues. The next invocation of thetransaction is debugged, providing that all the relevantsecurity checks are satisfied.


Destination:

CDCN user terminal

ERZ104056I Successfully configured debugging onfor program ’programName’

Explanation: The debugging configuration for thenamed program was successful. CDCN was able toinitialize the debugging process.

System action: CDCN terminates if the requestedconfiguration is successful for all specified resources,otherwise it continues. The next invocation of theprogram is debugged, providing that all the relevantsecurity checks are satisfied.


Destination:

ERZ104052W • ERZ104056I


CDCN user terminal

ERZ104057E Attempt to configure debugging on forsystem ’sysId’ was unsuccessful

Explanation: CICS has tried to configure debuggingon for the named system, but startup of the debuggingprocess was not successful. One possibility is that the’exec’ of the debugging process did not succeed.Another is that the debugging process encountered aproblem and so returned a bad response code to CICS.A third possibility is that because CICS only waits aspecific time interval for the debugging process to start,it is possible that the debugging process did not startwithin the allowed time period.



Destination:

CDCN user terminal

ERZ104058E Attempt to configure debugging on fortransaction ’transId’ was unsuccessful

Explanation: CICS has tried to configure debuggingon for the named transaction, but startup of thedebugging process was not successful. One possibilityis that the ’exec’ of the debugging process did notsucceed. Another is that the debugging processencountered a problem and so returned a bad responsecode to CICS. A third possibility is that because CICSonly waits a specific time interval for the debuggingprocess to start, it is possible that the debuggingprocess did not start within the allowed time period.



Destination:

CDCN user terminal

ERZ104059E Attempt to configure debugging on forprogram ’programName’ was unsuccessful

Explanation: CICS has tried to configure debuggingon for the named transaction, but startup of thedebugging process was not successful. One possibilityis that the ’exec’ of the debugging process did notsucceed. Another is that the debugging processencountered a problem and so returned a bad responsecode to CICS. A third possibility is that because CICSonly waits a specific time interval for the debuggingprocess to start, it is possible that the debuggingprocess did not start within the allowed time period.



Destination:

CDCN user terminal

ERZ104060E Security violation: User ’userId’ tried todebug transaction ’transId’ but wasdenied access

Explanation: The named user attempted to debug thenamed transaction, but a Transaction Security Level(TSL) or Resource Security Level (RSL) check failed.CICS performs TSL validation to verify that the debuguser (the user who configured debugging on usingCDCN), has sufficient authorization to debug thetransaction and, if so, subsequent RSL validation isperformed for both the user who is running thetransaction and the debug user. One of these securitychecks failed.

System action: The user transaction continues, but isnot debugged.

User response: If the debug user is allowed to debugthe transaction, check that both the CDCN transactionand the transaction to be debugged have the samevalues for both the TSLCheck and RSLCheckattributes in the Transaction Definitions (TD). Alsocheck that both transactions have TSLKey and RSLKeyattribute values that are defined in the correspondingTSLKeyList and RSLKeyList for the debug user in theUser Definitions (UD).

ERZ104057E • ERZ104060E


Destination:

CSMT

ERZ104061I Attempting to configure debugging onfor terminal ’termId’. Please wait

Explanation: The debugging configuration for thenamed terminal is in progress. CDCN is attempting toinitialize the debugging process to be associated withthe named terminal. As this can take some time, theabove message is used to inform the user what ishappening.



Destination:

CDCN user terminal

ERZ104062I Attempting to configure debugging onfor system ’sysId’. Please wait

Explanation: The debugging configuration for thenamed system is in progress. CDCN is attempting toinitialize the debugging process to be associated withthe named system. As this can take some time, theabove message is used to inform the user what ishappening.



Destination:

CDCN user terminal

ERZ104063I Attempting to configure debugging onfor transaction ’transId’. Please wait

Explanation: The debugging configuration for thenamed transaction is in progress. CDCN is attemptingto initialize the debugging process to be associated withthe named transaction. As this can take some time, theabove message is used to inform the user what ishappening.



Destination:

CDCN user terminal

ERZ104064I Attempting to configure debugging onfor program ’programName’. Please wait

Explanation: The debugging configuration for thenamed program is in progress. CDCN is attempting toinitialize the debugging process to be associated withthe named program. As this can take some time, theabove message is used to inform the user what ishappening.



Destination:

CDCN user terminal

ERZ104065I Attempting to configure debugging offfor terminal ’termId’. Please wait

Explanation: The debugging configuration for thenamed terminal is in progress. CDCN is attempting toterminate the debugging process associated with thenamed terminal. As this can take some time, the abovemessage is used to inform the user what is happening.



Destination:

CDCN user terminal

ERZ104066I Attempting to configure debugging offfor system ’sysId’. Please wait

Explanation: The debugging configuration for thenamed system is in progress. CDCN is attempting toterminate the debugging process associated with thenamed system. As this can take some time, the abovemessage is used to inform the user what is happening.



Destination:

CDCN user terminal

ERZ104067I Attempting to configure debugging offfor transaction ’transId’. Please wait

Explanation: The debugging configuration for thenamed transaction is in progress. CDCN is attemptingto terminate the debugging process associated with thenamed transaction. As this can take some time, theabove message is used to inform the user what ishappening.



Destination:

CDCN user terminal

ERZ104068I Attempting to configure debugging offfor program ’programName’. Please wait

Explanation: The debugging configuration for thenamed program is in progress. CDCN is attempting toterminate the debugging process associated with thenamed program. As this can take some time, the abovemessage is used to inform the user what is happening.

ERZ104061I • ERZ104068I




Destination:

CDCN user terminal

ERZ104069E CDCN could not display a message onterminal ’termId’

Explanation: An attempt to display a CDCN messageon the user terminal was unsuccessful. This is possiblydue to your cicsterm session being unavailable to CICS.Further information is possibly available in one of theCICS message files.


User response: Check that the cicsterm session inwhich CDCN is running is still active. Check that thescreen is properly connected and configured. Refer toany associated messages in the CICS symptom recordsand console.msg files for further guidance on resolvingthe problem.

Destination:

CSMT

ERZ104070E Attempt to terminate debug processprocessId was unsuccessful

Explanation: CICS has tried to terminate the debugprocess identified by the stated process number, buttermination of the debug process was not successful.One possibility is that the debug process encountered aproblem and so returned a bad response code to CICS.Another possibility is that because CICS only waits aspecific time interval for the debug process toterminate, it is possible that the debug process did notrespond within the allowed time period. CICS attemptsto terminate a debug process that is not activelydebugging (not attached to an application server),either as a result of a request to configure debuggingoff, or as a result of a new request to configuredebugging on. This allows the configuration to bealtered easily, providing debugging is not in progress.

System action: The CICS region and the CICSapplication server continue. The debug process waspossibly not terminated. However, CICS assumes that ithas died and so does not issue any further commandsto it. If the process was terminated in order toconfigure debugging on using a new configuration, theCDCN transaction continues with the configurationattempt.

User response: Investigate the reason that thetermination of the debug process did not succeed. If theprocess identifier of the debug process still appears inthe list of active processes, kill it manually. The twonamed pipes used by CICS to communicate with theprocess need to be removed manually if they still exist.The names of the pipes are of the form

/tmp/cicsc.<PID> and /tmp/cicsr.<PID> where <PID>is the process identifier of the debug process.

Destination:

CDCN user terminal

ERZ104071I Attempt to terminate debug processprocessId was successful

Explanation: CICS has tried to terminate the debugprocess identified by the stated process number, andtermination of the debug process was successful. CICSattempts to terminate a debug process that is notactively debugging (not attached to an applicationserver), either as a result of a request to configuredebugging off, or as a result of a new request toconfigure debugging on. This allows the configurationto be altered easily, providing debugging is not inprogress.

System action: The CICS region and the CICSapplication server continue. If the process wasterminated in order to configure debugging on using anew configuration, the CDCN transaction continueswith the configuration attempt.


Destination:

CDCN user terminal

ERZ104072I The display to be used for thedebugging information is ’displayName’

Explanation: This message is used to confirm thename of the output display for the debugginginformation to be displayed on.

System action: CDCN terminates if the requestedconfiguration is successful for all specified resources,otherwise it continues. The next transaction to be runon the named terminal is debugged, providing that allthe relevant security checks are satisfied.

User response: This message is for information only.However, if the display name indicated in the messageis not the one required, run CDCN again to configuredebugging using the correct display name.

Destination:

CDCN user terminal

ERZ104073I Attempting to terminate debug processprocessId. Please wait

Explanation: Debugging configuration is in progress.A debug process is already associated with a resource,but debugging is not in progress. CDCN is attemptingto terminate the debug process identified in themessage so that a new debug process can be started forthe resource. As this can take some time, the abovemessage is used to inform the user what is happening.

ERZ104069E • ERZ104073I




Destination:

CDCN user terminal

ERZ104074E CDCN was unable to save message’messageId’ in the message array

Explanation: The CDCN transaction attempted to savethe message identified by this message in order to beable to display it later on the CDCN message screen.Unfortunately, the array used by CDCN to storemessages is already full.

System action: CDCN continues. The messageidentified above is not displayed on the CDCNmessage screen.

User response: CDCN is always supposed to haveenough room to store all the messages that it is todisplay, so this message indicates an internal problemwith the CDCN transaction. Contact your supportorganization.

Destination:

CSMT

ERZ104075E Response on pipe ’fileName’ indicatesprocess ’debugProcess’ could not opendisplay ’displayId’

Explanation: The named debug process attempted toopen the display with the identifier supplied by CDCN,but the attempt was unsuccessful. The debug processhas returned an error response to CDCN on the namedresponse pipe.

System action: Debugging is not configured asrequested. CDCN continues, and waits for input of avalid display identifier. If the debug process treats thiserror as fatal, it terminates.

User response: Specify a valid display identifier in theDISPLAY field of the BMS map before retrying theoperation. You must specify a value for the DISPLAYoption when you configure debugging on.

Destination:

CDCN user terminal

ERZ104076E Response on pipe ’fileName’ indicatesprocess ’debugProcess’ could not forkchild process

Explanation: The named debug process attempted tocreate a child process using a fork() subroutine call, butthe attempt was unsuccessful. The debug process hasreturned an error response to CDCN on the namedresponse pipe.

System action: Debugging is not configured as

requested. CDCN continues. If the debug process treatsthis error as fatal, it terminates.

User response: Ensure that the named debug processis correctly installed. If the name of the child process isknown, ensure that this process is also correctlyinstalled. For example, xldb is the child process to thepipemon process. Investigate the state of the system tosee if any other factors possibly prevented the debugprocess from creating a new, child process. Forexample, the system possible does not have enoughresources to create another process.

Destination:

CDCN user terminal

ERZ104077E Response on pipe ’fileName’ indicatesdebugging process has alreadyterminated

Explanation: CICS has issued a command to thedebug process asking it to arrange to attach its childprocess (the actual debugging process) to a particularapplication server in order to debug some user code.However, the debugging (child) process has alreadyterminated, so the debug process has returned an errorresponse to CICS on the named response pipe.

System action: Debugging is not started as required.The CICS application server continues, but the usercode is not debugged.

User response: If the debugging process was notintentionally terminated, investigate the reason that thedebugging process has terminated. If the name of theprocess is known, for example xldb, ensure that theprocess is correctly installed. Investigate the state of thesystem to see if any other factors possibly caused thedebugging process to terminate. For example, thedebugging process possibly terminated because thesystem is short of resources.

Destination:

CSMT, or CDCN user terminal if running CDCN

ERZ104078E Response on pipe ’fileName’ indicatesprocess ’debugProcess’ could not exec newprogram

Explanation: The named debug process attempted toexecute a new program using an execv() subroutinecall, but the attempt was unsuccessful. The debugprocess has returned an error response to CDCN on thenamed response pipe.

System action: Debugging is not configured asrequested. CDCN continues. If the debug process treatsthis error as fatal, it terminates.

User response: Ensure that the named debug processis correctly installed. If the name of the new program isknown, ensure that this process is also correctlyinstalled. For example, xldb is the program started by

ERZ104074E • ERZ104078E


the pipemon process. Investigate the state of the systemto see if any other factors possibly prevented the debugprocess from starting a new program. For example, thesystem possibly does not have enough resources tostart another program.

Destination:

CDCN user terminal

ERZ104079E Response on pipe ’fileName’ indicatesprocess ’debugProcess’ could not closepipe

Explanation: The named debug process attempted toclose one, or both, of the command and response pipesused to communicate with CICS. At least one closeattempt was unsuccessful, so the debug process hasreturned an error response to CDCN on the namedresponse pipe.


User response: Ensure that the named pipe(s) existsand have the correct permissions for CICS (and thedebug process) to access the pipe(s). The two namedpipes used by CICS to communicate with the processneed to be removed manually if they still exist. Thenames of the pipes are of the form /tmp/cicsc.<PID>and /tmp/cicsr.<PID> where <PID> is the processidentifier of the debug process.

Destination:


ERZ104080E Response on pipe ’fileName’ indicatesprocess ’debugProcess’ could notrecognize command

Explanation: CICS has issued a command to thedebug process using the command pipe. However, thedebug process has not recognized the command, so thedebug process has returned an error response to CICSon the named response pipe.

System action: CDCN continues, but the state of thedebug process is not changed.

User response: CDCN is always supposed to issue avalid command, so this message indicates either aninternal problem with the CDCN transaction, or aninternal problem with the debug process. Contact yoursupport organization.

Destination:


ERZ104081E Response on pipe ’fileName’ indicatesprocess ’debugProcess’ could not openenvironment file ’envFileName’

Explanation: The named debug process attempted toopen the named environment file specified by CDCN,but the attempt was unsuccessful. The debug processhas returned an error response to CDCN on the namedresponse pipe.


User response: Specify a valid environment file nameusing the CICSDEBUGENV environment variable. Thisenvironment variable must be exported by each CICSuser that wishes to specify debugging control variableson an individual basis before running cicsterm. If anenvironment file name is specified, the file must exist,and the file permissions for the file must allow readaccess by the debug process.

Destination:

CDCN user terminal

ERZ104082E Return code value of returnCodeValue onpipe ’fileName’ not recognized

Explanation: CICS has issued a command to thedebug process using the command pipe, but the debugprocess has encountered an error and returned an errorresponse to CICS on the named response pipe.However, the return code indicated is not one of therange of values recognized by CICS.

System action: The CICS application server continues,but the state of the debug process is not known.

User response: The debug process is always supposedto issue a valid return code, so this message indicateseither an internal problem with the debug process oran internal problem with the CDCN transaction.Contact your support organization.

Destination:


ERZ104083E The transaction ’transId’ cannot bedebugged as it is a CICS-reserved name

Explanation: The user has requested debug of atransaction that begins with the character ’C’. Suchnames are reserved for use by internal CICStransactions, which cannot be debugged.


User response: Enter a valid user transactionidentifier. User transactions must not begin with thecharacter ’C’, as this is reserved for internal CICS use.

Destination:

ERZ104079E • ERZ104083E


CSMT

ERZ104084E The program ’programName’ cannot bedebugged as it is a CICS-reserved name

Explanation: The user has requested debug of aprogram that begins with the characters ’DFH’. Suchnames are reserved for use by internal CICS programs,which cannot be debugged.


User response: Enter a valid user program name. Userprograms must not begin with the characters ’DFH’, asthese are reserved for internal CICS use.

Destination:

CSMT

ERZ104085E CICS was unable to start process’processPath’, internal error ’errorMessage’,operating system error ’errorNumber’

Explanation: CICS was unable to start a process toallow debugging of a user transaction.

System action: The CICS region and the CICSapplication server continue. A debugging process wasnot started, so transactions are not debugged.


Destination:

CDCN user terminal

ERZ104086E CICS was unable to get the process idfor process ’processPath’, internal error’errorMessage’

Explanation: CICS was unable to get the processidentifier of a newly-started debugging process.

System action: The CICS region and the CICSapplication server continue. A debugging process wasnot started, so transactions are not debugged.


Destination:

CDCN user terminal

ERZ104087E Security violation: Resource LevelChecking for requested resource’resourceName’ failed

Explanation: A resource level security check failed forthe named resource. This can happen if the RSLKey forthe named resource is ’private’ and the RSLCheck forthe CDCN transaction is not ’none’, or if the RSLKey ofthe named resource is not in the RSLKeyList of theUser Definition for the debug user.

System action: Debugging is not configured for thissession.

User response: Investigate the reason for the securitycheck failure, amend the definitions and retry.

Destination:

CDCN user terminal

ERZ104088W Unknown UserId, reset to last UserId

Explanation: The debugging configuration for theuserId was unsuccessful. The UserId does not exist.

System action: The last UserId selected in the debugtransaction that was known to exist is refreshed on theBMS screen.

User response: Create the UserId before trying toconfigure the debugger for it.

Destination:

User terminal

ERZ104089E The COBANIMSRV Id field is notspecified. Configuration cannotcontinue.

Explanation: must have a CobAnimSrv ID forconfiguration because it is the input for cross sessionanimation in ServerExpress COBOL.

System action: CADB continues to wait for the user toenter data.

User response: Reenter data for the COBANIMSRV IDfield on the CADB screen and press Enter.

Destination:

CADB user terminal

ERZ104090E Unsuccessful deallocation of internaldebug data.

Explanation: CICS could not release the regionmemory that is held for debugging purposes.


User response: Check whether the nextself-consistency check for the region is successful.If the

ERZ104084E • ERZ104090E


problem occurs again, save any dump file that isproduced and contact your support organization.

Destination:

CSMT

ERZ104091I CADB has ended normally. Ready fornext transaction.

Explanation: This message is displayed when CADBends.



Destination:

CADB user terminal

ERZ104092E COBANIMSRV Id:cobAnimSrvId is notvalid.

Explanation: A COBANIMSRV ID that is not validwas entered.

System action: CADB reports the error and waits forthe user to reenter data.

User response: Refer to the documentation for therules about COBANIMSRV ID. Reenter the debugconfiguration data.

Destination:

console

ERZ104093W Attempt to configure debugging off forKey ’Key’ was unsuccessful.

Explanation: CICS has tried to configure debuggingoff for the Key. The attempt was not successful.Reasons for this might be: The user has not configureddebugging for this key. The failure is therefore valid.The resources that are associated with this key couldnot be deleted.


User response: If this Key was configured earlier andis still failing, try to remove, one at a time, everyresource that is under this key. This action might helpyou to isolate the problem.

Destination:

CADB user terminal

ERZ104094I Successfully configured debugging offfor the Key’Key’.

Explanation: CICS removed the debug configurationfor the Key successfully.



Destination:

CADB user terminal

ERZ104095I The COBANIMSRV Id to be used fordebugging is ’COBANIMSRVId’.

Explanation: This is the COBANIMSRV ID for thisdebug configuration. This ID is used when thecicsanimsrv process is started.


User response: None

Destination:

CADB User Terminal

ERZ104096E The CADB data structure has asignature’currentSignatureexpectedSignature.’ that isnot valid. It should be ’%3$s’.

Explanation: The CICS self-consistency check detectedan error in the CADB internal data structures that arestored in the region memory.

System action: CICS region terminates abnormally.

User response: This is a CICS internal error. Save anyerror logs (such as dumps, console, symrecs ) andcontact your support organization.

Destination:

console

ERZ104099W CADB not supported. Ready for nexttransaction.

Explanation: CADB transaction can be only used onnon-Windows platforms for configuring CICS forworking with Animator.



Destination:

CADB user terminal

ERZ104100E Invalid Host or Port DisplayId.

Explanation: Host name or port specified is not valid.

User response: Examine the value of DISPLAYparameter.

Destination:

ERZ104091I • ERZ104100E


ERZ105001E Unable to create lock file ’fileName’

Explanation: The lock file ’fileName’ cannot be created.Accompanying messages can identify the exact cause ofthe problem.

System action: Command abnormally terminates.

User response: Check that you have permission tocreate files in the directories named in ’fileName’.Ensure also that the file system is not full. Seeaccompanying messages for further information.Correct the problem and retry the command.

Destination:

stderr

ERZ105002W Waiting for lock

Explanation: A server command requires a server lockto be taken - however, the lock is already being held byanother user.

System action: The command loops until the lock canbe taken.

User response: None

Destination:

stderr

ERZ105003E Unable to remove lock file ’fileName’

Explanation: The lock file ’fileName’, used for lockinga server, cannot be removed during a lock or unlockprocedure. Accompanying messages identify the exactcause of the problem.


User response: Check that you have permission toremove files in the directories named in ’fileName’.Ensure also that the file system is not full. Seeaccompanying messages for further information.Correct the problem and retry the command.

Destination:

stderr

ERZ105004E Unable to access server definitions aslocked with file ’fileName’

Explanation: A CICS administration command wasentered that must secure a server definitions lock.However, the lock for this server was already taken byanother user. This can mean that the server is currentlyrunning, or some other command or process isadministering the server definitions, or the lock wastaken by a command or process that subsequentlyterminated abnormally, leaving the lock (this happensif, for example, the machine is shut down while the

server is running or while administration commandsare in progress).


User response: If there are other CICS administrationcommands in progress then wait for them to finish andretry the command. Otherwise remove the lock filespecified in the message text and retry the command.

Destination:

stderr


Explanation: It was not possible to create serverdirectory ’directoryName’.


User response: Check the existence and permissionson all the directories named in the path of the directorybeing created. See accompanying messages for furtherinformation. Correct the problem, and retry thecommand.

Destination:

stderr

ERZ105006I Directory ’directoryName’ created

Explanation: The directory ’directoryName’ wascreated.


User response: None

Destination:

stderr

ERZ105007E Unable to change access permissions ondirectory ’directoryName’

Explanation: A CICS command is unable to changethe access permissions on directory ’directoryName’.Either the directory does not exist or you do not havethe required privileges to change its ownership.


User response: Check the existence and permissionson all the directories named in the path of the directorybeing created. You must have read and executepermission on all parent directories, and writepermission to the directory itself. See accompanyingmessages for further information. Correct the problem,and retry the command.

Destination:

stderr

ERZ105001E • ERZ105007E


ERZ105008W Unable to change details of file’fileName’, errno ’errno’

Explanation: An attempt at changing the owner of’fileName’ to user ’errno’ failed.

System action: The command can possibly terminateabnormally.

User response: Examine the value of errno todetermine what the exact problem is.

Destination:

stderr

ERZ105009E Schema File already exists

Explanation: The cicsscdcreate command attempted tocreate the empty schema file with the specified name,but a file with that name already exists.

System action: The cicsscdcreate command terminatesabnormally.

User response: Reexecute the command specifying anew schema file name or remove the existing file if it isno longer required.

Destination:

stderr

ERZ105010I Usage: cicsscdcreate { -? | -fschemaFileName}




Destination:

stderr

ERZ105021I Usage: cicssfslock {-? | [ -l | -u | -t ] }serverName

Explanation: This is the usage message for thecicssfslock command.



Destination:

stderr

ERZ105022E cicscp failed to allocate storage

Explanation: This message is output when cicscp failsto allocate general storage (not storage mentioned inone of the other ″failed to allocate″ messages).


User response: Retry the command. If you are in a

long interactive session with cicscp try ending thesession and submitting the command on the commandline.

Destination:

stderr

ERZ105023E Internal cicscp error detected:’errorNumber’

Explanation: This message is displayed if cicscpdetects an internal problem with the operation of cicscpitself.

System action: None

User response: Retry the command. If the problempersists, contact your support organization.

Destination:

stderr

ERZ105025E cicscp failed to execute the program’programName’, error number is’errorNumber’

Explanation: This message is output if cicscp detectsan error when executing the program.


User response: On UNIX, consult the operatingsystem documentation for the execvp() function andcheck the conditions for the errorNumber value. OnWindows NT, Check the errorNumber value in theappropriate Microsoft Win32 manual.

Destination:

stderr

ERZ105026E The ’function’ of ’stream’ failed with errornumber ’errorNumber’

Explanation: This message is output if cicscp detectsan error when manipulating the standard I/O streamsduring the creation of a sub-process.


User response: Retry the command. If it still fails thena system resource limit was possibly reached. Consultthe operating system documentation for theappropriate function and check the conditions for theerrorNumber value.

Destination:

stderr

ERZ105008W • ERZ105026E


ERZ105027E stanza override must be of the formattributeName=attributeValue

Explanation: This message is output if cicscp fails toparse a string of stanza file attribute overrides.


User response: Correct the syntax and retry thecommand.

Destination:

stderr

ERZ105031E Subsystem definition ’subsystemName’cannot be found

Explanation: A subsystem definition for’subsystemName’ was not found. The most likely reasonfor this is that the server name was entered incorrectly,or the subsystem definition was prematurely deleted.Accompanying messages identify the exact cause of theproblem.


User response: Use accompanying to determine thecause of the problem. Correct the problem and retry thecommand.

Destination:

stderr

ERZ105032W Subsystem definition for ShortName’shortName’ is already used by server’serverName’

Explanation: The ShortName attribute of a servermust be unique because it is used to generate thesubsystem definition name. ’shortName’ is already usedby server ’serverName’.


User response: Specify a unique ShortName valueand retry the command.

Destination:

stderr




User response: If the system was heavily loaded, waituntil the load decreases and rerun the command. If theproblem persists check for error messages in the systemerror log and console.

Destination:

stderr

ERZ105035E Unexpected option ’option’ specified oncommand line.

Explanation: The option identified in the message wasincorrectly specified on the command line to theexecuting program. The program does not accept thisoption as a parameter.


User response: Consult the usage message producedby the program and respecify the options correctly.

Destination:

stderr

ERZ105036E Unexpected argument ’arguments’specified on command line.

Explanation: The argument identified in the messagewas incorrectly specified on the command line to theexecuting program. The program does not accept thisargument as a parameter.


User response: Consult the usage message producedby the program and respecify the arguments correctly.

Destination:

stderr

ERZ105037E Option -option has already beenspecified.

Explanation: The option identified in the message wasspecified twice in the command line to the executingprogram.


User response: Remove the extra options specifiedand attempt to reexecute the command.

Destination:

stderr

ERZ105038E Option -option must have a matchingargument.

Explanation: The option identified in the messagerequires a matching argument.


User response: Respecify the command specifying theargument required by the command. If an argumentwas specified but begins with a ’-’ it was possiblyinterpreted as an option; in this case, use a double ’-’ toensure it is treated as an argument.

Destination:

ERZ105027E • ERZ105038E


stderr

ERZ105039E The option -option must be specified.

Explanation: The option identified in the messagemust be specified.


User response: Respecify the command specifying themissing option with any appropriate arguments.

Destination:

stderr

ERZ105040E At least one of the following optionsmust be specified ’optionList’.

Explanation: At least one of the options from theabove list must be specified.


User response: Respecify the command specifying therequired option with any appropriate arguments.

Destination:

stderr

ERZ105041E At least optionNumb of the followingoptions must be specified ’optionList’

Explanation: At least optionNumb of the options fromthe above list must be specified.


User response: Respecify the command specifying therequired options with any appropriate arguments.

Destination:

stderr

ERZ105042E Only one of the following options maybe specified ’optionList’

Explanation: Only one of the options from the abovelist can be specified.


User response: Respecify the command specifyingonly one on the options from the above list.

Destination:

stderr

ERZ105043E A maximum of optionNumb options maybe specified from ’optionList’

Explanation: A maximum of optionNumb options canbe specified from the above list.


User response: Respecify the command specifyingonly the required options with any appropriatearguments.

Destination:

stderr

ERZ105050I Usage: cicscpio { -? | [-v] [-r | -w] [-ffileName]




Destination:

stderr

ERZ105051E Error opening or closing file or directory’fileName’, error number ’errno’

Explanation: The command you entered tried to openor close file or directory ’fileName’ but was unable to doso.


User response: Check that the file exists and hasreasonable permissions on it. If the file does not exist itis possible that your command was trying to create it,in which case check that the directory permissions arecorrect. Check that the file is in a valid format and isnot corrupted. Use the error number for moreinformation.

Destination:

stderr

ERZ105052E Error writing to file ’fileName’, errornumber ’errno’

Explanation: The command you entered tried to writeto file ’fileName’ but was unable to do so.


User response: Check that the specified file has thecorrect permissions (if it exists) and that there issufficient space in the file system to write to it. Use theerror number for more information.

Destination:

stderr

ERZ105053E Error - bad archive file

Explanation: The command you entered was unableto read the archive file you specified.


User response: Ensure you have given a valid archive

ERZ105039E • ERZ105053E


file name. Check also that the archive file you specifiedis not corrupted.

Destination:

stderr





Destination:

stderr

ERZ105062W Unable to access details on user ’userId’



User response: None

Destination:

stderr

ERZ105063E Unable to access details on user ’userId’



User response: Ensure that user ’userId’ exists andretry the command.

Destination:

stderr

ERZ105064W Directory ’directoryName’ is notaccessible by user ’userId’ or does notexist

Explanation: Either ’directoryName’ is not readable,writable and executable by ’userId’ or does not exist.


User response: None

Destination:

stderr

ERZ105065E Directory ’directoryName’ is notaccessible by user ’userId’ or does notexist

Explanation: Either ’directoryName’ is not readable,writable and executable by ’userId’ or it does not exist.


User response: Ensure ’directoryName’ exists and isreadable, writable and executable by ’userId’.

Destination:

stderr





Destination:

stderr

ERZ105067E Unable to access details on user orgroup ’userId’

Explanation: CICS was unable to access details onuser or group userId. This was probably because theuser or group does not exist. Previous messagesidentify the exact problem.


User response: Ensure that user or group userId existsand then rerun the command. If it does not exist thenensure that CICS is installed correctly.

Destination:

stderr

ERZ105068E Unable to get the current directory,errno ’errorNumber.’

Explanation: The command you entered tried to findout which directory you are in but was unable to do so.


User response: Check that you have installed CICScorrectly. Check the value of errno for moreinformation on the problem.

Destination:

stderr

ERZ105061E • ERZ105068E


ERZ105069E Unable to get information on file ordirectory ’fileName’, errno ’errorNumber.’

Explanation: The command you entered tried to getinformation on the specified file or directory but wasunable to do so.


User response: Check that the file or directorymentioned in the message exists and that you haveaccess to it. Check that it is not corrupted. Refer toerrno for more information.

Destination:

stderr

ERZ105070E Error reading file ’fileName’, errno’errorNumber.’

Explanation: The command you entered tried to readfile ’fileName’ but encountered an error.


User response: Check the file is not corrupted. It ispossible that the command received a spurious signal,in which case try the command again. Refer to errnofor more information.

Destination:

stderr

ERZ105071E Unable to alter permissions/owner offile ’fileName’, errno ’errorNumber.’

Explanation: The command you entered tried to alterthe permissions or the owner of ’fileName’ but wasunable to do so.


User response: Check that the file exists and that youhave sufficient priviledge to access it. Use the errornumber for more information.

Destination:

stderr

ERZ105090E Server ’serverName’ contacted but servernot fully operational

Explanation: The current command was able tocontact the server identified in the message, but iffailed to verify that the server is fully operational.

System action: The command cannot continue.

User response: Verify that the server is running andhas fully completed its initialisation. When initialisationis fully complete reissue the command.

Destination:

stderr

ERZ105093E Server ’serverName’ started, but has notbeen initialized

Explanation: The Server ’serverName’ was started butwas unable to be initialized.


User response: Verify that RPC is running, and useany previous messages to help identify the problem.The server must be shut down and restarted before itcan be used.

Destination:

stderr

ERZ105094E Unable to start server ’serverName’

Explanation: The Server ’serverName’ was unable to bestarted.


User response: Use accompanying messages todetermine the cause of problem. Correct the problemand retry the command.

Destination:

stderr

ERZ105095E Linked files detected - not supportedunder Windows NT

Explanation: You tried to import a file from anoperating system that supports links. When the file wascreated it was done so using the link option ofcicsexport which is not compatible in a Windows NTenvironment.


User response: Use a different import file.

Destination:

stderr

ERZ105096E Unable to create link from’sourceFileName’ to ’targetFileName’, errno’errno’

Explanation: You tried to import a file from anoperating system that supports links. When the file wascreated it was done so using the link option ofcicsexport. The command tried to create the link butwas unable to do so.


User response: Use the error number ’errno’ toinvestigate why the command failed. Correct the

ERZ105069E • ERZ105096E


problem and rerun the cicsimport command using the’-F’ option. You can use the ’-lo’ option to ignore thiserror.

Destination:

stderr

ERZ105097W Target ’targetFileName’ of symbolic link’sourceFileName’ does not exist

Explanation: You tried to import a file from anoperating system that supports links. When the file wascreated it was done so using the link option ofcicsexport. The command found that the target file doesnot exist.

System action: Since you specified the ’-lo’ option, thecommand continues.

User response: Ensure that the target exists beforerunning the region.

Destination:

stderr

ERZ105100E Both ’primaryRestartFile’ and’backupRestartFile’ are missing for server’serverName’

Explanation: The server restart files were unable to befound.


User response: On an auto start of a server at leastone of the restart files must be available. If neitherrestart file is available, you must cold start (initialize).

Destination:

stderr

ERZ105101W Restart file ’restartFileName’ is missingfor server ’serverName’

Explanation: The restart file ’restartFileName’ for server’serverName’ was unable to be found.

System action: Processing continues using the otherrestart file.

User response: None. The other restart file is rebuiltduring server startup.

Destination:

stderr

ERZ105102I Restart files located for server’serverName’

Explanation: The restart files for the server werelocated.


User response: None

Destination:

stderr

ERZ105104I Keytab file checked for server’serverName’

Explanation: The keytab file for the server waschecked.


User response: None

Destination:

stderr

ERZ105105W The archives directory ’directoryName’ forserver ’serverName’ does not exist

Explanation: The archives directory for the serverdoes not exist but is rebuilt.

System action: Processing continues and rebuilds thearchive directory.

User response: None. The archive directory is rebuilt.

Destination:

stderr

ERZ105106E The archives directory ’directoryName’ forserver ’serverName’ does not exist

Explanation: The archives directory for the serverdoes not exist.

System action: The command abnormally terminatesreturning the value 1

User response: Retry the command specifying the -Iflag (ignore errors) which causes the directory to berebuilt.

Destination:

stderr

ERZ105107I Archives directory located for server’serverName’

Explanation: The archives directory for the server waslocated.


User response: None

Destination:

stderr

ERZ105097W • ERZ105107I


ERZ105108E Unable to find data for region’regionName’




Destination:

stderr

ERZ105109E Unable to read the CICS internalinventory list

Explanation: The CICS internal inventory list is notreadable by the current user.


User response: Check that the CICS installation wassuccessful. If problem persists, contact your supportorganization.

Destination:

stderr

ERZ105110E The CICS internal inventory list hasinconsistent data

Explanation: The contents of CICS internal inventoryare invalid and cannot be used check region archives.



Destination:

stderr

ERZ105115W ’fileName’ does not exist in the archive


System action: Since you did not specify the ’-lm’option the command continues. Since you did notspecify the ’-lo’ option, the specified file is simplyignored.

User response: It is probable that the cicsexportcommand used to create the archive file used one ofthe linking options available to it. If this is as desired,retry the cicsimport command using the ’-lo’ option,which creates the desired link. If this is not the case,check that the CICS installation was successful and that

the region archive file you are using is not corrupt. Ifyou were running the cicsimport command, prior tomigrating your regions for a new level of CICS, thenensure that the cicsmigrate updates your region to addthe missing file. If the problem persists, contact yoursupport organization.

Destination:

stderr

ERZ105116E ’fileName’ does not exist in the archive -command terminating


System action: Since you specifed the ’-lm’ option, thecommand terminates.

User response: It is probable that the cicsexportcommand used to create the archive file used one ofthe linking options available to it. If this is as desired,retry the cicsimport command using the ’-lo’ option,which creates the desired link. If this is not the case,check that the CICS installation was successful and thatthe region archive file you are using is not corrupt. Ifyou were running the cicsimport command, prior tomigrating your regions for a new level of CICS, thenensure that the cicsmigrate updates your region to addthe missing file. If the problem persists, contact yoursupport organization.

Destination:

stderr

ERZ105117I ’fileName’ does not exist in the archive -creating link


System action: Since you specified the ’-lo’ command,the link is created and the command continues.

User response: It is probable that the cicsexportcommand used to create the archive file used one ofthe linking options available to it in which case youneed to do nothing. If this is not the case, check thatthe CICS installation was successful and that the regionarchive file you are using is not corrupt. If you wererunning the cicsimport command, prior to migratingyour regions for a new level of CICS, then ensure thatthe cicsmigrate updates your region to add the missingfile. If the problem persists, contact your supportorganization.

Destination:

stderr

ERZ105108E • ERZ105117I


ERZ106001E Insufficient storage to initialize theCICS Open Listener component

Explanation: During region initialization the OpenListener component was unable to obtain sufficientstorage from the Region Pool to initialize correctly.

System action: CICS abnormally terminates.

User response: Restart CICS with an increased RegionPool size by overriding the MaxRegionPool attribute(RD) on the command line. Do the same for thepermanent database (using cicsupdate).

Destination:

console.msg

ERZ106002E A DPL mirror transaction cannot replyto a syncpoint request received on aDTP conversation with system ’sysId’

Explanation: The current program was started as theresult of a Distributed Program Link (DPL) request thatdid not specify the SYNCONRETURN option. It hasstarted a Distributed Transaction Processing (DTP)conversation with another system ’sysId’. The programthat originated the DPL request is the only one that isallowed to issue syncpoint or backout commands.


User response: Correct the programs so that theoriginator of the DPL request is the only one that issuessyncpoints, or use the SYNCONRETURN option.

Destination:

CSMT

ERZ106003E The function shipping mirrortransaction ’transId’ cannot be startedfrom a terminal

Explanation: You have started the function shippingmirror transaction by entering the transaction code’transId’ at a terminal. The function shipping mirrortransaction can be started only by an Open Listenerrequest.


User response: Do not attempt to start the functionshipping mirror transaction from a terminal.

Destination:

CSMT

ERZ106004E A communications error has occurredwhile receiving data on an OpenListener conversation

Explanation: CICS detected a communications errorwhile attempting to receive request data from an OpenListener process.



Destination:

CSMT

ERZ106005E The Open Listener mirror program hasdetected an internal error during theprocessing of a request

Explanation: CICS detected an internal inconsistencyin when processing a request from an Open Listener.



Destination:

CSMT

ERZ106006E Unable to allocate commarea duringprocessing of an Open Listener request

Explanation: CICS is unable to allocate task privatestorage for a commarea when processing an OpenListener request.


User response: Retry the request when the system ismore lightly loaded or simplify the transaction so thatit uses less task private storage. Alternatively, increasethe size of the task private storage pool. This isconfigured in the Region Definition (RD) entry attributeMaxTaskPrivatePool.

Destination:

CSMT

ERZ106007E A communications error has occurredwhile sending data on an Open Listenerconversation

Explanation: CICS detected a communications errorwhile attempting to send respnse data to an OpenListener process.



Destination:

ERZ106001E • ERZ106007E


CSMT

ERZ106008E Storage corruption detected whenfreeing user commarea

Explanation: CICS detected that the commarea passedon an Open Listener request was corrupted on returnfrom the linked to program. The most likely cause ofthis type of error is a program writing beyond the endof the commarea storage.


User response: Check both the Open Listener programand the target CICS program to ensure that the size ofthe commarea being sent and received is consistent.

Destination:

CSMT

ERZ107001I Licenses available: serverLicenses,maximum usage (server/region):serverUsage/regionUsage

Explanation: This message contains a summary of thelicense activity for the CICS region that is now ending.’Licenses available’ refers to the number of licensesavailable for all CICS regions on this server. ’maximumusage’ refers to the High Water Mark (both at a regionlevel, and server wide) for the session. When the regionis not operating in Production mode, the values for’Licenses available’ and ’maximum usage (server)’areshown as -1, as they have no meaning in other modes.


User response: None required.

Destination:

console.msg

ERZ107002I Average usage for session: averageUsage,total usage for session: totalUsage

Explanation: The average usage for the CICS regionduring the session is shown, together with acumulative total of licenses requested during thesession.



Destination:

console.msg

ERZ107003I License requests for this region:regionRequests

Explanation: The number of license requests processedby the CICS License Manager for this region isdisplayed.



Destination:

console.msg

ERZ107004I License requests: addRequests Addrequests, releaseRequests Release requests

Explanation: The number of Add and Release licenserequests handled by the CICS License Manager for thisregion is displayed. An individual request can relate tomore than one license, and so the two numbers candiffer.



Destination:

console.msg

ERZ107005I Time spent above license threshold:overTime%% of session duration,overActivity%% of License Manageractivity

Explanation: The amount of time that this CICSregion required more licenses than were available isshown. The first figure displays the time as apercentage of the duration of the session, since it wasstarted. The second figure shows the amount of activityover the license threshold as a percentage of all LicenseManager activity for the session.


User response: If the license threshold is exceeded fora significant proportion of the session, then you requiremore licenses. You can update the number of licensesavailable to CICS via the Nodelock AdministrationTool. Refer to the documentation for furtherinformation, or contact your IBM Authorized Dealer orRepresentative.

Destination:

console.msg

ERZ106008E • ERZ107005I


ERZ107006I Total calls to License Use ManagementClient: lumTotalCalls; errors returned:lumErrorsReturned

Explanation: The CICS License Manager uses theLicense Use Management (LUM) Client (iFOR/LS) toprovide license use validation. This message recordsthe number of requests made to the LUM Client, andalso the number of errors returned. Errors returned bythe LUM Client are handled by the CICS LicenseManager and do not have any effect on the operationof CICS.


User response: If there are a large number of errorsreported, it is possible that the License UseManagement Client is not correctly installed orconfigured. Refer to the CICS documentation onLicensing, or contact your IBM Authorized Dealer orRepresentative.

Destination:

console.msg

ERZ107007I CICS License Manager has terminatednormally

Explanation: This message indicates that the CICSLicense Manager has completed its terminationprocessing normally.

System action: CICS shutdown continues.


Destination:

console.msg

ERZ107008I CICS License Manager initialization iscomplete, operation mode is initMode

Explanation:

This message indicates that the CICS License Managerhas completed its initialization processing. Licensemanagement is available for this session of CICS. Theoperation mode is one of the following:

0 Reserved.

1 Evaluation. This CICS system is licensed for alimited period only.

2 Production. This CICS system is fully licensed.

3 Registered. This CICS system is licensed forregistered usage.

4, 5, 6, 7Reserved.

System action: The region continues to initialize.

User response: If the licensing mode is Evaluation,

but you have a Production certificate, then enroll thiscertificate via the Nodelock Administration Tool assoon as possible. This can be done while CICS is active.If you have enrolled a Production certificate, but CICSstarts up in Evaluation mode, then verify that thecertificate is enrolled correctly. Refer to yourdocumentation for a description of how to enroll acertificate. If this copy of CICS is licensed as anEvaluation copy, then it continues to execute for theduration of the Evaluation period only. The number ofdays remaining is shown in an earlier message. You canenroll a Production certificate at any point during thisEvaluation period.

Destination:

console.msg

ERZ107009E CICS License Manager initialization wasnot successful

Explanation: During initialization, the CICS LicenseManager was unable to initialize. This can be caused bythe product expiring after an Evaluation period, orCICS being unable to validate the licensing mode.

System action: This is a fatal error and causes theCICS region to shut down.

User response: If this is an Evaluation copy of CICS,please contact your IBM Authorized Dealer orRepresentative for a Production certificate. If this is notan Evaluation copy of CICS then a serious error hasoccurred. Contact your support organization withdetails of the preceding messages.

Destination:

console.msg

ERZ107010I CICS License Manager in Productionmode, serverLicenses licenses available

Explanation: The CICS License Manager has found avalid Production certificate, which allows serverLicensesconcurrent users. Note that this value applies on aserver-wide basis, and concurrent use is calculatedacross all active regions.

System action: The CICS License Manager sets thelicense use threshold at serverLicenses.

User response: If the value of serverLicenses licenses isnot correct, modify the number of licenses available toCICS regions on this server by using the NodelockAdministration Tool. The number of concurrent usersallowed by the CICS regions is determined by yourLicense Agreement.

Destination:

console.msg

ERZ107006I • ERZ107010I


ERZ107011E This Evaluation copy of CICS has nowexpired and cannot be started without aProduction certificate

Explanation: This copy of CICS is licensed forEvaluation use only. The Evaluation period has nowfinished, and you cannot now start CICS.

System action: The region shuts down.

User response: If you wish to continue to use CICS,please contact your IBM Authorized Dealer orRepresentative for a Production certificate.

Destination:

console.msg

ERZ107012W This is the final day of the Evaluationperiod for this copy of CICS

Explanation: This copy of CICS is licensed forEvaluation use only. The Evaluation period is now inits final day. After today, you will not be able to startCICS.


User response: The region continues to executenormally until the next time it is shut down. Thesystem cannot be restarted after today. If you have aProduction certificate, enroll it before you next startCICS. If you are evaluating CICS, please contact yourIBM Authorized Dealer or Representative for aProduction certificate.

Destination:

console.msg

ERZ107013I There is one day left in the Evaluationperiod for this copy of CICS

Explanation: This copy of CICS is licensed forEvaluation use only. The Evaluation period lasts forone further day, after which you will not be able tostart CICS.


User response: The region continues to executenormally until the end of the Evaluation period, afterwhich it cannot be restarted. If you have a Productioncertificate, enroll it before you next start CICS. If youare evaluating CICS, please contact your IBMAuthorized Dealer or Representative for a Productioncertificate.

Destination:

console.msg

ERZ107014I There are expiryPeriodRemaining days leftin the Evaluation period of expiryPerioddays for this copy of CICS

Explanation: This copy of CICS is licensed forEvaluation use only. The Evaluation period lasts forexpiryPeriod days from when you first started CICS. TheEvaluation period lasts for expiryPeriodRemainingfurther days, after which you will not be able to startCICS.



Destination:

console.msg

ERZ107015I This Evaluation copy of CICS islicensed for a limited period only

Explanation: This copy of CICS is an Evaluation copy,which is licensed for use for a limited duration. TheEvaluation period is nearing its end, after which youwill not be able to start CICS.



Destination:

console.msg

ERZ107016I Licenses available now: serverLicenses,licenses available previously:serverPreviousLicenses

Explanation: The number of licenses available to theCICS License Manager has changed.

System action: License management continues, usingthe new number of licenses.

User response: None required. This message is usedto indicate that the number of available licenses wasupdated.

Destination:

console.msg

ERZ107011E • ERZ107016I


ERZ107017I CICS License Manager now inProduction mode, regionUsage licensesrequested

Explanation: The CICS License Manager has found aProduction certificate and has changed the mode ofoperation from Evaluation to Production. The level ofusage in Evaluation mode is used to determine thenumber of licenses now required.

System action: License management changes tooperate in Production mode.

User response: This message indicates that the CICSLicense Manager has found a Production certificate thatwas enrolled after the region was started in Evaluationmode. In Evaluation mode, the CICS License Managerkeeps track of the region’s license requirements. Whena Production certificate becomes available, this value isused to request enough licenses to fulful the region’srequirements. If this value exceeds the number oflicenses associated with the Production certificate, thena warning message is issued, but CICS continues to runas normal.

Destination:

console.msg

ERZ107018I Licenses currently in use are belowthreshold - current usage: serverUsage,licenses available: serverLicenses

Explanation: The number of licenses in use is lessthan the number of licenses available to CICS. Thismessage is issued when usage is greater than thenumber of licenses available, to confirm that usage hasnow returned to below threshold.

System action: License management continues.

User response: If usage frequently exceeds thenumber of licenses available, increase the number oflicenses available to CICS. Use the NodelockAdministration Tool to update this value, and contactyour IBM Authorized Dealer or Representative toupdate your license agreement.

Destination:

console.msg

ERZ107019I Licenses currently in use are close tothreshold - current usage: serverUsage,licenses available: serverLicenses

Explanation: The number of licenses in use is lessthan the number of licenses available to CICS. Thismessage is issued to provide a warning when usage isapproaching the maximum number of licenses availableto CICS.


User response: If usage exceeds the number of

licenses available, a further warning message is issued.However, this message is issued to give you advancewarning that the threshold is approaching. Considerreducing the license usage by one or more regions toensure that the usage remains below the licensethreshold.

Destination:

console.msg

ERZ107020W New Region high water mark, licensescurrently in use exceed threshold -current usage: serverUsage, licensesavailable: serverLicenses

Explanation: The number of licenses in use exceedsthe number of licenses available to all CICS regionsrunning on this server. The level of usage exceeds thelocal (Region) high water mark value for the session.


User response: Consider reducing the usage by one ormore regions to bring total usage below the threshold.Use the Nodelock Administration Tool to update thenumber of licenses available to CICS regions on thisserver, and contact your IBM Authorized Dealer orRepresentative to update your license agreement. Notethat all CICS regions continue to run as normal whenlicense usage is above threshold.

Destination:

console.msg

ERZ107021W New Server high water mark, licensescurrently in use exceed threshold -current usage: serverUsage, licensesavailable: serverLicenses

Explanation: The number of licenses in use exceedsthe number of licenses available to all CICS regionsrunning on this server. The level of usage exceeds theglobal (Server) high water mark value for the session.


User response: Consider reducing the usage by one ormore regions to bring total usage below the threshold.Use the Nodelock Administration Tool to update thenumber of licenses available to CICS regions on thisserver, and contact your IBM Authorized Dealer orRepresentative to update your license agreement. Notethat all CICS regions continue to run as normal whenlicense usage is above threshold.

Destination:

console.msg

ERZ107017I • ERZ107021W


ERZ107022E The Evaluation License Agreement wasnot accepted and an Evaluationcertificate was not enrolled

Explanation: The Evaluation License Agreement mustbe accepted before CICS enrols an Evaluationcertificate. This Agreement was not accepted, and soCICS cannot enroll the certificate.


User response: If you have a Production certificate,enroll it before you next start CICS. If you wish toevaluate CICS, you must agree to the Terms andConditions defined in the License Agreement. Thisagreement is available as the file ’license.agr’ in theETC subdirectory of your CICS system. If you do notenroll a Production certificate, the License Agreement isdisplayed next time you start CICS.

Destination:

console.msg

ERZ107023E An error occurred attempting to displaythe Evaluation License Agreement

Explanation: The Evaluation License Agreement mustbe accepted before CICS enrols an Evaluationcertificate. CICS was unable to display the LicenseAgreement, and so cannot enroll the certificate.


User response: If you have a Production certificate,enroll it before you next start CICS. Ensure that the file’license.agr’ is available in the ETC subdirectory ofyour CICS system. If the problem persists, you can readthe License Agreement and enroll the Evaluationcertificate by using the Nodelock Administration Tool.The Evaluation certificate is called ’evaluate.lic’ and islocated in the ETC subdirectory. Enrolling thiscertificate constitutes acceptance of the Terms andConditions contained within the Evaluation LicenseAgreement.

Destination:

console.msg

ERZ107024E The CICS License Manager could notperform Evaluation mode initialization,reason code: reasonCode

Explanation: The CICS License Manager attempted toinitialize the system for Evaluation use, but was notsuccessful.


User response: If you have a Production certificate,you enroll it before you next start CICS. ThereasonCode value is an internal diagnostic code. Reportit to your IBM Representative or your supportorganization for further assistance. Look through the

message log for other License Manager errors that canprovide more information. For example, initializationcan fail if the Evaluation period has now expired.

Destination:

console.msg

ERZ107025I The CICS License Manager is shuttingdown, reason code: reasonCode

Explanation:

The CICS License Manager has started its shutdownprocessing. This does not always mean that the regionis also shutting down. The reason code is one of thefollowing:

0 An error has occurred in the CICS LicenseManager. The CICS region continues tooperate, but License Management is notavailable.

1 The CICS License Manager has detected thatCICS is shutting down.

2 The CICS License Manager received a requestto shut down. This normally occurs when theregion is shutting down.

System action: The region continues or shuts down,according to the reasonCode value.

User response: This message is for information only. Ifthe reasonCode indicates that an error has occurred,examine any trace resources that are available forfurther information on the problem. A possible cause ofthis error is a CICS internal error, such as a resourceshortage. Look for errors from other modules to see ifthis is a likely cause. If no other errors have occurred,then CICS continues to execute, but LicenseManagement is not available.

Destination:

console.msg

ERZ107026I The Evaluation License Agreement wasaccepted and an Evaluation certificatewas enrolled

Explanation: An Evaluation certificate was enrolledafter the License Agreement was accepted. This copy ofCICS is now licensed as an Evaluation copy.


User response: The Evaluation certificate licenses thiscopy of CICS for 90 days usage. During this period,CICS issues messages to indicate the number of daysuntil expiration. At any point during this period, youcan enroll a Production certificate to license the productfor continued use, subject to the associated Terms andConditions. There is no need to reinstall CICS whenchanging from Evaluation use to Production use, and

ERZ107022E • ERZ107026I


you can enroll a Production certificate while CICS isactive in Evaluation mode.

Destination:

console.msg

ERZ107027E The CICS License Manager failed toenrol an Evaluation certificate

Explanation: Although the Evaluation LicenseAgreement was accepted, CICS was not able to enrollthe Evaluation certificate. This copy of CICS is notlicensed for use as an Evaluation copy.


User response: The Evaluation certificate ’evaluate.lic’is found in the ETC subdirectory of your CICS system.If this file is not available, then CICS is unable tooperate in Evaluation mode. If the file is available,restart the CICS region and try again. If this fails, tryenrolling the Evaluation certificate using the NodelockAdministration Tool, and restart the region. Enrollingthis certificate constitutes acceptance of the Terms andConditions contained within the Evaluation LicenseAgreement.

Destination:

console.msg

ERZ107028E The CICS License Manager has detectedan internal integrity error

Explanation: The CICS License Manager performed aself-consistency check, and found an error in the Cruntime. The License Manager cannot validate thelicensing status of the region, so CICS is forciblyterminated.


User response: This error indicates that certain criticalfunctions in the C runtime module that CICS is usinghave failed unexpectedly. This implies a seriousproblem with the level of the runtime installed on thismachine. You must contact your support organizationwith detailed information concerning the level of the Cruntime module on your machine to resolve thisproblem.

Destination:

console.msg

ERZ107040E The supplied password exceeds themaximum length of passwordLength

Explanation: The password supplied on the commandline is greater than the maximum length ofpasswordLength.

System action: The program exits.

User response: Ensure that the password you are

using is correct. If the error occurs again, contact yourIBM Representative to request the correct password forthis operation.

Destination:

stderr

ERZ107041E The password option requires apassword to be specified

Explanation: The password option was specified onthe command line without a value for the passworditself.


User response: Add the password to the commandline after the password option. To request help with thecommand syntax, use the -? option.

Destination:

stderr

ERZ107042E The days option requires an expiryperiod to be specified

Explanation: The days option was specified on thecommand line without a value for the expirationperiod.


User response: Add the expiration period value to thecommand line after the days option. To request helpwith the command syntax, use the -? option.

Destination:

stderr

ERZ107043W The option ’optionText’ is not recognizedand is ignored

Explanation: The option was specified on thecommand line but was not recognized.

System action: The program ignores the option andcontinues.

User response: Ensure that the correct options arespecified on the command line. To request help withthe command syntax, use the -? option.

Destination:

stderr

ERZ107044W The option ’optionText’ is not valid andis ignored

Explanation: The option was specified on thecommand line but does not have the correct syntax.

System action: The program ignores the option andcontinues.

ERZ107027E • ERZ107044W


User response: Ensure that required options arespecified using the correct syntax. To request help withthe command syntax, use the -? option.

Destination:

stderr

ERZ107045E A password is required for thiscommand

Explanation: This command requires a passwordvalue to be specified, but the password is missing fromthe command line.


User response: Ensure that the correct password isspecified on the command line. To request help withthe command syntax, use the -? option.

Destination:

stderr

ERZ107046I Using default expiry period ofexpiryPeriod days

Explanation: The update is using the defaultexpiration period of expiryPeriod days.

System action: The program continues normally.

User response: None required. This message is forinformation only.

Destination:

stderr

ERZ107047E The expiry period specified (expiryPeriod)lies outside the valid rangeminimumPeriod to maximumPeriod days

Explanation: The requested duration for the expirationperiod lies outside of the supported range,minimumPeriod to maximumPeriod days.


User response: Ensure that the number of daysspecified for the expiration period lies within the limitsshown.

Destination:

stderr

ERZ107048E The expiry period specified (expiryPeriod)is not a multiple of expiryInterval

Explanation: The duration for the expiration periodmust be a multiple of expiryInterval, which is not truefor the specified value of expiryPeriod.


User response: Ensure that the number of days

specified for the expiration period is a multiple ofexpiryInterval days.

Destination:

stderr

ERZ107049I Using password ....... [expiryPassword]

Explanation: The program is using the passwordshown for the update operation.



Destination:

stderr

ERZ107050I Using expiry period .. [expiryPeriod]

Explanation: The program is using the expirationperiod shown for the update operation.



Destination:

stderr

ERZ109001I FEPI initialization starting

Explanation: The Front End Programming Interface(FEPI) global initialization module is initializing.

System action: The system continues.


Destination:

CSMT

ERZ109002I LU0 Listener starting

Explanation: The FEPI LU0 listener module is loadingand initializing.

System action: The system continues.


Destination:

CSMT

ERZ109003E LU0 not available, return code is’returnCode’

Explanation: The FEPI LU0 listener module failed toinitialize.

System action: FEPI LU0 support is disabled and thesystem continues.

ERZ107045E • ERZ109003E


User response: Ensure that IBM CommunicationsServer is properly installed and enabled, then restartthe system.

Destination:

CSMT

ERZ109004W Error loading SNA RUI module, returncode is ’returnCode’

Explanation: The SNA RUI communications modulefailed to load.

System action: FEPI LU0 support is disabled and thesystem continues.

User response: Ensure that IBM CommunicationsServer is properly installed, and then restart the system.

Destination:

CSMT

ERZ109005W FEPI table manager PUT has failed,’returnCode’

Explanation: The FEPI LU0 table manager module hasfailed to write a record.

System action: FEPI LU0 support is continued.

User response: Ensure that the table manager hasinitialized and that there is no shortage of region poolstorage.

Destination:

stderr

ERZ109006I FEPI target ’targetName’ discarded

Explanation: The given FEPI ’targetName’ wasdiscarded.



Destination:

CSZL

ERZ109007I FEPI target ’targetName’ discardscheduled

Explanation: The given FEPI ’targetName’ wasscheduled for discard once all active conversationsusing it have completed.



Destination:

CSZL

ERZ109008E FEPI target ’targetName’ discard failed,resp2=’responseCode’

Explanation: The given FEPI ’targetName’ has failed tobe discarded due to the given FEPI ’responseCode’response code.


User response: Look up the given FEPI resp2 responsecode in the TXSeries Infocenter to determine the givenproblem.

Destination:

CSZL

ERZ109009E FEPI set target ’targetName’ failed,resp2=’responseCode’

Explanation: The given FEPI ’targetName’ has failed tobe set as required due to the given FEPI ’responseCode’response code.



Destination:

CSZL

ERZ109010I FEPI node ’nodeName’ installed

Explanation: The given FEPI ’nodeName’ was installedsuccessfully.



Destination:

CSZL

ERZ109011E FEPI node ’nodeName’ installation failed,resp2=resp2

Explanation: The given FEPI ’nodeName’ has failed toinstall due to the given FEPI ’resp2’ response code.



Destination:

CSZL

ERZ109004W • ERZ109011E


ERZ109012I FEPI target ’targetName’ installed

Explanation: The given FEPI ’targetName’ wasinstalled successfully.



Destination:

CSZL

ERZ109013E FEPI target ’targetName’ installationfailed, resp2=resp2

Explanation: The given FEPI ’targetName’ has failed toinstall due to the given FEPI ’resp2’ response code.



Destination:

CSZL

ERZ109014I FEPI property set ’propertySetName’installed

Explanation: The given FEPI ’propertySetName’ wasinstalled successfully.



Destination:

CSZL

ERZ109015E FEPI property set ’propertySetName’installation failed, resp2=resp2

Explanation: The given FEPI ’propertySetName’ hasfailed to install due to the given FEPI ’resp2’ responsecode.



Destination:

CSZL

ERZ109016I FEPI pool ’poolName’ installed

Explanation: The given FEPI ’poolName’ was installedsuccessfully.



Destination:

CSZL

ERZ109017E FEPI pool ’poolName’ installation failed,resp2=resp2

Explanation: The given FEPI ’poolName’ has failed toinstall due to the given FEPI ’resp2’ response code.



Destination:

CSZL

ERZ109018I FEPI target ’targetName’ added to pool’poolName’

Explanation: The given FEPI ’targetName’ was addedto the given ’poolName’.



Destination:

CSZL

ERZ109019E FEPI target ’targetName’ not added topool ’poolName’, resp2=resp2

Explanation: The given FEPI ’targetName’ has failed tobe added to the ’poolName’ due to the given FEPI ’resp2’response code.



Destination:

CSZL

ERZ109020I FEPI node ’nodeName’ added to pool’poolName’

Explanation: The given FEPI ’nodeName’ was added tothe given ’poolName’.



Destination:

CSZL

ERZ109012I • ERZ109020I


ERZ109021E FEPI node ’nodeName’ not added to pool’poolName’, resp2=resp2

Explanation: The given FEPI ’nodeName’ has failed tobe added to the ’poolName’ due to the given FEPI ’resp2’response code.



Destination:

CSZL

ERZ109022E FEPI node ’nodeName’ release failed,RC=reasonCode

Explanation: The given FEPI ’nodeName’ has failed tobe released due to the given communications reasoncode.


User response: Look up the given reason code in theIBM Communications Server for Windows NTConventional LU Programming Reference to determinethe given problem.

Destination:

CSZL

ERZ109023E FEPI node ’nodeName’ acquire failed,RC=reasonCode

Explanation: The given FEPI ’nodeName’ has failed tobe acquired due to the given communications reasoncode.



Destination:

CSZL

ERZ109024E FEPI connection node ’nodeName’ target’targetName’ release failed,RC=reasonCode

Explanation: The given FEPI connection has failed tobe released due to the given communications reasoncode.



Destination:

CSZL

ERZ109025E FEPI connection node ’nodeName’ target’targetName’ acquire failed,RC=reasonCode

Explanation: The given FEPI connection has failed tobe acquired due to the given communications reasoncode.



Destination:

CSZL

ERZ109026I FEPI node ’nodeName’ discarded

Explanation: The given FEPI ’nodeName’ wasdiscarded.



Destination:

CSZL

ERZ109027I FEPI node ’nodeName’ discard scheduled

Explanation: The given FEPI ’nodeName’ wasscheduled for discard once all active conversationsusing it have completed.



Destination:

CSZL

ERZ109028E FEPI node ’nodeName’ discard failed,resp2=resp2

Explanation: The given FEPI ’nodeName’ has failed tobe discarded due to the given FEPI ’resp2’ responsecode.



Destination:

CSZL

ERZ109021E • ERZ109028E


ERZ109029I FEPI property set ’propertySetName’discarded

Explanation: The given FEPI ’propertySetName’ wasdiscarded.



Destination:

CSZL

ERZ109030E FEPI property set ’propertySetName’discard failed, resp2=resp2

Explanation: The given FEPI ’propertySetName’ hasfailed to be discarded due to the given FEPI ’resp2’response code.



Destination:

CSZL

ERZ109031I FEPI pool ’poolName’ discarded

Explanation: The given FEPI ’poolName’ wasdiscarded.



Destination:

CSZL

ERZ109032I FEPI pool ’poolName’ discard scheduled

Explanation: The given FEPI ’poolName’ wasscheduled for discard once all active conversationsusing it have completed.



Destination:

CSZL

ERZ109033E FEPI pool ’poolName’ discard failed,resp2=resp2

Explanation: The given FEPI ’poolName’ has failed tobe discarded due to the given FEPI ’resp2’ responsecode.


User response: Look up the given FEPI resp2 response

code in the TXSeries Infocenter to determine the givenproblem.

Destination:

CSZL

ERZ109034E FEPI set connection node ’nodeName’target ’targetName’ failed, resp2=resp2

Explanation: The given FEPI connection has failed tobe set as required due to the given FEPI ’resp2’response code.



Destination:

CSZL

ERZ109035E FEPI set node ’nodeName’ failed,resp2=resp2

Explanation: The given FEPI ’nodeName’ has failed tobe set as required due to the given FEPI ’resp2’response code.



Destination:

CSZL

ERZ109036E FEPI set pool ’poolName’ failed,resp2=resp2

Explanation: The given FEPI ’poolName’ has failed tobe set as required due to the given FEPI ’resp2’response code.



Destination:

CSZL

ERZ109037I FEPI node ’nodeName’ deleted from pool’poolName’

Explanation: The given FEPI ’nodeName’ was deletedfrom ’poolName’ successfully.



ERZ109029I • ERZ109037I


Destination:

CSZL

ERZ109038E FEPI node ’nodeName’ not deleted frompool ’poolName’, resp2=resp2

Explanation: The given FEPI ’nodeName’ has failed tobe deleted from ’poolName’ due to given FEPI ’resp2’response code.



Destination:

CSZL

ERZ109039I FEPI target ’targetName’ deleted frompool ’poolName’

Explanation: The given FEPI ’targetName’ was deletedfrom ’poolName’ successfully.



Destination:

CSZL

ERZ109040E FEPI target ’targetName’ not deleted frompool ’poolName’, resp2=resp2

Explanation: The given FEPI ’targetName’ has failed tobe deleted from ’poolName’ due to given FEPI ’resp2’response code.



Destination:

CSZL

ERZ109041E FEPI node ’nodeName’ has been released,RC=reasonCode

Explanation: The given FEPI ’nodeName’ was releaseddue to the given communications reason code.



Destination:

CSZL

ERZ109042E FEPI connection node ’nodeName’ target’targetName’ has been released,RC=reasonCode

Explanation: The given FEPI connection was releaseddue to the given communications reason code.



Destination:

CSZL

ERZ109043W FEPI table manager DELETE has failed,’returnCode’

Explanation: The FEPI LU0 table manager module hasfailed to delete a record.



Destination:

stderr

ERZ109044W FEPI table manager GET has failed,’returnCode’

Explanation: The FEPI LU0 table manager module hasfailed to read a record.



Destination:

stderr

ERZ109045I CICS listener ’listenerName’ process’cicslu’ started

Explanation: The start of a ’cicslu’ listener process wassuccessful.

System action: CICS allows FEPI LU0communications.

User response: None

Destination:

console.msg

ERZ109038E • ERZ109045I


ERZ109046W FEPI table manager storage allocatefailed

Explanation: The FEPI LU0 table manager module hasfailed to allocate a storage block.



Destination:

stderr

ERZ109047W LU0 Add Connection failed, ’returnCode’

Explanation: The LU0 Listener has failed to add anew connection due to the given returnCode.


User response: Ensure that the LU0 Listener hasinitialized and that there is no shortage of region poolstorage.

Destination:

stderr

ERZ109048E Unable to allocate storage for user exit31 (UE109031) parameter list


System action: The transaction is terminated withabend code, A82N as a result of a ’RECEIVE’ failureand A82O as the result of a ’SEND’ failure.

User response: Produce a SNAP dump and investigatestorage usage in the CICS region.

Destination:

console.msg

ERZ109049E User exit 31 (UE109031) returned anerror response errorMessage

Explanation: User exit 31 returned an error response.

System action: The transaction is terminated withabend code, A82N as a result of a ’RECEIVE’ failureand A82O as the result of a ’SEND’ failure.

User response: Investigate the user exit source todetermine why the error response was returned.

Destination:

console.msg

ERZ109050W FEPI exception handler thread invokedfor RUI ’returnCode’

Explanation: A try/catch block has caught anexception in a FEPI thread.


User response: Report the message to your supportrepresentative.

Destination:

stderr

ERZ111001E CICS has detected an internal errorwhile processing a request from a Javaprogram

Explanation: An internal error has occurred whileprocessing a request from a CICS Java Application.

System action: CICS abnormally terminates thetransaction. The application server continues and isavailable to run further transactions.

User response: If the problem persists, please contactyour support organization.

Destination:

CSMT

ERZ111002E There is insufficient memory availablefor CICS to process a request from aCICS Java Application

Explanation: The system is short on virtual memoryand therefore cannot perform requests for the CICSJava application that is running.

System action: CICS abnormally terminates thetransaction. The application server continues and isavailable to run further transactions.

User response: Try to determine the cause of theproblem, and if necessary, reallocate system resourcesto prevent it. If the problem persists, please contactyour support organization.

Destination:

CSMT

ERZ113001E In a CICS Java application, a request toinitiate an APPC mapped conversationhas failed as a process name was not set

Explanation: CICS is processing a conversation initiaterequest for a Java application. The request cannot becompleted as the ’AttachInitiator’ object specified onthe request has not had a process name set in it.

System action: The CICS condition exception’LengthErrorException’ is raised by CICS. If theexception s not caught, the transaction is abnormally

ERZ109046W • ERZ113001E


terminated with the abend code appropriate to thatcondition.

User response: Examine the application in error.Ensure the process name is set in the ’AttachInitiator’object before the initiate request is made.

Destination:

CSMT

ERZ113002E In a CICS Java application, a CICSmethod was invoked for a File objectwith a null filename

Explanation: CICS is processing a file control APIrequest for a Java application. The file object involvedin the request has a null filename, so no file operationis possible.

System action: The CICS condition exception’FileNotFoundException’ is raised by CICS. If theexception is not caught, the transaction is abnormallyterminated with the abend code appropriate for thatcondition.

User response: Examine the application in error, andset the filename in the File object before requesting afile control operation. This can be done when the objectis created or by using the setName method afterinstantiation of the object.

Destination:

CSMT

ERZ113003E In a CICS Java application, a deleterequest for RRDS file ’filename’ failed asthe record number, ’record_number’ is toohigh

Explanation: CICS is processing a delete request foran RRDS file in a CICS Java application. The recordnumber specified on the request is higher than themaximum limit imposed by the file system for thenumber of records.

System action: The CICS condition exception’RecordNotFoundException’ is raised by CICS. If theexception is not caught, the transaction is abnormallyterminated with the abend code appropriate for thatcondition.

User response: Examine the application in error andcorrect the record number value used on the deleterequest.

Destination:

CSMT

ERZ113004E In a CICS Java application, a request tostart or reset a browse on Keyed file’%1s’ has failed because the key wasnull

Explanation: CICS is processing a start or reset browserequest for a Keyed file in a CICS Java application. Thekey specified on the request is null, so the requestcannot be performed.

System action: The CICS condition exception’RecordNotFoundException’ is raised by CICS. If theexception is not caught, the transaction is abnormallyterminated with the abend code appropriate for thatcondition.

User response: Examine the application in error andset the required key value on the browse request.

Destination:

CSMT

ERZ113005E In a CICS Java application, a request tosend data to a terminalhas failed as thelength of the data, ’dataLength’ is greaterthan the maximum length, ’maxLength’

Explanation: CICS is processing a request to send textdata to a terminal for a CICS Java application. The datais too long for such a request to be completed. Themaximum length of data that can be sent is shown inthe message.

System action: The CICS condition exception’LengthErrorException’ is raised by CICS. If theexception is not caught, the transaction is abnormallyterminated with the abend code appropriate for thatcondition.

User response: Examine the application in error andreduce the data to the permitted length.

Destination:

CSMT

ERZ113006E In a CICS Java application, an operationon Temporary Storage Queue ’TSQName’has failed as the item number specified,’itemNumber’, is outside the permittedrange of ’minItemNumber’ to’maxItemNumber’

Explanation: CICS is processing an operation on aTemporary Storage Queue for a CICS Java Application.The request has failed because the item numberspecified on the request is outside the permitted range,which is shown in the message.

System action: The CICS condition exception’ItemErrorException’ is raised by CICS. If the exceptionis not caught, the transaction is abnormally terminatedwith the abend code appropriate for that condition.

ERZ113002E • ERZ113006E


User response: Examine the application in error andcorrect the item number to one within the permittedrange.

Destination:

CSMT

ERZ113007W The Temporary Storage Queue name,’InputTSQname’ in a CICS Javaapplication has been truncated to’TruncatedTSQname’

Explanation: CICS on Open Systems supportsTemporary Storage Queue names of up to eightcharacters. A CICS Java application has specified alonger name on a CICS request; the name wastruncated to the first eight characters.

System action: The request continues, using thetruncated name.

User response: Verify that the truncated name isadequate to ensure unique names for all TemporaryStorage Queues used in this CICS region.

Destination:

CSMT

ERZ113008E In a CICS Java application, CICS wasunable to throw an UnknownCicsErrorException

Explanation: This is an internal CICS error. There arepossibly accompanying messages that indicate thecause of the error, such as a lack of system memory.


User response: Identify the cause of the error fromaccompanying messages if possible, and rectify. If thiserror persists with no obvious cause, contact yoursupport organization.

Destination:

CSMT

ERZ113009E The following Java exception wasgenerated by transaction ’transId’:’exceptionText’

Explanation: The exception shown in the message wascaught by CICS while running a CICS Java programwithin the transaction shown.


User response: Identify the cause of the error, ifpossible, and rectify. If this error persists with noobvious cause, contact your support organization.

Destination:

CSMT

ERZ113010W The Visual Age Java Debugger hasfailed to start for transaction ’transId’,with error code ’errorCode’

Explanation: The Visual Age Java Debugger wasunable to attach to the CICS Java transaction indicated.The error code returned by the debugger is shown inthe message.

System action: The transaction continues to run, but itis not debugged.

User response: Determine the reason for the failureusing the error code in the message. Rectify and retry.

Destination:

CSMT

ERZ113011E CICS was unable to initialize a CICSJava Task for transaction ’transId’

Explanation: An error occurred while CICS wasinitializing a CICS Java task to run a Java programwithin the transaction shown.


User response: Identify the cause of the error, ifpossible, and rectify. There is generally be additionalinformation in the system console; for example, a Javastack trace. If this error persists with no obvious cause,contact your support organization.

Destination:

CSMT

ERZ113012E The CICS Java Wrapper has been passed’numArgs’ arguments, which is not avalid number

Explanation: This is an internal error in CICS Javasupport.



Destination:

console.msg

ERZ114001E ’TransID’ transaction was invokedincorrectly.

Explanation: The CICS IIOP ORB adapter programwas invoked incorrectly.

System action: The CICS IIOP ORB adapter programterminates.

ERZ113007W • ERZ114001E


User response: Establish how the ’TransID’ transactionwas invoked. This transaction must be started by theCICS IIOP listener.

Destination:

console.msg

ERZ114002I CICS IIOP ORB service initializationprogram ended.

Explanation: The CICS IIOP ORB initializationprogram has run to completion.

System action: The CICS IIOP ORB initializationprogram terminates.

User response: Check that no error messages occurredprior to this message indicating that the CICS IIOPORB environment was unable to be initialized.

Destination:

console.msg

ERZ114003E Abnormal termination UB401. CICS wasunable to attach shared memory.

Explanation: CICS was unable to attach the RegionPool shared memory. The access permissions to theCICS shared memory segments were possibly altered,or the data segment shared memory identifier waspossibly overwritten.

System action: CICS abnormally terminates the regionwith a UB401 termination code.

User response: Ask the system administrator to checkfor inconsistencies in the CICS shared memorysegments using the ipcs command; these segmentsmust have read and write permissions for the user’cics’ who must be a member of the user group ’cics’. Ifthe problem cannot be identified, call your supportorganization.

Destination:

console.msg

ERZ114004E CICS IIOP ORB issued the followingmessage from transaction ’TransID’:messageText

Explanation: The CICS IIOP ORB issued the errormessage specified by messageText.

System action: CICS creates a symptom record(symrec), and the CICS IIOP ORB continues executing.

User response: Perform any actions required by themessage. For example, if the error message textindicates java.lang.NoSuchMethodError, then check thatthe CLASSPATH environment variable includes allrequired Java classes and the ’cics’ userid has access tothe files and directories specified by CLASSPATH.

Check the symptom records for any relatedinformation.

Destination:

console.msg

ERZ114005E Error in CICS Object Definitionassociated with class ’className’.

Explanation: The class className was not found in theCICS Object Definitions. An entry for the genericfactory is required in the Object Definition tables.

System action: CICS returns an error indication(CosLifeCycle::NoFactory exception) to the clientapplication.

User response: Correct the CICS Object Definition forthe class.

Destination:

console.msg

ERZ114006E Error creating application object,classname ’className’, extra data’messageText’.

Explanation: An error occured while trying to createan object of classname ’className’. The system wasunable to create the Java implementation for this object.messageText possibly provides further information onthe cause of the failure.

System action: CICS returns an error indication(CosLifeCycle::NoFactory exception) to the clientapplication.

User response: Check for further ERZ114004E orERZ114031W messages indicating failures whenloading or creating the Java classes or objects. Checkthat the CICS Object Definition is correct and that theJava implementation for the class is installed correctly.In particular check that all subdirectories for the Javaclass are installed and that the class file path isaccessible by either the CLASSPATH, orAPPLICATIONCLASSPATH environment variables ifthe Object Definition specifies the class is reloadable.You can specify these environment variables in theregion environment file.

Destination:

console.msg

ERZ114007E Invalid ’kind’ in NameComponent,’interfaceType’.

Explanation: There is an error in the client program.The client program must specify ″object interface″ asthe kind field in the CosNaming::NameComponentfield when creating an object. However, it specified’interfaceType’.

System action: CICS returns an error indication

ERZ114002I • ERZ114007E


(CORBA::BAD_PARAM system exception) to the clientapplication.

User response: Correct the client application.

Destination:

console.msg

ERZ114008E Abnormal termination AB41: Errorcreating application object.

Explanation: An internal error occurred processing theinternal class table.

System action: CICS terminates the application serverwith an abend code of AB41.

User response: Check console.msg and the symptomrecords for further information. If the problem cannotbe identified, call your support organization.

Destination:

console.msg

ERZ114009E Abnormal termination AB42: No factoryfor Java object creation.

Explanation: An internal error has occurred. CICS hasdiscovered that it does not have a factory for thecreation of Java objects.

System action: CICS terminates the application serverwith an abend code of AB42.

User response: Check console.msg and the symptomrecords for further information. If the problem cannotbe identified, call your support organization.

Destination:

console.msg

ERZ114010E CICS IIOP ORB internal error, codeerrorCode.

Explanation: An internal error occurred in the CICSIIOP ORB, further identified by errorCode.

System action: The CICS IIOP ORB terminates.

User response: Check console.msg and the symptomrecords for further information. If the problem cannotbe identified, make a note of the errorCode and call yoursupport organization.

Destination:

console.msg

ERZ114011E CICS is unable to initialize the ORBInterface Repository.

Explanation: CICS is unable to create an initializationfile called ″.odbc.ini″ in the region directory. This file isused to control initialization of the Interface Repositoryfor the ORB.

System action: The CICS region terminates withabend code UB402.

User response: Check the symrecs file for furtherinformation and correct the problem before restartingthe CICS region.

Destination:

console.msg

ERZ114012E Object reference not recognised by CICSIIOP ORB.

Explanation: The CICS IIOP ORB encounteredunrecognised reference data in a CORBA objectreference. Either the reference data is corrupted, or theobject reference was created by a different ORB.

System action: CICS returns an error to the clientapplication.

User response: Ensure the client application is usingthe correct object reference. If you have recentlyupgraded the level of CICS, ensure the object referenceof the generic factory (’genfac.ior’ file) wasredistributed to the clients.

Destination:

console.msg

ERZ114013E Unable to create object, CORBAexception id ’exceptionId’.

Explanation: An error occurred when the CICS IIOPORB generic factory attempted to create an object.’exceptionId’ identifies the CORBA exception that hasoccurred.

System action: CICS returns an error to the clientapplication.

User response: Ensure the object implementation iscorrectly configured to the CICS region. Previousmessages possibly give additional details of the failure.

Destination:

console.msg

ERZ114014W CICS is unable to create ’genfac.ior’ file.Error number errorNumber.

Explanation: CICS is unable to create a file called’genfac.ior’ in the region directory. This file holds theIOR to the CICS Generic Factory for the ORB.errorNumber is the error number returned to CICS bythe operating system.

System action: The system continues operation.

User response: Refer to the relevant operating systemdocumentation for an explanation of the error number.Without access to a Generic Factory IOR, IIOP clientsare not able to connect to the CICS region.

ERZ114008E • ERZ114014W


messages and codes · 2018. 6. 11. · erz001004e cobol runtime was not able to find program...

Documents