530
TIBCO ® Object Service Broker Messages Without Identifiers Software Release 6.0 July 2012

TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: TIBCO Object Service Broker · Adabas, 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

Messages Without IdentifiersSoftware Release 6.0July 2012

Page 2: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

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

Page 3: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTIBCO Object Service Broker Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xivHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Using Messages Without Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Use of Variables in the Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Resolving Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Messages beginning with: " . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Messages beginning with: #. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Messages beginning with: $. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Messages beginning with: % . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Messages beginning with: ( . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Messages beginning with: * . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Messages beginning with: = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Messages beginning with: @. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Messages beginning with: A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Messages beginning with: B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Messages beginning with: C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Messages beginning with: D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Messages beginning with: E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Messages beginning with: F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Messages beginning with: G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Messages beginning with: H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

Messages beginning with: I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

Messages beginning with: J. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

TIBCO Object Service Broker Messages Without Identifiers

Page 4: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

iv | Contents

Messages beginning with: K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Messages beginning with: L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Messages beginning with: M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Messages beginning with: N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Messages beginning with: O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Messages beginning with: P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Messages beginning with: Q. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Messages beginning with: R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Messages beginning with: S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Messages beginning with: T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

Messages beginning with: U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

Messages beginning with: V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

Messages beginning with: W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

Messages beginning with: X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

Messages beginning with: Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510

Messages beginning with: Numerals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

TIBCO Object Service Broker Messages Without Identifiers

Page 5: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| v

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 without identifiers that re produced byTIBCO Object Service Broker.

Topics

• Related Documentation, page vi

• Typographical Conventions, page xi

• Connecting with TIBCO Resources, page xiv

TIBCO Object Service Broker Messages Without Identifiers

Page 6: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

vi | 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.

TIBCO Object Service Broker Messages Without Identifiers

Page 7: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

Preface | vii

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.

TIBCO Object Service Broker Messages Without Identifiers

Page 8: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

viii | 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.

TIBCO Object Service Broker Messages Without Identifiers

Page 9: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

Preface | ix

• 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.

TIBCO Object Service Broker Messages Without Identifiers

Page 10: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

x | 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.

TIBCO Object Service Broker Messages Without Identifiers

Page 11: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

Preface | xi

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

TIBCO Object Service Broker Messages Without Identifiers

Page 12: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

xii | 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

TIBCO Object Service Broker Messages Without Identifiers

Page 13: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

Preface | xiii

{ } 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

TIBCO Object Service Broker Messages Without Identifiers

Page 14: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

xiv | 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.

TIBCO Object Service Broker Messages Without Identifiers

Page 15: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 1

Using Messages Without Identifiers

This chapter describes how to make use of the messages without identifiers thatare issued by TIBCO Object Service Broker.

Topics

• Introduction, page 2

TIBCO Object Service Broker Messages Without Identifiers

Page 16: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

2 | Using Messages Without Identifiers

Introduction

The error messages listed in this manual are issued by TIBCO Object ServiceBroker modules and have no identifiers. They appear in alphabetic order.

Use of Variables in the MessagesWithin the message, percent symbols(%) or number signs (#) may representvariable information such as rule names or the number of occurrences in a table.

If the message you are looking for is a warning message that tells you to press akey to confirm an action, you may find the message without the WARNING at thebeginning, or the “press <pfkey> to confirm” at the end. For example, if you seethe following message on your screen:

WARNING: About to delete report “DEPT_SALARY”, press <PF22> to

confirm.

and you cannot find this message beginning with WARNING, you may find it inthis manual as:

About to delete report “%”

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 xiv.

TIBCO Object Service Broker Messages Without Identifiers

Page 17: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 3

Messages beginning with: "

"%" exists already as a non-screen table;choose another nameSource: Screen Definer

Explanation: A screen table cannot have thesame name as another table.

Action: Enter a new name for the screen table.

"%" FOUND AT OFFSET +XXXXSource: S6BTLADM - PAGE IMAGES

Explanation: The specified target of a searchfunction has been located at the indicatedoffset within the page image.

Action: No action.

"%" has been used as a field nameSource: HLIPREPROCESSOR

Explanation: The indicated name has alreadybeen used for a field name.

Action: Change the name.

"%" has been used as a parameter nameSource: HLIPREPROCESSOR

Explanation: The indicated name has alreadybeen used for a parameter name.

Action: Change the name.

"%" has been used as a table nameSource: HLIPREPROCESSOR

Explanation: The indicated name has alreadybeen used.

Action: Change the appropriate identifier.

"%" is a non-existent value of parameter"%"Source: Report Generator

Explanation: There is no such parameter value inthe parameterized table for the specificparameter.

Action: Check if the value entered is wrong or ifthe parameterized table does not have thevalue you expected.

"%" is an invalid logical valueSource: Report Server

Explanation: You called the tool $RPTOVERLAP,and the blank overlap flag does not have avalid logical value.

Action: Use the Rule Editor to change the call to$RPTOVERLAP to produce a valid logicalvalue for the final argument.

TIBCO Object Service Broker Messages Without Identifiers

Page 18: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

4 |

"%" is an invalid pad justification forfunction PAD; use "RIGHT", "LEFT", or"CENTRE"Source: Interpreter

Explanation: The value for the argumentJUSTIFICATION of the tool PAD does notmatch one of the following:

• RIGHT

• LEFT

• CENTRE or CENTER

Using the first letter only is also valid.

Action: Correct the value.

"%" is an invalid rule library searchorder; valid values are S/I/LSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

"%" is an invalid UNITSource: Screen Definer

Explanation: The value you have assigned forUNIT is invalid.

Action: Enter a valid value. Check with yourSystem Administrator if problems persist.

"%" is incompatible with default dateformat "%" of "%"Source: Report Generator

Explanation: The indicated parameter value isnot in the required date format.

Action: Correct the parameter value by enteringthe value with date format yyyy-mm-ddwithout quotation marks.

"%" is invalid as source of % table "%"Source: TAM

Explanation: The specified parameter (PRM) orsubview (SUB) table has a source that is notan allowed table type for SUB or PRM tables.

Action: Correct the source table name using theTable Definer.

"%" is not a field of table "%"Source: Definition Differences

Explanation: The given name is not a field of thetable.

Action: Correct the field list.

"%" is not a field of table "%"Source: Interpreter

Explanation: You tried to access a field of a table,but the specified table does not contain thatfield.

Action: Verify the table definition or the fieldname spelling.

TIBCO Object Service Broker Messages Without Identifiers

Page 19: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 5

"%" is not a parameter name of table "%"Source: Interpreter

Explanation: An event rule was activated by adata access on a table. This event rule iscalled PARMVALUE. The argumentPARMNAME of PARMVALUE does notcorrespond to a parameter of the table thatwas accessed.

Action: Verify that the PARMNAME value is avalid parameter of the table.

"%" is NOT a parameter of this tableSource: Unload

Explanation: In INSTANCE SELECT you haverequested the FIND function. However theparameter name supplied for this function isnot a parameter of the table whose instancesare displayed.

Action: Correct the name of the requiredparameter for the FIND function.

"%" is not a report field of report table"%"Source: Report Server

Explanation: The source of a derived report fieldrefers to a name that is neither a field of abody or fixed table nor a report field.

Action: Use the Report Definer to correct thespelling error in the source for the reportfield.

"%" is not a titles report table of report"%"Source: Report Server

Explanation: You specified the indicated reporttable in a call to the $RPTOVERLAP tool.Either it is not a report table of the indicatedreport, or it is not a report table with titles.

Action: Do one of the following:

• Use the Report Definer to ensure that thereport table has titles.

• Use the Rule Editor to change the name ofthe report table or the report.

"%" is not a valid number of occurrences(1-999 or "*")Source: Screen Definer

Explanation: You have not entered either apositive integer, or an asterisk (*) in the MAXOCCUR prompt.

Action: Enter either a positive integer, or anasterisk (*).

"%" is referenced twice (in list, andthrough parent %)Source: Copy Definition

Explanation: An object has been linked to aparent, and the parent is an entry by itselfwith the parent only flag set to N. Therefore,the child is being referenced twice: once inthe list (explicitly), and the second time bythe parent entry (implicitly).

Action: Either remove the child entry, or set theparent only flag for the parent to Y.

TIBCO Object Service Broker Messages Without Identifiers

Page 20: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

6 |

"%" is referenced twice (in list, andthrough parent %)Source: Copy Defn/Data

Explanation: You have specified objects to copysuch that a child object is referenced twotimes: once explicitly and once through aparent whose children are also to be copied.

Action: No action required.

"%" must be a screen table of Screen "%"Source: Screen Definer

Explanation: You have entered the name of ascreen table in the SCROLL AMOUNTENTRY or DEFINE CURSOR POSITIONspecification. The screen table named is not ascreen table of the Screen being defined.

Action: Give the name of a screen table includedin this Screen definition.

"%" overlaps "%" (which needs an areaof % rows X % columns)Source: Screen Definer

Explanation: You have included and positioned ascreen table in the Screen definition. Thisscreen table overlaps another screen table.

Action: Reposition either the screen table that isoverlapping, or the screen table that is beingoverlapped.

"%" screen table will overlap % borderSource: Screen Definer

Explanation: You have included and positioned ascreen table in the Screen definition. Thisscreen table overlaps one of the TOP,BOTTOM, LEFT, or RIGHT boundaries.

Action: Reposition the screen table.

"%" table request is not supportedSource: TAM

Explanation: Inappropriate access to tablerequested.

Action: Reexamine application. Some builtinfunctions are not allowed against remotetables. Some accesses are not allowed, basedon the table type.

"@" NOT FOUND WITHIN PAGEIMAGESource: S6BTLADM - PAGE IMAGES

Explanation: The specified search target couldnot be located between the current displayposition and the end of the page image.

Action: No action.

"^" field marker was typed in oroverwritten; image restoredSource: Screen Definer

Explanation: You have typed in, or overwritten, a(^) field marker. This is not permitted, so theImage Area has been restored.

Action: No action required.

"Data" must be N for %-type tablesSource: Object Set Definer

Explanation: This type of table does not havepermanent data. You can include in an objectset only data from tables that havepermanent data.

Action: Set DATA to N.

TIBCO Object Service Broker Messages Without Identifiers

Page 21: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 7

"Data" must be Y, in order to specifyparametersSource: Object Set Definer

Explanation: The DATA field must be set to Ybefore you are allowed to specify parametersfor the table.

Action: Set the DATA field to Y before trying tospecify parameters.

"Element" not specified or invalidSource: Report Server

Explanation: $RPTSKIPLINES was called withan invalid value for Element. Valid values areblank, "T", "H", "R", or "*".

Action: Call $RPTSKIPLINES with a valid valuefor Element.

"END-EXEC" was not found;statement(s) ignoredSource: Host Language Interface

Explanation: A query was started by using theSQL brace EXEC SQL but was not terminatedby END-EXEC.

Action: Insert END-EXEC to specify the end-of-query location.

"End of box" without a box startSource: Character-based Text Editor

Explanation: You included the "end of box"command (.ebox) without the "start of box"command (.box).

Action: Remove the "end of box" command, orsupply the "start of box" command.

"INCLUDE" statement is missingSource: HLIPREPROCESSOR

Explanation: There is no $ INCLUDE HURONstatement in the deck.

Action: Enter the following statement in theappropriate place:

$ INCLUDE HURON

"Library/Env" is invalid forOBJECTSET; use "Default" fieldsSource: Copy Defn/Data

Explanation: You tried to specifyLIBRARY/ENV information for an object set.Since both types of information apply toobject sets, the information is ambiguous andmust be clarified.

Action: Remove the information from theLIBRARY/ENV field and fill in the defaultfields.

"Library/Env" is invalid forOBJECTSET; use Default fieldsSource: Copy Definition

Explanation: You specified a value in theLIBRARY/ENV field for an object of typeOBJECTSET. However, an object set requiresboth Library and Environment to identify allobjects that are included in it.

Action: Remove the entry from theLIBRARY/ENV field and put both a DefaultLibrary and a Default Environment in theSource specification section.

TIBCO Object Service Broker Messages Without Identifiers

Page 22: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

8 |

"List End" without "List"Source: Character-based Text Editor

Explanation: You have included one of thefollowing LIST END commands withoutproviding a list:

• listend

• edl

• eol

• eul

Action: Remove the command, or supply a list.

"MAX ACR" must equal 0 for a titlesreport tableSource: Report Definer

Explanation: Titles report tables (TITLEONLY=Y) are not allowed to repeat across.

Action: Change the MAX ACR value to 0.

"MAX OCC" must equal 1 for a titlesreport tableSource: Report Definer

Explanation: The titles report tables (TITLEONLY=Y) are only allowed to have oneoccurrence per page.

Action: Change the MAX OCC value to 1.

"NEW PAGE" can only be specified for"BREAK BY" fieldsSource: Report Definer

Explanation: NEW PAGE was requested on thecontrol screen without the specification of aBREAK BY field. NEW PAGE is used toindicate that a change in value of thespecified BREAK BY field should cause apage eject.

Action: Fill in the desired BREAK BY field orremove the NEW PAGE indicator.

"NOT" operator not allowed for NAMEor UNIT querySource: Global Cross Ref. Search

Explanation: You cannot use the NOT operator(^) for a query by NAME or UNIT.

Action: Change the query.

"Skip lines after" not specified ornegativeSource: Report Server

Explanation: $RPTSKIPLINES was called withan invalid value for the number of lines to beskipped after the specified element. Thevalue given must be a positive number.

Action: Specify a valid number of lines to beskipped.

TIBCO Object Service Broker Messages Without Identifiers

Page 23: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 9

"Skip lines before" not specified ornegativeSource: Report Server

Explanation: $RPTSKIPLINES was called withan invalid value for the number of lines to beskipped before the specified element. Thevalue given must be a positive number.

Action: Specify a valid number of lines to beskipped.

"TABLEEND" exception raised for table"%"Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 24: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

10 |

Messages beginning with: #

# of decimal places in field %Source: Field Dictionary

Explanation: The number of decimal placesspecified for the field is incompatible withthe syntax and/or type of field.

Action: Specify number of decimal places withinthe range as indicated by message.

TIBCO Object Service Broker Messages Without Identifiers

Page 25: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 11

Messages beginning with: $

$BINDOBJECT ERROR - BINDREQUIRES DBA CLEARANCESource: Builtin Routines

Explanation: A call to $BINDOBJECT was issuedby a non-level-7 user.

Action: Log in as a level-7 user and rerun the rulethat calls $BINDOBJECT.

$BINDOBJECT ERROR - CALLEDBEFORE INITIALIZATIONSource: Builtin Routines

Explanation: The $BINDOBJECT builtin hasbeen called before the Rules Manager hasbeen initialized.

Action: Wait till later in the session before callingthe $BINDOBJECT builtin.

$BINDOBJECT ERROR - INVALIDLIBRARY SPECIFIEDSource: Builtin Routines

Explanation: The library name specified in a$BINDOBJECT call was neither the name ofthe system library nor the installation library.

Action: Correct the name of the library in the$BINDOBJECT call.

$GETLOGSTATS must be calledbefore using $GETLOGRECSource: Builtin Routines

Explanation: In a transaction, $GETLOGSTATSmust be called before any call to$GETLOGREC can be issued.

Action: Insert a call to $GETLOGSTATS.

$RULENAME failed:LEVEL/TRANSACTION COUNTcombination invalidSource: Builtin Routines

Explanation: Either $RULENAME was issuedwith invalid argument values or there are notenough rules on the execution call stack tosatisfy the request. A recoverableRANGERROR is raised.

Action: Correct the invalid arguments.

$SYSCALL "%" for "%" failed; >%<Source: Builtin Routines

Explanation: The specified routine needsservices from the operating system, but theservices failed for the reason given at the endof this message.

Action: For assistance, show this message to aSystem Programmer.

TIBCO Object Service Broker Messages Without Identifiers

Page 26: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

12 |

$TYPECAST failed: input argumentcontains bad data bytesSource: Builtin Routines

Explanation: $TYPECAST was unable to convertthe input data to the Syntax specified. Arecoverable CONVERSION error is raised.

Action: Correct the input data to allowconversion.

$TYPECAST failed: input argumentspecification not allowedSource: Builtin Routines

Explanation: The specification of the cast is notvalid in Object Service Broker. Anunrecoverable CONVERSION error is raised

Action: Correct the specification of the cast toconform to Object Service Broker standards.

$TYPECAST failed: output argument istoo small to hold resultSource: Builtin Routines

Explanation: The output from the $TYPECAST islonger than the output specification. Thedata is truncated where possible. Arecoverable CONVERSION error is raised.

Action: Either correct the specification of the$TYPECAST output, or if you wanttruncation, trap the CONVERSION error.

$TYPECAST failed: TYPECASTINGnot allowed as specifiedSource: Builtin Routines

Explanation: The input data cannot be cast intothe specified output. A recoverableCONVERSION error is raised.

Action: Correct the specification of the castrequired.

TIBCO Object Service Broker Messages Without Identifiers

Page 27: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 13

Messages beginning with: %

%; Press <%> or type 'CONFIRM'Source: Confirmaction Utility

Explanation: This message gives youinstructions on how to confirm.

Action: Follow the instructions.

%; Type 'CONFIRM'Source: Confirmaction Utility

Explanation: Show the confirmation message.

Action: No action is required.

% "%" cannot be %Source: Rule Editor

Explanation: The message is one of thefollowing:

• LOCAL VARIABLE "%" cannot beCALLED

• PARAMETER "%" cannot be ASSIGNEDTO

Action: Remove the misuse of the local variableor parameter in question.

% % does not existSource: Copy Defn/Data

Explanation: This message indicates that thenamed object does not exist.

Action: No action.

% % failed: %Source: Rule Editor

Explanation: You are unable to delete or save thespecified rule due to locking or security.

Action:

• If due to locking, try again.

• If due to security, contact your DatabaseAdministrator if there is a need for you tobe able to read or modify this rule. TheDatabase Administrator can decide if youshould be given this authority.

% all rights partially completedSource: Manage Promotion Rights

Explanation: Notifies the user that not allpromotion rights have been OBTAINED,RELEASED, or TRANSFERRED.

Action: Read the message log to find out thereasons.

% at action # % statement #Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the TIBCO Object Service BrokerInformation Log.

TIBCO Object Service Broker Messages Without Identifiers

Page 28: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

14 |

% at action #Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

% at condition #Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

% at exception handler "%" statement #% statement #Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

% at exception handler "%" statement #Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

% at exception handler "% %" statement# % statement #Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

% at exception handler "% %" statement#Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

% at unknown statementSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

% cannot be % than %Source: Screen Definer

Explanation: You are trying to define the screentable with invalid values for "Last Col/Row"or for "Empty Occs". You need to modify thevalues so that they are logically correct.

Action: Modify the value at the cursor positionbased on the message.

TIBCO Object Service Broker Messages Without Identifiers

Page 29: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 15

% conversion error detected by functionROUNDSource: Builtin Routines

Explanation: The argument VALUE of theROUND tool cannot be converted to a binary4.

Action: Correct the problem as described by themessage.

% date '%' is an invalid dateSource: Secure Audit Log

Explanation: You specified an invalid date forthe date range to be purged.

Action: Correct the date value and try again.

% does not have permissions to purgethe AuditlogSource: Secure Audit Log

Explanation: You attempted to purge the auditlog contents but you did not have thepermissions to do so.

Action: Contact your security administrator.

% failed: %Source: Definition Differences

Explanation: The DIFFDEFN utility has faileddue to an error which cannot becircumvented by the user. When trying tocompare definitions, a corrupted definitionor unexpected security restriction, or invalidtable or data reference error wasencountered.

Action: No action required although the problemshould be reported.

% failedSource: Interpreter

Explanation: This message is used by the TIBCOObject Service Broke program that producesthe Information Log.

Action: Study the Object Service BrokerInformation Log.

% field "%" cannot be a % fieldSource: Report Generator

Explanation: No field can be an ACROSS BYfield and SORT BY field at the same time.

Action: Remove the field name from theACROSS BY or SORT BY section.

% field "%" does not follow thesequence of % field(s)Source: Report Generator

Explanation: The BREAK BY fields must begiven in the same order as the SORT BYfields. Furthermore, any field that you wantto BREAK BY, you must also SORT BY.

Action: Change the order of the BREAK BY fieldsto match the order of the SORT BY fields, orvice versa.

% for parameter # of table "%"Source: Interpreter

Explanation: An error occurred during theprocessing of the parameters for a table. Thecomplete message describes the nature of theerror.

Action: Study the complete message.

TIBCO Object Service Broker Messages Without Identifiers

Page 30: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

16 |

% inside area occupied by %; modifylast row/colSource: Screen Definer

Explanation: You are trying to define two screentables, but the Origin Row in one screen tableis in conflict with the Last Row in anotherscreen table.

Action: Modify the value for Origin Row or LastRow in one of the screen tables.

% is already in the "%" tableSource: Rule Editor

Explanation: Internal editor error.

The message log contains a more detailederror message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

% is an invalid dateSource: Offline Utilities

Explanation: Date specification has to be in theformat YYMMDD,HHMMSS.

Action: Correct the date format and retry.

% is invalid. Field must exist in tabledefinitionSource: Table Definer

Explanation: The value indicated in the messageis invalid. It must be defined as a field in thetable definition.

Action: Enter a value that is a field in thedefinition.

% is not a valid break eventSource: Debugger Utility

Explanation: This is a warning that you haveentered a blank in the Break Event field of theBreakevent control area.

Action: Specify a valid break event, press<Enter>, or press another key.

% library and % library cannot be thesameSource: Promotion

Explanation: Libraries have to be different.

Action: Ask your System Administrator to checkthe default libraries.

% not allowed between % % and % %Source: Interpreter

Explanation: The operation specified is notsupported between the specifiedcombinations of semantic type and syntax.

Action: Verify that the operation is valid. See theProcessing manual for more informationabout operations.

% of a null value is not allowedSource: Interpreter

Explanation: You tried to do an arithmeticoperation that involved a null value.

Action: Verify that null values do not appear inarithmetic expressions.

TIBCO Object Service Broker Messages Without Identifiers

Page 31: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 17

% required for % of type %Source: Definition Differences

Explanation: You have specified either a RULEbut no LIBRARY or a SCREEN which haspresentation-environment-specific definitioncomponents but no PRESENTATIONENVIRONMENT. This information isrequired to fully identify the object you wishto compare.

Action: For a RULE, specify which LIBRARY therule is to be found in. For a SCREEN specifythe PRESENTATION ENVIRONMENTwhich should be used in the comparison.

% screentable may overlap % borderSource: Screen Definer

Explanation: Based on the width of the screenand the screen table image, the indicated partof the screen table may be overlapped.

Action: Check the screen table's attributes to seeif the screen table needs to be repositioned ormodified.

% segment number "%" is invalid - itmust be numericSource: Promotion

Explanation: You have entered an invalidsegment number.

Action: You can either press <ENTER> for 0 orenter a number for the segment which youwant new table(s) to be stored in.

% table "%" error: %Source: TAM

Explanation: The ending part of the message textmay be:

• Allocation of file % failed. RC=%,ERRCODE=%, INFOCODE=%

• File % not found

• File % is a partitioned data set but amember name was not specified

• File % is a sequential data set but a membername was specified

• File % is not a partitioned data set

• Member % for file % not found

• Data set/member combination % invalid

• Cannot get virtual storage for DCB

• Too many open files

• Open for file % failed

• Open for file % failed - abend code = S%-%

• Open for DDNAME % failed

• Open for DDNAME % failed - abend code= S%-%

The following has occurred:

• The gateway is unable to allocate or openan external sequential or partitioned dataset.

• The data set or member does not exist.

• The data set is the wrong type - eitherpartitioned or sequential.

• Parameters have been specified for a non-partitioned data set.

• There is insufficient below-the-line storageavailable for the DCB.

• Too many Import/Export files arecurrently open.

Action: Do the following:

• Verify that the external data set exists andcontains valid data.

• Verify that parameters have not beenspecified for a non-partitioned data set.

• Consider accessing Import/Export tablesat a separate transaction level so that DCB

TIBCO Object Service Broker Messages Without Identifiers

Page 32: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

18 |

storage may be released at transaction endand therefore be available for reuse.

• Increase the maximum number of openfiles allowed by changing the ExecutionEnvironment parameterSESSIONFILEMAX.

% table "%" exit routine "%": No storagedefinedSource: TAM

Explanation: You specified a user exit routine,but did not specify the amount of workingstorage required by the routine.

Action: When using an exit routine, ensure thatyou specify a value from 1 to 32767 for theEXIT STORAGE field in the table definition.

%=%, it cannot exceed %Source: Table Definer

Explanation: The indicated item has theindicated value, which exceeds the indicatedmaximum.

Action: Reduce the value to less than theindicated maximum.

%=%, it must be %Source: Table Definer

Explanation: The indicated item has theindicated value, but it must be changed to thesecond indicated value.

Action: Change the value to the indicated value.

%= %, is above the range % : %Source: Table Definer

Explanation: The value indicated for the givenitem is above the indicated range. Forexample, if you change the length of avariable length character field from 22 to 300,you see a message similar to this:

Length of field LNAME = 300, is above the range 22 : 254

Action: Reduce the value so that it falls withinthe range given.

%= %, is below the range % : %Source: Table Definer

Explanation: The value indicated for the givenitem is below the indicated range. Forexample, if you change the length of avariable length character field from 127 to 90,you see a message similar to this:

Length of field ADDRESS = 90, is below the range 127 : 254

Action: Raise the value so that it falls within therange given.

TIBCO Object Service Broker Messages Without Identifiers

Page 33: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 19

Messages beginning with: (

(when "%" is displayed on a physicalscreen % rows X % cols)Source: Screen Definer

Explanation: This message is part of the overlapwarning messages that may appear at theend of a Screen Definer session, after youhave saved and viewed the message log. Thesaved screen has overlapping boundariesthat cannot be displayed on a screen with thecurrent dimensions. Detailed information onboundaries is in the message log.

Action: If you do not intend to display the screenon a physical screen that is larger than thecurrent physical screen, fix the overlaps asindicated in the message log after you savethe screen definition.

TIBCO Object Service Broker Messages Without Identifiers

Page 34: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

20 |

Messages beginning with: *

**** % all rights completed ****Source: Manage Promotion Rights

Explanation: The tool has completed performingone of the following operations on an object:OBTAIN all rights, RELEASE all rights, orTRANSFER all rights.

Action: No action required.

**** Begin to copy object "%" ****Source: Copy Definition

Explanation: Informs you of the starting point ofthe copy process for the specified object.

Action: No action required.

**** Begin to delete object "%" ****Source: Delete Definition

Explanation: Notifies the user of the startingpoint of the DELETE process.

Action: No action required.

**** Begin to print all definitions forobject "%" ****Source: Print Definition

Explanation: The tool is starting to print alldefinitions for the specified object.

Action: No action required.

**** Beginning % all rights for object"%" ****Source: Manage Promotion Rights

Explanation: The tool starts performing one ofthe following operations on an object:OBTAIN all rights, RELEASE all rights, andTRANSFER all rights.

Action: No action required.

**** Copy process ended ****Source: Copy Definition

Explanation: Informs you that the copy processhas ended.

Action: No action required.

**** Delete completed ****Source: Delete Definition

Explanation: Notifies the user that the DELETEprocess has completed.

Action: No action required.

**** Print all definitions completed ****Source: Print Definition

Explanation: Notifies the user that PRINTDEFNis finished.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 35: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 21

*** At Left edge of Window ***Source: Object Manager

Explanation: You pressed <PF10> to scroll thescreen to the left, but no further movement tothe left is possible.

Action: No action required.

*** At Right edge of Window ***Source: Object Manager

Explanation: You pressed <PF11> to scroll thescreen to the right, but no further movementto the right is possible.

Action: No action required.

*** Bottom of Window - % objects exist***Source: Object Manager

Explanation: You pressed <PF8> to scroll down,but no further movement down is possible.

Action: No action required.

*** Did NOT unload defn of % object"%"; already in DATASETSource: Unload

Explanation: The named object was notunloaded into the data set more than once.This situation arises when you request anunloading of two distinct objects and one ofthe objects is contained in the other, or bothobjects contain the same third object.

Action: No action required.

*** No such % as "%"; NOT unloadedSource: Unload

Explanation: One of the objects you requested tounload included another object by reference.Because this other object does not exist, itwas not unloaded.

Action: No action required.

*** Top of Window ***Source: Object Manager

Explanation: You pressed <PF7> to scroll up, butno further movement up is possible.

Action: No action required.

***Cannot INSERT % for Key=%: %Source: Unload

Explanation: During LOAD, an attempt wasmade to insert a data occurrence into a table.The insert failed for the reason indicated.

Action: Action depends upon which occurrenceshould prevail:

• If the occurrence in the file should beloaded, then the occurrence in the tableshould be deleted before the load.

• If the occurrence in the table should not beoverwritten, no action is required.

TIBCO Object Service Broker Messages Without Identifiers

Page 36: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

22 |

Messages beginning with: =

================ %=================== level #===========================Source: Interpreter

Explanation: This message is used by the ObjectService Broker progran that produces theInformation Log. It signals the end of the listof information for the trigger rule that failed.

Action: Study the Object Service BrokerInformation Log.

================ % for table "%"===== level #===========================Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log. It signals the beginning ofinformation about the trigger rule that failed.

Action: Study the Object Service BrokerInformation Log.

TIBCO Object Service Broker Messages Without Identifiers

Page 37: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 23

Messages beginning with: @

@DB2FIELDS definition error:Source: TDS

Explanation: @DB2FIELDS is defined incorrectly.This error occurred when you tried to accessthe specified table.

Action: Contact TIBCO Support.

@DB2FIELDS index page found fortableSource: TDS

Explanation: A large number of DB2 fields aredefined for the table, causing a data pagesplit in @DB2FIELDS.

Action: Contact TIBCO Support.

@DB2FIELDS table not found for tableSource: TDS

Explanation: The specified DB2 table is notcorrectly defined to Object Service Broker;@DB2FIELDS fields has no occurrences forthe table.

Action: Check the DB2 table definition.

@DB2TABLES definition error:Source: TDS

Explanation: @DB2TABLES is definedincorrectly. This error occurred when youtried to access the specified table.

Action: Contact TIBCO Support.

@DB2TABLES entry not found for tableSource: TDS

Explanation: The specified DB2 table is notcorrectly defined to Object Service Broker.

Action: Check the DB2 table definition.

@IMSCONTROL contains null fieldname - tableSource: TDS

Explanation: A value access field for the IMStable is incorrectly defined.

Action: Redefine the value access fields for thetable.

@IMSDBD definition error:Source: TDS

Explanation: @IMSDBD is incorrectly defined.

Action: Contact TIBCO Support.

@IMSDBD entry not found for IMSfieldSource: TDS

Explanation: The IMS database definition ismissing fields used as value access fields inthe IMS table.

Action: Do the following:

1. Verify the IMS database definition.

2. If necessary, rerun the extract utility.

TIBCO Object Service Broker Messages Without Identifiers

Page 38: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

24 |

@IMSDBD table not found for databaseSource: TDS

Explanation: The IMS database is incorrectlydefined to Object Service Broker.

Action: Do the following:

1. Check the database definition.

2. If necessary, rerun the extract utility.

@IMSDBS definition error:Source: TDS

Explanation: @IMSDBS is defined incorrectly.

Action: Contact TIBCO Support.

@IMSDBS entry not found for databaseSource: TDS

Explanation: The IMS database was not correctlydefined to Object Service Broker.

Action: Do the following:

1. Check the database definition.

2. Rerun the extract utility.

@IMSFIELDS definition error:Source: TDS

Explanation: @IMSFIELDS is not definedcorrectly.

Action: Contact TIBCO Support.

@IMSFIELDS index page found fortableSource: TDS

Explanation: A large number of IMS fields aredefined for the table, causing a data pagesplit in @IMSFIELDS.

Action: Contact TIBCO Support.

@IMSFIELDS table not found for tableSource: TDS

Explanation: The IMS table is not definedcorrectly.

Action: Check the IMS table definition.

@IMSSEGS definition error:Source: TDS

Explanation: @IMSSEGS is not defined correctly.

Action: Contact TIBCO Support.

@IMSSEGS entry not found forsegmentSource: TDS

Explanation: The IMS database is not definedcorrectly.

Action: Do the following:

1. Check the database definition.

2. If necessary, rerun the extract utility.

@IMSTABLES definition error:Source: TDS

Explanation: @IMSTABLES is definedincorrectly.

Action: Contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 39: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 25

@IMSTABLES entry not found for tableSource: TDS

Explanation: The IMS table was not correctlydefined to Object Service Broker.

Action: Check the IMS table definition andcontact TIBCO Support.

@PROMBINDOBJS completedsuccessfullySource: Promotions Bind Tools

Explanation: The @PROMBINDOBJS toolcompleted successfully.

Action: No action required.

@PROMBINDOBJS ended with error"%"Source: Promotions Bind Tools

Explanation: The @PROMBINDOBJS toolencountered the specified error andterminated.

Action: Resolve the error specified and re-run@PROMBINDOBJS.

@PROMUNBINDOBJS completedsuccessfullySource: Promotions Bind Tools

Explanation: The @PROMUNBINDOBJS toolcompleted successfully.

Action: No action required.

@PROMUNBINDOBJS ended witherror "%"Source: Promotions Bind Tools

Explanation: The @PROMUNBINDOBJS toolencountered the specified error andterminated.

Action: Resolve the error specified and run@PROMBINDOBJS before re-running@PROMUNBINDOBJS.

TIBCO Object Service Broker Messages Without Identifiers

Page 40: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

26 |

Messages beginning with: A

A % field must have zero number ofdecimal placesSource: Screen Definer

Explanation: In the Screen Table Painter, youtried to define a field that has a nonzeronumber of decimal places, but the syntax ofthe field does not permit decimal places (e.g.,COUNT).

Action: Do one of the following:

• Change the syntax of the field if yourequire decimal precision.

• Change the number of decimal places tozero if you do not require decimalprecision.

A % parameter is required for % tableSource: Table Definer

Explanation: Required parameter definitionmissing.

Action: Define the required parameter class asindicated in the message.

A constant cannot start a statementSource: Rule Editor

Explanation: A syntax error is in the rule; aconstant is at the beginning of a statement.For example:

'CALL' TEST

Action: Correct the statement.

A DB2 Gateway must be up to defineresult set cursorsSource: Table Definer

Explanation: In order to extract result set cursorinformation the stored procedure must beaccessed. To do this a gateway must beavailable.

Action: Bring up a gateway

A definition for "%" already exists, notoverwrittenSource: Copy Definition

Explanation: The definition of the specifiedobject exists, and the OVERWRITE flag is setto NO; therefore, it is not copied oroverwritten.

Action: Either change the overwrite flag to Y, orrename the destination object. This is part ofthe audit trail.

A definition for % already exists, notoverwrittenSource: Copy Defn/Data

Explanation: This message indicates that anexisting definition was not overwritten as aresult of a requested copy which specified nooverwrite.

Action: No action.

TIBCO Object Service Broker Messages Without Identifiers

Page 41: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 27

A FORALL loop cannot contain a "%"statementSource: Rule Editor

Explanation: An invalid statement appears in aFORALL loop.

Action: Remove the invalid statement.

A list item without a list startSource: Character-based Text Editor

Explanation: The tag "item" or "li" appearsoutside a list (preceded by a period or acolon).

Action: Do one of the following:

• Remove the tag.

• Put "ol" and "eol" tags (each preceded by aperiod or a colon) before and after the listitem tag.

• Put "list" and "listend" tags (each precededby a period or a colon) before and after thelist item tag.

A maximum of % distribution points isallowedSource: Table Definer

Explanation: You have specified moredistribution points than that allowed for CLCtable.

Action: Remove the extra distribution pointsdefined.

A member for Static SQL generatedmust be suppliedSource: Static SQL for DB2 Gateway

Explanation: The Static SQL interface is trying togenerate Static SQL code, but no membersuffix has been provided. The member suffixused when creating the PDS member nameswill hold the Assembler code generated.

Action: Supply a member suffix that is notcurrently in use.

A name is required for each definitionSource: Table Definer

Explanation: Each parameter, field, or eventrequires a name.

Action: Enter the missing name.

A new name is required for "%"Source: Copy Definition

Explanation: You require a new name for thisobject to be able to copy it.

Action: Enter a new name for the object.

A new name is required for "%"Source: Copy Defn/Data

Explanation: You are copying an object but youhave not specified the new name for thatobject and one cannot be defaulted.

Action: Supply a new name for the object.

TIBCO Object Service Broker Messages Without Identifiers

Page 42: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

28 |

A NUMERIC command is only valid ifused with the <Shift> PF keySource: Report Definer

Explanation: You entered a number in thecommand line. This is only valid when youuse the <Shift> PF key because the numberindicates the number of columns to shift leftor right.

Action: If you wish to shift, press the <Shift> PFkey. Otherwise, type in a valid nonnumericcommand.

A screen and screen table must bespecifiedSource: Menu Definer

Explanation: You cannot use this menu stylewithout supplying a screen with a suitablescreen table.

Action: Specify a screen and screen table. Thescreen and screen table must exist before youcan define the menu.

A Screen name is requiredSource: Screen Definer

Explanation: You tried to invoke the ScreenDefiner by executing the rule DRAW withoutproviding a Screen name.

Action: Provide a Screen name, or set the cursorto the workbench item Define Screen andpress <Enter>. This will invoke the listing ofexisting Screen names. Enter S next to theScreen you wish to select.

A screen table can have maximum %rows; this one has %Source: Screen Definer

Explanation: For any screen table definition, thenumber of rows must not exceed the lengthof the physical screen (less one line forfeedback messages). For your screen, youhave defined too many rows for the screentable.

Action: Correct the definition so that there are nomore rows than the number given in themessage.

A screen table cannot be referred tomore than once per screenSource: Screen Definer

Explanation: Screen table names must be uniquewithin a Screen definition.

Action: Remove the duplicate entry.

A screen table must have some contentto SAVE; <PF12> to CANCELSource: Screen Definer

Explanation: You have entered the ScreenPainter, not entered any information, andthen pressed <PF3> to save and exit.

Action: Press <PF12> to cancel the Paint activity,or enter some content into the screen tabledefinition.

TIBCO Object Service Broker Messages Without Identifiers

Page 43: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 29

A screen table with Title must haveSCROLL="Y"Source: Screen Definer

Explanation: The SCROLL prompt, in a Screendefinition, must be Y for a screen table if thescreen table has TITLE ^= 0.

Action: Set the SCROLL prompt to Y, or changethe definition so that the screen table doesnot contain titles (i.e., set TITLE = 0).

A title is required for each abbreviationSource: Menu Definer

Explanation: Every abbreviation mustcorrespond to some rule.

Action: Type in the rule name or remove theabbreviation.

A valid % must be supplied for % "%"Source: Copy Definition

Explanation: The object is incompletely specifiedfor the operation requested, e.g., a RULEobject specified without a LIBRARYidentifier.

Action: Specify the appropriate information toallow the operation to be completed.

A valid % must be supplied for % "%"Source: Copy Defn/Data

Explanation: You have specified an object whichrequires additional information to identify.For example, you have specified a rulewithout the library.

Action: Supply the missing information.

A window of this type CANNOT beexpanded furtherSource: Rule Editor

Explanation: Another window cannot be nested.

Action: No action required.

Abbreviation "%" is not validSource: Session Manager

Explanation: You entered an abbreviation thatdoes not appear in your menu.

Action: Correct the abbreviation.

About to % "%"Source: Report Definer

Explanation: About to perform an action thatrequires confirmation.

Action: Confirm action if desired.

About to % rule %Source: Rule Editor

Explanation: This message will be displayed inconjunction with message 39 of this module,and message 38 will precede message 39. Youhave received a warning message about anaction that is about to be performed on a rule.

Action: No action required.

About to % Screen "%"Source: Screen Definer

Explanation: This is a confirmation of one of thefollowing actions:

• You have requested that a Screendefinition be deleted.

TIBCO Object Service Broker Messages Without Identifiers

Page 44: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

30 |

• You have changed the name of the Screento the name of another existing Screen andthen pressed <PF3> to save. Thisconstitutes an overwrite.

You are being prompted for a confirmation.

Action: Do one of the following:

• Press <PF22> to confirm the request.

• Press any other function key to cancel therequest.

About to % screen table "%"Source: Screen Definer

Explanation: You have requested to delete ascreen table definition. This is a confirmationmessage.

Action: Press <PF22> to confirm, or press anyother function key to cancel the deletion.

About to archive Audit Log from % to%; press <%> to confirmSource: Secure Audit Log

Explanation: You are about to archive the auditlog contents of the specified date range.Please confirm or cancel.

Action: If you want the archive to be done, pressthe specified confirm key to confirm;otherwise, press any other key to cancel.

About to delete ADABAS definition:<PF22> to confirmSource: Adabas Extract

Explanation: Confirmation message.

Action: Use <PF22> to confirm the delete or anyother key to cancel the delete.

About to delete definition for %Source: Field Dictionary

Explanation: This message requires confirmationof your delete request.

Action: Confirm the request by pressing <PF22>or cancel the request by pressing any otherPF key.

About to delete queue definitionSource: Batch Submission Tool

Explanation: You made a request to delete thedefinition of a queue, and this requestrequires confirmation.

Action: Press <PF22> to delete the queuedefinition, or press any other key to cancelthe deletion.

About to delete SHARED screen tableSource: Screen Definer

Explanation: You are about to delete a screentable that is shared by other Screens.

Action: To cancel the delete request, press anyfunction key except <PF22>. Use the REFSfunction to view a list of Screens referring tothe screen table. If the screen table is notrequired, reinitiate the delete request andconfirm it (note that rules cannot displayother Screen definitions that refer to thedeleted screen table until the Screens havebeen modified).

TIBCO Object Service Broker Messages Without Identifiers

Page 45: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 31

About to delete table "%"Source: Table Definer

Explanation: The definition of the indicated tablewill be deleted if you press the indicated keyto confirm the deletion.

Action: Confirm the deletion by pressing theindicated key, or press any other function keyto cancel the request.

About to delete this documentSource: Character-based Text Editor

Explanation: You pressed <PF22> or entered theprimary command DELETE.

Action: Press the confirm key <PF22>, or pressany other key to cancel the deletion.

About to delete this menuSource: Menu Definer

Explanation: <PF22> was pressed.

Action: Confirm the deletion by pressing <PF22>again, or cancel the deletion by pressing anyother key.

About to delete this object listSource: DEFINE_OBJLIST Tool

Explanation: This message warns you that theobject list is to be deleted and asks forconfirmation.

Action: Press the confirm key if you want theobject list to be deleted.

About to overwrite filter %Source: Secure Audit Log

Explanation: You are about to overwrite thedefinition of an existing filter definition.Confirm or cancel the action.

Action: Press the specified confirm key toconfirm the action or any other key to cancel.

About to overwrite rule "%" in library"%"Source: Rule Editor

Explanation: The rule already exists in thelibrary.

Action: Select the desired action: Yes tooverwrite, No to cancel.

About to re-extract ADABASdefinition: <PF4> to confirmSource: Adabas Extract

Explanation: Confirmation of your request to re-extract ADABAS definition.

Action: Use <PF4> to confirm re-extract or anyother key to cancel re-extract.

Access directive must be OFS or OLSSource: Table Definer

Explanation: The IDMS set access directive mustbe either OFS (Obtain First in Set) or OLS(Obtain Last in Set).

Action: Specify a correct set access directive.

TIBCO Object Service Broker Messages Without Identifiers

Page 46: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

32 |

Access error on % "%"Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

Access from generator will beprevented by %Source: Report Definer

Explanation: Saving the report or report tablewithin the Report Definer causes the reportto be inaccessible to the Report Generator.

Action: If you need to make further changes tothis report through the Report Generator, donot save the changes made with the ReportDefiner.

ACCESS is a required fieldSource: Table Definer

Explanation: You must specify the type of eventACCESS. Valid access types for a validationrule are W, I, R, and D. Valid access types fora trigger rule are W, I, R, D, and G.

Action: Enter W for Write access, I for Insert, Rfor Replace, D for Delete, and G for Get andforall if it is a trigger event. You can also press<PF1> for selection.

Access to table "%" blocked by anotheruser - transaction cancelledSource: Session Manager

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Access value cannot be stored forparameterSource: Table Definer

Explanation: You cannot associate a MetaStorparameter field with an access value for IMStable access.

Action: No action required.

Access value must be specifiedSource: Table Definer

Explanation: You have not specified an accessvalue for the data set type of this VSM table.

Action: Specify the access value. A list of validaccess values can be obtained by pressing<PF1>.

Access value not supported for indexsubfields.Source: Table Definer

Explanation: Invalid line command. TheMetaStor does not support access value onsubfields of an IMS index. Only access valueon the base index field is supported.

Action: Define access value on the base IMSindex field.

TIBCO Object Service Broker Messages Without Identifiers

Page 47: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 33

Accesses that were not allowed willnow be displayed normallySource: Secure Audit Log

Explanation: You pressed <PF4> to reset all thehighlighted occurrences which indicatedaccess failures.

Action: No action required.

Accesses that were not allowed willnow be highlightedSource: Secure Audit Log

Explanation: You pressed <PF4> to highlight allthose occurrences which indicated accessfailures.

Action: Press <PF4> again if you want to reset allthe highlighted occurrences.

ACROSS_BY field cannot also beSORT_BY fieldSource: Report Definer

Explanation: SORT_BY fields control sorting ofrows. SORT_ACROSS_BY fields controlsorting of columns. The same field cannot doboth.

Action: Enter the field as either a SORT_BY fieldor a SORT_ACROSS_BY field.

ACROSS_BY field exists for non-acrossreport (MAX ACROSS = 0)Source: Report Definer

Explanation: You entered a value for theSORT_ACROSS_BY field but the report doesnot repeat across.

Action: Do one of the following:

• Enter a nonzero value in the MAX ACRfield.

• Remove all SORT_ACROSS_BY fields.

Action cancelled, "%" not %Source: Character-based Text Editor

Explanation: The specified action is canceled atyour request.

Action: No action required.

Action cancelled; document not savedSource: Character-based Text Editor

Explanation: The document was not saved atyour request.

Action: No action required.

Action may cause indefinite wait in"%"; press <%> or type "CONFIRM" toconfirmSource: Table Editor

Explanation: The Single Occurrence Editor whenused from the Table Browser starts a separatetransaction stream and therefore a separateexternal gateway will be used to do theupdate. The browse transaction may haveacquired shared locks in the externalenvironment. An attempt by the secondtransaction to access the same record maycause, depending on the externalenvironment, an indefinite wait on theparent transaction lock. This is onlyrecoverable by canceling the user session andmay require external environmentoperations to release lock.

Action: If you are sure that a parent/childindefinite lock will not occur then confirmrequest otherwise exit the Table Browser anduse the Table Editor.

TIBCO Object Service Broker Messages Without Identifiers

Page 48: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

34 |

ACTION must be one of N, C, MSource: Menu Definer

Explanation: The value in the ACTION fieldmust be one of the following:

• N - EXECUTE the named rule in a newtransaction.

• C - CALL the named RULE withoutstarting a new transaction.

• M- Display the named MENU.

Action: Enter N, C, or M.

ADABAS definition extractedSource: Adabas Extract

Explanation: ADABAS definition has beenextracted into Object Service Broker.

Action: No action required.

ADABAS Response code - %Source: Adabas Extract

Explanation: During processing an unexpectedADABAS response code was received.

Action: Review the returned response code todetermine the appropriate action required tofix the problem with ADABAS.

Added control table occurrence for % to%Source: Copy Definition

Explanation: You added a control tableoccurrence for the specified object to thespecified control table. This is part of theaudit trail for the COPY tool.

Action: No action is required.

ADDED user % cannot beDISCLAIMED; removed from listSource: Security

Explanation: You added a new subject to the listby using the ADD function. After the ADD,you selected this subject for a DISCLAIMfunction. Since the user has not been addedto this SecAdmin as yet (i.e., not saved andcommitted), the DISCLAIM is unnecessary,and the addition is removed from the list.

Action: No action required.

Address of SESSMGR %Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: For more information, show this messageto a System Programmer.

All % selected instances have beenUNSELECTEDSource: Unload

Explanation: In INSTANCE SELECTION, yourequested to unselect any instance that iscurrently selected. This is confirmation thatthe request has been done.

Action: No action is required.

All break events removedSource: Debugger Utility

Explanation: You have entered the OFF primarycommand. This provides feedback.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 49: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 35

All current data will be deletedSource: Adabas Extract

Explanation: You have requested to extract alldefinitions. This is to confirm that all currentADABAS extract files will be deleted.

Action: Use <Enter> to confirm.

ALL data REPLACED in populatedtable because action is % %Source: Unload/Load

Explanation: There was data in the table, orparameter instance, and it has beencompletely replaced because the action wasIR.

Action: No action required.

All fields must have a length greaterthan zero.Source: Adabas Definer

Explanation: All fields must have a lengthgreater than zero.

Action: Enter a length greater than zero.

All level % users %Source: Security

Explanation: You either suspended or restoredall users of the given level. This messageinforms you that the operation has beencompleted.

Action: No action required.

All level % users have already been %Source: Security

Explanation: You attempted to suspend orrestore all users of the given level but allthose users had already been suspended orrestored.

Action: No action required.

All relational operators must be thesameSource: Batch Control Card

Explanation: All the relational operators withinselection criteria must be the same. Forexample, the selection:

PARM1 = 10 & PARM2 > 12

is invalid because it has two differentrelational operators: equal (=) and greaterthan (>).

Action: Change the selection string so that itcontains only one unique relational operator.

All rules in list printedSource: Print Rules

Explanation: You pressed <PF4> to print all therules of the list.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 50: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

36 |

Allocation failed "%" dataset; module"%"; R15 = %, error = %, info = %Source: Session Manager

Explanation: Allocation of the SORT WORK dataset has failed. The DDNAME of the SORTWORK data set, the module name, the returncode, and the dynamic allocation error andinfo codes are supplied for debuggingpurposes.

Action: Call your System Administrator to checkthe return code in Register 15 against theappropriate vendor's manual. Correct theproblem as required.

Allocation of # bytes of ; scope storagefailedSource: TAM

Explanation: A storage allocation via an INSERTinto the table @MAP has failed.

Action: If the scope is SESSION increase thevalue of SESSIONMEMMAX to resolve thisproblem. If this does not resolve the problemcontact TIBCO Support.

Allocation of file "%" failed. RC="%",ERRCODE="%", INFOCODE="%"Source: Builtin Routines

Explanation: Allocation of the named file failed.The data set name, the return code, and thedynamic allocation error and info codes aresupplied for debugging purposes.

Action: Call your system administrator to checkthe return code in register 15 against theappropriate vendor's manual. Correct theproblem as required.

Already defined "%" in this ruleSource: Rule Editor

Explanation: The identifier has already beendeclared as either a parameter or a localvariable for this rule. An attempt is nowbeing made to declare this identifier a secondtime.

Action: Define a different identifier.

An abbreviation is required for eachtitleSource: Menu Definer

Explanation: Each rule must correspond to anabbreviation.

Action: Enter an abbreviation or remove the rulename.

An attempt was made to accessunregistered memory for MAP table #Source: TAM

Explanation: This message is produced when arule attempts to access a piece of storage,using a MAP or MEM table, that TIBCOObject Service Broker does not regard asbeing part of the current session and thepiece of storage is not registered for access.

Action: If the rule is attempting to access thecorrect piece of storage then preregister thestorage for access by inserting a row into@MAP of type EXTERNALRO orEXTERNALRW. See @MAP in the ShareableTools manual for more details.

TIBCO Object Service Broker Messages Without Identifiers

Page 51: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 37

An entry cannot be explicitly includedmore than onceSource: Security

Explanation: You included the same entry twiceon a list. For example, the same user or groupappear twice on a default or permissions list.

Action: Remove or change the duplicate entry.

An entry is requiredSource: Session Manager

Explanation: You chose a menu item that cannotbe used without making an entry.

Action: Type an appropriate entry for the menuitem.

An entry level rule to execute haspreviously been selectedSource: Promotion

Explanation: You chose to continue a request andselected a rule to execute when another rulewas previously selected to execute forpromotion. The first rule has to be marked asentry-level, so the one being submitted nowcannot be entry-level. The previouslysubmitted one must call the current one.

Action: Do not mark the current rule as entry-level. If the previous rule does not call thecurrent one, roll back the change, fix the ruleto execute, and resubmit.

An identifier cannot begin with "%"Source: Rule Editor

Explanation: An identifier begins with an invalidcharacter.

Action: Check the Processing manual forcharacters which are valid in identifiers.

An object of type "%" cannot have aparent of type "%"Source: Copy Definition

Explanation: Certain object types can havecertain parent types, i.e., an object of typeRULE can have a parent of type LIBRARYbut not of type RULE.

Action: Enter the correct parent type.

An object of type "rule" must have a"library" attributeSource: Copy Definition

Explanation: The library attribute for a rule mustbe specified.

Action: Enter the library name for the rule.

APPEND CNTL conflict; choose action:Source: Report Definer

Explanation: An APPEND request has beenissued to copy fields with existing controlinformation into a report table that also hascontrol information.

Action: Choose one of the following actions bypressing the indicated PF key:

• COPY/CNTL - copy all indicated fieldswith CONTROL information. Appendnew control information after any existingcontrol information.

• COPY/NOCNTL - copy all indicatedfields, but do not copy any new controlinformation.

• CANCEL APPEND.

TIBCO Object Service Broker Messages Without Identifiers

Page 52: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

38 |

APPEND overlap; choose action:Source: Report Definer

Explanation: Fields to be copied will overlapexisting fields.

Action: Choose one of the following actions bypressing the indicated PF key:

• COPY/ALL - copy all fields as non-display(row 0, column 0).

• COPY/NO OVERLAP - copy all fields thatdo not overlap.

• CANCEL APPEND.

APPENDAGE field is not yet supportedSource: Table Definer

Explanation: The Appendage field is not yetsupported; the source indicator A is notallowed. You can enter S to indicate a sourcefield or a D to indicate a derived field.

Action: Remove the A from the SRC field.

Applied % rulesSource: Promotion

Explanation: This message gives the number ofrules applied to another system.

Action: No action required.

APPLYING NEW RULES ANDDELETING OBJECTSSource: Promotion

Explanation: This message appears during Phase3 to confirm that the promotions are beingapplied.

Action: No action required.

Archive of AUDITLOG( % ) by % intofile % deniedSource: Audit Log Message

Explanation: The user was denied access topurge and archive the audit log data of thespecified date.

Action: The user can check with SecurityAdministrator to get access to the facility.

Archive of AUDITLOG( % ) by % intofile %Source: Audit Log Message

Explanation: The audit log of the specified datewas unloaded to the specified file by theindicated user.

Action: No action required.

Arg% is null so the followingarguments must also be nullSource: DEFINE_OBJLIST Tool

Explanation: You did not assign a value to theindicated argument; therefore all subsequentarguments should not be assigned values.

Action: Either specify a value for the indicatedargument or remove all the values assignedto subsequent arguments.

Argument "%" for "%" cannot havesyntax "%"Source: Builtin Routines

Explanation: The named argument does notsatisfy the syntax requirements.

Action: Ensure that the value used for the namedargument has a valid syntax.

TIBCO Object Service Broker Messages Without Identifiers

Page 53: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 39

Argument "%" for "%" has length "#", ithas been truncated to fit length "#"Source: Builtin Routines

Explanation: The specified character stringargument was passed to a tool that limits thelength of the string. Since the argumentexceeded the length, the excess characterswere ignored.

Action: No action required, but you may want toshorten the argument.

Argument "%" for "%" has length "#", itwill not fit within length "#"Source: Builtin Routines

Explanation: This message applies to one of thefollowing:

• Argument TEXT of routine $PRINTLINEcannot have a length that exceeds the printwidth.

• Argument STRING of routine$PRINTFIELD cannot have a length thatexceeds the argument LENGTH of routine$PRINTFIELD.

• Argument SECTION_NAME of $TOCPUTcannot have a length that exceeds the printwidth less four.

Action: Adjust the arguments.

Argument "%" for "%" has value "#"; itmust be < "#"Source: Builtin Routines

Explanation: Argument SPACING of $TOCPUTmust be smaller than the page length.

Action: Supply a valid argument.

Argument "%" for "%" has value "#"; itmust be <= "#"Source: Builtin Routines

Explanation: This message applies to one of thefollowing:

• Argument WIDTH of $RESETPRINTcannot exceed 256.

• Argument WIDTH of $SETPRINT cannotexceed 256.

• Argument POS of $PRINTFIELD cannotexceed the page width.

Action: Supply a valid argument.

Argument "%" for "%" has value "#"; itmust be non-negativeSource: Builtin Routines

Explanation: This message applies to one of thefollowing:

• Argument P# of $RESETPRINT

• Argument P# of $SETPRINT

• Argument COUNT of $SKIPLINE

• Argument LENGTH of $PRINTFIELD

The values given to these arguments must benon-negative.

Action: Supply a valid argument.

Argument "%" for "%" has value "#"; itmust be strictly positiveSource: Builtin Routines

Explanation: This message applies to one of thefollowing:

• Argument POS of $PRINTFIELD

• Argument LENGTH of $RESETPRINT

• Argument WIDTH of $RESETPRINT

• Argument LENGTH of $SETPRINT

TIBCO Object Service Broker Messages Without Identifiers

Page 54: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

40 |

• Argument WIDTH of $SETPRINT

• Argument SPACING of $TOCPUT.

The values given to these arguments must bepositive.

Action: Supply a valid argument.

Argument "%" for "%" has value "#"; itsabsolute value is not between 1 and 2 **31 - 1 inclusiveSource: Builtin Routines

Explanation: The argument passed to a tool suchas RANDOM or RANDOMSEED does notfall within the valid range.

Action: Correct the argument value.

Argument # of % routine "%" is nullSource: Interpreter

Explanation: You used a null value for a numericargument to a tool.

Action: Provide a non-null value for theargument of the routine.

Argument % for "%" does not match PICstringSource: Builtin Routines

Explanation: The input character string specifiedin the Object Service Broker DATE tool is notcompatible with the given date format ($PICstring). As a result, the tool did not have thecorrect or enough information to return therequested date result.

Action: Refer to the Shareable Tools manual forall the valid $PIC string values.

Argument % for "%" is not a characterstringSource: Builtin Routines

Explanation: The indicated tool requires acharacter string for the indicated argument.

Action: Correct the argument.

Argument % for "%" is not a type"DATE" variableSource: Builtin Routines

Explanation: The indicated tool requires theindicated argument be a type DATE variable.

Action: Check the semantic type of the offendingargument and make sure it is a type DATEvariable.

Argument % for "%" is not a valid PICstringSource: Builtin Routines

Explanation: The indicated Object Service Brokertool detects an invalid date format ($PICstring).

Action: Consult the Shareable Tools manual for adescription of the tool and valid $PIC stringformats.

Argument % for "%" is not a valid typeSource: Builtin Routines

Explanation: The indicated tool detected that theindicated argument does not have therequired semantic type.

Action: Refer to the Shareable Tools manual forthe required semantic type of the argumentor arguments for the indicated tool.

TIBCO Object Service Broker Messages Without Identifiers

Page 55: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 41

Argument ACTION of the routine %must equal FIRST before it equalsNEXTSource: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

Argument for "GETCHAR" has aninvalid syntaxSource: Interpreter

Explanation: The argument value for STRINGfor GETCHAR must be a local variable, or afield of a table with a syntax of C, UN, V, orW.

Action: Verify the syntax of the argument thatyou pass to GETCHAR is supported.

Arithmetic overflow %Source: Interpreter

Explanation: The result of an operation exceedssome predefined maximum.

Action: Verify the expression to ensure that themaximum possible value does not exceed thepredefined maximum.

Assignment-by-name of table "%" totable "%" failed; % for field "%"Source: Interpreter

Explanation: An assignment-by-name statementcan require conversion.

Action: Read the messages that follow todetermine which exception was raised.

Assignment-by-name of table "%" totable "%" failed; source field "%" isundefinedSource: Interpreter

Explanation: A table name appears on the rightside of an assignment-by-name statement,but the fields that are used in the assignmenthave not been assigned values.

Action: Verify that all the fields involved in theassignment have values.

At %Source: Table Editor

Explanation: Scrolling has reached the maximumto one of the following points:

• TOP

• BOTTOM

• LEFT

• RIGHT

Action: No action required.

At least one of % or % must be a primarykeySource: Print Table

Explanation: When a table is added to a join, atleast one of the fields named for that additionmust be a primary key.

Action: Change the table appropriately.

AT LEFT MARGINSource: Report Definer

Explanation: You are already at the left edge ofthe screen.

Action: Scroll right.

TIBCO Object Service Broker Messages Without Identifiers

Page 56: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

42 |

At most one data set parameter (noreference table) is allowedSource: Table Definer

Explanation: A parameter without a referencetable is treated as a data set parameter. Youspecified more than one data set parameter.

Action: Reduce the number of data setparameters to one.

AT RIGHT MARGINSource: Report Definer

Explanation: The scroll right operation has beenrequested and the right margin has alreadybeen reached.

Action: No more scroll right operations can beperformed until a scroll left is performed.

At rule "%" : %=%Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

At rule "%" : %='%'Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Attempt a second change FROM %; thischange is cancelledSource: CHANGERULE tool

Explanation: You have specified the same changetwice. Only the first change has effect.

Action: No action needed. The first change willhave been carried out.

ATTEMPT TO COPY REJECTED,DISPLAYED DATA IS CURRENTLYNOT SAVEDSource: S6BTLADM-Resource Management

Explanation: You attempted to copy the schedulethat has not yet been saved to the ResourceRepository.

Action: Save the current schedule beforeattempting to copy it to a different name.

Attempt to delete ESDS record for table"%" of VSAM % "%"Source: TAM

Explanation: You requested a DELETE operationfor the indicated table but deletion is notallowed because the associated data set is ofaccess type ESDS. The variables, from left toright, are as follows:

1. The name of the table

2. Either "file" or "DDNAME"

3. The name of the file or the DDNAME

Action: You can perform a logical delete on anESDS data set by replacing the record with adummy record.

TIBCO Object Service Broker Messages Without Identifiers

Page 57: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 43

Attempt to insert duplicate key to table"%"Source: TAM

Explanation: The user is inserting a newoccurrence with a primary key value thatalready exists in another occurrence of thetable.

Action: Change the primary key value of the newinserted occurrence, or add an ACCESSFAILexception handler.

Attempt to set number of print copiesfailed, value must be between 1 and 255Source: Builtin Routines

Explanation: One of the following occurred:

• The argument PRINT_COPIES of the$BATCHOPT tool does not fall within avalid range.

• An internal error.

Action: If the error was caused by the$BATCHOPT tool, supply a valid argument.If not, contact TIBCO Support.

ATTEMPTED TO CHANGEJOURNALLING ACTIVITY WHENTHE SEGMENT WAS NOT OFFLINESource: S6BTLADM - SEGMENT/DASD

Explanation: In order to change the journalingfor a segment that segment must first betaken offline.

Action: First take the segment offline. When thesegment is offline then change the journaling.When the journaling change is complete thenbring the segment online again.

ATTEMPTED TO CHANGESEGMENT MODE WHEN THESEGMENT WAS NOT OFFLINESource: S6BTLADM - SEGMENT/DASD

Explanation: In order to change the processingmode of the segment the segment must firstbe taken offline.

Action: Take the desired segment offline. Whenthe segment is offline then request thedesired mode change. When the modechange is complete then bring the segmentonline again.

ATTEMPTED TO CHANGESEGMENT STATUS WHEN THESEGMENT IS QUIESCINGSource: S6BTLADM - SEGMENT/DASD

Explanation: The segment is in the process ofbeing taken offline.

Action: Wait for the segment to completely shutdown before attempting to invoke furtherchanges.

Attempting to assign a value withinvalid type and/or syntax to a field of atable: "%.%"Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 58: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

44 |

Attempting to assign invalid data to afield of a table: "%.%"Source: Interpreter

Explanation: The source data in an assignment toa field of a table cannot be converted to thetarget semantic type and syntaxcombination.

Action: Check the field definition, its use, and thesource data.

Attempting to assign invalid data tofield % of table %Source: Debugger Utility

Explanation: You have tried to assign (usingSET) a value to a field of a table. This hasfailed; probably the source value cannot beconverted to fit the type, syntax of the field.

Action: Verify the spelling of the table, fieldcombination to be assigned. Verify that thevalue is suitable.

Attempting to divide by zeroSource: Interpreter

Explanation: You tried to divide by zero.

Action: Avoid dividing by zero or create ahandler for the ZERODIVIDE exception.

Attempting to generate code for the "%"instructionSource: Rule Editor

Explanation: Internal translator error.

The message log will contain a more detailederror message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

Attempting to nest FORALLs on table"%"Source: Interpreter

Explanation: Although you are allowed to nestFORALL statements, each FORALL must befor a different table or a different tableinstance of a parameterized table.

Action: Redesign the application so that thenested FORALLs are not being used againstthe same table, or in the case of aparameterized table, against the same tableinstance.

Attempting to purge Auditlog from %to % archive: %Source: Secure Audit Log

Explanation: This message informs you that theaudit log contents for the specified daterange are about to be archived to thespecified file.

Action: No action required.

Attribute ";" in call to"$SETRPTATTRIBUTE" has invaliddata ";" valueSource: Report Server

Explanation: The value specified for the namedattribute type of the $SETRPTATTRIBUTEtool is not a number or an empty string.

Action: Verify that the correct value was passedfor the input argument.

TIBCO Object Service Broker Messages Without Identifiers

Page 59: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 45

Attribute "EJECT" in$SETRPTATTRIBUTE must have "Y" or"N" as the data value parameterSource: Report Server

Explanation: The attribute EJECT will onlyaccept Y or N as valid values.

Action: Change parameter 3 in$SETRPTATTRIBUTE to Y (Yes) or N (No).

Attribute "IMMEDIATE" in$SETRPTATTRIBUTE requires a "Y" asthe data value parameterSource: Report Server

Explanation: The third parameter (value) forattribute IMMEDIATE must be Y.

Action: Change the third parameter value to Y.

Audit log can only be purged on singleuser execution environmentSource: Builtin Routines

Explanation: You logged on to Object ServiceBroker through a multiple-session ExecutionEnvironment (e.g., CICS) and attempted topurge the audit log. Purging the ObjectService Broker audit log through a multiple-session Execution Environment isdisallowed.

Action: Log on to Object Service Broker througha single-session Execution Environment andtry the purge again.

Audit log can only be purged on systemusing XMSSource: Builtin Routines

Explanation: You logged on to a Object ServiceBroker system through an ExecutionEnvironment that did not use Cross MemoryServices to communicate to the Data ObjectBroker. Purging the audit log from thisExecution Environment was disallowed.

Action: Log on to the Object Service Brokersystem through Object Service Broker anExecution Environment that uses CrossMemory Services to communicate to theData Object Broker. Then try the purge again.

Audit log of current date "%" cannot bepurgedSource: Builtin Routines

Explanation: You attempted to purge today'saudit log and this was not allowed.

Action: No action required.

Audit log of date "%" is emptySource: Builtin Routines

Explanation: You attempted to purge thespecified day's audit log which was empty.

Action: No action required.

Auditlog archived for dates: %-%Source: Secure Audit Log

Explanation: This message informs you that theaudit log contents of the specified date rangehave been archived successfully.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 60: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

46 |

Autoprompting on NON-REFERENCEfieldSource: Screen Server

Explanation: A screen field hasSCREENFIELDS.AUTOPROMPT = Y butFIELDS.REFERENCE = null.

Action: Either set AUTOPROMPT = N or specifythe name of a reference table asFIELDS.REFERENCE.

Available line commands: I(Insert)D(delete) M(move) R(repeat)Source: Report Definer

Explanation: Available line commands are I, D,M, and R. A line command other than thesewas entered.

Action: Correct the line command to one of theavailable values, or remove it.

Available rights list is too large; Narrowdown your searchSource: Promotion

Explanation: The selection specification (if any)has yielded too large a list to be managed.

Action: Use the template provided to furthernarrow down your search so that a smallerlist can be generated.

TIBCO Object Service Broker Messages Without Identifiers

Page 61: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 47

Messages beginning with: B

Back out request % cancelledSource: Promotion

Explanation: You canceled a request to back out apromotion.

Action: No action required.

Backed up %Source: Promotion

Explanation: The specified number of objectswere backed up before the change wasapplied to the system.

Action: No action required.

Backed up all information for % tablesSource: Promotion

Explanation: The Promotion utility has backedup both definition and data of the specifiednumber of tables so as to allow subsequentbackout of the change.

Action: No action required.

Backed up data only for % tables ortable instancesSource: Promotion

Explanation: The Promotion utility has backedup the specified number of tables or tableinstances so as to allow subsequent backoutof the change.

Action: No action required.

BACKING UP OLD OBJECTSSource: Promotion

Explanation: The Promotion tool backs up oldobjects before deleting them so that they canbe restored if the promotion is backed out.

Action: No action required.

Backout canceledSource: Promotion

Explanation: You canceled the backout process.The status of the change request did notchange.

Action: No action required.

Backup file contains % page files -segment '%' contains % page filesSource: Offline Utilities

Explanation: The backup file contains a differentnumber of page files than the segment.

Action: Correct the ACBS parameter of theDBDEF for the segment and/or ensure thatall files for the segment have been correctlydefined and initialized.

TIBCO Object Service Broker Messages Without Identifiers

Page 62: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

48 |

Backup file contains too many pages forsegment '%'Source: Offline Utilities

Explanation: The backup file has more pagesthan the segment is capable of handling.

Action: Run a verify (-v) on the backup file todetermine the number of pages in thesegment. Reformat the segment to allow forthe number of pages in the backup file.

Backup source file is larger than targetSource: Offline Utilities

Explanation: The target of a restore operation isnot large enough to contain all of the pages inthe backup set. The utility is terminated.

Action: Redefine the target segment with enoughspace to contain the backup set and rerun theutility.

Bad value length in parameter stringSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Bad value length in selection stringSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

BASE SEGMENT (0) CANNOT BEMODIFIED ONLINESource: S6BTLADM - SEGMENT/DASD

Explanation: You have requested modificationsto the base segment (0). This segmentcontains the MetaStor and cannot bemodified while the Data Object Broker isrunning.

Action: To make changes to the base segmentrefer to the appropriate documents. Recyclethe Data Object Broker to invoke thosechanges.

Batch connections are not accepted atthis timeSource: External Gateway Logon

Explanation: The Data Object Broker is notavailable for batch at this time.

Action: Resubmit the session when theenvironment is ready.

Batch job submitted for: % time: % togenerate Static SQLSource: Static SQL for DB2 Gateway

Explanation: A batch job has been submitted togenerate the requested Static SQL.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 63: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 49

Batch request not found on queue %;key = %Source: Batch Submission Tool

Explanation: A batch request was not found onthe indicated queue as expected.

Action: Contact TIBCO Support.

Batch request savedSource: Batch Submission Tool

Explanation: Batch request information wassaved.

Action: No action required.

Begin to print definition for object "%"type "%"Source: Print Definition

Explanation: You are trying to print an object andan object, which is defined by the object youspecified, is now printing.

Action: No action required.

Binary field decimal not allowed (mustbe 0)Source: Screen Definer

Explanation: You have defined a field to have aSYN of B but also defined it to have decimalplaces. This definition is not valid.

Action: Change the SYN to a syntax whichallows for decimal places, or change the fielddefinition to have 0 decimal places.

Binary field length must be less than 12Source: Screen Definer

Explanation: You have defined a field to have aSYN of binary but given it a LEN greater than12.

Action: Enter a valid value no greater than 12 toLEN, or change the syntax.

Binding failed: Press <PF2> for moreinformationSource: Screen Definer

Explanation: Your request to bind the indicatedscreen failed.

Action: If the failure was due to locking, try againlater. If the failure was due to security,contact your Security Administrator.

Blank commands are not allowedSource: DEFINE_OBJLIST Tool

Explanation: You did not specify any letters touse to invoke the command.

Action: Specify a letter to denote the command.

Both DBID and FILE NO. must beenteredSource: Adabas Definer

Explanation: Required field DBID and/or FILEnumber are missing.

Action: Specify ADABAS Database ID and FILEnumber.

TIBCO Object Service Broker Messages Without Identifiers

Page 64: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

50 |

Both from and to tokens are %; nochange necessarySource: CHANGERULE tool

Explanation: You have entered the same thing inboth the FROM and TO columns.

Action: Enter the token you wish to havechanged in the FROM column and the tokenyou want to replace it in the TO column.

Both LAST ROW and LAST COL mustbe '0'Source: Screen Definer

Explanation: This message indicates that one ofLAST COL or LAST ROW is "0" or empty butthe other is not. "0", or empty, is the defaultvalue for these fields. If you modified one ofthese fields, you should also modify theother to have them properly specified.

Action: Set both fields to be "0" or empty, or setthem to some specified values based on yourrequirements.

Both REFERENCE and SOURCENAMEmust be either null or non-nullSource: Table Definer

Explanation: Invalid REFERENCE and/orSOURCENAME values. For MEM table type,the fields REFERENCE and SOURCENAMEare used together optionally to providechaining. They should both be specified orelse left blank.

Action: Specify valid MetaStor names for bothREFERENCE and SOURCENAME, or leaveboth fields as blanks.

Both the field name & the screen tablename must be specifiedSource: Screen Definer

Explanation: You have entered either a fieldname, or a screen table name, to the SCROLLFIELD ENTRY or DEFAULT CURSORPOSITION specification.

If you are going to use these specificationsyou must enter both a field name and ascreen table name.

Action: Enter both a field name and a screen tablename.

Bottom of WindowSource: General

Explanation: You pressed <PF8> until youreached the bottom of the displayableinformation. No more information existsbelow the screen you are viewing.

Action: No action required.

Break event established at %Source: Debugger Utility

Explanation: You have specified a break eventusing either the primary command area orthe break event control area. This providesfeedback.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 65: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 51

Break event information for "%" cannotbe restored.Source: Debugger Utility

Explanation: The Debugger uses a childtransaction to restore break eventinformation. This failed. Possible cause:Attempting to nest too many transactions

Action: Verify that your application is not nestingtransactions too deeply.

Break event information saved for "%"Source: Debugger Utility

Explanation: You have used <PF4> to save thecurrent Break event information. Thisprovides feedback.

Action: No action required.

Break event removed at %Source: Debugger Utility

Explanation: You have used the OFF primarycommand (or <PF22>) to remove a specificbreak event. This provides feedback.

Action: No action required.

Break number # is missing in the reportfields of controlling report table "%"Source: Report Server

Explanation: The Report Server detected aninternal error regarding breaks withoutcontrolling break tables.

Action: Contact TIBCO Support.

Browse & Search may NOT be specifiedwhen Action="C"Source: Security

Explanation: In the User Profile, you specifiedthe startup rule to run. Since you specified C(CALL) as the method for initiating the rule,you cannot specify the Browse and SearchPath. These parameters are inherited fromthe parent transaction Session Manager (ifthere is a session menu), or from the logontransaction (if there is no session menu).

Action: If the Browse and Search attributes mustbe different from those used by the SessionManager (i.e., Y and S respectively), specify E(EXECUTE) or T (TRANSFERCALL) in theACTION field. If you specify E, the rule is achild transaction. If you specify T, the SessionManager TRANSFERCALLs to the startuprule.

NOTE: if you specify T, the session endsafter the startup rule has run because theSession Manager has ended, transferringcontrol to the rule. This kind of functionalityis better achieved by NOT using a SessionMenu, but simply specifying the rule to runat logon, the Browse mode, and the SearchPath.

Browse mode must be "Y" or "N"Source: Batch Submission Tool

Explanation: The browse mode flag can be eitherY or N. N means that the mode is update.

Action: Specify a Y or N value.

TIBCO Object Service Broker Messages Without Identifiers

Page 66: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

52 |

BROWSE must be Y or NSource: DEFINE_OBJLIST Tool

Explanation: You did not specify a value for theBROWSE field.

Action: Specify a value (Y or N) for the BROWSEfield.

BROWSE must be Y or NSource: Menu Definer

Explanation: When ACTION is N, the BROWSEfield requires a value to determine the modein which the rule executes. The choices are:

• Y - Execute in browse mode.

• N - Execute in update mode.

Action: Enter Y or N in the BROWSE field.

Buffer conversion error for subview"%"Source: TAM

Explanation: The attributes defined for thesource field cannot be converted to theattributes defined for the subview field.

Action: Match the definition of the attributes ofthe subview field with the attributes definedfor the source field.

Buffer position argument beyond endof buffer - position=#,buflen=#Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Buffer position argument is less than 1 -position=#Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Buffer provided to Catalog SearchInterface was too smallSource: Builtin Routines

Explanation: The buffer is provided by the$LISTDSN built-in routine to the CatalogSearch Interface (CSI). It is large enough for120 Generation Data Sets (GDS) in a givenGeneration Data Group (GDG). A GDG withall of its associated GDS is seen by CSI as onerecord.

Action: Change the filter key to reduce thenumber of GDSs to no more than 120.

BUFFER RETRIEVAL ERRORDETECTEDSource: S6BTLADM - PAGE DISPLAY

Explanation: An error occurred retrieving therequested buffer from the Data Object Broker.

Action: If this error persists contact TIBCOsupport.

TIBCO Object Service Broker Messages Without Identifiers

Page 67: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 53

BUFFER STATISTICS RETRIEVALERRORSource: S6BTLADM - BUFFER POOL

Explanation: When attempting to retrieve thedata to build the buffer statistics screen anerror was detected.

Action: Review the job logs for possibleadditional messages to identify the cause ofthe problem. Retry the request. If theproblem persists contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 68: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

54 |

Messages beginning with: C

CA-Datacom Name has changed: otherattributes refreshedSource: CA Datacom Table Definer

Explanation: You changed the name of the CA-Datacom table on which you want to definethe Object Service Broker DAT TableDefinition. The attributes of the CA-Datacomtable now referred to have been filled in,replacing what was previously there.

Action: No action is required.

Calculate offset from field %, offset %Source: Table Definer

Explanation: This message provides detailedinformation on the start field and offset tobegin offset calculation.

Action: Review the start field and offset values.Confirm offset calculation if values arecorrect. Otherwise do not confirm.

Call to "%" must be preceded by a call to$RESETPRINT OR $SETPRINTSource: Builtin Routines

Explanation: In a transaction, neither$RESETPRINT nor $SETPRINT was called,but one of the following tools was invoked:

• $BLANKPAGE

• $NEWPAGE

• $PRINTFIELD

• $PRINTLINE

• $PUTLINE

• $SETP#POS

• $SETTITLE

• $SKIPLINE

• TOCPRINT

• TOCPUT.

Action: Issue the appropriate call to$RESETPRINT or $SETPRINT beforeinvoking the specified tool.

Can only COPY/APPEND valid<TABLE>,<TABLE>.<FLD>, or<TABLE>.*Source: Report Definer

Explanation: A COPY or APPEND commandwas issued with an invalid table or fieldspecification.

Action: Correct the table or field name.

Can only specify parameters on a tableSource: Object Set Definer

Explanation: You must place your cursor on thetable for which you wish to specifyparameters before pressing <PF6>.

Action: Place your cursor on the table for whichyou wish to specify parameters, then press<PF6>.

TIBCO Object Service Broker Messages Without Identifiers

Page 69: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 55

CANCEL USER REQUEST HAS BEENISSUEDSource: S6BTLADM - USER ACTIVITY

Explanation: Notification that the cancel userrequest has been issued.

Action: No action required.

CANCEL USER REQUEST NOTCONFIRMED, REQUEST IGNOREDSource: S6BTLADM - USER ACTIVITY

Explanation: The previous cancel user functionyou requested was not confirmed; therequest has been abandoned.

Action: No action required.

Cancelled %Source: Print Rules

Explanation: You pressed <PF12> to cancel out ofthe parameter prompt.

Action: No action required.

CANCELLED change to EXTENSIONinformationSource: General Table Definer

Explanation: You were in the screen used tospecify extension information for theMetaStor table you are defining. Yourequested to cancel any changes you hadmade while in this screen.

Action: To determine what extensioninformation will be saved should you savethis table definition, request to view theEXTENSION screen again.

CANCELLED changes to COREinformationSource: General Table Definer

Explanation: You were specifying coreinformation for the MetaStor table you aredefining. You requested to cancel the changesyou had made in the screen.

Action: To determine what core information willbe saved you should save this tabledefinition and request to view the coreinformation again.

CANCELLED changes to definition ofIDM table "%"Source: Table Definer

Explanation: The table definition modificationshave been canceled.

Action: No action required.

CANCELLED changes to definition oflibrary "%"Source: Define Library

Explanation: You canceled your changes to thelibrary definition.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 70: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

56 |

CANCELLED changes to EXTENSIONinformationSource: CA Datacom Table Definer

Explanation: You requested to cancel anychanges you made in the EXTENSIONScontext of this DAT Table Definition.

Action: To determine what EXTENSIONSinformation will be saved should you savethis Table Definition, go back to theEXTENSIONS context to view what will besaved.

CANCELLED changes to MenuDefinition "%"Source: Menu Definer

Explanation: You requested to cancel anychanges you had made to the MenuDefinition you were viewing/updating.

Action: No action required.

CANCELLED request to UNLOADSource: Unload

Explanation: You have canceled your request toUNLOAD object definitions and data.

Action: No action is required.

Cannot %; promotion rights held by % -requested by %Source: Table Definer

Explanation: The indicated action is not allowedbecause the promotion rights of the currenttable definition are held in the indicatedlibrary by the indicated user.

Action: Contact the indicated user if you need todo the action.

Cannot % % "%"; rights held by "%",requestor "%"Source: Report Definer

Explanation: The promotion rights are notavailable to allow you to do the requestedoperation.

Action: If you need to do the requestedoperation, contact the person with thepromotion rights.

Cannot % an occurrence in the BrowserSource: Table Editor

Explanation: You entered either D (delete) or R(replicate) as a line command in the TableBrowser, and these commands are notallowed.

Action: If you want to delete or replicate anoccurrence, use the line command S for theSingle Occurrence Editor (SOE), or use theTable Editor. In the SOE, use the DELETEcommand or <PF22> to delete theoccurrence, or modify the primary key andpress <PF3> to replicate the occurrence.

Cannot % rights; rights held by %,requested by %Source: Promotion

Explanation: Cannot OBTAIN, RELEASE, orTRANSFER rights on an object because therights are held by % (a library, object, user, orSYSTEM, depending on what object is beingheld), and requested by % (the user whooriginally requested the rights).

Action: Have the requestor of the rights releasethem.

TIBCO Object Service Broker Messages Without Identifiers

Page 71: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 57

Cannot % rights; rule % does not existin library %Source: Promotion

Explanation: If you are transferring rights on arule from one library to another, the rulemust exist in the destination library.

Action: Copy the rule to the destination libraryand then transfer the rights.

Cannot % rights on object %; rights arenot heldSource: Promotion

Explanation: You attempted to RELEASE rightson an object when the rights are not held.

Action: No action required.

Cannot % rights to "%"; not a validborrowerSource: Promotion

Explanation: You attempted to transfer rights toa userid that either does not exist, or existsbut is not a borrower.

Action: Do one of the following:

• Choose another userid

• Modify the userid to be a borrower

• Create the userid to which you want totransfer rights, and then transfer the rights.

Cannot % rights to library "%"; librarydoes not existSource: Promotion

Explanation: You attempted to transfer rights toa non-existent library.

Action: Do one of the following:

• Choose another library

• Define the library to which you want totransfer rights, and then transfer the rights.

Cannot access VSAM table "%" withreference table "%"Source: TAM

Explanation: The VSAM table is an IDgen tablewhich indicates that it is a child table. Theparent VSAM table is indicated byPARMS.REFERENCE but either this was notspecified, or else the parent table cannot beaccessed.

Action: Either set IDgen=N if this is not a childtable, or set the first table parameter'sPARMS.REFERENCE to the table name ofthe parent.

Cannot add - a report field is alreadydefined at this row/colSource: Report Definer

Explanation: An attempt was made to add a newfield at a row or column that is alreadyoccupied by a report field.

Action: Before requesting the ADD fieldoperation again, reposition the cursor to arow and column that is not occupied by areport field.

Cannot ADD a field; maximum numberof fields are definedSource: Screen Definer

Explanation: In the Screen Table Painter, youtried to add a field. However, the maximumnumber of fields already exist in the screentable definition.

Action: You can delete an existing field and addthe new one.

TIBCO Object Service Broker Messages Without Identifiers

Page 72: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

58 |

Cannot add any more conditionsSource: Rule Editor

Explanation: You have reached the maximumnumber of conditions allowed in a rule.

Action: Try to separate the single rule into two ormore rules.

Cannot ADD FIELD at column 0; cursorrepositioned to column 1Source: Screen Definer

Explanation: You have pressed <PF19> to loadand requested a line-by-line load of a table oftype SCR. A table of this type is loaded asdefined, not line-by-line.

Action: No action required.

Cannot add field at row % and col %,max of % fields reachedSource: Screen and Report Painters

Explanation: Cannot add the field as themaximum number of fields allowed has beenreached.

Action: You can delete an existing field and addthe new one.

Cannot ADD user %; user has higherclearance than SecAdmin %Source: Security

Explanation: A level-7 security administratortried to add an existing user as a subject ofanother security administrator by updatingthat security administrator's profile. The newsubject however, has a higher clearance thanthe security administrator whose profile isbeing updated.

Action: If the new subject must be administeredby the indicated SecAdmin, do one of thefollowing:

• Reduce the clearance of the new subject tobe the same as or lower than the securityadministrator's

• Increase the clearance of the SecAdminwhose profile is being updated

If the new subject must simply bereassigned, go to the SecAdmin profile of theuser who currently administers that subjectand disclaim the subject to any otherSecAdmin who has a high enough clearance.You can even assign the subject to yourself,either from your SecAdmin profile, or fromthe profile of the subject's current SecAdmin.

Cannot apply function "%" tononnumeric field "%"Source: Report Generator

Explanation: You cannot apply the specifiedfunction to the specified nonnumeric field.

Action: Change the function or field, or removethe pair by blanking out the field name.

TIBCO Object Service Broker Messages Without Identifiers

Page 73: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 59

Cannot apply function to across field"%"Source: Report Generator

Explanation: You cannot apply a function to theindicated field because it is an across-byfield.

Action: Remove the indicated field from thesummary/break section.

Cannot apply function to break field"%" in this breakSource: Report Generator

Explanation: You cannot apply a function to theindicated break field because its value doesnot change within the break.

Action: Remove the indicated field from thatbreak section.

Cannot apply function to sort field "%"in SUMMARY PRINTSource: Report Generator

Explanation: You cannot apply a function to theindicated field in the SUMMARY PRINTsection because it is a SORT BY field and aSORT BY field is also used as a SUMMARYBY field in a summary report.

Action: Remove the indicated field from theSUMMARY PRINT section.

Cannot back out; no backup for table"%"Source: Promotion

Explanation: You cannot back out the changebecause the specified table was not backedup when the change was previously appliedto the system.

Action: You have to prepare another changerequest to undo the change.

Cannot back out; no occurrences werebacked up for table "%"Source: Promotion

Explanation: The occurrences cannot be restoredfor the specified table.

Action: Contact TIBCO Support.

Cannot back out; no PRM table for "%"Source: Promotion

Explanation: A back out request requires a PRMtable for a parameterized table to be restored.

Action: Create a PRM table for the specifiedtable.

Cannot backout change on remotelocationSource: Promotion

Explanation: You can only backout a change thathas been applied to your local node.

Action: Log on to the target node and backout thechange.

TIBCO Object Service Broker Messages Without Identifiers

Page 74: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

60 |

Cannot backup table "%", you mustturn off backup optionSource: Promotion

Explanation: The Promotion Utility is not able totake a backup of the specified table.

Action: Change the value of the backupparameter for this table to N.

Cannot be used as a Group name; "%" isa useridSource: Security

Explanation: You requested the creation of agroup that has the same name as an existinguser.

Action: Select a different group name becauseusers and groups cannot share a name.

Cannot be used as a userid; "%" is aGROUPSource: Security

Explanation: You are trying to create a newuserid which has the same name as anexisting group; users and groups cannotshare names.

Action: Select a different userid for the new user.

Cannot bind data for % tablesSource: Table Editor

Explanation: You attempted to bind the data of anon-TDS table.

Action: Do not attempt to bind the data in this orother non-TDS tables.

Cannot bind definition for a table oftype %Source: Table Editor

Explanation: You attempted to bind thedefinition of a table type which cannot bebound.

Action: Do no attempt to bind tables of this type.

Cannot change name; "%" already existsSource: Table Definer

Explanation: The indicated table name alreadyexists in the MetaStor. You cannot change thetable name to an existing table name.

Action: No action required.

Cannot change name; "%" already existsSource: Table Definer

Explanation: You typed over the existing name inthe TABLE NAME field, but the new name isalready used for another table definition.

Action: Change the name to something else.

Cannot change name; % already existsSource: Table Definer

Explanation: You changed the current tablename to the name of another existing table.

Action: No action required.

Cannot change name; %Source: Table Definer

Explanation: You cannot change the table namefor the indicated reason.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 75: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 61

Cannot change name to %; that filter isowned by %Source: Secure Audit Log

Explanation: You attempted to save a new filterdefinition but the name that you specifiedwas already used by another user.

Action: Change the name of the filter and tryagain.

Cannot change name to existing table"%"; use "%" or NEW nameSource: General Table Definer

Explanation: You have requested to define atable using the generic Table Definer. Youthen changed the name to the name ofanother existing table.

Action: You must change the name back to theone you started with, or use a name whichdoes not exist as a table.

Cannot change NLS bit for systemtablesSource: Table Editor

Explanation: You cannot change the setting ofthe NLS bit for system defined tables.

Action: No action is required.

Cannot change Screen name to "%";Screen already existsSource: Screen Definer

Explanation: In the Screen Table Painter, youtried to change the screen name to the nameof an existing screen.

Action: If you are trying to copy a currentdefinition, select another name. If you wantto update the definition for the indicatedscreen, leave the current Screen Definersession and reinitiate the Screen Definer withthe appropriate screen name.

Cannot change table type: %Source: Table Definer

Explanation: Failed to change table type for thereason specified in the message. A typicalscenario would be incompatible syntaxbetween different table types.

Action: Fix the error and try the operation again.

Cannot compare table % with table %since % does not existSource: Definition Differences

Explanation: You are trying to compare twotables and one of the tables does not exist.Therefore the comparison fails.

Action: No action required.

Cannot copy/append a table of type "%"Source: Screen Definer

Explanation: You pressed <PF19> to load andgave a table name on the prompting screen.This table is not one of the following validtypes: PRM, SCR, SUB, TEM, TDS.

Action: Enter the name of a valid type of table, orcancel the load command.

TIBCO Object Service Broker Messages Without Identifiers

Page 76: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

62 |

Cannot COPY requested screen table--wider than % columnsSource: Screen Definer

Explanation: In the Screen Table Painter, youwanted to COPY in a screen table that iswider than the maximum width possible forthe current physical screen.

Action: No action required.

Cannot copy tables of type %Source: Table Definer

Explanation: You cannot copy the indicated typeof table.

Action: If you are defining a table for an externaldatabase, you can copy only tables of thesame type (e.g., IMS, IDM, or DB2). If you aredefining any other table, you can copy anyother table type except for an externaldatabase table type.

Cannot create a minimal defn, Recordsand Sets have already been selectedSource: Table Definer

Explanation: Creation of an IDMS minimaldefinition failed since records and sets havealready been included in the table definition.

Action: Delete the current IDMS table definition.Define a minimal IDMS table definition bypressing <PF9>

Cannot create default security for %Source: Report Definer

Explanation: A VALIDATE FAIL signal is raisedwhen accessing the identified table.

Action: Contact your System Administrator toinvestigate what is wrong with the identifiedtable or replace it with a valid table.

Cannot create PRM table; a parametername of % is "NUMBER"Source: Table Definer

Explanation: You cannot define a PRM table forthe indicated table because one of itsparameters is called NUMBER.

Action: Change the parameter name of thesource table from NUMBER to some othername.

Cannot create PRM table if parametername is "NUMBER"Source: Table Definer

Explanation: This message is a warning that noPRM table can be created on the current tablebecause one of its parameters is namedNUMBER.

Action: Press the indicated key to confirm thatyou want to save the table anyway, or pressany other function key to cancel the SAVE.

Cannot create secondary key in TableDefinerSource: Table Definer

Explanation: You entered an S in the KEY fieldfor a field definition, but the Table Definerdoes not create secondary indexes.

Action: Remove the S from the KEY field. If yourequire a secondary index, run the SIXBUILDtool. You can find information aboutSIXBUILD in the Shareable Tools manual.

TIBCO Object Service Broker Messages Without Identifiers

Page 77: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 63

Cannot CREATE userid="%" sincelibrary of that name existsSource: Security

Explanation: A Security Administrator or aSystem Administrator made a request tocreate a new user, but a library already existswith the same name as the new userid. Sinceevery user has a home library named thesame as the userid, a new user cannot becreated with this ID.

Action: Select a new userid for the new user, orhave the existing library removed orrenamed by an authorized person.

Cannot default parameter "%" of "%" -no sourceSource: TAM

Explanation: A subview parameter that does nothave a matching parameter name in thesource table was specified.

Action: Do one of the following:

• Provide attributes for the subviewparameter, using the Table Definer.

• Change the parameter name to an existingsource parameter name.

Cannot define % for % tableSource: Table Definer

Explanation: The object specified in the messageis not supported by the table type. Forexample, you cannot define Data parametersfor MAP table type.

Action: Remove the invalid definition.

Cannot define a term except in adefinition listSource: Character-based Text Editor

Explanation: The tag ".term" or ".dt" appearsoutside of a definition list. (Colons can beused instead of periods.)

Action: Do one of the following:

• Remove the tag.

• Put ".dl" and ".edl" tags before and after thedefinition term tag.

• Put "list" and "listend" tags (preceded byperiods) before and after the definitionterm tag.

Cannot define addition key(s) for tablewith dataSource: Table Definer

Explanation: You attempted to add keys to atable containing data. This operation is notallowed.

Action: Modify the table definition to preservethe existing key definition.

Cannot define an orphan screenSource: Global Cross Ref. Search

Explanation: The screen you intend to define hasbeen deleted from the MetaStor. Cannotdefine this screen within the search utility.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 78: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

64 |

Cannot define external attributes forLocation parameterSource: Table Definer

Explanation: Operation invalid. Externalattributes are not supported for locationparameter.

Action: No action required.

Cannot define more than ONE title atline=%, position %Source: Menu Definer

Explanation: You are defining a menu with titlelines and you have specified the sameposition for different lines. Each title linemust be in a different row and columnposition.

Action: Change the position information for thetitle line(s) so that they will occupy differentpositions.

Cannot define report table "%"; tablealready exists with nameSource: Report Definer

Explanation: You tried to define a report table ora control break table with a name that isalready assigned to another table.

Action: Choose a new name for the specifiedreport table or control break table.

Cannot delete % "%", rights held by % -requested by %Source: Delete Definition

Explanation: You have requested to delete anobject; however, the Borrow Rights are heldby another user.

Action: You may not delete the object until youhave obtained Borrow Rights for the object orno rights are held for the object.

Cannot delete % "%", unable to verifypromotion rightsSource: Delete Definition

Explanation: You have requested to delete anobject; however, promotion rights for theobject cannot be verified at this time.

Action: You must either obtain promotion rightsfor the object and try the delete again, or ifyou have these rights, wait and try the deleteagain.

Cannot delete % (%): %Source: Delete Definition

Explanation: You are trying to delete an objectbut the operation fails.

Action: See attached message to find out thereason.

TIBCO Object Service Broker Messages Without Identifiers

Page 79: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 65

Cannot delete control field here;changed to non-displaySource: Report Definer

Explanation: A DELETE operation has beenrequested for a report field that is also acontrol field (e.g., the report is sorted or has acontrol break on this field). The field is notdeleted, but is changed to a non-displayfield, thus preserving the control attributes ofthe field.

Action: No action required.

Cannot delete definition & delete dataof table %Source: Promotion

Explanation: You do not have to explicitly deletedata when you are deleting the definition ofa table. Deleting a table definition wouldautomatically delete its data.

Action: Remove the D command(s) beside thedata of the named table.

Cannot delete definition & promotedata of table %Source: Promotion

Explanation: You cannot delete table definitionand promote table data in the same changerequest.

Action: If you really wish to delete the definition,you will also have to delete the data.

Cannot DELETE globalfield "%", rightsheld by "%", requestor "%"Source: Field Dictionary

Explanation: You cannot delete a global fieldwhile someone else holds the promotionrights.

Action: Contact the person holding the rightsand ask them to release them.

Cannot DELETE home library of userSource: Define Library

Explanation: A request was made to delete auser's home library. Since the user exists, thiscannot be done. Note that the home libraryhas the same name as the userid.

Action: If you want to delete the home library ofa user, you must first delete the userid fromObject Service Broker (i.e., DELETE USER).You can, however, delete the rules in thelibrary.

Cannot DELETE Menu: securityauthorization failedSource: Menu Definer

Explanation: You have requested to delete themenu definition; however, you do not havethe proper security authorization to do so.

Action: You must obtain the proper securitypermissions in order to delete the menu.

Cannot DELETE Menu due toLOCKINGSource: Menu Definer

Explanation: You have requested to delete amenu definition. However, due to locking,the DELETE request cannot be satisfied.

Action: Wait and retry, or cancel.

TIBCO Object Service Broker Messages Without Identifiers

Page 80: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

66 |

Cannot delete non-system % %Source: Promotion

Explanation: The rule, screen, report or tablespecified was selected for deletion, but is nota system object (i.e., it was not promotedpreviously).

Action: Do not select that object for deletion.

Cannot DELETE now; rights cannot bedeterminedSource: Screen Definer

Explanation: You attempted to DELETE either ascreen table definition or a Screen definition,but the rights could not be determined at thetime of the request.

Action: Wait and try to delete the object again.

Cannot delete report "%" (original namehas been changed)Source: Report Generator

Explanation: You can delete only the report withthe name that you entered when you startedthis Report Generator session.

Action: If you want to delete the report, changethe report name back to the one that youentered the Generator with and press <PF22>to delete.

Cannot delete rule % (original namewas changed)Source: Rule Editor

Explanation: You have rule A in your library. Youstarted editing rule B, renamed it to rule A,and then attempted to delete the rule nowrenamed to A. This is not allowed as you didnot start your editing session with rule A.

This is a promotion rights error message. Therule you are attempting to delete holdspromotion rights, which places restrictionson it.

Action: Do not attempt to delete a rule that haspromotion rights if you did not begin yourediting session with it.

Cannot DELETE screen; rights are heldby "%"Source: Screen Definer

Explanation: You have requested to delete ascreen definition; however, due to locking,the delete request cannot be satisfied.

Action: Wait and retry, or cancel.

Cannot DELETE this SecAdmin untilall users are DISCLAIMEDSource: Security

Explanation: A System Administrator isattempting to delete a SecurityAdministrator profile, but the SecurityAdministrator still has subjects and cannotbe deleted.

Action: The System Administrator can do thefollowing to delete a Security Administratorprofile:

1. Disclaim each user on the list

2. Save (to commit disclaims)

3. Request the deletion of the SecurityAdministrator profile.

Note that the userid profile for this SecurityAdministrator remains intact.

TIBCO Object Service Broker Messages Without Identifiers

Page 81: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 67

Cannot DELETE userid until DELETESecAdmin=useridSource: Security

Explanation: Either a Security Administrator or aSystem Administrator attempted to DELETEUSER in the User Profile screen, but the userbeing deleted is a Security Administrator.

Action: A System Administrator must first deletethe SecAdmin profile of the user, and thenthe user profile of the user can be deleted.

Cannot determine file name for % table"%": DSNAME or DDNAME must bespecified in table "%"Source: TAM

Explanation: The DSNAME and DDNAMEfields are both null in IMPORTFILES orEXPORTFILES, or no IMPORTFILES orEXPORTFILES occurrence exists for thespecified table.

Action: Add the occurrences with keys equal tothe given file name in tables IMPORTFILESor EXPORTFILES. Ensure that DSNAMEcontains an existing data set name or thatDDNAME refers to a previously allocateddata set.

Cannot determine if "%" has parametersSource: Object Set Definer

Explanation: For reasons such as security,locking, etc., it could not be determinedwhether or not the indicated table hasparameters. Thus, you are not permitted tospecify parameters for this table.

Action: Define the table to determine what is theproblem.

Cannot DISPLAY after Paint SAVE; exit& reenter Definer firstSource: Report Definer

Explanation: The DISPLAY report commandcurrently does not allow you to display areport after you have saved changes throughthe Report Painter.

Action: Exit the Report Definer (SAVE orCANCEL) and reenter the Report Definerbefore requesting a DISPLAY.

Cannot DISPLAY after Paint SAVE; exit& reenter Definer firstSource: Screen Definer

Explanation: The DISPLAY command currentlydoes not allow you to display a screen afteryou have saved changes through the ScreenPainter.

Action: Exit the Screen Definer (Save or Cancel)and reenter the Screen Definer beforerequesting a DISPLAY.

Cannot edit % line for % table with dataSource: Table Definer

Explanation: Invalid edit operation. Thespecified line command you have issued isinvalid for a table containing data.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 82: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

68 |

Cannot EDIT - No extracted data existsSource: Adabas Extract

Explanation: Unable to edit description.ADABAS definition for DBID and File No isnot defined to Object Service Broker.

Action: Invoke utility @ADAEXTRACT toextract ADABAS definition into ObjectService Broker prior to editing thedescription.

Cannot EDIT an occurrence in table "%"Source: Table Editor

Explanation: The occurrences that you areattempting to edit are contained in a tabletype that cannot be updated, e.g. PRM, TEM.

Action: Do one of the following:

• Use the Table Browser to view the table.

• Use rules to update the table, instead of theTable Editor.

Cannot edit documentation on object,rights are not heldSource: Promotion

Explanation: You cannot update thedocumentation of the object becausesomeone else currently owns the rights to it.

Action: No action required.

Cannot edit parameter line for tablewith dataSource: Table Definer

Explanation: You cannot use line commands inthe parameter specification area when thetable contains data.

Action: Remove all line commands from theparameter section.

Cannot edit table of type %Source: Table Definer

Explanation: You pressed <PF21> in the TableDefiner and tried to edit a table. You can onlyedit the following types of tables:

• DB2

• IMS

• SUB

• TDS

• VSM.

Action: No action required.

Cannot ENABLE for GROUP; object setincludes object CONTROLSource: Security

Explanation: You included a group name on anenable list for an object set that includescontrol access for some object. Since groupscannot control objects, the object set cannotbe enabled for groups.

Action: Do one of the following:

• Remove the group entry from the object set

• Use EXPAND to list and select useridsfrom the group before removing the groupentry.

Cannot expand object - no PRM tablefor table %Source: Promotion

Explanation: Cannot see if data rights areavailable. There is no PRM table for thisparameterized table.

Action: Create a PRM table for this table usingthe Table Definer and proceed.

TIBCO Object Service Broker Messages Without Identifiers

Page 83: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 69

Cannot expand object - rightsobtainable as isSource: Promotion

Explanation: You have entered object commandX against this object. There are no availabledata rights for this table.

Action: Can only obtain rights as indicated byEXT field.

Cannot extract occurrences for tablewith Definition RightsSource: Promotion

Explanation: You have Definition Rights for atable, and you entered O in the EXTRACTfield.

Action: If you want to promote the occurrencesof the table, enter A in the EXTRACT field. Ifyou expect to promote the occurrencesfrequently, make the table promotable.

Cannot FETCH; % must be emptySource: Security

Explanation: The specified object type(s) cannotbe fetched because the indicated lists mustfirst be emptied.

Action: Empty the indicated lists first, then enterthe FETCH command again.

Cannot find "%"Source: Character-based Text Editor

Explanation: The string was not located by theFIND command.

Action: Check the accuracy of the string. If it iscorrect, no further action is required.

Cannot find "%"Source: General

Explanation: The specified string or value cannotbe found.

Action: No action required.

Cannot find occurrence # of screen table"%"Source: Screen Server

Explanation: The indicated occurrence of theindicated screen table cannot be found. Thisis an internal Object Service Broker logicerror.

Action: Do the following:

1. Print the log.

2. Contact TIBCO Support with a copy of thelog and a description of what you weredoing when you received this message.

Cannot find row # of occurrence # ofscreen table "%"Source: Screen Server

Explanation: The indicated row of the indicatedoccurrence of the indicated screen tablecannot be found. This is an internal ObjectService Broker logic error.

Action:

1. Print the log.

2. Contact TIBCO Support with a copy of thelog and a description of what you weredoing when you received this message.

TIBCO Object Service Broker Messages Without Identifiers

Page 84: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

70 |

Cannot find STARTUP RULE "%" asper Search & Logon LibrarySource: Security

Explanation: In the User Profile, you specified aStartup Rule, a Search Path (default is S) anda Logon Library (default is your HomeLibrary = your USERID). The Startup Rulecannot be found according to thisspecification.

Action: If Search Path is "L", the rule must be inthe Logon Library to be executed the nexttime you logon. If Search Path is "I", the rulemust be in either the Installation or theLogon Library to be found at logon time. IfSearch Path is "S", the rule must be in eitherthe System, the Installation, or the LogonLibrary to be found and executed at yournext logon.

Cannot find STARTUP RULE "%" asper Search & Logon LibrarySource: Security

Explanation: In the User Profile, you specified aStartup Rule, a Search Path (default is S) anda Logon Library (default is your HomeLibrary = your USERID). The Startup Rulecannot be found according to thisspecification.

Action: If Search Path is "L", the rule must be inthe Logon Library to be executed the nexttime you logon. If Search Path is "I", the rulemust be in either the Installation or theLogon Library to be found at logon time. IfSearch Path is "S", the rule must be in eitherthe System, the Installation, or the LogonLibrary to be found and executed at yournext logon.

Cannot find TDS appendage table "%"Source: Table Definer

Explanation: The specified appendage table doesnot exist.

Action: Do not attempt to use an appendagetable as this type of table is not yetsupported.

Cannot generate rule; report "%" doesnot existSource: Report Generator

Explanation: You cannot generate a rule toproduce the report without saving the reportdefinition.

Action: Enter Y to SAVE REPORT and pressENTER again, or choose other options toexecute the report.

Cannot get virtual storage for DCBSource: Builtin Routines

Explanation: The program is unable to obtainstorage for a Data set Control Block. This isprobably caused by there being too manyusers on the system or by the region sizebeing too small.

Action: Call your system administrator forassistance.

Cannot have a % of %Source: Screen Definer

Explanation: The field indicated by the messagecannot have the value that is indicated.

Action: Change the value of the indicated field.

TIBCO Object Service Broker Messages Without Identifiers

Page 85: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 71

Cannot have a zero length field; imagerestoredSource: Screen Definer

Explanation: A field of length zero is not allowedby the Painter.

Action: Change the length of the field so that it isat least one character long.

Cannot imbed % because it is not a texttableSource: Character-based Text Editor

Explanation: The .imbed tag was used with atable that does not have the fields requiredfor text.

Action: Embed a text table instead.

Cannot include a consolidated changeSource: Promotion

Explanation: The change you have selected is aconsolidated change and you cannot includea consolidated change within a consolidatedchange.

Action: Include each associated changeindividually.

Cannot include change that containsobject with disposition %Source: Promotion

Explanation: You cannot include a changerequest which has a rule to execute.

Action: Remove the I command beside thechange request which has a rule to execute.

Cannot INSERT any more lines intoImage Area (maximum is %)Source: Screen Definer

Explanation: In the Screen Table Painter, yourequested to insert a line into the Image Area;however, the maximum number of linesalready exists in the Image Area.

Action: Do one of the following:

• Delete an existing line from the ImageArea and insert a new line.

• Remove the contents from an existing lineand re-use it.

Cannot insert occurrence for %; Primarykey = %Source: Unload/Load

Explanation: An error occurred when LOADtried to insert an occurrence into a table.

Action: Check if the occurrence already exists inthe target system. If you want to load a newoccurrence, delete the old one.

Cannot invoke SOE for newoccurrences prior to commit changesSource: Table Editor

Explanation: You cannot edit a new occurrenceby using the Single Occurrence Editor in theTable Editor before committing the newoccurrence to the database.

Action: Commit the new occurrences by using aSELECT, ORDERED, or SAVE command,then invoke the Single Occurrence Editor forthat occurrence again.

TIBCO Object Service Broker Messages Without Identifiers

Page 86: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

72 |

Cannot issue both COMMAND andGO TO date specificationSource: Session Manager

Explanation: You have specified a Command aswell as a GO TO date in the AppointmentBook. You can do only one of these at a time.

Action: Remove either the command or the GOTO specification and press <Enter>.

Cannot load field % of table %: syntaxnot allowed. Press <Enter>Source: Report Definer

Explanation: Fields of syntax Unicode and rawdata cannot be used in a report.

Action: None.

Cannot load field % of table %: syntaxnot allowedSource: Screen Definer

Explanation: Fields of syntax Unicode or rawdata cannot be used in a screen.

Action: Select another field.

Cannot load file in format > %Source: Unload/Load

Explanation: The LOAD utility can only handlefiles up to the specified format (version) butthe file that you are loading is in a newerformat.

Action: If possible, unload the objects using thespecified format (version).

Cannot LOAD this table; % too manyfields (max is %)Source: Screen Definer

Explanation: In the Screen Table Painter, yourequested the loading of a table definitionsuch that the total number of fields in thescreen table definition will exceed themaximum allowed.

Action: You can delete some of the existing fieldsor load fewer fields of the table.

Cannot LOGON from ID: %Source: Security

Explanation: You attempted to logon using adifferent userid from your host system userID. The request is refused because thepassword of the requested userid is null inthe user profile.

Action: Contact your Security Administrator andrequest that the password be reset to a non-null value. Unless external security is beingenforced, the Security Administrator shouldbe able to resolve the problem.

Cannot maintain@SYSTEM_PARMSETS(%)Source: Promotion

Explanation: This message follows:

WARNING: *** No PRM table for % ***

Table @SYSTEM_PARMSETS uses the PRMtable to track parameterized tables that havebeen promoted.

Action: Create a PRM table.

TIBCO Object Service Broker Messages Without Identifiers

Page 87: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 73

Cannot make the first primary key "%"a distribution pointSource: Table Definer

Explanation: You made the indicated primarykey field a distribution point. A distributionpoint must be a secondary index field. Sinceyou cannot build a secondary index againstthe first primary key field, you cannot chooseit as a distribution point.

Action: Select another field as the distributionpoint.

Cannot modify/delete enabled objectset "%", disable it and reapplySource: Promotion

Explanation: You cannot modify or delete thespecified object set because it has beenenabled.

Action: Use the security manager to disable thespecified object set and then reapply thechange request.

Cannot modify report "%" in Generator;use Report DefinerSource: Report Generator

Explanation: The indicated report definition wascreated or modified by the Report Definerand cannot be modified in the Generatoranymore.

Action: Use the Report Definer.

Cannot modify screen message duringscreen validationSource: Screen Server

Explanation: A validation rule has called theSCREENMSG tool while the Screen is in theprocess of being validated.

Action: Remove all calls to SCREENMSG fromthe validation rule.

Cannot move heading for field "%" to fitwithin columns 1 to %Source: Report Definer

Explanation: A column change for a field wasrequested. The change to the field COLrequires moving all headings for the fieldrelative to the new column position. Thisheading move cannot be accommodatedwithout extending a heading beyond themaximum report width.

Action: Remove the requested column change.Alternatively, you can type over yourheadings with some text that can be movedalong with the field to fit within themaximum report width.

Cannot obtain change rights for % "%"due to LOCKFAILSource: Report Definer

Explanation: Promotion rights cannot beobtained because of a locking error.

Action: Try using the Report Definer again later.

TIBCO Object Service Broker Messages Without Identifiers

Page 88: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

74 |

Cannot PAINT "%" -- screen table iswider than % columnsSource: Screen Definer

Explanation: The screen table you wish to paintis too wide.

Action: Redefine your screen table to be no morethan the allowed number of columnsindicated.

Cannot PASTE; % too many fields willresult (maximum is %)Source: Screen Definer

Explanation: You are trying to paste a copiedline, but the sum of the number of fieldsalready in the screen table definition plus thenumber of fields held for pasting exceeds themaximum number of fields allowed(currently 80).

Action: Do one of the following:

• If you still want to paste fields, removesome existing fields from the screen tabledefinition.

• SAVE the current screen table definition(held fields are discarded).

• CANCEL the Paint session.

Cannot PASTE within an existing fieldSource: Screen Definer

Explanation: You have pressed <PF17> to paste afield while the cursor is positioned within anexisting field.

Action: Position the cursor elsewhere, or movethe other fields, to allow the field to be pastedwhere first indicated.

Cannot PF4=TBLS; missingVIEW_DEFN permission for table "%"Source: Security

Explanation: You have requested to view tablespermissions while defining object setpermissions. To do so, you must haveVIEW_DEFN authorization for all of thetables in the list, since the definitions areconsulted for parameter information. You aremissing VIEW_DEFN for the named table, soyou cannot look at the list.

Action: You must obtain VIEW_DEFNpermission to the named table before beingable to look at or update the list of tablespermissions for this object set. Consult yourSystem Administrator.

Cannot pick more than one index fieldSource: Table Definer

Explanation: Invalid line command. Only oneindex base field can be included in an IMStable definition.

Action: Modify selection to include only oneindex base field.

Cannot place field here - overlap wouldresultSource: Screen Definer

Explanation: You have pressed <PF6> to add afield but the cursor is positioned on othercontents in the Image Area.

Action: Reposition the cursor, or move the othercontents, and press <PF6> again.

TIBCO Object Service Broker Messages Without Identifiers

Page 89: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 75

Cannot print Screen; no % for % %Source: General

Explanation: You cannot print a Screen for one ofthe following reasons:

• No screen tables exist for the indicatedScreen.

• No screen fields exist for the indicatedscreen table.

Action: Fix the offending Screen or screen tablebefore trying to print it.

Cannot purge a date range that is laterthan the current dateSource: Secure Audit Log

Explanation: You attempted to purge the auditlog contents of a date range which extendedbeyond the current date. This was notallowed since the audit log of current daycannot be purged.

Action: Correct the date range and try again.

Cannot recognize statement "%"Source: Rule Editor

Explanation: The statement beginning with thespecified keyword is not supported.

Action: Check the Processing manual for validstatements.

CANNOT refer more than once to %object "%"Source: Unload

Explanation: You have listed the same objectmore than once for unloading.

Action: Remove all but one of the references tothis object.

Cannot release rights; % is a deletedSystem ObjectSource: Promotion

Explanation: A system object that is deletedcannot have its rights released.

Action: Request the deletion of the objectthrough a change request.

Cannot release rights on % "%", rightsheld by % - requested %Source: Delete Definition

Explanation: You have requested to delete anobject but promotion rights for that object areheld by another user.

Action: You may not delete the object unless youobtain the promotion rights.

Cannot release rights on % "%", unableto verify rightsSource: Delete Definition

Explanation: Promotion rights for the objectcould not be released since they cannot beverified.

Action: If you do not have the promotion rightsfor the object, obtain them and then try again.Otherwise, just wait and then retry.

TIBCO Object Service Broker Messages Without Identifiers

Page 90: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

76 |

Cannot remotely apply a changerequest with rule to executeSource: Promotion

Explanation: You cannot apply change request toa remote node if that change has a rule toexecute.

Action: You have to extract the change from thesource system, transfer the data set to thetarget system (if both source and targetsystem do not reside on the same machine),and then apply the change using the PTmenu.

Cannot SAVE, object set "%" mustcontain the % for "%"Source: Security

Explanation: You cannot save the security for theobject set because the definition of the objectset itself must contain the indicated item.

Action: Modify the security of the indicatedobject so that the indicated item is no longerrequired to be present in the definition of theobject set.

Cannot save/delete "%"; rights held by%, requestor %Source: Report Generator

Explanation: You cannot save the indicatedreport because its promotion rights are heldin the indicated library by the indicated user.

Action: Contact the indicated user if you need tomodify the report.

Cannot SAVE: "%" does not matchglobal field definitionSource: Table Definer

Explanation: You cannot save the table definitionbecause the indicated field does not matchthe global field definition.

Action: Change the indicated field to match theglobal field definition. A list of global fielddefinitions can be obtained by pressing<PF14>.

Cannot SAVE: %Source: Session Manager

Explanation: You made a request to save, but aLOCK FAILURE or a SECURITY FAILUREhas prevented you from saving.

Action: Do the following:

• If a LOCK FAILURE has caused thisproblem, wait and try again. The USERIDlocking the information is shown in themessage and can be consulted with regardto how long you should wait.

• If a SECURITY FAILURE has caused thisproblem, consult your SecurityAdministrator to obtain appropriatepermissions. Alternatively, if the securityfailure is just a matter of trying to save amenu for which update permission is notallowed, you can select an entirely newname for the menu and save it until properauthorization is obtained. The messagewill have information about the type ofaccess that was denied.

TIBCO Object Service Broker Messages Without Identifiers

Page 91: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 77

Cannot SAVE: borrowing rightsUNVERIFIED for this menuSource: Menu Definer

Explanation: You have requested to SAVEchanges to a menu definition. However, sinceborrowing rights cannot be verified, youcannot save.

Action: Retry the SAVE command in case theborrowing rights can be verified afteranother try. Otherwise, you could change thename of the menu to a new name and try thesave again.

Cannot SAVE; "%" is specified morethan onceSource: Security

Explanation: You have specified the given namemore than once and this is not allowed.

Action: Remove the duplicate entries and try tosave again.

Cannot SAVE; %Source: Object Set Definer

Explanation: You defined an object set andrequested to SAVE. However, you includedtables for which you have no SECURITYpermissions.

Action: Remove the offending reference, thensave again. Obtain the required permissionsand then update the object set to include thetable as appropriate.

Cannot SAVE; including object set "%"results in a circular refSource: Object Set Definer

Explanation: You were unable to save because todo so would result in a circular reference ofobject sets. The simplest example of a circularreference is to have object set A contain objectset B, and object set B contain object set A.

Action: Remove the indicated object set from thecurrent object set.

Cannot SAVE; missing object "%"detected; DISABLE object setSource: Security

Explanation: You attempted to save an Object SetEnable List so that the object set has enabledstatus. The object set permissions definitionrefers to objects that do not exist. Thus, theobject permissions, according to thisspecification, cannot be applied.

Action: Complete the following steps:

1. Disable the object set.

2. Go to the object set permissions list for theobject set. Display each list of objects thatcompose the object set by pressing theappropriate PF key. When you press<Enter> the missing object will behighlighted and a message will explainthat the object does not exist.

3. When you find a missing object, remove itfrom the list.

4. Save the object set definition.

5. Return to the enable list and re-enable.

TIBCO Object Service Broker Messages Without Identifiers

Page 92: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

78 |

Cannot SAVE; missing table instancespecificationSource: Security

Explanation: You tried to save the tablespermissions for an object set definition, buttable instance information is missing for thehighlighted tables.

Action: Do one of the following:

• Place the cursor on a highlighted tableentry and use the PARMS function

• Cancel from the Table Permissions screento return to the Define ObjectSet screen

• Remove the highlighted table entry fromthe list of tables permissions

Cannot SAVE; no object permission hasbeen specifiedSource: Security

Explanation: You attempted to save withoutspecifying any object permissions for theobject set.

Action: Either cancel from this screen, or includethe permission of at least one object for thisobject set.

Cannot save; Replace failedSource: Field Dictionary

Explanation: You attempted to update thedefinition of a field, but the SAVE failed forsome reason, such as locking or security. Themessage following this one provides moreinformation.

Action: Do one of the following:

• If the problem was locking, retry theupdate.

• If the problem was security, contact thesecurity administrator for the proper

authority, or change the security to theappropriate level and group for updates tothe field dictionary table.

Cannot save; This field already existsSource: Field Dictionary

Explanation: You attempted to add a new field tothe global field dictionary, but the field nameduplicates one that already exists.

Action: Change the name of the field that you areadding.

Cannot SAVE (OVERWRITE willoccur); choose another nameSource: Session Manager

Explanation: You changed the name of a menu tothe name of an existing menu. Now you aretrying to save the menu, but because anoverwrite will occur, the save is not allowed.

Action: Replace the offending name with a newname and press <PF3> again.

Cannot SAVE changes; object part ofENABLED object setSource: Security

Explanation: You requested to save an objectpermissions list when the object is part of anenabled object set.

Action: You must cancel from this screen. To freethe object for individual changes, first use theAPPLICATIONS function to determinewhich enabled object sets include the objectand then have these object sets disabled.Alternatively, you can define another objectset that contains the permissions required forthe object and then enable this object set asappropriate.

TIBCO Object Service Broker Messages Without Identifiers

Page 93: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 79

Cannot SAVE changes; rights are heldby "%"; use CANCELSource: Screen Definer

Explanation: In the Screen Definer or the ScreenTable Painter, you requested to SAVE. Therights, however, are held by someone else,and therefore the changes cannot be saved.

Action: Do one of the following:

• Change the screen name to a nonexistingname and save the screen definition.

• Cancel your changes.

• Ask the person holding the rights torelease them and then try to save yourchanges.

Cannot SAVE changes -- undetermined% rights; try againSource: Screen Definer

Explanation: In the Screen Definer or ScreenTable Painter, you tried to save your changes.The rights to the current object, however,cannot be determined.

Action: Do one of the following:

• Wait and try again.

• Change the name of the Screen to a newname and save (this preserves the changesfor later).

Cannot SAVE changes to FCNKEYS;rights held by "%"; use CANCELSource: Screen Definer

Explanation: You tried to change the functionkeys for a Screen, but the rights for theFCNKEYS table instance are held by anotherperson.

Action: Do one of the following:

• Cancel your changes.

• Ask the person holding the rights torelease them.

• Change the name of the Screen to preserveyour changes.

Cannot SAVE Enabled object setwithout at least one memberSource: Security

Explanation: You attempted to save an object setenable list with the SAVE STATUS asENABLED, but no members are on theenable list.

Action: If you want to save the empty list, disablethe object set save status before saving. If theobject set must have the save statusENABLED, put one member on the list (i.e., auser or group).

Cannot save filter %; that filter alreadyexistsSource: Secure Audit Log

Explanation: You attempted to save a new filterdefinition but you used a name that hadalready been used by another user.

Action: Change the name of filter and try again.

Cannot SAVE globalfield "%", rightsheld by "%", requestor "%"Source: Field Dictionary

Explanation: The promotion rights for the globalfield you are editing are held by someoneelse. You cannot save the changes.

Action: Do one of the following:

• Change the global field name to anonexisting name and save the definition

TIBCO Object Service Broker Messages Without Identifiers

Page 94: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

80 |

• Ask the person holding the rights torelease them and then try to save yourchanges

• Cancel your changes.

Cannot save rule %, number ofconditions exceeds maximum of %Source: Rule Editor

Explanation: Unable to save rule because thenumber of conditions exceeds the maximumallowed in a rule.

Action: Reduce number of conditions in the ruleor try to separate the single rule into two ormore rules.

Cannot select "MONEY" or "D/C" forfunction "CNT"Source: Report Generator

Explanation: You cannot generate a Money orDebit/Credit mask for a COUNT field.

Action: If you want a mask, use the Commamask by entering a Y beside COMMA, andplace the cursor on the COUNT field.

Cannot select data & definition of sameparameterized table %Source: Promotion

Explanation: A parameter instance of a table andits definition cannot be promoted in the samechange request.

Action: Either select all instances to be promoted,or submit the selected instance as a separatepromotion request.

Cannot SELECT INSTANCES: no PRMtable defined for table "%"Source: Unload

Explanation: You have requested to specifywhich data instances of a table to unload;however, since no PRM table is defined forthe table named on the cursor row, theinstance list cannot be shown.

Action: To unload any data from a parameterizedtable, there must be a PRM table defined withthe parameterized table as a SOURCE.

Cannot share a BODY/TITLE reporttable as a BREAKSource: Report Definer

Explanation: You cannot use an existing bodyreport table as a break table.

Action: Remove the reference to the body tablename as a break table.

Cannot specify control fields withincontrol breaks or titlesSource: Report Definer

Explanation: Control fields (e.g., SORT, BREAK)cannot be specified within a control break ortitle report table.

Action: Request a CONTROL FIELD operationonly from within the Painter for a bodyreport table (i.e., a report table for whichTITLE ONLY=N).

TIBCO Object Service Broker Messages Without Identifiers

Page 95: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 81

Cannot specify selection without firstspecifying table nameSource: Batch Control Card

Explanation: You specified the selection criteriabut did not indicate which table the selectionspecification is for.

Action: Specify the name of the table for whichthe selection criteria apply or delete theselection criteria.

Cannot start literal at row % and col %Source: Screen and Report Painters

Explanation: A literal cannot be started at theindicated row and column.

Action: Move the literal so that it does not start atthe indicated row and column.

Cannot toggle prom on table %, rightsare not heldSource: Promotion

Explanation: You cannot change the PROM fieldof the named table because someone elsecurrently owns the rights to the table.

Action: No action required.

Cannot unload DATA from "%" --SECURITYFAILSource: Unload

Explanation: There is a security problem with theobject type definition data for one of theobjects you requested to unload.

Action: Report this to your SystemAdministrator since such a problem shouldnever arise for unloadable object types.

Cannot unload DATA from "%" --SYNTAX ERROR on SELECTIONSource: Unload

Explanation: There is a problem with the objecttype definition data for one of the objects yourequested to unload.

Action: Report this to your SystemAdministrator as this should not be aproblem for unloadable object types.

Cannot unload DATA from "%" -- tablenot foundSource: Unload

Explanation: There is a problem with the objecttype definition data for one of the objects yourequested to unload.

Action: Report this to your SystemAdministrator as there should not be aproblem for unloadable object types.

Cannot unload DATA from table oftype %Source: Unload

Explanation: You have requested to unloadDATA from a tab which is of a type that hasno data in it. You may unload only thedefinition of tables without data in them.

Action: Reset the DATA indicator to N.

TIBCO Object Service Broker Messages Without Identifiers

Page 96: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

82 |

Cannot unload data of table withminimal definitionSource: Unload

Explanation: You cannot unload the data of atable with minimal definition, full definitionis required.

Action: Restore the full definition of the tablewhich you want to unload.

Cannot unload defn of % object "%" --SECURITYFAILSource: Unload

Explanation: You have requested to unload anobject which includes by reference anotherobject. You do not have the correct securitypermissions to unload that object.

Action: You must obtain the correct permissionsto completely unload the object yourequested.

Cannot unload DEFN of table "%" --NOSUCH TABLESource: Unload

Explanation: You have requested to unload anobject which includes by reference thedefinition of a table. The referenced table hasno definition and so cannot be unloaded.

Action: No action required.

Cannot use derived field "%" to relatetablesSource: Report Generator

Explanation: You cannot use a derived field torelate source data tables.

Action: Remove the indicated derived field orreplace it with a non-derived field.

Cannot Validate: %Source: Screen Definer

Explanation: The Screen Definer was unable tovalidate this screen definition for the reasonindicated.

Action: Take the appropriate action based on thereason indicated.

Cannot VALIDATE screen data; storagedata is LOCKEDSource: Security

Explanation: In the course of normal processing,the data on any screen in the Securityinterface is validated. For example, the userprofile screen has validation to ensure thatthe requested Session Menu exists, that theDefault Library exists, and so on. If the dataused to validate the screen fields is locked,the validation does not complete and thescreen data cannot be said to be valid orinvalid.

Action: You can continue normal activities orcancel, if necessary.

Cannot VERIFY existence of "%";CONTROL TABLE not foundSource: Unload

Explanation: You have specified the name andtype of an object to unload; however, thereseems to be definitional data missing for thatobject type. When this is true, the existence ofthe object of that type cannot be verified.

Action: Remove the entry and report thisproblem to your System Administrator as thedefinition information for unloadable objecttypes should always be available in yoursystem.

TIBCO Object Service Broker Messages Without Identifiers

Page 97: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 83

Cannot verify promotion rights due toLOCKFAILSource: Report Generator

Explanation: The promotion rights of the reportcannot be verified because a system table islocked.

Action: Perform the action again later.

Cannot verify promotion rights due toLOCKFAILSource: Table Definer

Explanation: The promotion rights of the currenttable definition cannot be verified because asystem table is being blocked.

Action: Try to define the table again later.

Catalog Management error: Module ID"%" Return Code "%" Reason Code "%"Source: Builtin Routines

Explanation: Catalog Management encounterederrors while accessing the system catalog.The module name, return code, and reasoncode are supplied for problem determinationpurposes.

Action: Call your system administrator to checkthe return code in register 15 against theappropriate vendor's manual. Correct theproblem as required.

Certain overflowed value(s) ofparameter "%" are not shownSource: Report Generator

Explanation: Parameter values that do not fit inthe screen field are omitted from the list, butall other parameter values are shown.

Action: If the parameter value that you want islisted in the prompt area, you can select it.

If you want to choose one of the omittedvalues, do the following:

1. Select a value from the prompt area, andremember what it is.

2. Finish defining the report and save the rulethat generates the report.

3. Use the Rule Editor to modify the rule andchange the parameter value that youselected to the value that you want.

4. Run the report by executing the rule.

Change #% has not been appliedSource: Promotion

Explanation: You cannot back out a changeunless it has been applied.

Action: No action required.

Change #% or its associated changeshave been applied to the systemSource: Promotion

Explanation: You have already applied thespecified change number and/or itsassociated changes to this system and youcannot do it again.

Action: Do not apply the change again.

TIBCO Object Service Broker Messages Without Identifiers

Page 98: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

84 |

Change #% printedSource: Promotion

Explanation: The change request specified isprinted.

Action: No action required.

Change definition clearance required toalter indexesSource: TAM

Explanation: You called SIXBUILD orSIXDELETE and you do not have theauthority to change the table definition.

Action: Contact the Security Administrator.

Change definition clearance required toclear table occurrences withoutinvoking triggerSource: TAM

Explanation: You called CLRTAB to clear a table,but you do not have the necessary authority.

Action: Contact the security administrator.

Change group of USERID % to %Source: Audit Log Message

Explanation: The user changed to the specifiedgroup.

Action: No action required.

Change group of USERID % to %deniedSource: Audit Log Message

Explanation: The user cannot change the currentgroup to the specified group because the useris not a member of that group.

Action: The user can consult the SecurityAdministrator to become a member of thespecified group.

Change parameter nameSource: Table Definer

Explanation: You canceled your SAVE commandwhen you were warned that you have aparameter named NUMBER. This messageprompts you to change the parameter namefrom NUMBER to something else so that youcan define a PRM table on this table.

Action: Change the parameter name NUMBER.

Change request % does not existSource: Promotion

Explanation: You specified an incorrect changerequest number when you invoked one ofthe Promotion System rules.

Action: Correct the change request number.

Change request acceptedSource: Promotion

Explanation: You have accepted a changerequest. The status of the change request isnow A.

Action: No action is required.

TIBCO Object Service Broker Messages Without Identifiers

Page 99: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 85

Change request unacceptedSource: Promotion

Explanation: You have unaccepted a changerequest. The status of the change request isnow U.

Action: No action is required.

Changed archive file to: %Source: Secure Audit Log

Explanation: You made the specified file thearchive file for the audit log contents and thismessage informs you that the change wassuccessful.

Action: No action required.

Changes to control screen savedSource: Report Definer

Explanation: Saved the changes to the controlscreen.

Action: No action required.

Changes to default permissions forcreated libraries CANCELLEDSource: Security

Explanation: You canceled changes to the librarydefaults and you are viewing the SpecifyDefault Permissions screen. If you save theSpecify Default Permissions screen, thelibrary defaults are as they were at the lastSAVE to library defaults. For example,suppose you entered the Specify DefaultPermissions screen and performed thefollowing actions in this sequence:

1. Changed and saved the library defaults.

2. Changed and canceled the library defaults.

3. Saved the Specify Default Permissionsscreen.

The first changes to the library defaults arecommitted.

Action: No action required. If you want knowwhat the library defaults will be when yousave the Specify Default Permissions screen,view the Library Defaults screen again beforesaving.

Changes to default permissions forcreated reports CANCELLEDSource: Security

Explanation: You canceled changes to the reportdefaults and you are viewing the SpecifyDefault Permissions screen. If you save theSpecify Default Permissions screen, thereport defaults are as they were at the lastSAVE to report defaults. For example,suppose you entered the Specify DefaultPermissions screen and performed thefollowing actions in this sequence:

1. Changed and saved the report defaults.

2. Changed and canceled the report defaults.

3. Saved the Specify Default Permissionsscreen.

The first changes to the report defaults arecommitted.

Action: No action required. If you want knowwhat the report defaults will be when yousave the Specify Default Permissions screen,view the Report Defaults screen again beforesaving.

TIBCO Object Service Broker Messages Without Identifiers

Page 100: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

86 |

Changes to default permissions forcreated screens CANCELLEDSource: Security

Explanation: You canceled changes to the screendefaults and you are viewing the SpecifyDefault Permissions screen. If you save theSpecify Default Permissions screen, thescreen defaults are as they were at the lastSAVE to screen defaults. For example,suppose you entered the Specify DefaultPermissions screen and performed thefollowing actions in this sequence:

1. Changed and saved the screen defaults.

2. Changed and canceled the screen defaults.

3. Saved the Specify Default Permissionsscreen.

The first changes to the screen defaults arecommitted.

Action: No action required. If you want to knowwhat the screen defaults will be when yousave the Specify Default Permissions screen,view the Screen Defaults screen again beforesaving.

Changes to default permissions forcreated tables CANCELLEDSource: Security

Explanation: You canceled changes to the tabledefaults and you are viewing the SpecifyDefault Permissions screen. If you save theSpecify Default Permissions screen, the tabledefaults are as they were at the last SAVE totable defaults. For example, suppose youentered the Specify Default Permissionsscreen, and performed the following actionsin this sequence:

1. Changed and saved the table defaults.

2. Changed and canceled the table defaults.

3. Saved the Specify Default Permissionsscreen.

The first changes to the table defaults arecommitted.

Action: No action required. If you want to knowwhat the table defaults will be when yousave the Specify Default Permissions screen,view the Table Defaults screen again beforesaving.

Changes to enable list for object set "%"CANCELLEDSource: Security

Explanation: You were specifying the Enable Listfor some object set permissions. You canceledany changes you made by pressing <PF12>from the Enable List context.

Action: No action required.

Changes to enable list for object set "%"SAVEDSource: Security

Explanation: You made changes to an enable listfor an object set and saved the changes. Thismessage appears in the main menu.

Action: No action required.

Changes to filter % cancelledSource: Secure Audit Log

Explanation: You canceled changes to a filterdefinition.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 101: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 87

Changes to group "%" CANCELLEDSource: Security

Explanation: You canceled changes to a groupdefinition.

Action: No action required.

Changes to libraries permissions forobject set "%" CANCELLEDSource: Security

Explanation: You were specifying librarypermissions while defining object setpermissions. You requested to cancel anychanges you had made to thesespecifications. This does not affect anypermissions updated and saved in the othercontexts.

Action: No action required.

Changes to memberships kept; will bestored on SAVE USERSource: Security

Explanation: A Security Administrator madechanges in the Memberships screen of theUser Profile function. These changes arecommitted only if the User Profile is saved.

Action: No action required.

Changes to object set "%" CANCELLEDSource: Object Set Definer

Explanation: You have performed a CANCELfrom the Object Set Definer. Any changesmade to the object set have now beencanceled.

Action: No action required.

Changes to report "%" cancelledSource: Report Definer

Explanation: You pressed <PF12> to cancel anoperation for the report. Any changes madeto this screen are now canceled.

Action: No action required.

Changes to report "%" savedSource: Report Definer

Explanation: SAVE operation was requested forthe report. Any changes made to this screenare now saved.

Action: No action required.

Changes to reports permissions forobject set "%" CANCELLEDSource: Security

Explanation: You were specifying reportspermissions while defining object setpermissions. You requested to cancel anychanges you had made to thesespecifications. This does not affect anypermissions updated and saved in the othercontexts.

Action: No action required.

Changes to rule % cancelledSource: Rule Editor

Explanation: The changes just made to thenamed rule have not been saved.

Action: No action is required.

TIBCO Object Service Broker Messages Without Identifiers

Page 102: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

88 |

Changes to Screen "%" SAVEDSource: Screen Definer

Explanation: You saved changes to a screendefinition (using the Screen Definer), andreturned to the workbench successfully.

Action: No action required.

Changes to screens permissions forobject set "%" CANCELLEDSource: Security

Explanation: You were specifying screenspermissions while defining object setpermissions. You requested to cancel anychanges you had made to thesespecifications. This does not affect anypermissions updated and saved in the othercontexts.

Action: No action required.

Changes to Security Administrator "%"CANCELLEDSource: Security

Explanation: You canceled from a SecAdminprofile; all changes (including DISCLAIMS)are ignored.

Action: No action required.

Changes to tables permissions forobject set "%" CANCELLEDSource: Security

Explanation: You were specifying tablepermissions while defining object setpermissions. You requested to cancel anychanges you had made to thesespecifications. This does not affect anypermissions updated and saved in the othercontexts.

Action: No action required.

Changes to the STANDARD menu arenot allowedSource: Menu Definer

Explanation: You pressed <PF3> or <PF6> tosave changes to the STANDARD menu.

Action: To save your changes, change the nameof the menu.

Changes to userid "%" CANCELLED;Current Group is "%"Source: Security

Explanation: You canceled changes to your userprofile.

Action: No action required.

Changes to userid "%" CANCELLED;Current Group is nullSource: Security

Explanation: You canceled changes to your userprofile, and you are notified that you are notoperating out of any group.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 103: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 89

Changes to userid "%" CANCELLEDSource: Security

Explanation: You canceled from the user profilescreen. Any changes to the your profile ormemberships are ignored.

Action: No action required.

Changes to userid "%" SAVED; CurrentGroup is "%"Source: Security

Explanation: You saved the User Profile screen.Any changes made to the profile arecommitted and you are informed of yourcurrent group.

Action: No action required.

Changes to userid "%" SAVED; CurrentGroup is nullSource: Security

Explanation: You saved changes to your userprofile, and you are notified that you are notoperating out of any group.

Action: No action required.

Changes to userid "%" SAVEDSource: Security

Explanation: A Security Administrator or aSystem Administrator has saved changes to auser profile. Any changes to either the profileor the memberships are committed.

Action: No action required.

Check for an invalid printer nameSource: Report Server

Explanation: If report output has been directedto a system printer, either the name used inthe Execution Environment parameter isincorrect or the printer is not active.

Action: Verify printer name is valid and has beenstarted.

CHECKING FOR TABLEDEFINITIONS TO UNBINDSource: Promotion

Explanation: The Promotion tool is checking fortable definitions that it has to unbind topromote a new table definition.

Action: No action required.

CLC key must be syntax:B length:4 andnull Src & Source NameSource: Table Definer

Explanation: You specified the incorrectattributes for the CLC key field. The syntaxand length must be binary (B) and 4respectively, whereas the source indicatorand source name must be null.

Action: Modify the attributes for the key fieldaccordingly.

TIBCO Object Service Broker Messages Without Identifiers

Page 104: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

90 |

Clear access of TABLE % by % deniedSource: Audit Log Message

Explanation: The user is denied access to clearthe table using the CLRTAB builtin or the$CLRTAB builtin.

Action: The user can ask someone who hasCONTROL access to the table to provideDELETE or MODIFY_DEFN access, asrequired. CLRTAB needs both. $CLRTABneeds DELETE access.

CLEARANCE of user cannot exceedyour own (%)Source: Security

Explanation: While updating a User Profile forone of your subjects, you have specified theuser's clearance level to be higher than yourown. This is not allowed.

Action: Change the clearance specification forthe user to be less than or equal to your own.

CLEARANCE should NOT exceed %(that of Users SecAdmin)Source: Security

Explanation: You are updating a User Profile andhave set the user's clearance so that it exceedsthat of the SecAdmin of the user. TheSecAdmin will be unable to share ownershipprivileges with that user for any of the

objects owned by the user which have aclassification greater than that of theSecAdmin. This is due to mandatory securitypolicy which prohibits such access.

Action: The user's clearance should be set as lessthan or equal to that of the SecAdmin. Or theuser should be assigned to anotherSecAdmin with a higher clearance. This canbe done in the Manage SecAdmin for theuser's current SecAdmin or for the preferredSecAdmin.

Cleared table %Source: Copy Definition

Explanation: The specified table was cleared.This is part of the audit trail for the copy tool.

Action: No action required.

Close of "%" dataset failed; module "%";R15 = %Source: Session Manager

Explanation: Close of sort work data set failed.The DDNAME, the module name, and thereturn code are supplied for diagnosticpurposes.

Action: Call your system administrator to checkthe return code in Register 15 against theappropriate vendor's manual. Correct theproblem as required.

CLRTAB failed due to minimal tabledefinitionSource: Table Editor

Explanation: CLRTAB failed. Requested table tobe cleared is a minimal table definition.

Action: No action required. Refer to theShareable Tools manual for more informationabout CLRTAB.

TIBCO Object Service Broker Messages Without Identifiers

Page 105: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 91

Cntl Fld duplicate; % field "%" isreferred to more than onceSource: Report Definer

Explanation: The same field appears more thanonce in the Field Definition Area.

Action: Remove all redundant references to thesame field.

Codepage invalid for locale.codepage:%Source: TAM

Explanation: The codepage of the local.codepagecombination is invalid.

Action: Specify a correct codepage value.

COL specified is invalid : "-%"Source: Report Definer

Explanation: Only positive columndisplacements can be defined.

Action: Provide a positive column value in thedefinition of the indicated report field.

Column argument larger thanmaximum row sizeSource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Column argument less than 1Source: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Combination of table parameters,selection string, and ordering too longfor rule executorSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Command "%" is ambiguousSource: General

Explanation: Another primary command has thesame prefix as the indicated short-formcommand.

Action: Expand the command to make it unique.

TIBCO Object Service Broker Messages Without Identifiers

Page 106: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

92 |

Command "%" is not supported; <PF1>= HELPSource: General

Explanation: You entered an invalid command.

Action: Enter a valid command. If necessary,press <PF1> (Help) to see a list of the validcommands.

Command "%" is not supported; pressPF1 for HelpSource: Table Definer

Explanation: The indicated command is notsupported by the Table Definer for MetaStorIMS tables.

Action: Press <PF1> for a list of valid primarycommands or consult the Accessing IMSData manual.

Commit in % due to maximum numberof updates has been reachedSource: Copy Definition

Explanation: A commit was made in thespecified table. This is part of the audit trailfor the copy tool.

Action: No action required.

COMMIT LIMIT reached - SAVEupdates before continuingSource: Table Editor

Explanation: You have edited the maximumnumber of occurrences that the buffer willhold. These updates must be saved beforeyou can edit more occurrences.

Action: Type SAVE to save the updates beforecontinuing.

COMMIT while copying %Source: Copy Definition

Explanation: An intermediate commit was madesince commit limit was reached.

Action: No action is required.

COMMIT while deleting %Source: Copy Definition

Explanation: Committed the intent list whiledeleting the object. This is part of the audittrail for the copy tool.

Action: No action is required.

Communication area for "%" has notbeen suppliedSource: Builtin Routines

Explanation: A communication area must be setup by the caller of Object Service Broker if$GETENVCOMMAREA is to be called. Thisalso applies to $SETENVCOMMAREA insome environments.

Action: Confirm that you are using the rightenvironment/tool setup.

Communication area for "%" is toosmallSource: Builtin Routines

Explanation: The size of the parameter VALUE of$SETENVCOMMAREA exceeds the smallerof:

• Size of the communication area set up bythe caller of Object Service Broker.

• 32 KB - 1

Action: Use a bigger communication area or asmaller value.

TIBCO Object Service Broker Messages Without Identifiers

Page 107: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 93

Complete all key valuesSource: Table Editor

Explanation: You did not specify the values forall the key components of a composite keytable.

Action: Specify the values for all the keycomponents.

Complete cross-reference for library %has been DELETEDSource: Global Cross Ref. Search

Explanation: You asked to have the cross-reference deleted. This is done.

Action: No further action is required.

Complete table parametersSource: Table Editor

Explanation: When attempting to browse or edita parameterized table you have pressed<Enter> before supplying the values for theparameter(s).

Action: Do one of the following:

• Supply parameter value(s).

• Press <PF3> or <PF12> to exit from theprompt.

Completed CLEAR of DATA of table: %Source: Copy Defn/Data

Explanation: This message confirms that datawas deleted from the table.

Action: No action.

Composite key components must beconsecutiveSource: Table Definer

Explanation: You cannot have fields that are notpart of the composite key between fields thatare part of the composite key.

Action: Either make the non-key field a key field,or move the field after the last keycomponent.

CONFIRMATION NOT RECEIVED,CHANGE REQUEST NOT SENTSource: S6BTLADM - SEGMENT/DASD

Explanation: You failed to press the requiredfunction key to confirm your change request.The pending changes have been abandoned.

Action: No action required.

CONFIRMATION NOT RECEIVED,PREVIOUS REQUEST IGNOREDSource: S6BTLADM-Resource Management

Explanation: The prior request was one whichresulted in a confirmation prompt before theaction could be performed. The response tothe prompt was not valid to allow the actionto continue. The original action requestedwill be ignored.

Action: No action.

TIBCO Object Service Broker Messages Without Identifiers

Page 108: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

94 |

Conflicting attributes: PROTECTED &REQUIREDSource: Screen Definer

Explanation: You have defined a field withPROTECT=Y and RQD=Y. This isincompatible as you cannot change aprotected field.

Action: Change PROTECT=N or RQD=N, orchange both to N.

Connection failed, reason=x"%"Source: TAM

Explanation: The gateway/server failed toconnect to the Data Object Broker.

Action: Take appropriate action, depending onthe RETURN and REASON codes followingthe character x, which are described below:

• 0800 - Compatibility code not supplied:contact TIBCO Support.

• 0804- Compatibility-level error: contactTIBCO Support.

• 0808 - Connection type parameter was notsupplied: contact TIBCO Support.

• 080C - Userid parameter not supplied:contact TIBCO Support.

• 0810 - Connection type parameter(RGNTYPE) value is not valid: contactTIBCO Support.

• 0814 - Fail Safe level 1 required. DataObject Broker is at Fail Safe level 1 andrequires that all gateways/servers connectwith Fail Safe level 1.

• 0818 - Gateway/server type/ID value notsupplied: contact TIBCO Support.

• 081C - Tam gateway/server connectionrejected, invalid partner identifier: contactTIBCO Support.

• 0C00 - Object Service Broker is notaccepting any logons. Object ServiceBroker is possibly in a quiesce state oroperator stopped logon access.

• 0C04 - Storage not available: contactTIBCO Support.

• 0C08 - Connection restricted to operatorsat this time by request of the Object ServiceBroker administrator.

• 0C0C - Batch connections are not beingaccepted at this time by request of ObjectService Broker administrator.

• 0C10 - Userid is already active. Previousgateway/server started with identicalIDPREFIX parameter. Change theIDPREFIX startup parameter and restartthe gateway/server.

• 0C14 - Execution Environment limitalready reached: contact TIBCO Support.

• 0C18 - Peer region is not specified inregion's PEERS Data Object Brokerparameter: contact TIBCO Support.

CONNECTION LIST RETRIEVALERRORSource: S6BTLADM - USER ACTIVITY

Explanation: When attempting to retrieveinformation to build the next screen an errorwas detected.

Action: Review the joblog for possible additionalmessage which may help identify the causeof the problem. Retry your request. If theproblem persists contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 109: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 95

CONNECTION TO THE DATAOBJECT BROKER FAILED, RC=XXXXSource: S6BTLADM - COMMON MESSAGES

Explanation: After the communication pathwayto the desired Data Object Broker wasacquired, the request to initiatecommunication was rejected. Refer toS6BKC036 for return code explanation.

Action: Refer to the accompanying messages todetermine the appropriate action.

Connection with Data Object BrokerlostSource: TAM

Explanation: Communication with the DataObject Broker has been lost. This may becaused by a VTAM or Cross MemoryServices error, or because the Data ObjectBroker is not available.

Action: Verify that the Data Object Broker isstarted and available. You can also checkprevious messages for more information.

Content is pending placement; use<PF17> to PASTESource: Screen Definer

Explanation: The contents have been cut, andthey are awaiting placement.

Action: Paste the contents.

Continue request %Source: Promotion

Explanation: You have accepted or canceled yourcontinued modifications to an existingchange request.

Action: No action required.

CONTROL access allowed for useridentries only; "%" is a GroupSource: Security

Explanation: Either while specifying defaultpermissions, or while managing permissionsto an individual object, you specified that agroup is to have control access to an object.Control access is permitted for userids only.

Action: If you want everyone in the group to beallowed to control the object, you can use theVIEW GROUP function to view and select allthe users in the Group. If any new membersare added to the group after this, you willhave to add each new user to the permissionslist manually, or remove the group entryfrom the list by replacing it with blanks,nulls, or another user name.

If you do not want everyone in the group tohave control access, set the control mode toN for the group entry.

Control card specification cancelledSource: Batch Control Card

Explanation: The control card specification is notsaved and all changes are canceled asrequested.

Action: No action required.

Control card specification savedSource: Batch Control Card

Explanation: The control card specification forthe Batch Unload utility was saved asrequested.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 110: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

96 |

Control field specified as "%-by" not adefined report fieldSource: Report Definer

Explanation: The field specified for the controlattribute is not a report field which appearsin the definition area of the report table.

Action: Correct the report field name on thecontrol screen or add it to the definition area.

Controlling field "%" of break "%" isnot a report field of the body of report"%"Source: Report Server

Explanation: The report field that a break isbased on must be a report field of the bodyreport table.

Action: Use the Report Definer to correct thedefinition of the report.

Controlling report table "%" of report"%" overlays a titles report tableSource: Report Server

Explanation: The starting row for a body reporttable overlaps the rows of a title report table.

Action: Either start the body on an unused row,or move the origin of the title report tables.

Controlling table "%" of break "%" isnot the body of report "%"Source: Report Server

Explanation: The controlling table field of thenamed report break table is not the bodytable name of the report. Only one bodyreport table is allowed for a report.

Action: Use the Report Definer to correct thedefinition of the report.

Conversion error between valueselected from PROMPT and targetSource: Field Help for Reference

Explanation: The value selected from the promptcannot be converted into the type and syntaxof the target field.

Action: Contact your System Administrator.

Conversion error detected whencomputing report function "%"Source: Report Server

Explanation: The string OF-Field of a reportfunction contained a value that cannot beconverted to a number.

Action: Verify the input data for the OF-Field ofthe report function.

Conversion error for field "%". Containsrestricted value for High LevelLanguage program bufferSource: Builtin Routines

Explanation: In converting table data forpresentation to a High Level LanguageInterface program, a field has been found tocontain a restricted value that is used torepresent an "unassigned" field value. Thisvalue is the smallest negative value that thefield can hold. For a 2-byte binary field, thevalue is -32,768. For a 4-byte binary field, thevalue is -2,147,483,648.

For data integrity reasons, processing isterminated because Object Service Brokercannot differentiate between a legitimatevalue and the "null" designation.

Action: The restricted value must be removedfrom the field occurrence before theconversion can successfully proceed.

TIBCO Object Service Broker Messages Without Identifiers

Page 111: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 97

Conversion error for field "%" whilereading from High Level Languageprogram bufferSource: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

Conversion error for field "%" whilewriting to High Level Languageprogram bufferSource: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

Conversion error on assignment to %.%,possible definition errorSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Conversion error on table %; occurrenceskipped % %Source: Unload/Load

Explanation: The syntax of a table field isincompatible with the target table field.LOAD bypasses the table occurrence anddoes not load it.

Action: Ensure that the definition of the table,screen, or report is correct.

Conversion error when evaluatingsource of report field "%" of report table"%"Source: Report Server

Explanation: The value of the source cannot beconverted to the type and syntax of thederived report field. Either the value is toobig to be stored in the derived report field, orthe value is a nonnumeric string, and thederived report field has a numeric syntax.

Action: Do one of the following:

1. Use the Report Definer to enlarge thederived report field.

2. Use the Report Definer to look at thesource of the derivation and determinewhere the nonnumeric string is produced.

Conversion error while buildingOBJECT argument for debuggerSource: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

Conversion of field "%" to a stringfailed; Conversion not allowed to stringSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The value of the i-thfield could not be converted to a string.

Action: Contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 112: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

98 |

Conversion of field "%" to a stringfailed; Field contains bad data bytesSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The value of the i-thfield contains invalid data for the type andsyntax of the field. The table data may becorrupt.

Action: Contact TIBCO Support.

Conversion of field "%" to a stringfailed; Field type and/or syntax notallowedSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The value of the i-thfield has an invalid type and/or syntax.

Action: Contact TIBCO Support.

Conversion of field "%" to a stringfailed; String value is too largeSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The value of the i-thfield is too long for formatting. Strings arelimited to a maximum of 256 characters.

Action: Contact TIBCO Support.

Conversion parameter error detected in%. Conversion of % % to % % failedSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Conversion routine parameter errordetected for % routine "%"Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Copied % field(s) from the fielddictionarySource: Field Dictionary

Explanation: The % represents the number offields copied from the dictionary list.

Action: No action required.

Copied % from % where % = %Source: Copy Definition

Explanation: Copied an object X from Y where"field name" = "instance". This is part of theaudit trail for the copy tool.

Action: No action is required.

Copied % from %Source: Copy Definition

Explanation: Copied X from Y. This is part of theaudit trail for the copy tool.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 113: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 99

Copied reference data table %Source: Copy Definition

Explanation: Copied the indicated referencetable. This is part of the audit trail for theCOPY tool.

Action: No action required.

Copied reference data table %Source: Copy Defn/Data

Explanation: The copy of the named referencedata table was successful.

Action: No action required.

COPY/APPEND error - table "%" is notdefinedSource: Report Definer

Explanation: You tried to copy or append a tablethat does not exist.

Action: Change the table name given for theCOPY or APPEND command to an existingtable.

COPY/APPEND performed.WARNING: CONTROL info notcopiedSource: Report Definer

Explanation: The requested COPY or APPENDhas been performed. Control information(e.g., SORT, BREAK) has not been copied.

Action: No action required.

COPY/APPEND performed.WARNING: Not all requested fields arecopiedSource: Report Definer

Explanation: The requested COPY or APPENDhas been performed, but not all the selectedfields could be copied because of insufficientspace.

Action: No action required.

Copy failed: "%" is an invalid librarynameSource: Copy Rule or Copy Library

Explanation: The name of the library is eitherlonger than 8 characters or it does not followObject Service Broker syntax rules for validnames.

Action: Check the Processing manual for validname syntax and reenter the command.

Copy failed: % library "%" not foundSource: Copy Rule or Copy Library

Explanation: The indicated source or destinationlibrary cannot be found.

Action: Verify the existence of the indicatedlibrary.

Copy failed: %Source: Copy Definition

Explanation: The copy operation has failed.

Action: Press <PF2> to see the log for the cause ofthe failure.

TIBCO Object Service Broker Messages Without Identifiers

Page 114: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

100 |

Copy failed: %Source: Copy Defn/Data

Explanation: This message indicates that thecopy failed and why.

Action: No action.

Copy failed: Source and Destinationlibraries are the sameSource: Copy Rule or Copy Library

Explanation: You have to copy rues from onelibrary to different one.

Action: Change either the source or destinationlibrary so the two libraries are not the same.

Copy failed: locking prevents copy tolibrary "%"Source: Copy Rule or Copy Library

Explanation: The COPY failed. Another user hasa read lock on that library or is updating thesame rule that you are trying to copy.

Action:

1. Wait and retry the COPY.

2. Contact the owner of the library todetermine what the conflict might be.

Copy failed: no rule "%" in library "%"Source: Copy Rule or Copy Library

Explanation: The rule named as the source forthe COPY does not exist in the specifiedlibrary.

Action: Verify the existence of the rule in thesource library and the name of the rule.

Copy failed: security prevents copy tolibrary "%"Source: Copy Rule or Copy Library

Explanation: You attempted to copy to a librarythat has a security level or group that isoutside your classification.

Action: Contact the Security Administrator orlibrary owner to obtain update access to thedestination library.

Copy failed: security prevents copyingfrom library "%"Source: Copy Rule or Copy Library

Explanation: Your request to copy a set for rulesfrom the specified library could not becompleted. You do not have sufficientclearance or sufficient permissions (bothVIEW_DEFN and READ) to copy rules fromthis library.

Action: Contact your Security Administrator orthe libraries owner and request sufficientclearance/permission to copy rules from thislibrary.

Copy failed: Source library % is emptySource: Copy Rule or Copy Library

Explanation: There are no rules to copy in thesource library.

Action: Copy from a library which is not empty.

TIBCO Object Service Broker Messages Without Identifiers

Page 115: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 101

Copy failed: Table @DEFNS is emptyand Source and Dest locations are thesameSource: Copy Defn/Data

Explanation: When copying within one location,you have to avoid copying an object ontoitself by changing the name, or library in caseof a rule.

Action: Populate the @DEFNS table to controlname and library. See the manual.

Copy failed: unable to copy rule "%"Source: Copy Rule or Copy Library

Explanation: The COPY failed when copying thespecified rule.

Action: Contact the owner of the library. Ensurethat no other users are accessing thedestination library, then retry the COPY.

Copy failed: unable to copy to library"%"Source: Copy Rule or Copy Library

Explanation: The specified library is known to bean invalid destination for the COPYprogram.

Action: Change the destination library name.

Copy failed: unable to update library"%"Source: Copy Rule or Copy Library

Explanation: An error was encountered whenupdating the destination library with therule; an access problem exists for this library.

Action: Contact the owner of the library or theSystem Administrator to check thedestination library.

Copy process ended: at least 1 objectwas not copied. Press PF2Source: Copy Definition

Explanation: A problem has occurred whencopying at least one of the objects. Bypressing <PF2>, you will see a log of thecopy.

Action: Press <PF2> to see the log of the copy tofind out where the error occurred.

Copy request cancelledSource: Screen Definer

Explanation: In the Screen Table Painter, yourequested and then canceled the COPYoperation.

Action: No action required.

Copy successfulSource: Copy Definition

Explanation: The COPY operation has beensuccessfully completed.

Action: No action required.

Core Item entry DELETEDSource: General Table Definer

Explanation: You requested to delete an entryfrom some core information about theMetaStor table you are defining and the itemhas been deleted.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 116: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

102 |

Correct syntax is "ch str1 str2 {all}"Source: Character-based Text Editor

Explanation: Your CHANGE command has asyntax error. The correct syntax is given inthe message.

Action: Check that your CHANGE command isin the correct form. For example, if you wantto change all occurrences of the string"today" to "tomorrow", you would enter thecommand as:

ch today tomorrow all

Correct syntax is "f str"Source: Character-based Text Editor

Explanation: Your FIND command has a syntaxerror. The correct syntax is given in themessage.

Action: Check to ensure that your FINDcommand is of the correct form.

Could not access session logSource: Batch Client

Explanation: The session cannot create the log orwrite to the log.

Action: Check the log file path.

Could not find field/literal to beremovedSource: Screen and Report Painters

Explanation: The field/literal to be removedcould not be found.

Action: No action required.

Could not find object "%" for breakevent "%"Source: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

Could not find reference for %Source: Copy Definition

Explanation: The reference data for the indicatedobject could not be found. This is part of theaudit trail for the copy tool.

Action: Make sure that the object has data.

Could not find reference for %Source: Copy Defn/Data

Explanation: The reference data table could notbe found.

Action: No action.

Could not OPEN/READ file; pleaserespecifySource: Unload/Load

Explanation: The file name or path was notcorrect, or the file was not of the correct type.

Action: Check the file name, and path if present.Check that the file is an unload file, and thatit was written with the same DSBIFTYPEparameter as you have set now.

TIBCO Object Service Broker Messages Without Identifiers

Page 117: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 103

Could not OPEN/WRITE file; pleaserespecifySource: Unload

Explanation: You have requested to have thespecified objects unloaded into the specifiedfile; however, the file could not be opened orwritten to.

Action: To have the specified objects unloaded,you must supply a file name which can beboth opened and written to.

Could not open dataset for "%", %Source: Builtin Routines

Explanation: You called routine @READDSN or@WRITEDSN, but the data setcorresponding to the DSNAME argument ofthe routine @OPENDSN cannot be opened.

Action: Check that the specified data set isdefined.

Count field must be syntax:B length:4Src:C Source Name:COUNTSource: Table Definer

Explanation: The count field that you specifiedhas incorrect attributes.

Action: Modify the attributes accordingly.

Countfield must be entered forrepeating structuresSource: Adabas Definer

Explanation: Missing value for NAME OFCOUNTFIELD. This field is required fortable definition with repeating fields.

Action: Enter ADABAS field name forcountfield.

Create definition of GROUP % by %Source: Audit Log Message

Explanation: The specified group definition wascreated.

Action: No action required.

Create definition of LIBRARY % by %Source: Audit Log Message

Explanation: The specified library object wascreated.

Action: No action required.

Create definition of PRM TABLE to %by % deniedSource: Audit Log Message

Explanation: The user tried to create a PRM table(which is a list of the parameter values) of asource table and has been denied.

Action: The user can ask someone who hasCONTROL access to the source table toprovide DEFINE_PRM access.

Create definition of REPORT % by %Source: Audit Log Message

Explanation: The specified report object wascreated.

Action: No action required.

Create definition of SCREEN % by %Source: Audit Log Message

Explanation: The specified screen object wascreated.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 118: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

104 |

Create definition of TABLE % by %Source: Audit Log Message

Explanation: The specified table object wascreated by the indicated user.

Action: No action required.

Create definition of USERID % by %Source: Audit Log Message

Explanation: A new Object Service Broker useridwas added to the system.

Action: No action required.

Create definition of VIEW TABLE to %by % deniedSource: Audit Log Message

Explanation: The user attempted to define aSUBVIEW for a table and has been deniedaccess.

Action: Ask someone who has CONTROL accessto the source table to provide DEFINE_VIEWaccess.

Creating NEW library "%" (empty ruleslist bypassed)Source: Define Library

Explanation: You made a request to define a newlibrary. No rules are in the library, so theusual first screen is bypassed and you see thedocumentation screen immediately.

Action: No action required.

Creating NEW SecAdmin "%"Source: Security

Explanation: When a new SecurityAdministrator profile is created, the creatorsees this prompt in the initial SecAdminprofile as a reminder that this SecAdmindoes not currently exist.

Action: No action required.

Creation of NEW library "%"CANCELLEDSource: Define Library

Explanation: You canceled a library definition fora library that did not yet exist.

Action: No action required.

Cross reference complete. See messagelogSource: Global Cross Reference Build

Explanation: REFMAKER has succeeded inbuilding a new cross reference. Rulescontaining indirect calls are listed in themessage log.

Action: The list of rules in the message logshould be used to maintain the table@IND_CALLS.

CTABLE for DB2 data too large for tableSource: TDS

Explanation: The DB2 table contains too manyfields.

Action: Reduce the number of fields in the DB2table definition or contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 119: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 105

CTABLE for IMS data too large for tableSource: TDS

Explanation: The IMS table contains too manyfields.

Action: Do the following:

• Reduce the number of fields in the IMStable definition.

• Contact TIBCO Support.

CTABLE segment data for IMS datamissing at level %Source: TDS

Explanation: The IMS table or the associated IMSdatabase is incorrectly defined.

Action: Check the table and database definitions.

Current date can not be in given daterangeSource: Secure Audit Log

Explanation: You attempted to purge the auditlog contents of a given date range and thatrange included today's date. This was notallowed since the audit log contents of thecurrent day could not be purged.

Action: Change the date specification to excludethe current date and try again.

Current Group cannot be "ALL";instead use NO current groupSource: Security

Explanation: In the User Profile, you made arequest to change the current group to ALL.This is not valid.

Action: To indicate that you do not want tooperate out of a group, remove the ALL entryfrom the CURRENT GROUP field by usingthe EOF key or by overstriking the entry withblanks. Your requests to access data will beauthorized if your userid or the group ALLare allowed the requested access.

CURRENT GROUP changed to "%"Source: Security

Explanation: You changed the CURRENTGROUP field in the user profile and pressed<Enter> or a PF key. The current group ischanged as requested.

Action: No action required.

CURRENT GROUP changed to null(not operating out of any group)Source: Security

Explanation: In the User Profile screen, youchanged the CURRENT GROUP field toNULL and pressed <Enter> or a PF key.

Action: No action required.

Cursor % has already been defined, nocode generatedSource: Host Language Interface

Explanation: A cursor by the same name hasalready been declared.

Action: Change the name of this cursor, orremove the previous cursor declaration.

TIBCO Object Service Broker Messages Without Identifiers

Page 120: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

106 |

Cursor % is not defined or does notaccess table %Source: Host Language Interface

Explanation: The cursor used in this command iseither not declared, or is declared to access adifferent table.

Action: Change the cursor in the query or correctthe cursor declaration.

Cursor % is not definedSource: Host Language Interface

Explanation: This query references a cursor thathas not been declared.

Action: Check the cursor name; if necessary,declare the cursor.

Cursor % is not openSource: Host Language Interface

Explanation: This query attempts to use a cursorthat has not been opened.

Action: Add the command to open the cursor.

Cursor % must have parametersspecified explicitly for DELETESource: Host Language Interface

Explanation: The declaration of the indicatedcursor does not include parameter values.These must be included in the cursordeclaration for DELETE.

Action: Correct the cursor declaration.

Cursor does not have % fieldsSource: Host Language Interface

Explanation: The declaration of the cursor doesnot specify the indicated number of fieldsthat are required for this command.

Action: Correct the command or the cursordeclaration.

Cursor is not positioned on a fieldSource: Screen Definer

Explanation: To perform the operation you haverequested, the cursor must be positioned on afield in either the Image or Definition areas ofthe screen.

Action: Move the cursor so that it is positionedon the desired field in either the Image orDefinition areas of the screen. Then performthe desired operation again.

Cursor must be positioned on a screentable entrySource: Screen Definer

Explanation: You have pressed <PF6> to paint ascreen table but the cursor is not positionedon a screen table.

Action: Position the cursor on a row containing ascreen table entry, and press <PF6> again.

TIBCO Object Service Broker Messages Without Identifiers

Page 121: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 107

Cursor must be positioned on the % tobe %Source: General

Explanation: You made a request to DELETE,PAINT, or perform some other option thatrequires the cursor to be positioned on thechosen object. You did not position the cursoras required.

Action: Position the cursor properly and reenterthe command or press the PF key.

CURSOR POSITION INVALID,PLEASE POSITION ON DESIREDNODE NAME AND RETRYSource: S6BTLADM-Resource Management

Explanation: The system was not able to identifythe node name for which the previousrequest was raised.

Action: Reposition the cursor and try the requestagain.

CURSOR POSITION INVALID,PLEASE POSITION ON DESIREDPATH LINE AND RETRYSource: S6BTLADM-Resource Management

Explanation: You must identify the desired thepath you wish to process before pressing<PF11> to stop a specific gateway/server.

Action: Reposition the cursor and try again.

CURSOR POSITION INVALID,PLEASE POSITION ON DESIREDRESOURCE AND RETRYSource: S6BTLADM-Resource Management

Explanation: When attempting to display theResource Detail entry the system was unableto identify the desired entry's type andgroup.

Action: Position the cursor on the desiredresource name and press Enter.

CURSOR POSITION INVALID,PLEASE POSITION ON THEDESIRED SCHEDULE AND RETRYSource: S6BTLADM-Resource Management

Explanation: The system was not able to identifythe desired schedule to process for aSchedule Display of Association List request.

Action: Reposition the cursor on a displayedschedule name and retry your request.

CURSOR POSITION INVALID FORDETAIL DISPLAY SELECTIONSource: S6BTLADM - USER ACTIVITY

Explanation: When attempting to identify aconnection via cursor positioning an errorwas detected.

Action: Reposition your cursor and retry therequest.

TIBCO Object Service Broker Messages Without Identifiers

Page 122: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

108 |

CURSOR POSITION NOT ON VALIDENTRY, PLEASE RETRYSource: S6BTLADM - INDOUBT TRX

Explanation: When you selected a functionrequiring item selection by cursor positionthe processing was unable to identify whichentry was specified.

Action: Reposition the cursor and try yourrequest again.

CUT not allowed ... some content isalready heldSource: Screen Definer

Explanation: You have pressed <PF5> to cut afield but some information is already beingheld after being cut or copied.

Action: Press <PF17> to paste the informationbeing held before requesting CUT again.

TIBCO Object Service Broker Messages Without Identifiers

Page 123: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 109

Messages beginning with: D

DASD STATS ARE NOT AVAILABLESource: S6BTLADM - SEGMENT/DASD

Explanation: A segment must be online in orderto obtain the related DASD statistics.

Action: Either bring the segment online or selecta segment that is online to review its DASDstatistics.

DAT Field Name % not in CA-Datacomtable %Source: CA Datacom Table Definer

Explanation: You referred to a CA-Datacom fieldthat is not part of the CA-Datacom table onwhich you are defining the Object ServiceBroker DAT table.

Action: Remove the entry. You can use theFIELDS function to determine valid CA-Datacom fields.

DAT table defn must reference CA-Datacom NameSource: CA Datacom Table Definer

Explanation: You did specify a CA-Datacomtable name for this Object Service BrokerDAT table definition.

Action: You must specify the CA-Datacom tablename; press <PF1> to see a list.

DAT tables cannot havePARAMETERS definedSource: CA Datacom Table Definer

Explanation: You have requested to specifyPARAMETERS for this DAT Table Definition.Parameters are not supported for DAT tables.

Action: No action required.

Data error detected in %. Conversion of% % to % % failedSource: Interpreter

Explanation: You tried to do an operation orassignment of incompatible data types. Forexample, if you type

'A' + 1

you get a message such as:

Data error detected in ADDITION. Conversion of VARYING CHARACTER to BINARY failed.

Action: Verify that the operands of theexpression involved are compatible with theoperation performed.

Data error detected in conversion ofargument # of % routine "%"Source: Interpreter

Explanation: A routine was called with anargument value that cannot be converted tothe syntax of the routine argument.

Action: Verify the argument value that you passto the routine.

TIBCO Object Service Broker Messages Without Identifiers

Page 124: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

110 |

Data exists in % definition; cannot saveas % definitionSource: Table Definer

Explanation: Data has been added to the tabledefinition since the Table Definer wasopened but the table type has been changed.

Action: Save as a new table definition or exitwithout saving.

Data exists on local node; cannot save asminimal definitionSource: Table Definer

Explanation: Data has been added to the localcopy of the table since the Table Definer wasopened but you are attempting to save as aminimal definition.

Action: Save as a new table definition or exitwithout saving.

Data extracted for DBID - % FILE NO. -%Source: Adabas Extract

Explanation: ADABAS definition for thespecified DBID and File No has beenextracted.

Action: No action required.

Data item in expression has an invalidsyntax typeSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

DATA must be set to "Y" before usingINSTANCE SELECT functionSource: Unload

Explanation: You have requested to specifywhich instances of the table to unload;however, the DATA indicator for the table isset to N, indicating that you do not want tounload the data.

Action: If you wish to unload the data andspecify which instances of data to unload, setDATA to Y, then request INSTANCE SELECTagain.

DATA OBJECT BROKER BUFFER ISTOO SMALLSource: S6BTLADM - PAGE DISPLAY

Explanation: The buffer allocated by the DataObject Broker is too small to hold the resultdata.

Action: Contact Tibco Support

Data parameter is not allowed for "%"table typeSource: Table Definer

Explanation: You have specified a dataparameter which is not allowed for the giventable type.

Action: Remove the data parameter from thetable definition.

TIBCO Object Service Broker Messages Without Identifiers

Page 125: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 111

Data parameter must have % attributeset to %Source: Table Definer

Explanation: The SOURCE, SOURCENAME andDEFAULT attributes apply only to thelocation parameter. A data parameter musthave these attributes assigned NULL values.

Action: Specify a null value for the givenattribute of the data parameter.

Data set "%" not foundSource: Promotion

Explanation: Objects that you want to extractand apply to another system must go to aninterim data set. The specified data set doesnot exist.

Action: Allocate a data set.

Data set name has to be specified for"%"Source: Batch Control Card

Explanation: You did not specify the data set foreither the control card specification or theselection specification.

Action: Specify the data set as required.

Data set parameter of VSM table mustbe syntax %, length <= %Source: Table Definer

Explanation: A data set parameter of a VSAMtable is restricted to the indicated syntax andmaximum length.

Action: Modify the syntax and length of theparameter accordingly.

Data tables LOCKED; displayingUNCHANGED Screen definitionSource: Screen Definer

Explanation: In the Screen Definer, yourequested to DISPLAY the definition. Thedata store, however, is locked, so the Screenthat is displayed is the one that existed whenyou entered the Screen Definer.

Action: No action required. If you want todisplay the Screen that you modified in theScreen Definer instead of the original one, tryagain later.

Data tables LOCKED; only definitionprinted (not screen image)Source: Screen Definer

Explanation: You requested to PRINT the screendefinition from the Screen Definer, but thedata store is locked. The definition that wasprinted is the screen currently defined in theScreen Definer, but its screen image cannotbe printed.

Action: No action required. If you want to printthe screen image as well, try again later.

Database maintenance levelunavailableSource: Promotion

Explanation: The database maintenance level isunavailable from the expected table.

Action: Contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 126: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

112 |

Dataset "%" for "%" not allocated,dynamic allocation error; RC = %, error= %, info = %Source: Builtin Routines

Explanation: The tool ALLOCDSN failed. Thedynamic allocation return code, error code,and info code are supplied.

Action: To determine the nature of the error, lookup the error code in your operating systemmanual.

Dataset "%" for "%" not foundSource: Builtin Routines

Explanation: The argument DSNAME of theALLOCDSN tool must be the name of anexisting sequential data set.

Action: Verify the name of the data set or allocateone with that name.

Date return value for "%" overflowSource: Builtin Routines

Explanation: The value returned by the indicatedtool is too large to be stored in the datevariable.

Action: If the date variable is defined as binary 2,increase the size to binary 4. Otherwise,contact TIBCO Support.

DB2 creator and/or table does not exist:%.%Source: Table Definer

Explanation: The specified DB2 Creator or table(or both) does not exist in the DB2 database.

Action: Press <PF4> for a list of tables in the DB2database.

DB2 creator does not exist: %Source: Table Definer

Explanation: The indicated creator does not existin the DB2 database.

Action: Enter an existing creator or press <PF4>to select one.

DB2 Gateway unavailable or requestabortedSource: TAM

Explanation: The DB2 Gateway was not startedor it failed.

Action: Verify that the DB2 Gateway and theData Object Broker are started and available.If this problem persists, contact TIBCOSupport.

DB2 Table %.% not found in the DB2catalogSource: Static SQL for DB2 Gateway

Explanation: The creator.table was not found inthe DB2 catalog. If a LOCAL catalog is beingused ensure that it is up to date with thecurrent DB2 catalog.

Action: If LOCAL was used refresh@DB2SYSTABLES and@DB2SYSCOLUMNS. If not LOCAL ensureyou are pointing to the correct DB2subsystem.

TIBCO Object Service Broker Messages Without Identifiers

Page 127: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 113

DB2 Table name too long to generate astatic SQL handlerSource: Static SQL for DB2 Gateway

Explanation: The DB2 table name is too long tofit on a line in the generated static handlermodule. The maximum length of the tablename is 35

Action: None. Dynamic SQL must be used.

DB2 Typ "%" is incompatible withmetadata Syn "%"Source: Table Definer

Explanation: The indicated MetaStor syntax isincompatible with the indicated DB2 columntype.

Action: Change the MetaStor syntax to acompatible type. See the Accessing DB2 Datamanual for a list of compatible DB2 andMetaStor data types.

DBGCOM savedSource: Debugger Utility

Explanation: You have used <PF3> to save thecurrent DBGCOM. This provides feedback.

Action: No action required.

DBGCOM validatedSource: Debugger Utility

Explanation: You have used <PF4> to validatethe current DBGCOM. This providesfeedback.

Action: No action required.

DBID & FILE NO. have been extractedearlierSource: Adabas Extract

Explanation: This DBID and FILENOcombination has already been extracted andcannot be re-extracted from this option.

Action: Re-extract from the List of extracteddefinitions option.

DBID and FILE NO. must be enteredSource: Adabas Extract

Explanation: Values have not been supplied forrequired fields DBID and FILE NO.

Action: Specify DBID and FILE NO.

DDNAME allocation not allowed forparameterized "%" table "%"Source: TAM

Explanation: The table definition for theparameterized Export/Import table specifiesallocation using the DDNAME option. Thepresence of a DATA parameter andDDNAME allocation are mutually exclusive.

Action: Either remove the data parameter andallocate the fully qualified PDS membername on the DD statement or performallocation using the FILE option.

TIBCO Object Service Broker Messages Without Identifiers

Page 128: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

114 |

Deallocate failed "%" dataset; module"%"; R15 = %, error = %, info = %Source: Session Manager

Explanation: Deallocation of sort work file failed.The DDNAME, the module name, the returncode, and the dynamic allocation error andinfo codes are supplied for diagnosticpurposes.

Action: Call your system administrator to checkthe return code in Register 15 against theappropriate vendor's manual. Correct theproblem as required.

Debugger failedSource: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

Debugger TerminatedSource: Builtin Routines

Explanation: You have entered the EXIT primarycommand, or pressed <PF12>. This providesfeedback.

Action: No action required.

Debugger trace printedSource: Debugger Utility

Explanation: Provides feedback.

Action: No action required.

Decimal field length is too largeSource: Table Definer

Explanation: For a field with syntax P, thenumber of decimal places cannot be equal toor larger than twice the length of the IMSfield.

Action: Change the decimal length to be less thantwice the length of the IMS field.

Decimal must be 0 except for syntax PSource: Table Definer

Explanation: Only a MetaStor field with syntax P(packed decimal) can have a decimal valuelarger than 0.

Action: Enter 0 in the decimal field or change thesyntax to P.

Decimal must be 0 for type C syntax PSource: Table Definer

Explanation: You cannot have decimal places ifthe data type is Count.

Action: Enter 0 in the DEC field.

Default filter % may not be deletedSource: Secure Audit Log

Explanation: You attempted to delete thespecified default filters and this was notallowed. Default filters can be used by anyuser but they should not be deleted.

Action: No action is required.

TIBCO Object Service Broker Messages Without Identifiers

Page 129: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 115

Default filter % may not be modified -change name to saveSource: Secure Audit Log

Explanation: You attempted to modify thedefinition of the specified default filter andthis was not allowed. Default filters can beused by anyone but they cannot be modified.

Action: You can save the changes to the defaultfilter under a new filter name.

Default permissions for createdlibraries SAVEDSource: Security

Explanation: You saved default permissions forcreated libraries in the Specify DefaultPermissions function. Once the informationin the Specify Default Permissions screen issaved, the library defaults are applied for anylibraries subsequently created by the creatingmember.

Action: No action required.

Default permissions for created reportsSAVEDSource: Security

Explanation: You saved changes to defaultpermissions for created reports and you arenow viewing the Specify DefaultPermissions screen. Default reportpermissions are not committed unless theSpecify Default Permissions screen is saved.

Action: No action required.

Default permissions for created screensSAVEDSource: Security

Explanation: You saved changes to the defaultscreen permissions, and you are viewing theSpecify Default Permissions screen. Defaultscreen permissions are committed if theSpecify Default Permissions screen is saved,or ignored if the Specify Default Permissionsscreen is canceled.

Action: No action required.

Default permissions for created tablesSAVEDSource: Security

Explanation: You saved changes to the defaulttable permissions and you are viewing theSpecify Default Permissions screen. If yousave the Specify Default Permissions screen,changes to the default table permissions arecommitted; otherwise, the changes areignored.

Action: No action required.

Default permissions for objects createdby "%" SAVEDSource: Security

Explanation: You saved default permissionsspecifications.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 130: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

116 |

Default report % may not be deletedSource: Secure Audit Log

Explanation: Reports with a type of DEFAULTcan be used by anybody, but cannot bedeleted. If you do not want to see the reportin your list, use a selection.

Action: No action is required.

Default table % empty; see systemadministratorSource: Batch Control Card

Explanation: The default table containing the S-type card values is empty.

Action: Contact the System Administrator.

Default table % not found; see systemadministratorSource: Batch Control Card

Explanation: You are missing a TDS table thatcontains the default S-type card values.

Action: Contact the System Administrator.

Default value "%" is incompatible withtype % syntax % length %Source: Table Definer

Explanation: The indicated default value for thefield is incompatible with its type, syntax andlength.

Action: Change the default value for the field, orchange its type, syntax and length.

Defaults not allowed in definition ofderived field "%.%"Source: TAM

Explanation: Derived fields may not specifydefault values.

Action: Remove default values for all derivedfields in the definition of the subview table.

DEFINE can be used only from 1st levelof ObjectSet DefinerSource: Object Set Definer

Explanation: You attempted to define an objectfrom the Object Set Definer; however, you arealready in the process of defining an objectset from the Object Set Definer. You cannotgo more than one level from the originalobject set.

Action: Save your changes to the current objectset. Enter the Object Set Definer for the objectset from the workbench instead of the ObjectSet Definer.

Define input data table beforecontinuingSource: Batch Control Card

Explanation: The application has not received animport table, nor has an input file beendefined to it to provide a source of data.

Action: Define an input file on the current screen.

TIBCO Object Service Broker Messages Without Identifiers

Page 131: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 117

Defined table % is missing % entry %;No % loadedSource: Unload/Load

Explanation: The definition of the target table isincorrect. No occurrences are loaded.

Action: Correct the definition of the target tableand load the table again.

Definer FAILED: %Source: Object Set Definer

Explanation: The definer you invoked from theObject Set Definer failed for the reason given.

Action: Look up the message given for the failurefor more information.

Definition and data of table % will beboundSource: Table Editor

Explanation: Your request to bind the definitionand data of the indicated table wassuccessful. The next reference to the table inthis session, or the first reference to it in anyother session, causes its data and definitionto be bound for the duration of that session.

Action: No action required.

Definition and virtual layout for Screen"%" PRINTEDSource: Screen Definer

Explanation: The definition and layout for thenamed Screen has been printed at yourrequest.

Action: No action required.

DEFINITION ERROR - report table "%"defined twiceSource: Report Definer

Explanation: The same report table nameappears more than once in the list of reporttables and control breaks for this report.

Action: Specify each report table only oncewithin a report definition.

Definition error : %Source: Table Definer

Explanation: An internal error was detected inthe table definition.

Action: Contact TIBCO Support.

Definition error for report "%": "%"scope report function "%" notsupported with specified BY-FIELDsSource: Report Server

Explanation: Because of implementationrestrictions, this version of the Report Servercannot compute the report function inquestion.

Action: Contact TIBCO Support for moreinformation.

Definition for % updatedSource: Table Definer

Explanation: Information of the specified objecthas been updated.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 132: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

118 |

Definition for object set "%" PRINTEDSource: Object Set Definer

Explanation: The definition of the indicatedobject set was printed.

Action: No action required.

Definition is currently LOCKED; tryagainSource: Screen Definer

Explanation: You requested Define Screen fromthe workbench; however, the data store islocked, preventing the retrieval of thedefinition.

Action: Wait and try again.

Definition not saved - use % painterSource: Table Definer

Explanation: You cannot save a report tabledefinition in the Table Definer.

Action: Use the Report Painter to save thedefinition.

Definition of % % createdSource: Table Definer

Explanation: The specified object type/objecthas been successfully created.

Action: No action required.

Definition of % % does not existSource: Unload/Load

Explanation: Definition of the indicated objectwas not found; therefore, it was notunloaded.

Action: No action required.

Definition of % exists; No % loadedSource: Unload/Load

Explanation: The definition of a table, screen, orreport already exists in the system. LOADdoes not overwrite the existing definition.

Action: You can delete the existing object andload the new object if you want to replace theobject.

Definition of % savedSource: Table Definer

Explanation: The definition of the specifiedobject has been saved.

Action: No action required.

Definition of dynamically created table% is unusableSource: TAM

Explanation: The table definition you supplied tothe Dynamic Object Facility contains errors.

Action: Review the data you supplied to theDynamic Objects Facility and correct theerrors.

Definition of field "%" contains areference to itselfSource: Report Definer

Explanation: A derived field was defined whichrefers to itself in its definition.

Action: Remove the circular reference.

TIBCO Object Service Broker Messages Without Identifiers

Page 133: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 119

Definition of parameters for table "%"incorrect, sum of lengths of parameterstoo largeSource: Interpreter

Explanation: Internal error. The definition of thetable has been altered.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Use only the Table Definer to modify tabledefinitions.

Definition of report "%" deletedSource: Report Generator

Explanation: The definition of the indicatedreport, together with its correspondingGenerator tables, was deleted.

Action: No action required.

Definition of report "%" savedSource: Report Generator

Explanation: The definition of the indicatedreport, together with its correspondingGenerator tables, was saved.

Action: No action required.

Definition of report "%" too large -insufficient temporary memory to buildreport definitionSource: Report Server

Explanation: The definition of the report hasexceeded the Report Server storage limits forbuilding a report definition.

Action: Reduce the complexity of the report byreducing the number of report tables, bodyreport fields, break report fields, fixed reportfields, or literals.

Definition of screen % will be boundSource: Screen Definer

Explanation: Your request to bind the definitionof the indicated Screen was successful.Subsequent references to the Screen in thissession, or the first reference to the Screen inany other session, cause its definition (andthe definition of its constituent screen tables)to be bound.

Action: No action required.

Definition of screen % will not beboundSource: Screen Definer

Explanation: Your request to mark the indicatedScreen as not bound was successful.References to this Screen in subsequentsessions will not cause its definition (and thedefinition of its constituent screen tables) tobe bound.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 134: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

120 |

Definition of screen table "%" printedSource: Screen Definer

Explanation: In the Screen Table Painter, youissued a PRINT request and the screen tabledefinition was printed.

Action: No action required.

Definition of Static SQL for Table %Member % failedSource: Static SQL for DB2 Gateway

Explanation: You were attempting to build StaticSQL for the indicated table when an erroroccurred.

Action: View the message log for moreinformation about the problem. Fix theproblem, and try to generate or remove theStatic SQL again.

Definition of table "%" cannot beretrievedSource: Table Definer

Explanation: The definition of the indicated tablecannot be retrieved because of an internalerror.

Action: Contact TIBCO Support.

Definition of table "%" copiedSource: Table Definer

Explanation: The definition of the indicated tablewas copied to the table definition screen asyou requested in your COPY command.

Action: No action required.

Definition of table "%" deleted; rightsheld by %, requestor %Source: Table Definer

Explanation: The definition of the indicated tablewas deleted. Its promotion rights, however,are still held in the specified library by thespecified requestor.

Action: Notify the requestor that the tabledefinition has been deleted.

Definition of table "%" deletedSource: Table Definer

Explanation: The definition of the indicated tablewas deleted after you confirmed yourrequest to delete.

Action: No action required.

Definition of table "%" not foundSource: Table Definer

Explanation: The definition of the indicated tabledoes not exist.

Action: If your request requires the name of anexisting table, use the Object Manager to seea list of tables. See the Managing Datamanual for information about the ObjectManager.

Definition of table "%" printedSource: Table Definer

Explanation: A copy of the indicated tabledefinition was sent to the printer at yourrequest. You used the PRINT command orpressed <PF13>.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 135: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 121

Definition of table "%" saved; rightsheld by %, requestor %Source: Table Definer

Explanation: The definition of the indicated tablewas saved. Its promotion rights, however, arestill held in the indicated library by theindicated requestor.

Action: Notify the requestor of any changesmade.

Definition of table "%" savedSource: Table Definer

Explanation: The definition of the indicated tablewas saved at your request by pressing<PF3>.

Action: No action required.

Definition of table % cannot be viewedSource: Table Definer

Explanation: The viewing of the definition of thistable is not allowed. Most likely this is antable that is used internally for specialpurposes.

Action: None

Definition of table % will be boundSource: Table Editor

Explanation: Your request to bind the definitionof the indicated table was successful. Thenext reference to the table in this session, andthe first reference to it in any other session,causes its definition to be bound.

Action: No action required.

Definition of this special table can notbe unloadedSource: Unload/Load

Explanation: The definition of a system tablesuch as FIELDS, EVENTRULES,ORDERING, PARMS, or TABLES cannot beexported.

Action: No action required.

Definition requested not found in %Source: Table Definer

Explanation: The indicated SYSTABLES isempty.

Action: Specify another serverid.

Definition too large to process for tableSource: 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 16K. The DataObject Broker will have to be shut down andrestarted with the new parameter.

Definitions of '%' type '%' not printedSource: Print Definition

Explanation: The object is not printed.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 136: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

122 |

Definitions of '%' type '%' printedSource: Print Definition

Explanation: You are trying to print an object andthe object is printed.

Action: No action required.

DEFN rights requested for invalidobject: "%" of type "%"Source: Manage Promotion Rights

Explanation: You are trying to OBTAIN all rights,RELEASE all rights, or TRANSFER all rightson an object. However, the object or itschildren may have an invalid object type, ormay not even exist at all. Therefore theoperation fails.

Action: Check whether the object and its childrenexist and whether they have an invalid type.

Delete access to % %( % ) by % deniedSource: Audit Log Message

Explanation: DELETE access to this object wasdenied. If the object is a parameterized table,the value of the first parameter for this tableinstance is indicated.

Action: The user can ask someone who hasCONTROL access to the object to provideDELETE access.

Delete access to TABLE %( % ) by %Source: Audit Log Message

Explanation: The user has deleted data from thegiven table with the specified parameter.

Action: No action required.

Delete batch queue failed: %Source: Batch Submission Tool

Explanation: An error was encountered duringthe deletion of a batch queue definition.

Action: Contact TIBCO Support.

Delete batch requestSource: Batch Submission Tool

Explanation: You made a request to delete abatch request, and now you are required toconfirm the request.

Action: Press <PF22> to delete the batch request,or press any other key to cancel the deletion.

Delete canceledSource: Promotion

Explanation: You started, but did not confirm,the delete of the logs for a specific activity ona change request.

Action: No action required.

DELETE canceledSource: Tool for CA IDMS Data

Explanation: <PF22> to delete was pressed, butafter getting the confirmation message todelete a subschema definition, some otherkey besides <PF22> was pressed.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 137: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 123

Delete definition of % % by % deniedSource: Audit Log Message

Explanation: The user attempted to delete anobject, but only the owner of the object, theowner's Security Administrator, or theSystem Administrator can delete an object.

Action: The user can contact one of the aboveauthorized people to delete the object.

Delete definition of GROUP % by %Source: Audit Log Message

Explanation: The specified group definition wasdeleted.

Action: No action required.

Delete definition of LIBRARY % by %Source: Audit Log Message

Explanation: The specified library object wasdeleted.

Action: No action required.

Delete definition of REPORT % by %Source: Audit Log Message

Explanation: The specified report object wasdeleted.

Action: No action required.

Delete definition of SCREEN % by %Source: Audit Log Message

Explanation: The specified screen object wasdeleted.

Action: No action required.

Delete definition of TABLE % by %Source: Audit Log Message

Explanation: The specified table object wasdeleted by the indicated user.

Action: No action required.

Delete definition of USERID % by %Source: Audit Log Message

Explanation: The indicated Object ServiceBrokeruserid was removed from the system.

Action: No action required.

DELETE failed: table "%" notpositioned at any rowSource: Screen Server

Explanation: The rule attempted to delete anoccurrence without specifying theoccurrence to be deleted.

Action: Perform a GET or a FORALL to specifythe occurrence to be deleted.

Delete FailedSource: Delete Definition

Explanation: You are trying to delete a table butthe operation fails.

Action: Check and see whether all entered valuesare valid. Also, check whether the specifiedtable is deletable. If everything is correct butthe operation still fails, contact TIBCOSupport with the log and a description of theactions performed before the message wasdisplayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 138: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

124 |

DELETE for report table used by otherreportsSource: Report Definer

Explanation: The report table that you want todelete is referenced in other reports.

Action: Check that the other reports are notneeded or change the other reports toreference another report table.

Delete of rule "%" has been cancelledSource: Rule Editor

Explanation: The DELETE command made tothe named rule has been canceled.

Action: No action is required.

Delete request cancelledSource: Adabas Extract

Explanation: Delete of extracted data wasaborted by user request.

Action: No action required.

DELETE request CANCELLEDSource: Object Set Definer

Explanation: You have canceled your request todelete the object set.

Action: No action required.

DELETE request for library "%"cancelledSource: Define Library

Explanation: You made a request to delete thelibrary, but you did not confirm the requestas required by the system. As a result, thedeletion request was canceled.

Action: No action required.

Delete selected for % % %Source: Promotion

Explanation: You have selected the specifiedobject for deletion. When the change requestis promoted, this object will be deleted. If youdo not wish this to happen, use the C linecommand to remove it from the request.

Action: No action required.

Delete table with dataSource: Table Definer

Explanation: Deleting the specified tabledefinition will cause its data to be deleted aswell. You must confirm this request bypressing the indicated key.

Action: Confirm the deletion by pressing theindicated key, or press any other function keyto cancel the request.

Deleted %Source: General

Explanation: You pressed <PF22> to confirm thatyou wanted to delete the specified object.

Action: No action required.

Deleted %Source: Promotion

Explanation: The specified number of objectshave been deleted from the target system.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 139: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 125

Deleted data for % tables or tableinstancesSource: Promotion

Explanation: The data of the specified number oftables or table instances have been deletedfrom the target system.

Action: No action required.

DELETED definition of EMPTY library"%"Source: Define Library

Explanation: You confirmed a deletion requestfor an empty library, and the library wasDELETED.

Action: No action required.

DELETED rules and library definitionfor "%"Source: Define Library

Explanation: You confirmed your request todelete a library containing rules.

Action: No action required.

DELETING defn of EMPTY library "%"Source: Define Library

Explanation: You requested the deletion of anempty library and confirmation is now beingsolicited.

Action: You can press the specified key toconfirm the request and have the librarydeleted, or press any other function key(including <Enter>) to have the requestaborted.

Deleting occurrence "%"; press <%> ortype 'confirm' to confirmSource: Table Editor

Explanation: You are about to delete thisoccurrence. Please confirm or cancel yourrequest.

Action: If you wish to delete the occurrence,press the specified key or type confirm on theprimary command line. Press another key ifyou do not wish to delete the occurrence.

DELETING OLD VERSIONS OFOBJECTSSource: Promotion

Explanation: The Promotion tool deletes the oldobjects before loading the new ones.

Action: No action required.

DELETING rules & library defn for "%"Source: Define Library

Explanation: You made a request to DELETE alibrary with rules, and now you are beingasked to confirm your request.

Action: You can press the indicated key to havethe deletion carried out, or press any otherkey to have the deletion aborted.

Deletion cancelledSource: General

Explanation: You canceled your request to deleteby pressing a key other than <PF22>.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 140: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

126 |

Deletion of % % requested, but is usedby % %Source: Promotion

Explanation: The specified screen table or reporttable selected for deletion is used by thespecified Screen or report that you selectedfor promotion.

Action: Do one of the following:

• Do not delete the specified screen table orreport table.

• Do not promote the specified screen orreport.

Denied "%" access to % "%"Source: TAM

Explanation: The specified object cannot beaccessed by a user at that security level.

Action: Contact the Security Administrator.

Derived indicator must be "S"ource or"D"erivedSource: Table Definer

Explanation: The derived indicator is invalid.You must enter either S (the entry in theSOURCE NAME field is a field of the sourcetable), or D (the entry in the SOURCE NAMEfield is a functional rule).

Action: Change the derived indicator to S or D.

Derived report field "%" of report table"%" in error; "%" is not the name of areport fieldSource: Report Server

Explanation: In a call to $RPTOVERLAP, theindicated report field is not a field of theindicated report table.

Action: Use the Report Definer to determine thecorrect report field and report table names.Correct the call to $RPTOVERLAP by usingthe Rule Editor.

Descendents in LIST1 are DIFFERENTthan counterparts in LIST2Source: Definition Differences

Explanation: The objects in the lists are different.

Action: No action required.

Description of promotion request savedSource: Promotion

Explanation: The change request was in apending state before you changed thedescription. The description has beenchanged.

Action: No action required. The change request isstill in a pending state.

Description updatedSource: Adabas Extract

Explanation: The description for the particularDBID and File No has been savedsuccessfully.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 141: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 127

Designated line cannot be manipulateddue to existing dataSource: Table Definer

Explanation: You tried to use a line command inthe Table Definer, but it cannot work becausethe table contains data.

Action: Remove the line command.

Destination object requires a name,library, or environmentSource: Copy Definition

Explanation: Since the copy is local (nodestination location is specified), thedestination object should have at least a newname, library, or environment depending onthe object type.

Action: Depending on the object type, entereither a new name, library, or environment.

Did NOT Copy %; source & destinationobject are the sameSource: Copy Defn/Data

Explanation: You have specified a copy such thatthe source and destination are the same.Therefore there is no need to copy.

Action: No action.

Different number of fields in the twolistsSource: Definition Differences

Explanation: The two arguments, FIELD1 andFIELD2 have different numbers of fields.

Action: Correct the lists of fields to be compared.

Dimensions of a report page cannot bechanged while INSERTing occurrencesinto the same reportSource: Report Server

Explanation: The page length and width of areport cannot be modified while the report isbeing printed.

Action: In the rule application, call $RPTPARMSbefore the first INSERT into the report.

Disclaim FAILED: SecAdmin % haslower CLEARANCE than user %Source: Security

Explanation: If a Security Administrator tries todisclaim a user by referring the user toanother Security Administrator who has alower clearance than that user, the disclaimfails.

Action: Disclaim the user by referring the user toa Security Administrator who has the sameor higher clearance than the user.

DISCLAIM failed: selected SecAdminsame as current SecAdminSource: Security

Explanation: The Security Administratorrequested to DISCLAIM a userid, but thenew Security Administrator specified is thecurrent Security Administrator.

Action: If a userid is to be disclaimed, chooseanother Security Administrator during thedisclaim function.

TIBCO Object Service Broker Messages Without Identifiers

Page 142: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

128 |

DISPLAY & TRANSFERCALL rule "%"does not have a handler forVALIDATEFAIL on screen "%"Source: Interpreter

Explanation: The validation exit key was pressedon a screen displayed by DISPLAY ANDTRANSFERCALL. A VALIDATEFAILexception was raised, but an exceptionhandler does not exist in the DISPLAY ANDTRANSFERCALL rule.

Action: Use the Rule Editor to change the ruleinvoked by DISPLAY ANDTRANSFERCALL. Add an exception handlerfor VALIDATEFAIL to process the entry ofthe validation exit key.

Display access of SCREEN % by %deniedSource: Audit Log Message

Explanation: DISPLAY access to this screenobject was denied.

Action: The user can ask someone who hasCONTROL access to the screen to provideDISPLAY access.

DISPLAY FROM TOP OF DATASource: S6BTLADM - COMMON MESSAGES

Explanation: The data currently displayed on thescreen is the top of the data.

Action: No action.

Display mask "%" is not a valid datemaskSource: Screen and Report Painters

Explanation: The specified display mask is not avalid date display mask.

Action: Reenter a valid display mask. Refer to thedocumentation for valid values.

Display mask error detected for reportfield "%" of report table "%"Source: Report Server

Explanation: The display mask of a reportfunction contains a syntax error.

Action: Use the Report Definer to change thedisplay mask to a valid syntax.

Display masks are only valid for fieldswith syntax "B" or "P"Source: Field Dictionary

Explanation: Syntax of the field with the displaymask is invalid.

Action: Specify Binary (B) or Packed (P) forsyntax of the field with the display mask.

Display masks are only valid for fieldswith syntax "B" or "P"Source: Screen and Report Painters

Explanation: You can specify display masks forfields with syntax Binary or Packed only.

Action: Delete the display mask for this field.

TIBCO Object Service Broker Messages Without Identifiers

Page 143: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 129

DISPLAY not allowed under batchSource: Builtin Routines

Explanation: The Object Service Brokeroperation DISPLAY is not allowed underbatch since there is no terminal associatedwith the Object Service Broker session. Aterminal is required for the DISPLAYoperation.

Action: Either run the rule as an interactiveObject Service Broker user, or else change therule to not use the DISPLAY operation.

Display of report field "%" for reporttable "%" failed with a conversion errorSource: Report Server

Explanation: The conversion of a numeric reportfield to a string failed during the building ofa report page.

Action: This is an internal Report Server error;contact TIBCO Support.

DISPLAY operation not allowed forthis environmentSource: Screen Server

Explanation: The Object Service Broker DISPLAYoperation is not allowed under thisenvironment since there is no terminalassociated with the session. A terminal isrequired for the DISPLAY operation.Examples of environments where there is noterminal are batch, CLI, SDK (C/C++) andSDK (Java).

Action: Run the rule as an interactive ObjectService Broker user or change the rule to notuse the DISPLAY operation.

DISPLAYED RESOURCE DETAILENTRY HAS BEENUPDATED/INSERTEDSUCCESSFULLYSource: S6BTLADM-Resource Management

Explanation: The previous update or insertrequest has completed.

Action: No action required.

Disposition of % % in change#% ofnode % is inconsistentSource: Promotion

Explanation: The disposition of the named objectin the specified change request isinconsistent with that in the other selectedchange requests. You have missed someother changes in the consolidation.

Action: Do not include the specified changerequest, or include other changes such thatthe disposition of the named object in thespecified change is consistent with otherselect changes.

Disposition of % has been changedfrom % to %Source: Promotion

Explanation: The disposition of the specifiedobject has been changed to match that on thetarget system. Note that only the changerequest definition loaded on the targetsystem has been changed, the one in theextract file and the one in the source systemwill remain intact.

Action: You may now proceed to apply thechange to the target system.

TIBCO Object Service Broker Messages Without Identifiers

Page 144: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

130 |

Disposition refreshedSource: Promotion

Explanation: The dispositions of the objects inthe change request should match the targetsystem now.

Action: You may proceed to apply the change tothe target system.

Distribution point "%" does not exist insource tableSource: Table Definer

Explanation: The distribution point youspecified does not exist in the source table.

Action: Specify a field of the source table as thedistribution point.

Distribution point "%" must besyntax:% length:% decimal:%Source: Table Definer

Explanation: The indicated field, which youspecified as the distribution point, hasdifferent attributes from the source table.

Action: Modify the attributes accordingly.

Do not include % in the join more thanonceSource: Print Table

Explanation: You added a table that is already inthe join.

Action: You cannot add a table more than once.You may have to use <PF22> to delete thesecond instance.

Documentation is missing for thisobjectSource: Global Cross Ref. Search

Explanation: The SEARCH tool cannot retrievethe keywords or description of an object.

Action: No action required.

Documentation unavailable %Source: Rule Editor

Explanation: You pressed <PF2> in the windowfor documentation, but no documentation isavailable.

Action: No action required.

Due to locking, cannot % at this time;try againSource: Screen Definer

Explanation:YouaretryingtoDISPLAY,SAVEorPRINT a screen definition, but the data storeis LOCKED.

Action: Try the function again later.

Due to LOCKING cannot completelibrary DELETION; try againSource: Define Library

Explanation: You requested and confirmed thedeletion of a library, but data lockingprevents the deletion from occurring atrequest time.

Action: You can do one of the following:

• Wait and try to delete again, withoutleaving the current screen

• Cancel and try again later.

TIBCO Object Service Broker Messages Without Identifiers

Page 145: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 131

DUMP ITEM NUMBER MUST BESPECIFIEDSource: S6BTLADM - DIAGNOSTIC DUMP

Explanation: You must specify which dump youwish to initiate by entering the numberassociated with it.

Action: Specify a dump number and try yourrequest again.

Dump of active tablesSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log. It signals the beginning of alist of the tables accessed when the erroroccurred.

Action: Study the Object Service BrokerInformation Log.

Dump of local variablesSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log. It signals the beginning of alist of local variables used in the currenttransaction.

Action: Study the Object Service BrokerInformation Log.

Duplicate CA-Datacom Field Name notallowedSource: CA Datacom Table Definer

Explanation: You specified two of the ObjectService Broker fields to use the same CA-Datacom field.

Action: You can only have one field referring to agiven CA-Datacom field. Remove one of thereferences to the CA-Datacom field.

Duplicate field names in current oranother segmentSource: Table Definer

Explanation: You cannot have duplicateMetaStor field names in one table.

Action: Find the duplicate names and make theirnames unique.

Duplicate name in this or anothersegmentSource: Table Definer

Explanation: Two identical MetaStor field nameswere specified in the current segment oranother segment. Duplicate names are notallowed in a MetaStor defined table.

Action: Change the duplicate field names so thateach one is unique.

Duplicate NAME is not allowedSource: CA Datacom Table Definer

Explanation: You have specified a duplicatename for the field.

Action: Each field must have a unique name;remove one duplicate.

TIBCO Object Service Broker Messages Without Identifiers

Page 146: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

132 |

Duplicate NAME is not allowedSource: General Table Definer

Explanation: You have specified duplicate namesfor some part of the core information aboutthe MetaStor table you are defining.

Action: You must specify unique names for eachentry in the part of the core information.Remove one of the duplicates, or rename it.

Duplicate number is not allowedSource: CA Datacom Table Definer

Explanation: You have specified a duplicatenumber for one of the fields.

Action: You must give each field a uniquenumber. The numbers must be consecutivefrom 1 to the number of fields, with theprimary keys coming first.

Duplicate number is not allowedSource: General Table Definer

Explanation: You have specified a duplicatenumber, where duplicate numbering is notallowed.

Action: Respecify the duplicate number to be aunique number.

Duplicate parameter/field name "%"not allowedSource: Table Definer

Explanation: Each parameter or field name mustbe unique within a table definition.

Action: Remove the duplicate parameter or fieldname.

Duplicate specification detected;remove or change entrySource: Security

Explanation: In the screen where the tablepermissions for an object set are specified,you changed a table name in the list of tablesso that the entry duplicates the tablespecification for another entry in the list.Since the entries are both the same, one isconsidered invalid.

Action: Change the table name so that the entryis no longer a duplicate of another entry, orremove the duplicate entry by nullifying orblanking out the table name in that entry.

During attempt to load, % Error(s)occurredSource: Unload/Load

Explanation: The specified number of errorswere encountered during loading. Thismessage appears in the user log file.

Action: No action required.

During load, % Error(s) occurred; Readthe reportSource: Unload/Load

Explanation: An error was encountered duringthe loading process.

Action: Press <PF2> to view the error messages.You can find more information about theerror messages in this manual.

TIBCO Object Service Broker Messages Without Identifiers

Page 147: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 133

Dynamic ; of ";" failed, Return Code = #,error code = ;, info = ;Source: Report Server

Explanation: An error occurred during allocationor de-allocation of a report server work file.Additional information about the error isincluded in the message text.

Action: Using the "Return Code", "error code",and "info" values, refer to the appropriateoperating system documentation or give theinformation to your systems personnel forinterpretation.

DYNAMIC UNALLOCATE FAILURE:RC = ____, ERROR = ____,INFORMATION =Source: S6BTLADM - COMMON MESSAGES

Explanation: While attempting to release theallocation of the parameter card data set anerror was detected. The message will presentthe return code, error code and anyadditional information codes provided bythe system.

Action: Refer to the dynamicallocation/unallocation processes (SVC 99)in the manuals for the operating system todetermine the most appropriate course ofaction.

Dynamically created table cannot be oftype %Source: TAM

Explanation: Table types available in theDynamic Object Facility are:

• CLC

• EXP

• IMP

• MAP

• PRM

• SES

• SUB

• TEM

Action: Choose a supported type.

TIBCO Object Service Broker Messages Without Identifiers

Page 148: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

134 |

Messages beginning with: E

Each screen table must have a differentnameSource: Menu Definer

Explanation: You have supplied screen tablenames for the Session Menu you aredefining; however, the name is not unique.Each of these names will be used for adifferent screen table of the screen for thismenu.

Action: You must provide unique names for eachof the screen tables.

Either "Defn" and/or "Data" must be YSource: Object Set Definer

Explanation: A table must have either its DEFNand/or DATA set to Y.

Action: Set the table's DEFN and/or DATA to Y.

Either one group or a number of groupfields may be selectedSource: Adabas Definer

Explanation: You selected both group and groupfields. This selection is invalid.

Action: Select either a group or a collection ofgroup fields.

EITHER THE POOL NAME WAS NOTSUPPLIED OR IT IS INVALIDSource: S6BTLADM - MEMORY DISPLAY

Explanation: You have requested processing of apool. You have failed to enter a valid poolname for the processing to continue.

Action: Correct the pool name and retry yourrequest.

Empty selectionSource: Object Manager

Explanation: A SELECT command did not findany occurrences that satisfied it.

Action: No action required.

EMS function ";" failed: Reason code is#Source: POSIX ON support for EMS

Explanation: The EMS function failed with thereason code listed.

Action: Keep any logs and dumps produced forthis failure and report this error to TIBCOSupport.

EMS function ";" not supportedSource: POSIX ON support for EMS

Explanation: The routine name supplied is notsupported by either the S6BCALL or theS6BFUNCTION shareable tool.

Action: Correct the function name.

TIBCO Object Service Broker Messages Without Identifiers

Page 149: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 135

EMS function name conversion failedSource: POSIX ON support for EMS

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.

EMS initialization failed: Return code#, Reason code #Source: POSIX ON support for EMS

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.

EMS is not supportedSource: POSIX ON support for EMS

Explanation: TIBCO EMS is not supported in thisExecution Environment.

Action: Modify the EMS API parametersTASKPOSIXNUM andTHREADPOSIXNUM or the EMS APIparameter EMSWIRECODEPAGE asrequired.

EMS prior initialization attempt failed:Return code #, Reason code #Source: POSIX ON support for EMS

Explanation: See the explanation for message:EMS initialization failed: Return code #,Reason code #

Action: See the action for message: EMSinitialization failed: Return code #, Reasoncode #

Encountered "%" when expecting "."Source: Batch Submission Tool

Explanation: The field reference in@SCHEDULEMODEL is incorrect. It shouldbe of the form T.F where T is the table nameand F is the field name. This check isreporting an incorrect token for ".".

Action: Specify "." between the table name andfield name for the field reference.

Encountered "%" when expecting aconstant, identifier or "("Source: Rule Editor

Explanation: There is a syntax error in your rule.

The token was encountered when a constantvalue, an identifier, or a left parenthesis wasexpected.

Action: Check the Processing manual for thecorrect syntax, or cancel the changes.

TIBCO Object Service Broker Messages Without Identifiers

Page 150: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

136 |

Encountered "%" when expecting afield nameSource: Batch Submission Tool

Explanation: The field reference in@SCHEDULEMODEL is incorrect. It shouldbe of the form T.F where T is the table nameand F is the field name. This check isreporting that the field name is incorrect.

Action: Specify the correct field name for thefield reference.

Encountered "%" when expecting afield nameSource: Rule Editor

Explanation: You did not provide a valid fieldname in an indirect reference of the form:table.field

Action: Check the Processing manual for thecorrect syntax and valid field names.

Encountered "%" when expecting afield referenceSource: Rule Editor

Explanation: You did not provide a valid fieldreference in one of the following places:

• In the WHERE clause of a GET statement

• In the WHERE clause of a FORALLstatement

• In an ORDERED clause.

Possibly, you did not provide a validparameter reference in one of the followingplaces:

• In the WHERE clause of an INSERTstatement

• In the WHERE clause of a REPLACEstatement.

Action: Check the Processing manual for thecorrect syntax and valid field or parameterreferences.

Encountered "%" when expecting alocal variable nameSource: Rule Editor

Explanation: You did not provide a valid localvariable name after the keyword LOCAL.

Action: Check the Processing manual for thecorrect syntax and valid local variablenames.

Encountered "%" when expecting aparameter nameSource: Rule Editor

Explanation: You did not provide a validparameter name in brackets after the rulename in the rule header.

Action: Check the Processing manual for thecorrect syntax and valid parameter names.

Encountered "%" when expecting arelational operatorSource: Rule Editor

Explanation: There is a syntax error in your rule.

The token was encountered when:

• one of the following relational operatorswas expected =, <, <=, >, >=, ^= (in thecondition section of a rule)

• one of the relational operators or LIKE wasexpected (in a WHERE clause).

Action: Check the Processing manual for thecorrect syntax, or cancel the changes.

TIBCO Object Service Broker Messages Without Identifiers

Page 151: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 137

Encountered "%" when expecting a rulenameSource: Rule Editor

Explanation: You did not provide a valid rulename in one of the following places:

• In the rule header

• In a rule invocation statement (CALL,EXECUTE, TRANSFERCALL,SCHEDULE).

Action: Check the Processing manual for thecorrect syntax and valid rule names.

Encountered "%" when expecting atable nameSource: Batch Submission Tool

Explanation: The field reference in@SCHEDULEMODEL is incorrect. It shouldbe of the form T.F where T is the table nameand F is the field name. This check isreporting an incorrect table name.

Action: Change the table name in the fieldreference.

Encountered "%" when expecting atable referenceSource: Rule Editor

Explanation: You did not provide a valid tablereference in one of the following statements:

• FORALL

• GET

• REPLACE

• INSERT

• DELETE

• DISPLAY.

Action: Check the Processing manual for thecorrect syntax and valid table references.

Encountered "%" when expecting anempty stringSource: Batch Submission Tool

Explanation: The field reference in@SCHEDULEMODEL is incorrect. It shouldbe of the form T.F where T is the table nameand F is the field name. This check has foundextra tokens after T.F.

Action: Remove the extra token in the fieldreference.

Encountered "%" when expecting anexception nameSource: Rule Editor

Explanation: You did not provide a validexception name in one of the followingplaces:

• In an UNTIL clause

• After the SIGNAL keyword

• In an ON statement.

Action: Check the Processing manual for thecorrect syntax and valid exception names.

Encountered "%" when expecting anidentifierSource: Rule Editor

Explanation: There is a syntax error in your rule.The token was encountered when anidentifier was expected.

Action: Check the Processing manual for theproper syntax, or cancel the changes.

TIBCO Object Service Broker Messages Without Identifiers

Page 152: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

138 |

End of call listSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log. Itsignals the end of the list of the last 16 rulescalled before the error occurred.

Action: Study the Information Log.

End of file reached by "%"Source: Builtin Routines

Explanation: You called the @READDSN tool,but the last record has already been read.

Action: Supply a handler for exceptionENDFILE.

End of selection - % rows returnedSource: Secure Audit Log

Explanation: You scrolled to the bottom of theselection list and were informed of the totalnumber of rows in your selection.

Action: No action required.

End of table dumpSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log. Itsignals the end of the list of tables accessedwhen the error occurred.

Action: Study the Information Log.

End of tracebackSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log. Itsignals the end of the list of rules calledbefore the error occurred.

Action: Study the Information Log.

END statement ignored due to error inFORALLSource: HLIPREPROCESSOR

Explanation: An error has caused a FORALLstatement to be ignored; therefore, there aretoo many END statements.

Action: Usually, the FORALL statement needs tobe corrected.

Enter/change FIELD DEFINITION for"%"Source: Report Definer

Explanation: An EXPAND FLD operation wasrequested, and the expanded field definitionscreen is currently displayed.

Action: If desired, enter or change the expandedfield definition for the displayed field andpress <PF3>; otherwise, press <PF10>.

Enter "S" for system, "I" for installation,or "L" for localSource: Batch Submission Tool

Explanation: You specified an invalid searchpath code on the batch submission screen.

Action: Valid search path codes are:

• S - System

• I - Installation

TIBCO Object Service Broker Messages Without Identifiers

Page 153: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 139

• L - Local.

Enter a FIELD name to perform reportfunction ONSource: Report Definer

Explanation: If a report function has beenselected as the derived field definition value,the OF FIELD field must be filled in.

Action: Enter the name of the field or fields onwhich to perform the report function.Consult the Object Service Brokerdocumentation for further information.

Enter a valid input valueSource: Table Definer

Explanation: In order to describe result setcursors the stored procedure must return aresult set

Action: Provide valid values

Enter at least 1 field or Only entercompleted location parm for minimaldefnSource: Table Definer

Explanation: The current type of table requiresthat you specify at least one field unless thisis a minimal definition.

Action: Specify a field for the table, or if this is aminimal definition, define only the Locationparameter including the name of the remotenode. See the Managing Data manual formore information about defining fields andminimal definitions.

Enter DB2 creator or press <PF4> forselectionSource: Table Definer

Explanation: The DB2 CREATOR field must befilled in.

Action: Enter the DB2 creator of a DB2 sourcetable or press <PF4> for a list of tables in theDB2 database.

Enter DB2 table name or press <PF4>for selectionSource: Table Definer

Explanation: The DB2 TABLE field must be filledin to associate this MetaStor DB2 tabledefinition with a DB2 table.

Action: Enter the DB2 source table or press<PF4> for a list of tables in the DB2 database.If the DB2 CREATOR field is filled in, <PF4>will show you a list of the tables created bythe specified DB2 Creator.

Enter field of "%" to which "%" of "%" isto be relatedSource: Report Generator

Explanation: The field name of the table that youwant to relate to is missing.

Action: Specify a field name of the indicatedtable.

TIBCO Object Service Broker Messages Without Identifiers

Page 154: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

140 |

Enter M204 file/group name or press<PF4> for selectionSource: Table Definer

Explanation: The first step in defining a 204 tableis to specify the Model 204 file or groupname.

Action: Enter the file or group name, or press<PF4> to select one.

Enter name of a menu or tableSource: Menu Definer

Explanation: You have chosen to haveprompting for this item.

Action: If a menu manager is named in thecolumn entitled MENU_MANAGER orPROMPT RULE, enter the name of a menu. Ifan object manager is named in that column,enter a table name.

Enter name of the rule to be saved inlibrary %Source: Report Generator

Explanation: You specified that you wanted tosave the rule that generates this report, butyou neglected to provide a name for the rule.

Action: Enter a rule name or reset the SAVERULE flag to N.

Enter required field at the cursorpositionSource: Definition Differences

Explanation: You have forgotten to insert someimportant information when comparing twoobjects.

Action: Insert the missing information at theposition located by the cursor.

Enter table to which "%" of "%" is to berelatedSource: Report Generator

Explanation: You specified the indicated field orparameter of the indicated table, but did notrelate it to any other table.

Action: Enter the name of a preceding table andfield or parameter to relate to.

ENTERKEY requested before Screen"%" displayedSource: Screen Server

Explanation: A rule has called the ENTERKEYtool before the screen specified has beendisplayed.

Action: Display the screen before calling theENTERKEY tool.

Entries must be positioned either to theright (R) or left (L)Source: Menu Definer

Explanation: The menu manager can present theinput areas to the right or left of the title.

Action: Indicate R (right) or L (left).

TIBCO Object Service Broker Messages Without Identifiers

Page 155: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 141

Entry in @SYSTEM_TABLES notinsertedSource: Promotion

Explanation: This message is always precededby message 10 which says that a report tabledoes not have an entry in TABLES. As aresult, no entry will be inserted to@SYSTEM_TABLES. This implies that thereport table will not be recognized as anobject on the target system.

Action: Redefine the report table and promote itin another change request.

Entry level rule to execute % cannothave argumentsSource: Promotion

Explanation: The selected entry-level rule toexecute cannot require any arguments to bepassed to it.

Action: Fix the rule.

Entry rule flag set to % for %Source: Promotion

Explanation: You have toggled the value of theENT field for the specified rule. This fieldindicates whether a rule is an entry rule ornot. If you wish to change the value, use theT line command to toggle it back.

Action: No action required.

Entry too long; % characters allowedSource: Session Manager

Explanation: You typed an entry that exceeds thelength accepted by the field.

Action: Correct the entry.

Environment ID % not allowed to purgeaudit logSource: Builtin Routines

Explanation: The user ID that you used to log onto the external environment is not allowed topurge the Object Service Broker audit logbecause it does not appear in the secparmdata set with a Y in the required column.

Action: Contact your system administrator todetermine if your environment logon user IDshould be allowed to purge the ObjectService Broker audit log.

Environment ID % not allowed tospecify file for audit logSource: Builtin Routines

Explanation: The ID that you used to log on tothe external environment was disallowed tospecify the archive file for the backup auditlog data.

Action: Contact your system administrator todetermine if your environment ID should beallowed to specify the archive file for theObject Service Broker audit log data.

Environment stack overflowSource: Character-based Text Editor

Explanation: An internal problem in Script.

Action: Contact TIBCO Support.

Error(s) found in rule statementsSource: HLIPREPROCESSOR

Explanation: Errors were found in Object ServiceBroker statements.

Action: Correct or remove the erroneousstatements.

TIBCO Object Service Broker Messages Without Identifiers

Page 156: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

142 |

ERROR: *** No entry rule to execute ***Source: Promotion

Explanation: If rules are to be executed at thetime of promotion, one rule must be an entry-level rule.

Action: Contact the application developer toresolve the problem.

ERROR: *** No PRM table for % ***Source: Promotion

Explanation: Before all occurrences of aparameterized table can be promoted, a PRMtable must exist.

Action: Create a parameter table for the specifiedtable.

ERROR: *** Object "%" to be backed updoes not exist ***Source: Promotion

Explanation: The Promotion system tried to takea backup of the specified object beforepromoting it, but the object does not exist.

Action: Find out what happened to the object,e.g., who deleted it.

ERROR: *** Selected object "%" doesnot exist ***Source: Promotion

Explanation: Cannot find the object specifiedwhich was selected for promotion.

Action: Make sure that you have the correctname for the object.

ERROR: *** Table % used by promotionsystem; CANNOT apply ***Source: Promotion

Explanation: The specified table is used by thepromotion system and must be appliedspecially. Customers should not see thismessage because they should not bemodifying Object Service Broker systemtables.

Action: Contact TIBCO Support.

ERROR: *** Read the Message Log ***Source: Promotion

Explanation: Detected an error or errors whenupdating @SYSTEM_PARMSETS.

Action: Read the message log to determinewhich table causes the failure and actaccordingly.

Error: A parameter may be too longSource: Character-based Text Editor

Explanation: An overflow occurred during theinitialization of TED. A value that waspassed in for a parameter is too long for thetable definition.

Action: Correct the parameter.

Error # was detected by system;meaning:%Source: Report Server

Explanation: The operating system used on theportable platform returned a value otherthan zero for an internal function; meaningshows the text that corresponds to this valueas it was defined by the vendor of the system.

Common errors are

TIBCO Object Service Broker Messages Without Identifiers

Page 157: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 143

• Security restrictions

• Lack of disk space

• Incorrect system variable settings

Action: Inform your local systems supportperson for corrective action.

Error % VSAM % "%" for table "%"Source: TAM

Explanation: This is a general VSAM access error.The variables, from left to right, are asfollows:

1. The resulting error

2. Either "file" or "DDNAME"

3. The name of the file or the DDNAME

4. The name of the table

Action: Contact TIBCO Support.

ERROR *** Execution of rule to execute% failed ***Source: Promotion

Explanation: The rule to execute specified withthe promotion failed to execute. A dumpfollows in the log.

Action: Correct and execute the rule separately,or back out the change and resubmit thepromotion with the corrected rule.

Error - Mismatched quotes detectedSource: Object Manager

Explanation: You have entered a primarycommand which contains unmatchedquotes.

Action: Correct the quotes in your primarycommand.

ERROR - Overlap or fit problem forfields and/or headingsSource: Report Definer

Explanation: The definition of two or more fieldsin the definition area or the Paint Screenoverlap.

Action: All changes are erased. Redo anyrequired changes, and ensure that thedefinitions do not overlap.

Error - Probably bad selection. LIKE<number> not supportedSource: Object Manager

Explanation: The specified selection contains anerror. A common error is to use LIKE with anumber.

Action: Correct the selection specification.

Error - unable to prompt for this lineSource: Session Manager

Explanation: This line specifies that a rule is to becalled. Prompting is only supported for rulesthat are executed.

Action: Remove the prompting or change theinvocation from call to execute.

ERROR archiving Audit Log; %Source: Secure Audit Log

Explanation: You attempted to purge the auditlog contents but you were disallowed for thegiven reasons.

Action: Make the corrections accordingly and tryagain.

TIBCO Object Service Broker Messages Without Identifiers

Page 158: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

144 |

Error attempting to log in TAMSECMGSource: TAM

Explanation: A security logging error hasoccurred. In the traceback log, this messagewill be preceded by a message describing theexact error.

Action: Review the traceback log for a prior errormessage. Take appropriate steps based onthis prior message.

ERROR changing archive file; %Source: Secure Audit Log

Explanation: You attempted to specify the givenfile as the archive file but you weredisallowed for the given reasons.

Action: Correct the errors as given and try again.

Error converting "%.%" ** %Source: Screen Server

Explanation: The rule is attempting to insert anumerical value into the field of a screentable. The specific reason for the conversionerror is given in the message.

Action: If the value is too big, make the screentable field larger so that it can hold the value.

Error converting derived field "%.%"Source: TAM

Explanation: The derived field rule has returneda value which cannot be converted to theattributes of the derived field.

Action: Do one of the following:

• Rewrite the rule so that it returns a valuematching the attributes of the derivedfield.

• Change the attributes of the derived fieldso that the field matches the return value ofthe derived field rule.

Error converting field "%" ** %Source: Screen Server

Explanation: An error occurred during theconversion of a numeric value.

Action: Check that the size of the field is largeenough to hold the value.

Error converting parm "%" of table "%"Source: TAM

Explanation: The parameter value does notmatch the attributes of the parameter in thetable definition.

Action: Do one of the following:

• Change the attributes of the parameter inthe table definition to match the existingparameter value.

• Use a parameter value which matches theattribute of the parameter definition.

Error converting selection for table "%"Source: TAM

Explanation: A value in a selection cannot beconverted to the attributes of the target field,(e.g., alphanumeric to numeric).

Action: Use a value which matches the attributesof the target field in the selection clause orthe stored selection.

TIBCO Object Service Broker Messages Without Identifiers

Page 159: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 145

Error detected during definition build;PRINT abortedSource: Screen Definer

Explanation: In the Screen Definer, you issuedthe PRINT command; however, a systemerror in the internal tables prevented theprinting.

Action: Do one of the following:

• Try again during the same Screen Definersession.

• SAVE and then reenter and try to printagain.

• SAVE and try to print from the object list.

Error detected in %. Conversion of % %to % % not allowedSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Error detected in system dump routine;"%" is not a valid event type; dump ofrule error terminatedSource: Interpreter

Explanation: This message is used by theprogram that produces the Object ServiceBroker Information Log; it indicates aninternal error.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Error detected in system dump routine;dump of rule error terminatedSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Error detected in the definition of theparameters for routine "%"Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 160: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

146 |

ERROR DETECTED WHENATTEMPTING TO ISSUE CANCELUSERSource: S6BTLADM - USER ACTIVITY

Explanation: When attempting to send theCANCEL USER request to the Data ObjectBroker, an error was detected.

Action: Review the job log for possible additionalmessages which may help identify the causeof the error. Retry your request. ContactTIBCO Support if the problem persists.

ERROR DETECTED WHENATTEMPTING TO ISSUETRACEID/NOTRACESource: S6BTLADM - USER ACTIVITY

Explanation: When attempting to issue thechange in tracing request an error wasdetected.

Action: Review the joblog to determine if thereare addition messages which may helpidentify the cause of the problem. Retry yourrequest. Contact TIBCO Support if theproblem persists.

Error detected when loading thedefinition of report "%"Source: Report Server

Explanation: A table access error occurred whenthe report server loaded the definition of thenamed report.

Action: Contact TIBCO Support.

Error detected when processing % %Source: Promotion

Explanation: The Promotion utility detected anerror when processing the specified objectduring application of the change request.

Action: See log for the cause of the error. You mayreapply the change after you have correctedthe error.

ERROR DETECTED WHENPROCESSING RESPONSESource: S6BTLADM - MONITOR PROCESS

Explanation: When validating the values you setfor the monitor processing an undeterminederror was detected.

Action: Retry your request. If the problempersists contact TIBCO Support.

Error during default value conversionfor "%.%"Source: TAM

Explanation: The default value for a subviewfield cannot be converted to the targetattributes.

Action: Change the attributes to an allowabletype, syntax, length, and number ofdecimals.

Error during key conversion for table"%"Source: TAM

Explanation: The attributes for the primary keyfor the subview table cannot be differentfrom those of the source table primary key.

Action: Change the primary key attributes of thesubview table to match the attributes of thesource table primary key.

TIBCO Object Service Broker Messages Without Identifiers

Page 161: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 147

Error during sort of table "%"Source: TAM

Explanation: The system sort was unable tocontinue.

Action: Review the message log. You may alsowant to review the amount of DASD spaceavailable for sorting, and increase it toaccommodate the largest volume of data tobe sorted. Refer to your Installation andOperations manual for DASD allocation.

Error encountered in Server TYPE "%"Server ID "%"Source: TAM

Explanation: A request was sent to a gateway ofthe indicated type, and an error occurredwhile processing the request.

Action: Contact TIBCO Support.

Error executing HELP rule: "%"Source: Screen Server

Explanation: The specified HELP rule failed toexecute successfully.

Action: If this rule has been modified, refer to thetraceback. If it has not been modified, contactTIBCO Support.

Error executing PROMPT rule: "%"Source: Screen Server

Explanation: The indicated PROMPT rule failed.

Action: If user prompting was defined for thefield, you can leave the cursor on this fieldand press <PF1> to see a list of valuesallowed for the field. Contact TIBCOSupport.

Error in % table name for assignment-by-name; %Source: Interpreter

Explanation: At evaluation time, an indirectreference was not evaluated to a valid tablename.

Action: Study the second part of the message thatgives details about the invalid name.

Error in arithmetic expression; "%"system condition detectedSource: Interpreter

Explanation: While evaluating an arithmeticexpression, a system condition was raised,but not handled.

Action: Verify the arithmetic expression. Youmay need to supply a handler.

ERROR IN COMMIT/ABORTCONFIRMATION RESPONSE,RETRYSource: S6BTLADM - INDOUBT TRX

Explanation: The internal processing of theutility detected an unexpected conditionwhen processing a confirmation response.

Action: Retry your request. If the problempersists contact the support center.

Error in definition of % table "%" atfield "%"Source: TAM

Explanation: The type, syntax, length, or # ofdecimals specified are not valid for this table.

Action: Verify the field attributes against theexternal file layout.

TIBCO Object Service Broker Messages Without Identifiers

Page 162: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

148 |

Error in definition of report "%": reportfield "%" of report table "%" has aninvalid SORT-BY numberSource: Report Server

Explanation: An error exists in the control fieldsof the report.

Action: Use the Report Definer to fix the controlfields.

Error in definition of report "%": reportfield "%" of report table "%" has aninvalid SUMMARY-BY numberSource: Report Server

Explanation: An error exists in the control fieldsof the report.

Action: Use the Report Definer to fix the controlfields.

Error in definition of report "%";controlling report table "%" has noreport fieldsSource: Report Server

Explanation: The body report table for thenamed report has no report fields.

Action: Use the Report Definer to correct thedefinition of the report.

Error in definition of report "%"; morethan one report table bodySource: Report Server

Explanation: The named report has more thanone body report table.

Action: Use the Report Definer to correct thedefinition of the report.

Error in definition of report "%"; reportfield "%" of report table "%" cannot beboth an ACROSS-BY and SORT-BYfieldSource: Report Server

Explanation: A report field of the body reporttable was used as a SORT-BY and anACROSS-BY field.

Action: Use the Report Definer to remove thereport field from the list of SORT fields. Animplicit SORT is performed for ACROSS-BYfields.

Error in definition of report "%"; reportfield "%" of report table "%" has aninvalid ACROSS-BY numberSource: Report Server

Explanation: The ACROSS-BY numbers eitherdo not start at 1 or are not consecutive.

Action: Use the Report Definer to identify andcorrect the problem.

Error in definition of report "%"; reportfield "%" of report table "%" has aninvalid break numberSource: Report Server

Explanation: A break member was eithernegative or not consecutive for the bodyreport table of a report.

Action: Correct the error in the definition of thereport by using the Report Definer.

TIBCO Object Service Broker Messages Without Identifiers

Page 163: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 149

Error in definition of report "%"; reporthas no report tablesSource: Report Server

Explanation: The definition of the named reportis incomplete because it has no report tables.

Action: Use the Report Definer to add reporttables to the definition of the report.

Error in dictionary definition of table"%"Source: TAM

Explanation: The dictionary occurrences mayhave been modified outside of the TableDefiner.

Action: Delete the table definition and redefine itagain.

Error in field "%" for CLC table "%"Source: TAM

Explanation: One of the following occurred:

• A field of the calculation (CLC) table (thatis not a primary key or a COUNT field) isnot a field of the source table.

• A field of the CLC table (that is not aCOUNT field) does not have the samesyntax or length as the source field.

• The primary key for the CLC table is not ofsyntax B and length 4.

Action: Determine the error in the field definitionand redefine the field accordingly.

Error in indirect name on a tam call; %Source: Interpreter

Explanation: The evaluation of an indirect tableor field reference is found to be a value thatcannot be a name.

Action: Verify that the rule argument or field of atable that is used to resolve the indirectreference is a name.

Error in menu - Objectlist or Menu forthis item does not existSource: Session Manager

Explanation: The menu was defined to promptor display another menu for this item. Therequired objectlist or menu does not exist.

Action: Define the objectlist or menu.

Error in menu - There is no rule for thisselectionSource: Session Manager

Explanation: A menu item requires the call orexecution of a rule, but does not have thename of the rule.

Action: Correct the menu.

Error in option; % encountered whenexpecting %Source: HLIPREPROCESSOR

Explanation: An invalid token appears in theoptions for the HLIPREPROCESSOR tool.

Action: Correct the options as specified in themessage.

TIBCO Object Service Broker Messages Without Identifiers

Page 164: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

150 |

Error in queue name for asynchronousevent "%"; %Source: Interpreter

Explanation: The expression evaluated todetermine the queue in a SCHEDULE TOstatement has not yielded a value that can bea name.

Action: Modify the expression that determinesthe queue.

Error in quoted string "%"Source: Rule Editor

Explanation: There is a syntax error in the quotedstring.

Action: Correct the quoted string to be one of thesupported formats of quoted strings: Plainstring, Unicode string, hexadecimal string orraw data string.

Error in record #, columns #-#Source: TAM

Explanation: An error occurred converting thedata in the specified columns of the specifiedrecord of the Import file.

Action: Ensure that the definition of the externaldata is correct. Also ensure that the externaldata itself is valid.

Error in SCHEDULE statement; queue"%" is undefinedSource: Interpreter

Explanation: The queue specified in aSCHEDULE statement is unknown to thescheduler.

Action: Check the list of valid queues.

Error in source table "%"; unable toconstruct object screenSource: Object Manager

Explanation: The definition of the tablecontaining the list has an error that preventsthe display of the list.

Action: Correct the table definition.

ERROR OCCURRED WHEN DUMPREQUEST ISSUEDSource: S6BTLADM - DIAGNOSTIC DUMP

Explanation: When attempting to send yourdump request to the Data Object Broker, anerror was detected.

Action: Review the joblog to determine if therewhere associated messages that may helpidentify the cause of the problem. Retry yourrequest. If the problem persists contactTIBCO Support.

ERROR OCCURRED WHENPROCESSING LOCK OWNERRETRIEVALSource: S6BTLADM - LOCK MANAGER

Explanation: When attempting to retrieve the listof owners of a particular table, the LockManager encountered an error.

Action: Retry the request, if the error recurscontact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 165: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 151

Error occurred while closing file used toschedule rule, error code %Source: Interpreter

Explanation: An internal error occurred whileclosing the file descriptor used to write theschedule model instance to a disk file.

Action: Contact TIBCO Support.

Error occurred while closing streamused to schedule rule, error code %Source: Interpreter

Explanation: An internal error occurred whileclosing the buffered I/O stream used to writethe schedule model instance to a disk file.

Action: Contact TIBCO Support.

Error occurred while unlinkingtemporary file used to schedule rule,error code %Source: Interpreter

Explanation: An internal error occurred whileattempting to unlink a temporary disk fileused to hold an instance of a schedule model.

Action: Ensure that the directory specified by theTEMPUNIT parameter has permissions thatallow for the deletion of files.

Error occurred while waiting forprocess used to schedule rule, errorcode %Source: Interpreter

Explanation: An internal error occurred whilewaiting for termination of the at(1) commandthat is used to schedule a batch job.

Action: Contact TIBCO Support.

Error processing % "%": %Source: Promotions Bind Tools

Explanation: An error occurred while attemptingto update the Bind flag for the specifiedobject.

Action: Review the reasons for the failures andresolve if you require the objects to beunbound then run @PROMBINDOBJS andre-run @PROMUNBINDOBJS.

Error reading colors from table "%"Source: Screen Server

Explanation: An error occurred reading thesystem color definitions from the indicatedtable.

Action: Contact your System Administrator.

Error recovery - end-of-transactionfailedSource: Session Manager

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Error recovery - ROLLBACK failedSource: Session Manager

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

TIBCO Object Service Broker Messages Without Identifiers

Page 166: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

152 |

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

ERROR RETRIEVING CURRENTLOG, REQUEST REJECTEDSource: S6BTLADM - OPERATOR FUNCT

Explanation: When attempting to process yourrequest to retrieve the last 400 operatormessages an error was detected.

Action: Review the joblog to determine if thereare additional message which may helpidentify the cause of the problem. Retry yourrequest. If the problem persists contact thesupport center.

Error retrieving DB2 table definition for"%"Source: TAM

Explanation: This is an internal error.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support or the SystemAdministrator with the log and adescription of what actions were beingperformed when this message wasgenerated.

Error retrieving IMS definition for "%"Source: TAM

Explanation: Internal error.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support or the SystemAdministrator with the log and adescription of what actions were being

performed when this message wasgenerated.

Error retrieving Screen definition for"%"Source: TAM

Explanation: One of the following could haveoccurred:

• System error.

• The screen definition has been modifiedoutside of the Screen Definer.

Action: Use the Screen Definer to redefine thescreen. If the problem persists, contactTIBCO Support.

Error retrieving security parm accessinfo for table "%"Source: TAM

Explanation: Internal gateway/server error.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

Error retrieving table definition for "%"Source: TAM

Explanation: One of the following could haveoccurred:

• System error.

TIBCO Object Service Broker Messages Without Identifiers

Page 167: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 153

• The table definition has been modifiedoutside of the Table Definer.

Action: Use the Table Definer to redefine thetable. If the problem persists, press <PF2>and print the log, then contact TIBCOSupport or the Database Administrator withthe log and a description of what actionswere being performed when this messagewas generated.

Errors: % Warnings: %. Change #%backed outSource: Promotion

Explanation: The errors and warnings givenresult from the change request numberspecified that was backed out.

Action: Consult the Promotions manual if youreceived errors or warnings that you want toresolve.

Errors: % Warnings: %Source: Promotion

Explanation: This message gives the number oferror messages and warnings that occurredin one phase for the objects that wereunloaded. It is joined to a message listing thenumber of objects unloaded:

Unloaded % Tables, % Screens, % Rules, % Reports

Action: If you received errors or warnings,consult the Promotions manual.

Errors: % Warnings: %Source: Promotion

Explanation: This message gives the number oferrors and warnings that occurred when theobjects were being backed up. This messageis followed by:

Backed up % Tables, % Screens, % Rules, % Reports

Action: No action is required.

Errors: %Source: Promotion

Explanation: This message gives the number oferrors that occurred during Phase 1 of applyprocessing. In this phase, the change requestinstructions are validated to ensure that thedisposition of objects are correct (e.g., new,modified, deleted or deleted occurrences).

Action: If you have errors, consult thePromotions manual.

ERRORS DETECTED ONHIGHLIGHTED INPUT FIELDS,CORRECT AND RETRYSource: S6BTLADM-Resource Management

Explanation: The highlighted values on thescreen are either invalid, present when notsupported, or missing when required.

Action: Correct the indicated values and retryyour update request.

Event access "%" is invalid for % tabletypeSource: Table Definer

Explanation: You entered an event access that isnot defined.

Action: Specify a valid event access. To review alist of valid event accesses, press <PF1>.

TIBCO Object Service Broker Messages Without Identifiers

Page 168: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

154 |

Event rule '%' must have TYPE = 'T' tohave ACCESS = 'G'Source: Table Definer

Explanation: Only T (Trigger) type event isallowed for access type of G (General).

Action: Specify valid ACCESS value for type ofevent rule.

Event type "%" is not allowed for %table typeSource: Table Definer

Explanation: You entered an event type that isnot defined.

Action: Specify a valid event type. To review alist of valid event types, press <PF1>.

Exception "%" signaledSource: Interpreter

Explanation: An exception was raised by aSIGNAL statement.

Action: Determine whether an exception handleris needed.

Exception handler ON "%" is alreadydefined in this ruleSource: Rule Editor

Explanation: A syntax error is in the rule; anexception handler is defined twice.

Action: Remove the duplicate exception handler.

Excess parameter value "%"encounteredSource: Report Generator

Explanation: You selected a table but typed inmore parameter values than there areparameters for the table.

Action: Remove any extra values.

Execute failed: %Source: General

Explanation: Internal error.

Action: Do the following:

1. Press <PF2> to print the log.

2. Contact TIBCO Support or the SystemAdministrator with the log and adescription of what actions were beingperformed when this message wasgenerated.

Execute of % table "%" exit routine "%"failedSource: TAM

Explanation: The user exit routine produced aninvalid return code.

Action: Examine the user exit routine todetermine why it produced an invalid returncode.

Execute Phase 1 of the Apply processSource: Promotion

Explanation: You tried to execute Phase 2 beforePhase 1.

Action: Execute Phase 1 first by using theAPPLY_PHASE1 rule.

TIBCO Object Service Broker Messages Without Identifiers

Page 169: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 155

Execute Phase 2 of the Apply processSource: Promotion

Explanation: You tried to execute Phase 3 beforePhase 2.

Action: Execute Phase 2 by using the ruleAPPLY_PHASE2.

Execute selected for %Source: Promotion

Explanation: You have selected the specified rulefor execution. When the change request ispromoted, this rule will be executed. If youdo not wish this to happen, use the C linecommand to remove it from the request.

Action: No action required.

Executing *** "Rule to Execute" ***Source: Promotion

Explanation: The Promotion facility is executingthe rule that was designated to be executed atpromotion time.

Action: No action required.

Execution Environment limit reachedSource: External Gateway Logon

Explanation: No more sessions will be accepted,as the Data Object Broker limit has beenreached.

Action: If required, change the Data ObjectBroker parameter limiting the number ofExecution Environments the Data ObjectBroker will support, and restart the DataObject Broker. Then resubmit the sessionwhen the Data Object Broker is ready.

Execution Environment StartupCompletedSource: Start Execution Environment

Explanation: Start Execution Environment wassuccessful.

Action: No action required.

Execution of rule "%" (specified using"RULE" keyword) FAILEDSource: Security

Explanation: When you attempted to log on, youspecified the "RULE" CLIST parameter. Inthis case, once the rule has executed, yoursession is terminated. There is a problemwith the rule and as a result, its executionfailed.

Action: Log on to the workbench and debug therule. If you cannot logon to the workbench,contact your System Administrator.

Execution of rule "%" failedSource: Interpreter

Explanation: The specified rule invoked throughan EXECUTE statement has failed.

Action: Press <PF2> for the Information log fordetails about the failure.

Execution stack overflowSource: Interpreter

Explanation: The rules called are nested toodeeply for the current setting of theExecution Environment parameterEXECSTACKSIZE.

Action: Do one of the following:

TIBCO Object Service Broker Messages Without Identifiers

Page 170: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

156 |

• Verify that this error message is not causedby an infinite loop. If it is, correct the rulesto eliminate the loop.

• Increase the size of the EXECSTACKSIZEparameter.

• If possible, replace recursion withiteration.

Executor cannot load binary program"%"Source: Session Manager

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Executor detected a bad data value;possible error in table data storeSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Executor error - end-of-transactionfailedSource: Session Manager

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Executor error - invalid opcode at offset#Source: Interpreter

Explanation: Internal error that may indicate aproblem with the Rule Editor. The messagelog contains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Executor error - ROLLBACK failedSource: Session Manager

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Expected % more parameter(s) for table%Source: HLIPREPROCESSOR

Explanation: An access statement does not nameenough parameters for a table.

Action: Correct the access statement.

TIBCO Object Service Broker Messages Without Identifiers

Page 171: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 157

EXPECTED COMMIT/ABORTCONFIRMATION NOT RECEIVEDSource: S6BTLADM - INDOUBT TRX

Explanation: When you were prompted toconfirm your manual indoubt transactionresolution your failed to press the requiredconfirmation key. Your resolution request hasbeen abandoned.

Action: No action required.

Expecting parameter for % inunparameterized table "%"Source: Copy Definition

Explanation: A non-parameterized table wasencountered in an object type that shouldonly have parameterized tables. Thedefinition of that object type may becorrupted.

Action: Contact TIBCO Support.

Exponent overflow on an exponentialoperationSource: Interpreter

Explanation: The result of an exponentialoperation exceeds some predefinedmaximum. Currently, this maximum isapproximately 10E75.

Action: Verify the expression to ensure that themaximum possible value does not exceed thepredefined maximum.

Exponent underflow on an exponentialoperationSource: Interpreter

Explanation: The result of an exponentialoperation is smaller than some predefinedminimum (approximately 2E-78).

Action: Verify the expression to ensure that theminimum possible value does not fall belowthe predefined minimum.

Export Server transaction end failedSource: TAM

Explanation: An open export file cannot beclosed.

Action: Review the message log.

If necessary, recreate the export file.

Export table % is undefinedSource: Builtin Routines

Explanation: The specified table is not defined asan export table.

Action: Define the appropriate export table.

External attributes of a key field musthave DECIMAL set to '0'Source: Adabas Definer

Explanation: Invalid external decimal forADABAS key fields.

Action: Specify external decimal of 0 forADABAS key fields.

TIBCO Object Service Broker Messages Without Identifiers

Page 172: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

158 |

External field name must existSource: Adabas Definer

Explanation: Invalid ADABAS external fieldname. A matching field name cannot befound in the ADABAS file definition.

Action: Enter a valid external field name inADABAS.

External Gateway TYPE "%" Server ID"%" unavailable or request abortedSource: TAM

Explanation: The gateway of the indicated typewas not started or it failed.

Action: Do the following:

1. Verify that the gateway and the ObjectService Broker Data Object Broker arestarted and available.

2. Verify that the server3d is correct in thetable definition.

For IMS Gateways, the RESPONSEMODEparameter should be set to ASYNC foronline gateways and SYNC for gatewaysrunning in batch mode. If this problempersists, contact TIBCO Support.

External length must be % for externalsyntax "%"Source: Table Definer

Explanation: The external length is incompatiblewith the external syntax.

Action: Specify a value for the external lengthwithin the range indicated by the message.Examine the external syntax to evaluate thecorrectness of the syntax/lengthcombination.

External routine library error - cannotload routine "%"Source: Interpreter

Explanation: A module corresponding to thespecified external routine was not loadedsuccessfully.

Action: Verify that the required module is in theexternal routine library.

External Server TYPE "%" Server ID "%"unavailable or request abortedSource: Table Definer

Explanation: The Gateway ID specified in themessage in not available

Action: Change the SERVERID to an available IDor start a new gateway

External syntax "%" is invalidSource: Table Definer

Explanation: The external syntax indicated in themessage is invalid.

Action: Enter valid external syntax. Press <PF1>for list.

External syntax for key fields must be'B'Source: Adabas Definer

Explanation: Invalid external syntax forADABAS key fields.

Action: Specify external syntax of B for ADABASkey fields.

TIBCO Object Service Broker Messages Without Identifiers

Page 173: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 159

Extra input found beyond end of rulestatementSource: HLIPREPROCESSOR

Explanation: More characters appear in theObject Service Broker statement after thesemicolon or colon.

Action: Correct the Object Service Brokerstatement by removing the extra charactersor by removing the semicolon or colon.

Extra parameter found in table %Source: HLIPREPROCESSOR

Explanation: A parameter found in a DEFINETABLE or an access statement does not existin the definition of the table.

Action: Correct the DEFINE TABLE or the accessstatement.

Extract abortedSource: Adabas Extract

Explanation: The message is to confirm yourrequest to cancel the ADABAS extract.

Action: No action required.

Extract and backup file names must bedifferentSource: Promotion

Explanation: You are attempting to apply asource or target promotion but the names ofthe extract and backup files are the same.

Action: Modify the extract or backup file name.

Extract completedSource: Promotion

Explanation: The extract process you started hascompleted. The status of the change requestis now X.

Action: No action required.

Extract ended - <PF2> for logSource: Adabas Extract

Explanation: ADABAS extract completed.

Action: Press <PF2> to view log.

Extracted ADABAS definition deletedSource: Adabas Extract

Explanation: The ADABAS definition for theDBID and File No has been deleted.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 174: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

160 |

Messages beginning with: F

Fail Safe level 1 requiredSource: External Gateway Logon

Explanation: The environment requires that thegateway/server run at Fail Safe level 1.

Action: Change the appropriate parameters,depending on the gateway/server type, torun as a Fail Safe level-1 gateway/server.

Fail Safe level 2 requiredSource: External Gateway Logon

Explanation: The environment requires that thegateway/server run as Fail Safe level 2.

Action: Change the appropriate parameters,depending on the type of gateway/server torun as a Fail Safe level-2 gateway/server.

Fail to update file; %Source: Batch Control Card

Explanation: An explanation is provided todescribe why you cannot update the filename for either the control card or selectionspecification. The failure may be due tolocking.

Action: If the failure is due to locking, wait andtry again at a later time.

Fail to update membership; %Source: Security

Explanation: You cannot save the membershipinformation because certain tables are lockedby other users.

Action: Try again later or contact the personlocking the tables to ask that the locks bereleased.

Failed to %; %Source: Table Editor

Explanation: Explains that the INSERT, DELETE,or UPDATE failed and gives an explanationwhy. For example:

• You are trying to insert a duplicateprimary key.

• Your validation failed on aninsert/update.

• You have locking or security problems.

Action: If due to:

• Duplicate primary key - Ensure that onlyone key is assigned the primary key value.

• Validation failure - Check the data andreenter it if it is invalid.

• Locking - Try again at some other time.

• Security - Contact your DatabaseAdministrator if there is a need for you tobe able to edit this occurrence. The DBAcan decide if you should be given thisauthority.

TIBCO Object Service Broker Messages Without Identifiers

Page 175: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 161

Failed to %; command NOT allowed forIDGEN tableSource: Table Editor

Explanation: The Table Editor cannot be used tocreate new occurrences for an IDgen table.Thus, line commands such as INSERT orREPLICATE are not allowed.

Action: Use the Single Occurrence Editor or writea rule to insert new occurrences into anIDgen table.

Failed to %; primary key value(s) notfully displayedSource: Table Editor

Explanation: When the primary key values arenot displayed (either because the field is toolong to fit on the screen or it has beenexplicitly excluded), certain operations suchas the INSERT and REPLICATE linecommands are not allowed.

Action: If possible, display the primary key infull and try the operation again. Otherwise,use the Single Occurrence Editor to performthe necessary operation.

Failed to % a temporary file; return code#Source: Report Server

Explanation: The Report Server required the useof a temporary system file to store data, butthe file operation failed with the givensystem return code.

Action: Refer to the system documentation todetermine the reason for the error.

Failed to activate transactionSource: Interpreter

Explanation: A transaction failed to activate.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Failed to CLEAR table %Source: Copy Defn/Data

Explanation: This message indicates that datacould not be cleared from the named table.

Action: No action.

Failed to COPY: %Source: Copy Defn/Data

Explanation: This line indicates the previouslydescribed object was not copied and givesthe reason why.

Action: No action.

Failed to deactivate transactionSource: Interpreter

Explanation: A transaction failed to deactivate.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 176: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

162 |

Failed to GET table@SEARCHLIBRARY; no changes tocross reference.Source: Global Cross Reference Build

Explanation: Failed to GET table@SEARCHLIBRARY in MetaStor. Unable torun REFMAKER utility. No changes havebeen made to the existing cross reference.

Action: Contact your Object Service BrokerSystem Administrator.

Failed to import; %Source: Tool for IMS Data

Explanation: This message explains why youcannot import the IMS database information.For example, there may be locking orsecurity problems.

Action: If there are locking problems, try again ata later time. If there are security problems,contact your Security Administrator.

Failed to import; field % is not a key ofsegment %Source: Tool for IMS Data

Explanation: You failed to import the IMSdatabase information because theinformation was inconsistent. The indicatedfield (used to specify a unique sequence) isnot a key field of the indicated segment.

Action: Verify the IMS database information inthe IMSGEN table.

Failed to import; IMSGEN table isemptySource: Tool for IMS Data

Explanation: The IMSGEN table does not containany IMS database information, and there isnothing to import.

Action: Check why the IMSGEN table is empty.Make sure the S6BIMSU extract program isrun properly and completes successfully.

Failed to import; segment % does notexistSource: Tool for IMS Data

Explanation: You failed to import the IMSdatabase information because theinformation was inconsistent. There was noinformation about the indicated segment inthe IMSGEN table.

Action: Verify the IMS database information inthe IMSGEN table.

Failed to load definition andoccurrences of % TablesSource: Unload/Load

Explanation: There was a failure in loading thedefinition and occurrences of the listedtables.

Action: Refer to the message log for errormessages describing the failure.

Failed to load definition of %Source: Unload/Load

Explanation: There was a failure in loading thedefinitions of the listed objects.

Action: Refer to the message log for errormessages describing the failure.

TIBCO Object Service Broker Messages Without Identifiers

Page 177: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 163

Failed to load definition of %Source: Unload/Load

Explanation: There was a failure loading thedefinitions of the listed objects.

Action: Refer to the message log for errormessages describing the failure.

Failed to load occurrences of % TablesSource: Unload/Load

Explanation: There was a failure in loading theoccurrences of the listed tables.

Action: Refer to the message log for errormessages describing the failure.

Failed to script; %Source: Character-based Text Editor

Explanation: This messages arises when either atable is to be included in a scripted file, or atable is embedded in a scripted file. %represents any message from the Parser orthe TAB_CHECK which detects an error inthe TABLE command or the IMBEDcommand. For example:

• NO SUCH TABLE

• WRONG # PARMS

• SYNTAX ERROR IN PARMS LIST

• TABLE IS EMPTY

• TABLE % IS NOT A TEXT TABLE.

Action: Make the corrections indicated on themessage line.

Failed to scroll; screen cannot fitprimary key & next field %Source: Table Editor

Explanation: You cannot scroll furtherhorizontally because the primary key and thenext field (to be scrolled in) cannot fittogether on the screen.

Action: Exclude either the primary key or thenext field from screen if you want to scrollfurther horizontally.

Failed to start % session; no sessionmenu or rule to execute specifiedSource: Security

Explanation: The profile of the specified useriddid not have a session menu or startup ruledefined and thus the session cannot bestarted.

Action: Supply either a session menu or a startuprule for the userid profile.

Failed to SUSPEND; % has beensuspendedSource: Security

Explanation: You attempted to execute thesuspend utility but were disallowed becauseyou had been suspended by anotheradministrator.

Action: Contact other Security Administrators ofyour system.

Failing routine : address=% name=%Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log.

Action: Study the Information Log. You can alsoprint this log and see a System Programmerfor assistance.

TIBCO Object Service Broker Messages Without Identifiers

Page 178: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

164 |

FATAL error detected; screen tablechanges CANCELLEDSource: Screen Definer

Explanation: Internal error.

Action: Contact TIBCO Support.

Field "%" already existsSource: Report Generator

Explanation: You already specified the indicatedfield in the same section (PRINT, SORT,BREAK, or ACROSS).

Action: Remove any duplicate names.

Field "%" does not exist in any of theselected data tablesSource: Report Generator

Explanation: The indicated field does not belongto any of the source data tables.

Action: Remove or change the field name.

Field "%" does not exist in any of theselected data tablesSource: Report Generator

Explanation: The indicated field name does notbelong to any source data tables.

Action: Remove or change the indicated fieldname.

Field "%" does not exist in table "%"Source: Report Generator

Explanation: The indicated field does not exist inthe definition of the indicated data table.

Action: Change the field name or select a fieldfrom the prompt area.

Field "%" does not exist in this tableSource: Table Definer

Explanation: In the selection, you have specifieda field which does not exist in this table.

Action: In the selection, specify only the fields ofthis table.

Field "%" is not a correct % identifierSource: HLIPREPROCESSOR

Explanation: The field name is not a valididentifier in the language in which it is used.

Action: Change the name to one which is validfor the host language.

Field "%" is not a print fieldSource: Report Generator

Explanation: The indicated field is not a printfield; it must be one of those shown at thebottom right of the screen.

Action: You may replace the indicated field byone of those shown at the bottom right of thescreen. If the field that you want is not shownthere, remove the field first and then pressthe FIELD function key to display the Fieldscreen. Select the field that you want as aprint field, press the FUNCT function key todisplay the Function screen, and select thefunction-field pair that you want.

TIBCO Object Service Broker Messages Without Identifiers

Page 179: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 165

Field "%" is not a report field of reporttable "%"Source: Report Server

Explanation: The source of a derived report fieldrefers to a report field name that does notexist.

Action: Use the Report Definer to correct thereference to the name. Note that break reportfields can refer to both break and body reportfields.

Field "%" is not part of table "%"Source: Debugger Utility

Explanation: You have tried to list (or set) a fieldof a table which has not been accessed so farby your application.

Action: Verify the spelling of the table, fieldcombination to be listed (or set).

Field "%" is not part of table "%"Source: Screen Definer

Explanation: In the Screen Table Painter, yourequested a copy of a field of a table, but thefield that you named does not occur in theindicated table.

Action: Respecify the field if you made a typingerror, or request a partial copy and select theappropriate field from the table.

Field "%" is referred to more than onceSource: Screen Definer

Explanation: Field names must be unique withina screen table definition.

Action: Change one of the duplicate field names.

Field "%" requires a valueSource: Table Editor

Explanation: The field specified is marked asrequired in the table definition. You gave it anull value.

Action: Give a non-null value for this field.

Field "%" was not assigned a valueSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The i-th field of thetable was not assigned a value.$FORMATROW was called for a table beforethe first GET or FORALL for the table.

Action: Contact TIBCO Support.

Field "%.%" or "%.%" does not existSource: Print Table

Explanation: One of two fields that werematched for a join does not exist in theirrespective tables.

Action: Correct the field name.

Field "%.%" overflows screen fieldSource: Screen Server

Explanation: The rule is attempting to insert datafrom a table field into a screen field. Thelength of the data is too large for this screenfield.

Action: Increase the length of the field in thescreen table.

TIBCO Object Service Broker Messages Without Identifiers

Page 180: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

166 |

Field "%.%" too large to processjustificationSource: Screen Server

Explanation: The data in the field of the screentable has too many characters. The maximumnumber of characters allowed is 256.

Action: Do one of the following:

1. Insert less data into the screen table field.

2. Divide the data and put it into two screentable fields.

Field % cannot be a key fieldSource: Table Definer

Explanation: The indicated field cannot be a keyfield.

Action: Remove the P designation from theindicated field.

Field % cannot have a value in the %fieldSource: Table Definer

Explanation: You have specified an attributewhich is not permitted for the specified field.

Action: Remove the value from the indicatedfield.

Field % could not be found in any %cursor tablesSource: Host Language Interface

Explanation: The specified field does not belongto any tables referenced in the join cursortable.

Action: Check if field name is incorrectlyspecified, or use another.

Field % is undefinedSource: HLIPREPROCESSOR

Explanation: The named field was not defined,either in the Object Service Broker databaseor in the DEFINE TABLE statement. Possibly,the access statement refers to the wrong field.

Action: Correct the definition or the accessstatement.

Field % must be Q B 4Source: Table Definer

Explanation: You specified the incorrectattributes for an EES count field.

Action: Modify the attributes accordingly.

Field % not found in table %Source: Host Language Interface

Explanation: The indicated field is not in theindicated table.

Action: Correct the name of the field.

Field % of table % has a SIX that isincompatible with the source; deleteSIX before ApplySource: Promotion

Explanation: The named field has a secondaryindex on the target system, but the field is notincluded in the table definition beingpromoted.

Action: Remove the secondary index on this fieldbefore proceeding with the promotion.

TIBCO Object Service Broker Messages Without Identifiers

Page 181: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 167

Field % of table % is incompatible withthat on % systemSource: Promotion

Explanation: The specified field of the table isincompatible with the one on the specifiedsystem, so the APPLY process cannotproceed as requested.

Action: On the source system, Unaccept thechange and return it to the developer. Thedeveloper should roll back the changerequest and make the specified tablecompatible with the one on the target system.The change can then be re-extracted andreapplied to the target system.

Field % of table % too small to hold dataSource: Debugger Utility

Explanation: You have tried to assign (usingSET) a value to a field of a table. This hasfailed because the source value is too big forthe field.

Action: Verify the spelling of the table, fieldcombination to be assigned. Verify that thevalue is suitable. Verify that the field is bigenough.

Field % overlaps with field %Source: CA Datacom Table Definer

Explanation: In the EXTENSIONS context of theDAT Table Definition, where the fields of theObject Service Broker table are specified, youspecified an Object Service Broker field thatuses a CA-Datacom field in such a way thatpart of that CA-Datacom field is also used inanother Object Service Broker field. Forexample, if you use a group field for an

Object Service Broker field and then try touse one of the elements of this group field inanother Object Service Broker field, you getthis error.

Action: You can only refer to any given CA-Datacom data via one CA-Datacom fieldreference. Thus, you must change the fieldspecifications so that there is no suchoverlap.

Field '%' spans fixed column boundarySource: Screen Definer

Explanation: The specified field extends beyondthe fixed column boundary.

Action: Either adjust the fixed column boundaryto accommodate the field, or make sure thatfield does not interfere with the fixed columnboundary.

Field at row % and col % has a length ofzeroSource: Screen and Report Painters

Explanation: The field at the indicated row andcolumn has a length of zero. This is aninvalid value.

Action: Change the length of the field to be oneor greater.

Field cannot extend beyond screenlength at bottom (row %)Source: Screen Definer

Explanation: A field cannot extend beyond thelength of a page.

Action: Make sure that the field is withinspecified page length, or increase the pagelength to accommodate the field.

TIBCO Object Service Broker Messages Without Identifiers

Page 182: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

168 |

Field cannot extend beyond screenlength at top (row %)Source: Screen Definer

Explanation: A field cannot extend beyond thetop border of a screen.

Action: Either make sure that field is within thescreen area or adjust the starting point of thescreen to accommodate the field.

Field cannot overlap left boundary ofscreen (%-255 columns)Source: Screen Definer

Explanation: A field cannot start before thespecified left boundary of a screen.

Action: Either move the field to within thedefined screen area, or adjust the leftboundary of the screen to accommodate thefield.

Field cannot overlap right boundary ofscreen (% columns wide)Source: Screen Definer

Explanation: In the Screen Table Painter, youdefined a field so that it overlaps the rightboundary of the screen (e.g., the field is atcolumn 70 and you tried to change the fieldlength in the definition area to 50, but thescreen is only 80 columns wide).

Action: Change the length of the invalid field sothat it does not overlap the right boundary ofthe physical screen.

Field dictionary changes cancelledSource: Field Dictionary

Explanation: Creation of a new global fielddefinition or updates to an existing globalfield definition have been canceled.

Action: No action required.

Field dictionary definition for %deletedSource: Field Dictionary

Explanation: You confirmed the request to deletethe field dictionary definition by pressing<PF22>.

Action: No action required.

Field dictionary definition for % savedSource: Field Dictionary

Explanation: A new global field definition hasbeen saved or an existing global fielddefinition has been modified.

Action: No action required.

Field entered greater than 256 byteslongSource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 183: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 169

Field help changes cancelledSource: Screen Definer

Explanation: The changes that have been madeto the field Help during this edit session havebeen canceled.

Action: No action required.

Field help UPDATEDSource: Screen Definer

Explanation: The Help for the field has beenupdated.

Action: No action required.

Field length must be %Source: Table Definer

Explanation: Invalid field length.

Action: Modify field length to be within thedesired range specified in the message.

Field list selectedSource: Field Dictionary

Explanation: You requested a selection of fieldslisted for a tool. This message confirms theselect request.

Action: No action required.

Field marker "^" was typed in oroverwritten; image restoredSource: Report Definer

Explanation: The number of defined fields (eachfield marked with a ^ character) for aparticular row within the Paint area haschanged without an ADD-FIELD operation.

New fields can only be added by an ADD-FIELD operation. Also, fields may not bemoved between rows by Paint area changesonly.

Action: Remove any ^ fields from the indicatedrow in the Paint area until only the specifiedfield count remains.

Field must have BOTH its row and itscol as zero or nonzeroSource: Screen Definer

Explanation: A field cannot have a zero and anonzero combination for its row and column.

Action: Either assign row and column to zeros, ornon zeros.

Field name "%" is defined more thanonceSource: Report Definer

Explanation: A defined report field cannotappear more than once in the definition list.

Action: Refer to each report field only once in thedefinition list.

Field name "%" is not in appendagetable "%"Source: Table Definer

Explanation: The indicated name is not a field ofthe indicated appendage table.

Action: Do not use an appendage table as thistype of table is not yet supported.

TIBCO Object Service Broker Messages Without Identifiers

Page 184: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

170 |

Field name "%" is not in source table"%"Source: Table Definer

Explanation: The indicated field does not exist inthe source table definition.

Action: Look at the definition of the source tablefor fields that you can use in the subview, oradd a field to the source table.

FIELD NAME is required for eachmenu itemSource: Menu Definer

Explanation: You have included a menu itementry; however, you have not specifiedwhich field will invoke this entry.

Action: You must include the field name whichbelongs with this menu item.

Field referenced in the selection is notpart of table's defnSource: Static SQL for DB2 Gateway

Explanation: One or more of the fields in theselection is not in the MetaStor DB2 tabledefinition.

Action: Verify selection against table definition.

Field with syntax % cannot have defaultvalueSource: Table Definer

Explanation: A field with the specified syntaxcannot have a default value.

Action: Remove the default value from the field.

Fields "%" and "%" overlap in screentable "%"Source: Screen Server

Explanation: Fields in a screen table have beendefined in such a way that they areoverlapping each other.

Action: Change the screen table definition(s) sothat the fields are no longer overlapping.

Fields "%" and "%" overlapSource: Table Definer

Explanation: The indicated fields overlap eachother.

Action: Modify the offset or length (or both) ofthe inserted field to eliminate the overlap.

FIELDS copied - Use <PF4> to mark allheading rowsSource: Report Definer

Explanation: All requested fields have beencopied. Because the COPY command copiesheadings but does not mark rows as headingrows, a warning message is issued to requestthat the user mark any desired heading rows.

Action: Press <PF4>, if desired, and mark anyheading rows.

TIBCO Object Service Broker Messages Without Identifiers

Page 185: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 171

Fields have been added or removed inImage Area at row %Source: Screen and Report Painters

Explanation: Some fields have been added orremoved from the indicated row in the ImageArea by either typing in new fields, orblanking out existing fields in the ImageArea. This is not allowed.

Action: Restore the Image Area row so that itcontains the correct number of fields for thatrow.

Fields missing for table which now hasdata; cannot saveSource: Table Definer

Explanation: Data has been added to the tabledefinition since the Table Definer wasopened but you have deleted one or morefields from the definition.

Action: If you know the attributes of the fieldsthat have been deleted and the definer youare using allows it, you can add the fieldsback to the definition and save. Otherwise,you can save as a new table definition or exitwithout saving.

Fields with syntax F or length greaterthan 127 not copied from source tableSource: Table Definer

Explanation: Fields with syntax F or lengthgreater than 127 are not permitted in a CLCtable. These fields were not copied from thesource table.

Action: No action is required.

File "%" already opened for %Source: Builtin Routines

Explanation: @READDSN and @WRITEDSNcalled for the same opened file.

Action: Close the file and reopen it beforealternating @READDSN and @WRITEDSN.

File "%" is not a partitioned data setSource: Builtin Routines

Explanation: The function to be performedrequires the named file to be a partitioneddata set, but it is not.

Action: Correct the error and retry.

File "%" not foundSource: Builtin Routines

Explanation: The named file could not be foundin the system.

Action: Try another file name.

File % for change#% of node % isunavailable:Source: Promotion

Explanation: The extract file for the specifiedchange request is not available.

Action: Make the specified file available forextraction if you want to repackage thechange from the previously extracted file.

File '%' does not contain any pages forsegment '%'Source: Offline Utilities

Explanation: The specified file has no pages forthe specified segment.

Action: None

TIBCO Object Service Broker Messages Without Identifiers

Page 186: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

172 |

File contents printedSource: Unload/Load

Explanation: The list of objects in the file, asshown on the LOADER prompt screen, hasbeen printed.

Action: No action required.

File is too old; use LOAD or LLOADSource: Unload/Load

Explanation: This file is an older format and doesnot have some characteristics whichLOADER uses to recognize the contents.

Action: Use LOAD or LLOAD which have morebackward compatibility.

Fill in name of CREATING User orGroup before pressing <Enter>Source: Security

Explanation: You pressed <Enter> on the mainmenu in the DEFAULT PERMISSIONSoption without supplying a user or groupname.

Action: You can press <PF2> to select from a listof creating members, or you can type in thename of an existing user or group(depending upon who will have defaultpermissions defined for them).

Fill in OBJECT TYPE before pressing<Enter>Source: Security

Explanation: You requested the management ofpermissions from the main menu, and youspecified the object name, but not the objecttype.

Action: Fill in the object type and press <Enter>again.

Fill in OBJECT TYPE before pressingOPTIONSSource: Security

Explanation: You requested OPTIONS in themain menu for the Manage ObjectPermissions function, but you did not specifythe type of object to provide options for.

Action: Fill in the appropriate abbreviation andpress the OPTIONS function key again.

Fill in the name of the GROUP beforepressing <Enter>Source: Security

Explanation: You pressed <Enter> on theMANAGE GROUP option of the main menuwithout supplying a group name.

Action: Supply a group name, or request andselect from the options list.

Fill in the name of the OBJECT beforepressing <Enter>Source: Security

Explanation: You requested the management ofpermissions for an object, but you did not fillin the name of the object before pressing<Enter> (on the main menu).

Action: Fill in the name of the object (and objecttype) before pressing <Enter>, or a useroption list is available by filling in the objecttype and using the options function.

TIBCO Object Service Broker Messages Without Identifiers

Page 187: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 173

Fill in the name of the object set beforepressing <Enter>Source: Security

Explanation: You have indicated that you wish toSpecify Permissions for an object set orManage Permissions to an object set bypressing <Enter> on the Security ManagerMain Menu. You have not provided the nameof the object set.

Action: Fill in the name of the object set, or press<PF2> for a listing of options.

Fill in userid of Security Administratorbefore pressing <Enter>Source: Security

Explanation: You requested to view or updatethe profile of a Security Administrator fromthe main menu, but you did not supply theuserid before pressing <Enter>.

Action: Fill in the userid of the SecurityAdministrator, or use the OPTIONS functionto view a list and select a userid.

Filter % createdSource: Secure Audit Log

Explanation: You defined a new filter forviewing the auditlog contents and thismessage confirms the new filter definitionhas been created.

Action: No action required.

Filter % deletedSource: Secure Audit Log

Explanation: You deleted one of your filterdefinitions and this message confirms thatthe specified filter has been deleted.

Action: No action required.

Filter % not savedSource: Secure Audit Log

Explanation: You did not confirm to save thespecified filter definition and thus the filterwas not saved.

Action: No action required.

Filter % savedSource: Secure Audit Log

Explanation: You made changes to one of yourfilter definitions and saved the changes. Thismessage confirms that the changes have beensaved.

Action: No action required.

FINAL COLS must be consecutive,ending in column -1Source: Report Definer

Explanation: Final columns can only be markedas a consecutive series of Fs, and the last onemust be in the last report column.

Action: Correct the F line commands.

FINAL COLUMNs for break table "%"not the same as FINAL COLUMNs forbody table "%"Source: Report Server

Explanation: The number of final columns forbreak tables and body tables must be thesame.

Action: Use the Report Definer to correct thereport definition.

TIBCO Object Service Broker Messages Without Identifiers

Page 188: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

174 |

Find of screen table buffer failedSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The screen tablename is undefined or $FORMATROW wascalled before the first GET or FORALL for thetable in the transaction.

Action: Contact TIBCO Support.

First table cannot be deleted from thejoin; just type overSource: Print Table

Explanation: The cursor was placed on the firsttable when <PF22> was pressed; this tablecannot be deleted.

Action: If you want to change the first table, youcan type over the table name.

FL/EL conversion error - table "%", field"%", has invalid syntaxSource: TAM

Explanation: An invalid syntax definition of thefield in the table was found.

Action: Check and correct the syntax of the fieldin the table definition.

FL/EL conversion error - table "%", field"%", has occurrence longer thandictionary lengthSource: TAM

Explanation: The reported field has instance datawith longer lengths than the defineddictionary length.

Action: Change the total field length in thedefinition of the table so that it matches thelength of the instance.

FL/EL conversion error - table "%", field"%" contains invalid dataSource: TAM

Explanation: The external data does not matchthe attributes of the specified field in thedefinition of the table.

Action: Verify the attributes of the specifiedfield's definition with the external file layout.

Float field length can be 8 to 37charactersSource: Screen Definer

Explanation: You have defined a field with asyntax of float, but the length is not between8 and 37 characters.

Action: Change either the syntax or the length.

Float specification not supported inmaskSource: Builtin Routines

Explanation: The basic string starts with the firstdigit place holder and ends with the last digitplace holder. "E" or "e" is not allowed withinthe basic string of a mask.

Action: Remove all "E" and "e" characters fromthe basic string.

Float syntax keys not allowed - table"%"Source: TAM

Explanation: A primary key field cannot have asyntax of FLOAT.

Action: Change the syntax of the primary keyfield in the table definition from F to anothersyntax such as B, P, C or V.

TIBCO Object Service Broker Messages Without Identifiers

Page 189: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 175

Float value not supported in $PICsourceSource: Builtin Routines

Explanation: You have used a float number in aVALUE specification. This is not currentlysupported.

Action: Correct the VALUE specification.

For %, it must have Syntax: "%" Length:"%"Source: Table Definer

Explanation: Invalid syntax and/or length.

Action: Specify valid syntax and length for thefield/parameter as indicated in the message.

For %-type tables, ALL DATA is always"Y"Source: Security

Explanation: When requesting to managepermissions, or specifying an application'stable list, you referred to a table of type SCR,RPT, or TEM. Only the definition modes arerelevant, not the table instances, becausethese table types do not have data in thedatabase (i.e., the data in these tables existsonly in the user's Execution Environment).

Action: No action required.

For DELETE Static SQL to be generatedSELECT must be generatedSource: Static SQL for DB2 Gateway

Explanation: As part of the DELETE processing,a SELECT is performed to position on therecord to be deleted. Therefore, in order forDELETE Static SQL to be generated, SELECTStatic SQL must also be generated.

Action: Enter Y under the S column to indicategenerate SELECT Static SQL, or enter Nunder the D column to indicate no DELETEStatic SQL is to be generated.

For TABLE object type, must specifyDEFN and/or DATA = "Y"Source: Unload

Explanation: You have specified a table tounload, however you have not specifiedwhether to unload the data, the definition orboth.

Action: You must specify either DATA=Y orDEFN=Y or both. Remove the entry if neitherthe data nor definition of the table are to beunloaded.

FORALL loop has not started, ENDstatement ignoredSource: HLIPREPROCESSOR

Explanation: An END statement appearswithout a matching FORALL statement tobegin the loop.

Action: Remove END or enter the necessaryFORALL.

TIBCO Object Service Broker Messages Without Identifiers

Page 190: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

176 |

FORALL requests not allowed for %tablesSource: TAM

Explanation: FORALL operations are notallowed for the table type indicated.

Action: Remove the FORALL statement.

FORALL statement is not supportedinside an IF blockSource: HLIPREPROCESSOR

Explanation: The FORALL statement appearsinside a COBOL IF block; this is notsupported.

Action: Use GETFIRST and GETNEXT instead ofa FORALL statement.

Formatting of title/footing overflowsfor "%".length( left field)= "#". length(center field)= "#". length( right field)="#"Source: Builtin Routines

Explanation: When formatting a title or footingline (including the page number line), theleft, center and right portions of the linecannot overlap.

Action: Adjust the arguments or the page width.

Found % objectsSource: Global Cross Ref. Search

Explanation: A search has found the specifiednumber of objects.

Action: No action required.

From date (%) is greater than to date (%)Source: Secure Audit Log

Explanation: You attempted to purge the auditlog contents of a given date range but thedate range that you specified was incorrect;the start date was larger than the end date.

Action: Correct the date range specification andtry again.

Function "%" & field "%" already existSource: Report Generator

Explanation: You specified the function-fieldpair more than once in the samesummary/break section.

Action: Remove the indicated function-field pairby blanking out the field name.

Function "%" cannot be called assubroutineSource: Interpreter

Explanation: You invoked a functional tool as aprocedure.

Action: Modify the invoking statement.

Function "%" did not return a valueSource: Interpreter

Explanation: A RETURN statement is missing inthe functional rule.

Action: Ensure that the functional rule alwaysreturns a value or raises an exception.

TIBCO Object Service Broker Messages Without Identifiers

Page 191: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 177

Function "%" is invalidSource: Report Generator

Explanation: The indicated function is invalid; itmust be one of the functions shown at thebottom left of the screen.

Action: Type a valid function over the invalidone, or remove the function-field pair andselect from the prompt area.

Function "%" used in a CALL statementSource: Interpreter

Explanation: You invoked a functional rule in aCALL or TRANSFERCALL statement.

Action: Correct the invocation or definition of thespecified function.

Function "EVENTSCREEN" can only becalled by a screen validation ruleSource: Interpreter

Explanation: You called the EVENTSCREEN tooloutside of a validation rule.

Action: Use EVENTSCREEN only from within avalidation rule.

Function "EVENTTABLE" can only becalled by a derived fields, trigger, orvalidation ruleSource: Interpreter

Explanation: You called the EVENTTABLE toolfrom outside a derived field or an event rule.

Action: Use EVENTTABLE only from within aderived field or an event rule.

Function "PARMVALUE" may only beused with a triggered eventSource: Interpreter

Explanation: You used the routine PARMVALUEtool outside an event rule.

Action: Ensure that PARMVALUE is called by anevent rule only.

Function ABS has been called with anon-arithmetic argumentSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Function key "%" is not active; <PF1> =HELPSource: General

Explanation: You pressed an inactive functionkey.

Action: Enter a valid function key. If necessary,press <PF1> to see a list of available functionkeys.

Function key "%" is not supported;press <PF1> for HelpSource: Table Editor

Explanation: You have pressed an inactivefunction key.

Action: Enter a valid function key. If necessary,press <PF1> to see a list of the availablefunction keys.

TIBCO Object Service Broker Messages Without Identifiers

Page 192: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

178 |

Function key not supportedSource: Rule Editor

Explanation: You have pressed an inactivefunction key.

Action: Enter a valid function key. If necessarypress <PF1> to see a list of available functionkeys.

Function not allowed for EXECUTEstatementSource: Interpreter

Explanation: You invoked a function through anEXECUTE statement; this is not allowed.

Action: Modify the statement in error to invokethe function properly. See the Processingmanual for information about invokingfunctions.

FUNCTION RESTRICTED TO LOCALNODE, REQUEST REJECTEDSource: S6BTLADM - COMMON MESSAGES

Explanation: You are currently processing aremote node. Some functions such as theoperator and path management features areonly available to an Administrator operatingin local (directly connected to the target DataObject Broker), mode only.

Action: Terminate the Administrator and start anew Administrator session with the desiredtarget Data Object Broker.

TIBCO Object Service Broker Messages Without Identifiers

Page 193: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 179

Messages beginning with: G

Generate/Remove Static SQL: % errors.CHECK LOG for warningsSource: Static SQL for DB2 Gateway

Explanation: The generation or removal of StaticSQL for one or more modules produced oneor more errors.

Action: Press <PF2> to see the log. Find all of thewarning messages, and act on them.

Generated name "%" is identical toprevious; use renameSource: HLIPREPROCESSOR

Explanation: The combination of the table andfield names has resulted in a COBOL nameidentical to one already produced.

Action: Use the RENAME on the tabledeclaration to avoid the duplicate name.

Generated name "%" is identical toprevious; use renameSource: Host Language Interface

Explanation: New name of table is the same asthe old name.

Action: Rename the new name.

Generated name "%" is longer than %characters; use renameSource: Host Language Interface

Explanation: The preprocessor translates"table.field" names into "table-field" namesthat are valid in COBOL. COBOL, however,only permits these names to be a length of 30,while an Object Service Broker "table.field"name can be 33 characters long. This messageappears when the table and field namecombination exceeds 30 characters.

Action: Use the Host Language Interfacestatement DEFINE TABLE to rename thetable, field, or both to shorter names.

Generated name "%" more than %characters; use renameSource: HLIPREPROCESSOR

Explanation: The preprocessor translates"table.field" names into "table-field" namesthat are valid in COBOL. COBOL, however,only permits these names to be a length of 30,while an Object Service Broker "table.field"name can be 33 characters long. This messageappears when the table and field namecombination exceeds 30 characters.

Action: Use the Host Language Interfacestatement DEFINE TABLE to rename thetable, field, or both to shorter names.

TIBCO Object Service Broker Messages Without Identifiers

Page 194: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

180 |

Get failed for dataset "%"; module "%";R15 = %Source: Session Manager

Explanation: A GET operation failed against thedata set specified in the message. The nameof the module in which this failure occurredis specified. The return code is provided inRegister 15.

Action: Call your system administrator to checkthe return code in Register 15 against theappropriate vendor's manual. Correct theproblem as required.

GET requests to % tables must specifykey valueSource: TAM

Explanation: A GET operation has beenrequested against the indicated type of tablewithout a key selection clause.

Action: Specify a primary key equality in aselection while issuing GET requests againstthe indicated type of table.

Give default location with DEFAULT orSRC & SOURCENAME fieldsSource: Table Definer

Explanation: You tried to save a minimal tabledefinition whose definition is invalid.

Action: Refer to the Managing Data manual forinformation on how to create a valid minimaldefinition.

GLOBAL CONSTANT ANDVARIABLE RETRIEVAL ERRORSource: S6BTLADM - COMMON MESSAGES

Explanation: When attempting to retrieve vitalData Object Broker information, the requestfailed.

Action: Check the log for accompanyingmessages and retry if appropriate.

Global fields are not available for %Source: Table Definer

Explanation: The global field dictionary is notavailable for the specified table.

Action: No action required.

Global fields are not available for type"%" in table definerSource: Table Definer

Explanation: Global fields are not available forthe indicated table type.

Action: No action required.

GLOBAL PARMS COULD NOT BERETRIEVEDSource: S6BTLADM - GENERAL STATS

Explanation: The block of storage from the DataObject Broker that contains the informationrequired to build the General Statistics screencould not be retrieved.

Action: Press <Enter> to try obtain the blockagain. If the failure persists contact TIBCOSupport.

TIBCO Object Service Broker Messages Without Identifiers

Page 195: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 181

GlobalField "%" already exists; choosenew name or restore "%"Source: Field Dictionary

Explanation: You changed the field name afterentering the Field Manager. The name cannotbe changed because a field with that namealready exists.

Action: Another name must be selected.

GPR % %Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log.

Action: For more information, show this messageto a System Programmer.

Grammar "%" has occurrences withsame state "%" and token "%"Source: Parse

Explanation: The grammar specification isincorrect because it contains occurrenceswith the same state and token values.

Action: Correct the grammar specification toremove duplicate values.

Group "%" does not existSource: Security

Explanation: You referred to a non-existentgroup, usually in the userid profile screen.

Action: Remove or change the invalid group. Ifyou are in your profile, you can use theMEMBERSHIPS function to determinewhich groups include you as a member.

Group ALL is a VIRTUAL group;cannot be specifiedSource: Security

Explanation: You requested the definition of thevirtual group ALL, which is system-generated, and cannot be defined.

Action: No action required.

Group cannot include another group;use VIEW GROUP to selectSource: Security

Explanation: You included a group entry in themembership list of a group definition.

Action: You must remove the group entry beforeyou can successfully save this screen. If themembers of the group entry are to beincluded in the group being defined, use theVIEW GROUP function to select themembers of the new group.

TIBCO Object Service Broker Messages Without Identifiers

Page 196: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

182 |

Messages beginning with: H

Hawk Microagent: Buffer of length %bytes supplied when % bytes neededfor %Source: Hawk Microagent

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 Customer Support for assistance.

Hawk Microagent: Out of memorySource: Hawk Microagent

Explanation: An internal memory allocationfailure occurred related to Hawk.

Action: Either run fewer processes on yoursystem or add memory.

Hawk Microagent: System call '%'failed, error is % [%]Source: Hawk Microagent

Explanation: The specified operating system callfailed.

Action: Check the operating system errornumber provided with the message. Itshould indicate the reason for the failure.

Hawk Microagent: Unexpected errorSource: Hawk Microagent

Explanation: An unexpected error occurredrelated to Hawk.

Action: Contact Customer Support.

Hawk Microagent: Win32 call '%' failed,GetLastError() returned % [%]Source: Hawk Microagent

Explanation: A Win32 API call failed.

Action: Examine the operating system errorcodes to determine the reason for this failure.

Heading field spans two data rowfields; heading link set to NSource: Report Definer

Explanation: You added a heading field that ispositioned above two data fields. The ReportDefiner cannot tell which field the headingshould be associated with, and so theheading link to field attribute cannot be used.

Action: No action is required; you will have tomove your headings and fields separatelybecause heading link is set to N. If you wantthe heading link set to Y, move the headingfield so that it is above only one data field.

HEADING ROWS must be 0 for allTITLES ONLY report tablesSource: Report Definer

Explanation: A titles report table (TITLE

ONLY=Y) must have every row defined as atitle row.

Action: Change the HEADING ROWS for thisreport table to 0.

TIBCO Object Service Broker Messages Without Identifiers

Page 197: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 183

Help Screen for Screen definition "%"PRINTEDSource: Screen Definer

Explanation: You printed the Help defined forthe screen that you are currently defining.

Action: No action required.

HELP SELECTION IS INVALID,PLEASE TRY AGAINSource: S6BTLADM - COMMON MESSAGES

Explanation: You have entered a selection toprocess the next Help level, which is notvalid for the current family of Help text.

Action: Correct your selection and retry.

HEX FORMAT SEARCH TOKENTRUNCATED TO FULL WORDSource: S6BTLADM - PAGE IMAGES

Explanation: The search token you havespecified is in hex notation. The searchalgorithm is limited to 4 hex bytes for asearch of this type. The search processingroutine has truncated the specified searchargument to a fullword or length of 4 bytes.

Action: No action required.

Highest change request number fornode % is %Source: Promotion

Explanation: You have used the STARTNUMBER or END NUMBER to narrowdown the range of a query. However, therange specified is beyond the range ofchange requests that exist at this source nodeand location. The START NUMBER defaults

to the first change request on the system. TheEND NUMBER defaults to the last changerequest on the system. Either field can be leftblank to get the default range bound.

Action: Correct the range and try the queryagain.

Highlighted fields do not match globaldefinitionsSource: Table Definer

Explanation: You are warned that thehighlighted fields do not match global fielddefinitions.

Action: You may want to change the highlightedfield definitions so that they will matchglobal field definitions. A list of global fielddefinitions can be obtained by pressing<PF14>.

HOST COMMUNICATION PATHALLOCATION FAILED, RC=XXXXSource: S6BTLADM - COMMON MESSAGES

Explanation: When attempting to open acommunication pathway to the desired DataObject Broker, the request was rejected by thecommunication sub-system.

Action: Ensure the spelling of the HOST or TDSparameter values and ensure the target DataObject Broker is up and available.

TIBCO Object Service Broker Messages Without Identifiers

Page 198: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

184 |

HOST= IS A REQUIREDPARAMETERSource: S6BTLADM - COMMON MESSAGES

Explanation: When attempting to activate theAdministrator utility, you neglected tospecify either the HOST= or TDS=parameter. One of these parameters must bespecified to identify which Data ObjectBroker to connect to.

Action: Correct the start-up parameter list andrestart the Administrator.

TIBCO Object Service Broker Messages Without Identifiers

Page 199: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 185

Messages beginning with: I

Identifier "%" exceeds maximum lengthof % charsSource: Rule Editor

Explanation: The identifier specified exceeds thepresent limit of 16 characters.

Action: Reduce the number of characters in theidentifier.

IDgen % must be Type I, Syntax B,Length 4Source: Table Definer

Explanation: You specified Y for the IDgen field,and therefore you are defining a TDS or IMPtable with an IDgen key. If you are alsodefining a parameter for the IMP table, itmust be an IDgen parameter. IDgen keys orparameters must be defined with a semantictype of I, a syntax of B, and a length of 4.

Action: Specify the key or parameter attributesaccordingly.

IDGEN must be % for % tableSource: Table Definer

Explanation: Idgen value is invalid.

Action: Specify Idgen value as indicated in themessage.

IDM table definition OK... <PF3> toSAVESource: Table Definer

Explanation: The table you have just defined haspassed all the edits.

Action: Press <PF3> to save it.

IDMS subschema "%" deletedSource: Tool for CA IDMS Data

Explanation: The indicated subschema definitionis no longer defined in Object Service Brokerbecause you confirmed your request todelete it.

Action: No action required.

IDMS subschema delete failed: %Source: Tool for CA IDMS Data

Explanation: The deletion of a subschemadefinition failed.

Action: Check the message log for moreinformation. If the cause cannot bedetermined and resolved, contact TIBCOSupport.

TIBCO Object Service Broker Messages Without Identifiers

Page 200: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

186 |

If flag is 'N', fields must be defined inthe same order as in ADABASSource: Adabas Definer

Explanation: Field ordering is invalid. ForRepeat Type of GRP and MU/Special field inGrp of N, the selected fields must be definedin exactly the same order as in ADABAS.

Action: Reorder the fields to match ADABAS filedefinition.

Ignore rightsSource: Manage Promotion Rights

Explanation: The promotion rights for thespecified object are held by another user.

Action: Check who is holding the rights for thespecified object and ask that the rights bereleased.

Ill formed name for % % of dynamicallycreated table %Source: TAM

Explanation: The name you specified for theindicated Field or Parameter does not meetthe criteria for a valid Object Service Brokername.

Action: Consult the Processing manual forinformation about the criteria a name mustmeet.

Image Area contains a "typed in" field atrow %Source: Screen and Report Painters

Explanation: The Image Area contains a newfield in the indicated row which was createdby typing it into the Image Area. This is notallowed.

Action: Blank out the typed in field in the ImageArea.

Import of IMS database definitionscancelledSource: Tool for IMS Data

Explanation: The IMS database import wascanceled by not confirming with <PF22>.

Action: No action required.

Import Server transaction end failedSource: TAM

Explanation: An open input file cannot be closed.

Action: Forward the message log to TIBCOSupport.

Import table "%" could not berepositioned to start of data setSource: TAM

Explanation: Hardware error.

Action: Contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 201: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 187

Improperly quoted string: "%"Source: Debugger Utility

Explanation: You have entered a DBGCOMcontaining an ill-formed string literal.

Action: Verify that the quotes delimiting, as wellas those inside, the string literal are balanced.

Improperly quoted string: "%"Source: Parse

Explanation: You have mismatched opening andclosing quotes in your input.

Action: Insert the closing quote, or delete theopening quote, as appropriate.

Improperly quoted string: "%"Source: Rule Editor

Explanation: The string indicated is notsurrounded by an appropriate number ofquotation marks.

Action: Insert the necessary quotation marks.

IMS database definitions importedSource: Tool for IMS Data

Explanation: The IMS database(s) was (were)imported into Object Service Broker.

Action: No action required.

IMS Gateway unavailable or requestabortedSource: TAM

Explanation: The IMS Gateway has not beenstarted, or it has failed.

Action: Confirm that the IMS Gateway and theObject Service Broker Data Object Broker arestarted and available. If this problempersists, contact TIBCO Support.

IMS offset cannot exceed segmentlength %Source: Table Definer

Explanation: When defining a subdivided field,you must keep the offset value within thesegment length.

Action: Calculate the segment length by addingthe offset and length of the last field. Correctthe highlighted offset value.

IMSGEN filename will be importedSource: Tool for IMS Data

Explanation: The database definitions will beimported into Object Service Broker.

Action: No action required.

In/out argument # of % routine "%" isnot a local variable or a field of a tableSource: Interpreter

Explanation: Some routines, such as TOKEN,modify their arguments. The argument mustbe a local variable or a field of a table for theroutine to be able to modify it.

Action: Adjust the arguments.

TIBCO Object Service Broker Messages Without Identifiers

Page 202: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

188 |

In OBJECTSET %, a % requires a %Source: Copy Defn/Data

Explanation: You have requested to copy anobject set and its children. However, theobject set references an object which requiresadditional information to identify.

Action: Specify the required information.

In rule %, at break event % %Source: Debugger Utility

Explanation: Your application has reached abreak event you specified. This providesfeedback.

Action: No action required.

INBOUND RESOURCE DETAILENTRY NOT DEFINED FOR PATHFROM node-nameSource: S6BTLADM-Resource Management

Explanation: You request the display of theInbound Peer connection on the ResourceDetail screen, the identified inbound Peerdoes not exist.

Action: Select a different node name or add theinbound Peer Detail entry by pressing PF5Add on the Resource Type List screen.

INCLUDE statement has appearedalreadySource: HLIPREPROCESSOR

Explanation: At least one $ INCLUDE HURONstatement has already appeared.

Action: Remove extra INCLUDE statements.

Including object set "%" results in acircular referenceSource: Object Set Definer

Explanation: You cannot include the indicatedobject set because to do so would result in acircular reference of object sets. The simplestexample of a circular reference is to haveobject set A contain object set B, and objectset B contain object set A.

Action: Remove the indicated object set from thelist of object sets in the current object set.

Incompatible STARTUP PATH forSTARTUP RULE; rule "%" not runSource: Session Manager

Explanation: The Startup Rule cannot be foundthrough the Search Path specified in the UserProfile. For example, if the startup rule is inthe local library, and the search path specifiessearching the installation and systemlibraries, the rule cannot be found. The ruleand search path combination is validated inthe profile when specified, but events thattake place after the information is specifiedcan cause the specification to become invalid.

Action: You can EXECUTE the startup rule if youstill want to run the rule.

If you want the rule to run at the next logon,change the SEARCH field or the STARTUPRULE field in the User Profile.

Incomplete fields information - checkPrint/Control Fields screenSource: Report Generator

Explanation: An error or errors were detected inthe specified screen.

Action: Check the indicated screen.

TIBCO Object Service Broker Messages Without Identifiers

Page 203: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 189

Incomplete function information -check Report Functions screenSource: Report Generator

Explanation: An error or errors were detected inthe specified screen.

Action: Check the indicated screen.

Incomplete relationship information -check Relate Tables screenSource: Report Generator

Explanation: An error or errors were detected inthe specified screen.

Action: Check the indicated screen.

Incomplete selection information -check Selection Criteria screenSource: Report Generator

Explanation: An error or errors were detected inthe specified screen.

Action: Check the indicated screen.

Incorrect % in definition of % "%" oftable "%"Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Incorrect number of arguments for "%"Source: Interpreter

Explanation: When the specified rule wasinvoked, the number of arguments supplieddid not match the number of argumentsdefined for the rule.

Action: Verify that the rule is correctly definedand invoked.

Incorrect number of arguments for rule"%"Source: Debugger Utility

Explanation: You must either supply all thearguments expected by a rule or none (youwill be prompted if arguments are required).

Action: Verify the number of argumentssupplied.

Incorrect number of arguments forshareable tool ";"Source: POSIX ON support for EMS

Explanation: The number of arguments suppliedto the shareable tool is not correct for thefunction being invoked.

Action: Correct the argument list for theshareable tool.

Incorrect value specified; must be in therange % to %Source: Batch Control Card

Explanation: Invalid entry in a numeric field.

Action: Correct the input. The message gives youthe valid range.

TIBCO Object Service Broker Messages Without Identifiers

Page 204: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

190 |

Index field must be either be defined as'K'ey or 'P'arameterSource: Table Definer

Explanation: Invalid line command entered. IMSIndex field must be either defined as aMetaStor key or as a data parameter.

Action: Enter line command K or P to define IMSIndex as key or parameter respectively.

Index field must be selected as 'K', or 'P'before viewing subfieldsSource: Table Definer

Explanation: VIEW failed. The desired baseindex field must be selected prior to viewingthe sub index fields.

Action: Choose the desired base index field asKey (K) or Parameter (P). Press <PF6> toview the sub index fields.

Indexing of library "%" completed;Press PF2 for LogsSource: Global Cross Ref. Search

Explanation: You asked to have a libraryindexed. This is done. You can see the Logsby pressing <PF2>.

Action: No further action is required.

Indirect % name not allowed in %Source: Rule Editor

Explanation: An inappropriate indirect referenceto a table or rule has been made.

Action: Check the Processing manual to seewhere indirect references are valid.

INDOUBT TRANSACTIONRETRIEVAL FAILEDSource: S6BTLADM - INDOUBT TRX

Explanation: When attempting to issue theindoubt transaction retrieval request to theData Object Broker, an error with thetransmission was detected.

Action: Review the joblog to determine if thereare additional messages which may helpidentify the cause of the problem. Retry yourrequest. If the problem persists contact thesupport center.

Infinite loop suspected, handler forexception "%" was executed more thanonce for rule call ("%" was exceptionsignalled)Source: Interpreter

Explanation: The statements comprising thehandler for a given exception were executedand caused the same exception to be raised.

Action: Restructure the exception handler so thatit does not raise the same exception.

INFO_TO_EXPORT must be "A", "D" or"O"Source: Unload/Load

Explanation: When loading a table, you can onlyuse the following option codes:

• A - Load the definition and all occurrences.

• D - Load the definition only.

• O - Load occurrences only.

Action: Correct the option code and try again.

TIBCO Object Service Broker Messages Without Identifiers

Page 205: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 191

Input "%"; expected "%"Source: Rule Editor

Explanation: There is a syntax error in your rule.The input token was found; the other tokenwas expected.

Action: Check the Processing manual for theproper syntax, or cancel the changes.

Input string too longSource: Builtin Routines

Explanation: The ADDRESS and ENDADDRESSarguments to $GETSTRING are such that theinput string or length cannot be read.

Action: Verify that ADDRESS andENDADDRESS are correct and that thestring in storage is not corrupt.

Insert access to % %( % ) by % deniedSource: Audit Log Message

Explanation: INSERT access to this object wasdenied. If the object is a parameterized table,the value of the first parameter for this tableinstance is indicated.

Action: Ask someone who has CONTROL accessto the object to provide INSERT access.

Insert access to TABLE %( % ) by %Source: Audit Log Message

Explanation: The user has inserted data into thegiven table with the specified parameter.

Action: No action required.

INSERT failed: table "%" has max ##rows allowedSource: Screen Server

Explanation: No more occurrences can beinserted.

The screen table has reached its allowedmaximum number of occurrences.

Action: Do one of the following:

• Using the Screen Table Painter, increasethe number of occurrences allowed for thescreen table.

• Delete another occurrence beforeattempting this insertion.

• Substitute the insert with a replace.

INSERT failed for table "%" - rowalready existsSource: Screen Server

Explanation: The maximum number ofoccurrences allowed for this screen table isone. The rule has tried to insert more thanthis maximum.

Action: Using the Screen Table Painter, checkwhy the screen table was specified to haveonly one occurrence. Increase this number ifpossible.

TIBCO Object Service Broker Messages Without Identifiers

Page 206: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

192 |

Insert not generated, table % missingDB2 NOTNULL fieldsSource: Static SQL for DB2 Gateway

Explanation: Attempt to generate Static SQL fora DB2 INSERT failed because a DB2 fielddefined as NOT NULL is not part of theMetaStor DB2 table definition. An attempt todo this insert would fail in DB2.

Action: Select all fields marked NOT NULL aspart of the MetaStor DB2 table definition orredefine the DB2 table in DB2 to remove theNOT NULL restriction.

Insertfail encountered for % "%" Fix=%:%Source: Promotions Bind Tools

Explanation: An error occurred inserting thespecified row into @PROMUNBOUNDOBJSand the @PROMUNBINDOBJS toolterminated.

Action: Resolve the error specified and run@PROMBINDOBJS before re-running@PROMUNBINDOBJS.

INSERTFAIL on loading %Source: Unload/Load

Explanation: When inserting table occurrences,LOAD encountered an error that may becaused by duplicate primary key entries.

Action: Delete the duplicate occurrences in thetarget system and load the object again.

Insertion of selected fields cancelledSource: Report Generator

Explanation: The selected fields are not insertedbecause you did not place the cursor in anarea where fields can be inserted.

Action: If you still want to select the previous setof fields, press the RECALL function key andthen place the cursor in a valid area (PRINT,SORT, BREAK, or ACROSS) before you pressENTER.

If you want to select a different set of fields,type an alphanumeric (0-9, A-Z) next to thefield names, then place the cursor in a validarea (PRINT, SORT, BREAK, or ACROSS)before you press ENTER.

Insertion of selected functions andfields cancelledSource: Report Generator

Explanation: The selected function-field pairs arenot inserted because you did not place thecursor in an area where the pairs can beinserted.

Action: If you want to select the previousfunction-field pairs, press the RECALLfunction key and then place the cursor in thesummary/break area before you press<ENTER>.

If you want to select a different set offunction-field pairs, for each pair, type thesame alphanumeric (0-9, A-Z) next to thefunction name and the field name, then placethe cursor in the summary/break area beforeyou press <ENTER>.

TIBCO Object Service Broker Messages Without Identifiers

Page 207: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 193

INSTANCE SELECT function is forPARAMETERIZED TABLES onlySource: Unload

Explanation: In the UNLOAD first context, youhave requested the INSTANCE SELECTfunction for a table entry where the table isnot parameterized.

Action: Position the cursor on a parameterizedtable entry to use the INSTANCE SELECTfunction. The #PARMS column of the objectlist display will indicate which tables areparameterized.

Instance selection CANCELLEDSource: Unload

Explanation: You had requested to specify whichdata instances of a parameterized table tounload via the INSTANCE SELECT function.However you requested to CANCEL thechanges you made to the specification. Thestate of the selection list before you requestedINSTANCES select will be used to determinewhich instances to unload.

Action: You can request the INSTANCE SELECTfunction again to double check whichinstances will get unloaded should youcomplete the unload request (as opposed tocanceling it).

INSTANCES function is for TABLESwith STORED DATA onlySource: Unload

Explanation: You have requested to specifywhich instances for a table to unload,however the table on the same row as thecursor is not a table which has stored data init (e.g., it is a TEM, SCR, RPT table).

Action: You cannot unload data from anonpermanent table. Recheck the name.

Insufficient memory to run transactionSource: Session Manager

Explanation: The maximum amount of storageavailable for an Object Service Broker user torun transactions has been exceeded.

Action: Ensure your application does not use anexcessive amount of storage. Possible sourcesof problems may be:

• Inserting a large number of occurrencesinto a temporary table or screen table

• Running complex reports

• Accessing a large number of tables

• Nesting transactions

An Object Service Broker systemadministrator can limit the maximumamount of storage available to an ObjectService Broker user. Refer to the Parametersmanual for information about theTRANMEMMAX Execution Environmentparameter.

Insufficient room to ADD a field hereSource: Screen Definer

Explanation: In the Screen Table Painter, yourequested adding a field in a location wherethe space is insufficient to add a field.

Action: You can do any of the following to gainsufficient space to add a field:

• Remove some of the existing fields.

• Type over some literal text with blanks.

• Add the field in another location.

TIBCO Object Service Broker Messages Without Identifiers

Page 208: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

194 |

Insufficient room to PASTE the fieldSource: Screen Definer

Explanation: You have pressed <PF17> but thereis no room to paste the field.

Action: Paste the field elsewhere, or move theother fields to allow the field to be pastedwhere first indicated.

Insufficient room to PASTE the fieldSource: Screen Definer

Explanation: You pressed <PF17> but there isinsufficient room, as the pasted field wouldoverlap the physical boundaries of theterminal screen.

Action: Paste the field elsewhere.

Insufficient security clearance to %change#%Source: Promotion

Explanation: You did not have sufficient securityclearance to perform the specified actionagainst the specified change.

Action: Ask your Security Administrator orPromotion Administrator for the requiredsecurity clearance.

Insufficient security clearance to %defn of % %Source: Promotion

Explanation: You did not have sufficient securityclearance to perform the specified actionagainst the definition of the specified object.

Action: Ask your Security Administrator or theowner of the object for the required securityclearance. Then apply the change again.

Insufficient security clearance to % occsof table %Source: Promotion

Explanation: You did not have sufficient securityclearance to perform the specified actionagainst the occurrences of the specified table.

Action: Ask your Security Administrator or theowner of the object for the required securityclearance. Then apply the change again.

Insufficient security clearance to access% %Source: Unload/Load

Explanation: You do not have security clearanceto access the specified object.

Action: Ask your security administrator for therequired security clearance.

Insufficient security clearance to create% table %Source: Promotion

Explanation: You did not have sufficient securityclearance to create the specified table.

Action: Ask your Security Administrator or theowner of the base table for the requiredsecurity clearance. Then apply the changeagain.

Insufficient security clearance to runthis utilitySource: Promotion

Explanation: This utility can be run by a selectedgroup of users only and you are not amember of that group.

Action: Contact your DBA to include you in thegroup which can run this utility.

TIBCO Object Service Broker Messages Without Identifiers

Page 209: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 195

Insufficient space for COPY:<PF3>/COPY PARTIAL or<PF12>/CANCELSource: Screen Definer

Explanation: In the Screen Table Painter, youwanted to load a whole table; however, thescreen table does not have sufficient space.

Action: Do one of the following:

• Cancel the request by pressing <PF12>.

• Copy some of the table by pressing <PF3>.

Insufficient space to return all remotelog messagesSource: TAM

Explanation: During a distributed data access, acondition occurred at the remote node thatcaused error or informational messages to bewritten to the system log on the remotesystem. When the system attempted totransfer these messages back to the localsystem log, there was not enough space inthe peer-to-peer message buffer to contain allof them. The usual reason for a large remotelog is the failure of a remote trigger rule andthe dumping of its local variables, activetables, and so on. As well, log informationshares the buffer with any table occurrencesbeing returned, so a number of successfuloperations within a FORALL, followed by afailure may not leave room for all themessages.

Action: Investigate the reason for the failure onthe remote system. It may be necessary toreproduce the problem by accessing theremote table from a rule on the remotesystem, and examining the log on thatsystem.

Insufficient storage for DISPLAY &TRANSFERCALLSource: Screen Server

Explanation: Not enough session storage isavailable to contain the definition and datafor the current screen.

Action: Decrease the amount of storage requiredby either simplifying the definition of thescreen or having fewer occurrences in thecomponent screen tables.

Integrity Failure: Cannot order joincursor %Source: Host Language Interface

Explanation: Join cursors reference many tables.To sort outcome, one would need to create astorage table on the fly. The preprocessorcannot create one.

Action: Define a table to store outcomes, declarea cursor for the table by specifying orderclause, and use this cursor to retrieve anordered selection.

Integrity Failure: Cannot update joincursor %Source: Host Language Interface

Explanation: Join type cursors cannot updatetables referenced in the join.

Action: Use some other ways to update the tablesreferenced in the join.

TIBCO Object Service Broker Messages Without Identifiers

Page 210: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

196 |

Integrityfail:%Source: Table Editor

Explanation: The promotion rights on thecurrent table cannot be determined, probablyas a result of locking. Therefore, the specifiedoperation, which requires changes to thetable, cannot be performed.

Action: Try the operation again later.

Integrityfail on %; no printing doneSource: Print Table

Explanation: The table cannot be printed becausean INTEGRITYFAIL exception was raised.

Action: Check that you have access to that table.

Intermediate COMMIT not allowedSource: TAM

Explanation: COMMIT operations for certainexternal tables cannot be followed by anyother table or transaction operator in thesame transaction. Refer to the appropriateObject Service Broker documentation for therules governing each external table type.

Action: Remove any request for an intermediateCOMMIT.

Intermediate ROLLBACK not allowedSource: TAM

Explanation: ROLLBACK operations for certainexternal table types cannot be followed byany other table or transaction operator in thesame transaction. Refer to the appropriateObject Service Broker documentation for therules governing each external table type.

Action: Remove any request for an intermediateROLLBACK.

Internal editor error detected; press PF2for moreSource: Rule Editor

Explanation: This is a first-level message for aninternal editor error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message appeared.

Internal error; contact the CustomerSupport CenterSource: Table Editor

Explanation: The Table Editor has an unexpectederror situation.

Action: Contact TIBCO Support.

Internal error in $LISTDSN - IGGCSI00parmlist errorSource: Builtin Routines

Explanation: This is an internal error in the$LISTDSN built-in routine.

Action: Contact TIBCO Support for assistance.

Internal error in $LISTDSN - IGGCSI00parmlist pointer was zeroSource: Builtin Routines

Explanation: This is an internal error in the$LISTDSN built-in routine.

Action: Contact TIBCO Support for assistance.

TIBCO Object Service Broker Messages Without Identifiers

Page 211: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 197

Internal error obtaining definition fortable "%"Source: TAM

Explanation: The program for the tabledefinition retrieval is illegally called.

Action: This is an internal error; contact TIBCOSupport.

Internal occurrence length error fortable "%"Source: TAM

Explanation: The occurrence length in variablelength format is longer than the dictionaryrecord length in fixed length format.

Action: Change all the field lengths in thedefinition of the table, and ensure that thetotal field length matches the occurrencelength.

Internal parameter errorSource: External Gateway Logon

Explanation: One of the parameters on theconnect of the gateway/server session wasfound to be in error.

Action: Check that libraries of compatibleversions were used, and that the parametersyou provided were correct.

Internal report server error: attemptingto read a file that is not open for INPUTprocessingSource: Report Server

Explanation: The Report Server detected aninconsistent server action.

Action: Contact TIBCO Support.

Internal report server error: attemptingto write to a file that is not open forOUTPUT processingSource: Report Server

Explanation: The Report Server detected aninconsistent server action.

Action: Contact TIBCO Support.

Internal report server error: Invalidsequence of report blocks whenprinting report "%"Source: Report Server

Explanation: The Report Server detected aninvalid state while producing a report page.

Action: Contact TIBCO Support.

Internal report server error: Invalidsource opcode for a report field. Reporttable is "%"Source: Report Server

Explanation: The Report Server detected an errorin the data structures that describe a report.

Action: Contact TIBCO Support.

Internal report server error: Invalidsource opcode for report field "%" ofreport table "%"Source: Report Server

Explanation: An internal Report Server error wasdetected while the server was evaluating aderived report field.

Action: Contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 212: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

198 |

Internal report server error: recursionstack overflowSource: Report Server

Explanation: An error was detected during thebuilding of the definition of a report.

Action: Contact TIBCO Support.

Internal report server error: reportfunction accumulator has an invalidsyntaxSource: Report Server

Explanation: An error was detected in the datastructure of the Report Server.

Action: Contact TIBCO Support.

Internal report server error: reportfunction value for derived field "%" of"%" was not foundSource: Report Server

Explanation: Access to a computed reportfunction failed during report pageformatting.

Action: Contact TIBCO Support.

Invalid "%" specified- must be positiveSource: Report Definer

Explanation: This row or col is invalid. It shouldbe positive rather than negative.

Action: Change the value to a positive number.

Invalid "%" specified - must be numericor "*"Source: Report Definer

Explanation: Page Occ and Page Across valuesmust be numeric or an asterisk ("*"). Anumber indicates the number of occurrencesor across repetitions to allow per page. Anasterisk indicates that as many occurrencesor across repetitions as will fit on a page areto be allowed.

Action: Correct the Page Occ or Page Acrossvalue.

Invalid "%" specifiedSource: Report Definer

Explanation: An invalid row or column wasspecified.

Action: Row and column values must be >= 0.

Invalid "Attribute Name" in$SETRPTATTRIBUTESource: Report Server

Explanation: The second parameter of$SETRPTATTRIBUTE is not one of:

• IMMEDIATE (Send report directly tooutput)

• OCCLIMIT (Limit occurrences used togenerate report)

• PAGELENGTH (Set new physical pagelength)

• PAGEWIDTH (Set new physical pagewidth)

• EJECT (Control page eject if more than 1report in transaction)

TIBCO Object Service Broker Messages Without Identifiers

Page 213: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 199

• PAGENUMBER (Set new starting pagenumber).

Action: Correct second parameter to match oneof the listed values.

Invalid %; must be between 0 and 255(inclusive)Source: Security

Explanation: A Security Administrator specifiedan invalid TDS segment number. Validnumbers are in the range 0 to 255, but thenumber of segments being used areinstallation dependent.

Action: Change the value to a valid one.

Invalid access to table "%". Null parm"%" not allowedSource: TAM

Explanation: The user tried to access a table witha null parameter value.

Action: Use a non-null parameter value.

Invalid access to table "%": duplicatereference in parameters list andWHERE clauseSource: TAM

Explanation: For the same request, a parameterspecified in a WHERE clause is also specifiedin the table reference.

Action: Remove the parameter reference in eitherthe WHERE clause or the table reference.

Invalid access type for table "%" ofVSAM % "%"Source: TAM

Explanation: The specification in the TYPE fieldof the table definition is not one of thefollowing VSAM access types:

• KSDS

• ESDS

• RRDS

The variables in the message, from left toright, are as follows:

1. The name of the table

2. Either "file" or "DDNAME"

3. The name of the file or the DDNAME

Action: Change the TYPE value in the tabledefinition to one of the allowed values.

Invalid Action %Source: Unload/Load

Explanation: The action must be one of IS or IRfor an object definition, or one of IS, IR, MI, orMR for table data.

Action: Correct the action.

Invalid action requestedSource: Static SQL for DB2 Gateway

Explanation: The action specified is notsupported. The following line commands aresupported:

• G - Generate Static SQL for a table.

• R - Remove Static SQL association for thetable.

Action: Change the line command to G or R, orremove the action.

TIBCO Object Service Broker Messages Without Identifiers

Page 214: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

200 |

Invalid address specified in call to %.ADDRESS must be less than or equal toENDADDRESSSource: Builtin Routines

Explanation: The ENDADDRESS argument to$GETSTRING or $SETSTRING is the addressjust past valid storage and is used to protectagainst reading or writing to invalid storage.The ADDRESS argument is the storageaddress where you will read or write the nextstring, and so it must have a value less thanor equal to ENDADDRESS.

Action: Correct ADDRESS and/orENDADDRESS so that they refer to the sameblock of storage and ADDRESS is less than orequal to ENDADDRESS.

Invalid argument "%" -->#<-- for "%"Source: Builtin Routines

Explanation: Argument # of the $SETTITLE toolcannot take the value zero (0).

Action: Supply a valid argument.

Invalid argument "%" -->%<-- for "%"Source: Builtin Routines

Explanation: One of the following argumentsdoes not meet specifications:

• media of $RESETPRINT and $SETPRINT

• clear_title_yn of $SETPRINT

• title_yn of $BLANKPAGE

• just of $PRINTFIELD

• numbering_yn of $TOCPUT

Action: Supply a valid argument.

Invalid attribute "%" for"$SETATTRIBUTE"Source: Builtin Routines

Explanation: You specified an invalid attribute asa parameter to the $SETATTRIBUTE tool.Valid values are:

• H (Highlight)

• P (Protect)

• V (Visible)

• N (Numeric)

• D (Detectable)

• B (Blinking)

• R (Reverse video)

• U (Underline).

Action: Change the utility call to specify one ofthe valid values.

Invalid attribute for a fieldSource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Invalid attribute for report function "%"Source: Report Server

Explanation: An internal Report Server error wasdetected in the definition of a report function.

Action: Contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 215: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 201

Invalid Category; press <PF1> for HelpSource: Promotion

Explanation: The category is the reason for thechange request. Valid categories are listed inthe Help.

Action: Fill in a valid category.

Invalid CLASSIFICATION "%"; mustbe 1..7Source: Security

Explanation: You have specified an invalidclassification for the object whose AccessControl List you are updating.

Action: You must specify the classification to be anumber between 1 and 7.

Invalid color "%" for "$SETCOLOUR"Source: Builtin Routines

Explanation: You specified an invalid color forthe utility $SETCOLOUR. Valid colors arethose defined in the table @COLOURS.

Action: Change the invalid color to one that ispresent in the table @COLOURS.

Invalid color specified for field "%.%"Source: Screen Server

Explanation: The color code for the indicatedfield is not one of the valid codes defined inthe table @COLOURS.

Action: Change the value [email protected] [email protected] to avalid color code.

Invalid color type "%" for"$SETCOLOUR"Source: Builtin Routines

Explanation: You specified an invalid color typefor the utility $SETCOLOUR. Valid types areF (foreground) and B (background).

Action: Specify the color type as F or B.

Invalid column specified forCOPY/APPEND resultsSource: Report Definer

Explanation: The column indicated as the targetposition for the results of a COPY/APPENDcommand cannot contain the copied fieldsand headings without causing an overlapcondition, or exceeding the maximum reportwidth.

Action: Do one of the following:

• Reposition the cursor to a row and columnthat will not cause a copied field to overlapexisting report fields or exceed themaximum report width.

• Use the keyword NONAMES after theAPPEND command to indicate that noheadings are to be copied.

Invalid column specified for field"%.%"Source: Screen Server

Explanation: The column number that you gaveas an argument to the SETCURSOR_POS tooldoes not fall within the number.

Action: Change the column number to fall withinthe range of columns in the specified screenfield. The range begins with 1 and extends tothe length of the field.

TIBCO Object Service Broker Messages Without Identifiers

Page 216: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

202 |

Invalid combination of arguments for";": OFFSET "#" + LENGTH "#" >LENGTH(STRING) "#"Source: Builtin Routines

Explanation: Self-explanatory.

Action: Adjust the arguments so as to satisfy thestated constraint.

Invalid combination ofscreen/table/field specified for "%"Source: Builtin Routines

Explanation: Either the screen, screen table, orscreen field name has not been specified forthe indicated utility.

Action: Make sure that the screen, screen table,and screen field names are specified in theutility call.

Invalid command: "%"; Use "P"-parameter "K"-key "S"-selectSource: Table Definer

Explanation: The indicated command is invalid.Use one of the following line commands:

• P (Parameter)

• K (Primary Key)

• S (Selected Field)

Action: Change the line command to a validcommand.

Invalid command: "%"; use "S" to selectfieldsSource: Table Definer

Explanation: The indicated command is invalid;you can use only S to select fields.

Action: Change the invalid command to S if youwant to select that field; otherwise, removethe invalid command.

Invalid command: %Source: Character-based Text Editor

Explanation: You have entered an invalidcommand.

Action: Enter a valid command. If necessarypress <PF1> to see a list of the commands.

Invalid command for this object typeSource: Global Cross Ref. Search

Explanation: An invalid primary command wasentered.

Action: Correct or remove the command.

Invalid constant : "%"Source: Report Generator

Explanation: The indicated parameter value is aninvalid constant.

Action: Correct the parameter value.

TIBCO Object Service Broker Messages Without Identifiers

Page 217: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 203

Invalid CURRENT GROUP: "%"Source: Security

Explanation: You specified an invalid currentgroup in the user profile screen.

Action: You can use the MEMBERSHIPS functionto determine valid current groups, or changethe CURRENT GROUP field to null so thatyou are not operating out of any group.

INVALID CURSOR POSITION FORCOMMAND SELECTIONSource: S6BTLADM - OPERATOR FUNCT

Explanation: The Administrator processing wasunable to determine which operator requestyou wished to invoke.

Action: Reposition the cursor using the tab keyand try your request again.

Invalid D/C indicator "%" - must be"D"ebit, "C"redit, or "_"Source: Report Generator

Explanation: The specified indicator is invalid. Itmust be one of the following:

• D - Debit

• C - Credit

• _ - no indicator.

Action: Change the D/C indicator to a validcharacter.

Invalid data set %Source: General

Explanation: You specified an invalid data setname in the Rule Printer utility.

Action: Correct the data set name.

Invalid data value in syntax W field -DBCS delimiters are not pairedSource: Interpreter

Explanation: The DBCS delimiters are notpaired.

Action: Supply missing DBCS delimiter.Alternatively, remove unpaired one.

Invalid data value in syntax W field -odd number of bytes between DBCSdelimitersSource: Interpreter

Explanation: The value in the syntax W fieldyields an odd number of bytes between theDBCS delimiters.

Action: Verify the number of bytes between theDBCS delimiters.

Invalid data value in Unicode field -Length field incorrectSource: Interpreter

Explanation: Either the length value for aUnicode field is not even or the length is twoand the first two bytes contain the first half ofa surrogate pair.

Action: Correct the input Unicode data.

Invalid database name; press <PF4> forDB NAMESSource: Table Definer

Explanation: The IMS database name that youentered is not defined or loaded into theMetaStor.

Action: Press <PF4> for a list of valid IMSdatabase names and select one from the list.

TIBCO Object Service Broker Messages Without Identifiers

Page 218: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

204 |

Invalid date: %; expected format: %Source: Table Editor

Explanation: You specified a date value that doesnot conform to the expected date format.

Action: Change your date value to the indicatedexpected format and try again.

Invalid date display mask: "%"Source: Report Generator

Explanation: The indicated date display mask isinvalid.

Action: Correct the date display mask. You canrefer to the Reporting manual for adescription of valid date display masks.

Invalid date formatSource: Character-based Text Editor

Explanation: The format you have used for the.date command is unsuitable for the tool$TRXDATE.

Action: Refer to $CREATE_DATE in theShareable Tools manual for the correct syntaxto be used with this rule.

Invalid date in GO TO datespecificationSource: Session Manager

Explanation: You have specified a date whichyou wish to go to in the Appointment Book;however, there is no such date.

Action: Change the date to a valid data and press<Enter> again.

Invalid DBCS field - odd number ofbytesSource: Builtin Routines

Explanation: The field in error is supposed to bea pure double-byte character set (DBCS)field, where each character is represented by2 bytes.

Action: Correct the field so that it contains aneven number of bytes, representing a DBCSstring.

Invalid DBCS subfield - odd number ofbytesSource: Builtin Routines

Explanation: The specified text contains aninvalid DBCS subfield. A DBCS subfieldrepresents a string of DBCS characters withina mixed string. Each DBCS character isrepresented by 2 bytes so the length of theDBCS subfield must be a multiple of 2.

Action: Correct the DBCS subfield (the databetween the "Shift Out" and "Shift In"characters) so that it contains an evennumber of bytes.

Invalid DBCS subfield - unmatchedSO/SISource: Builtin Routines

Explanation: A string contains one of thecharacters SO or SI (Shift Out or Shift In)without the other. DBCS subfields must startwith an SO and end with an SI.

Action: Add a "Shift Out" or "Shift In" characterso that all DBCS subfields in the string arevalid.

TIBCO Object Service Broker Messages Without Identifiers

Page 219: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 205

Invalid DDname: "%"Source: Report Generator

Explanation: The DDname that you provided isnot a valid Object Service Broker identifier.

Action: Enter a valid Object Service Brokeridentifier. See the Object Service BrokerDocumentation for more information aboutObject Service Broker identifiers.

Invalid decimal length.Source: Table Definer

Explanation: You did not enter a positivenumber in the MetaStor decimal field toindicate a decimal length.

Action: Enter a positive integer value in thedecimal field.

Invalid default Security Group: "%"Source: Security

Explanation: You referred to an invalid defaultsecurity group in the User Profile screen.

Action: You can use the MEMBERSHIPS functionto determine valid default security groupsfor the profile.

Invalid derived defn request:"%" is notdefined as DERIVEDSource: Report Definer

Explanation: A derived field definition wasrequested for a non-derived field.

Action: Position the cursor on a derived fieldbefore requesting derived field definition.

Invalid display mask defined for field"%.%"Source: Screen Server

Explanation: An invalid display mask has beenspecified for the indicated screen field.

Action: Correct the display mask specificationusing the Screen Definer and Screen TablePainter.

INVALID DUMP IDENTIFICATIONITEM SPECIFIEDSource: S6BTLADM - DIAGNOSTIC DUMP

Explanation: The item number you input torequest a diagnostic dump is invalid.

Action: Correct your input and try your requestagain.

Invalid encoding "%" specified in call to%. Use ASCII, UTF-8, UTF-16BE, UTF-16LE, UTF-32BE, or UTF-32LESource: Builtin Routines

Explanation: The ENCODING argument for$GETSTRING or $SETSTRING does not haveone of the supported values.

Action: Use one of the supported values.

Invalid end of session actionSource: Builtin Routines

Explanation: Action parameter for$SETSESSIONEND is not a valid action to beperformed when the user's session ends.Valid actions are START, XTCL, FORMAT,SWITCH, RETCODE, RC, and ABEND.

Action: Change the call to $SETSESSIONEND topass a valid session end action.

TIBCO Object Service Broker Messages Without Identifiers

Page 220: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

206 |

Invalid exception name for a SIGNALstatementSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Invalid field lengthSource: Table Definer

Explanation: You must enter a positive integerfor the field length.

Action: Type a positive integer in the LEN field.

Invalid field name: %Source: Table Editor

Explanation: You specified an invalid field name.

Action: Check the field name that you specifiedand try the procedure again.

Invalid field number found indynamically created table %Source: TAM

Explanation: @DOFFIELDS.NUMBER does notcorrespond to the field's position in the table.

Action: Set @DOFFIELDS.NUMBER tocorrespond to the occurrence number [email protected].

Invalid field of %: %Source: DEFINE_OBJLIST Tool

Explanation: The indicated field is not a validfield of the indicated table.

Action: Check the table definition and specify avalid field name.

Invalid field specified forCOPY/APPEND of report table "%"Source: Report Definer

Explanation: A copy of a table.field has beenrequested, but the field specification isinvalid.

Action: Specifying only a table in a COPY or anAPPEND operation will display a promptlist of all available fields on the table. Therequired field can then be selected.

Invalid field syntax for ORDERING -field "%.%"Source: Screen Server

Explanation: The indicated field is syntax F(floating point), which is invalid for orderinga screen table.

Action: Either change the syntax of the screenfield or do not try to order occurrences basedon the indicated field.

Invalid filter keySource: Builtin Routines

Explanation: The filter key supplied for the$LISTDSN is not allowed.

Action: Check the Shareable Tools manual forvalid formats.

TIBCO Object Service Broker Messages Without Identifiers

Page 221: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 207

Invalid footnote definition in screentable "%" within Screen "%"Source: Screen Server

Explanation: One of the following occurred:

1. The footnote text exceeds the number ofrows specified for the occurrence.

2. Footnotes have been specified but notcreated.

Action: Correct the screen definition by using theScreen Table Painter.

INVALID FUNCTION KEY HIT, ORFUNCTION RESTRICTEDSource: S6BTLADM - COMMON MESSAGES

Explanation: The function key you pressed iseither invalid for this screen or providesaccess to a function for which you do nothave security clearance.

Action: Verify you pressed the key you intended,contact your security administrator toarrange the appropriate external security.Refer to the Security manual for furtherdetails.

Invalid hexadecimal numberSource: Table Editor

Explanation: You assigned an invalidhexadecimal number to a Unicode or rawdata field of an occurrence.

Action: Assign a valid hexadecimal number tothe field.

Invalid IDMS table: %Source: Tool for CA IDMS Data

Explanation: The table you selected from the listis not an IDMS table. The table type waschanged by nonstandard methods.

Action: Try to find out why the table type waschanged. If it should not have been changed,edit the TABLES table and change the tabletype back to IDM. You can then use the TableDefiner to see if the table definition was alsochanged, and change it back, if necessary.

Invalid IMS lengthSource: Table Definer

Explanation: The value in the IMS length field isnot a positive value.

Action: Enter a positive integer value that doesnot exceed the length of the current segment.

Invalid IMS offsetSource: Table Definer

Explanation: The IMS offset field has a negativeor null value.

Action: Enter a positive value in the offset field,but ensure that the offset value does notexceed the length of the segment.

Invalid indirect field name, %Source: Interpreter

Explanation: The evaluation of an indirectreference to a field did not yield a name.

Action: Verify that indirect references to fieldsresolve to names.

TIBCO Object Service Broker Messages Without Identifiers

Page 222: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

208 |

Invalid indirect rule name, %Source: Interpreter

Explanation: The evaluation of an indirectreference did not produce a name.

Action: Verify the expression for the indirectreference.

Invalid indirect table name, %Source: Interpreter

Explanation: The evaluation of an indirectreference to a table has not yielded a name.

Action: Verify that indirect references to tablesresolve to names.

Invalid input: % is not a text table nor avalid parameterSource: Character-based Text Editor

Explanation: TED was executed with an inputargument that is neither the name of a texttable nor a parameter of @TEXT.

Action: Correct the input argument.

Invalid Key - % not definedSource: Adabas Definer

Explanation: You have pressed a PF key that isnot defined.

Action: Use <PF1> for a list of valid PF keys.

Invalid key type "%" - must be"P"rimarySource: Table Definer

Explanation: The indicated key type is invalid. Itmust be either P (primary key) or S(secondary key). Since the Table Definer doesnot create secondary indexes, you can specifyonly P.

Action: Do one of the following:

• Remove the invalid key type.

• Change the invalid key type to P.

• Remove the invalid key type and build asecondary index by using the SIXBUILDtool. See the Shareable Tools manual formore information.

Invalid LENGTH and/or COL specified- max report width is %Source: Report Definer

Explanation: The maximum width that a reportfield can be defined is indicated.

Action: Ensure that each report field does notextend beyond the maximum width.

Invalid length specification; must beeither F or VSource: Batch Control Card

Explanation: You have specified an invalidlength specification for the input file.

Action: Specify whether the input file is fixed (F)or variable (V) length.

TIBCO Object Service Broker Messages Without Identifiers

Page 223: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 209

Invalid length specified; must be in therange 1 to 3915Source: Batch Control Card

Explanation: You specified an incorrect fieldlength.

Action: Correct the input. The field length mustbe in the range of 1 to 254 bytes.

Invalid library name: "%"Source: Define Library

Explanation: You tried to define a Library, butthe name you provided is not a valid libraryidentifier (e.g., the identifier has internalblanks, starts with a number or an invalidcharacter, etc.).

Action: Specify a library name that is up to 8characters in length, has no internal blanksand no invalid characters.

Invalid limit : "%"Source: Report Generator

Explanation: You specified an invalid value forthe record limit.

Action: Enter a positive number for the limit.

Invalid line command: %Source: Table Editor

Explanation: You entered an invalid linecommand.

Action: Enter a valid line command. Press <PF1>for a list of valid line commands.

Invalid line command: Only D-Deleteline command is allowedSource: Table Definer

Explanation: You have specified an invalid linecommand to be operated on the locationparameter.

Action: Specify only the D line command todelete the location parameter.

Invalid line command "%"Source: Promotion

Explanation: The specified character is an invalidline command.

Action: Remove the line command or change it toa valid command. You can get a list of validline commands by pressing <PF1> for Help.

Invalid line commandSource: Character-based Text Editor

Explanation: You entered a character that is not acommand in the line command position.

Action: Remove or correct the invalid character.Press <PF1> for a list of valid line commands.

Invalid line commandSource: Promotion

Explanation: The line command you entered isnot valid on this screen. Valid line commandsare listed at the bottom of the screen.

Action: Use a valid line command.

TIBCO Object Service Broker Messages Without Identifiers

Page 224: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

210 |

Invalid line specification: % - a numberis requiredSource: Character-based Text Editor

Explanation: You issued the script command .tmor .bm to specify the number of lines for thetop or bottom margin but you did not specifya valid number.

Action: Specify a valid number for the top orbottom margin lines.

Invalid location %Source: Copy Definition

Explanation: Informs you that the location isinvalid.

Action: No action required.

Invalid location %Source: Copy Defn/Data

Explanation: You have specified a location whichdoes not exist.

Action: Remove or correct the locationspecification.

Invalid logical: % for field %Source: Table Editor

Explanation: You assigned an invalid logicalvalue to a logical field of an occurrence.

Action: Assign a valid logical value (Y or N) tothe indicated field.

Invalid logical: %Source: Table Editor

Explanation: You assigned an invalid logicalvalue to a logical field of an occurrence.

Action: Assign a valid logical value (Y or N) tothat field.

Invalid logical value (must be "Y" or"N")Source: Screen Definer

Explanation: You have not entered either Y or Ninto the SCROLL prompt in the screen tabledefinition.

Action: Enter either Y or N.

Invalid message idSource: Screen Server

Explanation: This is an internal error in thescreen server.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log andan exact description of what actions werebeing performed when this message wasgenerated.

Invalid month for calendarSource: Session Manager

Explanation: You typed over the month namewith an invalid month name.

Action: Enter a valid month name.

TIBCO Object Service Broker Messages Without Identifiers

Page 225: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 211

Invalid name: "%"Source: Object Set Definer

Explanation: The indicated name is not a validObject Service Broker object name.

Action: Change the name so it is valid. A validname is any character string up to 16characters beginning with a letter (A-Z) or aspecial character ($ or #), and continuingwith more letters, special characters, digits(0-9), or underscores (_).

Invalid NEW_STATE "%" in "%"Source: Parse

Explanation: The grammar definition of % isinvalid as it contains a transition to a non-existent state.

Action: If the grammar was supplied with ObjectService Broker, contact TIBCO Support.

If the grammar is user-defined, examine thegrammar and either add the state or removethe attempted transition to that state.

Invalid number: "%"Source: Rule Editor

Explanation: An invalid numeric constant hasbeen detected (possibly one too large torepresent).

Action: Check the Processing manual todetermine the form of valid numericconstants.

Invalid number: % for field %Source: Table Editor

Explanation: You assigned an invalid value, suchas a string, to a numeric field of anoccurrence.

Action: Assign a numeric value to the indicatedfield.

Invalid number: %Source: Table Editor

Explanation: You assigned an invalid value, suchas a string, to a numeric field of anoccurrence.

Action: Assign a numeric value to that field.

Invalid number of copies %: must befrom 1 to 255Source: Security

Explanation: In the User Profile screen, youspecified an invalid number of copies for theprint parameters; the number must be in therange 1 to 255.

Action: Change the number of copies to a validnumber.

Invalid number of parameters suppliedfor table "%"Source: Interpreter

Explanation: The number of parameterssupplied for a table access does not match thenumber of parameters defined for the table.

Action: Check the table definition for theparameters and based on this informationcorrect the number of parameters that youare supplying.

TIBCO Object Service Broker Messages Without Identifiers

Page 226: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

212 |

Invalid number of parameters suppliedfor table "%"Source: TAM

Explanation: The parameters specified in a tablerequest (INSERT, GET, REPLACE, DELETE,or FORALL), and/or in an accompanyingWHERE clause, are different from theparameters in the definition of the table.

Action: Make sure that all parameters in the tabledefinition are specified in a table request,and/or the parameter names in theaccompanying WHERE clause are specifiedcorrectly.

Invalid object code in detranslator rule"%" at offset %Source: Rule Editor

Explanation: Internal translator error.

The message log will contain a more detailederror message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

Invalid object commandSource: Object Manager

Explanation: You entered a line command that isnot listed at the bottom of the screen.

Action: Correct the line command.

Invalid object specification "%"Source: Debugger Utility

Explanation: You have specified a break eventusing either the primary command area orthe break event control area. You may havemisspelled the name of the object qualifyingthe break event to be set.

Action: Verify the spelling of the object.

Invalid OBJECT_TYPE % - use PF1 keyto select valid typesSource: Global Cross Ref. Search

Explanation: The KEYWORDSEARCH tool hasbeen called with an invalid value for theargument object_type.

Action: This argument indicates which type ofobject to search for, and must be one of thefollowing single characters:

• R - rule

• T - table

• S - screen

• P - report

• A - any of these.

Invalid opcode in selection for table"%"Source: TAM

Explanation: Possible system error.

Action: Check the valid selection syntax in thecalling rule (see the traceback). Also checkfor a valid stored selection in the definition ofthe specified table. If this is correct, push<PF2> and print the log, then contact TIBCOSupport, or the Database Administrator, withthe log and a description of what actionswhere being performed when this messagewas generated.

TIBCO Object Service Broker Messages Without Identifiers

Page 227: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 213

Invalid opcode in selection string foraccess on table "%"Source: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

Invalid operation code found duringsecurity checkingSource: TAM

Explanation: Unexpected condition detectedduring clearance checking.

Action: Print the message log if possible. Log offand log on before continuing. Contact TIBCOSupport.

Invalid operator in selection stringSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Invalid ORDERING - field "%.%" notfoundSource: Screen Server

Explanation: During a FORALL, a non-existentfield was specified for ordering.

Action: Do one of the following:

1. Use the correct field name.

2. Add the field to the table on which theordered FORALL is to be done.

Invalid OTMA function request: %Source: Builtin Routines

Explanation: You specified an invalid OTMAfunction request to the $OTMA built-inroutine. Valid function requests are: OPEN,ALLO, SEND, FREE and CLOS.

If the function shown in the message text isOPEN, this indicates that you already havean IMS OTMA connection open. Only oneconnection is allowed per session.

Action: Correct the error and retry. Refer to thesample rules in the Shareable Tools manual.

If the function in error is OPEN, close thecurrent connection before opening anotherone.

Invalid page image in file '%'Source: Offline Utilities

Explanation: While processing a backup file, theutility has encountered an invalid page.Additional messages will indicate the exactnature of the problem.

Action: Refer to accompanying messages foradditional instructions.

Invalid parameter: % - must be "#", "t",or bullet charactersSource: Character-based Text Editor

Explanation: The list command requires aparameter of: #, T, or the characters that areassigned to be bullets.

Action: Correct the parameter.

TIBCO Object Service Broker Messages Without Identifiers

Page 228: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

214 |

Invalid parameter: % - must not benegativeSource: Character-based Text Editor

Explanation: A negative number has been givenas a parameter.

Numeric parameters must be non-negative,whole numbers.

Action: Change the parameter number to apositive, whole number.

Invalid parameter name "%" for table"%"Source: Batch Control Card

Explanation: The indicated name is not aparameter for the indicated table.

Action: Check the table definition for the correctparameter names, and change the selectionstring accordingly.

Invalid parameter or field in selectionstring for access on table "%"Source: Builtin Routines

Explanation: A parameter or field specified in atable access statement is not a parameter orfield of the indicated table. The tabledefinition or the processed program wasprobably modified since the last passthrough the preprocessor.

Action: Verify the parameter and field names,and preprocess the program again.

Invalid parameter value; %Source: Batch Control Card

Explanation: The indicated parameter value isinvalid and an explanation is provided.

Action: Modify the selection string accordinglyby assigning a valid value to the indicatedparameter.

Invalid parameter value; bad sourcedata for parameter %Source: Table Editor

Explanation: You specified an invalid value forthe indicated parameter. For example,specifying a string value for a numericparameter is invalid.

Action: Try again using a valid value for theindicated parameter.

Invalid parameter value; source numbertoo large for parameter %Source: Table Editor

Explanation: You specified a value that cannot berepresented by the syntax defined for theindicated numeric parameter.

Action: Try again using a value within the rangeof the syntax. See the Managing Data manualfor a description of valid values.

Invalid parameter value; source numbertoo small for parameter %Source: Table Editor

Explanation: You specified a value that cannot berepresented by the syntax defined for theindicated numeric parameter.

Action: Try again using a value within the rangeof the syntax. See the Managing Data manualfor a description of valid values.

TIBCO Object Service Broker Messages Without Identifiers

Page 229: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 215

Invalid parameter value; source stringtoo long for parameter %Source: Table Editor

Explanation: You have specified a string valuewhich is too long for the indicated parameter.

Action: Try again using a shorter string value forthe indicated parameter.

Invalid PF key assignment: must be 0(disabled), or 1..23Source: Screen Definer

Explanation: In the Screen Definer, you assigneda standard function to an invalid PF key.Valid PF key values are in the range 1 to 23and 0.

Action: If you want to disable the standardfunction, assign 0 to the PF key. If you do notwant to disable the function, assign a valuebased on:

• How many function keys are available inthe destination screen

• Which other function keys have been usedalready.

Invalid physical record size for table"%"Source: TAM

Explanation: One of the following has occurred:

1. After an INSERT or REPLACE to a VSAMtable with multiple record types, thelength of the record about to be written tothe VSAM file does not match the physicalrecord size of the file. This error can occurfor RRDS and ESDS type VSAM tables,which must have all physical records thesame length.

2. When accessing a VSAM KSDS basecluster with an attached alternate index,

the alternate index RECORDSIZE is notbig enough to add another duplicate basekey occurrence in the current alternateindex record.

Action: Depending on the cause of the problem,do one of the following:

1. Either alter the parent or child VSAM tabledefinitions, or else change the number ofINSERTs or DELETEs of child recordssuch that the total record size matches thephysical record size.

2. Rebuild the alternate index specifying alarger RECORDSIZE.

Invalid presentation environment forthis objectSource: Global Cross Ref. Search

Explanation: The environment of your systemdoes not support the presentation of this typeof object.

Action: Use a system that supports thepresentation of this type of object.

Invalid primary command "%"Source: Object Manager

Explanation: You entered an invalid primarycommand.

Action: Correct the command.

Invalid primary key combinationSource: Table Definer

Explanation: The primary key selection cannotbe rationalized.

Action: Select a correct primary key value.

TIBCO Object Service Broker Messages Without Identifiers

Page 230: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

216 |

Invalid print class: "%"; must be A-Z or0-9 or *Source: Batch Submission Tool

Explanation: You have specified an invalid printclass for your output setting. A valid printclass must be an alphanumeric character A-Zor 0-9.

Action: Specify a valid print class value.

Invalid print class: "%"; must be A-Z or0-9 or *Source: Security

Explanation: You have specified an invalid printclass for your profile. A valid print class mustbe an alphanumeric character A-Z or 0-9.

Action: Specify a valid print class value.

Invalid print destination: "%" (%)Source: Security

Explanation: You specified an invalid printdestination for your print parameters in youruser profile.

Action: Specify a correct print destination.

INVALID PROFILE SELECTIONENTRY NUMBER SUPPLIEDSource: S6BTLADM - PROFILES DISPLAY

Explanation: The item number you specified inthe input field is invalid.

Action: Select one of the values listed on thescreen and retry your request.

Invalid QUERYKIND %Source: Global Cross Ref. Search

Explanation: The CROSSREFSEARCH tool wascalled with the parameter QUERYKIND setto an invalid value.

Action: This parameter indicates the type ofsearch to conduct, and must be one of thefollowing strings:

• RULE

• TABLE

• SCREEN

• SIGNAL

• EXCEPTION

• STRING

Invalid report name : "%"Source: Report Generator

Explanation: You specified an invalid reportname.

Action: Enter a valid Object Service Brokeridentifier. See the Processing manual formore information about Object ServiceBroker identifiers.

Invalid request for dictionary table "%"Source: TAM

Explanation: You accessed the indicateddictionary table by using an invalid method.The dictionary table is one of the following:

• $$SYSTABLES

• $$SYSPARMS

• $$SYSFIELDS.

Action:

• If the indicated dictionary table is$$SYSTABLES, you cannot access thistable.

TIBCO Object Service Broker Messages Without Identifiers

Page 231: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 217

• If you want to access the $$SYSPARMS or$$SYSFIELDS tables, use an unqualifiedFORALL statement.

Invalid request to Screen ServerSource: Screen Server

Explanation: This is an Object Service Brokerinternal error. The Screen Server has beencalled with an invalid request code.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log andan exact description of what actions werebeing performed when this messageappeared.

Invalid rights requested for "%" of type"%"Source: Manage Promotion Rights

Explanation: You are trying to perform one of thefollowing operations: OBTAIN all rights,RELEASE all rights, or TRANSFER all rightson an object. However, the type of thepromotion rights (DEFN, DATA, etc.) thatyou have specified for that object is invalid ordoes not match with the type of rightsavailable for the object.

Action: Check the promotion type of thespecified object and try again.

Invalid row/col for screen table "%"within Screen "%"Source: Screen Server

Explanation: The screen table has been specifiedto start at a position outside the bounds thatthe Screen Server can handle.

Action: Using the Screen Table Painter, check thestart rows and columns for the screen table. Ifany unreasonable values exist, such as row =600 or column = -350, change these valuesand try the rule again.

Invalid ROW/COL specifiedSource: Report Definer

Explanation: An invalid row or column wasentered in the definition area. Row andcolumn values must be numeric and greaterthan zero.

Action: Correct the indicated row or columnvalue.

Invalid row % in FIND_REGIONSource: Rule Editor

Explanation: Internal editor error.

The message log will contain a more detailederror message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

TIBCO Object Service Broker Messages Without Identifiers

Page 232: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

218 |

Invalid ROW for COPY/APPEND; copyrequires 3 rows; exceeds %Source: Report Definer

Explanation: The copy of a field and its headingsrequires 3 rows.

Action: Do one of the following:

• Position the cursor to a row that has 2 rowsavailable below it for the copy results, andpress <ENTER>.

• Use the NONAMES keyword with theCOPY or APPEND command so that theheadings are not copied. In this case, youneed only 1 row.

Invalid rule name : "%"Source: Report Generator

Explanation: The rule name that you provided isnot a valid Object Service Broker identifier.

Action: Enter a valid Object Service Brokeridentifier. See the Processing manual if youwant to know more about Object ServiceBroker identifiers.

Invalid scope for report function "%" ofreport field "%" in report table "%"Source: Report Server

Explanation: The scope of the report functionwas not one of REPORT, RUNNING, orPAGE.

Action: Use the Report Definer to correct thederived report field.

Invalid SCOPE value "%" specifiedSource: Promotions Bind Tools

Explanation: An invalid Scope value wasspecified for the @PROMUNBINDOBJS tool.

Action: Specify a valid Scope value of SYSTEM,INSTALLATION or ALL.

Invalid scroll amount: %Source: Table Editor

Explanation: You specified an invalid value forthe scroll amount.

Action: Press <PF1> for a list of valid scrollamount values. Try again with a valid value.

Invalid scroll amount "%"Source: Object Manager

Explanation: You entered an invalid amount inthe scroll field. The invalid scroll amount wasreplaced with a P (Page).

Action: If you do not want to scroll by pages,enter another valid scroll amount. They are:

• C (Column)

• M (Maximum)

• H (Half)

• D (Display)

• a number.

Invalid scroll amountSource: General

Explanation: You entered an invalid scrollamount for vertical scrolling. Valid scrollamounts are:

• C - Scroll to the line on which the cursor isplaced.

• H - Scroll a half-page up or down.

TIBCO Object Service Broker Messages Without Identifiers

Page 233: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 219

• P - Scroll one screen up or down.

• M - Scroll to the top or bottom.

• n - Scroll the specified number of lines upor down.

Action: Enter a valid scroll amount and press<PF7> or <PF8>.

Invalid scroll amountSource: Secure Audit Log

Explanation: You specified an invalid value forthe scroll amount.

Action: Press <PF1> to invoke field-level help todisplay a list of valid scroll values. Try againwith a valid scroll value.

Invalid segment number, "#", for "%"Source: Builtin Routines

Explanation: You specified an invalid value asparameter SEGMENT# to one of thefollowing tools: $GETENVCOMMAREA,$SETENVCOMMAREA.

Action: Supply a valid SEGMENT#.

INVALID SELECTION, RETRYSource: S6BTLADM - COMMON MESSAGES

Explanation: Your menu selection value was notvalid.

Action: Retry.

Invalid SELECTION character; use "S"Source: Security

Explanation: You put an invalid selectioncharacter beside an object in the TransferOwnership screen. Valid selection charactersfor this screen are blank, null, and S.

Action: If you do not want to select the object,type over the invalid character with a blank,or remove it (i.e., becomes NULL). If youwant to select the object, replace it with an S.

Invalid selection string duringFORALL on table "%"Source: TAM

Explanation: The requested or stored selection issyntactically invalid.

Action: Verify that the stored selection was notmodified outside of the Table Definer. Ifmodified, redefine the table again.

Invalid selection string for report field"%" of report table "%"Source: Report Server

Explanation: A syntax error was detected in theselection string for a report function.

Action: Using the Report Definer, review theselection string for report functions that wereused in the source of the derived report field.

Invalid selection string for report table"%"Source: Report Server

Explanation: A syntax error was detected in theselection string for the body report table.

Action: Using the Report Definer, review theselection string for a body report table withsyntax errors.

TIBCO Object Service Broker Messages Without Identifiers

Page 234: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

220 |

Invalid selection term using parameter"%" in % selection for table "%"Source: TAM

Explanation: In an input selection string theselection term/clause using a tableparameter must be of the format:

TableParm "=" value

In a stored selection a selection term using atable parameter or source-table parametercan have one of the following formats:

SourceTableParm "=" value

or

SourceTableField RelationalOperator TableParm

Action: Replace the selection clause with one ofthe valid formats.

Invalid selection valueSource: Adabas Definer

Explanation: Unable to list ADABAS COLUMNSfor selection.

Action: Specify the ADABAS Database ID(DBID) and FILE No for COLUMN selection.

Invalid semantic type enteredSource: Table Definer

Explanation: You did not enter a valid MetaStorsemantic type in the MetaStor TYPE field.

Action: Consult the Managing Data manual forinformation about valid MetaStor semantictypes.

Invalid semantic type for OF-FIELD"%" of report function "%"; see reportfield "%" of report table "%"Source: Report Server

Explanation: The semantic type of the indicatedOF-Field is not valid for the indicated reportfunction.

Action: Either change the semantic type of theOF-Field or use a different report function forthe derived field.

Invalid server typeSource: External Gateway Logon

Explanation: The type of gateway/server youwill be running as must be supplied.

Action: Supply the gateway/server type in theparameters before starting thegateway/server.

Invalid session end valueSource: Builtin Routines

Explanation: The value for $SETSESSIONENDaction is invalid. For actions of START, XTCL,FORMAT, and SWITCH the value must be astring of a maximum length of 8. For actionsof RETCODE, RC, and ABEND the valuemust be an integer.

Action: Change the call to $SETSESSIONEND topass a suitable value for the action specified.

Invalid session menu % in user profile;STANDARD is usedSource: Session Manager

Explanation: Your user profile names a menuthat is not a logon menu or does not exist.

Action: Correct your user profile.

TIBCO Object Service Broker Messages Without Identifiers

Page 235: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 221

Invalid set nameSource: Table Definer

Explanation: The set name you specified on theVERIFY ACCESS PATH screen is incorrect orinvalid.

Action: Correct the set name; you can find validset names by returning to the SELECTRECORDS screen, and using the ? linecommand to list all valid set names.

Invalid setup: % - Default setup hasbeen assumedSource: Character-based Text Editor

Explanation: A non-existent setup name hasbeen given in the setup command.

Action: Check the setup name, and put in a validname.

Invalid sort direction in ordering ofdynamically created table %Source: TAM

Explanation: You specified a sort direction otherthan blank, "A", or "D".

Action: Set the sort direction accordingly.

Invalid sort order for report field "%" ofreport table "%"Source: Report Server

Explanation: The sort order in the controlinformation of the report is invalid.

Action: Use the Report Definer to correct the sortorder. Sort orders can be either A (ascending)or D (descending).

Invalid source: "%"; specify either"DATABASE" or "ARCHIVE"Source: Batch Control Card

Explanation: You invoked theBATCH_UNLD_CARDS tool, and specifiedan invalid source as the input parameter tothis utility.

Action: Specify either "DATABASE" if you wantto unload from the MetaStor, or "ARCHIVE"if you want to unload from an archivebackup file.

Invalid source: valid values for locationparameter SRC are: %Source: Table Definer

Explanation: You have assigned a value otherthan those allowed for the SOURCE attributeof a location parameter.

Action: Specify the correct value as the SOURCEattribute value.

Invalid source for report field "%" ofreport table "%"Source: Report Server

Explanation: The source of a derived report fieldcontains a syntax error.

Action: Use the Report Definer to correct thereport field.

Invalid string: % - "on" or "off" isrequiredSource: Character-based Text Editor

Explanation: The command requires a parameterwhich must have the value of ON or OFF.

Case is irrelevant.

Action: Supply the required parameter.

TIBCO Object Service Broker Messages Without Identifiers

Page 236: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

222 |

Invalid string: % - "on" or "off" or anumber is requiredSource: Character-based Text Editor

Explanation: A correct parameter value was notsupplied.

The command requires either the parameterON or OFF, or a number.

Action: Provide either a number, ON, or OFF.

Invalid string: % - a number is requiredSource: Character-based Text Editor

Explanation: The command requires a parameterin the form of a number, and the number wasnot supplied.

Action: Provide the required parameter number.

Invalid SYNC function requestedSource: TAM

Explanation: Internal error.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log, and adescription of what actions were beingperformed when this message wasgenerated.

Invalid syntax "%" for parameter "%"Source: Table Definer

Explanation: The indicated parameter hasinvalid syntax; only B (binary), P (packeddecimal), and C (fixed character) are allowed.

Action: Change the syntax of the indicatedparameter to a B, P, or C.

Invalid syntax % for field %Source: Field Dictionary

Explanation: The syntax specified is invalid.

Action: Change the syntax to a valid value. Seethe Processing manual for valid syntaxes.

Invalid syntax defined for field "%.%"Source: TAM

Explanation: The mentioned field is improperlydefined.

Action: Use the Table Definer to assign a validTBCO Object Service Broker syntax to thefield.

Invalid syntax entered.Source: Table Definer

Explanation: You entered an invalid syntax in theMetaStor SYN field.

Action: Enter a valid syntax. See the ManagingData manual for a list of valid syntax codes.

Invalid syntax for % % of dynamicallycreated table %Source: TAM

Explanation: The syntax you specified for theindicated Field or Parameter is notsupported for the specified semantic type.

Action: Consult the Managing Data manual forinformation about valid MetaStor syntaxes.

TIBCO Object Service Broker Messages Without Identifiers

Page 237: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 223

Invalid syntax found in dynamicallycreated table %Source: TAM

Explanation: An internal conversion of thecontents of @DOFEXTFIELDS encounteredan invalid syntax. This should never occur inthe course of normal operation.

Action: Contact TIBCO Support.

Invalid syntax specified; press <PF1>for list of valid syntaxesSource: Batch Control Card

Explanation: You specified an invalid syntax.

Action: Correct the input. Valid values are givenin the message. Press <PF1> for Help to finda detailed explanation of each syntax value.

Invalid table/field name: "%"Source: Screen Server

Explanation: A screen routine (e.g.,$SETATTRIBUTE) has been passed a non-existent screen table or field parameter forthe Screen parameter provided.

Action: Use the correct combination of screen,screen table and field parameters.

Invalid table type "%" defined for table"%"Source: TAM

Explanation: The source table must be one of:TDS, TEM, SCR, IMS, or EXP.

Action: Make sure that the table type used is oneof the allowed values.

Invalid table type for reference table"%" on table "%"Source: TAM

Explanation: The table that you reference cannotbe of type SCR, EXP, or RPT.

Action: Refer to a table with a valid type.

Invalid temporary sort directory "%"Source: TAM

Explanation: External sort is unable to find thedirectory name supplied in the Workfileparameter.

Action: Supply the SORTUNIT parameter with avalid directory name. For more detail, referto the Parameters manual.

Invalid TIMEZONE: must be -23 to +23(incl.)Source: Security

Explanation: In the User Profile, you havespecified an invalid TIMEZONE. TheTIMEZONE is really an OFFSET from thesystem time. So, if you are say, 3 hours aheadof the system time, then the TIMEZONEsetting should be 3. If you are 3 hours behindsystem time, then set TIMEZONE to -3 andso on. Note that your RESTRICTED HOURSare according to SYSTEM TIME.

Action: Set the TIMEZONE according to thedifference between your local time and thetime in which the system operates.

TIBCO Object Service Broker Messages Without Identifiers

Page 238: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

224 |

Invalid token "%" in selection string forreport field "%" of report table "%"Source: Report Server

Explanation: A syntax error was detected in theselection string for a report function.

Action: Using the Report Definer, look for thesyntax error near to the token listed andcorrect the error.

Invalid token "%" in selection string forreport table "%"Source: Report Server

Explanation: A syntax error was detected in theselection string for the body report table.

Action: Using the Report Definer, look for thesyntax error near to the token listed andcorrect the error.

Invalid token "%" in source of reportfield "%" of report table "%"Source: Report Server

Explanation: A syntax error exists in the sourceof a derived report field.

Action: Use the Report Definer to fix the syntaxerror in the report field.

Invalid type/syntax combination for %% of dynamically created table %Source: TAM

Explanation: The combination of semantic typeand syntax you specified for the indicatedField or Parameter is not supported.

Action: Consult the Managing Data manual forinformation about MetaStor semantic typeand syntaxes.

Invalid TYPE/SYNTAX combinationSource: Report Definer

Explanation: The type and syntax specified for areport field within the definition area cannotbe used together.

Action: Consult the Object Service Brokerdocumentation for the correct type andsyntax combinations.

Invalid TYPE/SYNTAX combinationSource: Screen Definer

Explanation: You have defined a field with aninvalid TYPE/SYNTAX combination.

Action: Refer to the Text-based Presentationmanual for valid values, and correct yourdefinition.

Invalid type "%" encountered in % tableSource: Rule Editor

Explanation: Internal editor error.

The message log will contain a more detailederror message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

Invalid type % for field %Source: Field Dictionary

Explanation: The semantic type specified isinvalid.

Action: Change the type to one of the validvalues. See the Processing manual for validsemantic types.

TIBCO Object Service Broker Messages Without Identifiers

Page 239: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 225

Invalid type for % % of dynamicallycreated table %Source: TAM

Explanation: The type you specified for theindicated Field or Parameter is notrecognized.

Action: Consult the Managing Data manual forinformation about valid MetaStor semantictypes.

Invalid upper/lower limitSource: Promotion

Explanation: The FROM and TO fields musthave non-negative integers with the value ofthe TO field greater than the FROM field.

Action: Change the value in the FROM or TOfield.

Invalid use of $PAGE_NUMBER forreport field ";" of report table ";"Source: Report Server

Explanation: The specified field references thereport function $PAGE_NUMBER eitherdirectly or indirectly, and is also a break, sort,summary, or across field. Since the pagenumber in a report is dependent on the breakfields in the report, the break fields cannot bedependent on the page number or we wouldhave a circular definition.

Action: Change the report definition so that thereare no circular dependencies.

Invalid userid/serveruseridSource: External Gateway Logon

Explanation: The userid or IDPREFIX that wassupplied was not valid, or not unique in thisenvironment.

Action: Ensure that your userid is valid, and thatonly one gateway/server run with thesupplied IDPREFIX.

Invalid userid; % is not one tokenSource: Security

Explanation: The userid that you specified hasembedded blank or special characters, suchas quotation marks or parentheses, which donot make it a valid single token.

Action: Make the necessary correction to theuserid value and try again.

Invalid userid; % starts with an illegalcharacterSource: Security

Explanation: The userid that you specified has aninvalid starting character. A userid must startwith either an alphabetic character, $, # or @.

Action: Make necessary correction to the useridvalue and try again.

Invalid userid; length must be between3 and 8Source: Security

Explanation: You specified a userid which haseither less than 3 characters or more than 8characters.

Action: Make necessary correction to the useridvalue and try again.

TIBCO Object Service Broker Messages Without Identifiers

Page 240: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

226 |

Invalid value "%" for field "%"Source: Batch Control Card

Explanation: The indicated value is invalid forthe indicated field.

Action: Specify a valid value for the given field.

Invalid value for % parameter; ensuretype-compatibleSource: Security

Explanation: While specifying an instance of atable, you entered a value for a parameter ofthe table that is incompatible with thedefined type and syntax of the parameter.For example, if you enter B5 for a DATE typeparameter, you will see this message.

Action: Remove the offending value and replaceit with a valid one.

Invalid value for option "%" of "%"Source: Builtin Routines

Explanation: One of the following occurred:

• This message applies to argumentsOPTION_NAME and OPTION_VALUE ofthe $BATCHOPT tool. You cannot assignthe latter value to the former.

• An internal error.

Action: If the error was caused by the$BATCHOPT tool, supply a valid value. Ifnot, contact TIBCO Support.

Invalid value in selectionSource: Print Rules

Explanation: A value in the selection cannot beused in the selection.

Action: Correct the value. This may require that adate be expressed in the format used on thescreen, YYYY-MM-DD.

Invalid version; enter V2.2, V2.3 orleave blankSource: Static SQL for DB2 Gateway

Explanation: The DB2 version number entereddid not match the allowed values of V2.2 orV2.3.

Action: Enter V2.2, V2.3, or leave blank.

TIBCO Object Service Broker Messages Without Identifiers

Page 241: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 227

Messages beginning with: J

Java external routine "%" raisedexception "%"Source: Interpreter

Explanation: The indicated Java external routineraised the indicated Java exception.

Action: Correct the Java external routine or theuse of it such that it does not raise a Javaexception.

Java Virtual Machine could not beloaded for Java external routine "%"Source: Interpreter

Explanation: The Java Virtual Machine could notbe located at the path given by the locationrow in the instance of @JAVAOPTIONSbelonging to the Execution Environment.

Action: Correct the path in the location row.

Job SubmittedSource: Promotion

Explanation: The batch job for applying thechange have been submitted.

Action: No action required.

Justification code invalid -justification=%Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Justification must be L, C, or RSource: Menu Definer

Explanation: When positioning titles for themenu, you must choose to place them on theleft (L), centre (C), or right (R).

Action: Correct the justification.

TIBCO Object Service Broker Messages Without Identifiers

Page 242: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

228 |

Messages beginning with: K

Key field % in source table missingfrom table definitionSource: Table Definer

Explanation: The indicated key field from thesource table is not found in the Subview tabledefinition.

Action: Define the indicated field as key field inyour Subview table definition.

Key field cannot have default valueSource: Table Definer

Explanation: A primary key cannot have adefault value.

Action: Remove the default value specificationfor the primary key field.

Key field not number 1 in dynamicallycreated table %Source: TAM

Explanation: The field identified [email protected] equal to "P" is not thefirst field.

Action: Set the first Primary Key field to be thefirst field.

Key field representing the records' ISNmust have a length of '4'Source: Adabas Definer

Explanation: Invalid external length for key fieldrepresenting the ADABAS ISN#.

Action: Specify special external length of 4 forkey field representing the ISN#.

Key field representing the records'relative number must have a length of'2'Source: Adabas Definer

Explanation: Length of key fields (other than thefirst key representing the ADABAS ISN#)should be 2.

Action: Specify a length of 2 for the keyrepresenting the records' relative occurrence.

Key fields not contiguous indynamically created table %Source: TAM

Explanation: A compound primary key must becomposed of an initial, contiguous set offields.

Action: Ensure that all primary key fields in@DOFFIELDS are grouped at the beginning.

TIBCO Object Service Broker Messages Without Identifiers

Page 243: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 229

Key for dynamically created IDGENtable % must be IDENTIFIER BINARY4Source: TAM

Explanation: The primary key of the table youare dynamically creating is not of semantictype IDENTIFIER, syntax BINARY, andlength 4.

Action: Set the type, syntax, and length toIDENTIFIER BINARY 4.

Key length > 127; cannot be selected askeySource: Table Definer

Explanation: You cannot choose a field that islonger than 127 bytes to be a primary key.

Action: Use another line command so that thefield is not a primary key for the MetaStorIMS table.

Key length for table "%" does not matchkey length of VSAM % "%"Source: TAM

Explanation: The length of the key for the ObjectService Broker definition of the indicatedtable is not equal to the length of the actualkey in the KSDS data set. The variables in themessage, from left to right, are as follows:

1. The name of the table

2. Either "file" or "DDNAME"

3. The name of the file or the DDNAME

Action: Change the definition of the ObjectService Broker table so that the key lengthequals the VSAM record key length.

Key offset for table "%" does not matchkey offset of VSAM % "%"Source: TAM

Explanation: The offset of the key in the tabledefinition does not match the actual keyoffset of the VSAM file. The variables, fromleft to right, are as follows:

1. Either "file" or "DDNAME"

2. The name of the file or the DDNAME

Action: Ensure that the table definition for theindicated table matches the characteristics ofthe actual VSAM file.

Keyfield for % M204 table must have %% % attributesSource: Table Definer

Explanation: The Keyfield must have thespecified attributes

Action: Specify the attributes as requested

Keys must be together and at the frontof the definitionSource: Adabas Definer

Explanation: The ordering of your key fields isinvalid.

Action: Define keys to be consecutive and at thefront of the table definition.

Keytype of % must be consistent withsource tableSource: Table Definer

Explanation: The keytype of the indicated fielddoes not match that of the source table.

Action: Change keytype to contain the samevalue as in source table.

TIBCO Object Service Broker Messages Without Identifiers

Page 244: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

230 |

Keyword(s) longer than 20 charactersignored - see message logSource: Keyword Manager

Explanation: This object has one or morekeywords of more than 20 characters. Thesekeywords will not be indexed. The objectsand their keywords are listed in the messagelog.

Action: Press <PF2> to see a list of objects whosekeywords must be shortened.

TIBCO Object Service Broker Messages Without Identifiers

Page 245: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 231

Messages beginning with: L

Label "%" is not a valid stringSource: Report Generator

Explanation: The indicated label is not a validstring.

Action: Type in a valid label for your report.

Largest positive ROW must be for body;use a negative rowSource: Report Definer

Explanation: Any report tables with a positiverow origin must be printed above the bodyreport table. In other words, the row origin ofthe report table must be less than the roworigin of the body report table.

Action: If you want to print the report tablebelow the body report table, change theROW specified to a negative number. Thenumber indicates the row offset relative tothe bottom of the report page (e.g., row -1represents the bottom line on a page).

Last % columns will be truncated uponsavingSource: Character-based Text Editor

Explanation: This message warns you that theindicated number of columns will betruncated from the document when thedocument is saved.

Action: Confirm whether the truncation isacceptable or adjust the documentaccordingly if you do not want it to betruncated.

Last 16 rules calledSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

Left edge of WindowSource: General

Explanation: You pressed <PF1> until youreached the left edge of the displayableinformation. No more information exists tothe left of the screen you are viewing.

Action: No action required.

Left edge of windowSource: Unload

Explanation: You have requested to page left andthe screen is already at the left border.

Action: No action required.

Length + pos - 1 is "#" for "%", it must be<= print width which is "#"Source: Builtin Routines

Explanation: The sum of the POS and LENGTHarguments for $PRINTFIELD must be lessthan the print width.

Action: Adjust the arguments or the page width.

TIBCO Object Service Broker Messages Without Identifiers

Page 246: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

232 |

Length argument extends beyond endof buffer - length=#,buflen=#Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Length argument less than 0 - length=#Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Length can be only 4, 8, or 16 for syntaxFSource: Table Definer

Explanation: The valid lengths for a MetaStorfloating point field are 4, 8, or 16.

Action: Change the field length to a valid one.

LENGTH CANNOT BE NEGATIVESource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

LENGTH field is insufficient for mask"%"; need length of %Source: Screen and Report Painters

Explanation: The specified display mask extendsbeyond the length of the field.

Action: Either increase the length of the field oradjust the display mask to the existinglength.

Length must be 1 for logical typeSource: Table Definer

Explanation: The length for a MetaStor logicalfield must be 1.

Action: Change the length of the field to 1.

Length must be between 1 and 12 forsyntax BSource: Table Definer

Explanation: The length for a MetaStor binaryfield must be either 2 or 4.

Action: Change the length of the field to 2 or 4.

Length must be between 1 and 16 forsyntax PSource: Table Definer

Explanation: The length for a MetaStor packeddecimal field must be between 1 and 8.

Action: Enter a value between 1 and 8 for thefield.

TIBCO Object Service Broker Messages Without Identifiers

Page 247: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 233

Length must be positive for % % ofdynamically created table %Source: TAM

Explanation: The length you specified for theindicated Field or parameter is negative.

Action: Specify a length greater than zero.

LENGTH MUST BE STRICTLYPOSITIVESource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Length of "%" cannot be null for offsetcalculationSource: Table Definer

Explanation: External length must be entered foroffset calculation.

Action: Specify starting length for offsetcalculation.

Length of # specified for function PADexceeds the current maximumpermissible value of #Source: Interpreter

Explanation: The length specified for the outputstring is larger than the current maximumpermissible value.

Action: Either specify a smaller value for thelength, or increase the session parameterEXECSTACKSIZE to allow for larger strings.The maximum permissible value of thelength for PAD is approximately(EXECSTACKSIZE - 32K). Note that if theresult of PAD is to be assigned to a localvariable, the value of the session parameterEXECLOCALSIZE may need to be increasedas well.

Length of % must %Source: Table Definer

Explanation: Invalid length.

Action: Specify new value with correct length asspecified in the message.

Length of 2 or 4 required with Binarysyntax for % % of dynamically createdtable %Source: TAM

Explanation: The indicated Field or Parameter isof syntax BINARY and of length other than 2or 4.

Action: Consult the Managing Data manual forinformation about valid representations ofnumerical data.

TIBCO Object Service Broker Messages Without Identifiers

Page 248: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

234 |

Length of 4/8/16 required with Floatsyntax for % % of dynamically createdtable %Source: TAM

Explanation: The indicated Field or Parameter isof syntax FLOAT and length other than 4, 8,or 16.

Action: Consult the Managing Data manual forinformation about valid representations ofnumerical data.

LENGTH OF A BINARY NUMBERMUST BE <= 4Source: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

LENGTH OF A FLOATING POINTNUMBER MUST BE 4, 8 OR 16Source: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

LENGTH OF A PACKED NUMBERMUST BE <= 8Source: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Length of argument for rule "%" toolong for an asynchronous eventSource: Interpreter

Explanation: The operating system imposes alimit on the total size of the arguments of arule to be run in batch (by using theSCHEDULE statement). This limit wasexceeded.

Action: Try passing the arguments through atable.

Length of binary field "%" must be 2 or4Source: Table Definer

Explanation: The length of the indicated binaryfield is not 2 or 4.

Action: Change the length of the indicated fieldto 2 or 4. If the length is 2, the field can storenumbers from -32,768 to 32,767. If the lengthis 4, the field can store numbers from -2,147,483,648 to 2,147,483,647.

TIBCO Object Service Broker Messages Without Identifiers

Page 249: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 235

Length of field %Source: Field Dictionary

Explanation: The user specified a length that isoutside the bounds for the field syntax. Thismessage continues:

= %, is above the range %:%

or

= %, is below the range %:%

Action: Change the length to a number withinthe bounds specified in the error message.

Length of float field "%" must be 4, 8, or16Source: Table Definer

Explanation: You did not specify 4, 8, or 16 as thelength for a floating point field.

Action: Change the length of the indicated fieldto 4, 8, or 16. The lengths correspond to 24,56, or 112 binary digits of precision.

Length of logical field %Source: Field Dictionary

Explanation: You entered a length for a logicalfield that is not equal to 1. This messagecontinues:

= %, is above the range 1:1

or

= %, is below the range 1:1

Action: Change the length to 1.

Length of parameter "%" for table "%" >127Source: TAM

Explanation: The defined length of theparameter is greater than 127.

Action: Correct the length parameter in the tabledefinition so that it is less than or equal to 127bytes.

Length of string greater than 32767Source: Interpreter

Explanation: Strings cannot contain more than32767 characters.

Action: Verify that no string can become largerthan 32767 characters.

Length of title/footing for "%" is # andmust be <= #Source: Builtin Routines

Explanation: The arguments L, C and R of$SETP#POS or $SETTITLE cannot have atotal length that exceeds the print width or132, whichever is smaller.

Action: Adjust the arguments or the page width.

LENGTH operand of the SUBSTRINGfunction goes beyond the end of thestringSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 250: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

236 |

LENGTH operand of the SUBSTRINGfunction is a negative numberSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Level 7 clearance required to usePAGE_STATS or PAGE_ENTRYSource: TAM

Explanation: These Object Service Brokerroutines require level-7 security clearance.

Action: Request that your system administratorrun the affected rule.

Libraries permissions for object set willbe committed on SAVESource: Security

Explanation: You saved library permissionsspecifications for an object set.

Action: No action required. To cancel anychanges made to library permissions for anobject set, you must cancel from the object setdefinition screen.

Library "%" cannot be referred to morethan onceSource: Security

Explanation: You referred to a particular librarymore than once while specifying librarypermissions for an Object set definition.

Action: Remove duplicate entries from the list byreplacing the library name with blanks, nulls,or another library name.

Library "%" does not existSource: Security

Explanation: You referred to a non-existentlibrary.

Action: No action required unless you have toremove the reference.

Library "%" was defined since createuser began; cannot SAVESource: Security

Explanation: A Security Administrator is tryingto create a userid, but since this request wasinitiated, someone has created a library of thesame name as the userid being created. Thehome library cannot be created for theuserid.

Action: You must cancel and restart with a newuserid, or you can have the created libraryrenamed by authorized individuals.

Library % is empty; no changes to crossreference.Source: Global Cross Reference Build

Explanation: The library named in the call toREFMAKER is empty. No changes have beenmade to the existing cross reference.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 251: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 237

Library % is not defined; you are inyour HOME library, %Source: Session Manager

Explanation: You specified a logon library thatexisted at the time of the specification, butdoes not exist at the time of this logon. Sincethe library no longer exists, the sessionmanager puts you into your home library atlogon.

Action: A recommended action is to remove thenon-existent library reference from your UserProfile Logon Library.

Library % is not definedSource: Session Manager

Explanation: You attempted to set the currentlibrary field in the workbench to a librarythat does not exist.

Action: Replace the name of the non-existentlibrary with an existing library, preferablyone for which you have at least VIEW_DEFNauthorization.

Library copy succeeded: % rules copiedSource: Copy Rule or Copy Library

Explanation: The library was copied successfully.The source library should contain thenumber of rules indicated as copied in themessage.

Action: Verify that the number of rules copied iscorrect.

Library definition and rules in library"%" DELETEDSource: Define Library

Explanation: You requested and confirmed thedeletion of a library.

Action: No action required.

Library does not contain any RulesSource: Unload/Load

Explanation: The specified library is empty.

Action: No action required.

Library error on rule "%"Source: Session Manager

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

LIBRARY is required for %, which caninclude %SSource: Unload

Explanation: You have requested to unload anobject which includes rules by reference. Youmust specify from which LIBRARY thereferenced rules should be unloaded.

Action: In the top area of the screen, type in theLIBRARY which should be used as thesource of these referenced rules.

TIBCO Object Service Broker Messages Without Identifiers

Page 252: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

238 |

Library name "%" is invalidSource: Promotion

Explanation: The library name entered cannot bea source library for promotions, or a rollbacklibrary.

Action: Change the library name.

Library name cannot be blankSource: Unload/Load

Explanation: You entered a rule name but did notenter a library name.

Action: On the first line beneath Rules in Library,type in a valid library name.

Library names can only be eightcharacters longSource: Copy Definition

Explanation: A library name cannot exceed 8characters in length.

Action: Retype the library name, up to 8characters.

Library parameters must be specifiedSource: CHANGERULE tool

Explanation: There is no library name on thescreen.

Action: Enter the name of the library containingthe rules you want changed.

Limit cannot be negativeSource: Batch Submission Tool

Explanation: You specified a negative number inthe limit field of the queue definition screen.

Action: Enter a positive value.

Line command "%" is invalidSource: Rule Editor

Explanation: You entered an invalid linecommand.

Action: Enter a valid line command; you canpress <PF1> for a list of valid line commands.

Line length too long for destinationSource: Character-based Text Editor

Explanation: The output line is set too long forthe field in the destination table. This lengthis the sum of the adjust and linelengthparameters.

Action: Check the most recent .setup, .ll, or .adcommands for specifying too large a valuefor linelength or adjust. There is a .setupdefault implied if no actual .setup commandappears at the start of the document.

Line numbers are 1, 2, or 3 for top andbottomSource: Menu Definer

Explanation: The top and bottom can each fitonly three lines which are numbered 1, 2, and3.

Action: Correct the line numbers.

Line position must be T=top orB=bottomSource: Menu Definer

Explanation: Title lines must appear at the top orbottom of the screen.

Action: Enter a valid letter to indicate the top orbottom.

TIBCO Object Service Broker Messages Without Identifiers

Page 253: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 239

LINK failed: module "%"; R15 = %Source: Session Manager

Explanation: Link to the sort program failed. Fordiagnostic purposes, the module to whichthe link was directed and the return code aresupplied.

Action: Call your system administrator to ensurethat the module being linked to is availableand to check the return code in Register 15against the appropriate vendor's manual.Correct the problem as required.

List "%" interface is not definedSource: Table Definer

Explanation: The interface for listing tablesand/or columns from external DBMS has notbeen defined.

Action: Invoke the "Define list tbl/col interface"option in GENDT to define the LISTinterface.

List of valid colors is not availableSource: Builtin Routines

Explanation: One or both of the TDS tables@COLOURS and @SCREENCOLOURScannot be accessed during initialization ofthe list of valid screen colors.

Action: Contact your System Administrator.

List printedSource: Object Manager

Explanation: You pressed <PF13> to print the listof objects.

Action: No action required.

Lists do not contain the same number ofobjects (out of synch)Source: Definition Differences

Explanation: You are trying to compare two listsof objects but the number of objects in thesetwo lists is not the same.

Action: Insert the missing objects or remove theextra objects and try again.

Literal '%' contains a word which spansthe fixed columnsSource: Screen Definer

Explanation: The specified literal contains aword that extends beyond the fixed columnboundary.

Action: Either adjust the fixed columns toinclude the interfering word, or adjust theliteral to fit within the fixed columns.

Literal text cannot start in the firstcolumn of Image AreaSource: Screen Definer

Explanation: You have entered literal text whichstarts in the first column of the Image Area.

Action: Either move, or remove, the character(s)in the first column.

Load completedSource: Tool for CA IDMS Data

Explanation: The subschema definitionidentified in the import files has been loadedinto the Object Service Broker/IDMSdictionary tables.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 254: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

240 |

Load ended due to error; <PF2> formoreSource: Unload/Load

Explanation: A system error occurred during theLOAD process.

Action: Press <PF2> to view the error messages.Print the log file and contact TIBCO Support.

Load of definition of table "%" willcause nested FORALLSource: Interpreter

Explanation: Internal error. You used a systemtable in a FORALL statement, then attemptedto access the table again within the FORALLloop.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Avoid nested FORALL statements on onetable.

Load of rule "%" failedSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Load of VSAM table "%" exit routine"%" failedSource: TAM

Explanation: The indicated exit routine cannot beloaded from the library of external routines.

Action: Make sure that the exit routine exists asan executable load module in a library that iscurrently allocated to Object Service Broker.

Loaded % Tbls % Scrs % Rpts % Rules% Objsets % MenusSource: Unload/Load

Explanation: The specified number of objectswere loaded.

Action: No action required.

Loaded %Source: Promotion

Explanation: The specified number of objectswere loaded as a result of applying thechange to the system.

Action: No action required.

Loading % of % %Source: Unload/Load

Explanation: This is an informational messagethat indicates what is being loaded (thedefinition, occurrences, or both definitionand occurrences), the type of object (table,screen, rule or report), and the object name.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 255: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 241

Loading definition and occurrences of% TablesSource: Unload/Load

Explanation: Definitions and occurrences of thenamed tables were loaded.

Action: No action required.

Loading definition of % TablesSource: Unload/Load

Explanation: The definitions of the named tableswere loaded.

Action: No action required.

Loading definition of %Source: Unload/Load

Explanation: Definitions of the named objectswere loaded. When tables are named, thismessage implies that only the definition andnot the occurrences of the table was loaded.

Action: No action required.

Loading definition of %Source: Unload/Load

Explanation: Definitions of the named objectswere loaded. When this message names atable, it implies that only the definition andno occurrences was loaded.

Action: No actions required.

Loading occurrences of % TablesSource: Unload/Load

Explanation: Occurrences only were loaded forthe named tables.

Action: No action required.

Local Variable "%" has not beendeclaredSource: Debugger Utility

Explanation: You have tried to list (or set) a localvariable which has not yet been declared byyour application.

Action: Verify the spelling of the local variable tobe listed (or set).

Local variable "%" is not defined in anyruleSource: Interpreter

Explanation: You assigned a value to a localvariable that you did not define.

Action: Define the local variable.

Local variable heap garbage collectionerrorSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 256: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

242 |

Local variable storage overflowSource: Interpreter

Explanation: You created too many localvariables in one transaction, or the variablesuse up too much storage. This message mayindicate an infinite loop or a recursion that istoo deep.

Action: Verify that recursion does not get out ofcontrol. Try increasing the value of the EEparameter EXECLOCALSIZE

Locale invalid for locale.codepage: %Source: TAM

Explanation: The Locale of the locale.codepagecombination is invalid.

Action: Specify a correct Locale.

Location parameter "%", cannot be usedin the selectionfieldSource: Table Definer

Explanation: Location parameter is referenced inthe Selection string which is invalid.

Action: Remove location parameter reference inSelection string.

Location parameter is not allowed for"%" table typeSource: Table Definer

Explanation: You defined a location parameterfor the specified table type for which locationparameter is not supported.

Action: Remove the location parameter in thetable definition.

Location parameter is not last parameterin dynamically created table %Source: TAM

Explanation: In @DOFPARMS, you assigned aCLASS of "L" to a parameter other than thelast.

Action: Ensure that only the last Parameter isgiven a CLASS of "L".

Location parameter must be defined as IC 16 0Source: Table Definer

Explanation: The location parameter must bedefined with a semantic type of I, a syntax ofC, and a length of 16.

Action: Specify the attributes of the locationparameter accordingly.

Location parameter must be specifiedSource: Table Definer

Explanation: You have tried to save a minimaldefinition but you have not specified thelocation parameter.

Action: Specify the location parameter and tryagain.

Lock check failed for "%" :table "%"Source: TAM

Explanation: The update operation "%" failed forthis EES table. The row has been modifiedbetween fetch and update operations. ALOCKFAIL signal is raised.

Action: If there is a need to update this EES tablerow, refetch and update the row again, elsefail the transaction. See the Managing Datamanual for details of the lock processing onEES tables.

TIBCO Object Service Broker Messages Without Identifiers

Page 257: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 243

Lock failed: %Source: General

Explanation: Internal error. % represents a tablename. The table named, which is required bythe tool, is locked by another user.

Action: Try again. If the problem persists contactyour System Administrator to determinewho is holding the lock.

Lock Failure:%Source: Copy Definition

Explanation: A table is being locked by someoneelse.

Action: Check for locking on the table and retrywhen the lock is released.

LOCK MANAGER STATISTICSRETRIEVAL ERRORSource: S6BTLADM - LOCK MANAGER

Explanation: The attempt to retrieve the statisticsfor the lock manager display failed.

Action: Review the message log for possibleadditional information. Retry the request. If aproblem persists contact the support center.

Lock request blocked for TABLE=% byself (parent/child deadlock)Source: Lock Manager

Explanation: The user was executing atransaction which started anothertransaction or transactions. The childtransaction required share or exclusivelock(s) on the table name displayed and/or akey or table instance of it. A parenttransaction had previously obtained lock(s)on these resources, so the child transaction's

lock request is blocked. This informationmessage is returned to the blocked user'sterminal. The LOCKFAIL exception is raisedand the transaction is terminated.

Action: To prevent this deadlock, you may needto make changes to one or more the ObjectService Broker rules which are beingexecuted.

Lock request blocked for TABLE=% byUSER=% (upgrade deadlock) <onNODE=%>Source: Lock Manager

Explanation: A rule executed by the user hadpreviously obtained lock(s) on the tablename displayed and/or a key or tableinstance of it. This rule now requires astronger lock on at least one of theseresources due to a more exclusive rulestatement (e.g., first GET, then REPLACE), orbecause the user's lock count has reached anescalation threshold while the lock managerwas running short of free lock buffers.

Another user or users had previouslyobtained locks on these resources and theselocks are currently being retained, so thisupgrade request is blocked. The resourcecontention situation is already sufficientlycomplex (other transactions queued) thatwaiting is not expected to succeed. Thisinformation message is returned to theblocked user's terminal. The LOCKFAILexception is raised and the transactionterminated. If the blocking user is from aremote node, the NODE name is appendedto the message.

Action: If there is an immediate need to completethe failed transaction, then the blocked usershould contact the blocking user to arrangethe release of the table/resource incontention. Contention situations can beresolved more permanently by making

TIBCO Object Service Broker Messages Without Identifiers

Page 258: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

244 |

appropriate changes to the rules and/ortable definitions. Escalation can bepostponed by increasing the size of the lockbuffer pool specified, using theLOCKBUFFERS Data Object Brokerparameter.

Lock request blocked for TABLE=% byUSER=% <on NODE=%>Source: Lock Manager

Explanation: A rule executed by the userrequired share or exclusive lock(s) on thetable name displayed and/or a key or tableinstance of it. Another user or users hadpreviously obtained locks on these resourcesand the locks are still retained, so the newrequest is blocked. The blocked user's lockrequest may have waited without success, orfailed without waiting due to a complex waitqueue or because the blocker was a long-running transaction. This informationmessage is returned to the blocked user'sterminal. The LOCKFAIL exception is raisedand the transaction terminated. If theblocking user is from a remote node theNODE name is appended to the message.

Action: If there is an immediate need to completethe failed transaction, the blocked usershould contact the blocking user to arrangethe release of the table/resource incontention. Contention situations can beresolved more permanently by makingappropriate changes to the rules and/ortable definitions.

If the user is displayed as IN*DOUBT, atransaction is being held in pending status.To investigate why the transaction did notcomplete successfully, use theAdministration Menu, IN-DOUBTTRANSACTIONS option. For moreinformation on the Administration Menu,

refer to the Object Service Broker Installingand Operating manual for your platform.

LOCK REQUEST BLOCKED FORTABLE=% BY USERID=%Source: TAM

Explanation: Another user or another transactionfor this user has locked the requestedoccurrence or table.

Action: Do one of the following:

• Try again later

• Contact the specified user

• Contact your System Administrator.

Lockfail: % - try againSource: Report Generator

Explanation: Access to a certain system table wasblocked by another transaction.

Action: Repeat the function you were trying toinvoke when you received this message.

Lockfail: %Source: Batch Control Card

Explanation: You encountered a lockingproblem.

Action: Try again at a later time.

Lockfail:Source: Keyword Manager

Explanation: You tried to save your editingchanges to keywords for an object, butanother user has blocked you from savingyour changes.

Action: Do one of the following:

TIBCO Object Service Broker Messages Without Identifiers

Page 259: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 245

• Wait until the other user is finished, thensave your changes

• Press the CANCEL PF key, which takesyou out of editing mode.

LOCKFAIL - %Source: Object Set Definer

Explanation: The current action cannot beperformed because someone else is holding alock on the indicated table.

Action: Wait until the lock is released.

LOCKFAIL - %Source: Report Definer

Explanation: The report indicated cannot bechanged because of a lockfail. Someone elseis holding a lock on the report.

Action: Wait until the lock is released.

LOCKFAIL - lock request for reporttable "%" blockedSource: Report Definer

Explanation: The lock for the indicated reporttable is being held by another user.

Action: Try again.

Lockfail : %Source: Table Definer

Explanation: Access to the indicated table isblocked by another transaction.

Action: Repeat your request at a later time.

Lockfail on @PROMUNBOUNDOBJS:%Source: Promotions Bind Tools

Explanation: A locking error occurred on aninsert to @PROMUNBOUNDOBJS and the@PROMUNBINDOBJS tool terminated.

Action: Resolve the error specified and run@PROMBINDOBJS before re-running@PROMUNBINDOBJS.

LOCKFAIL on table@BORROWED_OBJSource: Rule Editor

Explanation: You cannot get the promotionrights.

Action: Try again later.

Lockfail on TABLES; unable to locatePRM table for %Source: Promotion

Explanation: The TABLES table is locked. As aresult, the parameter table for the specifiedtable cannot be accessed.

Action: Wait and try your transaction again.

LOCKS COULD NOT BE FOUND FORTRANSACTION XXXXXXXXSource: S6BTLADM - USER ACTIVITY

Explanation: No logical locks for the specifiedtransaction when you attempted to zoom inon the detailed list to the selected stream.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 260: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

246 |

Log printedSource: Session Manager

Explanation: You pressed <PF13> and themessage log you are viewing was printed.

Action: No action required.

Logical field must have length of 1Source: Screen Definer

Explanation: You have defined a field to have a"Typ" of Logical but defined its length to begreater than 1, which is the maximum validlength for this Type.

Action: Change the field length to 1, or changethe syntax.

Logical type requires Length = 1 for %% of dynamically created table %Source: TAM

Explanation: The indicated Field or Parameter isof semantic type LOGICAL and of lengthother than 1.

Action: Set the length to 1.

Logoff from SYSTEM % by % fromenvironment ID %Source: Audit Log Message

Explanation: A user with the specified externalenvironment user ID logged off of thespecified Object Service Broker system.

Action: No action required.

Logon failed: Access prevented foruserid at this time: userid "%"Source: Security

Explanation: You attempted to log on, but thelogon restriction parameters in your userprofile prevent you from logging on at thistime.

Action: Contact your Security Administrator ortry again later.

Logon failed: Invalid userid for logonused: userid "%"Source: Security

Explanation: You attempted to log on with aninvalid userid.

Action: Try again with a valid userid or contactyour Security Administrator.

Logon failed: null SESSION MENU,START RULE & "R" keyword parmSource: Security

Explanation: You requested to log on, but did notspecify the RULE keyword parameter. Sincethe User Profile does not have a SessionMenu or Logon Startup Rule specified, thelogon cannot proceed past authorization.

Action: Either specify a rule with the RULE (R)keyword parameter, or have your SecurityAdministrator specify a Session Menu or aLogon Startup Rule in your User Profile.

TIBCO Object Service Broker Messages Without Identifiers

Page 261: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 247

Logon failed: Userid not defined tosystem: userid "%"Source: Security

Explanation: The logon failed because thespecified identifier is not defined in theMetaStor.

Action: Either define the identifier to theMetaStor using the Security Managerinterface, or attempt to log on with a differentidentifier.

Logon of userid "%" CANCELLEDSource: Security

Explanation: You canceled your logon requestfrom the Password panel.

Action: No action required.

Logon Restrict "%" parameter is not avalid time (HHMM)Source: Security

Explanation: A Security Administrator suppliedan invalid time in the User Profile. Thesupplied value is not in the valid range forhours and minutes of the form HHMM. Forexample, 2655 is invalid, and 1528 is valid.

Action: Correct the time to be a valid time in theform HHMM.

Logon Restrict parameters indicatelogon will always be deniedSource: Security

Explanation: A Security Administrator updateda user's profile so that the Logon Restrictparameters are equal and nonzero (e.g., 1145to 1145). These values never allow a user to

log on. 0 to 0 is accepted to mean that the useris never restricted from logging on. 0 to 945indicates that the user cannot logon betweenmidnight and 9:45 a.m.

Action: Change the Logon Restrict parameters.

Logon restricted to operators at thistimeSource: External Gateway Logon

Explanation: Only Data Object Broker operatorsessions are valid at this point in time.

Action: Resubmit the session when theenvironment is ready.

Logon Rule was not executed because itwas not foundSource: Session Manager

Explanation: You just logged on and the rule toexecute at logon, as specified in your UserProfile, is not in the local, installation, orsystem libraries.

Action: Remove the reference to a non-existentrule, or ensure that the rule exists in the local,installation, or system library.

Logon to SYSTEM % by % fromenvironment ID % denied: incorrectpasswordSource: Audit Log Message

Explanation: The specified external environmentuser ID attempted to log on to the specifiedObject Service Broker system but did not usethe correct password for the Object ServiceBroker userid.

Action: The user must retry with the correctpassword or consult the securityadministrator.

TIBCO Object Service Broker Messages Without Identifiers

Page 262: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

248 |

Logon to SYSTEM % by % fromenvironment ID % denied: restrictedtime windowSource: Audit Log Message

Explanation: The user attempted to log on withinthe restricted time boundaries set in theuser's profile. The user is not permitted to logon within these times.

Action: The user must log on to TIBCO ObjectService Broker within the allowed time rangeor consult the Security Administrator.

Logon to SYSTEM % by % fromenvironment ID % denied: user is not"real user"Source: Audit Log Message

Explanation: The password associated with theObject Service Broker userid that the usertried to use is blank. Because the password isblank, the following must be satisfied inorder for the user to log on to Object ServiceBroker:

• The EXTERNALSECURITY parametershould be set to something other thanInternal.

• The user's external environment user IDand Object Service Broker userid must bethe same.

Action: The user can do one of the following:

• Log on to Object Service Broker from anaccount where the external environmentuser ID matches the Object Service Brokeruserid.

• Ask the security administrator to changethe password to a non-blank value.

Logon to SYSTEM % by % fromenvironment ID % denied: user issuspendedSource: Audit Log Message

Explanation: The security clearance is zero forthe specified userid. The user cannot log onto the Object Service Broker system.

Action: If the user needs access to Object ServiceBroker, the user should contact a securityadministrator to have the security clearancechanged.

Logon to SYSTEM % by % fromenvironment ID % denied: userundefinedSource: Audit Log Message

Explanation: A user tried to log on to thespecified Object Service Broker system fromthe specified external environment user ID,but the Object Service Broker userid is notvalid.

Action: The user must use a userid and passwordthat Object Service Broker recognizes. See theExternal Environments for z/OS manual formore information about logging on to ObjectService Broker with the USERID andPASSWORD parameters.

Logon to SYSTEM % by % withclearance % from environment ID %Source: Audit Log Message

Explanation: A user logged on to the specifiedObject Service Broker system using thespecified external environment user ID andthe specified clearance level. The user passedthe userid and password security check.

Action: No action is required.

TIBCO Object Service Broker Messages Without Identifiers

Page 263: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 249

Lowest title line "#" > highest footingline "#" or more than 28title/footing/page number lines aftercall to "%"Source: Builtin Routines

Explanation: Any line above the lowest title lineis considered a title line; likewise, any linebelow the highest footing line is considered afooting line.

Action: Reduce the number of title or footinglines. If you have less than 28 of these lines,increase the page length.

TIBCO Object Service Broker Messages Without Identifiers

Page 264: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

250 |

Messages beginning with: M

Made % change(s)Source: Rule Editor

Explanation: The indicated number of changeswere made to the rule when the CHANGEALL command was executed.

Action: No action required.

Made % changesSource: Character-based Text Editor

Explanation: The CHANGE command with theALL option made the given number ofchanges.

Action: No action required.

Make a proper selectionSource: Tool for CA IDMS Data

Explanation: You must select an item.

Action: Type an S beside the desired option andpress <Enter>.

MANUAL INTERVENTION NOTSUPPORTED FOR CURRENTSTATUSSource: S6BTLADM - INDOUBT TRX

Explanation: The transaction you haveattempted to manually commit or abortcannot be processed because of its currentstatus. Possible reasons are an abort inprogress, resolution query request, TDS

processing deferred, or commitcomplete._Check the TIBOC Object ServiceBroker Administration Menu online help formore details on indoubt transaction.

Action: No action required.

Mask selection cancelledSource: Report Generator

Explanation: The display mask selection wascanceled because you did not place thecursor in a valid area.

Action: Choose a display mask again and movethe cursor to a line with a field name orfunction-field name pair before you press<ENTER>.

Max # of rows exceeded. Line command% cannot be executedSource: Table Definer

Explanation: The indicated line command is notexecuted because the number of rowsallowed is limited.

Action: Remove the line command to continueworking in the Table Definer.

TIBCO Object Service Broker Messages Without Identifiers

Page 265: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 251

MAX ACR ^= 0 only allowed forBREAKs with a BODY report tableSource: Report Definer

Explanation: The only break tables that canrepeat across are those associated with abody report table.

Action: Set the MAX ACR field to 0.

MAX ACR for BREAK must be 0 orMAX ACR for BODY report tableSource: Report Definer

Explanation: A break table within a body reporttable must have the MAX ACR field set toone of the following:

• Zero (0), indicating that it will not repeatacross.

• The same across value as the body reporttable, indicating that it will repeat acrossthe same number of times.

Action: Correct the MAX ACR field for the breaktable.

MAX ACROSS for break table "%" notthe same as MAX ACROSS for bodytable "%"Source: Report Server

Explanation: The MAX ACROSS value for breakand body tables must be the same so thatcolumns and headings will align on panelledpages for an Across Report.

Action: Use the Report Definer to correct thedefinition of the report.

MAXACROSS for body table "%" zerowhen TITLE COLUMNs or FINALCOLUMNs not zeroSource: Report Server

Explanation: The number of title columns andfinal columns must be zero unless the reportis an Across Report.

Action: Use the Report Definer to do one of thefollowing:

• Set the title columns and final columns tozero

• Make the report an Across Report bysetting MAX ACROSS to an asterisk (*) ora positive number.

Maximum CTABLE size exceeded fortable "%"Source: TAM

Explanation: The size of the definition of thetable exceeds the limit of 6 KB.

Action: Correct the definition of the table so thatthe total size is less than 6 KB.

Maximum level of nesting in %exceeded, increase level by %Source: Promotion

Explanation: Backing a change requires a certainminimum level of transaction nesting, andyou cannot backout a change until youincrease the maximum by the suggestedamount.

Action: Increase the maximum level oftransaction nesting by the suggested amount.

TIBCO Object Service Broker Messages Without Identifiers

Page 266: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

252 |

Maximum number of % control fieldsapplies; limit exceededSource: Report Definer

Explanation: The control field limit is exceeded.

Action: Remove control fields until the specifiedlimit is no longer exceeded.

Maximum number of ORDER fieldsexceeded for table "%"Source: TAM

Explanation: The number of ordering fields in arequest, added to the number of any storedordering fields, cannot exceed 15.

Action: Remove some of the ORDERspecifications on fields of the indicated table.

Maximum number of parametersallowed is %Source: Table Editor

Explanation: A table cannot have more than thespecified number of parameters. You havespecified more than this maximum.

Action: Reduce the number of parametersspecified, or do not supply any and you willbe prompted for them.

Maximum number of parametersallowed is 4Source: Batch Control Card

Explanation: You specified more than fourparameters in the selection string.

Action: Change the selection string so that itcontains the correct number of parametersfor the selected table.

Maximum number of report fields is %Source: Report Definer

Explanation: The current maximum number ofreport fields within a report table isindicated. The action you have requestedwould result in more than the maximumnumber of defined report fields.

Action: Do not attempt to add more report fieldsthan the maximum allowed.

Maximum of % allowed; % wereselectedSource: Field Help for Reference

Explanation: Too many prompt values wereselected.

Action: Limit the number of prompt valuesselected to the maximum indicated.

Maximum of % key components areallowed for a composite keySource: Table Definer

Explanation: You specified more than theindicated maximum number of fields asprimary keys.

Action: Remove the P designation from some ofthe fields. Ensure that the primary key fieldsare consecutive.

Maximum report width is %Source: Report Definer

Explanation: The report is over the maximumwidth indicated.

Action: Do not attempt to exceed the indicatedmaximum.

TIBCO Object Service Broker Messages Without Identifiers

Page 267: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 253

Maximum row at which new field maybe defined is %Source: Report Definer

Explanation: You tried to define a field on a rowbeyond the allowable maximum row.

Action: Change the row of the field to one withinthe allowed row limit.

Maximum row which can be referencedis "%"Source: Report Definer

Explanation: The message specifies themaximum row at which a report field can beadded or moved.

Action: Do not define a report field on any rowgreater than the specified maximum.

Maximum value is 32400 secondsSource: Batch Submission Tool

Explanation: The number of seconds specified onthe queue definition screen cannot exceed32400 seconds.

Action: Enter a number between 0 and 32400.

Member "%" not foundSource: Builtin Routines

Explanation: The named member could not befound in the partitioned data set.

Action: Try another member name.

Member name can not be used. In usefor %Source: Static SQL for DB2 Gateway

Explanation: A member suffix has beensupplied, but it is already being used for thegeneration of Static SQL for another table.

Action: Choose a different, unique membersuffix.

MEMORY ADDRESS IS VALID BUTTOO MUCH DATA WASREQUESTEDSource: S6BTLADM - MEMORY DISPLAY

Explanation: You have specified a valid address;however, the projected length of the memoryto be retrieved extends beyond the areacontrol by the Data Object Broker.

Action: Specify a retrieval length and retry yourrequest.

Memory operation would bedestructiveSource: Builtin Routines

Explanation: The memory operation requestedof $MEMCPY or $MOVEDATA involvesoverlapping blocks of storage, and cannot beperformed without guaranteeing loss ofdata.

Action: Only use $MEMCPY and $MOVEDATAfor non-overlapping blocks of storage.

TIBCO Object Service Broker Messages Without Identifiers

Page 268: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

254 |

MEMORY RETRIEVAL ERRORDETECTEDSource: S6BTLADM - MEMORY DISPLAY

Explanation: An error was detected whenattempting to issue the storage retrievalrequest.

Action: Review the syslog to determine ifadditional messages where produced thatmay help identify the cause of the problem.Retry the request. If the problem persistscontact TIBCO Support.

Menu "%" not foundSource: Session Manager

Explanation: You called a session manager orDISPLAY_MENU with a menu name thatdoes not appear in the SESSION_MENUStable.

Action: Correct the menu name.

Menu % deletedSource: Menu Definer

Explanation: The specified menu is deleted.

Action: No action required.

Menu % does not existSource: Menu Definer

Explanation: You called the display menu or asession manager entry point with the nameof a menu that does not exist.

Action: Correct the name.

Menu % savedSource: Menu Definer

Explanation: The menu is saved.

Action: No action required.

Menu deletion cancelledSource: Menu Definer

Explanation: The deletion of a menu wascanceled because a key other than <PF22>was pressed.

Action: No action required.

Menu name % conflicts with an existingscreenSource: Menu Definer

Explanation: The name of a new menu is thesame as an existing screen. DEFINE_MENUcannot make a new screen as requested.

Action: Change the name of the menu.

Menus with entries positioned at LEFTare no longer supportedSource: Menu Definer

Explanation: In a former incarnation of the MenuManager, menus having user entriespositioned to the left of their descriptionswere allowed. This format is no longersupported by the Menu Manager.

Action: To save changes to an existing menu withentries positioned on the left, modify thepositioning information to have entries onthe right, or cancel changes. New menusmust be saved such that entries arepositioned on the right.

TIBCO Object Service Broker Messages Without Identifiers

Page 269: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 255

Message could not be sent to location"%" peerseverid "%"Source: TAM

Explanation: A communications or ObjectService Broker message switch failureoccurred trying to send a message to anotherlocation.

Action: Verify that the location is valid. If not,correct using the Rule Editor and/or TableDefiner. If the location is valid, then confirmthat the location is configured and available.Ensure that the remote table access is notbeing initiated from an event rule running ina remote peer server as only local tableaccesses are allowed in that configuration.

Message length error when bindingtable "%"Source: TAM

Explanation: The GET occurrence passed the endof the message.

Action: Contact TIBCO Support.

Message log media must be "SCR" or"PRT"Source: Unload/Load

Explanation: The message log can be sent toeither the online log file or to the printer.

Action: Specify either SCR or PRT as the choice ofmedia.

Message log overflow - specify recordlimitSource: Report Generator

Explanation: The report is too big to be printed inthe message log.

Action: Specify a lower record limit.

Message log overflow - too manymessages inserted into the message logSource: Builtin Routines

Explanation: There are too many messages forthe SCR print destination.

Action: Use a different media: PRT or file.Alternatively, adjust the MSGLOGMAXsession parameter.

Message log overflowSource: Report Server

Explanation: The report that you are printingexceeded the maximum storage limit ofmedia SCR.

Action: Do one of the following:

• Limit the number of occurrences that youinsert into the report by using the$RPTOCCLIMIT tool.

• Use another media to print the report.

TIBCO Object Service Broker Messages Without Identifiers

Page 270: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

256 |

Metadata table definition of field doesnot match DB2's: field "%"Source: Static SQL for DB2 Gateway

Explanation: When the external table for DB2data was defined in the MetaStor, the field inquestion had a particular set of attributes onthe DB2 system. When the definition of thatfield was retrieved from DB2, its attributeswere different from when the external tablewas defined.

Action: Use the Table Definer to redefine andsave the external table for DB2 data, then trythe Static SQL generation again.

Mismatch betweenEMSWIRECODEPAGE and nationallanguage settingsSource: POSIX ON support for EMS

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.

Mismatch on %, table now has data and% was "%"; cannot saveSource: Table Definer

Explanation: Data has been added to the tabledefinition since the Table Definer wasopened but non-permissible changes havebeen made to the indicated field.

Action: If the definer you are using allows it, youcan set the attribute value back to the valueindicated in the message. Otherwise you cansave as a new table definition or exit withoutsaving.

Mismatched quotes detected by "%"Source: Builtin Routines

Explanation: An argument for the specifiedroutine contains mismatched quotationmarks.

Action: Balance the quotation marks.

Missing a value for the primary key(s)of table '%'Source: Copy Definition

Explanation: One of the primary key values ismissing for the specified table.

Action: Quit the tool, and provide primary keyvalue for table.

Missing dataset name for "%", file hasnot been openedSource: Builtin Routines

Explanation: You called @READDSN or@WRITEDSN, but did not call @OPENDSNbefore.

Action: Ensure that you call @OPENDSN first.

Missing documentation/unit forselected % %Source: Promotion

Explanation: No documentation exists for thespecified screen, report or table.

Action: Provide documentation by using the Eline command.

TIBCO Object Service Broker Messages Without Identifiers

Page 271: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 257

Missing KEY data from % atOFFSET=% -- see OFFSETS or FIELDS.Source: CA Datacom Table Definer

Explanation: You are defining extensions to coredefinition information in a DAT TableDefinition. These extensions are for the fieldsof the Object Service Broker table andprovide additional field attributes. To definea Object Service Broker table on a CA-Datacom table, you must have all the parts ofthe CA-Datacom table key included in theObject Service Broker definition. You aremissing the CA-Datacom key data at theoffset mentioned.

Action: Do one of the following:

• Review the OFFSETS information in thecurrent screen to see that the mentionedoffset is not included, or

• Review the OFFSETS information for theCA-Datacom table fields by requesting theFIELDS function and then looking for thementioned offset in the list of CA-Datacomfields for the CA-Datacom table you areusing.

Missing left parenthesisSource: Global Cross Ref. Search

Explanation: A query is missing a leftparenthesis.

Action: Correct the query.

Missing parm table for '%'Source: Delete Definition

Explanation: You are trying to delete an objectand this process may require deletion ofseveral tables. A PRM table is required inorder to delete some of the tables and one ofthese PRM tables does not exist.

Action: Check the message log to see which PRMtable is missing. Define that PRM table andretry the operation again.

Mixed-case password update failed; setvalue back to %Source: Security

Explanation: You updated the mixed-casepassword field in your user profile andsaved, but the routine that updates this valuefailed.

Action: If you want to save other profile changes,set the value back to the previous value asshow in the message and save otherwise,cancel. If you still want to update the mixed-case password value, contact your Securityor System Administrator to make the change.

Modify % or % to remove overlapSource: Report Definer

Explanation: The indicated fields overlap.

Action: Change the row or column of theindicated fields to remove the overlap.

Modify definition of % % by % deniedSource: Audit Log Message

Explanation: MODIFY_DEFINITION access tothis object by the specified user was denied.

Action: The user can ask someone who hasCONTROL access to the object to provide

MODIFY_DEFINITION access.

TIBCO Object Service Broker Messages Without Identifiers

Page 272: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

258 |

Modify definition of % % by % toremove default library permission %from %Source: Audit Log Message

Explanation: The specified default permissionsfor newly created libraries were removedfrom the indicated user or group.

Action: No action required.

Modify definition of % % by % toremove default report permission %from %Source: Audit Log Message

Explanation: The specified default permissionsfor newly created reports were removedfrom the indicated user or group.

Action: No action required.

Modify definition of % % by % toremove default screen permission %from %Source: Audit Log Message

Explanation: The specified default permissionsfor newly created screens were removedfrom the indicated user or group.

Action: No action required.

Modify definition of % % by % toremove default table permission %from %Source: Audit Log Message

Explanation: The specified default permissionsfor newly created tables were removed fromthe indicated user or group.

Action: No action required.

Modify definition of % % by % to setdefault library permission % to %Source: Audit Log Message

Explanation: The indicated default accesspermissions will be used for libraries createdby the indicated user or group.

Action: No action required.

Modify definition of % % by % to setdefault report permission % to %Source: Audit Log Message

Explanation: The indicated default accesspermissions will be used for reports createdby the indicated user or group.

Action: No action required.

Modify definition of % % by % to setdefault screen permission % to %Source: Audit Log Message

Explanation: The indicated default accesspermissions will be used for screens createdby the indicated user or group.

Action: No action required.

Modify definition of % % by % to setdefault table permission % to %Source: Audit Log Message

Explanation: The indicated default accesspermissions will be used for tables created bythe indicated user or group.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 273: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 259

Modify definition of AUDITLOG by %to specify archived file name % deniedSource: Audit Log Message

Explanation: The user was denied access tochange the name of the archive file for theaudit log data.

Action: The user can check with the SecurityAdministrator to get access to the facility.

Modify definition of AUDITLOG by %to specify archived file name %Source: Audit Log Message

Explanation: The user has specified the given fileas the archive file for the backed up audit logdata.

Action: No action required.

Modify definition of GROUP % by %Source: Audit Log Message

Explanation: The definition of the specifiedgroup object was modified.

Action: No action required.

Modify definition of GROUP % by % toadd user member %Source: Audit Log Message

Explanation: The indicated TIBCO ObjectServcie Broker userid was added to theindicated group.

Action: No action required.

Modify definition of GROUP % by % tochange view group access for %Source: Audit Log Message

Explanation: The view access to the given groupwas changed for the specified user.

Action: No action required.

Modify definition of GROUP % by % todelete user member %Source: Audit Log Message

Explanation: The indicated Object Service Brokeruserid was deleted from the indicated group.

Action: No action required.

Modifying % bound objectsSource: Promotion

Explanation: The specified number of objectswere unbound in order to apply changes tothose objects.

Action: No action required.

Module ; must be LINK EDITED withAMODE(31)Source: Builtin Routines

Explanation: The indicated module must beLINK EDITED with AMODE(31).

Action: Review and implement the procedure forthe creation of this module.

TIBCO Object Service Broker Messages Without Identifiers

Page 274: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

260 |

Module ; not found in EXLIB orSTEPLIBSource: Builtin Routines

Explanation: The indicated load module was notfound.

Action: Review and implement the procedure forthe creation of this module.

More than 4 parameters; No % loadedSource: Unload/Load

Explanation: Tables cannot have more than fourparameters.

Action: Correct the definition of the source table.

Move cursor to Display Mask sectionand press % to continueSource: Report Generator

Explanation: You selected a display mask, butdid not move the cursor to the line for thefield or function-field pair that you want todisplay with the mask.

Action: Use the cursor to indicate the field orfunction-field pair that gets the displaymask, and press <ENTER> to complete thedisplay mask specification.

MU/SPECIAL FLD IN GRP must be "Y"as not all fields in the group are definedSource: Adabas Definer

Explanation: You entered an invalid value forMU/Special Fld in Grp. It must have a valueof Y since not all the fields in the group areselected.

Action: Set MU/Special Fld in Grp to Y.

MU/SPECIAL FLD IN GRP must be "Y"as the group contains a Special fieldSource: Adabas Definer

Explanation: You entered an invalid value forMU/Special Fld in Grp. It must have a valueof Y since the group contains a Special field.

Action: Set MU/Special Fld in Grp to Y.

MU/SPECIAL FLD IN GRP must be 'Y'as there is a 'MU' field in the groupSource: Adabas Definer

Explanation: You entered an invalid value forMU/Special Fld in Grp. It must have a valueof Y since the group contains a MU field.

Action: Set MU/Special Fld in Grp to Y.

MU/SPECIAL FLD IN GRP must be 'Y'as there is an overridden external fieldformat in the tableSource: Adabas Definer

Explanation: You entered an invalid value forfield MU/Special fld in Grp. The value mustbe Y, since you have requested that thedefault ADABAS field definition is to beoverridden by the server.

Action: Specify Y for MU/Special fld in Grp.

Multiple fields and non-repeatinggroup fields cannot be mixedSource: Adabas Definer

Explanation: You selected repeating fields andnon-repeating fields. This selection is invalid.

Action: Select only repeating fields or non-repeating fields.

TIBCO Object Service Broker Messages Without Identifiers

Page 275: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 261

Must e(X)pand data rights for object"%" before obtainingSource: Promotion

Explanation: Cannot obtain data rights from thisscreen for this table.

Action: Type object command X which will takeyou to a screen where you may obtain datarights.

TIBCO Object Service Broker Messages Without Identifiers

Page 276: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

262 |

Messages beginning with: N

Name "%" is not a parameter of rule "%"Source: Interpreter

Explanation: You used a WHERE clause to passarguments to a rule, but one argument namedoes not correspond to any argument of therule.

Action: Verify the spelling of the argument name.

Name does not have type I, syntax C orV or WSource: Interpreter

Explanation: Names of Object Service Brokerobjects must meet specific requirements(type/syntax).

Action: Verify the type and syntax of the name.

Name has been changed - Unable toDELETE object set "%"Source: Object Set Definer

Explanation: You cannot delete an object set inthe Object Set Definer if you have changedthe name that appears at the top of the screenof the object set.

Action: If you want to delete the object set, youmust first exit the Object Set Definer, reenterit with the name of the object set to bedeleted, and then delete it by pressing<PF22>.

Name has been changed - Unable todelete report "%"Source: Report Definer

Explanation: The user tried to both rename anddelete a report.

Action: Either rename or delete the report, but donot do both.

NAME OF COUNTFIELD must exist inthe ADABAS file definitionSource: Adabas Definer

Explanation: The countfield you specified doesnot exist in the ADABAS file definition.

Action: Specify a valid ADABAS field name forthe countfield.

Name of Location parameter cannot bea Globalfield nameSource: Table Definer

Explanation: The name of the location parameterin the table definition is defined as a globalfield. This is not allowed.

Action: Change the name of the locationparameter to a valid MetaStor name that isnot a global field.

TIBCO Object Service Broker Messages Without Identifiers

Page 277: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 263

Need documentation for % beforeselecting itSource: Promotion

Explanation: The object selected for promotingor deleting requires documentation.

Action: Use the E object command to edit thesummary. Save it before repeating the action.

Negative lengthSource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Nested FORALL loop for table % is notallowedSource: HLIPREPROCESSOR

Explanation: Nested FORALL statements accessthe indicated table; this is not supported.

Action: Eliminate nesting by using GETFIRSTand GETNEXT to create a loop.

Nesting of FORALL and/or UNTILstatements is too deepSource: Rule Editor

Explanation: Loops have been nested too deeply.

Action: Separate the loops within the rule, oracross two or more rules.

New %Source: Table Definer

Explanation: The object indicated in the messagedoes not currently exist in the MetaStor.

Action: No action required.

New field definitionSource: Field Dictionary

Explanation: You changed the field name afterentering the Field Manager. The change isaccepted.

Action: No action required.

New global field definitionSource: Field Dictionary

Explanation: Informs you that this fielddefinition was not found in the global fielddictionary.

Action: You can fill in the appropriateinformation and press <PF3> to add the fielddefinition, or press <PF12> to cancel it.

New lines in history area not allowedSource: Session Manager

Explanation: You attempted to use the blank areabelow the bottom of the history stack.

Action: No action required.

New occurrenceSource: Table Editor

Explanation: Confirms that a new occurrence isbeing added to this table, in the SingleOccurrence Editor.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 278: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

264 |

New rule error for rule %Source: CHANGERULE tool

Explanation: An error occurred when trying tofind this rule to examine it for the giventoken.

Action: Attempt to edit the rule and save it. If asimilar error occurs, contact TIBCO Support.

New subschema definitionSource: Tool for CA IDMS Data

Explanation: The subschema being loaded is anew definition in Object Service Broker.

Action: No action required.

NEW table definition... SelectSUBSCHEMA and RECORDS firstSource: Table Definer

Explanation: This is a new IDM table definition.The record access path must be selected first.

Action: Enter the SUBSCHEMA name and <PF6>to display the CA-IDMS records defined inthe subschema.

New table definitionSource: Table Definer

Explanation: The current table is a new table.

Action: You can cancel (press <PF12>) this tabledefinition and it will not exist, or you canproceed to define a table.

NEXT BUFFER REQUESTED FROMDISPLAY OF LAST BUFFERSource: S6BTLADM - MEMORY DISPLAY

Explanation: You are currently displaying thelast buffer from a buffer list function. Thenext buffer request you requested cannot behonored.

Action: No action.

NLS check failed. Return Code=% forlocale.codepage: %Source: TAM

Explanation: The NLS check that validateslocal.codepage failed. The return codeindicates the reason.

Action: Review your NLS setup and verify thelocale.codepages you specified are correctand supported by Object Service Broker.

NLS initialization failed on table "%"Source: TAM

Explanation: NLS translation failed due to aninvalid or unknown configuration.

Action: Check the values in table @NLS1 and@SERVERCONFIG with parameters values"_NT" and "_NS". They must contain validlocale.codepage combinations.

TIBCO Object Service Broker Messages Without Identifiers

Page 279: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 265

No. of parms in table % does not matchwith that on source systemSource: Promotion

Explanation: The number of parameters in thespecified table does not match with thenumber on the target system, so the applyprocess cannot proceed as requested.

Action: On the source system, Unaccept thechange and return it to the developer. Thedeveloper should roll back the changerequest and make the specified tablecompatible with the one on the target system.The change can then be re-extracted andreapplied to the target system.

No % loadedSource: Unload/Load

Explanation: The % is replaced with one of thefollowing:

• DEFINITION

• OCCURRENCES

• DEFINITION AND OCCURRENCES.

The message indicates that a request was notperformed. The explanation precedes thismessage.

Action: No action required.

No % log for %Source: Promotion

Explanation: No log is available for phase 1, 2, or3. Logs are produced after each phase of theapply process. If for some reason the phasefailed before a log could be produced, thismessage appears. It is usually accompaniedby another message indicating which phasefailed and the reason for the failure.

Action: See the message indicating which phasefailed and the reason for failure, and take theappropriate action.

No % statement generatedSource: HLIPREPROCESSOR

Explanation: An error was detected in an ObjectService Broker statement that prevented thegeneration of the corresponding COBOLstatements.

Action: Correct the Object Service Brokerstatement.

No %S selectedSource: Promotion

Explanation: You must use "S" to select one ormore object types before pressing the key toselect individual objects for promotion.

Action: Type "S" beside the object type(s) thatyou want to select and then press the key toselect individual objects for promotion.

No @RULESDOCUMENT entry existsfor the ruleSource: Rule Editor

Explanation: Internal error.

TIBCO Object Service Broker Messages Without Identifiers

Page 280: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

266 |

The message log will contain a more detailederror message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

No ACROSS-BY fields for body table"%" when TITLE COLUMNs or FINALCOLUMNs not zeroSource: Report Server

Explanation: The number of title columns andfinal columns must be zero unless the reportis an Across Report.

Action: Use the Report Definer to do one of thefollowing:

• Set the title columns and final columns tozero

• Change the report to an Across Report byadding ACROSS-BY fields.

No active %Source: Debugger Utility

Explanation: You have used the DUMP (forinstance, DUMP LOCAL) primary commandto obtain a listing of some items. Thisprovides feedback.

Action: No action required.

No active tablesSource: Interpreter

Explanation: This message indicates that thereare no active tables.

Action: Study the Information Log.

No activity foundSource: Promotion

Explanation: You requested to view the activityfor a change request but none was found.This may occur if the activity has beendeleted from the TDS table where it is stored.

Action: No action required.

NO ALERT MESSAGE ON THESYSTEM AT THIS TIMESource: S6BTLADM - ALERT MESSAGE

Explanation: There are currently no alert-levelmessages to report.

Action: No action is required.

No authorization for Logon Library"%"; HOME library usedSource: Session Manager

Explanation: You specified a Logon Library inyour User Profile to which you do not haveVIEW_DEFN permission. As a result, thesession manager puts you in your homelibrary at logon time.

Action: Do one of the following:

• Obtain at least VIEW_DEFN permissionfor a logon library

• Remove the reference to this library fromthe LOGON LIBRARY field of your UserProfile.

TIBCO Object Service Broker Messages Without Identifiers

Page 281: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 267

No authorization for menu %,STANDARD is usedSource: Session Manager

Explanation: You have a session menu specifiedin your User Profile for which you do nothave proper authorization; therefore, theSTANDARD session menu is displayedinstead.

Action: Obtain the proper security authorizationfor the indicated session menu, or change thelogon session menu to one for which youhave proper authorization.

No break event present at %Source: Debugger Utility

Explanation: You have used the OFF primarycommand to remove a specific break event.However, this break event had not been set.You may have misspelled the break event tobe removed.

Action: Verify the spelling of the break event tobe removed.

No broadcast availableSource: Session Manager

Explanation: The BROADCAST table is empty.

Action: No action required.

No CA-Datacom fields selectedSource: CA Datacom Table Definer

Explanation: You were in the FIELDS contextlooking at the list of CA-Datacom fields andyou did not select any of the fields forinclusion into the definition.

Action: No action is required.

No change requests exist on systemSource: Promotion

Explanation: You are attempting to create aconsolidated change request but there are nochange requests on this system. Aconsolidated change request is one thatcontains other change requests. Since thereare no change requests at this time, aconsolidated change request cannot bedefined.

Action: Do not create a consolidated changerequest at this time or choose a differentsource node for the included changerequests.

No change requests for the specifiedsource node and locationSource: Promotion

Explanation: There are no change requests forthe FROM and AT nodes specified on thequery screen. This means that there isnothing to query given these nodes.

Action: Change the FROM and AT nodes forsubsequent queries.

No change requests match the criteriaSource: Promotion

Explanation: You requested to query a given setof change requests but no matches werefound.

Action: Verify that the FROM and AT nodes arecorrect. Also, check the selection criteriaspecified on the query screen. You may needto broaden the scope to find the changerequest(s) you are looking for.

TIBCO Object Service Broker Messages Without Identifiers

Page 282: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

268 |

No change requests were loadedSource: Promotion

Explanation: Before doing a target apply, thenecessary change requests must be loadedfrom extract files. You have attempted toAPPLY REQUESTS before any changerequests have been loaded.

Action: Fill in the FROM CHANGE # and TOCHANGE # fields and select APPLYREQUESTS again.

No changed required - press PF2 formoreSource: CHANGERULE tool

Explanation: No rules had to be changed for thetokens you entered.

Action: Press PF2 and review the report. Youmay wish to change the tokens you entered.

No changes necessarySource: Rule Editor

Explanation: Change command given of form:

CHANGE x x

No changes are necessary since x is x.

Action: No action is required.

No changes specifiedSource: CHANGERULE tool

Explanation: No changes are required by input.

Action: This may mean that your input is notcorrect. For instance, the FROM and TOtokens may be the same. Check that you havespecified changes correctly.

No code generatedSource: Host Language Interface

Explanation: The preprocessor will not createfurther code for this command.

Action: No action required.

No CONTROL TABLE entry for %object "%" (version=%)Source: Unload

Explanation: There is a problem with the objecttype definition data for one of the objects yourequested to unload.

Action: Report this to your SystemAdministrator as there should not be aproblem with the object type definition datafor unloadable object types.

No CTABLE found for report tableSource: TDS

Explanation: The table definition for theindicated report table cannot be found.

Action: Define the required report table.

NO DATA FOUNDSource: Copy Defn/Data

Explanation: This message indicates that no datawas found in the table and so it was notcleared.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 283: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 269

No data in ACCESSLOG topurge/archive for dates:%-%Source: Secure Audit Log

Explanation: You attempted to purge the auditlog contents of a specified date range but thatdate range contained no data.

Action: Check the date range that you want topurge and try again.

NO data LOADED in populated tablebecause action is % %Source: Unload/Load

Explanation: No data was loaded because thetable already contained data and the actionwas IS.

Action: No action required.

No data tables in change request#%Source: Promotion

Explanation: Since there are no data tables in thespecified change request, you do not need tospecify the backup options.

Action: No action required.

No data to printSource: Promotion

Explanation: There is no data on the screen sothere is nothing to print.

Action: Use this PF key when there is data on thescreen.

No data to printSource: Secure Audit Log

Explanation: You attempted to print a report ofthe audit log but the audit log was empty andcontained no data.

Action: No action required.

NO DATA TO REPORT FORSPECIFIED SEG, DSN AND STARTENTSource: S6BTLADM - RPP DIRECTORY

Explanation: The segment data set and entry youspecified are valid; however, there is data tobe displayed.

Action: No action is required.

No default DATE mask defined oraccessibleSource: Builtin Routines

Explanation: The Object Service Broker tool$DATE_DEFAULT cannot find the defaultDATE mask due to one of following:

• No installation default DATE mask wasdefined.

• An internal programming error.

Action: Contact TIBCO Support.

No definition extractedSource: Adabas Extract

Explanation: LIST definition failed. No ADABASdefinition found.

Action: Invoke utility @ADAEXTRACT toextract ADABAS definition into ObjectService Broker before listing the definitions.

TIBCO Object Service Broker Messages Without Identifiers

Page 284: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

270 |

No definition for "%.%" referenced bysubview field "%.%"Source: TAM

Explanation: One of the following occurred:

• A source table field name was notspecified for a subview field.

• The source table definition cannot befound for the subview field name.

Action: Do one of the following:

• Specify a source table field name for thesubview field.

• Modify or add the definition of the sourcetable so that it contains the reference fieldused in the subview field.

No definition for PARENT object type"%"Source: Unload

Explanation: There is a problem with the objecttype definition data for one of the objects yourequested to unload.

Action: Report this to your SystemAdministrator as there should not be aproblem with the object type definition datafor unloadable object types.

No definition found for table "%"Source: TAM

Explanation: A non-existent table is specified in atable operation.

Action: Do one of the following:

• Define the specified table, using the TableDefiner.

• Correct the pertinent rule, as indicated bythe traceback, to reference an existingtable.

No definition found for virtual ScreenSource: TDS

Explanation: The screen name is not found in thetable SCREENS.

Action: Contact TIBCO Support.

No Definition Rights on table % to bedeletedSource: Promotion

Explanation: You cannot request the deletion ofthe table because you have the wrong type ofpromotion rights.

Action: You can get Definition Rights, which willallow you to request deletion of the table, byusing the Table Definer.

No definitions were LOADEDSource: Unload/Load

Explanation: No definitions were loaded.Occurrences of tables, but not the definitions,may have been loaded, and will bementioned by other messages.

Action: No action required.

No document to deleteSource: Character-based Text Editor

Explanation: You issued the DELETE primarycommand but did not specify the documentto be deleted.

Action: Specify the document to be deleted.

TIBCO Object Service Broker Messages Without Identifiers

Page 285: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 271

No eligible change requests exist for theselected source nodeSource: Promotion

Explanation: You are attempting to create aconsolidated change request but the sourcenode you selected for included changerequests contains none that are eligible.Change requests must be promoted beforethey may be included in another changerequest.

Action: Promote change requests you wish toinclude before creating the consolidatedchange request.

No field dictionary definition to deleteSource: Field Dictionary

Explanation: A request was made to delete afield from the global field dictionary. No suchfield existed in the dictionary.

Action: No action required.

No field has been selected forSIXBUILDSource: Batch Control Card

Explanation: You tried to prepare control cardsfor the S6BBRSIX/ hrnbrsix utility withoutselecting a field for secondary indexbuilding.

Action: Select a field for a secondary index build.

No field to be CUT at the cursorpositionSource: Screen Definer

Explanation: You pressed <PF5> to cut a field,but the cursor is not positioned on a field.

Action: Position the cursor on the field to be cutand press <PF5> again.

No field to be CUT at the cursorpositionSource: Screen Definer

Explanation: You pressed <PF5> to cut the field,but the cursor is not positioned on a field.

Action: Position the cursor on the field to be cutand press <PF5> again.

No field to be DELETED at the cursorpositionSource: Screen Definer

Explanation: You pressed <PF18> to delete afield, but the cursor is not positioned on afield.

Action: Position the cursor on the field to bedeleted and press <PF18> again.

No field to be DELETED at the cursorpositionSource: Screen Definer

Explanation: You pressed <PF18> to delete afield, but the cursor is not positioned on afield.

Action: Position the cursor on the field to bedeleted and press <PF18> again.

TIBCO Object Service Broker Messages Without Identifiers

Page 286: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

272 |

No fields copied; relocate the cursorposition.Source: Report Definer

Explanation: When you copy fields into the table,they are positioned beginning at the cursorposition. You put the cursor into a positionwhich did not allow enough room for thefields being copied.

Action: Repeat the command with the cursor in aposition which accommodates all the fieldsbeing copied, or copy fewer or smaller fields.

No fields defined for table "%"Source: TAM

Explanation: A table without fields was definedin a rule.

Action: Correct the table definition in theappropriate rule so that at least one fielddefinition exists.

No fields defined for tableSource: TDS

Explanation: No field entries can be found for theModel 204 table definition.

Action: Use the Table Definer to verify or recreatethe table definition.

No fields defined for tableSource: TDS

Explanation: The IMS table does not have anyfields defined.

Action: Check the IMS table definition.

No fields defined for tableSource: TDS

Explanation: The specified DB2 table does nothave any fields defined.

Action: Check the DB2 table definition.

No fields selected for COPYSource: Report Definer

Explanation: A COPY command was issued anda prompt of available fields was displayed.No fields were selected from this display.

Action: No action required.

No fields selected for COPYSource: Screen Definer

Explanation: In the Screen Table Painter, yourequested the loading of part of a tabledefinition, but did not select any fields to becopied.

Action: No action required.

No further help is availableSource: Field Help for Reference

Explanation: You issued a request for Help, butno further Help exists.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 287: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 273

No IMS databases defined in systemSource: Table Definer

Explanation: No IMS database definitions existin the current MetaStor. IMS definitions mustbe imported into the MetaStor before anyIMS tables can be defined.

Action: Contact the System Administrator tohave an IMS database definition importedinto the MetaStor through the IMS utility.

No IMS segments defined for tableSource: TDS

Explanation: The IMS table is defined incorrectly.

Action: Check the IMS table definition.

NO IN-DOUBT TRANSACTIONSOUTSTANDING AT THIS TIMESource: S6BTLADM - INDOUBT TRX

Explanation: You requested the list of current in-doubt transactions. At the time the requestwas received, there were no in-doubttransactions and Fail Safe transactions inprogress.

Action: No action is required.

No index on library "%"; press PF5 tobuild indexSource: Global Cross Ref. Search

Explanation: You have entered the name of alibrary for which there is no index to search.You can build an index by pressing PF5. If thelibrary is large, this may tie up your terminalfor some time.

Action: If you want to search this library, pressPF5 to build the index, or use another tool,such as SEARCHLIB, which does not use anindex.

No information in message logSource: Session Manager

Explanation: You pressed <PF2> but there isnothing in the message logs.

Action: No action required.

No instances match the SELECT requestSource: Unload

Explanation: You specified a pattern and aparameter name and requested that any datainstances which match the specificationbecome selected in this screen. No instanceswere found that match your specification.

Action: Recheck the pattern you have specifiedas well as the parameter name you expect tofind the pattern in. If they are correct, thenthere is no such instance.

No instances satisfy the FIND requestSource: Unload

Explanation: In INSTANCE SELECT you issueda FIND request after specifying theparameter and value to look for. No instanceswere found that match the request.

Action: No action required.

No key field defined in "%"Source: TAM

Explanation: The definition for the subview tabledoes not contain a primary key.

Action: Modify the definition of the subviewtable so that it contains a primary key.

TIBCO Object Service Broker Messages Without Identifiers

Page 288: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

274 |

No local variablesSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

No logs foundSource: Promotion

Explanation: You requested to view, print, ordelete the logs for an activity on a changerequest but no logs were found. This willoccur if the activity does not produce anylogs (e.g., SAVE, SUBMIT). It will also occurif the SAVE LOGS flag in@PROM_CONSTANTS is not set. Finally, itmay be that the logs have been deleted byyour Promotion Administrator.

Action: Verify that the activity produces logs.Check the SAVE LOGS flag in@PROM_CONSTANTS for the activity andmake sure it is set to Y.

No longer existsSource: Select Data

Explanation: This occurrence no longer exists.

Action: No action required.

No manual set connects found for thisrecordSource: Table Definer

Explanation: There are no optional manual setsinvolved with this record.

Action: No action required.

No mask can be generated for field "%"of type "%" syntax "%"Source: Report Generator

Explanation: You selected a mask but placed thecursor on a nonnumeric field.

Action: Select a mask again and place the cursoron a numeric field.

NO MORE DATA TO BE DISPLAYEDSource: S6BTLADM - COMMON MESSAGES

Explanation: The available data is exhausted.

Action: No action required.

No more dependent segmentsSource: Table Definer

Explanation: The segment that you selected withyour cursor before you pressed <PF6> doesnot have any child segments. You havereached the bottom level of the current IMSaccess path.

Action: No action required.

No more information availableSource: Session Manager

Explanation: You pressed <PF2> but there is noother message log to display.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 289: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 275

No more than % allowedSource: Table Definer

Explanation: Table definition exceeded the limitas indicated in the message. For example,you can only define one Address parameterin a MAP table definition.

Action: Reduce to the specified limit as indicatedin the message

No more than 4 parameters are allowedSource: Table Definer

Explanation: You marked more than 4 DB2 fieldswith a P.

Action: Remove the excessive P line commands.

No need to copy "%", source anddestination are the sameSource: Copy Definition

Explanation: There is no need to copy thespecified object because the source and thedestination are the same.

Action: No action required.

No need to copy % "%"; source anddestination are the sameSource: Copy Definition

Explanation: You have specified the copy in sucha way that an object will be copied to itself,resulting in no change. Therefore the object isnot copied.

Action: Change the source or destination of thecopy.

No object of type % found to matchrequested nameSource: Security

Explanation: You requested a SEARCH in theTransfer Ownership screen, but nothing wasfound to match the requested pattern orname.

Action: No action required.

No objects are found under thisselection specificationSource: Object Selector

Explanation: You are trying to search for objectsthat match the selection specification. Noobjects are found.

Action: No action required.

No objects foundSource: Object Manager

Explanation: The Object Manager found anempty list.

Action: No action required.

No objects selected forpromotion/deletionSource: Promotion

Explanation: You submitted a change request butdid not select any rules, screens or reports forpromotion or deletion.

Action: Specify at least one object to promote ordelete. If you need more information aboutselecting objects, press <PF1> for Help or seethe Promotions manual.

TIBCO Object Service Broker Messages Without Identifiers

Page 290: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

276 |

No objects were UNLOADEDSource: Unload/Load

Explanation: No objects were unloaded.

Action: No action required unless there are errorsreported in other messages.

No occurrence foundSource: Table Editor

Explanation: States that a FIND or CHANGEcommand did not locate any occurrences.

Action: No action required.

No occurrence foundSource: Secure Audit Log

Explanation: The FIND command that youissued did not locate any occurrences.

Action: No action required.

No occurrences found in % where %Source: Delete Definition

Explanation: You are trying to delete a table butthe table is empty.

Action: No action required.

No occurrences loaded for table %Source: Unload/Load

Explanation: A security violation occurred. Thetable occurrences cannot be loaded.

Action: Ensure that you have the proper securityclearance for the objects that you are loading.

No occurrencesSource: Table Editor

Explanation: One of the following occurred:

• The table, or the instance of a table, thatyou are attempting to browse or editcontains no occurrences.

• You have requested a selection which nooccurrences satisfy.

Action: No action required.

No options list for this fieldSource: Batch Submission Tool

Explanation: No option list is associated with thefield where the cursor is placed.

Action: No action required.

No other Screens reference "%"Source: Screen Definer

Explanation: You requested a list of Screensreferring to a specified screen table, but sincethe date given, no screens fit the description.

Action: Check again after a new Cross Referencehas been run.

No parameter for COPY commandSource: Table Definer

Explanation: When you use the COPYcommand, provide the source MetaStor IMStable name. Note that the source table musthave a type of IMS; no other types areallowed.

Action: Enter the COPY command againfollowed by a valid MetaStor IMS tablename.

TIBCO Object Service Broker Messages Without Identifiers

Page 291: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 277

No parameter value to selectSource: Unload/Load

Explanation: You did not select parametervalues. UNLOAD will export all of theparameter values.

Action: No action required.

No parm table exists for "%", unable tocopySource: Copy Definition

Explanation: Could not find the parameter tablesassociated with the object.

Action: Quit the tool, and make sure that theparameter tables exist.

No previous commandSource: Global Cross Ref. Search

Explanation: You pressed <PF9> to recall theprevious command, but you have not yetentered a primary command in this sessionof the Search tool.

Action: You can enter a primary command.

No previous commandSource: Object Manager

Explanation: You pressed <PF9> to recall theprevious command, but you have notentered a command as yet.

Action: No action required.

No previous commandSource: Promotion

Explanation: You have attempted to recall thelast command when there have been nocommands used on this screen yet.

Action: Use this PF key when there have beenprevious commands.

No previous commandSource: Secure Audit Log

Explanation: You pressed <PF9> to recall the lastcommand but there was no previouscommand to be recalled.

Action: No action required.

No previous FIND commandSource: Object Manager

Explanation: You pressed <PF5> to repeat aFIND command, but did not enter a FINDcommand.

Action: Enter a FIND command.

No previous findSource: Global Cross Ref. Search

Explanation: You pressed <PF5> to find anotheroccurrence, but you did not enter a FINDprimary command in this session of theSearch tool.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 292: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

278 |

No previous request foundSource: Batch Submission Tool

Explanation: You tried to recall a previous batchrequest, but you did not save any previousbatch requests.

Action: No action required.

No primary key selectedSource: Table Definer

Explanation: You did not select a field to be theprimary key for the MetaStor IMS table. Theprimary key field always has the ordernumber 1.

Action: Use the S command to select the segmentthat contains the field that you want todesignate as the primary key. On the nextscreen, which lists the fields for the segment,select the key field by entering a K next to it.

No printing done because table % isemptySource: Print Table

Explanation: The specified table is empty;therefore, nothing was printed.

Action: No action required.

NO PRM table available to unload ALLINSTANCES of table "%"Source: Unload

Explanation: You have requested to unload datafrom a parameterized table. There is no PRMtable defined which lists those instances, andtherefore the data in the table cannot beunloaded.

Action: When data is to be unloaded from aparameterized table, there must be a PRMtable defined to list the instances in that table.Also, you must have authorization to READthe contents of the PRM table so that it maybe used for the unload.

No PRM table exists for "%", unable tocopySource: Copy Defn/Data

Explanation: This message indicates that datacould not be copied from a table withparameters since there is no PRM type tabledefined such that the table being copied isthe source.

Action: To copy data from the parameterizedtable using this tool, you must first define aPRM table which has the table containing thedata to be copied as the SOURCE table.

No PRM table for %; cannot extractoccurrencesSource: Promotion

Explanation: Cannot extract occurrences from aparameterized table without a PRM table forthe specified table.

Action: Define a PRM table for the specifiedtable.

TIBCO Object Service Broker Messages Without Identifiers

Page 293: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 279

No promotion rights/documentation forselected % %Source: Promotion

Explanation: No rights or documentation existsfor the specified rule.

Action: If no documentation exists, use the E linecommand; otherwise, contact the SystemAdministrator.

No promotion rights are held for %Source: Promotion

Explanation: One of the following occurred:

• Current screen is where you entered Sagainst the object type. You do not holdany promotion rights on any objects of theobject type selected.

• Current screen is an object managerscreen. You have entered an objectcommand but no promotion rights areheld for the named object.

Action: Do one of the following:

• Case 1: Choose another type of object forwhich rights may be held.

• Case 2: Choose another object.

No prompt possible for table "%" - enterparametersSource: Print Rules

Explanation: You entered the name of aparameterized table, but did not enter theparameters. You then pressed <PF5> or<PF6>. This table does not have acorresponding PRM table; therefore,prompting for parameters is not possible.

Action: Enter the parameters on the first screen.

No prompting for a rule that is calledSource: Menu Definer

Explanation: The rule for this item is to be called,and a prompt rule is specified. At present,prompting is supported only for rules thatare executed.

Action: Remove the prompt rule, or set theNEW_TRANS field to Y to execute the rule.

No READ authorization for library; rule"%" was not executedSource: Session Manager

Explanation: You specified a rule to execute atlogon time, but you do not have READaccess to the library in which the logon rule isstored. The library is probably a local library.

Action: Do one of the following:

• From an authorized user, obtain READpermission for the library containing therule, or remove the reference to the rulefrom your user profile.

• Possibly, you meant to execute a rule fromthe system or installation libraries, but thisrule also exists in the logon library. In thiscase, select another logon library.

No report media specified choose eitherprinter, screen or fileSource: Secure Audit Log

Explanation: You attempted to generate an auditlog report but you did not specify the outputmedium.

Action: Specify the output destination for thereport and try again.

TIBCO Object Service Broker Messages Without Identifiers

Page 294: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

280 |

NO RESOURCE NAME AVAILABLETO IDENTIFY DESIRED DETAIL, USETYPE LISTSource: S6BTLADM-Resource Management

Explanation: The system did not have a ResourceDetail entry name (type and group) toidentify which desired entry to display. Stepto the Detail display screen via the Type List.

Action: Select the detail entry by steppingthrough the Type and Group lists.

No result set table definitions found,use Refresh to generateSource: Table Definer

Explanation: No result set table definitions werefound for this stored procedure.

Action: Use the Refresh button to generate theresult set table definitions.

No result sets returned for the valueprovidedSource: Table Definer

Explanation: In order to describe result setcursors the stored procedure must return aresult set

Action: Enter a valid value

No rights for "%" type "%"; rights heldby %, requestor %Source: Manage Promotion Rights

Explanation: You tried to perform one of thefollowing operations on an object: OBTAINall rights, RELEASE all rights, or TRANSFERall rights. However, the promotion rights forthe object are held by other users andtherefore the operation on the object failed.

Action: Contact the person who has the rightsand, if available, have the rights transferred.

No room after this definition toINSERT a new fieldSource: Screen Definer

Explanation: You pressed <PF6> to add a fieldbut there is no room to add a field where thecursor is positioned.

Action: Put the field elsewhere, or move theother fields to allow the field to be inserted.

No room in physical record to insertoccurrence of table "%"Source: TAM

Explanation: There is no room to insert anoccurrence of the child VSAM table into thephysical record.

Action: Correct the rule which tries to insert theoccurrence.

TIBCO Object Service Broker Messages Without Identifiers

Page 295: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 281

No rule currently executingSource: Debugger Utility

Explanation: You have pressed <PF14>(EXPAND) after reaching a break eventwhere no rule is executing, for instanceTRANSACTIONEND. This providesfeedback.

Action: No action required.

No rule name provided for derivedfield "%.%"Source: TAM

Explanation: A derivation rule has not beenprovided for a derived field.

Action: Using the Table Definer, supply aderivation rule name for the field specified inthe message.

No rule to %Source: Rule Editor

Explanation: The rule you are attempting tocopy, append, or delete does not exist.

Action: Copy or append an existing rule.DELETE requires no action.

NO RULES exist in library "%"Source: Define Library

Explanation: You requested a display of thedefinition of a library that has no rules. Thismessage is issued when the empty list ofrules is displayed.

Action: No action required.

No rules to printSource: Print Rules

Explanation: You pressed <PF4>, but the list ofrules to print was empty.

Action: To see a list of rules, ensure that thelibrary name is the one that you want andpress <Enter>.

No screen for an existing menuSource: Menu Definer

Explanation: The screen for an existing menu nolonger exists.

Action: Delete the rest of the menu and startagain.

No SecAdmin was selected; DISCLAIMfunction CANCELLEDSource: Security

Explanation: The security administrator made arequest to disclaim the userid at the cursorposition, but the administrator did not selecta new SecAdmin for the user whenprompted. The disclaim was canceled.

Action: Select a new security administrator forthe user to be disclaimed.

TIBCO Object Service Broker Messages Without Identifiers

Page 296: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

282 |

No SECURITY AUTHORIZATION for"%"Source: Unload

Explanation: You have requested to unload anobject; however, you do not have theappropriate security authorization to do so.For any object you specify, you will require atleast VIEW_DEFN authorization; for data ina table, you will require both VIEW_DEFNand READ.

Action: You must remove the entry to completethe unload of any other objects you havespecified. To unload the unauthorized object,you must obtain the required permissionsfrom a person who is authorized to give themto you.

No source "%.%" found for subviewfield "%.%"Source: TAM

Explanation: The subview field definition refersto a source field name which is not in thesource table definition.

Action: Modify the source table definition so thatit contains the source fields that are referredto in the subview field definition.

No source for selected subview field"%.%"Source: TAM

Explanation: A WHERE clause or storedsubview selection refers to a subview fieldthat does not exist in the source table.

Action: Do one of the following:

• Remove the subview field reference in theWHERE clause or stored subviewselection.

• Modify the subview field name in theWHERE clause or stored subviewselection so that the field is contained inthe source table definition.

No source secondary index in CLC table"%"Source: TAM

Explanation: A calculation (CLC) table musthave a field whose source (by the samename) is a secondary index.

Action: Do one of the following:

• Change the CLC field name to one of thesource fields that are secondary indexes.

• Build a secondary index on the sourcefield.

The field whose source is a secondary indexshould have no SOURCE, SOURCENAMEand KEYTYPE in its FIELDS definition.

No source table "%" for % table "%"Source: TAM

Explanation: A subview or parameter table hasno source table.

Action: Add a source table name in the subviewor parameter table.

No statements; "%" cannot be savedSource: Rule Editor

Explanation: The rule specified has no actionsand so cannot be saved.

Action: Do one of the following:

• Insert at least one action line so that youcan save the existing rule and exit the RuleEditor.

TIBCO Object Service Broker Messages Without Identifiers

Page 297: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 283

• Use the CANCEL command to exit theRule Editor without saving the rule.

No stored procedure result sets todescribeSource: Table Definer

Explanation: The DB2 table @SYSROUTINESindicated that this procedure has zero resultsets

Action: None

No such JCL name existsSource: Batch Submission Tool

Explanation: You specified an undefined JCLname on the batch submission screen.

Action: Correct the JCL name or press <PF2> toget a list of defined JCL names.

No such OBJECT TYPE as "%"Source: Unload

Explanation: One of the objects you haverequested to unload included by referenceanother object. There is no such type as thatspecified by the reference.

Action: No action required; feedback only. Youmay want to report this to the SystemAdministrator since this indicates that thereare non-existent object types specified insome object type definition data referenceddefinitions.

No SUMMARY-BY fields for bodytable "%" when ACROSS-BY fieldspresentSource: Report Server

Explanation: Across Reports must have at leastone summarization field.

Action: Use the Report Definer to add aSUMMARY-BY field.

No table to printSource: Print Table

Explanation: <PF3> or <PF13> was pressed, butno table was specified for printing.

Action: Enter a table name or press <PF12> tocancel.

No Tables, Screens, Reports with Unit%Source: Unload/Load

Explanation: No tables, screens, or reports have aunit name that matches the specified unit.

Action: No action required.

No target specified for "%" commandSource: Table Editor

Explanation: You have pressed <PF5> to findnext, or <PF6> to change next, before issuinga FIND or CHANGE command.

Action: Give a FIND or CHANGE commandfirst, and then press <PF5> or <PF6>.

TIBCO Object Service Broker Messages Without Identifiers

Page 298: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

284 |

No target specified for "FIND"commandSource: Secure Audit Log

Explanation: You pressed <PF5> to find the nextoccurrence before issuing a FIND command.

Action: Issue the FIND command first and thenpress <PF5> to find the next occurrence.

No target specified for % commandSource: Rule Editor

Explanation: Either <PF5> or <PF6> was pressedwithout first entering a FIND or CHANGEcommand.

Action: Enter a FIND or CHANGE command.

NO TDS LOCK FOR THETRANSACTION BEING PROCESSEDSource: S6BTLADM - INDOUBT TRX

Explanation: The logical lock request wasprocessed successfully, but there were nological locks to report.

Action: No action required.

No text selectedSource: Character-based Text Editor

Explanation: When TED is executed with nullinput, you see a list of your documents tochoose from. You pressed <PF12> to exitwithout making a selection.

Action: No action required.

No tokens in TOKEN(%)Source: Rule Editor

Explanation: Internal translator error.

The message log will contain a more detailederror message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

No type PRM table found for table "%"Source: Definition Differences

Explanation: You have specified a parameterizedtable. However, to determine what all theinstances of that table are, a PRM tablehaving the specified table as SOURCE mustbe defined.

Action: Define a PRM type table having theparameterized table as a source and thenreattempt the operation.

No updates allowed on dictionary table"%(%)"Source: TAM

Explanation: You tried to change the definition ofa parameterized dictionary table.

Action: Do not update dictionary tabledefinitions.

No updates allowed on TABLES entryfor dictionary table "%"Source: TAM

Explanation: You tried to change the Table ofTables occurrence of a dictionary table.

Action: Do not update dictionary tabledefinitions by varying correspondingTABLES occurrences.

TIBCO Object Service Broker Messages Without Identifiers

Page 299: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 285

No updates to table "%"Source: Table Editor

Explanation: Informs you that you have pressed<PF3>, or entered the SAVE command,without having made any updates to thetable or the occurrence.

Action: No action required.

No user profile for %Source: Session Manager

Explanation: You tried to log on to Object ServiceBroker with a userid that has no user profile.

Action: Contact the System Administrator tocorrect or add your Object Service Brokeruserid.

NO USER SESSIONS CURRENTLYACTIVESource: S6BTLADM - USER ACTIVITY

Explanation: You requested a list of all activeExecution Environment connections; at thispoint in time there are no connectionspresent.

Action: Retry your request.

No valid destination specified forMOVE/COPY commandSource: Table Definer

Explanation: You positioned the cursor in an areawhere the lines to be moved or copied cannotbe placed.

Action: Use the cursor or line commands A or B(After or Before), to indicate where the linesare to be moved or copied.

No values match selection criteriaSource: Field Help for Reference

Explanation: No prompt values were found thatmeet the selection criteria specified.

Action: Enter an alternate selection criteria.

NO windows currently openSource: Rule Editor

Explanation: You pressed <PF15> when noWindows were open.

Action: No action required.

Node % invalid for % PromotionSource: Promotion

Explanation: Source nodename supplied forTarget Promotion matches nodename oftarget system.

Action: Either use Source Promotion or correctSource nodename.

Non-paired SO/SI in syntax W (DBCS)field "%"Source: TAM

Explanation: The syntax W field string value hasnon-matching shift-out/shift-in controlcharacter pair.

Action: Check for matching SO/SI,unintentionally SO/SI (hex 0F/0E)characters. You may also remove all SO/SI ifonly single-byte characters are to bedisplayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 300: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

286 |

Non-updateable fields must beimmediately after the key fieldsSource: Adabas Definer

Explanation: The ordering of yournonupdateable fields is invalid.

Action: Define nonupdateable fields right afterkey fields.

Non IDgen M204 table cannot have anydata parmsSource: Table Definer

Explanation: Only IDgen M204 tables cancontain parameters.

Action: If you want the data parameter, make thetable an IDgen table. Otherwise remove thedata parameter.

Not a stored procedure table definition:%Source: Table Definer

Explanation: PF9=SP_RSET is only usable forstored procedure table definitions.

Action: None

Not able to locate or start the ExecutionEnvironmentSource: Start Execution Environment

Explanation: Start Execution Environment failed.

Action: Check the Execution Environmentparameters.

Not allowed to change security group to%Source: Batch Submission Tool

Explanation: You specified an invalid securitygroup on the batch request submissionscreen.

Action: Enter one of your valid security groups.

Not allowed to delete batch queuedefinitionSource: Batch Submission Tool

Explanation: You do not have the authority todelete the definition of a batch queue. Onlyusers in the security group ADMIN areallowed to delete queue definitions.

Action: No action required.

Not cleared to use current group atremote locationSource: TAM

Explanation: A distributed data request wasattempted but the local group, userid and/orpassword is not valid at the remote location.

Action: Either retry using auserid/password/group combination that isvalid at the remote location or arrange for thesecurity administrator of the remote locationto provide a valid combination.

Not enough "%" storage for table "%"Source: TAM

Explanation: There is insufficient storage to holdthe table data.

Action: Do one of the following:

TIBCO Object Service Broker Messages Without Identifiers

Page 301: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 287

• Delete occurrences that are no longerneeded in tables of the type displayed inthis error message.

• Increase the relevant ExecutionEnvironment storage parameter value.

Not enough "%" table directory space tobind table %Source: TAM

Explanation: The internal table of EES/sessiontables is full.

Action: Do one of the following:

• Use fewer EES/session tables.

• Change the value of the TAMBSTSExecution Environment parameter toincrease the available space.

Not enough fixed storage to bind table%Source: TAM

Explanation: The storage where bound tabledefinitions and data are placed is full.

Action: Do one of the following:

• Bind fewer definitions and/or data.

• Change the REGIONTABLESIZEExecution Environment parameter toincrease the available memory.

Not enough storage to bind fixeddefinition for "%"Source: TAM

Explanation: The indicated screen requestedFIXED storage, but not enough storage wasavailable to bind it.

Action: Reset the bind for the screen or increasethe Execution EnvironmentREGIONTABLESIZE parameter.

Not enough transaction storage to bindtable %Source: TAM

Explanation: The storage where TEM tables areplaced is full.

Action: Do one of the following:

• Use fewer or smaller TEM tables.

• Change the value of the TRANMEMMAXExecution Environment parameter toprovide more space.

NOTE: definition modes can be set onlywhen ALL DATA="Y"Source: Security

Explanation: You are managing permissions for atable instance and you tried to set definitionpermissions from this screen. When youspecify a table instance, only the datapermissions are effective (READ, INSERT,REPLACE, DELETE). Definition permissionsto a parameterized table can be set only whenALL_DATA is Y.

Action: Specify appropriate data permissions inthis screen and then either update definitionpermissions for the whole table, or have anauthorized user do so. NOTE: If a user is

TIBCO Object Service Broker Messages Without Identifiers

Page 302: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

288 |

given INSERT access to a table instance, andthe user does not have VIEW_DEFN accessfor the whole table, the user cannot insertinto that table instance.

NOTE: definition modes must be setwith ALLDATA=YSource: Security

Explanation: You made a request to managepermissions for a table instance, and onlydata modes apply. If definition permissionsare to be managed, these should be done forthe whole table. Note that any users orgroups who are given data permissions to aninstance must have at least VIEW_DEFN setto Y for the whole table permission.

Action: Set data modes only in this screen, andensure that the definition modes are set in thescreen for the whole table.

NOTE: layout of LOADED screentables remains unchangedSource: Screen Definer

Explanation: In the Screen Table Painter, youloaded a table definition with a table type ofSCR. This message reminds you that thelayout of the loaded screen table stays asdefined in its stored screen table definition.

Action: No action required.

NOTE: Press <PF14> for permissionsLOST when object set ENABLEDSource: Security

Explanation: You just saved an object set enablelist when the object set was not previouslyenabled; any permissions on free objects inthe object set are wiped out of thepermissions lists. A report on permissionslost in this way is available by immediatelypressing <PF14> from the main menu.

Action: You can ignore this message, or press<PF14> to view and perhaps print the reporton lost permissions.

NOTE: Type % tables have no DATA;set DEFINITION modes onlySource: Security

Explanation: You made a request to managepermissions to a table, and the table type isTEM, SCR or RPT. Since these tables have nodata in the table data store, only thedefinition modes can be set.

Action: No action required.

NOTE: You are viewing a list of therules in library "%"Source: Define Library

Explanation: You made a request to view thedefinition of a library, and the first screenshows the list of rules in the library.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 303: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 289

Nothing has been selected forTRANSFER; to exit use CANCELSource: Security

Explanation: In the Transfer Ownership screen,you made a request to TRANSFER&EXIT,but did not select any objects to transfer.

Action: Either select an object to transfer, orcancel the operation.

Nothing is copiedSource: Copy Definition

Explanation: Nothing is copied.

Action: No action required.

Nothing to compareSource: Definition Differences

Explanation: No objects are entered forcomparison.

Action: Enter the objects and try again.

NULL can not be involved in anexpression with %Source: Static SQL for DB2 Gateway

Explanation: The specified field cannot supportNULL values; therefore, the expressioncannot be allowed.

Action: Change the definition of the field orchange the expression.

Null key value for table "%"Source: TAM

Explanation: The user tried to issue an INSERTor DELETE operation for an occurrence thathas a null primary or secondary key.

Action: Modify the occurrence to contain a non-null primary key.

Null primary key is not allowedSource: Table Editor

Explanation: You have not specified a primarykey value for this occurrence (and blanks areconsidered Null for a field of syntax C.)

Action: Provide a non-null primary key value.

Null value detected for % OF-FIELD"%" in report "%"Source: Report Server

Explanation: The Of-Field of a TOTAL orAVERAGE report function was null.

Action: Review input data for the field of thereport. If null values are possible, but a totalor average is required, use a selection stringon the report function to exclude null values.

Number of columns on a page too smallto produce report "%"Source: Report Server

Explanation: The page width of the report is toosmall to display the title column or the finalcolumn areas of an Across Report.

Action: Increase the page width to accommodatethe minimum required number of columns,or use the $RPTPARMS tool to change thewidth in the rule that prints the report.

TIBCO Object Service Broker Messages Without Identifiers

Page 304: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

290 |

Number of conditions exceedsmaximum of %Source: Rule Editor

Explanation: Number of conditions exceedsmaximum allowed in a rule.

Action: Reduce number of conditions.

Number of data parameters cannot bemore than 4 per tableSource: Table Definer

Explanation: You have defined more than 4 dataparameters for this table and this is notallowed.

Action: Delete the extra data parameters defined.

Number of decimal places must be 0 forpacked field length < 4Source: Screen Definer

Explanation: In the Screen Table Painter, youdefined a packed field with a length of lessthan 4 and a nonzero number of decimalplaces.

Action: Do one of the following:

• Change the syntax of the field to allow forthe number of decimal places required

• Change the length of the field to allow forrequired decimal places

• Change the number of decimal places to bezero.

Number of digit selectors in mask isgreater than 15Source: Builtin Routines

Explanation: You have used more than 15 digitplaceholders in a MASK specification.

Action: Correct the MASK specification.

Number of IDMS records in thissubschema: %Source: Tool for CA IDMS Data

Explanation: The number of records in asubschema is indicated when you select asubschema from the list of IDMS databasesdefined in Object Service Broker.

Action: No action required.

Number of IDMS subschemas defined:%Source: Tool for CA IDMS Data

Explanation: The number of IDMS databases(subschemas) defined in Object ServiceBroker is indicated when you select one ofthe following the menu options from theObject Service Broker/IDMS ManagerUtility:

• List IDMS Subschemas

• Delete IDMS Subschemas

Action: No action required.

Number of IDMS tables defined: %Source: Tool for CA IDMS Data

Explanation: The indicated number is thenumber of IDMS tables currently defined inthe system.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 305: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 291

Number of IMS databases defined: %Source: Tool for IMS Data

Explanation: The indicated number is thenumber of IMS databases currently definedin the system.

Action: No action required.

Number of lowest title line "#" +number of highest footing line "#" + 1 isnot < page length "#" after call to "%"Source: Builtin Routines

Explanation: Any line above the lowest title lineis considered a title line; likewise, any linebelow the highest footing line is considered afooting line.

Action: Reduce the number of title or footinglines. If you have less than 28 of these lines,increase the page length.

Number of objects not rebound = %Source: Promotions Bind Tools

Explanation: Errors were encountered whenattempting to rebind some objects.

Action: Review the output of @PROMBINDOBJSfor list of objects not rebound and the reasonsfor the failures. Resolve the reasons for thefailures and re-run @PROMBINDOBJS.

Number of objects not unbound = %Source: Promotions Bind Tools

Explanation: Errors were encountered whenattempting to unbind some objects.

Action: Review the output of@PROMUNBINDOBJS for a list of objectsnot unbound and the reason for the failure. Ifyou require these objects to be unbound,resolve the reasons for the failures then run@PROMBINDOBJS and re-run@PROMUNBINDOBJS.

Number of parms must be % for sourcetable "%"Source: Table Definer

Explanation: You specified too many or too fewparameters for the indicated source table.

Action: Specify the indicated number ofparameters for the source table.

Number of rows on a page too small toproduce report "%"Source: Report Server

Explanation: The page length defined in thereport is too small to allow the report to beprinted.

Action: Increase the page length to allow theprinting of at least one body report table on areport page.

Number of seconds cannot be negativeSource: Batch Submission Tool

Explanation: You entered a negative value in theduration field. The valid range is from 0 to32400.

Action: Enter a value in the valid range.

TIBCO Object Service Broker Messages Without Identifiers

Page 306: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

292 |

Number of TITLE ROWS required forthis table is "%"Source: Report Definer

Explanation: A titles report table (TITLEONLY=Y) must define every row that has areport field as a title row.

Action: Change the number of TITLE ROWS tothe number specified in the message.

Numbering for entries must beconsecutive: 1..%Source: General Table Definer

Explanation: You are supposed to assignconsecutive numbering to the list of entrieson the screen; however, the numbering is notconsecutive.

Action: The entries should be numbered so thatthere are no gaps in the numbering.

Numbers of %s loaded and defineddiffer for table "%"Source: Builtin Routines

Explanation: The table definition or theprocessed program was modified since thelast pass through the preprocessor.

Action: Preprocess again.

TIBCO Object Service Broker Messages Without Identifiers

Page 307: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 293

Messages beginning with: O

OAI Server Error: Invalid data receivedon connectionSource: ActiveX Adapter Server

Explanation: The header for the data being sentor received is invalid.

Action: Contact TIBCO Support.

OAI Server Error: OAI client version #.#is not supported by this ExecutionEnvironmentSource: ActiveX Adapter Server

Explanation: The version of the ActiveX Adapterclient is not compatible with the version ofthe Execution Environment.

Action: Upgrade your ActiveX Adapter client toa more current version.

OAI Server Error: Screentable '%' not inactive screen '%'Source: ActiveX Adapter Server

Explanation: The screentable requested by theActiveX Adapter client is not in the list ofscreentables for the current active screen.This can happen if an ActiveX Adapter clientrequests a screentable data from a previousscreen during the display of the currentscreen and OAIBLOCKFACTOR is set toolow (or set to the default value).

Action:

1. Avoid fetching data from screen other thanthe active/displayed one

2. Set OAIBLOCKFACTOR=32000 so that allscreen data is retrieved and buffered in theActiveX Adapter client without needingsubsequent requests to the ActiveXAdapter server.

3. Contact TIBCO Support.

OAI Server Error: System operationfailed, '%'Source: ActiveX Adapter Server

Explanation: An internal system call failed. Thename of the system call is given in themessage.

Action: Contact TIBCO Support.

OAI Server Error: Unable to compressdataSource: ActiveX Adapter Server

Explanation: The ActiveX Adapter CompressionEngine could not compress the requesteddata, probably due to an internalprogramming error.

Action: Contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 308: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

294 |

OAI Server Error: Unable todecompress dataSource: ActiveX Adapter Server

Explanation: The ActiveX Adapter CompressionEngine is unable to decompress therequested data, probably due to an internalprogramming error.

Action: Contact TIBCO Support.

OAI Server Error: Unable to initializecompression engine, level = #Source: ActiveX Adapter Server

Explanation: The ActiveX Adapter compressionengine could not be initialized.

Action: Contact TIBCO Support.

Object "%" does not exist in "%"Source: Definition Differences

Explanation: An object does not exist in thespecified library, environment or a location.

Action: Check to see whether the object is reallylocated in the specified library, environmentor location and try again.

Object "%" in LIST1 and object "%" inLIST2 are alikeSource: Definition Differences

Explanation: The objects that you compared arealike.

Action: No action required.

Object "%" of type % does NOT existSource: Unload

Explanation: You have specified the name andtype of an object you wish to have unloaded;however, there is no such object of that type.

Action: Recheck the object specification to ensurethat the name is correctly spelled and that thetype is also correct. If the object indeed doesnot exist, you cannot unload it.

Object "%" requires LIBRARY to bespecifiedSource: Unload

Explanation: You have requested to unload anobject which requires the library to bespecified. For example, if you have requestedto unload a rule, you must specify whichlibrary the rule should be unloaded from. Ifyou have requested to unload an objectwhich itself contains rules, the library mustbe specified to unload the rules which arepart of that object.

Action: In the top portion of the UNLOADscreen, type the name of the library to unloadrules from.

Object "%" type "%" does not existSource: Print Definition

Explanation: An object you want to print doesnot exist.

Action: Check and see whether the object existsor not before printing.

TIBCO Object Service Broker Messages Without Identifiers

Page 309: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 295

Object "%" type "%" not printedbecause %Source: Print Definition

Explanation: The specified object is not printed.

Action: Refer to the message log to find out thereason.

Object % % does not existSource: Promotion

Explanation: The named object does not exist inthe MetaStor.

Action: No action required.

Object % % with disposition "%"already existsSource: Promotion

Explanation: An object that was marked as NEWalready exists. The list of objects in the sourcesystem does not match the actual objects onthe target system.

Action: Refer to the Promotions manual forinformation on running the GEN_SYS_TBLSrule.

Object % % with disposition "%" is notpart of the systemSource: Promotion

Explanation: An object marked as MOD(modify), DEL (delete), or DELOCC (deleteoccurrences) does not exist.

Action: Refer to the Promotions manual forinformation on running the GEN_SYS_TBLSrule.

Object % used in PR#%Source: Promotion

Explanation: The specified object that you wantto back out is used in a later change request.

Action: No action required.

Object '%' is copied to '%'Source: Copy Definition

Explanation: Informs you that the object hasbeen copied to the destination.

Action: No action required.

Object '%' not copiedSource: Copy Definition

Explanation: Informs you that the specifiedobject is not copied.

Action: No action required.

Object '%' type '%' deletedSource: Delete Definition

Explanation: You are trying to delete an objectand the operation is successful.

Action: No action required.

Object '%' type '%' does not existSource: Delete Definition

Explanation: You are trying to delete an objectbut the object does not exist.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 310: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

296 |

Object command failed: %Source: Object Manager

Explanation: A condition prevents the linecommand from being executed. A systemmessage follows this message and specifiesthe condition, such as locking or the rule toexecute does not exist.

Action: Correct or cancel the command.

Object list % deletedSource: DEFINE_OBJLIST Tool

Explanation: Confirms that the indicated objectlist is deleted at your request.

Action: No action required.

Object list % savedSource: DEFINE_OBJLIST Tool

Explanation: Confirms that the indicated objectlist is saved at your request.

Action: No action required.

Object list deletion cancelledSource: DEFINE_OBJLIST Tool

Explanation: Confirms that the delete action iscanceled at your request.

Action: No action required.

OBJECT MODEL Table % cannot beincluded in a promotion requestSource: Promotion

Explanation: This table cannot be promotedthrough the promotion system because it isan object model definition table. That is, it isone of the tables that contain details about aspecific object type.

The relevant object model tables areautomatically promoted when a particularobject is requested for promotion andtherefore these object model tables must notbe promoted independently.

Action: Promote the required object, not theseunderlying tables.

Object name "%" invalid for breakevent "%"Source: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

Object set "%" DELETEDSource: Object Set Definer

Explanation: You have performed a delete fromthe Object Set Definer, and the object set hasbeen successfully deleted.

Action: No action required.

Object set "%" does not exist to bedeletedSource: Object Set Definer

Explanation: You were trying to delete an objectset that does not exist.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 311: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 297

Object set "%" has security enabledSource: Object Set Definer

Explanation: You cannot rename your currentobject set to the indicated object set becausethe indicated object set has its securityenabled.

Action: Choose a different name for your currentobject set.

Object set "%" SAVEDSource: Object Set Definer

Explanation: You have performed a SAVE fromthe Object Set Definer. Any changes made tothe object set are now saved.

Action: No action required.

Object set will be % once SAVEDSource: Security

Explanation: The percent sign (%) can be one ofthe following:

• ENABLED - The object set will have anenabled status when you save it.Users/groups on the Enable List willobtain those permissions specified for theobject set.

• DISABLED - The object set will have adisabled status when you save it. Theusers/groups on the Enable List will havethose permissions specified in the objectset permissions unless they have obtainedthese permissions through some otherenabled object set permissions.

Action: No action required.

Object type "%" is not protectableSource: Security

Explanation: The named object type (e.g., rule)cannot be protected by the Object ServiceBroker security system.

Action: If the object type is in error, correct it. If itis a rule, you can protect the library in whichit resides. If it is another non-protectableobject type (e.g., menu or object set,) you canprotect the underlying tables which containthe object's definition.

Object type "%" unknownSource: Copy Definition

Explanation: The specified object type is invalid.

Action: Reenter a valid object type.

Object type % name "%" not foundSource: Copy Definition

Explanation: Object type "object" is not found;i.e., rule "x" is not found.

Action: Correctly reenter the name of the object.

Object type '%' unknownSource: Print Definition

Explanation: The type of the specified object isinvalid.

Action: Check the type of the object.

TIBCO Object Service Broker Messages Without Identifiers

Page 312: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

298 |

Object TYPE and NAME or UNIT arerequired for query by objectSource: Promotion

Explanation: You are attempting to query changerequests that contain a certain object orobjects. An object search requires a validTYPE and NAME or UNIT.

Action: Fill in the missing information and trythe query again.

OBJECT TYPE DEFINITION table "%"has more than ONE Primary KeySource: Unload

Explanation: There is a problem with the objecttype definition data for an object yourequested to unload.

Action: Report this to your system administratoras there should not be a problem with thedefinition data of unloadable object types.

OBJECT TYPE is required for eachobject namedSource: Unload

Explanation: You have specified the name of anobject to unload; however, you have notspecified its type.

Action: Object names are not unique acrossobject types, so you must supply a validobject type. You can press <PF1> to get a listof valid object types.

Object TYPE must be one of: TBL, SCR,RPT, LIB, FRM, CON, APPSource: Security

Explanation: You made a request to managepermissions to an object, or you requested alist of objects (from the main menu), but yousupplied an invalid type of object.

Action: Fill in the object type before pressing<Enter> or invoking the OPTIONS function.

Objects "%" & "%" are deleted from'list1' & 'list2'Source: Definition Differences

Explanation: You are trying to delete an object onlist 1 and its counterpart on list 2 and both ofthem are deleted.

Action: No action required.

Objects are missing from selection list,due to securitySource: Object Selector

Explanation: The list of selected objects isincomplete because security prevents someobjects from appearing in the list.

Action: No action required.

Objects did not pass the checkingprocess, press <PF2> for logSource: Promotion

Explanation: Press <PF2> to see the list of objectswhich cannot be included in the changerequest.

Action: Press <PF2> to see the list and removethe objects from the change.

TIBCO Object Service Broker Messages Without Identifiers

Page 313: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 299

Objects in LIST1 and correspondingobjects in LIST2 are alikeSource: Definition Differences

Explanation: You are trying to compare two listsof objects to see whether there are anydifferences between them. The result is: thereare no differences.

Action: No action required.

Objects not loaded because action is %% %Source: Unload/Load

Explanation: These objects were not loadedbecause the action caused them to beskipped.

Action: No action required.

Objects of type "%" require a versionSource: Definition Differences

Explanation: You have specified an object forwhich version information is required toidentify the object. For example, to identify aRULE object, you must specify the LIBRARYin addition to the NAME.

Action: Specify the version of the object so it canbe identified.

Objects REPLACED because action is %% %Source: Unload/Load

Explanation: These objects were replacedbecause they collided with the database andthe action was IR.

Action: No action required.

Occurrence(s) above this screen: %Source: Table Editor

Explanation: The specified number is thenumber of undisplayed occurrences abovethe current screen. The message appears as aresult of the # primary command.

Action: No action required.

Occurrence(s) changed: %Source: Table Editor

Explanation: The specified number is thenumber of changed occurrences as a result ofa CHANGE command with the PAGE, ALL,or REST option.

Action: No action required.

Occurrence "%" in table "%" %Source: Table Editor

Explanation: Confirms that the occurrence hasbeen saved, deleted, or printed.

Action: No action required.

Occurrence not found in table "%"Source: TAM

Explanation: One of the following occurred:

1. A GET or DELETE operation specified anon-existent primary or secondary key.

2. The selection conditions could not besatisfied.

Action: Change the selection to refer to anexisting primary or secondary key value, oruse an ACCESSFAIL exception handler.

TIBCO Object Service Broker Messages Without Identifiers

Page 314: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

300 |

Occurrence not foundSource: Global Cross Ref. Search

Explanation: The FIND primary command wasunable to find an occurrence that matchedthe search criteria.

Action: No action required.

Occurrence not foundSource: Object Manager

Explanation: A FIND command has beenunsuccessful.

Action: No action required.

Occurrence not foundSource: Promotion

Explanation: The FIND command did not find amatch for the criteria you specified. If you arerepeating a previous successful find thissimply means you have reached the end ofthe list without finding another match.

Action: Verify the string you are attempting tofind is correct.

Occurrences NOT LOADED becauseaction is MI:Source: Unload/Load

Explanation: These occurrences were not loadedbecause occurrences with identical primarykeys already exist in the database.

Action: No action required.

Occurrences of table % deletedSource: Promotion

Explanation: As requested, the occurrences of thespecified table are deleted.

Action: No action required.

Occurrences only of % tablesSource: Unload/Load

Explanation: Occurrences, but not thedefinitions, were loaded for the listed tables.

Action: No action required.

Odd number of bytes between SO/SI infield "%"Source: TAM

Explanation: The syntax W field string valuecontains an odd number of bytes between anSO/SI pair (which make double-bytecharacter display impossible).

Action: Check how the field string value isassigned. Review the various stringfunctions (such as concatenation, headstring,etc.) used to derive the erroneous string.

OFFSET + LENGTH > LENGTH(STRING)Source: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 315: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 301

Offset calculated from "%"Source: Table Definer

Explanation: Offset has been calculated at yourrequest.

Action: No action required.

OFFSET CANNOT BE NEGATIVESource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

ONE and ONLY ONE selected rule toexecute must be entry levelSource: Promotion

Explanation: Of the rules that you have markedwith the X line command, only one can, andmust, have a Y in its ENTRY field. It must callall the other rules marked with an X.

Action: Mark only one X rule with a Y in theENTRY field.

One field must be defined as theprimary keySource: Table Definer

Explanation: The MetaStor requires that alltables have a primary key field.

Action: Use the K line command to specify whichfield is the primary key.

One of the fields must be a primary keySource: Table Definer

Explanation: You did not enter a P in the KEYfield for any of the fields defined.

Action: Enter a P in the KEY field for a field thatyou want to be the primary key. Ensure thatthis field is at the top of the list of fields. Youcan find more information about primarykeys in the Managing Data manual.

One scrolling screen table is required ifscroll entry usedSource: Screen Definer

Explanation: You have defined your screen tohave a scroll entry but not provided ascrolling screen table.

Action: Define one of your screen tables to scroll,or delete the information in the SCROLLAMOUNT ENTRY specification.

Only 1 primary key is allowed per tableSource: Table Definer

Explanation: A MetaStor IMS table can have onlyone primary key.

Action: Unselect the previously selected key field(line command D), or select it as an ordinaryfield (line command S).

Only first 200 valid values shown; useselection to see othersSource: Field Help for Reference

Explanation: The prompt screen is filled with thefirst 200 valid values.

Action: Enter a valid selection command to seeadditional prompt values.

TIBCO Object Service Broker Messages Without Identifiers

Page 316: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

302 |

Only IDMS CALC keys can be selectedas parametersSource: Table Definer

Explanation: The MetaStor parameter can onlybe an CA-IDMS CALC key. If compositeCALC keys exist, select all composites asparameters.

Action: Choose CALC field in the first IDMSrecord as data parameter.

Only INSERT and PRINT tableaccesses are supported for a report tableSource: Report Server

Explanation: The Report Server was passed aninvalid table access code.

Action: This is an internal Object Service Brokererror; contact TIBCO Support.

Only line command allowed for thisrow: "I"Source: Table Editor

Explanation: You have entered a line commandother than I in the first line command area.All other line commands are not allowed inthis area.

Action: Change the line command to I or removethe line command from this area.

Only literal source definitions mayexceed 255 charactersSource: Report Definer

Explanation: Source definition value is too large.Only a literal can be greater than 255characters.

Action: Change the source definition value.

Only occurrences for selected parmvalues are unloadedSource: Unload/Load

Explanation: You have unloaded some of theoccurrences of a parameterized table.

Action: No action required.

Only one count field is allowedSource: Table Definer

Explanation: You specified more than one countfield.

Action: Use the Delete line command (D) toremove any extra count fields.

Only one data parameter can bespecified for % tableSource: Table Definer

Explanation: You have specified more than onedata parameter for the given table type.

Action: Delete the extra parameters defined.

Only one group may be selectedSource: Adabas Definer

Explanation: You selected more than onerepeating group. This is an invalid selection.

Action: Select one repeating group only.

Only one IDgen key is allowedSource: Table Definer

Explanation: You can specify only one key fieldfor an IDgen table.

Action: Remove any additional P designationsfrom the fields.

TIBCO Object Service Broker Messages Without Identifiers

Page 317: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 303

ONLY ONE ITEM MAY BE CHANGEDIN A SINGLE REQUESTSource: S6BTLADM - SEGMENT/DASD

Explanation: You have attempted to make toomany changes within a single updatefunction.

Action: Retry your changes but restrict yourrequest to one action at a time.

Only one key field is allowedSource: Table Definer

Explanation: You cannot select any moreprimary key fields because only one primarykey field is allowed, and it is preselected foryou.

Action: Remove the primary key selectioncommand (K).

Only one location parameter is allowedSource: Table Definer

Explanation: You have specified more than onelocation parameter for the table. Each tablecan have only one location parameter.

Action: Delete the additional location parametersof the table.

Only One MU field can be selectedSource: Adabas Definer

Explanation: You selected more than one MUgroup field. This selection is invalid.

Action: Select only one MU group field.

Only one non-titles report table isallowed per reportSource: Report Definer

Explanation: Only one fixed report table within areport can be defined with TITLE ONLY=N.This report table can then have multipleoccurrences and control information (e.g.,SORT, BREAK).

Action: Ensure that all TITLE ONLY=Y except forone report table.

Only one primary key can be selectedSource: Table Definer

Explanation: You have selected more than oneprimary key.

Action: Make the necessary corrections.

Only one primary key is allowedSource: Table Definer

Explanation: A composite key is not supportedfor this type of table.

Action: Remove all but one P from the KEY fieldof the Table Definer.

Only one scrollindicator field may bemarkedSource: Screen Definer

Explanation: In a screen, one scroll indicator isallowed.

Action: Unmark all scroll indicators but one.

TIBCO Object Service Broker Messages Without Identifiers

Page 318: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

304 |

Only one statement per line is allowedSource: Rule Editor

Explanation: There is more than one statementending in semicolon (;) or a colon (:) on a line.

Action: Separate the statements so that there isonly one statement to a line.

Only one table can be specified forBatch Unload.Source: Batch Control Card

Explanation: You specified more than one tablefor your control card. The Batch Unloadutility for unloading data from the MetaStoraccepts only one table at a time.

Action: Specify one table only for your controlcard.

Only one target allowed for move andcopySource: Character-based Text Editor

Explanation: Lines that you move or copy are allplaced in one position marked by A, B, or thecursor. More than one position is marked.

Action: Remove all but one target.

Only parameters allowed forGETNEXT; % is not a parameterSource: HLIPREPROCESSOR

Explanation: Only table names and parameterscan be specified on a GETNEXT.

Action: Correct the GETNEXT statement.

Only TDS tables can be clearedSource: Table Editor

Explanation: You attempted to clear a nonnativeObject Service Broker table. Only nativeObject Service Broker tables (i.e., tables thatstore their data physically in the ObjectService Broker database) can be cleared byusing CLRTAB.

Action: A nonnative Object Service Broker tablecan be cleared by executing the ruleCLEARTABLE_APPL.

Only TDS tables can be movedSource: Table Editor

Explanation: Your request to move a nonnativeObject Service Broker table was rejected.Only native Object Service Broker tablescontain data that is stored physically in theObject Service Broker database; thus, onlynative Object Service Broker tables can bemoved.

Action: Do not attempt to move nonnative ObjectService Broker tables.

Only TDS tables can have secondaryindexesSource: Table Editor

Explanation: Your attempt to build a secondaryindex on a non-TDS table was rejected.Secondary indexes are only supported onTDS tables.

Action: Do not attempt to build a secondaryindex on a non-TDS table.

TIBCO Object Service Broker Messages Without Identifiers

Page 319: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 305

Only the OWNER may allowCONTROL access to an objectSource: Security

Explanation: You are authorized to control anobject and you were in the ManagePermissions function when you tried toextend that control access to another user.However, only the owner of the object, theowner's Security Administrator, and level-7users may pass control in this way.

Action: Set the control permission to N orremove the entire row. If you want to providecontrol access to another user, consult a userwho is authorized to pass control.

Only the select ("S") line command isallowedSource: Object Selector

Explanation: The only line command permittedis S (Select).

Action: Use only the S line command.

Only the select ("S") line command isallowedSource: Select Data

Explanation: You are only allowed to use theselect ("S") line command.

Action: Either "blank out" the line command, ortype an "S" in the line command.

Only valid for owner setsSource: Table Definer

Explanation: The SHOW IF NO OWNER optionis only valid where:

• Owner records are retrieved using anObtain-Owner GET and FORALLdirectives, and

• The set membership is Optional orManual.

Action: Specify valid values for SHOW IF NOOWNER field.

Open error on DBID - % FILE NO. - %Source: Adabas Extract

Explanation: Unable to open the specified DBIDand File No in ADABAS.

Action: Review the returned response code in themessage to determine the appropriate actionrequired to fix the problem with ADABAS.

Open failed "%" dataset; module "%";R15 = %Source: Session Manager

Explanation: Open of sort work file failed. TheDDNAME, the module name, and the returncode are supplied for debugging purposes.

Action: Call your system administrator to checkthe return code in Register 15 against theappropriate vendor's manual. Correct theproblem as required.

Open for file "%" failedSource: Builtin Routines

Explanation: Open of the named file failed. Formore error messages explaining the cause forthe open error, refer to the operating systemlog.

Action: Call your system administrator forassistance.

TIBCO Object Service Broker Messages Without Identifiers

Page 320: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

306 |

Open of a print file for report "%"failed: %Source: Report Server

Explanation: The Report Server cannot open aprint file for a report output media of PRT.

Action: Use the system message appended to thismessage to determine the action to take.

Open of an output dataset for report "%"failed: %Source: Report Server

Explanation: The Report Server cannot open afile as a report output media.

Action: Use the system message appended to thismessage to determine the action to take.

OPERATOR COMMAND NOTCONFIRMED, REQUEST IGNOREDSource: S6BTLADM - OPERATOR FUNCT

Explanation: The operator function youpreviously requested was not confirmed, ithas been abandoned.

Action: No action required.

OPERATOR COMMAND NOTSUPPORTED THROUGH THISFUNCTIONSource: S6BTLADM - OPERATOR FUNCT

Explanation: Only the highlighted operatorcommands can be supported via theAdministrator operator function. Therequest you have selected should either behandled through the function indicated inbrackets or through the operator console.

Action: No action.

ORDER field "%" not found in table"%"Source: TAM

Explanation: An ordering field in a table requestor in a stored ordering is not defined in thetable.

Action: Do one of the following:

• Include the ordering field in the tabledefinition.

• Use a different ordering field.

ORDER field "%.%" has invalidLENGTH, DECIMAL, SYNTAX orPOSITIONSource: TAM

Explanation: The specified field has invalidattributes. The table definition was probablyaltered without using the Table Definer.

Action: Use the Table Definer to correct theattributes of the order field.

Ordered GET not allowed becauseordered FORALL in progress for table"%"Source: TAM

Explanation: You issued a GET statement with aWHERE clause that specifies a field that isordered (in the table definition), and thisGET statement falls within a FORALL loop.This kind of GET statement is not permittedwithin a FORALL loop.

Action: Move the GET from within the FORALLloop, or remove the ordering from the field.

TIBCO Object Service Broker Messages Without Identifiers

Page 321: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 307

Ordering "%" is invalid - must be"A"scending or "D"escendingSource: Report Generator

Explanation: The specified ordering indicator isinvalid; it must be either A (Ascending) or D(Descending).

Action: Use A or D only.

Ordering error for table "%" - sequencenot A or DSource: TAM

Explanation: The ordering for a field must beeither A (ascending) or D (descending).

Action: Do one of the following:

• Modify the appropriate rule to use adifferent ordering field.

• Modify the table definition so that theordering field contains the orderingcharacter either A or D.

ORDERING field "%" not referred to infield listSource: CA Datacom Table Definer

Explanation: You have specified a field to use forordering the DAT table. The field you havereferred to is not defined in theEXTENSIONS information of the tabledefinition.

Action: You must remove the field named fromthe ORDERING part of the CORE context, oryou must include a field in the EXTENSIONScontext which has this name.

Ordering must be "A"scending or"D"escending for field %Source: Table Definer

Explanation: The order of the occurrences in thetable as determined by the indicated fieldmust be either A (Ascending) or D(Descending).

Action: Specify A or D only, or remove thespecification.

Ordering not allowed on derived field"%.%"Source: TAM

Explanation: Ordering on derived fields is notsupported.

Action: Using the traceback log, locate the rulecontaining the ordering clause and removethe reference to the derived field.

Ordering of derived field "%" is notallowedSource: Table Definer

Explanation: You cannot order a derived field.

Action: Remove the ordering specification frombeside the indicated field.

Ordering on field with syntax % is notallowedSource: Table Definer

Explanation: Ordering is not allowed on a fieldwith the specified syntax.

Action: Remove the ordering from the field.

TIBCO Object Service Broker Messages Without Identifiers

Page 322: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

308 |

Ordering string specified for access ontable "%" is too longSource: Builtin Routines

Explanation: More than 15 fields were specifiedin the table access statement.

Action: Reduce the number of fields specified.

OTMA component not properlyinstalledSource: Builtin Routines

Explanation: The Object Service Broker OTMACallable Interface component was notproperly installed. Specifically, the IBM IMSOTMA "C" stub, DFSYCRET, was not linked-in with the Object Service Broker S6BDRSESload module.

Action: Refer to the Object Service Broker installmanual or contact TIBCO Support forassistance.

OTMA request "%" failedSource: Builtin Routines

Explanation: The specified OTMA request failed.The return code and reason codes areprovided in the Map table. For anexplanation of the codes, refer to the IBM"IMS Open Transaction Manager AccessGuide and Reference" manual.

Action: Correct the error and try again.

OUT OF MEMORY: Unable toLOAD/INSERT any more occurrencesSource: Table Editor

Explanation: The table is too large for all of it tobe held in the memory allotted.

Action: Do one of the following:

• Reduce the number of occurrences, forexample use a SELECT command.

• Increase the amount of memory for theObject Service Broker session.

Output buffer overflow - no room toclear screenSource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Output buffer overflow - no room to setcursorSource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Output for % in Message LogSource: Print Rules

Explanation: You pressed <PF5> or <PF6> withHardcopy set to N. The output is either aPRINT TREE if you pressed <PF5>, or aCROSS REFERENCE if you pressed <PF6>.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 323: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 309

Output medium type in$SETRPTMEDIUM was not recognizedas an accepted valueSource: Report Server

Explanation: The second parameter in the$SETRPTMEDIUM tool is not one of:

• VISUAL (Output to Log)

• PRINTER (Output to system printer)

• DIRECTFILE (Output to named file)

• INDIRECTFILE (Output to file named invariable or ddname).

Action: Correct the second parameter in the$SETRPTMEDIUM tool to match one of theabove entries.

Output string too longSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The length of theresult of the function is greater than 16 KB.

Action: Contact TIBCO Support.

Output to either printer or data set, notbothSource: Batch Submission Tool

Explanation: You attempted to send the outputto both a printer and a data set.

Action: Send the output to only one destination.

Outstanding request(s) on queueSource: Batch Submission Tool

Explanation: You tried to delete the definition ofa batch queue, but the queue may still haveoutstanding batch requests.

Action: Ensure that no outstanding pendingbatch requests exist on the queue to bedeleted.

OVERFLOW: Total length of reportfunction must not exceed 128Source: Report Definer

Explanation: The total length of the sourcedefinition for a report function entered on thederived field derivation screen must notexceed 128.

Action: Remove some of the fields specified inyour OF or BY parameters, or shorten yourselection string. You may use a single derivedfield to contain the definition of a number offields that are defined separately.

Overflow detected when evaluatingsource of report field "%" of report table"%"Source: Report Server

Explanation: An arithmetic overflow wasdetected when a derived report field wasassigned a value.

Action: Review the source of the derived reportfield and the input data used to set its value.

TIBCO Object Service Broker Messages Without Identifiers

Page 324: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

310 |

Overflow when converting a string to anumberSource: Interpreter

Explanation: The conversion of a string yields anumber that is bigger than the maximumcurrently supported (approximately 10E75).

Action: Ensure that the string corresponds to anumber that does not exceed the maximum.

OVERLAP - Report table "%" and "%"overlapSource: Report Definer

Explanation: The indicated report tables overlapin their current definition.

Action: Change the specified row or column forthe report tables to remove the overlap.

OVERLAP : "%" in rows %-%, "%" inrows %-%Source: Report Definer

Explanation: Two report tables will overlap. Themessage indicates the rows occupied by eachreport table, with at least one row being incommon.

Action: Correct the report table definitions andensure that they do not overlap.

OVERLAP between field "%" and %"%"Source: Screen Definer

Explanation: Overlap detected between theindicated fields. The second percent sign (%)is either "literal" or "field"; the third % is theoffending field. If it is a literal, the value ofthe literal is displayed; otherwise, the fieldname is displayed.

Action: Fix the overlap problem.

Overlap exists between %(Col:%-%)and %(Col:%-%)Source: Screen and Report Painters

Explanation: The two indicated elements overlapeach other.

Action: Modify the columns/lengths of theelements so that they do not overlap eachother.

OVERLAP may not be resolved onCANCELSource: Report Definer

Explanation: CANCEL was requested when thecurrent screen was displaying the definitionof two report tables that overlap. CANCELmight not be able to resolve the overlapbecause changes to the Paint Screen havealready been saved. For example, fields wereadded.

Action: If you cannot execute the report becausethe overlap condition still exists, then returnto the Report Definer. Either change the rowand column of the report table to prevent theoverlap or move the overlapping report fieldin the Paint Screen.

TIBCO Object Service Broker Messages Without Identifiers

Page 325: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 311

Overlap not allowed for % tableSource: Table Definer

Explanation: Overlapping of external fields isnot allowed for the indicated table type.

Action: Recalculate offsets to ensure fields do notoverlap.

Overlap with %(Col:%-%) will occurSource: Screen and Report Painters

Explanation: Cannot add the field as it willoverlap the indicated element.

Action: Either relocate the indicated element oradd the field somewhere else.

Overwrite existing options of %Source: Batch Submission Tool

Explanation: The batch options specified on thescreen for the indicated rule are about toreplace the options that were savedpreviously for the same rule.

Action: Press <PF3> to save the options on thescreen, or press any other key to cancel theSAVE function.

Overwrote control table occurrence for% in %Source: Copy Definition

Explanation: Overwrote the control tableoccurrence for the specified object in thespecified control table. This is part of theaudit trail for the COPY tool.

Action: No action is required.

OWNERSHIP of selected objectsTRANSFERRED to "%"Source: Security

Explanation: You used the TRANSFER&EXITfunction from the Transfer Ownershipfunction of the main menu. Any objects thatwere selected have been transferred to thenew owner specified in the TransferOwnership screen.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 326: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

312 |

Messages beginning with: P

Packed field cannot have length greaterthan 15Source: Screen Definer

Explanation: You have defined a field to have aSYN of packed decimal but defined its lengthto be greater than 15, which is the maximumvalid length for a syntax of this type.

Action: Change the length to less than 15, orchange the SYN definition.

Pad character for "%" is not printable(decimal "#")Source: Builtin Routines

Explanation: The argument FILL of the$PRINTFIELD tool must be a printablecharacter.

Action: Supply a printable character.

Page '%' has an invalid lengthSource: Offline Utilities

Explanation: The specified page header had apage length that exceeded 4 KB.

Action: This usually indicates a corrupted page.

Page '%' has invalid type '%'Source: Offline Utilities

Explanation: The page number indicated in themessage has an invalid page type in the pageheader information. The page image isrestored and the utility continues. Thismessage is most common when pages are

encountered that were the target of a tabledelete operation. While the pages of the tableare being deleted, their page type indicator isconverted to lowercase. This may be anormal occurrence in this case.

Action: If the page type is not simply a lowercaseletter, the Pagestore may be corrupted.Validate and correct the Pagestore in thiscase.

Page file % only contains % pagesSource: Offline Utilities

Explanation: There are more pages for thespecified page file than can fit into the file.

Action: Reformat the file, expanding it enough tohold the number of pages in the file.

Page file '%' was encountered in backupsetSource: Offline Utilities

Explanation: This message is issued when a pagefile is encountered in the backup but is notavailable for processing. This can happenwhen the DBGEN definition for the segmentbeing processed does not specify enoughpage files in the ACBS= parameter.

Action: See accompanying message for furtherdetails. Respond as appropriate and rerunthe utility.

TIBCO Object Service Broker Messages Without Identifiers

Page 327: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 313

Page Length/Width must be greaterthan 0Source: Report Definer

Explanation: The page length and width must begreater than 0.

Action: Correct the page length and width.

Page length cannot be less than 1Source: Print Table

Explanation: You defined the page length to betoo small for any data to print.

Action: Make the page length 1 or greater.

Page size of report ";" too large - length* width greater than 262100 bytesSource: Report Server

Explanation: The size of the page to be output istoo large. The page size is equal to thenumber of lines on the page multiplied bythe maximum length of a line on the page.

Action: Decrease the number of lines on a page,the line length, or both.

Page width cannot be greater than 132Source: Print Table

Explanation: You defined the page to be toowide.

Action: Make the page width greater than orequal to 50 but not greater than 132.

Page width cannot be less than 50Source: Print Table

Explanation: You defined the page width to betoo small.

Action: Define the page length to be 50 or greater,but less than 132.

Page width too small to hold a TITLECOLUMN and a FINAL COLUMN forreport table "%"Source: Report Server

Explanation: The current page width does notpermit you to print the title column and thefinal column on the same page.

Action: Use the Report Definer or the$RPTPARMS tool in the rule that prints theAcross Report to increase the page width.

Page width too small to hold a TITLECOLUMN and one repeating body forreport table "%"Source: Report Server

Explanation: The current page width does notallow you to print a title column and onerepeating body report table in an AcrossReport.

Action: Use the Report Definer or the$RPTPARMS tool in the rule that prints thereport to increase the page width.

TIBCO Object Service Broker Messages Without Identifiers

Page 328: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

314 |

Parameter "%" does not exist in table"%"Source: Report Generator

Explanation: The indicated parameter namedoes not exist in the definition of theindicated table.

Action: Remove or change the indicatedparameter name.

Parameter "%" is not a correct %identifierSource: HLIPREPROCESSOR

Explanation: The name used for a parameter isnot a valid identifier in the host language.

Action: Change the name of the parameter.

Parameter "%" is not a location parm ofsource table "%"Source: Table Definer

Explanation: You have specified the givenparameter as a location parameter for thesubview table. However, the givenparameter is not a location parameter of thesource table.

Action: Check the source table definition forlocation parameter and change definition ofsubview accordingly.

Parameter "%" is not a source parm;must specify syntaxSource: Table Definer

Explanation: The parameter you specified is nota parameter of the source table therefore youmust specify a syntax.

Action: Specify a syntax for the parameter.

Parameter "%" is not defined inselection or source table "%"Source: Table Definer

Explanation: The indicated parameter does notexist in the source table nor does it appear inthe selection section of the current subviewtable definition.

Action: Do one of the following:

• Remove the parameter name from thesubview table definition.

• Change the parameter name to aparameter of the source table.

• Fill in the source parameter field with aparameter from the source table.

• Define the parameter in the selectioncriteria by relating it to one of the sourcetable fields.

Parameter "%" is specified more thanonce in the selectionSource: Batch Control Card

Explanation: You specified the indicatedparameter more than once in the selectionstring.

Action: Change the selection string so that itrefers to the parameter only once.

Parameter "%" of "%" has already beenspecifiedSource: Report Generator

Explanation: You specified the indicatedparameter name more than once.

Action: Remove one of the duplicate parameternames from the input area.

TIBCO Object Service Broker Messages Without Identifiers

Page 329: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 315

Parameter "%" of table "%" is null or anempty stringSource: Interpreter

Explanation: You tried to access a parameterizedtable, but the parameter specified cannot be anull value or an empty string.

Action: Ensure that the table parameter is neithernull nor an empty string.

Parameter % does not matchcorresponding key attributes of parenttableSource: Table Definer

Explanation: For VSAM multiple recorddefinition, each data parameter in the childtable must correspond exactly to the keys inthe parent table. In this scenario, you eitherentered an extra data parameter that does notcorrespond to keys in parent table, or theattributes do not match that of the parent.

Action: Delete extra data parameters or correctthe attributes to match that of the parent.

Parameter % is undefinedSource: HLIPREPROCESSOR

Explanation: The indicated parameter was notdefined either in the Object Service Brokerdatabase or in the DEFINE TABLE statement.

Action: Correct the definition or the accessstatement to refer to the correct parametername.

Parameter % must be Type %, Syntax %,Length %Source: Table Definer

Explanation: Parameter attributes are invalid.

Action: Define parameter attributes as indicatedin the message.

Parameter % of table % is incompatiblewith that on % systemSource: Promotion

Explanation: The specified table parameter isincompatible with the one on the specifiedsystem, so the APPLY process cannotproceed as requested.

Action: On the source system, Unaccept thechange and return it to the developer. Thedeveloper should roll back the changerequest and make the specified tablecompatible with the one on the target system.The change can then be re-extracted andreapplied to the target system.

Parameter does not exist in table %Source: HLIPREPROCESSOR

Explanation: A parameter named in the DEFINETABLE or access statement does not exist.

Action: Correct the COBOL program to agreewith the definition of the table.

Parameter error(s) for "%"Source: Builtin Routines

Explanation: The indicated Object Service Brokerroutine encountered some unresolved errorin an input argument or arguments.

Action: Ensure that all the arguments arecorrectly specified. If they are, contact TIBCOSupport.

TIBCO Object Service Broker Messages Without Identifiers

Page 330: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

316 |

Parameter length > 127; cannot beselected as parameterSource: Table Definer

Explanation: You cannot choose a field that islonger than 127 bytes to be a parameter.

Action: Use another line command so that thefield is not selected as a parameter for theMetaStor/IMS table.

Parameter list specified for access ontable "%" is too longSource: Builtin Routines

Explanation: The total length of parameters inthe table access is greater than 256 bytes.

Action: Verify the supplied parameter values.

PARAMETER must be N for a rule thatis calledSource: Menu Definer

Explanation: A rule that is called cannot bepassed arguments; therefore, PARAMETERmust be N.

Action: Correct the value of PARAMETER.

Parameter MUST be the KEY of the firstrecord in access pathSource: Table Definer

Explanation: If you want to define aparameterized IDM table, you must selectthe key of the first-level CA-IDMS record asthe parameter.

Action: Remove the P line command from thenon-key element.

PARAMETER must be Y forEXECUTE_PARSESource: Menu Definer

Explanation: When you call the special ruleEXECUTE_PARSE for your Standard SessionManager Menu, you must set thePARAMETER field to Y.

Action: Enter Y in the PARAMETER field.

PARAMETER must be Y or NSource: Menu Definer

Explanation: When ACTION is N, PARAMETERdetermines whether or not arguments arepassed to the rule being executed. Thechoices are:

• Y - Arguments are passed.

• N - Arguments are not passed.

Action: Enter a value in the PARAMETER field.

Parameter name "%" is already definedin parameter listSource: Table Definer

Explanation: The indicated parameter is definedmore than once in the same parametersection: once in the PARAMETER NAMEfield and once in the SOURCE PARM field.

Action: Remove one of the duplicate parameterdefinitions.

TIBCO Object Service Broker Messages Without Identifiers

Page 331: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 317

Parameter name "%" is already definedin selectionSource: Table Definer

Explanation: The indicated parameter name wasdefined in both the selection section and theparameter information section of the currentsubview table definition.

Action: Remove the indicated parameter namefrom either the selection criteria or theparameter information.

PARAMETER NAME must bespecified for the FIND functionSource: Unload

Explanation: In INSTANCE SELECT you haverequested a FIND. However, no parameterhas been specified which should be searchedfor the pattern provided.

Action: To use the FIND function, the name ofthe required parameter must be specified.

PARAMETER NAME must bespecified for the SELECT functionSource: Unload

Explanation: You have requested to haveparameter instances which match a patternyou have specified in the top area of thescreen. You have not specified whichparameter column to search for this pattern.

Action: The FIND/SELECT functions will searchonly one parameter value column, so youmust specify which parameter columnshould be searched.

Parameter not allowed for defn withonly 1 record selectedSource: Table Definer

Explanation: You cannot define a single recordaccess with as a parameterized table.

Action: Change the parameter to a primary key.

Parameter of % table must be syntax %,length <= %Source: Table Definer

Explanation: A parameter of the indicated typeof table is restricted to the indicated syntaxand the indicated maximum length.

Action: Modify the syntax or length or bothaccordingly.

Parameter processing errorSource: Batch Client

Explanation: Client parameters are wrong.

Action: Check the command line.

Parameter processing errorSource: Start Execution Environment

Explanation: An error occurred when theExecution Environment was processing theparameters.

Action: Check the Execution Environmentparameters.

TIBCO Object Service Broker Messages Without Identifiers

Page 332: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

318 |

Parameter selection for table "%" is notuniqueSource: TAM

Explanation: A selection (WHERE clause orstored selection) contains an ambiguouspredicate that mentions a table parameter.For example:

GET TABLE WHERE TABLEPARM = <value> AND TABLEPARM = <value2>;

Action: Use the Rule Editor or Table Definer toremove the ambiguity. For example, changethe above statement to:

GET TABLE WHERE TABLEPARM = <value>;

Parameter syntax of "V" not allowed.Source: Table Definer

Explanation: Syntax of V is not valid forparameter.

Action: Enter valid syntax for parameter.

Parameter value for the first table "%"must be specifiedSource: Report Generator

Explanation: The Generator requires allparameter values to be specified for the firstsource data table.

Action: Enter a value in the input area or selectone from the prompt screen.

Parameter value list unavailable - "%" isemptySource: Report Generator

Explanation: You cannot be prompted forparameter values because the source datatable is empty.

Action: You may want to put data in the tablebefore you complete the report definition.

Parameter value list unavailable - noPRM table for "%"Source: Report Generator

Explanation: You cannot be prompted forparameter values because a PRM table wasnot created for the indicated table.

Action: You must type in the parameter values inthe PARM VALUE field, or exit the ReportGenerator and create a PRM table for theindicated table.

Parameter values must be NULL whenALL DATA="Y"Source: Security

Explanation: You are specifying a table instanceby supplying parameter values either beforespecifying permissions to the instance, orwhile specifying table permissions for anobject set definition. You have specified thatALL DATA = Y as well as filled in somevalues for the individual table parameters.

Action: You must either specify ALL DATA = Yand leave all the parameter values blank (ornull), or you must specify ALL DATA = Nand supply values for each parameter.

TIBCO Object Service Broker Messages Without Identifiers

Page 333: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 319

Parameters cannot have access valuesSource: Table Definer

Explanation: You cannot associate a parameterfield with an IMS table access value.

Action: If you want to select a field as aparameter and that field already has anaccess value associated with it, you mustremove the access value before selecting thefield as a parameter.

Parent Name "%" and type "%" mustpoint to an object in listSource: Copy Definition

Explanation: The name of the parent and its typefor an object must also exist in the list exactlyas specified.

Action: Either enter the parent object, or set theparent only flag to N.

Parent Name "%" and type "%" mustpoint to an object in listSource: Copy Defn/Data

Explanation: You have requested to have copiesof children referenced by the copy of theparent. However, the parent specified doesnot have as a child the entry which youspecified for it.

Action: Change the parent to be one thatreferences the object copied from.

Parm#% must be name:% type:%syntax:% len:% dec:% class:%Source: Table Definer

Explanation: The attributes of the parameter thatyou entered are different from that of thesource. You cannot modify the attributes ofthe source parameter for a calculation (CLC)table.

Action: Correct the parameter's attributesaccording to the message.

Parm name is %. Will not be able tocreate PRM tbl. Rename parm?Source: Table Definer

Explanation: This is a warning message toinform you that, if the indicated parametername is used in the table definition, you willnot be able to create a PRM table based on itin the future.

Action: Rename the parameter if you will bedefining a PRM table based on the currenttable definition. Otherwise, you mayproceed.

PARMS changes IGNORED; instancepermissions already specifiedSource: Security

Explanation: You supplied parameter values forthe table instance specification in the TablePermissions screen of an object set definition.However, these specifications already exist inanother entry for the same table; therefore,the changes are ignored.

Action: Remove the entry because the tableinstance is already specified. If you want tochange the parameter values, use the PARMSfunction on the table entry again and specifya different table instance.

TIBCO Object Service Broker Messages Without Identifiers

Page 334: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

320 |

Parms of defined Table in differentorder than one loadedSource: Unload/Load

Explanation: The order of the table parametersfrom the import file is not the same as theorder of parameters for the table in the targetsystem.

Action: Ensure that the parameter definition ofthe target table is the same as the sourcetable.

PASSWORD and PASSWORD VERIFYare different; erase and reenterSource: Security

Explanation: You made a request to save youruser profile after changing the PASSWORDfield (and possibly the VERIFY PASSWORDfield). The verification failed because thevalue in the PASSWORD is different from thevalue in the VERIFY PASSWORD field.

Action: Erase and reenter values in both thePASSWORD and VERIFY PASSWORD fieldsto ensure that the password is the same inboth. Erasing the fields first is recommendedbecause overstriking a long password with ashorter password causes the new passwordto retain the end of the old password.

PASTE such that field and literal areSEPARATED by blankSource: Screen Definer

Explanation: In the Screen Table Painter, youtried to paste the content such that a literalwould occur immediately adjacent to a field(i.e., literal is immediately to the right of thefield). A blank must appear between the fieldand literal since blanks serve as fielddelimiters.

Action: Choose another place to paste into:

• One character to the left if you are pastinga field

• One character to the right if you arepasting a literal.

Permission % is not valid for % %Source: Security

Explanation: The specified object permission isnot valid for the object which is beingprotected. For example, READ access doesnot apply to the SCREEN object type.

Action: Correct the object permission.

Permissions cannot be specified forMETA-DATA tablesSource: Security

Explanation: You referred to a meta-data tablewhile requesting to manage permissions to atable object, or while specifying tablepermissions for an object set definition.Permissions cannot be specified for thesetables (e.g., TABLES, SCREENS,SCREENFIELDS, PARMS).

Action: You must remove or change the entryfrom the table permissions specification ofthe object set by replacing the table namewith blanks, nulls or another table name. Ifyou need to specify permissions for a meta-data table, contact TIBCO Support.

PF key % is not supportedSource: Global Cross Ref. Search

Explanation: You pressed a PF key that is notsupported on this screen.

Action: Choose another PF key. The valid keysare listed at the bottom of the screen and youcan press <PF1> for Help.

TIBCO Object Service Broker Messages Without Identifiers

Page 335: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 321

PF key % is not supportedSource: Session Manager

Explanation: You pressed a function key that isnot supported by the session manager.

Action: No action required.

PF key NOT supported INSIDE thiswindowSource: Rule Editor

Explanation: Rule Editor PF keys only functionwhen the cursor is outside of the window.

Action: Move the cursor and press the PF keyagain.

PHASE% failed: %Source: Promotion

Explanation: Phase 1, 2, or 3 failed and the reasonindicates which phase of the 3 apply phasesfailed and why.

Action: Based on the reason, take appropriateaction.

Phase 1 of Apply CompletedSource: Promotion

Explanation: Phase 1 of the target apply hascompleted successfully.

Action: No action required.

Phase 2 of Apply CompletedSource: Promotion

Explanation: Phase 2 of the target apply hascompleted successfully.

Action: No action required.

Phase 3 of Apply CompletedSource: Promotion

Explanation: Phase 3 of the target apply hascompleted successfully.

Action: No action required.

Physical screen buffer overflowedSource: Screen Server

Explanation: The output buffer containing datato be written to the screen is full and moredata remains to be written.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log andan exact description of what actions werebeing performed when this message wasgenerated.

Place an "S" on the option to be selectedSource: Tool for IMS Data

Explanation: A selection must be made.

Action: Type an S beside the desired option andpress <Enter>.

Place cursor %Source: Rule Editor

Explanation: If this message is:

Place cursor on object to be expanded

the cursor is not on a valid token for you topress <PF14>. If the message is:

Place cursor on line to be scrolled

you selected a scroll amount of C, but thecursor is not on the body of the rule.

Action: Do one of the following:

• Place the cursor on a valid token.

TIBCO Object Service Broker Messages Without Identifiers

Page 336: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

322 |

• Place the cursor on the body of the rule.

Place cursor on a menu option beforepressing <Enter>Source: Security

Explanation: You pressed <Enter> from the mainmenu without having the cursor on a validoption.

Action: Place the cursor on a menu option and fillin the required information before pressing<Enter>.

Place cursor on an objectSource: Global Cross Ref. Search

Explanation: You pressed <PF6> to edit anobject, but did not place the cursor on anobject.

Action: Place the cursor on the object that youwant to edit and press <PF6> again.

Place cursor on appropriate entry thenPF5 to edit or PF6 to addSource: National Lang. Support Mgr

Explanation: Instructions to user.

Action: None.

Place cursor on appropriate fieldSource: Session Manager

Explanation: You pressed <Enter> when thecursor was not on a user entry field.

Action: Move the cursor to an entry field beforeyou press <Enter>.

Place cursor on field of your choiceSource: Keyword Manager

Explanation: The cursor was not on a field whenyou pressed <Enter>.

Action: Choose any action by placing the cursoron the corresponding field and pressing<Enter>.

Place cursor on menu line to be deletedSource: Menu Definer

Explanation: The cursor was not placed on a lineof the menu items when <PF16> waspressed.

Action: Position the cursor on the line to bedeleted and press <PF16>.

Place cursor on row to be %Source: Table Editor

Explanation: Your action failed because you didnot position your cursor properly on aspecific row or occurrence.

Action: Position your cursor on a specific rowand try again.

Place cursor on row to scroll toSource: Secure Audit Log

Explanation: You specified C as the scrollamount but you did not place the cursor onthe destination row when you pressed thescroll key.

Action: Place the cursor on the row to be scrolledto and try again.

TIBCO Object Service Broker Messages Without Identifiers

Page 337: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 323

Place cursor on TABLE for whichinstances are to be SELECTEDSource: Unload

Explanation: In the UNLOAD first context, youhave requested the INSTANCE SELECTfunction. However, the cursor is notpositioned on an object entry.

Action: Position the cursor on a row whichnames a table to unload, and then request theINSTANCE SELECT function.

Place cursor on TABLE for which youwish to specify parametersSource: Security

Explanation: You requested the PARMS functionwhile specifying table permissions for anobject set definition, but the cursor is notpositioned on an entry.

Action: Position the cursor on a row containing aparameterized table name, and then requestthe PARMS function.

Place cursor on the field to %Source: Table Editor

Explanation: You have pressed the <PF18> key(exclude field) or the <PF19> key (showfield) without placing the cursor on a field.

Action: Before pressing <PF18> or <PF19>,position the cursor on the field to beexcluded or shown.

Place cursor on the menu lineSource: Menu Definer

Explanation: The cursor was not placed on amenu line when the PF key was pressed.

Action: Position the cursor and press the PF keyagain.

Place cursor on the object you wish todefineSource: Object Set Definer

Explanation: You must first place your cursor onan object before you press <PF9>.

Action: Place your cursor on the object you wishto define, then press <PF9>.

Place cursor on the table to be excludedSource: Report Generator

Explanation: The cursor must be placed on atable name before <PF23> is pressed.

Action: Move cursor to a table name, and press<PF23> again.

Place cursor on title lineSource: Menu Definer

Explanation: The cursor was not placed on a titleline when a PF key was pressed.

Action: Position the cursor on a title line andpress the PF key again.

Place the cursor on a commandSource: DEFINE_OBJLIST Tool

Explanation: You pressed either <PF4> or<PF16> to insert or delete a command line,but you did not position your cursor on theline on which the operation is to take place.

Action: Position your cursor on a specificcommand line and try again.

TIBCO Object Service Broker Messages Without Identifiers

Page 338: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

324 |

Place the cursor on a menu item beforerequesting OPTIONSSource: Security

Explanation: You requested the OPTIONSfunction from the main menu, but the cursoris not on a menu item.

Action: Position the cursor on the item for whichyou are requesting a list of options, andinvoke the OPTIONS function again.

Place the cursor on an active segment,then press <PF6>Source: Statistics

Explanation: The cursor is not positioned on ascreen occurrence for an active segment.

Action: Move the cursor to a screen occurrencefor an active segment and press <PF6> again.

Place the cursor to indicate your choiceSource: Menu Definer

Explanation: The cursor was not placed in a fieldto indicate a choice.

Action: Place the cursor and press <Enter>.

Please enter the export file nameSource: Unload/Load

Explanation: You did not provide an export filename on the entry screen.

Action: Type in a preallocated export file name.

PLEASE SPECIFY A DATASETNUMBER; SEG-DSN-ENTSource: S6BTLADM - RPP DIRECTORY

Explanation: In order to continue processing asegment and data set or a data set numbermust be specified.

Action: Supplied the required input and retryyour request.

PLEASE SPECIFY A MEMORYADDRESS TO BE DISPLAYEDSource: S6BTLADM - MEMORY DISPLAY

Explanation: You must specify the memoryaddress you wish to review.

Action: Specify the memory address start pointyou wish to view and retry the request.

PLEASE SPECIFY A PAGE NUMBER;SEG-PAGESource: S6BTLADM - PAGE IMAGES

Explanation: The segment and page numbermust be input. If omitted the segment willdefault to 0.

Action: Enter the segment and page number tocontinue.

Position cursor %Source: Table Definer

Explanation: Invalid cursor positioning.

Action: Position your cursor at the preciselocation on the screen as indicated by themessage.

TIBCO Object Service Broker Messages Without Identifiers

Page 339: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 325

Position cursor in Image Area or onexisting field definitionSource: Screen Definer

Explanation: You have pressed a contextsensitive function key but the cursor is notpositioned in either the Image Area, or theField Definition Area.

Action: Reposition the cursor.

Position cursor in paint area at row/colfor new field originSource: Report Definer

Explanation: When requesting a COPY of fieldsfrom a table (which is not a report table), thecursor position indicates the target row andcolumn for the first copied field.

Action: Place the cursor at the row or columnwhere the first field resulting from the COPYcommand is to be placed.

Position cursor on a field/literal definedin report table "%"Source: Report Definer

Explanation: An EXPAND FIELD DEFINITIONrequest was issued for a body table field fromwithin the Report Table Painter for a breaktable, or when the cursor was not positionedon an appropriate defined field.

Action: You can only request the expanded fielddefinition for a body table field from withinthe Report Table Painter for the body tableitself.

Position cursor on a LIST before youselect objectsSource: Definition Differences

Explanation: You are trying to select objects forcomparison but the cursor is not positionedat one of the two lists.

Action: Position the cursor at one of the two listsand try again.

Position cursor on a valid report table orcontrol breakSource: Report Definer

Explanation: When a Paint operation wasrequested, the cursor was not positioned on avalid report table or control break. Reporttables and control breaks must be assignednames before they can be painted.

Action: Position the cursor on a valid report tableor control break.

Position cursor on field to be deletedSource: Report Definer

Explanation: When requesting a DELETEoperation for a report table, the cursorshould be positioned on the report fieldwhich is to be deleted.

Action: Position cursor on the report field to bedeleted, and request the DELETE operationagain.

Position cursor on GROUP entry beforerequesting VIEW GROUPSource: Security

Explanation: You requested to view a Groupwithout specifying the Group to view.

Action: Position the cursor on a Group entrybefore requesting to view Group.

TIBCO Object Service Broker Messages Without Identifiers

Page 340: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

326 |

Position cursor on INSTANCE forwhich DETAIL is to be shownSource: Unload

Explanation: You have requested to see aninstance specification in detail by pressingthe DETAIL function. The cursor is notpositioned in such a way as to indicate whichinstance you wish to detail.

Action: Position the cursor on the row where theinstance required is located and then pressthe DETAIL function again.

Position cursor on starting field foroffset calculationSource: Table Definer

Explanation: Offset not calculated since cursor isnot positioned on any field in the tabledefinition.

Action: Position cursor at the starting field whereyou want offset to be calculated.

Position cursor on the ITEM you wishto removeSource: General Table Definer

Explanation: You have requested to remove anentry from some part of the core informationabout the MetaStor table you are defining.Your cursor is not positioned on an entry.

Action: Position the cursor on the same row asthe entry you wish to delete, then request toremove the item again.

Position cursor on the USERID youwish to DISCLAIMSource: Security

Explanation: A Security Administrator in aSecAdmin profile disclaimed a useridwithout indicating (by the cursor position)which userid to disclaim.

Action: Position the cursor on the userid to bedisclaimed and try DISCLAIM again.

Position cursor on title of the list fromwhich to DELETESource: General Table Definer

Explanation: You have requested to remove anentry from some part of the core informationabout the MetaStor table you are defining.You cannot remove these items, althoughyou may update them.

Action: Make the necessary updates to the itemsyou cannot remove, or leave them as is.

Position cursor on title of the list towhich to ADDSource: General Table Definer

Explanation: You have requested to updateinformation about the MetaStor tabledefinition in the core context of the genericTable Definer. You cannot update the coreinformation in this context.

Action: Use the extensions context to update thecore information as it is extended by thedefinition of the table type you are defining.

TIBCO Object Service Broker Messages Without Identifiers

Page 341: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 327

Position cursor within Paint Area atrow/col requiring shiftSource: Report Definer

Explanation: When a SHIFT operation isrequested, the cursor must be positionedwithin the Image Area. All report fields onthe indicated row at or beyond the indicatedcolumn are then shifted left for negative shiftnumbers, and right for positive shiftnumbers.

Action: Position the cursor in the Paint Area atthe row and column desired for the shift.

Position the cursor on a FieldDefinitionSource: Screen Definer

Explanation: You have pressed a context specificfunction key in the Field Definition Area butnot positioned the cursor on a field.

Action: Reposition the cursor on the appropriatefield.

Possible values for EXTRACT field areD, O, or ASource: Promotion

Explanation: You have entered an invalid valuein the EXTRACT field.

Action: Change the value in the EXTRACT fieldto D, O or A.

PREFIX must have a valid leadingcharacter and must be a length of 3Source: Static SQL for DB2 Gateway

Explanation: The 3 character prefix name for thestatic SQL handler name must start with anallowable character and must be threecharacters in length.

Action: Correct and retry.

Preprocessing completed with possibleerrors - Please check Preprocessoroutput.Source: Host Language Interface

Explanation: The Preprocessor has reported oneor more errors which could possibly becaused by invalid source code.

Action: Review the error messages in thePreprocessor output and take actionsaccordingly.

PRESENTATION ENVIRONMENT isrequired to unload SCREENSSource: Unload

Explanation: You have requested to unload ascreen; however, there is no presentationenvironment specified in the top portion ofthe screen. This information is required tofully specify the screen to be unloaded.

Action: In the top area of the screen, type in thepresentation environment.

TIBCO Object Service Broker Messages Without Identifiers

Page 342: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

328 |

Press <%> to confirm, or type"CONFIRM" at the command promptSource: Rule Editor

Explanation: This message will be appended tomessage 38 of this module. You havereceived a warning message about an actionthat is about to be performed on a rule.

Action: Press the indicated PF key or typeCONFIRM in the command line to performthe action. Press any other key to cancel theaction.

Press <PF21> for Table EditorSource: Table Definer

Explanation: You pressed <PF21> to edit tabledata. Normally the Table Definer saves thetable definition and invokes the Table Editorright away. In this scenario, the Table Defineris unable to save your table definition underyour default segment but has saved undersegment 0. The purpose of this message is toinform you of the above, and to confirm yourrequest to invoke the Table Editor.

Action: Press <PF21> to invoke the Table Editor.

PRESS key TO ABANDON PENDINGUPDATES AND requestSource: S6BTLADM-Resource Management

Explanation: The schedule screen currently hasupdates that have not been saved and yourrequest will cause those updates to be lost.

Action: Press the identified key to continueprocessing the identified request or any otherkey to abandon the request and preserve thepending updates.

PRESS PF10 TO CONFIRM COMMITSource: S6BTLADM - INDOUBT TRX

Explanation: You have requested the manualcommit of the displayed indoubt transaction.Before the request is issued you are requiredto confirm your intentions.

Action: Press PF10 to confirm your desire tocommit the transaction, press any otherfunction key to abandon it.

PRESS PF10 TO CONFIRMSCHEDULE UPDATE REQUESTSource: S6BTLADM-Resource Management

Explanation: You have requested the pendingchanges be committed to the repository,before the request is issued you must confirmyour intension by pressing PF10.

Action: Press PF10 to continue the updaterequest or any other key to abandon therequest.

PRESS PF10 TO CONFIRM USERTRACE "OFF" REQUESTSource: S6BTLADM - USER ACTIVITY

Explanation: Your have requested that the usertrace for the displayed user be turned off. Inorder to verify your intention a confirmationis required.

Action: Press <PF10> to issue the stop tracerequest. Press any other function key toabandon the request.

TIBCO Object Service Broker Messages Without Identifiers

Page 343: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 329

PRESS PF10 TO CONFIRM USERTRACE "ON" REQUESTSource: S6BTLADM - USER ACTIVITY

Explanation: You have requested that tracing bestarted for the displayed user. In order toverify your intention <PF10> must bepressed.

Action: Press <PF10> to issue the tracing request,press any other function key to abandon therequest.

PRESS PF11 TO CONFIRM CANCELUSER REQUESTSource: S6BTLADM - USER ACTIVITY

Explanation: You have requested a cancel userfunction. Before the request can be issued tothe Data Object Broker you must confirmyour intention by pressing <PF11>.

Action: Press <PF11> to issue the cancel userrequest or any other function key to abandonthe request.

PRESS PF11 TO CONFIRMOPERATOR COMMAND -Source: S6BTLADM - OPERATOR FUNCT

Explanation: You have selected the indicatedoperator function. In order to issue therequest you must first confirm yourintentions by pressing <PF11>.

Action: To issue the request press <PF11>, toabandon the request press any other functionkey.

PRESS PF11 TO CONFIRMRESOURCE DETAIL ENTRY DELETESource: S6BTLADM-Resource Management

Explanation: You have requested the deletion ofthe Resource detail entry currently beingdisplayed. In order to continue with theprocessing the request must be confirmed bypressing <PF11>.

Action: Press <PF11> to continue with theResource Detail entry delete or any other key(i.e. <Enter>) to abandon the request.

PRESS PF11 TO CONFIRMSCHEDULE DELETION REQUESTSource: S6BTLADM-Resource Management

Explanation: Before preparations to delete theschedule are performed you must confirmyour intensions by pressing PF11.

Action: Press PF11 to continue with Scheduledeletion preparations or any other key toabandon the request. NOTE: after the deleteis confirmed press PF10 to complete thedelete processing.

PRESS PF11 TO CONFIRM STOPREQUEST FOR PATH user-idSource: S6BTLADM-Resource Management

Explanation: Before the system will continue toprocess the requested stop gateway/server,your intensions must be confirmed bypressing <PF11>.

Action: Press <PF11> to confirm your desire tostop the identified path or any other key (i.e.<Enter>) to abandon the request.

TIBCO Object Service Broker Messages Without Identifiers

Page 344: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

330 |

PRESS PF11 TO CONFIRM THEDETAIL ENTRY INSERT/UPDATESource: S6BTLADM-Resource Management

Explanation: You completed valid changes to theDetail entry and requested the saving of thechanges.

Action: Press <PF11> to confirm your request orany other key (i.e., <Enter>) to abandon therequest.

PRESS PF11 TO CONFIRM YOURSTOP REQUEST FOR ALLRESOURCES WITH TYPE = typeSource: S6BTLADM-Resource Management

Explanation: You have requested that allgateways/servers with the identified type bestopped. Before the request can be honoredyou must confirm your intensions bypressing <PF11>.

Action: Press <PF11> to confirm the stop requestor another key to ignore the stop request.

PRESS PF11 TO CONFIRM YOURSTOP REQUEST FOR ALL TYPE =type,GROUP = groupSource: S6BTLADM-Resource Management

Explanation: You have requested a stop serverfor all resources in the specified type andgroup. Before the request is sent to thegateway/server, you must confirm yourdesire to stop the active paths.

Action: Press <PF11> to continue with therequest or another key (i.e., <Enter>) toabandon the request.

PRESS PF11 TO CONFIRMSource: S6BTLADM - SEGMENT/DASD

Explanation: You have requested an operationaltype function that will affect the processingin the Data Object Broker. In order for thatrequest to be submitted, a confirmation of theaction is requested.

Action: Press PF11 if you wish the functioninvoked or any other function key if youwish to abandon the request.

Press PF2 for more.Source: General

Explanation: More information is in a messagelog.

Action: Press the <PF2> key.

Press PF2 for status reportSource: Promotion

Explanation: Indicates what key to press to seethe audit trail of actions performed as a resultof the object command entered.

Action: Press <PF2> to see the audit trail.

Press PF2=LOGS for report onUNLOADSource: Unload

Explanation: You have requested to UNLOADand specified which objects to unload andthen pressed <PF3> to unload and exit. Areport was created to confirm what wasunloaded; it is available via <PF2>.

Action: To see the UNLOAD report, press <PF2>.

TIBCO Object Service Broker Messages Without Identifiers

Page 345: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 331

PRESS PF4 TO GENERATE REQUESTFORSource: S6BTLADM - DIAGNOSTIC DUMP

Explanation: Your dump request has beenreceived. Press PF4 to send the request to theData Object Broker to have the specifieddump generated.

Action: Press PF4 to send the dump request orany other function key to abandon therequest.

PREV OR NEXT REQUESTED BUTNO PAGE CURRENTLY DISPLAYEDSource: S6BTLADM - PAGE IMAGES

Explanation: You have requested a scrollingfunction; however, there is currently no pageimage being processed.

Action: No action required.

PREVIOUS BUFFER REQUESTEDFROM DISPLAY OF FIRST BUFFERSource: S6BTLADM - MEMORY DISPLAY

Explanation: You are processing a pool bufferdisplay. The buffer currently displayed if thefirst buffer. The previous buffer functioncannot be honoured.

Action: No action required.

PREVIOUS BUFFER REQUESTEDFROM DISPLAY OF FIRST BUFFERSource: S6BTLADM - PAGE DISPLAY

Explanation: PF10 has been used to request theprevious buffer whilst the first resident pagebuffer is displayed

Action: No action required.

Previous message(s) returned fromlocation "%"Source: TAM

Explanation: Advises that messages previous tothis one in the message log came from thenamed location. Remote messages referred toby this message are flagged with thecharacters " >" in columns 1 and 2.

This message is produced only duringdistributed data transactions.

Action: As indicated by the remote messagesreturned.

Primary command % not supportedSource: Field Dictionary

Explanation: You entered a command that iseither misspelled or does not exist.

Action: Press <PF1> for a list of valid commands.

Primary KEY can not be chosen fromthe parameter recordSource: Table Definer

Explanation: For parameterized IDMS tabledefinition, the primary key must be definedon the second level.

Action: Define primary key on the second levelof your access path.

Primary key cannot be on Owner recordfor parameterized tableSource: Table Definer

Explanation: You have made an invalid primarykey selection.

Action: Make the necessary corrections.

TIBCO Object Service Broker Messages Without Identifiers

Page 346: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

332 |

Primary key field must be mapped ifnot IDGENSource: Batch Control Card

Explanation: The primary key of the table to beloaded is not IDGEN and all of the key fieldsare not mapped to fields of the input file.

Action: Either map all of the key fields to fields ofthe input file or define the primary key of thetable to be IDGEN.

Primary key must be in second levelrecord for parameterized tableSource: Table Definer

Explanation: You have defined the first record inthe access path as a parameter; therefore, theprimary key must be defined in the secondrecord.

Action: Choose primary keys from the second-level IDMS record in your table definition.

Primary key must be in second levelrecord for PARM tableSource: Table Definer

Explanation: For a parameterized IDM tabledefinition, the primary key must be definedin the second record in the access path.

Action: Define the primary key in the secondrecord in the access path. Or, alternately,remove the parameter definition.

Primary key must be in the highestlevel recordSource: Table Definer

Explanation: If the CA-IDMS access path iscomposed of multiple records, you mustselect the primary key from the first level.

Action: Remove the primary key field selectionand select a primary key field from the firstlevel.

Primary key must be the first fieldSource: Table Definer

Explanation: The primary key must start fromthe first field.

Action: Move the field that you want todesignate as a primary key to the top of thelist of fields.

Print access of REPORT % by % deniedSource: Audit Log Message

Explanation: PRINT access to a report object wasdenied.

Action: The user can ask someone who hasCONTROL access to the report to providePRINT access.

Print definitions for object "%" type "%"completedSource: Print Definition

Explanation: You are trying to print an object andan object, which is defined by the object youspecified, is printed.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 347: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 333

Print definitions for object "%" type "%"partially completedSource: Print Definition

Explanation: Not all definitions of the specifiedobject are printed.

Action: Read the message log and find out whyall the definitions were not printed. Fix theproblems and try the operation again.

Print destination must be "PRT" or"SCR"Source: Print Table

Explanation: The print destination has someother value than PRT or SCR.

Action: Make the output destination the printer(PRT) or the screen (SCR).

Print failed: %Source: Rule Editor

Explanation: Internal error during printing.

The message log will contain a more detailederror message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

PRINT failed: %Source: Screen Definer

Explanation: You have tried to print out a virtuallayout and screen definition. For securityreasons you are not allowed to do this, for thenamed screen.

Action: No action required.

Print of report "%" failed; keyed dataaccess not supported for external filesSource: Report Server

Explanation: The Report Server detected aninconsistent server action.

Action: Contact TIBCO Support.

Print successfulSource: Promotion

Explanation: The print operation you started hascompleted successfully.

Action: No action required.

Print successfulSource: Secure Audit Log

Explanation: The specified selection list wasprinted as a result of the PRINT command.

Action: No action required.

PRINTDEFN failed, security failed onobject "%"Source: Print Definition

Explanation: You want to print an object.However, you do not have the authority toaccess an object which is required byPRINTDEFN to print your object.

Action: Find out what those objects are and askthe owners if they could give you access tothose objects. Retry the operation again.

Printed %Source: Print Table

Explanation: A table was printed.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 348: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

334 |

PRINTED definition of table "%"Source: General Table Definer

Explanation: You requested to print thedefinition of the table and the request hasbeen sent to the output.

Action: No action required.

PRM table is not available forparameter "%" of table "%"Source: Report Generator

Explanation: This message shows that there is noPRM table existing for the specificparameterized table.

Action: Using the Table Definer, create the PRMtable for the parameterized table.

Processing Execution Environmentstartup parametersSource: Start Execution Environment

Explanation: The Execution Environment isprocessing startup parameters.

Action: Wait until the Execution Environment isfinished the processing.

PROCESSING FAILURE REPORTEDFOR REQUEST (___), REASON CODEIS __Source: S6BTLADM-Resource Management

Explanation: When attempting to extractinformation from the Data Object Broker, anerror was detected. In the message, therequest code is one of the following:

• 004 - resource type list retrieval

• 008 - resource group list within typeretrieval

• 012 - resource detail entry retrieval

• 016 - resource schedule retrieval

• 020 - resource schedule index retrieval

• 024 - node name index retrieval

• 028 - update/insert detail entry

• 032 - associate schedule to resource detail

• 036 - update/delete schedule entries

• 040 - path list retrieval

• 044 - schedule association list retrieval

• 048 - histogram data retrieval

• 052 - delete resource detail entry

The reason code is one of the following:

• 04 - type and/or group not specified

• 08 - resource not found

• 12 - modcb for insert failed

• 16 - insert write failure

• 20 - modcb for update failed

• 24 - key read for update failed

• 28 - key write for update failed

• 32 - resource schedule entry not specified

• 36 - resource schedule entry not found

• 40 - entry erase failed

• 44 - reserved memory exhausted

• 48 - attempting to delete detail with activepaths

• 52 - request not in acceptable format

• 56 - invalid function code specified

Action: This error typically represent an internalerror which should be reported to TIBCOSupport. Before contacting Support reviewthe joblog to determine what messages wereproduced to help identify the problem. In thecase of a reason code 44 recycle the DataObject Broker, storage allocation is based ondefined configuration, you are trying toexpand the configuration beyond theallocated buffer zone.

TIBCO Object Service Broker Messages Without Identifiers

Page 349: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 335

PROFILE EXTRACT RETRIEVALERRORSource: S6BTLADM - COMMON MESSAGES

Explanation: When attempting to obtainstatistics for a profile display the retrievalfailed.

Action: Review the job log for additionalinformation and retry.

Program abnormally terminated withcode=%Source: Interpreter

Explanation: This message is used by theprogram that produces the Object ServiceBroker Information Log. More detailedmessages usually follow.

Action: Read the detailed messages that follow.

Program ADALNK must be in EXLIBlibrary concatenationSource: Adabas Extract

Explanation: Server is unable to locate programADALNK.

Action: Add program ADALNK in EXLIB libraryconcatenation.

PROM_TYPE must be "DATA"Source: Promotion

Explanation: Field RIGHTS of table@RULE_RIGHTS must be set to the characterstring DATA.

Action: Correct the field.

Promotable flag set to % for % % %Source: Promotion

Explanation: You have toggled the value of thePROM field for the specified table. This fieldindicates whether a table is promotable ornot. If you wish to change the value, use theT line command to toggle it back.

Action: No action required.

Promote selected for % % %Source: Promotion

Explanation: You have selected the specifiedobject for promotion. This object is nowincluded in the change request. It will bepromoted when the change request ispromoted. If you do not wish this to happen,use the C line command to remove it fromthe request.

Action: No action required.

Promoted %Source: Promotion

Explanation: The specified number of objectshave been promoted to the target system.

Action: No action required.

Promoted data for % tables or tableinstancesSource: Promotion

Explanation: The data of the specified number oftable or table instances has been promoted tothe target system.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 350: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

336 |

Promotion FAILED;@BORROWED_OBJ entry for object %not foundSource: Promotion

Explanation: Borrowing rights on the objectnamed were released before the promotionwas completed. The system may be in aninconsistent state.

Action: Contact TIBCO Support.

Promotion of change#% failedSource: Promotion

Explanation: The promotion of the specifiedchange has failed. The cause of the failure canbe found in the message log of thepromotion.

Action: Correct the problem described in themessage log and apply the change again.

Promotion request %Source: Promotion

Explanation: The promotion request was savedor canceled.

Action: No action required.

Promotion request % does not have theappropriate statusSource: Promotion

Explanation: Cannot accept a change requestunless the status is P. Cannot extract a changerequest unless the status is A or X.

Action: Change the status of the change requestbefore proceeding with the promotion.

Promotion request marked incompleteSource: Promotion

Explanation: The user has pressed <PF3> andsaved the change request as incomplete(Status=I). This has saved the intentions onobjects as well as any description.

Action: The user can resume preparing thischange request at a later time by entering Cagainst the CR number on the ManageIncomplete/ Pending screen.

Promotion rights for % % lostSource: Promotion

Explanation: In order to submit the CR, you needpromotion rights on the named object. Eitheryou have released/transferred rights on theobject, or you have deleted the named object,or you are continuing the CR from a differentlibrary.

Action: Check if you need this object to be part ofthe CR, and if so, ensure you have rights onthe object.

Promotion rights held by % - requestedby %Source: Table Definer

Explanation: The promotion rights of the currenttable definition are held in the indicatedlibrary by the indicated user.

Action: If you want to modify the tabledefinition, contact the indicated user to havethe rights released.

TIBCO Object Service Broker Messages Without Identifiers

Page 351: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 337

Promotion rights not obtained %Source: Rule Editor

Explanation: You do not have promotion rightsfor this rule and therefore you cannotpromote this rule to the development library.Possible reasons:

• You are not allowed to promote any rules.

• Someone else has this rule so you cannotpromote it.

• You have created a new rule and renamedit to the name of a rule that already existsin the development library. You do nothave promotion rights to this rule.

Action: Obtain promotion rights, if possible.

PROMPT must be N for a rule that iscalledSource: Menu Definer

Explanation: A rule that is called cannot havearguments; therefore, PROMPT must be N.

Action: Correct the value of PROMPT.

PROMPT must be O or N forEXECUTE_PARSESource: Menu Definer

Explanation: When you call the special ruleEXECUTE_PARSE for your Standard SessionManager menu, you must set the PROMPTfield to O or N.

Action: Enter O or N in the PROMPT field.

PROMPT must be one of O, P, NSource: Menu Definer

Explanation: When ACTION is N, the PROMPTfield requires a value to determine whetherprompting is needed or not. The choices are:

• O - Prompting displays an object list

• P - Prompting asks for the parameters ofthe rule, using the actual names of theparameters

• N - No prompting is done. The rule ispassed NULL values for each parameter.

Action: Enter the O, P, or N in the PROMPT field.

PROMPT_RULE must be one of %Source: Menu Definer

Explanation: Only certain rules can be used forprompting.

Action: Choose a rule from the list presented.

Prompting cannot be "Y" for a protectedfieldSource: Screen Definer

Explanation: If the PROTECT attribute for ascreen table is Y, the AUTOPROMPT andUSERPROMPT attributes cannot be Y.

Action: Change either the PROTECT attribute, orthe AUTOPROMPT and USERPROMPTattributes.

Protocol error obtaining definition fortable "%"Source: TAM

Explanation: The size of the parameter name isnot equal to 16.

Action: This is an internal error; contact TIBCOSupport.

TIBCO Object Service Broker Messages Without Identifiers

Page 352: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

338 |

Provide a database name; press <PF4>for DB NAMESSource: Table Definer

Explanation: You did not enter an IMS databasename in the DB NAME field.

Action: Enter a valid IMS database name, orpress <PF4> for a list of valid names andselect one from the list.

Provide a JCL nameSource: Batch Submission Tool

Explanation: No JCL name was specified on thebatch submission screen.

Action: Enter a valid JCL name or press <PF2> toget a list of all valid JCL names.

Provide a queue nameSource: Batch Submission Tool

Explanation: No target batch queue name wasspecified on the batch request submissionscreen.

Action: Enter a valid queue name or press <PF2>to see a list of valid queue names.

PSW at time of error % % ILC # INTC %Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log.

Action: For more information, show this messageto a System Programmer.

Purge and archive cancelledSource: Secure Audit Log

Explanation: You canceled the purging andarchiving of the audit log contents.

Action: No action required.

Purge batch processing finishingSource: Secure Audit Log

Explanation: This message informs you that thepurging of the audit log contents in batchmode has been completed.

Action: No action required.

Purge batch processing startingSource: Secure Audit Log

Explanation: This message informs you that thepurging of audit log contents in batch modehas started.

Action: No action required.

Put cursor on any Break/Summarysection & press % to continueSource: Report Generator

Explanation: You selected a function-field pair inthe prompt area of the Function screen, butyou did not move the cursor to abreak/summary section to indicate where toinsert the selected function-field pair.

Action: Use the cursor to indicate where to insertthe selected function-field pair, and press theindicated key to complete the specification.

TIBCO Object Service Broker Messages Without Identifiers

Page 353: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 339

Put cursor on break event in BreakeventControl sectionSource: Debugger Utility

Explanation: You have pressed <PF6> toassociate a debugger command with a breakevent. However, the cursor is not positionedin the primary command area nor on a breakevent.

Action: Verify the position of the cursor.

Put cursor on Print/Sort/Break/Across &press % to continueSource: Report Generator

Explanation: You selected a field in the promptarea of the Field screen, but you did notmove the cursor to a section (PRINT, SORT,BREAK, or ACROSS) to indicate where toinsert the selected field.

Action: Use the cursor to indicate where to insertthe selected field, and press the indicated keyto complete the specification.

TIBCO Object Service Broker Messages Without Identifiers

Page 354: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

340 |

Messages beginning with: Q

Queue "%" definition savedSource: Batch Submission Tool

Explanation: The indicated queue definition issaved.

Action: No action required.

Queue "%" deletedSource: Batch Submission Tool

Explanation: The definition of a batch queue wasdeleted as requested.

Action: No action required.

Queue name is not defined; press<PF2> for list of optionsSource: Batch Submission Tool

Explanation: The specified queue name is notdefined in the system.

Action: Correct the queue name or press <PF2>to get a list of valid queue names.

Quoted source values are only valid forliteral report fieldsSource: Report Definer

Explanation: You cannot enter a quoted sourcedefinition unless the field is a literal.

Action: Replace the quoted string with a validrule or report function.

Quoted strings now in %Source: Rule Editor

Explanation: When you enter the UPPER orLOWER command, the new status isdisplayed. For the UPPER command, % isUPPER CASE. For the LOWER command, %is MIXED CASE.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 355: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 341

Messages beginning with: R

Re-extract request cancelledSource: Adabas Extract

Explanation: Re-extract aborted by user request.

Action: No action required.

Read access to % %( % ) by % deniedSource: Audit Log Message

Explanation: READ access to this object wasdenied. If the object is a parameterized table,the value of the first parameter for this tableinstance is indicated.

Action: The user can ask someone who hasCONTROL access to the object to provideREAD access.

Read access to table "%" deniedSource: Report Generator

Explanation: Read access to the indicated table isdenied for security reasons.

Action: Remove the table from the report. If youneed that table to generate the report, contactyour Security Administrator.

Read access to TABLE %( % ) by %Source: Audit Log Message

Explanation: The user has read the given tablewith the specified parameter.

Action: No action required.

Ready mode is a required fieldSource: Table Definer

Explanation: You must enter a valid ready modeon the VERIFY ACCESS PATH screen toprepare the CA-IDMS database for a certaintype of access. Valid ready modes are:

• SR (Shared Retrieval)

• SU (Shared Update)

• PU (Protected Update)

• EU (Exclusive Update).

Action: Enter a valid ready mode.

Rebind of % "%" with FIX=% failed dueto error "%"Source: Promotions Bind Tools

Explanation: An error was encountered whenattempting to rebind the specified object.

Action: Resolve the error specified and re-run@PROMBINDOBJS.

Record and element filesincompatible...check their contentsSource: Tool for CA IDMS Data

Explanation: The data contained in the recordand element import files is not from the samesubschema.

Action: Do the following:

1. Check the contents of the record andelement files that you were going to load.

2. Use the "Load an IDMS Subschema"manager utility again to change the files

that you import.

TIBCO Object Service Broker Messages Without Identifiers

Page 356: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

342 |

Record length for table "%" is largerthan record length of VSAM % "%"Source: TAM

Explanation: The length of an occurrence in theindicated table does not equal the length of arecord in the VSAM data set. The variables,from left to right, are as follows:

1. The name of the table

2. Either "file" or "DDNAME"

3. The name of the file or the DDNAME

Action: Change the definition of the ObjectService Broker table so that the sum of thelengths of all the fields equals the actuallength of the VSAM record.

Record of % file smaller thanoccurrence size of table "%"Source: TAM

Explanation: The record size for the Import orExport table must be equal to or greater thanthe sum of the field lengths given in thedefinition of the table.

Action: Do one of the following:

• Allocate a larger record size for the file thatcorresponds to the Import or Export table.

• Reduce the total field length by changingthe definition of the Import or Export table.

REFD DATA source table "%" NOTFOUNDSource: Unload

Explanation: You have requested to unload anobject which includes by reference otherdata. The table which references the data tobe included does not exist.

Action: Report this to the System Administratoras it indicates a problem in the object typedefinition data for the object you requestedto unload.

REFD DEFN source table "%" not foundSource: Unload

Explanation: There is a problem with the objecttype specification for an object which youhave requested to unload.

Action: This should be reported to the SystemAdministrator as there should not be aproblem with the object type definitions forunloadable objects.

Reference check of "%" of table "%"failedSource: TAM

Explanation: The indicated field of the indicatedtable has an entry in the REFNAME field ofthe table definition. The table in theREFNAME field, however, is invalid.

Action: Check the REFNAME field to ensure thatyou are referring to the correct table. Alsocheck your field definition to ensure that it iscompatible with the field in the referredtable.

TIBCO Object Service Broker Messages Without Identifiers

Page 357: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 343

Reference data for '%' cannot bedeleted, error in resolvingSource: Delete Definition

Explanation: You are trying to delete a referencedata table of an object but the process fails.

Action: The utility fails to resolve the referencedata tables for the specified object.

Reference table '%' deletedSource: Delete Definition

Explanation: You are trying to delete a referencedata table of an object and the table has beendeleted.

Action: No action required.

Reference table for data parameter mustrefer to the same VSAM parent tableSource: Table Definer

Explanation: You have entered different valuesfor REFERENCE in your data parameter list.The field REFERENCE is used to store thename of the parent table used to accessmultiple record format VSAM file, andtherefore, all REFERENCE values must referto the same table.

Action: Change REFERENCE in your dataparameter list to refer to the same VSAMparent.

Reference table must be anunparameterized table of type VSMand IDGEN NSource: Table Definer

Explanation: Reference table (parent table toaccess multiple record format VSAM file) hasto be defined as a MetaStor VSM table withno data parameter and IDgen set to N.

Action: Specify a valid Reference table with nodata parameter, table type of VSM and IDgenset to N.

Reference to null in selection string foraccess on table "%"Source: Builtin Routines

Explanation: References to a NULL value are notcurrently supported in selection conditionsfor table access statements when using theHigh Level Language interface.

Action: Remove the NULL keyword.

Reference to report field "%" of reporttable "%" cannot be resolved, namerefers to itselfSource: Report Server

Explanation: A loop exists in the definition of aderived report field. The source of the reportfield refers to itself.

Action: Use the Report Definer to review thedefinition of the derived report field andresolve the name conflict.

TIBCO Object Service Broker Messages Without Identifiers

Page 358: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

344 |

Referenced data for object "%" notprinted, error in resolvingSource: Print Definition

Explanation: You are trying to print an object andan error occurred when PRINTDEFN tries toresolve the referenced data tables of thatobject.

Action: Check and see whether the referenceddata tables for that object do exist and aredefined properly. Retry the operation again.

Referenced data table "%" is emptySource: Print Definition

Explanation: You are trying to print an object anda table which is referenced by that object isempty and therefore not printed.

Action: No action required.

REGION TYPE TABLE RETRIEVALERRORSource: S6BTLADM - USER ACTIVITY

Explanation: In order to group connectionstogether a region or group code can bespecified at connection time; if omitted adefault code will be set based on theconnection type. An error was detected whentrying to retrieve the list of known regionnames.

Action: Review the joblog for possible additionalmessages which may help identify the causeof the problem. Retry your request. ContactTIBCO Support if the problem persists.

Relate Tables screen unavailable - onlyone table has been specifiedSource: Report Generator

Explanation: The Relate Tables screen isirrelevant because you selected only onesource data table.

Action: No action required.

Relation for "%" of table "%" hasalready been specifiedSource: Report Generator

Explanation: The indicated field is alreadyrelated to another field of a source data table.Each field can only be related to one fieldfrom another table.

Action: Remove one of the duplicate fields fromthe input area.

Release locks failedSource: TAM

Explanation: One of the following occurred:

1. Locks could not be released at transactionend.

2. A communicating failure occurred duringlock release initiation.

The session will be terminated but themessage can be reviewed first.

Action: Review the message log.

Contact TIBCO Support if the error is notidentifiable.

TIBCO Object Service Broker Messages Without Identifiers

Page 359: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 345

Renamed rule % is in library %.Promotion rights not obtainedSource: Rule Editor

Explanation: You have renamed a rule to a namethat exists in the Installation library. Thepromotion rights are not obtained.

Action: No action required. If you want tomodify the rule in the Installation library,you must explicitly edit it.

Renamed rule % to %Source: CHANGERULE tool

Explanation: The name of the rule was changedas one token was changed for another.

Action: None.

Repackaged % from change#%Source: Promotion

Explanation: The named object has beenrepackaged from the specified changerequest created from the specified node.

Action: No action required.

REPEAT failed - Max number of screentables has been reachedSource: Screen Definer

Explanation: The REPEAT command failedbecause the maximum number of screentables allowed for a screen has been reached.You are not allowed to add any more screentables.

Action: If you still want to use REPEAT to addanother screen table, remove or combinesome of the existing screen tables.

REPEAT TYPE must be specified forPeriod group and Multiple OccurringfieldSource: Adabas Definer

Explanation: You specified N for MU/SpecialFld in Grp which is incompatible with therepeat type. A value of N is only valid forrepeat type "GRP".

Action: Specify a value for MU/Special Fld inGrp that is compatible with the repeat type.

Repeating and non-repeating fieldscannot be mixed in the same definitionSource: Adabas Definer

Explanation: You have selected repeating andnon-repeating fields in the same tabledefinition; this is not supported in ObjectService Broker.

Action: Specify field selection by choosing onlyrepeating fields or non-repeating fields.

Repeating Group - incompatible parent"%"Source: TAM

Explanation: When a Repeating Group table isdefined its parameter must have a"reference" to a parent table. The parent tablemust not be parameterized nor can theFORALL, in which it is used to parent arepeating group FORALL, request"ordering".

Action: Correct and retry.

TIBCO Object Service Broker Messages Without Identifiers

Page 360: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

346 |

Repeating Group - parent table notfound "%"Source: TAM

Explanation: A Repeating Group Table FORALLcan only be used within a Parent TableFORALL, for example,

FORALL parent-table-name...

or

FORALL repeating-group-table-name...

No active parent FORALL could be found.

Action: Correct and retry.

Replace access to % %( % ) by % deniedSource: Audit Log Message

Explanation: REPLACE access to this object wasdenied. If the object is a parameterized table,the value of the first parameter for this tableinstance is indicated.

Action: The user can ask someone who hasCONTROL access to the object to provideREPLACE access.

Replace access to TABLE %( % ) by %Source: Audit Log Message

Explanation: The user has replaced data in thegiven table with the specified parametervalue.

Action: No action required.

REPLACE failed: table "%" notpositioned at any rowSource: Screen Server

Explanation: The rule attempted to replace anoccurrence.

The occurrence to be replaced has not beenspecified. Only the replacement data hasbeen specified.

Action: Perform a GET or a FORALL to specifythe occurrence to be replaced.

REPLACED occurrences because actionis MR:Source: Unload/Load

Explanation: These occurrences which were inthe table before loading have been replacedwith occurrences from the file because theaction was MR.

Action: No action required.

Report "%" already exists; cannotoverwriteSource: Report Definer

Explanation: The report name was changed andan attempt was made to save the currentreport definition under a new name. Becausea definition already exists for the specifiedname, the request to save has been denied.

Action: Rename the report to the original nameor a name that is not already associated witha report definition.

Report "%" cannot be referred to morethan onceSource: Security

Explanation: You referred to a particular reportmore than once while specifying reportpermissions for an Object set definition.

Action: Remove duplicate entries from the list byreplacing the report name with blanks, nulls,or another report name.

TIBCO Object Service Broker Messages Without Identifiers

Page 361: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 347

Report "%" deletedSource: Report Definer

Explanation: A DELETE operation has beenperformed.

Action: No action required.

Report "%" does not exist to be deletedSource: Report Definer

Explanation: The user tried to delete a report thatdoes not exist.

Action: Delete only those reports that have beenassigned a definition.

Report "%" does not existSource: Security

Explanation: You referred to a non-existentreport.

Action: Remove the entry or correct it.

Report "%" has been defined with morethan 24 breaksSource: Report Server

Explanation: A report can have at most a total of24 break and summary report fields.

Action: Reduce the complexity of the report byusing fewer break and/or summary fields.

Report "%" has been sent to %Source: Report Generator

Explanation: The indicated report was sent to therequested destination.

Action: No action required.

Report "%" has too many break andsummary report fields; the maximumnumber is #Source: Report Server

Explanation: The definition of the reportcontains too many break and summarycontrol fields.

Action: Simplify the report by reducing thenumber of break or summary fields.

Report "%" is undefinedSource: Report Server

Explanation: The report named does not exist.

Action: If the report name was misspelled, usethe Report Definer to determine the correctname of the report. Otherwise, use theReport Definer to create the named report.

Report "%" not deletedSource: Report Generator

Explanation: The indicated report was notdeleted because you did not confirm thedeletion request.

Action: No action required.

Report "%" not overwrittenSource: Report Generator

Explanation: The indicated report was notoverwritten because you did not press theconfirmation key.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 362: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

348 |

Report ";" can not request immediateoutput to a currently active outputmediumSource: Report Server

Explanation: Another report in the sametransaction has already requested immediateoutput to the same medium (Log, Printer orFile).

Action: Either send the reports to differentoutput media or remove one of theimmediate output requests.

Report % deletedSource: Secure Audit Log

Explanation: You confirmed a deletion requestfor a report definition. This messageconfirms that the specified report definitionhas been deleted.

Action: No action required.

Report % has already been unloadedSource: Unload/Load

Explanation: You entered a report name on theUNLOAD selection screen more than once. Areport can only be unloaded once.

Action: No action required.

Report % is not an entry in @REPORTSSource: Unload/Load

Explanation: A report by the name specified doesnot exist.

Action: Correct the report name and try again.

Report % not deleted - PF2 to check themessage logSource: Secure Audit Log

Explanation: An error occurred while deletingthe given report. Refer to the message log<PF2> for more information.

Action: Correct the errors which are described inthe message log and try again.

Report cannot be produced due to runtime errorSource: Report Generator

Explanation: The report cannot be produced dueto an internal problem.

Action: Contact TIBCO Support.

Report CTABLE too large for virtualreportSource: 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.

Report definition printedSource: Report Definer

Explanation: The report definition print has beencompleted.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 363: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 349

Report field "%" of report table "%" inerror, display masks not supported forstring valuesSource: Report Server

Explanation: The value in the indicated reportfield cannot be converted to a number.

Action: Review the source of the report field andthe input data used to set its value. Changethe display mask or the report field asappropriate.

Report field "%" of report table "%" isdefined as both an input field and aderived report fieldSource: Report Server

Explanation: A report field of a body report tablehas been defined as both an input field forthe report and a derived report field.

Action: Use the Report Definer to remove thesource string for the report field.

Report field definition required forcontrol field "%"Source: Report Definer

Explanation: A control field (e.g., SORT, BREAK)has been specified without a correspondingdefinition for the field in the Definition Area.

Action: Ensure that each field specified on thecommon screen is also in the Definition Area.

Report field name "%" is invalidSource: Report Definer

Explanation: Report field names can be amaximum of 16 characters and consists ofletters, digits, @, $, #, and underscores. Thename cannot begin with a digit orunderscore.

Action: Correct the indicated report field name.

Report function "%" must have exactlyone operand fieldSource: Report Server

Explanation: Report functions TOTAL,AVERAGE, MIN, and MAX can have at mostone Of-Field.

Action: Use the Report Definer to review thederived report fields of the report.

Report function selection error - %Source: Report Server

Explanation: An error was detected duringselection processing for a report or a reportfunction.

Action: See the appended message from theselection evaluator to determine the action totake.

Report functions cannot be referencedin TITLES report tablesSource: Report Definer

Explanation: Titles report tables cannot containreport functions.

Action: Remove the report function from theTitles report table.

TIBCO Object Service Broker Messages Without Identifiers

Page 364: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

350 |

Report Functions screen unavailable -no print field has been specifiedSource: Report Generator

Explanation: The Report Functions screen isirrelevant because you have not selected anyfields yet.

Action: No action required.

Report generation endedSource: Report Generator

Explanation: You ended the Report Generatorsession and returned to the Object Manageror workbench.

Action: No action required.

Report name not specifiedSource: Report Server

Explanation: A report name was not specifiedwhen $RPTOVERLAP was called.

Action: Use the Rule Editor to change the call to$RPTOVERLAP to include a report name asthe first argument.

Report on Load of Objects from File %Source: Unload/Load

Explanation: Heading for report issued byLOAD. The file which was the source isnamed.

Action: No action required.

Report permissions for object set willbe committed on SAVESource: Security

Explanation: You saved the report permissionsspecifications for an object set definition andyou are viewing the object set definitionscreen. If the object set definition screen issaved, the report permissions are committed;if not, changes to the report permissions areignored.

Action: No action required.

Report printedSource: Promotion

Explanation: The print process you started iscomplete.

Action: No action required.

Report table "%" deletedSource: Report Definer

Explanation: A DELETE operation for a reporttable has been performed.

Action: No action required.

Report table name "%" is not validSource: Report Definer

Explanation: Report table names can be amaximum of 16 characters and consist ofletters, digits, @, $, #, and underscores. Thename cannot begin with a digit or anunderscore.

Action: Correct the indicated report table name.

TIBCO Object Service Broker Messages Without Identifiers

Page 365: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 351

Report table name not specifiedSource: Report Server

Explanation: A report table name was notspecified when $RPTOVERLAP was called.

Action: Use the Rule Editor to change the call to$RPTOVERLAP to include a report tablename as the second argument.

Report tables/control breaks require avalid nameSource: Report Definer

Explanation: A report table or control break musthave a valid name before it can be painted.

Action: Assign the report table or control break avalid name before painting it.

Request "%" not allowed for table type"%"Source: TAM

Explanation: The requested table operationcannot be performed because of the tabletype. For example: PRM and IMP tablescannot be updated.

Action: Remove the table operation.

Request DENIED - cannot updatepermissions to META-DATA tablesSource: Security

Explanation: You requested to updatepermissions for a meta-table (e.g., FIELDS,TABLES, REPORTS, PARMS,SCREENTABLES); this is not allowed.

Action: If meta-table permission updates arerequired, contact TIBCO Support.

Request for attribute for screen field"%" failedSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The format stringcontains a request for the attributes for the i-th screen field of a screen table.

Action: Contact TIBCO Support.

REQUEST ISSUE INDICATED BUTNO CHANGES WERE REQUESTEDSource: S6BTLADM - SEGMENT/DASD

Explanation: You have requested the invocationof pending changes to the segment status ormode. However, there are no changespending.

Action: Reenter your desired changes and tryagain.

REQUEST ISSUED FORSource: S6BTLADM - DIAGNOSTIC DUMP

Explanation: The specified dump request hasbeen sent to the Data Object Broker.

Action: No action.

REQUEST LENGTH ROUNDED UPTO BE DIVISIBLE BY 16Source: S6BTLADM - MEMORY DISPLAY

Explanation: Notification that the system hasadjusted your requested length to bedivisible by 16.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 366: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

352 |

REQUEST POOL CONTROL BLOCKCOULD NOT BE RETRIEVEDSource: S6BTLADM - MEMORY DISPLAY

Explanation: When attempting to send therequest to the Data Object Broker to retrievethe pool management information for thepool you selected an error was detected.

Action: Review the joblog to determine if thereare other messages that may help identify thecause of the problem. Retry your request. Ifthe problem persists contact TIBCO Support.

Request to delete field % cancelledSource: Field Dictionary

Explanation: You rejected the request to deletethe specified field by pressing a key otherthan <PF22>.

Action: No action required.

Request to manage permissions to "%"CANCELLEDSource: Security

Explanation: You canceled from either theindividual object permissions list or from theObjectSet permissions list; changes areignored.

Action: No action is required.

Request to manage permissions to %CANCELLEDSource: Security

Explanation: You canceled a request from theobject permissions list.

Action: No action required.

REQUEST TO STARTCONNECTIONS TO group ISSUEDSource: S6BTLADM-Resource Management

Explanation: This acknowledgement messageindicates that the system has been requestedto initiate the generated connects as per yourrequest.

Action: No action required.

REQUESTED ACTION WILL NOT BEHONORED BECAUSE THERE AREPENDING UPDATESSource: S6BTLADM-Resource Management

Explanation: Schedule copy and associaterequests may not be issued while there arepending updates that have not been saved tothe repository.

Action: Either refresh the schedule recalling thecurrent schedule using the Schedule Indexselection or save the pending updates beforeproceeding with the copy or associaterequest.

REQUESTED BUFFER NUMBER ISTOO LARGESource: S6BTLADM - PAGE DISPLAY

Explanation: The buffer number requested islarger than the number of buffers allocated tothe resident page pool.

Action: Correct the buffer number and try again.

TIBCO Object Service Broker Messages Without Identifiers

Page 367: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 353

REQUESTED DATASET IS EITHERINVALID OR NOT AVAILABLESource: S6BTLADM - RPP DIRECTORY

Explanation: The input data set number is eitherinvalid or the data set is not available forprocessing.

Action: Correct your input and retry.

Requested DBID and FILE NO. do notexistSource: Adabas Extract

Explanation: The requested file does not exist inADABAS.

Action: Correct the DBID and FILENO values.

REQUESTED DETAIL ENTRY NOTFOUND, REENTER TYPE + GROUPOR GOTO GROUPLISTSource: S6BTLADM-Resource Management

Explanation: The Resource Detail entry for thespecified type and group could not belocated by the system; either reenter the typeand group or step through the Group ListScreen.

Action: Correct the request and retry.

Requested key was deleted from table"%"Source: TAM

Explanation: An INSERT, GET, or REPLACEoperation was requested for an occurrence.The occurrence has been deleted, but thedeletion has not yet been committed.

Action: Remove the INSERT, GET, or REPLACEoperation request.

REQUESTED MEMORY ADDRESS ISINVALIDSource: S6BTLADM - MEMORY DISPLAY

Explanation: The memory address you specifiedis not valid within the Data Object Brokeryou are currently processing under.

Action: Correct your address specification andretry the request.

REQUESTED PAGE NUMBER ISINVALIDSource: S6BTLADM - PAGE IMAGES

Explanation: The page number you requested fordisplay is invalid or could not be retrieved.

Action: Specify the page you desire again andresubmit your request.

REQUESTED SEGMENT IS EITHERINVALID OR NOT AVAILABLESource: S6BTLADM - RPP DIRECTORY

Explanation: The segment number specified isinvalid or currently offline. Only valid onlinesegments can be processed.

Action: Correct your input and retry.

REQUESTED SEGMENT IS NOT INLIST OF DEFINED SEGMENTSSource: S6BTLADM - SEGMENT/DASD

Explanation: The specified segment number isnot known to the Data Object Broker.

Action: Use cursor select processing from thesegment list to select a valid segmentnumber.

TIBCO Object Service Broker Messages Without Identifiers

Page 368: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

354 |

Required field "%" in source "%" butnot in subview "%"Source: TAM

Explanation: The subview occurrence that isbeing inserted or replaced does not contain afield that is required in the source tabledefinition.

Action: Include all fields required by the sourcetable in the definition of the subview table.

Required field is missingSource: Table Definer

Explanation: Enter a value for the required field.

Action: To continue, you need to specify a valuefor the highlighted field.

Required value for "%" in table "%" (orsecondary key value) is nullSource: TAM

Explanation: One of the following occurred:

• A primary or secondary key field with anull value has been specified.

• The field contains a null value butREQUIRED=YES is specified and nodefault value is present.

Action: For a primary or secondary key field,assign a non-null value. For a non-key field,provide a default value.

RESOURCE DETAIL ENTRY NOTDEFINED FOR THE OUTBOUNDPATH TO node-nameSource: S6BTLADM-Resource Management

Explanation: Via cursor position the named nodewas identified. You requested the display ofthe Resource Detail screen for that Node butit is not defined in the configuration.

Action: Select a different Node or add the desirednode selecting PF5 off the Resource Type Listscreen.

RESOURCE MANAGER INTERNALPROCESSING ERROR DETECTED,REASON CODE -Source: S6BTLADM-Resource Management

Explanation: When attempting to process arequest or obtain data from the Data ObjectBroker an error was detected. The processingthat detected the error is indicated by thereason code. The error code could be any ofthe following:

• 001 - The internal processing code wasoutside acceptable values.

• Reason codes 002 - 016 pertain to dataretrieval failures resulting fromcommunication problems or securityviolations in the Data Object Broker:

• 002 - Type list retrieval

• 003 - Group list retrieval

• 004 - Resource detail entry retrieval

• 005 - Resource detail update

• 006 - Start outbound peer connectionrequest

• 007 - Resource detail delete request

• 008 - Resource path list retrieval

• 009 - Stop server request

TIBCO Object Service Broker Messages Without Identifiers

Page 369: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 355

• 010 - Node name list retrieval

• 011 - Resource Histogram retrieval

• 012 - Schedule retrieval

• 013 - Request to associate a schedule toa resource

• 014 - Schedule update request

• 015 - Schedule list retrieval (list of allknown schedule names)

• 016 - User of a specified scheduleretrieval

Action: Review the joblog to determine if thereare additional messages which may helpidentify the cause of the problem. Try yourrequest again. If the problem persists contactTIBCO Support.

RESOURCE TYPE HAS NOT BEENSPECIFIED, PLEASE PRESS PF2 TODISPLAY TYPELISTSource: S6BTLADM-Resource Management

Explanation: The resource detail screen wasentered via PF5 off the type list, PF4 was thenpressed to display the list of groups withintype. At this point the system has never hada type identified and therefore cannot satisfythe request.

Action: press PF2 to display the type list and thenselect the desired type.

RESPONSE BUFFER NOTAVAILABLE FOR LOCK OWNERLISTSource: S6BTLADM - LOCK MANAGER

Explanation: When the Data Object Broker wasattempting to obtain a buffer in which tobuild the lock owner list for a given table, theacquisition failed.

Action: This should be a temporary problem,retry the request.

RESTART THE EXECUTIONENVIRONMENT AND REAPPLYSource: Promotion

Explanation: Some of the objects included in thechange request are bound on the targetsystem. These objects have to be unboundbefore the change can be applied. Thismessage is preceded by message 101.

Action: If you are in a multiple session system,restart the Execution Environment and applythe change again. If you are in a singlesession system, log off and log on to applythe change.

RESTORING RIGHTS ANDPERFORMING HOUSEKEEPINGSource: Promotion

Explanation: This message appears on the sourcesystem when you do a promotion and therights are reset.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 370: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

356 |

RESTORING VERSIONS OFOBJECTSSource: Promotion

Explanation: The Promotion utility is restoringprevious versions of objects as a result of aback out request.

Action: No action required.

Result of expression in condition is nota logical valueSource: Interpreter

Explanation: You have not followed therestrictions that apply to expressions in theconditions part of a rule.

Action: Verify that the expression yields a logicalvalue.

Result of ROUND is not between - 2 **31 and 2 ** 31 - 1 inclusiveSource: Builtin Routines

Explanation: The result of the ROUND tool doesnot fall within the valid range.

Action: No action required.

Result Set table name conflicts withexisting table name %Source: Table Definer

Explanation: You are defining a stored proceduretable definition that has one or more resultsets. The result set table name that will begenerated already exists.

Action: The first 14 characters of the table namemust be unique.

Return code "#" returned when loading ;Source: Builtin Routines

Explanation: Loading module M204DISP,M204ENCR or M204CMD failed.

Action: Review the procedure for creating thesemodules

Right edge of WindowSource: General

Explanation: You pressed <PF11> until youreached the right edge of the displayableinformation. No more information exists tothe right of the screen you are viewing.

Action: No action required.

Right edge of windowSource: Unload

Explanation: You have requested to page right;however, there is no more content to theright.

Action: No action required.

Rights already obtained for object "%"Source: Promotion

Explanation: Rights are already held for thisobject.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 371: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 357

Rights are not held for "%" of type "%"Source: Manage Promotion Rights

Explanation: You do not have the rights for thespecified object.

Action: Depending on the operation, you mayneed to obtain the rights if it is required.However, if the rights are not required, youmay take no actions on it.

Rights for "%" type "%" %Source: Manage Promotion Rights

Explanation: You are trying to do one of thefollowing operations on an object: OBTAINrights, RELEASE rights, and TRANSFERrights. The operation is successful.

Action: No action required.

Rights for % % and its children being %Source: Promotion

Explanation: Whileobtaining/releasing/transferring rights onan object which can have children, thisinformative message is shown in the audittrail.

Action: No action required.

Rights for % held by %Source: Promotion

Explanation: The promotion rights for thespecified object are held by the specified user.

Action: If you want to continue backing out achange, press <PF22>. If the object is not arule, rights for the object are reset and theobject is deleted. You will not be able torestore the object.

Rights for child objects of % % being %Source: Promotion

Explanation: Whileobtaining/releasing/transferring rights onan object which can have children, themessage is shown on the audit trail if anaction is being performed on child objects.

Action: No action required.

Rights for object "%" type "%" notobtained, object not existSource: Manage Promotion Rights

Explanation: You are trying to obtain the rightson an object but the object does not exist.

Action: No action required.

Rights for rule "%" cannot be obtainedin library "%"Source: Manage Promotion Rights

Explanation: You are trying to obtain the rightsfor a specified object; however, the operationfails. This is due to one of the following:

1. If the type of the object is a rule, the rulemay not exist in the library.

2. If the object type is a table, table may notexist.

Action: Check and see whether or not the objectyou specified really exists.

Rights for rule "%" cannot betransferred to library "%"Source: Manage Promotion Rights

Explanation: You are trying to transfer the rightsof one rule from one library to another butthe transfer fails. This failure is caused by oneof the following reasons:

TIBCO Object Service Broker Messages Without Identifiers

Page 372: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

358 |

• The destination library does not exist.

• The destination library does not containthe specified rule.

• You do not have the rights for the specifiedrule.

Action: Check whether you have the rights forthe specified rule, or whether the destinationlibrary exists and contains that rule.

Rights on % % in CR#% of loc % are notheld, cannot submitSource: Promotion

Explanation: You cannot submit the changebecause you do not have rights on the namedobject which is part of the specified change ofthe specified source node.

Action: Remove the specified change request orask the person/group who is holding rightson the named object to release or transfer therights to you.

Rollback request %Source: Promotion

Explanation: The request to roll back the changerequest is canceled, accepted, or acceptedand the description is saved.

Action: No action required.

Root is required for tree or crossreferenceSource: Print Rules

Explanation: You pressed <PF5> or <PF6> butdid not specify a root rule.

Action: Enter the name of a rule beside ROOTRULE:.

Routine "%" failedSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theInformation Log.

Action: Study the Object Service BrokerInformation Log.

Routine "%" not available in currentenvironmentSource: Builtin Routines

Explanation: A routine has been called in anenvironment (BATCH, CICS, IMS/DC andso on) where it is not available.

Action: Confirm that you are using the rightenvironment and/or routine.

Routine "%" returned an invalidexception code (#)Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 373: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 359

Routine "%" unsupported in 3270presentation environmentSource: Builtin Routines

Explanation: The specified routine needsservices from the operating system; theseservices are not currently available in a 3270environment.

Action: Reorganize your application so that itdoes not use operating system dependenttools.

Routine ";" cannot be object of ";"Source: POSIX ON support for EMS

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.

Row argument larger than maximumnumber of rowsSource: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Row argument less than 1Source: Builtin Routines

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Rule "%" copied as rule "%" to library"%"Source: Copy Rule or Copy Library

Explanation: The specified rule was successfullycopied.

Action: No action required.

Rule "%" has been overwrittenSource: Report Generator

Explanation: The indicated rule was overwrittenat your request.

Action: No action required.

Rule "%" has been saved for generatingreport "%"Source: Report Generator

Explanation: You requested that the indicatedrule be saved in the local library.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 374: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

360 |

Rule "%" is too large to saveSource: Rule Editor

Explanation: The rule named is too complex inits present form to save.

Action: Split the rule into two or more lesscomplex rules.

Rule "%" not foundSource: Print Rules

Explanation: You pressed <PF4>, but a rule onthe list was not found. The rules listed abovethe specified rule have been printed.

Action: Correct or remove the name of the rulethat could not be found. You can delete thenames above that rule to avoid printing themagain.

Rule "%" not foundSource: Debugger Utility

Explanation: Rule to be debugged must be in oneof the following rule libraries: SYSTEM,INSTALLATION, LOCAL.

Action: Verify the spelling of the rule name.

Rule "%" not foundSource: Session Manager

Explanation: The rule specified for executionfrom the workbench was not found.

Action: Check the spelling of the rule name andthe library in which it resides.

Rule "%" not overwrittenSource: Report Generator

Explanation: The indicated rule was notoverwritten because you did not confirmyour request to save the rule.

Action: No action required.

Rule "%" overwrites rule "%" in library"%"Source: Copy Rule or Copy Library

Explanation: The rule was copied successfully. Itresulted in overwriting a rule in thedestination library with the same name.

Action: No action required.

Rule "%" used as a function but doesnot return a valueSource: Interpreter

Explanation: You called a procedural rule as afunction.

Action: Correct the invocation or the definition ofthe rule.

Rule % %Source: Rule Editor

Explanation: Confirms that one of the followingactions was successful:

• RULE % DELETED

• RULE % SAVED

• RULE % PRINTED

• RULE % ...

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 375: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 361

Rule % does not exist in local library %Source: Promotion

Explanation: The specified rule cannot be foundin the specified local library. Consequently,the promotion has failed.

Action: Restore the specified rule into thespecified library and reapply the change.

Rule % has already been unloadedSource: Unload/Load

Explanation: You entered the rule name morethan once on the UNLOAD selection screen.A rule cannot be unloaded more than once.

Action: No action required.

Rule % is in use by user %Source: Rule Editor

Explanation: The rule is being edited by anotheruser.

Action: Repeat the operation when no other useris editing the rule.

Rule % is not a rule in library %Source: Unload/Load

Explanation: The requested rule cannot be foundin the specified library.

Action: Correct the name of the rule or the nameof the library.

Rule % not bound - insufficient securitySource: Promotion

Explanation: The promotion system attempts tobind all the rules being promoted, but thiswill fail unless the userid applying thepromotion has level-7 security.

Action: No action is required. At this point thepromotion has completed without bindingthe rules. If binding rules during promotionis desired, a level-7 user should administerthe promotions.

RULE % program output to dataset %Source: HLIPREPROCESSOR

Explanation: The program has been placed in theindicated data set.

Action: No action required.

Rule call for derived report field "%" ofreport table "%" failedSource: Report Server

Explanation: The source of the derived reportfield contains a rule function call that failedwhen the derivation was evaluated.

Action: Look at the error log to determine whythe rule failed.

Rule call stack error - traceback may bein errorSource: Interpreter

Explanation: TheObject Service Broker programthat produces the information Log cannotanalyze the error.

Action: Study the Object Service BrokerInformation Log.

TIBCO Object Service Broker Messages Without Identifiers

Page 376: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

362 |

Rule contains "%" statement(s)Source: Rule Editor

Explanation: % stands for one of the followingwarnings:

• NON-EXECUTABLE

• UNREACHABLE

A non-executable statement is missing asequence # on the action (when outside aFORALL or UNTIL loop). An unreachablestatement appears in the rule after aRETURN or SIGNAL statement in the sameexecution path.

Action: Check the rule to determine if statementsshould be added, deleted or moved.

Rule could not be executedSource: Batch Client

Explanation: Rule execution failed.

Action: See the log for more information.

Rule does not exist in Library %Source: Unload/Load

Explanation: The rule does not reside in thelibrary specified.

Action: Correct the rule or library name.

Rule has too many parameters forparameter values promptSource: Session Manager

Explanation: If the name of a rule to be executedis specified from the workbench withoutvalues for the required parameters beingspecified, a new screen is written to promptfor the parameter values. The number ofrequired parameter values must fit on onescreen without scrolling. For 3270 models 2,

3, 4, and 5, a maximum of 10, 14, 19, and 11parameter values can be specified. The ruleto be executed has more parameters than theallowed maximum.

Action: Do one of the following:

• Change the rule to have fewer parameters

• Specify all the parameter values from theworkbench

• Execute the workbench from a 3270terminal with a larger number of rows

• Write a "wrapper" rule with fewerparameters to call the desired target rule

Rule is in use by user %Source: Rule Editor

Explanation: The rule is being edited by anotheruser.

Action: Repeat the operation when no other useris editing the rule.

Rule list selectedSource: Print Rules

Explanation: You pressed <Enter> and the rulenames from the library chosen are displayedon the screen.

Action: No action required.

Rule may be missing "RETURN"statementsSource: Rule Editor

Explanation: The rule has conditions. One pathhas a RETURN statement, but at least oneother does not.

Action: Enter a RETURN statement or press<PF3> to confirm that you do not wantanother RETURN statement.

TIBCO Object Service Broker Messages Without Identifiers

Page 377: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 363

Rule name "%" exceeds maximumlength of % charsSource: Rule Editor

Explanation: The name of rule % has too manycharacters. The maximum number ofcharacters presently allowed is 16.

Action: Choose a shorter name for the rule.

Rule name and parameters could not beparsed properlySource: Batch Client

Explanation: There is a syntax error in the rulename or parameters.

Action: Check the command line.

Rule name not passed as command lineparameterSource: Batch Client

Explanation: The rule name has not beenspecified.

Action: Specify the rule name in the commandline.

Rule not executedSource: Session Manager

Explanation: When prompting for parametervalues for a rule, the user pressed <PF3> or<PF12> to terminate the prompt. Thespecified rule was therefore not executed.

Action: No action is necessary.

Rule submitted to queue "%"Source: Batch Submission Tool

Explanation: The batch request was submitted tothe indicated queue.

Action: No action required.

Rules to execute from a different library% are foundSource: Promotion

Explanation: You selected one or more rules toexecute from the named library, so youcannot select another rule to execute in thecurrent library.

Action: Do not select a rule to execute in thecurrent library.

RULESMGR ERROR - Initializationfailed with code %Source: Rules Manager

Explanation: The Rules Manager failed toinitialize correctly. The error code displayedindicates the type of failure.

Possible error codes are:

• 1 - Failed to allocate a Rules Manager workarea

• 2 - Failed to allocate a system library hashtable

• 3 - Failed to allocate an installation libraryhash table

• 4 - Failed to allocate a builtin library hashtable

• 5 - TAM rule read error encountered

• 6 - Insert of rule name to hash table failed

• 7 - TAM read error on rule index

• 8 - Rule already loaded

TIBCO Object Service Broker Messages Without Identifiers

Page 378: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

364 |

• 9 - Buffer error

Action: Contact TIBCO Support.

RULESMGR ERROR - RULES BUFFEROVERFLOWSource: Rules Manager

Explanation: The shared rules binding area is fulland no more rules can be bound.

Action: Increase the size of the rules binding areaand/or recycle the Execution Environment.

TIBCO Object Service Broker Messages Without Identifiers

Page 379: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 365

Messages beginning with: S

S6BTLADM INITIALIZATIONFAILED - INSUFFICIENT STORAGESource: S6BTLADM - COMMON MESSAGES

Explanation: When you started youradministration session there was not enoughstorage available to you to fulfill therequirements of the utility.

Action: Increase the region size of your TSOsession. It may be beneficial to invoke theadministrator from native TSO, (from theready prompt).

Same field number defaults for "%" and"%" of subview "%"Source: TAM

Explanation: Two subview fields specify thesame source field name.

Action: Change one of the source field names to adifferent source field in the subview tabledefinition.

Save batch queue failed: %Source: Batch Submission Tool

Explanation: An error was encountered duringthe saving of a queue definition.

Action: Contact TIBCO Support.

Save batch request failed: %Source: Batch Submission Tool

Explanation: An error was encountered when abatch request was saved.

Action: Contact TIBCO Support.

SAVE failed - too many report tablesspecified for reportSource: Report Definer

Explanation: The current definition of the reportcannot hold all the specified report tables.

Action: Remove the report tables from the reportdefinition until the save can be performed.

SAVE not permitted; use <PF12> tocancel and exitSource: Security

Explanation: You made a request to save whensaving is not allowed due to authorizationrestrictions.

Action: Use <PF12> to exit the screen.

TIBCO Object Service Broker Messages Without Identifiers

Page 380: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

366 |

Save request CANCELLEDSource: Object Set Definer

Explanation: Your request to save the object setwould have involved overwriting an existingobject set. You have decided that this is notwhat you desire and have thus canceled thesave.

Action: Change the name of the object set to thedesired name and perform the save again.

Save request CANCELLEDSource: Screen Definer

Explanation: Informational only. You havecanceled your request to overwrite a screentable definition.

Action: No action required.

SAVE request CANCELLEDSource: Security

Explanation: Your request to save has beencanceled.

Action: No action required.

Save stored procedure definition "%"firstSource: Table Definer

Explanation: Before defining result set tables youmust save the stored procedure definition.

Action: Save the table definition

SAVED changes to CORE informationSource: General Table Definer

Explanation: You have requested to save changesto core information about a MetaStor tableyou are defining using the generic TableDefiner.

Action: No action required.

SAVED changes to definition of DATtable "%"Source: CA Datacom Table Definer

Explanation: You requested to SAVE anychanges made to the definition of the DATtable. This confirms that the changes weresaved.

Action: No action required.

SAVED changes to definition of library"%"Source: Define Library

Explanation: You made changes to the librarydefinition and saved them.

Action: No action required.

SAVED changes to EXTENSIONinformationSource: General Table Definer

Explanation: You have requested to save theextension specification for the MetaStor tableyou are defining. If you save the tabledefinition, the extensions specification yousaved will be committed.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 381: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 367

SAVED definition of NEW library "%"Source: Define Library

Explanation: You saved the definition of anewly-created library.

Action: No action required.

SAVED instance selection for TABLE"%"Source: Unload

Explanation: You have specified which instancesfor a table should be selected for unloadingusing the INSTANCE SELECT function. Yourspecification was saved. If you press <PF3>from this screen, the instances selected forthe table will be unloaded.

Action: No action required.

Scanned % rules; press PF2 for moreinformationSource: CHANGERULE tool

Explanation: The scanning has completed afterexamining the stated number of rules.

Action: Press PF2 and examine the report.

SCHEDULE ASSOCIATIONATTEMPT FAILED, RESOURCE typegroup IS NOT DEFINEDSource: S6BTLADM-Resource Management

Explanation: You attempted to associate thedisplayed schedule to a Resource Detailentry that is not defined to the system.

Action: Correct the target fields and retry yourrequest.

SCHEDULE DELETE CANNOT BEPERFORMED BECAUSE THESCHEDULE IS IN USESource: S6BTLADM-Resource Management

Explanation: You requested to remove thedisplayed schedule from the system (PF11)but the schedule is currently in use by one ormore Resource Detail entries.

Action: From the Schedule Index display screen,position the cursor on the current scheduleand press PF9 to determine which ResourceDetail entries are currently using theschedule. Either associate those Detail entriesto other schedules or retain the schedule youattempted to delete.

Schedule of rule "%" failed - cannot finddefault model JCL for batch jobSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 382: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

368 |

Schedule of rule "%" failed - could notcreate process, error code %Source: Interpreter

Explanation: An attempt to spawn a processused to schedule a batch job failed. Likelycauses are that a system-imposed limit wasreached for the number of processes that maybe executed by a single user, or the system islow on virtual memory.

Action: Kill unnecessary processes that may berunning on the system. Increase physicalmemory and swap-file space.

Schedule of rule "%" failed - could notopen file, error code %Source: Interpreter

Explanation: An attempt to open a disk filefailed. Likely causes are exhaustion of filedescriptors or disk full conditions.

Action: Decrease the value specified for theMAXSESSION parameter. Increase theamount of free disk space available for thedirectory specified by the TEMPUNITparameter.

Schedule of rule "%" failed - could notopen stream, error code %Source: Interpreter

Explanation: An attempt to allocate a bufferedI/O stream failed. The most likely cause isthe exhaustion of buffered I/O streamresources.

Action: Decrease the value specified for theMAXSESSION parameter.

Schedule of rule "%" failed - insert in"%(%)" rejectedSource: Interpreter

Explanation: You have too many SCHEDULE TOstatements in a given transaction.

Action: Intersperse a few COMMIT statements,or distribute the SCHEDULE statementsamong several transactions.

Schedule of rule "%" failed - JCL cardoverflow- "%"Source: Interpreter

Explanation: Various limits apply to thearguments of a rule when you invoke it withthe SCHEDULE statement; one of theselimits was exceeded.

Action: Pass the argument values through atable.

Schedule of rule "%" failed - jobsubmission failed, exit code %Source: Interpreter

Explanation: The at(1) command used toschedule the batch job exited with a nonzeroexit code.

Action: See system documentation for the at(1)command.

Schedule of rule "%" failed - jobsubmission failed, signal %Source: Interpreter

Explanation: The at(1) command used toschedule the batch job terminatedabnormally as a result of the given signal.

Action: See system documentation for the at(1)command.

TIBCO Object Service Broker Messages Without Identifiers

Page 383: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 369

Schedule of rule "%" failed - ruleparameters too long for batch JCLSource: Interpreter

Explanation: Various limits apply to thearguments of a rule when you invoke it withthe SCHEDULE statement; one of theselimits was exceeded.

Action: Pass the argument values through atable.

Schedule of rule "%" failed - write tofile failedSource: Interpreter

Explanation: An attempt to write to a file on diskfailed. Likely causes are disk full conditions.

Action: Increase the amount of free disk spaceavailable for the directory specified by theTEMPUNIT parameter.

Schedule of rule ";" failed - cannotevaluate ";"Source: Interpreter

Explanation: You have used a SCHEDULEstatement referring to a@SCHEDULEMODEL containing a user-defined variable, typically a field of a table.Either the field value cannot be retrieved orthe value is too big.

Action: Verify the spelling of the field, tablenames. Verify the size of the returned value.

Schedule of rule ";" failed - Passworddecryption exit not installedSource: Interpreter

Explanation: The SCHEDULE_MODEL facilityencountered a substitution variable for apassword. The current password was in anencrypted format, and the site decryptionexit has not been installed.

Action: Check with your site administrator todetermine the cause and recommendedaction.

Schedule of rule ";" failed - Passworddecryption rejected by exitSource: Interpreter

Explanation: The SCHEDULE_MODEL facilityencountered a substitution variable for apassword. The current password was in anencrypted format, and the site decryptionexit rejected the decryption call.

Action: Check with your site administrator todetermine the cause and recommendedaction.

SCHEDULE schedule HAS BEENDELETED SUCCESSFULLYSource: S6BTLADM-Resource Management

Explanation: This message is to acknowledgethat the schedule you requested has beenremoved from the repository.

Action: No action.

TIBCO Object Service Broker Messages Without Identifiers

Page 384: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

370 |

SCHEDULE schedule IS CURRENTLYNOT ASSOCIATED WITH ANYRESOURCESSource: S6BTLADM-Resource Management

Explanation: When attempting to retrieve the listof resources which use the specified scheduleit was determined there were none.

Action: No action.

SCHEDULE schedule SUCCESSFULLYASSOCIATED WITH RESOURCE typegroupSource: S6BTLADM-Resource Management

Explanation: This message is to acknowledge thesuccessful completion of the requestedassociation of the specified schedule to thespecified Resource Detail entry.

Action: No action.

Schedule statement failed; dynamicallocation failed with RC=%ERRCODE=% INFOCODE=%Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. For an explanation of the codes, refer to theappropriate IBM manual for the SVC99error codes.

3. Contact your site's system programmer forassistance.

If additional assistance is required contactTIBCO Support with the log and adescription of the actions performed beforethe message was displayed.

SCHEDULE TO BE DELETED DOESNOT EXIST IN THE REPOSITORYSource: S6BTLADM-Resource Management

Explanation: In the Resource Manager Schedulescreen PF11 was pressed to delete a schedulewhich could not be located in the ResourceRepository.

Action: Check to ensure the schedule name wasnot change resulting in a new schedule.Select the schedule from the index list againand retry the delete.

SCHEDULE UPDATE WASREQUESTED BUT THERE ARE NOPENDING UPDATESSource: S6BTLADM-Resource Management

Explanation: Via PF10 your have requests thatpending updates be applied to the repositorybut the system cannot detect any pendingupdates.

Action: Key in the required changes and thenretry the update request.

Screen "%" cannot be referred to morethan onceSource: Security

Explanation: You referred to a particular screenmore than once while specifying screenpermissions for an Object set definition.

Action: Remove duplicate entries from the list byreplacing the screen name with blanks, nulls,or another screen name.

TIBCO Object Service Broker Messages Without Identifiers

Page 385: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 371

Screen "%" deletedSource: Screen Definer

Explanation: The screen indicated by themessage has been deleted.

Action: No action required.

SCREEN "%" DELETEDSource: Screen Definer

Explanation: You requested and confirmed arequest to delete a screen, either from theScreen Definer or from the Screen Object List.

Action: No action required.

Screen "%" does not existSource: Security

Explanation: You referred to a non-existentscreen.

Action: Remove the entry or correct it.

Screen "%" no longer existsSource: Promotions Bind Tools

Explanation: The specified screen waspreviously bound but no longer exists.

Action: No action required.

Screen "%" to be deleted does not existSource: Screen Definer

Explanation: The user tried to delete a screen thatdoes not exist.

Action: Delete only those screens that have beenassigned a definition.

Screen % does not contain screen table%Source: Menu Definer

Explanation: The screen table is not in the screen.

Action: Check the screen and screen table names.If necessary, modify the screen.

Screen % does not existSource: Menu Definer

Explanation: You have specified a screen thatdoes not exist.

Action: Correct the screen name, or if necessary,exit and define a screen.

Screen % has already been exportedSource: Unload/Load

Explanation: You entered a screen name morethan once in the entry screen. UNLOADcannot export a screen more than once.

Action: No action required.

Screen % is not an entry in SCREENSSource: Unload/Load

Explanation: The screen is not defined in thesystem.

Action: Ensure that the screen exists and unloadthe screen again.

Screen % printedSource: Print Rules

Explanation: A screen definition is printed.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 386: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

372 |

Screen definition changes cancelledSource: Screen Definer

Explanation: You have pressed <PF12> to cancelfrom the Screen Definer.

Action: No action required.

Screen definition printed for screen: %Source: General

Explanation: The definition of the specifiedscreen is sent to the printer.

Action: No action required.

Screen help changes cancelledSource: Screen Definer

Explanation: The changes that have been madeto the screen Help during this edit sessionhave been canceled.

Action: No action required.

Screen help UPDATEDSource: Screen Definer

Explanation: The Help for the screen has beenupdated.

Action: No action required.

Screen name not specifiedSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The format stringparameter contains a reference to the screenfield attributes of a screen table but a validscreen name was not passed to the function.

Action: Contact TIBCO Support.

Screen permissions for object set willbe committed on SAVESource: Security

Explanation: You saved screen permissions foran object set being defined. If the object setdefinition is saved, the screen permissionsare committed; if not, changes to the screenpermissions are ignored.

Action: No action required.

Screen table "%" of Screen "%" does notfit on physical screenSource: Screen Server

Explanation: The indicated screen table cannotbe shown on the physical display being used.

Action: Either change the screen definition sothat the indicated screen table can be shown,or run the application from a session using aterminal with a larger screen size.

Screen table % does not contain a fieldnamed "DATE"Source: Menu Definer

Explanation: The screen table must have a fieldwhere the session manager can insert thecurrent date.

Action: Add the required field to the screen table.

Screen table % does not contain a fieldnamed "USERID"Source: Menu Definer

Explanation: The screen table must have a fieldnamed USERID.

Action: Correct the screen table.

TIBCO Object Service Broker Messages Without Identifiers

Page 387: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 373

Screen table % does not contain a fieldnamed %Source: Menu Definer

Explanation: The screen table you specified doesnot contain the field you specified.

Action: Correct the screen table or field name.

Screen table % does not contain a fieldnamed TITLE or VALUESource: Menu Definer

Explanation: The scrollable table must providefields that are named TITLE and VALUE.

Action: Correct the screen table definition.

Screen table must be NEW; named(screen)table already existsSource: Menu Definer

Explanation: You are defining a New SessionMenu and referring to tables that alreadyexist as the head/body/history area screentables.

Action: Since a new menu is being defined, andsince the screen tables used for this menu areconsidered part of the menu (e.g., beingdeleted when the menu is deleted), thescreen tables must be unique to the menu.Choose new screen table names.

Screen tables "%" and "%" overlap inScreen "%"Source: Screen Server

Explanation: Screen tables may not overlap.

Action: Change the starting Row and/or Columnof one of the screen tables by using the ScreenTable Painter.

Screen update/display not allowedduring screen validationSource: Screen Server

Explanation: The validation rule is attempting tochange or display occurrences on the screenwhile it is in the process of validation.

Action: Remove the update or the displaystatements from the validation rule.

Screen validation interrupted forScreen "%"Source: Screen Server

Explanation: The Validation Exit key waspressed, bypassing the validation rules onthe screen.

Action: This situation can be caught with aVALIDATEFAIL, and dealt with by anexception handler.

Screen width has to be greater than 80columnsSource: Object Manager

Explanation: The Object Manager works only fora screen which is at least 80 columns wide.

Action: Check the width of the screen and adjustaccordingly.

Scripted strings too long to fit on pageand are truncatedSource: Character-based Text Editor

Explanation: The scripted strings do not fitwithin the given margins and are truncated.

Action: Do one of the following:

• Shorten the string.

• Adjust the margins.

TIBCO Object Service Broker Messages Without Identifiers

Page 388: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

374 |

SCROLL, EXIT or HELP functioncannot use REFRESH PF keySource: Screen Definer

Explanation: In the Screen Definer, you assigneda reserved PF key to one of the standardfunctions. For example, <PF24> is reservedfor REFRESH.

Action: Reassign the changeable standardfunction to use a PF key other than thereserved keys.

Scroll amount "%" is invalidSource: Rule Editor

Explanation: You have entered the invalid scrollamount indicated.

Action: Enter the scroll amount P, M, H, C or anumber.

Scroll amount "%" not valid forhorizontal scrollSource: General

Explanation: You entered an invalid scrollamount. Valid amounts for scrollinghorizontally are:

• P - One screen left or right

• M - To the left or right edge

• n - The specified number of columns left orright.

Action: Enter a valid scroll amount and press<PF10> or <PF11>.

Scroll field must be in Title of multi-occurrence screen tableSource: Screen Definer

Explanation: You have entered the name of afield to the SCROLL AMOUNT ENTRYprompt but the named field is not in the titlearea of your multi-occurrence screen table.

Action: Change the screen table definition tohave the SCROLL AMOUNT ENTRY field inthe Title area.

Scroll stopped at %Source: Rule Editor

Explanation: You have scrolled to the TOP, orBOTTOM, of the rule.

Action: No action required.

Scrollindicator field must haveTYPE=S, SYNTAX=CSource: Screen Definer

Explanation: A Field marked as a scrollindicatormust be of type=S and syntax=C.

Action: Either unmark the field or change its typeand syntax to correct values.

SEARCH must be one of S, I, LSource: Menu Definer

Explanation: The possible values for SEARCHare:

• S - System

• I - Installation and System

• L - Local, Installation, and System

• Y - Yes, search the local library

• N - No, do not search the local library.

Action: Choose one of the valid values.

TIBCO Object Service Broker Messages Without Identifiers

Page 389: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 375

Search results printedSource: Global Cross Ref. Search

Explanation: The list of objects found wasprinted by pressing <PF13>.

Action: No action required.

SEARCH TOKEN NOT SUPPLIEDSource: S6BTLADM - PAGE IMAGES

Explanation: You have requested a searchfunction but the search target has not beenidentified.

Action: Identify the search target and retry yourrequest.

SecAdmin "%" does not existSource: Security

Explanation: A Security Administratorrequested to view the profile of anotherSecAdmin which does not exist.

Action: You can use the OPTIONS function onthe main menu to determine which SecurityAdministrators exist, and then select fromthis list.

Secondary index built on field %Source: Table Editor

Explanation: Your request to build a secondaryindex on the specified field was successful.

Action: No action required.

Secondary index deleted on field %Source: Table Editor

Explanation: Your request to delete thesecondary index on the indicated field wassuccessful.

Action: No action required.

Secondary index fields cannot beselectedSource: Table Definer

Explanation: You cannot select any IMSsecondary index fields.

Action: No action required.

Security Audit Logging for EE % anduser % is %Source: Audit Log Message

Explanation: The value of the Logging ControlParameter for the indicated user on theindicated Execution Environment has beenlogged.

Action: No action required.

Security Failure:%Source: Copy Definition

Explanation: You do not have security access onthis table.

Action: If access is required, have your SecurityAdministrator modify the access.

TIBCO Object Service Broker Messages Without Identifiers

Page 390: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

376 |

Security failure: Denied VIEW_DEFNaccess to % "%"Source: Copy Definition

Explanation: You have requested (directly orindirectly through children) to copy thedefinition of an object for which you lackVIEW_DEFN security permission.

Action: You may not request to copy this objectuntil you have obtained VIEW_DEFNsecurity permission. This can be obtainedfrom any user who has CONTROLpermission to the object.

Security failure: Denied VIEW_DEFNaccess to % "%"Source: Copy Defn/Data

Explanation: You have specified an object tocopy for which you are denied VIEW_DEFNsecurity permission.

Action: Remove the reference and continue. Youmust obtain the required permission prior tomanipulating the object in any way.

Security Failure : %Source: Delete Definition

Explanation: You are trying to delete an object.However, you do not have the authority toaccess to the object or the objects defined bythat specified object.

Action: Search for the owners of those objectswhich you do not have the accesspermission. Ask them to give you accesspermissions on those objects and retry theoperation again.

Security File Definition ERRORSource: Security

Explanation: The logon was prevented by aSecurity File Definition error.

Action: Contact either the System Administratoror Security Administrator.

Security Group "%" DELETEDSource: Security

Explanation: You confirmed a deletion requestfor a security Group definition. This causesthe group definition to be deleted, andremoves all the references to the group fromthe security system.

Action: No action required.

Security violation: %Source: Print Rules

Explanation: The indicated security violation hashalted your print request. You cannot print atable without access to it.

Action: Contact your Security Administrator ifyou need access to the table.

Security violation : %Source: Table Definer

Explanation: Access to the indicated table isdenied for security reasons.

Action: Contact your Security Administrator ifyou need access to the indicated table.

TIBCO Object Service Broker Messages Without Identifiers

Page 391: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 377

Securityfail: % - contact securityadministratorSource: Report Generator

Explanation: Access to a table was denied forsecurity reasons.

Action: Contact your Security Administrator.

Securityfail: %Source: Batch Control Card

Explanation: You encountered a security failurebecause you are not authorized to access theobject specified in the message.

Action: Contact your Security Administrator ifyou need to access the object.

Securityfail: %Source: Character-based Text Editor

Explanation: Your action cannot be completedbecause of security problems. The messageexplains why.

Action: Contact your Security Administrator.

Securityfail: %Source: Host Language Interface

Explanation: While processing, a security failureoccurred on the specified table.

Action: See your Security Administrator with thetable name.

Securityfail: %Source: Tool for CA IDMS Data

Explanation: Your operation failed due tosecurity problems. The message gives anexplanation for the security failure.

Action: Contact your Security Administrator.

Securityfail:Source: Keyword Manager

Explanation: You tried to save your editingchanges to keywords for an object but you donot have permission to update the object.

Action: Press the Skip PF key to bypass thisobject and continue with the next object orpress the Stop PF key which takes you out ofediting mode.

SECURITYFAIL - %Source: Object Set Definer

Explanation: Security clearance has not beenpassed for access to the indicated object.

Action: Consult your Security Administrator.

SECURITYFAIL - %Source: Report Definer

Explanation: Security clearance has not beenpassed for access to the requested report.

Action: See your Security Administrator.

SECURITYFAIL - %Source: Screen Definer

Explanation: Due to lack of security access on thescreen table(s), all checks cannot beperformed.

Action: You do not have proper security for thescreen table(s). Obtain security access beforegoing back to the Screen Definer.

TIBCO Object Service Broker Messages Without Identifiers

Page 392: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

378 |

SECURITYFAIL - %Source: Screen Definer

Explanation: Security clearance has not beenpassed as indicated by the message.

Action: See your Security Administrator.

SECURITYFAIL - %Source: Security

Explanation: Security clearance has not beenpassed as indicated by the message.

Action: Contact your Security Administrator.

SECURITYFAIL on REFD DATAsource table "%"Source: Unload

Explanation: There is a problem with security fordata referenced by an object you requested tounload.

Action: Report this problem to your SystemAdministrator as there should not be aproblem in the object type definitions forunloadable objects.

SECURITYFAIL on REFD DEFN sourcetable "%"Source: Unload

Explanation: There is a security problem withobject type definition data for an object yourequested to unload.

Action: Report this to your SystemAdministrator. This should not arise fordefinition tables which reference definitionsincluded in an object type.

SEGMENT/DATASET RESIDENTPAGE POOL RETRIEVAL ERRORSource: S6BTLADM - RPP DIRECTORY

Explanation: When attempting to send therequest, the segment, and data setinformation you requested, an error wasdetected.

Action: Review the job log to determine ifadditional messages were produced whichmay help identify the problem. Retry yourrequest. If the problem persists contactTIBCO Support.

Segment % is unavailable for % table %Source: Table Editor

Explanation: Request failed due to the datasegment being offline or the indicatedsegment# not defined to Object ServiceBroker.

Action: Specify an active segment for the request.The shareable tool HURON_STATS can beused to list segment statistics. Also, check theuser profile to ensure that the segment# iscorrect.

SEGMENT CHANGE REQUESTSCHEDULEDSource: S6BTLADM - SEGMENT/DASD

Explanation: You have requested and confirmchanges to the current processing of thesegment. This message provides anacknowledgement that the request has beenissued to the Data Object Broker.

Action: No action required. Monitor the segmentscreen to determine when the requestprocessing has completed.

TIBCO Object Service Broker Messages Without Identifiers

Page 393: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 379

SEGMENT NUMBER SPECIFIED ONMENU WAS NOT NUMERIC,IGNOREDSource: S6BTLADM - SEGMENT/DASD

Explanation: You attempted to specify a segmentnumber when invoking the function from themenu. The segment number you specifiedfailed a validation edit.

Action: Use cursor select processing to processyour desired segment.

SEGMENT STATISTICS COULD NOTBE RETRIEVEDSource: S6BTLADM - SEGMENT/DASD

Explanation: An error was detected whenattempting to retrieve information about thesegments currently defined to the DataObject Broker.

Action: Review the joblog to determine if thereare additional messages which may helpidentify the cause of the problem. Retry yourrequest. If the problem persists, contactTIBCO Support.

Select a report function (such asTOTAL), or enter RULE/FIELDSource: Report Definer

Explanation: Either a report function, rule name,or field name must be entered as thedefinition for a derived field.

Action: Enter report function parameters or arule name, field name, or expression toderive a value for this field. Consult theproduct documentation for furtherinformation.

Select a rule to editSource: Global Cross Ref. Search

Explanation: The cursor is not placed against oneof the rules in the list.

Action: Place the cursor against the rule you wishto edit.

Select a SET that requires EXPLICITCONNECT upon insertSource: Table Definer

Explanation: Only pertains to a record thatrequires additional set connections. Ifadditional set connections for a record that isbeing inserted into IDMS are required, selectthose sets to participate in the access path.

Action: Select a SET connection.

Select all fields for COPY/APPEND andpress <PF3>Source: Report Definer

Explanation: A COPY or APPEND command hasbeen requested with only the table namesupplied. A prompt has displayed allexisting fields of the specified table.

Action: Select all fields to be copied by typingany non blank character or sequentialnumbers. Press <PF3> to execute the COPYor APPEND.

SELECT error: "%" is not a parm or fieldin source tableSource: Table Definer

Explanation: The indicated identifier does notexist in the source table.

Action: Look at the definition of the source tableto find the name of the parameter or field.

TIBCO Object Service Broker Messages Without Identifiers

Page 394: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

380 |

SELECT error: "%" is not a source fieldor a defined parameterSource: Table Definer

Explanation: The indicated identifier, found inthe selection criteria, is neither a field of thesource table nor a newly defined parameter.

Action: Do one of the following:

• Change the identifier to a source fieldname

• Define the identifier as a new parameter inthe parameter section

• Remove the expression that contains theidentifier.

SELECT error: source parm "%" can bedefined only onceSource: Table Definer

Explanation: You specified the indicated sourceparameter more than once in the selectioncriteria.

Action: Remove any additional references to theindicated source parameter.

SELECT error: source parm "%" mustuse equals (=) operatorSource: Table Definer

Explanation: The indicated parameter specifiedin the selection criteria must be set to a non-null value.

Action: Make the indicated parameter equal to anon-null value.

Select field & put cursor onPrint/Sort/Break/Across sectionSource: Report Generator

Explanation: This instruction appears when youenter the Field screen.

Action: Select a field by typing an alphanumericcharacter (0-9, A-Z) beside it and placing thecursor where you want to insert the field.Press <Enter> to be prompted for the fieldsfrom the next source data table.Alternatively, you can directly type the fieldnames into the desired section.

Select fields from a single file onlySource: Table Definer

Explanation: You can select fields from only onefile for each Model 204 table.

Action: Limit your selections to one file only.Define another 204 table if you need fieldsfrom another file.

Select from list or press <Enter> for nextselectionSource: Report Generator

Explanation: You can specify how to relate thesource data tables you have chosen for yourreport by selecting from the prompt area, orby entering their relationships directly to theinput area.

Action: Specify the relationships between sourcedata tables by selecting from the lists ofparameters and fields, or by entering aparameter or field name in the input area.

If the current pair of tables in the promptarea is not the desired one, move the cursorto the input area to indicate the desired tableor pair of tables and press <Enter>, orsimply move the cursor to the prompt area

TIBCO Object Service Broker Messages Without Identifiers

Page 395: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 381

and keep pressing <Enter> until the desiredpair is displayed.

Select from lists or enter selection stringdirectlySource: Report Generator

Explanation: This instruction appears when youenter the Selection screen.

Action: If you want to specify selection criteria,select items from the prompt area or enter theselection string directly in the input area.Press <Enter> to be prompted for the fields ofthe next source data table.

Select function & field then put cursoron appropriate sectionSource: Report Generator

Explanation: This instruction appears when youenter the Function screen.

Action: Select a function-field pair by typing thesame alphanumeric character (0-9, A-Z)beside a function name and a field name, andplace the cursor where you want to insert thefunction-field pair. You can select more thanone pair at the same time, as long as you usethe same alphanumeric character for the pair.

SELECT function found % instance(s)to match criteriaSource: Unload

Explanation: You requested to have instancesselected in this screen according to thecriteria for parameter name and valuespecified at the top of the screen. Noinstances matched the specification.

Action: No action required.

Select object type(s) to manage rightsSource: Promotion

Explanation: You have pressed <Enter> withoutselecting the type of object for which youwish to manage/admin rights.

Action: Type S against object type and press<Enter>.

Select object type(s) to promoteSource: Promotion

Explanation: You have pressed <Enter> withoutselecting the type of object you want toprepare this change request for.

Action: Type S against the object type and press<Enter>.

SELECT on IGNORE row of table "%"of VSAM % "%" is not allowedSource: TAM

Explanation: Selection is not allowed on a table ifyou specified an IGNORE value in the tabledefinition. The variables, from left to right,are as follows:

1. The name of the table

2. Either "file" or "DDNAME"

3. The name of the file or the DDNAME

Action: Either remove the IGNORE value fromthe table definition for this table, or do notrequest a selection operation.

Select only 1 segmentSource: Table Definer

Explanation: You entered an S next to more thanone segment.

Action: Remove the extraneous selections.

TIBCO Object Service Broker Messages Without Identifiers

Page 396: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

382 |

Select only one DB2 Creator/TableSource: Table Definer

Explanation: You typed an S next to more thanone DB2 table.

Action: Remove the extra selections.

Select only ONE item from each listSource: Report Generator

Explanation: You typed a character next to morethan one item in a list.

Action: Remove the extra selections.

Select only ONE M204 file/groupSource: Table Definer

Explanation: You can select only one file orgroup for each Model 204 table.

Action: Reduce the selection to one only.

Select only ONE report function OR aRule/Field referenceSource: Report Definer

Explanation: You selected more than one reportfunction, or you selected both a reportfunction and a rule/field reference in thedefinition of a derived field.

Action: Enter one report function or a rule/fieldreference.

Select only ONE value for "%" of table"%"Source: Report Generator

Explanation: The Generator allows only onevalue be specified for each parameter of asource data table.

Action: Remove any extra parameter valueselections.

Select or enter a function and print fieldfor SUMMARY PRINTSource: Report Generator

Explanation: You did not specify any functionsfor print fields in the Summary Print section.There must be at least one function-field pairin the Summary Print section for a summaryreport.

Action: Select or enter a function-field pair forSummary Print, or press the FIELD functionkey and turn the summary flag off.

Select or enter a Print field which is nota Sort/Across fieldSource: Report Generator

Explanation: Since it is a summary report, youhave to select or enter a PRINT field that isnot a SORT BY or ACROSS BY field so thatyou can apply a function to it on the Functionscreen.

Action: Select or enter a PRINT field that is not aSORT BY or ACROSS BY field.

TIBCO Object Service Broker Messages Without Identifiers

Page 397: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 383

Select or enter a Print fieldSource: Report Generator

Explanation: You tried to go to the next screenwithout selecting a field to print in the report.

Action: Specify at least one field to be printed inthe report.

Select or enter a Sort field forsummary/across reportSource: Report Generator

Explanation: You turned the SUMMARY flag on.Now you must specify a SORT BY fieldbecause a SORT BY field is also used as aSUMMARY BY field.

Action: Specify at least one SORT BY field or turnthe SUMMARY flag off.

Select parameter value from list or entervalue(s) directlySource: Report Generator

Explanation: You can select or enter parametervalues for the indicated parameter if it is notto be related to another table. However, if thefirst table is parameterized, then you mustassign values to each of its parameter.

Action: If necessary, select a parameter valuefrom the prompt by entering an S next to thevalue that you want, or type the parametervalue directly in the PARM VALUE field.

If you must select values for more than oneparameter, and the parameter valuesdisplayed are not for the parameter that youwant to see, then move the cursor to theinput area to indicate the desired parameterand press <Enter>, or simply move thecursor to the prompt area and keep pressing<Enter> until the desired one is displayed.

Select parameter values using "S"Source: Unload/Load

Explanation: You used an invalid line commandto select parameters.

Action: Use an S to select parameter values.

Select Print/Control Field screen beforethis actionSource: Report Generator

Explanation: Before selecting the break functionsor executing the report, you must select atleast some report print fields from thePrint/Control Fields screen.

Action: Type S in the Print/Control Fields field toaccess the screen.

Select table from list or enter tablename directlySource: Report Generator

Explanation: You must specify at least one tablethat will be the source of data for your report.

Action: Select source data tables from the promptarea or enter the table names in the inputarea.

Select the actionSource: Report Generator

Explanation: After you have selected adestination for a report, you must select theexecution action to have the report executedand saved to the MetaStor.

Action: Type Y in the SAVE REPORT AND SENDTO DEST field.

TIBCO Object Service Broker Messages Without Identifiers

Page 398: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

384 |

Select the destination mediumSource: Report Generator

Explanation: To execute and save a report, youmust specify where you want it to be sent toby selecting a destination medium.

Action: Select one of the media by typing Y in thefield.

Select the field for sixbuild by typing a'Y' in front of itSource: Batch Control Card

Explanation: You can choose fields for secondaryindex build by typing Y in the SECONDARYcolumn beside the field name.

Action: Select fields for secondary index build byfollowing the instruction.

Select the INDEX, SET or AREA youwant to navigateSource: Table Definer

Explanation: For FORALL requests, select theINDEX, SET, or AREA that are to benavigated.

Action: Specify either an AREA sweep or INDEXsweep on FORALL requests. If more thanone secondary index exists select the onewhich you wish the CA-IDMS Gateway tonavigate.

Selected CA-Datacom fields inserted orreplacedSource: CA Datacom Table Definer

Explanation: You were in the FIELDS contextand you selected some CA-Datacom fields toinclude in the Object Service Broker DATtable definition. The fields you selected wereinserted into the list, or have replaced entriesthat referred to the same CA-Datacom fieldname.

Action: No action is required.

Selected change request does notinclude other change requestsSource: Promotion

Explanation: The X line command applies onlyto consolidated change requests.Consolidated change requests are those thatcontain other change requests. TheCONSOLIDATED field indicates whetherthe change request is consolidated or not.

Action: Use this line command only ifCONSOLIDATED = Y.

Selected data for table % does not existSource: Promotion

Explanation: The selected table or table instanceis empty.

Action: No action required.

Selected field "%" is not in thedefinition of table "%"Source: TAM

Explanation: The field used in the selectionstring is not defined in the table specified.

Action: Do one of the following:

TIBCO Object Service Broker Messages Without Identifiers

Page 399: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 385

• Remove the selection clause that containsthe undefined field.

• Include the undefined field in the tabledefinition.

Selected import table does not exist.Source: Batch Control Card

Explanation: You specified a non-existent importtable.

Action: Create the table or specify a different one.

Selected object "%" no longer existsSource: Object Manager

Explanation: The object command fails becausethe selected object no longer exists. Theobject may have been deleted by anotheruser.

Action: No action required.

Selected object cannot be expandedSource: Promotion

Explanation: The X line command can be used tomanage rights on objects that are containedin the object being expanded. Objects that donot contain other objects cannot beexpanded. Only screens, reports, object setsand tables can be expanded.

Action: Use this line command on a screen,report, object set or table.

SELECTION change; check allREPORT FUNCTIONSSource: Report Definer

Explanation: You requested a change to thereport selection.

Action: Check all defined report functions todetermine if the modified report selectionshould be placed inside the WHERE clausefor the report function.

Selection Code must match one fromInput File and be uniqueSource: Batch Control Card

Explanation: You either assigned a selection codethat is undefined in the input file, or youhave assigned the same selection code tomore than one output field of your table.

Action: Ensure that the selection code is definedin the input file and is assigned to only oneoutput field of the table.

Selection criteria is too long to fit inreport definitionSource: Report Generator

Explanation: Any selection criteria and controlfields specified are required for a reportfunction to produce a derived field. One orboth of the following has occurred:

• You specified a selection criteria that is toolong.

• You specified too many control fields onthe Field screen.

Action: Do one or both of the following:

• Shorten the criteria by removingunnecessary blanks or parentheses, or byreplacing "AND" and "OR" with "&" and"|" respectively.

TIBCO Object Service Broker Messages Without Identifiers

Page 400: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

386 |

• Press the FIELD function key to displaythe Field screen, and reduce the number ofSORT BY or ACROSS BY fields if theSUMMARY flag is on, or reduce thenumber of BREAK BY fields if theSUMMARY flag is off.

Selection date must be specifiedSource: Offline Utilities

Explanation: Parameter -d'YYMMDD,HHMMSS' must be specified toselect up to which point in time pages are tobe restored from backup.

Action: Retry specifying the date and time asindicated above.

Selection evaluation error on table "%"Source: TAM

Explanation: A selection could not be appliedagainst an occurrence. The message log willcontain a more detailed error message.

Action: Review the message log.

Selection for table "%" can have onlyone of >, <, >=, <=Source: Batch Control Card

Explanation: The selection for a table can onlyhave only one of the following:

• Greater than (>)

• Less than (<)

• Greater than or equal to (>=)

• Less than or equal to (<=).

For example, given a table T withparameters P1 and P2 and the followingselection criteria:

1. P1 > aaa & P2 > xxx

2. P1 < bbb & P2 < yyy

3. P1 > ccc & P2 > zzz

Selection (1) and (2) cannot be both specifiedfor table T since only either > or < is allowed,but not both.

Selection (1) and (3) cannot be both specifiedfor table T since the selection criteria canhave only one >.

Action: Follow the rules allowed for selectionand modify the selection string accordingly.

Selection for table "%" too large toprocessSource: TAM

Explanation: The internal representation of aselection exceeded 254 bytes.

Action: Reduce the length of the selection.

SELECTION ITEM NOT SUPPLIED,PLEASE RETRYSource: S6BTLADM - PROFILES DISPLAY

Explanation: You must specify an item numberto display the profile.

Action: Key the desired item number in the inputfield and retry your request.

Selection must be 'S', 'D' or 'X'Source: Adabas Extract

Explanation: You have entered an invalidselection.

Action: Enter one of S, D, or X.

TIBCO Object Service Broker Messages Without Identifiers

Page 401: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 387

Selection not allowed for non-parameterized tableSource: Batch Control Card

Explanation: You specified a selection string for anon-parameterized table, but you can onlyuse the selection string to specify parametervalues (i.e., select table instances).

Action: Delete the selection string for the non-parameterized table.

Selection not allowed on derived field"%.%"Source: TAM

Explanation: Selection on a derived field is notsupported.

Action: Using the traceback log, determine therule containing the invalid selection andremove the reference to the derived field.

SELECTION OF SEGMENT VIACURSOR POSITION FAILEDSource: S6BTLADM - SEGMENT/DASD

Explanation: When attempting to process aspecific segment, the cursor positioninganalyzer failed to identify a valid segment.

Action: Reposition the cursor using the tab keysand try your request again.

Selection string: %Source: Batch Control Card

Explanation: An explanation of why thespecified selection string is syntacticallyincorrect is provided.

Action: Correct the syntax error in the selectionstring. Press <PF1> for Help if you want toknow the correct syntax.

Selection string cannot exceed % linesSource: Report Generator

Explanation: The selection criteria cannot exceedthe indicated number of lines.

Action: You can reduce the length of the selectionstring by removing unnecessary blanks orparentheses, or by replacing "AND" and"OR" with "&" and "|" respectively.

Selection string for report field "%" ofreport table "%" is too bigSource: Report Server

Explanation: The selection string for a reportfunction had too many terms.

Action: Simplify the selection criteria for thereport function.

Selection string for report field "%" ofreport table "%" is too complex to build(stack overflow)Source: Report Server

Explanation: Brackets for a report functionselection string are nested too deeply.

Action: Review the selection string to reduce thedepth of the brackets.

Selection string for report table "%" istoo bigSource: Report Server

Explanation: The selection string for a report hadtoo many terms.

Action: Simplify the selection criteria for thebody report table.

TIBCO Object Service Broker Messages Without Identifiers

Page 402: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

388 |

Selection string for report table "%" istoo complex to build - stack overflowSource: Report Server

Explanation: Brackets for the body report tableselection string are nested too deeply.

Action: Review the selection string to reduce thedepth of the brackets.

Selection string for TAM call too longSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Selection string is too large to processSource: Table Editor

Explanation: Selection string you have suppliedfor tool PROCESS_TABLE is too large toprocess.

Action: Reduce the size of the selection string.

Selection string specified for access ontable "%" is too longSource: Builtin Routines

Explanation: The selection conditions in the tableaccess statement are too complicated.

Action: Simplify the conditions.

Selection string too long for report body"%"Source: Report Server

Explanation: A selection string for the bodyreport table exceeds the maximum size.

Action: Reduce the complexity of the selectionstring by removing or joining terms.

Separator lines cannot be editedSource: Rule Editor

Explanation: You tried to edit one of the lineswhich separate the rule quadrants.

Action: Move the cursor to an editable line.

Sequence number "%" is not on the firstline of the statementSource: Rule Editor

Explanation: A sequence number was placed ona line other than the first line in a multilinestatement.

Action: Do one of the following:

• Remove the sequence number if the firstline already has a sequence number.

• Move the sequence number to the first lineif the first line does not already have asequence number.

Sequence number "%" is within aFORALL or UNTIL loopSource: Rule Editor

Explanation: A sequence number was includedin a loop structure.

Action: Remove the sequence number.

TIBCO Object Service Broker Messages Without Identifiers

Page 403: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 389

Server ID "%" is invalidSource: Table Definer

Explanation: The indicated serverid isundefined.

Action: Contact your Database Administrator forvalid serverids.

Server parameter % must be definedwith USAGE "%"Source: Table Definer

Explanation: Invalid gateway parameter valuesare entered for field USAGE.

Action: Specific correct value for USAGE asindicated in the message.

Server parameter not defined for tabletype "%"Source: Table Definer

Explanation: There is no gateway parameterdefined for the specified table type.

Action: Invoke option "Define serverparameters" in tool GENDT to definegateway parameter for the new table type.

Serverid "%" is not definedSource: Table Definer

Explanation: The specified Serverid has not beendefined.

Action: Define Serverid.

Serverid is longer than maximumallowed (8 characters)Source: Table Definer

Explanation: Length of serverid is longer thanallowed.

Action: Specify serverid with length less than orequal to 8.

Servers could not be deactivatedSource: Batch Client

Explanation: Log, transaction or sessiondeactivation failed.

Action: See the log for more information.

SESSEXRN - executor environment callstack overflowSource: Session Manager

Explanation: Internal error.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Session end abend code out of rangeSource: Builtin Routines

Explanation: Call to $SETSESSIONEND isattempting to set an invalid session endabend code. The user abend codes must begreater than zero but less than 4000.

Action: Change the call to $SETSESSIONEND topass a valid user abend code.

TIBCO Object Service Broker Messages Without Identifiers

Page 404: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

390 |

Session end return code out of rangeSource: Builtin Routines

Explanation: Call to $SETSESSIONEND isattempting to set an invalid session endreturn code. The user return code must begreater than or equal to zero but less than4000.

Action: Change the call to $SETSESSIONEND topass a valid user return code value.

Session menu "%" does not existSource: Security

Explanation: You referred to a non-existentsession menu in the user profile beingupdated.

Action: Use STANDARD until you find the nameof a valid session menu.

Set and index files incompatible...checktheir contentsSource: Tool for CA IDMS Data

Explanation: The data contained in the set andindex import files is not from the samesubschema.

Action:

1. Check the contents of the set and indexfiles that you were going to load.

2. Use the LOAD AN IDMS SUBSCHEMAmanager utility again to change the filesthat you import.

Set and record filesincompatible...check their contentsSource: Tool for CA IDMS Data

Explanation: The data contained in the set andrecord import files is not from the samesubschema.

Action:

1. Check the contents of the set and recordfiles that you were going to load.

2. Use the "Load an IDMS Subschema"manager utility again to change the filesthat you import.

Set permission of % % by % deniedSource: Audit Log Message

Explanation: CONTROL access to this object bythe specified user was denied.

Action: The user can ask someone who hasCONTROL access to the object to provideCONTROL access.

Set permission of LIBRARY % by % togrant % access to %Source: Audit Log Message

Explanation: The indicated discretionary accesspermissions to the given library weregranted to the indicated user/group.

Action: No action required.

Set permission of LIBRARY % by % toremove % access from %Source: Audit Log Message

Explanation: Discretionary access permissions tothe specified library were removed from theindicated user/group.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 405: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 391

Set permission of REPORT % by % togrant % access to %Source: Audit Log Message

Explanation: The indicated discretionary accesspermissions to the given report were grantedto the indicated user/group.

Action: No action required.

Set permission of REPORT % by % toremove % access from %Source: Audit Log Message

Explanation: Discretionary access permissions tothe specified report were removed from theindicated user/group.

Action: No action required.

Set permission of SCREEN % by % togrant % access to %Source: Audit Log Message

Explanation: The indicated discretionary accesspermissions to the given screen were grantedto the indicated user/group.

Action: No action required.

Set permission of SCREEN % by % toremove % access from %Source: Audit Log Message

Explanation: Discretionary access permissions tothe specified screen were removed from theindicated user/group.

Action: No action required.

Set permission of TABLE % by % togrant access % to %Source: Audit Log Message

Explanation: The indicated discretionary accesspermissions to the given table were grantedto the indicated user/group.

Action: No action required.

Set permission of TABLE % by % toremove access % from %Source: Audit Log Message

Explanation: Discretionary access permissions tothe specified table were removed from theindicated user/group.

Action: No action required.

Set security of LIBRARY % by % todelete recordSource: Audit Log Message

Explanation: A library entry was deleted fromthe security table (@LIB_SECURITY) byexecuting rules.

Action: Contact the Security Administrator.

Set security of LIBRARY % by % toinsert recordSource: Audit Log Message

Explanation: A library entry was inserted intothe security table (@LIB_SECURITY) byexecuting rules.

Action: Contact the Security Administrator.

TIBCO Object Service Broker Messages Without Identifiers

Page 406: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

392 |

Set security of LIBRARY % by % toupdate recordSource: Audit Log Message

Explanation: The security information (e.g.classification) of the specified library waschanged by the indicated user.

Action: No action required.

Set security of REPORT % by % todelete recordSource: Audit Log Message

Explanation: A report entry was deleted from thesecurity table (@RPT_SECURITY) byexecuting rules.

Action: Contact the Security Administrator.

Set security of REPORT % by % toinsert recordSource: Audit Log Message

Explanation: A report entry was inserted into thesecurity table (@RPT_SECURITY) byexecuting rules.

Action: Contact the Security Administrator.

Set security of REPORT % by % toupdate recordSource: Audit Log Message

Explanation: The security information (e.g.classification) of the specified report waschanged by the indicated user.

Action: No action required.

Set security of SCREEN % by % todelete recordSource: Audit Log Message

Explanation: A screen entry was deleted from thesecurity table (@SCR_SECURITY) byexecuting rules.

Action: Contact the Security Administrator.

Set security of SCREEN % by % toinsert recordSource: Audit Log Message

Explanation: A screen entry was inserted into thesecurity table (@SCR_SECURITY) byexecuting rules.

Action: Contact the Security Administrator.

Set security of SCREEN % by % toupdate recordSource: Audit Log Message

Explanation: The security information (e.g.classification) of the specified screen waschanged by the indicated user.

Action: No action required.

Set security of TABLE % by % to deleterecordSource: Audit Log Message

Explanation: A table entry was deleted from thesecurity table (@TBL_SECURITY) byexecuting rules.

Action: Contact the Security Administrator.

TIBCO Object Service Broker Messages Without Identifiers

Page 407: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 393

Set security of TABLE % by % to insertrecordSource: Audit Log Message

Explanation: A table entry was inserted into thesecurity table (@TBL_SECURITY) byexecuting rules.

Action: Contact the Security Administrator.

Set security of TABLE % by % to updaterecordSource: Audit Log Message

Explanation: The security information (e.g.classification) of the specified table waschanged by the indicated user.

Action: No action required.

Set security of USERID % by %Source: Audit Log Message

Explanation: The security information for theindicated userid was changed. Because someof the changes take effect immediately, andothers may not take effect until the next timethe user logs on, it is recommended thatchanges are made to a user's securityinformation only when the user is not on thesystem.

Action: No action required.

Set security of USERID % to changelogon password deniedSource: Audit Log Message

Explanation: The user cannot change the logonpassword because the user failed to providethe current password.

Action: No action required.

Setting of blank overlap for report field"%" not allowed because blank overlapenabled for report table "%"Source: Report Server

Explanation: You cannot alter the blank overlapfor a report field if the blank overlap settingwas requested for the same report table.

Action: Do not use the blank overlap option on areport table basis. Set the blank overlap foreach report field of the report table.

Setup "%" %Source: Character-based Text Editor

Explanation: The changes to the given setuphave been processed as indicated.

Action: No action required.

Setup "%" cannot be %Source: Character-based Text Editor

Explanation: Your specified action cannot beperformed on the given setup. For exampleyou may be attempting to save or delete thePRINT setup. This is not allowed sincePRINT is one of the standard setups.

Action: No action required.

Setup "%" to be %Source: Character-based Text Editor

Explanation: A message to confirm that thespecified action is to be performed on thegiven setup.

Action: Follow the instruction to confirm theaction or not.

TIBCO Object Service Broker Messages Without Identifiers

Page 408: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

394 |

Severe communication errorSource: External Gateway Logon

Explanation: An error has been determinedbetween the gateway/server EE and theData Object Broker it is communicating with.

Action: Check the communications definitionsand their status.

Severe error in Dynamic Object FacilitySource: TAM

Explanation: The Dynamic Object Facilityencountered an event that should neverhappen in normal operation.

Action: Contact TIBCO Support.

Severe error in VSAM server: Feedbackcode = %Source: TAM

Explanation: The VSAM I/O request could notbe completed successfully. The feedbackcode (displayed in hexadecimal) correspondsto the 3-byte RPL feedback area described inthe current VSAM Macro InstructionReference IBM manual.

Action: Refer to the IBM manual for additionalinformation about the type of error thatoccurred.

Severe error in VSAM ServerSource: TAM

Explanation: An error occurred when you triedto access a VSAM data set. The VSAM RPLfeedback return code and reason code maybe included in this message.

Action: If the RPL feedback code is provided,check the z/OS system documentation forfurther explanation.

Severe error obtaining bound table "%"Source: TAM

Explanation: No occurrence found for the boundtable. This is additional informationconcerning bound storage. The messageappears in the system log when a transactionfailure causes other problems.

Action: No action required.

Severe error occurred incommunications ServerSource: TAM

Explanation: A message could not be sent to theData Object Broker or a gateway/server or amessage reply was not received from theData Object Broker or gateway/server.

Action: Data Object Broker output or logs willgive further information. The user messagelog may also provide a message issued by theData Object Broker or gateway/server.

After the Data Object Broker orgateway/server problem has been resolved,it may be necessary to log off the usersession and log back on.

Severe error occurred in TDS ServerSource: TAM

Explanation: The native server is unable tosatisfy the request. The message log willcontain a more detailed error message.

Action: Review the message log.

TIBCO Object Service Broker Messages Without Identifiers

Page 409: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 395

Severe IMS error occurredSource: TAM

Explanation: The IMS Gateway could notcontinue.

Action: Check the IMS Gateway log for errormessages.

Shareable Tool % failed: %Source: Builtin Routines

Explanation: The indicated tool failed for thereason shown.

Action: Use the reason shown to correct thefailure. If you need further help, contactTIBCO Support with the log:

• Internal processing error - contact TIBCOSupport with the log

• Truncation occurred - contact TIBCOSupport with the log

• Input parameter specification error -contact TIBCO Support with the log

• Source literal has invalid length - correctthe length of the source literal to match therequirements

• Source field has invalid length - correct thelength of the source field to match therequirements

• Source literal has invalid format - correctthe format of the source literal

• Source literal contains invalid data -examine the literal and correct the contentsto match the specification

Shortage of memorySource: Batch Client

Explanation: The client machine ran out ofmemory.

Action: Try to kill some processes.

Shortage of memorySource: Start Execution Environment

Explanation: The client machine ran out ofmemory.

Action: Try to kill some processes.

Show IF NO OWNER only valid forOptional or Manual setsSource: Table Definer

Explanation: Invalid SHOW flag. Show IF NOOWNER is only supported for set optionsOA, OM and MM.

Action: Set SHOW flag to N.

Show IF SET EMPTY invalid for 2ndlevel record in a parameterized tableSource: Table Definer

Explanation: The second-level record in theaccess path cannot have "SHOW IF SETEMPTY" if the table is parameterized.

Action: Set SHOW flag to N.

SHOW indicator invalid (Y/N/blank)Source: Table Definer

Explanation: Invalid value entered for SHOWindicator.

Action: Specify value Y, N, or blank for SHOWindicator.

TIBCO Object Service Broker Messages Without Identifiers

Page 410: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

396 |

Side title is too long to fit the screenSource: Menu Definer

Explanation: The side title exceeds the width ofthe screen.

Action: Shorten the title or remove optional itemssuch as the library name, TEST andBROWSE, or the date and time.

Signature does not match parametersfor Java external routine %Source: Interpreter

Explanation: The signature of the Java externalroutine in the LIBNAME field of thecorresponding row in the table ROUTINESdoes not match one or more of the parameterdescriptions in the corresponding instance ofthe table ARGUMENTS.

Action: Correct either the signature or theparameter description in the ARGUMENTStable instance.

Single Occurrence Editor is notsupported for this utilitySource: Table Editor

Explanation: You invoked the Single OccurrenceEditor which is not supported in this utility(e.g., BROWSER).

Action: If you need to use the Single OccurrenceEditor, terminate the current transaction andinvoke a utility (e.g., STE, STEBROWSE) thatsupports the Single Occurrence Editor.

Single Rule Menus can not be updated;they may be used onlySource: Menu Definer

Explanation: Support for Single Rule Managermenu type is being removed since thiscapability is encompassed in other menutypes (e.g., Simple). Use of existing SingleRule menus (via DISPLAY_MENU orSINGLEMGR) is supported, but support willeventually be removed when these menushave been converted to other menu types.

Action: No action required. You cannot updatethe menu.

SIX field "%" does not exist; cannot saveSource: Table Definer

Explanation: A secondary index has been builton the indicated field since the Table Definerwas opened but this field has either beenrenamed or deleted from the definition.

Action: If the definer allows it, you can restorethe field name or add the field back to thedefinition. Otherwise, you can save as a newtable definition or exit without saving.

SIX now exists on %; % must equal "%"Source: Table Definer

Explanation: A secondary index has been builton the indicated field since the Table Definerwas opened but the field attribute specifiedhas been changed.

Action: Change the attribute value for the field tothe value specified.

TIBCO Object Service Broker Messages Without Identifiers

Page 411: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 397

Size error detected in %. Conversion of% % to % % failedSource: Interpreter

Explanation: Internal error that may indicate aproblem with the scheduling of rules. Themessage log contains a more detailed errormessage.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Size error detected in conversion ofargument # of % routine "%"Source: Interpreter

Explanation: A routine was called with anargument value that is too big for the routineargument.

Action: Verify the argument value that youpassed.

Some objects could not be FETCHedbecause they do not existSource: Security

Explanation: Some of the objects that youattempted to FETCH from the object set areobjects that do not exist. These objects werenot fetched.

Action: No action required.

Some occs no longer exist; some areincomplete due to securitySource: Select Data

Explanation: Some of the selected occurrences nolonger exist (i.e. they were deleted). Othersare not viewable by you because of security,for these occurrences you will only see theprimary key, the other fields will be blank.

Action: No action required.

Some occurrences no longer existSource: Select Data

Explanation: Some of the selected occurrences nolonger exist (i.e. they were deleted).

Action: No action required.

Some type of Static SQL to be generatedmust be chosenSource: Static SQL for DB2 Gateway

Explanation: You made a request to generateStatic SQL, but you did not identify the typeof Static SQL to generate.

Action: Under the columns marked by S, I, D, R,enter Y to generate SELECT (Get/Forall),INSERT, DELETE, and REPLACE Static SQLstatements respectively. Enter N under theones for which no Static SQL statement is tobe generated.

Some Unicode or raw data fields areomitted from table %Source: Screen Definer

Explanation: Unicode and raw data fields are notallowed in screens.

Action: None.

TIBCO Object Service Broker Messages Without Identifiers

Page 412: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

398 |

Some Unicode or raw data fields wereomitted from table %. Press <Enter>Source: Report Definer

Explanation: Unicode and raw data fields are notallowed in reports.

Action: None.

Sort field "%" for report "%" is anunsupported syntax for sortingSource: Report Server

Explanation: SORT only supports syntaxes of B(binary), P (packed), C (fixed-length string),and V (variable-length string).

Action: Redefine the syntax of the report field toallow sorting.

Sort for report "%" failed; # rows readbut # rows output by sortSource: Report Server

Explanation: The number of SORT input recordsdoes not match the number of SORT outputrecords.

Action: Contact TIBCO Support.

Sort for report "%" failed with a returncode of #Source: Report Server

Explanation: The system sort failed when theserver attempted to print the report.

Action: Refer to your installation system sortdocumentation to determine the reason forthe error return code.

SORTIN/SORTOUT record totalmismatch; module "%"Source: Session Manager

Explanation: A mismatch occurred between thenumber of records input to the sort and thenumber of records output. The name of themodule in which this mismatch occurred isspecified.

Action: Call your system administrator to checkthe sort parameters for validity, and to checkthe return code in Register 15 against theappropriate vendor's manual. Correct theproblem as required.

Source & destination libraries are alike,must specify a nameSource: Copy Defn/Data

Explanation: You have requested to copy a rulesuch that the source and destination librariesare the same. To copy the rule, you mustsupply a new name.

Action: Supply a new name for the rule.

Source & Destination libraries arealike; must specify a nameSource: Copy Definition

Explanation: You have specified only one libraryas both the source and destination of thecopy.

Action: You must specify a rule name to copyinto since the source and destination librariesare identical.

TIBCO Object Service Broker Messages Without Identifiers

Page 413: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 399

Source (rule) name must be specifiedfor "D"erived indicatorSource: Table Definer

Explanation: You entered a D in the SRC field,but did not enter anything in the SOURCENAME field.

Action: Enter the name of a functional rule thatwill derive values for the field, or remove theD from the SRC field.

Source expression for report field "%"of report table "%" is too complex toevaluate - stack overflowSource: Report Server

Explanation: Insufficient storage exists toevaluate a derived report field. This problemcan be caused by a derivation based on a rulecall that returned a string which is too long.

Action: Modify the rule to return a shorter string.

Source location parm "%" is not definedin parameter listSource: Table Definer

Explanation: Location parameter in the sourcetable is missing from the subview tabledefinition.

Action: Ensure the location parameter of thesource table is being defined in the subview.

Source name of field % is undefined insource tableSource: HLIPREPROCESSOR

Explanation: The preprocessor cannot find thename of a field in the definition.

Action: Check the definitions of the subview andthe base table.

Source name of parameter % isundefined in source tableSource: HLIPREPROCESSOR

Explanation: The preprocessor cannot find thename of a parameter.

Action: Check the definition of the subview andthe base table.

Source name required for "S" indicatorSource: Table Definer

Explanation: You entered an S in the SRC field,but did not provide a field name in theSOURCE NAME field.

Action: Enter a field name from the source tablein the SOURCE NAME field, or remove the Sfrom the SRC field and type the source fieldname directly in the FIELD NAME field.

Source parm "%" is already defined inparameter listSource: Table Definer

Explanation: The specified parameter of thesource table has been defined more than oncein the parameter information section of asubview table definition.

Action: Remove the excess definitions of theindicated source parameter.

TIBCO Object Service Broker Messages Without Identifiers

Page 414: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

400 |

Source parm "%" is already defined inselectionSource: Table Definer

Explanation: The indicated parameter of thesource table is defined in both the selectionsection and the parameter informationsection of the subview table definition.

Action: Remove the indicated parameter fromthe selection criteria or from the parameterinformation.

Source parm "%" is not defined inselection or parameter listSource: Table Definer

Explanation: The indicated parameter of thesource table is not defined in the selectionsection nor in the parameter section of thecurrent subview definition.

Action: Define the indicated parameter of thesource table in either the selection criteria(SELECT field) or the parameter informationfor the subview.

Source parm "%" is not in source table"%"Source: Table Definer

Explanation: The indicated parameter does notexist in the indicated source table.

Action: Do one of the following:

• Look at the definition of the source table toget the name of an existing parameter

• If the source table does not contain data,you can add a parameter to the sourcetable.

Source parm "%.%" not defined insubview "%"Source: TAM

Explanation: A source table parameter was notspecified. It must be specified in one of thefollowing places:

• The subview definition

• The subview stored selection

• The WHERE clause of the request.

Action: Specify the source table parameter in oneof the following:

• Subview definition

• Subview stored selection

• WHERE clause of the request.

Source record length (#) > lrecl (#) of theoutput dataset "%" for "%"Source: Builtin Routines

Explanation: The length of the record to beoutput to a data set is bigger than the definedlength of a record in the data set.

Action: Ensure that the source record is not toobig for the data set record, or define the dataset record length to be longer.

Source string for report field "%" ofreport table "%" is too bigSource: Report Server

Explanation: The source of a derived report fieldis too complex to be stored in the ReportServer data structure.

Action: Simplify the source of the derived field.

TIBCO Object Service Broker Messages Without Identifiers

Page 415: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 401

Source table "%" cannot be updatedbecause the data is boundSource: TAM

Explanation: The user tried to update a sourcetable in which data is stored in the boundarea.

Action: Correct the appropriate rule and do notupdate this table.

Source table "%" does not existSource: Table Definer

Explanation: The indicated source table does notexist.

Action: You must define the source table beforedefining a parameter (PRM) or subview(SUB) table for it.

Source table "%" has no data parametersSource: Table Definer

Explanation: The indicated source table does nothave any data parameters; therefore thecurrent PRM table cannot be created.

Action: Provide the name of a table that has dataparameter(s) as the source for the PRM table,or cancel the table definition.

Source table "%" no longer exists. UseSelect Table(s) screen to verifySource: Report Generator

Explanation: One of the source tables used in thisreport no longer exists. The table has eitherbeen deleted or renamed.

Action: Verify if the table has been deleted orrenamed, and do one of the following:

• If the table has been renamed, select "SelectTable(s)" from the main Report Generator

screen. Exclude the table in question fromthe report and enter the new table name.

• If the table has been deleted and is nolonger required in the report, select "SelectTable(s)" from the main Report Generatorscreen and exclude the table in questionfrom the report.

Source table "%" potential occurrencewidth is too wide to COMMITSource: TAM

Explanation: The total length of the occurrence inthe internal storage is greater than 2 016bytes.

Action: Reduce the occurrence length in thedefinition of the table.

Source table is required for table type %Source: Table Definer

Explanation: You did not enter the name of asource table.

Action: Enter the name of a table that willprovide data for your current tabledefinition.

Source table of type "%" is not allowedSource: Table Definer

Explanation: You cannot define a parameter(PRM) or subview (SUB) table on theindicated type of table.

Action: If you are defining a subview table, youcan choose a DB2, 204, IDM, IMP, IMS, TDS,or VSM table as the source table.

If you are defining a PRM table, you canchoose an IMP, TEM, or TDS table as thesource.

TIBCO Object Service Broker Messages Without Identifiers

Page 416: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

402 |

Source value overflowing maskspecifications in $PICSource: Builtin Routines

Explanation: The number you have used in aVALUE specification requires more digitplaceholders than are available in the MASKspecification.

Action: Verify that MASK, VALUE specificationsare compatible.

SOURCENAME must be % when SRCis %Source: Table Definer

Explanation: The values of SOURCENAME andSOURCE must either be both present or bothset to nulls.

Action: Remove the values from SOURCENAMEand SOURCE, or set the both their valuesaccordingly.

Specification of parameter valuesCANCELLEDSource: Security

Explanation: You canceled from the screen whereyou supply parameter values to specify atable instance.

Action: No action required.

SPECIFIED ACCUMULATIVESCREEN PRINT INVALID, MUST BE"A", "E" OR "N"Source: S6BTLADM - MONITOR PROCESS

Explanation: The value you entered for theaccumulative screen print function is invalid.

Action: Correct the input and retry your request.See the online help for more information.

SPECIFIED BUFFER NUMBER ISINVALIDSource: S6BTLADM - PAGE DISPLAY

Explanation: The buffer number entered isnegative, too large or contains invalidcharacters.

Action: Specify a valid number

SPECIFIED DISPLAY SCREENINVALID, MUST BE "A" OR "I"Source: S6BTLADM - MONITOR PROCESS

Explanation: The value you entered to identifywhich screen is to be displayed is invalid.

Action: Correct your input and retry the request.See the online help screens for additionalinformation.

SPECIFIED INTERVAL IS OUT OFRANGE (5 TO 60)Source: S6BTLADM - MONITOR PROCESS

Explanation: The time interval you specified isnot within the specified range.

Action: Correct the interval and retry yourrequest.

SPECIFIED INTERVAL SCREENPRINT INVALID, MUST BE "Y" OR"N"Source: S6BTLADM - MONITOR PROCESS

Explanation: The value you specified for theinterval screen print is invalid; it must be Y orN.

Action: Correct your input and retry the request.

TIBCO Object Service Broker Messages Without Identifiers

Page 417: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 403

SPECIFIED ITERATION IS OUT OFRANGE (5 TO 60)Source: S6BTLADM - MONITOR PROCESS

Explanation: The number of iterations yourequested is outside the specified range.

Action: Correct the iteration count and retry therequest.

SPECIFIED MEMORY ADDRESS-LENGTH CONTAINS INVALIDCHARACTERSSource: S6BTLADM - MEMORY DISPLAY

Explanation: The value you entered for thememory location and or response lengthcontains invalid characters.

Action: Correct your input and retry the request.

SPECIFIED SCHEDULE IS NOTDEFINEDSource: S6BTLADM-Resource Management

Explanation: You have identified a schedulename that is invalid.

Action: Either rekey the schedule name or use<PF10> to determine what schedules arecurrently available.

SPECIFIED SEG-DSN-ENTCONTAINS INVALID CHARACTERSSource: S6BTLADM - RPP DIRECTORY

Explanation: The segment-data set or data setnumber you specified contained invalidcharacters.

Action: Correct your input and retry yourrequest.

SPECIFIED SEG-PAGE CONTAINSINVALID CHARACTERSSource: S6BTLADM - PAGE IMAGES

Explanation: The segment and or page numberyou have specified is invalid.

Action: Correct your input and retry.

SPECIFIED START ENTRY EXCEEDDIRECTORY LIMITSSource: S6BTLADM - RPP DIRECTORY

Explanation: The entry number you specified(segment-data set-entry number) exceeds thelimit of the resident page directory.

Action: Correct the entry number and retry yourrequest.

Specify "Default" fields in "Source"section for Objectset "%"Source: Copy Defn/Data

Explanation: You requested to copy an object set.However, you did not specify informationrequired to identify objects referenced by thatobject set. For example, if the object setcontains rules and you want to copy them aswell, you must specify a Default Library.

Action: Supply the needed information.

TIBCO Object Service Broker Messages Without Identifiers

Page 418: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

404 |

Specify a medium and select an actionto produce reportSource: Report Generator

Explanation: This instruction appears when youenter the Execute screen. Before you do so,you may want to edit your report title,modify your field labels, add masks for thefields, save the report to the MetaStor only, orcreate the report rule.

Action: Use Y to select one of the four destinationmedia, as well as SAVE REPORT AND SENDTO DEST; then press <Enter> to produceyour report.

Specify a parameter, FILE, or DDNAMESource: Table Definer

Explanation: You must specify either aparameter, Data Set or DDname for a VSMtable.

Action: Define a parameter or enter a data setname or DDname.

SPECIFY A SELECTION CODE ANDPRESS <ENTER> FOR A NEW HELPTOPICSource: S6BTLADM - COMMON MESSAGES

Explanation: You must enter the selectionnumber specified at the end of the currenthelp text in order to progress to the next level(more detailed) of Help text.

Action: No action required.

Specify all parameters either with tablename or in WHERESource: HLIPREPROCESSOR

Explanation: Some table parameters appear inparentheses after the table name, and someappear in the WHERE clause.

Action: Put all the parameters together in oneplace or the other.

Specify an IDgen parameter (parameterwith a reference table)Source: Table Definer

Explanation: You turned the IDgen flag on, butyou did not specify an IDgen parameter forthe table. A parameter with a reference tableis treated as an IDgen parameter.

Action: Specify an IDgen parameter, or turn theIDgen flag off.

Specify any justification required fortitles shownSource: Report Definer

Explanation: In a titles only report table, all rowsare marked with T. The Titles/Mask screencan be used to specify any justificationrequired for the displayed title rows.

Action: Specify any justification for title rows.

TIBCO Object Service Broker Messages Without Identifiers

Page 419: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 405

Specify Default fields in Source sectionfor Objectset "%"Source: Copy Definition

Explanation: You have specified an object set butyou have not specified the Default Libraryand Default Environment in the Sourcesection. These are required to properlyidentify all objects in the object set.

Action: Fill in the DEFAULT LIBRARY andDEFAULT ENVIRONMENT field in theSource section. Default Library will be usedto find RULES in the object set; DefaultEnvironment will be used to copy screens inthe object set.

Specify either default printer options ordata set, not bothSource: Batch Submission Tool

Explanation: You specified both the defaultprinter options and a data set.

Action: Specify only one option.

Specify FILE or DDNAMESource: Table Definer

Explanation: You must specify a data set name ora DDNAME for IMP or EXP tables.

Action: Enter a data set name or a DDNAME.

Specify NEW OWNER to transferownership of selected objectsSource: Security

Explanation: You attempted to use theTRANSFER&EXIT function from theTransfer Ownership function withoutspecifying the new owner of objects to betransferred.

Action: Type in the userid of the new owner, oruse the USERIDS function to select from a listof potential new owners.

Specify one report medium at a timeSource: Report Generator

Explanation: The report can be sent to only onedestination at a time, and you have specifiedmore than one.

Action: Specify one destination after the other.

SPECIFY OR PLACE THE CURSORON THE DESIRED TYPE AND RETRYYOUR REQUESTSource: S6BTLADM-Resource Management

Explanation: In order to proceed from thecurrent Resource Type List screen you mustidentify the "Type" you wish to process. Thetype can be identified by cursor positioningor by keying it into the Type input field at thebottom of the screen.

Action: Identify the type and retry the request.

TIBCO Object Service Broker Messages Without Identifiers

Page 420: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

406 |

Specify Parameter(s) screen unavailable- no parameters for specified tablesSource: Report Generator

Explanation: The Specify Parameter(s) screen isirrelevant because none of the source datatables are parameterized.

Action: No action required.

Specify required UNIT attributeSource: General

Explanation: You must specify the UNIT for theobject.

Action: Enter a valid identifier for UNIT.

Specify table name for parameter % "%"Source: Report Generator

Explanation: The first percent sign (%) isreplaced with Name or Value. The indicatedparameter name or parameter value is notaccompanied by a table name.

Action: Enter the table name for the parametername or value.

Specify the class of parameterSource: Table Definer

Explanation: CLASS is a required attribute for aparameter and a value must be specified forit.

Action: Specify the appropriate class for theparameter. D is for data parameter and L isfor Location parameter.

Specify the name of a tableSource: Table Editor

Explanation: Your action cannot be performedbecause you have not specified the name ofthe table.

Action: Specify the name of the table.

Specify TYPE and PATTERN beforerequesting SEARCHSource: Security

Explanation: You requested the SEARCHfunction in the Transfer Ownership screen,but you did not specify the type of object tosearch for and the pattern to search for.

Action: Specify the pattern (e.g., *USR40* orXYZ) and the type of object being sought:TBL (table), SCR (screen), RPT (report), LIB(library), GRP (group). Press the SEARCH PFkey again.

Specify value for %Source: Table Definer

Explanation: Required value is missing.

Action: Specify a value for the object indicated inthe message.

Specify values for ALL table parametersor set ALL DATA="Y"Source: Security

Explanation: One of the following situationsoccurred:

• You are specifying a table instance or thewhole table before managing permissionsto a parameterized table

• While specifying table permissions for anobject set definition, you left ALL DATA

TIBCO Object Service Broker Messages Without Identifiers

Page 421: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 407

set to N and did not specify values for eachparameter of the table

Action: If you want to refer to the whole table, setALL DATA to Y and set all the parametervalues to NULL. If you want to refer to justone instance of the table, set ALL DATA to Nand supply a value for each table parameterbefore pressing <Enter> to continue.

Split this line before trying to replace"%" with "%"Source: Rule Editor

Explanation: Replacing the first token by thesecond one may cause a line overflow.

Action: If appropriate, split the line as suggested.

SRBMODE=N SRB STATISTICS NOTSUPPORTEDSource: S6BTLADM - GENERAL STATS

Explanation: The user has attempted to retrieveSRB enclave statistics. These are onlysupported if SRBMODE=Y or Z.

Action: None required

Start by using Select Table(s) screenSource: Report Generator

Explanation: To generate a report, you must firstsupply a source table name. The sourcetable(s) will provide the information needed.

Action: Type S in the Select Table(s) field toaccess the screen.

START CONNECTION REQUESTREJECTED, CONNECTION INPROGRESS OR AT LIMITSource: S6BTLADM-Resource Management

Explanation: After verifying your <PF9> startrequest the system determined either all therequired connections were present or thesystem was currently initiating connectionsfor the displayed resource detail.

Action: No action required.

START NUMBER must be less than orequal to END NUMBERSource: Promotion

Explanation: The START NUMBER and ENDNUMBER fields provide a way to limit therange of the change requests queried. Thefirst number in the range must be less than orequal to the last number. If both numbers arethe same, only one change request will be inthe range of the query.

Action: Correct the range and try the queryagain.

START position operand of theSUBSTRING function is greater thanthe length of the stringSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

TIBCO Object Service Broker Messages Without Identifiers

Page 422: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

408 |

START position operand of theSUBSTRING function is less than 1Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

START REQUEST IS INVALID FORRESOURCES THAT DO NOTSUPPORT USER IDPREFIXSource: S6BTLADM-Resource Management

Explanation: You pressed <PF9> to start a DataObject Broker generated connection;however, the Detail entry currentlydisplayed does not have a "User ID Prefix"and does not support connection generation.

Action: No action required; invalid operation.

Starting *** Phase 1 of Apply ***Source: Promotion

Explanation: Starting Phase 1 of the applyprocess used to apply a promotion to aseparate system. There are 3 phases.

Action: No action required.

Starting *** Phase 2 of Apply ***Source: Promotion

Explanation: Starting Phase 2 of 3 phases.

Action: No action required.

Starting *** Phase 3 of Apply ***Source: Promotion

Explanation: Starting the last phase.

Action: No action required.

STARTING APPLY FOR CHANGEREQUEST #% FROM NODE %Source: Promotion

Explanation: The Promotion tool is starting theapplication of the specified change requestfrom the specified source node.

Action: No action required.

STARTING BACKOUT OF CHANGEREQUEST #%Source: Promotion

Explanation: The Promotion utility is starting toback out the specified change request.

Action: No action required.

Starting EXECUTE of rule %Source: Debugger Utility

Explanation: Provides feedback.

Action: No action required.

STARTING EXTRACT OF CHANGEREQUEST #%Source: Promotion

Explanation: The Promotion utility is extractingthe change request specified.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 423: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 409

STARTING PROMOTION OFCHANGE REQUEST #%Source: Promotion

Explanation: The promotion of the specifiedchange request is beginning.

Action: No action required.

Starting TRANSFERCALL to rule %Source: Debugger Utility

Explanation: Provides feedback.

Action: No action required.

Static SQL generated for Table %Source: Static SQL for DB2 Gateway

Explanation: Static SQL was successfullygenerated for the table.

Action: No action required.

Static SQL removed from Table %Source: Static SQL for DB2 Gateway

Explanation: The definition of the table indicatesthat Static SQL is no longer available.

Action: Manually delete the code previouslygenerated.

Status cleared for % % %Source: Promotion

Explanation: You have cleared the status for thespecified object. If this object was previouslyselected for promotion, deletion, orexecution, it is no longer included in thechange request.

Action: No action required.

Status of change request % changed to"%"Source: Promotion

Explanation: The status of the specified changerequest has been changed to one of thefollowing:

• A (Accepted)

• B (Back Out)

• C (Completed)

• I (Incomplete)

• J (Batch Job Submitted)

• L (Loaded)

• P (Pending)

• R (Backed Out)

• S (Saved)

• U (Unaccepted)

• V (Verified)

• X (Extracted).

Action: No action required.

Status of promotion request % is not "C"Source: Promotion

Explanation: You tried to back out a promotion,but you cannot do so unless the status is C(Completed).

Action: No action required.

Stop Debugger RequestedSource: Builtin Routines

Explanation: You have entered theSTOPDEBUGGER primary command. Thisprovides feedback.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 424: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

410 |

STOP TYPE = type AND GROUP =group REQUEST HAS BEEN ISSUEDSource: S6BTLADM-Resource Management

Explanation: This message acknowledges thereceipt of confirmation for the stop serverrequest for the type and group identified inthe message.

Action: No action required.

Storage at error % %Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log.

Action: For more information, show this messageto a System Programmer.

Storage limit exceededSource: Session Manager

Explanation: Insufficient memory exists to runthe transaction.

Action: Ensure that the applications you arerunning do not use an excessive amount ofstorage. Review the usage of session tables.

Storage management initialization ofscope TRANSACTION failed with areturn code of #Source: Session Manager

Explanation: Internal error.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Storage management termination ofscope TRANSACTION failed with areturn code of #Source: Session Manager

Explanation: Internal error.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Stored procedure extract verifysuccessful, PF3 to extractSource: Table Definer

Explanation: The input values provided return 1or more result sets. @RESULT@ contains thenumber returned.

Action: PF3 to extract. Note: you will be asked toexecute the stored procedure one more time.

Stored procedure result set tablecreation SUCCESSFULSource: Table Definer

Explanation: The result set table definitions havebeen created

Action: PF5=Info to view the tables created

Stored selection error: %Source: TAM

Explanation: A table definition stored selectioncould not be parsed. The message log willcontain a more detailed error message.

Action: Review the message log.

TIBCO Object Service Broker Messages Without Identifiers

Page 425: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 411

Stored selection field "%" not in table"%"Source: TAM

Explanation: A stored table selection refers to afield which is not specified in the definitionof the table.

Action: Do one of the following:

• Include the field in the table definition.

• Remove the stored table selection.

String "%" is not a valid nameSource: General

Explanation: The string does not contain a validObject Service Broker name.

Action: Enter a valid Object Service Broker name.Valid entries are any character string up to 16characters beginning with a letter (A-Z) or aspecial character ($ or #), and continuingwith more letters, special characters, digits(0-9), or underscore characters (_).

String "%" is not a valid nameSource: Secure Audit Log

Explanation: The string does not contain a validObject Service Broker name.

Action: Enter a valid Object Service Broker name.Valid entries are any character string up to 16characters beginning with a letter (A-Z) or aspecial character ($ or #), and continuingwith more letters, special characters, digits(0-9), or underscore characters (_).

String size error on table %; occurrenceskipped % %Source: Unload/Load

Explanation: The specified field of the specifiedtable was too small to hold the specifiedvalue; hence, the occurrence was skipped.

Action: No action required.

String too long to be scriptedSource: Character-based Text Editor

Explanation: The string is too long to be scriptedand displayed on the screen.

Action: Shorten the string.

String value is too large to returnSource: Interpreter

Explanation: One of the following occurred:

• The argument LENGTH forHEADSTRING exceeds 4000.

• The argument LENGTH for TAILSTRINGexceeds 3999.

Action: Verify the argument of the tool involved.

STRINGSIZE detected whenevaluating source of report field "%" ofreport table "%"Source: Report Server

Explanation: The derived report field is too smallto hold the string value that is assigned to it.

Action: Review the source of the derived reportfield and the input data used to set its value.Change the definition of the derived fieldappropriately.

TIBCO Object Service Broker Messages Without Identifiers

Page 426: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

412 |

Subfield cannot be a parameterSource: Table Definer

Explanation: You cannot select a subdividedfield as a parameter.

Action: No action required.

Subfield cannot be a primary keySource: Table Definer

Explanation: You cannot select a subdividedfield as a primary key.

Action: No action required.

Subfields cannot be access value fieldsSource: Table Definer

Explanation: You cannot store an access value ina subdivided field.

Action: No action required.

Submit failed: %Source: Batch Submission Tool

Explanation: An error was encountered when abatch request was submitted to a batchqueue.

Action: Contact TIBCO Support.

Submitted % - output will appear in %Source: Print Rules

Explanation: You pressed <PF5> or <PF6> anddirected the output to a data set. The outputis the PRINT TREE if you pressed <PF5>, orCROSS REFERENCE if you pressed <PF6>.The name of the data set is given in themessage.

Action: No action required.

Submitted % to print at %Source: Secure Audit Log

Explanation: This message notifies you that youhave printed the specified report to the givenmedium.

Action: No action required.

Submitted %Source: Print Rules

Explanation: You pressed <PF5> or <PF6> withHardcopy set to Y. The output is either aPRINT TREE if you pressed <PF5>, or aCROSS REFERENCE if you pressed <PF6>.

Action: No action required.

Subroutine "%" is being called as afunctionSource: Interpreter

Explanation: You are using a procedural routineas a function. Note that CICS or IMS externalroutines may not be used as functions.

Action: Verify the name of the routine or theusage.

Subview "%"'s primary key fields arenot the same as its source table primarykey fieldsSource: TAM

Explanation: The primary key fields of thesubview must be compatible with the sourcetable, and the same number of fields mustexist.

Action: Change the definition of the subview.

TIBCO Object Service Broker Messages Without Identifiers

Page 427: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 413

Subview "%" has different primarykey(s) than its sourceSource: TAM

Explanation: The source field name of a subviewprimary key field is different from the nameof the primary key for the source table.

Action: Modify the subview table definition sothat the source field of the subview primarykey is the same as the primary key in thesource table.

Subview selection criteria not metSource: TAM

Explanation: An INSERT, REPLACE, or DELETEoperation on a subview table has failed. Theoccurrence to be manipulated did not meetthe stored selection criteria.

Action: Modify the selection criteria in thesubview table definition.

Sum of parameter value lengths (%)exceeds maximum (%)Source: Security

Explanation: You are specifying a table instanceby providing values for the table'sparameters (i.e., before viewing apermissions list of the instance, or whilespecifying table instances for the object setdefinition), and the sum of the lengthsexceeds the maximum.

Action: You can shorten the parameter values oruse the whole table permissions to set thepermissions.

SUMMARY field "%" of report table"%" must be a sort field of across report"%"Source: Report Server

Explanation: For Across Reports, all SUMMARYfields must also be SORT fields.

Action: Use the Report Definer to add theSUMMARY field to the list of SORT fields.

SUMMARY LIST SORTED BYXXXXXXXXXXXXXXSource: S6BTLADM - USER ACTIVITY

Explanation: Notification of the sort order of thedisplayed list of Execution Environmentconnections.

Action: No action required.

SUMMARY_BY field must exist ifACROSS_BY specifiedSource: Report Definer

Explanation: All Across Reports must besummaries. SUMMARY_BY controls rows;SORT_ACROSS_BY controls columns.

Action: Enter at least one SUMMARY_BY field.

TIBCO Object Service Broker Messages Without Identifiers

Page 428: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

414 |

SUPPLIED TYPE (type) IS INVALID,RETRY YOUR REQUEST OR PRESSPF5 TO ADDSource: S6BTLADM-Resource Management

Explanation: The type value you keyed in doesnot exist.

Action: If you want to add a new Resource Type,press <PF5> to invoke the Resource Detailscreen in input mode so the new resource canbe added. If you are trying to display anexisting Resource, either rekey the value orselect the type from the displayed list.

SUPPLIED TYPE (type) IS MISSINGOR INVALID, STOP REQUEST WILLBE IGNOREDSource: S6BTLADM-Resource Management

Explanation: When the Stop request was madethe cursor was not positioned on a definedResource Type or the value keyed in the Typeinput field does not identify an existingResource Type.

Action: Identify a valid Resource Type andreissue the Stop request.

Supply report nameSource: Report Definer

Explanation: A report name is required.

Action: Supply a report name.

Supply target (line command A = after)for MOVE commandSource: Report Definer

Explanation: A move (M) line command wasissued without a corresponding after (A) linecommand to indicate where to move therows.

Action: Place an after (A) line command on therow that is the target position for the movedrows.

SYNC failed - too many updates to becommittedSource: TAM

Explanation: The updates to be committedexceeded 16 KB in size, and therefore werenot applied.

Action: Review the message log.

Change the appropriate rules to commitmore frequently.

SYNC processing failed, possibleduplicate or non-existent key in massupdate tableSource: TAM

Explanation: Within the mass insert data, anentry with a duplicate key or an entrywithout a key occurred.

Action: Find and remove the duplicate entry, orensure that every entry has a key.

TIBCO Object Service Broker Messages Without Identifiers

Page 429: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 415

Syntax % is not allowed for primary key"%"Source: Table Definer

Explanation: You cannot define the specifiedsyntax as a primary key. Valid syntaxes for aprimary key are:

• C - fixed-length character string

• V - variable-length character string

• B - binary

• P - packed decimal

Action: Do one of the following:

• Change the syntax of the primary key to C,V, B, or P.

• Designate a different field as the primarykey.

SYNTAX ERROR:"%" is not a validfield on table "%"Source: Report Definer

Explanation: The indicated field was entered aspart of a selection string and does not exist inthe current definition of the report.

Action: Ensure that selection strings contain onlyvalid fields that appear in the definition areaof the report.

Syntax error: "%" encountered whenexpecting %Source: HLIPREPROCESSOR

Explanation: An unexpected token was found.

Action: Correct the syntax of the statement.

SYNTAX ERROR: "%" when expecting"%","%","%"Source: Report Definer

Explanation: Syntax error.

Action: Correct the syntax as indicated in themessage.

SYNTAX ERROR: "%" when expecting"%"Source: Report Definer

Explanation: Syntax error.

Action: Correct the syntax as indicated in themessage.

SYNTAX ERROR: input "%"; expected%Source: Parse

Explanation: The input token was seen when theparser expected to see the token named.

Action: Check the syntax of the input and changeit as required.

SYNTAX ERROR: too % ")"Source: Parse

Explanation: You have mismatched parenthesesin your input; there are too few or too manyparentheses.

Action: Review your input and add or removeparentheses as required.

TIBCO Object Service Broker Messages Without Identifiers

Page 430: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

416 |

Syntax error in %Source: Print Table

Explanation: The table name or parameter list isnot syntactically correct.

Action: Check for typing errors.

Syntax error in Derived field definition"%"Source: Report Definer

Explanation: The Rule/Field value entered as adefinition for a derived field contains asyntax error.

Action: Correct the syntax error. If the definitionis a rule or an expression, see the ObjectService Broker documentation for syntaxinformation. If the definition is an ObjectService Broker tool, see the Object ServiceBroker documentation for the correct syntax.

Syntax error in primary command;press <PF1> for HelpSource: Table Editor

Explanation: You entered a primary commandwith invalid syntax.

Action: Press <PF1> for descriptions of validsyntax for the primary commands andcorrect the command.

Syntax error in rule arguments at "%"Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

SYNTAX ERROR in SELECTIONspecified for DAT tableSource: CA Datacom Table Definer

Explanation: Your selection information, in theCORE context of this Table Definition,contains a syntax error.

Action: Go to the CORE context and correct thesyntax error in the SELECTION specification.

Syntax error in signature for Javaexternal routine "%"Source: Interpreter

Explanation: There is a syntax error in thespecification of the Java external routine inthe LIBNAME field of the corresponding rowof the ROUTINES table.

Action: Correct the value of the LIBNAME field.

SYNTAX ERROR on SELECTION forREFD DATA source table "%"Source: Unload

Explanation: One of the objects which wasrequested for unload has, as part of it, somedata which is referenced in the object'sdefinition. However, there is a problem withthe specification of this data to unload in theobject type definition data.

Action: This problem should be reported to theSystem Administrator since it should not bethe case the there are problems in the objecttype specifications for unloadable objects.

TIBCO Object Service Broker Messages Without Identifiers

Page 431: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 417

SYNTAX ERROR on SELECTION forREFD DEFN source table "%"Source: Unload

Explanation: There is a problem in the objecttype definition for one of the objects yourequested to unload.

Action: Report this problem to your SystemAdministrator since there should not be aproblem with object type definitions ofunloadable objects.

Syntax F is not permitted for aparameter definitionSource: Table Definer

Explanation: You cannot define a floating pointfield as a parameter field in a MetaStor IMStable.

Action: Change the syntax of the field or do notselect it as a parameter.

Syntax F is not permitted for a primarykey.Source: Table Definer

Explanation: A field defined with floating pointsyntax cannot be chosen as a primary key fora MetaStor IMS table.

Action: Change the syntax of the field or do notselect it as a primary key.

Syntax of field "%" is not valid forreportsSource: Report Generator

Explanation: The indicated field has a syntax thatis not valid for reports.

Action: Remove the indicated field.

System error, please see your systemadministratorSource: HLIPREPROCESSOR

Explanation: An error occurred in thepreprocessor.

Action: Contact TIBCO Support.

System error - error detected in tablescope stack; expected "%" but found "%"Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

System error - overflow of executorscope stackSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

System error - table "%" has no eventnodesSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

TIBCO Object Service Broker Messages Without Identifiers

Page 432: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

418 |

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

System error - table name "%" cannot befound in executorSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

System error in HLL preprocessor, rule%Source: HLIPREPROCESSOR

Explanation: An error occurred in the indicatedrule.

Action: Contact TIBCO Support.

System error in HLL preprocessor, table%Source: HLIPREPROCESSOR

Explanation: A table provided with the systemcontains an error.

Action: Contact TIBCO Support.

System failed during sync processingSource: TAM

Explanation: The Data Object Broker was unableto complete the updates in a SYNC message.There was either a lock buffer overflow orthere were too many updates.

Action: Commit updates more often. If manytable sets are being updated in the sametransaction, use the EXECUTE statement toupdate them in separate transactions.

System internal error - display ofargument prompt screen failedSource: Session Manager

Explanation: Internal error.

Action: Verify that your 3270 display isfunctioning correctly. If it is not, then contactyour system administrator.

System routines cannot be edited:routine "%"Source: Global Cross Ref. Search

Explanation: You placed the cursor beside asystem routine and pressed <PF6>. Systemroutines cannot be edited.

Action: No action required.

System tables have been generatedSource: Promotion

Explanation: GEN_SYS_TBLS has runsuccessfully.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 433: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 419

System tables have been loadedSource: Promotion

Explanation: LOAD_SYS_TBLS has runsuccessfully.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 434: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

420 |

Messages beginning with: T

T = TITLE rows/cols H = HEADINGrows F = FINAL colsSource: Report Definer

Explanation: The code T or H can be used todesignate a row as a title or heading row. ForAcross reports only, the code T or F can beused to designate a column as a title or finalcolumn.

Action: Enter or change all title or heading rowsby entering the correct code on the commandline for the row. For Across reports only,enter or change all title or final columns byentering the correct code on the line bar at thedesired column.

TABLE.* expected on both sides of anassign-by-name statementSource: Rule Editor

Explanation: An invalid assignment-by-namestatement was detected.

Action: Check the Processing manual for thesyntax of an assignment-by-name statement.

Table "%", field "%" has no source fieldin source table "%"Source: TAM

Explanation: Cannot find the field in the sourcetable that corresponds to the given field.

Action: Use a different source field for the givenfield, and make the appropriate changes inthe definition of the given table.

Table "%", parameter "%" has no sourceparameter in "%" source tableSource: TAM

Explanation: Cannot find the field in the sourcetable that corresponds to the givenparameter.

Action: Use a different source field for the givenparameter, and make the appropriate changein the definition of the given table.

Table "%" and its fields excluded -selection removedSource: Report Generator

Explanation: The source data table and its fieldshave been excluded. Since some of its fieldsare referenced in the selection criteria, theselection criteria were also removed.

Action: No action required.

Table "%" and its fields excludedSource: Report Generator

Explanation: The source data table and its fieldshave been excluded at your request.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 435: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 421

Table "%" can only be BROWSEDSource: Table Editor

Explanation: Some types of tables may only bebrowsed, for example tables of type PRM.You have attempted to edit one of these typesof tables.

Action: Use the Table Browser on the table.

Table "%" cannot be referred to morethan onceSource: Security

Explanation: You referred to a particular tablemore than once while specifying tablepermissions for an object set definition. Sincethe table is not parameterized, the entryrefers to the whole table and thus only oneentry is allowed.

NOTE: You can refer to a parameterizedtable more than once, but you must specifyeither the instance involved for each entry, orrefer to the whole table.

Action: Remove duplicate entries from the list byreplacing the table name with blanks, nulls,or another table name.

Table "%" contains data; cannot changetype from "%" to "%"Source: Promotion

Explanation: Because the specified table containsdata on the target system but the source tabletype does not match the target type, theapply process cannot proceed as requested.

Action: If the target type is TDS: 1) Unaccept thechange and return it to the developer on thesource system. 2) The developer should rollback the change request and make the tablecompatible with the target system. 3) Submita change to delete the data from the table. 4)

Submit a change to modify the table type. Ifthe target type is SES or EES, either restart thesession or EE to clear the table, or explicitlyclear the table before re-applying the change.

Table "%" copied into table "%"Source: Table Editor

Explanation: The contents of the source tablehave been copied into the destination table.

Action: No action required.

Table "%" could not previously beboundSource: TAM

Explanation: No bound data occurred for thetable in the fixed storage; therefore, the datacould not be found and used.

Action: No action required.

Table "%" does not exist or has nolocation parmSource: Promotion

Explanation: In order to remotely apply a changethat involves table data, the table in questionmust have a location parameter.

Action: Ask your Promotion Administrator tounaccept your change by selecting U, thenroll it back and add a location parameter tothe specified table and submit your changeagain.

TIBCO Object Service Broker Messages Without Identifiers

Page 436: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

422 |

Table "%" does not existSource: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The table is notdefined or $FORMATROW was called beforethe access to the table in the transaction.

Action: Contact TIBCO Support.

Table "%" does not existSource: Report Generator

Explanation: The indicated data table does notexist. A data table must be created before youcan use it to generate a report.

Action: Remove the indicated table.

Table "%" does not existSource: Security

Explanation: You referred to a non-existent table.

Action: Remove the entry or correct it.

Table "%" has already been specifiedSource: Report Generator

Explanation: You specified the indicated sourcedata table more than once.

Action: Remove one of the duplicate source datatables from the input area.

Table "%" has invalid or non-existentsource table "%"Source: TAM

Explanation: The source table cannot be found.

Action: Check the definition of the table and seeif it uses a valid source table.

Table "%" has no fieldsSource: Interpreter

Explanation: Internal error. The definition of thetable has been altered.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Use only the Table Definer to modify tabledefinitions.

Table "%" is emptySource: Table Editor

Explanation: This message confirms that theindicated table is empty.

Action: No action required.

Table "%" is not a metadata IMS table.Source: Table Definer

Explanation: The table specified in the COPYcommand is not a MetaStor IMS table. Youcannot copy the definitions of other types oftables into a MetaStor IMS table.

Action: You can execute the COPY commandagain, and provide a valid MetaStor IMStable as the source table.

Table "%" is NOT a PARAMETERIZEDtableSource: Security

Explanation: You requested the PARMS functionfor a non-parameterized table in the tablepermissions screen of an object set definition.

Action: No action is required.

TIBCO Object Service Broker Messages Without Identifiers

Page 437: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 423

Table "%" is not a report table of report"%"Source: Report Server

Explanation: The application is attempting toINSERT into a report table that is neither abody nor a fixed report table. Either thewrong report name was specified, or thename of the report table was misspelled.

Action: Use the Report Definer to determine andspecify the correct name.

Table "%" is not definedSource: Debugger Utility

Explanation: You have tried to list (or set) a fieldof an undefined table.

Action: Verify the spelling of the table to be listed(or set).

Table "%" is not one of the data tables inthe preceding rowsSource: Report Generator

Explanation: You can only relate a source datatable to another source table that precedes it.

Action: Choose another table to relate to.

Table "%" is not related to a precedingtableSource: Report Generator

Explanation: The indicated table is not related toany other source data tables. Each table(except the first one) must be related toanother source data table.

Action: Relate a field of the indicated table to apreceding data table.

Table "%" is undefinedSource: Interpreter

Explanation: A table access was attempted on atable which is not defined.

Action: Verify the spelling of the table name ordefine the table.

Table "%" must be of type "%"Source: Table Definer

Explanation: Specify the table type indicated inthe message.

Action: An invalid table type was entered. Tabletype must be the same as the one indicated inthe message.

Table "%" needs % data parameter(s)and % location parameterSource: Table Editor

Explanation: You tried to edit or browse anothertable using the EDIT or BROWSE commandbut you specified the wrong number ofparameters.

Action: Supply the right number of parameter(s).

Table "%" no longer existsSource: Promotions Bind Tools

Explanation: The specified table was previouslybound but no longer exists.

Action: No action required.

Table "%" not foundSource: Print Rules

Explanation: A table that you specified forindirect calls does not exist.

Action: Correct the table name.

TIBCO Object Service Broker Messages Without Identifiers

Page 438: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

424 |

Table "%" NOT foundSource: Table Editor

Explanation: The specified table cannot befound.

Action: Check the table name and existence ofthe specified table.

Table "%" not in virtual Screen "%"Source: Screen Server

Explanation: The rule has attempted to insert,delete or replace an occurrence from a screentable. This screen table has been specifiedwith the wrong screen as its parameter.

Action: Do one of the following:

• Specify a screen which already containsthe desired screen table as the parameter tothe screen table in the rule.

• Using the Screen Table Painter, add thedesired screen table to the screen.

Table "%" not printed because a PRMtable was not foundSource: Print Definition

Explanation: You are trying to print an object anda table which stores part of the object'sdefinition. A PRM table for that table isrequired.

Action: Define a PRM table for that table and trythe operation again.

Table "%" not printedSource: Print Definition

Explanation: You are trying to print an object anda table which stores part of the object'sdefinition is not printed.

Action: Read the message log and find out thereason why the table is not printed.

Table "%" of type "%" is not allowedSource: Report Generator

Explanation: You cannot use the indicated typeof table as a source data table for generating areport.

Action: Choose any type of table except one ofthe following:

• Export table (EXP)

• Report table (RPT)

• Screen table (SCR)

• Temporary table (TEM).

Table "%" of VSAM % "%" not open forupdateSource: TAM

Explanation: You requested a REPLACE orDELETE operation, but the VSAM data set isnot open for update. The variables, from leftto right, are as follows:

1. The name of the table

2. Either "file" or "DDNAME"

3. The name of the file or the DDNAME

Action: Ensure that the table definition for thistable specifies Y in the UPDATE field and Nin the LOAD field.

TIBCO Object Service Broker Messages Without Identifiers

Page 439: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 425

Table "%" printedSource: Print Definition

Explanation: You are trying to print an object anda table which stores part of the object'sdefinition is printed.

Action: No action required.

Table "%" PRINTEDSource: Table Editor

Explanation: The specified table was printed as aresult of the PRINT command.

Action: No action required.

Table "%" requires % parameter(s)Source: Table Editor

Explanation: The message indicates how manyparameters the table has been defined with.You have attempted to supply a differentnumber of parameters.

Action: Do one of the following:

• Add or remove parameters as required

• Do not specify any parameters so that youcan have the Table Browser/Editorprompt for them.

Table "%" requires % parameter(s)Source: Batch Control Card

Explanation: The number of parameters yousupplied in the selection string for theindicated table does not match the actualnumber of parameters for the table.

Action: Check the parameter list from the tabledefinition and change the selection stringaccordingly.

Table % already exists; choose anothernameSource: Promotion

Explanation: To run GEN_SYS_TBLS, you mustprovide a table name for the system to createa table. If a table with the specified namealready exists, this message appears.

Action: Use a different table name.

Table % cannot be moved due tominimal table definitionSource: Table Editor

Explanation: MOVTAB failed. Requested table tobe moved is a minimal table definition.Segment# of the table is not changed.

Action: No action required. Refer to theShareable Tools manual for more informationon MOVTAB.

Table % clearedSource: Table Editor

Explanation: Some or all occurrences of thespecified table have been deleted asrequested.

Action: No action required.

Table % does not exist or is of type"OBJ" or "EXP"Source: Print Table

Explanation: Rule object code (OBJ) and export(EXP) tables are not printed.

Action: Verify your choice of table.

TIBCO Object Service Broker Messages Without Identifiers

Page 440: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

426 |

Table % does not existSource: Host Language Interface

Explanation: The indicated table does not exist.

Action: Check the name of the table; define thetable if it is not defined.

Table % does not existSource: Print Table

Explanation: The table specified does not exist.

Action: Check your command for typing errors.

Table % does not have a field called %Source: Print Table

Explanation: The specified field is not a field ofthe table.

Action: Correct the field name.

Table % does not have a field named %Source: Host Language Interface

Explanation: The indicated table does not have afield with the indicated name.

Action: Correct the field name.

Table % does not have a parameternamed %Source: Host Language Interface

Explanation: The indicated table does not have aparameter with the indicated name.

Action: Correct the parameter name or the tablename.

Table % has a SIX that is incompatiblewith the backup; delete SIX beforeBackoutSource: Promotion

Explanation: One of the secondary index fields ofthis table does not exist in the backup file.

Action: Remove the secondary index beforeproceeding with the Backout.

Table % has already been definedunder Serverid %Source: Table Definer

Explanation: The specified defined table hasalready been mapped to another Serveridunder the same external DBMS.

Action: Enter a Serverid that is not in use.

Table % has already been unloadedSource: Unload/Load

Explanation: You entered the table name morethan once in the selection screen. You cannotunload a table more than once.

Action: No action required.

Table % has more than 4 parameters; Nooccurrences unloadedSource: Unload/Load

Explanation: A table cannot have more than fourparameters. No occurrences are unloaded.

Action: Correct the definition of the source table.

TIBCO Object Service Broker Messages Without Identifiers

Page 441: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 427

Table % has no primary key; No %loadedSource: Unload/Load

Explanation: No primary key exists in the tableyou are loading.

Action: Check the definition of the table anddesignate a primary key.

Table % is already definedSource: Host Language Interface

Explanation: A definition has already beengenerated for the indicated table.

Action: Put the DECLARE TABLE commandbefore any other commands, such asDECLARE CURSOR, which cause thedefinition to appear automatically.

Table % is emptySource: Character-based Text Editor

Explanation: You specified an empty source texttable with the COPY command.

Action: No action required.

Table % is not a TDS table; No % loadedSource: Unload/Load

Explanation: You can only load occurrences of aTDS-type table.

Action: No action required.

Table % is not a text tableSource: Character-based Text Editor

Explanation: TED was called with an input tablethat does not have the fields required to holdtext.

Action: Call TED with a table that meets thespecifications for text. Refer to the ShareableTools manual for information about definingthe table.

Table % is not an entry in TABLESSource: Unload/Load

Explanation: The requested table cannot befound in the system. This message appears inthe user log.

Action: Ensure that a table by that name existsand unload the table again.

Table % is not defined in this programSource: Host Language Interface

Explanation: The indicated table is not defined inthis program.

Action: Define the table either by using DEFINETABLE or by declaring a cursor on the table.

Table % is undefinedSource: HLIPREPROCESSOR

Explanation: The indicated table is not defined inthe Object Service Broker database, or wasnot defined in a DEFINE TABLE statement.

Action: Make sure the DEFINE TABLE statementspecifies a table that is already defined toObject Service Broker.

TIBCO Object Service Broker Messages Without Identifiers

Page 442: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

428 |

Table % moved to segment %Source: Table Editor

Explanation: Your request to move the table tothe specified segment was successful.

Action: No action required.

Table % must appear in the join before%Source: Print Table

Explanation: The table used for the matchingfield does not previously appear in the join.

Action: Add the table to the join. If it is already inthe join, try changing the order of the tablesin the join.

Table % NOT clearedSource: Table Editor

Explanation: The request to clear the indicatedtable is canceled.

Action: No action required.

Table % not supported in % since field% has syntax F 16Source: HLIPREPROCESSOR

Explanation: A field of the table has syntax F(floating point) length 16, which is notsupported in COBOL.

Action: Change the definition of the table or useanother table.

Table % of % cannot be included in apromotion requestSource: Promotion

Explanation: This table cannot be promotedthrough the promotion system because:

• It is used by the promotion system

• The table contains data that is specific tothe system, such as valid userids orborrowing rights.

• The table contains data that is shared bysystems, such as @SCHEDULEMODEL.

The first % is OCCURRENCES orDEFINITION. The second % is the tablename.

Action: If you want to promote the table anyway,contact TIBCO Support.

Table % or % may not exist or be ascreen and screen tableSource: Character-based Text Editor

Explanation: GEN_TED was called withparameters that are not the names of a screenand a screen table.

Action: Correct the call to GEN_TED.

Table % requires % parameter(s)Source: Print Table

Explanation: A table was specified with theincorrect number of parameters.

Action: Correct the parameter list.

Table % requires % parametersSource: Character-based Text Editor

Explanation: You entered the incorrect numberof parameters for a table.

Action: Correct the parameter list.

TIBCO Object Service Broker Messages Without Identifiers

Page 443: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 429

Table % requires % parametersSource: Host Language Interface

Explanation: The indicated table requires thegiven number of parameters to be specifiedexplicitly.

Action: Put the required parameter specificationright after the table name.

Table % will not be boundSource: Table Editor

Explanation: Either your request to reset the bindon the table was successful, or you attemptedto bind something other than the tabledefinition or data.

Action: If your request was successful, no actionis required. If you attempted to bindsomething other than the table definition ordata, try again and specify either thedefinition or data.

Table %Source: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log.

Action: Study the Information Log.

Table '%' deletedSource: Delete Definition

Explanation: Inform the user that the specifiedtable has been deleted.

Action: No action required.

Table '%' does not existSource: Delete Definition

Explanation: You are trying to delete a table butthe table does not exist.

Action: Check and see whether the table reallyexists.

Table @PROMUNBOUNDOBJScontains data; run @PROMBINDOBJSSource: Promotions Bind Tools

Explanation: Objects have been unbound withthe @PROMUNBINDOBJS tool and have notall been successfully rebound using the@PROMBINDOBJS tool.

Action: Run the @PROMBINDOBJS tool torestore the bind information beforeattempting to unbind objects again.

Table access error detected whenloading the definition of table "%"Source: Interpreter

Explanation: Internal error. The definition of thetable has been altered.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Use only the Table Definer to modify tabledefinitions.

TIBCO Object Service Broker Messages Without Identifiers

Page 444: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

430 |

Table access errorSource: Interpreter

Explanation: This message generally introducesmore specific messages that describe theerror encountered.

Action: Read the messages that follow in theInformation Log.

Table contains data; modifications arerestrictedSource: Table Definer

Explanation: The specified table contains data.Modifications of the table definition arerestricted to the unprotected fields. Note thatthe length of the fields can only be increased,not decreased.

Action: No action required.

Table definer for % type tbl notavailableSource: Table Definer

Explanation: The Table Definer tool cannot beused for the table type specified in theparticular presentation environment.

Action: Press <PF1> for a listing of table typesaccessible from the Table Definer.

Table definition at location "%" has "%"which are incompatible with definitionat this locationSource: TAM

Explanation: A distributed transactionencountered a table definition at the namedlocation which was incompatible with thedefinition at this location. Definitions do nothave to be identical on both systems, butPARMS, FIELDS, ORDERING, SELECTION,and CODEPAGE must match.

Action: Determine which definition item isincompatible and use the Table Definer tocorrect it.

Table definition at this location has noLOCATION parm; % can not beaccessed remotelySource: TAM

Explanation: A distributed transactionencountered a table definition that did nothave a location parameter at the remoteObject Service Broker system. A tablewithout a location parameter cannot beaccessed remotely.

Action: Use the Table Definer on the remotesystem to add an appropriate locationparameter. Note that this may not be anerror; the remote system's administrator mayhave chosen to make a table accessible fromthat system only, by not defining a locationparameter.

Table definition changes cancelledSource: Table Definer

Explanation: Changes to the table definitionwere canceled at your request when youpressed <PF12> to cancel.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 445: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 431

Table definition could not be boundfrom location "%"Source: TAM

Explanation: A table's definition implied that itwas to be obtained from another location.However, the definition was invalid or themessage failed. In either case, subsequentmessage log text will specify the reason.

Action: Preceding messages will identify theerror in the definition or the distributedmessage.

Table definition does not have a fieldnumber %Source: Builtin Routines

Explanation: Formatting of a table buffer by$FORMATROW failed. The table does nothave an i-th field. The format string does notmatch the definition of the table.

Action: Contact TIBCO Support.

Table definition invalid for EES table"%"Source: TAM

Explanation: The EES table definition does notcontian the correct defintions for mandatoryfields @@UPDATE_COUNT and@@REF_COUNT.

Action: Correct the definition of this EES table.

Table definition was not bound fromthis locationSource: TAM

Explanation: A local transaction attempted touse an incompatible definition which waspreviously obtained from another location.Prior messages will have detailed theincompatibility.

Action: Revise one or both table definitions usingthe Table Definer.

Table is not of type TDS; Nooccurrences unloadedSource: Unload/Load

Explanation: Only occurrences of a TDS table canbe unloaded.

Action: Check the type of the table that you wantto unload.

Table name "%" is too long.Source: Parse

Explanation: No table name has more than 16characters.

Action: Correct the table name.

Table name can only be given for tableaccess exceptionsSource: Rule Editor

Explanation: Only table access exceptions (suchas GETFAIL, INSERTFAIL, etc.) may have anassociated table name. For example ONGETFAIL TABLE is permissible, but ONCONVERSION TABLE and ONMY_EXCEPTION TABLE are not.

Action: Remove the associated table name.

TIBCO Object Service Broker Messages Without Identifiers

Page 446: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

432 |

Table name requiredSource: Table Editor

Explanation: You did not enter the table namewhen using either the Table Browser/Editor,or the Single Occurrence Editor.

Action: Supply the table name.

Table NOT printed; database integrityerrorSource: Table Definer

Explanation: The definition of the table is notprinted because of an integrity error.

Action: Do the following:

1. Try printing the table definition againlater. If it still does not work, try printinganother table definition.

2. Report the results to the SystemAdministrator. The Administrator cancheck your security clearance and theintegrity of the database.

3. If the problem is not resolved, contactTIBCO Support.

Table or table instance for BIND table"%" exceeds system instance bind limitSource: TAM

Explanation: The total occurrence for a boundtable has exceeded the system limit. Thismessage appears in the system log to providemore information about bound table storagewhen there is a transaction failure.

Action: No action required.

Table parameter "%" has not beenspecifiedSource: HLIPREPROCESSOR

Explanation: The indicated table parameter wasnot specified.

Action: Specify the parameter correctly.

Table parameter cannot be repeated inthe WHERE clauseSource: HLIPREPROCESSOR

Explanation: A table parameter appears bothinside parentheses after the table name andin the WHERE clause.

Action: Correct the access statement so that theparameter is specified only once.

Table type changedSource: Table Definer

Explanation: You changed the table type. Youmay see a different screen which displays theattributes of the new type of table.

Action: No action required.

Table type code must be N or PSource: Table Definer

Explanation: The table type code must be N forregular DB2 table definitions or P for storedprocedure definitions. After saving a storedprocedure definition you can create resultsets table by pressing PF9. The table typecode for these tables are tagged with an R.

Action: Enter an N or a P

TIBCO Object Service Broker Messages Without Identifiers

Page 447: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 433

Tables % and % are not the sameSource: Host Language Interface

Explanation: More than one table name appearsin this command.

Action: Only one table is supported; therefore, alltable names must be the same.

Tables are identicalSource: Definition Differences

Explanation: The two tables named forcomparison are the same.

Action: Compare data in two different tables.

Tables permissions for object set willbe committed on SAVESource: Security

Explanation: You saved changes to tablespermissions for an object set definition.These changes are committed if the object setdefinition is saved, or ignored if the object setdefinition is canceled.

Action: No action required.

Tables whose segment number was notpreservedSource: Unload/Load

Explanation: The definition of the loaded tablehas been changed so it is on a differentsegment than before.

Action: No action required.

Tally of object LOADEDSource: Unload/Load

Explanation: Title for the tally showing thenumber of each type of object loaded.

Action: No action required.

TAM selection string not found in theconstants tableSource: Rule Editor

Explanation: Internal editor error.

The message log will contain a more detailederror message.

Action:

1. Push <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

Task completedSource: Keyword Manager

Explanation: The chosen action has beencompleted.

Action: No action required.

Task failedSource: Keyword Manager

Explanation: The chosen action has failed.

Action: Press <PF2> to view the traceback, if any.

TIBCO Object Service Broker Messages Without Identifiers

Page 448: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

434 |

Task stoppedSource: Keyword Manager

Explanation: You pressed <PF12> to cancel someprocessing.

Action: Choose any action from the menu.

TDS CTABLE missing DTABLE fieldSource: TDS

Explanation: The DB2 table is definedincorrectly. An entry in the Object ServiceBroker table FIELDS is missing.

Action: Check the DB2 table definition.

TDS CTABLE missing ITABLE fieldSource: TDS

Explanation: The IMS table is defined incorrectly.

Action: Check the IMS table definition.

TDS field "%" in table "%" has invalidlengthSource: TAM

Explanation: The reported field holds data with alength that differs from its definition. Thedefinition of the length of this field waschanged after data was entered.

Action: Correct the field length in the tabledefinition to match the data occurrencelength.

TDS LOCK LIST SCREEN DISPLAYERROR DETECTEDSource: S6BTLADM - INDOUBT TRX

Explanation: When attempting to display the listof logical locks an undetermined error wasdetected.

Action: Retry your request. If the problempersists contact TIBCO Support.

TDS LOCK RETRIEVAL ERRORDETECTEDSource: S6BTLADM - INDOUBT TRX

Explanation: An error was detected whenattempting to issue the logical TDS lockrequest to the Data Object Broker.

Action: Review the job log to determine if therewere additional messages which may helpidentify the cause of the problem. Retry yourrequest. If the problem persists contactTIBCO Support.

TDS occurrence in table "%" is missingfieldsSource: TAM

Explanation: A TDS error has occurred or atable's definition has been corrupted.

Action: Do the following:

1. Press <PF2> and print the message log (ifany).

2. Print the Data Object Broker logs.

3. Contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 449: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 435

TDS occurrence length error in table"%"Source: TAM

Explanation: A TDS occurrence that containsmore fields than are defined was retrieved.

Action: If fields were deleted from the definition,replace them. If this is not the case, contactTIBCO Support.

TDS Table % is not defined; No %loadedSource: Unload/Load

Explanation: You tried to load only theoccurrences of a table, but the table is notdefined in the target system.

Action: Define the table and load theoccurrences, or load both the table definitionand occurrences.

TDS UPDATE INTENT LISTRETRIEVAL ERRORSource: S6BTLADM - INDOUBT TRX

Explanation: When attempting to send yourrequest to retrieve the pending update list tothe Data Object Broker, an error wasdetected.

Action: Review the joblog to determine if thereare additional messages which may helpidentify the cause of the problem. Retry yourrequest. If the problem persists contactTIBCO Support.

Terminal I/O error during DISPLAYprocessingSource: Builtin Routines

Explanation: An I/O error occurred whileattempting to write to or read from aterminal as a result of a call to ETDISP.

Action: Contact the installation's hardwaresupport.

Terminal I/O error during DISPLAYprocessingSource: Screen Server

Explanation: A terminal I/O error occurredduring the Object Service Broker DISPLAYoperation.

Action: Notify the installation's hardwaresupport.

Text % savedSource: Character-based Text Editor

Explanation: The text specified has been saved asa result of pressing <PF3>.

Action: No action required.

Text printedSource: Character-based Text Editor

Explanation: The unformatted text has beenprinted as a result of pressing <PF13>.

Action: No action required.

The % clause is too long to saveSource: Rule Editor

Explanation: An ORDERED or WHERE clausecontains too many terms.

Action: Reduce the number of terms.

TIBCO Object Service Broker Messages Without Identifiers

Page 450: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

436 |

The % entered for % "%" is not validSource: Copy Definition

Explanation: You specified an invalid LIBRARYfor a rule object.

Action: Specify a valid identifier to allow theoperation to be completed.

The % entered for % "%" is not validSource: Copy Defn/Data

Explanation: You specified information about anobject that is invalid.

Action: Correct the invalid information.

The % must be specifiedSource: Field Dictionary

Explanation: One of the following required fieldswas not specified in the field definition:

• USE

• SYNTAX

• LENGTH

Action: Supply a value for the indicatedattribute.

The accumulator for report function"%" overflowedSource: Report Server

Explanation: An accumulator for thecomputation of a report function overflowedwhen the report function was evaluated.

Action: Validate whether or not the Of-Fieldvalues of the report function are withinreasonable ranges. If the validation does notsolve the problem, use the syntax FLOAT forthe Of-Field.

The command "%" failed. Data segmentis unavailable.Source: Table Definer

Explanation: The indicated request failed due tothe data segment being offline.

Action: Bring the data segment online beforeproceeding with the request.

THE CURRENT SCHEDULE NAME ISEITHER INVALID OR NOTSUPPLIEDSource: S6BTLADM-Resource Management

Explanation: A schedule name or target wasentered on the input which contains invalidcharacters or identifies a schedule that doesnot exist.

Action: Correct the input and retry.

The cursor must be on a table to bedeleted from the joinSource: Print Table

Explanation: The cursor was not placed on anytable when <PF22> was pressed.

Action: Put the cursor on the table to be excludedfrom the join, and press <PF22> again.

The Data Object Broker is not acceptingany logons at this timeSource: External Gateway Logon

Explanation: The Data Object Broker is not readyto accept new connections.

Action: Check on the status of the Data ObjectBroker and resubmit the session when theenvironment is ready.

TIBCO Object Service Broker Messages Without Identifiers

Page 451: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 437

The Data Object Broker is quiescing, nonew logons allowedSource: External Gateway Logon

Explanation: The Data Object Broker is in theprocess of normal termination.

Action: Resubmit the session when the DataObject Broker is available.

The DB2 catalog definition is notavailable. Metastor definition shownSource: Table Definer

Explanation: The DB2 Gateway for the Server IDspecified is not available. The currentMetastor definition is displayed. Seedocumentation for instructions on setting upa local side catalog.

Action: Start a DB2 Gateway with the desiredServer ID.

The defined table has % parms; Thetable loaded has %Source: Unload/Load

Explanation: The number of parameters in thesource table is not the same as the number inthe target table.

Action: Check the definition of both the sourceand target tables to ensure that thedefinitions of the parameters are the same.

The definition of file "%" in group "%"has been changedSource: Table Definer

Explanation: The definition of the indicated fileon the Model 204 system did not match theone in the MetaStor. This is caused by achange in the Model 204 file definition on theModel 204 system.

Action: Redefine the table, if necessary.

The definition of table "%" (Server "%")has been changedSource: Table Definer

Explanation: The definition of the indicated tablein the MetaStor does not match the one in theDB2 system which corresponds to theindicated gateway. This is caused by achange in the DB2 table definition on the DB2system.

Action: Redefine the table, if necessary.

The field % must be marked as aprimary keySource: CA Datacom Table Definer

Explanation: You have not marked one of theCA-Datacom key fields as a Primary Key forthe Object Service Broker table. All the CA-Datacom key fields must appear in the ObjectService Broker DAT Table Definition key,either as simple fields or as group fields, butnot both.

Action: You must mark the indicated field as aprimary key or include the CA-Datacom keydata another way.

TIBCO Object Service Broker Messages Without Identifiers

Page 452: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

438 |

THE GROUP INPUT (group) FORDETAIL DISPLAY IS NOT DEFINED,RETRYSource: S6BTLADM-Resource Management

Explanation: You keyed an invalid group nameinto the input group field and requested adetail display; the group does not exist in theData Object Broker repository.

Action: To add the group press <PF5>; ifattempting to display an existing grouprekey the group name or identify it by cursorposition.

THE GROUP MUST BE IDENTIFIEDIN ORDER TO DISPLAY RESOURCEDETAILSSource: S6BTLADM-Resource Management

Explanation: You have requested the display ofthe details for a specific resource but thesystem could not determine which resourceyou wished to review.

Action: Key in the group name on the input fieldor identify the group via cursor position andretry your request.

THE GROUP MUST BE IDENTIFIEDTO ISSUE A STOP, PLEASE INPUTOR SELECT GROUPSource: S6BTLADM-Resource Management

Explanation: You have requested the issue of astop for all paths within a specific group butthe system is not able to identify the groupyou wish to stop.

Action: Either type the desired group name in theinput field or position the cursor on thedesired group and retry your request.

The M204 file/group "%" does not exist.Source: Table Definer

Explanation: The indicated file or group does notexist in the MetaStor.

Action: Do one of the following:

• Enter another name

• Press <PF4> to select a file or group

• Import the required file or group into theMetaStor before defining the table.

The maximum number of allowedselections is %Source: Select Data

Explanation: You are only allowed to select up tothe indicated number of entries.

Action: "Blank out" some selections so that thetotal number of selections does not exceedthe indicated maximum.

The name "%" is referred to more thanonceSource: Object Set Definer

Explanation: The indicated name appears morethan once for the object type shown.

Action: Remove the duplicate entries.

The name "%" is too long; maximum is% charactersSource: Global Cross Ref. Search

Explanation: A name entered on the Searchscreen has exceeded the given number ofcharacters.

Action: Correct the name.

TIBCO Object Service Broker Messages Without Identifiers

Page 453: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 439

The name % is invalid for adynamically created tableSource: TAM

Explanation: The table name specified [email protected] is already in use by anObject Service Broker system table.

Action: Choose another name.

The NEW owner must be different thanthe CURRENT ownerSource: Security

Explanation: In the Transfer Ownership screen,you specified that the new owner is the sameas the current owner, meaning that notransfer is to take place.

Action: Either cancel the Transfer Ownershipfunction, or supply a new owner that isdifferent from the current owner. A list ofnew owners is available to select from byusing the appropriate function key.

The number of OCCURS/READ mustbe in the range 1 - 100Source: Adabas Definer

Explanation: The number you specified for fieldOCCURS/READ is out of range.

Action: Specify a number for fieldOCCURS/READ that is greater than or equalto 1 and less than or equal to 100.

The number of OCCURS/READ to beread in each ADABAS call must bespecifiedSource: Adabas Definer

Explanation: Field OCCURS/READ requires avalue. This field specifies the number ofoccurs of a periodic group or multiple valuefield to be accessed in each call to ADABAS.

Action: Specify the number of occurs of aperiodic group or multiple value field to beaccessed. It is suggested that this value be setto the average number of occurs for thisperiodic group or multiple field so that in90% of reads all occurs are read by one call toADABAS.

The number of primary keys cannotexceed 16Source: General Table Definer

Explanation: The number of primary keys thatyou have specified in your MetaStor tabledefinition exceeds the maximum number of16 primary keys.

Action: You must make some of the keys non-primary.

The object "%" does not exist in % "%"Source: Copy Definition

Explanation: The object does not exist in alocation or library.

Action: Reenter object or location (destinationlocation, library, or environment).

TIBCO Object Service Broker Messages Without Identifiers

Page 454: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

440 |

The object "%" is deleted from 'list1'Source: Definition Differences

Explanation: You are trying to delete an objectfrom list 1 and the object is deleted.

Action: No action required.

The object % does not exist in % "%"Source: Copy Defn/Data

Explanation: You have specified a nonexistentobject.

Action: Remove or correct the specification.

The object name "%" is not a valid nameSource: Copy Definition

Explanation: The specified object name is not avalid name.

Action: Retype the name correctly.

The operating system denied (S0C4)access to memory for MAP table %Source: TAM

Explanation: During a read or write to an area ofmain storage by a MAP table, the operatingsystem detected an invalid storage address,and terminated the access with a 0C4 abend.Object Service Broker recovers from thissituation and raises the DATAREFERENCEexception. A partial data transfer may haveoccurred, and consistency is not guaranteed.

Action: Investigate why the address beingaccessed is invalid. It may be necessary toregister the storage area to be accessed usingthe @MAP tool.

The operation % failed: %Source: Manage Promotion Rights

Explanation: You are trying to do one of thefollowing operations: OBTAIN all rights,RELEASE all rights, and TRANSFER allrights. The operation fails.

Action: Refer to the reason given in the errormessage and correct the problem.

The print default parameters table isemptySource: Print Definition

Explanation: The table @PRINTDEFAULTS isempty. This table is used to store the defaultparameters of printing, e.g., page length,page width, etc.

Action: Update the default parameters table andtry the operation again.

The report is too big to fit in themessage logSource: Secure Audit Log

Explanation: You attempted to print a report tothe message log but the report with thecurrent date range was too large to fit into themessage log.

Action: Try sending the report to either theprinter or a file. To see the part of the reportthat was sent to the message log press <PF2>twice.

TIBCO Object Service Broker Messages Without Identifiers

Page 455: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 441

THE REQUEST TO STOP ALLRESOURCES OF TYPE = type HASBEEN ISSUEDSource: S6BTLADM-Resource Management

Explanation: Your confirmed stop request hasbeen issued to the Data Object Broker.

Action: No action required.

The result of an exponential was animaginary numberSource: Interpreter

Explanation: An exponential number had to beevaluated with floating-point arithmetic. Ifthe base number is negative, the result isassumed to be an imaginary number.

Action: Ensure that the base is not negative.

The rule Debugger must be set upbefore using %Source: Builtin Routines

Explanation: Internal error.

Action: Contact TIBCO Support.

The same PF key cannot be assigned todifferent functionsSource: Screen Definer

Explanation: In the Screen Definer, you assignedthe same PF key to more than one standardfunction.

Action: Change the assignments so that each PFkey is assigned to only one standardfunction.

THE SCHEDULE HAS BEENUPDATED SUCCESSFULLYSource: S6BTLADM-Resource Management

Explanation: This message is to acknowledgethat the updates have been applied to therepository as your requested.

Action: No action.

The source definition for a literal mustbe enclosed in quotesSource: Report Definer

Explanation: The text that defines the source fora literal report field must be enclosed insingle quotation marks.

Action: Enter single quotation marks around thetext you have entered as the source for thisliteral.

The specified rule name is the same as asystem routine: name "%"Source: Rule Editor

Explanation: You have tried to give a rule thesame name as a system routine (which is notwritten with rules).

Action: Choose a different name for the rule.

THE STOP SERVER REQUEST HASBEEN ISSUEDSource: S6BTLADM-Resource Management

Explanation: This message acknowledges thatthe stop server request has been issued to theData Object Broker.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 456: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

442 |

The sum of primary key LENGTHScannot exceed 127Source: General Table Definer

Explanation: The sum of the primary key lengthsthat you have specified exceeds themaximum allowed of 127.

Action: You must respecify the primary keyfield(s) so that the sum of their lengths do notexceed 127.

The total of all TITLE and HEADINGrows must not exceed %Source: Report Definer

Explanation: The total number of title andheading rows defined for a report tableexceeds the maximum given in the message.

Action: Change the specified title/heading rowsso that their sum does not exceed themaximum.

The type and syntax are not compatibleSource: Table Definer

Explanation: The defined MetaStor semantictype and syntax are not compatible.

Action: See the Managing Data manual for thepossible combinations of field syntax andsemantic types.

The version parameter is required forobjects of type '%'Source: Delete Definition

Explanation: You are trying to delete an objectbut the version of that object is not specified.

Action: Enter the version of the specified objectand retry the operation again.

There are % host variables but cursorhas % fieldsSource: Host Language Interface

Explanation: This query specifies the givennumber of host variables, but the cursordeclaration specifies a different number offields.

Action: Make the query and cursor declarationagree on the number of host variables andfields.

THERE ARE CURRENTLY NORESOURCE GROUPS DEFINEDUNDER TYPE typeSource: S6BTLADM-Resource Management

Explanation: When the system was attempting toretrieve the groups under the specified type,there were no groups available.

Action: Redisplay the Type List screen (PF4) andtry your request again.

There are more fields than valuesSource: Host Language Interface

Explanation: This command names more fieldsthan it gives values.

Action: Make the numbers of fields and valuesagree.

There are more values than fieldsSource: Host Language Interface

Explanation: This command provides morevalues than fields.

Action: Make the number of values and fieldsagree.

TIBCO Object Service Broker Messages Without Identifiers

Page 457: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 443

There are no % to promoteSource: Promotion

Explanation: You have selected an object type forwhich you do not have any objects withpromotion rights.

Action: Select some other object type.

THERE ARE NO ACTIVE PATHS TOBE DISPLAYED, REQUEST IGNOREDSource: S6BTLADM-Resource Management

Explanation: From the Resource Detail screenyou pressed <Enter> to display the activepath list; at present there are no paths active.

Action: No action required.

THERE ARE NO ACTIVE SESSIONSFROM REGION =Source: S6BTLADM - USER ACTIVITY

Explanation: You have requested the activesessions which have been grouped under theidentified region name. There are currentlyno connections to report.

Action: Retry your request.

There are no ENABLED object setswhich include this objectSource: Security

Explanation: You requested to view EnabledObject Sets from an object permissions list tosee if any enabled object set includes thisobject.

Action: No action is required.

There are no fields definedSource: CA Datacom Table Definer

Explanation: You requested the FIELDS functionto see the list of CA-Datacom fields in theCA-Datacom table you specified in theprevious context. There are no fields in theextraction tables.

Action: Call your database administrator todetermine why the extraction informationshows the presence of the CA-Datacom tablebut not its fields.

There are no GROUPS to LISTSource: Security

Explanation: You requested a list of Groups, butthere are no Groups to list.

Action: No action required.

There are NO instances currentlyselectedSource: Unload

Explanation: In INSTANCE SELECT you haverequested to unselect any currently selectedinstance; however, there are no currentlyselected instances.

Action: No action required.

There are no LIBRARIES to LISTSource: Security

Explanation: You requested a list of libraries, butnone exist. You may have made your requestfrom the main menu "Manage ObjectPermissions" section by pressing theOPTIONS function key when your cursorwas on the OBJECT field.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 458: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

444 |

There are NO object sets enabled forgroup "%"Source: Security

Explanation: You requested the OBJECTSETSfunction in the Manage Group screen, whichlists object sets enabled for the group. Thereare no enabled object sets that include thegroup on the enable list.

Action: No action is required.

There are no OBJECT SETS to LISTSource: Security

Explanation: You have requested a list of existingobject sets. There are no object sets defined.

Action: No action required.

There are no REPORTS to LISTSource: Security

Explanation: You requested a list of reports,either in the main menu through OPTIONS,or while specifying reports in an object setdefinition. However, there are no reports tolist.

Action: No action is required.

There are no SCREENS to LISTSource: Security

Explanation: You requested a list of screens, butthere are no screens to list.

Action: No action required.

There are no SECURITYADMINISTRATORS to LISTSource: Security

Explanation: You requested a list of SecurityAdministrators, but there are no SecurityAdministrators to list.

Action: No action required.

There are no USERS to LISTSource: Security

Explanation: You requested a list of users, butthere are no users to list.

Action: No action required.

There is no content available to PASTESource: Screen Definer

Explanation: You have pressed <PF17> to paste afield but there are no contents being held tobe pasted.

Action: Before issuing a PASTE command, copy aline or cut a field.

There is no cross-reference informationavailableSource: Screen Definer

Explanation: You requested a list of screensreferencing a screen table, but no cross-reference material is available.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 459: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 445

There is NO DATA in table "%"Source: Unload

Explanation: You have requested to specify datainstances for the table named on the cursorrow; however, there is no data in the table tounload.

Action: No action required.

There is no data in the Audit Log for thecurrent date rangeSource: Secure Audit Log

Explanation: You attempted to purge the auditlog contents but you specified a date rangewhich started and ended before the earliestdate recorded in the audit log.

Action: Check the date range to be purged andtry again.

There is no data in the Audit LogSource: Secure Audit Log

Explanation: The audit log does not contain anydata and therefore the utility has nothing todisplay.

Action: No action required.

There is no data to be purgedSource: Secure Audit Log

Explanation: At this time the accesslog onlycontains entries for the current date. There isno data that can be purged.

Action: No action required.

There is no occurrence in (identifying)table "%" for %Source: Definition Differences

Explanation: You have specified an object whichhas a corrupted definition. There is nooccurrence for that object in the identifyingtable (table which has object names as keyvalues.

Action: You cannot perform the requestedoperation on the corrupted object. See yourdatabase administrator for further assistance.

There is no such field as "%" in screentable "%"Source: Screen Definer

Explanation: You have referenced a field thatdoes not exist in the screen table named.

Action: Check your screen table definition andreference an existing field, or add the desiredfield in your definition.

There is no such object set as "%"Source: Security

Explanation: You have requested to ManagePermissions for, or Specify Permissions foran object set, in the Main Menu of theSecurity Manager. The object set named doesnot exist.

Action: You must enter the name of an existingobject set or press <PF2> to obtain a list ofexisting object sets for selection.

TIBCO Object Service Broker Messages Without Identifiers

Page 460: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

446 |

There is no such table as "%"Source: Screen Definer

Explanation: You have pressed <PF19> to loadand given a non-existent table name on theprompting screen.

Action: Provide an existing table name.

There is no such Userid as "%"Source: Security

Explanation: You referred to a non-existentuserid when you requested to view a useridprofile.

Action: You can request a list of users and selectfrom this list, or correct the entry.

There is no such USERID or GROUP as"%"Source: Security

Explanation: You referred to a non-existentmember when specifying a permissions listor default list.

Action: No action is required unless you have toremove the entry.

There must be a MENU to displaySource: Menu Definer

Explanation: When ACTION is M, the OBJ LISTOR MENU field requires the name of themenu to display.

Action: Enter the name of the menu.

There must be a RULE to execute or callSource: Menu Definer

Explanation: When ACTION is N or C, the RULEfield requires the name of a rule to execute orcall.

Action: Enter the name of the rule.

There must be an object list forpromptingSource: Menu Definer

Explanation: You have set the PROMPT to O, sothe object list to be displayed must be namedin OBJ LIST OR MENU.

Action: Enter the name of the menu in OBJ LISTOR MENU.

There must be at least 1 distributionpoint and 1 count fieldSource: Table Definer

Explanation: You did not specify a distributionpoint or a count field for the CLC table. Adistribution point must be a field of thesource table, and a count field must havesemantic type count (C), binary syntax (B), alength of 4, Src C, and Source Name COUNT.

Action: Specify one distribution point and onecount field.

These objects are differentSource: Definition Differences

Explanation: You want to compare two lists ofobjects to see if they are different. The resultis, they are different.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 461: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 447

This command needs a descriptionSource: DEFINE_OBJLIST Tool

Explanation: The highlighted command does nothave a description.

Action: Type in the description text for thecommand.

This command needs a ruleSource: DEFINE_OBJLIST Tool

Explanation: The highlighted command does nothave a rule associated with it.

Action: Specify the rule to be executed when thecommand is invoked.

This document has been printedSource: Character-based Text Editor

Explanation: <PF13> was pressed and theformatted text was printed.

Action: No action required.

This field cannot have a negative valueSource: Screen Definer

Explanation: You have entered a negative valueinto a field requiring a positive value.

Action: Change the field to have a positive value.

This field is missing a valueSource: Object Selector

Explanation: The indicated field needs a value.

Action: Supply a value for the indicated field.

This field is missing a valueSource: Select Data

Explanation: The indicated field requires a value.

Action: Put a value in for the indicated field.

This field is used only for SCREENSand RULESSource: Copy Definition

Explanation: You have specified a LIBRARY orENVIRONMENT identifier for an objectwhen the object does not require thisinformation to identify it.

Action: Remove the reference.

This field is used only for screens andrulesSource: Copy Defn/Data

Explanation: You have included informationwhich does not pertain to the type of objectyou are specifying.

Action: Remove the information or change theobject type.

This field must have a numeric valueSource: Screen Definer

Explanation: You have entered a nonnumericvalue into a field requiring a numeric value.

Action: Enter a numeric value.

This field must have a positive valueSource: Screen Definer

Explanation: You have entered a non-positivevalue (i.e., 0, -1) into a field requiring apositive value.

Action: Enter a positive value.

TIBCO Object Service Broker Messages Without Identifiers

Page 462: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

448 |

This is an invalid object typeSource: Definition Differences

Explanation: The type of the object is not one ofthe valid ones.

Action: Enter a valid type.

This line will call or execute a rule;enter its nameSource: Menu Definer

Explanation: A title exists for this item, but a ruledoes not.

Action: Enter the name of the rule or remove thetitle.

This menu uses a non-standard sessionmanagerSource: Menu Definer

Explanation: DEFINE_MENU was executedwith the name of a special session managerentry point that does not correspond to oneof the menu types supported byDEFINE_MENU.

Action: Change the menu name to an undefinedname or to a menu whose type is supportedby DEFINE_MENU.

THIS SCREEN ONLY SUPPORTSSTOP BY TYPE, GROUP MUST NOTBE SPECIFIEDSource: S6BTLADM-Resource Management

Explanation: You entered a stop request afterkeying in both the type and group. The TypeList screen does not support stop serverrequest for a specific group.

Action: If you wish to stop all gateways/serverswithin the type clear the group field andretry the request. If you wish to stop only thegateways/servers in the specified group thenproceed to the Group List screen and issuethe Stop from there.

This SecAdmin requires aCLEARANCE of at least %Source: Security

Explanation: Based upon users who are assignedas subjects of the SecAdmin whose userprofile is being viewed, the clearanceassigned to this Security Administrator mustbe raised. This ensures that the SecurityAdministrator's clearance is higher than orequal to any of the SecAdmin's subjects.

Action: The Security Administrator's clearancemust be set to the clearance indicated in thismessage, or higher.

TIBCO Object Service Broker Messages Without Identifiers

Page 463: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 449

This subschema exists; will beoverwritten upon confirmationSource: Tool for CA IDMS Data

Explanation: The subschema that you are aboutto load is already defined in Object ServiceBroker. The current definition will bereplaced by the new data from the importfiles shown on the screen.

Action: Press <PF21> to confirm that you want toload the subschema or press any other key ifyou do not want to load it.

This table has an instance that isreferred to more than onceSource: Object Set Definer

Explanation: The instance for this table, specifiedby the parameters, occurs more than once.

Action: Remove the duplicate entries.

This table is referred to more than onceSource: Object Set Definer

Explanation: This table is referred to more thanonce.

Action: Remove the duplicate entries.

This tool must be run with a Level 7useridSource: Promotions Bind Tools

Explanation: The userid being used to run thetool is not a Level 7 id.

Action: Use a Level 7 userid.

TITLE/FINAL cols & body will not fitwithin defined page widthSource: Report Definer

Explanation: The title columns, final columns,and all body report fields must fit within thepage width.

Action: Change the page width to accommodateall the fields.

TITLE/HEADING/FINAL rows/colsmust be 0 or a positive numberSource: Report Definer

Explanation: Title and heading rows can only bea positive number or zero. Negative title orheading rows are not valid.

Action: Change the indicated title or headingrow to a valid value.

TITLE COLS must be consecutive,starting from column 1Source: Report Definer

Explanation: Title columns can only be markedconsecutively and the first title column mustbe in column 1.

Action: Correct the T line commands to beconsecutive and start with column 1.

TITLE COLUMNs for break table "%"not the same as TITLE COLUMNs forbody table "%"Source: Report Server

Explanation: The number of title columns forbreak tables and body tables must be thesame.

Action: Use the Report Definer to correct thereport definition.

TIBCO Object Service Broker Messages Without Identifiers

Page 464: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

450 |

Title report tables can only have skipbefore and after TABLESource: Report Definer

Explanation: A Title report table can have skipbefore and after table spacing attributes only.Therefore, a user who enters values for theother spacing attributes is prompted and thevalues are reset to null. Users are encouragedto use the format screen by pressing <PF4>where a Title report table has only theappropriate attributes shown.

Action: No action required.

Titlecol too small for field "%" of reporttable "%"Source: Report Definer

Explanation: A report field is defined partly intitle columns and partly out of title columns.

Action: Move the report field or title columns tocorrect the problem.

Titles must be consecutive - followedby consecutive headingsSource: Report Definer

Explanation: Only consecutive title rows can bemarked, and consecutive heading rows canfollow them. Headings cannot precede titles.

Action: Correct the T and H markers specified toagree with the restrictions given above.

TO ASSOCIATE A SCHEDULE THETARGET RESOURCE TYPE-GROUPMUST BE SPECIFIEDSource: S6BTLADM-Resource Management

Explanation: You pressed PF5 to associated thedisplayed schedule to a specific ResourceDetail entry but you did not identify theResource ahead of time.

Action: Key in the target type and group in theinput fields provided and try your requestagain.

TO COPY A SCHEDULE SPECIFY THENEW SCHEDULE NAME IN THETARGET INPUT FIELDSource: S6BTLADM-Resource Management

Explanation: You have pressed PF4 to copy theschedule currently displayed but have notidentified the new name of the schedule.

Action: Key in the new schedule name asinstructed and press PF4 again.

To DELETE Menu "%", you mustDEFINE_MENU("%")Source: Menu Definer

Explanation: You have changed the MENUNAME and then requested to DELETE. If amenu of this new name does not exist, thereis nothing to delete. If a menu of this newname does exist, then you may not delete itfrom here.

Action: If the menu does not exist, there is noneed to delete it. To delete the (existing)menu you specified on entry to this tool,change the Menu Name back to this nameand then request delete. To delete the(existing) menu you refer to in the changed

TIBCO Object Service Broker Messages Without Identifiers

Page 465: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 451

Menu Name field, CANCEL this MenuDefinition and then request DEFINE_MENUspecifying the name of the menu you wish todelete as an argument.

To INSERT, select occurrence then useCLEAR command in SOESource: Table Editor

Explanation: You tried to use the I line commandin the Table Browser where this linecommand is not valid.

Action: To insert an occurrence, follow thedirections in the message.

To promote table % occurrence,promote the definition as wellSource: Promotion

Explanation: Table occurrences for a new tablecannot be promoted on their own.

Action: Promote the table definition as well.

To unload this object, "%" is requiredSource: Unload

Explanation: The indicated field must besupplied in order to unload the indicatedobject.

Action: Supply the indicated field.

To use LIST TABLES function, youmust fill in the UNITSource: Security

Explanation: You requested a list of tables whilespecifying tables permissions on the objectset definition screen, but you did not specifythe unit.

Action: Specify the unit to use the list tablesfunction; it narrows the search.

Token "%" not foundSource: Rule Editor

Explanation: The token specified for a FIND orCHANGE command was not found.

Action: Make sure that you have specified thetoken correctly.

Token too long to store internallySource: Rule Editor

Explanation: A rule token (quoted string) is toolong.

Action: Break the string into more parts and usethe concatenation symbol (||) to join them.

Too % END statementsSource: Rule Editor

Explanation: There are too MANY, or too FEW,END statements in the rule.

Action: Add or delete the appropriate number ofEND statements.

TIBCO Object Service Broker Messages Without Identifiers

Page 466: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

452 |

Too many % fields to fit in reportdefinitionSource: Report Generator

Explanation: Control fields and selection criteriaspecified are required for a report function toproduce a derived field. One or both of thefollowing has occurred:

• You specified too many SORT BY orACROSS BY fields for a summary report,or too many BREAK BY fields for a detailreport.

• The selection criteria, specified on theSelection screen, is too long.

Action: Do one or both of the following:

• Reduce the number of SORT BY orACROSS BY fields if the SUMMARY flag ison, or reduce the number of BREAK BYfields if the SUMMARY flag is off.

• Press the SELECT function key to displaythe Selection screen, and shorten thecriteria by removing unnecessary blanksor parentheses, or by replacing "AND" and"OR" with "&" and "|" respectively.

Too many colors in table "%"Source: Screen Server

Explanation: There are more than 600 colorsdefined in the indicated table.

Action: Either delete some color definitions thatare no longer needed, or contact TIBCOSupport to increase the limit.

Too many conditions, maximum is %Source: Rule Editor

Explanation: You have reached the maximumnumber of conditions allowed in a rule.

Action: Try to separate a single rule into two ormore rules.

Too many conditions, maximum is %Source: Rule Editor

Explanation: You have reached the maximumnumber of conditions allowed in a rule.

Action: Try to separate the single rule into two ormore rules.

Too many destinations specified forMove/CopySource: Table Definer

Explanation: Only one line command, A (After)or B (Before) is allowed for each M (Move) orC (Copy).

Action: Remove the extra As and Bs.

Too many exception handlers;maximum 32Source: Rule Editor

Explanation: A rule may have at most 32exception handlers. This includes not onlythe explicit exception handlers, but also anyUNTIL statements within the actions.

Action: If possible, delete some of the exceptionhandlers or UNTIL loops. If not, split therule.

Too many key fields in dynamicallycreated table %Source: TAM

Explanation: The number of fields in a compositeprimary key is too large.

Action: Reduce the number of fields in thecomposite primary key to 16 or fewer.

TIBCO Object Service Broker Messages Without Identifiers

Page 467: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 453

Too many levels of event rules; at most5 event levels may be nestedSource: Interpreter

Explanation: Event rules can be nested, but onlyto five levels; you have exceeded that depth.

Action: Reduce the nesting of the event rules.

Too many local variables in ruleprogramSource: Interpreter

Explanation: You created too many localvariables in one transaction, or the variablesuse up too much storage. This message mayindicate an infinite loop or a recursion that istoo deep.

Action: Verify that the recursion does not get outof control.

Too many nested listsSource: Character-based Text Editor

Explanation: At this point in the list, the numberof nested lists has not left enough room forthe last one to be indented.

Action: Remove some of the lists from beingnested.

Too many non-derived fields inDefinition Area; max is %Source: Report Definer

Explanation: The maximum number of fields hasbeen exceeded in the Definition Area.

Action: Decrease the number of fields specifieduntil you have the indicated maximum orless.

Too many open filesSource: Builtin Routines

Explanation: The maximum number of open filespermitted for a user has been reached. Nomore files can be opened.

Action: Call your system administrator for help ifyou need more files opened at the same time.

Too many parm values to show; Alloccurrences unloadedSource: Unload/Load

Explanation: The number of occurrences of aparameterized table is too great to fit into thescreen table. UNLOAD bypasses theselection of parameter values and unloads alloccurrences from the table.

Action: No action required.

TOO MANY PEER NODESACCESSED DURING PROCESSING,REQUEST REJECTEDSource: S6BTLADM - COMMON MESSAGES

Explanation: When you select remote nodes fromthe node list screen security data is retainedfor function validation. The retained data isstored in a table which has a limited numberof entries. The current request to process anew node has exhausted the node securitytable.

Action: Exit and reenter the Administrator utilityto clear the table.

Too many pops of % stackSource: Rule Editor

Explanation: Internal translator error.

TIBCO Object Service Broker Messages Without Identifiers

Page 468: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

454 |

The message log will contain a more detailederror message.

Action:

1. Push <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

Too many report tables; # is themaximum that can be used by atransactionSource: Report Server

Explanation: The number of tables of type RPTused by an application exceeded themaximum allowed. These are report tablesinto which a rule can INSERT occurrences.

Action: Reduce the number of reports used bythe application.

Too many reports used by transaction;maximum number possible is #Source: Report Server

Explanation: The number of distinct reports usedby an application exceeded the maximumallowed. Note that a report can be run anindefinite number of times, and this is a limiton report definitions.

Action: Use fewer reports in your transaction.

Too many Screens used in thistransactionSource: Screen Server

Explanation: The number of distinct screensused by an application exceeds themaximum allowed.

Action: Use fewer screens in your application.

Too many table names for FORALLAroutine; maximum number is 16Source: Interpreter

Explanation: The FORALLA routine has a totalof 16 tables currently active. It has just beencalled referencing another table name, butthere is a limit of 16 active tables.

Action: Call routine FORALLE to indicateFORALL processing is finished for at leastone of the tables that are currently active.

Too much output for Message Log from%; excess discardedSource: Print Rules

Explanation: The message log overflowed. Theoverflow was discarded.

Action: To get all the output, direct it to hardcopy or a data set.

Top of selectionSource: Secure Audit Log

Explanation: Scrolling had reached the top ofyour selection list of audit log occurrences.

Action: No action required.

Top of WindowSource: General

Explanation: You pressed <PF7> until youreached the top of the displayableinformation. No more information existsabove the screen that you are viewing.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 469: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 455

Total length of order fields too longSource: TAM

Explanation: When invoking an external sort toperform an ordering function the total lengthof the order fields and internal suffixes hasexceeded 4080 bytes

Action: Modify the rules/table definitions suchthat the total length of order fields is less than4081.

Total number of Sort/Break/Acrossfields is %, maximum is %Source: Report Generator

Explanation: The indicated total number ofcontrol fields has exceeded the indicatedmaximum.

Action: Reduce the number of control fields tothe indicated maximum or less.

Total sort field length too largeSource: Report Server

Explanation: The total length of all sort fields forthis report has exceeded 4080 bytes

Action: Alter the report definition to reduce thesort criteria field lengths to less than 4081bytes.

Total width of Print fields is %; limit is%Source: Report Generator

Explanation: The indicated report width hasexceeded the limit.

Action: Reduce the width of the report asfollows:

• Shorten the labels or display masks if theyare longer than the actual data.

• Remove some print fields from the Fieldscreen.

• Remove some function-field pairs from theSUMMARY PRINT section of the Functionscreen if it is a summary but not an acrossreport.

Traceback of rules called at time of errorSource: Interpreter

Explanation: This message is used by the ObjectService Broker program that produces theObject Service Broker Information Log. Itsignals the beginning of a list of rules thatwere called before the error occurred,starting with the most recent.

Action: Study the Information Log.

Traceback terminated; the call stack isdamagedSource: Interpreter

Explanation: This message is used by theprogram that produces the Object ServiceBroker Information Log; it indicates aninternal error.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Transaction being debugged hasreached % break eventSource: Debugger Utility

Explanation: This message is informational.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 470: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

456 |

Transaction cannot be activatedSource: Batch Client

Explanation: Transaction activation failed.

Action: See the session log for more information.

Transaction could not be committedSource: Batch Client

Explanation: The COMMIT failed.

Action: See the log for more information.

Transaction creation failedSource: Batch Client

Explanation: The session is not able to create atransaction.

Action: Check the session log for moreinformation.

TRANSFER OWNERSHIP functionCANCELLEDSource: Security

Explanation: You returned to the main menuafter canceling the TRANSFEROWNERSHIP function. The objects chosen inthe function are not transferred.

Action: No action required.

Translation object not found or invalidlocale.codepage combination for %Source: TAM

Explanation: The Locale and Codepage are validvalues but the combination of the two is not.

Action: Specify a valid locale.codepagecombination.

Translator error for rule %Source: CHANGERULE tool

Explanation: An error occurred when the rulewas detranslated to examine it for the giventoken.

Action: Try to edit the rule and save it. If a similarerror occurs, contact TIBCO Support.

Trying to % non-existent row % inE$MAPSource: Rule Editor

Explanation: Internal editor error.

The message log will contain a more detailederror message.

Action:

1. Push <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of what actions were beingperformed when this message wasgenerated.

TSO & BATCH user IDs differ;password provided is invalidSource: Security

Explanation: You submitted an offline job thathas a userid that differs from the TSO userID. A password was provided as required,but the password was not the correct one forthe userid used. Since password promptingis not possible in this case (logon in batch),the logon failed.

Action: Resubmit the batch job with the correctpassword or use the same userid as the TSOuser ID for the offline job.

TIBCO Object Service Broker Messages Without Identifiers

Page 471: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 457

Two fields of "%" have same source"%.%"Source: TAM

Explanation: The subview table definitioncontains two fields with the same sourcename.

Action: Change one of the source field names to adifferent source field in the subview tabledefinition.

Two keys must be specified forREPEAT TYPE 'PE'Source: Adabas Definer

Explanation: For an ADABAS table definitionwith repeat type of GRP, exactly two primarykeys must be supplied.

Action: Supply two primary keys for the tabledefinition.

Two or three keys must be specified forREPEAT TYPE 'MU'Source: Adabas Definer

Explanation: An ADABAS table definition withrepeat type of MU must have either two orthree primary keys.

Action: Define the correct number of keys for thetable definition.

Type and syntax combination is invalidfor ";" argumentSource: Builtin Routines

Explanation: The argument does not satisfy thetype/syntax requirements for the specifiedshareable tool.

Action: Ensure that the value used for theargument has a syntax and type combinationthat is valid for the specified shareable tool.

Type and Syntax mismatched for field:%Source: Field Dictionary

Explanation: The semantic type and syntax arean invalid combination.

Action: Change either the semantic type or thesyntax to make an acceptable pair. Refer tothe Processing manual for valid semanticand syntax combinations.

Type and syntax require Decimal = 0 for% % of dynamically created table %Source: TAM

Explanation: Decimal must be zero for thecombination of semantic type and syntaxyou specified.

Action: Consult the Managing Data manual forinformation about valid combinations ofType, Syntax, and Decimal.

Type does not match for table "%"Source: Builtin Routines

Explanation: The table definition or theprocessed program was probably modifiedsince the last pass through the preprocessor.

Action: Preprocess the program again.

TIBCO Object Service Broker Messages Without Identifiers

Page 472: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

458 |

Type error detected in conversion ofargument # of % routine "%"Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Type in 'S' to select an optional actionthen press <Enter>Source: Report Generator

Explanation: The optional selection list isselected by typing S; you can also press<PF4> to access the TABLE screen directly.

Action: Select the screen you want to access.

TYPE is a required fieldSource: Table Definer

Explanation: You must enter the TYPE of event.Valid values for TYPE include V forvalidation, and T for trigger.

Action: Enter T for trigger or V for validation forTYPE, or press <PF1> for selection.

Type mismatch for table "%"; source is"%" but target is "%"Source: Promotion

Explanation: Because the table type for thespecified table does not match on the sourceand target systems, the apply process cannotproceed as requested.

Action: If the source type is correct, either:

• include the definition change with thischange request

• or if the definition change is in anotherchange request, ensure that change isapplied prior to the change to the data.

If the target type is correct, return the changeto the developer to have the source typefixed.

Type of "%" is incompatible with that of"%"Source: Report Generator

Explanation: The semantic data types of thefields that you want to relate areincompatible.

Action: Choose another field or modify thesemantic type of the field definition throughthe Table Definer.

Type of rule "%" cannot be both"V"alidation and "T"riggerSource: Table Definer

Explanation: You used the indicated rule for bothvalidation and trigger. A validation rulemust be a logical function, whereas a triggercannot be a function.

Action: Change the event type according to thetype of the rule.

TIBCO Object Service Broker Messages Without Identifiers

Page 473: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 459

Messages beginning with: U

Unable to %, "%" is currently used in apending change requestSource: Rule Editor

Explanation: Unable to save the rule because it isused in a pending change request.

Action: Roll back the change request beforesaving the rule.

Unable to %...%Source: Table Definer

Explanation: Failed to perform specifiedoperation due to reason indicated by themessage.

Action: Make appropriate modifications to thetable definition and try the operation again.

Unable to %: %Source: Character-based Text Editor

Explanation: This message explains why theindicated action cannot be performed. Forexample, there may be security problems.

Action: If there are security problems, contactyour Security Administrator.

Unable to %; rights to object set "%"held by %Source: Object Set Definer

Explanation: Cannot perform the indicatedaction because the rights to the object set areheld by someone else.

Action: Contact the indicated person tocoordinate changes.

Unable to %; rights to object set "%"held by %Source: Security

Explanation: You cannot update the object setyou have specified because you do not havepromotion rights to the object set. Consultthe user who holds these rights in order tocoordinate update objectives.

Action: You must obtain promotion rights beforeyou may update the object set. You musteither wait for the rights to be released or youmay request that these rights be transferredto you by the current borrower.

Unable to %; undetermined rights forobject set "%"Source: Object Set Definer

Explanation: Cannot perform the indicatedaction because rights for the object set couldnot be determined.

Action: Wait and try again.

TIBCO Object Service Broker Messages Without Identifiers

Page 474: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

460 |

Unable to %; undetermined rights forobject set "%"Source: Security

Explanation: You have requested to update theobject set. Promotion rights for the object setcould not be determined. This could meanthat the object set has already been borrowedby another user for update.

Action: You can wait and try again, or you cancancel changes to the object set.

Unable to % (implies COMMITchanges; rights held by %, user %)Source: Table Editor

Explanation: The promotion rights on thecurrent table are held by the specified libraryunder the specified userid. You cannot makechanges to the table. Therefore, the specifiedoperation (e.g., SAVE, ORDER, DELETE,SELECT), which implies saving changes,cannot be performed.

Action: No action required. If you need to makechanges to the table, contact the user with thepromotion rights.

Unable to % rights for "%" of type "%":%Source: Manage Promotion Rights

Explanation: There are two possibilities:

• You are trying to perform one of thefollowing operations on an object:OBTAIN all rights, RELEASE all rights,and TRANSFER all rights. However, atable which is required by the tool islocked by another user and therefore theoperation failed.

• You are trying to perform one of thefollowing operations on an object:

OBTAIN all rights, RELEASE all rights,and TRANSFER all rights. However, youdo not have the authority to access one ofthe objects defined by the specified masterobject and therefore the operation failed.

Action: Try again.

If the problem persists contact the SystemAdministrator to determine who is holdingthe lock or ask the owners of those objects togive you access to those objects.

Unable to % Screen "%" : %Source: Screen Definer

Explanation: You have tried to do one of thefollowing to a Screen definition: DELETE,DEFINE, or SAVE. For security reasons youare not allowed to do this, for the namedscreen.

Action: No action required.

Unable to % table: %Source: Screen Definer

Explanation: You requested to do one of thefollowing to a screen table definition: LOAD,DELETE, SAVE, or PAINT. For securityreasons you are not allowed to do this.

Action: No action required.

Unable to % table of type %Source: Table Editor

Explanation: The indicated operation cannot beperformed on the table of the indicated type.For example, you may not be able to print atable of a specified type.

Action: If you want to print the contents of thetable, you can write a rule to do so.

TIBCO Object Service Broker Messages Without Identifiers

Page 475: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 461

Unable to %Source: Rule Editor

Explanation: The token cannot be expandedbecause of the given reason.

Action: Take action based on the return messagethat follows this message.

Unable to allocate VSAM file "%" fortable "%". Access denied by externalsecuritySource: TAM

Explanation: Non-Object Service Broker securitycheck rejected access to the VSAM file by thisuser.

Action: Notify customer security personnel.

Unable to allocate VSAM file "%" fortable "%". Error code = "%"Source: TAM

Explanation: A VSAM file was not allocated."Error code" concatenates the VSAM ReturnCode and VSAM Reason Codes.

Action: Consult a VSAM reference forexplanation of Return and Reason codes.Also use the Table Definer to review the dataset name and file name values.

Unable to allocate VSAM file "%" fortable "%". File is currently in useSource: TAM

Explanation: The VSAM file could not beallocated because another transaction or non-Object Service Broker application is currentlyusing it in a conflicting mode.

Action: Retry when other conflicting transactionsor applications are not active.

Unable to bind fixed definition for "%""%" using "%" "%"Source: TAM

Explanation: The definition for the specifiedcompound object cannot be bound unless allof its component objects are bound.

Action: If the compound object is a screen, ensurethat SCREENS.FIX = Y and that TABLES.FIX= Y for each screen table present in thescreen.

Unable to bind table %; %Source: Table Editor

Explanation: Your request to bind the indicatedtable was unsuccessful. The message alsocontains a reason for the failure. For example,you may not have the security authorizationnecessary (modify definition) to bind thetable, or the table may be locked while othertransactions use it.

Action: If the failure was due to locking, you cantry again later. If the failure was due tosecurity, you can contact your SecurityAdministrator. Report failures that occur forany other reason to TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 476: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

462 |

Unable to bind the definition of screen% : %Source: Screen Definer

Explanation: Your request to bind the indicatedscreen was unsuccessful. The message alsocontains a reason for the failure. For example,you may not have the security authorizationnecessary (modify definition) to bind thescreen, or the screen may be locked whileother transactions use it.

Action: If the failure was due to locking, you cantry again later. If the failure was due tosecurity, you can contact your SecurityAdministrator. Report failures for any otherreasons to TIBCO Support.

Unable to CANCEL; changes to "%"tables cannot be cancelledSource: Table Editor

Explanation: Updates to some table types, suchas VSAM, are immediately committed to thephysical database and cannot be rolled back.Thus the CANCEL command is notsupported for these table types.

Action: If you want to cancel your changes, youhave to undo the changes manually by usingthe Table Editor.

Unable to change definition: % dataexists, press PF12 to exitSource: Table Definer

Explanation: Cannot use Table Definer tomaintain definition containing Bill ofMaterial table structure.

Action: Delete existing table definition andredefine.

Unable to change definition of"%",unchanged definition copiedSource: Copy Definition

Explanation: Did not change the definition of thespecified object.

Action: Quit the tool and make sure you haveproper security access for the object.

Unable to change definition of "%"unchanged definition copiedSource: Copy Defn/Data

Explanation: This message indicates that thedefinition of the copy could not be changedto reference its new (copied) children, and sothe definition was left as is.

Action: No action.

Unable to clear table "%", copy failedSource: Copy Definition

Explanation: Some control tables need to becleared before copying into them. Could notclear this specified table.

Action: Quit the tool, and find out what type ofaccess you have on the table.

Unable to close VSAM % "%" for table"%": %Source: TAM

Explanation: A VSAM file was not closed. Thevariables, from left to right, are as follows:

1. Either "file" or "DDNAME"

2. The name of the file or the DDNAME

3. The name of the table

TIBCO Object Service Broker Messages Without Identifiers

Page 477: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 463

4. Any system-dependent information

Action: This is a system error; contact TIBCOSupport.

Unable to continue - %Source: Character-based Text Editor

Explanation: Script is unable to place its outputinto the specified destination.

There are probably too many characters to beshown as formatted. Normally 77 charactersare allowed. (This may be less in theDocument Handler.)

Action: Check that your line lengths (set by .ll)plus adjust (set by .ad) do not exceed 77.

If you are using your own setup, check yourtotal line lengths.

Unable to continue searchSource: Session Manager

Explanation: You pressed <PF5> while viewing amessage log, but either you did not enter aFIND command to be repeated, or the searchhas come to the end of the log.

Action: If you did not enter a FIND command, doso; otherwise, no action is required.

Unable to continue VSAM FORALL: %"%", table "%"Source: TAM

Explanation: The VSAM FORALL execution wasnot continued. The variables, from left toright, are as follows:

1. Either "file" or "DDNAME"

2. The name of the file or the DDNAME

3. The name of the table

Action: This is a system error; contact TIBCOSupport.

Unable to de-allocate VSAM file "%"for table "%". Error code = "%"Source: TAM

Explanation: A VSAM file was not deallocated."Error Code" concatenates the VSAM ReturnCode and VSAM Reason Code as returnedfrom VSAM.

Action: Consult a VSAM reference forexplanation of VSAM Return and ReasonCodes. Also use the Table Definer to reviewthe data set name and file name values.

Unable to debug rule "%" : %Source: Debugger Utility

Explanation: You are unable to debug the namedrule due to locking.

Action: Try again later.

Unable to define field : %Source: Field Dictionary

Explanation: An attempt to view a global fielddefinition has failed. The reason for thefailure is provided in the following message.The cause of the failure is most likely securityor locking.

Action: If the failure is due to locking, try againlater. If security is the cause, contact yourSecurity Administrator.

TIBCO Object Service Broker Messages Without Identifiers

Page 478: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

464 |

Unable to DEL OCCS; %Source: Table Editor

Explanation: This message explains why youfailed to delete all the occurrences in a table.There may be locking or security problems.

Action: If you have locking problems, try again ata later time. If you have security problems,contact your Security Administrator, whowill determine whether you should begranted delete access to the table.

Unable to DEL OCCS; no PARM tabledefined for "%"Source: Table Editor

Explanation: You are attempting to delete alloccurrences in every instance of a tablewhich is parameterized. In order to do this aPRM table is required for the table.

Action: Define a PRM table for this table.

Unable to delete field : %Source: Field Dictionary

Explanation: An attempt to delete a global fielddefinition has failed. The reason for thefailure is provided in the following message.The cause of failure is most likely security orlocking.

Action: If the failure is due to locking, try againlater. If security is the problem, contact yourSecurity Administrator.

Unable to delete table '%'Source: Delete Definition

Explanation: Inform the user that the operationof deleting the specified table fails.

Action: No action required.

Unable to display menu, % has nochoicesSource: Session Manager

Explanation: You made a request to display amenu, but the menu has no choices andcannot be displayed.

Action: Specify some choices in the definition ofthe menu if you want to display it.

Unable to display report: "%"Source: Report Definer

Explanation: Report cannot be displayed as it iscurrently defined.

Action: Check the report definition.

Unable to EDIT occurrence "%"Source: Table Editor

Explanation: You are unable to update theoccurrence you are browsing with the SingleOccurrence Editor. This may be due tolocking or security, or because one of the fieldvalues of the occurrence has specialcharacters in it.

Action: Do the following:

• If due to locking, try again at some othertime.

• If due to security, and you need to edit thisoccurrence, contact your SecurityAdministrator.

TIBCO Object Service Broker Messages Without Identifiers

Page 479: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 465

Unable to EDIT or BROWSE; "%" hasmore than 8 key fieldsSource: Table Editor

Explanation: Your table has more than 8 keyfields, which is beyond the limit supportedby the Table Browser/Editor.

Action: Reduce the number of key fields for yourtable or use other tools (e.g., Rule Editor) toupdate your table.

Unable to EDIT or BROWSE; %Source: Table Editor

Explanation: Gives an explanation of why youare unable to edit or browse the table. Forexample, it might contain the followingmessage:

READ ACCESS TO TABLE "_" DENIED

The explanation is due to locking or security.

Action: You might have attempted to edit orbrowse a table with an invalid definition.Modify the definition and try again.

• If the message is due to locking, try againlater.

• If the message is due to security, and youneed to browse or edit this table, contactyour Security Administrator.

Unable to EDIT or BROWSE; invalidsyntax "%" for % "%"Source: Table Editor

Explanation: One of the fields or parameters ofthe table you are attempting to edit or browsehas an invalid syntax value.

Action: Use the Table Definer to give the field orparameter a valid syntax. If required refer tothe Managing Data manual for valid values.

Unable to EDIT or BROWSE; noprimary key for table "%"Source: Table Editor

Explanation: A primary key has not been definedfor the table you are attempting to browse oredit.

Action: Define a primary key to the table.

Unable to EDIT or BROWSE; sourcetable "%" not foundSource: Table Editor

Explanation: You cannot edit or browse arequested subview table because thespecified source table cannot be found.

Action: Ensure that the source table is defined.

Unable to EDIT or BROWSE; table "%"is of type "%"Source: Table Editor

Explanation: The indicated table type cannot beedited or browsed.

Action: If you need to update the table, do so byusing rules.

Unable to EDIT or BROWSE;unsupported syntax "%" for parm "%"Source: Table Editor

Explanation: One of the parameters of the tableyou are attempting to edit or browse has asyntax which is not supported by the tableeditor/browser.

Action: Use another tool to access your tabledata.

TIBCO Object Service Broker Messages Without Identifiers

Page 480: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

466 |

Unable to edit rule "%" : %Source: Rule Editor

Explanation: You are unable to edit the namedrule due to locking or security.

Action: If due to locking, try again. If due tosecurity, contact your DatabaseAdministrator if there is a need for you to beable to read or modify this rule. The DatabaseAdministrator can decide if you should begiven this authority.

Unable to expand; "%" is a LOCALVARIABLE or PARAMETERSource: Rule Editor

Explanation: The requested token is a localvariable or parameter; therefore, it cannot beexpanded.

Action: No action required.

Unable to expand; "%" is anEXCEPTION nameSource: Rule Editor

Explanation: You cannot expand an exception.

Action: No action required.

Unable to EXPAND; % is not a valididentifierSource: Table Editor

Explanation: You attempted to expand an itemthat is not a valid Object Service Broker object(i.e., table, screen, report, or rule).

Action: No action required.

Unable to EXPAND; %Source: Table Editor

Explanation: An explanation of why you areunable to expand an object is provided. Forexample, it might contain the message:

Denied "VIEW_DEFN" access to "xxx"

This means you have attempted to expandan object that you do not have access to (dueto security).

Action: If the explanation is related to security,contact your Security Administrator.

Unable to EXPAND; cursor on aninvalid objectSource: Table Editor

Explanation: You pressed <PF14> to invoke theEXPAND function, but the cursor is notpositioned on an appropriate object.

Action: Position the cursor on the object to beexpanded before pressing <PF14>.

Unable to expand "%"Source: Rule Editor

Explanation: You cannot expand the selectedtoken because no object by that name exists.

Action: No action required.

Unable to find rule "%" in librarySource: Interpreter

Explanation: The specified rule was invoked by aCALL, EXECUTE or TRANSFERCALLstatement, but the rule is not in any of thelibraries (local, installation, or system).

Action: Verify that the specified rule appears inone of the libraries.

TIBCO Object Service Broker Messages Without Identifiers

Page 481: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 467

Unable to find rule % required by menuSource: Session Manager

Explanation: In the menu definition, youspecified a rule to execute, but the rulespecified cannot be found in the local,installation or system libraries.

Action: Change the rule name to one that existsin one of the libraries: system (S), installation(I), or local (L). Ensure the S, I, or L librarysearch path is the appropriate level for theanticipated location of the rule specified.

Unable to format, identifier "%" is toolongSource: HLIPREPROCESSOR

Explanation: The indicated string is too long forthe preprocessor to output.

Action: Change the identifier.

Unable to generate ruleSource: Report Generator

Explanation: The generator failed to generate arule due to an internal problem.

Action: Contact TIBCO Support.

Unable to Generate Static SQLSource: Static SQL for DB2 Gateway

Explanation: A request was made to generateStatic SQL and an error occurred. At the timeof the error, the Data Object Broker wastrying to retrieve the DB2 definition for thetable.

Action: View the message log for moreinformation about why the Static SQL cannotbe generated.

Unable to identify referenced DATAfor object "%" of type "%"Source: Manage Promotion Rights

Explanation: You are trying to perform one of thefollowing operations: OBTAIN all rights,RELEASE all rights, TRANSFER all rights onan object that contains reference data.However, the tool had some difficultyidentifying the referenced data for thatobject.

Action: Check to see whether the referenced datafor that object is defined correctly.

Unable to INSERT because of %Source: Unload/Load

Explanation: LOAD was unable to insert theindicated occurrence. An attempt is made toexplain the failure.

Action: Action depends on the reason for thefailure. A duplicate primary key usuallymeans that the occurrence already existed,and may not require any further action. Thisis common with shared screen or reporttables. Reasons such as lockfail or securityfailmay require action, or mean that it isimpossible to load the object under yourconditions.

Unable to insert into '%', copy failedSource: Copy Definition

Explanation: The COPY operation requiresaccess to some tables that are not accessible atthis time.

Action: Make sure you have proper security onthe table specified in the error message.

TIBCO Object Service Broker Messages Without Identifiers

Page 482: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

468 |

Unable to invoke Table Definer; DATtable does not existSource: CA Datacom Table Definer

Explanation: You are attempting to view theDAT table definition for a CA-Datacom tablebut it has not yet been generated.

Action: Generate the DAT table definition.

Unable to load data for table %: Thedata and definition are boundSource: Unload/Load

Explanation: New data cannot be inserted into atable whose data are bound.

Action: The data of the table must be unboundbefore the load will succeed.

Unable to load data in IDGEN table %;definition is boundSource: Unload/Load

Explanation: Load cannot insert data into anIDGEN table whose definition is bound.

Action: The definition must be unbound for loadto succeed.

Unable to load rule "%" in "%"Source: Definition Differences

Explanation: You are trying to compare thedifference between two rules; however, anerror occurred while loading the rules.

Action: Check and see whether the rules andlibraries exist, and whether you have theauthority to access these libraries and rules.Retry the operation again.

Unable to locate or create XML parserobjectSource: Builtin Routines

Explanation: An internal failure occurredcreating an XML parser object.

Action: Contact TIBCO Support.

Unable to move and copy at the sametimeSource: Character-based Text Editor

Explanation: You issued MOVE (M) and COPY(C) line commands at the same time.

Action: Remove all but one type of linecommand. You can do the other linecommands in separate subsequentinteractions.

Unable to obtain exclusive lock on fastmass insert table "%"Source: TAM

Explanation: An exclusive lock on the table couldnot be obtained. Most likely, other people areusing the table.

Action: Try the fast mass insert later. The tablelock will be obtained when other people havefinished using the table.

Unable to obtain lock on '%', nothingdeletedSource: Delete Definition

Explanation: You are trying to delete an objectbut somebody is using and locking the dataon one of the tables required in the operation.

Action: Wait and try the operation again until thelock has been released.

TIBCO Object Service Broker Messages Without Identifiers

Page 483: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 469

Unable to obtain promotion rights dueto LOCKFAILSource: Rule Editor

Explanation: You cannot obtain promotion rightsfor the rule you have edited because oflocking.

Action: Try again later.

Unable to open VSAM % "%" for table"%" for %Source: TAM

Explanation: A VSAM file or DDNAME couldnot be opened. The variables, from left toright, are as follows:

1. Either "file" or "DDNAME"

2. The name of the file or the DDNAME

3. The name of the table

4. One of "input," "output," or "update"

Action: This is a system error; contact TIBCOSupport.

Unable to parse copy specificationsSource: Copy Definition

Explanation: A parser error has occurred whenreading an entry.

Action: Check for syntax errors and try again.

Unable to parse table specification : '%'Source: Delete Definition

Explanation: You are trying to delete a table;however, the specified table does not have acorrect syntax.

Action: Make sure the table you have entered hasthe correct syntax and try the operationagain.

Unable to perform justificationSource: Report Definer

Explanation: The justification that was requestedcannot be accommodated within the pagewidth. It is likely that the length of a numberof left or right justified fields do not leaveenough room to allow for other fields that arecentered.

Action: Change the justification values.

Unable to print - %Source: Print Table

Explanation: A security restriction, definitionerror, or data error is preventing the tablefrom printing.

Action: Check that you have access to the tableand check the definition and contents of thetable.

Unable to print - too many indirectreference tablesSource: Print Rules

Explanation: You specified too many indirectreference tables.

Action: Reduce the number of indirect referencetables until you can print.

Unable to print rule "%"Source: Print Rules

Explanation: An internal problem is preventingthe specified rule from being printed. Therules listed above this rule have been printed.

Action: Delete this rule from the list and tryagain. You can also delete the rules above thespecified rule because they have alreadybeen printed. Contact TIBCO Support aboutthe internal error.

TIBCO Object Service Broker Messages Without Identifiers

Page 484: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

470 |

Unable to process date - possibly badcharacterSource: Session Manager

Explanation: You have typed over a date so thatit cannot be used.

Action: Correct the date.

Unable to read defaultsSource: Copy Definition

Explanation: Cannot read the default attributesfrom the specified file.

Action: Obtain security rights on this objectbefore copying.

Unable to remove bind from table %; %Source: Table Editor

Explanation: Your request to reset the bind onthe indicated table failed. The message alsocontains a reason for the failure. For example,you may not have the security authorizationnecessary (modify definition) to reset thebind from the table, or the table may belocked while other transactions use it.

Action: If your request failed due to locking, youcan try again later. If your request failed dueto security, you can contact your SecurityAdministrator. If your request failed for anyother reason, contact TIBCO Support.

Unable to remove the bind fromdefinition of screen % : %Source: Screen Definer

Explanation: Your request to mark the indicatedscreen as not being bound was unsuccessful.The message also contains a reason for thefailure. For example, you may not have the

security authorization necessary (modifydefinition) to bind the screen, or the screenmay be locked while other transactions useit.

Action: If the failure was due to locking, you cantry again later. If the failure was due tosecurity, you can contact your SecurityAdministrator. Report failure for any otherreason to TIBCO Support.

Unable to repeat commandSource: Character-based Text Editor

Explanation: You pressed <PF9>, but noprevious command exists to be repeated.

Action: No action required.

Unable to repeat searchSource: Global Cross Ref. Search

Explanation: You pressed <PF9>, but noprevious query exists.

Action: Enter a new query.

Unable to resolve definition of %Source: Static SQL for DB2 Gateway

Explanation: The Static SQL interface for the DB2Gateway is attempting to resolve thedefinition of the MetaStor field identified.The next error message outlines the problem.Potentially, the field is no longer in the DB2table, or the syntax of the DB2 field is not oneof the DB2 syntaxes supported (i.e., floatingpoint).

Action: View the next error message. Ifappropriate, use the Table Definer to updateand save the external table for DB2 data.Attempt Static SQL generation again.

TIBCO Object Service Broker Messages Without Identifiers

Page 485: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 471

Unable to resolve type %Source: Static SQL for DB2 Gateway

Explanation: Static SQL code is being generated.Specifically, the DECLARE statement wasbeing generated. The field's type as providedby DB2 cannot be resolved. The next errormessage indicates the reason.

Action: If necessary, contact TIBCO Support.

Unable to RESTORE defn of % becauseof %Source: Unload/Load

Explanation: The LOAD tool failed to restoresome attributes of PARMS and/or FIELDS ofthe specified table.

Action: Clear the table data which you haveloaded in and do one of the following:

• If the failure is due to insufficient securityclearance:

• Ask your Security Administrator forMODIFY DEFN access to that tableand try loading the file again, or

• Ask your Security Administrator toload the file for you.

• If the failure is due to LOCKFAIL, tryloading the file later.

UNABLE TO RETRIEVE DATA FROMREMOTE NODE, LOCALPROCESSING CONTINUESSource: S6BTLADM-Resource Management

Explanation: The control information required toprocess under the selected node could not beretrieved from the target node. Processingwill continue under the current (local) node.

Action: Review the outbound Resource Detail todetermine if there are enough activeoutbound paths. In addition review theSYSLOG to obtain any additional messagesthat may have been produced.

Unable to save, %Source: Tool for IMS Data

Explanation: This message explains why theinformation cannot be saved. For example,there may be locking problems.

Action: If there are locking problems, try againlater.

Unable to SAVE; intermediate commitnot allowed for "%" tablesSource: Table Editor

Explanation: The SAVE primary command is notsupported for the indicated table type.

Action: You can issue the EDIT command to savethe changes and continue editing the sametable.

TIBCO Object Service Broker Messages Without Identifiers

Page 486: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

472 |

Unable to save changes to %; rights heldby % user %Source: Session Manager

Explanation: You made a request to SAVEchanges to a menu. You cannot save yourchanges, however, because borrowing rightsfor some parts of the menu are held bysomeone else.

Action: Do one of the following:

• Cancel your changes.

• Change the menu name to a non-existentmenu name, SAVE, obtain the borrowingrights from whoever has them, and editthe first menu again to look like the othersaved menu.

Unable to save definition...%Source: Table Definer

Explanation: Failed to save table definition dueto reason specified in the message. Forexample, you may be missing requiredinformation.

Action: Make appropriate modifications asindicated in the message to obtain a validtable definition.

Unable to save field : %Source: Field Dictionary

Explanation: An attempt to save a global fielddefinition has failed. The reason for thefailure is provided in the following message.The cause of the failure is most likely securityor locking.

Action: If the failure is due to locking, try againlater. If security is the cause, contact yourSecurity Administrator.

Unable to save or test a menu with nochoicesSource: Menu Definer

Explanation: You have not entered any items forthis menu. It cannot be saved or displayedwithout items.

Action: Enter at least one item for the menu.

Unable to SAVE screen table; data isLOCKED. Try again.Source: Screen Definer

Explanation: In the Screen Table Painter, youtried to SAVE your changes but the data storeis locked.

Action: Do one of the following:

• Wait and try again

• Change the screen table name to a newname and then SAVE. You can copy thechanges to the original screen at a latertime.

Unable to save table definition... Enterrequired informationSource: Table Definer

Explanation: All mandatory information was notentered.

Action: Enter mandatory information.

TIBCO Object Service Broker Messages Without Identifiers

Page 487: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 473

Unable to separate field "%.%" from thedisplay mask dataSource: Screen Server

Explanation: It was not possible to determine thefield data from the user input. The input maycontain characters which are potentialdisplay mask control characters, thus aunique interpretation of the data is notpossible.

Action: Enter valid data in the indicated field.

Unable to set VSAM skip RPL: % "%",table: "%"Source: TAM

Explanation: VSAM SKIP PPL was not set. Thevariables, from left to right, are as follows:

1. Either "file" or "DDNAME"

2. The name of the file or the DDNAME

3. The name of the table

Action: This is a system error; contact TIBCOSupport.

Unable to shift % character(s)Source: Report Definer

Explanation: The user tried to shift all reportfields, starting from the cursor position, leftor right N characters (N is the number ofcharacters indicated on the command line).This shift will cause overlapping fields ormove fields past the left or right boundary ofthe report (limited by the maximum pagewidth).

Action: Change the number of shift characters(N) specified on the command line.

Unable to show fields due to securitySource: Select Data

Explanation: You do not have the security accessnecessary to view the fields of thisoccurrence.

Action: No action required.

Unable to show fields of someoccurrences due to securitySource: Select Data

Explanation: You do not have security access tosome of the selected occurrences.Consequently, you cannot view the fields ofthese occurrences.

Action: No action required.

Unary operation (; of a ; ;) not allowedSource: Interpreter

Explanation: You applied a unary operator to avalue that does not have a semantic typewhich is compatible with the operator.

Action: Verify that the operation is valid. See theProcessing manual for more informationabout operations.

TIBCO Object Service Broker Messages Without Identifiers

Page 488: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

474 |

Unauthorized: CURRENT GROUP is"%"Source: Security

Explanation: You made a request to change thecurrent group in the User Profile screen, butyou are not authorized to operate out of thespecified group. The current group is notchanged.

Action: If you want to be able to operate out ofthe specified group, you must become amember of that group by having the SystemAdministrator, the Security Administrator ofthe group owner, or the group owner addyour userid to the group definition.

Unauthorized: CURRENT GROUP isnullSource: Security

Explanation: You requested a change to theCurrent Group from null to a group of whichyou are not a member. The Current Groupremains as null (i.e., you are not operatingout of any group).

Action: You can use the MEMBERSHIPS functionfrom the userid profile to determine thegroups that have you as a member, then typea valid group name into CURRENT GROUPfield of your userid profile. Press <Enter> tohave the group change take effect.

Unauthorized: press <PF14> to viewmissing authorizationSource: Security

Explanation: You made a request to update theenable list for an object set, without havingcontrol of all the objects in the object set, orwithout owning all the objects in the objectset that have control mode set to Y.

Action: Press <PF14> to view a list of objects forwhich you require authorization before youcan update the enable list of the object set. Toget authorization, you can ask the objectowner to either extend control access ortransfer ownership as appropriate.

Unauthorized request -- DENIEDSource: Security

Explanation: You requested a function that youare not authorized to do. For example, youmay have tried to look at a group definition,manage permissions, or enable an object set.

Action: No action is required.

Unauthorized to generate/remove StaticSQLSource: Static SQL for DB2 Gateway

Explanation: A Security error was raised whenyou attempted to remove Static SQL. Thefollowing error message indicates why theaccess was disallowed.

Action: Contact your System Administrator toobtain the appropriate security.

TIBCO Object Service Broker Messages Without Identifiers

Page 489: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 475

Unbalanced parenthesesSource: Global Cross Ref. Search

Explanation: The number of openingparentheses does not match the number ofclosing parentheses.

Action: Correct the parentheses in the query.

Unbinding failed: Press <PF2> for moreinformationSource: Screen Definer

Explanation: Your request to mark the indicatedscreen as not being bound failed.

Action: If the failure was due to locking, try againlater. If the failure was due to security,contact your Security Administrator.

Undefined action code %; EntryskippedSource: Unload/Load

Explanation: The action code is not A, D, or O.LOAD bypasses the current subload andprocesses the next subload.

Action: Do one of the following:

• If you were using the UNLOAD tool,contact the database administrator to see ifthe @UNLOAD and IMPORTCODEStables are complete.

• If you were using EXPTABLE, check thearguments that are passed to the tool.

Undefined option "%"Source: HLIPREPROCESSOR

Explanation: You specified an invalid option forthe HLIPREPROCESSOR tool.

Action: The valid options are: LIST, NO LIST,ERRORSTOP, NO ERRORSTOP.

Unexpected end of statementencountered at "%"Source: Rule Editor

Explanation: A semicolon (;) or colon (:) ismissing.

A new statement was started before thelogical end of the first statement wasencountered.

Action: Add the missing semicolon (;) or colon(:).

Unfinished rule statementSource: HLIPREPROCESSOR

Explanation: An Object Service Broker rulestatement does not have a semicolon or colonat the end.

Action: Correct the syntax of the statement.

Unicode or raw data fields are omittedfrom the table(s). Press <Enter>Source: Report Definer

Explanation: Unicode and raw data fields are notallowed in reports.

Action: None.

Unicode value must have a multiple of4 hexadecimal digitsSource: Table Editor

TIBCO Object Service Broker Messages Without Identifiers

Page 490: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

476 |

UNIT is requiredSource: Screen Definer

Explanation: You must fill out the UNIT fieldbefore you can save the screen. Press <PF1>for more information regarding this field.

Action: Type your unit into this field.

Unknown character encounteredSource: Screen Definer

Explanation: An unrecognized character hasappeared in the Image Area.

Action: Overstrike the character with arecognizable character.

Unknown line command; Use "s" toselect fields, then press PF3Source: Field Dictionary

Explanation: You typed in a line command otherthan S.

Action: Remove the line command. Use S toselect fields from the global field dictionary.

Unknown object type, '%' not deletedSource: Delete Definition

Explanation: You are trying to delete an objectbut the object has an invalid type. Therefore,the object is not deleted.

Action: Check to see if an invalid type for thespecified object has been provided. If so, thenfix the error and retry it again.

Unknown object typeSource: Security

Explanation: You requested the management ofpermissions for an object, but the type ofobject requested is not recognized.

Action: Fill in the TYPE field with one of thesupplied abbreviations.

Unknown screen field at row # column#Source: Screen Server

Explanation: A 3270 Read Modified operationdetected a screen field starting at theindicated screen row and column. ObjectService Broker, however, did not place anyObject Service Broker-defined screen field atthat location. This message may be seen if thescreen formatting for the last screendisplayed by Object Service Broker wasdestroyed. For example, you pressed theCLEAR key which physically clears thescreen, or an operating system messagedisrupted the screen format.

Action: If the screen formatting was lost, press<PF24> to redisplay the last Object ServiceBroker screen shown.

Unload cancelledSource: Unload/Load

Explanation: The exit key was pressed while youwere in the UNLOAD tool. You return to theworkbench.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 491: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 477

Unload ended due to error; <PF2> formoreSource: Unload/Load

Explanation: An error was encountered duringthe UNLOAD process.

Action: Press <PF2> to view the error messages.

Unloaded % rules from library %Source: Unload/Load

Explanation: The specified number of rules havebeen unloaded from the specified library.

Action: No action required.

Unloaded % Tables % Screens %Reports % RulesSource: Unload/Load

Explanation: The number of objects specified inthe message were unloaded to the data set.Note that a screen or a report can containmultiple screen tables or report tablesrespectively. For example, if you unload onescreen that has three screen tables, thismessage will say:

3 TABLES 1 SCREENS 0 REPORTS 0 RULES UNLOADED

Action: No action required. If SCR was chosen asthe media, press <PF2> to see a more detailedmessage or any error messages resultingfrom the unload process.

Unloaded %Source: Promotion

Explanation: The specified number of objectshave been unloaded.

Action: No action required.

Unloaded data for % tables or tableinstancesSource: Promotion

Explanation: The data of the specified number oftables or table instances have been extractedfrom the MetaStor.

Action: No action required.

Unloading % %Source: Unload/Load

Explanation: The indicated object has beenunloaded.

Action: No action required.

Unloading all information for % Table%Source: Unload/Load

Explanation: The definition and occurrences of atable are being unloaded. The first % isreplaced with the type of the table. Thismessage appears in the user log file.

Action: No action required.

UNLOADING CONTROL TABLESSource: Promotion

Explanation: This message appears when youextract a change request to be applied toanother system.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 492: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

478 |

Unloading definition of % Table %Source: Unload/Load

Explanation: The definition of a table is beingunloaded. The first % displays the type oftable, and the second % displays the tablename. This message appears in the user logfile.

Action: No action required.

UNLOADING OBJECTSSource: Promotion

Explanation: This message appears when youextract a change request to be applied toanother system.

Action: No action required.

Unloading occurrences only of Table %Source: Unload/Load

Explanation: The occurrences of a TDS table arebeing unloaded. This message appears in theuser log file.

Action: No action required.

Unloading Report %Source: Unload/Load

Explanation: This message appears in the userlog file to show which report is beingunloaded.

Action: No action required.

Unloading report table %Source: Unload/Load

Explanation: This message appears in the userlog file to show which report table is beingunloaded.

Action: No action required.

Unloading RULE % from Library %Source: Unload/Load

Explanation: This message appears in the userlog file to show which rule is being unloaded.

Action: No action required.

Unloading Screen %Source: Unload/Load

Explanation: The definition of a screen is beingunloaded. This message appears in the userlog file.

Action: No action required.

Unmatched "%" in selection string forreport field "%" of report table "%"Source: Report Server

Explanation: The opening and closing bracketsin a selection string for a report function donot match.

Action: Using the Report Definer, review thereport field in error and match the opening tothe closing brackets.

TIBCO Object Service Broker Messages Without Identifiers

Page 493: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 479

Unmatched "%" in selection string forreport table "%"Source: Report Server

Explanation: The opening and closing bracketsin a selection string for a body report table donot match.

Action: Using the Report Definer, review thecontrol information for the report and matchthe opening to the closing brackets.

Unmatched quotation marks found inselection criteriaSource: Report Generator

Explanation: The selection string contains an oddnumber of single quotation marks.

Action: Ensure that the single quotation marksoccur in pairs.

Unmatched quotation marks found oncommand lineSource: Table Definer

Explanation: Unmatched quotation marks werefound on the primary command line whenyou executed a command.

Action: Ensure that the single quotation marksoccur in pairs.

Unmatched quotes in %Source: General

Explanation: You issued a primary command inthe message log that contained unmatchedquotation marks.

Action: Correct the command so that thequotation marks are matched.

Unrecognized character: "%"Source: Rule Editor

Explanation: Possibly a mismatch in terminaltypes. The message log may contain a moredetailed error message.

Action: See the Processing manual for adescription of what characters are valid in agiven context. Replace the indicatedcharacter by one valid in that context.

UNRECOGNIZED CONFIRMATIONRECEIVED, PROCESSING HAS BEENABANDONEDSource: S6BTLADM-Resource Management

Explanation: The required key was not pressedto confirm the previous action.

Action: No action required.

Unrecognized serverid %Source: Static SQL for DB2 Gateway

Explanation: The table definition identifies aserverid to handle requests for that table.Table @DB2SYS does not contain anoccurrence for that serverid value.

Action: Add an entry to @DB2SYS that identifiesthe DB2 tables from which to retrievedefinition information for that table. Refer tothe TIBCO Service Gateway for DB2 manualfor more information.

TIBCO Object Service Broker Messages Without Identifiers

Page 494: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

480 |

Unrecoverable error in rule %Source: Debugger Utility

Explanation: Your application has reached apoint in processing where an unrecoverableerror occurs.

Action: Use the debugger commands to obtainmore information about the error. If theunrecoverable error is unexpected (forinstance, it occurs under the debugger)contact TIBCO Support.

Unsupported DB2 column type %Source: Static SQL for DB2 Gateway

Explanation: When the Static SQL interface forthe DB2 Gateway attempted to generate theHost variable declarations, the DB2 typecould not be resolved. The error message thatfollows this message indicates the reason.

Action: If necessary, contact TIBCO Support.

Unsupported selection: Table %, cursortype "%", abbrev "%"Source: Static SQL for DB2 Gateway

Explanation: Static SQL cannot be generated forthe requested selection.

Action: The selection needs to be modified.

Unsupported syntax "%"; cannot useCA-Datacom field "%"Source: CA Datacom Table Definer

Explanation: You requested the inclusion of aCA-Datacom field that has a syntax notsupported by the Object Service Broker CA-Datacom server.

Action: You must remove the entry; the fieldcannot be included. Note: If the unsupportedfield is part of the CA-Datacom table KEY,you cannot define an Object Service Brokertable on this CA-Datacom table.

UNTITLED multi-occurrence screentable cannot have scroll fldSource: Screen Definer

Explanation: You have entered the name of aScroll field, and the name of a screen table, tothe SCROLL AMOUNT ENTRYspecification. However, the screen table isspecified to be untitled and to have morethan one occurrence.

In a multi-occurrence screen table the scrollfield must be in the title area.

Action: Do one of the following:

• Change the screen table reference to haveMAX OCCUR = 1.

• Change the screen table definition to havethe SCROLL AMOUNT ENTRY field inthe Title area.

TIBCO Object Service Broker Messages Without Identifiers

Page 495: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 481

UPD must be set to 'N' - Field is aSpecial fieldSource: Adabas Definer

Explanation: Invalid value specified for fieldUPD. It must have a value of N since the fieldis a special field, i.e., one of Superdescriptors,Hyperdescriptors, Subdescriptors andPhonetic descriptors.

Action: Specify N for UPD field.

UPD must be set to 'Y' - Field is not aSpecial fieldSource: Adabas Definer

Explanation: Invalid value specified for fieldUPD. It must have a value of Y since the fieldis not a special field, i.e., not one ofSuperdescriptors, Hyperdescriptors,Subdescriptors and Phonetic descriptors.

Action: Specify Y for field UPD.

Update not allowed during validationor derived fields processingSource: TAM

Explanation: A validation or derived field rulehas attempted to do an update operation.

Action: Do one of the following:

• Correct the validation rule or derived fieldrule in the table definition.

• Remove the update operation from thevalidation or derived field rule.

Update not allowed in browse modeSource: TAM

Explanation: An INSERT, DELETE or REPLACEoperation was requested while the SessionManager was in BROWSE mode.

Action: Exit the BROWSE mode and go intoUPDATE mode for INSERT, DELETE, orREPLACE operations.

Update not generated, no fields in table% to updateSource: Static SQL for DB2 Gateway

Explanation: Cannot generate update Static SQLrequest because there are no field in thespecified table to update.

Action: Verify that specified table is valid.

UPDATE NOT PERMITTED:displaying UNCHANGED ScreendefinitionSource: Screen Definer

Explanation: In the Screen Definer, yourequested to display a screen as defined inthe current context (i.e., you changed thedefinition since the Screen Definer sessionbegan). Since you are not allowed to updatethe definition, the stored definition isdisplayed.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 496: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

482 |

UPDATE NOT PERMITTED; printingUNCHANGED Screen definitionSource: Screen Definer

Explanation: In the Screen Definer, you changedthe screen definition and requested toPRINT. Since you did not have permission tomodify the screen definition, the storeddefinition is printed.

Action: No action required.

Update refused - maximum number ofupdates pendingSource: TAM

Explanation: The commit limit exception hasbeen raised.

Action: Do one of the following:

• Issue COMMITs more often.

• Use the COMMITLIMIT exception signal.

Update to queue definition deniedSource: Batch Submission Tool

Explanation: You do not have the authority toupdate the definition of a queue. Only usersin the security group ADMIN are allowed toupdate batch queue definitions.

Action: No action required.

UPDATED PAGES PERTRANSACTION PROFILERETRIEVAL ERRORSource: S6BTLADM - UPDT PAGES/TRX

Explanation: When attempting to retrieve thedata to build the screen an error wasdetected.

Action: Review the job log for possible additionalmessage that may help identify the cause ofthe problem. Retry your request. Contact thesupport center if the problem persists.

Updates to % SAVED; promotion rightsNOT obtainedSource: Table Editor

Explanation: Changes to the table were saved,but you have not obtained the promotionrights.

Action: Inform the user with the promotionrights of any changes that you make.

Updates to object set Permissions for"%" CANCELLEDSource: Security

Explanation: You canceled from the Object SetEnable list.

Action: No action is required.

Updates to Security Administrator "%"CANCELLEDSource: Security

Explanation: You canceled from the SecAdminprofile screen.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 497: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 483

Updates to table "%" %Source: Table Editor

Explanation: Confirms that as you haverequested all updates to the table were eithersaved or canceled.

Action: No action required.

Updates to user "%" CANCELLEDSource: Security

Explanation: The Security Administrator hascanceled changes to a user profile.

Action: No action required.

Use "S" to select a starting recordSource: Table Definer

Explanation: Select the CA-IDMS record wheredatabase access will begin. For optimumresults this record should be a CALC recordor indexed with the MetaStor primary keybeing the CA-IDMS CALC key or index field.

Action: Select a starting record in IDMS.

Use "S" to select one DB2 Creator/TableSource: Table Definer

Explanation: You did not type an S next to a DB2Creator/Table pair.

Action: Use an S to mark your DB2Creator/Table selection.

Use "S" to select one M204 file/groupSource: Table Definer

Explanation: You can use only S to indicate yourselection.

Action: Type an S next to the file or group thatyou want to select and press <Enter>.

Use 'S' to select an optionSource: Report Generator

Explanation: You have pressed <Enter> withoutmaking a selection.

Action: Use S to select the screen you want toaccess.

Use a "D" to indicate which subschemadefinition to deleteSource: Tool for CA IDMS Data

Explanation: You selected the "Delete IDMSSubschemas" option from the main menu ofthe Object Service Broker/IDMS ManagerUtility, but you did not use the correct linecommand to specify the subschema to delete.

Action: Type a D line command next to thesubschema you want to delete, and press<Enter>.

Use alphanumeric character forselectionSource: Report Generator

Explanation: Only alphanumeric characters (0 -9, A - Z) can be used to select an item.

Action: Use alphanumeric characters (0 - 9, A - Z)to select.

Use an "S" to select a functionSource: Tool for CA IDMS Data

Explanation: All IDMS management screensrequire at least an S to choose an action.

Action: Type an S beside a function.

TIBCO Object Service Broker Messages Without Identifiers

Page 498: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

484 |

Use P(arm), K(ey) or S(elect) to selectfieldsSource: Table Definer

Explanation: You did not use a valid letter toselect the CA-IDMS elements that willparticipate in the MetaStor table definition.

Action: Select valid parameters and/or keys andfields.

Use Relate Tables screen to define thetable relationshipsSource: Report Generator

Explanation: As you have selected more than onetable, you need to relate the tables in aspecific way so that the data in them can beproperly matched.

Action: Type S in the Relate Table(s) field toaccess the screen.

Use S to select object type(s) to managerightsSource: Promotion

Explanation: You have used a character otherthan S to select an object type tomanage/administer rights.

Action: Use the character S to select objecttype(s).

Use S to select object type(s) to promoteSource: Promotion

Explanation: You have used a character otherthan S to select the object type of objects topromote.

Action: Enter S against the object type(s).

Use same char for field to which "%" of"%" is to be relatedSource: Report Generator

Explanation: You did not use the samealphanumeric character (0-9, A-Z) to select apair of related fields from the given sourcedata tables.

Action: Use the same alphanumeric charactersfor both fields, such as S.

Use same char for field which "%" of"%" is related toSource: Report Generator

Explanation: You did not use the samealphanumeric character (0-9, A-Z) to select apair of related fields from the given sourcedata tables.

Action: Use the same alphanumeric character tomark both fields, such as S.

Use Specify Parameter(s) screen for theselected table(s)Source: Report Generator

Explanation: As the table(s) you selected areparameterized, you need to specify theparameter values for them by filling out theparm values in the Specify Parameter(s)screen.

Action: Type S in the PARAMETER VALUEselection field.

TIBCO Object Service Broker Messages Without Identifiers

Page 499: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 485

User/group % has rights for objects inCR%Source: Promotion

Explanation: The named user/group has rightsfor some of the objects in the specifiedchange request, so you cannot include thespecified change in the consolidation.

Action: Do not include the specified changerequest in the consolidated change.

User "%" DISCLAIMED; on SAVE, newSecAdmin will be "%"Source: Security

Explanation: A Security Administrator in aSecAdmin profile successfully disclaimed auserid. The userid will be disclaimed onlywhen the Security Administrator saves theprofile.

Action: Save this profile to have the disclaim takeeffect.

User "%" has NO belongings to transferSource: Security

Explanation: You requested to TRANSFEROWNERSHIP for either yourself or for yoursubject, but the specified user does not haveany belongings.

Action: No action required.

User % does not have clearance to reporton the Access LogSource: Secure Audit Log

Explanation: You attempted to invoke thereporting facilities for the audit log but youdid not have the permissions to do so.

Action: Contact your Security Administrator toset up the proper permissions for you.

User % does not have rights to deletereport %Source: Secure Audit Log

Explanation: You attempted to delete thespecified audit log report but you did nothave borrowing rights to that report.

Action: Contact the Promotion Administrator.

User % does not have the clearance toview the Access LogSource: Secure Audit Log

Explanation: You attempted to view the audit logcontents but you did not have thepermissions to do so.

Action: Contact your Security Administrator toget the proper clearance.

User exit % failed: %Source: General

Explanation: The user exit rule failed.

Action: Correct the rule or the arguments passedto it.

User Profile segment# unavailable.Used seg0 insteadSource: Table Definer

Explanation: Segment# specified in the UserProfile is non-existent or offline. Defaultsegment# 0 is used.

Action: User table data should not reside onsegment 0. Execute the sharable toolMOVTAB to correct the segment# after theproper segment has been defined or madeactive.

TIBCO Object Service Broker Messages Without Identifiers

Page 500: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

486 |

USER TRACE "OFF" REQUEST HASBEEN ISSUEDSource: S6BTLADM - USER ACTIVITY

Explanation: Notification that the requested stopuser trace has been issued.

Action: No action required.

USER TRACE "OFF" REQUEST NOTCONFIRMED, REQUEST IGNOREDSource: S6BTLADM - USER ACTIVITY

Explanation: The request to stop the tracing ofthe displayed user was not issued becausethe request was not confirmed.

Action: No action required.

USER TRACE "ON" REQUEST HASBEEN ISSUEDSource: S6BTLADM - USER ACTIVITY

Explanation: Notification that the tracing requesthas been issued to the Data Object Broker.

Action: No action required.

USER TRACE "ON" REQUEST NOTCONFIRMED, REQUEST IGNOREDSource: S6BTLADM - USER ACTIVITY

Explanation: When requested to press <PF10> toconfirm the user tracing request you chose toabandon the request by pressing a differentfunction key.

Action: No action required.

Userid % is already in the list; notADDEDSource: Security

Explanation: You made a request to add a useridto the list of subjects in a SecAdmin profile,but the subject is already in the list.

Action: No action required.

Userid % is SUSPENDED. Contact yourSecurity AdministratorSource: Security

Explanation: You attempted to log on, but yourclearance is currently set to 0 (suspended).Possible reasons for the suspension are thatthe system is undergoing routinemaintenance, or there is a problem associatedwith this particular userid.

Action: Contact the Security Administrator todetermine the reason for the suspension.

Userid is already logged on orIDPREFIX in useSource: External Gateway Logon

Explanation: The Userid or IDPREFIX you areusing to connect to the Data Object Broker isalready in use.

Action: Check to see if the session is alreadyrunning. If required, cancel the previoussession and resubmit the new one.

TIBCO Object Service Broker Messages Without Identifiers

Page 501: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 487

Userid not defined; contact SystemAdministratorSource: Table Definer

Explanation: Your userid is not recognized by theData Object Broker. It has been changed sinceyou logged on.

Action: Contact your System Administrator.

Utility not accessible here - submitJCL(IMSUJCL)Source: Tool for IMS Data

Explanation: Option selected is not supportedfrom this screen.

Action: Modify and run sample memberIMSUJCL in the JOB.CNTL data set.

TIBCO Object Service Broker Messages Without Identifiers

Page 502: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

488 |

Messages beginning with: V

Valid length for key or parameter is 1 -127Source: Table Definer

Explanation: A parameter or primary key lengthcannot exceed 127.

Action: Correct the length of the parameter orprimary key.

Valid length is 1 - 254Source: Table Definer

Explanation: Except for a parameter or primarykey field, the maximum length for acharacter field is 254.

Action: Correct the length of the selected field.

Valid number of copies is 1 to 255Source: Batch Submission Tool

Explanation: The specified number of outputcopies is invalid.

Action: Enter a number in the range of 1 to 255.

Valid table types : %Source: Table Definer

Explanation: The table type that you specified isinvalid.

Action: Select a valid type from the given list.

Valid types for SEARCH are TBL, SCR,RPT, LIB, OBS, GRPSource: Security

Explanation: In the TRANSFER OWNERSHIPfunction, you made a request to SEARCH foran entry in the six lists provided, but you didnot specify which list to search: table, screen,report, library, object set, group (indicated byTBL, SCR, RPT, LIB, OBS, GRP, respectively).

Action: Change the type abbreviation to one thatis appropriate, and request the SEARCHfunction again. The cursor is placed on thematching entry in the appropriate list if suchan entry is found.

NOTE: you can use pattern matching for thesearch (e.g., *EMPLOYEE* or ??LIST).

Validatefail: %Source: Batch Control Card

Explanation: Some of your input values havefailed validation, as explained by themessage.

Action: Correct the errors and try again.

Validation failed for table "%"Source: TAM

Explanation: An event rule has signalledvalidation fail.

The message log will contain a more detailederror message.

Action: Review the message log.

TIBCO Object Service Broker Messages Without Identifiers

Page 503: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 489

Value "%" is incompatible with syn %len % dec % of "%"Source: Report Generator

Explanation: The indicated parameter value isincompatible with its definition.

Action: Correct the parameter value.

Value for serverparm "%" must bespecifiedSource: Table Definer

Explanation: Enter a value for the indicatedserverparm.

Action: A value for the serverparm must beentered.

Value of "%" is too large for field "%"Source: Table Editor

Explanation: You entered a value for a numericfield that is too large. For example, if the fieldis defined as B2, this message appears whena number greater than 32767 is entered.

Action: Enter a smaller value or possible changethe definition of the table to allow largervalues. For example, change the B2 to B4.

Value of "%.%" has an invalid instancelength; possible error in table data storeSource: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Value of "%.%" is undefinedSource: Interpreter

Explanation: You tried to use a field of a tablewithout assigning a value to the field orwithout accessing the table with a FORALLor GET statement.

Action: Verify that the field has a value beforeusing the field.

Value of FIELD cannot be NULL for anon-parameterized tableSource: Print Table

Explanation: This table can only be included in ajoin by matching one of its fields to the othertable's field, but no field name was entered.

Action: Enter a field name and ensure that atleast one of the fields is a primary key.

Value of FINAL COLUMN of reporttable "%" of report "%" is invalidSource: Report Server

Explanation: The FINAL COLUMN fieldcontains a negative number.

Action: Use the Report Definer to correct theindicated report table.

Value of TITLE COLUMN of reporttable "%" of report "%" is invalidSource: Report Server

Explanation: The title column value of a body orbreak report table was a negative number, orthe number of title columns is greater thanthe number of final columns.

Action: Use the Report Definer to correct theindicated report table.

TIBCO Object Service Broker Messages Without Identifiers

Page 504: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

490 |

Value selected will not fit in field beingprompted forSource: Field Help for Reference

Explanation: The prompt value that you selecteddoes not fit in the screen field for which theprompt is active.

Action: Choose another prompt value, or contactyour system administrator.

Value will not fit within lengthspecified - value="%",length=#Source: Interpreter

Explanation: Internal error. The message logcontains a more detailed error message.

Action: Do the following:

1. Press <PF2> and print the log.

2. Contact TIBCO Support with the log and adescription of the actions performedbefore the message was displayed.

Variable %.% too small to holdexpression valueSource: Interpreter

Explanation: In an assignment statement, thetarget field of a table is not large enough toreceive the source data.

Action: Change the field definition or the sourcedata.

Verify indirect call parameter valuesSource: Print Rules

Explanation: You have chosen parameter valuesfrom the prompt.

Action: You can verify, change, delete or add tothe values you have chosen.

Version is required for object % of type%Source: Copy Definition

Explanation: A value for the version parameter isrequired for the specified object.

Action: Enter the appropriate value for theversion parameter and try the operationagain.

Version mismatch detectedSource: External Gateway Logon

Explanation: The version of the gateway/serverand the Data Object Broker it iscommunicating with, are not compatible.

Action: Check that you are using the correctversion of the gateway/server, and that youare communicating with the Data ObjectBroker that you expect. Restart thegateway/server with a version that iscompatible with the Data Object Broker thatit is communicating with.

View definition access to % % by %deniedSource: Audit Log Message

Explanation: VIEW_DEFINITION access to thisobject by the specified user was denied.

Action: The user can ask someone who hasCONTROL access to the object to provideVIEW_DEFINITION access.

VIEW DEFN mode must be "Y" if anyother modes are "Y"Source: Security

Explanation: You are specifying a permissionslist for one of the following:

• An object

TIBCO Object Service Broker Messages Without Identifiers

Page 505: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 491

• Defaults

You have set some of the modes to Y, but notthe VIEW_DEFN mode. The VIEW_DEFNmode is required to exercise any of the othermode permissions because the definition ofan object is needed to read or modify thedefinition, for example.

Action: Do one of the following:

• Set the VIEW_DEFN mode to Y.

• Set the other modes in the row to N.

• Remove the row completely by blankingout or erasing the USER|GROUP field ofthe row.

VIEW DEFN permission needed toinclude "%" in the object setSource: Security

Explanation: You attempted to include a table forwhich you do not have permission in thetables permissions of an object set definition.Since the definition of the table must beconsulted to determine if the table hasparameters, the table entry cannot beincluded.

Action: You must remove the entry before savingthe tables permissions specification of theobject set, either by replacing the table namewith blanks, nulls or another name. You canconsult an authorized user to gainpermissions for the table before including itin the object set definition.

VIEW failed. No index field defined onsegmentSource: Table Definer

Explanation: Invalid operation. You cannot viewsince there is no index field defined on theparticular IMS segment

Action: No action required.

VIEW GROUP is for GROUP entriesonly; "%" is a userid entrySource: Security

Explanation: You positioned the cursor on auserid entry and requested to view a group.

Action: Position the cursor on a group entrybefore requesting to view a group.

Virtual image NOT printed (%); onlydefinition was printedSource: Screen Definer

Explanation: In the Screen Definer, yourequested printing the screen definition andthe virtual image; however, because theimage is too wide to print, only the definitionwas printed.

Action: No action required.

Virtual screen template printedSource: General

Explanation: The virtual image of the screen hasbeen printed.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 506: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

492 |

VSAM GET failure for % "%" for table"%"Source: TAM

Explanation: A record cannot be obtained from aVSAM file. The variables, from left to right,are:

1. Either "file" or "DDNAME"

2. The name of the file or the DDNAME

3. The name of the table

Action: Check if the VSAM file exists. If the fileexists, contact TIBCO Support.

TIBCO Object Service Broker Messages Without Identifiers

Page 507: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 493

Messages beginning with: W

WARNING: "%" may be an invalidscreen table nameSource: Screen Definer

Explanation: When using the Screen Definer, youincluded a reference in the Screens list thatcannot be validated (by validation code).This warning usually occurs because oflocking.

Action: No action required.

WARNING: %'s row offset % is notenough, should be at least %Source: Report Definer

Explanation: There is not enough room todisplay this title report table and its spacingattributes.

Action: Increase the offset from the bottom of thepage to make enough room for the display.The least amount required is given.

WARNING: %; Press <%> to confirmSource: Confirmaction Utility

Explanation: warning and instruction on how toconfirm

Action: No action

WARNING: % % has been extractedfrom Library %Source: Promotion

Explanation: The named rule has been extractedfrom the specified library because thepreviously extracted file is not available.

Action: Make the extract file available if youwant to repackage from the previouslyextracted file.

WARNING: % does not currently existSource: Security

Explanation: A Security Administrator or aSystem Administrator updating the profile ofa user, has entered a TDS segment numberthat does not exist.

Action: This message is only a warning, so youdo not have to change the segment number.The TDS segment must exist, though, beforethe user can put objects there.

WARNING: % has been re-extractedSource: Promotion

Explanation: The specified object has beenextracted from the MetaStor because thepreviously extracted file is not available.

Action: Make the file available if you want torepackage the object from the previouslyextracted file.

TIBCO Object Service Broker Messages Without Identifiers

Page 508: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

494 |

Warning: % has maximum number offields definedSource: Field Dictionary

Explanation: All of the fields cannot be copiedinto the table definition because themaximum number of fields has beenreached.

Action: Remove some or all of the selected fieldsand retry.

WARNING: *** Change request hasCorequisites ***Source: Promotion

Explanation: The application developer specifiedother change requests that must accompanythis change request.

Action: Ensure that the corequisite changerequests have been processed.

WARNING: *** Error flag(s) in@PROM_OBJ(%) found to be set ***Source: Promotion

Explanation: Phase 2 or Phase 3 apply processingoccurred although errors were detected inPhase 1. The request may not work asdesigned.

Action: Refer to the Promotions manual forinformation on running the GEN_SYS_TBLSrule.

WARNING: *** No TABLES entry forreport table "%" ***Source: Promotion

Explanation: The specified report table does nothave an entry in TABLES. This is probably abreak table created in release 1.16.

Action: You should use the report painter toredefine the report table.

WARNING: *** Objects have beenunbound ***Source: Promotion

Explanation: Some of the objects included in thechange request are bound on the targetsystem. Thus, these objects have to beunbound before the change can be applied.This message is followed by a messageinforming you of the action to take.

Action: If you are in a multiple session system,restart the Execution Environment and applythe change again. If you are in a singlesession system, log off and log on to applythe change.

WARNING: Screen image may containtruncated linesSource: General

Explanation: The screen image that wasproduced may have image lines that aretruncated.

Action: You can try using a larger page width.

TIBCO Object Service Broker Messages Without Identifiers

Page 509: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 495

Warning: A COMMIT occurred during% of:Source: Copy Defn/Data

Explanation: This message indicates that aCOMMITLIMIT was reached whileprocessing processing a copy request andthat a COMMIT was issued. This means thatany subsequent errors arising while copyingthe current object could leave a partial copystored.

Action: No action.

WARNING: about to % rule %; press %or type 'confirm'.Source: Rule Editor

Explanation: You have received a warningmessage about an action that is about to beperformed on a rule.

Action: Press the indicated PF key or typeCONFIRM in the command line to performthe action. Press any other key to cancel theaction.

WARNING: About to delete report "%";press <PF22> to confirmSource: Report Generator

Explanation: The indicated report and its tableswill be deleted if you confirm your deletionrequest.

Action: Press the indicated function key toconfirm the deletion, or press any otherfunction key to cancel.

WARNING: about to OVERWRITEexisting objset "%"; press <%> toconfirmSource: Object Set Definer

Explanation: You are attempting to save an objectset with a new name that has the same nameas an existing object set. Confirmation isbeing requested because if the existing objectset is overwritten it will be lost.

Action: Press the specified key to confirm or anyother key to cancel. If you do not wish tooverwrite an existing object set then canceland enter a new nonexisting name for theobject set.

WARNING: About to overwrite report"%"; press <ENTER> to confirmSource: Report Generator

Explanation: The definition of the indicatedreport will be overwritten if you press theindicated function key to confirm.

Action: To confirm the request, press theindicated function key. To cancel the request,press any other key.

WARNING: About to overwrite rule"%"; press <ENTER> to confirmSource: Report Generator

Explanation: The indicated rule name alreadyexists in the local library, and will beoverwritten if you confirm the action.

Action: Press the specified key to confirm theaction, or press any other key to cancel.

TIBCO Object Service Broker Messages Without Identifiers

Page 510: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

496 |

WARNING: ACROSS_BY required forAcross Report (MAX ACR ^= 0)Source: Report Definer

Explanation: If the MAX ACR field is not 0, youare producing an Across Report, and youmust put a value in the SORT_ACROSS_BYfield.

Action: Do one of the following:

• Enter a value in the SORT_ACROSS_BYfield.

• Set the MAX ACR field to 0.

WARNING: ALL report fields on breaktable must be derived fieldsSource: Report Definer

Explanation: Only derived fields may be presenton break tables.

Action: Change all fields for the break table toderived fields.

WARNING: an intermediate commitwas madeSource: Copy Definition

Explanation: The commit limit has been reachedand therefore a warning has been issued tolet you know that some of the object has beencopied.

Action: No action required.

WARNING: borrowing rightsUNVERIFIED for this menuSource: Menu Definer

Explanation: You are updating a MenuDefinition and Borrow Rights could not beverified when you requested the update.

Action: No action required.

WARNING: Break table "%" requires aminimum page length of "%"Source: Report Definer

Explanation: All the fields on the defined breaktable cannot fit within the specified pagelength.

Action: Remove some fields from the break tableor alter the page length.

WARNING: cannot access body controlfields - no security on %Source: Report Definer

Explanation: During validation, impropersecurity on the body table is detected.

Action: To continue with the task, either obtainsecurity on the table or change the tablename to one on which there is propersecurity.

WARNING: Cannot check changerightsSource: Report Definer

Explanation: Promotion rights cannot bechecked because of a locking error.

Action: Try using the Report Definer later.

WARNING: cannot perform all checks -no security on %Source: Report Definer

Explanation: On the way into the Report Definer,certain checks are performed. Due to lack ofsecurity on a table, not all checks can beperformed.

Action: Get proper security on the identifiedtable or replace it with one that you haveproper security on.

TIBCO Object Service Broker Messages Without Identifiers

Page 511: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 497

WARNING: cannot SAVE changes;rights are held by "%"Source: Screen Definer

Explanation: You just entered the Screen Defineror the Screen Table Painter, and the rights tothe screen are held in such a way that yourchanges cannot be saved.

Action: No action required. If you want to makechanges to the screen, ask the person whohas the rights to release them. Otherwise,you can change the name of the screen to anonexisting one to save your changes.

WARNING: Cannot SAVE changes;rights held by %, user %Source: Table Editor

Explanation: Changes for the table that the userchose to edit cannot be saved because thepromotion rights on the table are held by thespecified library under the specified userid.

Action: No action required. If you need to makechanges to the table, contact the user with thepromotion rights.

WARNING: cannot SAVE changessince this object set is ENABLEDSource: Security

Explanation: You are viewing an object setdefinition for an enabled object set.

Action: No action required.

WARNING: changes will be ignored;no update authorizationSource: Security

Explanation: A Security Administrator isviewing the definition of a group that theAdministrator is not authorized to update.Security Administrators can view any Groupdefinition, but they cannot always update it.This warning is displayed upon entry to thescreen to notify the Security Administratorthat no changes are allowed.

Action: No action required.

WARNING: Control break "%" deletedSource: Report Definer

Explanation: After the deletion of a control breakfield from within a body report table, thecontrol break and any control break tableassociated with that breakpoint are deleted.

Action: No action required.

WARNING: CONTROL permissionmay not be ENABLED for GroupsSource: Security

Explanation: You are looking at an object setenable list, and the object set includesControl permission to an object in the objectset; since Control is not allowed for groups,the object set can be enabled for users only.

Action: No action is required.

WARNING: decimal symbol shouldappear ONCE in basic stringSource: Screen and Report Painters

Explanation: The decimal symbol should appearonly once in the basic string

Action: Make sure that the decimal symbolappears only once in the basic string.

TIBCO Object Service Broker Messages Without Identifiers

Page 512: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

498 |

WARNING: decimal symbol shouldnot be a digit place holderSource: Screen and Report Painters

Explanation: You should not have the decimalsymbol as a place holder.

Action: This will cause the gateway problemsinterpreting the mask. Remove the decimalsymbol from the digit place holder spot.

WARNING: Definition may be toolarge to process for table %Source: Screen and Report Painters

Explanation: The number of fields in the screentable or report table definition exceeds themaximum number of fields allowed in aCTABLE.

Action: Reduce the number of fields in the screentable or report table.

WARNING: Definition of table % mayhave been modified by %Source: Promotion

Explanation: You are promoting the data of thenamed table but the specified user/grouphas right to the definition of the table. If thespecified user/group has modified the tabledefinition, your change request may failduring phase 1 of target apply because thedefinition of the table is not part of yourchange.

Action: Check with the specified user/group tosee if the change (if any) of the tabledefinition would affect your change request.

WARNING: displaymask basic stringshould not contain digits 0-8Source: Screen and Report Painters

Explanation: The basic string should not containany digits between 0 and 8.

Action: Remove the digits between 0 and 8 fromthe basic string.

WARNING: Exclude "%" from currentdefn; press <PF23> to confirmSource: Report Generator

Explanation: The indicated source data table willbe excluded from the report if you confirmyour request. This will also remove any fieldsof that table referenced in the report.

Action: Press the specified function key toconfirm, or press any other function key tocancel.

WARNING: existing permissions maybe LOST when ENABLEDSource: Security

Explanation: You are enabling an object set forthe first time. If any of the objects in the objectset are not part of another enabled object setand they have permissions specified, thesepermissions are lost when the object setbecomes enabled (i.e., if you save the enablelist).

Action: If you are concerned about losingexisting permissions, you can do one of thefollowing:

• View individual permissions lists forobjects in an object set to determine thepermissions.

• Enable the object set and save, then view areport of lost permissions when you returnto the main menu.

TIBCO Object Service Broker Messages Without Identifiers

Page 513: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 499

WARNING: Exit the Report Generator;press <PF12> to confirmSource: Report Generator

Explanation: This confirmation message appearswhen you request to exit the ReportGenerator by pressing <PF12>.

Action: Press <PF12> to exit; otherwise, press<Enter> to stay on the current screen.

WARNING: Fields "%" and "%"overlap; IMS updates will bedisallowedSource: Table Definer

Explanation: The indicated fields overlap eachother.

Action: Modify the IMS offset or IMS length (orboth) of the inserted field to eliminate theoverlap.

WARNING: Last % characters of %truncated; press <%> to confirmSource: Table Editor

Explanation: When a long W string is editedusing the Single Occurrence Editor, it isbroken up into several rows. Additionalshift-in/shift out characters may be added tomake each row a well-formed W string. Thusextra space may be created for the user toinput data. The input value can then be toolong to fit the original field. This message isgenerated to warn the user about thesituation. The last few characters will betruncated and the user is prompted forconfirmation.

Action: Do one of the following:

• Press the confirm key to confirm the save.The value is truncated automatically bythe Single Occurrence Editor.

• Press some other key to cancel the save.Edit the value manually to make it fit thefield.

WARNING:MAX_ACROSS/ACROSS_BY requiredif TITLE/FINAL COLS ^= 0Source: Report Definer

Explanation: Title columns and final columns areonly valid for Across Reports.

Action: Do one of the following:

• Enter valid values in the MAX ACR andSORT_ACROSS_BY fields.

• Set the TITLE COLS and FINAL COLSfields to zero.

WARNING: Missing documentation orunit for highlighted %(S)Source: Promotion

Explanation: Documentation is missing fortables, screens or reports.

Action: Use the E line command to providedocumentation.

WARNING: No promorights/documentation for highlighted%(S)Source: Promotion

Explanation: The highlighted rules are missingtheir documentation or promotion rights.

Action: If the problem is missing documentation,provide documentation by using the E linecommand. If promotion rights are missing,contact the System Administrator.

TIBCO Object Service Broker Messages Without Identifiers

Page 514: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

500 |

WARNING: non-printable datadisplayed as "."Source: Builtin Routines

Explanation: Unprintable data is displayed asthe dot (.) character. Unprintable charactersare hexadecimal &x'AD 1..3F &x'BD.

Action: No action required.

WARNING: non-printable datadisplayed as "."Source: General

Explanation: Unprintable data is displayed asthe dot (.) character. Unprintable charactersare hexadecimal &x'AD 1..3F &x'BD.

Action: No action required.

WARNING: not all print fields havefunctions in SUMMARY PRINTSource: Report Generator

Explanation: The SUMMARY flag is on, butsome of the PRINT fields that are not SORTBY or ACROSS BY fields do not havefunctions in the SUMMARY PRINT section.You may want to select functions for thosefields.

Action: Ignore the warning if you want to ignorethose fields; otherwise, select functions forthose fields.

WARNING: object is part of ENABLEDobject set; cannot SAVESource: Security

Explanation: You have requested to managepermissions for an object whose permissionsare managed through object sets. You cannotmake changes to these permissions directly.

Action: To obtain a list of the Enabled Object SetPermissions which include this object, press<PF4>. To add permissions, you must defineanother object set which contains this object,then specify Object Set Permissions on theobject set and then Enable it. To removepermissions, disable any Enabled Object SetPermissions which include the permissionsof this object you wish to revoke.

WARNING: Objectset "%" has objectsmissing securitySource: Security

Explanation: You attempted to save the securityinformation for the object set but did notspecified security for all its componentobjects.

Action: You can define the missing security forthe objects of the object set save again, orpress the specified confirm key to ignore thewarning message.

WARNING: only % of % fields could beLOADED into Image AreaSource: Screen Definer

Explanation: In the Screen Table Painter, youmade a request to load a table. Some of thefields are omitted, however, because thescreen table Image Area does not have

TIBCO Object Service Broker Messages Without Identifiers

Page 515: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 501

enough room to load all of the fields. Notethat this is different from exceeding themaximum number of fields in a screen tabledefinition.

Action: You can cancel your changes or comparethe screen table and the source table fields todetermine which fields are missing.

Warning: Parameter list too long toshow on the screenSource: Character-based Text Editor

Explanation: You executed TED with an inputtable that has too many parameters to bedisplayed.

Action: No action required.

WARNING: Password update FAILEDSource: Security

Explanation: You updated the password in a userprofile and saved, but the routine thatupdates passwords failed. If you are creatinga new user, the password will be null. If youare trying to update the password of anexisting user, the old password is stillcurrent.

Action: If you still want to update the password,ask your security administrator to examinethe encryption exit. If you are updating yourown profile, note that the password updaterequest failed and that to gain entry to ObjectService Broker at next logon, you must usethe old password.

WARNING: possible overlaps detected;see MSGLOG for detailsSource: Screen Definer

Explanation: You just saved a screen definitionand returned to the workbench. The screendefinition you saved will overlap thephysical boundaries of the current screen ifyou display it. Details about these overlapsare in the message log.

Action: Press <PF2> to see the details of theoverlap potential, and then either change thescreen definition (if the screen is to bedisplayed on a physical screen that is thesame size as the current one), or ignore theinformation (if the screen is to be displayedon a physical screen large enough to handlethe indicated overlaps).

WARNING: PRM table for % should beincluded in this changeSource: Promotion

Explanation: When you promote a newparameterized TDS table, you should alsopromote its PRM table in the same change.Otherwise the promotion system will not beable to backup the data in the table next timewhen you modify the table definition.

Action: Create a PRM table for the specified TDStable and include it in this change.

WARNING: Promotion rights for % "%"not obtainedSource: Field Dictionary

Explanation: The promotion rights for the objectbeing edited are held by someone else.

Action: If you need promotion rights, contact thespecified user.

TIBCO Object Service Broker Messages Without Identifiers

Page 516: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

502 |

WARNING: Promotion rights for % "%"not obtainedSource: Report Definer

Explanation: The promotion rights for the objectbeing edited are held by someone else.

Action: If you need the promotion rights, contactthe specified user.

WARNING: Promotion rights for % "%"not releasedSource: Field Dictionary

Explanation: The promotion rights for an objectare held by someone else; therefore they havenot been released.

Action: If you need promotion rights, contact thespecified user.

WARNING: Promotion rights for % "%"not releasedSource: Report Definer

Explanation: The promotion rights for an objectare held by someone else; therefore, theyhave not been released.

Action: If you need the promotion rights, contactthe specified user.

WARNING: Report field % not entirelydefined within finalcolSource: Report Definer

Explanation: A report field is defined partly infinal columns and partly out of finalcolumns.

Action: Move the report field or the finalcolumns.

WARNING: Report field col extendsbeyond defined page width: %Source: Report Definer

Explanation: A report field is defined to extendbeyond the current page width.

Action: If the report field is to be printed on thereport, either change the page width withinthe Definer, or change the page width at runtime through the utility $RPTPARMS.

WARNING: Report field in "%" extendsbeyond page width of %Source: Report Definer

Explanation: A report field is defined beyond thepage width boundary.

Action: Move the report field or alter the pagewidth.

WARNING: Report field row extendsbeyond defined page: %Source: Report Definer

Explanation: One of the field's rows extendsbeyond the specified page length.

Action: Make the specified field start at aposition that does not make it extend beyondthe page length, or increase the page length.

TIBCO Object Service Broker Messages Without Identifiers

Page 517: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 503

WARNING: Report selection will notfit within report functionSource: Report Definer

Explanation: The report selection string cannotfit within the report function selection.

Action: If you want the report functioncalculation to be limited by the reportselection, enter the report selection on theFORALL statement that inserts data intoyour report table.

WARNING: Report table "%" requiresminimum page length of "%"Source: Report Definer

Explanation: The specified report table is definedto have at least one report field that cannot beplaced within the page length specified.

Action: Change the defined page length or movethe report field to a line above the pagebottom.

WARNING: Rights for % "%" held by"%", requestor "%"Source: Report Definer

Explanation: Promotion rights cannot beobtained on the object because they are heldby someone else.

Action: If you need the promotion rights, contactthe person who holds them.

WARNING: Rights for globalfield "%"held by "%", requestor "%"Source: Field Dictionary

Explanation: Someone else holds the promotionrights for the global field you are defining.You will not be able to save changes or deleteit the field.

Action: No action required, if you are not makingchanges to the field. If you need promotionrights, contact the specified user.

WARNING: Rights held by %, user %Source: Table Editor

Explanation: The promotion rights on the tableare held by the specified library under thespecified userid. Changes to the table will besaved, but promotion rights will not beobtained.

Action: No action required. If you need thepromotion rights, contact the user who holdsthem.

Warning: Rights to % held by % user %Source: Session Manager

Explanation: You made a request to edit a menu.When the menu definition is presented, thismessage indicates that the borrowing rightsfor parts of the menu are held by anotheruser. You cannot save any changes until theborrowing rights are released or transferredto you.

Action: You can view the menu, but you cannotsave any changes. Acquire borrowing rightsfrom whoever currently has them beforetrying to update the menu again.

TIBCO Object Service Broker Messages Without Identifiers

Page 518: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

504 |

WARNING: rights to FCNKEYS ofScreen held by "%"Source: Screen Definer

Explanation: You pressed the SPEC_FCNKEYSoption <PF18> from the Screen Definer, butthe rights to the FCNKEYS table are held bysomeone else. If SYSTEM is holding therights, you cannot save any changes that youmake; otherwise, you may be able to saveyour changes.

Action: You cannot save changes if the rights areheld by SYSTEM, but you may be able tosave changes otherwise. Discuss the matterwith the person holding the rights toFCNKEYS for this screen.

WARNING: Rights to object set "%"held by %Source: Object Set Definer

Explanation: Someone else has rights to theobject set that you are currently defining. Youwill not be able to save any changes that youmake.

Action: No action required.

WARNING: Rights to object set "%"held by %Source: Security

Explanation: You have just entered the object setpermissions context. The warning indicatesthat you cannot make changes to the objectset permissions because the borrowing rightsare held by another user.

Action: If you must make changes, then youshould consult with the borrower so thatborrowing rights can be transferred to you.Otherwise, you will need to wait for theborrowing rights to be released.

WARNING: rights to Screen held by %Source: Screen Definer

Explanation: You just entered the Screen Definerfor the indicated screen. If the rights for thescreen are held by SYSTEM, you cannot saveany changes you make; otherwise, you maybe able to save changes.

Action: You cannot save changes if the rights areheld by SYSTEM, but you may be able tosave changes otherwise. Discuss the matterwith the person holding the rights toFCNKEYS for this screen.

WARNING: rights to screen table heldby %Source: Screen Definer

Explanation: You just entered the Screen TablePainter, and the rights to the screen table areheld by another person. If SYSTEM isholding the rights, you cannot save anychanges you make; otherwise, you may beable to save your changes.

Action: You cannot save changes if the rights areheld by SYSTEM, but you may be able tosave changes otherwise. Discuss the matterwith the person holding the rights toFCNKEYS for this screen.

WARNING: Security not set correctlyon objectset %, no @CAPABILITIESSource: Promotion

Explanation: The change request did not includean occurrence of the @CAPABILITIES table.

Action: Check the source system and make surethat there is an occurrence of@CAPABILITIES for every object set there. Itmay be necessary to roll back the changerequest and re-extract it after correcting thesource system.

TIBCO Object Service Broker Messages Without Identifiers

Page 519: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 505

WARNING: Segment "%" not coveredby metadata fieldsSource: Table Definer

Explanation: Define the indicated segment withMetaStor fields at least up to the minimumlength indicated on the screen.

Action: Specify a field or fields to cover theminimum length of the segment.

WARNING: Source table "%" has morefields than allowedSource: Table Definer

Explanation: The indicated source table for thecurrent subview table definition has morefields than allowed in the Table Definer. As aresult, only the maximum number of fieldsallowed is shown.

Action: You can delete and change the fields thatare shown. When you save the subview tabledefinition, only the fields shown will besaved.

WARNING: Table "%" has more fieldsthan allowedSource: Table Definer

Explanation: The indicated table has more fieldsthan allowed. As a result, only the allowedmaximum number of fields are shown.NOTE: If you save the table definition, onlythe fields shown are saved; the excess fieldsare removed.

Action: If you want to include any fields notshown, you must first remove some of thefields displayed.

If you want to exclude the fields notdisplayed, you can save the table definitionwhen you are finished.

If you want to keep the same fields, press theCANCEL function key to leave the TableDefiner.

WARNING: Table may contain data;see help for restricted modificationsSource: Table Definer

Explanation: The Table Definer cannot determinewhether the table has data or not for variousreasons. For example, the data segmentmight be off line.

The message warns that you are modifyingthe definition at your own risk. In general,you are safe if you are NOT shortening afield length, changing a field or parametersyntax and decimal length, changing aparameter or key length, adding new fieldsin between existing ones, adding newparameters, deleting existing fields orparameters, or modifying the "key" attributeof any field.

Action: Care must be taken when performing themodifications mentioned above.

WARNING: Tables of type "%" shouldbe maintained by % painterSource: Table Definer

Explanation: Maintain tables of the indicatedtype with its specialized painter, or you mayget unexpected results.

Action: Cancel the Table Definer session.

TIBCO Object Service Broker Messages Without Identifiers

Page 520: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

506 |

Warning: There are % additional userson the systemSource: Promotion

Explanation: This warning message tells youhow many other users are on the ObjectService Broker system.

Action: If you are going to do a promotion, makesure that no other users are on the system.

WARNING: unable to perform allchecks, no security on "%"Source: Screen Definer

Explanation: On the way into the Screen Definer,certain checks are performed to ensure thescreen is structured correctly. Due to lack ofsecurity on the identified table, some of thechecks that involve this table cannot beperformed.

Action: Obtain proper security on the identifiedtable or replace it with one with propersecurity.

WARNING: values may be truncated;use DETAIL for full displaySource: Unload

Explanation: You are viewing the data instancelist for a table, as requested from theUNLOAD screen via the INSTANCESELECT function. Since this display showsonly a fixed number of characters/parametervalue, and the parameter may have greaterlength than this number, you may not see theentire value in this screen.

Action: If you wish to see the parameter valuesfor a given data instance in their entirety,position the cursor to the instance entryrequired and press the DETAIL function. Youwill be shown a screen which has parametervalues only for that instance.

Warning - Cannot validate all of thedefinition. Press <PF3> to confirm.Source: Adabas Definer

Explanation: Because the definition is of a DBIDand FILENO combination that has not beenextracted, the definer is unable to crossvalidate all of the components of thedefinition. Note that this message couldappear if the DBID and FILENO combinationhave been incorrectly specified.

Action: Either except the definition and ensuremanually that it is correct or extract the DBIDand FILENO combination and then re-saveor redefine the table to validate thedefinition.

WELCOME TO THEADMINISTRATOR, PRESS PF1 ONANY SCREEN FOR HELPSource: S6BTLADM - COMMON MESSAGES

Explanation: The welcome messages is aninformation message to ensure users areaware of the online help facility in the ObjectService Broker Administrator utility.

Action: No action required.

WHERE string invalid on % to table "%"Source: TAM

Explanation: One of the following occurred:

• A non-unique key selection was specifiedfor a DELETE operation.

• An INSERT/REPLACE operationspecified a selection string.

Action: Do one of the following:

• Specify a unique key selection for aDELETE operation.

TIBCO Object Service Broker Messages Without Identifiers

Page 521: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 507

• Remove the selection string in theINSERT/REPLACE operation.

Will not delete actual job in operatingsystemSource: Batch Submission Tool

Explanation: When you delete a batch requestthat has a status of SUBMITTED orEXECUTING, the delete command removesthe request entry from only the ObjectService Broker queue. You are still requiredto delete the job from the operating systemjob queue.

Action: Press <PF22> to confirm that you want todelete the job, or press any other key tocancel the deletion request. If you confirmedthe deletion request, delete the job entry inthe operating system.

Window Manager ERROR: Unable torestore previous window.Source: Rule Editor

Explanation: Internal error.

Action: Contact TIBCO Support.

WORK SPACE NOT AVAILABLE TOCOMPLETE REQUESTSource: S6BTLADM - COMMON MESSAGES

Explanation: When attempting to perform largedata manipulations the Administrator uses alarge work buffer. During programinitialization this work buffer could not beacquired.

Action: Try rerunning the Administrator utilitywith a larger region size.

Write to "%" dataset failed; module "%";R15 = %Source: Session Manager

Explanation: Write to sort work file failed. TheDDNAME, the module name, and the returncode are supplied for diagnostic purposes.

Action: Call your system administrator to checkthe return code in Register 15 against theappropriate vendor's manual. Correct theproblem as required.

TIBCO Object Service Broker Messages Without Identifiers

Page 522: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

508 |

Messages beginning with: X

XCALL statement not permitted in aderived fields, trigger, or validationruleSource: Interpreter

Explanation: You cannot use a TRANSFERCALLstatement in a derived field or an event rule.

Action: Verify that the derived field or event ruledoes not invoke another rule withTRANSFERCALL.

XXXXXXXX HAS AN UNKNOWNCONNECTION TYPE CODESource: S6BTLADM - USER ACTIVITY

Explanation: When translating the connectiontype code for the display, the type code couldnot be identified.

Action: Contact TIBCO Support.

XXXXXXXX IS A SERVICEREQUESTOR FROM NODE XX--16--XXSource: S6BTLADM - USER ACTIVITY

Explanation: The connection list is intended todisplay information about Execution Enginetype connections. The selection you made isfor a connection from a Peer systemidentified by the specified node name.

Action: No action is required.

XXXXXXXX IS A XXXX SERVERASSOCIATED WITH XXXXXXXX INSTREAM XXSource: S6BTLADM - USER ACTIVITY

Explanation: The connections display isintended to process Execution Environmentconnections. The connection you selected is agateway/server of the specified type that iscurrently in use by the specified user.

Action: No action is required.

XXXXXXXX IS AN AVAILABLE XXXXSERVERSource: S6BTLADM - USER ACTIVITY

Explanation: The connection screen is intendedto list Execution Environment sessions. Theconnection you selected to display is agateway/server of the specified type. Thespecified gateway/server is not currently inuse by any transactions.

Action: No action is required.

XXXXXXXX IS SIGNING ON, DETAILSTATUS NOT AVAILABLESource: S6BTLADM - USER ACTIVITY

Explanation: The selected connection has notcompleted all the logon processing. You willnot be able to retrieve detailed informationuntil the log on processing is complete.

Action: Retry your request.

TIBCO Object Service Broker Messages Without Identifiers

Page 523: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 509

XXXXXXXX NOT AVAILABLE, LISTPRESENTED IN ITS PLACESource: S6BTLADM - USER ACTIVITY

Explanation: The specified connection ID is notavailable for detailed display. The generalconnection list is redisplayed in its place.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 524: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

510 |

Messages beginning with: Y

YOU ARE NOT AUTHORIZED FORTHE REQUESTED SELECTIONSource: S6BTLADM - COMMON MESSAGES

Explanation: You have selected a menu item forwhich you are not authorized.

Action: Contact your security administrationpeople and have them set up the appropriatesecurity. Refer to the Security manual forfurther details on security.

You are NOT AUTHORIZED to changethis informationSource: Security

Explanation: A Security Administrator isviewing the profile of a user or anotherSecAdmin, and this message just reminds theadministrator that updates are not allowed(e.g., through option lists).

Action: No action required.

You are not authorized to PAINT screentable "%"Source: Screen Definer

Explanation: From the Screen Definer, yourequested painting a screen table; however,you do not have definition access to thescreen table.

Action: You can request that the OWNER(usually the CREATOR) provide you withthe required authority:

• READ to view the screen table definition

• CHANGE DEFINITION to modify thescreen table definition.

You can only specify display masks fornon-literal fieldsSource: Screen and Report Painters

Explanation: You cannot specify display masksfor literals.

Action: Delete the specified display mask.

You cannot add users; selectedUSERID(s) ignoredSource: Security

Explanation: The Security Administrator is notauthorized to add users to a group definition,so the request is ignored.

Action: No action required.

You cannot change any Groupinformation %Source: Security

Explanation: You attempted to change groupinformation when you are only authorized toview the information.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers

Page 525: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 511

You cannot DELETE this object set; it iscurrently ENABLEDSource: Security

Explanation: You attempted to delete an objectset definition, but you cannot because theobject set is enabled.

Action: You must cancel from this screen. Todelete the object set, you must first disable itby removing all the members from the enablelist.

You cannot SAVE changes; this objectset is ENABLEDSource: Security

Explanation: You tried to save an object setdefinition screen, or one of its functionscreens, and this message informs you thatthe object set cannot be updated because it isenabled.

Action: You must cancel from this screen. Toupdate the object set definition, first disablethe object set by removing all the membersfrom the object set enable list.

You do NOT have authorization toinclude user in this groupSource: Security

Explanation: In the Memberships screen of auserid profile, a Security Administrator triedto add a new group for the userid. However,the Security Administrator does not haveupdate authorization for the added group.

Action: Remove the entry from the list. TheSecurity Administrator can look at the groupdefinition and then request the owner of thegroup to include the userid in the groupdefinition.

You do NOT have securityauthorization for %Source: Menu Definer

Explanation: You have requested to view a menudefinition or save changes for a menudefinition; however, you do not have theproper security authorization.

Action: You must obtain the appropriate securityauthorization for the part of the menumentioned.

You do not have security authorizationto % this librarySource: Define Library

Explanation: You tried to look at or update alibrary definition when you do not have thesecurity authorization for that library.

Action: You can request proper authorizationfrom either the owner of the library, thesecurity administrator of the owner of thelibrary, or any security level-7 user (i.e.,someone with system administrator status).

You may not add more items to this coreinformationSource: General Table Definer

Explanation: You have requested to add anotherentry to some core information you areupdating for the MetaStor table you aredefining. The maximum number of entriesallowed for this part of the core informationhas already been reached.

Action: You cannot add more items. You canupdate another one or delete one and thenadd.

TIBCO Object Service Broker Messages Without Identifiers

Page 526: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

512 |

You may not delete this core itemSource: General Table Definer

Explanation: You have requested to delete somerequired core information.

Action: You can update this core item instead ofdeleting it.

You may not manually add fields: mustcome from copybook or DataDictionarySource: CA Datacom Table Definer

Explanation: You attempted to add a field(OFFSET=NULL); the DAT definer onlyallows to delete/edit fields generated via themetadata extract facility or cre ated in the UIDAT Table Editor.

Action: Extract the metadata for the table you aredefining (see the DATACOM shared tool) oruse the UI DAT Table Editor to create yourDAT definition o n the basis of a COBOLcopybook.

You may NOT specify non-CA-Datacom-key data (in "%") as a KEYSource: CA Datacom Table Definer

Explanation: You specified a CA-Datacom fieldthat is not part of the CA-Datacom key to bea key of the Object Service Broker DAT TableDefinition. This is not supported.

Action: You must remove the P specificationfrom the KEY column of the offending entry.

You must change screen name to "%" toDELETE from hereSource: Screen Definer

Explanation: You have changed the screen nameafter entering the Screen Definer and you arenow trying to delete.

Action: To delete the named screen, cancel andreinitiate the Screen Definer with the name ofthe screen to be deleted, or change the nameback to the Screen name you entered theDefiner with. You may then delete thisscreen.

You must fill in a name before SAVINGSource: Session Manager

Explanation: You were defining a menu andpressed <PF3> to save; however, the menu isnot named.

Action: You must name the menu before savingit. Enter the name into the field at the top ofthe menu screen.

You must have an entry for this part ofthe definitionSource: General Table Definer

Explanation: When using the generic TableDefiner, you have not specified some coreinformation which is required to define atable of this type.

Action: Supply a valid entry for the missing partof the definition.

TIBCO Object Service Broker Messages Without Identifiers

Page 527: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 513

You must have at least ONE entry toSAVE a GroupSource: Security

Explanation: You requested to save a groupdefinition, but there are no users on themembership list.

Action: Either include a member in the groupand save, or cancel.

You must have borrowing ability to usethis utilitySource: Promotion

Explanation: You must be a borrower to use thistool.

Action: Set your userid to have the ability toobtain borrowing rights on objects. You musthave a security level of 7.

You must provide a unique number foreach fieldSource: CA Datacom Table Definer

Explanation: You have not specified a uniquefield number for all of the fields in thedefinition.

Action: Correct the definition by specifying aunique field number for each field.

You must provide a valid DAT FieldName for each fieldSource: CA Datacom Table Definer

Explanation: You specified the CA-Datacom fieldname to use for the Object Service Brokerfield in the DAT Table you are defining. TheCA-Datacom field you specified is not in theCA-Datacom table you specified.

Action: Use FIELDS to determine which CA-Datacom field names can be used in this tabledefinition. Also, ensure that the CA-Datacomtable you are using (specified in the previousscreen) is the correct one.

You must provide a valid object namefor each fieldSource: General Table Definer

Explanation: You have provided a name for afield. The name is not valid. See theManaging Data manual for valid fieldnames.

Action: Replace the invalid name with a validfield name.

You must set up table % for node %Source: Promotion

Explanation: You must customize the specifiedtable for the specified node. The promotionutility needs the information in the specifiedtable in order to continue with yourrequested activity.

Action: Create an occurrence in the specifiedtable for the specified node.

TIBCO Object Service Broker Messages Without Identifiers

Page 528: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

514 |

You must specify a % before continuingSource: Table Definer

Explanation: You have not provided a value for arequired field.

Action: Specify required information and try theoperation again.

You must specify a % for that objecttypeSource: Copy Definition

Explanation: You have specified a RULE objectwithout specifying LIBRARY.

Action: You must specify the appropriateinformation before the operation cancomplete.

You must specify a REPORTFUNCTIONSource: Report Definer

Explanation: You must specify a report functionif you specify an OF FIELD, BY FIELD, orreport function SELECTION.

Action: Select a report function from theavailable list.

You must specify at least a destinationnameSource: Definition Differences

Explanation: You must specify a name in list 2 forthe copy of the object.

Action: Type in the name and/or other attributesin list2.

You must specify library NAMESource: Define Library

Explanation: You executed DEFINE_LIBRARY,but you did not specify a library name.

Action: Execute DEFINE_LIBRARY again, butprovide a library name as an argument in theexecute request, or provide a library namewhen you are prompted for one. If you wantto access an existing library and you do notknow its name, place the cursor next to theDL define library field and press <Enter>.You will see a list of libraries that you canchoose from.

You must specify the screen table thathas field "%"Source: Screen Definer

Explanation: You have entered a field name tothe SCROLL FIELD ENTRY or DEFAULTCURSOR POSITION specification, but didnot enter the name of a screen table.

Action: Enter the name of a valid screen table.

YOU MUST SPECIFY THE TYPE ANDGROUP IN ORDER TO REQUESTTHE DETAILED DISPLAY SCREENSource: S6BTLADM-Resource Management

Explanation: In order to bypass the ResourceGroup List screen and advance directly to theDetail screen for a specific resource you mustkey in the type and group name.

Action: Key in the required information and retryyour request or select the desired type andinvoke the Group List screen.

TIBCO Object Service Broker Messages Without Identifiers

Page 529: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

| 515

You should have a BODY tableSource: Report Definer

Explanation: A report should have at least onebody table in it.

Action: Create a body table.

Your userid is not logged onto CICSSource: Security

Explanation: You tried to log on from CICS usinga userid that differs from the CICS one. Dueto security restrictions, only the userid thatmatches the CICS user ID is allowed whenlogging in from CICS.

Action: Contact your security administrator orensure that your userid and CICS user ID arethe same.

TIBCO Object Service Broker Messages Without Identifiers

Page 530: TIBCO Object Service Broker · Adabas, CA Datacom, and VSAM LDS data. System Administration on the z/OS Platform The following manuals describe system administration on the z/OS platform:

516 |

Messages beginning with: Numerals

1-15 Display place holders allowed indisplay mask "%"Source: Screen and Report Painters

Explanation: You can have up to 15 display placeholders in a display mask.

Action: Decrease the number of place holders sothat it is between 1 and 15.

1 selected instance has beenUNSELECTEDSource: Unload

Explanation: In INSTANCE SELECT you haverequested to unselect any currently selectedinstances. There was one selected and it hasbeen unselected.

Action: No action required.

TIBCO Object Service Broker Messages Without Identifiers