CICS TS for z/OS 4.2: CICSPlex SM Messages and Codes · SM element of CICS ® T ransaction Server...

CICS Transaction Server for z/OSVersion 4 Release 2

CICSPlex SM Messages and Codes

GC34-7201-01

IBM

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

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

© Copyright IBM Corporation 1999, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . vWho this book is for. . . . . . . . . . . . vTerminology . . . . . . . . . . . . . . v

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

Chapter 1. Introduction . . . . . . . . 1Message identifiers . . . . . . . . . . . . 1

Action and severity codes . . . . . . . . . 1Format of message descriptions . . . . . . . . 2CICSPlex SM messages . . . . . . . . . . . 2

Trace records . . . . . . . . . . . . . 2Console messages. . . . . . . . . . . . 2

Chapter 2. EYUARnnnn messages . . . 3

Chapter 3. EYUBInnnn messages . . . . 9

Chapter 4. EYUBMnnnn messages . . . 11

Chapter 5. EYUBNnnnn messages . . . 19

Chapter 6. EYUBUnnnn messages . . . 23

Chapter 7. EYUCCnnnn messages . . . 25

Chapter 8. EYUCInnnn messages . . . 27

Chapter 9. EYUCLnnnn messages . . . 33

Chapter 10. EYUCPnnnn messages . . 43

Chapter 11. EYUCRnnnn messages . . 53

Chapter 12. EYUCSnnnn messages . . 55

Chapter 13. EYUCTnnnn messages . . 61

Chapter 14. EYUCWnnnn messages . . 63

Chapter 15. EYUHInnn messages . . . 65

Chapter 16. EYUMMnnnn messages . . 67

Chapter 17. EYUNLnnnn messages . . 75

Chapter 18. EYUNXnnnn messages . . 89

Chapter 19. EYUPEnnnn messages . . 99

Chapter 20. EYUPInnnn messages 101

Chapter 21. EYUPMnnnn messages 103

Chapter 22. EYUPNnnnn messages 107

Chapter 23. EYUPPnnnn messages 115

Chapter 24. EYUPRnnnn messages 119

Chapter 25. EYUPSnnnn messages 121

Chapter 26. EYUPTnnnn messages 123

Chapter 27. EYUTInnnn messages 125

Chapter 28. EYUTSnnnn messages 127

Chapter 29. EYUTTnnnn messages 135

Chapter 30. EYUVCnnnn messages 137

Chapter 31. EYUVEnnnn messages 157

Chapter 32. EYUVHnnnn messages 167

Chapter 33. EYUVSnnnn messages 169

Chapter 34. EYUWGnnnn messages 187

Chapter 35. EYUWInnnn messages 189

Chapter 36. EYUWMnnnn messages 193

Chapter 37. EYUWRnnnn messages 203

Chapter 38. EYUWTnnnn messages 209

Chapter 39. EYUXCnnnn messages 211

Chapter 40. EYUXDnnnn messages 215

Chapter 41. EYUXEnnnn messages 239

Chapter 42. EYUXLnnnn messages 247

Chapter 43. EYUXMnnnn messages 269

Chapter 44. EYUXQnnnn messages 271

© Copyright IBM Corp. 1999, 2014 iii

Chapter 45. EYUXSnnnn messages 273

Chapter 46. EYUXUnnnn messages 281

Chapter 47. EYUXZnnnn messages 299

Chapter 48. Debugging transactionmessages . . . . . . . . . . . . . 305COD0 messages . . . . . . . . . . . . 305CODB messages . . . . . . . . . . . . 306CMAS shutdown transaction messages . . . . . 307

Chapter 49. Abend and dump codes 309CICS abend and dump codes . . . . . . . . 309Uxxxx abend codes . . . . . . . . . . . 311

System dump codes . . . . . . . . . . . 311

Notices . . . . . . . . . . . . . . 313Trademarks . . . . . . . . . . . . . . 314

Bibliography. . . . . . . . . . . . 315CICS books for CICS Transaction Server for z/OS 315CICSPlex SM books for CICS Transaction Serverfor z/OS . . . . . . . . . . . . . . . 316Other CICS publications . . . . . . . . . . 316

Accessibility . . . . . . . . . . . . 317

Index . . . . . . . . . . . . . . . 319

iv CICS TS for z/OS 4.2: CICSPlex SM Messages and Codes

Preface

This book contains all the messages issued by the CICSPlex® SM element of CICS®

Transaction Server for z/OS®.

It is closely linked with the CICSPlex System Manager Problem Determination manual,which should also be consulted if a message indicates there is a problem withCICSPlex SM.

Who this book is forThis book is for anyone who needs to understand and respond to CICSPlex SMmessages, including CICS operators, system programmers, and systemadministrators.

You can refer to this book for the meaning of a message without understanding thebook as a whole. Your understanding of CICSPlex SM, however, will be enhancedby a knowledge of the types of messages CICSPlex SM produces, the differentplaces it sends messages, and the different audiences it intends to reach. For astructural overview of the product, see the CICSPlex System Manager ProblemDetermination manual.

TerminologyIn the text of this book, the term CICSPlex SM (spelled with an uppercase letter P)means the IBM® CICSPlex System Manager element of CICS TS.

The term CICSplex (spelled with a lowercase letter p) means the largest set of CICSsystems to be managed by CICSPlex SM as a single entity.

The term MVS™ means MVS/ESA.

The phrase issue the command is used in this book to mean that the command mayeither be typed in the COMMAND field of an Information Display panel orinvoked by pressing the PF key to which it is assigned. When the location of thecursor affects command processing, this phrase means that you can do one of thefollowing:v Type the command in the COMMAND field, place the cursor on the appropriate

field, and press Enter.v Move the cursor to the appropriate field and press the PF key to which the

command is assigned.

© Copyright IBM Corp. 1999, 2014 v

vi CICS TS for z/OS 4.2: CICSPlex SM Messages and Codes

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

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

v CICS Transaction Server for z/OS Upgrading from CICS TS Version 4.1



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

© Copyright IBM Corp. 1999, 2014 vii

viii CICS TS for z/OS 4.2: CICSPlex SM Messages and Codes

Chapter 1. Introduction

CICSPlex SM produces the following types of message:v Operator messages issued to the console, a job log, or bothv End-user messages issued to the Web User Interface web browserv Batch report messages issued by the data repository or trace facilities

Message identifiersCICSPlex SM messages begin with EYU, followed by a two-letter componentidentifier and a four-digit message number.

‘EYU’ is the IBM-assigned identifier for CICSPlex SM modules. The componentidentifier shows the component that issues the message. The following table liststhe component identifiers and their associated components.

Table 1. EYU message identifiers and their componentsPrefix Component Location

EYUAR Application programming interface (REXX)EYUBx Business Application Services (BAS)EYUCx CommunicationsEYUMM Monitor ServicesEYUNx Managed Application System (MAS)EYUPx Real-time analysisEYUTx Topology ServicesEYUWx Workload ManagerEYUXC Data Cache ManagerEYUXD Data RepositoryEYUXE Environment Services System Services (ESSS)EYUXL Kernel LinkageEYUXM Message ServicesEYUXQ Queue ManagerEYUXS Common ServicesEYUXU Batched Repository FacilityEYUXZ Trace Services

Action and severity codesMessage identifiers are followed by an action or severity code (for example,EYUCI0102W) that identifies the type of response that is required to the message.The following action and severity codes are used:

A Immediate action required.

D Immediate decision required.

E Error. Something has gone wrong; some action may be required by theuser before CICSPlex SM processing can continue.

I Information only; no action is required.

S Severe error. Something serious has gone wrong; CICSPlex SM processingis suspended until corrective action has been taken.

© Copyright IBM Corp. 1999, 2014 1

U Unrecoverable error; CICSPlex SM processing terminates.

W Warning. Something may have gone wrong, but CICSPlex SM processingcontinues.

Format of message descriptionsEach CICSPlex SM message description consists of the following:

Message identifierIn the form EYUccnnnn.

Message textThe words and variable inserts that make up the message as displayed byCICSPlex SM.

ExplanationA description of the events leading to or following the production of themessage.

System actionThe action that has been or will be taken by CICSPlex SM.

User responseThe recommended action to be taken by the user.

DestinationThe device or log to which the message is sent. The destination can be oneor more of the following:v Console (refers to a specific type of terminal attached to CICS)v CICS terminalv EYULOGv Job logv SYSOUT

Module(s)The name or names of the module or modules that caused the message tobe sent. (This is not necessarily the module that issued the macro to writethe message.)

CICSPlex SM messagesAll CICSPlex SM messages are listed alphanumerically. The information includesan explanation of each message, the system response, an action you can take toresolve the message, the destination to which the message is written, and thenames of one or more modules that may issue the message.

Trace recordsMany of the EYU messages are accompanied by trace records, which provideadditional diagnostic information. CMAS and MAS trace records are written asCICS user trace records to the CICS trace data set. For more information about theCICSPlex SM trace facilities, see the CICSPlex System Manager ProblemDetermination manual.

Console messagesAll EYU messages that are issued to the console are prefixed with the date, time,and application ID of the CMAS or MAS to which the message applies.

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

Chapter 2. EYUARnnnn messages

EYUARnnnn messages are issued by the REXX run-time interface of the applicationprogramming interface (API). The run-time interface makes one pass through aREXX program to check the syntax of any CICSPlex SM API commands and asecond pass to evaluate the content of those commands. Note that none of theconditions described by these messages affect the REXX program as a whole.Depending on how it deals with error conditions, the program may continue torun after an EYUARnnnn message is issued.

EYUARnnnn messages are issued to the destination defined on your system forIRXSAY WRITEERR output. By default, such output goes to one of the followingplaces:v In TSO foreground, the output goes to the terminal.v In background, including batch, the output goes to the SYSTSPRT DD

destination.

EYUAR0001E Command (cmdname) invalid.

Explanation: The specified command is not a validAPI command, where:

cmdnameis the command name that was specified.

System action: Processing of the current APIcommand terminates.

User response: Review the syntax of available APIcommands in the CICSPlex System Manager ApplicationProgramming Guide manual. Then correct the error andrerun the REXX program.

Module: EYU0ARCL

Destination: As defined by REXX IRXSAY WRITEERRfunction

EYUAR0002E Keyword (parm) invalid for command.

Explanation: The specified keyword parameter is notvalid for the current API command, where:

parm is the keyword parameter that is invalid.

System action: The remainder of the current APIcommand syntax is checked, if possible. However,processing of the current command terminates.

User response: Review the syntax of the currentcommand in the CICSPlex System Manager ApplicationProgramming Guide manual. Then correct the error andrerun the REXX program.

Module: EYU0ARKL


EYUAR0003E Required keyword (parm) missing.

Explanation: The specified keyword parameter, whichis required for the current API command, was notfound, where:

parm is the keyword parameter that is required.


User response: Review the syntax of the currentcommand in the CICSPlex System Manager ApplicationProgramming Guide manual. Then add the requiredparameter and rerun the REXX program.

Module: EYU0ARRF


EYUAR0005E Argument missing for keyword(parm).

Explanation: The specified keyword parameterrequires an argument, but none was found, where:

parm is the keyword parameter that requires anargument.


User response: Review the syntax of the currentcommand in the CICSPlex System Manager ApplicationProgramming Guide manual. Then add the requiredargument and rerun the REXX program.

Module: EYU0ARCL, EYU0ARKL



EYUAR0006E Command (cmdname) too long.

Explanation: The length of the specified APIcommand is too long, where:

cmdnameis the command name that is too long.


User response: Review the syntax of the specified APIcommand in the CICSPlex System Manager ApplicationProgramming Guide manual. Then correct the error andrerun the REXX program.

Module: EYU0ARPR


EYUAR0007E Keyword (parm) too long.

Explanation: The length of the specified keywordparameter is too long, where:

parm is the keyword name that is too long.


User response: Review the syntax of the current APIcommand in the CICSPlex System Manager ApplicationProgramming Guide manual. Then correct the error andrerun the REXX program.

Module: EYU0ARPR


EYUAR0008E Unexpected end of commandencountered.

Explanation: The API command that was beingprocessed ended unexpectedly before anend-of-command delimiter was found. One reason forthis error could be that a closing parenthesis is missingfrom the command syntax.


User response: Check the current API command forsyntax errors. Correct any errors and rerun the REXXprogram.

Module: EYU0ARPR, EYU0ARRF


EYUAR0009E Duplicate keyword (parm)encountered.

Explanation: The specified keyword parameter wasfound more than once in the current API command,where:

parm is the name of the keyword parameter that is aduplicate.


User response: Remove the duplicate parameter andrerun the REXX program.

Module: EYU0ARFB


EYUAR0010E Argument not valid for keyword(parm).

Explanation: The specified keyword parameter doesnot accept an argument, but one was found, where:

parm is the name of the keyword parameter.


User response: Remove the argument from thespecified parameter and rerun the REXX program.

Module: EYU0ARCL, EYU0ARKL


EYUAR0011E Parameter data (data) too long forkeyword (parm).

Explanation: The data supplied with the specifiedkeyword parameter is too long for the parameter's datatype, where:

data is the data that was specified.



User response: Review the description of the specifiedparameter in the CICSPlex System Manager ApplicationProgramming Reference manual. Then correct the errorand rerun the REXX program.

Module: EYU0ARFB


EYUAR0006E • EYUAR0011E


EYUAR0012E Parameter data (data) invalid forkeyword (parm).

Explanation: The data supplied with the specifiedkeyword parameter is not the correct type for thatparameter, where:

data is the data that was specified.




Module: EYU0ARFB


EYUAR0013E The variable parameter (var) forkeyword (parm) is invalid.

Explanation: REXX considers the variable identifiedwith the specified keyword parameter to be invalid,where:

var is the variable name that is invalid.




Module: EYU0ARFB, EYU0ARRF


EYUAR0014E The variable parameter (var) forkeyword (parm) is too long.

Explanation: The length of the specified variableparameter is too long, where:

var is the variable name that is too long.






EYUAR0015E The variable parameter (var) forkeyword (parm) contains no data.

Explanation: The variable identified with the specifiedkeyword parameter was either not initialized or is null,where:

var is the variable that was specified.



User response: Make sure the variable was specifiedcorrectly and that it contains appropriate data. Thenrerun the REXX program.



EYUAR0016E Conflicting keyword (parm) specified.

Explanation: The specified keyword parameterconflicts with another parameter in the same APIcommand, where:

parm is the name of the keyword parameter that isin conflict.

System action: The remainder of the current APIcommand syntax is checked, if possible. AnotherEYUAR0016E message may be issued when the otherconflicting parameter is identified. Processing of thecurrent command terminates.

User response: Review the syntax of the current APIcommand in the CICSPlex System Manager ApplicationProgramming Reference manual. Then remove theconflicting parameter and rerun the REXX program.



EYUAR0016E Conflicting keyword (parm) specified.

Explanation: The specified keyword parameterconflicts with another parameter in the same APIcommand, where:

parm is the name of the keyword parameter that isin conflict.

System action: The remainder of the current APIcommand syntax is checked, if possible. AnotherEYUAR0016E message may be issued when the otherconflicting parameter is identified. Processing of the


Chapter 2. EYUARnnnn messages 5

current command terminates.

User response: Review the syntax of the current APIcommand in the CICSPlex System Manager ApplicationProgramming Reference manual. Then remove theconflicting parameter and rerun the REXX program.




Explanation: The indicated keyword is required andwas not found.

Explanation: The specified keyword parameter isrequired for the current API command, but it was notsupplied, where:

parm is the name of the keyword parameter that isrequired.


User response: Add the required parameter and rerunthe REXX program.

Module: EYU0ARFB



Explanation: The indicated keyword is required andwas not found.

Explanation: The specified keyword parameter isrequired for the current API command, but it was notsupplied, where:

parm is the name of the keyword parameter that isrequired.


User response: Add the required parameter and rerunthe REXX program.

Module: EYU0ARFB


EYUAR0020E Data for variable (var) of keyword(parm) is too long.

Explanation: The variable identified with the specifiedkeyword parameter contains data that is too long forthat parameter, where:

var is the variable that was specified.



User response: If the command being processed wasTBUILD or TPARSE, the data being passed by yourprogram may be invalid. Otherwise, contact your IBMSupport Center with the name of the resource tablebeing processed and a record of the data being passedwhen this message was issued.

Module: EYU0ARFI, EYU0ARRB, EYU0ARRF


EYUAR0021E Data for attribute (attr) is too long.

Explanation: The data supplied for the specifiedresource table attribute is too long for that attribute,where:

attr is the name of the attribute.


User response: Review the description of the specifiedattribute in the CICSPlex System Manager Resource TablesReference manual. Then correct the error and rerun theREXX program.

Module: EYU0ARRB


EYUAR0022E Data for attribute (attr) is invalid.

Explanation: The data supplied for the specifiedresource table attribute is invalid for that attribute,where:

attr is the name of the attribute.


User response: Review the description of the specifiedattribute in the CICSPlex System Manager Resource TablesReference manual. Then correct the error and rerun theREXX program.

Module: EYU0ARRB




EYUAR0023E Argument is required for functionfunc.

Explanation: The specified function requires anargument, but none was found, where:

func is the function that requires an argument.

System action: Function processing terminates with areturn code of -1.

User response: For a list of the return codes and thesyntax for the specified function, refer to the CICSPlexSystem Manager Application Programming Guide manual.Then add the required argument and rerun the REXXprogram.

Module: EYU0AREY


EYUAR0024E Argument is not permitted forfunction var.

Explanation: The specified function does not accept anargument, but one was found, where:

func is the function that does not accept anargument.


User response: For a list of the return codes and thesyntax for the specified function, refer to the CICSPlexSystem Manager Application Programming Guide manual.Then remove the argument from the specified functionand rerun the REXX program.

Module: EYU0AREY


EYUAR0025E Argument (arg) is invalid for functionfunc.

Explanation: REXX considers the argument identifiedwith the specified function to be invalid, where:

arg is the argument that was specified.

func is the name of the function.


User response: For a list of the return codes and thesyntax for the specified function, refer to the CICSPlexSystem Manager Application Programming Guide manual.Then correct the argument and rerun the REXXprogram.

Module: EYU0AREY


EYUAR0026E Object (name) is not found.

Explanation: A TBUILD or TPARSE command wasissued, but the object specified on the OBJECT optioncould not be found, where name is the object namespecified on the OBJECT option.

System action: The TBUILD or TPARSE commandreturns a STATUS value of FAILURE. Trace records arewritten to the EYUTRACE stem variable.

User response: Make sure the OBJECT optionidentifies a valid CICSPlex SM resource table.

The TBUILD and TPARSE commands cannot be used toprocess a user-defined view of a resource table. If youdefine a view with the same name as a suppliedresource table and then issue a TBUILD or TPARSEcommand for that object, the API attempts to processthe view and fails.

Module: EYU0ARRF


EYUAR0027E Object (name) is invalid for TBUILDcommand.

Explanation: A TBUILD command was issued, but theobject specified on the OBJECT option is not valid,where name is the object name specified on the OBJECToption. The TBUILD command can only be used onCICSPlex SM definitions. A definition is represented bya CICSPlex SM resource table with a type of CPSMDefinition.

System action: The TBUILD command returns aSTATUS value of FAILURE. Trace records are written tothe EYUTRACE stem variable.

User response: Make sure the OBJECT optionidentifies a valid CPSM Definition resource table.

Module: EYU0ARRB



Chapter 2. EYUARnnnn messages 7

Chapter 3. EYUBInnnn messages

EYUBI0003I BAS Initialization Complete

Explanation: Initialization of Business ApplicationServices (BAS) completed successfully.

System action: Processing continues.

User response: None.

Module: EYU0BINT

Destination: EYULOG

EYUBI0004I BAS initialization for CICSplex plexnamehas started

Explanation: BAS has started to initialize datastructures for a CICSplex, where:

plexnameis the name of the CICSplex.

This can occur either during CMAS initialization, orafter a new CICSplex has been added to a CMAS.

System action: The BAS internal data structures forthe CICSplex are initialized.

User response: None

Module: EYU0BIBD

Destination: EYULOG

EYUBI0005I BAS initialization for CICSplex plexnamecomplete

Explanation: BAS has ended the initialization of datastructures for a CICSplex, where:



System action: The CICSplex is now available for BASprocessing in the CMAS and the MASs connected tothe CMAS.

User response: None

Module: EYU0BIBD

Destination: EYULOG

EYUBI0006I BAS termination for CICSplex plexnamehas started

Explanation: BAS has started to remove datastructures for a CICSplex, where:


This can occur either during CMAS termination, orafter a CICSplex has been removed from a CMAS.

System action: The BAS internal data structures forthe CICSplex are removed.

User response: None

Module: EYU0BIBD

Destination: EYULOG

EYUBI0007I BAS termination for CICSplex plexnameis complete

Explanation: BAS has ended the removal of datastructures for a CICSplex, where:



System action: The CICSplex is no longer available forBAS processing in the CMAS and the MASs connectedto the CMAS.

User response: None

Module: EYU0BIBD

Destination: EYULOG

EYUBI0102E BAS initialization for CICSplex plexnamehas failed

Explanation: BAS has experienced a failure whileinitializing the data structures for a CICSplex, where:



System action: The CICSplex is not available for BASprocessing in the CMAS and the MASs connected tothe CMAS.

User response: Determine if other messages occurredearlier that may explain the failure (e.g., the CICSplexwas removed from the CMAS). If not, collect the CMASjob output and auxtrace data set(s) and contact yourIBM Support Center.

Module: EYU0BIBD

Destination: Console, job log, EYULOG


EYUBI0103E BAS termination for CICSplex plexnamehas failed

Explanation: BAS has experienced a failure whileremoving the data structures for a CICSplex, where:



System action: Processing continues, possibly withorphaned data structures.

User response: Determine if other messages occurredearlier that may explain the failure (e.g., the BASinitialization for the CICSplex failed). If not, collect theCMAS job output and auxtrace data set(s) and contactyour IBM Support Center.

Module: EYU0BIBD


EYUBI0103E


Chapter 4. EYUBMnnnn messages

The following variables are commonly used in the EYUBMnnnn messages:

event1An event notification that is not recognized by Business Application Services.

event2One of the following event notifications:EDEFCHG EMASSTRTECSYSCHG EPLEXCHGEMASJOIN ESGRPCHGEMASSTOP

resassgnThe name of a resource assignment. The absence of a resource assignmentname indicates that the resource group was in a resource description.

resdescThe name of a resource description.

resgroupThe name of the resource group.

resnameThe name of the resource.

restypeThe name of a resource type. See Managing Business Applications for a completelist of resource types.

resversThe version of the definition record in the CICSPlex SM CMAS DataRepository.

scopeThe name of the target, related, or install scope, as indicated in the messagetext.

sysgroupThe name of the CICS systems group. The absence of a system group nameindicates that the system itself is the scope.

systemThe name of the CICS system.

usageIndicates how the resource will be used (locally, remotely, or as is).

EYUBM0101W BAS encountered an unknown eventnotification (event1)

Explanation: BAS received an unsolicited eventrecord.

System action: BAS ignores the event record andcontinues processing. The invalid event record iswritten to the CICS trace data set.

User response: Collect the trace records and anyrelated messages and contact your IBM Support Center.

Module: EYU0BMLT

Destination: Console, EYULOG

EYUBM0102W BAS has reported an error processingevent (event2)

Explanation: BAS experienced an internal error whileattempting to process the specified event.

System action: BAS event processing continues. Auser trace record is written to the CICS trace data set.


User response: Collect the trace records, any relatedmessages, and the job log and contact your IBMSupport Center.

Module: EYU0BMLT


EYUBM0301E Addition of System (system) to SystemGroup (sysgroup) would cause aninconsistent resource set

Explanation: An attempt to add the specified systemto the specified system group failed because it wouldresult in an inconsistent set of resources.

System action: Additional, detailed EYUBM032nImessages are written to the EYULOG.

User response: See the additional messages for furtherexplanation.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0302E Addition of Definition(restype,resname,resvers) to ResourceGroup (resgroup) would cause aninconsistent resource set

Explanation: An attempt to add the specifieddefinition to the specified resource group failed becauseit would result in an inconsistent set of resources.



Module: EYU0BMSG

Destination: EYULOG

EYUBM0303E Update of Definition(restype,resname,resvers) in ResourceGroup (resgroup) would cause aninconsistent resource set

Explanation: An attempt to update the specifieddefinition to the specified resource group failed becauseit would result in an inconsistent set of resources.



Module: EYU0BMSG

Destination: EYULOG

EYUBM0304E Addition of Resource Assignment(resassgn) to Resource Description(resdesc) for Resource Type (restype)would cause an inconsistent resource set

Explanation: An attempt to add the specified resourceassignment to the specified resource description failedbecause it would result in an inconsistent set ofresources.



Module: EYU0BMSG

Destination: EYULOG

EYUBM0305E Addition of Resource Group (resgroup)to Resource Description (resdesc) wouldcause an inconsistent resource set

Explanation: An attempt to add the specified resourcegroup to the specified resource description failedbecause it would result in an inconsistent set ofresources.



Module: EYU0BMSG

Destination: EYULOG

EYUBM0306E Update of Resource Assignment(resassgn) in Resource Description(resdesc) for Resource Type (restype)would cause an inconsistent resource set

Explanation: An attempt to update the specifiedresource assignment (RASGNDEF) contained in thespecified resource description failed because it wouldresult in an inconsistent set of resources.



Module: EYU0BMSG

Destination: EYULOG

EYUBM0307E Update of Resource Assignment inResource Description for(resassgn,resdesc) and Resource Type(restype) would cause an inconsistentresource set

Explanation: An attempt to update the specified

EYUBM0301E • EYUBM0307E


resource assignment contained in the specified resourcedescription (RASINDSC) failed because it would resultin an inconsistent set of resources.



Module: EYU0BMSG

Destination: EYULOG

EYUBM0308E Update of Resource Description(resdesc) with Install Scope (scope) wouldcause an inconsistent resource set

Explanation: An attempt to update the specifiedresource description with the specified install scopefailed because it would result in an inconsistent set ofresources.



Module: EYU0BMSG

Destination: EYULOG

EYUBM0309E Update of Resource Description(resdesc) for Resource Type (restype) andResource Assignment (resassgn) wouldcause an inconsistent resource set

Explanation: An attempt to update the specifiedresource description, which contains the specifiedresource assignment, failed because it would result inan inconsistent set of resources.



Module: EYU0BMSG

Destination: EYULOG

EYUBM0320I The Candidate definition(restype,resname,resvers) is in ResourceGroup (resgroup) for ResourceAssignment (resassgn) with [override |no override] and Usage (usage) inResource Description (resdesc) for [target| related] system (system) in systemgroup (sysgroup)

Explanation: This message follows an EYUBM030nEmessage and provides diagnostic information for thatmessage.

System action: The addition of the Business

Application Services administration definition indicatedin the accompanying EYUBM030nE message is notperformed.

User response: Review the information in thismessage to determine why the attempted additionwould cause an inconsistent set of resources. If themessage indicates that an override expression wasspecified for the resource assignment, the expressionmight be the cause of the conflict.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0321I The existing definition(restype,resname,resvers) is in ResourceGroup (resgroup) for ResourceAssignment (resassgn) with [override |no override] and Usage (usage) inResource Description (resdesc) for [target| related] system (system) in systemgroup (sysgroup)

Explanation: This message follows an EYUBM030nEmessage and provides diagnostic information for thatmessage.

System action: The update of the Business ApplicationServices administration definition indicated in theaccompanying EYUBM030nE message is not performed.

User response: Review the information in thismessage to determine why the attempted updatewould cause an inconsistent set of resources. If themessage indicates that an override expression wasspecified for the resource assignment, the expressionmight be the cause of the conflict.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0328E BAS has exhausted its supply ofassociation elements in this CMAS

Explanation: While attempting to define anassociation between BAS entities, no free BASAssociation Matrix Elements were found.

System action: Definition of the current BAS entity orassociation fails.

User response: Increase the value of BASASSOCBLKin the CMAS EYUPARM file and restart the CMAS.Each Association Block adds 257544 Association MatrixElements. Note that a copy of the BAS AssociationMatrix is maintained by each CMAS which takes partin management of the plex, so it will be necessary toincrease BASASSOCBLK by a similar amount in allCMASes.

Module: EYU0BMZA


EYUBM0308E • EYUBM0328E

Chapter 4. EYUBMnnnn messages 13

EYUBM0329I The target scope (scope) in [ResourceAssignment | Resource Description](resaorresd) and the related scope (scope)in [Resource Assignment | ResourceDescription] (resaorresd) are the same.

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the target andrelated scopes were the same.

System action: This message is issued with anEYUBM30nE message, which indicates whether an addor update action was attempted. The requested actionis not performed.

User response: Change the target scope or the relatedscope so that they are not the same.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0330I The target scope (scope) in [ResourceAssignment | Resource Description](resaorresd) and the related scope (scope)in Resource Assignment in ResourceDescription for (resassgn,resdesc) are thesame.




Module: EYU0BMSG

Destination: EYULOG

EYUBM0331I The target scope (scope) in ResourceAssignment in Resource Description for(resassgn,resdesc) and the related scope(scope) in [Resource Assignment |Resource Description] (resaorresd) are thesame.



User response: Change the target scope or the related

scope so that they are not the same.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0332I The target scope (scope) in ResourceAssignment in Resource Description for(resassgn,resdesc) and the related scope(scope) in Resource Assignment inResource Description for(resassgn,resdesc)) are the same.




Module: EYU0BMSG

Destination: EYULOG

EYUBM0333I The target system (system) in[Resource Assignment | ResourceDescription] (resaorresd) is contained inthe related scope (scope) in [ResourceAssignment | Resource Description](resaorresd).

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the target systemwas contained in the related scope.


User response: Change either the target system or therelated scope.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0334I The target system (system) in[Resource Assignment | ResourceDescription] (resaorresd) is contained inthe related scope (scope) in ResourceAssignment in Resource Description for(resassgn,resdesc).


EYUBM0329I • EYUBM0334I




Module: EYU0BMSG

Destination: EYULOG

EYUBM0335I The target system (system) in ResourceAssignment in Resource Description for(resassgn,resdesc) is contained in therelated scope (scope) in [ResourceAssignment | Resource Description](resaorresd)).




Module: EYU0BMSG

Destination: EYULOG

EYUBM0336I The target system (system) in ResourceAssignment in Resource Description for(resassgn,resdesc) is contained in therelated scope (scope) in ResourceAssignment in Resource Description for(resassgn,resdesc)).




Module: EYU0BMSG

Destination: EYULOG

EYUBM0337I The related system (system) in[Resource Assignment | ResourceDescription] (resaorresd) is contained inthe target scope (scope) in [ResourceAssignment | Resource Description](resaorresd).

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the related systemwas contained in the target scope.


User response: Either remove the CICS system fromResource Assignment or Resource Description, orchange the target scope.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0338I The related system (system) in[Resource Assignment | ResourceDescription] (resaorresd) is contained inthe target scope (scope) in ResourceAssignment in Resource Description for(resassgn,resdesc).

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the related systemwas contained in the target scope.


User response: Either remove the CICS system fromResource Assignment or Resource Description, orResource Assignment in Resource Description, orchange the target scope.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0339I The related system (system) inResource Assignment in ResourceDescription for (resassgn,resdesc) iscontained in the target scope (scope) in[Resource Assignment | ResourceDescription] (resaorresd)).


System action: This message is issued with anEYUBM30nE message, which indicates whether an add



or update action was attempted. The requested actionis not performed.

User response: Either remove the CICS system fromResource Assignment in Resource Description orResource Assignment or Resource Description, orchange the target scope.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0340I The related system (system) inResource Assignment in ResourceDescription for (resassgn,resdesc) iscontained in the target scope (scope) inResource Assignment in ResourceDescription for (resassgn,resdesc)).



User response: Either remove the CICS system fromResource Assignment in Resource Description, orchange the target scope.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0341I The target scope (scope) in [ResourceAssignment | Resource Description](resaorresd) and the related scope (scope)in [Resource Assignment | ResourceDescription] (resaorresd) contain the samesystem (system).

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the target scope andthe related scope contain the same CICS system.


User response: Remove the duplicated CICS system.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0342I The target scope (scope) in [ResourceAssignment | Resource Description](resaorresd) and the related scope (scope)in Resource Assignment in ResourceDescription for (resassgn,resdesc) contain

the same system (system).




Module: EYU0BMSG

Destination: EYULOG

EYUBM0343I The target scope (scope) in ResourceAssignment in Resource Description for(resassgn,resdesc) and the related scope(scope) in [Resource Assignment |Resource Description] (resaorresd))contain the same system (system).




Module: EYU0BMSG

Destination: EYULOG

EYUBM0344I The target scope (scope) in ResourceAssignment in Resource Description for(resassgn,resdesc) and the related scope(scope) in Resource Assignment inResource Description for(resassgn,resdesc)) contain the samesystem (system).




Module: EYU0BMSG

Destination: EYULOG



EYUBM0345I The related scope scope in [ResourceAssignment | Resource Description](resaorresd) contains multiple systems.

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the related scopecontains multiple systems. Multiple systems are notallowed within a related scope unless the ResourceType is TRANDEF and the USAGE is DYNAM.

System action: This message is issued with anEYUBM30nE message, which indicates whether an addor update action was attempted. The requestedoperation is not performed.

User response: Make sure that the related scope doesnot contain multiple systems.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0346I The related scope scope in ResourceAssignment in Resource Description for(resassgn,resdesc) contains multiplesystems.

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the related scopecontains multiple systems. Multiple systems are notallowed within a related scope unless the ResourceType is TRANDEF and the USAGE is DYNAM.

System action: This message is issued with anEYUBM30nE message, which indicates whether an addor update action was attempted. The requestedoperation is not performed.

User response: Make sure that the related scope doesnot contain multiple systems.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0347I The system system for related scopescope in [Resource Assignment |Resource Description] (resaorresd)) hasno SYSID.

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the system named inthe related scope does not have a defined SYSID. Asystem named in a related scope must have a definedSYSID unless the Resource Type is TRANDEF and theUSAGE is DYNAM.

System action: This message is issued with anEYUBM30n message, which indicates whether an addor update action was attempted. The requestedoperation is not performed.

User response: Make sure that the CICS definition forthe system named in the related scope contains aSYSID.

Module: EYU0BMSG

Destination: EYULOG

EYUBM0348I The system system for related scopescope in Resource Assignment inResource Description for(resassgn,resdesc) has no SYSID.

Explanation: While attempting to add or updateBusiness Application Services administrationdefinitions, it was determined that the system named inthe related scope does not have a defined SYSID. Asystem named in a related scope must have a definedSYSID unless the Resource Type is TRANDEF and theUSAGE is DYNAM.

System action: This message is issued with anEYUBM30n message, which indicates whether an addor update action was attempted. The requestedoperation is not performed.

User response: Make sure that the CICS definition forthe system named in the related scope contains aSYSID.

Module: EYU0BMSG

Destination: EYULOG



Chapter 5. EYUBNnnnn messages

The following variables are commonly used in the EYUBNnnnn messages:

cmdnameOne of the following EXEC CICS commands:CREATE DISCARDINQUIRE

or where cmdname is COMPLETE, the CREATE CONNECTION COMPLETEcommand.

restypeThe name of a resource type. See Managing Business Applications for a completelist of resource types.

resnameThe name of the resource.

versionThe version of the definition record in the CICSPlex SM CMAS DataRepository. A value of N/A indicates that the resource type does not representa definition record (for example, TERMINAL POOL).

respThe RESP= value as returned by CICS.

resp2The RESP2= value as returned by CICS.

resp2loThe RESP2LO= value as returned by CICS.

resp2hiThe RESP2HI= value as returned by CICS.

For descriptions of the RESP, RESP2, RESP2LO, and RESP2HI values for aparticular CICS command, refer to the CICS/ESA System Programming Reference.

Other less common variables are described in the messages in which they appear.

EYUBN0001I CICS release nnn does not supportresource creation

Explanation: During resource installation, it wasdetermined that the specified CICS release does notsupport the EXEC CICS CREATE command.

System action: BAS request processing terminates.


Module: EYU0BNCC

Destination: EYULOG

EYUBN0002I CICS release nnn does not supportrestype resource function

Explanation: During resource installation, it was

determined that the specified CICS release does notsupport the function of the specified resource type,where function is one of the following:

creationThe CICS release does not support EXEC CICSCREATE for the specified resource.

discardingThe CICS release does not support EXEC CICSDISCARD for the specified resource.

This message is issued only once for each differentresource type encountered.

System action: BAS processing for this resource isbypassed and the processing continues with the nextrequest.



Module: EYU0BNCC, EYU0BNC1, EYU0BNDC

Destination: EYULOG

EYUBN0005E cmdname failed for restype resname(version version), RESP=resp,RESP2LO=resp2lo, RESP2HI=resp2hi

Explanation: The specified EXEC CICS commandfailed for the specified resource. See the introduction tothe EYUBNnnnn messages for a description of themessage variables. If the specified resource alreadyexists, refer to the related DFH messages for additionalinformation.

System action: An exception trace record is written tothe CICS trace data set. The recovery action specifiedfor the CICS system is performed. The default action isto continue processing, otherwise, messageEYUBN0008W is issued indicating an alternative action.

User response: Check to see if EYUBN0008W wasissued.

Module: EYU0BNCA, EYU0BNCB, EYU0BNCC,EYU0BNCD, EYU0BNCE, EYU0BNCF, EYU0BNCG,EYU0BNCH, EYU0BNC1, EYU0BNC2, EYU0BNC3,EYU0BNC4, EYU0BNC5, EYU0BNC6, EYU0BNC7,EYU0BNC8, EYU0BNC9

Destination: Console, job log, EYULOG.

EYUBN0006E cmdname failed for restype resname(version version), RESP=resp,RESP2=resp2

Explanation: The specified EXEC CICS commandfailed for the specified resource. See the introduction tothe EYUBNnnnn messages for a description of themessage variables.

System action: An exception trace record is written tothe CICS trace data set. The recovery action for theCICS system is performed. The default action is tocontinue processing, otherwise, message EYUBN0008Wis issued indicating an alternative action.

User response: Check to see if EYUBN0008W wasissued.

Module: EYU0BNCC, EYU0BNC1, EYU0BNC2,EYU0BNC3, EYU0BNC4, EYU0BNC5, EYU0BNC6,EYU0BNDC


EYUBN0007W restype resname (version version), exists<as object name> and is status

Explanation: The specified resource already exists andis not in the appropriate status for resourcereplacement, where:

status Is one of the following:

v not CLOSED

v not DISABLED

v not OUTSERVICE

v not RELEASED

v currently in use

object Is either file, program, or transient data queue.

name Is the actual name of the file, program, ortransient data queue.

Note that since terminals and connections cannot havethe same name, this message may identify a terminalwhen the CREATE is actually for a connection, or itmay identify a connection when the CREATE is for aterminal.

This message is only produced if State Check is set toYes on the resource installation request.

System action: The BAS processing stops and noresources are installed because at least one installedresource is not in the correct state.


Module: EYU0BNCC, EYU0BNC2, EYU0BNC3,EYU0BNC4, EYU0BNC5, EYU0BNC6, EYU0BNDC


EYUBN0008W An error has occurred and the failureaction is to action

Explanation: Indicates the recovery action, as specifiedfor the CICS system, to be taken after an erroroccurred, where:

action Is one of the following:

v terminate the CICS

v prompt the operator

v terminate the CREATE processing

This message accompanies either EYUBN0005E orEYUBN0006E.

System action: The processing continues based on thefailure action. If the action is to prompt the operator,message EYUBN0010E is issued.

User response: If the action is to prompt the operator,respond to message EYUBN0010E.



EYUBN0005E • EYUBN0008W


EYUBN0009W CICS type termination has beenrequested

Explanation: Termination of the target CICS systemhas been scheduled as a result of BAS installationfailures, where:

type Is NORMAL or IMMEDIATE.

System action: The BAS request processing terminatesand the indicated target CICS shutdown is initiated.


Module: EYU0BNCC


EYUBN0010E Please specify failure processingaction - CONTINUE, TERMINATE,NORMAL, or IMMEDIATE

Explanation: A failure has occurred and the recoveryaction for the CICS system is to prompt the operator.

System action: The system waits for an operatorresponse.

User response: Respond to the console message withone of the following:

CONTINUEContinue processing the BAS requests.

TERMINATETerminate processing of the BAS requests.

NORMALInitiate a NORMAL shutdown of the targetCICS.

IMMEDIATEInitiate an IMMEDIATE shutdown of thetarget CICS.



EYUBN0011E Failure processing action action isinvalid

Explanation: The operator response to messageEYUBN0010E is invalid.

System action: Message EYUBN0010E is reissued.

User response: Respond to message EYUBN0010Ewith one of the responses listed in the message.



EYUBN0013W [CONNECTION | SESSION |TERMINAL | TERMINAL POOL]resname (version version) is not availabledue to a COMPLETE failure of[CONNECTION | TERMINAL POOL]resname2 (version version2)

Explanation: The specified resource is not availablebecause processing has failed for another resource. Seethe introduction to the EYUBNnnnn messages for adescription of the other message variables.

System action: The action taken is based on therecovery action specified for the CICS system. Thismessage is accompanied by EYUBN0005E, whichprovides additional information.

User response: Note that the resource was notprocessed successfully and is not available.

Module: EYU0BNC5, EYU0BNC6


EYUBN0014W [CONNECTION | SESSION |TERMINAL | TERMINAL POOL]resname (version version) is not availabledue to a successful DISCARD of[CONNECTION | TERMINAL POOL]resname2 (version version2)

Explanation: The specified resource is not availablebecause processing is incomplete for another resource.See the introduction to the EYUBNnnnn messages for adescription of the other message variables.

System action: This message is accompanied byEYUBN0005E, which provides additional information.




EYUBN0015W [CONNECTION | SESSION |TERMINAL | TERMINAL POOL]resname (version version) is not availabledue to a DISCARD failure of[CONNECTION | TERMINAL POOL]resname2 (version version2)

Explanation: The specified resource is not availablebecause processing has failed for another resource. Seethe introduction to the EYUBNnnnn messages for adescription of the other message variables.

System action: The action taken is based on therecovery action specified for the CICS system. Thismessage is accompanied by EYUBN0005E, whichprovides additional information.


EYUBN0009W • EYUBN0015W

Chapter 5. EYUBNnnnn messages 21



EYUBN0016W [CONNECTION | SESSION |TERMINAL | TERMINAL POOL]resname (version version) is not availabledue to no sessions available for[CONNECTION | TERMINAL POOL]resname2 (version version2)






EYUBN0017W [CONNECTION | SESSION |TERMINAL | TERMINAL POOL]resname (version version) is not availabledue to an undefined or unavailable[CONNECTION | TERMINAL POOL]resname2 (version version2)






EYUBN0018W Installation of the specifiedMQCONN definition failed.

Explanation: Installation of the specified MQCONNdefinition failed because more than one resource cannotbe installed at once.

System action: Installation fails and a message isissued..

User response: Issue the install command again withonly one MQCONN definition specified.

Module: EYU0BNCD

EYUBN0098E Resource creation failed

Explanation: A catastrophic failure occurred. Eitherthe main module encountered a problem or asubordinate module returned a non-normal responsecode.

System action: An exception trace record is written tothe CICS trace data set. BAS request processingterminates. The target CICS remains active.

User response: Collect the following information andcontact your IBM Support Center:

v The target CICS job log.

v The target CICS trace.

v The CICSPlex SM CICS EYULOG.

Module: EYU0BNCC


EYUBN0099I Resource creation processing complete

Explanation: BAS resource creation processing hascompleted.

System action: If resource creation was unsuccessful,this message is accompanied by one or more errormessages describing the failure.

If resource creation was successful, not accompanied byother error messages and no action is necessary.

User response: Refer to those error messages todetermine the appropriate action.

Module: EYU0BNCC


EYUBN0016W • EYUBN0099I


Chapter 6. EYUBUnnnn messages

EYUBUnnnn messages are issued by the EYU9BCSD CSD EXTRACT routine. Theyappear in the EYUOUT ddname.

EYUBU0010W Field value longer than 30 characters- truncated

Explanation: The object being extracted from the CSDhas a description longer than 30 characters. This hasbeen truncated to meet the CICSPlex SM descriptionrequirements.

System action: The DESCRIPTION card written to theEYUOUT data set only contains the first 30 charactersof the DESCRIPTION field supplied by DFHCSDUP.Following the message a comment is written toEYUOUT containing the complete description.DFHCSDUP Extract processing continues.

User response: Before using the EYUOUT as input toBATCHREP, ensure the DESCRIPTION is appropriate.

Module: EYU9BCSD

Destination: EYUOUT

EYUBU0020I Object from IBM supplied groupignored. Group name: groupname Objecttype: objecttype Object name: objectname

Explanation: Objects from groups starting with DFHor EYU are not processed by EYU9BCSD. groupname isthe name of the CSD group containing the object.objecttype is the CSD type of object (for exampleTRANSACTION, FILE, etc). objectname is the name ofthe object that has not been processed.

System action: DFHCSDUP Extract processingcontinues.

User response: CICS and CICSPlex SM supplieddefinitions should be installed via RDO and not BAS. Ifyou need to migrate definitions for sample programs,then copy the necessary resources from the IBMsupplied group to a user group and rerun theDFHCSDUP extract specifying the user group or list.

Module: EYU9BCSD

Destination: EYUOUT

EYUBU0110E Invalid card type - ERROR conditionset

Explanation: An invalid EYUIN control statement hasbeen found.

System action: The DFHCSDUP Extract command isnot processed.

User response: Correct the EYUIN input. The EYUINcontrol statement in error will precede the message. Seethe CICSPlex SM Managing Business Applicationsmanual, Appendix A for details.

Module: EYU9BCSD

Destination: EYUOUT

EYUBU0111E Duplicate card - ERROR condition set

Explanation: An EYUIN control statement has beenfound twice.


User response: Correct the EYUIN input. Theduplicate EYUIN control statement will precede themessage.

Module: EYU9BCSD

Destination: EYUOUT

EYUBU0112E Invalid or missing value - ERRORcondition set

Explanation: An invalid EYUIN control statement hasbeen found.


User response: Correct the EYUIN input. Ensure thatthe syntax of the EYUIN control statement is correct.The invalid EYUIN control statement will precede themessage. See the CICSPlex SM Managing BusinessApplications manual, Appendix A for details.

Module: EYU9BCSD

Destination: EYUOUT

EYUBU0113E Call out of order from DFHCSDUP -ERROR condition set

Explanation: The extract routine EYU9BCSD has beencalled by DFHCSDUP with an unexpected parameter.

System action: The DFHCSDUP Extract processingstops.

User response: Use DFHCSDUP to VERIFY the CSDand resubmit the job. If the problem persists, collect thejoblog and CSD and contact your IBM Support Center.

Module: EYU9BCSD


Destination: EYUOUT

EYUBU0114E Null object name from DFHCSDUP -ERROR condition set

Explanation: The extract routine EYU9BCSD has notbeen passed an object name by DFHCSDUP.



Module: EYU9BCSD

Destination: EYUOUT

EYUBU0115E Null keyword name from DFHCSDUP- ERROR condition set

Explanation: The extract routine EYU9BCSD has notbeen passed an object attribute by DFHCSDUP.



Module: EYU9BCSD

Destination: EYUOUT

EYUBU0116E INQUOTES not YES or NO - ERRORcondition set

Explanation: The INQUOTES EYUIN controlstatement has an invalid value. Valid values are YES orNO.


User response: Correct the EYUIN input and resubmitthe job.

Module: EYU9BCSD

Destination: EYUOUT

EYUBU0117W Non-default value specified.Keyword suppressed.

Explanation: The extract routine EYU9BCSD has beenpassed a keyword, for an attribute which it does notsupport, with a non-default value.

System action: The DFHCSDUP Extract processingcomments out the keyword in EYUOUT and continuesprocessing. A condition code 8 is returned fromDFHCSDUP. The default value for the attribute will beapplied by CICS on installation.

User response: Review the EYUOUT file.

Module: EYU9BCSD

Destination: EYUOUT

EYUBU0114E • EYUBU0117W


Chapter 7. EYUCCnnnn messages

EYUCC0002E Connecting CMAS name reported errorduring action

Explanation: An attempt to notify a connecting CMASof data repository changes has failed, where:

name Identifies the CMAS that reported the error;this could be either the local CMAS, which isthe maintenance point, or the CMAS that wasbeing connected to.

error Is one of the following:

v Method Failure

v Repository Corrupt

action Is the type of change that was being reported,as one of the following:

v Create

v Delete

v Update

System action: This message is followed immediatelyby message EYUCC0003E. A user trace record iswritten to the CICS trace data set.

User response: Depending on the type of error thatwas reported, do one of the following:

v For Method Failure, collect the exception tracerecords and contact your IBM Support Center.

v For Repository Corrupt, check the local CMAS andthe connecting CMAS to see which CICSplexes stillhave pending notification requests, and then retrythe data repository update.

Module: EYU0CCPP


EYUCC0003E Evaluation of Connecting CMAS nameterminated

Explanation: The Evaluate CMAS routine terminatedabnormally because of the error reported in messageEYUCC0002E, where:

name Identifies the CMAS that reported the error;this could be either the local CMAS, which isthe maintenance point, or the CMAS that wasbeing connected to.

System action: The pending notification process isretried automatically the next time the connectingCMAS makes contact with the local CMAS.


Module: EYU0CCPP



Chapter 8. EYUCInnnn messages

EYUCI0001I Communications initialization complete

Explanation: The Communications component hasbeen successfully initialized.

System action: CICSPlex SM initialization continues.


Module: EYU0CIIN

Destination: EYULOG

EYUCI0002I Communications termination complete

Explanation: The Communications component hasbeen terminated.

System action: CICSPlex SM termination continues.


Module: EYU0CITM, EYU1CITM

Destination: EYULOG

EYUCI0003I subcompid initialization has started

Explanation: The specified subcomponent of theCommunications component is being initialized, where:

subcompidIdentifies the subcomponent as one of thefollowing:

v Timing services

v Transport services

v Link set services

v Protocol services

v Connection services

v Access services

System action: Initialization of the subcomponentcontinues.


Module: EYU0CIIN, EYU1CIIN

Destination: EYULOG

EYUCI0004I Data Repository does not contain LinkDefinitions, Communications Groupgrpname is being deleted.

Explanation: During CMAS initialization, the datarepository was scanned for CMAS-to-CMAS linkrecords, but none were found. This either means thatno links have been defined to CICSPlex SM (throughthe CMTCMDEF or CMTPMDEF views), or that the

data repository has been reinitialized since links weredefined.

To ensure that the CICS DFHCSD file coincides withthe data repository, the specified CSD communicationsgroup, which contains the link definitions for theCMAS, is being deleted, where:

grpnameIs the name of the communications group inthe form EYUCxxxx, where xxxx is thefour-character CICS system ID of the CMAS.

System action: CICSPlex SM attempts to delete thecommunications group. This message is followed byanother message that indicates whether the groupcould be deleted: EYUCI0005I indicates the group wasdeleted; EYUCI0006E indicates it was not.


Module: EYU0CSSR


EYUCI0005I Delete of Communications Groupgrpname successful.

Explanation: This message follows messageEYUCI0004I to indicate that the specified CSDcommunications group was successfully deleted, where:


System action: Initialization of the Communicationscomponent continues.


Module: EYU0CSSR

Destination: EYULOG

EYUCI0006E Delete of Communications Groupgrpname failed, reason

Explanation: This message follows messageEYUCI0004I to indicate that the specified CSDcommunications group could not be deleted, where:


reason Identifies the reason for the failure as one ofthe following:


CSD in useThe DFHCSD file was in use byanother user or transaction for morethan two minutes. Deleting a grouprequires update access to theDFHCSD file.

CEDA FailureA nonzero return code was receivedfrom the CEDA interface, which isused to delete a group from theDFHCSD file.

System action: Any CMAS-to-CMAS links defined toCICSPlex SM are not established. In the case of aCEDA failure, message EYUXS0003E is issued withdetails about the failure.

User response: Depending on the reason for thefailure, do one of the following:

v For CSD in use, ensure that the DFHCSD file isavailable to the CMAS being initialized. Then stopand restart the CMAS.

v For CEDA Failure, review the text of messageEYUXS0003E and the CICS Customization Guide todetermine the cause of the CEDA failure. Then stopand restart the CMAS.

Module: EYU0CSSR


EYUCI0007I Install of Communications Groupgrpname started.

Explanation: During initialization of theCommunications component, the definitions in thespecified communications group are being installed. AllCICS definitions for CMAS-to-CMAS links reside in acommunications group in the DFHCSD file, where:


System action: CICSPlex SM attempts to install thegroup. This message is followed by another messagethat indicates whether the group could be installed:EYUCI0008I indicates the group was installed;EYUCI0008E or EYUCI0014W indicates it was not.


Module: EYU0CSSR

Destination: EYULOG

EYUCI0008I Install of Communications Groupgrpname successful.

Explanation: This message follows messageEYUCI0007I to indicate that the specified CSDcommunications group was successfully installed,where:




Module: EYU0CSSR

Destination: EYULOG

EYUCI0009E Install of Communications Groupgrpname failed, reason

Explanation: This message follows messageEYUCI0007I to indicate that the specified CSDcommunications group could not be installed, where:



CSD in useThe DFHCSD file was in use byanother user or transaction for morethan two minutes. Installing a grouprequires update access to theDFHCSD file.

CEDA FailureA nonzero return code was receivedfrom the CEDA interface, which isused to install a group from theDFHCSD file.

System action: Any CMAS-to-CMAS links defined toCICSPlex SM are not established. In the case of aCEDA failure, message EYUXS0003E is issued withdetails about the failure.

User response: Depending on the reason for thefailure, do one of the following:

v For CSD in use, make sure the DFHCSD file isavailable to the CMAS being initialized. Then stopand restart the CMAS.

v For CEDA Failure, review the text of messageEYUXS0003E and the CICS Customization Guide todetermine the cause of the CEDA failure. Then stopand restart the CMAS.

Module: EYU0CSSR


EYUCI0007I • EYUCI0009E


EYUCI0010I Communications link to addspace sysnameis being added to the Connection List.

Explanation: During CMAS initialization, the datarepository is scanned for CMAS-to-CMAS link records.Appropriate CONNECTION, SESSION, and PARTNERresources are dynamically created in the runningCMAS, where:

addspaceIdentifies the type of address space beinglinked to as either a CMAS or a MAS.

sysnameIs the name of the CMAS or MAS being linkedto.

System action: CICSPlex SM attempts to create therequired resources and to update the connection list.This message is followed by another message thatindicates whether or not the list could be updated.EYUCI0011I indicates that the list was updated;EYUCI0012E indicates that it was not.


Module: EYU0CSSR

Destination: EYULOG

EYUCI0011I Communications link to addspace sysnamesuccessful.

Explanation: This message follows messageEYUCI0010I to indicate that a link to the specified CICSsystem was successfully defined and installed, where:

addspaceIdentifies the type of address space that waslinked to as either a CMAS or a MAS.

sysnameIs the name of the CMAS or MAS that waslinked to.



Module: EYU0CSSR

Destination: EYULOG

EYUCI0012E Communications link to addspace sysnamefailed, reason

Explanation: This message follows messageEYUCI0010I to indicate that a link to the specified CICSsystem could not be defined and installed, where:

addspaceIdentifies the type of address space as either aCMAS or a MAS.

sysnameIs the name of the CMAS or MAS.


CSD in useThe DFHCSD file was in use byanother user or transaction for morethan two minutes. Updating a grouprequires update access to theDFHCSD file.

SYSID used in another linkThis CMAS already has a connectionto a CMAS or MAS with the samenam

APPLID used in another linkThis CMAS already has a connectionto a CMAS or MAS with the samez/OS Communications ServerAPPLID.

CREATE FailureAn abnormal response was receivedwhile dynamically creating resources.

System action: The impact on system processingdepends on the reason for the failure:

CSD in useThe definition is not processed.

SYSID used in another linkThe definition is not processed.

APPLID used in another linkThe definition is not processed.

CREATE FailureIf creation of CONNECTION or SESSIONdefinitions failed, the incomplete set will bediscarded.If creation of related PARTNERdefinitions failed, the connection is NOTdiscarded.

User response:

v For CSD in use, make sure the DFHCSD file isavailable to the CMAS being initialized. Thenattempt to define the link again.

v For SYSID used in another link, remove and recreatethe CMTCMDEF or CMTPMDEF, insuring that theSYSID of the remote CMAS is not already in use.

v For APPLID used in another link, remove andrecreate the CMTCMDEF or CMTPMDEF, insuringthat the APPLID of the remote CMAS is not alreadyin use.

v For CREATE Failure, examine the exception tracerecords to determine the cause of the problem.Correct any errors and restart the CMAS with asystem initialization parameter of START=COLD.

Module: EYU0CSSR



Chapter 8. EYUCInnnn messages 29

EYUCI0013I Install of Communications Groupgrpname is bypassed, CICS was notstarted COLD.

Explanation: The CMAS that is being initialized wasnot started with a system initialization table (systeminitialization table) parameter of START=COLD. Thelink definitions in the specified communications groupare not installed; CICS restores all link definitions fromthe DFHRSD file. Any recent changes or additions tothe CICSPlex SM CMAS-to-CMAS link definitions(made using the CMTCMDEF or CMTPMDEF views)are not available to the CMAS, where:


System action: The CMAS uses whatever linkdefinitions existed in the DFHRSD file at the time of itslast shutdown. If either the CICSPlex SM datarepository or the DFHCSD file was restored frombackup or reinitialized since the last CMAS execution,the link definitions may not be up to date.

User response: To make use of the latest linkdefinitions, stop the CMAS and then restart it with asystem initialization table parameter of START=COLD.

Module: EYU0CSSR

Destination: EYULOG

EYUCI0014W Install of Communications Groupgrpname failed, Group not in DFHCSD.

Explanation: This message follows messageEYUCI0007I to indicate that the specifiedcommunications group could not be installed because itcould not be found in the DFHCSD file. This problemcould occur for one of two reasons:

v The DFHCSD file was either restored from backup orreinitialized.

v No communication links have been defined toCICSPlex SM through the CMTCMDEF orCMTPMDEF views.

Where:


System action: If the DFHCSD file was restored frombackup or reinitialized, this message is followed by oneor more EYUCI0010I messages as CICSPlex SMattempts to synchronize the file with its data repository.

Otherwise, no CMAS-to-CMAS connections areestablished.


Module: EYU0CSSR


EYUCI0015W Transaction COIR not available

Explanation: During initialization of theCommunications component, an error has beendetected while trying to set the priority of theCICSPlex SM supplied transaction COIR.

System action: MAS initialization continues. However,evaluation definitions (EVALDEFs) that run in thisMAS operate as if the CICSPlex SM system parameterCOIRTASKPRI=0 is set. This means the MASlong-running task COIE is used for all EVALDEFs, evenif the Separate Task field is set to Yes.

User response: Check that transaction COIR isinstalled in the MAS. Once COIR has been installed,the MAS agent will need to be restarted to pick up thechange.

Module: EYU0CIIN

Destination: Console, job log

EYUCI0016W Transaction COHT not available

Explanation: During initialization of theCommunications component, an error has beendetected while trying to set the priority oftheCICSPlex SM supplied transaction COHT.

System action: MAS initialization continues. However,it will not be possible to obtain data for completedtasks (HTASK resource table) because the MAS COHTtransaction is not available.

User response: Check that transaction COHT isinstalled in the MAS. Once COHT has been installed,the MAS agent will need to be restarted to pick up thechange.

Module: EYU0CIIN


EYUCI0101E Communications initialization failed

Explanation: One or more subcomponents of theCommunications component could not be initialized.

System action: CICSPlex SM initialization terminatesabnormally. A user trace record is written to the CICStrace data set.

User response: Examine the exception trace records,and any messages issued before this one, to determinethe cause of the problem.

Module: EYU0CIIN




EYUCI0102W Communications termination failed

Explanation: One or more subcomponents of theCommunications component could not be properlyterminated. Some resources may remain allocated.

System action: CICSPlex SM termination continues. Auser trace record is written to the CICS trace data set.

User response: Examine the exception trace recordsand, any messages issued before this one, to determinethe cause of the problem.

Module: EYU0CITM


EYUCI0102W

Chapter 8. EYUCInnnn messages 31

Chapter 9. EYUCLnnnn messages

The following variables are used in EYUCLnnnn messages:

protocolIdentifies the communications protocol being used as one of the following:

CPI-C Common Programming Interface Communications

LU6.2 CICS intersystem communication

MRO CICS/ESA Multiregion Operation

ESSS CICSPlex SM Environment Services System Services

taskIdentifies a specific communications task. One or more of the following tasksare initiated, depending on the communications node involved and the type ofprotocol in use:

Receive Link ManagerInitiated within a CMAS network node to manage a set of MAS CPI-Cendpoint connections.

Receive Link TaskInitiated within a MAS endnode to form a controlled endpointconnection.

Send Link ManagerInitiated within a CMAS network node to manage CPI-C and MROlogical connections.

Independent Receive TaskInitiated within a CMAS network node to manage a single networkconnection.

nodenameIdentifies a communications node by its CMAS or MAS name.

EYUCL0001I Protocol Services initialization complete

Explanation: The protocol services subcomponent ofthe Communications component has been successfullyinitialized.

System action: The Communications componentcontinues to initialize its other subcomponents.


Module: EYU0CLIN, EYU1CLIN

Destination: EYULOG

EYUCL0002I protocol Initial Contact Transientinitiated

Explanation: The Initial Contact Transient for thespecified protocol has been started where protocol is asdescribed in the introduction to the EYUCLnnnnmessages. The necessary data structures are built in

preparation for initial contact from the First SpeakerNode.

System action: Initialization of the protocol servicessubcomponent continues.


Module: EYU0CLET, EYU0CLCT, EYU0CLMT,EYU0CLRT, EYU0CLST

Destination: EYULOG

EYUCL0003I protocol task initiated

Explanation: The specified protocol has successfullyinitiated a required task where protocol and task are asdescribed in the introduction to the EYUCLnnnnmessages.

System action: Initialization of the protocol servicessubcomponent continues.



Module: EYU0CLER, EYU0CLEV, EYU0CLCS,EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS,EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST,EYU0CLSV, EYU0CLSW

Destination: EYULOG

EYUCL0004I protocol Initial Contact Transientterminated

Explanation: The Initial Contact Transient (ICT) forthe specified protocol has been terminated whereprotocol is as described in the introduction to theEYUCLnnnn messages. Other nodes may no longerestablish contact with the current node. All previouslycreated data structures are destroyed.

System action: Termination of the protocol servicessubcomponent continues.


Module: EYU0CLET, EYU0CLCT, EYU0CLMT,EYU0CLRT, EYU0CLST

Destination: EYULOG

EYUCL0005I protocol task terminated

Explanation: A required task for the specified protocolhas been terminated where protocol and task are asdescribed in the introduction to the EYUCLnnnnmessages.

System action: Termination of the protocol servicessubcomponent continues.



Destination: EYULOG

EYUCL0006I protocol link to nodename established

Explanation: A link between the current node and thespecified node has been established using the specifiedprotocol where protocol and nodename are as describedin the introduction to the EYUCLnnnn messages.

System action: This communications link is availablefor data transmission between the specified nodes.


Module: EYU0CLER, EYU0CLEV, EYU0CLRT

Destination: EYULOG

EYUCL0007I protocol link to nodename terminated

Explanation: The link between the current node andthe specified node, using the specified protocol, hasbeen terminated where protocol and nodename are asdescribed in Chapter 9, “EYUCLnnnn messages,” onpage 33.

System action: This communications link is no longeravailable for data transmission between the specifiednodes.


Module: EYU0CLER, EYU0CLEV

Destination: EYULOG

EYUCL0008I ESSS ICT entered for Attach to nodename

Explanation: The ESSS ICT was entered for a localMAS request to establish a communications link to thespecified node where nodename is as described in theintroduction to the EYUCLnnnn messages.

System action: The ICT Attach request is processed.


Module: EYU0CLET

Destination: EYULOG

EYUCL0009I ESSS ICT entered for Detach fromnodename

Explanation: The ESSS ICT was entered for a localMAS request to terminate the communications linkbetween the current node and the specified node wherenodename is as described in the introduction to theEYUCLnnnn messages.

System action: The ICT Detach request is processed.


Module: EYU0CLET

Destination: EYULOG

EYUCL0010I Protocol Services termination complete

Explanation: The protocol services subcomponent ofthe Communications component has been terminated.

System action: Termination of the Communicationscomponent continues. Because protocol services is notactive, data can no longer be transmitted betweenCICSPlex SM address spaces.


Module: EYU0CLTM

Destination: EYULOG

EYUCL0004I • EYUCL0010I


EYUCL0012I Connection of nodename to nodenamecomplete.

Explanation: The process of connecting the specifiednodes is complete where nodename is as described inthe introduction to the EYUCLnnnn messages.

System action: The status of this connection is set toactive. The specified nodes and their connection cannow be managed using the end-user interface.


Module: EYU0CLCS, EYU0CLMS, EYU1CLRW


EYUCL0013I Link Buffer Pool element shortagerelieved

Explanation: A link buffer shortage that was detectedby the protocol services subcomponent has beensuccessfully relieved. A new pool of link buffers hasbeen acquired.

System action: Protocol services processing continues.


Module: EYU0CLBL, EYU0CLBE

Destination: EYULOG

EYUCL0015I task initiated for protocol connection withtype nodename

Explanation: In an attempt to establish a link betweenthe current node and the specified node, a receive taskusing the specified protocol has been started wheretask, protocol, and nodename are as described in theintroduction to the EYUCLnnnn messages, and where:

type Identifies the node being connected to as aCMAS.

System action: Connection Services continuesinitializing the link to the specified node.


Module: EYU0CLCS, EYU0CLCT, EYU0CLMS,EYU0CLMT, EYU0CLRR, EYU0CLRS, EYU0CLRV,EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV,EYU0CLSW, EYU1CLRV, EYU1CLRW

Destination: EYULOG

EYUCL0016I task terminated for protocol connectionwith type nodename

Explanation: The link between the current node andthe specified node, using the specified protocol, isbeing terminated normally where task, protocol, andnodename are as described in the introduction to theEYUCLnnnn messages, and where:

type Identifies the node to which the link is beingterminated as a CMAS.

System action: The task for this link is terminated.Protocol services is notified that the link is no longeravailable.


Module: EYU0CLCS, EYU0CLCV, EYU0CLMS,EYU0CLMV, EYU0CLRR, EYU0CLRS, EYU0CLRV,EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV,EYU0CLSW, EYU1CLRV, EYU1CLRW


EYUCL0017I Send Link Manager initiated forNetView

Explanation: The Send Link Manager task, whichmanages the sending of generic alerts from a CMAS toNetView®, was successfully initiated. This task can beinitiated as part of CMAS initialization or as a result ofa user request to activate the NetView interface in arunning CMAS.

System action: NetView interface processingcontinues.


Module: EYU0CLNW

Destination: EYULOG

EYUCL0018I Send Link Manager terminated forNetView

Explanation: The Send Link Manager task wassuccessfully terminated. This task can be terminated aspart of CMAS termination or as a result of a userrequest to deactivate the NetView interface in arunning CMAS.

System action: The NetView interface is no longeravailable.


Module: EYU0CLNW

Destination: EYULOG

EYUCL0022I Communications buffer long-runningtask termination complete.

Explanation: The communications buffer long runningtask (LRT) has been termianted.

System action: If the LRT was terminated as the resultof a normal shutdown, the CICSPlex SM shutdowncontinues.

If the LRT terminated because of an abnormalcondition, a message preceding this one describes thecondition that caused the termination. CICSPlex SMmay continue running without the services of the LRT.

EYUCL0012I • EYUCL0022I

Chapter 9. EYUCLnnnn messages 35

User response: If a normal CICSPlex SM shutdown isin progress, no action is required.

If the LRT terminated because of an abnormalcondition (as indicated by message EYUCL0121Epreceding this message), CICSPlex SM should be shutdown and restarted.

Module: EYU0CSGT

Destination: EYULOG

EYUCL0023W The MVS image is running inworkload management goal mode butthe CMAS is not defined to the serviceclass, SYSSTC.

Explanation: The MVS image is running in workloadmanagement goal mode but the CMAS is not definedto the MVS service class, SYSSTC. For goal mode theCMASs should not be run as servers, but should bedefined to SYSSTC as exempt from server transactionresponse time management. Started tasks in SYSSTCare assigned a high dispatching priority.

System action: The CMAS issues this warningmessage and continues processing. However, CICSPlexSM may experience severe performance problems.

User response: It is important that the CMAS have theability to process data with a higher priority than theMAS it manages. Therefore, when the MVS image isrunning in workload management goal mode, theCMAS should be defined to the MVS service class,SYSSTC. See the CICS Transaction Server for z/OSInstallation Guide.

Module: EYU0CLET


EYUCL0024W The MVS image is running inworkload management compatibilitymode and the dispatching priority(X'nn') of the connecting MAS(nodename) is higher than thedispatching priority (X'nn') of theCMAS.

Explanation: When the MVS image is running inworkload management compatibility mode, thedispatching priority of the CMAS should be greaterthan or equal to the dispatching priority of theconnecting MAS to ensure optimal performance.

nn is the hexadecimal dispatching priority.

System action: The CMAS issues this warningmessage and continues processing. However, CICSPlexSM may experience severe performance problems.

User response: It is important that the CMAS have theability to process data with a higher priority than theMAS it manages. Therefore, when the MVS image isrunning in workload management compatibility mode,

the CMAS's dispatching priority should be greater thanor equal to the dispatching priority of the connectingMAS. See the Preparing to start a CMASCICSTransaction Server for z/OS Installation Guide.

Note: The minimum required level of operating systemfor CICS Transaction Server for z/OS, Version 2 Release3 is z/OS Version 1 Release 4. Beginning with z/OS V1R3 WLM compatibility mode is no longer available.Therefore, this message will not be issued in CICSTransaction Server for z/OS Version 2 Release 3. Themessage remains in the documentation for referencepurposes.

Module: EYUOCLET


EYUCL0101E Protocol Services initialization failed

Explanation: The protocol services subcomponent ofthe Communications component could not beinitialized.

System action: The impact on system processingdepends on what type of address space was beinginitialized:

CMAS The CMAS is terminated. CICSPlex SM takesan SVC dump with a dump code ofEYUXL001.

MAS The MAS is terminated. CICSPlex SM takes atransaction dump with a dump code of EYUIand returns control to CICS.


Module: EYU0CLIN, EYU1CLIN


EYUCL0102E protocol Initial Contact Transientinitiation failed

Explanation: An attempt to initialize the InitialContact Transient (ICT) for the specified protocol in theCMAS has failed where protocol is as described in theintroduction to the EYUCLnnnn messages.

System action: Communications initialization failscausing the CMAS to terminate. CICSPlex SM takes anSVC dump with a dump code of EYUXL001.

User response: Verify that the appropriate ICTtransaction ID is defined for program EYU9XLOP.Examine the trace records generated by EYU0CLINand, if the ICT transaction ID was not found, usekernel linkage to determine the cause of the problem.

Module: EYU0CLIN


EYUCL0023W • EYUCL0102E


EYUCL0103E protocol task initiation failed

Explanation: An attempt to initiate a required task forthe specified protocol has failed where protocol and taskare as described in the introduction to the EYUCLnnnnmessages.

System action: If the task was started from the InitialContact Transient (ICT), the ICT terminates, whichprevents links from being established with the currentnode.

If the task was started from protocol servicesinitialization, the impact on system processing dependson what type of address space was being initialized:



User response: Verify that the appropriate transactionID is defined for program EYU9XLOP. Examine thetrace records generated by any of the issuing modulesto determine the cause of the problem.

Module: EYU0CLET, EYU0CLIN, EYU0CLCT,EYU0CLMT, EYU0CLRT, EYU0CLST


EYUCL0104E protocol Initial Contact Transientterminated abnormally

Explanation: The Initial Contact Transient (ICT) forthe specified protocol terminated abnormally due to anerror condition where protocol is as described in theintroduction to the EYUCLnnnn messages.

System action: The ICT task terminates, whichprevents nodes using the named protocol fromestablishing communications links.


Module: EYU0CLET


EYUCL0104E protocol Initial Contact Transientterminated abnormally

Explanation: The Initial Contact Transient (ICT) forthe specified protocol terminated abnormally due to anerror condition where protocol is as described in theintroduction to the EYUCLnnnn messages.

System action: The ICT task terminates, whichprevents nodes using the named protocol fromestablishing communications links.


Module: EYU0CLET


EYUCL0106E protocol link to nodename terminatedabnormally

Explanation: A link between the current node and thespecified node has terminated due to an error conditionwhere protocol and nodename are as described in theintroduction to the EYUCLnnnn messages.

System action: The link conversation state is set toinactive, which prevents SENDs or RECEIVEs betweenthe two nodes.




EYUCL0107E protocol ICT attach to nodename failed,reason

Explanation: The Initial Contact Transient (ICT) Attachrequest made by the MAS to establish acommunications link has failed where protocol andnodename are as described in the introduction to theEYUCLnnnn messages, and where reason indicates thecause of the failure.

System action: The ICT Attach request is denied.Initialization of the local MAS terminates. A user tracerecord is written to the CICS trace data set.

User response: Response depends on the reason givenfor the failure as follows:MAS already exists

No action is required. However, some invalidrecords may remain in the data repository. Ifyou want to clean up the data repository, youshould stop and restart the CMAS to whichthe MAS was trying to connect.

MAS name is invalidCheck the MAS startup job to make sure theCICS system and CICSplex names are correctlyspecified. If the MAS startup job is correct,then use the CICSSYS and CMASPLEX viewsto make sure the CICS system and CICSplexhave been defined to the data repository.

query parametersCollect the exception trace records and contactyour IBM Support Center.

EYUCL0103E • EYUCL0107E


Link Conversation Block shortagesCollect the exception trace records and CMASor MAS job logs and contact your IBMSupport Center.

add capability failedCollect the exception trace records, CMAS andMAS job logs and contact your IBM SupportCenter.

check capability failedCollect the exception trace records, CMAS andMAS job logs and contact your IBM SupportCenter.

CICS release not supportedUpgrade the MAS to a supported version ofCICS.

Module: EYU0CLET, EYU0CLRT, EYU0CLST


EYUCL0108E ESSS ICT detach from nodename failed

Explanation: The Initial Contact Transient (ICT)Detach request made by the local MAS to terminate anESSS communications link has failed where nodename isas described in the introduction to the EYUCLnnnnmessages.

System action: The ICT Detach request is denied.

User response: Examine the exception trace recordsissued by EYU0CLET and any messages issued beforethis one, to determine the cause of the problem.

Module: EYU0CLET


EYUCL0110E ESSS ICT link activation for nodenamefailed

Explanation: An Environment Services SystemServices (ESSS) Initial Contact Transient (ICT) toestablish a link between the current CICSPlex SMaddress space (CMAS) and the specified nodename hasfailed where nodename is as described in theintroduction to the EYUCLnnnn messages.

System action: Initialization of the MAS terminates.

User response: Make sure the name of the MAS usedin the startup JCL is one that is in the CMAS datarepository. Examine the user trace records in the CICStrace data set to determine the cause of the problem.

Module: EYU0CLET


EYUCL0110E ESSS ICT link activation for nodenamefailed

Explanation: An Environment Services SystemServices (ESSS) Initial Contact Transient (ICT) toestablish a link between the current CICSPlex SM

address space (CMAS) and the specified nodename hasfailed where nodename is as described in theintroduction to the EYUCLnnnn messages.

System action: Initialization of the MAS terminates.

User response: Make sure the name of the MAS usedin the startup JCL is one that is in the CMAS datarepository. Examine the user trace records in the CICStrace data set to determine the cause of the problem.

Module: EYU0CLET


EYUCL0111E Link Buffer Pool element shortage couldnot be relieved

Explanation: A link buffer shortage detected by theprotocol services subcomponent could not be relieved.There was not enough virtual storage available toacquire a new pool of link buffers.

System action: The Communications componentterminates.

User response: Make more virtual storage availableand then restart CICSPlex SM.

Module: EYU0CLBL


EYUCL0112E Protocol Services initialization unable toaction

Explanation: During initialization of a CMAS or MAS,the protocol services subcomponent was unable tocomplete the specified action, where action identifiesthe action that could not be completed as one of thefollowing:

acquire storageAn attempt to acquire CICS/ESA storage wasunsuccessful.

query parametersAn attempt to query the Parameter Servicessubcomponent was unsuccessful.

post ICT ECBAn attempt to post the CMAS Initial ContactTransient (ICT) event control block (ECB) wasunsuccessful.

wait on ICT ECBAn attempt to wait on the MAS ECB for ICTprocessing to finish was unsuccessful.

perform ICT AttachAn attempt to connect the MAS to the CMASusing the Environment Services SystemServices (ESSS) ICT was unsuccessful.

obtain Initial Contact ElementAn attempt to connect the MAS to the CMASusing the Environment Services System



Services (ESSS) was unsuccessful due to anInitial Contact Element (EICE) shortage.

System action: Initialization of the CMAS or MASterminates.


Module: EYU0CLIN


EYUCL0113E task terminated abnormally for protocolconnection with type nodename

Explanation: An abnormal condition caused the linkbetween the current node and the specified node to beterminated where task, protocol, and nodename are asdescribed in the introduction to the EYUCLnnnnmessages, and where:

type Identifies the node to which the link wasterminated as a CMAS.

System action: Protocol services is notified that thelink is no longer available. A user trace record iswritten to the CICS trace data set.

User response: If the specified node terminatedabnormally, this message is to be expected. Determinewhy the node terminated and then reestablish thecommunication link, if possible.

If the node appears to be active and available, collectthe exception trace records, and any messages issuedbefore this one, and contact your IBM Support Center.

Module: EYU0CLCS, EYU0CLCV, EYU0CLMS,EYU0CLMV, EYU0CLRR, EYU0CLRS, EYU0CLRV,EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV,EYU0CLSW.


EYUCL0114E Send Link Manager initiation failed forNetView

Explanation: The Send Link Manager task, whichmanages the sending of generic alerts from a CMAS toNetView, could not be initiated.

System action: The NetView interface is not available.A user trace record is written to the CICS trace data set.

User response: Collect the exception trace records andcontact your IBM Support Center.

Module: EYU0CLNW


EYUCL0115E Send Link Manager abnormallyterminated for NetView

Explanation: An abnormal condition caused the SendLink Manager task to terminate.

System action: The NetView interface is no longeravailable. A user trace record is written to the CICStrace data set.


Module: EYU0CLNW


EYUCL0117E Insufficient ECDSA storage to expandlink buffer pool

Explanation: There is not enough ECDSA storageavailable to successfully expand the link buffer pool tomeet a use request.

System action: CICSPlex SM terminates theCMAS-to-CMAS connection.

User response: Identify and fix the cause of theshort-on-storage condition or allocate a larger ECDSAstorage area. When the storage constraint is relieved,CICSPlex SM attempts to restore communications.

Module: EYU0CLBL


EYUCL0118E Inconsistent CMAS-CMAS definition.Expected cmastype idtype id1, foundcmastype idtype id2

Explanation: While two CMASs were attempting toconnect to each other, one of the CMASs determinedthat their connection definitions are inconsistent, where:

cmastypeIdentifies the CMAS that has the inconsistencyas either the TARGET or SOURCE of theconnection attempt. Either CMAS in theconnection attempt can identify and report aninconsistency.

idtype Indicates whether the inconsistency was in theCICS system ID (SYSID) or the CMAS name(CMAS).

id1 Is the system ID or CMAS name that wasexpected.

id2 Is the system ID or CMAS name that wasfound.

System action: The attempt to connect the twoCMASs fails. No communication is possible betweenthe CMASs.

User response: Use the CMTCMDEF view to correct



the inconsistencies in the definitions of the specifiedCMASs.

Module: EYU0CLCT


EYUCL0119E A failure occurred while attempting toconnect to CMAS cmasname

Explanation: While attempting to activate aCICSPlex SM connection between this CMAS andanother CMAS, a failure has occured, where:

cmasnameIs the name of the other CMAS.

System action: The connection is not completed.

User response: Collect all job output and AUXTRACEdata sets from both CMASs. After a timeout period inthe other CMAS, the connection attempt shouldautomatically be retried. If the problem persists, contactyour IBM Support Center.

Module: EYU0CLCT, EYU0CLMT


EYUCL0120E Unable to start Communications bufferlong-running task

Explanation: The protocol services subcomponent ofthe communications component was not able to startthe communications buffer long running task (LRT) fora CICSPlex SM address space (CMAS).

System action: CICSPlex SM terminates abnormally. Auser trace record is written to the CICS trace data set.

User response: Examine the CICS CSD to verify thattransaction LSGT and program EYU9XLOP are defined.If the definitions are correct, collect the exception tracerecords and the job log and contact your IBM supportcenter.

Module: EYU0CLIN


EYUCL0121E Communications buffer long-runningtask terminating due to nonrecoverableerror

Explanation: The communications buffer long runningtask (LRT) encountered an error from which it couldnot recover.

System action: The LRT terminates. CICSPlex SMmay continue running without the services of the LRT.

User response: Examine any messages issued beforethis one to determine the cause of the problem. Collectany exception trace records, the job log, and CICS orMVS/ESA dump output, if available, and contact yourIBM support center.

Module: EYU0CSGT


EYUCL0122E MAS communications buffer shortagehas been detected

Explanation: A shortage of MAS communicationbuffers has been detected by a CMAS or one of its localMASes. This message is issued the first time a shortageoccurs during the execution of the CMAS.

System action: The CMAS or MAS will issue thismessage, request an SVCdump, and then issue anexception trace. Execution of the CMAS or MAS thencontinues.

User response: Collect the CICS auxtrace data sets, theSVC dump, and the job output from the CMAS orMAS. If the requesting system is a MAS, also collect theCICS auxtrace data sets and job output from the CMASto which the MAS connects. Contact your IBM SupportCenter with the documentation collected.

Module: EYU0CTBT


EYUCL0124E A failure occurred while attempting toconnect to CMAS cmasname

Explanation: While attempting to activate aCICSPlex SM connection between this LMAS and aCMAS, a failure has occured, where:

cmasnameIs the name of the CMAS.

System action: The connection is not completed.

User response: Refer to the job output of the CMASfor messages that provide more details of the failure.

Module: EYU0CLIN


EYUCL0125E ESSS ICT encountered an error duringCMAS termination

Explanation: During CMAS termination, EYU0CLETencountered an error while attempting to disconnectactive local MASes.

System action: A dump is requested, this message isissued, and CMAS termination continues. The title ofthe dump will be similar to the following:

EYU0XZSD Dump,cmasjobn,cmasname,lpar,CMAS,LEEI,tasknum,TRAC,EYU0CLET,mm/dd/yy,hh:mm:ss

User response: Collect the dump, the auxtrace datasets, and the complete job output from the CMAS andcontact your IBM support center.

Module: EYU0CLET




EYUCL0126E ESSS ICT attach to name failed, MAS isalready connected to CMAS (cmasname).

Explanation: A MAS attempted to connect to a CMAS,but it is already connected to another CMAS, wherecmasname is the name of the CMAS the MAS is alreadyconnected to. Both the MAS and the CMAS it isattempting to connect to will issue this message, butthe variable, name, will have different meanings:

v When this message is issued by the CMAS, name isthe name of the MAS.

v When this message is issued by the MAS, name is thename of the CMAS that the MAS is attempting toconnect to.

System action:

After issuing the message, the CMAS will continuenormal processing, while the MAS will process asfollows:

v Issue new prompt message EYUCL0127A.

v Issue a delay for five seconds.

v Retry the connect to the CMAS until the attachcompletes successfully or until the MAS agent isterminated.

User response:

While it is possible that the EYUCL0126E error is valid,and that a duplicate MAS was started, or a MAS wasstarted with an incorrect NAME EYUPARM, it is alsopossible that because of the asynchronous nature ofCMAS-MAS connect and disconnect processing, theCMAS might still be in the process of disconnecting aprevious connection of the MAS when it receives, andfails, a subsequent connection of the MAS.

v If the connect request is valid then no action isrequired.

v If the connect request is not valid, then one of thefollowing actions can be performed to terminate theMAS agent and stop the connect retry processing:

– Reply to prompt message EYUCL0127A.

– Issue the COSH transaction.

– Use the CEMT transaction to terminate the region.

– Cancel the region.

Note: If the MASPLTWAIT(YES) EYUPARM is in affectfor the MAS, then the region will not be able torespond to COSH or CEMT requests.

Module: EYU0CLET


EYUCL0127A ESSS ICT attach will be retried. Reply“T” to terminate the MAS agent.

Explanation: The MAS connect will be retried untilthe attach completes successfully or until the MASagent is terminated. This message is preceded bymessage EYUCL0126E.

System action: After issuing this message, the MASwill delay and then retry the connection process.

User response: Reply “T” to stop the connection retryprocess and terminate the MAS agent. Please refer tomessage EYUCL0126E for more information about useractions for this message.

Module: EYU0CLIN


EYUCL0128E The reply to EYUCL0127A was invalid.The prompt will be re-issued.

Explanation: An invalid reply was given for messageEYUCL0127A.

System action: After issuing this message,EYUCL0127A is re-issued

User response: See user action for EYUCL0127A.

Module: EYU0CLIN


EYUCL0130E Capability of MAS nodename is notlower or equal.

Explanation: A request by MAS nodename to establisha communications link has failed because MASnodename is running at a later version than the CMASwhere:

nodenameis the MAS name of a communications node.

The capability of a CMAS or MAS is determined by itsservice level or CICSPlex SM release and version.

This message might be followed by messageEYUCL0131E which can give more information.

System action: The request to establish acommunications link is denied. Initialization of theMAS terminates.

User response: Correct the startup JCL for MASnodename so that its service level or CICSPlex SMrelease and version is not later than that of the CMASthat issued this message.



EYUCL0131E Resource type mismatch n with MASnodename is objname

Explanation: MAS nodename has a version of resourcetable objname that does not match the version in use bythis CMAS where:




|

|||

|

|

|

|

|||

|

|

|||

|

||||||||

||

|||

|

|

|

|

|||

||

||||

||

||||

|

|

|||

||

||

|

|

|

objnameis the name of a resource table in use by MASnodename which is at an earlier or later releasethan that in use by this CMAS.

n is the number of mismatches detected.

This message can be issued for up to two resource tabletypes.

System action: See message EYUCL0130E for moreinformation.

User response: See message EYUCL0130E for moreinformation.



EYUCL0201I Link Buffer Pool element shortagedetected

Explanation: The protocol services subcomponent hasdetermined that there are no link buffers left in the linkbuffer pool.

System action: CICSPlex SM attempts to acquire anew pool of link buffers. This message is followed byanother message that indicates whether the shortagecould be relieved: EYUCL0013I indicates the shortagewas relieved; EYUCL0111E indicates it was not.


Module: EYU0CLBL, EYU0CLBE

Destination: EYULOG

EYUCL0201I


Chapter 10. EYUCPnnnn messages

EYUCP0001E Duplicate Maintenance Points forCICSplex plexname, MPs on cmasid1 andcmasid2.

Explanation: In attempting to connect the specifiedCMASs to each other, CICSPlex SM determined thatboth CMASs were considered the maintenance pointfor the specified CICSplex. This occurs when the sameCICSplex is manually created under two differentCMASs. The CMAS under which a CICSplex is createdbecomes its maintenance point, and each CICSplex canhave only one.

System action: The communications link between thetwo CMASs is terminated.

User response: If you want the CMASs tocommunicate with each other, the CICSplex must bedefined to only one of them. Use the CPLEXDEF viewto remove the CICSplex definition from one of theCMASs and then restart that CMAS.

Module: EYU0CPSI


EYUCP0002E NetTop Import Failure for ConnectingCMAS cmasid, Failure occurred inmethod.

Explanation: The Connection Services subcomponentwas not able to import network topology informationabout the specified CMAS, where:

method Identifies the Connection Services method thatfailed.

System action: The network topology import processterminates.

User response: Stop and restart the CMAS where thefailure occurred, as indicated by the APPLID stampthat precedes the message.

Module: EYU0CPTI


EYUCP0003E Duplicate MAS masid, in CICSplexplexname, systems on cmasid1 andcmasid2. MASs being shut down.

Explanation: In attempting to connect the specifiedCMASs to each other, CICSPlex SM determined that aMAS of the same name was active for each CMAS. Thenames of CICS systems to be managed byCICSPlex SM must be unique within a CICSplex.Because both CMASs are participating in themanagement of the specified CICSplex, duplicate MASnames are not allowed.

System action: The duplicate MASs are terminated.The CICS systems continue to run normally, but theyare not known to CICSPlex SM. The connectionbetween the CMASs is completed.

User response: Change one of the MAS names in theappropriate CICS system startup JCL. Then stop andrestart both CICS systems.

Module: EYU0CPMI


EYUCP0004I Connection Services long-running taskinitialization has started

Explanation: The Connection Services long runningtask (LRT) is being initialized.

System action: Initialization of the LRT continues.

User response: None

Module: EYU0CPLT

Destination: EYULOG

EYUCP0005I Connection Services long-running taskinitialization complete

Explanation: The Connection Services long runningtask (LRT) has been successfully initialized.

System action: The initialization of ConnectionServices subcomponent.

User response: None

Module: EYU0CPLT

Destination: EYULOG

EYUCP0006I Connection Services long-running tasktermination has started

Explanation: The Connection Services long runningtask (LRT) is being terminated.

System action: Termination of the LRT continues.

User response: None

Module: EYU0CPLT

Destination: EYULOG

EYUCP0007I Connection Services long-running tasktermination complete

Explanation: The Connection Services long runningtask (LRT) has been terminated.


System action: Termination of the Connection Servicessubcomponent continues.


Module: EYU0CPLT

Destination: EYULOG

EYUCP0008E Connection Services long-running taskterminating due to nonrecoverable error

Explanation: The Connection Services long runningtask (LRT) encountered an error from which it couldnot recover.


User response: Stop and restart the CMAS where thefailure occurred, as indicated by the APPLID stampthat precedes the message. If the problem persists,collect any exception trace records, the job log, andCICS or MVS dump output, if available, and contactyour IBM Support Center.

Module: EYU0CPLT


EYUCP0009E Connection Services long-running taskerror, continuing processing.

Explanation: The Connection Services long runningtask (LRT) encountered an error, but was able torecover and continue processing.

System action: Connection Services processingcontinues. A user trace record is written to the CICStrace data set.

User response: If the problem persists, collect theexception trace records and the job log, and contactyour IBM Support Center.

Module: EYU0CPLT


EYUCP0010E Synchronization for CICSplex plexnameon CMAS cmasname failed. That CMASis being isolated.

Explanation: An attempt to perform repositorysynchronization for the specified CICSplex and CMASfailed, where:

plexnameIs the name of the CICSplex for which thesynchronization was attempted.

cmasnameIs the name of the CMAS that could not besynchronized.

System action: This CMAS will issue an exceptiontrace, request an SVCdump, and issue this message.

The CMAS which could not be synchronized is thenremoved from the CMAS network.

User response: Collect the CICS auxtrace data sets, theSVCdump, the job output from this CMAS, and abackup copy of this CMAS's data repository. Note thatmessage EYUCP0011E is issued in the CMAS that wasisolated. Refer to the description of that message foradditional documentation to collect.

To recover from the problem, the isolated CMAS andall MASs connected to it should be terminated.Thenrestart the isolated CMAS. After it successfullyperforms repository synchronization with the otherCMASs in the network (EYULOG messagesEYUCP0203I and EYUCP0204I), its MASs can berestarted.

To determine the cause of the problem, contact yourIBM Support Center with the documentation collected.

Module: EYU0CPLT


EYUCP0011E Repository synchronization failed forone or more CICSplexes. This CMAS isbeing isolated at the request of CMAS(cmasname).

Explanation: The data repository of the CMAS thatissued this message could not be synchronized for oneor more CICSplexes, where:

cmasnameIs the name of the CMAS that requested theisolation.

System action: This CMAS issues an exception trace,request an SVC dump, and issues this message. ThisCMAS is then removed from the CMAS network.

All the connections to the CMAS are terminated.

User response: Collect the CICS auxtrace data sets, theSVCdump, the job output from this CMAS, and abackup copy of this CMAS's data repository. If therequesting CMAS is not the local CMAS, messageEYUCP0010E is also issued in the requesting CMAS.Refer to the description of that message foradditionaldocumentation to collect. If the requesting CMAS is thelocal CMAS, message EYUXD0029E is also issued inthe local CMAS, and no additional documentationneeds to be collected.

To recover from the problem, the local CMAS and allMASsconnected to it should be terminated. The localCMAS should then be restarted. After it successfullyperforms repository synchronization with the otherCMASs in the network (EYULOG messagesEYUCP0203I and EYUCP0204I), its MASs can berestarted.


EYUCP0008E • EYUCP0011E


Module: EYU0CPRL


EYUCP0012E Maintenance point for CICSplexplexname on cmasid1 is at a lower versionthan cmasid2. The CICSplex will bedeleted from cmasid2.

Explanation: In attempting to connect the specifiedCMASs to each other, CICSPlex SM determined thatthe connecting CMAS is running a later release of theproduct than the maintenance point CMAS, where:

plexnameIs the name of the CICSplex that is affected.

cmasid1Is the name of the maintenance point CMASfor the CICSplex.

cmasid2Is the name of a CMAS that was found to berunning a later release of CICSPlex SM thanthe maintenance point.

The maintenance point CMAS must always be runningthe most current release of any CMAS actively involvedin managing the CICSplex.

System action: The CMAS running the later release ofCICSPlex SM is removed from active management ofthe CICSplex. All definitions related to the CICSplexare deleted from the later level CMAS's data repository.

User response: Upgrade the maintenance point CMASto the most current release of CICSPlex SM. Bring upboth CMASs. When both CMASs have connected,re-add the non-maintenance point CMAS to theCICSplex.

For details on upgrading from one release ofCICSPlex SM to another, see the Upgradingdocumentation for this CICS release.

In a complex CICSplex environment, repeated instancesof message EYUCP0012E and message EYUTS0012Emight be issued by a newly upgraded CMAS. This canbe relieved by recycling the affected CMAS.

Module: EYU0CCPA, EYU0CPAI, EYU0CPSI


EYUCP0013E CMAS cmasid1 at version relnum is notsupported by cmasid2. cmasid2 willterminate.

Explanation: In attempting to connect the CMASs in anetwork, CICSPlex SM determined that the specifiedCMASs are running incompatible releases of theproduct, where:

cmasid1 Is the name of the CMAS that is running anearlier release of CICSPlex SM.

relnum Identifies the release of CICSPlex SM that isno longer supported by a later release.

cmasid2 Is the name of the CMAS that is running alater release of CICSPlex SM.

System action: The CMAS running the later release ofCICSPlex SM shuts down.

User response: If you want to include the CMASidentified as cmasid1 in a network with more currentCMASs, you must upgrade that CMAS to a supportedrelease of CICSPlex SM.

For a list of supported releases and details onupgrading from one release to another, see theUpgrading documentation for this CICS release.

Module: EYU0CPCI, EYU0CPDG


EYUCP0014E A failure occurred while attempting todisconnect from CMAS cmasname

Explanation: While attempting to remove aCICSPlex SM connection between this CMAS andanother CMAS, a failure has occured, where:

cmasnameIs the name of the other CMAS.

System action: The connection is terminated, but allappropriate cleanup may not have occured. This mayresult in errors when the link is re-established.

User response: Collect all job output and AUXTRACEdata sets from both CMASs. When the link isre-established, ensure that each CMAS JOINs the MASsof the other CMAS. If not, restarting either CMASshould correct the problem. If the problem persists,contact your IBM Support Center.

Module: EYU0CPRL


EYUCP0015E NetTop Import Error. Invalid valuedetected for CMAS cmas, APPLID applid,SYSID sysid

Explanation: A network topology exchange hasoccurred, but the definition of CMAS cmas, which wasreceived, specifies an APPLID or SYSID that conflictswith an existing CMAS.

System action: The CMAS cmas is not added to theissuing CMAS's network topology.

User response: Check the CMTCMDEFs of otherCMASs to ensure that the definitions are correct andthat all CMAS names, APPLIDs and SYSIDs are unique.

Module: EYU0CPCI



Chapter 10. EYUCPnnnn messages 45

EYUCP0016I This CMAS converts to the lowercapability of CMAS nodename.

Explanation: This CMAS is communicating withCMAS nodename which has one or more resource tablesat an earlier version or level of service where:

nodenameis the CMAS name of a communications node.

The capability of a CMAS is determined by its servicelevel or CICSPlex SM release and version.

System action: This CMAS might perform additionalprocessing during transmissions with CMAS nodenamebecause of the need to convert one or more of itsresource tables to the earlier version in use by CMASnodename.

User response: No action is needed. This message isfor information only.

Module: EYU0CPUC

Destination: EYULOG

EYUCP0017E Capability of CMAS nodename is notvalid for this CMAS to connect.

Explanation: CMAS nodename has at least one resourcetable at a later version or service level and at least oneresource table at an earlier version or service level thanthis CMAS where:


The capability of a CMAS is determined by its servicelevel or CICSPlex SM release and version.

This CMAS cannot determine whether it has theresponsibility to convert resource tables to an earlierversion during transmissions between itself and CMASnodename, or whether CMAS nodename will do so.

This message might be followed by messageEYUCP0018E which can give more information.

System action: The request to establish acommunications link is denied.

User response: Correct the startup JCL for either thisCMAS or CMAS nodename. The service level orCICSPlex SM release and version should either be thesame for both CMAS systems, or one of the CMASsystems should be at a later level of service or versionof CICSPlex SM.

Module: EYU0CPUC


EYUCP0018E Resource type mismatch n with CMASnodename is objname

Explanation: CMAS nodename has a version ofresource table objname that does not match the versionin use by this CMAS where:


objnameis the name of a resource table in use byCMAS nodename which is at an earlier or laterrelease than that in use by this CMAS.

n is the number of mismatches detected.

This message can be issued for up to two resource tabletypes.

System action: See message EYUCP0017E for moreinformation.

User response: See message EYUCP0017E for moreinformation.

Module: EYU0CPUC


EYUCP0019I This CMAS no longer needs to convertto a lower capability for CMASnodename.

Explanation: This CMAS has had to convert one ormore of its resource tables to an earlier version duringtrasmissions between itself and CMAS nodename where:


The additional processing is no longer performed.

System action: Processing continues

User response: No action is needed. The message isfor information only..

Module: EYU0CPUC

Destination: EYULOG

EYUCP0020I This CMAS converts to the lowercapability of MAS nodename.

Explanation: This CMAS is communicating with MASnodename which has one or more resource tables at anearlier version or level of service where:


The capability of a MAS is determined by its servicelevel or CICSPlex SM release and version.

System action: This CMAS might perform additionalprocessing during transmissions with MAS nodename

EYUCP0016I • EYUCP0020I


because of the need to convert one or more of itsresource tables to the earlier version in use by MASnodename.

User response: No action is needed. This message isfor information only.

Module: EYU0CPAM

Destination: EYULOG

EYUCP0021I This CMAS no longer needs to convertto a lower capability for MAS nodename.

Explanation: This CMAS has had to convert one ormore of its resource tables to an earlier version duringtrasmissions between itself and MAS nodename where:


The additional processing is no longer performed.


User response: None. The message is for informationonly..

Module: EYU0CPAM

Destination: EYULOG

EYUCP0022E Maintenance point for plexname oncmasid1 has a lower capability thancmasid2. CMAS cmasid2 will be isolatedfrom the CICSplex.

Explanation: In attempting to connect the specifiedCMASs CICSPlex SM determined that the maintenancepoint is at an earlier service level of CICSPlex SM thanthe connecting CMAS where:

plexnameis the name of the affected CICSplex.

cmasid1is the name of the maintenance point for theCMAS.

cmasid2is the name of the connecting CMAS.

The maintenance point CMAS must run at the same ora later service level of CICSPlex SM than a connectingCMAS for a particular CICSplex. The capability of aCMAS is determined by service level.

System action: The connecting CMAS, which isrunning a later service level of CICSPlex SM is isolatedfrom the CICSplex.

User response: If you want to include the CMASidentified as cmasid1 in a network with more currentCMASs, you must upgrade that CMAS to the same orlater service level of CICSPlex SM.

Module: EYU0CPAI, EYU0CPSI

Destination: EYULOG

EYUCP0023E A communications failure has occurredwhile performing RepositorySynchronization with CMAS (cmasname)That CMAS is being isolated.

Explanation: A communications error has occurredwhile this CMAS was performing repositorysynchronization with another CMAS, resulting in theisolation from the CMAS network of the other CMAS,where

cmasnameIs the name of the CMAS being isolated.

System action: This CMAS issues an exception trace,request an SVCdump, and issue this message. TheCMAS which could not be synchronized is thenremoved from the CMAS network.

User response: Collect the CICS auxtrace data sets, theSVCdump, and the job output from this CMAS. Notethat message EYUCP0024E is issued in the CMAS thatwas isolated. Refer to the description of that messagefor additional documentation to collect.

To recover from the problem restart the isolated CMAS.


Module: EYU0CPLT


EYUCP0024E A communications failure has occurredwhile performing RepositorySynchronization. This CMAS is beingisolated at the request of CMAS(cmasname) .

Explanation: A communications error has occurredwhile this CMAS was performing repositorysynchronization with another CMAS, resulting in theisolation from the CMAS network of this CMAS,where:

cmasnameIs the name of the CMAS that requested theisolation.

System action: This CMAS issues an exception trace,request an SVC dump, and issue this message. ThisCMAS is then removed from the CMAS network.

User response: Collect the CICS auxtrace data sets, theSVC dump, and the job output from this CMAS. Notethat message EYUCP0023E is issued in the CMAS thatrequested the isolation. Refer to the description of thatmessage for additional documentation to collect.

To recover from the problem restart this CMAS.


EYUCP0021I • EYUCP0024E


Module: EYU0CPLT


EYUCP0029E The data repository records forCICSplex (plexname) cannot beupgraded. Resynchronization with theMaintenance Point CMAS (mpcmasnm) isrequired.

Explanation: While this CMAS was processing datarepository updates that were shipped from themaintenance point CMAS for a CICSplex, anunrecoverable error was encountered, where:

mpcmasnmIs the name of the maintenance point CMAS.

plexnameIs the name of the CICSPlex for which theupdates were being attempted.

System action: This CMAS issues an exception trace,this message and message EYUCP0011E. This CMAS isthen removed from the CMAS network.

User response: Refer to the description of messageEYUCP0011E for guidance.

Module: EYU0XDRS


EYUCP0030I Connected directly to CMAS cmasname

Explanation: The local CMAS is now directlyconnected to a CMAS, where:

cmasnameIs the name of the CMAS to which the localCMAS is directly connected.

System action: This message is issued.

User response: None

Module: EYU0CPDG

Destination: EYULOG

EYUCP0031I Connected indirectly to CMAScmasname1 through CMAS cmasname2

Explanation: The local CMAS is now indirectlyconnected to a CMAS, where:

cmasname1Is the name of the CMAS to which the localCMAS is indirectly connected.

cmasname2Is the name of the first CMAS that the localCMAS connects through for the indirectconnection.


User response: None

Module: EYU0CPDG

Destination: EYULOG

EYUCP0032I No longer connected to CMAS cmasname

Explanation: The local CMAS no longer has aconnection, where:

cmasnameIs the name of the CMAS to which the localCMAS is no longer connected.


User response: None

Module: EYU0CPDG, EYU0CPSL

Destination: EYULOG

EYUCP0033I Disconnect requested for CMAScmasname Reason reason

Explanation: The local CMAS will disconnect a CMASto CMAS link, where:

cmasnameIs the name of the partner CMAS that will bedisconnected.

reason Is the reason why the local CMAS isrequesting the disconnect. Values may be:

Method failureA method call has failed.

Method ABENDAn abend has occurred.

CMAS isolatedThe CMAS is being isolated, so allCMAS communications will stop.

Duplicate MPThe CMAS to CMAS link is beingstopped because a duplicatemaintenance point CMAS for aCICSplex has been detected.

CMTCMLNK discardThe CMTCMLNK is being discardedby a WUI or API discard action.

System action: The CMAS to CMAS send link task forthe identified CMAS will be stopped. The CMAS mustbe restarted if communications to the partner system isto be retried.

User response: Depending on the reason indicated inthe message, take action as follows:

Method failure or Method ABENDRefer to other messages for both the local andthe partner CMASes. If no relevant messagescan be found, collect the CICS auxtracedatasets, any SVC dumps and the completejob output from the local and partner CMASes

EYUCP0029E • EYUCP0033I


###

##

###

###

##

##

###

#####

###

####

##

######

identified in the message. To determine thecause of the problem, contact your IBMSupport Center with the documentationcollected.

CMAS isolatedRefer to message EYUCP0011E.

Duplicate MPRefer to message EYUCP0001E.

CMTCMLNK discardNone. The CMAS to CMAS link was discardedbased on a user request.

Module: EYU0CPDG, EYU0CPRL, EYU0CPTI,EYU0CSUC

Destination: EYULOG

EYUCP0032I No longer connected to CMAS cmasname

Explanation: The local CMAS no longer has aconnection, where:

cmasnameIs the name of the CMAS to which the localCMAS is no longer connected.


User response: None

Module: EYU0CPDG, EYU0CPSL

Destination: EYULOG

EYUCP0102W Check CICSPlex SM licensecompliance: count1 type CICS regionsbeing managed in CICSplex plexname,this is percentage% of the count2Managed Region features licensed forthis CICSplex. You may need to licensefurther copies of the Managed Regionfeature from IBM.

Explanation: You have exceeded the maximumnumber of Managed Region features allowed for thespecified type, where:

count1 Indicates the current number of activemanaged regions of the indicated type.

type Identifies the managed region type as MVS orVSE.

plexnameIs the name of the CICSplex.

percentageIs percentage of the maximum allowed that iscurrently active.

count2 Indicates the maximum number of activemanaged regions allowed.

System action: None.

User response: Check your IBM license agreement or

a current billing statement for the number of copies ofthe Managed Region feature licensed by yourenterprise. The number of CICS systems you intend tomanage concurrently cannot exceed the number ofManaged Region features you have licensed.

If the number of Managed Region features you havelicensed appears to be sufficient, then make sure thattheir distribution among your CICSplexes matches youractual CICSplex configurations. Use the CPLEXDEFview (described in theCICSPlex System ManagerAdministration manual) to review the number ofmanaged regions assigned to each CICSplex.

If you have not licensed a sufficient number ofManaged Region features to support your enterprise,then you should:

v Remove the excess CICS systems from theCICSPlex SM management environment.

v Contact your IBM representative to license additionalcopies of the Managed Region feature.

Module: EYU0CPCM


EYUCP0103W LIKELY VIOLATION OF CICSPLEXSM LICENSE TERMS. count1 type CICSregions being managed in CICSplexplexname Only count2 are covered byManaged Region feature. Currentlymanaging percentage% of permittednumber of regions. Please contact IBMto license additional copies of theManaged Region feature.

Explanation: You have greatly exceeded the maximumnumber of Managed Region features allowed, where:

count1 Indicates the current number of activemanaged regions of the indicated type.

type Identifies the managed region type as MVS orVSE.


count2 Indicates the maximum number of activemanaged regions allowed.

percentageIs percentage of the maximum allowed that iscurrently active.


User response: Check your IBM license agreement ora current billing statement for the number of copies ofthe Managed Region feature licensed by yourenterprise. The number of CICS systems you intend tomanage concurrently cannot exceed the number ofManaged Region features you have licensed.

If the number of Managed Region features you havelicensed appears to be sufficient, then make sure that

EYUCP0032I • EYUCP0103W


####

##

##

###

##

#

their distribution among your CICSplexes matches youractual CICSplex configurations. Use the CPLEXDEFview (described in the CICSPlex System ManagerAdministration manual) to review the number ofmanaged regions assigned to each CICSplex.

If you have not licensed a sufficient number ofManaged Region features to support your enterprise,then you should:

v Remove the excess CICS systems from theCICSPlex SM management environment.

v Contact your IBM representative to license additionalcopies of the Managed Region feature.

Module: EYU0CPCM


EYUCP0200I CMAS cmas1 being added to CMASdirectory in CMAS cmas2

Explanation: The CMAS known as cmas1 has beensuccessfully identified to the CMAS known as cmas2.cmas1 can now participate in the CMAS network.



Module: EYU0CPAC

Destination: EYULOG

EYUCP0201I NetTop import started from CMAScmasname

Explanation: A network topology change has beeninitiated by the specified CMAS. This message appearsonly if trace level 23 (for the Communicationscomponent) is set to YES in the CMAS.



Module: EYU0CPTI

Destination: EYULOG

EYUCP0202I NetTop import ended from CMAScmasname

Explanation: A network topology change that wasinitiated by the specified CMAS has been successfullycompleted. This message appears only if trace level 23(for the Communications component) is set to YES inthe CMAS.



Module: EYU0CPTI

Destination: EYULOG

EYUCP0203I Repository Synchronization started withCMAS cmasname

Explanation: The data repository for the specifiedCMAS is being synchronized with the data repositoryof the CMAS that issued this message. The datarepositories for all CMASs that participate in a networkare synchronized to contain the same network topologyinformation.



Module: EYU0CPLT

Destination: EYULOG

EYUCP0204I Repository Synchronization endedsuccessfully with CMAS cmasname

Explanation: The data repository for the specifiedCMAS has been successfully synchronized with thedata repository of the CMAS that issued this message.



Module: EYU0CPLT

Destination: EYULOG

EYUCP0205S Repository Synchronization with CMAS(cmasname) failed.

Explanation: The Connection Services long runningtask (LRT) encountered an error while trying tosynchronize the repository of the CMAS that issued themessage with the CMAS (cmasname).

System action: The CMAS which issues the messagecontinues processing. However the CMAS (cmasname)may no longer be able to accept Topology Joins orWLM requests.

User response: If you shut down more than oneCMAS at the same time, you might receive messageEYUCP0205S. In this situation, the message does notindicate a problem, and CICSPlex SM does not producea diagnostic SVC dump as it normally would when thismessage is issued. You can avoid the message bystaggering your CMAS shutdowns.

For all other situations, stop and restart CMAS (cmasname). This causes the synchronization process tobe retried on the restart. If the problem persists, collectany exception trace records and the job logs of bothCMASs, and contact your IBM Support Center.

Module: EYU0CPLT


EYUCP0200I • EYUCP0205S


EYUCP0206E Data repository definitions forCICSplexCMAS (plexname) areincomplete. Repository Synchronizationwill bypass this CICSplex.

Explanation: During repository synchronizationprocessing between the current CMAS and anotherCMAS, the current CMAS determined that the datarepository (EYUDREP) records were incomplete for aCICSplex for which it is the maintenance point (MP)CMAS, where:


System action: This message and a trace record areissued. Repository synchronization continues withoutprocessing the CICSplex that is in error.

User response: An error occurred when the CICSplexwas either added or removed, resulting in incompleteEYUDREP records for the CICSplex. Check the currentand previous job logs for this CMAS to determine ifany error messages were issued. If any error messagesare found, collect the messages, the unformattedauxtrace data sets from that run of the CMAS (ifavailable), and a backup copy of the CMAS'sEYUDREP, then contact your IBM support center.

To resolve the error message, remove the CICSplexfrom the CPLEXDEF view of the Web user interface(WUI). If the CICSplex is required, recreate it afterremoving it. If this does not resolve the problem, collectthe job output, unformatted CICS auxtrace data setsfrom the current execution of the CMAS, and a backupcopy of the CMAS's EYUDREP, then contact your IBMsupport center.

Module: EYU0CPLT


EYUCP0207E CICSplex plexname on CMAS cmasnamecannot be action as MASes are active onCMAS cmasname.

Explanation: The CMAS that issues this message isthe maintenance point (MP) CMAS for CICSplexplexname.

During a data repository synchronization for CICSplexplexname with CMAS cmasname the maintenance pointCMAS has determined that the CICSplex definition inCMAS cmasname must be deleted. The CICSplex deletewas not possible as MASes within CICSplex plexnamewere directly connected (or were in the process ofconnecting) to CMAS cmasname at the time of the datarepository synchronization attempt.

action may be 'deleted' or redefined':

v If action is 'deleted' the delete of the CICSplex is dueto a 'FORce' action on the CPLXCMAS view orbecause the non-MP CMAS is using a later level ofCICSPlex SM than the MP CMAS for the CICSplex.

v If action is 'redefined' the CICSPlex is being deletedas the CICSplex is being redefined on CMAScmasname as the definitions for CICSplex plexname areout of date.

System action: Message EYUCP0010E will be issuedand CMAS cmasname will be isolated.

User response: The MAS agents that connect directlyto CMAS cmasname need to be stopped and CMAScmasname will need to be restarted in order for the datarepository synchronization to complete.

To identify the MAS agents that were connected (ortrying to connect), review the CMAS cmasnameEYULOG for the following messages:

v EYUTI0001I (with 'Topology Connect') identifiesMASs directly connected to the CMAS

v EYUTI0009I identifies MASes trying to connect to theCMAS

To stop the CICSPlex SM MAS agent in these MASseither use the COSH transaction in each MAS or if theMASs are connected to the non-MP CMAS, the MASview STOp action (or WUI/API equivalent).Alternatively, shut down the MAS.

Once the MAS agents have been stopped, restart CMAScmasname to retry the data repository synchronization.

When the data repository synchronization hascompleted, restart the previously stopped MAS agentswith the COLM transaction, or restart the MASs.

Module: EYU0CPLT




Chapter 11. EYUCRnnnn messages

EYUCR0001I Security Services initialization complete

Explanation: The Security Services subcomponent hasbeen successfully initialized.

System action: CMAS initialization continues.


Module: EYU0CRIN

Destination: EYULOG

EYUCR0002I Security Services long-running taskinitialization complete

Explanation: The Security Services long running task(LRT) has been successfully initialized.

System action: The initialization of Security Servicessubcomponent continues.

User response: None

Module: EYU0CRLT

Destination: EYULOG

EYUCR0003I Security Services long-running tasktermination complete

Explanation: The Security Services long running task(LRT) has been terminated.

System action: Termination of the Security Servicessubcomponent continues.


Module: EYU0CRLT

Destination: EYULOG

EYUCR0004E Security Services initialization failed

Explanation: The Security Services subcomponentcould not be initialized.

System action: CMAS initialization terminates. A usertrace record is written to the CICS trace data set.

User response: Collect the exception trace records andthe job log, and contact your IBM Support Center.

Module: EYU0CRIN


EYUCR0005E Security Services long-running taskterminating due to nonrecoverable error

Explanation: The Security Services long running task

(LRT) encountered an error from which it could notrecover.

System action: The LRT terminates. The CMAS maycontinue running without the services of the LRT.

User response: Stop and restart the CMAS where thefailure occurred. If the problem persists, collect anyexception trace records, the job log, and CICS or MVSdump output, if available, and contact your IBMSupport Center.

Module: EYU0CRLT


EYUCR0006W Security checking disabled perSEC(NO) EYUPARM parameterspecification

Explanation: The CMAS is running without anysecurity checking, as requested in its startup job.

System action: CMAS processing continues.

User response: If you want the CMAS to use security,then specify SEC(YES) in the EYUPARM member forthe CMAS If SEC is not specified, the default isSEC(NO). Then stop and restart the CMAS.

Module: EYU0CRIN


EYUCR0007E Security mismatch between CMAScmasname and MAS masname. Connectionterminating.

Explanation: The specified MAS was started with aCICS SIT parameter of SEC=YES, but the CMAS thatmanages it was started with an EYUPARM parameterof SEC(NO). A CMAS that has security disabled cannotprovide security processing for any of its MASs.

System action: The connection between the MAS andCMAS is terminated. The CICS system continues torun, but it is not known to CICSPlex SM.

User response: If you want security to be active in theMAS, change the SEC parameter for the CMAS thatmanages it to YES. If you decide you do not wantsecurity for the MAS, change its SEC parameter to NO.Then stop and restart the CMAS or MAS, asappropriate.

Module: EYU0CRSC



EYUCR0008E Mutually exclusive CICS andCICSPlex SM security parametersspecified. The CMAS will terminate.

Explanation: A CMAS was being initialized with boththe CICS SIT parameter SEC=YES and theCICSPlex SM system parameter SEC(YES) specified. Toensure proper security checking by CICSPlex SM, thefollowing CICS SIT parameters for a CMAS must all beset to NO:

v XCMD=

v XDCT=

v XFCT=

v XJCT=

v XPCT=

v XPPT=

The external security manager (ESM) resource listscannot be correctly referenced by both CICS andCICSPlex SM.

System action: CMAS initialization terminates.

User response: If you want to use both CICS andCICSPlex SM security in a CMAS, make sure theXCMD=, XDCT=, XFCT=, XJCT=, XPCT=, and XPPT=CICS SIT parameters are all set to NO. Then restart theCMAS.

Module: EYU0CRIN


EYUCR0009I Security check: Userid=userid,Class=classname, Access=access,Resource=resource,ESMResponse=esmresp,ESMReason=esmrson

Explanation: A security check has occurred, where:

userid Is the user ID of the user requesting access tothe resource.

classnameIs the name of the class being checked.

access Is the access level being attempted. It may beRead, Update, Control, Alter or Unknown.

resourceIs the name of the resource being accessed.

esmrespIs the response code from the ESM.

esmrsonIs the reason code from the ESM.

The CICSPlex SM CMAS system parameterSECLOGMSG must be set to YES or ALL for thismessage to be issued.

System action: If access to the resource is notpermitted by the External Security Manager, the request

will fail. Typically the response from an API or WUIrequest would be NOTPERMIT with a reason ofUSRID.

User response: None if access is being correctlydisallowed. If access is being incorrectly disallowed,use the information in the message to determine whatresource is being checked, and why the ESM is notallowing access.

Module: EYU0CRCK

Destination: EYULOG

EYUCR0010I Security profiles not refreshed. Refreshmust be performed using ESM.

Explanation: A security rebuild has been requested.This request has not been actioned, as the ExternalSecurity Manager (ESM) must be used to refresh thesecurity profiles used by the CMAS.


User response: Use the facilities provided by the ESMto refresh the security profiles. For example, RACFusers could issue the TSO command:

SETROPTS RACLIST(xxxxxxxx) REFRESH

where xxxxxxxx is the name of the RACF class torefresh.

Module: EYU0CRLT

Destination: EYULOG

EYUCR0008E • EYUCR0010I


Chapter 12. EYUCSnnnn messages

The following variables are used in EYUCSnnnn messages:

modeIdentifies the communications mode that is used on the communicationsconnection as either Standard or Enhanced. The communications mode isdetermined automatically by the link set services subcomponent and cannot becontrolled by the user.

textA message received from a partner system. Consult the Messages and Codesmanual for a description of this message.

typeIdentifies the type of communications connection that has been assigned as oneof the following:

CPI-C networkCMAS-to-CMAS connection using CPI-C (LU6.2) transmission protocol

MRO networkCMAS-to-CMAS connection using MRO transmission protocol

Netview endpointCMAS-to-Netview connection using the Netview PPI link

nameThe name of the communications partner.

EYUCS0001I Link Set Services initialization complete

Explanation: The link set services subcomponent ofthe Communications component has been successfullyinitialized.


User response: None

Module: EYU0CSIN

Destination: EYULOG

EYUCS0002I Communications long-running taskinitialization has started

Explanation: The Communications long running task(LRT) is being initialized.

System action: Initialization of the CommunicationsLRT continues.

User response: None

Module: EYU0CSLT

Destination: EYULOG

EYUCS0003I Communications long-running taskinitialization complete

Explanation: The Communications long running task(LRT) has been successfully initialized.


User response: None

Module: EYU0CSLT

Destination: EYULOG

EYUCS0004I Communications long-running tasktermination has started

Explanation: The Communications long running task(LRT) is being terminated.

System action: Termination of the CommunicationsLRT continues.

User response: None

Module: EYU0CSLT

Destination: EYULOG

EYUCS0005I Communications long-running tasktermination complete

Explanation: The Communications long running task(LRT) has been terminated.


System action: If the LRT was terminated as the resultof a normal shutdown, the CICSPlex SM shutdowncontinues. If the LRT terminated because of anabnormal condition, a message preceding this onedescribes the condition that caused the termination.CICSPlex SM may continue running without theservices of the LRT.

User response: If a normal CICSPlex SM shutdown isin progress, no action is required. If the LRT terminatedbecause of an abnormal condition (as indicated bymessage EYUCS0104E preceding this message),CICSPlex SM should be shut down and restarted.

Module: EYU0CSLT

Destination: EYULOG

EYUCS0006I type connection name assigned to link set

Explanation: The specified communicationsconnection has been successfully assigned to aCICSPlex SM link set where type and name are asdescribed in the introduction to the EYUCSnnnnmessages. Link sets are the means by whichCICSPlex SM optimizes processing to be performed forconnections with similar attributes. Once a connectionhas been assigned to a link set, CICSPlex SM cantransmit data to, and receive data from, itscommunications partner.

System action: The connection becomes available toother CICSPlex SM communications processes.


Module: EYU0CSAC

Destination: EYULOG

EYUCS0007I type connection name unassigned fromlink set

Explanation: The specified communicationsconnection has been successfully unassigned from aCICSPlex SM link set. Link sets are the means bywhich CICSPlex SM optimizes processing to beperformed for connections with similar attributes wheretype and name are as described in the introduction tothe EYUCSnnnn messages. Once a connection has beenunassigned from a link set, CICSPlex SM can no longertransmit data to, or receive data from, itscommunications partner.

System action: The connection is no longer availableto other CICSPlex SM communications processes.


Module: EYU0CSUC

Destination: EYULOG

EYUCS0008I Service request block element shortagerelieved

Explanation: A shortage of service request blockelements for a communications long running task (LRT)has been successfully relieved by allocating additionalelements. Service request block elements are the meansby which CICSPlex SM communications processesdirect requests to the LRT.

System action: Any communications processeswaiting for an element are dispatched and permitted toacquire one.


Module: EYU0CSES

Destination: EYULOG

EYUCS0009I Message received from CMAS name :text

Explanation: An message had been received from thepartner CMAS during the connection initializationprocess. See Chapter 12, “EYUCSnnnn messages,” onpage 55for the meaning of name and text.

System action: Depending on the severity of themessage text, either the CMAS to CMAS connectioncompletes successfully, or the connection terminatesand other supporting messages are issued.

User response: If the connection has failed tocomplete successfully, retain the EYULOG, JOBLOGand exception trace records from both CMASes andcontact your IBM support center

Module: EYU0CLCS, EYU0CLMS

Destination: EYULOG

EYUCS0010I mode type to CMAS name beinginitialized

Explanation: A communications connection betweenthe local CMAS and a partner CMAS is starting. SeeChapter 12, “EYUCSnnnn messages,” on page 55 forthe meaning of mode, type and name.

System action: The communications connectioncontinues to initialize.

User response: None


Destination: EYULOG

EYUCS0011W The value of EYUPARM parmnamewas specified less than 10 seconds. Thisvalue has been set to 10 seconds for thisexecution of the CMAS.

Explanation: The indicated EYUPARM was set to anon-zero value less than 10 seconds.

EYUCS0006I • EYUCS0011W


System action: The value for the indicated EYUPARMis set to 10 seconds and CMAS initialization continues.

User response: If a value greater than 10 seconds isdesired, modify the indicated EYUPARM and restartthe CMAS. If a value of 10 seconds is desired, no userresponse is required for the current execution of theCMAS. However, to avoid this message for futureexecutions of the CMAS, modify the indicatedEYUPARM to 10 before the CMAS is restarted.

Module: EYU0CSLT


EYUCS0012W Request timeout EYUPARM eyuparmhas been set less than timeout pollingEYUPARM TOPOLLINT

Explanation: The indicated EYUPARM has been givena value that is less than the TOPOLLINT EYUPARM.While this is allowed, it is not efficient.


User response: Since polling is used to determinewhen to time out a request, specifying a lower valuefor time out than for polling will most likely result inthe request being timed out later than specified. If thisis not desired, modify the EYUPARMs so thatTOPOLLINT is less than or equal to the indicatedEYUPARM and restart the CMAS.

Module: EYU0CSLT


EYUCS0101E Link Set Services initialization failed

Explanation: The link set services subcomponent ofthe Communications component could not beinitialized.

System action: CICSPlex SM initialization terminatesabnormally. A user trace record is written to the CICStrace data set.


Module: EYU0CSIN


EYUCS0102E Unable to create Link Set PendingConnections List

Explanation: The Communications long running task(LRT) was not able to create the link set pendingconnections list. This list is used to store informationabout communications connections whose status is tobe monitored.


User response: Collect the exception trace records andthe job log and contact your IBM Support Center.

Module: EYU0CSLT


EYUCS0103E Unable to start Communicationslong-running task

Explanation: The link set services subcomponent ofthe Communications component was not able to startthe Communications long running task (LRT) for aCICSPlex SM address space (CMAS).


User response: Examine the CICS CSD to verify thattransaction CSLT and program EYU9XLOP are defined.If the definitions appear to be correct, collect theexception trace records and the job log and contactyour IBM Support Center.

Module: EYU0CSIN


EYUCS0104E Communications long-running taskterminating due to nonrecoverable error

Explanation: The Communications long running task(LRT) encountered an error from which it could notrecover.


User response: Examine any messages issued beforethis one to determine the cause of the problem. Collectany exception trace records, the job log, and CICS orMVS dump output, if available, and contact your IBMSupport Center.

Module: EYU0CSLT


EYUCS0105E Unable to assign link set for typeconnection name

Explanation: The specified communicationsconnection could not be assigned to a CICSPlex SMlink set where type and name are as described in theintroduction to the EYUCSnnnn messages. Link sets arethe means by which CICSPlex SM optimizes processingto be performed for connections with similar attributes.Until a connection has been assigned to a link set,CICSPlex SM cannot transmit data to, or receive datafrom, its communications partner.

System action: CICSPlex SM attempts to assign theconnection again at periodic intervals.

User response: If the problem persists, collect any

EYUCS0012W • EYUCS0105E

Chapter 12. EYUCSnnnn messages 57

exception trace records and the job log and contactyour IBM Support Center.

Module: EYU0CSAC


EYUCS0106E Unable to unassign link set for typeconnection name

Explanation: The specified communicationsconnection could not be unassigned from aCICSPlex SM link set where type and name are asdescribed in Chapter 12, “EYUCSnnnn messages,” onpage 55. Link sets are the means by whichCICSPlex SM optimizes processing to be performed forconnections with similar attributes.

System action: The connection cannot be used byother CICSPlex SM communications processes. A usertrace record is written to the CICS trace data set.


Module: EYU0CSUC


EYUCS0107E Service request block element shortagecould not be relieved

Explanation: A shortage of service request blockelements for a communications long running task (LRT)could not be relieved because there was insufficientstorage to allocate additional elements. Service requestblock elements are the means by which CICSPlex SMcommunications processes direct requests to the LRT.

System action: Any communications processeswaiting for an element receive an indication of thefailure.

User response: Allocate additional storage to the CICSextended dynamic storage area (EDSA).

Module: EYU0CSES


EYUCS0108E The initialization wait for CMASconnections to complete has terminatedbefore all connections have completed

Explanation: During CMAS initialization, the localCMAS is waiting for other active CMASes to initiate aCMAS to CMAS connection. At least one partnerCMAS has failed to do this in the allotted five minutetime frame.

System action: CMAS initialization continues after asystem dump is requested and an exception tracerecord is written to the CICS trace data set.

User response: This situation can occur if CICScommunications problems exist or if a CMAS to CMAS

definition (CMTCMDEF) was removed from a partnerCMAS without COLD starting the CMAS. If thesecauses can be ruled out, collect the system dump, theauxtrace data sets, and the complete job output fromthe CMAS and contact your IBM support center.

Module: EYU0CSLT


EYUCS0201W NetView PPI module could not beloaded - NetView support unavailable

Explanation: The Communications long running task(LRT) was not able to load the NetView PPI module,CNMNETV.

System action: CICSPlex SM continues running withNetView support disabled.

User response: Determine why CNMNETV could notbe loaded and correct the problem.

Module: EYU0CSLT


EYUCS0202W NetView release incompatible -NetView support unavailable

Explanation: The Communications long running task(LRT) determined that the release of NetView installedon the system does not provide the required level ofPPI support.

System action: CICSPlex SM continues running withNetView support disabled.

User response: Review the CICSPlex SM installationrequirements and install a supported release ofNetView on the system.

Module: EYU0CSLT


EYUCS0203W Service request block elementshortage detected

Explanation: A Communications long running task(LRT) service request block element shortage has beendetected. Service request block elements are the meansby which CICSPlex SM communications processesdirect requests to the LRT.

System action: Any communications processeswaiting for an element are suspended. CICSPlex SMattempts to allocate additional elements. This messageis followed by another message that indicates whetherthe shortage could be relieved: EYUCS0008I indicatesthe shortage was relieved; EYUCS0107E indicates it wasnot.


Module: EYU0CSES

EYUCS0106E • EYUCS0203W



EYUCS0204W A timeout has occurred with CMAScmasname

Explanation: Data records have not been received byor have not been able to be sent to the specified CMASfor an internally-defined period of time.

System action: The communications link between thelocal CMAS and the specified CMAS is terminated.

User response: Check the job log of the specifiedCMAS for messages that may indicate the cause of theproblem.

Module: EYU0CSLT


EYUCS0205W Connection to CMAS name beingretried due to : reason

Explanation: An unexpected condition was foundwhen the local CMAS attempted to initiate acommunications connection. See Chapter 12,“EYUCSnnnn messages,” on page 55 for the meaningof name. reason is one of the following values:

Initialization version resetThis occurs when an enhanced connection isattempted by the first speaker, but the partnersystem has responded in such a manner thatindicates that it will accept only the standardconnection method.

Session Allocation failureThis may occur only on a CPI-C connection.The CPI-C protocol services have returned aresponse to the initial connection allocationrequest that implies that, although a failurehas occurred, it is not necessarily severe andmay be retried. The CICSPlex SM connectionprocess may retry the CPI-C allocate up tofifteen times before it considers the connectionunserviceable.

Partner System requestThis may occur when either of the CMASpartners recognize a temporary processingissue that cannot be resolved at the point ofexecution (that is, a resource lock required bythe local connection process has beenwithheld). In these situations, the local systemmay reject the connection request with anindication that it may be retried after a shortperiod of time (typically two minutes). Thepartner CMAS issues the message and thenwaits for the instructed period before retryingthe connection.

System action: The CMAS-to-CMAS connection isretried.

User response: If the connection establishes itself

properly, no further action is required. If the connectionfails to complete, retain the EYULOG, JOBLOG andexception trace records from the CMAS and contactyour IBM support center.



EYUCS0206W Exception trace issued: PointId=tracepoint, Debug text=debug

Explanation: A communications method has writtenan exception trace record where tracepoint is the tracepoint identifier and debug is the debug text. Thismessage is imbedded in message EYUCS0009I. Thetracepoint and debug information is for use by IBMsupport.

System action: The CMAS terminates the connectionto the partner system.

User response: This message occurs with othercommunication error messages. If the connectionremains inactive, collect the job log, EYULOG andexception trace records from both CMASes and contactyour IBM support center.

Module: EYU0CLCT, EYU0CLMT

Destination: EYULOG via message EYUCS0009I

EYUCS0207W Connected MAS masname is notresponding - APPLID (masappl)CICSplex (plexname)

Explanation: The CMAS has determined that thespecified connected MAS is not responding to requestssent to it by the CMAS.

System action: This message is issued and processingcontinues.

User response: Since a nonresponsive MAS can causethe CMAS to experience problems with other MAS andCMAS connections, you are recommended toinvestigate the MAS to determine whether it should beshut down to alleviate the problem.

Module: EYU0CSLT


EYUCS0208I Connected MAS masname is nowresponding - APPLID (masappl)CICSplex (plexname)

Explanation: The CMAS has determined that a MASthat was not responding to requests sent to it by theCMAS is now responding to those requests.

System action: This message is issued and processingcontinues.

User response: None

Module: EYU0CSLT

EYUCS0204W • EYUCS0208I

Chapter 12. EYUCSnnnn messages 59

Chapter 13. EYUCTnnnn messages

EYUCT0001I Transport Services initializationcomplete

Explanation: The Transport Services subcomponent ofthe Communications component has been successfullyinitialized.


User response: None

Module: EYU0CTIN

Destination: EYULOG

EYUCT0002I Transport Services termination complete

Explanation: The Transport Services subcomponent ofthe Communications component has been terminated.

System action: Termination of the Communicationscomponent continues. Because Transport Services is nolonger active, data can no longer be transmittedbetween the current CMAS and any othercommunications node.


Module: EYU0CTRM

Destination: EYULOG

EYUCT0101E Transport Services initialization failed

Explanation: The Transport Services subcomponent ofthe Communications component could not beinitialized.

System action: CICSPlex SM initialization terminateswith abend U1000. A user trace record is written to theCICS trace data set.


Module: EYU0CTIN


EYUCT0102W Transport Services termination failed

Explanation: An error occurred during an attempt toterminate the Transport Services subcomponent of theCommunications component.

System action: All other Communicationssubcomponents attempt an orderly shutdown. A usertrace record is written to the CICS trace data set.

User response: Examine the exception trace records,

and any messages issued before this one, to determinethe cause of the problem.

Module: EYU0CTRM


EYUCT0102W Transport Services termination failed

Explanation: An error occurred during an attempt toterminate the Transport Services subcomponent of theCommunications component.

System action: All other Communicationssubcomponents attempt an orderly shutdown. A usertrace record is written to the CICS trace data set.


Module: EYU0CTRM


EYUCT0104W Transport Services EYUPARMCOMMTSBLOCKS is invalid - theminimum value will be used

Explanation: The value specified for EYUPARMCOMMTSBLOCKS for the CMAS or MAS was less thanthe minimum required.

System action: The minimum value forCOMMTSBLOCKS is used during this execution of theCMAS or MAS.

User response: None, if the minimum value isacceptable. Otherwise, the EYUPARM should bemodified and the CMAS or MAS restarted. Refer to theexplanation of the CICSPlex SM system parameterCOMMTSBLOCKS EYUPARM in CICS TransactionServer for z/OS Installation Guide.

Module: EYU0CTIN


EYUCT0105E Transport Services control blockshortage has occurred

Explanation: A resource shortage has occurred in aCMAS or MAS while attempting to process an API orinternal request. This message is issued the first time ashortage occurs during the execution of the CMAS orMAS.

System action: Execution of the CMAS or MAScontinues.

User response: Message EYUCT0106W should be


issued when the CMAS or MAS terminates. Seemessage “EYUCT0106W” for guidance.

Module: EYU0CAMP, EYU0CTBP, EYU0CTBS,EYU0CTES, EYU0CTMB, EYU0CTSK, EYU0CTSP


EYUCT0106W Transport Services control blockmaximum concurrent shortage wasnumber elements

Explanation: A shortage of transport services controlblocks occurred during the execution of the CMAS orMAS that is terminating, where number is themaximum concurrent shortage that occurred.

System action: A trace record is written andtermination of the CMAS or MAS continues.

User response: Increase the value of theCOMMTSBLOCKS EYUPARM parameter for the CMASor MAS before restarting the CMAS or MAS, using thenumber value as a guide. See the explanation ofCOMMTSBLOCKS EYUPARM in CICS TransactionServer for z/OS Installation Guide for more information.

If increasing the value of COMMTSBLOCKSEYUPARM does not resolve the problem, collect the joboutput and unformatted CICS auxtrace data sets fromthe execution of the CMAS or MAS, and contact yourIBM support center.

Module: EYU0CTRM


EYUCT0107 E date time applid A duplicate packet setwas received from CMAS {name |SYSID} (cmasid).

Explanation: A duplicate packet set has been receivedin this CMAS from another CMAS, where cmasid is theID of the sending CMAS, and where cmasidtypeindicates whether the ID is the sending CMAS 'name'or 'SYSID'.

System action: A dump is requested of the receivingCMAS. If cmasidtype is 'name', then a dump has beenrequested of the sending CMAS. If cmasidtype is'SYSID', then a dump could not be requested of thesending CMAS. Processing then continues.

User response: If cmasidtype is 'SYSID', then a dumpof the sending CMAS should be requested manually.The dump should include the CMAS and ESSS addressspaces, and the dataspaces allocated by the ESSS for theCMAS. See the CICSPlex SM Problem DeterminationGuide section User-requested dumps for moreinformation on the MVS DUMP command. Then collectthe complete job output, auxtrace datasets and dumpsfrom both CMASes.

After the documentation is collected, it is recommendedto shutdown and restart the sending CMAS to correct

the duplicate packet set problem. Note that sincemessage EYUCT0107E is only issued once during therun of a CMAS, the duplicate packet set conditioncould continue occurring even though no subsequentmessages are issued.

To determine the cause of the duplicate packet setproblem, contact your IBM Support center, providingthe collected documentation.

Module: EYU0CTSK

Message inserts:

1. date

2. time

3. applid

4. Value chosen from the following options:

1=name,2=SYSID

5. cmasid

Destination: Console and COLG

EYUCT0106W • EYUCT0107 E


Chapter 14. EYUCWnnnn messages

EYUCW0001I Timing Services initializationcomplete

Explanation: The Timing Services subcomponent hasbeen successfully initialized. Time period registration isnow available.



Module: EYU0CWIN

Destination: EYULOG

EYUCW0002I Timing Services termination complete

Explanation: The Timing Services subcomponent hasbeen terminated. Time period registration is no longeravailable.

System action: CMAS termination continues.


Module: EYU0CWTM

Destination: EYULOG

EYUCW0101E Timing Services initialization failed

Explanation: The Timing Services subcomponentcould not be initialized.

System action: CMAS initialization continues, butTiming Services are not available. A user trace record iswritten to the CICS trace data set.


Module: EYU0CWIN


EYUCW0102E Timing Services termination failed

Explanation: The Timing Services subcomponentcould not be properly terminated. Some resources mayremain allocated.

System action: CMAS termination continues. A usertrace record is written to the CICS trace data set.


Module: EYU0CWTM


EYUCW0103E Timing Services Notifying task hasfailed due to reason

Explanation: The notifying task of the Timing Servicessubcomponent failed for one of the following reasons:

v Excessive Failures

v Registration Failure

v Unsuccessful Wait

v Insufficient Storage

v Internal Error

System action: All existing time period registrationsare canceled. No more time period registration requestsare accepted. A user trace record is written to the CICStrace data set.


Module: EYU0CWTM


EYUCW0104E Time Period definition removed dueto reason

Explanation: An existing time period definition isbeing canceled for one of the following reasons:

v Excessive Failures

v Registration Failure

v Unsuccessful Wait

v Insufficient Storage

v Internal Error

System action: Timing Services processing continues.A user trace record is written to the CICS trace data set.


Module: EYU0CWTR


EYUCW0105W Time Period registration failed fordefinition in context (plexname) due to -reason

Explanation: A CMAS component attempted toregister interest in a time period definition, but therequest failed, where:

plexnameIdentifies the CICSplex for which the CMASwas registering interest.


reason Indicates the reason for the failure, as one ofthe following:

Time Period not defined (defname)The specified time period is notdefined in the data repository.

Timing Services inactiveThe Timing Services subcomponent isnot available.

Internal ErrorThe Timing Services subcomponentencountered an error from which itcould not recover.

System action: Timing Services fails the request.

User response: The user response depends on thereason for the failure:

v For Time Period not defined (defname), make surethe time period name was specified correctly. Use thePERIODEF view to display a list of time perioddefinitions.

v For Timing Services inactive, stop and restart theCMAS. If this problem persists, contact your IBMSupport Center.

v For Internal Error, collect the exception trace recordsand the job log and contact your IBM SupportCenter.

Module: EYU0CWTR


EYUCW0106I Time Period (periodef) is now statusdue to online modification

Explanation: The specified period definition is in useby one or more CICSPlex SM components, such asMonitor Services or real-time analysis. The perioddefinition was either updated or removed using thePERIODEF view and, as a result, its status haschanged, where status identifies the new status of theperiod definition as one of the following:

ACTIVEA period definition that was inactive is nowactive. Any definitions that make use of thetime period also become active.

INACTIVEA period definition that was active is nowinactive. Any definitions that make use of thetime period also become inactive.

REMOVEDThe period definition was removed. Alldefinitions that made use of the time periodare automatically discarded from the runningsystem.

System action: Timing Services processing continues.


Module: EYU0CWTR

Destination: EYULOG

EYUCW0107I Plex end-of-interval is set to occuronce every nnnn minutes for context(plexname)

Explanation: As part of CMAS initialization orCICSplex definition, the Timing Services subcomponentreports the monitor interval that is in effect for thespecified CICSplex. Various CICSPlex SM componentsperform special processing at the end of each monitorinterval, where:

nnnn Is the monitor interval in minutes.

plexnameIdentifies the affected CICSplex.



Module: EYU0CWPR

Destination: EYULOG

EYUCW0108I Time zone offset from GMT computedbased on text

Explanation: As part of CMAS initialization, theTiming Services subcomponent reports how GreenwichMean Time (GMT) was computed from the CPU clock,where text indicates what the computation was basedupon as one of the following:

CMAS time zone attributesThe time zone offset specified in the CMASstartup job was added to or subtracted fromthe CPU store clock value.

TIMEZONE operand in SYS1.PARMLIB(CLOCKxx) orSysplex Timer

The CPU clock was set to GMT, so noadjustment was made.



For a discussion of CICSPlex SM time zone attributes,see the CICSPlex System Manager Administration manual.

Module: EYU0CWIN, EYU0CWMT

Destination: Job log, EYULOG

EYUCW0106I • EYUCW0108I


Chapter 15. EYUHInnn messages

EYUHI001I Processing data set EYUHISTx.

Explanation: A statement has been located in thejobstream for DDName EYUHISTx.

System action: The program continues to open,interrogate and format the data set associated with theEYUHISTIx DD statement.


Module: EYU9XHID

Destination: Console, job log.

EYUHI002I EYUHISTx initialization count is nnnn.

Explanation: The data set associated with theEYUHISTIx DDName has been formatted with nnnninitialization records.

System action: The program continues to process thenext sequential EYUHISTIx data set.


Module: EYU9XHID


EYUHI003W Data set EYUHISTx is alreadyinitialized and is being skipped.

Explanation: The data set associated with theEYUHISTn DDName has been found to be formattedalready.

System action: The program terminates immediately.

User response: Either supply a different data set forthe DDName specified, or delete and redefine the dataset associated with the EYUHISTx DDname.

Module: EYU9XHID


EYUHI004E Data set EYUHISTx is not a history file.Program terminated.

Explanation: The data set associated with theEYUHISTn DDName has been found to contain datawhich is not history records. If a given data set name isto be reused for history recording purposes, it must bedeleted and re-defined beforehand.

System action: The program will terminateimmediately.

User response: Either supply a different data set forthe DDName specified, or delete and re-define the dataset associated with the EYUHISTIx DDname.

Module: EYU9XHID


EYUHI005I Program terminated

Explanation: The program has completed execution.

System action: The program terminates.


Module: EYU9XHID


EYUHI006E Error from xxxxxx request: RPLFeedback is X'0x0x0x0x'

Explanation: A VSAM OPEN, GET, PUT or CLOSErequest has failed. The RPL feedback code is shown.


User response: Determine the reason for the failure bylooking at the RPL feedback code. These aredocumented in the DFSMS/MVS Macro Instructions forData Sets manual.

Module: EYU9XHID


EYUHI007E Error from xxxxx request:R15=X'0x0x0x0x', R0=X'0x0x0x0x'

Explanation: A VSAM GENCB, MODCB or SHOWCBrequest has failed. The request reason and responsecodes from general registers 15 and 0 are shown.


User response: Determine the reason for the failure bylooking at the macro response codes. These aredocumented in the DFSMS/MVS Macro Instructions forData Sets manual.

Module: EYU9XHID



Chapter 16. EYUMMnnnn messages

The following variables are used in EYUMMnnnn messages:

restypeIdentifies the type of resource involved as one of the following:v Allv CICSv Connectionv Data Basev Filev Globalv Journalv Programv Terminalv Transactionv Transient Data Queuev Unknown

contextIdentifies the CICSplex to which the message applies.

scopeIdentifies the CICS systems to which the message applies.

EYUMM0001I Monitor Initialization Complete

Explanation: The CMAS Monitor Services componenthas been successfully initialized. Monitoring is nowenabled.



Module: EYU0MMIN

Destination: EYULOG

EYUMM0002E Monitor Initialization Failed

Explanation: The CMAS Monitor Services componentcould not be initialized.

System action: CMAS initialization continues, butMonitor Services is not available.

User response: Refer to the messages issued beforethis one, to determine the cause of the problem.

Module: EYU0MMIN


EYUMM0071E Monitor MOEB Initialization Failed

Explanation: The CMAS Monitor Services component

was not able to acquire enough storage for its majorobject environment block (MOEB).


User response: Make more storage available to theCMAS by doing one of the following:

v Increase the CICS region size using the REGION=parameter on the EXEC statement.

v Increase the size of the EUDSA.

Module: EYU0MMIN


EYUMM0072E Monitor Data Cache Create Failed

Explanation: The CMAS Monitor Services componentwas not able to allocate the required data cache.

System action: CMAS initialization continues, butMonitor Services is not available. A user trace record iswritten to the CICS trace data set.

User response: Examine the exception trace recordsand any related messages from the Data Cachecomponent (EYUXCnnnn) to determine the cause of theproblem.

Module: EYU0MMIN



EYUMM0073E Monitor List Header InitializationFailed

Explanation: The CMAS Monitor Services componentwas not able to create a required internal work list.


User response: Examine the exception trace records todetermine the cause of the problem.

Module: EYU0MMIN


EYUMM0074E Monitor Cache Attribute TableInitialization Failed

Explanation: The CMAS Monitor Services componentwas not able to load the Resource Descriptor Table,EYUTMMDT.


User response: Make sure the CICSPlex SM loadlibrary contains all distributed modules.

Module: EYU0MMIN


EYUMM0075E Monitor Administration Service TaskStart Failure

Explanation: The CMAS Monitor Services componentwas not able to start its service task, EYU0MMST.



Module: EYU0MMIN


EYUMM0076E Monitor has encountered anunknown event notification (nn) eventignored

Explanation: The CMAS Monitor Services componentreceived an unsolicited event record, where nn is theevent notification ID that was not recognized byMonitor Services. Given the event notification ID, it ispossible to determine which CICSPlex SM methodcreated the event.

System action: Monitor Services ignores the eventrecord and continues processing. The invalid eventrecord is written to the CICS trace data set.


Module: EYU0MMST


EYUMM0077E Monitor Administration Service Taskhas had a failure – Task will beTerminated.

Explanation: The CMAS Monitor Services task hasfailed.

System action: Monitor Services is not able toacknowledge MAS termination. A user trace record iswritten to the CICS trace data set. Monitoring continuesfor those MASs currently being monitored. If a MASthat is being monitored terminates, some MonitorServices resources, such as data cache, may remainallocated.

User response: Restart the affected CMAS. Examinethe exception trace records to determine the cause ofthe problem.

Module: EYU0MMST


EYUMM0079E Monitor was unable to start a restypedata collector task

Explanation: During CMAS initialization, MonitorServices was not able to start the data collector task forthe specified resource type where restype is as describedin the introduction to the EYUMMnnnn messages.

System action: Monitoring of the specified resourcetype is not available for any MAS associated with theCMAS that was initializing. A user trace record iswritten to the CICS trace data set. CMAS initializationcontinues.

User response: Examine the exception trace records todetermine the cause of the problem. Then, if you wantto monitor the specified resource type, stop and restartthe CMAS.

Module: EYU0MCCM


EYUMM0080E Monitor data collector task has failedfor restype resources

Explanation: The data collector task for the specifiedresource type experienced a problem that caused it toterminate where restype is as described in theintroduction to the EYUMMnnnn messages.

System action: Monitor Services attempts to recoverfrom the failure and restart the data collector task.Monitoring of that resource type is not available,however monitoring of other resource types continues.

EYUMM0073E • EYUMM0080E


User response: Examine the exception trace records todetermine the cause of the problem. If the problempersists, collect the trace records and the job log andcontact your IBM Support Center.

Module: EYU0MCCM


EYUMM0081E Monitor data collector task hasterminated due to excessive failures forrestype resources

Explanation: In attempting to recover the datacollector task for the specified resource type, MonitorServices determined that the task had exceeded themaximum allowable number of failures where restype isas described in the introduction to the EYUMMnnnnmessages.

System action: The data collector task is terminatedand monitoring of that resource type is no longeravailable. Monitoring of other resource types continues.

User response: Collect the trace records and the joblog and contact your IBM Support Center.

Module: EYU0MCCM


EYUMM0082W Monitor has reported an errorprocessing event name

Explanation: The Monitor Services long running taskexperienced an internal error while attempting toprocess the specified event, where:

name Identifies the event as one of the following:

v CsysChg

v EndOfPer

v ENetDisc

v MasJoin

v MasStart

v MasStop

v MonSick

v PlexChg

v TimeChg

System action: Monitor event processing continues.However, due to the event failure, some data orinternal structures may be invalid or incomplete. A usertrace record is written to the CICS trace data set.

User response: Make a note of the event name, thencollect the trace records and the job log and contactyour IBM Support Center.

Module: EYU0MMST


EYUMM0300I Monitor resource removal pendingfor restype for Context(context)Scope(scope)

Explanation: Monitoring has been stopped for thespecified resource type in the specified context andscope where restype is as described in the introductionto the EYUMMnnnn messages. Monitor Services waitsfor the defined retention period before continuing withits resource cleanup procedure. The retention period formonitor data is defined as part of either a CICSSYS orMONSPEC definition; for more information, seeCICSPlex System Manager Administration.



Module: EYU0MMIS

Destination: EYULOG

EYUMM0301I Monitor resource removal completefor restype for Context(context)Scope(scope)

Explanation: The retention period for the specifiedresource type in the specified context and scope hasexpired where restype, context, and scope are asdescribed in the introduction to the EYUMMnnnnmessages. Monitor Services has successfully released alloutstanding resources.



Module: EYU0MMKL

Destination: EYULOG

EYUMM0302E Monitor resource removal wasunsuccessful for restype Context(context)Scope(scope)

Explanation: The retention period for the specifiedresource type in the specified context and scope hasexpired where restype, context, and scope are asdescribed in the introduction to the EYUMMnnnnmessages. Monitor Services was not able to release oneor more outstanding resources of the specified type.

System action: Monitor Services continues its resourcecleanup procedures. A user trace record is written tothe CICS trace data set.


Module: EYU0MMKL


EYUMM0081E • EYUMM0302E

Chapter 16. EYUMMnnnn messages 69

EYUMM0303I Monitor resource removal beingforced for Context(context) Scope(scope)

Explanation: A request has been issued to eitherremove a CICSplex or to remove a CICS system from aCICS system group where context and scope are asdescribed in the introduction to the EYUMMnnnnmessages. All monitor resources whose removal waspending in this context and scope (as indicated bymessage EYUMM0300I) are forcibly removed so thatthe CICSplex or CICS system can be removedsuccessfully.



Module: EYU0MPUD

Destination: EYULOG

EYUMM0304W Monitoring has been stopped forrestype resources for Context(context)Scope(scope)

Explanation: As the result of a previous errorcondition, Monitor Services has stopped monitoring thespecified resource type in the specified context andscope where restype, context, and scope are as describedin the introduction to the EYUMMnnnn messages.

System action: Monitor Services begins its resourceremoval processing for the specified resource type, asindicated by message EYUMM0300I. Monitoring ofother resource types continues.

User response: Check the job log for EYUMMnnnnmessages issued previously that relate to the specifiedresource type. Because this message is not issued untilthe end of the monitoring interval, it may be separatedfrom the related error message by as much as thelength of an interval. If you cannot determine the causeof the problem, collect the job log and contact yourIBM Support Center.

Module: EYU0MAUD


EYUMM0400I Monitor resource reset in progress forContext(context) Scope(scope)

Explanation: Monitor Services has begun to reset thecache data fields for the specified context and scope totheir predetermined values where context and scope areas described in the introduction to the EYUMMnnnnmessages. The reset process, which occurs at the end ofeach monitoring performance interval, is done for allresources types currently being monitored.

System action: Reset processing continues.


Module: EYU0MMEI

Destination: EYULOG

EYUMM0401I Monitor resource reset complete forContext(context) Scope(scope)

Explanation: Monitor Services has successfully resetthe cache data fields for the specified context and scopewhere context and scope are as described in theintroduction to the EYUMMnnnn messages.



Module: EYU0MMEI

Destination: EYULOG

EYUMM0402E Monitor resource reset failed forContext(context) Scope(scope)

Explanation: A problem occurred while MonitorServices was attempting to reset the cache data fieldsfor the specified context and scope where context andscope are as described in the introduction to theEYUMMnnnn messages.

System action: Processing continues with the nextmanaged application system (MAS) in the context forwhich monitoring is active. A user trace record iswritten to the CICS trace data set. Partial or incompletemonitoring data may be reported.

User response: Collect the exception trace records andany related messages and contact your IBM SupportCenter.

Module: EYU0MMEI


EYUMM0600I Monitoring type (name) has beensuccessfully installed forContext(context) Scope(scope)

Explanation: A request to install the specifiedmonitoring criteria for the specified context and scopewas successful where context and scope are as describedin the introduction to the EYUMMnnnn messages,where:

type Identifies the type of monitoring criteria thatwas installed as one of the following:

v Definition

v Group

v Specification

v Time Definition

name Is the user-defined name for that criteria.



Module: EYU0MMIC

EYUMM0303I • EYUMM0600I


Destination: EYULOG

EYUMM0602E Monitoring definition (defname) ofGroup (grpname) could not be located,request ignored

Explanation: A request was made against the specifiedmonitor definition in the specified monitor group, butthe definition could not be found in the data repository.


User response: Make sure the definition name wascorrectly specified in the request. If necessary, add thedefinition to the data repository.

Module: EYU0MMIR


EYUMM0603E Unsuccessful start for restypemonitoring for Context(context)Scope(scope)

Explanation: An attempt by Monitor Services to starta monitoring agent in the specified context and scopewas unsuccessful where restype, context, and scope are asdescribed in the introduction to the EYUMMnnnnmessages.

System action: Processing continues, howevermonitoring is not active for the specified resource typein the specified context and scope. A user trace recordis written to the CICS trace data set.


Module: EYU0MMCL


EYUMM0604E Start failed for Monitor End ofTransaction data collector

Explanation: While attempting to install transactionmonitoring definitions, Monitor Services tried to startan end of transaction data collector, but wasunsuccessful.

System action: The installation of the monitordefinitions fails. A user trace record is written to theCICS trace data set.


Module: EYU0MMCL


EYUMM0605E Monitor had nn out of tt type installfailures for Context(context) Scope(scope)

Explanation: During installation of a monitorspecification, group, or definition, tt install requestswere made in the specified context and scope, but nnrequests failed where context and scope are as describedin the introduction to the EYUMMnnnn messages.

type Identifies the type of monitoring criteria thatwas being installed as one of the following:

v Definition

v Group

v Specification

v Time Definition

Prior to this message, an EYUMM0601E message isissued for each install request that failed.

System action: The monitor definition install processcontinues. A user trace record is written to the CICStrace data set.


Module: EYU0MMID


EYUMM0606W Monitor could not install nn restyperesource definition(s) forContext(context) Scope(scope) - reason.

Explanation: During installation of a monitorspecification, group, or definition, a certain number ofdefinitions could not be installed in the specified CICSsystem, where restype, context, and scope are asdescribed in Chapter 16, “EYUMMnnnn messages,” onpage 67, and where:

nn Identifies how many definitions could not beinstalled.

reason Indicates the definitions could not be installedfor one of the following reasons:

A zero sample intervalThe sample interval for the specifiedresource type was zero, which meansno monitor sampling will occur.

Resource not supportedThe specified CICS system does notsupport the specified resource.

System action: The monitor definition install processcontinues. Monitoring of the specified resource type isnot available on the specified CICS system.

User response: Depending on the reason value, do oneof the following:

EYUMM0602E • EYUMM0606W


A zero sample intervalUse the MAS view to set the monitoringsample interval for the specified resource typeto a nonzero value. Then, reinstall the monitordefinitions for that resource type.

Resource not supportedTo prevent this message from appearing thenext time monitor definitions are installed,limit the scope associated with the specifiedresource definitions to CICS systems thatsupport the resource. To determine if aparticular resource is supported by a particularplatform or release of CICS, refer to theCICSPlex System Manager Resource TablesReference Vol 1.

Module: EYU0MMIB


EYUMM0607W Monitor could not install nndefinition(s) for Context(context)Scope(scope) due to Time Period(defname)not being defined.

Explanation: During installation of a monitorspecification, group, or definition, Monitor Servicesattempted to register interest in the specified timeperiod, but the period definition does not exist wherecontext and scope are as described in the introduction tothe EYUMMnnnn messages. The specified number ofdefinitions, which reference the time period, could notbe installed, where:

nn Identifies how many definitions could not beinstalled.

defnameIs the name of the time period definition thatcould not be found.

System action: The monitor definition install processcontinues. Any monitor definitions that reference thespecified time period are not installed.

User response: Make sure the time period name wasspecified correctly on the MONINGRP view. You canuse the PERIODEF view to display a list of existingtime period definitions and, if necessary, create a newone. Then, reinstall the monitor definitions using thecorrect time period name.

Module: EYU0MMIC


EYUMM0903E Monitor Data Cache Delete Failed

Explanation: The CMAS Monitor Services componentwas not able to purge its data cache during terminationprocessing.

System action: Monitor Services terminationcontinues.


Module: EYU0MMTM


EYUMM0904E Monitor MOEB Delete Failed

Explanation: The CMAS Monitor Services componentwas not able to release its major object environmentblock (MOEB) during termination processing.



Module: EYU0MMTM


EYUMM0905E Monitor Termination Failed

Explanation: One or more errors occurred whileattempting to terminate the CMAS Monitor Servicescomponent.



Module: EYU0MMTM


EYUMM0906E Monitor event notificationunregistration Failed

Explanation: An attempt by the CMAS MonitorServices component to unregister interest inCICSPlex SM events was unsuccessful.



Module: EYU0MMTM


EYUMM0999I Monitor Termination Complete

Explanation: The CMAS Monitor Services componenthas been terminated. Resource monitoring is no longeravailable.



EYUMM0607W • EYUMM0999I


Module: EYU0MMTM

Destination: EYULOG


Chapter 17. EYUNLnnnn messages

The following variables are used in EYUNLnnnn messages:

eibrcodeThe EIBRCODE= value as returned by CICS.

respcodeThe RESP= value as returned by CICS.

resp2codeThe RESP2= value as returned by CICS.

Each message that uses these variables identifies the CICS command that returnedthem. For descriptions of the values for a particular CICS command, refer to theCICS/ESA System Programming Reference.

EYUNL0001E MOEB registration failed

Explanation: The MAS subcomponent was not able toregister its major object environment block (MOEB)control block with the Kernel Linkage component.

System action: MAS initialization terminates. A usertrace record is written to the CICS trace data set. TheCICS system continues to run normally, but it is notknown to CICSPlex SM.


Module: EYU0NLRT, EYU1NLRT


EYUNL0002E Termination ECB registration failed

Explanation: The MAS subcomponent was not able toregister its termination ECB with the Kernel Linkagecomponent.



Module: EYU0NLRT


EYUNL0003E GETMAIN for MOEB storage failed

Explanation: The MAS subcomponent was not able toacquire the necessary storage for its major objectenvironment block (MOEB) control block.

System action: MAS initialization terminates. A usertrace record is written to the CICS trace data set. The

CICS system continues to run normally, but it is notknown to CICSPlex SM.


Module: EYU1NLRT


EYUNL0007E Communications Receiver Block notavailable

Explanation: The address of the CommunicationsReceiver Block required for MAS-to-CMAScommunications is zero. MAS-to-CMAScommunications is not available.

System action: MAS processing terminates. A usertrace record is written to the CICS trace data set. TheCICS system continues to run normally, but it is notknown to CICSPlex SM.




EYUNL0010E Parameter Services query failed

Explanation: A request was issued to CICSPlex SMParameter Services and it returned an abnormalresponse.






EYUNL0087E EXEC CICS SET TRANSACTIONrequest for CONA failed

Explanation: Upon discovering a non-zero value forthe MASALTLRTCNT EYUPARM during MAS agentinitialization, EYU0NLRT attempted to set the priorityof the CONA transaction to the value specified in theMASALTLRTPRI EYUPARM, but a non-OK responsewas received.

System action: MAS agent initialization continuesafter the message is issued.

User response: Ensure that the CONA transaction isinstalled in the MAS. If not, upgrade the CSD ifnecessary, install the transaction, and restart the MASagent. If the CONA transaction is installed, collect theauxtrace data sets and the complete job output from theMAS and the CMAS it connects to and contact yourIBM Support Center.

Module: EYU0NLRT


EYUNL0088I (a ) alternate LRTs were requested and (b) were started

Explanation: During MAS agent initialization,EYU0NLRT running under the CONL task will issuethis message after starting CONA tasks if theMASALTLRTCNT EYUPARM is non-zero, where:

a Is the number of CONA tasks that wereattempted to be started (the value of theMASALTLRTCNT parm).

b Is the actual number of tasks that EYU0NLRTsuccessfully started.

System action: MAS agent initialization continuesafter the message is issued.

User response: If a equals b, no action is required,unless a change is required for the number of tasksstarted. If a does not equal b, collect the auxtrace datasets and the complete job output from the MAS and theCMAS it connects to and contact your IBM SupportCenter.

Module: EYU0NLRT


EYUNL0089I Alternate LRT is performing messageprocessing

Explanation: This message is issued when the firstalternate long running task in a MAS processes arequest.

System action: MAS processing continues after themessage is issued.

User response: No action is required unless alternatelong running task processing is not desired in the MAS,in which case set EYUPARM MASALTLRTCNT to 0(zero) and restart the MAS agent.

Normally the absence of this message, when theEYUNL0088I message indicates that at least onealternate LRT was started, indicates that a problemexists. Verify that the CONA transaction is defined tosecurity and that the userid used to start the MAS hasauthority to start the transaction. If security is not anissue, collect the auxtrace data sets and the completejob output from the MAS and the CMAS it connects toand contact your IBM Support Center.

Module: EYU0NLRA


EYUNL0090W addspace is shutting down because itfailed to become available to processrequests

Explanation: After initialization completed, themanaged application system (MAS) determined thatthe heartbeat task was not active and initiated a normalshutdown, where:

addspaceIdentifies the MAS as a local MAS (LMAS).

System action: The CICS system continues to runnormally, but it is not known to CICSPlex SM.

User response: Check the CMAS EYULOG for anyrelated messages and follow the instructions providedfor those messages. The MAS can be restarted with theCOLM transaction. If the problem persists, collect thetrace records and the CMAS EYULOG and contact yourIBM Support Center.

Module: EYU0NLRT


EYUNL0096E Alternate LRT (n ) is terminatingabnormally

Explanation: This message is issued when thealternate long running task terminates with an error,where:

n Is the number of the CONA task that isterminating.


User response: Check for any previous messages inthe log that may indicate why the alternate longrunning task terminated abnormally, referring to thedocumentation for those messages. If no othermessages exist, collect the auxtrace data sets and thecomplete job output from the MAS and the CMAS itconnects to and contact your IBM Support Center.

EYUNL0087E • EYUNL0096E


Module: EYU0NLRA


EYUNL0098E addspace LRT initialization failed

Explanation: The long running task (LRT) for a MAScould not be initialized, where:

addspaceIdentifies the MAS as a local (LMAS).

System action: MAS initialization terminates. TheCICS system continues to run normally, but it is notknown to CICSPlex SM.

User response: Refer to the messages preceding thisone for details on the cause of the problem.


Destination: Console, job log, EYULOG,

EYUNL0099I addspace LRT initialization complete

Explanation: The long running task (LRT) for a MAShas been successfully initialized, where:

addspaceIdentifies the MAS as a local MAS (LMAS) ora single server region (SMSS).

System action: The MAS is ready for work.CICSPlex SM processing continues.

User response: None



EYUNL0101W Method not supported: Format ID=id

Explanation: Another component of CICSPlex SMmade a request that is not supported by the MASsubcomponent, where:

id Is the request identifier.

System action: The request is ignored. MASprocessing continues.


Module: EYU0NLRT


EYUNL0103E WAIT EXTERNAL failed,RESP=respcode RESP2=resp2code

Explanation: An EXEC CICS WAIT EXTERNALcommand returned an abnormal response. The respcodeand resp2code values are as returned by CICS.

System action: The MAS attempts a normalshutdown. A user trace record is written to the CICStrace data set.

User response: Follow the instructions associated withthe respcode and resp2code values for the EXEC CICSWAIT EXTERNAL command.

Module: EYU0NLRT, EYU0NLRA


EYUNL0105E Lock Services failed. Messageprocessing is inoperative.

Explanation: An error occurred in the Lock Servicessubcomponent while retrieving a message to beprocessed by the MAS. The MAS can no longer processCICSPlex SM requests.

System action: MAS processing terminates. A usertrace record is written to the CICS trace data set. TheCICS system continues to run normally, but it is notknown to CICSPlex SM.


Module: EYU0NLRT, EYU0NLRA


EYUNL0120W ENABLE PROGRAM prgmid failed,RESP=respcode EIBRCODE=eibrcode

Explanation: A program required by the MASsubcomponent could not be enabled, where:

prgmid Identifies the program that could not beenabled as one of the following:

v EYU9NLDC

v EYU9NLDR

v EYU9NLID

v EYU9NLME

v EYU9NMST

v EYU9NMTE

v EYU9XLAP

respcodeValue is as returned by CICS.

eibrcodeValue is as returned by CICS.

System action: The impact on system processingdepends on which program could not be enabled:

EYU9NLDCThe XDUREQC Dump Domain exit is notavailable. MAS processing continues.Transaction dump completion will be detectedby the XDUOUT exit. System dumpcompletion will be detected by the heartbeattask.

EYU9NLDRThe XDUREQ Dump Domain exit is notavailable. MAS processing continues, but

EYUNL0098E • EYUNL0120W

Chapter 17. EYUNLnnnn messages 77

transaction dump and system dump (sickhealth) notifications are not issued.

EYU9NLIDThe XRSINDI exit is not available. MASprocessing continues, but topology changes arenot communicated to the CMAS.

EYU9NLMEThe XMEOUT Message Domain exit is notavailable. MAS processing continues, buttopology changes are not communicated to theCMAS.

EYU9NMSTThe XMNOUT Monitoring Domain exit is notavailable. MAS processing continues, butend-of-task monitoring data are not collected.

EYU9NMTEThe XSTOUT Statistics Domain exit is notavailable. MAS processing continues, butmonitoring statistics data are lost.

EYU9XLAPThe CICSPlex SM API is not available. MASprocessing continues, but the MAS cannot beaccessed by API programs.

In all cases, a user trace record is written to the CICStrace data set.

User response: Follow the instructions associated withthe respcode and eibrcode values for the EXEC CICSENABLE command. Then, depending on whichprogram could not be enabled, do one of the following:

EYU9NLDR, EYU9NLID, EYU9NLME, EYU9NMST, orEYU9XLAP

Stop the MAS by issuing the STO actioncommand from the MAS view. Then restartthe MAS by issuing the COLM (for a localMAS) transaction from CICS; thesetransactions restart the CICSPlex SM MASagent code in a running CICS system.

EYU9NMTEStop and restart CICSPlex SM transactionmonitoring by using the CICSSYS view toupdate the CICS system definition. Specify asample rate of zero to stop transactionmonitoring; change the sample rate back to anonzero value to restart transactionmonitoring.

Module: EYU0NLGT, EYU0NLHD, EYU0NLRA,EYU0NLRT, EYU0NMMC


EYUNL0123W DISABLE PROGRAM prgmid failed,RESP=respcode EIBRCODE=eibrcode

Explanation: A program used by the MASsubcomponent could not be disabled, where:

prgmid Identifies the program that could not bedisabled as one of the following:

v EYU9NLDR

v EYU9NLID

v EYU9NLME

v EYU9NMST

v EYU9NMTE

v EYU9XLAP


eibrcodeValue is as returned by CICS.

System action: MAS processing continues. A usertrace record is written to the CICS trace data set.

User response: Follow the instructions associated withthe respcode and eibrcode values for the EXEC CICSDISABLE command.

Module: EYU0NLHD, EYU0NLRA, EYU0NLRT,EYU0NMMC


EYUNL0130W addspace heartbeat terminated. Retrylimit reached.

Explanation: The MAS heartbeat task, which issuesnotification events to the CICSPlex SM address space(CMAS) at regular intervals, terminated abnormally.The heartbeat task can not be restarted because theabnormal condition has occurred the maximum numberof times allowed by CICSPlex SM, where:


System action: The heartbeat task for the specifiedMAS is not restarted. MAS processing continues andthe CICS system is unaffected. User trace records arewritten to the CICS trace data set. If the heartbeat taskabended, a transaction dump is written to the CICSdump data set.

User response: Collect the trace records and thetransaction dump, if available, and contact your IBMSupport Center.



EYUNL0131W addspace heartbeat terminated. Beingrestarted.

Explanation: The MAS heartbeat task, which issuesnotification events to the CICSPlex SM address space(CMAS) at regular intervals, terminated abnormallyand is being restarted, where:

EYUNL0123W • EYUNL0131W



System action: The heartbeat task for the specifiedMAS is automatically restarted.




EYUNL0140W restype monitoring terminated. Retrylimit reached.

Explanation: Monitoring of the specified resourceterminated abnormally and can not be restartedbecause the abnormal condition has occurred themaximum number of times allowed by CICSPlex SM,where:

restype Identifies the type of resource for whichmonitoring terminated as one of the following:

HTASKCompleted task

MCICSCICS systems

MCONNConnections and modenames

MDBX DB2® and DBCTL resources

MFILE Files

MGLBLGlobal resources

MJRNLJournals

MPROGPrograms

MTDQSTransient data queues

MTERMTerminals

MTRANTransactions

System action: The monitoring task for the specifiedresource is not restarted. MAS processing, includingother monitoring tasks, continues. User trace recordsare written to the CICS trace data set. If the monitoringtask abended, a transaction dump is written to theCICS dump data set.

User response: Use the MONDEF view to reinstall themonitor definitions for the specified resource. If thecondition persists, collect the trace records and thetransaction dump, if available, and contact your IBMSupport Center.



EYUNL0141W restype monitoring terminated. Beingrestarted.

Explanation: Monitoring of the specified resourceterminated abnormally and is being restarted, where:

restype Identifies the type of resource for whichmonitoring terminated as one of the following:

HTASKCompleted task

MCICSCICS systems

MCONNConnections and modenames

MDBX DB2 and DBCTL resources

MFILE Files

MGLBLGlobal resources

MJRNLJournals

MPROGPrograms

MTDQSTransient data queues

MTERMTerminals

MTRANTransactions

System action: The monitoring task for the specifiedresource is automatically restarted.




EYUNL0142W MDBX monitoring terminated. DB2release level not supported.

Explanation: Monitoring of DB2 resources wasrequested, but is not available for the specified releaseof DB2.

System action: The monitoring task for DB2 (MDBX)is terminated. MAS processing, including themonitoring of other resources, continues.

User response: Review the installation requirementsfor a list of the DB2 releases supported byCICSPlex SM. If a supported release of DB2 becomesavailable and you want to monitor its resources, youmust restart monitoring for the DB2 resource class.

Module: EYU0NM2T




EYUNL0143W MTRAN monitoring data incomplete- CICS Monitor data reason

Explanation: Some or all MTRAN monitoring data isunavailable because CICSPlex SM was not able toprocess CICS monitor data at exit point XMNOUT,where:

reason Identifies the reason why CICS monitor datacould not be processed:

missingThe work area for dictionary datawas too small. All performance datawill be discarded.

truncatedThe buffers used to pass performancedata to the CICSPlex SM monitorcomponent were too small.Performance records will betruncated.

System action: CICSPlex SM monitoring of MTRANresources continues but some or all performance dataprovided by the CICS monitor domain will be missing.Data provided by CICS statistics domain will becollected and reported at monitor sample intervals.

User response: Collect AUXTRACE records and MASand CMAS job logs and contact your IBM SupportCenter.

Module: EYU0NMMC

Destination: Console, job log, CMAS EYULOG

EYUNL0148W Warning - active MAS tasks forcepurged during addspace termination

Explanation: During termination of a MAS, one ormore MAS tasks could not be properly terminated;instead, the tasks were forcibly purged from the CICSsystem, where:


System action: MAS termination continues. A series oftask abend messages (EYUXL09nn) is written to theconsole for each task that was purged. This message isalso accompanied by message EYUNL0149I. After allactive tasks are forcibly purged, the MAS waits up toone minute for the tasks to terminate completely. MAStermination then continues and storage areas are freed.The disposition of any task remaining active isunpredictable.

User response: If the condition persists, collect thetrace records and the job log and contact your IBMSupport Center.



EYUNL0149I Active MAS tasks being terminated byLRT for addspace termination

Explanation: All active MAS tasks are beingterminated as a result of a MAS termination, where:


System action: Termination ECB are posted for allactive MAS tasks. The MAS waits one minute for thetasks to terminate, then continues its terminationprocess.




EYUNL0150W Get Topology for resource restypefailed, COMMAND=cmdnameRESP=respcode RESP2=resp2code

Explanation: Topology data collection for the specifiedresource failed during the execution of an EXEC CICScommand, where:

restype Identifies the type of resource for which datacollection failed as one of the following:

v ATOMSERVICE

v AUTINSTMODEL

v BUNDLE

v CAPTURE SPEC

v CAPTURE SPEC OPT PRED

v CAPTURE SPEC DATA PRED

v CAPTURE SPEC INFO PRED

v CFDT POOL

v CONNECTION

v DATA SET NAMES

v DB2 CONNECTION

v DB2 ENTRY

v DB2 TRANSACTION

v ENQUEUE MODEL

v EVENT BINDING

v EVENT PROCESSING ADAPTER

v FEPI CONNECTIONS

v FEPI NODE

v FEPI POOL

v FEPI TARGET

v FILE

v GLOBAL EXITS

v IP CONNECTION

v JOURNAL



|

|

|

|

v JOURNALNAMES

v JVM SERVER

v LIBRARY

v MODENAME

v PARTNER

v PIPELINE

v PROCESS TYPE

v PROFILE

v PROGRAM

v REQUEST MODEL

v SYSTEM DUMP CODES

v TASK EXITS

v TCP/IP SERVICE

v TDQUEUE

v TEMP STORAGE MODEL

v TERMINAL

v TRANCLASS

v TRANSACTION DUMP CODES

v TRANSACTION

v URIMAP

v WEB SERVICE

v XML TRANSFORM

cmdnameIdentifies the EXEC CICS command that wasbeing issued as either START or NEXT.


resp2codeValue is as returned by CICS.

System action: Topology data collection continueswith the next resource.

User response: Follow the instructions associated withthe respcode and resp2code values for the specified EXECCICS command. To resume topology data collection forthe specified resource, first stop the MAS by issuing theSTO action command from the MAS view. Then restartthe MAS by issuing the COLM (for a local MAS) orCORM transaction from CICS; these transactions restartthe CICSPlex SM MAS agent code in a running CICSsystem.

Module: EYU0NLGT, EYU1NLGT


EYUNL0151I Get Topology for resource restype haszero data records

Explanation: Topology data collection for the specifiedresource returned no data. Either no data was available,or a problem occurred during the data collectionprocess, where:

restype Identifies the type of resource for which nodata was returned as one of the following:

v ATOMSERVICE

v AUTINSTMODEL

v BUNDLE

v CAPTURE SPEC




v CFDT POOL

v CONNECTION

v DATA SET NAMES

v DB2 CONNECTION

v DB2 ENTRY

v DB2 TRANSACTION

v ENQUEUE MODEL

v EVENT BINDING


v FEPI CONNECTIONS

v FEPI NODE

v FEPI POOL

v FEPI TARGET

v FILE

v GLOBAL EXITS

v IP CONNECTION

v JOURNAL

v JOURNALNAMES

v JVM SERVER

v LIBRARY

v MODENAME

v PARTNER

v PIPELINE

v PROCESS TYPE

v PROFILE

v PROGRAM

v REQUEST MODEL

v SYSTEM DUMP CODES

v TASK EXITS

v TCP/IP SERVICE

v TDQUEUE


v TERMINAL

v TRANCLASS


v TRANSACTION

v URIMAP

v WEB SERVICE

v XML TRANSFORM

EYUNL0151I


|

|

|

|

System action: Topology data collection continueswith the next resource.

User response: If no topology data was expected forthe specified resource, no action is required.

If topology data was expected, a problem may haveoccurred during data collection. In that case, thismessage is preceded by one of two messages, eitherEYUNL0150W or EYUNL0153W. Refer to theappropriate message for details on the cause of theproblem.


Destination: EYULOG

EYUNL0153W Get Topology for resource restype isincomplete

Explanation: Topology data collection for the specifiedresource failed before it could be completed, where:

restype Identifies the type of resource for which datacollection was incomplete as one of thefollowing:

v ATOMSERVICE

v AUTINSTMODEL

v BUNDLE

v CAPTURE SPEC




v CFDT POOL

v CONNECTION

v DATA SET NAMES

v DB2 CONNECTION

v DB2 ENTRY

v DB2 TRANSACTION

v ENQUEUE MODEL

v EVENT BINDING


v FEPI CONNECTIONS

v FEPI NODE

v FEPI POOL

v FEPI TARGET

v FILE

v GLOBAL EXITS

v IP CONNECTION

v JOURNAL

v JOURNALNAMES

v JVM SERVER

v LIBRARY

v MODENAME

v PARTNER

v PIPELINE

v PROCESS TYPE

v PROFILE

v PROGRAM

v REQUEST MODEL

v SYSTEM DUMP CODES

v TASK EXITS

v TCP/IP SERVICE

v TDQUEUE


v TERMINAL

v TRANCLASS


v TRANSACTION

v URIMAP

v WEB SERVICE

v XML TRANSFORM

System action: Topology data collection continueswith the next resource. A user trace record is written tothe CICS trace data set.

User response: Check for one of two messages thatmay have preceded this one:

EYUNL0150WA problem occurred with an EXEC CICScommand.

EYUTS0021EThe request for MAS topology timed out.

Refer to the appropriate message for details on thecause of the problem. If the condition persists, collectthe trace records and the job log and contact your IBMSupport Center.



EYUNL0159I Resource topology data retrievalcomplete

Explanation: The collection of resource topology databy the MAS is complete. This message does notnecessarily indicate that the data collection process wassuccessful. If any problems occurred during datacollection, they would be described in EYUNLnnnn orEYUTSnnnn messages issued before this one.

System action: MAS topology processing is completeand the MAS is ready for work.



Destination: EYULOG

EYULOG,

EYUNL0153W • EYUNL0159I


|

|

|

|

EYUNL0160I Workload registration complete

Explanation: The region has been joined to theworkload.



Module: EYU0NLSP

Destination: EYULOG

EYUNL0161E Resource topology data retrieval failed

Explanation: During topology connect, an error hasoccurred during resource topology data retrieval in theMAS.

System action: Topology connect fails and the MASagent is terminated.

User response: Check for any previous messages inthe MAS job log that may indicate why the problemoccurred. If the problem cannot be determined, collectthe complete job output and auxtrace data sets from theMAS and the CMAS to which it was connecting, andany dumps that might have occurred in the MAS orCMAS, and contact your local IBM Support Center.

Module: EYU0NLGT


EYUNL0170I Task History Recorder has beenactivated

Explanation: The history recorder long running taskhas been successfully initialized.

System action: CICSPlex SM processing continues.The task history recorder task is ready to accept detailsof completed CICS transactions.


Module: EYU0NHCT


EYUNL0171I Task History Recorder has beenterminated

Explanation: The history recorder long running taskhas been terminated.

System action: CICSPlex SM processing continues. Nofurther task history recording will take place.

User response: If termination of history recording isnot expected examine earlier messages to determinewhy the history recorder terminated.

Module: EYU0NHCT


EYUNL0172E An abend has occurred within TaskHistory Recorder

Explanation: The history recorder long running taskhas detected an abend.

System action: The history recorder task willterminate and then attempt to restart. CICSPlex SMprocessing continues.

User response: Check for previous messages toidentify the cause of the abend or error that caused thehistory recorder to terminate. If you cannot determinethe cause of the problem, collect the complete job logfrom the MAS, any dumps that may have beencaptured, the complete CMAS job log or EYULOG, andCMAS auxiliary trace data sets and contact your IBMsupport center.

Module: EYU0NHCT


EYUNL0173I Task History Recorder has switched datasets from x to y

Explanation: The long running task history recordertask in attempting to record a completed task on VSAMdata set EYUHISTx found that the data set was full,and so has switched to start using data set EYUHISTy.

System action: Task history recorder continues usingdata set EYUHISTy. The full data set EYUHISTxremains open and its data is available until such timethat the history recorder has filled all data sets andrequires use of EYUHISTx again. At this timeEYUHISTx will be set closed, emptied and reopened,thereby destroying its previous contents.


Module: EYU0NHCT


EYUNL0174E Error Returned from XXXXXXcommand to data setEYUHISTx,RESP=nnnnnnnnRESP2=nnnnnnnn

Explanation: The long running task history recordertask issued a CICS file control command or CICS SPIcommand against the specified history data set andreceived a bad response.

System action: History recording terminates.

User response: Examine the RESP and RESP2 valuesreturned for the CICS command to identify theproblem. If you cannot determine the cause of theproblem, collect the complete job log from the MAS,any dumps that may have been captured, the completeCMAS job log or EYULOG and CMAS auxiliary tracedata sets and contact your IBM support center.

Module: EYU0NHCT

EYUNL0160I • EYUNL0174E



EYUNL0175W Concurrent iteration of Task HistoryRecorder

Explanation: During initialization, the long runningtask history recorder task has detected that there wasalready an instance of the history recorder task active.

System action: This instance of the history recordertask is terminated.


Module: EYU0NHCT


EYUNL0176W No History Datasets available

Explanation: During initialization, the long runningtask history recorder task detected problems meaningthat there no are history data sets available for it torecord to.

System action: The history recorder task is not started.

User response: If you are sure that history recordingwill not be required on the local CICS region, thismessage is simply a confirmation that the historyrecorder process will not be startable. If you anticipatethat task history recording will be required at somepoint during the execution of the current CICS region,you must ensure that the history data sets have beenallocated to the local MAS region by means of DDcards. If allocated correctly, examine earlier messages todetermine the problem. If you cannot determine thecause of the problem, collect the complete job log fromthe MAS, any dumps that may have been captured, thecomplete CMAS job log or EYULOG and CMASauxiliary trace data sets and contact your IBM supportcenter.

Module: EYU0NHCT


EYUNL0177W HISTDBUFFS EYUPARM is toosmall, and has been increased to nnnnn

Explanation: The CICS definitions for the history datasets are created automatically during the initializationof the history recorder task. During this process, theprogram has determined that the default setting for theDATABUFFS parameter of the EXEC CICS CREATE forthe data set in question has been overridden with aninvalid value. As such, the DATABUFFS value has beenreset to that shown in this message.

System action: CICS file creation for the history datasets continues using the value shown.

User response: Re-adjust the HISTDBUFFS EYUPARMto an acceptable numeric value that is at least 1 greaterthan the HISTIBUFFS specification.

Module: EYU0NHFM


EYUNL0178E Task History Recorder unable toinitialize EYUHISTx

Explanation: The MAS history file manager detectedproblems meaning that it was unable to initialize thenamed history data set with its control information.

System action: The named history data set is markedunuseable. The history recorder task is terminated.

User response: Examine earlier messages to determinethe problem. If you cannot determine the cause of theproblem, collect the complete job log from the MAS,any dumps that may have been captured, the completeCMAS job log or EYULOG and CMAS auxiliary tracedata sets and contact your IBM support center.

Module: EYU0NHFM


EYUNL0179I Task History Recorder datasetEYUHISTx has accrued nnnn records

Explanation: Informational message detailing howmany records have been written by the history recorderlong running task to the named history data set. Thedisplay frequency of this message is controlled by theHISTRECSMSG EYUPARM.

System action: Task history recording continues.


Module: EYU0NHCT


EYUNL0181E Invalid number of History data sets

Explanation: The history file manager detected aninvalid number of history data sets (EYUHISTx). Atleast two history data sets (EYUHISTA and EYUHISTB)must be allocated to the MAS.

System action: History recording is not activated.

User response: Ensure that at least two history datasets have been allocated and that DD statements(EYUHISTA, EYUHISTB and so on in sequence) havebeen supplied for the data sets in the MAS JCL.

Module: EYU0NHFM


EYUNL0182W No History buckets available, nnnrecords dropped

Explanation: Completed task history data is passed tothe history recorder via a service queue that is loadedby the CPSM Monitor Data Global User Exit. This exitprogram places tasks data in pre-allocated data slots, or



"buckets", to transport the completed task detail to thehistory long running task. When trying to acquire afree bucket to use for the current completed task detail,the GLUE has determined that there are no bucketsavailable for use.

System action: The Glue drops the current completedtask datum, and increments a count of droppedrecords. When the history recorder completes the filingof it's outstanding data queue, it reports this droppedrecord count, and resets the counter to zero.

User response: It is possible that this message may beissued occasionally during peaks of transactionprocessing on the local MAS. As such, it will benecessary to retune the settings of the controllingparameters of the history recorder to accommodatethese processing peaks. This should be performed onlyunder the advice and guidance of qualified CICSservice personnel. Please contact you IBM supportcenter to seek advice.

Module: EYU0NHCT


EYUNL0183W No History Exit Workarea available,nnn records dropped

Explanation: Completed task history data is passed tothe history ecorder via a service queue that is loadedby the CPSM Monitor Data Global User Exit. This exitprogram places tasks data in pre-allocated data slots, or"buckets", to transport the completed task detail to thehistory long running task. These buckets reside in acontiguous exit workarea within the MAS dataspacethat is allocated by an asynchronous process controlledby the CMAS. When trying to acquire a free bucket (touse for the current completed task detail) the GLUE hasdetermined that the controlling process has notcompleted the allocation of this exit workarea, and sono buckets are currently available for use.

System action: The Glue drops the current completedtask datum, and increments a count of droppedrecords. When the history recorder completes the filingof it's outstanding data queue, it reports this droppedrecord count, and resets the counter to zero.

User response: It is possible that on a busy MAS, thiscondition may be reported because the GLUE will begathering task data before the history recorderenvironment has completed initialization. If thiscondition is reported during regular transactionprocessing within the MAS, this indicates a moreserious problem. Therefore, collect the complete job logfrom the MAS, any dumps that may have beencaptured, the complete CMAS job log or EYULOG andCMAS auxiliary trace data sets and contact your IBMsupport center.

Module: EYU0NHCT


EYUNL0184E Invalid Attribute for History FileEYUHISTx:

Explanation: The MAS history file manager detectedinvalid attributes for the named history file. Thismessage is followed by message EYUNL0185E whichgives details of the invalid attribute.

System action: The history recorder long running taskis terminated.

User response: Use the following EYUNL0185message to determine which file attribute is invalid.

Module: EYU0NHFM


EYUNL0185E Keyword: xxxxxxxxx Expectedvalue:nnn Returned value:nnn

Explanation: This message is output in conjunctionwith message EYUNL0184E and gives details of aninvalid attribute for a history file. The expected valueand value detected are returned in the form of CICSCVDA values.

System action: CICSPlex SM processing continues.

User response: Use the information in the message tocorrect the history file attribute.

Module: EYU0NHFM


EYUNL0186I Task History Recorder has begun datacollection.

Explanation: The history recorder long running taskhas started receiving and storing completed task data.Prior to the display of this message, the historyrecorder was in a waiting state ready to process taskdata. This message indicates that the first completedtask datum has been received and appropriatelyprocessed.

System action: CICSPlex SM processing continues.The task history recorder task will continue to acceptand process details of completed CICS transactions.


Module: EYU0NHCT


EYUNL0901I addspace LRT NORMAL terminationinitiated

Explanation: The long running task (LRT) for a MASis being terminated because the CICS system it isassociated with is being terminated, where:


EYUNL0183W • EYUNL0901I


System action: Termination of the MAS continues.




EYUNL0902I addspace LRT CMAS Requestedtermination initiated

Explanation: The long running task (LRT) for a MASis being terminated as a result of a request from theCMAS that controls it, where:


System action: Termination of the MAS continues. TheCICS system continues to run normally, but it is nolonger known to CICSPlex SM.




EYUNL0903E addspace LRT Abnormal terminationinitiated

Explanation: The long running task (LRT) for a MASis being terminated as a result of an error or abend inthe LRT, where:


System action: Termination of the MAS is attempted.

User response: Check for previous messages toidentify the cause of the abend or error that caused theLRT to terminate. If you cannot determine the cause ofthe problem, collect the complete joblog from the MAS,any dumps that may have been captured, the completeCMAS Joblog / EYULOG and CMAS auxillary tracedata sets and contact your IBM support center.

Module: EYU0NLRT


EYUNL0904E LRT Abnormal termination failed

Explanation: An attempt to abnormally terminate thelong running task (LRT) for a MAS has failed.

System action: The MAS agent LRT completes butsome MAS agent components may remain active. TheMAS agent will not be able to be restarted in this CICSexecution.

User response: See the User Response for message“EYUNL0903E,” which should precede this message.You need to restart the CICS region before the MASagent can reconnect.

Module: EYU0NLRT


EYUNL0906E The CMAS has initiated a shutdown ofthe MAS agent. See the CMAS job logfor additional information.

Explanation: An attempt was made to initialize theMAS agent in a CICS system but the request has failed.

System action: Processing continues, but the CICSsystem cannot be managed by CICSPlex SM.

User response: Check the job log of the CMAS formessages that might indicate the cause of the problem.If you cannot determine the cause of the problem byreading the messages in the log, collect the exceptiontrace records, CMAS and MAS job logs, and contactyour IBM Support Center.

Module: EYU0NLSD


EYUNL0910I Alternate LRT (n ) is terminatingnormally

Explanation: This message is issued when thealternate long running task terminates normally, where:

n Is the number of the CONA task that isterminating.


User response: No action is required.

Module: EYU0NLRA


EYUNL0911I date time applid Number of activealternate LRTs : n.

Explanation: No explanation available.



Module: Module unknown.

Message inserts:

1. date

2. time

3. applid

4. n

Destination: Console and COLG.

EYUNL0902I • EYUNL0911I


EYUNL0912I date time applid Maximum concurrentlybusy alternate LRTs : n.





Message inserts:

1. date

2. time

3. applid

4. n


EYUNL0913I date time applid Number of times allalternate LRTs were busy : n.





Message inserts:

1. date

2. time

3. applid

4. n


EYUNL0999I addspace LRT termination complete

Explanation: The long running task (LRT) for a MAShas been terminated, where:


System action: The MAS subcomponent is removedfrom the CICS system. The CICS system eitherterminates or continues to run, as indicated by themessage that precedes this one (either EYUNL0901I orEYUNL0902I).




EYUNL0912I • EYUNL0999I


Chapter 18. EYUNXnnnn messages

The following variables are used in EYUNXnnnn messages:

eibrcodeThe EIBRCODE= value as returned by CICS.

respcodeThe RESP= value as returned by CICS.

resp2codeThe RESP2= value as returned by CICS.

Each message that uses these variables identifies the CICS command that returnedthem. For descriptions of the values for a particular CICS command, refer to theCICS System Programming Reference.

EYUNX0001I addspace initialization program starting

Explanation: The initialization program for a MAS isbeing started, where:


System action: CICS passes control to the MAS or aninitialization program and processing continues.


Module: EYU9NXSM

Module: EYU9NXSM, EYU1NXRM


EYUNX0010E addspace1 agent startup failed becauseregion was an addspace2

Explanation: The request to start the addspace1 agentin the CICS failed because the addspace2 agent haspreviously run in this CICS execution. To changeaddspace agent types, the CICS region must berestarted.

addspace1 and addspace2 refer to LMAS for a local MASor SMSS for a single server.

System action: A system dump is taken with a dumpcode of EYUN and control returns to CICS. The CICSregion continues to initialize, but it is not known toCICSPlex SM and single server processing is notavailable.

User response: If addspace2 is the appropriate agent,use the COLM (LMAS) or CORM (SMSS) transactionsto restart the appropriate agent.

If addspace1 is the appropriate agent, restart the CICSregion and ensure that the addspace1 agent is initialized.

Module: EYU9NXSM


EYUNX0011W The definition for{PROFILE|PROGRAM|TRANSACTION|TDQUEUE} resourcename has beenreplaced

Explanation: The initialization program for a MAS hasreplaced an invalid definition for the CICSPlex SMresource resourcename. Previous message EYUNX0013Egives details of the invalid definition options.

System action: MAS initialization continues.

User response: None

Module: EYU9NXLM

Destination: Console

EYUNX0012E addspace initialization failed

Explanation: Initialization of a MAS failed in thePLTPI program, where:


System action: Control returns to CICS. The CICSsystem continues to initialize, but it is not known toCICSPlex SM.



Destination: Console, job log, terminal user

EYUNX0013E {PROFILE|PROGRAM|TRANSACTION|TDQUEUE} resourcename has invalidvalue: xxxxxxxx for option: yyyyyyyyy


Explanation: The initialization program for a MASdetected an invalid definition option for the CICSPlexSM resource resourcename

System action: CICSPlex SM takes one of thefollowing actions based on whether the invaliddefinition is a critical or non-critical definition. Forexample, the CODB transaction is a non-criticaltransaction, and the MAS agent can fully functionwithout it.

v Critical: CICSPlex SM attempts to replace thedefinition with the default definition for the resource.If successful, it issues message EYUNX0011W. If thereplacement fails it issues message EYUNX0014E andterminates MAS initialization.

v Non-critical: CICSPlex SM issues messageEYUNX0013E to identify the invalid definition,CICSPlex SM takes no further action and the MASagent continues the initialization processing.

User response: Review your GRPLIST SIT parameterto determine the source of the invalid definition.

Module: EYU9NXLM


EYUNX0014E The{PROFILE|PROGRAM|TRANSACTION|TDQUEUE} definition for resourcenameis invalid. MAS initialization isterminating

Explanation: The initialization program for a MASwas unable to replace an invalid definition for theCICSPlex SM resource resourcename. Previous messageEYUNX0013E gives details of the invalid definitionoptions.


User response: Review the definition within the grouplist you use when starting the MAS. Change the invalidoptions before reinstalling the definition and restartingthe MAS using the COLM transaction. The defaultoptions are shown in the sample EYUúMDEF.

Module: EYU9NXLM


EYUNX0015E addspace initialization transaction notfound

Explanation: The initialization transaction used on theEXEC CICS START command for a MAS is not definedto the CICS system, where:


System action: MAS initialization terminates andcontrol returns to CICS. The CICS system continues toinitialize, but it is not known to CICSPlex SM.

User response: Make sure the transaction andprogram for the MAS long running task (LRT) aredefined in the CSD for this CICS system. Thetransaction is CONL; the program is EYU9XLEV.



EYUNX0016E addspace initialization programabended

Explanation: The initialization program for a MASterminated abnormally, where:

addspaceIdentifies the MAS as a local (LMAS) or asingle server region (SMSS).

System action: A system dump is taken with a dumpcode of EYUN and control returns to CICS. The CICSsystem continues to initialize, but it is not known toCICSPlex SM.




EYUNX0017E addspace initialization program - CICSerror

Explanation: The initialization program for a MASterminated abnormally due to a CICS error.

System action: Control returns to the CICS HANDLEABEND routine. A system dump is taken with thedump code assigned by CICS. The CICS systemcontinues to initialize, but it is not known toCICSPlex SM.

User response: Collect the dump and contact yourIBM Support Center.



EYUNX0018E Enable Program prgmid failed,EIBRCODE=code

Explanation: An EXEC CICS ENABLE command wasissued to enable the specified program, and it returnedan abnormal response, where:

prgmid Identifies the program that could not beenabled.

code Value is as returned by CICS.


User response: Follow the instructions associated with

EYUNX0014E • EYUNX0018E


the EIBRCODE= value for the EXEC CICS ENABLEPROGRAM command. If the problem persists, collectthe dump and contact your IBM Support Center.

Module: EYU9NXSM


EYUNX0019E Extract Exit prgmid failed,EIBRCODE=code

Explanation: An EXEC CICS EXTRACT EXITcommand was issued to obtain the global work areaaddress for the specified program, and it returned anabnormal response. prgmid identifies the program forwhich an address was requested. The EIBRCODE=value is as returned by CICS.


User response: Follow the instructions associated withthe EIBRCODE= value for the EXEC CICS EXTRACTEXIT command. If the problem persists, collect thedump and contact your IBM Support Center.

Module: EYU9NXSM, EYU9NXSD


EYUNX0020E START failed: RESP=respcodeRESP2=resp2code

Explanation: An EXEC CICS START command wasissued to start the MAS long running task (LRT), and itreturned an abnormal response. The respcode andresp2code values are as returned by CICS.


User response: Follow the instructions associated withthe respcode and resp2code values for the EXEC CICSSTART command. If the problem persists, collect thedump and contact your IBM Support Center.



EYUNX0021E addspace global work area size is largerthan 32K

Explanation: The size of a global work area requestedfor a MAS is too large, where:


System action: A system dump is taken with a dumpcode of EYUN and control returns to CICS. The CICS

system continues to initialize, but it is not known toCICSPlex SM.

User response: Collect the dump and contact yourIBM Support Center.

Module: EYU9NXSM


EYUNX0022E INQUIRE failed: RESP=respcodeRESP2=resp2code

Explanation: An EXEC CICS INQUIRE SYSTEMcommand was issued to obtain the CICS release level,and it returned an abnormal response. The respcode andresp2code values are as returned by CICS.


User response: Follow the instructions associated withthe respcode and resp2code values for the EXEC CICSINQUIRE SYSTEM command. If the problem persists,collect the dump and contact your IBM Support Center.

Module: EYU9NXSM, EYU9NXSD, EYU1NXRM


EYUNX0023E CICS release cicsrel is not supported

Explanation: The MAS subcomponent can not beinitialized because the version of CICS that is installedis not supported by CICSPlex SM, where cicsrelidentifies the release of CICS that was encountered.


User response: Review the CICSPlex SM installationrequirements and install a supported release of CICS.



EYUNX0024E ASSIGN failed, RESP=respcodeRESP2=resp2code

Explanation: An EXEC CICS ASSIGN command wasissued to obtain the CICS SYSID, APPLID, andTERMCODE; it returned an abnormal response. Therespcode and resp2code values are as returned by CICS.

System action: MAS initialization terminates.

User response: Follow the instructions associated withthe respcode and resp2code values for the EXEC CICSASSIGN command.




Chapter 18. EYUNXnnnn messages 91

EYUNX0026E WAIT EXTERNAL failed,RESP=respcode RESP2=resp2code

Explanation: An EXEC CICS WAIT EXTERNAL wasissued to delay PLT processing until the MAS initializesand POSTs the ECB. The EXEC CICS WAITEXTERNAL command failed. The respcode and theresp2code values are returned by CICS.

System action: MAS PLT processing completes andcontrol is returned to CICS. PLT processing continueswhile MAS initialization continues.

User response: Follow the instructions associated withthe respcode and resp2code values for the EXEC CICSATTACH command. If BAS is being used to define andinstall resources, it is possible that resources may notbe available when needed by the various applications.If the problem persists, contact your IBM SupportCenter.

Module: EYU9NXSM


EYUNX0027E START exit cccccccc failed,EIBRCODE=xxxxxxxxxxxx

Explanation: An error occurred during local MASinitialization while attempting to start processing for aCICSPlex SM related CICS exit (EXEC CICS ENABLEPROGRAM START), where:

cccccccc Is the name of the exit

xxxxxxxxxxxxIs the CICS hexadecimal EIBRCODE

System action: An EYUN transaction dump will betaken and the MAS initialization will fail.

User response: User Response: Verify that the exitprogram is defined and installed in the MAS, that itresides in a DFHRPL library being used by the MAS,and then restart the MAS. If the error continues afterthe above is verified, then restart the MAS. If the errorcontinues after the above is verified, collect as much ofthe following as possible and contact your IBM SupportCenter:

v The complete job output

v The EYUN transaction dump

v The unformatted AUXTRACE data sets

Module: EYU9NXSM


EYUNX0028E INQUIRE PROGRAM cccccccc failed,EIBRCODE=xxxxxxxxxxxx

Explanation: An error occurred during local MASinitialization while attempting to inquire on the entrypoint address for a CICSPlex SM related CICS exit(EXEC CICS INQUIRE PROGRAM), where:

cccccccc Is the name of the exit


System action: An EYUN transaction dump will betaken and the MAS initialization will fail.

User response: User Response: Verify that the exitprogram is defined and installed in the MAS, that itresides in a DFHRPL library being used by the MAS,and then restart the MAS. If the error continues afterthe above is verified, then restart the MAS. If the errorcontinues after the above is verified, collect as much ofthe following as possible and contact your IBM SupportCenter:


v The EYUN transaction dump


Module: EYU9NXSM


EYUNX0030I addspace successfully initiated fromterminal termid

Explanation: A MAS has been successfully started byan operator at the specified terminal, where:


termid Identifies the terminal from which the MASwas started.

System action: MAS initialization continues. Furthermessages related to the initialization process appear inthe job log.




EYUNX0031I MAS is already initialized

Explanation: An attempt was made to start a MASthat is already initialized.





EYUNX0032E LOAD Program EYU9XLEV failed,RESP2=resp2code

Explanation: An EXEC CICS LOAD command wasissued for the specified program to determine if aCICSPlex SM environment could be established. The



||

||||

||

||

||

||||||||

|

|

|

|

|

||

||||

||

||

||

||||||||

|

|

|

|

|

LOAD command returned an abnormal response,where:


System action: MAS initialization terminates.

User response: Follow the instructions associated withthe resp2code value for the EXEC CICS LOADcommand.

Module: EYU9NXSM


EYUNX0033I RELEASE Program EYU9XLEV failed,RESP2=resp2code

Explanation: An EXEC CICS RELEASE command wasissued to release the specified program. The RELEASEcommand returned an abnormal response, where:




Module: EYU9NXSM


EYUNX0034I Name Token Services call failed.RC=code

Explanation: The MAS agent has attempted to invokethe MVS name token service IEANTRT, but the requesthas failed with (decimal) return code code.

System action: MAS agent initialization terminates.

User response: Check for previous messages toidentify the cause of the abend or error that caused thefailure. If you cannot identify the cause of the problem,collect the complete job log from the MAS, any dumpsthat may have been captured, and contact your IBMsupport center.

Module: EYU9NXSM


EYUNX0035I Startup aborted. Previous LRT abnormaltermination failure.

Explanation: An attempt was made to initialize theMAS agent in an execution of CICS that previously hada MAS agent that failed to terminate correctly.

System action: MAS agent initialization terminates.

User response: The CICS region must be restartedbefore the MAS agent will initialize.

See the User Response of messages EYUNL0903E andEYUNL0904E, which should precede this message.

Module: EYU9NXSM


EYUNX0037E MAS startup rejected due to LRTabnormal termination

Explanation: Transaction COLM was issued in a localMAS to start the MAS agent, but a previous failure ofthe CICSPlex SM controlling task CONL was detected,so the startup request is rejected.

System action: The startup request is ignored.

User response: Message EYUXS1018E was previouslyissued during this execution of the MAS. Please refer tothe documentation for this message. Then restart theCICS system to start the MAS agent.

Module: EYU9NXSM


EYUNX0038E CREATE{PROFILE|PROGRAM|TRANSACTION|TDQUEUE} resourcename failed:RESP=respcode, RESP2=resp2code

Explanation: The MAS initialization program issuedan EXEC CICS CREATE command to create theresource resourcename for CICSPlex SM. The CREATEcommand returned an abnormal response, with thevalues shown in respcode and resp2code.


User response: Examine the CICS trace records todetermine what caused the EXEC CICS error. Thenrestart MAS initialization using the COLM transaction.

Module: EYU9NXLM


EYUNX0039E CICS Transaction Server SMSS releasesmssrelease is different from CICS releasecicsrelease. SMSS initialization isterminated.

Explanation: SMSS initialization has failed because theSMSS and CICS release levels do not match. An SMSScan run only with a CICS Transaction Server at thesame release level.

System action: Initialization terminates.

User response: Ensure that the CICS TransactionServer SMSS release smssrelease matches the CICSrelease cicsrelease. Check the CICS STEPLIB and ensurethat the SDFHAUTH and SEYUAUTH data sets are forthe same CICS TS release. Check CICS DFHRPL andensure that the SDFHLOAD and SEYULOAD data setsare for the same CICS TS release.

Module: EYU9NXRM


EYUNX0033I • EYUNX0039E


||

||||

|

||||

|

|

EYUNX0040I applid Termination task initiated

Explanation: A request was issued to shut down thespecified CICS system. The shutdown transaction hasreceived control and the shutdown process has begun.

System action: The MAS and CICS systemtermination processes are begun.


Module: EYU9NPS2, EYU1NPS2


EYUNX0041E applid RETRIEVE failed:RESP=respcode, RESP2=resp2code

Explanation: An EXEC CICS RETRIEVE commandwas issued to obtain data from the communicationsarea for shutdown of the specified CICS system; thecommand returned an abnormal response. The respcodeand resp2code values are as returned by CICS.

System action: The shutdown task returns control toCICS. Shutdown of the CICS system is not initiated.

User response: Follow the instructions associated withthe respcode and resp2code values for the EXEC CICSRETRIEVE command.



EYUNX0044E applid PERFORM SHUTDOWN failed:RESP=respcode RESP2=resp2code

Explanation: A PERFORM SHUTDOWN commandwas issued for the specified CICS system, and itreturned an abnormal response. The respcode andresp2code values are as returned by CICS.


User response: Follow the instructions associated withthe respcode and resp2code values for CEMT PERFORMSHUTDOWN or EXEC CICS PERFORM SHUTDOWN.



EYUNX0045E applid Shutdown task bad branchvalue - value

Explanation: The shutdown task for the specifiedCICS system received a bad branch value and couldnot determine what command to execute.


User response: Collect the job log and contact yourIBM Support Center.

Module: EYU9NPS2


EYUNX0046E MAS shutdown rejected due to LRTabnormal termination

Explanation: Transaction COSH was issued in a localMAS to shutdown the MAS agent, but a previousfailure of the CICSPlex SM controlling task CONL wasdetected, so the shutdown request is rejected.

System action: The shutdown request is ignored.

User response: Message EYUXS1018E was previouslyissued during this execution of the MAS. Please refer tothe documentation for this message. Then restart theCICS system to start the MAS agent.

Module: EYU9NXSM


EYUNX0047E EXTRACT EXIT failed: RESP=nnnn,EIBRCODE= hhhhhh

Explanation: During processing of an API, or WUIMAS termination request, module EYU9NPS2encountered an error when issuing an EXEC CICSEXTRACT command.

System action: CICS termination is aborted.

User response: Collect the complete job output andthe auxtrace data sets from the MAS and the CMAS itconnects to and contact your IBM Support Center. Toterminate the MAS, use CEMT PERFORMSHUTDOWN.

Module: EYU9NPS2


EYUNX0051I addspace termination initiated

Explanation: The MAS shutdown task has been givencontrol by a CICS system that is terminating, where:


System action: MAS termination begins and controlreturns to CICS.


Module: EYU9NXSD, EYU1NXTM


EYUNX0052I compid termination ECB posted

Explanation: The termination ECB for the specifiedcomponent has been posted; its task will be terminated,where:

EYUNX0040I • EYUNX0052I


||

||||

|

||||

|

|

compid Identifies the component as either KernelLinkage (KNL) or managed application system(MAS).

System action: MAS termination continues.




EYUNX0053W Global area address is zero or invalid

Explanation: The global work area address that waspassed to the MAS shutdown program was zero orinvalid.

System action: The MAS, if active, cannot terminatenormally. Control returns to CICS and terminationcontinues.

User response: If MAS tasks remain active, the CICSsystem must be either terminated with theIMMEDIATE operand or canceled.

Module: EYU9NXSD


EYUNX0054W XLWA address is zero or invalid

Explanation: The Kernel Linkage work area addressthat was passed to the MAS shutdown program waszero or invalid.





EYUNX0055W MODB list address is zero

Explanation: The address of the list of major objectdescriptor block (MODB) addresses that was passed tothe MAS shutdown program was zero.



Module: EYU9NXSD


EYUNX0058W ASSIGN failed: RESP=respcodeRESP2=respcode2

Explanation: An EXEC CICS ASSIGN TERMINALcommand was issued to obtain the type of terminalassociated with the task and it returned an abnormalresponse. The respcode and resp2code values are asreturned by CICS.

System action: The MAS agent shutdown task returnscontrol to CICS. The MAS agent code will not beterminated.

User response: The MAS agent code can be stoppedby issuing the STOP action from a CICSPlex SM APIprogram.

Module: EYU9NXTM


EYUNX0060W compid MODB address is zero orinvalid

Explanation: The major object descriptor block(MODB) address for the specified component is zero orinvalid, where compid identifies the component as eitherKernel Linkage (KNL) or managed application system(MAS).

System action: The component tasks are notterminated. Control returns to CICS and terminationcontinues.


Module: EYU9NXSD


EYUNX0061W compid OPB address is zero orinvalid.

Explanation: The major object descriptor block(MODB) for the specified component has an ObjectProcess Block (OPB) address that is zero or invalid,where compid identifies the component as either KernelLinkage (KNL) or managed application system (MAS).



Module: EYU9NXSD


EYUNX0053W • EYUNX0061W


EYUNX0062W compid ECB address is zero

Explanation: The Object Process Block (OPB) for thespecified component has a termination ECB addressthat is zero; the ECB cannot be posted, where compididentifies the component as either Kernel Linkage(KNL) or managed application system (MAS).



Module: EYU9NXSD


EYUNX0070I XLWA termination ECB posted

Explanation: The ECB in the Kernel Linkage (KNL)work area has been posted to indicate that the CICSsystem is terminating and the MAS is not to berestarted.

System action: Control returns to CICS andtermination of the CICS system and the MAScontinues.




EYUNX0071I MAS successfully terminated fromterminal termid

Explanation: The MAS agent code has beensuccessfully stopped by an operator runningtransaction COSH at terminal termid.

System action: The MAS agent code is stopped. CICScontinues to run.


Module: EYU9NXTM


EYUNX0072E addspace termination from terminaltermid failed

Explanation: An error has occured during MAStermination invoked using transaction COSH, where:


termid Identifies the terminal from which the MASwas terminated.

Previous messages indicate the cause of the failure.


User response: See previous error messages written tothe console and job log.

Module: EYU9NXTM


EYUNX0101E QUERY SECURITY forTRANSATTACH resourcename failed:RESP=respcode, RESP2=resp2code.

Explanation: The MAS initialization program issuedan EXEC CICS QUERY SECURITY command to verifythat transaction resourcename is defined correctly to theexternal security manager. The command returned anabnormal response, with the values shown in respcodeand resp2code.

System action: MAS initialization will continue untilall transaction IDs have been processed, then the MASagent will issue message EYUNX0103E and terminate.

User response: Follow the instructions associated withthe respcode and resp2code values for EXEC CICSQUERY SECURITY.

Module: EYU9NXLM, EYU9NXRM


EYUNX0102E QUERY SECURITY forTRANSATTACH resourcename isincorrect: READ=NOTREADABLE.

Explanation: The MAS initialization program issuedan EXEC CICS QUERY SECURITY command to verifythat transaction resourcename is defined correctly to theexternal security manager. The userid under which theMAS initialization program executes (the region userid)does not have permission to START transactionresourcename.

System action: MAS initialization will continue untilall transaction IDs have been processed, then the MASagent will issue message EYUNX0103E and terminate.

User response: Correct the resource profile andpermissions for transaction resourcename and restartMAS initialization using the COLM transaction.



EYUNX0103E Incorrect security profile for one ormore resources. MAS initialization isterminating.

Explanation: The MAS initialization program issuedEXEC CICS QUERY SECURITY commands to verifythat each internal CPSM transaction is defined correctlyto the external security manager. One or more of thecommands returned an abnormal response, or one ormore transactions had incorrect security profiles.

System action: MAS initialization will terminate.

EYUNX0062W • EYUNX0103E


|||

||||||

|||

|||

|

|

|||

|||||||

|||

|||

|

|

|||

||||||

|

User response: Correct the problems identified bymessages EYUNX0101E and EYUNX0102E and restartMAS initialization using the COLM transaction.




|||

|

|

Chapter 19. EYUPEnnnn messages

EYUPE0001I RTAEVL initialization complete

Explanation: The Evaluation Services subcomponentof RTA has been successfully initialized.

System action: RTA initialization continues.


Module: EYU0PEIN

Destination: EYULOG

EYUPE0002I RTAEVL termination complete

Explanation: The Evaluation Services subcomponentof RTA has been terminated.

System action: RTA termination continues.


Module: EYU0PETM

Destination: EYULOG

EYUPE0004I RTAEVL long-running task terminated

Explanation: The long running task (LRT) for theEvaluation Services subcomponent of RTA has beenterminated.



Module: EYU0PELT

Destination: EYULOG

EYUPE0005W RTAEVL was unable to call program(prgmid) transaction (tranid) - reason

Explanation: RTA attempted to call the specifieduser-written status probe program, but the call was notsuccessful, where:

prgmid Is the name of the status probe program.

tranid Is the name of the transaction used to start theprogram.


Unsuccessful linkAn attempt to link to the specifiedstatus probe program wasunsuccessful.

Program marked disabledCICS has marked the specified statusprobe program as disabled.

Unable to start CICS taskA task could not be started to call thespecified status probe program.

Transaction marked disabledCICS has marked the transaction usedto call the specified status probeprogram as disabled.

Transaction not linked to EYU9XLOPThe transaction used to call thespecified status probe program (asdefined in the STATDEF view) is notlinked to the CICSPlex SM programEYU9XLOP.

Program cannot be foundCICS has returned a PGMIDERRcondition in response to aCICSPlex SM program inquiryrequest.

System action: RTA processing continues as if thestatus probe program had returned a status ofNORMAL. A user trace record is written to the CICStrace data set.

User response: Depending on the reason text, do oneof the following:

Unsuccessful linkMake sure the program is correctly defined toCICS and that it is located in one of theSTEPLIB data sets.

Program marked disabledMake sure the program is located in one of theCICS STEPLIB data sets.

Unable to start CICS taskMake sure the CICS system where theprogram is to run is not at MAX TASK. If it is,increase the MAXTASK parameter. Also makesure both the program and the transactionused to call it are correctly defined to CICS.

Transaction marked disabledMake sure the transaction is correctly definedto CICS.

Transaction not linked to EYU9XLOPMake sure the CICS definition of thetransaction points to EYU9XLOP.

Module: EYU0PEMA, EYU0PEMS


EYUPE0006W RTAEVL was returned an invalidstatus from program (prgmid)


Explanation: After successfully calling a user-writtenstatus probe program, RTA received an invalid returnstatus, where:

prgmid Is the name of the status probe program.

System action: RTA processing continues as if thestatus probe program had returned a status ofNORMAL.

User response: Review the source code for the statusmonitor program and determine if and where a returnstatus is being set. Modify the program to return avalid status indicator. For details on writing RTA statusprobe programs, see the CICSPlex System ManagerManaging Resource Usage manual.

Module: EYU0PEMA


EYUPE0007E RTAEVL agent has had a failure

Explanation: The Evaluation Services subcomponentof RTA encountered a problem while running auser-written status probe program. Depending onwhere the problem occurred, the status probe programmay have completed successfully.

System action: RTA processing continues as if thestatus probe program had returned a status ofNORMAL. A user trace record is written to the CICStrace data set.


Module: EYU0PEMA


EYUPE0101E RTAEVL initialization failed.

Explanation: The Evaluation Services subcomponentof RTA could not be initialized.

System action: RTA initialization terminates. A usertrace record is written to the CICS trace data set.


Module: EYU0PEIN


EYUPE0102E RTAEVL termination failed.

Explanation: An error occurred while attempting toterminate the Evaluation Services subcomponent ofRTA.

System action: All other RTA subcomponents attemptan orderly shutdown. A user trace record is written tothe CICS trace data set.


Module: EYU0PETM


EYUPE0104E RTAEVL long-running task failed.

Explanation: The long running task (LRT) for theEvaluation Services subcomponent of RTA encountereda problem from which it could not recover.

System action: RTA terminates. A user trace record iswritten to the CICS trace data set.


Module: EYU0PELT


EYUPE0105E RTAEVL long-running task encounteredan unknown event (nn), event ignored

Explanation: The Evaluation Services long runningtask (LRT) received an unsolicited event record, where:

nn Is the event notification ID that was notrecognized. Given the event notification ID, itis possible to determine which CICSPlex SMmethod created the event.

System action: Evaluation Services ignores the eventrecord and continues processing. The invalid eventrecord is written to the CICS trace data set.


Module: EYU0PELT


EYUPE0106W RTAEVL event name processing failed.

Explanation: The Evaluation Services subcomponentexperienced an internal error while attempting toprocess the specified event, where:

name Identifies the event being processed as one ofthe following:

CICSSTRTA CICS system was started.

CICSSTOPA CICS system was stopped.

System action: Evaluation Services event processingcontinues. A user trace record is written to the CICStrace data set.


Module: EYU0PELT


EYUPE0007E • EYUPE0106W


Chapter 20. EYUPInnnn messages

EYUPI0001I subcompid initialization has started

Explanation: RTA has started to initialize the specifiedsubcomponent, where:

subcompidIdentifies the subcomponent that is beinginitialized. The RTA subcomponents areinitialized in the following order:

1. Analysis Services (RTAALZ)

2. Evaluation Services (RTAEVL)

3. system availability monitoring (RTASAM)

4. Action Services (RTAACT)

5. analysis point monitoring (RTAAPM)

6. MAS resource monitoring (RTAMRM)



Module: EYU0PINT

Destination: EYULOG

EYUPI0002I RTA initialization complete

Explanation: All RTA subcomponents have beensuccessfully initialized.



Module: EYU0PINT

Destination: EYULOG

EYUPI0101E RTA initialization unable to action

Explanation: RTA could not complete the specifiedaction, which is required for initialization, where:

action Identifies the action that could not becompleted as one of the following:

v Acquire storage

v Register MOEB

v Create data cache

v Create queue

v Register events

v Build CICSplex list

v Query parameters

System action: RTA initialization terminates. CMASinitialization continues. A user trace record is written tothe CICS trace data set.

User response: Collect the trace records and any

related messages and contact your IBM Support Center.

Module: EYU0PINT


EYUPI0102E RTA initialization failed.

Explanation: The RTA component could not beinitialized.

System action: RTA terminates. CMAS initializationcontinues. A user trace record is written to the CICStrace data set.


Module: EYU0PINT



Chapter 21. EYUPMnnnn messages

EYUPM0001I RTAMRM initialization complete

Explanation: The MAS resource monitoringsubcomponent of RTA has been successfully initialized



Module: EYU0PMIN

Destination: EYULOG

EYUPM0002I RTAMRM termination complete

Explanation: The MAS resource monitoringsubcomponent of RTA has been terminated.



Module: EYU0PMTM

Destination: EYULOG

EYUPM0003I RTA Specification (specname)successfully installed forContext(plexname) Scope(sysname)

Explanation: The named RTA specification has beeninstalled for the specified context and scope, where:

specnameIdentifies the specification that was installed.

plexnameIdentifies the CICSplex to which thespecification applies.

sysnameIdentifies the CICS system or CICS systemgroup to which the specification applies.

System action: RTA processing continues.

User response: None

Module: EYU0PMCS

Destination: EYULOG

EYUPM0004I RTAMRM long-running taskterminated

Explanation: The long running task (LRT) for theMAS resource monitoring subcomponent of RTA hasbeen terminated.



Module: EYU0PMLT

Destination: EYULOG

EYUPM0005I RTA Specification (specname)successfully released for Context(plexname) Scope (sysname)

Explanation: The named analysis specification hasbeen released from processing in the specified contextand scope. A specification is released when the scope itis associated with is shut down, where:

specnameIdentifies the specification that was released.

plexnameIdentifies the CICSplex from which thespecification was released.

sysnameIdentifies the CICS system from which thespecification was released.



Module: EYU0PMCE

Destination: EYULOG

EYUPM0006I The deftype (defname) has beensuccessfully installed for Context(plexname) Scope (sysname)

Explanation: The specified analysis or status definitionhas been installed in the named context and scope,where:

deftype Identifies the type of definition that wasinstalled as either RTADEF or STATDEF.

defnameIs the name of the definition.

plexnameIdentifies the CICSplex for which thedefinition was installed.

sysnameIdentifies the CICS system for which thedefinition was installed.



Module: EYU0PMDI

Destination: EYULOG

EYUPM0101E RTAMRM initialization failed.


Explanation: The MAS resource monitoringsubcomponent of RTA could not be initialized.



Module: EYU0PMIN


EYUPM0102E RTAMRM termination failed.

Explanation: An error occurred while attempting toterminate the MAS resource monitoring subcomponentof RTA.



Module: EYU0PMTM


EYUPM0103E RTA Specification (specname)unsuccessfully installed forContext(plexname) Scope(sysname)

Explanation: The named RTA specification could notbe installed because there was not enough storageavailable for its internal data structures, where:

specnameIs the name of the specification.


sysnameIdentifies the CICS system to which thespecification applies.

System action: RTA processing continues. A user tracerecord is written to the CICS trace data set.


Module: EYU0PMCS


EYUPM0104E RTAMRM long-running task failed.

Explanation: The long running task (LRT) for theMAS resource monitoring subcomponent of RTAencountered a problem from which it could not recover.


User response: Collect the trace records and any

related messages and contact your IBM Support Center.

Module: EYU0PMLT


EYUPM0105E RTAMRM long-running taskencountered an unknown event (nn),event ignored

Explanation: The MAS resource monitoring longrunning task (LRT) received an unsolicited eventrecord, where:


System action: MAS resource monitoring ignores theevent record and continues processing. The invalidevent record is written to the CICS trace data set.


Module: EYU0PMLT


EYUPM0106E RTA Specification(specname)unsuccessfully released forContext(plexname) Scope(sysname)

Explanation: The named RTA specification could notbe released because of an internal error, where:



sysnameIdentifies the CICS system to which thespecification applies.

System action: RTA processing continues. Anexception trace record is written to the CICS trace dataset.


Module: EYU0PMCE


EYUPM0107E Install of deftype (defname) forRTASPEC specname in Context (plexname)Scope (sysname) failed.

Explanation: The specified analysis or status definitioncould not be installed for the named RTA specification,where:

EYUPM0102E • EYUPM0107E


deftype Identifies the type of definition that was notinstalled as either RTADEF or STATDEF.



plexnameIdentifies the CICSplex to which the CICSsystem belongs.

sysnameIdentifies the CICS system for whichdefinitions could not be installed.



Module: EYU0PMDI


EYUPM0108E Time Period name (defname)registration failed. Time Period notdefined.

Explanation: RTA attempted to register interest in thespecified time period, but it is not defined in the datarepository, where:

defnameIs the name of the time period that could notbe found.

System action: RTA processing continues. AnyRTADEF or STATDEF definitions that reference thetime period are not installed until a time period withthat name is defined.

User response: Make sure the time period name wasspecified correctly on all RTADEF and STATDEFdefinitions. Use the PERIODEF view to display a list ofexisting time period definitions. If necessary, create anew time period definition with the specified name.

Module: EYU0PMDI


EYUPM0109E Install of RTADEF (defname) forRTASPEC specname in Context (plexname)Scope (sysname) failed. description.

Explanation: An attempt was made to install thenamed analysis definition (RTADEF) into an analysisspecification. The installation was unsuccessful becausethe definition does not have a valid evaluationdefinition (EVALDEF) associated with it, where:

defnameIs the name of the analysis definition thatcould not be installed.

specnameIs the name of the analysis specification intowhich the definition was being installed.



descriptionThis is one of the following pieces ofadditional text:v EVALDEF not foundv Resource not valid for CICS releasev Evaluation column invalid for version of

resource table


User response: Create an appropriate evaluationdefinition and associate it with the analysis definition.Then reinstall the analysis definition.

Module: EYU0PMDI


EYUPM0110E RTAMRM is not active for Context(plexname) Scope (sysname). Nodefinitions installed.

Explanation: An attempt was made to install analysisor status definitions in a CICS system, but the MASresource monitoring subcomponent of real-timeanalysis is not active, where:



For real-time analysis to occur, the CICS system mustbe associated with an analysis specification.


User response: Use the RTASPEC view to associate ananalysis specification with the CICS system. Becausethe CICS system is already active, you must also usethe UPD action command from the MAS view to turnreal-time analysis on. For a description of the RTASPECview, see the CICSPlex System Manager ManagingResource Usage. For a description of the MAS view andits UPD action command, see the CICSPlex SystemManager Operations Views Reference.

Once the CICS system has been associated with ananalysis specification and real-time analysis has beenturned on, you can install the desired definitions.

Module: EYU0PGDI

EYUPM0108E • EYUPM0110E

Chapter 21. EYUPMnnnn messages 105


EYUPM0111E The deftype (defname) for RTASPECspecname in Context (plexname) Scope(sysname) is already installed. Discardand reinstall.

Explanation: An attempt was made to install ananalysis or status definition in a CICS system for thenamed RTA specification, but the specified definition isalready installed, where:

deftype Identifies the type of definition as eitherRTADEF or STATDEF.






User response: If the analysis or status definition hasbeen updated since the last time it was installed, youmust discard the active definition before installing theupdated one. Use the RTAACTV view, as described inthe CICSPlex System Manager Operations Views Reference,to discard the definition from the running CICS system.

If the definition has not been updated, there is no needto reinstall it; the definition is already active in theCICS system.

Module: EYU0PMDI


EYUPM0111E


Chapter 22. EYUPNnnnn messages

EYUPN0001I RTAACT initialization complete

Explanation: The Action Services subcomponent ofRTA has been successfully initialized.



Module: EYU0PNIN

Destination: EYULOG

EYUPN0002I RTAACT termination complete

Explanation: The Action Services subcomponent ofRTA has been terminated



Module: EYU0PNTM

Destination: EYULOG

EYUPN0004I RTAACT long-running task terminated

Explanation: The long running task (LRT) for theAction Services subcomponent of RTA has beenterminated.



Module: EYU0PNLT

Destination: EYULOG

EYUPN0005W Notify created for SAM,Context=plexname, Target=targetsys,Sev=level, Event=evntname, Text=usertxt.

Explanation: A user-requested external notificationwas created as the result of a system availabilitymonitoring (SAM) event, where:

plexnameIdentifies the CICSplex for which thenotification was created.

targetsysIdentifies the target of the notification, whichcould be a CICS system, CICS system group orCICSplex.

level Indicates the severity of the notification.

evntnameIs the event name assigned to this notificationby SAM:

!!SAMOPSA CICS system that is scheduled to beactive is not.

!!SAMMAXA CICS system has reached itsmaximum task limit.

!!SAMNRMA CMAS has lost contact with anactive MAS that it is managing.

!!SAMSDMA CICS system is taking a systemdump.

!!SAMSOSA CICS system is short-on-storage.

!!SAMSTLA CICS system has stalled.

!!SAMTDMA CICS system is taking a transactiondump.

usertxt Is text defined by a user for use with SAMnotifications.

Note: For a list of the default text stringsissued for various stall conditions (!!SAMSTL),see the table in CICS Transaction Server for z/OSInstallation Guide.


User response: Check the following for details aboutthe event:

v The EVENT and EVENTD views

v NetView alerts, if requested

Also check the job log or system log to determine thecurrent status of the named CICS systems. Then, basedupon your enterprise criteria, decide if the eventrequires any user action.

Module: EYU0PNAN


EYUPN0006W Notify created for RTADEF defnameby APM, Context=plexname,Target=targetsys, Sev=level,Resource=restype Key=resname,Text=usertxt.

Explanation: A user-requested external notificationwas created as the result of an RTA definition becomingtrue, where:


defnameIs the name of the RTA definition that causedthe notification to be created.

plexnameIdentifies the CICSplex where the RTAdefinition was installed.



restype Indicates the type of resource to which thenotification applies.

resnameIdentifies the specific resource to which thenotification applies.

usertxt Is text defined by a user for use with APMnotifications.





Then, based upon your enterprise criteria, decide if theevent requires any user action.

Module: EYU0PNAN


EYUPN0007W Notify created for deftype defname byMRM, Context=plexname,Target=targetsys, Sev=level,Resource=restype Key=resname,Text=usertxt.

Explanation: A user-requested external notificationwas created as the result of an RTA or status definitionbecoming true, where:


defnameIs the name of the definition that caused thenotification to be created.

plexnameIdentifies the CICSplex where the definitionwas installed.

targetsysIdentifies the target of the notification as asingle CICS system.




usertxt Is text defined by a user for use with MRMnotifications.






Module: EYU0PNAN


EYUPN0008W Notify updated for SAM,Context=plexname, Target=targetsys,Sev=level, Event=evntname, Text=usertxt.

Explanation: An outstanding external notification wasupdated as the result of a change in severity for asystem availability monitoring (SAM) event, where:

plexnameIdentifies the CICSplex for which thenotification was updated.


level Indicates the new severity of the notification.

evntnameIs the event name assigned to this notificationby SAM.






Also check the job log or system log to determine thecurrent status of the named CICS systems. Then, basedupon your enterprise criteria, decide if the eventrequires any user action.

Module: EYU0PNUN


EYUPN0007W • EYUPN0008W


EYUPN0009W Notify updated for RTADEF defnameby APM, Context=plexname,Target=targetsys, Sev=level,Resource=restype Key=resname,Text=usertxt.

Explanation: An outstanding external notification wasupdated as the result of a change in severity for anRTA definition, where:

defnameIs the name of the RTA definition that causedthe notification to be updated.






usertxt Is text defined by a user for use with APMnotifications.






Module: EYU0PNUN


EYUPN0010W Notify updated for deftype defname byMRM, Context=plexname,Target=targetsys, Sev=level,Resource=restype Key=resname,Text=usertxt.

Explanation: An outstanding external notification wasupdated as the result of a change in severity for anRTA or status definition, where:


defnameIs the name of the definition that caused thenotification to be updated.






usertxt Is text defined by a user for use with MRMnotifications.






Module: EYU0PNUN


EYUPN0011W Notify action for SAM,Context=plexname, Target=targetsys,Sev=level, Event=evntname, Text=usertxt.

Explanation: An outstanding external notification fora system availability monitoring (SAM) event waseither resolved or removed, where:

action Indicates what happened to the notification, asfollows:

RESOLVEDThe condition that caused the eventwas alleviated.

REMOVEDThe condition that caused the eventcould no longer be monitored for oneof the following reasons:

v The CICS system has terminated.

v The CICSPlex SM MAS agent hasbeen stopped in the monitoredCICS system.

v The CICS system being monitoredhas had its Real Time Analysis(RTA) status changed from YES orSAM, to NO or MRM.

plexnameIdentifies the CICSplex to which thenotification applied.





evntnameIs the event name assigned to this notificationby SAM.




Module: EYU0PNCN


EYUPN0012W Notify action for RTADEF defname byAPM, Context=plexname, Target=targetsys,Sev=level, Resource=restype, Key=resname,Text=usertxt.

Explanation: An outstanding external notification foran RTA definition was either resolved or removed,where:


RESOLVEDThe condition described by the RTAdefinition is no longer true.

REMOVEDThe condition described by the RTAdefinition could no longer bemonitored because the CICS systemwent down or because a modificationstring was executed.

defnameIs the name of the RTA definition.






usertxt The value displayed depends upon the valueof the "action" variable insert:

v If the action variable insert indicatesRESOLVED, the value is the text defined bya user for use with APM notifications.

v If the action variable insert indicatesREMOVED, the value is one of thefollowing:

– “Definition cannot be evaluated” if theCICS system went down.

– “Resource modification issued” if theRTADEF specifies ALWAYS for the"Perform Ops" operand and theEVALDEF's modification stringexpression was executed without aCICSPlex SM or CICS response error.



Module: EYU0PNCN


EYUPN0013W Notify action for deftype defname byMRM, Context=plexname,Target=targetsys, Sev=level,Resource=restype, Key=resname,Text=usertxt.

Explanation: An outstanding external notification foran RTA or status definition was either resolved orremoved, where:


RESOLVEDThe condition described by thedefinition is no longer true.

REMOVEDThe condition described by thedefinition could no longer bemonitored either because the CICSsystem went down or because amodification string was executed.










usertxt The value displayed depends upon the valueof the "action" variable insert:

v If the action variable insert indicatesRESOLVED, the value is the text defined bya user for use with MRM notifications.

v If the action variable insert indicatesREMOVED, the value is one of thefollowing:

– “Definition cannot be evaluated” if theCICS system went down.

– “Resource modification issued” if theRTADEF specifies ALWAYS for the"Perform Ops" operand and theEVALDEF's modification stringexpression was executed without aCICSPlex SM or CICS response error.



Module: EYU0PNCN


EYUPN0014I Resource modification forContext=plexname, Target=targetsys,Resource=restype, Key=resname,Evaldef=defname Submitted.

Explanation: A resource modification that wasrequested in the specified real-time analysis evaluationdefinition has completed successfully, where:

plexnameIdentifies the CICSplex where the change wasmade.

targetsysIdentifies the target of the change as a singleCICS system.

restype Indicates the type of resource to which thechange applies.

resnameIdentifies the specific resource to which thechange applies.

defnameIs the name of the evaluation definition thatresulted in the change being made.



Module: EYU0PNAN

Destination: EYULOG

EYUPN0101E RTAACT initialization failed.

Explanation: The Action Services subcomponent ofRTA could not be initialized.



Module: EYU0PNIN


EYUPN0102E RTAACT termination failed.

Explanation: An error occurred while attempting toterminate the Action Services subcomponent of RTA.



Module: EYU0PNTM


EYUPN0104E RTAACT long-running task failed.

Explanation: The long running task (LRT) for theAction Services subcomponent of RTA encountered aproblem from which it could not recover.



Module: EYU0PNLT


EYUPN0105E RTAACT long-running taskencountered an unknown event (nn),event ignored

Explanation: The Action Services long running task(LRT) received an unsolicited event record, where:


System action: Action Services ignores the eventrecord and continues processing. The invalid eventrecord is written to the CICS trace data set.


Module: EYU0PNLT


EYUPN0014I • EYUPN0105E


EYUPN0106W RTAACT event evntname processingfailed.

Explanation: The Action Services subcomponentexperienced an internal error while attempting toprocess the specified event. evntname identifies theevent being processed as one of the following:

EACTSERVThe RTA long running task (LRT) was calledto perform asynchronous processing.

ENETCONNA connection was established between adjacentCMASs.

ENETJOINAn indirect connection was establishedbetween CMASs.

System action: Action Services event processingcontinues. A user trace record is written to the CICStrace data set.


Module: EYU0PNLT


EYUPN0107E Internal Event evntname is invalid, noaction created

Explanation: An internal event name used either bythe RTA system availability monitoring (SAM)subcomponent, or as a default for an RTADEF orSTATDEF definition was invalid.

System action: No external notification is created. Auser trace record is written to the CICS trace data set.

User response: Collect the trace records and contactyour IBM Support Center.

Module: EYU0PNAN


EYUPN0108E User-supplied ACTION definitionname defname is not defined, internaldefault is used

Explanation: An RTADEF, STATDEF, or CICSSYSdefinition includes the name of an action that can notbe found in the data repository. The internal defaultaction is used instead, where:

defnameIs the name of the action definition that couldnot be found.

System action: RTA uses the default action andcontinues processing.

User response: Make sure the action name was

specified correctly on all RTADEF, STATDEF, andCICSSYS definitions. Use the ACTNDEF view todisplay a list of existing action definitions. If necessary,create a new action definition with the specified name.

Module: EYU0PNAN


EYUPN0109E Resource modification forContext=plexname, Target=targetsys,Resource=restype, Key=resname,Evaldef=defname failed. RESP=respcode,RESP2=resp2code, EIBRCODE=eibrcode,ATTRIBUTE=attrname.

Explanation: CICSPlex SM attempted to issue anEXEC CICS SET command to make the resourcemodification that was requested in the specifiedreal-time analysis evaluation definition. However, themodification could not be completed because either anattribute value was invalid for the specified CICSsystem, or CICS returned an abnormal response, where:

plexnameIdentifies the CICSplex where the change wasto be made.




defnameIs the name of the evaluation definition thatrequested the change.

respcodeIs the RESP= value, if the EXEC CICScommand failed. A value of 0 is returned if theproblem occurred before the EXEC CICScommand was issued.

resp2codeIs the RESP2= value, if the EXEC CICScommand failed. A value of 0 is returned if theproblem occurred before the EXEC CICScommand was issued.

eibrcodeIs the EIBRCODE= value, if the EXEC CICScommand failed. A value of 0 is returned if theproblem occurred before the EXEC CICScommand was issued.

attrnameIs the name of the resource attribute that wasinvalid, if the problem occurred before the

EYUPN0106W • EYUPN0109E


EXEC CICS command was issued. A value ofN/A is returned if the EXEC CICS commandfailed.


User response: If the problem occurred before theEXEC CICS command was issued (as indicated by theattrname value), refer to the CICSPlex System ManagerResource Tables Reference Vol 1 manual to determine thevalues and CICS releases that are valid for the attribute.Then use the EVALDEF view to correct the evaluationdefinition.

If the EXEC CICS command failed (as indicated by therespcode, resp2code, and eibrcode values) the restype valuein this message can help you determine what EXECCICS SET command was being issued when theproblem occurred. For example, if the restype value isLOCTRAN, then an EXEC CICS SET TRANSACTIONcommand was being issued.

Once you have determined what EXEC CICS commandwas being issued, follow the instructions associatedwith the respcode and resp2code values for thatcommand. For descriptions of the RESP values for aparticular CICS command and the EIBRCODE values,refer to the CICS System Programming Reference.

Module: EYU0PNAN



Chapter 23. EYUPPnnnn messages

EYUPN0109E Resource modification forContext=plexname, Target=targetsys,Resource=restype, Key=resname,Evaldef=defname failed. RESP=respcode,RESP2=resp2code, EIBRCODE=eibrcode,ATTRIBUTE=attrname.

Explanation: CICSPlex SM attempted to issue anEXEC CICS SET command to make the resourcemodification that was requested in the specifiedreal-time analysis evaluation definition. However, themodification could not be completed because either anattribute value was invalid for the specified CICSsystem, or CICS returned an abnormal response, where:

plexnameIdentifies the CICSplex where the change wasto be made.




defnameIs the name of the evaluation definition thatrequested the change.

respcodeIs the RESP= value, if the EXEC CICScommand failed. A value of 0 is returned if theproblem occurred before the EXEC CICScommand was issued.

resp2codeIs the RESP2= value, if the EXEC CICScommand failed. A value of 0 is returned if theproblem occurred before the EXEC CICScommand was issued.

eibrcodeIs the EIBRCODE= value, if the EXEC CICScommand failed. A value of 0 is returned if theproblem occurred before the EXEC CICScommand was issued.

attrnameIs the name of the resource attribute that wasinvalid, if the problem occurred before theEXEC CICS command was issued. A value ofN/A is returned if the EXEC CICS commandfailed.

System action: RTA processing continues. A user trace

record is written to the CICS trace data set.

User response: If the problem occurred before theEXEC CICS command was issued (as indicated by theattrname value), refer to the CICSPlex System ManagerResource Tables Reference Vol 1 manual to determine thevalues and CICS releases that are valid for the attribute.Then use the EVALDEF view to correct the evaluationdefinition.

If the EXEC CICS command failed (as indicated by therespcode, resp2code, and eibrcode values) the restype valuein this message can help you determine what EXECCICS SET command was being issued when theproblem occurred. For example, if the restype value isLOCTRAN, then an EXEC CICS SET TRANSACTIONcommand was being issued.

Once you have determined what EXEC CICS commandwas being issued, follow the instructions associatedwith the respcode and resp2code values for thatcommand. For descriptions of the RESP values for aparticular CICS command and the EIBRCODE values,refer to the CICS/ESA System Programming Reference.

Module: EYU0PNAN


EYUPP0002I RTAAPM termination complete

Explanation: The analysis point monitoringsubcomponent of RTA has been terminated.



Module: EYU0PPTM

Destination: EYULOG

EYUPP0003I Analysis Point Specification (specname)successfully installed forContext(plexname)

Explanation: The named analysis point specificationhas been installed for the specified context and scope,where:

specnameIdentifies the specification that was installed.




Module: EYU0PPAS


Destination: EYULOG

EYUPP0004I RTAAPM long-running task terminated

Explanation: The long running task (LRT) for theanalysis point monitoring subcomponent of RTA hasbeen terminated.



Module: EYU0PPLT

Destination: EYULOG

EYUPP0005I RTAAPM Analysis Point Specification(specname) successfully released inCMAS (cmasname)

Explanation: The named analysis point specificationhas been released from processing in the specifiedCMAS. A specification is released from a secondaryCMAS when either the primary CMAS or a secondaryCMAS with a lower CICS SYSID becomes available,where:

specnameIdentifies the specification that was released.

cmasnameIdentifies the CMAS from which thespecification was released.

System action: The analysis point specification isautomatically installed in the new CMAS. RTAprocessing continues.


Module: EYU0PPRS

Destination: EYULOG

EYUPP0006I The RTADEF (defname) has beensuccessfully installed for Context(plexname) Scope (sysname)

Explanation: The specified analysis definition hasbeen installed in the named context and scope, where:


plexnameIdentifies the CICSplex for which thedefinition was installed.

sysnameIdentifies the CICS system for which thedefinition was installed.



Module: EYU0PPRI

Destination: EYULOG

EYUPP0101E RTAAPM initialization failed.

Explanation: The analysis point monitoringsubcomponent of RTA could not be initialized.



Module: EYU0PPIN


EYUPP0102E RTAAPM termination failed.

Explanation: An error occurred while attempting toterminate the analysis point monitoring subcomponentof RTA.



Module: EYU0PPTM


EYUPP0103E Analysis Point Specification (specname)unsuccessfully installed forContext(plexname)

Explanation: The named analysis point specificationcould not be installed because there was not enoughstorage available for its internal data structures, where:





Module: EYU0PPAS


EYUPP0104E RTAAPM long-running task failed.

Explanation: The long running task (LRT) for theanalysis point monitoring subcomponent of RTAencountered a problem from which it could not recover.



EYUPP0004I • EYUPP0104E


Module: EYU0PPLT


EYUPP0105E RTAAPM long-running taskencountered an unknown event (nn),event ignored

Explanation: The analysis point monitoring longrunning task (LRT) received an unsolicited eventrecord, where:


System action: analysis point monitoring ignores theevent record and continues processing. The invalidevent record is written to the CICS trace data set.


Module: EYU0PPLT


EYUPP0107E Install of RTADEF (defname) for APSpecspecname in Context (plexname) Scope(sysname) failed.

Explanation: The specified RTA definition could notbe installed for the named analysis point specification,where:



plexnameIdentifies the CICSplex for which the RTAdefinition was being installed.

sysnameIdentifies the CICS system for which the RTAdefinition was being installed.



Module: EYU0PPRI


EYUPP0108E Time Period name (defname) registrationfailed. Time Period not defined.

Explanation: RTA attempted to register interest in thespecified time period, but it is not defined in the datarepository, where:

defnameIs the name of the time period that could notbe found.

System action: RTA processing continues. AnyRTADEF definitions that reference the time period arenot installed until a time period with that name isdefined.

User response: Make sure the time period name wasspecified correctly on all RTADEF definitions. Use thePERIODEF view to display a list of existing time perioddefinitions. If necessary, create a new time perioddefinition with the specified name.

Module: EYU0PPRI


EYUPP0109E Install of RTADEF (defname) for APSPECspecname in Context (plexname) Scope(sysname) failed description

Explanation: An attempt was made to install ananalysis definition into an analysis point specification.The installation was unsuccessful because the definitiondoes not have a valid evaluation definition (EVALDEF)associated with it, where:

defnameIs the name of the analysis definition thatcould not be installed.

specnameIs the name of the analysis point specificationinto which the analysis definition was beinginstalled.

plexnameIdentifies the CICSplex for which the analysisdefinition was being installed.

sysnameIdentifies the CICS system for which theanalysis definition was being installed.

descriptionThis is one of the following pieces ofadditional text:v Evaluation column invalid for version of

resource tablev Resource not valid for CICS Releasev Evaldef not found.


User response: Create an appropriate evaluationdefinition, associate it with the analysis definition, andthen reinstall the analysis definition.

Module: EYU0PPRI


EYUPP0105E • EYUPP0109E

Chapter 23. EYUPPnnnn messages 117

EYUPP0110E The RTADEF (defname) for APSPECspecname in Context (plexname) Scope(sysname) is already installed. Discardand reinstall.

Explanation: An attempt was made to install ananalysis definition in a CICS system for the namedanalysis point specification, but the specified definitionis already installed, where:



plexnameIdentifies the CICSplex for which the analysisdefinition was being installed.

sysnameIdentifies the CICS system for which theanalysis definition was being installed.


User response: If the analysis definition has beenupdated since the last time it was installed, you mustdiscard the active definition before installing theupdated one. Use the APACTV view, as described inthe CICSPlex System Manager Operations Views Reference,to discard the definition from the running CICS system.

If the definition has not been updated, there is no needto reinstall it; the definition is already active in theCICS system.

Module: EYU0PPRI


EYUPP0110E


Chapter 24. EYUPRnnnn messages

EYUPR0001I RTAALZ initialization complete

Explanation: The Analysis Services subcomponent ofRTA has been successfully initialized.



Module: EYU0PRIN

Destination: EYULOG

EYUPR0002I RTAALZ termination complete

Explanation: The Analysis Services subcomponent ofRTA has been terminated.



Module: EYU0PRTM

Destination: EYULOG

EYUPR0004I RTAALZ long-running task terminated

Explanation: The long running task (LRT) for theAnalysis Services subcomponent of RTA has beenterminated.



Module: EYU0PRLT

Destination: EYULOG

EYUPR0101E RTAALZ initialization failed.

Explanation: The Analysis Services subcomponent ofRTA could not be initialized.



Module: EYU0PRIN


EYUPR0102E RTAALZ termination failed.

Explanation: An error occurred while attempting toterminate the Analysis Services subcomponent of RTA.



Module: EYU0PRTM


EYUPR0104E RTAALZ long-running task failed.

Explanation: The long running task (LRT) for theAnalysis Services subcomponent of RTA encountered aproblem from which it could not recover.



Module: EYU0PRLT



Chapter 25. EYUPSnnnn messages

EYUPS0001I RTASAM initialization complete

Explanation: The system availability monitoringsubcomponent of RTA has been successfully initialized.



Module: EYU0PSIN

Destination: EYULOG

EYUPS0002I RTASAM termination complete

Explanation: The system availability monitoringsubcomponent of RTA has been terminated.



Module: EYU0PSTM

Destination: EYULOG

EYUPS0101E RTASAM initialization failed.

Explanation: The system availability monitoringsubcomponent of RTA could not be initialized.



Module: EYU0PSIN


EYUPS0101E RTASAM initialization failed.

Explanation: The system availability monitoringsubcomponent of RTA could not be initialized.



Module: EYU0PSIN


EYUPS0102W RTASAM termination failed.

Explanation: An error occurred while attempting toterminate the system availability monitoringsubcomponent of RTA.

System action: All other RTA subcomponents attempt

an orderly shutdown. A user trace record is written tothe CICS trace data set.


Module: EYU0PSTM


EYUPS0104E RTASAM long-running task failed.

Explanation: The long running task (LRT) for thesystem availability monitoring subcomponent of RTAencountered a problem from which it could not recover.



Module: EYU0PSLT


EYUPS0105E RTASAM long-running taskencountered an unknown event (nn),event ignored

Explanation: The system availability monitoring longrunning task (LRT) received an unsolicited eventrecord, where:


System action: system availability monitoring ignoresthe event record and continues processing. The invalidevent record is written to the CICS trace data set.


Module: EYU0PSLT


EYUPS0106W RTASAM event evntname processingfailed.

Explanation: The system availability monitoringsubcomponent experienced an internal error whileattempting to process the specified event, where:

evntnameIdentifies the event being processed as one ofthe following:


EDEFCHGData repository records were changedthat require immediate processing inan active CMAS.

ELSIGNALA local MAS is taking a CICS systemdump.

EMASCNTLThe RTA system availabilitymonitoring (SAM) subcomponentreported changes to an analysis pointspecification (APSPEC).

EMASJOINA MAS established a connection to aCMAS that manages it.

EMASSICKA MAS is experiencing one of thefollowing sick conditions:

v CICS system dump

v CICS transaction dump

v CICS DSA short-on-storage

v Maximum task limit reached

v CICS system stalled

EMASSTOPA MAS disconnected from theCMASs that manage it.

EMASSTRTA MAS established a connection to itsmaintenance point CMAS.

EMASWELLA MAS has recovered from apreviously reported sick condition.

ENETCONNA connection was established betweenadjacent CMASs.

ENETDISCA CMAS was disconnected from anadjacent CMAS.

ENETEXITA CMAS was disconnected fromanother CMAS to which it wasindirectly connected.

ENETJOINAn indirect connection wasestablished between CMASs.

EPLEXCHGEither a CMAS was added to orremoved from the management of aCICSplex, or the CICSplex itself wasremoved.

ETIMECHGThe time zone attributes of a CMASor CICS system were changed.

System action: System availability monitoring eventprocessing continues. A user trace record is written tothe CICS trace data set.


Module: EYU0PSLT


EYUPS0107W RTASAM cannot monitor CICSSystem(sysname) due to undefined TimePeriod(defname)

Explanation: The system availability monitoringsubcomponent of RTA cannot monitor the availabilityof the specified CICS system because the time periodassociated with it is not defined, where:

sysnameIdentifies the CICS system that could not bemonitored.

defnameIs the name of the time period definition thatcould not be found.

System action: System availability monitoringprocessing continues, but the specified CICS system isnot monitored.

User response: Make sure the time period name wasspecified correctly on the CICSSYS or MAS view. Youcan use the PERIODEF view to display a list of existingtime period definitions and, if necessary, create a newone. If you update the MAS view to include a validtime period name, system availability monitoring startsautomatically. If you change the CICSSYS view but donot update the MAS view, the CICS system must berestarted for system availability monitoring to takeeffect.

Module: EYU0PSCC, EYU0PSLT, EYU0PSRC


EYUPS0107W


Chapter 26. EYUPTnnnn messages

EYUPT0001I subcompid termination requested

Explanation: RTA has started to terminate thespecified CICSPlex SM, where:

subcompidIdentifies the subcomponent that is beingterminated. The RTA subcomponents areterminated in the following order:

1. MAS resource monitoring (RTAMRM)

2. Analysis point monitoring (RTAAPM)

3. System availability monitoring (RTASAM)

4. Analysis Services (RTAALZ)

5. Evaluation Services (RTAEVL)

6. Action Services (RTAACT)



Module: EYU0PTRM

Destination: EYULOG

EYUPT0002I RTA termination complete

Explanation: All RTA subcomponents have beenterminated.



Module: EYU0PTRM

Destination: EYULOG

EYUPT0101W RTA termination failed.

Explanation: An error occurred while attempting toterminate one or more RTA subcomponents.



Module: EYU0PTRM



Chapter 27. EYUTInnnn messages

EYUTI0002E Invocation of Topology long-runningtask (TRANID=tranid) has failed.

Explanation: An attempt to start the specified longrunning task (LRT) for Topology Services has failed,where:

tranid Identifies the LRT as one of the following:

TICT Topology Services Map Change LRT

TIRT Topology Services RODM ManagerLRT

TIST Topology Services LRT



Module: EYU0TIML


EYUTI0003E Topology Initialization Failed

Explanation: The Topology Services component couldnot be initialized.


User response: Examine the exception trace records,and any messages issued before this one to determinethe cause of the problem.

Module: EYU0TIML


EYUTI0004I Topology Initialization Complete

Explanation: The Topology Services component hasbeen successfully initialized.



Module: EYU0TIST

Destination: EYULOG

EYUTI0008E CICSplex plexname Creation Failed

Explanation: A problem occurred during creation ofthe data structures for the specified CICSplex, where:

plexnameIdentifies the CICSplex for which datastructures could not be created.

System action: Processing continues. A user tracerecord is written to the CICS trace data set.


Module: EYU0TIPC


EYUTI0009I Topology warm start for sysnameinitiated - APPLID(applid) CICSPlex(plexname)

Explanation: The CMAS CICSPlex SM topologycomponent is warm starting and has recovered MASinformation for CICS System sysname in CICSPlexplexname. This MAS is currently attempting to reconnectto the CICSPlex plexname.


Note: A MAS that is going through Topology warmstart processing is considered active when a datarepository synchronization is performed. NormalTopology connection for the MAS will occur laterduring CMAS initialization.

User response: None, unless you are trying tocomplete a data repository synchronization that haspreviously failed due to message EYUCP0207E issuedin the maintenance point CMAS for CICSplex plexname.See the user response for message EYUCP0207E fordetails.

Module: EYU0TIWS

Destination: EYULOG

EYUTI0200W NetView PPI module could not beloaded. RODM support unavailable.

Explanation: During initialization, Topology Servicescould not load the NetView subsystem interfacemodule, CNMNETV.

System action: Processing continues. However,support for the NetView RODM interface is notavailable.

User response: Make sure module CNMNETV residesin one of these places:

v The STEPLIB concatenation of the CMAS that wasattempting to communicate with NetView

v The MVS linklist

v The LPA library

Then shut down the CMAS and restart it.

Module: EYU0TIML


Destination: Job log


Chapter 28. EYUTSnnnn messages

EYUTS0001I Topology event for sysname Initiated -APPLID (applid) CICSplex (plexname)

Explanation: Topology Services has begun processinga communications endpoint event for the specifiedCICS system, where:

event Identifies the event as one of the following:

ConnectA physical connection between theMAS (CICS system) and itsmaintenance point CMAS.

Join A logical connection between theMAS (CICS system) and anotherCMAS.

DisconnectA disconnection of the MAS (CICSsystem) from its maintenance pointCMAS.

sysnameIdentifies the MAS name for the CICS system.

applid Identifies the APPLID of the CICS system.

plexnameIdentifies the CICSplex the CICS system isbeing processed for.



Module: EYU0TSSC, EYU0TSSE, EYU0TSSJ.


EYUTS0002E Topology event for sysname Failed -APPLID (applid) CICSplex (plexname)

Explanation: A communications endpoint event thatTopology Services was processing for the specifiedCICS system failed to complete, where:










Module: EYU0TSCI, EYU0TSMJ, EYU0TSSC,EYU0TSSE, EYU0TSSJ


EYUTS0003I Topology event for sysname Complete -APPLID (applid) CICSplex (plexname)

Explanation: Topology Services has completed acommunications endpoint event for the specified CICSsystem, where:










Module: EYU0TSSC, EYU0TSSE, EYU0TSSJ


EYUTS0004I Topology found sysname Already Active.

Explanation: Topology Services could not process a


communications endpoint event for the specified CICSsystem because the MAS agent was already active.



Module: EYU0TSSC, EYU0TSSJ, EYU3TSIM

Destination: EYULOG

EYUTS0005E Topology type Data StructuresCompromised.

Explanation: The Topology Services data cachestructures for a CICSplex or CICS system are no longerreliable, where:

type Identifies the type of data structures that are inerror as either CICSplex or Scope.


User response: Shut down the affected CMAS andthen restart it. Examine the exception trace records todetermine the cause of the problem. If the problempersists, collect the trace records and any relatedmessages and contact your IBM Support Center.

Module: EYU0TSFD


EYUTS0006I Topology event of CICSPlex plexnameInitiated.

Explanation: Topology Services has begun processinga CICSplex Change event for a CMAS, where:


v Add

v Update

v Remove




Module: EYU0TSPA, EYU0TSPD, EYU0TSPU


EYUTS0007E Topology event of CICSPlex plexnameFailed.

Explanation: A CICSplex Change event that TopologyServices was processing for a CMAS failed to complete,where:


v Add

v Update

v Remove






EYUTS0008I Topology event of CICSPlex plexnameComplete.

Explanation: Topology Services has completed aCICSplex Change event for a CMAS, where:


v Add

v Update

v Remove






EYUTS0009E CICS System Group grpname Not Found.

Explanation: A requested topology action could not beprocessed because the specified CICS system group,which is the current scope, is not known to TopologyServices.


User response: Make sure the CICS system groupname was correctly specified. If the CICS system groupis known to exist, examine the exception trace recordsto determine the cause of the problem.

Module: EYU0TSFD, EYU0TSGR, EYU0TIBS


EYUTS0010E Unable to event sysname. CICSPlexplexname Unknown.

Explanation: A communications endpoint event forthe specified CICS system could not be processedbecause the specified CICSplex, which is the context forthe event, is not known to Topology Services, where:


ConnectA physical connection between the

EYUTS0005E • EYUTS0010E


MAS (CICS system) and itsmaintenance point CMAS.





Module: EYU0TSSC, EYU0TSSJ, EYU0TSST


EYUTS0011E Unable to event sysname. CICS Systemsysname Unknown.

Explanation: A communications endpoint event forthe specified CICS system could not be processedbecause the CICS system, which is the scope for theevent, is not known to Topology Services, where:







Module: EYU0TSSC, EYU0TSSJ, EYU0TSST


EYUTS0012E CICSPlex plexname Not Found.

Explanation: A requested topology action could not beprocessed because the specified CICSplex, which is thecurrent context, is not known to Topology Services.


User response: Make sure the CICSplex name wascorrectly specified. If the CICSplex is known to exist,

examine the exception trace records to determine thecause of the problem.

In a complex CICSplex environment, repeated instancesof message EYUCP0012E and message EYUTS0012Emight be issued by a newly upgraded CMAS. This canbe relieved by recycling the affected CMAS.

Module: EYU0TSFD, EYU0TSGA, EYU0TSGR,EYU0TSPR, EYU0TSPU, EYU0TSSA, EYU0TSSR,EYU0TSSU


EYUTS0013E CICS System sysname Not Found.

Explanation: A requested topology action could not beprocessed because the specified CICS system, which isthe current scope, is not known to Topology Services.


User response: Make sure the CICS system name wascorrectly specified. If the CICS system is known toexist, examine the exception trace records to determinethe cause of the problem.

Module: EYU0TSGR, EYU0TSSR


EYUTS0014E Unable to Connect sysname. No ResourceTopology Collected.

Explanation: An attempt to connect the specified CICSsystem failed because the required resource topologydata was not provided by the MAS.



Module: EYU0TSRA


EYUTS0015I Topology event of CICS System sysnameInitiated.

Explanation: Topology Services has begun processinga CICS system Change event for a CMAS, where:


v Add

v Update

v Remove

sysnameIdentifies the affected CICS system.



EYUTS0011E • EYUTS0015I


Module: EYU0TSSA, EYU0TSSD, EYU0TSSU


EYUTS0016E Topology event of CICS System sysnameFailed.

Explanation: A CICS system Change event thatTopology Services was processing for a CMAS failed tocomplete, where:


v Add

v Update

v Remove






EYUTS0017I Topology event of CICS System sysnameComplete.

Explanation: Topology Services has completed a CICSsystem Change event for a CMAS, where:


v Add

v Update

v Remove






EYUTS0018I Topology event of System Group grpnameInitiated.

Explanation: Topology Services has begun processinga CICS system group Change event for a CMAS,where:


v Add

v Remove

grpnameIdentifies the affected CICS system group.



Module: EYU0TSGA, EYU0TSGD


EYUTS0019E Topology event of System Group grpnameFailed.

Explanation: A CICS system group Change event thatTopology Services was processing for a CMAS failed tocomplete.


v Add

v Remove






EYUTS0020I Topology event of System Group grpnameComplete.

Explanation: Topology Services has completed a CICSsystem group Change event for a CMAS, where:


v Add

v Remove






EYUTS0021E Topology event of CICS System sysnamefailed due to a type Time-Out.

Explanation: An attempt to connect or join thespecified CICS system has failed, where:

event Identifies the event being attempted as eitherConnect or Join.

sysnameIdentifies the CICS system.

type Identifies the type of time-out condition thatoccurred as one of the following:



Resource Topology CollectionA request for resource topology timedout during the connection of a localMAS.

Topology Resource Map GetA request to get topology resourcemaps from a CMAS timed out duringthe joining of a MAS.

System action: The CICS system continues to execute,but it is not known to CICSPlex SM. MAS agent codeis active in the CICS system; however, because of thespecified time-out failure, CICSPlex SM cannot managethe CICS system.

User response: Shut down the affected CICS systemand then restart it.

Module: EYU0TSMJ, EYU0TSRA, EYU0TSSC


EYUTS0023E Topology connect of CICS systemsysname not initiated. CSYSDEF andMAS SysIds mismatch. APPLID (applid)CICSplex (plexname)

Explanation: Topology services could not process aconnect for the specified CICS system because theSYSIDNT specified in the CICS system definition doesnot match that specified for the SYSIDNT SITparameter, where:




System action: Processing continues, however theCICS system cannot be managed by CICSPlex SM.

User response: Either update the CICS systemdefinition, or specify the correct SYSIDNT in the SIT.

Module: EYU0TIST


EYUTS0024I Topology connect for mas waiting forBAS to complete initialization forCICSplex plexname

Explanation: During Topology connect processing fora MAS, where:

mas is the name of the MAS.

it was determined that resources need to be installedby BAS, but BAS has not yet initialized data structuresfor the CICSplex, where:


System action: Connect processing for the MAS willwait until BAS completes initialization of the CICSplex(EYULOG message EYUBI0005I) or the MASinitialization time expires (as specified by theMASINITTIME EYUPARM).

User response: There should not be a need for userresponse unless the MAS connect fails. If the connectprocess fails because BAS initialization for the CICSplex(bracketed by EYULOG messages EYUBI0004I andEYUBI0005I) extends beyond the time allowed for theMAS to initialize (as specified by the MAS'sMASINITTIME EYUPARM), then it may be necessaryto increase the MASINITTIME EYUPARM for the MAS.If the connect process fails because BAS initializationfor the CICSplex failed (message EYUBI0102E), the BASfailure should be pursued according to the commentsfor message EYUBI0102E.

Module: EYU0TSCI


EYUTS0026I User userid has issued theFORCEDISCON action for MASmasname - APPLID(applid)CICSplex(plexname).

Explanation: The specified user has successfullyissued the MAS resource table FORCEDISCON actionagainst the specified MAS. If the user ID is *Internal*,the action was generated as the result of internalCICSPlex SM processing.

System action: The ESSS connection for the MAS isterminated and this message is issued to document therequester of this action.

User response: None, unless the user is *Internal*. Ifso, to determine why the action was issued, collect thecomplete job output and auxtrace data sets from theMAS and the CMAS that issued this message, alongwith any dumps that may have been produced at thistime by the MAS or CMAS, and contact your local IBMSupport Center.

Module: EYU0TSUM


EYUTS0025I Topology Connect|Join for masterminated due to Disconnect request -APPLID(applid) CICSplex(plexname)

Explanation: A Topology Connect or Join request isbeing terminated because a Disconnect request hasbeen received for the MAS during the Connect or Joinprocess.

System action: The Connect or Join request isterminated.

EYUTS0023E • EYUTS0025I


####

####

##

User response: The Disconnect request is due to theMAS being shutdown or the MAS agent beingterminated. If this is not expected, review the job logfor the MAS to determine the reason.

Module: EYU0TSCI , EYU0TSMJ , EYU0TSSC ,EYU0TSSJ


EYUTS0030I Topology RODM Manager registeredwith NetView.

Explanation: The Topology Services long running task(LRT) task has successfully registered with NetView asa sender and receiver program.



Module: EYU0TIRT

Destination: Job log

EYUTS0031I Receiver program for rodmname is active.

Explanation: Topology Services has determined thatthe CICSPlex SM NetView OS task receiver program(EYU9Tnnn) for the specified RODM subsystem isactive, where rodmname is the name of the RODMsubsystem to be populated.



Module: EYU0TIRT


EYUTS0032I NetView subsystem is inactive. Willquery again in 5 minutes.

Explanation: The NetView subsystem is not currentlyactive. Topology Services continues to query NetViewat 5 minute intervals until the subsystem becomesactive.



Module: EYU0TIRT


EYUTS0033I NetView release does not support userrequests.

Explanation: The release of NetView that was foundto be active in the MVS image does not support theCICSPlex SM interface to NetView RODM. TheCICSPlex SM interface requires NetView Version 2.4 orlater.

System action: Topology Services processing

continues. However, no RODM-related requests areaccepted.

User response: If you want to use the CICSPlex SMinterface to RODM, you must upgrade to NetView 2.4or later.

Module: EYU0TIRT


EYUTS0034I Receiver program for rodmname isinactive or undefined. Will query againin 5 minutes.

Explanation: The CICSPlex SM OS task receiverprogram (EYU9Tnnn) for the specified RODMsubsystem is either not currently active or is notdefined to the NetView program-to-program interface(PPI), where:

rodmnameIs the name of the RODM subsystem to bepopulated.

Topology Services continues to query NetView at 5minute intervals until the receiver program becomesactive.



Module: EYU0TIRT


EYUTS0035E Topology RODM Manager NetView PPIrequest failed. Request type=nnnn,RC=rcode.

Explanation: A Topology Services request was sent tothe NetView program-to-program interface, but therequest failed, where:

nnnn Is a numeric identifier for the topology requestthat was issued.

rcode Is the NetView return code.

System action: The Topology Services interface toNetView terminates.

User response: For a description of the NetView PPIreturn code, see the NetView Application ProgrammingGuide. If the cause of the problem is not apparent,collect the CMAS job log and either the NetViewnetwork log or the MVS system log, depending onwhere NetView messages are issued. Then, contactyour IBM Support Center.

Module: EYU0TIRT


EYUTS0030I • EYUTS0035E


####

##

#

EYUTS0036E CMAS cmas at incompatible CPSMversion. RODM reporting negated.

Explanation: The specified CMAS attempted to makecontact with the Topology Services agent for NetView.However, the CMAS is running a different release ofCICSPlex SM than the Topology Services agent, where:

cmas Identifies the CMAS that was trying to contactTopology Services.

System action: The specified CMAS is not known tothe Topology Services agent for NetView. The CMAScannot report to RODM on its resources.

User response: If you want the specified CMAS toparticipate in the RODM interface, it must be runningthe same release of CICSPlex SM as the TopologyServices agent.

Module: EYU0TIRT


EYUTS0050I plexname/sysname restype: resname state<status>

Explanation: The operational state of the specifiedresource is being reported, where:


sysnameIs the name of the CICS system where theresource is defined.

restype Is the type of resource.

resnameIs the name of the resource.

status Is the current operational state of the resource.

Resource status messages such as this are issued whenthe CICSPlex SM system parameter RESSTATUS(MSG)is specified in the CMAS startup job.



Module: EYU0TREH

Destination: EYULOG

EYUTS0051I plexname/sysname restype: resname state<status>

Explanation: The operational state of the specifiedresource is being reported, where:


sysnameIs the name of the CICS system where theresource is defined.

restype Is the type of resource.

resnameIs the name of the resource.

status Is the current operational state of the resource.

Resource status messages such as this are issued whenthe CICSPlex SM system parameterRESSTATUS(CONMSG) is specified in the CMASstartup job.



Module: EYU0TREH

Destination: Job log, console, EYULOG

EYUTS0060I Topology ResMap Hardening longrunning task Initialization Complete

Explanation: The topology services resource maphardening long running task has completedinitialization.



Module: EYU0TSMH

Destination: EYULOG

EYUTS0061I Topology ResMap Hardening longrunning task Termination Complete

Explanation: The topology services resource maphardening long running task has ended.


User response: None if CMAS is being shut down. Ifthe CMAS is not being shut down, take the actionsdescribed by message EYUTS0062E, which should havebeen issued before this message.

Module: EYU0TSMH

Destination: EYULOG

EYUTS0062E Topology ResMap Hardening longrunning task error

Explanation: The topology services resource maphardening long running task has detected an error.

System action: The topology services resource maphardening long running task attempts to continue.After recovering from ten errors, if another erroroccurs, the task is terminated.

User response: Collect the CMAS trace records, joblog and EYULOG, and contact your IBM supportcenter.

Module: EYU0TSMH



Destination: EYULOG

EYUTS0063E Topology encountered an errorprocessing a change to a CICS systemgroup

Explanation: During the processing of an Add orRemove command, to add a CICS region to or removea CICS region from a CICS system group, the CMASencountered an error while performing the topologyupdate for the change.

System action: The data repository update iscomplete, but the topology updates, and any changesthat the monitor, RTA, WLM, and BAS componentsneed to make to support the change, have not beenmade.

User response: A dump is also taken with a dumptitle similar to the following:

EYU0XZPT Dump,cmasjobn,cmasname,lpar,CMAS,TIST,tasknum,TRAC,EYU0TSEC,date,time

Collect the dump, complete job output, and auxtracedata sets for the CMAS, and contact your IBM supportcenter.

Message EYUXD0002E should be issued prior to thismessage, in the CMAS's job log, indicating whichchange was aborted by topology. If this change isrequired during the current run of the CMAS, theCMAS must be restarted. Topology will then properlyprocess the request during CMAS initialization.

Module: EYU0TSEC


EYUTS0063E


####

#####

#####

##

##

###

######

#

#

Chapter 29. EYUTTnnnn messages

EYUTT0001I Topology Termination Complete.

Explanation: The Topology Services component hasbeen terminated.



Module: EYU0TSTM

Destination: EYULOG

EYUTT0002E Topology Termination Failed.

Explanation: An error occurred while attempting toterminate the Topology Services component. Someresources may not have been released.



Module: EYU0TSTM



Chapter 30. EYUVCnnnn messages

EYUVCnnnn messages are Web User Interface client messages reflecting statusduring operation of the interface. They are written to the user's web browser.

EYUVC1000I Signon by User userid successful. Lastaccess at time on date. Your passwordwill expire in nn days.

Explanation: The named user signed on successfullyon the date and time indicated.

System action: The session continues.


Destination: Web browser.

EYUVC1001I Signon by User userid successful. Lastaccess at time on date.

Explanation: The named user signed on successfullyon the date and time indicated.


System programmer response: None.



EYUVC1002I Please enter a User name.

Explanation: A user name is required for signon.

System action: Signon is suspended. An input form ispresented to the user.


User response: Enter your user name into the form,and press “Sign on”.

Destination: Browser.

EYUVC1003I Please enter a password.

Explanation: A password is required for signon.



User response: Enter your password into the formand press “Sign on”.


EYUVC1004E Invalid User name. Please try again.

Explanation: An invalid user name has been enteredinto the signon form.



User response: Enter the correct user name into theform and press “Sign on”.


EYUVC1005E Invalid password. Please try again.

Explanation: An invalid password has been enteredinto the signon form.



User response: Enter the correct password into theform and press “Sign on”.


EYUVC1006E Signon failed because the User nameis revoked.

Explanation: You have attempted to sign on using auser ID which has been revoked by external securitymanager.


System programmer response: Investigate the statusof the user ID in the external security manager, andreinstate if required.

User response: Contact your system administrator.


EYUVC1007E The password has expired. Pleasere-enter the password, enter a newpassword, and verify the new password.

Explanation: Your password has been expired byexternal security manager.



User response: Re-enter your password, enter a newpassword into both the New Password and Verify NewPassword fields, then press “Sign on”.



EYUVC1008E The New Password and Verify NewPassword fields do not match. Please tryagain.

Explanation: You have attempted to change yourpassword, but did not enter the same password in boththe New Password and Verify New Password fields.



User response: Re-enter your old password, enter anew password into both the New Password and VerifyNew Password fields, then press “Sign on”.


EYUVC1009E Signon for User (userid) failed. (CICSinformation: RESP(response1),RESP2(response2),EIBFN(eibfn))(External security managerinformation: ESMRESP(esmresp),ESMREASON(esmreason))

Explanation: The signon process has failed for anunusual reason.

System action: Signon terminates.

System programmer response: Review EIBFN valueand consult the documentation for CICS and theexternal security manager. Collect AUXTRACE andconsole log and contact IBM service if the problemcannot be resolved.



EYUVC1010E The new password was notacceptable. Please try again.

Explanation: You attempted to change the passwordto a value that was rejected by external securitymanager.



User response: Re-enter your password, enter a newpassword into both the New Password and Verify NewPassword fields, then press “Sign on”. Your newpassword must conform to the external securitymanager rules.


EYUVC1011E Unable to create User environment.User already signed on.

Explanation: You attempted to sign on, but a sessionwas already active for the user ID.



User response: Either go back to the web browser onwhich you are currently signed on, or sign on againspecifying the “Reconnect” option.


EYUVC1012E Unable to create User environment.Maximum user limit reached.

Explanation: You attempted to sign on, but the serveralready has the maximum number of users signed on.



Actions to consider include:

v Persuading someone to log off.

v Purging users with COVC if necessary.

v Increasing the value of the MAXUSERS parameter,and restarting the server.


EYUVC1013E Unable to create User environment.Failed to start user task.

Explanation: The signon process has failed.


System programmer response: Refer to associatedmessages that will have been written in EYULOG.



EYUVC1014E Unable to create User environment.Failure during user task creation.

Explanation: The signon process has failed.





EYUVC1008E • EYUVC1014E


EYUVC1015I Signon complete for User (userid).

Explanation: The named user has successfully signedon.





EYUVC1016I Please confirm User name.

Explanation: Signon was started with a user namespecified in the URL. This name must now beconfirmed.



User response: Check (and correct, if required) theuser name in the form and press “Sign on”.


EYUVC1017E User task failed to connect toCICSPlex SM.

Explanation: The signon process has failed because aconnection could not be made to CICSPlex SM for theuser name specified.





EYUVC1018I CICS_good_morning_message

Explanation: The current Web User Interface serverCICS good morning message is displayed in thismessage.

This message can be issued both before and aftersign-on depending on the Web User Interface serverparameter GMMTEXTMSG. You can set theGMMTEXTMSG server parameter to one of thefollowing values:

NO The message is not issued.

YES The message is issued before and aftersign-on.

BEFOREThe message is issued before sign-on.

AFTER The message is issued after sign-on.


System programmer response: None

User response: None


EYUVC1019E Passwords and password phrasescannot be mixed. Try again.

Explanation: You cannot authorize a new passwordwith a password phrase or a new password phrasewith a password.

System action: Sign-on terminates.


User response: Use a password to change a passwordor a password phrase to change a password phrase.

Module: EYU0VPSN


EYUVC1020E The external security managerinterface has not been initialized.Sign-on request failed.

Explanation: The sign-on attempt has failed becausethe external security manager interface has not beeninitialized.


System programmer response: Ensure that theexternal security manager interface has been initialized.

User response: Ask your system administrator toinitialize the external security manager interface.

Module: EYU0VPSN


EYUVC1021E The external security manager iscurrently not accepting sign-on requests.Try again later.

Explanation: The sign-on request has failed becausethe external security manager (ESM) was in a tranquilstate.


System programmer response: Check that the externalsecurity manager is not in a tranquil state and ensurethat it is running correctly so that sign-on can takeplace.

User response: The external security manager hasbeen put into a tranquil state to allow for externalsecurity manager database maintenance. Determinewhether maintenance is currently occurring and howlong it will take. When maintenance is finished thetranquil state should be removed from the externalsecurity manager, which will allow you to sign on. Ifthe external security manager has not been put into atranquil state, contact your security administrator.

EYUVC1015I • EYUVC1021E


||

|||

|

|

||

|

|

|||

|||

|

||

||

|

|

|||

|||

|

||||

|||||||||

Module: EYU0VPSN


EYUVC1023E Incorrect password length. Sign-on isterminated.

Explanation: The value of the password keyword isincorrect. A password must be between 1 and 8characters. A password phrase must be between 9 and100 characters. Your security administrator might havechanged the minimum or maximum lengths.



User response: Enter a password that is of the rightlength. If this still fails, check whether your securityadministrator has changed the minimum or maximumpassword lengths.

Module: EYU0VPSN


EYUVC1024E Incorrect new password length.Sign-on is terminated.

Explanation: The value of the new password keywordor the verify new password keyword is incorrect. Apassword must be between 1 and 8 characters. Apassword phrase must be between 9 and 100characters. Your security administrator might havechanged the minimum or maximum lengths.



User response: Enter a new password or verifypassword of the right length. If this still fails, checkwhether your system administrator has changed theminimum or maximum password lengths.

Module: EYU0VPSN


EYUVC1025E Incorrect user name length. Sign-on isterminated.

Explanation: The value of the user ID keyword isincorrect. A user ID must be between 1 and 8characters.



User response: Enter a user ID of the right length.

Module: EYU0VPSN


EYUVC1026E Incorrect group name length.

Explanation: The value of the group name is incorrect.A group name must be between 1 and 8 characters.

System action: Sign-on continues and the defaultgroup associated with the user ID is used if possible.


User response: Sign off and sign on again with agroup name of the right length if required.

Module: EYU0VPSN


EYUVC1027E Invalid group name specified

Explanation: The value of the group name is invalid.

System action: Sign-on continues and the defaultgroup associated with the user ID is used if possible.


User response: Sign off and sign on again with a validgroup name if required.

Module: EYU0VPSN


EYUVC1028I The password or password phrase hasbeen changed.

Explanation: The password or password phrase waschanged successfully.

System action: Sign-on continues unless a session forthe current user already exists.


User response: No action is required. However, if anexisting user session exists, reattempt the log on usingthe RECONNECT option.

Module: EYU0VPSN


EYUVC1029E Unable to create User environment.User task creation timed out.

Explanation: The sign-on process has failed.


System programmer response: Examine the systemlog for problems that could delay completion of usertask creation.

User response: Retry the sign-on. If this continuesto time out, contact your systemadministrator.

Module: EYU0VPSN




|

|

||

|||||

|

|

||||

|

|

||

||||||

|

|

||||

|

|

||

|||

|

|

|

|

|

|

||

||

|

||

|

|

|

|

||

|

||

|

|

|||

||

||

|

|||

|

|

||

|

|

|||

|||

|

|

EYUVC1100I Signoff request accepted.

Explanation: You have requested to terminate thesession by clicking the “Sign off” link.

System action: The user session will be terminated assoon as possible.


User response: Close the web browser window.


EYUVC1101I Signoff request failed.

Explanation: You have requested to terminate thesession by clicking the “Sign off” link, but your requestcould not be processed correctly.

System action: User session is terminated.

System programmer response: Collect AUXTRACE,console log, and dump information, and contact IBMservice.



EYUVC1102I Press button to begin signon.

Explanation: A request has been made to the WebUser Interface server but the user has not yet beenauthenticated.

System action: A page containing a single button ispresented to the user.


User response: Press the button presented and thensign on using the form that appears.


EYUVC1190W CMAS currently unavailable.

Explanation: The CICSPlex SM CMAS address spacedoes not appear to be available to the interface.Attempts to sign on may fail.

System action: A signon form is presented to the user.

System programmer response: Ensure that the CMASis active and the LMAS component of the Web UserInterface server is connected to it.

User response: Attempt to sign on. If signon attemptscontinue to fail, contact your system administrator.


EYUVC1200E Frame-enabled web browser required.

Explanation: You have attempted to sign on to theWeb User Interface using a web browser that does notsupport frames.

System action: User session has been established butwill remain inactive until the user reconnects with aweb browser with frame support or the session isdestroyed by the inactivity time out.


User response: Use a web browser that supportsframes or review your web browser settings to ensureframe support has not been disabled.


EYUVC1209 E Error formatting Kernel Error data.

Explanation: A response was not received from one ormore MASs in the requested scope, but an erroroccurred when trying to format error messagesEYUVC1293E or EYUVC1294W.

System action: The WUI screen is refreshed with datafrom MASs which did respond.


Administrator response: Collect AUXTRACE recordsfrom the WUI Server and the CMAS, and the WUIServer and CMAS joblogs and contact your IBMSupport Center.

Destination: Browser

Module: EYU0VISE

EYUVC1210E Requested View-set (viewsetname) notavailable.

Explanation: The named view-set was referenced, butwas either not present in the repository, or you are notauthorized to view it.

System action: The view is not displayed.

System programmer response: Check EYULOG forsecurity exceptions, and if necessary revise the user'sauthorization levels.

If there is no security exception, check the view setname. If it is incorrect, use the editor to correct theview or menu link that caused the error, or correct theDEFAULTxxxxxx server parameter, as appropriate. Ifthe view-set name is correct, use the editor to create theview-set, or use the COVC transaction to import froman export file.

User response: Contact your system administrator.Press the Back icon to continue.




EYUVC1211E Requested Menu (menuname) notavailable.

Explanation: The named menu was referenced, butwas either not present in the repository, or you are notauthorized to view it.

System action: The menu is not displayed.


If there is no security exception, check the menu name.If it is incorrect, use the editor to correct the menu linkthat caused the error, or correct the DEFAULTxxxxxxserver parameter, as appropriate. If the menu name iscorrect, use the editor to create the menu, or use theCOVC transaction to import from an export file.



EYUVC1212E A navigation error has occurred.Please use the following link to go backto your current position.

Explanation: You have requested a page out ofsequence, perhaps by using the web browser's Backbutton.

System action: A link is provided to go back to thecurrent page.


User response: Select the link to return to the currentpage.


EYUVC1213E No more windows available. Pleaseclose some windows and try again.

Explanation: You have attempted to open morewindows than are permitted in a single session.



User response: Use a window that is already open, orclose one and try again. If you no longer have thewindows open, sign off, then sign on again.


EYUVC1214E Window closed.

Explanation: The interface has closed the window forwhich the message is displayed.



User response: Close the web browser window.


EYUVC1215E The data required for this printoperation is no longer available.

Explanation: The data used to generate a 'printpreview' window is no longer available because thewindow from which the request was generated hasbeen used subsequently.

System action: The request is ignored and the sessioncontinues.


User response: Close the web browser windowcontaining the message. If a printed display is required,open a new 'print preview' for your required displayand use the web browser to print the page before usingthe window from which the request is generated.


EYUVC1216E Requested View (viewname) notavailable.

Explanation: The named view was referenced, butwas not present in the view-set.


System programmer response: If the view name isincorrect, use the editor to correct the view or menulink that caused the error.

If the view name is correct, then use the editor to createthe view within the view-set.



EYUVC1217E Object (objectname) used in View set(viewsetname) is not recognized in thisrelease of CICSPlex SM.

Explanation: The named view set was created for anobject that is not known. For example, the view setmay have been created on another release of CICSPlexSM.


System programmer response: Verify that CICSPlexSM and the Web User Interface is running at the correctrelease. Use the View Editor to delete the view set, ifnecessary.

Collect the exported view set definition, AUXTRACE,console log, and dump information, and contact IBMservice if the problem cannot be resolved.





EYUVC1219E Requested View set or Menu (name) inrepository contains an invalid versionidentifier

Explanation: The requested view set or menu cannotbe displayed because it contains a version identifierthat does not match the current version of CICSPlexSM.

System action: The view set or menu is not displayed.

System programmer response: Ensure that the WebUser Interface server repository has been correctlymigrated to the current version of CICSPlex SM.


EYUVC1220E CICSPlex SM API command(commname) failed. (apiresponse, apireason)

Explanation: The interface experienced an unexpectedresponse from a CICSPlex SM API command.


System programmer response: Review theCICSPlex SM API response and reason codes and anyassociated messages in the EYULOG to determine thecause of the problem. Collect AUXTRACE, console log,and dump information, and contact IBM service if theproblem is not resolved.



EYUVC1221E CICSPlex SM not available becausethe CMAS has disconnected.

Explanation: The interface has lost contact with theCMAS.

System action: The session continues but will beterminated shortly.


User response: Sign off from the interface and sign onwhen the CMAS becomes available again.


EYUVC1222E Possible navigation error. Parent stubinvalid.

Explanation: The interface detected a problem ininternal integrity.

System action: The session continues but maycontinue to have problems.

System programmer response: Collect AUXTRACE,console log, and dump information, and contact IBMservice.

User response: Contact your system adminstrator.Sign off from the interface and try again.


EYUVC1223E Unable to start Editor. User notauthorized.

Explanation: You attempted to access the View Editor,but your user ID was rejected by the external securitymanager.

System action: The session continues but View Editoraccess is denied.

System programmer response: Add the user into theView Editor external security manager profile if theuser is to be given access to the View Editor.

User response: Contact your system adminstrator.


EYUVC1224E A submit error has occurred. Use thefollowing link to go back to yourcurrent position.

Explanation: You have submitted a page without anassociated action, perhaps by pressing the enter key ina text box rather than selecting a button..

System action: A link to the current page is provided.


User response: Select the link to return to the currentpage.


EYUVC1225E Requested user group or userprofilename in repository contains aninvalid version number

Explanation: During sign on, the Web User Interface'sattempt to retrieve information from the user profile oruser group profile profilename failed because the versionnumber associated with the object in the repository isnot valid.

System action: Sign on continues.

If the message relates to a user group profile, thedefaults specified as Web User Interface parameters areused for this session.

If the message relates to a user profile, user favoritesare not available during this session.






EYUVC1227W Not connected to requested groupgroup1. Default group group2 used.

Explanation: During sign on, the Web User Interfaceuser specified group group1 on the sign on screen. Thespecified group group1 is not used because the user IDis not connected to group1

System action: The sign on continues, but the WebUser Interface will attempt to use the user's defaultgroup group2 as the name of the Web User Interfaceuser group profile.

System programmer response: Contact the securityadministrator to check that the group1 group specifiedis appropriate and that the user ID is connected to thatgroup.

The sign on group option is available to Web UserInterface users only if the Web User Interface systemparameter SIGNONPANEL is set to ENHANCED. Ifthe group option is not required, set SIGNONPANEL toBASIC.

User response: If the default user group profile is notappropriate, sign off the Web User Interface and specifya group on the sign on screen that your user ID isconnected to.


EYUVC1228E Select an object before clicking theopname button.

Explanation: You have attempted to initiate a mapoperation before selecting one or more objects as astarting point.

System action: The tabular or detailed view isredisplayed.


User response: Select one or more objects then clickMap to retry the operation.


EYUVC1229E Select an object before clicking theopname icon.

Explanation: You have attempted to initiate a mapoperation before selecting an object as a starting point.opname identifies the operation as map left or mapright.

System action: The map screen is redisplayed.


User response: Select an object then click Map left orMap right to retry the operation.


EYUVC1230I 'externact' (apiact) request completedsuccessfully for nn records.

Explanation: The request to perform an action onmanaged resources completed successfully, where:

v externact is the external description of the action.

v apiact is the API action name.

v nn is the number of records processed.




Destination: Web browser

EYUVC1231E 'externact' (apiact) request failed.Request was for nn records(apiresponse, apireason)

Explanation: The request to perform an action onmanaged resources failed.

System action: Additional messages may follow withmore information. The session continues, but an actionmay be partially complete.

System programmer response: Consult theCICSPlex SM Application Programming Referencebook for a description of the API response and reasoncodes.

User response: Use the following messages todetermine the nature of the problem. Contact thesystem administrator if the problem cannot be resolved.


EYUVC1232E Please select one or more objects tochange before pressing the ‘externact'button.

Explanation: An action button was pressed with noobjects selected.

System action: The action is not performed and thesession continues.


User response: If you wish to perform the action,select one or more objects before pressing the buttonagain.


EYUVC1233E Attribute (attrname) not valid forObject (objname)

Explanation: A view definition named an invalidattribute for the object in this release of CICSPlex SM.


EYUVC1227W • EYUVC1233E


System programmer response: Use the View Editor tocorrect the view definition.



EYUVC1234E Attribute (attrname) cannot be alteredfor Object (objname).

Explanation: A view definition named an attributewhich cannot be set for this release of CICSPlex SM.





EYUVC1235E Parameter (parmname) is not valid forAction (action) of Object (objname).

Explanation: A view definition named a parameterwhich does not exist for this release of CICSPlex SM.





EYUVC1236E Parameter (parmname) hasunrecognized type for Action (action) ofObject (objname).

Explanation: A view definition named a parameterwhich has an invalid specification.


System programmer response: Use the View Editor toremove the parameter from the view definition. ContactIBM service.



EYUVC1237E Parameter (parmname) is not valid forAction (action) of Object (objname).

Explanation: A view definition named a parameterwhich does not exist for this release of CICSPlex SM.





EYUVC1238E Parameter (parmname) hasunrecognized type for Action (action) ofObject (objname).

Explanation: A view definition named a parameterwhich has an invalid specification.


System programmer response: Use the View Editor toremove the parameter from the view definition. ContactIBM service.



EYUVC1239E No Attribute values altered. Action(action) not performed.

Explanation: You attempted to perform an action onan object but no attributes were selected for the action.



User response: Select attributes for update beforeretrying the action.


EYUVC1240E Invalid value entered for Attributeattribute. Action action not performed.

Explanation: You attempted to perform an action onan object but an invalid attribute value was selected forthe action.



User response: Enter a valid value for the attributebefore retrying the action.


EYUVC1241E Invalid value entered for Parameterparameter. Action action not performed.

Explanation: You attempted to perform an action onan object but an invalid parameter value was enteredfor the action.





User response: Enter a valid value for the parameterbefore retrying the action.


EYUVC1243E The requested map mapname is notavailable. No map hyperlinks will bedisplayed.

Explanation: The map mapname was referenced butwas not available from the repository.

System action: The map hyperlinks are not displayed.

System programmer response: Check the map name.If it is incorrect, use the editor to correct the user groupprofile, or correct the DEFAULTMAxxx serverparameter, as appropriate. If the map name is correct,use the editor to create the map, or use the COVCtransaction to import from an export file.



EYUVC1245E The requested map mapname in therepository contains an invalid versionidentifier. No map hyperlinks will bedisplayed.

Explanation: The map mapname cannot be displayedbecause it contains a version identifier that does notmatch the current version of CICSPlex SM.





EYUVC1246E The requested map mapname is notavailable because the user is notauthorized. No map hyperlinks will bedisplayed.

Explanation: The map mapname was referenced butyou are not authorized to view it.





EYUVC1247E Invalid character (%0) has beenentered for attribute (%1) at characterposition (%2)

Explanation: A syntax error has been detected.

System action: The requested operation is notperformed.


User response: Correct the syntax error. The trace flagsyntax rules are:

v Specify bits either singly or as a sequence:

– To turn bits 1, 5 and 12 on, enter 1, 5, 12.

– To turn on bits 1, 2, and 3, enter 1-3.

v Bit numbers are valid only in the range 1 to 32.

v Single bits and bit sequences must always beseparated by a comma.

v Start and end the input sequence with a bit number;for example 1, 5-8 is valid but both ,1, 5-8 and 1, 5-8,are not.

v Spaces are allowed but can only precede or follow acomma, except for the first bit, which may havepreceding spaces.

v Single bits can be specified in any order butsequences must be specified in order; for example 1-3is valid but 3-1 is not.

v The bits numbers in a sequence cannot be the same.

v All bits can be disabled either by leaving the fieldempty or by entering blanks.

v Type 1-32 in a field to enable all bits.


EYUVC1248E Bit number (%0) is out of range forattribute (%1) at character position (%2).Bits should be within the range 1-32.

Explanation: An out of range error has been detected.



User response: Correct the out of range error. Thetrace flag syntax rules are:


– To turn bits 1, 5 and 12 on, enter 1, 5, 12.

– To turn on bits 1, 2, and 3, enter 1-3.








v The bits numbers in a sequence cannot be the same.

v All bits can be disabled either by leaving the fieldempty or by entering blanks.



EYUVC1249E Invalid bit sequence entered forattribute (%0) at character position (%1).

Explanation: A bit sequence that does not conform tothe required syntax has been detected.



User response: Correct the bit sequence syntax. Thetrace flag syntax rules are:


– To enable bits 1, 5 and 12, enter 1, 5, 12.

– To enable bits 1, 2, and 3, enter 1-3.






v The bit numbers in a sequence cannot be the same.All bits can be disabled by either leaving the fieldempty or by entering blanks.



EYUVC1250E Attributes cannot be altered for thisObject (objname).

Explanation: You attempted to update attributes foran object which does not support the SET action forthis release of CICSPlex SM.


System programmer response: Use the View Editor to

remove the offending action button from the viewdefinition.



EYUVC1251E Object (objname) is not recognized inthis release of CICSPlex SM.

Explanation: You attempted to perform an action foran object which is not present in this release ofCICSPlex SM.


System programmer response: Use the View Editor tocorrect the view.



EYUVC1252E Invalid Action name specified onView.

Explanation: The name of the action which youattempted to perform is not valid in CICSPlex SM.


System programmer response: Use the View Editor toreview the view definition.



EYUVC1253E Action (action) not available forObject (objname).

Explanation: You attempted to perform an actionwhich is not supported by the object in this release ofCICSPlex SM.


System programmer response: Use the View Editor toreview the view definition.



EYUVC1254I Operation canceled for remainingselections.

Explanation: You selected "No to all" on theconfirmation panel.

System action: The action is not performed for theremaining selected objects, and the session continues.


EYUVC1249E • EYUVC1254I




EYUVC1255I Operation not performed for previousselection.

Explanation: You selected “No” on the confirmationpanel.

System action: The action has not been performed forthe previous selected object. The confirmation panel ispresented again for any remaining selected objects. Thesession continues.




EYUVC1258W This action may produce a result setcontaining n entries. The warningthreshold is n. Click Refresh to retrywith different filters or click OK toproceed

Explanation: The action you have initiated mayproduce a large amount of data and could take sometime to process.

System action: The WUI waits for your response.

System programmer response: The potential resultsset is larger than the value set on the default warningcount (DEFAULTWARNCNT) parameter or as definedin user group profile settings . If users are receiving alot of these messages, you may want to check that thisparameter is set appropriately.

User response: Click OK to proceed with therequested action or Refresh to amend the filters.


EYUVC1261E Attribute (attrname) not found forObject (objname).

Explanation: A request for a filtered view specified anattribute name which is not present in the object in thisrelease of CICSPlex SM.

System action: The request is canceled but the sessioncontinues.

System programmer response: Use the View Editor toreview the definition of the hyperlink that caused theerror.



EYUVC1262E Parameter (parmname) not valid forObject (objname).

Explanation: A request for a filtered view specified aparameter which is not supported by the object in thisrelease of CICSPlex SM.

System action: The request is canceled but the sessioncontinues.

System programmer response: Use the View Editor toreview the definition of the hyperlink that caused theerror.



EYUVC1263E Attribute (attrname) filter containsinvalid data.

Explanation: A request for a filtered view specified aninvalid attribute filter value.

System action: The requested display is presented tothe user with no data records.

System programmer response: Use the editor toreview the filters specified on the link used and correctif necessary.

User response: Review the filter values and correct asnecessary. If the problem cannot be resolved, contactyour system administrator.


EYUVC1264E Parameter (parmname) filter containsinvalid data.

Explanation: A request for a filtered view specified aninvalid parameter filter value.



User response: Review the filter values and correct asnecessary. If the problem cannot be resolved, contactyour system administrator.


EYUVC1265E Attribute (attributename) is notsupported as a filter.

Explanation: A request for a filtered view specified anattribute filter which is not supported. For example, ahidden character attribute cannot be used as a filter.

System action: The requested display is not presentedto the user.

System programmer response: Use the editor to



review the filters specified on the link used and correctif necessary.

User response: If the problem resulted from selectinga link on a view or menu then select the Back icon tocontinue and contact your system administrator. If theproblem resulted from entering URL request to the WebUser Interface then review the attribute filters specified.


EYUVC1267E Request denied as this action mayproduce a result set containing <n1>entries which exceeds the threshold of<n2>. After modifying the filters, clickrefresh to retry.

Explanation: The action you have initiated mightproduce n1 records. Your Web User Interfaceadministrator has determined that you can processrequests only up to n2 records.

System action: The WUI waits for a response.

System programmer response: The potential result setis larger than the default warning count value. If usersare receiving a lot of these messages, consider checkingthat this value is set appropriately.

User response: Either amend the filters and clickREFRESH to retry the request, or click CANCEL toreturn to the previous view or menu.


EYUVC1266E Field length exceeded for attribute'attributedesc' (attributename).Maximum length maxlen. Action(actionname) not performed.

Explanation: A request to perform action actionnamewas attempted. This request has failed as attribute'attributedesc' exceeds the maximum allowed length ofmaxlen characters.



User response: Enter a valid value for the attributebefore retrying the action.


EYUVC1268I CICS information: EIBFN(eibfn -eibfn_name) RESP (resp - resp_name)RESP2 (resp2)

Explanation: This message provides CICS relatedinformation about a previous error as follows:

eibfn Identifies the failing CICS command EIBfunction code.

eibfn_nameIdentifies the failing CICS command namecorresponding to eibfn

A value of N/A is displayed if the eibfn valuecannot be resolved by the release of CICSsupporting the WUI server.

resp Identifies the failing CICS numerical (decimal)EIB RESP condition.

resp_nameIdentifies the failing CICS EIB RESP conditionname

A value of N/A is displayed if the resp valuecannot be resolved by the release of CICSsupporting the WUI server.

resp2 Identifies the failing CICS numerical (decimal)EIB RESP2 value.


User response: Use eibfn_name and resp_name todetermine the failing command and condition. Iffurther information is required, see the CICSInformation Center.


EYUVC1270I Action (action) failed for 'objname' in'cicsregion'. Expln (CICS information:RESP(response1) RESP2(response2)EIBFN(eibfn))

Explanation: This message provides additionalinformation following message EYUVC1231E. It isissued for each object for which CICS reported afailure. The Expln field describes the response reportedby CICS. This can be one of the following:

v Invalid request.

v Failure.

v Data set name not found.

v Duplicate record.

v ‘END' condition not handled.

v File not found.

v Illegal login condition not handled.

v I/O error on output data set.

v Journal ID error.

v Length error.

v Model ID error.

v No temporary storage available.

v No storage available.

v Not authorized.

v Not found.

v Partner ID error.

v Program ID error.

v Queue ID error.

EYUVC1267E • EYUVC1270I


#####

####

#

####

###

#

####

####

##

#

##

#

v System busy.

v System ID error.

v Task ID error.

v Task class ID error.

v Terminal ID error.

v Transaction ID error.

v User ID error.

v Volume ID error.

v Invalid exit request.





EYUVC1271I Action (action) failed due to attribute,'description'(attrname).

Explanation: This message provides additionalinformation following messages EYUVC1231E andEYUVC1278E. It is issued for each Attribute whichcontributed to the failure and contains the Attribute'sname (attrname) and description. If messageEYUVC1231E is reporting a parameter error, thismessage just reports which record is affected.





EYUVC1272I Action (action) failed. explanation (errcode).

Explanation: This message provides additionalinformation following message EYUVC1231E andEYUVC1278E. It is issued for each individual failure.The explanation field describes the error code (errcode)reported by CICSPlex SM.





EYUVC1273I Action (action) failed for 'resourcename'(resourcetype) version resourceversion, in'cicsregion'. resp1explanation (CICSinformation: RESP(resp1) RESP2(resp2hi,resp2lo) EIBFN(eibfn))

Explanation: This message provides additionalinformation following message EYUVC1231E. It isissued for each object for which CICS reported a failurewhen attempting to install CICS resources or BASobjects. The resp1explanation field describes the response

reported by CICS. This is one of the following:

v Invalid request.

v Failure.

v Data set name not found.

v Duplicate record.

v ‘END' condition not handled.

v File not found.

v Illegal login condition not handled.

v I/O error on output data set.

v Install not supported.

v Journal ID error.

v Length error.

v Model ID error.

v No temporary storage available.

v No storage available.

v Not authorized.

v Not found.

v Partner ID error.

v Program ID error.

v Queue ID error.

v System busy.

v System ID error.

v Task ID error.

v Task class ID error.

v Terminal ID error.

v Transaction ID error.

v User ID error.

v Volume ID error.

v Invalid exit request.



User response: See CICS System Programming Referencefor an explanation of EXEC CICS CREATE responsecodes.


EYUVC1274I Action (action) failed due to inconsistentscope involving 'cicsregion'.binconscerrcodeexplanation (Target details:scope 'targetscope', resource assignment'targetassignment', resource description'targetdescription'. Related details: scope'relatedscope', resource assignment'relatedassignment', resource description'relatedescription'.)

Explanation: This message provides additionalinformation following message EYUVC1231E. Therequested action is checked to ensure that the targetand related scope values are not in conflict with each

EYUVC1271I • EYUVC1274I


other. CICSPlex SM flags the target and related scopesas inconsistent if:

v There is any overlap between the two (for example,the same CICS system is in both scopes)

The related scope is anything other than a singleCICS system for which a system ID is defined

It is issued for each object for which CICS reported aninconsistent scope error.

System action: The action is not performed for theindicated resource. This does not affect action requestsalready performed. Any subsequent actions are held aspending.


User response: None


EYUVC1275I Action (action) failed due to inconsistentresource set in 'cicsregion'

Explanation: This message provides additionalinformation following message EYUVC1231E if anaction fails due to an inconsistent resource set error.CICSPlex SM flags a resource set as inconsistent if aresource being added or updated is in conflict with aresource that already exists in the CICS system. Forexample, this could occur if an attempt is made to:

v Assign different versions of the same resource to thesame CICS system.

Assign a resource to the same CICS system as bothlocal and remote.

System action: The session continues. This message isfollowed by one or more pairs of messages EYUVC1276and EYUVC1277.


User response: None


EYUVC1276I Candidate resource details: name'candname' (candtype), version 'candver',resource group 'candrgrp', resourceassignment 'candrasg', resourcedescription 'candrdsc', usage 'candusage',system group 'candsgrp', system type'candtype', assignment override'candasgovr'

Explanation: This message is issued followingmessage EYUVC1275I to provide additionalinformation about the candidate resource involved inan inconsistent resource set error.

System action: The session continues. This message isalways accompanied by message EYUVC1277.


User response: None

Destination:

EYUVC1277I Existing resource details: name'existname' (existtype), version 'existver',resource group 'existrgrp', resourceassignment 'existrasg', resourcedescription 'existrdsc', usage 'existusage',system group 'existsgrp', system type'existtype', assignment override'exisrasgovr'

Explanation: This message is issued followingmessage EYUVC1275I to provide additionalinformation about the existing resource involved in aninconsistent resource set error.

System action: The session continues. This message isalways accompanied by message EYUVC1277.

User response: None


EYUVC1278E Unable to obtain data for requestedView. externact (apiact) request failed.(apiresponse, apireason).

Explanation: The CICSPlex SM request used to obtainthe data for the requested view failed.

v externact and apiact describe the CICSPlex SM APIrequest that failed

v apiresponse and apireason are the CICSPlex SM APIresponse and reason codes.

System action: The data for the requested view is notdisplayed.

System programmer response: See the CICSPlexSystem Manager Application Programming Reference for adescription of the API response and reason codes.

User response: Use the subsequent messages todetermine the nature of the problem. Often the error iscaused by an invalid value in a filter attribute or Viewparameter field


EYUVC1279I CICS information: EIBFN(eibfn -eibfn_name) RESP (resp - resp_name)RESP2 (resp2Hi, resp2Lo)

Explanation: This message provides CICS relatedinformation about a previous error as follows:

eibfn Identifies the failing CICS command EIBfunction code.

eibfn_nameIdentifies the failing CICS command namecorresponding to eibfn



A value of N/A is displayed if the eibfn valuecannot be resolved by the release of CICSsupporting the WUI server.

resp Identifies the failing CICS numerical (decimal)EIB RESP condition.

resp_nameIdentifies the failing CICS EIB RESP conditionname

A value of N/A is displayed if the resp valuecannot be resolved by the release of CICSsupporting the WUI server.

resp2Hi Identifies the failing CICS numerical (decimal)EIB RESP2 high-order half-word value.

resp2Lo Identifies the failing CICS numerical (decimal)EIB RESP2 low-order half-word value.


User response: Use eibfn_name and resp_name todetermine the failing command and condition. Iffurther information is required, see the CICSInformation Center.


EYUVC1280I count records collected at time.

Explanation: This message indicates how manyrecords the CICSPlex SM API returned to the Web UserInterface server and the (local) Web User Interfaceserver time at which the records were collected. Thenumber of records may not be the number of recordsavailable on the current view, for example on asummary or detail view the number of recordscollected may be greater than the number of recordsavailable for display.





EYUVC1281W The specified CMAS context(CMAScontext) is not available.

Explanation: The requested resource could not bedisplayed as the specified CMAS context is notavailable to this Web User Interface server.


System programmer response: If the CMAS context isincorrect, use the editor to correct the value in linkused, or correct the DEFAULTCMASCTXT serverparameter, as appropriate. If the CMAS context iscorrect, ensure that the specified CMAS context isavailable to the CICSPlex SM API from Web UserInterface server.

User response: Review the CMAS context and, if theinput field is available, correct as necessary. See theWeb User Interface help page Filtering Data UsingSelection Criteria for more information. If the problemcannot be resolved, contact your system administrator.Press the Back icon to continue.


EYUVC1282W The specified Context (context) is notavailable, or is not a CICSPlex.

Explanation: The requested resource could not bedisplayed as the specified Context is not available tothis Web User Interface server.


System programmer response: If the Context isincorrect, use the editor to correct the value in linkused, or correct the DEFAULTCONTEXT serverparameter, as appropriate. If the Context is correct,ensure that the specified Context is available to theCICSPlex SM API from Web User Interface server.

User response: Review the Context and, if the inputfield is available, correct as necessary. See the Web UserInterface help page Filtering Data Using Selection Criteriafor more information. If the problem cannot beresolved, contact your system administrator. Press theBack icon to continue.


EYUVC1283W The specified Scope (scope) is notavailable for this Context (context).

Explanation: The requested resource could not bedisplayed as the specified Scope is not available withinthe specified Context.


System programmer response: If the Context or Scopeare incorrect, use the editor to correct the value in linkused, or correct the DEFAULTCONTEXT andDEFAULTSCOPE server parameters, as appropriate. Ifthe Context and Scope are correct, ensure that thespecified Scope is defined to the specified Context.

User response: Review the Context and Scope and, ifthe input fields are available, correct as necessary. Seethe Web User Interface help page Filtering Data UsingSelection Criteria for more information. If the problemcannot be resolved, contact your system administrator.Press the Back icon to continue.


EYUVC1280I • EYUVC1283W


EYUVC1284E The specified Attribute filter isinvalid.

Explanation: The requested resource could not bedisplayed as a specified filter was invalid. For example,you may have attempted to use an invalid genericcharacter such as the plus sign (+) or asterisk (*) in anattribute filter in a WLM active view.



User response: Review the filter values and correct asnecessary. See the Web User Interface help pageFiltering Data Using Selection Criteria for moreinformation. If the problem cannot be resolved, contactyour system administrator.


EYUVC1285E The specified Parameter filter isinvalid or is required and missing

Explanation: The requested resource could not bedisplayed as a specified filter was invalid or missing.



User response: Review the filter values and correct asnecessary. See the Web User Interface help pageFiltering Data Using Selection Criteria for moreinformation. If the problem cannot be resolved, contactyour system administrator.


EYUVC1286W The CMAS to which the request isdirected is not available.

Explanation: The requested resource could not bedisplayed because the required CMAS could not befound or contacted.


System programmer response: Use the editor toreview the filters specified on the link used and correctif necessary. If the filter values are correct, check thestatus of the CMAS network.

User response: Review the filter values and correct asnecessary. If the filter values are correct, check thestatus of the CMAS network. If the problem cannot beresolved, contact your system administrator.


EYUVC1287W The workload to which the request isdirected is not available.

Explanation: The requested resource could not bedisplayed because the named workload does not exist,or the CMAS required to operate on the workloadcould not be contacted.


System programmer response: Use the editor toreview the filters specified on the link used and correctif necessary. If the filter values are correct, check thestatus of the workload and the CMAS network.

User response: Review the filter values and correct asnecessary. If the filter values are correct, check thestatus of the workload and the CMAS network. If theproblem cannot be resolved, contact your systemadministrator.


EYUVC1288W The requested resource is notsupported by any available MASs in thespecified scope.

Explanation: The requested resource could not bedisplayed because either none of the MASs within thespecified scope are available or none of them supportthe requested resource object.



User response: Review the filter values and correct asnecessary. See the CICSPlex System Manager Web UserInterface Guide for more information. If the filter valuesare correct, check the status of the MASs within thescope and that the requested resource is available onthose releases.


EYUVC1289W Review the filters and click OK toconfirm this action

Explanation: A filter confirmation screen is beingdisplayed for you to review and confirm the currentfilter criteria.

System action: The WUI displays the filterconfirmation screen and waits for a response.


User response: Review the filter values and amend asnecessary. Click OK to continue.


EYUVC1284E • EYUVC1289W


EYUVC1290I Action (action) failed. Record updated byanother user or application.

Explanation: An attempt to update or remove adefinition has failed because the definition wasupdated by another user or application while therecord was being viewed.

System action: The action fails.


User response: If you wish to retry the action, firstrefresh the view to display the updated definition.


EYUVC1291E Action (action) failed. Maintenancepoint not available.

Explanation: An attempt to create, update, or removea definition has failed because the maintenance pointCMAS for the CICSPlex is not available. Either themaintanance point CMAS itself, or the link to it, hasfailed.

System action: The action fails.

System programmer response: Ensure that themaintenance point CMAS is active and linked to theWeb User Interface CMAS.

User response: Wait for the maintenance point CMASfor the CICSPlex to become available, then retry theaction. If necessary, contact your system administrator.


EYUVC1293 E No response received from CMAScmasname Reason: Reason Text (ReasonCode ).

Explanation: One or more MASs attached to a remoteCMAS did not respond because of a problemcommunicating with the remote CMAS.

System action: The WUI screen is refreshed with datafrom MASs which did respond.

User response: Retry the request. If the problempersists, contact your system administrator.

Administrator response: Review any messages writtento the console or to the EYULOGs of the CMASs.


Module: EYU0VISZ

EYUVC1294W No response received from MASmasname Reason: Reason Text (ReasonCode)

Explanation: A response was not received from one ormore MASs in the requested scope, because ofproblems communicating with the MAS or executingthe request in the MAS.

System action: The WUI screen is refreshed with datafrom MASs that did respond.

System programmer response: Review any messageswritten to the console or to the EYULOGs of theCMASs.

User response: Retry the request. If the problempersists, contact your system administrator.


EYUVC1300I Processing request. Please wait.

Explanation: The requested action has not completedwithin a period of time. Normally, this will be due toother activity in the systems being managed.

System action: Processing continues. The results willbe displayed when the request is completed.

System programmer response: Review any messagesthat may have been written to the console andEYULOG. If there are errors from the external securitymanager then ensure that the user has been given thecorrect authority to sign on to the Web User Interface.

User response: If your request does not completewithin several minutes then contact your systemadministrator.


EYUVC1310I Add to favorites operation canceled.

Explanation: You have clicked Cancel on an Add tofavorites screen. No updates have been saved.

System action: The previous WUI screen isredisplayed.


User response: None


EYUVC1311I Add to favorites operation forfavoritename complete.

Explanation: You have successfully added a screen toyour favorites menu.

System action: The screen you have selected as afavorite is redisplayed. A hyperlink to this screen nowappears in your favorites menu.


User response: None




EYUVC1312W User (userid) is being updated byanother user. You may not alter yourfavorites.

Explanation: An attempt to acquire your favorites hasfailed because another user is updating them. You areunable to edit your favorites until the lock is released.

System action: Processing continues. When the lock isreleased, message EYUVC1314I is issued.


User response: None


EYUVC1313E Repository not available or notauthorized for user.

Explanation: An attempt add to your favorites hasfailed because the repository is not available or you donot have the necessary authorization to access it.

System action: The favorites operation fails. Otherprocessing continues.




EYUVC1314I You currently do not have any favorites.

Explanation: You have successfully signed on but youdo not have any user favorites.

System action: Processing continues. No Favoritesgroup is displayed on the navigation menu.


User response: Click on an add to favorites icon in thenavigation frame to create your first user favorite andto create a user object in the repository.


EYUVC1315I Attribute, attributename, has beensuccessfully updated.

Explanation: You have selected a new value forattribute attributename from a dynamic selection list andthe attribute has been updated successfully.

System action: The WUI screen is redisplayedshowing the updated value for the attribute.


User response: None


EYUVC1316I Parameter, parameter, has beensuccessfully updated.

Explanation: You have successfully chosen aparameter from the pick list.



User response: None


EYUVC1317I Attribute, attributename, has not beenupdated.

Explanation: You have clicked Cancel on an Attributeselection screen. Attribute attributename has not beenupdated.

System action: The WUI screen is redisplayed.


User response: None


EYUVC1318I Parameter, parameter, has not beenupdated.

Explanation: You have cancelled the parameterselection.



User response: None


EYUVC1319E A value must be selected beforeclicking the OK button.

Explanation: You must select a value from the pick listbefore clicking the OK button.



User response: Select a value and click OK, or clickCancel to return to the previous screen.


EYUVC1321E A menu item title is required. Itcannot be blank.

Explanation: You attempted to create a favorite with ablank title. Menu items that are part of your favoritesmust have a valid title.



EYUVC1312W • EYUVC1321E


User response: Enter a valid title for the menu item.


EYUVC1380I recordnum records expanded at datetime.

Explanation: This message indicates the number ofrecords displayed on a view following an expandoperation. datetime indicates the date and time whenthe expansion took place.





EYUVC1380I


Chapter 31. EYUVEnnnn messages

EYUVEnnnn messages are issued by the Web User Interface view and menu editor.

EYUVE1001E An unrecoverable editor error hasoccurred (Screen number screennumber).

EYUVE1002E Invalid editor request (Screen numberscreennumber).

EYUVE1003E Repository not available or notauthorized for User.

EYUVE0011E New Menu contains invalid characters.Please enter a new Menu name.

EYUVE0012E Menu (menuname) already exists. Pleaseenter a new Menu name.

EYUVE0014I The Menu (menuname) has been created.

EYUVE0015E No Menu name specified. Please entera new Menu name.

EYUVE0016E Menu names starting with 'EYU' arereserved and cannot be created.

EYUVE0017E You are not authorized to create amenu with this name (menuname).

EYUVE0021E New Menu name contains invalidcharacters. Please enter a new Menuname.

EYUVE0022E Menu (menuname) already exists. Pleaseenter a new Menu name.

EYUVE0024E Source Menu (sourcemenuname) notfound. Please select a source Menuname.

EYUVE0025I Menu (sourcemenuname) has been copiedas new Menu (targetmenuname).

EYUVE0026E No source Menu selected. Please selecta source Menu name.

EYUVE0027E No Menu name specified. Please entera new Menu name.

EYUVE0028E Menu names starting with 'EYU' arereserved and cannot be created.

EYUVE0029E You are not authorized to create amenu with this name (menuname).

EYUVE0033E No Menu selected. Please select aMenu name.

EYUVE0034E Menu may not be deleted as it eitherstarts with EYU or is locked.

EYUVE0040E Menu (menuname) not found. Pleaseselect a Menu name for deletion.

EYUVE0041I Menu (menuname) has been deleted.

EYUVE0042E Unable to delete Menu (menuname) asit is being updated. Please select aMenu name for deletion.

EYUVE0043E You are not authorized to delete amenu with this name (menuname)

EYUVE0048E No Menu selected. Please select aMenu name.

EYUVE0050I Menu (menuname) has been opened foredit.

EYUVE0051E Unable to edit Menu (menuname) as itis already being updated by anotheruser (userid). Please select a Menu namefor edit.

EYUVE0052W Menu may not be altered as it eitherstarts with EYU or is locked. You willnot be able to save any changes.

EYUVE0053E Unable to edit Menu (menuname) asthe repository record contains an invalidversion identifier. Please select a Menuname for edit.

EYUVE0054E You are not authorized to update amenu with this name (menuname)


EYUVE0060E Save of Menu (menuname) failed.Updates have been lost.

EYUVE0061I Menu (menuname) updates savedsuccessfully.

EYUVE0067I Menu title and annotation have beenedited.

EYUVE0073I Context and Scope options have beenedited.

EYUVE0101E Help location invalid or containsinvalid characters. Please enter a validhelp location.

EYUVE0102E Help location not specified. Pleaseselect, and enter a help location.

EYUVE0103I Help location has been edited.

EYUVE0109I Menu contents have been edited.

EYUVE0110E Menu item not specified. Please selecta Menu item.

EYUVE0111E A menu item title is required. It cannotbe blank.

EYUVE0116E Menu item type not specified. Pleaseselect a Menu item type.

EYUVE0122I Menu group title has been edited.

EYUVE0128I Menu choice title and annotation havebeen edited.

EYUVE0134I Menu choice components have beenedited.

EYUVE0141I Menu item, 'menuitemname', has beendeleted.

EYUVE0142I Menu item, 'menuitemname ', has beenmoved.

EYUVE0144I Menu item, menuitemname, has beencopied as new menu item,'menuitemname'.

EYUVE0147E Menu choice type not specified. Pleaseselect a Menu choice type.

EYUVE0148I Link to Menu created.

EYUVE0149I Link to external URL created.

EYUVE0150I Link to View created.

EYUVE0156I External URL has been edited.

EYUVE0157E No external URL specified. Pleaseenter an external URL.

EYUVE0162I Menu link components have beenedited.

EYUVE0201E Menu name contains invalidcharacters. Please enter a valid Menuname.

EYUVE0202I Menu link target edited.

EYUVE0203E No Menu selected. Please select aMenu.

EYUVE0204E No Menu name entered. Please enter aMenu name.

EYUVE0205E No Menu selection method indicated.Please indicate method of Menuselection.

EYUVE0211I Context and Scope settings have beenedited.

EYUVE0212E No Context option specified. Pleaseselect a Context option.

EYUVE0213E No Scope option specified. Pleaseselect a Scope option.

EYUVE0214E No CMAS context option specified.Please select a CMAS context option.

EYUVE0215E No fixed Context specified. Pleaseenter a fixed Context name.

EYUVE0060E • EYUVE0215E


EYUVE0216E No fixed Scope specified. Please entera fixed Scope name.

EYUVE0217E No fixed CMAS context specified.Please enter a fixed CMAS contextname.

EYUVE0223E View set name contains invalidcharacters. Please enter a new View setname.

EYUVE0224E No View set named. Please indicatemethod of View set selection and selector enter a View set name.

EYUVE0225I View link target edited.

EYUVE0231E No Object selected. Please select anObject.

EYUVE0232I Object for View selected.

EYUVE0238I View link components edited.

EYUVE0239E View link cannot be edited. TargetView set represents an Object that is notavailable in this release of CICSPlexSM.

EYUVE0244E CMAS context specificationincomplete. Please complete thespecification.

EYUVE0245E Context specification incomplete.Please complete the specification.

EYUVE0246E Invalid fixed value entered. Pleaseenter a valid fixed value.

EYUVE0247E Scope specification incomplete. Pleasecomplete the specification.

EYUVE0248I View link Context and Scope settingshave been set.

EYUVE0254E No filter selected. Please select a Viewlink filter.

EYUVE0255I View link filters have been edited

EYUVE0262I View link filter, 'filtername', deleted.

EYUVE0268E No filter attribute selected. Pleaseselect a filter attribute.

EYUVE0269E No filter parameter selected. Pleaseselect a filter parameter.

EYUVE0270I View link filter attribute selected.

EYUVE0271I View link filter parameter selected.

EYUVE0277I View link filter settings edited.

EYUVE0278E Incomplete filter value specification.Please select a filter value from the list.

EYUVE0280E No attribute filter operator specified.Please select an attribute filter operator.

EYUVE0281E Incomplete filter value specification.Please indicate whether the filter valueis fixed or variable.

EYUVE0282E Please select a variable filter sourceattribute

EYUVE0283E Incomplete filter value specification.Please enter a filter value.

EYUVE0284E Invalid filter value specified. Pleaseenter a valid value for filter type,'filtertypedescription'.

EYUVE0285E Filter value too long. Please enter avalid value for filter type,'filtertypedescription'.

EYUVE0301E View name contains invalidcharacters. Please enter a View name.

EYUVE0302E No View named. Please indicatemethod of View selection and select orenter a View name, if applicable.




EYUVE0309E No filter type specified. Please select afilter type.

EYUVE0310I View link filter type selected.

EYUVE0316E Incomplete link condition attributespecification. Please select an attributefrom the list.

EYUVE0317E No link condition selected. Pleaseselect a link condition.

EYUVE0318I View link condition type selected.

EYUVE0329E New View set name contains invalidcharacters. Please enter a new View setname.

EYUVE0330E View set (viewsetname) already exists.Please enter a new View set name.

EYUVE0332I The View set (viewsetname) has beencreated.

EYUVE0333E No Object specified. Please select anObject.

EYUVE0334E No View set name specified. Pleaseenter a new View set name.

EYUVE0335E View set names starting with 'EYU' arereserved and cannot be created.

EYUVE0336E You are not authorized to create aview set with this name (viewsetname).

EYUVE0340E New View set name contains invalidcharacters. Please enter a new View setname.

EYUVE0341E View set (viewsetname) already exists.Please enter a new View set name.

EYUVE0343E Source View set (sourceviewsetname) notfound. Please select a source View setname.

EYUVE0344I View set (sourceviewsetname) has beencopied as new View set(targetviewsetname).

EYUVE0345E No source View set selected. Pleaseselect a source View set name.

EYUVE0346E No View set name specified. Pleaseenter a new View set name.

EYUVE0347E View set names starting with 'EYU' arereserved and cannot be created.

EYUVE0348E You are not authorized to create aview set with this name (viewsetname).

EYUVE0352E No View set selected. Please select aView set name.

EYUVE0353E View set may not be deleted as iteither starts with EYU or is locked.

EYUVE0359E View set (viewsetnamed) not found.Please select a View set name fordeletion.

EYUVE0360I View set (viewsetname) has been deleted.

EYUVE0361E Unable to delete View set(viewsetname) as it is being updated.Please select a View set name fordeletion.

EYUVE0362E You are not authorized to delete aview set with this name (viewsetname)

EYUVE0367E No View set selected. Please select aView set name.

EYUVE0369I View set (viewsetname) has been openedfor edit.

EYUVE0370E Unable to edit View set (viewsetname)as it is already being updated byanother user (userid). Please select aView set name for edit.

EYUVE0371E View set (viewsetname) cannot beedited because it represents an Objectthat is not available in this release ofCICSPlex SM.

EYUVE0303I • EYUVE0371E


EYUVE0372W View set may not be altered as iteither starts with EYU or is locked. Youwill not be able to save any changes.

EYUVE0373E Unable to edit View set (viewsetname)as the repository record contains aninvalid version identifier. Please select aView set name for edit

EYUVE0374E You are not authorized to update aview set with this name (viewsetname)

EYUVE0377E No View selected. Please select a Viewfor this operation.

EYUVE0378E Save of View set (viewsetname) failed.Updates have been lost.

EYUVE0379I View set (viewsetname) updates savedsuccessfully.

EYUVE0401E New View name contains invalidcharacters. Please enter a new Viewname.

EYUVE0403I View (sourceviewname) has been copiedas new View (targetviewname).

EYUVE0404E No View name specified. Please entera new View name.

EYUVE0405E View name already exists in View set.Please enter an new View name.

EYUVE0411I View (viewname) has been deleted.

EYUVE0417E No pre-fill option specified. Pleaseselect a pre-fill option.

EYUVE0418E View name already exists in View set.Please enter an new View name.

EYUVE0419E No View name specified. Please entera View name.

EYUVE0420E No View type specified. Please selecta View type.

EYUVE0421I View (viewname) has been added to theView set.

EYUVE0422E New View contains invalid characters.Please enter a new View name.

EYUVE0428I View (viewname) edited and will besaved when the View set is saved.

EYUVE0434E Invalid automatic refresh time. Pleaseenter a new automatic refresh time.

EYUVE0435E Invalid maximum number of rows.Please enter a new maximum number ofrows.

EYUVE0436E No automatic refresh option selected.Please select an automatic refreshoption.

EYUVE0437E No automatic refresh time entered.Please enter an automatic refresh time.

EYUVE0438E No maximum number of rowsentered. Please enter a maximumnumber of rows.

EYUVE0439I View display options edited.

EYUVE0449I View title and annotation edited.

EYUVE0455E No button selected. Please select abutton for this operation.

EYUVE0456I View buttons have been edited.

EYUVE0463I View button, 'buttonname', deleted.

EYUVE0469E No button action specified. Pleaseselect a button action.

EYUVE0475E No action specified. Please select anaction for this View button.

EYUVE0501E No confirmation panel selected. Pleaseindicate method of confirmation panelselection and select or enter aconfirmation panel name.

EYUVE0372W • EYUVE0501E


EYUVE0502E No confirmation panel named. Pleaseindicate method of confirmation panelselection and select or enter aconfirmation panel name.

EYUVE0503E Incomplete confirmation panelspecification. Please indicate method ofconfirmation panel selection and selector enter a confirmation panel name.

EYUVE0504E Confirmation panel name containsinvalid characters. Please enter a newconfirmation panel name.

EYUVE0509E Table column not specified. Pleaseselect a table column.

EYUVE0510I Table contents have been edited.

EYUVE0517I Table column, 'tablecolumnname', hasbeen deleted.

EYUVE0523E Attribute not selected. Please select anattribute from the list.

EYUVE0524I Attribute for table column selected.

EYUVE0530I Table column has been edited.

EYUVE0531E Table column cannot be edited. Thecolumn represents an Attribute that isnot available in this release of CICSPlexSM.

EYUVE0536I Table column title and options havebeen edited.

EYUVE0542E No View link specified. Please select aView link.

EYUVE0543I View links have been edited.

EYUVE0550I View link, 'viewlinkname', has beendeleted.

EYUVE0556I Local view link selected.

EYUVE0557I View set link selected.

EYUVE0558E No link type specified. Please select alink type

EYUVE0564I View link components edited.

EYUVE0565E View link cannot be edited. The linkrepresents an Object that is notavailable in this release of CICSPlexSM.

EYUVE0601E Incomplete condition testspecification. Please select conditiontest.

EYUVE0602E Invalid condition value specified.Please enter a valid value for Attributetype, 'attributetypedescription'.

EYUVE0603E Condition value too long. Please entera valid value for Attribute type,'attributetypedescription'.

EYUVE0604I View link condition test edited.

EYUVE0608E View name contains invalidcharacters. Please enter a View name.

EYUVE0609E No View named. Please indicatemethod of View selection and select orenter a View name, if applicable.


EYUVE0616E No filter specified. Please select afilter.

EYUVE0617I Available filters have been edited.

EYUVE0624I View filter, 'filtername', deleted.

EYUVE0630E No filter type specified. Please select afilter type.

EYUVE0631I Attribute filter specified.

EYUVE0632I Parameter filter specified.

EYUVE0502E • EYUVE0632I


EYUVE0638E No Attribute specified. Please selectan Attribute.

EYUVE0639E No entry mechanism specified. Pleaseselect an entry mechanism for the filter.

EYUVE0640I Attribute filter has been edited.

EYUVE0641I Automatic generation of selection listnot possible as selected attribute typedoes not have defined values. Pleaseedit selection list values manually.

EYUVE0646E No Parameter specified. Please select aParameter.

EYUVE0647E No entry mechanism specified. Pleaseselect an entry mechanism for the filter.

EYUVE0648I Parameter filter has been edited.

EYUVE0649I Selection list values invalidated andhave been discarded.

EYUVE0654E No value specified. Please select avalue.

EYUVE0655I Selection list values have been edited.

EYUVE0661I Selection list value, 'selectionlistvalue',added.

EYUVE0662I Selection list value, 'selectionlistvalue',edited.

EYUVE0663E No value specified. Please enter avalue.

EYUVE0664E Value specified is invalid for CVDAtypes. Please enter a new value.

EYUVE0669I Selection list value, 'selectionlistvalue', hasbeen deleted.

EYUVE0701E No presentation type selected. Pleaseselect a presentation type.

EYUVE0702I Presentation type selected.

EYUVE0708E No threshold selected. Please select athreshold.

EYUVE0709I Presentation thresholds edited.

EYUVE0715E Threshold value invalid. Please entera new threshold value.

EYUVE0716E No threshold range specified. Pleaseselect the type and enter the value forthe threshold range.

EYUVE0717I Presentation threshold range edited.

EYUVE0718E Invalid percentage value specified.Please enter a number between 0 and100.

EYUVE0719E Invalid range specified. Please enter anew threshold range.

EYUVE0725I Presentation threshold,'presentationthresholdvalue', deleted.

EYUVE0731E Invalid number specified. Please entera valid numerical value.

EYUVE0732E Upper limit not specified. Pleaseselect a type and value for the upperlimit of the bar gauge.

EYUVE0733E Lower limit not specified. Pleaseselect a type and value for the lowerlimit of the bar gauge.

EYUVE0734I Presentation options edited.



EYUVE0747E View (viewname) cannot be editedbecause it represents an Action that isnot available in this release of CICSPlexSM.



EYUVE0752E No Action specified. Please select anAction for the confirmation panel.

EYUVE0754I Confirmation panel Action selected.

EYUVE0758E No item selected. Please select a formitem for this operation.

EYUVE0759I Form contents edited.

EYUVE0760I Edit operation ignored. White spaceitems have no editable options.

EYUVE0765E No form item type specified. Pleaseselect a form item type.

EYUVE0766I Form item type selected.

EYUVE0801I Form item has been edited.

EYUVE0802E Form item, 'formitemname', cannot beedited as it references an Attribute thatis not available in this release ofCICSPlex SM.

EYUVE0803E Form item, 'formitemname', cannot beedited as it references a Parameter thatis not available in this release ofCICSPlex SM.

EYUVE0807I Form item title and annotation havebeen edited.

EYUVE0812I Form item display options have beenedited.

EYUVE0813E No display option specified. Pleaseselect a display option.

EYUVE0814I Automatic generation of selection listnot possible as selected attribute typedoes not have defined values. Pleaseedit selection list values manually.

EYUVE0820I Form item, 'formitemname', deleted.

EYUVE0821I Form items, 'formitemname1' andformitemname2, deleted.

EYUVE0825I Attribute for form item specified.

EYUVE0826I Parameter for form item specified.

EYUVE0827E No Attribute specified. Please selectan Attribute to be represented by thisform item.

EYUVE0828E No Parameter specified. Please select aParameter to be represented by thisform item.

EYUVE0833I Form item default Parameter value hasbeen edited.

EYUVE0838I Presentation threshold components havebeen edited.

EYUVE0843E No color selected. Please select a colorfor the presentation threshold.

EYUVE0844I Presentation threshold color specified.

EYUVE0949I User group (usergroup) has been created.

EYUVE0950E New user group contains invalidcharacters. Enter a valid user groupname.



EYUVE0952E User group (usergroupname) alreadyexists. Enter a new user group name.

EYUVE0953E You are not authorized to create usergroups.

EYUVE0954E User group attribute, attributename,contains an invalid value. Enter a validvalue for attributename.

EYUVE0956I User group (usergroupname) updatessaved successfully.

EYUVE0752E • EYUVE0956I


EYUVE0957E No user group selected. Select a usergroup name.

EYUVE0958E Unable to edit user group(usergroupname) because it is alreadybeing updated by another user (userid).Select another user group name for edit.

EYUVE0959E Unable to edit user group(usergroupname) as the repository recordcontains an invalid version. Select auser group name for edit.

EYUVE0960E You are not authorized to update usergroups.

EYUVE0961I User group (usergroupname) has beenopened for edit.

EYUVE0962I User group (usergroupname) has beendeleted.

EYUVE0963E User group (usergroupname) not found.Select another user group name fordeletion.

EYUVE0964E Unable to delete user group(usergroupname) because it is beingupdated by another user (userid). Selecta user group name to delete.

EYUVE0965E You are not authorized to delete usergroups.

EYUVE0969I User group (usergroupname) has beencreated.

EYUVE0970E No user name specified. Enter a newuser name.

EYUVE0971E New user contains invalid characters.Enter a valid user name.

EYUVE0972E User (username) already exists. Enter anew user name.

EYUVE0973E You are not authorized to create users.

EYUVE0974E No user selected. Select a user name.

EYUVE0975E Unable to edit user (username) becauseit is being updated by another user(userid). Select another user name foredit.

EYUVE0976E Unable to edit user (username) becausethe repository record contains an invalidversion. Select a user name for edit.

EYUVE0977E You are not authorized to updateusers.

EYUVE0978I User (username) has been opened foredit.

EYUVE0979I User (username) has been deleted.

EYUVE0980E User (username) not found. Select auser name for deletion.

EYUVE0981E Unable to delete user (username)because it is being updated by anotheruser (userid). Select a user name todelete.

EYUVE0982E You are not authorized to delete users.

EYUVE0983I User (username) updates savedsuccessfully.

EYUVE0984E User (userid) is being updated byanother user. You may not alter yourfavorites.

EYUVE0985E Unable to edit user (userid) becausethe repository contains an invalidversion number.

EYUVE1003E Repository not available or notauthorized for User.

EYUVE1010I The map (mapname) has been created.

EYUVE1011E No map name specified. Enter a newmap name.

EYUVE1012E New map contains invalid characters.Enter a new map name.



EYUVE1013E Map (mapname) already exists. Enter anew map name.

EYUVE1014E Map names starting with EYU arereserved and cannot be created.

EYUVE1015E You are not authorized to create a mapwith this name (mapname).

EYUVE1016E No Map selected. Select a Map name.

EYUVE1017E Unable to edit Map (mapname) becauseit is already being updated by anotheruser (userid). Select another Map namefor edit.

EYUVE1018W Map may not be altered as it eitherstarts with EYU or is locked. You willnot be able to save any changes.

EYUVE1019E Unable to edit Map (mapname) becausethe repository record contains an invalidversion. Select another Map name foredit.

EYUVE1020E You are not authorized to update aMap with this name (mapname).

EYUVE1021E Map (mapname) has been opened foredit.

EYUVE1022I Map (sourcemapname) has been copied asnew Map (newmapname).

EYUVE1023E No source Map selected. Select asource map name.

EYUVE1024E Source Map (mapname) not found.Select a source Map name.

EYUVE1025E Map cannot be deleted as it eitherstarts with æEYUÆ or is locked.

EYUVE1026I Map (mapname) has been deleted.

EYUVE1027E Unable to delete Map (mapname). It isbeing updated by another user (userid).Select a map name for deletion.

EYUVE1028E Map (mapname) not found. Select aMap name for deletion.

EYUVE1029E You are not authorized to delete a mapwith this name (mapname).

EYUVE1030I Map (mapname) updates savedsuccessfully.

EYUVE1031E Map item not specified. Select a mapitem.



Chapter 32. EYUVHnnnn messages

EYUVHnnnn messages are issued by the Web User Interface in response to HTTPresponse codes.

EYUVH0400E Bad HTTP request.

Explanation: The request was incorrectly formatted bythe web browser.

System action: The request is ignored.

System action: Check the service levels of the CICSWeb Interface and the CICSPlex SM Web User Interfacefeatures. Collect the AUXTRACE and contact IBM if theproblem is not resolved.

User response: If you are using a different webbrowser from the one normally used to access theserver, try the usual one. Contact your systemadministrator if problem is not resolved.


EYUVH0403E Request forbidden.

Explanation: The user must be signed on andauthorized to access this resource.


System action: Check the EYULOG for securityexceptions and review the user's authorizations. Collectthe AUXTRACE and contact IBM if you cannot resolvethe problem.

User response: Sign on to the Web User Interfaceserver and try again. Contact your systemadministrator if the problem is not resolved.


EYUVH0404E Request not found.

Explanation: The requested resource was notrecognized by the server.


System action: Check that the URL entered by theuser is valid. If the request is for a customized helppage then use the View Editor to ensure that theassociated view or menu definition specifies the correctmember name, and that the member is contained in theDFHHTML data set. Collect the AUXTRACE andcontact IBM if you cannot resolve the problem.

User response: If you entered the address manually,ensure that the address was entered correctly. Contactyour system administrator if the problem is notresolved.


EYUVH0500E Internal server error.

Explanation: The server experienced an unexpectedinternal error.

System action: The response is cancelled but theaction requested may have completed.

System action: Collect the AUXTRACE and anydumps and contact IBM.



EYUVH0501E HTTP request method not supported.

Explanation: The web browser sent a request using aninvalid or unsupported HTTP request method.


System action: Collect the AUXTRACE and anydumps and contact IBM.

User response: If you are using a different webbrowser from the one normally used to access theserver, try the usual one. Contact your systemadministrator if the problem is not resolved.


EYUVH0503E Service temporarily unavailable.

Explanation: The server is not currently available forconnections.


System action: Review the status of the CICSPlex SMWeb User Interface server and restart if necessary.

User response: Try again later. Contact your systemadministrator if the problem is not resolved.



Chapter 33. EYUVSnnnn messages

EYUVSnnnn messages are issued by the Web User Interface server to reflect thestatus of the interface server, written to the EYULOG, administrator terminal andconsole.

EYUVS0001I CICSPlex SM Web User Interfaceinitialization started.

Explanation: The Web User Interface serverinitialization sequence has begun.

System action: Initialization sequence continues.


Destination: EYULOG, Console.

EYUVS0002I CICSPlex SM Web User Interfaceinitialization complete.

Explanation: The Web User Interface serverinitialization sequence has completed successfully.

System action: Ready for web browser requests.



EYUVS0003I CICSPlex SM Web User Interfacetermination started.

Explanation: The Web User Interface servertermination sequence has begun.

System action: Termination sequence continues.Further web browser requests will be rejected.



EYUVS0004I CICSPlex SM Web User Interfacetermination complete.

Explanation: The Web User Interface servertermination sequence has completed successfully.

System action: The server terminates.



EYUVS0005S CICSPlex SM Web User Interfaceinitialization failed. (reasontext).

Explanation: The currently executing Web UserInterface server initialization sequence has failed.Diagnostic messages may have been written to theEYULOG.

System action: The currently executing serverinitialization program terminates.

System action: Review EYULOG for server addressspace. If reasontext is "Web User Interface alreadystarted", check the system initialization parameters forboth CPSMCONN and PLTPI.


EYUVS0006E CICS shutdown request failed.RESP(resp) RESP2(resp2)

Explanation: The request to shut down the Web UserInterface CICS region, as part of the Web User Interfaceserver termination sequence, has failed.

The message contains the RESP and RESP2 valuesreturned by the EXEC CICS PERFORM SHUTDOWNcommand.

System action: The Web User Interface terminates butthe CICS region remains active.

System action: Review the RESP and RESP2 valuessupplied in the message to determine the cause of theproblem. Shut down the CICS region manually.


EYUVS0007E The server repository version version isnot correct.

Explanation: The WUI server repository wasinitialized by a WUI server running a version ofCICSPlex SM other than the current release.

System action: The currently running serverinitialization program terminates.

User response: Restart the server address space with anew WUI server repository data set, or an existingrepository which has been initialized by a serverrunning the current CICSPlex SM release.

Destination: EYULOG, Console

EYUVS0008I The server repository version version isnot correct.

Explanation: The server repository has been initializedfor shared access.

System action: Server processing continues.



##

###

##

####

#

###

##

#

#

Destination: EYULOG, Console

EYUVS0010I Server connected to CMAS,SYSID(sysid).

Explanation: The connection to the CMAS is available.Users may now sign on to the Web User Interfaceserver.



Destination: EYULOG.

EYUVS0011W Server connection to CMASunavailable.

Explanation: The connection to the CMAS isunavailable. User sessions will be signed off and WebUser Interface server will remain unavailable untilCMAS connection is established.

System action: User sessions are be terminated andprocessing continues.

System action: Re-establish CMAS connectivity, ifappropriate.


EYUVS0020I Task initialization complete for User(username).

Explanation: A User task has been successfully createdfor the named user as a result of a signon request.




EYUVS0021I Task termination complete for User(username). reasontext.

Explanation: A User task has terminated and theassociated session was closed.




EYUVS0022E Task for User (username) failed.

Explanation: An internal error was encountered whenattempting to create a User session.

System action: User signon is cancelled.

System action: Review any preceeding messagesassociated with the problem. If there are no associatedmessages, collect AUXTRACE, console log, and dumpinformation, and contact IBM service.


EYUVS0023E Task failed to connect to CICSPlex SMfor User (username). (conncode,connreason)

Explanation: A new user session failed to connect toCICSPlex SM for the named user.


System action: Review the CMAS status and accessauthorities for the user ID. Note that the messageincludes the Response and Reason values from theEXEC CPSM CONNECT command.


EYUVS0024W User user is not connected torequested group group1. Default groupgroup2 used.

Explanation: During sign on, the Web User Interfaceuser user specified group group1 on the sign on screen.The specified group group1 is not used because the userID is not connected to group1

System action: The sign on continues, but the WebUser Interface will attempt to use the user's defaultgroup group2 as the name of the Web User Interfaceuser group profile.

Programmer response: Administrator Action

Contact the security administrator to check that thegroup1 group specified is appropriate and that the userID is connected to that group.

The sign on group option is available to Web UserInterface users only if the Web User Interface systemparameter SIGNONPANEL is set to ENHANCED. Ifthe group option is not required, set SIGNONPANEL toBASIC.

Destination: EYULOG

EYUVS0025E Creation of user (userid) failed. Usersignon aborted.

Explanation: An attempt, during signon, to create auser object to store the favorites of user userid hasfailed.

System action: The signon process terminates.

System action: Check the message user log formessages reporting the exception.

Destination: EYULOG

EYUVS0030E Signon rejected. Maximum user limit(maxusers) reached.

Explanation: A user attempted to sign on to the WebUser Interface server but the maximum number ofconcurrent sessions, as defined by the MAXUSERS

EYUVS0010I • EYUVS0030E


#

###

####

####

#

###

#####

#

parameter, had already been reached.


System action: If this message occurs frequently,consider increasing the MAXUSERS parameter,reducing the INACTIVETIMEOUT parameter, orintroducing additional Web User Interface servers. Ifthe problem must be resolved immediately, use theadministration transaction (COVC) to purge aredundant user session.


EYUVS0031E Signon failed. Unable to start task forUser (username). (CICS information:RESP(response1) RESP2(response2))

Explanation: A new user session failed to start for thenamed user, because the user task transaction (COVA)could not be started.


System action: Review the health of your WUI serverand access authorities for the named user ID, and theuser ID associated with the COVG transaction. Notethat the message includes the RESP and RESP2 valuesfrom the EXEC CICS START command.


EYUVS0101I Parameter service initializationcomplete.

Explanation: Server parameters were read successfullyduring the initialization sequence and have been madeavailable to other server components.

System action: Initialization sequence continues.



EYUVS0102I Parameter service terminated.

Explanation: Server parameters have been discardedduring the termination sequence.

System action: Termination sequence continues.



EYUVS0103E Parameter service failed.

Explanation: The server was unable to read serverparameters during the initialization sequence.

System action: The initialization sequence is abended,and the server terminates.

System action: Review previous messages todetermine the cause of failure.


EYUVS0104E Parameter (parmname) invalid.

Explanation: The value supplied for the named serverparameter in the parameter data set was either badlyformatted or out of range.

System action: Initialization fails.

System action: Review the value of the namedparameter before attempting to restart the server.


EYUVS0105E Invalid record in parameter data set.

Explanation: The Web User Interface server found abadly formatted line in the server parameters.


System action: Review the contents of the serverparameter data set before attempting to restart theserver.


EYUVS0106W Over-length record in parameter dataset ignored.

Explanation: A record in the server parameter data setwas too long to process and has been ignored.

System action: Initialization continues.

System action: Review the contents of the serverparameter data set before attempting to restart theserver.


EYUVS0107I Reading startup parameters.

Explanation: The Web User Interface is reading theserver parameters.




EYUVS0108I Startup parameters read.

Explanation: The Web User Interface has read theserver parameters.




EYUVS0109I parmname(parmvalue)

Explanation: The named server parameter has beenread and found to contain the given value.


EYUVS0031E • EYUVS0109I




EYUVS0110E Required parameter (parmname) notspecified.

Explanation: The Web User Interface server has readall the parameters supplied but failed to find a valuefor a required parameter.


System action: Supply the named parameter beforeattempting to restart the server.


EYUVS0111E Trace flag specification invalid.

Explanation: The WUITRACE parameter wasspecified, but was formatted incorrectly.


System action: Review value of WUITRACEparameter before attempting to restart the server.


EYUVS0112E Unable to open parameter TDQ(TDQname).

Explanation: The Web User Interface was unable toopen the data set containing the server parameters.


System action: Check the status of the data set namedin the EYUWUI DD card of the server JCL, and ensureit is of the correct record format and is readable.


EYUVS0113E No AUTOIMPORTMEM specified.EYUx* is assumed.

Explanation: You have specified a data set name forthe AUTOIMPORTDSN WUI server initializationparameter but you have not specified a data setmember name for the AUTOIMPORTMEM parameter.The data set member name defaults to EYUx*, where xidentifies the language in which the definitions arewritten and the asterisk is a wildcard character. Thismeans that all of the definitions in the specifiedlanguage starting with the characters EYU areimported.

System action: Auto-import continues with the defaultdata set member name.

System action: Ensure that the correct data setmembers have been imported.


EYUVS0114E The AUTOIMPORTDSN parameter ismissing. This is required when youspecify AUTOIMPORTMEM.

Explanation: You have specified a data set membername for the AUTOIMPORTMEM WUI serverinitialization parameter but you have not specified adata set name for the AUTOIMPORTDSN parameter.You must specify a value for AUTOIMPORTDSN whenyou specify AUTOIMPORTMEM.

System action: WUI server initialization continueswithout auto-import being performed.

System action: You can either shut down the WUIserver restart initialization with the correct auto-importparameters, or use the COVC transaction to importdata repository definitions for the existing WUI server.


EYUVS0120E Unable to load resource table(restable).

Explanation: The server was unable to load thenamed module from the SEYULOAD data set.


System action: Contact IBM.


EYUVS0121W National language specificationinvalid. Using "ENU".

Explanation: The EYU9VKEC INITPARM was eithermissing or did not contain a valid national languagespecification. This message is issued each time theserver attempts to use the INITPARM value.

System action: 'ENU' is used as the default nationallanguage and processing continues.

System action: Review the language specificationsupplied as EYU9VKEC INITPARM.

Destination: Console.

EYUVS0122W Default codepage specificationinvalid. Using "ENU1".

Explanation: The EYU9VWAN INITPARM was eithermissing or did not contain a valid codepagespecification. This message is issued each time theserver attempts to use the INITPARM value, that is,each time a web browser request is received with aninvalid or missing codepage specification.

System action: 'ENU1' is used as the default codepagespecification and processing continues.

System action: Review the language specificationsupplied as EYU9VWAN INITPARM.


EYUVS0110E • EYUVS0122W


EYUVS0123W The thousand separator and decimalseparator are the same.

Explanation: Either by default or by design the WebUser Interface startup parametersDECIMALSEPARATOR and THOUSANDSEPARATORhave been set equal. This could cause ambiguity whenviewing a numeric in the thousands that also containsdecimal places.


System action: Consider changing these parametersettings.


EYUVS0150E Message messageNum could not bewritten to EYULOG.

Explanation: The specified message could not bewritten to the EYULOG.


System action: Review the status of the EYULOGdestination. Collect AUXTRACE and contact IBM if theproblem cannot be resolved.


EYUVS0200I Starting CICS Web Interface.

Explanation: The Web User Interface server isattempting to open the CICS Web Interface forincoming requests from the web browser.




EYUVS0201I Start of CICS Web Interface transaction(transname) successful.

Explanation: When running on systems prior to CICSTransaction Server V1.3, the server requested theinitialization of the CICS Web Interface.




EYUVS0202E Start of CICS Web Interfacetransaction (transname) failed.

Explanation: When running on systems prior to CICSTransaction Server V1.3, an attempt to start the CICSWeb Interface failed.


System action: Ensure the CICS Web Interface hasbeen configured correctly.


EYUVS0203I Discarding previously installed TCP/IPservice (tcpipname).

Explanation: When running on CICS TransactionServer V1.3 or later, the named TCP/IP service wasalready present and is being discarded.




EYUVS0204I TCP/IP service (tcpipname) installedsuccessfully.

Explanation: When running on CICS TransactionServer V1.3 or later, the named TCP/IP service hasbeen installed for CICS Web Interface requests.




EYUVS0205E Failed to install TCP/IP service(tcpipname).

Explanation: When running on CICS TransactionServer V1.3 or later, an attempt to create the namedTCP/IP service failed.


System action: Ensure that the CICS Web Interface hasbeen configured correctly, that the port numberspecified by the TCPIPPORT server parameter is notalready in use, and that the related TCP/IP serverparameters have valid values.


EYUVS0206I CICS Web Interface enabled on portnumber portnum.

Explanation: When running on CICS TransactionServer V1.3 or later, a TCP/IP service has beensuccessfully opened on the given port number.




EYUVS0207E Failed to enable CICS Web Interfaceon port number portnum.

Explanation: When running on CICS TransactionServer V1.3 or later, a TCP/IP service has not beensuccessfully opened for the given port number.


EYUVS0123W • EYUVS0207E


System action: Ensure that the CICS Web Interface hasbeen configured correctly, that the port numberspecified by the TCPIPPORT server parameter is notalready in use, and that the related TCP/IP serverparameters have valid values.


EYUVS0208E SSL support not available in thisrelease of CICS.

Explanation: The TCPIPSSL server parameterrequested secure socket layer support on a release ofCICS on which it is not supported.


System action: Use unsecure sockets (by removing theTCPIPSSL server parameter) or upgrade the serverCICS to an appropriate release.


EYUVS0209I URI map (urimapname) installedsuccessfully.

Explanation: The named URI map has been installedfor CICS Management Client Interface requests.


User response: None

Destination: EYULOG

EYUVS0210E Failed to install URI map (urimapname).

Explanation: An attempt to create the named URImap failed.


User response: Ensure that the CICS ManagementClient Interface has been configured correctly and thatthe PATH specified by the CICS Management ClientInterface is not already in use.

Destination: EYULOG

EYUVS0211I CICS Management Client Interfaceenabled on TCP/IP port numberportnum.

Explanation: A TCP/IP service has been successfullyopened on the given port number for the CICSManagement Client Interface.



Destination: EYULOG

EYUVS0212E Failed to enable CICS ManagementClient Interface on TCP/IP port numberportnum.

Explanation: A TCP/IP service has not beensuccessfully opened for the given port number for theCICS Management Client Interface.


User response: Ensure that the CICS ManagementClient Interface has been configured correctly, that theport number specified by the CMCIPORT serverparameter is not already in use, and that the relatedTCP/IP server parameters have valid values.

Destination: EYULOG

EYUVS0213I Discarding previously installed URImap (urimapname).

Explanation: The name URI map was already presentand is being discarded.



Destination: EYULOG

EYUVS0900I SSL support not available in this releaseof CICS.

Explanation: Web User Interface server initializationhas been requested using the COVC transaction.

System action: Initialization sequence is started.


Destination: Console, Terminal, EYULOG.

EYUVS0901I Web User Interface server stoprequested from terminal.

Explanation: Web User Interface server terminationhas been requested using the COVC transaction.

System action: Termination sequence is started.


Destination: Console, Terminal, EYULOG.

EYUVS0902W Web User Interface server is currentlyactive.

Explanation: Web User Interface server initializationhas been requested using the COVC transaction but theserver is already active.



Destination: Terminal.



EYUVS0903W Web User Interface server is currentlyinactive.

Explanation: Web User Interface server terminationhas been requested using the COVC transaction but theserver is already inactive.



Destination: Console, Terminal.

EYUVS0904E Web User Interface control transactioncommand invalid.

Explanation: The specified operation was notunderstood by the Web User Interface controltransaction (COVC).


System action: Retry the operation ensuring that thespecification is correct.


EYUVS0905E Web User Interface control transactionfailed.

Explanation: The Web User Interface controltransaction suffered an internal error.


System action: Collect any abend information,AUXTRACE and dumps, and contact IBM service.


EYUVS0906I Web User Interface control transactionoperation complete.

Explanation: The specified operation was carried outsuccessfully.




EYUVS0907E Invalid entry. Enter Y or N.

Explanation: An invalid character has been entered asa flag on the Web User Interface control transactiontrace settings panel.


System action: Correct the field that is in error.


EYUVS0908E Web User Interface control transactionrequires 3270 terminal for specifieddisplay.

Explanation: The requested operation requires a fullscreen map which is not supported by the currentdevice.


System action: Retry the operation from a suitableterminal.


EYUVS0909I Purge of User (username1) requested byUser (username2).

Explanation: The named user has purged the WebUser Interface session for the named user.

System action: The purged user session will beterminated as soon as possible.



EYUVS0910E Purge request failed. User (username)not found.

Explanation: An attempt to terminate the active WebUser Interface session for the named user failed as theuser was not signed on.




EYUVS0911E Purge request of user (username)failed.

Explanation: An attempt to terminate the active WebUser Interface session for the named user failed due toan internal error.

System action: The request is abended.

System action: Collect any abend information,AUXTRACE and dumps, and contact IBM service.


EYUVS0912I Purge request successful.

Explanation: The request to terminate active Web UserInterface sessions has been accepted.

System action: The purged user sessions will beterminated as soon as possible.



EYUVS0903W • EYUVS0912I


EYUVS0913E Purge request failed.

Explanation: The request to terminate an active WebUser Interface session failed.

System action: The request may not have beencompleted.

System action: See associated messages in EYULOG.


EYUVS0914E Purge already requested.

Explanation: A request to terminate an active usersession has been ignored as the session is alreadyterminating.




EYUVS0915E Purge already requested for user(username).

Explanation: A request to terminate an active usersession has been ignored as the session is alreadyterminating.




EYUVS0916E Import operation completedsuccessfully. count objects processed.

Explanation: The request to import menu or view setdefinitions has been successful.




EYUVS0917E Import operation failed.

Explanation: The request to import menu or view setdefinitions has failed.

System action: Menu or view set definitions that weresuccessfully completed before the definition in error areretained. The menu or view set definition thatcontained the error is not imported. Further menu orview set definitions in the data set are ignored.



EYUVS0918E Invalid TDQ name.

Explanation: The request to import or export menu orview set definitions specified an invalid TDQ name.

System action: The request is not performed.

System action: Review status of TDQ and correct asnecessary.


EYUVS0919I Export completed successfully. nnobjects written.

Explanation: The request to export menu or view setdefinitions has been successful.




EYUVS0920E Export failed.

Explanation: The request to export menu or view setdefinitions has failed.

System action: The output in the export data set istruncated at the point where the error is encountered.



EYUVS0921E Invalid name pattern.

Explanation: The menu or view set name patternspecified for export was invalid.


System action: Correct the pattern name beforeretrying the operation.


EYUVS0922E Invalid Object type.

Explanation: The object type specified for export wasinvalid.


System action: Correct input before retrying theoperation.


EYUVS0923W Invalid Object type. "objectname" isassumed.

Explanation: An invalid object type was specified onthe import or export panel.

System action: The field is set as indicated.





EYUVS0924W Invalid duplicate names field. "action"is assumed.

Explanation: An invalid duplicate names action wasspecified on the import panel.

System action: The field is set as indicated.



EYUVS0925W Invalid lock option. option is assumed.

Explanation: An invalid lock value is specified in thelock field of the export panel.

System action: The field is set as indicated in themessage text.



EYUVS0926I Import operation partially complete.count objects processed.

Explanation: Some resources could not be importedsuccessfully by the request to import menu or view setdefinitions.


System action: See the associated messages inEYULOG.


EYUVS0929E It is invalid to specify both a TDQname and a data set name. Use one orthe other.

Explanation: You have specified both a TDQ nameand a data set name on the COVC import panel. This isan invalid combination. You cannot import datarepository definitions to both a data set and a TDQ inone operation using the COVC transaction.

System action: The COVC Import panel is redisplayedwith the values you have specified.

System action: Specify either a data set name or aTDQ name but not both.

Destination: Terminal

EYUVS0930W No data set member name has beenspecified. EYUx* is assumed.

Explanation: You have specified a data set name butnot a data set member name. The data set membername field has defaulted to the value EYUx*, where xidentifies the WUI server language and the asterisk is a

wildcard character. This would have the effect ofimporting all definitions in the specified languagestarting with the letters EYU.

System action: The COVC Import panel is redisplayedwith the default data set member name.

System action: Ensure that the data set member namevalue is correct before proceeding with the COVCimport operation.


EYUVS0931E The data set name is missing. This isrequired when you specify a data setmember name.

Explanation: You have specified a data set membername but not a data set name. The COVC importoperation cannot proceed without a valid data setname.

System action: The COVC Import panel is redisplayedwith the values you have specified.

System action: Specify a valid data set name beforeproceeding with the COVC import operation.


EYUVS0950I Web User Interface server PLT start.

Explanation: The Web User Interface PLT start processhas been triggered.

System action: Web User Interface initialization isstarted.



EYUVS0951I Web User Interface server PLTshutdown.

Explanation: The Web User Interface PLT shutdownprocess has been triggered.

System action: Web User Interface termination isstarted.



EYUVS0952I Web User Interface server inactive atPLT shutdown.

Explanation: The Web User Interface PLT shutdownprocess was triggered but the server was not running.




EYUVS0924W • EYUVS0952I


EYUVS0953E Web User Interface server PLT startfailed.

Explanation: The Web User Interface PLT start processwas unable to start the COVG transaction.

System action: The Web User Interface is not started.

System action: Verify Web User Interface installation,including the presence of the CSD resource groups inthe group list. Collect AUXTRACE, console log, andany dump information, and contact IBM service if theproblem cannot be resolved.


EYUVS0954E Web User Interface cpsmrel does notmatch CICS release cicsrel

Explanation: The version of the Web User Interfacecpsmrel does not match CICS release cicsrel.

System action: The Web User Interface is not started.

System action: Ensure that the Web User Interfaceversion and the CICS release match before retrying theoperation.


EYUVS0960E {CREATE|OPEN} {FILE|PROGRAM|MAPSET|TRANSACTION|TDQUEUE|ENQMODEL} resourcenamefailed: RESP=respcode, RESP2=resp2code

Explanation: A WUI server initialization programissued an EXEC CICS CREATE or EXEC CICS SETFILE OPEN command for the resource resourcename forCICSPlex SM. The CREATE or SET command returnedan abnormal response, with the values shown inrespcode and resp2code.

System action: WUI initialization continues.

User response: Examine the CICS trace records todetermine what caused the EXEC CICS error. Thenrestart WUI server initialization using the COVCtransaction.

Module: EYU0VKIT, EYU0VKC0


EYUVS0961E {FILE|MAPSET|PROGRAM|TRANSACTION|TDQUEUE} resourcename has invalidvalue: xxxxxxxx for option: yyyyyyyyy

Explanation: The initialization program for a WUIserver detected an invalid definition option for theCICSPlex SM resource resourcename

System action: CICSPlex SM will try to replace thedefinition with the default definition for the resource. Ifthis is successful, it will issue message EYUVS0962W. Ifthe replacement fails it will issue message EYUVS0963E

and will terminate WUI server initialization.

User response: None



EYUVS0962W The definition for {FILE|MAPSET|PROGRAM|TRANSACTION|TDQUEUE} resourcename has beenreplaced.

Explanation: The initialization program for a WUIserver has replaced an invalid definition for theCICSPlex SM resource resourcename. Previous messageEYUVS0961E gives details of the invalid definitionoptions.

System action: WUI server initialization continues.

User response: None



EYUVS0963E The {FILE|MAPSET|PROGRAM|TRANSACTION|TDQUEUE} definition for resourcenameis invalid. Web user interface serverinitialization is terminating.

Explanation: The initialization program for a WUIserver was unable to replace an invalid definition forthe CICSPlex SM resource resourcename. Previousmessage EYUVS0961E gives details of the invaliddefinition options.

System action: WUI server initialization is terminated.CICS initialization continues.

User response: Review the definition within the grouplist you use when starting the WUI server. Change theinvalid options before reinstalling the definition andrestarting the WUI server with the COVC transaction.The default options are shown in the sampleEYUúWDEF.



EYUVS0988I Dump complete.

Explanation: The dump request for the previouslyreported abend has completed.


System action: Collect AUXTRACE, console log, andprevious dump information, and contact IBM service.




####

######

#

####

#

#

||||

|||

||||

|

|

|

|

||||

|||||

|

|

|

|

|||||

|||||

||

||||||

|

|

EYUVS0989I Dump suppressed.

Explanation: The abend appears to be a duplicate of aprevious abend for which a system dump has alreadybeen taken.

System action: A system dump is not taken.

System action: Collect AUXTRACE, console log, andprevious dump information, and contact IBM service.


EYUVS0990I information

Explanation: This message contains auxiliaryinformation.




EYUVS0991S Abend recovery failed.

Explanation: The Web User Interface task was unableto recover from a previous abend.

System action: The Web User Interface taskterminates.

System action: Collect AUXTRACE, console log, anddump information, and contact IBM service.


EYUVS0992S Abend abendCode in modulemoduleName.

Explanation: An abend occurred in the specifiedmodule.

System action: A system dump is taken and theindividual user request is abended.



EYUVS0993S Abend while scanning storage area.Description of probable cause

Explanation: An error was detected when attemptingto collect diagnostic information for a previous abend.

System action: The Web User Interface taskterminates.



EYUVS0994I dumpTitle

Explanation: This message contains the title of asystem dump that is about to be taken.

System action: A system dump is taken.



EYUVS0995E System dump request failed.

Explanation: An attempt to take a system dump torecord a previous abend has failed.

System action: A dump is not taken and abendprocessing continues.



EYUVS0996S Abend abendCode System codesystemAbendCode at OffsetabendOffset.

Explanation: An abend has occurred during Web UserInterface processing.

System action: Further diagnostic information willfollow.



EYUVS0998I abendInformation

Explanation: This message contains diagnosticinformation for a previous abend.

System action: Abend processing continues.



EYUVS0999S WUI failed: failureString

Explanation: An internal error occurred during WebUser Interface processing.

System action: Processing will continue, if possible.



EYUVS0989I • EYUVS0999S


EYUVS1000E Import encountered unexpectedcharacter in record number nn of TDQ(tdqname).

Explanation: The import process encountered a badlyformatted record in the input data set. The exporteddefinitions have probably been corrupted.


System action: Review the import data set to see if ithas been damaged. Use another copy or reexport fromsource, if available. Collect AUXTRACE, EYULOG andinput data set, and contact IBM service.


EYUVS1001E Import string missing from recordnumber nn of TDQ (tdqname).





EYUVS1002E Import unable to obtain versionnumber in record number nn of TDQ(tdqname).





EYUVS1003E Import unable to obtain index numberin record number nn of TDQ (tdqname).





EYUVS1004E Import found invalid data in recordnumber nn of TDQ (tdqname).





EYUVS1005E Import found invalid string in recordnumber nn of TDQ (tdqname).





EYUVS1000E • EYUVS1005E


EYUVS1006E Import detected missing punctuation inrecord number nn of TDQ (tdqname).





EYUVS1007E Import found an unknown object typeat record number nn of TDQ (tdqname).

Explanation: The import process encountered anunknown record identifier in the input data set. Theexported definitions have probably been corrupted.




EYUVS1008E Import failed at record number nn inTDQ (tdqname).

Explanation: The import process has failed due topreviously recorded errors.


System action: Collect AUXTRACE, EYULOG andinput data set, and contact IBM service.


EYUVS1009E Import failed at record number nnwhen the end of TDQ (tdqname) wasunexpectedly encountered.

Explanation: The import process encountered the endof the input data set before the current menu or viewset definition had been completed. The input data sethas probably been truncated.


System action: Review import data set to see if it hasbeen damaged. Use another copy or reexport fromsource, if available. Collect AUXTRACE, EYULOG andinput data set and contact IBM service.


EYUVS1010E Import failed to open TDQ (tdqname).

Explanation: The request to import menu or view setdefinitions specified an invalid TDQ name, or thespecified TDQ could not be opened.


System action: Review the status of the TDQ andcorrect as necessary.


EYUVS1011E Export failed to open TDQ (tdqname).

Explanation: The request to export menu or view setdefinitions specified an invalid TDQ name, or thespecified TDQ could not be opened.


System action: Review the status of the TDQ andcorrect as necessary.


EYUVS1012E Import encountered unknown recordversion in record number of TDQ(tdqname).

Explanation: The import process has encountered arecord in the import data set that has a higher versionnumber than is supported by the server. The importdata was written by a server using a higher version ofthe record.

System action: Menu or view set definitions importedsuccessfully before the definition in error are retained.The menu or view set definition that contains the erroris not imported. Further menu or view set definitionsin the data set are ignored.

System action: Ensure that the release and servicelevel of the server is not lower than the release andservice level of the server from which the import dataset was exported. If the problem cannot be resolved,save the content of the AUXTRACE, EYULOG, and theinput data sets, and contact IBM service.




EYUVS1013E Resource (resourcetype, resourcename) isbeing updated by another user (userid).Import terminated.

Explanation: The import of the menu or view setdefinition, resourcetype, resourcename, has failed becauseit is being updated by user userid.

System action: The import of the named resource failsbut the processing of other resources in the data setcontinues.

System action: Retry the import operation once theuser has finished updating the resource.


EYUVS1014E Import terminated due to a previoussecurity exception.

Explanation: An import has failed because of aprevious security exception. It is likely that the userlacks the necessary authorization to import one or moreof the resources included in the operation.

System action: The import operation terminates.Menu or view set definitions imported successfullybefore the resource in error are retained. The menu orview set definition in error is not imported. Theremaining menu or view set definitions in the data setare ignored.

System action: Check the message user log formessages reporting the security exception.


EYUVS1015W User (userid) not authorized forresource (resourcetype, resourcename).Resource not exported.

Explanation: Web User Interface user userid hasattempted to export the resource resourcetype,resourcename but does not have the required access tothe resource.

System action: The named resource is not exportedbut the rest of the input stream is processed. The useris not informed of the failure.

System action: Review the user's securityauthorizations.


EYUVS1016I Import 'importType' initiated by user(userid) from TDQ (tdqname).

Explanation: Import processing is beginning to importdefinitions of the specified importType from the namedTDQ.




EYUVS1017W Repository record for resource(resourcetype, resourcename) contains aninvalid version identifier. Record notexported.

Explanation: An attempt to export the resourceresourcetype, resourcename has failed because the recordcannot be read by the Web User Interface. This isbecause the resource contains a version identifier thatdoes not match the current version of CICSPlex SM.

System action: The named resource is not exportedbut the rest of the input stream is processed. The useris not informed of the failure.

System action: Ensure that the Web User Interfaceserver repository has been correctly migrated to thecurrent version of CICSPlex SM.


EYUVS1018I Import completed successfully. countobjects read from TDQ tdqname.




Destination: EYULOG

EYUVS1019W Partial import completed. count objectsfrom TDQ (tdqname) rejected.




Destination: EYULOG

EYUVS1020E Import of resources failed. countobjects from TDQ (tdqname) rejected.

Explanation: No resources could be importedsuccessfully by the request to import menu or view setdefinitions.



Destination: EYULOG



EYUVS1030E TDQ (tdqname) is invalid for export.

Explanation: No resources could be exported becausethe export transient data queue (TDQ) is invalid. TheTDQ may be in an invalid state, or may have beendefined incorrectly.


System action: Ensure that the TDQ is open andenabled, and has been defined correctly.

Destination: EYULOG

EYUVS1050E Import encountered unexpectedcharacter in record number nn of dataset ( dsname ), member ( membername ).

Explanation: The import process encountered a badlyformatted record in the input data set member. Thedefinitions have probably been corrupted.

System action: Menu or view set definitions that weresuccessfully completed before the definition in error areretained. The menu or view set definition thatcontained the error is not imported. Further menu orview set definitions in the data set member are ignored.

System action: Review the import data set member tosee if it has been damaged. Use another copy orreexport from source, if available. If necessary, collectAUXTRACE, EYULOG and input data set, and contactIBM service.


EYUVS1051E Import string missing from recordnumber nn of data set (dsname), member(membername).





EYUVS1052E Import unable to obtain versionnumber in record number nn of data set( dsname ), member ( membername ).





EYUVS1053E Import unable to obtain index numberin record number nn of data set (dsname ), member ( membername ).





EYUVS1054E Import found invalid data in recordnumber nn of data set ( dsname ),member ( membername ).



System action: Review the import data set to see if ithas been damaged. Use another copy or reexport fromsource, if available. If necessary, collect AUXTRACE,EYULOG and input data set, and contact IBM service.


EYUVS1055E Import found invalid string in recordnumber nn of data set ( dsname ),member ( membername ).

Explanation: The import process encountered a badlyformatted record in the input data set member. Theexported definitions have probably been corrupted.




System action: Review the import data set to see if ithas been damaged. Use another copy or reexport fromsource, if available. If necessary, collect AUXTRACE,EYULOG and input data set, and contact IBM service.


EYUVS1056E Import detected missing punctuation inrecord number nn of data set (dsname),member (membername).



Administrator response: Review the import data setto see if it has been damaged. Use another copy orexport it again from source, if available. If necessary,collect AUXTRACE, EYULOG, and input data set, andcontact IBM service.


EYUVS1057E Import found an unknown object atrecord number nn of data set (dsname),member (membername).

Explanation: The import process encountered anunknown record identifier in the input data setmember. The exported definitions have probably beencorrupted.




EYUVS1058E Import failed at record number nn ofdata set (dsname), member (membername).

Explanation: The import process has failed due topreviously recorded errors.

System action: Menu or view set definitions that were

successfully completed before the definition in error areretained. The menu or view set definition thatcontained the error is not imported. Further menu orview set definitions in the data set member are ignored.

Administrator response: Collect AUXTRACE,EYULOG, and input data set, and contact IBM service.


EYUVS1059E Import failed at record number nnwhen the end of data set (dsname),member (membername) was unexpectedlyencountered.

Explanation: The import process encountered the endof the input member (membername) before the currentmenu or view set definition had been completed. Theinput member has probably been truncated.




EYUVS1060E Import failed to open data set (dsname).

Explanation: The request to import menu or view setdefinitions specified an invalid data set name, or thespecified data set could not be opened.


Administrator response: Review the status of the dataset and correct as necessary.


EYUVS1061E Import failed to find any membersmatching, (memberpattern).

Explanation: There are no members matchingmemberpattern in the data set specified in the importrequest.


Administrator response: Review the member patternand data set name, correct as necessary.




###

###

#####

#####

#

###

####

#####

#####

#

##

##

#

####

##

#

####

####

#####

#####

#

#

###

#

##

#

##

###

#

##

#

EYUVS1062E Import encountered unknown recordversion in record nn of data set (dsname),member (membername).

Explanation: The import process has encountered arecord in the import member that has a higher versionnumber than is supported by the server. The importdata was written by a server using a higher version ofthe record.

System action: Menu or view set definitions importedsuccessfully before the definition in error are retained.The menu or view set definition that contains the erroris not imported. Further menu or view set definitionsin the data set are ignored.

Administrator response: Ensure that the release andservice level of the server is not lower than the releaseand service level of the server from which the importdata set was exported. If the problem cannot beresolved, save the content of the AUXTRACE,EYULOG, and the input data sets, and contact IBMservice.


EYUVS1063I Import 'importType' initiated for user(userid) from data set (dsname), member(memberpattern).

Explanation: Import processing is beginning to importdefinitions of the specified importType from the nameddata set and member pattern.


Administrator response: None.


EYUVS1064I Import completed successfully. nnobjects read from data set (dsname),member (memberpattern).



Administrator response: None.


EYUVS1065W Partial import completed. nn objectsfrom data set (dsname), member(memberpattern) rejected.



Administrator response: See the associated messagesin EYULOG.


EYUVS1066W Import of resources failed. nn objectsfrom data set (dsname), member(memberpattern) rejected.

Explanation: No resources could be importedsuccessfully by the request to import menu or view setdefinitions.


Administrator response: See the associated messagesin EYULOG.


EYUVS1067E Import of resources failed. Data set(dsname) is invalid for import.

Explanation: No resources could be imported becausethe import data set is invalid. The data set may be inan invalid state, or may have been defined incorrectly.


Administrator response: Ensure that the data set is ina valid state, and has been defined correctly.


EYUVS1068E Import of resources failed. The CICStemporary storage data set is full.

Explanation: No resources could be imported becausethe CICS DFHTEMP data set is full.


Administrator response: Enlarge the DFHTEMP dataset and try the import again.


EYUVS1069E Import failed to find data set (dsname).

Explanation: No data sets matching the data setspecified were found.


Administrator response: Check the data set name hasbeen specified correctly.


EYUVS1070E Import terminated. Import in progressby another user.

Explanation: Another user is currently performing animport. Only one user may perform an import at atime.


Administrator response: Retry the import at a latertime.



###

#####

#####

#######

#

####

###

#

#

#

####

##

#

#

#

###

###

#

##

#

###

###

#

##

#

##

###

#

##

#

##

##

#

##

#

#

##

#

##

#

##

###

#

##


EYUVS1071E Dynamic allocation of data set (dsname)failed. Return codes rrrr, cccc, dddd.

Explanation: While importing Web User Interfaceviews or menus, an attempt to dynamically allocatedata set dsname has failed. The DYNALLOC macrofailed with return code rrrr. cccc is the SVC 99 errorreason code and dddd is the additional SVC 99 errorinformation code.

System action: Import processing ends.

User response: For the meaning of the DYNALLOCreturn codes, see the z/OS MVS Programming: AssemblerServices Guide.

Destination: EYULOG

EYUVS1072I Acquiring access to server repository forimport.

Explanation: The WUI server initialization programhas requested an exclusive enqueue on the serverrepository EYUWREP for the purpose of importingdefinitions from a data set or an extrapartition TDQ.

System action: The WUI server waits until exclusivecontrol of resource EYUWREP_IMPORT has beenacquired.

User response: If this message is followed by messageEYUVS1073I, no action is required. Otherwise, checkother WUI Servers that share the server repository toidentify the holder of the enqueue. The DISPLAY GRSsystem command:

D GRS,RES=(DFHECPSM,’EYUWREP_’*)

might also be used to identify the server that holds therepository enqueue.

Destination: EYULOG

EYUVS1073I Access to server repository acquired forImport.

Explanation: The WUI server initialization programhas acquired an exclusive enqueue on the serverrepository EYUWREP for the purpose of importingdefinitions from a data set or an extrapartition TDQ.

System action: WUI initialization continues.

User response: None

Destination: EYULOG

EYUVS1100E User (userid) not authorized forrequired access (access) for resource(resourcetype, resourcename).

Explanation: User userid has attempted an action onresource resourcetype, resourcename but the action has

failed because the user does not have the necessaryaccess to the resource.

System action: The action on the named resource failsbut the rest of the input stream is processed. The useris not informed of the failure.

System action: Review the user's securityauthorizations.


EYUVS1101I (userid) modified resource (resourcetype,resourcename).

Explanation: User userid has successfully imported,created, or edited resource resourcetype, resourcename.


System action: None


EYUVS1102I User (userid) deleted resource(resourcetype, resourcename).

Explanation: User userid has successfully deleted theresource resourcetype, resourcename.


System action: None




#

###

####

###

#####

#

##

#

###

####

#

#

#

Chapter 34. EYUWGnnnn messages

EYUWG0100E Insufficient Storage for WLM MOEB

Explanation: During initialization in either the CMASor the MAS, Workload Manager (WLM) was not able toacquire enough storage for its major object environmentblock (MOEB) control block.

System action: WLM initialization terminates. CMASor MAS initialization continues.

User response: Increase the CICS region size or makemore storage available to the CMAS or MAS.

Module: EYU0WINT


EYUWG0101E WLM MOEB Registration Failure

Explanation: During initialization in either the CMASor the MAS, Workload Manager (WLM) was not able toregister its major object environment block (MOEB)control block with the Kernel Linkage component.

System action: WLM initialization terminates. A usertrace record is written to the CICS trace data set. CMASor MAS initialization continues.


Module: EYU0WINT


EYUWG0102E WLM Create Cache Failure

Explanation: During initialization in the CMAS,Workload Manager (WLM) was not able to allocate therequired data cache.



Module: EYU0WINT


EYUWG0103E WLM Termination ECB RegistrationFailure

Explanation: During initialization in the CMAS,Workload Manager (WLM) was not able to register itstermination ECB with the Kernel Linkage component.



Module: EYU0WMGR


EYUWG0104E WLM Event Notification RequestFailed

Explanation: During initialization, Workload Manager(WLM) was not able to register interest CICSPlex SMevents.

System action: WLM initialization terminates. A usertrace record is written to the CICS trace data set.


Module: EYU0WINT


EYUWG0105E WLM WMGR Transaction Failure

Explanation: The Workload Manager (WLM) longrunning task terminated abnormally.

System action: WLM terminates. A user trace record iswritten to the CICS trace data set.


Module: EYU0WINT


EYUWG0106E WLM has encountered an error whileattempting to release MAS resources

Explanation: When module EYU0WNLM was calledto free resources used during CICSPlex SM dynamictransaction routing (DTR) processing, it found that allallocated resources were associated with active tasks.

System action: An SVCdump is issued for diagnosticpurposes, and processing continues.

User response: It appears that there is a long runninguser application that invokes EYU9XLOP for DTRprocessing that is not making the required terminationcall. If that is not the case, or cannot be determined,then collect the SVCdump, the MAS's AUXTRACE dataset(s), and the complete job output from the MAS andcontact your IBM Support Center.


It might also be that the MXT setting in the region hasbeen dynamically increased during the current run ofCICS. CPSM allocates a fixed number of certain controlblocks based on the MXT setting at region initialization.If MXT is later increased dynamically, and all thepreallocated control blocks are legitimately used byactive tasks, CPSM issues this message and produce adiagnostic dump.

If you are likely to increase the MXT setting of a regiondynamically during the run of CICS, you might wantto set the MXT value in the SIT to its maximum valuefor region initialization, then lower it to its 'running'value afterward. This causes CPSM to preallocate alarger number of some control blocks during MASinitialization and reduce the chances of this errormessage and SVC dump being produced.

Module: EYU0WNLM


EYUWG0500E Workload Manager Task has had acatastrophic error - Reason (code) DebugText (text)

Explanation: The Workload Manager (WLM) longrunning task experienced an unrecoverable error. codeidentifies the reason for the failure, where:

text Provides some additional debugginginformation for use by the IBM SupportCenter.



Module: EYU0WMGR


EYUWG0501E Workload Manager Task hasencountered an unrecoverable error -restarting task

Explanation: The Workload Manager (WLM) longrunning task (WMGR) experienced an unrecoverableerror. WMGR will attempt to restart itself up to tentimes.

System action: An exception trace is issued whichmay result in a dump being taken. WMGR then restartsitself and processing continues.

User response: Collect the trace records (and possibledumps) and the job log and contact your IBM SupportCenter.

Module: EYU0WMGR


EYUWG0502E Workload Manager Task hasencountered an error restarting -terminating task

Explanation: The Workload Manager (WLM) longrunning task (WMGR) experienced an unrecoverableerror and attempted to restart itself. The restart attemptfailed.



Module: EYU0WMGR


EYUWG0500E • EYUWG0502E


Chapter 35. EYUWInnnn messages

EYUWI0001I Workload Manager Task InitializationStarted

Explanation: Initialization of the Workload Manager(WLM) long running task has begun.

System action: WLM initialization continues.


Module: EYU0WINT

Destination: EYULOG

EYUWI0002I Workload Manager Task InitializationComplete

Explanation: The Workload Manager (WLM) longrunning task has been successfully initialized.

System action: WLM initialization continues.


Module: EYU0WMGR

Destination: EYULOG

EYUWI0003I WLM Initialization Complete

Explanation: The Workload Manager (WLM)component has been successfully initialized. WLM isnow available for work.



Module: EYU0WINT

Destination: EYULOG

EYUWI0010E WLM Initialization Failed

Explanation: The Workload Manager (WLM)component could not be initialized.

System action: WLM is not available for work. A usertrace record is written to the CICS trace data set. CMASinitialization continues.


Module: EYU0WINT


EYUWI0020I date time applid WLM Routing initiatedfor Workload(workname) in RoutingRegion(sysname).

Explanation: WLM routing support has successfullyinitialized in a Routing Region, where:

worknameIdentifies the workload to which the RoutingRegion belongs.

sysnameIs the name of the Routing Region.

System action: Initialization of the Routing Regioncontinues.


Module: EYU0WNWK

Destination: EYULOG

EYUWI0021E date time applid WLM Routinginitialization failed forWorkload(workname) in RoutingRegion(sysname).

Explanation: A failure occurred during workloadinitialization in a Routing Region, where:

worknameIdentifies the workload to which the RoutingRegion belongs.

sysnameIs the name of the Routing Region.

System action: The Routing Region will be unable toroute transactions.

User response: Correct the problems which preventedWLM routing support from initializing and restart theRouting Region. If the problem persists, collect anyexception trace records and the job logs of the CMASand the Routing Region, and contact your IBM SupportCenter.

Module: EYU0WNWK


EYUWI0080I WLM workload action process forcontext (plexname) has been started -direction CMAS (cmasname)

Explanation: As part of the connection processbetween two CMASs, Workload Manager (WLM) hasbeen asked to exchange information about workloadsin the specified CICSplex, where:

action Identifies the action that WLM is performingas either:

query One CMAS is requesting informationfrom the other CMAS.


analysisOne CMAS is analyzing theinformation received from the otherCMAS.

directionIndicates what role the specified CMAS isplaying in the exchange:

directed to CMASA query is being sent to the specifiedCMAS.

initiated by CMASAn analysis of information received isbeing done by the specified CMAS.

System action: Workload query process continues.


Module: EYU0WMQM EYU0WMQW


EYUWI0081I WLM workload action process forcontext (plexname) has been completed -direction CMAS (cmasname)

Explanation: During connection of a TOR to a CMAS,the Workload Manager determined that the requiredworkload already existed in another CMAS andinitiated an query request to that CMAS to retrieve allpertinent information about the workload. Thismessage indicates the successful conclusion of thatprocess and may be issued either by the CMASinitiating the request or by the CMAS receiving therequest, where:

action Identifies the action that WLM completed aseither:

analysisOne CMAS has analyzed theinformation received from the otherCMAS.

build One CMAS has constructed theappropriate workload based oninformation received from the otherCMAS.

directionIndicates what role the specified CMAS isplaying in the exchange:

directed toA query is being sent to the specifiedCMAS.

initiated byAn analysis of information received isbeing done by the specified CMAS.

cmasnameIdentifies the CMAS that initiated this stage ofworkload processing.



Module: EYU0WMQB EYU0WMQW


EYUWI0082E WLM Workload action failed forcontext (plexname) direction (cmasname)

Explanation: During connection of a TOR to a CMAS,the Workload Manager (WLM) determined that therequired workload already existed in another CMASand initiated an query request to that CMAS to retrieveall pertinent information about the workload. Thismessage indicates the failure of that process and maybe issued either by the CMAS initiating the request orby the CMAS receiving the request, where:

action Identifies the action that WLM could notcomplete as either:

query A request for information could notbe completed.

analysisAn analysis of information could notbe completed.

directionIndicates what role the specified CMAS wasplaying in the exchange:

directed to CMASA query could not be sent to thespecified CMAS.

initiated by CMASAn analysis of information receivedby the specified CMAS could not becompleted.

System action: Workload query process fails for theCICSPlex.

User response: Other messages should appear withdetailed information about the failure.

Module: EYU0WMQM EYU0WMQW


EYUWI0083E WLM Query Workload hasencountered an unknown type duringworkload build process - nn (nn)ignored

Explanation: During composition of a workloadreceived from another CMAS, Workload Manager(WLM) encountered a record that contains an invalidcommand type or object type. The command or objecttype identifying number is inserted in the message,where:

nn Is the invalid command or object typeidentifier.

EYUWI0081I • EYUWI0083E


System action: The invalid record is ignored. Usertrace records are written to the CICS trace data set. Theworkload build process continues.


Module: EYU0WMQB


EYUWI0084E WLM Query Workload was unable tolocate object (nn), key (type), updateignored

Explanation: A request was made to update thespecified Workload Manager (WLM) object, but theobject could not be found.

System action: The update record is ignored. Usertrace records are written to the CICS trace data set. Theworkload build process continues.


Module: EYU0WMQU


EYUWI0085E WLM Query Workload has detected aWorkload synchronization failure forWorkload (name)

Explanation: During workload analysis, a workloadwas found to be active on both the inquiring CMASand the reporting CMAS. Because the workloads wereinitiated by different CMASs, they can not besynchronized to reflect the same workloadcharacteristics.

This situation can occur when two unconnected CMASsare initialized with their respective MASs (acting asTORs and AORs) and the workload becomes active inboth. When the two CMASs attempt to connect to eachother, the workloads do not reflect the sameinformation and can not be combined into a singleworkload. Note that this situation does not prevent aTOR that is using one of the workloads from routing toAORs connected to the other CMAS.

System action: The workloads are considered to beunique; they do not share any information. Theworkload query process continues.

User response: If you want to synchronize the twoworkloads, first shut down all of the TORs and AORsassociated with one of the CMASs, and then shut downthe CMAS itself. Then restart the CMAS and wait for itto establish a connection to the other CMAS. After theCMAS is fully initialized and connected, restart theTORs and AORs. The workload on each CMAS issynchronized and treated as a single workload.

Module: EYU0WMQW


EYUWI0086I Cannot import workload wlmspec.Continue install for routing regionmasname? (Y=Yes, N=No, R=Retry)

Explanation: During connection of a routing region toa CMAS, the workload manager determined that therequired workload already existed in another CMAS,however communications with that CMAS were notactive. This prevents the import of the requiredworkload.

The console is queried as to whether or not theworkload should be installed from the repositoryrecords on the local CMAS (possibly creating aduplicate workload) or whether workload installationshould be deferred until communications with a CMASwhich knows of the workload is reestablished.

Should the operator defer installation of the workload,WLM must be restarted in the TOR using the MASview after communications is reestablished.

Should the operator continue the installation of a localcopy of the workload, it is possible that the newlycreated workload contains affinity relationships thatconflict with those already established in the originalworkload.

System action: WLM waits for a response. Anexception trace is written to the CICS trace data set.The trace provides a list of CMASes where theworkload already exists, but communication with theseCMASes is not active.

User response: Entering N on the console abortsinstallation of any workload.

Entering Y on the console causes the workload to beinstalled at that time. If a CMAS that already has theworkload installed has become accessible, the workloadis imported from that CMAS. Otherwise the workloadis built from the local CMAS's data repository records.

Entering R on the console retries the workload import.If a CMAS that already has the workload installed hasbecome accessible, the workload is imported from thatCMAS. Otherwise the EYUWI0086I message andprompt are reissued.

Note:

1. If you enter a Y response before a CMAS that hasthe workload installed becomes accessible to thelocal CMAS, a duplicate workload is created. Ifdefinitional changes had been made since theoriginal workload was installed, this can result inthe workloads routing with different rules.Additionally, affinity cannot be honored betweenthe workloads. If you do not want a duplicateworkload, ensure that a CMAS that has theworkload installed becomes accessible to the localCMAS before replying Y.

EYUWI0084E • EYUWI0086I

Chapter 35. EYUWInnnn messages 191

2. The EYUWI0086I message prompt expires 15minutes after issue. At that time, a check is made todetermine whether or not a CMAS that has theworkload installed has become accessible. If onehas, the workload is imported from that CMAS. Ifnot, the EYUWI0086I message and prompt arereissued.

Module: EYU0WMQM


EYUWI0087I Attempt to query workload (workname)for context (contname) by lower levelCMAS (cmasname) is rejected

Explanation: CMAS cmasname attempted to importworkload workname for CICSPlex, but this import wasfailed because CICS BTS data was present, and CMAScmasname is at an earlier release level.

System action: Import is rejected.

User response: If you intended to share the workload,you should either create a separate workload for theCICS BTS data, or remove the CICS BTS data from theworkload.

Module: EYU0WMQW


EYUWI0087I Attempt to query workload (workname)for context (contname) by lower levelCMAS (cmasname) is rejected

Explanation: CMAS cmasname attempted to importworkload workname for CICSPlex, but this import wasfailed because CICS BTS data was present, and CMAScmasname is at an earlier release level.

System action: Import is rejected.

User response: If you intended to share the workload,you should either create a separate workload for theCICS BTS data, or remove the CICS BTS data from theworkload.

Module: EYU0WMQW


EYUWI0089E Invalid reply -- reenter

Explanation: The reply to preceding messageEYUWI0086I was not valid, that is. a character otherthan N or Y was entered.

System action: Message EYUWI0086I is reissued.

User response: Provide a valid reply to messageEYUWI0086I.

Module: EYU0WMQW


EYUWI0087I • EYUWI0089E


Chapter 36. EYUWMnnnn messages

EYUWM0400I Workload type (name) has beensuccessfully installed for Context(plexname) - initiated by CMAS(cmasname)

Explanation: Workload information was received fromthe specified CMAS and installed in the specifiedCICSplex, where:

type Identifies the type of workload informationthat was installed as one of the following:

v Specification

v Definition

v Group

name Is the user-defined name for that information.

System action: Workload processing continues.


Module: EYU0WMWB, EYU0WMWI

Destination: EYULOG

EYUWM0401E Workload type (name) failed to installfor Context (plexname) - direction(objectname)

Explanation: The indicated workload specification,definition or group has failed to install in the specifiedCICSplex. This workload specification, definition, orgroup was propagated throughout the CICSplex by theindicated CMAS, where:

type Identifies the type of workload informationthat could not be installed as one of thefollowing:

v Specification

v Definition

v Group


directionIndicates what role the specified CMAS wasplaying in the exchange:

initiated by join of TORA query could not be sent to thespecified CMAS.

received fromAn analysis of information receivedby the specified CMAS could not becompleted.

There may be other related messages further detailingthe reasons for the failure.

System action: Workload processing continues, but thespecified workload information is not available to theCICSplex. A user trace record is written to the CICStrace data set.

User response: Examine the exception trace records,and any messages issued before this one, to determinethe cause of the problem. If the problem can beidentified and corrected, then try reinstalling theworkload information. If the problem can not becorrected, then contact your IBM Support Center.

Module: EYU0WMWB EYU0WMWI EYU0WMWUEYU0WMWC


EYUWM0402I E date time applid Workload{Specification | Definition | TransactionGroup} (name) {is not defined | has notransaction links | has an invalid scopespecification} for Context(plexname).

Explanation: The specified workload informationcould not be installed for the specified reason, where:

type Identifies the type of workload informationthat could not be installed as one of thefollowing:

v Specification

v Definition

v Transaction Group


reason Explains why the workload information couldnot be installed:

is not defined No record exists in the datarepository for the specification,definition or transaction group.

has an invalid scope specification The AOR scope for the specificationor definition is invalid.

has no transaction links There are no transactions associatedwith the transaction group.

System action: Workload processing continues, but thespecified workload information is not available to theCICSplex . A user trace record is written to the CICStrace data set.

User response: Depending on the reason given, do oneof the following:


is not defined Make sure the specification, definition ortransaction group name was specifiedcorrectly. If so, then the record has beenremoved from the data repository.

has an invalid scope specification Make sure the AOR name in the specificationor definition was specified correctly and thatthe AOR itself still exists.

has no transaction links Make sure the transaction group name wasspecified correctly. If so, use the DTRINGRPview to determine what transactions areassociated with the group.

Module: EYU0WMWC, EYU0WMBD

XMEOUT Parameters: date, time, applid, {1=Specification,2=Definition, 3=Transaction Group}, name, {1=is notdefined, 2=has no transaction links, 3=has an invalid scopespecification}, plexname

Destination: Console Routecode 11 and Transient DataQueue COLG

EYUWM0403E Workload Manager Task has reportedan error processing event (event) forentity_type (entity_name)

Explanation: The Workload Manager (WLM) longrunning task experienced an internal error whileattempting to process the specified event, where:


v CICSChg

v CMASConn

v CMASDisc

v CMASExit

v CMASJoin

v Connect

v DupWrkLd

v EmStatus

v ENetDisc

v LambInterval

v LogOff

v MasJoin

v MasSick

v MasStart

v MasStop

v MasWell

v PIInterval

v PlexChg

v PlexCnfg

v RTAEvent

v SignOff

v SysGroup

If entity_type is CMAS and (entity_name) contains novalue, the CMAS is the local CMAS.

System action: Workload event processing continues.A user trace record is written to the CICS trace data set.


Module: EYU0WMEV


EYUWM0404E Workload Manager Task hasencountered an unknown eventnotification (nn) event ignored

Explanation: The Workload Manager (WLM) longrunning task received an unsolicited event record,where:

nn Is the event notification ID that was notrecognized by WLM.

System action: WLM ignores the event record andcontinues processing. The invalid event record iswritten to the CICS trace data set.


Module: EYU0WMEV


EYUWM0410I Workload type (name) has beenremoved from Context (plexname)

Explanation: The specified workload information is nolonger installed for use by the specified CICSplex,where:

type Identifies the type of workload informationthat was removed as one of the following:

v Specification

v Definition




Module: EYU0WMDF, EYU0WMWT

Destination: EYULOG

EYUWM0411I Workload Specification (wlmspec) hasbeen removed from this CMAS forContext (plexname)

Explanation: During termination of a CMAS, aworkload manager determined that a workload couldbe removed from the CMASCICSplex, where:

EYUWM0403E • EYUWM0411I


wlmspecis the name of the Workload Specification andwhere:

plexnameis the name of the CICSplex that the workloadspecification is associated with. Please notethat the Workload Specification is still installedin at least one other active CMAS.



Module: EYU0WMWT

Destination: EYULOG

EYUWM0420I Routing System (sysname) has beenjoined to Workload (name)

Explanation: The specified routing system has beenconnected to the specified workload. The routingsystem is now available for use by WLM.



Module: EYU0WMTJ

Destination: EYULOG

EYUWM0421I Routing system (sysname) has beenremoved from Workload (name)

Explanation: The connection between the specifiedrouting system and the specified workload has beenremoved. The routing system is no longer available foruse by WLM.



Module: EYU0WMTT

Destination: EYULOG

EYUWM0422E Routing System (sysname) alreadyactive in Workload (name)

Explanation: An attempt was made to link thespecified Routing System to a new workload, butWorkload Manager (WLM) determined that theRouting System is already active and linked to thespecified workload.

System action: Creation of the new workload fails.The Routing System continues to be managed by thespecified workload.

User response: Use the WLMSCOPE view to reviewthe links that are defined between Routing Systems andworkloads. Then collect the trace records and the joblog and contact your IBM Support Center.

Module: EYU0WMWC


EYUWM0423I Target region (sysname) has beenquiesced for Context (plexname)

Explanation: All Workload Manager (WLM) activityhas been quiesced for the specified target region in thespecified CICSplex. When a request is made to quiescea target region for one workload, that target region isquiesced for all workloads in the CICSplex. The factthat a target region is quiesced only indicates thatWLM no longer considers it for routing purposes.

System action: The target region is marked asquiesced and is no longer available to WLM forrouting. Workload processing continues.


Module: EYU0WMQA

Destination: Console, and transient data queuedestination COLG. (By default, this is EYULOG).

EYUWM0424I Target region (sysname) has beenactivated for Workload (name)

Explanation: The indicated target region has beenactivated for the indicated workload. This indicates thatWLM may now route transactions to this target regionas it is available for work.



Module: EYU0WMAA

Destination: EYULOG

EYUWM0425I Target region (sysname) has beenterminated for Workload (name)

Explanation: The indicated target region is no longeractive in the indicated workload. This means that theCMAS no longer has any connection to this MAS andthe MAS will not be available for transaction routine.



Module: EYU0WMAT

Destination: EYULOG

EYUWM0426I type (name) already installed inWorkload (name) - parameter ignored

Explanation: A transaction or transaction group thatwas to be installed as part of a workload definition wasfound to already exist in an active workload, where:

type Indicates what was already installed:

DefinitionThe definition is already installed.

EYUWM0420I • EYUWM0426I


TransactionThe transaction is already installed aspart of another transaction group.

Group The definition of the transactiongroup is different from one that isalready installed under the samename; the existing one remains ineffect.

name Identifies the specific transaction or transactiongroup and the workload in which it isinstalled.

The indicated parameter is not reinstalled.



Module: EYU0WMWI

Destination: EYULOG

EYUWM0427I Parameters have been ignored duringthe installation of Workloaddefinition|group (def name|group name) forcontext (context)-received from (cmasname)

Explanation: During installation of the indicatedWLM definition or group, duplicate parameters wereencountered and subsequently ignored.



Module: EYU0WMWI

Destination: EYULOG

EYUWM0428I WLMDEF (wlmdefname1) alreadyinstalled in Workload (workloadname) as(wlmdefname2) - parameter ignored

Explanation: While attempting to install the specifiedWLM definition, it was found to match all theparameters of a previously installed definition.

System action: The definition is not installed.


Module: EYU0WMWI

Destination: EYULOG

EYUWM0429E WLMDEFs (defname1) and (defname2)for Workload (workloadid) containconflicting parameters. WLMDEF(defname3) is ignored

Explanation: During installation of the specifiedworkload, two workload definitions were found tohave the same transaction group, LUname, and user IDvalues, but different AOR scopes. The conflicting AOR

scopes would make routing decisions impossible, soone of the WLMDEFs is discarded, where:

System action: The indicated workload definition isnot installed.

User response: Do one of the following:

v change one of the workload definitions to use adifferent transaction group, LUname, or user ID.

v remove one of the definitions from the workload.

Module: EYU0WMBD, EYU0WMWI, EYU0WMBP

Destination: fonsole, job log, EYULOG

EYUWM0430I Workload workloadid transition to type:sysname at sysplex reason

Explanation: The routing algorithm for the specifiedworkload is changing because an application-owningregion (AOR) or terminal-owning region (TOR) namedin the workload underwent a change in status, where:

workloadidIdentifies the workload that is affected by thechange.

type Identifies the algorithm to which the workloadis changing as GOAL, LNGOAL, LNQUEUEor QUEUE.

sysnameIs the name of the AOR or TOR that causedthe change.

sysplex Is the name of the MVS sysplex where theCICS system is running.

reason Indicates the reason for the change as one ofthe following:

InitializingThe specified CICS system isinitializing.

TerminatingThe specified CICS system isterminating.

Changing statusThe sysplex changed its MVS/WLMstatus.

This message is issued only when the workloadspecification (WLMSPEC) identifies GOAL or LNGOALas the algorithm type.

System action: The routing algorithm for all TORs inthe workload changes to the type specified in thismessage.


Module: EYU0WSUA

Destination: EYULOG



EYUWM0431E Target region (sysname) has failedactivation for Workload (name)

Explanation: Target region (sysname) has failedactivation for Workload (name) because it has the sameAPPLID as previously activated target region (sysname).



Module: EYUTWMM0

Destination: EYULOG

EYUWM0432E WLMDEF (wlmdefname) in Workload(workloadname) cannot be processed dueto a CICS BTS Processtype specification

Explanation: Whilst installing a WLMDEF into anexisting Workload that is shared with a / CICSPlex SMV1R2M0 or V1R3M0 TOR, a non-generic CICS BTSProcesstype value was found.

System action: The WLMDEF install will fail.

User response: A Workload that is being used by aCICSPlex SM V1R2M0 or V1R3M0 TOR cannot containany CICS BTS definitions or attributes. Either removethe candidate TOR from the Workload Scope, orseparate the non-CICS BTS WLMDEFs into a differentWorkload, and include the candidate TOR in theinstallation scope for the new Workload.

Module: EYU0WMBD


EYUWM0433E TRANGRP (trangrpname) inWorkload (workloadname) cannot beprocessed due to a CICS BTS Affinityspecification

Explanation: Whilst installing a WLMDEF into anexisting Workload that is shared with a CICSPlex SMV1R2M0 or V1R3M0 TOR, a TRANGRP with a CICSBTS Affinity specification was found.

System action: The WLMDEF install will fail.

User response: A Workload that is being used by aCICSPlex SM V1R2M0 or V1R3M0 TOR cannot containany CICS BTS definitions or attributes. Either removethe candidate TOR from the Workload Scope, orseparate the non-CICS BTS TRANGRPs into a differentWorkload, and include the candidate TOR in theinstallation scope for the new Workload.

Module: EYU0WMBD


EYUWM0434W Multiple conntype connections areinstalled from routing region (torname)to target region (aorname) WLM will useconnection (conn)

Explanation: During activation of a routing region ortarget region, multiple connections were discoveredbetween the routing region and the target region,where:

conntypeis the connection type.

tornameis the name of the routing region.

aornameis the name of the target region.

conn is the name of the connection that WLM willuse to route from the routing region to thetarget.

System action: This message and a trace record areissued. WLM attempts to route from the routing regionto the target region using the connection indicated inthe message. Note that if routing is not possible overthis connection, WLM will not switch to any alternateconnection between the routing region and the targetregion.

CPSM chooses which connection to use according tothe following rules:

v After the routing region and target region are joinedto the workload, a second connection is theninstalled which is used by WLM.

v After the routing region is joined to the workloadwith both connections installed, the target regionjoins the workload. WLM uses the connection withthe name that comes first alphabetically.

v After the target region is joined to the workload withboth connections installed, the routing region joinsthe workload. WLM uses the connection with thename that comes first alphabetically.

User response: If you want routing over theconnection indicated in the message, no response isnecessary. If you want routing over a differentconnection, discard all the unwanted connections andrestart the target region.

Module: EYU0WMAA, EYU0WMTJ


EYUWM0435W An additional conntype connectionhas been installed from routing region(torname) to target region (aorname) WLMwill now use connection (newc) insteadof (oldc)

Explanation: While processing an ad-hoc install of aconnection between an active routing region and anactive target region, WLM determined that a previous

EYUWM0431E • EYUWM0435W


connection was installed, where:

conntypeis the connection type.

tornameis the name of the routing region.

aornameis the name of the target region.

newc is the name of the newly installed connectionfrom the routing region to the target.

oldc is the name of the existing connection from therouting region to the target.

System action: This message and a trace record areissued. WLM attempts to route from the routing regionto the target region using the newly installedconnection. Note that if routing is not possible over thisconnection, WLM will not switch to any alternateconnection between the routing region and the targetregion.

User response: If you want routing over the newlyinstalled connection indicated in the message, noresponse is necessary. If you want routing over adifferent connection, discard all the unwantedconnections and restart the target region.

Module: EYU0WMTU


EYUWM0436I Target region (sysname) has beenreactivated for Context (plexname)

Explanation: The indicated target region has beenactivated as a potential target of workloads in thespecified CICSplex. This indicates that WLM may nowroute transactions to this target region as it is availablefor work.



Module: EYU0WAUO


EYUWM0437I Target region masname has beenquiesced for Workload workload becauseit is already quiesced for Contextplexname.

Explanation: All Workload Manager (WLM) activityhas been quiesced for the specified target region in thespecified context because the CICS system is defined toCICSplex SM as not being a target region at startup, ora QUIESCE request was previously issued for the targetregion.

This definition is set by specifying NO in either:

WUI - on EYUSTARTCSYSDEF as "Target regionactive at startup".

API - as the DYNROUTE attribute of the CSYSDEFobject.

The target region is quiesced for all workloads in theCICSplex. The fact that a target region is quiesced onlyindicates that WLM no longer considers it for routingpurposes.

System action: The target region is marked asquiesced and is no longer available to WLM forrouting. Workload processing continues.

User response: Change the definition to YES, if thetarget region should be part of the workload at startup.

Alternatively, when the target region is ready to receivework use one of the following methods:

WUI EYUSTARTWLMAWAOR view: use theACTIVATE action to change the "Target Regionstatus". API ACTIVATE action: use theWLMAWAOR object to update the STATUS.

Module: EYU0WMAA

Destination: EYULOG

EYUWM0438I Workload Manager is using the goalalgorithm and has detected a z/OSpercentile goal.

Explanation: CICSPlex SM workload management isusing the goal algorithm and has detected a workrequest that has a percentile goal defined to the z/OSWorkload Manager.

System action: CICSPlex SM workload managementwill use z/OS Workload Manager percentile goals as afactor in determining the routing decision for any workrequests that have such goals defined.


Module: EYU0WTCL

Destination: EYULOG

EYUWM0439I TRANGRP groupid in CICSplexplexname for workload workloadidtransition to type: sysname at sysplexreason.

Explanation: The routing algorithm for the specifiedtransaction group (TRANGRP) in CICSplex plexname ischanging because an application-owning region (AOR)or terminal-owning region (TOR) named in theworkload underwent a change in status, where:

groupid Identifies the transaction group that is affectedby the change

plexnameIs the name of the CICSplex where thetransactions are running



##

#####

#

#

#

## |

|||

|||||

|||

|||

workloadidIdentifies the affected workload.

type Identifies the algorithm to which the workloadis changing as GOAL, LNGOAL, LNQUEUEor QUEUE.

sysnameIs the name of the AOR or TOR that causedthe change.

sysplex Is the name of the MVS sysplex where theCICS system is running.

reason Indicates the reason for the change as one ofthe following:

InitializingThe specified CICS system isinitializing.

TerminatingThe specified CICS system isterminating.

Changing statusThe sysplex changed its MVS/WLMstatus.

This message is issued only when the workloadtransaction group definition (TRANGRP) identifiesGOAL or LNGOAL as the algorithm type.

System action: The routing algorithm for all TORs inthe workload changes to the type specified in thismessage.


Module: EYU0WSUA

Destination: EYULOG

EYUWM0440I Transaction group trangrpid inCICSplex plexname for workloadworkloadid algorithm reset to {GOAL |INHERIT | LNGOAL | LNQUEUE |QUEUE}.

Explanation: The routing algorithm for the specifiedactive transaction group in the specified CICSplex forworkload workloadid has been changed to algorithm.

trangrpidIdentifies the active workload transactiongroup that is affected by the change.

plexnameIdentifies the name of the CICSplex that themodified active transaction group belongs to.

workloadidIdentifies the parent workload of the affectedactive transaction group.

type Identifies the algorithm to which the

transaction group in workload is changing aseither GOAL, LNGOAL, QUEUE, LNQUEUE,or INHERIT.

This message is issued only when the active transactiongroup (WLMATGRP) algorithm type is modified.

System action: The routing algorithm for alltransactions in the active transaction group changes tothe type specified in this message.


Module: EYU0WMUT

Destination: EYULOG

EYUWM0441 I date time applid A quiesce has beenissued for target region (sysname) forcontext (plexname).

Explanation: A quiesce request has been issued for thespecified target region in the specified CICSplex.

System action: The target region is marked asquiescing and is no longer available to WLM forrouting of transactions and programs, unless there is anactive affinity for the transaction or program. When itis determined that all affinities have ended, the targetregion will be marked as quiesced and EYULOGmessage EYUWM0423I will be issued.


Module: EYU0WAUO

Message inserts:

1. date

2. time

3. applid

4. sysname

5. plexname

Destination: COLG

EYUWM0442I Transaction group trangrpid inCICSplex plexname for workloadworkloadid status reset to {ACTIVE |DORMANT}.

Explanation: The status of a transaction groupinstalled in an active workload was reset, where:

trangrpidis the name of the active transaction group.

plexnameis the name of the CICSplex in which theworkload was active.

workloadidis the name of the active workloadspecification.

status is one of the following:



||

||||

|||

|||

|||

|||

|||

|||

|||

|||

|

|

|

|||||

|||

|||

|||

|||

||

|||

||

|||

|

|

|

||||

||

||

|||

|||

||

v ACTIVE

v DORMANT



Module: EYU0WMUT

Destination: EYULOG

EYUWM0443I Dynamic transaction trannamediscarded from transaction grouptrangrpid in CICSplex plexname forworkload workloadid.

Explanation: A dynamic transaction has beendiscarded from an active workload, where:

trannameis the transaction ID of the dynamictransaction.


plexnameis the name of the CICSplex in which theaction was executed.


System action: If the transaction is started in a routingregion, it will be routed to a target region in the defaultAOR scope identified in the workload specification.


Module: EYU0WMUT

Destination: EYULOG

EYUWM0444I Affinity from transaction grouptrangrpid to target AOR discarded inCICSplex plexname for workloadworkloadid.

Explanation: A transaction affinity between atransaction group in an active workload and a specifictarget region was forced, where:


AOR is the name of the affinity target region.

plexnameis the name of the CICSplex in which theaction was executed.


System action: If the transaction is started in a routingregion, a new transaction affinity will be established.


Module: EYU0WMUT

Destination: EYULOG

EYUWM0503I date time applid Routing region (name)is running in a sysplex optimized WLMstate.

Explanation: This routing region is now successfullyswitched into sysplex optimized workload managementmode to enable improved dynamic workload routingdecisions.

System action: The optimization status for the regionis marked as ACTIVE.


Module: EYU0WNRS

XMEOUT Parameters: date, time, applid, name


EYUWM0504I date time applid Routing region (name)is not running in a sysplex optimizedWLM state.

Explanation: This routing region is not running in asysplex optimized workload management state. Anydynamic routing decisions made by this region will bemade in non-optimized mode.

System action: The optimization status for the regionis marked as INACTIVE.

User response: None

Module: EYU0WNRS


Destination: Console routecode 11 and transient dataqueue COLG

EYUWM0505I date time applid Target region (name) isrunning in a sysplex optimized WLMstate.

Explanation: This target region has now successfullyswitched into sysplex optimized workload managementmode to enable improved dynamic workload routingdecisions.

System action: The optimization status for the targetregion is marked as ACTIVE.

User response: CICSPlex SM assumes that any regionfor which workload optimization is enabled acts asboth a dynamic router and target region. When yourequire the region issuing this message to adopt apurely routing role, then target region optimizationshould be disabled. This is achieved by resetting theUPDATERS attribute of the CICS system definition



|

|

|

|

|

|

||||

||

|||

||

|||

|||

|||

|

|

|

||||

|||

||

||

|||

|||

||

|

|

|

object (CSYSDEF) in CICSPlex SM to zero. TheUPDATERS attribute can be changed in an activeregion using the MAS resource table or view set.

Module: EYU0WNRS



EYUWM0506I date time applid Target region (name) isnot running in a sysplex optimizedWLM state.

Explanation: This target region is not running in asysplex optimized workload management state. Anydynamic routing decisions for this region will be madein non-optimized mode.

System action: The optimization status for this regionis marked as INACTIVE.

User response: None

Module: EYU0WNRS



EYUWM0507I I date time applid Routing region (name)optimization termination reason:(reason).

Explanation: The routing region optimization hasterminated. The reason gives an indication of the cause:

RS server failureThe Region Status (RS) server has terminatedunexpectedly. Possible reasons for this caninclude a failure in the z/OS coupling facility.For example, a system operator interventionresulted in the termination or cancellation ofthe RS server address space.

Optimization disabledThe Optimization enablement status for therouting region has changed from enabled todisabled. This action might have been takenby a CICSPlex SM WUI user or an applicationprogram that uses the CICSPlex SM API.

RSPOOLID changedThe "RS Server pool name" attribute in theCPLEXDEF resource definition that describesthe current CICSplex has been modified whileregions in the CICSplex are in-flight. Allsubsequent dynamic routing requests made byWLM routing regions in the CICSplex aremade in non-optimized more until theCICSplex is restarted.

System action: The Optimization Status for the regionis marked as INACTIVE. Workload manager continues

to handle dynamic routing requests from CICS, butrouting regions determine the potential target regionsusing non-optimized processing.

User response: Depending on the reason, take thefollowing action:

RS server failureCheck the MVS system log for the reason whythe RS server terminated. When appropriate,restart the RS Server address space.

Optimization disabledUse the MAS WUI view for the reportedregion to verify the state of the "Optimizationenablement" setting. If it is in a disabled state,re-enable the setting.

RSPOOLID changedVerify the setting of the "RS Server pool name"attribute of the CPLEXDEF resource definitionthat describes the current CICSplex.

If the change of name is not valid, change itback to its original name to resume optimizedrouting mode for regions that are enabled foroptimization.

As soon as the RS server is available, workloadmanager automatically switches back into optimizedrouting mode for regions that are enabled foroptimization.

Module: EYU0WNRS EYU0WNHD

XMEOUT Parameters: date, time, applid, name, reason


EYUWM0508I I date time applid Target region (name)optimization termination reason:(reason).

Explanation: The target region optimization hasterminated. The reason gives an indication of the cause.

reason Explains why the workload managementoptimization has stopped. Possible reasonsinclude:

RS server failureThe Region Status (RS) server cannotsupport WLM optimization because,for example, the coupling facility hasfailed.

Optimization disabledWLM optimization has been stoppedby a user.

RSPOOLID changedThe CPLEXDEF RSPOOLID value hasbeen changed.

Link to DFHRSFDL failedAn error occurred during the

EYUWM0506I • EYUWM0508I I


|||

||

||||

|||||

|||

|||

||

coupling facility data table filecreation process while trying to linkto program DFHRSFDL in DFHRSSR.

System action: The Optimization Status for the regionis marked as INACTIVE. If message EYUWM0508I isissued in a CMAS, it means that the CMAS was unableto retrieve the region status block during AORactivation. Workload Optimization might still bemarked ACTIVE for the region if status recording canbe started in the target region.

User response: Depending on the reason, take thefollowing action:

RS server failureCheck the cause of the Region Status (RS)server failure.

Optimization disabledNo action required.

RSPOOLID changedThe region must be restarted to resumerunning in optimized state with the newRSPOOLID. If the CPLEXDEF RSPOOLIDchange was unintentional change the valueback to its original value.

Link to DFHRSFDL failedThe CFDT could not be created because thelink to DFHRSFDL failed. Verify that the IBMsupplied group DFHRS is included in yourGRPLIST. Examine the CICS job log todetermine if other messages occurred earlierthat may explain the failure. If not, collect theauxtrace data sets and the complete job outputfrom the MAS and the CMAS it connects to,and contact your IBM Support Center.

Module: EYU0WNRS EYU0WNHD EYU0WMAA

XMEOUT Parameters: date, time, applid, name, reason



|||

|||||||

||

|||

||

||||||

||||||||||

|

|

||

Chapter 37. EYUWRnnnn messages

The text of these messages, like the program itself, can be modified. If theEYU9WRAM program has been modified at your enterprise, the text and meaningof these messages may vary.

The EYUWRnnnn messages are issued by the user-modifiable program calledEYU9WRAM, which CICSPlex SM distributes as part of its Workload Managercomponent. The EYU9WRAM program can be modified to control the dynamictransaction routing process used by CICSPlex SM. For more information aboutEYU9WRAM and the CICSPlex SM Workload Manager, refer to the CICSPlexSystem Manager Managing Workloads manual.

The following variables are used in EYUWRnnnn messages, as distributed byCICSPlex SM:

fnameThe name of the EYU9WRAM function being processed, as one of thefollowing:

SM_BALANCESelects a target AOR from a list of candidates.

SM_CREAFFCreates an affinity to an AOR.

SM_DELAFFDeletes an affinity to an AOR.

SM_ROUTERoutes a transaction to a named AOR, bypassing normal CICSPlex SMprocessing.

SM_SCOPEReturns a list of candidate AORs.

fcodeThe numeric code of the EYU9WRAM function being processed, as one of thefollowing:

0 Route Select

1 Route Error

2 Route Termination

3 Transaction ABEND

4 Route Notify

EYUWR0001E Internal Error Raised in EYU9WRAM:Error is text

Explanation: The EYU9WRAM program detected anunexpected error, where:

text Identifies the error as one of the following:

Nonzero return code from API: RC=code.A call to the WLM internal API returned a

nonzero return code. The return code from theWLM API should always be zero, where:

code Identifies the return code as a decimalvalue.

The WLM API function processor was notcalled.


Invalid input COMMAREA size: Size=nnn.The size of the COMMAREA passed toEYU9WRAM was not as expected, where:

nnnn Is the size of the COMMAREA as adecimal value.

Unknown Function in WCOM_CTYPE:Function=fcode.

The specified function code is not known tothe EYU9WRAM program where fcode is asdescribed in the introduction to theEYUWRnnn messages.

Unknown API Response from fname:RESPONSE=code.

The API response code received from thespecified EYU9WRAM function is not known,where:

code Identifies the response code as adecimal value.

Unknown API Reason from fname: REASON=code.The API reason code received from thespecified EYU9WRAM function is not known,where:

code Identifies the reason code as adecimal value.

System action: The transaction that was using theEYU9WRAM program is not routed.

User response: Report the problem to the person atyour site who is responsible for workload managementand the EYU9WRAM program.

The most likely causes of an internal error inEYU9WRAM are:

v An improper user modification to EYU9WRAM.

v Maintenance being applied to CICSPlex SM but notto the EYU9WRAM program.

Module: EYU9WRAM

Destination: CICS user terminal

EYUWR0002W warning text

Explanation: The EYU9WRAM program was invokedfor a Route Error function after having selected an AORfor routing. The selected AOR is not available and thereare no other AORs from which to select, where:

warning textIdentifies the problem as one of the following:

v The CICS link to the selected AOR (typeid)was not found.

v The CICS link to the selected AOR (typeid) iscurrently out of service.

v No sessions are available for route to AOR(typeid).

v An allocation timeout occurred on thetransaction route to AOR typeid.

typeid Identifies the AOR that is not available by its:

APPLID applidEight-character application identifier,if available.

SYSID sysidFour-character system identifier, if theAPPLID is not available.



Module: EYU9WRAM


EYUWR0003W The Affinity AOR (typeid) is notavailable because the reason. text

Explanation: The EYU9WRAM program was invokedfor a Route Select or Route Error function and callSM_SCOPE to obtain a scope list. The scope listcontained a single affinity AOR, which was notavailable, where:

typeid Identifies the AOR that is not available by its:



dt.reason dd.identifies the reason the AOR isnot available, as one of the following:

AOR is down.The AOR is not active.

CICS Link to the AOR is not available.The link to the AOR is either notdefined or not in service.

AOR job is different.The AOR is active but the Jobterminated and restarted again afterthe affinity was initially created.

text describes the new state of the affinity

The affinity remains.Neither the EYU9WRAM programnor CICSPlex SM deleted the affinity.

The affinity is ended.Either EYU9WRAM or CICSPlex SMdeleted the affinity.


User response: Report the problem to the person at

EYUWR0002W • EYUWR0003W


your site who is responsible for workload managementand the EYU9WRAM program.

Module: EYU9WRAM


EYUWR0101E Invalid Request to CPSM:FUNCTION=fname, REASON=code.

Explanation: The specified EYU9WRAM functionreturned an invalid request response where:

fname Is as described in the introduction to theEYUWRnnn messages

code Identifies the reason code as a decimal value.

System action: The transaction that was using theEYU9WRAM program is not routed. A user tracerecord is written to the CICS trace data set.


Module: EYU9WRAM


EYUWR0102E Parameter Error on call to CPSM:FUNCTION=fname, REASON=code.

Explanation: The specified EYU9WRAM functionreturned a parameter error response where:





Module: EYU9WRAM


EYUWR0103E Function Error on call to CPSM:FUNCTION=fname, REASON=code.

Explanation: The specified EYU9WRAM functionreturned a function error response where:




User response: Report the problem to the person at

your site who is responsible for workload managementand the EYU9WRAM program.

Module: EYU9WRAM


EYUWR0104E CPSM Reports an unexpected erroron FUNCTION fname.

Explanation: The specified EYU9WRAM functionencountered an unexpected error where fname is asdescribed in the introduction to the EYUWRnnnmessages.



Module: EYU9WRAM


EYUWR0201W The CICS link to the SM_ROUTEselected AOR (typeid) is not available.

Explanation: The SM_ROUTE function of theEYU9WRAM program determined that the selectedAOR is not available for routing, where typeid identifiesthe AOR that is not available by its:

APPLID applidEight-character application identifier, ifavailable.

SYSID sysidFour-character system identifier, if the APPLIDis not available.


User response: Report the problem to the person atyour site who is responsible for workload managementand the EYU9WRAM program. Note that the sampleEYU9WRAM program, as delivered with CICSPlex SM,does not use the SM_ROUTE function.

Module: EYU9WRAM


EYUWR0301W The initial affinity transaction cannot be routed because reason.

Explanation: The SM_SCOPE function of theEYU9WRAM program determined that an affinity to anAOR is required but can not be created, where reasonidentifies the reason an affinity can not be created asone of the following:

required CICSPlex SM services are not available.Either the CMAS to which the TOR is attached

EYUWR0101E • EYUWR0301W


is not active, or the workload that the TOR isusing has been frozen. In the first case, theWLMAWTOR view shows a value of YES inthe Connection Lost field. In the second case,the WLMAWORK view shows a status ofFROZEN.

no systems are available.There are no AORs available for routing. TheWLMAWAOR view shows the status of AORsdefined as part of the workload.



Module: EYU9WRAM


EYUWR0401W warning text

Explanation: The SM_BALANCE function of theEYU9WRAM program returned a warning response,where:

warning textIdentifies the problem as one of the following:

No AORs are available for TransactionRouting.

SM_BALANCE determined that noneof the AORs presented to it forselection were available for routing.

The required affinity AOR (typeid) is notactive. SM_BALANCE identified an affinity

with the specified AOR and isobligated to select that AOR forrouting. However, the AOR is notactive and can not be selected.

The CICS link to the affinity AOR (typeid) isnot available.

SM_BALANCE identified an affinitywith the specified AOR and isobligated to select that AOR forrouting. However, the CICS link tothe AOR is not available.

The affinity transaction cannot be routedbecause required CICSPlex SM services arenot available.

SM_BALANCE is obligated to createan affinity with one of the AORspresented to it, but the requiredCICSPlex SM services are notavailable.

typeid Identifies the affinity AOR by its:





Module: EYU9WRAM


EYUWR0501W Affinity to AOR (typeid) was notcreated because the reason.

Explanation: The SM_CREAFF function of theEYU9WRAM program returned a warning response,where:

typeid Identifies the AOR by its:



reason Identifies the reason, as one of the following:

AOR is quiescedThe AOR is quiesced; no newaffinities can be created to it.

AOR is marked ignoreThe EYU9WRAM program previouslymarked the AOR to be ignored byCICSPlex SM.

transaction group is dormantThe transaction group for thetransaction is dormant.

AOR is downThe AOR is not active.

Workload is not activeThe create affinity call was for asystem or permanent lifetime affinity,but the workload is not consideredactive.



Module: EYU9WRAM

EYUWR0401W • EYUWR0501W


Chapter 38. EYUWTnnnn messages

EYUWT0051I Workload Manager Task TerminationComplete

Explanation: The Workload Manager (WLM) longrunning task has been terminated.

System action: WLM termination continues.


Module: EYU0WMGR

Destination: EYULOG

EYUWT0052I WLM Termination Complete

Explanation: The Workload Manager (WLM)component has been terminated. WLM is no longeravailable for work.



Module: EYU0WTRM

Destination: EYULOG

EYUWT0053W Workload Specifications cannot beremoved during CMAS termination forCICSplex (plexname) because at least oneregiontype region is connected to theCMAS.

Explanation: DuringWorkload Manager (WLM) longrunning task termination of CMAS that has workloadsinstalled for a CICSplex, workload manager determinedit could not remove the workloads for the CICSplexbecause at least one routing region or target region forat least one workload associated with the CICSplex isstill connected to the CMAS, where:

plexnameis the name of the CICSplex that theworkloads are associated with, and

regiontypeis either:

routing or:

target

System action: After issuing message EYUWT0053W,message EYUWT0054I will be issued, identifying thefirst connected routing or target region that isdetermined to still be connected to the CMAS. CMAStermination then continues without terminating anyworkloads for the CICSplex.WLM

User response: Since the CMAS terminated withoutremoving its installed workloads, other CMASes can

experience problems when trying to install theworkloads, issuing message and prompt EYUWI0086I,and, if PTF UK62967 is applied, message EYUWI0090I.

To avoid this, the terminated CMAS must be restartedand connected into the CMAS network before anyother CMAS in the network tries to install anyworkloads that were installed in the terminated CMAS.

To ensure that a CMAS removes all installed workloadsfor a CICSplex when it terminates, you must ensurethat all MASes that are connected to the CMAS that arerouting or target regions for any workload associatedwith the CICSplex, are terminated before startingCMAS termination.

Module: EYU0WTRM


EYUWT0054I MAS masname is connected to theCMAS as a (regiontype) region inWorkload (wlmspec) for CICSplex(plexname).

Explanation: DuringWorkload Manager (WLM) longrunning task termination of CMAS that has workloadsinstalled, workload manager determined it could notremove the workloads for a CICSplex because at leastone MAS is still connected to the CMAS, as a routingor target region in a workload associated with theCICSplex, where:

masnameis the name of the first connected MAS

regiontypeis either:

routing or:

target and:

plexname

System action: This message will be issued aftermessage EYUWI0053W is issued, identifying therouting or target region. CMAS termination thencontinues without removing any workloads for theCICSplex.WLM

User response: This message is informational only.Please refer to the documentation for messageEYUWT0053W for user action.

Module: EYU0WTRM


EYUWT0060E WLM Termination Failed


Explanation: One or more errors occurred whileattempting to terminate the Workload Manager (WLM)component. WLM is no longer available for work.


User response: Examine the exception trace recordsand any related messages to determine the cause of theproblem.

Module: EYU0WTRM


EYUWT0061E WLM Topology resource removal hasfailed for Context (plexname) Scope(sysname)

Explanation: During termination, Workload Manager(WLM) was not able to release one or more of itsoutstanding resources for the specified context andscope. WLM is no longer available for work.


User response: Examine the exception trace recordsand any related messages to determine the cause of theproblem.

Module: EYU0WPUD


EYUWT0061E


Chapter 39. EYUXCnnnn messages

EYUXC0001I Data Cache initialization complete

Explanation: The Data Cache Manager component hasbeen successfully initialized.

System action: CICSPlex SM continues to initializeother components.


Module: EYU0UCIN, EYU0XCIN, EYU3XCIN

Destination: EYULOG

EYUXC0002E Data Cache initialization failed

Explanation: The Data Cache Manager componentcould not be initialized.





EYUXC0005S Unable to register MOEB controlblock

Explanation: The Data Cache Manager initializationprocess was not able to register its major objectenvironment block (MOEB) control block with theKernel Linkage component.





EYUXC0006S Unable to create Data CacheManagement Dataspace, DSPSERVRC=rccccccc, REAS=rrrrrrrr

Explanation: The Data Cache Manager initializationprocess made a DSPSERV request to create its controldataspace and the request was unsuccessful (CMASonly).


User response: Refer to the MVS/ESA SystemProgramming Library: Application Development Macro

Reference for explanations of the return code and reasoncode. If you cannot resolve the problem using thatinformation, collect the exception trace records and thejob log and contact your IBM Support Center.

Module: EYU0XCIN


EYUXC0007S Unable to establish access to DataCache Management Dataspace,ALESERV RC= rccccccc, REAS=rrrrrrrr

Explanation: The Data Cache Manager initializationprocess made a ALESERV request to access its controldataspace and the request was unsuccessful (CMASonly).


User response: Refer to the MVS/ESA SystemProgramming Library: Application Development MacroReference for explanations of the return code and reasoncode. If you cannot resolve the problem using thatinformation, collect the exception trace records and thejob log and contact your IBM Support Center.

Module: EYU0XCIN


EYUXC0008W Maximum aggregate cache limit hasbeen reached

Explanation: A request was received to create a cache,but the maximum number of caches permitted byCICSPlex SM already exist.

System action: Data Cache Manager fails the request.A user trace record is written to the CICS trace data set.


Module: EYU0XCCC, EYU0UCCC


EYUXC0009W Maximum aggregate data cache limithas been reached

Explanation: A request was received to create orextend a cache and the maximum number of data cacheareas permitted by CICSPlex SM already exist (RMASonly).


User response: Collect the exception trace records and


the job log and contact your IBM Support Center.

Module: EYU0XCCC, EYU0XCEC, EYU0UCCC,EYU0UCEC


EYUXC0010E Unable to create dataspace dspace,DSPSERV RC=rccccccc, REAS=rrrrrrrr

Explanation: Data Cache Manager made a DSPSERVrequest to create a dataspace and the request wasunsuccessful (CMAS only), where:

dspace Is the name of the dataspace to be created, inthe following format:

cccnssss

where:

ccc Internal CICSPlex SM componentabbreviation (for example, DAT forthe Data Repository component)

n Numeric identifier, indicating thedataspace number for the associatedcache (the first dataspace is number 1,the second is number 2, etc.)

ssss CICS system identifier (SYSIDNT) ofthe CICS system on whichCICSPlex SM is executing



Module: EYU0XCCC, EYU0XCEC


EYUXC0011E Unable to establish access to dataspacedspace ALESERV RC=rccccccc,REAS=rrrrrrrr

Explanation: Data Cache Manager made a ALESERVrequest to establish access to a dataspace and therequest was unsuccessful (CMAS only), where:

name Is the name of the dataspace to be accessed, inthe following format:

cccnssss

where:

ccc Internal CICSPlex SM componentabbreviation (for example, DAT forthe Data Repository component)

n Numeric identifier, indicating the

dataspace number for the associatedcache (the first dataspace is number 1,the second is number 2, etc.)




Module: EYU0XCCC, EYU0XCEC


EYUXC0012E Unable to extend dataspace dspace,DSPSERV RC=rccccccc, REAS= rrrrrrrr

Explanation: Data Cache Manager made a DSPSERVrequest to extend a dataspace and the request wasunsuccessful (CMAS only), where:

name Is the name of the dataspace to be extended,in the following format:

cccnssss

where:

ccc Internal CICSPlex SM componentname abbreviation (for example, DATfor the Data Repository component)

n Numeric identifier, indicating thedataspace number for the associatedcache (the first dataspace is number 1,the second is number 2, etc.)




Module: EYU0XCEC


EYUXC0010E • EYUXC0012E


EYUXC0013S Unable to obtain information aboutData Cache Management Dataspace

Explanation: The Data Cache Manager initializationprocess was not able to obtain information about anexisting Data Cache Manager management dataspace(CMAS only).



Module: EYU0XCEC, EYU0XCIN


EYUXC0014W Maximum data cache limit has beenreached for compid cache

Explanation: Data Cache Manager was unable toextend an existing cache because it would requirecreation of another data cache area and the cache isalready at its CICSPlex SM-defined maximum (RMASonly).



Module: EYU0XCEC, EYU0UCEC


EYUXC0015S Unable to extend Data CacheManagement Dataspace, DSPSERVRC=rccccccc, REAS=rrrrrrrr

Explanation: Data Cache Manager has run out ofroom in its management dataspace, but the DSPSERVrequest it made to extend the dataspace wasunsuccessful (CMAS only).



Module: EYU0XCED


EYUXC0016S Maximum space allocation has beenreached for Data Cache ManagementDataspace

Explanation: Data Cache Manager has run out ofroom in its management dataspace and the dataspace

has already been allocated to its CICSPlex SM-definedmaximum (CMAS only).



Module: EYU0XCED


EYUXC0017E Unable to release resources indataspace dspace DSPSERV RC=rccccccc,REAS=rrrrrrrr

Explanation: Data Cache Manager made a DSPSERVRELEASE request for unrequired dataspace resourcesand the request was unsuccessful (CMAS only).

System action: Data Cache Manager ignores thefailure. A user trace record is written to the CICS tracedata set.


Module: EYU0XCBR


EYUXC0020E Cache request exceeds extension sizefor compid cache.

Explanation: Data Cache Manager was unable tosatisfy a block allocation request because the size of therequest exceeded the size of a data cache area, where:

compid Is the abbreviation for the component thatrequested the block allocation (for example,DAT for Data Repository).



Module: EYU0UCBA, EYU0XCBA


EYUXC0021S type auxiliary storage limit has beenreached

Explanation: The Data Cache Manager has determinedthat the current request would cause CICSPlex SM toexceed the auxiliary Storage usage limit for this CMASor for the MVS image.

This message is normally issued as a result of abnormalgrowth of one or more cache data spaces due to an

EYUXC0013S • EYUXC0021S

Chapter 39. EYUXCnnnn messages 213

exceptional condition. When the CMAS is restarted theCache component is reinitialized and some excess cachestorage is released. If the CMAS terminates repeatedlyafter issuing this message, there may be insufficientauxiliary storage available to support the normalstorage requirements of the CMAS. It may be necessaryto provide additional auxiliary storage by adding orexpanding external page data sets, where:

type identifies the limit which would be exceeded:

CPSM The maximum percent of auxiliarystorage slots which may becommitted to a CMAS.

total The maximum percent of auxiliarystorage slots which may be in use.

System action: Message EYUXC0024S is issued,SDUMP is taken and the CMAS is terminated. If CMASinitialization completed before the failure, an attempt ismade to ARMRESTART the CMAS.

User response: If the CMAS failed duringinitialization, increase one or both of theMAXAUXCPSM and MAXAUXTOTL parameters andrestart the CMAS. If CMAS initialization completedbefore the failure, capture the CMAS job output andthe SDUMP created in response to this error, andcontact your IBM Support Center.

Module: EYU0XCCL


EYUXC0022S Maximum aggregate data cache limithas been reached.

Explanation: A request was received to create orextend a cache and the maximum number of data cacheareas permitted by CICSPlex SM already exist (CMASonly).


User response: Capture the CMAS job output and theSDUMP created in response to this error, and contactyour IBM Support Center.

Module: EYU0XCCL


EYUXC0023S Maximum data cache limit has beenreached for compid cache

Explanation: Data Cache Manager was unable toextend an existing cache because it would requirecreation of another data cache area and the cache isalready at its CICSPlex SM defined maximum (CMASonly), where:

compid is the abbreviation for the component whosecache is to be extended (for example, DAT forData Repository).


User response: Capture the CMAS job output and theSDUMP created in response to this error, and contactyour IBM Support Center.

Module: EYU0XCCL


EYUXC0024S The CMAS is terminating due to aprevious error with the Cachecomponent

Explanation: This message appears after messagesEYUXC0021S, EYUXC0022S, and EYUXC0023S. See thepreceding message for required User Response.

System action: An SDUMP is taken and the CMAS isterminated. If CMAS initialization completed before thefailure, an attempt is made to ARMRESTART theCMAS.

User response: Perform the actions indicated for thepreceding message EYUXC0021S, EYUXC0022S, orEYUXC0023S.

Module: EYU0XCCL


EYUXC0101I Data Cache termination complete

Explanation: The Data Cache Manager component hasbeen terminated.

System action: CICSPlex SM shutdown continues.


Module: EYU0UCTM, EYU3XCTM

Destination: EYULOG

EYUXC0022S • EYUXC0101I


Chapter 40. EYUXDnnnn messages

EYUXD0001I Data Repository initialization complete

Explanation: The Data Repository component hasbeen successfully initialized.



Module: EYU0XDIN, EYU3XDIN


EYUXD0002I action CONTEXT(plexname)MAJOR_ID(deftype)MAJOR_NAME(defname)MAJOR_VER(defver) MINOR_ID(deftype)MINOR_NAME(defname)MINOR_VER(defver) By User(userid)System(sysname) Date(dddyy)Time(hh.mm.ss)

Explanation: A change was made to the datarepository; this message serves as a record of thechange, where:

action The type of change that was made, as one ofthe following: ADD, UPDATE, DELETE,GENERIC DELETE, or INTERNAL DELETE.

A generic delete is one that used a genericname (including the characters + or *) to affectmultiple instances of a definition. An internaldelete is one that was made as a result ofanother delete to maintain the referentialintegrity of the data repository.

plexnameThe name of the CICSplex that was affected bythe change.

deftype The type of definition that was changed,which corresponds to an administrativedefinition such as CPLXCMAS or MONDEF.

defnameThe name of the definition that was changed.

defver The version of the definition that waschanged.

userid The ID of the user who made the change.

sysnameThe name of the CICS system where thechange was made.

dddyy The date on which the change was made, inJulian format.

hh.mm.ssThe time at which the change was made.


User response: If this message accurately reflects achange that was made by a user, no action is required.If, however, this message contains information that youconsider invalid, contact your IBM Support Center.

Module: EYU0XDCR


EYUXD0003I Data Repository termination complete

Explanation: The Data Repository component hasbeen terminated.



Module: EYU0XDTM, EYU3XDTM

Destination: EYULOG

EYUXD0004I Import of PLEX(plexname) from (cmasid)successful

Explanation: A request was issued to add a CMAS tothe management of a CICSplex, where:

plexnameIdentifies the name of the CICSplex beingimported.

cmasid Identifies the maintenance point CMAS fromwhich CICSplex information was beingimported.

System action: This message is written to theEYULOG of the CMAS that was being added. Thedefinitions required to manage the specified CICSplexare added to the data repository; the CMAS can nowparticipate in the management of the CICSplex.

User response: No action is required.

Module: EYU0XDIP

Destination: EYULOG

EYUXD0005I Managed Object Services initializationhas started

Explanation: The Managed Object Servicessubcomponent of the Data Repository component isbeing initialized.

System action: Initialization of Managed ObjectServices continues.


Module: EYU0XDIN


Destination: EYULOG

EYUXD0006I Managed Object Services initializationcomplete

Explanation: The Managed Object Servicessubcomponent of the Data Repository component hasbeen successfully initialized.



Module: EYU0XDMI

Destination: EYULOG

EYUXD0007I Managed Object Services terminationrequested

Explanation: The Managed Object Servicessubcomponent of the Data Repository component isbeing terminated.

System action: Termination of Managed ObjectServices continues.


Module: EYU0XDMT

Destination: EYULOG

EYUXD0008I Managed Object Services terminationcomplete

Explanation: The Managed Object Servicessubcomponent of the Data Repository component hasbeen terminated.


User response: None

Module: EYU0XDMT

Destination: EYULOG

EYUXD0009E I/O error on repository for CMAScmasid Offline Maintenance Required.CMAS will terminate.

Explanation: An input/output error has occurred inthe repository.

System action: CMAS terminates.

User response: Restore repository from backup.

Module: EYU0XDKL

Destination: EYULOG

EYUXD0010E CICSPlex SM Version nnnn Does notMatch Repository Version yyyy. CMASTerminates.

Explanation: During initialization of a version nnnnCMAS, CICSPlex SM detected a version yyyy DataRepository.


User response: Ensure that the correct DataRepository (EYUDREP) is being used with the CMAS.If the CMAS has been migrated to a later Version ofCICSPlex SM, ensure that the Data Repository has beenconverted to the appropriate TARGETVER withEYU9XDUT. For details of EYU9XDUT, see theCICSPlex SM Setup manual.

Module: EYU0XDIN

Destination: Console, Job Log, EYULOG

EYUXD0011S The Data Repository is full; all furthermodifications will fail. The repositorymust be expanded.

Explanation: An attempt to update the DataRepository failed due to a NOSPACE condition.

System action: The CMAS continues to run, but theprocess that initiated the Data Repository updateterminates.

User response: To successfully update the DataRepository, stop the CMAS and reorganize or expandthe Data Repository.

Module: EYU0XDAI, EYU0XDCA, EYU0XDCR,EYU0XDIP, EYU0XDRS, EYU0XDUI


EYUXD0013E Error converting Repository for CMAScmasname from non-recoverable torecoverable. CMAS Terminates.

Explanation: During CICSplex add or removeprocessing, an error occurred while changing the statusof the repository from non-recoverable to recoverable,where:

cmasnameis the name of the CMAS.

System action: The CMAS is terminated.

User response: Before attempting to restart the CMAS,collect the CMAS job output and auxtrace data set(s).restart the CMAS with a COLD start. If the failurepersists, contact your IBM Support Center., providingthe job output and trace data set(s).

Module: EYU0XDIP, EYU0XDDP


EYUXD0006I • EYUXD0013E


EYUXD0014I date time applid Special repositoryrecovery processing has started.

Explanation: The special repository recovery processhas started to check records in the EYUDREP file forerrors to automatically correct them.

System action: If any EYUDREP records are found tobe in error, they are automatically corrected.

User response: None

Module: EYU0XDRR


EYUXD0015I date time applid Special repositoryrecovery processing has ended.

Explanation: The process to check records in theEYUDREP file for errors and automatically correct themhas ended.

System action: None

User response: None

Module: EYU0XDRR


EYUXD0016W CSD definition for file EYUDREPNis missing or not installed. CMASinitialization continues.

Explanation: During CMAS initialization, DataRepository initialization detected that the alternate filedefinition for the Data Repository file, EYUDREPN,was not installed.

System action: CMAS initialization continues withoutuse of the EYUDREPN file definition. This has anadverse effect on the performance of CICSplex add andremove processing.

User response: Ensure that the IBM-supplied CMASCSD group EYU310G0 is installed on the CMAS.

Module: EYU0XDIN


EYUXD0017E The Data Repository records forCICSplex (cicsplex) appear to becorrupted. Resyncronization with theMaintenance Point CMAS (cmasname) isrequired.

Explanation: While this CMAS was processing DataRepository updates for a CICSplex that were shippedfrom the maintenance point CMAS for the CICSplex, anunrecoverable error was encountered, where:

cicsplexis the name of the CICSplex

cmasnameis the name of the maintenance point CMAS.

System action: The error is noted internally, a dump istaken, and CMAS execution continues. However, nofurther updates to this CMAS's repository for thisCICSplex is processed.

User response: All MASs connected to this CMASshould be terminated, and the CMAS should then berestarted. This results in this CMAS performingrepository syncronization with the maintenance pointCMAS. Because the system has noted that this CMAS'srepository is corrupted for this CICSplex, the CICSplexis removed from and then re-added to this CMAS'srepository as part of the repository syncronizationprocess.

Module: EYU0XDRS


EYUXD0018I Enhanced MOS initialization inprogress.

Explanation: The enhanced MOS initialization phaseof CMAS initialization has started.


User response: No action is needed. The message isfor information only.

Module: EYU0MOIT

Destination: EYULOG

EYUXD0019I Enhanced MOS initialization complete.

Explanation: The enhanced MOS initialization phaseof CMAS initialization completed successfully.



Module: EYU0MOIT

Destination: EYULOG

EYUXD0020E Enhanced MOS initialization failed.

Explanation: A failure occurred during the enhancedMOS initialization phase of CMAS initialization.

System action: The system terminates.

User response: Examine the job log for messagesissued earlier which might indicate the reason for thefailure. Examine any dumps and traces which havebeen produced. If no reason for the failure can befound, contact your IBM support centre.

Module: EYU0MOIT

Destination: EYULOG



EYUXD0021I Enhanced MOS termination in progress.

Explanation: The enhanced MOS termination phase ofCMAS termination has started.



Module: EYU0MOIT

Destination: EYULOG

EYUXD0022I Enhanced MOS termination complete.

Explanation: The enhanced MOS termination phase ofCMAS termination completed successfully.



Module: EYU0MOIT

Destination: EYULOG

EYUXD0024E Field (field) value (value) has beendeleted from modification string.

Explanation: A modification string contains a fieldwhich does not exist at the target end. This messagecan be issued by the CICSPlex SM API or the batchedrepository-update facility. This message can arise whena resource assignment is installed in multiple CMASswhich are at different levels of CICSPlex SM and thefield that is to be modified is unknown at the lowerCICSPlex SM levels.

System action: The modification string is installedwith the fields removed that are unknown at thisrelease.

User response: Correct the error in the input string.

Module: EYU0MOSS

Destination: EYULOG

EYUXD0025E Field (fielda) requires field (fieldb) inMAL(mal).

Explanation: This message is issued by theCICSPlex SM batched repository-update facility. Fieldsfielda and fieldb are both required for the creation of abase table. However the batched repository inputcontains only fielda.

System action: The batched repository-update facilityrequest fails.

User response: Correct the error in the input andreissue the request.

Module: EYU0MOMB

Destination: EYULOG

EYUXD0026E Field (fielda) mutually exclusive with(fieldb) in MAL(mal).

Explanation: This message is issued by theCICSPlex SM batched repository-update facility. Eitherfielda or fieldb may be specified for the creation of abase table but not both. However the batchedrepository input contains both fielda and fieldb.

System action: The batched repository-update facilityrequest fails.

User response: Correct the error in the input andreissue the request.

Module: EYU0MOMB

Destination: EYULOG

EYUXD0027E MAL (mal )cannot be transformed.Metadata not available.

Explanation: A transformation between two systemsfailed. This is a CICSPlex SM internal error.

System action: A MAL is a request to run a programin another MAS or CMAS. The program request is sentto its destination without being transformed. Ifassociated resource tables have changed, the programmight fail.

User response: Contact your IBM support centre.

Module: EYU0MOX2

Destination: EYULOG

EYUXD0030W The performance of the operation onthe data repository records for CICSplexcicsplex may be degraded due to therecoverable attribute of EYUDREPN.

Explanation: The EYUDREPN file has taken on therecoverable attribute of the data repository data set.The result is a degradation of performance (loggingwill occur) on the data repository records when addingor deleting a CICSplex.

EYUDREPN's recovery definition change fromnon-recoverable to recoverable could have occurred inone of two ways:

1. The Backup While Open (BWO) option wasspecified for the data repository data set associatedwith EYUDREP in the ICF catalog via the IDCAMSDEFINE CLUSTER definition. IDCAMS marks theEYUDREP data set as recoverable. Thus, when theEYUDREPN file name is associated with theEYUDREP data set, EYUDREPN is marked asrecoverable. The ICF catalog definition takesprecedence over the EYUDREPN RDO definition.

2. EYUDREPN RDO definition was copied to a usergroup and RECOVERY(NONE) was modified.

System action: CICSPlex SM processing continues.However, because EYUDREPN was defined as

EYUXD0021I • EYUXD0030W


recoverable, the operation on the data repositoryrecords may be degraded.

User response: To make the data repository eligiblefor backup while open, you must change the defaultRDO EYUDREP definition by copying the RDOEYUDREP definition to a user group and specifying thefollowing keywords:

RECOVERY(ALL)

FWDRECOVLOG( nn )

BACKUPTYPE(DYNAMIC)

where nn is a number between 1 and 99.

This definition change marks the file EYUDREP asrecoverable and any data set, while associated with theEYUDREP file name, is marked as recoverable.

Requesting BWO for the CICSPlex SM data repositorydata set via the IDCAMS DEFINE CLUSTER definitionwithin the ICF catalog is not supported.

You should not change the recovery options of theEYUDREPN FILE definition.

Module: EYU0XDDP, EYU0XDIP

Destination: job log, EYULOG

EYUXD0031E Capability mismatch(relationship) fortable(rtnum/rtname) (Service=servlevel).Local=lver/lsub : Remote=rver/rsub.

Explanation: The service and maintenance level of aresource table is incompatible with the partner systemwhere:

relationshipis the relationship between the service andmaintenance levels of the local and remotesystems and can be::

HIGH where the partner system is at ahigher level than the local system.

LOW where the partner system is at alower level than the local system.

rtnum/rtnameis the number and name of the CICSPlex SMresource table.

servlevelis the service and maintenance level of theresource table as defined in the local CMAS.

lver/lsubis the local version and subversion of theresource table.

rver/rsubis the remote version and subversion of theresource table.

The partner name is given in a later message, which isEYUCL0130E if the partner is a MAS, or EYUCP0022Eif the partner is a CMAS.

System action: Information about the system action isgiven in a later message, either EYUCL0130E orEYUCP0022E.

User response: For CMAS-to-CMAS connections, themaintenance point CMAS must not be at a lower levelthan the non-maintenance point CMAS. Restart one ofthe CMASs with a version of the CICSPlex SM loadlibraries that is at a maintenance level compatible withthe other CMAS.

For CMAS-to-MAS connections, the CMAS must not beat a lower level than the MAS. Restart either the MASor the CMAS with a version of the CICSPlex SM loadlibraries that is at a maintenance level compatible withthe other system.

Module: EYU0MOCS


EYUXD0032E Import of PLEX(plexname) from(cmasid) failed

Explanation: A request was issued to add a CMAS tothe management of a CICSplex, where:

plexnameIdentifies the name of the CICSplex beingimported.

cmasid Identifies the maintenance point CMAS fromwhich CICSplex information was beingimported.

System action: This message is written to the consoleand to the job log and EYULOG of the CMAS that wasbeing added. If the add request was made through theWUI, messages EYUVC1231E and EYUVC1272I will bereceived.

User response: If the cause of the problem cannot bedetermined by the messages displayed where the addwas attempted, collect the complete job output andauxtrace data sets from both the maintenance pointCMAS and the CMAS being added, and contact yourIBM support center.

Module: EYU0XDIP


EYUXD0033E Definitions delivered for CICSplex(plexname) by maintenance point CMAS(cmasname) cannot be processed becausethe local data repository is full.

Explanation: A data repository update for a CICSplexcould not be added to the local CMAS's data repositorybecause the local CMAS's data repository is full, where:

v plexname identifies the name of the CICSplex thedefinitions are associated with.

EYUXD0031E • EYUXD0033E


||||

|||

||

v cmasname identifies the maintenance point CMAS forthe CICSplex.

System action: This message is written to the consoleand to the job log and EYULOG of the local CMAS,and an exception trace is written to the local CMAS'sauxtrace data sets. The CMAS continues to execute, butall subsequent updates to the local data repository forthe CICSplex fail. Note that the message and trace onlyoccurs once, regardless of how many updates for theCICSplex fail.

User response: This message is preceded by messageEYUXD0011S. As the instructions in that messageindicate, the local CMAS should be terminated and itsdata repository reorganized or expanded. When thelocal CMAS is restarted and performs repositorysynchronization with the maintenance point CMAS ofthe CICSplex, the missing updates will be added to thelocal data repository.

Module: EYU0XDRS


EYUXD0038I The data repository has been upgradedfor CICSplex (cicsplex).

Explanation: While this data repository was beingupgraded from an earlier release through theEYU9XDUT utility, it was found that one or moreresources for a CICSplex were dropped because theresource type did not exist at the earlier release, where:

cicsplex is the name of the affected CICSplex.

As part of repository synchronization with themaintenance point CMAS, the dropped records havebeen restored to the data repository for this CMAS.

System action: This message is issued and CMASprocessing continues.


Module: EYU0XDRS


EYUXD0101E Data Repository initialization failed.

Explanation: The Data Repository component couldnot be initialized.


User response: Check the exception trace records, andany messages issued before this one, to determine thecause of the problem.

Module: EYU0XDIN, EYU3XDIN


EYUXD0103E Data Repository termination failed.

Explanation: An error occurred while attempting toterminate the Data Repository component.



Module: EYU0XDTM, EYU3XDTM


EYUXD0104E Data Repository initialization failed.Repository Not Defined.

Explanation: The Data Repository component couldnot be initialized because the DD statement forEYUDREP was missing or invalid.


User response: Make sure the DD statement forEYUDREP is properly specified in the CMAS startupJCL. Restart the CMAS.

Module: EYU0XDIN


EYUXD0105E Data Repository initialization failed.Cannot Open File.

Explanation: The Data Repository component couldnot be initialized because the VSAM file could not beopened.


User response: Make sure the VSAM file definition isproperly specified in the CMAS startup JCL. Restart theCMAS.

Module: EYU0XDIN


EYUXD0106E Data Repository initialization failed.Invalid File Attributes.

Explanation: The Data Repository component couldnot be initialized because the VSAM file attributes areinvalid.


User response: Make sure the file is a KSDS data set,with a key length of 64, a key position of 0, andattributes of ADD, UPDATE, DELETE, BROWSE, andREAD.

Module: EYU0XDIN




||

||||||||

||||||||

|

|

|||

|||||

|

|||

||

|

|

|

EYUXD0107E Data Repository initialization failed.SYSID Mismatch, RepositorySYSID=sysid1, CICS SYSID=sysid2.

Explanation: The Data Repository component couldnot be initialized because the SYSID specified in theEYU9XDUT repository initialization program does notmatch the SYSID of the CMAS to which it isconnecting.


User response: Correct the SYSID parameter in eitherthe EYU9XDUT program or the CMAS startup job, andthen restart the CMAS.

Module: EYU0XDIN


EYUXD0108E Data Repository initialization failed.CMAS name cmasid not defined onrepository.

Explanation: The Data Repository component couldnot be initialized because the CMAS name does notmatch a CMAS specified in the EYU9XDUT repositoryinitialization program.


User response: Correct the CMAS name on the startupjob, and then restart the CMAS.

Module: EYU0XDIN


EYUXD0109E Unable to load EYUTXDMD Module

Explanation: The Managed Object Servicesinitialization routine was unable to perform an OSLOAD for a required module, EYUTXDMD.


User response: Verify that module EYUTXDMD existsin the STEPLIB for the CMAS startup job, thenresubmit the job.

Module: EYU0XDMI


EYUXD0110E Managed Object Service initializationfailed

Explanation: The Managed Object Servicessubcomponent of the Data Repository component couldnot be initialized.


User response: Check the job log for EYUXD01nnmessages issued before this one to determine the causeof the problem. If the problem persists, contact yourIBM Support Center.

Module: EYU0XDMI


EYUXD0111E Managed Object Service terminationfailed

Explanation: The Managed Object Servicessubcomponent of the Data Repository component couldnot be properly terminated.

System action: Data Repository termination continues.A user trace record is written to the CICS trace data set.


Module: EYU0XDMT


EYUXD0112I API initialization has started

Explanation: The application programming interface(API) subcomponent of the Data Repository componentis being initialized.

System action: Initialization of the API continues.


Module: EYU0XDIN

Destination: EYULOG

EYUXD0113E Data repository initialization failed.System log must not be type dummy.

Explanation: The data repository component could notbe initialized because the CICS system log DFHLOGhas been defined as being a dummy log. In order tomaintain data integrity on the CICSPlex SM datarepository a fully functioning CICS system log isrequired.


User response: Follow the CICS procedures for settingup the system log DFHLOG.

Module: EYU0XDIN


EYUXD0601I Successful CMASDEFCMASNAME=cmasid SYSID=sysidTIMEZ=x ZONEO=nn DAYLSV=optionwritten to EYUDREP.

Explanation: A repository batch header record for thespecified CMAS has been successfully formatted. Theparameters are shown as they were specified in theEYU9XDUT repository initialization program, where:

cmasid Identifies the CMAS for which the datarepository was defined.

EYUXD0107E • EYUXD0601I


sysid Is the CICS system ID of the CMAS.

x Is a time zone code, from B – Z.

nn Is a time zone offset in minutes, from 00 – 59.

option Indicates whether daylight saving time is ineffect, as Y or N.

System action: The data repository (EYUDREP) isready for CMAS initialization.


Module: EYU9XDUT

Destination: SYSOUT

EYUXD0602E SYSPRINT must be specified.

Explanation: The SYSPRINT DD statement for theCMAS data repository was missing or invalid.

System action: Data repository initializationterminates.

User response: Make sure a valid SYSPRINT DDstatement is included in the data repositoryinitialization routine, then resubmit the job.

Module: EYU9XDUT


EYUXD0602E SYSPRINT must be specified.

Explanation: The SYSPRINT DD statement for theCMAS data repository was missing or invalid.


User response: Make sure a valid SYSPRINT DDstatement is included in the data repositoryinitialization routine, then resubmit the job.

Module: EYU9XDUT


EYUXD0604E EYUDREP VSAM file must bespecified. EYUDREP Init terminated.

Explanation: The EYUDREP DD statement for theCMAS data repository was missing or invalid.


User response: Make sure a valid EYUDREP DDstatement is included in the data repositoryinitialization JCL.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0605E Invalid parm length SYSID=statusCMASNAME=status TIMEZONE=statusZONEOFFSET=status DAYLIGHT=status.EYUDREP Init terminated.

Explanation: The length of one of the parametersspecified for the EYU9XDUT repository initializationprogram was invalid, where:

status Identifies the status of each parameter as:

ERR The parameter was in error.

OK The parameter was correctlyspecified.


User response: Correct the length of the parameters inerror, as follows:

SYSID=1- to 4-characters.

CMASNAME=1- to 8-characters.

TIMEZONE=1-character.

ZONEOFFSET=2-characters.

DAYLIGHT=1-character.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0606E Invalid parm data SYSID=statusCMASNAME=status TIMEZONE=statusZONEOFFSET=status DAYLIGHT=status.EYUDREP Init terminated.

Explanation: One of the parameters specified for theEYU9XDUT repository initialization program wasinvalid, where:





User response: Correct the parameters in error, asfollows:

SYSID=1- to 4-character CICS system ID of the CMAS.

CMASNAME=1- to 8-character name of the CMAS.



TIMEZONE=1-character time zone code, from B—Z.

ZONEOFFSET=2-character time zone offset in minutes, from00—59.

DAYLIGHT=Y or N, to indicate whether daylight savingtime is in effect.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0607E CMASNAME=xxxxxxx 1st positioninvalid. EYUDREP Init terminated.

Explanation: The first character of the CMASNAME=parameter as specified for EYU9XDUT was invalid. Thefirst character must be one of the following: A–Z a–z @$ or #.


User response: Correct the parameter, then resubmitthe job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0608E EYUDREP contains at least one(1)record. EYUDREP Init terminated.

Explanation: The data repository could not beinitialized because it already contains at least onerecord.


User response: Initialize EYUDREP with the IDCAMSutility, using ‘DELETE data set name,PURGE,ERASE'followed by the DEFINE CLUSTER parameters, thenresubmit the job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0609E EYUDREP Relative Key Position error.EYUDREP Init terminated.

Explanation: The EYUDREP relative key position wasinvalid.


User response: Initialize EYUDREP with the IDCAMSutility, using KEYS(64,0), then resubmit the job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0610E EYUDREP KEYLEN must be(nnnnnnnnn). EYUDREP Initterminated.

Explanation: The EYUDREP relative key length wasinvalid.


User response: Initialize EYUDREP with the IDCAMSutility, using KEYS(64,0), then resubmit the job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0611I Error is terminating execution

Explanation: An error is causing the data repositoryinitialization routine to terminate. One or moreEYUXDnnnn messages issued before this one describethe error.


User response: Follow the instructions associated withthe EYUXDnnnn messages issued to SYSOUT.

Module: EYU9XDUT


EYUXD0612E VSAM Error Processing EYUDREPReturn Code=code Feedback=charsMACRO=macro Mode=mode.

Explanation: This message describes a VSAM errorencountered during data repository processing.


User response: Refer to the VSAM documentation fora description of the specified error and follow theinstructions given there for correcting the problem.Once the problem has been corrected, resubmit the job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0613E SYSID= cannot be binary zeroes.EYUDREP Init terminated.

Explanation: The SYSID= parameter specified forEYU9XDUT was invalid; it contained binary zeroes.


User response: Correct the SYSID= parameter byspecifying the 1- to 4-character CICS system ID of theCMAS, then resubmit the job.

Module: EYU9XDUT



Destination: SYSOUT

EYUXD0614E Invalid KEYWORD SYSID=statusCMASNAME=status TIMEZONE=statusZONEOFFSET=status DAYLIGHT=status.EYUDREP Init terminated.

Explanation: One of the keywords specified for theEYU9XDUT repository initialization program wasinvalid, where status identifies the status of eachkeyword as:

ERR The keyword was in error or was notspecified.

OK The keyword was correctly specified.


User response: Correct the keywords in error, asfollows:

v SYSID=

v CMASNAME=

v TIMEZONE=

v ZONEOFFSET=

v DAYLIGHT=

Then resubmit the job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0615E Invalid KEYWORD WUINAME=statusWUIPLEX=status WUISYSID=statusWUIAPPLID=status EYUDREP Initterminated.

Explanation: One of the keywords specified for theEYU9XDUT repository initialization program wasinvalid, where status identifies the status of eachkeyword as:

ERR The keyword was in error or was notspecified.

OK The keyword was correctly specified.


User response: Correct the keywords in error, asfollows:

v WUINAME=

v WUIPLEX=

v WUISYSID=

v WUIAPPLID=


Module: EYU9XDUT

Destination: SYSOUT

EYUXD0616I Successful CPLEXDEFCICSplex=CICSplex MP=mp written toEYUDREP.

Explanation: The parameters are shown as they werespecified in the EYU9XDUT repository initializationprogram, where:

CICSplexIdentifies the CICSplex the maintenance pointCMAS is to manage.

mp Refers to the maintenance point CMAS thatmanages the CICSplex.

System action: The data repository (EYUDREP) isupdated.


Module: EYU9XDUT

Destination: SYSOUT

EYUXD0617I Successful CPLEXDEFCICSplex=CICSplex MP=mp SYSID=sysidwritten to EYUDREP.

Explanation: The parameters are shown as they werespecified in the EYU9XDUT repository initializationprogram, where:

CICSplexIdentifies the CICSplex the maintenance pointCMAS is to manage.

mp Refers to the maintenance point CMAS thatmanages the CICSplex.

sysid Is the CICS system ID of the maintenancepoint CMAS.

System action: The data repository (EYUDREP) isupdated.


Module: EYU9XDUT

Destination: SYSOUT

EYUXD0618E Invalid parm lengthWUINAME=status WUIPLEX=statusWUISYSID=status WUIAPPLID=statusEYUDREP Init terminated.

Explanation: The length of one of the parametersspecified for the EYU9XDUT repository initializationprogram was invalid, where:







User response: Correct the length of the parameters inerror, as follows:

WUINAME=1- to 8-character name of the WUI.

WUIPLEX=1- to 8-character name of the WUI CICSplex.

WUISYSID=1- to 4-character CICS system ID of the WUI.

WUIAPPLID=1- to 8-character APPLID of the WUI.


Module: EYU9XDUT

Destination: SYSOUT

EYUXD0619E Invalid parm data WUINAME=statusWUIPLEX=status WUISYSID=statusWUIAPPLID=status EYUDREP Initterminated.

Explanation: One of the parameters specified for theEYU9XDUT repository initialization program wasinvalid, where:





User response: Correct the parameters in error, asfollows:

WUINAME=1- to 8-character name of the WUI.

WUIPLEX=1- to 8-character name of the WUI CICSplex.

WUISYSID=1- to 4-character CICS system ID of the WUI.

WUIAPPLID=1- to 8-character APPLID of the WUI.


Module: EYU9XDUT

Destination: SYSOUT

EYUXD0620E WUINAME=xxxxxxx 1st positioninvalid. EYUDREP Init terminated.

Explanation: The first character of the WUINAME=parameter as specified for EYU9XDUT was invalid. Thefirst character must be one of the following: A–Z a–z @$ or #.



Module: EYU9XDUT

Destination: SYSOUT

EYUXD0621E WUIPLEX=xxxxxxx 1st positioninvalid. EYUDREP Init terminated.

Explanation: The first character of the WUIPLEX=parameter as specified for EYU9XDUT was invalid. Thefirst character must be one of the following: A–Z a–z @$ or #.



Module: EYU9XDUT

Destination: SYSOUT

EYUXD0622E WUIAPPLID=xxxxxxx 1st positioninvalid. EYUDREP Init terminated.

Explanation: The first character of the WUIAPPLID=parameter as specified for EYU9XDUT was invalid. Thefirst character must be one of the following: A–Z a–z @$ or #.



Module: EYU9XDUT

Destination: SYSOUT

EYUXD0624E WUISYSID= cannot be binary zeroes.EYUDREP Init terminated.

Explanation: The WUISYSID= parameter specified forEYU9XDUT was invalid; it contained binary zeroes.


User response: Correct the WUISYSID= parameter byspecifying the 1 to 4 character CICS system ID of theWUI, then resubmit the job.

Module: EYU9XDUT

Destination: SYSOUT



EYUXD0625E Parameters XXXX and XXXX must beset to different values. EYUDREP Initterminated.

Explanation: Two parameters as specified forEYU9XDUT were set to the same value. The valuesmust be different.


User response: Ensure different values are specifiedfor these parameters, then resubmit the job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0626E Invalid EYUXDPRM found.EYUDREP Init terminated.

Explanation: Invalid parameters were entered forEYUXDPRM. Valid parameters are WUINAME,WUIPLEX, WUISYSID, and WUIAPPLID.


User response: Enter valid parameters forEYUXDPRM, then resubmit the job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0627E EYUXDPRM could not be opened.EYUDREP Init terminated.

Explanation: The EYUXDPRM job stream could not beread.


User response: Ensure EYUXDPRM is specifiedcorrectly, then resubmit job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0628E EYUXDPRM DD Statement must bespecified

Explanation: The EYUXDPRM DD statement forEYU9XDUT parameters was missing or invalid.


User response: Make sure a valid EYUXDPRM DDstatement is included in the data repositoryinitialization JCL. It is required whenPARM=('TARGETVER=xxxx') is not specified as input.That is, the EYUXDPRM DD statement is requiredwhen you are initializing a data repository but notwhen you are migrating a data repository.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0700E Invalid TARGETVER= value, Fournumeric characters are required.

Explanation: The TARGETVER= parameter specifiedfor the EYU9XDUT repository initialization programwas invalid. The TARGETVER= value must be anumeric that represents a version of CICSPlex SM. Forexample, TARGETVER=0230 represents CICSPlex SMfor CICS Transaction Server for z/OS, Version 3 Release2.

System action: The data repository is not converted.

User response: Correct the TARGETVER= parameter,then resubmit the job.

Module: EYU9XDUT

Destination: SYSOUT

EYUXD0701E VSAM Error Processing EYUDREPReturn Code=code Feedback=charsMACRO=macro.

Explanation: This message describes a VSAM errorencountered during the data repository conversionprocess.

System action: The data repository conversion processterminates.

User response: Refer to the VSAM documentation fora description of the specified error and follow theinstructions given there for correcting the problem.Then resubmit this job.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0702I Repository successfully converted.

Explanation: The EYU9XDUT repository initializationprogram successfully converted the data repository tothe version of CICSPlex SM specified by theTARGETVER= parameter.



Module: EYU9XDU1

Destination: SYSOUT

EYUXD0703E Internal conversion error.

Explanation: The EYU9XDUT repository initializationprogram encountered a problem while attempting toconvert the data repository to a new version ofCICSPlex SM.

System action: The data repository conversion process



terminates with a 2048 abend. A system dump isproduced.

User response: Collect the dump output and contactyour IBM Support Center.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0704E DDNAME NEWREP key lengthincompatible with target version.

Explanation: While attempting to convert the datarepository, the EYU9XDUT utility determined that thetarget data repository specified in the NEWREP DDstatement has a key length that is incompatible withthe version of CICSPlex SM specified in the TARGETVERparameter.

System action: The EYU9XDUT utility terminates.

User response: Verify that the desired CICSPlex SMversion is specified in the TARGETVER parameter. If it is,verify that the correct data set is specified on theNEWREP DD statement and that the data set is definedwith the appropriate key length for the target version.Refer to the CICS Transaction Server for z/OS InstallationGuide manual for key length information.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0705E DDNAME EYUDREP record nnnnnlength incompatible with targetrepository.

Explanation: While attempting to convert the datarepository, the EYU9XDUT utility encountered a recordwhose length, after conversion, would exceed themaximum record length for the target data repository,where nnnnn is the number of the record.

System action: The specified record is not updated oradded to the target data repository. The EYU9XDUTutility continues processing.

User response: Ensure that the attributes of the targetdata repository are correct for version of CICSPlex SMspecified in the TARGETVER parameter. Refer to the CICSTransaction Server for z/OS Installation Guide manual forsample JCL containing the appropriate DEFINECLUSTER information.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0706W DDNAME NEWREP nnnnn recordswere bypassed.

Explanation: While attempting to convert the datarepository, the EYU9XDUT utility encountered somerecords that will not be written to the new target data

repository, where nnnnn is the number of the record(s)bypassed.

System action: The bypassed record(s) are not addedto the new target data repository. The EYU9XDUTutility continues processing with a return code of 4.The bypassed records are not correct for the version ofCICSPlex SM specified in the TARGETVER parameterand have been printed to the //BYPASS DD statement.

User response: This may not be a problem situation. Ifyou suspect an error has occurred collect yourEYUDREP and NEWREP data repositories, the job logoutput from the EYU9XDUT batch utility, and contactyour IBM support center.

Note: If you specify a TARGETVER that is less thanthe VERSION of your current EYUDREP, records maybe bypassed because they are not supported on thelower level of CICSPlex SM as specified by theTARGETVER parameter. In this case the message isnormal and can be expected. In other cases it is not andshould be investigated.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0707E BYPASS DD statement must bespecified. TARGETVER BYPASS DDstatement must be specified.TARGETVER init terminated.

Explanation: The BYPASS DD statement for theCMAS data repository was missing or invalid.


User response: Make sure a valid BYPASS DDstatement is included in the data repositoryinitialization JCL. It is required whenPARM=('TARGETVER=xxxx') is specified as input.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0708I CRESxxxx resource table nnnnn recordsnot converted.

Explanation: CRESxxxx is a CICSPlex SM topologymanager object that describes instances of a resourcewithin a CICS system. They will not be converted bythe EYU9XDUT batch utility. These object types will berecreated when a MAS joins to the CMAS. CRESxxxxresource descriptions can be found in the CICSPlexSystem Manager Resource Tables Reference Vol 1

System action: Data repository initialization continues.

User response: None

Module: EYU9XDU1

Destination: SYSOUT



EYUXD0709E The TARGETVER value (xxxx) isgreater than the CICSPlex SM version ofEYU9XDUT (yyyy)

Explanation: To ensure that the data repositoryconversion works properly, it is required that the valueprovided on the PARM=('TARGETVER=xxxx')statement cannot be greater than the version ofEYU9XDUT being loaded from the SEYUAUTH dataset.


User response: Ensure that your STEPLIB DDstatement is referencing the correct SEYUAUTH dataset.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0710E The CICSPlex SM version of theEYUDREP (xxxx) is greater than theCICSPlex SM version of EYU9XDUT(yyyy)

Explanation: To ensure that the data repositoryconversion works properly, it is required that theversion of the EYUDREP (data repository) cannot begreater than the version of EYU9XDUT being loadedfrom the SEYUAUTH data set.


User response: Ensure that your STEPLIB andEYUDREP DD statements are correct.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0711E TARGETVER value (xxxx) is not avalid CICSPlex SM version.

Explanation: An invalid value was entered on theTARGETVER=xxxx parameter. The value given is not avalid CICSPlex SM version.


User response: Ensure that yourPARM=(TARGETVER=xxxx) specifies a valid CICSPlexSM version.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0712E NEWREP contains at least one(1)record. Data Repository conversionterminated.

Explanation: The NEWREP DD statement references adata set that is not empty. This data set must be emptybefore the EYUDREP can be migrated to it.


User response: Ensure that your NEWREP DDstatement references an empty data set.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0714I DDNAME NEWREP Switched toDIRECT update after nnnnn recordswere written.

Explanation: During CICSPlex SM data repositoryconversion a record key was modified requiring aswitch from SEQUENTIAL to DIRECT updating of thenew data repository. This may result in an increase inthe time required to complete the repositoryconversion.



Module: EYU9XDU1

Destination: SYSOUT

EYUXD0716W The data repository may beincomplete for CICSplex (cicsplex).

Explanation: While this data repository was beingupgraded from an earlier release, it was found that oneor more resources for a CICSplex were droppedbecause the resource type did not exist at the earlierrelease, where:

cicsplex is the name of the affected CICSplex.

System action: The error is noted internally, andEYU9XDUT conversion continues. When conversion iscomplete, if no more serious errors were found, areturn code of 4 is issued.

User response: Restart this CMAS with the upgradeddata repository. Before any MAS connects to thisCMAS, it must connect to the maintenance pointCMAS. This results in this CMAS performingrepository synchronization with the maintenance pointCMAS. Because the utility has noted that this CMAS'srepository is incomplete for this CICSplex, themaintenance point CMAS delivers the required missingrecords to this CMAS as part of the repositorysynchronization process. If the delivery is successful,this CMAS issues message EYUXD0038I. If the deliveryis not successful, the CICSplex is removed and thenre-added to this CMAS's repository.

EYUXD0709E • EYUXD0716W


####

######

#

#

#

#

||||

|||||||||||||

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0717E The CPSM version of EYU9XDUT(xxxx) must match the version of theEYUDREP (yyyy) or the TARGETVER(zzzz)

Explanation: To ensure that the data repositoryconversion works properly, you must ensure that theversion of EYU9XDUT that is being loaded from theSEYUAUTH data set matches the version of the datarepository (EYUDREP) or the value provided on thePARM=(’TARGETVER=zzzz’) statement.

System action: Data repository conversion terminates.

User response: Ensure that your STEPLIB DDstatement is referencing the correct SEYUAUTH dataset.

Module: EYU9XDU1

Destination: SYSOUT

EYUXD0800I API initialization complete

Explanation: The application programming interface(API) subcomponent of the Data Repository componenthas been successfully initialized.



Module: EYU0XDJI

Destination: EYULOG

EYUXD0801E API initialization has failed. APIservices are unavailable.

Explanation: The application programming interface(API) subcomponent of the Data Repository componentcould not be initialized.

System action: API initialization terminates. CMASinitialization continues, but the API is not available. Auser trace record is written to the CICS trace data set.

User response: If you need API services, stop andrestart the CMAS and any local MASs that are attachedto it. If the problem persists, collect the exception tracerecords and the job log and contact your IBM SupportCenter.

Module: EYU0XDJI


EYUXD0802E API initialization is unable to startname task

Explanation: One of the long running tasks (LRTs)required by the API could not be initialized, where:

name Identifies the LRT that could not be initializedas one of the following:

v Notification

v Connection

v Disposition

v Service

System action: API initialization terminates. CMASinitialization continues, but the API is not available. Auser trace record is written to the CICS trace data set.


Module: EYU0XDJI


EYUXD0803E name task has failed. Task is beingrestarted.

Explanation: One of the long running tasks (LRTs)required by the API experienced a problem from whichit is attempting to recover, where:

name Identifies the LRT that is being restarted asone of the following:

v Notification

v Connection

v Disposition

v Service

System action: The CMAS attempts to restart the LRT.A user trace record is written to the CICS trace data set.

User response: If the problem persists, collect theexception trace records and the job log and contactyour IBM Support Center.

Module: EYU0XDNC, EYU0XDND, EYU0XDNE,EYU0XDNS


EYUXD0804E name task unable to recover fromfailure(s). Task being terminated.

Explanation: The specified API long running task(LRT) was attempting to recover from a failure.However, the LRT determined that the number ofrecovery attempts it had made exceeded the maximumallowed, where:

name Identifies the LRT that is being terminated asone of the following:

v Notification

v Connection

v Disposition

v Service



System action: The LRT and the API serviceenvironment are terminated. CMAS processingcontinues, but the API is not available for use. A usertrace record is written to the CICS trace data set.




EYUXD0805I API name task terminated

Explanation: The specified API long running task(LRT) has been terminated, where:

name Identifies the LRT that was terminated as oneof the following:

v Notification

v Connection

v Disposition

v Service

System action: Additional EYUXD0805I messages areissued as the remaining API LRTs are terminated.



Destination: EYULOG

EYUXD0806E API ESSS action has failed. ESSSResponse (code)

Explanation: A CMAS attempt to communicate withthe Environment Services System Services (ESSS)address space on behalf of the API failed, where:

action Identifies the CMAS action as eitherCONNECTION or DISCONNECTION.

code Is the hexadecimal return code.

System action: The API service environment isterminated. CMAS processing continues, but the API isnot available. A user trace record is written to the CICStrace data set.


Module: EYU0XDF1


EYUXD0807I date time applid API User(userid) has beensuccessfully {signed on | signed off} from{Jobname | MASname}.

Explanation: An application programming interface(API) user issued either an EXEC CPSM CONNECT orDISCONNECT command and the command completedsuccessfully, where:

userid Identifies the API user. This ID was eithersupplied by the user on a CONNECTcommand or determined by CICSPlex SMbased on the operating environment.

action Indicates that the user was either signed on orsigned off, depending on which EXEC CPSMcommand was issued.

System action: API processing continues.

User response: None. This message can be suppressedby setting the CMAS CICSPlex SM system parameterAPISIGNMSG(NO).

Module: EYU0XDF1, EYU0XDF2

Destination: EYULOG

EYUXD0808W date time applidAPI User (userid) hasfailed to {signoff | signon} from {Jobname| MASname}.

Explanation: An application programming interface(API) user issued either an EXEC CPSM CONNECT orDISCONNECT command, but the command failed,where:

userid Identifies the API user. This ID was eithersupplied by the user on a CONNECTcommand or determined by CICSPlex SMbased on the operating environment.

action Indicates that the user could not either sign onor sign off, depending on which EXEC CPSMcommand was issued.

System action: API processing continues. A user tracerecord is written to the CICS trace data set.

User response: Make sure the CONNECT orDISCONNECT command was correctly specified. If itwas and the problem persists, collect the exceptiontrace records and the job log and contact your IBMSupport Center.

Module: EYU0XDF1, EYU0XDF2


EYUXD0809W CPSM resources will remainoutstanding for API user(userid) due toresource release failures

Explanation: As part of its disconnection process, theAPI attempted to release resources that had beenallocated for its use. However, the attempt was not

EYUXD0805I • EYUXD0809W


completely successful, where:

userid Identifies the API user with which theresources were associated. This ID was eithersupplied by the user on a CONNECTcommand or determined by CICSPlex SMbased on the operating environment.

System action: The API user is signed off. However,some of the resources associated with that user's APIthread remain allocated. A user trace record is writtento the CICS trace data set.


Module: EYU0XDF2


EYUXD0810E CPSM API environment is damaged.API services are now unavailable

Explanation: A problem has caused the API serviceenvironment to become damaged.

System action: The API service environment isterminated. CMAS processing continues, but the API isnot available. A user trace record is written to the CICStrace data set.


Module: EYU0XDNE


EYUXD0811W CPSM API type resource shortagedetected

Explanation: The API has exhausted its supply ofcertain resources, where:

type Identifies the type of resource as one of thefollowing:

v Thread Index

v Thread Set

v List Link

v Command Free Queue

System action: The API request that prompted theshortage fails.


Module: EYU0XDNE


EYUXD0901E SYSPRINT must be specified

Explanation: The SYSPRINT DD statement for thebatched repository update utility was missing orinvalid.

System action: The batched repository update utilityterminates.

User response: Correct the JCL for the batchedrepository update utility to include a valid SYSPRINTDD statement and resubmit the job.

Module: EYU9XDBC


EYUXD0902E SYSPRINT could not be opened

Explanation: The SYSPRINT data set for the batchedrepository update utility could not be opened.


User response: Correct the JCL for the batchedrepository update utility to include a valid reference toa printer destination and resubmit the job.

Module: EYU9XDBC


EYUXD0903E SYSIN could not be opened

Explanation: The SYSIN data set for the batchedrepository update utility could not be opened.


User response: Correct the JCL for the batchedrepository update utility to include a valid SYSIN DDstatement and resubmit the job.

Module: EYU9XDBC


EYUXD0904E command command failed.Response=response Reason=reason

Explanation: This message provides additionalinformation on the cause of an error that occurredduring a run of the batched repository update utility.The CICSPlex SM API command command returned aresponse value of response and a reason value of reason.


User response: Refer to additional messages producedby the batched repository update utility. For anexplanation of the response and reason values of thecommand refer to the CICSPlex System ManagerApplication Programming Reference.

Module: EYU9XDBC




EYUXD0905E An attempt to connect to CMAScmasname failed

Explanation: The batched repository update utilityfailed to connect to CMAS cmasname. The CMAScmasname must be available for the batch repositoryupdate utility to connect and to submit batchedrepository updates.


User response: Ensure that CMAS cmasname isrunning so that it is available for the batch repositoryupdate utility to connect. Additional messagesproduced by the batched repository update utilityprovide further information.

Module: EYU9XDBC


EYUXD0906E An attempt to submit a batchedrepository update to run in CMAScmasname failed.

Explanation: The attempt to submit the batchedrepository update failed.


User response: Refer to additional messages producedby the batched repository update utility to determinewhy the attempt to submit a batch repository updatefailed.

Module: EYU9XDBC


EYUXD0907E Unable to interpret commandresponse and reason. Response=responseReason=reason

Explanation: The batched repository update utilityreceived a response value of response and a reasonvalue of reason which it was unable to interpret.

System action: The batched repository update utilityabnormally terminates.

User response: Examine the job log for messagesissued earlier which might indicate the reason for thefailure. Also examine the job log for the CMAS.Examine any dumps and traces which have beenproduced, including those produced by the CMAS. Ifno reason for the failure can be found, collect the joblog and trace for the CMAS, and the job log and dumpfor the batched repository update utility. Contact yourIBM support center.

Module: EYU9XDBC


EYUXD0908I A batched repository update has beensubmitted to run in CMAS cmasname

Explanation: The batched repository update utility hassubmitted a batched repository update to run in thespecified CMAS.

System action: A batched repository update runs inthe specified CMAS.

User response: Review the spooled output of thebatched repository update that runs in the specifiedCMAS as appropriate.

Module: EYU9XDBC


EYUXD0909I CICSPlex SM Batched RepositoryUpdate Utility is terminating

Explanation: The batched repository update utility isterminating.

System action: The job ends.


Module: EYU9XDBC


EYUXD0910E An attempt to obtain feedbackinformation failed.

Explanation: An attempt to obtain feedbackinformation failed for a previous CICSPlex SM APIcommand that also failed.


User response: Examine the job log for additionalmessages produced by the batched repository updateutility which might indicate the reason for the failure.Also examine the job log for the CMAS. Examine anydumps and traces which have been produced,including those produced by the CMAS. If no reasonfor the failure can be found, collect the job log andtrace for the CMAS, and the job log and dump for thebatched repository update utility. Contact your IBMSupport Center.

Module: EYU9XDBC


EYUXD0911E Feedback information did not containan error code

Explanation: The batch repository update utilityissued a CICSPlex SM API command that failed. Itthen attempted to obtain further information describingthe error by attempting to obtain error code feedback



information but no error code was available.


User response: See other messages issued by thebatchrep repository update utility.

Module: EYU9XDBC


EYUXD0912E Error code nn supplied in feedbackinformation not recognized

Explanation: Feedback information supplied errorcode nn which was not recognized.


User response: Examine the job log for messagesissued earlier which might indicate the reason for thefailure. Also examine the job log for the CMAS.Examine any dumps and traces which have beenproduced, including those produced by the CMAS. Ifno reason for the failure can be found, collect the joblog and trace for the CMAS, and the job log and dumpfor the batched repository update utility. Contact yourIBM Support Center.

Module: EYU9XDBC


EYUXD0913E Feedback information contained errorcode nn - feedback text

Explanation: An attempt by the batched repositoryupdate utility to submit a batched repository update inthe CMAS failed. The reason for the failure is describedby feedback text and is one of the following:

Duplicate request for this input data set and memberThe batched repository update job could notbe submitted because there was already abatched repository update in progress in theCMAS for the same input data set name andinput data set member.

Failure to obtain storage for jobThere was insufficient storage in the CMAS torun the batched repository update.

Failure during print processingThe batched repository update could not runbecause an error occurred during spooledprint output processing in the CMAS.

Security violation with input data setThe batched repository update job could notrun because the userid for the batchedrepository update utility was not authorizedfor access to the input data set.

Spool found to be not availableThe batched repository update job could notrun because spooled print output was notavailable in the CMAS.

Input data set not foundThe batched repository update could not runin the CMAS because the input data set wasnot be found.

Security violation with output data setThe batched repository update job could notrun because the userid for the batchedrepository update utility was not authorizedfor access to the output data set.


User response: Correct the cause of the error thatprevents the batched repository update from beingsubmitted and rerun the batched repository updateutility.

Module: EYU9XDBC


EYUXD0914E Invalid input parameter

Explanation: An invalid input parameter for thebatched repository update utility was detected.

System action: The batched repository update utilityterminates without submitting a batched repositoryupdate to run in a CMAS.

User response: Correct the input parameter and rerunthe batched repository update utility. Consult theCICSPlex System Manager Administration manual for adescription of the input parameters.

Module: EYU9XDBC


EYUXD0915E Required parameter parameter is notspecified

Explanation: The parameter input parameter for thebatched repository update utility is required but hasnot been specified.


User response: Supply the correct input parameterand rerun the batch repository update utility. Consultthe CICSPlex System Manager Administration manual fora description of the input parameters.

Module: EYU9XDBC




EYUXD0916E Run type is not specified

Explanation: A run type input parameter for thebatched repository update utility is required but hasnot been specified.


User response: Supply the correct input parameterand rerun the batch repository update utility. Consultthe CICSPlex System Manager Administration manual fora description of the input parameters.

Module: EYU9XDBC


EYUXD1000W date time applid The LIMIT parameterhas been set to (limit) which is outsidethe supported range of 1 to 9999999.

Explanation: The LIMIT parameter must specify anumber between 1 and 9999999 inclusive. A valueoutside this range or a non-numeric value has beensupplied.

System action: Processing terminates.

User response: Ensure the LIMIT parameter iscorrectly specified.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, restype


EYUXD1001E date time applid Parameter parameter ismandatory and is missing or blank.

Explanation: The mandatory CMAS parameter has notbeen found in the SYSIN data stream.


User response: Correct the SYSIN data stream toinclude a SET CMAS parameter specifying a validCMAS name.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, parameter


EYUXD1002E date time applid EYU9XDDA attemptedto retrieve data for OBJECT object fromCONTEXT context and this failed.

Explanation: EYU9XDDA is unable to retrieve data forOBJECT object from CONTEXT context .


User response: Check the @DLALOG or the CMASEYULOG for further messages.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, object, context


EYUXD1003I date time applid Processing complete.

Explanation: EYU9XDDA processing is complete.


User response: No further action required.

Module: EYU9XDDA

XMEOUT Parameters: date, time,applid


EYUXD1004I date time applid EYU9XDDA processing isdiscovering CICSplex (cicsplex).

Explanation: DLA processing is discovering CICSplexcicsplex

System action: None


Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, cicsplex


EYUXD1005I date time applid Establishing connectionto CONTEXT(context) SCOPE(scope).

Explanation: Connection to context context and scopescope is being established.



Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, context


EYUXD1006I date time applid Closing connection toCONTEXT(context).

Explanation: DLA processing has completed forcontext context The connection to context context isclosed.





Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, context


EYUXD1007W date time applid Resource type (restype)is not recognized and has been ignored.

Explanation: Resource type restype is not recognized.



Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, restype


EYUXD1008E date time applid Object type(objtype)within the current CONTEXT(context)and SCOPE (scope) could not beretrieved.

Explanation: EYU9XDDA could not retrieve objtyperesources from the current context context and scopescope.



Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, objtype, objname,context


EYUXD1009E date time applid Parameter (command) isnot valid input.

Explanation: The command command specified on theSYSIN card is not supported by EYU9XDDA.


User response: Correct the JCL card and resubmit.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, command


EYUXD1010E date time applid The CICS TransactionServer version (version) specified is notsupported by this release of theprogram.

Explanation: The version version specified is notsupported by this level of the program.


User response: Correct the SET VERSION parametercard and resubmit the JCL.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, version


EYUXD1011E date time applid SYSIN contains no data.

Explanation: No valid data was read from SYSIN.


User response: Provide valid data on SYSIN andresubmit the JCL.

Module: EYU9XDDA



EYUXD1012E date time applid An error occurred whileperforming action(action) on PDSmember (membername) The return code is(returncode).

Explanation: While performing action action againstPDS member membername a severe error occurred withreturn code returncode .

System action: The program terminates

User response: Check the SYSPRINT and JOBLOG forfurther messages relating to the PDS whichEYU9XDDA is attempting to access.

Module: EYU9XDDA

XMEOUT Parameters: date, time,applid, action,membername, returncode


EYUXD1013I date time applid PDS Member(membername) has been written.

Explanation: The data set member membername hasbeen written successfully.



Module: EYU9XDDA

XMEOUT Parameters: date, time, membername,returncode


EYUXD1007W • EYUXD1013I


EYUXD1014W date time applid FEEDBACK data is notavailable. RESPONSE(response)REASON(reason).

Explanation: An attempt to retrieve FEEDBACK datafailed with RESPONSE response and REASON reason


User response: Check the @DLALOG for furthermessages.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, response, reason


EYUXD1016 S date time applid Unable to connect toCMAS(cmasname) at version(version).

Explanation: The program was unable to connect toCMAS cmasname at version version and perform adiscovery.

System action: The program terminates.

User response: Review the following points in yourJCL.

v Ensure that the CMAS parameter specifies the correctCMAS name and the CMAS is currently executing.

v Ensure that the CMAS supports an API connection atCICS Transaction Server version.

v Ensure that the JCL has been executed on the samez/OS system that the CMAS is currently executingon.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, cmasname,version


EYUXD1017I date time applid API command(command)for object(object) returnedRESPONSE(response) REASON(reason).

Explanation: The API command command againstobject object gave a RESPONSE of response and aREASON of reason .


User response: See the CICS Information Center formore information about command command

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, command, object,response, reason


EYUXD1018I date time applid Datastream rejected.

Explanation: The SYSIN datastream contains incorrectdata.


User response: See previous messages for moreinformation and correct the JCL.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid


EYUXD1019 I date time applid PDSMember(membername) has been deleted.

Explanation: The PDS member membername has beendeleted from the PDS specified in the JCL.



Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, membername


EYUXD1021E date time applidThe CICSplex (cicsplex)was not defined to the current CMAS.

Explanation: The CICSplex cicsplex was not known tothe current CMAS.


User response: Ensure that the BOOK CICSPLEXvalue is correct within the context of the SET CMASparameter.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, cicsplex


EYUXD1022W date time applid Resource limit reachedfor RESOURCE(resource) in BOOK(book).

Explanation: The number of resources of type resourcein book book has reached the value of the LIMITparameter.

System action: No further resources of this type arediscovered and processing continues.


Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, book, resource

EYUXD1014W • EYUXD1022W



EYUXD1023I date time applid Discovering CICSRegion(region).

Explanation: Discovery of resources in CICSplexcicsplex has begun.


User response: None

Module: EYU9XDDA

XMEOUT Parameters: date, time,applid, region


EYUXD1024I date time applid Discovery of booktype(resource) suppressed by filter(filter).

Explanation: The specification of filter filter hasresulted in suppressing discovery of CICS region region


User response: None

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, booktype,resource, filter


EYUXD1025I date time applid Start of FEEDBACK datafor command(cmdtype).

Explanation: Detailed FEEDBACK informationfollows.


User response: See following messages for moreinformation.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, cmdtype


EYUXD1026II date time applid End of FEEDBACKdata.

Explanation: Detailed FEEDBACK information hascompleted.


User response: See previous messages for moreinformation.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid


EYUXD1028E date time applid Organization nameparameter ORGNAME has not been set.

Explanation: The mandatory organization nameparameter ORGNAME has not been found in theSYSIN datastream.

System action: Processing terminates

User response: Correct the SYSIN datastream toinclude a SET ORGNAME entry

Module: EYU9XDDA



EYUXD1029E date time applid Input booktype(booktype) is not valid.

Explanation: The BOOK parameter book is not valid.


User response: Correct the BOOK parameter andresubmit the JCL.

Module: EYU9XDDA

XMEOUT Parameters: date, time, applid, booktype


EYUXD1030E date time applid HOSTNAME parameteris mandatory and was not found.

Explanation: The mandatory parameter HOSTNAMEwas not specifeid in the SYSIN datastream.


User response: Correct the SYSIN datastream toinclude a SET HOSTNAME entry

Module: EYU9XDDA



EYUXD1031E date time applid Organization nameparameter ORGNAME(orgname) is notvalid.

Explanation: The value specified in the SETORGNAME entry is not valid.


User response: Correct the SYSIN datastream to have



a valid SET ORGNAME entry.

Module: EYU9XDDA

XMEOUT Parameters: date, time,applid, orgname



Chapter 41. EYUXEnnnn messages

EYUXE0001I CPSM subsystem (EYUX) initializationcomplete

Explanation: The CICSPlex SM address space (CMAS)startup program, EYU9XECS, has completedinitialization of the CICSPlex SM MVS subsystementry, which is called EYUX. The CICSPlex SMsubsystem entry is only created the first time a CMASis started after an IPL. Subsequent CMAS startupsverify the existence of the subsystem entry for therequired release of CICSPlex SM.



Module: EYU9XECS


EYUXE0002I CICSPlex SM Service Address Spaceactive

Explanation: This message confirms the existence ofthe Environment Services System Services (ESSS)address space. The first CICSPlex SM address space(CMAS) to start after an IPL creates the ESSS addressspace. All subsequent CMAS startups verify that theaddress space is active. If the address space exists butis not active, the CMAS currently being started mustrestart it.


User response: None

Module: EYU9XECS


EYUXE0003I End of Task entered for CICSPlex SMrelnum

Explanation: The CICSPlex SM subsystem end of taskroutine, EYU9XEET, was entered due to the abnormaltermination of a CICSPlex SM address space, where:

relnum Identifies the release of CICSPlex SM that wasaffected.

System action: CICSPlex SM releases all itsenvironment dependencies in the Environment ServicesSystem Services (ESSS) address space.

User response: Examine the exception trace records,and any messages issued before this one, to determinethe cause of the abnormal termination.

Module: EYU9XEET


EYUXE0004E CPSM subsystem (EYUX) not found

Explanation: The Environment Services SystemServices (ESSS) utility program, EYU9XEUT, wasinvoked, but no CICSPlex SM MVS subsystem couldbe found. EYUX is the name of the subsystem thatEYU9XEUT expected to find. At least one CICSPlex SMaddress space (CMAS) must be running for theCICSPlex SM subsystem to exist.

System action: The ESSS utility program terminates.

User response: Make sure there is a CMAS runningand then restart the ESSS utility program.

Module: EYU9XEUT


EYUXE0005E Invalid ESSS function request

Explanation: An invalid Environment Services SystemServices (ESSS) utility function was requested. Thevalid functions are:

v DUmp

v RELoad


User response: Check the SYSIN statement on theutility program JCL and specify a valid function.

Module: EYU9XEUT


EYUXE0006E Invalid CICSPlex SM version request

Explanation: An Environment Services SystemServices (ESSS) utility function was requested for aninvalid version of CICSPlex SM.


User response: Check the version specified on theESSS utility request and make sure it is a valid versionof CICSPlex SM running at your site.

Module: EYU9XEUT


EYUXE0007E Module is not requested version

Explanation: An Environment Services SystemServices (ESSS) RELOAD utility function wasrequested, but the new program in the UTILLIB dataset is not of the requested version.



User response: Update either the UTILLIB data set orthe utility request to specify the correct version.

Module: EYU9XEUT


EYUXE0008E Invalid ESSS function request options

Explanation: An Environment Services SystemServices (ESSS) utility request contained invalidoptions.


User response: Refer to the CICSPlex System ManagerProblem Determination manual for a list of valid ESSSutility request options.

Module: EYU9XEUT


EYUXE0009E Invalid ESSS request syntax

Explanation: The syntax of an Environment ServicesSystem Services (ESSS) utility request was invalid.


User response: Refer to the CICSPlex System ManagerProblem Determination manual for the correct syntax ofESSS utility requests.

Module: EYU9XEUT


EYUXE0010E CICSPlex SM version required

Explanation: The Environment Services SystemServices (ESSS) utility request that was made requires aspecific version of CICSPlex SM.


User response: Check the ESSS utility program JCLand add the VERSION keyword to the appropriateutility request. Refer to the CICSPlex System ManagerProblem Determination manual for the correct syntax ofESSS utility requests.

Module: EYU9XEUT


EYUXE0011E Program name is not APF authorized.

Explanation: The specified program should be in anAPF-authorized library, but is not, where:

name Identifies the program as one of the following:

EYU9XECSThe CICSPlex SM address space(CMAS) startup program

EYU9XEUTThe Environment Services SystemServices (ESSS) utility program

Be aware that the specified program may be inan APF-authorized library, but if that library isin a STEPLIB concatenation with otherlibraries that are not APF-authorized, itbecomes unauthorized.

System action: Depending on which program was notauthorized, either CMAS initialization or the ESSSutility terminates.

User response: Make sure the specified program, andall other libraries in the STEPLIB concatenation, areAPF-authorized. Then, restart the job.

Module: EYU9XECS, EYU9XEUT


EYUXE0012E dsname data set not opened

Explanation: One of the following data sets could notbe opened by the Environment Services SystemServices (ESSS) utility program:

v SYSIN DD

v UTILPRINT DD

v UTILLIB DD


User response: Determine the cause of the OPENerror and then restart the utility program.

Module: EYU9XEUT


EYUXE0013E BLDL error has occurred

Explanation: An error occurred while attempting toissue a BLDL for a module in the UTILLIB data set,while executing the EYU9XEUT utility or during CMASinitialization.

System action: The ESSS utility program or CMASinitialization terminates, depending on whichenvironment produced the error.

User response: Determine the cause of the BLDL errorand then restart the utility program or the CMAS,depending on which environment produced the error.

Module: EYU9XEUT, EYU9XECS


EYUXE0014E modname module not found

Explanation: The specified module could not belocated in the UTILLIB data set if executing utilityprogram EYU9XEUT, or the specified module could notbe located in the MVS linklist or LPALIB if this

EYUXE0008E • EYUXE0014E


message was issued during CMAS initialization.


User response: Place the module in the UTILLIB dataset and then restart the utility program if runningEYU9XEUT, or ensure that the module is in the MVSlinklist or LPALIB if the message was issued duringCMAS initialization.



EYUXE0015E modname module not executable

Explanation: The specified module is in anonexecutable format.


User response: Determine the reason for the modulebeing nonexecutable and then restart the utilityprogram, or restart the CMAS, depending on whichenvironment produced the error message.



EYUXE0016E type GETMAIN failure

Explanation: A GETMAIN for the specified type ofstorage has failed, where:

type Identifies the type of storage that could not beobtained as CSA, DSA, or ECSA.


User response: Increase the appropriate region sizeand then restart the utility program, or restart theCMAS, depending on which environment produced theerror.



EYUXE0017E Module modname cannot be loaded

Explanation: An attempt to load the specified modulehas failed.


User response: Determine the reason for the LOADfailure and then restart the utility program, or restartthe CMAS, depending on which environment producedthe error.



EYUXE0019E ESSS PC REPLACE request failed

Explanation: An attempt to update the CICSPlex SMprogram call routines in the ESSS service address spacehas failed.

System action: System continues to run using existingPC routines.

User response: Attempt to rerun the EYU9XEUTutility, if the problem persists contact IBM service.

Module: EYU9XEUT


EYUXE0020E ESSS IDENTIFY Failed Return code =X'code'

Explanation: The CICSPlex SM address space (CMAS)startup program, EYU9XECS, received a nonzero returncode while attempting to identify itself to theEnvironment Services System Services (ESSS) addressspace, where:



User response: Use the DUMP option of the ESSSutility program, EYU9XEUT, to obtain a report on thedata structures in the ESSS address space. Then, contactyour IBM Support Center.

Module: EYU9XECS


EYUXE0021E No EYURXESS available

Explanation: The CICSPlex SM ESSS service addressspace could not be found.

System action: EYU9XEUT utility terminates.

User response: Ensure that the VERSION keywordmatches a running CICSPlex SM service address space.

Module: EYU9XEUT


EYUXE0022E ESSS not active

Explanation: The Environment Services SystemServices (ESSS) utility JCL included a request for arelease of CICSPlex SM that is not currently active.


User response: Check the ESSS utility program JCLand specify a valid VERSION keyword. Then, restartthe utility program.



Module: EYU9XEUT


EYUXE0023E ESSS address space not created - reason

Explanation: The Environment Services SystemServices (ESSS) address space could not be created,where:

reason indicates one of the following errors:v Invalid return code from EYU9X420v EYUTXEPC cannot be loadedv Getmain for region storage failedv Getmain for common storage failedv ESSS control block build failedv EYUX420 address space abended

System action: A dump is taken of the ESSS addressspace. For the EYUX420 address space abended error,the title of the dump is EYU9X420.SYSTEM.FAILURE. Forall other errors the dump title isEYU9X420.CREATE.FAIL.DUMP. The creating CMAS issuesthis message and then terminates.

User response: Make sure the ESSS initializationroutine, EYUX420, resides in one of the followingplaces:

v An authorized library in LINKLIB

v The extended link pack area (ELPA)

Then, restart the CMAS startup program.

Determine the cause of the error from the messageinsert. Depending upon the message, you may be ableto correct the error:EYUTXEPC cannot be loaded

Ensure that EYUTXEPC is in a data setallocated to the SEYUAUTH file in the CMAS,then restart the CMAS.

Getmain for region storage failedEnsure that any IEFUSI exit in place allows theEYUX420 address space to allocate at least 32MB of storage above the 16 MB line, thenrestart the CMAS.

Getmain for common storage failed Ensure that at least 8 KB of contiguous ECSAstorage (SP241 above the 16 MB line) isavailable, then restart the CMAS.

If the error cannot be rectified as specified above, andfor all other messages, collect the dump, the CMAS joboutput, and the system log from the time of the error,and contact your IBM support center.

Module: EYU9XECS


EYUXE0024E ESSS release limit exceeded

Explanation: The maximum number of differentCICSPlex SM releases allowed in a system at one timehas been reached.

System action: The CICSPlex SM address space(CMAS) startup program, EYU9XECS is terminated.

User response: Remove at least one previous releaseof CICSPlex SM from your system. Then, restart theCMAS startup program.

Module: EYU9XECS


EYUXE0025E ESSS and PC Routines MismatchEncountered.

Explanation: During CMAS initialization, theEnvironment Services System Services (ESSS)IDENTIFY function determined that the generationdates of the ESSS address space code and the programcall (PC) routines it uses were not the same.

System action: A dump is taken of the ESSS addressspace. The title of the dump isEYU9X420.CREATE.FAIL.DUMP. The creating CMAS issuesthis message and then terminates.

User response: Verify the following:

v You have the latest versions of modules EYU9X420and EYUTXEPC.

v The library containing module EYU9X420 resides inthe linklist.

Issue the MVS command F LLA,REFRESH to refresh theLNKLST LOOKASIDE address space (LLA). Then tryto restart a CMAS. If this problem reoccurs, you mustreIPL the system.

Module: EYU9XECS


EYUXE0026I EYU9XECS Recovery Routine Entered

Explanation: The CICSPlex SM address space (CMAS)startup recovery routine has been entered due to anabnormal termination of the startup program,EYU9XECS.

System action: CICSPlex SM attempts to recover fromthe abend and obtain an SVC dump.

User response: Examine the SVC dump, if available,and any messages issued prior to this one, to determinethe cause of the abnormal termination.

Module: EYU9XECS


EYUXE0023E • EYUXE0026I


EYUXE0027W Lock recovery failed - reason

Explanation: CICSPlex SM uses its own logical lockscheme to serialize access to its shared resources.During CICSPlex SM address space (CMAS) ormanaged application system (MAS) termination, theMVS end-of-task routine provided by CICSPlex SMinvokes a lock recovery PC routine to:

v Release control of any held locks

v Remove the CMAS or MAS from any queues onwhich it is waiting for control of locks.

This lock recovery routine has failed for one of thefollowing reasons:

1. Insufficient storage for work area There wasinsufficient storage for a local work area requiredby the PC routine.

2. Parameter list not addressable The parameter listpassed as input to the PC routine was in storagethat could not be addressed.

3. Invalid parameter(s) One or more invalidparameters were found in the parameter list passedas input to the PC routine.

4. Abnormal termination An abnormal terminationwas intercepted by the PC routine.

System action: The impact on system processingdepends on the reason for the failure:

1. The PC routine is unable to fulfill any of itsresponsibilities. This may result in errors inassociated address spaces (that is, MASs associatedwith a CMAS or the CMAS associated with a MAS).It may also make it impossible to restart theterminating address space without first terminatingall associated address spaces.

2. Same as 1.

3. Same as 1.

4. The PC routine may have managed to partiallyfulfill its responsibilities before encountering theabnormal termination. Therefore, the result of theerror cannot be predicted. Before returning controlto the end-of-task exit, an attempt is made to obtainan SVC dump and a software error recordingrequest is made to the MVS LOGREC facility.

User response: The appropriate response depends onthe reason for the failure:

1. Terminate all address spaces associated with theterminating address space. Then, restart all theaddress spaces. If the problem persists, contact yourIBM Support Center.

2. Same as 1.

3. Same as 1.

4. Collect the following information and contact yourIBM Support Center:

v The SVC dump, if one was obtained

v The job log, and

v The record written to the SYS1.LOGREC data set

Module: EYU9XEET


EYUXE0028I End of Memory entered for CICSPlexSM relnum, JOB jobname Return code =X'code'

Explanation: The CICSPlex SM subsystem end ofmemory routine, EYU9XEEM, was entered due to anabnormal termination of a CICSPlex SM address space,where:


jobnameIs the name of the address space thatterminated.


System action: CICSPlex SM releases all itsenvironment dependencies in the Environment ServicesSystem Services (ESSS) address space.

User response: Examine the exception trace records,and any messages issued before this one, to determinethe cause of the abnormal termination.

Module: EYU9XEEM


EYUXE0029E ESSS connection termination failed:Return Code = X'code'

Explanation: The CICSPlex SM subsystem end of taskroutine, EYU9XEET, could not terminate the connectionbetween a CMAS or MAS and the EnvironmentServices System Services (ESSS) address space, where:


System action: End of task processing continues.However, some dependencies still exist between theCMAS or MAS and the ESSS address space.

User response: Use the DUMP option of the ESSSutility program, EYU9XEUT, to dump the datastructures in the ESSS address space. Collect the dumpoutput and contact your IBM Support Center.

Module: EYU9XEET


EYUXE0030E Insufficient storage for Subsystemfunction routing

Explanation: The CICSPlex SM subsystempreprocessor routine (EYU9XEER) attempted to create awork area for end of task or end of memoryprocessing, but there was not enough storage available.The routine requires approximately 100 bytes above the16Mb line.

EYUXE0027W • EYUXE0030E


System action: The subsystem preprocessor routineterminates. No CICSPlex SM-related end of task or endof memory processing occurs.

User response: Increase the appropriate region size.

Module: EYU9XEER


EYUXE0031E Function (funcname) not performed:MASs are active

Explanation: The TERMINATE or REPLACE requestcannot be processed because of active CICSPlex SMMASs.

System action: EYU9XEUT utility terminates.

User response: Ensure that the CICSPlex SM functionin MAS regions is shut down before rerunningEYU9XEUT.

Module: EYU9XEUT


EYUXE0032A CICSPlex SM relnum Service AddressSpace Dump termination requested.Reply Y when a Dump Data set isavailable.

Explanation: The program call (PC) routines detectedpossible corruption in the internal data structures of theEnvironment Services System Services (ESSS) addressspace, where:


System action: This message remains on the consoleuntil a reply is received.

Once a reply of Y is received, a system dump is takenand the ESSS address space terminates. Any CMAS orMAS that was connected to the ESSS address space alsoabends as a result of ESSS not being available.Additional messages related to CMAS or MAS abendsmay be issued to the console.

User response: Make sure a system dump data set isavailable and then issue a reply of Y to this message.Collect the dump output and contact your IBM SupportCenter.

Messages related to CMAS or MAS abends can beignored, as they are a result of the ESSS address spacetermination.

Module:


EYUXE0033E ESSS Shutdown detected: CMAS startupterminated

Explanation: During CMAS initialization,CICSPlex SM detected that the ESSS service addressspace is being shutdown.

System action: The CMAS startup is terminated andthe CICS job ends.

User response: Wait until ESSS shutdown completesand restart the CMAS

Module: EYU9XECS


EYUXE0034E Invalid Version Detected for module,found version, expected version

Explanation: This message is issued during CMASstartup while loading the specified module inpreparation for initializing or restarting the ESSSaddress space.

The CICSPlex SM version of the module does notmatch the version of EYU9XECS. The possible valuesfor module are:

EYU9XEEM (End Of Memory Exit) EYU9XEET (End OfTask Exit) EYUTXEPC (ESSS PC routines)

System action: CMAS startup fails, the ESSS addressspace is not created.

User response: Ensure that the named module at theproper version is in a load library which is first in theconcatenation of the following search order: 1.steplib/joblib 2. link list 3. LPA Restart the CMAS.

Module: EYU9XECS


EYUXE0035W Site security user exit program,EYU9XESV, not found

Explanation: The security exit program could not befound.

System action: The system continues and uses thedefault security validation processing.

User response: Ensure EYU9XESV is in a library inthe CMAS STEPLIB concatenation if you have written asecurity validation exit.

Module: EYU9XECS

Destination: Console, Joblog

EYUXE0036E Address Space Create program failed -R15=X'xxxxxxxx'

Explanation: When attempting to create the EYUX320address space the CMAS's LINK to the address spacecreate program ended with the specified non-zero



return code in general register 15.

System action: A dump is taken of the CMAS addressspace. The title of the dump isEYU9XECS.AS.CREATE.FAIL.DUMP. The CMAS then issuesthis message and terminates.

User response: Collect the dump, the CMAS joboutput, and the system log from the time of the error,and contact your IBM support center.

Module: EYU9XECS

Destination: Console, joblog


Chapter 42. EYUXLnnnn messages

EYUXL0001I addspace initialization program starting

Explanation: The startup program for a CICSPlex SMaddress space (CMAS) or managed application system(MAS) is being initialized.


User response: None

Module: EYU9XLCS


EYUXL0001I addspace PLTPI program starting

Explanation: The startup program for a CICSPlex SMaddress space (CMAS) or managed application system(MAS) is being initialized.


User response: None

Module: EYU9XLCS


EYUXL0003I jobname CPSM Version nnnn comptypestartup in progress

Explanation: A CICSPlex SM component is beginningits initialization process, where:

jobnameIs the job name of the initializing component

nnnn Is the version of CICSPlex SM under whichthe component is being initialized, forexample, 0420 for CICS Transaction Server forz/OS Version 4 Release 2.

comptypeIdentifies the component as one of thefollowing:

CMAS CICSPlex SM address space

LMAS Local managed application system

SMSS Single server region



Module: EYU1XLEV, EYU9XLEV


EYUXL0004I ESSS connection complete

Explanation: A connection between the Kernel

Linkage (KNL) component and the EnvironmentServices System Services (ESSS) has been successfullyestablished.


User response: None

Module: EYU9XLEV


EYUXL0005I Major Object created for component

Explanation: The specified component has had itsload module loaded and its public and privatedirectories created. All basic control blocks for acomponent have been acquired and formatted, where:

componentIdentifies the component as one of thefollowing:

v Kernel Linkage

v Trace Services

v Message Services

v External Services

v Common Services

v Cache Manager

v Data Repository

v Queue Manager

v Communications

v Topology

v Monitor Services

v real-time analysis

v Workload Manager

v MAS (Managed Application System)



Module: EYU1XLBE, EYU9XLBE


EYUXL0006I component initialization has started

Explanation: The Kernel Linkage component hasrequested initialization of the specified component.CICSPlex SM components are initialized in thefollowing order:

v Message Services

v Parameter Services

v Common Services

v Data Cache Manager (CMAS only)


v Queue Manager

v Data Repository (CMAS only)

v Communications

v Topology Services (CMAS only)

v Monitor Services (CMAS only)

v Workload Manager

v real-time analysis (CMAS only)

System action: Initialization of the named componentbegins. Additional messages are issued to record theprogress of the component initialization.


Module: EYU0XLBI, EYU3XLBI, EYU3XLBV,EYU9XLEV

Destination: EYULOG

EYUXL0007I comptype Phase nn initializationcomplete

Explanation: A CICSPlex SM component of thespecified type has completed one of its initializationphases, where:

comptypeIdentifies the component that is initializing asone of the following:



SMSS Single server version of the CICSmanagement client interface

nn Indicates which initialization phase has beensuccessfully completed. Depending on the typeof address space, between one and fourinitialization phases must be completed. Thismessage appears after completion of thefollowing phases:

Phase Description

II Initializes all Kernel Linkagesubcomponents and establishes aconnection to the EnvironmentServices System Services (ESSS).

III Initializes all CICSPlex SM BaseService components.

IV Registers all supported CICSplexeswith the ESSS address space, attachesan OS task to manage connections tothe CAS.



Module: EYU1XLEV, EYU9XLEV.


EYUXL0008I CICSplex registration complete

Explanation: All CICSplexes managed by the CMASthat is initializing have been registered withEnvironment Services System Services (ESSS). Thismessage is issued only when a CMAS is beinginitialized.



Module: EYU9XLEV


EYUXL0009I CAS connection established

Explanation: A connection between a CICSPlex SMaddress space (CMAS) and a coordinating addressspace (CAS) has been successfully created.

System action: All service points to the CAS areattached. The ISPF end-user interface, which isprovided by the CAS, is now available.

User response: None

Module: EYU9XLEC


EYUXL0010I applid CMAS initialization complete

Explanation: A CICSPlex SM address space (CMAS)has been successfully initialized.





EYUXL0011I comptype shutdown in progress

Explanation: A CICSPlex SM component of thespecified type is being shut down, where comptypeidentifies the component as one of the following:



SMSS Single server version of the CICS managementclient interface

System action: Shutdown of the specifiedCICSPlex SM component continues.

User response: None



EYUXL0007I • EYUXL0011I


EYUXL0012I ESSS disconnect complete

Explanation: The connection to the EnvironmentServices System Services (ESSS) address space that wasestablished during CICSPlex SM initialization has beenterminated. Disconnection from the ESSS occurs duringthe normal shutdown of a CICSPlex SM address space(CMAS) or local managed application system (MAS).

System action: CICSPlex SM shutdown continues.The ESSS address space is no longer available.


Module: EYU9XLEV


EYUXL0013I CICSplex registration terminated

Explanation: All CICSplexes previously registeredwith this CICSPlex SM address space (CMAS) in theEnvironment Services System Services (ESSS) areunregistered. No other address space can connect tothis CMAS.

System action: The CMAS continues to executeswithout any connections to other CICSPlex SM addressspaces.


Module: EYU0XLES

Destination: EYULOG

EYUXL0014I CAS connection terminated

Explanation: A connection between a CICSPlex SMaddress space (CMAS) and a coordinating addressspace (CAS) has been terminated.

System action: The ISPF end-user interface, which isprovided by the CAS, is no longer available. TheCMAS continues to execute.

User response: If this message occurs before thetermination of the CMAS, then this indicates that theCAS address space has terminated. If the ISPF end-userinterface is required, the CAS address space must berestarted.

Module: EYU0XLES, EYU9XLEV


EYUXL0015I component termination requested

Explanation: The Kernel Linkage component hasrequested termination of the specified component aspart of CICSPlex SM shutdown. CICSPlex SMcomponents are terminated in the following order:

v real-time analysis (CMAS only)

v Workload Manager

v Monitor Services (CMAS only)

v Topology Services (CMAS only)

v Communications

v Data Repository (CMAS only)

v Queue Manager

v Data Cache Manager (CMAS only)

v Common Services

v Parameter Services

v Message Services

System action: Termination of the named componentbegins.


Module: EYU0XLES, EYU3XLES

Destination: EYULOG

EYUXL0016I addspace shutdown complete

Explanation: A CICSPlex SM component of thespecified type has been successfully shut down, where:

addspaceIdentifies the type of address space as one ofthe following:




System action: The specified address space no longerexists. If it was a CMAS or local MAS, control isreturned to CICS.




EYUXL0017I CMAS Phase 0 initialization complete

Explanation: The startup program for a CICSPlex SMaddress space (CMAS) is complete.


User response: None

Module: EYU9XLCS


EYUXL0018I comptype restart in progress

Explanation: A CICSPlex SM component of thespecified type is attempting to restart itself after aCICSPlex SM address space (CMAS) shutdown orabend. All CICSPlex SM components have beenshutdown and control has been returned to the startupprocesses of those components, where:



comptypeIdentifies the component that is restarting as alocal MAS (LMAS).

System action: The MAS attempts to restart itself andwait for the terminated CMAS to initialize andestablish a connection to Environment Services SystemServices (ESSS).




EYUXL0019I comptype restart complete

Explanation: A CICSPlex SM component of thespecified type has been successfully restarted and hasreestablished its connection to the CICSPlex SMaddress space (CMAS), where:

comptypeIdentifies the component that was restarted asa local MAS (LMAS).



Module: EYU9XLEV

Destination: EYULOG

EYUXL0021I component initialization has started

Explanation: Initialization of the specified componenthas begun, where:

componentIdentifies the component as one of thefollowing:

v Trace Services

v Message Services

System action: This message is issued by the ExternalMessage processor because the Message Servicescomponent is not yet active. Initialization continues.


Module: EYU3XLBV, EYU9XLEV


EYUXL0022I addspace Phase I initialization complete

Explanation: An address space of the specified typehas completed the first of its initialization phases,which verifies CICSPlex SM requirements and sets upthe Major Object Base environment, where:

addspaceIdentifies the type of address space that isinitializing as one of the following:






Module: EYU9XLEV


EYUXL0023I Trace Services termination requested

Explanation: The Kernel Linkage component hasrequested termination of Trace Services as part ofCICSPlex SM shutdown.

System action: This message is issued by the externalmessage processor because the Message Servicescomponent is no longer active. Trace Servicestermination begins.


Module: EYU0XLES, EYU3XLES


EYUXL0024I Waiting for CICSPlex SM subsystemactivation

Explanation: Initialization of a local MAS wassuspended because the Environmental Services SystemServices (ESSS) subsystem is not yet active. ESSS isinitialized by the first CMAS to start up in the MVSimage. Message EYUXL0103E is issued before this one.

System action: Initialization is suspended. The CICSsystem remains active but is not known toCICSPlex SM. As long as the CICS system is active, theMAS checks at regular intervals to determine if theESSS subsystem is active. Once the ESSS subsystem isavailable, MAS initialization completes.

User response: Start the CMAS.

Module: EYU9XLBE


EYUXL0025I Waiting for ESSS for CICSPlex SMrelease

Explanation: Initialization of a local MAS wassuspended because the release descriptor block (RDB)is not yet available from the CICSPlex SM subsystem(CPSM). The RDB identifies the CICSPlex SM releasethat is running; it is built during initialization of thefirst CMAS. Message EYUXL0104E is issued before thisone.

System action: The CICS system continues to runnormally, but it is not known to CICSPlex SM. As longas the CICS system is active, the MAS tries at regularintervals to find the RDB. Once the RDB is available,MAS initialization completes.




Module: EYU9XLBE


EYUXL0026I Waiting for ESSS to become active forCICSPlex SM release

Explanation: Initialization of a local MAS wassuspended because no Environment Services SystemServices (ESSS) address space was found to be activefor the release of CICSPlex SM identified by the releasedescriptor block (RDB).

System action: MAS initialization is suspended untilan ESSS address space becomes active.

User response: Restart the ESSS address space bystarting a CMAS.

Module: EYU9XLBE


EYUXL0027I date time applid Automatic Restart requestfrom { API | EUI | RTA } for sysname inplexname issued by {event | userid}requestor.

Explanation: A request was issued to cancel andrestart the specified CICS system using the MVSautomatic restart manager (ARM), where:

compid Identifies the component that issued therequest as one of the following:

API Application programming interface.

RTA real-time analysis, which means theACTNDEF for a notification conditionspecified the restart.

sysnameIdentifies the CICS system that will becanceled and restarted.

plexnameIdentifies the CICSplex of which the CICSsystem is a member.

entity Identifies the entity that issued the request asone of the following:

event An RTA event.

userid An API user.

requestorIdentifies the RTA event or API user.

System action: The automatic restart request is passedto ARM. If the request is accepted and completessuccessfully, the CICS system is immediately canceledand automatically restarted.

If the request cannot be processed, MVS writesmessages to the console and writes a user trace recordto the CICS trace data set.

User response: Check the MVS console log todetermine if the restart request was successful.

Module: EYU0XLTA

Message inserts:

1. date

2. time

3. applid

4. compid, chosen from the following options:

v API

v EUI

v RTA

5. sysname

6. plexname

7. entity, chosen from the following options:

v event

v userid

8. requestor

Destination: Console, TDQ

EYUXL0029I ESDUMP value set to value throughprocess.

Explanation: During CMAS or MAS execution, thevalue for the ESDUMP EYUPARM has been updated,where:

value Identifies the value the ESDUMP was set to:

YES No SVC dumps are suppressed.

NO Duplicate SVC dumps taken byEYU9XLRV and EYU0XZPT may besuppressed, depending upon thevalue of the ESDUMPLIMITEYUPARM.

process Identifies how the ESDUMP value wasupdated:

COD0 The update was performed throughthe COD0 transaction SET command.

CMAS resource tableThe update was performed bychanging the CMAS resource tablethrough the API or WUI.



Module: EYU9DBG1, EYU0XLAU

Destination: EYULOG



EYUXL0030I ESSS connection in progress toCICSPLEX(plexname) forSYSID(cmasname).

Explanation: As part of initialization, the KernelLinkage (KNL) subcomponent is attempting to establisha connection between Environment Services SystemServices (ESSS) and the CICSplex and CMAS specifiedin the startup parameters of a MAS. This connectionprovides CICSPlex SM with access to certain requiredMVS program call routines.

System action: The attempt to establish a connectionto ESSS continues. This message is followed by one oftwo messages indicating the success or failure of theconnection attempt: EYUXL0004I indicates theconnection was successful, while EYUXL0105E indicatesit was not. If no further messages follow then a likelycause is that a CICS system definition does not exist forthis MAS.


Module: EYU9XLEV


EYUXL0031I ESSS connection in progress toCICSPLEX(plexname).

Explanation: As part of initialization, the KernelLinkage (KNL) subcomponent is attempting to establisha connection between Environment Services SystemServices (ESSS) and the CICSplex specified in thestartup parameters of a MAS, when no CMAS wasspecified. This connection provides CICSPlex SM withaccess to certain required MVS program call routines.

System action: The attempt to establish a connectionto ESSS continues. This message is followed by one oftwo messages indicating the success or failure of theconnection attempt: EYUXL0004I indicates theconnection was successful, while EYUXL0105E indicatesit was not.


Module: EYU9XLEV


EYUXL0032I ESSS connection in progress.

Explanation: As part of initialization, the KernelLinkage (KNL) subcomponent is attempting to establisha connection between Environment Services SystemServices (ESSS) and a CMAS . The CMAS beingconnected to can be identified by the APPLID in themessage prefix. This connection provides CICSPlex SMwith access to certain required MVS program callroutines.

System action: The attempt to establish a connectionto ESSS continues. This message is followed by one oftwo messages indicating the success or failure of the

connection attempt: EYUXL0004I indicates theconnection was successful, while EYUXL0105E indicatesit was not.


Module: EYU9XLEV


EYUXL0033I Attempting to PURGE TRANID(tranid),TASKID(taskid), METHOD(method),CALLER(cmethod).

Explanation: When attempting to terminate an activetask, the task did not respond to the post of itstermination ECB. A purge was issued, where:

tranid is the transaction name of the task.

taskid is the number of the CICS task the transactionis running under.

methodis the name of the CPSM method that is activeat the time of the purge request.

cmethodis the name of the CPSM method that calledthe active method.

System action: After issuing this message, a purge isissued for the specified task. Processing then continues.


Module: EYU0XLTP


EYUXL0075W CMAS recovery entered.

Explanation: The MVS recovery routine was entered.

System action: MVS diagnostic messages are writtento the CMAS job log.

CMAS processing continues, but the ISPF end user mayreceive unexpected results because of the failure.

User response: Review the job log for MVS orCMAS-related messages issued before this one. Collectany related messages and a dump of the CMASaddress space, and contact your IBM Support Center.

Module: EYU9XLCI


EYUXL0076W CMAS STCB corruption detected -STCB will be orphaned

Explanation: During processing of an ISPF end-userinterface request, the CMAS attempted to locate anavailable server task control block (STCB). The CMASfound an STCB, but it could not be validated; it mayhave been overwritten.

System action: The CMAS unchains the STCB at the

EYUXL0030I • EYUXL0076W


point of the validation failure. If another STCB cannotbe located and validated, a new one is allocated tosatisfy the end-user interface request.

User response: If this problem persists, obtain a dumpof the CMAS address space and contact your IBMSupport Center.

Module: EYU9XLCI


EYUXL0077W No SVC dumps will be taken becauseESDUMP has been set to NEVERthrough process.

Explanation: During CMAS or MAS execution, thevalue for the ESDUMP EYUPARM has been set toNEVER, where:

process Identifies how the ESDUMP value wasupdated:

EYUPARMThe update was performed throughthe ESDUMP EYUPARM.

COD0 The update was performed throughthe COD0 transaction SET command.

CMAS resource tableThe update was performed bychanging the CMAS resource tablethrough the API or WUI.

System action: Processing continues. All SVC dumpsthat would normally be issued by CICSPlex SM in thesystem will be suppressed.

User response: Suppression of SVC dumps may affectthe ability to debug problems. If a problem occurs withSVC dump suppression active, users may be requiredto reproduce the problem without SVC dumpsuppression active before debugging can be performedfor the problem. It is strongly recommended byCICSPlex SM service that ESDUMP is not set toNEVER.

Module: EYU0XLBV, EYU9DBG1, EYU0XLAU


EYUXL0078W The definition for {FILE|PROFILE|PROGRAM|TRANSACTION|TDQUEUE} resourcename has beenreplaced

Explanation: The PLTPI program for the CMAS hasreplaced an invalid definition for the CICSPlex SMresource resourcename. Previous message EYUXL0155Egives details of the invalid definition options.


User response: None

Module: EYU9XLCD


EYUXL0090W PLT Processing continuing whileMAS Agent waits to connect to ESSSSubsystem

Explanation: Processing of the CICS initialization PLTcontinues but the MAS agent will continue to wait forthe CICSplex to be registered with the ESSS subsystemby a starting CMAS.

System action: The CICS system continues to runnormally, but it is not known to CICSPlex SM. When aCMAS registers the CICSplex with the ESSS subsystem,MAS agent initialization will continue.

User response: Ensure that the CMAS to which theMAS will connect is started. If the functioning of theregion depends upon CICSPlex SM facilities (forexample, BAS resource installation or WLM routing) itmay be desirable to shut down the CICS region until aCMAS can be started.

Module: EYU0XLBV


EYUXL0100E No CICS CWA available

Explanation: The CICS common work area (CWA) isnot large enough to contain the CICSPlex SM KernelLinkage work area, EYURXLWA, which is required forCMAS initialization.


User response: The default CWA size is-512 bytes,which is not large enough for EYURXLWA. Make sureWRKAREA=2048 is included as one of the initializationparameters for the CMAS.

Module: EYU9XLCS


EYUXL0101E Not authorized for TRACE inquires

Explanation: The CICSPlex SM address space (CMAS)PLTPI program does not have the authorization to issuea required EXEC CICS INQUIRE TRACEDEST orTRACEFLAG command.

System action: The PLTPI program ends with an errorcondition, which forces the CMAS to terminate.

User response: Acquire the necessary authorizationand then restart the CMAS initialization job.

Module: EYU9XLCS


EYUXL0077W • EYUXL0101E


EYUXL0102E Unable to set type option

Explanation: The CICSPlex SM address space (CMAS)PLTPI program issued an EXEC CICS SET commandfor the specified trace option, but it received an errorcode, where:

type Identifies the option as either TRACEDEST orTRACEFLAG.


User response: Examine the CICS trace records todetermine what caused the EXEC CICS error. Then,restart the CMAS initialization job.

Module: EYU9XLCS


EYUXL0103E CICSPlex SM subsystem (EYUX) notactive

Explanation: The CICSPlex SM MVS/ESA subsystementry is not active.


CMAS CMAS initialization terminates.

Local MAS The MAS issues message EYUXL0024I andthen waits for a CMAS to initialize and restartthe ESSS address space.

User response: The appropriate response depends onwhat type of address space was being initialized:

CMAS Make sure the startup JCL is executingprogram EYU9XECS.

Local MAS None. MAS initialization continues once theESSS address space is available.

Module: EYU9XLEV


EYUXL0104E No ESSS for current CICSPlex SMrelease

Explanation: The ESSS address space does not containan entry for the release of CICSPlex SM that isattempting to initialize.


CMAS CMAS initialization terminates. CICSPlex SMtakes an SVC dump with a dump code ofEYUXL001.

Local MAS The MAS issues message EYUXL0025I andthen waits for a CMAS of the required versionto initialize and restart the ESSS address space.

User response: The appropriate response depends onwhat type of address space was being initialized:

CMAS Make sure the startup JCL is executingprogram EYU9XECS.

Local MAS None. MAS initialization continues once theESSS address space is available.

Module: EYU9XLEV


EYUXL0105E ESSS connection failed

Explanation: An attempt to establish a connectionbetween the Kernel Linkage component and theEnvironment Services System Services (ESSS) has failedduring initialization of an address space in theCICSPlex SM environment.




User response: The trace record indicates the reasonfor the ESSS connection failure. Depending upon whattype of address space was initializing when the failureoccurred, take one of the following actions:

CMAS Make sure the JCL specifies the proper PLTPIprogram to identify the CMAS to the ESSS.

MAS If the JCL specifies both a CICSplex and aCMAS, make sure the named CMAS is activeand participates in the management of theCICSplex.

If the JCL specifies only a CICSplex, make surethe CICSplex exists in at least one CMASattached to the ESSS.

Module: EYU9XLEV


EYUXL0102E • EYUXL0105E


EYUXL0106E Unable to acquire CICS storage

Explanation: An attempt to acquire main storage fromthe specified storage area has failed, where:

storage Identifies the storage area as one of thefollowing:

DSA Dynamic storage area (below the16MB line)

EDSA Extended dynamic storage area(above the 16MB line)

System action: The startup program for the addressspace that was being initialized ends.

User response: Determine the cause of the GETMAINfailure by examining the CICS trace records.

Module: EYU1ISTI, EYU1XLBE, EYU1XLEV,EYU1XLOP, EYU9XLBE, EYU9XLEV


EYUXL0107W Major Object create failed for compid

Explanation: An attempt to create the specifiedcomponent has failed, where:

compid Identifies the component as one of thefollowing:

KNL Kernel Linkage

TRC Trace Services

MSG Message Services

SRV Common Services

CHE Data Cache Manager

DAT Data Repository

QUE Queue Manager

COM Communications

TOP Topology Services

MON Monitor Services

RTA real-time analysis

WLM Workload Manager

MAS Managed Application System


User response: If the component that could not becreated is required by the initializing address space,make sure the load module for that component(EYU9xx0x) is in the proper load library.

If the module is in the correct load library and thecomponent still cannot be created, collect the exceptiontrace records and any messages issued before this oneand contact your IBM Support Center.

Module: EYU1XLBE, EYU9XLBE


EYUXL0108E date time applid CICSPlex registrationfailed.

Explanation: An attempt to register CICSplexes withEnvironment Services System Services (ESSS) has failedduring initialization of a CMAS .

System action: CMAS initialization terminates.CICSPlex SM takes an SVC dump with a dump code ofEYUXL001 and writes a user trace record to the CICStrace data set.

User response: Make sure the ESSS address space isactive. Examine the exception trace records todetermine the cause of the problem.

Module: EYU9XLEV

Message inserts:

1. date

2. time

3. applid


EYUXL0109E CAS connection failed

Explanation: An attempt to establish a connectionbetween a CICSPlex SM address space (CMAS) and acoordinating address space (CAS) has failed.

System action: The EYU9XLEC subtask attached tohandle CAS interfacing is ended. Because nocommunication exists between the CMAS and the CAS,the ISPF end-user interface, which is provided by theCAS, is not available. The CMAS continues to execute.

User response: Examine the user trace records, andany messages issued prior to this one, to determine thecause of the problem. If the cause cannot bedetermined, contact your IBM Support Center.

Module: EYU9XLEC


EYUXL0110E Load failed for module modname

Explanation: An attempt to load the specified modulehas failed.

System action: Processing continues, if possible.

User response: Examine the user trace records todetermine the reason for the load failure.

Module: EYU1ISTI, EYU1XLBE, EYU9XLEV


Console, job log



EYUXL0111E ESSS disconnect failed, RESP=response

Explanation: During orderly shutdown of aCICSPlex SM component, an attempt to disconnectfrom the Environment Services System Services (ESSS)address space failed.response is the ESSS response codefrom the disconnect routine.

System action: CICSPlex SM shutdown continues.

User response: Examine the user trace records todetermine the cause of the disconnection failure. Youmay need further assistance from IBM to solve thisproblem. If so, you will need to report the value ofresponse from the message.

Module: EYU9XLEV


EYUXL0112E addspace initialization failed

Explanation: An address space of the specified typecould not be initialized, where:

addspaceIdentifies the type of address space as one ofthe following:


MAS Local managed application system


System action: The impact on system processingdepends on the type of address space that was beinginitialized:

CMAS The CMAS is terminated. CICSPlex SMproduces an SVC dump with a dump code ofEYUXL001.

MAS The MAS is terminated. CICSPlex SMproduces a transaction dump with a dumpcode of EYUI and returns control to CICS.

SMSS The SMSS is terminated. CICSPlex SMproduces a transaction dump with a dumpcode of EYUI and returns control to CICS.

User response: Examine the user trace records, andany messages issued before this one, to determine thecause of the problem.



EYUXL0113E Termination of CICSPlex registrationfailed

Explanation: An attempt to unregister CICSplexespreviously registered with Environment ServicesSystem Services (ESSS) has failed during CMASshutdown.

System action: CMAS shutdown continues. A usertrace record is written to the CICS trace data set.


Module: EYU0XLES


EYUXL0114E CAS termination failed

Explanation: An attempt to terminate the connectionbetween a CMAS and a CAS has failed during CMASshutdown. The termination may have failed for one oftwo reasons:

1. The CAS abended or terminated prematurely

2. ECBs provided by the CAS during connection arenot valid

System action: CMAS shutdown continues. A usertrace record is written to the CICS trace data set. OnceCMAS shutdown is complete, all connections to theCAS are broken.

User response: If this error persists, examine theexception trace records and any related messages todetermine the cause of the problem.

Module: EYU0XLES


EYUXL0115E CMAS initialization transaction notfound

Explanation: An EXEC CICS START TRANIDcommand was issued for the transaction XLEV, by theCMAS PLTPI program EYU9XLCS, but the transactionXLEV could not be found.


User response: Make sure transaction XLEV is definedin the CSD and that the CMAS PLTPI programEYU9XLCS is being run during PLTPI stage 2processing (that is EYU9XLCS should appear after theDFHDELIM statement in the CMAS PLTPI).

Module: EYU9XLCS


EYUXL0116E addspace initialization program abended

Explanation: The startup program for a CICSPlex SMaddress space (CMAS) terminated abnormally.

System action: Initialization terminates. CICSPlex SMtakes a CICS system dump.

User response: Collect the dump, and any messagesissued before this one and contact your IBM SupportCenter.

Module: EYU9XLCS




EYUXL0117E addspace initialization program -reasontext

Explanation: The startup program for a CICSPlex SMaddress space (CMAS) terminated.

reasontext identifies the reason for the prematuretermination as follows:

CICS errorInitialization terminated because of a CICSerror

Already startedBoth CPSMCONN=CMAS andinitialization=CM were encountered in thesystem initialization parameters in effect.

System action: The currently executing initializationprogram terminates.

User response: This depends on the reason for thetermination:

CICS errorExamine the messages issued before this oneto determine the cause of the CICS error.Correct the problem and restart the job.

Already startedThe CMAS was started by another instance ofthe program EYU9XLCS. Ensure that only oneof CPSMCONN or initialization is coded inthe system initialization parameters.

Module: EYU9XLCS


EYUXL0118E PERFORM SHUTDOWN failed:RESP=respcode RESP2=resp2code

Explanation: A PERFORM SHUTDOWN commandwas issued during CMAS shutdown, and it returned anabnormal response, where:

respcode Is the value returned by CICS.

resp2codeIs the value returned by CICS.


User response: Follow the instructions associated withthe respcode and resp2code values for CEMT PERFORMSHUTDOWN or EXEC CICS PERFORM SHUTDOWN.For descriptions of the respcode and resp2code valuesassociated with these commands, refer to the CICSSystem Programming Reference.

Module: EYU9XLEV


EYUXL0119I Major Object loaded from module

Explanation: A system management object has beenloaded from load module module .


User response: None

Module: EYU9XLBE


EYUXL0122E No XLWA found

Explanation: The parameters passed to the KernelLinkage startup program by the PLTPI program did notcontain the EYURXLWA control block.



MAS The MAS is terminated. CICSPlex SM takes atransaction dump with a dump code of EYUIand returns control to CICS. CICSPlex SMtakes a transaction dump with a dump code ofEYUI.

User response: Make sure the startup JCL is invokingthe proper PLTPI program.



EYUXL0123E name is not a supported CICSPlex SMenvironment

Explanation: The parameters passed to the KernelLinkage startup program by the PLTPI programcontained an invalid four-character address spacename.




CICSPlex SM initialization is halted with a userABEND 1000.




Module: EYU9XLEV


EYUXL0124E Parameter block not passed from PLTPIprogram

Explanation: The Kernel Linkage startup programcould not obtain the parameter block passed by thePLTPI program.







EYUXL0125E Not authorized to INQUIRE SYSTEM

Explanation: The Kernel Linkage startup program isnot authorized to issued the EXEC CICS INQUIRESYSTEM command.




User response: Obtain the required authority andrestart the job.

Module: EYU9XLEV


EYUXL0126E An status CMAS has the same name asthis CMAS.

Explanation: During Environment Services SystemServices (ESSS) connect processing, the ESSS addressspace determined that a CMAS with the same name orSYSID as the connecting CMAS was either active or, ifinactive, had API applications or local MAS systemsconnected to it and is therefore encumbered, where:

status Is either active or encumbered

name Is either the CMAS name or SYSID

This message precedes message EYUXL0105E (ESSSconnection failed).

System action: CMAS initialization fails

User response: Make sure that no two CMASs havethe same name and/or SYSID if run on the same MVSimage for the same release of CICSPlex SM.

Module: EYU0XLBV

Destination: Console, Job Log, EYULOG

EYUXL0127E addspace restart attempt failed

Explanation: An attempt to restart a CICSPlex SMcomponent after a CMAS shutdown or abend was notsuccessful, where addspace identifies the type of addressspace that was attempting to restart as a local MAS(LMAS). A MAS connection to the CMAS cannot beestablished if, after the CMAS becomes active, it nolonger manages the CICSplex to which the MAS needsto connect.

System action: MAS initialization terminates. TheCICS system continues to execute normally, but it is notknown to CICSPlex SM.

User response: Make sure the MAS JCL specifies thecorrect CICSplex and, if appropriate, CMAS.

Module: EYU9XLEV


EYUXL0132I Notification Services Long RunningTask has started.

Explanation: The Notification Services subcomponentof Kernel Linkage was either initialized as part ofCICSPlex SM initialization or was restarted after anabnormal termination.



Module: EYU0XLNX


EYUXL0133I Notification Services Long RunningTask terminated type.

Explanation: The Notification Services subcomponentof Kernel Linkage has been terminated, where typeindicates the type of termination that occurred:

NormallyNotification Services was terminated as part ofCICSPlex SM termination.

EYUXL0124E • EYUXL0133I


AbnormallyNotification Services terminated abnormallyand will be restarted.

System action: If Notification Services terminatednormally, CICSPlex SM termination continues. IfNotification Services terminated abnormally, a usertrace record is written to the CICS trace data set and itrestarts itself. Message EYUXL0132I is issued whenNotification Services has been restarted.

User response: If Notification Services terminatednormally, no action is required. If it terminatedabnormally, examine the trace records to determine thecause of the problem.

If Notification Services terminates abnormally andrestarts itself repeatedly (as indicated by this messageand message EYUXL0132I being issued recursively),then shut down the CMAS. If Notification Servicesterminates abnormally and restarts itself ten times, theCMAS shuts down automatically. Collect the tracerecords and the job log and contact your IBM SupportCenter.

Module: EYU0XLNX


EYUXL0134E ESSS for current CICSPlex SM release isnot active

Explanation: During CMAS or local MASinitialization, no Environment Services System Services(ESSS) address space was found to be active for therelease of CICSPlex SM identified by the releasedescriptor block (RDB). The CICSPlex SM subsystem(CPSM) and the RDB were found, but the ESSS addressspace itself had been terminated.

System action: In the case of a CMAS, initializationterminates.

In the case of a local MAS, initialization is suspendedand message EYUXL0026I is issued.

User response: Restart the ESSS address space bystarting a CMAS.

Module: EYU9XLBE


EYUXL0135A CPSM subsystem (EYUX) or versionESSS still not available. Reply 'C' toterminate wait processing.

Explanation: During local MAS initialization, moduleEYU9XLBE has determined that either the CPSMsubsystem EYUX or the ESSS address space is notavailable, where version identifies the ESSS CPSMrelease.

System action: The message remains on the consoleuntil a reply is received or the EYUX subsystem and/orESSS become available.

If the proper reply is made, local MAS initialization isterminated with message EYUXL0136E, and CICSinitialization continues without the CPSM MAS agentpresent.

User response: Start a CMAS of the appropriaterelease to create the EYUX subsystem and ESSS. WhenEYU9XLBE detects that the proper environment hasbeen reached, it cancels the message from the console.

If the appropriate CMAS cannot be started, reply 'C' toterminate local MAS initialization and continue withCICS initialization in the region. If a CMAS is started ata later time, the COLM transaction can be used toinitialize the CPSM MAS agent in the region.

Module: EYU9XLBE


EYUXL0136E LMAS initialization is terminating dueto operator reply to EYUXL0135A

Explanation: The operator has replied 'C' to messageEYUXL0135A.

System action: Local MAS initialization is terminated,and CICS initialization continues without the CPSMMAS agent present.

User response: After a CMAS has been started thatthe MAS can connect to, issue the COLM transaction toinitialize the CPSM MAS agent in the region.

Module: EYU9XLBE


EYUXL0137E LMAS initialization is terminating dueto failure attempting to issueEYUXL0135A

Explanation: An error has occured attempting to issuemessage EYUXL0135A.

System action: Local MAS initialization is terminated,and CICS initialization continues without the CPSMMAS agent present.

User response: After a CMAS has been started thatthe MAS can connect to, issue the COLM transaction toinitialize the CPSM MAS agent in the region.

Module: EYU9XLBE


EYUXL0138I EYU9XLOP waiting for workload

Explanation: This message occurs in a region that hasspecified EYU9XLOP as the distributed or dynamicrouting exit, when that region is not connected to aworkload.

System action: If EYU9XLOP was specified, and thereis no workload associated with the region, then anyrequest to CICS that drives the appropriate routing exit

EYUXL0134E • EYUXL0138I


causes CICS to invoke EYU9XLOP, which then goesinto a wait state. Requests that may drive one of therouting exits include, for example, dynamic andundefined transactions, EXEC CICS START commands,CICS BTS activities, and dynamic program linkrequests.

User response: Ensure that you only specifyEYU9XLOP when you have a workload associated withthe region, by using one of the following procedures:

1. Change the specified routing module

2. Associate the region with a workload, then activateWLM in the region in one of the following ways:

a. Recycle the region

b. Stop and restart the MAS agent code in theregion. For example, use the COSH transactionto stop the MAS agent code and the COLMtransaction to restart the MAS agent code.

Module: EYU9XLOP


EYUXL0140E Automatic Restart request not issued forCMAS jobname (cmas), reason: reason.CMAS terminating without restart.

Explanation: An attempt to perform an automaticrestart of the named CMAS failed for the reason given,where:

cmas is the job name of the failing CMAS.

reason is the reason why an ARM Restart of theCMAS could not be attempted.

System action: The CMAS is terminated.

User response: Perform the recommended actions forany messages which preceded this message and restartthe CMAS.

Module: EYU0XLES


EYUXL0141E (tranname transaction definition missingor incorrect

Explanation: During CMAS or MAS initialization theCICS transaction definition for tranname is not found ordoes not specify the correct program name.

System action: Initialization continues, butunpredictable results may occur due to the missing orincorrect transaction definition.

User response: Ensure that the CSD used by theCMAS or MAS is correct and the appropriate CICSPlexSM definitions have been installed.

Module: EYU9XLBE


EYUXL0142E CICS Transaction Server CMAS releasecmasrelease is different from CICS releasecicsrelease. CMAS initialization isterminated.

Explanation: CMAS initialization has failed becausethe CMAS and CICS release levels do not match. ACMAS can run only with a CICS Transaction Server atthe same release level.

System action: Initialization terminates.

User response: Ensure that the CICS TransactionServer CMAS release cmasrelease matches the CICSrelease cicsrelease.

Module: EYU9XLCS


EYUXL0148E ENABLE PROGRAM cccccccc failed,EIBRCODE=xxxxxxxxxxxx

Explanation: An error occurred during CMASinitialization while attempting to enable a CICSPlex SMrelated CICS exit (EXEC CICS ENABLE PROGRAM),where:

ccccccccIs the name of the exit


System action: An EYUS transaction dump will betaken and the CMAS initialization will fail.

User response: Verify that the exit program is definedand installed in the CMAS, that it resides in a DFHRPLlibrary being used by the CMAS, and then restart theCMAS. If the error continues after the above is verified,collect as much of the following as possible and contactyour IBM Support Center:


v The EYUS transaction dump


Module: EYU9XLCS


EYUXL0149E EXTRACT EXIT cccccccc failed,EIBRCODE=xxxxxxxxxxxx

Explanation: An error occurred during CMASinitialization while attempting to extract the global areaaddress for a CICSPlex SM related CICS exit (EXECCICS EXTRACT EXIT), where:



System action: An EYUS transaction dump will be



taken and the CMAS initialization will fail.





Module: EYU9XLCS


EYUXL0150E START EXIT cccccccc failed,EIBRCODE=xxxxxxxxxxxx

Explanation: An error occurred during CMASinitialization while attempting to start processing for aCICSPlex SM related CICS exit (EXEC CICS ENABLEPROGRAM START), where:








Module: EYU9XLCS


EYUXL0151E INQUIRE PROGRAM cccccccc failed,EIBRCODE=xxxxxxxxxxxx

Explanation: An error occurred during CMASinitialization while attempting to inquire on the entrypoint address for a CICSPlex SM related CICS exit(EXEC CICS INQUIRE PROGRAM), where:




User response: Verify that the exit program is defined

and installed in the CMAS, that it resides in a DFHRPLlibrary being used by the CMAS, and then restart theCMAS. If the error continues after the above is verified,collect as much of the following as possible and contactyour IBM Support Center:




Module: EYU9XLCS


EYUXL0154E CREATE {FILE|PROFILE|PROGRAM|TRANSACTION|TDQUEUE} resourcename failed:RESP=respcode, RESP2=resp2code

Explanation: The CICSPlex SM address space (CMAS)PLTPI program issued an EXEC CICS CREATEcommand to create the resource resourcename forCICSPlex SM. The CREATE command returned anabnormal response, with the values shown in respcodeand resp2code.


User response: Examine the CICS trace records todetermine what caused the EXEC CICS error. Thenrestart the CMAS initialization job.

Module: EYU9XLCD


EYUXL0155E {FILE|PROFILE|PROGRAM|TRANSACTION|TDQUEUE} resourcename has invalidvalue: xxxxxxxx for option: yyyyyyyyy

Explanation: The PLTPI program for a CMAS detectedan invalid definition option for the CICSPlex SMresource resourcename

System action: CICSPlex SM will try to replace thedefinition with the default definition for the resource. Ifthis is successful, it will issue message EYUXL0078W. Ifthe replacement fails it will issue message EYUXL0156Eand will terminate CICS.

User response: None

Module: EYU9XLCD


EYUXL0156E The {FILE|PROFILE|PROGRAM|TRANSACTION|TDQUEUE} definition for resourcenameis invalid. CICS is terminating

Explanation: The PLTPI program for the CMAS wasunable to replace an invalid definition for the CICSPlexSM resource resourcename. Previous message



EYUXL0155E gives details of the invalid definitionoptions.

System action: CICS is terminated.

User response: Review the definition within the grouplist you use when starting the CMAS and change theinvalid options before restarting CICS. The defaultoptions are shown in the sample EYUúCDEF.

Module: EYU9XLCD


EYUXL0157E QUERY SECURITY for TRANSATTACHresourcename failed: RESP=respcode,RESP2=resp2code.

Explanation: The CMAS initialization program issuedan EXEC CICS QUERY SECURITY command to verifythat transaction resourcename is defined correctly to theexternal security manager. The command returned anabnormal response, with the values shown in respcodeand resp2code.

System action: CMAS initialization will continue untilall transaction IDs have been processed, then theCMAS agent will issue message EYUXL0159E andterminate.

User response: Follow the instructions associated withthe respcode and resp2code values for EXEC CICSQUERY SECURITY.

Module: EYU9XLCD


EYUXL0158E QUERY SECURITY for TRANSATTACHresourcename is incorrect:READ=NOTREADABLE.

Explanation: The CMAS initialization program issuedan EXEC CICS QUERY SECURITY command to verifythat transaction resourcename is defined correctly to theexternal security manager. The userid under which theCMAS initialization program executes (the regionuserid) does not have permission to START transactionresourcename.

System action: CMAS initialization will continue untilall transaction IDs have been processed, then theCMAS will issue message EYUXL0159E and terminate.

User response: Correct the resource profile andpermissions for transaction resourcename and restartCMAS initialization using the COLM transaction.

Module: EYU9XLCD


EYUXL0159E Incorrect security profile for one ormore resources. CICS is terminating.

Explanation: The CMAS initialization program issuedEXEC CICS QUERY SECURITY commands to verifythat each internal CPSM transaction is defined correctlyto the external security manager. One or more of thecommands returned an abnormal response, or one ormore transactions had incorrect security profiles.

System action: The CMAS region will terminate.

User response: Correct the problems identified bymessages EYUXL0157E and EYUXL0158E and resubmitthe CMAS job.

Module: EYU9XLCD


EYUXL0200S Invalid Parameter Table initializationfailed

Explanation: During CMAS or MAS initialization, theinternal parameter table could not be initialized.

System action: Parameter initialization for the CMASor MAS terminates. A user trace record is written to theCICS trace data set.


Module: EYU0XLPI


EYUXL0201E EYUPARM Data Set Cannot BeAccessed

Explanation: During CMAS or MAS initialization, theEYUPARM data set could not be accessed for one ofthe following reasons:

v The DD statement for EYUPARM is missing from thestartup JCL.

v The extrapartition transient data queue COPR is notdefined to CICS or does not reference the EYUPARMdata set.

System action: Parameter initialization for the CMASor MAS terminates.

User response: Make sure the DD statement forEYUPARM is properly specified in the CMAS or MASstartup JCL. Check that the resource definition forCOPR is present and references the EYUPARM data set.

Module: EYU0XLPI, EYU1XLPI




||||

||||||

||||

|||

|

|

||||

|||||||

|||

|||

|

|

|||

||||||

|

|||

|

|

EYUXL0202E EYUPARM Data Set Invalid LRECL

Explanation: During CMAS or MAS initialization, thelogical record length of the EYUPARM data set wasfound to be invalid. The data set must have a recordlength of 80.


User response: Make sure the EYUPARM data set andits DD statement specify a logical record length of 80.

Module: EYU0XLPI


EYUXL0203E EYUPARM Data Set Invalid RECFORM

Explanation: During CMAS or MAS initialization, therecord format of the EYUPARM data set was found tobe invalid. The data set must have a record format offixed (F) or fixed block (FB).


User response: Make sure the EYUPARM data set andits DD statement specify a record format of F or FB.

Module: EYU0XLPI


EYUXL0204E EYUPARM Data Set Invalid I/O Type

Explanation: During CMAS or MAS initialization, thedisposition of the EYUPARM data set was found to beinvalid. EYUPARM must be an input data set.


User response: Make sure the DD statement forEYUPARM is properly specified in the CMAS or MASstartup JCL.

Module: EYU0XLPI


EYUXL0205D Parameter Errors have Occurred.Reply 'GO' or 'CANCEL'.

Explanation: Noncritical errors occurred duringCMAS or MAS parameter initialization.

System action: Parameter initialization pauses andwaits for a reply.

User response: Review the messages issued before thisone to determine what types of parameter errorsoccurred. Then decide if parameter initialization shouldcontinue with those errors or be canceled. If you reply‘GO’, parameter initialization continues. If you reply‘CANCEL’, parameter initialization is terminated;correct the errors identified in the related messages and

rerun the CMAS or MAS startup job.

Module: EYU0XLPI


EYUXL0206E Invalid parameter name - parmname -parameter bypassed

Explanation: An invalid parameter name was foundduring CMAS or MAS parameter initialization, where:

parmnameIdentifies the invalid parameter name.

System action: The invalid parameter name isignored. This is a noncritical error; parameterinitialization for the CMAS or MAS continues. Thismessage is followed by message EYUXL0205D.

User response: Reply to message EYUXL0205D whenit is issued.



EYUXL0207E Invalid parameter value - value -parameter bypassed

Explanation: An invalid parameter value was foundduring CMAS or MAS parameter initialization, wherevalue identifies the invalid parameter value.

System action: The invalid parameter value isignored. This is a noncritical error; parameterinitialization for the CMAS or MAS continues. Thismessage is followed by message EYUXL0205D.




EYUXL0208E Invalid parameter statement - parameter

Explanation: An invalid parameter statement wasfound during CMAS or MAS parameter initialization.The parameter statement was either too long or notproperly delimited, where value identifies the invalidparameter statement.

System action: The invalid parameter statement isignored. This is a noncritical error; parameterinitialization for the CMAS or MAS continues. Thismessage is followed by message EYUXL0205D.






EYUXL0209I type Parameters For compid

Explanation: This is the message header for aparameter list request, where type identifies the type ofparameters being listed as SYSTEM, major objectdescriptor block (MODB), or major object executionparameters (MOEP). For MODB parameters, compididentifies which CICSPlex SM component theparameters are associated with.



Module: EYU0XLPR

Destination: EYULOG

EYUXL0210I parameter = value

Explanation: This message lists a parameter and thevalue that is currently in effect.



Module: EYU0XLPR

Destination: EYULOG

EYUXL0211I CPSM Start Up Parameters

Explanation: This is the message header for anEYUPARM list and any associated errors.





EYUXL0212I parameter

Explanation: This message lists a parameter statementas it was found in the EYUPARM input data set duringCMAS or MAS parameter initialization.

System action: If any part of the parameter statementis invalid, this message is followed by the appropriateerror message.




EYUXL0213E Required Parameter "parameter" notsupplied

Explanation: A required parameter was not foundduring CMAS or MAS parameter initialization.


User response: Review the parameter requirements inthe CICS Transaction Server for z/OS Installation Guideand add the missing parameters to the EYUPARM dataset.



EYUXL0214I Parameter Services initializationcomplete

Explanation: The Parameter Services subcomponenthas been successfully initialized.




Destination: EYULOG

EYUXL0215E Parameter Services initialization failed

Explanation: The Parameter Services subcomponentcould not be initialized.

System action: CICSPlex SM initialization terminates.A user trace record is written to the CICS trace data set.




EYUXL0216I EYUPARM SET issued by user useridfrom termid termid : eyuparm = value

Explanation: A CICSPlex SM EYUPARM has beenupdated via the COD0 transactions SET request, where:

userid Is the user ID associated with the terminalrunning the COD0 transaction.

termid Is the CICS terminal identifier associated withthe COD0 transaction.

eyuparmIs the CICSPlex SM system parameter(EYUPARM) being updated.

value Is the name value the EYUPARM is being setto.

If one or both userid and terminal inserts are notavailable N/A will be displayed for these inserts.

System action: The specified EYUPARM is updated.

User response: None. This message is to log a changein the CICSPlex SM system parameter.

Module: EYU9DBG1




EYUXL0900I Starting Environment Recovery

Explanation: The CICSPlex SM recovery routine hasbeen entered as a result of an abend in a CMAS or aMAS.

System action: The recovery routine attempts tocapture and format any relevant diagnostic information.All available information is presented in EYUXL09nnmessages that follow this one.

A transaction dump is taken. If a CMAS or local MASabended and the method that abended was found to bein access register (AR) mode improperly, an SVC dumpmay also be taken.

User response: Collect as much of the followinginformation as possible, and contact your IBM SupportCenter:

v Job log for the job that received the abend. If the joblog is not available, get the system log.

v EYULOG file. If a CMAS abended, get the EYULOGfile for that CMAS. If a MAS abended, get theEYULOG file for the CMAS to which the MAS wasconnected.

v Formatted transaction dump.

v Unformatted SVC dump, if one was taken.

v AUXTRACE file, if available. If a MAS abended andAUXTRACE was not active in that CICS system, getthe AUXTRACE file from the CMAS to which theMAS was connected.

Module: EYU9XLRV

Destination: Console, Job log

EYUXL0902I ABEND Outputting Storage Areas

Explanation: While attempting to capture and formatdiagnostic information, the CICSPlex SM recoveryroutine encountered addresses that could not beaccessed.

System action: The recovery routine terminates andno further diagnostic information is presented.

User response: Follow the instructions in messageEYUXL0900I.

Module: EYU9XLRV


EYUXL0903I Branch to location ZERO, Using R14 forOffset

Explanation: A calling program attempted to branchto an invalid address. The CICSPlex SM recoveryroutine uses the address in register 14 in an attempt toformat any relevant diagnostic information.

System action: The recovery routine begins formattingdiagnostic information.


Module: EYU9XLRV


EYUXL0904I method call-type in AR MODE,Displaying from call

Explanation: A program was found to be in accessregister (AR) mode when it should not be, where:

call-typeIndicates whether the problem was found by acalling program (CALL) or a returningprogram (EXIT).

method Is displayed only for a call-type of EXIT, andidentifies the CICSPlex SM method thatdetected the problem.

System action: The recovery routine identifies theproblem program and displays its name in messageEYUXL0905E.


Module: EYU9XLRV


EYUXL0905E applid abcode IN method OFFSETnnnnnnnn PSW psw1 psw2 INTC=intcodeILC=len TXCP=addr SCODE=syscodeTRAN=tranid TASK=tasknumMETHODS=methnames

Explanation: This message describes the location andconditions of an abend that occurred in CICSPlex SM,where:

applid z/OS Communications Server application IDof the CICS system that abended.

abcode Four-digit CICS user abend code.

methodCICSPlex SM method that abended.

nnnnnnnnOffset within the method where the abendoccurred.

psw1/psw2Contents of the PSW at the time of the abend.

intcode Interrupt code.

len Length of the instruction.

addr Address of the last translation exception.

syscodeThree-digit system abend equivalent of theCICS user abend code.

tranid CICS transaction id.

EYUXL0900I • EYUXL0905E


tasknumCICS task number.

methnamesnames of all CICSPlex SM methods active inthe failing task.

System action: The recovery routine continues toformat diagnostic information.


Module: EYU9XLRV


EYUXL0906I Registers at ABEND

Explanation: The register contents at the location ofthe abend have been formatted; this message serves asa header for the content records that follow.

System action: The recovery routine continues toformat diagnostic information. The register contents aredisplayed in EYUXL0907I messages immediatelyfollowing this header.


Module: EYU9XLRV


EYUXL0907I register contents

Explanation: The name of each register that wasformatted is displayed along with its content.



Module: EYU9XLRV


EYUXL0908I Storage At ABEND

Explanation: The contents of storage at the location ofthe abend have been formatted; this message serves asa header for the content records that follow.

System action: The recovery routine continues toformat diagnostic information. The contents of storageare displayed in EYUXL0909I messages immediatelyfollowing this header.


Module: EYU9XLRV


EYUXL0909I +/-nn storage contents

Explanation: The contents of storage at each of thefollowing locations is displayed:

-20 32 bytes before the PSW

-10 16 bytes before the PSW

+00 Start of the PSW

+10 16 bytes after the PSW

System action: The formatting of diagnosticinformation is complete. The recovery routineterminates.

The impact on system processing depends on when theabend occurred:

During CMAS initializationThe CMAS terminates.

During MAS initializationAll MAS agent code is removed from the CICSsystem. The CICS system continues toinitialize, but it is not known to CICSPlex SM.

After CMAS or MAS initializationCICSPlex SM attempts to return control to thelast point of processing before the abend.


Module: EYU9XLRV


EYUXL0910I dump_title

Explanation: This message indicates that an SDUMPhas been requested by CPSM recovery, where:

dump_titleIs the title string passed to the system dumproutine.

System action: An SDUMP has been requested,containing the current region, the ESSS Address Space,and cache data spaces for components accessed in theabending task.


Module: EYU9XLRV


EYUXL0911W EYU9XLRV dump suppressed becauseESDUMP is set to NEVER

Explanation: A SVC dump that would have beenissued by abend recovery module EYU9XLRV has beensuppressed because the value of the ESDUMPEYUPARM is NEVER.


EYUXL0906I • EYUXL0911W



Module: EYU9XLRV


EYUXL0912W EYU9XLRV dump suppressed becauseESDUMPLIMIT has been reached forjob jobname date dd/mm/yyyy timehh:mm:ss.

Explanation: A SVC dump was requested but thedump was suppressed because the CICSPlex SMsystem parameter ESDUMP is set to NO and the numberof dumps requested with this program name, abendcode, offset and region type (CMAS or MAS)combination exceeds the value specified on theCICSPlex SM system parameter ESDUMPLIMIT.

<jobname>Is the job name of the CICS system when thelast abend was captured.

<dd/mm/yyyy>Is the date when the last abend was captured.

<hh:mm:ss>Is the time when the last abend was captured.


User response: This is normal and can be ignoredunless a new dump is needed. If a new dump isneeded, set the ESDUMP parameter to YES, reproduce theproblem, and then reset ESDUMP back to NO. Refer tothe ESDUMP and ESDUMPLIMIT documentation in CICSTransaction Server for z/OS CICSPlex SM ProblemDetermination.

Module: EYU9XLRV


EYUXL0913E EYU9XLRV request to take an SDUMPXfailed with return code retcde, reasoncode reason.

Explanation: An SDUMPX request issued by this CICSregion failed to complete successfully.

retcde Is the hexadecimal return code returned by theSDUMPX macro.

reason Is the hexadecimal reason code returned bythe SDUMPX macro.

System action: This message is issued and the dumpis not taken. Processing then continues.

User response: Refer to the z/OS MVS Programming:

Authorized Assembler Services Reference manual thatdocuments the SDUMPX macro, to determine themeaning of the return code and reason code.

Module: EYU9XLRV

Message inserts:

1. retcde

2. reason


EYUXL0951E Exception occurred on mm/dd/yy athh:mm:ss

Explanation: This message indicates the date and timeat which the abend described in message EYUXL0950Eoccurred, where:

mm/dd/yyIs the date when the abend occurred.

hh:mm:ssIs the time when the abend occurred.



Module: EYU1XLRV

Destination: Console, Job log, EYULOG

EYUXL0951E Exception occurred on mm/dd/yy athh:mm:ss

Explanation: This message indicates the date and timeat which the abend described in message EYUXL0950Eoccurred, where:

mm/dd/yyIs the date when the abend occurred.

hh:mm:ssIs the time when the abend occurred.



Module: EYU1XLRV


EYUXL0953E CPSM method name at offset offset

Explanation: This message identifies the CICSPlex SMmethod where the abend occurred, where:

name Is the name of the method.

offset Is the offset within the method where theabend occurred.

EYUXL0912W • EYUXL0953E


####

#######

###

##

##

#

#######

#

#



Module: EYU1XLRV


EYUXL0955I Registers at ABEND:

Explanation: The register contents at the location ofthe abend have been formatted; this message serves asa header for the content records that follow.

System action: The recovery routine continues toformat diagnostic information. The register contents aredisplayed in EYUXL0956I messages immediatelyfollowing this header.


Module: EYU1XLRV


EYUXL0956I CS=cs DS=ds ES=es FS=fs GS=gs SS=ssEIP=eip EAX=eax EBX=ebx ECX=ecxEDX=edx EBP=ebp EDI=edi ESI=esiESP=esp FLAGS=flags PID=pid TID=tid

Explanation: The name of each register that wasformatted is displayed along with its content. Theregisters are displayed in logical groups. The firstgroup includes the machine registers, where:

cs Code segment

ds Data segment

es Extra segment

fs Far segment

gs General segment

ss Stack segment

The next group includes the extended (32-bit) registers,where:

eip Instruction pointer

eax Extended ax

ebx Extended bx

ecx Extended cx

edx Extended dx

ebp Base pointer

edi Destination index

esi Source index

esp Stack pointer

The last group includes hardware and operating systemregisters, where:

flags Hardware status flags

pid Operating system process ID

tid Operating system thread ID



Module: EYU1XLRV


EYUXL0957I Stack Len: length Extra Info: data

Explanation: This message provides additionalinformation about the abend, where:

length Is the length of the remaining stack.

data Is additional data that is supplied for someabend codes.



Module: EYU1XLRV


EYUXL0958I Exception handled

Explanation: The CICSPlex SM recovery routine wasable to recover from the abend.

System action: The formatting of diagnosticinformation is complete. The recovery routineterminates.


Module: EYU1XLRV


EYUXL0999I XLRV Exiting Successfully

Explanation: The CICSPlex SM recovery routine(XLRV) has successfully completed processing theabend reported in the previous EYUXL09xx messages.



Module: EYU9XLRV




Chapter 43. EYUXMnnnn messages

EYUXM0001I Message Service initializationcomplete

Explanation: The Message Services component hasbeen successfully initialized.



Module: EYU0XMIN, EYU3XMIN

Destination: EYULOG

EYUXM0004I Message Services terminationcomplete

Explanation: The Message Services component hasbeen terminated.

System action: The Message Services component is nolonger available to issue messages.


Module: EYU0XMTM, EYU3XMTM


EYUXM0010E Message Services termination failed

Explanation: An error occurred while attempting toterminate the Message Services component.

System action: The Message Services component is nolonger available to issue messages. A user trace recordis written to the CICS trace data set.

User response: Examine the exception trace records,and any messages issued prior to this one, to determinethe cause of the problem.

Module: EYU0XMTM


EYUXM0020W Consolidated message log queue notallocated

Explanation: During initialization of a MAS, a failureoccurred while retrieving the message queue ID for theCMAS to which the MAS is connecting.


User response: Collect the AUXTRACE data sets fromthe CMAS and the complete JOB output from theCMAS and the MAS and contact your IBM supportcenter.

Module: EYU0XMIN


EYUXM0100I Consolidated message log longrunning task started

Explanation: The EYULOG writing task, XMLT, hassuccessfully started in the CMAS.



Module: EYU0XMLT

Destination: EYULOG

EYUXM0101I Consolidated message log longrunning task terminated

Explanation: The EYULOG writing task, XMLT, hasterminated normally in the CMAS.



Module: EYU0XMLT

Destination: EYULOG

EYUXM0110W Consolidated message log notavailable

Explanation: During initialization of the EYULOGwriting task XMLT, a failure occurred attempting toaccess the EYULOG.

System action: CMAS initialization continues. Nomessages will be written to the EYULOG.

User response: Collect the AUXTRACE data sets andthe complete JOB output from the CMAS and contactyour IBM support center.

Module: EYU0XMLT


EYUXM0120E Consolidated message log longrunning task terminated abnormally

Explanation: The EYULOG writing task, XMLT, hasterminated abnormally in the CMAS.


User response: Collect the AUXTRACE data sets andthe complete JOB output from the CMAS and contactyour IBM support center.

Module: EYU0XMLT



EYUXM0505E IYP2Z001 Method = mmmm Debug =dddddddd Comp = cc SComp = s MsgID= xxxx PtID (yyyy) = pt

Explanation: An error occurred while attempting togenerate a message, where:

mmmmIdentifies the method that called MessageServices.

ddddddddIdentifies the debug string from methodmmmm.

cc Identifies the component that tried to issue themessage.

s Identifies the subcomponent that tried to issuethe message.

xxxx Is the number of the message that could notbe issued.

yyyy Identifies the method that issued messageEYUXM0505E (either XMSM or XMSX).

pt Identifies the point in method xxxx at whichthe error occurred.

System action: The requested message is either notcreated or not directed to its destination.

User response: Refer to the related messages issued inassociation with this one to determine the cause of theproblem. You might need to contact your IBM SupportCenter.

Module: EYU0XMSM,, EYU0XMSX


EYUXM0506E IYP2Z002 Var num = vv Type = tt Len= ll Val = vvvvvvvv

Explanation: An error occurred while attempting toprocess an insert variable when generating a message,where:

vv Is the number of the message insert variable.

tt Is the type of the message insert variable.

ll Is the length of the message insert variable.

vvvvvvvvIs the value (in hexadecimal) of the first fourbytes of the message insert variable.

If this message is issued EYUXM0505E will be issuedas well providing additional information.

System action: The requested message is either notcreated or not directed to its destination.

User response: Refer to the related messages issued inassociation with this one, including EYUXM0505E andDFHME0109, to determine the cause of the problem.

You may need to contact your IBM Support Center.

Module: EYU0XMSM,, EYU0XMSX


EYUXM0507E Message Service initialization hasfailed - CICS compatibility APAR ismissing.

Explanation: CICSPlex SM (at CICS TS level 3.2 andlater) has failed to start in a MAS because theappropriate CICS compatibility APAR has not beenapplied to the pre-CICS TS 3.2 level of CICS in theMAS. The compatibility APARs for each supportedlevel of CICS are as follows:

v PK17360 for CICS TS 3.1



System action: Message EYUXL0112E willsubsequently be issued. See the explanation forEYUXL0112E for further information.

User response: Apply the appropriate CICS APAR. Ifthis APAR has been installed correctly andEYUXM0507E persists contact your IBM SupportCenter.

Module: EYU0XMIN


EYUXM0508E Message Service initialization hasfailed - unable to generate messages viaCICS message services.

Explanation: CICSPlex SM message services havefailed to start in either in a CMAS, MAS, or in a SSMSbecause it could not generate messages via CICSmessage services.

The probable cause is that the CICSPlex SM messagedefinition module (EYUMCT1x) is not present in any ofthe STEPLIB libraries. Message EYUXM0508E ispreceded by one or more CICS message domainmessages (DFHMEnnnn) which give additionalinformation about the cause of the failure.

System action: Depending on the environment,message EYUXL0112E might subsequently be issued.See the explanation for EYUXL0112E for furtherinformation.

In an SMSS environment, the CMCI call fails, reportingan error in the CONNECT api_function.

User response: Ensure that the CICSPlex SMSEYUAUTH data set, containing the message definitionmodule (EYUMCT1x), is in the STEPLIB.

Module: EYU0XMIN


EYUXM0505E • EYUXM0508E


Chapter 44. EYUXQnnnn messages

EYUXQ0001I Queue Manager initialization complete

Explanation: The Queue Manager subcomponent hasbeen successfully initialized.



Module: EYU0XQIN, EYU3XQIN

Destination: EYULOG

EYUXQ0002I Queue Manager termination complete

Explanation: The Queue Manager subcomponent hasbeen terminated.



Module: EYU0XQTM, EYU3XQTM

Destination: EYULOG

EYUXQ0101E Queue Manager initialization failed

Explanation: The Queue Manager subcomponentcould not be initialized.



Module: EYU0XQIN, EYU3XQIN


EYUXQ0102W Queue Manager termination failed

Explanation: An error occurred while attempting toterminate the Queue Manager subcomponent.



Module: EYU0XQTM, EYU3XQTM



Chapter 45. EYUXSnnnn messages

EYUXS0001I Common Services initializationcomplete

Explanation: The Common Services subcomponenthas been successfully initialized.



Module: EYU0XSIN, EYU3XSIN

Destination: EYULOG

EYUXS0002I Common Services termination complete

Explanation: The Common Services subcomponenthas been terminated.



Module: EYU0XSTM, EYU3XSTM

Destination: EYULOG

EYUXS0003E Journaling was requested however,Journal 25 is not allocated

Explanation: One or all of the journaling EYUPARMparameters were specified which caused the CMAS tomake an attempt to open the journal file. CICS returnedresponses which indicated that the journal file was notallocated.

System action: Initialization continues. Anotherattempt will be made to open the journal file when ajournal record is about to be written.

User response: Ensure that a JOURNALMODELdefinition has been created for Journal 25.

Module: EYU0XSIN

Destination: EYULOG, console

EYUXS0005E Common Services was unable tosuccessfully action Journal 25,Resp1=response1 Resp2=response2

Explanation: One or all of the journaling EYUPARMparameters were specified which caused the CMAS tomake an attempt to perform the indicated actionagainst the journal.


User response: Look up the responses from CICS inthe Application reference manual to determine theproblem.

Module: EYU0XSIN


EYUXS0006W Common Service was unable tosuccessfully action Journal 25,Resp1=response1 Resp2=response2Journaling data has been lost

Explanation: One or all of the journaling EYUPARMparameters were specified which caused the CMAS tomake an attempt to perform the indicated actionagainst the journal. Journaling data has been lost as aresult of this error.


User response: Look up the responses from CICS inthe Application reference manual to determine theproblem.

Module: EYU0XSJW


EYUXS0007E Extract for exit EYU9XSTR failed,RESP=nn, EIBRCODE=xxxxxxxxxxxx

Explanation: An error occurred in a CMAS or localMAS while attempting to extract the address of theglobal area for the CICSPlex SM task recovery taskrelated user exit (TRUE), where:

nn Is the CICS numeric RESP value


System action: CICSPlex SM Common Servicesinitialization fails. If the system is a CMAS, anEYUXL001 system dump will be taken, CMASinitialization will fail, and the CMAS will terminate. Ifthe region is a local MAS, an EYUI transaction dumpwill be taken and the MAS agent initialization will fail.

User response: Verify that the exit program,EYU9XSTR, is defined and installed in the CMAS orlocal MAS, and that it resides in a DFHRPL librarybeing used by the CMAS or local MAS. If the errorcontinues after the above is verified, collect as much ofthe following as possible and contact your IBM SupportCenter:

v The complete job output.

v The unformatted SVC dumps for any abends thatmay have occurred during the execution of theCMAS or MAS.

v The unformatted AUXTRACE data sets (if the systemis a MAS and AUXTRACE was not active in that


system, collect the AUXTRACE data sets from theCMAS to which the MAS was connected).

Module: EYU0XSIN


EYUXS0101E Common Services initialization failed

Explanation: The Common Services subcomponentcould not be initialized.


User response: Collect the exception trace records andcontact your IBM Support center.

Module: EYU0XSIN


EYUXS0102W Common Services termination failed

Explanation: An error occurred while attempting toterminate the Common Services subcomponent.


User response: Collect the exception trace records andcontact your IBM support center.

Module: EYU0XSTM


EYUXS0910I dump title

Explanation: This message indicates that an SDUMPhas been requested by the CICSPlex SM task recoveryexit, EYU9XSTR, executing in a CMAS or local MAS,where:

dump titleIs the title string passed to the system dumproutine

System action: An SVC dump has been requested,containing the current region and the ESSS addressspace.

User response: Collect as much of the following aspossible and contact your IBM Support Center:


v The unformatted SVC dump (the dump title in themessage can be used to identify the required dump).

v The unformatted AUXTRACE data sets (if the systemis a MAS and AUXTRACE was not active in thatsystem, collect the AUXTRACE data sets from theCMAS to which the MAS was connected).

Module: EYU9XSTR


EYUXS1001I Interval Timing initialization has started

Explanation: The Interval Timing subcomponent isbeing initialized.

System action: Interval Timing initialization continues.


Module: EYU9XSTC


EYUXS1002I Interval Timing initialization complete

Explanation: The Interval Timing subcomponent hasbeen successfully initialized.



Module: EYU9XSTC


EYUXS1003S Interval Timing unable to attach CICSinitialization program

Explanation: An attempt by the Interval Timingsubcomponent to attach DFHSIP, the CICS initializationprogram, as a subtask was unsuccessful.

System action: CMAS execution is terminated.

User response: Check the system log for MVSContents Supervisor messages, which begin with theprefix CSVnnn. These messages should explain thecause of the problem. If the cause of the problem is notapparent, collect the MVS system log and the CMASjob log and contact your IBM support center.

Module: EYU9XSTC


EYUXS1004W Interval Timing queue elementshortage detected

Explanation: The Interval Timing subcomponent hasexhausted the queue elements that it uses to receiverequests from other components.

System action: Interval Timing attempts to allocateadditional queue elements.

User response: If the shortage can be relieved, thismessage is followed by message EYUXS1005I and nouser action is required. If the shortage cannot berelieved, report the problem to your IBM supportcenter.

Module: EYU9XSTC


EYUXS0101E • EYUXS1004W


EYUXS1005I Interval Timing queue element shortagerelieved

Explanation: The Interval Timing subcomponent hassuccessfully handled a queue element shortage.



Module: EYU9XSTC


EYUXS1006I Interval Timing has interceptedabnormal termination

Explanation: An abnormal termination has occurred inthe Interval Timing subcomponent.

System action: Interval Timing recovery processing isinitiated.


Module: EYU9XSTC


EYUXS1007I Interval Timing recovery has started

Explanation: The Interval Timing subcomponent hasinitiated its recovery processing in response to anabnormal termination.

System action: Interval Timing takes an SVC dumpand attempts to recover from the error.


Module: EYU9XSTC


EYUXS1008I Interval Timing recovery complete

Explanation: The Interval Timing subcomponent hassuccessfully recovered from an abnormal termination.


User response: If an SVC dump was produced byInterval Timing, notify your IBM support center.

Module: EYU9XSTC


EYUXS1009S Interval Timing recovery impossible -control task is terminated

Explanation: The Interval Timing subcomponent wasunable to recover from an abnormal termination.

System action: Interval Timing takes an SVC dump.CMAS execution is terminated.

User response: Collect the SVC dump and contactyour IBM support center.

Module: EYU9XSTC


EYUXS1010S Interval Timing has detected possiblerecursive error condition

Explanation: The Interval Timing recovery routinedetected an error condition from which recovery is notpossible.

System action: Interval Timing takes an SVC dump.CMAS execution is terminated.

User response: Collect the SVC dump and contactyour IBM support center.

Module: EYU9XSTC


EYUXS1011S applid Interval Timing could not load theexternal security manager interface

Explanation: During initialization, the Interval Timingsubcomponent could not load the EYU9XSEC externalsecurity manager (ESM) interface, where:

applid Is the z/OS Communications Serverapplication ID of the CMAS.

System action: Interval Timing initialization continues.

User response: If you want security to be active in theCMAS, ensure the EYU9XSEC module is contained inthe CMAS STEPLIB, the MVS linklist, or the LPAlibrary concatenation, then restart the CMAS.

Module: EYU9XSTC


EYUXS1012S applid Interval Timing unable to attachthe external security manager interface

Explanation: During initialization, the Interval Timingsubcomponent attempted to use an MVS ATTACHcommand to start the external security manager taskand the ATTACH failed, where applid is the z/OSCommunications Server application ID of the CMAS.

System action: Interval Timing initializationterminates. CMAS initialization terminates.

User response: Check the system log for MVSContents Supervisor messages, which begin with theprefix CSVnnn; these messages should explain thecause of the problem. If the cause of the problem is notapparent, collect the MVS system log and the CMASjob log and contact your IBM support center.

Module: EYU9XSTC


EYUXS1005I • EYUXS1012S


|||

|||

|||

|

||||

|

|

EYUXS1013I Interval Timing detached the externalsecurity manager interface

Explanation: The interval timing subcomponent hasquiesced the external security manager interface.CICSPlex SM security services are now no longeravailable.


User response: None

Module: EYU9XSTC


EYUXS1014I Task recovery starting for task nnnnntransaction cccc

Explanation: The CICSPlex SM task recovery TRUE,EYU9XSTR, executing in a CMAS or local MAS,encountered a terminating task that did not go throughCICSPlex SM cleanup processing, where:

nnnnn Is the task number

cccc Is the transaction ID for the task

System action: CICSPlex SM cleanup processing willbe attempted for the task. The results of this recoveryprocessing will be reported after recovery is completeby message EYUXS1015I or EYUXS1016E.

User response: The most common causes for aCICSPlex SM task to not go through cleanup processingis if a monitor, interactive debugger, or EYU9WRAMprogram is being used to "KILL" tasks, eitherautomatically or on demand, or otherwise cause anabnormal termination that does not go through normalCICS HANDLE ABEND processing (for example, issuesEXEC CICS ABEND with the CANCEL option). If thismessage occurs without the benefit of one of the above,or if there is no subsequent EYUXS1015I orEYUXS1016E message to pair with this EYUXS1014Imessage, then collect as much of the following aspossible and contact your IBM Support Center:


v the unformatted SVC dumps for any abends thatmay have occurred during the execution of theCMAS or MAS.


Module: EYU9XSTR


EYUXS1015I Task recovery complete for task nnnnnflags 123456789

Explanation: The CICSPlex SM task recovery TRUE,EYU9XSTR, executing in a CMAS or local MAS,completed task recovery for a terminating task where:


1 Is Y if recovery successfully unchained thetask's CICSPlex SM task work area, N if it didnot.

2 Is Y if recovery successfully completed globallock recovery for the task, N if it did not.

3 Is Y if recovery successfully freed a global lockholder element for the task, N if it did not. If ?is displayed for this flag, the ESSS addressspace was not restarted after applying the PTFfor APAR PQ79290.

4 Is Y if recovery successfully freed a global lockwaiter element for the task, N if it did not. If ?is displayed for this flag, the ESSS addressspace was not restarted after applying the PTFfor APAR PQ79290.

5 Is Y if recovery successfully completed locallock recovery for the task, N if it did not.

6 Is Y if recovery successfully freed a local lockholder element for the task, N if it did not.

7 Is Y if recovery successfully freed a local lockwaiter element for the task, N if it did not.

8 Is Y if recovery successfully freed 64-bitstorage for the task, N if it did not.

9 Is N. Recovery was successful, so no SVCdump was taken for this task.

System action: CICSPlex SM cleanup processing hascompleted for the task. The start of this recoveryprocessing has been reported by a previousEYUXS1014I message.

User response: Please refer to the documentation forpartner message EYUXS1014I to determine whether ornot the issuing of these messages should be reported toIBM support.

Module: EYU9XSTR


EYUXS1016E Task recovery in error for task nnnnnflags 123456789

Explanation: The CICSPlex SM task recovery TRUE,EYU9XSTR, executing in a CMAS or local MAS,encountered at least one error while performing taskrecovery for a terminated task, where:


1 Is Y if recovery successfully unchained thetask's CICSPlex SM task work area, N if it didnot.

2 Is Y if recovery successfully completed globallock recovery for the task, N if it did not, or Eif the address space was not connected to theESSS.

EYUXS1013I • EYUXS1016E


3 Is Y if recovery successfully freed a global lockholder element for the task, N if it did not. If ?is displayed for this flag, the ESSS addressspace was not restarted after applying the PTFfor APAR PQ79290.

4 Is Y if recovery successfully freed a global lockwaiter element for the task, N if it did not. If ?is displayed for this flag, the ESSS addressspace was not restarted after applying the PTFfor APAR PQ79290.

5 Is Y if recovery successfully completed locallock recovery for the task, N if it did not.

6 Is Y if recovery successfully freed a local lockholder element for the task, N if it did not.

7 Is Y if recovery successfully freed a local lockwaiter element for the task, N if it did not.

8 Is Y if recovery successfully freed 64-bitstorage for the task, N if it did not, or F if afailure occurred freeing storage.

9 Is Y if a dump was taken because of errorsduring recovery for the task, S if a dump wasrequested but suppressed because a previousdump was taken for this execution of theCMAS or MAS, E if the CMAS or MAS is notconnected to the ESSS, or F if a failureoccurred taking the dump.

System action: CICSPlex SM cleanup processing hascompleted for the task. The first time this messageoccurs during the execution of the CMAS or MAS, anSVC dump will be requested, along with messageEYUXS0910I.





Module: EYU9XSTR


EYUXS1017E The controlling task for this region,transaction cccc, is terminatingabnormally.

Explanation: The CICSPlex SM task recovery TRUE,EYU9XSTR, executing in a CMAS or local MAS,determined that the terminating task for which cleanupprocessing is being performed is the CICSPlex SMcontrolling task in the region where:


System action: An SVC dump will be requested, alongwith message EYUXS0910I, if one has not already beenrequested for this task. If the region is a CMAS, it willbe cancelled. If the region is a local MAS, it will bedisconnected from the ESSS and a restart of the regionwill be required in order for it to reconnect.

Note: This message will be preceded by messageEYUXS1014I and will be followed by messageEYUXS1015I or EYUXS1016E.

User response: Refer to the documentation for theaccompanying EYUXS1015I or EYUXS1016E message,and then restart the region.

Note: Additional errors (for example, abends) mayoccur in the region as a result of the cancel (CMAS) orESSS disconnection (local MAS). These errors are to beexpected and should be ignored.

Module: EYU9XSTR


EYUXS1018E ESSS disconnect failed, RESP nnn.

Explanation: The CICSPlex SM task recovery TRUE,EYU9XSTR, executing in a local MAS, encountered aninvalid return code when requesting that the MAS bedisconnected from the ESSS where:

nnn Is the invalid return code


Note: This message is preceded by messageEYUXS1017E.





Then restart the local MAS.

Module: EYU9XSTR


EYUXS1019W API resources allocated for task nnnnnmay be orphaned.

Explanation: The CICSPlex SM task recovery TRUE,EYU9XSTR, executing in a local MAS, is performingcleanup for a task that allocated CICSPlex SM APIresources which have not been freed where:


EYUXS1017E • EYUXS1019W


System action: CICSPlex SM cleanup processingcontinues. This message will be preceded by messageEYUXS1014I and followed by message EYUXS1015I orEYUXS1016E.

User response: The API resources orphaned reside inthe local MAS and in the CMAS to which it isconnected. If this message occurs frequently, the localMAS receiving the message and the CMAS to which itis connected should be restarted to release theorphaned resources.

Module: EYU9XSTR


EYUXS1020E Terminating the MAS agent due to thetermination of the task for transactioncccc.

Explanation: The CICSPlex SM task recovery TRUE,EYU9XSTR, executing in a local MAS, determined thatthe terminating task for which cleanup processing isbeing performed is the receive task (transaction COI0)or the status task (transaction COIE), where:


System action: An SVC dump will be requested, alongwith message EYUXS0910I, if one has not already beenrequested for this task. The MAS agent is thenterminated.

User response: Refer to the documentation for theaccompanying EYUXS1015I or EYUXS1016E message,and then restart the region or issue the COLMtransaction to restart the MAS agent.

Module: EYU9XSTR


EYUXS1021S applid Interval Timing could not load theCICS initialization program

Explanation: During initialization, the Interval Timingsubcomponent could not load the CICS initializationprogram DFHSIP, where:

applid Is the z/OS Communications Serverapplication ID of the CMAS.

System action: CMAS execution is terminated.

User response: Ensure the DFHSIP module iscontained in the CMAS STEPLIB, the MVS linklist, orthe LPA library concatenation, and then restart theCMAS.

Module: EYU9XSTC


EYUXS1026E Security Interface has interceptedabnormal termination CNNNN

Explanation: An abnormal termination has occurred inthe External Security subcomponent, where:

C is S for a System abend or U for a User abend

NNNN is the System or User abend code.

System action: External Security recovery processingis attempted.


Module: EYU9XSEC


EYUXS1027I Security Interface recovery has started

Explanation: The External Security subcomponent hasinitiated its recovery processing in response to anabnormal termination.

System action: The External Security Interface takesan SVC dump and attempts to recover from the error.


Module: EYU9XSEC


EYUXS1028I Security Interface recovery complete

Explanation: The External Security subcomponent hassuccessfully recovered from an abnormal termination.


User response: If an SVC dump was produced by theExternal Security subcomponent, notify your IBMsupport center.

Module: EYU9XSEC


EYUXS1029S Security Interface recovery impossible.Attempting CMAS termination

Explanation: The External Security subcomponent wasunable to recover from an abnormal termination.

System action: The External Security subcomponentrequests an SVC dump and terminates the CMAS.


Module: EYU9XSEC


EYUXS1020E • EYUXS1029S


|||

|||

|||

|

||||

|

|

EYUXS1030S Security Interface Abend limit reached

Explanation: The External Security subcomponentdetected a possible recursive abnormal terminationcondition.

System action: The External Security subcomponentrequests an SVC dump and terminates the CMAS.


Module: EYU9XSEC


EYUXS1101I Interval Timing termination has started

Explanation: The Interval Timing subcomponent isbeing terminated.

System action: Termination of the Interval Timingsubcomponent continues.


Module: EYU9XSTC


EYUXS1102I Interval Timing termination complete

Explanation: The Interval Timing subcomponent hasbeen terminated.



Module: EYU9XSTC


EYUXS1030S • EYUXS1102I


Chapter 46. EYUXUnnnn messages

EYUXUnnnn messages are issued by various utilities of the Kernel Linkagecomponent, such as the online utility transaction (COLU) and the batchedrepository-update facility.

The COLU transaction is a diagnostic tool that should be used only at the requestof customer support personnel; it is described in the CICSPlex System ManagerProblem Determination manual.

Note: If the COLU transaction is issued from an MVS console, its messages(EYUXU0001 – EYUXU0017) are returned to the console, rather than to a CICSterminal.

The batched repository-update facility can be used to create and modify definitionsin a CMAS data repository. Some of these messages describe problems with thebatched repository input file, such as invalid commands or resource objects. For adescription of the input file and its commands, see the CICSPlex System ManagerAdministration manual. For a list of valid resource objects and keywords, see theCICSPlex System Manager Resource Tables Reference Vol 1.

EYUXU0001I command input

Explanation: This message echoes the text of thecommand that was issued for the current COLUtransaction.

System action: COLU processing continues.


Module: EYU0XLUT

Destination: CICS terminal, SYSOUT

EYUXU0002I Online Utility terminated with result.

Explanation: The COLU transaction has completedprocessing, where:

result Indicates the result of COLU processing, asone of the following:

no errorsThe transaction completedsuccessfully.

error(s) The transaction encountered one ormore error conditions.

System action: The COLU transaction completes itsprocessing.

User response: If this message indicates there wereerrors, review any EYUXUnnnn messages issued beforethis one to determine the cause of the problem. Thencorrect the input to COLU and rerun the transaction.

Module: EYU0XLUT


EYUXU0003E CICS command failed, RESP=respcode,RESP2=resp2code.

Explanation: An EXEC CICS command returned anabnormal response, where:

commandIs the EXEC CICS command that caused theerror, and is one of the following:

v FREEMAIN

v GETMAIN

v SPOOLCLOSE

v SPOOLOPEN

v SPOOLWRITE

respcodeIs the EIBRESP code returned by CICS.

resp2codeIs the EIBRESP2 code returned by CICS.

System action: The COLU transaction terminates.

User response: Evaluate the RESP= and RESP2=values for the specified EXEC CICS command. Thencorrect the input to COLU, if possible, and rerun thetransaction. If the problem persists, contact your IBMSupport Center with the text of this message.

Module: EYU0XLUS


EYUXU0004E No parmtype specified in the inputstream.


Explanation: A required parameter was missing fromthe input to COLU, where:

parmtypeIdentifies the type of parameter that wasmissing as either a key word or data.


User response: Review the syntax of the COLUtransaction in the CICSPlex System Manager ProblemDetermination manual. Then correct the input to COLUand rerun the transaction.

Module: EYU0XLUT


EYUXU0005E Invalid parmtype (parm) specified.

Explanation: The COLU transaction was issued withan invalid parameter, where:

parmtypeIdentifies the type of parameter that wasinvalid as either a component ID or a keyword.

parm Is the component ID or keyword parameterthat was invalid.



Module: EYU0XLUT


EYUXU0006E cblock for compid is not available.

Explanation: A control block that is required byCOLU is not available for the specified component,where:

cblock Identifies the required control block as eitherMODB or MOEB.

compid Identifies the component that COLU wastrying to access.

The component may not be initialized in the CMAS orMAS where COLU was issued.


User response: Make sure the specified component isfully initialized and then rerun the transaction.

Module: EYU0XLUT


EYUXU0007E Invalid number of keyword values forkeyword parm.

Explanation: An invalid number of values werespecified with a keyword parameter on the COLUtransaction, where:

parm Is the keyword parameter that was invalid.



Module: EYU0XLUT


EYUXU0009E Invalid syntax in parameter parm.

Explanation: A parameter was specified incorrectly onthe COLU transaction, where:

parm Is the parameter whose syntax was incorrect.



Module: EYU0XLUT


EYUXU0010E Missing keyword value in keywordparm.

Explanation: A keyword parameter was specified onthe COLU transaction without a required value, where:

parm Is the keyword parameter that was missing avalue.



Module: EYU0XLUT


EYUXU0011W Requested service is not availablefrom a addspace.

Explanation: An option was requested on the COLUtransaction that is not available from the type ofaddress space where the transaction was issued, where:

EYUXU0005E • EYUXU0011W


addspaceIdentifies the address space as a CMAS, a localMAS (LMAS), or a single server region(SMSS).


User response: Review the description of the COLUtransaction in the CICSPlex System Manager ProblemDetermination manual for a list of options and theaddress spaces from which they are available.

Module: EYU0XLUT


EYUXU0012E An ABEND occurred.

Explanation: An abend occurred during COLUtransaction processing.

System action: The COLU transaction terminates.User trace records are written to the CICS trace data setand a transaction dump is taken.

User response: Collect the trace records and thetransaction dump, and contact your IBM SupportCenter.

Module: EYU0XLUT


EYUXU0013E Options not supported for compid.

Explanation: There are no COLU options available forthe specified component of CICSPlex SM, where:

compid Is the component ID that was specified.


User response: Review the description of the COLUtransaction in the CICSPlex System Manager ProblemDetermination manual for a list of options and thecomponents for which they are available.

Module: EYU0XLUT


EYUXU0014E Utility processor for compidencountered an unexpected error.

Explanation: A CICSPlex SM program that was calledby the COLU transaction returned a Method FailureResponse, where:

compid Identifies the component that generated theerror.

System action: The COLU transaction terminates.User trace records are written to the CICS trace dataset.

User response: Collect the trace records and contactyour IBM Support Center.

Module: EYU0XLUT


EYUXU0015I There are no allocated queue resourceswhich satisfy your request

Explanation: The COLU online utility transaction wasissued with the QUE option and qualifying operands,but there are no allocated queues that match thespecified criteria.



Module: EYU0XL70


EYUXU0016E Component and/or method ID areinvalid

Explanation: Either a component ID or a method IDwas specified incorrectly on the COLU online utilitytransaction's QUE option.


User response: Reissue the COLU QUEUE transactionwith a valid component or method ID.

For a list of valid CICSPlex SM component IDs, see theCICSPlex System Manager Problem Determination manual.Valid method IDs are supplied by customer supportpersonnel, as needed.

Module: EYU0XL70


EYUXU0017E Query queue environment methodfailed with a status of nn

Explanation: The query queue environment method,which is used by the COLU online utility transaction'sQUE option, failed, where:

nn Is a numeric status code that identifies theproblem.

System action: A user trace record is written to theCICS trace data set. Additional messages relating to theproblem might also be written to the job log.


v SYSOUT file

v Trace records

v Job log of the CMAS or MAS where COLU wasrunning

Module: EYU0XL70


EYUXU0012E • EYUXU0017E


EYUXU1401I Initializing CICSPlex SM APIenvironment

Explanation: This shows a successful start for thebatch process.

System action: The CICSPlex SM batch utilitycontinues to run.

User response: None

Module: EYU9XDBT

Destination: SYSTSPRT

EYUXU1402S CICSPlex SM API environmentinitialization has failed

Explanation: The EYUINIT() program fails to initializebecause it is unable to access or run the CICSPlex SMinitialization program.

System action: The CICSPlex SM batch utility stops.

User response: Either your REXX or CICSPlex SMenvironment is not properly installed.

Module: EYU9XDBT


EYUXU1403E CONTEXT must be the first commandparameter

Explanation: The CONTEXT parameter in theEYU9XDBT job is not the first option. The firstoccurrence of the CONTEXT command parameter inthe EYU9XDBT job defines the name of the CMAS.


User response: Edit the EYU9XDBT job and move theCONTEXT parameter to the beginning.

Module: EYU9XDBT


EYUXU1404W Data following CONTEXT value hasbeen ignored

Explanation: The only data that should be associatedwith the CONTEXT parameter is the name of thecontext.


User response: Edit the EYU9XDBT job and delete theextraneous data.

Module: EYU9XDBT


EYUXU1405E CONTEXT must be the first commandspecification of the CPSMDEFS inputstream

Explanation: The CONTEXT parameter in theEYU9XDBT job is not the first option.


User response: Edit the EYU9XDBT job and move theCONTEXT parameter to the beginning.

Module: EYU9XDBT


EYUXU1406E CICSPlex SM API environmentinitialization has failed

Explanation: Unknown DEFINE command parameter.


User response: Edit the EYU9XDBT job and ensurethat the parameters are valid and spelt correctly.

Module: EYU9XDBT


EYUXU1407E Resource type must be explicit forobject deletion

Explanation: The name of the object that follows theDELETE command in the EYU9XDBT job has not beenrecognized or is missing.


User response: Review the log. Edit the EYU9XDBTjob and ensure that the name of the object is valid.

Module: EYU9XDBT


EYUXU1408E Unsupported ADD command resourcetype

Explanation: The ADD command supports tworesource types; TOGROUP and REGION.



Module: EYU9XDBT


EYUXU1409E Unsupported REMOVE commandresource type

Explanation: The REMOVE command supports theresource type FROMGROUP.


EYUXU1401I • EYUXU1409E



Module: EYU9XDBT


EYUXU1410E Input file reference omitted fromIMPORT command, request rejected.

Explanation: The DD name is either invalid or ismissing following the IMPORT command.



Module: EYU9XDBT


EYUXU1411E Input datasteam DDname is empty

Explanation: The contents of the specified input fileare either invalid or missing.


User response: Edit the input file.

Module: EYU9XDBT


EYUXU1412I numberof records records exported to fileDDname

Explanation: This reports the number of records thathave been exported to the specified output file.

System action: The specified output file is created.

User response: None

Module: EYU9XDBT


EYUXU1413I Processing complete

Explanation: This shows a successful end for the batchprocess.


User response: None

Module: EYU9XDBT


EYUXU1414W Data following CICSPLEX name isredundant and has been ignored

Explanation: There is additional unnecessary data onthe line following the CICSPLEX name.

System action: The CICSPlex SM batch utilitycontinues.

User response: Edit the EYU9XDBT job and ensurethat there is only the name of the CICSPlex present.

Module: EYU9XDBT


EYUXU1415E DEFINE REGION parametersincomplete

Explanation: One or more of the parameters followingthe DEFINE REGION command are missing. Theparameters are APPLID and SYSID.


User response: Edit the EYU9XDBT job and ensurethat all the parameters are present for all your regions.

Module: EYU9XDBT


EYUXU1416W Data following CICSGRP name isredundant and has been ignored

Explanation: There is additional unnecessary data onthe line following the CICSGRP name.


User response: Edit the EYU9XDBT job and removethe redundant data.

Module: EYU9XDBT


EYUXU1417E Resource resourcetype not consistentwith context type

Explanation: The CICSPlex is not defined as part ofthe CMAS name.


User response: Edit the EYU9XDBT job and ensurethat the CMAS name and the CICSPLEX namescorrespond.

Module: EYU9XDBT


EYUXU1418E Cannot specify both REGION andCICSGRP on same ADD command

Explanation: CICSGRP and REGION are defined onthe same ADD command in the CPSMUTL job.


User response: Edit the EYU9XDBT job and ensure



that there are separate ADD commands for theREGION and CICSGRP.

Module: EYU9XDBT


EYUXU1419E Must specify either REGION orCICSGRP on ADD command

Explanation: Each ADD command must have either aREGION or CICSGRP specified.


User response: Edit the EYU9XDBT job and ensurethat each ADD command has either a REGION orCICSGRP specified.

Module: EYU9XDBT


EYUXU1420E Cannot specify both REGION andCICSGRP on same REMOVE command

Explanation: CICSGRP and REGION are defined onthe same REMOVE command in the EYU9XDBT job.


User response: Edit the EYU9XDBT job and ensurethat there are separate REMOVE commands for theREGION and CICSGRP.

Module: EYU9XDBT


EYUXU1421E Must specify either REGION orCICSGRP on REMOVE command

Explanation: Each REMOVE command must haveeither a REGION or CICSGRP specified.


User response: Edit the EYU9XDBT job and ensurethat each REMOVE command has either a REGION orCICSGRP specified.

Module: EYU9XDBT


EYUXU1422I Object creation successful forresourcetype resourcename

Explanation: The object has been created successfully.


User response: None

Module: EYU9XDBT


EYUXU1423E Object creation failed for resourcetyperesourcename

Explanation: The object creation failed because anerror was encountered.


User response: This message is followed by messageEYUXU1430, which marks the start of the sectioncontaining the error feedback data, including errorcodes. Review the error feedback information, correctthe error, and retry the action.

Module: EYU9XDBT


EYUXU1424I Establishing connection to CONTEXTcontextname

Explanation: The CICSPlex SM batch utility isattempting to establish a connection to the namedcontext.


User response: None

Module: EYU9XDBT


EYUXU1425I Terminating connection from CONTEXTcontextname

Explanation: The CICSPlex SM batch utility isdisconnecting from the named context.


User response: None

Module: EYU9XDBT


EYUXU1426E Resource type resourcetype is notrecognized, request rejected.

Explanation: The resource type has not beenrecognized.


User response: Edit the EYU9XDBT job and enter avalid CICSPlex SM resource type.

Module: EYU9XDBT




EYUXU1427E Object objectType objectname within thecurrent Context contextname could not belocated in the CICSPlex SM datarepository

Explanation: The named object is either not defined inthe CICSPlex SM data repository, or is defined but notwithin the current CONTEXT assignment.

System action: EYU9XDBT processing will continue tothe next command.

User response: If you know that the named object hasbeen defined, ensure that is applicable to the previouslyset CONTEXT value. Otherwise the object name itselfmust be corrected.

Module: EYU9XDBT


EYUXU1428I Object deletion successful for objectypeobjectname

Explanation: The object was deleted following theREMOVE command.


User response: None

Module: EYU9XDBT


EYUXU1429E Object Deletion failed for objectypeobjectname

Explanation: The object could not be deletedfollowing the REMOVE command.


User response: Edit the EYU9XDBT job and enter avalid resource type.

Module: EYU9XDBT


EYUXU1430E Start of CICSPlex SM feedback data

Explanation: This marks the start of the section thatreturns data from the system.

System action: None

User response: None

Module: EYU9XDBT


EYUXU1431E End of CICSPlex SM feedback data

Explanation: This marks the end of the section thatreturns data from the system.

System action: None

User response: None

Module: EYU9XDBT


EYUXU1432E Command verb is invalid

Explanation: The command verb is invalid.


User response: Correct the EYU9XDBT input stream.

Module: EYU9XDBT


EYUXU1433E Mandatory resource name parameteromitted

Explanation: A valid parameter is missing.



Module: EYU9XDBT


EYUXU1434E Mandatory resource type parameteromitted

Explanation: A valid resource type is missing.



Module: EYU9XDBT


EYUXU1435E Command parameter repeated

Explanation: A command parameter has been usedtwice in the batch program.



Module: EYU9XDBT


EYUXU1436E Version ID version is not allowed forthis program

Explanation: The CICSPlex SM batch utility supportsCICS TS 1.3 and CICS TS 2.2.




User response: Ensure that you are using the correctlevel of CICS TS.

Module: EYU9XDBT


EYUXU1437E DDname data set is empty

Explanation: The named data set is empty or missing.


User response: Ensure that the data set is present andthat it has some contents.

Module: EYU9XDBT


EYUXU1439E Resource name length must not belonger than resource key length.

Explanation: The resource name length is longer thatthe key length.



Module: EYU9XDBT


EYUXU1440S TPARSE failed for ATTR data

Explanation: The CICSPlex SM TPARSE commandfailed to access the attribute data in a resource tablerecord. See the CICSPlex SM Application ProgrammingGuide for more information about the TPARSEcommand.


User response: Check the input stream is valid for theversion of CICSPlex SM in use.

Module: EYU9XDBT


EYUXU1441S TBUILD failed for resourceName data

Explanation: The CICSPlex SM TBUILD commandfailed to build a CICSPlex SM definition or a CICSresource table record from the data that was supplied.See the CICSPlex SM Application Programming Guide formore information about the TBUILD command.


User response: Check the input stream is valid for theversion of CICSPlex SM in use.

Module: EYU9XDBT


EYUXU1442S I/O error occurred reading DDnamedata set

Explanation: The CICSPlex SM batch utility is unableto access the data set.


User response: Check the feedback cpsmresponse andcpsmreason codes to identify the reuse of the feedbackfailure.

Module: EYU9XDBT


EYUXU1443S CICSPlex SM FEEDBACK OBJECTdata is not available: RESP=cpsmresponseREASON=cpsmreason

Explanation: CICSPlex SM is unable to create a bufferin preparation for receiving records.



Module: EYU9XDBT


EYUXU1444S CICSPlex SM FEEDBACK data is notavailable: RESP=cpsmresponseREASON=cpsmreason

Explanation: The feedback buffer has been created butthere is no feedback date available to populate it.



Module: EYU9XDBT


EYUXU1445S CICSPlex SM FEEDBACK cannot beextracted

Explanation: This has received an attribute butCICSPlex SM is unable to provide feedback data.


User response: Check for other messages to determinethe cause of the problem.

Module: EYU9XDBT


EYUXU1437E • EYUXU1445S


EYUXU1446E CICSPlex SM APIRESPONSE=cpsmresponseREASON=cpsmreason

Explanation: This message is issued as part of anothermessage.


User response: Check the cpsmresponse and cpsmreasoncodes to identify the cause of the error.

Module: EYU9XDBT


EYUXU1447I Object resourceType resourceName is aduplicate of an existing record. Recordcreation skipped

Explanation: The record already exists.


User response: None

Module: EYU9XDBT


EYUXU1448E Datastream rejected

Explanation: This message is issued as part of anothermessage.


User response: Refer to the initial message to decidewhat action to take.

Module: EYU9XDBT


EYUXU1449W Data following OPTION value hasbeen ignored

Explanation: There is invalid or additional datafollowing the value associated with the OPTIONparameter.


User response: Edit the file to remove or modify thedata.

Module: EYU9XDBT


EYUXU1450I responseOption process OPTION has beenset to responseValue

Explanation: The values for responseOption are eitherFEEDBACK or DUPREC. The values of responseValuefor the FEEDBACK option are either QUIET or

VERBOSE. The values of responseValue for the DUPRECoption are SKIP, OVERWRITE or REJECT. For moreinformation, see the CICSPlex SM ApplicationProgramming Reference manual.


User response: None

Module: EYU9XDBT


EYUXU1451I Object Update successful for resourceTyperesourceName

Explanation: The object has been updated successfully.


User response: None

Module: EYU9XDBT


EYUXU1452E OPTION command verb is invalid

Explanation: The OPTION command verb can beeither DUPREC or FEEDBACK.


User response: Check the syntax of your command.

Module: EYU9XDBT


EYUXU1453W responseOption OPTION is invalid andhas been forced to responseValue

Explanation: The values for responseOption are eitherFEEDBACK or DUPREC. The values of responseValuefor the FEEDBACK option are either QUIET orVERBOSE. The values of responseValue for the DUPRECoption are SKIP, OVERWRITE or REJECT. For moreinformation, see the CICSPlex SM ApplicationProgramming Reference manual.


User response: None

Module: EYU9XDBT


EYUXU1454E ModelType the model record isinvalid, and has been ignored

Explanation: The model record is invalid.




User response: None

Module: EYU9XDBT


EYUXU1456E ResourceType name is invalid

Explanation: You have tried to define a CICSPlex,region or group with an invalid name, that is, a namethat does not follow the CICSPlex SM namingstandards.

System action: The program rejects the rest of thecommand stream and terminate with return code 8.

User response: You should supply a name thatfollows the CICSPlex SM naming standards.

Module: EYU9XDBT


EYUXU0200E Failure action input file (dsname) -reason code (code)

Explanation: A failure occurred during allocationprocessing of the specified batched repository inputfile, where:

action Identifies the action being performed as eitherallocating or unallocating.

dsname Is the name of the data set that was beingprocessed.

code Is the reason code returned from the MVSdynamic allocation call.

System action: The batched repository run terminates.

User response: Refer to the MVS ApplicationDevelopment Guide: Authorized Assembler LanguagePrograms for an explanation of the reason code returnedby dynamic allocation. Correct the problem andresubmit the batched repository job.

Module: EYU0XDBI

Destination: SYSOUT

EYUXU0201E Failure action input file (dsname) -return code (code)

Explanation: A failure occurred during theinput/output processing of the specified batchedrepository input file, where:

action Identifies the action being performed asopening, reading, or closing.


code Is the return code from the MVS BSAM call.

Note: A return code of zero (0) means anabend occurred during MVS input/outputprocessing. When the batchedrepository-update facility intercepts an abend,a return code cannot be set.


User response: Check the job log of the appropriateCMAS for MVS messages related to the problem. Thenrefer to the MVS Messages and Codes manual for anexplanation of those messages.

Correct the problem and resubmit the batchedrepository job.

Module: EYU0XDBI

Destination: SYSOUT

EYUXU0202E Insufficient storage to build typebuffer

Explanation: A buffer of the specified type, which isrequired for the batched repository facility, could not becreated because of a GETMAIN failure, where:

type Identifies the type of buffer that could not becreated as either input or parser.


User response: Increase the region size of the CMASunder which the batched repository-update facility isrunning. The CMAS is indicated by the context of theBATCHREP view. Resubmit the job.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0203E Method failure in (module) - response(respcode) - reason (rcode)

Explanation: A failure occurred during execution ofthe specified CICSPlex SM module by the batchedrepository facility, where:

module Is the name of the module that failed.

respcodeIs the response code returned by the module.

rcode Is the reason code returned by the module.

System action: The batched repository run terminates.User trace records are written to the CICS trace dataset.


v batched repository process report

v EYULOG

v CICS trace data set

Module: EYU0XDBM

Destination: SYSOUT



EYUXU0204E Utility parmtype (parmname) too long

Explanation: The length of a parameter used as inputto the batched repository facility was too long, where:

parmtypeIdentifies the type of parameter as one of thefollowing:

Type Length

Command7 characters or less

Object 8 characters or less

Keyword12 characters or less

parmnameIs the name of the parameter that was toolong.

System action: If the input file was being executed,further processing is limited to syntax checking. If theinput file was being checked, the run continues.

User response: Correct the input parameter andresubmit the batched repository job.

Module: EYU0XDBP

Destination: SYSOUT

EYUXU0205E Value clause missing followingparameter (parmname)

Explanation: No value was found for the specifiedparameter, where:

parmnameIs the name of the parameter for which novalue was found.


User response: Correct the parameter and resubmitthe batched repository job.

Module: EYU0XDBP

Destination: SYSOUT

EYUXU0206E Invalid syntax following parameter(parmname)

Explanation: In the batched repository input file,either a parameter was specified incorrectly, or therewas no semicolon delimiter following the lastparameter in a control statement.

parmnameIs the name of the parameter that wasincorrect.

System action: If the input file was being executed,further processing is limited to syntax checking. If the

input file was being checked, the run continues.


Module: EYU0XDBP

Destination: SYSOUT

EYUXU0207E Parser buffer error

Explanation: The input stream exceeded the limits ofthe batched repository parser buffer. The most likelycause of this error is that a command was not properlydelimited with a semicolon (;). The parser continuestrying to build a command block until it encounters acommand delimiter.

System action: Processing of the current commandterminates. If the input file was being executed, furtherprocessing is limited to syntax checking. If the inputfile was being checked, the run continues.

User response: Check each line of command input fora delimiter. Correct any errors and resubmit thebatched repository job.

Module: EYU0XDBP

Destination: SYSOUT

EYUXU0208E Invalid Context (context) for executionof (command)

Explanation: The specified context is not appropriatefor processing of the specified batched repositorycommand, where:

context Identifies the CMAS or CICSplex that wasspecified on the CONTEXT command. Notethat if CONTEXT is used with no parameter,the local CMAS (that is, the CMAS underwhich the repository facility is running) isassumed.

commandIs the name of the command that could not beprocessed.


User response: Check the last CONTEXT commandbefore the command statement. Make sure it specifiesan appropriate context (either the local CMAS or aCICSplex) for the command being processed. Correctany errors and resubmit the batched repository job.

Module: EYU0XDBM

Destination: SYSOUT



EYUXU0209E Maintenance point not active forContext (plexname)

Explanation: The specified CICSplex was named asthe context for subsequent commands. However, eitherthe maintenance point CMAS for that CICSplex is notactive, or the context does not name a CICSplex. Datarepository records cannot be updated for a CMAS thatis not active.

System action: Processing of the current commandterminates. Further processing is limited to syntaxchecking.

User response: Make sure the CICSplex name wasspecified correctly on the CONTEXT command. If itwas and you expected the maintenance point CMASfor that CICSplex to be active, investigate why it is not.Once the required CMAS is active, resubmit thebatched repository job.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0210E Invalid record attribute for batch inputfile (dsname)

Explanation: Some attribute of the records in thespecified batched repository input file is invalid, where:

attributeIndicates whether it is the record length or therecord format that is invalid. Input to thebatched repository facility must be supplied as80-byte records in a fixed blocked format.



User response: Correct the input file and resubmit thebatched repository job.

Module: EYU0XDBI

Destination: SYSOUT

EYUXU0211E Context (context name) not found

Explanation: The context name specified on theCONTEXT command either is not the name of the localCMAS or is the name of a CICSplex that has not beendefined to CICSPlex SM.


User response: Make sure the specified context nameis either the name of the local CMAS or the name of aCICSplex that has been defined to CICSPlex SM. Usethe CPLEXDEF view to verify that the CICSplex hasbeen defined to CICSPlex SM. Correct any errors and

resubmit the batched repository job.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0211E Context (context name) not found

Explanation: The context name specified on theCONTEXT command either is not the name of the localCMAS or is the name of a CICSplex that has not beendefined to CICSPlex SM.


User response: Make sure the specified context nameis either the name of the local CMAS or the name of aCICSplex that has been defined to CICSPlex SM. Usethe CPLEXDEF view to verify that the CICSplex hasbeen defined to CICSPlex SM. Correct any errors andresubmit the batched repository job.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0213E Invalid parmtype (parmname)

Explanation: A parameter in the batched repositoryinput file was specified incorrectly.

parmtypeIdentifies the type of parameter as eithercommand or object.

parmnameIs the name of the parameter that was invalid.



Module: EYU0XDBS

Destination: SYSOUT

EYUXU0214E Object (objname) may not be referencedby batch utility

Explanation: The specified resource object is not onethat can be processed by the batched repository facility,where objname identifies the resource object that wasspecified.


User response: Remove all references to the specified



object from the batched repository input file andresubmit the job. For a list of resource objects that canbe processed by the batched repository facility, see theCICSPlex System Manager Administration manual.

Module: EYU0XDBS

Destination: SYSOUT

EYUXU0215E Invalid value (parmvalue) followingparameter (parmname)

Explanation: A parameter value in the batchedrepository input file was specified incorrectly, where:

parmvalueIs the value that was specified.

parmnameIs the name of the parameter for which thevalue is invalid.



Module: EYU0XDBS

Destination: SYSOUT

EYUXU0216E Required parameter (parmname)missing

Explanation: A keyword parameter that is required bythe batched repository facility was not supplied.


User response: Refer to theCICSPlex System ManagerAdministration manual and the CICSPlex System ManagerResource Tables Reference Vol 1 for a discussion of theparameters required by the batched repository facility.Then correct any errors and resubmit the batchedrepository job.

Module: EYU0XDBS

Destination: SYSOUT

EYUXU0217E Conflicting parameter (parmname)supplied

Explanation: A parameter was specified in the batchedrepository input file that conflicts with anotherparameter, where: parmname is the name of theconflicting parameter.

System action: Processing of the current commandterminates. If the input file was being executed, furtherprocessing is limited to syntax checking. If the input

file was being checked, the run continues.

User response: Refer to the CICSPlex System ManagerAdministration manual and the CICSPlex System ManagerResource Tables Reference Vol 1 for a discussion of theparameters required by the batched repository facility.Remove the conflicting parameter from the batchedrepository input file, and resubmit the job.

Module: EYU0XDBS

Destination: SYSOUT

EYUXU0218I Batch type request complete - Status(status) - Associated fields (fielda), (fieldb)

Explanation: Processing of the specified batchedrepository request has been completed, where:

type Identifies the type of request that wasprocessed as one of the following: CREATE,UPDATE, LIST, DUMP, REMOVE, MAPLEFT,or MAPRIGHT.

status Indicates the status of the request'scompletion.

fielda and fieldbAre fields which are in error when the staus isnot OK. Additional fields are included inmessage EYUXU0240I which is a continuationof this message.

System action: Processing continues. However, astatus which is not OK causes further processing to belimited to syntax checking.

User response: If the status is OK, no action isrequired. Otherwise, correct the indicated condition andresubmit the batch stream for execution. Status codesother than OK depend on the resource table beingmanipulated and are self-explanatory. Please refer tothe CICSPlex System Manager Resource Tables ReferenceVol 1 manual for valid input.

Module: EYU0XDBR

Destination: SYSOUT

EYUXU0219E Batch type request failed - Response(respcode) - Reason (rcode)

Explanation: Processing of the specified batchedrepository request failed, where:

type Identifies the type of request that failed as oneof the following: CREATE, UPDATE, LIST,DUMP, or REMOVE.

respcodeIs the response code returned by the batchedrepository facility.

rcode Is the reason code returned by the batchedrepository facility.

System action: Further processing is limited to syntax



checking. User trace records are written to the CICStrace data set.


v batched repository input file

v batched repository process report

v CICS trace data set

Module: EYU0XDBR

Destination: SYSOUT

EYUXU0220E Invalid record key for update process

Explanation: The requested repository record selectedfor UPDATE processing was not found on the datarepository.

System action: Further processing is limited to syntaxchecking.

User response: Make sure the correct record wasspecified, and resubmit the batched repository job.

Module: EYU0XDBI

Destination: SYSOUT

EYUXU0221E Failure action Batch Utility Spool File -Reason (rcode)

Explanation: A failure occurred while processing thebatched repository output spool file, where:

action Identifies the action being performed as eitheropening, writing, or closing.

rcode Indicates the reason for the failure as one ofthe following:

v Allocation Failure

v Invalid Class Value

v Invalid Output Record Length

v Unidentified Node/User Combination

v Storage GETMAIN Error

v Storage FREEMAIN Error

v Unsupported Language

v Unsupported Function

v UserId Missing

v Node Missing

v From Missing

v Invalid Keep/Delete

v Input/Output Missing

v CICS SSI Already Enabled

v No Subsystem Present

v Interface Being Disabled

v Interface Stopped

v Data Set Not Open

v Open Macro Failure

v Internal Spool Error

v VSAM SHOWCB Failure

v JES Thread Unavailable

v Spool In Use by Another Task

v Spool In Use by Current Task

v MVS Interface Failure


User response: Correct the condition indicated byrcode and resubmit the batched repository job.

Module: EYU0XDBO

Destination: EYULOG

EYUXU0222E Parameter (parmname) invalid forcmd/obj (cmd/objname)

Explanation: The indicated parameter is not valid foruse during the current processing. If obj/cmd is 'object'the parameter is not valid with the resource tableindicated by cmd/obj name. If obj/cmd is 'command' theparameter is valid for the resource table, but not validduring the command process indicated by cmd/objname.


User response: Make sure the correct object orcommand was specified and resubmit the batchedrepository job.

Module: EYU0XDBS

Destination: SYSOUT

EYUXU0223E Command (cmdname) not valid forobject (objname)

Explanation: The indicated command is not valid foruse when processing the indicated resource table.


User response: Make sure the correct object orcommand was specified and resubmit the batchedrepository job.

Module: EYU0XDBF

Destination: SYSOUT

EYUXU0224E Unexpected end of file encountered

Explanation: While processing the input stream,end-of-file was encountered before a commanddelimiter was detected.

System action: Batch stream processing is terminated.

User response: Make sure the last command isproperly terminated and the brackets in the commands



are properly balanced, then resubmit the batchedrepository job.

Module: EYU0XDBP

Destination: SYSOUT

EYUXU0225E Duplicate parameter (parmname)encountered

Explanation: While processing the input stream, aresource table parameter was encountered that hadalready been processed.

System action: Processing of the current command isterminated. If the input file was being executed, furtherprocessing is limited to syntax checking. If the inputfile was being checked, the run continues.

User response: Check for duplicate parameters in eachcommand, and make sure all commands are properlyterminated. Correct any errors and resubmit thebatched repository job.

Module: EYU0XDBP

Destination: SYSOUT

EYUXU0226E A previous error has causedincomplete processing to occur.

Explanation: An error which had occurred earlier inthe input stream caused the batch utility to not fullyprocess. This message is issued at end of process toinsure users are aware of any error conditions whichhave occurred during execution run processing.


User response: Examine output from batchedrepository job for prior messages indicating the causeof failure.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0227I There is no data which satisfies yourrequest.

Explanation: A MAPLEFT or MAPRIGHT request wasincluded in the batched repository input file, but theobject that you asked to map does not exist. Thismessage appears immediately after the MAPLEFT orMAPRIGHT statement in the batched repository outputfile.



Module: EYU0XDBZ

Destination: SYSOUT

EYUXU0228I Invalid values encountered whileformatting resource table.

Explanation: One or more invalid data values wereencountered while processing a BATCHREP DUMP orLIST command.

System action: Further processing is limited to syntaxchecking.

User response: Invalid attribute values are formattedas "********". Correct any invalid values using the APIor BATCHREP UPDATE command and resubmit thebatched repository job.

Module: EYU0XDBR

Destination: SYSOUT

EYUXU0229E OUTPUT statement must be the firstinput to batched repository

Explanation: If you include an OUTPUT controlstatement in the batched repository input stream, theOUTPUT statement must come first.

System action: The batched repository run continues.Output will continue to be written to the originaltarget.

User response: Place the OUTPUT statement at thebeginning of the batched repository input stream.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0230E OUTPUT must be followed by thekeyword LISTING or DATASET

Explanation: You specified a keyword other thanLISTING or DATASET on the OUTPUT controlstatement. These are the only supported keywords.


User response: Correct the OUTPUT controlstatement.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0231E OUTPUT DSNAME only supportsparameters DSNAME and INQUOTES

Explanation: You specified a parameter other thanDSNAME or INQUOTES on an OUTPUT DSNAMEcontrol statement. These are the only valid parameters.


User response: Correct the OUTPUT controlstatement.

Module: EYU0XDBM

Destination: SYSOUT



EYUXU0232E DSNAME does not specify a validdata set name

Explanation: The DSNAME parameter did not specifya valid data set name. Data set names must not bemore than 44 bytes long. They must consist of groupsfrom 1 to 8 characters separated by full stops.DSNAME may include an optional member nameplaced following the data set name. The member namemust be enclosed in parentheses and must not be morethan 8 characters long. The data set name and membername of the batched repository output data set mustnot be the same as the data set name and membername of the batched repository input data set.


User response: Correct the DSNAME parameter of theOUTPUT statement.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0233E INQUOTES must take the value YESor NO

Explanation: You specified a value other than YES orNO as the value of the parameter INQUOTES.


User response: Correct the INQUOTES parameter onthe OUTPUT control statement.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0234E Failure action output file (dsname) -return code (code)

Explanation: A failure occurred during theinput/output processing of the specified batchedrepository output file, where:

action Identifies the action being performed asopening, reading, or closing.


code Is the return code from the MVS BSAM call.

Note: A return code of zero (0) means anabend occurred during MVS input/outputprocessing. When the batchedrepository-update facility intercepts an abend,a return code cannot be set.


User response: Check the job log of the appropriateCMAS for MVS messages related to the problem. Thenrefer to the MVS Messages and Codes manual for anexplanation of those messages.

Correct the problem and resubmit the batchedrepository job.

Module: EYU0XDBW

Destination: SYSOUT

EYUXU0235E Invalid record length nnn for batchoutput file

Explanation: The record length (LRECL) for theoutput file used by the batched data repository is not80 bytes.


User response: Use an output data set with 80 byterecords.

Module: EYU0XDBW

Destination: SYSOUT

EYUXU0236E Failure action output file (dsname) -reason code (code)

Explanation: A failure occurred during allocationprocessing of the specified batched repository outputfile, where:

action Identifies the action being performed as eitherallocating or unallocating.


code Is the reason code returned from the MVSdynamic allocation call.


User response: Refer to the MVS ApplicationDevelopment Guide: Authorized Assembler LanguagePrograms for an explanation of the reason code returnedby dynamic allocation. Correct the problem andresubmit the batched repository job.

Module: EYU0XDBW

Destination: SYSOUT

EYUXU0237E Syntax error. Unbalanced quotes onBATCHREP statement

Explanation: A batched repository parameter valuebegan with a quote but did not end with a quote. If thefirst character (the one immediately following the leftparenthesis) of a parameter value is a quote, then thelast character (the one immediately preceding the rightparenthesis) must also be a quote, and any imbeddedquotes within the parameter value must occur in pairs.


User response: Correct the BATCHREP controlstatement

Module: EYU0XDBP



Destination: SYSOUT

EYUXU0238W Invalid set-attributes have beenignored

Explanation: The MP CMAS has shipped a ResourceAssignment (RASGNDEF) to a CMAS running a lowerlevel of CICSPlex SM, as part of repositorysynchronization. The RASGNDEF in question containsan Override string that identifies an attribute that is notapplicable to the lower level CMAS.

System action: The unknown attribute is ignored, butthe lower level CMAS will issue an exception traceentry to identify the definition attribute that is beingignored. This message will be issued only once in theCMAS job step, regardless of the number of invalidset-attributes detected.

User response: As the system is reporting an attributethat is not applicable to the lower level CMAS, thennormally this message can be ignored. If there is anydoubt as to the integrity of system resources after thismessage is issued, then collect the CMAS AuxiliaryTrace Data Sets and contact your IBM Support Center.

Module: EYU0XDOS


EYUXU0239W Invalid filter-attributes have beenmodified

Explanation: The MP CMAS has shipped a ResourceAssignment (RASGNDEF) to a CMAS running a lowerlevel of CICSPlex SM, as part of repositorysynchronization. The RASGNDEF in question containsa Filter string that identifies an attribute that is notapplicable to the lower level CMAS.

System action: The unknown attribute is modifiedinternally to generate a FALSE condition in the lowerlevel CMAS. An exception trace entry will be taken toidentify the filter-attribute that has been changed. Thismessage will be issued only once in the CMAS job step,regardless of the number of invalid filter-attributesdetected.

User response: The system is reporting an attributetest that is being modified to enable the filter to beexecuted. However, users should be aware that themodified test will be updated to produce anunconditional FALSE state. This means that resourcesthat you would assume to be successfully installed maynot now be defined at their target scopes - particularlyif these invalid filter-attributes are part of a compoundspecification connected with the AND logical operator.If there is any doubt as to the integrity of systemresources after this message is issued, then collect theCMAS Auxiliary Trace Datasets and contact your IBMSupport Center.

Module: EYU0XDOP


EYUXU0240I Additional associated fields (fielda),(fieldb), (fieldc), (fieldd).

Explanation: This is an extension to messageEYUXU0218I which gives up to two associated fields.This message can give up to four more associatedfields. Refer to the explanation for EYUXU0218I formore information.

System action: Refer to the explanation forEYUXU0218I for more information.

User response: Refer to the explanation forEYUXU0218I for more information.

Module: EYU0XDBR

Destination: SYSOUT

EYUXU0241E Invalid syntax for BATCHREPOPTION command.

Explanation: A syntax error was encountered whileparsing an OPTION command. The OPTION commandhas the following form:

OPTION type keyword ^keyword ...]

where:OPTION

is the option typekeyword

are keywords whose form depends upon theoption type being processed.

System action: The batch repository run terminates.

User response: Correct the BATCHREP controlstatement.

Module: EYU0XDBM

Destination: SYSOUT

EYUXU0242E Invalid BATCHREP OPTION cardtype (type).

Explanation: The OPTION command had anunrecognized type. The following option types arecurrently supported:DUPREC

Sets processing option for duplicate recordcondition for the CREATE command.



Module: EYU0XDBM

Destination: SYSOUT

EYUXU0238W • EYUXU0242E


EYUXU0243E Invalid keyword for OPTION (type)(keyword).

Explanation: The OPTION command contained aninvalid keyword , wheretype is the option card typekeyword

is the unrecognized keyword.



Module: EYU0XDBM

Destination: SYSOUT

EYUXU0244E Generic keys are not allowed onremove.

Explanation: A batched repository request was madeto remove a record and a generic key was specified.That is, either a "+" or a "*" was specified in the keyfield. The request failed because remove acts only uponspecific keys.

System action: The batched repository-update requestfails. Further processing is limited to syntax checking.

User response: Correct and resubmit the batchedrepository request.

Module: EYU0XDBX

Destination: SYSOUT

EYUXU0245E Insufficient authority to access outputfile (dsname)

Explanation: The issuer of the BATCHREP commandstream is not authorized to write to the data set namedin the OUTPUT command, where:

dsname Is name of the output data set specified in theBATCHREP OUTPUT command.

System action: The BATCHREP stream is aborted.

User response: Update the OUTPUT command tospecify the name of a data set that the user has theauthority to write to.

Module: EYU0XDBM

Destination: SYSOUT



Chapter 47. EYUXZnnnn messages

EYUXZ0001I Trace Services termination complete

Explanation: The Trace Services subcomponent hasbeen terminated.

System action: CICSPlex SM can no longer issue usertrace records to the CICS trace data set.

User response: None

Module: EYU0XZTM, EYU3XZTM


EYUXZ0002E Filename filename could not be opened.

Explanation: The specified file, which is used by theEYU9XZUT trace format utility, could not be opened,where:

filenameIdentifies the file as SYSIN, TRCEIN, orTRCEOUT.

System action: The trace format utility terminates.

User response: Make sure the JCL contains the properDD statements and the named files exist. Then,resubmit the job. Refer to the CICSPlex System ManagerProblem Determination manual for sample JCL.

Module: EYU9XZUT

Destination: Console, SYSOUT

EYUXZ0003E Component text is not a valid CPSMcomponent.

Explanation: An invalid component ID was specifiedon the COMPID= option of the EYU9XZUT traceformat utility, where:

text Is what was specified.


User response: Correct the component ID and thenresubmit the job. Refer to the CICSPlex System ManagerProblem Determination manual for a list of validcomponent IDs.

Module: EYU9XZUT

Destination: SYSOUT

EYUXZ0004I Please correct and resubmit.

Explanation: This message follows one or moreEYUXZnnnnE messages that describe a problem withthe EYU9XZUT trace format utility.


User response: Correct the problem described inprevious messages and then resubmit the job.

Module: EYU9XZUT

Destination: SYSOUT

EYUXZ0005E Keyword text is not a valid selectioncriteria keyword.

Explanation: An invalid keyword was specified forthe EYU9XZUT trace format utility, where:

text Is what was specified.


User response: Correct the keyword and thenresubmit the job. Refer to the CICSPlex System ManagerProblem Determination manual for a list of validEYU9XZUT options.

Module: EYU9XZUT

Destination: SYSOUT

EYUXZ0006I Option ALL is assumed.

Explanation: No selection criteria were specified withthe EYU9XZUT trace format utility, so all trace recordsin the trace data set are formatted.

System action: Trace formatting continues.


Module: EYU9XZUT

Destination: SYSOUT

EYUXZ0007E Sequence number not numeric

Explanation: Either the sequence number or tasknumber in the input record is not numeric.

System action: The program ignores the record inerror and continues to process other user input.

User response: Correct the problem and then resubmitthe job.

Module: EYU9XZUT

Destination: SYSOUT

EYUXZ0007W Filename filename is required,processing is terminated.

Explanation: The specified file, which is required forthe EYU9XZUT trace format utility, was not available,where:


filenameIdentifies the file as TRCEIN or TRCEOUT.


User response: Make sure the JCL contains the properDD statements and the named files exist. Then,resubmit the job. Refer to the CICSPlex System ManagerProblem Determination manual for sample JCL.

Module: EYU9XZUT

Destination: Console, SYSOUT

EYUXZ0010E Trace Services termination failed

Explanation: An error occurred while attempting toterminate the Trace Services subcomponent.

System action: CICSPlex SM can no longer issue usertrace records to the CICS trace data set. Trace recordsmay have been written to the data set before this erroroccurred.

User response: Examine the exception trace records,and any messages issued prior to this one, to determinethe cause of the problem.

Module: EYU0XZTM


EYUXZ0011E Internal SORT failed - examine SORTmessages for reason.

Explanation: An error occurred while the EYU9XZUTtrace format utility was attempting an internal sortoperation.


User response: Examine any accompanying sortmessages to determine the cause of the problem.Correct the problem and resubmit the job.

Module: EYU9XZUT

Destination: SYSOUT

EYUXZ0012I Time and date will be formatted usingtype time adjustments.

Explanation: EYU9XZUT will format all time anddates using either type CPSM or CVT time adjustments.

CPSM time adjustmentsThe CPSM defined time zone and time zoneoffset for the CMAS or MAS.

CVT time adjustmentsThe time zone offset and leap secondadjustment from the CVT on the system wherethe CMAS or MAS executed.

System action: All time and dates in the formattedtrace records have been adjusted as specified.

User response: None

Module: EYU9XZUT


EYUXZ0013I Time and date formatting has beenswitched to use CPSM timeadjustments, starting with sequencenumber nnnnnnnnnn.

Explanation: Starting with the specified trace recordsequence number nnnnnnnnnn, EYU9XZUT will switchfrom using CVT adjustments to CPSM adjustmentswhen formatting the time and date. Please see thedescription for message EYUXZ0012I for informationabout the different types of time adjustments.

System action: All time and dates in the formattedtrace starting with the specified sequence number havebeen adjusted using the CPSM time zone and timezone offset for the CMAS or MAS.

User response: None

Module: EYU9XZUT


EYUXZ0901 I date time applid A dump of this CMAS,code (dumpcode), has been requested byCMAS (cmasname).

Explanation: A dump of this CMAS, where dumpcodeis the code associated with the dump, has beenrequested by another CMAS, where cmasname is thename of the requesting CMAS. If a dump is taken inthis CMAS, dumpcode will be contained in the title ofthe dump.

System action: A dump is requested of this CMAS. Ifit is successful, it will be followed by messageEYUXZ0910I, containing the title of the dump. If it isnot successful, it will be followed by messageEYUXZ0913E. Processing then continues.

User response: Refer to the job log of the requestingCMAS, which will have issued one of the followingmessages:

EYUXZ0902I , EYUXZ0903I , EYUXZ0904I ,EYUXZ0905I

Then refer to that message description to determinehow to respond.

Module: EYU0XZSD

Message inserts:

1. date

2. time

3. applid

4. dumpcode

5. cmasname


EYUXZ0010E • EYUXZ0901 I


EYUXZ0902 I date time applid This CMAS hasrequested dumps, code (dumpcode), ofthis CMAS and of CMAS (cmasname).

Explanation: A dump of this CMAS and of anotherCMAS that is directly or indirectly connected to it,where cmasname is the name of the connected CMAS,has been requested by this CMAS. A code, dumpcode,has been associated with both dumps and will becontained in the dump title of the dumps.

System action: A dump is requested of this CMASand the CMAS identified as cmasname, which will issuemessage EYUXZ0901I. If the dumps are successful, theywill be followed by message EYUXZ0910I, containingthe title of the dump. If they are not successful, theywill be followed by message EYUXZ0913E. Processingthen continues.

User response: Search the job log of the requestingCMAS for additional messages indicating a problem,referring to those message descriptions to determinehow to respond. If there are no other messages, thencollect the complete job output, auxtrace datasets anddumps from both CMASes, and contact your IBMsupport center.

Module: EYU0XZSD

Message inserts:

1. date

2. time

3. applid

4. dumpcode

5. cmasname


EYUXZ0903 I date time applid This CMAS hasrequested dumps, code (dumpcode), ofthis CMAS and of all CMASesconnected to it.

Explanation: A dump of this CMAS and of allCMASes directly or indirectly connected to it, has beenrequested by this CMAS. A code, dumpcode, has beenassociated with all of the dumps and will be containedin the dump title of the dumps.

System action: A dump is requested of this CMASand all CMASes connected to it. The connectedCMASes will issue message EYUXZ0901I. If the dumpsare successful, they will be followed by messageEYUXZ0910I, containing the title of the dump. If theyare not successful, they will be followed by messageEYUXZ0913E. Processing then continues.

User response: Search the job log of the requestingCMAS for additional messages indicating a problem,referring to those message descriptions to determinehow to respond. If there are no other messages, thencollect the complete job output, auxtrace datasets and

dumps from all CMASes, and contact your IBMsupport center.

Module: EYU0XZSD

Message inserts:

1. date

2. time

3. applid

4. dumpcode


EYUXZ0904 I date time applid This CMAS hasrequested dumps, code (dumpcode), ofthis CMAS and of all CMASesconnected to it that manage CICSplex(plexname).

Explanation: A dump of this CMAS and of allCMASes directly or indirectly connected to it, thatmanage a specific CICSplex, where plexname is thename of the CICSplex, has been requested by thisCMAS. A code, dumpcode, has been associated with allof the dumps and will be contained in the dump titleof the dumps.

System action: A dump is requested of this CMASand all CMASes connected to it that manage CICSplexplexname. The connected CMASes will issue messageEYUXZ0901I. If the dumps are successful, they will befollowed by message EYUXZ0910I, containing the titleof the dump. If they are not successful, they will befollowed by message EYUXZ0913E. Processing thencontinues.

User response: Search the job log of the requestingCMAS for additional messages indicating a problem,referring to those message descriptions to determinehow to respond. If there are no other messages, thencollect the complete job output, auxtrace datasets anddumps from all CMASes, and contact your IBMsupport center.

Module: EYU0XZSD

Message inserts:

1. date

2. time

3. applid

4. dumpcode

5. plexname


EYUXZ0905 I date time applid This CMAS hasrequested dumps, code (dumpcode), ofthis CMAS and of all CMASesconnected to it that manage workload(wkldname) for CICSplex (plexname).

Explanation: A dump of this CMAS and of all

EYUXZ0902 I • EYUXZ0905 I


CMASes directly or indirectly connected to it, thatmanage a specific workload, where wkldname is thename of the workload and where plexname is the nameof the CICSplex it is associated with, has beenrequested by this CMAS. A code, dumpcode, has beenassociated with all of the dumps and will be containedin the dump title of the dumps.

System action: A dump is requested of this CMASand all CMASes connected to it that manage workloadwkldname for CICSplex plexname. The connectedCMASes will issue message EYUXZ0901I. If the dumpsare successful, they will be followed by messageEYUXZ0910I, containing the title of the dump. If theyare not successful, they will be followed by messageEYUXZ0913E. Processing then continues.

User response: Search the job log of the requestingCMAS for additional messages indicating a problem,referring to those message descriptions to determinehow to respond. If there are no other messages, thencollect the complete job output, auxtrace datasets anddumps from all CMASes, and contact your IBMsupport center.

Module: EYU0XZSD

Message inserts:

1. date

2. time

3. applid

4. dumpcode

5. wkldname

6. plexname


EYUXZ0910I applid dump_title

Explanation: This message indicates that an SDUMPhas been requested by CPSM recovery, where:

applid Is the application ID of the CICS system thatrequested the dump.

dump_titleIs the title string passed to the system dumproutine.

System action: An SDUMP has been requested,containing the current region, the ESSS Address Space,and cache data spaces for components accessed in therequesting task.

User response: Collect as much of the followinginformation as possible, and contact your IBM SupportCenter:

v The job log for the job for which the dump wastaken. If the job log is not available, get the systemlog.

v The EYULOG file. If the dump was taken for aCMAS, the EYULOG file for that CMAS. If the dump

was taken for a MAS, the EYULOG of the CMAS towhich the MAS was connected.

v The unformatted SVC dump (SDUMP). The dumptitle in the message can be used to identify therequired dump.

v The AUXTRACE file. If the dump was taken for aMAS, and AUXTRACE was not active in that CICSsystem, then the AUXTRACE file from the CMAS towhich the MAS connected.

Module: EYU0XZPT, EYU0XZSD


EYUXZ0911W method dump suppressed becauseESDUMP is set to NEVER

Explanation: An on demand request for an SVC dumphas been suppressed because the value of the ESDUMPEYUPARM is NEVER, where:

method identifies the CPSM method that suppressedthe dump:

EYU0XZPT

EYU0XZSD



Module: EYU0XZPT, EYU0XZSD


EYUXZ0913 E date time applid A request to take anSDUMPX failed with return code retcde,reason code reason.

Explanation: An SDUMPX request issued by this CICSregion failed to complete successfully.

retcde Is the hexadecimal return code returned by theSDUMPX macro.

reason Is the hexadecimal reason code returned bythe SDUMPX macro.

System action: This message is issued and the dumpis not taken. Processing then continues.

User response: Refer to the z/OS MVS Programming:Authorized Assembler Services Reference manual thatdocuments the SDUMPX macro, to determine themeaning of the return code and reason code.

Module: EYU0XZPT

EYU0XZSD

EYUXZ0910I • EYUXZ0913 E


Message inserts:

1. date

2. time

3. applid

4. retcde

5. reason

Destination: Console, TDQ


Chapter 48. Debugging transaction messages

These messages are issued by the COD0 and CODB debugging transactions. If youreceive one of these messages and you are not working with an IBM supportrepresentative at the time, collect the following information and contact your IBMSupport Center:v Error messagesv Transaction dumpv Other appropriate diagnostic information

COD0 messagesCOD0 messages

COD0 IS ABENDING! EIBFN: fcode RESP1: resp1code RESP2: resp2code RC:rcode The COD0 debugger transaction encountered an error from which it could

not recover. The transaction terminates and this message is issued to theCICS terminal. In order to protect the CICSPlex SM control block chains,no CICS abend occurs.

The message contains the following diagnostic information:

fcode The last CICS command function code returned by DFHEIBFN.

resp1codeThe last RESP code returned by a CICS command.

resp2codeThe last RESP2 code returned by a CICS command.

rcode The reason code, which can be one of the following:

01 The DBG1 internal transaction was issued instead ofCOD0. Use the COD0 transaction to start the debugger.

02 A CICS error occurred while requesting information aboutthe terminal.

03 CICS reported a non-3270 style terminal.

04 The terminal width is not 80 characters. The debugger runsonly in 80-character mode (Models 2 - 4).

06 Module DBG9DBG3, which is used by the COD0 ATTACHcommand, could not be loaded by an MVS LOADcommand.

07 Internal error. The table of started and attached tasksindicated an entry was available, but none could be found.

11 A CICS WRITE TS command, which is used to list startedand attached tasks and allocated resources, failed.

12 A CICS GETMAIN command failed.

13 A CICS PUSH HANDLE command failed.

14 A CICS POP HANDLE command failed.


15 Internal error. A stack frame request was issued, but itwould have exceeded the maximum number of framesallowed.

16 A CICS HANDLE ABEND command failed.

17 Internal error. A request was issued to add a line to aterminal buffer, but it would have exceeded the maximumnumber of lines allowed.

18 Internal error. The calculation of a terminal buffer size wasincorrect.

20 A CICS CONVERSE command failed.

21 Internal error. An attribute that was expected in theterminal buffer could not be found.

22 A create cache method call, which is used to create a kernellinkage cache, failed.

23 Internal error. There was a mismatch between the numberof fields on a panel and the number of fields passed to thepanel processor.

24 Internal error. There was a mismatch between the numberof fields in a panel header and the number found on thepanel.

25 Internal error. A requested panel could not be found.

26 A CICS FREEMAIN command failed.

27 Internal error. A message number could not be found inthe message table.

28 Program EYU9XLCI, which is required by the COD0ATTACH command, was not loaded during CMASinitialization and could not be loaded by an MVS LOADcommand.

29 Either the CICSPlex SM XLWA could not be found or itseyecatcher could not be validated.

30 Internal error. A field in an XLTD (method table) entry wasnot either one or two bytes long, as expected.

31 Module DBG9DBG2, which is used by the COD0 STARTcommand, could not be loaded by an MVS LOADcommand.

32 In the output of a COD0 ATTACH command, the length ofa message argument list (MAL) was found to be longerthan 256 bytes.

CODB messagesThese messages are displayed in the MSG==> field at the bottom of the CODBdisplay panel.

THE SPECIFIED ALET IS NOT A VALID ONE.The value entered in the ALET==> field, or selected by PF22, is not a validALET.


DISPLAY COMMAND IGNORED, CURSOR NOT ON VALID FIELD.PF9, PF10, or PF22 was pressed, but the cursor was not on a field thatcould be used to develop a display address.

TO ALTER MEMORY, PF11.The memory display portion of the screen was modified. Press PF11 tomake the change take effect.

MEMORY CHANGED SINCE DISPLAY, PF11 TO ALTER.The data at the memory location to be altered has been modified since itwas displayed. Press PF11 to make the change take effect.

DATA IS FETCH PROTECTED AT LOCATION addressAn attempt was made to display memory in protected storage. If theproblem was caused by scrolling an existing display, the display isautomatically adjusted. address identifies the storage location that can notbe displayed.

DATA IS STORE PROTECTED AT LOCATION addressAn attempt was made to alter protected memory. address identifies thestorage location that can not be altered.

'NEXT' PFKEY NOT ACTIVE FOR CURRENT COMMAND.The current command or display mode (as indicated by the ADDR field,PF9, PF10, or PF22), does not support the NEXT function.

'PREVIOUS' PFKEY NOT ACTIVE FOR CURRENT COMMAND.The current command or display mode (as indicated by the ADDR field,PF9, PF10, or PF22), does not support the PREVIOUS function.

CURSOR NOT ON VALID QUEUE/CACHE TOKEN.PF13 was pressed, but the data pointed to by the cursor is not a validqueue token.

REQUESTED QUEUE/CACHE TOKEN CANNOT BE FOUND.The queue defined by the queue token no longer exists.

END OF QUEUE/CACHE OR QUEUE/CACHE EMPTY.Either the queue is empty, or the end of the queue had been reached whenthe NEXT function was requested.

'TOP' NOT ACTIVE FOR CURRENT DISPLAY.The current command or display mode (as indicated by the ADDR field,PF9, PF10, or PF22), does not support the TOP function.

'BOTTOM' NOT ACTIVE FOR CURRENT DISPLAY.The current command or display mode (as indicated by the ADDR field,PF9, PF10, or PF22), does not support the BOTTOM function.

AN UNEXPECTED ABEND OCCURRED, DUMP TAKEN, AND RESTARTINGTHE TRANSACTION.

The CODB transaction terminates and is automatically restarted. Thisproblem can be caused by corrupted CICSPlex SM control blocks or chains.

CMAS shutdown transaction messagesThese messages are issued by the CICSPlex SM shutdown transaction COSD. Theyare informational messages only, issued by the terminal user. No user action isrequired.

CMASSTOP SUCCESSFULLY INITIATEDThe CMAS shutdown process has begun.

Chapter 48. Debugging transaction messages 307

CMASSTOP REQUESTED, SYSTEM NOT A CMAS - IGNOREDThe COSD transaction may only be used to shut down a CMAS. Thetransaction is ignored.


Chapter 49. Abend and dump codes

When abnormal conditions occur, CICSPlex SM attempts to recover in an orderlymanner and continue with normal processing. Occasionally conditions arise thatprevent or preclude such recovery and a task, component, or system mayterminate. If this occurs, one of the following abend or dump codes is issued:

CICS abend and dump codesIf you need to contact your IBM Support Center in response to any of these codes,gather as much of the following diagnostic information as possible:v Job log from the MAS.v EYULOG from the CMAS to which the MAS was connected or was attempting

to connect.v CICS TRANDUMP data set from the MAS. Use the CICS DFHDUP utility to

format the dump data set.v CICS AUXTRACE data set from the MAS, if available. Use the EYU9XZUT trace

format utility to format the data set, as described in CICSPlex System ManagerProblem Determination. Also keep a copy of the unformatted trace data set.

EYUI

Explanation: A non-recoverable error occurred duringinitialization.


User response: Examine the MAS job log for anymessages that might indicate a problem. If suchmessages exist, follow the instructions associated withthose messages and then restart the MAS. If nomessages exist, or if no appropriate action is indicated,gather the specified diagnostic information and contactyour IBM support center.

Module: EYU9XLEV

EYUK

Explanation: Either a non-recoverable abend occurredduring MAS initialization or a proper environment didnot exist when attempting to recover from an abend.


System action: If this abend occurred duringinitialization, MAS initialization terminates. The CICSsystem continues to run normally, but it is not knownto CICSPlex SM.

User response: Examine the MAS job log for anymessages that might indicate a problem. If suchmessages exist, follow the instructions associated with

those messages and then restart the MAS, if necessary.If no messages exist, or if no appropriate action isindicated, gather the specified diagnostic informationand contact your IBM support center.

Module: EYU9XLRV

EYUO

Explanation: The environment create routine in aCMAS or MAS was called invalidly. The calling processwas not a CICSPlex SM service.

System action: CICS system processing continues.

User response: Make sure that:

v No site-written programs are attempting to callCICSPlex SM environment create.

v Users are not attempting to use CICSPlex SMTRANIDS directly, either from a terminal or via anEXEC CICS START.

If neither of these conditions exists, gather the specifieddiagnostic information and contact your IBM supportcenter.

Module: EYU9XLOP

EYUR

Explanation: An error occurred while attempting torecover from an abend.

System action: The failing task terminates. The CICSsystem continues to run normally, but it may not beknown to CICSPlex SM.


User response: Examine the MAS job log for anymessages that might indicate a problem. If suchmessages exist, follow the instructions associated withthose messages and then restart the MAS, if necessary.If no messages exist, or if no appropriate action isindicated, gather the specified diagnostic informationand contact your IBM support center.

Module: EYU9XLRV

EYUV

Explanation: The Web User Interface environmentcreate routine in a CMAS or MAS was called invalidly.The calling process was not a CICSPlex SM service.

System action: The failing task terminates. Atransaction dump is taken. CICS system processingcontinues.

User response: Make sure that:

v No site-written programs are attempting to callCICSPlex SM Web User Interface environment create.

v Users are not attempting to use CICSPlex SMTRANIDS directly, either from a terminal or via anEXEC CICS START.

If neither of these conditions exists, contact your IBMSupport Center.

Module: EYU0VGIN

EYUX

Explanation: An exception condition was detected in aremote MAS but a full CICSPlex SM exception tracecould not be written at that time. This condition is notnecessarily a failure in the application, but thereporting of an exception condition, which is usuallythe result of communications problems.Communications exceptions cannot be sent to theconnected CMAS.

System action: A transaction dump is taken todocument the exception. Task execution continues,taking the appropriate action for the exceptioncondition.

User response: Examine the MAS and CMAS job logsfor any messages that might indicate a problem,especially for those related to the communicationsnetwork. If such messages exist, follow the instructionsassociated with those messages. If no messages exist, orif no appropriate action is indicated, gather thespecified diagnostic information and contact your IBMsupport center.

Module: EYU9XLEV, EYU9XLOP

EYUY

Explanation: A CMAS-to-CMAS connection hasterminated abnormally. The receive task component ofthe connection has tried to terminate as cleanly aspossible, but it has detected that it is still in a networkreceive state. This makes it impossible for it toterminate, without CICS generating an additionaltransaction abend describing this apparent transmissionstate discrepancy. However, this network state cannotbe reset because of the reported connection failure. Thisabend is issued to preempt the normal CICS abendcode related to these network state errors.

System action: The CPI-C or MRO receive task shouldnow end completely with this abend. When all taskcomponents for the connection have terminated, thefirst speaker CMAS of the connection pair shouldattempt to reestablish the connection.

User response: Check the CMAS job log, EYULOG,and CICS message log for previous failures or errorconditions and follow the User Response for thesemessages.

Module: EYU0CLCT, EYU0CLCU, EYU0CLMT,EYU0CLMU

EYUV • EYUY


Uxxxx abend codesIn response to any of the Uxxxx abend codes, gather any of the information that isavailable from the list shown in “CICS abend and dump codes” on page 309 andcontact your IBM Support Center.

U100

Explanation: An ISPF interface failure has occurred.

U1600

Explanation: A PC has issued a call to an unavailableservice.

U1700 through U1798

Explanation: Recovery Manager abends.

U1799

Explanation: A should-not-occur condition hasoccurred.

U1800

Explanation: Indicates that a C housekeeping failurehas occurred.

U1801

Explanation: A failure has occurred in GSIhousekeeping.

U1802

Explanation: A failure has occurred in GSI routerhousekeeping.

U1803

Explanation: A transaction manager housekeepingfailure has occurred.

U1804

Explanation: A failure has occurred in the SAS/Cresident module.

U1899

Explanation: System environmental conditions havecaused a failure with DYNAEC EPD.

U1900

Explanation: A failure has occurred with the storagemanager.

U3000

Explanation: An error has occurred in a built inservice function routine.

U4000

Explanation: Indicates that a pseudo GSI servicefailure has occurred.

Explanation: An unrecoverable control task error hasoccurred.

U4090

Explanation: A server or application initializationerror has occurred.

U4095

Explanation: A task has been terminated by PGTERM.

System dump codesIn response to any of these dump codes, gather the following diagnosticinformation and contact your IBM Support Center:v Job log and EYULOG from the CMAS.v Unformatted SVC dump (SDUMP). Have access to IPCS.v CICS AUXTRACE data set from the CMAS. Use the EYU9XZUT trace format

utility to format the data set, as described in the CICSPlex System ManagerProblem Determination manual. Also keep a copy of the unformatted trace dataset.

EYUXL001

Explanation: The initialization process failed.

System action: initialization terminates.

Module: EYU9XLEV

U100 • EYUXL001

Chapter 49. Abend and dump codes 311

EYUXL002

Explanation: The recovery routine was entered duringinitialization.

System action: initialization terminates.

Module: EYU9XLRV

EYUXL003

Explanation: The recovery routine was entered, butcould not successfully recover from the abend.

System action: processing terminates.

Module: EYU9XLRV

EYUXL002 • EYUXL003


Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply in the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore this statement may not applyto you.

This publication could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Licensees of this program who want to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact IBM United KingdomLaboratories, MP151, Hursley Park, Winchester, Hampshire, England, SO21 2JN.


Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Programming License Agreement, or any equivalent agreementbetween us.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at Copyright andtrademark information at www.ibm.com/legal/copytrade.shtml.

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Bibliography

CICS books for CICS Transaction Server for z/OSGeneral

CICS Transaction Server for z/OS Program Directory, GI13-0565CICS Transaction Server for z/OS What's New, GC34-7192CICS Transaction Server for z/OS Upgrading from CICS TS Version 3.1, GC34-7188CICS Transaction Server for z/OS Upgrading from CICS TS Version 3.2, GC34-7189CICS Transaction Server for z/OS Upgrading from CICS TS Version 4.1, GC34-7190CICS Transaction Server for z/OS Installation Guide, GC34-7171

Access to CICSCICS Internet Guide, SC34-7173CICS Web Services Guide, SC34-7191

AdministrationCICS System Definition Guide, SC34-7185CICS Customization Guide, SC34-7161CICS Resource Definition Guide, SC34-7181CICS Operations and Utilities Guide, SC34-7213CICS RACF Security Guide, SC34-7179CICS Supplied Transactions, SC34-7184

ProgrammingCICS Application Programming Guide, SC34-7158CICS Application Programming Reference, SC34-7159CICS System Programming Reference, SC34-7186CICS Front End Programming Interface User's Guide, SC34-7169CICS C++ OO Class Libraries, SC34-7162CICS Distributed Transaction Programming Guide, SC34-7167CICS Business Transaction Services, SC34-7160Java Applications in CICS, SC34-7174

DiagnosisCICS Problem Determination Guide, GC34-7178CICS Performance Guide, SC34-7177CICS Messages and Codes Vol 1, GC34-7175CICS Messages and Codes Vol 2, GC34-7176CICS Diagnosis Reference, GC34-7166CICS Recovery and Restart Guide, SC34-7180CICS Data Areas, GC34-7163CICS Trace Entries, SC34-7187CICS Debugging Tools Interfaces Reference, GC34-7165

CommunicationCICS Intercommunication Guide, SC34-7172CICS External Interfaces Guide, SC34-7168

DatabasesCICS DB2 Guide, SC34-7164CICS IMS Database Control Guide, SC34-7170


CICS Shared Data Tables Guide, SC34-7182

CICSPlex SM books for CICS Transaction Server for z/OSGeneral

CICSPlex SM Concepts and Planning, SC34-7196CICSPlex SM Web User Interface Guide, SC34-7214

Administration and ManagementCICSPlex SM Administration, SC34-7193CICSPlex SM Operations Views Reference, SC34-7202CICSPlex SM Monitor Views Reference, SC34-7200CICSPlex SM Managing Workloads, SC34-7199CICSPlex SM Managing Resource Usage, SC34-7198CICSPlex SM Managing Business Applications, SC34-7197

ProgrammingCICSPlex SM Application Programming Guide, SC34-7194CICSPlex SM Application Programming Reference, SC34-7195

DiagnosisCICSPlex SM Resource Tables Reference Vol 1, SC34-7204CICSPlex SM Resource Tables Reference Vol 2, SC34-7205CICSPlex SM Messages and Codes, GC34-7201CICSPlex SM Problem Determination, GC34-7203

Other CICS publicationsThe following publications contain further information about CICS, but are notprovided as part of CICS Transaction Server for z/OS, Version 4 Release 2.

Designing and Programming CICS Applications, SR23-9692CICS Application Migration Aid Guide, SC33-0768CICS Family: API Structure, SC33-1007CICS Family: Client/Server Programming, SC33-1435CICS Family: Interproduct Communication, SC34-6853CICS Family: Communicating from CICS on System/390, SC34-6854CICS Transaction Gateway for z/OS Administration, SC34-5528CICS Family: General Information, GC33-0155CICS 4.1 Sample Applications Guide, SC33-1173CICS/ESA 3.3 XRF Guide , SC33-0661


Accessibility

Accessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use software products successfully.

You can perform most tasks required to set up, run, and maintain your CICSsystem in one of these ways:v using a 3270 emulator logged on to CICSv using a 3270 emulator logged on to TSOv using a 3270 emulator as an MVS system console

IBM Personal Communications provides 3270 emulation with accessibility featuresfor people with disabilities. You can use this product to provide the accessibilityfeatures you need in your CICS system.


Index

Ttrademarks 314


Readers’ Comments — We'd Like to Hear from You

CICS Transaction Server for z/OSVersion 4 Release 2CICSPlex SM Messages and Codes

Publication No. GC34-7201-01

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Submit your comments using one of these channels:v Send your comments to the address on the reverse side of this form.v Send a fax to the following number: +44 1962 816151v Send your comments via email to: [email protected]

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. Email address

Readers’ Comments — We'd Like to Hear from YouGC34-7201-01

GC34-7201-01

IBM®Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

PLACE

POSTAGE

STAMP

HERE

IBM United Kingdom LimitedUser Technologies Department (MP095)Hursley ParkWinchesterHampshireUnited KingdomSO21 2JN

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

IBM®

GC34-7201-01

CICS TS for z/OS 4.2: CICSPlex SM Messages and Codes · SM element of CICS ® T ransaction Server...

Documents

Transcript of CICS TS for z/OS 4.2: CICSPlex SM Messages and Codes · SM element of CICS ® T ransaction Server...