Messages With Identifiers - TIBCO Software · 2012-07-31 · TIBCO Object Service Broker Messages With Identifiers |vii Preface TIBCO® Object Service Broker is an application development

TIBCO® Object Service Broker

Messages With IdentifiersSoftware Release 6.0July 2012

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDEDOR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITEDADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLEDSOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FORANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF ALICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSEAGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USERLICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THESOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARELICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATEDIN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMSAND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND ANAGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws andtreaties. No part of this document may be reproduced in any form without the written authorization of TIBCOSoftware Inc.TIBCO, The Power of Now, TIBCO Object Service Broker, and and TIBCO Service Gateway are either registeredtrademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALLOPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAMETIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFICOPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BEINCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKEIMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED INTHIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDINGBUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.The TIBCO Object Service Broker technologies described herein are protected under the following patentnumbers:Australia: - - 671137 671138 673682 646408Canada: 2284250 - - 2284245 2284248 2066724Europe: - - 0588446 0588445 0588447 0489861Japan: - - - - - 2-513420USA: 5584026 5586329 5586330 5594899 5596752 5682535

Copyright © 1999-2012 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiTIBCO Object Service Broker Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Using Messages With Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Identifier Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Resolving Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

AD: Adabas Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

BA: Batch Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

BC: Various Offline Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

BL: Batch Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

BP: Pagestore Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

BT: Segment Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

BU: Batch Unload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

BX: Batch Secondary Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

CF: Configuration Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

CM: General Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

CS: CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

DA: Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

DB: File Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

DC: IMS TM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

DD: DB2 - DOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

DM: CA Datacom server, utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

DP: Execution Environment print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

DR: Execution Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

TIBCO Object Service Broker Messages With Identifiers

iv | Contents

D2: DB2 Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

EE: Execution Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

HM: Hawk Microagent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

IC: IMS/DB Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

ID: CA IDMS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

IM: IMS/DB Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

JX: Journal Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

KA: DOB Query Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

KC: DOB Communication Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

KF: DOB Commit Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

KL: Lock Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

KP: DOB Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

KQ: Ready To Use Queue Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

KR: DOB Redo Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

KS: DOB Supervisor Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

KX: DOB Checkpoint Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

MN: osMon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

MS: Message Switch Address Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

NC: Network Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

OU: Open Transaction Mgr Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

PF: Journal Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

PR: EE Parameter Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

PX: POSIX ON support for EMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

RA: TCP/IP RELAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

RE: Communications RELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

RT: EE Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

SB: Segment Balance Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

SI: SVC Install Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

SK: ODBC Gateway/Oracle Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

SM: Session Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

SP: External Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

SS: UNIX System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

ST: Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

SV: Batch Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

TA: TDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

TB: TDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449


Contents | v

TC: TDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .450

TD: TDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .452

TE: TDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .453

TF: TDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .454

TG: TDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .455

TH: TDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .456

TK: TRACKER Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459

TL: DOB Support Offline Utils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .460

TR: TDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .483

TS: TDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .491

TW: TDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .494

TY: ostty Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .495

UA: DOB Application Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .496

UB: DOB File Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .504

UC: DOB Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .506

UL: Data Object Broker (DOB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .508

UM: HCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .536

UN: DOB Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .543

UR: DOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .544

US: DOB Supervisor Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .547

UX: DOB Checkpoint Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .554

XC: Cross-Memory Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .559


vi | Contents


| vii

Preface

TIBCO® Object Service Broker is an application development environment andintegration broker that bridges legacy and non-legacy applications and data.

This manual describes the messages with idenfiers that are issued by TIBCOObject Service Broker.

Topics

• Related Documentation, page viii

• Typographical Conventions, page xiii

• Connecting with TIBCO Resources, page xvi


viii | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Object Service Broker DocumentationThe following documents form the TIBCO Object Service Broker documentationset:

Fundamental Information

The following manuals provide fundamental information about TIBCO ObjectService Broker:

• TIBCO Object Service Broker Getting Started Provides the basic concepts andprinciples of TIBCO Object Service Broker and introduces its components andcapabilities. It also describes how to use the default developer’s workbenchand includes a basic tutorial of how to build an application using the product.A product glossary is also included in the manual.

• TIBCO Object Service Broker Messages with Identifiers Provides a listing of theTIBCO Object Service Broker messages that are issued with alphanumericidentifiers. The description of each message includes the source andexplanation of the message and recommended action to take.

• TIBCO Object Service Broker Messages without Identifiers Provides a listing ofthe TIBCO Object Service Broker messages that are issued without a messageidentifier. These messages use the percent symbol (%) or the number symbol(#) to represent such variable information as a rules name or the number ofoccurrences in a table. The description of each message includes the sourceand explanation of the message and recommended action to take.

• TIBCO Object Service Broker Quick Reference Presents summary information foruse in the TIBCO Object Service Broker application developmentenvironment.

• TIBCO Object Service Broker Shareable Tools Lists and describes the TIBCOObject Service Broker shareable tools. Shareable tools are programs suppliedwith TIBCO Object Service Broker that facilitate rules language programmingand application development.

• TIBCO Object Service Broker Release Notes Read the release notes for a list ofnew and changed features. This document also contains lists of known issuesand closed issues for this release.


Preface | ix

Application Development and Management

The following manuals provide information about application development andmanagement:

• TIBCO Object Service Broker Application Administration Provides informationrequired to administer the TIBCO Object Service Broker applicationdevelopment environment. It describes how to use the administrator’sworkbench, set up the development environment, and optimize access to thedatabase. It also describes how to manage the Pagestore, which is the nativeTIBCO Object Service Broker data store.

• TIBCO Object Service Broker Managing Data Describes how to define,manipulate, and manage data required for a TIBCO Object Service Brokerapplication.

• TIBCO Object Service Broker Managing External Data Describes the TIBCOObject Service Broker interface to external files (not data in external databases)and describes how to define TIBCO Object Service Broker tables based onthese files and how to access their data.

• TIBCO Object Service Broker National Language Support Provides informationabout implementing the National Language Support in a TIBCO ObjectService Broker environment.

• TIBCO Object Service Broker Object Integration Gateway Provides informationabout installing and using the Object Integration Gateway which is theinterface for TIBCO Object Service Broker to XML, J2EE, .NET and COM.

• TIBCO Object Service Broker for Open Systems External EnvironmentsProvides information on interfacing TIBCO Object Service Broker with theWindows and Solaris environments. It includes how to use SDK (C/C++) andSDK (Java) to access TIBCO Object Service Broker data, how to interface toTIBCO Enterprise Messaging Service (EMS), how to use the TIBCO ServiceGateway for WMQ, how to use the Adapter for JDBC-ODBC, and how toaccess programs written in external programming languages from withinTIBCO Object Service Broker.

• TIBCO Object Service Broker for z/OS External Environments Providesinformation on interfacing TIBCO Object Service Broker to various externalenvironments within a TIBCO Object Service Broker z/OS environment. Italso includes information on how to access TIBCO Object Service Broker fromdifferent terminal managers, how to write programs in external programminglanguages to access TIBCO Object Service Broker data, how to interface toTIBCO Enterprise Messaging Service (EMS), how to use the TIBCO ServiceGateway for WMQ, and how to access programs written in externalprogramming languages from within TIBCO Object Service Broker.


x | Related Documentation

• TIBCO Object Service Broker Parameters Lists the TIBCO Object Service BrokerExecution Environment and Data Object Broker parameters and describestheir usage.

• TIBCO Object Service Broker Programming in Rules Explains how to use theTIBCO Object Service Broker rules language to create and modify applicationcode. The rules language is the programming language used to access theTIBCO Object Service Broker database and create applications. The manualalso explains how to edit, execute, and debug rules.

• TIBCO Object Service Broker Managing Deployment Describes how to submit,maintain, and manage promotion requests in the TIBCO Object Service Brokerapplication development environment.

• TIBCO Object Service Broker Defining Reports Explains how to create bothsimple and complex reports using the reporting tools provided with TIBCOObject Service Broker. It explains how to create reports with simple featuresusing the Report Generator and how to create reports with more complexfeatures using the Report Definer.

• TIBCO Object Service Broker Managing Security Describes how to set up, use,and administer the security required for an TIBCO Object Service Brokerapplication development environment.

• TIBCO Object Service Broker Defining Screens and Menus Provides the basicinformation to define screens, screen tables, and menus using TIBCO ObjectService Broker facilities.

• TIBCO Service Gateway for Files SDK Describes how to use the SDK providedwith the TIBCO Service Gateway for Files to create applications to accessAdabas, CA Datacom, and VSAM LDS data.

System Administration on the z/OS Platform

The following manuals describe system administration on the z/OS platform:

• TIBCO Object Service Broker for z/OS Installing and Operating Describes how toinstall, migrate, update, maintain, and operate TIBCO Object Service Broker ina z/OS environment. It also describes the Execution Environment and DataObject Broker parameters used by TIBCO Object Service Broker.

• TIBCO Object Service Broker for z/OS Managing Backup and Recovery Explainsthe backup and recovery features of OSB for z/OS. It describes the keycomponents of TIBCO Object Service Broker systems and describes how youcan back up your data and recover from errors. You can use this information,along with assistance from TIBCO Support, to develop the best customizedsolution for your unique backup and recovery requirements.


Preface | xi

• TIBCO Object Service Broker for z/OS Monitoring Performance Explains how toobtain and analyze performance statistics using TIBCO Object Service Brokertools and SMF records

• TIBCO Object Service Broker for z/OS Utilities Contains an alphabeticallyordered listing of TIBCO Object Service Broker utilities for z/OS systems.These are TIBCO Object Service Broker administrator utilities that aretypically run with JCL.

System Administration on Open Systems

The following manuals describe system administration on open systems such asWindows or UNIX:

• TIBCO Object Service Broker for Open Systems Installing and OperatingDescribes how to install, migrate, update, maintain, and operate TIBCOObject Service Broker in Windows and Solaris environments.

• TIBCO Object Service Broker for Open Systems Managing Backup and RecoveryExplains the backup and recovery features of TIBCO Object Service Broker forOpen Systems. It describes the key components of a TIBCO Object ServiceBroker system and describes how to back up your data and recover fromerrors. Use this information to develop a customized solution for your uniquebackup and recovery requirements.

• TIBCO Object Service Broker for Open Systems Utilities Contains analphabetically ordered listing of TIBCO Object Service Broker utilities forWindows and Solaris systems. These TIBCO Object Service Brokeradministrator utilities are typically executed from the command line.

External Database Gateways

The following manuals describe external database gateways:

• TIBCO Service Gateway for DB2 Installing and Operating Describes the TIBCOObject Service Broker interface to DB2 data. Using this interface, you canaccess external DB2 data and define TIBCO Object Service Broker tables basedon this data.

• TIBCO Service Gateway for IDMS/DB Installing and Operating Describes theTIBCO Object Service Broker interface to CA-IDMS data. Using this interface,you can access external CA-IDMS data and define TIBCO Object ServiceBroker tables based on this data.

• TIBCO Service Gateway for IMS/DB Installing and Operating Describes theTIBCO Object Service Broker interface to IMS/DB and DB2 data. Using thisinterface, you can access external IMS data and define TIBCO Object ServiceBroker tables based on it.


xii | Related Documentation

• TIBCO Service Gateway for ODBC and for Oracle Installing and OperatingDescribes the TIBCO Object Service Broker ODBC Gateway and the TIBCOObject Service Broker Oracle Gateway interfaces to external DBMS data.Using this interface, you can access external DBMS data and define TIBCOObject Service Broker tables based on this data.


Preface | xiii

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

OSB_HOME

By default, all TIBCO products are installed into a folder referenced in thedocumentation as TIBCO_HOME.

On open systems, TIBCO Object Service Broker installs by default into adirectory within TIBCO_HOME. This directory is referenced in documentation asOSB_HOME. The default value of OSB_HOME depends on the operating system.For example on Windows systems, the default value is C:\tibco\OSB. Similarly,all TIBCO Service Gateways on open systems install by default into a directoryin TIBCO_HOME. For example on Windows systems, the default value isC:\tibco\OSBgateways\6.0.

On z/OS, no default installation directories exist.

code font Code font identifies commands, code examples, filenames, pathnames, andoutput displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font

Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are ofparticular interest.

• In command syntax, to indicate the default parameter for a command. Forexample, if no parameter is specified, MyCommand is enabled:MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrixBusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain severalportlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace.For example: MyCommand PathName


xiv | Typographical Conventions

Keycombinations

Key name separated by a plus sign indicate keys pressed simultaneously. Forexample: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after theother. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, forexample, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to applythe information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example,data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3


Preface | xv

{ } A logical group of items in a command. Other syntax notations may appearwithin each logical group.

For example, the following command requires two parameters, which can beeither the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parametercan be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters.The first parameter must be param1. You can optionally include param2 as thesecond parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}

Table 2 Syntax Typographical Conventions

Convention Use


xvi | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, andresident experts, a place to share and access the collective experience of theTIBCO community. TIBCOmmunity offers forums, blogs, and access to a varietyof resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, pleasecontact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting startedwith TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a username, you can request one.


http://www.tibco.com/services/support

https://support.tibco.com

http://docs.tibco.com

http://www.tibcommunity.com

| 1

Using Messages With Identifiers

This chapter describes how to make use of the messages with identifiers that areissued by TIBCO Object Service Broker.

Topics

• Introduction, page 2


2 | Using Messages With Identifiers

Introduction

This manual belongs in the set of documentation for the TIBCO Object ServiceBroker Integration Foundation product.

Identifier SyntaxThe messages with identifiers have the following form:

S6Baaxxxq: mmm

where the variables mean the following:

ComponentsThe table below describes the relationship of the 2- letter component identifiersand the product component associated with the message:

Variable Description

aa Two characters that identify the TIBCO Object Service Brokercomponent that issued the message. See the table in theComponents section.

xxx Message number

q Severity of error. Valid values: A–Action; E–Explanation;I–Information; L–Logging only; R–Reply; W–Warning.

mmm Message text

Identifier Component Description

AD @ADA ADABAS Gateway

BA @BA Batch Archive

BC @BC Various Offline Utilities

BL @BL Batch Load

BP @BP Page Store Validation


Introduction | 3

BT @BT Segment Reset

BU @BU Batch Unload

BX @BX Batch Secondary Index

CF @CF Configuration Processing

CE @CHGRULE CHANGERULE tool

CL @CL Client Defaults Editor

CM @CM General Communications

CS @CS CICS

DA @DA Dynamic Allocation

DB @DB File Task

DC @DC IMS/DC

DD @DD DB2 - Data Object Broker

DM @DM Service Gateway for CA-Datacom andutilities

DP @DP Execution Environment print

DR @DR Execution Environment

D2 @D2 Service Gateway for DB2

EE @EE Execution Environment

IC @IC Service Gateway for IMS

ID @ID Service Gateway for CA-IDMS

IM @IM Service Gateway for IMS

KA @KA Data Object Broker Query Task

KC @KC Data Object Broker Communication Task

KF @KF Data Object Broker Commit Task




KL @KL Lock Manager

KP @KP Data Object Broker Operator Tasks

KR @KR Data Object Broker Redo Tasks

KS @KS Data Object Broker Supervisor Tasks

KX @KX Data Object Broker Checkpoint Tasks

MC @MC Model 204 - Data Object Broker

MN @MN osMon

MS @MS Message Switch Address Space

NC @NC Network Control

OS @OBJECTSERVER Object Server

PC @PC TCP/IP Control

PF @PF Journal Formatting

PR @PR Execution Environment ParameterProcessing

RT @RT Execution Environment Resources

SB @SB Segment Balance Utility

SI @SI SVC Install Program

SK @SLK Service Gateway for ODBCService Gateway for Oracle

SM @SM Session Manager

SP @SP External Servers

SS @SS UNIX System Services

ST @ST Storage Management

SV @SV Batch Server



Introduction | 5

TA @TA TDS

TB @TB TDS

TC @TC TDS

TD @TD TDS

TE @TE TDS

TF @TF TDS

TG @TG TDS

TH @TH TDS

TL @TL Data Object Broker Support OfflineUtilities

TR @TR TDS

TS @TS TDS

TW @TW TDS

TY @TY ostty client

UA @UA Data Object Broker Application Tasks

UB @UB Data Object Broker File Tasks

UC @UC Data Object Broker Communications

UL @UL Data Object Broker (DOB)

UM @UM HCS

UN @UN Data Object Broker Administration Tasks

UQ @UP HRNTLADM

UR @UR Data Object Broker

US @US Data Object Broker Supervisor Tasks

UX @UX Data Object Broker Checkpoint Tasks




Resolving IssuesThe information about messages in the following pages present information tohelp you recover. Refer to the Action entries.

If you need more help, you may want to contact TIBCO Support.

How to Contact TIBCO SupportRefer to How to Contact TIBCO Support on page xvi.

XC @XC Cross-Memory Control



| 7

AD: Adabas Server

S6BAD001ENo more locks can be taken by ADABAS - (Respcode % Command code %)

Source: Adabas Server

Explanation: Maximum number of locks that canbe taken by an ADABAS user has beenexceeded.

Action: Either adjust the ADABAS systemparameter to allow more locks to be taken oramend the program to release the locks bystarting a new transaction.

S6BAD002EFile OPEN error - (Resp code % Command code%)


Explanation: An error has occurred duringOPEN processing.

Action: Determine the cause of the problem fromthe ADABAS Response code.

S6BAD003EUnexpected error encountered - (Resp code %Command code %)


Explanation: An unexpected Response code wasreceived by the ADABAS server.

Action: Determine the cause of the error from theADABAS Response code.

S6BAD004EFile CLOSE error - (Resp code % Commandcode %)


Explanation: An error occurred during CLOSEprocessing.


S6BAD005EError encountered during SEARCH processing -(Resp code % Command code %)


Explanation: An error has occurred whileselecting data from ADABAS.


S6BAD006EError during DELETE - (Resp code % Commandcode %)


Explanation: An error has occurred when tryingto delete data from ADABAS.

Action: Determine the cause of the problem fromthe ADABAS response code.


8 |

S6BAD007EError during INSERT - (Resp code % Commandcode %)


Explanation: An error has occurred wheninserting data to ADABAS.


S6BAD008EError during ROLLBACK - (Resp code %Command code %)


Explanation: An error occurred when trying toroll back update requests from ADABAS.


S6BAD009EError during UPDATE - (Resp code %Command code %)


Explanation: An error has occurred whenattempting to update data in ADABAS.


S6BAD012ELOCKFAIL - ADABAS resource not available -(Resp code % Command code %)


Explanation: A LOCKFAIL condition occurredbecause another user is already using therequested resource.

Action: Determine the cause of the error from theADABAS Response code.

S6BAD014ERunaway task limit exceeded - Read terminated


Explanation: The server has detected that themaximum number of sequential reads to onetable has been exceeded.

Action: Either correct the application logic toprevent this condition occurring or increasethe server parameter RUNAWAY via the@CONFIGURESERVER tool.

S6BAD015ESearch Predicates cannot include nulls or zerolength fields. Predicate % contains a null.


Explanation: A search argument passed to theADABAS server contains a NULL value.ADABAS has no concept of a NULL value, sothe server is unable to translate this requestinto a valid ADABAS request.

Action: Correct the application logic to prevent aNULL being used in an ADABAS serveraccess request.

S6BAD084EWorkarea GETMAIN failed, RC=#


Explanation: The GETMAIN for the ADABASESTAE routine failed

Action: The server task is terminated. Determinethe reason for the failure from the returncode, correct the problem and restart theserver.


| 9

S6BAD085IDBID cursor work area size=#


Explanation: Indicates the size in bytes of theDBID cursor work area

Action: None

S6BAD086EDBIDCURSOR GETMAIN FAILURE


Explanation: Storage Cannot be obtained to holdDBID list

Action: Contact TIBCO Support.

S6BAD087EADABAS Server: ESTAE establishment failure


Explanation: The ESTAE cannot be established

Action: Review additional messages in the log

S6BAD088EDBIDCURSOR SIZE NOT SUPPLIED


Explanation: ESTAE has been called incorrectly

Action: Check to see if correct version of theESTAE has been used

S6BAD089EADALNK ADDRESS NOT SUPPLIED


Explanation: ESTAE has been called incorrectly.

Action: Check to see if correct version of theESTAE has been used.

S6BAD090EWORKAREA GETMAIN FAILURE


Explanation: A getmain has failed

Action: Increase the region size and try again.

S6BAD091ISDWA not available for ADABAS serverESTAE processing


Explanation: During abnormal termination ofthe ADABAS server, the ESTAE routine wasnot provided with an SDWA from RTM. Dueto this circumstance, the ESTAE routine wasunable to report on the cause of the ABEND.

Action: No action required.

S6BAD092EADABAS Server: ESTAE processing terminated- Environment error


Explanation: During abnormal termination ofthe ADABAS server, the ESTAE routine wasunable to locate certain control blocksneeded for cleanup processing. Due to thiscircumstance, certain fixed storage pools willnot be released back to the system.

Action: Certain portions of REAL storage willremain unavailable to the system until an IPLis performed. If the amount of storageoccupied by these orphaned control blockscauses system performance problems, animmediate IPL may be required.


10 |

S6BAD093EADALNK NONZERO RETURN CODE


Explanation: When calling ADALNK anunexpected response code was received

Action: Review ADABAS log to determine whythe error occurred

S6BAD094EADABAS Server: ESTAE cancel unsuccessful


Explanation: An error occurred during ESTAEcancellation

Action: Gather the appropriate dumps andcontact TIBCO Support.

S6BAD095IAn ADABAS backout transaction has beenissued.


Explanation: The ESTAE has been invoked. Atransaction backout has been issued to cleanup any pending updates.

Action: None.

S6BAD096EADABAS Server: ESTAE parameter list notsupplied


Explanation: ESTAE has been called incorrectly

Action: Check to see if the correct version of theESTAE has been used

S6BAD097IADABAS Server: ESTAE routine entered


Explanation: The ADABAS server ESTAE hasbeen invoked during Abend processing

Action: Review addition messages to determinewhy the ESTAE has been invoked

S6BAD098IADABAS Server: ESTAE cancellation entered


Explanation: The ESTAE has been terminatedduring normal thread shutdown

Action: None

S6BAD099IADABAS Server: ESTAE activation entered


Explanation: The ADABAS server ESTAE hasbeen successfully established

Action: None


| 11

BA: Batch Archive

S6BBA001IRESTART PROCESSING REQUEST AFTERPVS SELECTION BREAK

Source: Batch Archive

Explanation: S6BBRULA is running in restartmode after a break occurred for external tableinstance processing.


S6BBA002Icount PVS ENTRIES TO RECOVERACCORDING TO BREAK POINT CONTROLRECORD


Explanation: When the process was interruptedto allow external table instance selection, acontrol record was generated containing thenumber of table instances. This messagedisplays the total number of table instancesso that you can verify that the restart is usingthe correct file.


S6BBA003Icount PVS ENTRIES RECOVERED AFTERBREAK POINT


Explanation: This message displays the numberof table instances that were processed in therestart processing mode.


S6BBA004Icount PVS ENTRIES IGNORED AFTERBREAK POINT


Explanation: This message displays the numberof table instances that were removed fromthe table instance break file during externalselection processing.


S6BBA005Icount DATA ENTRIES TO RECOVERACCORDING TO BREAK POINT CONTROLRECORD


Explanation: When the process was interruptedto allow external table instance selection, acontrol record was generated containing thenumber of data page entries. This messagedisplays the total number of data pageentries so that you can verify that the restartis using the correct file.


S6BBA006Icount DATA ENTRIES RECOVERED AFTERBREAK POINT


Explanation: This message displays the numberof data page entries that were processed inthe restart processing mode.



12 |

S6BBA007Icount DATA ENTRIES IGNORED AFTERBREAK POINT


Explanation: This message displays the numberof data page entries that were ignoredbecause of external table instance selection.


S6BBA011IPASS ONE PROCESSING INITIATED


Explanation: The first pass (read through) of thearchive file was initiated.


S6BBA012IPASS ONE; count RECORDS READ, countACCEPTED, count PROCESSED


Explanation: This message specifies the numberof archive records read, accepted, andprocessed. If the archive contains multiplesegments, only the correct segment pages areaccepted. If the archive containsunrecognizable pages, the processed countmay be less than the accepted count.


S6BBA013IPASS TWO PROCESSING INITIATED


Explanation: The second pass of the archiveinformation occurs only if one or more of theunloaded tables are parameterized. Pass twoprocessing reads through only those pagesthat pertain to table instances that weresaved in the pages file.


S6BBA014IGIX TABLE COMPRESSION COMPLETEINPUT=count, OUTPUT=count


Explanation: Table instance information isretained for all tables in the archive. Once therequired table instance pages are identified,all others are removed. The input count is thetotal number of table instance pages. Theoutput count is the number that are required.


S6BBA015IDATA TABLE COMPRESSION COMPLETEINPUT=count, OUTPUT=count


Explanation: When all the tables are processedand it is known which data page contains therequired information, all others areeliminated. The input count is the totalnumber of data pages. The output count isthe number of data pages that are required.



| 13

S6BBA016ITABLE INSTANCE SELECTION BREAKREQUESTED


Explanation: The BREAK run time parameterwas supplied. Therefore, processing will beinterrupted at the end of pass two.


S6BBA017Icount DATA CHAIN ENTRIES SAVED ATBREAK POINT


Explanation: At the time of the interruption (toexternally select table instances), count datapage entries were backed up to theBRKDATA file.


S6BBA018Icount PVS TABLE ENTRIES SAVED ATBREAK POINT


Explanation: At the time of the interruption (toexternally select table instances) count tableinstances were backed up to the BRKPVS file.


S6BBA019IPASS TWO; GROUP INDEX PAGES READcount, count PROCESSED


Explanation: The extracted table instance pagesare processed. Of the pages read in READcount, count were processed.


S6BBA020IPASS THREE PROCESSING INITIATED


Explanation: The third and final pass of the datais initiated. The third pass extracts allrequired data elements from the archive file.


S6BBA021IPASS THREE; count RECORDS READ, countACCEPTED, count PROCESSED


Explanation: The indicated number of recordswere read from the archive file. Of therecords read, the indicated number wereaccepted and the indicated number wereprocessed. Note that the actual number ofrecords read may be less than the recordsread in pass one. This can occur because allrequested records were retrieved before theend of the archive was reached.


S6BBA022Itablename count RECORDS UNLOADED


Explanation: There were count records unloadedfor table tablename.



14 |

S6BBA023Itablename count RECORDS UNLOADEDBEFORE PROCESSING ABORTED


Explanation: There were count records unloadedfor table tablename. Table tablename did notcomplete unloading because of an errordetected during processing. However, anyrecords unloaded prior to the error areretained in the recovery file.


S6BBA050WSELECTION RCD count; PARM parm#NUMERIC DATA INVALID; TABLEtablename


Explanation: The selection record number countfor the specified parm# of table tablenamecontains an invalid numeric. The selectionentry is ignored.

Action: Correct the selection card.

S6BBA051WSELECTION TABLE NOT FOUND;SELECTION RECORD IGNORED


Explanation: The table specified on the selectionis not among the tables to be unloaded.Following this message, the first 80 bytes ofthe selection record are displayed.

Action: Correct or remove the selection record.

S6BBA052WSELECTION TABLE NOT PARAMETERIZED;SELECTION RECORD IGNORED


Explanation: The table specified in the selectionrecord is not parameterized according to theObject Service Broker definition cards. Theselection record is ignored. Following thismessage, the first 80 bytes of the selectionrecord are displayed.

Action: Correct or remove the selection record.

S6BBA053WTOO MANY TABLES TO PROCESS; RECORDIGNORED


Explanation: More tables were detected in theObject Service Broker definition cards thanthe program was prepared to handle basedon the table count in the first control card.The rejected control card is displayed afterthis message.

Action: Divide the tables to be unloaded intosmaller groups.

S6BBA054WPROCESSING TERMINATED FOR TABLEtablename


Explanation: The specified table is ignored forthe remainder of the run because an errorwas detected.

Action: Refer to the previous message in theaudit trail to determine what the error was.


| 15

S6BBA055WACTUAL LENGTH (len) GREATER THANDEFINED LENGTH (len) ON FIELD fieldname


Explanation: The actual length of a field valuefrom the archive file is greater than the lengthof the field according to the Object ServiceBroker definition control cards.

Action: Verify that your definition is appropriatefor the time when the archive was created.

S6BBA056WMORE FIELDS DEFINED IN DATAOCCURRENCE THAN VIA DEFINITIONCONTROL CARDS


Explanation: The number of fields in an archivefile occurrence is greater than the number ofthe fields according to the Object ServiceBroker definition control cards.

Action: Verify that your definition is appropriatefor the time when the archive was created.

S6BBA057WNULL-EQUIVALENT VALUE SPECIFIED ISIGNORED


Explanation: Columns 64-79 are valid for packeddecimal and binary fields only.

Action: Columns 64-79 on this line are ignored.

S6BBA058EEXEC-PARMS HIX/GIX/PVS INCORRECT


Explanation: The Table Control File Entry beingprocessed indicates that it is a parameterizedtable. The EXEC-PARMS which requestresource allocation to process such tables areHIX, GIX and PVS. These PARMS indicatethat no parameterized tables are to beprocessed (each PARM is set to zero).

Note: If parameterized table(s) are to berecovered, all three of the above mentionedPARMS must be nonzero.

Action: Either remove the HIX, GIX and PVSEXEC-PARMS altogether (request thedefaults) or assign a percentage to eachPARM. Resubmit the request after correctingthe PARMS.

S6BBA100ESPACE NOT AVAILABLE TO RETAININFORMATION FOR XX-30-XX


Explanation: GETMAIN failed to retrievememory space to retain internal processingtables. XX-30-XX is one of the following:

• DATA PAGE

• PRIMARY INDEX PAGE

• GROUP INDEX PAGE

• UPPER GROUP INDEX PAGE

• TABLE INSTANCES

• CONTROL CARD TABLE

• TABLE INSTANCE SELECTION

• LAYOUT OF tablename

Abend code 201 is issued.

Action: Check the message log and storagelimits.


16 |

S6BBA101EFILE OPEN ERROR; XX-40-XX


Explanation: During the attempt to open the filenamed in the message, an open error wasdetected. XX-40-XX is one of the following:

• I - SEQUENTIAL ARCHIVE (ARCHIVE)202,204

• I - VSAM ARCHIVE (ARCHIVE) 202,204

• I - CONTROL CARDS (CNTRL) 201

• I - TABLE INSTANCE SAVE (CONTPVS)201

• I - DATA SAVE (CONTDATA) 201

• I - GROUP INDEX CAPTURE (PAGES)203

• O - RECOVERY FILE (RECOVER) 200

• O - GROUP INDEX CAPTURE (PAGES)202

• O - DATA SAVE (BRKDATA) 203

• O - TABLE INSTANCE SAVE (BRKPVS)203

• O - PRE-SORT WORK FILE (WORK) 204

The "I -" and "O -" represent open for inputor output respectively. The abend codesissued are 201 to 204 as listed above.

Action: Refer to the job log for more details.

S6BBA102ETABLE OVERFLOW DETECTED FOR XX-20-XX


Explanation: The named internal tableoverflowed. XX-20-XX is one of thefollowing:

• PRIMARY INDEX

• DATA PAGE

• UPPER GROUP INDEX

• GROUP INDEX

Abend code 202 is issued.

Action: Increase the number of pages, orredistribute the page concentrations by usingthe run time parameters.

S6BBA103ERESTART ERROR DETECTED; CONTROLRECORD FOR PVS NOT FOUND


Explanation: When the BRKPVS file wasgenerated in pass 2 to allow external tableinstance selection, a control record wasgenerated to indicate the number of entries.When the restart initialization processingretrieved the table instances file, the controlentry was not the first record. Abend code201 is issued.

Action: Correct the CONTPVS file.

S6BBA104ERUN TIME PARAMETER IS NOTRECOGNIZED - run_time_parm


Explanation: The indicated run time parameter isnot recognized. Abend code 201 is issued.

Action: Check the spelling of the parameter.


| 17

S6BBA105EVALUE value OUT OF RANGE (range TOrange) FOR PARAMETER - parm


Explanation: The run time parameter parmcontains a value that is outside the rangespecified in the error message. Abend code201 is issued.

Action: Correct the run time parameter.

S6BBA106ECONTROL CARD HAS AN INVALID TYPECODE (COLUMN 7)


Explanation: The control card type is notrecognized. Refer to the card image thatfollows this message in the audit trail. Abendcode 201 is issued.

Action: Correct the control card.

S6BBA107ERESTART ERROR DETECTED; CONTROLTABLE NOT FOUND FOR TABLE - tablename


Explanation: The specified table cannot be foundin the table definition which is based on thecontrol cards. Abend code 201 is issued.

Action: Ensure that the restart files (CONTPVSand CONTDATA) are the appropriate filesfor the control card file supplied.

S6BBA108ERESTART ERROR DETECTED; CONTROLRECORD FOR DATA NOT FOUND


Explanation: When the BRKDATA file wasgenerated in pass 2 (to allow external tableinstance selection), a control record wasgenerated to indicate the number of entries.When the restart initialization processingretrieved the data occurrence file, the controlentry was not the first record. Abend code201 is issued.

Action: Correct the CONTDATA file.

S6BBA109ETABLE COUNT CONTROL RECORD (TYPE"*" - COLUMN 7) NOT FOUND


Explanation: The first card expected in thecontrol card file is the table count card.During the processing of the control card file,the table count card was not found. Abendcode 201 is issued.

Action: Correct the control card file.

S6BBA110ETABLE INSTANCE PVS SELECTIONCONTROL CARD NOT FOUND


Explanation: The record in the table instanceselection file must be a control recordspecifying the number of entries. This controlrecord was not found. Abend code 201 isissued.

Action: Correct the table instance selection file.


18 |

S6BBA111EINPUT SELECTION RECORDS NOT SORTEDBY TABLE NAME


Explanation: The table instance selection was notpresorted into table name sequence. Abendcode 201 is issued.

Action: Sort the selection file by table name andrerun S6BBRULA.

S6BBA112EPARM/FIELD SEQUENCE ERRORDETECTED; TABLE NUMBER NOT EQUALTO PREVIOUS TABLE CARD


Explanation: The sequence of the parameter orfield definition cards is in error. Abend code201 is issued.

Action: Correct either the card sequencenumbers or sort the control cards again.

S6BBA113EERROR DETECTED WHEN DETERMININGARCHIVE FILE FORMAT


Explanation: When attempting to determine theorganization of the input archive file(sequential or VSAM), RDJFCB failed. Abendcode 202 or 204 is issued.

Action: Refer to the job log for furtherinformation.

S6BBA114ERESIDENT TABLE INDEX ENTRY NOTFOUND FOR TABLE - tablename


Explanation: The specified table cannot be foundin the resident table index. Abend code 202 isissued.

Action: Verify the following:

• The spelling of the table name in thecontrol cards

• The segment number in the run timeparameters

• The archive file used.

S6BBA115EARCHIVE CONTAINS WRONG SEGMENTFOR TABLE - tablename


Explanation: The specified table resides on asegment other than the one being processed.Abend code 201 is issued.

Action: Check the segment number in the runtime parameters, and verify that you havethe appropriate archive file.

S6BBA116EPAGE NUMBER (page#) NOT FOUND, INPUTPARM % INCORRECT


Explanation: One of the following has occurred:

• The specified page number is part of thenamed table's tree, but that page is not onthe archive file.

• GIX/PVS run time parameter is specifiedas 0 and the table is parameterized.

Action: Take the following actions:


| 19

• For item 1, check that you have a completearchive and/or run the archive pointervalidation process (S6BBRPTR).

• For item 2, if the table is parameterizedverify that the GIX and PVS values areentered correctly. Refer to thedocumentation for the default values.

S6BBA117EARCHIVE UNLOAD PROCESSINGTERMINATED BECAUSE OF ERROR


Explanation: All the tables to be unloaded wereeliminated because of errors. Abend code 203or 204 is issued.

Action: Correct the errors detected for each tableand rerun S6BBRULA.

S6BBA118ETABLE NUMBER CONTAINSNONNUMERIC CHARACTERS


Explanation: The table number (columns 3-5) ona T, P, F or R type of card contains an invalidnumeric character. Leading zeros arerequired.

Action: Processing is terminated. The card imageis displayed after the message.

S6BBA119EPARM/FIELD LENGTH CONTAINSNONNUMERIC CHARACTERS


Explanation: The length (columns 50-52) enteredon a parameter or field definition cardcontains an invalid numeric character.Leading zeros are required.


S6BBA120EDECIMAL POSITION CONTAINSNONNUMERIC CHARACTERS


Explanation: The decimal position (columns 54-56) entered on a parameter or field definitioncard contains an invalid numeric character.Leading zeros are required.


S6BBA121EOUTPUT OFFSET/RECORD LENGTH NOTNUMERIC


Explanation: The output offset (columns 60-63)entered on a parameter or field definitioncard contains an invalid numeric character.When you enter the offset, remember thatleading zeros are required. If calculatedoffsets are desired, the field must be blank.



20 |

S6BBA122EFIELD COUNT CONTAINS NONNUMERICCHARACTERS


Explanation: The field count (columns 54-56)entered on the table header card contains aninvalid numeric character. Leading zeros arerequired.


S6BBA123EPARAMETER COUNT CONTAINSNONNUMERIC CHARACTERS


Explanation: The parameter count (columns 50-52) entered on the table header definitioncard contains an invalid numeric character.Leading zeros are required.


S6BBA124EMEMORY REQUIREMENT CALCULATIONERROR DETECTED


Explanation: When calculating the internalmemory requirements (which are based on apercentage of the total anticipated pages), thetotal number of pages was found to be zero.Check the specification of the PAGESexecution parameter.

Action: Processing is terminated.

S6BBA125ETABLE NUMBER IS OUT OF SEQUENCE ORINVALID


Explanation: The table number (columns 3-5) iseither out of sequence, or the first tablenumber is not 000.

Action: Processing is terminated. Do thefollowing:

• Ensure that the table numbers start at 000.

• Ensure that the control cards are properlyorganized.

• For each table to be unloaded, cards mustappear in the following sequence:

1. One T card

2. Zero to four P cards

3. One to n F cards

4. One R card.

S6BBA126Etablename END RECORD CONTROLRECORD MISSING


Explanation: When validating table definitionsafter the control card file was exhausted,S6BBRULA determined that the R end oftable block record was not received for theindicated table. Either the R card wasomitted, or it is not positioned correctly inthe control card file.

Action: Processing is terminated. Correct thecontrol card file.


| 21

S6BBA127Etablename PARAMETERS DEFINITIONINVALID


Explanation: The number of parametersspecified in the header for the indicated tableis invalid, or the parameter definitioninformation is incomplete.

Action: Processing is terminated. Correct theparameters.

S6BBA128Etablename FIELDS DEFINITION INVALID


Explanation: The number of fields specified inthe header for the indicated table is invalid,or the field definition information isincomplete.

Action: Processing is terminated. Correct thefield number or definitions.

S6BBA129Etablename END RECORD LENGTH INVALID


Explanation: The text length specified in the endof table block (R type) record does not agreewith the total length of the definedparameters and fields for the table indicatedin the message.

Action: Processing is terminated. Correct thelength specified in the R record.

S6BBA130ENUMBER OF TABLES TO UNLOAD IS NOTNUMERIC


Explanation: The number of tables (columns 60to 63) specified in the table control card (type= "*") contains an invalid numeric character.Leading zeros must be specified.

Action: Processing is terminated. Correct thenumber of tables.

S6BBA131EHIX/GIX/PVS CONSISTENCY ERRORDETECTED


Explanation: The run time parameters HIX, GIX,and PVS have been entered to override thedefault page type percentage estimates. Oneor more of the parameters contains a zeroand the remainder are nonzero.

Action: Processing is terminated. If the table ortables you are unloading do not contain anyparameters, set all three to zero. Ifparameters are present, all three mustcontain positive nonzero values.

S6BBA132ETABLE SPECIFIED NO PARMS, BUT PARMSDEFINED


Explanation: Conflicting specifications forparameterized tables.

Action: Processing is terminated with ABEND201. Check the specifications. Make sure thattables are correctly defined.


22 |

S6BBA133WNULL-EQUIVALENT VALUE FOUND INTABLE ROW FIELD:


Explanation: A null equivalent value was foundin the table. This value is the value youselected to represent a null in the unloadedfile. Obviously, should you wish to load thisdata to an Object Service Broker database, theLOAD utility will be unable to distinguishbetween this value and an actual null-equivalent value. This field would be loadedas a null value.

Action: It is advisable to discard the output fromthis UNLOAD, choose a unique null-equivalent value and rerun.

S6BBA134WNULL FOUND IN "NOVALUE" (NO NULLALLOWED) FIELD:


Explanation: A field described by the controldata set as a NOVALUE or "no nullspermitted" field has a null value. It will beunloaded as zero.

Action: Determine whether this field shouldhave been described as NOVALUE, discardthe output from this run, and try again withthe correct control specifications.

S6BBA135ENULL-EQUIVALENT VALUE SPECIFIED ISINVALID


Explanation: Columns 64-79 are invalid. If thevalue entered is one of the acceptable codes(LOWVALUE, HIGHVALUE, orNOVALUE), it is probably misspelled;otherwise, it should be numeric.

Action: Check and correct.

S6BBA137EWARNING LIMIT EXCEEDED


Explanation: Null Equivalent related warningsindicate that the control data set may beincorrect.

Action: Check and correct the warnings receivedprior to this message and try again.

S6BBA140EINVALID LRECL - SELECTION


Explanation: The selection data set LRECL isincorrect.

Action: Check the documentation and correct theJCL.

S6BBA141EINVALID LRECL - ARCHIVE/SAVE/WORK


Explanation: At least one of the DDNAMESmentioned has incorrect LRECL.

Action: Check the documentation and correct theJCL.


| 23

S6BBA142EINVALID LRECL - CONTROL


Explanation: The CONTROL data set must beRECFM F or FB; LRECL 80.

Action: Correct and retry.

S6BBA143EARCHIVE RECORD EXCEEDS MAXIMUMLENGTH


Explanation: The data set supplied does notappear to be an archive.

Action: Check and if JCL is correct, contactTIBCO Support.

S6BBA144ESYNTAX/SEMANTIC TYPE COMBINATIONNOT SUPPORTED


Explanation: The semantic type and syntax codecombination on the identified definition cardis not supported.

Action: Correct the definition cards and resubmitthe job.

S6BBA145EUNICODE FIELD LENGTH MUST BE EVEN(DIVISIBLE BY 2)


Explanation: The identified definition cardcontains a field with Unicode syntax whoselength is not even. This is not supported.

Action: Correct the definition card and resubmitthe job.

S6BBA146EUNICODE PARAMETERS ARE NOTSUPPORTED


Explanation: Unicode syntax is not support for aparameter field.

Action: Correct the definition cards and run thejob again.

S6BBA255EAUDIT TRAIL FILE (PRINTER) FAILED TOOPEN


Explanation: The audit trail file would not openfor output.

Action: See the job log for additionalinformation.


24 |

BC: Various Offline Utilities

S6BBC001ETABLE ENTRY CANNOT BE LOCATED ONCONTROL PAGE

Source: Various Offline Utilities

Explanation: The table name specified in thePSTABLE parameter was greater than all thetables on the system.

Action: Check the table name specified in thePSTABLE parameter.

S6BBC002ETABLE ENTRY CANNOT BE FOUND IN RTIX


Explanation: The table specified in the PSTABLEparameter cannot be located in the ResidentTable Index.

Action: Check the table name specified in thePSTABLE parameter.

S6BBC007ETABLE POINTERS INVALID - CLEAR NOTPOSSIBLE


Explanation: The physical pointers in the tableindicated are not in a valid format; theCLEAR cannot navigate the table structure.


S6BBC101EERROR LOG FILE HEADER NOT INEXPECTED FORMAT


Explanation: S6BBRPGC - ERRORLOG fileincorrect format.

Action: S6BBRPGC requires an ERRORLOG filecreated by S6BBRPTR. Check your JCL toensure the file is correctly specified.S6BBRPGC must be run immediately afterthe S6BBRPTR which created theERRORLOG and before any activity on thesegment.

S6BBC102ESEGMENT NUMBER IN ERROR LOGHEADER IS TOO LONG


Explanation: S6BBRPGC - ERRORLOG filepossible incorrect format. The segmentnumber recorded on the file is incorrect.

Action: S6BBRPGC requires an ERRORLOG filecreated by S6BBRPTR. Check your JCL toensure file is correctly specified. S6BBRPGCmust be run immediately after theHRNBRPTR which created the ERRORLOGand before any activity on the segment.


| 25

S6BBC103EERROR LOG IS NOT FOR ACTIVE SEGMENT


Explanation: S6BBRPGC - ERRORLOG filesegment number and segment numberrequested in the PARMS are not the same.S6BBRPGC must be run immediately afterthe S6BBRPTR which created theERRORLOG and before any activity on thesegment.

Action: Correct your JCL and try again.

S6BBC104EINVALID PAGE NUMBER REQUESTED:XXXXXXXX


Explanation: S6BBRPGC - ERRORLOG filecontains an Error page pointer whichappears to be invalid.

Action: The ERRORLOG file must be current.Check that you are not running an oldERRORLOG against your segment, as thiscan have serious consequences. S6BBRPGCmust be run immediately after theS6BBRPTR which created the ERRORLOGand before any activity on the segment.

S6BBC105ETABLE ENTRY CANNOT BE LOCATED ONCONTROL PAGE


Explanation: There are certain page types in thedatabase which are critical. If these pagetypes are freed it could affect the segment tothe extent that it becomes unusable or that

the path to tables is lost. These page typesinclude: "0" data set control page; "1" RTIXIndex; "R" RTIX; as well as reserved systempages.

Action: If the request in the ERRLOG wasgenerated by S6BBRPTR, contact TIBCOSupport for assistance. This problem shouldNOT occur; the segment from which thearchive was taken could be seriouslydamaged. If the request was built manually,the reason for attempting this activity shouldbe discussed with TIBCO Support before anyfurther action is taken.

S6BBC106EPAGE TYPE CANNOT BE MODIFIED


Explanation: There are certain page types in thedatabase which are critical. If these pagetypes are modified it could affect thesegment to the extent that it becomesunusable or that the path to tables is lost.These page types include: "0" data set controlpage; "1" RTIX Index; "R" RTIX; as well asreserved system pages.

Action: If the request in the ERRLOG wasgenerated by S6BBRPTR, contact TIBCOSupport for assistance. This problem shouldNOT occur; the segment from which thearchive was taken could be seriouslydamaged. If the request was built manually,the reason for attempting this activity shouldbe discussed with TIBCO Support before anyfurther action is taken.


26 |

S6BBC107IERRLOG WAS CREATED


Explanation: This line indicates when thehrnbrptr that created this ERRLOG file wasrun

Action: No action required

S6BBC108ENO SEGMENT-TIMESTAMP FOUND


Explanation: hrnbrptr which creates theERRLOG used as input for this requestselects a timestamp from one of the pages inthe segment processed. hrnbrpgc then checksthe timestamp against that in the same pageon the target segment, if there is notimestamp in the ERRLOG then this erroroccurs and the request is aborted. Thisprobably means that the ERRLOG wascreated by a previous (old) version ofhrnbrptr, it could also mean that this orphanrecovery is being run against the wrongversion of the target segment.

Action: If this version of the segment is in doubtthen rerun hrnbrptr to create a new ERRLOGand try again. If after an investigation youwish to force hrnbrpgc to use the invalidERRLOG then follow the instructionsoutlined in the product documentation.NOTE: This is a high-risk decision andshould not be made lightly, the audit reportwill indicate that you made this choice

S6BBC109ETIMESTAMP MISMATCH


Explanation: The hrnbrptr that created theERRLOG used as input for this requestselects a timestamp from one of the pages inthe segment processed. hrnbrpgc then checksthe timestamp against that in the same pageon the target segment. If the timestamps donot match, this error occurs and the request isaborted. The failure to match could meanthat this orphan recovery is being run againstthe wrong version of the target segment.

Action: If this version of the segment is in doubt,rerun hrnbrptr to create a new ERRLOG andtry again or run orphan recovery against thecorrect segment version.

If after an investigation you want to forcehrnbrpgc to use the invalid ERRLOG, followthe instructions outlined in the productdocumentation.

NOTE: This is a high-risk decision andshould not be made lightly, the audit reportwill indicate that you made this choice.

S6BBC201EUnsupported Data Type on Control File


Explanation: Control File Record I/R column 48must be either blank or H.

Action: Correct the Control File and try again.


| 27

S6BBC202ETranslation cannot be done


Explanation: The utility is unable to gain accessto the translation objects required to dotranslation.

Action: The translation objects must be availableto the utility at run time. Ensure that thetranslation objects are available by includingthem in:

• z/OS - Load library search path

• Windows - PATH

• Solaris - Shared Library path

Refer to the Utilities manual for youroperating system for more information.

S6BBC203EInsufficient Memory available


Explanation: Insufficient memory available to dothe necessary processing.

Action: Increase the amount of memoryavailable.

S6BBC204INo translation requested


Explanation: Input code page equals output codepage, so no translation is required.


S6BBC205ITranslation requested


Explanation: Indicates that the utility hasdetermined that translation is required.Translation is required if both of thefollowing conditions are true:

• Input code page and output code page aredifferent

• At least one character-file-field tocharacter-table-field is specified in theControl File

Action: No action is required.

S6BBC206IInput Code Page will still be tested for validity


Explanation: No translation is required but thecode page(s) specified are still checked toensure they are supported.


S6BBC207ETotal Records Processed


Explanation: Displays the number of recordsread from the Input file.



28 |

S6BBC208INo data requiring translation in file definition


Explanation: Indicates that the utility hasdetermined that translation is not required.No character-file-field to character-table-field is specified in the Control File.


S6BBC209EReserved Table Name, cannot be translated


Explanation: The table name specified in theControl File is an Object Service Brokersystem table; these tables should not betranslated.

Action: The utility will not translate this table.Refer to the Utilities documentation for youroperating system for more information.

S6BBC216ERecord shorter than minimum length


Explanation: The input record read is shorterthan the minimum size according to the filedefinition in the Control File.

Action: Make sure your input file is completelydefined in the Control File and try again.Also check that the Control File specified isthe correct one for the file being processed.

S6BBC217WInput record length exceeds hrnbrtbl capability


Explanation: The record size of the input file islarger than is acceptable to hrnbrtbl (offlinebatch load); therefore, neither the input filenor the output file will be accepted as inputto hrnbrtbl.

Action: Warning only. The input file record sizeindicates it is probably not an unloadedObject Service Broker table. If it is, redo theunload and specify a record size closer to themaximum size of an Object Service Brokerrow. Refer to the Utilities documentation foryour operating system for more information.

S6BBC219WInvalid Data - No Sequence Check on ThisRecord


Explanation: Invalid data has been encounteredon the input file; the format does not matchthe file-definition on the Control File. Thedata in error is ignored and no sequencechecking is performed on the error record.

Action: Check that the Control File specified isfor the file being translated. If it is, then thereis invalid data on the file. If the file is loadedusing hrnbrtbl this record will be ignored.


| 29

S6BBC220W***** File is not in correct sequence for hrnbrtbl*****


Explanation: The file is not in the correctsequence for hrnbrtbl. If you attempt to loadthis file using hrnbrtbl, the load may abortdue to bad sequence.

Action: Before attempting to load using hrnbrtbl,sort the file into the correct sequence:PARM1...PARMn, PRIMARYKEY1...PRIMARY KEYn.

S6BBC221WStatic values will not be translated


Explanation: The Control File shows that StaticValues exist for this file/table. These areconstant values which are inserted into everyinstance of the specified table field.

Action: You must ensure that Static Values on theControl File are correctly encoded to matchthe code page of the table data once loaded.Make sure when modifying the Control Filemanually that you do not inadvertentlychange the encoding of other Control Fileinformation. Any changes to Static Valuesmust be done prior to attempting the load(hrnbrtbl).

S6BBC222ITable field has no source file field


Explanation: The utility has detected that a tablefield has no source file field defined. This isnot an error; the table field will be set toNULL for each instance by the load(hrnbrtbl).


S6BBC223WFile is not in correct sequence


Explanation: After translation the utility hasdetected that the file is no longer in thesequence required by the load (hrnbrtbl).

Action: The file must be sorted prior toattempting a load (hrnbrtbl). Refer to theUtilities documentation for your operatingsystem for more information.

S6BBC224IRecords Translated


Explanation: Shows the total number of recordswhich were checked to see whethertranslation was necessary.


S6BBC225IRecords Copied


Explanation: Shows the total number of recordscopied.



30 |

S6BBC226IValues Changed


Explanation: Shows the number of field valueschanged.


S6BBC227IRecords Changed


Explanation: Shows the number of recordschanged by translation.


S6BBC228WOut of Sequence Records


Explanation: Shows the total number of recordswhich are not in the correct sequence.

Action: Refer to message S6BBC220W.

S6BBC229EToo Many Invalid Data Errors - process aborted


Explanation: The utility has a limit on thenumber of invalid data error records it willignore.

Action: This error normally indicates that theControl File does not correctly describe thefile. You must correct this situation before thefile can be processed by this utility.

S6BBC230EINFILE and OUTFILE or INPLACE required


Explanation: z/OS only: You must specify aninput and an output DD statement or aninput/output DD statement.

Action: Correct your request and try again.

S6BBC231ERECFM not compatible/invalid


Explanation: z/OS only: Either the RECFMspecified for OUTFILE is not compatiblewith INFILE (they must both be fixed or bothbe variable); or the RECFM specified forINPLACE is neither fixed nor variable.


S6BBC232ELRECL not compatible


Explanation: z/OS only: The LRECL of theOUTFILE is smaller than that of the INFILE.


S6BBC233IIN-PLACE translation not required


Explanation: z/OS only: The request does notrequire any translation and INPLACEprocessing is requested (copy file to itself).Request is denied.

Action: Check your request.


| 31

S6BBC234W** PLEASE CHECK INPUT FILE FORMATSPECIFICATIONS **


Explanation: Refer to the explanation forS6BSV954W.

Action: Ensure that the input file is describedcorrectly both in the Control File (-C) and onthe command line (-m). If the requestedprocess completed successfully, check thatthe format is specified correctly before usingthe translated file.

S6BBC255EAUDIT TRAIL FILE (PRINTER) FAILED TOOPEN


Explanation: The audit trail file would not openfor output.


S6BBC801EARCHIVE PARM REQUIRED (SEG)


Explanation: The SEG parameter is required forARCHIVE requests.

Action: Include the SEG parameter in yourrequest and try again.

S6BBC802EUNKNOWN PARM


Explanation: An unrecognized parameter is usedin your request.

Action: Check and correct your parameters andtry again.

S6BBC803ESEG PARM INVALID


Explanation: The SEG parameter value providedis invalid; it must be the segment number.

Action: Check and correct the SEG parameterand try again.

S6BBC804EARCHIVE SIZE PARM INVALID


Explanation: The BYTES parameter supplied hasan invalid value.

Action: This parameter is optional but if suppliedit must be a valid number. Remove or correctand try again.

S6BBC806EINPUT FILE OPEN ERROR


Explanation: The utility could not open thespecified input data set.

Action: Correct and try again.


32 |

S6BBC807EINPUT RECFM UNACCEPTABLE


Explanation: The input data set RECFM is notacceptable for the TYPE of reformatrequested.

Action: Check the documentation.

S6BBC808WINPUT FILE EMPTY


Explanation: The input data set contains no data.

Action: Check that you have specified the correctDSN.

S6BBC809EOUTPUT RECFM INVALID


Explanation: The RECFM specified is notacceptable to the reformat TYPE requested.


S6BBC810EOUTPUT ARCHIVE LRECL INVALID


Explanation: The LRECL specified is invalid.


S6BBC811EMEMORY NOT AVAILABLE


Explanation: The utility needs to acquireapproximately 100 KB of memory storage forbuffers to do the requested reformat. Thememory is not available.

Action: Increase REGION size and try again.

S6BBC812EINVALID SEGMENT NUMBER


Explanation: The segment number in the inputdata set data does not match that specified inthe SEG parameter.

Action: The utility attempts to continueprocessing using the segment number foundin the data as the actual SEG. If the jobfinishes successfully, no action is required;however, if other errors occur, refer to theactions for those error(s).

S6BBC814EOUTPUT FILE OPEN ERROR


Explanation: The Output data set could not beopened.



| 33

S6BBC815IINVALID PAGE TYPE


Explanation: In the field position that shouldcontain the page type, the utility discoveredan illegal value.

Action: This message is provided for informationonly. It is possible that an archive couldcontain corrupted data, and if hrnbrptr wasnot run against the archive prior to porting,this corruption could go undetected. If thisjob finishes successfully, run S6BBRPTR priorto using the output data set as a z/OSArchive.

S6BBC816WFILE SIZE PROVIDED DIFFERS FROM SIZEREFORMATTED


Explanation: The file size specified in theoptional parameter BYTES does not matchthe actual size of the input data read. This canbe because the BYTES value was incorrect oryou ported the archive from Windows orSolaris into an FB rather than a VB data set.An FB LRECL could result in padding of thelast record.


S6BBC817W# PAGES PROVIDED DIFFERS FROM #PAGES REFORMATTED


Explanation: The number of pages countedduring reformatting differs from the numberprovided in the PAGES parameter; thenumber provided is wrong.

Action: Check back to the original archive onWindows or Solaris; if the discrepancycannot be explained, contact TIBCO Support.

S6BBC818EBAD PAGE # SEQUENCE


Explanation: The input data set does not containa single segment archive.

Action: Do the following:

• Make sure hrnbrptr is run on the archiveprior to porting to z/OS.

• Make sure the archive contains only onesegment and try again.

S6BBC819WARCHIVE CONTAINS TAGGED PAGETYPES


Explanation: Data Object Broker failures canleave pages in an indeterminate state; theutility has found such pages. Databasecorruption should be fixed prior to porting,but may be done on z/OS after reformatting.

Action: If the request finishes successfully, makesure you run S6BBRPTR against the outputfile before using it as an archive.


34 |

S6BBC820ECONFLICTING PARMS


Explanation: The parameter(s) entered do notmatch the REFORMAT type.

Action: Check the documentation and try again.

S6BBC822ENO PARMS PROVIDED


Explanation: Each request requires at least 1parameter.

Action: Refer to the documentation and tryagain.

S6BBC823EUNKNOWN REQUEST


Explanation: The reformat type requested isunknown.


S6BBC826EFORMAT ERROR - INPUT


Explanation: The input data set format is invalid.

Action: For PARM='REFORMAT=MVSLOAD'requests, the data set must be in ObjectService Broker data format (DSBIFTYPE) andmust have been FTPed in binary mode fromWindows or Solaris.

For PARM='REFORMAT=OFFLINE'requests, the data set must have been createdon Windows or Solaris using one of theoffline unload utilities (hrnbrulb, hrnbrulh,

or hrnbrula). It must also have been FTPedto z/OS in binary mode.

For PARM='REFORMAT=NOBDW'requests, the data set must have beenoriginally created (on z/OS) as VB. Whenthe data set was FTPed to Windows orSolaris, it must have been in binary modewith RDW enabled. When FTPed fromWindows or Solaris to z/OS, it must havebeen in binary mode.

S6BBC827EOUTPUT RECORD LRECL BIGGER THANFILE LRECL


Explanation: The output record created is toolarge for the maximum LRECL you specifiedfor the output data set.

Action: Check the documentation, correct, andtry again.

S6BBC832WEND OF LAST RECORD IGNORED, PLEASECHECK


Explanation: This indicates that there was dataleft after end of file and after building the lastreformatted record. This could happen if theinput (ported) data set is RECFM=FB (ratherthan VB) and the last record is padded to itsfull LRECL.

Action: The data does not appear to be paddingso check the output carefully forcompleteness before using.


| 35

S6BBC833WEND OF LAST RECORD IGNORED,PADDING ASSUMED


Explanation: This indicates that there was dataleft after end of file and after building the lastreformatted record. This could happen if theinput (ported) data set is RECFM=FB (ratherthan VB) and the last record is padded to itsfull LRECL.

Action: The data appears to be padding, butcheck the output data set for completenessbefore using it.

S6BBC834IIGNORED BYTES


Explanation: This information accompaniesmessages S6BBC832W and S6BBC833W andshows the number of bytes ignored at theend of the input data set.


S6BBC904ENO TABLE OF TABLES ENTRY ONMETASTOR


Explanation: There is no ACCESSLOG entry inthe list of existing tables.

Action: The MetaStor must be installed prior torunning this utility. If this has been done,contact TIBCO Support.

S6BBC905ETABLE OF TABLES ENTRY SEGMENT #ERROR


Explanation: The TABLES table has a field,SEGMENT#, that should contain thesegment number of the segment thatcontains ACCESSLOG's data. This utilitydoes not accept a NULL value in this field.

Action: Correct the SEGMENT# field inACCESSLOG's TABLES entry.

S6BBC906EACCESSLOG ALREADY ON TARGETSEGMENT


Explanation: ACCESSLOG is already located onthe segment you indicated as the target.


S6BBC907EACCESSLOG NOT ON METASTOR


Explanation: The ACCESSLOG data segmentmust be the MetaStor. This utility does notinstall ACCESSLOG from segments otherthan the MetaStor.

Action: You cannot use this utility to move theACCESSLOG from any segment other thanthe MetaStor.


36 |

S6BBC908ELOG MUST BE PURGED FIRST


Explanation: This utility will not install theACCESSLOG until all data has been purgedand archived.

Action: Purge/Archive the ACCESSLOG as perthe documentation and run this utilityimmediately following.

S6BBC910ISEARCH METASTOR FOR ACCESSLOG


Explanation: Informational message only: theutility has started its search of the MetaStortable index for the ACCESSLOG entry.


S6BBC911ICHECKING METASTOR POINTERS


Explanation: Informational message only: theACCESSLOG entry has been found in theMetaStor table index and its pointers areabout to be checked to ensure that the dataportion of the table is located on theMetaStor.

Action: No action is necessary.

S6BBC912IINSTALLATION COMMENCED - TARGETSEGMENT


Explanation: Informational message only:indicates that the target segment is about tobe modified. If a failure occurs at this timeyou must assume that the target segment isunusable until restored from an archive.


S6BBC913IINSTALLATION COMPLETED - TARGETSEGMENT


Explanation: Informational message only:indicates that the necessary changes havebeen made to the target segment to create anACCESSLOG data allocation. If a failureoccurs at this stage the target segment mustbe restored from archive before attempting arerun of this utility.


S6BBC914IMODIFYING METASTOR POINTERS


Explanation: Informational message only: Thedata allocation for ACCESSLOG on thetarget segment has been completed and theMetaStor pointers are about to be changed. Afailure at this time requires that both theMetaStor and target segments be restoredbefore attempting any further Pagestoreprocessing.



| 37

S6BBC915IACCESSLOG INSTALLATION COMPLETE


Explanation: Informational message only:request successfully completed.

Action: Take a backup of both the MetaStor andtarget segments.

S6BBC916ECOULD NOT OPEN SEGMENT


Explanation: The segment indicated could not beopened.

Action: The Data Object Broker must be shutdown before running this utility and thetarget segment must exist. Check that youhave allowed for the requirements of thisutility and that the segment indicated in thePARM/OPTION is correct.

S6BBC917EDATA LOCATION DIFFERS TABLES v RTIX


Explanation: The table of TABLES contains adifferent target segment than the oneindicated in the MetaStor RTIX entry.

Action: Correct the table of TABLES.SEGMENT#field so that it agrees with the MetaStor RTIXtarget segment number and try the utilityagain.

S6BBC918ESEGMENT COULD NOT BE CLOSED


Explanation: Either the MetaStor or the targetsegment could not be closed after processingwas completed; neither segment is usable.

Action: Attempt to discover how this situationoccurred, bearing in mind that both thesesegments were in the process of beingchanged and must be considered unusable.Restore the backups taken prior to runningthis utility and try again.


38 |

BL: Batch Load

S6BBL001IPOST INPUT RECORD READ EXIT ACTIVE

Source: Batch Load

Explanation: This message notifies you that theS6BBRTL1 exit is active.


S6BBL002IPOST FIXED FORMAT CONVERSION EXITACTIVE

Source: Batch Load



S6BBL003IFORMAT COMPRESSION EXIT ACTIVE

Source: Batch Load



S6BBL004IPRIMARY KEY VALUE WILL BEGENERATED (IDGEN)

Source: Batch Load

Explanation: This message notifies you that theprimary key will be generated (IDgen).


S6BBL005IERROR ATTEMPTING INPUT FIELDFORMAT CONVERSION

Source: Batch Load

Explanation: The conversion routine detected anerror during the conversion of the inputrecord to fixed length format. The actualconversion error message will immediatelyprecede this message. The processingcontinues with the next record.


S6BBL006IPARAMETER(S) INSTANCE SEQUENCEERROR

Source: Batch Load

Explanation: A table instance was rejected. Therejected table instance contained count1records starting at input record count2.

Action: See the previous audit message andcorrect the previous error condition.

S6BBL007IDUPLICATE TABLE INSTANCE, # REJECTSSEE BELOW

Source: Batch Load

Explanation: Records have been rejected as theybelong to a previously complete instance.

Action: The number of records rejected areshown below this message.


| 39

S6BBL008ITABLE NOT UPDATED; NO INPUTRECORDS ACCEPTABLE

Source: Batch Load

Explanation: Notification that the Object ServiceBroker Pagestore was not updated becausenone of the input records were accepted.

Action: See the messages in the audit trail todetermine why all the records were rejected.

S6BBL009ENO INPUT FIELD OR VALUE DEFINED FORPARM

Source: Batch Load

Explanation: When loading a parameterizedtable there must always be a value associatedwith each parameter, either from an input filefield or from static values.

Action: Correct your data and retry loading thetable.

S6BBL011IDUPLICATE PRIMARY KEY

Source: Batch Load

Explanation: The primary key of an input recordis a duplicate.

Action: No action possible; the record is ignored.

S6BBL012IPRIMARY KEY(S) SEQUENCE ERROR

Source: Batch Load

Explanation: The primary keys must be sortedproperly within the table instances (ifapplicable).

Action: Either manually add the entries that areout of sequence, or delete the tree, sort again,and run again.

S6BBL013IRECORD SHORTER THAN MINIMUMLENGTH

Source: Batch Load

Explanation: A zero data length recordencountered.

Action: Record is ignored.

S6BBL014ICONVERSION - INPUT FIELD CONTAINSBAD DATA

Source: Batch Load

Explanation: The field indicated contains datawhich does not conform to the specifiedformat.


S6BBL015ICONVERSION - OUTPUT FIELD TOOSMALL

Source: Batch Load

Explanation: The field indicated cannot beconverted without possible data-integrityloss.



40 |

S6BBL016ICONVERSION - CONVERSION NOTPOSSIBLE

Source: Batch Load

Explanation: The field indicated cannot beconverted due to incompatible source/targetsyntax.


S6BBL017ICONVERSION - PARAMETER(S) INVALID

Source: Batch Load

Explanation: Conversion routine internal error.


S6BBL018IPARAMETER OR PRIMARY KEY NULL

Source: Batch Load

Explanation: Null primary key/parametervalues are not permitted.


S6BBL019ISECONDARY KEY NUMERIC VALUE NULL

Source: Batch Load

Explanation: Null numeric-syntax secondarykeys are not permitted.


S6BBL020ECONTROL CARD INPUT FILE FAILED TOOPEN

Source: Batch Load

Explanation: Problem experienced opening theControl File.

Action: Processing terminated; check run JCL.

S6BBL021ESPACE FOR DEFINITION TABLE IS NOTAVAILABLE

Source: Batch Load

Explanation: GETMAIN for the internal table tohold input and output definitions failed.

Action: The required space is 88 multiplied bythe maximum number of fields (50 is thedefault). Check with your data centermanager for private extended storage limits(above the line storage).

S6BBL022EPRIMARY KEY MUST COME FROM INPUTOR BINARY 4 FOR IDGEN

Source: Batch Load

Explanation: The primary key in Object ServiceBroker is not derived from an input field. Tobe considered for IDgen, it must be binarylength 4.

Action: Do one of the following:

• If you want an IDgen key, make theprimary key binary length 4.

• If the field is from input, correct the controlcards.

• If you want to generate a key yourself,define a dummy input field and use exitpoint 1 (S6BBRTL1). Refer to the Utilitiesmanual for details on exits.


| 41

S6BBL023ESPECIFIED INPUT/OUTPUT SYNTAXCONVERSION TEST FAILED

Source: Batch Load

Explanation: When testing the conversion of thedata field syntaxes, an error was detected.

Action: See accompanying message. ContactTIBCO Support if a syntax combination isrequired.

S6BBL024ESPACE NOT AVAILABLE IN WHICH TOBUILD THE ENTRY

Source: Batch Load

Explanation: GETMAIN for internal work spacefor the compressed Object Service Brokerentry failed.

Action: The requested memory was 2025 bytes.Contact your data center manager for privateextended storage limits (above the linestorage).

S6BBL025ESPACE NOT AVAILABLE TO RETAINREQUIRED INDEXING DATA

Source: Batch Load

Explanation: GETMAIN for internal indexcapture record work area failed. Requestedspace is the following added together:

• The primary key length

• The length of the largest secondary indexkey

• The length of all the parameters

• 9.

The space is to be below the line.

Action: Increase the region size in the JCL.

S6BBL026ELOAD TABLE COULD NOT BE LOCATEDON CONTROL PAGE

Source: Batch Load

Explanation: The table to be loaded could not belocated in the index of the Resident TableIndex.


• Check the spelling of the table name on theObject Service Broker output definitioncard and ensure that the table type is TDS.

• Ensure that the table you are attempting toload is on the segment specified in the runtime parameter.

S6BBL027ELOAD TABLE COULD NOT BE LOCATEDON TABLE INDEX

Source: Batch Load

Explanation: The Resident Table Index entrycould not be found for the requested table.


• Check spelling on the output definitioncard and ensure the table type is TDS.

• Ensure that the table you are attempting toload is on the segment specified in the runtime parameter.


42 |

S6BBL028ESPACE NOT AVAILABLE FOR INTERNALINDEX CONTROL TABLES

Source: Batch Load

Explanation: GETMAIN for internal indexcontrol stack failed. The requested space is 16multiplied by 6 from the storage.

Action: Check with your data center manager forprivate extended storage limits (above theline storage).

S6BBL029ESPACE NOT AVAILABLE FOR REQUIREDPAGE BUFFERS

Source: Batch Load

Explanation: GETMAIN for Object ServiceBroker page buffer space failed. Therequested space is 4 KG multiplied by 6. Add4 KB if there are parameters, and add 4 KB ifthere are secondary indexes.


S6BBL030EEXPECTED SECONDARY INDEX ENTRYNOT FOUND ON SIT PAGE

Source: Batch Load

Explanation: The output definition cardsspecified a secondary index which was notdefined within the Object Service BrokerPagestore.

Action: Either build the secondary index byusing SIXBUILD processing online, orremove the S for the field in the ObjectService Broker output definition card.

S6BBL031EINCORRECT SEGMENT ACTIVE FOR TABLELOAD PROCESSING

Source: Batch Load

Explanation: The table to be loaded is not on thebase store with which the batch utility wasstarted.

Action: Specify a run time parameter of"SEGMENT=nnnn", where nnnn is thesegment number that contains the table to beloaded.

S6BBL032ETABLE TO BE LOADED IS NOT EMPTY

Source: Batch Load

Explanation: The table to be loaded contains dataand no parameters are associated with it.Only table instances can be added to anexisting table. Data within a table instancecannot be added.

Action: Either remove the data from the table oruse an Object Service Broker rule to load thenew data.

S6BBL033EEXPECTED SECONDARY INDEXES NOTFOUND

Source: Batch Load

Explanation: When a secondary index is built byusing S6BBRSIX, the table definition ischanged (online) to reflect the newly builtsecondary index. This message was issued


| 43

because you tried to load the table again (byusing S6BBRTBL) but did not change thedefinition control records to reflect the newsecondary index.

Action: Recreate the load control records byusing BATCHLOAD_CARDS or delete thesecondary indexes by using SIXDELETE.

S6BBL034IUSER-EXIT REQUESTED REJECT

Source: Batch Load

Explanation: Your user exit requested that thisrecord be ignored.

Action: Record is ignored. Recreate the loadcontrol records by usingBATCHLOAD_CARDS or delete thesecondary indexes by using SIXDELETE.

S6BBL035EINVALID UNIT COUNT SPECIFIED

Source: Batch Load

Explanation: The UNIT COUNT specified on thecontrol data set for multivolume work filesupport must be less than or equal to theactual number of units available for the unitgroup name specified.

Action: Enter an acceptable number and retry.

S6BBL036EREQUESTED SECONDARIES DO NOTMATCH THOSE ALLOCATED

Source: Batch Load

Explanation: The Secondary key field namesidentified on the Definition Control File donot match the field names of the allocatedsecondaries on the Pagestore.

Action: The report indicates the discrepancies;use the online tool BATCHLOAD_CARDS togenerate an accurate Definition Control File.

S6BBL037ESECONDARIES ARE ALLOCATED BUTNONE REQUESTED

Source: Batch Load

Explanation: There are secondary index fieldsdefined for the table being loaded but nosecondaries are defined in the definitioncontrol file.

Action: Use the online toolBATCHLOAD_CARDS to generate an up-to-date/ accurate Definition Control File for thistable.

S6BBL040ECONTROL CARD TYPE CODE ISINVALID,(EXPECTED I,H,S OR V)

Source: Batch Load

Explanation: The control card type (column 1)has an invalid code. Only I, H, S, or V areacceptable.

Action: Enter I, H, S, or V for the control cardtype.


44 |

S6BBL041EDEFINITION: SEQUENCE FIELD ERROR

Source: Batch Load

Explanation: The sequence numbers (column 3-5) for the input definition cards are notproperly sorted.

Action: Reorganize the cards or correct thesequence numbers.

S6BBL042EINPUT DEFINITION CARD ENTRY TYPECODE INVALID; R OR F

Source: Batch Load

Explanation: The entry type code (column 7) isinvalid for an input definition. Only R(records) and F (field) are acceptable.

Action: Enter R or F for the entry type code.

S6BBL043EINPUT DEFINITION CARD SYNTAX CODEIS NOT SUPPORTED

Source: Batch Load

Explanation: The syntax code (column 48)defined for the input field is not supported.

Action: See the documentation on inputdefinition cards for valid codes.

S6BBL044EINPUT DEFINITION CARD FIELD LENGTHBLANK/OUT OF RANGE

Source: Batch Load

Explanation: The field length (column 50-52) onthe input definition card is either blank or thevalue is outside the range for the givensyntax.

Action: Fill in a field length that is within therange for the syntax. See the documentationon input definitions for valid length ranges.

S6BBL045EINPUT DEFINITION CARD DECIMALPOSITION IS OUT OF RANGE

Source: Batch Load

Explanation: The decimal position (column 54-55) specified for the input field is outside therange of the field length.

Action: Change the decimal position to fallwithin the range of the field length.

S6BBL046EINPUT DEFINITION RECORD CARD HASINVALID FILE TYPE (F-V)

Source: Batch Load

Explanation: File type is either F (Fixed) or V(Variable). Default is F; no other value isacceptable.

Action: Correct the file type and retry.


| 45

S6BBL047EDEFINITION TABLE OVERFLOW;INCREASE MAX FIELDS ON SPEC

Source: Batch Load

Explanation: The internal table that retains theinput/output definition information hasoverflowed.

Action: Increase the maximum number of fieldson the specification card. Refer to the onlineUtilities documentation for details.

S6BBL048ESPECIFICATION CARD MUST BE FIRST INCONTROL CARD FILE

Source: Batch Load

Explanation: If included, the specification cardmust be the first card in the control card file.

Action: Put the specification card at the front ofthe control card file.

S6BBL049EMISSING INPUT DEFINITION - NUMERICSECONDARY

Source: Batch Load

Explanation: Numeric Secondary index fieldvalues cannot be null. No input field isdefined cross-referencing to a table fielddefined as a secondary index, which meansthe table field value will be loaded as NULL.

Action: Remove the secondary index indicator orprovide an input field which has significantdata in every record or change the syntax ofthe target (table) field to a character syntax (Cor V).

S6BBL051WNULL-EQUIVALENT VALUE SPECIFIED ISIGNORED

Source: Batch Load

Explanation: A null-equivalent value is validonly when the input file field from which thedata is being loaded to this output (table)field is either binary or packed decimalsyntax. Columns 64-79 are ignored.

Action: None.

S6BBL060EOUTPUT DEFINITION CARDS ARE OUT OFSEQUENCE

Source: Batch Load

Explanation: The sequence numbers (column 3-5) for the output definition cards are notproperly sorted.

Action: Reorganize Object Service Broker outputdefinition cards or correct the sequencenumbers.

S6BBL061EOUTPUT DEFINITION CARD HAS INVALIDENTRY TYPE (R,P/F)

Source: Batch Load

Explanation: The entry type code (column 7) isinvalid for an Object Service Broker outputdefinition. Only R (record), P (parameter),and F (field) are acceptable.

Action: Change the entry type code to R, P, or F.


46 |

S6BBL062EDEFINITION TABLE OVERFLOW;INCREASE MAX FIELDS ON SPEC

Source: Batch Load

Explanation: The internal table that retains theinput/output definition information hasoverflowed.


S6BBL063EOUTPUT DEFINITION SEMANTICTYPE/SYNTAX NOT SUPPORTED

Source: Batch Load

Explanation: The semantic type (column 46) andsyntax code (column 48) do not form a validcombination.

Action: Change either the semantic type or thesyntax to form a valid combination. See theProcessing manual for a list of validcombinations or check the online definition.

S6BBL064EOUTPUT DEFINITION CARD FIELDLENGTH BLANK/OUT OF RANGE

Source: Batch Load

Explanation: The field length (column 50-52) onthe output definition card is either blank orthe value is outside the range for the givensyntax.

Action: Enter a field length that is within therange for the syntax. Check the onlinedefinition.

S6BBL065EOUTPUT DEFINITION CARD DECIMALPOSITION IS OUT OF RANGE

Source: Batch Load

Explanation: The decimal position (column 54-55) specified for the Object Service Brokerparameter or field is outside the range of thefield length.

Action: Enter a decimal position that is withinthe range for the field length.

S6BBL066EOUTPUT DEFINITION CARD KEY TYPE NOTSUPPORTED (" ",P/S)

Source: Batch Load

Explanation: The output Object Service Brokerkey type (column 57) is invalid. Only blank,P (primary key), and S (secondary key) aresupported.

Action: Enter a P, an S, or a blank for the outputObject Service Broker key type.

S6BBL067EINVALID SYNTAX FOR KEY/PARM FIELD

Source: Batch Load

Explanation: The syntax specified is not valid asused.

Action: Check documentation and correct thespecification.

S6BBL069EINVALID NUMERIC DEFINITION VALUE

Source: Batch Load

Explanation: A numeric value is required.



| 47

S6BBL070EPRIMARY OR SECONDARY KEY LENGTHERROR

Source: Batch Load

Explanation: The primary or secondary keylength specified exceeds the maximum.


S6BBL071ETOO MANY PARAMETERS

Source: Batch Load

Explanation: The number of parameters definedexceeds the limit.


S6BBL072EPARAMETER(S) LENGTH ERROR

Source: Batch Load

Explanation: The total parameter(s) lengthexceeds the limit.


S6BBL080ESPECIFICATION CARD MAXIMUMPROCESS RECORDS NOT NUMERIC

Source: Batch Load

Explanation: The maximum records field(column 15-29) contains an invalid numericalvalue.

Action: Correct the value and ensure that it isright aligned.

S6BBL081ESPECIFICATION CARD MAXIMUMNUMBER OF FIELD NOT NUMERIC

Source: Batch Load

Explanation: The maximum number of fieldsvalue in column 31-33 contains invalidnumeric data.


S6BBL082ESPECIFICATION CARD MAXIMUM BLOCKSIZE IS NOT NUMERIC

Source: Batch Load

Explanation: The maximum block size field (incolumn 44-48) contains an invalid numericvalue.


S6BBL083ESPECIFICATION CARD SPACE USAGEVALUE IS NOT NUMERIC

Source: Batch Load

Explanation: The percentage specified for one ofthe following is not numeric:

• Data

• Index

• Secondary index

• Group index.



48 |

S6BBL084ENULL-EQUIVALENT VALUE SPECIFIED ISINVALID

Source: Batch Load

Explanation: The null-equivalent value (incolumns 64-79) is invalid; either the code ismisspelled or the value is not numeric.


S6BBL100EVALUE CARD FIELD/PARAMETER NAMENOT FOUND

Source: Batch Load

Explanation: The name specified (in column 3-18) cannot be matched with the outputdefinition table.

Action: Check the spelling of the field name.Correct the Object Service Broker outputdefinition name or the static value name.

S6BBL101EVALUE CARD FOR FIELD/PARAMETERDEFINITION AS INPUT

Source: Batch Load

Explanation: A value card cannot be enteredagainst a field or parameter which isreferenced in the input file.


• Remove the static value card or cards forthe given field or parameter.

• Remove the reference to the field in theinput specification card.

S6BBL102EVALUE CARD FOR FIELD/PARAMETERALREADY PROCESSED

Source: Batch Load

Explanation: A value card was entered for a fieldor parameter which has already been set.

Action: Check to ensure a continue indicator(column 20) is set, if a continuation is beingattempted.

S6BBL103EVALUE CARD FOR NUMERICFIELD/PARAMETER NOT NUMERIC

Source: Batch Load

Explanation: The value card contains static text(column 22-71) for a numeric field orparameter (packed or binary), but the textcontains non-numeric characters.

Action: Correct the value and ensure that it is leftaligned.

S6BBL104EVALUE CARD TEXT LENGTH IS INVALIDFOR A NUMERIC ENTRY

Source: Batch Load

Explanation: The length of the numeric data inthe value card text area is not valid (out ofrange 1-15 digits).

Action: Make the numeric data 1 to 15 digits.


| 49

S6BBL105EVALUE CARD DECIMAL POSITIONCONFLICTS WITH DEFINED

Source: Batch Load

Explanation: The number of post decimal digitsmust match the definition of the field orparameter.

Action: Change the number of post decimaldigits to match the definition of the field orparameter.

S6BBL106EINVALID OR NO CHARACTER SET TYPESPECIFIED

Source: Batch Load

Explanation: The character set code was found tobe invalid.

Action: Specify a proper character set. Blankdefaults to ENGL.

S6BBL107EVALUE EXCEEDS LENGTH OF FIELD

Source: Batch Load

Explanation: There are too many ValueContinuations for the field as defined.Remember that each Value Record holds 50characters.

Action: Shorten the value for the field to thedefined length of the field, and removeextraneous Value Records.

S6BBL108EVALUE CONTINUATION INVALID OR OUTOF SEQUENCE

Source: Batch Load

Explanation: Value Continuation ColumnEntries must be consecutive and in ascendingsequence if there are multiple records (morethan 50 characters).

Action: The first record of a single field's "ValueRecords" must have 0 in its ContinuationColumn. If the value continues beyond 50characters, the second "Value Record" (whichis the first actual continuation) must have 1in its Continuation Column; the third musthave 2, and so on.

S6BBL109EVALUE DATE INVALID

Source: Batch Load

Explanation: Static Value date is in the wrongform.

Action: Check documentation and yourinstallation's date format.

S6BBL110ESTATIC VALUE REJECTED DURINGCONVERSION

Source: Batch Load

Explanation: The static value associated with thefield identified could not be converted to thesemantic type/syntax of the target field.

Action: This error should have been trappedwhen the utility processed the DefinitionControl File - contact TIBCO Support andprovide all relevant information: the value ofthe static value and the target field definition.


50 |

S6BBL111EPAGESTORE WRITE FAILURE

Source: Batch Load

Explanation: When attempting to write a page tothe current segment a failure occurred.

Action: Inspect the audit report for othermessages which should indicate why thefailure occurred. The table being loaded mustbe considered incomplete and the segmentitself suspect. Contact TIBCO Support andsupply all relevant documentation: the auditreport, the core dump if produced.

S6BBL120EDYNAMIC ALLOCATION OF TEMPORARYFILE FAILED

Source: Batch Load

Explanation: A dynamic allocation requestfailed.

Action: Check the job log for an explanation andverify the dynamic symbolic unit name onthe specification card.

S6BBL121ESPACE NOT AVAILABLE FOR TEMPORARYFILE DCB DEFINITION

Source: Batch Load

Explanation: The GETMAIN to obtain storage(below the line) for the temporary file DCBfailed.

Action: Increase the size parameter in your JCL.

S6BBL122ESPACE FOR INTERNAL FIXED FORMATRECORD IS NOT AVAILABLE

Source: Batch Load

Explanation: GETMAIN for internal work spacefor fixed format work record failed.Requested space is 2028 bytes.


S6BBL140EERROR DETECTED WHEN EVALUATINGACCESS METHOD OF INPUT

Source: Batch Load

Explanation: The JFCB of the input file is used todetermine if the input file is sequential orVSAM access. The read JFCB failed.

Action: Check your JCL and the job log. If thisinformation does not provide a solution,contact TIBCO Support.

S6BBL141EINPUT FILE FAILED TO OPEN USINGSEQUENTIAL ACCESS

Source: Batch Load

Explanation: The input file was determined to besequential and the open for the file failed.

Action: Check your JCL and the job log.


| 51

S6BBL142EINPUT FILE FORMAT IS NOT SUPPORTED

Source: Batch Load

Explanation: The input file was determined tohave a format other than fixed or variable.The format is not supported.

Action: Ensure that the input file is either fixed orvariable.

S6BBL143EINPUT FILE FAILED TO OPEN USING VSAMACCESS METHOD

Source: Batch Load

Explanation: The input file was determined to bea VSAM data set. The open for the file failed.

Action: Check your JCL and the job log. A VSAMverify may be required.

S6BBL144EINDEX CAPTURE WORK FILE FAILED TOOPEN FOR OUTPUT

Source: Batch Load

Explanation: The work file used to captureindexing information failed to open foroutput.

Action: Check the dynamic symbolic unit andblocksize in the specification cards. Reviewthe job log for further information.

S6BBL145EINPUT RECORD CONVERSION ERRORTHRESHOLD EXCEEDED

Source: Batch Load

Explanation: The number of conversion errorsdetected by the conversion routine exceedsan allowable limit.

Action: Verify the input file layout and check forthe values rejected by the conversion routine.

S6BBL146EINVALID PAGE TYPE FOUND WHENSEARCHING GROUP INDEXTREE

Source: Batch Load

Explanation: A page type code detected whensearching for existing table instances was nota group index or group index page type.

Action: Verify the Pagestore by using theS6BBRPTR utility. Contact TIBCO Support.

S6BBL147E***** PROCESSING TERMINATED, ALLINPUT REJECT ******

Source: Batch Load

Explanation: None of the user input data wasaccepted. Processing ended.

Action: Correct the reported audit trailconditions that caused the input to berejected.


52 |

S6BBL148ENO INPUT RECORDS READ, PROCESSINGTERMINATED

Source: Batch Load

Explanation: No input records have been foundusable.

Action: No load is possible.

S6BBL149ENULL INPUT KEY VALUE ENCOUNTERED

Source: Batch Load

Explanation: During loading, a null value in theprimary key or a secondary index wasdetected.

Action: Record is rejected.

S6BBL150EREJECT LIMIT EXCEEDED

Source: Batch Load

Explanation: The reject count has exceeded thelimit.

Action: Job is terminated.

S6BBL151W** PLEASE CHECK INPUT FILE FORMATSPECIFICATIONS **

Source: Batch Load

Explanation: Refer to the explanation forS6BSV954W.

Action: Ensure that the input file is describedcorrectly both in the Control File (-C) and onthe command line (-m). If the requestedprocess completed successfully, check thatthe table data is correctly loaded.

S6BBL152ETOO MANY SECONDARIES

Source: Batch Load

Explanation: There is a limit to the number ofsecondary index fields permitted in a tabledefinition. This limit is used to determine thesize of certain tables within the utility. One ofthese tables has overflowed.


S6BBL153EPROGRAM ERROR

Source: Batch Load

Explanation: An internal program erroroccurred.


S6BBL154ISECONDARY INDEX COMPLETE

Source: Batch Load

Explanation: Indicates that the load hascompleted successfully; the secondary indexis complete and has been COMMITTED.

Action: No action necessary.

S6BBL155IPRIMARY DATA LOAD COMPLETE

Source: Batch Load

Explanation: The primary data has been loadedsuccessfully and COMMITTED.

Action: If no secondaries are being built then theload has completed building the target table.If a secondary index build follows theprimary build and it fails, the primary data is


| 53

complete. After determining why thesecondary build failed, use the SecondaryIndex Builder S6BBRSIX to build the missingsecondary indexes.

S6BBL157EFREE-PAGE REQUEST FAILURE

Source: Batch Load

Explanation: Usually indicates the segment isfull.

Action: Provide more segment space and retry.

S6BBL160ESORT SYNTAX CODE COULD NOT BELOCATED FOR SYNTAX

Source: Batch Load

Explanation: The syntax code of the field orparameter cannot be converted to a codeacceptable to the sort routine.


S6BBL161EGROUP INDEX CAPTURE FILE COULD NOTBE OPENED FOR OUTPUT

Source: Batch Load

Explanation: The work file used to retain tableinstance information cannot be opened foroutput.

Action: Check the dynamic symbolic unit andblocksize on the specification card. See thejob log for further details.

S6BBL162ESECONDARY INDEX ROOT PAGE NOTFOUND ON SIT PAGE

Source: Batch Load

Explanation: The secondary index entry cannotbe located on the Secondary Index Tablepage.

Action: Ensure that all fields with a key type of Sare defined as secondary indexes. If not,invoke online SIXBUILD processing.

S6BBL163EINVALID PAGE TYPE DETECTED WHENCAPTURING EXISTING GIX

Source: Batch Load

Explanation: Existing group index chain containsinvalid page type codes. (Table is possiblycorrupted.)

Action: Verify the Pagestore by using S6BBRPTR.Also, contact TIBCO Support.

S6BBL164ESORT FAILURE DETECTED DURINGSECONDARY INDEX PROCESSING

Source: Batch Load

Explanation: An error was detected by the sortprogram when reorganizing the indexcapture file for a secondary index load.

Action: Check the job log for messages fromSORT. Ensure that you have a SYSOUT DD inyour JCL.


54 |

S6BBL165ESORT FAILURE DETECTED DURINGGROUP INDEX PROCESSING

Source: Batch Load

Explanation: An error was detected by the sortprogram when reorganizing the group indexcapture file for a group index build.

Action: Check the job log for messages fromSORT. Ensure that you have a SYSOUT DD inyour JCL.

S6BBL168EINDEX CAPTURE FILE FAILED TO OPENFOR INPUT

Source: Batch Load

Explanation: The internal index file could not beopened after being built.


S6BBL169EINDEX CONTROL TABLE OVERFLOWED;TOO MANY INDEX LEVELS

Source: Batch Load

Explanation: The internal index table is too smallfor this run.


S6BBL170ERESIDENT TABLE INDEX UPDATEPREPARATION FAILED

Source: Batch Load

Explanation: Preparation for actual databaseupdate failed.


S6BBL171EINPUT RECORD LENGTH EXCEEDS LOADSCAPABILITY

Source: Batch Load

Explanation: The record size is too large.


S6BBL172ETABLE ROW SIZE ERROR

Source: Batch Load

Explanation: The total length of the row definedfor the target table is larger than themaximum permitted.

Action: Check and correct the definition on thecontrol data set; the table as specified wouldnot have been accepted by the Object ServiceBroker Table Definer.

S6BBL173IBROWSE MODE - REQUEST VALIDATIONCOMPLETE

Source: Batch Load

Explanation: The option BROWSE was specified,which results in termination after validationof the control file.

Action: No action necessary. Remember toremove the BROWSE option when (if) theload is actually submitted.

S6BBL174ERESERVED TABLE - OFFLINE LOAD NOTPERMITTED

Source: Batch Load

Explanation: The table name requested cannot beloaded using this utility.

Action: Contact TIBCO Support for assistance.


| 55

S6BBL175EOLD NULL OPTION NOT SUPPORTED

Source: Batch Load

Explanation: The OLD NULL option applies tothe unload utilities only.

Action: Remove the option and retry or contactTIBCO Support.

S6BBL176ESTATICS VALUES NOT SUPPORTED FORUNICODE FIELDS

Source: Batch Load

Explanation: When attempting to load data intoa table using the offline batch utilityS6BBRTBL, a default value was specified fora field that has a Unicode syntax. This is notsupported.

Action: Remove the default value card and rerunyour load process.

S6BBL177EUNICODE SYNTAX NOT SUPPORTED FORPARMS OR KEYS

Source: Batch Load

Explanation: A Unicode syntax was specified onthe definition cards for a field that either aparameter or key field.

Action: Correct the control cards and try theS6BBRTBL utility.

S6BBL255EAUDIT TRAIL FILE FAILED TO OPEN

Source: Batch Load

Explanation: The audit trail (printer) failed toopen. User abend code 932 is issued.

Action: Review job log for further details.


56 |

BP: Pagestore Validation

S6BBP001WCHILD % POINTER FOR PAGE % ISINVALID; BRANCH IGNORED

Source: Pagestore Validation

Explanation: The specified entry number on theindicated group or primary index page is -1,which is invalid. A completion code of 8 isgenerated.


S6BBP002WPAGE % IS GREATER THAN HIGHEST PAGEBACKED UP


Explanation: The specified page was referencedbut it cannot be located in the page headertable. This indicates an incomplete backup orarchive, or an internal error. A completioncode of 8 is generated.


S6BBP003WDUPLICATE REFERENCE TO PAGE %DETECTED


Explanation: The specified page is referenced inmore than one place. A completion code of 12(X'0C') is generated.

Action: Stop processing the segment and contactTIBCO Support immediately. Do notcontinue processing on the tables in error.

S6BBP004WPAGE % REFERENCED BUT NOT FOUND INBACKUP FILE


Explanation: The specified page was referencedbut it cannot be located in the page headertable. This indicates one of the following:

• An incomplete backup or archive

• A corrupt Pagestore

A completion code of 12 (X'0C') is generated


S6BBP005WPOINTER ERROR ON PAGE %; EXPECTEDPREVIOUS %; FOUND %


Explanation: The chain pointers on the pagespecified do not match the pointers expectedby the index level above. Either the index orthe data chain is invalid. A completion codeof 8 is generated.



| 57

S6BBP006WPOINTER ERROR ON PAGE %; EXPECTEDNEXT %; FOUND %


Explanation: The chain pointers on the pagespecified do not match the pointers expectedby the index level above. Either the index orthe data chain is invalid. A completion codeof 8 is generated.


S6BBP007WPAGE TYPE ERROR; PAGE %, EXPECTED %,FOUND %


Explanation: The page type indicator on thespecified page is not consistent with otherpages in the chain. A completion code of 8 isgenerated.


S6BBP008WPAGE TYPE ERROR ON PAGE %, PAGE TYPE= %


Explanation: The page type indicator on thespecified page is not supported. If the typecode specified is in lowercase, an updateprocess (such as SIXBUILD, SIXDELETE, orTable Clear) may have failed to completeproperly. A completion code of 8 isgenerated.


S6BBP009WPAGE % HEADER CANNOT BE PROCESSED;REJECTED


Explanation: The header of the specified pagefailed to pass a validation test; the page wasrejected from the process. A completion codeof 8 is generated.


S6BBP010WINVALID PAGE TYPE %; PAGE % FROMBACKUP FILE


Explanation: The page type indicator on thespecified page is not supported. If the typecode specified is in lowercase, an updateprocess (such as SIXBUILD, SIXDELETE, orTable Clear) may have failed to completeproperly. A completion code of 8 isgenerated.


S6BBP011W% HAS BEEN DETECTED AS AN ORPHANPAGE


Explanation: The page specified in the messageis not referenced by any of the tables on thesegment, but the system indicates it is notavailable. The page header information forthis page will be listed in the ORPHAN LIST.A completion code of 4 is generated.



58 |

S6BBP012W% IS REFERENCED BUT INDICATED FREEBY THE SYSTEM


Explanation: The page specified in the messageis referenced by a table, but the system thinksit is available for use. The page will bereported in the ORPHAN LIST. A completioncode of 4 is generated.

Action: Stop using the segment and contactTIBCO Support immediately. If processingcontinues on the segment, duplicate pageerrors may occur.

S6BBP013WPAGE % IS AN ALLOCATE PAGE WITHROWS OR SIZE


Explanation: The page specified in the messagehas a page type of ALLOCATED, and therows and entry size fields are not zero. Acompletion code of 8 is generated.


S6BBP014WPAGE % HAS A TAGGED PAGE TYPE CODE-%-


Explanation: The page specified in the messagehas a page type that has been tagged for asecondary index build in progress or a tableclear in progress. The operation did notcomplete properly. A completion code of 8 isgenerated.

Action: Do one of the following with the tablewhose name you will find in the REFLOG(the output reference log file from BatchPointer Check):

• If a secondary index build was in progress,clear and rebuild the secondary index.

• If a table clear was in progress, try to clearthe table again. The table is not currentlyusable.

S6BBP015WPAGE % BIT MAP PAGE ERROR ; REJECTED


Explanation: The Bit Map Page indicated isinvalid and is ignored.


S6BBP016WPAGE % SEQUENCE ERROR OR DUPLICATEPAGE THIS PAGE IGNORED


Explanation: The Page indicated is in error.

Action: This can occur if you run the PointerCheck on a Cumulative Journal whichcontains multiple copies of changed pages. Ifthis is the case, run Pointer Check against atrue backup. Ensure that the segmentinvolved is not corrupted, take a backup andtry this program again. If the backup trulyreflects the content of your segment:

1. Protect the segment from any furtheraccess/updates.

2. Make sure all Journals, etc., are saved.

3. Contact TIBCO Support.


| 59

S6BBP018WPAGES MADE ORPHANS BY MISSINGCONTROL PAGE NOT REPORTED


Explanation: This warning indicates that at leastone control (bit map) page was reported asmissing. The pages whose usage is controlledby the missing control page(s), if checked,would be classified (possibly incorrectly) asorphans when the reason they are orphans isdue to the fact that the control page(s) aremissing. Refer message: S6BBP129E. Thismessage will occur twice: prior to the list ofall orphans and at the end of the list oforphans.

Action: This warning indicates a serious problemexists in the archive (backup) being checkedand under no circumstance should it be used,do not restore. Contact TIBCO Support.

S6BBP019WNO ROOT PAGE EXISTS


Explanation: The Resident Table Index (RTIX)indicates that a secondary index exists forthis table but it was not found.


S6BBP100EINVALID EXECUTION PARAMETERRECEIVED


Explanation: The execution parameter list wasinvalid. One or more of the parameters arenot supported.

Action: Processing terminated. Check spelling tomake sure the parameter is correct.

S6BBP101ESPECIFIED SEGMENT NUMBER CONTAINSMORE THAN 5 DIGITS


Explanation: The value of the segmentparameter or command line option is invalid.


S6BBP102ESPECIFIED SEGMENT NUMBER CONTAINSINVALID NUMERICS


Explanation: The segment number provided(EXEC-PARM/command option) is invalid.


S6BBP103EPAGE BUFFER SPACE NOT AVAILABLE


Explanation: Failed to obtain enough memoryfor index-level buffers.

Action: Make more memory available to theutility and retry.

S6BBP104EWORK FILE TO RETAIN PAGE IMAGESFAILED TO OPEN


Explanation: As the backup or archive file isprocessed, entire selected page images arecaptured. The file used to retain these pagesfailed to open for output. User abend code200 is issued.



60 |

S6BBP105EWORK FILE TO RETAIN INDEX POINTERSFAILED TO OPEN


Explanation: As the backup or archive file isprocessed, indexing information is capturedand stored in a variable blocked file. The fileused to retain this data failed to open foroutput. User abend code 200 is issued.


S6BBP106EINPUT ARCHIVE FILE TYPEDETERMINATION FAILED


Explanation: The S6BBRPTR program will acceptinput of a VSAM or a sequential file. Whenthe program attempted to determine the typeof the file supplied, an error was detected.User abend code 200 is issued.


S6BBP107EBACKUP/ARCHIVE TAPE FAILED TO OPENFOR INPUT


Explanation: The backup or archive sequentialfile (on tape or disk) failed to open for input.User abend code 200 is issued.

Action: Check the JCL and the message log.

S6BBP108EBACKUP/ARCHIVE VSAM FILE FAILED TOOPEN FOR INPUT


Explanation: The backup or archive VSAM filefailed to open for input. User abend code 200is issued.


S6BBP109EBACKUP/ARCHIVE FILE READ FAILED


Explanation: An attempt to read the next recordin the backup or archive VSAM file resultedin a nonzero return code. User abend code200 is issued.

Action: Check the log for a VSAM error code.

S6BBP110EERROR DETECTED WHEN FREEINGUNUSED SPACE


Explanation: When S6BBRPTR processes thebackup or archive file page, headerinformation is retained in tables above theline. When a new data set is detected, enoughspace is obtained to hold the maximumnumber of page headers. When the data set iscomplete, unused space is released. Theprogram detected a nonzero return code onthe free main. User abend code 200 is issued.



| 61

S6BBP111ESPACE NOT AVAILABLE TO RETAIN PAGEHEADER DATA


Explanation: When a change in an Object ServiceBroker page data set is detected, a block ofstorage is obtained that is large enough toretain page header information for all thepossible pages in the data set. Whenattempting to retrieve this space, the utilityreceived a nonzero return code. User abendcode 200 is issued.

Action: Check the storage limits above the line,and contact TIBCO Support.

S6BBP112EPAGE USAGE REFERENCE LOG FAILED TOOPEN


Explanation: An 80-character record is generatedfor each Object Service Broker page that isreferenced. The file used to retain theserecords failed to open. User abend code 200 isissued.


S6BBP113ESPACE NOT AVAILABLE FOR BITMAPPROCESSING


Explanation: A bitmap is used to indicate whichpages are assigned and which ones are free.The GETMAIN to obtain the above-the-linestorage for the bitmap table resulted in anonzero return code. User abend code 200 isissued.

Action: Check the storage limits above the line.

S6BBP114EORPHAN CAPTURE LOG FAILED TO OPENFOR OUTPUT


Explanation: A file is used to retain pageinformation for pages where actual andexpected usage differ. This file failed to openfor output. User abend code 200 is issued.


S6BBP115ESPACE NOT AVAILABLE BELOW THE LINEFOR I/O BUFFER


Explanation: The GETMAIN to obtain storagefor I/O buffers resulted in a nonzero returncode. The request was approximately 22 KB.User abend code 200 is issued.

Action: Increase the region size in your JCL.

S6BBP116EINDEX STACK OVERFLOW DETECTED;PROCESSING ABORTED


Explanation: The indexing levels for the tablebeing processed exceed the limit that theprogram was designed to handle (i.e., thereare too many indexing levels). User abendcode 200 is issued.



62 |

S6BBP117EPAGE HEADER TABLE OVERFLOWDETECTED AT PAGE %


Explanation: The page header information isretained in a table that is intended to hold themaximum number of pages in a data set. Theprogram detected a table overflow condition.User abend code 200 is issued.

Action: On z/OS, increase the memory availablefor S6BBRPTR. On Windows or Solaris, usethe -p flag for hrnbrptr to specify a largerbuffer to hold your Pagestore.

S6BBP118EPAGE RETRIEVAL ERROR


Explanation: When the utility attempted toretrieve a stored page image, either the PAGEfile failed to open, or the page could not befound. User abend code 200 is issued.

Action: See the job log for additional informationand contact TIBCO Support.

S6BBP119EPAGE CANNOT BE LOCATED IN INDEXTABLE


Explanation: When the utility attempted toretrieve an index page from the internalindex table, the specified page could not belocated. User abend code 200 is issued.


S6BBP120EINDEX RETRIEVAL ERROR


Explanation: When the utility attempted toretrieve an index record from the INDEX file,either the file failed to open, or the recordcould not be found. User abend code 200 isissued.

Action: See the job log for additionalinformation, and contact TIBCO Support.

S6BBP121EPAGE DATA SET SEQUENCE ERROR


Explanation: While processing the backup orarchive file, the utility detected a sequenceerror at the page specified. User abend code200 is issued.

Action: Sort the backup or archive file and rerunthe utility. If the error occurs again, contactTIBCO Support.

S6BBP122ENO VALID ARCHIVE RECORDS FOUND


Explanation: When the utility processes thebackup or archive file, only the pages for onesegment are processed. The segment numberis defaulted to zero unless a SEGMENTparameter is specified. The backup or archivefile did not contain any pages for thesegment being processed. User abend code200 is issued.

Action: Ensure that the backup or archive file isfor the segment being processed.


| 63

S6BBP123EINDEX FILE PROCESSING ERROR


Explanation: A sequence error was detected inthe index data capture file. User abend code200 is issued.


S6BBP124EINDEX ENTRY MEMORY MANAGEMENTERROR


Explanation: To increase program efficiency andreduce I/O requirements, captured indexinformation is retrieved from the INDEX fileand retained in memory tables when spacepermits. The process of retrieving the indexrecord resulted in an unexpected tableoverflow. User abend code 200 is issued.


S6BBP126EREQUESTED HEADER LOG FAILED TOOPEN


Explanation: The Header log could not beopened for output. This could be due topermissions or a lack of space, or because thefile already exists.

Action: Investigate and correct.

S6BBP127EDEFAULT FILES (NAMES) CANNOT BEOPENED


Explanation: At least one default filenamecannot be opened, probably because the filealready exists.


S6BBP129ECONTROL PAGE FOR THIS PAGE MISSING


Explanation: This is a serious error and indicatesthat under no circumstances should thearchive (backup) be used. Each segmentextent is preceded by a control page, whichcontains the usage bitmap, among otherthings, for the pages in its extent. As thecontrol page is missing, usage information ismissing. Therefore, all apparent used pagesin the extent would be classified as orphans.This message appears once for each missingcontrol page, even though all pages withinthe extent are affected, refer to messageS6BBP018W.

Action: Do not use this archive (backup) for anypurpose. Contact TIBCO Support.

S6BBP130ESYSTEM TABLE MISSING


Explanation: A system-required table was notfound on the MetaStor.



64 |

S6BBP131EDUPLICATE TABLE NAME


Explanation: A table name has been used morethan once.


S6BBP132ESYSTEM TABLE - ROOT PAGE# ERROR


Explanation: A system table that must have afixed root location does not have one.


S6BBP133ERTIX TABLE NAME SEQUENCE ERROR


Explanation: Table names on the Resident TableIndex (RTIX) must be in ascending sequence.


S6BBP134WSECONDARY INDEX INVALIDATED


Explanation: This line identifies a secondaryindex field whose index has been flagged asinvalid. If the table is parameterized, thesecondary index of at least one of the tableinstances is invalid.

Action: This is a warning only. The performanceof access via the secondary index might beslightly degraded as an extra read of theprimary key will be required. As primaryindices are normally resident, no extra I/Oshould be required.

S6BBP135EDATA PAGE ENTRY SIZE ERRORDETECTED AT xxxxxxxx


Explanation: The data page entry size indicatesthe total length of data (rows + lengths) onthat page. If the entry size does not match thedata rows various unpredictable problemscan occur when processing the table to whichthe data page belongs.


S6BBP136EDATA PAGE ROW SIZE ERROR DETECTEDAT xxxxxxxx


Explanation: Data page rows have a maximumand minimum row-length; an invalid lengthhas been found. Invalid row sizes can resultin various unpredictable problems whenprocessing the table to which the data pagebelongs.


S6BBP137ESEGMENT # NOT FOUND IN DBDLIB


Explanation: The segment number specifieddoes not exist in the input file.



| 65

S6BBP138ENEITHER ARCHIVE NOR DBDLIB COULDBE OPENED


Explanation: You must provide a valid BACKUPor DBDLIB DD statement.


S6BBP139EI/O ERROR READING SEGMENT


Explanation: The offline segment cannot beprocessed.

Action: Investigate the cause of the problem,correct it, and then try again.

S6BBP140WDSN XX BITMAP # PAGES= XXXXXXX LESSTHAN ACTUAL PAGES=XXXXXX


Explanation: In the data set number indicated,the number of pages the control pagecontrols (either in use or not) is less than thenumber of pages on the data set.

Action: No immediate action is required. Thisdiscrepancy should disappear the next timethe segment is formatted (S6BTLFPS) andrestored (S6BTLRPS).

S6BBP141EDSN XX BITMAP # PAGES = XXXXXXXGREATER THAN ACTUAL PAGES =XXXXXXXX


Explanation: In the data set number indicated,the number of pages the control page thinksit controls exceeds the actual number ofpages on the data set.

Action: This error could result in seriousproblems if the Data Object Broker attemptsto use the nonexistent pages beyond the endof the data set. If there is any danger of this,do not use this segment until the problem hasbeen resolved. Contact TIBCO Support.

S6BBP142EPAGE # XXXXXXXX INCORRECTLYLABELLED XXXXXXXX


Explanation: Page numbers should match thepage's location in the data set. The numberon this page does not.

Action: Do not use the segment until thisproblem has been resolved. Further usecould make a potentially serious problem,worse. Contact TIBCO Support.

S6BBP143EACCUMULATED FIELD SIZES NOT EQUALROW SIZE


Explanation: The field sizes within the currentrow have been totaled and do not equal thespecified row size.


The following information appears on thenext line:


66 |

• ACCSZ=Total value of accumulated fieldsizes (HEX)

• ROWSZ=Specified Row Size (HEX)

• ROWOF=Offset of row relative to pagestart (HEX)

• FLDOF=Offset of field relative to pagestart (HEX)

• ROW#=Number of the row, where 1 = 1st

S6BBP144EFIELD SIZE TOO BIG


Explanation: A field size encountered is too bigfor its row size.


The following information is provided onthe next line:

• FLDSZ=Size of field (HEX)




S6BBP145EINVALID FIELD SIZE


Explanation: An invalid field size wasencountered.


Following information provided on the nextline:

• FLDSZ=Invalid field size (HEX)




S6BBP146EDATA PAGE VALIDATION ERRORDETECTED AT PAGE XXXXXXXX


Explanation: During data page validation, theindicated page was found to be in error. Thefirst such error results in the utilityabandoning further validation of theindicated page's data. A more specificmessage identifying the error can be foundpreceding this message.


S6BBP147EDATA PAGE ROW SIZE IS TOO BIG FORPAGE XXXXXXXX


Explanation: A row size has been encounteredon this page that is larger than the specifiedheader-entry size.



• DATASZ=Header entry size (HEX)





| 67

S6BBP148EBAD FIELD OR ROW SIZE


Explanation: Using the row size and/or field sizeto traverse the page's data results inencountering an obviously incorrect rowsize.




• NXTSZ=Next Row Size (HEX)



• ROW#=Number of the row, 1 = 1st

S6BBP149EFILE I/O ERROR, FUNCTION '%', ERRNO % %


Explanation: A file I/O related error hasoccurred. Messages that follow give thecontext for the error.

Action: The function and errno information maybe used to further diagnose the problem.

S6BBP150EFILE I/O ERROR, FILE '%', FUNCTION '%',ERRNO % %


Explanation: A file I/O related error hasoccurred. Messages that follow will give thecontext for the error.

Action: The file, function, and errno informationmay be used to further diagnose theproblem.

S6BBP200EAUDIT FILE COULD NOT BE OPENED


Explanation: The file that holds the executionreport failed to open for output. This file isintended to be SYSOUT or a similar device.User abend code 201 is issued.

Action: Check the JCL to ensure that it is correct.

S6BBP201EERROR LOG FILE COULD NOT BE OPENED


Explanation: The file that holds the errormessage report failed to open for output.This file is intended to be SYSOUT or asimilar device. User abend code 201 is issued.

Action: Check the JCL to ensure that it is correct.


68 |

S6BBP202EERROR ON OUTPUT - INDEX TEMPORARYWORK FILE


Explanation: An error occurred when trying towrite to this work file.

Action: The error was probably due to either lackof space or an unauthorized work directory.Correct and retry.

S6BBP203EERROR ON OUTPUT - PAGE TEMPORARYWORK FILE


Explanation: An error occurred trying to write tothis work file.

Action: Probably due to either lack of space or anunauthorized directory. Correct the problemand try again.

S6BBP204EMISSING DATASET REFERENCE - ARCHIVEINCOMPLETE


Explanation: Pointer Check has been run on anincomplete segment backup.

Action: Processing terminated. This can occur ifbackups are taken of individual segment-data sets and those data sets are thenconcatenated. It can also occur (if tapebackup) if all tapes are not mounted. Checkthe number of data sets that comprise yoursegment and investigate.

S6BBP205EINCOMPLETE ARCHIVE - SYSTEM PAGES


Explanation: Pointer Check has been run on anincomplete segment backup.

Action: Processing terminated. This can occur ifbackups are taken of individual segment-data sets and those data sets are thenconcatenated. It can also occur (if tapebackup) if all tapes are not mounted. Checkthe number of data sets that comprise yoursegment and investigate.

S6BBP206EUNEXPECTED END OF FILE


Explanation: The archive (input file) appears tobe incomplete.


S6BBP207EPAGE ZERO MISSING


Explanation: The archive is incomplete.

Action: This utility cannot process archiveswhich have missing page zeros.


| 69

S6BBP208ECANNOT PROCESS ARCHIVE - JOBABORTED


Explanation: The file cannot be processed as anarchive. Something about the file leads theutility to believe that the file is not a legalarchive.

Action: Refer to the associated error message formore detailed information.

S6BBP209EILLEGAL PAGE NUMBER


Explanation: An illegal page number was readfrom the archive. This page number is higherthan the highest legal page number on asegment file.

Action: This error indicates either Pagestorecorruption or that the file being processed isnot an archive. If your investigation does notreveal the cause of the error, contact TIBCOSupport. Make sure that the Pagestore filethat appears to be corrupted is not used untilthe reason for the problem is discovered.

S6BBP210EILLEGAL SEGMENT NUMBER - IGNOREDSEG# XXXX PAGE#:XXXXXXXX


Explanation: A page was encounteredcontaining an invalid segment number.

Action: Check that the data set or file used asinput to the utility is valid. If it is, contactTIBCO Support.

S6BBP211EERROR IN dbdef FILE


Explanation: An error was discovered whenprocessing the dbdef file.

Action: The dbdef must be properly formatted asper the documentation. The error must becorrected before the utility can process therequested segment.

S6BBP212Edbdef FILE COULD NOT BE OPENED


Explanation: The dbdef file specified could notbe opened.


S6BBP213ESEGMENT FILE COULD NOT BE OPENED


Explanation: A segment file could not be opened.

Action: Make the segment file accessible and tryagain. This problem may be caused by thesegment file being active. The segment mustbe offline and if the target segment is theMetaStor, the Data Object Broker must beshut down.


70 |

BT: Segment Reset

S6BBT001ETable of FIELDS not found on Segment 0

Source: Segment Reset

Explanation: This is a MetaStor error.


S6BBT002ECould not retrieve page from Segment 0


Explanation: A MetaStor page read operationfailed.


S6BBT003ECould not retrieve page from Target Segment


Explanation: A target segment read pageoperation failed.


S6BBT004ETarget Segment has not been initialized (RTIX)


Explanation: The target segment cannot be resetin its present state.

Action: If the target segment contains data thatyou want to retain, the segment may becorrupted. Contact TIBCO Support.Otherwise, reformat the target segment andtry again.

S6BBT005ETarget Segment has not been initialized (DUPL)


Explanation: At least one RTIX table entry existson both the MetaStor and the target segment.The target segment cannot be reset under thiscondition.

Action: If needed data exists on the targetsegment, the segment cannot be reset.Otherwise, reformat the target segment andtry the utility again.

S6BBT006EPage Header error on Segment 0


Explanation: A problem was experienced withheader data from the MetaStor. This mayindicate data corruption.



| 71

S6BBT007ESegment 0 Page 1 Error


Explanation: There is a page format problem onthe MetaStor, which may indicate either datacorruption or a newly formatted segment 0.

Action: If the MetaStor has not been completelybuilt, complete the build according to thedocumentation. Otherwise, contact TIBCOSupport.

S6BBT008ETarget Segment has not been initialized (HDR)


Explanation: A target segment page has a badpage header.

Action: If the target segment contains neededdata, contact TIBCO Support. Otherwise,format the segment and try again.

S6BBT009ENo definition found for this table


Explanation: No definition was found on theMetaStor for a table (name) that existsaccording to the RTIX.


S6BBT012EFIELDS table error (Secondaries exceeded)


Explanation: The FIELDS table entry indicatesthat more Secondaries exist for the table thanthe permitted maximum.

Action: Investigate and correct the table'sdefinition data. If in doubt, contact TIBCOSupport.

S6BBT013EFIELDS table error (Field name)


Explanation: A table's definition data iscorrupted.


S6BBT014EUnexpected Page Type encountered, Segment 0


Explanation: A MetaStor page header corruptionwas encountered.


S6BBT015EUnexpected Page Type encountered, TargetSegment


Explanation: During the processing of the groupindex or data trees for the table being reset,an unexpected page type code was detected.Abend code 200 is issued.

Action: Validate the table structure usingS6BBRPTR.


72 |

S6BBT016ENo Tables defined for the Target Segment


Explanation: A request was made to reset asegment (target) but no tables exist for it onthe base segment.

Action: If the request is directed at the correctsegment, this run is unnecessary.

S6BBT255EAudit Trail File failed to OPEN


Explanation: The audit trail (printer) failed toopen. User abend code 932 is issued.

Action: Review job log for further details.

S6BBT501ENo Data Object Broker communicationidentification specified


Explanation: No communication identifier (e.g.,VTAM name) is specified in the startupparameters data set.

Action: Specify the Data Object Broker'scommunications identifier in the startupparameters data set, BPARM. The format is:

TDS=commid

S6BBT502ENo QUEUE name input


Explanation: The target queue name is notspecified in the STARTUP PARAMETERSdata set.

Action: Specify the target queue name in theSTARTUP PARAMETERS data set; theformat is:

QUEUE=queue_name

S6BBT503EData Object Broker is unavailable


Explanation: The batch server is not able tocommunicate with the Data Object Broker.

Action: Check the execution status of the DataObject Broker. The Data Object Broker mustbe active when the batch server is running.You may find messages in the batch server orData Object Broker JES joblogs to explainwhy communications cannot be establishedor sustained.

S6BBT504EConnection to the Data Object Broker failed


Explanation: The batch server failed to connectwith the Data Object Broker.


• Ensure that the Data Object Broker isrunning.

• Ensure that the communication identifierfor the Data Object Broker specified in theSTARTUP PARAMETERS TDS=parameter data set BPARM is correct.


| 73

S6BBT505ECommunication Error when reading@BATCH_QUEUE


Explanation: The batch server encountered anerror when processing the target batch queuedefinition.

Action: Ensure that the Data Object Broker isrunning as well as checking the validity ofthe @BATCH_QUEUE table.

S6BBT506EUndefined QUEUE Name: #


Explanation: The queue name provided in thestartup parameter BPARM data set is notproperly defined to Object Service Broker.

Action: Ensure that the queue name specified inthe QUEUE= startup parameter is correct.

S6BBT507EError encountered when reading@BATCH_REQUEST


Explanation: The batch server is unable toprocess batch requests on the target queue.

Action: Ensure that the Data Object Broker isrunning and check the validity of the@BATCH_REQUEST table.

S6BBT508ERequested JCL name (#) not found


Explanation: The JCL for this request could notbe read successfully from the Data ObjectBroker. The job was not submitted.

Action: Ensure that the Data Object Broker isrunning and check the validity of the@BATCH_JCL table.

S6BBT509EBatch server step JCL missing


Explanation: The JCL step for running the ObjectService Broker rule is missing in the@BATCH_JCL table.

Action: Check whether the Object Service BrokerJCL step is in the table instance@BATCH_JCL(@DEFAULT,HURON). If theJCL is missing, contact the Object ServiceBroker system administrator to have it addedto the table.

S6BBT510ENo batch server USERID specified


Explanation: No Object Service Broker DataObject Broker logon identifier is specified inthe startup parameter file BPARM.

Action: Ensure that a logon ID is specified in thestartup parameter file. The format is:

USERID=logon_identifier


74 |

S6BBT511EUnable to dynamically allocate a JES InternalReader


Explanation: The batch server cannot allocate aninternal reader for submitting the batchrequests. The server keeps trying to allocatethe reader until it succeeds.

Action: Contact your systems programmer toincrease the number of available internalreaders.

S6BBT512IBatch Queue (#) server waiting for next interval


Explanation: This message is produced when theprogram is in debug mode (the DEBUGparameter is set to YES), to provide feedbackon the server queue facility's activity. Usuallythis mode is required only at the request ofTIBCO Support.


S6BBT513IBatch server stopped by operator command(QUEUE=#)


Explanation: The batch server was shut down byan operator command (i.e., F jobname,STOP,or STOP jobname).


S6BBT514ISubmitted JOB# USERID=# JCLID=#


Explanation: This message is produced when theprogram is in debug mode (the DEBUGparameter is set to YES), to provide feedbackon the server queue facility's activity. Usuallythis mode is required only at the request ofTIBCO Support. The three parameters listed,identify the JES job number of the job justsubmitted, the requesting Object ServiceBroker user and the JCL name submitted.

Action: No action is required. You may use theJES job number to identify the batch jobssubmitted by this facility and to track theirexecution in JES. The USERID= parameteridentifies the Object Service Broker user thatrequested this job submission and theJCLID= parameter identifies the requestedJCL to execute.


| 75

BU: Batch Unload

S6BBU001I999999999 DATA OCCURRENCESUNLOADED

Source: Batch Unload

Explanation: This message provides a summarycount of the data occurrences (records)unloaded.


S6BBU002I999999999 TABLE INSTANCES ACCEPTED


Explanation: This message provides a summarycount of the table instances accepted byselection processing.


S6BBU003I999999999 TABLE INSTANCES REJECTED


Explanation: This message provides a summarycount of the table instances rejected byselection processing.


S6BBU004I999999999 TOTAL DATA OCCURRENCESUNLOADED


Explanation: This message provides a summarycount of all the data occurrences (records)unloaded.


S6BBU050WSELECTION RECORD 999 CONTAINSINVALID NUMERIC FOR PARAMETERXXXXXXXXXXXXXXXX


Explanation: The specified table instanceselection record contains invalid data for theindicated numeric parameter.

Action: The record is rejected.

S6BBU051WNULL-EQUIVALENT VALUE IS IGNORED


Explanation: Null-equivalent values (in columns64-79) are valid for packed decimal andbinary fields only. Columns 64-79 on this lineare ignored.

Action: None.


76 |

S6BBU100ETABLE TO BE UNLOADED DOES NOTCONTAIN ANY DATA


Explanation: The table that is to be unloadeddoes not contain any data; it is an emptytable.

Action: Determine whether the requested tablewas actually the one to be unloaded.

S6BBU101EUNEXPECTED PAGE TYPE DETECTED


Explanation: During the processing of the groupindex or data trees for the table beingunloaded, an unexpected page type codewas detected.

Action: Validate the table structure usingS6BBRPTR.

S6BBU102EGROUP INDEX PAGE HAS UNEXPECTEDENTRY LENGTH


Explanation: The expected length of a groupindex entry (based on the Object ServiceBroker definition cards) is less than the actuallength.

Action: Check the definition control cards.

S6BBU103EFILE OPEN ERROR; I - DEFINITIONCONTROL CARDS


Explanation: The definition control card filefailed to open for input. Abend code 200 isissued.

Action: See the job log for more details.

S6BBU104ETABLE INSTANCE SELECTION CONTROLNOT FOUND


Explanation: The table instance selection file ispresent, but the first record of the file is not acontrol record. Abend code 200 is issued.

Action: Correct the selection file.

S6BBU105ESPACE NOT AVAILABLE TO RETAININFORMATION FOR TABLE INSTANCESELECTION


Explanation: GETMAIN failed to retrievestorage for the table instance selection tableentries. Abend code 200 is issued.

Action: Check the job log and storage limits.

S6BBU106ERESIDENT TABLE INDEX ENTRY NOTFOUND FOR TABLE


Explanation: The table specified to be unloadedis not in the resident table index.

Action: Check the spelling of the table name, andmake sure the table type is TDS.


| 77

S6BBU107EFILE OPEN ERROR; - UNLOAD FILE


Explanation: The file used to retain unloadedrecords cannot be opened for output.


S6BBU108EDEFINITION CONTROL CARD TYPE CODENOT RECOGNIZED


Explanation: The type code on the tabledefinition control cards is not valid. Abendcode 200 is issued.

Action: Check the control card type (column 7).

S6BBU109ESPACE NOT AVAILABLE TO RETAININFORMATION FOR TABLE DEFINITION


Explanation: GETMAIN failed to retrieve spaceto hold the table definition information.Abend code 200 is issued.

Action: Check the job log for storage limits.

S6BBU110ESPACE NOT AVAILABLE TO RETAININFORMATION FOR GROUP INDEX PAGEIMAGE


Explanation: GETMAIN failed to retrieve spaceto hold a group index page image.

Action: Memory requirements exceed thoseprovided.

S6BBU111EDATA VALUE IS LARGER THAN DEFINEDLENGTH FOR FIELD XXXXXXXXXXXXXXXX


Explanation: The specified field name containsphysical data that is larger than themaximum length of the fields specified in thedefinition cards. Abend code 200 is issued.

Action: Correct the definition cards.

S6BBU112EDATA CONTAINS MORE FIELDS THANTHE DEFINITION


Explanation: An occurrence in the table containsmore fields than were specified by theDefinition Control File.

Action: Check the definition.

S6BBU113EPARAMETER COUNT VALUE NOTNUMERIC


Explanation: In the control file, the tabledefinition for the table being unloadedrequires that the # PARAMETERS field benumeric.

Action: The # PARAMETERS field must be blankor numeric; enter the correct value.


78 |

S6BBU114EFIELD COUNT VALUE NOT NUMERIC


Explanation: In the control file, the tabledefinition for the table being unloadedrequires that the # OF FIELDS field benumeric.

Action: The # OF FIELDS field must be blank ornumeric; enter the correct value.

S6BBU115EPARM/FIELD LENGTH VALUE NOTNUMERIC


Explanation: In the control file, the tabledefinition for the table being unloadedrequires that the PARAMETER/FIELDLENGTH field be numeric.

Action: The PARAMETER/FIELD LENGTHfield must be blank or numeric; enter thecorrect value.

S6BBU116EPARM/FIELD DECIMAL POSITION VALUENOT NUMERIC


Explanation: In the control file, the tabledefinition for the table being unloadedrequires that the # OF DECIMAL PLACESfield be numeric.

Action: The # OF DECIMAL PLACES field mustbe blank or numeric; enter the correct value.

S6BBU117EPARM/FIELD OFFSET VALUE NOTNUMERIC


Explanation: In the control file, the tabledefinition for the table being unloadedrequires that the FIELD OFFSET field benumeric.

Action: The FIELD OFFSET field must be blankor numeric; enter the correct value.

S6BBU118ETOTAL RECORD LENGTH SPECIFIED ASNONNUMERIC VALUE


Explanation: In the control file, the tabledefinition for the table being unloadedrequires that the TOTAL RECORD LENGTHfield be numeric.

Action: The TOTAL RECORD LENGTH fieldmust be blank or numeric; enter the correctvalue.

S6BBU119ETABLE DATA NOT ON THE REQUESTEDSEGMENT


Explanation: You have requested the unload of atable which does not exist on the segmentyou have indicated.

Action: Check that you have entered the correctsegment ID for the table you wish to unload.If it is wrong, correct it and try again;otherwise, contact your support staff toinvestigate why the RTIX entry for the table'sdata is missing.


| 79

S6BBU121E# OF PARMS/FIELDS DIFFERS FROM T SPEC


Explanation: The control file table definitiondiffers from that of the table definition on thePagestore. They must be the same.

Action: If the control file (table definition) youare using does not agree with the Pagestore'stable definition, then the control file must becorrected before the UNLOAD will accept it.

S6BBU122ESELECTION REQUESTED BUT NO PARMSIN TABLE


Explanation: Selection Criteria refers toparameter instances; the table beingunloaded has no parameters according to theDefinition Control File


S6BBU124ENULL-EQUIVALENT VALUE SPECIFIED ISINVALID


Explanation: Either the null-equivalent-code(LOWVALUE,HIGHVALUE,orNOVALUE)is misspelled or the value entered is notnumeric. Columns 64-79 are invalid.


S6BBU126ECONTROL FILE INCORRECT RECORDLENGTH


Explanation: This data set should be F or FB,LRECL = 80.


S6BBU133WNULL_EQUIVALENT VALUE FOUND INTABLE ROW FIELD


Explanation: The Null-equivalent value (thedefault value if nothing entered in columns64-79 or the value entered in columns 64-79)has been found in the table row fieldindicated. This means that the field, ifreloaded with the same null-equivalentvalue, will be loaded as NULL. The null-equivalent value should be a value whichwill not be found in the table data. Thismeans when it is used in unloaded file fieldsto represent NULL, it can be safely convertedback to NULLs if/when the data is loadedback to an Object Service Broker table.

Action: If this warning is ignored and the table isreloaded to an Object Service Broker table,the fields identified by this warning will beconverted to Null on the loaded table. Thismeans the reloaded table's data will bedifferent from the original table's (before thisunload) data. If an unused value cannot beselected to represent Null for this field in theunloaded file, this table should not beunloaded using this utility; use the onlineUNLOAD tool.


80 |

S6BBU134ENULL FOUND IN "NOVALUE" (NO NULLSALLOWED) FIELD


Explanation: "NOVALUE" placed in columns 64-79 of a field's definition control entryindicates that no Nulls will be found in thetable data for that field. A Null has beenfound and because no Null-equivalent valuecan be used on the output file, the integrity ofthe data cannot be maintained if the datawere to be reloaded to an Object ServiceBroker table.

Action: This utility cannot be used to unload thistable; use the online UNLOAD function.

S6BBU137EWARNINGS LIMIT EXCEEDED


Explanation: This utility will terminate after themaximum permitted warnings have beenissued.

Action: The number of warnings indicate that thetable data selected may not match thedefinition provided in the control file.Investigate the mismatch, make the requiredcorrections using BATCHUNLD_CARDS,and resubmit.

S6BBU138ITABLE ROW NUMBER


Explanation: This is the table row number thatcould not be unloaded.

Action: Check that the table selected matches thedefinition in the control file. Investigate thereason, if a mismatch exists.

S6BBU139EACCESS FOR UNLOAD DENIED


Explanation: The user does not have the correctauthorization to unload the table requested.

Action: Contact your Object Service BrokerSecurity Administrator if you should haveunload authority for the table requested.

S6BBU140EOUTPUT DATASET ERROR RECFM ORLRECL


Explanation: This data set must be RECFM VB.

Action: If data set is RECFM VB, check andcorrect LRECL/BLKSIZE.

S6BBU142ESECURITY TABLE(S) NOT ACCESSIBLE


Explanation: In order to check whether the userhas the authority to unload this table it isnecessary to access the Object Service BrokerSecurity Tables. These tables must be locatedon the MetaStor.

Action: Check with your system administrator.

S6BBU143ESYNTAX/SEMANTIC TYPE COMBINATIONNOT SUPPORTED


Explanation: The semantic type and syntax codecombination on the identified definition cardis not supported.



| 81

S6BBU144EUNICODE FIELD LENGTH MUST BE EVEN(DIVISIBLE BY 2)


Explanation: The identified definition cardcontains a field with a Unicode syntax whoselength is not even. This is not supported.


S6BBU145EUNICODE PARAMETERS AND KEYS ARENOT SUPPORTED


Explanation: Unicode syntax is not supportedfor a parameter or key fields.

Action: Correct the definition cards and run thejob again.

S6BBU200EAPPLID MISSING OR GREATER THAN 8CHARACTERS


Explanation: The TIBCO(r) Object Service Brokercommunication identifier (e.g., VTAMAPPLID) specified in the startup parametersis invalid or missing. Abend code 100 isissued.

Action: Correct the run time parameters.

S6BBU201ECOMMUNICATION PORT FAILED TO OPEN


Explanation: The TIBCO(r) Object Service Brokercommunication identifier (e.g., VTAMAPPLID) specified in the startup parametersis invalid or missing. Abend code 101 isissued.

Action: Correct the run time parameters.

S6BBU202EATTEMPT TO ESTABLISH SESSION FAILED


Explanation: The attempt to connect to the DataObject Broker failed. Abend code 102 isissued.

Action: Check that TIBCO(r) Object ServiceBroker is active.

S6BBU203EPAGE BUFFER SPACE NOT AVAILABLEBELOW THE LINE


Explanation: GETMAIN failed to retrievestorage below the 16 MB line. Abend code103 is issued.



82 |

S6BBU204ERELEASE MISMATCH, SESSION COULDNOT BE ESTABLISHED


Explanation: The connection to the Data ObjectBroker failed because the unload utility andData Object Broker are at different releaselevels. Abend code 104 is issued.

Action: Check the release of the load librariesused.

S6BBU205EPAGE READ PROCESSING FAILED;UNLOAD TERMINATED


Explanation: An attempt to retrieve a page failed.Abend code 105 is issued.

Action: See the job log for more details, andcontact TIBCO Support.


| 83

BX: Batch Secondary Index

S6BBX001ESPACE FOR DEFINITION TABLE IS NOTAVAILABLE

Source: Batch Secondary Index

Explanation: GETMAIN failed to get internalspace for the table to return the definition ofthe Object Service Broker table.

Action: Memory available is not sufficient toexecute.

S6BBX002ECONTROL CARD INPUT FILE FAILED TOOPEN


Explanation: The attempt to open the controlcard file for input failed.


S6BBX003EDEFINITION DOES NOT IDENTIFY A NEWSECONDARY


Explanation: You did not identify a newsecondary index. The secondary indexesidentified from the cards already exist.

Action: Correct the control cards.

S6BBX004EINTERNAL TABLE WORKING SPACE NOTAVAILABLE


Explanation: GETMAIN failed to get space toretain internal tables.


S6BBX020ECONTROL CARD TYPE CODE ISINVALID,(EXPECTED H OR S)


Explanation: The control card type (in column 1)contains an invalid code. Only H or S aresupported.

Action: See the card image with the message andcorrect the control cards.

S6BBX021EOUTPUT DEFINITION CARDS ARE OUT OFSEQUENCE


Explanation: The sequence numbers (column 3-5) for the output definition cards are notproperly sorted.

Action: Reorganize the Object Service Brokeroutput definition cards or correct thesequence numbers.


84 |

S6BBX022EOUTPUT DEFINITION CARD HAS INVALIDENTRY TYPE (R,P OR F)


Explanation: The entry type code (column 7) isinvalid for an Object Service Broker outputdefinition. Only R (record), P (parameter),and F (field) are acceptable.

Action: Change the entry type code to R, P, or F.

S6BBX023EDEFINITION TABLE OVERFLOW,INCREASE MAX FIELDS ON SPEC


Explanation: The internal table that retains theObject Service Broker table definitioninformation has overflowed.


S6BBX024EOUTPUT DEFINITION SEMANTICTYPE/SYNTAX NOT SUPPORTED


Explanation: The semantic type (column 46) andsyntax code (column 48) do not form a validcombination.

Action: Change either the semantic type or thesyntax to form a valid combination. Refer tothe Processing manual for a list of validcombinations or check the online definition.

S6BBX025EOUTPUT DEFINITION CARD FIELDLENGTH BLANK/OUT OF RANGE


Explanation: The field length (column 50-52) onthe output definition card is either blank orthe value is outside the range for the givensyntax or key type. A secondary index isconstrained to 127 bytes.

Action: Enter a field length that is within therange for the syntax or key type required.Check the online definition.

S6BBX026EOUTPUT DEFINITION CARD DECIMALPOSITION IS OUT OF RANGE


Explanation: The decimal position (column 54-55) specified for the Object Service Brokerparameter field is outside the range of thefield length.

Action: Enter a decimal position that is withinthe range for the field length.

S6BBX027EOUTPUT DEFINITION CARD KEY TYPE NOTSUPPORTED (" ",P/S)


Explanation: The Object Service Broker key type(column 57) is invalid. Only a blank, P(primary key), and S (secondary key) aresupported.

Action: Enter a P, S, or a blank for the outputObject Service Broker key type.


| 85

S6BBX028EINVALID UNIT COUNT SPECIFIED


Explanation: This field on the control data setmust be either blank or a number equal to orless than the actual total number of unitscomprising the dynamic unit name selected.


S6BBX029EUNICODE FIELD LENGTH MUST BE EVEN


Explanation: The field length for a field withUnicode syntax must be even.

Action: Correct the S6BBRSIX CNTRL inputcards and resubmit the job.

S6BBX030EUNICODE SYNTAX NOT SUPPORTED FORPARMS OR KEYS


Explanation: The definition cards provided tothe S6BBRSIX Offline Batch Utility indicatethat a field with a Unicode syntax is to beused as a parameter or key (primary orsecondary). This is not supported.

Action: Correct the input control cards andresubmit the job.

S6BBX040ESPECIFICATION CARD MAXIMUMPROCESS RECORDS NOT NUMERIC


Explanation: The maximum record field (column15-29) contains invalid numerics.


S6BBX041ESPECIFICATION CARD MAXIMUMNUMBER OF FIELD NOT NUMERIC


Explanation: The maximum number of fieldsvalue (column 31-33) contains invalidnumeric values.


S6BBX042ESPECIFICATION CARD MAXIMUM BLOCKSIZE IS NOT NUMERIC


Explanation: The maximum block size field(column 44-48) contains invalid numerics.


S6BBX060ESPACE FOR INDEX CONTROL STACK NOTAVAILABLE


Explanation: GETMAIN failed to get space toretain the index-level stack.



86 |

S6BBX061EREQUESTED SECONDARY INDEXALREADY EXISTS


Explanation: A definition key type was specifiedas S for a secondary index that alreadyexisted. Only specify S for new secondaryindexes.


S6BBX062ELOAD TABLE COULD NOT BE LOCATEDON CONTROL PAGE


Explanation: The requested table name is greaterthan all the TDS tables currently in theTIBCO(r) Object Service Broker data store.

Action: Check the spelling of the table name andcheck that the correct segment wasprocessed.

S6BBX063ELOAD TABLE COULD NOT BE LOCATEDON TABLE INDEX


Explanation: The Resident Table Index entry forthe requested table cannot be located.

Action: Verify the following:

• The spelling of the table name.

• The table type = TDS.

• The segment.

S6BBX064ESPACE NOT AVAILABLE FOR SECONDARYINDEX TABLE


Explanation: GETMAIN failed to get space toretain the TIBCO(r) Object Service Brokersecondary index table page.


S6BBX065ESECONDARY INDEX TABLE PAGE INVALID


Explanation: A secondary index table page (T)exists but contains no entries.


S6BBX080EDYNAMIC ALLOCATION OF TEMPORARYFILE FAILED


Explanation: S6BBRSIX detected a failure whenit attempted to allocate a temporary workfile.

Action: Check the unit on the specification card,and check the job log for additionalinformation.

S6BBX081ESPACE NOT AVAILABLE FOR TEMPORARYFILE DCB DEFINITION


Explanation: GETMAIN failed to get DCB space.

Action: Increase the below the line region size inyour JCL.


| 87

S6BBX100EWORK FILE USED TO RETAIN CAPTUREDDATA FAILED TO OPEN


Explanation: A sequential file is used to retaindata pointers captured from the ObjectService Broker Pagestore. The file intended toretain this data failed to open.


S6BBX101EINVALID PAGE TYPE DETECTED WHENEXTRACTING DATA


Explanation: An unexpected page type wasdetected during the attempt to captureinformation required for the secondary indexbuild.

Action: Run S6BBRPTR to verify segmentintegrity.

S6BBX102ESPECIFIED SYNTAX CODE INVALID FORCAPTURE PROCESSING


Explanation: You specified an invalid syntaxcode on a parameter or field required byextract processing.


S6BBX103ERESIDENT TABLE INDEX OFFSETCALCULATION ERROR DETECTED


Explanation: A Resident Table Index internalcontrol error is detected.


S6BBX104ESORT TYPE CODE NOT FOUND FORSECONDARY KEY SYNTAX CODE


Explanation: The syntax of a parameter, primarykey field, or secondary key field cannot betranslated for the sort parameter list.


S6BBX105ESECONDARY INDEX SORTING FAILED


Explanation: The routine used to sort theextracted data into the appropriate order forsecondary index creation failed.


S6BBX106EINPUT OPEN ERROR DETECTED ON INDEXTEMPORARY FILE


Explanation: The file used to retain indexinginformation failed to open during the indexconstruction phase of processing.



88 |

S6BBX107EINDEX CONTROL TABLE OVERFLOWED-TOO MANY INDEXING LEVELS


Explanation: The batch secondary index buildprocess was designed to support 5 levels ofindexing. This limit has been exceeded.


S6BBX108EGROUP INDEX CAPTURE FILE FAILED TOOPEN FOR OUTPUT


Explanation: The work file that retains groupindex (table instance) information failed toopen.


S6BBX109ETOO MANY SECONDARY INDEXES


Explanation: An attempt has been made to createmore secondary indexes than the ObjectService Broker system supports.

Action: Consult your System Administrator forthe maximum number of secondary indexesallowed for the release of Object ServiceBroker you are using.

S6BBX110ETABLE ROW DATA INVALID


Explanation: The utility is unable to process tabledata obtained from the Pagestore.

A possible cause of this problem is the use ofout-of-date control cards to attempt to buildthe secondary index after adding extra fieldsto the underlying table.

Action: Verify your control cards. If they arecorrect, contact TIBCO Support for assistancein resolving the issue.

S6BBX111ENUMERIC SECONDARY INDEX, VALUE ISNULL


Explanation: Secondary indexes cannot containnumeric nulls.

Action: It is not possible to create a secondaryindex for fields which have NULL valuesand are defined as either binary or packeddecimal syntax.

S6BBX112ETABLE HAS NO DATA


Explanation: The table specified has no data.

Action: Unload of empty table is not possible

S6BBX113IBROWSE MODE - REQUEST VALIDATIONCOMPLETED


Explanation: You requested the BROWSE=YPARM option which results in terminationafter the validation of the control file entries



| 89

S6BBX114EGET TABLE DATA PAGE FAILED


Explanation: The program was unable to read apage from the segment.

Action: Ensure the correct number of data setsfor the correct segment were opened atstartup. If this seems correct then take abackup/pointercheck of the segment andrerun the program and capture a dump.Contact support and supply output from allthree programs and the dump.

S6BBX124EREQUESTED TABLE NAME NOT FOUND ININDEX


Explanation: The table name specified in thecontrol file does not have an entry in therequested segment RTIX.

Action: Check the table name and the segmentnumber. If both are correct, the table must bedefined and contain data before a secondaryindex can be built.

S6BBX125ENO SECONDARY INDEXES SPECIFIED


Explanation: The control file does not indicateany secondary index fields

Action: Check to make sure the correct controlfile is being used, if it is then modify thecontrol file to indicate which field(s) are to beused as secondaries.

S6BBX126EERROR ENCOUNTERED JOB ABORTED


Explanation: An unexpected event occurred thatthe utility cannot handle.

Action: The detail associated with this message isessential to identify and resolve the problem.Print the audit report and pass it on to TIBCOSupport.

S6BBX135EWRITE TO PAGESTORE FAILURE


Explanation: A write to the Pagestore has failed.

Action: The detail associated with this message isessential to identify and resolve the problem.Print the audit report and pass to supportpersonnel.

S6BBX136EEXPECTED PAGE NOT FOUND ONPAGESTORE


Explanation: The page retrieved is not the pageexpected by the utility.

Action: Print the audit report and pass to supportpersonnel.

S6BBX137EOLD GROUP INDEX CAPTURE RECORDOUTPUT FAILURE


Explanation: A work file has run out of spaceand the job is aborted.

Action: Provide more space in the current orselected work directory and retry.


90 |

S6BBX144EINDEX CAPTURE WORK FILE FAILED TOOPEN FOR OUTPUT


Explanation: The utility needs to build a workfile. A path (-W) to the directory if specifiedwill result in the utility trying to use thatdirectory for the work file otherwise it willattempt to build the work file in the currentdirectory.

Action: Make sure you have the necessarypermissions in the directory you havespecified (or defaulted).

S6BBX147ENO INDEX INFORMATION ON WORK FILE


Explanation: The Index Work File is empty; noindex information was recovered for thetable.

Action: If the table contains no data, a secondaryindex cannot be built. If the table containsdata print the audit file and pass to supportpersonnel.

S6BBX157EFREE-PAGE REQUEST FAILURE


Explanation: The utility could not locate a freepage.

Action: The Pagestore segment is full; increasethe space available and try again.

S6BBX159EREQUIRED PAGE COULD NOT BERETRIEVED


Explanation: The utility was unable to retrieve apreviously retrieved page.

Action: Contact support personnel.

S6BBX170ERESIDENT TABLE INDEX UPDATEPREPARATION FAILED


Explanation: The utility was unable to locatepreviously retrieved information on theRTIX.


S6BBX255EAUDIT TRAIL FILE (PRINTER) FAILED TOOPEN


Explanation: A write-to-operator message isgenerated to indicate that the file used toretain the execution report (audit trail)cannot be opened.



| 91

CF: Configuration Processing

S6BCF001EError detected in the Execution EnvironmentEXEC parameter string

Source: Configuration Processing

Explanation: An error was detected whenprocessing the Execution Environmentstartup parameter string.

Action: Refer to the next message for moreinformation about the error.

S6BCF002EError detected in the HRNIN parameter file


Explanation: An error was detected whenprocessing the HRNIN DDNAME file forExecution Environment parameters.

Action: Refer to the next message for moreinformation about the error.

S6BCF003ELoad of configuration defaults member "%"failed


Explanation: The installation's configurationdefaults could not be loaded.

Action: Either an I/O error occurred whenattempting to load the configuration defaultsmodule, or the configuration defaultsmodule does not exist. Each type of ObjectService Broker Execution Environment has astandard defaults module name. In addition,the Execution Environment parameter

CONFIGURATION can be used to overridethe default module name. Verify that aconfiguration default module was generatedcorrectly.

S6BCF004IConfiguration defaults loaded from member"%"


Explanation: The configuration defaults for theExecution Environment were successfullyloaded.

Action: No action needs to be taken.


92 |

CM: General Communications

S6BCM000ECommunication protocol error occurred inconnection to %

Source: General Communications

Explanation: A message sent from one process toanother contains invalid data.

Action: If the messages that precede this messagedo not provide sufficient information todiagnose the cause of this failure, contactTIBCO Support.

S6BCM001EAttempt to send kill signal failed


Explanation: The attempt by one Object ServiceBroker process to kill another via the killsignal failed.

Action: Check the operating system errornumber provided with the message. Itshould indicate the reason for the failure.

S6BCM002EFailed to retrieve a message from the messageDLL


Explanation: An attempt to retrieve a messagefrom the message DLL failed.

Action: Make sure the file osmsgs.dll is located inthe installation's bin folder. If the messagepersists, contact TIBCO Support.

S6BCM003EFailed to write log message to the system eventlog


Explanation: An attempt to write a log messageto the system event log failed.

Action: Make sure your event log is not full.

S6BCM007ESocket operation failed, '%'


Explanation: The specified operation failed on asocket connection.


S6BCM008ECreate registry key\\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\EventLog\\Application\\ObjectStar


Explanation: An attempt to create the specifiedregistry key failed.

Action: Examine the operating system errorcodes to determine the reason for the failure.


| 93

S6BCM009EInsert EventMsgFile value into the messageDLL registry key


Explanation: An attempt to set the Object ServiceBroker event message file failed.


S6BCM010EInsert TypesSupported value into the messageDLL registry key


Explanation: An attempt to enter the typessupported by the Object Service Broker eventsource failed.


S6BCM011ERegister the event source


Explanation: An attempt to register the ObjectService Broker event source failed.


S6BCM800ICOMMUNICATION RESMGR CLEANUPSUCCESSFUL FOR ASID=X'%'|TCB=X'%'


Explanation: This message provides the status ofthe communications services cleanup thatthe resource cleanup module performed. Theresource cleanup module received controlfrom the z/OS Recovery TerminationManager because an address space or taskended unexpectedly.

The first variable holds ASID data ifprocessing is unilateral. The second variableholds TCB data if the cleanup processing isbilateral. Unilateral resource cleanup occursif a failing address space has insufficientresources or z/OS has terminated it. Bilateralresource cleanup occurs when theterminated task has not been removed fromthe address. The resource cleanup modulecan then attempt to coordinate cleanupbetween the terminated task and other tasksin other address spaces that had activecommunication with it.

Action: This message is informational only andindicates successful completion ofcommunications services cleanup. No actionis required.

S6BCM801ICOMMUNICATION RESMGR CLEANUPUNILATERAL PROCESSING SUCCESSFUL


Explanation: Unilateral resource cleanupprocessing completed successfully.Unilateral resource cleanup notifies allcommunications partners that thecomponent is no longer available. It occurs


94 |

when a z/OS address space containing anObject Service Broker communicationsenvironment terminated abnormally or thebilateral resource cleanup failed.

Action: This message is informational only. Noaction is required.

S6BCM810WCOMMUNICATION RESMGR CLEANUPCOULD NOT EXECUTE BILATERALCLEANUP, DEMOTING TO UNILATERALFOR %


Explanation: The resource cleanup module wasattempting to use bilateral resource cleanupto recover resources from a task that endedabnormally in an Object Service Brokeraddress space. The error, described in aprevious message, occurred during thiscleanup and unilateral cleanup occurredinstead. Unilateral resource cleanup notifiesall communications partners that thecomponent is no longer available.

The message includes the Object ServiceBroker communications identifier of theObject Service Broker environment involved.

Action: This message is informational only andindicates the cleanup steps taken. No actionis required.

S6BCM870EABEND= %, REASON=X'%' INTERCEPTEDIN COMMUNICATIONS REQUESTHANDLER


Explanation: This message is issued by theObject Service Broker communicationsrequest handler ESTAE routine because of anabend during communications processing.

The ESTAE recovery routine will attempt torecovery from the abend. MessageS6BCM871E is issued if recovery fails. Othermessages may also be issued to indicatesuccess or failure of the recovery. Diagnosticdata, consisting of an error record in thesystem log, is also provided and if possible,an SVC dump is collected.

The first variable contains the system or userabend code. The second variable containsthe reason code for the error.

Action:

1. Ensure the communications are stillavailable.

2. Collect any diagnostic informationavailable (System log printout, JES log forthe affected Object Service Broker addressspaces, and any dumps) and contactTIBCO Support.

3. Optionally, recycle your Data ObjectBroker or Execution Environment.

S6BCM871ECOMMUNICATIONS ESTAE CLEANUPFAILED - ABEND WILL BE PERCOLATED


Explanation: This message is issued in alongwith message S6BCM870E. A cleanupattempt during recovery processing for acommunications request handler failed. Nofurther communications recovery attempt isto be made for the request handler. The callerof the communications request may stillattempt recovery. If this recovery isunsuccessful, the affected Object ServiceBroker component is abnormally ended anda dump is requested.

Action: Collect diagnostic information available(system log printout, JES log for the affectedObject Service Broker address spaces, andany dumps) and contact TIBCO Support.


| 95

S6BCM889ECOMMUNICATION RESMGR CLEANUPFOR % FAILED for %


Explanation: The resource cleanup modulecannot successfully release task or addressspace resources allocated to Cross MemoryServices. This message is specific to the firstfailure encountered.

The first variable in the message representsthe Object Service Broker communicationsidentifier of the Object Service Brokerenvironment involved. The second variablerepresents one of the following:

• ABNDCDE=X'........' - a task abnormal endwas intercepted during resource cleanup.The text supplies data from the TCBCMPfield of the affected task. This is onlyproduced if resource cleanup failed.

• RTRNCDE=X'........' - a nonzero returncode was received during communicationstermination. The resource cleanup cannotbypass the condition causing thetermination.

• RESOURCES UNAVAILABLE - theminimal resources required for resourcecleanup (e.g., GETMAIN storage,establishing a recovery environment viaESTAE) are unavailable. Resource cleanupfailed.

Action: This message is only significant to ObjectService Broker and does not necessarilyindicate an error that impacts z/OS. Whenissued, the following symptoms may bedisplayed:

• A user may appear to be logged on afterthe Execution Environment that supportedthe user has terminated. The user is unableto re-logon to the same Data Object Broker.

• Data access requests from other users maybe queued indefinitely because of locks

still held by the user that appears to belogged on.

If any of these symptoms are displayed, dothe following:

• Using the Object Service Broker operatorinterface, terminate the user's session.

• In exceptional cases, shutdown and restartthe Data Object Broker.

• Collect any diagnostic informationavailable (system log printout, JES log forthe affected Object Service Broker addressspaces, and any dumps) and contactTIBCO Support.

S6BCM890ICOMMUNICATION RESMGR CLEANUPUNILATERAL PROCESSING MAY BEINCOMPLETE


Explanation: Unilateral resource cleanup didsuccessfully notify all communicationspartners that a communications componentis no longer available. Unilateral resourcecleanup occurs when a z/OS address spacecontaining an Object Service Brokercommunications environment terminatedabnormally or the bilateral resource cleanupfailed.

Action: Collect diagnostic information (systemlog printout, JES log for the affected ObjectService Broker address spaces, and anydumps) and contact TIBCO Support.


96 |

S6BCM898WMODULE % COULD NOT BE LOADED


Explanation: The program made a request for anadditional program module. However, thenamed module could not be loaded.

Action: Verify that the load module libraries havenot been damaged. This message shouldalways be paired with the S6BCM999Emessage providing the return code from theLOAD macro. Record this information andcontact TIBCO Support.

S6BCM900IOPENPORT FOR COMMUNICATIONIDENTIFIER "%" HASSUCCEEDED|PARTIALLYSUCCEEDED|FAILED


Explanation: This message summarizes theoutcome of processing that attempted tobuild a communications environment. If thisprocessing was not completely successful,then the situations or errors encountered aredescribed in detailed messages issued foreach Object Service Broker CommunicationsImplementation, prior to this message. Themessage provides the following information:

• The Communication Identifier that wasselected as a name for the Object ServiceBroker communications environment thatwas being built.

• The completion status (SUCCEEDED |PARTIALLY SUCCEEDED | FAILED),that summarizes the outcome of theprocessing to build the Object ServiceBroker communications environment.This is interpreted as follows:

• SUCCEEDED - Processing wascompletely successful. All Object

Service Broker CommunicationsImplementations that could be used,after any restrictions of the ExecutionEnvironment were taken into account,were successfully initialized.Communication can proceedoptimally.

• PARTIALLY SUCCEEDED -Processing was not completelysuccessful. Not all Object ServiceBroker CommunicationsImplementations that could be used,after any restrictions of the ExecutionEnvironment were taken into account,were successfully initialized, but atleast one was. Additional messageshave been issued describing thesituations and/or errors that weredetected. Communication canproceed, but may not be optimal.

• FAILED - Processing wasunsuccessful. No Object ServiceBroker CommunicationsImplementations were successfullyinitialized. Additional messages havebeen issued describing the situationsand/or errors that were detected. Nocommunication is possible.

Action: See the preceding detailed messagesissued for each Object Service BrokerCommunications Implementation todetermine what action is required for specificerrors or situations encountered by a specificObject Service Broker CommunicationsImplementation.


| 97

S6BCM901ICONTACT WITH COMMUNICATIONIDENTIFIER "%" HAS SUCCEEDED|FAILED


Explanation: This message summarizes theoutcome of processing that attempted tobuild a connection between two ObjectService Broker communicationsenvironments. If this processing was notsuccessful, then the situations or errorsencountered are described in detailedmessages issued for each Object ServiceBroker Communications Implementation,prior to this message. The message providesthe following information:

• The Communication Identifier that wasspecified as the name for the Object ServiceBroker communications environment thatwas to be contacted.

• The completion status (SUCCEEDED |FAILED), that summarizes the outcome ofthe processing to contact the Object ServiceBroker communications environment.These text data are interpreted as follows:

• SUCCEEDED - Processing wascompletely successful. At least oneObject Service BrokerCommunications Implementation wasable to provide resources to supportthe connection of the two ObjectService Broker communicationsenvironments. Communicationbetween the two Object Service Brokerentities can now proceed.

• FAILED - Processing wasunsuccessful. No Object ServiceBroker CommunicationImplementations were able to provideresources to support the connection ofthe two Object Service Brokercommunications environments.Additional messages have been issued

describing the situations and/orerrors that were detected. Nocommunication is possible.

Action: See the preceding detailed messagesissued for each Object Service BrokerCommunications Implementation todetermine what action is required for specificerrors or situations encountered by a specificObject Service Broker CommunicationsImplementation.

S6BCM980ESELECTED COMMUNICATION IDENTIFIER"%" AND CONNECTION PARTNERCOMMUNICATION IDENTIFIER ARE THESAME


Explanation: The Object Service BrokerCommunication Identifier that has beenspecified or selected for use by the currentObject Service Broker communicationsenvironment has also been supplied as theObject Service Broker CommunicationIdentifier to be contacted by the currentObject Service Broker communicationsenvironment. Such a configuration request ispointless, and considered to be an error.

Action: Determine how the Object Service BrokerCommunication Identifier was supplied tothe current Object Service Brokercommunication environment as a candidatefor communication and correct it. Forexample, examine execution parameter listsand control statements.


98 |

S6BCM981EALL COMMUNICATION IDENTIFIERS INPOOL "........" ARE IN USE


Explanation: While attempting to establish anObject Service Broker communicationsenvironment, Object Service Broker wasunable to allocate an Object Service BrokerCommunication Identifier from the pooldefined for the z/OS system on which theObject Service Broker communicationsenvironment is built. All Object ServiceBroker Communication Identifiers in thepool were tested and found to be in use byother Object Service Broker communicationsenvironments.


• Determine whether the pool is sufficientlysized (defined by the length of the numericsuffix on the Model Object Service BrokerCommunication Identifier) to support themaximum number of the Object ServiceBroker Execution Environments thatexecute on the z/OS System.

• If all these Object Service BrokerCommunication Identifiers are in use, thenconsider using another pool by followingthe procedures outlined in the ObjectService Broker Installation and Operationsfor z/OS manual.

S6BCM982ECOMMUNICATION IDENTIFIER "........" ISUNAVAILABLE, IN USE BY REGION "........"


Explanation: While attempting to establish anObject Service Broker communicationsenvironment, it was determined that theObject Service Broker CommunicationsIdentifier specified for use by the Object

Service Broker communications environmentwas already being used by another ObjectService Broker communicationsenvironment. The name of the z/OS Region(Started Task, Batch Job or TSO User) that iscurrently using the Object Service BrokerCommunications Identifier is supplied in themessage.


• Ensure that the correct Object ServiceBroker Communication Identifier has beensupplied to the Object Service Brokercommunications environment thatreceived this message.

• Ensure that the correct Object ServiceBroker communication identifier wassupplied to the Object Service BrokerRegion named in this message.

• Ensure that the Object Service BrokerRegion currently using the Object ServiceBroker communication identifier is notanother execution copy of the ObjectService Broker Data Object Broker thatreceived this message.

S6BCM990I% UNAVAILABLE, OTHER MESSAGESISSUED


Explanation: While attempting to establish anObject Service Broker communicationenvironment using a specific Object ServiceBroker Communications Implementation, asituation or an error was encountered thatprohibits the use of that specific ObjectService Broker CommunicationsImplementation. The nature of the situationor error is described in detail in othermessages issued to this message. Thismessage is usually accompanied by othermessages giving specific details about the


| 99

situation that was detected or the error thatoccurred. The name of the Object ServiceBroker Communications Implementationappears as variable data in the message text.

Action: See the other detailed messages todetermine what action is required for thespecific situation or error.

S6BCM991ECOMMUNICATION RESMGR CLEANUPDISCONNECT FROM % FAILED FORTCB=X'%', RC=X'%'


Explanation: This message indicates that acommunications environment was notsuccessfully built.

• The first variable is the name of the ObjectService Broker user for whom cleanup wasbeing undertaken when the failureoccurred.

• The second variable is the address of theTCB (Task Control Block) in the currentObject Service Broker communicationsenvironment address space for whichcleanup was being undertaken when thefailure occurred.

• The third variable is the return code, inhexadecimal, generated duringdisconnection failure.

Action: This message is only significant to ObjectService Broker and does not necessarilyindicate an error that impacts z/OS. Whenissued, the following symptoms may bedisplayed:

• A user may appear to be logged on afterthe Execution Environment that supportsthe user has terminated. The user is unableto re-logon to the same Data Object Broker.

• Data access requests from other users maybe queued indefinitely because of locks

still held by the user that appears to belogged on.

If these symptoms are displayed, do thefollowing:



• Collect diagnostic information (system logprintout, JES log for the affected ObjectService Broker address spaces, and anydumps) and contact TIBCO Support.

S6BCM992WSYSTEM AUTHORIZATION REQUIRED TOUSE %


Explanation: While attempting to initialize aparticular Object Service BrokerCommunications Implementation, an ObjectService Broker communications environmentdetermined that the z/OS address space isnot APF Authorized. APF Authorization isrequired to initialize this particular ObjectService Broker CommunicationsImplementation. This message indicates thatnot all the installation procedures,specifically those relating to APFAuthorization of load libraries and/orauthorization of programs executing underTSO are complete. The name of the ObjectService Broker CommunicationsImplementation appears as variable data inthe message text.

Action: It is possible that APF Authorization isnot available to this particular Object ServiceBroker component by a decision of theinstaller. If this is the case, this message canbe ignored. If this is not the case, then do thefollowing:


100 |

• Ensure that all the installation procedures,especially those relating to APFAuthorization of load libraries andauthorization of programs that executeunder TSO, were successfully completed.

• Restart the Object Service Brokercomponent that caused this message to beissued.

• If this message persists, contact TIBCOSupport.

S6BCM993IUSE OF % BYPASSED BY OPTIONSREQUEST


Explanation: A particular Object Service BrokerCommunications Implementation has notbeen initialized because it was explicitly orimplicitly specified that the Object ServiceBroker Communications Implementation bebypassed, using an HCS Options DataDefinition Statement. The name of the ObjectService Broker CommunicationsImplementation appears as variable data inthe message text.

Action: No action needs to be taken. Thismessage confirms that the Object ServiceBroker Communications Implementationwill not be used, as specified by the user.

S6BCM994W% INTERNAL ERRORS WERE RECORDED INTHE COMMUNICATIONS COMPONENT


Explanation: The message is issued duringObject Service Broker shutdown to indicatethat there were serious processing errorsdetected in the communications component

of Object Service Broker. The variable in themessage will indicate the number of errorsencountered. This message will be followedby S6BCM995 and S6BCM996.

Action: Refer to messages S6BCM995 andS6BCM996.

S6BCM995W% LOGREC RECORDS WERE WRITTEN AND% SYSTEM DUMPS WERE REQUESTED


Explanation: Message S6BCM994 is issued priorto this message and it is followed byS6BCM996.

The message is issued during Object ServiceBroker shutdown to indicate the extent ofdiagnostic data gathering performed forserious internal errors in theCommunications Component of ObjectService Broker. The first variable indicatesthe number of software symptom recordsthat were successfully written to theLOGREC data set. The second variableindicates the number of system dumprequests that were initiated to collectdiagnostic data concerning the errorsencountered.

Action: Collect the message log from the ObjectService Broker region, the LOGREC data andany system dumps taken, and contact TIBCOSupport for assistance.


| 101

S6BCM996ACOLLECT THE DIAGNOSTIC DATA ANDCONTACT TIBCO SUPPORT


Explanation: This message is issued followingmessages S6BCM994 and S6BCM995 duringthe shutdown of an Object Service Brokerregion, if serious internal errors wererecorded in the CommunicationsComponent during the life of the ObjectService Broker Region.

Message S6BCM997 may have been issued atthe time that the error was detected.

Action: Collect all the diagnostic data availableand contact TIBCO Support for assistance indetermining the cause of the error(s). Thediagnostic data may consist of any or all ofthe following:

• The JES JOBLOG of the affected ObjectService Broker regions

• The z/OS system log

• The z/OS LOGREC data set

• z/OS system dumps taken at the time ofthe errors

Note: System dumps taken for the errorsrecorded are titled:

*** OBJECT SERVICE BROKER COMMUNICATIONS INTERNAL ERROR - CONTACT TIBCO SUPPORT ***

S6BCM997ECOMMUNICATIONS INTERNAL ERRORDETECTED


Explanation: This is the first line of a multilinemessage that indicates the occurrence of aserious internal error in the Communicationscomponent of Object Service Broker.

The full text of the message includes theexecution PSW address, as well as themodule and control section name if known,where the error was detected. The internalcode for the error detected is listed with areason code for the error in hexadecimalform, followed by the register contents fromthe detecting module. The address spaceidentifiers (ASIDs) of the Home addressspace, the Primary address space, and theSecondary Address space are provided.

When the error is detected in an ExecutionEnvironment that permits it, an SDUMPX(extended SVC Dump) request is issued. Thesuccess or failure of the dump request isindicated in the last line of the message.

The last line shows the status of a systemdump request. It can be one of the following:

• WAS SUCCESSFULLY STARTED

• WAS SUPPRESSED BY DAE

• WAS NOT ATTEMPTED

• FAILED - RC=X'rc', REASON=X'rs'

Note that when the message indicates thatthe dump was suppressed by DAE (z/OSDump Analysis and Elimination), this isbecause it is a duplicate of an earlier dumptaken for the same error symptoms.

Action: If it is possible, Object Service Brokerattempts to recover from the error andcontinue processing. However, certain errorscan cause the loss of some communicationscapability and connectivity options.

If the error is of such a severe nature that it isimpossible to continue, even in a degradedmanner, then Object Service Brokerabnormally terminates with a User ABENDcode related to the error.

If Object Service Broker is able to continue,examine the joblog for any additionalmessages indicating the actions taken torecover from the error. The type of actions


102 |

may include such things as terminating aconnection with a user, droppingconnectivity to a Peer Object Service Broker,or the loss of a connectivity interface (e.g.,VTAM).

If the error was detected in an Data ObjectBroker, Execution Environment or DatabaseServer region, determine if the degradedcommunications capability is adequate forthe needs of your users and application mix.If not, then recycle the affected region inorder to restore full communicationscapability.

If the normal operation of your ObjectService Broker applications is unaffected,you may safely schedule the recycling of theaffected regions until a convenient time.

In any case, collect the system log, the JESjob log, any system dumps, and the z/OSLOGREC data and contact TIBCO Supportfor assistance.

S6BCM999EZ/OS LOAD REQUEST FAILED, R15=X'%'


Explanation: A request for a system servicefailed. A Return Code appears in register 15describing the reason for the request failure.The request is one of the following:

• ESTAE

• GQSCAN

• GETMAIN

• FREEMAIN

• BLDL

• LOAD

Action: Refer to the documentation for adescription of the service requested and thereason for the failure as described by theReturn Code. Determine remedial action byconsidering the information provided in themanual. If the message persists, contactTIBCO Support.


| 103

CS: CICS

S6BCS014ITIBCO(r) Object Service Broker/CICS interfaceinitialization complete.

Source: CICS

Explanation: The TIBCO(r) Object ServiceBroker/CICS interface activation is completeand the interface is ready to accept logons.


S6BCS022I...... user(s).

Source: CICS

Explanation: This message provides the numberof users who have logged on through thisExecution Environment.


S6BCS023ECICS Server Task attach failed, check JOBLOGfor error message(s)

Source: CICS

Explanation: An attempt to attach the TIBCO(r)Object Service Broker/CICS gateway taskfailed. More diagnostic message(s) may befound in the JOBLOG.

Action: Correct the error and retry.

S6BCS024ECLI Client CONNECT request failed. Reason:Error detected during CLI CICS task"STARTSESSION".

Source: CICS

Explanation: A severe error was detected whiletrying to connect the CLI CICS task to theStandby Session for the CLI Client.Additional error messages precede thismessage.

This error is likely caused by other events orerrors elsewhere in the system.

Action: Correct the errors indicated by thepreceding messages. If necessary, contactTIBCO Support for assistance.

S6BCS037EExecution Environment Subtask Locate FailureRC=X'...... ...'

Source: CICS

Explanation: A request to locate the ExecutionEnvironment gateway subtask has failed.Use the return code to determine the cause ofthe failure:

• X'00000004' - The MSB control block couldnot be located.

• X'00000008' - The MSB control block failedvalidation.

• X'0000000C' - A VSMLOC request failed.

• X'00000010' - A TCB validation failuredetected during TCB scan.

Action: Depending on the return code, do one ofthe following:


104 |

• RC=X'00000004' - Indicates that the DataObject Broker gateway task is not attached.Use the HOPS command to provide astatus of Object Service Broker. Issue theHINT command to restart the gatewaytask if required and retry the session.

• RC=X'00000008' - This is an internal error.Take an SDUMP of the address space if theproblem persists and contact TIBCOSupport.

• RC=X'0000000C' - This is an operatingsystem error. Take an SDUMP of theaddress space in question and contactTIBCO Support.

• RC=X'00000010' a TCB validation errormay occur when another application isATTACHing or DETACHing subtaskswhile TIBCO(r) Object Service Broker isscanning the TCBs. Retrying the sessionwill likely succeed. If problems persist,take a SDUMP and contact TIBCOSupport.

S6BCS038ECICS EXECUTION ENVIRONMENTSUBTASK ABENDED, TCBCMP=X'......'

Source: CICS

Explanation: This message is issued by theS6BCSCIC module. The ExecutionEnvironment subtask abended with theindicated completion code. Probable cause oferror may be that the Data Object Broker wasnot active and therefore OPENPORT wasfailed.

Action: Check the console log for error messagesissued by other TIBCO(r) Object ServiceBroker routines for more information. Ifunable to determine the error, do thefollowing:

1. Obtain the console log and storage dumps.


S6BCS039ICICS EXECUTION ENVIRONMENTSUBTASK DETACHED

Source: CICS

Explanation: This message is issued by theS6BCSCIC module. The ExecutionEnvironment subtask was successfullydetached.


S6BCS046ESYNTAX ERROR - CLEAR SCREEN ANDENTER AGAIN

Source: CICS

Explanation: This message is issued by theS6BCSCIC module.

Action: Do as the message suggests.

S6BCS047ISESSION ENDED

Source: CICS

Explanation: This message is issued by theS6BCSCIC module. The TIBCO(r) ObjectService Broker session has ended at therequest of the user.



| 105

S6BCS048ESESSION TERMINATED ABNORMALLY->CODE: ....

Source: CICS

Explanation: This message is issued by theS6BCSKRN module. The TIBCO(r) ObjectService Broker session has terminatedabnormally with the indicated ABEND code.

Action: See the previous diagnostic messages, ifany. Refer to the IBM manual for CICSmessages if it is a CICS ABEND code.

S6BCS049ETRANSACTION TERMINATED. CANNOTBE STARTED AT CONSOLE.

Source: CICS

Explanation: This message is issued by theS6BCSCIC module. You used a console toestablish a TIBCO(r) Object Service Brokersession.

Action: Use a dedicated terminal to establish aTIBCO(r) Object Service Broker session.

S6BCS050I........ ........ ........ ........

Source: CICS

Explanation: This message is issued by theS6BCSOPS module. This message displaysthe list of users that are currently logged onto the Object Service Broker Data ObjectBroker through this Object Service BrokerCICS interface.


S6BCS051ECICS: NO STORAGE AVAILABLE FORGETMAIN

Source: CICS

Explanation: This message is issued by theS6BCSCIC module. No more storage isavailable to start a TIBCO(r) Object ServiceBroker session.

Action: Wait for storage to become available andtry again (for example, when one or morelogged on users finish their TIBCO(r) ObjectService Broker session). If this situationoccurs often, more resources may be requiredfor this CICS region.

S6BCS052IUSER ID TERM ID USER ID TERM ID

Source: CICS

Explanation: This messages is a header forinformation that follows, dividingsubsequent information into columns.


S6BCS053Etttt uuuuuuuu cccc Session end action failed.Reason: rr

Source: CICS

Explanation: An attempt to perform the sessionend action failed for the indicated reason:

• tttt is the terminal ID

• uuuuuuuu is the user ID

• cccc is the transaction ID


106 |

Reason codes are documented in the CICSApplication Programming Referencemanual.

Action: Resolve the error situation as indicatedand try again. Contact TIBCO Support if youneed further assistance.

S6BCS054E"START TRANSID(xxxx)USERID(uuuuuuuu)" failed. Reason:rrrrrrrrrrrrrrr

Source: CICS

Explanation: Attempt to start the CLI sessionCICS background task failed for theidentified user and for the indicated reason,which can be one of the following:

• NOTAUTH The regular Object ServiceBroker transaction (default HURN) is notauthorized to issue the "START TRANSID"CICS command for the identified user.

• USERIDERR The identified user is notdefined to the external security system.

• TRANSIDERR The identified transactionis not defined to CICS.

• RESP=c1 RESP2=c2 These response codesare not translated into English. They aredocumented in the IBM CICS ApplicationProgramming Reference manual. RESP=c1was extracted from EIBRESP andRESP2=c2 was extracted from theEIBRESP2, fields in the EIB (EXECInterface Block) control block.

Action: Resolve the error situation as indicatedby the reason or the response codes. ContactTIBCO Support if you need furtherassistance.

S6BCS055EUNABLE TO LOAD mmmmmmmmABCODE=X'aaaaaaaa' REASONCODE=X'cccccccc'

Source: CICS

Explanation: Error detected when loading ObjectService Broker system modules. ObjectService Broker Execution Environmentstartup will be terminated.

In the message:

• mmmmmmmm is the module name thatthe load operation was failed

• aaaaaaaa is the abend code

• cccccccc is the reason code for the abend

Action: Correct the error and retry.

S6BCS056ECOMMAREA TOO SMALL FOROCCURRENCE

Source: CICS

Explanation: This message is issued by theBLTPASSD module. Object Service Brokerattempted to place a requested occurrence inthe user-created COMMAREA. The spaceremaining in this COMMAREA is too smallto contain the occurrence.


• Increase the size of the COMMAREApassed to Object Service Broker

• Reduce the size of the occurrence to bewritten to the COMMAREA

• If writing multiple occurrences to theCOMMAREA, reduce the number ofoccurrences


| 107

S6BCS058ETABLE NOT FOUND

Source: CICS

Explanation: This message is issued by theBLTPASSD module. The table specified in$SETCOMMAREA cannot be found.

Action: Ensure that the requested table exists.

S6BCS068ECONNECTION WITH DATA OBJECTBROKER LOST, ID=........

Source: CICS

Explanation: This message is issued by theS6BCSCIC module. The ExecutionEnvironment connection to the Data ObjectBroker has been lost.

Action: Check that Data Object Broker is stillactive, whether the user session wascanceled, and that VTAM is still functioning.

S6BCS070APRESS ENTER FOR NEXT SCREEN, OR PF3TO END.

Source: CICS

Explanation: This message is issued by theS6BCSOPS module. When there is more thanone screen of display output, the systemwaits for the action from the user to displaythe second and subsequent screens, or to endthe transaction.

Action: Follow the instructions of the messageand act accordingly.

S6BCS076I..../........ Session cancelled by operator command

Source: CICS

Explanation: This message indicates that thecurrent session has been canceled by a HCUStransaction entered from another terminal oran OS console or lost terminal error logic in aCICS environment.

Action: Check with the system administrator tofind out why the session was canceled. Youmay reconnect to Object ServiceBroker/Object Service Broker and continueprocessing.

S6BCS077ISession terminated - terminal timed out

Source: CICS

Explanation: This message is issued by theS6BCSCIC module. The current session wasabnormally terminated because theinstallation terminal inactivity threshold wasexceeded.

Action: Discuss with the System Administrator ifthe threshold is impractical and modify it ifnecessary.

S6BCS078EInternal storage STACK error, RC=X

Source: CICS

Explanation: An internal storage stack requesthas failed. The failure can be identified byanalyzing the return code. A CICStransaction dump will be taken with adumpcode of HEXC.

Action: Possible return codes are:

• X'00000004' - Storage area provided isinsufficient for request


108 |

• X'00000008' - Invalid storage requestlength

• X'0000000C' - Storage area notdoubleword-aligned

The HEXC transaction dumpcode is used byObject Service Broker to identify a CICStransaction associated with this message.Format the CICS transaction dump using theutilities supplied with CICS, and contactTIBCO Support for assistance.

S6BCS080EInvalid PARMS length passed in CICSCOMMAREA

Source: CICS

Explanation: The two byte binary COMMAREAlength supplied in the COMMAREA isinvalid.

Action: Recheck length by calling user programand correct.

S6BCS081IExecution Environment has been recycled

Source: CICS

Explanation: The Execution Environment hasbeen recycled since the last time the userpressed <Enter>.

Action: Log back on to Object Service Broker.

S6BCS082IApplication owning region has been recycled

Source: CICS

Explanation: The Application Owning Regionhas been recycled. The user session no longerexists.

Action: Log back on to start a new user session.

S6BCS083ECICS Transaction 'hhhh' Abend 'xxxx' detectedon terminal 'tttt' for user 'uuuuuuuu' at'hh:mm:ss'

Source: CICS

Explanation: A CICS transaction abend wasdetected for the specified transaction. Theterminal and user identification areidentified in the message.

Action: A CICS transaction abend wasintercepted. A CICS transaction dump willbe scheduled for most abends. Exceptionsare: ATCH, ATCI, ATNI, AZ** and AX**codes.

Refer to the CICS Messages and Codesmanual for a description of the abend. Savethe CICS transaction dump and allassociated logs for analysis by TIBCOSupport if the problem appears to be causedby Object Service Broker.

Recovery of the error will be attemptedexcept for the abend codes noted above.Message S6BCS084I accompanies thismessage and provides information on theaction scheduled by Object Service Brokerfor this error condition.

S6BCS084IAction taken for user 'uuuuuuuu': aaaaaaaabbbbbbbb cccccccc

Source: CICS

Explanation: A CICS transaction abend has beendetected as indicated by the associatedS6BCS083E message. This message describesthe action scheduled as a result of the abend.

Action: The uuuuuuuu in the message identifiesthe user session and the fields aaaaaaaa,bbbbbbbb, and cccccccc indicate the actionsscheduled as a result of the associated errorcondition. Possible values include:


| 109

• LOSTTERM - indicates that the terminalfacility cannot be used.

• CICSDUMP - a CICS transaction dumphas been scheduled for this error. Save thisdiagnostic information for analysis.

• TERMSESS - the user session must beterminated. The abend is unrecoverable.

• RECOVERY - an attempt to recover thesession will be scheduled as the error maybe recoverable.

• TERMIMM - a recursive non-recoverableabend situation has been detected andimmediate session termination must beperformed.

• CANCEL - an abend has been detectedwhile the session is in the process ofterminating.

S6BCS085ISession lost, please reenter transaction.

Source: CICS

Explanation: The user session cannot becontinued because of an undeterminedcondition.

Action: Your session will be terminated. Performyour logon again to reestablish a valid ObjectService Broker session. If the logon attemptfails, contact your Object Service Brokersystem administrator. Use the HOPScommand to verify that your original sessionhas been terminated successfully. Save allCICS and Data Object Broker job logs anderror logs for analysis.

S6BCS086ENOT AUTHORIZED TO WRITETEMPORARY STORAGE. SESSIONCANCELLED

Source: CICS

Explanation: An unauthorized attempt wasmade to write to TOR temporary storage.

Action: The transaction is ended after the abovemessage has been issued.

S6BCS087EUser ........ session lost connection with DOB,enter CICS canceluser transaction to cancelsession

Source: CICS

Explanation: The named user in the message haslost their session with the Data Object Broker.The Execution Environment is unable toschedule a CICS HCUS command to cancelthe user because it is running unauthorized.

Action: Manually issue an Object Service BrokerCICS HCUS transaction against the nameduser to cancel them.

S6BCS100IS6BCSNEM started HCUS TTTTNNNNNNNNrouted to AAAAAAAA

Source: CICS

Explanation: This message is issued when aHCUS termid command is scheduled byS6BCSNEM because of a lost terminalcondition. It appears in the CICS region'sCSMT log, or in the case of an MROconfiguration, in the TOR CICS region'sCSMT log.

The variables represent the following:

• TTTT - The user's CICS terminal ID


110 |

• NNNNNNNN - The user's VTAMterminal ID

• AAAAAAAA - The VTAM applid of theCICS region where the HCUS {TTTT |NNNNNNNN} request will be processed.


S6BCS101ES6BCSNEM ERROR: EEEEEEEETERMID=TTTT

Source: CICS

Explanation: This message is issued when anerror condition is detected duringS6BCSNEM lost terminal processing. Itappears in the CICS region's CSMT log, or inthe case of an MRO configuration, in the TORCICS region's CSMT log.

The variables represent the following:

• TTTT - The user's CICS terminal ID

• EEEEEEEE - The CICS error condition,which can be any of the following errorcodes:

1. INVREQ, IOERR, NOAUTH,SYSIDERR, TERMIDERR,TRANSIDERR, ISCINVREQ

2. NOCOMMA

3. INVAPPL

A CICS dump is generated with abend codeSNEP.

Action: Analyze the generated CICS dump. Thedescriptions of the error codes in item 1 aredescribed in the IBM CICS/VS applicationprogrammer's guide. Item 2 indicates that acommon area was not specified in theprogram calling S6BCSNEM. Item 3 indicatesthat the VTAM applid of the AOR is notdefined in the TOR.

S6BCS102ES6BCSOPT ERROR:WWWWWWWWREASON:XXXXXXXX TERMID=YYYYSYSID=ZZZZ

Source: CICS

Explanation: This message is issued when anerror condition is detected in the programmodule S6BCSOPT. It appears in the CSMTlog of the CICS owning region. A CICS dumpis generated with a dump code of HOPT. Thevariables represent the following:

• WWWWWWWW - The EXEC commandthat returned the error response. Thepossible values are RETRIEVE andSTART.

• XXXXXXXX - The error condition whichcan be any of the following: INVREQ,IOERR, ISINVREQ, NOTAUTH,SYSIDERR, TERMIDERR, TRANSIDERR,ENDDATA, ENVDEFERR, LENGERR,NOTFIND.

• YYYY - The ID of the user's CICS terminal.

• ZZZZ - The system ID of the CICSapplication owning region.

Action: Analyze the CICS transaction dump.Detailed error descriptions are documentedin the IBM CICS/VS applicationprogrammer's guide.


| 111

S6BCS120ETRANSACTION requires valid Userid. Sessioncancelled

Source: CICS

Explanation: The Cancel User transaction mustbe followed by a blank and then a userid.Example: HCUS BILLUSER.

Action: Storage areas are released then thetransaction is terminated. The user shouldreenter the transaction in the correct format,as shown in the given example.

S6BCS121ETRM. TRANS. requires parm; SHUT(SHUTD)or SHUTI

Source: CICS

Explanation: The Session Terminationtransaction must be followed by a validparameter, which maybe either SHUT,SHUTD (which is functionally the same asSHUT) or SHUTI. Example: HTRM SHUT,where HTRM is the Session Terminationtransaction.

Action: Storage areas are released and thetransaction is terminated. The transactionshould be reentered. The example illustratesthe correct format.

S6BCS123ELOAD OF MODULE, S6BCSKRN FAILED.CICS INTERFACE INITIALIZATIONTERMINATED

Source: CICS

Explanation: An attempt to load the CICS-ObjectService Broker interface initializationmodule, S6BCSKRN failed. Because of this,the Object Service Broker transaction isunable to continue and is thereforterminated.

Action: Retry the Object Service Brokertransaction. If the same failure persists,contact the CICS technical supportrepresentative.

S6BCS124ETRANSACTION requires valid parm; refer todocumentation.

Source: CICS

Explanation: The parameters passed to this CICStransaction are invalid. Additional errormessages may precede or follow thismessage.

Action: Refer to the Object Service Brokerdocumentation for the valid parameters.


112 |

S6BCS125EInvalid transaction from terminal

Source: CICS

Explanation: The TIMEOUT and securitytransaction, HCSS is only supposed to run bymeans of a started transaction. Instead, theuser entered HCSS from the terminal, whichis not permitted.

Action: Storage areas are released and thetransaction is terminated. The HCSStransaction will never work, when enteredfrom a terminal.

S6BCS126EThe HOPS transaction is no longer supported.Please use HINQ for inquiry and HCUS forcanceluser

Source: CICS

Explanation: The HOPS transaction has beenreplaced by HINQ, HCUS, and HFUS

Action: Use HINQ for userlist, HCUS for canceluser session, and HFUS for force usersession.

S6BCS127EProgram XXXXXXXX received bad return codefrom HDRBUSR.RC = XXXX

Source: CICS

Explanation: Program XXXXXXXX received aninvalid return code from programHDRBUSR.


S6BCS128EInvalid or unsupported function code XXXXpassed to S6BCSKRN

Source: CICS

Explanation: The function code XXXX passed toprogram S6BCSKRN was invalid or is notsupported in the current ExecutionEnvironment (CICS, IMS, NEE).



| 113

DA: Dynamic Allocation

S6BDA013EDAIR ERROR xxxx/yyyyDSN='________.________.______'

Source: Dynamic Allocation

Explanation: A dynamic allocation erroroccurred for an Object Service Broker dataset. xxxx is the error reason code and yyyy isthe information code. For an explanation ofthe codes, refer to the appropriate IBMmanual that describes dynamic allocation(SVC99) and its functionality.

For example, error code 1708 means that thedata set is not cataloged.

Action: Look up the codes and take correctiveaction. Contact the system programmerresponsible for Object Service Broker forassistance.

S6BDA014WENQUEUE FAILEDDSN='________.________.________.___'

Source: Dynamic Allocation

Explanation: The dynamic allocation for therequested data set failed because the data setwas being enqueued by another user. Furtheraction is taken based on how critical the dataset is to the system.

Action: Attempt to identify the user of therequired data set and have them release it.Once the data set is available, take the actionappropriate for the state of the system.


114 |

DB: File Task

S6BDB001EFILE INITIALIZATION FAILED

Source: File Task

Explanation: During Object Service Brokerstartup processing, certain databaseinitialization errors were detected. Othermessages have already indicated theenvironmental errors. Object Service Brokerterminates abnormally with abend code 301.

Action: Investigate the relevant messages andtake corrective action. Contact the SystemProgrammer responsible for Object ServiceBroker.

S6BDB002IFILE INITIALIZATION OK

Source: File Task

Explanation: Object Service Broker databaseinitialization completed successfully atsystem startup. For cold starts, the activedatabase configuration is as defined in theDBDLIB. For warm starts, the active databaseconfiguration is the same as it was when thesystem abnormally terminated.

Action: No action required. If active ObjectService Broker segments are subsequentlyrequired for BATCH operations, they mustbe manually shut down with Object ServiceBroker console commands before the BATCHjobs are submitted.

S6BDB003WUNKNOWN VSAM EVENT COMPLETED

Source: File Task

Explanation: Internal logic error. A VSAMrequest that the Object Service Brokersupervisor does not recognize hascompleted.


S6BDB004WVSAM HEX REQ=__ RC=__ FB=__R15=________ RBA=________

Source: File Task

Explanation: Object Service Broker detected aVSAM error. The error was intercepted andthe request code (REQ), return code (RC),feedback code (FB), macro return code (R15),and the address of the failing record (RBA)are shown in the message. Standard z/OSsystem messages of the form IECxxxIprecede the Object Service Broker message.

Action: Contact the Object Service Broker systemadministrator. Reason codes are documentedin z/OS DFP VSAM Macro Instructions.z/OS messages are documented in the z/OSSystem Messages manual.


| 115

S6BDB005EUNDEFINED EVENT CODE X'____'

Source: File Task

Explanation: Internal logic error. Object ServiceBroker supervisory code detected an invalidsystem service request. The transaction isaborted.


S6BDB006IDSN=________.________.________.________ ...

Source: File Task

Explanation: This message is issued to indicatethe name of the data set associated with afailed I/O request.

Action: No action is required for this message.Refer to preceding messages for details of thefailure.

S6BDB007WFREBUF ERROR FOR PAGE QUEUE

Source: File Task

Explanation: During transaction cleanupprocessing, a transient work area was notreturned to the buffer pool. Object ServiceBroker continues to run, possibly withdegraded resources. Cumulative errorcounts are available in the BUFFER pooldisplays.


S6BDB008WINVALID FILE REQUEST

Source: File Task

Explanation: Internal logic error. The ObjectService Broker COMMIT processor detectedan invalid system service request. Thetransaction is aborted.


S6BDB009WLOGGING ERROR - COMMIT ABORTED

Source: File Task

Explanation: I/O errors were detected duringnormal logging operations. The COMMITtransaction was aborted.

Action: See the accompanying messages fordetails about the error. Contact TIBCOSupport.

S6BDB010EREDOLOG PRIMARY AND DUPLEX CI-SIZE/DATASET SIZE DIFFERENCEDETECTED

Source: File Task

Explanation: During start-up validation of theData Object Broker, it was determined thatthe primary and duplex REDOLOG data setdefinitions are different, that is, either theControl Intervals or the allocated spaces arenot identical.

The Data Object Broker cannot initialize.

Action: Correct the difference and retry.

Note: If the REDOLOG is to be redefined,ensure the CACHE is redefined as well.


116 |

S6BDB013WERROR DURING RESIDENT PAGE LOOKUP

Source: File Task

Explanation: During the freeing of locks, the RPELOOKUP routine compared the owner of thepage to be freed with the requestor. Therequest failed because the owner andrequestor did not match.


S6BDB015WSESSION NOT ON DEFERRED PAGE QUEUE

Source: File Task

Explanation: During session cleanup, nodeferred page requests were found on thequeue. The system continues processing.


S6BDB016ISESSION REMOVED FROM PAGE QUEUE

Source: File Task

Explanation: The session was removed.


S6BDB017ICLEANUP DONE - FREE SESSBUFF

Source: File Task

Explanation: A cleanup was performed; sessionbuffers are free.


S6BDB018EINVALID DBD RELEASE IDENTIFIER

Source: File Task

Explanation: An attempt has been made to use aDBD library which is incompatible with theversion of Object Service Broker beingexecuted. The Data Object Broker or utilityprogram is terminated.

Action: Regenerate the DBD using the correctrelease of Object Service Broker and re-execute the failing program.

S6BDB020AREDOLOG WRITE ERROR

Source: File Task

Explanation: An error occurred while writing tothe REDOLOG. A previous S6BDB026Wmessage was issued detailing the nature ofthe error. If it is a physical error, the write isretried once. When this error occurs duringsystem initialization or on the last availableREDOLOG data set, the system is terminatedand a subsequent S6BDB027A message isissued. If a DUPLEX REDOLOG data set isavailable and DUPLEXLOGFAIL is set toCONTINUE, system processing continuesusing the remaining data set.

Action: Contact your Object Service Brokersystem administrator.

If the system was terminated, follow theaction outlined for message S6BDB027A.

If system operation continued, prior to thenext restart of the system it will be necessaryto re-synchronize the two redolog data setsas outlined in the Object Service BrokerBackup and Recovery for z/OS manual.


| 117

S6BDB021AREDOLOG DUPLEX WRITE ERROR

Source: File Task

Explanation: An error occurred while writing tothe REDOLOG. A previous S6BDB026Wmessage appeared detailing the nature of theerror. If it is a physical error, the write isretried once. When this error occurs duringsystem initialization or on the last availableREDOLOG data set, the system is terminatedand a subsequent S6BDB027A message isissued. If a the REDOLOG data set isavailable and DUPLEXLOGFAIL is set toCONTINUE, system processing continuesusing the remaining data set.

Action: Contact your Object Service Brokersystem administrator.

If the system was terminated, follow theaction outlined for message S6BDB027A.

If system operation continued, you must re-synchronize the two redolog data sets priorto the next restart of the system, as outlinedin the Object Service Broker Backup andRecovery for z/OS manual.

S6BDB026WVSAM LOG ERROR RC=__ FB=__

Source: File Task

Explanation: An I/O error occurred during logprocessing. The return code (RC) andfeedback code (FB) are given in the message.

Action: Contact your Object Service BrokerSystem Administrator about a possiblemedia or space problem.

S6BDB027A'_______' SUSPENDED DUE TO PHYSICALERRORS

Source: File Task

Explanation: This message results from the I/Oerror mentioned in message S6BDB026W.The system retries once, and then stopslogging. If the problem is with the redolog,the system shuts down. If the problem is withlogging to anything else, processing carrieson as usual. The variable portion of themessage text indicates which logencountered the I/O error.

Action: Contact your Object Service Brokersystem administrator. Recovery from loss ofthe REDOLOG requires manual interventionas detailed in the Object Service BrokerBackup and Recovery for z/OS manual. Theminimum action required is the formatting ofthe REDOLOG/DUPLEX data sets.

S6BDB028EDBDLIB OPEN ERROR

Source: File Task

Explanation: Object Service Broker startupprocessing, or an Object Service Brokerutility program, is unable to open theDBDLIB. This message is accompanied bystandard z/OS messages indicating theDDNAME and reason code. Object ServiceBroker terminates abnormally.

Action: Verify that the Object Service Brokerstartup procedure or utility programcorrectly identifies a valid DBDLIB.


118 |

S6BDB029EDBDLIB READ ERROR

Source: File Task

Explanation: Object Service Broker startupprocessing was unable to read the DBDLIB.Object Service Broker terminates abnormally.

Action: Ensure that an Object Service BrokerDBGEN has been successfully run to build avalid DBDLIB. Accompanying VSAM errormessages indicate the nature of the problem.

S6BDB030EDBDLIB DEFINITION ERROR

Source: File Task

Explanation: During initialization, the DBDLIBwas found to be logically incorrect.

Action: Contact the Object Service Broker SystemAdministrator. Ensure that a valid DBDLIBwas allocated to the Object Service Brokerstartup procedure or batch utility JCL.

S6BDB031EDATABASE OPEN ERROR X'__'

Source: File Task

Explanation: An error was encountered whileopening the VSAM data set specified inmessage S6BDB090I or S6BKX002I. AllObject Service Broker Pagestores andjournals, and the redolog, are opened atinitialization. Object Service BrokerPagestores can be reopened dynamicallyusing the DBONLINE command. Journalsare reopened at the conclusion of SPINprocessing. The VSAM OPEN return codesare documented in z/OS DFP VSAM MacroInstructions. Object Service Broker online

processing continues without the segmentbecoming available, or in the case of anObject Service Broker offline utility,processing is terminated.

Action: Standard IBM messages of the formIECxxxI accompany such failures. Contactyour Object Service Broker systemadministrator to review the probable causes.

S6BDB032EPAGESTORE INITIALIZATION FAILED

Source: File Task

Explanation: The Pagestore segment indicated inmessage S6BDB092I is not available to ObjectService Broker. Additional Object ServiceBroker or IBM messages have already beendisplayed to indicate the exact cause of error.Object Service Broker processing continuesunless the base segment has failed.

Action: Review the associated error messages todetermine recovery action. Contact yourSystem Programmer to correct theconfiguration or environmental problems.

S6BDB033EREDOLOG INITIALIZATION FAILED

Source: File Task

Explanation: Initialization of the Object ServiceBroker redolog failed. Additional ObjectService Broker or IBM messages have alreadybeen displayed to indicate the exact cause oferror. Object Service Broker terminatesabnormally.

Action: Review the associated error messages todetermine recovery action. Contact yourSystem Programmer to correct theconfiguration or environmental problems.


| 119

S6BDB034EGETMAIN FAILED FOR DBINITIALIZATION

Source: File Task

Explanation: Object Service Broker startupprocessing cannot obtain sufficient storage tocomplete Object Service Broker initialization.

Action: Contact the Object Service Broker SystemAdministrator to increase the region size.

S6BDB035IREDOLOG CI SIZE = ' _____'

Source: File Task

Explanation: Object Service Broker startupprocessing displays the control interval sizeas currently defined in the redolog.


S6BDB036EREDOLOG.PENDING IS NOTCATALOGUED

Source: File Task

Explanation: When trying to open thecontingency log (Redolog.pending), thesystem could not locate a catalog entry forthe data set. The Data Object Brokerinitialization fails with a U049 abend.

Action: Define and format the Redolog.Pendingdata set.

S6BDB037EREQUIRED SEGMENT FAILED TOINITIALIZE

Source: File Task

Explanation: Segment 0 or a segment which hasbeen defined in the DBGEN as Required bythe system cannot be initialized. ObjectService Broker terminates abnormally sincethe required meta-data is not available forObject Service Broker transaction processing.

NOTE: All segments previously online mustbe available after an abnormal termination.


S6BDB043EREDOLOG NOT PREFORMATTED

Source: File Task

Explanation: The redolog is normally formattedat installation time. If it is not formatted,Object Service Broker does not start up.


S6BDB044EGETMAIN FOR SMF SUBTYPE 13 RECORDBUFFER FAILED

Source: File Task

Explanation: During Data Object Brokerinitialization, Object Service Broker was notable to obtain the virtual storage needed forthe SMF subtype 13 record.

Action: Modify the REGION parameter in theData Object Broker's JCL to provide morevirtual storage. Restart the Data ObjectBroker.


120 |

S6BDB045ESEGMENT ID DOES NOT MATCH DBDGEN

Source: File Task

Explanation: During segment activation, thedata set as indicated in message S6BDB090Ior S6BKX002I does not contain the correctsegment ID as specified in the DBGEN.Object Service Broker startup continues, butdoes not activate this segment, or in the caseof an offline utility, processing is terminated.

Action: Contact your Object Service BrokerSystem Administrator. Invalid data mayhave been inadvertently loaded into thewrong segment by offline utilities.

S6BDB046EPAGESTORE HAS NOT BEENPREFORMATTED

Source: File Task

Explanation: The segment and data set aspreviously displayed (S6BDB092I,S6bDB090I) have not been properlyconfigured for Object Service Broker use.

Action: Review the Installation and Operationsmanual for Pagestore setup requirements.

S6BDB047EEXCP ERROR X'__' ON CONTINGENCY LOG(REDOLOG.PENDING)

Source: File Task

Explanation: An I/O recovery error occurredwhile the Data Object Broker was writingrecovery information to the contingency log.

Action: Investigate the reason for the I/O errorand, if necessary, move theREDOLOG.PENDING data set.

S6BDB048EPAGE ID DOES NOT MATCH DBGEN

Source: File Task

Explanation: During segment activation, thedata set as indicated in message S6BDB090Ior S6BKX002I does not contain the correctpage number as specified in the DBGEN atObject Service Broker startup.

Action: Contact your Object Service Brokersystem administrator. Invalid data may havebeen inadvertently loaded into the wrongpage by offline utilities.

S6BDB050ARESTORE OF PAGE SEGMENT= ___ NAME=________ DID NOT COMPLETE

Source: File Task

Explanation: During segment initialization,indicators were found within the Pagestoredata set that indicate that a restore wasstarted but failed to complete successfully.

Action: The segment will not be brought online.Try the segment restore again and then bringthe segment online.

S6BDB051AFORMAT OF PAGE SEGMENT= ___ NAME=________ DID NOT COMPLETE

Source: File Task

Explanation: The initialization of the segmentindicated in the name segment data setsshow the formatting of the data set startedbut never completes.

Action: Reformat the Pagestore data set andretry.


| 121

S6BDB052WERROR IN ABORT CLEANUP FREEINGPAGE

Source: File Task

Explanation: An Object Service Broker userrequested a free page, but aborted thetransaction before the page was used. Whenprocessing was aborted, the File taskvalidated the free page to ensure that theowner of the page and the user running thecurrent session are the same. This message isissued because the page owner and the userare not the same.


S6BDB053WVALIDATION ERROR FREEING LOCK

Source: File Task

Explanation: The File task received a request tofree a lock. During this process, the File taskensures that the page for which the lock isbeing released is owned by the same userwho is running the current session. Thismessage is issued because the page ownerand the user are not the same.


S6BDB058ISEGMENT ________ SET TO ________ MODE

Source: File Task

Explanation: The segment identified in themessage has been set to the mode shown inresponse to a request by the operator.


S6BDB063WSEGMENT ___:________ BUSY - SHUTDOWNDEFERRED (PENDING CHECKPOINT ___)

Source: File Task

Explanation: A shutdown of segmentnumber:name was requested, but thesegment is still active. The shutdown requestis deferred until the next checkpoint is taken.


S6BDB064WVSAM CLOSE ERROR ___DSN='________.________._______'

Source: File Task

Explanation: A VSAM error was encounteredwhile closing the data set indicated in themessage.

Action: Look for additional messages thatprovide information identifying the specificcause of the error, and take the appropriatecorrective action.

S6BDB065ESTORAGE NOT AVAILABLE FOR RESIDENTPAGE POOL

Source: File Task

Explanation: During Data Object BrokerInitialization, there was not enough storageavailable to construct the Resident Page Pool.

Action: Increase the amount of Virtual Storageavailable to the Data Object Broker.


122 |

S6BDB066WINSUFFICIENT STORAGE AVAILABLE FORRESIDENT PAGES

Source: File Task

Explanation: During Data Object BrokerInitialization, there is not enough storageavailable to construct the Resident Page Poolto the size specified in the RESIDENTPAGESparameter.

Action: The Data Object Broker attempts tocontinue initialization with a reducednumber of resident pages. The message"RESIDENT PAGE REQUESTED..." indicatesthe number of resident pages available to theData Object Broker. Increase the amount ofVirtual Storage available to the Data ObjectBroker.

S6BDB067IRESIDENT PAGES REQUESTED = _____,AVAILABLE = _____

Source: File Task

Explanation: The requested size of the ResidentPage Pool as requested via theRESIDENTPAGES initialization parameter,and the number of Resident Pages obtainedare displayed in this message.


S6BDB090IOPEN'________.________.________.________.________'

Source: File Task

Explanation: This message appears during DataObject Broker initialization. It identifies thedata set names of the database segments,journals, redolog, Statistics Log, and anyother control files that are active for thisObject Service Broker Data Object Broker.

These data set names were defined in anObject Service Broker DBGEN. They arestored in a VSAM data set, the Data ObjectBroker DBDLIB.

Action: No action is required. This message maybe followed by IEC161I 056-084 and IEC161I062-086 if the files were not closed normallywhen the previous Object Service Brokerexecution terminated.

S6BDB092IACTIVATING SEGMENT=___ NAME='________'

Source: File Task

Explanation: The indicated segment is beingactivated.


S6BDB093ISHUT DOWN SEGMENT=___ NAME='________'

Source: File Task

Explanation: The indicated segment is being shutdown.


S6BDB095AFREE SPACE SHORTAGE DETECTED FORSEGMENT=________ - ___% FULL

Source: File Task

Explanation: When obtaining a free page for thesegment, the Object Service Broker systemdetected that the space utilization thresholdfor the indicated segment has been exceeded.This message will be repeated for every


| 123

increment defined in the DBGEN entry forthe segment up to 100% unless implicit orexplicit corrective actions bring it below theminimum allowable threshold.

Action: It is recommended that you increase thenumber of free pages available either byclearing up or moving existing tables, or byincreasing the size of the data sets within thesegment.

S6BDB096IFREE SPACE SHORTAGE FORSEGMENT=________ RELIEVED

Source: File Task

Explanation: This message indicates that thespace utilization for the segment had earlierincreased beyond the warning threshold buthas now come back to below this threshold.



124 |

DC: IMS TM

S6BDC001EUNABLE TO LOAD 12345678ABCODE=X"12345678" REASONCODE=X"1234567..8"

Source: IMS TM

Explanation: This message is issued by theHDRDCDIT module. The Object ServiceBroker Execution Environment initializationmodule was unable to load the namedmodule for the reason indicated by thereason code (which is the return code in R15passed from the z/OS LOAD macro). ObjectService Broker Execution Environmentinitialization is terminated.

Action: Correct the problem if possible, orcontact TIBCO Support.

S6BDC005EATTACH OF SERVER TASK FAILED -INITIALIZATION TERMINATING

Source: IMS TM

Explanation: This message is issued by theHDRDCDIT module. The Object ServiceBroker EE initialization module was unableto attach the Object Service Broker gatewaytask; the initialization process wasterminated. (This message is usuallyaccompanied by other more specific errormessages.)

Action: Investigate and correct the problem, orcontact TIBCO Support for assistance.

S6BDC006IIMS TM INTERFACE INITIALIZATIONCOMPLETE

Source: IMS TM

Explanation: This message is issued by theHDRDCDIT module. The Object ServiceBroker Execution Environment interfaceinitialization is complete and is ready forprocessing.


S6BDC007EIMS TM INTERFACE INITIALIZATIONFAILED

Source: IMS TM

Explanation: This message is issued by theHDRDCDIT module. The Object ServiceBroker Execution Environment initializationmodule was unable to initialize the interface.This message is usually accompanied byother more specific error messages.



| 125

S6BDC008EIMS TM INTERFACE INITIALIZATIONFAILED; REMOTE NEE IS REQUIRED

Source: IMS TM

Explanation: This message is issued by theHDRDCDIT module. The Object ServiceBroker Execution Environment initializationmodule detected that the IMS MPR is tryingto connect directly to an Data Object Broker.

For now, only the remote Object ServiceBroker Execution Environment is supportedfor IMS MPR. Therefore, the IMS MPR mustconnect to an Object Service Broker NativeExecution Environment. The Object ServiceBroker remote Execution Environmentinitialization is terminated.

Action: To connect an IMS MPR ExecutionEnvironment to an Object Service BrokerNative Execution Environment, specifyREGIONTYPE=REMOTE in the HRNIN filefor the IMS MPR.

S6BDC011EUNABLE TO START SESSION;&PRODNAME ENVIRONMENT NOTAVAILABLE

Source: IMS TM

Explanation: This message is issued by theHDRDCIMS module. The Object ServiceBroker session cannot be started because theObject Service Broker gateway task was notinitialized.

Action: Initialize the Object Service Brokerenvironment and try again.

S6BDC012ESESSION INITIALIZATION FAILED (SMG)

Source: IMS TM

Explanation: This message is issued by theHDRDCIMS module. An Object ServiceBroker session cannot be initialized becauseof an internal Object Service Broker controlblock error.


S6BDC013ESESSION DENIED BY PHASE 1 USER EXIT

Source: IMS TM

Explanation: This message is issued by theHDRDCIMS module. Phase 1 user exitreturned with return code 4, which stops thesession from being started.

Action: Check with System Administrator forlegitimacy of the session request.

S6BDC014ESESSION DENIED BY PHASE 2 USER EXIT

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. Phase 2 user exitreturned with return code 4, which stops thesession from being started.

Action: Check with System Administrator forlegitimacy of the session request.


126 |

S6BDC016EUNABLE TO IDENTIFY TRANCODE

Source: IMS TM

Explanation: This message is issued by theHDRDCIMS module. The TRANCODEsupplied was invalid, it was either null ormore than 8 characters.

Action: Session was terminated. Retry with avalid TRANCODE, if possible, or contactTIBCO Support.

S6BDC017ENO SPA WITH CONVERSATIONAL TRAN

Source: IMS TM

Explanation: This message is issued by theHDRDCIMS module. The IMS TMTRANCODE was defined as a conversationaltransaction and yet the TRANCODE wasassociated with a non-conversationalprogram.

Action: The session was terminated. Correct theerror and retry, if possible, or contact TIBCOSupport.

S6BDC018EMESSAGE LENGTH ERROR

Source: IMS TM

Explanation: This message is issued by theHDRDCIMS module. The message lengthdid not add up to the required length. Thiscondition should not have occurred. Thiswas probably due to some internal systemerror.

Action: The session was terminated. Try again orcontact TIBCO Support.

S6BDC020EINITIALISATION ERROR, UNABLE TOCONTINUE

Source: IMS TM

Explanation: This message is issued by theHDRDCIMS module. The system was unableto obtain storage for internal control blocks.

Action: The session was terminated. Try again orcontact TIBCO Support.

S6BDC021EMULTI-DATA SEGMENTS NOTSUPPORTED

Source: IMS TM

Explanation: Multiple data segments are notsupported under the current release of ObjectService Broker.

Action: Change the application so that it does notuse multiple segments.

S6BDC022E"CHNG" ALTERNATE IOPCB ERROR,STATUS CODE = " "

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. An error wasencountered when issuing the changerequest to IMS modifiable alternate IOPCBfor program switching. The status code isreturned by IMS.

Action: Determine the cause of the error, ifpossible, or contact TIBCO Support forassistance.


| 127

S6BDC023E"ISRT" SPA ERROR, STATUS CODE = " "

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. An error wasencountered when issuing the insert SPArequest to IMS. The status code is returnedby IMS.

Action: Determine the cause of the error, ifpossible, or contact TIBCO Support.

S6BDC024E"ISRT" MESSAGE ERROR, STATUS CODE = ""

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. An error wasencountered when issuing the insert messagerequest to IMS. The status code is returnedby IMS.


S6BDC025ETRANSACTION "XXXXXXXX":RRRRRRRRRRRRRR

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. Immediate programswitch to the transaction XXXXXXXX wasunsuccessful; RRRRRRRRRRRRRR is thereason.

Action: The switch operation was terminated.Correct the error and re-run the program, ifpossible, or contact TIBCO Support.

S6BDC026E"XX" SEGMENT ERROR, STATUS CODE ="XX"

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. An error wasencountered when issuing the get segmentrequest to IMS. The operation and the statuscode returned by IMS are displayed in themessage.

Action: Determine the cause of the error, ifpossible, or contact TIBCO Support.

S6BDC031ISESSION ENDED

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. The Object ServiceBroker session is ended at the request of theuser.


S6BDC032ESESSION ABNORMALLY TERMINATED

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. The Object ServiceBroker session has terminated abnormally.This message is usually accompanied byother more specific error messages.



128 |

S6BDC033ESESSION TERMINATED; SUBTASK NOTATTACHED

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. A Object Service Brokersession cannot continue because the gatewaytask was not initialized.

Action: Initialize the Object Service Brokerenvironment and try again.

S6BDC034ESESSION TERMINATED; INVALIDCONTROL BLOCK POINTER

Source: IMS TM

Explanation: This message is issued by theS6BDCKRN module. A Object Service Brokersession cannot continue because of an invalidObject Service Broker internal control blockerror.


S6BDC041EUNABLE TO DELETE 12345678 REASONCODE=X"12345678"

Source: IMS TM

Explanation: This message is issued by theHDRDCDIT module. The Object ServiceBroker Execution Environment terminationmodule was unable to delete the namedmodule for the reason indicated by thereason code (which is the return code in R15passed from the z/OS DELETE macro). TheObject Service Broker ExecutionEnvironment termination continues.

Action: Determine the cause of the error ifpossible, or contact TIBCO Support.

S6BDC043IIMS TM INTERFACE TERMINATIONCOMPLETE

Source: IMS TM

Explanation: This message is issued by theHDRDCDIT module. The Object ServiceBroker Execution Environment interfacetermination is complete.


S6BDC044EIMS TM INTERFACE TERMINATIONFAILED

Source: IMS TM

Explanation: This message is issued by theHDRDCDIT module. The Object ServiceBroker Execution Environment interfacetermination failed. This message is usuallyaccompanied by other more specific errormessages.



| 129

DD: DB2 - DOB

S6BDD000I@DB2TABLES definition error:

Source: DB2 - DOB

Explanation: @DB2TABLES is definedincorrectly. This error occurred when youtried to access the specified table.


S6BDD001I@DB2TABLES entry not found for table

Source: DB2 - DOB

Explanation: The specified DB2 table is notcorrectly defined to Object Service Broker.

Action: Check the DB2 table definition.

S6BDD002I@DB2FIELDS definition error:

Source: DB2 - DOB

Explanation: @DB2FIELDS is defined incorrectly.This error occurred when you tried to accessthe specified table.


S6BDD003I@DB2FIELDS table not found for table

Source: DB2 - DOB

Explanation: The specified DB2 table is notcorrectly defined to Object Service Broker;@DB2FIELDS fields has no occurrences forthe table.


S6BDD004ICTABLE for DB2 data too large for table

Source: DB2 - DOB

Explanation: The DB2 table contains too manyfields.

Action: Reduce the number of fields in the DB2table definition or contact TIBCO Support.

S6BDD005INo fields defined for table

Source: DB2 - DOB

Explanation: The specified DB2 table does nothave any fields defined.

Action: Verify the DB2 table definition.

S6BDD006ITDS CTABLE missing DTABLE field

Source: DB2 - DOB

Explanation: The DB2 table is definedincorrectly. An entry in the Object ServiceBroker table FIELDS is missing.



130 |

S6BDD007I@DB2FIELDS index page found for table

Source: DB2 - DOB

Explanation: A large number of DB2 fields aredefined for the table, causing a data pagesplit in @DB2FIELDS.



| 131

DM: CA Datacom server, utilities

S6BDM001EDenied access to table %

Source: CA Datacom server, utilities

Explanation: Access to the table has been deniedby security

Action: Acquire the adequate access authorityfrom your security administrator.

S6BDM002ITable % successfully generated


Explanation: The named table has been createdbased on the CA-Datacom's DataDictionary's definition of the data in thetable.

Action: Review the defined table for compliancewith any local standards.

S6BDM003EUnable to generate a unique DAT table namefrom CA-Datacom definition "%"


Explanation: The table definition generation isunable to create a unique MetaStor tablename to reflect the CA-Datacom's definitionof the table.

Action: Use the normal Table Definer utility tocreate a unique MetaStor table definition ofthis CA-Datacom table.

S6BDM004IRedefines not supported for DAT tabledefinition: CA-Datacom table "%"


Explanation: Only one definition of a portion of arecord is allowed. Table definition generationwill only use the first definition found.

Action: Create a different MetaStor tabledefinition for each of the CA-Datacom tableredefinitions.

S6BDM005EUnable to convert syntax for field "%"


Explanation: The CA-Datacom field's data typedoes not have a corresponding MetaStorfield syntax or conversion.

Action: Use the RD syntax to access the field inits raw form.

S6BDM006EUnable to generate unique DAT field namefrom CA-Datacom field "%"


Explanation: The named field name is notunique enough for the table generationfacility to create the required uniqueMetaStor field name.

Action: Use the normal Table Definer utility tocreate the MetaStor definition of this CA-Datacom table, assigning your own uniquefield names.


132 |

S6BDM007IPlease extract the CA-Datacom metadata for %


Explanation: The named CA-Datacom tabledefinition was not found in the extract tables.

Action: Run an extract of the CA-Datacom DataDictionary to get the metadata for this table,or correct the spelling of this table name.

S6BDM008IPlease use a security-level-1 OSB userid togenerate CA-Datacom tables


Explanation: You should use a security-level-1OSB userid to create definitions. Otherwise,other users will not be able to access thegenerated table definition.

Action: Switch to a userid with level-onesecurity. If the table needs a higher securitylevel, assign it after the definition has beengenerated, or use the standard Table Definerutility to create the definition using theuserid with a security level higher than one.

S6BDM009ICA-Datacom extract submitted; please checkoutput of job


Explanation: The CA-Datacom Data Dictionaryextract job has been submitted.

Action: Check the output of the job forcorrectness. The JCL submitted must becustomized before first use.

S6BDM011ITable not generated; use a valid serverid


Explanation: A valid SERVERID must beprovided before the CA-Datacom definitioncan be generated into a MetaStor tabledefinition.

Action: Provide the SERVERID that this CA-Datacom table will be accessed with.

S6BDM012EData conversion error in table "%", "%"


Explanation: Gives the table name and fieldname where the data could not be convertedusing the MetaStor and CA-Datacomdefinitions provided.

Action: Change the definition of this table toreflect the actual data, or correct the data inthe invalid row occurrence.

S6BDM013ITable not generated; Serverid cannot exceed 8characters


Explanation: The maximum length for aSERVERID is 8 characters.

Action: Provide a SERVERID value of 8characters or less.


| 133

S6BDM015EURT not found, or %/% not in the URT


Explanation: The URT associated with the tablebeing access was found neither in theHRNEXTR library nor in the STEPLIBconcatenation, or the required CA Datacomtable was not found in the URT.

Action: Prepare a CA Datacom URT withDBNTRY entry point and place it the loadlibrary available to the DAT server throughthe STEPLIB or HRNEXTR DD statement(see the manual for details).

S6BDM016EUnexpected RC %-% from CA-Datacom whileissuing command(%) against table(%),DBID(%)


Explanation: The CA-Datacom Gatewayreceived an unexpected return code fromCA-Datacom while executing the namedcommand against table / DBID, as indicated.

Action: Look up the RC returned by the Gatewayin the CA Datacom/DB Message ReferenceGuide to determine the cause of failure.

S6BDM017EUnexpected RC %-% from CA-Datacom whileissuing command(%) against URT(%)


Explanation: The requested row is not found.


S6BDM018IEnter a CA-Datacom table name, ALL or partial*


Explanation: Enter the data to indicate the CA-Datacom dictionary information to beextracted.

Action: Enter the CA-Datacom table name, ALLor partial* to indicate the eligible tables.

S6BDM019IThe CA-Datacom metadata batch extract onlyworks from TSO/MVS


Explanation: This facility (CA-DatacomDictionary extract) only works wheninitiated from the TSO environment.

Action: Exit the Execution Environment you arecurrently using, and use a TSO ExecutionEnvironment to initiate the CA-DatacomDictionary extract Utility.

S6BDM020EDBID % (table %) does not have an entry in@DATACOM_URTS


Explanation: The DBID for the table specifieddoes not have a URT associated with it. Thelist of URTs loaded at CA-Datacom serverstartup time can be found in@DATACOM_URTS(serverid).

Action: Add the appropriate URT to the@DATACOM_URTS table and retry. Notethat the CA-Datacom server does NOT haveto be recycled.


134 |

S6BDM021IURT % is closed. Try later


Explanation: The URT with the specified namehas been closed by an operator request and isunavailable until specifically opened.

Action: Wait for the URT to be opened via aOPENURT=name command.

S6BDM023I% % URT name % closed


Explanation: The specified URT name has beenclosed via a CLOUSEURT command

Action: None.

S6BDM024I% % URT name % marked available


Explanation: The specified URT has beenmarked available by an OPENURTcommand. The URT will not be opened untilthe first data access.

Action: None.

S6BDM025E% % URT name % specified in CLOSEURT orOPENURT not found


Explanation: The URT name specified by aCLOSEURT or OPENURT was not found inthe server.

Action: Look in the CA-Datacom Gateway joblog for the list of URTs loaded, and specify acorrect name.

S6BDM026I% % URT name % successfully loaded


Explanation: The named URT has beensuccessfully loaded

Action: None.

S6BDM027E% % Load of URT name % failed


Explanation: The named URT could not beloaded.

Action: The URTs to load reside in a LOADlibrary described in the STEPLIB orHRNEXTR DD statement of the DAT serverstartup JCL.

S6BDM028E% % Server initialization FAILED, check themessage log for possible causes


Explanation: The server failed to complete itsinitialization process.

Action: Possible causes are indicated in the logabove this message.

S6BDM030I% % CA-Datacom Gateway Terminated


Explanation: Information message indicatingthat the CA-Datacom server has completednormal termination.

Action: None.


| 135

S6BDM032E% % Unknown command %


Explanation: The SERVERCOMMAND enteredin the Data Object Broker is unknown.

Action: Enter a valid command.

S6BDM033I% % Fail Safe query


Explanation: Message indicating that an indoubttransaction is outstanding for this server.This request queries the Fail Safe transactiondatabase to determine if the indoubttransaction had completed.

Action: None.

S6BDM034E% % No URT modules found, serverterminating


Explanation: The server could not find any URTmodules to load.

Action: A URT named after the server ID ornamed S6BDATDB could not be found. TheURT modules must reside in the load libraryspecified either in the STEPLIB or HRNEXTRDD statement.

S6BDM035I@SERVERDEBUG(%) settings: %


Explanation: Displays the values specified in the@SERVERDEBUG table for this gateway

Action: None

S6BDM036ESecurity error for user % : SAF rc=%, RACFrc=%.


Explanation: Unsuccessful verification of the(USERID, PASSWORD) pair by OSB DATServer when running withSECURITYLEVEL=1.

Action: Check the USERID and PASSWORD thatyour application passes to CA Datacom .

S6BDM038ECA-Datacom user security credentialsunavailable or malformed.


Explanation: The server runs withSECURUTYLEVEL=1. The application haspassed no security credentials or thosepassed cannot be used.

Action: Make sure the application passes the usersecurity credentials (USERID, PASSWORD)to the DAT server by invoking theSET_DAT_SEC rule.

S6BDM039EThe WHERE clause against table % is too longfor the DAT server to process.



136 |

DP: Execution Environment print

S6BDP000E- PARM=('userid,spoolid,jobname,jobnumber')

Source: Execution Environment print

Explanation: This message is displayed at thesystem console when a CICS-submittedprinting job fails. This message is precededby S6BDP001E message. This message text isthe job parameter of the submitted job. Theparameter fields are:

• userid is the CICS operator user ID

• spoolid is a unique ID generated byspooling subsystem

• jobname is the CICS job name thatsubmitted this printing job

• jobnumber is the CICS job number thatsubmitted this job

Action: Take appropriate action as described inmessage S6BDP0001E.

S6BDP001EIEFSSREQ ERROR - R15=X'XX'SSOBRETN=X'XX'


Explanation: This message is issued by theoffline print utility S6BDRPRT. The error wasencountered when trying to obtain theDSNAME for the SYSOUT data set. TheSYSOUT data set is not printed or deleted.Refer to the following codes to determine thecause for the failure (the values for R15 aredetermined in the z/OS macro IEFSSOBHand for SSOBRETN in macro IEFSSSO):

1. R15

• SSRTOK -- 0: A successful completion.The request was sent to the JESsubsystem.

• SSRTNSUP -- 4: The subsystem doesnot support this function.

• SSRTNTUP -- 8: The subsystem exists,but it is not up.

• SSRTNOSS -- 12: The subsystem doesnot exist.

• SSRTDIST -- 16: The function did notcomplete - disastrous error.

• SSRTLERR -- 20: Logical error (badSSOB format).

2. SSOBRETN

• SSSORTOK -- 0: Everything is OK.

• SSSOEODS -- 4: No more data sets toselect. This error can be caused byspecification of a HELD sysout classfor the EE parameterPRINTSPOOLCLASS=. This conditionmay also be caused if a JES2 operatorattempted to purge the output of theCICS or native EE job and subsequentprint requests were made.

• SSSONJOB -- 8: Job not found.

• SSSOINVA -- 12: Invalid searcharguments.

• SSSOUNAV -- 16: Unable to processnow.

• SSSODUPJ -- 20: Duplicate jobnames.

• SSSOINVJ -- 24: Invalidjobname/jobid combination.

• SSSOIDST -- 28: Invalid destinationspecified.


| 137

• SSSOAUTH -- 32: Authorizationfailed.

• SSSOTKNM -- 32: Token map failed.

Action: The program is terminated. Take actionsappropriate to the return codes. If assistanceis required, contact TIBCO Support.

S6BDP002EALLOCATE FAILED FOR JESDS='XXXXXX',R15=X'XX' RBERROR=X'XXXX'RBINFO=X'XXXX'


Explanation: This message is issued by theoffline print utility S6BDRPRT. The error isencountered during dynamic allocation ofthe SYSOUT data set. JESDS identifies thedata set being allocated. The return code, andthe error and information codes, are alsoincluded in the message. Refer to the z/OSApplication Development Guide:Authorized Assembler Language Programsmanual for further information regarding themeaning of the RBERROR and RBINFOcodes. The sysout data set is not to be printedor deleted.

Action: The program is terminated. Use thereturn code, and the error and informationcodes, to determine the problem. If you needhelp, contact TIBCO Support.

S6BDP003EOPEN ERROR FOR JESDS=


Explanation: This message is issued by theoffline utility S6BDRPRT. The error isencountered when trying to open theSYSOUT data set. JESDS identifies the nameof the data set being opened. The SYSOUTdata set is not printed or deleted.

Action: The program is terminated. Determinethe cause of the error. Refer to the z/OSSystem Messages manual for furtherinstructions. If you need assistance, contactTIBCO Support.

S6BDP004EUNALLOC FAILED FOR JESDS='XXXXXX',R15=X'XX' RBERROR=X'XXXX'RBINFO=X'XXXX'


Explanation: This message is issued by theoffline utility S6BDRPRT. The error isencountered during dynamic unallocation ofthe SYSOUT data set. JESDS identifies thename of the data set being unallocated. Thereturn code, and the error and informationcodes, are also included in the message. Referto the z/OS Application DevelopmentGuide: Authorized Assembler LanguagePrograms manual for further informationregarding the meaning of the RBERROR andRBINFO codes. The SYSOUT data set is notprinted or deleted.

Action: This program is terminated. Use thereturn code, and the error and informationcodes, to determine the problem. If you needassistance, contact TIBCO Support.


138 |

DR: Execution Environment

S6BDR001EERROR=0000 ABCDEFGH.ABCDEFGH+12345VERSION=00/00/00 00.00 V0.00.000

Source: Execution Environment

Explanation: This message is issued by theHDRSBLMC module. This message is issuedat the time of an abend if the ESTAE flag is setand if the abend was intentionally generatedby the $ABEND macro.

• ERROR displays the abend reason codereferencing the internal error messagestable in the HDRSBLMC module.

• ABCDEFGH.ABCDEFGH+00000 points tothe abend instruction offset from the activemodule CSECT beginning.

• VERSION displays the abend CSECT date,time and version identification in thatorder.


S6BDR002EERROR=E000 ABCDEFGH.ABCDEFGH+12345VERSION=00/00/00 00.00 V0.00.000


Explanation: This message is issued by theHDRSBLMC module at the time of an abendif the ESTAE flag is set and if the abend wasunintentional.

• ERROR displays the abend completioncode.

• ABCDEFGH.ABCDEFGH+00000 points tothe abend instruction offset from the activemodule csect beginning.

• VERSION displays the abend csect date,time and version identification in thatorder.


S6BDR003ETIBCO Object Service Broker REQUIRESMVS/XA FOR THIS VERSION


Explanation: You must upgrade your system toMVS/XA to use this version of Object ServiceBroker.


S6BDR004WADDRESS SPACE NOT APF AUTHORIZED


Explanation: This warning message is issuedwhen the Native Execution Environmentinitialization module detects that it is notinvoked as APF authorized. Without APFauthorization, Object Service Broker cannotuse privileged Operating System facilitiessuch as Cross Memory Services.

The reason could be one of the following:

• The Object Service Broker loadlib is notAPF authorized

• One of the loadlibs concatenated to theObject Service Broker loadlib for the//JOBLIB or //STEPLIB DD is not APFauthorized


| 139

• Module S6BDR000 is not linked with a"SETCODE AC(1)" statement

Action: Do one of the following, in this order:

1. Identify and correct the cause of theproblem and retry

2. Install the Object Service Broker ExecutionEnvironment SVC routine to enable APFauthorization

S6BDR005E******** OF SERVER TASK FAILED


Explanation: This message is issued by theS6BDR000 module. The ExecutionEnvironment initialization/terminationroutine was unable to either attach or detachthe TIBCO(r) Object Service Broker gatewaytask; the initialization or termination processwas terminated. This message is usuallyaccompanied by other more specific errormessages.


S6BDR006EEXECUTION ENVIRONMENT STARTUPFAILED


Explanation: This message is issued by theS6BDR000 module. The ExecutionEnvironment initialization routine is unableto initialize the interface. This message isusually accompanied by other more specificerror messages.


S6BDR007EUnknown or no gateway specified


Explanation: The specified name given is not avalid gateway, or no gateway was specified.

Action: Specify a valid gateway.

S6BDR008EExecution Environment subtask abended,R15=X'xxxxxxxx'


Explanation: This message is issued by theHDRSBSVA module. An attempt to attachthe subtask failed. This message is usuallypreceded by other error messages providingmore information for the failure. In themessage, xxxxxxxx is the abend code.

Action: Determine the cause of the error orcontact TIBCO Support for assistance.

S6BDR009EShared memory error: %


Explanation: The specified error occurred whileprocessing the osee shared memory area.

Action: If messages that precede this message donot provide sufficient information todiagnose the cause of this failure, contactTIBCO Support.


140 |

S6BDR010EEE MAIN TASK TCB ABENDEDPROCESSING ................................_CPE FNC.UID= .........


Explanation: The Execution Environment maintask abended. If the abend occurred duringthe processing of a CPE function, the name ofthe function appears in the message. Ifavailable, the userid is also in the message.


S6BDR011ISUBTASK ........ WAS ATTACHED.


Explanation: The Execution Environment hasattached the subtask named in the message.


S6BDR012IEE subtask ........ was terminated.


Explanation: The Execution Environment hasdropped the subtask named in the message.The action was due to an abend or initiatedfor refreshing purposes.


S6BDR013ENEE COULD NOT RESTART THE RULE-BASED SERVER.


Explanation: The Execution Environmentunsuccessfully tried to restart the abendedrule-based gateway/server.


S6BDR014EEE main task TCB has been terminatedprematurely due to the unrecoverable error


Explanation: The Execution Environment maintask suffered an abend and is unable torecover due to one of the following reasons:1) an abend occurred before the recoveryroutine was set up. 2) an abend occurred inthe retry routine. 3) the number of abendsexceeded the limit set.

Action: The recovery routine would percolate theabend and the Execution Environmentterminated.

S6BDR015IEE subtask xxxxxxxx is recovering after the userabend Uyyyy at zzzzzzzz


Explanation: To explain the following actions,such as a subtask recycle, an externalgateway recycle, etc., xxxxxxxx names thesubtask that has experienced the user abendyyyy while running module called zzzzzzzz.

Action: Take no action unless the situationcaused other problems, in which case contactTIBCO Support.

S6BDR016EError occurred while parsing parameter: '%'


Explanation: The specified error occurred whileparsing the startup parameters.

Action: Correct the syntax of the startupparameters.


| 141

S6BDR017EPrinter operation '%' failed for printer %


Explanation: The specified operation failed forthe specified printer.

Action: Make sure the printer is correctlyinstalled on your network and retry yourprinting operation. If it continues to fail,contact your system administrator.

S6BDR018EDevice context operation '%' failed


Explanation: The specified operation failed on aMicrosoft Device context.


S6BDR019EFailed to access font '%'


Explanation: An attempt to access the specifiedfont for printing failed.


S6BDR020IEXECUTION ENVIRONMENT IS NOTATTACHED


Explanation: This message is issued by theS6BCSOPS module. The ExecutionEnvironment is not attached.


S6BDR021IEXECUTION ENVIRONMENT ISATTACHED - ........


Explanation: This message is issued by theS6BCSOPS module. The ExecutionEnvironment is attached and ready to acceptlogons.


S6BDR022IEXECUTION ENVIRONMENT IS ALREADYATTACHED


Explanation: This message is issued byS6BCSRUN module. A HINT (interfaceinitialization) transaction was issued toactivate the TIBCO(r) Object Service BrokerCICS interface, but the ExecutionEnvironment task has already been attachedand the interface is ready to accept logons.


S6BDR023EFailed to initialize NLS


Explanation: An attempt to initialize theNational Language Support tables failed.

Action: Make sure the value specified for theCHARSET parameter to the osee issupported on your system.


142 |

S6BDR024EFirst rule failed


Explanation: The first rule for a given usersession failed.

Action: Previous error messages written to thelog should explain the reason for the failure.

S6BDR025EError occurred while spawning %


Explanation: The attempt to spawn a newprocess using the specified binary failed.


S6BDR026EFunction undefined for argument value


Explanation: A programming error has occurred.


S6BDR027EThread operation '%' failed


Explanation: The specified thread action failed.

Action: Check the operating system errornumber provided with the message. Itshould indicate the reason for the failure. If itdoes not, contact TIBCO Support.

S6BDR028EConversion of '%' failed for parameter %


Explanation: Conversion of the specified stringvalue to a value that could be stored in thespecified parameter failed.

Action: If the value originates from user input,check the type of the parameter and correctthe value. Otherwise, contact TIBCOSupport.

S6BDR029EUnable to determine computer name


Explanation: At osee startup, an attempt is madeto determine the name of the computer onwhich the process is executing.


S6BDR030ETDS=........ MDL=........ OPENPORT FAILED,SERVER TASK IS NOW DORMANT


Explanation: An attempt by the ExecutionEnvironment to establish communicationswith the Data Object Broker has failed. Thevalue for TDS identifies the Data ObjectBroker and the value for MDL is the VTAMAPPLID supplied by the user.


1. Ensure that the Data Object Broker isactive.

2. Ensure that the TDS parameter specifiesthe correct ID for the Data Object Broker.

3. If unable to determine the problem, contact TIBCO Support.


| 143

S6BDR031IENCRYPTION EXIT LOAD FAILED DUE TOMISSING SVC


Explanation: The Object Service Broker SVC ismandatory for the use of the securityencryption exit.

Action: Refer to earlier messages as to why theSVC is not present. Correct the reason, andrestart your Execution Environment for theexit to be enabled.

S6BDR032IENCRYPTION EXIT LOAD FAILED DUE TOUNAUTHORIZED USER EXIT


Explanation: The customer-installableencryption exit is not authorized, or has beenloaded from an unauthorized library.

Action: The customer exit must be link editedwith an authorized code of 1 (AC(1)). It mustalso reside in an APF authorized library, andall libraries that may be concatenated withthis library must also be APF authorized.

S6BDR033IENCRYPTION EXIT LOAD FAILED DUE TOMISSING LOAD MODULE


Explanation: The customer encryption exit(HDRSCXIT) could not be found in theSTEPLIB or HRNLIB data sets.

Action: Ensure that you link the HDRSCXIT loadmodule into the proper library.

S6BDR034EBuffer overflow occurred while writing to afixed length buffer




S6BDR035EAttempt to create a temporary file name failed


Explanation: An attempt to create a temporaryfile name failed.

Action: Check the operating system errornumber provided with the message. Itshould indicate the reason for the failure. If itdoes not, contact TIBCO Support.

S6BDR036EAn access was made on an unregistered session




S6BDR037EError of type '%' occurred while performing adata conversion


Explanation: An attempt to convert data fromone semantic/syntax type to another failedfor the specified reason. The reason is one ofthe following:

• DATAERR - The input data does notconform to the restrictions placed on it bythe input semantic/syntax.


144 |

• OVERFLOW - The data is too large for thesupported syntax.

• CONVERR - An unsupported conversionwas attempted.

• PARMERR - One or more of theparameters to a conversion routine wasinvalid.

• TRUNCATION - The data was truncatedas a result of the conversion to the targetsyntax.

• SYSTEMERR - A system error occurredduring the conversion.

Action: Examine the online logs to locate thesource of the error. If the reason specified isSYSTEMERR, contact TIBCO Support. If thedata originates from user input, provide theuser with the appropriate diagnosticmessages and re-prompt for input.Otherwise, correct either the data source orthe application.

S6BDR038EUnexpected exception was caught


Explanation: An unexpected internal exceptionoccurred.


S6BDR039EConversion of '%' failed for parameter %


Explanation: Conversion of the specified integralvalue to a value that could be stored in thespecified parameter failed.

Action: If the value originates from user input,check the type of the parameter and correctthe value. Otherwise, contact TIBCOSupport.

S6BDR040ECall was made to dummy member function




S6BDR041EEE abended due to exception thrown at %:%


Explanation: An osee process abended due to aninternal exception that occurred at thespecified line in the specified source file ofthe product.



| 145

S6BDR042EEE abended


Explanation: An osee process abended.


S6BDR043ESession Abended


Explanation: A user session abended.


S6BDR044ETransaction Stack Abended


Explanation: A transaction stack abended.


S6BDR045ETransaction Abended


Explanation: A transaction abended.


S6BDR046EFailed to initialize transaction stack


Explanation: The osee failed to initialize atransaction stack.


S6BDR047EFailed to activate session start transaction


Explanation: During session startup, atransaction is created for access to startupinformation that is stored in the MetaStor.The attempt to activate this transactionfailed.


S6BDR048EFailed to activate session terminationtransaction


Explanation: During session termination, atransaction is created for the logoff rule. Theattempt to activate this transaction failed.



146 |

S6BDR049EFailed to activate transaction for the first rule


Explanation: A transaction is created for the firstrule that is run by the session. The attempt toactivate this transaction failed.


S6BDR050EError occurred while setting the security group


Explanation: An attempt to change the user'ssecurity group failed.

Action: Previous log messages should providemore information as to the reason for thefailure. Make sure the user belongs to thespecified security group.

S6BDR051ECross Memory ABTERM detected, ASID=%


Explanation: The Object Service Broker ESTAErecovery routine detected a problem thatoccurred while in cross-memory mode. TheASID indicated was the one where the erroroccurred. This message provides additionalinformation to other error messages for thesituation.

Action: None.

S6BDR052EConnection to Data Object Broker has been lost;EE interface re-initialization required


Explanation: This message is issued by theHDRSBEXR module. It was found that theData Object Broker connected to this ObjectService Broker Execution Environment hasbeen shutdown and restarted, and therefore,the Execution Environment is out ofsynchronization with the restarted DataObject Broker.

Action: The Object Service Broker ExecutionEnvironment will have to be re-initialized tore-establish the link.

S6BDR053IEE SVC nnn(xx) validated, Version: ................Level: .. ......


Explanation: The Object Service Broker SVCroutine has been verified to be correct andcompatible with the rest of the Object ServiceBroker EE system modules. The version andcompatibility level are displayed.


S6BDR054ICROSS-MEMORY COMMUNICATIONENABLED, ID=........


Explanation: This message is issued by theS6BDRTMR module. Communication hasbeen established with the Object ServiceBroker Data Object Broker utilizing CrossMemory Services with the MDL described bythe message.



| 147

S6BDR055EFailed to connect to DOB '%'


Explanation: An osee process is unable toconnect to the specified Data Object Broker.

Action: The preceding log messages shouldexplain the reason for the failure. Make surethe Data Object Broker in question isrunning.

S6BDR056ECOMMAREA TOO SMALL FOROCCURRENCE


Explanation: This message is issued by theBLTPASSD module. Object Service Brokerhas attempted to place a requestedoccurrence in the user created COMMAREA.The space remaining in this COMMAREAwas too small to contain the occurrence.


• Increase the size of the COMMAREApassed to Object Service Broker.

• Reduce the size of the occurrence to bewritten to the COMMAREA.

• If the user is writing multiple occurrencesto the COMMAREA, reduce the number.

S6BDR057ETABLE OCCURRENCE NOT FOUND


Explanation: This message is issued by theBLTPASSD module. Object Service Brokercannot find the occurrence that was chosen tobe written to the user suppliedCOMMAREA.

Action: Ensure that the occurrence exists, or thatthe occurrence is placed in the table bufferbefore $SETCOMMAREA is called.

S6BDR058ETABLE NOT FOUND


Explanation: This message is issued by theBLTPASSD module. The table specified in$SETCOMMAREA cannot be found.

Action: Ensure that the requested table exists.

S6BDR059ESVC routine(.. ......) SVA module(.. ......)


Explanation: This message is issued by theHDRSBSVA module. It is preceded by eitherS6BDR060E or S6BDR062E. It provides theMajor and Minor compatibility-levelnumbers for the SVC routine and theHDRSBSVA module.

Action: Correct the incompatibility situation orcontact TIBCO Support for assistance.


148 |

S6BDR060EShared ENQ on specified SVC no. nnn(xx)failed verification: xxxxxxxxxxxxxxxxxxxx


Explanation: This message is issued by theHDRSBSVA module when a shared ENQwas unsuccessful on the Object ServiceBroker SVC. In the message:

• nnn is the SVC number in decimal

• xx is the SVC number in hexadecimal

• xxxxxxxxxxxxxxxxxxxxxxxxxxxx is thereason for the failure

Possible reasons are as follows:

• The SVC number is not specified

• The SVC number is invalid (range: 255-200)

• The SVC routine is not available

• The SVC routine is not installed

• The SVC routine is incompatible

• SVC is not type 3 or 4

Action: Correct the error and retry or contactTIBCO Support for assistance.

S6BDR061ELoad failed for "xxxxxxxx"ABCODE=X'xxxxxxxx' ReasonCode=X'xxxxxxxx'


Explanation: This message is issued by theHDRSBSVA module. Loading of theinstallation default module failed. Themodule name, abend code, and reason codeare documented in the appropriate IBMmanual, under the LOAD macro. The ObjectService Broker Execution Environment will

therefore be running in a non-authorizeddegraded mode. Full Object Service BrokerExecution Environment functionality maynot be provided.

Action: This message is followed by messageS6BDR063W.

S6BDR062E"mmmmmmmm" specified SVC numbernnn(xx) failed verification:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


Explanation: This message is issued by theHDRSBSVA module. In the message:

• mmmmmmmm is the name of theinstallation defaults module

• nnn is the SVC number in decimal

• xx is the SVC number in hexadecimal

• xxxxxxxxxxxxxxxxxxxxxxxxxxxx is thereason for the failure

Possible reasons are as follows:

• The SVC number is not specified

• The SVC number is invalid (range: 200-255)

• The SVC routine is unavailable

• The SVC routine is not installed

• The SVC routine is incompatible

• The SVC is not type 3 or 4

Action: This message is followed by messageS6BDR063W.


| 149

S6BDR063WExecution Environment will run unauthorized


Explanation: This message is issued by theHDRSBSVA module and may be preceded bymessage S6BDR061E or S6BDR062E. TheExecution Environment will rununauthorized for the reason stated in thepreceding message. If no reason is stated, theObject Service Broker SVC was locatedproperly but the library from whichTIBCO(r) Object Service Broker was loadedwas unauthorized.

Action: To ensure that TIBCO(r) Object ServiceBroker always initializes in an authorizedstate, use one of the three methods describedin the Installation and Operations manual.

S6BDR064IINITIALIZATION COMPLETE FOR SERVERCLASS ........ (ATTACHED TASK=...)


Explanation: This message is issued by theS6BDRTMR module. Initialization of thespecified gateway/server class has beensuccessful.


S6BDR065ITERMINATION COMPLETE FOR SERVERCLASS ........


Explanation: This message is issued by theS6BDRTMR module. Termination of thespecified gateway/server class has beensuccessful.


S6BDR066ECOMMUNICATION CONNECTION LOST,ID=........


Explanation: This message is issued by theS6BDRTMR module. Execution Environmentcommunication with the Data Object Brokerhas been lost.

Action: Check that the Data Object Broker is stillactive, and that VTAM is still functioning.

S6BDR067ECOMMUNICATION PORT FAILURE, ID=.......


Explanation: This message is issued by theS6BDRTMR module. The user's ExecutionEnvironment connection to the Data ObjectBroker has been lost.

Action: Check that the Data Object Broker is stillactive, and whether the user session wascanceled.

S6BDR068EERROR RECOVERY FAILED FOR TASKCLASS ........, USER ........


Explanation: This message is issued by theHDRSBEXR module. The attempt to recoverfrom an error situation has failed for the Taskclass (and the user if the Task was processinga user). The Task was terminated with anObject Service Broker snap dump.



150 |

S6BDR069ECPE CONNECT PROCESSING FAILED FORXXXXXXXX, RC=XX. CPE HEX DUMPFOLLOWS


Explanation: This message indicates that anattempt to connect with the ExecutionEnvironment has failed for the named VTAMapplication identifier. The connectionprocessing element is dumped inhexadecimal format to allow diagnosis of theproblem.

Action: Retain the Execution Environment JESjoblog and forward to Object Service BrokerTIBCO Support for analysis.

S6BDR070EOPERATOR CONNECTION LOST,EXECUTION ENVIRONMENT SHUTDOWNSCHEDULED


Explanation: The operator connection with theData Object Broker has been lost. TheExecution Environment cannot continuewithout this connection. An automaticshutdown of the Execution Environment isscheduled.

Action: The likely cause of this message is theData Object Broker to which the ExecutionEnvironment is connected has beenshutdown either normally or abnormally.Review the Data Object Broker's JES joblogand determine the reason for its termination.

S6BDR071EEUT CONNECTION FAILED, ID = ????????


Explanation: This message is issued when theExecution Environment is unable to requite aconnection request from either an end userterminal or a remote program.

Action: Check communication parameters.

S6BDR072I- SESSION CANCELLED


Explanation: The session has been canceled.There can be any number of reasons to cancela session: the Data Object Broker is beingrecycled, locks held by one session preventother sessions from proceeding, the session isin an infinite loop, etc.

Action: This is an information message. The usershould consult with the Object ServiceBroker System Administrator if sessioncancellation was not only unexpected butdisruptive.

S6BDR073E%


Explanation: This message contains ahexadecimal dump of the connectionprocessing element that could not besuccessfully processed. Message S6BDR069Eindicates the end user attempting connectionand the reason for the failure.

Action: Keep the Execution Environment JESjoblog for TIBCO Support.


| 151

S6BDR074EFailed to initialize task parameters


Explanation: An attempt to initialize the oseestartup parameters with values stored in theData Object Broker failed.

Action: Previous log messages should providemore information as to the reason for thefailure. Make sure the version of the DataObject Broker is compatible with the versionof the osee.

S6BDR075EFailure occurred while initializing the sessionparameters


Explanation: An attempt to initialize one or moreof the session parameters failed.

Action: Previous log messages should providemore information as to the reason for thefailure.

S6BDR076EFailed to initialize the screen server


Explanation: An attempt to initialize the ActiveXAdapter server in an osee failed.

Action: Previous log messages should providemore information as to the reason for thefailure.

S6BDR077I- NOT AUTHORIZED TO ISSUE SMFRECORDS


Explanation: The address space is not sufficientlyauthorized to issue SMF records.

Action: This is an information message. TheExecution Environment can execute fromeither an authorized or unauthorized loadlibrary. Without APF authorization, SMFrecords cannot be issued.

S6BDR078ICOMMAND "%" ISSUED


Explanation: This message is issued by theHDRSBOCP module. This message is anecho to the command entered to serve as anaudit trail.


S6BDR079EEXECUTION ENVIRONMENT REQUIRESAUTHORIZATION FOR THIS COMMAND.COMMAND FAILED.


Explanation: This message is issued by theHDRSBOCP module. The command enteredrequires APF authorization for the ExecutionEnvironment.

Action: The command was not processed. Referto the Installation and Operations manual forinformation on Authorized Libraryrequirements.


152 |

S6BDR080IEXECUTION ENVIRONMENT SHUTDOWNALREADY IN PROGRESS


Explanation: Execution Environment shutdownis in progress.

Action: The shutdown request is ignored.

S6BDR081WUSER ........ NOT CURRENTLY LOGGED ONTO THE EXECUTION ENVIRONMENT.


Explanation: This message is issued by theHDRSBOCP module. The user identified inthe CANCELUSER command was notcurrently logged on to TIBCO(r) ObjectService Broker via this ExecutionEnvironment, and the request could not becompleted.

Action: Check the userid entered with theCANCELUSER command, correct, andreenter the command.

S6BDR082ICANCEL OF USER ........ HAS BEENSCHEDULED


Explanation: This message is issued by theHDRSBOCP module. The user sessionidentified was scheduled to be canceled inresponse to the CANCELUSER commandentered.


S6BDR083IEXECUTION ENVIRONMENT SHUTDOWNHAS BEEN SCHEDULED


Explanation: This message is issued by theHDRSBOCP module. A shutdown requesthas been entered, and this is theacknowledgement that the shutdownsequence has been initiated.


S6BDR084ECOMMAND SPECIFIED IS NOT A VALIDEXECUTION ENVIRONMENT COMMAND.


Explanation: This message is issued by theHDRSBOCP module. The command enteredwas not recognized as a valid ExecutionEnvironment command. This message ispreceded by the S6BDR078I message, whichechoed the command entered.

Action: Check the preceding S6BDR078I messagefor the command entered and reenter with avalid Execution Environment command.

S6BDR085EAN INTERNAL ERROR OCCURREDPROCESSING THE COMMAND


Explanation: This message is issued by theHDRSBOCP module. An ExecutionEnvironment internal error has beenencountered during the processing of thecommand.



| 153

S6BDR086Iuser ........ session termination already inprogress


Explanation: This message was issued inresponse to an Execution EnvironmentCANCELUSER request. This systemdetermined that session termination wasalready in progress either by a priorCANCELUSER request or due to some othererrors such as terminal lost.

Action: If the session in question was notterminated for some reason such as it was ina loop, the FORCEUSER command can beused to force the session. 2 WARNING: Useof the FORCEUSER command may causesystem integrity problems as proper cleanupis not always possible. Use with discretion.

S6BDR087Iuser ........ FORCE session termination has beenscheduled


Explanation: FORCE session request wasaccepted.

Action: Session termination is in progress.

S6BDR088Iuser ........ FORCE session termination already inprogress


Explanation: FORCE termination of the usersession was in progress.

Action: The current request is ignored.

S6BDR089Iuser ........ cancellable - try CANCEL beforeFORCE


Explanation: Always use the CANCEL sessioncommand to take out a session gracefully.Use FORCE only as a last resort.

Action: The FORCE session command has notbeen honoured.

S6BDR090WExecution Environment not authorized, SHUTImay not be successful


Explanation: SHUTI may need to FORCE a usersession and if the Execution Environment isnot running APF authorized, the FORCE willfail and the shutdown may fail.

Action: It is recommended that the ExecutionEnvironment be APF authorized.

S6BDR091ECannot CANCELUSER/FORCEUSER withNOSTAE option specified


Explanation: This message was issued inresponse to an Execution EnvironmentCANCELUSER request. This request cannotbe processed because NOSTAE was specifiedas an Execution Environment configurationoption. TIBCO(r) Object Service Broker uses


154 |

the z/OS ESTAE facilities to cancel a usersession; if NOSTAE is in effect, TIBCO(r)Object Service Broker cannot perform theCANCELUSER function.

Action: Issuing the Data Object Broker commandCANCELUSER may have left the user activeto the Execution Environment. Configureyour Execution Environment with the STAEoption to allow the successful cleanup of theabnormally terminated user session.

S6BDR092EServer type not specified, enter "TYPE="parameter in the command


Explanation: The gateway/server type is neededin order to perform the request for theintended type of gateway/server.

Action: Reenter the command with the TYPE=keyword parameter.

S6BDR093ESTARTNUMSERVER value exceeded themaximum number set - use the SETN commandto increase


Explanation: STARTNUMSERVER valueexceeded either the initial number specifiedin the HRNIN parameter file or the numberset by the SETNUMSERVER command.

Action: Use the SETNUMSERVER command toincrease the maximum.

S6BDR094ESETNUMSERVER value exceeded maximumallowable with the current number ofDISINTRP tasks


Explanation: The SETNUMSERVER value isgreater than the number of DSPINTRP tasksminus one. User sessions run under theDSPINTRP tasks, each rule-basedgateway/server monopolizes oneDSPINTRP task, and at least onegateway/server must be available to run theuser session.

Action: Run a higher number of DSPINTRP tasksby specifying a higher value for theTASKEXECNUM= parameter in the HRNIN.

S6BDR095EUnable to obtain the definition for table '%'


Explanation: An attempt to load the definitionfor the specified table failed.

Action: Make sure the specified table is definedin the MetaStor of the Data Object Broker towhich your osee is connected.

S6BDR096EAttempt was made to start too manytransactions in a session. The limit is %


Explanation: An attempt is being made to nestmore than TRANMAXNUM transactions.

Action: Either increase the value of yourTRANMAXNUM parameter or rewrite yourapplication to require fewer nestedtransactions.


| 155

S6BDR097ESHUTI is invalid without a prior SHUT


Explanation: SHUTI was rejected because theExecution Environment parameter"REJECTSHUTI=YES" is specified.

Action: Try SHUT first. If that does not shutdown the Execution Environment, then useSHUTI.

S6BDR098EData Object Broker rejected server registration


Explanation: An attempt to connect agateway/server process to a Data ObjectBroker failed.


S6BDR099EHCS close port failed for server


Explanation: An attempt to close an HCS portopened for a gateway/server process failed.


S6BDR100IParameter '%' will not be used for server of type'%'


Explanation: Gateways/servers started by anosMon process via a gateway/serverdefinition file have some of their parametersset by the osMon. Any value specified by theuser is ignored. This message informs theuser that the specified parameter's value isoverridden by osMon for the specifiedgateway/server type.

Action: No action required. If you want to avoidthe message, remove the parameter'sassignment from the gateway/serverdefinition file.

S6BDR101EHCS send/receive failure


Explanation: An attempt to send or receive amessage between a gateway/servers processand a Data Object Broker process failed.

Action: Ensure that the Data Object Broker isrunning.

S6BDR102EPreemptive shutdown of server


Explanation: A shutdown message was sent to agateway/server process from a Data ObjectBroker process. As a result, thegateway/server is brought down.

Action: Look in the Data Object Broker processeslog file to determine the reason for theshutdown.


156 |

S6BDR103EUnknown server message type


Explanation: An unknown message type wassent from the Data Object Broker to agateway/server.


S6BDR104ELogon request for remote user was rejected


Explanation: A peer server rejected a logonrequest from a remote user.

Action: Messages that precede this messageshould provide sufficient information todetermine the reason for the failure. Checkthe security profile of the user.

S6BDR105EExecution of server transaction failed


Explanation: Execution of a gateway/servertransaction failed.

Action: Messages that precede this message inthe log should provide sufficient informationto determine the cause of the failure.

S6BDR106EServer parameters generation failed


Explanation: Several of the parameters used tostart peer servers are generated by theosMon. This process failed.

Action: Make sure the EENAME parameter is setto a non-empty string and the number ofservers started by a given osMon is less than1369.

S6BDR107EThis server TYPE is ONLY valid in a CICS EE.


Explanation: The TYPE of gateway/server beingrequested in the operator command is onlyvalid in a CICS Execution Environment.

Action: Please refer to the Object Service Brokerdocumentation for the valid gateway/servertypes. Contact TIBCO Support if you needfurther assistance.

S6BDR108EThis server TYPE is NOT valid in a CICS EE.


Explanation: The TYPE of gateway/server beingrequested in the operator command is notvalid in a CICS Execution Environment.

Action: Please refer to the Object Service Brokerdocumentation for the valid gateway/servertypes. Contact TIBCO Support if you needfurther assistance.


| 157

S6BDR109EOnly 1 (one) server of this TYPE is allowed in agiven EE.


Explanation: This is due to the restrictions of theTYPE of DBMS which allows only one threadper Address Space.

Action: Please refer to the Object Service Brokerdocumentation for a detailed explanation.Contact TIBCO Support if you need furtherassistance.

S6BDR110ECLI Client CONNECT request failed. Reason:EE not initialized with Standby Sessions.


Explanation: The Execution Environment wasnot initialized with Standby Sessions.Standby Sessions are needed to support CLIClient/Server applications.

Action: Use either of the following options toprovide Standby Sessions in the ExecutionEnvironment:

• Specify the STANDBYNUM=n regionparameter via EECONFIG or via HRNINto set the number of sessions desired.

• Use the following set of operatorcommands to dynamically start upStandby Sessions:

• For Native Execution Environment:

F jobname,SETN=n,TYPE=STB

F jobname,STARTN=n,TYPE=STB

• For CICS Execution Environment, usethe HSRV transaction:

HSRV SETN=n,TYPE=STB

HSRV STARTN=n,TYPE=STB

S6BDR111EStart <type> CICS background task failed.Reason: EE not APF authorized.


Explanation: z/OS APF authorization is requiredfor the Execution Environment to start theindicated CICS background task.

Action: Refer to the Object Service Brokerdocumentation to learn how to APFauthorize the Execution Environment.Contact TIBCO Support if you need furtherassistance.

S6BDR112ECLI Start session failed. Reason: No StandbySessions exist in EE


Explanation: There are no Standby Sessions inthe Execution Environment. StandbySessions are needed to support CLIClient/Server applications.

Action: Use one of the following options toprovide Standby Sessions in the ExecutionEnvironment:

• Specify the STANDBYNUM=n regionparameter via EECONFIG or via HRNINto set the number of sessions desired.

• Use the following set of operatorcommands to dynamically start upStandby Sessions:

• For Native Execution Environment:

F jobname,SETN=n,TYPE=STB

F jobname,STARTN=n,TYPE=STB

• For CICS Execution Environment, usethe HSRV transaction:

HSRV SETN=n,TYPE=STB

HSRV STARTN=n,TYPE=STB


158 |

S6BDR113WEE FAILED TO CONNECT TOCOMMUNICATION PORT ........ HDRINITIALIZATION TERMINATED


Explanation: This message is issued by theS6BDRTMR module. Unable to establish anoperator communication connection with thehost Object Service Broker Data ObjectBroker or the Object Service Broker NativeExecution Environment.


1. Ensure that the Object Service Broker DataObject Broker or the Object Service BrokerNative Execution Environment is active.

2. If the Object Service Broker Data ObjectBroker or the Object Service Broker NativeExecution Environment is active, contactTIBCO Support.

S6BDR114EComputer name (%) is too long


Explanation: The operating system name givento the host computer is too long. ObjectService Broker expects it to be less than 17characters.

Action: Rename your host computer to a namewhose length is less than 17 characters.

S6BDR115ETOKEN service is not supported by theOperating System, Encryption Exit not enabled


Explanation: The Operating System's TOKENservice is used to implement the EncryptionExit to protect the potential integrityexposure and this version of the OperatingSystem does not support this service.

Action: z/OS is required for the IEANTCRservice.

S6BDR116ETOKEN create failed, Encryption Exit notenabled


Explanation: Attempt to create the EncryptionExit TOKEN failed. This is probably causedby Object Service Broker internal error.


S6BDR117ETOKEN delete failed, Encryption Exit notdeleted


Explanation: Attempt to delete the EncryptionExit TOKEN failed, this is probably causedby Object Service Broker internal error. TheEncryption Exit routine would be deleted bythe Operating System cleanup routine at EEtermination.

Action: None.


| 159

S6BDR118WSERVERTYPE=........ NOT SUPPORTED IN A........ ENVIRONMENT


Explanation: This message is issued by theHDRSBSRV csect called by S6BDRTMRduring Execution Environment initializationand termination. The message indicates thatthe Execution Environment is attempting tostart a gateway/server in an environmentthat does not support the specified gatewaytype. Execution Environment initializationcontinues as normal.

Action: Start the gateway/server in a supportedenvironment. Refer to the Object ServiceBroker documentation for more information.

S6BDR119WSERVERS NOT STARTED


Explanation: Message issued by CSECTHDRSBSRV. This message accompaniesmessage S6BDR118W and indicates that agateway/server of the specified type couldnot be started.

Action: Start the gateway/server in a supportedenvironment. Refer to the documentation formore information.

S6BDR120WNUMBER OF SERVERS REDUCED TO 1 FORTHIS SERVERTYPE


Explanation: Multiple external databasegateways were requested via the SERVERS=parameter. Only one gateway of the specifiedgateway type can be started. The system hasautomatically reduced the requested numberof gateways to one.


S6BDR121ILanguage Environment pre-initializationmodule successfully loaded


Explanation: The Object Service BrokerExecution Environment initializationsuccessfully loaded module CEEPIPI, theIBM Language Environment pre-initialization module.


S6BDR122ECLI Start EE failed. Reason: This version ofS6BDRAPI does not support CICS EE.


Explanation: The S6BDRAPI load module is notlinkedited with the required CICS stubs.

Action: Reinstall the Object Service Broker CICScomponent.


160 |

S6BDR123EWait on named pipe %


Explanation: A wait() on an operating systemnamed pipe (or FIFO) failed.

Action: If this message persists, contact TIBCOSupport.

S6BDR124EClient socket cannot be duplicated


Explanation: The osee process cannot duplicatethe client socket.


S6BDR125WStart session waiting for available standbysession


Explanation: All available standby sessions inthis Execution Environment are in use.Therefore the Start session request is put in await queue.

Action: Check with your Object Service Brokersystem administrator about increasing thenumber of standby sessions.

S6BDR126IWaiting for standby session complete


Explanation: The waiting for a standby session isover; one or more standby sessions havebecome available.

Action: None.

S6BDR127ERemote CLI user ........ session Receive Exiterror, session terminated


Explanation: The Object Service Brokercommunications Receive Exit detected asevere internal system error during theprocessing of an incoming message. Theerror was unrecoverable and the session wasunable to continue.

Action: The session was terminated.

S6BDR128INumber of tttttttt task changed to nnn


Explanation: The number of the named task hadbeen increased to the number nnn. This isbecause the number specified in EE CONFIGor in the EE HRNIN parameter file did notmeet the minimum required for thesuccessful operation of the ExecutionEnvironment. tttttttt is the type of task nnn isthe number of the type of task

Action: None.

S6BDR130IEXECUTION ENVIRONMENT QUIESCE HASCOMMENCED


Explanation: Normal shutdown of the ExecutionEnvironment has started.



| 161

S6BDR131ICLI Start session waiting for standby session toinitialize


Explanation: There are no active standbysessions in the CICS Execution Environment.Standby sessions are needed to support CLIclient/server applications.

This situation could happen if the CLIapplication is getting ahead of the standbysession initialization.

Action: None.

S6BDR132ICLI Start session waiting for standby session toinitialize is complete


Explanation: The wait for standby sessioninitialization is over; one or more standbysessions have become ready.

Action: None.

S6BDR133W........ DD statement ignored


Explanation: The print DD statement named inthe message is ignored because it is not to beused in a multi-user Execution Environmentsuch as CICS or in a Native ExecutionEnvironment.

Object Service Broker dynamically allocatesspool data sets for print output.


S6BDR135WOPERATOR COMMAND REJECTED;SHUTDOWN PROCESS IN FINAL STAGES


Explanation: Operator command logged via thepreceding S6BDR078I message is not beingaccepted since Shutdown processing is in itsfinal stages and necessary components toservice this command may have beendismantled.

Action: None.

S6BDR136IExecution Environment initialization complete,Version: ........


Explanation: This message indicates that theExecution Environment initialization processhas completed and Version indicates thecurrent release level.

Action: None.

S6BDR137EInvalid request code XXXXXXXX passed toHDRCSOPS


Explanation: An invalid request code was passedto HDRCSOPS.



162 |

S6BDR138EInvalid data returned to HDRCSOPS fromHDRBUSR


Explanation: Invalid data was returned toprogram HDRCSOPS from programHDRBUSR.


S6BDR139ESMG could not be initialized


Explanation: The SMG control block could not beinitialized.


S6BDR140ESTOPSERVER failed, Type=..., Name=........,Id=........, RC=...., reason code=....


Explanation: The STOPSERVER request sent tothe Data Object Broker came back with thereturn code and the reason code indicated inthe message.

Possible return codes and their reason codesare:

• 8

• 0 - Request not implemented

• 4 - Type or group not defined

• 8 - Resource not defined

• 12 - Path not found

• 12 - Directive error detected

Action: The Execution Environment would notbe shutdown successfully if thegateway/server was not stopped. TheExecution Environment may appear to behung You can try to stop the gateway/servermanually by using the Admin Facility or thefollowing z/OS console command:

F dobjname,STOPSERVER=id,TYPE=type

S6BDR141ESession ran out of memory


Explanation: The session ran out of memory.

Action: Increase the SESSIONMEMMAXparameter value.

S6BDR142ETransaction ran out of memory


Explanation: A transaction ran out of memory.

Action: Increase the TRANMEMMAX parametervalue.

S6BDR143WFailed to send session log to OAI client due toloss of communication connection


Explanation: The attempt to send the session logto the ActiveX Adapter client failed becausethe connection to the client is lost.

Action: Determine why the connection is lost. Itis typically either a hardware failure or animproper shutdown of the ActiveX Adapterapplication.


| 163

S6BDR144WFailed to send end-of-session message to theclient due to loss of communication connection


Explanation: The attempt to send the end-of-session message to the client failed becausethe connection to the client is lost.

Action: Determine why the connection is lost. Itis typically either a hardware failure or animproper shutdown of the ActiveX Adapterapplication.

S6BDR145WClient closed session


Explanation: The client process closed thesession. The normal shutdown procedurecalls for the Execution Environment toinitiate session close.

Action: Determine why the client process closedthe session. Typically it is as a result of theuser forcing a disconnection.

S6BDR146EInvalid data received on client / EE connection


Explanation: Data received by an ExecutionEnvironment process from a client processdid not satisfy the constraints of thecommunication protocol.

Action: If the message persists, contact TIBCOSupport.

S6BDR147WUnable to initialize compression engine,level=%


Explanation: The attempt to initialize thecompression engine for ActiveX Adaptercommunication packet compression failed.The ActiveX Adapter connection isestablished with no compression.


S6BDR148EOAI client version %.% is not supported by thisExecution Environment


Explanation: The ActiveX Adapter client versionis not supported by the ExecutionEnvironment.

Action: Upgrade your ActiveX Adapter client toa more recent version.

S6BDR149EUnable to compress data. Error code = %


Explanation: The Execution Environment failedto compress a packet destined for an ActiveXAdapter client.

Action: If the problem persists, contact TIBCOSupport.


164 |

S6BDR150EUnable to decompress data. Error code = %


Explanation: The Execution Environment failedto decompress a packet received from anActiveX Adapter client.


S6BDR151EThread operation failed, '%'


Explanation: An attempt to execute the specifiedthread operation failed.

Action: Examine the operating system errorcodes to determine the reason for this failure.

S6BDR152EFailed to initialize the trusted base


Explanation: During session initialization, theExecution Environment failed to initializethe trusted base tables.

Action: Make sure the Data Object Broker isoperating correctly.

S6BDR153EUpdate of audit log Failed


Explanation: An attempt to update the audit logfailed.

Action: Make sure the Data Object Broker isoperating correctly. Check to see if the auditlog is full. If this error persists, contact TIBCOSupport.

S6BDR154ECommunication Services close port failed


Explanation: An attempt to close an ObjectService Broker Communication Service portfailed.

Action: This message may result from the abendof the process on the other end of the port.Examine accompanying messages in thelocal log and in the remote processes' logfiles.

S6BDR155EAttempt to prompt user for userid/passwordfailed


Explanation: An attempt to prompt a user fortheir userid and password failed.

Action: Retry to log on onto the system.

S6BDR156EAn error occurred while attempting to % amutex


Explanation: The specified action on anoperating system mutex failed.

Action: Examine the operating system errorcodes to determine the reason for the failure.If the error persists, contact TIBCO Support.


| 165

S6BDR157EAttempt to exceed EE-DOB connection limit forDOB '%' failed


Explanation: The specified Data Object Brokerhas been configured to accept only aspecified number of Execution Environmentconnections. An attempt was made to exceedthis limit.

Action: Do either of the following:

• Connect fewer Execution Environments tothe Data Object Broker. This can be doneby increasing the number of sessions thatrun on each Execution Environment.

• Increase the MAXUSERS parameter that isset in the crparm file.

S6BDR158EAn error occurred while attempting to % amemory mapped file


Explanation: The specified action on a memorymapped file failed.

Action: Check the operating system error code todetermine the reason for the failure. If theproblem persists, contact TIBCO Support.

S6BDR159EAn error occurred while attempting to % anevent


Explanation: The specified action on an eventfailed.

Action: Check the operating system error code todetermine the reason for the failure. If theproblem persists, contact TIBCO Support.

S6BDR160EAn error occurred while attempting to % asecurity descriptor


Explanation: The specified action on a securitydescriptor failed.

Action: Check operating system error code inorder to determine the reason for the failure.If the problem persists, contact TIBCOSupport.

S6BDR161EAn atexit call failed


Explanation: An atexit call, a system called madeto ensure proper process shutdown, failed.

Action: Check operating system error code inorder to determine the reason for the failure.If the problem persists, contact TIBCOSupport.

S6BDR162EFailed to bind to shared table / rule cache


Explanation: An Execution Environment failedto bind to the shared table or rule cachemaintained by its osMon.

Action: Check the logs to determine the reasonfor failure. If the problem persists, contactTIBCO Support.


166 |

S6BDR163EProcess operation '%' failed


Explanation: The specified operation failed on aprocess object.


S6BDR169EFailed to create or start the thread that waits forsession terminations


Explanation: An attempt to create or start thethread that waits for session threadterminations failed.

Action: Previous error messages and operatingsystem error codes written to the log shouldexplain the reason for the failure.

S6BDR170ITIMEOUTLIMIT reached waiting for keyboardinput


Explanation: The session has shutdown afterwaiting for keyboard input for more than theamount of time specified by theTIMEOUTLIMIT parameter.

Action: If you do not want a timeout, set theTIMEOUTLIMIT parameter to a larger valueor to zero. Refer to the Parameters manual formore detail on the TIMEOUTLIMIT andALLOWSESSIONTIMEOUTLIMITparameters.

S6BDR171EStandby Session initialization failed


Explanation: The initialization of a standbysession failed. This message follows other,more specific, error messages.

Action: Check for other error messagespreceding this message.

S6BDR172IUnable to issue HINT command. Reason: EEnot APF authorized.


Explanation: An automatic re-cycle of the CICSinterface was required due the failure of theData Object Broker. The EE was unable toissue the HINT command to achieve this asthe EE was not APF authorized.

Action: If desired restart the CICS interfacemanually. If automatic restart capability isrequired APF authorize this EE.

S6BDR173EError in registry key %


Explanation: The previous error was found inthis registry entry.

Action: Correct the previous error.

S6BDR174EError in parameter file % in section preceedingline %


Explanation: The previous error was found inthis file.

Action: Correct the previous error.


| 167

S6BDR200ILanguage Environment pre-initializationmodule is being loaded


Explanation: This is an informational messageindicating that CEEPIPI, the LE pre-initialization module, is being loaded.

If loading of this module is successful,initialization of the Object Service BrokerExecution Environment continues.

If it fails, initialization of the Object ServiceBroker Execution Environment is terminatedby the Operation System with an abend codeand a reason code.

Action: If initialization is unsuccessful,determine the cause of failure by referring toyour operating system's abend codesmanual. For assistance, contact TIBCOSupport.

S6BDR201ELanguage Environment function(%) failed,RC=%


Explanation: A call to the IBM LanguageEnvironment preinitialization interfaceroutine (CEEPIPI), to run the identifiedfunction, ended in an error.

RC identifies the Return Code from the LEinterface routine. The function code and RCare documented in the IBM LanguageEnvironment Programming Guide.

This is likely an internal Object ServiceBroker error.


S6BDR202Esub_ret_code=% sub_reason_code=%sub_feedback_code=%


Explanation: This message provides additionalinformation, if available, to messageS6BDR201E. All the codes are documented inthe IBM Language EnvironmentProgramming Guide.

See message S6BDR201E for moreinformation.


S6BDR300EParameter % does not specify an accessibledirectory


Explanation: The value of the parameter does notspecify an existing directory.

Action: Set the parameter to the path of anaccessible directory.

S6BDR301ETemporary file allocation routine '%' failed


Explanation: An attempt to allocate a temporarydisk file failed. Likely causes are insufficientdirectory permissions or disk full conditions.



168 |

S6BDR302EError occurred during sanity check of temporarydirectory parameter % [%]


Explanation: Verification that temporary filesmay be created, opened for read and writeaccess, and deleted within the temporarydirectory failed.

Action: Review any previous messages related totemporary files to determine the action to betaken.

S6BDR400ESystem call '%' failed


Explanation: A system call failed.


S6BDR401EPOSIX thread API '%' failed, retcode=[%]


Explanation: A POSIX thread API call failed.

Action: Examine the return code to determine thereason for the failure.

S6BDR402EPOSIX semaphore API '%' failed


Explanation: A POSIX semaphore API call failed.


S6BDR403EUI thread API '%' failed, retcode=[%]


Explanation: A UNIX International thread APIcall failed.

Action: Examine the return code to determine thereason for the failure.

S6BDR405EWin32 API '%' failed


Explanation: A Win32 API call failed.


S6BDR420EError occurred creating thread


Explanation: An attempt to create a thread failed.


S6BDR421EError occurred destroying thread


Explanation: An attempt to destroy a threadfailed.



| 169

S6BDR422EError occurred starting thread


Explanation: An attempt to start a thread failed.


S6BDR423EInvalid state for thread start, state=%


Explanation: A thread object was not in thecorrect state to allow a start operation.


S6BDR424EError occurred resuming thread


Explanation: An attempt to resume a threadfailed.


S6BDR425EError occurred joining with thread


Explanation: An attempt to join with a threadfailed.


S6BDR426EAttempt made to join with detached thread


Explanation: An illegal attempt was made to joinwith a thread that is detached.


S6BDR427EInvalid state for thread join, state=%


Explanation: A thread object was not in thecorrect state to allow a join operation.


S6BDR428EError occurred obtaining thread state


Explanation: An attempt to get the state of athread failed.


S6BDR429EError occurred exiting thread


Explanation: An attempt to exit a thread failed.



170 |

S6BDR430EError occurred during thread sleep


Explanation: A request to sleep could not besatisfied for the requested interval.


S6BDR431EThread Id % has ABENDED from an exceptionthrown at %:%


Explanation: A thread detected it has notcorrectly handled an internal exception.


S6BDR432EThread Id % has ABENDED from anunexpected exception


Explanation: A thread detected that it incorrectlyhandled an unexpected exception.


S6BDR440EError occurred allocating TLS index


Explanation: An attempt to allocate an index forthread local storage failed.


S6BDR441EError occurred getting TLS value, index=%


Explanation: An attempt to get a valueassociated with an index for thread localstorage failed.


S6BDR442EError occurred setting TLS value, index=%


Explanation: An attempt to set a value associatedwith an index for thread local storage failed.


S6BDR450EError occurred creating mutex


Explanation: An attempt to create a mutex failed.


S6BDR451EError occurred destroying mutex


Explanation: An attempt to destroy a mutexfailed.



| 171

S6BDR452EError occurred locking mutex


Explanation: An attempt to lock a mutex failed.


S6BDR453EError occurred unlocking mutex


Explanation: An attempt to unlock a mutexfailed.


S6BDR460EError occurred creating semaphore


Explanation: An attempt to create a semaphorefailed.


S6BDR461EError occurred opening semaphore


Explanation: An attempt to open a semaphorefailed.


S6BDR462EError occurred destroying semaphore


Explanation: An attempt to destroy a semaphorefailed.


S6BDR463EError occurred posting semaphore


Explanation: An attempt to post a semaphorefailed.


S6BDR464EError occurred waiting on semaphore


Explanation: An attempt to wait on a semaphorefailed.


S6BDR465EError occurred during semaphore timed wait


Explanation: A timed wait on a semaphorefailed.



172 |

S6BDR501EFailed to load DLL/Shared Object % forS6BCALL/S6BFUNCTION support


Explanation: The Execution Environment failedto load one of the DLLs/Shared Objectslisted in the S6BCALLLIBRARIES parametervalue.

Action: Ensure that the DLL/Shared Objectnames in S6BCALLLIBRARIES are spelledcorrectly and the DLLs/Shared Objects are inthe relevant paths.

S6BDR502EDLL/Shared Object % has no entry point forS6BCALL/S6BFUNCTION support


Explanation: The Execution didn't find therequired entry point forS6BCALL/S6BFUNCTION support in theDLL/Shared Object.

Action: Ensure that the DLL/Shared Object isproperly coded S6BCALL/S6BFUNCTIONsupport.

S6BDR969EFailed to update DOB session counter


Explanation: An attempt to update a Data ObjectBroker session counter (increase or decrease)failed.

Action: Preceding log messages should providemore information as to the reason for thefailure.

S6BDR970ENot licensed to access TIBCO(r) Object ServiceBroker


Explanation: The limits entry is missing in thelicense key.

Action: Check the session limits and types in thelicense key. Contact TIBCO Support.

S6BDR971ELicense key limit exceeded


Explanation: You exceeded the limit of usersallowed for this session type as specified inthe license key.

Action: Check the session limits and types in thelicense key. If necessary, contact TIBCOSupport.

S6BDR972WNot enough session memory to minimizeRemote CLI/Java CLI message buffer


Explanation: The Execution Environment failedto optimize Remote CLI/Java CLI memoryusage - not enough session memory.

Action: Increase the SESSIONMEMMAXparameter.


| 173

S6BDR973ENot enough session memory to accommodateDataOut Remote CLI/Java CLI commarea


Explanation: The Execution Environment cannotallocate the DataOut Remote CLI/Java CLIcommarea for rule call -- not enough sessionmemory.

Action: Increase the SESSIONMEMMAXparameter value.

S6BDR974ECannot allocate memory for a Remote CLI or aJava CLI session


Explanation: There is not enough memory tocomplete Remote CLI or Java CLI requestprocessing.

Action: Increase the SESSIONMEMMAXExecution Environment parameter value ormake more main memory available to ObjectService Broker.

S6BDR975EInvalid Remote CLI/Java CLI message received.Session abended


Explanation: Data received by an ExecutionEnvironment process from a Remote CLI orJava CLI client process does not satisfy theconstraints of the communication protocol.


S6BDR976EThis version of Remote CLI or Java CLI client isnot supported


Explanation: This version of the Remote CLIclient or the Java CLI client is not supportedby this Execution Environment.

Action: Use the appropriate version of theRemote CLI client or the Java CLI client.

S6BDR977EUnexpected Remote CLI or Java CLI requestreceived. Session abended


Explanation: The Remote CLI client or the JavaCLI client issued an invalid sequence ofrequests. The session abended.


S6BDR978ECannot open Remote CLI/Java CLI port. Sessionabended


Explanation: The Execution Environment failedto open a port for Remote CLI or Java CLIconnection.



174 |

S6BDR979WNot enough session memory to receive RemoteCLI/Java CLI message


Explanation: The Execution Environment cannotaccommodate the incoming RemoteCLI/Java CLI message - not enough sessionmemory.

Action: Increase the SESSIONMEMMAXExecution Environment parameter value.

S6BDR980ERemote CLI/Java CLI DataOut commarea isinconsistent after rule call


Explanation: A rule called via the Remote CLI orthe Java CLI reformatted the DataOutcommarea header incorrectly.

Action: Make sure that the rule formats the CLIDataOut commarea header correctly.

S6BDR981ECannot register Remote CLI/Java CLIcommareas


Explanation: The Execution Environment failedto register Remote CLI/Java CLI commareamemory.


S6BDR984ESystem message log overflow


Explanation: An attempt is being made to writetoo much data into the system message log.

Action: Increase the value of the SESSIONMSGLOGMAX parameter.

S6BDR985EUser message log overflow


Explanation: An attempt is being made to writetoo much data into the user message log.

Action: Increase the value of the SESSIONMSGLOGMAX parameter.

S6BDR992ERemote CLI or Java CLI connection lost. Sessionabended


Explanation: A connection to a Remote CLI or aJava CLI client process was lost.

Action: Check the accompanying messages todetermine the reason for the lost connection.


| 175

S6BDR996EThere are no local printers accessible from yourcomputer


Explanation: The PRINTDEST parameter is set toLOCAL. An attempt was made to determinewhich printers are local with respect to themachine on which the process is executing. Itfailed to locate any local printer.


S6BDR997EError occurred while attempting to enumeratelocal printers


Explanation: The PRINTDEST parameter is set toLOCAL. An attempt was made to determinewhich printers are local with respect to themachine on which the process is executing. Itfailed to locate any printer.


S6BDR998WOnly one of PRINTDEST and PRINTXWTRshould be non-NULL


Explanation: The PRINTDEST parameterspecifies the name of the printer the userwants reports printed on. PRINTXWTRspecifies a program that directs reports to anonstandard device. Only one of themshould be specified at a time.

Action: Reset one of these parameters to NULL.Look in the session log file to determine thesource of each parameter.

S6BDR999EEnd OAI client failed. Return code = %


Explanation: An attempt to terminate aconnection to an ActiveX Adapter client byan osee failed.



176 |

D2: DB2 Gateway

S6BD2000I%

Source: DB2 Gateway

Explanation: This is an echo of the start upparameters.


S6BD2001IStarting gateway initialization

Source: DB2 Gateway

Explanation: Object Service Broker gatewayinitialization is starting.


S6BD2002EDB2 CAF % ERROR: % % % %

Source: DB2 Gateway

Explanation: The CAF CONNECT call failedwith the specified DB2 reason code. A DB2Call Attach Facility (CAF) call failed. Thefirst variable identifies the type of call(CONNECT, OPEN, CLOSE, orDISCONNECT). The second variableidentifies the DB2 reason code for the failure.The third variable indicates the DB2 SSIDthat the call was issued against. The fourth

displays the DB2 plan name being OPENEDor CLOSED. The fifth is the DB2 errormessage, if available, that describes thereason for the OPEN plan failure.

Action: The reason code is described in the DB2Messages & Codes manual. Check thismanual for the meaning of the error code andtake the action dictated. Verify that the CAFcall is being issued against the correct DB2SSID and/or PLAN. If not, make sure thegateway was started with the correct DB2SSID and/or PLAN.

S6BD2003ETIBCO(r) Object Service Broker "%" is notavailable

Source: DB2 Gateway

Explanation: The external gateway for DB2 datahas not been connected to the Data ObjectBroker identified by the indicated APPLID.

Action: Ensure that the TDSAPPL andMODLAPPL parameters are correct. Verifythat the Data Object Broker is active beforestarting the gateway.

S6BD2004IDB2 Gateway terminated

Source: DB2 Gateway

Explanation: The DB2 Gateway terminated. Theserverid and userid are indicated in themessage prefix.



| 177

S6BD2005EStartup parameter format error

Source: DB2 Gateway

Explanation: The gateway start-up parameterscontain a syntax error. The parameter inquestion was echoed by message S6BD2000I.

Action: Correct the parameter format.

S6BD2006EThe previous startup parameter is invalid

Source: DB2 Gateway

Explanation: The start-up parameter value isinvalid. The parameter value appears in thepreceding S6BD2000I message.

Action: Correct the parameter and start thegateway again.

S6BD2007EFail safe table definition ; not found

Source: DB2 Gateway

Explanation: The table name specified cannot befound.

Action: Determine the fail safe table name andcorrect it. The default table name is@DB2FSTRXDB.

S6BD2023ERequired input parameter missing

Source: DB2 Gateway

Explanation: A required gateway start-upparameter is missing. The TDSAPPL andSSID parameters are both required.

Action: Provide the missing parameter andrestart the gateway.

S6BD2024EError attaching gateway subtask

Source: DB2 Gateway

Explanation: An error was encountered duringthe attachment of a gateway subtask.


S6BD2026EFailed to open file: "%"

Source: DB2 Gateway

Explanation: The specified file cannot be opened.

Action: Check the file. If you cannot find aproblem with the file, contact TIBCOSupport.

S6BD2028EGateway subtask initialization failed: "%"

Source: DB2 Gateway

Explanation: During gateway subtask startupone of the storage initialization functionsfailed:

• HDRSB$SV - Stack storage format failed.

• HDRSBCEV - Initialization of the Cenvironment failed.


1. Verify that the installation procedureswere correct.

2. Verify that the JOB/TASK region size issufficient.

3. Contact TIBCO Support if the first twoitems are correct.


178 |

S6BD2029EDefinition bind area initialization failed

Source: DB2 Gateway

Explanation: An error was encountered whileinitializing the table definition bind area.


1. Verify installation procedures are correct.

2. Verify that the POOLSIZE startupparameter is specified correctly.

3. Verify that the JOB/TASK region size issufficient.

4. Contact TIBCO Support if the first twoitems are correct.

S6BD2030ETIBCO(r) Object Service Broker "%" versionmismatch

Source: DB2 Gateway

Explanation: The gateway is attempting toconnect to a Data Object Broker that is not atthe same release level.

Action: Verify the TDS start-up parameter.Contact your system administrator to findout what release of the gateway andTIBCO(r) Object Service Broker wereinstalled.

S6BD2031IGateway connected to TIBCO(r) Object ServiceBroker "%"

Source: DB2 Gateway

Explanation: The DB2 Gateway connected withthe TIBCO(r) Object Service Broker runningunder the indicated APPLID.


S6BD2032ECLOSE PLAN(%) SSID(%) %

Source: DB2 Gateway

Explanation: The gateway closed the DB2 planfrom the specified SSID for the indicatedreason.


S6BD2033ESQL ERROR FOR: % CODE: % VARIABLES: %

Source: DB2 Gateway

Explanation: The gateway received an SQL errorwith the indicated code after issuing theindicated SQL call to DB2.

Action: Refer to the DB2 messages and codes forfurther information and take the actionindicated for the code that was receivedbased on the variables.

S6BD2034ESQL WARNING FOR: % CODE: % WARNING:% VARIABLES: %

Source: DB2 Gateway

Explanation: The gateway received an SQLwarning of the indicated code after issuingthe indicated SQL statement to DB2.

Action: Refer to the DB2 messages and codes andtake the action indicated for the code thatwas received.


| 179

S6BD2036ESQLCODE % %. %

Source: DB2 Gateway

Explanation: A DB2 SQL call returned theindicated sqlcode. The third parameter is thetext of the DB2 message.

Action: Refer to the DB2 messages and codes forfurther information and take the actionindicated for the code received.

S6BD2037ENo columns in the DB2 table definition

Source: DB2 Gateway

Explanation: The DB2 table definition containsno columns.

Action: Correct the DB2 table definition from theDB2 environment.

S6BD2038EOccurrence not found

Source: DB2 Gateway

Explanation: The requested occurrence was notfound in the DB2 table.


S6BD2039EStatic SQL is not supported after partial access

Source: DB2 Gateway

Explanation: Static SQL was used to satisfy partof the request, but is not supported toperform the remainder of the request.


1. Regenerate the Static SQL, for the gatewayfor the table being accessed.

2. Reattempt the request.

3. Contact TIBCO Support if necessary.

To default back to Dynamic SQL for therequest, use the Object Service Broker TableDefiner to save the definition of the table.

S6BD2040EDB2 row too large

Source: DB2 Gateway

Explanation: The DB2 row instance is too largefor the gateway buffer.


S6BD2041EUnknown DB2 column type

Source: DB2 Gateway

Explanation: The gateway encountered a DB2column with a COLTYPE that is not known.


S6BD2042ENo columns found for requested table

Source: DB2 Gateway

Explanation: The DB2 table definitioncorresponding to the Object Service Brokerexternal table has no columns defined.

Action: Correct the DB2 table definition. ContactTIBCO Support if necessary.

S6BD2043ESelection string error

Source: DB2 Gateway

Explanation: An error was encountered whenparsing the selection string.



180 |

S6BD2044EDB2 column not found for: "%"

Source: DB2 Gateway

Explanation: The DB2 column mapped to one ofthe Object Service Broker external table fieldsdoes not exist in the DB2 table definition.This could be caused when the named DB2column is also a DB2 reserved word.

Action: Correct the external table or the DB2table definition.

S6BD2046ECursor not found for subsequent Forall

Source: DB2 Gateway

Explanation: The gateway encountered an errorwhen trying to obtain the next set of recordsduring FORALL processing. The cursorassociated with the request in progress couldnot be found.


S6BD2047ENo available cursors for request

Source: DB2 Gateway

Explanation: The limit of nested GETs orFORALLs on DB2 tables was exceeded.

Action: Verify that the transaction logic is correct.Contact TIBCO Support if necessary.

S6BD2049EMissing definition of host variable

Source: DB2 Gateway

Explanation: When trying to get a column valuefrom the row retrieved, the host variable thatis to contain it could not be found.


1. Regenerate the Static SQL, for the gatewayfor the table being accessed.

2. Reattempt the request.

3. Contact TIBCO Support, if necessary.

To default back to Dynamic SQL for therequest, use the Object Service Broker TableDefiner to save the definition of the table.

S6BD2051ECONVERSION ERROR on field %: %

Source: DB2 Gateway

Explanation: When converting the field orparameter value to the DB2 syntax, an erroroccurred.

Action: Verify your definitions.

S6BD2052EMaximum number of tables exceeded

Source: DB2 Gateway

Explanation: The maximum number of DB2tables that can be accessed in one transactionwas exceeded.

Action: Verify transaction logic. IncreasePOOLSIZE parameter if necessary.

S6BD2053EGateway cannot store table definition for: "%"

Source: DB2 Gateway

Explanation: Attempt to bind a new tabledefinition failed.

Action: Restart the gateway with a largerPOOLSIZE.


| 181

S6BD2054EUnsupported request: "%"

Source: DB2 Gateway

Explanation: The request received by thegateway is not supported.


S6BD2055ESecurity information was not received

Source: DB2 Gateway

Explanation: The TIBCO(r) Object Service Brokerrelease level does not match the Gatewayrelease level or a severe error occurred.

Action: Ensure that the gateway was installed atthe current release level. If this was done andthe problem persists, contact TIBCO Support.

S6BD2056ECurrent group value cannot be used as a validuserid

Source: DB2 Gateway

Explanation: The gateway is configured to usethe Current Group as the DB2 primaryauthorization ID. The group of the currentuser cannot be used as a valid DB2 primaryauthorization ID.

Action: Make sure the user belongs to a TIBCO(r)Object Service Broker group and the lengthof the TIBCO(r) Object Service Broker groupdoes not exceed 8 bytes.

S6BD2057EBlank userid received

Source: DB2 Gateway

Explanation: Security requirements are notfulfilled according to documentedprocedures, or a version mismatch existsbetween the gateway and the Object ServiceBroker Execution Environment.


S6BD2058EUserid "%" is not authorized to execute plan"%", or plan "%" does not exist

Source: DB2 Gateway

Explanation: You are not authorized to executethe named plan, or the named plan does notexist.

Action: Grant execute on the plan name to theuserid; and/or define the plan to DB2.

S6BD2059EUserid "%" matches a DB2 privilegedauthorization id and is rejected

Source: DB2 Gateway

Explanation: The Object Service Broker useridmentioned in the message matches a DB2primary authorization ID coded in macroHRNSECDZ. The IDs in HRNSECDZ areprivileged DB2 authorization IDs and cannotbe used to access DB2 from Object ServiceBroker. These IDs are defined and coded bythe customer.

Action: Do one of the following;

• Remove the ID form HRNSEDZ.

• Use another Object Service Broker useridto access DB2.


182 |

S6BD2062EUserid "%" is not authorized to start an DB2Gateway

Source: DB2 Gateway

Explanation: HRNSECD2 (the DB2 securitymacro) within DSN3@ATH (DB2 connectionauthorization exit) could not match theuserid used to start the DB2 Gateway withone of the IDs within HRNSECDT.

Action: Verify that:

• The macro HRNSECD2 was correctlyinstalled in DSN3@ATH.

• The DB2 Gateway was installed correctly.

• The userid used to start the DB2 Gatewayis defined in table HRNSECDT.

• Contact TIBCO Support, if necessary.

S6BD2063EDB2 primary authorization id was not set to theTIBCO(r) Object Service Broker userid

Source: DB2 Gateway

Explanation: The DB2 Gateway was started withSECLEVEL=1 but macro HRNSECD2 in DB2connection authorization exit DSN3@ATHfailed to set the DB2 primary authorizationID with the TIBCO(r) Object Service Brokeruserid.

Action: Verify that:

• The macro HRNSECD2 was correctlyinstalled in DSN3@ATH

• The DB2 Gateway was correctly installed.

S6BD2064IDEBUG: %

Source: DB2 Gateway

Explanation: An echo of the CAF debugmessages. This is displayed if DEBUG is on.


S6BD2066EMissing value for table parameter

Source: DB2 Gateway

Explanation: The table is parameterized and aparameter value is missing.


S6BD2067EUnsupported operator: "%"

Source: DB2 Gateway

Explanation: The operator specified in theselection is not supported.


S6BD2069EField in key selection was not found in table

Source: DB2 Gateway

Explanation: The field specified in the selectionwas not found in the definition of the table.



| 183

S6BD2070EField in ordered clause was not found in table

Source: DB2 Gateway

Explanation: A field in the order statement wasnot found in the definition of the table.


1. Verify the definition of the request.

2. Verify the definition of the table.

3. Restart the gateway and user session.

4. Retry the request.

5. Contact TIBCO Support if still failing.

S6BD2071EDB2 SQL statement too long

Source: DB2 Gateway

Explanation: The SQL statement that thegateway is attempting to build is too large forthe buffer that the gateway is using.


S6BD2072ENo DB2 threads available

Source: DB2 Gateway

Explanation: The maximum number ofconcurrent identify level agents has beenexceeded. The DB2 Gateway detected a00F30055 error code.

Action: User response: Try again later.

System Programmer Response: Ensure thatthe DB2 system parameters controlling themaximum number of concurrent identifiesare correct. These system parameters areMax Users, Max TSO connect and Max Batchconnect on installation panel DSNTIPE.

S6BD2073IThe DB2 Gateway is not running authorized

Source: DB2 Gateway

Explanation: The DB2 Gateway is being executedfrom an unauthorized library or one or moreof the libraries in the STEPLIB concatenationis unauthorized.

Action: Ensure that the library the DB2 Gatewayexecutes from, and all the libraries in theSTEPLIB concatenation, are authorized.

S6BD2074IThe DB2 Gateway is running authorized

Source: DB2 Gateway

Explanation: The gateway is running inauthorized mode.

Action: None.

S6BD2075IThe DB2 Gateway is non-swappable

Source: DB2 Gateway

Explanation: The DB2 Gateway address space isnon-swappable.

Action: None.

S6BD2076IThe DB2 Gateway is swappable

Source: DB2 Gateway

Explanation: The DB2 Gateway address space isswappable. In a high volume system this candegrade performance.

Action: None.


184 |

S6BD2077IDB2 Release ; Level ;

Source: DB2 Gateway

Explanation: Shows the DB2 Release Level.

Action: None.

S6BD2078IDB2 Application Encoding Scheme is ;

Source: DB2 Gateway

Explanation: Shows the DB2 ApplicationEncoding Scheme found in DSNHDECP.

Action: None.

S6BD2079EUnable to use static sql: table=% module=% %

Source: DB2 Gateway

Explanation: The DB2 Gateway has failed to loadthe static SQL module for the table. There is ashort description as to why the modulecannot be loaded/used.

Action: Either disable static SQL for the table orcorrect the indicated module.

S6BD2099EGateway subtask ABNORMALLYTERMINATED: "%"

Source: DB2 Gateway

Explanation: The DB2 Gateway task abended.

Action: Previous messages may indicate thecause for the abend. Contact TIBCO Support.

S6BD2100IREQUEST: % % %

Source: DB2 Gateway

Explanation: The message is an echo of theObject Service Broker requests. It isdisplayed if DEBUG is on.


S6BD2401I% Gateway shutdown requested, reason="%"

Source: DB2 Gateway

Explanation: The gateway received a request toshut down from the TIBCO(r) Object ServiceBroker The description of the reason codesfollows:

• 0000 - TIBCO(r) Object Service Broker isshutting down.

• 0004 - A stopserver all*** was requested.All the gateways of this type will beterminated.

• 0008 - A stopserver gateway userid wasrequested. Only this gateway will beterminated.

• 0010 - The TIBCO(r) Object Service Brokerresource directory is full. Contact TIBCOSupport.

• 0014 - The maximum number of gatewayshas been exceeded. Increase theMAXDBMS parameter in the TIBCO(r)Data Object Broker and restart, or contactTIBCO Support.

• 00018 - The gateway anchor list hasoverflowed. Contact TIBCO Support.

Action: No further action is required.


| 185

EE: Execution Environment

S6BEE001ICompleted Activation of ExecutionEnvironment


Explanation: The Execution Environment hasbeen successfully activated.


S6BEE002ICompleted Deactivation of ExecutionEnvironment


Explanation: The Execution Environment hasbeen successfully deactivated.


S6BEE008EBinding area could not be created


Explanation: Binding area creation failed.

Action: Check the binding area parameters inclient defaults.

S6BEE009EThere was insufficient memory to create abinding area


Explanation: Binding area creation failed due toa shortage of memory.

Action: Try to kill some processes.

S6BEE010ECould not create shared memory


Explanation: Shared memory creation failed.


S6BEE011ECould not release existing binding area,because the shared memory segment is in use


Explanation: Failed to release existing bindingarea because it is being used.


S6BEE012EOS would not permit release existing bindingarea


Explanation: Release of existing binding areafailed.



186 |

S6BEE013ECould not remove locks for shared binding area


Explanation: Remove locks failed for sharedbinding area.


S6BEE014ECould not create locks for binding area


Explanation: Create locks failed for binding area.


S6BEE015IPeer servers started


Explanation: Peer gateways started.


S6BEE016I... data servers started


Explanation: The listed data gatewayssuccessfully started.


S6BEE017EData Server ... terminated because ...


Explanation: The indicated gatewaydisconnected for the given reason.

Action: See the log file for more details.

S6BEE020I... server ... started


Explanation: The Execution Environment starteda new peer or rules-based gateway.

Action: This message is generated duringExecution Environment initialization, whenpeers or rules-based gateways are defined forthe Execution Environment. No action needbe taken.

S6BEE021E... server ... connection lost, server likely failed


Explanation: The Execution Environment wasnotified that a peer or rule-based gatewayunexpectedly terminated. The gateway haslikely failed.

Action: Review the session message log for thegateway to determine the cause of the failureand take corrective action. The file name forthe log is determined by the gateway namedisplayed in the message. The path of the logfile for the gateway is defined by theExecution Environment defaults for thegateway type.


| 187

S6BEE022E... server ... failed because ...


Explanation: A peer or rules-based gateway hasfailed during initialization. The messagedisplays the cause of the error.

Action: Review the cause of the error and takecorrective action. Possibly more informationcan be found in the gateway's session log.The name of the log file is determined by thegateway name. The path of the log file isdetermined by the Execution Environmentdefaults for the gateway type.

S6BEE023I... server ... restarted


Explanation: The Execution Environment hasdetermined that a peer server rules-basedgateway has failed and should be restarted.

Action: Review the session log for thegateway/server to determine the cause of thefailure. The name of the file is determined bythe name of the gateway/server. The path ofthe log file is defined in the defaults for theExecution Environment for thegateway/server type.

S6BEE024I... server ... terminated normally


Explanation: The peer server or rules-basedgateway has terminated normally. It waslikely stopped through a Data Object Brokercommand.

Action: No action needs to be taken.


188 |

HM: Hawk Microagent

S6BHM001EOut of memory

Source: Hawk Microagent

Explanation: An internal memory allocationfailure occurred related to Hawk.

Action: Either run fewer processes on yoursystem or add memory.

S6BHM002EAMI ERROR: thread=%, code=%, text=%


Explanation: A Hawk Application ManagementInterface API call failed.


S6BHM003EAMI ERROR: thread=%, code=%, text=%,file=%, line=%


Explanation: A Hawk Application ManagementInterface API call failed and a file stamp hasbeen provided.


S6BHM004LAMI TRACE: level=%, id=%, text=%


Explanation: Hawk Application ManagementInterface API tracing has been enabled,resulting in this message.

Action: No action required. Disable tracing ifmessages of this kind are not desired.

S6BHM005LFailed to establish Hawk connection to daemon%, further attempts will be made every %milliseconds


Explanation: The internal Hawk microagentfailed to connect to the specified daemon.Further connection attempts will be made incase of temporary network problems.

Action: If after an extended time period aconnection cannot be established, review theparameters related to Hawk and ensure theyare correct. If the parameters are correct thencontact your network administrator.

S6BHM006LSuccessfully established Hawk connection todaemon %


Explanation: The internal Hawk microagent hassuccessfully connected to the specifieddaemon.



| 189

S6BHM007LUsing %


Explanation: This message is used to log versioninformation for the APIs used by the internalHawk microagent.


S6BHM008EBuffer of length % bytes supplied when % bytesneeded for %


Explanation: An internal buffer is not largeenough to completely hold message data tobe sent to Hawk.

Action: Reduce the length of the message text, orcontact TIBCO Support for assistance.

S6BHM009LDEBUG: thread=%, text=%


Explanation: Logging of debug information forthe Hawk microagent infrastructure has beenenabled, resulting in this message.

Action: No action required. Disable the loggingof debug information if messages of this kindare not desired.

S6BHM010EDynamic loader function '%' failed: %


Explanation: A failure occurred dynamicallyloading a module or resolving a symbolrelated to Hawk.


S6BHM011ESystem call '%' failed


Explanation: The specified operating system callfailed.


S6BHM012EUnexpected error


Explanation: An unexpected error occurredrelated to Hawk.


S6BHM013EWin32 call '%' failed


Explanation: A Win32 API call failed.



190 |

IC: IMS/DB Gateway

S6BIC000I@IMSTABLES definition error:

Source: IMS/DB Gateway

Explanation: @IMSTABLES is definedincorrectly.


S6BIC001I@IMSTABLES entry not found for table


Explanation: The IMS table was not correctlydefined to Object Service Broker.

Action: Check the IMS table definition andcontact TIBCO Support.

S6BIC002I@IMSDBS definition error:


Explanation: @IMSDBS is defined incorrectly.


S6BIC003I@IMSDBS entry not found for database


Explanation: The IMS database was not correctlydefined to Object Service Broker.

Action: Check the database definition and rerunthe extract utility.

S6BIC004I@IMSFIELDS definition error:


Explanation: @IMSFIELDS is not definedcorrectly.


S6BIC005I@IMSFIELDS table not found for table


Explanation: The IMS table is not definedcorrectly.

Action: Check the IMS table definition.

S6BIC006I@IMSSEGS definition error:


Explanation: @IMSSEGS is not defined correctly.


S6BIC007I@IMSSEGS table not found for database


Explanation: The IMS table is not definedcorrectly.



| 191

S6BIC008I@IMSSEGS entry not found for segment


Explanation: The IMS database is not definedcorrectly.

Action: Check the database definition, and ifnecessary, rerun the extract utility.

S6BIC009ICTABLE for IMS data too large for table


Explanation: The IMS table contains too manyfields.

Action: Reduce the number of fields in the IMStable definition and contact TIBCO Support.

S6BIC010INo IMS segments defined for table


Explanation: The IMS table is defined incorrectly.


S6BIC011I@IMSCONTROL contains null field name -table


Explanation: A value access field for the IMStable is incorrectly defined.

Action: Redefine the value access fields for thetable.

S6BIC012I@IMSDBD definition error:


Explanation: @IMSDBD is incorrectly defined.


S6BIC013I@IMSDBD table not found for database


Explanation: The IMS database is incorrectlydefined to Object Service Broker.

Action: Check the database definition, and ifnecessary, rerun the extract utility.

S6BIC014I@IMSDBD entry not found for IMS field


Explanation: The IMS database definition ismissing fields used as value access fields inthe IMS table.

Action: Verify the IMS database definition, and ifnecessary, rerun the extract utility.

S6BIC015INo fields defined for table


Explanation: The IMS table does not have anyfields defined.



192 |

S6BIC016ITDS CTABLE missing ITABLE field


Explanation: The IMS table is defined incorrectly.


S6BIC017ICTABLE segment data for IMS data missing atlevel %


Explanation: The IMS table or the associated IMSdatabase is incorrectly defined.

Action: Check the table and database definitions.

S6BIC018I@IMSFIELDS index page found for table


Explanation: A large number of IMS fields aredefined for the table, causing a data pagesplit in @IMSFIELDS.



| 193

ID: CA IDMS Gateway

S6BID000I%

Source: CA IDMS Gateway

Explanation: This is an informational messagethat is displayed in the gateway's job logwhen the DEBUG option is used in the inputcontrol parameters. It echoes request calls tothe CA-IDMS Gateway.


S6BID001ICA-IDMS Gateway initialization


Explanation: The external gateway is beginningits startup processing.


S6BID002IProcessing control input


Explanation: The external gateway startupprocess is processing the input controlparameters specified in the data setidentified by the DDNAME IDMSSRV0.


S6BID004IOpening a model port: %


Explanation: The CA-IDMS Gateway is openinga port by using the indicated model identifierto generate a communications port name.


S6BID005EOpen port failed


Explanation: The gateway communications portcannot be opened. Other messagesaccompany this message and provide morespecific information.

Action: Verify that the TDS and the MDLparameters are specified correctly in theinput control. Take action based on theaccompanying messages that contain morespecific information.

S6BID006IAttaching % gateway subtask(s)


Explanation: The indicated number of gatewaysubtasks are being started.



194 |

S6BID007ECA-IDMS Gateway subtask failed


Explanation: The attachment of a gatewaysubtask failed.

Action: Possible causes of failure are:

• The region size is too small

• S6BIDSRV is not linked properly

S6BID008EStart CIB not freed


Explanation: The console support setup failed.

Action: Check that the CA-IDMS Gateway isauthorized to use console support via theMODIFY command.

S6BID009IConsole support ready


Explanation: The operator commands for CA-IDMS as specified in the Accessing CA-IDMSData manual can be entered from theoperator console.


S6BID010IStorage POOLSIZE=%


Explanation: The external gateway for the CAIDMS database uses GETMAIN to get theinternal storage pool size. The size iscontrolled by the POOLSIZE parameter inthe input control parameters. The default is256KB.


S6BID011IINITIALIZATION COMPLETE


Explanation: The Object Service Broker CA-IDMS Gateway completed its initializationprocessing successfully and is ready forrequests.


S6BID012IConsole command REJECTED; Invalid syntax


Explanation: The MODIFY command enteredfrom the operator console has invalid syntax.

Action: Correct the syntax of the command andenter the command again.

S6BID013IConsole command ACCEPTED


Explanation: The MODIFY command enteredfrom the operator console was accepted andprocessed accordingly.



| 195

S6BID014IConsole command UNKNOWN


Explanation: The MODIFY command enteredfrom the operator console is invalid.

Action: For a description of a valid MODIFYcommand, see the Accessing CA-IDMS Datamanual.

S6BID015I% gateway(s) SHUTDOWN


Explanation: The percent sign (%) indicateswhich gateways were shut down with theMODIFY command from the operatorconsole.


S6BID016IGATEWAY STA USERID


Explanation: These are the headings formessages S6BID017I and S6BID018I.


S6BID017I% % %


Explanation: The gateway name and status aredisplayed as requested with the MODIFYcommand from the operator console.


S6BID018IMAX=% HWM=% ACT=%


Explanation: The percent signs (%) are replacedwith the maximum number of gatewaysallowed in the session, the High Water Markreached so far, and the number of gatewayscurrently active.


S6BID019ITIBCO(r) Object Service Brokercommunication CLOSED


Explanation: The communication port to theData Object Broker is closed. The shutdownis proceeding normally.


S6BID020ITIBCO(r) Object Service Broker requesthandler DELETED


Explanation: Communication routines weredeleted from memory. The shutdown isproceeding normally.


S6BID021ICA-IDMS interface module DELETED


Explanation: The module for the interface to theCA-IDMS database was removed frommemory. The shutdown is proceedingnormally.



196 |

S6BID022IFREEING storage


Explanation: The storage pool was freed.


S6BID023ICA-IDMS Gateway terminated


Explanation: The Gateway shut downsuccessfully.


S6BID026EGateway subtask ABNORMALLYTERMINATED> %


Explanation: An gateway subtask abnormallyterminated with the indicated abend code.

Action: Save all dumps and circumstances thatmight have caused the abend and contactTIBCO Support.

S6BID027E% connection to TIBCO(r) Object ServiceBroker failed


Explanation: The physical connection to the DataObject Broker failed.

Action: Correct the communications identifierspecified in the TDS parameter and activatethe Data Object Broker.

S6BID028EUnknown execution environment requestcode=%


Explanation: The internal request code sent fromthe Execution Environment is unknown tothe CA-IDMS Gateway.

Action: Check that the versions of the DataObject Broker, Execution Environment, andthe CA-IDMS Gateway are compatible.

S6BID029ICA-IDMS run unit was ACTIVE - ROLLBACKperformed


Explanation: A shutdown request was receivedwhile a transaction was active. AROLLBACK is performed.


S6BID030IPhy I/Os: % DB calls: % Recs rqst: %


Explanation: CA-IDMS statistics displayed attransaction end if DEBUG has been specifiedin the Object Service Broker CA-IDMSgateway startup parameters. Statistics areretrieved via the CA-IDMS ACCEPTSTATISTICS request.



| 197

S6BID032ICA-IDMS Gateway version %


Explanation: The current software version of theCA-IDMS Gateway is displayed.

Action: None.

S6BID033EMaximum number of tables allowed exceeded


Explanation: The maximum number of tablesyou are allowed to access in one transactionis 32. This limit has been exceeded.

Action: Divide the transaction into smaller units.

S6BID034ECA-IDMS ERROR status % RECORD %


Explanation: The indicated CA-IDMS errorstatus for the indicated record wasencountered.

Action: Check the CA-IDMS error messagemanual to determine the CA-IDMS errorstatus code.

S6BID035ECONVERSION ERROR on field % in record %DBKEY=%, %


Explanation: A data conversion error wasdetected while converting from CA-IDMS toObject Service Broker. The field name of thefield in error, the CA-IDMS record name, theDBKey of the CA-IDMS record and the causeof the error are contained in the message.

Action: Use the DBKey to view and possiblycorrect the field in error via a CA-IDMSproduct (e.g., DML/O). The DBKeydisplayed is a 4 byte binary field display indecimal. For example DBKEY=19205121converted to hexadecimal equals 1250C01where 1250C is the CA-IDMS page numberand 01 is the relative record number. Convert1250C to decimal and the DBKey for DML/Obecomes 75020-001.

S6BID036ESelection criteria specified invalid


Explanation: The CA-IDMS Gateway cannotdecipher the selection criteria for the tableaccessed.

Action: Correct the table selection and retry.

S6BID037EKey field not a field in table %


Explanation: The key field requested for the tableaccess was not located in the table definition.

Action: Check the table @IDMSFIELDS for theindicated field and regenerate the tabledefinition.


198 |

S6BID038ECONVERSION ERROR on field %: %


Explanation: The indicated error was detected bythe data conversion routine converting fromObject Service Broker to CA-IDMS.

Action: Verify that the table definition is correct,check for redefined fields in the tabledefinition, and check that the version of thesubschema definition loaded into ObjectService Broker is correct.

S6BID039ECA-IDMS server record I/O buffer full


Explanation: The I/O area used for CA-IDMSrecords is full.

Action: Restructure your transaction into smallerunits.

S6BID040EUnsupported GET or FORALL directive: %


Explanation: The GET or FORALL directivestored in the table @IDMSACCESS isunknown to the external gateway.

Action: Use the Table Definer to correct thedefinition of the Object Service Brokerexternal table for an CA-IDMS database andretry the transaction.

S6BID041EData Object Broker communication failure


Explanation: Internal error. A message sent to theData Object Broker failed because of acommunication error.

Action: Contact your network servicesdepartment to determine the cause of theerror.

S6BID043EInternal synchronization error


Explanation: An Internal logic error hasoccurred. Possible storage corruption in theObject Service Broker CA-IDMS Gateway.Review number of Object Service Brokertables and CA-IDMS records defined in thetransaction.


S6BID044ENecessary DBKEY fields not defined in table %


Explanation: CA-IDMS database keys areinternally attached to the external tabledefinition to provide proper replace anddelete processing.

Action: Check the table definition to ensure thatthe database definitions exist.


| 199

S6BID045E% record not defined in access path of table %


Explanation: Internal error. An internal recordpointer was corrupted.


S6BID046EINSERT failed. All elements not represented intable %


Explanation: To ensure data integrity, allELEMENTS for the lowest-level record in theaccess path must be defined in the tabledefinition to do the insertion.

Action: Verify that the table definition includesall the elements from the lowest-level record(excluding FILLER elements).

S6BID047ENested FORALL on a CA-IDMS table notallowed


Explanation: Due to CA-IDMS navigationalconstraints, nested FORALL statements onthe same table are not allowed.

Action: Change your Object Service Broker ruleto remove the nested FORALLs.

S6BID048ESelected field not found in table %


Explanation: The field specified in the selectionwas not found in the internal table definition.

Action: Regenerate the table definition and retry.

S6BID049EInternal selection evaluation error on table %


Explanation: The Object Service Broker selectionevaluator cannot decipher the selectioncriteria.

Action: Simplify the selection criteria.

S6BID050EError converting FIXED to EXPANDED formatfor table %


Explanation: An error was detected whenconverting from the CA-IDMS format to theinternal Object Service Broker format.

Action: Do one or both of the following:regenerate the table definition and/or reloadthe subschema definition.

S6BID051IConnecting % to TDS %


Explanation: This is an information messageindicating the Data Object Broker where thegateway is attached.


S6BID052IMaximum CTABLESIZE = %


Explanation: This is the maximum length of theinternal definition of a CA-IDMS table thatcan be passed to the gateway. The value isretrieved from the Data Object Broker startupparameter CTABLESIZE.



200 |

S6BID053ENo record in table % could be deleted


Explanation: No record in the table is qualified tobe deleted. The last record in an access paththat is an "Obtain CALC", "Obtain First inSet", or "Obtain First in Area" (see access pathdirectives) is the record that will be deleted.None of these directives can be found in theaccess path.

Action: Properly define the table.

S6BID054EDELETE where key =, Not valid for table %


Explanation: More than one record type makesup the table definition. A DELETE where thekey equals a value can only be specified fortables that have one record in the access path,and that record must be a CALC record.

Action: Use a qualified GET or optimizedFORALL processing to specify the recordyou want to delete.

S6BID055ESubschema % not found in dictionary %


Explanation: The specified subschema was notfound in the specified dictionary.

Action: Specify a valid subschema name.

S6BID056ENo DD statement found for %


Explanation: The specified DD name was notfound in the JCL.

Action: Specify all the necessary DD statements.

S6BID057EOpen error encountered for %


Explanation: The file cannot be opened.

Action: Check that the data set has all the validattributes (i.e., RECL, BLKSIZE).

S6BID058ESyntax error in request format


Explanation: The SYSIN statement has invalidsyntax.

Action: Correct the SYSIN statement andresubmit the job.

S6BID059EInsufficient storage available to start gateway %


Explanation: There is not enough storageavailable to GETMAIN the required storageareas.

Action: Make sure that the MODE statement inmember XLINKIDM in the job control libraryreads MODE AMODE(31),RMODE(ANY). IfRMODE is ANY specify a smaller POOLSIZE(i.e., 250 (the default)) and/or specify a largerregion size.


| 201

S6BID060EStorage pool initialization failed for %


Explanation: Initialization of the storage poolGETMAINed at gateway startup failed.

Action: Restart the gateway with a smallerPOOLSIZE (i.e., 250 (the default)).

S6BID061ESecurity profile STORAGE POOLINITIALIZATION failed


Explanation: Security profile STORAGE POOLINITIALIZATION failed. Initialization forthe storage pool GETMAINed to storesecurity profiles failed.

Action: Increase the region size of the gatewaystartup job and retry.

S6BID062EInsufficient space to store users security profile


Explanation: Insufficient space to store user'ssecurity profile.

Action: More than 1,000 different users havebeen signed on since the gateway wasrecycled. The very first time a user accesses agateway a security control block is stored.Subsequent accesses will use the storedcontrol block instead of recreating it everytime. Recycle the gateway to force aninitialize of the storage pool.

S6BID063ICA-ACF2 security INITIALIZATION DONE


Explanation: CA-ACF2 security storage poolinitialization has been completed.


S6BID064IACMCB built for user %


Explanation: ACMCB built for the specified user.

Action: Message indicating that a securitycontrol block has been created for thespecified user.

S6BID065EACMCB for % could not be built


Explanation: ACMCB for this userid could not bebuilt.

Action: The security profile control block couldnot be constructed. Check the indicated usersecurity access level.


202 |

S6BID066EThe CA-IDMS gateway must beAUTHORIZED to useEXTERNALSECURITY=ACF2


Explanation: The CA-IDMS Gateway must runfrom an authorized library in order to useCA-ACF2 security (i.e.,EXTERNALSECURITY=ACF2).

Action: Make sure the CA-IDMS Gateway is link-edited with SETCODE AC(1) and that thelibrary where the gateway resides is anauthorized library.

S6BID067EPARAMETER ERRORS FOUND... Gatewayterminated


Explanation: One or more parameters was foundto be in error.

Action: Correct the parameters in error andrestart the job.

S6BID068ECA-IDMS Gateway version mismatch


Explanation: The version number of the DataObject Broker does not match the version ofthe CA-IDMS Gateway.

Action: Review the installation procedure toensure that the proper version of the CA-IDMS Gateway is being executed.

S6BID069EParameter instance has changed... Requestdenied for table %


Explanation: The parameter value for a tablecannot change between a GET or a FORALLand a REPLACE.

Action: Correct the offending rule.

S6BID071ISort Key value exceeds work area size for table%


Explanation: The sort key selection provided inthe access statement was too large to fit in thegateway's work area.

Action: Decrease the size of the selectionspecified. Contact TIBCO Support.

S6BID072ELoad of the Fail Safe table % failed


Explanation: The Fail Safe table named@IDMFSTRXDB, or the table specified in theFSTABLENAME parameter, could not beloaded.

Action: Consult the Object Service Broker CA-IDMS Installation, Operations, and Usagemanual for an explanation of defining theFail Safe database to Object Service Broker.


| 203

S6BID073ECannot CONNECT % to % set


Explanation: The IDMS connect function couldnot be done for the indicated record and set.

Action: Verify that the IDMS set option ismanual.

S6BID074E%


Explanation: Message received from the Fail SafeCTABLE setup routine.

Action: Review the message content for a furtherexplanation of the error. Review the Fail Safeprocessing section of the Object ServiceBroker CA-IDMS manual.

S6BID075ETwo different views of record % detected


Explanation: The IDMS Gateway tried to bind arecord that had already been bound butfound it to have a different record length. Theprobable cause is that the subsequent tabledefinition uses a different subschema thanthe first of those that have a record viewdefined.

Action: Correct the offending table definition touse the correct subschema.

S6BID076EInsufficient storage available to store theCTABLE for %


Explanation: There was insufficient storageavailable to store the internal representationof the table being accessed (CTABLE).

Action: Increase the POOLSIZE parameter andrestart the gateway.

S6BID080E% DD statement not found


Explanation: Future use


S6BID081ESchema % Version % not found


Explanation: The CA-IDMS schema version forthe specified subschema could not be found.

Action: Verify the CA-IDMS data dictionarydefinition for the given subschema. Checkthat the dictionary or dbname specified iscorrect.


204 |

S6BID082IThe CA-IDMS Gateway is not runningauthorized


Explanation: The IDMS Gateway is beingexecuted from an unauthorized library orone or more of the libraries in the STEPLIBconcatenation is unauthorized.

Action: Ensure that the library the IDMSGateway executes from, and all the librariesin the STEPLIB concatenation, areauthorized.

S6BID083IThe CA-IDMS Gateway is running authorized


Explanation: The Gateway is running inauthorized mode.

Action: None.

S6BID084IThe CA-IDMS Gateway is non-swappable


Explanation: The IDMS Gateway address spaceis non-swappable.

Action: None.

S6BID085IThe CA-IDMS Gateway is swappable


Explanation: The IDMS Gateway address spaceis swappable. In a high volume system thiscan degrade performance.

Action: None.

S6BID086IMixed Subschema detected: RU using %, Table% defined with %


Explanation: A transaction has attempted toaccess two or more IDMS tables defined withdifferent subschemas. A transaction is onlyallowed to access one subschema and that isthe first subschema referenced. Accessingsubsequent tables could cause data to bemapped incorrectly.

Action: Review the application to ensure that thetables can be accessed with the subschemafirst referenced. Depending on theprocessing requirements you may wish tocode the IDMS gateway parameterMIXEDSSCDETECTION to define the actionthat should be taken for this condition whichinclude:

• I -ignore condition

• W -issue warning message and continue

• E -issue message and abort transaction

S6BID401I% Gateway shutdown requested, reason="%"







| 205






206 |

IM: IMS/DB Gateway

S6BIM100ETIBCO(r) Object Service Broker (%) is notavailable


Explanation: The gateway failed to connect tothe specified Data Object Broker.

Action: Ensure that the Data Object Broker is up.Ensure that the correct value is specified onthe TDS startup parameter.

S6BIM101EInvalid or missing DD card: "%"


Explanation: The specified DD card could not befound in the jobstep.

Action: Ensure the startup JCL contains thespecified DD card.

S6BIM102EFailed to open file: "%"


Explanation: An error occurred during theattempt to open the data set associated withthe specified DD card.

Action: Ensure the required data set is valid.

S6BIM103EStartup parameter format error: "%"


Explanation: An error occurred during theattempt to open the data set associated withthe specified DD card.

Action: Ensure the required data set is valid.

S6BIM104EInvalid value for startup parameter: "%"


Explanation: The specified startup parameterwas not supplied the correct value.

Action: Ensure the startup parameter has anallowed value.

S6BIM105ERequired startup parameter "%" was notsupplied


Explanation: One of the required startupparameters was not supplied.

Action: Ensure all the required startupparameters are supplied.

S6BIM106ESecurity parameters required withSECLEVEL=1


Explanation: If SECLEVEL=1, the IMS gatewayrequires more startup parameters in order tocorrectly define the security requirements.

Action: Specify one of the Resource/Classand/or DBDclass or Segclass.


| 207

S6BIM107EBoth CLASS and RESOURCE must be specified


Explanation: If SECLEVEL=1, the Resource mustbe coded if the Class is coded and vice versa.

Action: Ensure both Class and Resource havebeen coded.

S6BIM108ESupply only one of DBDCLASS or SEGCLASS


Explanation: If SECLEVEL=1, DBDclass andSegclass are mutually exclusive.

Action: Code only one of the DBDclass orSegclass, not both.

S6BIM109EBoth SEGCLASS and PSBNAME must besupplied


Explanation: If SECLEVEL=1, the PSBNAME isalso required if the Segclass is coded.

Action: Code the PSBNAME.

S6BIM110ENumber of records in IMSSEC00 exceeds themaximum allowed


Explanation: Maximum is 1000.

Action: Enter a number that is equal to or belowthe maximum.

S6BIM111EFailed to load PSB: "%"


Explanation: An attempt to load the specifiedPSBNAME as specified on the startupparameter failed.

Action: Ensure the specified PSBNAME is in//IMS DD DSN=IMS.PSBLIB.

S6BIM112IGateway "%" terminated


Explanation: The specified gateway isterminating.

Action: No action is required; part of shutdownprocessing.

S6BIM113I% % % %


Explanation: Echo gateway startup parameters.

Action: Ensure the startup parameters arecorrect.


208 |

S6BIM117ERequested gateway type cannot be "%"


Explanation: The Execution EnvironmentExternal Data Server initializer/terminatordoes not recognize the gateway type. Thismay occur due to a version mismatchbetween the external data gateway and theExecution Environment.

Action: Ensure that the external data gatewayand the TIBCO(r) Object Service Broker wereproperly installed. If the problem persists,contact TIBCO Support.

S6BIM119EFail Safe level 1 requires a valid TRXDB startupparameter


Explanation: TRXDB gateway startup parameterrequired with Fail Safe level 1.

Action: Specify a valid TRXDB value.

S6BIM130EStorage area initialization failed


Explanation: There may be a version mismatchbetween the different IMS Gateway modules.

Action: Contact your system administrator.

S6BIM131ENo database PCBs found in PSB: "%"


Explanation: The PSB used to start up thegateway did not contain any database PCBs.

Action: At least one DB PCB is required for agateway PSB.

S6BIM132EDefinition bind area initialization failed


Explanation: There may be a version mismatchbetween the different IMS Gateway modules.


S6BIM134EFailed to locate entry point for HDB2SRVR


Explanation: For the IM2 Gateway, this indicatesthat correct installation procedures were notfollowed, since the DB2 Gateway code wasnot linked in with the IMS Gateway code.

Action: Ensure the IMS Gateway installation wasdone correctly.

S6BIM135EFailed to initialize the DB2 portion of the IMSgateway


Explanation: There may be a version mismatchbetween the DB2 Gateway module and theIMS Gateway module.


S6BIM136EDB2 Gateway storage initialization failed


Explanation: Module mismatch for the IM2gateway.



| 209

S6BIM137EIMS PSB is not sensitive to Fail Safe IMS DBD:"%"


Explanation: No PCB for the specified DBDcould be found during FSLEVEL=1 gatewaystartup processing.

Action: If FSLEVEL=1 then PSB must containPCB for the Fail Safe database.

S6BIM138EOP02-"%" TIBCO(r) Object Service Brokerversion mismatch


Explanation: A mismatch of versions wasencountered.

Action: Contact your System Administrator.

S6BIM139IThe IMS Gateway is ready


Explanation: The IMS Gateway is ready toprocess requests.


S6BIM140IGateway session initialization started


Explanation: Initialization has started.


S6BIM141IIMS Gateway terminated


Explanation: The IMS Gateway has terminated.


S6BIM144ENo I/O PCB found in PSB: "%"


Explanation: The PSB used to start up thegateway did not contain an I/O PCB.

Action: Check whether CMPAT=YES is specifiedin PSBGEN statement for the gateway PSB.This is required because the gateway expectsthe first PCB to be an I/O PCB.

S6BIM150I% % %


Explanation: Echo Object Service Broker requestin the following format: gateway userid,tranid, type of request, and table name.


S6BIM151ETable definition required for: "%"


Explanation: IMS table definition not found inObject Service Broker.

Action: Check table name, supply definition ifrequired.


210 |

S6BIM152EGateway cannot store table definition for: "%"


Explanation: POOLSIZE startup parameter is toosmall to hold the requested number of tabledefinitions in this transaction.

Action: To rerun the transaction, the gatewaymust be shut down and restarted with alarger POOLSIZE value.

S6BIM153EUnsupported request: "%"


Explanation: The request issued to Object ServiceBroker is not supported.

Action: If not version mismatch, contact TIBCOSupport.

S6BIM154ESecurity information was not received


Explanation: Requires third-level support if notversion mismatch.


S6BIM155EBlank userid received


Explanation: Version mismatch.


S6BIM157EIdentification failed for: "%"


Explanation: SECLEVEL=1 and the ObjectService Broker session ID is not a valid useridas far as SAF is concerned (SECURITYFAIL).

Action: Ensure the Object Service Broker sessionID is defined externally (RACF, TSS, CA-ACF2).

S6BIM158EAccess Denied: UID(%) RESOURCE(%)CLASS(%)


Explanation: The Object Service Broker sessionID is not allowed access to the resource andclass (SECURITYFAIL).

Action: Ensure the session ID is correct.

S6BIM159EGateway received an invalid cursor





| 211

S6BIM160ECurrent Group value cannot be used as a userid


Explanation: Server startup parameterEXTERNALUSERID=GROUP was specified.In order for the gateway to use the currentgroup ID, the group ID must not exceed 8bytes in length.

Action: Make sure the current group value doesnot exceed 8 bytes if accessing the IMSgateway with SECLEVEL=1 andEXTERNALUSERID=GROUP.

S6BIM161EIdentification failed for "%", no decision couldbe made


Explanation: The gateway could not verify theObject Service Broker userid. The verificationfailed because SAF returned a SAF returncode of 4 indicating that the userid is notdefined to (RACF/ACF2/TSS/...) or thatSAF could not pass the request on to(RACF/ACF2/TSS/...). SECURITYFAIL willbe returned to the Object Service Broker usersession that initiated the request. Useridverification is done through the RACROUTEREQUEST=VERIFY call to SAF. % =userid||group.

Action: Make sure the gateway is using thecorrect userid group and the userid isdefined to the external security product(ACF2/TSS/RACF). Make sure the SAFrouter for the external security product isinstalled, including the correct SAFmaps andSAFprot record entries.

S6BIM162ENo security decision: "%" "%"


Explanation: The gateway could not verify theObject Service Broker userid access to aresource. The verification failed because SAFreturned a SAF return code of 4 indicatingthat the specified RESOURCE/CLASS is notdefined to (RACF/ACF2/TSS/...) or thatSAF could not pass the request on to(RACF/ACF2/TSS/...). SECURITYFAIL willbe returned to the Object Service Broker usersession that initiated the request. Resourceverification is done through the RACROUTEREQUEST=AUTH call to SAF.

Action: Make sure the gateway is using thecorrect userid group and the userid isdefined to the external security product(ACF2/TSS/RACF). Make sure the SAFrouter for the external security product isinstalled including the correct SAFmaps andSAFprot record entries.

S6BIM163EIMS PSBNAME "%" supplied is not valid


Explanation: The PSBNAME in the tabledefinition is not valid.

Action: Modify the table definition and resubmitthe request.


212 |

S6BIM167EScheduled "%" and requested "%" IMS PSBs donot match


Explanation: The gateway was started withTHREADUSAGE=TABLE and a transactionaccessed two tables with different PSBs.

Action: THREADUSAGE=TABLE says that allTABLES accessed in one transaction musthave the same PSB in their definition or havethe PSB not specified.

S6BIM168EDB2 PLAN "%" supplied is not valid


Explanation: The plan in the table definition isnot valid.

Action: Modify the table definition and resubmitthe request.

S6BIM169EScheduled "%" and requested "%" DB2 PLANsdo not match


Explanation: The gateway was started withTHREADUSAGE=TABLE and a transactionaccessed two tables with different PSBs.

Action: THREADUSAGE=TABLE says that alltables accessed in one transaction must havethe same PSB in their definition or have thePSB not specified.

S6BIM170IDEBUG: % CURSOR: % - % - % %


Explanation: Debug messages during optimizeupdate processing.


S6BIM173ENo IMS Database PCB available for: "%"


Explanation: Attempting to access an IMSdatabase for which no PCB was supplied inthe gateway startup PSB.

Action: Stop the gateway, add the PCB to thePSB, and restart the gateway with themodified PSB.

S6BIM174EUPDATE request sent to a read-only IMSgateway


Explanation: Mode=RO gateway received anupdate request from the TIBCO(r) ObjectService Broker.

Action: Do not attempt to update IMS data usinga read-only IMS Gateway.


| 213

S6BIM175EOverlapping IMS fields in table definition


Explanation: An attempt was made toinsert/replace a segment that had two ormore fields mapping parts of the segmenttwo or more times.

Action: Correct the definition so that the segmentbeing replaced/inserted does not haveoverlapping fields.

S6BIM176EIncomplete IMS segments in table definition


Explanation: An attempt was made to insert asegment that was not correctly mapped by anObject Service Broker IMS table, or a replacewas attempted using optimize update wherethe segment was not correctly defined.

Action: Correct the definition so that the segmentbeing replaced/inserted is correctly defined.You must ensure that fields do not overlap orupdates will be disallowed. The total lengthof the mapping fields must equal the DBDsegment size if dealing with fixed segmentsizes.

S6BIM177EInsert and secondary index access


Explanation: An attempt was made to insertusing secondary index access. This is notallowed in IMS.

Action: Change your access to a valid mode.

S6BIM178ECursor sequence error




S6BIM179EOptimize Update - message format




S6BIM180EOptimize Update - ordering not allowed


Explanation: Data access call had order onselection when using optimize update.

Action: Order processing is not supported withoptimize update access.

S6BIM181EOptimize Update - no record held


Explanation: REPLACE/DELETE was issuedwithout prior GET using optimize update.

Action: Prior to a REPLACE/DELETE you mustissue a GET/FORALL, if you are usingoptimize update.


214 |

S6BIM182EIMS Database PCB "%" is not sensitive tosegment "%"


Explanation: For SECLEVEL=1, the PSBspecified for the startup PSBNAME is notsensitive to the specified segment.

Action: Ensure the gateway PSB and startupPSBNAME are the same. If they are, makesure the PSB is sensitive to the desiredsegment.

S6BIM183ENon-unique segments can only be updatedusing optimize update


Explanation: Cannot replace/delete non-uniquesegments, if the table is not defined withoptimize update on.

Action: Set optimize update=Y in the tabledefinition in order to replace/delete non-unique segments.

S6BIM190ESecurity profile storage pool initializationfailed




S6BIM191EInsufficient space to store user security profile




S6BIM192EGateway PSB and security PSB (PSBNAME=)do not match


Explanation: The PSB used to start up thegateway must be equal to the value specifiedon the gateway startup parameterPSBNAME.

Action: Change the PSBNAME parameter andrestart the gateway.

S6BIM193ISecurity initialization: "%"


Explanation: Gateway security initialization isstarting.


S6BIM194IBuilding security profile for: "%"


Explanation: Security processing for userid.


S6BIM195IIdentification and verification for: "%"


Explanation: Security verification for userid.



| 215

S6BIM196ICheck Access: % % % %


Explanation: Security access check for userid,resource, class and type.


S6BIM197ICheck Access: UID(%) RESOURCE(%)CLASS(%) TYPE(%)


Explanation: Security access check for userid,resource, class and type.


S6BIM210IDL/I (%) CALL; STATUS CODE (%)


Explanation: The call to access DL/I data did notcomplete successfully.


• If the STATUS CODE is not blank, thenlook up the STATUS CODE in the IMSmessages and codes/applicationdevelopers guide and take appropriateaction.

S6BIM211IDL/I (%) CALL; STATUS CODE (%); DBNAME(%)





S6BIM212EGateway I/O area overflow on DL/I call "%"using DBD "%"


Explanation: The returned amount of data fromthe indicated DL/I call for the indicated IMSdatabase exceeds the gateway's I/O area.

Action: The gateway's I/O area is 32 KB. If thereturned amount of data should not haveexceeded this size then a version mismatchmay have occurred.

S6BIM213EGateway installation exit error


Explanation: IMSUSRXT coded by customerfailed a request.


S6BIM214EInsert loop failed


Explanation: Attempt to insert multiplesegments has failed.

Action: A DL/I trace is required.


216 |

S6BIM215EREPL/ISRT/DLET loop failed. Maximum SSAcount reached




S6BIM217EFailed to identify S6BDRSSR as "%" reason: "%"


Explanation: The IM2 gateway running underthe Execution Environment using the BMPinterface requires that the program name beused as the PLAN name when connecting toDB2. Since the gateway's program name willalways be S6BDRSSR, then prior to invokingDFSRRC00, program S6BDRSSR is identifiedto z/OS as the requested DB2 PLAN name.On this occasion the identification failed.

Action: The REASON is the return code from theIDENTIFY macro instruction.

S6BIM220EConversion error: IMS to internal, field: "%"


Explanation: Converting IMS data to ObjectService Broker data has failed for theindicated Object Service Broker field name.Convert2 message will follow.

Action: Make sure the IMS database containsdata that matches the external syntax asdefined for the Object Service Broker IMStable.

S6BIM221IDL/I (%) CALL; STATUS CODE (%); DBNAME(%) PSB (%) RC(%) USING (%) SEGMENT(;,;,;)




• If the STATUS CODE is not blank, look upthe STATUS CODE in the IMS messagesand codes/application developers guideand take appropriate action.

• If the STATUS CODE is blank, then the RCvalue may contain more information:

• RC(TIMEOUT) - The call failed tocomplete within the DLITIMEOUT=value specified at gateway startup.The gateway task has terminated andany updates to DL/I should have beenrolled back depending on the interfaceto DL/I being usedUSING(DLI/DBB/BMP/CICS).

• RC(Q-LIMIT) - The number of DL/IGU/GN/ calls since the lastCHKP/ROLB exceeds theDLIQUERYLIMIT value specified atstartup.

• RC(U-LIMIT) - The number of DL/IGHU/GHN/ISRT calls since the lastCHKP/ROLB exceeds theDLIUPDATELIMIT value specified atstartup.

• If USING(CICS), the last four (4) hexdigits of the RC contain the CICS-DL/IUser Interface Block (UIB) ReturnCodes.


| 217

S6BIM222IDL/I (%) CALL; STATUS CODE (%); PSB (%)RC(%) USING (%)




• If the STATUS CODE is not blank, look upthe STATUS CODE in the IMS messagesand codes/application developers guideand take appropriate action:

• If the STATUS CODE is blank, then the RCvalue may contain more information.



S6BIM223IDL/I (;) CALL;; STATUS CODE (;);; DBNAME(;) PSB (;) RC(;) USING (;)





• If the STATUS CODE is blank, then the RCvalue may contain more information.


• RC(Q-LIMIT) - The number of DL/IGU/GN/ calls since the lastCHKP/ROLB exceeds theDLIQUERYLIMIT value specified atstartup.

• RC(U-LIMIT) - The number of DL/IGHU/GHN/ISRT calls since the lastCHKP/ROLB exceeds theDLIUPDATELIMIT value specified atstartup.


S6BIM250EGateway DL/I call limit exceeded: DL/I unit ofwork has been rolled back


Explanation: One of DLIQUERYLIMIT orDLIUPDATELIMIT was exceeded in aprevious call. The gateway notified the callerof this but the caller did not request a CHKPor ROLB which are the only two allowedactions after a call limit has been exceeded.The gateway rolled back the current DL/Iunit of work.

Action: Change the application so that on a Q-LIMIT or U-LIMIT from IMS Gateway does acommit/rollback.


218 |

S6BIM261EError building IMS segments: value was notreceived for data parameter: "%"


Explanation: Error occurred in IMSRECprocessing.`

Action: Ensure the table definitions match theIMS database definition. If the definitionsmatch, contact TIBCO Support.

S6BIM262EError building IMS segments: table definitiondoes not contain segment: "%"


Explanation: Error occurred in IMSRECprocessing.


S6BIM263EError building IMS segments: table definitioncontains invalid segment entries




S6BIM264EError building IMS segments: maximum fieldsize exceeded for: "%"




S6BIM265EError building IMS segments: SSA segmentpointers do not match table definition




S6BIM266EError building IMS segments: conversion,internal to IMS, field: "%"



Action: Ensure the table definitions match theIMS databases definition. If the definitionsmatch, contact TIBCO Support.


| 219

S6BIM271EError building SSA: no key provided for Delete


Explanation: Error occurred in IMSSSAprocessing.


S6BIM272EError building SSA: no row received




S6BIM273EError building SSA: select error



Action: Ensure that table definitions match theIMS database definition. If the definitionsmatch, contact TIBCO Support.

S6BIM274EError building SSA: maximum field sizeexceeded




S6BIM275EError building SSA: invalid M1 request




S6BIM276EError building SSA: SSA overflow




S6BIM277EError building SSA: conversion, internal toIMS, field: "%"




S6BIM278EError building SSA: unsupported request





220 |

S6BIM280EIMSROW - table search error


Explanation: Version mismatch

Action: Contact your System Administrator

S6BIM281ERow selection error


Explanation: Bad return code from selecnam.Possible definition error.

Action: Ensure selection criteria matchesdefinition. If it does not match, contact yourSystem Administrator.

S6BIM282E%


Explanation: A message returned from the DataObject Broker at startup indicating thespecific failure when trying to retrieve theFail Safe table definition.

Action: As of release 3.0 PUT05 the@IMSFSTRXDB Fail Safe table definition isrequired to be defined in each Data ObjectBroker that is using FSLEVEL=1.

S6BIM283ELoad of the Fail Safe table % failed


Explanation: The Fail Safe table named in themessage could not be found.

Action: The @IMSFSTRXDB Fail Safe tabledefinition is required to be defined in eachData Object Broker that is using FSLEVEL=1.

S6BIM301EDFSPZP; module not found


Explanation: The IMS DRA start up parametertable could not be found in the IMS gatewaysteplib.

Action: Check that a valid DRASUFFIX has beenspecified in the IMS gateway start upparameters.

S6BIM302EPAPLRETC # returned from the DRA interface


Explanation: A non zero return code wasreturned from IMS DRA.

Action: See the current IMS Messages and CodesIBM manual for a possible explanation of thereturn code value.

S6BIM303IIMS/DRA Initialization complete


Explanation: The IMS DRA interface has beensuccessfully initialized.


S6BIM304IIMS/DRA Interface terminated


Explanation: The IMS DRA interface has beensuccessfully terminated.



| 221

S6BIM305IIMS/DRA Control exit entered. PAPLFUNC=#,PAPLSFNC=#


Explanation: The IMS DRA control exit has beenentered for the reason specified byPAPLFUNC and PAPLSFNC.

Action: For an explanation of the PAPLFUNCand PAPLSFNC, see the current IMSCustomization Guide.

S6BIM306IDBCTL % identified to DRA


Explanation: This message shows the IMSDBCTL name to which the IMS gateway isattached.


S6BIM307EIMS System abend code # detected


Explanation: An abnormal IMS system abendhas been detected.

Action: See the current IMS Messages and CodesIBM manual for an explanation of the Systemabend codes.

S6BIM308EIMS User abend code # detected


Explanation: An IMS DRA user abend code hasbeen detected.

Action: See the current IMS Messages and CodesIBM manual for an explanation of IMS Userabend codes.

S6BIM309IProceeding with DRA termination


Explanation: A message indicating that the IMSServer termination is proceeding.


S6BIM310EPAPLFUNC=# code not handled


Explanation: The function code indicated is notvalid.

Action: Possible IMS DRA versus IMS Gatewayversion mismatch.

S6BIM311EIMS/DRA failure: % Reason: %


Explanation: A severe IMS DRA failure hasoccurred.

Action: See the current IMS Messages and CodesIBM manual for an explanation of possiblefailure.

S6BIM312IStarting IMS/DRA Initialization


Explanation: Information message indicatingthat the IMS/DRA interface initialization hasstarted.



222 |

S6BIM313EDRA Startup/Router routine (DFSPRRC0) notfound


Explanation: DFSPRRC0 could not be found inthe STEPLIB

Action: Make sure DFSPRRC0 is in one of thedata sets in the STEPLIB concatenation.Either copy it from the IMS.RESLIB library orinclude IMS.RESLIB in the STEPLIBconcatenation

S6BIM401I% Gateway shutdown requested, reason="%"











| 223

JX: Journal Extract

S6BJX001ICOUNT = ________

Source: Journal Extract

Explanation: Upon completion of the Journalextract, the count message is displayed toindicate the number of Journal recordsprocessed.


S6BJX002EVSAM ERROR RC=__ FB=__ RBA=


Explanation: When attempting to read theJournal, VSAM detected an error as indicatedby the return code and the feedbackinformation provided in the message. Theerror itself occurred when processing therecord at the RBA specified in the message.

Action: Refer to the VSAM message manual forerror identification.

S6BJX003EJOURNAL NOT PREFORMATTED


Explanation: When the Journal data set wasopened, the VSAM catalog indicated that thedata set was not properly formatted.

Action: Format the Journal using S6BTLFJR andthen resubmit the program that failed.

S6BJX004EJOURNAL OPEN ERROR


Explanation: When attempting to open theJournal data set, VSAM reported an error.

Action: View the SYSLOG for more information.

S6BJX005EJOURNAL CI SIZE TOO SMALL


Explanation: When processing the Journal, it wasdetermined that the control interval size (CI)is not valid for a Journal data set.

Action: Ensure that your JCL is correct andresubmit it. If your JCL is correct, contactTIBCO Support.

S6BJX006EBACKUP OPEN FAILED


Explanation: When processing the backupJournal to determine the type (VSAM orsequential), an error was detected by theoperating system.

Action: Ensure that your JCL is correct andresubmit it. If your JCL is correct, contactTIBCO Support.


224 |

S6BJX007EVSAM OUTPUT ERROR ON BACKUP


Explanation: When attempting to add a record tothe VSAM backup Journal, an error wasdetected.


S6BJX008EWRITE ERROR ON ERASING JOURNAL


Explanation: When attempting to clear the firstrecord on a Journal to indicate its data hasbeen extracted, VSAM detected a write error.


S6BJX010WBACKUP CANCELLED VIA DD DUMMYSPECIFICATION


Explanation: When the module was examiningthe backup data set, it detected that the dataset was set to "dummy", which indicates thatthe backup is not required. To saveprocessing, the Journal extract is notinvoked. The Journal is simply re-initializedso it can be reused.


S6BJX011ES6BSPCXO ERROR R15=X"XXXXXXXX"


Explanation: The optional compressionprocessing was selected for the journaloffload utility (using the COMPRESSparameter for S6BSPJEX). When the user-supplied compression exit was called forinitialization processing, it returned with acompletion code greater than 4.

Action: Review the user-supplied compressionexit.

S6BJX012WCOMPRESSION DISABLED BY S6BSPCXO


Explanation: The optional compressionprocessing was selected for the journaloffload utility (using the COMPRESSparameter for S6BSPJEX). When the user-supplied compression exit was called forinitialization processing, it returned with acompletion code of 4 indicating compressionshould be disabled.

Action: Review the user-supplied exit todetermine why it indicated the compressionprocessing should be disabled.

S6BJX013ES6BSPCXR ERROR R15=X"________"


Explanation: The user-supplied compression exitreturned control to the S6BSPJEX (JournalOffload) utility with a completion code thatwas greater then 4 or less than zero.

Action: Review the user-supplied compressionexit to determine the cause of the errorcondition code.


| 225

S6BJX014EBUFFER CONTROL ERROR DETECTED,SPIN TERMINATED


Explanation: When processing the journal in theS6BSPJEX (Journal Offload) utility, aninternal control error was detected.



226 |

KA: DOB Query Task

S6BKA002WFREE LOCKS FAILED

Source: DOB Query Task

Explanation: During a transaction cleanup, theattempt to free logical locks failed.


S6BKA003WFREE LOCK REQUEST BUFFER FAILED


Explanation: During a transaction cleanup, theattempt to free the lock buffer failed. ObjectService Broker processing continues.


S6BKA004EUNDEFINED EVENT CODE X'____'


Explanation: Object Service Broker logic error.The Query supervisor detected a physicalevent for which it does not have a serviceroutine. The request is ignored. ObjectService Broker processing continues.


S6BKA005WINVALID TDS REQUEST


Explanation: Object Service Broker protocolerror. The Query supervisor received aninvalid request for service. The offendingtransaction is aborted.


S6BKA006WDATA ERROR - NOT PAGE REQUESTED


Explanation: The page passed was not the pagerequested.


S6BKA007WINVALID RETURN CODE FROM PAGELOOKUP


Explanation: During Resident Page Lookup, anunexpected return code was returned by thelookup service routine.


S6BKA008WINVALID TDS REQUEST CODE


Explanation: An invalid request code wasreceived from TDS.



| 227

S6BKA009WUSER GONE - UNEXPECTED LOGOFF


Explanation: Object Service Broker tried tocommunicate back to the user, but the userwas not there.


S6BKA010EUSER CANCELLED OR FORCED,TRANSACTION TERMINATED


Explanation: During the processing of a servicerequest it was detected that a user connectionhad been cancelled or forced via theOperator/Administrator.

Action: The transaction in progress is abnormallyterminated to allow the system to invokesession cleanup.

S6BKA011WINVALID PAGE REQUESTED


Explanation: The page requested is not in theextents that are available to the user.


S6BKA012WILLEGAL PAGE HOLD


Explanation: Object Service Broker protocolerror. A Query transaction attempted toretrieve a page for update.


S6BKA013WHOLDING TOO MANY BUFFERS


Explanation: A query transaction requestedmore working set storage than allowedinternally. The assumption is that thetransaction might be looping. The offendingtransaction is aborted. Object Service Brokercontinues processing.


S6BKA014WPAGE POOL BUFFER ERROR


Explanation: Internal system error. An erroroccurred during an attempt to get a pagepool buffer.


S6BKA015WINVALID FREE 4K ADDRESS


Explanation: Object Service Broker attempted tofree a buffer at an invalid address.



228 |

S6BKA016WPAGE POOL BUFFER ERROR ON FREE


Explanation: Query transaction cleanupencountered an error in returning transientstorage to the system. Processing continues,possibly with the loss of working set storage.Statistics are available on BUFFER pooloperations. Object Service Broker processingcontinues.


S6BKA017WLOCK BUFFER ERROR


Explanation: A request was made to the lockmanager, but the request failed.


S6BKA018WUNLOCK REQUEST IN ERROR


Explanation: An unlock request to the lockmanager failed.


S6BKA019WLOCK INTERFERENCE


Explanation: Object Service Broker protocolerror. The Execution Environment tried tostart a new transaction without terminatingthe current transaction that is using thisstream. Logical resources remain locked bythe previous transaction.

Action: No action required. The user may have tolog off to re-synchronize the session.

S6BKA020WFILE UPDATES NOT ALLOWED IN PHASE 1


Explanation: Object Service Broker protocolerror. A QUERY transaction attempted toupdate a page. The transaction is aborted.


S6BKA021WNO FREE CTABLE SLOTS


Explanation: This is a transient buffer shortageproblem. All resident CTABLE build areasare currently in use. The transaction isaborted.

Action: The number of resident CTABLEs is aninvocation parameter (CTABRESIDENT) tothe Data Object Broker. Review theInstallation and Operations manual fordetails. Contact the Object Service Brokersystem administrator to configure ObjectService Broker to meet the requirements of aparticular workload.


| 229

S6BKA022WINVALID TABLE NAME ON CTABLEREQUEST


Explanation: Object Service Broker protocolerror. The table name specified in an internalaccess method request contains invalidcharacters. The transaction is aborted.

Action: Contact the Object Service Broker SystemAdministrator. Ensure that the Object ServiceBroker versions for both user and DataObject Broker are identical.

S6BKA024WBUFFER NOT AVAILABLE TO SUPPORTPAGE RETRIEVAL REQUEST


Explanation: When the Data Object Brokerattempted to obtain a buffer to store a pageimage, the buffer was not available.

Action: This should be a temporary condition;retry the transaction.

S6BKA026WXTAB POOL BUFFER ERROR ON FREE


Explanation: Object Service Broker internal logicerror. A transient work area cannot bereturned to its buffer pool. Object ServiceBroker processing continues, perhaps withdegraded resources.


S6BKA027WXTAB POOL BUFFER ERROR ON GET(SESSION LIMIT?)


Explanation: The Query supervisor failed toacquire a transient work area. Thetransaction is aborted.

Action: If the situation persists, ensure that theactual number of concurrent users isaccurately reflected in the Object ServiceBroker startup parameters. Contact theObject Service Broker system administratorto configure Object Service Broker to matchthe expected workload. Refer to theInstallation and Operations manual fordetails.

S6BKA030WNO STORAGE FOR CTABLE POOL


Explanation: During Object Service Brokerstartup, insufficient storage was available toprovide the concurrent resource pools asconfigured.

Action: Review the Installation and Operationsmanual and ensure that Object ServiceBroker is running with an appropriate jobclass and region size.


230 |

S6BKA031ESTORAGE NOT AVAILABLE FOR LOCKMANAGER WORK AREAS


Explanation: There was not sufficient virtualstorage available during Data Object Brokerinitialization for the allocation of LockManager work areas.

Action: Increase the amount of virtual storageavailable and restart the Data Object Broker.

S6BKA033IAPPL INITIALIZATION OK


Explanation: The Query supervisor initializedsuccessfully during the startup of the DataObject Broker.


S6BKA034WFREE PAGE BUFFER SERVICE FAILUREDETECTED


Explanation: When an attempt to release apreviously obtain buffer, an error occurred.


S6BKA035WTRANSACTION ABORTED - LOCK BUFFERMEMORY LIMIT


Explanation: The Object Service Broker lockmanager ran out of LOCK BUFFER POOLmemory during the last request. Thetransaction is aborted.


S6BKA036WCENTRAL SERVER ERROR DETECTED INTRANSACTION PROCESSING


Explanation: An abend was detected during theprocessing of a transaction by the QueryProcessor. The Query Processor was able torecover from the abend; however, thetransaction which was being processed at thetime of the abend was aborted.

Action: Retain the Job Log for the Data ObjectBroker, and contact TIBCO Support.

S6BKA037WREAD REQUEST REJECTED, SEGMENTOFFLINE REQUEST IN PROGRESS


Explanation: A Page read request has attempt toobtain a page that is resident on a segmentthat is in the process of being taken offline.

Action: The page request is failed.

S6BKA038ECTABLE BUILD FAILED, SEGMENTOFFLINE REQUEST IN PROGRESS


Explanation: When attempting to build aCTABLE (table definition block) it wasdetermined that segment on which the tableresides is currently in process of being takenoffline.

Action: The request is terminated.


| 231

S6BKA039WLOGICAL LOCK PROCESSING ERRORDETECTED


Explanation: The routine that manages logicallocking of table instances responded with areturn code that was out of range.


S6BKA040ECTABLE CHAINING ERROR: SESSIONQUEUE POINTER INCORRECT, DUMPGENERATION REQUESTED


Explanation: An internal CTABLE managementerror was detected in the chains of sessionswaiting for the completion of the CTABLE(table definition block) build.

Action: The Data Object Broker generates an SVCdump in order to provide diagnostics. Thisdump should be packaged and included inan incident report. After the dumpgeneration is complete the Data ObjectBroker processes through all the sessioncontrol blocks in order to reconstruct thechain and then continues processing.

S6BKA041ECTABLE CHAINING ERROR, SESSIONQUEUE POINTER INCORRECT, DUMPGENERATION REQUESTED


Explanation: While processing a CTABLE (tabledefinition block) request the internalCTABLE Managements service detected anerror in the pointer/chain processing.

Action: The Data Object Broker reports the error,generates a dump, and then abends with aUser 402 abend.

S6BKA042EINVALID RETURN CODE FROM SERVICEROUTINE, DUMP GENERATIONREQUESTED.


Explanation: When control returned from a DataObject Broker service routine the return codewas found to be outside the expected range.

Action: The Data Object Broker requests thegeneration of a dump and then terminateswith a User 404 abend.

S6BKA043ECTABLE REFERENCE COUNT FORCED TOZERO, DUMP GENERATION REQUESTED


Explanation: The CTABLE (table definitionblock) Manager detected a negative referencecount when updating the current number ofsessions accessing the CTABLE.

Action: After the message a DIB Dump will berequested and the Data Object Brokerterminates with a User 404 abend.


232 |

KC: DOB Communication Task

S6BKC000Iexplanation of return/reason code forconnection failure

Source: DOB Communication Task

Explanation: When a connection to a Data ObjectBroker fails, the error message displayedmay contain a return code or a reason code inthe "sense data" field. Some of the codesrequire the user to correct a setting and thenretry; others represent severe problems overwhich the user has no control.

Other error messages reference this messagefor the descriptions of these codes.

The following are the return/reason codes:

• 08 - Logic Errors

• 00 - Compatibility code not passed inconnect parameters. Coding error.

• 04 - Compatibility-level error,Execution Environment notcompatible. Attempting to connect to aData Object Broker that is at a differentrelease level.

• 08 - Connection type parameter notsupplied (RGNTYPE=). Coding error.

• 0C - USERID parameter not supplied.Coding error.

• 10 - Connection type value is notsupported. Coding error.

• 14 - Fail Safe level 1 required.Attempting to connect to a Data ObjectBroker that requires at least Fail Safelevel-1 (contingent commit) supportwith a gateway/server or Data Object

Broker that supports only Fail Safelevel 0 (serial commit).

• 18 - Server type/ID not specified (specblock too small). Coding error.

• 1C - TAM Server rejected, combinedExecution Environment not specified.The remote peer server requires twoconnections: an ExecutionEnvironment and a server. During theattempt to connect the rule server, theExecution Environment to which itwas to be coupled could not be found.

• 20 - Fail Safe level 2 required.Attempting to connect to a Data ObjectBroker that requires at least Fail Safelevel-1 (contingent commit) supportwith a gateway/server or Data ObjectBroker that supports only Fail Safelevel 0 (serial commit).

• 24 - Server type not specified. Codingerror.

• 28 - Userid is invalid. Either the passeduserid is blank or you are attemptingto use a superseded version ofS6BBRULH.

• 2C - Server path ID not specified.Coding error.

• 30 - Registration characteristicsdifferent than configured. Thecharacteristics specified in the pathmanagement system do not matchthose supplied in the connection list.

• 34 - Expected associated connectionnot found. Some gateways require twoconnections: an ExecutionEnvironment and a gateway. During


| 233

the attempt to connect the gateway,the Execution Environment to which itwas to be coupled could not be found.

• 38 - Specified associated userid isduplicated. Some gateways requiretwo connections: an ExecutionEnvironment and a gateway. Duringthe attempt to connect the gateway, asearch of the user list determined thatthe target Execution Environmentuserid was used in more than oneconnection. Therefore it could not bedetermined which one wasappropriate.

• 0C - Environmental Restrictions

• 00 - Data Object Broker is notaccepting logons. The Data ObjectBroker is currently in a status thatprevents the acceptance ofconnections.

• 04 - Storage not available to supportconnection. Each connection to theData Object Broker requires a block ofprivate space. The pool containing thespace is currently completelyallocated.

• 08 - Connections currently restricted tooperators. The Data Object Broker iscurrently in a status that prevents theacceptance of connections other thanoperator sessions (IR ADMIN CLIST).

• OC - Batch connections are not beingaccepted. The Data Object Broker iscurrently in a status that prevents theacceptance of connections from batchjobs.

• 10 - User/Server already logged on.The userid specified in the connectionis the same as an existing connection.

• 14 - Maximum ExecutionEnvironments limit exceeded. Thenumber of Execution Environments

has reached the defined limit(usermax).

• 18 - An inbound connection from aData Object Broker is not predefinedto the resource management facility.

• 1C - Logon is rejected because thesystem is quiesced.

• 20 - An external DBMS gateway is notdefined to the resource managementfacility.

• 24 - EXTN resource limits already atmaximum for path.

• 28 - Connections only accepted via aMessage Switch address space

• 2C - Reserved, not currently active.

• 30 - Reserved, not currently active.

• 34 - Nonzero alert pointer.

• 38 - DXE chaining not supported.

• 3C - Wild card resource exceedsdefined resource limit.

Action: Based on the return and reason codes, doone of the following:

• 08

• 00 - Contact TIBCO Support.

• 04 - Use the same release-level librariesfor the Data Object Broker and theitem attempting to connect to it.


• 0C - Contact TIBCO Support.


• 14 - No longer supported.


• 1C - Try to determine if the ExecutionEnvironment failed, and then contactTIBCO Support.

• 20 - No longer supported.



234 |


• 2C - Specify the gateway path ID.

• 30 - Check the joblog for a S6BKC081message, which will identify thecharacteristics that were specified withthe connection. Adjust the connectionrequest or the path management so thecharacteristics match.

• 34 - Try to determine if the ExecutionEnvironment failed, and then contactTIBCO Support.

• 38 - Try to eliminate duplicateExecution Engine userids. If this doesnot work, contact TIBCO Support.

• 0C

• 00 - Wait for the condition to clear andtry again later - the Data Object Brokeris not accepting logon requests at thistime, check the log for outstandingerror conditions.

• 04 - Try again later or increase theMAXUSERS parameter.

• 08 - Wait for the condition to clear andtry again later - the Data Object Brokeris only accepting logon requests foradministration sessions.

• 0C - Wait for the condition to clear andtry again later - the Data Object Brokeris not accepting logon requests forbatch sessions at this time. Check thelog for outstanding error conditions.

• 10 - Try to determine why the useridsare duplicated or retry the connectionwith a different userid.

• 14 - Execution Environment sessionlimit reached, retry later or increasethe USERMAX limit.

• 18 - Define the incoming Data ObjectBroker via the Administrator ResourceManagement function.

• 1C - Check the joblog for outstandingjournal spins and try again later.

• 20 - Define the required gateway viathe Administrator ResourceManagement Facility.

• 24 - Increase the schedule limits orretry the connection later (see theAdministrator Resource ManagementFacility).

• 28 - Modify the connecting session toconnect to a Message Switch addressspace.

• 2C - No action is required.

• 30 - No action is required.



• 3C - Increase the MAXRESOURCESData Object Broker parameter.

S6BKC001EINVALID PEER COMMID SPECIFIED FORPEERCANCEL REQUEST, REQUESTIGNORED


Explanation: An invalid PEERCANCELcommand was issued. The COMMIDspecified in the console command is notdefined to the Resource Manager.

Action: Reissue the PEERCANCEL commandwith a valid peer identifier.


| 235

S6BKC002WINBOUND PEER CONNECTION REJECTEDDUE TO DUPLICATE USERID, &, HIN &


Explanation: The message identifies the useridand source of an inbound peer connectionthat has been prevented from logging on tothe Data Object Broker. Peer connectionsmust have a unique userid, whether or notthe DUPUSERID parameter has been coded.The peer connection has not beenestablished.

Action: Determine why a duplicate userid wasgenerated by the remote peer and correct thesituation.

The duplicate userid may be the result of aconfiguration error, such as multiple DataObject Brokers using the same userid prefix.In this case, correct the configuration andrestart the HRN connections from the remoteData Object Broker.

S6BKC003WSVC DUMP GENERATED VIA THEADMINISTRATOR UTILITY


Explanation: An SVC dump of the Data ObjectBroker was requested via the AdministratorDiagnostics Dumps feature.


S6BKC004ESEVERE SESSION LIMIT MANAGEMENTERROR DETECTED, DUMP REQUESTED-INCR


Explanation: During the process used to controllicensed limits, the internal bitmap maskswere not set. This error indicates a problemwith the licensing process that is beyond thecontrol of the site.

Action: A system dump is generated. Pleaseforward the dump and the Data ObjectBroker and Native Execution Environmentjoblogs to TIBCO Support.

S6BKC005ESEVERE SESSION LIMIT MANAGEMENTERROR DETECTED, DUMP REQUESTED-DECR


Explanation: During the processing of licensedlimits, the in-use count was decrementedwhen it was already zero. This is an internalcontrol error that is beyond the control of thesite.

Action: A system dump is generated. Pleaseforward the dump and the Data ObjectBroker and Native Execution Environmentjoblogs to TIBCO Support for analysis.


236 |

S6BKC007WRESOURCE MANAGEMENT ERRORDETECTED, DIAGNOSTIC DUMPREQUESTED, PROCESSING CONTINUES


Explanation: During the processing of agateway/server logoff action, it was detectedthat a pointer in the gateway/server's controlblock was pointing to an invalid association.

Action: As a result of the error, a diagnosticsdump will be requested, the invalid pointerwill be cleared and processing will continue.The diagnostics dump generated should beforwarded to TIBCO Support.

S6BKC008WUSER CONNECTION CANCELLED DUE TOENDSERVER PROCESSING - USER=_____


Explanation: An external resource utilized by thein-flight transaction has terminated. In orderto avoid potential integrity issues theassociated user session was cancelled.

Action: The user can reconnect at theirconvenience.

S6BKC013ANO COMMUNICATION FACILITIESAVAILABLE


Explanation: Neither Cross Memory Services norNetwork Communications are available tothe Object Service Broker Data Object Broker.Object Service Broker terminates abnormally.

Action: Look for any associated messages whichprovide further explanation. If this is aninitial installation, ensure that thecommunication definitions required by

Object Service Broker are in SYS1.VTAMLSTand are activated. Verify that the correctVTAM application identifier initializationvalue was specified. If you are unable toresolve the situation, contact TIBCO Support.

S6BKC014L________________ ACCESS VIA ________TERMINATED


Explanation: Access to the specified ObjectService Broker node along the specified pathwas lost because the connection wasterminated.

Action: If the termination was not expected,review the associated messages to determineif an error condition was reported.

S6BKC015L________ SERVER HAS BEEN STOPPED VIAOPERATOR REQUEST


Explanation: The specified gateway has beenterminated as a result of an operatorstopserver or shutdown request.


S6BKC016Lconnectid CONNECTED #=num TYPE=typeCOMM=comm-type SOURCE=xxxx


Explanation: This notification message willidentify the connection for a user or batch jobto the Data Object Broker.

• connectid may or may not be uniquedepending on site configuration


| 237

• num is the relative connection block usedto support this connection. It will alwaysbe unique.

• type identifies the type of session beingconnected, e.g., CICSUSER

• comm-type identifies the type ofcommunication supported for theconnection (VTAM, XMS or TCP/IP)

• If the connection is for a terminal-baseduser, the SOURCE value identifies theterminal through which the user isconnected

• If the connection is for a Batch Job, theSOURCE value displays the job name andstep name for the connection.


S6BKC017Lconnectid LOGGED OFF #=num TYPE=typeCOMM=comm-type SOURCE=xxx


Explanation: This notification message identifiesthe logoff for a user or batch job from theData Object Broker.

• connectid may or may not be uniquedepending on site configuration

• num is the relative connection block usedto support this connection. It is alwaysunique.

• type identifies the type of session loggingoff, e.g., CICSUSER

• comm-type identifies the type ofcommunication supported for theconnection (VTAM, XMS or TCP/IP)

• If the logoff is for a terminal-based user,the SOURCE value identifies the terminalthrough which the user is connected

• If the logoff is for a Batch Job, the SOURCEvalue displays the job name and step namefor the connection.


S6BKC018I________ SERVER AVAILABLE, TYPE=___,SERVER ID=_


Explanation: A gateway/server connection hasbeen accepted by the Data Object Broker for agateway/server with the specified uniqueidentifier. This gateway/server has thespecified type and serverid, which are usedto group it with like gateways/servers.


S6BKC019LSERVER TERMINATED, SERVER ID =________, ID = ___________


Explanation: A gateway/server that wasconnected to Object Service Broker with thespecified type and serverid and uniqueidentifier as specified by "ID=" hasterminated its connection.



238 |

S6BKC020IROUTING ERROR


Explanation: A communications exit received arequest that it does not support.

Action: Try to identify the circumstances thattrigger this message. An isolated occurrencemay be insignificant. Contact TIBCO Supportif there are multiple occurrences or relatedproblems.

S6BKC021E_______ OVERRUN, TRX ID =________, USER=


Explanation: Object Service Brokersynchronization error. A new transactionarrived before the current transactioncompleted. The user who experienced theerror, their current transaction ID, and thephase (COMMIT or QUERY) are included inthe message to help identify the cause.

Action: Contact TIBCO Support. If the problemcan be recreated make sure you turn snap onso a snap dump can be generated when theproblem occurs.

S6BKC022ISESS GETBUF FAILED


Explanation: The table processing required tosatisfy the request could not be processedbecause a sessarea buffer could not beobtained.

Action: Ensure that the Object Service Brokerstartup configuration specifies a concurrencylevel that is appropriate for your workload.The concurrency level is set by theMAXTHREADS Data Object Brokerparameter.

S6BKC024IUNSOLICITED DBMS MESSAGE


Explanation: Object Service Broker protocolerror. An unassigned DBMS gateway madean unsolicited request for service. Therequest is ignored.


S6BKC025WSERVER ACCESS IS NOT DEFINED


Explanation: A request was made for access to agateway with a specific type and serverid. Amatching gateway provider has notconnected to the Object Service Broker DataObject Broker since it was started.

Action: Contact the person responsible for theData Object Broker or the access you requireand request the gateway be made available.


| 239

S6BKC026ISERVER ACCESS NOT AVAILABLE


Explanation: A request was made for a serviceprovider with a specific type and serverid.Service providers with match characteristicshave registered with the Data Object Brokerbut they are either all in use or the connectionis no longer active.

Action: Either wait for a service provider to befreed up (try again) or contact the personresponsible for the Data Object Broker andhave more service providers made available.

S6BKC027WUSER CURRENTLY ACCESSING MAXIMUMNUMBER OF SERVERS


Explanation: During the execution of atransaction there is a limit of six serviceproviders. The request for an additionalgateway provider has been rejected becauseit would exceed this limit.

Action: Redesign the application to adhere to thelimits.

S6BKC028WREQUEST REJECTED, MESSAGE FLOWRESTRICTED


Explanation: A request has arrived at the ObjectService Broker Data Object Broker which iscurrently not able to process any newrequests. The restriction could be temporaryor the Data Object Broker could be in the

process of shutting down. PrecedingS6BDB095A messages may also have beenissued indicating another cause of theproblem.

Action: Retry your request at a later time. IfS6bDB095A messages were issued, take theappropriate actions as documented forS6BDB095A.

S6BKC029EWORK BUFFER NOT AVAILABLE TOSUPPORT PROCESSING, REQUESTREJECTED


Explanation: A work buffer was not available toretain vital information when the requestprocessing was being initialized. Theinformation could not be retained so therequest was rejected.

Action: Ensure the system is configured with theMAXUSERS parameter at a level appropriatefor the current workload. During theretrieval of the buffer an attempt is first madeto obtain a work buffer; if that fails, a pagebuffer is retrieved. The S6BKC029E messageis only generated if no buffers are availablefrom either of these pools. If both pools areexhausted, there is a good chance that otherproblems have occurred or are occurring.Check the joblog to try to determine thecause of these failures.


240 |

S6BKC030EUNDEFINED EVENT CODE X'____'


Explanation: The Communications subtaskreceived a request that it does not support.The request is ignored. Normal processingcontinues.

Action: Try to identify the circumstances whichtrigger this message. An isolated occurrencemay be insignificant. Contact TIBCO Supportif there are multiple occurrences or relatedproblems.

S6BKC031AD.O.B. ACTIVE, NO COMMUNICATIONAVAILABLE


Explanation: An unrecoverable condition in thecommunication environment has resulted inthe termination of all communication to theObject Service Broker Data Object Broker.

Action: Refer to the joblog to determine what theerror condition is. When the condition iscorrected, restart the Data Object Brokercommunication using the COMRESTARTcommand via the console.

S6BKC032L'_'


Explanation: This message is displayed inresponse to the receipt of a command froman administrator. The message displays thefirst 20 characters of the command text, andthe ID of the operator who issued thecommand.


S6BKC033LUSER LIMIT EXCEEDED, CONNECTIONREJECTED - ________


Explanation: When attempting to connect a usersession the configured limit was exceeded.

Action: Review the MAXUSERS parameter todetermine if it is set appropriately for therequired workload.

S6BKC034LCONNECTION MANAGEMENT POOLEXHAUSTED, CONNECTION REJECTED


Explanation: Each connection made to the DataObject Broker requires a block of privatememory to retain information about theconnection and statistics. The pool fromwhich this memory is acquired (theCOMMPOOL) has exhausted its supply ofbuffers. The number of buffers available isbased on the MAXUSERS parameter and thepath management data available at startup. Ifthe schedule for paths have been increased ornew paths have been added it may accountfor the pools shortfall.

Action: The only way to reset the size of the poolis to recycle the Data Object Broker. If therehas been a lot of changes to the pathmanagement limits, the Data Object Brokershould be recycled when it is convenient.


| 241

S6BKC035LINITIATING PEER CONNECTION TOluname:node name


Explanation: Notification that the connection tothe identified peer node is being attempted.


S6BKC036Lconnectid REJECTED TYPE=typeREASON=ee/rr


Explanation: When a connection to the DataObject Broker is rejected, this messageappears to identify the reason why.

• connectid is the name used to connect tothe Data Object Broker. It may or may notbe unique depending on site settings

• type is the type of session, e.g., CICSUSER

• ee is the error code; it can be either 08 or 12

• rr is the reason code

For Error Code 08 - Logic error, the followingreason codes apply:

• 00 - compatibility code not passed inconnection data

• 04 - compatibility error - check for wrongload library

• 08 - connection data incomplete, regiontype missing

• 12 - connection data incomplete,connection ID block missing

• 16 - connection data invalid, connectiontype not supported

• 20 - Data Object failed to accept the session

• 24 - connection data incomplete,specification block too small

• 28 - rules-based gateway rejected, partnerconnection not specified

• 32 - no longer used

• 36 - gateway connection data incomplete

• 40 - invalid connection ID specified (note:S6BBRULH not acceptable)

• 44 - gateway connection data incomplete,group ID not specified

• 48 - gateway connection data invalid,characteristic error

• 52 - rule-based gateway rejected,connection partner not found

• 56 - rule-based gateway rejected,connection partner associated already

For Error code 12 - Environmental errors, thefollowing reason codes apply:

• 00 - Data Object Broker is not acceptingconnection request

• 04 - storage not available for the requiredconnection block

• 08 - connection currently restricted tooperators

• 12 - batch jobs are not permitted to connectat this time

• 16 - connection ID is already present

• 20 - MAXUSERS users already connected

• 24 - Inbound Peer connection not definedin Resource Manager

• 28 - system quiesced, connection requestsare not being accepted

• 32 - gateway type/group combination notdefined to the resource managementsystem

• 36 - gateway connection already atmaximum as per resource manager

• 40 - In a multi Data Object Broker systemconnections to the Data Object Broker areonly accepted from Message Switches


242 |



• 52 - connection information is not inacceptable format

• 56 - connection block format error detected

• 60 - wild card gateway definition exceedsresource limits

• 64 - CICS display user limit exceeded

• 68 - Data Object Broker is not licensed forCICS access

Action: Contact TIBCO Support if you needfurther clarification.

S6BKC039WTRANSACTION NUMBER EXTRACTIONERROR ON PATH SELECTION


Explanation: An internal error or messagestructure problem has been detected duringexternal gateway/server path selection. Theselection process fails and the user isreturned an error.


S6BKC041WSERVER LOST BEFORE COMMITPROCESSING INVOKED


Explanation: During the edit processing before acommit is initiated, an externalgateway/server required for the commit isno longer available. The commit is rejectedbefore any updates are processed.

Action: Retry the transaction. If available,another gateway/server will be usedautomatically.

S6BKC042IERROR DETECTED DURING PREPARE TOCOMMIT PHASE


Explanation: Internal indicators show pendingupdates for a DBMS gateway. However, thegateway association does not exist.

Action: Invoke the transaction again. If the errorrecurs, contact TIBCO Support.

S6BKC043WPREPARE TO COMMIT FAILURE DETECTED


Explanation: A discrepancy has been detected inthe user/DBMS gateway cross-reference.

Action: Invoke the transaction again. If the errorrecurs, contact TIBCO Support.

S6BKC044WNO CONTINGENCY LOG RECORDSAVAILABLE


Explanation: This request had exceeded theconfigured limit for concurrent indoubttransactions. All tracks within theREDO.PENDING file are in use. This requestis aborted.

Action: Expand the contingency log allocation.


| 243

S6BKC045EREMOTE COMMIT REQUIRING FAIL SAFEPROCESSING HAS FAILED


Explanation: The response to a Prepare-To-Commit or Commit request sent to anexternal resource has indicated an inability tosatisfy the request.

Action: System Action: The commit group failed,none of the commit processing for the syncpoint is processed. User Action: Review thelogs of the external resource to determinewhat cause the prepare to commit failure.

S6BKC047ISERVER COMMIT FAILURE DETECTED,TRANSACTION REJECTED


Explanation: A DBMS gateway has respondedwith a nonzero return code for the firstgateway updated within the COMMITgroup. The COMMIT group is aborted.

Action: Retry the application.

S6BKC048ISERVER LOST, PENDING TABLE UPDATESHELD IN-DOUBT


Explanation: A DBMS gateway session was lostafter the point it was issued a commit andbefore it could acknowledge the COMMITcomplete. The pending TDS table updatesare held in-doubt until the system candetermine if the DBMS updates werecompleted or the transaction is manuallyresolved.

Action: Restart the gateway or manually resolvethe error by using the administrator utility.

S6BKC049ISERVER LOST, REQUEST REJECTED


Explanation: While a service provider wasprocessing a request, its connection to theObject Service Broker Data Object Broker wasterminated.

Action: View the system log to determine whythe service provider was terminated, or retryyour request at a later time.

S6BKC050ISERVER FAILURE, COMMIT CURRENTLYIN PROGRESS ABORTED


Explanation: The COMMIT group has beenaborted because the session for a DBMSgateway with updates responded with anerror return code during it commitprocessing.

Action: Refer to the gateway's job log todetermine the reason for the failure.

S6BKC051ACONTINGENCY LOG WRITE FAILUREDETECTED


Explanation: When attempting to record the TDSintent list on the contingency log(REDO.PENDING), physical write errorswere reported. The Data Object Broker willbe terminated if continuing after this errorcould result in a data integrity issue.

Action:

• If this error does not result in terminationof the Data Object Broker, then shut theData Object Broker down at the earliest


244 |

convenient time and address the problemwith the contingency log.

• If this error terminates the Data ObjectBroker, address the problem with thecontingency log, restart the Data ObjectBroker and use the administration utilityto resolve any IN*DOUBT transactions.

• If necessary contact TIBCO support forguidance.

S6BKC052ACONTINGENCY LOG IS NOT EMPTY


Explanation: At Data Object Broker initializationtime the contingency log contained datarecords. This means that manualintervention may be required to clean up anyin*doubt transactions.

Action: Once the Data Object Broker hascompleted initialization use theAdministrator utility to review thecontingency log and perform any requiredactions.

S6BKC053ESERVER ERROR, TDS UPDATES ABORTED,SERVER DATA INCONSISTENT


Explanation: During the COMMIT cycle, aDBMS gateway (not running under Fail Safeconstraints) reported a COMMIT error. Thedefault action of the system is to abort theCOMMIT, snap the pending TDS updatesand roll back any other DBMS gateways.

Data between the DBMS gateways andObject Service Broker may now be out ofsync because of a partially completedCOMMIT group.

Action: Try to resolve any data inconsistenciesand then retry the application.

S6BKC054IIN-DOUBT RESOLVED, TDS COMMITISSUED


Explanation: An outstanding in-doubttransaction has been resolved eitherautomatically or due to manual intervention.The pending TDS table updates have beensubmitted for processing.


S6BKC055IIN-DOUBT RESOLVED, TDS REQUESTABORTED


Explanation: An outstanding in-doubttransaction has been resolved eitherautomatically or due to manual intervention.The pending TDS table updates have beenrejected.



| 245

S6BKC057INO STORAGE AVAILABLE FOR MESSAGEINBOUND POOL


Explanation: A message was received that mustbe copied into a work buffer to support largeinbound messages. When an attempt wasmade to acquire a buffer from the pool therewere no buffers available. This could indicatean internal buffer release issue or a pool sizethat is inadequate to meet your needs.

Action: Take a COMM dump and create anincident with TIBCO Support. To alleviatethe problem for now, recycle the Data ObjectBroker with a larger MAXTHREADparameter value to cause the number ofMSGI pool buffers to be increased.

S6BKC058INO STORAGE AVAILABLE FORCONTINGENCY LOG POOL


Explanation: During Object Service Brokerinitialization, sufficient storage (above theline) was not available for use by thecontingency log. The Object Service Brokeraddress space may require a larger regionsize, or authorization to exceed site-imposedlimits (IEFUSI).

Action: Contact your site's system administrator.

S6BKC059ECONTINGENCY LOG ERROR DETECTED


Explanation: An error was detected whenattempting to process the contingency log(REDO.PENDING).

Action: See the job log for accompanyingmessages with more detail.

S6BKC060EGROUP SYNCHRONIZATION FAILED-UPDATED SERVER LOST


Explanation: When preparing to commitchanges, the Object Service Broker DataObject Broker detected that a serviceprovider which had updates against it wasno longer available. The pending transactionwill be aborted.

Action: Retry the transaction.

S6BKC061EGROUP SYNCHRONIZATION FAILED-SERVER MANAGEMENT ERROR


Explanation: When preparing to commitchanges, the Object Service Broker DataObject Broker detected that its internalpointers were not set as expected. Thepending transaction will be aborted.

Action: Retry the transaction. If the problemrecurs contact TIBCO Support.


246 |

S6BKC062EGROUP SYNCHRONIZATION FAILED-MIXED COMMIT PROTOCOLS


Explanation: When preparing to commitchanges, the Object Service Broker DataObject Broker detected that multiple serviceproviders were updated that supporteddifferent levels of Fail Safe processing. Thepending transaction will be aborted.

Action: Redesign the application to conform toFail Safe requirements. See the discussions ofFail Safe processing in the Backup andRecovery manual and the appropriateGateway manual.

S6BKC063EGROUP SYNCHRONIZATION FAILED-COMMIT CONSTRAINT VIOLATION


Explanation: When preparing to commitchanges, the Object Service Broker DataObject Broker detected that multiple serviceproviders that require Fail Safe support wereupdated. This violates the constraints of FailSafe level-1 processing. The pendingtransaction is aborted.

Action: Redesign the application to conform toFail Safe requirements. See the discussions ofFail Safe processing in the Backup andRecovery manual and the appropriateGateway manual.

S6BKC064EGROUP SYNCHRONIZATION FAILED-OUTSTANDING INDOUBT TRX


Explanation: When preparing to commitchanges, the Object Service Broker DataObject Broker detected that a Fail Safe level-1commit was required against a DBMS serviceprovider which already had an in-doubttransaction against it. The pendingtransaction is aborted.

Action: Retry the transaction and/or resolve thein-doubt transaction. See the discussions ofFail Safe processing in the Backup andRecovery manual and the appropriateGateway manual.

S6BKC065EGROUP SYNCHRONIZATION FAILED-PREPARE TO COMMIT FAILURE


Explanation: A prepare to commit request wasmade to a peer Object Service Broker duringthe processing of a transaction which utilizedObject Service Broker distributed data. ThePEERS parameter on the remote ObjectService Broker indicated Fail Safe support;however, when "prepare to commit" requestwas received the remote Object ServiceBroker was unable to support the request.The pending transaction will be aborted.

Action: Correct the PEERS parameter on the localObject Service Broker. See the discussions ofFail Safe processing in the Backup andRecovery manual and the appropriateGateway manual.


| 247

S6BKC066EGROUP SYNCHRONIZATION FAILEDDURING COMMIT CYCLE, HELD IN-DOUBT


Explanation: A Fail Safe level-2 commit hasfailed. The contingency log is retained untilall peer Object Service Broker systems haveacknowledged a release of their contingencylogs.

Action: Review the system log for accompanyingmessages to determine why the Fail Safelevel-2 commit aborted.

S6BKC067EINCOMPLETE PREPARE TO COMMITABORTED DURING RESTART


Explanation: During the restart of an ObjectService Broker Data Object Broker, acontingency log in the "prepare to commit"phase of a Fail Safe level-2 commit wasrecovered. In the "prepare to commit" phase,no updates were committed, the transactionis aborted, and all service providers will berequested to release their contingency logs ifthey are present.


S6BKC068AINDOUBT TDS UPDATES COULD NOT BERETAINED


Explanation: When a transaction is determinedto be in-doubt the TDS intents are transferredfrom the user controlled space to an ObjectService Broker control buffer. A buffer couldnot be acquired.

Action: The transaction is aborted and held in-doubt; the TDS is already safe, stored in theREDOLOG.PENDING data set.

S6BKC069EUNABLE TO ESTABLISH INDOUBT LOCKSDURING RESTART


Explanation: During the startup processing of aData Object Broker, logical locks for in-doubttransactions are reacquired. During theattempt to acquire the logical lock, an errorwas detected.

Action: Check the joblog for an error from thelock manager, which may help identify thenature of the problem. Contact TIBCOSupport for additional assistance.

S6BKC070IGROUP SYNCHRONIZATIONINCOMPLETE-PEER UPDATES DEFERRED


Explanation: During a disrupted two phasecommit, communications to one of the peerregions was lost. The commit cycle is helduntil the status of the peer commit isdetermined.

Action: Restart the communications link to thepeer region as soon as possible.


248 |

S6BKC071IGROUP SYNCHRONIZATIONORIGINATOR STATUS INDOUBT


Explanation: The contingent resource of acontingent two phase commit has suffered acommunication interruption. The originatingData Object Broker put the transaction intoin-doubt status. The message will beproduced by the peer when it is informed ofthe in-doubt condition.

Action: Reactivate the lost communication linkas soon as possible.

S6BKC072W2 PHASE GROUP SYNC ABORTED;ORIGINATOR LOST, PENDING FAIL SAFE 1RESOURCE UPDATES


Explanation: The remote commit coordinator ofa transaction doing a contingent two phasecommit has aborted a transaction. It wasdetermined that the connection with theoriginator was lost before any of the commitgroup was filed. The transaction has endedabnormally with no updating taking place.


S6BKC073WGROUP SYNCHRONIZATIONTERMINATED BY ORIGINATOR


Explanation: The remote commit coordinator hasbeen instructed by the originator to cancelthe two phase commit processing for atransaction and release the remote resources.

There was a problem in the commit groupcoordinated by the originator which couldnot be overcome, therefore the transactionwas aborted.


S6BKC074ARESOURCE ___-________ IDENTIFIED INCLOG, NOT IN PATH CONTROL


Explanation: When Object Service Brokerrestarted, it found an indoubt transactionwith an external resource that is no longernamed in the configuration repositories.

Action: Ensure the repository is still intact anddetermine why the identified path is nolonger defined. Either correct theconfiguration and retry or use theS6BTLADM utility to delete the indoubttransaction.

S6BKC075ELOGON REJECTED - CICS DISPLAY LIMITEXCEEDED userid


Explanation: The connection request for theidentified user was rejected because thenumber of CICS display-type connections isalready at the value specified by theMAXDISPLAY parameter.

Action: Retry your transaction or wait for a CICSdisplay-type connection to terminate.


| 249

S6BKC077EATTEMPTED TO CHANGE REMOTE RULEPROCESSOR WITHIN A TRANSACTION


Explanation: When processing remote tables aremote rule server is used. Normally the ruleserver will default; this can be overriddenusing the session table. If you do wish tooverride the rule server selection process itmust be done prior to the first remote accesson that node within the current transaction.The current transaction has been abendedbecause the rule server had already beenselected prior to the failing attempt.

Action: Override the Remote Rule Server earlierin your transaction.

S6BKC080I-________CONNECTION REJECTED,REGISTRATION DIFFERENT THANRESOURCE MANAGER


Explanation: An external resource (DBMSgateway, Remote Rule Server or Peer ObjectService Broker) connection was rejected witha return code of x'08' and a reason code ofx'30'. This means the flags identifying thecharacteristics of the resource do not matchthe requirements specified in the ResourceManagement system. A KC081 messagefollows this message and identifies theresource characteristics that failed atconnection time.

Action: Review the KC081 message that follows.

S6BKC081ISUPPLIED: INT.RLBK _, EARLY RELEASE _,LAST USER _ AND FAIL SAFE


Explanation: An external resource (DBMSgateway, Remote Rule Server or Peer ObjectService Broker) connection was rejected witha return code of x'08' and a reason code ofx'30'. This means the flags identifying thecharacteristics of the resource do not matchthe requirements specified in the ResourceManagement system. This message identifiesthe resource characteristics that failed atconnection time.

Action: Compare the indicators in the KC081message for the path identified by thepreceding KC080 message against thosedefined in the Resource Managementfunction via the Administrator utility.

S6BKC082ACONFIGURATION ERROR, PEER HASLOCAL VTAMID


Explanation: In the definition of a peer ObjectService Broker connection, the serveridspecified is the applid of the target ObjectService Broker. During start-up processingfor a peer connection, it was detected that thetarget applid matched the VTAMID of thelocal Data Object Broker. The connection isnot logically or physically valid.

Action: The administrator should go into thepath management facility via S6BTLADMand remove the invalid path control entry.


250 |

S6BKC083WDUPLICATE USERID (PREFIX ___) ALREADYON PEER


Explanation: When a Data Object Broker wasattempting to make a connection to a remoteData Object Broker, the connection wasrejected because there is already a session onthe remote Data Object Broker with the sameuserid.

Action: In the Administrator ResourceManagement Facility, edit the outbound Peerdetail entry (HRN) and ensure a uniquePREFIX is specified for the generated userid.

S6BKC084EDATA EXCHANGE ELEMENT NOTAVAILABLE FOR RESPONSE


Explanation: A buffer to build an operatorresponse could not be obtained from thesystem.

Action: The request is rejected.

S6BKC085EDATA EXCHANGE ELEMENT LENGTH OUTOF RANGE; TRANSACTION REJECTED


Explanation: A message length greater than theacceptable limit has been detected by thequery processor.

Action: The system will abend the transaction. Ifa snap dump was produced (optional, basedon start-up parameters) contact TIBCOSupport and forward the snap dump in anincident report.

S6BKC086WSERVER COMMAND TO _______ TYPE=___,GROUP=________ REJECTED, COMMANDALREADY ACTIVE


Explanation: A gateway/server commandoperator modify command was receivedwhich includes processing a gateway/serverwhich already has a gateway/servercommand outstanding.

Action: The request is ignored for thegateway/server path.

S6BKC087EBUFFER NOT AVAILABLE TO CHAINDEFERRED SERVER COMMANDS


Explanation: When attempting to obtain a bufferto support a gateway/server commandrequest, the required buffer space was notavailable.

Action: The requested gateway/servercommand processing is terminated.

S6BKC088ISRVR CMD: ISS=____, DEFER=____, RSC=___________, CMD=__________


Explanation: This informational message isproduced at the completion of the gatewaycommand resource identification process. Itidentifies how many requests were issuedimmediately, how many had to be deferredbecause the path was in use, the name of theresource and the requested command text.



| 251

S6BKC089ISRVR CMD: OK=_____, FAILED=_____,RSC=___ ________, CMD=________


Explanation: This informational message presentthe gateway/server command processingresults when the last candidate path hasresponded.


S6BKC090ESRVR CMD REJECTED, NO PATHS MATCH___ ________


Explanation: When attempting to selectappropriate paths to send the requestedgateway/server command it was found thatno active paths existed.

Action: The gateway/server command request isrejected

S6BKC091WNO SESSAREA AVAILABLE, TASKDELAYED


Explanation: A new query or commit request isto be processed by the Data Object Broker. Atthis time no SESSAREA is available for thisrequest. The request is delayed until aSESSAREA becomes available. This messagemay occur while the Data Object Broker isfrozen.

Action: If this message occurs regularly duringnormal processing, increase the value of theMAXTHREADS Data Object Brokerparameter until this message no longerappears.

S6BKC105WSPIN IN PROGRESS SHUTDOWN REQUESTREJECTED


Explanation: A SHUTDOWN request wasreceived while a journal spin is active.

Action: The operator command:

MODIFY jobname,JOURNALSTATUS

S6BKC106WUSER NOT PERMITTED TO SHUT DOWNSYSTEM


Explanation: An Object Service Broker shutdownrequest was issued by the operator utility,but the Object Service Broker parameters areset to disallow the shutdown.

Action: Issue the shutdown request from theoperator console.

S6BKC186WJOURNAL SPIN FLAG ALREADY INREQUESTED STATE


Explanation: A job executed the S6BSPJEXprogram to change the Journal spin status.The SPIN flag is already set to whatever wasrequested. No action is taken.

Action: No action is required, but it isrecommended that access to the S6BSPJEXprogram be restricted.


252 |

S6BKC187WJOURNAL SPIN FLAG RESET ONLY - NOOFFLINE JOURNAL


Explanation: A job executed the S6BSPJEXprogram to enable Journal spins. However,no Journal was offline, and therefore noJournal was reopened.

Action: No action is required. You may want todisplay the Journal status. It is recommendedthat access to the S6BSPJEX program berestricted.

S6BKC188WSRBMODE=Z SPECIFIED BUT NO ZIIPAVAILABLE


Explanation: The SRBMODE parameter has beenset to Z, but no zIIP processor is available tooffload work to.

Action: None. The Data Object Broker reverts toSRBMODE=Y for this instance.

S6BKC200EREPOSITORY DYNALLOC FAILURE


Explanation: When attempting to dynamicallyallocate the repository data set for theResource Manager, an error was detected.

Action: The communication subtask will failduring initialization.

S6BKC201EERROR DETECTED IN GENCB FOR "GENCB"FOR REPOSITORY


Explanation: When attempting to build a controlblock to support Resource Managementprocessing, an error was detected.

Action: The communication sub-task will failinitialization.

S6BKC202EERROR DETECTED ON REPOSITORY


Explanation: During the initialization of the DataObject Broker, an error was detected with therepository open or read.

Action: The Data Object Broker initializationfails.

S6BKC204ERESOURCE ENTRY NOT SPECIFIED INDBDLIB, REBUILD DBDLIB


Explanation: The remote Data Object Broker andgateway/server definitions are saved in aKSDS 128 data set. The required data setcould not be located.

Action: Rebuild your DBDLIB.


| 253

S6BKC228LTRANSACTION MANAGEMENTDIRECTIVE INVALID


Explanation: An Object Service Broker usertransaction issued a transaction managementdirective to cause the Data Object Broker todo user accounting or user update. Therequest has been rejected because of aninvalid function code or other format error.

Action: The transaction management requestshould be investigated and corrected.


254 |

KF: DOB Commit Task

S6BKF000EINVALID TDS REQUEST

Source: DOB Commit Task

Explanation: Internal TDS server error. Anunsupported request for service wasreceived by the supervisory code. Thetransaction is aborted.


S6BKF001WNO INLINE WRITES ALLOWED


Explanation: A request was received to write apage, but the request is illogical, reflecting aninternal TDS server error.

Action: Contact TIBCO Support

S6BKF003WNO MESSAGES ALLOWED FROM SYNCHPOINT


Explanation: Object Service Broker protocolerror. A commit process is not permitted tohave a dialog with an Object Service Brokeruser.


S6BKF004WINVALID PAGE NUMBER SPECIFIED


Explanation: An invalid page number wasrequested. The transaction is aborted.Associated information is displayed througha generalized abort message.

Action: Contact the Object Service Broker SystemAdministrator. The error may indicateinternal data corruption errors within certainindex pages. Alternatively, severaladministrator-only tools do allow data accessthat bypass normal Object Service Brokernavigation. The error may represent keyingerrors by the System Administrator.

S6BKF005WPAGE POOL BUFFER ERROR


Explanation: Object Service Broker failed toobtain transient storage for this transaction.

Action: Contact the Object Service Broker SystemAdministrator and verify that Object ServiceBroker was configured to handle the currentlevel of concurrency. Refer to the Installationand Operations manual for details.

S6BKF006WILLEGAL GET LOCK DURING SYNCH


Explanation: Protocol error. The COMMITprocess is not allowed to acquire additionallogical locks.



| 255

S6BKF008WNO PAGE BUFFERS AVAILABLE


Explanation: No more page buffers are available.


• Refer to the Installation and Operationsmanual for configuration options

• Change the Object Service Broker startupparameters

• Contact TIBCO Support.

S6BKF009WNO FREE PAGES AVAILABLE IN SEGMENT


Explanation: The underlying Pagestore does nothave any more free pages. Consequently newdata cannot be stored in this segment.

Action: Object Service Broker Pagestores must beregularly administered to ensure thatsufficient space is available for theanticipated workload. Numerous tools areavailable to the System Administrator tomanage the Pagestores and extend the publicspace available. Review the relevantdocumentation in the ApplicationAdministration manual.

S6BKF011WPAGE NOT FOUND IN HOLD LIST


Explanation: Object Service Broker logic error. Apage to be written was not held by thecurrent transaction. The transaction isaborted with a snap dump.


S6BKF012EATTEMPT TO WRITE PAGE ZERO


Explanation: Object Service Broker logic error.The commit process attempted to overwrite areserved page. The transaction is abortedwith a snap dump.


S6BKF013WTDS PAGE CONTROL VIOLATION


Explanation: Object Service Broker logic error.The commit process attempted to writeinvalid data. The transaction is aborted witha snap dump.


S6BKF014WCTABLE SLOTS IN USE


Explanation: Refer to message S6BKA021W.


S6BKF016WTOO MANY BUFFERS REQUIRED


Explanation: The users exceeded the maximumnumber of buffers allowed for a session.


• Shorten the transaction by issuing moreintermediate commits.

• If the WORKINGSET Data Object Brokerparameter is not at a maximum, considerincreasing it to allow for more data and


256 |

index pages to participate in thetransaction.

S6BKF017WINVALID FREE BUFFER ATTEMPT


Explanation: An attempt to free a buffer failed.

Action: Contact the Object Service Broker SystemAdministrator.

S6BKF018WPAGE POOL BUFFER ERROR


Explanation: An attempt to free a page bufferfailed.

Action: Contact the Object Service Broker SystemAdministrator.

S6BKF019EINVALID HOLD LIST MANAGEMENTDIRECTIVE


Explanation: An invalid request was made of theroutine that manages pages held for update.The transaction executing at the time thiserror is encountered abends.

Action: This is an internal processing error andshould be reported to TIBCO Support.

S6BKF020EPAGE TO BE ADDED TO HOLD LISTALREADY EXISTS


Explanation: The page being added to the list ofpages held for update by this transaction wasalready in the list. The transaction executingat the time this error occurred will beaborted.


S6BKF021EDATA PAGE UPDATE LIMIT EXCEEDED,TRANSACTION ABORTED


Explanation: The current transaction attemptedto access more Data pages then werepermitted based on the DATAPAGELIMITrun time parameter.

Action: The transaction is aborted. To avoid theproblem either add an intermediate committo the application or increase theDATAPAGELIMIT parameter value.


| 257

S6BKF025WUNABLE TO OBTAIN HOLD LIST BUFFER


Explanation: While processing a commit request,the Data Object Broker was not able to obtaina buffer to contain the list of held pages. Thefailing transaction is aborted, and processingcontinues normally.

Action: This problem will only occur whenprocessing very large transactions whichutilize external buffers for the held page list.The problem is that these buffers are a finiteresource, and there are too many largetransactions executing concurrently. Retrythe failing transaction.

S6BKF026ECANNOT UPDATE - REQUIRED SEGMENTIS IN READ ONLY MODE


Explanation: One or more of the segmentsrequired by this commit are in read onlymode and cannot make the requestedupdates. The transaction is aborted.

Action: If possible, change the mode of therequired segment to read/write and rerunthe failed transaction.

S6BKF028EATTEMPTED TO READ A PAGE THAT ISCURRENTLY FREE, SEG=____, PAGE=__


Explanation: The processing routine that servicespage reads determined that the requestedpage is indicated as a free page. Theseproblems tend to be the results of dirty readsthat occur when a query is accessing pagesvia an index where the index is in the processof being changed by another transaction.

Action: Depending on your preceding actions,do one of the following:

• If you were doing an administrationfunction to view a page image, such asusing option U from the AdministrationMenu, no action is required.

• In all other situations, this message meansthat you have a corrupted segment. Do thefollowing:

1. Immediately take the segment offline.

2. Run S6BTLBPS (Back Up Page DataSets utility).

3. Run S6BBRPTR (Batch Pointer Checkutility) with the HDR option.

4. Contact TIBCO Support, supplyingthe output from Pointer Check.

S6BKF029WPAGESTORE SEGMENT NOT AVAILABLE


Explanation: The system requested a segmentthat is currently unavailable.

Action: Contact the Object Service Broker SystemAdministrator because the segment may beoffline.


258 |

S6BKF030WINVALID SEGMENT SPECIFIED


Explanation: A GETPAGE request was receivedwith a segment number greater than themaximum number of segments defined.


S6BKF032WDEADLOCK AVOIDANCE FAILED


Explanation: Deadlock avoidance logic wasinvoked and a request redriven. The redrivenrequest was again intercepted by deadlockavoidance, and aborted as a result.

Action: Requests are interfering with oneanother. Retry the request and contact TIBCOSupport.

S6BKF033WPAGE READ IS NOT PAGE REQUESTED


Explanation: Internal error.


S6BKF034WTRANSACTION PAGE READ LIMITEXCEEDED


Explanation: The transaction currently beingprocessed by the Data Object Broker has readmore pages from the Pagestore data sets thanpermitted by the Object Service BrokerSystem Administrator. The transaction isaborted.

Action: Contact the System Administrator todetermine a method by which the transactioncan be executed within the constraints of theObject Service Broker system. If needed, theTRXREADLIMIT can be adjusted to allowmore pages to be read by a transaction.

S6BKF035WRETRY LIMIT EXCEEDED, USER ________BLOCK BY USER ________ ON TABLE


Explanation: During the processing of atransaction, an attempt to gain exclusiverights to a resource failed and the retry limitwas exceeded. The transaction was not ableto wait because it retained resources neededdirectly or indirectly by other transactionsthat held the resource the transaction wastrying to obtain.

Action: The transaction fails.


| 259

S6BKF036WDBOFFLINE REQUEST DEFERRED,SEGMENT IN USE


Explanation: While validating a request to take asegment offline it was determined that one ormore CTABLEs (table definition blocks) fortables resident on segment were still in use.

Action: Segment offline processing is deferreduntil the CTABLEs are no longer required.

S6BKF037EUNABLE TO OPEN SEGMENT, CACHECAPACITY EXCEEDED


Explanation: The actions required to bring asegment online requires enough outputprocessing to exceed the available spaceremaining in the checkpoint write-ahead log(CACHE). The segment online attempt wasrequested twice without success.

Action: Try your request again. You shouldreview your configuration; your cache maybe too small.

S6BKF038WPAGESWEEP LIMIT EXCEEDED, -user---, ---table name -,commarea, trx#


Explanation: The site specified a Page SweepLimit to identify transactions that accessmore than a "threshold" number of pages.This message attempts to identify the userand transaction that exceeded the codedlimit.


S6BKF039EPAGE NOT FOUND IN HOLD LIST DURINGPAGE FREE PROCESS


Explanation: When attempting to change apreviously used page to a free page, it wasdetermined that the page was not properlyrecorded in the internal control tables.


S6BKF041EUNEXPECTED RESIDENT PAGEMANAGEMENT RESULT, TRANSACTIONTERMINATED


Explanation: When processing a transaction thereturn code from the Resident Page Managerwas unexpected in the given scenario. Thereis a very good chance that the cause of theproblem is temporary.

Action: Re-invoke the transaction after theabnormal transaction termination hascompleted.

S6BKF042ERTUQTASK LOAD FAILED,INITIALIZATION TERMINATED


Explanation: During Data Object Brokerinitialization, a subtask (RTUQTASK) wasnot able to perform its initializationsuccessfully. The Data Object Broker will failduring startup.

Action: Review the joblog and contact TIBCOSupport.


260 |

S6BKF043ASYSTEM IS FROZEN AND CHECKPOINTREQUIRED FOR %


Explanation: During this period when the ObjectService Broker system named is frozen,sufficient commit activity has occurred for acheckpoint to be necessary. No more commitprocessing will be performed until thesystem is UNFROZEN.

Action: Verify that the system should remainfrozen. To resume normal Object ServiceBroker processing, use the Unfreezecommand.

S6BKF044ILONG RUNNING TASK(S) IN PROGRESSFREEZE DELAYED 10 SECONDS FOR %


Explanation: A Freeze command was issued forthe named Object Service Broker system.This command cannot execute until tasksthat may span a checkpoint boundary arecomplete. Examples of such tasks are ClearTable, Building Secondary Indices, andDeleting Secondary Indices while the data isonline.

Action: The Freeze request will be retried in 10seconds. You may list the long running tasksusing the Status command.

S6BKF045AFREEZE REQUEST CANCELLED FOR %


Explanation: The Freeze request has beendelayed by long running tasks, but no workbuffers are available to reschedule therequest.

Action: Contact the system administrator.

S6BKF046WSYSTEM IS FROZEN AND CHECKPOINT %IS %% COMPLETE FOR %


Explanation: The system is FROZEN and thenext checkpoint has completed to theindicated percentage. The commit will stopwhen this reaches 100%.

Action: If possible, use the Unfreeze command toenable checkpoint processing to continue.Commit processing will stop when thischeckpoint is full.

S6BKF047EUNEXPECTED BWO STATE %


Explanation: During an attempt to open either ajournal data set or a page data set, the BWOstatus was not one of the expected values.

Action: Use IDCAMS to determine the BWOstatus and then find the reason for this statusin the IBM DFSMS documentation. If you arestill unable to resolve the problem, contactTIBCO Support.


| 261

S6BKF048EBWO STATUS READ FAILED (%-%) %


Explanation: During an attempt to open a journaldata set or a page data set, the read of theBWO failed with the indicated return/reasoncode for the indicated data set.

Action: Use the IBM DFSMS documentation todetermine the cause of the read failure. If youare still unable to resolve the problem,contact TIBCO Support.

S6BKF049EBWO STATUS SET TO % FAILED (%-%) %


Explanation: While processing either a journaldata set or a page data set, a request to set theBWO status failed with the indicatedreturn/reason code for the indicated data set.

Action: Use the IBM DFSMS documentation todetermine the cause of this failure. If you arestill unable to resolve the problem, contactTIBCO Support.

S6BKF050ELOAD FAILED FOR BWO INTERFACEMODULE IGWABWO


Explanation: On a system with BWO support,the load for the BWO interface moduleIGWABWO failed.

Action: Using the IBM documentation,determine the cause of the load failure andrectify it.

S6BKF051ICURRENT BWO STATUS % % (%-%) %


Explanation: As a result of a BWOSTATUScommand, this message is issued for onlinepage and journal data sets that supportBWO. The BWO status value appears,followed by the last action requested, withthe return/reason code from this action,followed by the data set name. Where:

• BWO_Status - is the BWO 3-byte statusfield maintained by IBM DFSMSdfpAdvanced Services module IGWABWO.The contents of this field, bwo_flags, isdescribed in the IBM DFSMSdfpdocumentation, part of the DFHSMSlibrary.

• BWO_Last_Action - this is an internalObject Service Broker BWO requestfunction. Values are:

• READ - READ status

• RESET - set BWO_Status to 000

• BWO - set BWO_Status to 100

• FORWARD - set BWO_Status to 001

• ANALYSE - ANALYSE BWO status

• DISPLAY - DISPLAY BWO status

• (return-reason code from this action) - seethe IBM DFSMSdfp documentation forinterpretation of IGWABWO Return andReason Codes.

• {datasetname} - the Object Service Brokerdata set being processed.



262 |

S6BKF052EREDOLOG-1 USER EXIT FAILUREDETECTED, DOB ABNORMALLYTERMINATED


Explanation: The Redolog-1 user exit returned anonzero return code in GPR 15. The DataObject Broker is terminated with a U320abend.

Action: Contact the Object Service Broker systemadministrator.

S6BKF053EREDOLOG-2 USER EXIT FAILUREDETECTED, DOB ABNORMALLYTERMINATED


Explanation: The Redolog-2 user exit returned anonzero return code in GPR 15. The DataObject Broker is terminated with a U320abend.


S6BKF054EFILECHPT USER EXIT FAILURE DETECTED,DOB ABNORMALLY TERMINATED


Explanation: The File Management Checkpointuser exit returned a nonzero return code inGPR 15. The Data Object Broker isterminated with a U320 abend.


S6BKF055ETABLE @CRITICALMSGS IS NOTCORRECTLY DEFINED


Explanation: During Data Object Brokerinitialization, table @CRITICALMSGS wasfound to be incorrectly defined.

Action: Contact the Object Service Broker systemadministrator to rectify the definition of@CRITICALMSGS.

S6BKF056E@CRITICALMSGS IS NOT EMPTY


Explanation: During Data Object Brokerinitialization, table @CRITICALMSGS wasfound to contain critical system messages.

Action: Contact the Object Service Broker systemadministrator, who should review themessages in table @CRITICALMSGS, takeany action required, and then delete themessages from the table.

S6BKF057IBWO NOT SUPPORTED FOR %


Explanation: As a result of a BWOSTATUScommand, this message is issued for onlinepage and journal data sets that do notsupport BWO where % is the data set name.

Action: No action is required unless BWO shouldbe supported for this data set. If BWO isrequired check that the data set is correctlyallocated on a DASD device that supportsBWO and is managed by DFSMS.


| 263

S6BKF099ITRANSACTION REQUEUED


Explanation: Deadlock avoidance logic has beeninvoked and a request redriven. Thetransaction is rolled back and retried with theexpectation that any deadlock will beresolved on the subsequent attempt.



264 |

KL: Lock Manager

S6BKL010EUNSUPPORTED LOCK MANAGERREQUEST CODE __

Source: Lock Manager

Explanation: The Lock Manager received arequest code which it is not designed toprocess.


S6BKL011ELOCK MANAGER INSUFFICIENT STORAGECODE ____


Explanation: There is insufficient Lock Managerstorage to store the Lock Manager datastructures for all the concurrent transactions,tables, parameters, keys, andgranted/waiting lock units on hand / beingrequested. Any transaction reporting thiserror gets the LOCKFAIL exception.

Action: If this error frequently interferes withObject Service Broker operation, then DataObject Broker parameter changes should beattempted (increase LOCKBUFFERS and/ordecrease MAXTHREADS). These changesonly take effect after Object Service Broker isrestarted. If problems persist, contact TIBCOSupport.

S6BKL012ELOCK STORAGE MANAGEMENT ERRORCODE ____-____


Explanation: An error has occurred in the ObjectService Broker Lock Manager's StorageManagement.

Action: Contact TIBCO Support. They will needthe complete message text including theerror code. A Lock Manager Dump may beuseful (option Z, suboption 3 from the ObjectService Broker Administration menu).

S6BKL013ELOCK MANAGER INTERNAL ERROR CODE____


Explanation: An Internal error has been detectedin the Object Service Broker Lock Manager.

Action: Contact TIBCO Support. They will needthe complete message text including theerror code. A Lock Manager Dump may beuseful (option Z, suboption 3 from the ObjectService Broker Administration menu).


| 265

S6BKL014WDEFUNCT TRANSACTION LOCKSDETECTED, USER=________


Explanation: The Lock Manager has detectedLock Manager structures for a user who is nolonger logged on to Object Service Broker.These structures are purged. This message isissued to warn that this has occurred -normally a transaction's storage should all bereleased at transaction end.

Action: If this message occurs regularly, thencontact TIBCO Support.


266 |

KP: DOB Operator Tasks

S6BKP001IOPER INITIALIZATION COMPLETED

Source: DOB Operator Tasks

Explanation: Initialization was successful for thetask supporting operator console MODIFYcommands. You can enter Object ServiceBroker MODIFY commands and receive aresponse.


S6BKP002EOPER INITIALIZATION FAILED


Explanation: An error has been encounteredduring the initialization of the Data ObjectBroker's console interface. Data ObjectBroker initialization continues but consoleservices are not available.

Action: Review the initialization messages in theData Object Broker's job log to determine thereason for the failure. Terminate and restartthe Data Object Broker at the earliestopportunity after the problem is resolved.

S6BKP005LMODIFY ' _________________________________________'


Explanation: The command received from theconsole is echoed. This verifies commandrecognition and records the command in theconsole log for the Object Service BrokerData Object Broker task.


S6BKP006IMODIFY COMMAND ACCEPTED


Explanation: This message is the standardacknowledgement that the command is validwhen no more specific reply exists.Parameter assignment has completedsuccessfully.

Action: No action usually required. If thecommand triggers an action other thanparameter assignment, check for subsequentresponses that are issued from the task whichactually performs the request.

S6BKP007EUNDEFINED EVENT CODE X' '


Explanation: This message indicates that aninvalid post code has been received by theData Object Broker's operational supporttask and cannot be processed.



| 267

S6BKP008LTIMED COMMAND INITIATED -


Explanation: This message is issued to record theprocessing of a command initiated by atimed event.


S6BKP010WSYSTEM IS DRAINING


Explanation: The command issued was:

MODIFY jobname,QUIESCE

This prevents any new user logons to ObjectService Broker and helps existing work drainout of the system. Setting the QUIESCE statehelps prepare for an Object Service Brokersystem shutdown.

Action: An Object Service Broker SHUTDOWNcommand may be issued, or normaloperation can continue by issuing thecommand:

MODIFY jobname,RESUME

S6BKP011ITRAFFIC ENABLED (QUIESCE OFF)


Explanation: The command issued was:


The flag for the QUIESCE state that occurredin Object Service Broker was reset.

Action: The command that displays theQUIESCE flag setting is:

F jobname,JOURNALSTATUS

Investigate cases, other than during ashutdown, where Object Service Brokerenters a QUIESCE state.

S6BKP013WCONSOLE MESSAGE BUFFER FREE FAILED


Explanation: The processing of operator consolemessages encountered a problem whilefreeing a message buffer. This may result infailure of the Operator Command Interface.

Action: If operator console MODIFY commandsare no longer being accepted, contact TIBCOSupport.

S6BKP014ASERVICES SUSPENDED - INITIALIZATIONFAILURE


Explanation: Services provided by theoperations support task indicated in themessage are not available due to the failureof this task to initialize.

Action: Review the initialization messages in theData Object Broker's job log to determine thereason for the failure. Terminate and restartthe Data Object Broker at the earliestopportunity after the problem is resolved.


268 |

S6BKP015ELENGTH OF SPECIFIED USER ID IS OUT OFRANGE FOR THE CANCEL OR FORCEUSERCOMMAND


Explanation: A CANCELUSER or FORCEUSERcommand was entered and the specifieduserid was not between 1 and 8 characterslong, for example,CANCELUSER=uuuuuu;nnnn. The userid(uuuuuu) must be 1 to 8 characters long.

Action: Enter the command again with thecorrect format.

S6BKP016ASERVICES TERMINATED


Explanation: The operations support servicestask indicated in the message terminated dueto an unrecoverable failure. The system willattempt a restart of the failing task.

Action: Review the Data Object Broker's job logto determine the reason for the failure andreport this problem to TIBCO Support.

S6BKP017ARE-INSTATING ________, SERVICES


Explanation: This message indicates thatautomatic recovery is in progress for theservice indicated in the message.

Action: Begin an investigation into the cause ofthe initial failure. If the service is successfullyreinstated, no immediate action is required.

S6BKP018ARESTART OF ________ SERVICES ________


Explanation: This message is issued to indicatethe success or failure of the restart action forthe indicated operations service.


S6BKP019A________ SERVICES SUSPENDED - RESTARTLIMIT EXCEEDED


Explanation: The operations support serviceindicated in the message could not berecovered after a failure. These services aredisabled until the Data Object Broker isrestarted.

Action: Review the Data Object Broker's job logto determine the reason for the failure andreport this problem to TIBCO Support.

S6BKP020E_____________ CANNOT BE ASSIGNED AVALUE


Explanation: A MODIFY command was issuedin the form "command=value". Theparticular command verb specified isdefined to be a one word action commandwithout any assigned value. The command isrejected.

Action: The command can be reissued withoutan assigned value, if appropriate. If in doubt,refer to the operator commanddocumentation in the Installation andOperations manual.


| 269

S6BKP021E_____________ COMMAND CONTAINSINVALID CHARACTER(S)


Explanation: The indicated command containscharacters that are not alphabetic. Thecommand is rejected.

Action: Verify the spelling of the command. Referto the Installation and Operations manual ifnecessary.

S6BKP022E_____________ COMMAND IS AMBIGUOUS


Explanation: The indicated command has beenabbreviated so that it is no longer unique.The command is rejected. Object ServiceBroker MODIFY commands may be spelledin full or abbreviated through truncation. Forexample, SNAPOVERRIDE, SNAPOVER, orSNAPO are all accepted. Excessivetruncation results in abbreviations that canbe one of several commands. For example,SNAP might be any one of SNAPCLASS,SNAPREMOTE, SNAPQUERY,SNAPOVERRIDE, or SNAPVOLSER.

Action: Spell the parameter keyword name morefully, or completely. Generally, 5 charactersare adequate to achieve uniqueness.(TRACEID and TRACEOFF are exceptions).Refer to the Installation and Operationsmanual if necessary.

S6BKP023E_____________ COMMAND IS NOT DEFINED


Explanation: The indicated command (only thefirst 12 characters appear in the message) isnot defined to Object Service Broker. Youmay have used an unrecognizableabbreviation. The command is rejected.

Action: Verify the spelling of the command. Referto the Installation and Operations manual ifnecessary. Abbreviations are only recognizedif they are spelled the same as the fullcommand up to the point of truncation.

S6BKP025ECOMMAND NOT PROCESSED, COULD NOTOBTAIN BUFFER


Explanation: The Data Object Broker was notable to obtain the work area needed toprocess an operator request. This is usually atemporary situation and should be resolvedalmost immediately.

Action: Reenter the rejected operator command.If the problem persists, obtain a dump of theData Object Broker and terminate it at yourearliest convenience. Notify TIBCO Support.


270 |

S6BKP026ECOULD NOT OBTAIN WORK BUFFER FORTIMER COMMAND


Explanation: The Data Object Broker was notable to obtain the work area needed toprocess an the indicated timed service. Thisis usually a temporary situation and shouldbe resolved almost immediately.

Action: If possible enter the command from theoperator console. If the problem persists,obtain a dump of the Data Object Broker andterminate it at your earliest convenience.Notify TIBCO Support.

S6BKP027Exxxxxxxx PARM NOT DYNAMICALLYMODIFIABLE


Explanation: xxxxxxxx parameter is onlymodifiable at STARTUP

Action: None - self-explanatory.

S6BKP030E_____________ MUST BE ASSIGNED A VALUE


Explanation: A MODIFY was issued as a oneword action command. The particularcommand verb is defined to be for a"keyword=value" command. The commandis rejected.

Action: Provide an appropriate value whenissuing this command. Refer to theInstallation and Operations manual ifnecessary.

S6BKP031E_____________ SPECIFIED VALUE HAS TOOMANY CHARACTERS


Explanation: The value assigned to the keywordhas too many characters. The command isrejected.

Action: Reenter the command with an acceptablevalue. Refer to the Installation andOperations manual if necessary.

S6BKP032E_____________ SPECIFIED VALUECONTAINS INVALID CHAR(S)


Explanation: The value assigned to thecommand failed its edit validity check. Thiserror occurs for any non-alphanumericvalue, or for a discrepancy between editspecifications and the input provided. Thecommand is rejected.


S6BKP033E_____________ SPECIFIED VALUE NOTVALID QUALIFIER/DSNAME


Explanation: The value assigned to thecommand failed its validity check. A data setname or qualifier, member name, or otherentity with similar syntax was expected. Thecommand is rejected.



| 271

S6BKP034E_____________ SPECIFIED VALUE IS OUT OFRANGE


Explanation: The value assigned to the keywordis too big or too small.


S6BKP035E_____________ ALREADY ASSIGNED -CANNOT MODIFY


Explanation: The specified parameter waspreviously assigned a value. Further changesare not permitted. The MODIFY commandfor this parameter is provided to permitassignment only if the parameter wasomitted from the initialization parameters.

Action: This parameter is normally specified as aData Object Broker Initialization parameter.Changes are effective at the next Data ObjectBroker startup.

S6BKP036E_____________ REJECTED, SHUTDOWN INPROGRESS


Explanation: The specified request was rejectedbecause Object Service Broker had alreadyaccepted a shutdown request.

Action: Object Service Broker is coming down --no action required.

S6BKP037ENOT MODIFIED


Explanation: The value of the parameterindicated in the variable portion of themessage text is not changed as requested.Refer to any preceding messages for thecause of the failure.

Action: Correct the request as indicated by theaccompanying messages and resubmit therequest.

S6BKP038EJOURNAL ___ CANNOT SUPPORTCHPAGELIMIT OF ____


Explanation: A request has been made toincrease the value of the CHPAGELIMITparameter; however, while validating thisrequest, the Data Object Broker determinedthat there was not sufficient space in theJournal data set indicated in the message tosupport this change. The request is rejected.

Action: Select a lower value and retry the requestor reallocate the failing Journal data set to asize which will support this request andreissue the request.

S6BKP039EREDO LOG CANNOT SUPPORTCHTRANLIMIT OF ____


Explanation: A request has been made toincrease the value of the CHTRANLIMITparameter; however, while validating thisrequest, the Data Object Broker determined


272 |

that there was not sufficient space in theREDOLOG data set indicated in the messageto support this change. The request isrejected.

Action: Select a lower value and retry the requestor reallocate the REDOLOG data set to a sizewhich will support this request and reissuethe request.

S6BKP040LSYSTEM RUNNING ___ __ ____ __:


Explanation: This message provides a timestampin the SYSLOG.


S6BKP041ECHPAGELIMIT OF ___ EXCEEDS 15% OFRESIDENT PAGES


Explanation: While validating a request toincrease the value of the CHPAGELIMITparameter, the Data Object Brokerdetermined that the new value would exceedthe maximum allowed based on the size ofthe Resident Page Pool. The request isrejected.

Action: Select a lower new value forCHPAGELIMIT and reissue the request.

S6BKP042ICHECKPOINT MAXIMUM PAGES = ______,TRANSACTIONS = ______


Explanation: This message is issued asconfirmation of the new values set by arequest to modify either the CHPAGELIMITparameter or the CHTRANLIMIT parameter.


S6BKP045ITASK STATUS BUSY-TIME TCB-SECEVENTS MSGS INFLT M-CON


Explanation: This is the heading line forinformation displayed in response to theObject Service Broker Data Object BrokerStatus command:

F jobname,CRSTATUS

Action: No action is required. Refer also to theexplanations for messages S6BKP046I andS6BKP047I.

S6BKP046I' _________ __:__:__.__ ____.___'


Explanation: These lines display information inresponse to the Object Service Broker DataObject Broker Status command:

F jobname,CRSTATUS.

One status line appears for the Data ObjectBroker main task and attached subtasks.During routine operation these are numbers0-4 and 6. If issued while a shutdown is inprogress, any task which has properlyterminated is absent.


| 273

Subtasks are most commonly in READYstatus; they go into ACTIVE status whenhandling a unit of work and return toREADY state when complete. Busy time andTCB time are displayed for each. CRSTATUSalways shows Task 6 as ACTIVE because it isactively generating the CRSTATUS display.

The presence of one or more asterisksbetween BUSY MM:SS and TCB TIMEidentifies a situation where the TCB has beenactive nonstop processing events - A task hasbeen active in excess of one second of clocktime (*) or over 10 seconds (**). In such casesthe TCB SEC amount shown may be lessthan the actual current value. A problemmay have occurred in the TCB.

Action: If any task is flagged with two asterisks(**), investigation is required. Start the ObjectService Broker ADMINISTRATOR clist checksystem activity (option s monitoring), useractivity and usage statistics. Contact TIBCOSupport if a system problem is detected.Otherwise, no action is required. Refer toexplanations for messages S6BKP045I andS6BKP047I.

S6BKP047I_______ I/O _____.___ SRB _____.___ TCB


Explanation: This is the final summary line forinformation displayed in response to theData Object Broker Status command:

F jobname,CRSTATUS

Data Object Broker Address Space totals areshown. In general the TCB time valuereported on this line will be greater than butclose to the sum of the individual task TCBSEC values.

Action: No action required. Refer also toexplanations for messages KP045I andKP047I.

S6BKP050ID/S MODE JRN PAGES USED READ WRITES


Explanation: These are the headings for datadisplayed in response to the command:

F jobname,DBSEGMENTSTATUS

One status line appears for each databasesegment defined in the DBDLIB. The firstletter is the status:

• O (Online)

• F (Offline)


S6BKP051Ia num name d/s mode jrn pages used readwrites


Explanation: This informational messageprovides the display under the S6BKP050headings:

• A (a) can be O for online or F for offline (ifoffline, Pages, Used, Read, and Writes arenot displayed)

• ID (num) is the segment number asspecified in the DBDLIB

• NAME (name) is the name of the segmentas specified in the DBDLIB

• MODE (mode) is the processing mode (canbe R/W -- read/write, R -- read only, and -S -- system segment)

• JRN (jrn) indicates whether journaling isactive for the segment (yes or no)

• PAGES (pages) is the number of pages inthe segment

• USED (used) is the number of used pagesin the segment


274 |

• READ (read) is the number of physicalpage reads against the segment

• WRITES (writes) is the number of physicalpages written to the segment


S6BKP052EDBSEGMENT ________ IS A 'SYSTEM'SEGMENT - REQUEST DENIED


Explanation: You entered one of the followingcommands:

F jobname,DBONLINE=segment_number

F jobname,DBONLINE=segment_name

against a segment which has been defined inthe DBGEN as required by the system (orsegment 0 which is required by definition).The request is rejected.

Action: Do not attempt to take a requiredsegment offline while Object Service Brokeris running. Any batch maintenance of thesesegments requires that the Object ServiceBroker system be shut down.

S6BKP053WDBSEGMENT ________ IS NOT DEFINED



F jobname,DBOFFLINE=identifier

F jobname,DBONLINE=identifier.

The DBSEGMENT that you specified is notdefined.

Action: To see the names and numbers of thesegments that are available, enter thiscommand:

F jobname,DBSEGMENTSTATUS

S6BKP054WDBSEGMENT ________ IS ALREADY ONLINE


Explanation: You entered the command:

F jobname,DBONLINE=identifier

but the segment is already online.


S6BKP055WDBSEGMENT ________ IS ALREADYOFFLINE


Explanation: You entered the command

F jobname,DBOFFLINE=identifier

but the specified DBSEGMENT is alreadyoffline.


S6BKP056WDBSEGMENT ________ VARY ALREADYACTIVE - REQUEST DENIED


Explanation: The DBONLINE or DBOFFLINEcommand you entered was rejected becausethere was already another DBONLINE orDBOFFLINE command being processed forthe requested segment.

Action: Wait for the previous DBONLINE orDBOFFLINE command to complete, andthen reenter your request if needed.


| 275

S6BKP057WDBSEGMENT ________ IS ONLINE -REQUEST DENIED


Explanation: An operator initiated request todisable Journaling for the segment identifiedin the message was denied as the segmentwas still online to the Data Object Broker.

Action: Take the desired segment offline via theDBOFFLINE command, and reissue thecommand to disable journaling for thesegment.

S6BKP058AWARNING, SEGMENT=________ IS ___%FULL


Explanation: When Object Service Brokerexecution crosses the midnight boundary, allsegments are checked to ensure that thespace utilization has not exceeded the 80%threshold. This message is issued once foreach segment that has exceeded thethreshold.

Action: It is recommended that you increase thenumber of free pages available either bycleaning up or moving existing tables, or byincreasing the size of the data sets within thesegment.

S6BKP060IJRNL# STATUS % DATE TIME BKUP DEFRQSCE


Explanation: You issued the command:


Messages S6BKP060I and S6BKP061I areheadings and data in response.

Normally, one of the Journals is ACTIVE, theother is READY, and all flags are N. When aJournal becomes full, its status becomesOFFLINE or DEFER and the BKUP andDEFR flags are set to Yes. When thecorresponding Journal spin job completessuccessfully, the BKUP and DEFR flags arereset, and the OFFLINE Journal becomesREADY.

The PEND flag is set to Yes by thecommands:

SPINSUBMIT=Checkpoint SPINSUBMIT=Immediate

The flag is reset to No by using:

SPINSUBMIT=Notnow

The QUIESCE flag is set to Yes during anObject Service Broker Shutdown. It may alsobe set to Yes if a Journal fills and there is noREADY alternate Journal. In such a case,steps must be taken to resolve the Journalsituation and the QUIESCE state can then beended using:

F jobname,RESUME

Action: Usually no action is required. Correctdetected Journal problems as necessary.

S6BKP061I_' ______ ______ _ _ _'


Explanation: Refer to message S6BKP060I.

Action: Refer to message S6BKP060I.


276 |

S6BKP062WJOURNALLING ALREADY ________ FORSEGMENT ________


Explanation: An operator initiated request tomodify the Journaling status for the segmentidentified in the message was denied sincethe Journaling status for the segment wasalready in the requested state.

Action: Reissue the command specifying thecorrect Journaling status.

S6BKP063WJOURNALLING ________ FOR SEGMENT________


Explanation: This message is issued to confirm achange in the Journaling status for thesegment shown in the message text.

Action: No further action required.

S6BKP064IMAXIMUM USERS =_____ (AS INITIALIZED)


Explanation: You issued the command

F jobname,USERMAX=####

#### is a one to four digit maximum usercount. The message was issued because ####exceeded the MAXUSERS value in effectwhen Object Service Broker was started. Thisvalue can be adjusted but not increasedbeyond the initial value until the next timethat Object Service Broker is restarted.

Action: No further action required.

S6BKP065ILOGGED ON USERS/DBMS/OPER/JOBS



F jobname,USERLIST

S6BKP065I and S6BKP066I are headings anddata in response. They are followed bysummary messages S6BKP067I andS6BKP068I. If no Object Service Broker usersare logged on, only S6BKP067I andS6BKP068I are issued.

Object Service Broker connections areidentified by their userid. The format of thedisplay is ctuuuuuuuu, where:

• c is the connection type

• t is a trace indicator

• uuuuuuuu is the userid

If the trace indicator is "+", it indicates theconnection is currently being traced. A blankor "-" has no significance other than aseparator.

The valid connection types are:

• blank - TSO Execution Environment User

• C - CICS Execution Environment user

• N - Native Execution Environment user

• I - IMS/DC Execution Environment user

• U - Solaris Execution Environment user

• t - Other Execution Environment user

• J - Batch Job

• D - DBMS Server connection or OutboundPeer (HRN)

• O - Operator connection

• P - Inbound Peer connection (HIN)

• L - Connection that is in the process oflogging on

• ? - Unknown connection type



| 277

S6BKP067IUSERS DBMS OPER JOBS OTHER AVAIL


Explanation: You issued one of the followingcommands

. F jobname,USERLIST

. F jobname,USER

S6BKP067I and S6BKP068I are headings anddata in response. The count of users, DBMSgateways, batch jobs, and operator interfaceusers is provided, as well as the number ofavailable slots.


S6BKP068I_' ____ _____ _____ _____ _____ _____'


Explanation: Refer to message S6BKP067I.


S6BKP069IJOURNALLING DISABLED BYINITIALIZATION PARAMETER


Explanation: This message is issued in responseto an operator request to display the status ofthe Data Object Broker's JOURNAL data sets.Status cannot be displayed as journaling wasdisabled at initialization by theJOURNALS=NO directive in theinitialization parameters.


S6BKP070IGTF STATUS GTF ID SSTRACE MSGTRACE


Explanation: You issued the followingcommand:

F jobname,GTFSTATUS

S6BKP070I and S6BKP071I are headings anddata in response to the command. Thecurrent settings of the various tracingcontrols are displayed.


S6BKP071IACTIVE X'0__' ___


Explanation: This message provides the datadisplay for message S6BKP070I.


S6BKP072EREQUEST DENIED - CANNOT CHANGEMODE FOR SEGMENT 000


Explanation: An operator request was made tochange the base segment's recording mode toread-only. This segment MUST remain inread/write mode. The request is rejected.



278 |

S6BKP073ESEGMENT ________ ALREADY IN ________MODE


Explanation: An operator request has beenreceived to change the recording mode of theindicated segment; however, the Data ObjectBroker found that the segment was alreadyset to the requested mode.


S6BKP075WGET WORK BUFFER FAILED


Explanation: A CANCELUSER or STOPSERVERcommand was issued to terminate a user orDBMS gateway. Because no work buffer wasavailable, the request could not be processed.

Action: The command may succeed if reissued. Ifthis message occurs again, the reason for thelack of work buffers should be investigated.

S6BKP076WFREE WORK BUFFER FAILED


Explanation: Upon completion of externalcommand processing (e.g., fromS6BTLCMD), the work buffer used to carrythe command could not be released.


S6BKP078ECANCEL DENIED - LOGOFF INITIATED AT________ ON _________, WAITINGFOR___________


Explanation: A request was received by the DataObject Broker to cancel a specified usersession that is currently being terminated.The request cannot be fulfilled because theprocessing for termination has alreadypartially completed. The connection has beenwaiting for a response from the displayeddate and time from the identified externalresource.


S6BKP079ECANCEL DENIED - USER LOGOFFDEFERRED



F jobname,CANCELUSER=userid

The specified user is in deferred logoffstatus. The user's logoff cannot proceed untila coordinated external resource updatehappens. No action is taken.

Action: If unable to resolve a problem with a userhung up in deferred logoff status, thencontact TIBCO Support.

S6BKP080WSPECIFIED USER NOT LOGGED ON



F jobname,action=userid


| 279

The specified USER was not logged on toObject Service Broker. No action is taken.

Action: No action required. The command:

F jobname,USERLIST

displays a list of the userids logged on toObject Service Broker.

S6BKP081ECANCEL DENIED - DBMS SERVER, USESTOPSERVER



F jobname,CANCELUSER=server_id

The ID specified is a DBMS gateway. Noaction is taken.

Action: Use the STOPSERVER command to shutdown a DBMS gateway.

S6BKP086WJOURNAL SPIN FLAG ALREADY INREQUESTED STATE



F jobname,SPINENABLE=YES or NO

The spin flag is already set to whatever yourequested. No action is taken.


S6BKP087WJOURNAL SPIN FLAG RESET ONLY - NOOFFLINE JOURNAL



F jobname,SPINENABLE=YES

No Journal was offline; therefore, no Journalwas reopened. Probably, a previousMODIFY command forced SPIN deferral formaintenance purposes.

Action: No action is required. You may want todisplay the current Journal status with thecommand:


S6BKP089WUNEXPECTED USER ID FOUND INSPECIFIED COMMAREA


Explanation: A cancel user request was issuedfrom the S6BTLADM utility. The bufferidentified as containing the user informationis invalid.

Action: Retry the cancel request. If the errorrecurs, contact TIBCO Support.

S6BKP090ICHECKPOINT REQUEST TERMINATED -NO PENDING UPDATES


Explanation: An operator has entered theCHECKPOINT command to flush thepending changes to the database. There wereno updates pending, so the request isignored.



280 |

S6BKP091EREQUEST DENIED - NO ALTERNATEJOURNALS AVAILABLE FOR RECORDING


Explanation: An attempt was made to spin thelast available journal via the SPINSUBMIToperator command. The request is rejected.

Action: Determine the reason that the alternatejournal is not available. Correct the situationand reissue the command.

S6BKP092EREQUEST DENIED - JOURNAL ___ IS NOTCONFIGURED


Explanation: An operator request to vary theindicated journal data set has been rejected asthe journal data set was not defined in theDBGEN.

Action: If more journal data sets are required,modify the journals definition in the DBGENso that more are available the next time theData Object Broker is started.

S6BKP093EREQUEST DENIED - JOURNAL ___ISALREADY


Explanation: An operator request has beenreceived to vary the indicated journal dataset; however, the Data Object Broker foundthat the journal was already set to therequested state.


S6BKP094EREQUEST DENIED - CANNOT CHANGESTATUS OF ACTIVE JOURNAL


Explanation: An attempt has been made to varyoffline the active journal data set. Thisrequest is rejected.

Action: If the active journal data set must betaken offline, issue a journal spin command.Once the spin completes, the journal can besafely taken offline.

S6BKP095EREQUEST DENIED - JOURNALLINGSERVICES ARE NOT AVAILABLE


Explanation: An operator command has beenentered to manipulate one or more journaldata sets; however, JOURNALS=NO wasspecified in the Data Object Broker'sinitialization parameters. The request isignored.


S6BKP096EVARY REQUEST ACCEPTED FOR JOURNAL


Explanation: An operator initiated vary requestfor the indicated journal data set has beensuccessfully received by the Data ObjectBroker.



| 281

S6BKP097L________ TERMINATED BY SHUTDOWN


Explanation: This message displays the name ofa user session that has been terminatedbecause Object Service Broker is being shutdown.


S6BKP098EVARY REQUEST ALREADY ACTIVE FORJOURNAL ___ - REQUEST DENIED


Explanation: A vary request has been receivedfor the indicated journal data set, however,the Data Object Broker is already processinga vary request for this journal.

Action: Wait for the current vary request tocomplete and then reenter your request. Ifthe current request does not complete, take adump of the Data Object Broker, and restartat your earliest convenience. Contact TIBCOSupport.

S6BKP099WSHUTDOWN COMMAND ACCEPTED


Explanation: The command:

F jobname,SHUTDOWN

executed successfully.


S6BKP100EREQUEST DENIED - SPIN OPTION IS STC


Explanation: A request has been issued againstthe Data Object Broker which acts upon SPINJCL; however, the Data Object Broker wasinitialized to use STC for spin jobs. Thisrequest is denied.

Action: If the intent of the request was to modifythe SPIN JCL, then simply modifying theSTC PROC is all that is necessary. Otherwise,this request is illogical for the environment,and subsequently no further action isrequired.

S6BKP101ISPIN LOAD REQUEST FOR JOURNAL ___ACCEPTED


Explanation: This message is issued as anacknowledgement of a SPINLOAD requestfor the indicated Journal's SPIN JCL.


S6BKP102ESPECIFIED PEER NOT DEFINED,STARTPEER COMMAND REJECTED


Explanation: The peer you specified is notdefined.

Action: Check the spelling, or check the peerdefinitions with S6BTLADM.


282 |

S6BKP103ESPECIFIED PEER IS ALREADYATTEMPTING CONNECTIONS, STARTPEERCOMMAND REJECTED


Explanation: The Peer connection is currently inprogress. When processing of the Peercompletes, all required connections that areviable should have been established.

Action: Retry the command at a later time ifrequired.

S6BKP104ILOCKTRACE (ON/OFF/MARK POINT), ONTABLE ________, ON USER ______


Explanation: This informational message ispresented to show the lock tracecharacteristics for the trace just activated.

Action: No action

S6BKP105WINVALID LOCKTRACE PARAMETER; "ON","OFF", "T=...", "U=..." OR "*" ACCEPTABLE


Explanation: This warning identifies theacceptable parameters for a locktracerequest.

Action: Reenter the locktrace request with thecorrect parameter values.

S6BKP106WLOCKTRACE "T=" OR "U=" REQUIRE TABLENAME OR USER ID


Explanation: The LOCKTRACE request wasinvalid because of missing information.

Action: Reenter the request with all requiredinformation.

S6BKP107W"FORCEUSER" COMMAND REPLACEDWITH "CANCELUSER" FOR USER ________,NO PREVIOUS CANCEL


Explanation: Before a FORCEUSER commandcan be processed a CANCELUSER mustalready be active for the specified user. TheFORCEUSER is intended to provide a lastresort method terminating a hung user,before it is attempted a CANCELUSER mustbe attempted.

Action: The command is downgraded to aCANCELUSER and processed.

S6BKP108AFORCEUSER COMMAND ISSUED AGAINSTUSER ________


Explanation: This message is produced to ensurethere is a record of the use of theFORCEUSER command.



| 283

S6BKP109WSHUTDOWN COMMAND ACCEPTED,DEFERRED DUE TO CURRENTPROCESSING


Explanation: The shutdown command has beenaccepted. There is currently workoutstanding that must be completed beforethe shutdown can proceed. In particular,there is a long running transaction such as atable clear or secondary index build or deleteinflight. When the long running transactioncompletes, the shutdown request willautomatically continue and the Data ObjectBroker will terminate.

Action: No user intervention is required.

S6BKP110IDUPLICATE ______ DETECTED


Explanation: The console command detectedmultiple userid/termids and needs to knowwhich userid/termid to act upon.

Action: Reissue the command with ";xxxx",where xxxx is the commnum from messageS6BKP112I.

S6BKP111IUSERID TERMID JOBNAME TYPECOMMNUM


Explanation: These are the headings for messageS6BKP112I.


S6BKP112Iuuuuuuu tttttttt jjjjjjjj tttttttttttt cccccc


Explanation: S6BKP111I shows headings for thedata rows in S6BKP112I; the data inS6BKP112I is used to determine the differentuserid/termids.

Action: Determine which commnum to use whenthe console command is reissued.

S6BKP113ITOTAL NUMBER OF DUPLICATES ____


Explanation: This message displays the count ofduplicate entries.


S6BKP114AREPEAT COMMAND WITH "command =userid;commnum"


Explanation: The console command could notdetermine which duplicate entry to act on.S6BKP112I lists the commnum of allduplicates.

Action: Reissue the console command with";commnum" at the end of the command,where the commnum is from the precedingS6BKP112I messages.


284 |

S6BKP115ENO DATA SENT, COMMAND REJECTED


Explanation: The console command wasreissued but no data was detected beyond ";".

Action: Reissue the command with thecommnum.

S6BKP116ECOMMNUM NOT NUMERIC, COMMANDREJECTED


Explanation: The console command after the ";"was not numeric. The commnum is anumeric value.

Action: Reenter the console command with anumeric value for the commnum.

S6BKP117ECOMMNUM TOO LARGE, COMMANDREJECTED


Explanation: The commnum entered was greaterthan the highest allocated commnum.

Action: Check the value of the commnum andreenter the command.

S6BKP118ISPECIFIED COMMAREA NUMBER OUT OFRANGE, REQUEST REJECTED


Explanation: A CANCELUSER request wasissued with an explicate commarea number,the supplied commarea number is out ofrange.

Action: Correct the CANCELUSER request andresubmit.

S6BKP119ESWEEPLIMIT FORMAT INVALID;EXPECTED "SWEEPLIMIT=(LIMIT,USERID)"


Explanation: When attempting to set a SweepLimit for a specific user, you used an invalidcommand format.

Action: Re-enter the command in the requiredformat.

S6BKP120ESWEEPLIMIT REQUEST COMMAREANUMBER CONTAINS INVALID NUMERICCHARACTERS


Explanation: When entering a command to set asweep limit, you used invalid characters inthe numeric portion of the command.

Action: Re-enter the command with the correctformat.


| 285

S6BKP121ESWEEPLIMIT REQUEST SPECIFIED ACOMMAREA NUMBER THAT IS OUT OFRANGE


Explanation: When entering a Sweep Limit, youspecified an out-of-range value.

Action: Refer to the Object Service Brokerdocumentation and re-enter the commandwith a valid limit.

S6BKP122ESWEEPLIMIT REQUEST IDENTIFIES AUSERID AND COMMAREA NUMBER THATDO NOT MATCH


Explanation: In your Sweep Limit command,either the userid or the relative connectionnumber are in error.

Action: Re-enter the command with the correctuserid and COMMAREA number.

S6BKP124ESWEEPLIMIT REQUEST LIMIT CONTAINSINVALID NUMERIC CHARACTERS


Explanation: The Sweep Limit specified in thecommand has invalid numeric characters.

Action: Re-enter the command with a validSweep Limit value.

S6BKP125ESWEEPACTION FORMAT INVALID;EXPECTED"SWEEPACTION=(ACTION,USERID)"


Explanation: The specified action to be invokedwhen a user exceeds the Sweep Limitthreshold is invalid.

Action: Refer to the Object Service Brokerdocumentation for valid actions and re-enterthe command.

S6BKP126ESWEEPACTION REQUEST COMMAREANUMBER CONTAINS INVALID NUMERICCHARACTERS


Explanation: When specifying the action to beinvoked when a Sweep Limit Threshold isexceeded, you entered a COMMAREAnumber that contains invalid numericcharacters.

Action: Re-enter the command with a validCOMMAREA number.

S6BKP127ESWEEPACTION REQUEST SPECIFIED ANCOMMAREA NUMBER THAT IS OUT OFRANGE


Explanation: In your attempt to specify theaction to be taken when the Sweep Limitthreshold is exceeded, the COMMAREAnumber specified is not valid. It exceeds thenumber of the pool buffers available.

Action: Re-enter the command with a correctCOMMAREA number.


286 |

S6BKP128ESWEEPACTION REQUEST IDENTIFIES AUSERID AND COMMAREA NUMBER THATDO NOT MATCH


Explanation: The COMMAREA numberspecified in the command identifies aconnection for a userid other than the onesupplied.

Action: Re-enter the command with the correctuserid and COMMAREA number.

S6BKP129ESWEEPACTION SPECIFIED USERID COULDNOT BE LOCATED


Explanation: The userid specified in theSWEEPACTION command could not belocated on the Data Object Broker.

Action: Verify the userid and re-enter thecommand.

S6BKP130ESERVER COMMAND - PROCESSINGBUFFER NOT CURRENTLY AVAILABLE,RETRY


Explanation: A buffer to retain the gatewaycommand control block could not beobtained from the system.

Action: This is most likely a temporary situation,retry the gateway command.

S6BKP131ESERVER COMMAND - SERVER TYPE MUSTBE A 3 CHARACTER VALUE FOLLOWED BYA COMMA


Explanation: The system was not able to identifythe desired resource type to process becausethe message format was incorrect.

Action: Correct the message format and reissuethe request.

S6BKP132ESERVER COMMAND - SERVER TYPE WILD-CARD MUST BE "*," OR "***,"


Explanation: The gateway command was issuedwith the gateway type value with wildcards.However the format of the wildcard isinvalid. The type value must either becompletely specified or completelywildcards.

Action: Correct the gateway command requestand reissue it.

S6BKP133ESERVER COMMAND - FORMAT"TYPE,GROUP,COMMAND" ONE OR MORESUB-PARAMETERS MISSING.


Explanation: The format of the gatewaycommand was incorrect.

Action: Resubmit the request using the correctformat.


| 287

S6BKP134ESERVER COMMAND - SERVER GROUPMUST BE 1 TO 8 CHARACTERS FOLLOWEDBY A COMMA


Explanation: When extracting the group namefrom the input command, either the groupname was too long or a comma was missing.

Action: Correct the request and reissue it.

S6BKP135ESERVER COMMAND - SERVER GROUPWILD-CARD VALUE DOES NOT ACCEPTEMBEDDED "*"


Explanation: The group ID was entered using a *to indicate a wildcard the * must be followedimmediately by a "," to indicate the end of thegroup name.


S6BKP136ESERVER COMMAND - SERVER COMMANDIS TOO LONG TO PROCESS, LIMITED TO 48CHARACTERS


Explanation: The longest gateway command thatcan be processed is 48 bytes. The requestexceeds this limit. If this restriction causes aproblem, contact TIBCO Support.


S6BKP137ESWEEPACTION COMMAND ACTIONINVALID; USELOG,NOLOG,SMF,NOSMF,DUMP ORNODUMP


Explanation: The action specified in aSWEEPACTION command is invalid. Themessage identifies the acceptable actions.

Action: Re-enter the command with a validaction.

S6BKP138ESWEEPACTION REQUEST SET ACTION TOSMF, SMF RECORD IS NOT ACTIVE


Explanation: The action specified in theSWEEPACTION command specifies an SMFrecord to be cut when the threshold isexceeded. The current Data Object Brokerenvironment is not producing any SMFrecords.

Action: Either select a different action or set theSMFRECORD parameter to start SMFlogging and re-enter the command.

S6BKP200WTIMER ________ COMPLETED, RC = __,ENTRY =


Explanation: This message is provided asfeedback of the completion of a timedservices maintenance request.



288 |

S6BKP201ETIMER INTERVAL GREATER THAN 1 DAY,ENTRY DISABLED


Explanation: A timed services entry has beenencountered which specifies an intervalgreater than 1 day (1440). This entry isdisabled, and Data Object Broker processingcontinues normally.

Action: This is an internal error condition.Contact TIBCO Support for furtherassistance.

S6BKP202EPROCESSING BUFFER NOT AVAILABLE TOPROCESS ____________


Explanation: A buffer was not available toprocess the indicated timed services request.The request is ignored.

Action: Contact TIBCO Support for furtherassistance.

S6BKP203ECOMMAND % REJECTED; SYSTEM ISFROZEN: %


Explanation: Only certain commands may beissued while the system is frozen.

Action: Wait until the system is unfrozen andreissue the command.

S6BKP204ISYSTEM IS % %


Explanation: This message is issued as a result ofa Status operator command. The systemstatus is ACTIVE, FROZEN, FREEZING, orUNFREEZING.


S6BKP205LLONG RUNNING TASK ACTIVE id #=numTYPE=_ COMM=comm-type SOURCE= xxxx


Explanation: This message is issued for each longrunning task active at the time of a Statusoperator command. See message S6BKC016for the meaning of the fields displayed in thismessage.


S6BKP206ECOMMAND % REJECTED; INVALID STATEFOR %


Explanation: This message appears as a result ofone of the following actions:

• You issued a Freeze command and you donot have a valid license for this feature

• You issued a Freeze command while thesystem was already frozen

• You issued an Unfreeze command whilethe system was not frozen.

Action: Reissue the command when the systemstate is the appropriate one.


| 289

S6BKP208IBACKUP WHILE OPEN SUPPORT ENABLED


Explanation: This message is issued as a result ofa STATUS command on a system whereBWO support is licensed and enabled.


S6BKP209IBACKUP WHILE OPEN NOT ENABLED


Explanation: This message is issued as a result ofa BWOSTATUS command on a system that isnot enabled for BWO support.

Action: BWO support may be enabled using theBWO Data Object Parameter if required.

S6BKP210ECOMMAND ______________ REJECTED;SYSTEM IN SECONDARY MODE


Explanation: The system is in secondary modeand a command that is only valid when thesystem is in primary mode has been entered.

Action: Correct the command that is entered.

S6BKP211ECOMMAND REJECTED:


Explanation: A switch command was for one ofthe following reasons:

• FORCE OR ALLOW REQUIRED: Theswitch command requires either theFORCE or ALLOW option to completesuccessfully.

• INVALID MEMBER NAME: The membername specified is not a member of thecurrent XCF group

• XCF NOT ENABLED: The Data ObjectBroker is not running in XCF mode, theSwitch command is not supported.

• SWITCH IN PROGRESS: A SWITCH isalready in progress for this Data ObjectBroker

• LRT IN PROGRESS: A Long RunningTransaction, such as a Clear Table, is inprogress. The SWITCH command isignored. Retry the SWITCH commandafter the Long Running Transaction hascompleted.

• WORK BUFFER UNAVAILABLE: A workbuffer was not available to schedule theSWITCH. Retry the SWITCH later.

Action: Correct the Switch command and re-issue it.


290 |

KQ: Ready To Use Queue Task

S6BKQ001IRTUQTASK INITIALIZATION COMPLETEDSUCCESSFULLY

Source: Ready To Use Queue Task

Explanation: This informational message notifiesthe operator that the sub-task RTUQTASKhas been started successfully.


S6BKQ002WRTUQTASK HAS INITIATED ACHECKPOINT DUE TO INSUFFICIENTBUFFER ALLOCATION

Source: Ready To Use Queue Task

Explanation: The RTUQTASK is responsible forensuring that there are an adequate numberof buffers available to store online pageimages. When attempting to replenish thesupply due to critically low levels, no bufferswere available.

Action: No immediate action is required. TheObject Service Broker administrator shouldconsider increasing the size of theRESIDENTPAGES.


| 291

KR: DOB Redo Tasks

S6BKR000IDB RECOVERY IN PROGRESS

Source: DOB Redo Tasks

Explanation: The Recovery task is performingthe required recovery.


S6BKR001I_____ REDO TRANSACTIONS RECOVERED


Explanation: The Recovery task is indicatinghow many transactions will be redone fromthe redolog.


S6BKR002AREDOLOG RECOVERY INFORMATIONNOT AVAILABLE, RECOVERING CACHEONLY


Explanation: During the restart processing in theData Object Broker, data was expected in theREDOLOG to be reapplied. This data wasnot available.

Action: There is little that can be done from theObject Service Broker standpoint. The data isrecovered to the last completed checkpoint.Any changes since that point will be lost.

S6BKR003EPRIMARY AND DUPLEX REDOLOGDIFFERENCE FOUND


Explanation: When processing the primary andthe duplex copy of the REDOLOG it wasdetermined that the two were not identical.

Action: Recovery is failed and the Data ObjectBroker initialization will terminate.

S6BKR004EREDOLOG FORMAT ERROR DETECTED


Explanation: When reading the REDOLOG todetermine recovery requirements the formatof the REDOLOG was deemed to be invalid.This should only occur after the REDOLOGhas been reformatted to upgrade to a newlevel of code.

Action: Reformat the REDOLOG using thecorrect level of S6BTLFRL.


292 |

S6BKR005EREDOLOG NOT FORMATTED AFTERPREVIOUS FAILURE


Explanation: Access to the redolog wasterminated during the previous execution ofthe Data Object Broker. In order for ObjectService Broker to restart after this, theredolog must be formatted.

Action: Follow the relevant recovery procedurein the Object Service Broker Backup andRecovery for z/OS manual.

S6BKR006AREDOLOG AND CACHE FORMATTED.REPLY TO S6BKR098


Explanation: All the recovery data sets have beenformatted. A reply to the subsequentS6BKR098 message is required to continueinitialization.

Action: If this is the first initialization of this DataObject Broker, or if it is a restart after a cleanshutdown followed by data set formatting,reply G to the subsequent S6BKR098message to continue initialization.Otherwise, reply C to the S6BKR098 messageto cancel Data Object Broker initializationand contact your system administrator.

S6BKR007IRESTART CANCELLED BY OPERATOR


Explanation: The operator replied C to aS6BKR098 message. System initialization isterminated.


S6BKR008ACACHE DATA MISSING. REPLY TOS6BKR098


Explanation: One of the two cache data sets is ina formatted state. This is expected only if theother cache data set contains data forcheckpoint number one. A subsequentS6BKR098 message is issued to determine ifinitialization should be allowed to continue.

Action: Contact the person responsible for thissystem. If it is determined that the formattedcache data set is NOT required for thisinitialization, reply G to the subsequentS6BKR098 message. Otherwise reply C.

S6BKR009ECHECKPOINT OUTSTANDING AND NOCACHE DATA AVAILABLE


Explanation: Both cache data sets are in aformatted state, yet there is an outstandingcheckpoint to be recovered. The only validcheckpoint number for which this can occuris one, but this is not the case.

Action: The system will terminate thisinitialization. Report this message to theperson responsible for the system.


| 293

S6BKR010ECHECKPOINT COMPLETE YET NO CACHEDATA AVAILABLE


Explanation: A checkpoint has completed yet thecache data for this checkpoint is notcomplete.

Action: The system initialization is terminated.Contact the person responsible for thissystem.

S6BKR011AREDOLOG FORMATTED YET CACHE DATAAVAILABLE. REPLY TO S6BKR098


Explanation: The redolog is in a formatted state,yet the cache data sets are not empty. Asubsequent S6BKR098 message is issued.

Action: Contact the person responsible for thesystem. If it is determined that recovery maycontinue, reply G to the S6BKR098 message.Otherwise, reply C to cancel systeminitialization.

S6BKR012IRECOVERY NOT REQUIRED


Explanation: The system has determined that norecovery is required for this initialization,even though the previous execution of thisData Object Broker did not shut downcleanly.


S6BKR013IINVALID RDF IN REDOLOG


Explanation: The Recovery task was unable todecipher the redolog data. Recoverytransactions may be lost.


S6BKR014ADOBRESTART PROCESSING FAILED DUETO REDO TRANSACTION FAILURE


Explanation: During the application of changesto a Data Object Broker during restartfollowing an abnormal termination, atransaction failed. To ensure integrity, theData Object Broker terminates with an error.


S6BKR015EREDOLOG SMALLER THAN REQUIREDFOR RESTART


Explanation: During a system restart, the startingoffset in the REDOLOG data set is greaterthan the maximum offset allowed. Asubsequent message S6BKX002I indicates thename of the REDOLOG data set being used.

Action: Contact the person responsible for thesystem. A possible cause is that theREDOLOG has been reallocated while thesystem was not active and the newREDOLOG is smaller than the originalREDOLOG.


294 |

S6BKR016ERECOVERY USER EXIT FAILUREDETECTED, STARTUP ABNORMALLYTERMINATED


Explanation: The Recovery user exit returned anonzero return code in GPR 15. The DataObject Broker is terminated with a U502abend.


S6BKR098AREAD message_ AND REPLY G TO GO, C TOCANCEL


Explanation: The system issues this message tofind out if you want it to continueinitialization.

Action: Read the previous message, then replyeither G to continue initialization or C tocancel it.

S6BKR099IEND OF DATABASE RECOVERY


Explanation: The Recovery Task is indicatingthat recovery is complete.



| 295

KS: DOB Supervisor Tasks

S6BKS001EEVENT (xxxx) REJECTED IN taskname, DOBTERMINATING termtype

Source: DOB Supervisor Tasks

Explanation: The module identified by"taskname" received an event to process"xxxx" and the Data Object Broker started thetermination process. The "termtype" valuecan be either "NORMALLY" indicating aSHUTDOWN request was issued or"ABNORMALLY" indicating a task abended.The requested event processing is ignored.

Action: Wait for the termination to complete andthen recycle the Data Object Broker.

S6BKS002EDUMP GENERATION SUPPRESSED, TWOOCCURRENCES ALREADY REPORTED


Explanation: A transaction error has occurredmore than 2 times, on the third andsubsequent time no dump will be build todiagnose the problem.


S6BKS004WDATA OBJECT BROKER DUMP COMPLETE


Explanation: The Data Object Broker requesteddump has been completed.


S6BKS005WDATA OBJECT BROKER DUMP FAILEDRC(__), REASON (__)


Explanation: The Data Object Broker requested adump. The dump which is generated by theSDUMP macro was not successful for thereturn and reason code provided in themessage. Review the SDUMP macrodocument in the IBM Authorized ReferenceManual.

Action: No action

S6BKS006WDATA OBJECT BROKER DUMP PARTIALLYCOMPLETED


Explanation: When the Data Object Broker wasgenerating an SVC dump, the dump was notcompleted. The most probable cause was alack of space in the dump data set.

Action: Consider expanding the allocation forthe dump data set.

S6BKS010IDATA OBJECT BROKER VERSION '________'


Explanation: The Object Service Broker DataObject Broker software version andapplication identifier are displayed whenObject Service Broker starts up.



296 |

S6BKS011ITASK NAME ________ ASID '____'


Explanation: The Object Service Broker DataObject Broker job or task name and theAddress Space Identifier are displayed whenObject Service Broker starts up.


S6BKS012IAPPLID ________ NODENAME'_______________'


Explanation: This message is present to identifythe Object Service Broker Data Object Brokerfor both a VTAM application identifier andpeer Object Service Broker node name usedfor distributed data access.


S6BKS013WSMF 24 OR SMF 27 MAY BE REQUESTED BUTNOT BOTH


Explanation: In the run time parameters for theData Object Broker, you specified a nonzerovalue for the SMF27INTERVAL Data ObjectBroker parameter (default 0) and theSMF24INTERVAL parameter was nonzero (itdefaults to 30). Data Object Brokerprocessing does not allow the creation ofboth the default response time SMF record(SMF24) and the extended response timeSMF record (SMF27). If you require theextended response time record, theSMF24INTERVAL parameter must explicitly

be set to zero. If you want to use the defaultresponse time record, either omit theSMF27INTERVAL parameter or explicitly setit to zero.

Action: Correct the Data Object Broker run timeparameters and retry.

S6BKS014IMAXIMUM CONNECTIONS OBSERVEDFOR THIS DOB INSTANCE WAS number


Explanation: This message appears at the time ofData Object Broker shutdown and thenumber in the message is the highest numberof end users connected simultaneously tothis instance of the Data Object Broker.

Action: This message is for information only.

S6BKS030ISYSTEM ___SWAPPABLE


Explanation: The Object Service Broker DataObject Broker is executing from anAuthorized library. The following featuresare available to assist performance andtuning when you execute. Object ServiceBroker from an Authorized library:

• Object Service Broker non-swappable

• Cross Memory Services for Object ServiceBroker inter-region communication

• Internal Object Service Broker SMFrecords (optional)

• Journal offload (spin) by Started SystemTask (optional)



| 297

S6BKS031WNO SMF - LOAD LIBRARY NOTAUTHORIZED


Explanation: SMFRECORD=### was specified asa Data Object Broker initialization parameterwith a valid value between 128 and 255. Nointernal SMF recording is possible becausethe Data Object Broker is executing from adata set or concatenation that is notAuthorized.

Action: If Object Service Broker internal SMFrecords are required, the Object ServiceBroker Data Object Broker load library mustbe Authorized. Contact the SystemProgrammer responsible for Object ServiceBroker installation.

S6BKS032EGETMAIN FAILURE ON ____ POOL, ____SPACE _____ THE LINE ON A ____BOUNDARY, RC=


Explanation: Object Service Broker manages itsown storage in blocks referred to as pools.When attempting to acquire storage tosupport, the specified pool the storage wasnot available.

Action: Determine why the storage requirementswere not satisfied. Check the memory controlparameters on the run and increase asneeded. Contact TIBCO Support if furthersupport is required.

S6BKS033EDATA OBJECT BROKER INITIALIZATIONFAILURE - APF AUTHORIZATIONREQUIRED


Explanation: During Data Object Brokerinitialization, it was determined that the DataObject Broker was not executed in an APFAuthorized state as required. The DataObject Broker will abend with user code 33.

Action: Refer to the Object Service BrokerDocumentation for instructions on how toAPF Authorize your Data Object Broker.

S6BKS034ECOMMPOOL SPACE COULD NOT BEACQUIRED ABOVE THE 16M LINE


Explanation: When acquiring storage to buildthe pool used to retain connectioninformation (COMMPOOL) the storage wasnot available above the line. TheCOMMPOOL must reside above the 16 MBline in order to support some processingissues.

Action: Increase the step or job region size andrerun the startup.


298 |

S6BKS038EGETMAIN FAILED DURINGINITIALIZATION


Explanation: During Data Object Brokerinitialization, a failure was encountered inobtaining Virtual Storage. The job will abendwith user code 38.

Action: Increase the amount of Virtual Storageavailable to the Data Object Broker. Refer tothe Planning, Installation, andCustomization Manual for furtherinstructions, if needed.

S6BKS039EGLOBAL ____ POOL BUILD FAILED


Explanation: Insufficient storage was available tobuild Object Service Broker resources for thespecified configuration.

Action: Refer to the Installation and OperationsManual. Validate that the concurrencyoptions are compatible with the region sizespecified at Object Service Broker startup.

S6BKS040ESUBTASK INITIALIZATION FAILED


Explanation: An error occurred during theinitialization of the indicated subtask. ObjectService Broker terminates abnormally.

Action: See the previous messages on the consoleand refer to the Installation and OperationsManual.

S6BKS045ESUBTASK ATTACH FAILED


Explanation: The module for the indicatedsubtask cannot be accessed. Object ServiceBroker terminates abnormally.

Action: See the previous messages on the consoleand refer to the Installation and OperationsManual.

S6BKS047ESDWA NOT AVAILABLE FOR ESTAEPROCESSING


Explanation: During Abnormal Termination ofthe Data Object Broker, the ESTAE routinewas not provided with an SDWA from RTM.Due to this, the ESTAE routine was unable toreport on the cause of the ABEND.


S6BKS048EESTAE PROCESSING TERMINATED -ENVIRONMENT ERROR


Explanation: During Abnormal Termination ofthe Data Object Broker, the ESTAE routinewas unable to locate certain control blocksneeded for cleanup processing. Due to thiscircumstance, certain fixed storage pools willnot be release back to the system.

Action: Certain portions of REAL storage willremain unavailable to the system until an IPLis performed. If the amount of storageoccupied by these orphaned control blocks


| 299

causes system performance problems, animmediate IPL may be required. ContactSystem Programming and/or Operationsstaff for further assistance.

S6BKS049EINITIALIZATION ABORTED


Explanation: Object Service Broker isterminating abnormally after encountering asevere error or errors during initialization.

Action: Refer to the job log for preceding errormessages that explain why Object ServiceBroker cannot start up.

S6BKS050ISYSTEM READY __ ____ __:


Explanation: The Supervisor task issues thismessage to notify you that the initializationof Object Service Broker is complete.


S6BKS059EUNDEFINED EVENT CODE X'____'


Explanation: The Object Service BrokerSupervisor task received a request codewhich it is not defined to handle. The requestis ignored.


S6BKS060WDAIR ERROR ____/____ FOR WTOMSGSYSOUT


Explanation: A dynamic allocation erroroccurred during initial or subsequentallocation of a SYSOUT file to receive copiesof all WTO messages issued by the DataObject Broker. For an explanation of thecodes, refer to the appropriate IBM manualthat describes dynamic allocation (SVC99)and its functionality.

Action: Review the WTO____ initializationparameters that define the attributes of theWTO Sysout file. If unable to resolve, contactTIBCO Support.

S6BKS062WOPEN FAILED FOR WTOMSG SYSOUT


Explanation: A SYSOUT file allocated to receivecopies of all WTO messages issued by theData Object Broker could not be opened.

Action: If unable to resolve, contact TIBCOSupport.

S6BKS070ISNAP DUMP COMPLETED TO '________ ...'


Explanation: This message is issued upon thesuccessful completion of a snap dump. Thevariable portion of the message indicates thefinal destination of the dump.



300 |

S6BKS077EUNRECOVERABLE FAILURE DETECTED INSRB PROGRAM


Explanation: The Object Service Broker SRBprogram responsible for Pagestore I/Ofunctions has abnormally terminated. TheData Object Broker is terminated as thisfailure may cause a loss of data integrity.User abend code 77.


S6BKS088ESUBTASK ABEND - S___/U


Explanation: A severe error occurred during theindicated subtask. The Object Service BrokerData Object Broker terminates abnormally.S___ is the system abend code and U___ isthe Object Service Broker abend code.

Action: If an Object Service Broker return code isprovided, look at previous console messagesfor more information. If only a system returncode is provided and you cannot resolve theproblem based on this code, contact TIBCOSupport.

S6BKS089AABEND S___/U____ REAS=_______DETECTED IN MODULE


Explanation: The Data Object Broker hasabended as described in the message. If aSYSxDUMP data set was allocated to theData Object Broker, it will contain the dumpfor the error.

Action: Collect as much information about thefailure as possible and contact TIBCOSupport.

S6BKS090ISUBTASK DETACH


Explanation: The indicated subtask has shutdown successfully.


S6BKS099ISHUTDOWN COMPLETED


Explanation: Object Service Broker execution hasended successfully.


S6BKS101EINITPARM FILE BYPASSED - OPENUNSUCCESSFUL


Explanation: An INITPARM DD statement wasprovided but failed to open properly. DataObject Broker initialization continues.Parameter values are default values unless aPARM= string containing override values is

provided.

Action: If Object Service Broker started withincorrect parameter values, shut it down.Investigate the INITPARM file problem.When the problem is resolved, restart ObjectService Broker.


| 301

S6BKS102EINITPARM FILE BYPASSED - INVALIDRECFM OR LRECL


Explanation: An INITPARM DD statement wasprovided, but its record format was not fixedblock, or its record length was not 80. DataObject Broker initialization continues.Parameter values are default values unless aPARM= string containing override values isprovided.

Action: If Object Service Broker started withincorrect parameter values, shut it down. Doone of the following:

• Allocate an INITPARM file withRECFM=FB and LRECL=80, and supplythe correct parameter assignments.

• If Object Service Broker runs as a batch job,you can use //INITPARM DD * to defineparameters in- stream.

• If the parameter specifications are 100characters or less, you can omit//INITPARM and just use the PARM=string.

When ready, restart Object Service Broker.

S6BKS105WMAXIMUM CICS DISPLAY LIMIT RESET TOMAXUSERS


Explanation: The MAXDISPLAY parameterspecified a value that was greater than thesetting of MAXUSERS. It is not possible tohave more users on than MAXUSERS,therefore the Display CICS limit is reduced tothe MAXUSERS level.

Action: No action is required. Adjust theMAXDISPLAY parameter to avoid themessage from occurring again.

S6BKS121E_____________ PARM CONTAINS INVALIDCHARACTER(S)


Explanation: The indicated parameter containscharacters which are not alphabetic. Theparameter is rejected. Object Service Brokerstartup terminates abnormally.

Action: Verify and correct the spelling of theparameter. Refer to the Installation andOperations manual if necessary.

S6BKS122E_____________ PARM IS AMBIGUOUS


Explanation: The indicated parameter wasabbreviated so that it is no longer unique.The parameter is rejected. Object ServiceBroker startup terminates abnormally.

You can spell Data Object Broker parametersin full or abbreviate them throughtruncation. For example, SNAPOVERRIDEor SNAPOVER or SNAPO are all accepted.Excessive truncation, however, results inabbreviations that can be one of severalparameters. For example, SNAP might beany one of SNAPCLASS, SNAPREMOTE,SNAPQUERY, SNAPOVERRIDE, orSNAPVOLSER.

Action: Spell the parameter keyword name morefully or completely. In general, fivecharacters are sufficient to achieveuniqueness. Refer to the Installation andOperations manual if necessary.


302 |

S6BKS123E_____________ PARM IS NOT DEFINED


Explanation: The indicated parameter (only thefirst 13 characters appear in the message) isnot defined to Object Service Broker. Youmay have used an unrecognizableabbreviation. The parameter is rejected.Object Service Broker startup terminatesabnormally.

Action: Verify the spelling of the parameter.Refer to the Installation and Operationsmanual if necessary. Abbreviation throughtruncation is permitted, but it isrecommended that at least the first fiveletters be supplied to ensure uniqueness.

S6BKS124I____________ PARM DISCONTINUED - NOFUNCTION


Explanation: The indicated parameter used to befunctional in a previous Object ServiceBroker release but has been superseded. Theparameter is ignored. Object Service Brokerinitialization continues.

Action: Update the file referenced by theINITPARM DDNAME in your Object ServiceBroker Data Object Broker JCL, or by thePARM= string in the Object Service BrokerEXEC statement to discard obsoleteparameters.

S6BKS126E_____________ PARM NOT DYNAMICALLYMODIFIABLE


Explanation: An operator console command wasissued, of the form:

MODIFY jobname,PARM=keyname=value

The keyname specified was a recognizedObject Service Broker Data Object Brokerparameter, but it is not eligible formodification after startup or once set. Theparameter change is rejected. Object ServiceBroker execution continues.

Action: If the parameter must be changed thenthis change must be made to the ObjectService Broker Data Object Brokerinitialization parameters and will take effectthe next time Object Service Broker isrestarted.

S6BKS127E_____________ COMPULSORY PARMOMITTED


Explanation: The parameter name listed iscompulsory and the Object Service BrokerData Object Broker cannot be initializedsuccessfully without it. Object Service BrokerData Object Broker startup terminatesabnormally.

Action: Provide an acceptable parameter value in//INITPARM or PARM= string. Refer to theInstallation and Operations manual ifnecessary.

S6BKS130E_____________ MUST BE ASSIGNED A VALUE


Explanation: The indicated parameter does nothave an associated assigned value. All DataObject Broker parameters are of the form:keyword=value. Spaces are not permitted


| 303

between the keyword, equal sign, or value.The parameter is rejected. Object ServiceBroker Data Object Broker startup terminatesabnormally.


S6BKS131E_____________ SPECIFIED VALUE HAS TOOMANY CHARACTERS


Explanation: The value assigned to the keywordhas too many characters. The parameter isrejected. Object Service Broker startupterminates abnormally.


S6BKS132E_____________ SPECIFIED VALUECONTAINS INVALID CHAR(S)


Explanation: The value assigned to theparameter has failed its edit validity check.This occurs for any non-alphanumeric value,or for a discrepancy between editspecifications and the input provided. Theparameter is rejected. Object Service Brokerstartup terminates abnormally.


S6BKS133E_____________ SPECIFIED VALUE NOTVALID QUALIFIER(S)


Explanation: The value assigned to theparameter has failed its validity check. Adata set name or qualifier, member name, orother entity with similar syntax wasexpected. The parameter is rejected. ObjectService Broker startup terminatesabnormally.

Action: Provide an acceptable parameter value in//INITPARM or PARM= string. Refer to theInstallation and Operations if necessary.

S6BKS134E_____________ SPECIFIED VALUE OUT OFRANGE


Explanation: The value assigned to theparameter is too big or too small. Theparameter is rejected. Object Service Brokerstartup terminates abnormally.


S6BKS135WINTERVAL OF '9999' NO LONGERSUPPORTED - USE '0' TO DISABLE ___


Explanation: The special value of 9999 for theindicated interval parameter is no longersupported. This value was used in previousreleases to disable the indicated parameter.


304 |

Effective with this release, a value of 0 is usedto disable an interval value. This message isonly a warning. The indicated parameter isstill disabled.

Action: Modify the Data Object Brokerinitialization parameter indicated in themessage, replacing the value of 9999 with 0.

S6BKS140IREFER TO DATA OBJECT BROKER PARMSIN INSTALLATION MANUAL


Explanation: An error was detected in yourObject Service Broker initializationparameters.

Action: Refer to the Job message log forpreceding specific parameter error(s). Referto the Object Service Broker Documentationfor parameter syntax, spelling, ranges,defaults.

S6BKS141IRESIDENT CTABLE VALUE INCREASEDBASED ON MAXTHREADS


Explanation: During the initialization of the DataObject Broker, it was determined that thenumber of resident CTABLEs was too low forthe maxthread limit set. In an attempt to keepphysical CTABLE builds to a minimum, theCTABRESIDENT parameter value has beenoverridden. The value is increased to themaxthread limit or the maximum allowableresident CTABLEs, whichever is lower.

Action: Adjust the CTABRESIDENT parameterto avoid the message in the future.

S6BKS142EPAGESWEEP ACTION MUST BE"LOG/NOLOG", "SMF/NOSMF" OR"DUMP/NODUMP", CORRECT AND RETRY


Explanation: The PAGESWEEPACTIONparameter is invalid.

Action: Correct the parameter and restart theData Object Broker.

S6BKS143EPAGESWEEPACTION WAS NOT SPECIFIEDWHEN EXPECTED BASED ONPAGESWEEPLIMIT


Explanation: The PAGESWEEPLIMIT andPAGESWEEPACTION are relatedparameters. Either both must exist or neithershould.

Action: Correct the parameters and restart theData Object Broker.

S6BKS144EPAGESWEEPACTION SPECIFIED SMFREPORTING BUT THE SMFRECORDPARAMETER OMITTED OR 0


Explanation: The PAGESWEEPACTIONspecifies that an SMF record should be cutand the PAGESWEEPLIMIT threshold isexceeded.

Action: Either select a newPAGESWEEPACTION or specify a validSMFRECORD number.


| 305

S6BKS145EXCF MEMBER NAME AND GROUP NAMEBOTH SET TO


Explanation: The XCF member name and groupname must be different

Action: Correct the Data Object Brokerparameters

S6BKS200WTRANSACTION ABORTED


Explanation: An Object Service Brokertransaction has aborted. Depending on thetype of database access (QUERY/COMMIT)and the settings of the control flags(SNAPQUERY/SNAPOFF) a snap dumpmay be produced for diagnosis. ObjectService Broker standard recovery is taken.

Action: Look for and investigate associatedwrite-to-operator messages and any snapdumps. Corrective action is indicated ifmessages are frequent or related to importanttables, or if application problems result.

S6BKS201LT TRX=________ USER=________ SEG=____PAGE=________ TBL=___________


Explanation: This message accompanies atransaction abend in order to help identifythe problem. Included in the message is the:transaction type, transaction number, userid,requested segment id, requested pagenumber , calling program and table name.


S6BKS210WDAIR ERROR ____/____ FOR SNAP SYSOUT


Explanation: A dynamic allocation erroroccurred for an Object Service Broker snapdump SYSOUT file. The snap dump cannotbe printed. Object Service Broker executioncontinues. The first code is the error reasoncode, and the second code is the informationcode. For an explanation of the codes, refer tothe appropriate IBM manual that describesdynamic allocation (SVC99) and itsfunctionality.

Action: Look up the codes and take correctiveaction, if possible. Operator MODIFYcommands are available to change theSYSOUT class (SNAPCLASS) or remoteprinter (SNAPREMOTE). Contact the SystemProgrammer responsible for Object ServiceBroker if the problem persists.

S6BKS211WDAIR ERROR ____/____DSN='________.________._______'


Explanation: A dynamic allocation erroroccurred for an Object Service Broker snapdump data set. The snap dump cannot beprinted. Object Service Broker executioncontinues. The first code is the error reasoncode and the second code is the informationcode. For an explanation of the codes, refer tothe appropriate IBM manual that describesdynamic allocation (SVC99) and itsfunctionality.

Action: Look up the codes and take correctiveaction, if possible. Operator MODIFYcommands are available to change the targetvolume (SNAPVOLUME). Contact thesystem programmer responsible for ObjectService Broker if the problem persists.


306 |

S6BKS212WOPEN FAILED FOR SNAP SYSOUT


Explanation: The snap dump cannot be printed.Object Service Broker execution continues.

Action: Use the operator MODIFY command

SNAPOVERRIDE=Yes

to direct snap dumps to a data set andcompare results. Contact TIBCO Support ifthe problem persists.

S6BKS213WOPEN FAILED FOR SNAP DATASET


Explanation: No snap dump is printed. ObjectService Broker execution continues.

Action: Investigate with particular attention tothe allocation and DCB of the data set. Usethe operator MODIFY command:

MODIFY command SNAPOVERRIDE=No

to direct snap dumps to a SYSOUT class andcompare results. Contact TIBCO Support ifthe problem persists.

S6BKS215WSNAPDSN DYNALLOC FAILED, WILL SNAPTO PRINTER



F jobname,SNAPOVERRIDE=Yes

F jobname,SNAPVOLSER=volume

Trial allocation of a snap disk data set failedand SNAPs are routed to SYSOUT. Someroutine causes of this problem include:

• Invalid data set high-level qualifiers

• A nonexistent disk volume

• Insufficient space on the volume

Action: A DAIR ERROR message accompaniesthis message and provides error reasoncodes. Operator MODIFY commands areavailable to change the target volume(SNAPVOLUME).

S6BKS311EUSEREXIT PARAMETER IS INCONSISTENT


Explanation: If the USEREXIT parameter valuewas Y then the user exit initialization modulewas not found during system initialization. Ifthe USEREXIT parameter value was N thenthe user exit initialization module was foundduring system initialization. Systeminitialization is terminated.


S6BKS312IUSER EXITS HAVE BEEN ACTIVATED


Explanation: Any user exits activated byINITIALIZATION user exit routineUSRX0000 will be taken during subsequentData Object Broker processing.



| 307

S6BKS313EINITIALIZATION USER EXIT FAILED, DOBSTART-UP WILL FAIL


Explanation: USRX0000 returned a nonzeroreturn code in GPR 15. The Data ObjectBroker is terminated with a U0049 abend.


S6BKS400IXCF INITIALIZATION COMPLETED


Explanation: The XCF control task has started

Action: None

S6BKS401EXCF INITIALIZATION FAILED


Explanation: The XCF control task has notstarted. Other messages will indicate thereason for this failure. Data Object Brokerinitialization will be terminated

Action: Correct the error and restart the DataObject Broker

S6BKS402EUNDEFINED EVENT CODE X''____'''


Explanation: The Object Service Broker XCFControl task received a request code which itis not defined to handle. The request isignored.


S6BKS403EEVENT (____) REJECTED IN XCFTASK, DOBTERMINATING'


Explanation: XCFTASK received an event toprocess "xxxx" and the Data Object Brokerhad started the termination process. The"termtype" value can be either"NORMALLY" indicating a SHUTDOWNrequest was issued or "ABNORMALLY"indicating a task abended. The requestedevent processing is ignored.

Action: Wait for the termination to complete andthen recycle the Data Object Broker.

S6BKS404IGROUP STATUS FOR XCF GROUP gggggggg


Explanation: Output from a Memberlist DataObject Broker command. gggggggg is theXCF group to which the Data Object Brokerbelongs


S6BKS405IMEMBER JOBNAME SYSTEM SYSTEMSTATE USER STATE


Explanation: Memberlist display heading


S6BKS406I----- ------- ------ ------------ ----------





308 |

S6BKS407Immmmmmmm jjjjjjjj xxxxxxxx ssssssss tuuuuuuu


Explanation: Output from a MemberlistCommand. One line for each member in theXCF group

• mmmmmmmm XCF Member name

• jjjjjjjj Job Name

• xxxxxxxx System Name

• ssssssss System State

• t Member Type

• P Primary Data Object Broker

• S Secondary Data Object Broker

• M Message Switch

• uuuuuu User State


S6BKS408EXCF REQUEST aaaaaaaa FAILED RETURNCODE hhhh REASON CODE jjjj


Explanation: An XCF request failed.

Action: Look up the return and reason code inappropriate IBM z/OS Sysplex ServicesReference manual. If you are unable todetermine the cause of error message contactTIBCO Support.

S6BKS409ESWITCH REQUEST FAILED


Explanation: An operator initiated switch hasfailed.

Action: Other messages will have been issuedindicating the reason for the failure. If youare still unable to determine the cause of theswitch failure contact TIBCO Support. Thesystem will terminate the switch process

S6BKS410ESUITABLE DATA OBJECT BROKER NOTFOUND


Explanation: A switch command was enteredbut a valid target Data Object Broker couldnot be located

Action: Ensure a suitable target Data ObjectBroker is available for the SWITCHcommand

S6BKS411EIXCQUERY ____ RECORDS NOT RETRIEVED


Explanation: As part of an IXCQUERY issued byXCFTASK a number of records were notreturned by XCF.



| 309

S6BKS412EACTIVE PRIMARY DATA OBJECT BROKERLOCATED


Explanation: A SWITCH command was enteredfor a secondary Data Object Broker but therewas already an active primary Data ObjectBroker in the group

Action: Issue the SWITCH command via thePrimary Data Object Broker.

S6BKS413EINVALID STATE FOR SWITCH


Explanation: A SWITCH command was issuedto a Data Object Broker that was not able toaccept it for one of the following reasons:

• For the Primary Data Object Broker it wasnot in a READY1 state.

• For the Secondary Data Object Broker itwas not in either a READY2 orNSWITCH2 state.

Action: Use the XCF display command todetermine the state of the Data Object Brokerand wait until the Data Object Broker entersthe desired state.

S6BKS414ESWITCH REQUEST FAILED TARGET________ IN INVALID STATE


Explanation: The target of a SWITCH was not inthe correct state for the SWITCH commandto continue processing.

Action: The SWITCH is cancelled. Re-issue theSWITCH command to a target Data ObjectBroker to accept a SWITCH.

S6BKS415ISWITCH WAITING FOR FOLLOWINGMEMBERS OF GROUP ________


Explanation: A SWITCH is in progress and somemembers of the XCF group have notcompleted the SWITCH in a timely manner.A list of members delaying the switchcompletion follows this message.

Action: Try to determine the reason the listedXCF group members have not completed theSWITCH and correct them. Otherwisecontact TIBCO Support.

S6BKS416ISWITCH COMMENCED TO TARGET_________


Explanation: A SWITCH has commenced to thetarget Data Object Broker.


S6BKS417ESWITCH DISALLOWED:


Explanation: The secondary Data Object Brokercannot be the target of a switch command forone of the following reasons:

• DATABASE DEFINITION DATASETSNOT IDENTICAL: The DBD dataset is notidentical to that of the current PrimaryData Object Broker.

• PARAMETER DIFFERENCES FOUND:One of the following parameters was notidentical to that of the current PrimaryData Object Broker:

• NODENAME


310 |

• MAXUSERS

• LOCKBUFFERS

Action: See also messages KS420, KS421 andKS422 for details. Either terminate theSecondary Data Object Broker and correctthe error or if a SWITCH is to be allowedignoring the differences then use SWITCHcommand ALLOW option to ignore thedifferences. WARNING only do this if youare sure that the differences will not impactthe system. For example to increase thenumber of users, buffers or to add extradatasets to the DBD. Attempting to reduceany of the parameters may cause the systemto fail.

S6BKS418ESWITCH=ALLOW FAILED:


Explanation: The SWITCH ALLOW commandfailed for the following reason:

1. ALLOW NOT SUPPORTED FORPRIMARY

2. SWITCH ALREADY ALLOWED

3. DATA OBJECT BROKER STATUS NOTNSWITCH:

4. STATUS SET FAILED

Action:

1. No action required

2. No action required

3. Determine current status using theMEMBERLIST command. If still unable todetermine the cause contact TIBCOsupport.

4. Contact TIBCO Support

S6BKS419ISWITCH=ALLOW SUCCESSFUL


Explanation: A SWITCH command hascompleted


S6BKS420IMEMBER NODENAME DBDJOB DATE TIMEMAXUSERS LOCKBUFFERS


Explanation: Heading for KS421


S6BKS421I-------- -------- -------- -------- --------- -------- -----------


Explanation: Heading for KS422


S6BKS422Immmmmmmm nnnnnnnn jjjjjjjj ddddd ttttttxxxx llll


Explanation: Informational message followingerror message KS417

• mmmmmmmm XCF DOB group membername

• nnnnnnnn DOB Node name

• jjjjjjjj Job name that generated the DBD

• ddddd Date the DBD was generated

• tttttt Time the DBD was generated

• xxxx MAXUSER parameter


| 311

• llll LOCKBUFFERS parameter



312 |

KX: DOB Checkpoint Tasks

S6BKX001EVSAM HEX REQ=__ RC=__ FB=__R15=________

Source: DOB Checkpoint Tasks

Explanation: A VSAM error occurred duringcheckpoint processing. Standard z/OSsystem messages of the form IECxxxaccompany the Object Service Brokermessage.

Action: Contact the Object Service Broker SystemAdministrator. VSAM return codes aredocumented in the IBM z/OS DFP VSAMMacro Instructions.

S6BKX002IDSN=' ________.________.________.______...'


Explanation: This message is issued to indicatethe name of a data set on which an action isbeing performed, or for which an error hasoccurred.

Action: Refer to the associated messages todetermine whether further action should betaken.

S6BKX004AJOURNAL PROPAGATION ERROR


Explanation: Object Service Broker internal logicerror. The number of pages written to theJournal do not match the number of pageswritten to the Pagestore. The message will befollowed by a user 105 abend.

Action: Contact TIBCO Support with thefollowing information:

• A printout of the Data Object Brokerinitialization parameters

• A list of any maintenance (including fieldmodifications) made to the Data ObjectBroker beyond that included in PUT07

• The dump at the time the Data ObjectBroker fails

• The output from S6BTLDBR runimmediately after the Data Object Brokerfails

• The output from S6BTLPCA runimmediately after the Data Object Brokerfails

• A copy of the failing journal data set

Restart the Data Object Broker; restartrecovery will correct the problem.


| 313

S6BKX005ANO ALTERNATE JOURNAL AVAILABLE -SYSTEM QUIESCED FOR COMMITS


Explanation: The system is preparing to spin thejournal and no alternate journal is availablebecause the alternate journal was taken off-line. The Data Object Broker does not acceptany more commits until such time as ajournal becomes available.

Action: Determine why the alternate journal wastaken offline and make one available. Note:As soon as the current spin completes, thequiesce will be reset.

S6BKX006AALL JOURNALS FULL - SYSTEM QUIESCEDFOR COMMITS


Explanation: All Journal space has been usedand COMMIT processing is suspended -Object Service Broker is quiesced.

Action: Display the current situation with thecommand:


Check for a Journal offload (spin) jobawaiting execution, requiring a tape mount,or failed, and resolve the situationimmediately. As soon as the spin jobcompletes successfully, QUIESCE status isautomatically removed.

Manual intervention by using the command:


cancels the QUIESCE state, but leaves yourcontinuous backups in an indeterminatestate.

S6BKX007AACTIVE JOURNAL __% FULL - SPINREQUIRED FOR JOURNAL _


Explanation: The currently active Journal isnearing the end of its extent, and thealternate Journal is still offline. When thisJournal reaches 100% capacity, messageS6BKX006A will be issued and the DataObject Broker will stop accepting COMMITrequests.

Action: Display the current situation with thecommand:


Check for a Journal offload (spin) jobawaiting execution, requiring a tape mount,or failed, and resolve the situationimmediately. As soon as the spin jobcompletes successfully, this condition will berelieved.

S6BKX008AJOURNAL ___ SPIN IN PROCESS


Explanation: A Journal backup is being taken.The Journal is now offline to Object ServiceBroker. A system task or job is submittedautomatically to offload this filled Journal.When the offload is complete the S6BSPJEXutility will notify the Data Object Broker tobring the Journal back online.

Action: No action is usually required, unlessother messages indicate a problem.


314 |

S6BKX009AJRNL ___ SPIN:JOB=________ PG=__________STATUS=__-__ DUR=__:__ CHT= _______-________


Explanation: A Journal backup is signalledfinished. The Journal is ready for ObjectService Broker use. It becomes active when itis the next available journal after a spin isinitiated.


S6BKX010EUNDEFINED EVENT CODE X'____'


Explanation: The Checkpoint task detected thecompletion of an unknown event.


S6BKX011AJOURNAL SPINS DEFERRED - SPINREQUIRED FOR JOURNAL _


Explanation: The currently active Journal hasexhausted its available space and needs to bespun; however, the operator has requested(via the SPINENABLE command) thatJournal spins are to be delayed until a moreappropriate time. The filled journal is takenoffline.

Action: When spins are to once again beprocessed, the SPINENABLE commandmust be issued to inform the Data ObjectBroker of the change in status:

MODIFY jobname,SPINENABLE=Y

When this command is issued, the spin jobfor the offline Journal will be submitted orstarted as appropriate.

S6BKX012INO PAGE UPDATES FOUND


Explanation: No page updates were found forthe current checkpoint. This may occurduring Object Service Broker shutdown if noactivity occurred since the previouscheckpoint.


S6BKX013IRPE CHAIN IN ERROR


Explanation: Object Service Broker internal logicerror. The resident page entry chain isincorrect. The system shuts down.


S6BKX014IUNABLE TO SCHEDULE LAST CHPT


Explanation: Object Service Broker cannot issuea final checkpoint because a checkpoint isstill in progress. No action is taken.

Action: Retry the shutdown command.

S6BKX015WSHUTDOWN INITIATED


Explanation: Object Service Broker is shuttingdown as requested.



| 315

S6BKX016WEXCP FAILURE X'__'


Explanation: An I/O error occurred during thewriting of a checkpoint.


1. Contact the Object Service Broker SystemAdministrator in case there is a hardwareproblem.


S6BKX017EINVALID DEVICE CLASS FOR CACHE


Explanation: This message occurs duringinitialization if the cache is not cataloged onan appropriate device.

Action: Change the device for the cache to adirect access device.

S6BKX018EJOURNAL NOT PREFORMATTED


Explanation: Either no Journals are available, orthe Journal size is less than 10 cylinders. AJournal size of at least 50 cylinders isrecommended. A Journal size of less than 10cylinders is not permitted. Object ServiceBroker does not startup.


1. Check if an associated messageS6BDA013E was issued. If it was, takeappropriate action to make Journalsavailable.

2. If S6BDA013E was not issued, increase theJournal size. A Journal offload (spin) maybe required.

S6BKX019EINSUFFICIENT STORAGE FOR CACHEBUFFER


Explanation: The system failed to get storage fora cache buffer. The system shuts down.

Action: Contact the Object Service Broker systemadministrator to increase the region sizethrough the Object Service Broker JCL.

S6BKX020ECACHE DATASET NOT FOUND


Explanation: The cache data set identified toObject Service Broker is not found.


S6BKX021ECACHE READ ERROR


Explanation: The system tried to read the cacheand failed. This is probably an I/O error.

Action: Contact the Object Service Broker systemadministrator about a possibly bad device.

S6BKX022ECHPT RECOVERY ERROR


Explanation: During initialization or recovery,the system tried to recover a page that is notlogically within the defined extents ofPagestores.

Action: Contact the Object Service Broker systemadministrator to check the DBGEN. Also,verify that the page should be recovered.


316 |

S6BKX023ICHPT RECOVERY IN PROGRESS


Explanation: The Checkpoint task is recovering acheckpoint.


S6BKX024IVSAM I/O ERROR ON CHPT RECOVERY


Explanation: During recovery, a VSAM I/O erroroccurred.

Action: Contact the Object Service Broker SystemAdministrator to investigate a possiblehardware error.

S6BKX025I_____ PAGES RECOVERED


Explanation: The message indicates the numberof pages that are recovered.


S6BKX026EUNABLE TO OPEN SPIN JCL MEMBERS -MEMBER NAME PREFIX TOO LONG


Explanation: During initialization, the DataObject Broker was not able to load the SPINjob JCL due to the value specified for theSPINMEMBER initialization parameter. This

value cannot exceed (8 - the number of digitsin the highest numbered journal data set ID)characters in length. Data Object Brokerinitialization is terminated.

Action: Correct the value specified for theSPINMEMBER initialization parameter andrestart the Data Object Broker.

S6BKX027ESPIN JCL DAIR ERROR ____/____MEMBER='________'


Explanation: During Object Service Brokerinitialization, SPIN JCL is loaded for latersubmission. A dynamic allocation erroroccurred for the indicated SPINDSNAMEmember. The first code is the error code, andthe second code is the information code.Object Service Broker initializationcontinues. Unless the problem is resolvedand Object Service Broker is shut down andrestarted, automatic Journal spin jobsubmission does not function. Anexplanation of the codes is in the IBMApplication Development Guide for z/OSsystem programming.


1. Verify that the indicated member is in theSPINDSNAME data set.

2. Refer to the appropriate z/OS manual foran explanation of the error andinformation codes.

3. If the problem cannot be resolved, contactTIBCO Support.

4. When the situation is resolved, do one ofthe following: shut down and restartObject Service Broker to restore automaticspin job submission, or be prepared tosubmit spin jobs manually.


| 317

S6BKX028ESPIN JCL ________ DCB FAILED TO OPEN


Explanation: During Object Service Brokerinitialization, SPIN JCL is loaded for latersubmission. The OPEN for the indicated spindata set member has failed. Object ServiceBroker initialization continues. Unless theproblem is resolved and Object ServiceBroker is shut down and restarted, automaticJournal spin job submission does notfunction.

Action: Investigate possible SPINDSNAMEspecification error or deleted data set. Whenthe situation is resolved, do one of thefollowing: shut down and restart ObjectService Broker to restore automatic Journalspin job submission, or be prepared tomanually submit spin jobs.

S6BKX029ESPIN JCL ________ STORAGE BUFFERGETMAIN FAILED


Explanation: During Object Service Brokerinitialization, SPIN JCL is loaded for latersubmission. The request for storage in whichto load the SPIN JCL has failed. The requiredamount of virtual storage may not beavailable. Object Service Broker initializationcontinues. Unless the problem is resolvedand Object Service Broker is shut down andrestarted, automatic Journal spin job

submission does not function. It is unlikelythat an Object Service Broker system thatcannot obtain enough virtual storage to loadits SPIN JCL can function successfully.

Action: Increase the Object Service Broker DataObject Broker memory specification(REGION=). Shut down and restart ObjectService Broker to restore automatic Journalspin job submission, or be prepared tosubmit spin jobs manually.

S6BKX030ESPIN JCL ________ LINECOUNT EXCEEDSSTORAGE CAPACITY


Explanation: During Object Service Brokerinitialization, SPIN JCL is loaded for latersubmission. Sufficient storage for 300+ JCLcards per spin job is obtained, not includingcomment cards which are discarded toconserve space. The number of cardssupplied for the indicated member exceedsthis capacity. Object Service Brokerinitialization continues. Unless the problemis resolved and Object Service Broker is shutdown and restarted, a partial JCL deck issubmitted whenever the Journal fills.

Action: 300 cards are sufficient for any normalspin process. It is recommended that the JCLloaded consist of job cards and EXECprocedure cards only, with the necessaryprocedure stored in a PROCLIB. This greatlyreduces the card count, and if JCL errorsoccur, most can be corrected withoutreloading the SPIN JCL decks.

S6BKX031ESPIN JCL ________ IS EMPTY, INVALID, ORMISSING


Explanation: During Object Service Brokerinitialization, SPIN JCL is loaded for latersubmission. The indicated member is empty,invalid, or missing. Object Service Broker


318 |

initialization continues. Unless the problemis resolved and Object Service Broker is shutdown and restarted, automatic Journal spinjob submission does not function.

Action: Provide suitable JCL. When the situationis resolved, do one of the following: shutdown and restart Object Service Broker torestore automatic Journal spin jobsubmission, or be prepared to submit spinjobs manually.

S6BKX032ASPIN ___ DAIR ERROR ____/____ INTERNALREADER


Explanation: A dynamic allocation erroroccurred while attempting to allocate aninternal reader during automatic spin jobsubmission. The first code is the error code,and the second code is the information code.For an explanation of the codes, refer to theappropriate IBM manual that describesdynamic allocation (SVC99) and itsfunctionality.

Action: Manually submit the required Journalspin job. Contact the System Programmer.

S6BKX033ASPIN ___ INTERNAL READER DCB OPENFAILED


Explanation: The system tried to open the readerand failed. This is probably a JES problem.

Action: Manually submit the required Journalspin job. Contact the System Programmer.

S6BKX034ASPIN ___ JCL NOT AVAILABLE TO SUBMIT


Explanation: A Journal data set exceeded itsprimary extent and is now using secondaryextents. An attempt was made toautomatically submit a Journal spin job tooffload the filled Journal. Presumably due toan error at initialization time, no suitableSPIN JCL was found to submit.


1. Manually submit the required Journal spinjob

2. Investigate and resolve any initializationerrors, see the message log.

3. When the situation is resolved, do one ofthe following:

• Manually shut down and restartObject Service Broker to restoreautomatic Journal spin job submission

• Be prepared to submit spin jobsmanually

If there were no initialization errors, contactTIBCO Support.

S6BKX040EREQUIRED JOURNAL DATASET FAILED TOOPEN


Explanation: The ACTIVE Journal data set failedinitialization during system startup.Accompanying messages will indicate thefailing Journal data set, and the reason for thefailure.

Action: Take corrective action as indicated by theaccompanying messages.


| 319

S6BKX042EINSUFFICIENT SPACE AVAILABLE INJOURNAL DATASET


Explanation: There is not sufficient space definedin the Journal data set being brought onlineto support checkpoint activities.

Action: Consult the Installation and Operationsmanual for information on defining theJournal data sets.

S6BKX043IJOURNAL SPINS ENABLED


Explanation: This message indicates that the spinprocess has completed its processing of theoffline journal, and that the Journal data sethas been successfully brought online to theData Object Broker. The Data Object Broker isnow able to process journal SPIN requests.


S6BKX044EINITIALIZATION OF JOURNAL ___ FAILED


Explanation: The Data Object Broker was unableto bring the indicated Journal data set on line.Refer to the accompanying messages todetermine the cause of the initializationfailure.

Action: Correct the problem indicated by theassociated messages, and then use theJOURNALONLINE operator command tomake the Journal data set available to theData Object Broker.

S6BKX045ASPIN JCL FOR JOURNAL ________RELOADED


Explanation: This message is issued to confirmthat the SPIN JCL for the indicated journaldata set has been successfully reloaded asrequested by the operator.


S6BKX046ESPIN JCL RELOAD FOR JOURNAL ___FAILED


Explanation: The reloading of the SPIN JCL forthe indicated journal has failed. Scan theData Object Broker's job log for indications asto why the process terminated.

Action: If possible correct the source of the failureand retry the command.

S6BKX051LSTART CHECKPOINT - '________'


Explanation: A checkpoint started. Thecheckpoint number, the timestamp stored inthe Pagestore records and journals, andwhether the timestamp is Local or UTC isincluded in the message.



320 |

S6BKX052LEND CHECKPOINT - '________' COUNT='________'


Explanation: The checkpoint was successful. Thecheckpoint number, the timestamp stored inthe Pagestore records and journals, andwhether the timestamp is Local or UTC isincluded in the message. Count is thenumber of pages written by this checkpoint.


S6BKX053ECHECKPOINT USER EXIT FAILUREDETECTED, DOB ABNORMALLYTERMINATED


Explanation: The Checkpoint Start user exitreturned a nonzero return code in GPR 15.The Data Object Broker is terminated with aU107 abend.


S6BKX054WSPIN REQUIRED FOR JOURNAL_


Explanation: During Object Service Brokerinitialization, it was discovered that theindicated Journal was also being processedby a Journal spin job when the systemterminated, and no notification was given to

Object Service Broker that the spin hadcompleted. Object Service Brokerinitialization continues, and the Journal istaken offline.

Action: Determine the status of the last spin jobfor the indicated Journal and take theappropriate action. If the spin job completedsuccessfully, you can use the SPINENABLEoperator command to make the Journalavailable to Object Service Broker.

S6BKX055EJOURNAL NOT ENABLED


Explanation: While trying to enable an offlineJournal, Object Service Broker encountered acondition that made it impossible to bringthe Journal online.

Action: From the accompanying messages,determine the cause of the failure and takethe appropriate action for the error. Once thecause of the failure has been corrected, theJournal can be brought online with theSPINENABLE operator command.

S6BKX056ECHECKPOINT CACHE USER EXIT FAILUREDETECTED, DOB ABNORMALLYTERMINATED


Explanation: The Cache Complete user exitreturned a nonzero return code in GPR 15.The Data Object Broker is terminated with aU107 abend.



| 321

S6BKX057WPAGE LIMIT REDUCED - EXCEEDS 15% OFRESIDENT PAGES


Explanation: The value specified for theCHPAGELIMIT initialization parametermust not exceed 15% of the Resident PageDirectory as defined by theRESIDENTPAGES initialization parameter.The value of CHPAGELIMIT has beenautomatically reduced so as to conform tothis requirement.

Action: Adjust the CHPAGELIMIT parameter orthe RESIDENTPAGES parameter or both sothat this condition is addressed.

S6BKX059W_________ REDUCED - INSUFFICIENT SPACEIN _______ DATA SET


Explanation: The value specified for theinitialization parameter indicated by thismessage is too large to be supported by theindicated data set.

Action: Adjust the indicated initializationparameter to relieve this condition, orincrease the amount of space available to theindicated data set. Consult the Installationand Operations manual for furtherinformation.

If the data set is a cache, it must be bigenough to hold at least a full checkpoint'sworth of data pages.

If the data set is a journal, it must be bigenough to hold at least 3 full checkpoints'worth of data pages.

S6BKX060ICHECKPOINT MAXIMUM PAGES = ____,TRANSACTIONS = ____


Explanation: This message is provided forinformational purposes only and is issued toconfirm the thresholds set for the maximumsize of a Checkpoint.


S6BKX061IGETMAIN FOR JOURNAL I/O BUFFERFAILED


Explanation: Data Object Broker initializationwas unable to obtain the Virtual Storageneeded for the Journal I/O buffer.

Action: Provide more Virtual Storage to the DataObject Broker. Consult the Installation andOperations manual for further information.

S6BKX062ECANNOT SPIN JOURNAL ___ - NOALTERNATE JOURNAL AVAILABLE


Explanation: During Data Object Brokerinitialization, it was determined that theactive journal was full and needed to bespun. The Data Object Broker cannot switchto the alternate journal because this journal isoffline.

Action: Determine why the alternate journal isoffline. Correct the situation and restart theData Object Broker. Alternatively, the fullactive journal could be spun manually whilethe Data Object Broker is down.


322 |

S6BKX063WJOURNAL ___ WAITING FOR SPIN


Explanation: During Data Object Brokerinitialization, an incomplete spin wasdetected for the indicated journal data set.The data set remains offline to the DataObject Broker until the spin is completed.

Action: Determine why the spin has notcompleted. If the SPIN had failed, submit thespin job manually to clear the data set.

S6BKX064IJOURNAL ___ NOW


Explanation: This message is issued to confirmthe completion of a journal vary command.The journal and its new status are displayedin the message text.


S6BKX066ACACHE DATASET OPEN FAILUREDETECTED


Explanation: When attempting to open the cachedata set to identify the previous checkpoint afailure was detected.

Action: Review the joblog for information andcorrect the problem.

S6BKX067ISEGMENT % PAGE %


Explanation: This message indicates which pagenumber and segment number is causing thesubsequent S6BKX022 message.

Action: If this message appears while you arerecovering after a restart with no redolog,modify the DBDGEN to include the segmentas online at initialization.

S6BKX068Wparameter SET BASED ON SPACEAVAILABLE IN THE dataset DATASET


Explanation: The value of the specifiedparameter is set automatically based on thecalculated maximum capacity of thespecified data set.


S6BKX069ISYSTEM IS FROZEN: %


Explanation: As a result of a Freeze command,the system has entered the frozen state.


S6BKX070ISYSTEM IS UNFROZEN: %


Explanation: As a result of an UNFREEZEcommand, the system has resumedprocessing.



| 323

S6BKX071ESPIN NOTIFICATION REPORTED ERROR rc-re JOB jobid


Explanation: The Data Object Broker receivednotification that a spin job had completedwith a fatal error (return code 16 or higher).In the message:

• rc=Return code

• re=Reason code

• jobid=the identification number of the spinjob that reported the fatal error

Action: Review the message in the spin job andtake the appropriate action.


324 |

MN: osMon

S6BMN000EOut of memory

Source: osMon

Explanation: A request by a process for storagefailed because all the virtual memory is inuse.

Action: Either run fewer processes on yoursystem or add memory.

S6BMN001IUnable to open the mon.prm file '%'

Source: osMon

Explanation: The attempt to open the mon.prmparameter file failed.

Action: Check the operating system error code todetermine the reason for this failure. Note:Use of the mon.prm is optional.

S6BMN002IUnable to open the ee.prm file '%'

Source: osMon

Explanation: The attempt to open the ee.prmparameter file failed.

Action: Check the operating system error code todetermine the reason for this failure. Note:Use of the ee.prm is optional.

S6BMN004EAn invalid message type was received from anosee. It is ignored

Source: osMon

Explanation: The osMon process received anunrecognized message type from a child oseeprocess.


S6BMN005EA pipe read failed with error '%'

Source: osMon

Explanation: A read on a named pipe (or FIFO)failed.

Action: Examine operating system suppliederror codes to determine reason for thefailure.

S6BMN006LosMon shutdown due to a CLOSE request

Source: osMon

Explanation: The osMon process shut downbecause it received a CLOSE request fromanother osMon process.



| 325

S6BMN007EWrite on named pipe % failed

Source: osMon

Explanation: A write on a named pipe (or FIFO)failed.

Action: Examine operating system suppliederror codes to determine the reason for thefailure.

S6BMN008ESystem operation failed, '%'

Source: osMon

Explanation: The specified operating systemoperation failed.


S6BMN009EInvalid data received on connection

Source: osMon

Explanation: An error was discovered in the datareceived from an inter-processcommunication connection.


S6BMN010LSession (%) stopped with exit code (%) on EE[%]:%

Source: osMon

Explanation: Object Service Broker sessionstopped with specified exit code.

Action: No action is required. If the exit code ismore than 128, the session abended. Checkexit code documentation in order todetermine what the exit code signifies.

S6BMN011LSession (%) started on EE [%]:%

Source: osMon

Explanation: The Object Service Broker sessionstarted on the specified ExecutionEnvironment.


S6BMN012EInvalid session start notification received fromEE [%]:%

Source: osMon

Explanation: When a session is started by anosMon, it sends the start request to a childosee process. After the child osee processspawns the thread for the session, it shouldnotify the osMon process that the session hasstarted. This message is generated when theosMon process receives a notification on asession that it has no record of initiating.

Action: Recycle your osMon process. If thismessage persists, contact TIBCO Support.

S6BMN013EInvalid session stop notification received fromEE [%]:%

Source: osMon

Explanation: When a session initiated by anosMon process ends, the child osee processsends the parent osMon a notification. Thismessage is generated if the osMon processreceives notification on a session for which ithas no record.

Action: Recycle your osMon process. If thismessage persists, contact TIBCO Support.


326 |

S6BMN014WEENAME [%] was not found in ee.prm.Defaults used

Source: osMon

Explanation: An attempt was made to start asession with the session parameter EENAMEset to a value that is not assigned to anyNAME parameter in the ee.prm file.

Action: If your intention is to use the EENAMEparameter to access a set of ExecutionEnvironment parameter settings in theee.prm file, then add those settings, precededby "NAME = <your EENAME value>".

S6BMN015LosMon shutdown due to a STOP request

Source: osMon

Explanation: An osMon process shut down uponreceipt of a STOP request from anotherosMon process.


S6BMN016LosMon shutdown due to a STOPALL request

Source: osMon

Explanation: An osMon process shut down uponreceipt of a STOPALL request from anotherosMon process.


S6BMN017LTerminating due to signal %

Source: osMon

Explanation: An osMon process terminatedupon receiving the specified signal.


S6BMN018LTerminating on request

Source: osMon

Explanation: An osMon process terminatedbecause it received a request to do so.


S6BMN019ETerminating due to error

Source: osMon

Explanation: An osMon process terminated dueto an error.

Action: If messages that precede this message donot provide sufficient information todetermine the cause of this failure, contactTIBCO Support.

S6BMN020LLogon from %:%, user=%, terminal=%

Source: osMon

Explanation: This message is written to the logwhenever a connection is establishedbetween an ActiveX Adapter client and anosee via an osMon process.



| 327

S6BMN021EInvalid data received on connection from %:%

Source: osMon

Explanation: An invalid request type wasreceived by an osMon process from thespecified client machine on the specified portnumber.


S6BMN022EUnable to connect to osMon at port %, monitormay not be running

Source: osMon

Explanation: An attempt to make a socketconnection to an osMon process listening onthe specified port failed.

Action: Check to see if the osMon process inquestion is running. Otherwise, contact yoursystem administrator. This is likely acommunications problem.

S6BMN023LConnection to port % was rejected

Source: osMon

Explanation: An attempt to establish aconnection by an ActiveX Adapter clientfailed.


S6BMN024LStop request sent to osMon with pid=%

Source: osMon

Explanation: This message is written to anosMon log whenever an osMon processsends a request to another osMon process tostop executing.


S6BMN025EUnable to send request

Source: osMon

Explanation: This message is sent to an osMonlog if the corresponding process failed toexecute a request.


S6BMN026LCLOSE request sent to osMon with pid=%

Source: osMon

Explanation: A CLOSE request was sent to theosMon process whose process Id is specifiedin the message.



328 |

S6BMN027ICould not find DEFAULT_MON_NAMEsystem variable

Source: osMon

Explanation: The osMon process is unable toload the DEFAULT_MON_NAME systemvariable.

Action: Use the osconfig utility to change thevalue of the DEFAULT_MON_NAMEparameter.

S6BMN028LSession startup on PID=% completed

Source: osMon

Explanation: This message is written to anosMon log whenever the correspondingprocess successfully spawns the binary withthe specified process ID.


S6BMN029EPort % is in use, osMon may already be running

Source: osMon

Explanation: An attempt was made to start anosMon process with a MONPORT parameterequal to another osMon process that isrunning on the same machine.

Action: Start the osMon process with a uniqueMONPORT value with respect to the givenmachine.

S6BMN030LosMon at port % has been stopped

Source: osMon

Explanation: This message is written to anosMon log whenever the correspondingosMon process successfully stops anotherosMon process.


S6BMN031EUnable to stop osMon at port %, attempting tokill process

Source: osMon

Explanation: If a request is made of an osMon tostop another osMon process, it first attemptsto contact the other osMon process and bringit down in a graceful manner. If this fails, thismessage is written to the log and an attemptis made to kill the other osMon process.


S6BMN032IThe DEFAULT_MON_NAME system variable(%) must be between 1 and 32 characters long

Source: osMon

Explanation: The DEFAULT_MON_NAMEsystem variable must be at least 1 characterand at most 32 characters long.

Action: Use the osconfig utility to change thevalue of the DEFAULT_MON_NAMEvariable.


| 329

S6BMN033LLog file % was deleted

Source: osMon

Explanation: The specified log file is deleted. Logfiles are automatically deleted when they aresufficiently old. See the documentation fordetails on the osMon DELETELOGparameter.


S6BMN034EMissing NAME parameter at line % in file %.Parameter assignment sets must begin with aNAME assignment

Source: osMon

Explanation: Parameter files consist of one ormore parameter assignment sets. Each setmust begin with a NAME assignment.

Action: Add a NAME assignment to thespecified parameter file on the specified line.

S6BMN035LParameter reload request sent to osMon withpid=%

Source: osMon

Explanation: The osMon with the given processID was sent the request to reload theExecution Environment and sessionparameters.


S6BMN036ESession startup failed

Source: osMon

Explanation: The attempt by osMon to start asession failed.

Action: Check preceding messages in the osMonlog for the failure.

S6BMN037WError occurred in idle shutdown thread

Source: osMon

Explanation: An osMon process allocates athread to keep track of how long each oseehas been idle. This thread experienced anerror.

Action: If the message repeats, assume theosMon is in an undefined state, and shouldbe brought down as soon as possible.

S6BMN038Eosee abended. PID=% EE [%]:% Exit code %

Source: osMon

Explanation: The specified osee process abendedwith the specified exit code.

Action: Check the osee log file to determine thereason for the abend.

S6BMN039EosMon abended due to exception thrown at%:%

Source: osMon

Explanation: The Object Service Broker Monitor

abended due to an internal (unexpected)exception.



330 |

S6BMN040EosMon abended

Source: osMon

Explanation: The Object Service Broker Monitorabended.


S6BMN041ESession (%) abended with exit code (%) on EE[%]:%

Source: osMon

Explanation: The specified session abended withthe specified exit code.

Action: Check the session log and the osee logfiles to determine the reason for the abend.

S6BMN043EValue of STOPEE parameter (%) must be eitherpid or eename:instance

Source: osMon

Explanation: The value of the STOPEEparameter must be either a process ID (i.e., anumber) or an Execution EnvironmentNAME immediately followed by a colon thatis immediately followed by an ExecutionEnvironment INSTANCE number.

Action: Rerun the osMon process with the correctsyntax for the STOPEE parameter.

S6BMN044EValue of STOPSESS parameter (%) must beeither pid:tid or eename:instance:instance

Source: osMon

Explanation: The value of the STOPSESSparameter must be either aprocessId:threadId (i.e., number:number) oran EENAME:Execution Environmentinstance number:Session instance number.

Action: Rerun the osMon process with the correctsyntax for the STOPSESS parameter.

S6BMN045LSTOPSESS request received for session (%)

Source: osMon

Explanation: The osMon process received aSTOPSESS request for the specified session.


S6BMN046LSTOPEE request received for EE (%)

Source: osMon

Explanation: The osMon process received aSTOPEE request for the specified ExecutionEnvironment.


S6BMN047LCLOSEEE request received for EE (%)

Source: osMon

Explanation: The osMon process received aCLOSEEE request for the specified ExecutionEnvironment.



| 331

S6BMN050EFailed to create main thread

Source: osMon

Explanation: An attempt by the service to createthe main thread failed.


S6BMN051EFailed to connect main thread to service controldispatcher

Source: osMon

Explanation: An attempt to connect the mainthread to the service control dispatcherfailed.


S6BMN052EFailed to create or open the semaphore forstopall requests

Source: osMon

Explanation: An attempt to create or open aninterprocess semaphore used for STOPALLrequests failed.


S6BMN053EFailed to open or post the semaphore for stopallrequests

Source: osMon

Explanation: An attempt to open or post aninterprocess semaphore used for STOPALLrequests failed.


S6BMN054EFailed to create or start the thread for stopallrequests

Source: osMon

Explanation: An attempt to create or start thethread that waits for STOPALL requestsfailed.


S6BMN055EFailed to create or start the delete log thread

Source: osMon

Explanation: An attempt to create or start thethread that deletes log files failed.



332 |

S6BMN056EFailed to create or start the thread that waits forosee terminations

Source: osMon

Explanation: An attempt to create or start thethread that waits for the termination of oseeprocesses failed.


S6BMN057EFailed to create or start the thread that listens forosee messages

Source: osMon

Explanation: An attempt to create or start thethread that listens for messages from oseeprocesses failed.


S6BMN058EFailed to create or start the thread that servicesTN3270 clients

Source: osMon

Explanation: An attempt to create or start thethread that services TN3270 clients failed.


S6BMN059EFailed to join with the thread that servicesTN3270 clients

Source: osMon

Explanation: An attempt to join with the threadthat services TN3270 clients, that is, to waitfor the termination of the thread, failed.


S6BMN060EFailed to create or start a thread to service aclient connection

Source: osMon

Explanation: An attempt to create or start athread to process a client connection failed.


S6BMN061EFailed to create or start a thread to shutdownidle osee processes

Source: osMon

Explanation: An attempt to create or start athread to shutdown idle osee processesfailed.



| 333

S6BMN099EThe value specified for the osMon SERVERSparameter is not valid

Source: osMon

Explanation: The osMon SERVERS parametervalue does not conform to the syntax"<number1> <session name1> <number2><session name2> ... <numberN> <sessionnameN>".

Action: Correct the SERVERS parameter value.

S6BMN100LThe % service was installed

Source: osMon

Explanation: The osMon service with the givenname is successfully installed on the host.


S6BMN101LThe % service was removed

Source: osMon

Explanation: The osMon service with the givenname is successfully removed from the host.


S6BMN102EThe % service could not be removed

Source: osMon

Explanation: An attempt to remove an osMonservice failed.

Action: Check the operating system error code.Retry to remove the service. If all else fails,reboot.

S6BMN103EThe control handler could not be installed

Source: osMon

Explanation: The attempt to register the osMonservice with the system failed.

Action: Retry to start the service. If that fails,reboot the system and retry. If that fails,contact TIBCO Support.

S6BMN104EThe initialization process failed

Source: osMon

Explanation: Failed to initialize the osMonservice.

Action: Retry. If that fails, reboot the system andretry. If that fails, contact TIBCO Support.

S6BMN105EFailed to detach from the binding area

Source: osMon

Explanation: An osee process failed to detachfrom the shared memory area provided bythe osMon process that spawned it.

Action: Check to make sure the osMon process isstill running. If messages that precede thismessage do not provide sufficientinformation to determine the cause of thisfailure, contact TIBCO Support.


334 |

S6BMN106WThe service received an unsupported request

Source: osMon

Explanation: The service received (and ignored)an unsupported request type.

Action: No immediate action is required.However, if this message persists, contactTIBCO Support.

S6BMN107LThe service was stopped

Source: osMon

Explanation: The osMon service is successfullystopped.


S6BMN108LThe service was started

Source: osMon

Explanation: The osMon service startedsuccessfully.


S6BMN110WThe server name (%) in the osMon SERVERSparameter is not associated with a set ofparameter assignments

Source: osMon

Explanation: The given gateway/server name isnot associated with a set of parameterassignments in the session.prm file or in theWindows registry.

Action: Change the gateway/server name or addan entry for this name to the session.prm fileor to the Windows registry.

S6BMN111ECould not release existing binding area,because the shared memory segment is in use

Source: osMon

Explanation: An osMon process failed to releasea shared memory binding area because someprocess is attached to it.


S6BMN112EOS would not permit release existing bindingarea

Source: osMon

Explanation: The operating system did notpermit the osMon process to release a sharedmemory binding area.


S6BMN113ECould not remove locks for shared binding area

Source: osMon

Explanation: An osMon process is unable toremove locks held on portions of a sharedmemory binding area.

Action: The messages that precede this messageshould provide sufficient information todetermine the cause of this failure. Check tosee if the osee processes that were spawnedby the osMon processes were brought downsuccessfully.


| 335

S6BMN115ICould not open defaults file %

Source: osMon

Explanation: At startup, osMon attempted toload startup parameters from the specifiedfile.

Action: Check the operating system errornumber provided with the message. Itshould indicate the reason for the failure. Ifyou do not want to load startup parametersfrom the specified file, this message can beignored.

S6BMN117Losee shutdown. PID=% EE [%]:% Exit code %

Source: osMon

Explanation: This message is written to anosMon log every time an osee that wasspawned by the corresponding osMonprocess is shut down.

Action: If the exit code is nonzero, the osee didnot shut down normally. Check thedocumentation of osee exit codes todetermine the cause of the shutdown.

S6BMN120EError occurred when getting exit code

Source: osMon

Explanation: An error occurred when an osMonprocess attempted to get the exit code for oneof the osee processes that it spawned.

Action: If the operating system error code doesnot provide sufficient information todetermine the cause of this failure, contactTIBCO Support.

S6BMN121EError occurred while waiting on child process

Source: osMon

Explanation: An error occurred while an osMonprocess was waiting to see if any of its childprocesses had terminated.

Action: If the operating system error code doesnot provide sufficient information todetermine the cause of this failure, contactTIBCO Support.

S6BMN122ELine % in % is too long. It must be no more than% characters

Source: osMon

Explanation: The specified line in the specifiedconfiguration file is too long.

Action: Edit the specified file, shortening thespecified line to be no longer than thespecified maximum length.

S6BMN123EUnexpected token % occurred in % on line %

Source: osMon

Explanation: The specified token was found onthe specified line in the specified file. It wasnot expected.

Action: Edit the specified file.


336 |

S6BMN124EMatching 'end' for server definition blockmissing from %, line %

Source: osMon

Explanation: Gateways/servers started by anosMon process have definition files wherethe startup parameters for thegateway/server are stored. The parametersfor a given group of gateways/servers arelisted inside a definition block within thedefinition file. The definition block shouldbegin with a line of the form "begin <n>"(where <n> is the number ofgateways/servers which will be started withthe given parameters) and end with a line ofthe form "end". The ending line was notfound in the specified definition file on thespecified line.

Action: Edit the specified definition line, addingthe missing end line.

S6BMN125EServer definition corresponding to sessionname % is missing non-blank server type

Source: osMon

Explanation: In the gateway/server definitionfile (which is read by the osMon process inorder to run gateway/server processes), eachgateway/server definition block is requiredto specify the type of gateway/server that isto be started. A block was processed thatdoes not contain a gateway/server type.

Action: Edit the specified file, adding theappropriate gateway/server type.

S6BMN126L% started with pid=%. Executing server type %

Source: osMon

Explanation: This message is written to anosMon log file every time a correspondingosMon process starts a gateway/serverprocess.


S6BMN127ELogon Failed

Source: osMon

Explanation: The logon of an ActiveX Adapterclient to an osee server failed.


S6BMN128EAttempt to start an osee timed out

Source: osMon

Explanation: An attempt to start an osee timedout. When an osee is started, the osMon waitsCONNTIMEOUT seconds for the osee toconnect to the ActiveX Adapter client. If itfails to do so, this message is written to thelog and the connection to the client is closed.

Action: Increase the value of your osMonCONNTIMEOUT parameter.


| 337

S6BMN129IThe osMon DOB parameter is empty

Source: osMon

Explanation: The Data Object Broker parameterto the osMon is an empty string.

Action: When an osee is started, its Data ObjectBroker parameter defaults to the Data ObjectBroker parameter of the osMon that spawnedit. Therefore, all osees spawned by the osMonwhose Data Object Broker parameter isempty require their Data Object Brokerparameter to be set to a valid Data ObjectBroker name. The osee Data Object Brokerparameter can be set either from the ActiveXAdapter client or as an environment variablein a default file. Refer to the documentationon the osee for more information.

S6BMN130ECreate named pipe %

Source: osMon

Explanation: Creation of a named pipe (or FIFO)failed.

Action: Examine the operating system error codein order to determine the reason for thefailure.

S6BMN131EConnect to named pipe %

Source: osMon

Explanation: An attempt to connect to a namedpipe (or FIFO) failed.


S6BMN132ESet named pipe % property

Source: osMon

Explanation: An attempt to set a named pipe (orFIFO) property failed.


S6BMN133ECreate Windows Event Object

Source: osMon

Explanation: An attempt to create a WindowsEvent Object failed.

Action: Examine the operating system error codeto determine the reason for the failure. Themost common reason is lack of storage.

S6BMN134EDisconnect from named pipe %

Source: osMon

Explanation: An attempt to disconnect from anamed pipe (or FIFO) failed.

Action: Examine the operating system error codeto determine the reason for the failure.

S6BMN135EState error on named pipe %

Source: osMon

Explanation: The named pipe has entered aninvalid state.

Action: If operating system error codes do notprovide enough information to resolve thereason for this failure, contact TIBCOSupport.


338 |

S6BMN136Losee started. PID=% EE [%]:%

Source: osMon

Explanation: A child osee process was spawnedwith the given process ID, NAME, andINSTANCE number.


S6BMN137EThe maximum number of EE (%) that the osMoncan execute has been reached

Source: osMon

Explanation: The MON parameter MAXEEdetermines how many osee processes anosMon process can spawn simultaneously.An attempt was made to exceed the limit.

Action: Do either of the following:

• Increase the value of the MAXEEparameter.

• Increase the Execution EnvironmentMAXSESSION parameter, so that fewerosee processes can service the samenumber of sessions.

S6BMN138LRemote CLI or Java CLI logon

Source: osMon

Explanation: A Remote CLI or a Java CLI clientinitiated a logon.


S6BMN139LRemote CLI or Java CLI logon succeeded

Source: osMon

Explanation: A Remote CLI or a Java CLI logoncompleted successfully.


S6BMN140LRemote CLI or Java CLI logon failed

Source: osMon

Explanation: A Remote CLI or a Java CLI logonfailed.

Action: Examine the accompanying log messagesto determine the reason for the failure. Thestartup log may also provide pertinentinformation.

S6BMN142EInvalid host name specified: %

Source: osMon

Explanation: The host name specified in theMONHOST parameter is invalid.

Action: Determine the correct spelling of yourhost's name.


| 339

S6BMN143WIP address (%) does not correspond to host name(%). Using IP address

Source: osMon

Explanation: Both the IP and the HOSTExecution Environment parameters are set.However, the IP address corresponding tothe DNS name is not the same as the IPExecution Environment parameter.Therefore the NAME value is ignored andthe IP value is used.

Action: No action is required unless you want theHOST Execution Environment parameter tobe used. In this case, do not set the IPExecution Environment parameter.

S6BMN144INo host name or IP specified. osMon will listenon all IP addresses

Source: osMon

Explanation: Neither the HOST nor the IPExecution Environment parameters are setTherefore, the osMon process listens on all IPaddresses associated with the host it isrunning on.

Action: No action is required unless you want theosMon process to listen exclusively on aparticular IP address. If this is the case, youshould set either the HOST or the IPExecution Environment parameter.

S6BMN145ERemote CLI client or Java CLI client requestedunsupported code page

Source: osMon

Explanation: A Remote CLI or a Java CLIapplication attempted to use an unsupportedRemote CLI/Java CLI code page.

Action: Make sure that the application usessupported code pages, and that the @NLS1table is initialized as documented in the NLSmanual.

S6BMN200ELogon terminated at user's request

Source: osMon

Explanation: The user canceled the logonprocess.


S6BMN201EUnsupported version of TN3270 terminal

Source: osMon

Explanation: osMon process cannot acceptconnections from this terminal.

Action: Use either the IBM 3278 or the IBM 3279terminal.

S6BMN202EUnsupported TN3270 protocol

Source: osMon

Explanation: An error occurred during theTN3270 negotiation protocol.



340 |

S6BMN300EUnable to open osMon NAME parameterlockfile '%'

Source: osMon

Explanation: An attempt to create or open a diskfile failed. The disk file is used to ensure aNAME parameter is not in use by more thanone osMon process. Likely causes areinsufficient directory permissions or disk fullconditions.


S6BMN301EUnexpected file locking error during '%'command for osMon NAME parameter lockfile'%'

Source: osMon

Explanation: An attempt to get or set a file lockusing the fcntl(2) system call failed. The filelock is used to ensure a NAME parameter isnot in use by more than one osMon process.


S6BMN302EUnexpected file mapping creation error forosMon NAME parameter lockfile '%'

Source: osMon

Explanation: An attempt to create or open amemory-mapped file failed. The memory-mapped file is used to ensure a NAMEparameter is not in use by more than oneosMon process.


S6BMN303EUnexpected error mapping view of osMonNAME parameter lockfile '%'

Source: osMon

Explanation: An attempt to create a view of amemory-mapped file failed. The memory-mapped file is used to ensure a NAMEparameter is not in use by more than oneosMon process.



| 341

S6BMN304EosMon NAME parameter '%' is in use byprocess ID %

Source: osMon

Explanation: An osMon NAME parameter maynot be used by multiple osMon processesbecause it is used to uniquely identifyExecution Environment resources.

Action: Start osMon with a NAME parameterthat is not in use. A new set of defaultparameter assignments may have to beadded to the Object Service Broker monitorparameter source file.

S6BMN900EError occurred during an attempt to releaseresources

Source: osMon

Explanation: A failure occurred while the osMonwas shutting down.

Action: Restart the osMon process. If thismessage persists, contact TIBCO Support.


342 |

MS: Message Switch Address Space

S6BMS001IMESSAGE SWITCH READY date time

Source: Message Switch Address Space

Explanation: The Message Switch Address isready to accept requests


S6BMS002EUNDEFINED EVENT CODE X'____'


Explanation: Logic error. The supervisor hasdetected a physical event for which it doesnot have a service routine. The request isignored. Processing continues


S6BMS003ISHUTDOWN COMPLETED


Explanation: The message switch address spacehas successfully terminated.


S6BMS004EGETMAIN FAILED DURINGINITIALIZATION


Explanation: Allocation of storage required tocomplete Message Switch initializationfailed.


S6BMS005EINITIALIZATION ABORTED


Explanation: The initialization of a MessageSwitch address space has failed.

Action: Other messages will have been issued. Ifyou are still unable to ascertain the cause ofthis failure contact TIBCO Support.

S6BMS006IMAXIMUM CONNECTIONS OBSERVEDFOR THIS MESSAGE SWITCH WAS number'


Explanation: This message appears at the time ofMessage Switch shutdown and the numberin the message is the highest number of endusers connected simultaneously to thisinstance of the Message Switch.

Action: This message is for information only.


| 343

S6BMS007ISUBTASK DETACHED


Explanation: The indicated subtask has shutdown successfully.


S6BMS008E____ SUBTASK ABEND - S___/U____'


Explanation: A severe error occurred during theindicated subtask. The Object Service BrokerMessage Switch terminates abnormally. S___is the system abend code and U___ is theObject Service Broker abend code.

Action: If an Object Service Broker return code isprovided, look at previous console messagesfor more information. If only a system returncode is provided and you cannot resolve theproblem based on this code, contact TIBCOSupport.

S6BMS009EMESSAGE SWITCH INITIALIZATIONFAILURE - APF AUTHORIZATIONREQUIRED'


Explanation: During Message Switchinitialization, it was determined that theMessage Switch was not executed in an APFAuthorized state as required. The MessageSwitch will abend with user code 49.

Action: Refer to the Object Service BrokerDocumentation for instructions on how toAPF Authorize your Message Switch.

S6BMS010ESTORAGE NOT AVAILABLE


Explanation: Storage for an internal MessageSwitch control block was not available.

Action: Increase the region size and restart theMessage Switch

S6BMS011E____ SUBTASK ATTACH FAILED'


Explanation: The module for the indicatedsubtask cannot be accessed. Object ServiceBroker terminates abnormally.

Action: See the previous messages on the consoleand refer to the Installation and Operationsmanual.

S6BMS012E____ SUBTASK INITIALIZATION FAILED'


Explanation: An error occurred during theinitialization of the indicated subtask. ObjectService Broker terminates abnormally.

Action: See the previous messages on the consoleand refer to the Installation and Operationsmanual.


344 |

S6BMS013EGLOBAL ____ POOL BUILD FAILED'


Explanation: Insufficient storage was available tobuild the Message Switch resources for thespecified configuration.

Action: Refer to the Installation and Operationsmanual. Validate that the concurrencyoptions are compatible with the region sizespecified at Message Switch startup.

S6BMS014EABEND S___/U____ REAS=________DETECTED IN MODULE '


Explanation: The Message Switch has abendedas described in the message. If a SYSxDUMPdata set was allocated to the Message Switch,it will contain the dump for the error.

Action: Collect as much information about thefailure as possible and contact TIBCOSupport.

S6BMS015EEVENT (____) REJECTED IN ________,MESSAGE SWITCH TERMINATING


Explanation: The module identified by"taskname" received an event to process"xxxx" and the Message Switch started thetermination process. The "termtype" valuecan be either "NORMALLY" indicating aSHUTDOWN request was issued or"ABNORMALLY" indicating a task abended.The requested event processing is ignored.

Action: Wait for the termination to complete andthen recycle the Message Switch.

S6BMS016EMUST BE ASSIGNED A VALUE


Explanation: The indicated parameter does nothave an associated assigned value. AllMessage Switch parameters are of the form:keyword=value. Spaces are not permittedbetween the keyword, equal sign, or value.The parameter is rejected. Object ServiceBroker Message Switch startup terminatesabnormally.

• Object Service Broker non-swappable

• Cross Memory Services for Object ServiceBroker inter-region communication

• Internal Object Service Broker SMFrecords (optional)

• Journal offload (spin) by Started SystemTask (optional)

Action: Correct the parameter in error.

S6BMS017IREFER TO MESSAGE SWITCH PARMS ININSTALLATION MANUAL


Explanation: An error was detected in yourObject Service Broker initializationparameters.

Action: Refer to the Job message log forpreceding specific parameter error(s). Referto the Object Service Broker Documentationfor parameter syntax, spelling, ranges,defaults.


| 345

S6BMS018EMSWPARMS FILE BYPASSED - INVALIDRECFM OR LRECL'


Explanation: An MSWPARMS DD statementwas provided, but its record format was notfixed block, or its record length was not 80.Data Object Broker initialization continues.Parameter values are default values unless aPARM= string containing override values isprovided.

Action: If Object Service Broker started withincorrect parameter values, shut it down. Doone of the following:

• Allocate an MSWPARMS file withRECFM=FB and LRECL=80, and supplythe correct parameter assignments.

• If Object Service Broker runs as a batch job,you can use //MSWPARMS DD * todefine parameters in- stream.

• If the parameter specifications are 100characters or less, you can omit//MSWPARMS and just use the PARM=string.

When ready, restart Object Service Broker.

S6BMS019EMSWPARMS FILE BYPASSED - OPENUNSUCCESSFUL


Explanation: A MSWPARMS DD statement wasprovided but failed to open properly. DataObject Broker initialization continues.Parameter values are default values unless aPARM= string containing override values isprovided.

Action: If Object Service Broker started withincorrect parameter values, shut it down.Investigate the MSWPARMS file problem.When the problem is resolved, restart ObjectService Broker.

S6BMS020E_____________ PARM CONTAINS INVALIDCHARACTER(S)'


Explanation: The indicated parameter containscharacters which are not alphabetic. Theparameter is rejected. Object Service Brokerstartup terminates abnormally.

Action: Verify and correct the spelling of theparameter. Refer to the Installation andOperations manual if necessary.

S6BMS021E_____________ PARM IS AMBIGUOUS'


Explanation: The indicated parameter wasabbreviated so that it is no longer unique.The parameter is rejected. Object ServiceBroker startup terminates abnormally.

You can spell Data Object Broker parametersin full or abbreviate them throughtruncation. For example, SNAPOVERRIDE


346 |

or SNAPOVER or SNAPO are all accepted.Excessive truncation, however, results inabbreviations that can be one of severalparameters. For example, SNAP might beany one of SNAPCLASS, SNAPREMOTE,SNAPQUERY, SNAPOVERRIDE, orSNAPVOLSER.

Action: Spell the parameter keyword name morefully or completely. In general, fivecharacters are sufficient to achieveuniqueness. Refer to the Installation andOperations manual if necessary.

S6BMS022E_____________ PARM IS NOT DEFINED'


Explanation: The indicated parameter (only thefirst 13 characters appear in the message) isnot defined to Object Service Broker. Youmay have used an unrecognizableabbreviation. The parameter is rejected.Object Service Broker startup terminatesabnormally.

Action: Verify the spelling of the parameter.Refer to the Installation and Operationsmanual if necessary. Abbreviation throughtruncation is permitted, but it isrecommended that at least the first fiveletters be supplied to ensure uniqueness.

S6BMS023EPARM NOT DYNAMICALLY MODIFIABLE


Explanation: An operator console command wasissued, of the form:

MODIFY jobname,PARM=keyname=value

The keyname specified was a recognizedObject Service Broker Data Object Brokerparameter, but it is not eligible for

modification after startup or once set. Theparameter change is rejected. Object ServiceBroker execution continues.

Action: If the parameter must be changed thenthis change must be made to the ObjectService Broker Data Object Brokerinitialization parameters and will take effectthe next time Object Service Broker isrestarted.

S6BMS024E_____________ SPECIFIED VALUE HAS TOOMANY CHARACTERS'


Explanation: The value assigned to the keywordhas too many characters. The parameter isrejected. Object Service Broker startupterminates abnormally.

Action: Provide an acceptable parameter value in//MSWPARMS or PARM= string. Refer tothe Installation and Operations manual ifnecessary.

S6BMS025E_____________ SPECIFIED VALUECONTAINS INVALID CHAR(S)'


Explanation: The value assigned to theparameter has failed its edit validity check.This occurs for any non-alphanumeric value,or for a discrepancy between editspecifications and the input provided. Theparameter is rejected. Object Service Brokerstartup terminates abnormally.



| 347

S6BMS026E_____________ SPECIFIED VALUE NOTVALID QUALIFIER(S)'


Explanation: The value assigned to theparameter has failed its validity check. Adata set name or qualifier, member name, orother entity with similar syntax wasexpected. The parameter is rejected. ObjectService Broker startup terminatesabnormally.

Action: Provide an acceptable parameter value in//MSWPARMS or PARM= string. Refer tothe Installation and Operations if necessary.

S6BMS027E_____________ SPECIFIED VALUE OUT OFRANGE'


Explanation: The value assigned to theparameter is too big or too small. Theparameter is rejected. Object Service Brokerstartup terminates abnormally.


S6BMS028EGETMAIN FAILURE ON ____ POOL, ____SPACE _____ THE LINE ON A ____BOUNDARY, RC=


Explanation: Object Service Broker manages itsown storage in blocks referred to as pools.When attempting to acquire storage tosupport, the specified pool the storage wasnot available.

Action: Determine why the storage requirementswere not satisfied. Check the memory controlparameters on the run and increase asneeded. Contact TIBCO Support if furthersupport is required.

S6BMS029EXCF MEMBER NAME AND GROUP NAMEBOTH SET TO ___________


Explanation: The XCF group and member nameare identical. This is not allowed.

Action: Modify either the XCF group or membername and restart the message switch.

S6BMS201EUNDEFINED EVENT CODE X'____'


Explanation: The Communications subtaskreceived a request that it does not support.The request is ignored. Normal processingcontinues.

Action: Try to identify the circumstances whichtrigger this message. An isolated occurrencemay be insignificant. Contact TIBCO Supportif there are multiple occurrences or relatedproblems.


348 |

S6BMS202ENO COMMUNICATION FACILITIESAVAILABLE'


Explanation: No Communications protocols areavailable to the Object Service BrokerMessage Switch. Object Service Broketerminates abnormally.

Action: Look for any associated messages whichprovide further explanation. If this is aninitial installation, ensure that thecommunication definitions required byObject Service Broker are in place. If you areunable to resolve the situation, contactTIBCO Support.

S6BMS203LUSER LIMIT EXCEEDED, CONNECTIONREJECTED - ________


Explanation: When attempting to connect a usersession the configured limit was exceeded.

Action: Review the MAXUSERS parameter todetermine if it is set appropriately for therequired workload.

S6BMS204EUNFORMATTED LOGON REJECTED


Explanation: An unformatted logon request hasbeen received by the Message Switch.

Action: The logon request is rejected with a sensecode of x'0C00'. This is normally caused byan attempt to connect to the Message Switchin error. If the message is issued repeatedlytry to ascertain the source of the request. Ifyou are unable to resolve the situation,contact TIBCO Support.

S6BMS205EREQUEST __________ RETURN CODE ____FOR ________ USER ________ # =______ FROM_____'


Explanation: A request for action has failed withreturn code given.

Action: If you are unable to determine the causeof the message, contact TIBCO Support.

S6BMS206IUSER ________ #=______ CANCELLED'


Explanation: The specified user has beencancelled.

Action: None

S6BMS207Lconnectid action TERM=termid J=jobnameconnecttype #=num S=source T=target


Explanation: This notification message identifiesa logon or logoff from the message switch.

• .connectid may or may not be uniquedepending on site configuration

• .action is either 'LOGGED ON' or'LOGGED OFF'

• .termid is the terminal identification or'UNKNOWN'

• .jobname is the jobname of the connector

• .connecttype is the type of connection e.g.'TSO USER'

• .num is the relative connection block usedto support this connection. It is alwaysunique.


| 349

• .source is the communication type for thesource session

• .target is the communications type for thetarget session

Action: None.

S6BMS601ESERVICES SUSPENDED - INITIALIZATIONFAILURE


Explanation: Services provided by theoperations support task indicated in themessage are not available due to the failureof this task to initialize.

Action: Review the initialization messages in theMessage Switch's job log to determine thereason for the failure. Terminate and restartthe Message Switch at the earliestopportunity after the problem is resolved.

S6BMS602EOPER INITIALIZATION FAILED


Explanation: An error has been encounteredduring the initialization of the MessageSwitch's console interface. Message Switchinitialization continues but console servicesare not available.

Action: Review the initialization messages in theMessage Switch's job log to determine thereason for the failure. Terminate and restartthe Message Switch at the earliestopportunity after the problem is resolved.

S6BMS603IOPER INITIALIZATION COMPLETED'


Explanation: Initialization was successful for thetask supporting operator console MODIFYcommands. You can enter Object ServiceBroker MODIFY commands and receive aresponse.


S6BMS604EUNDEFINED EVENT CODE X''____''


Explanation: This message indicates that aninvalid post code has been received by theMessage Switch's operational support taskand cannot be processed.


S6BMS605IMODIFY COMMAND ACCEPTED


Explanation: This message is the standardacknowledgement that the command is validwhen no more specific reply exists.

Action: None

S6BMS606WFREE WORK BUFFER FAILED ' ____


Explanation: Upon completion of externalcommand processing, the work buffer usedto carry the command could not be released.



350 |

S6BMS607ESERVICES TERMINATED


Explanation: The operations support servicestask indicated in the message terminated dueto an unrecoverable failure. The system willattempt a restart of the failing task.

Action: Review the Message Switch's job log todetermine the reason for the failure andreport this problem to TIBCO Support.

S6BMS608E_______ SERVICES SUSPENDED - RESTARTLIMIT EXCEEDED'


Explanation: The operations support serviceindicated in the message could not berecovered after a failure. These services aredisabled until the Message Switch isrestarted.

Action: Review the Message Switch's job log todetermine the reason for the failure andreport this problem to TIBCO Support.

S6BMS609ERE-INSTATING _______ SERVICES


Explanation: This message indicates thatautomatic recovery is in progress for theservice indicated in the message.

Action: Begin an investigation into the cause ofthe initial failure. If the service is successfullyreinstated, no immediate action is required.

S6BMS610ERESTART OF _______ SERVICES '


Explanation: This message is issued to indicatethe success or failure of the restart action forthe indicated operations service.


S6BMS611WSPECIFIED USER NOT LOGGED ON



F jobname,action=userid

The specified USER was not logged on toObject Service Broker. No action is taken.

Action: No action required. The command:

F jobname,USERLIST

displays a list of the userids logged on toObject Service Broker.

S6BMS612IDUPLICATE ______ DETECTED


Explanation: The console command detectedmultiple userid/termids and needs to knowwhich userid/termid to act upon.

Action: Reissue the command with ";xxxx",where xxxx is the mswcnum from messageS6BMS514I.


| 351

S6BMS613IUSERID TERMID JOBNAME TYPEMSWCNUM STATUS SOURCE TARGET


Explanation: These are the headings for messageS6BMS614I.

Action: None

S6BMS614I________ ________ ________ __________________ _______ ______ ____


Explanation: S6BMS613I shows headings for thedata rows in S6BMS614I; The data inS6BMS614I is used to determine the differentuserid/termids.

Action: May be used to determine whichmswcnum to use when a console commandis issued.

S6BMS615ITOTAL NUMBER OF DUPLICATES ______'


Explanation: This message displays the count ofduplicate entries.

Action: None

S6BMS616IREPEAT COMMAND AS____________USERID;MSWCNUM"


Explanation: The console command could notdetermine which duplicate entry to act on.S6BMS614I lists the commnum of allduplicates.

Action: Reissue the console command with";mswcnum" at the end of the command,where the mswcnum is from the precedingS6BMS614I messages.

S6BMS617WUNEXPECTED USER ID FOUND INSPECIFIED MSWCOMMA


Explanation: A display/cancel user request wasissued. The buffer identified as containingthe user information is invalid.

Action: Retry the cancel request. If the errorrecurs, contact TIBCO Support.

S6BMS618ISPECIFIED MSWCOMMA NUMBER OUT OFRANGE, REQUEST REJECTED'


Explanation: A CANCELUSER/DISPLAYUSERrequest was issued with an explicatemswcomma number, the suppliedmswcomma number is out of range.

Action: Correct the request and resubmit.


352 |

S6BMS621ECANCEL DENIED - DBMS SERVER'



F jobname,CANCELUSER=server_id

The ID specified is a DBMS gateway. Noaction is taken.

Action: Use the Data Object BrokerSTOPSERVER command to shut down aDBMS gateway.

S6BMS623WGET WORK BUFFER FAILED ____


Explanation: A CANCELUSER command wasissued to terminate a user or DBMS gateway.Because no work buffer was available, therequest could not be processed.

Action: The command may succeed if reissued. Ifthis message occurs again, the reason for thelack of work buffers should be investigated.

S6BMS624ECANCEL DENIED - LOGOFF IN PROGRESS


Explanation: A request was received by theMessage Switch to cancel a specified usersession that is currently being terminated.The request cannot be fulfilled.

Action: No action is required

S6BMS625ELENGTH OF SPECIFIED USER ID IS OUT OFRANGE


Explanation: A command was entered and thespecified userid was not between 1 and 8characters long, for example,CANCELUSER=uuuuuu;nnnn. The userid(uuuuuu) must be 1 to 8 characters long.

Action: Enter the command again with thecorrect format.

S6BMS626ENO DATA SENT, COMMAND REJECTED'


Explanation: The console command wasreissued but no data was detected beyond ";".

Action: Reissue the command with the desiredmswcnum.

S6BMS627EMSWCNUM NOT NUMERIC, COMMANDREJECTED'


Explanation: The data in the console commandafter the ";" was not numeric.

Action: Reenter the console command with anumeric value for the mswcnum.


| 353

S6BMS628EMSWCNUM TOO LARGE, COMMANDREJECTED'


Explanation: The mswcnum entered was greaterthan the highest allocated mswcnum.

Action: Check the value of the mswcnum andreenter the command.

S6BMS629ILOGGED ON USERS/DBMS/OPER/JOBS



F jobname,USERLIST

S6BMS629I is the heading followed by the response data. They are followed by summary messages S6BMS630I and S6BMS631I. If no Object Service Broker users are logged on, only S6BMS630I and S6BMS631I are issued.

Object Service Broker connections areidentified by their userid. The format of thedisplay is c-uuuuuuuu, where:

• c is the connection type

• uuuuuuuu is the userid

The valid connection types are:

• blank - TSO Execution Environment User

• C - CICS Execution Environment user

• N - Native Execution Environment user

• I - IMS TM Execution Environment user

• U - Solaris Execution Environment user

• t - Other Execution Environment user

• J - Batch Job

• D - DBMS Server connection or OutboundPeer (HRN)

• O - Operator connection

• P - Inbound Peer connection (HIN)

• L - Connection that is in the process oflogging on

• ? - Unknown connection type


S6BMS630IUSERS DBMS OPER JOBS OTHER AVAIL'


Explanation: See explanation for messageS6BMS629I.


S6BMS631I_' ____ _____ _____ _____ _____ _____"


Explanation: See explanation for messageS6BMS629I.


S6BMS632E_____________ CANNOT BE ASSIGNED AVALUE'


Explanation: A MODIFY command was issuedin the form "command=value". Theparticular command verb specified isdefined to be a one word action commandwithout any assigned value. The command isrejected.

Action: The command can be reissued withoutan assigned value, if appropriate. If in doubt,refer to the operator commanddocumentation in the Installation andOperations manual.


354 |

S6BMS633E_____________ COMMAND CONTAINSINVALID CHARACTER(S)'


Explanation: Verify the spelling of the command.Refer to the Installation and Operationsmanual if necessary.

Action: The indicated command containscharacters that are not alphabetic. Thecommand is rejected.

S6BMS634E_____________ COMMAND IS AMBIGUOUS'


Explanation: The indicated command has beenabbreviated so that it is no longer unique.The command is rejected. Object ServiceBroker MODIFY commands may be spelledin full or abbreviated through truncation.Excessive truncation results in abbreviationsthat can be one of several that can be one ofseveral commands.

Action: Spell the parameter keyword name morefully, or completely. Generally, 5 charactersare adequate to achieve uniqueness. Refer tothe Installation and Operations manual ifnecessary.

S6BMS635E_____________ COMMAND IS NOT DEFINED'


Explanation: The indicated command (only thefirst 12 characters appear in the message) isnot defined to Object Service Broker. Youmay have used an unrecognizableabbreviation. The command is rejected.

Action: Verify the spelling of the command. Referto the Installation and Operations manual ifnecessary. Abbreviations are only recognizedif they are spelled the same as the fullcommand up to the point of truncation.

S6BMS636E_____________ REJECTED, SHUTDOWN INPROGRESS'


Explanation: The specified request was rejectedbecause Object Service Broker had alreadyaccepted a shutdown request.

Action: Object Service Broker is coming down --no action required.

S6BMS637E_____________ MUST BE ASSIGNED AVALUE'


Explanation: A MODIFY was issued as a oneword action command. The particularcommand verb is defined to be for a"keyword=value" command. The commandis rejected.

Action: Provide an appropriate value whenissuing this command. Refer to theInstallation and Operations manual ifnecessary.


| 355

S6BMS638E_____________ SPECIFIED VALUE HAS TOOMANY CHARACTERS'


Explanation: The value assigned to the keywordhas too many characters. The command isrejected.


S6BMS639E_____________ SPECIFIED VALUECONTAINS INVALID CHAR(S)'


Explanation: The value assigned to thecommand failed its edit validity check. Thiserror occurs for any non-alphanumericvalue, or for a discrepancy between editspecifications and the input provided. Thecommand is rejected.


S6BMS640E_____________ SPECIFIED VALUE NOTVALID QUALIFIER/DSNAME'


Explanation: The value assigned to thecommand failed its validity check. A data setname or qualifier, member name, or otherentity with similar syntax was expected. Thecommand is rejected.


S6BMS641WCONSOLE MESSAGE BUFFER FREE FAILED'


Explanation: The processing of operator consolemessages encountered a problem whilefreeing a message buffer. This may result infailure of the Operator Command Interface.

Action: If operator console MODIFY commandsare no longer being accepted, contact TIBCOSupport.

S6BMS642ECOMMAND NOT PROCESSED, COULD NOTOBTAIN BUFFER'


Explanation: The Message Switch was not able toobtain the work area needed to process anoperator request. This is usually a temporarysituation and should be resolved almostimmediately.

Action: Reenter the rejected operator command.If the problem persists, obtain a dump of theMessage Switch and terminate it at yourearliest convenience. Notify TIBCO Support.

S6BMS643LMODIFY ' _________________________________________"


Explanation: The command received from theconsole is echoed. This verifies commandrecognition and records the command in theconsole log for the Object Service BrokerMessage Switch.



356 |

S6BMS644INO USERS CONNECTED


Explanation: There are no user sessionsconnected to this message switch.


S6BMS701EUNDEFINED EVENT CODE X''____'''


Explanation: Internal logic error. Object ServiceBroker supervisory code detected an invalidsystem service request. The transaction isaborted.


S6BMS702EXCF REQUEST ________ FAILED RETURNCODE ____ REASON CODE ____'


Explanation: An XCF request failed.

Action: Look up the return code and reason codefor the failing request in the IBM SysplexServices Reference. If unable to determinethe cause of the failure contact TIBCOSupport.

S6BMS703EIXCQUERY ____ RECORDS NOTRETRIEVED'


Explanation: The internal buffer for theIXCQUERY response was not sufficientlylarge to accommodate all the recordsreturned by the IXCQUERY request.


S6BMS704EPRIMARY DATA OBJECT BROKERLOCATION TIME INTERVAL EXPIRED'


Explanation: A primary Data Object Broker wasnot located in the time specified.

Action: The Message Switch will terminate. Ifrequired restart the Message Switch.

S6BMS705WPRIMARY DATA OBJECT BROKER NOTAVAILABLE


Explanation: The Message Switch could notlocate the Primary Data Object Broker.

Action: If allowed the message switch will waitfor a Primary Data Object Broker to becomeavailable, if not the Message Switch willterminate. Make sure a Primary Data ObjectBroker is available and restart the MessageSwitch.

S6BMS706IPRIMARY DATA OBJECT BROKERLOCATED AT MEMBER NAME ________'


Explanation: The Message Switch has located thePrimary Data Object Broker.



| 357

S6BMS707IGROUP STATUS FOR XCF GROUP gggggggg


Explanation: Output from a Memberlist MessageSwitch command. gggggggg is the XCFgroup to which the Data Object Brokerbelongs.


S6BMS708IMEMBER JOBNAME SYSTEM SYSTEMSTATE USER STATE'




S6BMS709I------ ------- ------ ------------ ----------'




S6BMS710Immmmmmmm jjjjjjjj xxxxxxxx ssssssss tuuuuuuu


Explanation: Output from a MemberlistCommand. One line for each member in theXCF group:

• mmmmmmmm XCF Member name

• jjjjjjjj Job Name

• xxxxxxxx System Name

• ssssssss System State

• t Member Type

• P Primary Data Object Broker

• S Secondary Data Object Broker

• M Message Switch

• uuuuuu User State



358 |

NC: Network Control

S6BNC100I"SRBEXIT=NO" CODED/DEFAULTED ONVTAM APPLID='%', BUT ADDRESS SPACEIS AUTHORIZED

Source: Network Control

Explanation: The VTAM Application Identifierassigned for the use of an Object ServiceBroker communications environment isdefined with a VTAM APPL statement thatspecifies or defaults the SRBEXIT keywordoperand to the value of NO, but the ObjectService Broker communications environmentis executing in an APF Authorized addressspace.

This message is issued to bring attention tothe fact that, since the address space is APFAuthorized, the SRBEXIT keyword operandcould be coded with a value of YES. Thiswould allow VTAM to schedule the ObjectService Broker VTAM ACB and NIB exitsusing z/OS SRBs, which reduces CPUutilization and increase multiprocessingconcurrency.

The APPLID is the VTAM ApplicationIdentifier that is used by the Object ServiceBroker Region, and which has SRBEXIT=NOcoded in its definition.

Action: If you do not expect the APFAuthorization of the Object Service BrokerRegion using this VTAM ApplicationIdentifier to be downgraded toUnauthorized at some time in the future, youcan change the SRBEXIT keyword operandon the VTAM APPL statement (inSYS1.VTAMLST, in a VTAM Major NodeDefinition for Object Service Broker Network

Resources) for the VTAM ApplicationIdentifier used by the Object Service BrokerRegion. Change it to specify SRBEXIT=YESto achieve a performance improvement inCPU utilization and multiprocessingconcurrency. If the APF Authorization of theObject Service Broker Region is at some latertime rescinded, the SRBEXIT keywordoperand must again be changed. SpecifySRBEXIT=NO; otherwise, messageS6BNC998E will be issued (indicating anOPEN request failed withACBERFLG=X'F4'), and the Object ServiceBroker Region will fail during initialization.

S6BNC870W"UNBIND" REQUEST UNIT RECEIVED,APPLID='%', LU='%', TYPE=X'%'


Explanation: An SNA UNBIND Request Unitwas received by the Object Service BrokerRegion for one of its sessions, indicating theloss of the session for an exceptional reason.This message is issued if session terminationwas not solicited.

The message provides the followinginformation:

• The APPLID is the VTAM ApplicationIdentifier that is used by the Object ServiceBroker Region.

• The LU is the VTAM Logical Unit name ofthe session partner network resource thathas (directly or indirectly) caused the SNAUNBIND Request Unit to be generated.


| 359

• The TYPE is the hexadecimal UNBINDTYPE code from the SNA UNBINDRequest Unit. Interpretations of this codecan be found in the IBM manual SystemsNetwork Architecture Formats.

Action: The VTAM session is lost. To resumecommunications, request a new session.

S6BNC871E"CINIT" REQUEST UNIT REJECTED,APPLID='%', LU='%', IMPROPER SESSIONPARAMETERS ARE INDICATED:


Explanation: An SNA CINIT Request Unit wasreceived by the Object Service Broker Region,representing a pending logon from somenetwork resource. The Object Service BrokerRegion rejected the SNA CINIT RequestUnit, due to unacceptable values in thesession parameters. The SNA CINIT RequestUnit is rejected with an SNA Sense CodeX'08210000', which will be conveyed by thenetwork in an SNA UNBIND Request Unit tothe rejected session's session partner LogicalUnit.



• The LU is the VTAM Logical Unit name ofthe session partner Logical Unit that hadits request for a session rejected.

This message is usually followed bymessages S6BNC872I and S6BNC873I, whichconvey additional information about theunacceptable session parameters.

Action: The request for a session was rejected.The session parameters associated with theLogical Unit must be corrected before furtherattempts to establish a session are made.

S6BNC872I%


Explanation: An SNA CINIT Request Unit wasreceived by the Object Service Broker Region,representing a pending logon from somenetwork resource. The Object Service BrokerRegion has rejected the SNA CINIT RequestUnit, due to unacceptable values in thesession parameters. The session parametersfrom the SNA CINIT Request Unit aredisplayed in this message as a string ofhexadecimal digits.

This message is usually preceded bymessage S6BNC871E and followed bymessage S6BNC873I.

Action: The request for a session has beenrejected. The session parameters associatedwith the LU must be corrected before furtherattempts to establish a session are made.

S6BNC873I%


Explanation: An SNA CINIT Request Unit wasreceived by the Object Service Broker Region,representing a pending logon from somenetwork resource. The Object Service BrokerRegion has rejected the SNA CINIT RequestUnit, due to unacceptable values in thesession parameters. This message contains acursor that indicates the particular sessionparameter(s) that is (are) the reason forrejecting the SNA CINIT Request Unit.

This message is preceded by messageS6BNC872I. The cursor in this message isaligned with the hexadecimal digits in thesession parameters in message S6BNC872I


360 |

that are the reason for rejecting the SNACINIT Request Unit.

Action: The request for a session has beenrejected. The session parameters associatedwith the LU must be corrected before furtherattempts to establish a session are made.

S6BNC874E"LOGON" CONVERSATION REJECTED,APPLID='%', LU='%', RETURN CODE: X'%'


Explanation: An SNA APPC Conversation thatwill Logon a new Object Service Broker userto the Object Service Broker Data ObjectBroker has arrived from another ObjectService Broker Region in the network. Due toconditions apparent at the time of the arrivalof the new Conversation, the Logon has beenrejected by the Data Object Broker. Themessage provides the following information:

• The APPLID is the character encodedname of the Object Service Broker DataObject Broker that was the target of theSNA APPC Conversation.

• The LU is the character encoded name ofthe SNA Session Partner Logical Unit thatoriginated the SNA APPC Conversation.

• The RETURN CODE is the hexadecimalencoded value of the Return Code that theData Object Broker generated to describethe situation that caused it to reject theSNA APPC Conversation. The four digitsdisplay a two-digit return code followedby a two-digit reason code.

Action: The request for a Conversation wasrejected. The originating ConversationPartner will act on the information containedin the Return Code made available to it. Referto message S6BKC036I for an explanation ofthe return code and reason code.

S6BNC875EVTAM ATTN(FMH5) LOGIC ERROR,APPLID='%', LU='%', MODENAME='%':ATTEMPTING SDUMP


Explanation: An SNA APPC Conversationintended to logon a new Object ServiceBroker user to the Data Object Broker arrivedfrom another Object Service Broker region inthe network. Due to timing conditions,Object Service Broker is unable to uniquelyidentify the SNA session that theconversation has been allocated to. TheObject Service Broker APPC LU 6.2implementation is unable to continueprocessing data on this conversation, andwill reject the Logon. Also, if systemauthority is sufficient, an SDUMP will bescheduled to aid in diagnosing the errorcondition. The message provides thefollowing information:

• The APPLID is the character-encodedname of the Object Service Broker DataObject Broker that was the target of theSNA APPC Conversation.

• The LU is the character-encoded name ofthe SNA Session Partner Logical Unit thatoriginated the SNA APPC Conversation.

• The MODENAME is the character-encoded name of the VTAM LogmodeTable entry that was used for theConversation.

Action: The request for a Conversation wasrejected. The originating ConversationPartner may retry the request, as the errorcondition is probably temporary. If the errorreoccurs, it may be necessary to shut downthe originating partner's VTAM LU in orderto terminate all the VTAM sessions betweenit and the Data Object Broker.

In any case, if this message is issued, collectany diagnostic information available


| 361

(System Log printout, JES Log for theaffected Object Service Broker regions, andany dumps produced) and contact TIBCOSupport.

S6BNC880W"NOTIFY" REQUEST UNIT RECEIVED,PLU='%', SLU='%', STATUS=X'%',REASON=X'%', SENSE=X'%'


Explanation: A VTAM session cannot beestablished.

The Object Service Broker region received anSNA NOTIFY Request Unit for one of itssessions. Currently, an SNA NOTIFYRequest Unit is generated only by the failureof session establishment initiated by aVTAM REQSESS RPL Request. This messageis issued if session establishment wasrefused after the VTAM REQSESS Requestwas successfully completed. This messagecontains significant data from fields in theSNA NOTIFY Request Unit received.


• The PLU is the character encoded name ofthe SNA Primary Logical Unit that hadbeen engaged in the session.

• The SLU is the character encoded name ofthe SNA Secondary Logical Unit that hadbeen engaged in the session.

The hexadecimal values provided by themessage are as follows:

• Although it is not shown in this message(because the SNA NOTIFY Request Unit isgenerated as the result of a failure duringsession establishment), the NOTIFYCONTROL VECTOR KEY field contains avalue of x'03'.

• The STATUS is the hexadecimal NOTIFYSTATUS field contents.

• The REASON is the hexadecimal NOTIFYREASON field contents.

• The SENSE is the hexadecimal NOTIFYSENSE field contents.

Interpretations of these codes can be foundin the IBM manual Systems NetworkArchitecture - Formats, and as describedbelow.

Additional messages will have been issuedbased on the interpretation of the SENSEdata receive in the SNA NOTIFY RequestUnit.

If an Object Service Broker region refusedthe connection, then the STATUS andREASON codes are x'03' and x'80'respectively, and the sense code has theformat x'0000eerr', where "ee" is the errorcode and "rr" is the reason code for therefusal, both reported in hexadecimal. If thetarget of the connection is a Data ObjectBroker, refer to the Explanation for messageS6BKC036 for the interpretation of thesecodes.

Action: Examine the reported status, reason, andsense codes, as well as the additionalmessages issued, to determine what action isrequired for the specific situation or error.

S6BNC881W"CLEANUP" REQUEST UNIT RECEIVED,PLU='%', SLU='%'


Explanation: An SNA CLEANUP Request Unitwas received by the Object Service BrokerRegion for one of its sessions. This RequestUnit notifies the Object Service BrokerRegion of the loss of the VTAM session, so


362 |

that the resources allocated to support thesession can be released. This messagecontains significant data from fields in theSNA CLEANUP Request Unit received.


• The PLU is the character encoded name ofthe SNA Primary Logical Unit that hadbeen engaged in the lost session.

• The SLU is the character encoded name ofthe SNA Secondary Logical Unit that hadbeen engaged in the lost session.Additional messages are issued inresponse to the activity of releasing theVTAM session's resources.

Action: The VTAM session is lost. To resumecommunications, request a new session.

S6BNC882WVTAM ATTN(LOSS) EXIT ENTERED,APPLID='%', LU='%', MODENAME='%',RPL6FLG3=X'%'


Explanation: An SNA Session that was initiatedto support APPC Conversations has beenterminated, and VTAM has driven the ObjectService Broker ATTN Exit with a LOSS event.The message names the Object ServiceBroker APPLID, the name of theConversation Partner LU and the SNAModename (these two items define the LMTable entry), and the significant indicatorsfrom the RPL6FLG3 field.


• The APPLID is the character encodedname of the Object Service Brokerapplication to which VTAM has reportedthe ATTN(LOSS) event.

• The LU is the character encoded name ofthe SNA Session Partner Logical Unit thathad been engaged in the lost session.

• The MODENAME is the characterencoded name of the VTAM LogmodeTable entry that was used for the lostsession.

• The RPL6FLG3 is the hexadecimalinterpretation of the RPL6DERC andRPL6LAST indicators from the VTAMRead-Only RPL that was made availableby VTAM to the Object Service BrokerATTN(LOSS) exit.

Action: The VTAM session is lost. This isprobably the result of a coordinateddeactivation of one of the Logical Unitsinvolved. This message is issued fordocumentation purposes only.

S6BNC883EPROTOCOL OR STATE ERROR ONSESSION, APPLID ='%', LU='%' - SESSIONTERMINATED


Explanation: An unexpected situation hasoccurred on an SNA session in an ObjectService Broker Region for one of its sessions.Either the defined protocol rules have beenviolated or an invalid state has been reached.An example of a protocol error is thetransmission of an unsupported Data FlowControl request unit. An example of a stateerror is the arrival of data on a session that isin the "send" state.


• The LU is the VTAM Logical Unit name ofthe session partner network resource that


| 363

has caused the SNA Response Unit to begenerated.

Action: The VTAM session in error is lost. Toresume communications, request a newsession. You should determine the reason theunexpected event occurred and correct theproblem. A VTAM buffer trace will assist inthis determination.

If the session was with another ObjectService Broker region, contact TIBCOSupport.

S6BNC888ECOMMUNICATIONS IDENTIFIER "%" ISNOT ACCEPTING SESSIONS


Explanation: An attempt by the current ObjectService Broker communications environmentto contact another Object Service Brokercommunications environment using theNetwork Communication (SNA) ObjectService Broker CommunicationsImplementation has failed because the targetObject Service Broker communicationsenvironment has not yet initialized itself as aVTAM Application.

Action: If the target Object Service Broker Regionis required, ensure that it is executing, andhas successfully initialized its Object ServiceBroker communications environment.

S6BNC889EVTAM VERSION Vv.r.l INSUFFICIENT FOROBJECT SERVICE BROKER'S APPC<LU 6.2>IMPLEMENTATION


Explanation: While attempting to connect thecurrent Object Service Brokercommunications environment with anotherObject Service Broker communicationsenvironment, it was determined that theappropriate Object Service BrokerCommunications Implementation to supportthe communication was SNA APPC (LU 6.2).The version/release level of VTAM that isinstalled is insufficient for use by ObjectService Broker, however, and so SNA APPCcannot be used.

This message is likely to be issued only if theversion/release level of the VTAM in use atthe installation is very old.

Action: If the version/release level of theinstalled VTAM is very old, upgrade to amore current VTAM.

S6BNC890WLOSTERM EXIT ENTERED, APPLID='%',LU='%', REASON CODE=X'%'


Explanation: The VTAM LOSTERM Exitsupplied by the Object Service Broker Regionwas driven by VTAM. This exit is enteredwhen a VTAM session is being deactivated orlost.



• The LU is the VTAM Logical Unit name ofthe session partner network resource


364 |

whose session with the Object ServiceBroker Region has been lost.

• The REASON CODE is the hexadecimalvalue of the Reason Code passed byVTAM to the VTAM LOSTERM Exit. TheReason Code supplies details about thedisposition of the topic VTAM session.Interpretations of the Reason Codes can befound in the IBM manual VTAMProgramming.

Additional messages may have been issuedin response to the activity of releasing theVTAM session's resources.

Action: The VTAM session is lost. Loss of theVTAM session may be the result ofdeactivating Network Resources by a VTAMConsole Operator. To resumecommunications, request a new session.

S6BNC900WTPEND EXIT ENTERED, APPLID='%',REASON CODE=X'%'


Explanation: The VTAM TPEND Exit suppliedby the Object Service Broker Region is drivenby VTAM. This exit is entered when a VTAMApplication Definition is being deactivatedby the system operator, or when VTAM isabnormally terminating.



• The REASON CODE is the hexadecimalvalue of the Reason Code passed byVTAM to the VTAM TPEND Exit. TheReason Code supplies details about thedisposition of the Object Service BrokerRegion's status as a VTAM Application.Interpretations of the Reason Codes can be

found in the IBM manual VTAMProgramming.

Additional messages may have been issuedin response to the activity of relinquishingthe Object Service Broker Region's VTAMApplication Program status.

Action: The Object Service Broker Region's statusas a VTAM Application Program either hasbeen lost, or is being relinquished gracefully.Loss of the VTAM Application Programstatus may be the result of a VTAM consoleoperator deactivating Network Resources.Refer to the accompanying messages todetermine what action is required for thespecific situation or error.

S6BNC991EVTAM RESP EXIT ENTERED WITHUNSOLICITED "%" %RSP,APPLID='*UNKNWN*', LU='*UNKNWN*' -SESSION TERMINATED


Explanation: An unexpected SNA Response Unitwas received by the Object Service BrokerRegion for one of its sessions. It is either anunsolicited positive response to normal flowdata, or else it is an unsupported responsetype.


• The type of response unit received, whichmay be:

• *UNKNWN*

• FMDATA

• CANCEL

• QC

• CHASE

• BID

• RTR


| 365

• LUSTAT

• BIS

• Whether the response was positive (+RSP)or negative (-RSP)


• The LU is the VTAM Logical Unit name ofthe session partner network resource thathas caused the SNA Response Unit to begenerated.

Action: The VTAM session in error is lost. Toresume communications, request a newsession. You should determine the reason theunexpected response unit was generated andcorrect the problem.

If the session was with another ObjectService Broker region, contact TIBCOSupport.

S6BNC992EAPPC ERROR LOG DATA RECEIVED -> %


Explanation: While engaged in an SNA APPC(LU 6.2) Conversation, an error was detectedby the conversation partner Logical Unit,and an APPC Error Log string was sent to thecurrent Object Service Brokercommunications environment. The text fromthe APPC Error Log string is contained in themessage. The conversation will have beenterminated.

Action: The text of the APPC Error Log stringprovides an explanation of the error thatoccurred in the conversation partner LogicalUnit. Any specific action to be taken dependson the content of this text.

S6BNC993EVTAM APPCCMD RPL REQUEST ERRORDETECTED, APPLID='%', LU='%'CONTROL=%, QUALIFY=%, RCPRI='%',RCSEC='%'


Explanation: A physical error related to an LU6.2 API request issued to VTAM wasdetected by VTAM and passed to ObjectService Broker. Such an error can disruptcommunication on the APPC Conversationfor which the request was issued. Thismessage contains significant data from fieldsin the VTAM RPL (Request Parameter List)that conveyed the failed request to VTAM.This message is in two parts, due to thelength of the text that it contains.


• The APPLID is the character encodedname of the Object Service BrokerApplication to which VTAM has reportedthe LU 6.2 Request failure.

• The LU is the character encoded name ofthe SNA Session Partner Logical Unit thatis engaged in the SNA session for whichthe LU 6.2 Request failure has occurred.

• The CONTROL and QUALIFY are thecharacter encoded names that togetherdescribe the VTAM LU 6.2 API Requesttype that has failed. The purpose of theseVTAM RPL requests can be found in theIBM manual Macro Instructions.

• The RCPRI and RCSEC are thehexadecimal interpretations of the VTAMLU 6.2 API's Primary and SecondaryReturn Codes made available in the VTAMRPL Extension of the VTAM RPL used toissue the failed VTAM LU 6.2 Request.Interpretations of these codes can be foundin the IBM manuals VTAM Programmingfor LU 6.2.


366 |

If the error is accompanied by nonzero Sensedata, this message will be followed by:

S6BNC994E SENSE DATA PRESENT, RPL6SN SI=X' %'

Action: This message is issued to providedocumentation about the error that has beendetected. The affected Object Service Brokercomponent is advised of the error and takessubsequent action to remedy or recover fromthe error.

S6BNC994ESENSE DATA PRESENT, RPL6SNSI=X'%'


Explanation: A physical error related to an LU6.2 API request issued to VTAM wasdetected by VTAM and passed to ObjectService Broker. Such an error can disruptcommunication on the session for which therequest was issued. This message is alwayspreceded by:

S6BNC993E VTAM APPCCMD RPL REQUEST ERROR DETECTED, APPLID='%', LU='%', CONTROL=%, QUALIFY=%, RCPRI=X'%', RCSEC='%'

which describes the VTAM RPL Request thatwas issued, and the exceptional or abnormalcondition that was encountered. TheS6BNC994E message contains additionalsignificant data from fields in the VTAMRPL (Request Parameter List) that conveyedthe request in error to VTAM.

The RPL6SNSI is the hexadecimalrepresentation of the System Sense Codedata stored in the VTAM RPL Extension todescribe the physical error encountered.Interpretations of this code can be found in

the IBM manual VTAM Messages andCodes.

Action: Since this message augments themessage that precedes it, refer to thepreceding message to determine the properaction to take.

S6BNC995EVTAM % EXIT ENTERED, APPLID='%', {LU='%',} RPLREQ=%,RPLRTNCD/RPLFDB2=X'%'


Explanation: A physical error or logical errorrelated to a request issued to VTAM wasdetected by VTAM and passed to ObjectService Broker. Such an error can disruptcommunication on the session for which therequest was issued. This message containssignificant data from fields in the VTAM RPL(Request Parameter List) that conveyed thefailed request to VTAM.


• The first variable data item is substitutedwith either "SYNAD" or "LERAD",signifying either a physical or a logicalerror, respectively.


• The LU is the VTAM Logical Unit name ofthe session partner network resource forthe session that has experienced theproblem. This item may be omitted fromthe message if it cannot be determined,such as in the case of a logical error.

• The RPLREQ is the type of VTAM RPLRequest that was issued. The purpose ofthese VTAM RPL requests can be found inthe IBM manual instructions.


| 367

• The RPLRTNCD/RPLFDB2 data is thehexadecimal return and feedback codesfrom VTAM that describe the physical orlogical error encountered.

Interpretations of these codes can be foundin the IBM manuals VTAM Programmingand VTAM Messages and Codes.

If the first variable item is replaced by"SYNAD" (indicating a physical error), thismessage may be followed by:

S6BNC996E SENSE DATA PRESENT, SSENSEI/SSENSMI=X'%', USENSEI=X'%'

Action: Action depends on the interpretation ofthe data extracted from the RPL for the failedrequest. In the case of a physical error("SYNAD" specified), the problem canusually be identified and corrected ifinformation in the message and relevantmanuals is interpreted by personnel familiarwith VTAM networks. If remedial actioncannot be determined, contact TIBCOSupport. In the case of a logical error("LERAD" specified), although correctiveaction can be taken for some logic errors, aprogramming fix is usually required. If this isthe case, contact TIBCO Support.

S6BNC996ESENSE DATA PRESENT,SSENSEI/SSENSMI=X'%', USENSEI=X'%'


Explanation: A physical error related to a requestissued to VTAM was detected by VTAM andpassed to Object Service Broker. Such anerror can disrupt communication on thesession for which the request was issued.This message is always preceded by:

S6BNC995E VTAM SYNAD EXIT ENTERED, RPLREQ=%, RPLRTNCD/RPLFDB2=X' %'

which describes the VTAM RPL Request thatwas issued, and the exceptional or abnormal

condition that was encountered. TheS6BNC996E message contains additionalsignificant data from fields in the VTAMRPL (Request Parameter List) that conveyedthe request in error to VTAM.

The SSENSEI/SSENSMI data is thehexadecimal System Sense Code and SystemSense Modifier data stored in the VTAM RPLto describe the physical error encountered.Interpretations of this code can be found inthe IBM manual VTAM Messages andCodes.

The USENSEI is the hexadecimal User SenseCode data stored in the VTAM RPL todescribe the physical error encountered. Ifthe SSENSEI/SSENSMI data is nonzero,then interpretations of the USENSEI codecan be found in the IBM manual VTAMMessages and Codes.

Action: Since this message augments themessage that precedes it, refer to thepreceding message to determine the properaction to take.

S6BNC997EVTAM % % REQUEST FAILED, R15=X'%',R0=X'%'


Explanation: A VTAM Manipulative MacroInstruction request has failed. A Return Codeand possibly a Reason Code were providedby VTAM in registers 15 and 0 respectively,describing the reason for the request failure.Interpretations of the Return and ReasonCodes can be found in the IBM manualVTAM Programming. The VTAMManipulative Macro Instruction is one of thefollowing:

• GENCB

• MODCB

• SHWCB


368 |

The VTAM Control Block being manipulatedis one of the following:

• ACB

• RPL

• NIB

• LNG

Action: Action depends on the interpretation ofthe Return and Reason Codes provided byVTAM. This message usually indicates that aprogramming fix is required. If this is thecase, contact TIBCO Support.

S6BNC998EUNABLE TO % VTAM ACB, APPLID='%',R15=X'%', ACBERFLG=X'%'


Explanation: A VTAM ACB-Based MacroInstruction failed. The message provides thefollowing information:

• The first variable item is the name of theVTAM ACB-based Macro Instruction thatwas issued, either OPEN or CLOSE.


• A Return Code is provided by VTAM inregister 15 describing the reason for therequest failure.

• The contents of the ERROR field(ACBERFLG) from the VTAM ACB is alsoprovided in the message.

Interpretations of the Return Code andERROR field can be found in the IBMmanual VTAM Programming, in the section

for the appropriate VTAM ACB-BasedMacro Instruction.

Action: Contact the person who supports theVTAM Network to interpret the ERROR fieldextracted from the VTAM ACB anddetermine remedial action. If remedial actioncannot be determined, contact TIBCOSupport.

S6BNC999EMVS % REQUEST FAILED, R15=X'%'


Explanation: A request for a system serviceprovided by z/OS has failed. A Return Codewas provided by z/OS in register 15describing the reason for the request failure.The request is one of the following:

• ESTAE

• GQSCAN

• GETMAIN

• FREEMAIN

Action: Refer to the appropriate z/OS manual fora description of the service requested and thereason for the failure as described by theReturn Code. Determine remedial action byconsidering the information provided in themanual. If the problem persists, contactTIBCO Support.


| 369

OU: Open Transaction Mgr Access

S6BOU001EOTMA error Function=% RC=% reason1=%reason2=% reason3=% reason4=%

Source: Open Transaction Mgr Access

Explanation: The OTMA module return code isnon-zero.

Action: Review the information in the messageand in the IBM "IMS Open TransactionManager Access Guide and Reference"manual, and take the appropriate action.


370 |

PF: Journal Formatting

S6BPF001ISPACE = __________ MEGABYTES

Source: Journal Formatting

Explanation: Upon completion of the Journalformatting process, this message is written toindicate the size of the Journal just processed.


S6BPF002EJOURNAL TOO SMALL - LESS THAN 10 MEG


Explanation: When attempting to format theJournal data set, it was determined that thedefined space was less than the minimumallowed.

Action: Increase the size of the Journal andresubmit the job.

S6BPF003EJOURNAL NOT EMPTY


Explanation: When attempting to format theJournal data set, it was determined that thedata set was not empty.

Action: Delete and redefine the Journal, andresubmit the job.

S6BPF004EVSAM OPEN ERROR


Explanation: When attempting to open theJournal data set for formatting, VSAMindicated an open error.


S6BPF005EJOURNAL CI SIZE TOO SMALL


Explanation: When attempting to format theJournal, it was determined that the controlinterval size was invalid.

Action: Delete and redefine the Journal data withthe correct CI size and resubmit.

S6BPF006EVSAM WRITE ERROR RC=XX FDBK=YY


Explanation: When attempting to output aformatted record to the Journal, VSAMdetected an error.

Action: Refer to the VSAM manual for the returncode and feedback codes indicated in themessage.


| 371

PR: EE Parameter Processing

S6BPR001EParameter area storage overflow

Source: EE Parameter Processing

Explanation: User has specified too much ObjectService Broker parameter data.

Action: Review the HRNIN parameter input fileand verify that it contains valid ObjectService Broker parameters, that all quotedstring end with a quote, and that parameterlists end with a closing parenthesis.

S6BPR002EInvalid token classification


Explanation: Object Service Broker parameterinput token could not be classified.


S6BPR003EExceeded depth that parameters may be nested


Explanation: The value of an Object ServiceBroker parameter had parentheses that werenested to a depth greater than 8.

Action: Verify that a closing parenthesis is notmissing in the input parameter string or theHRNIN input file. If the value of theparameter is a string that containsparenthesis, then quote the string.

S6BPR004EParameter '%' previously specified


Explanation: A parameter has been used morethan once.

Action: Object Service Broker parameters mayonly be specified once in an input string orHRNIN input file. Remove the duplicateparameter reference.

S6BPR005EMissing end of comment


Explanation: Closing "*/" of a comment ismissing.

Action: All comments that start with the string"/*" must end with a closing "*/" string. Editthe input parameter string, or the HRNINinput file, and insert a closing "*/" whererequired.

S6BPR006EMissing end of quote for parameter %


Explanation: Closing quote for a string ismissing.

Action: All quoted strings should start with aquote and end with a quote. Edit the inputparameter string, or the parameter input file,and insert a closing quote where required.


372 |

S6BPR007ESyntax error in line % at column %


Explanation: A syntax error was detected at theline and column specified.

Action: Review the Object Service Brokerparameter input string, or HRNIN file, at theline specified, and correct the syntax error.

S6BPR008EValue of parameter '%' is not an integer


Explanation: The value for the Object ServiceBroker parameter is not an integral value.

Action: The specified Object Service Brokerparameter may be set only to an integervalue. Integer values consist of numericdigits preceded by an optional minus sign.An integer value may also be appended by aunits indicator where "K" specifies the valueis a multiple of 1024 and "M" specifies thevalue is a multiple of 1024*1024 or 1048476.Correct the parameter value in the inputparameter string or in the HRNIN input file.

S6BPR009EInteger value is too small for parameter '%'


Explanation: The value for the Object ServiceBroker parameter is beyond the minimalrange for the parameter.

Action: The Object Service Broker parameterspecified has a minimal value. Correct theparameter value in the input parameterstring or in the HRNIN input file.

S6BPR010EInteger value is too big for parameter '%'


Explanation: The value for the Object ServiceBroker parameter is beyond the maximumrange for the parameter.

Action: The Object Service Broker parameterspecified has a maximum value. Correct theparameter value in the input parameterstring or in the HRNIN input file.

S6BPR011IUnable to load registry keyHKEY_LOCAL_MACHINE\\SOFTWARE\\Amdahl\\ObjectStar\\CurrentVersion\\%


Explanation: An attempt to load the specifiedregistry key failed.

Action: Reboot your system and try again. If itcontinues to fail, contact TIBCO Support.

S6BPR012EString too short for parameter '%'


Explanation: The length of the value for theObject Service Broker parameter is too small.

Action: Correct the parameter value in the inputparameter string or in the HRNIN input file.


| 373

S6BPR013EString (%) is too long for parameter '%'


Explanation: The value you want to assign to theObject Service Broker parameter is too long.

Action: Correct the length of the value in theinput parameter string or in the HRNINinput file.

S6BPR014EReserved word '%' was assigned a value


Explanation: A reserved word parameter cannotbe set a value.

Action: A reserved word cannot appear to the leftof an equal sign. Correct the input parameterstring or the HRNIN input file.

S6BPR015EReserved word '%' must have an element list


Explanation: A reserved word parameter wasincorrectly defined in the Object ServiceBroker system code.


S6BPR016EValue '%' is invalid for parameter '%'


Explanation: An Object Service Brokerparameter has an invalid value.

Action: Review the documentation for theparameter to determine what values may beassigned to the parameter.

S6BPR017EKeyword element does not have an action


Explanation: An Object Service Brokerparameter was incorrectly defined in ObjectService Broker system code.


S6BPR018EInvalid value type


Explanation: An Object Service Brokerparameter was incorrectly defined in ObjectService Broker system code.


S6BPR019EParameter source '%' contains unsupportedparameter '%'


Explanation: The parameter specified is notsupported by Object Service Broker. It iseither not valid or misspelled, or it is notallowed in the specified HRNIN.

Action: Check in the Parameters Manual for thedescription and correct spelling of theparameter.

S6BPR020EArea too small for a value store


Explanation: Object Service Broker system codeallocated too small a work area for parameterprocessing.



374 |

S6BPR021EParameter '%' has been previously specified


Explanation: An Object Service Brokerparameter has been entered more than once.

Action: Delete the duplicate reference to thesame parameter.

S6BPR022EIncorrect number of names for parameter '%'


Explanation: The value of this parameter consistsof a list of names; an incorrect number ofnames has been specified.

Action: Review the source of the parameter valueand ensure that the correct number of listelements is specified.

S6BPR023EBad name length for parameter '%'


Explanation: The value of this parameter consistsof a list of names and one of the items in thelist has an incorrect length.

Action: Review the source of the parameter valueand correct the list element in error.

S6BPR024EIncorrect syntax for name list for parameter '%'


Explanation: This parameter consists of a list ofnames and an item in the list is not a validname.

Action: Review the source of the parameter valueand correct the list element in error.

S6BPR025EEncountered unexpected % after text '%'


Explanation: The unexpected string after theindicated text resulted in a syntax error.

Action: Review the source of the parameter textand correct the syntax error. Note thatseparating parameters with commas isoptional. However, the location of syntaxerrors tends to be more specific if commas areused.

S6BPR026EEncountered unexpected % at beginning of line


Explanation: The string specified results in asyntax error.

Action: Review the source of the parameter textand correct the syntax error. Note thatseparating parameters with commas isoptional. However, the location of syntaxerrors tends to be more specific if commas areused.

S6BPR027EValue for keyword parameter '%s' missing


Explanation: A keyword parameter wasspecified without providing a value for thekeyword.

Action: Reenter the Object Service Brokercommand and specify a value for thekeyword.


| 375

S6BPR028IUnable to open registry keyHKEY_LOCAL_MACHINE\\SOFTWARE\\Amdahl\\ObjectStar\\CurrentVersion\\%\\%


Explanation: An attempt to open the specifiedWindows Registry key failed.


S6BPR029IUnable to open registry keyHKEY_LOCAL_MACHINE\\SOFTWARE\\Amdahl\\ObjectStar\\CurrentVersion\\%


Explanation: An attempt to open the specifiedregistry key failed.

Action: Reboot your system and try again. If itcontinues to fail, contact TIBCO Support.

S6BPR030EInvalid type for value % whose key isHKEY_LOCAL_MACHINE\\SOFTWARE\\Amdahl\\ObjectStar\\CurrentVersion\\%\\%


Explanation: The type of the specified WindowsRegistry key is not what TIBCO ObjectService Broker expects it should be.


S6BPR031EHKEY_LOCAL_MACHINE\\SOFTWARE\\Amdahl\\ObjectStar\\CurrentVersion\\%\\% has a value whose name (%) is not aparameter name


Explanation: The specified Windows RegistryKey contains a value whose name is not aparameter name.

Action: Remove the value from the key.

S6BPR032WMore than one group of parameter assignmentsindexed by % in %


Explanation: Two or more groups of parameterassignments are preceded by a NAMEassigned with the same value.

Action: Edit the specified location, so that eachNAME assignment assigns a unique value.

S6BPR033IFailed to load parameter file %


Explanation: The process is unable to load thespecified parameter file.

Action: No action is required unless you want touse the specified parameter file. If it does notexist, create it. If it exists, and is in%OS_ROOT%\database, check theoperating system error code.


376 |

S6BPR034EInvalid system ROOT setting [%]. Check formissing path


Explanation: The system ROOT is set incorrectly.Object Service Broker processes need thissetting to locate log and parameter filefolders.

Action: Set the system ROOT to the name of anaccessible folder. Refer to your Installationand Operations manual about setting thesystem ROOT.

S6BPR035EInvalid system ROOT setting [%]. It is not thename of a directory


Explanation: The system ROOT is set incorrectly.Object Service Broker processes need thissetting to locate log and parameter filedirectories.

Action: Set the system ROOT to the name of anaccessible directory. Refer to yourInstallation and Operations manual aboutsetting the system ROOT.

S6BPR036EInvalid system DATEFORMAT setting %


Explanation: The default date format parameteris not set correctly. Default date formats oflength six (6) are not permitted.

Action: Set the DATEFORMAT parameter to avalid string such as YYYY-MM-DD. Avoidsix-byte formats.

S6BPR100EError occurred on attempt to make '%' thecurrent working directory


Explanation: An osee failed in its attempt to setits working directory to the value to which itsWORKINGDIR startup parameter is set.


S6BPR101IDefaults successfully generated


Explanation: The installation defaults utilitydetected no errors and successfullygenerated installation defaults.

Action: Verify that the subsequent assembly andlink of the defaults member were successful.

S6BPR103ECould not open output file '%' for generateddefaults


Explanation: The installation defaults utilitycould not open the output file for thegenerated installation defaults.

Action: Verify that the output file has beenallocated for the job step for the utility.


| 377

S6BPR104EDefaults not generated because error wasdetected


Explanation: The installation defaults utilitydetected an error and stopped generatingdefaults.

Action: Review the error messages in the utilitymessage file to determine the errors detected.

S6BPR105ECould not open input file '%' for installationdefaults


Explanation: The installation defaults utilitycould not open the input file for theinstallation default parameters.

Action: Verify that the input file has beenallocated for the job step for the utility.

S6BPR106ECould not open output file '%' for messages


Explanation: The installation defaults utilitycould not open the message file.

Action: Verify that the message file has beenallocated for the job step for the utility.

S6BPR107ECould not load parameter definition table,HRNPRMD


Explanation: The installation defaults utilitycould not load the Object Service Brokerparameter definitions load module.

Action: Verify that the job step for the utilitycontains a STEPLIB or JOBLIB DD card thatreferences the Object Service Broker loadlibrary data set.

S6BPR108ECould not initialize value store


Explanation: The installation defaults utilitydetected an error at parameter processinginitialization time.


S6BPR200EParameter processing error detected in line %dof %s %s


Explanation: A parameter processing error wasdetected at the line specified.

Action: Review the source file listed at the linespecified to determine the error.

S6BPR201EParameter processing error detected in startsession command


Explanation: An error was detected in thecommand line entered.

Action: Review the line entered to determine the

error.


378 |

S6BPR202ELine %d of %s too long because of expansionenvironment variable(s)


Explanation: The substitution of theenvironment variables results in a parameterinput that is too long.

Action: Substitution variables consist of a "$"character followed by a name. Verify that thecorrect variable names have been specifiedand that they are set to the correct values. Ifthey are correct, then the parameter file inputline must be split into two or more lines.

S6BPR203EParameter file name %s/%s too long


Explanation: The parameter file name is longerthan the maximum 256 characters.

Action: Verify that the correct file name has beenspecified. The path name for the installationparameter file name is determined by theObject Service Broker environment variableand may be overridden by the Object ServiceBroker Execution Environment parameter.The path name for the session parameter fileis determined by the HOME environmentvariable and the complete session parameterfile name can be overridden by the HRNINenvironment variable.

S6BPR900EError occurred during attempt to releaseresources


Explanation: During the release of systemresources such as memory or file storage, afailure occurred. As a result, the process inwhich this occurred is in an invalid state.

Action: Restart the associated process.

S6BPR952IFailed to expand environment string in registryvalue %, keyHKEY_LOCAL_MACHINE\\SOFTWARE\\Amdahl\\ObjectStar\\CurrentVersion\\


Explanation: The process failed to expandenvironment variable strings contained inthe specified registry value.

Action: Change the value of the registry variable.

S6BPR995LThe OS_ROOT environment variable has beenset to '%'


Explanation: The OS_ROOT environmentvariable has been set to the specified value.

Action: No action is required. This message tellsyou the default location for parameter files(%OS_ROOT%/database) and log files(%OS_ROOT%/log).


| 379

S6BPR996EThe OS_ROOT environment variable has notbeen set


Explanation: The OS_ROOT environmentvariable is not set, and the process that issuedthis message is not able to determine areasonable value to assign to OS_ROOT.

Action: Add OS_ROOT to your environment andrestart the process.

S6BPR997EFirst rule name is too long: '%'


Explanation: The first rule name, specified in theRULE parameter to an osee process, is toolong.

Action: The rule name cannot be more than 16characters long. Reenter the RULE parameterwith a shorter value.

S6BPR998EFirst rule parameter list is too long: '%'


Explanation: The parameters to the first rule arenot permitted to be longer than 256characters.

Action: Check the value of the parameterspassed, along with the rule name in theRULE parameter of the osee. Make surequote and parenthesis characters areproperly paired off and that the length of theparameters does not exceed 256 characters.

S6BPR999EInvalid rule parameter


Explanation: The osee failed to parse theparameters provided for the first rule in itsRULE startup parameter.

Action: Check the value of the RULE parameter.Make sure string parameters are enclosed insingle quotes and numeric parameters areproperly specified.


380 |

PX: POSIX ON support for EMS

S6BPX002EPOSIX TCB initialization error; Load ofS6BDRPSX DLL failed

Source: POSIX ON support for EMS

Explanation: The DLL S6BDRPSX could not beloaded. The Execution Environment task forrunning EMS did not successfully initializeand EMS will not be available for ruleapplications.

Action: Look at the job log for more informationabout why the S6BDRPSX DLL could not beloaded.

S6BPX003EPOSIX TCB initialization error; Load ofPSXIROUT variable for DLLS6BDRPSX failed


Explanation: Initialization of the POSIX TCBfailed. EMS will not be available for rulesapplications.

Action: Look at the job log for more informationabout why PSXIROUT could not be loaded.

S6BPX004EPOSIX task thread intialization error at #; #failed with errno=#


Explanation: Initialization of dispatch threadsfailed. The Execution Environment task forrunning EMS did not successfully initializeand EMS will not be available for ruleapplications.

Action: For more informations about errnovalues, refer to the IBM z/OS UNIX SystemServices Messages and Codes.

S6BPX005EPOSIX task thread error at #; # failed witherrno=#


Explanation: POSIX task detected en error. If theerror occurred during POSIX taskinitialization then EMS will not be availableto rules applications. If the error occurredwhile processing an EMS request then therequest is aborted and the rule is notified ofthe error. The message displays the UNIXSystem Service call that failed and the errnofor the error.

Action: For more information about errno values,refer to the IBM z/OS UNIX System ServicesMessages and Codes. The description of theerrno may indicate a system limit has beenexceeded or an incorrect setting of a systemservices parameter. Otherwise contactTIBCO Support.


| 381

S6BPX006EPOSIX task thread error at #; # is an invalidrequest code


Explanation: A service thread in the POSIX taskhas detected a bad request code. The EMSrequest was aborted.

Action: Contact TIBCO support.

S6BPX007EPOSIX task thread termination error at #; ; failedwith errno #


Explanation: Termination of the POSIX taskfailed. A UNIX system service failed.Execution Environment termination willcontinue.


S6BPX008EPOSIX task intialization error at #; # failed witherrno=#


Explanation: POSIX task initialization failed.EMS will not be available for rulesapplications.


S6BPX009EPOSIX task termination error at #; # failed witherrno=#


Explanation: POSIX task termination failed.Execution Environment termination willcontinue.



382 |

S6BPX010EPOSIX task run request error at #; # failed witherrno=#


Explanation: An UNIX System Services errorwas detected while processing a POSIX taskrequest. The request will be aborted and therule requesting rule notified of the error.

Action: For more information about errno values,refer to the IBM z/OS UNIX System ServicesMessages and Codes. The description of theerrno may indicate a system limit has beenexceeded or an incorrect setting of a systemservices parameter. Otherwise contactTIBCO Support

S6BPX012EPOSIX task intialization error at #; failed tocreate a $SAVE area


Explanation: Initialization of the POSIX taskfailed. Interfaces like EMS will not beavailable to rule applications.

Action: Check whether a sufficient region sizewas specified for the job step. Otherwisecontact TIBCO Support.

S6BPX013EPOSIX task run request error at #; QueueMananer call failed with RC=#


Explanation: An error was detected when theresult of a POSIX task request was sent to thecalling rule.

Action: The hung session maybe killed andresources released by the cancel usercommand for the Execution Environment orData Object Broker. Contact TIBCO Support.

S6BPX014EPOSIX task initialization error; Set of errorresume point failed with feedback code #


Explanation: Resume point for errors in a POSIXtask worker thread could not be established.Initialization for the thread terminated.


S6BPX015EPOSIX task initialization error; Creation oferror handler failed with feeback code #


Explanation: Error handler could not be createdfor a POSIX task thread. The thread wasterminated.


S6BPX016EPOSIX task initialization error; Set of host andwire encoding failed failed with status code #


Explanation: POSIX task could not set the hostand wire encoding for the EMS interface.EMS is unavailable for rule applications.

Action: Verify that code page name used by theExecution Environment parameter,EMSWIRECODEPAGE, is a valid code page.The name must be a valid IBM ICONV codepage name for your MVS system.


| 383

S6BPX100EEMS initialization failed: Return code #, Reasoncode #


Explanation: The initialization failed for anexternal TIBCO supplied API. It will bedisabled for the life of the ExecutionEnvironment.

Action: A return code of 4 with a reason code 4indicates a failure to load the EMS interfacecode S6BDRPSX. Check the installation ofEMS support. A return code of 8 with areturn code of 0 indicates thatTASKPOSIXNUM is set to 0. SetTASKPOSIXNUM to 1 and retry. For anyother values contact TIBCO support.

S6BPX101EEMS is not supported


Explanation: TIBCO EMS is not supported in thisExecution Environment.

Action: Modify the EMS API parametersTASKPOSIXNUM andTHREADPOSIXNUM or the EMS APIparameter EMSWIRECODEPAGE asrequired.

S6BPX102EEMS function ";" failed: Reason code is #


Explanation: The EMS function failed with thereason code listed.

Action: Keep any logs and dumps produced forthis failure and report this error to TIBCOsupport.

S6BPX103EEMS function name conversion failed


Explanation: The routine name coded asargument of the shareable tool S6BCALL orS6BFUNCTION could not be converted to avalid variable length string.

Action: Correct the routine name supplied

S6BPX104EEMS function ";" not supported


Explanation: The routine name supplied is notsupported by either the S6BCALL or theS6BFUNCTION shareable tool.

Action: Correct the function name.

S6BPX105EIncorrect number of arguments for shareabletool ";"


Explanation: The number of arguments suppliedto the shareable tool is not correct for thefunction being invoked.

Action: Correct the argument list for theshareable tool


384 |

S6BPX106EEMS prior initialization attempt failed: Returncode #, Reason code #


Explanation: See the explanation for message:EMS initialization failed: Return code #,Reason code #

Action: See the action for message: EMSinitialization failed: Return code #, Reasoncode #

S6BPX107ERoutine ";" cannot be object of ";"


Explanation: The routine cannot be invoked bythis shareable tool. Either the routine returnsa value and is being invoked using shareabletool S6BCALL or the routine does not returna value and is being invoked byS6BFUNCTION.

Action: Use the correct shareable tool to invokethe routine.

S6BPX201EMismatch between EMSWIRECODEPAGE andnational language settings


Explanation: The value of the parameterEMSWIRECODEPAGE must be either UTF-8or match the code page name in the ASCIIoccurrence of @NLS1, if present, or ISO8859-1 (the default), if not present.

Action: Correct the value of theEMSWIRECODEPAGE parameter.


| 385

RA: TCP/IP RELAY

S6BRA001ITCP/IP RELAY started; Incoming connectionswill not be accepted

Source: TCP/IP RELAY

Explanation: Communications services will notaccept incoming TCP/IP connections for thiscomponent.

Action: If the component needs to acceptconnections from TCP/IP then look in the joblog for previous messages that will explainwhy connections will not be accepted. Lookat your RELAY parameter file to ensure thatthe communication identifier for yourcomponent is defined correctly.

S6BRA003EOutbound connection rejected. Insufficientnumber of socket handles


Explanation: TCP/IP connection could not beestablished because no more socket handlescould be opened.

Action: Increase the maximum number of sockethandles for the component using the RELAYparameter file. Either increase the maximumnumber of sockets for a TCP/IP RELAY TCBby incrementing the "maxtcbsockets"parameter or increase the number of TCP/IPRELAY TCBs by incrementing the "tcbnum"parameter.

S6BRA004EAttach of TCP/IP communications task failedwith R15=%


Explanation: TCP/IP RELAY initialization failedwhen attaching a relay TCB. TCP/IP supportfor the Object Service Broker component isunavailable. R15 contains the return codefrom the ATTACH macro that failed.

Action: Refer to the description of the returncodes for the ATTACH macro in the IBMMVS Authorized Assembler ServicesReference manual to determine what actionshould be taken.

S6BRA005EInitialization of TCP/IP communicationsRELAY task failed


Explanation: Initialization of the TCP/IP RELAYfailed. TCP/IP support for the component isdisabled.

Action: Refer to the previous message for moreinformation.


386 |

S6BRA006EObtain of storage failed during intialization ofTCP/IP RELAY with R15=%


Explanation: Initialization of the TCP/IP RELAYfailed when allocating memory. TCP/IPcommunications support has been disabled.R15 contains the reason why the STORAGEmacro failed.

Action: Refer to the description of return codesfor the STORAGE macro in the IBM MVSAssembler Services Reference manual todetermine the action to be taken.

S6BRA007ECommunications identifier "%" not defined inthe RELAY parameter file


Explanation: Open of communications nodefailed because the node was not defined inthe RELAY parameter file.

Action: Assure the communications identifier isdefined in the directory section of yourRELAY parameter file.

S6BRA008ITCP/IP RELAY started; Accepting connectionson interface address % socket port=%


Explanation: TCP/IP support for the componentsuccessfully initialized. New socketconnections are being accepted on theadapter interface and port numberdisplayed.


S6BRA009ITCP/IP RELAY stopped


Explanation: TCP/IP support for the componenthas been terminated. New socketconnections are no longer being accepted.


S6BRA011EConnection to node "%" failed; Host "%" isunavailable


Explanation: Open of a TCP/IP connection failedbecause the host was unavailable.

Action: Assure that the correct host name or IPaddress was used in the definition of thecommunication identifier in the directorysection of your RELAY parameter file.

S6BRA012EConnection to node "%" failed; CONNECTsocket request failed with errno=%


Explanation: Open of a new connection failedbecause socket connect called error.

Action: Refer to the return code appendix of theIBM IP Sockets Application ProgrammingInterface Guide and Reference to determinethe meaning of the errno value and the actionto be taken.


| 387

S6BRA013IConnection to node "%" refused


Explanation: Connection to the node wasrejected or the socket port for the node wasnot open.

Action: Verify that the remote node has beenstarted. If the node is running then check thejob log for the node to determine why theconnection was rejected.

S6BRA014ESocket receive error with errno=%; TCP/IPconnection closed


Explanation: A socket receive error was detectedduring the exchange of data between thecomponent and a TCP/IP remotecommunications node. The connection wasclosed.

Action: Refer to the return code appendix of theIBM IP Sockets and ApplicationProgramming Guide and Reference todetermine the meaning of the errno and theaction to be take. The most common cause isthat the remote node closed the connection.

S6BRA015ESocket send failed; TCP/IP connection closed


Explanation: Socket send failed during theexchange of data to the remote node. Theconnection was automatically closed.

Action: If this problem repeats then contactTIBCO Support.

S6BRA016EFailed to allocate DXE memory; TCP/IPconnection closed


Explanation: The TCP/IP RELAY failed toallocate memory for a buffer for a receiverequest. The connection was automaticallyclosed.

Action: Increase the region size in the JCL.

S6BRA017ERELAY connection failed with RC=%; TCP/IPconnection closed


Explanation: TCP/IP RELAY could not open aCross Memory connection for the newTCP/IP connection. The new clientconnection was automatically closed.

Action: View the SYSLOG for additional data onthe error, and contact TIBCO Support iffurther assistance is required.

S6BRA018EUnexpected socket read; TCP/IP connectionclosed


Explanation: Remote connect sent data when itwas not expected. The connection wasautomatically closed.

Action: A non Object Service Broker applicationmay be attempting to use the Object ServiceBroker port. Otherwise contact TIBCOSupport.


388 |

S6BRA019EOpen of socket listening port failed; % requestfailed with errno=%


Explanation: Open of the Object Service Brokenlisting port failed. TCP/IP support wasdisabled.


S6BRA020ECould not determine socket port number fornode communications identifier %


Explanation: The service name used in thedefinition of the port number for thecommunication identifier could not beresolved.

Action: Review the directory section of yourRELAY parameter file and assure the correctservice name has been specified. If the nameis correct then assure that the service name isdefined for your MVS system.

S6BRA021EConnection to node "#" failed; GETSOCKOPTsocket request failed with errno=#


Explanation: Outbound connection to nodefailed. GETSOCKOPT was called to confirmwhether non-blocking socket connect wassuccessful but the call failed.


S6BRA022EHost name "%" for communications identifier"%" could not be resolved


Explanation: Host name could not be resolved toan IP address.

Action: Assure that the host name for thecommunications identifier was enteredcorrectly in the directory section of yourRELAY parameter file. Otherwise the namespecified may not be defined on your MVScommand. Use the PING command on yourMVS system to determine whether the hostname is correct.

S6BRA023ECannot open socket for communicationsidentifier %


Explanation: Open of socket failed.

Action: Look at the previous message for moreinformation.


| 389

S6BRA024ECannot resolve communications identifier "%"


Explanation: Communications identifier couldnot be found in the directory section of yourRELAY parameter file.

Action: Assure the communications identifierhas been entered correctly in your RELAYparameter file.

S6BRA025EFailed to put socket into nonblocking mode;FCNTL socket requestfailed with errno=#


Explanation: Call to FCNTL failed whenattempting to put a socket into non-blockingmode. The new connection wasautomatically closed.


S6BRA026EAccept of new inbound socket connectionfailed; GIVESOCKET failed with errno=%


Explanation: New inbound connection wasrejected because of a GIVESOCKET error.


S6BRA027EACCEPT of new connection failed witherrno=%


Explanation: New inbound socket connectionwas rejected. ACCEPT socket API call failed.


S6BRA028ECannot open new connection; maximumnumber of open sockets exceeded


Explanation: New socket connection was rejectbecause the limit of open socket connectionswas exceeded.

Action: The number of socket connections islimited by TCP/IP configuration parametersin your RELAY configuration file. Dependingon you circumstance either increase thenumber of sockets for each TCP/IP RELAYtask by the maxtcbsockets parameter orincrease the number of TCP/IP tasks byusing the tcbnum parameter.

S6BRA029EBad command code sent to TCP/IP RELAYselect task


Explanation: The TCP/IP RELAY select taskreceived a bad command code. The requestwas ignored and normal operation wascontinued.



390 |

S6BRA030EBad work list returned by HCS received exit


Explanation: The TCP/IP RELAY detected a badqueue of work from its CommunicationsServices SEND/RECEIVE exit. Some TCP/IPconnections have been left in anindeterminate state but the relay iscontinuing processing.


S6BRA031ESocket state error on socket SEND; connectionclosed


Explanation: Object Service Broker expected thatdata is to be received from the TCP/IPConnection but Object Service Broker isattempting to SEND data to the connection.The connection was automatically closed.

Action: If this message is received as part ofCANCELUSER/LOGOFF processing itshould be ignored. Otherwise if it cannot bedetermined why Object Service Broker isattempting to SEND data to a connectionwhose next expected communication is toRECEIVE data then Contact TIBCO Support.

S6BRA032ESocket SEND failed with errno=%; connectionclosed


Explanation: A socket error was detected whendata was sent to the TCP/IP client.

Action: Refer to the return code appendix of theIBM IP Sockets and ApplicationProgramming Guide and Reference todetermine the meaning of the errno and theaction to be take.

S6BRA033ERELAY disconnect request failed with R15=%


Explanation: Cross-Memory control errordetected when a TCP/IP connection wasclosed.

Action: Contact TIBCO Support if this errorpersists.

S6BRA035EOpening of a socket failed with errno=%


Explanation: SOCKET socket request failed andnew out-bound connection failed to open.



| 391

S6BRA036ESETSOCKOPT call failed with errno=%


Explanation: Setting of socket options failed.


S6BRA037EGETADDRINFO for host "%" failed witherrno=%


Explanation: Resolution of host name to an IPaddress failed.


S6BRA038ETCP/IP image "%" not defined to MVS system


Explanation: The TCP/IP protocol stack namedefined by the tcpname parameter in yourRELAY parameter file is not defined on yourMVS system. TCP/IP support has beendisabled.

Action: Assure the name entered is defined onyour MVS system.

S6BRA039ETCP/IP image "%" is not active


Explanation: The TCP/IP protocol stack namedefined by the tcpname parameter in yourRELAY parameter file is disabled. TCP/IPsupport has been disabled.

Action: Verify that the correct name wasspecified in the RELAY parameter file. If sothen contact your TCP/IP systemadministrator to enable the image.

S6BRA040EConnection to TCP/IP interface failed witherrno=%


Explanation: The TCP/IP relay failed to initializeits connection to the MVS system TCP/IPimage. TCP/IP support has been disabled.


S6BRA041ESocket SELECTEX failed with errno=#; theTCP/IP RELAY is terminating


Explanation: SELECTEX socket called failed.TCP/IP support was terminated for thecomponent.



392 |

S6BRA042ETAKESOCKET failed with errno=%; socketconnection request rejected


Explanation: In-bound socket connection wasrejected because TAKESOCKET socket callfailed.


S6BRA043ESocket message contains an incorrect length;connection closed


Explanation: Bad message was received from asocket client. The message length did notmatch the length of data read. The socketconnection was closed.

Action: Assure that the client attempting aconnection was a Object Service Broker clientor component.

S6BRA044EBad host address in HOSTENT entry;connection closed


Explanation: When opening an new out-boundTCP/IP connection a bad HOSTENTstructure was detected from aGETHOSTBYNAME socket call. The newsocket connection was not opened.

Action: Contact TCBCO support.

S6BRA045EBad command code received by TCP/IP RELAYcontrol task


Explanation: The TCP/IP RELAY control taskreceived a bad internal message. The requestwas ignored and processing was continued.

Action: If this problem persists the contactTIBCO support.

S6BRA048EGETCLIENTID failed with errno=%


Explanation: GETCLIENTID TCP/IP system callfailed. The relay control task could not obtainthe socket identifier for a new connection.This identifier is required to pass the socketto a TCP/IP relay select task.

Action: Refer to the return code appendix of theIBM IP Sockets and ApplicationProgramming Guide and Reference todetermine the meaning of the error and theaction to be take.


| 393

RE: Communications RELAY

S6BRE001ICommand ; processed with return code #

Source: Communications RELAY

Explanation: An command has been receivedand processed via operator interface. If thereturn code is 0 the command has completedsuccessfully. If the return code is not 0 then aprevious error message will have been issueddescribing the problem.

Action: If the return code is 0 then this message isfor information only. If the return code is not0 then the action for the previous errormessage should be followed.

S6BRE002ERELAY parameters processing failed due to LEinitialization error - R15=;


Explanation: Initialization of theCommunications RELAY failed because of anLE failure. TCP/IP support has beendisabled.

Action: Refer to the IBM Language EnvironmentProgram Guide manual to determine themeaning of the return code from LEinitialization. For most errors an LE willproduce a formatted dump in the CEEDUMPDDNAME and will provide additional errorinformation in a dynamically allocated printfile.

S6BRE003ERELAY parameter error;; ;


Explanation: During RELAY initialization or aspart of a REFRESH command an error wasdetected in the active relay parameter file.

Action: Correct the error described by thismessage.

S6BRE004ERELAY invalid event code #


Explanation: An invalid event code has beenreceived by the RELAY CONTROL TASK.


S6BRE005ERELAY parameter file not allocated toDDNAME ; ;; Communication RELAY disabled.


Explanation: During RELAY initialization or aspart of a REFRESH command the RELAYparameter file could not be located.

Action: Correct the allocation of the RELAYparameter file.


394 |

S6BRE006ERELAY parameter file dynamic allocationerror;; errcode=# infocode=#


Explanation: Dynamic allocation of the RELAYparameter file at either initialization or as a aresult of an operator command.

Action: Look up the errcode and infocode valuesin the 'z/OS Authorized Assembler ServicesGuide' manual to determine the cause of thisproblem.

S6BRE007ECommand ";" not recognized


Explanation: An unsupported command hasbeen received via the operator interface.

Action: Correct the command and re-issue it.

S6BRE008ECommand ";" rejected: ;


Explanation: An operator command was rejectedfor the reason stated.

Action: Correct the operator command asrequired and re-issue it.

S6BRE009I;. The parameter dataset is ;.


Explanation: This message is issued as a result ofa CS,STATUS or after the successfulprocessing of a CS,PARMDSN= command.The relay status is displayed as eitherenabled or disabled. In addition the name ofthe current relay parameter dataset isdisplayed.


S6BRE010ERELAY parameter area storage obtain failedwith Return Code #


Explanation: At either initialization or after aCS,REFRESH storage was not available tohold the in store copy of the RELAYparameter file.

Action: Look up the return code in the 'z/OSAssembler Services Reference' under theSTORAGE macro. If the return code indicatesinsufficient storage is available increase thestorage available and retry. For any otherreturn code contact TIBCO support.

S6BRE011ERELAY OPENPORT failed with return code #.


Explanation: An internal CommunicationsSubsystem OPENPORT has failed.

Action: Contact TIBCO support


| 395

S6BRE012ERELAY ; failed for relay number # with returncode #.


Explanation: Either initialization or terminationof a Communications Subsystem relayprocessor failed.

Action: Contact TIBCO support

S6BRE875ICLEANUP FROM ABEND WILL TERMINATECONNECTION


Explanation: This message is issued by cleanupprocessing. It is issued during recovery froman intercepted abend that occurred duringrelay communications send/receiveprocessing. It indicates that the retryprocessing has reset the relaycommunications control indicators and willattempt to terminate the communicationsconnection that was active when the abendoccurred.

Action: Since this message indicates a successfulretry from an abend, no immediate actionmay be necessary. Consider the following:

• If the affected Object Service Brokercomponent (Data Object Broker, ExecutionEnvironment, Server, etc.) displays noother symptoms of difficulty, the error hassuccessfully been isolated to affect only asingle user connection.

• If this message is issued repeatedly, it mayindicate a severe problem with thecommunications capability of the affectedObject Service Broker component. Ifnormal production work is seriouslyaffected, it may be prudent to recycle thejob. In this case, collect any diagnosticinformation available (system log

printout, JES log for the affected ObjectService Broker address spaces, and anydumps produced) and contact TIBCOSupport.

S6BRE888ECommunications identifier "%" could not beloacted


Explanation: An attempt by the current ObjectService Broker communications environmentto contact another Object Service Brokerusing the Relay Object Service BrokerCommunications Implementation failedbecause the target Object Service Brokercommunications environment could not belocated via the relay processes. This may benormal, if the target Object Service Broker isnot normally accessible via a relay protocol.

Action: If the target Object Service Brokercommunications environment is required,ensure that it is executing and hassuccessfully initialized its Object ServiceBroker Relay communications environment.Ensure that the target Object Service Brokercommunications environment is definedcorrectly in the relay parameter file.


396 |

RT: EE Resources

S6BRT001IUSER UUUUUUUU DDDD, RESOURCERRRRRRRR AAAAAAAA, USED=00000MAX=00000.

Source: EE Resources

Explanation: This message is issued by theS6BDRTMR module. The user indicated inthe message has either acquired/released theresource named. USED is the use count forthe resource in this Object Service BrokerExecution Environment and MAX is themaximum allowed.


S6BRT002IRESOURCE THROTTLE BLOC FOR"12345678" DYNAMICALLY CREATED

Source: EE Resources

Explanation: This message is issued by theHRNDRRTH module. The internal ObjectService Broker Resource Throttle Blockindicated was dynamically created because itwas not predefined in the resource table. Thisshould not occur as all resources should bepredefined.



| 397

SB: Segment Balance Utility

S6BSB001EInvalid/Unknown Option

Source: Segment Balance Utility

Explanation: An unidentified option orparameter was encountered


S6BSB002ESegment # given is invalid


Explanation: The segment number specified isinvalid.


S6BSB003E# files missing or invalid


Explanation: The new segment will be made upof a number of files or data sets; this numbermust be specified (-f / F parameter).


S6BSB004ENumber of pages invalid


Explanation: The number of pages contained inthe old archive (-p / P parameter) is anoptional entry, but if entered it must be avalid numeric value.


S6BSB005EOld archive path/name required


Explanation: The full path and filename or theDDNAME (OLDARC) for the old archivemust be specified.


S6BSB006EOld archive cannot be opened


Explanation: This may be caused by problemswith the input device but most commonly iscaused by: a lack of read-authority or anincorrect file name (DSN). For Solaris, it maybe caused by the file size being over 2gigabytes.

Action: Check and correct. If you require theLarge File Support feature, contact TIBCOSupport.


398 |

S6BSB007ENew archive cannot be opened


Explanation: The new archive (-N / DDNAMENEWARC) cannot be opened.


S6BSB008WFile will be over 90% full


Explanation: This warning is issued if, afterbalancing, the new archive (single file or dataset segment) will be 90% or more full.


S6BSB010EInsufficient memory


Explanation: The utility could not acquiresufficient memory to complete the request.

Action: Check the audit report for total memoryrequired.

S6BSB011EI/O Error


Explanation: An I/O error was encountered onthe file or data set identified.

Action: Investigate, correct and retry.

S6BSB012EProgram Error


Explanation: The Segment Balance utility hasterminated prematurely due to a previouserror. An error message will have beenissued describing this error.

Action: If unable to determine the cause of thefailure from the error messages issued by theutility contact TIBCO support for assistance.

S6BSB013EUnexpected End of File


Explanation: An unexpected end of file wasencountered while reading the old archive.The most probable cause of this error is anincomplete archive.

Action: Make sure the archive is complete andtry again.

S6BSB014EUnable to reopen old archive


Explanation: The old archive is read twice. Onthe second pass the utility was unable toopen it.



| 399

S6BSB016WDuplicate Page


Explanation: The utility has encountered aduplicate page (two pages with the samepage number).

Action: This is a warning only. The samesituation will exist in the new archive afterbalancing. This is considered an error bybatch pointer check.

S6BSB017EControl page missing


Explanation: A control (bitmap) page is missingon the old archive.

Action: Balancing cannot be done while thiscondition exists. Run batch pointer check onthe old archive and correct all errors beforeattempting to balance the archive.

S6BSB018EIllegal sequence


Explanation: Pages are not in sequence on the oldarchive.

Action: Balancing cannot be done while thiscondition exists. Run pointer check on theold archive and correct all errors beforeattempting to balance the archive.

S6BSB019ESystem Pages missing


Explanation: All archives require Object ServiceBroker system pages to be present; on the oldarchive, system pages are incomplete.


S6BSB020EControl Page PREV/NEXT pointers invalid


Explanation: Control pages must be correctlyformatted in order to do balancing.


S6BSB021EControl Page invalid


Explanation: Control pages must be valid inorder to do balancing.


S6BSB022EPage List Area overflow (# archive pages error)


Explanation: The size of the PLA is dependent onthe # pages to be processed. This value can be

either a supplied value (-p / P parameter) orthe default; in either case the number ofpages was not a realistic estimate of thenumber of pages in the archive.

Action: Try again with a more realistic estimate.


400 |

S6BSB023ENo records found


Explanation: No records for this segment werefound in the old archive.

Action: Enter the correct segment # or the correctold archive.

S6BSB024WTagged Page Type


Explanation: A tagged page type wasencountered; this page will remain taggedafter balancing. This is a warning, but batchpointer check will also report the existence ofthis tagged page.


S6BSB025EInvalid Page Type


Explanation: An invalid page (type) was foundon the old archive.


S6BSB026EPage List overflow; -p option error


Explanation: The size of the PLA is dependent onthe # pages to be processed. This value can beeither a supplied value (-p / P parameter) orthe default, but in this case the number ofpages was not a realistic estimate of thenumber of pages in the archive.

Action: Try again with a more realistic estimate.

S6BSB027WFree Page system says in use


Explanation: A free page has been encounteredthat, according to the control page (bitmap),is in use. This condition will be carried overto the new archive.

Action: This is a warning; however, this segment-error condition will be reported by batchpointer check.

S6BSB028EInvalid Control page pointers


Explanation: Control Page pointers have beencorrupted.



| 401

S6BSB029EInvalid page size values


Explanation: This page has invalid headerinformation.


S6BSB030WSecondary Index flagged invalid


Explanation: The secondary index is invalidated.

Action: Warning only; no action required.

S6BSB032IFile 90% full warning given and was instructedto continue


Explanation: The Operator was warned of thiscondition and chose to continue.


S6BSB033IProcess cancelled by Operator


Explanation: Operator chose to discontinueprocessing.


S6BSB034EControl Page Number exceeds maximum


Explanation: The old archive's pages will not fiton the number of files or data sets specifiedfor the new archive.

Action: Investigate and redefine yourrequirements.

S6BSB040EInvalid INPUT RECFM must be VB or FB


Explanation: z/OS users only:

• If the old archive is a z/OS archive, or aWindows or Solaris archive reformattedby the S6BBRFRU utility, its RECFM mustbe VB.

• If the old archive is an unformattedWindows or Solaris archive, its RECFMcan be either VB or FB.


S6BSB041EInvalid OUTPUT RECFM must be VB


Explanation: z/OS users only: the RECFM of thenew archive must always be VB.


S6BSB042EIncorrect OUTPUT LRECL must be at least 4100


Explanation: z/OS users only: the new archiveLRECL is invalid.



402 |

S6BSB043EInput LRECL not acceptable must be at least 36


Explanation: z/OS users only: the old archiveLRECL is invalid.


S6BSB044ECould not CLOSE NEWARC


Explanation: z/OS users only: After finishing thebalance, it was not possible to close theoutput data set (NEWARC).

Action: Investigate the reason for the error andensure that the new archive is completebefore using it. If in doubt, rerun the job.


| 403

SI: SVC Install Program

S6BSI001IType 3 SVC number nnn install successful,Version: vvvvvvvv

Source: SVC Install Program

Explanation: Indicates the successful installationof the SVC routine. In the message:

• nnn is the SVC number installed

• vvvvvvvv is the version installed


S6BSI002ESVC number ??? invalid (Valid range: 200-255)


Explanation: An invalid SVC number wasdefined to the system at initialization.

Action: Define the SVC number statically usingPARMLIB member IEASVCxx and theLPALIB, or define the SVC numberdynamically using the program S6BSVCIN.

S6BSI003IType 3 SVC nnn replace successful, Old:oooooooooooooooo New: vvvvvvvvvvvvvvvv


Explanation: Indicates the SVC routine Replaceoperation was successful. In the message:

• nnn is the SVC number

• oooooooooooooooo is the old versionidentification

• vvvvvvvvvvvvvvvv is the new versionidentification


S6BSI004EInvalid function request: rrrrrrrr (Validrequests: ADD, DELETE or REPLACE)


Explanation: The function requested is invalid.In the message, rrrrrrrr is the input request.Valid requests are: ADD, DELETE, orREPLACE.

Action: Correct the function request andresubmit the JOB.

S6BSI005EGETMAIN from SQA for SVC routine failed


Explanation: S6BSVCIN was unable to obtainstorage from the SQA for the SVC routine.

Action: See the reason code supplied with theabend for the GETMAIN return code.

S6BSI006ELOAD failed for SVC routine rrrrrrrr


Explanation: S6BSVCIN was unable to LOADthe SVC. The reason code supplies the loaderreturn code via the abend.

Action: Check that the SVC is in STEPLIB.


404 |

S6BSI007EDirected LOAD failed for SVC routine


Explanation: S6BSVCIN was unable to load theSVC into SQA storage. The reason codesupplies the loader return code via theabend.

Action: Check that the SVC is in STEPLIB.

S6BSI008EGETMAIN for local work storage failed


Explanation: S6BSVCIN was unable to obtainlocal program work storage.

Action: See the reason code supplied by theGETMAIN return code via the abend.

S6BSI009ESVCUPDTE for SVC nnn failed


Explanation: S6BSVCIN was unable to define theSVC to the system. In the message, nnn is theSVC number in decimal.

Action: Check the return code provided via theabend reason code.

S6BSI010ES6BSVCIN module is not APF authorized


Explanation: Module S6BSVCIN is not APFauthorized.

Action: Insure that S6BSVCIN has been linkedauthorized and/or is executing from anauthorized library.

S6BSI011ESVC number nnn is in use, add failed


Explanation: The SVC number specified is notavailable to be used. The "add" functionrequest failed. In the message, nnn is the SVCnumber in decimal.

Action: Try another number or redefine theexisting one.

S6BSI012EType 3 SVC number ??? delete successful,Version: vvvvvvvvvvvvvvvv


Explanation: The SVC number currently definedhas been successfully removed. In themessage, vvvvvvvvvvvvvvvv is the versionidentification.


S6BSI013E"SVCUPDTE DELETE" for SVC nnn failed


Explanation: The SVCUPDTE DELETEoperation was unsuccessful. The "delete"function request failed.

Action: Check the return code provided via theabend reason code.


| 405

S6BSI014ESVC nnn delete failed, version mismatch.STEPLIB: pppppppp vvvv Current: ppppppppvvvv


Explanation: The SVC routine ID and the versionhave to match with the copy in the STEPLIBlibrary for the delete request to be honored.In the message:

• pppppppp is the SVC routine ID

• vvvv is the SVC routine version

Action: Confirm the SVC version that is installedis the same as that in the STEPLIB library. Ifdifferent, use the correct library or confirmthat the SVC number specified is indeed thecorrect Object Service Broker SVC to bedeleted. Correct the error and resubmit theJOB.

S6BSI015Emmmmmmmm not found in STEPLIB


Explanation: The default installation EECONFIGmodule could not be found in STEPLIB. Inthe message, mmmmmmmm is the modulename.

Action: Ensure that the named module is inSTEPLIB.

S6BSI016ESVC nnn in use is not TIBCO(r) Object ServiceBroker SVC routine, replace failed


Explanation: The current SVC nnn routine in useis not TIBCO(r) Object Service Broker SVCroutine, therefore the replace request isrejected.

Action: Take one of the following actions: 1)Correct the SVC number if it is incorrect. 2) Ifthe SVC number specified is correct, then usethe "delete" function to delete the SVCroutine first then use the "add" function toadd the new SVC routine.

S6BSI017EModule IGCERROR not in NUCLEUS MAP


Explanation: The IGCERROR module is not onthe z/OS nucleus map.

Action: Ensure that IBM module IGCERROR islinked into the z/OS nucleus map.

S6BSI019ESVC nnn is actively being used by an ExecutionEnvironment


Explanation: The SVC being added, replaced, ordeleted is currently in use by one or moreExecution Environments.

Action: Rerun this program once all ExecutionEnvironments using this SVC have beenquiesced.


406 |

SK: ODBC Gateway/Oracle Gateway

S6BSK001EDBSource % in the definition of % does notmatch the gateway's TRXDB %

Source: ODBC Gateway/Oracle Gateway

Explanation: Under Security Level=1, an attemptwas made to modify data via an SLKdefinition, referring to the data source, whichis different from the gateway's Fail Safetransaction database (TRXDB).

Action: Make sure the data source name in thedefinition matches the Fail Safe transactiondatabase (TRXDB) in the gateway sessionconfiguration.

S6BSK002EUnqualified delete request on the table %: %


Explanation: An attempt was made to delete arow of a table, while no current occurrencewas available and no WHERE clause wasspecified.

Action: The occurrence cannot be deleted unlessit has been read previously or specified bymeans of a WHERE clause in the deletestatement.

S6BSK003E% %: %


Explanation: Either the client interface (ODBC orOCI) or the target DBMS has issued an errormessage. Depending on the nature of theerror, this message may also refer to the tableand field (in parentheses), which were beingprocessed when the error occurred.

Action: Refer to the Error Messages in yourODBC documentation, the documentationprovided with your target DBMS, or yourOracle documentation.

S6BSK004EFailed to initialize the gateway's Fail SafeDBSource %


Explanation: At Fail Safe query time, thegateway failed to establish a connection tothe Fail Safe transaction database (TRXDB).

Action: Make sure the transaction database in thegateway session configuration (TRXDB,FSTABLENAME, RECOVERYID,RECOVERYPASSWORD) is properly set up.

S6BSK005EIllegal attempt to update the table %


Explanation: An attempt has been made tomodify data via an SLK definition, while thedefinition is either reserved or maps a non-

modifiable entity.

Action: Make sure no attempts are made tomodify data by means of this definition.


| 407

S6BSK006EThe DBSource % does not support %.


Explanation: The operation was rejected. In mostcases, a data modification request wassubmitted to a read-only external DBMSsession.

Action: Make sure your transaction mode(BROWSE, NOBROWSE) matches yourtarget DBMS's mode of operation.

S6BSK007EThe versions of the DB and binary componentsdo not match: % and % respectively


Explanation: The version of the Object ServiceBroker database objects does not match thatof the binary component (LIBHRNSQ.dll forODBC Gateway on Windows,LIBHRNOR.dll for Oracle Gateway onWindows, LIBHRNOR for Oracle Gatewayon Solaris).

Action: Make sure the releases of the ObjectService Broker software you are running areconsistent. Run the rule@COMP_INSTALLED to verify the releaseinformation associated with the databaseobjects.

S6BSK008E% %: % (connection failure)


Explanation: An error message has been issuedeither by the client interface (ODBC, OCI)you use or by the target DBMS. Theconnection was broken. If appropriate, themessage also refers to the table, which wasbeing processed when the error occurred.

Action: Refer to the Error Messages in yourODBC documentation, the documentationprovided with target DBMS, or your Oracledocumentation.

S6BSK012EAn error has occurred at connection time: %


Explanation: A connection attempt was rejected.

Action: Test your ODBC data source forconnectivity using any ODBC-complianttool, or test your Oracle connectivity usingOracle's tools. Note that this error may occurbecause of invalid security information usedby the gateway. Refer to the Object ServiceBroker ODBC/Oracle Gateway manual forinformation on security configuration.

S6BSK013EGET (as opposed to FORALL) request onreserved table %: %


Explanation: A GET request was issued againstan interpreted (reserved) table. The datasource name has been dynamically insertedin the definition. Only FORALL is allowedfor this table. The Object Service BrokerODBC/Oracle Gateway recognizes thefollowing reserved table names:


408 |

@SLKTABLES, @SLKCOLUMNS,@SLKQUALIFIERS, @SLKOWNERS,@SLKPROCEDURES,@SLKPROCCOLUMNS.

Action: Avoid accessing the above tables. If thiserror message occurs again, contact TIBCOSupport.

S6BSK014ECorrupted definition of reserved table % : %


Explanation: The table is an interpreted(reserved) SLK table. The data source namewas dynamically inserted in the definition.The definition was modified beyondusability.

Action: Make sure no corruption has occurred inyour database, as the definition is essential tothe gateway.

S6BSK015EInsert/update field list empty (table %) : %


Explanation: The process of building anUPDATE/INSERT SQL statement for thetable has resulted in an empty field list. Thiscan occur if your definition declares all of itsfields to be virtual.

Action: Make sure your definition correctlyreflects your view of the table it maps. If yes,INSERT/REPLACE is not allowed.

S6BSK018EInvalid update request on table %: %


Explanation: An invalid attempt was made tomodify data.

Action: Make sure this table is not modified bythe application.

S6BSK019EThe server lost track of cursor on the table %: %


Explanation: While performing a FORALL onthe table, the gateway has lost its cursorposition.

Action: This situation indicates possible memorycorruption. Contact TIBCO Support.

S6BSK021EUnable to create an additional statementcontext: %


Explanation: While accessing the table, thegateway failed to create an additionalstatement context.

Action: Reduce the number of tables accessedthat refer to the same data source within onetransaction; this data source has exhaustedthe maximum number of statement contextsthat the target DBMS allows to existsimultaneously.


| 409

S6BSK027EInvalid HANDLE field value in WHERE clause:stored proc result set %: %


Explanation: While processing a request to thestored procedure result set mapping, a valuefor @HANDLE@ was detected that points tono actual procedure execution context.

Action: Review your WHERE clause and makesure it the value for @HANDLE@= refers to ahandle returned by aCALL/EXECUTE/TRANSFERCALLstatement previously issued against a storedprocedure mapping.

S6BSK028E"R" or "O" parameter in WHERE clause: storedproc %: %


Explanation: While processing a request to thestored procedure mapping, references toreturn value and/or output parameters havebeen detected.

Action: Review your parameter list (or WHEREclause) and make sure it references input andinput/output parameters only.

S6BSK029EDBSource or TableName missing at runtime(table %): %


Explanation: The definition of the table containsempty DBSource and/or TableName serverparameters.

Action: Review your definition to make sureboth values are specified. If you use theDynamic Server Parameter facility, reviewyour code to make sure the definition iscomplete at data request time.

S6BSK030EInvalid WHERE clause (table %) : %


Explanation: While processing a request to thetable, an invalid WHERE clause wasdetected.

Action: Review your WHERE clause and makesure it is correct.

S6BSK031EInvalid field mapping or datacorrupted/truncated (field %, table %) : %


Explanation: While converting the field of thetable, a data conversion error occurred.

Action: Review your definition. Make sure theexternal and Object Service Broker syntaxesyou specified are compatible.


410 |

S6BSK032ENo HANDLE field reference in WHERE clause:stored proc result set %: %


Explanation: While processing a request to thestored procedure result set mapping, noreference to @HANDLE@ was detected.

Action: Review your WHERE clause and makesure it unambiguously specifies the value for@HANDLE@.

S6BSK034EDBSource not found (table %): %


Explanation: The ODBC data source thedefinition of the table refers to does not exist.

Action: Review your definition and make surethe data source name you specified is correct.If yes, run the ODBC Administrator andmake sure this data source exists and isproperly configured.

S6BSK036EIllegal attempt to execute a catalog function(table %): %


Explanation: An attempt has taken place toexecute, as a stored procedure, theinterpreted (reserved) table.

Action: Review your application and make sureyou are not attempting toCALL/EXECUTE/TRANSFERCALL one ofthe following: @SLKTABLES,@SLKCOLUMNS, @SLKQUALIFIERS,@SLKOWNERS, @SLKPROCEDURES,@SLKPROCCOLUMNS.

S6BSK037ETIBCO Service Gateway for ODBC has notbeen installed


Explanation: TIBCO Service Gateway for ODBCis a component of TIBCO Object ServiceBroker and has to be separately purchasedand installed.

Action: Obtain and install the Service Gatewayfor ODBC.

S6BSK038ETIBCO Service Gateway for Oracle has not beeninstalled


Explanation: TIBCO Service Gateway for Oracleis a component of TIBCO Object ServiceBroker and has to be separately purchasedand installed.

Action: Obtain and install the Service Gatewayfor Oracle.


| 411

SM: Session Manager

S6BSM001ESession Manager failed

Source: Session Manager

Explanation: The session startup rule or theworkbench failed.

Action: The message log is automatically printedif a startup rule or workbench fails. Browsethe log in the output of the job for moreinformation.

S6BSM002EFolding, printability tables cannot be loaded


Explanation: The specified CHARSET is invalidor is not supported. CHARSET is a sessionparameter.

Action: Verify the list of valid CHARSETs.

S6BSM003EInvalid Execution Mode


Explanation: You specified the EXECMODEExecution Environment parameter with avalue other than Y.

EXECMODE is obsolete and remains inObject Service Broker for legacy purposesonly.

Action: Remove EXECMODE or specifyEXECMODE=Y. In either case, you get strongtype checking in the Rule Editor withoutlogging of violations.

S6BSM005ELogon rejected - session limit reached


Explanation: This message is issued by theSESSMGR module. The logon request wasrejected by the Data Object Broker becausethe limit for the number of sessions set by theinstallation has been reached.

Action: Consult your System Administrator.

S6BSM006ELogon rejected - restricted to operators at thistime


Explanation: This message is issued by theSESSMGR module. The Data Object Broker isrestricting logons to operators only.


S6BSM007ELogon rejected - batch connections are not beingaccepted at this time


Explanation: This message is issued by theSESSMGR module. The Data Object Broker isnot accepting batch connections.



412 |

S6BSM008EVersion mismatch detected


Explanation: The release level of the ExecutionEnvironment software is not compatible withthe release level of the Data Object Broker.

Action: Verify that you are logging onto theintended Data Object Broker. If you are, thencontact your system administrator.

S6BSM009EUSERID already logged on


Explanation: You are attempting to log on with auserid that is already being used.

Action: Verify that the userid was correctlyentered and that you are logging on to theintended Data Object Broker. If these arecorrect, contact your system administrator.

S6BSM010ECommunication error during LOGONSENSE=X'9999' ID=XXXXXXXX


Explanation: A communication error occurredwhen the session attempted to connect to theData Object Broker. The Data Object Brokermay be quiesced.

Action: If the Data Object Broker is not quiesced,contact TIBCO Support.

S6BSM011ELogon rejected - userid missing


Explanation: You did not specify a userid.

Action: Review the entered HURN CICScommand, or your batch JCL sessionparameters, to ensure that a userid has beenspecified.

S6BSM012EUSERID exceeds 8 characters


Explanation: You specified an invalid userid. Thename contains more than 8 characters.

Action: Verify that you have entered a correctuserid when logging on.

S6BSM013EUSERID not added to Execution EnvironmentList


Explanation: During Execution Environmentlogon processing, HDRSBUSR could not adda new userid to the Execution Environment'slist of users.


S6BSM014EUSERID not removed from ExecutionEnvironment List


Explanation: During Execution Environmentlogoff processing, HDRSBUSR could notremove the session's userid from theExecution Environments's list of users.



| 413

S6BSM015ESession Scope Storage could not be initialized


Explanation: During logon processing, thestorage manager could not initialize a scopefor session storage.


S6BSM016ESession Scope Storage could not be released


Explanation: During logon processing, thestorage manager could not terminate thescope for session storage.


S6BSM017ELOGON terminated - terminal timeout cleanupin progress, try again later


Explanation: The current session was canceledbecause the user's terminal has been inactivefor too long.

Action: Press the <Enter> key and attempt to logon again. The maximum period of time aterminal may be left inactive is controlled bythe TIMEOUTLIMIT Execution Environmentparameter.

S6BSM018EUnable to Logon - unknown SENSE=X'9999'ID=XXXXXXXX


Explanation: You cannot connect to the DataObject Broker. For an explanation of theSENSE information, refer to messageS6BKC036.

Action: Refer to message S6BKC036.

S6BSM019ELOGON terminated at Security Logon


Explanation: You failed logon securityvalidation.

Action: Review any previous security messagesto determine the action to be taken.

S6BSM020EShared Rules Area Initialization failed


Explanation: The rule manager detected an errorduring initialization.

Action: The message log is automatically printedif a startup rule or workbench fails. Browsethe log in the output of the job for moreinformation.

S6BSM021ELogon SMF initialization failed


Explanation: The EVENT/SMF monitor detectedan error during session initialization.



414 |

S6BSM022EEXITSES1 exit failed


Explanation: The pre-session create user exitdetected an error.

Action: A session create exit for the ExecutionEnvironment Exit Facility has been definedby the installation. Review the exit definedby HRNXD to determine why the exitreturned a nonzero return code.

S6BSM023EScope Storage Modification failed


Explanation: Default storage limits andthresholds for a session could not bechanged.


S6BSM024ESession SMF initialization failed


Explanation: The EVENT/SMF monitor detectedan error during session recordinginitialization.


S6BSM025EEXITSES2 exit failed


Explanation: The pre-execution session user exitdetected an error.

Action: A pre-execution session exit for theExecution Environment Exit Facility hasbeen defined by the installation. Review theexit defined by HRNXD to determine whythe exit returned a nonzero return code.

S6BSM026ESecurity Logoff failed


Explanation: The security logoff process detectedan error.

Action: Review any previous messages fromsecurity logoff processing to determine theaction to be taken.

S6BSM027EEnvironment initialization error


Explanation: Initialization of the run timeenvironment failed.


S6BSM028ECAPTURE/REPLAY exit EXITSESR failed


Explanation: Insertion of the Capture/Replayfacility exit failed.



| 415

S6BSM029EStorage not available in Data Object Broker


Explanation: This message is issued by theSESSMGR module. The Data Object Broker isnot accepting any logons due to storageconstraints.

Action: Check the Data Object Broker for moremessages, and contact your systemadministrator.

S6BSM030EInternal parameter error SENSE=X'9999'ID=XXXXXXXX


Explanation: This message is issued by theSESSMGR module. An internal parametererror has been detected.


S6BSM031EMessage-out length error detected


Explanation: This message is issued by theSESSMGR module. A length error has beendetected during session end processing.Either the length is a negative number or itexceeded the maximum of 31 KB for amessage segment.

Action: Correct the error and retry or contactTIBCO Support.

S6BSM032ELogon rejected - system is in quiesce state


Explanation: The Data Object Broker is in aquiescent state and is not accepting anylogons at this time.

Action: Check with your System Administratorto find out when you should try again.

S6BSM033IExecution Environment shutdown in progress


Explanation: The Execution Environment isbeing shut down and is not accepting anylogons at this time.

Action: Check with your System Administratorto find out when you should try again.

S6BSM034IPath not defined to the Path ManagementSystem


Explanation: Execution Environment startupparameters SERVERTYPE= or SERVERID=may have been misspelled, omitted, or maynot be coordinated with the ResourceManagement System.

Action: Use the TSO ADMIN clist to access theResource Management System and verifythat path definitions are coordinated withExecution Environment startup parametersSERVERTYPE= ("TYPE" in PathManagement) and SERVERID= ("GROUPID" in Path Management).


416 |

S6BSM035IPath already at resource limit


Explanation: The CONNECTIONS MAX valuein the Path Management System definitionfor a specific path has been exceeded by thenumber of paths requested from theExecution Environment.

Action: Use the TSO ADMIN clist to access thePath Management System, and increase theCONNECTIONS MAX value for the path inquestion. Then reissue the request for pathsfrom the Execution Environment.

S6BSM036IServer limit in path exceeds max servers


Explanation: Possible logic error in PathManagement System.


S6BSM037ICharacteristics different than configured


Explanation: An external resource (DBMSgateway, Remote Rule Server or Peer System)connection has been rejected with a returncode of x'08' and a reason code of x'30'. Thismeans the flags identifying thecharacteristics of the resource do not matchthe requirements specified in the Path

Management system. A KC081 message onthe Data Object Broker console log identifiesthe resource characteristics that were failedat connection time.

Action: Review the KC081 message on the DataObject Broker console log, and coordinatesimilar parameters specified in ExecutionEnvironment, Data Object Broker and PathManagement (e.g., FSLEVEL).

S6BSM038IExpected associated connection not found


Explanation: A peer serverid defined on oneData Object Broker is not defined as expectedon another Data Object Broker.

Action: Use the TSO ADMIN CLIST to access thePath Management System on both DataObject Brokers, and examine and coordinatethe peer server definitions between them.

S6BSM039ISpecified associated user id is duplicated


Explanation: A peer serverid on one Data ObjectBroker is already defined for use on anotherData Object Broker.

Action: Use the TSO ADMIN clist to access thePath Management System on both DataObject Brokers, and examine and coordinatethe peer server definitions between them.


| 417

S6BSM040IServer path id not specified


Explanation: The Execution Environment has notspecified a supported serverid to the PathManagement System in the Data ObjectBroker.

Action: Use the TSO ADMIN clist to access thePath Management System, and verify thatthe paths are defined correctly. Check thatthe SERVERID= startup parameter in theExecution Environment has been specifiedcorrectly. If the message persists, contactTIBCO Support.

S6BSM041EDISPLAYCODEPAGE value not supported


Explanation: The session received aDISPLAYCODEPAGE value that is invalid orunsupported. This message is onlyapplicable in a z/OS environment.

Action: Correct the value of the sessionparameter DISPLAYCODEPAGE.

S6BSM042ENLS initialization failed


Explanation: The NLS initialization routine hasfailed. Either the NLS specification in table@NLS1 is invalid or the loading of therequired translation tables has failed.

Action: Check the log for previous errormessages issued during NLS initialization.Respecify correct values for the @NLS1 fieldsif they are invalid, and ensure the requiredtranslation table modules are available andon the search path.

S6BSM043ECODEPAGE FILE ERROR - TYPE n, RETURNCODE = xx


Explanation: An error has been detected readingthe value of the LOCALE_CP field in thetable @NLS1 for the SELF row. The error typen is as follows:

1. Execution Environment to Data ObjectBroker communication has failed

2. Transaction aborted by Data Object Broker

3. A GETFAIL has been generated by theread of @NLS1

4. A serious error has occurred

xx is the return code from the read.

Action: Take the action corresponding to thenumber of the error type:

1. Check the communications path betweenthe Execution Environment and the DataObject Broker.

2. Check the Data Object Broker for errormessages and take corrective action asnecessary.

3. Check the table definition and the contentsof table @NLS1 and correct as necessary.

4. Check the table definition and the contentsof table @NLS1 and correct as necessary.

S6BSM044ECommunication with the DOB failed, PeerServer terminated; ID=% Current user=%


Explanation: An attempt to communicate withthe Data Object Broker ended with an error.The most likely cause of the problem is thatthe connection between the ExecutionEnvironment and the Data Object Broker isbroken because the Data Object Broker


418 |

abnormally terminated. The ID in themessage text is the Peer Server that detectedthe problem and Current user is the usersession being served at the time of error.

Action: The peer server is terminated by theExecution Environment. If the Data ObjectBroker did indeed terminate abnormally,shutdown and restart the ExecutionEnvironment after the Data Object Brokerbecomes available again.

If it was a transient communication problem,you can restart the peer server using one ofthe following commands:

• For a native Execution Environment:

/F neejobname,STARTN=1,TYPE=API

• For a CICS Execution Environment:

/F cicsjobname,HSRV STARTN=1,TYPE=API

S6BSM045ETAMNLS.nlsinit ended with RC=%


Explanation: RC is the Return Code from theexecution of the TAMNLS.nlsinit module.


S6BSM046ELOAD failed for NLS translate table module %


Explanation: Attempt to load the indicated NLStranslate table module was unsuccessful.


S6BSM047ELogon rejected - CICS display limit reached


Explanation: The logon request was rejected bythe Data Object Broker because the limit forthe number of CICS display-style sessions setby the installation has been reached.

Action: Consult with your system administratorto review the setting of MAXDISPLAY.

S6BSM048ELogon rejected - CICS access is not licensed


Explanation: The logon request was rejected bythe Data Object Broker because it is notlicensed for access from CICS systems.

Action: Consult with your system administrator.

S6BSM099EPseudoregister length is too large


Explanation: The stack space reserved for theSAS/C modules is less than indicated in thepseudoregister. This is an Object ServiceBroker internal error.



| 419

S6BSM100EIncorrect password or userid


Explanation: You are not permitted to log onwith the userid and password combinationspecified.

Action: Verify that the userid and the passwordare correctly entered and that you arelogging on to the intended Data ObjectBroker. Otherwise, contact your securityadministrator for assistance.

S6BSM101ESevere screen I/O error


Explanation: The Execution Environmentdetected an error when prompting a user fora password.


S6BSM102EInvalid userid: %


Explanation: The userid specified is not definedto the Data Object Broker being accessed.

Action: Verify that the userid is correctly entered,and that you are logging on to the intendedData Object Broker. Otherwise, contact yoursecurity administrator for assistance.

S6BSM103ESecurity File definition error


Explanation: A communications error wasdetected during logon security validation.The type and return code reported giveinformation about the specificcommunications error. A hex dump of themessage buffer contents will also be written.

Action: In most situations, simply retry thelogon. If the problem persists, contact TIBCOSupport.

S6BSM104EUserid % cannot access system at this time


Explanation: The userid specified cannot log onduring the time period specified in the UserProfile.

Action: Contact your security administrator forassistance.

S6BSM105ECannot logon from ID: %


Explanation: The logon failed because the useridspecified must match the environmentidentifier. Your type of session determinesthe environment identifier.

Action: Verify that the userid is correctly enteredand that you are logging on to the intendedData Object Broker. If they both are correct,logon to TSO or CICS using the user ID asyour environment identifier. If you are usingbatch processing, specify the userid with theUSERID keyword on your jobcard.


420 |

S6BSM106ENo userid was specified


Explanation: No userid was specified whenlogging on. Either no prompting waspossible or the user did not enter a userid inresponse to the prompt.

Action: Specify a userid either as a TSO CLISTparameter or in response to the full-screenprompt.

S6BSM107EUserid % is suspended. Contact your securityadministrator


Explanation: The userid entered cannot logonbecause it has been suspended.

Action: Verify that the userid was correctlyentered and that you are logging on to theintended Data Object Broker. Otherwise,contact your security administrator forassistance.

S6BSM108ELogon of userid "%" cancelled


Explanation: Function key <PF3> or <PF12> waspressed when a user was being prompted fora password.

Action: Retry the logon sequence if desired.

S6BSM109EPassword provided was invalid and cannotprompt for password


Explanation: Either the password specified forthe userid was incorrect or else it was notspecified. Prompting for the correct value isnot possible either because you are runningfrom batch or from a seamless connection.

Action: Verify that the userid and password werecorrectly entered and that you are logging onto the intended Data Object Broker.Otherwise, contact your securityadministrator for assistance.

S6BSM110EInitialization failed (SMG)


Explanation: Session initialization failed.


S6BSM111ESession has abnormally terminated


Explanation: Session failed abnormally.


S6BSM113ESystem cannot be accessed from this terminal


Explanation: Due to RACF security restrictions,you cannot logon from this particularterminal.

Action: Logon from a terminal designated foruse, or talk to the System Administrator.


| 421

S6BSM114EAutomatic password upgrade failed for userid:%


Explanation: During LOGON processing, anautomatic password upgrade was attemptedfor this user due to a new encryptionalgorithm being present in the ExecutionEnvironment. The upgrade failed due tosome previous error in the processing.

Action: Refer to a previous error message for anexplanation and take appropriate action.

S6BSM116EDecryption exit call failed for userid: %


Explanation: The password description exitfailed.


S6BSM117EPassword provided has expired and cannotprompt for new password


Explanation: The password for the externalsystem has expired and the system needs toprompt for a new password but cannot do so.

Action: Logon to the external system via aterminal and set a new password for the userwhose password has expired. Alternatively,logon to Object Service Broker using theuser's Object Service Broker passwordinstead of the external system password.

S6BSM123EINTERNAL ERROR


Explanation: An internal error was detected.


S6BSM200ETIBCO(r) Object Service Broker REQUIRESMVS/XA FOR THIS VERSION


Explanation: You are trying to run this versionon a system other than MVS/XA or later.

Action: Refer to the Installation and Operationsfor z/OS manual for more information.

S6BSM201ETIBCO(r) Object Service Broker ALREADYACTIVE IN THIS ADDRESS SPACE


Explanation: You are attempting to start morethan one Execution Environment in the sameaddress space.

Action: Verify that neither a call to the TSOCMDSutility nor an external routine is attemptingto start an Execution Environment from atransaction. Otherwise, contact TIBCOSupport.


422 |

S6BSM202EInitialization failed (SMG)


Explanation: A GETMAIN failure occurredduring Data Object Broker initialization.SYSMVS was attempting to get x'2400' bytes(3 pages of 4 KB each) of memory below theline (i.e., 24-bit storage), and it failed.


S6BSM203EEXECUTION ENVIRONMENTINITIALIZATION FAILED


Explanation: Execution Environmentinitialization failed. The reason for the failureis posted in a preceding message.


S6BSM204EATTACH OF TIBCO(r) Object Service BrokerSERVER TASK FAILED, INITIALIZATIONTERMINATING


Explanation: Execution Environmentinitialization failed.


S6BSM301ESession initialization error, %


Explanation: An Execution Environment sessioncould not be started.

Action: If storage could not be allocated, use the"ps" and "sar" UNIX commands to determinethe reason. You may have started too manyprocesses or there may be an insufficientamount of swap space allocated for paging. Ifyou cannot determine the cause of the error,then make note of the complete message textand contact your system administrator.

S6BSM302E'%' is an unsupported character set


Explanation: The name displayed is not asupported National character set.

Action: The CHARSET Execution Environmentparameter determines the National characterset to be used. CHARSET may be set on thecommand line and in the session andinstallation defaults parameter files. Verifythat the character set specified is supported.Supported characters sets are documented inthe Processing manual.

S6BSM303ECould not open port for TDS(%) access


Explanation: The Execution Environment couldnot establish a connection to the Data ObjectBroker. The most common causes of thiserror are that no Data Object Broker has been


| 423

specified via the TDS ExecutionEnvironment parameter, or that the DataObject Broker that is specified is notavailable.

Action: See the session log for additionalinformation. Verify that a value has beenspecified for the TDS parameter, or that acorrect value is being used.

S6BSM304ESession limit reached for TDS(%)


Explanation: The Data Object Broker cannotservice any more users at this time.

Action: The maximum number of users that canlog on to a Data Object Broker is limited bythe MAXUSERS Data Object Brokerparameter. If you have started more than oneExecution Environment, then end anysessions that are not required. TheS6BTLADM utility can be used to determinewhat other sessions are active. If you stillcannot log on, contact the SystemAdministrator for the TDS you are trying touse.

S6BSM305ETDS(%) rejected logon attempt


Explanation: The Data Object Broker has rejectedyour logon attempt.

Action: The TDS Execution Environmentparameter determines which Data ObjectBroker you wish to use. Verify that thecorrect TDS name has been specified.Otherwise, contact the System Administratorfor the TDS being requested.

S6BSM306ECould not contact TDS(%)


Explanation: A communications error occurredwhen you attempted to log on to a DataObject Broker.

Action: The TDS Execution Environmentparameter determines which Data ObjectBroker you want to use. Verify that thecorrect TDS name is specified. Otherwise,review the session log for more informationand contact your system administrator.

S6BSM307Efork of the session process failed, errno=%d


Explanation: The Execution Environment couldnot complete initialization because a processcould not be created.

Action: Use "ps" to determine whether your userhas started too many processes. If so, end orkill any processes that are not required or areorphans. You may not be able to start aprocess because there are insufficientresources available on your machine. Use the"sar" command to determine whether youhave reached the system's resource limit.Verify that you have enough swap (pagespace) to start a new process. Otherwise,contact your system administrator.


424 |

S6BSM313ISystem logs


Explanation: This message is issued when atransaction fails. It signals the beginning of alist of error messages that describe why thetransaction failed. The list of messagesappear in reverse chronological order, themost recent message first.

Action: Study the Information Log.

S6BSM314IUser logs


Explanation: This message signals the beginningof the user's message log in the session logfile. The logs of the current transaction andits children appear in parent then child order.


S6BSM315IEnd of logs


Explanation: This message signals the end of thelogs in the session log file.


S6BSM401EUnsupported/unrecognized server type


Explanation: The external gateway typespecified by the SERVERTYPE ExecutionEnvironment parameter is not supported.

Action: The gateway type can be specified on thecommand line that invoked the ExecutionEnvironment or in the HRNIN parameterfile. Verify that the gateway type has beenspelled correctly and that the type ofgateway you wish to start is supported byyour version of the Data Object Broker.

S6BSM503EData Object Broker rejected server registration


Explanation: The Data Object Broker may not berunning.

Action: Make sure the Data Object Broker is up.

S6BSM507ELogon request for remote user was rejected


Explanation: Security validation failed.

Action: Check your password and defaultlibrary.

S6BSM510EUnknown error


Explanation: An internal problem has occurred.



| 425

S6BSM511IExternal gateway session XXX starting up


Explanation: External gateway session is startingnow.


S6BSM512IExternal gateway session XXX is shutting down


Explanation: External gateway session isshutting down now.


S6BSM513EInitialize of smGlobal_t failed


Explanation: A memory shortage has occurred.


S6BSM514EInitialization of session parameter failed




S6BSM515EInitialization of session log failed


Explanation: The session failed to create a log.

Action: Check client defaults.

S6BSM516EConnection to DOB failed


Explanation: The session failed to connect to theData Object Broker.

Action: Check your huron.dir file.

S6BSM517EDisconnection from DOB failed


Explanation: The session failed to disconnectfrom the Data Object Broker.

Action: See session log for more information

S6BSM519EInitialization of Euro-language support failed




S6BSM520EInitialization of Global Memory for CR rulebinding failed




S6BSM521ESession level initialization of the rules executorfailed


Explanation: Executor initialization failed.

Action: See the session log for more information.


426 |

S6BSM522EInitialization of the rules debugger failed


Explanation: The session failed to initialize therules debugger.


S6BSM523EGet of TASKPARMS information from theDOB failed


Explanation: The request for TASKPARAMSfailed.

Action: See Data Object Broker log for moreinformation.

S6BSM524ELogon security processing failed


Explanation: The logon procedure failed.

Action: Check your password and defaultlibrary.

S6BSM525EInitialization of screen colors failed


Explanation: A memory shortage occurred.


S6BSM526EInitialization of window colors failed


Explanation: A memory shortage occurred.


S6BSM527EInitialization of Hash tables for builtins andbound rules failed


Explanation: Hash tables initialization failed.


S6BSM528EShared binding areas for ExecutionEnvironment do not exist


Explanation: Session cannot access ExecutionEnvironment binding areas.

Action: See the Execution Environment log formore information.

S6BSM529ESession not authorized to use the sharedbinding areas


Explanation: An internal problem occurred.



| 427

S6BSM530ESession could not access the shared bindingareas


Explanation: An internal problem occurred.


S6BSM531EInvalid userid or password


Explanation: You entered an invalid userid orpassword.

Action: Verify that the userid and password werecorrectly entered and that you are logging onto the intended Data Object Broker.Otherwise, contact your securityadministrator for assistance.

S6BSM999ETDS(%) termination received


Explanation: The Data Object Broker to whichthe osee is connected has sent the osee atermination signal.



428 |

SP: External Gateways

S6BSP001EServer failed to store table definition: "%"

Source: External Gateways

Explanation: The gateway for external datafailed to store the Object Service Broker tabledefinition. The main reason for this is that thetable storage pool size (POOLSIZE) is notlarge enough.

Action: Restart the gateway with a largerPOOLSIZE parameter value.

S6BSP003EUnsupported request: "%"


Explanation: The gateway for external datareceived a request that it cannot process. Thisis a symptom of a version mismatch.

Action: Ensure Object Service Broker andgateway release levels are compatible. If thisdoes not resolve the problem then contactTIBCO Support.

S6BSP004EFail Safe level 1 table "%" has no serverparameters


Explanation: The Object Service Broker table thatmaps the external Fail Safe level-1transaction database is not defined correctly.

Action: Correct the table definition.

S6BSP005EFailed to load program "%" from library "%"


Explanation: The interface routine between theexternal gateway and the external datagateway could not be loaded or is not valid.If you receive this message outside thecontext of an Object Service Broker externalDBMS gateway, the attempt to load thespecified program from the specified libraryfailed for the reason indicated in theextension to this message. If the library valueis NULL, the search on z/OS was done usingthe steplib searchpath.

On Windows and Solaris, a valid libraryfrom which programs/functions can bedynamically loaded must be specified.

Action: Specify a valid value for theEXTERNALROUTINE configurationparameter. Specify valid values for bothprogram and library:

• On z/OS, valid values for library are SMG(steplib) or EXL (Object Service Brokerexternal routines library).

• On Solaris, the library must be a valid .sofile accessible at run time.

• On Windows, the library must be a valid.dll or .exe file. The library value can bespecified as either an absolute path orsimply as a file name.


| 429

S6BSP006EInvalid Fail Safe transaction database tablename: "%"


Explanation: The indicated table name is not avalid Object Service Broker table name.

Action: Specify a valid Object Service Brokertable name for the external Fail Safe level-1transaction database (FSTABLENAME).

S6BSP007EServer table definition storage pool,initialization failed


Explanation: The gateway for external datafailed to acquire and/or initialize the tabledefinition storage pool specified on thePOOLSIZE parameter.

Action: Reduce the POOLSIZE value or increaseavailable memory.

S6BSP008IServer session ended


Explanation: The gateway for external data hasended.


S6BSP009EServer failed to connect to Data Object Broker:"%"


Explanation: The gateway session failed toconnect to specified Data Object Broker.

Action: Check previous messages and DataObject Broker log for more information. Fixthe problem and try again.

S6BSP010EFail Safe table "%" is missing field "%"


Explanation: The Fail Safe table definition is notvalid

Action: Check to make sure that the definition iscorrect.

S6BSP011EServer failed to build "%" occurrence


Explanation: While attempting to build theObject Service Broker occurrence from theexternal occurrence or vice versa, an errorwas encountered. The extension to thismessage gives more detail.

Action: Correct the table definition or the data.


430 |

S6BSP012EServer session initialization failed


Explanation: The initialization of the ObjectService Broker gateway for external datafailed. Previous messages give moreinformation.

Action: Correct the initialization error and restartthe gateway.

S6BSP014EServer did not receive an occurrence to "%"


Explanation: The gateway for external data didnot receive an occurrence toINSERT/REPLACE. This is a symptom of aversion mismatch.


S6BSP015EServer did not receive the session securityinformation


Explanation: The gateway for external data didreceive the Object Service Broker sessionsecurity information. This is a symptom of aversion mismatch.


S6BSP016ECurrent group "%" is not a valid external userid


Explanation: The Object Service Broker currentgroup is either null or more that 8 characterslong.

Action: Specify a valid current group value thatwill be accepted as a valid external user ID.

S6BSP017EMemory in the amount of "%" could not beacquired


Explanation: The memory requested throughroutine @MEMORYINSTANCES could notbe acquired.

Action: Request less memory or increaseavailable memory. If necessary, contactTIBCO Support.

S6BSP018EServer configuration parameter "%" required orinvalid


Explanation: The gateway for external datacannot initialize without a valid value for thespecified gateway configuration parameter.

Action: Specify a valid value for theconfiguration parameter.


| 431

S6BSP019EServer does not support Fail Safe level "%"


Explanation: The requested Fail Safe level cannotbe supported by the gateway.

Action: Specify a valid value for the FSLEVELgateway parameter and restart the gateway.

S6BSP020EServer session failed


Explanation: The gateway for external datafailed. Previous messages give moreinformation.

Action: Correct the error and restart the gateway.

S6BSP021EServer did not receive a required serverparameter "%"


Explanation: The Object Service Broker requestsent to the gateway did not contain therequired gateway parameter. This parameteris part of the table definition.

Action: Correct the table definition to include therequired parameter with a valid value.

S6BSP022EA server cursor was not found to process therequest for "%"


Explanation: The gateway for external datafailed to acquire a cursor to process therequest. This is a symptom of a versionmismatch.


S6BSP023EField of "%" bytes exceeds the maximumallowed length


Explanation: The field length exceeds the ObjectService Broker gateway for external datamaximum.

Action: Modify table definition to use a shorterfield length.

S6BSP024ENo servers like server type *%* exist


Explanation: No entries in table@SERVERIDCONFIG exist for the specifiedgateway type.

Action: Execute rule @CONFIGURESERVERwith a null parameter and ADD an entry forthe desired gateway type and ID.


432 |

S6BSP025EValue at cursor position is not one of theallowed values


Explanation: The value entered is not one of theallowed values for this parameter.

Action: Enter a valid value.

S6BSP026EValue "%" is incompatible with type "%" syntax"%" length "%" decimal"%" of "%"


Explanation: The value entered does not matchthe attributes of this parameter.

Action: Enter a valid value.

S6BSP027EInvalid command


Explanation: The command entered is not valid.

Action: Enter a valid command.

S6BSP028EInvalid server type: "%"


Explanation: The gateway type entered is not avalid gateway type that this utility supports.

Action: If the utility is @CONFIGURESERVERthen an entry for this gateway type was notfound in @SERVERCONFIG.

S6BSP029EServer type "%" has no modifiableconfiguration parameters


Explanation: All entries in @SERVERCONFIGfor this gateway type are marked as notmodifiable.

Action: This gateway type does not have anyparameters that can be configured throughthis utility.

S6BSP032EServer could not find "%" entry point


Explanation: The gateway failed to find the entrypoint to the mentioned function.


S6BSP100E% connection failed, reason="%"


Explanation: The gateway failed to connect tothe Data Object Broker. The followinginformation is given:

• % - SERVER USERID - IDPREFIX+ext

• reason (rr/ee) -- refer to the explanationfor message S6BKC036 for theinterpretation of the reason code

Action: Contact TIBCO Support if you needfurther clarification.


| 433

S6BSP101I% Server shutdown requested, reason="%"


Explanation: The gateway received a request toshut down from the Data Object Broker. Thedescription of the reason codes follows:

• 0000 - Object Service Broker is shuttingdown.



• 0010 - The Object Service Broker resourcedirectory is full. Contact TIBCO Support.

• 0014 - The maximum number of gatewayshas been exceeded. Increase theMAXDBMS parameter in the Data ObjectBroker and restart, or contact TIBCOSupport.

• 00018 - The Object Service Broker gatewayanchor list has overflowed. Contact TIBCOSupport.


S6BSP102E%


Explanation: The gateway failed to connect tothe Data Object Broker. The text of themessage describes the reason and contains asubsequent message ID that can be lookedup for more information.

Action: Take appropriate action based on thesubsequent message ID.


434 |

SS: UNIX System Services

S6BSS001ECall to UNIX services module BPX1SDD failed.Return code xxxxxxxx Reason code xxxxxxxx

Source: UNIX System Services

Explanation: A call to BPX1SDD, the Set DubDefault Service routine, failed. The errorReturn code and Reason code are displayedin hex value.

Action: Refer to IBM "z/OS UNIX SystemServices Messages and Codes" - SA22-7807.


| 435

ST: Storage Management

S6BST001ESTORAGE MANAGER ERROR

Source: Storage Management

Explanation: The Object Service BrokerExecution Environment storage managerdetected a severe error that does not permitthe continuation of execution.

Action: Contact TIBCO Support and provide thefull text of the message.

S6BST002EINSUFFICIENT MEMORY IN PRIVATE AREATO SATISFY STORAGE REQUEST


Explanation: Execution Environment servicesrequire more storage than there is availablein the Execution Environment address space.

Action: The amount of storage available to ObjectService Broker is controlled by the REGIONJCL parameter of the job step where theExecution Environment is executing. Thetype of the Execution Environment (e.g. TSO,BATCH, or CICS) affects how a limit may bespecified. The storage limit for an addressspace can be exceeded by a user requiring toomuch storage or by trying to run too manyusers in the same Execution Environment.Consider the following suggestions todetermine your situation: For single-userExecution Environments like TSO andBATCH, increasing the REGION parameterfor the Object Service Broker ExecutionEnvironment will increase the amount ofstorage available. Very large session or

temporary tables will have a large storagerequirement. Review the application; if itdoes have large session or temporary tables,you will either have to increase the storageavailable or modify the application in someway so that it fits into the storage available.Verify that the MAXIMUM parameter setting(the amount of storage available to a user) iscompatible with the REGION parameter, andthat in a multiple-session ExecutionEnvironment like the CICS ExecutionEnvironment the setting of this parameter issuch that there is enough storage for allconcurrent users. When designingapplications that will require a large numberof concurrent users in the same ExecutionEnvironment, storage utilization isminimized if pseudo-conversational codingtechniques are used (DISPLAY &TRANSFERCALL). Review your SMF data ata transaction level to determine your storagerequirements. This should be done regularlyto monitor the effectiveness of currentparameter settings and to detect changes insystem utilization that might require newallocations of resources.

S6BST003ESTORAGE LIMIT EXCEEDED FOR ASTORAGE POOL


Explanation: Execution Environment servicesrequire more storage than ExecutionEnvironment or user limits permit.

Action: Please refer to the suggestions listed withmessage S6BST001E.


436 |

S6BST004ESTORAGE LIMIT EXCEEDED FOR ASTORAGE TYPE


Explanation: Execution Environment servicesrequire more storage than ExecutionEnvironment or user limits permit.

Action: Please refer to the suggestions listed withmessage S6BST002E.

S6BST092EINVALID CELL STORAGE ADDRESSDETECTED


Explanation: During GET or FREE processing,the Storage Manager detected that thestorage cell does not reside within theallocated block. This message isaccompanied by abend U878.

Action: This represents a severe internal errorcondition. Save the accompanying dump andcontact TIBCO Support.

S6BST300I- EXTENDED STORAGE LIMIT FOR REGIONINCREASED TO XXXXXXXK


Explanation: The job limit for 31-bit addressstorage was successfully extended to theamount displayed in the message. TheCICSREGIONLIMIT Execution Environmentparameter allows the extension of the z/OSstorage limit for CICS ExecutionEnvironments.


S6BST301ISTORAGE AVAILABLE AT STARTUP ISXXXXXK OF 24 BIT AND XXXXXXXK OF 31BIT


Explanation: This message is displayed by CICSExecution Environments. The messagedisplays the amount of 24-bit and 31-bitaddressing storage available for the ObjectService Broker Execution Environment.


S6BST302I- EXTENDED STORAGE LIMIT FOR REGIONNOT MODIFIED


Explanation: The CICSREGIONLIMIT ExecutionEnvironment parameter was specified butthe job limit for 31-bit address storage couldnot be changed. The CICSREGIONLIMITparameter may only be specified for CICSExecution Environments that executeauthorized or are invoked using the ObjectService Broker SVC. Note that this messagewill also be displayed if the current limit for31-bit addressing storage is greater than thevalue specified for the region limitparameter.

Action: This is an information message andObject Service Broker ExecutionEnvironment initialization will continue. If alarger region is required, run the ObjectService Broker Execution Environmentauthorized and then use theCICSREGIONLIMIT parameter. For moreinformation about authorization, refer to theInstallation and Operations manual.


| 437

SV: Batch Server

S6BSV901ECNTL File: Invalid numeric value

Source: Batch Server

Explanation: Definition Control File Error: Onthe S entry of the file, there are variouscontrol fields that must be either completelyblank or contain a numeric value. Theseinclude all fields on the "S"pecification entry.

Action: Check the file and correct any incorrectentries.

S6BSV902ECNTL File: - no entries found


Explanation: Definition Control File Error: Theutility requested requires a DefinitionControl File and an S type entry must be thefirst entry in the file. No S type entry wasfound in the Control file indicated.

Action: Check that the file name entered on thecommand line is correct. If the file isdamaged, use the online toolBATCHLOAD_CARDS to recreate the file.

S6BSV903ECNTL File: 'S' type must be first entry


Explanation: Definition Control File Error: Theutility requested requires a DefinitionControl File and the S type entry must be thefirst entry in the file. No S type entry wasfound in the Control file indicated.

Action: Check that the file name entered on thecommand line is correct. If the file isdamaged, use the online toolBATCHLOAD_CARDS to recreate the file.

S6BSV904ECNTL File: 'I' sequence # error


Explanation: Definition Control File Error: TheInput (I) entries in the Definition Control filemust be in sequence and the sequencenumber itself must be numeric.

Action: Check the sequence numbers in theDefinition Control File and either place themin sequence or correct the sequence numbers.

S6BSV905WNull-Equivalent value is ignored


Explanation: A NULL-EQUIVALENT value hasbeen specified for a syntax/field for which itis not accepted.



438 |

S6BSV906ENull-Equivalent value is invalid


Explanation: A NULL-EQUIVALENT valuespecified on the control file is invalid.

Action: Check the documentation if necessary,correct and retry.

S6BSV907ECNTL File: field length invalid


Explanation: Definition Control File Error: Thefield lengths entered in the DefinitionControl File must be numeric.

Action: Correct the field length for the fieldindicated.

S6BSV908ECNTL File: # of decimals error


Explanation: Definition Control File Error: The #of decimals entered in the Definition ControlFile must be either completely blank or avalid number.

Action: Correct the # of decimals for the fieldindicated. NOTE: For certain semantic-type/syntax combinations no decimals arepermitted.

S6BSV909ECNTL File: field offset error


Explanation: Definition Control File Error: Theoffset field must be either completely blankor numeric. The offset (based on 0 as the firstposition in the input file) is the physical startof the field within the input file.

Action: Check the offset; it may not be required ifthe field immediately before it in the inputfile is defined.

S6BSV911ECNTL File: 'H' sequence error


Explanation: Definition Control File Error: TheTable (H) entries in the Definition Control filemust be in numeric sequence.

Action: Check the sequence numbers in theDefinition Control File and either place themin sequence or correct the sequence numbers.

S6BSV912ECNTL File: unknown 'H' subtype


Explanation: Definition Control File Error: Thissub-type is incorrect for a type H entry.

Action: Check the manual for acceptable typesand correct the entry or use the requisiteonline Batch tool (BATCHLOAD_CARDS,etc.) to generate a correct definition file.


| 439

S6BSV913ECNTL File: 'H' internal field name blank


Explanation: Definition Control File Error: TypeH definition statement field names cannot beblank.

Action: Correct the statement in error.

S6BSV915ECNTL File: invalid key type


Explanation: Definition Control File Error: Thekey type entered is incorrect.

Action: Check the manual for acceptable keytypes and correct the definition for the fieldindicated.

S6BSV916ECNTL File: invalid # parms


Explanation: Definition Control File Error: TypeH sub-type T columns 50 through 52 areinvalid. This field should show the numberof parameters in the table to be unloaded.

Action: Correct the entry.

S6BSV917ECNTL File: invalid # fields


Explanation: Definition Control File Error: TypeH sub-type T columns 54 through 57 areinvalid. This field should show the numberof fields in the table to be unloaded.


S6BSV918ECNTL File: bad sequence, static value


Explanation: Definition Control File Error:

Static value (type V) entries (column 20)must be in sequence. Single entry values(less than 50 characters) sequence number =blank, 0 or 1. If the static value is greater than50 characters, it appears on more than onedefinition statement. These statements mustbe in the correct sequence.

Action: Correct the static value sequencenumbers or generate a valid file using theonline tool BATCHLOAD_CARDS.

S6BSV919ECNTL File: no match for static value field


Explanation: Definition Control File Error: Thetarget field name that is to receive the staticvalue must exist in the table definition (Hentries).

Action: Either remove the static value if it issuperfluous or insert the correct target fieldname.

S6BSV920ECNTL File: collision - field and static value


Explanation: Definition Control File Error: Astatic value is loaded into every instance ofthe field to which it is targeted. Its target fieldcannot also receive input from an input filefield. Both values cannot be placed in thetarget field.

Action: Correct the table definitions so that onlyone value is provided to each table field.


440 |

S6BSV922ECNTL File: Static value max length exceeded


Explanation: Definition Control File Error: Thisstatic value exceeds the maximum lengthpermitted.

Action: Consider splitting the field to be filled bythe static value, then entering a static valuefor each of the subfields.

S6BSV923ECNTL File: no fields defined


Explanation: Definition Control File Error.

Action: Generate a valid Definition Control Fileby using the online tool(BATCHLOAD_CARDS;BATCHUNLD_CARDS;SIXBUILD_CARDS).

S6BSV924ECNTL File: invalid syntax



Action: Check the manual for acceptable entriesand correct the definition for the field nameindicated.

S6BSV925ECNTL File: invalid semantic type



Action: Check the manual for acceptable entriesand correct the definition for the field nameindicated.

S6BSV926ECNTL File: 'I' to 'H' field incompatibility


Explanation: Definition Control File Error: Thereare semantic-type/syntaxes which cannot beconverted to other selected semantic-type/syntaxes, (for example packed decimalcannot be converted to Logical/Character).

Action: Check the definition for the fieldsindicated (length to length; syntax to syntax).

S6BSV927ECNTL File: Value to 'H' field incompatibility


Explanation: Definition Control File Error: Staticvalues are always considered to be NO-semantic-type/syntax Character (C or V). Ifthe target field's semantic-type/syntax is notcompatible with this combination, this errorwill occur.

Action: Check and correct the target (table) field'ssemantic-type/syntax.


| 441

S6BSV928ECNTL File: Offset overlaps previous fields


Explanation: Definition Control File Error: Fieldsmust be defined once only and cannot beredefined (no part of a field can occur inanother field). Offsets are expected to be inrelation to zero (the first character in a file isconsidered at offset 0). The offset specifiedoverlaps a previously defined field.

Action: Check the definition for the fieldindicated in relation to the field before it. Iftwo adjacent fields are defined it is notnecessary to include an offset for the secondas the first field will establish the second'sposition in the file.

S6BSV929ECNTL File is required (-C option)


Explanation: The identity of the DefinitionControl File is missing from the commandline (-C).

Action: Try again, ensuring that the -C option isspecified on the command line.

S6BSV934EInvalid Segment requested


Explanation: The segment identifier provided inthe -s option on the command line is invalid.


S6BSV935EParameter field length exceeds maximum



Action: Check the manual for the maximumlength permitted and correct the entryindicated.

S6BSV936ETotal Parameter length exceeds maximum


Explanation: Definition Control File Error: Thereis a maximum total length for all parameterscombined; this limit has been exceeded.

Action: Check the manual for the maximum totalparameter length.

S6BSV937EIllegal Parameter syntax


Explanation: Definition Control File Error: Notall syntaxes are acceptable as parameters.

Action: Check the manual for acceptableparameter syntaxes.

S6BSV938EMaximum # of Parameters exceeded


Explanation: Definition Control File Error: Thereis a limit on the number of parameters whichcan be defined for a table; this limit has beenexceeded.



442 |

S6BSV939EPrimary/Secondary key field length exceedsmaximum


Explanation: Definition Control File Error: Thereis a limit on the length of each individual keyfield.


S6BSV940ETotal Primary key length exceeds maximum


Explanation: Definition Control File Error: Thereis a limit to the total length of all primary keyfields combined.


S6BSV941EIllegal Primary key syntax


Explanation: Definition Control File Error: Allsyntaxes are not eligible to be used asprimary keys.

Action: Check the definition of the field indicatedand correct it.

S6BSV942EMaximum # Primary key fields exceeded


Explanation: There is a limit to the number ofprimary keys which can be defined in asingle table.


S6BSV943EFirst Primary key cannot serve as Secondary


Explanation: Definition Control File Error: Thefirst or PRIMARY primary-key may not alsobe defined as a secondary key.


S6BSV944EIDGEN Primary key definition error


Explanation: Definition Control File Error: Whena table is defined as IDgen, its primary keymust be defined as binary (B) syntax with alength of 4.


S6BSV946EMaximum # Secondary key fields exceeded


Explanation: Definition Control File Error: Thereis a limit to the number of secondary keyfields which may be defined in a single table.


S6BSV947EUnknown key type


Explanation: Definition Control File Error: Aninvalid entry has been made in the key-typefield of the identified field's definitionstatement.



| 443

S6BSV948EIDGEN permits 1 Primary Key only


Explanation: Definition Control File Error: AnIDgen keyed table is allowed only oneprimary key field.


S6BSV949EHCS processing failed


Explanation: This utility requires the -t option onthe command line.

Action: Try again, indicate the ID of the ObjectService Broker node using the -t commandline option.

S6BSV950EUnable to open Segment requested


Explanation: The segment requested must bedisconnected (offline) from online processingin order for this utility to function correctly.

Action: Request that the segment be placedoffline.

S6BSV951EUnable to close the Segment


Explanation: The utility was unable to close thesegment on which it was working.

Action: If the utility in use modifies the Pagestore(LOAD/SIXBUILD/S6BBRPGC (Pagestorecorrection)) the Pagestore must beconsidered potentially inconsistent.Investigate or report the error to support

staff. The cause of the error must beidentified and corrected before the failedactivity is tried again. Inspect the reportproduced by the utility, it may help indetermining the reason for the failure orshow that the primary-data-build wassuccessfully completed. If the LOAD-secondary-index-build failed, it is possible todelete the secondary index pages (online)and rebuild using the SIXBUILD only. If theutility in use was an UNLOAD, it cannothave impacted the Pagestore in any way.However before using the file which hasbeen created it should be checked forcompleteness.

S6BSV953EStatic Value content error


Explanation: Definition Control File Error:

• The target field specified is too small toreceive the value.

• The target field requires a numeric value,the value is not.

• The static value will create an invalid keyvalue (numeric null).

• Syntax C fields cannot contain lowercase.

Action: Correct the static value.

S6BSV954W**WARNING** - Possible Input File FormatError - **WARNING*


Explanation: There are three file formats. All arederived from z/OS sequential file types:

• FIXED - The equivalent of a z/OS FB dataset after FTP to Windows or Solaris. Thefile contains records all the same length (as


444 |

described in the Control (-C) File). Norecord lengths are contained in the file.

• VARIABLE NO BDW - The result when az/OS VB data set is FTPed to Windows orSolaris. This file contains a 4-byte RDW(length) in front of each record. Allpossible fields in the file must be definedusing BATCHLOAD_CARDS (-C ControlFile) and "Input Data File Length Format"must be set to "V". NOTE: Do not specifythe -m (Blocked Variable) option on thecommand line.

• VARIABLE BLOCKED - The first record ofeach block is preceded by a 4-byte BDW(block length) and a 4-byte RDW (recordlength). This is the file format used whenfiles are created using the Unload utilities(hrnbrulh, hrnbrulb, and hrnbrula) onWindows or Solaris. When usingBATCHLOAD_CARDS to describe thefile's format, you must define all possiblefields and set the "Input Data File LengthFormat" to "V". On the command line youmust specify the -m option.

Using BATCHLOAD_CARDS, the input fileis described using the "INPUT FILEDEFINITION SCREEN". All possible datafields in the file must be defined. Do notdefine the length fields if the file is Variable.If the input file was created usingS6BBRULA, then the entry "Was input dataunloaded from an archive" must be set to"Y". If the input file is either "VARIABLE NOBDW" or "VARIABLE BLOCKED" (seeabove), then the entry "Input Data FileLength Format" must be set to "V".

NOTE: This is a warning only; it is notpossible for the utility, by analyzing the file'sdata, to be absolutely certain that the file hasa format that differs from that specified in

the Control File (-C) and the Command Line(-m).

Action: Ensure that the input file is describedcorrectly both in the Control File (-C) and onthe command line (-m). If the requestedprocess completed successfully, check thatthe format was correctly specified beforeusing the output from the utility.

____________________________________________ If you are transferring Object ServiceBroker files between platforms, refer todocumentation for the S6BBRFRU/hrnbrfru(Reformat Object Service Broker FilesTransferred with FTP) utility.

S6BSV957EUnable to open the specified input file


Explanation: An Open input file request failed.This can be caused by problems with theinput device, but most commonly is causedby one of:

• A lack of authority to read the file

• [Solaris] The file exceeds the 2 gigabytefile-size limit

• The incorrect file name or path is specified

Action: Correct the problem and try again. If youneed the Large File Support feature, contactTIBCO Support.


| 445

S6BSV962ESELECT File: invalid include/exclude indicator


Explanation: Selection Criteria File Error: Eachselection entry requires an indicator (I or X)in column 17. It indicates inclusion (I) orexclusion (X) (for rows matching theselection criteria) in the unloaded table.

Action: Check and correct the entry.

S6BSV963ESELECT File: invalid relational operator


Explanation: Selection Criteria File Error: Therelational operator specified is invalid.

Action: Check the UNLOAD documentation foracceptable relational operators and correctthe select statement.

S6BSV964ESELECT File: relational operator not constant


Explanation: Selection Criteria File Error: Therelational operator chosen for the firstselection statement must be used on all otherselection statements.


S6BSV965ESELECT File: invalid numeric value


Explanation: Selection Criteria File Error: Theselection value stated refers to a numericfield and therefore should be numeric.


S6BSV966ENumeric Syntax secondaries cannot be NULL


Explanation: Definition Control File Error: Asecondary index field is defined with nocorresponding input field which means allfield instances in the table will be Null. Nullnumeric secondary values are not permitted.


S6BSV967EIllegal Secondary Key syntax


Explanation: Definition Control File Error: Allsyntaxes are not eligible to be used assecondary keys.

Action: Check the field indicated and correct it.

S6BSV968EStd Input not permitted with non-text input


Explanation: Text data as input is not currentlysupported.

Action: An input file name must be provided onthe command line.

S6BSV970EUnable to acquire a free page on this segment


Explanation: The segment in use is full.

Action: Inspect the utility report.

• LOAD -- If the primary-data-index iscomplete and the failure occurred duringthe secondary-index build:


446 |

1. Delete the secondary index using theonline tool.

2. Increase the storage available to thesegment.

3. Use the offline secondary indexbuilder to build the secondary index.

• LOAD or SIXBUILD

1. Clear the partially built table usingeither: for a failed LOAD, theCLEARTAB tool; for a failedSIXBUILD, the online toolSIXDELETE.

2. Increase the storage available to thesegment.

3. Rerun the failed utility.

• S6BBRPGC/hrnbrpgc (PagestoreCorrection) -- Increase the storageavailable to the segment and rerun thefailed utility.

S6BSV972EMaximum # Fields for a table - exceeded


Explanation: Definition Control File Error: Thenumber of fields specified (S type entrycolumns 31-33) exceeds the maximumnumber of fields which can be defined in atable.

Action: Check the entry; if it is correct, this tablecannot be loaded using this utility.

S6BSV973E# fields specified in control file exceeded


Explanation: Definition Control File Error: Thenumber of fields defined exceeds themaximum specified (S type entry columns31-33) earlier in the Control File.


S6BSV974ESELECT File: Illegal selection statement


Explanation: Selection Criteria File Error: Noselection criteria value supplied.


S6BSV975ESELECT File: Illegal Format


Explanation: Selection Criteria File Error: Thestatement cannot be processed.

Action: Refer to the documentation for thecorrect format of the Selection Criteriaentries, or use the onlineBATCHUNLD_CARDS tool to create aproperly formatted file.


| 447

S6BSV979EInput Data I/O error


Explanation: An input operation failed. This canbe caused by problems with the input device,but may be caused (on Solaris) by attemptingto read a file larger than 2 gigabytes in size.

Action: Check for the cause of the I/O failure andfix the problem. If the problem is caused byfile size, you may require the Large FileSupport feature. To obtain this feature,contact TIBCO Support.

S6BSV982EBad input data variable length format


Explanation: If variable-length format data isindicated in the Definition Control File, thedata must conform to z/OS variable-lengthformat: each record must be preceded by fourbytes as follows: a 2-byte length followed by2 bytes of binary zero.

Action: Check the input file and ensure the datais in Object Service Broker data format(EBCDIC) and that it is variable. If the file isnot variable, modify the Definition ControlFile accordingly.

S6BSV986EI/O error


Explanation: An input or output operationfailed. This can be caused by problems withthe I/O device, but most commonly is causedby one of:

• A lack of space on the device

• [Solaris] The file exceeds the 2 gigabytefile-size limit (input) or is attempting toexceed the limit (output)

Action: Check for the cause of the I/O failure andfix the problem. If the problem is caused byfile size, you may require the Large FileSupport feature. To obtain this feature,contact TIBCO Support.

S6BSV990ESELECT File: Blank value not permitted


Explanation: Selection Criteria File Error: Ablank criteria value is not permitted.


S6BSV996EMaximum row size exceeded


Explanation: There is a limit on the size of rowwhich Object Service Broker supports;anything longer than this cannot be stored onthe Pagestore.

Action: Correct the table definition, thedefinition in the utility control file does notmatch that presented to the Object ServiceBroker Table Definer.

S6BSV998EAccess to table denied


Explanation: You do not have the necessaryauthority to access this table

Action: Contact Object Service Brokeradministration and request the necessaryauthority


448 |

TA: TDS

S6BTA001ECTABLE build not supported for requestedtable type

Source: TDS

Explanation: Only valid table types such as TDS,SCR, IMS, etc. are supported. BecauseCTABLE build is issued internally, aninternal system error has occurred.


S6BTA004EExpected field not found in CTABLE

Source: TDS

Explanation: An internal system error occurred.


S6BTA008EGet key descriptor failed

Source: TDS

Explanation: Internal system error: unable toretrieve key/index information.



| 449

TB: TDS

S6BTB004EAttempt to insert duplicate parameter value set

Source: TDS

Explanation: Internal system error. If issuedduring redo processing, it warns that inserthas already been committed to the database(DASD) and it may or may not be a concern.


S6BTB005EExpected parameter value set not found

Source: TDS

Explanation: Internal system error. If issuedduring redo processing, it warns that thedelete (which causes this error) has alreadybeen done; it may or may not be a concern.



450 |

TC: TDS

S6BTC002ESecondary key field name already exists in SIT-page

Source: TDS

Explanation: Internal system error. If issuedduring redo processing, it warns thatsecondary index has already been built; itmay or may not be a concern.


S6BTC003EError detected during restart processing of SIXbuild

Source: TDS

Explanation: Internal system error.


S6BTC005EExpected secondary index entry not foundduring COMMIT

Source: TDS



S6BTC006ESecondary key field not found in table FIELDS

Source: TDS



S6BTC008EPrimary key (in secondary index entry) notfound

Source: TDS



S6BTC009ELower case page type encountered

Source: TDS

Explanation: Data or secondary index isunusable because a previous %CLRTAB,CLRTAB, table delete, SIXDELETE, orSIXBUILD did not complete.


• Avoid using that secondary key access.

• Delete the secondary index by callingSIXDELETE.

• Repeat the incomplete action.

S6BTC010EToo many secondary indexes

Source: TDS

Explanation: You attempted to build moresecondary indexes than are allowed.

Action: No action required. If you want to buildanother index, you can delete an existingsecondary index and rebuild the current one.


| 451

S6BTC011ELocation parameter is not last parameter in table

Source: TDS

Explanation: Table parameter of CLASS=L is aremote location parameter and must be thelast table parameter listed.

Action: Remove the location parameter or makeit the last parameter for this table.

S6BTC012EMismatch # secondaries SIT-PAGE andCTABLE

Source: TDS

Explanation: The number of secondary indexfields specified in the definition of this tabledoes not match the actual number accordingto the table's Secondary Index "T" page.


S6BTC013EExpected FIELDS entry not found

Source: TDS

Explanation: During an attempt to update thetable definition for the secondary index fieldbeing deleted, the FIELDS row could not befound.



452 |

TD: TDS

S6BTD003EChain of 3 or more pages detected with no indexlevel

Source: TDS



S6BTD004EIndex chaining error detected

Source: TDS




| 453

TE: TDS

S6BTE003EPage header data length error

Source: TDS



S6BTE004EIDGEN key exceeds maximum value

Source: TDS

Explanation: The IDgen key exceeds themaximum 4-byte integer value.

Action: Reorganize the IDgen table by unloadingit (both definition and occurrences),dropping the table, and reloading it.

S6BTE005EInvalid key length in occurrence

Source: TDS

Explanation: Internal system error. The actualkey length must be less than the definitionlength, which must be less than 128 bytes.Null key (i.e., key length=0) is not allowedfor a primary key, table parameter, andsecondary key of syntax B or P.

Action: If this message is received as a result ofattempting a SIXBUILD, the target table'sdefinition may have been modified to makethe partial Secondary Index unusable. Toavoid future table access problems, you mustissue a SIXDELETE against the same fieldthat caused the error, this will reset thedefinition.

For other requests (non-SIXBUILD), noaction is necessary. You cannot insert aNULL into a key or parm field of syntax B orP.

S6BTE006EInvalid field length in occurrence

Source: TDS

Explanation: Invalid field length detected duringCLC processing.


S6BTE007EInvalid data row length error

Source: TDS

Explanation: This error indicates that an invaliddata-row length was encountered in DataObject Broker processing, in either a messagerequest or a data page.



454 |

TF: TDS

S6BTF001EUnexpected page type found

Source: TDS



S6BTF002ETable name already exists in resident tableindex

Source: TDS



S6BTF003EDuplicate primary key or secondary index entry

Source: TDS

Explanation: If this message is issued duringRedo processing, it warns that the insert hasalready been committed to the database, andit may or may not be a concern. This couldalso happen during a "fast insert", whereinserted rows are not screened for duplicatekeys.

Action: Contact TIBCO Support unless youreceived this message during:

• Redo processing - Ignore this message if itappears only a few times.

• Fast insert when no phase 1 verification isdone - You have to verify that the data youare loading does not have duplicate keys.

S6BTF004EExpected row not found during COMMITprocessing

Source: TDS



• Ignore this message if you received itduring Redo processing.

• Contact TIBCO Support if this messagerepeats many times or if you did notreceive it during Redo processing.

S6BTF005EUnexpected page type within page chain

Source: TDS




| 455

TG: TDS

S6BTG001EInput request code is not supported

Source: TDS



S6BTG003ETable name in CTABLE does not matchrequested table name

Source: TDS




456 |

TH: TDS

S6BTH001ELength and/or range of MVCL is invalid

Source: TDS



S6BTH002ETable name not found in resident table index

Source: TDS



S6BTH007EInvalid field syntax detected

Source: TDS



S6BTH008EInvalid page header; row count is zero

Source: TDS



S6BTH009EError detected during index binary search

Source: TDS



S6BTH011EError detected while inserting a non-highkey

Source: TDS



S6BTH012EInvalid access path specification

Source: TDS



S6BTH015EInvalid input key value specification

Source: TDS



S6BTH051ETable type incompatible with target segment

Source: TDS

Explanation: A TDS table can only reside in aTDS segment.

Action: Check the target segment and table typefor compatibility when using MOVTAB.


| 457

S6BTH065EHash# (in LPMAP) not found in internal table

Source: TDS

Explanation: The hash number in LPMAP is notfound in the internal table. Internal systemerror.


S6BTH070ENon-standard hash (randomizer) failed

Source: TDS

Explanation: A hash function failed and returnedan error code.


• If it is a user-written hash function,determine the cause and correct theproblem. Changing a hash function whenthere are non-empty HDS tables still usingit may corrupt the tables.

• If the failed hash function is not user-written, contact TIBCO Support.

S6BTH080EInvalid syntax for a CLC field is found

Source: TDS

Explanation: One of the CLC fields has a fieldsyntax currently not supported by the CLCimplementation.

Action: Include in the CLC table definition onlythe source fields that have one of thefollowing field syntaxes: B, C, P, RD, UN, V,or W. The Key and Count fields must havesyntax B and length 4.

S6BTH081EInvalid length for a CLC field is found

Source: TDS

Explanation: One of the CLC fields has a fieldlength that exceeds the CLC implementationlimit.

Action: Include in the CLC table definition onlythe source fields that have field length <=127. The Key and Count fields must havesyntax B and length 4.

S6BTH082ENumber of CLC fields exceeds maximum

Source: TDS

Explanation: The total number of source fields ina CLC table definition exceeds the CLCimplementation limit.

Action: Include in the CLC table definition onlyup to 16 source fields. (Including the Key andCount fields, a CLC table can have maximum18 fields.)

S6BTH083ETarget table on TABLES must not contain data

Source: TDS

Explanation: When deleting a TDS tabledefinition or changing a TDS table type, thetable must not contain data.

Action: Before deleting the table definition orchanging a TDS table type, you must ensurethe table is empty. Use $CLRTAB.


458 |

S6BTH084EOBJ table type on TABLES cannot be changed

Source: TDS

Explanation: The request is to change a tabletype from/to the OBJ type.

This type of request is not supported. Youcannot change an OBJ table type to any othertype nor can you change any other table typeto OBJ.



| 459

TK: TRACKER Notification

S6BTK001ITRACKER Task initialization complete

Source: TRACKER Notification

Explanation: The TRACKER Notification Taskhas initialized successfully. The job will sendinitialization/termination notificationmessages to the TIBCO TRACKERSubsystem if it is running and theappropriate TRACKER DD JCL statement isspecified. Refer to TIBCO Object ServiceBroker Installing and Operating manual andTIBCO Mainframe Service TrackerInstallation and Administration manual.

Action: None.

S6BTK002ITRACKER Task termination complete


Explanation: The TRACKER Notification Taskhas ended normally.

Action: None.

S6BTK003ETRACKER Task invalid event code #


Explanation: An invalid request code wasreceived by the TRACKER task.

Action: Contact Product Support.

S6BTK004EInitialization of TRACKER Task failed;; RC=#


Explanation: The TRACKER Notification Taskfailed to initialize successfully.

Action: Contact Product Support.


460 |

TL: DOB Support Offline Utils

S6BTL001IRESTORE IN PROGRESS FORSEGMENT=___

Source: DOB Support Offline Utils

Explanation: The Pagestore restore utility(S6BTLRPS) was invoked to restore thesegment number indicated by this message.


S6BTL002EVSAM ERROR READING DBDLIB


Explanation: An error was detected reading theDBDLIB defined by the DBDLIB DD card.The utility terminates with a return code of12.

Action: Ensure that the data set specified on theDBDLIB DD statement points to a validDBDLIB.

S6BTL003WWARNING - PAGESTORE SMALLER THANBACKUP


Explanation: The Pagestore restore utility(S6BTLRPS) determined that the receivingPagestore data set currently being processedis smaller than the original, but should belarge enough to hold the data. The restorecontinues, and a return code of 4 is issuedupon its completion.

Action: If a reduction of the total space for thePagestore data set was intended, then nofurther action is required. Otherwise,reallocate the Pagestore data set to a largersize and rerun the restore utility.

S6BTL004EVSAM WRITE ERROR RC=__ FB=__


Explanation: An I/O error was detected whilewriting to the Pagestore data set currentlybeing processed. The utility terminates witha return code of 12.

Action: Verify that the Pagestore data setindicated is properly defined and rerun thejob.

S6BTL005EPAGE SPACE ALLOCATION TOO SMALL


Explanation: This message is issued when the

minimum space requirement, as determinedby the executing utility, is not satisfied.Utilities which issue this message areS6BTLFPS and S6BTLRPS. In the case of thePagestore formatting utility (S6BTLFPS) the


| 461

space allocated for the failing segment dataset does not meet or exceed the minimumspace allocation allowed for this data set.Failures encountered by the restore utility(S6BTLRPS) are issued when the segmentwhich is the target of the restore functiondoes not have enough space to contain all ofthe pages in the backup set.

Action: Reallocate the failing segment data setsso that they are large enough to satisfy therequirements of the executing utility. Rerunthe failed job.

S6BTL006ESYNTAX ERROR IN PARAMETER


Explanation: A syntax error was detected, aninvalid parameter was passed, or a requiredparameter was omitted in the PARMSspecified on the EXEC card for this utility.The utility terminates with a return code of12.

Action: Correct the parameters specified andrerun the utility.

S6BTL007WBAD PAGE NUMBER DETECTED


Explanation: An invalid page number wasdetected in the input file to the Pagestorerestore utility (S6BTLRPS). This may indicatea problem with the backup file beingprocessed. Message S6BTL008I is also issued

to indicate which record was found to be inerror. The restore utility continuesprocessing, but issues a return code of 8 uponcompletion.

Action: The database may be corrupted. Contactthe Object Service Broker SystemAdministrator for further assistance.

S6BTL008IRELATIVE RECORD NUMBER ____


Explanation: The indicated record is associatedwith a previous error.

Action: Refer to the accompanying message todetermine the cause of the problem and theappropriate action.

S6BTL009EDYNAMIC ALLOCATION FAILED


Explanation: A dynamic allocation error wasbeen detected. The utility is terminated witha return code of 12.

Action: Refer to the accompanying messages todetermine the failing data set and the causeof the failure.

S6BTL010EOPEN FAILED FOR _______ DATASET RC=__


Explanation: The opening of a Journal or aPagestore data set failed with the indicatedVSAM return code. The utility terminateswith a return code of 8 or 12.

Return codes appearing in the message arefor OPEN failures documented in the IBM"DFSMS Macro Instructions for Data Sets"


462 |

manual. The RC= value is actually returnedin the VSAM ACB field ACBERFLG and isexpressed as a decimal number.

Action: Refer to the accompanying systemmessages to determine the cause of thefailure.

RC=168 is most commonly caused byanother z/OS job or started task using thedata set and preventing the current job fromsuccessfully opening the data set. Retry thefailing job later or, if the Data Object Brokeris the user, vary the associated segmentoffline to the Data Object Broker and thenretry the failing job.

S6BTL011EJOURNAL DD NOT FOUND


Explanation: The required DD card for theJournal data set was not found in the JCLstream. The utility terminates with a returncode of 12.

Action: Include a Journal DD card in the JCLstream that points to a valid Object ServiceBroker Journal data set.

S6BTL012I_______ PAGES RESTORED FROM JOURNAL


Explanation: This message indicates the totalnumber of pages restored by the Pagestoreutility (S6BTLRPS).


S6BTL013EINVALID SEGMENT SPECIFIED


Explanation: The segment number specified wasnot located in the DBDLIB. The utilityterminates with a return code of 12.

Action: Verify that the correct segment numberwas requested.

S6BTL015EBITMAP MISSING FROM BACKUP,RESTORE TERMINATED


Explanation: The first record in the journal(backup) used to restore the PageStore dataset was not a bitmap page as expected. If youare attempting to apply a spinout journalonto a PageStore data set, the positionalparameter APPLY must be specified beforethe "SEG=" or "DUP=" keyword parameter.

Action: If applying a spinout journal, specifyAPPLY. If attempting to restore a backup,verify the backup using the S6BBRPTR(Batch Pointer Check) utility beforererunning the restore.

S6BTL016EERROR DETECTED EXTRACTINGARCHLOG DEFINITION FROM DBDLIB


Explanation: The utility requires access to theARCHLOG but was unable to access theDBDLIB definition for it. Possible causes are:

• The DBDLIB DD statement is not coded inthe utility JCL

• The DBDLIB does not contain a definitionfor the ARCHLOG

Action: Correct the specification of the DBDLIB.


| 463

S6BTL017EORIGINAL DATA FOR ARCHLOG UPDATECOULD NOT BE LOCATED


Explanation: When an Object Service BrokerS6BTL*** utility was attempting to update anentry in the ARCHLOG, the entry to bemodified could not be located. The logupdate process terminates with a nonzeroreturn code.


S6BTL018EERROR DETECTED WHENUNALLOCATING ARCHLOG DATASET


Explanation: An error was detected whenattempting to release the ARCHLOG after ithad been updated.


S6BTL019EOPEN ERROR FOR REPORT LISTING


Explanation: The utility being executed was notable to open the DD for the output listing(DDNAME=REPORT). The utility stoppedexecuting.

Action: Accompanying messages indicate thereason that the open failed. Correct thesituation and rerun the job.

S6BTL020EI/O ERROR ON JOURNAL


Explanation: An I/O error was encounteredwhile processing the Object Service BrokerJournal data set. The utility terminates with areturn code of 12.

Action: Contact the Object Service Broker SystemAdministrator for further assistance.

S6BTL021EJOURNAL RECORDS OUT OF SEQUENCE


Explanation: Input journal records are not in theexpected sort sequence.

Action: Sort the input journal data set in theexpected sequence and rerun.

S6BTL022I_________ PAGES ARCHIVED TO JOURNAL


Explanation: This message indicates the numberof pages that are archived to the ObjectService Broker Journal data set.



464 |

S6BTL023EVSAM ERROR RC=__ FB=__ RBA=________


Explanation: A VSAM error was encountered onthe data set currently being processed, asindicated by the accompanying messages.The VSAM Return Code (RC), FeedbackCode (FB), and the RBA of the failing recordare provided in the message text. The utilityterminates with a return code of 8.

Action: Contact the Object Service Broker systemadministrator. Reason codes are documentedin the z/OS DFP VSAM Macro InstructionReference. z/OS messages are documentedin the z/OS System Messages Manual.

S6BTL024EDATA CONTROL ERROR


Explanation: A page was found in an ObjectService Broker Pagestore that containsinvalid control data. The utility terminateswith a return code of 12.

Action: Contact your Object Service Brokersystem administrator for assistance.

S6BTL025EREAD ERROR RBA=0


Explanation: The record located at RBA=0 didnot contain the expected Object ServiceBroker control data. The utility terminateswith a return code of 12.

Action: Contact your Object Service BrokerSystem Administrator for assistance.

S6BTL026EARCHLOG OPEN ERROR FOR(READ|WRITE)


Explanation: An error was detected by thesystem when the ARCHLOG processor wasattempting to open the ARCHLOG for eithera read or a write operation.

Action: Review the joblog to identify the cause ofthe problem.

S6BTL027EDOB NOTIFICATION FAILED FOR SPINPROCESSING


Explanation: After the completion of the dataoffload from the Data Object Broker Journaldata set, the owning Data Object Brokercould not be contacted to reactivate thejournal. The journal is not available for reuseuntil the Data Object Broker is manuallynotified or recycled.

Action: If the Data Object Broker is currentlyactive, try rerunning the spin job to re-sendthe spin complete notification to the DataObject Broker.


| 465

S6BTL028EERROR DETECTED IN SEND WHENATTEMPTING TO NOTIFY DOB


Explanation: After the completion of the dataoffload from the Data Object Broker journaldata set, the notification of the completioncould not be sent to the owning Data ObjectBroker. The journal is not available for reuseuntil the Data Object Broker is manuallynotified or recycled.

Action: If the Data Object Broker is still active,rerun the SPIN process to attempt to re-sendthe notification.

S6BTL029EERROR DETECTED WHEN RELEASINGACQUIRED STORAGE


Explanation: When attempting to release storageobtained by a utility, the system found therelease to be in error. The process terminateswith a nonzero return code.


S6BTL030WARCHLOG RECORD FAILURE DETECTED,PROCESSING CONTINUED


Explanation: The ARCHLOG update processingroutine returned a nonzero return code.

Action: Processing continues. No action isrequired.

S6BTL031ES6BBKCXO ERROR R15=X'XXXXXXXX'


Explanation: An error was detected in the datacompression subroutine. Processingterminated.

Action: Review the user-supplied compressionexit to determine the cause of the error.

S6BTL032EARCHLOG PROCESSING ROUTINE LOADREQUEST FAILED


Explanation: The common subroutine thatmanipulates the ARCHLOG is dynamicallyloaded by various S6BTL*** utilities. Theload failed.

Action: Review the joblog to determine why theARCHLOG could not be loaded.

S6BTL033WARCHLOG PROCESSING IGNORED,DBDLIB NOT DEFINED IN JCL


Explanation: The DBDLIB is not defined in theutility job stream, the ARCHLOG cannot beidentified and therefore it cannot beprocessed.

Action: Correct the job stream to include a DDstatement for the DBDLIB.


466 |

S6BTL034ES6BBKCXR ERROR R15=X'XXXXXXXX'


Explanation: A failure was returned from theuser-supplied data compression routine.

Action: Determine the cause of the error as perthe supplied exit.

S6BTL035WHRNBKDXI ERROR R15=X'XXXXXXXX'


Explanation: An error was detected by the user-supplied data decompression routine.

Action: Determine the error by looking at yourroutine.

S6BTL036WCOMPRESSION DISABLED BY HRNBKDXI


Explanation: A user-supplied compressionroutine elected to disable compression.


S6BTL037WHRNBKDXR ERROR R15=X'XXXXXXXX'


Explanation: A user-supplied decompressionexit returned a nonzero return code.

Action: Determine the error via the user exit.

S6BTL038EARCHLOG CLOSURE ERROR DETECTED,PROCESSING CONTINUES


Explanation: After the successful completion ofARCHLOG update processing, the processdetected an error when closing theARCHLOG.

Action: Refer to the joblog for further failureinformation. No action is required,processing continues.

S6BTL039WHRNBKDXE ERROR R15=X'XXXXXXXX'


Explanation: A user-supplied datadecompression exit returned a nonzeroreturn code.

Action: Correct the error via the user exit.

S6BTL040WDATASET JFCB EXTRACT FAILED,PROCESSING CONTINUES


Explanation: During an attempt to obtain thedata set name and DASD volume for theCache data set, the read "JFCB" failed.Processing continues even though the DSNand volume are not available.



| 467

S6BTL041EINVALID DEVICE CLASS FOR LOGGING


Explanation: The Object Service Broker loggingdata set specified does not reside on a directaccess device.

Action: Change the allocation of the logging dataset so that it resides on a direct accessvolume.

S6BTL042EEXCP ERROR ON RELATIVE TRACK ___


Explanation: An EXCP error was encounteredwhile reading or writing to the Cache orContingency Log data set at the indicatedrelative track. The utility terminates with areturn code of 12.

Action: Refer to the accompanying z/OSmessages for further information regardingthis error, and contact TIBCO Support forassistance.

S6BTL043IRELATIVE TRACK ___ FORMATTEDSUCCESSFULLY


Explanation: The relative track indicated by themessage text was successfully formatted. Incases where the cache data set is beingformatted, the Cylinder and Head (CC HH)address of the track are also indicated.


S6BTL044EREDO.PENDING RESTRICTED TO 255TRACK MAXIMUM


Explanation: The contingency log format routinedetected the data set was defined to havemore than 255 tracks.

Action: Redefine the clog with 255 or less tracksand rerun the format utility (S6BTLFCL).

S6BTL045EREDO.PENDING RESTRICTED MUST HAVEAT LEAST 6 TRACKS


Explanation: When formatting the contingencylog it was detected to have less than 6 tracks.

Action: Redefine the CLOG with 6 to 255 tracksand rerun the format utility (S6BTLFCL).

S6BTL046WWORKING STORAGE NOT AVAILABLECONFIGURATION RECOVERY IGNORED


Explanation: When the contingency logformatting routine was attempting to acquirestorage to process the configurationinitialization data set the storage was notavailable.

Action: Increase the region parameter of your jobcontrol statements and rerun the formatutility (S6BTLFCL).


468 |

S6BTL047EREDOLOG RECORD SIZE MUST BECONTROL INTERVAL SIZE - 7


Explanation: In order to allow the REDOLOG tobe dump using IDCAMS it is important thatthe maximum record length defined for theVSAM data set is adequate. To ensure thesize is appropriate the S6BTLFRL(REDOLOG Format Utility) required therecord length to be the VSAM maximumwhich is the CISIZE-7 (Control Interval Size).

Action: Change the VSAM define parameters tocorrect the record length. For example(CISZ(4096) RECSZ(200,4089)).

S6BTL048EDEVICE CHARACTERISTICS EXTRACTFAILURE DETECTED


Explanation: When attempting to extract thedevice characteristics of the media on whichthe ARCHLOG is defines an error wasdetected.

Action: Ensure the ARCHLOG is defined onDASD. If the problem recurs, contact TIBCOSupport.

S6BTL049EDEVICE DOES NOT SUPPORT DIRECTACCESS


Explanation: The ARCHLOG is maintainedusing "Update In Place" processing and musttherefore reside on media that supportsdirect access.

Action: Redefine the ARCHLOG data set onDASD and run the S6BTLFAL format utilityagain.

S6BTL050EREDOLOG CI SIZE NOT 2K OR 4K


Explanation: While processing the redolog, anunacceptable value for the CISIZE of the dataset was found as displayed in the messagetext. The utility terminates with a return codeof 12.

Action: Redefine the Object Service Brokerredolog with an acceptable CISIZE.


| 469

S6BTL051EWRITE ERROR ON RELATIVE TRACK ___ -CC HH=____ ____


Explanation: An error was encountered writingto the data set indicated by previousinformational messages, at the relative trackindicated in the message. The physical trackaddress (CC HH) is also noted by thismessage. The utility terminates with a returncode of 12.

Action: This message has probably been issuedin response to a media failure. Try redefiningthe affected data set on another volume, andcontact your Object Service Broker SystemAdministrator.

S6BTL052EDATASET JFCB EXTRACT FAILED,PROCESSING TERMINATED


Explanation: When attempting to extract theJFCB (data set characteristics) for theARCHLOG and error was detected.

Action: Ensure the ARCHLOG is defined, theJCL is correct and run the format utilityagain. If the problem recurs, contact TIBCOSupport.

S6BTL053WSCHEDULE CANNOT HAVE BOTHAPPLICABLE DAYS AND OVERRIDE DATE,CARD REJECTED


Explanation: When processing the pathmanagement cards in S6BTLFCL, it wasdetected that an override date was suppliedon a card that also specified applicable days.The two scheduling techniques are mutuallyexclusive and the card is rejected.

Action: Correct the rejected card and reformatthe CLOG.

S6BTL054EARCHLOG MUST HAVE AT LEAST 2BLOCKS PER TRACK


Explanation: The ARCHLOG is fixed blocked(FB) with a record length of 132. In order tosupport processing the blocksize must bedefined to be less than one half of a track.

Action: Redefine the ARCHLOG with anappropriate blocksize, (half track blocking isrecommended) and rerun the format utility.

S6BTL055ITRACKS SUCCESSFULLY FORMATTED


Explanation: During the formatting of the DataObject Broker's data sets, the specified trackswere formatted successfully. This message isgenerated when formatting the cache and thecontingency log. The CACHE formattersuffixes the message with "CCHH=..." to

indicate the track head position. The CLOGformatter indicates if the tracks are"RESERVED" or "CLOG" with a suffix to the

message.



470 |

S6BTL056IFORMATTING DUPLEX REDOLOG


Explanation: This informational messageidentifies this run is formatting the duplexcopy of the REDOLOG.


S6BTL057EARCHLOG CONTROL ENTRY NOT FOUND


Explanation: The first entry in the ARCHLOGdata set is a control entry used to retaininformation about the ARCHLOG and thenext insert point. When attempting to readthis entry, it could not be found. The mostprobable cause is that the ARCHLOG wasnot formatted.

Action: Format the ARCHLOG using theS6BTLFAL utility.

S6BTL058EARCHLOG BLOCK SIZE TOO SMALL


Explanation: The entries on the ARCHLOG aregrouped together for each Object ServiceBroker utility execution. The number of lineswithin a group depends on theconfiguration. In order to support processingrequirements, it is required that the blocksizebe such that it is large enough to retain onefull group. For example, if a segment is

defined with 100 ACBS the backup utility(S6BTLBPS) generates an ARCHLOG groupof 103 items, therefore the minimumblocksize would be 103 * 132.

Action: Redefine and reformat the ARCHLOGwith a large blocksize (half track blocking isrecommended).

S6BTL059EARCHLOG I/O ERROR DETECTED,PROCESSING TERMINATED


Explanation: When attempting to read theARCHLOG in order to produce theARCHLOG report, S6BTLPAL detected anI/O error.

Action: Rerun the S6BTLPAL. If the problemrecurs, contact TIBCO Support.

S6BTL060ENO ENTRIES FOR ARCHLOG UPDATEPROCESS


Explanation: The ARCHLOG update processingroutine was called to add records to theARCHLOG. The calling program failed toprovide the entries to be added.



| 471

S6BTL061EPAGESTORE DATASET LIMITED TO 507904PAGES, ALLOCATION EXCEEDS LIMITS


Explanation: When the Pagestore data set wasdefined, the number of cylinders allocatedprovided more space than the Data ObjectBroker can support.

Action: Redefine your Pagestore data set with asmaller allocation. Refer to the Installationand Configuration manual for moreinformation. If you need to expand yoursegment capacity, an alternative would be toincrease the ACB limit (number of Pagestoredata sets).

S6BTL070ENO ____STORES DEFINED IN DBDLIB


Explanation: Processing was requested for theindicated Object Service Broker data set type.However, none was defined in the DBGENinformation provided by the DBDLIB DDcard. The utility terminates with a returncode of 12.

Action: Correct your DBGEN to include therequired Object Service Broker data set type,and rerun the utility.

S6BTL071EDDNAME=________ NOT A VSM DATASET


Explanation: The data set pointed to by theDDNAME indicated in the message text isnot a VSAM data set. The utility terminateswith a return code of 12.

Action: Correct the data set referenced by theDDNAME, and rerun the utility.

S6BTL072EDDNAME=________ NOT A VALIDPAGESTORE


Explanation: The data set pointed to by theDDNAME reflected in the message text wasnot defined in the DBGEN as an ObjectService Broker data set of the type indicated.The utility terminates with a return code of12.

Action: Correct the indicated DDNAME to pointto a valid Object Service Broker data set, andrerun the utility.

S6BTL073I_______ PAGES SUCCESSFULLYFORMATTED


Explanation: This message confirms the numberof pages formatted by one of the formattingutilities.


S6BTL074ENO INPUTS SPECIFIED VIA DD CARDS


Explanation: The executing utility expected tofind "DDn" DD cards in the JCL that indicatethe data sets to be processed. However, nonewere found. The utility terminates with areturn code of 12.

Action: Correct the JCL stream to include DDcards for processing.


472 |

S6BTL075E________ DATASET NOT EMPTY


Explanation: The format utility has determinedthat the data set being processed may containvalid data. The utility terminates with areturn code of 12.

Action: Correct the JCL stream to point to anempty data set. If you are reformatting apreviously used data set, delete and redefinea new cluster prior to executing this utility.

S6BTL079EREDOLOG OPEN FAILED


Explanation: HRNTLRDO was unable to open aredolog file and terminates with a returncode of 12.

Action: Correct the JCL stream to point to a validredolog file.

S6BTL080ETIBCO(r) Object Service Broker NOTAVAILABLE


Explanation: The requested Object ServiceBroker system is not currently available.

Action: Ensure that the correct Object ServiceBroker system was requested, and wait for itto become available. Contact your ObjectService Broker System Administrator forfurther assistance.

S6BTL081ETIBCO(r) Object Service Broker VERSIONMISMATCH


Explanation: The version of Object ServiceBroker under which this utility is executingdoes not match the version of Object ServiceBroker under which the requested DataObject Broker is executing. The utilityterminates with a return code of 12.

Action: Ensure that anyJOBLIB/TASKLIB/STEPLIB DD cardspresent in either the utility program's JCL, orthe Object Service Broker Data ObjectBroker's startup JCL are referencing theproper level of the Object Service Brokersoftware. Contact your Object Service BrokerSystem Administrator for further assistance.

S6BTL083ETIBCO(r) Object Service BrokerCOMMUNICATION ERROR CODE


Explanation: When attempting to establish acommunication link from a batch utility tothe Data Object Broker, the Object ServiceBroker communication subsystem detectedan error. In the current release the only validreturn codes are 0 - successful and 16 -unsuccessful.



| 473

S6BTL084ETIBCO(r) Object Service Broker CONNECTERROR CODE


Explanation: When attempting to opencommunications between the applicationand the Object Service Broker Data ObjectBroker, either the communicationssubsystem or the Data Object Brokerdetected an error.


S6BTL085EMDLAPPL COULD NOT BE MATCHED


Explanation: When attempting to open VSAMcommunications to the Object Service BrokerData Object Broker, the model APPLID wasfound to be invalid. No such VTAM resourceis defined or available in the network.

Action: Ensure that the appropriate TDS=and/or MDL= parameters represent realresources in your environment.

S6BTL090E'TDSAPPL,MDLAPPL' PARAMETERSOMITTED OR INVALID


Explanation: Mandatory parameters to describethe target Object Service Broker connectionname were not provided.

Action: Ensure that the appropriate TDS= andMDL= parameters are provided.

S6BTL091E'##,TDSAPPL,MDLAPPL' PARAMETERSOMITTED OR INVALID


Explanation: Mandatory parameters to describethe target Object Service Broker connectionname or timing delays were not provided toS6BTLCMD.

Action: Ensure that the appropriate TDS= andMDL= parameters are provided.

S6BTL092EUNEXPECTED KEYWORD PARAMETER,________


Explanation: A keyword parameter passed to anoffline utility is not supported by that utility.

Action: Correct the keyword specification andresubmit the job. View the SYSLOG foradditional data on the error, or contactTIBCO Support if further assistance isrequired.

S6BTL093ENO TEXT FOLLOWING KEYWORDPARAMETER, ________


Explanation: A keyword parameter passed to anoffline utility has not specified acorresponding value.

Action: Correct the keyword specification andresubmit the job. View the SYSLOG foradditional data on the error, or contactTIBCO Support if further assistance isrequired.


474 |

S6BTL094EUNEXPECTED POSITIONAL PARAMETER


Explanation: A startup parameter passed to anoffline utility via the PARM=.... JCL directivewas specified incorrectly or containsparameters not supported by this utility.


S6BTL095E,


Explanation: The S6BTL095E message labelprovides a reference point for the display oferror text returned from the Data ObjectBroker when a SPIN ENABLE process fails tocomplete properly. It is expected that themessage text will be detailed enough toidentify the problem so it can be corrected.

Action: Base your action on the message textreceived from the Data Object Broker.

S6BTL096EUser -------- has been denied access to thisservice by External Secur


Explanation: DOB is running withSECUREADMIN=Y and user uuuuuu doesnot have External Security authorization toissue DOB Commands. Rest of the inputstream is flushed and the utility stops sincethere is no point in keep s sending thecommands to the DOB.

Action: Contact your Security Administrator andeither run the DOB without SECUREADMIN=Y or update this user's ExternalSecurity profile to allow_him/he theprivillege of issuing DOB Commands viaS6BTLCMD

S6BTL100EBATCH INITIALIZATION FAILED


Explanation: The initialization of the batchprocessing environment failed. Refer to theaccompanying messages to determine thecause of the failure.

Action: Correct the problem indicated andresubmit the job.

S6BTL101IBATCH INITIALIZATION OK


Explanation: The initialization of the batchprocessing environment completedsuccessfully.



| 475

S6BTL102ISUMMARY STATS: READS ________ WRITES________


Explanation: This message is issued tosummarize the database activity generatedby an offline utility.


S6BTL103IFREE PAGES ACQUIRED ________


Explanation: This message is issued tosummarize the database activity generatedby an offline utility.


S6BTL104ETERMINATION EXIT ERROR


Explanation: A nonzero return code wasreturned by the batch processing terminationexit (BATCHTMX).

Action: Contact your system administrator forfurther information.

S6BTL105IBATCH FUNCTION COMPLETED


Explanation: This message is issued to signal theend of batch processing.


S6BTL106EI/O ERROR WHILE WRITING THECONTROL PAGE


Explanation: An I/O error occurred whilewriting the Object Service Broker controlpage.

Action: Read the accompanying messages to findthe cause of the I/O error.

S6BTL107EMESSAGE ERROR


Explanation: An invalid Object Service Brokermessage unit was encountered during batchprocessing.

Action: Contact your System Administrator forassistance.

S6BTL108ENO HOST SESSION FOR BATCH SERVER


Explanation: The requested host session eitherdoes not exist or is not able to service yourrequest at this time.

Action: Ensure that a valid host VTAM APPLIDwas coded. If the APPLID is valid, retry yourrequest at a later time, or contact your ObjectService Broker System Administrator.


476 |

S6BTL109EBATCH - PUTFREE PAGE FAILED


Explanation: During batch processing, aPUTFREE page request failed.


S6BTL110EFREE OVERFLOW FAILED


Explanation: An attempt to free an overflow areahas failed.


S6BTL111EFREE HASH EXTENT FAILED


Explanation: An attempt to free a HASH tableextent has failed.


S6BTL112EPAGE NUMBER OUT-OF-RANGE FOR THISPAGESTORE


Explanation: The requested page number is notwithin the range of available pages for thissegment.


S6BTL121IPAGESTORE INPUT OPEN ERROR


Explanation: An error was detected by theoperating system when attempting to openthe Pagestore data set. The utility terminateswith a return code of 8.

Action: View the job SYSLOG for moreinformation about the open failure.

S6BTL122IOUTPUT TAPE OPEN ERROR


Explanation: An error was detected by theoperating system when attempting to openthe tape file for output. The utility terminateswith a return code of 8.


S6BTL123IVSAM LOGICAL ERROR ON INPUT


Explanation: An error was detected by theoperating system when attempting to readthe VTAM RPL for the next Pagestore record.The read attempt resulted in a return code of4 or 8. The utility terminates with a returncode of 8.



| 477

S6BTL124IVSAM PHYSICAL ERROR ON INPUT


Explanation: An error was detected by theoperating system when attempting to readthe VTAM RPL for the next Pagestore record.The read attempt resulted in a return code of12. The utility terminates with a return codeof 8.


S6BTL130IINVALID NUMERIC FIELD SET TO ZERO


Explanation: The configuration input record toS6BTLFCL contains invalid numeric data.The value of 0 is assumed.

Action: Correct the configuration cards andrerun S6BTLFCL.

S6BTL131IINPUT: ______ CONTROL, ______SCHEDULES


Explanation: This message is issued by thecontingency log formatting utility(S6BTLFCL) to report on the number of PathManagement control cards processed whileformatting the log. The variable portions ofthe message text indicate the number of Pathcontrol cards (CONTROL) and the number ofPath Management control cards(SCHEDULES) processed.


S6BTL132EDBDLIB PROCESSING ERROR


Explanation: ERROR READING DBDLIB

Action: CORRECT ERROR & RESUBMIT

S6BTL133EGETMAIN STORAGE FAILED "OR"GETMAIN FAILED


Explanation: insufficient memory available

Action: increase region size & resubmit

S6BTL134EREPORT PROCESSING PROBLEM


Explanation: ERROR ALLOCATING REPORTDD

Action: CHECK JCL TO ENSURE ALLREQUIRED REPORT DD STATEMENTSARE PRESENT

S6BTL135EINVALID ADDRESS - LOGIC ERROR


Explanation: There is an invalid address pointerto the next bitmap page.

Action: This is the result of a program logic error;the program is unable to continue. ContactTIBCO Support.


478 |

S6BTL136IDATE CONVERSION ACTIVATED


Explanation: Date Conversion Parameter CONVappears in JCL.

Action: No action required; date conversion isautomatic.

S6BTL137I#DATTIM CONVERSION ERROR


Explanation: Something got triggered duringexecution of the date conversion routine.

Action: Open a problem incident and retain theimage of the backup for analysis.

S6BTL150EKEYWORD PARAMETER TOO LONG


Explanation: The identified keyword is too long.Possibly the "=" is missing.


S6BTL151EPARAMETER IS TOO LONG


Explanation: The parameter value supplied forthe specified keyword is too long.


S6BTL152EIS AN UNRECOGNIZED KEYWORDPARAMETER


Explanation: The specified keyword parametercould not be identified.


S6BTL153EHOST AND MODEL ARE REQUIREDPARAMETERS


Explanation: The host and model parameters arerequired to make the connection to the DataObject Broker. One or both of theseparameters is missing or not recognized.


S6BTL154EOUTPUT FILE COULD NOT BE OPENED, SEEJOB LOG


Explanation: The file onto which the Resourcerepository is to be backed up could not beopened. Check the job log for moreinformation.



| 479

S6BTL155EREQUEST COULD NOT BE SENT TO THEDOB


Explanation: When attempting to send a requestto the Data Object Broker the send functionreturned an error.

Action: Correct and retry, review the job log forfurther information.

S6BTL156ERETRIEVAL ERROR DETECTED


Explanation: When attempting to retrieveresource detail information the retrievalrequest failed.

Action: If the job log messages do not identify theproblem, contact TIBCO Support.

S6BTL160IREDOLOG COPY INPUT CI SIZE IS(4096|8192) BYTES


Explanation: Identifies the control interval (CI)size of the input redolog on the REDOIN DD.Valid CI sizes are 4096 or 8192 - any other sizecauses S6BTLFRL to fail with RC=12.

Action: None - information only.

S6BTL161IREDOLOG COPY OUTPUT CI SIZE IS(4096|8192) BYTES


Explanation: Identifies the control interval (CI)size of the output redolog on the REDOOUTDD. Valid CI sizes are 4096 or 8192 - anyother size causes S6BTLFRL to fail withRC=12.

Action: None - information only.

S6BTL162EREDOLOG COPY REDOIN OPEN FAILED


Explanation: The open of the input redolog onthe REDOIN DD failed. The task terminateswith a RC=12.

Action: Check that the file is not in use by anyother task. Check that the file is a validVSAM REDOLOG. Rerun the job.

S6BTL163EREDOLOG COPY REDOOUT OPEN FAILED


Explanation: The open of the input redolog onthe REDOOUT DD has failed. The taskterminates with a RC=12.

Action: Check that the file is not in use byanother task. Check that the file is a validVSAM REDOLOG. Rerun the job.


480 |

S6BTL164EREDOLOG COPY REDOIN/OUT HI-U-RBANOT EQUAL TO HI-A-RBA


Explanation: A valid redolog has a VSAM HIused RBA equal to the HI alloc RBA. If eitherthe input REDOLOG or the outputREDOLOG does not meet this requirement,the file could be corrupt or not be a redolog.

Action: Obtain a listcat of the respectiveredologs. Identify which one is invalid.Confirm that it is a redolog.

S6BTL165EREDOLOG COPY REDOIN/OUT CI SIZEMISMATCH


Explanation: The CISIZE for the inputREDOLOG is different from the CISIZE ofthe output redolog. Both LOGS must havethe same CISIZE for the copy to work.

Action: Delete and redefine the target REDOLOGwith the correct CISIZE. Reformat the targetredolog. Rerun the copy task.

S6BTL166EREDOLOG COPY DATASET SIZEMISMATCH


Explanation: The input and output redologs arenot the same size. For the copy to work, theymust be the same size. The task is terminatedwith RC=12.

Action: Delete and redefine the target REDOLOGwith the correct CISIZE. Reformat the targetredolog. Rerun the copy task.

S6BTL167EREDOLOG COPY REDOOUT DATASET NOTFORMATTED


Explanation: The target redolog is not formatted.The copy is terminated with RC=12.

Action: Check that the target redolog is thecorrect data set. Reformat the target redolog.Rerun the copy task.

S6BTL168EREDOLOG COPY INPUT DATASET ISFORMATTED - COPY DISALLOWED


Explanation: The input REDOLOG is formatted.The copy task terminates with RC=12.

Action: Check that you have specified the correctREDOLOG, and then rerun the job.

S6BTL169EREDOLOG COPY I/O ERROR WRITINGREDOOUT


Explanation: An I/O error occurred whilewriting to the target REDOLOG. The job isterminated with RC=12.

Action: Refer to message S6BTL172E for VSAMfeedback codes to determine the cause of theerror.


| 481

S6BTL170EREDOLOG COPY I/O ERROR READINGREDOIN


Explanation: There was an I/O error reading theinput REDOLOG. The job is terminated witha RC=12.


S6BTL171EREDOLOG COPY I/O ERROR READINGREDOOUT


Explanation: There was an I/O error reading thetarget redolog.


S6BTL172EREDOLOG COPY I/O ERROR RC=__ FB=


Explanation: An I/O error occurred processingeither the REDOIN or REDOOUT DD. Thismessage contains the VSAM return code andfeedback code, and is issued after messagesS6BTL169E, S6BTL170E, or S6BTL171E.

Action: Refer to the appropriate IBM manual forthe meaning of the VSAM error codes.

S6BTL173IREDOLOG COPY REDOIN CI COUNT =


Explanation: This message indicates the numberof control intervals (CIs) read from the inputREDOLOG.

Action: None - Information only.

S6BTL174IREDOLOG COPY REDOOUT CI COUNT =____


Explanation: This message indicates thenumbers of control intervals (CIs) written tothe output REDOLOG.

Action: None - Information only.

S6BTL175ECACHE OPEN ERROR DETECTED


Explanation: During the execution of a utilitywhere the cache is processed, the cache dataset open failed.

Action: Review the job log for furtheridentification of the problem.

S6BTL176EDATASET MUST BE CONTAINED WITHINONE EXTENT


Explanation: When formatting a Data ObjectBroker file, Object Service Broker detectedthat the allocation required multiple extents.This is not supported.



482 |

• Decrease the primary quantity for thedefinition

• Relocate the data set to a different volume

• Request the definition with contiguousspace


| 483

TR: TDS

S6BTR001EInvalid field syntax for secondary index

Source: TDS

Explanation: Secondary index cannot be definedand built on fields with syntax W and F.

Action: Do not use SIXBUILD on fields withsyntax W or F.

S6BTR002ECTABLE too large to return for table

Source: TDS

Explanation: The table definition is too large tobe processed. Possible reasons are:

• Too many fields

• The Data Object Broker parameterCTABLESIZE is too small

• Too many stored selections.

Action: Increase the Data Object Brokerparameter CTABLESIZE from 8 to 16 todouble the CTABLE size to 16 KB. The DataObject Broker must be shut down andrestarted with the new parameter.

S6BTR003ECannot derive PRM table from non-TDS table

Source: TDS

Explanation: The source of a parameter (PRM)table must be a TDS table.

Action: Do not define a PRM table on a non-TDSsource.

S6BTR004EOn-line SIXBUILD disallowed for large table

Source: TDS

Explanation: Online use of SIXBUILD isrestricted by the size of the table, forperformance and operation reasons.

Action: Use S6BBRSIX to build a secondary indexwhen the table has more than 3000 datapages.

S6BTR005EField name not found in table

Source: TDS

Explanation: The input field name is not one ofthe defined fields for the table.

Action: Verify the field name and repeat theoperation.

S6BTR006ESecondary index not found in

Source: TDS

Explanation: The secondary index was not built,but was expected.

Action: Call SIXBUILD (online) or S6BBRSIX(offline) to build the secondary index andrepeat the operation.


484 |

S6BTR007ESecondary index already exists in

Source: TDS

Explanation: You tried to build a secondaryindex when it already exists.


S6BTR008ESecondary key length > 127 in

Source: TDS

Explanation: You used SIXBUILD (to build asecondary index) on a field whose length isgreater than maximum allowed.

Action: Do not use SIXBUILD on a field with alength greater than 127.

S6BTR009EInvalid table type (not TDS) for table

Source: TDS

Explanation: Certain database operations, suchas SIXBUILD and CLRTAB, are applicableonly to TDS tables.

Action: Do not use SIXDELETE or CLRTAB onnon-native tables (i.e., tables other than TDStables). Do not use SIXBUILD on non-TDStables.

S6BTR010EField name must not be the primary key in

Source: TDS

Explanation: You tried to build an index(SIXBUILD) or delete an index (SIXDELETE)on a primary key.

Action: Do not use SIXBUILD or SIXDELETE ona primary key field.

S6BTR011EToo many fields defined for a composite key

Source: TDS

Explanation: The maximum number of fieldsallowed in a composite key is 16.

Action: Reduce the number of fields in thecomposite key.

S6BTR013ETABLES occurrence not found for table

Source: TDS

Explanation: The requested table has not beendefined yet.

Action: Use the Table Definer to define the table.

S6BTR014ENo fields defined for table

Source: TDS

Explanation: No occurrence for the table is in theFIELDS table, but an occurrence exists in theTABLES table.

Action: Use the Table Definer to define fields forthe table.

S6BTR015ESource tablename required in definition fortable

Source: TDS

Explanation: The name of a source table was notprovided when required.

Action: Provide the appropriate source name.


| 485

S6BTR017ETable row exceeds maximum size for table

Source: TDS

Explanation: The calculated row length (basedon the sum of field lengths) exceeds 4051bytes.

Action: Reduce the field lengths or the number offields.

S6BTR018EInvalid field number found for a field of table

Source: TDS

Explanation: The field number must be aninteger greater than 0.

Action: Edit the occurrences of the FIELDS tableto ensure that all NUMBER values are greaterthan 0 and consecutive.

S6BTR019EInvalid sort direction in ordering of table

Source: TDS

Explanation: Stored ordering must either be A(for ascending) or D (for descending).

Action: Edit the occurrences of the ORDERINGtable for this table to ensure that the order isA or D.

S6BTR021EKey field not field number 1 in table

Source: TDS

Explanation: For TDS tables, the primary keyfield must be the first field.

Action: Edit the occurrence for the table in theFIELDS table to ensure that the field whereNUMBER=1 is the primary key.

S6BTR022EKey must be defined as BINARY 4 for IDGENtable

Source: TDS

Explanation: The only type of key supported foran IDgen table is one with binary syntax (B)and a length of 4.

Action: Use the Table Definer to either setIDgen=N or define the primary key correctly.

S6BTR023EDefinition too large to process for table

Source: TDS

Explanation: The table definition is too large tobe processed. Possible reasons are:

• Too many fields

• The Data Object Broker parameterCTABLESIZE is too small

• Too many stored selections.

Action: Increase the Data Object Brokerparameter CTABLESIZE from 8 to 16 todouble the CTABLE size to 16 KB. The DataObject Broker must be shut down andrestarted with the new parameter.

S6BTR024ESevere error occurred building CTABLE fortable

Source: TDS




486 |

S6BTR025ELength must be 1 for LOGICAL attribute for

Source: TDS

Explanation: For a field with a semantic type oflogical (L), its LENGTH must be 1.

Action: Either change the field type or fieldlength to avoid error.

S6BTR027ELength of 2 or 4 required with BINARY syntaxfor

Source: TDS

Explanation: For a field with binary syntax (B),only lengths of 2 and 4 are currentlysupported.

Action: Change the field length accordingly.

S6BTR028EZero DECIMAL required with type/syntaxspecified for

Source: TDS

Explanation: Unless a field is defined withpacked decimal syntax (P), the DECIMALfield must be 0.

Action: Either make SYNTAX=P or setDECIMAL=0 for the indicated field.

S6BTR029ENon-positive length specified for

Source: TDS

Explanation: The length of a field must be greaterthan 0.

Action: Change the field length to a valid integer.

S6BTR030ELength of 4/8/16 required with FLOAT syntaxfor

Source: TDS

Explanation: For a field of floating point syntax(F), only three places of precision aresupported.

Action: Change the field length to 4, 8, or 16.

S6BTR031EInvalid type/syntax combination for

Source: TDS

Explanation: The combination of semantic typeand syntax is not supported.

Action: Refer to the Managing Data manual forthe permitted syntaxes for each semantictype.

S6BTR032EInvalid syntax for

Source: TDS

Explanation: The syntax for the indicated field isnot permitted for its semantic type.


S6BTR033EInvalid semantic type for

Source: TDS

Explanation: The semantic type for the indicatedfield is not permitted for its syntax.



| 487

S6BTR034ENo definition found for virtual Screen

Source: TDS

Explanation: The screen name is not found in thetable SCREENS.


S6BTR035ENo screen tables found for virtual Screen

Source: TDS

Explanation: The screen has no correspondingscreen table.

Action: Use the Screen Painter to define at leastone screen table.

S6BTR036ENo screen fields defined for screen table

Source: TDS

Explanation: Every screen table must have atleast one field.

Action: Use the Screen Table Painter to create atleast one field for the named screen table.

S6BTR037ENo CTABLE found for screen table

Source: TDS

Explanation: An error was encountered inbuilding a CTABLE for the screen table whilebuilding a CTABLE for the screen.

Action: Check that all the field definitions for theindicated screen table are correct or contactTIBCO Support.

S6BTR038ENo CTABLE field entry found for screen field

Source: TDS

Explanation: No screen field is defined for theindicated screen table.

Action: Use the Screen Table Painter to define atleast one field for the screen table.

S6BTR039EScreen CTABLE too large for virtual Screen

Source: TDS

Explanation: Too many screen fields or too manyscreen tables are defined for the screen.

Action: Change the Data Object Brokerparameter XTABLESIZE from 16 KB (thedefault size) to an appropriate value, orreduce the number of screen tables andscreen fields.

S6BTR040ENo definition found for reference table

Source: TDS

Explanation: The reference table name providedin the REFERENCE field of the FIELDS tabledoes not exist.

Action: Set the REFERENCE field to null orprovide a valid table name.

S6BTR041EInvalid table type for reference table

Source: TDS

Explanation: The reference table named in theREFERENCE field of the FIELDS tablecannot be a screen table or an export table.

Action: Set the REFERENCE field to null orprovide a valid table name.


488 |

S6BTR042EError occurred building key code for table

Source: TDS



S6BTR045EMultiple key fields are not contiguous for table

Source: TDS

Explanation: Composite primary key must bedefined over contiguous fields.

Action: Redefine the table using Table Definer.Rearrange the order of defined fields suchthat the primary key fields are contiguous.

S6BTR050EWindow ctable build error encountered indefinition table

Source: TDS

Explanation: An inconsistency has been detectedin the definition table. For example, the tableinstance for the window may be empty, or agraphical object mapping a screen field(given by @DATAMAPPING) may not existin the window. This could have resulted fromediting the definition table without knowingthe dependencies involved.

Action: For a nonexistent graphical object as anoccurrence in @DATAMAPPING, either addthe graphical object through the WindowBuilder or remove the occurrence from@DATAMAPPING. Contact TIBCO Support.

S6BTR053EDictionary table not defined

Source: TDS

Explanation: The requested table is not in@IDMSTABLES.

Action: Redefine the external table for CA-IDMSdata.

S6BTR054ENo IDMSTABLES definition found for table

Source: TDS

Explanation: No occurrence was found in thetable @IDMSTABLES for the requested IDMtable.

Action: Delete the table definition for the giventable (by using the Table Editor) and redefinethe table with the CA-IDMS manager system.

S6BTR055EError encountered retrieving IDMSACCESS

Source: TDS

Explanation: The IDMSACCESS page retrievedis not a data page.


S6BTR056ESubschema definition not found

Source: TDS

Explanation: The subschema definition for thegiven table does not exist in TIBCO(r) ObjectService Broker.

Action: Load the subschema definition with theCA-IDMS manager system.


| 489

S6BTR057ERecord name not found in tableIDMSRECORDS

Source: TDS

Explanation: The requested record was notfound in the subschema definition.

Action: Use the CA-IDMS manager system toreload the subschema.

S6BTR058ENo IDMSFIELDS table found for table name

Source: TDS

Explanation: No fields were found for the giventable.

Action: Delete and redefine the CA-IDMS tabledefinition.

S6BTR059ENo IDMSFIELDS entry found for field name

Source: TDS

Explanation: FIELDS(tablename) and@IDMSFIELDS(tablename) do not match.

Action: Delete and redefine the CA-IDMS tabledefinition.

S6BTR060ENo IDMSELEMENTS table found for recordname

Source: TDS

Explanation: The requested field was not foundin the subschema definition.

Action: Reload the subschema definition.

S6BTR061ENo IDMSELEMENTS entry found for elementname

Source: TDS

Explanation: The requested element name wasnot found in the @IDMSELEMENTS table forthe given subschema and record.

Action: Reload the subschema definition.

S6BTR063EError encountered retrieving IDMSINDEXES

Source: TDS

Explanation: The page retrieved was not a datapage.


S6BTR064ECTABLE for IDMS data too large for table

Source: TDS

Explanation: The IDM table definition hasexceeded the maximum allowed.

Action: Increase the XTABLESIZE= parameter inthe Data Object Broker startup.

S6BTR074ENo definition found for report

Source: TDS

Explanation: No definition could be found forthe indicated report.

Action: Check that you have specified the correctreport name.


490 |

S6BTR075ENo report tables defined for report

Source: TDS

Explanation: No component report tables existfor the indicated report.

Action: Use the Report Definer to define thereport tables you want to include in theindicated report.

S6BTR076ENo report fields defined for report table

Source: TDS

Explanation: There are no report fields definedfor the indicated report table.

Action: Define some report fields for theindicated report table, or remove the reporttable name from the report definition.

S6BTR077ENo CTABLE found for report table

Source: TDS

Explanation: The table definition for theindicated report table cannot be found.

Action: Define the required report table.

S6BTR079EReport CTABLE too large for virtual report

Source: TDS

Explanation: If the Data Object Brokerparameters CTABLESIZE and XTABLESIZEare both set to 31, the definition of theindicated report is too complex. In otherwords, there are too many report tables,report fields, or literals for this report.

Action: Ensure the Data Object BrokerParameters CTABLESIZE ANDXTABLESIZE are set to 31. If the problem stilloccurs, decrease the number of report fieldsand literals for this report.

S6BTR082EUnicode Field length must be even

Source: TDS

Explanation: The length of a Unicode fieldcannot be an odd number.

Action: Correct the definition of the Unicodefield.


| 491

TS: TDS

S6BTS000ETDS internal system error detected

Source: TDS

Explanation: An internal error has unexpectedlyoccurred, possibly due to databasecorruption.


S6BTS001ETable relocation command issued against anon-TDS table

Source: TDS

Explanation: The Object Service Broker gatewayfor external data failed to store the ObjectService Broker table definition. The mainreason for this is that the table storage poolsize (POOLSIZE) is not large enough.

Action: Restart gateway with a larger POOLSIZEparameter value.

S6BTS002ETable relocation request; target segment sameas current

Source: TDS

Explanation: The TABLE MOVE function wasissued to relocate at table to the segmentwhere it already resides.

Action: Ensure that the target segment isdifferent from the current segment in whichthe table resides.

S6BTS003ERTIX search failed during table relocate request- PG#

Source: TDS

Explanation: The Object Service Broker gatewayfor external data received a request that itcannot process. This is a symptom of aversion mismatch; Object Service Brokerdoes not support unqualified deletes.

Action: Ensure that the Object Service Broker andgateway release levels are compatible. If thisdoes not resolve the problem, contact TIBCOSupport.

S6BTS004ERTIX search failed during table relocate request- name

Source: TDS

Explanation: The Object Service Broker table thatmaps the external Fail Safe Level-1transaction database is not defined correctly.

Action: Correct the table definition.


492 |

S6BTS005EExpected SIT page not found for tablerelocation request

Source: TDS

Explanation: The interface routine between theObject Service Broker external gateway andthe external data gateway could not beloaded or is not valid.

Action: Specify a valid value forEXTERNALROUTINE configurationparameter.

S6BTS006EInvalid page type found during table relocationprocess

Source: TDS

Explanation: The indicated table name is not avalid Object Service Broker table name.

Action: Specify a valid Object Service Brokertable name for the external Fail Safe level-1transaction database (TRXDB).

S6BTS007ETable relocation requested on table with SIXentries

Source: TDS

Explanation: The Object Service Broker gatewayfor external data failed to acquire and/orinitialize the table definition storage poolspecified on the POOLSIZE parameter.

Action: Reduce POOLSIZE value or increaseavailable memory.

S6BTS008ERTIX branch lost during table relocationprocessing

Source: TDS

Explanation: The Object Service Broker gatewayfor external data has ended.


S6BTS009ETable relocation requested on table with data

Source: TDS

Explanation: The gateway session failed toconnect to the Data Object Broker.

Action: Check previous messages and DataObject Broker log for more information. Fixthe problem and try again.

S6BTS010ERTIX entry found on target segment in tablerelocation

Source: TDS

Explanation: During TABLE MOVE function fora table, the same table name was found in thetarget segment's resident table index. This isdue to a database corruption.

Action: Ensure that the target segment isproperly reformatted or restored correctlyfrom a backup. Contact TIBCO Support.


| 493

S6BTS011ETable relocation requested on system table

Source: TDS

Explanation: While attempting to build theObject Service Broker occurrence from theexternal occurrence or vice versa, an errorwas encountered. The extension to thismessage gives more detail.

Action: Correct the table definition or the data.

S6BTS012EFIELDS table row format error

Source: TDS

Explanation: The initialization of the ObjectService Broker gateway for external datafailed. Previous messages give moreinformation.

Action: Correct the initialization error and restartthe gateway.


494 |

TW: TDS

S6BTW001ETable name not found in the resident tableindex;

Source: TDS



S6BTW003EUnexpected page type found in CTABLE build;

Source: TDS



S6BTW005EHighest level index updated for table "%"

Source: TDS

Explanation: The highest supported level of anindex has been updated. This could be eithera primary or secondary index. This messageis also recorded in table @CRITICALMSGS.

Action: The table listed in this message isapproaching its maximum size for an index.The systems administrator should take stepsto reduce the amount of data currently in thetable. Failure to take action may result in thesystem being unable to insert more data rowsinto the table.

A copy of this message is saved in the@CRITICALMSGS table. Contact the systemadministrator to review the@CRITICALMSGS table and take action forany critical messages saved in it.

S6BTW006ETable @CRITICALMSGS is full

Source: TDS

Explanation: The table @CRITICALMSGS is full.No more critical messages can be written to ituntil some of the current entries are deleted.

Action: Contact the system administrator toreview the messages stored in@CRITICALMSGS and to delete those forwhich action has been taken.

S6BTW007ETable @CRITICALMSGS is not correctlydefined

Source: TDS

Explanation: Either table @CRITICALMSGS isnot defined or its root page is invalid.



| 495

TY: ostty Client

S6BTY001EUnknown host: %

Source: ostty Client

Explanation: The host name of the osMonprocess to which the ostty process isattempting to connect could not be found.

Action: Change the MONHOST and/or theMONNAME parameter so that a valid hostname is used by the ostty process when itattempts to connect to your osMon process.

S6BTY002ECannot initialize TTY client terminal


Explanation: An attempt to initialize an osttyterminal failed.


S6BTY003ECannot resize TTY client terminal


Explanation: An attempt to resize an osttyterminal failed.


S6BTY004ETTY client ABENDED


Explanation: An ostty process abended.

Action: Examine the accompanying log messagesto determine the reason for the abend. If theproblem persists, contact TIBCO Support.

S6BTY005ETTY connection lost


Explanation: The connection between the osttyprocess and the osee process was lost.



496 |

UA: DOB Application Tasks

S6BUA002EAbort, cannot query/commit while offline

Source: DOB Application Tasks

Explanation: A transaction was aborted becausethe Data Object Broker is offline.


S6BUA003EAbort, cannot query/commit during startup


Explanation: A transaction was aborted becausethe Data Object Broker is still in the processof starting up.


S6BUA004EAbort, cannot commit while quiesced


Explanation: A transaction was aborted becausethe Data Object Broker is quiesced.

Action: Retry the connection.

S6BUA005EAbort, cannot query/commit during shutdown


Explanation: A transaction was aborted becausethe Data Object Broker is in the process ofshutting down.


S6BUA006EAbort, Data Object Broker stopping due to error


Explanation: A transaction was aborted becausethe Data Object Broker is abending.

Action: Peruse the Data Object Broker log forpreviously occurring messages that maymore explicitly diagnose the nature of theerror.

S6BUA010EUnable to initialize European language support


Explanation: The Data Object Broker was unableto initialize European code page support forTDS. This message may indicate a DataObject Broker internal problem.

Action: Contact TIBCO Support. Be prepared tosubmit a copy of the Data Object Broker logfile and any core file produced as a result ofthis problem.


| 497

S6BUA011EUnable to initialize lock manager


Explanation: The Data Object Broker was unableto initialize the Lock Manager. This messagemay indicate a Data Object Broker internalproblem.


S6BUA012E'%': no such peer


Explanation: The name of the node identified inthe message is not known to your local node.

Action: Check the spelling of the node name inthe application. If it correctly matches thenode name specified by the remote peer, thelookup failure indicates that initialconnection from the local to the remote peerhas not yet been established.

S6BUA013ENo available connections to '%'


Explanation: A distributed transaction is unableto proceed because all connections to thespecified peer are in use.

Action: If this problem occurs frequently, youmay need to define more connections to thepeer by updating the appropriate PEERSparameter in the crparm file.

For more information, refer to the ObjectService Broker Installation and Operationsfor Windows and Solaris manual.

S6BUA014W'%' has exceeded maximum resources for stream%


Explanation: The user has attempted to acquiremore than the allowable maximum numberof distributed resources (gateways or peers)for the stream. The transaction is aborted.

Action: Change the application so that it involvesno more than the maximum allowablenumber of service providers at each nestingof the transaction.

S6BUA015E% service unavailable for user % on %


Explanation: A request for a gateway/server ofthe indicated type and Server ID has failedbecause of lack of availability. Either there areno gateways/servers of this type/IDcombination logged on or they are allcurrently engaged in other transactions.

Action: Wait for the service to become availableor, if the problem is chronic, ask the ObjectService Broker system administrator to startmore gateways/servers of the desiredtype/ID combination.


498 |

S6BUA019WLock interference on stream %


Explanation: Object Service Broker protocolerror. The Execution Environment attemptedto start a new transaction withoutterminating the current transaction that isusing this stream. Logical resources remainlocked by the previous stream.

Action: The user may have to log off to re-synchronize the session.

S6BUA020IPeer user '%' logged on from '%'%


Explanation: A user (client) connection from thespecified peer Data Object Broker has beenestablished.


S6BUA021IUser '%' logged on from '%'%


Explanation: An Execution Environmentconnection has been established andaccepted from the specified terminal ID (tty)or remote machine name. An origin tag ofUNKNOWN is displayed if the session isstarted locally from a shell script.


S6BUA022I% server % logged off from '%'


Explanation: A gateway of the specified type andID has disconnected from the Data ObjectBroker and will thus no longer be availablefor work. The message indicates from whichpartner Execution Environment the gatewaywas logged on from.


S6BUA023I% server % logged on from '%'


Explanation: A gateway/server of the specifiedtype and ID has connected to the Data ObjectBroker. The message indicates from whichpartner Execution Environment thegateway/server has logged on.


S6BUA024IUser '%' logged off from '%'


Explanation: The specified client (Peer ObjectService Broker or Execution Environment)has disconnected from the Data ObjectBroker.



| 499

S6BUA025IPeer user '%' logged off from '%'


Explanation: A user (client) connection from thespecified peer Object Service Broker DataObject Broker has been terminated.


S6BUA026IServer shutdown request: No servers match %'%'


Explanation: This message indicates that thegateway/server you requested to shutdownwas not started. You may have specified thename incorrectly.

Action: Specify the shutdown request correctly.

S6BUA027EServer shutdown request: Wildcard '*' must bepreceded by at least one character


Explanation: You can use wildcards in thegateway/server shutdown request, as longas the gateway/server name in the requeststarts with a character.

Action: Specify the shutdown request correctly.

S6BUA028ERemote request rejected from peer session '%'


Explanation: Peer to peer to peer transactionpaths are not currently permitted in ObjectService Broker. A message coming from aPeer Data Object Broker that is bound for athird Data Object Broker is rejected.

Action: Redesign the distributed application.

S6BUA029I'%' logon failed, user limit exceeded


Explanation: A logon attempt from a client wasrejected because all of the allocated usercontrol tables are held by other users.

Action: Increase the MAXUSERS parameter inthe crparm file and restart the Data ObjectBroker to allocate a greater number of usercontrol tables. It is worth noting that nativeExecution Environments, inbound peerconnections, and distributed gateway ruledriver connections, all require user controltables and should be considered whensetting the MAXUSERS parameter.

S6BUA030I'%' logon failed, server limit exceeded


Explanation: An incoming gateway connectionhas been rejected by the Data Object Brokerbecause all pre-allocated gateway controltables are occupied by other gatewayconnections.

Action: Increase the MAXDBMS parameter in thecrparm file and restart the Data Object Brokerto allocate a greater number of gatewayspaces. It is worth noting that each expected


500 |

gateway connection, be it a distributedgateway or a DBMS gateway, should beconsidered when setting the MAXDBMSparameter.

S6BUA031IUnrecognized peer login from '%', rejected


Explanation: Another Data Object Brokerattempted to connect to this Data ObjectBroker. There is, however, no correspondingPEERS parameter for that Data ObjectBroker, therefore the connection is rejected.

Action: If two Data Object Brokers are to be peersthen each must have a PEERS parameter torefer to the other. Either the PEERSparameter at the other Data Object Brokermust be deleted, or a PEERS parameter mustbe added at this Data Object Broker. Restartany Data Object Broker at which a parameterchange is made.

S6BUA032IOperator '%' logged on from '%'%


Explanation: This message, displayed when anoperator session connects, indicates theuserid of the session, the terminal or remotemachine name, and the IP address fromwhich it originates.


S6BUA033IOperator '%' logged off from '%'


Explanation: This message, displayed when anoperator session disconnects, indicates theuserid of the session and the terminal orremote machine from which it originates.


S6BUA034EContingency log is undefined, transactionaborted


Explanation: A distributed transaction operatingat Fail Safe level 1 or 2 was aborted becausethere is no contingency log defined on theData Object Broker.

Action: Have your Object Service Broker SystemAdministrator format a contingency logusing the hrntlfcl utility, add the definition tothe $Huron/database/dbdef file, and restartthe Data Object Broker.

S6BUA035EUnable to initialize new Contingency Log entry


Explanation: A transaction operating at Fail Safelevel 1 or 2 was aborted because a request fora new contingency log entry (slot) wasunable to be fulfilled.

Action: The contingency log is probably full. TheObject Service Broker administrator shouldeither manually commit or abort contingenttransactions held in the log using thehrntladm administration utility. If thisproblem is a frequently recurring one, thecontingency log should be reformatted witha greater number of slots.


| 501

S6BUA036EPartner '%' multiply logged on, rejected


Explanation: Each distributed gateway/server(API) must specify a rule driver (NEE)partner. The gateway/server connection isrejected if the partner cannot be uniquelyidentified and logically bound to thegateway/server connection.

Action: Start another distributedgateway/server. If the problem persists withthis subsequent attempt, contact TIBCOSupport.

S6BUA037EPartner '%' not found, logon rejected


Explanation: If a connecting distributedgateway/server (API) specifies as its partnera nonexistent userid, the gateway/serverconnection is rejected.

Action: Start another distributedgateway/server. If this subsequent attemptfails, contact TIBCO Support.

S6BUA038ILogon rejected, system is not online


Explanation: You cannot presently log on to thesystem.

Action: Try to log on again when the system isonline.

S6BUA040IUnable to support Fail Safe level % connectionfrom '%', Contingency Log is undefined


Explanation: Your request for Fail Safe level-1 orlevel-2 processing cannot be supportedbecause there is no contingency log defined.

Action: Have your Object Service Broker systemadministrator format a contingency log usingthe hrntlfcl utility, add the definition to the$Huron/database/dbdef file, and restart theData Object Broker.

S6BUA041IService trace for user %:% enabled


Explanation: You requested that all servicemessages to the Data Object Broker on behalfof the specified user be recorded in the DataObject Broker log.


S6BUA042IService trace for user %:% disabled


Explanation: You requested that all servicemessages to the Data Object Broker on behalfof the specified user no longer be recorded inthe Data Object Broker log.



502 |

S6BUA043EService trace for user %s cannot beenabled/disabled; userid not connected orambiguous


Explanation: You requested that messages to theData Object Broker be recorded or stoppedfrom being recorded. This cannot be donebecause the userid in the command isincorrect.

Action: Submit the command with a correctuserid.

S6BUA047IServer commit failure detected, transactionaborted


Explanation: An acquired service provider wasunable to commit the requested updates andthe transaction was subsequently aborted.

Action: Retry the application.

S6BUA054IIn-doubt resolved, TDS commit issued


Explanation: An outstanding in-doubttransaction has been resolved and thepending TDS updates have been submittedfor processing.


S6BUA055IIn-doubt resolved, TDS request aborted


Explanation: An outstanding in doubttransaction has been resolved and thepending TDS updates have been rejected.


S6BUA057ITDS request failed, transaction held in doubt


Explanation: Local TDS processing has failedand the transaction will be held in doubtuntil such time as the TDS updates can becommitted.


S6BUA060EGroup sync failed - updated server lost


Explanation: An updated service provider waslost during the commit phase. Thetransaction will be aborted.


S6BUA062EGroup sync failed - mixed commit protocols


Explanation: A transaction involving multipleservice providers was aborted due toincompatible Fail Safe level specifications.

Action: Redesign the application to conform toFail Safe restrictions as outlined in theBackup and Recovery manual.


| 503

S6BUA070I'%' logon from '%' rejected - MAXPEERUSERSexceeded


Explanation: The peer tried to initiate too manyinbound connections - the number ofinbound connections defined for that peer incrparm table has been exceeded.

Action: Change crparm file on either side ofconnection - increase maxinbound on thePEER entry of the local crparm OR decreaseoutbound on the corresponding PEER entryof the Data Object Broker trying to connect.

S6BUA071I'%' logon from '%' rejected - MAXDBMSexceeded


Explanation: The logon command is rejected.The maximum number of external databasesare already in use.

Action: Restart the Data Object Broker with anincreased MAXDBMS parameter in thecrparm file.

S6BUA072I'%' logon from '%' rejected - MAXUSERSexceeded


Explanation: You cannot log on because themaximum number of users are alreadylogged on.

Action: Restart the Data Object Broker with anincreased MAXUSERS parameter in thecrparm file.

S6BUA073I'%' logon form '%' rejected - peer servers exceedtotal inbound peer connections


Explanation: Number of peer server that canconnect is limited to the number of allpossible inbound peer connections.

Action: Decrease the number of peer serversdefined for the Execution Environment orincrease the maximum number of inboundpeer connections.

S6BUA074I'%' logon from '%' rejected - MAXOPERATORSexceeded


Explanation: Your logon request is rejectedbecause the maximum number of operatorsis already logged on.

Action: Restart the Data Object Broker with anincreased MAXOPERATORS parameter inthe crparm file.

S6BUA075EInvalid connection information detected


Explanation: The connection to the Data ObjectBroker failed because of incorrectinformation in the connect message.

Action: Possible causes are a missing USERIDparameter or an Object Service BrokerActiveX Adapter client, SDK (C/C++) client,or SDK (Java) client connecting directly to theData Object Broker. Check whether the SDK(C/C++) client or the SDK (Java) client isusing a Data Object Broker port instead of theosMon port.


504 |

UB: DOB File Tasks

S6BUB001ESegment '%' undefined

Source: DOB File Tasks

Explanation: An attempt to access a segmentfailed because the segment is not defined inthe database definition file, dbdef.

Action: If this error occurs during redoprocessing then the database definition haschanged between time of failure andrecovery. Restore the missing definition andrestart the Data Object Broker.

S6BUB002ISegment '%' now online


Explanation: The segment has successfully beenbrought online.


S6BUB003ISegment '%' now offline


Explanation: The segment has successfully beenbrought offline.


S6BUB006EUnable to complete checkpoint, page=%undefined


Explanation: A page in the checkpoint has asegment number that is undefined. Thismessage may indicate a Data Object Brokerinternal problem.


S6BUB007EUnable to use journals, both are active


Explanation: At start up the Data Object Brokercould not determine which journal wasactive last.

Action: If the Data Object Broker was previouslyshut down successfully then simply reformatboth journals and the redolog. Otherwise,determine which journal was active last andformat the other journal. If this fails, reformatboth journals and the redolog.

S6BUB008WCheckpoint recovery started


Explanation: The Data Object Broker terminated

abnormally during its last checkpoint. Thecheckpoint is being reapplied to thePagestore to ensure database integrity.



| 505

S6BUB009ICheckpoint recovery successful, checkpoint=%


Explanation: Checkpoint recovery wassuccessful, the next checkpoint number isshown.


S6BUB010EUnable to continue, segment '%' required forsystem operation


Explanation: At start up the Data Object Brokerwas unable to bring segment 0 online. Thissegment contains the MetaStor and isessential for TIBCO(r) Object Service Brokeroperation.

Action: Look for previous error messages thatmay indicate the specific problem.

S6BUB011ECheckpoint recovery failed


Explanation: At start up a problem occurredduring checkpoint recovery and the DataObject Broker was not able to reapply thecheckpoint to the Pagestore.

Action: Look for any previous error messagesthat may indicate the specific problem.

S6BUB012WDboffline request deferred till checkpoint %,segment ID=% in use


Explanation: A segment can be varied offlineonly after all the changes to the segment havebeen propagated, which should happen afterthe specified checkpoint ends.

Action: Wait until the specified checkpoint isdone, or force it to start.


506 |

UC: DOB Communications

S6BUC001EInbound connection rejected, system resourceshortage

Source: DOB Communications

Explanation: A connection was established to theData Object Broker but it was not able to starta process to handle the connection. Thisproblem indicates that there is a systemmemory shortage or an excess number ofprocesses on the system.

Action: If this problem occurs regularly, thesystem administrator needs to address theresource shortage in terms of system load,system configuration, and machine capacity.

S6BUC002EUnable to allocate % bytes from system heap


Explanation: The system has a temporaryshortage of real memory.

Action: If this problem occurs regularly, thesystem administrator needs to address theresource shortage in terms of system loadand machine capacity.

S6BUC013IConnection(%) to '%' established


Explanation: An outbound connection to a peerData Object Broker was established.


S6BUC014IConnection(%) to '%' terminated


Explanation: An outbound connection to a peerData Object Broker was terminated.


S6BUC016EPeer user '%' failed to logon to node '%'


Explanation: You are trying to connect to aremote Data Object Broker and its name isnot recognized in the crparm file, or thehuron.dir file may have incorrectinformation regarding the node name of theremote Data Object Broker. If these arecorrect, the remote Data Object Broker maynot have started yet.

Action: If necessary, correct either the huron.dirinformation for the local Data Object Broker,or the PEERS parameter information in thecrparm file on the remote node.

S6BUC030EUnable to read from environment initializationfile '%'


Explanation: A file system error occurred whilereading from the file.

Action: Verify that the file is a valid text file andthat it has not been damaged in some way.


| 507

S6BUC031ELine % of environment initialization file '%'exceeds % characters


Explanation: A line in the file was longer than theprogram expected.

Action: Edit the file and ensure that the lengths ofall the lines in the file are within the limitstated.

S6BUC032EUnable to add setting '%' to environment


Explanation: The hrncomt process, attempting tomodify its own environment, was unable todo so. The likely cause of the failure is ashortage of real memory on the system, or anexcess of existing environment variablesettings.

Action: If the environment in which the hrncomtprocess is started has a large number ofenvironment variables set, consider reducingthe number of settings, if this is possible.

S6BUC033EUnable to determine transport protocol,environment variable 'HRNCOMT' not set


Explanation: The hrncomt process depends onan environment variable HRNCOMT toindicate which transport protocol it is tolisten on. For TCP/IP, this setting should be

HRNCOMT=TCPIP. This setting should bein the hrncomt environment initialization filecalled hrncomt.env, situated in the samedirectory as the hrncomt binary.

Action: Ensure that hrncomt environmentinitialization file sets the HRNCOMTenvironment variable.

S6BUC034EInvalid value '%' assigned to environmentvariable 'HRNCOMT'


Explanation: The value assigned to theHRNCOMT environment variable wasinvalid. The value should be TCPIP. Theproblem is likely the setting of HRNCOMTin the hrncomt environment initializationfile. This file is called hrncomt.env and it islocated in the same directory as the hrncomtbinary.

Action: Ensure that the hrncomt environmentinitialization file has the settingHRNCOMT=TCPIP.

S6BUC035EUnable to open environment initialization file'%'


Explanation: A file system error occurred whileattempting to open the file.

Action: Ensure that the file exists and that itsaccess permissions enable the Data ObjectBroker to read it.


508 |

UL: Data Object Broker (DOB)

S6BUL001EInvalid file/path name, longer than % characters

Source: Data Object Broker (DOB)

Explanation: A path name, supplied as anargument for a command line option, islonger than the expected maximum length.

Action: Verify that the path name is correct.

S6BUL002EInvalid parameter override, longer than %characters


Explanation: The length of a parameter overridestring exceeds the maximum lengthexpected.

Action: Use abbreviated parameter names toshorten the length of the command lineparameter override.

S6BUL003EInvalid option '%'


Explanation: An option encountered on thecommand line was not of the form -X, whereX is a single character. The user may haveattempted to combine options (notsupported) or may have omitted the whitespace between the option and the optionargument.

Action: Using the explanation as a guide, enterthe option correctly.

S6BUL004EUnrecognized option '%'


Explanation: The option specified is notsupported by this command.

Action: Verify the command syntax.

S6BUL005EMissing argument for command line option '%'


Explanation: The option specified on thecommand line expects an argument tofollow. The expected argument was missingfrom the command line.


S6BUL006EToo many command line arguments


Explanation: The user has specified morearguments on the command line than wereexpected.



| 509

S6BUL007EUnrecognized keyword '%'


Explanation: While scanning a configuration fileor a command line argument, an invalidkeyword was encountered. A subsequentmessage may identify where the problemoccurred.

Action: Verify the configuration file or commandsyntax.

S6BUL008I% dump created in file %


Explanation: A dump has been created in the filenamed.


S6BUL009EUnable to write to file <filename>


Explanation: The device is either full orotherwise unavailable.

Action: The system administrator should firstcheck the status of the file and of the filesystem. If the problem recurs, contactSupport.

S6BUL010EInvalid parameter value for '%', range forinteger is % to %


Explanation: While scanning a configuration fileor a command line parameter override, aninteger value was encountered that was outof the expected range for that value. Asubsequent message should identify wherethe problem occurred.

Action: Correct the value so that it falls withinthe expected range.

S6BUL011EInvalid parameter value for '%', must be % to %characters in length


Explanation: While scanning a configuration fileor a command line parameter override, aparameter value was encountered that wasshorter or longer than expected. Asubsequent message should identify wherethe problem occurred.

Action: Correct the parameter value so that itslength falls within the expected range.

S6BUL012EInvalid parameter override


Explanation: A problem was encountered whilescanning a command line parameteroverride. A previous message should haveidentified the specific problem.

Action: Review the previous messages todetermine the appropriate actions to take.


510 |

S6BUL013EUnable to open file '%'


Explanation: A file system error occurred whileattempting to open the file.

Action: Ensure that the file exists and that itsaccess permissions enable it to be read.

S6BUL014EUnable to read from file '%'


Explanation: A file system error occurred whilereading from the file.

Action: Verify that file is a valid text file and thatit has not been damaged somehow.

S6BUL015ELine % of file '%' exceeds % characters


Explanation: A line in the file was longer than theexpected maximum length.

Action: Edit the file to ensure that the lengths ofall the lines are within the limit specified.

S6BUL016EInvalid parameter assignment, line % of file '%'


Explanation: An error was encountered whilescanning the file. A previous message shouldindicate the specific problem.

Action: Edit the file to correct the specificproblem.

S6BUL017EUnable to close file '%'


Explanation: A file system error occurred whileclosing the file.


S6BUL018EUnable to determine path from environmentvariable 'HURON' or '-h' option


Explanation: The HURON environment variablehas not been set and no override wassupplied on the command line.

Action: Ensure that the HURON environmentvariable is properly set, or indicate theinstallation path on the command line withthe -h option.

S6BUL019EUnable to update file header of file '%'


Explanation: During the format of a page file,control information was written to the filebut it cannot be read or it cannot be verified.

Action: A previous error may indicate a morespecific problem. Otherwise this error wouldseem to indicate an I/O error on the disk.


| 511

S6BUL020EUnable to verify file header of file '%'


Explanation: Upon opening a page file, thecontrol information was unable to be read orunable to be verified. A previous messageshould indicate a more specific problem.

Action: Review previous messages to determinethe appropriate actions to take.

S6BUL027EUnable to allocate % bytes from system heap



Action: If this problem occurs regularly, thesystem administrator needs to address theresource shortage in terms of system load,system configuration, and machine capacity.

S6BUL028EUnable to lock journal %, online or in use


Explanation: An attempt to lock a journal forformatting failed because the journal isalready in use by the Data Object Broker orby another Object Service Broker utility.

Action: If the Data Object Broker is running itshould be stopped to format either journal. Ifthe journal is being used by another ObjectService Broker utility then you must wait forthe utility to finish.

S6BUL029EUnable to use journal %, control informationunreadable


Explanation: An attempt to open a journal failedbecause control information at the beginningof the journal is not valid. This is likely due toa loss of data on the disk.

Action: Refer to the Object Service Broker Backupand Recovery for Windows and Solarismanual.

S6BUL030EUnable to open journal %, online or in use


Explanation: An attempt to open a journal failedbecause the journal is already in use by theData Object Broker or by an Object ServiceBroker utility.

Action: If the Data Object Broker is running thenthe journal cannot be used until the DataObject Broker shuts down or a journal spinoccurs. If the journal is being used by anObject Service Broker utility then you mustwait for the utility to finish before startingthe Data Object Broker or running anotherutility.

S6BUL031EUnable to use journal %, page file unformatted


Explanation: An attempt to open a journal failedbecause the journal has not been formatted.

Action: Format the journal.


512 |

S6BUL032ENo free buffers in page or CTABLE handle pool


Explanation: The Resident Page/CTABLEManager has run out of handles forpages/CTABLEs. This message may indicatea Data Object Broker internal problem.


S6BUL033WNo free buffers in resident page pool


Explanation: The Resident Page Manager hastemporarily run out of buffers for pages. Thisis likely due to a burst of update activity thatconsumed buffers faster than they could bewritten to disk, or a transaction thatattempted to update more buffers than theResident Page Manager contained.

Action: Consider increasing the value for theRESIDENTPAGES Data Object Brokerparameter. Consult the Backup and Recoverymanual.

S6BUL034EUnable to begin checkpoint, previouscheckpoint in progress


Explanation: An internal Data Object Brokerrequest to start a new checkpoint has failedbecause a checkpoint is already in progress.This message may indicate a Data ObjectBroker internal problem.


S6BUL035EUnable to create semaphore, IPC key=%,num=%, perm=%


Explanation: An attempt to create a semaphorefailed. The specific reason for the failure isindicated by the error number value thatshould be part of this message.

The most likely causes of failure are either ashortage of defined semaphores, or an IPCkey conflict with another application.

Action: The system administrator may be neededto help understand and fix the problem. Ashortage of defined semaphores will requireupdates to the Solaris kernel configuration. Aconflict with another application may requirethat a new IPC key be chosen for this DataObject Broker and the HCS configuration fileupdated.


| 513

S6BUL036EUnable to remove conflicting semaphore, IPCkey=%


Explanation: An attempt to remove a conflictingbut unused semaphore has failed. Thespecific reason for the failure is indicated bythe errno value that should be part of themessage. A likely cause of the problem is thatthe semaphore in question was created by adifferent userid.

Action: The system administrator may be neededto help understand and fix the problem. Toremove a semaphore manually the ipcrmcommand can be used, assuming the userhas the authority to do so.

S6BUL037EUnable to remove semaphore, IPC key=%


Explanation: An attempt to remove a semaphorehas failed. The specific reason for the failureis indicated by the errno value that should bepart of this message.

Action: The system administrator may be neededto help understand and fix the problem. Toremove a semaphore manually the ipcrmcommand can be used, assuming the userhas the authority to do so.

S6BUL039EUnable to create shared memory, IPC key=%,size=%, perm=%


Explanation: An attempt to create sharedmemory has failed. The specific reason forthe failure is indicated by the errno value thatshould be part of this message. The most

likely causes of failure are either a shortage ofdefined shared memory, a size that exceedssystem configured limits, or an IPC keyconflict with another application.

Action: The system administrator may be neededto help understand and fix the problem. Ashortage of defined shared memory or a sizeproblem will require updates to the kernelconfiguration.

A conflict with another application mayrequire that a new IPC key be chosen for thisData Object Broker and the HCSconfiguration file updated.

S6BUL040EUnable to remove conflicting shared memory,IPC key=%


Explanation: An attempt to remove conflictingbut unused shared memory has failed. Thespecific reason for the failure is indicated bythe errno value that should be part of themessage. A likely cause of the problem is thatthe shared memory in question was createdby a different userid.

Action: The system administrator may be neededto help understand and fix the problem. Toremove shared memory manually the ipcrmcommand can be used, assuming the userhas the authority to do so.

S6BUL041EUnable to attach shared memory, IPC key=%,address=%, flags=%


Explanation: An attempt to attach sharedmemory has failed. The specific reason forthe failure is indicated by the errno value thatshould be part of the message. The likely


514 |

causes of the problem are either an invalidvalue for the Data Object Broker parameterSHAREDMEMADDR, or two Data ObjectBrokers on the same system that are peersand that have the same value forSHAREDMEMADDR.

Action: The system administrator may be neededto help understand and fix the problem. If theproblem is due to an invalidSHAREDMEMADDR value, consult theInstallation and Operations manual.

Normally the default forSHAREDMEMADDR works on any system.If the problem is related to peer Data ObjectBrokers on the same system, change theSHAREDMEMADDR parameter for one ofthe Data Object Brokers.

Add a multiple of SHAREDMALIGN togenerate a new SHAREDMEMADDR value.

S6BUL042EUnable to perform semaphore operation, id=%


Explanation: An attempt to use a semaphore hasfailed. The specific reason for the failure isindicated by the errno value that should bepart of the message. A likely cause of theproblem is a shortage of defined semaphoreundo structures in the system.

Action: The system administrator may be neededto help understand and fix the problem. Ashortage of defined semaphore undostructures will require updates to the kernelconfiguration. Otherwise the message mayindicate a Data Object Broker internalproblem. Contact TIBCO Support. Beprepared to submit a copy of the Data ObjectBroker log file and any core file produced asa result of this problem.

S6BUL044EUnable to get shared memory, IPC key=%


Explanation: An attempt to get shared memoryhas failed. The specific reason for the failureis indicated by the errno value that should bepart of the message.

Action: The system administrator may be neededto help understand and fix the problem.

S6BUL045EUnable to attach shared memory, unrecognizedheader, IPC key=%


Explanation: Shared memory was attached but itwas not identifiable as Object Service Brokershared memory. This problem may indicatean IPC key conflict with another application.

Action: The system administrator may be neededto help understand and fix the problem. If theproblem is due to an IPC key conflict a newIPC key must be chosen for this Data ObjectBroker and the HCS configuration fileupdated.

S6BUL046EUnable to query shared memory, IPC key=%


Explanation: The specific reason for the failure isindicated by the errno value that should bepart of the message.

Action: The system administrator may be neededto help understand and fix the problem.


| 515

S6BUL047EUnable to remove conflicting shared memory,in use by other processes, IPC key=%


Explanation: A shared memory remnant cannotbe removed because one or more processesare still attached to it. This may indicate anIPC key conflict with another application.The most likely explanation, however, is thatthe Data Object Broker had been killed orhad abended without the opportunity toclean up.

Action: Use the command "hrncr kill" to force aclean up of all Data Object Broker processesand shared resources. If the same problemoccurs, use the ipcrm command to removethe conflicting shared memory manually.

S6BUL048EFile is formatted for % data


Explanation: You are trying to use an ObjectService Broker file formatted for one type ofObject Service Broker data as the type ofObject Service Broker data specified in themessage (e.g., a Journal file is being accessedas if it were a page file of the segment).

Action: Adjust your links accordingly.

S6BUL049EUnable to detach shared memory, IPC key=%


Explanation: An attempt to detach sharedmemory has failed. The specific reason forthe failure is indicated by the errno value thatshould be part of the message.

Action: The system administrator may be neededto help understand and fix the problem.Otherwise contact TIBCO Support.

S6BUL050EUnable to remove shared memory, IPC key=%


Explanation: An attempt to detach sharedmemory has failed. The specific reason forthe failure is indicated by the errno value thatshould be part of the message.

Action: The system administrator may be neededto help understand and fix the problem.Otherwise contact TIBCO Support.

S6BUL051EUnable to initialize page manager, checkparameters 'RESAGE' and 'RESIDENTPAGES'


Explanation: The Resident Page Manager failedto initialize. The most likely problem isinvalid values for the parameters mentioned.RESIDENTPAGES must be at least 3.RESAGE must not be greater thanRESIDENTPAGES.

Action: Verify the parameter settings in the DataObject Broker parameter file. Adjust thevalues if necessary. If the parameter valuesare valid and the problem persists, contactTIBCO Support.


516 |

S6BUL052EUnable to initialize CTABLE manager, checkparameters 'CTABLESIZE', 'CTABAGE', and'CTABRESIDENT'


Explanation: The Resident CTABLE Managerfailed to initialize. The most likely problem isinvalid values for the parameters mentioned.CTABRESIDENT must be at least 3.CTABAGE must not be greater thanCTABRESIDENT. CTABLESIZE must be amultiple of 4.

Action: Verify the parameter settings in the DataObject Broker parameter file. Adjust thevalues if necessary. If the parameter valuesare valid and the problem persists, contactTIBCO Support.

S6BUL053E'%' required in database definition


Explanation: An entry in the dbdef file is missinga required attribute like NAME or TYPE. Asubsequent message should identify wherethe problem occurred.

Action: Correct the invalid entry in the dbdef file.

S6BUL054W'%' is only valid on a segment definition,ignored


Explanation: An entry in the dbdef file for theredolog or a journal contained anunnecessary attribute.

Action: Change the dbdef attribute.

S6BUL055EInvalid database definition in line % of file '%'


Explanation: Identifies the line at which aninvalid entry was detected. A previousmessage should indicate the specific problemencountered.

Action: Correct the invalid entry in the dbdef file.

S6BUL056WMaximum number of database definitions read(%) at line % of file '%'


Explanation: The dbdef file contains more than260 entries. Since there can be 256 segmentsdefined, a contingency log, a redo log, andtwo journals, there can be no more than 260definitions in the dbdef file.

Action: Remove any extra or duplicate entries inthe dbdef file.

S6BUL057EDuplicate name '%' in database definitions


Explanation: Two of the entries in the dbdef filehave the same NAME attribute.

Action: Ensure that each entry in the dbdef filehas a unique NAME attribute.


| 517

S6BUL058EDuplicate id '%' in database definitions


Explanation: Two of the segments defined in thedbdef file have the same ID attribute. If an IDis not explicitly assigned then it defaults to 0.

Action: Ensure that each segment defined in thedbdef file has a unique ID attribute and thatonly the MetaStor segment has ID 0.

S6BUL059EDuplicate database definitions, more than one%


Explanation: More than one redolog,contingency log, or set of journals has beendefined in the dbdef file.

Action: Remove the duplicate definition.

S6BUL060EDatabase definition missing for %


Explanation: A required database definition ismissing in the dbdef file.

Action: Add the required definition to the dbdeffile.

S6BUL061ESegment '%' must be of type 'TDS'


Explanation: The segment must be defined asTYPE=PAGE.

Action: Change the TYPE attribute of thedatabase definition to PAGE.

S6BUL062ESegment '%' must be defined with 'init=yes'


Explanation: The segment must be defined withINIT=YES.

Action: Change the INIT attribute of the databasedefinition to YES.

S6BUL065ESegment '%' undefined


Explanation: The segment is not defined in thedbdef file. If the dbdef file has been changedwhile the Data Object Broker is running, itmust be restarted before the changes takeeffect.

Action: Define the segment in the dbdef file.

S6BUL067ESegment '%' undefined


Explanation: The segment is not defined in thedbdef file. If the dbdef file has been changedwhile the Data Object Broker is running, itmust be restarted before the changes takeeffect.

Action: Define the segment in the dbdef file.


518 |

S6BUL068EUnable to vary segment '%' offline, segmentrequired for system operation


Explanation: A request was made to varysegment 0 offline. Segment 0 is required to beonline at all times while the Data ObjectBroker is running.

Action: Do not vary segment 0 offline.

S6BUL069EUnable to lock redo log, online or in use


Explanation: An attempt to lock the redolog forformatting failed because the redolog isalready in use by the Data Object Broker orby another Object Service Broker utility.

Action: If the Data Object Broker is running itshould be stopped to format the redolog. Ifthe redolog is being used by another ObjectService Broker utility then you must wait forthe utility to finish.

S6BUL070EUnable to use redo log, cannot determine lastcheckpoint


Explanation: The redolog contains an invalidcheckpoint sequence and the Data ObjectBroker cannot determine the last validcommit. This is likely due to a loss of data onthe disk.

Action: Consult the Backup and Recoverymanual.

S6BUL071EUnable to use redo log, required pageunreadable


Explanation: The redolog cannot be read due to aloss of data on the disk.


S6BUL072EUnable to open redo log, online or in use


Explanation: An attempt to open the redologfailed because the redolog is already in useby the Data Object Broker or by an ObjectService Broker utility.

Action: If the Data Object Broker is running thenthe redolog cannot be used until the DataObject Broker shuts down. If the redolog isbeing used by an Object Service Brokerutility then you must wait for the utility tofinish before starting the Data Object Brokeror running another utility.

S6BUL073EUnable to use redo log, page file unformatted


Explanation: An attempt to open the redologfailed because the redolog has not beenformatted.

Action: Format the redolog.


| 519

S6BUL074EUnable to read redo log, inconsistent pageheader info


Explanation: The redolog contains at one or morepages with invalid data and the Data ObjectBroker cannot determine the last validcommit. This is likely due to a loss of data onthe disk.


S6BUL075EUnable to read redo log, message size exceeds %pages


Explanation: The redolog contains a committedtransaction that exceeds the maximumconfigured message size.

Action: Adjust the MSGSIZE parameter in thecrparm file. Normally this value should be 32(for 32 KB).

S6BUL076EUnable to read redo log, message size exceeds %bytes


Explanation: The redolog contains a committedtransaction that exceeds the maximumconfigured message size.


S6BUL077EUnable to write to redo log, message sizeexceeds % bytes


Explanation: An attempt to write a transaction tothe redolog has failed. The size of thetransaction message exceeds the maximumconfigured message size.


S6BUL078ENo free space available in redo log


Explanation: An attempt to write a transaction tothe redolog has failed. There is insufficientspace in the redolog to write the transaction.

Action: Expand the redolog allocation.

S6BUL079EUnable to confirm checkpoint % in redo log, outof sequence


Explanation: An attempt to release transactionsin the redolog has failed. If this problemoccurs during start up then it likely indicatesthat the journals and the redolog are out of


520 |

sync, i.e., the journals were formatted but notthe redolog. If this problem occurs after theData Object Broker is online then it indicatesan internal logic error.

Action: If the problem is due to ajournal/redolog mismatch then format theredolog using the hrntlfrl utility. Otherwisecontact TIBCO Support. Be prepared tosubmit a copy of the Data Object Broker logfile and any core file produced as a result ofthis problem.

S6BUL080EUnable to open segment '%', online or in use


Explanation: An attempt to open a segmentfailed because the segment is already in useby the Data Object Broker or by an ObjectService Broker utility.

Action: If the Data Object Broker is running thenthe segment cannot be used until the DataObject Broker shuts down. If the segment isbeing used by an Object Service Brokerutility then you must wait for the utility tofinish before starting the Data Object Brokeror running another utility.

S6BUL081EUnable to open file % of segment '%'


Explanation: An attempt to open a segment pagefile failed. A previous message shouldindicate the specific problem encountered.

Action: Review previous messages to determinethe appropriate actions to take.

S6BUL082EUnable to close segment '%', offline or in use


Explanation: The segment identified cannot beclosed.

Action: Reenter the command when the segmentbecomes available.

S6BUL083EUnable to close file % of segment '%'


Explanation: A problem occurred whileattempting to close a page file in a segment.A previous message may indicate a morespecific problem.

Action: No action required. If there are otherrelated messages there may be actionsindicated for these messages.

S6BUL084EUnable to lock segment '%', online or in use


Explanation: An attempt to lock a segment pagefile for formatting failed because the page fileis already in use by the Data Object Broker orby another Object Service Broker utility.

Action: If the Data Object Broker is running itshould be stopped to format the page file. Ifthe page file is being used by another ObjectService Broker utility then you must wait forthe utility to finish.


| 521

S6BUL085EUnable to access segment '%', offline or in use


Explanation: The segment identified cannotpresently be accessed.

Action: Try again at a later time.

S6BUL086EUnable to get/put undefined page, page=%


Explanation: An attempt to access a page in asegment failed. The page number is largerthan the number of pages in the page file.

Action: The problem may be caused by a requestfrom a user (using either hrntladm or@PAGE) to see a page that is undefined, inwhich case it can be ignored. Otherwise themessage may indicate a Data Object Brokerinternal problem. Contact TIBCO Support.Be prepared to submit a copy of the DataObject Broker log file and any core fileproduced as a result of this problem.

S6BUL087EInvalid to get/put control page, page=%


Explanation: This message may indicate a DataObject Broker internal problem.


S6BUL088EUnable to get unallocated page, page=%




S6BUL089ENo free pages available in segment '%'


Explanation: An attempt to allocate a new pagein a segment failed. The segment iscompletely full.

Action: The solution to this problem is to expandthe size of the segment, either by addingadditional page files, or expanding theexisting page files. If this problem resultedfrom defining or adding data to a table, youmay consider defining or moving the table toanother segment that has sufficient space.Otherwise, refer to the ApplicationAdministration manual.

S6BUL090EUnable to complete checkpoint, segment '%'offline or in use





522 |

S6BUL091EUnable to complete checkpoint, page=%undefined




S6BUL093IAbort, msgid=%, retcode=%


Action: Review the previous messages in theData Object Broker log to determine theappropriate actions to take.

S6BUL095ENo free buffers in working set pool


Explanation: TDS used all the available workingset buffers while processing a request.

Action: Increase the value for the WORKINGSETparameter in the crparm file.

S6BUL097EAttempt to free buffer not in working set




S6BUL098EUnable to allocate % bytes from session heap


Explanation: TDS used all its available heapwhile processing a request.

Action: Increase the value for the HEAPSIZEparameter in the crparm file.

S6BUL100EUnable to build CTABLE, name='%'


Explanation: An error occurred during theconstruction of a CTABLE. A previous errormessage may indicate the specific problem.This error may indicate that certain criticaltables have inconsistent or invalid data inthem.


S6BUL101EUnable to get CTABLE, name='%'


Explanation: An error occurred during theconstruction of a CTABLE. A previous errormessage may indicate the specific problem.This error may indicate that certain criticaltables have inconsistent or invalid data inthem.



| 523

S6BUL103EUnable to invalidate CTABLE during phase 1,name='%'




S6BUL105EUnable to get free page during phase 1,segment=%




S6BUL108EUnable to hold page during phase 1, page=%




S6BUL109EUnable to get page, page=%


Explanation: A request to read a page from apage file has failed.


S6BUL111EUnable to hold page (deadlock avoidance),page=%


Explanation: Three or more transactions,proceeding in parallel, have shown signs ofpossible deadlock over physical pagecontention. During sync processing atransaction which holds pages that othertransactions are waiting for, may not itselfwait for pages. The transaction that fails isautomatically retried once. If deadlockavoidance fails the transaction a second timethen it is aborted. This problem should rarelyoccur under normal circumstances.

Action: If this message is seen frequently in theData Object Broker log, it may require achange in one or more of the applicationsthat may be running. Even an applicationwith hot spots should experience thisproblem only while processing a highvolume of transactions.


524 |

S6BUL113EAttempt to put/free page not in working set




S6BUL114EUnable to put/free page, inconsistent headerinformation




S6BUL115EUnable to put/free page not held, page=%




S6BUL118EUnable to perform commit during phase 1




S6BUL119EUnable to write to redo log


Explanation: A commit request could not bewritten to the redolog.


S6BUL120ICommit, id=%


Explanation: Indicates that a transaction hasbeen committed. The tracing of commits iscontrolled by the parameter SYNCTRACE inthe Data Object Broker parameter file.


S6BUL121ICommit (intermediate)


Explanation: Indicates that part of a transactionhas committed. The tracing of commits iscontrolled by the SYNCTRACE parameter inthe Data Object Broker parameter file.



| 525

S6BUL122EUnable to use Data Object Broker sharedmemory, abend or invalid state detected


Explanation: A Data Object Broker process hasattached to a running Data Object Broker, butthe state of the Data Object Broker indicatesthat it is abending or is invalid.

This message may simply indicate that aData Object Broker process attempted tostart up just as the Data Object Broker hadfailed. If the Data Object Broker is runningand this problem occurs, the Data ObjectBroker may be "hung" while trying to stop orabend.

Action: Use the command "hrncr kill" to ensurethat all Data Object Broker processes arestopped and that all shared resources arecleaned up.

If the problem persists, contact TIBCOSupport. Be prepared to submit a copy of theData Object Broker log file and any core fileproduced as a result of this problem.

S6BUL123EUnable to initialize IPC resources, node '%' isnot local or has no defined IPC key


Explanation: The entry for this Data ObjectBroker in the HCS configuration file may bemissing the IPCKEY or HOST attributes,and/or the host name specified may bewrong.

Action: Check that the NODENAME parameterin the crparm file is correct. If it is correctthen verify that the NODE definition in theHCS configuration file (huron.dir) has validIPCKEY and HOST attributes. The host namemust be the host on which you are

attempting to start the Data Object Broker orutility. NOTE: verify that the properpunctuation is in place, such as delimitingcommas.

S6BUL126EInvalid Fail Safe level, must be 0, 1, or 2


Explanation: The Fail Safe level specified in aPEERS parameter is invalid.

Action: Ensure that the Fail Safe level is 0, 1, or 2.

S6BUL127EInvalid value for '%'


Explanation: A parameter assignment oroperator command contained an invalidvalue.

Action: Verify the parameter or commandsyntax.

S6BUL128ESyntax error near '%'


Explanation: A syntax error was detected whileparsing a parameter assignment or operatorcommand. The last valid token is included inthe message to help identify the location ofthe problem. If the syntax error is in a filethen a subsequent message should indicatewhich file and what line number.



526 |

S6BUL129ESyntax error '%', expecting %


Explanation: A syntax error was detected whileparsing a parameter assignment or operatorcommand. The offending token is includedin the message along with a description ofwhat was expected. If the syntax error is in afile then a subsequent message shouldindicate which file and what line number.


S6BUL130ESyntax error, unexpected end of line


Explanation: A syntax error was detected whileparsing a parameter assignment or operatorcommand. The line ended while theparameter assignment or operator commandwas incomplete. If the syntax error is in a filethen a subsequent message should indicatewhich file and what line number.


S6BUL131ESyntax error, % exceeds % characters in length


Explanation: A syntax error was detected whileparsing a parameter assignment or operatorcommand. A string value was longer thanthe maximum allowed length. If the syntaxerror is in a file then a subsequent messageshould indicate which file and what linenumber.


S6BUL132EUnable to add peer to table, maximum of %peers exceeded


Explanation: The maximum number of peershave been configured and an additionalPEERS parameter is not accepted.

Action: Ensure that only the allowed maximumnumber of peers are configured.

S6BUL133EError: %, function unsupported in batchenvironment




S6BUL134EUnable to open % file '%', file was formatted as'%'


Explanation: An attempt to open one of thedatabase files failed because the file wasmoved or an invalid link was created. ObjectService Broker database files cannot bemoved to different locations in the filesystem. Once they have been formatted witha certain name, they can only be used underthat name.


| 527

This feature protects against possibleintegrity problems.

Action: If the file was moved, it must be movedback to its original location. If it is necessaryto move a segment, the segment must bebacked up then restored to its new location.

S6BUL136ENumber of connections specified for peerexceeds %


Explanation: The number of connectionsspecified in a PEERS parameter exceeds themaximum number of connection allowableto one peer.

Action: Ensure that the number of connections isno more than the maximum stated value.

S6BUL137ENo free buffers in wait list pool




S6BUL138ENo free buffers in holding process list pool




S6BUL139ESyntax error, byte in IP address '%' exceeds 255


Explanation: The value provided exceeds thelimit.

Action: Provide a valid value.

S6BUL140EUser '%' is not authorized to %, must be %


Explanation: The user is not allowed to performthe stated action based on his or her securitylevel. The security level of the user isestablished by the parameters SYSADMIN,OPERATOR, and PRIVILEGED. By default auser is given a security level of general ObjectService Broker user.

Action: Either the action must be performedwhile logged on with an authorized userid,or the Object Service Broker SystemAdministrator may need to update thesecurity parameters mentioned above.


528 |

S6BUL141EUser '%' is not authorized to access Data ObjectBroker configuration files


Explanation: The user does not have permissionto read the Data Object Broker parameter file.Any user that performs Object Service Brokeradministration or uses Object Service Brokerutilities must have read access to the crparmfile, the dbdef file, and the HCS configurationfile.

Action: Ensure that the userid and groupownerships for the various Data ObjectBroker configuration files are correct and thatthe permissions allow read access to thenecessary userids. Ensure that the user inquestion has the necessary groupmembership to access Object Service Broker.

S6BUL142EUser '%' is not authorized to access Data ObjectBroker IPC resources


Explanation: The user does not have permissionto attach the Data Object Broker sharedmemory. Any user that performs ObjectService Broker administration or uses ObjectService Broker utilities must have permissionto access to the Data Object Broker sharedmemory.

Action: Ensure that the SHAREDMEMPERMparameter in the crparm file allowsread/write access to the necessary userids.Ensure that the user in question has thenecessary group membership to accessObject Service Broker.

S6BUL143EUser id is invalid


Explanation: The userid supplied is greater than8 characters.

Action: Respecify with a userid of 8 characters orless.

S6BUL144EEnd-of-transaction was initiated with heldpages in the working set


Explanation: An internal error has occurred.NAM is notifying the Data Object Broker thatit has completed commit processing but thereare still held pages in the working set.

Action: This error is fatal and indicates a seriousprogramming error. Development should benotified immediately.

S6BUL150EUnable to connect via IPC, Data Object Brokeris offline, IPC key=%


Explanation: A connection could not beestablished to a Data Object Broker because itis not online.

Action: If the Data Object Broker is known to beonline when this problem occurs, verify thatthe IPC key used by the Data Object Broker isthe one that was used to attempt theconnection (using the ipcs command).Ensure that the HURONDIR environmentvariable is properly set.


| 529

S6BUL152EUnable to connect via IPC, no free buffers inport pool, IPC key=%


Explanation: A connection could not beestablished to a Data Object Broker becausethe maximum number of IPC connectionshas already been reached. The maximumnumber of connections allowed via IPC isbased mainly on the Data Object Brokerparameter MAXUSERS.

Action: Increase the value of the MAXUSERSparameter in the crparm file.

S6BUL153EUnable to connect via IPC, port is not available,IPC key=%


Explanation: A connection could not beestablished to a Data Object Broker becausethe Data Object Broker is still initializingitself.

Action: Wait for the Data Object Broker to comeonline. Use the command "hrncr state" todetermine when the Data Object Brokercomes online.

S6BUL155EUnable to listen on IPC, no free buffers in portpool, IPC key=%




S6BUL157EUnable to send message via IPC, no free buffersin message pool, IPC key=%


Explanation: A message could not be sent viaIPC due to a temporary shortage of messagebuffers. This problem should rarely occurunder normal circumstances.

Action: If this problem occurs with anyfrequency then contact TIBCO Support. Beprepared to submit a copy of the Data ObjectBroker log file and any core file produced asa result of this problem.

S6BUL158EUnable to send message, no free buffers inbuffer pool, IPC key=%


Explanation: A message could not be sent viaIPC due to a temporary shortage of messagebuffers. This problem should rarely occurunder normal circumstances.

Action: If it occurs with any frequency thencontact TIBCO Support. Be prepared tosubmit a copy of the Data Object Broker logfile and any core file produced as a result ofthis problem.

S6BUL159EUnable to send message via IPC, port is notactive, IPC key=%





530 |

S6BUL161EUnable to communicate via IPC, Data ObjectBroker has gone offline, IPC key=%


Explanation: A connection could not beestablished or a message could not be sentvia IPC because the Data Object Broker hasgone offline.

Action: Try again when the Data Object Broker isonline.

S6BUL163WUnable to send message via IPC to '%', processnot active, IPC key=%


Explanation: A message could not be sent viaIPC because the recipient of the message hasterminated without closing its ports. Therecipient likely terminated due to an explicitkill request from a user or administrator.


S6BUL170EUnable to lock Contingency Log, online or inuse


Explanation: An attempt to lock the contingencylog for formatting failed because thecontingency log is already in use by the DataObject Broker or by another Object ServiceBroker utility.

Action: If the Data Object Broker is running itshould be stopped to format the contingencylog. If the contingency log is being used byanother Object Service Broker utility thenyou must wait for the utility to finish.

S6BUL171EUnable to open Contingency Log, online or inuse


Explanation: An attempt to open the contingencylog failed because the contingency log isalready in use by the Data Object Broker orby an Object Service Broker utility.

Action: If the Data Object Broker is running thenthe contingency log cannot be used until theData Object Broker shuts down. If thecontingency log is being used by an ObjectService Broker utility then you must wait forthe utility to finish before starting the DataObject Broker or running another utility.

S6BUL172EUnable to use Contingency Log, page fileunformatted


Explanation: An attempt to open the contingencylog failed because the contingency log hasnot been formatted.

Action: Format the contingency log.

S6BUL173WUnable to abort contingent transaction, slot % isempty


Explanation: A request to abort an in-doubttransaction specified a slot this is empty. Themost likely cause of this problem is "stale"data on an administrator's display. The in-


| 531

doubt transaction may have been resolvedautomatically, aborted by a previous requestnot yet reflected on the display, or aborted byanother administrator.

Action: Have the administrator refresh the dataon the display.

S6BUL174WUnable to abort contingent transaction inactive/retry state, slot=%, transaction=%


Explanation: A request to abort an in-doubttransaction failed because the Data ObjectBroker is currently trying to resolve thetransaction. This problem may be caused by"stale" data on an administrator's display.

Action: Have the administrator refresh the dataon the display.

S6BUL175WUnable to release contingent transaction inactive/retry state, slot=%, transaction=%


Explanation: A request to release an in-doubttransaction failed because the Data ObjectBroker is currently trying to resolve thetransaction. This problem is likely caused bypeers and/or administrators resolving an in-doubt transaction simultaneously.

Action: Try again.

S6BUL176EUnable to format Contingency Log with % slots,maximum of % exceeded


Explanation: The maximum number of slots youcan specify in the Contingency Log is 65535.

Action: Specify a number of slots within theallowed range.

S6BUL177EInsufficient number of pages to format aContingency Log with % slots (3 pages arerequired for each slot)


Explanation: The number of pages you specifiedwas too low.

Action: Specify the number of pages as at leastthree times the number of required slots.

S6BUL179EUnable to read Contingency Log, invalid data inslot %


Explanation: An attempt to read a contingencylog slot failed because the slot containedinvalid data. This is likely due to a loss ofdata on the disk.



532 |

S6BUL180ENo free space available in Contingency Log


Explanation: An attempt to begin a distributedFail Safe transaction failed because there isno more room in the contingency log. Thismay be due to a lack of slots (each distributedFail Safe transaction requiring one slot) or toa lack of space on which to store thetransaction intent list. A lack of slots may bedue to a build up of in-doubt transactionsdue to connection outages.

Action: Either increase the number of slots in thecontingency log or increase its overall size.

S6BUL181EUnable to complete checkpoint in recovery,segment '%' online or recovery not in progress




S6BUL183EUnable to find message queue port, segmentid=%, file=%




S6BUL184EUnable to initialize access control,'SYSADMIN' parameter is required


Explanation: A required parameter is missing.

Action: Add the SYSADMIN parameter andretry.

S6BUL185EInvalid or unknown userid '%' specified on '%'parameter


Explanation: The userid identified to theparameter named is not valid.

Action: Ensure the userid is defined to thesystem and respecify the parameter.

S6BUL186EUnable to become system administrator fromroot


Explanation: The command was started withroot authority, but it was unable to change itsuserid to the Object Service Broker systemadministrator's userid. You may require helpfrom the system administrator to resolve thisproblem.

Action: Login as the Object Service Brokersystem administrator and retry theoperation.


| 533

S6BUL187EUnable to add userid to access control list,maximum of % userids exceeded


Explanation: The maximum number ofauthorized userids has already beenconfigured. An attempt to define anotherauthorized userid has failed.

Action: Reduce the number of authorized useridsdefined in the Data Object Brokerconfiguration file or on the command line.

S6BUL189EUnable to initialize access control, no more thanone system administrator may be specified,check 'SYSADMIN' parameter(s)


Explanation: An attempt was made to initializeaccess control to more than one SystemAdministrator at a time.


S6BUL190WSpace shortage in segment '%', xx% full


Explanation: Your segment is getting close tobeing full.

Action: Consider increasing the segment size.

S6BUL191ISpace shortage eased in segment '%', down toxx% full


Explanation: You have succeeded in increasingthe amount of free space in your segment.


S6BUL192EInsufficient number of pages for Journal.Required minimum is nnnn


Explanation: The actual number of journal pagesis less than the number of pages in theresident page manager, as defined by aparameter RESIDENTPAGES in theCRPARM file.

Action: Increase the number of actual pages inthe journal or decrease the value in theRESIDENTPAGES parameter.

S6BUL193IShared memory size is nnnn Kbytes


Explanation: This value shows the amount ofmemory in the shared region of the DOB.Data Object Broker.

This value should be smaller than theamount of physical memory on the system inorder to avoid thrashing. For systems withmultiple Data Object Brokers, it is also usedto determine what the value of the nextSHAREDMEMADDR value should be.

Action: If your system is paging excessively,reduce the RESIDENTPAGES parameter.


534 |

S6BUL194ESegment <segmentName> file <pagefileName>too big - check 'MAXTDSEXTENTS' parameter


Explanation: The size of the TDS file is limited bythe number of TDS extents it can contain; thisis a configurable value set byMAXTDSEXTENTS parameter in crparmfile.

Action: Increase the value of theMAXTDSEXTENTS parameter.

S6BUL195EUnable to create semaphore<semaphoreName>, error = <errorNo>


Explanation: Internal error - indicates ObjectService Broker inability to use operationssystem facilities; error number is comingfrom system API.

Action: See your system administrator for help infixing this problem, which may requireupdates to the kernel configuration. ContactTIBCO Support.

S6BUL196EUnable to use semaphore <semaphoreName>,error = <errorNo>


Explanation: Internal error - indicates ObjectService Broker inability to use operationssystem facilities; error number is comingfrom system API.


S6BUL197EUnable to create mutex <mutexName>, error =<errorNo>


Explanation: Internal error - indicates ObjectService Broker inability to use operatingsystem facilities; error number is comingfrom system API.


S6BUL198EUnable to use mutex <mutexName>, error =<errorNo>


Explanation: Internal error - indicates ObjectService Broker inability to use operatingsystem facilities; error number is comingfrom system API.


S6BUL200EInternal error: Bitmap access inconsistent


Explanation: This is an extreme error. ObjectService Broker took this action to prevent apossible Pagestore corruption.



| 535

S6BUL201EUnable to flush page file %; % = %; %


Explanation: Pages from the resident page poolcould not be flushed to the page files. OnUNIX the fdatasync system call failed and onWindows the FlushFileBuffers Windows APIcall failed.

Action: Review the error codes to determinewhat cause the error. A possible cause of theerror is that a disk I/O error occurred. OnWindows review the event log for system orhardware errors. Restart the DOB todetermine whether the failures arepersistent.

S6BUL211ENo free buffers in CTABLE pool


Explanation: The CTABLE Manager hastemporarily run out of buffers for tables. Thisis likely due to a burst of update activity thatconsumed buffers faster than they could bewritten to disk.

Action: Consider increasing the value for theData Object Broker parameterCTABRESIDENT. Consult the Installationand Operations manual.

S6BUL213ECompoundSynch internal failure, call '%'failed, error=%


Explanation: An unexpected error occurred withan internal synchronization object.


S6BUL214WRedo log full or near-full condition reached


Explanation: The redo log has become full or isnearly full. A checkpoint will be requestedthat should result in the condition beingresolved. Until the condition is resolved,sync processing is temporarily suspended.

Action: Increase the size of the redo log as it is notadequate for the current volume orfrequency of sync requests.

S6BUL215IRedo log full or near-full condition resolved


Explanation: The redo log is no longer full ornear-full after checkpoint processing andsync processing will be allowed to continue.



536 |

UM: HCS

S6BUM001EUnable to allocate % bytes from system heap

Source: HCS


Action: If this problem occurs regularly, thesystem administrator should address theresource shortage in terms of system load,system configuration, and machine capacity.

S6BUM003EUnable to open port, node '%' is not accessiblevia %

Source: HCS

Explanation: Communication with the node isnot possible.

Either the node has not been configured forthe appropriate transport mechanism, or thesystem you are on does not have access tothat transport mechanism.

Keep in mind that Object Service Broker usesIPC to communicate with a node on thesame system, otherwise it chooses TCP/IP.

Action: Examine the HCS configuration file toensure that the target node is properlyconfigured. Ensure that it is addressable viathe appropriate transport mechanisms.

S6BUM004EUnable to open port, node '%' is not local and isnot accessible on any network

Source: HCS

Explanation: Communication with the node isnot possible. The node has not beenconfigured for TCP/IP connectivity and it isnot local to this system.

Action: Examine the HCS configuration file toensure that the target node is properlyconfigured. Ensure that it is addressable viathe appropriate transport mechanisms.

S6BUM013EInbound connection rejected, system resourceshortage

Source: HCS

Explanation: An inbound connection could notbe accepted due to a system resourceshortage. This is likely a temporary shortagethat should be alleviated when otherprocesses end, or other users logoff.



| 537

S6BUM014EUnable to connect to node '%'

Source: HCS

Explanation: A connection could not be made tothe target node. The specific reason for thefailure may be indicated by an errno valuethat is part of the message, or by a previousmessage.

Action: Review the errno and previous messagesto determine the appropriate action.

S6BUM016EUnable to connect to node '%', connectionrejected

Source: HCS

Explanation: A connection was made to thetarget node, but the node rejected the logon.If this message occurs on a peer connection itmay mean that the peer Data Object Brokerhas not been configured to expect a peerconnection from the originator. It may alsoindicate that target node has run out ofresources and is not able to accept theconnection.

Action: If the reasons for the rejected connectionare not obvious, examine the Data ObjectBroker log at the target node for moreinformation.

S6BUM018EUnable to open % port for node '%'

Source: HCS

Explanation: The Data Object Broker could notopen a port on the particular transportmechanism. The specific reason for thefailure may be indicated by an errno valuethat is part of the message, or by a previousmessage.

Action: Review the errno and the previousmessages to determine the appropriateaction.

S6BUM020EInvalid connection information detected

Source: HCS



S6BUM021EUnable to perform SNA request, SNA librarieswere not linked during installation

Source: HCS

Explanation: During the installation process, theinstaller indicated that SNA support was notavailable on the system. Consequently thecurrent installation of TIBCO(r) ObjectService Broker has not been linked to use the


538 |

system's SNA services. The Data ObjectBroker, however, has been configured to useSNA to communicate with a peer Data ObjectBroker.

Action: Either modify the Data Object Brokerconfiguration so that connections to SNAnodes are not required, or (assuming thatSNA services are available on the system) re-link TIBCO(r) Object Service Broker so thatSNA connectivity is enabled. Refer to theInstallation and Operations manual forinstructions on how to re-link TIBCO(r)Object Service Broker to enable SNAconnectivity.

S6BUM050ESyntax error '%', expecting %

Source: HCS

Explanation: A syntax error was detected whileparsing the HCS configuration file. Theoffending token is included in the messagealong with a description of what wasexpected. A subsequent message shouldindicate the file name and line number wherethe problem occurred.

Action: Verify the syntax of the node definition.

S6BUM051ELine exceeds % characters

Source: HCS

Explanation: A line in the HCS configuration filewas longer than the expected maximumlength. A subsequent message shouldindicate the file name and line number wherethe problem occurred.

Action: Edit the file to ensure that the lengths ofall the lines are within the limit specified.

S6BUM052EUnrecognized keyword '%'

Source: HCS

Explanation: While scanning the HCSconfiguration file an invalid keyword wasencountered. A subsequent message mayidentify where the problem occurred.


S6BUM054ENode name not specified

Source: HCS

Explanation: A definition in the HCSconfiguration file does not have a NAMEattribute. A subsequent message shouldindicate the file name and line number wherethe problem occurred.

Action: Verify that the node definition iscomplete.

S6BUM055EUnknown host name '%', node='%'

Source: HCS

Explanation: The HOST name specified in thenode definition is not known at this system.The HOST name may be misspelled, or itmay not be defined locally (in /etc/hosts) orat the name server.

Action: Verify that the HOST name is spelledcorrectly. If the HOST name is correct thencontact the system administrator to have thename defined using the appropriate facility.Adding the IP attribute to the node definitionmay allow you to proceed if you are simplytrying to connect to a node.


| 539

S6BUM056EHost name and specified IP address do notcorrespond, node='%'

Source: HCS

Explanation: A HOST attribute and an IPattribute have both been specified in thedefinition of the node, but the IP addressdoes not correspond to the HOST name.

Action: Ensure that the IP address is the correctone for the HOST name.

S6BUM057ESystem host name '%' is not known to network

Source: HCS

Explanation: The local system has not yet beenfully configured. The system name is notdefined locally (in /etc/hosts) or at the nameserver.

Action: Contact the system administrator to havethe system name defined using theappropriate facility.

S6BUM058EUnable to determine system host name

Source: HCS

Explanation: The local system has not yet beenfully configured. The system name has notbeen set.

Action: Contact the system administrator to havethe system name set.

S6BUM059EUnknown service name '%', node='%'

Source: HCS

Explanation: The SERVICE name specified in thenode definition is not known at this system.The SERVICE name may be misspelled, or itmay not be defined locally (in /etc/services)or at the name server.

Action: Verify that the SERVICE name is spelledcorrectly. If the SERVICE name is correct thencontact the system administrator to have thename defined using the appropriate facility.As an alternative replace the SERVICE namewith an actual PORT number.

S6BUM060EService name and specified port do notcorrespond, node='%'

Source: HCS

Explanation: A SERVICE attribute and a PORTattribute have both been specified in thedefinition of the node, but the PORT numberdoes not correspond to the SERVICE name.

Action: Ensure that the PORT number is thecorrect one for the SERVICE name.

S6BUM061EAlias or LU name not specified, node='%'

Source: HCS

Explanation: The node NAME is greater than 9characters long and no ALIAS or LU namehas been given for the node. Although nodenames can be up to 16 characters in length,Object Service Broker requires an 8-characteridentifier that tags the node both internallyand on administrative controls. On z/OS,


540 |

this is the LU name. On Windows andSolaris, this is either the LU name (if it isgiven), the node NAME (if it is 8 charactersor less in length), or the ALIAS.

Action: Add an ALIAS to the definition on thenode.

S6BUM062ENode '%' is not defined in directory '%'

Source: HCS

Explanation: The node is not defined in the HCSconfiguration file.

Action: Verify that the node name is spelledcorrectly both as it is given and in the HCSconfiguration file.

S6BUM063EError detected at line % of directory '%'

Source: HCS

Explanation: An error occurred while scanningthrough the HCS configuration file. Aprevious message should indicate thespecific error detected.


S6BUM064EUnexpected end of file encountered

Source: HCS

Explanation: While scanning a node definition inthe HCS configuration file, the end of file wasencountered. This probably means that thelast attribute in the last node definition had acomma indicating there were more attributesto come.


S6BUM070EUnable to open directory '%'

Source: HCS

Explanation: The HCS configuration file couldnot be opened. The specific reason for thefailure is indicated by the errno value thatshould be part of this message.

Action: Review the errno to determine theappropriate action to take.

S6BUM071EUnable to read directory '%'

Source: HCS

Explanation: The HCS configuration file couldnot be read. The specific reason for the failureis indicated by the errno value that should bepart of this message.


S6BUM072EUnable to close directory '%'

Source: HCS

Explanation: The HCS configuration file couldnot be closed. The specific reason for thefailure is indicated by the errno value thatshould be part of this message.



| 541

S6BUM102ITCP/IP library call failed: %

Source: HCS

Explanation: This message traces the failure of aTCP/IP function. In most cases a subsequentmessage will indicate the effects of the failure(for instance, the loss of connection). Theerror description and/or errno value may beuseful in determining TCP/IPcommunication problems.

Action: Consult the appropriate TCP/IPprogramming manuals for your system todetermine the meaning of the errorinformation.

S6BUM103ISystem call '%' failed, errno=% [%]

Source: HCS

Explanation: A System call failed during theattempt to open a socket listing port or aremote location. A subsequent message willdetail the impact of the error.

Action: Review the error code for the system calland the following message to determinewhat action to take.

S6BUM105EProcedure % address not found; Windowsextended message %

Source: HCS

Explanation: This message indicates a failure ofthe Windows GetProcAddress function tofind the indicated procedure. The Windowsextended message gives additionalinformation. Most likely cause is a corruptedDLL.

Action: Get a fresh copy of the WAPPC32.dll orWINCSV32.dll files.

S6BUM106Iioctl() request % failed, errno=%

Source: HCS

Explanation: This message traces the failure of anioctl call. A subsequent message indicates theeffects of the failure. The errno value can beuseful in determining the problem.

Action: Consult the system documentation fornetwork interfaces to determine the meaningof the error information for the ioctl request.

S6BUM107EUnable to get network interface configurationlist

Source: HCS

Explanation: The list that fully describes allnetwork interface configurations for the localmachine cannot be obtained. This list isneeded when determining if a node is local.

Action: Contact TIBCO Support. Be prepared tosubmit a copy of all log files containing thismessage. Any Data Object Broker log filesubmitted should be from a Data ObjectBroker configured such that theERRNOTRACE parameter has not been setN. This will ensure that the Data ObjectBroker log file will contain system andinternal error tracing.


542 |

S6BUM108EKeep-alive monitor error, pthread call ';' failedwith return code ;and errno ;

Source: HCS

Explanation: TCP keepalive processing failedwhen making a call to the Pthreads library.Keepalive processing for the ExecutionEnvironment was likely terminated.

Action: TCP keepalive polls can be activated by auser by using the keepalive parameter for anode in the huron.dir configuration file. Onthe Solaris platform TCP keepalive polls areimplemented using a keepalive monitorthread and out-of-band TCP/IP messages.An error was detected when starting themonitor thread or when interfacing with thethread. Review the errno value to determinethe cause of the failure.

S6BUM109EKeep-alive probe sent to node ';' failed witherrno=;, keep-alive probes for connectiondisabled

Source: HCS

Explanation: The send of a TCP keepalive probeto a remote node failed. Keep-alive probeswill no longer be sent to the remote location.

Action: TCP keepalive probes are enabled for aremote node by using the keepaliveparameter for the definition of the node inthe huron.dir configuration file. Review theerrno to determine why the socket send ofthe keepalive probe failed.


| 543

UN: DOB Administration Tasks

S6BUN005EThe screen size stack is empty - aborting %

Source: DOB Administration Tasks



S6BUN006EScreen size must be at least % by %


Explanation: You are attempting to starthrntladm from a terminal or window thatdoes not have the required dimensions.

Action: Start hrntladm from a terminal orwindow with the stated minimumdimensions.

S6BUN007ECurses: color initialization failed



Action: Contact TIBCO Support. Be prepared tosubmit a copy of the Data Object Broker logfile and any core file produced as a result ofthe problem.

S6BUN008ECurses: system initialization failed




S6BUN009EUnexpected end of file in %





544 |

UR: DOB

S6BUR001EUnable to allocate % bytes from system heap

Source: DOB


Action: If this problem occurs regularly, yoursystem administrator should address theresource shortage in terms of system load,system configuration, and machine capacity.

S6BUR002WRedo recovery started

Source: DOB

Explanation: This message indicates that thereare transactions in the redolog that were notpart of a checkpoint, due to an abnormaltermination of the Data Object Broker. TheData Object Broker will attempt to reapplythese transactions to the Pagestore to recoverthe consistency of the database.


S6BUR003ERedo transaction out of sequence,checkpoint=%, commit=%

Source: DOB



S6BUR004IRedo recovery successful, commit=%

Source: DOB

Explanation: The transactions found in theredolog at startup have been reapplied to thePagestore.


S6BUR005ERedo recovery failed

Source: DOB

Explanation: A failure occurred while readingtransactions from the redolog during redorecovery. A previous message shouldindicate the specific problem.


S6BUR006IData Object Broker quiesced, redo log spaceshortage

Source: DOB

Explanation: The redolog has becomecompletely filled while waiting for acheckpoint to complete. The Data ObjectBroker has been quiesced and will no longerprocess updates. This may result from anexcessive volume of updates (with respect tothe current configuration parameters) or


| 545

from a delay in checkpoint processing.Checkpoint processing may be delayed dueto a sudden volume of updates or because aspin job has failed.

Action: Ensure that the any spin jobs havecompleted successfully. If a spin job hasfailed you can attempt to run it again bydirectly executing either the spin01 or spin02scripts. Once the spin job has completedsuccessfully, request a checkpoint with theCHECKPOINT operator command. After thecheckpoint has completed successfully, usethe RESUME operator command to bring theData Object Broker back online.

S6BUR008EUnable to initialize European language support

Source: DOB



S6BUR009EUnable to initialize lock manager

Source: DOB



S6BUR010EUnable to free locks for contingent transaction,slot=%, transaction=%

Source: DOB



S6BUR011WRequest to abort/commit contingent transactionignored, transaction not found, slot=%,transaction=%

Source: DOB

Explanation: A request to commit/abort an in-doubt transaction specified a slot this isempty or in use by another transaction. Themost likely cause of this problem is "stale"data on an administrator's display. The in-doubt transaction may have been resolvedautomatically, aborted by a previous requestnot yet reflected on the display, or aborted byanother administrator.

Action: Have the administrator refresh the datathat is being displayed.

S6BUR012WUnable to reacquire logical locks for contingenttransaction, slot=%,transaction=%

Source: DOB

Explanation: At startup, one or more in-doubttransactions were present in the contingencylogs. An attempt to reacquire logical locks fora contingent transaction failed. A previous


546 |

message may indicate the specific problemthat occurred processing the lock request.This message may also indicate a Data ObjectBroker internal problem.

Action: If you suspect that this is a Data ObjectBroker internal problem, contact TIBCOSupport. Be prepared to submit a copy of theData Object Broker log file and any core fileproduced as a result of this problem.

S6BUR013ILogical locks reacquired for % contingenttransactions

Source: DOB

Explanation: At startup, one or more in-doubttransactions were present in the contingencylogs. This message indicates how many in-doubt transactions were successfully able toreacquire logical locks.


S6BUR014EDOB restart processing failed due to redotransaction failure

Source: DOB

Explanation: When applying changes to a DataObject Broker during restart following anabnormal termination, a transaction failed.To ensure integrity the Data Object Brokerterminates with an error.



| 547

US: DOB Supervisor Tasks

S6BUS001I% stopped due to error


Explanation: This message indicates the exitstatus of an internal Data Object Brokerprocess. In this case the process stopped afterdetecting a problem. Look for previous errormessages that may indicate the specificproblem.

Action: No action required for this message. Ifother messages are present they may requirespecific actions.

S6BUS002I% startup completed (pid=%)


Explanation: The internal Data Object Brokerprocess has started and initializedsuccessfully. The pid is the identifier for theprocess.


S6BUS003EUnable to transmit message % to %


Explanation: This problem may occur duringabend situations if parts of the Data ObjectBroker have stopped unexpectedly. If thereare no apparent reasons for this problem tooccur then this message may indicate a DataObject Broker internal problem.

Action: If you suspect that this is a Data ObjectBroker internal problem then contact TIBCOSupport. Be prepared to submit a copy of theData Object Broker log file and any core fileproduced as a result of this problem.

S6BUS004EUnable to receive message


Explanation: This problem may occur duringabend situations if the internalcommunication mechanism has beendamaged. If there are no apparent reasons forthis problem to occur then this message mayindicate a Data Object Broker internalproblem.



548 |

S6BUS005EUnexpected message % received




S6BUS006IOperator command: %


Explanation: The operator command indicatedin the message was issued.


S6BUS009IData Object Broker stopped


Explanation: All internal processes of the DataObject Broker have been stopped and allresources have been cleaned up.


S6BUS010IData Object Broker shutdown requested


Explanation: The Data Object Broker hasreceived a shutdown request. This can occurin the following ways: a SHUTDOWNoperator command is received, a shutdownrequest is issued from an Execution

Environment, a "hrncr shutdown" or "hrncrstop" command is issued, or a SIGTERMsignal is sent to the hrncr supervisor processof the Data Object Broker.


S6BUS012EUnable to initialize shared rules buffer


Explanation: An attempt to create the sharedrules buffer, used by local ExecutionEnvironments, has failed. Look for aprevious error message to indicate thespecific problem.

Action: Review the previous messages todetermine the appropriate action to take.

S6BUS013IData Objct Broker kill requested


Explanation: The Data Object Broker hasreceived a kill request. The Object ServiceBroker System Administrator has issued the"hrncr kill" command, or a SIGABRT signalhas been sent to the hrncr supervisor processof the Data Object Broker.


S6BUS014IStarting %


Explanation: The Data Object Broker isattempting to start an internal process.



| 549

S6BUS015EUnable to start %


Explanation: The Data Object Broker was unableto start an internal process. The specificreason for the failure is indicated by the errnovalue that should be part of this message.The most likely cause of failure is a shortageof memory or process entries in the system. Itmay also be the result of a configured limiton the number of processes.

Action: The system administrator may be neededto help understand and fix the problem.Exceeding the configured limit on thenumber of processes may require updates tothe kernel configuration.

S6BUS016EUnable to start %, maximum number ofprocesses started




S6BUS017EUnable to start %, process already started orrunning, pid=%




S6BUS018EUnable to register %, already registered




S6BUS019EUnable to terminate message queue port '%'


Explanation: During shutdown, the Data ObjectBroker was unable to terminate an internalcommunication queue. A previous messageshould indicate the specific problem.


S6BUS020EUnexpected message type % received





550 |

S6BUS021EUnable to reply to request




S6BUS022I% stopped


Explanation: This message indicates the exitstatus of an internal Data Object Brokerprocess. In this case, the process shutdownsuccessfully with no problems.


S6BUS023I% stopped due to signal %


Explanation: This message indicates the exitstatus of an internal Data Object Brokerprocess. In this case, the process wasterminated by a signal. If the signal isSIGKILL, the process was likely terminatedas part of the cleanup during an abnormaltermination of the Data Object Broker.Signals such as SIGFPE, SIGSEGV, andSIGBUS are exception conditions raised bythe system that indicate an internal DataObject Broker problem.


S6BUS024EData Object Broker abending, startup time limitexceeded, time=% minutes


Explanation: The Data Object Broker is abendingbecause the overall startup procedure tooktoo long.

A very busy system may account for thedelay in the startup. Otherwise the DataObject Broker is likely hanging as it attemptsto access either communications or files.

Action: If this problem is due simply to a busysystem, increase the value of theTIMEOUTSTART parameter in the crparmfile. Verify that the devices and file systemsthat hold the Pagestore are available, andthat TCP/IP communications areresponding.

S6BUS025EData Object Broker abending, shutdown timelimit exceeded, time=% minutes


Explanation: The Data Object Broker is abendingbecause the shutdown procedure took toolong.

Action: You may need to manually drop anysessions and transaction programs that maybe "hung".


| 551

S6BUS026EData Objec Broker abending, shutdownrequested during startup


Explanation: The Data Object Broker is abendingbecause a shutdown was requested while itwas starting up.

Action: Start up the Data Object Broker again, if itis required.

S6BUS027EData Objec Broker abending, child processstopped unexpectedly


Explanation: The Data Object Broker is abendingbecause one or more Data Object Brokerprocesses have stopped without being askedto stop. Subsequent messages shouldindicate the status of each of the internalprocesses and should help identify whichprocess stopped unexpectedly.

Action: Review the messages to determine theappropriate actions to take.

S6BUS028EData Objec Broker abending


Explanation: The Data Object Broker is abendingbecause the Object Service Broker systemadministrator issued the "hrncr kill"command, or because a SIGABRT signal wassent to the hrncr supervisor process.

Action: No action required for this message. Ifother messages are present they may requirespecific actions.

S6BUS029EData Object Broker abending, unexpectedsignal % received


Explanation: The Data Object Broker is abendingbecause a signal was received that was notanticipated. The signal was likely sentexplicitly from the Object Service BrokerSystem Administrator's account, or from auser with root authority. If there is noexplanation for the signal then this mayindicate an internal Data Object Brokerproblem.


S6BUS030IData Object Broker - TIBCO(r) Object ServiceBroker Release %


Explanation: Identifies the release of TIBCO(r)Object Service Broker which is being used.


S6BUS031EData Object Broker abending, MaxUsersexceeds NOFILES


Explanation: The number of users is greater thanthe hard limit for the number of filedescriptors for the system.

Action: Decrease users in the crparm file, or havethe system administrator increase thenumber of file descriptors allowed perprocess.


552 |

S6BUS032EData Object Broker abend requested, fn=%,source=%(%)


Explanation: This message shows the functionname, source, and line number of an abend.

Action: Review all messages to determine theappropriate actions to take.

S6BUS033EProcess (pid=%) stopped due to error (exitcode=%)


Explanation: This message identifies the processand its exit code.

Action: Accompanying messages should tellwhat action to take.

S6BUS100ISystem library call failed: %, errno=%


Explanation: This message traces the failure of anoperating system function. A subsequentmessage will usually indicate the effects ofthe failure. The errno value may be useful indetermining the cause of the problem.

Action: Consult the appropriate systemprogramming manual for your system todetermine the meaning of the errno value.Your system administrator may be needed tohelp diagnose the problem.

S6BUS101IError: errno=%


Explanation: This message traces the initialdetection of a failure in the Data ObjectBroker. A subsequent message will usuallyindicate the effects of the failure. Thismessage may indicate a Data Object Brokerinternal problem.


S6BUS104ISystem library call failed: %, errno=%, %


Explanation: This message traces the failure of anoperating system function. A subsequentmessage will usually indicate the effects ofthe failure. The errno value may be useful indetermining the cause of the problem.

Action: Consult the appropriate systemprogramming manuals for your system todetermine the meaning of the errno value.The system administrator may be needed tohelp diagnose the problem.


| 553

S6BUS105IInternal library call failed: %, errno=%


Explanation: This message traces the failure of aninternal Data Object Broker function. Asubsequent message will usually indicate theeffects of the failure. This message mayindicate a Data Object Broker internalproblem.


S6BUS106IInternal library call failed: %, errno=%, %


Explanation: This message traces the failure of aninternal Data Object Broker function. Asubsequent message will usually indicate theeffects of the failure. This message mayindicate a Data Object Broker internalproblem.


S6BUS107INode % accepting connections on interfaceaddress % socket port %


Explanation: This information message in theDOB log displays the communicationsadapter IP address and the socket portnumber for the listening port for allconnections to the DOB. The information isdisplayed to assist DOB administratorsdebug connection problems with the DOB.


S6BUS108ESHUTDOWN and STOP commands cannot beused when the DOB runs as a service; use theWindows NET command to shutdown the DOB


Explanation: On Windows, the DOB was startedas a service but an "HRNCR STOP" or"HRNCR SHUTDOWN" command wasentered on the command line to shut downthe DOB. This is not permitted.

Action: Use the Windows .NET command tostop the DOB running as a service.

S6BUS112IRedolog surplus capacity=%


Explanation: This message appears when theData Object Broker is shut down. It is aninformation message, indicating how manypages are still available at the redolog high-water mark of usage.

Action: No action is required. If the capacity isclose to 0, then the Data Object Broker is closeto quiescing, and you may considerincreasing the size of the redolog.


554 |

UX: DOB Checkpoint Tasks

S6BUX001IStarting spin job '%'


Explanation: The spin job identified by themessage has been started.


S6BUX002EUnable to start spin job; %, errno = %


Explanation: The Data Object Broker was unableto start a spin job. The specific reason for thefailure is indicated by the errno value that ispart of this message, as well as the name ofthe function call that failed The most likelycause of failure is a shortage of memory orprocess entries in the system. It may also bethe result of a configured limit on the numberof processes.

Action: The system administrator may be neededto help understand and fix the problem.Exceeding the configured limit on thenumber of processes may require updates tothe kernel configuration.

S6BUX003ESpin job '%' ended with exit code %


Explanation: This message indicates the exitstatus of a spin job. In this case, the spin jobterminated due to a an error. In order formessages from spin jobs to be included in theData Object Broker log, the parameterSTDERRTRACE in the crparm file must havethe value YES.

Action: Rerun the spin job by simply starting thescript (spin01 or spin02) from the commandline. If the job still fails, you should see moreinformation about the nature of the problem.

S6BUX004ESpin job '%' ended with signal %


Explanation: This message indicates the exitstatus of a spin job. In this case, the spin jobwas terminated by a signal. Spin jobs do notnormally use or expect signals, so it is likelythat the signal was sent explicitly from theObject Service Broker system administrator'saccount, or from a user with root authority. Ifthere is no explanation for the signal, thismay indicate an internal Data Object Brokerproblem.

Action: Rerun the spin job by simply starting thescript (spin01 or spin02) from the commandline. If the job fails, you should seeinformation about the nature of the problem.If you suspect that this is a Data Object


| 555

Broker internal problem, contact TIBCOSupport. Be prepared to submit a copy of theData Object Broker log file and any core fileproduced as a result of this problem.

S6BUX005ISpin job '%' ended


Explanation: This message indicates the exitstatus of a spin job. In this case, the spin jobcompleted successfully.


S6BUX006Ijournal % full, switching journals


Explanation: During a spin job the journalidentified in the message reached its capacityand another journal is now being used.


S6BUX007EUnable to use journal %, not emptied by spinjob


Explanation: The Data Object Broker is not ableto use the journal because it was not emptiedby the spin jobs as anticipated. This messagemay indicate a Data Object Broker internalproblem.


S6BUX008EUnable to write checkpoint to either journal


Explanation: The Data Object Broker is unable towrite a checkpoint into either journal, evenafter successfully switching journals. Thisproblem may indicate that the journals havebeen defined to be too small and that the sizeof the checkpoint exceeds the size of eitherjournal. If this explanation does not seemlikely and there are no other problemsindicated, this may indicate a Data ObjectBroker internal problem.

Action: Reformat the journals. Ensure that bothjournals are large enough to handle at leastone checkpoint. That means that the numberof pages in each journal should be greaterthan or equal to the value ofRESIDENTPAGES in the crparm file. If yoususpect that this is a Data Object Brokerinternal problem, contact TIBCO Support. Beprepared to submit a copy of the Data ObjectBroker log file and any core file produced asa result of this problem.

S6BUX009WCheckpoint request ignored, %


Explanation: A checkpoint request was receivedor generated internally, but no updates havebeen processed due to the specified reason.



556 |

S6BUX010ICheckpoint begin, id=%, pages=%


Explanation: A checkpoint started. Thecheckpoint number and number of pages aregiven in the message.


S6BUX011EUnable to complete checkpoint, page=%undefined




S6BUX012ICheckpoint end, id=%


Explanation: The checkpoint was successful. Thecheckpoint number is given in the message.


S6BUX013EUnable to use journal %, contains unrecovereddata




S6BUX015EUnable to complete checkpoint, not all data setsconfirmed




S6BUX016ISpinning journal % on operator's request


Explanation: The operator has issued commandSPINSUBMIT to activate journal spin.


S6BUX017EJournal switch cannot be completed, journal %cannot be used


Explanation: Journal switch activated byoperator's command SPINSUBMIT cannot becompleted, due to the fact that the otherjournal has not been emptied and thereforecannot be used online

Action: Upon receipt of this message,administrator should try to executecorresponding batch spin jobIMMEDIATELY (from the OS commandline). Successful spin will reset journal fileand SPINSUBMIT could be reapplied


| 557

S6BUX018IDOB is now online - Redolog available forprocessing


Explanation: The Data Object Broker is nowrecovered from a quiesced state.


S6BUX019ICheckpoint deferred, previous checkpoint stillin progress


Explanation: Only one checkpoint can beexecuted at a time.

Action: Wait until the current checkpoint is done.

S6BUX020ICHECKPOINT MAXIMUM PAGES = ____,TRANSACTIONS =


Explanation: This message is provided forinformational purposes only and is issued toconfirm the thresholds set for the maximumsize of a Checkpoint.


S6BUX021WPAGE LIMIT REDUCED - EXCEEDS 15% OFRESIDENT PAGES


Explanation: The value specified for theCHPAGELIMIT initialization parametermust not exceed 15% of the Resident PageDirectory as defined by the

RESIDENTPAGES initialization parameter.The value of CHPAGELIMIT has beenautomatically reduced so as to conform tothis requirement.

Action: Adjust the CHPAGELIMIT parameter orthe RESIDENTPAGES parameter or both sothat this condition is addressed.

S6BUX022WParameter '%' REDUCED - INSUFFICIENTSPACE IN %


Explanation: The value specified for theinitialization parameter indicated by thismessage is too large to be supported by theredolog.

Action: Adjust the indicated initializationparameter to relieve this condition, orincrease the amount of space available to theredolog. Consult the Installation andOperations manual for further information.

S6BUX023EUnable to determine the status of the spin job,errno = %d


Explanation: This message indicates that duringa journal switch we cannot figure out thestatus of the previous spin job. We have towait to check the actual status of the journalfile.



558 |

S6BUX024EPath % specified by parameter 'SPINSHELL' isnot accessible, errno = %


Explanation: The SPINSHELL parameterspecifies a path to a shell that is not readableor executable.


• Correct the value of the SPINSHELLparameter.

• Correct the permissions for the specifiedshell.

• Use the default value.

S6BUX027EError encountered %; % failure, error %


Explanation: An internal Data Object Brokerfailure occurred with respect to the capturingof spin job output.



| 559

XC: Cross-Memory Control

S6BXC200ICROSS-MEMORY CORRESPONDENTREGIONS MAY HAVE BEEN ABANDONED

Source: Cross-Memory Control

Explanation: This message is issued by an ObjectService Broker communications environmentthat is being terminated, if it has detectedthat not all the other Object Service Brokercommunications environments with which ithad engaged in communications exchangesusing Cross Memory Services have beenallowed to disconnect. Any communicationerrors experienced by those Object ServiceBroker communications environments thatstill had active Cross Memory Servicescommunications paths to the terminatingObject Service Broker communicationsenvironment can be attributed to thetermination of the current Object ServiceBroker communications environment.


S6BXC875ICROSS-MEMORY CLEANUP FROM ABENDWILL TERMINATE CONNECTION


Explanation: This message is issued by cleanupprocessing. It is issued during recovery froman intercepted abend that occurred duringcross memory communications send/receiveprocessing. It indicates that the cleanupprocessing has reset the cross memory

communications control indicators and willattempt to terminate the communicationsconnection that was active when the abendoccurred.

This message is usually accompanied byother messages that provide additionalinformation concerning the error, such asmessage S6BCM997E. Occasionally,environmental restrictions prevent any othermessage from being issued. An error recordis written to the system log and an SVCdump is attempted.

Action: Since this message indicates a successfulcleanup from an abend, no immediate actionmay be necessary. Consider the following:

• If the affected Object Service Brokercomponent (Data Object Broker orExecution Environment) displays no othersymptoms of difficulty, the error hassuccessfully been isolated to affect only asingle user connection.

• If this message is issued repeatedly, it mayindicate a severe problem with thecommunications capability of the affectedObject Service Broker component. Ifnormal production work is seriouslyaffected, it may be prudent to recycle thejob. In this case, collect any diagnosticinformation available (system logprintout, JES log for the affected ObjectService Broker address spaces, and anydumps produced) and contact TIBCOSupport.


560 |

S6BXC888ECOMMUNICATIONS IDENTIFIER "%"COULD NOT BE LOCATED


Explanation: An attempt by the current ObjectService Broker communications environmentto contact another Object Service Brokercommunications environment using theCross Memory Services Object ServiceBroker Communications Implementationfailed because the target Object ServiceBroker communications environment couldnot be located in any address space withinthe current image of z/OS. This may benormal, if the target Object Service Brokercommunications environment is usuallyexecuted on another machine (under anotherimage of z/OS).

Action: If the target Object Service Brokercommunications environment is required,ensure that it is executing and hassuccessfully initialized its Object ServiceBroker communications environment.

S6BXC950WUNABLE TO SERIALIZE CROSS-MEMORYENVIRONMENT, RESOURCE OWNED BY %,ASID= X'%'


Explanation: This message is issued if an ObjectService Broker address space is attempting toinitiate or terminate the use of a CrossMemory Services environment, but is unableto obtain control of the Object Service BrokerCross Memory Services environmentresource needed to ensure the integrity ofthat environment during the process.

While attempting to gain control of theObject Service Broker Cross MemoryServices environment resource, the ObjectService Broker address space detected that

control of that resource is held by anotherObject Service Broker address space, and allindications are that the other Object ServiceBroker address space is not going to releaseits control of the Object Service Broker CrossMemory Services resource. Something hassuspended this "culprit" Object ServiceBroker address space while it was intransition and owning control of the ObjectService Broker Cross Memory Servicesenvironment resource.

For example, a user might have pressed the<ATTN>/<PA1> key to interrupt theexecution of an Object Service BrokerExecution Environment executing underTSO without taking any subsequent actionto continue or terminate the execution of theObject Service Broker ExecutionEnvironment.

This message provides the followinginformation:

• The name of the Object Service Brokeraddress space that currently has control ofthe Object Service Broker Cross MemoryServices environment in question.

• The ASID, which is the hexadecimalinterpretation of the z/OS Address SpaceIdentifier of the address space thatcurrently has control of the Object ServiceBroker Cross Memory Servicesenvironment in question.

Together these two data items uniquelyidentify the culprit Object Service Brokeraddress space that is impeding the progressof the Object Service Broker address spacethat is attempting to initiate or terminate theuse of the Object Service Broker CrossMemory Services environment.

This message is always followed by:

S6BXC951R REPLY "RETRY" OR "DEFER"


| 561

which provides the system operator with ameans to direct the Object Service Brokeraddress space on how to proceed.

Action: This message provides the systemoperator with the identity of the culpritObject Service Broker address space that hascontrol of the Object Service Broker CrossMemory Services environment resource. Theoperator can use this identity to determinewhether the culprit Object Service Brokeraddress space is still legitimate or if it shouldbe purged from the system.

The system operator can make this decisionbased on the status of the culprit ObjectService Broker address space:

• If the culprit Object Service Broker addressspace is swapped out and/or notconsuming any CPU resources, it is notgoing to be able to release control of theObject Service Broker Cross MemoryServices environment that it is holding.

• If the culprit Object Service Broker addressspace is consuming processor resources,then it may be about to complete itsprocessing and release its control of theObject Service Broker Cross MemoryServices environment.

The system operator can do one of thefollowing:

• If the culprit Object Service Broker addressspace does not appear to be consumingany system resources, the operator couldpurge it from the system by canceling it.The operator should then reply with"RETRY" to message S6BXC951R (if it hasnot already been deleted from the systemconsole). Processing by the Object ServiceBroker address space that issued thismessage then proceeds. If another ObjectService Broker address space also hascontrol of the Object Service Broker CrossMemory Services environment resourceand will not release it, this message is

reissued and additional assessment andaction as described above may be required.

• If the culprit Object Service Broker addressspace is consuming system resources, theoperator could decide to allow the culpritObject Service Broker address space moretime to release its control of the ObjectService Broker Cross Memory Servicesenvironment. The operator should replywith "RETRY" to message S6BXC951R; thiscauses the message issuer to reassess thesituation and reissue the message if theassessment does not change.

• If the Object Service Broker address spacethat issued this message is attempting toinitiate the use of an Object Service BrokerCross Memory Services environment, theoperator could decide to bypass its use ofCross Memory Services, for the time being.The operator should reply with "DEFER"to message S6BXC951R; this causes theObject Service Broker address space tocontinue without the use of Object ServiceBroker Cross Memory Services. Theoperator can use the COMRESTARTcommand to direct the Object ServiceBroker address space to reattemptinitialization of Object Service BrokerCross Memory Services at a later time.

• If the Object Service Broker address spacethat issued this message is attempting toterminate the use of an Object ServiceBroker Cross Memory Servicesenvironment, a reply of "DEFER" tomessage HRNXC951R is treated the sameas a reply of "RETRY". This means that theculprit Object Service Broker addressspace must release the Object ServiceBroker Cross Memory Servicesenvironment resource or be purged fromthe system, in either case allowing theObject Service Broker address space thatissued the message to proceed with itstermination processing.


562 |

If no reply to message S6BXC951R isprovided within 5 minutes of the time thatthis message is issued, the issuing ObjectService Broker address space simulates areply of "DEFER" and proceeds withprocessing accordingly.

S6BXC951RREPLY "RETRY" OR "DEFER"


Explanation: This message is issued inaccompaniment with message S6BXC950W,in order to permit the System Operator toprovide a reply to message S6BXC950W, anddirect subsequent processing of the situationthat message S6BXC950W describes.

Action: See the Action description of messageS6BXC950W for a complete description ofhow to deal with this message.

S6BXC992ECROSS-MEMORY CLEANUP CANNOTCONTINUE - INVALID CSA STRUCTUREDETECTED FOR % (ASID X'%').


Explanation: Unilateral resource cleanupprocessing cannot identify the addressspace(s) that require cleanup action. Thecontrol blocks that identify established crossmemory communicants have beencorrupted.

The first variable item represents the nameof the Object Service Broker environmentinvolved. The second variable represents the

address space identifier of the z/OS addressspace involved.

Action: This message is only significant to ObjectService Broker and does not necessarilyindicate an error that has impact on z/OS.When issued, the following symptoms maybe displayed:

• A user may appear to be logged on afterthe Execution Environment that supportedthe user has terminated. The user is unableto re-logon to the same Data Object Broker.

• Data access requests from other users maybe queued indefinitely because of locksstill held by the user that appears to belogged on.

If any of these symptoms are displayed, dothe following:



• Collect any diagnostic informationavailable (system log printout, JES log forthe affected Object Service Broker addressspaces, and any dumps) and contactTIBCO Support.


| 563

S6BXC995WMVS CROSS-MEMORY SERVICESUNAVAILABLE, NO RESOURCE MANAGERINSTALLED


Explanation: The Object Service Broker CrossMemory Services CommunicationsImplementation could not be initialized,because the Object Service Broker MVSResource Manager Module was not found onthe system, and could not be dynamicallyinstalled.

Action: Determine why the Object Service BrokerMVS Resource Manager Module could notbe dynamically installed. This information isobtained from messages that have beenissued prior to this one. Correct the situationand restart the Object Service Broker Region.

S6BXC996WMVS CROSS-MEMORY SERVICESUNUSABLE, SYSTEM AX SET IN ADDRESSSPACE


Explanation: During the process of initializingthe Object Service Broker Cross MemoryServices Communications Implementation, itwas found that the z/OS address space hadalready obtained a System Authority levelthat permits access to all other addressspaces under the same image of z/OS.Initialization of the Object Service BrokerCross Memory Services would rescind thisSystem Authority level, so it cannot be usedat this time.

Action: Determine how the Object Service BrokerRegion's address space was able to obtain theSystem Authority to access other addressspaces (Object Service Broker does notattempt to obtain this authority itself), and

assess whether or not it is necessary. Such anauthority level may be cause for concern ifunscreened User External Routines are beinginvoked by Object Service Broker Rules.

S6BXC999EMVS % REQUEST FAILED, R15=X'%'


Explanation: A request for a system serviceprovided by z/OS failed. A Return Code wasprovided by z/OS in register 15 describingthe reason for the request failure. The requestis one of the following:

• ESTAE

• GQSCAN

• GETMAIN

• FREEMAIN.

Action: Refer to the appropriate z/OS manual fora description of the service requested and thereason for the failure as described by theReturn Code. Determine remedial action byconsidering the information provided in themanual. If the message persists, contactTIBCO Support.


564 |


Documents

Messages With Identifiers - TIBCO Software · 2012-07-31 · TIBCO Object Service Broker Messages With Identifiers |vii Preface TIBCO® Object Service Broker is an application development