cicsplex sm messages and codes - ibm - united states 1. directly-connectable cics systems by...

CICS Transaction Server for z/OS

CICSPlex SM Messages and CodesVersion 3 Release 1

GC34-6471-07

Note!Before using this information and the product it supports, be sure to read the general information under Notices on page501.

This edition applies to Version 3 Release 1 of CICS Transaction Server for z/OS, program number 5655-M15, andto all subsequent versions, releases, and modifications until otherwise indicated in new editions. Make sure you areusing the correct edition for the level of the product.

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

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWho this book is for . . . . . . . . . . . . . . . . . . . . . . . viiCICS system connectivity . . . . . . . . . . . . . . . . . . . . . viiNotes on terminology . . . . . . . . . . . . . . . . . . . . . . viii

Summary of changes . . . . . . . . . . . . . . . . . . . . . . ixChanges for CICS Transaction Server for z/OS, Version 3 Release 1 . . . . . ixChanges for CICS Transaction Server for z/OS, Version 2 Release 3 . . . . . ixChanges for CICS Transaction Server for z/OS, Version 2 Release 2 . . . . . xNew and changed messages in CICS Transaction Server for z/OS, Version 2

Release 1 . . . . . . . . . . . . . . . . . . . . . . . . . . x

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

BB identifiers . . . . . . . . . . . . . . . . . . . . . . . . . 1EYU identifiers . . . . . . . . . . . . . . . . . . . . . . . . 1Action and severity codes . . . . . . . . . . . . . . . . . . . . 2

Format of message descriptions . . . . . . . . . . . . . . . . . . . 2

Chapter 2. BB messages . . . . . . . . . . . . . . . . . . . . . 5Diagnostic information for BB messages . . . . . . . . . . . . . . . . 5Completion code values . . . . . . . . . . . . . . . . . . . . . . 5BBCQxnnn messages . . . . . . . . . . . . . . . . . . . . . . . 6BBCxxnnn messages . . . . . . . . . . . . . . . . . . . . . . 10

Session name values . . . . . . . . . . . . . . . . . . . . . 10Conversation name values . . . . . . . . . . . . . . . . . . . 10Sense code values . . . . . . . . . . . . . . . . . . . . . . 10

BBMHxnnn messages . . . . . . . . . . . . . . . . . . . . . . 25BBMLxnnn messages . . . . . . . . . . . . . . . . . . . . . . 29BBMMxnnn messages . . . . . . . . . . . . . . . . . . . . . . 32BBMQnxnn messages . . . . . . . . . . . . . . . . . . . . . . 36BBMSxnnn messages . . . . . . . . . . . . . . . . . . . . . . 39BBMSSnnn messages . . . . . . . . . . . . . . . . . . . . . . 42BBMXxnnn messages . . . . . . . . . . . . . . . . . . . . . . 50BBMYAnnn messages. . . . . . . . . . . . . . . . . . . . . . 123

Alphabetic Character Values . . . . . . . . . . . . . . . . . . 123BBMZAnnn messages. . . . . . . . . . . . . . . . . . . . . . 134BBMZBnnn messages. . . . . . . . . . . . . . . . . . . . . . 143BBMZCnnn messages. . . . . . . . . . . . . . . . . . . . . . 148BBMZEnnn messages. . . . . . . . . . . . . . . . . . . . . . 156BBMZSnnn messages. . . . . . . . . . . . . . . . . . . . . . 162BBMZZnnn messages . . . . . . . . . . . . . . . . . . . . . . 165

Chapter 3. EYU messages. . . . . . . . . . . . . . . . . . . . 167Trace records . . . . . . . . . . . . . . . . . . . . . . . . . 167Console messages . . . . . . . . . . . . . . . . . . . . . . . 167EYUARnnnn messages . . . . . . . . . . . . . . . . . . . . . 168EYUAZnnn messages . . . . . . . . . . . . . . . . . . . . . . 173EYUBAnnnn messages . . . . . . . . . . . . . . . . . . . . . 175EYUBInnnn messages . . . . . . . . . . . . . . . . . . . . . 177EYUBMnnnn messages . . . . . . . . . . . . . . . . . . . . . 179EYUBNnnnn messages . . . . . . . . . . . . . . . . . . . . . 184EYUBUnnnn messages . . . . . . . . . . . . . . . . . . . . . 189

Copyright IBM Corp. 2005, 2011 iii

EYUCAnnn messages. . . . . . . . . . . . . . . . . . . . . . 191EYUCCnnnn messages . . . . . . . . . . . . . . . . . . . . . 193EYUCInnnn messages . . . . . . . . . . . . . . . . . . . . . 194EYUCLnnnn messages . . . . . . . . . . . . . . . . . . . . . 199EYUCPnnnn messages . . . . . . . . . . . . . . . . . . . . . 208EYUCRnnnn messages . . . . . . . . . . . . . . . . . . . . . 218EYUCSnnnn messages . . . . . . . . . . . . . . . . . . . . . 220EYUCTnnnn messages . . . . . . . . . . . . . . . . . . . . . 225EYUCWnnnn messages . . . . . . . . . . . . . . . . . . . . . 227EYUDDnnnn messages . . . . . . . . . . . . . . . . . . . . . 229EYUDVnnnn messages . . . . . . . . . . . . . . . . . . . . . 238EYUEInnnn messages . . . . . . . . . . . . . . . . . . . . . 242EYUEOnnn messages. . . . . . . . . . . . . . . . . . . . . . 269EYUHxnnn messages . . . . . . . . . . . . . . . . . . . . . . 271EYUMAnnn messages . . . . . . . . . . . . . . . . . . . . . 272EYUMMnnnn messages . . . . . . . . . . . . . . . . . . . . . 275EYUNLnnnn messages . . . . . . . . . . . . . . . . . . . . . 283EYUNXnnnn messages . . . . . . . . . . . . . . . . . . . . . 295EYUPAnnn messages . . . . . . . . . . . . . . . . . . . . . . 301EYUPEnnnn messages . . . . . . . . . . . . . . . . . . . . . 305EYUPInnnn messages . . . . . . . . . . . . . . . . . . . . . 307EYUPMnnnn messages . . . . . . . . . . . . . . . . . . . . . 308EYUPNnnnn messages . . . . . . . . . . . . . . . . . . . . . 312EYUPPnnnn messages . . . . . . . . . . . . . . . . . . . . . 318EYUPRnnnn messages . . . . . . . . . . . . . . . . . . . . . 321EYUPSnnnn messages . . . . . . . . . . . . . . . . . . . . . 322EYUPTnnnn messages . . . . . . . . . . . . . . . . . . . . . 324EYUTAnnn messages . . . . . . . . . . . . . . . . . . . . . . 325EYUTInnnn messages. . . . . . . . . . . . . . . . . . . . . . 328EYUTRnnnn messages . . . . . . . . . . . . . . . . . . . . . 329EYUTSnnnn messages . . . . . . . . . . . . . . . . . . . . . 336EYUTTnnnn messages . . . . . . . . . . . . . . . . . . . . . 344EYUVCnnnn messages . . . . . . . . . . . . . . . . . . . . . 344EYUVEnnnn messages . . . . . . . . . . . . . . . . . . . . . 358EYUVHnnnn messages . . . . . . . . . . . . . . . . . . . . . 368EYUVSnnnn messages . . . . . . . . . . . . . . . . . . . . . 368EYUWAnnn messages . . . . . . . . . . . . . . . . . . . . . 382EYUWGnnnn messages . . . . . . . . . . . . . . . . . . . . . 385EYUWInnnn messages . . . . . . . . . . . . . . . . . . . . . 387EYUWMnnnn messages . . . . . . . . . . . . . . . . . . . . . 391EYUWRnnnn messages . . . . . . . . . . . . . . . . . . . . . 397EYUWTnnnn messages . . . . . . . . . . . . . . . . . . . . . 401EYUXCnnnn messages . . . . . . . . . . . . . . . . . . . . . 402EYUXDnnnn messages . . . . . . . . . . . . . . . . . . . . . 407EYUXEnnnn messages . . . . . . . . . . . . . . . . . . . . . 425EYUXLnnnn messages . . . . . . . . . . . . . . . . . . . . . 432EYUXMnnnn messages . . . . . . . . . . . . . . . . . . . . . 453EYUXQnnnn messages . . . . . . . . . . . . . . . . . . . . . 456EYUXSnnnn messages . . . . . . . . . . . . . . . . . . . . . 457EYUXUnnnn messages . . . . . . . . . . . . . . . . . . . . . 464EYUXZnnnn messages . . . . . . . . . . . . . . . . . . . . . 476

Chapter 4. Unnumbered ISPF messages . . . . . . . . . . . . . . 479

Chapter 5. Debugging transaction messages . . . . . . . . . . . . 483COD0 messages. . . . . . . . . . . . . . . . . . . . . . . . 483

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

CODB messages . . . . . . . . . . . . . . . . . . . . . . . 484CMAS shutdown transaction messages . . . . . . . . . . . . . . . 485

Chapter 6. Abend and dump codes . . . . . . . . . . . . . . . . 487CICS abend and dump codes . . . . . . . . . . . . . . . . . . . 487Uxxxx abend codes. . . . . . . . . . . . . . . . . . . . . . . 489System dump codes . . . . . . . . . . . . . . . . . . . . . . 489

List of abbreviations . . . . . . . . . . . . . . . . . . . . . . 491

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . 493The CICS Transaction Server for z/OS library . . . . . . . . . . . . . 493

The entitlement set . . . . . . . . . . . . . . . . . . . . . . 493PDF-only books . . . . . . . . . . . . . . . . . . . . . . . 493

Other CICS books . . . . . . . . . . . . . . . . . . . . . . . 495Books from related libraries . . . . . . . . . . . . . . . . . . . . 495Determining if a publication is current . . . . . . . . . . . . . . . . 496

Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . 497

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 501Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 502

Sending your comments to IBM . . . . . . . . . . . . . . . . . 503

Contents v

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

Preface

This book contains all the messages issued by the CICSPlex SM element ofCICS Transaction Server for z/OS. It is closely linked with the CICSPlex SystemManager Problem Determination manual, which should also be consulted if amessage indicates there is a problem with CICSPlex 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.

CICS system connectivityThis release of CICSPlex SM can be used to control CICS systems that are directlyconnected to it.

For this release of CICSPlex SM, the connectable CICS systems are:v CICS Transaction Server for z/OS 3.1v CICS Transaction Server for z/OS 2.3v CICS Transaction Server for z/OS 2.2v CICS Transaction Server for OS/390 1.3

You can use this release of CICSPlex SM to control systems running supportedreleases of CICS that are connected to, and managed by, your previous release ofCICSPlex SM. However, if you have any directly-connectable release levels ofCICS, as listed above, that are connected to a previous release of CICSPlex SM,you are strongly recommended to migrate them to the current release ofCICSPlex SM, to take full advantage of the enhanced management services. Seethe CICS Transaction Server for z/OS Migration from CICS TS Version 2.3 forinformation on how to do this.

Table 1 shows which supported CICS systems can be directly connected to whichreleases of CICSPlex SM.

Table 1. Directly-connectable CICS systems by CICSPlex SM release

CICS system CICSPlex SMcomponent of CICSTS 3.1

CICSPlex SMcomponent of CICSTS 2.3



CICS TS 3.1 Yes No No No

CICS TS 2.3 Yes Yes No No

CICS TS 2.2 Yes Yes Yes No

CICS TS 1.3 Yes Yes Yes Yes

TXSeries 4.3.0.4 No Yes Yes No

Copyright IBM Corp. 2005, 2011 vii

|

||

||

||||

|||

|||

|||

|||||

|||||

|||||

|||||

|||||

Table 1. Directly-connectable CICS systems by CICSPlex SM release (continued)

CICS system CICSPlex SMcomponent of CICSTS 3.1




TXSeries 5.0 No Yes Yes No

Notes on 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 termCICSplex (spelled with a lowercase letter p) means the largest set of CICS systemsto be managed by CICSPlex SM as a single entity.

Other terms used in this book are:

Term Meaning

MVS MVS/ESA

See also List of abbreviations on page 491.

The phrase issue the command is used in this book to mean that the commandmay either 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 appropriatefield, and press Enter.

v Move the cursor to the appropriate field and press the PF key to which thecommand is assigned.

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

|

||||

|||

|||

|||

||||||

Summary of changes

This book is based on the CICSPlex SM Version 1 CICS Transaction Server forz/OS, Version 2 Release 3 edition. It has been updated to incorporate changesmade for CICS Transaction Server for z/OS, Version 3 Release 1.

Changes made since the last edition are indicated by vertical bars to the left of thechange.

Changes for CICS Transaction Server for z/OS, Version 3 Release 1This book now includes all messages issued by the Web User Interface. Thesemessages are of the form:

v EYUVCnnn issued by the clientv EYUVEnnn issued by the editorv EYUVHnnn issued by HTTPv EYUVSnnn issued by the serverIn previous releases these were documented in the CICSPlex System ManagerWeb User Interface Guide.

The following messages are new in this edition:

Table 2. New messages

EYUXD0901E EYUXD0902E EYUXD0903E


EYUXD0907E EYUXD0908I EYUXD0909I



EYUXD0916E

CICSPlex SM support for the CICS for Windows component of IBM TXSeries(also known as Windows NT 4.3 and Windows NT 5.0) is no longer provided inCICS Transaction Server for z/OS, Version 3 Release 1.

There are no other significant changes.

Changes for CICS Transaction Server for z/OS, Version 2 Release 3The following messages are new in this edition:

Table 3. New messages

EYUCL0124 EYUCL0130 EYUCL0131

EYUCP0016 EYUCP0017 EYUCP0018



EYUXD0018 EYUXD0019 EYUXD0020


Copyright IBM Corp. 2005, 2011 ix

|||

|||

|||

|||

|||

|||

Table 3. New messages (continued)


EYUXD031 EYUXL0117 EYUXU0240


Changes for CICS Transaction Server for z/OS, Version 2 Release 2A new message destination, the Windows application event log has been introducedin support of the CICSPlex SM remote MAS agent for Windows.


New and changed messages in CICS Transaction Server for z/OS,Version 2 Release 1

The following messages are new in this edition:

BBCSJ015EBBCSJ016EBBMXCL56BBMZA100IBBMZS100IBBMZS150IEYUBI0004IEYUBI0005IEYUBI0006IEYUBI0007IEYUBI0103EEYUBM0328EEYUBU0116EEYUBU0117EEYUCP0205EEYUDV0130IEYUDV0131IEYUEI0619EEYUEI0650IEYUTS0024IEYUWG0106EEYUWM0432EEYUWM0433EEYUXC0021SEYUXC0022SEYUXC0023SEYUXC0024SEYUXD0010EEYUXD0013EEYUXD0016EEYUXD0017EEYUXL0140EEYUXL0999IEYUXS1026EEYUXS1027I

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

EYUXS1028IEYUXS1029SEYUXS1030S

The following messages are changed in this edition:

BBMZS110WEYUBI0102EEYUTA044EYUWM0422EEYUXL0115E

A new section, EYUDDnnnn messages on page 229, has been added thatdescribes the CICS production deployment tool for EJB technology offline utilitymessages.

Summary of changes xi

xii CICS TS for z/OS: 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 browserv End-user messages issued to an ISPF end-user interface windowv Batch report messages issued by the data repository or trace facilities

Message identifiersCICSPlex SM messages begin with BB or EYU.

BB identifiersThese identifiers consist of a five-digit prefix that begins with either BBC or BBMfollowed by a three-digit message number. Table 4 lists the message prefixes andthe components they are associated with:

Table 4. BB message identifiers and their componentsPrefix Component Page

BBCQx ISPF end-user interface 6BBCxx Communications Manager 10BBMHx ISPF end-user interface 25BBMLx Linkage Services 29BBMMx ISPF end-user interface 32BBMQx ISPF end-user interface 36BBMSx General Services 39BBMSS Security Services 42BBMXx ISPF end-user interface 50BBMYA DIAGMSG View 123BBMZA CAS Server Control 134BBMZB User Session Control 143BBMZC Common Control Function 148BBMZE Recovery Manager 156BBMZS Server Scheduling Services 162BBMZZ Built-in Service Functions 165

EYU identifiersThese identifiers consist of the prefix EYU followed by a two-letter componentidentifier and a four-digit message number. EYU is the IBM-assigned identifier forCICSPlex SM modules. The component identifier shows the component that issuesthe message. Table 5 lists the component identifiers and their associatedcomponents.

Table 5. EYU message identifiers and their componentsPrefix Component Page

EYUAR Application programming interface (REXX) 168EYUAZ ISPF Interface 173EYUBx Business Application Services (BAS) 175EYUCA ISPF Interface 191EYUCx Communications 193EYUDV IPCS diagnostic VERBEXIT 238

Copyright IBM Corp. 2005, 2011 1

|

Table 5. EYU message identifiers and their components (continued)Prefix Component Page

EYUEI Information Display Panel 242EYUEO ISPF Interface 269EYUMA ISPF Interface 272EYUMM Monitor Services 275EYUNx Managed Application System (MAS) 283EYUPA ISPF Interface 301EYUPx real-time analysis 301EYUTA ISPF Interface 325EYUTx Topology Services 325EYUWA ISPF Interface 382EYUWx Workload Manager 382EYUXC Data Cache Manager 402EYUXD Data Repository 407EYUXE Environment Services System Services (ESSS) 425EYUXL Kernel Linkage 432EYUXM Message Services 453EYUXQ Queue Manager 456EYUXS Common Services 457EYUXU Batched Repository Facility 464EYUXZ Trace Services 476

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 SMprocessing is suspended until corrective action has been taken.

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 BBxxxnnn or 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.

introduction

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

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 Windows application event logv EYULOGv Information Display panel window (refers to an ISPF terminal session)v 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.)

introduction

Chapter 1. Introduction 3

introduction


Chapter 2. BB messages

This chapter documents CICSPlex SM messages that begin with the prefix BB. Themessages are listed alphanumerically. The information includes an explanation ofeach message, the system response, and an action you can take to resolve themessage. All of these messages are issued to either the operator console or thewindow interface.

Note: Although several window interface messages can appear for a single error, itis always the first message that provides the most information about theerror. Subsequent messages provide additional diagnostic information for useprimarily by IBM support personnel.

Diagnostic information for BB messagesIf you must contact your IBM Support Center in response to any of the BBmessages, obtain as much of the following information as possible before you call:

v The original message and any preceding messagesv A printout of any window error messagesv System logv Job console log from the failing address spacev SVC dump (SDUMP)v SYS1.LOGREC recordsv SYSxDUMP

Note: If the system shuts down due to an abend, one or more SYS1.LOGRECrecords should be written.

Completion code valuesIn several BB messages, except BBCSxnnn messages, a completion code appearseither as a decimal value or a hexadecimal value. The following list shows thesecodes in decimal and in hexadecimal, and describes their meaning.

Decimal Hex Description

00 X'00' Function complete

04 X'04' Function complete, but anabnormal condition wasdetected

08 X'08' Function failed due tofunction detected error

12 X'0C' Function failed due to internallogic error

16 X'10' Function failed due to fatalerror

-1 X'FFFFFFFF' Forced exit from function dueto an intercepted error suchas an abend or programcheck

Copyright IBM Corp. 2005, 2011 5

BBCQxnnn messagesThis section contains window messages that are prefixed with BBCQ. Thesemessages indicate an error when a command is issued against a system definitiondisplayed a PlexManager view for a coordinating address space (CAS).

Note: When displayed, each of these messages has an alphabetic characterappended to the end; the character depends upon the return code receivedat the time the message is issued. See Action and severity codes on page2 for more information about these characters.

BBCQA103 Error adding to tree

Explanation: This is a diagnostic message containingerror information used by IBM support to resolve theerror condition.

System action: Additional messages are issued.

User response: See preceding messages andperform the actions provided.

BBCQA104 System delete failed for system

Explanation: A DEL line command was issued againstthe system definition named system to delete it, butsystem was not deleted. Other messages indicate thereason the command failed.

System action: The system definition is not deletedfrom the PlexManager views and any current sessionswith system continue to communicate.

User response: Read the related messages andperform the suggested actions.

BBCQA105 System halt failed for system

Explanation: An H line command was issued againstthe system named system to halt communications, butcommunications with system were not stopped. Othermessages indicate the reason the command failed.

System action: Any current sessions with systemcontinue to communicate with the coordinating addressspace (CAS).


BBCQA106 System quiesce failed for system

Explanation: A Q line command was issued againstthe system named system to quiesce communication,but the coordinating address space (CAS) is not waitingfor communications with system to end. Othermessages indicate the reason the command failed.

System action: New sessions between system andthe CAS continue to be established, if requested.


BBCQA107 System start failed for system

Explanation: An S line command was issued againstthe system named system to restart communicationswith the coordinating address space (CAS), butcommunications cannot be started. Other messagesindicate the reason the command failed.

System action: New sessions between system andthe CAS cannot be established.


BBCQA108 System refresh failed

Explanation: The REFRESH command was issuedfrom the COMMAND line so the current coordinatingaddress space (CAS) could read changes made to thesystem definition of a target system, but the changeswere not read. Other messages indicate the reason thecommand failed.

System action: The current CAS continues to use theprevious system definition of the target system.


BBCQA109 System add failed for system

Explanation: The ADD command was issued from theCOMMAND line to add a new system definition for asystem named system, but the system definition wasnot added to the current coordinating address space(CAS). Other messages indicate the reason thecommand failed.

System action: The system definition is not added tothe PlexManager views.


BBCQA110 System change failed for system

Explanation: A C (change) line command was issuedagainst the system named system to modify the currentsystem definition, but the definition was not changed.Other messages indicate the reason the commandfailed.

BB messages


System action: The coordinating address space(CAS) retains the system definition without changes.


BBCQA111 Processing error during add




BBCQA112 Display dialog error, RC=code

Explanation: The command to add or change asystem definition was issued, but the dialog that acceptsmodifications or new definition information failed with areturn code of code.

System action: The command is not processed.

User response: Verify that the product is correctlyinstalled and check any SMP listings to ensure thatrecent service was properly applied. (All link edits totarget data sets should be RC=0. If SMP target datasets are copied to execution libraries, the copy stepshould be repeated, taking care to copy everything.)

If the installation is valid, contact your IBM SupportCenter with any of the available information listed inDiagnostic information for BB messages on page 5.

BBCQA113 DataBusActionProcess error, cc=code




BBCQA114 DataBusProcess error, cc=code




BBCQA115 Access denied for function,DSN=dsname

Explanation: An action named function wasattempted, but the user address space was deniedaccess by the external security system to the data set

named dsname. If a user address space cannot accessa required data set, an action cannot be performed.

System action: The action is not performed.

User response: Contact your security administrator toobtain the proper authority for the data set nameddsname.

BBCQA116 Halt not accepted for current system,command ignored

Explanation: An H (halt) line command was issuedagainst the current system to halt communications, butcommunications were not stopped. Communicationscannot be halted with the current system because this isthe system you are logged onto. Since the H linecommand causes immediate termination of all currentsessions, the coordinating address space (CAS) doesnot permit you to terminate your own session.

System action: The action is ignored.

User response: Contact your IBM Support Center withany of the information that is available from the listshown in Diagnostic information for BB messages onpage 5.

BBCQA117 Quiesce not accepted for currentsystem, command ignored

Explanation: A Q (quiesce) line command was issuedagainst the current system to quiesce communication,but the coordinating address space (CAS) is not waitingfor all session communications to end and is allowingnew sessions to be established. Communicationscannot be quiesced with the current system becausethis is the system you are logged onto. Since the Q linecommand schedules termination of all current sessions(and causes the CAS to reject any new sessions), youare not permitted to schedule termination of your ownsession.

System action: The action is ignored.


BBCQA118 Unable to obtain working storage

Explanation: During the processing of an actionagainst a system definition, an attempt to obtain workingstorage to process the action failed. The most probablecause for this message is an internal error.

System action: The action is not performed and thismessage is displayed.

User response: Obtain as much of the informationthat is available from the list shown in Diagnosticinformation for BB messages on page 5 and contactyour IBM Support Center.

BB messages

Chapter 2. BB messages 7

BBCQA119 Attempting to add system with aduplicate name

Explanation: There are two ways this error can occur:

v An ADD command was issued from the COMMANDline to add a new system definition, but the nameassigned to the new system definition is alreadydefined to an existing system definition.

v A C (change) line command was issued against anexisting system definition to change the name of thesystem, but the new name is already defined to anexisting system definition.

Each system definition must have a unique namedefined to the System Name field of the ADD CASSYSTEM or CHANGE CAS SYSTEM panel.

System action: The new system definition is notcreated or the existing system definition is not changed.

User response: To determine if a name is alreadybeing used, display a PlexManager view and review thenames.

If an ADD command was issued, reissue the ADDcommand from the COMMAND line and define a uniquename to the system definition.

If the C line command was issued, reissue the linecommand and define a unique name to the systemdefinition.

BBCQA120 Unable to find requested systemdefinition


v An ADD command was issued from the COMMANDline, but the action processor cannot locate aBBIPARM DD data set in which to save the newsystem definition file.

v A C (change) or DEL (delete) line command wasissued against a system, but the action processorcannot find a system definition file for the system inthe BBIPARM DD data set to change or delete.

These three commands dynamically change systemdefinitions, and attempt to permanently savemodifications in the BBIPARM DD data set wheresystem definition files reside. At coordinating addressspace (CAS) startup, any system definition files in theBBIPARM DD data set are loaded into storage, wheredynamic modifications are held. This error can occur ifthe CAS started task does not have a BBIPARM DDallocated.

System action: The action is performed against thein-storage version of the system definition, but theBBIPARM DD data set system definition file is notupdated.

User response: Define a BBIPARM DD data set tothe CAS started task and restart the CAS ifmodifications need to be made permanently; otherwise,ensure that a BBIPARM DD data set is eventually

allocated to the CAS started task so this error does notoccur again.

BBCQA121 Attempting to add system with aduplicate APPL name


v An ADD command was issued from the COMMANDline to add a new system definition, but the VTAM

application ID name assigned to the new systemdefinition is already defined to an existing systemdefinition.

v A C (change) line command was issued against anexisting system definition to change the VTAMapplication ID name of the system, but the new nameis already defined to an existing system definition.

Each system definition must have a unique VTAMapplication ID name defined to the VTAM ApplicationName field of the ADD CAS SYSTEM or CHANGE CASSYSTEM panel.

System action: The new system definition is notcreated or the existing system definition is not changed.

User response: To determine if a name is alreadybeing used, display a PlexManager view and review thenames.

If an ADD command was issued, reissue the ADDcommand from the COMMAND line and define a uniqueVTAM application ID name to the system definition.

If the C line command was issued, reissue the linecommand and define a unique VTAM application IDname to the system definition.

BBCQA122 Unknown error - CC=code

Explanation: During the processing of an actionagainst a system definition, an unexpected erroroccurred with a completion code of code. SeeCompletion code values on page 5 for a description ofthe code value. This message indicates that an internalerror has occurred.

System action: The action is not performed.

User response: Obtain as much of the informationthat is available from the list shown in Diagnosticinformation for BB messages on page 5 and contactyour IBM Support Center.

BBCQA203 Error adding to tree




BB messages


BBCQA204 Session Delete Failed for session




BBCQA205 Session session Deleted




BB messages


BBCxxnnn messagesThis section lists the communications manager messages. The communicationsmanager controls the communication tasks between the coordinating address space(CAS) and other address spaces and MVS systems.

Session name valuesA session name value, which is used in various messages in this section, appearsin the message text as a (b.c), where:

a Is a unique number of variable length that identifies the session betweenthis coordinating address space (CAS) and a partner CAS.

b Is the system ID of the partner CAS. The partner system ID is derived fromthe name defined to this partner CAS.

c Is the LU6.2 mode type, which has a valid value of DEFAULT; other valuesare not supported.

Conversation name valuesA conversation name value, which is used in various messages in this chapter,appears in the message text as x (y.z), where:

x Is a unique number of variable length that identifies the conversationinternally. This value is used to correlate messages to sessions.

y Is a 1- to 8-character value identifying the TSO user ID or the name of theaddress space service that owns the conversation.

z Is a 1- to 8-character value, used internally, to uniquely identify theconversation. For TSO users, this value is assigned as nondisplayable.

Sense code valuesSense codes are displayed in several of the messages prefixed with BBCS. TheBBCS codes are closely related to the standard meanings assigned to VTAM sensecodes, as described in the VTAM Format and Protocol Reference Manual:Architecture Logic for LU Type 6.2. Sense codes that are not in that manual or thathave a slightly different meaning when used in a BBCS message are documentedhere. If you cannot find a sense code that appears in a BBCS message in thefollowing list, refer to the VTAM documentation for the standard meaning:

08350001Same as LU6.2 sense code 08350000; see the VTAM documentation.





084c0000The requested user or application is not active.

BBCxxnnn messages


08640000The conversation terminated abnormally because either the user terminatedabnormally or the coordinating address space (CAS) is stopping and isterminating all conversations.

08ff0001Internal error occurred sending the BIND.

1008600bResource failure; no retry is attempted.

10086021Allocation error; transaction is not recognized.





20120000Invalid sense code received.

BBCSA002S A SUBTASK ENDED UNEXPECTEDLY

Explanation: A communications manager subtask hasterminated without a system shutdown. Subtasks areexpected to end only at a request to do so.

System action: Either the system terminates orexisting sessions continue, but they might encounterprocessing problems. New sessions might not beestablished and existing sessions might not terminate.

User response: Restart the coordinating addressspace (CAS) and contact your IBM Support Center withany of the information that is available from the listshown in Diagnostic information for BB messages onpage 5.

BBCSA005E WAIT FAILED, RC=X'n'

Explanation: A communications manager WAITfunction has failed while the function was waiting to beposted. The return code is indicated by n and is alwaysa value of 8, which means either an error recoveryfailed or an invalid control block was detected.

System action: The system proceeds as if the WAITfunction completed normally. This may lead to otherprocessing errors and cause synchronization problems.

User response: See other messages to determinewhether or not to restart the coordinating address space(CAS). If the problem persists, contact your IBMSupport Center with any of the information that isavailable from the list shown in Diagnostic informationfor BB messages on page 5.

BBCSA006E subtask ABENDED, COMPLETIONCODE=X'nnnn'

Explanation: The communications manager subtasknamed subtask has abended. The completion code isnnnn and is one of the following values:1600 PC call to unavailable service.17xx Recovery manager abends.1799 Should Not Occur condition (see note).1800 "C" housekeeping failure.1801 GSI housekeeping failure.1802 GSI router housekeeping failure.1803 Transaction manager housekeeping failure.1804 SAS/C resident module failure.1899 Improper event for DYNAEC "EPD".1900 Storage manager abend code.3000 Built-in service function error.4000 Pseudo GSI service failure.4080 Unrecoverable control task error.4090 Server/application initialization error.4095 Task terminated by PGTERM.

System action: Either the system terminates orexisting sessions continue, but they might encounterprocessing problems. New sessions might not beestablished and existing sessions might not terminate.

Note: In the case of completion code 1799 (Should NotOccur), an abend occurs and a record is writtento the SYS1.LOGREC data set; no additionalmessages are issued and no SDUMP is taken.

User response: See messages that follow todetermine whether the coordinating address space(CAS) is terminating.

BBCxxnnn messages


If the CAS is not terminating, restart it and contact yourIBM Support Center with the name of the subtask in thismessage.

If the CAS is terminating, contact your IBM SupportCenter with any of the information that is available fromthe list shown in Diagnostic information for BBmessages on page 5.

BBCSA010A VTAM IS NOT ACTIVE. REPLY R TORETRY, C TO CONTINUE WITHOUTVTAM, OR T TO TERMINATE

Explanation: This is a WTOR message that promptsthe user to take an action concerning the initialization ofthe CAS. The CAS uses VTAM for cross systemcommunication. If VTAM is inactive, the CAS can'tcommunicate with other defined CAS(s) running ondifferent systems.

System action: The CAS waits for the reply.

User response: Reply with one of the following:

R To restart the CAS if VTAM has completed itsinitialization or has been started.

C To continue initialization of the CAS withoutcross-system communication.

T To terminate the CAS. When the CASterminates, message BBMZC012E is displayedand the CAS is abended with code of U4090.

BBCSA011I VTAM IS NOT ACTIVE YET, CAS ISDELAYED UNTIL VTAM IS UP

Explanation: This informational message indicatesthat the CAS is waiting for VTAM initialization.

System action: The CAS checks the status of VTAMevery 30 seconds for three minutes. If VTAM is still notactive after three minutes, message BBCSA010A isdisplayed. If VTAM becomes active within threeminutes, the CAS continues its initialization.

User response: None.

BBCSA013I VTAM IS NOW ACTIVE, CAS ISSTARTING

Explanation: VTAM was inactive when the CAS wasstarted. However, VTAM completed its initialization andthe CAS continues to initialize. This message normallyfollows message BBCSA011I.

System action: VTAM is now active, and the CAScontinues to initialize.


BBCSA014W VTAM IS INOPERATIVE, CAS ISCONTINUING. ERRORS MAY OCCUR

Explanation: The user specified C when messageBBCSA010A was issued. The CAS continues toinitialize without VTAM. If cross system communicationis enabled and VTAM is still inactive, errors may occur.If this is a standalone CAS, no errors occur.

System action: The CAS continues its initializationwithout waiting for VTAM to become active.

User response: Find out why VTAM is inactive. StartVTAM to avoid future errors.

BBCSA015E ERROR IN SETTING TIMER, BBCTERMINATED

Explanation: The communication component of theCAS encountered an internal error while setting up atimer.

System action: The CAS terminates. Additional errormessages are written to the system log.

User response: Collect the error information from thesystem log, then contact your IBM Support Center.

BBCSA016E CSZ_GETCB ERROR IN CSA40, BBCTERMINATED

Explanation: The communication component of theCAS encountered an internal error while obtainingstorage.

System action: The CAS terminates. Additional errormessages are written to the system log.

User response: Collect the error information from thesystem log, then contact your IBM Support Center.

BBCSA017E INVALID REPLY

Explanation: An invalid reply to messageBBCSA010A was entered.

System action: The reply is rejected. MessageBBCSA010A is redisplayed and the CAS waits for areply.

User response: Specify a valid reply. See messageBBCSA010A for a list of valid replies.

BBCSB004E BID RSP FAILURE ON SESSION a (b.c)CONVERSATION x (y.z)

Explanation: The coordinating address space (CAS)received a bid response (RSP) for this session andconversation, but the session resource cannot belocated in the free session pool, so the bid responsefailed.

Sessions occur between CASs and CICSPlex SMaddress spaces (CMASs) and user address spaces.The session name is described in Session name

BBCxxnnn messages


values on page 10. Conversations are always initiatedwhen a user opens a window. The conversation name isdescribed in Conversation name values on page 10.

System action: The CAS's bid response is ignored.The conversation with the end user can malfunction.

User response: Attempt logging off the system andthen reconnecting. If the conversation is malfunctioningand a logoff is not possible, contact the system operatorto cancel the TSO session. If the problem persists,contact your IBM Support Center with any of theinformation that is available from the list shown inDiagnostic information for BB messages on page 5.

BBCSB006E CANNOT FIND BIDDINGCONVERSATION FOR SESSION a (b.c)

Explanation: The coordinating address space (CAS)received a bid response for a session and located thesession resource in the free session pool, but could notfind the conversation associated with the session. Theconversation name is unknown because it cannot befound. The session name is described in Session namevalues on page 10.

System action: The session terminates and theconversation can malfunction.

User response: Look for other messages on thepartner CAS system for more information about thesession failure. The partner CAS is identified in thesession name. If the problem persists, contact your IBMSupport Center with any of the information that isavailable from the list shown in Diagnostic informationfor BB messages on page 5.

BBCSB009I SESSION a (b.c) WITHCONVERSATION x (y.z) IS BEINGCANCELED DUE TO SENSE=xx

Explanation: Due to the reason specified by thesense code xx, the coordinating address space (CAS) iscancelling the session. This message can be caused bya user logging off abnormally (S522 and so on). SeeSense code values on page 10 for possible sensecode values. The indicated conversation terminateswhen the session is canceled. The session name isdescribed in Session name values on page 10.Conversations are always initiated when a user opens awindow. The conversation name is described inConversation name values on page 10.

This message can be caused by a user logging offabnormally (S522 and so on). See the Format andProtocol Reference Manual: Architecture Logic for LUType 6.2 for details on possible sense code values.

System action: The session and conversation arecanceled. An error message about a conversationfailure appears in the window.

User response: Close the window and retry therequest. If the problem persists, contact your IBM

Support Center with the sense code from this messageand any of the information that is available from the listshown in Diagnostic information for BB messages onpage 5.

BBCSB010E PROGRAMMING SEQUENCE ERRORON BIDDER SESSION a (b.c) WITHCONVERSATION x (y.z), EVENT=n,SESSION STATUS=xx

Explanation: A programming sequence error occurredwhen the bidder session, with a status of xx, had anevent of n. The session name is described in Sessionname values on page 10. Conversations are alwaysinitiated when a user opens a window. The conversationname is described in Conversation name values onpage 10.

Possible event n values are:0 Receive positive bid response1 Receive bid2 Receive attach3 Receive security message4 Receive free session message5 Receive yield session message6 Receive session activation for first speaker7 Receive session activation for bidder8 Receive session activation security

Possible status xx values are:0 Session activation1 Free2 Pending attach3 In use4 Pending security message5 Waiting for a bid

System action: The system responds depending uponthe event and session status combination. The sessionor conversation may be canceled.

User response: Look for additional messages andrespond to those actions. If the problem continues,contact your IBM Support Center with any of theinformation that is available from the list shown inDiagnostic information for BB messages on page 5.

BBCSB011E PROGRAMMING SEQUENCE ERRORON FIRST SPEAKER SESSION a (b.c)WITH CONVERSATION x (y.z),EVENT=n, SESSION STATUS=xx

Explanation: A programming sequence error occurredwhen the first speaker session, with a status of xx, hadan event of n. The session name is described inSession name values on page 10. Conversations arealways initiated when a user opens a window. Theconversation name is described in Conversation namevalues on page 10.

Possible event n values are:0 Send get session message1 Receive bid

BBCxxnnn messages


2 Receive attach3 Receive security message4 Receive free session message5 Receive yield session message6 Receive session activation for first speaker7 Receive session activation for bidder8 Receive session activation security

Possible status xx values are:0 Session activation1 Free2 Pending attach3 In use4 Pending security message5 Pending a bid



BBCSB012E PROGRAMMING SEQUENCE ERRORFOR BIDDER CONVERSATION x (y.z)ON SESSION a (b.c), EVENT=n,CONVERSATION STATUS=xx

Explanation: A programming sequence error occurredwhen the bidder conversation, with a status of xx, hadan event of n. The session name is described inSession name values on page 10. Conversations arealways initiated when a user opens a window. Theconversation name is described in Conversation namevalues on page 10.

Possible event n values are:0 Send get session message1 Receive positive bid response2 Receive negative bid response3 Receive attach4 Send deallocate conversation message

Possible status xx values are:0 Free conversation1 Conversation in use2 Conversation waiting for a session



BBCSB013E PROGRAMMING SEQUENCE ERRORFOR FIRST SPEAKER CONVERSATIONx (y.z) ON SESSION a (b.c), EVENT=n,CONVERSATION STATUS=xx

Explanation: A programming sequence error occurredwhen the first speaker conversation, with a status of xx,had an event of n. The session name is described inSession name values on page 10. Conversations arealways initiated when a user opens a window. Theconversation name is described in Conversation namevalues on page 10.

Possible event n values are:0 Send allocate session message1 Send get session message2 Receive remote attach3 Receive local attach4 Send deallocate conversation message

Possible status xx values are:0 Free conversation1 Conversation in use2 Conversation waiting for a session



BBCSB014E BEGIN INPUT SEQUENCE ERROROCCURRED FOR SESSION a (b.c)WITH CONVERSATION x (y.z),EVENT=n, SESSION STATUS=xx

Explanation: The Begin Input Sequence was theevent that occurred when the session had a status of xxcausing a sequence error. The session name isdescribed in Session name values on page 10.Conversations are always initiated when a user opens awindow. The conversation name is described inConversation name values on page 10.

Possible event n values are:0 Send Begin Input Sequence request1 Receive Begin Input Sequence reply2 Receive Begin Input Sequence request3 Send Begin Input Sequence reply

Possible status xx values are:0 Reset state1 Begin Input Sequence sent2 Begin Input Sequence received3 Closed state

System action: The system responds depending uponthe event and session status combination. The sessionor conversation may be canceled. The error can be

BBCxxnnn messages


corrected when the session or conversation is canceled.


BBCSB016E RRB IGNORED ON SESSION a (b.c)CONVERSATION x (y.z) DATA=data

Explanation: A Response/Request Block (RRB)containing the information specified as data was ignoredbecause the data could not be processed. The datacould not be processed because it arrived after theconversation had terminated. Typically, this occurs whenthe coordinating address space (CAS) is processing asession outage condition on a session that wassupporting the conversation.

The session name is described in Session namevalues on page 10. Conversations are always initiatedwhen a user opens a window. The conversation namefor which the data could not be processed is describedin Conversation name values on page 10.

System action: The CAS assumes the session hasended and discontinues processing data for anyconversations associated with the session. The user'ssession may malfunction.

User response: Attempt logging off and then loggingback on to the system. If this message conditioncontinues, restart the CAS. If the error persists afterrestarting, contact your IBM Support Center with any ofthe information that is available from the list shown inDiagnostic information for BB messages on page 5.

BBCSB017E LU6.2 MODE NAME modename NOTVALID FOR SESSION a (b.c)

Explanation: The session a (b.c) has requested aninvalid LU6.2 mode name of modename. The modename is not supported because it is incorrectly defined.This is an application error.

The session name is described in Session namevalues on page 10.

System action: The user session is not activated.


BBCSB022E LU6.2 MODE NAMEid.sysname.modename NOT FOUNDFOR SESSION a (b.c) withCONVERSATION x (y.z)

Explanation: The session a (b.c) with a conversationof x (y.z) cannot locate an LU6.2 mode name ofid.sysname.modename. The mode name is not

supported because it is not valid. This is an applicationerror.

The session name is described in Session namevalues on page 10. Conversations are always initiatedwhen a user opens a window. The conversation name isdescribed in Conversation name values on page 10.The LU6.2 mode name shows the following information:

id The internal system ID

sysnameThe name of the system

modenameThe LU6.2 mode name

System action: The user session is terminated.


BBCSB023I LU6.2 MODE NAME modename NOTVALID FOR system sysname

Explanation: The system sysname has requested aninvalid LU6.2 mode name of modename. The modename is not supported because it is incorrectly defined.This message is issued with other messages about thesystem. The sysname is the name of the system.

System action: The user session is not activated.

User response: Look for other messages that followthis message.

BBCSB024E THE ADDRESS SPACE aspace IS NOTAVAILABLE

Explanation: The address space aspace is no longeractive, but a session on another system is attemptingcommunication.

System action: The inbound conversation for thesession is terminated. The user on the other system hasreceived a message that the conversation cannot beestablished.

User response: Attempt the request when theaddress space is active. If the address space is activeand this message is issued, contact your IBM SupportCenter with any of the information that is available fromthe list shown in Diagnostic information for BBmessages on page 5.

BBCSB028E PROTOCOL ERROR WITH SENSE nnON SESSION a (b.c) CONVERSATIONx (y.z)

Explanation: The communications protocol betweentwo coordinating address spaces (CASs) has beenviolated with a sense code of nn. The protocol violationhas occurred on the partner CAS for the indicated

BBCxxnnn messages


session and conversation. This message can be issuedwhen a user session terminates abnormally or a timeoutcondition is incurred, because the CAS may deliberatelyforce a protocol error to end the session connection.

See Sense code values on page 10 for possible sensecode values. The session name is described in Sessionname values on page 10. Conversations are alwaysinitiated when a user opens a window. The conversationname is described in Conversation name values onpage 10.

System action: The session and conversation areterminated.

User response: If possible, find out if the user sessiontimed out or logged off improperly. If this error occurredfor any other reason, contact your IBM Support Centerwith any of the information that is available from the listshown in Diagnostic information for BB messages onpage 5 for both coordinating address spaces (CASs).

BBCSB030E SESSION a (b.c) CANNOT BE FOUNDFOR CONVERSATION x (y.z)

Explanation: The session a (b.c) for conversationx (y.z) is not where it is supposed to be. Aprogramming error has occurred. The session name isdescribed in Session name values on page 10.Conversations are always initiated when a user opens awindow. The conversation name is described inConversation name values on page 10.

System action: The conversation is terminatedbecause the session through which it mustcommunicate cannot be located.


BBCSB036E PARAMETER MEMBER memberMISSING, DEFAULT PARAMETERSUSED

Explanation: The parameter member member ismissing from the data set defined by the BBIPARM DDstatement in the coordinating address space (CAS)PROC.

System action: The default parameters are used.These parameters default to a single systemconfiguration.

User response: Define other CASs to this system ifyou require cross-system communications.

BBCSB037E PARAMETER MEMBER memberINVALID, DEFAULT PARAMETERSUSED

Explanation: The contents of the parameter membermember are invalid. This condition can occur if ISPF

Edit was used to attempt to update this member. Theparameter member member contains binary data andcannot be modified.

System action: The default parameters are used.These parameters default to a single systemconfiguration.

User response: Delete the parameter membermember in the data set defined by the BBIPARM DDstatement in the CAS PROC. Redefine other CASs tothis system, if you require cross-systemcommunications. The parameter member is dynamicallycreated when you save your changes.

BBCSB038E UPDATE TO PARAMETER MEMBERmember FAILED

Explanation: Changes were made to parametermember member, but the changes were not saved tothis member. These changes are temporarily in effect,but only while the coordinating address space (CAS)continues to execute. Other messages should indicatethe cause of the update failure.

System action: Any changes entered are valid untilan IPL or the CAS is restarted. The parameter memberis not updated.

User response: Look for other messages to correctthe problem that caused the update failure. Reenterchanges and save them.

BBCSC001E PROGRAMMING SEQUENCE ERRPRON LU SESSION a (b.c) AN INVALIDSTATE OCCURRED WHEN LU=luIDWITH CID=cid had session status=xxand event=n

Explanation: A programming sequence error occurredwhen the LU session a (b.c) on LU luID had a status ofxx and attempted to process event n.

The session name is described in Session namevalues on page 10. The luID value is the LU6.2conversation ID. The CID (connection identifier) valuefor the LU is cid, which is a 4-byte field.

Possible values for the session status are:0 Reset1 Pending initiation response, PLU2 Pending initiation response, SLU3 Pending CINIT4 Pending bind5 Pending local path control response6 Pending local bind response7 Pending local initiation half-session response8 Pending remote path control response9 Pending remote bind response10 Pending remote initiation half-session response11 Active12 Pending unbind response

Possible values for the event are:

BBCxxnnn messages


0 Activate session as a PLU1 Activate session as an SLU2 Positive response to initialize session3 Negative response to initialize session4 Notify message5 CINIT okay6 CINIT no good7 Positive response to path control connect8 Negative response to path control connect9 Positive response to bind, format okay10 Positive response to bind, format no good11 Negative response to bind, format okay12 Negative response to bind, format no good13 Positive response from initialize half-session14 Negative response from initialize half-session15 Bind okay16 Bind did not work17 Session deactivation pending18 Session deactivation active19 Session deactivation cleanup active20 Half-session aborting21 Positive response to unbind22 Negative response to unbind23 Session cleanup24 CTERM orderly25 CTERM forced26 Reset, session outage notification27 Reset, normal

System action: The system responds depending uponthe event and session status combination. The sessionmay be canceled.


BBCSC002E RU=n RECEIVED NEGATIVERESPONSE DUE TO SENSE=code

Explanation: A negative response has been receivedfrom the partner coordinating address space (CAS) thatwas attempting to send an RU of n, with a sense codeof code, through the session to this CAS. An RU is arequest unit, which is the smallest sized VTAM protocolmessage unit that is processed on a VTAM link. Thesense code is documented in either the Format andProtocol Reference Manual: Architecture Logic for LUType 6.2 or in VTAM Messages and Codes.

System action: System action depends upon thestate of the session. The session can be terminated ora conversation on the session can be terminated.

User response: Check for related VTAM messages orother CAS messages to determine problem. If theproblem persists, contact your IBM Support Center withany of the information that is available from the listshown in Diagnostic information for BB messages onpage 5.

BBCSC003E UNABLE TO CORRELATE BIND FORRU=n, SENSE=code

Explanation: A bind response was received by thecoordinating address space (CAS), but nocorresponding bind was sent requesting a bindresponse. The RU n identifies the bind response thatwas received. An RU is a request unit, which is thesmallest sized VTAM protocol message unit that isprocessed on a VTAM link. This RU has a sense codeof code. The sense code is documented in either theFormat and Protocol Reference Manual: ArchitectureLogic for LU Type 6.2 or in VTAM Messages andCodes.

System action: The session is terminated.


BBCSC004E UNABLE TO CORRELATE UNBINDFOR RU=n, SENSE=code

Explanation: An unbind response was received by thecoordinating address space (CAS), but nocorresponding unbind was sent requesting an unbindresponse. The RU n identifies the unbind response thatwas received. An RU is a request unit, which is thesmallest sized VTAM protocol message unit that isprocessed on a VTAM link. This RU has a sense codeof code. The sense code is documented in either theFormat and Protocol Reference Manual: ArchitectureLogic for LU Type 6.2 or in VTAM Messages andCodes.

System action: The session is terminated.


BBCSD002W RRB DISCARDED, HS_ID=N/A,LU_ID=N/A, CID=N/A, DATA=messagetext

Explanation: A message with the text of message textwas directed to a session that no longer exists. Thesession had a VTAM RRB (Request Reply Buffer) thatwas discarded once the session ended.

System action: Normal processing continues.

User response: Check for related VTAM orcoordinating address space (CAS) messages that couldindicate a problem. If none are issued, this is anisolated occurrence and no action is required.

BBCxxnnn messages


BBCSD005E PROGRAMMING SEQUENCE ERRORON RECEIVE FOR HALF SESSIONhsID, WHERE RH=rh AND DATA=data.INVALID STATE OCCURRED WITHSENSE OF code WHEN LU=luID withCID=cid HAD STATUS=xx ANDEVENT=n WITH CHAIN=a.

Explanation: A programming sequence error with asense code of code occurred for half session hsID. Thehalf session was on LU luID with a status of xx andattempted to process event n with a chain value of awhen the error occurred. See Sense code values onpage 10 for possible sense code values.

The half session ID, hsID, is an internal valuerepresenting the coordinating address space'sconnection to VTAM, which is half of a session betweentwo CASs. The error occurred while the CAS wasattempting to process an RU (VTAM request unit),which contains two parts: an RH (request header) anddata. In this case the RH value was rh and the datavalue was data.

The luID value is the LU6.2 conversation ID. The CID(connection identifier) value for the LU is cid, which is a4-byte field.

Possible values for the half session status, xx, are:00 Between chain01 In chain02 Negative response sent03 Pending response04 Pending send reply

Possible values for the event, n, are:0 Receive request to begin chain1 Receive request to end chain, definite

response2 Receive request to end chain, exception

response with conditional end bracket3 Receive request to end chain, exception

response with change direction4 Receive request to end chain, Begin Input

Sequence5 Send a negative response, Function

Management Data with LU status6 Send a positive response, Function

Management Data with LU status7 Send a response of ready to receive8 Send a request reply9 Receive a request to begin chain10 Receive a request to not begin chain

Possible chain values, a, are:0 Begin chain1 End chain2 Not specified

System action: The system responds depending uponthe half session status, event, and chain combination.The half session is canceled and, as a result, thepartner half session on the other CAS also is canceled.

Any conversations on the session are terminated.


BBCSD006E PROGRAMMING SEQUENCE ERRORON SEND FOR HALF SESSION hsID,WHERE RH=rh AND DATA=data.INVALID STATE OCCURRED WITHSENSE OF .code WHEN LU=luID WITHCID=cid HAD STATUS=xx ANDEVENT=n WITH CHAIN=a.

Explanation: A programming sequence error with asense code of code occurred for half session hsID. Thehalf session was on LU luID with a status of xx andattempted to process event n with a chain value of awhen the error occurred. See Sense code values onpage 10 for possible sense code values.

The half session ID, hsID, is an internal valuerepresenting the coordinating address space (CAS)'sconnection to VTAM, which is half of a session betweentwo CASs. The error occurred while the CAS wasattempting to process an RU (VTAM request unit),which contains two parts: an RH (request header) anddata. In this case the RH value was rh and the datavalue was data.

The luID value is the LU6.2 conversation ID. The CID(connection identifier) value for the LU is cid, which is a4-byte field.

Possible values for the half session status, xx, are:00 Between chain01 In chain02 Negative response received03 Pending response04 Pending receive reply

Possible values for the event, n, are:0 Receive request to begin chain1 Receive request end chain, definite response2 Receive request to end chain, exception

response with conditional end bracket3 Receive request to end chain, exception

response with change direction4 Receive request to end chain, Begin Input

Sequence5 Send a negative response, Function

Management Data with LU status6 Send a positive response, Function

Management Data with LU status7 Send a response of ready to receive8 Send a request reply

Possible chain values, a, are:0 Begin chain1 End chain2 Not specified

BBCxxnnn messages


System action: The system responds depending uponthe half session status, event, and chain combination.The half session is canceled and, as a result, thepartner half session on the other CAS also is canceled.Any conversations on the session are terminated.


BBCSI001E LDISP FAILED, RC=n, REASONCODE=reason

Explanation: A communications manager LDISP (localdispatch) function has failed while the functionattempted to schedule a receive. The return code isindicated by n and is always a value of 8, which occurswhen the user terminates suddenly (x22) while thecoordinating address space (CAS) is attempting to senddata to the user.

Possible reason code values, reason, are:0101 Nonzero reserved field0102 Unsupported version ID0201 Nonzero reserved field0202 Invalid or conflicting options0203 Invalid target memory ID0301 Nonconnected memory0302 System work cell size is less than the minimum

allowed0303 Unable to obtain work cell0304 Local dispatcher not active

System action: The system ignores that it cannotschedule a receive for the user and waits for the user toterminate. If the problem is not due to an x22, the usermay experience a loss of data. This error may lead toother processing errors and cause synchronizationproblems.

User response: If the reason code (reason) is 0301,ignore this message. For all other reason codes, contactyour IBM Support Center with any of the informationthat is available from the list shown in Diagnosticinformation for BB messages on page 5.

BBCSI002E INVALID RECEIVE, DATA=data

Explanation: A positive response message containingthe data data was received from the user's addressspace. No message requesting the data could belocated.

System action: The system proceeds as if the datarequest could be located. Storage used to hold the datamay not be released. This can lead to other processingerrors.

User response: Look for other messages and contactyour IBM Support Center with any of the informationthat is available from the list shown in Diagnosticinformation for BB messages on page 5.

BBCSJ001E UNABLE TO CORRELATE BINDREQUEST TO CID=cid OR TO URC=urc

Explanation: The coordinating address space (CAS)cannot locate the VTAM INIT_SELF for a bind request.Typically, a user has attempted to log on to the CASthrough VTAM directly. The bind request contains aURC (user request correlation) value of urc and isdirected at the LU with a CID (connection identifier)value of cid, which is a 4-byte field. The URC is the partof the bind request that is used to locate the originatorof a request when a response is received.

System action: The bind request is rejected. If theuser was attempting to log on, the logon is rejected.

User response: Access to the CAS should beattempted through TSO, if the user was attempting tolog on. If this message is issued for any other reason,look for other messages and contact your IBM SupportCenter with any of the information that is available fromthe list shown in Diagnostic information for BBmessages on page 5.

BBCSJ002E UNABLE TO CORRELATE BINDRESPONSE TO CID=cid OR TOURC=urc

Explanation: The coordinating address space (CAS)cannot locate the VTAM INIT_SELF for a bindresponse. This is a programming error. The bindresponse contains a URC (user request correlation)value of urc and is directed at the LU with a CID(connection identifier) value of cid, which is a 4-bytefield. The URC is the part of the bind response that isused to locate the originator of a request for theresponse.

System action: The bind response is rejected.


BBCSJ003E UNABLE TO CORRELATE BINDRESPONSE TO CID=cid

Explanation: The coordinating address space (CAS)cannot locate the VTAM INIT_SELF for a bindresponse. This is a programming error. The bindresponse is directed at the LU with a CID (connectionidentifier) value of cid, which is a 4-byte field.

System action: The bind response is rejected.


BBCxxnnn messages


BBCSJ004E UNBIND FAILED FOR CID=cid, RC='n'

Explanation: When the coordinating address space(CAS) attempted to unbind the session with the CID(connection identifier) value of cid, the internal VTAMunbind routine failed with a return code of n. The cid isa 4-byte field. Typically, this problem is caused whenthe session does not exist because VTAM hasterminated the session. Possible return code values, n,are:4 Could not obtain storage for RPL8 TERMSESS failed

System action: The system proceeds as if the unbindwas accepted.

User response: Correct the error by referring to theVTAM Programming manual for information about thereturn code value. Also look for VTAM messagesindicating VTAM failures that may have caused thisproblem.

BBCSJ006S UNABLE TO LOCATE SSCP PCB

Explanation: When processing a message, the SSCPPCB internal control block that points to VTAM could notbe located.

System action: The coordinating address space(CAS) cannot communicate with other address spaces.The message being processed when this error occurredis not issued. User sessions can malfunction.

User response: Restart the CAS. If the problempersists, contact your IBM Support Center with any ofthe information that is available from the list shown inDiagnostic information for BB messages on page 5.

BBCSJ007S UNABLE TO LOCATE SSCP PCB

Explanation: When processing a message, the SSCPPCB internal control block that points to VTAM could notbe located.

System action: The coordinating address space(CAS) cannot communicate with other address spaces.The message being processed when this error occurredis not issued. User sessions can malfunction.

User response: Restart the CAS. If the problempersists, contact your IBM Support Center with any ofthe information that is available from the list shown inDiagnostic information for BB messages on page 5.

BBCSJ008W A VTAM OPEN FOR ACB applid FAILEDWITH AN ERROR CODE OF X'nnnn'

Explanation: VTAM is reporting to the coordinatingaddress space (CAS) that an OPEN of an ACB with theapplication ID of applid failed with an error code ofnnnn. The CAS had attempted to open the ACB toconnect to VTAM. The applid is a 1- to 8-charactervalue.

System action: Communications with other CASs isnot possible. The CAS automatically retries the OPENof the ACB.

User response: Correct the problem associated withthe indicated OPEN error code. Error codes arediscussed in the VTAM Programming manual in theOPEN macro instruction section.

BBCSJ009E LOAD FOR module FAILED, ZERR=n

Explanation: The coordinating address space (CAS)cannot open its own VTAM ACB during processingbecause the program module is required and it couldnot be loaded. The n value describes the internal loadfailure that occurred. This is an 8-character valuecomprised of:v Componentv Modulev Function in process at the time of the failurev Return code or reason the request was rejectedSystem action: Until the ACB can be opened,communications with local system address spaces arepermitted; however, no cross-system communicationsare supported.

User response: Check to see if one of the followingproblems is the cause of this error:

v An I/O errorv The module is missing due to an incomplete installv The STEPLIB DD statement is defined incorrectly or

is missing in the CAS PROC

If the problem persists, contact your IBM SupportCenter with this message text and any of theinformation that is available from the list shown inDiagnostic information for BB messages on page 5.

BBCSJ010W DELETE FOR module FAILED, ZERR=n

Explanation: The program module loaded duringcoordinating address space (CAS) processing to openthe VTAM ACB was not deleted. The n value describesthe internal delete failure that occurred. This is an8-character value comprised of:v Componentv Modulev Function in process at the time of the failurev Return code or reason the request was rejectedSystem action: The CAS functions as if the modulewas deleted and continues processing.

User response: Contact your IBM Support Center withthis message text and any of the information that isavailable from the list shown in Diagnostic informationfor BB messages on page 5.

BBCxxnnn messages


BBCSJ011S ALL SAVEAREAS ARE IN USE

Explanation: Only two saveareas are required forVTAM but a third savearea is being requested.

System action: The system abends.

User response: Restart the coordinating addressspace (CAS) and contact your IBM Support Center withthis message text and any of the information that isavailable from the list shown in Diagnostic informationfor BB messages on page 5.

BBCSJ012W TPEND EXIT ENTERED FOR applid,REASON CODE IS xx

Explanation: VTAM is calling the TPEND exit forapplication ID applid. This can happen if VTAM isabending or applid has been varied inactive.

System action: The coordinating address space(CAS) closes its application ID and automatically retriesthe ACB for applid.

User response: See VTAM Programming in the UsingExit Routines chapter under TPEND Exit Routine for anexplanation of the reason codes, then correct theproblem.

BBCSJ013W LOSTERM EXIT ENTERED FOR applidSESSION WITH CID=cid AND URC=urc,REASON CODE IS reason

Explanation: VTAM is calling the LOSTERM exit forthe session with a connection identifier (CID) value ofcid and a user request correlation (URC) value of urcfor application applid.

The cid is a 4-byte field. The URC is used to locate theoriginator of a request for the response. VTAM is callingthe LOSTERM exit for the reason identified in reason.

System action: Any active conversations on thesession are terminated.

User response: See VTAM Programming in the UsingExit Routines chapter under LOSTERM Exit Routine foran explanation of the reason code, then correct theproblem.

BBCSJ014W A VTAM CLOSE FOR ACB applidFAILED WITH AN ERROR CODE OFX'nnnn'

Explanation: VTAM is reporting to the coordinatingaddress space (CAS) that a CLOSE of an ACB with theapplication ID of applid failed with an error code ofnnnn. The CAS had attempted to close the ACB todisconnect from VTAM. The applid is a 1- to 8-charactervalue.

System action: The CAS proceeds as if the CLOSEwas successful. Potential problems can occur if the

CAS later attempts to reopen the ACB application IDdefined as applid.

User response: Correct the problem associated withthe indicated CLOSE error code. Error codes arediscussed in VTAM Programming in the CLOSE macroinstruction section. If the problem persists, contact yourIBM Support Center.

BBCSJ015I The RPL macro encountered an errorwhile attempting operation on applidapplid for destination destination.Detected by module module.

Explanation:

System action: None.

User response: Certain debugging modes cause allVTAM requests to be traced. More messages mayfollow.

BBCSJ016E R0=rrrr, R15=ssss, FDBK=ffff,FDBK2=kkkk

Explanation: This message is issued only for Version3.1. This message is a continuation of messageBBCSJ015W.

v rrrr is R0 from VTAMv ssss is R15 from VTAMv ffff is the RPL FDBKv kkkk is the RPL FDBK2System action: None.

User response: None at this time. More messagesmay follow.

BBCSJ017W MODULE module HAS DETECTED ANUNEXPECTED EVENT FOR DATA=data,RC='nnnn'

Explanation: A programming error has occurred. Themodule module detected the error that had a returncode of nnnn for the associated data at storage locationdata.

System action: The individual modules will notprocess their requests. Other errors and sessionoutages can occur as a result.

User response: Contact your IBM Support Center withthis message text and any of the information that isavailable from the list shown in Diagnostic informationfor BB messages on page 5.

BBCSJ018I SYSTEM UNDER STRESS

Explanation: A predefined, internal limit on theamount of storage that the communications managercan use has been exceeded.

System action: The communications manager stops

BBCxxnnn messages


accepting requests until messages currently in itscontrol space can be delivered.

User response: If the problem persists, contact yourIBM Support Center with any of the information that isavailable from the list shown in Diagnostic informationfor BB messages on page 5.

BBCSJ019W UNBIND NOT PROCESSED FORCID=cid ON PATH path

Explanation: The coordinating address space (CAS)was attempting to end a session by processing anunbind on path path with the CID (connection identifier)value of cid. The cid value is a 4-byte field. The unbindrequest cannot be processed because the session hasalready ended or because a TPEND has occurred onVTAM. The path value is the path control ID for the LUassociated with the session.

System action: The CAS proceeds as if the unbindwas successful.


BBCSJ020E MODULE module DETECTED A TIMERSERVICE FAILURE WITH AN INTERNALERROR of n

Explanation: The coordinating address space (CAS)could not OPEN its own VTAM ACB during processing,so a timer service is automatically set to retry the OPENof the ACB. The module module detected that theattempt to set the timer service failed with an internalerror of n.

BBCxxnnn messages


The internal error, n, is an 8-character value comprisedof:v Componentv Modulev Function in process at the time of the failurev Return code or reason the request was rejectedSystem action: Until the ACB can be opened,communication with local system address spaces ispermitted; however, no cross-system communication issupported.

User response: If the problem does not correct itself,restart the CAS. If the problem persists, contact yourIBM Support Center with this message text and any ofthe information that is available from the list shown inDiagnostic information for BB messages on page 5.

BBCSJ021W LOCAL CAS(ssid) USINGAPPLID(applid1) IS UNABLE TOCOMMUNICATE WITH REMOTE CASAT DESTINATION applid2

Explanation: During initialization or execution, thelocal CAS with a subsystem ID of ssid and a VTAMapplication ID of applid1 could not communicate with aremote CAS having a VTAM application ID of applid2.

The local CAS, using VTAM application applid1,attempted to establish communication with a definedremote CAS known to the local CAS as applid2. Thismessage issues for each remote CAS the local CAScannot connect to, where applid2 is a unique VTAMapplication ID for each remote CAS. When a remoteCAS becomes available and the local CAS canestablish communication, message BBCSJ022I isissued for the remote CAS.

When the local CAS is already active and hascommunications established with remote CASs, thismessage is issued when communications are disruptedbecause a remote CAS, with a VTAM application ID ofapplid2, becomes unavailable for some reason. When aremote CAS becomes available again and the localCAS can establish communications, messageBBCSJ022I is issued for the remote CAS.

Possible reasons that the local CAS cannotcommunicate with a remote CAS include:

v The remote CAS is not initializedv The local CAS's VTAM application, applid1, is not

active

v The VTAM Cross-Domain Resource Manager(CDRM) definition for the remote CAS's VTAMapplication, applid2, is not correctly defined

v The remote CAS's VTAM application, applid2, isactive on the local CAS system known as ssid, ratherthan the remote system

System action: The local CAS cannot establishcommunications with the remote CAS having a VTAMapplication name of applid2.

User response: Perform the following to determinethe nature of the communication problem and thencorrect it:

v Check the MVS system for the remote CAS to see ifthe CAS is active. If the remote CAS is not active,start the remote CAS on the correct system.

v Determine if the local CAS's VTAM application knownas applid1 is active. If applid1 is not active, use theVTAM VARY command to vary the application active.

v Determine if the VTAM CDRM definition for theremote CAS's VTAM application, applid2, is correctlydefined.

v Determine if the remote CAS's VTAM application,applid2, is active on the local CAS system, ssid. Ifapplid2 is active on the local CAS system, use theVTAM VARY command to inactivate the applicationon ssid, and then access the remote system and usethe VTAM VARY command to activate the applicationon the remote system.

If the problem persists, contact your IBM SupportCenter.

BBCSJ022I COMMUNICATION BETWEEN LOCALCAS(ssid) USING APPLID(applid1) ANDREMOTE CAS AT DESTINATION applid2IS NOW ACTIVE

Explanation: The local coordinating address space(CAS) with a subsystem ID of ssid and a VTAMapplication ID of applid1 has establishedcommunications with a remote CAS havin

cicsplex sm messages and codes - ibm - united states 1. directly-connectable cics systems by...

Documents