IBM SH19-4480-01 User Manual

TME 10 Operations Planning and Control IBM

Messages and Codes

Version 2 Release 2

SH19-4480-01

TME 10 Operations Planning and Control IBM

Messages and Codes

Version 2 Release 2

SH19-4480-01

Note

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

ISO 9001 Certification

This product was developed using an ISO 9001 certified quality system. Certification has been awarded by the Italian quality system certification group, CSQ (Certification No. CISQ/CSQ 9150.IBM7). CSQ is a member of the mutually recognized organization of European assessors, ITQS, which assesses and certifies quality

systems in the field of information technology enterprises.

Second Edition (June 1998)

This is a major revision of, and obsoletes, SH19-4480-00. This edition applies to Version 2 Release 2 Modification Level 0 of TME 10 Operations Planning and Control, Program Number

5697-OPC, and to all subsequent releases and modifications until otherwise indicated in new editions or technical newsletters. See the “Summary of TME 10 OPC Version 2 Release 2 Enhancements” on page xi for the changes made to this manual. Technical changes or additions to the text and illustrations are indicated by a vertical line to the left of the change. Make sure you are using the correct edition for the level of the product.

Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below.

IBM welcomes your comments. A form for readers' comments appears at the back of this publication. If the form has been removed, address your comments to:

TME 10 OPC Information Development Rome Tivoli Laboratory IBM Italy S.p.A. Via Sciangai, 53 00144 Rome Italy

Fax Number (+39) 6 5966 2077

Internet ID: ROMERCF at VNET.IBM.COM

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

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

How This Book Is Organized ............................. vii

TME 10 OPC Publications .............................. viii

TME 10 OPC Online Books ............................. ix

Online Message Facility ............................... ix

Books About Related Products ............................. ix

Summary of TME 10 OPC Version 2 Release 2 Enhancements ........ xi

Version 2 Release 1.0 Summary ........................... xiv

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Where Messages Are Presented ............................ 1

Data Entry Errors ..................................... 2

Chapter 2. EQQATnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 3. EQQAnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 4. EQQCnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 31

| Chapter 5. EQQCLnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 6. EQQDnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 7. EQQEXnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 8. EQQEnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 9. EQQFnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter 10. EQQGnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 11. EQQHnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 12. EQQICnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 121

Chapter 13. EQQJnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 131

Chapter 14. EQQKnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 155

Chapter 15. EQQLnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 161

Chapter 16. EQQMnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 171

Chapter 17. EQQNnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 213

 Copyright IBM Corp. 1991, 1998 iii

Chapter 18. EQQOnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 229

Chapter 19. EQQPnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 231

Chapter 20. EQQQnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 235

Chapter 21. EQQRMnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 243

Chapter 22. EQQRnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 249

Chapter 23. EQQSUnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 263

Chapter 24. EQQSnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 267

Chapter 25. EQQTTnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 271

Chapter 26. EQQTnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 275

Chapter 27. EQQUnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 281

Chapter 28. EQQVnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 283

Chapter 29. EQQWLnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 291

Chapter 30. EQQWnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 295

Chapter 31. EQQXnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 327

Chapter 32. EQQYnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 385

Chapter 33. EQQZnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 405

Chapter 34. EQQnnnn Messages . . . . . . . . . . . . . . . . . . . . . . . . 437

Chapter 35. Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

Chapter 36. Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

Chapter 37. TME 10 OPC Batch Program Codes and Messages ..... 487

EQQPDLF Batch Program Condition Codes ................... 487

EQQPURGE Batch Program WTO Messages .................. 488

iv TME 10 OPC Messages and Codes

Notices

References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM’s product, program, or service may be used. Subject to IBM's valid intellectual property or other legally protectable rights, any functionally equivalent product, program, or service may be used instead of the IBM product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user’s responsibility.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing IBM Corporation 500 Columbus Avenue Thornwood, New York 10594 U.S.A.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation P.O. Box 12195 3039 Cornwallis Research Triangle Park, NC 27709-2195 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

 Copyright IBM Corp. 1991, 1998 v

Trademarks

The following terms are trademarks of Tivoli Systems or IBM Corporation in the United States or other countries or both:

ACF/VTAM AIX AIX/6000 AS/400 BookManager CICS DATABASE 2 DB2 DFSMS/MVS DFSMShsm DFSORT Extended Services for OS/2 GDDM Hiperbatch Hiperspace IBM IBMLink IMS LoadLeveler MVS/DFP MVS/ESA MVS/SP MVS/XA NetView OPC Operating System/2 OS/2 OS/390 OS/400 Personal System/2 PS/2 RACF RISC System/6000 RS/6000 SAA Sysplex Timer System/390 Systems Application

Architecture TME TME 10 VM/ESA VTAM Workplace Shell

Tivoli

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.

C-bus is a trademark of Corollary, Inc. Java and Hot Java are trademarks of Sun Microsystems, Inc. PC Direct is a trademark of Ziff Communications Company and is used by IBM

Corporation under license. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks or registered

trademarks of Intel Corporation in the United States and other countries. Other company, product, and service names which may be denoted by a double

asterisk (**), may be trademarks or service marks of others. DEC Digital Equipment Corporation

Hewlett-Packard Hewlett-Packard Corp. HP-UX Hewlett-Packard Corp. Solaris Sun Microsystems, Inc. SPARC SPARC International, Inc. SPARCstation SPARC International, Inc. Sun Sun Microsystems, Inc. SunOS Sun Microsystems, Inc. VMS Digital Equipment Corporation

vi TME 10 OPC Messages and Codes

Preface

This book describes messages issued by TME 10 Operations Planning and Control (TME 10 OPC), program number 5697-OPC. This book documents the messages issued by these features:

 The TME 10 OPC controller  The TME 10 OPC tracker  The Tracker Agent for OS/2 enabler  The Tracker Agent for OS/400 enabler  The Tracker Agent for AIX enabler  The Tracker Agent for HP-UX enabler  The Tracker Agent for Sun Solaris enabler  The Tracker Agent for SunOS enabler

|  The Tracker Agent for Digital VAX/Alpha enabler |  The Tracker Agent for Digital OpenVMS enabler |  The Tracker Agent for Pyramid MIPS ABI |  The Tracker Agent for System/390 Open Edition

Messages issued by the trackers on the non-MVS platforms are documented in the

Installation and Operation

the TME 10 OPC Workload Monitor/2 are documented in the Workload Monitor/2 dialogs. for these messages.

This book should be used by operators, system or application programmers, or by anyone who is responsible for controlling or diagnosing problems in TME 10 OPC.

TME 10 OPC Workload Monitor/2 User's Guide

How This Book Is Organized

This book contains these chapters:

Chapter 1, “Introduction” contains general information that applies to all product messages.

Chapter 2, “EQQATnn Messages” through Chapter 34, “EQQnnnn Messages” list the product messages, in alphanumeric order (A–Z, 0–9).

Chapter 35, “Abend Codes” lists the TME 10 OPC abend codes, in numeric

order. Chapter 36, “Reason Codes” lists the TME 10 OPC reason codes, in numeric

order. Chapter 37, “TME 10 OPC Batch Program Codes and Messages” lists the

codes and WTO messages generated by TME 10 OPC batch programs.

book for the Tracker Agent feature. Messages issued by

describes how to get help

 Copyright IBM Corp. 1991, 1998 vii

TME 10 OPC Publications

This book is part of an extensive TME 10 OPC library. These books can help you use TME 10 OPC more effectively:

Task Publication Order

number

Evaluating TME 10 OPC Evaluating Tracker Agents Planning TME 10 OPC Understanding TME 10 OPC Learning TME 10 OPC

concepts and terminology Starting to use the GUI

Interpreting messages and codes

Installing TME 10 OPC Customizing and tuning

TME 10 OPC Planning and scheduling the

workload Controlling and monitoring

the current plan Using Workload Monitor/2 Writing application programs Quick reference Diagnosing failures Controlling the AIX, UNIX**,

VMS, OS/390 Open Edition workload

Controlling the OS/2 and NT workload

Controlling the OS/400 workload

General Fact Sheet Tracker Agent Features Fact Sheet Licensed Program Specifications General Information Getting Started with TME 10 OPC

Getting Started with the Graphical User Interface for Application Description

Messages and Codes

Installation Guide Customization and Tuning

Planning and Scheduling the Workload

Controlling and Monitoring the Workload

Workload Monitor/2 User’s Guide Programming Interfaces Quick Reference Diagnosis Guide and Reference Tracker Agents for AIX, UNIX, VMS, OS/390 Open Edition

Installation and Operation

Tracker Agents for OS/2 and Windows NT Installation and Operation

Tracker Agent for OS/400 Installation and Operation

GH19-4370 GH19-4371 GH19-4373 GH19-4372 SH19-4481

SH19-4486

SH19-4480

SH19-4379 SH19-4380

SH19-4376

SH19-4377

SH19-4482 SH19-4378 GH19-4374 LY19-6405 SH19-4484

SH19-4483

SH19-4485

Master Index

, SH19-4375, is published for the TME 10 OPC library. A standard binder, SX80-0258, is available for your TME 10 OPC books. For each binder you order, you should also order binder inserts, GH19-4487.

Maximizing Your OPC/ESA Throughput

, SG24-2130, contains useful information for

| tuning the OPC installation.

viii TME 10 OPC Messages and Codes

TME 10 OPC Online Books

All the books in the TME 10 OPC library, except the licensed publications, are available in displayable softcopy form on CD-ROM in the following Softcopy Collection Kits:

|  MVS, SK2T-0710 |  OS/390, SK2T-6700

TME 10 OPC Messages and Codes Productivity Edition Messages and Codes Collection

You can read the softcopy books on CD-ROMs using these IBM licensed programs:

 BookManager READ/2 (program number 5601-454)  BookManager READ/DOS (program number 5601-453)  BookManager READ/6000 (program number 5765-086)

All the BookManager programs need a personal computer equipped with a CD-ROM disk drive (capable of reading disks formatted in the ISO 9660 standard) and a matching adapter and cable. For additional hardware and software information, refer to the documentation for the specific BookManager product you are using.

Updates to books between releases are provided in softcopy only.

Online Message Facility

The Online Message Facility (OMF) is an OS/2 program that provides online access to information from BookManager softcopy books. It helps you diagnose problems without interrupting your work. You can retrieve the description of a message by clicking on a message number in a Communications Manager emulator window. Additional information about OMF is available on the Messages and Codes CD-ROM.

is also available as part of

, SK2T-2068.

Online Library

Books About Related Products

These books describe IBM products that are related to TME 10 OPC:

Short Title Publication Order

Number

DFP Services for ICF MVS/DFP: Access Method Services for the Integrated

Catalog Facility DFSMS/MVS Version 1 Access Method Services for the

Integrated Catalog Facility

DFP Services for VSAM MVS/DFP: Access Method Services for VSAM Catalogs

DFSMS/MVS Version 1 Access Method Services for VSAM Catalogs

JES2 Messages MVS/ESA JES2 Version 4 Messages

MVS/ESA JES2 Version 5 Messages

JES3 Messages MVS/ESA JES3 Version 4 Messages

MVS/ESA JES3 Version 5 Messages

Preface ix

SC26-4562

SC26-4905

SC26-4570 SC26-4906

GC23-0085 GC28-1488 GC23-0091 SC28-1489

Short Title Publication Order

Number

MVS/ESA Codes MVS/ESA System Codes

MVS/ESA SP5 System Codes

MVS/ESA Messages MVS/ESA System Messages, Volume 1 (ABA-ASA)

MVS/ESA System Messages, Volume 2 (ASB-ERB) MVS/ESA System Messages, Volume 3 (GFSA-IEB) MVS/ESA System Messages, Volume 4 (IEC-IFD) MVS/ESA System Messages, Volume 5 (IGD-IZP) MVS/ESA SP5 System Messages, Volume 1 (ABA-ASA) MVS/ESA SP5 System Messages, Volume 2 (ASB-ERB) MVS/ESA SP5 System Messages, Volume 3 (GFSA-IEB) MVS/ESA SP5 System Messages, Volume 4 (IEC-IFD)

MVS/ESA SP5 System Messages, Volume 5 (IGD-IZP) NetView Messages NetView Version 2 Release 3 Messages RACF Messages and Codes Resource Access Control Facility (RACF) Version 1

Release 9 Messages and Codes SMP/E Messages System Modification Program Extended Messages and

Codes TSO/E Messages TSO/E Version 2 Messages VTAM. Messages and Codes VTAM Version 4 Release 1 for MVS/ESA Messages and

Codes

TME 10 GEM Installation and

| GC31-8474 |

User's Guide

| |

TME 10 GEM Application Policy

| GC31-5108 |

Manager User's Guide

| |

TME 10 GEM Instrumentation

| GC31-5109 |

Guide

| |

SAP R/3 User's Guide

| GC31-5147 |

Maestro Supplemental

| SK3T-3566 |

Documentation Set

TME 10 Global Enterprise Manager: Installation and

User's Guide

TME 10 Global Enterprise Manager: Application Policy

Manager User's Guide

TME 10 Global Enterprise Manager: Instrumentation

Guide

SAP R/3 User's Guide

Unison Maestro Supplemental Documentation Set

GC28-1664 GC28-1486 GC28-1656 GC28-1657 GC28-1658 GC28-1659 GC28-1660 GC28-1480 GC28-1481 GC28-1482 GC28-1483 GC28-1484 SC31-6138 SC38-1014

GC28-1108

GC28-1885 SC31-6418

x TME 10 OPC Messages and Codes

Summary of TME 10 OPC Version 2 Release 2 Enhancements

| Instrumentation for TME 10 Global Enterprise Manager | TME 10 Global Enterprise Manager (GEM) is the industry's first solution for | unifying the management of cross-platform business applications that run | businesses and make them competitive. TME 10 GEM helps you to manage | strategic applications from a unique business systems perspective, focusing | your IT resources on keeping these systems working properly and | productively. TME 10 OPC has been enhanced to support the Job | Scheduling Business System of the TME 10 GEM Systems Management | Business System. From the TME 10 GEM console, which provides a single | point of management, a TME 10 OPC user has complete control of all the | TME 10 OPC components, regardless of the platform on which they run. In | more detail, the TME 10 OPC instrumentation for TME 10 GEM enables you | to do the following:

|  Show all the TME 10 OPC components, including controllers, stand-by | controllers, OS/390 trackers, AS/400 tracker agents, TCP/IP connected | tracker agents.

|  Show the different links between the above components. This provides, | at a glance, a check on the health of the connections. For example, an | OS/390 tracker might be running but might have no connection to the | controller.

|  For each component, manage a set of status parameters (monitors) | specific to that component. These monitors might report the status of | some vital OPC controller data sets such as database, current plan, and | long-term plan)

|  Manage this set of monitors graphically. You can: | – Ask for value of the monitor

| – Be notified when the value of the monitor changes | – Associate a severity (such as normal, warning, severe, or critical) | with each monitor value

|  Start or stop TME 10 OPC trackers without logging them on. |  Know at a glance, in a sysplex environment, which is the active controller

| and which the stand-by. |  Execute commands on TME 10 OPC components, from a single point of

| control, regardless of the platform and operating system used for that | component.

| SAP R/3 support | TME 10 OPC has been enhanced to exploit the Extended Agent technology | of the TME 10 Workload Scheduler product. This technology enables | TME 10 OPC to interface with a number of third party applications that can | perform scheduling. By using this technology, you can now start and track a | SAP R/3 job from TME 10 OPC. You can also retrieve and display the job | log at the TME 10 OPC controller. This function requires the TME 10 OPC | Tracker Agent for one of the following platforms:

|  AIX |  Digital UNIX |  Sun Solaris

 Copyright IBM Corp. 1991, 1998 xi

|  Windows NT |  HP–UX

| TCP/IP communication improvements | The TCP/IP communication component that enables the controller to | communicate with the TCP/IP connected tracker agents has been | restructured to use the standard TCP/IP C–Socket interface. This change | enables TME 10 OPC for the latest OS/390 releases and provides for the | use of the standard TCP/IP features, such as the KEEPALIVE option.

| Catalog management enhancements | The logic that TME 10 OPC uses when determining which catalog | management actions to perform has been extended to manage the following | situations:

|  Some steps in a job are not executed, but are flushed. The datasets | referred to in those steps are ignored by the catalog management | function.

|  A dataset referred to with disposition NEW in one step is also referred to | in other steps. Logic to determine the action to perform in these cases | has been added to the Catalog Management function.

| Dataset Delete function (EQQDELDS) improvements | The Dataset Delete function has been enhanced to determine the correct | action when a dataset referred to with disposition NEW in one step is also | referred to in other steps. Logic to determine the correct action to perform in | these cases has been added to the Dataset Delete function. The Dataset | Delete function has also been improved to do the following:

|  Delete datasets for which an expiration date was specified. |  Issue diagnostic information when the IDCAMS DELETE command or

| the DFHSM ARCHDEL command fails to delete a dataset. | Current plan occurrence limit removal

| The maximum number of occurrences in the current plan has been increased | from 32767 to 9999999. This enhancement enables you to manage the | current plan more flexibly when you have large workloads.

| Operations in AD limit removal | You can now define up to 255 operations in each Application Description. | This enhancement provides for more flexibility in the definition of the | workload.

| AD and OI consistency check | The consistency between the Application Description and the Operator | Instruction OPC databases is now enforced by OPC. For instance, whenever | an operation is deleted the associated operator instructions is also deleted. | Some usability enhancements have also been implemented in the Application | Description dialogs when defining operator instructions. For instance, you | can now also access temporary operator instructions.

| JCL editing from Application Description dialogs | You can now customize the TME 10 OPC dialogs so that a library | management application used in the customer's environment to manage the | production jobs can be invoked from the Application Description OPC | dialogs, thus increasing user productivity. New row commands have been | added to invoke such an application from the Operation List panel while | working with an Application Description.

xii TME 10 OPC Messages and Codes

| OPC Control Language tool | The OPC Control Language (OCL) tool enables you to access and | manipulate TME 10 OPC data by using a REXX-like language. Several | macro-functions are made available that perform, in a single action, what | would require several invocations of the OPC Program Interface functions. | The OCL tool acts as an extension to the REXX language processor. | Therefore, normal REXX statements can be coded together with OCL | statements. This tool runs in a batch TSO session.

| Tracker agents | New Tracker Agents are provided to control the workload on:

|  Digital UNIX |  OS/390 Open Edition

| SmartBatch coexistence | TME 10 OPC has been extensively tested to make sure that all the features | continue to work correctly when the production workload is under SmartBatch | control.

| Other enhancements to functions |  EQQZSUBX 16 MB limit removal: because it is no longer necessary to

| move the JCL buffer below the 16 MB line before submitting it to JES2 or | JES3, this processing has been removed from TME 10 OPC.

|  To improve the robustness of TME 10 OPC, the STIMERM macro is now | invoked, wherever the STIMER macro was previously invoked.

|  TME 10 OPC Job-Submit user exit (EQQUX001) has been improved by | adding two new parameters: WorkstationID and ErrorCode. When | ErrorCode is set, TME 10 OPC will not submit the job.

|  TME 10 OPC Operation-Status-Change user exit (EQQUX007) has been | improved by adding the procstep name to the JOBAREA parameter. | This enhancement provides for fully automated problem management.

|  Debugging aids for performance problems: new statistics are now | produced by TME 10 OPC to trace all the activities performed during the | job submission process. These statistics are especially useful when you | tune your systems to maximize job throughput in TME 10 OPC. You | can dynamically activate and deactivate these statistics by means of new | MODIFY commands.

| New and changed installation exits | User exit EQQUX001 has two new parameters:

| RETCO The error code | WSNAME The workstation name of submission process

| User Exit EQQUX007 has a new field in the JobArea called procedure step | name.

| Changes to commands | The following modify commands have been added:

| CPQSTA Activates or deactivates CP lock statistic messaging | EVELIM Sets a new value for the EVELIM keyword of the JTOPTS | statement | EVESTA Activates or deactivates EVENT statistic messaging | GENSTA Activates or deactivates GS task statistic messaging

Summary of TME 10 OPC Version 2 Release 2 Enhancements xiii

| HB Issues a heartbeat message for an OPC controller or for all | trackers connected to that controller | JCLDBG Activates or deactivates the JCL debugging trace | QUELEN Sets a new value for the QUEUELEN keyword of the JTOPTS | statement | STATIM Sets a new value for the STATIM keyword of the JTOPTS | statement | STATUS Returns status information about the OPC controller and the | tracker agents connected to it. | WSASTA Activates or deactivates WSA task statistic messaging

| New and changed initialization statements | The following values have been added to the STATMSG keyword of the | JTOPTS statement:

| EVELIM Makes customizable the event number criterion for statistic | messaging. | STATIM Uses an interval time criterion to issue statistics messaging. | WSATASK Activates new statistics for WSA task.

| The following new values have been added to the SUBFAILACTION keyword | of the JTOPTS statement:

| XC, XE and XR | To specify how OPC must handle values returned by the Job | Submission Exit (EQQUX001) for the RETCO parameter.

| A new keyword has been added to the BATCHOPT statement: | MAXOCCNUM Set the maximum number of occurrences in the current

| plan for the daily planning function. | A new keyword has been added to the JTOPTS statement: | MAXOCCNUM Set the maximum number of occurrences in the Current

| Plan for the dialog, ETT, Automatic Recovery and PIF | functions.

| Changes to programming interfaces | The OPC Programming Interface (PIF) has been extended as follows:

|  A new subsegment has been added to the Workstation record called the | Workstation Access Method Information (WSAM).

|  A new keyword, ADOICHK, has been added to the OPTIONS request to | activate the consistency check between Application Description and | Operator Instruction records.

Version 2 Release 1.0 Summary

TME 10 OPC Version 2 Release 1 became generally available in March 1997. Major enhancements compared to OPC/ESA Release 3.1 are described in the following sections.

Graphical User Interface for Application Description

The GUI enables a user to create, change, and view application descriptions stored on the OPC host through an interactive interface on OS/2.

xiv TME 10 OPC Messages and Codes

Tracker agents

New Tracker Agents are provided to control the workload on:

|  Digital OpenVMS

 Pyramid MIPS ABI

Shared parm library in Sysplex environment

MVS controllers and trackers can share common controller and tracker initialization statements and started task JCLs, making it easier to install many OPC subsystems inside an MVS/ESA sysplex environment.

Controller configuration in Sysplex environment

TME 10 OPC support of MVS/ESA sysplex (base and parallel) has been extended to enable any one of many cloned controllers on different MVS images to switch from standby to active status. An OPC controller is started on each member of the XCF group. The first potential controller that becomes active is the active controller and the others are standby controllers. If the active controller fails, a standby controller running in another MVS/ESA image of the sysplex environment takes over automatically as the active controller.

Single system image

This enhancement allows OPC TSO dialog users and PIF users to be on a different MVS/ESA image from the OPC controller. Dialog users and PIF applications can also be on MVS systems outside the sysplex where the controller runs. Remote communication is based on APPC.

Extended dialog filter

The dialog filter has been extended to allow more specific search arguments and to define the interpretation of wildcard characters.

Reparsing of NOERROR

New operator commands allow the operator to dynamically update the NOERROR table using the NOERROR initialization statements defined by the OPC PARMLIB member, and to read the statements from a member of the EQQPARM DD concatenated libraries. In addition a new initialization statement allows the inclusion of NOERROR statements from members of the EQQPARM DD concatenated libraries.

PIF extension

Program Interface has been greatly extended to support almost all OPC database record types.

Job tracking log

This enhancement provides to user exit 11 job tracking records on which an effective disaster recovery procedure can be based. The customer through exit 11 receives job tracking records, and can send this data to a remote controller that, in case of failure of the active controller, will take over as controller.

GMT clock support improvement

The GMTOFFSET keyword in the OPCOPTS statement lets the user define an offset between the GMT time set in the MVS system and the actual GMT time. The OPC controller uses the GMT clock to validate an OPC Tracker Agent trying to connect; this improvement addresses the need of some users to have the MVS GMT clock independent of the actual GMT time, while keeping the ability to use Tracker Agents.

Summary of TME 10 OPC Version 2 Release 2 Enhancements xv

Batch command interface tool

A batch command interface tool is supplied to perform most of the actions supported by the PIF interface by means of a batch command interface.

New and changed initialization statements

Initialization statements have been added and changed in TME 10 OPC Version 2. The following sections summarize the differences.

The INCLUDE statement

Added in TME 10 OPC Version 2, the INCLUDE statement lets you reduce the size of the parameter library member that contains the OPCOPTS and JTOPTS statements and reduce the associated maintenance activities.

Table 1. The INCLUDE Statement

Keyword Short description

NOERROR Specifies to read NOERROR information

from other members of the EQQPARM library.

The INIT statement

Added in OPC/ESA Release 3.1, the INIT statement lets you define run-time options for processing requests from a PIF application. These settings override the values set by the INTFOPTS statement in EQQPARM. The statement is defined in a second parameter file that is identified by the EQQYPARM DD statement in the JCL procedure of the PIF application. In TME 10 OPC Version 2 the LUNAME keyword has been added.

Table 2. The INIT Statement

Keyword Short description

CWBASE Specifies the origin for the century window

used by the PIF application

HIGHDATE Specifies the high date presented to the

PIF application in valid-to fields

LUNAME Specifies a server or controller LU name

for the PIF application

SUBSYS Identifies the TME 10 OPC subsystem

controller

TRACE Specifies the level of trace information to

write to the diagnostic file.

Changes to commands

These modify commands have been added:

NEWNOERR Requests that the NOERROR statements be reprocessed. NOERRMEM

(member) Requests that the NOERROR information be

read from the specified member.

xvi TME 10 OPC Messages and Codes

The MODIFY command has been extended to accept stop and start of the server started tasks:

F ssname, P=SERV S ssname, P=SERV

Changes to programming interfaces

The Programming Interface is extended as follows: UPDATE is supported for calendars, periods, workstations, and all

workstations closed. BROWSE and UPDATE are supported for ETT and special resources. The LIST request has been extended to support a new keyword,

MATCHTYP, to specify whether generic search arguments (* and % are to be treated as normal characters.

A new keyword, ADVERS, has been added to the OPTIONS request, to activate the support of AD versioning.

New and changed installation exits

Table 3 summarizes the changes to installation exits in TME 10 OPC Version 2.

Table 3. Changes to Installation Exits

Exit name Short description of change

EQQUX001 TME 10 OPC Version 2 now also supports the

addressing modes RMODE(24) and AMODE(31).

EQQUX011 Sample job tracking log write exit.

Messages

Messages have been changed, deleted, and added in TME 10 OPC Version

2. Refer to

TME 10 OPC Messages and Codes

for the complete message text and descriptions. Note that in Version 2 the message text and explanations refer to the product as OPC/ESA.

Summary of TME 10 OPC Version 2 Release 2 Enhancements xvii

xviii TME 10 OPC Messages and Codes

Chapter 1. Introduction

This manual explains all the error, warning, and information messages, as well as the user abend codes and reason codes, that TME 10 OPC issues.

The messages are listed in alphanumeric order by message identifier. To help you find messages, the range of messages on a particular page is shown at the top of the page.

Message Format

TME 10 OPC messages have the following formats:

EQQ

FnnnC Text

where:

or EQQ

FFnnC Text

or EQQ

nnnnC Text

EQQ Means that the message was issued by TME 10 OPC. The

EQQ prefix is used for all TME 10 OPC messages.

FF nn, nnn C

Text

, or

nnnn

Identifies the function that issued the message. Is the message number Is the message severity code, with one of these values:

I Information message. Processing continues and, in

W Warning message. Processing continues and, in most

E Error message. Processing terminates, and action by

Is the message text, which can vary in length. The text may contain message variables that are substituted at run time or when the message is issued. In this book, message variables are represented by asterisks (***) or

Where Messages Are Presented

The messages described in this book can be presented in two ways:

 In the “long message” area on an Interactive System Productivity Facility (ISPF)

panel. This message is displayed if you enter HELP after a message is issued in the “short message” area on the panel. The ISPF long message area is normally the third line on the ISPF panel. All TME 10 OPC dialog messages that are presented in this area have mixed-case text.

almost all cases, no action by the user is required.

cases, no action by the user is required.

the user is required.

italic

text.

 As one or more records in the TME 10 OPC message-log dataset. The

message log is defined by the EQQMLOG DD statement. The message log is used by the TME 10 OPC started task and by TME 10 OPC's own batch jobs. Any message in the message log can also be displayed as a write-to-operator message.

 Copyright IBM Corp. 1991, 1998 1

The format of a TME 10 OPC message printed in the message log dataset is:

mm/dd HH.MM.SS msgnum TEXT

where:

Introduction

mm/dd

Is the current date, given as a 2-digit month number and a 2-digit day-of-month number. For example, 02/03 means February 3.

HH.MM.SS

Is the current time-of-day:

HH Is the hour, starting from midnight, in the range 00–23. MM Is the minute of the current hour, in the range 00–59. SS Is the second of the current minute, in the range 00–59.

msgnum

Is the message number in the format described in “Message Format” on page 1.

TEXT

Is the message text in uppercase.

An example of messages in the TME 10 OPC message log follows:

à ð

. ð2/21 16.31.11 EQQZðð5I TME 1ð OPC SUBTASK EVENT WRITER IS BEING STARTED ð2/21 16.31.13 EQQZðð5I TME 1ð OPC SUBTASK VTAM I/O TASK IS BEING STARTED ð2/21 16.31.14 EQQZðð5I TME 1ð OPC SUBTASK JOB SUBMIT TASK IS BEING STARTED ð2/21 16.31.16 EQQZðð5I TME 1ð OPC SUBTASK DATA ROUTER TASK IS BEING STARTED ð2/21 16.31.17 EQQZð13I NOW PROCESSING PARAMETER LIBRARY MEMBER EWOPTS ð2/21 16.31.19 EQQZð15I INIT STATEMENT: EWTROPTS HOLDJOB(NO) ð2/21 16.31.26 EQQZð15I INIT STATEMENT: STEPEVENTS(ALL) ð2/21 16.31.28 EQQZð15I INIT STATEMENT: RETCODE(LAST) ð2/21 16.31.29 EQQZð15I INIT STATEMENT: EWSEQNO(1) ð2/21 16.31.3ð EQQZð16I RETURN CODE FOR THIS STATEMENT IS: ðððð ð2/21 16.31.31 EQQZð14I MAXIMUM RETURN CODE FOR PARAMETER MEMBER EWOPTS IS: ððð ð2/21 16.31.32 EQQVðð1I NCF APPLICATION STARTED ð2/21 16.31.33 EQQFðð1I DATA ROUTER TASK INITIALIZATION IS COMPLETE

Data Entry Errors

A data entry error occurs in the dialog when you enter an invalid value or do not enter a value for a required field.

System action:

invalid or missing. If you enter the HELP command or press the Help PF key, the system displays a longer message telling you what to enter. The cursor appears on the panel in the field where the error is located, and the system waits for you to respond.

User response:

you omitted. Then press Enter.

2 TME 10 OPC Messages and Codes

The system displays a short message telling you that something is

Type over the incorrect values, or type in the required values that

EQQAT00I  EQQAT05I

Chapter 2. EQQATnn Messages

EQQAT00I THE APPC TRACKER TASK HAS STARTED Explanation: The APPC tracker task has started successfully. TME 10 OPC will start this task if the ROUTOPTS

initialization statement defines one or more APPC destinations.

System action: TME 10 OPC normal processing continues. System programmer response: None.

EQQAT01I THE APPC TRACKER TASK HAS ENDED Explanation: The APPC tracker task has been requested to stop and is ending normally. System action: TME 10 OPC normal processing continues. System programmer response: None.

EQQAT02E THE APPC TRACKER TASK HAS BEEN CONTACTED BY AN UNKNOWN DESTINATION: Explanation: The APPC tracker task has recognized an inbound attach request from a destination that is not defined

in the ROUTOPTS initialization statement. System action: The APPC tracker task will free all resources allocated to this APPC conversation. The partner

program that is attempting to start the conversation will get a failing return code from the APPC service routine. System programmer response: If the APPC tracker task should support the destination specified in this message,

then the ROUTOPTS initialization statement should be updated and the TME 10 OPC subsystem should be restarted.

EQQAT03E A QUEUE ELEMENT ON THE APPC TRACKER TASK QUEUE IS NOT RECOGNIZED:

ELEM

Explanation: An invalid queue element has been found on the APPC tracker task’s work queue. System action: The incorrect queue element is returned to the APPC tracker task’s free queue without any further

processing. System programmer response: Save the TME 10 OPC message log dataset containing this message and then

contact your IBM representative.

EQQAT04E THE APPC TRACKER TASK RECEIVED INVALID IDENTIFICATION DATA FROM DESTINATION: Explanation: The initial data received from a partner APPC program is not valid. System action: The APPC tracker task will free all resources allocated to this APPC conversation. The partner

program sending incorrect data will get a failing return code from the APPC service routine. System programmer response: Verify that the correct partner program has been started on the remote destination

and that the program is at a supported maintenance level. After making corrections, restart the partner program.

EQQAT05I A CONVERSATION WITH AN APPC TRACKER AT DESTINATION LU HAS ENDED.

SEND

RECORDS WERE TRANSMITTED,

Explanation: A conversation with an APPC tracker is ending normally. System action: TME 10 OPC normal processing continues. System programmer response: None.

RCV

RECORDS WERE RECEIVED

EQQAT06E  EQQAT11E

EQQAT06E THE APPC TRACKER TASK RECEIVED UNRECOGNIZED DATA FROM DESTINATION: Explanation: Data received from a partner APPC program is not valid. System action: The APPC tracker task will free all resources allocated to this APPC conversation. The partner

and that the program is at a supported maintenance level. After making corrections, restart the partner program.

EQQAT07E NO CONVERSATION FOUND FOR OUTBOUND DATA ON THE APPC TRACKER TASK QUEUE:

ELEM

Explanation: A queue element has been found on the APPC tracker task’s work queue which is not addressed to any currently active APPC conversation.

System action: The queue element is returned to the APPC tracker task’s free queue without any further processing.

System programmer response: Save the TME 10 OPC message log dataset containing this message and then contact your IBM representative.

EQQAT08E THE APPC TRACKER TASK CANNOT START, TRACKER FEATURE IS NOT INSTALLED Explanation: The APPC tracker task could not locate a required load module. System action: The APPC tracker task terminates. System programmer response: If the APPC tracker feature is not installed, then the ROUTOPTS initialization

statement should not specify the APPC keyword. If the APPC tracker feature is installed, then make sure that the TME 10 OPC subsystem can access corresponding load module libraries. After making appropriate corrections, restart the TME 10 OPC subsystem.

EQQAT09E THE APPC TRACKER TASK RECEIVED INVALID IDENTIFICATION DATA FROM DESTINATION: LU.

VALIDATION RETURN CODE IS

Explanation: The initial data received from a partner APPC program is not valid. System action: The APPC tracker task will free all resources allocated to this APPC conversation. The partner

and that the program is at a supported maintenance level. After making corrections, restart the partner program.

EQQAT10E SEND TO DESTINATION: LU FAILED WITH RETCODE RC IMMEDIATELY Explanation: The APPC tracker task received an immediate nonzero return code from the APPC send data service

routine.

System action: The APPC tracker task will terminate this APPC conversation and free all allocated resources. System programmer response: Verify that the partner program on the remote destination is at a supported