User`s guide | Acer 630 Laptop 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.
 Copyright International Business Machines Corporation 1991, 1998. All rights reserved.
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 .
Trademarks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface . . . . . . . . . . . .
How This Book Is Organized
TME 10 OPC Publications .
TME 10 OPC Online Books
Online Message Facility .
Books About Related Products
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary of TME 10 OPC Version 2 Release 2 Enhancements
Version 2 Release 1.0 Summary . . . . . . . . . . . . . . . . . . .
Chapter 1. Introduction . . . .
Message Format . . . . . . . . .
Where Messages Are Presented
Data Entry Errors . . . . . . . . .
|
v
vi
vii
vii
viii
. ix
. ix
. ix
. . . . . . . .
. . . . . . . .
xi
xiv
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1
1
2
Chapter 2. EQQATnn Messages
. . . . . . . . . . . . . . . . . . . . . . . . . . .
3
Chapter 3. EQQAnnn Messages
. . . . . . . . . . . . . . . . . . . . . . . . . . .
9
Chapter 4. EQQCnnn Messages
. . . . . . . . . . . . . . . . . . . . . . . . . .
31
. . . . . . . . . . . . . . . . . . . . . . . . .
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
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5. EQQCLnnn Messages
 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
EQQPDLF Batch Program Condition Codes . . . . . . . . . . . . . .
EQQPURGE Batch Program WTO Messages . . . . . . . . . . . . .
iv
TME 10 OPC Messages and Codes
. . . . .
. . . . .
. . . . .
487
487
488
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
AS/400
DATABASE 2
DFSMShsm
GDDM
IBM
LoadLeveler
MVS/SP
OPC
OS/390
PS/2
RS/6000
System/390
TME
VTAM
AIX
BookManager
DB2
DFSORT
Hiperbatch
IBMLink
MVS/DFP
MVS/XA
Operating System/2
OS/400
RACF
SAA
Systems Application
Architecture
TME 10
Workplace Shell
AIX/6000
CICS
DFSMS/MVS
Extended Services for OS/2
Hiperspace
IMS
MVS/ESA
NetView
OS/2
Personal System/2
RISC System/6000
Sysplex Timer
Tivoli
VM/ESA
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
Hewlett-Packard
HP-UX
Solaris
SPARC
SPARCstation
Sun
SunOS
VMS
vi
TME 10 OPC Messages and Codes
Digital Equipment Corporation
Hewlett-Packard Corp.
Hewlett-Packard Corp.
Sun Microsystems, Inc.
SPARC International, Inc.
SPARC International, Inc.
Sun Microsystems, Inc.
Sun Microsystems, Inc.
Digital Equipment Corporation
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
The
The
The
The
The
The
The
The
The
The
The
TME 10 OPC controller
TME 10 OPC tracker
Tracker Agent for OS/2 enabler
Tracker Agent for OS/400 enabler
Tracker Agent for AIX enabler
Tracker Agent for HP-UX enabler
Tracker Agent for Sun Solaris enabler
Tracker Agent for SunOS enabler
Tracker Agent for Digital VAX/Alpha enabler
Tracker Agent for Digital OpenVMS enabler
Tracker Agent for Pyramid MIPS ABI
Tracker Agent for System/390 Open Edition
Messages issued by the trackers on the non-MVS platforms are documented in the
Installation and Operation book for the Tracker Agent feature. Messages issued by
the TME 10 OPC Workload Monitor/2 are documented in the Workload Monitor/2
dialogs. TME 10 OPC Workload Monitor/2 User's Guide describes how to get help
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.
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.
 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
General Fact Sheet
GH19-4370
Evaluating Tracker Agents
Tracker Agent Features Fact Sheet
GH19-4371
Planning TME 10 OPC
Licensed Program Specifications
GH19-4373
Understanding TME 10 OPC
General Information
GH19-4372
Learning TME 10 OPC
concepts and terminology
Getting Started with TME 10 OPC
SH19-4481
Starting to use the GUI
Getting Started with the Graphical User Interface for Application
Description
SH19-4486
Interpreting messages and
codes
Messages and Codes
SH19-4480
Installing TME 10 OPC
Installation Guide
SH19-4379
Customizing and tuning
TME 10 OPC
Customization and Tuning
SH19-4380
Planning and scheduling the
workload
Planning and Scheduling the Workload
SH19-4376
Controlling and monitoring
the current plan
Controlling and Monitoring the Workload
SH19-4377
Using Workload Monitor/2
Workload Monitor/2 User’s Guide
SH19-4482
Writing application programs
Programming Interfaces
SH19-4378
Quick reference
Quick Reference
GH19-4374
Diagnosing failures
Diagnosis Guide and Reference
LY19-6405
Controlling the AIX, UNIX**,
VMS, OS/390 Open Edition
workload
Tracker Agents for AIX, UNIX, VMS, OS/390 Open Edition
Installation and Operation
SH19-4484
Controlling the OS/2 and NT
workload
Tracker Agents for OS/2 and Windows NT
Installation and Operation
SH19-4483
Controlling the OS/400
workload
Tracker Agent for OS/400
Installation and Operation
SH19-4485
A 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 is also available as part of Online Library
Productivity Edition Messages and Codes Collection, SK2T-2068.
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.
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
SC26-4562
DFSMS/MVS Version 1 Access Method Services for the
Integrated Catalog Facility
SC26-4905
MVS/DFP: Access Method Services for VSAM Catalogs
SC26-4570
DFSMS/MVS Version 1 Access Method Services for VSAM
Catalogs
SC26-4906
MVS/ESA JES2 Version 4 Messages
GC23-0085
MVS/ESA JES2 Version 5 Messages
GC28-1488
MVS/ESA JES3 Version 4 Messages
GC23-0091
MVS/ESA JES3 Version 5 Messages
SC28-1489
DFP Services for VSAM
JES2 Messages
JES3 Messages
Preface
ix
Short Title
Publication
Order
Number
MVS/ESA Codes
MVS/ESA System Codes
GC28-1664
MVS/ESA SP5 System Codes
GC28-1486
MVS/ESA System Messages, Volume 1 (ABA-ASA)
GC28-1656
MVS/ESA System Messages, Volume 2 (ASB-ERB)
GC28-1657
MVS/ESA System Messages, Volume 3 (GFSA-IEB)
GC28-1658
MVS/ESA System Messages, Volume 4 (IEC-IFD)
GC28-1659
MVS/ESA System Messages, Volume 5 (IGD-IZP)
GC28-1660
MVS/ESA SP5 System Messages, Volume 1 (ABA-ASA)
GC28-1480
MVS/ESA SP5 System Messages, Volume 2 (ASB-ERB)
GC28-1481
MVS/ESA SP5 System Messages, Volume 3 (GFSA-IEB)
GC28-1482
MVS/ESA SP5 System Messages, Volume 4 (IEC-IFD)
GC28-1483
MVS/ESA SP5 System Messages, Volume 5 (IGD-IZP)
GC28-1484
NetView Messages
NetView Version 2 Release 3 Messages
SC31-6138
RACF Messages and Codes
Resource Access Control Facility (RACF) Version 1
Release 9 Messages and Codes
SC38-1014
SMP/E Messages
System Modification Program Extended Messages and
Codes
GC28-1108
TSO/E Messages
TSO/E Version 2 Messages
GC28-1885
VTAM. Messages and Codes
VTAM Version 4 Release 1 for MVS/ESA Messages and
Codes
SC31-6418
|
|
TME 10 GEM Installation and
User's Guide
TME 10 Global Enterprise Manager: Installation and
User's Guide
GC31-8474
|
|
TME 10 GEM Application Policy
Manager User's Guide
TME 10 Global Enterprise Manager: Application Policy
Manager User's Guide
GC31-5108
|
|
TME 10 GEM Instrumentation
Guide
TME 10 Global Enterprise Manager: Instrumentation
Guide
GC31-5109
|
SAP R/3 User's Guide
SAP R/3 User's Guide
GC31-5147
|
|
Maestro Supplemental
Documentation Set
Unison Maestro Supplemental Documentation Set
SK3T-3566
MVS/ESA Messages
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
WSNAME
|
|
User Exit EQQUX007 has a new field in the JobArea called procedure step
name.
|
|
|
|
|
|
|
The error code
The workstation name of submission process
Changes to commands
The following modify commands have been added:
CPQSTA
EVELIM
EVESTA
GENSTA
Activates or deactivates CP lock statistic messaging
Sets a new value for the EVELIM keyword of the JTOPTS
statement
Activates or deactivates EVENT statistic messaging
Activates or deactivates GS task statistic messaging
Summary of TME 10 OPC Version 2 Release 2 Enhancements
xiii
|
|
|
|
|
|
|
|
|
|
HB
JCLDBG
QUELEN
STATIM
STATUS
WSASTA
|
|
|
Issues a heartbeat message for an OPC controller or for all
trackers connected to that controller
Activates or deactivates the JCL debugging trace
Sets a new value for the QUEUELEN keyword of the JTOPTS
statement
Sets a new value for the STATIM keyword of the JTOPTS
statement
Returns status information about the OPC controller and the
tracker agents connected to it.
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
|
|
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
|
A new keyword has been added to the JTOPTS statement:
|
|
|
MAXOCCNUM
STATIM
WSATASK
|
|
Makes customizable the event number criterion for statistic
messaging.
Uses an interval time criterion to issue statistics messaging.
Activates new statistics for WSA task.
Set the maximum number of occurrences in the current
plan for the daily planning function.
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
NOERRMEM
Requests that the NOERROR statements be reprocessed.
(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:
EQQFnnnC Text or
EQQFFnnC Text or
EQQnnnnC Text
where:
EQQ
Means that the message was issued by TME 10 OPC. The
EQQ prefix is used for all TME 10 OPC messages.
F or FF
Identifies the function that issued the message.
nn, nnn, or nnnn
Is the message number
C
Is the message severity code, with one of these values:
Text
I
Information message. Processing continues and, in
almost all cases, no action by the user is required.
W
Warning message. Processing continues and, in most
cases, no action by the user is required.
E
Error message. Processing terminates, and action by
the user is required.
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 italic text.
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.
Ÿ 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
Introduction
The format of a TME 10 OPC message printed in the message log dataset is:
mm/dd HH.MM.SS msgnum TEXT
where:
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
ð2/21
ð2/21
ð2/21
ð2/21
ð2/21
ð2/21
ð2/21
ð2/21
ð2/21
ð2/21
ð2/21
ð2/21
..
.
ð
16.31.11
16.31.13
16.31.14
16.31.16
16.31.17
16.31.19
16.31.26
16.31.28
16.31.29
16.31.3ð
16.31.31
16.31.32
16.31.33
EQQZðð5I
EQQZðð5I
EQQZðð5I
EQQZðð5I
EQQZð13I
EQQZð15I
EQQZð15I
EQQZð15I
EQQZð15I
EQQZð16I
EQQZð14I
EQQVðð1I
EQQFðð1I
TME 1ð OPC SUBTASK EVENT WRITER
IS BEING STARTED
TME 1ð OPC SUBTASK VTAM I/O TASK
IS BEING STARTED
TME 1ð OPC SUBTASK JOB SUBMIT TASK IS BEING STARTED
TME 1ð OPC SUBTASK DATA ROUTER TASK IS BEING STARTED
NOW PROCESSING PARAMETER LIBRARY MEMBER EWOPTS
INIT STATEMENT: EWTROPTS HOLDJOB(NO)
INIT STATEMENT:
STEPEVENTS(ALL)
INIT STATEMENT:
RETCODE(LAST)
INIT STATEMENT:
EWSEQNO(1)
RETURN CODE FOR THIS STATEMENT IS: ðððð
MAXIMUM RETURN CODE FOR PARAMETER MEMBER EWOPTS IS: ððð
NCF APPLICATION STARTED
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: The system displays a short message telling you that something is
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: Type over the incorrect values, or type in the required values that
you omitted. Then press Enter.
2
TME 10 OPC Messages and Codes
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: LU
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: LU
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, RCV RECORDS WERE RECEIVED
Explanation: A conversation with an APPC tracker is ending normally.
System action: TME 10 OPC normal processing continues.
System programmer response: None.
 Copyright IBM Corp. 1991, 1998
3
EQQAT06E Ÿ EQQAT11E
EQQAT06E THE APPC TRACKER TASK RECEIVED UNRECOGNIZED DATA FROM DESTINATION: LU
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
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.
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 RC
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.
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
maintenance level. After making corrections, restart the partner program.
EQQAT11E SEND TO DESTINATION: LU FAILED WITH RETCODE RC ASYNCHRONOUSLY
Explanation: The APPC tracker task received a 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
maintenance level. After making corrections, restart the partner program.
4
TME 10 OPC Messages and Codes
EQQAT12E Ÿ EQQAT21E
EQQAT12E RECEIVE AND WAIT FROM DESTINATION: LU FAILED WITH RETCODE RC IMMEDIATELY
Explanation: The APPC tracker task received an immediate nonzero return code from the APPC receive and wait
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
maintenance level. After making corrections, restart the partner program.
EQQAT13E RECEIVE AND WAIT FROM DESTINATION: LU FAILED WITH RETCODE RC ASYNCHRONOUSLY
Explanation: The APPC tracker task received a nonzero return code from the APPC receive and wait 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
maintenance level. After making corrections, restart the partner program.
EQQAT14E IDLE CONVERSATION DELAY ERROR FOR DESTINATION: LU
Explanation: The APPC tracker task received send permission from a remote partner program without any data and
without the minimum delay required for an idle conversation.
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
maintenance level. After making corrections, restart the partner program.
EQQAT15E PREPARE TO RECEIVE FROM DESTINATION: LU FAILED WITH RETCODE RC IMMEDIATELY
Explanation: The APPC tracker task received an immediate nonzero return code from the APPC prepare to receive
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
maintenance level. After making corrections, restart the partner program.
EQQAT16E PREPARE TO RECEIVE FROM DESTINATION: LU FAILED WITH RETCODE RC
ASYNCHRONOUSLY
Explanation: The APPC tracker task received a nonzero return code from the APPC prepare to receive 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
maintenance level. After making corrections, restart the partner program.
EQQAT21E WRONG NUMBER OF PERIODS IN THE ADDR VALUE, VALUE
Explanation: The ADDR keyword of the APPCROUT initialization statement must specify a value containing one
period.
System action: Processing of the current APPCROUT statement terminates with a nonzero return code. This will
cause TME 10 OPC initialization to fail.
System programmer response: Either remove or correct the APPCROUT statement and restart the TME 10 OPC
system.
Chapter 2. EQQATnn Messages
5
EQQAT22E Ÿ EQQAT30E
EQQAT22E THE PERIOD IN THE ADDR VALUE, VALUE, IS INCORRECTLY PLACED
Explanation: The ADDR keyword of the APPCROUT initialization statement must specify a value containing one
period, and that period cannot be placed more than eight characters after the beginning of the value or more than
eight characters before the end of the value.
System action: Processing of the current APPCROUT statement terminates with a nonzero return code. This will
cause TME 10 OPC initialization to fail.
System programmer response: Either remove or correct the APPCROUT statement and restart the TME 10 OPC
system.
EQQAT23E THE VALUE OF THE ADDR KEYWORD IS MISSING OR TOO SHORT
Explanation: The ADDR keyword of the APPCROUT initialization statement must specify a value that is at least
three characters long.
System action: Processing of the current APPCROUT statement terminates with a nonzero return code. This will
cause TME 10 OPC initialization to fail.
System programmer response: Either remove or correct the APPCROUT statement and restart the TME 10 OPC
system.
EQQAT24E THE ADDR KEYWORD IS MISSING
Explanation: The current APPCROUT initialization statement does not contain an ADDR keyword.
System action: Processing of the current APPCROUT statement terminates with a nonzero return code. This will
cause TME 10 OPC initialization to fail.
System programmer response: Either remove or correct the APPCROUT statement and restart the TME 10 OPC
system.
EQQAT25E THE WORKSTATIONS KEYWORD IS MISSING
Explanation: The current APPCROUT initialization statement does not contain a WORKSTATIONS keyword.
System action: Processing of the current APPCROUT statement terminates with a nonzero return code. This will
cause TME 10 OPC initialization to fail.
System programmer response: Either remove or correct the APPCROUT statement and restart the TME 10 OPC
system.
EQQAT26E WORKSTATION WSN HAS BEEN SPECIFIED MORE THAN ONCE IN A WORKSTATIONS
KEYWORD. THIS IS NOT SUPPORTED
Explanation: The WORKSTATIONS keyword in current APPCROUT initialization statement contains a workstation
name that has already been specified in a WORKSTATIONS keyword. This is a duplicate definition that is not
supported.
System action: Processing of the current APPCROUT statement terminates with a nonzero return code. This will
cause TME 10 OPC initialization to fail.
System programmer response: Either remove or correct the APPCROUT statement and restart the TME 10 OPC
system.
EQQAT30E APPC KEYWORD VALUE, VAL1, IS TOO LONG (OR MISSING)
Explanation: A workstation destination name specified as a value of the APPC keyword of the ROUTOPTS
statement is incorrect. The destination name is required and must not be longer than eight characters.
System action: Processing of the APPC keyword continues. Message EQQAT34E will be issued when all
destinations have been processed.
System programmer response: Either remove or correct the invalid destination and restart the TME 10 OPC
system.
6
TME 10 OPC Messages and Codes
EQQAT31E Ÿ EQQAT34E
EQQAT31E APPC KEYWORD VALUE, VAL2, MUST CONTAIN EXACTLY ONE PERIOD
Explanation: A network address specified as a value of the APPC keyword of the ROUTOPTS statement is
incorrect. The network address is required and must be specified as netid.netlu where the netid and netlu names
cannot contain periods.
System action: Processing of the APPC keyword continues. Message EQQAT34E will be issued when all
destinations have been processed.
System programmer response: Either remove or correct the invalid destination and restart the TME 10 OPC
system.
EQQAT32E THE PERIOD IN THE APPC KEYWORD VALUE, VAL2, IS INCORRECTLY PLACED
Explanation: A network address specified as a value of the APPC keyword of the ROUTOPTS statement is
incorrect. The network address is required and must be specified as netid.netlu where the netid and netlu names
cannot be longer than eight characters.
System action: Processing of the APPC keyword continues. Message EQQAT34E will be issued when all
destinations have been processed.
System programmer response: Either remove or correct the invalid destination and restart the TME 10 OPC
system.
EQQAT33E APPC KEYWORD VALUE, VAL2, IS MISSING OR TOO SHORT
Explanation: A network address specified as a value of the APPC keyword of the ROUTOPTS statement is
incorrect. The network address is required and must be specified as netid.netlu where both netid and netlu are
required.
System action: Processing of the APPC keyword continues. Message EQQAT34E will be issued when all
destinations have been processed.
System programmer response: Either remove or correct the invalid destination and restart the TME 10 OPC
system.
EQQAT34E AT LEAST ONE APPC DESTINATION IS INCORRECTLY DEFINED
Explanation: The APPC keyword of the ROUTOPTS statement contains one or more incorrectly defined APPC
destinations.
System action: Processing of the current ROUTOPTS statement terminates with a nonzero return code. This will
cause TME 10 OPC initialization to fail.
System programmer response: Review earlier error messages to determine the incorrectly defined destination.
Either remove or correct the invalid destination and restart the TME 10 OPC system.
Chapter 2. EQQATnn Messages
7
8
TME 10 OPC Messages and Codes
EQQA000E Ÿ EQQA009I
Chapter 3. EQQAnnn Messages
EQQA000E YOU ARE NOT AUTHORIZED TO ACCESS THE AD DATABASE
Explanation: You have attempted to access the application description (AD) database, but you are not authorized to
access it. Or, you do not have access authority to at least one of the following TME 10 OPC resources that are used
together with the AD database: the calendar database, the workstation description database, or in some cases, the
long-term plan dataset.
System action: The request is rejected.
User response: If you require access, contact your security administrator.
EQQA003E SELECTED PREDECESSOR IS NOT EXTERNAL
Explanation: The predecessor you selected is not external. When defining an external dependency, you must
specify the application ID of the external predecessor before selecting to describe it.
System action: The system waits for you to respond.
User response: Specify the application ID of the external predecessor.
EQQA004E NO MATCHING APPLICATION DESCRIPTION(S) FOUND
Explanation: No application description matched the generic or nongeneric search criteria you specified to generate
a list of applications.
System action: The system waits for you to respond.
User response: Retry using new selection criteria.
EQQA005E NO MATCHING APPLICATION DESCRIPTION FOUND
Explanation: You selected an application that does not have a matching application description. In a list of
applications in either the browse or list function, the application you selected was not found. The application may
have been deleted or modified after the list of application entries was generated.
System action: The request is rejected.
User response: Return to the application selection criteria panel and press ENTER to generate a fresh list of
applications.
EQQA006I NO RUNCYCLES FOUND FOR THIS APPLICATION
Explanation: You have attempted to display the run cycles of an application for which no run cycles have been
specified.
System action: The request is rejected.
User response: None.
EQQA009I NO PREDECESSORS FOUND FOR THIS OPERATION
Explanation: You have attempted to display the predecessors of an operation for which no predecessors have been
specified.
System action: The request is rejected.
User response: None.
 Copyright IBM Corp. 1991, 1998
9
EQQA010E Ÿ EQQA017E
EQQA010E INVALID PARAMETER INPUT TO MODULE MOD
Explanation: This message indicates a programming error.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Contact your IBM representative.
EQQA011I THE APPLICATION IS CREATED
Explanation: The application has been created and saved in the application description database.
System action: None.
User response: None.
EQQA012I THE SELECTED APPLICATION IS MODIFIED
Explanation: The selected application has been modified and saved in the application description database.
System action: None.
User response: None.
EQQA013I THE SELECTED APPLICATION IS COPIED
Explanation: The selected application has been copied and the copy has been saved in the application description
database.
System action: None.
User response: None.
EQQA014I THE SELECTED APPLICATION IS DELETED
Explanation: The selected application has been deleted from the application description database.
System action: None.
User response: None.
EQQA015E THE NUMBER OF INTERNAL PREDECESSORS IS TOO LARGE
Explanation: You specified too many internal predecessors.
System action: The system waits for you to respond.
User response: Delete one or more internal predecessors.
EQQA016E THE NUMBER OF EXTERNAL PREDECESSORS IS TOO LARGE
Explanation: You specified too many external predecessors.
System action: The system waits for you to respond.
User response: Delete one or more external predecessors.
EQQA017E THE NUMBER OF SPECIAL RESOURCES IS TOO LARGE
Explanation: You specified too many special resources.
System action: The system waits for you to respond.
User response: Delete one or more special resources.
10
TME 10 OPC Messages and Codes
EQQA018E Ÿ EQQA103E
EQQA018E OP OP HAS AN EXTERNAL PRED WS EWS, WHICH IS NOT FOUND
Explanation: Operation op has an external predecessor workstation (ews) that does not exist in the workstation
description database.
System action: The system waits for you to respond.
User response: Enter correct data.
EQQA021I NO SPECIAL RESOURCES FOUND FOR THIS OPERATION
Explanation: You have attempted to display the special resources of an operation for which no special resources
have been defined.
System action: None.
User response: None.
EQQA022E THE APPLICATION STATUS SPECIFIED IS NOT VALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid application statuses you can specify as selection criteria are: A for active, P for pending, or blank for both active
and pending.
EQQA023E PRIORITY MUST BE A NUMBER FROM 1 - 9
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA024E STATUS MUST BE OCHCACT OR OCHCPEND
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA025E INPUT DATA IN FIELD IS REQUIRED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA101E THE VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The name of a variable table contains 1 to 16 alphanumeric characters, where the first character is alphabetic.
EQQA102E AN APPLICATION WITH THIS ID ALREADY EXISTS
Explanation: You have attempted to create an application, but the application ID that you specified already exists in
the application description database.
System action: The system waits for you to respond.
User response: Enter a unique application ID. If you want to create versions of an already existing application, you
should use the copy function.
EQQA103E THE APPLICATION IS BEING UPDATED BY ANOTHER USER
Explanation: Another user is currently updating the application you want to update.
System action: The system waits for you to respond.
User response: Try to update the application later.
Chapter 3. EQQAnnn Messages
11
EQQA104E Ÿ EQQA116E
EQQA104E THE PERIOD NAME DOES NOT EXIST IN THE CALENDAR
Explanation: The period name you specified is not defined in the calendar database.
System action: The system waits for you to respond.
User response: Enter an existing period name, or use the Calendar dialog to define the period name.
EQQA105E YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE
Explanation: You have attempted to refer to a JCL variable table. To do this, you need read authority to the JCL
variable table database.
System action: The system waits for you to respond.
User response: Contact your security administrator if you need to refer to JCL variable table names.
EQQA106E DEADLINE PRECEDES INPUT ARRIVAL TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The deadline must be later than the input arrival time.
EQQA107E WORK STATION DOES NOT EXIST IN WS DESCRIPTION DATA BASE
Explanation: The workstation name you specified is not defined in the workstation description database.
System action: The system waits for you to respond.
User response: Enter an existing workstation name, or use the Work Station Description dialog to define the work
station name.
EQQA108W WHEN UPDATING WS NAME, OPR, EXT AND INT ITEMS MUST ALL BE SELECTED
Explanation: To obtain a correct result, you must select all of:
OPR
INT
EXT
Work station name
Predecessor ws name
Predecessor ws name
This does not prevent you from updating only one of the items.
System action: The system waits for you to continue.
User response: Select all three items.
EQQA109E YOU HAVE ENTERED AN INVALID VALUE IN THE CATALOG MANAGEMENT FIELD.
Explanation: The only valid values in this field are Y (Yes), N (No), and D (Deferred).
System action: The system waits for you to respond.
User response: Enter a valid value.
EQQA110E JOBNAME REQUIRED FOR JOB SETUP, PRINT, OR COMPUTER WS
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A job name is required for an operation at a job setup, print, or computer workstation.
EQQA116E DURATION TIME IS NOT SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
12
TME 10 OPC Messages and Codes
EQQA117E Ÿ EQQA124I
EQQA117E 24.00 IS NOT ALLOWED AS INPUT ARRIVAL TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid input arrival times are 00.00 through 23.59.
EQQA118E 00.00 IS NOT ALLOWED AS DEADLINE TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid deadline times are 00.01 through 24.00.
EQQA119W SPECIFIED OPERATION DEADLINE EARLIER THAN APPLICATION INPUT ARRIVAL
Explanation: You specified an operation deadline that is earlier than the application input arrival time for the
application. This does not prevent you from saving the application description as it is.
System action: The operation deadline is accepted and the system waits for you to respond.
User response: Enter END to save the application description or make the deadline and the input arrival time
consistent.
EQQA120I SPECIFIED OPERATION INPUT ARRIVAL LATER THAN APPLICATION DEADLINE
Explanation: You specified an operation input arrival time that is later than the deadline time for the application.
This does not prevent you from saving the application description as it is.
System action: The input arrival time for the operation is accepted and the system waits for you to respond.
User response: Enter END to save the application description or make the operation input arrival and the application
deadline consistent.
EQQA121E SPECIFIED OPERATION DEADLINE EARLIER THAN OP INPUT ARRIVAL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The deadline time must be later than the input arrival time.
EQQA122I SPECIFIED APPLICATION INPUT ARRIVAL LATER THAN AN OP INPUT ARRIVAL
Explanation: The specified application input arrival time you specified is later than an operation input arrival time
defined in the OPER table. This does not prevent you from saving the application description as it is.
System action: The input arrival time for the application is accepted and the system waits for you to respond.
User response: Enter END to save the application description, or make the input arrival times consistent.
EQQA123I SPECIFIED OP INPUT ARRIVAL EARLIER THAN APPLICATION INPUT ARRIVAL
Explanation: The operation input arrival time you specified is earlier than the input arrival time for the application.
This does not prevent you from saving the application description as it is.
System action: The input arrival time for the operation is accepted and the system waits for you to respond.
User response: Enter END to save the application description, or make the input arrival times consistent.
EQQA124I SPECIFIED OP DEADLINE LATER THAN APPLICATION DEADLINE
Explanation: The operation deadline time you specified is later than the deadline time for the application. This does
not prevent you from saving the application description as it is.
System action: The deadline time for the operation is accepted. The system waits for you to respond.
User response: Enter END to save the application description, or make the deadline times consistent.
Chapter 3. EQQAnnn Messages
13
EQQA125I Ÿ EQQA202E
EQQA125I NO APPLICATION INPUT ARRIVAL TIME SPECIFIED YET
Explanation: No application input arrival time is specified for this application. This does not prevent you from saving
the application description as it is.
System action: The times specified for the operation are accepted. The system waits for you to respond.
User response: Enter END to save the application description, or make the deadline times consistent.
EQQA126E SPECIFY AT LEAST ONE RUNDAY
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA127E OUT-OF-EFFECT-FROM DATE PRECEDES IN-EFFECT-FROM DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The out-of-effect-from date for a run cycle must be later than the in-effect-from date.
EQQA134E SUPPRESS IF LATE = YES ALLOWED ONLY WHEN TIME DEPENDENT = YES
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The SUPPRESS IF LATE option may be YES only when the TIME DEPENDENT option is specified as YES.
EQQA135E THE SMOOTHING FACTOR MUST BE A NUMBER 0 - 999
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA136E THE FEEDBACK LIMIT MUST BE A NUMBER 100 - 999
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA137E DEADLINE WTO IS NOT DEFINED OR INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid deadline WTO options are Y for Yes, and N for No.
| EQQA200E OPERATION NUMBER MUST BE 1 - 255
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA201E THE VARIABLE TABLE IS NOT DEFINED TO OPC/ESA
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You have tried to define a variable table ID that does not exist in TME 10 OPC's database.
EQQA202E THE RUN CYCLE TYPE IS INVALID, ENTER EITHER N, X, R OR E
Explanation: Valid run cycle types are:
N
X
R
E
Normal offset-based run cycles.
Negative offset-based run cycles.
Regular rule-based run cycles.
Exception rule-based run cycles.
System action: The request is rejected.
User response: Change the run cycle type to one of the supported values.
14
TME 10 OPC Messages and Codes
EQQA203E Ÿ EQQA210E
EQQA203E THE FREE DAY RULE SPECIFICATION IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A valid free day rule specification is any of the following:
E
1
2
3
4
Free days excluded.
Run on the closest workday before the free day.
Run on the closest workday after the free day.
Run on the free day.
Do not run at all.
EQQA204E YOU HAVE ENTERED AN INVALID VALUE IN THE CATALOG MANAGEMENT FIELD.
Explanation: The only valid values in this field are Y (Yes), N (No), and D (Deferred).
System action: The system waits for you to respond.
User response: Enter a valid value.
EQQA205E THE RUN CYCLE TYPE MUST BE SPECIFIED
Explanation: Valid run cycle types are:
N
X
R
E
Normal offset-based run cycles.
Negative offset-based run cycles.
Regular rule-based run cycles.
Exception rule-based run cycles.
System action: The request is rejected.
User response: Change the run cycle type to one of the supported values.
EQQA206E THE FREE DAY RULE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A valid free day rule specification is any of the following:
E
1
2
3
4
Free days excluded.
Run on the closest workday before the free day.
Run on the closest workday after the free day.
Run on the free day.
Do not run at all.
EQQA207E AN IN-EFFECT-FROM DATE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA208E AN OUT-OF-EFFECT-FROM DATE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA209E THE RUN DAY OFFSET MUST BE A NUMBER FROM -999 TO -1 OR 1 TO 999
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA210E THE PRINT OPTION MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 3. EQQAnnn Messages
15
EQQA211E Ÿ EQQA223E
EQQA211E THE PRINT OPTION CHARACTER IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid print option characters are A for always, and C for conditionally.
EQQA212E WHEN TIME DEPENDENT = YES, SUPPRESS IF LATE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The SUPPRESS IF LATE option must be specified when the TIME DEPENDENT option is specified as YES.
EQQA213E THE WS RESOURCE AMOUNT SPECIFIED MUST BE A NUMBER 0 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA214E THE JOB OPTION CHARACTER SPECIFIED IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid job option characters are Y for yes, and N for no.
EQQA215E THE NUMBER OF PARALLEL SERVERS MUST BE 1 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA216E THE INPUT ARRIVAL DAY MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA217E THE INPUT ARRIVAL DAY MUST BE A NUMBER 0 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA218E THE INPUT ARRIVAL TIME MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA219E THE NUMBER OF PARALLEL SERVERS MUST BE 1 FOR CPU OPERATIONS
Explanation: Operations on a computer workstation can only use one parallel server.
System action: The panel is redisplayed and the dialog waits for you to change the number of parallel servers.
User response: Change the number of parallel servers to 1.
EQQA220E THE DEADLINE DAY MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA221E THE DEADLINE DAY OFFSET SPECIFIED MUST BE A NUMBER 0 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA222E THE DEADLINE TIME MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
| EQQA223E JOBNAME MISSING. THE JCL EDIT/BROWSE FUNCTION NEEDS A JOBNAME.
| Explanation: The JCL edit/browse option can only be called if a jobname has been specified.
| System action: The panel is redisplayed with this error message.
| User response: Specify a jobname.
16
TME 10 OPC Messages and Codes
EQQA226E Ÿ EQQA238E
EQQA226E THE OPERATION NUMBER MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA228E THE SPECIFIED SPECIAL RESOURCE HELD OPTION IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid special resource held options are S for shared, and X for exclusive.
EQQA229W OFFSET WRKOFF IS GREATER THAN PERIOD INTERVAL WRKINT
Explanation: The number you specified for a positive or negative run day offset is greater than the period interval
value. If the period is type A, no occurrences will be created in the LTP for this offset. If the period type is W, the
message is issued as a warning but occurrences can still be created in the LTP.
System action: The system waits for you to respond.
User response: Check if the offset value will provide the desired run dates. Correct the value if required. If LTP
occurrences should be created, and the period type is A, you must change either the period interval value or the run
cycle offset value. Press the END key to save the offset values.
EQQA230E THE VALID RESPONSE IS Y OR N FOLLOWED BY ENTER KEY
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Y deletes the application; N cancels the deletion of the application.
EQQA231E A PERIOD NAME MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA232E UP TO 24 (12 POSITIVE AND 12 NEGATIVE) RUNDAY OFFSETS ARE ALLOWED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA233E THE SPECIFIED HIGHEST RETURN CODE MUST BE A NUMBER 0 - 4095
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA234E THE APPLICATION ID IS NOT SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA235E THE FIRST CHARACTER IN APPLICATION ID MUST BE ALPHABETIC
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA236E THERE IS AN INVALID CHARACTER IN THE APPLICATION ID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
An application ID can be made up of the following valid characters: A through Z, 0 through 9, and national characters
(that is, #, $, and @).
EQQA237E ENTER THE OWNER ID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA238E THE PRIORITY MUST BE A NUMBER FROM 1 TO 9
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 3. EQQAnnn Messages
17
EQQA239E Ÿ EQQA247E
EQQA239E ENTER THE STATUS, A OR P
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A stands for active, P for pending.
EQQA240E SPECIFY A VALID-FROM DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA241E THE MAXIMUM 4 ACTIVE VERSIONS ALREADY EXIST
Explanation: You have attempted to enter an active version of an application description but the maximum four
active versions of the application description already exist in the application description database.
System action: The system waits for you to respond.
User response: Reenter with a new application ID, valid-from data, or status; or delete one of the four active
versions.
EQQA242E THE MAXIMUM 4 PENDING VERSIONS ALREADY EXIST
Explanation: You have attempted to enter a pending version of an application description but the maximum four
pending versions of the application description already exist in the application description database.
System action: The system waits for you to respond.
User response: Reenter with a new application ID, valid-from data, or status; or delete one of the four pending
versions.
EQQA243E A PENDING VERSION CANNOT BE COPIED
Explanation: You have attempted to copy a pending version of the application description but only an active version
can be copied.
System action: The request is rejected and the system waits for you to respond.
User response: Select an active version to copy.
EQQA244E APPLICATION ID, STATUS, OR VALID-FROM MUST BE CHANGED
Explanation: In the copy function, one of the three key fields (application ID, status, or valid-from key fields) must be
changed to create a new version of an existing application description, or a new application description.
System action: The system waits for you to respond.
User response: Change one of the three key fields.
EQQA245E THE RUN DAY OFFSET TABLE CONTAINS DUPLICATES
Explanation: The list of run days cannot contain duplicate offsets.
System action: The system waits for you to respond.
User response: Use the row command D to delete the duplicate run day offsets, or change the duplicates.
EQQA246E SPECIFY A WORK STATION NAME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA247E THE OPERATION TABLE CONTAINS DUPLICATE OPERATION NUMBERS
Explanation: The list of operations cannot contain duplicate operation numbers.
System action: The system waits for you to respond.
User response: Use the row command D to delete the duplicate operation numbers, or change the duplicates.
18
TME 10 OPC Messages and Codes
EQQA248E Ÿ EQQA254E
EQQA248E THE PREDECESSOR TABLE CONTAINS DUPLICATE PREDECESSORS
Explanation: The list of predecessors cannot contain duplicate predecessors.
System action: The system waits for you to respond.
User response: Use the row command D to delete the duplicate predecessors, or change the duplicates.
EQQA249E THE SPECIAL RESOURCE TABLE CONTAINS DUPLICATE RESOURCES
Explanation: The list of special resources cannot contain duplicate resources.
System action: The system waits for you to respond.
User response: Use the row command D to delete the duplicate resources, or change the duplicates.
EQQA250I AD DOES NOT EXIST IN DATA BASE
Explanation: The specified external predecessor application does not exist in the application description database.
This does not prevent you from saving the application as it is.
System action: The system waits for you to respond.
User response: Enter END to save the external predecessor application, or change the external predecessor
application.
EQQA251E AD DOES NOT EXIST IN DATA BASE, ENTER WS NAME
Explanation: The specified external predecessor application does not exist in the application description database,
so the predecessor workstation name cannot be picked up. Therefore, you must specify the predecessor workstation
name.
System action: The system waits for you to respond.
User response: Enter the workstation name of the external predecessor.
EQQA252I PRED OP DOES NOT EXIST IN PREDECESSOR APPLICATION
Explanation: The specified external predecessor operation does not exist in the external predecessor application.
This does not prevent you from saving the application as it is.
System action: The system waits for you to respond.
User response: Enter END to save the external predecessor operation, or change the external predecessor
operation.
EQQA253E PRED OP DOES NOT EXIST IN PREDECESSOR APPLICATION, ENTER WS NAME
Explanation: The specified external predecessor operation does not exist in the external predecessor application, so
the predecessor workstation name cannot be picked up. Therefore, you must specify the predecessor workstation
name.
System action: The system waits for you to respond.
User response: Enter the predecessor workstation name.
EQQA254E PRINT OPERATION OP MAY HAVE ONLY ONE CPU PREDECESSOR
Explanation: The print operation number (op) can have only one CPU internal predecessor.
System action: The system waits for you to respond.
User response: Delete all except one of the internal predecessors.
Chapter 3. EQQAnnn Messages
19
EQQA255E Ÿ EQQA265E
EQQA255E JOB SETUP OP OP MUST HAVE THE SAME JOBNAME AS A CPU SUCCESSOR
Explanation: The job setup operation number (op) must have the same job name as any of its CPU successors.
System action: The system waits for you to respond.
User response: Enter a valid CPU successor job name.
EQQA256E PRINT OP OP MUST HAVE THE SAME JOBNAME AS THE CPU PREDECESSOR
Explanation: The print operation number (op) must have the same job name as its CPU predecessor.
System action: The system waits for you to respond.
User response: Enter a valid CPU predecessor job name.
EQQA257E THIS VERSIONS VALID-FROM DATE CAN NOT PRECEDE MSGVALF
Explanation: The application valid-from date for a previously defined application description version has been
modified. The valid-from date now falls within the validity period of another version of this application description.
System action: The system waits for you to respond.
User response: Change the valid-from date so that it is later than the date specified in MSGVALF. Review the
validity periods for versions of this application. If a new version is required for the date you specified, you can copy a
version of the application description and specify the required valid-from date.
EQQA260E SAME DATE SPECIFIED FOR IN-EFFECT-FROM AND OUT-OF-EFFECT-FROM
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The out-of-effect-from date must be later than the in-effect-from date.
EQQA261E NO MORE THAN 12 ITEMS CAN BE SPECIFIED
Explanation: The print function can handle up to 12 print items at a time.
System action: The system waits for you to respond.
User response: Delete print items so that the total does not exceed 12.
EQQA262E NO MORE THAN 5 ITEMS CAN BE SELECTED
Explanation: No more than five sort items can be selected to be part of the cross reference list.
System action: The system waits for you to respond.
User response: Delete sort items so that the total does not exceed five.
EQQA263E THE SORT ORDER SPECIFIED IS NOT A NUMBER 1 - 5
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA264E THE SPECIFIED SORT ORDER CONTAINS DUPLICATE DIGITS
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA265E THE SPECIFIED SORT ORDER SEQUENCE IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The digits representing the sort order must be continuous and start with the digit 1.
20
TME 10 OPC Messages and Codes
EQQA266E Ÿ EQQA278E
EQQA266E YOU ARE NOT AUTHORIZED TO READ THE OI DATA BASE
Explanation: You have attempted to read the operator instruction database, but you are not authorized to read it.
System action: The system waits for you to respond.
User response: Contact your security administrator if you require access to the OI database.
EQQA267E YOU ARE NOT AUTHORIZED TO UPDATE THE OI DATA BASE
Explanation: You have attempted to update the operator instruction (OI) database, but you are not authorized to
update it.
System action: The system waits for you to respond.
User response: Contact your security administrator if you require update authority to the OI database.
EQQA271E THERE IS AN INVALID CHARACTER IN JOBNAME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A job name can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that
is, #, $, and @). The first character must be alphabetic or national, the remaining characters can be alphabetic,
numeric, and national characters.
EQQA272E THE FIRST CHARACTER IN GROUP ID MUST BE ALPHABETIC
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA273E THERE IS AN INVALID CHARACTER IN GROUP ID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A group ID can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that
is, #, $, and @).
EQQA274E THE FIRST CHARACTER IN JOBNAME MUST BE ALPHABETIC
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA275E THE WS RESOURCE AMOUNT MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA276E THE NUMBER OF PARALLEL SERVERS MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA277E THE FILTER NUMBER FNR IS NOT SUPPORTED
Explanation: This message indicates a programming error.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Contact your IBM representative.
EQQA278E THE VERIFICATION NUMBER VNR IS NOT SUPPORTED
Explanation: This message indicates a programming error.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Contact your IBM representative.
Chapter 3. EQQAnnn Messages
21
EQQA279E Ÿ EQQA286E
EQQA279E THE TABLE OF UPDATES CONTAINS DUPLICATE UPDATES
Explanation: The table of pending updates cannot contain duplicate updates.
System action: The system waits for you to respond.
User response: Use the row command D to delete the duplicate updates, or change the duplicates.
EQQA280E THE TABLE CONTAINS DUPLICATE ROWS
Explanation: The table cannot contain duplicate rows.
System action: The system waits for you to respond.
User response: Use the row command D to delete the duplicate row items, or change the duplicates.
EQQA281E NO MORE THAN 25 PENDING UPDATES CAN BE SPECIFIED IN THIS SESSION
Explanation: It is not allowed to specify more than 25 pending updates in this session.
System action: The system waits for you to respond.
User response: Use the row command D to delete pending updates, or cancel the latest pending updates.
EQQA282E THE SPECIFIED BATCH JOB TYPE OPTION IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A valid batch job type is T for trial run, or U for updating run.
EQQA283E NO UPDATE AUTHORITY TO APPLICATION DESCRIPTION DATA BASE
Explanation: You have attempted to update the application description database, but you are not authorized to
update it.
System action: The system waits for you to respond.
User response: Contact your security administrator if you need to update the application description database.
EQQA284E YOU ARE NOT AUTHORIZED TO READ THE CALENDAR DATA BASE
Explanation: You have attempted to read the calendar database, but you are not authorized to read it.
System action: The system waits for you to respond.
User response: Contact your security administrator if you need access to the calendar database.
EQQA285E YOU ARE NOT AUTHORIZED TO READ THE WS DESCRIPTION DATA BASE
Explanation: You have attempted to read the workstation (WS) description database, but you are not authorized to
read it.
System action: The system waits for you to respond.
User response: If you need to access the WS description database, contact your security administrator.
EQQA286E THE DATA SPECIFIED IS TOO LONG
Explanation: The data you have specified for mass updating is longer than the maximum length allowed for the data
item.
System action: The system waits for you to respond.
User response: Check the maximal data length allowed and enter the correct data.
22
TME 10 OPC Messages and Codes
EQQA287E Ÿ EQQA299I
EQQA287E THE CONVERSION NUMBER CNR IS NOT SUPPORTED
Explanation: This message indicates a programming error.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Contact your IBM representative.
EQQA288E THE RESCALE FACTOR IS NOT SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA289E THE RESCALE FACTOR MUST BE A NUMBER 0 - 999
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA290E VALID DATA IS A NUMBER 1 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA291E VALID DATA IS A NUMBER 0 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA292E VALID DATA IS A NUMBER 100 - 999
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA293E VALID DATA IS A NUMBER 0 - 999
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA294E PERIOD NAME FILTER IS NOT RELEVANT FOR CURRENT DATA ITEM
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA295E JOBNAME FILTER IS NOT RELEVANT FOR CURRENT DATA ITEM
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA296E WS NAME FILTER IS NOT RELEVANT FOR CURRENT DATA ITEM
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA297E NEITHER JOBNAME NOR WS NAME IS RELEVANT FOR CURRENT DATA ITEM
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA298E FILTER CRITERIA ARE NOT RELEVANT FOR OWNER ID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA299I DATA SET NAME GIVEN; SPECIFIED APPLICATION ID(S) IGNORED
Explanation: When the dataset name is specified, it is not necessary to specify the application IDs.
System action: None.
User response: None.
Chapter 3. EQQAnnn Messages
23
EQQA300E Ÿ EQQA308E
| EQQA300E VALID DATA IS A NUMBER 1 - 255
| Explanation: Data entry error; “Data Entry Errors” on page 2.
EQQA301E THERE MUST BE AT LEAST ONE OPERATION IN AN APPLICATION
Explanation: The application has no operations. You must specify at least one operation.
System action: The system waits for you to respond.
User response: Specify one or more operations for the application.
EQQA302E PREDECESSOR OPERATION PO IS NOT FOUND FOR OPERATION OP
Explanation: The predecessor operation (predecessor operation number po) was not found for the operation
(operation number op). An internal predecessor operation must exist within the application.
System action: The system waits for you to respond.
User response: Enter an existing operation number.
EQQA303E OPERATION OP IS NOT CONNECTED TO APPLICATION
Explanation: The operation (operation number op) has no predecessor or successor connections to the application.
System action: The system waits for you to respond.
User response: Enter or change an internal predecessor to establish a correct application link.
EQQA304E OPERATION OP SPECIFIES WORK STATION OPWS, WHICH IS NOT FOUND
Explanation: The operation (operation number op) of this application specifies a workstation (workstation name
opws), which was not found in the workstation description database.
System action: The system waits for you to respond.
User response: Enter an existing workstation name, or use the workstation description dialog to define the
workstation name.
EQQA305E DEPENDENCIES INCLUDING OPERATION OP FORM A LOOP
Explanation: A loop was detected in the operation (operation number op) dependency network which must be
corrected. For example, operation 10 has operation 5 its as predecessor, and operation 5 has operation 10 its as
predecessor.
System action: The system waits for you to respond.
User response: Correct the loop found with these internal predecessors.
EQQA306E VALID-FROM DATE LATER THAN VALID-TO DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
When modifying an application, the valid-from date cannot be changed to a date later than the valid-to date.
EQQA307E OPERATION INPUT ARRIVAL TIME MUST BE SPECIFIED FOR A TIME JOB
Explanation: Data entry error; see “Data Entry Errors” on page 2.
An operation input arrival time must be specified if the time-dependent job option is specified as YES.
EQQA308E JOB SETUP OPERATION OP MUST HAVE A CPU SUCCESSOR
Explanation: The job setup operation (operation number op) must have a CPU successor operation.
System action: The system waits for you to respond.
User response: Enter the job setup operation number as a CPU predecessor number.
24
TME 10 OPC Messages and Codes
EQQA309E Ÿ EQQA400E
EQQA309E PRINT OPERATION OP MUST HAVE A CPU PREDECESSOR
Explanation: The print operation (operation number op) must have a CPU predecessor operation.
System action: The system waits for you to respond.
User response: Enter a CPU operation number as the predecessor number.
EQQA310E FIELD FORMAT SPECIFIED AS DBCS BUT INPUT NOT BRACKETED DBCS
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA311E DBCS PART OF BRACKETED FIELD IS BLANK
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA314E THE OWNER ID IS NOT SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA315E FORMAT OF OWNER ID SPECIFIED AS DBCS BUT INPUT NOT BRACKETED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA316E DBCS PART OF BRACKETED OWNER ID FIELD IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA317E DBCS FIELD CONTAINS UNPAIRED SHIFT-OUT / SHIFT-IN CHARACTER
Explanation: The field indicated by the cursor contains one or more superfluous shift-out or shift-in characters.
System action: The data is rejected.
User response: Correct data and reenter.
EQQA318E DBCS PART CONTAINS INVALID DBCS-CHARACTER
Explanation: The field indicated by the cursor contains out-of-range DBCS characters. With the exception of DBCS
blank, X'4040', each byte must be within the range X'41' - X'FE'.
System action: The data is rejected.
User response: Correct data and reenter.
EQQA319E DBCS PART CONTAINS AN ODD NUMBER OF BYTES
Explanation: The field indicated by the cursor is specified as a DBCS field, and requires two bytes per character.
System action: The data is rejected.
User response: Correct data and reenter.
EQQA400E NO MATCHING JOB DESCRIPTION(S) FOUND
Explanation: No job descriptions were found matching the generic or non-generic search criteria that you specified
to generate a list of jobs.
System action: The system waits for you to respond.
User response: Try again, with different selection criteria.
Chapter 3. EQQAnnn Messages
25
EQQA401E Ÿ EQQA409I
EQQA401E NO MATCHING JOB DESCRIPTION FOUND
Explanation: The job that you selected from a list does not have a matching job description. The job may have
been deleted or modified after the list of job entries was generated.
System action: The request is rejected.
User response: Return to the job selection criteria panel and press Enter to generate a fresh list of jobs.
EQQA402I NO RUNCYCLES FOUND FOR THIS JOB
Explanation: You tried to display the run cycles for a job for which no run cycles have been specified.
System action: The request is rejected.
User response: None.
EQQA403I THE JOB IS CREATED
Explanation: The job has been created and saved as a job description.
System action: None.
User response: None.
EQQA404I THE SELECTED JOB IS MODIFIED
Explanation: The job has been modified and saved as a job description.
System action: None.
User response: None.
EQQA405E THE WS SPECIFIED IS NOT A CPU WS OR A GENERAL WS WITH WTO SET
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA406E A JOB WITH THIS ID ALREADY EXISTS
Explanation: You tried to create a job with an ID that already exists in the AD database.
System action: The system waits for you to respond.
User response: Enter a unique job ID. If you want to create a new version of an existing job, use the copy function.
EQQA407E THE JOB IS BEING UPDATED BY ANOTHER USER
Explanation: Another user is currently updating the job that you want to update.
System action: The system waits for you to respond.
User response: Try again later.
EQQA408E THE JOBNAME HAS NOT BEEN SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA409I THE SELECTED JOB IS DELETED
Explanation: The selected job has been deleted from the job description database.
System action: None.
User response: None.
26
TME 10 OPC Messages and Codes
EQQA410E Ÿ EQQA500E
EQQA410E THE JOB DIALOG CANNOT BE USED WHEN DBCS IS DEFINED FOR APPLID
Explanation: You have tried to enter the job description dialog but DBCS bracketed input has been defined for
application IDs in your installation. The application ID of job descriptions must be the same as the job name. Job
names cannot be entered in DBCS bracketed format.
System action: The panel is redisplayed with this error message.
User response: Use the application description dialog instead.
EQQA411E WORK STATION MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The workstation pointed to by the cursor must be entered.
EQQA412E WORK STATION SPECIFIED IS NOT A VALID JCL PREPARATION WORK STATION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The workstation must be a workstation with the JCL preparation indicator set to Y.
EQQA413E WORK STATION SPECIFIED IS NOT A VALID MANUAL WORK STATION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The workstation must be a MANUAL workstation.
EQQA414E 24.00 NOT ALLOWED AS A FROM-RUN TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA415E NO PREDECESSORS FOUND THAT MATCH SELECTION CRITERIA
Explanation: You tried to select predecessors for a job. No predecessors were found with the specified selection
criteria.
System action: The request is rejected.
User response: None.
EQQA416E 00.00 NOT ALLOWED AS A TO-RUN TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQA418E FROM-RUN TIME MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Either a run time has been entered, or run cycles are missing. Therefore, a from run time must be specified.
EQQA419E INTERNAL PREDECESSORS ARE NOT ALLOWED FOR JDS
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The application ID must be completed for a predecessor if you are currently defining a job.
EQQA500E GROUP DEFINITION CANNOT HAVE OPERATIONS
Explanation: A group definition cannot contain operations.
System action: The system waits for you to respond.
User response: Change application type to A if operations are to be defined in this application.
Chapter 3. EQQAnnn Messages
27
EQQA501W Ÿ EQQA507I
EQQA501W GROUP DEFINITION APPLGRID COULD NOT BE FOUND IN AD FILE
Explanation: The current application description references an application group definition that cannot be found in
the AD database. Either you entered the wrong name or the application group has not yet been created or you are
not authorized to reference it. If you want to, and if you are authorized, you can save the current application
description while it references an application group that does not exist. Such an application description will not be
used to create occurrences in the Long Term Plan.
System action: The system waits for you to respond.
User response: Enter the correct group definition ID, or create the referenced group definition, if you want the
application description to be selected by Long Term Plan programs.
EQQA502E GROUP DEFINITION ID FIELD CAN BE FILLED IN ONLY WHEN NO RUN CYCLES EXIST
Explanation: You cannot specify a group definition ID when run cycles already exist.
System action: The system waits for you to respond.
User response: Either erase the data in the group definition ID field or delete the run cycles for the application.
EQQA503E GROUP DEFINITION CANNOT BELONG TO ANOTHER GROUP
Explanation: You can specify a group definition ID only when the application type is A.
System action: The system waits for you to respond.
User response: Change the application type to A or erase the group definition ID field.
EQQA504E APPLICATION TYPE MUST BE OCHCSTN, OCHCGRP OR BLANK
Explanation: The selection criteria you have specified contains an invalid application type.
System action: The system waits for you to respond.
User response: Specify A (applications), G (group definitions), or blank to select both applications and group
definitions.
EQQA505E TYPE MUST BE OCHCSTN OR OCHCGRP
Explanation: You have specified an invalid application type. Valid application types are A (application) and G (group
definition).
System action: The system waits for you to respond.
User response: Enter one of the supported types.
EQQA506I RUN COMMAND NOT ALLOWED. APPLICATION IN A GROUP CONTAINS NO RUN CYCLES
Explanation: An application that references a group definition for run cycle information does not itself contain run
cycles.
System action: The request is rejected.
User response: None.
EQQA507I OPER COMMAND NOT ALLOWED. A GROUP DEFINITION DOES NOT HAVE OPERATIONS
Explanation: A group definition (application type=G) does not contain operations.
System action: The request is rejected.
User response: None.
28
TME 10 OPC Messages and Codes
EQQA508E Ÿ EQQA515E
EQQA508E RUN CYCLES ARE NOT ALLOWED FOR A JOB DESCRIPTION IN A GROUP
Explanation: A job description that references a group definition for run cycle information cannot itself contain run
cycles.
System action: The system waits for you to respond.
User response: Either erase the data in the group definition ID field or delete the run cycles for this job description.
EQQA509I NO RUN CYCLES FOR A JOB DESCRIPTION IN A GROUP
Explanation: A job description that references a group definition for run cycle information cannot itself contain run
cycles.
System action: The request is rejected.
User response: None.
EQQA510E PRIORITY CANNOT BE SPECIFIED FOR A GROUP DEFINITION
Explanation: You cannot specify priority for a group definition.
System action: The system waits for you to respond.
User response: Erase the data in the priority field.
EQQA511E CALENDAR CANNOT BE SPECIFIED FOR AN APPLICATION IN A GROUP
Explanation: A calendar ID cannot be specified for an application that references a group definition for run cycle
information.
System action: The system waits for you to respond.
User response: Either erase the data in the calendar ID field or erase the data in the group definition ID field.
EQQA512E GROUP DEFINITION CANNOT BELONG TO ANOTHER GROUP
Explanation: Group definitions can be specified only when the application type is A (application) or blank (both
application and group definition).
System action: The system waits for you to respond.
User response: Change type to A or blank, or erase the data in the group definition ID field.
EQQA513I COMMAND NOT VALID FOR A GROUP DEFINITION
Explanation: Calculate and print rundays, or Modify LTP can be requested only for applications.
System action: The request is rejected.
User response: None.
EQQA514W GROUP DEFINITION HAS NO RUN CYCLES.
Explanation: The group definition contains no run cycle information. Applications that reference this group definition
will not be automatically included in the long term plan.
System action: The system waits for you to respond.
User response: If you want to use this group definition to schedule applications, specify run cycle information.
EQQA515E CALENDAR CANNOT BE SPECIFIED FOR A JOB IN A GROUP
Explanation: A calendar ID cannot be specified for a job that references a group definition for run cycle information.
System action: The system waits for you to respond.
User response: Either erase the data in the calendar ID field or erase the data in the group definition ID field.
Chapter 3. EQQAnnn Messages
29
EQQA516E Ÿ EQQA523E
EQQA516E NO RUN CYCLES FOR AN APPLICATION IN A GROUP
Explanation: An application that references a group definition for run cycle information cannot itself contain run
cycles.
System action: The request is rejected.
User response: None.
EQQA520E THE RULE ON WHICH THE RUN CYCLE IS BASED MUST BE DEFINED
Explanation: A rule-based run cycle (type R or E) was inserted or replicated in the run cycle table, but no rule
definition was specified.
System action: The request is rejected.
User response: Use the S row command to select the rule modification panel and define the rule.
EQQA521E A VALID RULE NAME MUST BE SPECIFIED
Explanation: You have not entered a valid rule name. A valid rule name is maximum 8 characters long, first
character alphabetical and the remaining characters alphanumeric, or national.
System action: The request is rejected.
User response: Specify a valid rule name.
EQQA522E THE RULE NAME MUST BE UNIQUE WITHIN AN AD
Explanation: You have specified a rule name that has already been defined for a rule-based run cycle for this AD.
System action: The request is rejected.
User response: Specify a unique rule name.
EQQA523E THE RUN CYCLE TYPE HAS BEEN INCORRECTLY MODIFIED
Explanation: You have modified the type from an offset-based run cycle to a rule-based run cycle, or vice versa.
You can only change type within the run cycle subtype; that is, N and X for offset-based run cycles, or R and E for
rule-based run cycles.
System action: The request is rejected.
User response: Specify one of the required types, or create a new run cycle.
30
TME 10 OPC Messages and Codes
EQQC001I Ÿ EQQC006E
Chapter 4. EQQCnnn Messages
EQQC001I THE AUTOMATIC RECOVERY SUBTASK HAS STARTED
Explanation: The automatic job recovery subtask has been successfully initialized.
System action: Automatic job recovery processing is started.
User response: None.
EQQC002E THE AUTOMATIC RECOVERY INITIALIZATION FAILED
Explanation: The automatic job recovery subtask was not initialized because there is an error in the AROPTS
initialization statement.
System action: Automatic job recovery initialization is terminated.
Problem determination: This message is preceded by a message in the TME 10 OPC message log giving the
reason for this error message.
User response: Contact your system programmer.
System programmer response: Correct the error in the AROPTS initialization statement and then restart TME 10
OPC.
EQQC003I THE AUTOMATIC RECOVERY SUBTASK HAS ENDED NORMALLY
Explanation: This message is issued when the TME 10 OPC subsystem is being stopped by an operator command.
System action: The TME 10 OPC termination processing continues.
User response: None.
EQQC004E STARTTIME OR ENDTIME OPTION TIME IN AROPTS STATEMENT IS NOT VALID
Explanation: The STARTTIME or ENDTIME option in the AROPTS initialization statement is not specified in a valid
TME 10 OPC time format. The option TIME must be a 4-digit decimal number in the format HHMM, where HH is
from 00 through 23, and MM is from 00 through 59.
System action: Automatic job recovery initialization is terminated.
User response: Correct the STARTTIME or ENDTIME value in the AROPTS initialization statement. Then stop
TME 10 OPC and restart it.
EQQC005E THE AUTOMATIC RECOVERY INITIALIZATION FAILED, MODULE EQQCASEM NOT FOUND
Explanation: The initialization of the automatic job recovery subtask failed because the load module EQQCASEM
could not be found in a library accessible to TME 10 OPC.
System action: Automatic job recovery initialization is terminated.
User response: Contact your system programmer.
System programmer response: Make sure that the load module EQQCASEM is present in a library that can be
accessed by TME 10 OPC. Then stop the TME 10 OPC started task and restart it.
EQQC006E HOUR AND MINUTE MUST BOTH BE TWO-DIGIT NUMBERS
Explanation: A nonnumeric time value has been specified.
System action: Processing continues.
System programmer response: Reenter a numeric time value.
 Copyright IBM Corp. 1991, 1998
31
EQQC007E Ÿ EQQC012W
EQQC007E AN ABEND OCCURRED IN THE AUTOMATIC RECOVERY SUBTASK, IT IS RESTARTED
Explanation: An error has caused the automatic job recovery subtask to end abnormally, but it has been able to
restart.
System action: Automatic job recovery resumes normal processing but one or more requests for service may have
been rejected.
Problem determination: At abend, a dump is written to the SYSxDUMP dataset.
User response: Inform your system programmer about the error and, if the error can be reproduced, of the
sequence of dialog requests leading to the error.
System programmer response: Collect relevant information about the sequence of events leading to this error.
Make the dump dataset and the TME 10 OPC message log available for inspection. Contact your IBM representative.
EQQC008E HOUR MUST BE IN THE RANGE 0 TO 23
Explanation: A time value has been specified where the hour number is not valid.
System action: Processing continues.
System programmer response: Reenter the time value and specify an hour number in the range 0 through 23.
EQQC009E MINUTE MUST BE IN THE RANGE 0 TO 59
Explanation: A time value has been specified where the minute number is not valid.
System action: Processing continues.
System programmer response: Reenter the time value and specify a minute number in the range 0 through 59.
EQQC011W AUTOMATIC RECOVERY REQUEST FAILED, SERVICE INACTIVE
Explanation: Automatic job recovery requires service from other TME 10 OPC subtasks. When automatic job
recovery was initiated to determine whether or not recovery should be performed for the job that ended in error, the
service SERVICE was down (not available).
System action: No recovery attempt is made and the job remains ended in error.
Problem determination: To determine why the service is not available, review the earlier messages in the TME 10
OPC message log. For job tracking, consider the messages that mention the Normal Mode Manager.
User response: Use the ended-in-error list of the Modify Current Plan dialog to decide whether or not a new
automatic job recovery attempt should be made for the job that ended in error.
System programmer response: Check why the service SERVICE was down.
EQQC012W AUTOMATIC RECOVERY REQUEST FAILED, CANNOT OPEN FILE FILE
Explanation: Automatic job recovery requires access to TME 10 OPC VSAM files. Failure to open one of these files
prevented automatic job recovery from checking whether or not recovery should be performed for the job that ended in
error. FILE is the name of the VSAM file that could not be opened.
System action: No recovery attempt is made and the job remains ended in error.
Problem determination: To determine why the file cannot be opened, review the earlier messages in the TME 10
OPC message log.
User response: Use the ended-in-error list of the Modify Current Plan dialog to decide whether or not a new
automatic job recovery attempt should be made for the job that ended in error.
System programmer response: Check with your system programmer why the file FILE could not be opened.
32
TME 10 OPC Messages and Codes
EQQC013W Ÿ EQQC022I
EQQC013W AUTOMATIC RECOVERY REQUEST FAILED, CANNOT ALLOCATE BUFFERS
Explanation: A storage allocation error prevented automatic job recovery from checking whether or not recovery
should be performed for the job that ended in error. This message may be followed by message EQQC045I with
reason code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended in error.
User response: Use the ended-in-error list of the Modify Current Plan dialog to decide whether or not a new
automatic job recovery attempt should be made for the job that ended in error.
System programmer response: Stop TME 10 OPC and then restart it in a larger region.
EQQC014W AUTOMATIC RECOVERY REQUEST FAILED DUE TO I/O ERROR
Explanation: An I/O error prevented automatic job recovery from determining whether or not recovery should be
performed for the job that has ended in error. This message may be followed by message EQQC045I with reason
code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended in error.
Problem determination: Review the earlier messages in the TME 10 OPC message log for a message issued for
the I/O error.
User response: Use the ended-in-error list of the Modify Current Plan dialog to decide whether or not a new
automatic job recovery attempt should be made for the job that ended in error.
System programmer response: Refer to the associated I/O error message for guidance.
EQQC021W NO AUTOMATIC RECOVERY TEST BECAUSE NO ERROR INFORMATION IN JNT RECORD
Explanation: When a job fails, error information about the failing operation is saved in the job-name-table (JNT)
record. Automatic job recovery was initiated but could not determine if recovery should be performed for the failed job
because no error information was available in the JNT record. This message is followed by message EQQC045I with
reason code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended-in-error.
Problem determination: Review the TME 10 OPC message log for inconsistencies at the time the job ended in
error. Also review the event dataset for the completion of the job. Refer to TME 10 OPC Diagnosis Guide and
Reference for the layout of the event dataset record.
User response: If any recovery actions by automatic job recovery were required for the job that failed, the actions
must be initiated manually. Use the Modify Current Plan dialog to initiate the actions.
If you use automatic job recovery together with catalog management and have defined the RESSTEP parameter of
the RECOVER statement, specify STEPEVENTS(ALL) on the EWTROPTS statement. Otherwise automatic job
recovery and catalog management will not be invoked.
System programmer response: Check the TME 10 OPC message log for any messages issued at the time the job
ended in error to determine why no JNT record exists.
EQQC022I AUTOMATIC RECOVERY ACTION POSTPONED FOR OPERATION OPNO IN APPLICATION ADID
Explanation: When the automatic recovery for this operation was about to start, TME 10 OPC found that a catalog
management action for this operation was in progress. The automatic recovery for this operation will be postponed
until catalog management has finished its processing for the operation.
System action: The recovery attempt is postponed.
User response: None.
Chapter 4. EQQCnnn Messages
33
EQQC023W Ÿ EQQC027W
EQQC023W NO AUTOMATIC RECOVERY TEST BECAUSE NO JCL RECORD FOR THE OPERATION
Explanation: The JCL record could not be read. This prevented automatic job recovery from determining whether or
not recovery should be performed for the job that ended in error. This message is followed by message EQQC045I
with reason code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended in error.
Problem determination: Review the TME 10 OPC message log for inconsistencies at the time the job ended in
error.
User response: If any recovery actions by automatic job recovery were required for the job that failed, the actions
must be initiated manually. Use the Modify Current Plan dialog to initiate the actions.
System programmer response: Check the TME 10 OPC message log for any messages issued at the time the job
ended in error to determine why the JCL record could not be read.
EQQC024W NO AUTOMATIC RECOVERY TEST BECAUSE OPERATION RECORD MODIFIED
Explanation: Automatic job recovery could not determine whether or not recovery should be performed for the job
that ended in error because the operation record indicates that the operation no longer has the error status.
System action: No recovery attempt is made for the job that ended in error.
User response: None.
EQQC026W NO AUTOMATIC RECOVERY TEST BECAUSE JCL MEMBER IS BEING USED
Explanation: Automatic job recovery could not determine whether or not recovery should be performed for the job
that ended in error, because the member on the JCL repository file (ddname EQQJ1SDS and EQQJS2DS) was being
used by another TME 10 OPC subtask. This message is followed by message EQQC045I with reason code 50,
which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended in error.
User response: When the EQQJSxDS JCL member is free, you can initiate a new automatic job recovery attempt
for the job that ended in error. Use the ended-in-error list of the Modify Current Plan dialog to do that.
EQQC027W NO AUTOMATIC RECOVERY BECAUSE PROCLIB MEMBER NOT FOUND
Explanation: No automatic job recovery could be performed for the job that ended in error because the RECOVER
statement that matched the error specifies a procedure library member that could not be found. This message is
followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended in error.
Problem determination: Review the JCL to determine the procedure library member name. The selected
RECOVER statement is followed by a comment line that gives the member name.
User response: Check that the member name is correctly spelled and that it is available in the EQQPRLIB file.
When you have found and corrected the error, edit the JCL and insert a % sign in column 4 of the RECOVER line in
order to convert the line into a RECOVER statement again. You can initiate a new automatic job recovery attempt for
the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog.
34
TME 10 OPC Messages and Codes
EQQC028W Ÿ EQQC045I
EQQC028W NO AUTOMATIC RECOVERY TEST BECAUSE ERROR IN RECOVER STATEMENT
Explanation: While automatic job recovery was checking whether or not recovery should be performed for a job that
ended in error, a RECOVER statement with a syntactical error was found. This message is followed by message
EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended in error.
Problem determination: Review the JCL of the identified operation.
User response: Check the RECOVER statements for syntactical errors. Make sure that the operation is separated
from the operands by one or more blanks, and that the operands are separated by a comma. When you have found
and corrected the error, you can initiate a new automatic job recovery attempt for the job that ended in error by using
the ended-in-error list of the Modify Current Plan dialog.
EQQC029I NO AUTOMATIC RECOVERY BECAUSE RECOVER STATEMENT DOES NOT MATCH THIS ERROR
Explanation: While automatic job recovery was checking whether or not recovery should be performed for a job that
ended in error, one or more RECOVER statements were found but none matched the current error. This message is
followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended in error.
User response: Consider if the error should be covered in the recovery scheme.
EQQC044I AUTO RECOVERY OF APPL ADID DATE H.M, OP WSN OP JN JID
Explanation: Automatic job recovery actions have been taken for the specified occurrence (application ADID DATE
H. M, operation WSN OP, where DATE H. M is the occurrence input arrival time). The specified JCL rebuild is made.
Restart, application addition, and release of successors are in process as specified in the RECOVER statement.
System action: The specified automatic recovery actions are started up.
User response: None.
EQQC045I AUTO RECOVERY INFO RS, APPL ADID DATE H.M, OP WSN OP JN JID
Explanation: Automatic job recovery is being performed for the job identified as application ADID DATE H. M,
operation WSN OP; where DATE H. M is the occurrence input arrival time). This message is issued to keep track of
a particular action taken during the recovery processing.
RS is a reason code that stands for a certain error and/or action related to automatic job recovery. Message
EQQC047E has a list of the reason codes and their meanings.
System action: The specified automatic recovery actions are started up.
Problem determination: Review the JCL of the identified operation. Identify the recovery actions described in the
RECOVER statement of the JCL.
User response: Look up the meaning of reason code RS in the list given in message EQQC047E. Review the
action taken and see if it matches the action requested. If necessary, take the appropriate action.
Chapter 4. EQQCnnn Messages
35
EQQC046W Ÿ EQQC047E
EQQC046W AUTO RECOVERY WARNING RS, APPL ADID DATE H.M, OP WSN OP JN JID
Explanation: Automatic job recovery was attempted for the job identified as application ADID DATE H. M, operation
WSN OP, where DATE H. M is the occurrence input arrival time. A problem was encountered that inhibited automatic
job recovery.
RS is a reason code that stands for a certain error and/or action related to automatic job recovery. Message
EQQC047E has a list of the reason codes and their meanings.
System action: The operation is left unchanged by automatic job recovery.
Problem determination: Review the JCL of the identified operation. Identify the recovery actions described in the
RECOVER statement of the JCL.
User response: Look up the meaning of reason code RS in the list given in message EQQC047E. Review what
recovery actions are taken and see if they match the actions requested in the RECOVER statement. If necessary,
use the Modify Current Plan dialog to perform the rest of the recovery actions.
EQQC047E AUTO RECOVERY ERROR RS, APPL ADID DATE H.M, OP WSN OP JN JID
Explanation: Automatic job recovery was attempted for the job identified as application ADID DATE H. M, operation
WSN OP, where DATE H. M is the occurrence input arrival time. An error was encountered that inhibited the
recovery actions.
RS is a reason code that stands for a certain error and/or action related to automatic job recovery. The list below
gives the reason codes and their meanings.
System action: The job remains ended in error and the extended status of the operation is set to E. The JCL
record on the JCL repository dataset might have been updated with information about the error.
Problem determination: The following reason codes (RS) indicate the errors and/or actions related to automatic job
recovery:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
36
Misplaced TME 10 OPC recover statement.
Incorrect parameter.
Unbalanced parentheses.
Invalid continuation line.
Invalid length of parameter value.
A parameter appears twice in same recover statement.
Invalid return code from exit.
Terminate return code from exit.
Abandon return code from exit.
Invalid restart parameter value. Set Y, YES, N, or NO.
Procedure library member not found.
I/O error.
Unable to load exit routine.
No job statement found.
Incorrect job statement. Cannot add restart parameter.
Invalid specification of generic code.
Loop in the case code lists.
Checkpoint name contains special characters.
Missing stepname.
Too many values specified in parameter.
Failing OP is outside rerun or successor tree.
External successor in rerun tree is not in the failing tree.
Inconsistency with AD of failing occurrence (for example, AD no longer exists or is not active).
AD of application to add could not be found.
Error while using MCP (additional message by MCP).
Unable to allocate virtual storage.
Error detected and handled by other subtask.
Improper naming of steps, give all unique names.
Cannot add restart param. because no delimiter last job line.
No information about error in job name table (JNT).
TME 10 OPC Messages and Codes
EQQC048W Ÿ EQQC049E
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
50
51
52
Failing operation record could not be read.
Invalid stepname or no step with that name.
More than one step in JS record with the given name.
JS dataset in use. Recovery test canceled.
JS dataset member in use. Recovery test canceled.
OP record has been changed. Recovery test canceled.
Invalid range.
No occurrence exists for the specified application.
Recovery actions taken.
No JS record.
Restart step not present in the JCL.
Step end entries missing in JNT record (CPLREC04). The error can relate to:
Ÿ Nested procedures
Ÿ JCL INCLUDE statements
Ÿ JCL IF/THEN/ELSE/ENDIF statement constructs.
These JCL statements are restricted by automatic job recovery when used in conjunction with the ERRSTEP,
RESSTEP, or STEPCODE parameters of the RECOVER statement.
Parameter not supported when STEPEVENTS(ABEND) specified.
RESSTEP=% specified but error not related to a step.
A required service function (NMM) has terminated.
No free input arrival time for the application to add.
Missing value for parameter.
Authorization check requires user ID.
Adding identification data to messages in ARTOP.
Error in ALTWS parameter.
Error in ALTJOB parameter.
User response: Check the RECOVER statements. Comment lines that describe the error in detail are added to the
JCL. When you have found and corrected the error, you can use the ended-in-error list of the Modify Current Plan
dialog to initiate a new automatic job recovery attempt.
EQQC048W AUTO RECOVERY WARNING RS
Explanation: Automatic job recovery was attempted for the job that ended in error but was inhibited because of a
problem with reason code RS. This message differs from EQQC046W in that automatic job recovery was not able to
identify the application to be handled.
System action: No recovery is made and the job remains ended in error.
Problem determination: Message EQQC047E has a list of the reason codes and their meanings. Review the JCL
of the identified operation. Identify the recovery actions described in the RECOVER statement of the JCL.
User response: Look up the meaning of reason code RS in the list given in message EQQC047E. Review what
recovery actions are taken and see if they match the actions requested in the RECOVER statement. If necessary,
use the Modify Current Plan dialog to perform the rest of the recovery actions.
EQQC049E AUTO RECOVERY ERROR RS
Explanation: Automatic job recovery was attempted for the job that ended in error but was inhibited because of an
error with reason code RS. This message differs from EQQC047E in that automatic job recovery was not able to
identify the application to be handled.
System action: No recovery is made and the job remains ended in error. The extended status of the operation is
set to E.
Problem determination: Message EQQC047E has a list of the reason codes and their meanings. The JS record
may have been updated with information about the error. Review the JCL of the identified operation. Identify the
recovery actions described in the RECOVER statement of the JCL.
User response: Look up the meaning of reason code RS in the list given in message EQQC047E. Review what
recovery actions are taken and see if they match the actions requested in the RECOVER statement. If necessary,
use the Modify Current Plan dialog to perform the rest of the recovery actions.
Chapter 4. EQQCnnn Messages
37
EQQC061E Ÿ EQQC500E
EQQC061E AUTOMATIC RECOVERY FAILED, I/O ERROR
Explanation: Automatic job recovery failed for the job that ended in error because an I/O error occurred. The I/O
error occurred while the automatic job recovery subtask was determining whether recovery should be performed, or
while the recovery actions were being activated or implemented.
This message is preceded by a message that describes the I/O error in more detail, and is followed by message
EQQC045I with reason code 50, which identifies the job handled by automatic job recovery.
System action: The job remains ended in error. Some of the intended recovery actions may have been started up
or completed.
Problem determination: Review the JCL of the identified operation. Identify the recovery actions described in the
RECOVER statement of the JCL.
User response: When you have found and corrected the error, you can initiate a new automatic job recovery
attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog. You may
have to initiate the recovery actions manually, or you may have to change the RECOVER statement to encompass
only the remaining recovery actions.
System programmer response: Review the TME 10 OPC message log for I/O errors that immediately precede this
message.
EQQC062E AUTOMATIC RECOVERY FAILED, NOT ENOUGH VIRTUAL STORAGE - SIZE
Explanation: Automatic job recovery failed for the job that ended in error because of insufficient virtual storage. The
failure occurred while the automatic job recovery subtask was determining whether recovery should be performed, or
while the recovery actions were being activated or implemented. SIZE is the amount of virtual storage requested.
This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic
job recovery.
System action: The job remains ended in error. Some of the intended recovery actions may have been started up
or completed.
Problem determination: Review the JCL of the identified operation. Identify the recovery actions described in the
RECOVER statement.
User response: When you have found and corrected the error, you can initiate a new automatic job recovery
attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog. You may
have to initiate the recovery actions manually, or you may have to change the RECOVER statement to encompass
only the remaining recovery actions.
System programmer response: Stop TME 10 OPC and restart it in a larger region.
EQQC500E THE JCL LIBRARY, DDNAME EQQPRLIB, COULD NOT BE OPENED
Explanation: Automatic job recovery could not open the JCL procedure library (ddname EQQPRLIB) to read a
procedure specified in the ADDPROC parameter of the RECOVER statement. This message is followed by message
EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made, and the job remains ended in error.
Problem determination: Review the preceding messages in the TME 10 OPC message log for a message
describing an I/O error on the EQQPRLIB file.
User response: Contact your system programmer. When your system programmer has fixed the problem, you can
initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the
Modify Current Plan dialog.
System programmer response: Check that the ddname EQQPRLIB is correctly specified and that the task started
by TME 10 OPC is authorized to open the dataset for input. When the error is corrected, stop TME 10 OPC and
then restart it.
38
TME 10 OPC Messages and Codes
EQQC501E Ÿ EQQC501E
EQQC501E LOGICAL RECORD LENGTH FOR THE JCL LIBRARY, DDNAME EQQPRLIB, IS NOT VALID
Explanation: Automatic job recovery could not read a procedure specified in the ADDPROC parameter of the
RECOVER statement because the logical record length is not 80 bytes. This message is followed by message
EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
System action: No recovery attempt is made and the job remains ended in error.
Problem determination: Check the definition of the EQQPRLIB DD statement.
User response: Contact your system programmer. When your system programmer has fixed the problem, you can
initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the
Modify Current Plan dialog.
System programmer response: Check that the ddname EQQPRLIB is correctly defined. When the error is
corrected, stop TME 10 OPC and then restart it.
Chapter 4. EQQCnnn Messages
39
40
TME 10 OPC Messages and Codes
EQQCL00I Ÿ EQQCL08I
|
Chapter 5. EQQCLnnn Messages
| EQQCL00I Processing: instruction
| Explanation: OCL is processing the instruction instruction
| System action: Processing continues.
| User response: None.
| EQQCL02 x instr instruction executed: RC=return_code
| Explanation: This message reports the return code (return_code) of the instruction. x can be one of the following:
| I
| W
| E
Information (RC=0)
Warning (RC=4)
Error (RC=8)
| System action: Processing continues.
| User response: None.
| EQQCL03I True condition: IF expression
| Explanation: An IF instruction was specified. OCL processed the instruction specified in the THEN clause.
| System action: Processing continues.
| User response: None.
| EQQCL04I True condition: ELSE expression
| Explanation: An IF instruction was specified. OCL processed the instruction specified in the ELSE clause.
| System action: Processing continues.
| User response: None.
| EQQCL05I False condition: IF expression
| Explanation: The condition specified in the IF instruction is false.
| System action: Processing continues.
| User response: Verify that the specified keywords are correct.
| EQQCL06I The default value of variable varname was updated
| Explanation: An UPD or SETUPD instruction was specified. The default value of the variable varname was updated
| in the OPC variable table specified by the INIT instruction.
| System action: Processing continues.
| User response: None.
| EQQCL08I Occurrence appl was completed
| Explanation: OCL processed a COMPL instruction that completed the occurrence appl.
| System action: Processing continues.
| User response: None.
 Copyright IBM Corp. 1991, 1998
41
EQQCL09I Ÿ EQQCL0GI
| EQQCL09I The operation was completed: OPNO(opnum) APPL(appl) IA(iadt)
| Explanation: OCL completed the operation opnum within the occurrence appl with the input arrival date and time
| iadt.
| System action: Processing continues.
| User response: None.
| EQQCL0AI The occurrence was added: APPL(appl) IA(iadt)
| Explanation: OCL added a new occurrence in the OPC current plan or long term plan. appl is the occurrence ID
| and iadt is the input arrival date and time.
| System action: Processing continues.
| User response: None.
| EQQCL0BI A DELETE request was executed for application appl
| Explanation: OCL tried to add a new occurrence in the OPC plan, but a problem occurred, so it issued a DELETE
| request for the application appl.
| System action: Processing continues.
| User response: None.
| EQQCL0CI Default predecessor operation is used: defpreopno
| Explanation: OCL defined defpreopno as an external predecessor of the operation to be modified.
| System action: Processing continues.
| User response: None.
| EQQCL0DI Internal predecessor preopnum defined to operation opnum
| Explanation: A new internal predecessor was defined for operation opnum.
| System action: Processing continues.
| User response: None.
| EQQCL0EI appl belongs to group applgrp
| Explanation: Application appl is associated to the application group applgrp.
| System action: Processing continues.
| User response: None.
| EQQCL0FI The occurrence was deleted: APPL(appl) IA(iadt)
| Explanation: The occurrence appl was deleted from the OPC current plan.
| System action: Processing continues.
| User response: None.
| EQQCL0GI The operation was deleted: OPNO(opnum) APPL(appl) IA(iadt)
| Explanation: The operation opnum was deleted from the occurrence appl with the input arrival date and time iadt.
| System action: Processing continues.
| User response: None.
42
TME 10 OPC Messages and Codes
EQQCL0HI Ÿ EQQCL0OI
| EQQCL0HI Occurrence found in LTP: APPL(appl) IA(iadt)
| Explanation: OCL found an occurrence in the long term plan that matches
| with the specified selection parameters.
| System action: Processing continues.
| User response: None.
| EQQCL0II Date is valid
| Explanation: The input date is valid.
| System action: OCL calculates about 210 variables, based on the input date.
| User response: None.
| EQQCL0JI Searching for occurrence appl in CP
| Explanation: OCL is searching the occurrence appl in the OPC current plan.
| System action: Processing continues.
| User response: None.
| EQQCL0KI Total number of matching occurrences: n_occ
| Explanation: OCL found n_occ occurrences in the OPC current plan that match the specified selection parameters.
| System action: Processing continues.
| User response: None.
| EQQCL0LI Oper. in error: opnum APPL(appl) IA(iadt) WS(wsname) ERR(err_code)
| Explanation: OCL found an ended-in-error operation with error code err_code.
| System action: Processing continues.
| User response: None.
| EQQCL0MI Error code err_code matches ERR() for operation opnum
| Explanation: This “output” message reports all the operations whose error code matches the value that the user
| specified in the ERR() parameter.
| System action: Processing continues.
| User response: None.
| EQQCL0NI Reply to WTOR was issued
| Explanation: An operator replied to the WTO issued by OCL.
| System action: Processing continues.
| User response: None.
| EQQCL0OI Occurrence found: APPL(appl) IA(iadt) STATUS(status)
| Explanation: OCL found an occurrence in the current plan that matches the selection parameters.
| System action: Processing continues.
| User response: None.
Chapter 5. EQQCLnnn Messages
43
EQQCL0PI Ÿ EQQCL0WI
| EQQCL0PI cmd command was issued
| Explanation: OCL issued command cmd, which can be SRSTAT, OPSTAT, or WSSTAT.
| System action: Processing continues.
| User response: None.
| EQQCL0QI Operation opnum was successfully modified
| Explanation: OCL modified the operation opnum.
| System action: Processing continues.
| User response: None.
| EQQCL0RI Deleting the special resource from operation opnum
| Explanation: OCL is deleting the special resource definition from operation opnum.
| System action: Processing continues.
| User response: None.
| EQQCL0SI Deleting the external predecessor(s) from operation opnum
| Explanation: OCL is deleting the external predecessors from operation opnum.
| System action: Processing continues.
| User response: None.
| EQQCL0TI Operation status was changed to 'R': OPNO(opnum)
| Explanation: OCL modified the status of operation opnum.
| System action: Processing continues.
| User response: None.
| EQQCL0UI External predecessor(s) will be deleted from operation opnum
| Explanation: OCL will delete all the external predecessors from operation opnum.
| System action: Processing continues.
| User response: None.
| EQQCL0VI Occurrence appl is now started
| Explanation: OCL forced the occurrence appl to start.
| System action: Processing continues.
| User response: None.
| EQQCL0WI Jobname was changed for operation opnum
| Explanation: OCL changed the jobname for operation opnum.
| System action: Processing continues.
| User response: None.
44
TME 10 OPC Messages and Codes
EQQCL0XI Ÿ EQQCL14I
| EQQCL0XI Default operation number is used: defopno
| Explanation: OCL will use defopno as the default operation number.
| System action: Processing continues.
| User response: None.
| EQQCL0YI Predecessor added to operation opnum: PREOPNO(preopnum) PREAPPL(preappl)
| Explanation: OCL added a new predecessor to operation opnum. preopnum is the predecessor operation, and
| preappl is the predecessor application ID.
| System action: Processing continues.
| User response: None.
| EQQCL0ZI New dependency created for occurrence appl: PREAPPL(preappl)
| Explanation: OCL added a new predecessor to operation opnum. preappl is the predecessor application ID.
| System action: Processing continues.
| User response: None.
| EQQCL10I Predecessor deleted: PREOPNO(preopnum) PREAPPL(preappl) PREIA(iadt)
| Explanation: OCL deleted a predecessor definition. preopnum is the predecessor operation number, preappl is the
| occurrence ID, and iadt is the input arrival date and time.
| System action: Processing continues.
| User response: None.
| EQQCL11I Special resource added to operation opnum: res_name
| Explanation: OCL added a new special resource definition to operation opnum. res_name is the name of the
| special resource.
| System action: Processing continues.
| User response: None.
| EQQCL12I Special resource deleted from operation opnum: res_name
| Explanation: OCL deleted a special resource definition from operation opnum res_name is the name of the special
| resource.
| System action: Processing continues.
| User response: None.
| EQQCL13I Successor released from operation opnum: OPNO(s_opnum) APPL(appl)
| Explanation: OCL deleted a successor dependency definition from operation opnum. s_opnum is the successor
| operation number, and appl is the successor application ID.
| System action: Processing continues.
| User response: None.
| EQQCL14I Operation p_opnum was defined as an internal predecessor of operation opnum
| Explanation: OCL added a new predecessor to operation opnum. p_opnum is the predecessor operation number.
| System action: Processing continues.
| User response: None.
Chapter 5. EQQCLnnn Messages
45
EQQCL15I Ÿ EQQCL1CI
| EQQCL15I Internal successor released: OPNO(s_opnum) APPL(appl)
| Explanation: OCL released the internal successor operation number s_opnum in the occurrence appl.
| System action: Processing continues.
| User response: None.
| EQQCL16I External successor found for operation opnum: OPNO(s_opnum) APPL(appl)
| Explanation: OCL found an external successor for operation opnum. s_opnum is the successor operation number;
| appl is the successor occurrence ID.
| System action: Processing continues.
| User response: None.
| EQQCL17I Internal successor found for operation opnum: OPNO(s_opnum)
| Explanation: OCL found an internal successor for operation opnum. s_opnum is the successor operation number.
| System action: Processing continues.
| User response: None.
| EQQCL18I External predecessor found: PREAPPL(appl) PREIA(iadt)
| Explanation: OCL found an external predecessor. appl is the predecessor occurrence ID, and iadt is its input arrival
| date and time.
| System action: Processing continues.
| User response: None.
| EQQCL19I External predecessor found: PREOPNO(opnum) PREAPPL(appl) PREIA(iadt)
| Explanation: OCL found an external predecessor. opnum is the predecessor operation number, appl is the
| predecessor occurrence ID and iadt is its input arrival date and time.
| System action: Processing continues.
| User response: None.
| EQQCL1AI n_occ occurrences found for application appl
| Explanation: OCL found n_occ occurrences of application appl in the current plan.
| System action: Processing continues.
| User response: None.
| EQQCL1BI Operation opnum was added to occurrence appl with IA iadt
| Explanation: OCL added operation opnum to occurrence appl.
| System action: Processing continues.
| User response: None.
| EQQCL1CI Number of not completed occurrences: n_occ
| Explanation: OCL found n_occ occurrences that are not in Complete status.
| System action: Processing continues.
| User response: None.
46
TME 10 OPC Messages and Codes
EQQCL1DI Ÿ EQQCL44W
| EQQCL1DI External predecessor deleted: PREAPPL(preappl) PREIA(iadt)
| Explanation: OCL deleted an external predecessor definition. preappl is the predecessor occurrence ID, and iadt its
| input arrival date and time.
| System action: Processing continues.
| User response: None.
| EQQCL1EI Special resource found for operation opnum: res_name
| Explanation: OCL found a special resource defined to operation opnum. res_name is the name of the special
| resource.
| System action: Processing continues.
| User response: None.
| EQQCL40W The routine returned result return code
| Explanation: The value of result is the return code of the routine. This message is issued when the return code is
| not zero.
| System action: If the return code issued by the called routine is higher than the highest return code of the other
| processed OCL instructions, it will be assumed as the highest return code.
| OCL processing continues.
| User response: None.
| EQQCL41W Process terminated due to a LABEL instruction - Highest RC=lastrc
| Explanation: OCL processed a LABEL instruction.
| System action: OCL terminates with the highest return code of the processed OCL instructions.
| User response: None.
| EQQCL42W Variable varname will be added to the variable table vartab
| Explanation: OCL processed an UPD or SETUPD instruction to modify the value of a variable that does not exist in
| the OPC variable table.
| System action: OCL will add the variable varname to the variable table vartab. OCL processing continues.
| User response: Verify that the variable name specified in the UPD or SETUPD instruction is correct.
| EQQCL43W No occurrence to complete: appl
| Explanation: OCL processed a COMPL instruction for an application occurrence, but no occurrence in a
| noncomplete status was found in the current plan.
| System action: OCL processing continues.
| User response: Verify that the selection parameters for the application occurrence are correct.
| EQQCL44W Occurrence not found in the current plan: APPL(appl) IA(iadt)
| Explanation: OCL attempted to modify or list the application occurrence appl, which does not exist in the current
| plan. iadt is the input arrival date and time used to search for the occurrence.
| System action: OCL processing continues.
| User response: Verify that the selection parameters are correct.
Chapter 5. EQQCLnnn Messages
47
EQQCL45W Ÿ EQQCL4CW
| EQQCL45W Occurrence not found in the LTP: APPL(appl) IA(iadt)
| Explanation: OCL attempted to modify or list the application occurrence appl, which does not exist in the long term
| plan. iadt is the input arrival date and time used to search for the occurrence.
| System action: OCL processing continues.
| User response: Verify that the selection parameters are correct.
| EQQCL46W Only OCL instructions are accepted: sysin_line
| Explanation: A non-OCL instructions was specified, and the initialization parameter TSOCMD is set to NO.
| System action: OCL processing continues.
| User response: If you want the user to be able to specify TSO commands or REXX instructions other than those of
| OCL, set the TSOCMD parameter to YES.
| EQQCL47W Oper. not found or not in Error: opnum APPL(appl) IA(iadt)
| Explanation: The application occurrences appl with input arrival date and time iadt does not contain the selected
| operation or the selected operation is not in error status.
| System action: OCL processing continues.
| User response: Verify that the selected operation really exists in the application occurrence.
| EQQCL48W Error code errcode does not match ERRCODE() for operation opnum
| Explanation: errcode is the error code specified in the CHKAPPL instruction for operation opnum. OCL found the
| operation opnum in error status, but its error code does not match errcode.
| System action: OCL processing continues.
| User response: None.
| EQQCL49W Operation opnum is not in HOLD status
| Explanation: OCL tried to release an operation that was not manually held.
| System action: OCL processing continues.
| User response: None.
| EQQCL4AW Operation opnum is already in HOLD status
| Explanation: OCL tried to hold an operation that was already in HOLD status.
| System action: OCL processing continues.
| User response: None.
| EQQCL4BW Operation opnum is not in NOP status
| Explanation: OCL issued an UNNOP command against an operation that was not in NOP status.
| System action: OCL processing continues.
| User response: None.
| EQQCL4CW Operation opnum is already in NOP status
| Explanation: OCL issued a NOP command against an operation that was already in NOP status.
| System action: OCL processing continues.
| User response: None.
48
TME 10 OPC Messages and Codes
EQQCL4DW Ÿ EQQCL4JW
| EQQCL4DW External predecessor(s) found, status cannot be changed
| Explanation: OCL tried to set an operation to Ready status, but external predecessors are defined. OCL will delete
| the dependency definitions and will try to set the operation Ready again.
| System action: OCL processing continues.
| User response: None.
| EQQCL4EW Occurrence appl is still in Waiting status
| Explanation: OCL tried to force the application occurrence to start, but it is still in Waiting status.
| System action: OCL processing continues.
| User response: Verify the conditions that cause the occurrence to wait. Check the current operation status and
| extended status, using the OPC dialogs, to determine more precisely why the application occurrence failed to start.
| EQQCL4FW No operation found to be changed
| Explanation: OCL tried to change the jobname associated with an operation in the current plan, but the operation
| was not found.
| System action: OCL processing continues.
| User response: Verify that the selection parameters are correct.
| EQQCL4GW Predecessor application not found in CP: PREAPPL(preappl) PREIA(preiadt)
| Explanation: preappl is the predecessor application ID and preiadt is the input arrival date and time of the
| predecessor application. OCL tried to define preappl as a predecessor of the application occurrence specified in the
| APPL() keyword, but preappl is not present in the current plan.
| System action: OCL processing continues.
| User response: Verify that the selection parameters are correct.
| EQQCL4HW Operation opnum doesn't exists
| Explanation: OCL tried to change or delete an operation that does not exist in the current plan.
| System action: OCL processing continues.
| User response: Verify that the specified keywords are correct.
| EQQCL4IW Already predecessor: preopnum
| Explanation: OCL tried to define a predecessor that is already defined.
| System action: OCL processing continues.
| User response: Verify that the specified keywords are correct.
| EQQCL4JW Predecessor not found in the LTP: PREAPPL(preappl) PREIA(preiadt)
| Explanation: OCL tried to define preappl as a predecessor of the application occurrence specified in the APPL()
| keyword, but preappl is not present in the long term plan.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
Chapter 5. EQQCLnnn Messages
49
EQQCL4KW Ÿ EQQCL4RW
| EQQCL4KW No external successor found for the occurrence appl
| Explanation: OCL tried to release the external successors of the occurrence appl, but no successor was found for
| the occurrence.
| System action: OCL processing continues.
| User response: None.
| EQQCL4LW Operation opnum not found: APPL(appl) IA(iadt)
| Explanation: OCL tried to change operation opnum that is not present in the current plan.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL4MW No internal successor found for operation opnum of the occurrence appl
| Explanation: OCL tried to release the internal successors of operation opnum, but no successor was found.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL4NW No external predecessor found for the occurrence appl
| Explanation: OCL tried to release the external predecessors of occurrence appl, but no predecessor is present in
| the current plan.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL4OW No special resource found
| Explanation: OCL tried to delete a special resource definition, but no special resource is defined to the operation.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL4PW No operation was modified
| Explanation: OCL did not modify any operation in the occurrence.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL4QW Operation opnum already exists
| Explanation: OCL tried to add an operation that already exists in the occurrence.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL4RW Operation deadline later than occurrence deadline - accepted: deadline
| Explanation: The specified operation deadline is later than the occurrence deadline but is accepted.
| System action: OCL processing continues.
| User response: Verify that the specified keywords are correct.
50
TME 10 OPC Messages and Codes
EQQCL4SW Ÿ EQQCL51E
| EQQCL4SW Operation deadline precedes operation input arrival - accepted: deadline
| Explanation: The operation deadline precedes the operation input arrival but is accepted.
| System action: OCL processing continues.
| User response: Verify that the specified keywords are correct.
| EQQCL4TW Operation Input Arrival precedes occurrence - accepted: iadt
| Explanation: The operation input arrival precedes the occurrence input arrival but is accepted.
| System action: OCL processing continues.
| User response: Verify that the specified keywords are correct.
| EQQCL4UW Dependency already defined
| Explanation: OCL tried to define a predecessor that is already defined.
| System action: OCL processing continues.
| User response: Verify that the specified keywords are correct.
| EQQCL4VW No parameter was specified
| Explanation: No parameter was specified for the MODOP instruction. No change is required for the operation.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL4WW Occurrence already in Complete status: appl with IA iadt
| Explanation: OCL tried to complete an occurrence that was already completed.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL4XW Occurrence not found in the current plan: APPL(appl)
| Explanation: No occurrence exists in the current plan for application appl.
| System action: OCL processing continues.
| User response: Verify the selection parameters.
| EQQCL50E Not possible to read the OCL MLIB
| Explanation: OCL was not able to read the dataset referenced by the OCLMLIB DD card.
| System action: OCL terminates.
| User response: Verify the dataset name specified in the OCLMLIB DD card.
| EQQCL51E Not possible to read the OCL PARMLIB
| Explanation: OCL was not able to read the EQQYRPRM member in the OCL library.
| System action: OCL terminates.
| User response: Verify the dataset name specified in the OCLPARM ddname.
Chapter 5. EQQCLnnn Messages
51
EQQCL52E Ÿ EQQCL59E
| EQQCL52E Not possible to read the SYSIN card
| Explanation: OCL was not able to read the SYSIN DD card.
| System action: OCL terminates.
| User response: Verify the dataset specified in the EQQOCL.SYSIN DD card.
| EQQCL53E Invalid syntax: instruction
| Explanation: An invalid instruction was specified in the OCL SYSIN.
| System action: OCL terminates
| User response: Correct the instruction, then resubmit the job.
| EQQCL54E Not possible to write the control cards for PIFTEST program
| Explanation: OCL was not able to write the input control cards for the PIFTEST program.
| System action: OCL terminates
| User response: Contact your IBM representative.
| EQQCL55E Error during the GETMAIN request
| Explanation: OCL was not able to get the storage for the PIF session.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL56E PIF initialization failed for subsystem subsys
| Explanation: OCL was not able to initialize the OPC PIF session.
| System action: OCL terminates.
| User response: Check the OPC subsystem name specified in the PARMLIB SUBSYS() parameter or in the INIT
| instruction. If the subsystem name is correct and if the subsystem is active, contact your IBM representative.
| EQQCL57E Variable name is missing
| Explanation: The variable name was not specified in the UPD or SETUPD instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job
| EQQCL58E PIF TERM request failed
| Explanation: OCL was not able to terminate the OPC PIF session.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL59E PIF TERM request failed: error during FREEMAIN
| Explanation: OCL was not able to terminate the OPC PIF session.
| System action: OCL terminates.
| User response: Contact your IBM representative.
52
TME 10 OPC Messages and Codes
EQQCL5AE Ÿ EQQCL5HE
| EQQCL5AE Predecessor can't be equal to the operation to be added
| Explanation: OCL was requested to add a new operation in an application occurrence, but the operation number is
| equal to its internal predecessor operation number.
| System action: OCL terminates.
| User response: If you have specified the DEFOPNO initialization parameter, OCL will use it as a default
| predecessor operation number. You cannot add an operation with a number equal to DEFOPNO.
| EQQCL5BE No Current Plan exists
| Explanation: OCL cannot add or modify occurrences because the current plan does not exist.
| System action: OCL terminates.
| User response: Extend the current plan, then resubmit the job.
| EQQCL5CE No default value for variable varname
| Explanation: OCL did not find a value for variable varname.
| System action: OCL terminates.
| User response: Verify that a SET or SETUPD instruction was specified to set the variable value.
| EQQCL5DE Invalid operand for the PIF request: operand
| Explanation: A PIF request contained an invalid operand.
| System action: OCL terminates.
| User response: Verify that the length of operand is specified in the SETSTEMS subroutine in the OCL program.
| EQQCL5EE Not possible to complete the occurrence appl with IA iadt
| Explanation: OCL was not able to complete the occurrence appl.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL5FE Not possible to modify the occurrence appl with IA iadt
| Explanation: OCL was not able to modify the occurrence appl in the current plan.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL5GE Cannot complete operation opnum of occurrence appl with IA iadt
| Explanation: OCL was not able to complete the operation opnum in the occurrence appl with input arrival time iadt.
| System action: OCL terminates.
| User response: Verify if the operation has external predecessors.
| EQQCL5HE Required keyword(s) missing
| Explanation: A required keyword was not specified in the instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
Chapter 5. EQQCLnnn Messages
53
EQQCL5IE Ÿ EQQCL5PE
| EQQCL5IE APPL and GROUP are mutually exclusive keywords
| Explanation: APPL and GROUP keywords were specified in the same ADD instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL5JE OPC subsystem id must be supplied
| Explanation: The OPC subsystem ID was not specified.
| System action: OCL terminates.
| User response: Specify the subsystem ID in the SUBSYS initialization parameter (EQQYRPRM member in the OCL
| library) or in the INIT instruction.
| EQQCL5KE No application found for the group applgrp
| Explanation: OCL tried to add the application group applgrp, but no application was defined to the group.
| System action: OCL terminates.
| User response: Verify the application group ID.
| EQQCL5LE Not possible to add the occurrence appl
| Explanation: OCL was not able to add the occurrence appl.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL5ME Not possible to use an IA date other than the actual date
| Explanation: OCL tried to add an occurrence in the current or long term plan. An occurrence with the same input
| arrival already existed, so OCL tried to increment the input arrival time by 1 minute. An error occurs if the occurrence
| input arrival time is 23:59.
| System action: OCL terminates.
| User response: Specify an input arrival time other than 23:59 for the occurrence to be added.
| EQQCL5NE Not possible to add the occurrence with IA iadt
| Explanation: OCL was not able to add the occurrence with IA iadt.
| System action: OCL terminates.
| User response: Verify if the occurrence input arrival date and time is later than the long term plan end time.
| EQQCL5OE Operation number must be specified
| Explanation: The operation number is a required keyword for the instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL5PE Workstation id must be specified
| Explanation: Workstation ID is a required keyword for the instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
54
TME 10 OPC Messages and Codes
EQQCLQE Ÿ EQQCL5XE
| EQQCLQE Workstation wsname not found in the OPC database
| Explanation: Workstation wsname is not defined in the OPC Workstation database.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL5RE Jobname must be specified for workstation wsname
| Explanation: Workstation wsname requires the jobname (job-setup, computer, or printer)
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL5SE DATE1 and DATE2 are mutually exclusive keywords
| Explanation: You cannot use DATE1 and DATE2 keywords in the same CHKDATE instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL5TE Internal predecessor doesn't exist: preopnum
| Explanation: OCL tried to add an internal predecessor that does not exist.
| System action: OCL terminates.
|
|
|
|
User response: Check that the PREOPNUM() keyword refers to an existing operation number. If it does not, correct
the instruction, then resubmit the job. If the PREOPNUM() keyword is not specified, OCL uses the default operation
number (initialization parameter DEFOPNO) as the internal predecessor operation. Verify that the application contains
an operation with the number equal to the number specified in the DEFOPNO parameter.
| EQQCL5UE INCVALUE value can't be greater than 30
| Explanation: The value of INCVALUE must be in the range 1–30.
| System action: OCL terminates.
| User response: Specify a correct INCVALUE, then resubmit the job.
| EQQCL5VE The operation input arrival must be in the YYMMDDHHMM format
| Explanation: OCL found an invalid operation input arrival date and time.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL5WE The operation deadline must be in the YYMMDDHHMM format
| Explanation: OCL found an invalid operation deadline date and time.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL5XE Not possible to add the operation opnum in occurrence appl
| Explanation: OCL tried to insert a new operation in the application occurrence appl, but a problem occurred.
| System action: OCL terminates.
| User response: Verify if the operation opnum already existed in the occurrence. Refer to the error messages in the
| OPC message log.
Chapter 5. EQQCLnnn Messages
55
EQQCL5YE Ÿ EQQCL65E
| EQQCL5YE Not possible to define internal pred. preopnum to operation opnum
| Explanation: OCL tried to define an internal predecessor to operation opnum, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL5ZE Not possible to remove the occurrence from the application group
| Explanation: OCL tried to remove an occurrence from the application group before deleting it from the current plan
| or from the long term plan. A problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL60E Not possible to delete occurrence appl with IA iadt
| Explanation: OCL tried to delete the occurrence appl, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL61E Not possible to delete operation opnum of occurrence appl
| Explanation: OCL tried to delete operation opnum from the occurrence appl, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL62E Date must be supplied
| Explanation: A date must be supplied in the CHKDATE instruction.
| System action: OCL terminates.
| User response: Use the DATE1 or DATE2 keyword according with the format of the date, then resubmit the job.
| EQQCL63E Date not valid: date length cannot be > 10
| Explanation: An invalid date was specified in the CHKDATE instruction. Valid date formats are YYMMDD,
| YY/MM/DD, YYYYMMDD, YYYY/MM/DD, DDMMYY, DD/MM/YY, DDMMYYYY, and DD/MM/YYYY.
| System action: OCL terminates.
| User response: Correct the date, then resubmit the job.
| EQQCL64E Date not valid: date length cannot be < 6
| Explanation: An invalid date was specified in the CHKDATE instruction. Valid date formats are YYMMDD,
| YY/MM/DD, YYYYMMDD, YYYY/MM/DD, DDMMYY, DD/MM/YY, DDMMYYYY, and DD/MM/YYYY.
| System action: OCL terminates.
| User response: Correct the date, then resubmit the job.
| EQQCL65E Date not valid: format not recognized
| Explanation: An invalid date was specified in the CHKDATE instruction. Valid date formats are YYMMDD,
| YY/MM/DD, YYYYMMDD, YYYY/MM/DD, DDMMYY, DD/MM/YY, DDMMYYYY, and DD/MM/YYYY.
| System action: OCL terminates.
| User response: Correct the date, then resubmit the job.
56
TME 10 OPC Messages and Codes
EQQCL66E Ÿ EQQCL6DE
| EQQCL66E Date not valid: it's not in the YYYYMMDD format
| Explanation: The date supplied is not in the YYYYMMDD format.
| System action: OCL terminates.
| User response: Correct the date, then resubmit the job.
| EQQCL67E Year year must be included between 1996 and 2999
| Explanation: The date specified in the CHKDATE instruction is outside the valid range 1996–2999.
| System action: OCL terminates.
| User response: Correct the date, then resubmit the job.
| EQQCL68E Month month must be included between 01 and 12
| Explanation: The date specified in the CHKDATE instruction is invalid; it is not in the range 01–12.
| System action: OCL terminates.
| User response: Correct the date, then resubmit the job.
| EQQCL69E Day day must be included between 01 and last_day
| Explanation: The date specified in the CHKDATE instruction is invalid. The value of day day must be in the range
| 01–last_day. last_day is the last day of the month specified in the input date.
| System action: OCL terminates.
| User response: Correct the date, then resubmit the job.
| EQQCL6AE Status invalid: it can be: C, E, D, P, S, U or W
| Explanation: An invalid occurrence status was specified in the CHKAPPL instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL6BE Occurrence name can't be '*'
| Explanation: An invalid occurrence ID was specified.
| System action: OCL terminates.
| User response: Correct the APPL keyword, then resubmit the job.
| EQQCL6CE Alert parameter can be YES or NO
| Explanation: An invalid ALERT keyword was specified.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL6DE User id must be specified for alerting
| Explanation: The USER keyword is required with ALERT(YES).
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
Chapter 5. EQQCLnnn Messages
57
EQQCL6EE Ÿ EQQCL6LE
| EQQCL6EE Not possible to issue the WTO
| Explanation: OCL tried to invoke the IPOWTO program, but a problem occurred.
| System action: OCL terminates.
| User response: Make sure that the IPOWTO program is available to OCL, then resumbit the job.
| EQQCL6FE Invalid cmd command
| Explanation: cmd can be only SRSTAT, OPSTAT, or WSSTAT.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL6GE Variable table not found in OPC database
| Explanation: The variable table specified in the INIT instruction does not exist in the OPC database.
| System action: OCL terminates.
| User response: Specify a valid variable table in the INIT instruction, then resubmit the job.
| EQQCL6HE Internal successor operation not found: s_opnum
| Explanation: OCL tried to release an internal successor, but a problem occurred. s_opnum is the successor
| operation number.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL6IE Not possible to execute PIFTEST program
| Explanation: OCL could not to run the PIFTEST program.
| System action: OCL terminates.
| User response: Make sure that the PIFTEST load module is available to OCL, then resubmit the job.
| EQQCL6JE New jobname invalid or missing
| Explanation: A valid NEWJOB keyword must specified in the CHGJOB instruction.
| System action: OCL terminates.
| User response: Specify a valid NEWJOB keyword, then resubmit the job.
| EQQCL6KE Cannot list the workstations
| Explanation: OCL tried to list the workstations defined in the OPC Workstation database, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL6LE Not possible to modify operation opnum of occurrence appl
| Explanation: OCL tried to modify operation opnum in the occurrence appl, but a problem occurred.
| System action: OCL terminates.
| User response: Refer to the messages in the OPC message log, and contact your IBM representative.
58
TME 10 OPC Messages and Codes
EQQCL6ME Ÿ EQQCL6SE
| EQQCL6ME Specify the OPNO() keyword or specify the default operation number
| Explanation: The OPNO keyword is not specified. OCL tried to use the default operation number, which is not
| specified in the initialization parameter DEFOPNO.
| System action: OCL terminates.
| User response: Specify the OPNO keyword or the default operation number in the initialization parameter
| DEFOPNO.
| EQQCL6NE Not possible to modify the operation status: OPNO(opnum)
| Explanation: OCL tried to modify the status of operation opnum, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL6OE New jobname is blank
| Explanation: The NEWJOB keyword was not specified in the CHGJOB instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL6PE Not possible to change the jobname
| Explanation: OCL tried to change the jobname of an operation, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL6QE Predecessor operation not found: preopnum
| Explanation: OCL tried to add a predecessor that does not exist
| System action: OCL terminates.
| User response: Verify the PREOPNO keyword or the initialization parameter DEFPREOPNO. Correct the
| instruction, then resubmit the job.
| EQQCL6RE Not possible to modify the operation opnum
| Explanation: OCl tried to modify operation opnum, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL6SE Can't define the pred. for operation opnum: PREOPNO(p_opnum) APPL(p_appl)
| Explanation: OCL tried to add a new predecessor to operation opnum.
| p_opnum
| p_appl
The predecessor operation number
The predecessor occurrence ID
| System action: OCL terminates.
| User response: Contact your IBM representative.
Chapter 5. EQQCLnnn Messages
59
EQQCL6TE Ÿ EQQCL70E
| EQQCL6TE Can't have a dependency on itself: PREAPPL(p_appl) PREIA(iadt)
| Explanation: In the long term plan, an occurrence cannot have a predecessor with the same occurrence ID and
| input arrival date and time.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL6UE Not possible to create a new dependency: PREAPPL(preappl)
| Explanation: OCl tried to define a new dependency in an application occurrence in the long term plan, but a problem
| occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL6VE Operation not found: opnum
| Explanation: Operation opnum does not exist in the occurrence to be modified.
| System action: OCL terminates.
| User response: Verify the OPNO keyword or the default operation number in the initialization parameter DEFOPNO.
| Correct the instruction, then resubmit the job.
| EQQCL6WE Not possible to delete the dependency definition
| Explanation: OCL tried to delete a predecessor, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL6XE Special resource name must be supplied
| Explanation: RESNAME is a required keyword.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL6YE Special resource usage must be supplied
| Explanation: RESUSAGE is a required keyword.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL6ZE ONERROR action can be Y or N
| Explanation: An invalid ONERROR keyword was specified.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL70E Not possible to add the special resource: RESNAME(res_name)
| Explanation: OCL tried to add the special resource res_name, but a problem occurred.
| System action: OCL terminates.
| User response: Refer to the messages in the OPC message log, and contact your IBM representative.
60
TME 10 OPC Messages and Codes
EQQCL71E Ÿ EQQCL78E
| EQQCL71E OPNO() and EXCLOP() are mutually exclusive keywords
| Explanation: OPNO and EXCLOP are mutually exclusive keywords.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL72E Can't release the successor of operation opnum: APPL(s_appl) OPNO(s_opnum)
| Explanation: OCL tried to release an external successor of operation opnum, but a problem occurred.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL73E You can specify only one operation number
| Explanation: Only one operation number is accepted in the OPNO keyword.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL74E Default operation number is not specified (DEFOPNO parameter)
| Explanation: OCL is trying to release an internal successor. OCL would use the default operation number as an
| internal predecessor of this operation, but the default operation number was not specified in the DEFOPNO parameter
| of the OCL parmlib.
| System action: OCL terminates.
| User response: Specify the DEFOPNO parameter in the OCL parmlib.
| EQQCL75E OPNO() cannot be equal to DEFOPNO initialization parameter: opnum
| Explanation: OCL is trying to release an internal successor of operation opnum. It would use the default operation
| number as an internal predecessor of this operation, but the value of OPNO must not be the same as the default
| operation number.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL76E Required keyword(s) missing. Specify the INIT instruction
| Explanation: The variable table or the OPC subsystem name was not supplied.
| System action: OCL terminates.
| User response: Specify the INIT instruction before the UPD or SETUPD instructions, then resubmit the job.
| EQQCL77E Can't define the default operation number opnum as a predecessor of s_opnum
| Explanation: OCL tried to add the default operation number opnum as a predecessor of s_opnum. s_opnum is the
| internal successor to be released by the RELOP instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL78E Can't release the successor operation: s_opnum
| Explanation: OCL tried to release an internal successor, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
Chapter 5. EQQCLnnn Messages
61
EQQCL79E Ÿ EQQCL7GE
| EQQCL79E Can't delete the special resource: res_name OPNO(opnum)
| Explanation: OCL tried to delete the special resource res_name from the operation opnum.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL7AE Occurrence ID must be supplied
| Explanation: APPL is a required keyword.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL7BE OPC calendar not found: cal
| Explanation: The calendar cal was not found in the OPC Calendar database.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL7CE Specify the PREOPNO() keyword or the default operation number
| Explanation: OCL is adding a new operation in an application occurrence. It tried to define the internal predecessor
| of this operation, but neither the PREOPNO keyword nor the default operation number was specified.
| System action: OCL terminates.
| User response: Specify the PREOPNO keyword or the default operation number in the OCL parmlib.
| EQQCL7DE Date is blank
| Explanation: OCL tried to determine whether an input date corresponds to a free day, but the date is blank.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL7EE Valid values for OPCVER are 1 and 2
| Explanation: The initialization parameter OPCVER is neither 1 nor 2.
| System action: OCL terminates.
| User response: Correct the parameter, then resubmit the job.
| EQQCL7FE Not possible to allocate dataset: dsname(WTOIN)
| Explanation: OCL tried to allocate the member WTOIN in the dataset dsname, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL7GE Valid values for TSOCMD parameter are YES and NO
| Explanation: The initialization parameter TSOCMD is neither YES nor NO.
| System action: OCL terminates.
| User response: Correct the parameter, then resubmit the job.
62
TME 10 OPC Messages and Codes
EQQCL7HE Ÿ EQQCL7KE
| EQQCL7HE Not possible to write the message on dataset: dsname(WTOIN)
| Explanation: OCL tried to the message text of the WTOR in the member WTOIN of dataset dsname.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL7IE Invalid parameter: parameter
| Explanation: An invalid parameter was specified in the MODOP instruction.
| System action: OCL terminates.
| User response: Correct the instruction, then resubmit the job.
| EQQCL7JE Not possible to modify the occurrence appl
| Explanation: OCL tried to modify the occurrence appl, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
| EQQCL7KE Can't update the Log dataset
| Explanation: OCL tried to write a new record in the log dataset, but a problem occurred.
| System action: OCL terminates.
| User response: Contact your IBM representative.
Chapter 5. EQQCLnnn Messages
63
64
TME 10 OPC Messages and Codes
EQQD001E Ÿ EQQD011E
Chapter 6. EQQDnnn Messages
EQQD001E INVALID VALUE SPECIFIED FOR REPORT SELECTION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
If you want a report, you must specify a Y; if you do not want a report, you must specify an N.
EQQD002E START AND END DATES MUST NOT BE THE SAME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQD003I ENTER END AGAIN TO EXIT, OR PRESS ENTER TO PRINT
Explanation: You can either cancel the print request and leave this panel by entering END again, or print the
specified reports by pressing ENTER.
System action: The system waits for you to respond.
User response: Enter END or press ENTER.
EQQD004E END TIME MUST BE LATER THAN START TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQD005E END DATE MUST BE LATER THAN START DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQD006E THE END TIME MUST BE A VALUE 00.01 TO 24.00
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQD007E SPECIFY A (ALL DAYS) OR W (WORKDAYS ONLY)
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQD008E THE EXTENSION TIME SPECIFIED MAY NOT BE > 21 DAYS OR 504 HOURS
Explanation: The extension time you specified is greater than 21 days (504 hours), the maximum extension time
allowed.
System action: The system waits for you to respond.
User response: Enter a valid extension time.
EQQD009E A MINUTE VALUE GREATER THAN 60 IS NOT ALLOWED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQD010E EXTENSION TIME MUST BE IN THE FORM HHHMM
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The valid extension time format is HHHMM, where HHH is 000 through 504, and MM is 00 through 59.
EQQD011E SPECIFY EITHER EXTENSION OR END DATE AND TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You extend a plan period by specifying either an extension length, or an end date and time; not both.
 Copyright IBM Corp. 1991, 1998
65
EQQD012E Ÿ EQQD020E
EQQD012E END DATE OR EXTENSION LENGTH MUST BE FILLED IN
Explanation: Data entry error; see “Data Entry Errors” on page 2.
To extend a plan period, you must specify either an end date and time or an extension length.
EQQD013E A START DATE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You must specify a start date because no current plan exists.
EQQD014E A CURRENT PLAN ALREADY EXISTS FOR THE SPECIFIED PERIOD
Explanation: You specified a start date and time for a current plan when a current plan already exists.
System action: The system waits for you to respond.
User response: Blank out the start date and time, and enter a valid extension length.
EQQD015E NO CURRENT PLAN EXISTS, SPECIFY START DATE AND TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
To create a current plan, you must specify a start date and time.
EQQD016E NO CURRENT PLAN EXISTS, FUNCTION CANNOT BE USED
Explanation: You have attempted to use a function that requires the existence of a current plan.
System action: The system waits for you to respond.
User response: Check why a current plan does not exist.
EQQD017E SPECIFIED PERIOD MUST BE WITHIN CURRENT PLAN PERIOD
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The start and end times must be within the current plan start and end times.
EQQD018E PLAN START MUST BE EQUAL TO OR GREATER THAN CURRENT PLAN END
Explanation: The start of the future trial plan cannot be before the end of the current plan.
System action: The system waits for you to respond.
User response: Enter a valid start date and time.
| EQQD019E INVALID VALUE SPECIFIED FOR COPY VSAM USAGE SELECTION
| Explanation: Data entry error; see “Data Entry Errors” on page 2.
| User response: To copy VSAM usage data, specify Y; otherwise, specify N.
EQQD020E END DATE AND TIME MUST BE LATER THAN CURRENT PLAN END
Explanation: When extending the current plan the end date and time must be later than the end of the current plan.
System action: The system waits for you to respond.
User response: Enter an end date and time that is later than current plan end.
66
TME 10 OPC Messages and Codes
EQQD100E Ÿ EQQD105E
EQQD100E CATALOG MANAGEMENT TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE
Explanation: A queue element did not contain the correct eye catcher or version number.
System action: The catalog management task does not process the invalid element, but continues normal
processing.
User response: Contact your system programmer.
System programmer response: Save the OPC/ESA message log containing this message, then contact your IBM
representative.
EQQD101I CATALOG MANAGEMENT INITIALIZATION COMPLETE
Explanation: The catalog management task has successfully completed its initialization.
System action: Catalog management processing starts.
User response: None.
EQQD102E CATALOG MANAGEMENT INITIALIZATION FAILED
Explanation: The catalog management task could not acquire the resources needed for normal operation.
System action: Catalog management processing is terminated.
Problem determination: Review previous messages on the OPC/ESA message log.
User response: Contact your systems programmer.
System programmer response: Correct all errors and either restart the catalog management subtask, or restart
OPC/ESA.
EQQD104E CATALOG MANAGEMENT ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT
DQE
Explanation: An abend prevented the catalog management task from processing a queue element.
System action: MVS recovery/termination is requested to generate a dump. The catalog management task attempts
to continue normal processing.
Problem determination: Review the OPC/ESA message log dataset, the BEX diagnostic dataset, and the dump
dataset to determine the cause of the problem.
User response: Contact your systems programmer.
System programmer response: Save the MLOG, dump and BEX datasets, then contact your IBM representative.
EQQD105E CATALOG MANAGEMENT QUEUE POINTER IS DESTROYED. DSCQ IS LOST
Explanation: The catalog management task abended while processing elements on the DSCQ because queue
chaining is invalid.
System action: MVS recovery/termination is requested to generate a dump. The catalog management task attempts
to continue normal processing.
Problem determination: Review the OPC/ESA message log dataset, the BEX diagnostic dataset, and the dump
dataset to determine the cause of the problem.
User response: Contact your systems programmer.
System programmer response: Save the MLOG, dump and BEX datasets, then contact your IBM representative.
Chapter 6. EQQDnnn Messages
67
EQQD107E Ÿ EQQD112I
EQQD107E OPC/ESA IS NOT AUTHORIZED TO DELETE DATASET DSNAME IN CATALOG CAT.
Explanation: An attempt was made to scratch this dataset, but OPC/ESA is not authorized to do so.
System action: OPC/ESA will set error status for the catalog management action of this dataset. Also, the catalog
management status for this operation will be set to error.
User response: Contact your systems programmer.
System programmer response: If OPC/ESA should be authorized to delete the dataset, contact your security
administrator.
EQQD108E OPC/ESA WAS UNABLE TO COLLECT CATALOG MANAGEMENT INFORMATION FOR JOB JNM,
JOB ID JOBID. RETURN CODE IS RC, REASON CODE IS RSN.
Explanation: An error occurred when OPC/ESA tried to collect information about datasets created in this operation.
System action: This information is passed to the controller, and the catalog management status for the operation will
be set to N (cancelled).
User response: Contact your systems programmer.
System programmer response: The problem may be related to I/O errors on a catalog. If this is not the case,
please contact your IBM representative.
EQQD109E CATALOG MANAGEMENT INITIALIZATION FAILED. THE REASON IS THAT THERE IS NO
CONNECTION ESTABLISHED FOR TRANSFERRING DATASET INFORMATION TO THE
CONTROLLER.
Explanation: The catalog management task could not start, as it did not find a connection between this tracker and
the controller.
Problem determination: Check the OPC/ESA parmlib members involved.
User response: Contact your system programmer.
System programmer response: Make sure this tracker is connected to the controller by either NCF or XCF, and
that the connection has been established.
EQQD110I DATASET DSN WAS UNCATALOGED. THE DATASET RESIDES ON VOLUME VOL. APPLICATION IS
AD, INPUT ARRIVAL IS IA, OPERATION NUMBER IS OPNO, AND JOBNAME IS JNM.
Explanation: Catalog management has uncataloged this dataset. The dataset still exists, and resides on the volume
indicated in the message.
System action: Normal processing continues.
User response: None.
EQQD111I DATASET DSN WAS UNCATALOGED. APPLICATION IS AD, INPUT ARRIVAL IS IA, OPERATION
NUMBER IS OPNO, AND JOBNAME IS JNM. THE DATASET RESIDES ON THE FOLLOWING
VOLUMES
Explanation: Catalog management uncataloged this dataset. The dataset still exists, and resides on the volumes
indicated by EQQD112I messages.
System action: Normal processing continues.
User response: None.
EQQD112I VOLSER VOL.
Explanation: This list of volume numbers always follows message EQQD111I, and identifies a volume serial
number. This message is repeated for each volume that the uncataloged dataset resides on.
System action: Normal processing continues.
User response: None.
68
TME 10 OPC Messages and Codes
EQQD114E Ÿ EQQD119I
EQQD114E OPC/ESA COULD NOT DELETE MIGRATED DATASET DSN. APPLICATION IS AD, INPUT ARRIVAL
IS IA, OPERATION NUMBER IS OPNO, AND JOBNAME IS JNM.
Explanation: When OPC/ESA tried to locate the dataset, it resided on logical volume MIGRAT. OPC/ESA has tried
to recall the dataset and waited the time given in the CHSMWAIT keyword. As the dataset has not been recalled
within the time given, the catalog management status for the dataset and the operation will be set to error.
System action: The catalog management action ends in error for this operation.
User response: Delete the dataset manually. Also, inform your system programmer that OPC/ESA was not able to
delete a migrated dataset.
System programmer response: Increase the time interval in the CHSMWAIT keyword.
EQQD115I THE CATALOG MANAGEMENT EXIT XIT TERMINATED ABNORMALLY WHEN IT WAS CALLED. SEE
THE SYSMDUMP DATASET FOR MORE INFORMATION. THE EXIT HAS BEEN MARKED AS NOT
EXECUTABLE, AND WILL NOT BE CALLED AGAIN.
Explanation: An abend has occurred in the exit. TME 10 OPC has flagged the exit as not executable, and will not
try to call it again.
System action: Processing continues. The exit will not be called again.
User response: Contact your system programmer.
System programmer response: Analyze the dump generated for the problem, and correct the failing exit. When
you have corrected the errors, load the exit again by stopping and then starting the catalog management subtask, or
by stopping and starting the TME 10 OPC address space.
EQQD116I THE CATALOG MANAGEMENT ACTION FOR DATASET DSN HAS BEEN DISCARDED.
APPLICATION IS AD, INPUT ARRIVAL IS IA, OPERATION NUMBER IS OPNO, AND JOBNAME IS
JNM.
Explanation: Due to a dialog status change, the catalog management action for this dataset has been discarded.
System action: OPC/ESA updates the dataset status to D (discarded).
User response: None.
EQQD118I A JOBLOG FOR JOB JNM HAS ARRIVED AT THE CONTROLLER. CATALOG MANAGEMENT IS
NOT ACTIVE AT THE CONTROLLER SO THE JOBLOG IS DISCARDED.
Explanation: A joblog or joblog status record has been sent to the controller but catalog management has not been
activated at the controller so joblogs can not be received.
System action: The joblog is discarded. Processing continues.
System programmer response: Specify CATMGT=Y in the OPCOPTS statement for the controller if you want to
store joblogs.
EQQD119I A DATASET COLLECTION EVENT HAS BEEN ENCOUNTERED. THE EVENT WILL NOT BE
PROCESSED BECAUSE THE CATALOG MANAGEMENT FUNCTION IS NOT ACTIVE AT THE
CONTROLLER. JOBNAME IS JNM, JOB ID IS JID AND NODE NAME IS NODE
Explanation: An event describing datasets to be managed for a job by catalog management has been passed to the
controller. However, catalog management is not active at the controller. The event information will not be saved by
the controller, and no catalog management will be performed for this operation.
System action: The event is discarded. No further catalog management action is taken for the operation.
System programmer response: If catalog management should be active, specify CATMGT(YES) in the controller's
OPCOPTS statement, and then restart the controller.
Chapter 6. EQQDnnn Messages
69
EQQD120I Ÿ EQQD126I
EQQD120I OPC HAS PROCESSED KEYWORD CATACT IN THE OPCOPTS STATEMENT. THE KEYWORD IS
IGNORED, BECAUSE OPC HAS BEEN DEFINED AS A TRACKER SYSTEM.
Explanation: The CATACT keyword is a controller keyword. When you define it for a tracker system it is ignored.
System action: The keyword is ignored.
System programmer response: If you do not want this message to be issued, remove the keyword from the
OPCOPTS statement and restart the system.
EQQD121W OPC/ESA WILL NOT TRY TO PERFORM ANY AUTOMATIC RECOVERY ACTION FOR
APPLICATION AD, WITH INPUT ARRIVAL IA, OPERATION NUMBER OPNO.
Explanation: The catalog management for this operation was unsuccessful. Therefore OPC/ESA will not
automatically initiate auto recovery for this operation.
System action: No automatic recovery attempt is done for the operation.
User response: The automatic recovery for this operation has to be manually initiated from the MCP dialog.
System programmer response: None.
EQQD123I NO CATALOG MANAGEMENT ACTIONS HAVE BEEN TAKEN FOR OPERATION OPNO IN
APPLICATION AD BECAUSE THE PRE-CATALOG-MANAGEMENT EXIT HAS DISCARDED THE
PROCESSING. EXIT NAME IS XIT.
Explanation: The pre-catalog-management exit has suppressed catalog management for all datasets in this
operation.
System action: Normal processing continues.
User response: None.
EQQD124E OPC/ESA COULD NOT PROCESS DATASET DSN. CATALOG NAME IS CAT. REASON FOLLOWS
Explanation: OPC/ESA tried to locate and process a dataset in the catalog indicated in the message, but failed to
perform the actions against the dataset. The reason is described in message EQQD125 that follows this message.
System action: The catalog management status for the dataset is set to error.
User response: Contact your system programmer.
System programmer response: Check message EQQD125.
EQQD125I CMTXT
Explanation: This message describes why TME 10 OPC could not process the dataset that was identified in
message EQQD124. It contains messages issued by other MVS products that were used by TME 10 OPC to process
the dataset.
System action: The catalog management status for the operation is set to error.
User response: Contact your system programmer.
System programmer response: Review any messages issued by the non-TME 10 OPC products and take the
action described in the documentation for each product concerned.
EQQD126I OPC HAS ACT DATASET DSN IN CATALOG CAT. JOBNAME IS JNM, JOB ID IS JID.
Explanation: OPC/ESA has performed the action described in the message for this dataset. The catalog name in
the message is the catalog that OPC/ESA has updated. The catalog name is only printed when a JOBCAT or
STEPCAT was specified in the JCL, otherwise the catalog name contains ********.
System action: Normal processing continues.
User response: None.
70
TME 10 OPC Messages and Codes
EQQD128I Ÿ EQQD132E
EQQD128I THE CATALOG MANAGEMENT EXIT LOAD MODULE MODULE COULD NOT BE LOADED.
Explanation: The catalog management subtask could not load the EQQUX008 exit.
System action: The catalog management exit will not be used.
User response: Contact your system programmer.
System programmer response: If the exit should be called by OPC/ESA, make sure that the exit load module is
stored in a library that can be reached by OPC/ESA. Also check the setting of the EXIT initialization statement for
keywords LOAD08 and CALL08. If the exit should be loaded, correct all errors and restart the catalog management
subtask.
EQQD129E A REQUEST TO CALL EXIT XIT HAS BEEN MADE IN THE CATALOG MANAGEMENT SUBTASK.
DUE TO A PREVIOUS ABNORMAL TERMINATION IN THE EXIT, IT WILL NOT BE CALLED AGAIN.
Explanation: The exit that was going to be called in the catalog management subtask has terminated abnormally in
a previous call. Due to this, the exit was flagged as not usable, and will not be called.
System action: The catalog management status for the operation is set to error, and no datasets are deleted or
uncataloged.
User response: Contact your systems programmer.
System programmer response: Correct the module and restart the catalog management subtask.
EQQD130E THE JOBLOG RETRIEVAL EXIT USRX HAS ABENDED WHILE PROCESSING JOB JNM JOBNUM
JID, OPERATION OPN IN APPLICATION APPL WITH IA IA SCHEDULED ON WORKSTATION
WSNAME.
THE EXIT IS MARKED AS NOT USABLE, AND WILL NOT BE CALLED AGAIN
Explanation: The exit abended while processing. TME 10 OPC will not try to call it again unless the Catalog
Management task is restarted. The exit will be flagged as not executable.
System action: The processed operation will get a joblog-request status of Error. Dialog users will not be able to
use the step-level restart function or browse-joblog function for this or other jobs until the error has been corrected.
System programmer response: Investigate the SYSxDUMP dataset, correct the failing exit, and restart the Catalog
Management task or TME 10 OPC.
EQQD131E THE JOBLOG RETRIEVAL EXIT USRX HAS RETURNED RC=8 WITH ERROR TEXT ETXT
WHEN PROCESSING JOB JNMJOBNUM JID. FOR OPERATION NUMBER OPN
IN APPLICATION APPL WITH IA IA SCHEDULED ON WORKSTATION WSNAME.
Explanation: TME 10 OPC could not retrieve joblog data as requested for this job. DELAYED or DELAYEDEXIT is
defined for JOBLOGRETRIEVAL.
System action: The processed operation will get a joblog-request status of Error. Dialog users will not be able to
step restart this operation or browse the joblog.
System programmer response: Correct all errors in the exit and restart the Catalog Management task.
EQQD132E THE JOBLOG RETRIEVAL EXIT USRX HAS RETURNED RC=12 WITH ERROR TEXT ETXT
WHEN PROCESSING JOB JNM JOBNUM JID, FOR OPERATION OPN IN APPLICATION APPL WITH
IA IA
SCHEDULED ON WORKSTATION WSNAME
THE EXIT IS MARKED AS NOT USABLE, AND WILL NOT BE CALLED AGAIN
Explanation: The exit could not retrieve joblog data as requested for this job. DELAYED or DELAYEDEXIT is
defined for JOBLOGRETRIEVAL. The exit has requested that TME 10 OPC not call it again.
System action: The processed operation will get a joblog-request status of Error. The exit will not be called again.
System programmer response: Correct all errors in the exit and restart the Catalog Management task or the
address space.
Chapter 6. EQQDnnn Messages
71
EQQD133I Ÿ EQQD135E
EQQD133I THE JOBLOG FOR JNM JID FOR OPERATION OPN IN APPLICATION APPL WITH IA IA SCHEDULED
ON WORKSTATION WSNAME DOES NOT CONTAIN ALL DATASETS
REQUIRED BY THE OPC/ESA CATALOG MANAGEMENT FUNCTION
Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT or DELAYED is
specified for JOBLOGRETRIEVAL. The Catalog Management task has determined that the joblog for the current job
does not contain all joblog datasets required by TME 10 OPC. The necessary datasets are JESJCL and JESYSMSG,
one or both of the datasets are missing.
System action: The Catalog Management task processing continues. The joblog-retrieval status for the operation is
set to Error.
System programmer response: Verify the JES installation setup or that the job does not suppress JESJCL and/or
JESYSMSG files from being created.
EQQD134E CATALOG MANAGEMENT TASK COULD NOT FIND ANY SYSOUT DATA SETS FOR JOB JNM(JID)
IN APPLICATION ADID.
Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT is specified for
JOBLOGRETRIEVAL. CM has tried to retrieve SYSOUT datasets for the requested job but no datasets have been
returned by the JES.
System action: No more attempts to retrieve SYSOUT datasets are made for this job. CM attempts to continue
normal operation with the next request. The joblog-retrieval status for this operation will be set to Error.
Problem determination: In a JES3 system, check that the SYSOUT class is defined as external writer classes to
JES3.
Operator response: Determine the current status of the job. If necessary, set the correct status for the job
manually.
System programmer response: If necessary, correct any incorrectly specified operands in the JOBLOGRETRIEVAL
and JOBLOGDISP keywords and then restart the Catalog Management task or the address space.
EQQD135E UNEXPECTED SUBSYSTEM REQUEST RETURN CODES FOR JOB JNM (JOBNUM) IN
APPLICATION ADID.
REQUEST TYPE: TYPE, R15: R15, SSOBRETN: SSOBRETN
Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT or DELAYED is
specified for JOBLOGRETRIEVAL. An error occurred when the Catalog Management task was retrieving information
from JES for job JOBNAME. The information request is either a status request (request type = CS), or a process
SYSOUT request (request type = SO). R15 and SSOBRETN are return codes from JES. CM issues this message
because this combination of return codes can not be handled by the task.
System action: This error message is written to the tracker messages log, EQQMLOG. CM stops processing the
current joblog-request, and the joblog-retrieval status is set to Error in the Current Plan.
User response: Step-level restart the job manually. Then contact your system programmer.
System programmer response: Save the EQQMLOG containing this error message and contact your IBM
representative.
72
TME 10 OPC Messages and Codes
EQQD136E Ÿ EQQD139E
EQQD136E CM ALLOCATION OF A SYSOUT DATA SET FAILED FOR JNM(JID) IN APPLICATION ADID.
DYNAMIC ALLOCATION ERROR CODE: RETC, INFORMATION REASON CODE: RSNC
Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT or DELAYED is
specified for JOBLOGRETRIEVAL. The Catalog Management task could not allocate a SYSOUT dataset for the job
JOBNAME(JOBNUM). The dynamic allocation error and information reason codes are given in hexadecimal.
System action: This error message is written to the tracker MLOG. CM stops processing the current joblog-request,
and the joblog-retrieval status is set to Error Completion in the Current Plan.
Problem determination: Use the DYNALLOC return code and reason code to determine the cause of the error. For
more information, refer to the appropriate DYNALLOC documentation for the currently active MVS system.
User response: Step-level restart the job manually. Then contact your systems programmer.
System programmer response: Look up the meaning of the dynamic allocation error and information reason codes,
and take appropriate action.
EQQD137E CM UNALLOCATION OF A SYSOUT DATA SET FAILED FOR JNM (JID)
IN APPLICATION ADID.
DYNAMIC ALLOCATION ERROR CODE: RETC, INFORMATION REASON CODE: RSNC
Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT or DELAYED is
specified for JOBLOGRETRIEVAL. An error occurred when the Catalog Management task was deallocating a
SYSOUT dataset for the job JOBNAME(JOBNUM). The dynamic allocation error and information reason codes are
given in hexadecimal.
System action: This error message is written to the tracker MLOG. CM stops processing the current joblog-retrieval
request, and the joblog-retrieval status is set to Error Completion in the Current Plan.
Problem determination: Use the DYNALLOC return code and reason code to determine the cause of the error. For
more information, refer to the appropriate DYNALLOC documentation for the currently active MVS/ESA system.
User response: Step-level restart the job manually. Then contact your systems programmer.
System programmer response: Look up the meaning of the dynamic allocation error and information reason codes,
and take appropriate action.
EQQD138E CM OPEN OF A SYSOUT DATA SET FAILED FOR JNM(JID) IN APPLICATION ADID.
DDNAME: DDNAME, DSNAME: DSNAME
Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT or DELAYED is
specified for JOBLOGRETRIEVAL. An error occurred when the Catalog Management task was trying to open a
SYSOUT dataset for the job JOBNAME(JOBNUM).
System action: This error message is written to the tracker MLOG. CM stops processing the current joblog-request,
and the joblog-retrieval status is set to Error Completion in the Current Plan.
User response: Step-level restart the job manually. Then contact your systems programmer.
System programmer response: Determine the reason for the open failure and correct all errors.
EQQD139E CM ABEND CODE ABCODE OPENING A SYSOUT DATA SET FOR JOBNAME(JOBNUM) IN
APPLICATION ADID, DDNAME: DDNAME, DSNAME: DSNAME
Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDSYSOUT or DELAYED is
specified for JOBLOGRETRIEVAL. An serious error occurred when the Catalog Management task tried to open a
SYSOUT dataset for the job JOBNAME(JOBNUM).
System action: This error message is written to the tracker message log, EQQMLOG. CM stops processing the
current joblog-request, and the joblog-retrieval status is set to Error in the Current Plan.
User response: Step-level restart the job manually. Then contact your systems programmer.
System programmer response: Determine the reason for the abend and correct all errors.
Chapter 6. EQQDnnn Messages
73
EQQD140E Ÿ EQQD144I
EQQD140E THE JOBLOG RETURNED BY EXITNAME FOR JOBNAME JOBNUM IN APPLICATION APPL IS
INCOMPLETE. FOLLOWING DATA NOT FOUND: DDNAME1, DDNAME2
Explanation: A joblog-retrieval request has been issued to a tracker where DELAYEDEXIT or DELAYED is specified
for JOBLOGRETRIEVAL. The Catalog Management makes a basic validity check of what is passed back from the
joblog-retrieval exit. It will check for the existence of a jobcard (which is always part of the JESJCL sysout dataset)
and the IEF375I/IEF376I messages (which are always part of the JESYSMSG dataset). DDNAME(s) associated with
the missing data are displayed.
System action: This error message is written to the tracker message log, EQQMLOG. CM stops processing the
current joblog-retrieval request, and the joblog-retrieval status is set to Error in the Current Plan.
User response: Step-level restart this operation manually. Then contact your system programmer.
System programmer response: Verify that JES installation setup or the job does not suppress JESJCL and/or
JESYSMSG files from being created. Verify the logic of the joblog retrieval exit.
EQQD141E OPC/ESA COULD NOT RETRIEVE REQUIRED DATA FROM THE HISTORY DATABASE.
Explanation: OPC/ESA tried to access operation data in the DB2 history database but failed. The reason is
described in message EQQD142, which follows this message.
System action: Processing continues, but the required data is not passed to the caller.
User response: Contact your system programmer.
System programmer response: Check message EQQD142.
EQQD142I DB2TXT
Explanation: This message describes why TME 10 OPC could not access the DB2 history database. It contains
messages issued by the DB2 system.
System action: Processing continues.
User response: Contact your system programmer.
System programmer response: Review the messages issued by DB2 and take the action described in the DB2
documentation.
EQQD143I DB2 SYSTEM DB2 HAS STOPPED. THE HISTORY FUNCTION IS NOT AVAILABLE
Explanation: OPC/ESA has discovered that the DB2 system has either stopped or abended. It cannot support
requests for data from the history database.
System action: Processing continues but the history function is not available.
User response: Contact your system programmer.
System programmer response: Restart the DB2 system that stopped or abended.
EQQD144I DB2 SYSTEM DB2 IS AVAILABLE
Explanation: The DB2 system containing OPC/ESA history data is available.
System action: Processing continues.
User response: None.
System programmer response: None.
74
TME 10 OPC Messages and Codes
EQQD145E Ÿ EQQD147E
EQQD145E OBJECT OBJ COULD NOT BE CREATED. REASON FOLLOWS:
Explanation: The initialization program tried to create a table, index or an alias in the history database but failed.
The reason is described in message EQQD142, which follows this message.
System action: Processing is terminated.
User response: Contact your system programmer.
System programmer response: Check message EQQD142.
EQQD146I OBJECT OBJ HAS BEEN CREATED IN THE HISTORY DATABASE
Explanation: The initialization program has successfully created this object in the history database.
System action: Processing continues.
User response: None.
EQQD147E THE SYSIN FILE CONTAINS BAD OR MISSING PARAMETERS
Explanation: The initialization program was unable to create the history database because some SYSIN parameters
are missing or specified incorrectly. The following parameters are required to create the history database:
DBNAME
MAIN
MAINX
OCC
OCCX1
OCCX2
OCCX3
OPR
OPRX1
OPRX2
OPRX3
DS
DSX1
DSX2
DSX3
JL
JLX1
JLX2
JLX3
The database name
The name of OPC/ESA history database main table
The main table index name
The name of the OPC/ESA table that stores occurrence data
Occurrence data index 1
Occurrence data index 2
Occurrence data index 3
The name of the OPC/ESA table that stores operation data
Operation data index 1
Operation data index 2
Operation data index 3
The name of the OPC/ESA table that stores operation data set information
Dataset information index 1
Dataset information index 2
Dataset information index 3
The name of the OPC/ESA table that stores joblog status information
Joblog status information index 1
Joblog status information index 2
Joblog status information index 3
System action: Processing is terminated.
User response: Contact your system programmer.
Chapter 6. EQQDnnn Messages
75
76
TME 10 OPC Messages and Codes
EQQEX01I Ÿ EQQEX05E
Chapter 7. EQQEXnn Messages
EQQEX01I THE EXTERNAL ROUTER TASK HAS BEEN STARTED
Explanation: The external router task has successfully completed initialization. The external router task handles the
interface to the operation-initiation exit, EQQUX009, which is used to start operations at user-defined destinations.
System action: The external router task processing continues.
User response: None.
EQQEX02I THE EXTERNAL ROUTER TASK HAS ENDED
Explanation: The external router task has ended either because the TME 10 OPC controller is in the process of
shutting down or as a result of an operator modify command to terminate this task or a related task.
System action: TME 10 OPC processing continues.
User response: None.
EQQEX03E THE EXTERNAL ROUTER TASK HAS ENDED DUE TO PROCESSING ERRORS
Explanation: The external router task has terminated due to processing errors.
Problem determination: Check the TME 10 OPC message log and the dump datasets for additional information
which describes the problem.
System action: Normal TME 10 OPC processing continues.
User response: Contact your systems programmer.
System programmer response: If the cause of the error is due to a problem in the operation-initiation exit,
EQQUX009, correct the error and restart the TME 10 OPC controller. If the cause of the error cannot be determined
take a dump of the TME 10 OPC address space, retain a copy of the message log and the job tracking datasets and
contact your IBM representative.
EQQEX04W NO ROUTING FOR USER DESTINATIONS IS IN EFFECT
Explanation: The external router task has not been able to load the operation-initiation exit, EQQUX009.
System action: Normal TME 10 OPC processing continues. Operations at user-defined workstations will not be
started.
User response: Contact your systems programmer if the TME 10 OPC controller includes workstations with
user-defined destinations.
System programmer response: Determine why TME 10 OPC was unable to find or load the operation-initiation
exit, EQQUX009. When the problem has been corrected restart the TME 10 OPC controller.
EQQEX05E THE EXTERNAL ROUTER HAS TERMINATED DUE TO AN INITIALIZATION FAILURE
Explanation: The external router task could not acquire the resources required for normal operation.
System action: External router processing is terminated.
Problem determination: Review previous messages in the TME 10 OPC message log.
User response: Contact your system programmer.
System programmer response: Correct all errors and restart TME 10 OPC.
 Copyright IBM Corp. 1991, 1998
77
EQQEX06E Ÿ EQQEX08E
EQQEX06E A SEVERE ERROR IN THE EXTERNAL ROUTER TASK HAS CAUSED ONE OR MORE REQUESTS
TO BE LOST
Explanation: The external router task encountered an error processing elements on the EXAQ. As a result, at least
one queue element has been lost.
System action: MVS/ESA recovery/termination is requested to generate a dump. The external router task attempts
to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
TME 10 OPC administrator response: Save the message log, dump and diagnostic datasets, and contact your IBM
representative.
EQQEX07E THE EXTERNAL ROUTER TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST
REQUEST
Explanation: An abend prevented the external router task from processing a queue element.
System action: MVS/ESA recovery/termination is requested to generate a dump. The external router task attempts
to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
User response: Contact your system programmer.
System programmer response: Save the message log, dump, and diagnostic datasets, and contact your IBM
representative.
EQQEX08E THE EXTERNAL ROUTER TASK HAS IGNORED THE FOLLOWING QUEUE ELEMENT: REQUEST
Explanation: The external router task has detected an invalid queue element on its queue.
System action: The element is discarded from the external router queue. The task continues normal processing.
Problem determination: Review the TME 10 OPC message log dataset.
User response: Contact your system programmer.
System programmer response: Save the message log (EQQMLOG) and the current plan (EQQCPxDS) and
contact your IBM representative.
78
TME 10 OPC Messages and Codes
EQQE000I Ÿ EQQE001E
Chapter 8. EQQEnnn Messages
EQQE000I TOTAL NUMBER OF EVENTS PROCESSED BY THE EVENT MANAGER TASK IS: NUMEV
NUMBER OF EVENTS SINCE THE PREVIOUS MESSAGE IS: NEWEV
EVENT MANAGER QUEUE LENGTH STATISTICS FOLLOW:
TOTAL
Q1
Q2
Q5 Q10 Q20 Q50 Q100 >100
CALLS Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8
| Explanation: This message is issued if the EVENTS statistics are made active, either by specifying the
| STATMSG(EVENTS) keyword in the JTOPTS initialization statement, or by issuing the modify command, /F
| subsys,EVESTA=ON.
| Once activated, this messages is regularly issued by the event manager subtask, until it is deactivated. The interval
| between two messages is calculated as follows:
|
|
Ÿ If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every n
minutes (where n is the STATIM value), if any events have been processed.
|
|
Ÿ Otherwise, if EVELIM is nonzero (in the initial parm or by modify command) then the message is issued
approximately every n events (where n is the EVELIM value).
|
|
Ÿ Otherwise, the message is issued approximately every n events, where n is half the JTOPTS BACKUP keyword
value (default BACKUP is 400).
| This message shows the total number of events processed and how many events have been processed since the
| message was last issued or, if it is the first time it is issued, since the last time the event manager processed the
| events queue.
The message also contains information about how many events were waiting to be processed each time the queue
processing routine was called. The value below the TOTAL heading gives the total number of times that the event
queue was emptied. The values below the Qx headings give the number of times that the length of the queue was in
a particular interval. For example, Q50 gives the number of times that the queue was between 21 and 50 events.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQE001E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG I/O ERROR READING AD DATA BASE
Explanation: ETT was triggered by an event but could not add the associated application due to an I/O-error on the
AD database.
System action: The associated application was not added by ETT, but ETT processing continues normally.
Problem determination: Review the preceding messages in the TME 10 OPC message log dataset to determine
the cause of the error.
User response: Contact your system programmer.
System programmer response: Save the message log dataset containing this error, and contact your IBM
representative.
 Copyright IBM Corp. 1991, 1998
79
EQQE002E Ÿ EQQE003E
EQQE002E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG FIRST OPERATION NOT ON CPU WS,
JOBNAME CANNOT BE REPLACED
Explanation: ETT was triggered by an event but could not add the associated application since the first operation (ie
the operation with the lowest operation number) was not a CPU-operation and ETT's Job Name Replace option was
specified.
System action: The associated application was not added by ETT, but ETT processing continues normally.
Problem determination: Check the AD data base to make sure that the first operation in the application to be added
is a CPU-operation if the Job Name Replace option is used. Or, check the ETT criteria table to make sure that the
correct Job Name Replace option was specified. Or, check that the CPU work station is part of CP since it might
have been added to the WS data base after a new CP was created.
User response: Correct the ETT criteria table or/and the AD data base, or get the CPU work station into the CP.
System programmer response: None.
EQQE003E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG FIRST OPERATION HAS
PREDECESSORS, JOBNAME CANNOT BE REPLACED
Explanation: ETT was triggered by an event but could not add the associated application since the first operation
(that is, the operation with the lowest operation number) had internal predecessor operations, and ETT's Job Name
Replace option was specified.
System action: The associated application was not added by ETT, but ETT processing continues normally.
Problem determination: Check the AD data base to make sure that the first operation in the application to be added
does not have any internal predecessor operations. Or, check the ETT criteria table to make sure that the correct Job
Name Replace option was specified.
User response: Correct the ETT criteria table or/and the AD data base.
System programmer response: None.
80
TME 10 OPC Messages and Codes
EQQE004I Ÿ EQQE005I
EQQE004I CP ENQ LOCK STATISTICS SINCE PREVIOUS MESSAGE FOLLOW:
NAME
NEXCL NSHRD THELD TWAIT AHELD AWAIT
| Explanation: This message is issued if the CP ENQ LOCK statistics are active. This can be done either by
| specifying the STATMSG(CPLOCK) keyword in the JTOPTS initialization statement, or by using the modify command,
| /F subsys,CPQSTA=ON.
| Once activated, this messages is regularly issued by the event manager subtask, until it is deactivated. The interval
| between two messages is calculated as follows:
|
|
Ÿ If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every n
minutes (where n is the STATIM value), if any events have been processed.
|
|
Ÿ Otherwise, if EVELIM is nonzero (in the initial parm or by modify command) then the message is issued
approximately every n events (where n is the EVELIM value).
|
|
Ÿ Otherwise, the message is issued approximately every n events, where n is half the JTOPTS BACKUP keyword
value (default BACKUP is 400).
| This message shows which TME 10 OPC tasks have referred to the current plan data since the last message was
| issued, or if it is the first time it is isuued, since the last time the event manager processed the events queue.
| The message consists of column headers that describe data indicating how often and in what way the current plan
| data set has been referenced. The data values are displayed in the message EQQE005I. The values for each
heading are:
NAME
NEXCL
NSHRD
THELD
TWAIT
AHELD
AWAIT
The
The
The
The
The
The
The
name of the TME 10 OPC task for which data was gathered.
number of times that the task acquired exclusive use of the current plan.
number of times that the task acquired shared use of the current plan.
total amount of time, in seconds, that the task was using the current plan.
total amount of time, in seconds, that the task was waiting to use the current plan.
average amount of time, in seconds, that the task was using the current plan.
average amount of time, in seconds, that the task was waiting to use the current plan.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQE005I NAME NEXCL NSHRD THELD TWAIT AHELD AWAIT
| Explanation: This message is issued together with the message EQQE004I. See the explanation for EQQE004I for
| details about when it is issued.
The message contains information about the use of the current plan dataset by one TME 10 OPC subtask. The
descriptions of the column headings in the previous message, EQQE004I, also describe the variables in this message.
System action: Normal TME 10 OPC processing continues.
User response: None.
Chapter 8. EQQEnnn Messages
81
EQQE006I Ÿ EQQE007I
EQQE006I EVENT MANAGER EVENT TYPE STATISTICS FOLLOW:
TYPE NTOT NNEW TTOT
TNEW
TAVG NAVG
NSUS
| Explanation: This message is issued if the EVENTS statistics are active. This can be done either by specifying the
| STATMSG(EVENTS) keyword in the JTOPTS initialization statement, or by using the modify command, /F
| subsys,EVESTA=ON.
| Once activated, this messages is regularly issued by the event manager subtask, until it is deactivated. The interval
| between two messages is calculated as follows:
|
|
Ÿ If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every n
minutes (where n is the STATIM value), if any events have been processed.
|
|
Ÿ Otherwise, if EVELIM is nonzero (in the initial parm or by modify command) then the message is issued
approximately every n events (where n is the EVELIM value).
|
|
Ÿ Otherwise, the message is issued approximately every n events, where n is half the JTOPTS BACKUP keyword
value (default BACKUP is 400).
|
|
|
|
|
This message consists of column headers that describe measured values that are displayed in the message
EQQE007I that follows. The measured values contain information about the total number of events processed, how
many have been processed since the message was last issued, or, if it is the first time it is isuued, since the last time
the event manager processed the events queue, and the elapsed time that the event manager needed to process the
events.
The values for each heading are:
TYPE
TTOT
NNEW
TTOT
TNEW
TAVG
NAVG
NSUS
The
The
The
The
The
The
The
The
event type for which data was gathered.
total number of events of this type.
number of events of this type since the last message.
total time, in seconds, used to process this event type.
total time, in seconds, used to process this event type since the last message.
average time, in seconds, used to process an event of this type.
average time, in seconds, used to process an event of this type since the last message.
number of times that the Event Manager could not immediately process an event of this type.
The values in the TYPE column will be one of the following:
ALL
1
2
3S
3J
3P
4
5
USER
CATM
OTHR
This line is a total line for all event types.
Reader events.
Job start events.
Step end events.
Job end events.
Job on output queue events.
Dataset print events.
Job purge events.
User generated event, EQQUSINT program or the OPSTAT command.
Catalog Management events.
Other events.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQE007I TYPE NTOT NNEW TTOT
TNEW
TAVG NAVG NSUS
Explanation: This message is issued if STATMSG(EVENTS) has been specified in the JTOPTS initialization
statement. The message contains information about how the Event Manager task processed one type of event. The
descriptions of the column headings in the previous message, EQQE006I, also describe the variables in this message.
System action: Normal TME 10 OPC processing continues.
User response: None.
82
TME 10 OPC Messages and Codes
EQQE008I Ÿ EQQE008I
| EQQE008I READY OPERATIONS QUEUE LENGTH STATISTICS FOLLOW:
|
Q10 Q100 Q1000 Q5000 Q10000 >10000
|
R1 R2 R3 R4 R5
R6
|
OPERATIONS READY AND FOUND WAITING FOR SPECIAL RESOURCES:
|
Q10 Q100 Q1000 Q5000 Q10000 >10000
|
S1 S2 S3 S4 S5
S6
|
OPERATIONS READY TO SELECT A WINNER:
|
Q10 Q100 Q1000 Q5000 Q10000 >10000
|
Q1 Q2 Q3 Q4 Q5
Q6
| Explanation: This message is issued if the WSA statistics are active. This can be done either by specifying the
| STATMSG(WSATASK) keyword in the JTOPTS initialization statement, or by using the modify command, /F
| subsys,WSASTA=ON.
| Once activated, this messages is regularly issued by the event manager subtask, until it is deactivated. The interval
| between two messages is calculated as follows:
|
|
Ÿ If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every n
minutes (where n is the STATIM value), if any events have been processed.
|
|
Ÿ Otherwise, if EVELIM is nonzero (in the initial parm or by modify command) then the message is issued
approximately every n events (where n is the EVELIM value).
|
|
Ÿ Otherwise, the message is issued approximately every n events, where n is half the JTOPTS BACKUP keyword
value (default BACKUP is 400).
| This message shows some statistic information about the operations ready queue list and its handling by the WSA
| task since it was last issued, or, if it is the first time it is isuued, since the last time the event manager processed the
| events queue.
| The first set of variables (R1-R6) gives the number of times that the ready list was found to be within a specific range,
| each time the WSA task processed it to select a “winner” operation (one to be submitted). For example, R1=10
| means that the ready queue list was found 10 times to contain n operations, where n < 10.
| The second set of variables (S1-S6) gives the number of times that the number of operations, read from the ready list
| and found waiting for special resources, was found to be within a specific range. For example, S2=10 means that the
| number of opertaions read and found waiting for special resources was >= 10 and < 100.
| The third set of variables (Q1-Q6) gives the number of times that the number of operations, read from the ready list
| before finding a “winner,” was found to be within a specific range. For example, Q3=5 means that three times the
| WSA task needed to read n operations (where n sources was >= 100 and < 1000, before finding a “winner.”
| System action: Normal TME 10 OPC processing continues.
| User response: None.
Chapter 8. EQQEnnn Messages
83
EQQE009I Ÿ EQQE012E
| EQQE009I READY QUEUE LAST VALUE
V1
|
NEW READY OPERATIONS
V2
|
NEW STARTED OPERATIONS
V3
|
NEW COMPLETED OPERATIONS
V4
|
SELECT WINNER CALLS
V5
|
ACCESS JS CALLS
V6
|
ACCESS JOBLIB CALLS
V7
|
USER EXIT 001 CALLS
V8
|
USER EXIT 002 CALLS
V9
| Explanation: This message is issued together with message EQQE008I. See the explanation for EQQE008I for
| details about when it is used.
| The meanings of variables V1 through V9 are as follows:
|
|
|
|
|
|
|
|
|
V1
V2
V3
V4
V5
V6
V7
V8
V9
Size of the ready list queue when the message is issued
Number of operations whose status changed to ready (R, *, or A) since the last message
Number of operations whose status changed to started since the last message
Number of operations whose status changed to completed since the last message
Number of times the WSA task was called to select a 'winner' operation since the last message
Number of times the JS VSAM was accessed to read JCL since the last message
Number of times the JOBLIB PDS was accessed to read JCL since the last message
Number of times the User Exit 001 was called since the last message
Number of times the User Exit 002 was called since the last message
| System action: Normal TME 10 OPC processing continues.
| User response: None.
EQQE011E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG NO ACTIVE APPLICATION
DESCRIPTION IN AD DATABASE
Explanation: ETT was triggered by an event but could not add the associated application because there was no
active application description in the AD database.
System action: The associated application was not added by ETT, but ETT processing continues normally.
Problem determination: Check the ETT criteria to make sure that the triggering event identifies an active application
description.
User response: Correct the ETT criteria table or the AD database.
EQQE012E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG UNABLE TO ALLOCATE NECESSARY
STORAGE
Explanation: TME 10 OPC was unable to allocate storage needed to build the tables required when adding an
application (occurrence) to the current plan.
System action: The associated application was not added by ETT, but ETT processing continues normally.
Problem determination: Check the region size allocated to the TME 10 OPC started task.
User response: Contact your system programmer.
System programmer response: Increase the region for the TME 10 OPC started task.
84
TME 10 OPC Messages and Codes
EQQE013E Ÿ EQQE018I
EQQE013E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG ERROR DETECTED BY MODIFY
CURRENT PLAN INTERFACE
Explanation: TME 10 OPC was unable to add the application because the modify current plan interface detected an
error.
System action: The associated application was not added by ETT, but ETT processing continues normally.
Problem determination: Check the TME 10 OPC message log data for EQQMxxx messages (that is, the MCP
messages) preceding this message. These messages give the exact reason why the application could not be added.
User response: Contact your system programmer.
System programmer response: Save the message log dataset containing these error messages, then contact your
IBM representative.
EQQE014E ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG AD DATABASE NOT OPEN
Explanation: ETT was triggered by an event but could not add the associated application since the AD database
was not open.
System action: The associated application was not added by ETT, but ETT processing continues normally.
Problem determination: This is an TME 10 OPC internal error.
System programmer response: Save the message log dataset containing these error messages, then contact your
IBM representative.
EQQE015W ETT CANNOT TRACK JOB JOB EVEN THOUGH APPLICATION APPL HAS BEEN ADDED
Explanation: ETT was unable to track the specified job, even though the specified associated application was
successfully added.
System action: The job that triggered the addition of application APPL is not tracked by TME 10 OPC. ETT
processing continues.
Problem determination: The track keyword of the job tracking option statement has most likely been defined so that
no tracking should occur.
User response: Review the tracking options and correct if in error.
EQQE016I ETT HAS SUCCESSFULLY ADDED ADID FOR TRIGGERING EVENT TRIG
Explanation: ETT has detected a triggering event (TRIG) and has added the associated application (ADID) to the
current plan.
System action: Processing continues.
User response: None.
EQQE017I THE ETT FUNCTION IS ACTIVATED
Explanation: The ETT function has been activated from the dialog or has been started during the controller start up
process because ETT(YES) is specified on the JTOPTS initialization statement.
System action: Processing continues.
User response: None.
EQQE018I THE ETT FUNCTION IS DEACTIVATED
Explanation: The ETT function has been deactivated due to a dialog request or because the Event Manager task
has been requested to terminate.
System action: Processing continues.
User response: None.
Chapter 8. EQQEnnn Messages
85
EQQE019I Ÿ EQQE025I
EQQE019I JOBNAME(JOBNUM) WAS NOT SUBMITTED BY OPC/ESA AND TRACK(OPCASUB) OR
TRACK(JOBOPT) IS ACTIVE, BUT THE JOB WILL BE TRACKED ANYWAY BECAUSE IT BELONGS
TO AN APPLICATION THAT WAS ADDED BY ETT
Explanation: ETT has a job on its list of jobs to be tracked, but the specified job has not been submitted by TME 10
OPC.
System action: TME 10 OPC will track the job because it belongs to an application that was added by ETT.
User response: None.
EQQE021E THE EVENT MANAGER WAS UNABLE TO SET STATUS STATUS FOR JOBNAME(JOBNUM)
Explanation: The Event Manager was unable to change the status of an operation in the current plan.
System action: The status of the current operation remains unchanged. The Event Manager continues normally by
processing the next event.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine which operation is
involved. The most likely cause of this error is an unsuccessful I/O operation against the current plan dataset.
User response: If the current operation can be determined, set the correct status for this operation.
System programmer response: Correct all errors and, if necessary, restart TME 10 OPC.
EQQE022E EVENT MANAGER INITIALIZATION FAILED
Explanation: The Event Manager could not acquire all resources required for normal operation. The most likely
cause of this error is that the subsystem is being stopped but the Normal Mode Manager subtask has not started. It is
also possible that the JCL repository dataset could not be opened.
System action: If this message is issued while the TME 10 OPC subsystem is being stopped, subsystem
termination continues normally. Otherwise, message EQQZ045W is issued.
System programmer response: Review earlier messages in the TME 10 OPC message log to determine the exact
reason for this message.
EQQE023I THE EVENT MANAGER ENDED NORMALLY
Explanation: This message is issued if the TME 10 OPC subsystem is being stopped and Event Manager
initialization has completed successfully. The message is also issued if the Event Manager has been requested to
stop by an operator modify command.
System action: Termination processing continues.
User response: None.
EQQE024E THE EVENT MANAGER TERMINATED BECAUSE OF UNRECOVERABLE ERRORS
Explanation: This message is issued if a serious error that prevents normal operation by the Event Manager has
been encountered after Event Manager initialization has completed.
System action: Message EQQZ045W is issued.
System programmer response: Review earlier messages in the TME 10 OPC message log to determine the exact
reason for this message.
Operator response: If the Event Manager should be activated, issue an operator modify command to start the Event
Manager again.
EQQE025I THE EVENT MANAGER HAS STARTED
Explanation: Event Manager initialization has completed successfully and the Event Manager is about to start
processing.
System action: TME 10 OPC processing continues.
User response: None.
86
TME 10 OPC Messages and Codes
EQQE026I Ÿ EQQE036I
EQQE026I APPLICATION APPL ENDED IN ERROR EC. OPER = OPERNUM, PRTY = PRI, IA = IA
Explanation: This message is issued when an operation on a general type work station has ended in error and the
ALERTS initialization statement specifies TYPE(ERROROPER).
System action: Normal TME 10 OPC processing continues.
User response: Perform error recovery actions for the operation specified.
EQQE027I OPERATION OPERNUM, IN APPLICATION APPL, IA = ARRTIME IS LATE
Explanation: This message is issued when a ready operation on a general type workstation has reached its latest
start time but has not yet started.
System action: Normal TME 10 OPC processing continues.
User response: Investigate what is keeping the operation from starting and take appropriate actions to enable it to
start.
EQQE028I LONG DURATION FOR OPERATION OPERNUM, IN APPLICATION APPL, IA = ARRTIME
Explanation: This message is issued when a started operation on a general type workstation has been active longer
than its estimated duration multiplied by the feedback limit, divided by 100. For example, if the feedback limit is 200
and the estimated duration is ten minutes, then the message will be issued if the operation has been active longer
than twenty minutes.
System action: Normal TME 10 OPC processing continues.
User response: Investigate why the operation has been active so long. If possible, take corrective action to speed
up operation processing.
EQQE029E TRACK (OPCASUB/JOBOPT) IS SPECIFIED, AND AS USER SUBMITTED JOBNAME(JOBNUM)
OUTSIDE OPC/ESA, IT WILL NOT BE TRACKED
Explanation: The job is not one that TME 10 OPC has submitted although it is known to TME 10 OPC as one that
should be tracked. However, because someone submitted the job outside of TME 10 OPC’s control, the job will not
be tracked.
System action: None.
User response: None.
EQQE030I USER USER CAUSED A NEW SPECIAL RESOURCE TO BE DEFINED. NAME OF NEW RESOURCE
IS: RESOURCE
Explanation: The request to create the new resource came from; an SRSTAT command, EQQEVPGM using
SRSTAT as input, the EQQUSINS subroutine, the EQQUSIN subroutine, or from the dataset triggering function.
System action: Processing continues.
User response: None.
EQQE036I JOB JOBNAME(JNUM) ENDED IN ERROR EC. PRTY=PRI, APPL = APPL, WORK STATION = WSID, IA
= IA
Explanation: This message is issued when an operation on a computer or printer workstation has ended in error and
the ALERTS initialization statement specifies TYPE(ERROROPER).
System action: Normal TME 10 OPC processing continues.
User response: Perform error recovery actions for current job.
Chapter 8. EQQEnnn Messages
87
EQQE037I Ÿ EQQE042I
EQQE037I JOB JOBNAME(JNUM), IN APPLICATION APPL, IS LATE, WORK STATION = WSID, IA = ARRTIME
Explanation: This message is issued when a job has reached its latest start time but has not yet started.
System action: Normal TME 10 OPC processing continues.
User response: Investigate what is keeping the job from starting and take appropriate actions to enable it to start.
EQQE038I LONG DURATION FOR JOB JOBNAME(JNUM), IN APPLICATION APPL, WORK STATION = WSID, IA
= ARRTIME
Explanation: This message is issued when a job has been active longer than its estimated duration multiplied by the
feedback limit, divided by 100. For example, if the feedback limit is 200 and the estimated duration is ten minutes,
then the message will be issued if the job has been active longer than twenty minutes. The feedback limit specified
on the JTOPTS initialization statement is used in the calculation.
System action: Normal TME 10 OPC processing continues.
User response: Investigate why the job has been active so long. If possible, take corrective action to speed up the
processing of the job.
EQQE039I LONG TIME ON INPUT QUEUE FOR JOB JOBNAME(JNUM), APPL = APPL, WORK STATION = WSID,
IA = ARRTIME
Explanation: This message is issued when a job has been waiting in a job input queue longer than ten minutes.
The message is only issued when the DURATION keyword is specified in the ALERTS statement.
System action: Normal TME 10 OPC processing continues.
User response: Investigate what is keeping the job from starting and take appropriate actions to enable it to start.
EQQE040W OPC/ESA CANNOT HANDLE JOB JOBNAME(JOBNUM). THE JOB MAY HAVE TO BE CANCELED
Explanation: TME 10 OPC job tracking has encountered an “add job to JES queue” event for a job whose job name
matches job names defined in the current plan. However, none of the operations with this job name has a status that
is consistent with an “add job to JES queue” event. This message indicates that jobs with TME 10 OPC job names
are being submitted by non-TME 10 OPC functions.
System action: TME 10 OPC assumes that the job is not an TME 10 OPC job and will not track the job. If the job
was held by an TME 10 OPC job tracking exit it will be released. Note that since this job is not handled by TME 10
OPC, any dependencies this job may have must be manually implemented.
System programmer response: Determine if TME 10 OPC and non-TME 10 OPC jobs are using the same job
names. Check that all jobs belonging to TME 10 OPC defined applications are defined in the current plan.
EQQE042I JOBNAME(JOBNUM) WAS NOT SUBMITTED BY OPC/ESA BUT WILL BE TRACKED ANYWAY
Explanation: The Event Manager has encountered an event for a job whose job name matches an operation defined
in the current plan. However, TME 10 OPC did not submit this job. This message indicates that jobs with TME 10
OPC job names are being submitted by non-TME 10 OPC functions.
System action: TME 10 OPC accepts current job as an TME 10 OPC job and will continue to track events for this
job.
System programmer response: Determine if TME 10 OPC and non-TME 10 OPC jobs are using the same job
names. If TME 10 OPC and non-TME 10 OPC jobs are using the same job names, take appropriate action to
minimize such name conflicts. Inform TME 10 OPC application owners that rerunning applications or adding
additional work to the job queue should be done using the TME 10 OPC Modify Current Plan dialog.
88
TME 10 OPC Messages and Codes
EQQE043W Ÿ EQQE045E
EQQE043W JOB START OR JOB END EVENT RECEIVED FOR JOBNAME(JOBNUM) IS NOT CONSISTENT WITH
CURRENT OPC/ESA STATUS OF THIS JOB
Explanation: The Event Manager has received an event for a job on an automatically reporting computer workstation
that conflicts with the information already collected for this operation. For example, a job complete event can only
occur for a job that has started to execute.
System action: The status of the operation is not changed. The Event Manager continues normal operation with the
next queued event.
System programmer response: Use console messages in the MVS SYSLOG dataset, or records in an SMF log
dataset to determine what has happened to this job. If possible, try to locate the SYSMSG dataset for this job.
EQQE044W JOBNAME(JOBNUM) MAY HAVE BEEN STARTED OUT-OF-ORDER. IF REQUIRED, SET CORRECT
STATUS MANUALLY
Explanation: The Event Manager has received a job start event for an operation on an automatically reporting
computer workstation. However, this operation has predecessor operations that have not yet been reported complete.
System action: The status of the operation is not changed. The Event Manager continues normal operation with the
next queued event.
System programmer response: Determine if the job was submitted outside of TME 10 OPC or if it was held and
then released manually. Inform all people concerned about the reason for this message and take appropriate action
to make sure that operations are started only after all predecessors are complete.
Operator response: Determine if predecessors to the current operation have completed. If they have, change their
status to complete, and change the status of the current operation to started. If they have not, the current job should
be entered into hold status, and the job should be restarted. After predecessors have completed, the job should be
released from hold.
EQQE045E ERRORS OCCURRED READYING SUCCESSORS TO THE FOLLOWING OPERATION:
APPLICATION = APPL, INPUT ARRIVAL = ARRTIME, OPERATION NUMBER = OPNUM THE FAILURE
REASON WAS REASON. THE PROBLEM SUCCESSOR OPERATION: APPLICATION = SAPPL,
INPUT ARRIVAL = SARRTIME, OPERATION NUMBER = SOPNUM
Explanation: OPC/ESA changed the status of an operation to Complete but encountered errors when attempting to
set the status to Ready for a successor of the complete operation.
System action: The status is not changed for any of the successor operations. Processing continues.
System programmer response: Review earlier messages in the TME 10 OPC message log to determine the exact
reason for this message. Some possible values for reason are:
R
A VSAM I/O error was encountered when reading the successor operation. See the message reporting the I/O
error for more details.
N
The successor operation does not list the predecessor as a dependency.
W
The workstation name for the successor operation is not defined in the current plan.
C
The status of the successor operation is already complete.
M
Setting the status of the successor operation to Ready failed. Check the message log for further messages
describing the error.
All of the reasons above indicate an internal OPC/ESA error. Save a copy of the active current plan, the job-tracking
archive, and the active job-tracking log. Contact your IBM representative.
Operator response: Check each successor operation to see if all its predecessors are complete. If they are
complete, change the status of the operation to ready using the MCP dialog.
Chapter 8. EQQEnnn Messages
89
EQQE046W Ÿ EQQE049W
EQQE046W THE EVENT MANAGER WAS UNABLE TO RELEASE JOBNAME(JOBNUM) FROM HOLD
Explanation: The Event Manager was unable to communicate successfully with JES while trying to release a job
from hold.
System action: The hold status of the current job is not changed. The Event Manager continues normal operation
with the next queued event.
System programmer response: Check that JES is executing normally.
Operator response: Check that the job is still held by JES. If it is, enter an appropriate operator command to
release the job from hold.
EQQE047W JOBNAME(JOBNUM) COULD NOT BE RELEASED FROM HOLD BECAUSE THE SUBMIT/RELEASE
DDNAME DDNAME COULD NOT BE LOCATED
Explanation: A job that was held by an TME 10 OPC job tracking exit could not be released from hold because the
“add job to JES queue” event was read by an event reader where the RELDDNAME keyword on the ERDROPTS
statement defines a ddname that is not defined as a submit/release ddname for any workstation defined in the current
plan.
System action: The hold status of the current job is not changed. The Event Manager continues normal operation
with the next queued event.
System programmer response: Determine if the EWTROPTS statement is in error and should be corrected or if a
new current plan containing an additional workstation must be created.
Operator response: Check that the job is still held by JES on the system where it is executing. If it is, enter an
appropriate operator command to release the job from hold.
EQQE048W JOBNAME(JOBNUM) COULD NOT BE RELEASED FROM HOLD BECAUSE OF ERRORS ON THE
SUBMIT/RELEASE FILE WITH DDNAME DDNAME
Explanation: A job that was held by an TME 10 OPC job tracking exit could not be released from hold because an
error occurred while writing the release command to a submit/release dataset.
System action: The hold status of the current job is not changed. The Event Manager continues normal operation
with the next queued event.
System programmer response: Review earlier messages in the TME 10 OPC message log to determine the exact
reason for this message.
Operator response: Check that the job is still held by JES on the system where it is executing. If it is, enter an
appropriate operator command to release the job from hold.
EQQE049W THE EVENT MANAGER HAS IGNORED THE FOLLOWING USER DEFINED EVENT RECORD
BECAUSE NO MATCHING OPERATION COULD BE FOUND IN CURRENT PLAN: EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager’s work queue. No
operation in the current plan dataset could be found that matches the operation defined by the event record.
System action: The incorrect event record is returned to the Event Manager’s free queue without any further
processing.
System programmer response: Determine if any user program generates events for an undefined application or for
an undefined operation in a known application.
90
TME 10 OPC Messages and Codes
EQQE055W Ÿ EQQE058W
EQQE055W THE EVENT MANAGER HAS IGNORED THE FOLLOWING SUBMIT EVENT RECORD BECAUSE NO
MATCHING OPERATION WAS FOUND IN THE CURRENT PLAN: EXITREC
Explanation: The Event Manager’s work queue contains an incorrect submit event. No operation in the current plan
dataset matches the operation defined by the event record. This submit event record is created for work being
scheduled on one of the systems in this Controller's OPC configuration by another Controller having the same name.
System action: The Event Manager continues normal processing.
Problem determination: Check if the Current Plan has changed significantly since the job defined in the event
record was submitted. Check if the submit event is old, and was sent by an TME 10 OPC subsystem that has been
inactive a long time.
System programmer response: If you cannot determine the reason for this message, contact your IBM
representative.
EQQE056W THE EVENT MANAGER HAS IGNORED THE FOLLOWING INVALID EVENT RECORD: EXITREC
Explanation: An invalid event record has been found on the Event Manager’s work queue. The most likely error is
that the last 4 bytes of the record do not contain the TME 10 OPC character string EQQ3. It is also possible that the
first 3 characters of the job number field do not contain the character string JOB.
System action: The incorrect event record is returned to the Event Manager’s free queue without any further
processing.
TME 10 OPC administrator response: Note the job name and job number in the exit record. If necessary, set the
correct status for this job manually.
System programmer response: Save the TME 10 OPC message log dataset (EQQMLOG) containing this message
and then contact your IBM representative.
EQQE057W AN INVALID EVENT QUEUE ENTRY HAS CAUSED OPC/ESA TO IGNORE THE FOLLOW. EVENT:
EVENT HEADER: EVNTHDR EVENT RECORD: EXITREC
Explanation: An invalid event queue entry has been found on the Event Manager’s work queue. The Event
Manager could not determine the origin of the event. Each event must come from one of sixteen possible event
datasets on each TME 10 OPC node. In the current event queue entry, either the event dataset number or the
TME 10 OPC node number is not valid.
System action: The incorrect event record is returned to the Event Manager’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.
EQQE058W THE EVENT MANAGER HAS IGNORED THE FOLLOWING USER DEFINED EVENT RECORD
BECAUSE THE WORK STATION NAME WSNAME IS NOT RECOGNIZED: EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager’s work queue. The
workstation name in the current event record does not match any workstation definition in the current plan dataset.
System action: The incorrect event record is returned to the Event Manager’s free queue without any further
processing.
System programmer response: Determine if any user program generates events for an undefined workstation or if
a new current plan containing an additional workstation must be created.
Chapter 8. EQQEnnn Messages
91
EQQE059W Ÿ EQQE066E
EQQE059W THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE WORK
STATION WSNAME IS NOT AN AUTOMATICALLY REPORTING WORK STATION: EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager’s work queue.
Workstations referenced by user-defined event records must be automatically reporting workstations. The current
workstation does not have this attribute.
System action: The incorrect event record is returned to the Event Manager’s free queue without any further
processing.
System programmer response: Determine if the user program generating the event should reference some other
workstation or if the attributes of the current workstation should be changed.
EQQE061E THE INPUT DATA SET, DDNAME = SYSIN, COULD NOT BE OPENED
Explanation: The EQQEVPGM program could not open the dataset referenced by the SYSIN DD statement, the
statement was not defined correctly, or no SYSIN DD statement was present.
System action: The EQQEVPGM program ends.
User response: Check that the SYSIN DD statement is present and that it is correctly coded. After making
corrections, resubmit the EQQEVPGM batch job.
EQQE062E EQQEVPGM INITIALIZATION FAILED
Explanation: The EQQEVPGM program found one or more errors during initialization.
System action: The EQQEVPGM program ends.
User response: Review the message log dataset for error messages. Remove the cause of each error and
resubmit the EQQEVPGM batch job.
EQQE063I EQQEVPGM ENDED NORMALLY
Explanation: The EQQEVPGM program has finished processing. No errors were found during execution.
System action: The EQQEVPGM program ends.
User response: None.
EQQE064E EQQEVPGM TERMINATED BECAUSE OF UNRECOVERABLE ERRORS
Explanation: A severe error occurred during execution of the EQQEVPGM program.
System action: The EQQEVPGM program ends.
User response: Review the message log dataset and the SYSUDUMP dataset to determine the cause of the error.
After making corrections, resubmit the EQQEVPGM batch job. If you cannot determine the cause of the error and if
the error persists, contact your IBM representative.
EQQE065I THE EQQEVPGM PROGRAM HAS STARTED
Explanation: The EQQEVPGM program has been correctly initialized and is about to start generating events.
System action: EQQEVPGM processing continues normally.
User response: None.
EQQE066E SUBSYS IS NOT A VALID SUBSYSTEM NAME. NO EVENT IS CREATED
Explanation: The SUBSYS keyword contains an invalid subsystem name.
System action: The event will not be created. The EQQEVPGM program continues processing the next event
creation statement.
User response: If the event should be created, make the necessary corrections and resubmit the EQQEVPGM
batch job.
92
TME 10 OPC Messages and Codes
EQQE067E Ÿ EQQE071E
EQQE067E A SUBSYSTEM REQUEST ERROR (R15 = R15) OCCURRED. NO EVENT IS CREATED
Explanation: An error occurred when attempting to send an event to an TME 10 OPC subsystem.
System action: The event will not be created. The EQQEVPGM program continues processing the next event
creation statement.
User response: If R15 is 4 then the SUBSYS keyword does not define an TME 10 OPC system. If R15 is 8 then
the SUBSYS keyword either does not define an TME 10 OPC system or it defines an TME 10 OPC system that has
not been properly installed. Make the necessary corrections and resubmit the EQQEVPGM batch job. If R15 is 12,
16 or 20 contact your IBM representative.
EQQE068E A SUBSYSTEM ERROR (SSOBRETN = RETN) OCCURRED. NO EVENT IS CREATED
Explanation: An error occurred when attempting to send an event to an TME 10 OPC subsystem.
System action: The event will not be created. The EQQEVPGM program continues processing the next event
creation statement.
User response: Contact your IBM representative.
EQQE069E ERRORS ENCOUNTERED IN EVENT DEFINITION STATEMENTS. ONE OR MORE EVENTS HAVE
NOT BEEN CREATED
Explanation: The EQQEVPGM program found one or more incorrectly coded event definition statements.
System action: The EQQEVPGM program ends.
User response: If the events should be created, make the necessary corrections and resubmit the EQQEVPGM
batch job.
EQQE070E THE SPECIAL RESOURCE NAME GIVEN IS TOO LONG. MAXIMUM SIZE IS 44 CHARACTERS
Explanation: The special resource name defined by the SRSTAT event definition statement is too long.
System action: The event will not be created. The EQQEVPGM program continues processing the next event
creation statement.
User response: If the event should be created, make the necessary corrections and resubmit the EQQEVPGM
batch job.
EQQE071E A SPECIAL RESOURCE NAME IS REQUIRED ON THE SRSTAT STATEMENT
Explanation: The current SRSTAT event definition statement does not define any special resource name. This
name is required.
System action: The event will not be created. The EQQEVPGM program continues processing the next event
creation statement.
User response: If the event should be created, make the necessary corrections and resubmit the EQQEVPGM
batch job.
Chapter 8. EQQEnnn Messages
93
EQQE072E Ÿ EQQE075E
EQQE072E YOU ARE NOT AUTHORIZED TO UPDATE SPECIAL RESOURCES FOR SUBSYSTEM SUBSYS
Explanation: In order to change a special resource for an TME 10 OPC subsystem, update authority to the SR
resource is necessary. You do not have this authority.
System action: If you specified SUBSYSTEM(MSTR) in the command, no event is created for this subsystem.
However, EQQEVPGM tries to create an event for the next active TME 10 OPC subsystem in this MVS system. If
you are authorized to update one or more of the TME 10 OPC subsystems, the statement return code is set to 4.
Otherwise, it is set to 8. After scanning all active TME 10 OPC systems, EQQEVPGM continues processing the next
event creation statement.
If you specified a unique TME 10 OPC subsystem name instead of MSTR, no event is created for the subsystem
specified. The statement return code is set to 8. The EQQEVPGM program continues processing the next event
creation statement.
User response: Contact your security administrator.
EQQE073E YOU ARE NOT AUTHORIZED TO UPDATE THE CURRENT PLAN FOR SUBSYSTEM SUBSYS
Explanation: In order to create an operation or workstation event for an TME 10 OPC subsystem, update authority
to the RL resource is necessary. You do not have this authority.
System action: If you specified SUBSYSTEM(MSTR) in the command, no event is created for this subsystem.
However, EQQEVPGM tries to create an event for the next active TME 10 OPC subsystem in this MVS system. If
you are authorized to update one or more of the TME 10 OPC subsystems, the statement return code is set to 4.
Otherwise, it is set to 8. After scanning all active TME 10 OPC systems, EQQEVPGM continues processing the next
event creation statement.
If you specified a unique TME 10 OPC subsystem name instead of MSTR, no event is created for the subsystem
specified. The statement return code is set to 8. The EQQEVPGM program continues processing the next event
creation statement.
User response: Contact your security administrator.
EQQE074E THE EVENT CREATION DATE SPECIFIED BY THE EVDATE KEYWORD IS NOT VALID
Explanation: The EVDATE keyword contains an invalid date. The date must be specified in the format YYMMDD
where:
YY
MM
DD
Is year and must specified as 72 to 99 for years 1972 to 1999 or 00 to 71 for years 2000 to 2071.
Is the month number and must be in the range 01 to 12.
Is the day number and must be in the range 01 to 31.
System action: The event will not be created. The EQQEVPGM program continues processing the next statement.
User response: If the event should be created, correct the EVDATE keyword and resubmit the EQQEVPGM batch
job.
EQQE075E THE EVENT CREATION TIME SPECIFIED BY THE EVTIME KEYWORD IS NOT VALID
Explanation: The EVTIME keyword contains an invalid time-of-day value. The time must be specified in the format
HHMMSS, where:
HH
MM
SS
Is a two-digit hour number. It must be in the range 00–23.
Is a two-digit minute number. It must be in the range 00–59.
Is a two-digit second number. It must be in the range 00–59.
System action: The event will not be created. The EQQEVPGM program continues processing the next statement.
User response: If the event should be created, make the necessary corrections and resubmit the EQQEVPGM
batch job.
94
TME 10 OPC Messages and Codes
EQQE076E Ÿ EQQE080E
EQQE076E THE INPUT ARRIVAL TIME SPECIFIED BY THE IA KEYWORD IS NOT VALID
Explanation: The IA keyword contains an invalid input arrival value. The value must be specified in the format
YYMMDDHHMM where:
YYMMDD
HHMM
Is the input arrival date:
YY
Is year and must specified as 72 to 99 for years 1972 to 1999 or 00 to 71 for years 2000 to
2071.
MM
Is the month number and must be in the range 01 to 12.
DD
Is the day number and must be in the range 01 to 31.
Is the input arrival time:
HH
Is the hour number and must be in the range 00 to 23.
MM
Is the minute number and must be in the range 00 to 59.
System action: The event will not be created. The EQQEVPGM program continues processing the next statement.
User response: If the event should be created, correct the IA keyword and resubmit the EQQEVPGM batch job.
EQQE077E WORK STATION NAME (WSNAME KEYWORD) MUST BE SPECIFIED
Explanation: The current OPSTAT or WSSTAT event definition statement does not define any workstation name.
This name is required.
System action: The event will not be created. Processing ends if it was invoked by a current TSO command. If the
command was invoked by the EQQEVPGM program, processing continues with the next statement.
User response: If the event should be created, make the necessary corrections and reissue the command.
EQQE078E THE EVENT DURATION TIME SPECIFIED BY THE DURATION KEYWORD IS NOT VALID
Explanation: The DURATION keyword contains an invalid duration value. Event duration must be specified in the
format HHMM, where:
HH
MM
Is a two-digit hour number. It must be in the range 00–99.
Is a two-digit minute number. It must be in the range 00–59.
System action: The event will not be created. The EQQEVPGM program continues processing the next statement.
User response: If the event should be created, make the necessary corrections and resubmit the EQQEVPGM
batch job.
EQQE079E KEYWORD KEY HAS AN INVALID VALUE
Explanation: The only valid values for the CREATE and AVAIL keywords are YES, NO, or RESET or abbreviations
of YES, NO, or RESET.
System action: The event will not be created. Processing ends for current SRSTAT command. If SRSTAT is
invoked by the EQQEVPGM program then processing continues with the next statement.
User response: If the event should be created, make the necessary corrections and reissue the SRSTAT command.
EQQE080E THE EQQMINOR PROGRAM ABENDED WITH ABEND CODE ABEND
Explanation: This message is issued when an TME 10 OPC TSO command has failed due to an error when
communicating with the TME 10 OPC subsystem.
Problem determination: If necessary, generate a dump by allocating a SYSxDUMP dataset to the TSO user's
address space, or by defining a slip trap, and reissue the failing command.
User response: Contact your systems programmer.
System programmer response: If the failing command contains an error, correct it and retry. If the error cannot be
corrected, contact your IBM representative for assistance.
Chapter 8. EQQEnnn Messages
95
EQQE081E Ÿ EQQE086E
EQQE081E R15 RETURN CODE R15 WAS RETURNED BY THE TSO SERVICE FACILITY. RETURN CODE RC,
REASON CODE RSN WERE ALSO RETURNED
Explanation: This message is issued when an TME 10 OPC TSO command has failed due to an error when
communicating with the TME 10 OPC subsystem.
System action: The TME 10 OPC service requested has not been executed.
User response: Contact your systems programmer.
System programmer response: If the failing command contains an error, correct it and retry. If the error cannot be
corrected, contact your IBM representative for assistance.
EQQE082E THE OPC/ESA SUBSYSTEM SUBSYS IS NOT INITIALIZED. NO EVENT IS CREATED
Explanation: An TME 10 OPC TSO command or EQQEVPGM has failed because the TME 10 OPC subsystem
SUBSYS has not been initialized. TME 10 OPC subsystems are initialized during an MVS IPL.
System action: No event is created.
Problem determination: Check the system log for error messages issued during IPL that identify why the TME 10
OPC subsystem was not initialized.
User response: If the command referred to the wrong subsystem correct the input, and retry the command.
System programmer response: If the TME 10 OPC subsystem should be initialized the EQQINITC program must
be executed successfully. Ensure EQQINITC is located in a library in the LNKLSTnn concatenation and IPL the MVS
system.
EQQE083E SUBSYSTEM SUBSYS IS NOT AN OPC/ESA SYSTEM. NO EVENT IS CREATED
Explanation: This message is issued when an TME 10 OPC TSO command has failed because the subsystem that
was referenced is not an TME 10 OPC subsystem.
System action: None.
User response: Correct the command and retry.
EQQE084E YOU ARE NOT AUTHORIZED TO UPDATE THE SPECIAL RESOURCE SPECIFIED FOR SUBSYSTEM
SUBSYS
Explanation: An SRSTAT request to update a special resource specified for subsystem SUBSYS failed because the
user making the request was not authorized to update the resource.
System action: The request is rejected.
User response: Contact your security administrator if access is required.
EQQE085E RESDS IS NOT A VALID RESOURCE DATASET NAME, NO EVENT IS CREATED
Explanation: The value specified for the resource dataset keyword—RESDS was not valid. The keyword value must
be specified as CP or JS.
System action: The request is ignored.
User response: Correct the input and resubmit the request.
EQQE086E THE RESDS KEYWORD MUST BE SPECIFIED
Explanation: The resource dataset keyword—RESDS was not specified.
System action: The request is ignored.
User response: Supply the RESDS keyword and a valid value and resubmit the request.
96
TME 10 OPC Messages and Codes
EQQE087E Ÿ EQQE091E
EQQE087E YOU ARE NOT AUTHORIZED TO REQUEST A BACKUP OF THE RESDS RESOURCE DATASET
SPECIFIED FOR SUBSYSTEM SUBSYS
Explanation: In order to request a backup of an TME 10 OPC resource dataset, update authority to the BKP fixed
resource is required. You do not have this authority.
System action: The request is ignored.
User response: If authority is required contact your security administrator.
EQQE088E YOU ARE NOT AUTHORIZED TO UPDATE THE OPERATION, SUBRES CHECK FAILED AT
SUBSYSTEM SUBSYS
Explanation: An OPSTAT requests to update an operation in subsystem SUBSYS failed because the user making
the request was not authorized to update the SUBRES subresource.
System action: The request is rejected.
User response: If authority is required contact your security administrator.
EQQE089E YOU ARE NOT AUTHORIZED TO UPDATE STATUS OF WORKSTATION WSNAME FOR
SUBSYSTEM SUBSYS
Explanation: A WSSTAT request to update the status of workstation WSNAME in subsystem SUBSYS failed
because the user making the request was not authorized to update the RL.WSSTAT subresource.
System action: The request is rejected.
User response: If authority is required contact your security administrator.
EQQE090E EITHER WORKSTATION NAME OR DESTINATION MUST BE SPECIFIED
Explanation: The current WSSTAT statement does not define a workstation name (WSNAME) or a destination ID
(DESTINATION). At lease one of WSNAME or DESTINATION must be specified. Both can be specified.
System action: The event will not be created. The EQQEVPGM program continues processing any further event
creation statements.
User response: If the event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
EQQE091E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE OPCTOKEN
VALUE IS NOT CONSISTENT WITH THE VALUE(S) SPECIFIED IN THE ADID, IA, JOBNAME AND/OR
OPNUM KEYWORDS:
EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An
OPSTAT event definition statement defined an OPCTOKEN value that is not consistent with some or all of the values
specified in the ADID, IA, JOBNAME, AND OPNUM keywords. The operation cannot be identified by OPC/ESA.
System action: The incorrect event record is returned to the Event Manager's free queue without any further
processing.
User response: If a new event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
Chapter 8. EQQEnnn Messages
97
EQQE092E Ÿ EQQE096E
EQQE092E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE CURRENT
OPERATION STATUS IS NOT STARTED:
EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An
OPSTAT event definition statement specified a new status of SQ or SS, but the current operation status is not started
(S).
System action: The incorrect event record is returned to the Event Manager's free queue without any further
processing. The operation status is not changed.
User response: If a new event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
EQQE093E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE
WORKSTATION WSNAME IS NOT A COMPUTER OR WTO WORKSTATION:
EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An event
generated by WSSTAT or EQQUSINW specified a workstation that is not a computer, or WTO workstation.
System action: The incorrect event record is returned to the Event Manager's free queue without any further
processing. The workstation status is not changed.
User response: If a new event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
EQQE094E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE
WORKSTATION WSNAME DOES NOT MATCH THE DESTINATION DEST: EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An
WSSTAT event definition statement specified a workstation that did not match the destination specified in the event.
System action: The incorrect event record is returned to the Event Manager's free queue without any further
processing. The workstation status is not changed.
User response: If a new event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
EQQE095E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE
DESTINATION DEST IS NOT SPECIFIED IN THE ROUTOPTS INITIALIZATION STATEMENT:
EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An
WSSTAT event definition statement specified a destination which was not specified in the ROUTOPTS initialization
statement.
System action: The incorrect event record is returned to the Event Manager's free queue without any further
processing. The workstation status is not changed.
User response: If a new event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
EQQE096E THE STATUS KEYWORD MUST BE SPECIFIED
Explanation: The current WSSTAT event definition statement does not define any status. This keyword is required.
System action: The event will not be created. The EQQEVPGM program continues processing the next event
creation statement.
User response: If the event should be created, make the necessary corrections and resubmit the EQQEVPGM
batch job.
98
TME 10 OPC Messages and Codes
EQQE097E Ÿ EQQE101E
EQQE097E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE SPECIFIED
TOKEN VALUE DOES NOT MATCH ANY OPERATION IN THE CURRENT PLAN:
EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An
OPSTAT event definition statement defined a TOKEN value that does not match any operation in the current plan.
The operation cannot be identified by OPC/ESA.
System action: The incorrect event record is returned to the Event Manager's free queue without any further
processing.
User response: If a new event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
EQQE098E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE CURRENT
OPERATION STATUS IS SS: EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. An
OPSTAT event definition statement specifies a new status Q for an operation which has a current status SS. This is
not allowed
System action: The incorrect event record is returned to the Event Manager's free queue without any further
processing. The workstation status is not changed.
User response: If a new event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
EQQE099E THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE
ALTERNATE WORKSTATION WSNAME DOES NOT EXIST: EXITREC
Explanation: An invalid user-defined event record has been found on the Event Manager's work queue. A WSSTAT
event definition statement specified an alternate workstation that did not exist.
System action: The incorrect event record is returned to the Event Manager's free queue without any further
processing. The workstation status is not changed.
User response: If a new event should be created, make the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
EQQE100E THE CURRENT WORKSTATION WSNAME CANNOT BE USED AS ALTERNATE TO ITSELF.
REROUTE IS NOT IN EFFECT FOR THE WORKSTATION
Explanation: A WSSTAT event definition statement specified an alternate workstation which was the same as the
current workstation.
System action: Reroute will not be in effect for the actual workstation. The workstation status is changed.
User response: None.
EQQE101E KEYWORD KEY HAS AN INVALID VALUE
Explanation: The only valid values for the QUANTITY and DEVIATION keywords are KEEP, RESET or a numeric
value.
System action: The event will not be created. Processing ends for current SRSTAT command. If SRSTAT is
invoked by the EQQEVPGM program then processing continues with the next event creation statement.
User response: If the event should be created, make the necessary corrections and reissue the SRSTAT command.
Chapter 8. EQQEnnn Messages
99
EQQE102W Ÿ EQQE104E
EQQE102W PULSE LOST FROM TRACKER SUBS AT DESTINATION DEST
Explanation: This message indicates that handshake processing, the frequency for which is determined by the
PULSE keyword of the ROUTOPTS statement, has terminated for the indicated Tracker system. When handshake
processing is in use, each connected Tracker system sends an identification (ID) event to the controller at the
specified interval. If the controller detects that a Tracker system has missed two consecutive PULSE intervals, this
message is issued. SUBS is the name of the Tracker (the subsystem name for MVS/ESA trackers). DEST is the
destination for this system, as defined in the ROUTOPTS statement.
System action: If the destination DEST is defined using shared DASD (submit/release) dataset communication, this
destination is forced Offline by the TME 10 OPC controller. For other communication methods, no action is taken.
System programmer response: Check that the destination is active. If it is, check that the event writer at the
destination is active.
EQQE103W TRACKER SUBS AT DESTINATION DEST LOST THE FUNC
Explanation: This message is issued for reporting purposes on the controller message log, EQQMLOG, when the
ROUTOPTS PULSE processing is active for Tracker systems on TME 10 OPC release 3 level or higher. The
message indicates that the FUNC subtask in the SUBS subsystem on the MVS/ESA system represented in TME 10
OPC by the DEST destination has abnormally terminated.
System action: No action is taken by the controller.
System programmer response: Check the message log for the indicated Tracker address space and take
appropriate actions to restart the failed subtask.
EQQE104E KEYWORD KEYW MISSING. IT IS REQUIRED FOR SUBRESOURCE SUBRES CHECKING AT
SUBSYSTEM SUBSYS
Explanation: Authority checking for subresource SUBRES is specified in the AUTHDEF statement for subsystem
SUBSYS. A valid subresource name cannot be built for protection of the operation when keyword KEYW is omitted.
System action: No event is created for the subsystem identified in the message text. The request is directed to the
next OPC subsystem if SUBSYSTEM(MSTR) was specified in the input. Return code 4 is set if event creation failed
for one or more subsystems. If it failed for all subsystems, or for a subsystem specifically identified in the input, return
code 8 is set.
System programmer response: Add the keyword and resubmit the EQQEVPGM job for the failing subsystem.
100
TME 10 OPC Messages and Codes
EQQF000E Ÿ EQQF004E
Chapter 9. EQQFnnn Messages
EQQF000E DATA ROUTER TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE
Explanation: A queue element did not contain the correct eye catcher or version number.
System action: The data router task does not process the invalid element, but continues normal processing.
User response: Contact your system programmer.
System programmer response: Save the TME 10 OPC message log and contact your IBM representative.
EQQF001I DATA ROUTER TASK INITIALIZATION IS COMPLETE
Explanation: The data router task has successfully completed initialization.
System action: Data router task processing starts.
User response: None.
EQQF002E DATA ROUTER TASK INITIALIZATION FAILED
Explanation: The data router task could not acquire the resources required for normal operation.
System action: Data router processing is terminated.
Problem determination: Review previous messages in the TME 10 OPC message log.
User response: Contact your system programmer.
System programmer response: Correct all errors and restart the data router task.
EQQF003E MEMBER MEMBER IS DEFINED AS A DESTINATION IN ROUTOPTS BUT IS STARTED AS A
STANDBY SYSTEM
Explanation: An XCF member has joined the same XCF group as the controller. This member was defined as a
tracker in the ROUTOPTS but has been started as an TME 10 OPC standby system.
System action: TME 10 OPC will not recognize the joined standby member as a destination. No communication
will take place between the controller and the standby member.
Problem determination: Check the ROUTOPTS initialization statement and the initialization statement defined for
the member.
User response: Contact your system programmer.
System programmer response: Restart the standby system as a tracker or update the controller ROUTOPTS
statement.
EQQF004E DATA ROUTER TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT DQE
Explanation: An abend prevented the data router task from processing a queue element.
System action: MVS recovery/termination is requested to generate a dump. The data router task attempts to
continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP dataset, and the
SYSMDUMP dataset to determine the cause of the problem.
User response: Contact your system programmer.
System programmer response: Save the message log and dump datasets and contact your IBM representative.
 Copyright IBM Corp. 1991, 1998
101
EQQF005E Ÿ EQQF008I
EQQF005E DATA ROUTER TASK QUEUE POINTERS ARE DESTROYED, RTRQ IS LOST
Explanation: The data router task abended while processing elements on RTRQ because the queue chaining is
invalid.
System action: MVS recovery/termination is requested to generate a dump. All elements on RTRQ are skipped, but
the data router task attempts to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP dataset, and the
SYSMDUMP dataset to determine the cause of the problem.
TME 10 OPC administrator response: Save the message log and dump datasets and contact your IBM
representative.
EQQF006I UNKNOWN XCF MEMBER MEMBER HAS JOINED THE GROUP. IT IS IGNORED
Explanation: A member that is not defined in ROUTOPTS has joined the XCF group.
System action: The controller ignores the joined member. No workload or event communication between the
controller and the tracker will take place.
Problem determination: Check the XCFOPTS initialization statement of the TME 10 OPC tracker system and check
the ROUTOPTS initialization statement of the controller.
TME 10 OPC administrator response: Verify that the tracker system has been defined with an XCF member name
that corresponds to the definition in ROUTOPTS. Add the member name to ROUTOPTS and restart the controller.
EQQF007I XCF MEMBER MEMBER HAS JOINED THE GROUP. THE DESTINATION WILL BE REPORTED
ACTIVE
Explanation: An TME 10 OPC tracker system has joined the same XCF group as the controller. The member is
defined as an XCF destination in the ROUTOPTS initialization statement.
System action: The controller will report the destination as active. Work can be scheduled at workstations defining
this destination.
User response: None
EQQF008I XCF MEMBER MEMBER HAS JOINED THE GROUP AS STANDBY FOR THE OPC/ESA CONTROLLER
Explanation: An TME 10 OPC standby system has joined the same group as the controller.
System action: Controller processing continues as normal.
User response: None
102
TME 10 OPC Messages and Codes
EQQF009I Ÿ EQQF012I
EQQF009I ADAPTIVE PACING ON EVENT INFLOW MODE
Explanation:
The MODE can be ACTIVATED or DEACTIVATED.
ACTIVATED
The data router has detected that the maximum number of queue elements on the event manager
queue (MGRQ) were already in use when the data router task attempted to add incoming events to
the MGRQ. The data router task has posted each locally attached event reader task and event
writer task (when EWSEQNO(n)), to stop reading from the event datasets or adding to the DRTQ.
The data router task has also built and sent a DQE request (type RTQ) to each remote (NCF or
XCF) linked tracker, where the remote data router task will post each attached event reader task and
event writer task (when EWSEQNO(n)), to stop reading from the event datasets or adding to the
DRTQ.
DEACTIVATED The data router task has detected that the event manager has processed all events on the event
manager queue (MGRQ), so the data router task has posted each locally attached event reader task
and event writer task (when EWSEQNO(n)), to start reading from the event datasets or dding to the
DRTQ. The data router task has also built and sent a DQE request (type RTQ) to each remote
(NCF and/or XCF) linked tracker, where the remote data router task will post each attached event
reader task and event writer task (when EWSEQNO(n)), to start reading from the event datasets or
adding to the DRTQ.
System action:
TME 10 OPC processing continues.
User response: None, this message is for information only.
EQQF010I INVALID RETURN CODE RETC FROM EQQUX009 IS IGNORED
Explanation: User exit EQQUX009 passed an invalid return code back to the Data Router task. The return code is
ignored.
System action: Normal processing will continue. The return code is treated as return code 0.
User response: Inform your systems programmer.
System programmer response: Investigate why EQQUX009 returned an invalid return code.
EQQF011E THE OPERATION INITIALIZATION EXIT USRX HAS ABENDED WHILE PROCESSING OPERATION
OPN IN APPLICATION APPL WITH IA IA SCHEDULED ON WORKSTATION WSNAME. THE EXIT IS
MARKED AS NOT USABLE.
Explanation: The exit abended while processing. TME 10 OPC will not try to call it again unless the Data Router
task is restarted. The exit will be flagged as not executable.
System action: The current operation status is set according to what is specified in the SUBFAILACTION JTOPTS
parameter.
System programmer response: Correct all errors in the exit and restart the Data Router task.
EQQF012I PROCESSING RETURN CODE RETC FROM EQQUX009
Explanation: User exit EQQUX009 passed a return code, RETC, that is not 0. The Data Router task processes the
return codes and continues normal processing.
System action: The return code is processed as follows:
4
8
The current operation status will be set according to the specification in the SUBFAILACTION keyword in the
JTOPTS initialization statement.
The operation status will be set according to the specification in the SUBFAILACTION keyword in the JTOPTS
initialization statement. All workstations specifying the destination will be set to offline status.
User response: Inform your systems programmer.
System programmer response: Investigate why EQQUX009 returned the return code.
Chapter 9. EQQFnnn Messages
103
EQQF013I Ÿ EQQF015I
EQQF013I EXIT EQQUX009 IS NOT LOADED OR HAS BEEN DISABLED
Explanation: User exit EQQUX009 has not been loaded, or has abended previously. The operations scheduled to
run on a workstation which specifies a user-defined destination will not be routed.
System action: The operation status is set according to what is specified in the SUBFAILACTION keyword on the
JTOPTS initialization parameter.
User response: Issue a WSSTAT command, or use the workstation dialog, to vary the destination workstations
offline.
System programmer response: Investigate why EQQUX009 is not loaded. If a previous abend caused the exit to
be disabled, correct the error and stop/start the TME 10 OPC subsystem to get the exit reloaded.
EQQF014E THE EXTERNAL ROUTER QUEUE IS FULL. USER DESTINATION WILL BE SET TO OFFLINE
STATUS
Explanation: The external router queue is full. TME 10 OPC will set the destination to offline status and set the
corresponding operation to the status specified in the SUBFAILACTION keyword value in the JTOPTS initialization
statement.
System action: The current operation status is set according to what is specified in the SUBFAILACTION JTOPTS
parameter.
System programmer response: Investigate why the EQQUX009 exit is not processing.
EQQF015I XCF TYPE MEMBER MEMBER HAS LEFT THE GROUP.
REASON: REASON
Explanation: The XCF link to TYPE with member name MEMBER has been disconnected. The REASON is either
that the linked TME 10 OPC address space terminated or the entire MVS/ESA system terminated.
System action: The transmission of data (such as event records) through the XCF link is postponed. The
transmission of data will resume when the XCF member rejoins the group.
Problem determination: If this message is not expected, review the message log (EQQMLOG) and the SYSLOG of
the linked TME 10 OPC MEMBER to determine the cause of the outage.
User response: Contact your system programmer.
System programmer response: This is an TME 10 OPC informational message.
If this message was expected and:
Ÿ The TYPE indicated CONTROLLER and message EQQW070I was also issued when the controller was restarted,
you should consider increasing the size of the tracker's event data set.
Ÿ The TYPE indicated TRACKER and message EQQZ035I was also issued when the tracker was restarted, you
should consider increasing the size of the ECSA buffer (SYS1.PARMLIB(IEFSSNxx)).
104
TME 10 OPC Messages and Codes
EQQG001I Ÿ EQQG004E
Chapter 10. EQQGnnn Messages
EQQG001I SUBTASK SUBTASK HAS STARTED
Explanation: The subtask SUBTASK has been successfully initialized.
System action: Processing for the subtask indicated is started.
User response: None.
EQQG002E INITIALIZATION OF SUBTASK SUBTASK FAILED. REASON CODE: RS
Explanation: The subtask indicated could not acquire all the resources needed for normal operation.
System action: Processing continues but no requests from the dialog or the program interface for TME 10 OPC can
be served.
Problem determination: The message variable RS can have the following values:
|
|
|
02
11
12
13
14
15
16
17
18
19
The
The
The
The
The
The
The
The
The
The
main task, the normal mode manager, is unavailable.
application description file is unavailable.
workstation description file is unavailable.
calendar file is unavailable.
period file is unavailable.
all workstations closed record is unavailable.
operator instruction file is unavailable.
JCL variables file is unavailable.
resource description file is unavailable.
ETT criteria file is unavailable.
User response: Review earlier messages in the TME 10 OPC message log to determine the cause of the error.
System programmer response: Correct errors shown by the earlier messages and restart the subtask indicated.
EQQG003I SUBTASK SUBTASK HAS ENDED
Explanation: This message is issued when the TME 10 OPC subsystem is being stopped by an operator command.
System action: TME 10 OPC termination processing continues.
User response: None.
EQQG004E SUBTASK SUBTASK ABENDED, IT IS RESTARTED AT RETRYAT
Explanation: A serious error caused the SUBTASK subtask to end abnormally. SUBTASK has been able to restart,
at RETRYAT.
System action: SUBTASK resumes normal processing, but one or more requests for service may have been
rejected. The dialog user requesting service may or may not be informed about the completion or termination of the
requests. A dump is created. Message EQQX271E, when issued, informs the dialog user that the request has failed
due to a serious error in SUBTASK. If the subtask is GENERAL SERVICE, the dialog user must press “attention” to
break the request.
Problem determination: Review the dump dataset to determine what caused the problem.
User response: Inform the system programmer about the error and, (if the error can be reproduced), of the
sequence of dialog requests leading to the error.
System programmer response: Collect relevant information about the sequence of events leading to this error,
make the dump dataset and the message log available for inspection, and contact your IBM representative.
 Copyright IBM Corp. 1991, 1998
105
EQQG005E Ÿ EQQG010I
EQQG005E VALIDATION FAILED FOR FILE: FILE, REASON: REASON, OFFSET: POS
Explanation: The record that was to be written to the TME 10 OPC database was rejected because it was incorrect.
System action: No update to the database is made.
Problem determination: FILE gives the database on which the update was attempted; REASON indicates the
reason for the failure; and POS indicates the failing position in hexadecimal form within the record.
See Chapter 36, “Reason Codes” on page 481 for a list of the reason codes and their meanings.
User response: Look in the dump dataset (with ddname EQQDUMP) for further information about the error. This
dataset contains the record and the position of the error. If you cannot find a valid reason for the error, contact your
system programmer.
System programmer response: If you cannot find a valid reason for the error, make the dump dataset (with
ddname EQQDUMP) and the message log available for inspection. Contact your IBM representative.
EQQG006I THE FUNC FUNCTION IS ACTION by USER
Explanation: This message confirms and logs some action taken to an TME 10 OPC function. FUNC is either
AUTOMATIC JOB RECOVERY or JOB SUBMISSION. ACTION is either ACTIVATED or DEACTIVATED. USER is
the userid of the user who requested the function. The message confirms that the dialog request has been
successfully accomplished.
System action: Processing continues.
User response: None.
EQQG008W THE REQUEST FAILED, GENERAL SERVICE QUEUING PROBLEM, REASON: XSSRS
Explanation: The request was rejected because of an interface problem in the General Service function.
System action: The system waits for you to respond.
Problem determination: Review the TME 10 OPC message log for errors related to General Service to determine
the cause of the error.
User response: Try again. If the error persists, contact your system programmer.
System programmer response: Correct the General Service error given in the TME 10 OPC message log.
EQQG009W INSUFFICIENT VIRTUAL STORAGE FOR THE COMPLETE LIST, REASON: XSSRS
Explanation: The requested list could not be displayed because the amount of virtual storage in the dialog address
space was not sufficient.
System action: A partial list is displayed, or no list at all.
User response: If this is a request from a dialog function in which a selection criterion can be specified, change the
selection criterion to select fewer items. Increase the region size at TSO logon.
EQQG010I GENERAL SERVICE REQUEST STATISTICS FOLLOW:
TYPE
TOTAL NEWRQS TOTTIME NEWTIME TOTAVG
NEWAVG
| Explanation: This message is issued if the GENERAL SERVICE task statistics are active. This can be done either
| by specifying the STATMSG(GENSERV) keyword in the JTOPTS initialization statement, or with the modify command,
| /F subsys,GENSTA=ON.
| This message is issued every n minutes if any requests have been processed, where n is the value specified in the
| JTOPTS keyword STATIM if it has a nonzero value, or the default of 30.
| It consists of column headers defining the values of the EQQG011I message following.
The following column headers are defined:
TYPE
TOTAL
NEWRQS
106
The request for which data was gathered.
The total number of requests of this type.
The number of requests of this type since the last message.
TME 10 OPC Messages and Codes
EQQG010I Ÿ EQQG010I
TOTTIME
NEWTIME
TOTAVG
NEWAVG
The
The
The
The
total time, in seconds, used to process this request.
total time, in seconds, used to process this request since the last message.
average time, in seconds, used to process a request of this type.
average time, in seconds, used to process a request of this type since the last message.
The values in the TYPE column will be one of the following resources:
ALL
AD
AR
PERI
CALE
WSCL
WSD
LTPS
PLAN
WS
WSRL
RL
OPER
OPRL
PREP
DEPC
R3P
C3C
C3CR
CP_G
JCL
JSUB
JCLA
JCLP
JCLT
JVAR
JV
RACF
SRES
ETT
OI
STAT
MCP
DEP
CATM
OTHR
Total line for all resources
Application description
Automatic recovery
Calendar periods
Calendar
All workstations closed
Workstation description
Long-term plan
Long-term plan status
Current plan workstation status
Current plan workstation status requested from the ready list
Current plan ready list
Current plan operation
Current plan operation requested from the ready list
Preparation CPU operations
Dependency operation
Current plan operation record
Current plan occurrences
Current plan occurrences requested from the ready list
Current plan general
JCL Repository record
Job submission
Automatic JCL preparation
Promptable JCL variables
JCL tailoring
Tailoring session
JCL variable table
Refresh RACF resources
Special resources
Event-triggered tracking
Operator instruction
TME 10 OPC status record
Modify current plan
Successor candidates
Catalog management
All other resources
System action: Normal TME 10 OPC processing continues.
User response: None.
Chapter 10. EQQGnnn Messages
107
EQQG011I Ÿ EQQG013I
EQQG011I TYPE
NUMRQ NEWRQ
TTOT
TNEW
TAVG NAVG
| Explanation: This message is issued if the GENERAL SERVICE task statistics are active. This can be done either
| by specifying the STATMSG(GENSERV) keyword in the JTOPTS initialization statement, or with the modify command,
| /F subsys,GENSTA=ON.
| This message is issued every n minutes if any requests have been processed, where n is the value specified in the
| JTOPTS keyword STATIM if it has a nonzero value, or the default of 30.
In the message text shown above:
nnnnn
secs
A five-digit number.
The number of seconds.
The message contains data about how the General Service subtask processed requests for one resource. See the
description of message EQQG010I for an explanation of what the data values mean.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQG012I GENERAL SERVICE QUEUE STATISTICS FOLLOW: TYPE
Q20 Q50 Q100 >100
TOTAL
Q1
Q2
Q5
Q10
| Explanation: This message is issued if the GENERAL SERVICE task statistics are active. This can be done either
| by specifying the STATMSG(GENSERV) keyword in the JTOPTS initialization statement, or with the modify command,
| /F subsys,GENSTA=ON.
| This message is issued every n minutes if any requests have been processed, where n is the value specified in the
| JTOPTS keyword STATIM if it has a nonzero value, or the default of 30.
| The message shows the size and delay of the General Service queue since the message was last issued.
The value below the TYPE heading can be either QUEUE SIZE or QUEUE DELAY. The value below the TOTAL
heading gives the total number of times that the General Service queue was emptied. The values below the Qx
headings give the number of times that either the length of the queue, or the time spent waiting for General Service
processing, was in a particular interval. For example, Q20 on the queue size line gives the number of times that the
queue size was between 11 and 20 requests.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQG013I TYPE TOTSZ Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q8
| Explanation: This message is issued if the GENERAL SERVICE task statistics are active. This can be done either
| by specifying the STATMSG(GENSERV) keyword in the JTOPTS initialization statement, or with the modify command,
| /F subsys,GENSTA=ON.
| This message is issued every n minutes if any requests have been processed, where n is the value specified in the
| JTOPTS keyword STATIM if it has a nonzero value, or the default of 30.
In the message text shown above:
nnnnn
A five-digit number.
This message contains data about the General Service queue size. See the description of message EQQG012I for
an explanation of what the data values mean.
System action: Normal TME 10 OPC processing continues.
User response: None.
108
TME 10 OPC Messages and Codes
EQQG014W Ÿ EQQG107I
EQQG014W REQUEST TERMINATED BECAUSE TIME LIMIT IS EXCEEDED
Explanation: A general service request has terminated because the requesting process; a PIF program or a dialog
user, did not respond within 10 minutes.
System action: Processing continues.
User response: None.
EQQG015W REQUEST TERMINATED - REQUESTOR NO LONGER CONNECTED
Explanation: A general service request was terminated because the requesting process, a PIF program or a dialog
user, is no longer connected to the general service task. The connection can be lost if the requestor is cancelled, or if
a dialog user presses the ATTN (attention) key, after a request for service has been sent to the controller and before
a response has been received.
System action: Processing continues.
User response: None.
EQQG100E GDDM COULD NOT BE LOADED
Explanation: When requesting a graph, TME 10 OPC could not load GDDM*.
System action: The graph request is ignored. Processing continues.
User response: Contact your system programmer.
System programmer response: Make sure that the GDDM load library is part of ISPLLIB.
EQQG104W POSITION THE CURSOR ON AN ELEMENT IN THE GRAPHICAL AREA
Explanation: A graph selection command has been given, but the cursor was not located in the graphical area.
System action: The command is ignored. Processing continues.
User response: Position the cursor in the graphical area at or close to the element to be selected and reissue the
command.
EQQG105E DUMMY NODES ARE NOT VALID, REPOSITION CURSOR
Explanation: This node is a dummy node and as such has no data related to it.
System action: The system waits for you to respond.
User response: Specify another node for processing.
EQQG106I THE SPECIFIED ATTRIBUTE MUST BE NUMERIC. SEE GDDM MANUALS
Explanation: An invalid graphical attribute has been given.
System action: The attribute panel is re-displayed and prompts you for a correct attribute value.
User response: Correct the invalid attribute.
EQQG107I GDDM NOT ALLOWED IN SPLIT MODE
Explanation: The GDDM is not allowed in split-screen mode.
System action: The call to GDDM is disabled.
User response: Set the screen in single-screen mode and repeat the command.
Chapter 10. EQQGnnn Messages
109
EQQG109E Ÿ EQQG109E
EQQG109E NET LOADER MODULE COULD NOT BE LOADED
Explanation: When requesting a graph, TME 10 OPC could not load the net building routine.
System action: The graph request is ignored. Processing continues.
User response: Contact your system programmer.
System programmer response: Make sure that the ISPLLIB libraries are updated to contain the graph net building
routines. The name of the routine can be seen in the ISPF log. See message EQQX009.
110
TME 10 OPC Messages and Codes
EQQH001E Ÿ EQQH205E
Chapter 11. EQQHnnn Messages
EQQH001E THE NETVIEW INTERFACE MODULE CNMNETV COULD NOT BE LOADED
Explanation: CNMNETV was not found in the library search path.
System action: TME 10 OPC continues, but the generic alert functions as requested in the GENALERT keyword of
the ALERT initialization statement are disabled. Instead, TME 10 OPC will generate WTO messages for the error
conditions specified in the GENALERT keyword.
System programmer response: Ensure that the CNMNETV module is accessible and start TME 10 OPC again.
EQQH003E SEND GENERIC ALERT TO NETVIEW FAILED WITH RC=RC
Explanation: Request type 12 sent to the NetView* PPI failed.
System action: An WTO will be issued instead of the generic alert.
System programmer response: Check NetView documentation for further information.
EQQH201W AN INCORRECTLY PLACED COMMA AT H20101 IS IGNORED
Explanation: You have coded a comma that is not required at H20101.
System action: The statement is accepted. The extraneous comma is ignored. TME 10 OPC continues verifying the
statements.
User response: Remove the extra comma if you run the job again.
EQQH202W AN INCORRECTLY PLACED COMMA IN THE PARMSTRING IS IGNORED
Explanation: An unnecessary comma is coded in the parameter.
System action: The parameter is accepted and the extraneous comma is ignored. The TME 10 OPC continues
verifying the commands
User response: Remove the extra comma and rerun.
EQQH203E THE KEYWORD H20301 APPEARS TOO MANY TIMES
Explanation: A statement is specified with two or more identical keywords.
System action: TME 10 OPC continues to verify the statement but the database is not updated.
User response: Remove the duplicate keyword and rerun.
EQQH204E THE STATEMENT H20401 IS UNDEFINED
Explanation: The statement H20401 is not recognized.
System action: Processing of the statement ends.
User response: Correct the invalid statement and rerun.
EQQH205E THE COMMAND IS MISSING OR THE FORMAT IS INVALID
Explanation: The statement does not start with a valid command.
System action: Processing of the statement ends.
User response: Add a valid command or correct the invalid command and rerun.
 Copyright IBM Corp. 1991, 1998
111
EQQH206W Ÿ EQQH214E
EQQH206W A MISSING END OF COMMENT IS ASSUMED AT THE END OF THE STATEMENT
Explanation: A start of comment delimiter (/*) has been detected, without a corresponding end of comment (*/).
System action: TME 10 OPC assumes the comment ends after the control statement.
User response: Add an end of comment (*/) and rerun if required.
EQQH207W A MISSING END QUOTE IS ASSUMED AT THE END OF THE STATEMENT
Explanation: The quote for this character string is not closed.
System action: TME 10 OPC assumes the quote ends after the control statement.
User response: Add a quote and rerun if required.
EQQH208E THE KEYWORDS H20801 AND H20802 ARE EXCLUSIVE
Explanation: Two mutually exclusive keywords are entered on the same statement.
System action: Processing of the statement ends.
User response: Remove one of the keywords and rerun.
EQQH209E AN INVALID RIGHT PARENTHESIS WAS FOUND AT H20901
Explanation: More right parentheses than left parentheses are coded.
System action: Processing of the statement ends.
User response: Correct the number of parentheses and rerun.
EQQH210E TOO MANY VALUES ARE CODED IN THE KEYWORD H21001
Explanation: The keyword H21001 cannot have that many values.
System action: Processing of the statement ends.
User response: Correct the keyword values and rerun.
EQQH211E AN INVALID VALUE H21101 SPECIFIED OR A KEYWORD IS MISSPELLED
Explanation: Either the value H21101 is not valid for the keyword, or the keyword is misspelled.
System action: Processing of the statement ends.
User response: Correct the statement and rerun.
EQQH213E A VALUE IS MISSING AFTER H21301
Explanation: Not enough keyword values for H21301 are specified.
System action: Processing of the statement ends.
User response: Add the missing keyword value(s) and rerun.
EQQH214E TOO MANY LEFT PARENTHESES OR AN INVALID VALUE FOUND AT H21401
Explanation: Too many parentheses at H21401 are provided, or you have provided an invalid value for a keyword.
System action: Processing of the statement ends.
User response: Correct the statement and rerun.
112
TME 10 OPC Messages and Codes
EQQH215E Ÿ EQQH222E
EQQH215E TOO MANY LEFT PARENTHESES ARE INSERTED IN THE PARMSTRING
Explanation: Too many left parentheses are provided.
System action: Processing of the statement ends.
User response: Remove the extra left parentheses and rerun.
EQQH216E A LEFT PARENTHESIS IS MISSING BEFORE H21601
Explanation: A left parenthesis is omitted.
System action: Processing of the statement ends.
User response: Add the missing left parentheses and rerun.
EQQH217E AN INVALID COMMA IS INSERTED IN H21701
Explanation: A keyword and its values are separated by an invalid comma.
System action: Processing of the statement ends.
User response: Remove the comma and rerun.
EQQH218W A MISSING RIGHT PARENTHESIS IS ASSUMED AT THE END OF THE STATEMENT
Explanation: The right parenthesis, which should delimit the end of statement, is missing. Too many items might be
specified.
System action: The Processing continues.
User response: Specify the keyword and its value in the correct format and rerun.
EQQH219E THE REQUIRED KEYWORD H21901 IS MISSING
Explanation: The keyword H21901 is missing from the statement.
System action: Processing of the statement ends.
User response: Specify the missing keyword and rerun.
EQQH220E A REQUIRED KEYWORD IS MISSING. SPECIFY EITHER H22001 OR H22002
Explanation: You must specify either H22001 or H22002.
System action: Processing of the statement ends.
User response: Specify one of the keywords and rerun.
EQQH221E AN INVALID H22101 H22102 WAS FOUND IN THE KEYWORD H22103
Explanation: The value type H22101 in field H22102 for keyword H22103 is invalid.
System action: Processing of the statement ends.
User response: Specify a valid value and rerun.
EQQH222E AT LEAST ONE KEYWORD MUST BE SPECIFIED FOR STATEMENT H22201
Explanation: Specify at least one keyword for H22201.
System action: Processing of the statement ends.
User response: Correct the command and rerun.
Chapter 11. EQQHnnn Messages
113
EQQH223E Ÿ EQQH306W
EQQH223E THE EMPTY QUOTED STRING IS INVALID FOR THE KEYWORD H22301
Explanation: No values for keyword H22301 are specified.
System action: Processing of the statement ends.
User response: Correct the string and rerun.
EQQH224E REQUIRED KEYWORD(S) MISSING IN COMMAND H22401
Explanation: One or more required keywords were not found in the statement H22401.
System action: Processing of the statement ends.
User response: Correct the statement and rerun.
EQQH301E NUMERIC FACTOR H30101 EXCEEDS CYCLE H30102 LENGTH
Explanation: Numeric factor out of range.
System action: The rule is invalid and will not be saved.
User response: Correct the numeric factor or cycle specification and rerun.
EQQH302E NUMERIC FACTOR H30201 AND WEEKDAY > CYCLE H30202 LENGTH
Explanation: Numeric factor combined with a week day exceeds the period length. Name of a predefined cycle is
preceded by two unprintable characters (..).
System action: The rule is invalid and will not be saved.
User response: Correct the numeric factor or cycle specification and rerun.
EQQH303E THE USER PERIOD H30301 DOES NOT EXIST
Explanation: Invalid user period specified. Name of OPC predefined cycles is preceded by two unprintable
characters (..).
System action: The rule is invalid and will not be saved.
User response: Correct the period specification and rerun.
EQQH304E THE CALENDAR H30401 DOES NOT EXIST
Explanation: Invalid calendar H30401 specified.
System action: The rule is invalid and will not be saved.
User response: Correct the calendar specification and rerun.
EQQH305E ORIGIN SHIFT H30501 IS TOO LARGE FOR THE PERIOD H30502.
Explanation: The number specified for origin shift is out of range for period H30501. Name of OPC predefined
cycles is preceded by two unprintable characters (..).
System action: The rule is invalid and will not be saved.
User response: Correct the origin shift or period specification and rerun.
EQQH306W SELECTION OF EVERY AND FIRST/LAST - INTERPRETED AS EVERY
Explanation: You have selected both EVERY and FIRST (or numeric 1), or EVERY and LAST during the definition
of a rule. The rule is interpreted as EVERY without any numeric factor. This may not be what you intended.
System action: The system waits for you to respond.
User response: Decide whether the rule should be defined using EVERY or ONLY. Change the selected fields if
required. If you are unsure of the affect of EVERY and ONLY use the GENDAYS command.
114
TME 10 OPC Messages and Codes
EQQH308W Ÿ EQQH502E
EQQH308W DUPLICATE VALUE(S) H30801 IGNORED.
Explanation: You have specified duplicate values. Only one of the values will be used.
System action: Duplicate value removed.
User response: Check the specified values, and correct them if necessary.
EQQH309E THE SAVED RULE VALUE HAS BEEN DESTROYED, PLEASE REENTER THE INFO
Explanation: The rule value saved on the AD data base is not valid can not be used.
System action: The rule is invalid and must be reentered before use.
User response: Reenter the rule and rerun.
Problem determination: The diagnostic file of the TME 10 OPC subsystem (ddname EQQDUMP) contains a dump
of the rule value.
EQQH310E UNEXPECTED ERROR IN THE CALENDAR ROUTINE
Explanation: The calendar routine used in the rule interpretation or date generation has returned an unexpected
reason code.
System action: Processing of this specific rule cannot continue.
Problem determination: The diagnostic file of the TME 10 OPC subsystem (ddname EQQDUMP) contains a dump
of the control blocks.
User response: This is likely to be an internal error. If possible, rerun the request.
System programmer response: If you cannot find a valid reason for the error, save the diagnostic file and the
message log and contact your IBM representative.
EQQH401I NO DATE GENERATED BY THIS RULE
Explanation: No date generated by this rule.
System action: No dates generated.
User response: Inspect the rule and the validity period.
EQQH402W THE PERIOD H40201 HAS NO ORIGIN WITHIN RULE VALIDITY.
Explanation: Period H40201 has no origin within rule validity period.
System action: No dates generated.
User response: Correct the period specification or validity period and rerun.
EQQH501E NUMERIC FACTOR H50101 EXCEEDS CYCLE H50102 LENGTH
Explanation: Numeric factor out of range.
System action: The rule is invalid and will not be saved.
User response: Correct the numeric factor or cycle specification and rerun.
EQQH502E NUMERIC FACTOR H50201 TOGETHER WITH WEEKDAY EXCEEDS CYCLE H50202 LENGTH
Explanation: Numeric factor combined with a week day exceeds the period length. Note that name of a predefined
cycle is preceded by two unprintable characters.
System action: The rule is invalid and will not be saved.
User response: Correct the numeric factor or cycle specification and rerun.
Chapter 11. EQQHnnn Messages
115
EQQH503E Ÿ EQQH511E
EQQH503E THE USER PERIOD H50301 DOES NOT EXIST
Explanation: Invalid user period specified. The name of TME 10 OPC predefined cycles is preceded by two
unprintable characters.
System action: The rule is invalid and will not be saved.
User response: Correct the period specification and rerun.
EQQH504E THE CALENDAR H50401 DOES NOT EXIST
Explanation: Invalid calendar H50401 specified.
System action: The rule is invalid and will not be saved.
User response: Correct the calendar specification and rerun.
EQQH505E ORIGIN SHIFT H30501 IS TOO LARGE FOR THE PERIOD H30502.
Explanation: The number specified for origin shift is out of range for period H50501. Note that the name of a
predefined cycle is preceded by two unprintable characters.
System action: The rule is invalid and will not be saved.
User response: Correct the origin shift or period specification and rerun.
EQQH509E THE SAVED RULE VALUE HAS BEEN DESTROYED, PLEASE REENTER THE INFORMATION
Explanation: The rule value saved on AD data base is invalid and can not be used.
System action: The rule is invalid and must be reentered before use.
User response: Reenter the rule and rerun.
Problem determination: The diagnostic file of the TME 10 OPC subsystem (ddname EQQDUMP) contains a dump
of the rule value.
EQQH510E UNEXPECTED ERROR IN THE CALENDAR ROUTINE
Explanation: The calendar routine used in the rule interpretation or date generation has returned an unexpected
reason code.
System action: Processing of this specific rule cannot continue.
Problem determination: The diagnostic file of the TME 10 OPC subsystem (ddname EQQDUMP) contains a dump
of the control blocks.
User response: This is likely to be an internal error. If possible, rerun the request.
System programmer response: If you cannot find a valid reason for the error, save the diagnostic file and the
message log and contact your IBM representative.
| EQQH511E CALENDARS DATASPACE CREATION FAILED
| Explanation: An error occurred while the batch program or the normal mode manager subtask was trying to create
| the calendar dataspace.
| System action: The job or the normal mode manager terminates.
| User response: Contact your system programmer.
| System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
| cannot determine the cause and if the error persists, contact your IBM representative.
116
TME 10 OPC Messages and Codes
EQQH700I Ÿ EQQH706E
EQQH700I HIGHEST RETURN CODE FROM PARSER IS H70001
Explanation: This information message is displayed after parsing a date generating rule. The short message is set
to 'VALID RULE' if the parser returns 04 or lower, 'INVALID RULE' for all other return codes. The return code value is
shown in H70001. This message is followed by one or more information or warning messages for a valid rule, and by
up to 5 error messages for an invalid rule.
System action: If 'VALID RULE' is returned then the date generating rule definition is accepted. If 'INVALID RULE'
is returned then the rule is rejected.
User response: If the rule was rejected, then correct the rule definition according to the diagnostics provided by the
messages.
EQQH701E EITHER ONLY OR EVERY MUST BE SELECTED
Explanation: ONLY and EVERY are mutually exclusive, and one of them has to be selected for a valid rule
definition.
System action: The request is rejected.
User response: Select one of ONLY and EVERY.
EQQH702E MAKE AT LEAST ONE SELECTION/SPECIFICATION FROM EACH RULE SECTION
Explanation: You have failed to make at least one selection/specification from each rule section.
System action: The request is rejected.
User response: Select at least one from each section.
EQQH703E THE ENTRY IS INVALID, ENTER XRSEL OR LEAVE BLANK
Explanation: You have entered an invalid value in the selection field.
System action: The request is rejected.
User response: Change the field to a valid value.
EQQH704E THE ENTRY IS INVALID, ENTER A DAY IN THE RANGE 1 TO 999
Explanation: You have entered an invalid day in the field. It must be in the range 1 to 999.
System action: The request is rejected.
User response: Change the day to a valid value.
EQQH705E A PERIOD NAME BEGINS ALPHABETICALLY, REMAINDER IS ALPHANUMERIC
Explanation: You have not entered a valid period name. A valid period name must be maximum 8 characters, first
character must be alphabetical and the remaining characters alphanumeric, or national.
System action: The request is rejected.
User response: Specify a valid period name.
EQQH706E THE ENTRY IS INVALID, ENTER A VALUE IN THE RANGE 1 TO 53
Explanation: You have entered an invalid week number in the field. It must be in the range 1 to 53.
System action: The request is rejected.
User response: Change the week number to a valid value.
Chapter 11. EQQHnnn Messages
117
EQQH707E Ÿ EQQH711E
EQQH707E THE ENTRY IS INVALID, ENTER A NUMBER IN THE RANGE 0 TO 999
Explanation: You have entered an invalid number in the field, it must be in the range 0 to 999.
System action: The request is rejected.
User response: Change the number to a valid value.
EQQH708E H70801 TOGETHER WITH SPECIFIC H70801 SELECTION(S) IS AMBIGUOUS
Explanation: Message variable H70801 is DAY, WEEK or MONTH. You have selected either:
Ÿ DAY together with specific days such as WORKDAY, MONDAY, FRIDAY
Ÿ WEEK together with specific week numbers such as WEEK 26 and WEEK 34
Ÿ MONTH together with specific months such APRIL, AUGUST and DECEMBER.
Such specifications are redundant and make the rule ambiguous.
System action: The request is rejected.
User response: Remove the redundancies to make the selection unambiguous.
EQQH709E RULE DEFINITION CANNOT BE MAPPED, THE RULE MUST BE REDEFINED
Explanation: The internal representation of a rule cannot be interpreted, and the corresponding rule command
cannot be derived from it. This is most likely caused by an internal OPC/ESA error.
System action: The rule command is not mapped and rule selections are not shown.
User response: Copy the AD temporarily to another AD identification. Then update the original AD by redefining the
erroneous rule so as to be able to continue using the original rule(s). Contact your local IBM Representative to
pursue the error analysis using the copied version.
EQQH710I NO DATES GENERATED FOR THE INTERVAL IVLFROM IVLTO
Explanation: GENDAYS is unable to generate dates for the rule and interval specified.
System action: No dates generated.
User response: Check the rule definitions and other factors that have an impact on date generation, such as
interval, calendar, user periods, and free day rule.
EQQH711E INTERVAL START IVLFROM IS LATER THAN INTERVAL END IVLTO
Explanation: The start date of the generating interval is later than the end date.
The start date of the interval is the latest of these dates:
Ÿ Run cycle in-effect date
Ÿ AD valid-from date
Ÿ 1 January of the current year.
The end date of the interval is the earliest of these dates:
Ÿ Run cycle out-of-effect date
Ÿ AD valid-to date
Ÿ 31 December of the current year plus three years.
A maximum of 4 years can be displayed.
System action: The request is rejected.
User response: Check the dates, correct any inconsistency, and enter the GENDAYS command again.
118
TME 10 OPC Messages and Codes
EQQH712E Ÿ EQQH712E
EQQH712E UNABLE TO GENERATE DATES FOR THE INTERVAL IVLFROM IVLTO
Explanation: GENDAYS is not able to generate dates for the rule because the entire requested interval is outside
the limits of the internal calendar
When the interval is calculated:
Ÿ The start date of the interval is the later of the run cycle in-effect date and the AD valid-from date.
Ÿ The end date of the interval is the earlier of the run cycle out-of-effect date and the AD valid-to date.
GENDAYS can generate a maximum of 4 years starting at 1 January of the current year and ending on 31 December
of the current year plus three.
System action: The request is rejected.
User response: Check the dates for the interval, correct any inconsistency, and enter the GENDAYS command
again.
Chapter 11. EQQHnnn Messages
119
120
TME 10 OPC Messages and Codes
EQQIC00I Ÿ EQQIC03E
Chapter 12. EQQICnn Messages
EQQIC00I FILE FILE HAS BEEN CONVERTED NCOPY RECORDS COPIED, NUPD RECORDS UPDATED, NSKIP
RECORDS SKIPPED
Explanation: An OPC VSAM file has been successfully built from the corresponding file in a different release of
OPC. This message documents the number of records copied without change, the number of modified records, and
the number of records in the input file that were not used.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file.
Problem determination: If there is a problem using the output file, verify that the statistical information in this
message is correct.
System programmer response: None.
EQQIC01E THE INPUT DATA SET, DDNAME = SYSIN, COULD NOT BE OPENED
Explanation: The file migration program could not open its input dataset.
System action: The migration program ends.
System programmer response: Check that the SYSIN DD statement exists and is correctly coded.
Correct the errors, and resubmit the file migration batch job.
EQQIC02E UNABLE TO CONVERT FILE FILE
Explanation: The file migration program could not execute the requested file conversion. This message is preceded
by one or more error messages that describe the problem.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file.
Problem determination: Check the previous messages to determine the cause of the problem.
Verify that:
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
The
The
The
The
The
The
output datasets are empty VSAM datasets.
output datasets are correctly allocated.
job executing the migration program is authorized to update the output datasets.
input datasets do not contain errors.
input datasets are OPC VSAM datasets at the level specified.
migration program is authorized to read the input datasets.
System programmer response: Correct the errors, and resubmit the file migration batch job.
EQQIC03E LOGICAL RECORD SIZE FOR THE INPUT DATA SET, DDNAME SYSIN, IS NOT VALID
Explanation: The file migration program could not use the input dataset, SYSIN, because its logical record length is
not 80 bytes.
System action: The migration program ends.
Problem determination: Check that the SYSIN DD statement exists and is correctly coded.
System programmer response: Correct the errors, and resubmit the file migration batch job. If necessary, copy
SYSIN statements to a file that has record size 80 bytes.
 Copyright IBM Corp. 1991, 1998
121
EQQIC04E Ÿ EQQIC08I
EQQIC04E EQQICTOP TERMINATED BECAUSE OF UNRECOVERABLE ERRORS
Explanation: A severe error occurred during the execution of the file migration program.
System action: The migration program ends.
Problem determination: Review the message log and the dump dataset.
System programmer response: If you cannot determine the cause of the error, contact your IBM representative.
| EQQIC05E WRITE OF NEW RECORD FAILED, RECORD WITH SAME KEY IS ALREADY PRESENT
| Explanation: A VSAM error occurred when writing a new record to the output data set. Error codes indicate that the
| output data set contains a record with the same key as the new record.
| System action: The migration program continues processing with the next CONVERT statement, if one is defined.
| System programmer response: Make sure that the output data set is empty when the migration starts.
EQQIC06W THE INPUT DATA SET DOES NOT CONTAIN ANY TYPE RECORDS
Explanation: An OPC VSAM file has been successfully built from the corresponding file in a different OPC release,
but the input dataset did not contain all of the record types that were expected.
System action: The migration program continues processing by reading the next CONVERT statement from the
SYSIN file. The return code for the current CONVERT statement is set to 4.
Problem determination: If there is a problem using the output file, verify that the input dataset was correctly
specified.
System programmer response: None.
EQQIC07E APPLICATION AD WITH INPUT ARRIVAL IA AND OPERNUM OP£ THE FOLLOWING SPECIAL
RESOURCES CAUSE OUTPUT RECORD SIZE TO BE EXCEEDED:
Explanation: During conversion of the current plan operation record identified in the message text, the migrated
output record would be too great to store without modification. At least one special resource referenced by the
operation cannot be included. The subsequent message EQQIC08I identifies the special resources that cannot fit.
System action: The migration program terminates. No valid current plan has been created.
Problem determination: As each special resource entry is expanded 8 bytes, while the maximum record size
remains the same, it is possible to encounter this problem.
System programmer response: Start up the previous release of OPC/ESA or OPC/A and delete any special
resource entries from the operation that are unnecessary. The entries you delete do not have to be those identified in
EQQIC08I.
EQQIC08I SR
Explanation: This message is associated with EQQIC07E. It lists those special resources that could not fit into the
output current plan record.
System action: The migration program terminates.
System programmer response: See the description for message EQQIC07E.
122
TME 10 OPC Messages and Codes
EQQIC09E Ÿ EQQIC14E
EQQIC09E APPLICATION INDEX RECORD FOR AD HAS AN INVALID INPUT ARRIVAL IA FOR AN
OCCURRENCE IN STATUS ST
Explanation: A current plan application index record CPLREC05, identified in the message text, contains an invalid
input arrival date in one of its occurrence data.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file. No valid Current Plan is created.
System programmer response: Do one of the following:
Ÿ Update the occurrence with a valid I/A date.
Ÿ If the occurrence status is complete, run two or more CP EXTENDS to delete it from the Current Plan, before
rerunning the conversion.
EQQIC10E THE FILE KEYWORD IS MISSING
Explanation: The current CONVERT statement does not contain the FILE keyword.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file.
System programmer response: Add the FILE keyword to the current CONVERT statement, and resubmit the file
migration batch job.
EQQIC11E A PARAMETER IS REQUIRED FOR THE FILE KEYWORD
Explanation: The FILE keyword in the current CONVERT statement does not specify a value.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file.
System programmer response: Add a file name value to the FILE keyword of the current CONVERT statement,
and resubmit the file migration batch job.
EQQIC12E THE FROMREL KEYWORD IS MISSING
Explanation: The current CONVERT statement does not contain the FROMREL keyword.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file.
System programmer response: Add the FROMREL keyword to the current CONVERT statement, and resubmit the
file migration batch job.
EQQIC13E A PARAMETER IS REQUIRED FOR THE FROMREL KEYWORD
Explanation: The FROMREL keyword in the current CONVERT statement does not specify a value.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file.
System programmer response: Add a file name value to the FROMREL keyword of the current CONVERT
statement, and resubmit the file migration batch job.
EQQIC14E THE TOREL KEYWORD IS MISSING
Explanation: The current CONVERT statement does not contain the TOREL keyword.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file.
System programmer response: Add the TOREL keyword to the current CONVERT statement, and resubmit the file
migration batch job.
Chapter 12. EQQICnn Messages
123
EQQIC15E Ÿ EQQIC20W
EQQIC15E A PARAMETER IS REQUIRED FOR THE TOREL KEYWORD
Explanation: The TOREL keyword in the current CONVERT statement does not specify a value.
System action: The migration program continues processing by reading the next CONVERT statement from the
input file.
System programmer response: Add a file name value to the TOREL keyword of the current CONVERT statement,
and resubmit the file migration batch job.
EQQIC16W INPUT APPLICATION APPL IS TOO LARGE TO BE WRITTEN TO THE OUTPUT FILE
Explanation: An application description in the input AD file defined to the migration program is too large to be written
to the output data set. The most likely cause of this message is that the maximum record size is larger for the input
AD file than for the output AD file.
System action: The current input AD record is skipped. The migration program continues normal processing by
reading next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Determine if the maximum record size defined for the output AD file is too small. If
it is, reallocate the output AD file and reexecute the migration program. If this is fallback to an earlier OPC release,
determine if the application is needed. If it is, define it using the AD dialog for the earlier OPC release.
EQQIC17E INPUT LTP OCCURRENCE APPL IA IS TOO LARGE TO BE WRITTEN TO THE OUTPUT FILE
Explanation: A long term plan occurrence in the input LTP file defined to the migration program is too large to be
written to the output data set. The most likely cause of this message is that the maximum record size is larger for the
input LTP file than for the output LTP file.
System action: The current input LTP record cannot be converted to the format of the output file. The migration
program continues processing by reading next record on the input file but no more records are written to the output
file. Return code for the current CONVERT command will be 8 or higher.
System programmer response: Determine if the maximum record size defined for the output LTP file is too small.
If it is, reallocate the output LTP file and reexecute the migration program.
If this is fallback to an earlier OPC release, use the LTP dialog to delete the problem occurrence in the input LTP file,
then reexecute the migration program. Determine if the occurrence is needed. If it is, define it using the LTP dialog
for the earlier OPC release.
EQQIC18E FROMREL AND TOREL COMBINATION NOT SUPPORTED FOR FILE FILE
Explanation: The file FILE specified in the current CONVERT statement is not supported by the release defined for
the FROMREL or TOREL keyword.
System action: The migration program continues processing with the next CONVERT statement, if one is defined.
System programmer response: Refer to TME 10 OPC Installation Guide for information about the valid
combinations. Correct the value in the FILE, FROMREL, or TOREL keyword of the current CONVERT statement and
resubmit the job.
EQQIC20W INPUT JCL VARIABLE TABLE RECORD JCL UPDATED AFTER 1999-12-31 AND CANNOT BE
CONVERTED
Explanation: The JCL variable table record has been updated after 1999-12-31, so it cannot be converted for
fallback to a release that does not support dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Update or delete the JCL variable table record then resubmit the migration
program.
124
TME 10 OPC Messages and Codes
EQQIC21W Ÿ EQQIC25W
EQQIC21W INPUT APPLICATION APPL CONTAINS A DATE LATER THAN 1999-12-31 AND CANNOT BE
CONVERTED
Explanation: An application description in the input AD file is not valid 1999-12-31 or earlier, or it contains a run
cycle that is not valid 1999-12-31 or earlier, or it has been updated after 1999-12-31, so it cannot be converted for
fallback to a release that does not support dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Update the application description then resubmit the migration program.
EQQIC22I INPUT APPLICATION APPL HAS A VALID-TO DATE LATER THAN 1999-12-31. VALID-TO DATE SET
TO 1999-12-31
Explanation: An application description in the input AD file has a valid-to date later than 1999-12-31 or a run cycle
with an out-of-effect date later than 1999-12-31 when converting for fallback to a release that does not support dates
after 1999-12-31.
System action: The current input record is converted. Valid-to date, or out-of-effect date, is set to 1999-12-31.
The migration program continues normal processing by reading next record on the input file.
System programmer response: None.
EQQIC23W INPUT PERIOD PER CONTAINS A DATE LATER THAN 1999-12-31 AND CANNOT BE CONVERTED
Explanation: A period description in the input WS file has an interval origin date or interval end date later than
1999-12-31, or the description has been updated after 1999-12-31, so it cannot be converted for fallback to a release
that does not support dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Update or delete the period description record and resubmit the migration program.
EQQIC24W INPUT WORKSTATION DESCRIPTION WS HAS A DATE LATER THAN 1999-12-31 AND CANNOT BE
CONVERTED
Explanation: A workstation description in the input WS file has a specific date later than 1999-12-31, or the
description has been updated after 1999-12-31, so it cannot be converted for fallback to a release that does not
support dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Update or delete the workstation description and resubmit the migration program.
EQQIC25W INPUT CALENDAR CAL CONTAINS A DATE LATER THAN 1999-12-31 AND CANNOT BE
CONVERTED
Explanation: A calendar description in the input WS file has a specific date later than 1999-12-31, or it has been
updated after 1999-12-31, so it cannot be converted for fallback to a release that does not support dates later than
1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Update or delete the calendar description and resubmit the migration program.
Chapter 12. EQQICnn Messages
125
EQQIC26W Ÿ EQQIC29E
EQQIC26W INPUT ALL WORKSTATION CLOSED WAC HAS A DATE LATER THAN 1999-12-31 AND CANNOT
BE CONVERTED
Explanation: An all workstation closed record in the input WS file has a specific date later than 1999-12-31, or the
record has been updated after 1999-12-31, so it cannot be converted for for fallback to a release that does not
support dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Update or delete the workstation closed record and resubmit the migration
program.
EQQIC27W INPUT OPERATOR INSTRUCTION OI HAS A DATE LATER THAN 1999-12-31 AND CANNOT BE
CONVERTED
Explanation: An operator instruction record in the input OI file has a valid-from or valid-to date later than
1999-12-31, or the record has been updated after 1999-12-31, so it cannot be converted for fallback to a release that
does not support dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Update or delete the operator instruction and resubmit the migration program.
EQQIC28E INPUT LTP HEADER RECORD HAS A DATE LATER THAN 1999-12-31. LTP CANNOT BE
CONVERTED
Explanation: One or more of the following dates in LTP header is later than 1999-12-31, so the LTP cannot be
converted for fallback to a release that does not support dates later than 1999-12-31.
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
LTP start date
LTP end date
LTP latest update date
First noncompleted occurrence
Plan next period end date
System action: The migration program continues processing by reading the next CONVERT statement from the
input file. Return code for the current CONVERT command will be 8.
System programmer response: A new LTP must be created after fallback.
EQQIC29E INPUT LTP OCCURRENCE APPL IA HAS A DATE LATER THAN 1999-12-31. LTP CANNOT BE
CONVERTED
Explanation: One or more of the following dates in LTP occurrence is later than 1999-12-31, so the LTP cannot be
converted for fallback to a release that does not support dates later than 1999-12-31.
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Run date
Original run date
Deadline date
Predecessor run date
Successor run date
Operation input arrival date
Operation deadline date
System action: The migration program continues processing by reading the next CONVERT statement from the
input file. Return code for the current CONVERT command will be 8.
System programmer response: A new LTP must be created after fallback.
126
TME 10 OPC Messages and Codes
EQQIC30E Ÿ EQQIC31E
EQQIC30E INPUT CURRENT PLAN HAS A DATE LATER THAN 1999-12-31. CURRENT PLAN CANNOT BE
CONVERTED
Explanation: One or more of the following dates in current plan header record or common information is later than
1999-12-31, so the current plan cannot be converted for fallback to a release that does not support dates later than
1999-12-31.
Ÿ In header record:
– Current plan creation date
– Last plan next period end
– Last backup date
– Tail end date
– Report period start date
Ÿ In workstation record:
– Interval start date
– Interval end date
Ÿ In AD index record:
– Input arrival date
– Actual completion or deadline date
Ÿ In remaining slack record:
– Earliest latest start date
Ÿ In workstation activity record:
– Activity date
Ÿ In catalog management record:
– Input arrival date
Ÿ In job log retrieval record:
– Input arrival date
System action: The migration program continues processing by reading the next CONVERT statement from the
input file. Return code for the current CONVERT command will be 8.
System programmer response: A new current plan must be created after fallback.
EQQIC31E INPUT CURRENT PLAN OCCURRENCE AD IA HAS A DATE LATER THAN 1999-12-31. CURRENT
PLAN CANNOT BE CONVERTED
Explanation: One or more of the following dates in a current plan occurrence or operation is later than 1999-12-31,
so the current plan cannot be converted for fallback to a release that does not support dates later than 1999-12-31.
Ÿ In occurrence record:
– Input arrival date from LTP
– Modified input arrival date or input arrival date from LTP
– Deadline date
– Actual arrival date
– Actual completion date
Ÿ In operation record:
– Application input arrival date after MCP update
– Planned start date
– Planned end date
– Operation input arrival date
– Operation deadline date
– Latest out date for operation
– Actual start date
– Actual arrival date
– Intermediate start date
– Actual end date
Ÿ In undecided operation record:
– Input arrival date
System action: The migration program continues processing by reading the next CONVERT statement from the
input file. Return code for the current CONVERT command will be 8.
System programmer response: A new current plan must be created after fallback.
Chapter 12. EQQICnn Messages
127
EQQIC32W Ÿ EQQIC36E
EQQIC32W JCL DATASET RECORD FOR APPLICATION APPL WITH INPUT ARRIVAL IA AND OPERATION
NUMBER OP£ CONTAINS A DATE LATER THAN 1999-12-31 AND CANNOT BE CONVERTED
Explanation: A JCL dataset record in the input file has an occurrence input arrival date later than 1999-12-31 or the
record has been updated after 1999-12-31, so it cannot be converted for fallback to a release that does not support
dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: None.
EQQIC33W SPECIAL RESOURCE DATASET RECORD SR CONTAINS A DATE LATER THAN 1999-12-31 AND
CANNOT BE CONVERTED
Explanation: A special resource dataset record in the input file has an interval date later than 1999-12-31 or the
record has been updated after 1999-12-31, so it cannot be converted for fallback to a release that does not support
dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: Update or delete the special resource record and resubmit the migration program.
EQQIC34W ETT RECORD SI UPDATED AFTER 1999-12-31 AND CANNOT BE CONVERTED
Explanation: An ETT record in the input SI file has been updated later than 1999-12-31, so it cannot be converted
for fallback to a release that does not support dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: If the ETT record is correctly defined in the RD database, no action is required. If
not, use SRSTART or EVPGM to add the record to the CX file.
EQQIC35W JOBLOG RECORD FOR APPLICATION APPL WITH INPUT ARRIVAL IA AND OPERATION NUMBER
OP£ HAS INPUT ARRIVAL DATE LATER THAN 1999-12-31 AND CANNOT BE CONVERTED
Explanation: A Joblog record in the input JCL file has an occurrence input arrival date later than 1999-12-31, so it
cannot be converted for fallback to a release that does not support dates later than 1999-12-31.
System action: The current input record is skipped. The migration program continues normal processing by reading
next record on the input file. Return code for the current CONVERT command will be 4 or higher.
System programmer response: None.
| EQQIC36E CURRENT PLAN RECORD OF TYPE RECID FOR APPLICATION AD WITH INPUT ARRIVAL IA AND
|
OPERATION NUMBER OPNUM IS NOT VALID, TOO HIGH OPERATION NUMBER, CANNOT BE
|
CONVERTED
| Explanation: The operation number in one of the records in the input file is higher than the range supported by the
| TME 10 OPC release to which you are migrating. RECID is the current plan record type:
|
|
|
|
03
09
13
14
An operation record
A rerun record
A catalog management record
A joblog record
| System action: The migration fails without producing a migrated current plan file.
| User response: Update the current plan file being migrated using the OPC dialog or the program interface to ensure
| that all the operation numbers are in the range supported by the release to which you are migrating.
| System programmer response: None.
128
TME 10 OPC Messages and Codes
EQQIC37E Ÿ EQQIC38W
| EQQIC37E CURRENT PLAN RECORD OF TYPE RECID FOR APPLICATION AD WITH INPUT ARRIVAL IA IS
|
NOT VALID, TOO HIGH OCCURRENCE NUMBER, CANNOT BE CONVERTED
| Explanation: The occurrence number in one of the records in the input file is higher than the range supported by the
| TME 10 OPC release you are migrating to. RECID is the current plan record type:
|
|
|
|
03
09
13
14
An operation record
A rerun record
A catalog management record
A joblog record
| System action: The migration fails without producing a migrated current plan file.
| User response: Perform daily planning to reduce the number of occurrences in the current plan being migrated.
| The BATCHOPT parameter PREVRES should be set to NO at the replan. If the current plan still has too many
| occurrences, do one of the following:
|
|
Ÿ Run TME 10 OPC until enough occurrences have been completed.
Ÿ Delete occurrences, using the OPC dialog or the program interface.
| Then repeat the plan.
| System programmer response: None.
| EQQIC38W RECTYP RECORD FOR OCCURRENCE AD AI, OPERATION OPNUM IS TOO LARGE TO BE
|
WRITTEN TO THE OUTPUT FILE
| Explanation: A record in the input JS file defined to the migration program is too large to be written to the otput file.
| This is most likely because the maximun record size is larger for the input JS file than for the output JS file.
| System action: The record that is too large is ignored. The migration program continues to process normally. The
| return code for the current CONVERT run will be at least 4.
| System programmer response: Determine whether the maximum record size defined for the JS file is too small.
| Then reallocate the file and rerun the migration job.
Chapter 12. EQQICnn Messages
129
130
TME 10 OPC Messages and Codes
EQQJ001I Ÿ EQQJ010I
Chapter 13. EQQJnnn Messages
EQQJ001I ETT ACTIVATION/DEACTIVATION REQUEST WAS NOT CONFIRMED
Explanation: You chose not to confirm the original request, and so it was ignored by TME 10 OPC.
System action: None.
User response: None.
EQQJ002W ETT ACTIVATION REQUEST IGNORED SINCE ETT ALREADY ACTIVE
Explanation: The ETT function was already active when you requested activation of the function.
System action: None.
User response: None.
EQQJ003W ETT DEACTIVATION REQUEST IGNORED SINCE ETT NOT ACTIVE
Explanation: The ETT function was not active when you requested deactivation of the function.
System action: None.
User response: None.
EQQJ004I ETT FUNCTION HAS BEEN SUCCESSFULLY ACTIVATED
Explanation: The ETT activation request has been successfully processed.
System action: None.
User response: None.
EQQJ005I ETT FUNCTION HAS BEEN SUCCESSFULLY DEACTIVATED
Explanation: The ETT deactivation request has been successfully processed.
System action: None.
User response: None.
EQQJ006W ETT REQUEST IGNORED DUE TO LACK OF PROPER AUTHORIZATION
Explanation: You have attempted to use the ETT function but you do not have the necessary authorization.
System action: None.
User response: Contact your TME 10 OPC security administrator.
EQQJ010I YOUR CHANGES HAVE SUCCESSFULLY UPDATED THE ETT DATABASE
Explanation: Your modifications to the ETT table have successfully updated the ETT database.
System action: None.
User response: None.
 Copyright IBM Corp. 1991, 1998
131
EQQJ011E Ÿ EQQJ022E
EQQJ011E YOUR CHANGES DID NOT UPDATE THE ETT DATABASE DUE TO ERRORS
Explanation: Your modifications to the ETT table did not update the table dataset due to some error in the TME 10
OPC subsystem.
System action: None.
User response: You should exit from this panel, and then enter it again to determine which modifications updated
the ETT database. Reenter those modifications that did not take effect. If the errors persist, then contact your system
programmer.
System programmer response: Review the TME 10 OPC message log for I/O errors pertaining to the table
dataset. Correct all errors and restart TME 10 OPC.
EQQJ012E YOUR CHANGES TO THE ETT CRITERIA CONTAIN SYNTAX ERROR(S)
Explanation: Your changes to the ETT criteria contain syntax error(s).
System action: None.
User response: Enter correct data.
EQQJ013E THE ETT CRITERIA IS BEING UPDATED BY SOMEONE ELSE - TRY LATER
Explanation: Another user is currently updating the ETT criteria table. Only one person can use the table at a time.
System action: None.
User response: Try again later.
EQQJ014E VALID MATCHING TYPES ARE E, P, AND S.
Explanation: For the data entry error, the valid matching types are: E for Exact, P for Prefix, and S for Suffix
matching.
System action: None.
User response: Enter the right matching type.
EQQJ020E AVAILABILITY STATUS CHANGE INFO MUST BE SPECIFIED FOR RESOURCE EVENTS
Explanation: You have defined a triggering event as a resource event but failed to indicate if ETT triggering should
occur only for an availability status switch from NO to YES, or if ETT triggering should occur whenever the availability
is set to YES.
System action: The system waits for you to respond.
User response: If you want the ETT triggered application to be added only when the resource is switched from
unavailable to available, specify Y in the availability switch field. If the application should be added everytime the
resource is set to available, regardless of the old status, set the availability switch to N.
EQQJ021E ETT EVENT TYPE MUST BE OCHCJOB OR OCHCRES
Explanation: ochcjob and ochcres are the national language characters for 'J' (job) and 'R' (resource).
System action: The system waits for you to respond.
User response: Enter correct data.
EQQJ022E JOB NAME REPLACEMENT INFO MUST BE SPECIFIED FOR JOB EVENTS
Explanation: You have specified the event to be a job event, but failed to indicate whether the job name in the first
operation of the added application should be replaced or not.
System action: The system waits for you to respond.
User response: Enter correct data.
132
TME 10 OPC Messages and Codes
EQQJ023E Ÿ EQQJ029E
EQQJ023E JOB NAME REPLACEMENT INFO MUST BE OCHCYES OR OCHCNO
Explanation: ochcyes and ochcno are the national characters for 'Y' (yes) and 'N' (no).
System action: The system waits for you to respond.
User response: Enter correct data.
EQQJ024E JOB NAME REPLACEMENT INFO MUST BE OCHCNO OR BLANK FOR RESOURCE EVENT
Explanation: You have specified the event to be a resource event. You cannot replace job name information for
resource events. TME 10 OPC will automatically set this information to N (no) for resource events.
ochcno is the national character for 'N' (no).
System action: None.
User response: None.
EQQJ025E A VALID NAME OF AN ASSOCIATED APPLICATION MUST BE SPECIFIED
Explanation: You must specify the name of a valid application to be added to the current plan when an ETT event
matching this criteria entry occurs.
System action: The system waits for you to respond.
User response: Enter correct data.
EQQJ026E VALID VALUES ARE: OCHCYES, ochcno, ochpred, ochsucc and blank
Explanation: You have entered a value for the dependency resolution attribute that is not recognized by the ETT
dialog. You must change the value to one of the supported values defined by this message.
System action: The system waits for you to respond.
User response: Change the dependency resolution value.
EQQJ027E AVAILABILITY STATUS CHANGE FIELD IS NOT OCHCNO OR BLANK
Explanation: You have defined a triggering event as a reader event but have specified a character other than
ochcno or blank in the availablility switch field. The availability status switch is relevant only when the triggering event
is a resource.
System action: The system waits for you to respond.
User response: Change the availablity switch indicator for the trigger to ochcno or leave the field blank.
EQQJ028E EACH ETT CRITERIA ROW MUST HAVE A UNIQUE EVENT NAME WITHIN TYPE
Explanation: You have specified duplicate event names in the ETT table.
System action: The system waits for you to respond.
User response: Remove the duplicate entry, or make its name unique.
EQQJ029E AVAILABILITY STATUS CHANGE FIELD IS NOT OCHCYES OR OCHCNO
Explanation: You have defined a triggering event as a resource event but have specified a character other than
ochcyes or ochcno in the availablility switch field. The availability status switch must be set when the triggering event
is a resource.
System action: The system waits for you to respond.
User response: If you want the ETT triggered application to be added only when the resource is switched from
unavailable to available specify, Y in the availability switch field. If the application should be added everytime the
resource is set to available, regardless of the old status, set the availability switch to N.
Chapter 13. EQQJnnn Messages
133
EQQJ500E Ÿ EQQJ505E
EQQJ500E INVALID STRING IN DIRECTIVE AT LINE LINE OF SCTN
Explanation: The predicate for any keyword other than COMP must:
Ÿ Consist of alphanumeric characters
Ÿ Begin with an alphabetic character.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the tailoring directive.
EQQJ501E DUPLICATE TABLE NAME TBL AT LINE LINE OF SCTN
Explanation: The same table name was encountered twice in an OPC SEARCH directive.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the tailoring directive.
EQQJ502E CONTRADICTORY USE OF STANDARD TABLES AT LINE LINE OF SCTN
Explanation: An OPC SEARCH directive contains either both GLOBAL and NOGLOBAL, or both APPL and
NOAPPL.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the tailoring directive.
EQQJ503E ERROR ATTEMPTING TO READ JCL MEMBER MBR
Explanation: The member specified in an OPC FETCH directive could not be found. The member name is
incorrect, or the member cannot be accessed.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the tailoring directive, or ensure that the member is available.
EQQJ504E KEYWORD STRING TOO LONG IN OPC DIRECTIVE BEGINNING AT LINE LINE OF SCTN
Explanation: The third and final string in an OPC directive contains more than 1024 characters after substitution,
including continuation lines.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the tailoring directive.
EQQJ505E INVALID KEYWORD COMBINATION IN OPC DIRECTIVE BEGINNING AT LINE LINE OF SCTN
Explanation: An OPC directive has at least one of these problems:
Ÿ Keywords are incompatible with each other.
Ÿ Keywords are incompatible with the type of directive.
Ÿ Mandatory keywords are missing.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the tailoring directive.
134
TME 10 OPC Messages and Codes
EQQJ506E Ÿ EQQJ510E
EQQJ506E RECURSIVE SUBSTITUTION AT LINE LINE OF SCTN
Explanation: The value of a variable depends on the values of other variables, which in turn depend on its value.
No value can be determined for this variable.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Examine the table definitions of the variables in the line, and eliminate the closed translation loop.
EQQJ507E CHANGE OF STRUCTURE CAUSED BY SUBSTITUTION IN DIRECTIVE BEGINNING AT LINE LINE
OF SCTN
Explanation: Variable substitution has caused at least one of these changes:
Ÿ
Ÿ
Ÿ
Ÿ
An OPC directive has been created.
The type of an OPC directive has changed.
The keywords of an OPC directive have changed.
An OPC directive has changed to another line type.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the original tailoring directive or substitution values.
EQQJ508E RECURSIVE SUBSTITUTION OF LENGTH LINES FROM FROM OF SCTN
Explanation: A closed loop of dependency definitions or variable translations exists.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Examine the table definitions of this variables in this section, and eliminate the loop.
If this section contains promptable variables, the values supplied for these variables may have caused the error.
EQQJ509E TABLE TBL NOT FOUND
Explanation: A table declared in a SEARCH or TABLE directive does not exist.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Check the directives to ensure that the table names are correct. Use the variable definition dialog
to ensure that the tables exist.
EQQJ510E UNSET VARIABLE VAR AT LINE LINE OF SCTN
Explanation: A non-dependant variable with no value was encountered in the submit phase, or a JCLPREPA
simulation request.
In the submit phase, or at simulation, these types of variables can be encountered:
Ÿ Variables that have already been provided with values
Ÿ Variables that are dependent on other variables
Ÿ Variables that do not require a setting (which are eliminated from the job stream).
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Either change the variable definition, or give the variable a value.
Chapter 13. EQQJnnn Messages
135
EQQJ511E Ÿ EQQJ516E
EQQJ511E JOB JOBNAME IN APPLICATION APPL CONTAINS AN OPC/ESA CONTROL STATEMENT THAT IS
NOT RECOGNIZED
Explanation: OPC/ESA was unable to submit the job identified because it contains an incorrectly coded //*%OPC
statement and JCL variable scanning is active for this job.
System action: Status for current operation is set to ended-in-error with error code OJCV.
User response: Locate the JCL for this job and correct the //*%OPC statement. Use the OPC/ESA dialog to rerun
the operation.
EQQJ512E RECURSIVE DEPENDENCY VARIABLE VAR AT LINE LINE OF SCTN
Explanation: A closed loop of dependency definitions exists.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Examine the table definitions of this variable and the chain on which it is dependent, and eliminate
the closed dependency loop. The loop does not necessarily include the variable listed in the message.
EQQJ513E SETUP VARIABLE CHLD DEPENDENT ON SUBMIT VARIABLE PRNT AT LINE LINE OF SCTN
Explanation: A prompt variable cannot be dependent on a submit variable.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the table definitions, SEARCH directives, or TABLE directives.
EQQJ514E RETURN CODE RC FROM USER EXIT USRX. THE EXIT WAS DEFINED FOR VARIABLE VAR IN
TABLE TAB FOR APPLICATION ADID, WITH OCCURRENCE INPUT ARRIVAL IAD, IAT. THE
OPERATION NUMBER IS OPNO
Explanation: TME 10 OPC received an unexpected return code from an exit.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the user module and supply a valid return code, and restart TME 10 OPC.
EQQJ515E RECOVERABLE ABEND IN USER EXIT USRX THAT WAS DEFINED FOR VARIABLE VAR IN TABLE
TAB FOR APPLICATION ADID, INPUT ARRIVAL IS IAD, IAT, OPERATION NUMBER IS OPNO
Explanation: The user module caused an abend from which TME 10 OPC recovered.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the user module, and restart TME 10 OPC.
EQQJ516E UNRECOVERABLE ABEND IN USER EXIT USRX THAT WAS DEFINED FOR VARIABLE VAR IN
TABLE TAB, APPLICATION IS ADID, WITH OCCURRENCE INPUT ARRIVAL IAD, IAT, OPERATION
NUMBER IS OPNO
Explanation: The user module caused an abend from which TME 10 OPC could not recover.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the user module, and restart TME 10 OPC.
136
TME 10 OPC Messages and Codes
EQQJ517E Ÿ EQQJ522E
EQQJ517E INVALID VALUE VAL SUPPLIED BY USER EXIT USRX FOR VARIABLE VAR IN TABLE TAB FOR
APPLICATION ADID, OCCURRENCE IA IS IAD, IAT, OPERATION NUMBER IS OPNO
Explanation: The value that the user supplied for the variable violates the verification rules in the variable definition.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the user module or verification criteria. To use the corrected user module, you must restart
TME 10 OPC.
EQQJ518E THE SUBSTITUTION EXIT USRX WAS REFERENCED BY VARIABLE VAR. THE EXIT WILL NOT BE
CALLED AS IT HAS BEEN MARKED NOT EXECUTABLE BY OPC/ESA. APPLICATION IS ADID,
INPUT ARRIVAL IS: IAD, IAT, AND OPERATION NUMBER IS OPNO
Explanation: TME 10 OPC has previously discovered an abend in this exit and marked it as not executable. This
exit will not be called again.
System action: The current operation status is set to ended-in-error, with error code OJCV.
System programmer response: Correct the exit, and restart TME 10 OPC to use the exit again.
EQQJ519E OPC/ESA DID NOT GET STORAGE ENOUGH TO BUILD JCL RECORD APPLICATION IS: ADID,
OPERATION NO IS: OPNO, INPUT ARRIVAL DATE IS: IAD AND INPUT ARRIVAL TIME IS: IAT
Explanation: TME 10 OPC tried to allocate storage for a final build of the JCL record, but the request for storage
failed.
System action: The operation status depends on the SUBFAILACTION keyword in the JTOPTS initialization
statement. The operation can:
Ÿ Keep status R or extended status RE
Ÿ Get status C (complete)
Ÿ Get status E (ended-in-error) with error code OSUF.
System programmer response: Make sure TME 10 OPC is running in a big enough region, and restart TME 10
OPC.
EQQJ520E VALUE LENGTH IS REQUIRED WHEN COMPARISON OPERATOR SPECIFIED
Explanation: Because you entered a comparison operator, you must enter a value length.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ521E COMPARISON OPERATOR REQUIRED WHEN LENGTH OPERATOR SPECIFIED
Explanation: Because you entered a value length, you must enter a comparison operator.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ522E THE DEFAULT VALUE IS INVALID FOR THE VERIFICATION TYPE
Explanation: The default value that you entered does not match the verification rules for the variable.
System action: The system waits for you to respond.
User response: Enter the correct value.
Chapter 13. EQQJnnn Messages
137
EQQJ523E Ÿ EQQJ530E
EQQJ523E A VALIDATION PATTERN IS REQUIRED FOR PICT VERIFICATION
Explanation: Because you asked for PICT verification, you must enter a validation pattern.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ524E Y/N MUST BE ENTERED IN NUMERIC FIELD FOR LIST/RANGE
Explanation: Because you asked for RANGE verification, you must enter Y (yes) or N (no) in the numeric field.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ525E THE JCL VARIABLE TABLE HAS BEEN DELETED
Explanation: The current variable table has been deleted from TME 10 OPC’s database.
System action: The table is deleted.
User response: None.
EQQJ526E CHARACTER CHR IN POSITION PDS IS INVALID
Explanation: The value entered as a default value does not match the validation pattern defined for the variable.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ527E THE VALUES/RANGES MAY NOT CONTAIN IMBEDDED BLANKS
Explanation: You cannot use blanks in a LIST/RANGE verification value list.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ528E THE NUMBER OF VALUES MUST BE EVEN FOR RANGE VERIFICATION
Explanation: You specified an odd number of values for a range verification.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ529E THE VALUES DEFINING A RANGE ARE IN DESCENDING SEQUENCE
Explanation: You entered a range that consists of a larger number followed by a smaller number. You must specify
the smaller number (beginning of the range) before the larger number (end of the range).
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ530E SCANNING LENGTH EXCEEDED LINE LINE OF SCTN
Explanation: Substitution of a JCL command has caused the command length to exceed 71 characters, or
substitution of an in-stream data line has caused the in-stream data line to exceed 80 characters.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
System programmer response: If the substitution is correct, split the command line over two or more lines. If the
problem occurs in an in-stream data line, verify that the ISPF profile option for sequence numbering is turned off in the
JCL job library.
138
TME 10 OPC Messages and Codes
EQQJ531E Ÿ EQQJ535E
EQQJ531E OPC/ESA WAS UNABLE TO LOAD VARIABLE SUBSTITUTION EXIT USRX TABLE NAME IS TAB,
VARIABLE NAME IS VAR, APPLICATION IS ADID, OCCURRENCE IA = IAD, IAT, OPERATION
NUMBER IS OPNO
Explanation: A variable substitution exit that was referred to could not be loaded by TME 10 OPC.
System action: The current operation status is set to ended-in-error, with error code OJCV.
System programmer response: Check the current load library in the started task JCL, and make sure the exit is
link-edited to the correct library.
EQQJ532E INVALID OPC/ESA EXPRESSION BEGINNING EXPR
AT LINE LINE OF SCTN
Explanation: The expression must consist of keyword= where keyword is one of; NAME, ACTION, PHASE,
MEMBER, COMP, EXIT.
This message can also be issued if all compulsory keywords have not been specified.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Correct the JCL.
EQQJ533E OPC/ESA DIRECTIVE DIR OUT OF POSITION LINE LINE OF SCTN
Explanation: There are two possibilities:
Ÿ No previous //*%OPC BEGIN directive corresponds to the current //*%OPC END directive.
Ÿ A //*%OPC BEGIN directive was found previously, but the current directive is not the corresponding //*%OPC END
directive.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the JCL.
EQQJ534E INVALID VARIABLE VAR LINE LINE OF SCTN
Explanation: The name of a variable can contain 1 to 8 alphanumeric characters, where the first character is
alphabetic. This message can also be reported if a tabular variable, that is a ? variable, does not include the
substitution column position and a default position is not defined in the JCL variable table.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the JCL, or the JCL variable table as appropriate.
EQQJ535E UNDEFINED VARIABLE VAR LINE LINE OF SCTN
Explanation: A variable that is not predefined by TME 10 OPC must appear in a table that is created by the JCL
variable dialog and is included in the current table concatenation.
For more information, refer to the description of the SEARCH and TABLE directives in TME 10 OPC Planning and
Scheduling the Workload.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the JCL.
Chapter 13. EQQJnnn Messages
139
EQQJ536E Ÿ EQQJ541E
EQQJ536E POSITIONAL OVERLAP VARIABLE VAR LINE LINE OF SCTN
Explanation: The tabular variable (?-variable) cannot be assigned the positions specified in the prefix or by default
because part or all of the receiving string is already occupied.
For more information, refer to TME 10 OPC Planning and Scheduling the Workload.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the JCL.
EQQJ537E CALENDAR CAL CANNOT BE FOUND. SUBSTITUTION FAILED
Explanation: During variable substitution of a job, a function that requires access to a calendar, such as a SETVAR
directive asking for an expression involving arithmetics on calendar days, could not be processed. The Calendar
referenced by the occurrence no longer exists.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: The calendar may have been deleted by mistake. Delete the SETVAR directive from the JCL, find
out what the Calendar once looked like and insert the needed date manually under JCL Edit.
EQQJ538E BEGIN ACTION NOT CLOSED LINE LINE OF SCTN
Explanation: At the end of the JCL stream, the last //*%OPC BEGIN command has not been closed by a //*%OPC
END command.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the JCL.
EQQJ539E VARIABLE SUBSTITUTION WAS INTERRUPTED BY SUBSTITUTION EXIT USRX. APPLICATION IS
ADID, INPUT ARRIVAL DATE AND TIME IS IAD, IAT OPERATION NUMBER IS OPNO
Explanation: A substitution exit set return code 8, which interrupted the JCL variable substitution. No further
substitution is done for this operation.
System action: The current operation status is set to ended-in-error, with error code OJCV.
System programmer response: Check the current exits and determine the reason for return code 8 being passed
back. If the exit is changed and you want to use it again, restart TME 10 OPC.
EQQJ540E MORE THAN 16 TABLES DECLARED IN SEARCH DIRECTIVE AT LINE LINE OF SCTN
Explanation: The number of tables requested by a SEARCH directive is greater than 16.
Unless GLOBAL and APPL are explicitly excluded (NOGLOBAL and NOAPPL), they contribute to the total even if they
are not specified in the SEARCH directive.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Check if all tables are necessary, then correct the JCL.
EQQJ541E ATTEMPT TO CONCATENATE MORE THAN 16 TABLES BY TABLE DIRECTIVE AT LINE LINE OF
SCTN
Explanation: A TABLE directive has been encountered when 16 tables are already active.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Check if all tables are necessary, then correct the JCL.
140
TME 10 OPC Messages and Codes
EQQJ542E Ÿ EQQJ547E
EQQJ542E COMP EXPRESSION BEGINNING AT LINE LINE OF SCTN EXCEEDS 1024 BYTES
Explanation: The total length of all fields of a COMP expression, including COMP= and all continuations of the right
side of the expression on subsequent JCL lines, cannot exceed 1024 characters after substitution.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Correct the JCL.
EQQJ543E COMP EXPRESSION BEGINNING AT LINE LINE OF SCTN IS NOT WELL FORMED: EXPR
Explanation: The syntax of the COMP keyword is not correct.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: This message is followed by message EQQJ544E, EQQJ545E, EQQJ546E, EQQJ572E,
EQQJ573E, or EQQJ547E, which describes the exact cause of the syntax error.
User response: Correct the OPC directive using the current COMP keyword.
EQQJ544E COMP EXPRESSION CONTAINS UNBALANCED PARENTHESIS
Explanation: Parentheses are not used correctly in the COMP keyword.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: This message is issued together with message EQQJ543E. For an explanation of the
COMP keyword, refer to TME 10 OPC Planning and Scheduling the Workload.
User response: Correct the JCL for the operation and make sure the COMP keyword contains the correct number of
parentheses.
EQQJ545E COMP EXPRESSION MUST CONTAIN AT LEAST ONE OPERATOR
Explanation: The COMP keyword does not contain any operators.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: This message is issued together with message EQQJ543E. For an explanation of the
COMP keyword, refer to TME 10 OPC Planning and Scheduling the Workload.
User response: Correct the JCL for the operation and make sure the COMP keyword contains at least one operator.
EQQJ546E COMP EXPRESSION CONTAINS TOO FEW EQUATION SEPARATING COMMAS
Explanation: At least one comma is missing in the COMP keyword.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: This message is issued together with message EQQJ543E. For an explanation of the
COMP keyword, refer to TME 10 OPC Planning and Scheduling the Workload.
User response: Correct the JCL for the operation and make sure the COMP keyword is correct.
EQQJ547E COMP EXPRESSION CONTAINS TOO FEW OPERATORS
Explanation: At least one operator is missing in the COMP keyword.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: This message is issued together with message EQQJ543E. For an explanation of the
COMP keyword, refer to TME 10 OPC Planning and Scheduling the Workload.
User response: Correct the JCL for the operation and make sure the COMP keyword is correct.
Chapter 13. EQQJnnn Messages
141
EQQJ548W Ÿ EQQJ561E
EQQJ548W VARIABLE VAR IN TABLE TABLE COULD NOT BE UPDATED. REASON IS RSN
Explanation: A SAVEVAR directive with ERRORACT=CONT was found during variable substitution. TME 10 OPC
tries to update the default value as requested in the SETVAR directive, but it was not possible for one of the following
reasons:
HELDLOCK
NOTFOUND
BADVNAME
Could not get ENQ lock necessary to access the variable.
Variable/table did not exist in the table dataset
Variable/table is either an TME 10 OPC-supplied variable or a temporary variable. These variables
are never saved.
System action: Processing continues. The job is submitted as normal but next time the default value is requested
as input to variable substitution, it will not show the latest updated value.
User response: The value can be corrected by allowing a person with update access to the variable table to update
the default value manually in the JCL variable dialog.
EQQJ549E A SETUP PHASE DIRECTIVE AT LINE LINE OF SCTN REFERS TO A VARIABLE DEFINED FOR USE
AT SUBMIT
Explanation: The current job contains a JCL processing directive specifying PHASE=SETUP. TME 10 OPC could
not determine what action is requested by the statement because it refers to a JCL variable whose value will not be
determined until the submit phase.
System action: The system waits for you to respond.
User response: Enter the JCL Edit dialog and correct the incorrect statement. Then reenter the Ready List dialog
and retry JCL setup for this operation.
EQQJ550E Character CHR in position POS is invalid
Explanation: The value entered as a default value does not match the validation pattern defined for the variable.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ551E The value of the independent variable already exists
Explanation: The same value of the independent variable appears on two different rows of the dependency table.
System action: The system waits for you to respond.
User response: Correct or delete the values that you entered.
EQQJ560E MORE THAN 16 VARIABLES SPECIFIED IN SAVEVAR DIRECTIVE AT LINE LINE OF SCTN
Explanation: The number of variables requested to be saved in a SAVEVAR directive is greater than 16.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Split the SAVEVAR directive into multiple directives.
EQQJ561E TEMPORARY VARIABLE NAME VAR ALREADY USED FOR SUBSTITUTION IN JOB JOBNAME
Explanation: A SETVAR directive requests creation of a temporary variable. There has been an earlier reference in
the job to the same name and it has been found in the TME 10 OPC Variable Table.
System action: If the error occurs during submit, the current operation status is set to ended-in-error with error code
OJCV. Otherwise, the status is not changed.
User response: Use another name for your temporary variable.
142
TME 10 OPC Messages and Codes
EQQJ562E Ÿ EQQJ566E
EQQJ562E OPC/ESA WAS UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF DDNAME
Explanation: TME 10 OPC was attempting to build a VSAM dataset record to be inserted in the JCL repository
dataset, but it was unable to do so because of insufficient virtual storage.
System action: The operation remains in ready status. TME 10 OPC is unable to submit the job to JES.
User response: Submit the job manually.
System programmer response: Stop TME 10 OPC and then restart in a larger region.
EQQJ563E OPC/ESA WAS UNABLE TO FIND MEMBER MEMBER IN DDNAME LIBRARY FILE
Explanation: TME 10 OPC was attempting to submit a job to JES for a ready operation on a computer workstation.
However, no JCL for this operation is saved in the JCL repository dataset, and the job is not present as a member in
the library defined by the EQQJBLIB DD statement.
System action: The operation remains in ready status. TME 10 OPC assumes that some other function will submit
the job to JES.
Problem determination: Check that the EQQJBLIB DD statement is correctly defined and that all required members
are defined.
User response: If necessary, submit the job manually.
EQQJ564W MEMBER MEMBER IN DDNAME LIBRARY FILE IS EMPTY
Explanation: The JCL library member exists in the library defined by the EQQJBLIB DD statement but there are no
records in the member.
System action: The operation remains in ready status. TME 10 OPC assumes that some other function will submit
the job to JES.
Problem determination: Check that the EQQJBLIB DD statement is correctly defined and that all required members
are defined.
User response: If necessary, submit the job manually.
EQQJ565E INVALID VARIABLE OR TABLE NAME AT LINE LINE OF SCTN
Explanation: During variable substitution of a job, a SAVEVAR directive specified the name of a variable, or variable
table, with incorrect syntax.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Correct the syntax of the variable or variable table.
EQQJ566E INVALID REFERENCE TO GLOBAL TABLE AT LINE LINE OF SCTN
Explanation: During variable substitution of a job, a SAVEVAR directive was found which specified only the variable
name. The implied table is then the Variable Substitution global table. However, no GTABLE keyword has been
specified in OPCOPTS.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Either add a GTABLE keyword to OPCOPTS and restart the controller, or specify the variable table
in the SAVEVAR statement.
Chapter 13. EQQJnnn Messages
143
EQQJ567E Ÿ EQQJ571E
EQQJ567E THE JCL FOR APPLICATION AD COULD NOT BE INSERTED IN THE JS REPOSITORY PHYSICAL
RECORD SIZE IS TOO SMALL
Explanation: The physical record length specified for the JS repository is too small.
System action: The current operation remains in ready status.
Problem determination: Check the VSAM definitions for EQQJS1DS and EQQJS2DS.
User response: Contact your system programmer.
System programmer response: Increase the physical record length for EQQJS1DS and EQQJS2DS.
EQQJ568E VARIABLE VAR IN TABLE TABLE COULD NOT BE UPDATED.REASON: RSN
Explanation: A SAVEVAR directive with ERRORACT=NOCONT was found during variable substitution. TME 10
OPC tried to update the default value as requested in the SETVAR directive but it was not possible for one of these
reasons:
HELDLOCK
NOTFOUND
BADVNAME
Could not get ENQ lock necessary to access the variable.
Variable/table did not exist in the variable table dataset
Variable/table is either an TME 10 OPC-supplied variable or a temporary variable. These variables
are never saved.
User response: The value can be corrected by allowing a person with update access to the variable table to correct
the default value manually in the variable table dialog.
EQQJ569E INVALID REFERENCE TO DYNAMIC FORMAT VARIABLE AT LINE LINE OF SCTN
Explanation: A reference to a dynamic-format variable has been found and the format of the variable has not been
set in a SETFORM directive.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Insert a SETFORM directive in the JCL earlier than the point where it is referenced.
EQQJ570E INVALID DYNAMIC FORMAT VARIABLE NAME AT LINE LINE OF SCTN
Explanation: During variable substitution of a job, a SETFORM directive was found where the name of the
dynamic-format variable is not an TME 10 OPC-supplied dynamic format variable.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Correct the variable name in the SETFORM directive.
EQQJ571E INVALID FORMAT EXPRESSION IN SETFORM DIRECTIVE AT LINE LINE OF SCTN
Explanation: During variable substitution of a job, a SETFORM directive was found where the format did not have
the proper syntax. Possible errors are:
Ÿ The first characters after the left parenthesis and the last characters before the right parenthesis of the expression
are not meaningful keywords for the specified dynamic format variable. (For example CCYY, YY, MM, DD, or
DDD for a date-related dynamic variable)
Ÿ The whole format expression was searched and no meaningful keywords for the specified dynamic-format variable
were found (For example CCYY, YY, MM, DD, or DDD was not found for a date-related dynamic variable)
Ÿ TME 10 OPC variable substitution characters (&, %, = or ?) are found in the expression.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Correct the format expression in the SETFORM directive.
144
TME 10 OPC Messages and Codes
EQQJ572E Ÿ EQQJ577E
EQQJ572E COMP EXPRESSION CONTAINS MULTIPLE VALUES FOR 'EXPRESSION2'
Explanation: A COMP expression with operators GT, GE, LT, or LE only allows one value for expression2.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Correct the JCL for the operation and make sure the COMP keyword is correct.
EQQJ573E COMP EXPRESSION CONTAINS GENERIC SEARCH CHARACTERS
Explanation: A COMP expression with operators GT, GE, LT, or LE does not allow the generic characters * or % in
expression2.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Correct the JCL for the operation, ensure the COMP keyword is correct.
EQQJ575E ARITHMETIC EXPRESSION BEGINNING AT LINE LINE OF SCTN EXCEEDS LIMITS
Explanation: During variable substitution of a job, the calculation of a SETVAR arithmetic expression resulted in a
date value that exceeds TME 10 OPC limits. TME 10 OPC supports dates from 1 January 1974 to 31 December
2071. If the expression includes WD, the calculated date must fall within the range of three years earlier and six
years later than the current year.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Correct the SETVAR arithmetic expression.
EQQJ576E THE EQQUX002 EXIT COULD NOT OPEN AN INPUT DATA SET TO READ JOB MEMBER. EXIT
MESSAGE IS: UX002MSG
Explanation: The joblib I/O exit was called and gave a return code indicating that it could not open one of its input
datasets.
System action: The job is not submitted by TME 10 OPC as intended. The operation remains in ready status.
Problem determination: Check that all DD statements needed by the EQQUX002 exit have been correctly defined
and that the TME 10 OPC started task has (at least) read access to all referenced datasets.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart TME 10 OPC.
EQQJ577E OPC/ESA COULD NOT ALLOCATE STORAGE TO PROCESS JOB MEMBER FOR EQQUX002 EXIT
Explanation: TME 10 OPC was building a VSAM dataset record to be inserted in the JCL repository dataset but it
was unable to do so because of insufficient virtual storage.
System action: The operation remains in ready status. TME 10 OPC is unable to submit the job to JES.
User response: Submit the job manually.
System programmer response: Stop TME 10 OPC and then restart it in a larger region.
Chapter 13. EQQJnnn Messages
145
EQQJ578E Ÿ EQQJ582E
EQQJ578E THE EQQUX002 EXIT COULD NOT FIND JOB MEMBER IN ANY INPUT DATA SET
Explanation: TME 10 OPC was attempting to submit a job to JES for a ready operation on a computer workstation.
However, no JCL for this operation is saved in the JCL repository dataset, and the joblib I/O exit could not find the job
in any input dataset.
System action: The operation remains in ready status. TME 10 OPC assumes that some other function will submit
the job to JES.
Problem determination: Check that all DD statements needed by the EQQUX002 exit have been correctly defined
and that all required members are defined.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart TME 10 OPC.
EQQJ579W THE EQQUX002 EXIT DID NOT RETURN ANY DATA FOR JOB MEMBER
Explanation: The joblib I/O exit was called to retrieve a job to be submitted, but the exit did not return any data.
System action: The job is not submitted by TME 10 OPC as intended. The operation remains in ready status.
Problem determination: Check that the joblib I/O exit has been correctly installed and that it works properly.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart TME 10 OPC.
EQQJ580E THE EQQUX002 EXIT RETURNED THE FOLLOWING I/O ERROR MESSAGE FOR JOB MEMBER:
UX002MSG
Explanation: The joblib I/O exit was called to retrieve a job to be submitted, but the exit gave a return code
indicating that an I/O error had occurred on an input dataset.
System action: The job is not submitted by TME 10 OPC as intended. The operation remains in ready status.
Problem determination: Check that the joblib I/O exit can access all required input datasets and that it works
properly.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart TME 10 OPC.
EQQJ581E INVALID TEMPORARY VARIABLE NAME AT LINE LINE OF SCTN
Explanation: During variable substitution of a job, a SETVAR directive was found where the name of the temporary
variable is incorrect. The possible errors are:
Ÿ The variable name does not start with a T
Ÿ The rest of the variable name contains one or more non-alphanumeric characters.
System action: If the error occurs during job submit, the current operation status is set to ended-in-error with error
code OJCV. Otherwise, the status is not changed.
User response: Correct the name of the temporary variable.
EQQJ582E JOB MEMBER RETURNED BY THE EQQUX002 EXIT EXCEEDS MAXIMUM SUPPORTED SIZE
Explanation: The joblib I/O exit was called to retrieve a job to be submitted, but the job returned exceeds the
maximum supported size, which is 256KB (kilobytes) of data.
System action: The job is not submitted by TME 10 OPC as intended. The operation remains in ready status.
Problem determination: Check that the joblib I/O exit has been correctly installed and that it works properly.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart TME 10 OPC.
146
TME 10 OPC Messages and Codes
EQQJ583E Ÿ EQQJ586W
EQQJ583E JOB MEMBER IN APPLICATION APPL IS TOO LARGE TO BE SAVED ON THE JS DATA SET
Explanation: A job that is about to be submitted to JES is too large to be saved in the JCL repository dataset.
System action: The job will be submitted but the JCL repository data will not be updated.
Problem determination: Use the IDCAMS LISTCAT function to determine the maximum size of records in the
dataset defined by the EQQJSDS DD statement.
System programmer response: If necessary, allocate a new JCL repository dataset with a larger maximum record
size. Using the IDCAMS REPRO function, copy the old dataset into the new dataset. Then restart TME 10 OPC.
EQQJ584E JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE THE EQQUX001
EXIT RETURNED A SUBMITTING USER ID, USER, WHOSE AUTHORITY COULD NOT BE
DETERMINED
Explanation: The job submit exit was called and returned the name of a TSO user on whose behalf the job submit
should be done. An authority error occurred when trying to build a job submit environment for this user.
System action: The current job will not be submitted. TME 10 OPC processes the next read operation.
Problem determination: Check that the job submit exit, EQQUX001, returns only valid TSO user names to the
caller.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and, if necessary, restart TME 10 OPC.
EQQJ585E INVALID SETVAR ARITHMETIC EXPRESSION AT LINE LINE OF SCTN
Explanation: Invalid syntax in the arithmetic expression of a SETVAR directive was found during JCL variable
substitution.
Here are some possible causes for the error:
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
Ÿ
One or more parentheses missing in the arithmetical expression.
A valid sign (+ or -) is missing.
Both plus and minus signs are present in the expression, but only one sign is allowed.
Invalid variable name.
Invalid number in the expression. The number must be in the range 1–999.
An invalid type in the expression.
Erroneous non-blank characters within parenthesis. Any non-blank within parenthesis must be part of the
arithmetic expression.
System action: If the error occurs during job submission, the current operation status is set to ended-in-error with
error code OJCV. Otherwise, the status is not changed.
User response: Correct the arithmetic expression.
EQQJ586W TEMPORARY VARIABLE VAR IN SETVAR DIRECTIVE NOT REFERRED IN JCL. JOBNAME:
JOBNAME
Explanation: During variable substitution of a job, a SETVAR directive was found and created a temporary variable.
The temporary variable was not referred to anywhere in the JCL.
System action: This is a warning. Operation status is not changed.
User response: Either delete the SETVAR directive, or make sure you have a corresponding reference to the
temporary variable in your JCL.
Chapter 13. EQQJnnn Messages
147
EQQJ587W Ÿ EQQJ598E
EQQJ587W VARIABLE VAR IN SAVEVAR DIRECTIVE NOT REFERRED IN JCL JOBNAME IS: JNM
Explanation: During variable substitution of a job, a SAVEVAR directive was found requesting update of the default
value of a variable. This variable was however not referred to anywhere in the JCL.
System action: This is a warning. Processing continues.
User response: Either delete the variable name from the SAVEVAR directive, or make sure you have a
corresponding reference to the variable in the JCL.
EQQJ588E JOB MEMBER IN APPLICATION APPL IS TOO LARGE TO BE SUBMITTED BY OPC
Explanation: This job exceeds 65 535 records, which is the limit that TME 10 OPC can process.
System action: The job is not submitted. The operation remains in status Arriving or Ready, with extended status
Error during job submission.
User response: Submit the job outside of TME 10 OPC.
EQQJ590E VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQJ591E THE VARIABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQJ592E INVALID VALUE. MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You can enter only Y (for Yes) or N (for No) in this field.
EQQJ594E THE DEFAULT POSITION MUST BE IN THE RANGE 1-80
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The position you have entered is out of the 80-column range for instream data or a JCL line.
| EQQJ595E VALUE LENGTH IS REQUIRED WHEN COMP.OP IS SPECIFIED
| Explanation: Data entry error; see “Data Entry Errors” on page 2.
| Because you entered a comparison operator, you must enter a value length.
| EQQJ596E COMPARISON OPERATOR REQUIRED WHEN LENGTH IS SPECIFIED
| Explanation: Data entry error; see “Data Entry Errors” on page 2.
| Because you entered a value length, you must enter a comparison operator.
| EQQJ597E THE DEFAULT VALUE IS INVALIDATED BY THE VERIFICATION CRITERIA
| Explanation: Data entry error; see “Data Entry Errors” on page 2.
| The default value that you entered does not comply with the verification rules for the variable.
| EQQJ598E VALIDATION PATTERN IS REQUIRED FOR PICT VERIFICATION
| Explanation: Data entry error; see “Data Entry Errors” on page 2.
| Because you asked for PICT verification, you must enter a validation pattern.
148
TME 10 OPC Messages and Codes
EQQJ599E Ÿ EQQJ611E
| EQQJ599E NUMERIC MUST BE SPECIFIED FOR RANGE/LIST VERIFICATION
| Explanation: Data entry error; see “Data Entry Errors” on page 2.
| Because you asked for RANGE or LIST verification, you must set the Numeric field to Yes.
EQQJ604I A DEPENDENCY HAS BEEN MODIFIED
Explanation: The dependency you modified has been inserted into the database.
System action: None.
User response: None.
EQQJ606I A DEPENDENCY HAS BEEN CREATED
Explanation: The dependency you created has been inserted into the database.
System action: None.
User response: None.
EQQJ607I A DEPENDENCY HAS BEEN DELETED
Explanation: The dependency you deleted has been removed from the database.
System action: None.
User response: None.
EQQJ609E YOU ARE NOT AUTHORIZED TO DELETE THIS JCL VARIABLE TABLE
Explanation: You have tried to delete a JCL variable table that you are not authorized to delete.
System action: None.
User response: Contact your system programmer
System programmer response: If the user should have this authorization, update the RACF profiles.
EQQJ610E THE JCL IMBED EXIT USRX RETURNED RETCODE = RC WHILE PROCESSING JOB MEMBER IN
APPLICATION APPL. THIS RETURN CODE IS NOT SUPPORTED, RETCODE = 4 IS ASSUMED
Explanation: A JCL imbed exit that was referenced in a FETCH directive of the current JCL returned an invalid
return code.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: Check the exit and correct possible errors. It you change the exit and want to use it again,
restart TME 10 OPC.
EQQJ611E OPC/ESA COULD NOT ALLOCATE ENOUGH STORAGE TO PROCESS JOB MEMBER IN
APPLICATION APPL FOR THE JCL IMBED EXIT USRX
Explanation: TME 10 OPC was trying to build a JCL record from the data supplied by the exit defined in a FETCH
directive, but it could not do so because of insufficient virtual storage.
System action: The current operation status is set to ended-in-error, with error code OJCV.
System programmer response: Stop TME 10 OPC, and restart it with a larger region.
Chapter 13. EQQJnnn Messages
149
EQQJ612E Ÿ EQQJ617E
EQQJ612E THE JCL IMBED EXIT USRX COULD NOT FIND JOB MEMBER IN ANY INPUT DATA SET
Explanation: The exit gave a return code indicating that the JCL could not be found in the exit’s input datasets.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: Check that all DD statements needed by the exit have been correctly defined.
System programmer response: Correct all errors and then restart TME 10 OPC.
EQQJ613E THE JCL IMBED EXIT USRX DID NOT RETURN ANY DATA FOR JOB MEMBER IN APPLICATION
APPL
Explanation: The exit was called to return JCL to TME 10 OPC, but no data was returned.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: Check that the exit works properly and is correctly installed.
System programmer response: Correct all errors and then restart TME 10 OPC.
EQQJ614E THE AMOUNT OF DATA RETURNED BY THE JCL IMBED EXIT USRX FOR JOB MEMBER IN
APPLICATION APPL EXCEEDS THE MAXIMUM AMOUNT SUPPORTED
Explanation: The exit was called to return JCL to TME 10 OPC, but more than 256KB (kilobytes) of data was
returned.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: Check that the exit is correctly installed, and that it works properly.
System programmer response: Correct all errors and then restart TME 10 OPC.
EQQJ615E THE JCL IMBED EXIT USRX COULD NOT BE LOADED. THE EXIT WILL BE FLAGGED AS NOT
USABLE
Explanation: TME 10 OPC was unable to load the exit. TME 10 OPC will not try to call it again. The exit will be
flagged as not executable.
System action: The current operation status is set to ended-in-error, with error code OJCV.
Problem determination: Check the JCL FETCH directive referring to the exit, and make sure the exit is in the
current load libraries in the started task JCL for TME 10 OPC.
System programmer response: Correct all errors and restart TME 10 OPC.
EQQJ616E THE JCL IMBED EXIT USRX HAS ABENDED WHILE PROCESSING JOB MEMBER IN APPLICATION
APPL. SEE THE SYSUDUMP DATA SET FOR MORE INFORMATION. THE EXIT WILL BE FLAGGED
AS NOT USABLE
Explanation: The exit abended while processing. TME 10 OPC will not try to call it again. The exit will be flagged
as not executable.
System action: The current operation status is set to ended-in-error, with error code OJCV.
System programmer response: Correct all errors in the exit and restart TME 10 OPC.
EQQJ617E JOB MEMBER IN APPLICATION APPL REFERS TO AN UNUSABLE JCL IMBED EXIT, USRX. NO
DATA CAN BE RETRIEVED USING THIS EXIT
Explanation: TME 10 OPC has previously discovered an abend in this exit and marked it as not executable. This
exit will not be called again.
System action: The current operation status is set to ended-in-error, with error code OJCV.
System programmer response: Correct the exit, and restart TME 10 OPC to use the exit again.
150
TME 10 OPC Messages and Codes
EQQJ618E Ÿ EQQJ707I
EQQJ618E OPC/ESA COULD NOT ALLOCATE STORAGE ENOUGH FOR RECORD READ FROM JS DATA SET.
APPLICATION IS: APPL, JOBNAME IS MEMBER
Explanation: TME 10 OPC tried to allocate storage for a record read from the JS dataset, but the request for
storage failed.
System action: The operation status depends on the SUBFAILACTION keyword in the JTOPTS initialization
statement. The operation can:
Ÿ Keep status R or extended status RE
Ÿ Get status C (complete)
Ÿ Get status E (ended-in-error) with error code OSUF.
System programmer response: Make sure TME 10 OPC is running in a big enough region, and restart TME 10
OPC.
EQQJ702E THE JCL VARIABLE TABLE HAS BEEN DELETED
Explanation: The JCL variable table has been removed from the TME 10 OPC database.
System action: The variable table is deleted.
User response: None.
EQQJ703E THE JCL VARIABLE TABLE IS BEING UPDATED BY ANOTHER USER
Explanation: You cannot access the variable table because it is being updated by another user.
System action: The system waits for you to respond.
User response: Try again later.
EQQJ704E THE JCL VARIABLE TABLE TID ALREADY EXISTS
Explanation: You have tried to create a table that already exists.
System action: The system waits for you to respond.
User response: Enter correct data and try again.
EQQJ705I THE JCL VARIABLE TABLE HAS BEEN REPLACED IN THE DATA BASE
Explanation: The JCL variable table has been modified and successfully updated in the database.
System action: The system waits for you to respond.
User response: None.
EQQJ706E JCL VARIABLE TABLE ENTRY COULD NOT BE RETRIEVED
Explanation: You have tried to access a JCL variable table that has been deleted since the variable table list was
displayed.
System action: The system waits for you to respond.
User response: Check if another user has already deleted the table.
EQQJ707I A JCL VARIABLE DEFINITION HAS BEEN CREATED
Explanation: A JCL variable definition has been created and inserted in the database.
System action: None.
User response: None.
Chapter 13. EQQJnnn Messages
151
EQQJ708I Ÿ EQQJ801E
EQQJ708I THE JCL VARIABLE TABLE HAS BEEN REPLACED IN THE DATA BASE
Explanation: The JCL variable table has been modified and successfully replaced in the database.
User response: None.
System action: None.
EQQJ712E THE VARIABLE TO BE DELETED HAS DEPENDENCIES
Explanation: Another variable is dependent on this variable.
System action: None.
User response: To delete this variable, first remove the dependency. You can re-assign the dependency, delete the
dependency, or delete the dependent variable.
EQQJ713E THE NUMBER OF VALUES MUST BE EVEN FOR RANGE TYPE
Explanation: You specified an odd number of values for a range verification.
System action: The system waits for you to respond.
User response: Correct the error and try again.
EQQJ714E THE LIST OF VALUES CONTAINS A BAD VALUE PAIR
Explanation: One of the pairs of values that you specified is in error.
System action: The system waits for you to respond.
User response: Correct the error and try again.
EQQJ715E THE CHARACTER CHR IN POSITION POS IS INVALID
Explanation: The value that you entered contains a non-numeric character.
System action: The system waits for you to respond.
User response: Correct the error and try again.
EQQJ716E ONE VALID VALUE CANNOT EXCEED 44 POSITIONS
Explanation: You defined as valid a value that contains more than 44 characters. This is not allowed.
System action: The system waits for you to respond.
User response: Correct the error and try again.
EQQJ717E THE DEPENDENT VARIABLE VALUE IS INVALID FOR THE VERIFICATION TYPE
Explanation: The dependent value that you entered does not match the verification rules for the dependent variable.
System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ800E INVALID VALUE. MUST BE Y, N OR P
Explanation: Data entry error; see “Data Entry Errors” on page 2.
In this field, you can enter only Y (for Yes), N (for No), or P (for Prompt).
EQQJ801E VALUES/RANGE MUST BE SPECIFIED FOR RANGE/LIST
Explanation: You specified verification type RANGE or LIST, but did not specify any values.
System action: The system waits for you to respond.
User response: Correct the error and try again.
152
TME 10 OPC Messages and Codes
EQQJ802E Ÿ EQQJ813E
EQQJ802E NUMERIC CAN ONLY BE SPECIFIED FOR RANGE/LIST VERIFICATION
Explanation: You specified a valid numeric field type, but did not specify RANGE or LIST verification.
System action: The system waits for you to respond.
User response: Correct the error and try again.
EQQJ805E INVALID VERIFICATION TYPE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid types are ALPHA, NUM, ENUM, HEX, BIT, PICT, NAME, DSNAME, RANGE and LIST.
EQQJ806E INVALID VALUE LENGTH
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The length must be in the range 1 to 44.
EQQJ807E INVALID COMPARISON OPERATOR
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid operators are:
EQ
=
LT
<
GT
>
LE
<=
GE
>=
NE
¬=
NG
¬>
NL
¬<
EQQJ808I THERE ARE NO DEPENDENCIES DEFINED FOR THIS VARIABLE
Explanation: There are no dependencies defined for this variable.
System action: None.
User response: None.
EQQJ809E THE INDEPENDENT VALUE DOES ALREADY EXIST
Explanation: You specified a duplicate value for the independent variable.
System action: The system waits for you to respond.
User response: Correct the error and try again.
EQQJ810I THERE ARE NO VERIFICATION CRITERIA DEFINED FOR THIS VARIABLE
Explanation: There are no verification criteria defined for this variable.
System action: None.
User response: None.
EQQJ811E THE VARIABLE ALREADY EXISTS IN THE CURRENT VARIABLE TABLE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You have defined a variable that already exists in this table.
EQQJ812E VARIABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQJ813E TABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 13. EQQJnnn Messages
153
EQQJ814E Ÿ EQQJ819E
EQQJ814E OWNER ID IS MISSING
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQJ815E SUBSTITUTION EXIT NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQJ816E THE MAXIMUM NUMBER OF DEPENDENCIES IS 360
Explanation: You tried to define more than 360 dependencies.
System action: The system waits for you to respond.
User response: Type over the incorrect value, and press Enter.
EQQJ817E THE INDEPENDENT VARIABLE NAME IS REQUIRED
Explanation: You tried to enter a value for an independent variable without specifying an independent variable
name.
System action: The system waits for you to respond.
User response: Correct the error and try again.
EQQJ818E THE VERIFICATION LENGTH DIFFERS FROM THE LENGTH OF VALID VALUES
Explanation: You have specified a verification length that is shorter than one of the values listed in the valid
VALUES or RANGES.
User response: Correct the length or values, and try again.
System action: The panel is redisplayed with the cursor pointing at the field that is in error.
EQQJ819E VALUE OF DEPENDENT IS TOO LONG
Explanation: The value in the value-of-dependent field is longer than the value length specified on the panel
'Specifying Verification Criteria'.
User response: Either change the value-of-dependent field, or the value length of the dependent variable.
System action: The panel is redisplayed with the cursor pointing at the field that is in error.
154
TME 10 OPC Messages and Codes
EQQK000E Ÿ EQQK022E
Chapter 14. EQQKnnn Messages
EQQK000E VALID-TO SPECIFICATION PRECEDES VALID-FROM SPECIFICATION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The valid-to date must be later than the valid-from date.
EQQK001E OI ALREADY EXISTS IN OI DATA BASE
Explanation: You have attempted to create an OI that already exists in the OI database.
System action: The system waits for you to respond.
User response: Exit and then use the modify function instead of the create function.
EQQK002E VALIDITY PERIODS OF TEMPORARY OIS MUST NOT OVERLAP
Explanation: There is an existing OI whose validity period overlaps with this temporary OI. The validity period of a
temporary OI is defined by a valid-from and valid-to specification. The validity periods of temporary OIs must not
overlap each other.
System action: The system waits for you to respond.
User response: Respecify valid-from and valid-to period limits.
| EQQK003E OPERATOR INSTRUCTION NOT FOUND IN OI DATA BASE. REFRESH YOUR LIST
Explanation: You have attempted to browse, modify, or delete an OI that no longer exists in the OI database. Most
likely, the OI has been deleted by another user after your list of OIs was created.
System action: The system waits for you to respond.
User response: Return to the selection panel, have a fresh list of OIs created, and continue your work.
EQQK004W OPERATOR INSTRUCTION IS IN USE, TRY LATER
Explanation: Another user is currently updating the same OI.
System action: The system waits for you to respond.
User response: Try again later.
EQQK007E YOU ARE NOT AUTHORIZED TO ACCESS THE OI DATA BASE
Explanation: You have attempted to access the OI database, but you are not authorized to access it.
System action: The system waits for you to respond.
User response: Contact your security administrator.
EQQK008E YOU ARE NOT AUTHORIZED TO UPDATE THE OI DATA BASE
Explanation: You have attempted to update the OI database, but you are not authorized to update it.
System action: The system waits for you to respond.
User response: Contact your security administrator.
EQQK021E BOTH DATE AND TIME MUST BE SPECIFIED, OR BOTH BLANK
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQK022E THE INPUT FIELD MUST BE ALL NUMERIC, OR BLANK
Explanation: Data entry error; see “Data Entry Errors” on page 2.
 Copyright IBM Corp. 1991, 1998
155
EQQK023W Ÿ EQQK031E
EQQK023W THE OPERATOR INSTRUCTION CONTAINS NO TEXT
Explanation: The OI you selected does not contain any text.
System action: The system waits for you to respond.
User response: If this OI should contain text, use the OI dialog to add the desired text.
| EQQK024W IT IS NOT POSSIBLE TO SAVE AN OPERATOR INSTRUCTION WITHOUT TEXT
| Explanation: An operator instruction must have at least one line of text.
| System action: The system waits for you to respond.
| User response: Make sure that there is at least one line of text, or issue the CANCEL command to terminate the
| CREATE, COPY, or MODIFY request.
EQQK025I THE OI WAS MODIFIED IN THE OI DATA BASE
Explanation: The OI record was modified and the OI database was updated.
System action: None.
User response: None.
EQQK026E INVALID PARAMETERS PASSED TO THE MODULE
Explanation: The parameters passed to the module from the ISPF panels were invalid. This is an internal TME 10
OPC error.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Contact your IBM representative.
EQQK027I THE OI WAS ADDED TO THE OI DATA BASE
Explanation: The OI record was added to the operator instruction database.
System action: None.
User response: None.
EQQK028I THE OI WAS NOT MODIFIED IN THE OI DATA BASE
| Explanation: The OI record in the OI database was not updated, either because you cancelled your modify request
| or because no lines existed in the OI record you attempted to store.
System action: None.
User response: None.
EQQK030I THE OI WAS NOT ADDED TO THE OI DATA BASE
Explanation: No OI record was added to the OI database either because you cancelled your create request, or no
lines existed in the OI record you attempted to add.
System action: None.
User response: None.
EQQK031E APPLICATION IDENTIFICATION MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
156
TME 10 OPC Messages and Codes
EQQK032E Ÿ EQQK043E
EQQK032E THE NAME DOES NOT START WITH AN ALPHABETIC CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
| EQQK033E THE OPERATION NUMBER MUST BE IN THE RANGE 1 - 255
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQK034E THE NAME CONTAINS INVALID CHARACTER(S)
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A name can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that is,
#, $, and @).
EQQK035E BOTH VALID-FROM AND VALID-TO REQUIRED FOR TEMPORARY OIS
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Both a valid-from date and a valid-to date are required when creating temporary OIs.
| EQQK036E THE OPERATION NUMBER CONTAINS A NON-NUMERIC CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The operation number must be numeric.
EQQK037E THE OPERATION NUMBER MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQK038E TIME MISSING IN VALID-FROM OR VALID-TO SPECIFICATION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Both date and time are required when specifying a valid-from or a valid-to date.
EQQK039E DATE MISSING IN VALID-FROM OR VALID-TO SPECIFICATION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Both date and time are required when specifying a valid-from or a valid-to date.
EQQK040I OI WAS DELETED FROM OI DATA BASE - REQUEST CONFIRMED
Explanation: The operator instruction you selected was deleted from the operator instruction database, as specified.
System action: None.
User response: None.
EQQK041I OI NOT DELETED FROM OI DATA BASE - REQUEST NOT CONFIRMED
Explanation: The operator instruction you selected was not deleted from the operator instruction database. The
initial request was not confirmed.
System action: None.
User response: None.
EQQK043E THE WORK STATION NAME MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 14. EQQKnnn Messages
157
EQQK044I Ÿ EQQK456E
EQQK044I NO OPERATOR INSTRUCTION MATCHED YOUR SELECTION CRITERIA
Explanation: No OIs matched the selection criteria you specified.
System action: None.
User response: None.
EQQK050E A REMOVAL DATE FOR PURGING OLD TEMPORARY OIS MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQK051I PRESS ENTER TO CREATE REMOVAL JCL, OR END TO CANCEL
Explanation: You have requested to create JCL for a job to remove operator instructions. You must press ENTER
to generate the JCL, or enter the END command to cancel your request.
System action: The system waits for you to respond.
User response: Press ENTER or the End PF-key (or enter the END command).
EQQK052E A VALID DATA SET NAME MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQK053E REPLY MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQK054I PRESS ENTER TO CREATE UPDATE JCL, OR END TO CANCEL REQUEST
Explanation: You have requested to create JCL for a job to mass update OIs. You must press ENTER to generate
the JCL, or enter the END command to cancel your request.
System action: The system waits for you to respond.
User response: Press ENTER or the End PF-key (or enter the END command).
EQQK450E THE APPLICATION DESCRIPTION AD DOES NOT EXIST
Explanation: When attempting to create or modify an OI, the OI data is checked for validity. A check is made for
the corresponding operation. The validation failed because the application description AD does not exist.
System action: The system waits for you to respond.
User response: Correct the application ID and save the OI.
EQQK455E APPLICATION DESCRIPTION AD HAS NO WORK STATION WS
Explanation: When attempting to create or modify an OI, the OI data is checked for validity. A check is made for
the corresponding operation. The validation failed because the application description AD has no workstation WS.
System action: The system waits for you to respond.
User response: Correct the workstation name and save the OI.
EQQK456E APPLICATION DESCRIPTION AD HAS NO OPERATION OP
Explanation: When attempting to create or modify an OI, the OI data is checked for validity. A check is made for
the corresponding operation. The validation failed because the application description AD has no operation OP.
System action: The system waits for you to respond.
User response: Correct the operation number and save the OI.
158
TME 10 OPC Messages and Codes
EQQK457E Ÿ EQQK457E
EQQK457E APPLICATION DESCRIPTION AD HAS NO OPERATION WS OP
Explanation: When attempting to create or modify an OI, the OI data is checked for validity. A check is made for
the corresponding operation. The validation failed because the application description AD has no operation WS OP.
System action: The system waits for you to respond.
User response: Correct the operation number and save the OI.
Chapter 14. EQQKnnn Messages
159
160
TME 10 OPC Messages and Codes
EQQL000E Ÿ EQQL006I
Chapter 15. EQQLnnn Messages
EQQL000E YOU ARE NOT AUTHORIZED TO ACCESS THE LTP DATA SET
Explanation: You have attempted to access the LTP dataset but you are not authorized to do so. Or, you do not
have access authority to at least one of the following TME 10 OPC resources that are used together with the LTP
dataset: the application description database, the calendar database, or the workstation description database.
System action: The system waits for you to respond.
User response: Contact your security administrator if you require access to the LTP dataset or to any of the related
resources given above.
EQQL001E YOU ARE NOT AUTHORIZED TO UPDATE THE LTP DATA SET
Explanation: You have attempted to access the LTP dataset for update but you are not authorized to do so. Or,
you do not have access authority to at least one of the following TME 10 OPC resources that are used together with
the LTP dataset: the application description database, the calendar database, or the workstation description database.
System action: The system waits for you to respond.
User response: Contact your security administrator if you require access to the LTP dataset or to any of the related
resources given above.
EQQL002I OCCURRENCE IS UPDATED
Explanation: The LTP record for the occurrence has been updated.
System action: None.
User response: None.
EQQL003I THE OCCURRENCE IS NOT UPDATED
Explanation: The LTP record for the occurrence was not updated because you cancelled your modify request.
System action: None.
User response: None.
EQQL004I THE OCCURRENCE IS NOT UPDATED
Explanation: The LTP record for the occurrence was not updated because its content was not changed.
System action: None.
User response: None.
EQQL005E LONG-TERM PLAN IS BEING UPDATED BY SOMEONE ELSE
Explanation: You have attempted to update the LTP dataset but it is being updated by another user. The LTP
dataset can only be updated by one user at a time.
System action: The system waits for you to respond.
User response: Try again later.
EQQL006I THE OCCURRENCE IS DELETED
Explanation: The LTP record for the occurrence has been deleted from the LTP plan dataset.
System action: None.
User response: None.
 Copyright IBM Corp. 1991, 1998
161
EQQL007I Ÿ EQQL018E
EQQL007I THE OCCURRENCE IS CREATED
Explanation: A LTP record for the occurrence has been added to the LTP dataset.
System action: None.
User response: None.
EQQL008E THE DEPENDENCY IS ALREADY DELETED
Explanation: You have tried to delete a dependency that has already been deleted.
System action: Request rejected.
User response: None.
EQQL010E EITHER AN END DATE OR AN EXTENSION LENGTH MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL011E THE END DATE MUST BE LATER THAN THE CURRENT END DATE
Explanation: The end date specified must be later than the current end date.
System action: The system waits for you to respond.
User response: Display the status of the LTP to view the current end date, and then reenter a valid end date.
EQQL012E AN APPLICATION ID MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL013E START AND END OF PRINT MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL014E REPORT TYPE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL015E SORT ORDER MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL016E REPORT TYPE SPECIFIED IS NOT VALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid report types are F for full report, and D for dependencies only.
EQQL017E SORT ORDER SPECIFIED IS NOT VALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid sort orders are I for input arrival date, O for owner ID, and A for application ID.
EQQL018E PRINT END DATE MUST BE LATER THAN PRINT START DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
162
TME 10 OPC Messages and Codes
EQQL019E Ÿ EQQL102I
EQQL019E THE PRINT INTERVAL MUST BE WITHIN THE RANGE OF THE LTP
Explanation: You have specified a print end date or print start date that is outside the range of the LTP start and
end.
System action: The system waits for you to respond.
User response: Check the displayed LTP start and end dates, and then reenter a valid print interval.
EQQL020E THE LTP CANNOT BE LONGER THAN FOUR YEARS
Explanation: The LTP cannot be more than four years in length, starting from the date of the first uncompleted
occurrence.
System action: The system waits for you to respond.
User response: Enter a valid end date.
EQQL022E THE EXTENSION LENGTH SHOULD BE A NUMERIC VALUE FROM 0001 TO 1461
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL023E EXTENSION LENGTH AND START DATE CANNOT BE ENTERED TOGETHER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL024E EITHER AN END DATE OR AN EXTENSION LENGTH MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL025E IF YOU SPECIFY A START DATE YOU MUST ALSO SPECIFY AN END DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL026E THE END DATE MUST BE LATER THAN THE CURRENT DATE
Explanation: The end date for a Long Term Plan Create must be later than the current date.
System action: The request is rejected.
User response: Correct the LTP end date and retry.
EQQL100E THE SPECIFIED DEPENDENCY TYPE MUST BE P OR S
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The dependency type P stands for predecessor; S stands for successor.
EQQL101W THE LTP DATA SET IS EMPTY - ONLY LTP CREATE ALLOWED
Explanation: You have attempted to extend the LTP but there is no LTP.
System action: The system returns you to the SELECTING LONG TERM PLAN BACKGROUND JOB menu so you
can select another function.
User response: Select option 7 to create the LTP.
EQQL102I NO LISTITEM DEFINED FOR THIS OCCURRENCE
Explanation: No items matched the selection criteria you specified for listitem.
System action: None.
User response: None.
Chapter 15. EQQLnnn Messages
163
EQQL310E Ÿ EQQL464E
EQQL310E THE LTP DATA SET IS EMPTY - NO HEADER FOUND
Explanation: You have attempted to do one of the following:
Ÿ Submit an LTP batch job, but there is no header record in the LTP dataset
Ÿ Make a trial plan, but no LTP exists.
System action: The system waits for you to respond.
User response: Select the background job that creates a new LTP, and then try again.
EQQL311E AN APPLICATION ID IS REQUIRED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL312E AN INPUT ARRIVAL DATE IS REQUIRED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL313E AN INPUT ARRIVAL TIME IS REQUIRED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL314E A DEADLINE DATE IS REQUIRED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL315E A DEADLINE TIME IS REQUIRED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL316E A CURRENT PLAN EXISTS
Explanation: You have attempted to create a LTP without first refreshing the LTP. Occurrences in the LTP have
been selected by daily planning and might have been included in the current plan.
System action: The system waits for you to respond.
User response: Either select LTP EXTEND, or perform a REFRESH from the service dialog and request the LTP
CREATE again.
EQQL317E A START DATE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL318E THE END DATE MUST BE LATER THAN THE START DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL319E VALID REPLY IS Y, N, OR BLANK
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL464E NO COMPUTER OPERATION(S) FOUND IN APPLICATION
Explanation: Job setup cannot be done because the application does not contain any computer operations.
System action: The system waits for you to respond.
User response: Add a computer operation to the application, and then try again.
164
TME 10 OPC Messages and Codes
EQQL465E Ÿ EQQL472E
EQQL465E DEPENDENCY LTPDERR NOT FOUND
Explanation: The specified dependency (ltpderr) could not be found in the LTP dataset.
System action: The system waits for you to respond.
User response: Check that the specified dependency is correctly defined.
EQQL466E OCCURRENCE HAS SUCCESSOR IN CURRENT PLAN, CANNOT BE MOVED
Explanation: The run date and run time of the occurrence cannot be changed, because the occurrence has a
successor that is part of the current plan.
System action: The system waits for you to respond.
User response: Check that the dependency for the occurrence is correct and that you have correctly specified the
occurrence.
EQQL467E LTPDERR IS ALREADY IN CURRENT PLAN
Explanation: You have attempted to add a dependency for an occurrence that is already part of the current plan.
System action: The system waits for you to respond.
User response: Enter a valid dependency.
EQQL468E LTPDERR CANNOT HAVE A DEPENDENCY ON ITSELF
Explanation: You specified a dependency for an occurrence, but the dependency is on the occurrence itself. This is
not valid.
System action: The system waits for you to respond.
User response: Enter a valid dependency.
EQQL469E DEPENDENCY ON LTPDERR ALREADY SPECIFIED
Explanation: The dependency you specified already exists for this occurrence.
System action: The system waits for you to respond.
User response: Enter a valid dependency.
EQQL471E LTPDERR CANNOT HAVE MORE SUCCESSORS
Explanation: You have specified too many successors for this predecessor operation. The maximum number of
dependencies possible depends on the maximum record size in the LTP VSAM file. If the default maximum record
size is used, the maximum number of dependencies (predecessors and successors) is 3574.
System action: The system waits for you to respond.
User response: Review the dependencies for this predecessor.
EQQL472E LTPDERR CANNOT HAVE MORE PREDECESSORS
Explanation: You have specified too many predecessors for this successor operation. The maximum number of
dependencies possible depends on the maximum record size in the LTP VSAM file. If the default maximum record
size is used, the maximum number of dependencies (predecessors and successors) is 3574.
System action: The system waits for you to respond.
User response: Review the dependencies for this successor.
Chapter 15. EQQLnnn Messages
165
EQQL473E Ÿ EQQL499E
EQQL473E MORE DEPENDENCIES DEFINED FOR LTPDERR THAN WILL FIT IN ONE RECORD
Explanation: You have defined too many dependencies for the current LTP occurrence. The maximum number of
dependencies possible depends on the maximum record size in the LTP VSAM file. If the default maximum record
size is used, the maximum number of dependencies is 3574.
System action: The LTP dialog waits for you to respond.
User response: Enter the primary command CANCEL to return to the calling panel or enter the DELETE row
command for one or more unnecessary dependencies.
EQQL474E MORE OPERATIONS CHANGED FOR LTPDERR THAN WILL FIT IN ONE LTP RECORD
Explanation: You have updated too many operations in the current LTP occurrence. The maximum number of
changed operations depends on the maximum record size in the LTP VSAM file and on the number of external
dependencies for the current occurrence.
System action: The LTP dialog waits for you to respond.
User response: Enter the primary command CANCEL to return to the calling panel.
EQQL480E INPUT ARRIVAL TIME: T24. RESPECIFY T00 ON THE FOLLOWING DAY
Explanation: T24 is not a valid input arrival time.
System action: The system waits for you to respond.
User response: Respecify the input arrival time as suggested (T00).
EQQL481E DEADLINE TIME: T00. RESPECIFY T24 ON THE PREVIOUS DAY
Explanation: T00 is not a valid deadline time.
System action: The system waits for you to respond.
User response: Respecify the deadline time as suggested (T24).
EQQL482E PRIORITY MUST BE A NUMBER FROM 1 - 9
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL487E RUN DATE IS EARLIER THAN THE LTP START DATE LTPSDAY
Explanation: The run date you specified is earlier than the LTP start date LTPSDAY. This is not allowed.
System action: The system waits for you to respond.
User response: Enter a valid run date.
EQQL489E NO OCCURRENCE MATCHES THE SEARCH CRITERIA
Explanation: No dependent occurrence matched the search criteria you specified to generate a list of occurrences.
System action: The system waits for you to respond.
User response: Respecify your selection criteria.
EQQL498E W._O IS FIRST OPERATION, INPUT ARRIVAL MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The first operation (w._o) in an occurrence must have an input arrival time specified.
EQQL499E W._O IS THE LAST OPERATION, A DEADLINE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The last operation (w._o) in an occurrence must have a deadline specified.
166
TME 10 OPC Messages and Codes
EQQL504E Ÿ EQQL512E
EQQL504E APPLICATION DEPAID NOT FOUND
Explanation: The application (DEPAID) specified in the LTP occurrence was not found in the application description
database. The application might have been deleted from the application description database or the user does not
have access to read the application description for the dependent application.
System action: The system waits for you to respond.
User response: Check why the application description cannot be found. If it has been inadvertently deleted, it
should be reentered.
EQQL505E APPLICATION APPL NOT FOUND
Explanation: The application (APPL) specified in the LTP occurrence was not found in the application description
database.
These are possible explanations:
Ÿ The application description has been deleted from the application description database, but the corresponding
occurrences in the LTP dataset have not.
Ÿ You do not have read access to the application description for this application.
Ÿ The application was not active at the input arrival time of the LTP occurrence.
System action: The system waits for you to respond.
User response: Check why the application description cannot be found. If it has been inadvertently deleted, it
should be reentered.
EQQL506E DEPENDENT APPLICATION IS NOT AVAILABLE IN AD DATA SET
Explanation: This occurrence has at least one external dependency that is not available to the user. The dependent
application might have been deleted from the application description database or the user does not have access to
read the application description for the dependent application.
System action: The system waits for you to respond.
User response: Check why the application description cannot be found. If it has been inadvertently deleted, it
should be reentered. Operations with no workstation name and operation number 000 should be checked.
EQQL507E RUN DATE SPECIFIED IS LATER THAN THE LTP END LTPEDAY
Explanation: The run date you specified is later than the LTP end date.
System action: The system waits for you to respond.
User response: Enter a run date within the range of the LTP.
EQQL509E THE SPECIFIED OCCURRENCE ALREADY EXISTS
Explanation: The occurrence you specified already exists.
System action: The system waits for you to respond.
User response: Change data to make a new entry, or exit.
EQQL510E DEADLINE IS EARLIER THAN (OR EQUAL TO) THE INPUT ARRIVAL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The deadline date must be later than the input arrival date.
EQQL512E THE VARIABLE TABLE IS NOT DEFINED TO OPC/ESA
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You have tried to define a variable table ID that does not exist in TME 10 OPC's database.
Chapter 15. EQQLnnn Messages
167
EQQL513E Ÿ EQQL567I
EQQL513E THE VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL514E YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE
Explanation: You have attempted to refer to a JCL variable table. To do this, you need read authority to the JCL
variable table database.
System action: The system waits for you to respond.
User response: Contact your security administrator if you need to refer to JCL variable table names.
EQQL530E I/O-ERROR READING CALENDAR. DEFAULT DAY STATUS USED
Explanation: An I/O error occurred when reading the calendar database. The default day status is used.
System action: The system waits for you to respond.
User response: Enter correct data if the default should not be used.
EQQL540E OCCURRENCE IN A GROUP MUST BE REMOVED BEFORE IT CAN BE DELETED
Explanation: An occurrence that belongs to an occurrence group cannot be deleted.
System action: The system waits for you to respond.
User response: You must remove the occurrence from the group before you can delete it. You can do this from the
LONG TERM PLAN OCCURRENCES panel by typing the row command RG, or from the MODIFYING OCCURRENCE DATA
panel by erasing the group definition ID field.
EQQL541W THE APPLICATION IS A MEMBER OF A GROUP. CONSIDER ADDING THE OTHER MEMBERS
Explanation: The application is a member of an application group. This message is issued as a reminder in case
you should also add the other members of the same group to the long-term plan.
System action: Normal processing continues.
User response: If applicable, create occurrences in the long-term plan for the other applications in the same group.
EQQL542E OCCURRENCE IS NOT A MEMBER OF AN OCCURRENCE GROUP
Explanation: The occurrence does not belong to an occurrence group.
System action: The request is rejected.
User response: None.
EQQL566E INPUT ARRIVAL TIME SPECIFIED PRECEDES THE CP END LTPPNEND, LTPPNENT
Explanation: You can not modify, delete, or add an occurrence to the LTP which has an input arrival time within the
range of the current plan.
System action: The request is rejected.
User response: Make sure that input arrival is correctly specified. If it is and you still want to process the
occurrence, use the Modify Current Plan dialog instead.
If you need to delete a dependency to an occurrence in the current plan, use the Modify Current Plan dialog to delete
the predecessor specification.
EQQL567I LTPCHIAD, LTPCHIAT INPUT ARRIVAL OUTSIDE OCCURRENCE TIME LIMIT
Explanation: The operation input arrival date and time LTPCHIAD, LTPCHIAT is outside the occurrence time limit.
System action: None.
User response: None.
168
TME 10 OPC Messages and Codes
EQQL568I Ÿ EQQL706E
EQQL568I LTPCHDD, LTPCHDT DEADLINE PAST OCCURRENCE TIME LIMIT
Explanation: The operation deadline LTPCHDD, LTPCHDT is outside the occurrence time limit.
System action: None.
User response: None.
EQQL570I THE INPUT ARRIVAL SPECIFIED IS LATER THAN THE DEADLINE
Explanation: The operation input arrival date and time are later than the application deadline.
System action: The system waits for you to respond.
User response: Change the input arrival date and time if they are not what you intended.
EQQL572E DATE OR TIME IS MISSING FROM THE INPUT ARRIVAL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL573E DATE OR TIME IS MISSING FROM THE DEADLINE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQL701E INVALID DATA LENGTH IN LONG TERM PLAN REQUEST: L
Explanation: An internal parameter list, consisting of a sequence of control blocks followed by an application
description record, was validated and found to have an invalid length.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file of the TME 10 OPC subsystem (ddname EQQDUMP) contains a dump
of the control blocks.
User response: This is likely to be an internal error. If possible, do the requests in a different order and rerun.
System programmer response: If you cannot find a valid reason for the error, make the diagnostic file and the
message log available and contact your IBM representative.
EQQL705E THE APPLICATION DESCRIPTION AD COULD NOT BE FOUND REQUESTED AS PREDECESSOR
TO LTP OCCURRENCE LTOC
Explanation: The application AD is specified in a program interface request to set up a dependency between two
long-term plan occurrences. Its application description could not be found.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
User response: Correct the application ID and resubmit the job.
EQQL706E PREDECESSOR OPERATION WSN OPNO DOES NOT EXIST IN AD AD REQUESTED AS
PREDECESSOR TO LTP OCCURRENCE LTOC
Explanation: The operation WSN OPNO is specified in a program interface request to set up a dependency between
two long-term plan occurrences. The specified application description does not contain the operation.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
User response: Correct the application ID, workstation name, or operation number and resubmit the job.
Chapter 15. EQQLnnn Messages
169
170
TME 10 OPC Messages and Codes
EQQM000E Ÿ EQQM011I
Chapter 16. EQQMnnn Messages
EQQM000E YOU DO NOT HAVE AUTHORITY TO ACCESS THE CURRENT PLAN
Explanation: To use the function you selected, you must have access authority to the current plan.
System action: The request is rejected and the system waits for you to respond.
User response: Contact your security administrator if you require access to the current plan.
EQQM001E YOU DO NOT HAVE AUTHORITY TO UPDATE THE CURRENT PLAN
Explanation: To use the function you selected, you must have update authority to the current plan.
System action: The request is rejected and the system waits for you to respond.
User response: Contact your security administrator if you need to update the current plan.
EQQM004E PRIORITY MUST BE A NUMBER FROM 1 - 9
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM005E THE MCP ADDED OPTION MUST BE Y, N, OR BLANK
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM006E THE RERUN OPTION MUST BE Y, N, OR BLANK
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM008E EXTERNAL DEPENDENCIES FORM A LOOP
Explanation: You specified an external dependency that generates a loop. This must be corrected.
System action: The dependency is rejected and the system waits for you to respond.
User response: Check your dependencies.
EQQM009E THE SPECIFIED APPLICATION COULD NOT BE FOUND
Explanation: The application you specified could not be found in the application description database. The
application may have been deleted after the list of applications was created.
System action: The system waits for you to respond.
User response: Return to the previous panel and recreate the list of applications. If the problem persists, contact
your system programmer.
System programmer response: Analyze messages in the TME 10 OPC message log to determine the cause of the
error. If there are no messages, contact your IBM representative.
EQQM010I OCCURRENCE ADDED TO THE CURRENT PLAN
Explanation: The occurrence you specified was added to the current plan.
System action: None.
User response: None.
EQQM011I OCCURRENCE MODIFIED IN THE CURRENT PLAN
Explanation: The occurrence you specified was modified in the current plan.
System action: None.
User response: None.
 Copyright IBM Corp. 1991, 1998
171
EQQM012I Ÿ EQQM019E
EQQM012I OCCURRENCE DELETED FROM THE CURRENT PLAN
Explanation: The occurrence you specified was deleted from the current plan.
System action: None.
User response: None.
EQQM013I THE OCCURRENCE IS SET TO RERUN
Explanation: In the current plan, the status of the occurrence specified was changed to “rerun.”
System action: None.
User response: None.
EQQM014I THE OCCURRENCE IS SET TO WAITING
Explanation: In the current plan, the status of the occurrence specified was changed to “waiting.”
System action: None.
User response: None.
EQQM015I AN OCCURRENCE HAS BEEN COMPLETED
Explanation: The occurrence you specified has been completed.
System action: None.
User response: None.
EQQM016E THE OCCURRENCE HAS BEEN UPDATED BY AN AUTOMATIC EVENT
Explanation: During the time taken to enter the modifications for the occurrence, at least one operation status has
been updated because an automatic event has been processed.
System action: The request is rejected.
User response: Repeat the dialog request. The status set when the automatic event was processed is now the
initial status for the dialog request.
EQQM017E OCCURRENCE BEING UPDATED BY ANOTHER USER
Explanation: You selected an occurrence that is being updated by another user.
System action: The system waits for you to respond.
User response: Try again later.
EQQM018E OCCURRENCE ALREADY EXISTS - NOT ADDED
Explanation: The occurrence you attempted to add already exists in the current plan.
System action: The occurrence is not added to the current plan, and the system waits for you to respond.
User response: Check the existing occurrence to determine whether or not the occurrence specified should be
added with a new input arrival date and time.
EQQM019E THE SPECIFIED APPLICATION IS CURRENTLY BEING UPDATED
Explanation: The application description you specified is currently being updated by another user.
System action: The system waits for you to respond.
User response: Try again later.
172
TME 10 OPC Messages and Codes
EQQM020E Ÿ EQQM026E
EQQM020E VALID STATUSES ARE W, S, C, E, AND U, IN ANY COMBINATION
Explanation: In the Modify Current Plan dialog, you entered an invalid status for selecting occurrences in the current
plan.
System action: The panel is redisplayed and the system waits for you to respond.
User response: Correct the invalid values.
EQQM021I THE OPERATION WAS RESET TO READY
Explanation: In the current plan, the status of the operation specified was reset to “ready.”
System action: None.
User response: None.
EQQM022I THE OPERATION WAS COMPLETED
Explanation: The operation you specified has been completed.
System action: None.
User response: None.
EQQM023E A DELETED OCCURRENCE CANNOT BE MODIFIED
Explanation: The function you selected attempts to modify an occurrence that has been deleted from the current
plan.
System action: The request is rejected.
User response: None.
EQQM024E SUBSYSTEM REQUEST FAILED DUE TO I/O ERROR
Explanation: The modify current plan request failed because of an I/O error.
System action: The modify current plan function is terminated; no updates are made.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log to determine the cause of the error.
EQQM025E DEPENDENT OPERATIONS HAVE BEEN CHANGED DURING SESSION. RS: XSSRS
Explanation: Operations that have external dependencies to the occurrence you attempted to modify have been
changed in such a way that your modify request failed.
System action: The request is rejected. Message EQQMxssrsE is written to the message log, where xssrs is the
reason code displayed by this message.
User response: See the message indicated by the reason code.
EQQM026E REQUEST FAILED BECAUSE OF SUBSYSTEM ERROR
Explanation: The modify current plan request failed because of an error in the TME 10 OPC subsystem.
System action: The modify current plan function is terminated; no updates are made.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log to determine the cause of the error.
Chapter 16. EQQMnnn Messages
173
EQQM027E Ÿ EQQM033E
EQQM027E REQUEST FAILED BECAUSE OF SUBSYSTEM ERROR. REASON: XSSRS
Explanation: The modify current plan request failed because of an error in the TME 10 OPC subsystem.
System action: The modify current plan function is terminated; no updates are made. Message EQQMxssrsE is
written to the message log, where xssrs is the reason code displayed by this message.
User response: See the message indicated by the reason code.
EQQM028I DELETE OF MAAID MAIMD MAIMT IGNORED WHILE CREATING NEW PLAN
Explanation: An attempt to delete an occurrence with status complete has been rejected because a daily planning
batch program is currently creating a new current plan. Occurrences that were complete when the daily planning job
started are removed, and will not be available in the new plan.
System action: The request is rejected. Message EQQM937E is written to the TME 10 OPC message log.
User response: None.
EQQM029E REQUEST FAILED BECAUSE OF SUBSYSTEM ERROR
Explanation: The modify current plan request failed because of an error in the TME 10 OPC subsystem.
System action: The modify current plan function is terminated; no updates are made.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log to determine the cause of the error.
EQQM030E INPUT ARRIVAL IS LATER THAN CURRENT PLAN END
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM031I THE OCCURRENCE HAS NO EXTERNAL DEPENDENCIES
Explanation: The selected occurrence has no external dependencies.
System action: None.
User response: None.
EQQM032E UNSUPPORTED STATUS CHANGE OF OSEQ OP. WITH UNCOMPLETED PREDECESSOR(S)
Explanation: The request requires an operation in error status with error code OSEQ to change status. There are
restrictions as to how this can be done when the operation has uncompleted predecessors, that is, the operation is
still out of sequence. This is not one of the accepted ways.
System action: The request is rejected. The system waits for you to respond.
User response: The OSEQ operation can be reset to the proper status, waiting, by using the operation restart
request from the ended-in-error list panel. The modify occurrence request can also be used, The operation can be
deleted, or the occurrence can be deleted or set to waiting. An occurrence rerun or a change of the operation status
will not be accepted until all predecessors have been completed or the dependencies have been deleted.
EQQM033E CODE MUST BE ONE OF ST1E , ST1D , ST1P or ST1A
Explanation: You entered an invalid code for selecting occurrences from the current plan in the Modify Current Plan
dialog.
System action: The system waits for you to respond.
User response: Enter correct code.
174
TME 10 OPC Messages and Codes
EQQM034E Ÿ EQQM062E
EQQM034E THE JCL FOR THIS OPERATION IS BEING EDITED BY ANOTHER USER
Explanation: You tried to rerun an operation, but the JCL for this operation is being edited by another user.
System action: The system waits for you to respond.
User response: Try again later.
EQQM035E ONE OF THE WS REFERENCED BY OPERATIONS IN THIS OCC. IS NOT IN CP
Explanation: TME 10 OPC was validating an occurrence to be added. A workstation referenced by an operation in
this occurrence is not defined to the current plan.
Perhaps a new workstation has been created, but the daily plan batch program has not yet been executed.
System action: The request is rejected.
User response: Examine the TME 10 OPC MLOG. Look for message EQQM933E, which identifies the workstation
and operation. Then, contact your system programmer.
System programmer response: If necessary, run a daily plan batch program to add the workstation to the current
plan.
EQQM040E ERROR CODE MUST BE GIVEN FOR ERROR STATUS OPERATION
Explanation: An error code must be given for an operation in error.
System action: The panel is redisplayed.
User response: Correct the error.
EQQM041E ERROR CODE MUST BE BLANK FOR OPERATION NOT IN ERROR
Explanation: Error code only has meaning for an operation in error.
System action: The panel is redisplayed.
User response: Change operation status or blank out the error code.
EQQM043W THE OPERATION WAS NOT FOUND, MAY HAVE BEEN ALTERED
Explanation: The automatic job recovery request could not be processed because the operation record could not be
read.
System action: The automatic job recovery request is ignored; the system waits for you to respond.
User response: If the error persists, contact your system programmer.
System programmer response: To determine the cause of the error, check the TME 10 OPC message log for I/O
error messages issued at the time the automatic job recovery request was made.
EQQM061E NEW STATUS MUST BE ONE OF THE SUPPORTED CHARACTERS
Explanation: The workstation status must be A, F, or O.
System action: The workstation status is not changed.
User response: Correct the status character, or issue the CANCEL command to cancel the status change request.
EQQM062E THE FAIL/OFFLINE OPTIONS ENTERED ARE NOT VALID
Explanation: The restart option can be R (restart), E (set to error), or L (leave). The reroute option can be Y (yes,
reroute operations) or N (no, do not reroute).
System action: The workstation does not change status. No fail or offline actions are performed.
User response: Correct the options and try again.
Chapter 16. EQQMnnn Messages
175
EQQM063E Ÿ EQQM100W
EQQM063E THE ALTERNATE WS NAME IS NOT FOUND IN THE DATA BASE
Explanation: The alternate workstation is not defined in the workstation database.
System action: The status of the workstation does not change. Reroute is not performed to an alternate WS.
User response: Correct the name specified for alternate WS, or update the workstation description database with
this workstation name.
EQQM064E ALTERNATE WS IS REQUIRED TO BE CPU/WTO TYPE WS
Explanation: The alternate workstation is not defined in the workstation database as a computer type workstation.
System action: The status of the workstation does not change.
User response: Correct the name specified for alternate workstation, or update the workstation description database
for this workstation to specify the correct attributes.
To exit the modification without saving any changes, issue the CANCEL command.
EQQM065W FAIL/OFFLINE OPTIONS NOT APPLICABLE FOR SETTING WS TO ACTIVE
Explanation: Fail/offline options do not apply to active workstations. If you change the status of a workstation to A
(active), any previously defined fail/offline options are ignored.
System action: The system waits for you to respond.
User response: Confirm the request, or cancel it.
EQQM066E THE WORK STATION STATUS INHIBITS ALTERNATE WS SPECIFICATION
Explanation: An active workstation cannot have an alternate workstation.
System action: The WS status does not change.
User response: Either change the workstation status to something other than A (active), or clear the alternate WS
field in the panel.
EQQM067I WORK STATION WSID, HAS BEEN SET TO STAT STATUS
Explanation: The status of a workstation has changed, as you requested on the previous panel.
System action: The status of the workstation is changed. This may affect ongoing work.
User response: None.
EQQM068E THE CURRENT WS CANNOT BE ALTERNATE TO ITSELF
Explanation: The alternate workstation cannot be the current workstation.
System action: The WS status does not change.
User response: Change the alternate workstation name.
EQQM100W DEADLINE IS EARLIER THAN INPUT ARRIVAL TIME - VALUE ACCEPTED
Explanation: The deadline you specified is not valid because it is earlier than the input arrival time; however, the
deadline value is accepted.
System action: None.
User response: None.
176
TME 10 OPC Messages and Codes
EQQM104E Ÿ EQQM115E
EQQM104E NO APPLICATIONS MET THE SELECTION CRITERIA
Explanation: No applications were found in the application description database, which met the selection criteria that
you specified.
System action: The system waits for you to respond.
User response: Change the selection criteria.
EQQM106E DEP OPTION MUST BE ONE OF OCHCYES, ochpred, ochsucc, ochgrp or ochcno
Explanation: You have entered a value for the dependency resolution attribute that is not recognized by the MCP
dialog. You must change the value to one of the supported values defined by this message.
System action: The system waits for you to respond.
User response: Change the dependency resolution value.
EQQM107E BOTH DATE AND TIME MUST BE SPECIFIED FOR INPUT ARRIVAL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM108E BOTH DATE AND TIME MUST BE SPECIFIED FOR DEADLINE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM109E APPLICATION VALID-FROM IS LATER THAN PLAN END MPLENDI
Explanation: The valid-from date and time of the occurrence you attempted to add to the current plan lie outside the
current plan end.
System action: The request is rejected. The system waits for you to respond.
User response: Change the valid-from date and time of the occurrence using the Application Description dialog.
EQQM110E OPERATIONS WITH DUPLICATE NUMBERS ARE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM112E THE OCCURRENCE CONTAINS UNCONNECTED OPERATIONS
Explanation: In the occurrence you are modifying, there is more than one network of dependencies. This is not
allowed.
System action: The modifications is rejected; the system waits for you to respond.
User response: Verify and correct the dependencies.
EQQM113E JOBNAME MOJBN MUST BE SAME IN JOB SETUP, PROCESS, AND PRINT
Explanation: The job name specified (MOJBN) for the job setup, process, and print operations must be the same.
System action: The system waits for you to respond.
User response: Verify and correct, for example, the dependencies or the job names.
EQQM115E A PROCESS OPERATION MUST PRECEDE A PRINT OPERATION
Explanation: A print operation must be preceded by a process operation.
System action: The system waits for you to respond.
User response: Verify and correct, for example, the print operation or the process operation.
Chapter 16. EQQMnnn Messages
177
EQQM117E Ÿ EQQM150E
EQQM117E WORK STATION MOWSN IS NOT FOUND IN THE CP, OR ACCESS WAS REVOKED
Explanation: The workstation specified (mowsn) does not exist in the current plan, or you are not authorized to
access this workstation.
System action: The system waits for you to respond.
User response: Change the occurrence so that it uses only workstations that are in the current plan. If you are not
authorized to access this workstation, contact your security administrator.
EQQM118E A SETUP OPERATION MUST HAVE A PROCESS SUCCESSOR
Explanation: A setup operation must be succeeded by a process operation.
System action: The system waits for you to respond.
User response: Verify and correct, for example, the setup operation or the process operation.
EQQM119E A PREDECESSOR TO OPERATION MONUM IS ALSO A SUCCESSOR
Explanation: A predecessor to operation monum is also a successor. This forms a dependency loop and is not
allowed.
System action: The system waits for you to respond.
User response: Verify the dependencies to the operation monum.
EQQM120E ADID: ADID, IA: IA, OPNO: OPNO, CAUSES A LOOP
Explanation: The specified dependencies create a loop in the operations network.
System action: The update request is rejected.
User response: Check your dependency specifications.
EQQM121W THERE IS JCL ON THE JS FILE FOR OPERATION MONUM
Explanation: There is a record on the JS file that matches an operation on a computer workstation in the occurrence
being added and this record was not added during the current MCP dialog session.
System action: The current panel is redisplayed.
User response: Go to the operation list panel and enter the J row command to review the JCL for the operation
defined by this message. If the JCL is correct for the operation, exit JCL edit via the END command. If the JCL is not
correct, then correct it or delete it and exit JCL edit via the END command.
EQQM130W OCCURRENCE HAS A PENDING PREDECESSOR, REQUEST IS NOT POSSIBLE
Explanation: The occurrence to be deleted or completed has a predecessor which is not yet in the current plan.
System action: The request is rejected.
User response: The function cannot be performed until the pending predecessor dependency is removed.
EQQM150E INPUT ARRIVAL IS LATER THAN CURRENT PLAN END CPED CPET
Explanation: A request to modify or create an occurrence on the current plan specifies an input arrival time later
than or equal to the current plan end time. All modifications to the current plan must be earlier than the current plan
end time.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
User response: Correct the input arrival time and resubmit the job.
178
TME 10 OPC Messages and Codes
EQQM151E Ÿ EQQM155E
EQQM151E CURRENT PLAN READ ERROR, AD NOT ADDED TO CURRENT PLAN
Explanation: A request to create an occurrence in the current plan failed due to an I/O error.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The message log of the TME 10 OPC subsystem contains the I/O error message.
User response: Resubmit the job when the problem causing the I/O error has been corrected.
System programmer response: Review the message log of the TME 10 OPC subsystem to determine the cause of
the error. If you cannot determine the cause and the error persists, contact your IBM representative.
EQQM152E ALL OCCURRENCES OF AD BEFORE CP END CPED CPET exist
Explanation: A request to create an occurrence in the current plan failed because the occurrence already exists. No
input arrival time was given in the request which implies that a default input arrival time should be used.
Problem determination: The default input arrival time is the current time, consisting of the current date, current
hour, and current minute. If an occurrence of the application with that input arrival time already exists, the next minute
is used. If that occurrence also exists, the following minute is used. This search for an input arrival time continues up
to the current plan end time.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
User response: If necessary, resubmit the job after either extending the current plan or deleting some existing
occurrence.
EQQM153E IA NOT BEFORE CP END CPED CPET, AD NOT ADDED
Explanation: A request to create an occurrence in the current plan failed because the current plan end time has
passed. No input arrival time was given in the request, which implies that a default input arrival time should be used.
This default is the current time, consisting of the current date, current hour, and current minute. The request is
rejected because the current plan ends before the current time.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
User response: If necessary, resubmit the job after extending the current plan.
EQQM154E ALL POTENTIAL EXTERNAL SUCCESSORS COULD NOT BE RESOLVED
Explanation: A request to create an occurrence in the current plan failed because the resolve required option was
YES and there are occurrences in the current plan that are possible successor occurrences but the application
description defines more dependencies than could be resolved using existing successor candidates.
System action: The current occurrence is not added to the current plan.
User response: If necessary, change the resolve required option to NO and retry the request to add the occurrence
to the current plan.
EQQM155E OCCURRENCE WITH SAME ADID AND IA EXISTS IN LONG-TERM PLAN
Explanation: A request to create or modify an occurrence in the current plan specifies an application ID and input
arrival date and time that are the same as an existing occurrence in the long-term plan.
System action: If this is an MCP dialog request, the request is rejected. If it is a request to the program interface
function (PIF), the request is rejected and control is returned with an error return code.
User response: Change the input arrival date or time, and resubmit the request.
Chapter 16. EQQMnnn Messages
179
EQQM161E Ÿ EQQM171E
EQQM161E MODIFY CP REQUEST FAILED, INSUFFICIENT STORAGE. REASON: RS
Explanation: A request to create or modify an occurrence in the current plan failed due to storage allocation failure.
The reason code provides debugging information for IBM personnel.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
User response: If necessary, resubmit the job after the TME 10 OPC subsystem has been restarted in a larger
region.
System programmer response: Allocate a larger region to the TME 10 OPC subsystem and then restart the
subsystem. If the error persists, contact your IBM representative.
EQQM162W OPERATION MONUM DEFINES TOO MANY RESOURCES, FIRST MAXRES USED
Explanation: The application description record defines an operation that has more special resources than is
supported by the Create Occurrence function in the MCP dialog.
System action: The dialog uses the maximum resources defined by the application description to initialize special
resources for this operation.
User response: Enter the OPER primary command to display operations for this occurrence. Select the operation
defined by this message and review the current definition of special resources for the operation. Modify currently
defined resources if required, but note that no additional resources can be added for this operation.
EQQM163W TWO OR MORE OPERATIONS DEFINE TOO MANY RESOURCES, FIRST MAXRES USED
Explanation: The application description record defines one or more operations that have more special resources
than is supported by the Create Occurrence function in the MCP dialog.
System action: The dialog uses the maximum resources defined by the application description for each operation
that have too many special resources.
User response: Enter the OPER primary command to display operations for this occurrence. Review the current
definition of special resources for this occurrence. Modify currently defined resources if required, but note that the
number of resources that can be defined per operation is limited by the maximum record length of 32,768 bytes.
EQQM164E AN OPERATION RECORD IS TOO LARGE TO BE SAVED IN CURRENT PLAN
Explanation: The current occurrence contains an operation that contains too much information to be saved in the
Current Plan data set.
System action: The occurrence has not been saved. The dialog waits for the dialog user to continue updating the
current occurrence.
User response: Enter the OPER primary command to display operations for this occurrence. Review the current
definition of the operations. Try to reduce the number of special resources and/or dependencies defined for the most
complex operations. After making corrections, retry the Current Plan update request.
EQQM171E MAXIMUM NUMBER OF OCCURRENCES OF AD EXISTS
Explanation: No more occurrences of this application can be added. TME 10 OPC can handle approximately 870
occurrences of each application.
System action: The create request is rejected.
User response: If possible, delete occurrences of this application that have finished processing. These occurrences
will be removed from the plan next time, producing a new plan. If necessary, copy the application description and add
the occurrence with a new name.
180
TME 10 OPC Messages and Codes
EQQM172E Ÿ EQQM204E
EQQM172E MAXIMUM NUMBER OF OCCURRENCES EXISTS, FAILED TO ADD AD
| Explanation: No more occurrences can be added to the Current Plan because the maximum number of
| occurrences—32767 or the number specified in the MAXOCCNUM option of the JTOPTS statement—has been
| reached.
System action: The request is rejected.
Problem determination: If you use ETT, PIF, or Automatic Recovery, check that these functions are working
correctly. For example, make sure that you do not have an endless ETT loop where the availability of a special
resource is set to YES by a job that ETT adds when it detects that this same resource is set to YES. Check the
Current Plan for instances of an unusually high number of occurrences of a particular application. If you see such an
application, look in the application description data base and make sure that the run cycles for the application are
correct. When you specify PREVRES(YES) on the BATCHOPT initialization statement, information about completed
and deleted occurrences is carried forward, for reporting purposes, into a new Current Plan. If your Current Plan
regularly contains a large number of occurrences, and you specify YES for PREVRES, you should consider changing
this value to NO.
User response: Check that the current plan does not contain any occurrences that should not be in the plan. If you
find any such occurrences, complete or delete them. Replan the Current Plan to remove all completed and deleted
occurrences, and then try to add the occurrence again. If your Current Plan regularly contains a large number of
occurrences, you should consider shortening the length of the Current Plan in future daily planning runs.
EQQM173W CHANGING INPUT ARRIVAL MAY CAUSE EDITED JCL TO BE LOST
Explanation: The JCL for an operation in this occurrence has been edited. Changing input arrival for this
occurrence may cause the edited JCL to be lost.
System action: The system waits for you to respond
User response: To keep the edited JCL, change the input arrival back to the original value and press ENTER. If
you need the input arrival to change acknowledge this by pressing ENTER, this may cause the JCL you edited to be
lost.
EQQM200E THE SPECIFIED WORK STATION ID DOES NOT EXIST
Explanation: Data entry error; see “Data Entry Errors” on page 2.
| EQQM201E THE OPERATION NUMBER MUST BE BETWEEN 1 - 255
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM202E THE JOBNAME MUST BE IN THE FORMAT CAAAAAAA
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A job name can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that
is, #, $, and @). The first character must be alphabetic or national, the remaining characters can be alphabetic,
numeric, and national characters.
EQQM203E JOB SETUP, COMPUTER, AND PRINT OPERATIONS REQUIRE A JOBNAME
Explanation: A jobname must be given for an operation at a general workstation with the job setup option, or at a
computer or printer workstation.
System action: The panel is redisplayed.
User response: Specify a jobname for the operation.
EQQM204E A DURATION MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 16. EQQMnnn Messages
181
EQQM205E Ÿ EQQM218E
EQQM205E NUMBER OF SERVERS MUST BE BETWEEN 1 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM206E NUMBER OF WORK STATION RESOURCES MUST BE BETWEEN 0 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM207E THE NEW STATUS MUST BE R-READY, S-STARTED, OR C-COMPLETED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM208E THE STATUS CANNOT BE CHANGED - EXTERNAL SUCCESSOR STARTED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM209E THE VARIABLE TABLE IS NOT DEFINED TO OPC/ESA
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You have tried to define a variable table ID that does not exist in TME 10 OPC's database.
EQQM210E RESOURCES WITH DUPLICATE NAMES WERE FOUND
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM211E A RESOURCE NAME MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM212E RESOURCE OPTION MUST BE S-SHARE OR X-EXCLUSIVE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM213E OPTION FOR AUTOMATIC TRACKING MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM214E OPTION FOR AUTOMATIC SUBMIT MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM215E OPTION FOR HOLD/RELEASE MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM216E OPTION FOR TIME DEPENDENCY MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM217E OPTION FOR SUPPRESS IF LATE MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM218E EXTERNAL PREDECESSOR FOUND, STATUS CANNOT BE CHANGED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You cannot change the status of an operation when an external predecessor exists in the current plan.
182
TME 10 OPC Messages and Codes
EQQM219E Ÿ EQQM226E
EQQM219E OPERATION NUMBER MUST NOT BE CHANGED FROM MOONU
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM220E DEPENDENCY TYPE MUST BE P-PREDECESSOR OR S-SUCCESSOR
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM221E NO OPERATIONS IN CURRENT PLAN MATCH THE SEARCH ARGUMENT
Explanation: In the current plan, there are no operations that meet your selection criteria.
System action: The system waits for you to respond.
User response: Check your selection criteria.
EQQM222W UNRESOLVED EXTERNAL PREDECESSORS EXIST
Explanation: This message is issued when the Automatic Dep option is set to Y or P and the Resolve Required
option is set to Y. When the message is issued on panel EQQMAOCP it means that the current occurrence could not
be added to the Current Plan because one or more external predecessors defined by the application description could
not be resolved.
When the message is issued on panel EQQMARXL it means that one or more external predecessors displayed by the
panel could not be resolved. Input arrival time for unresolved dependencies is blank.
System action: The MCP dialog waits for input from the dialog user.
User response: If the message is issued on panel EQQMAOCP enter the DEP primary command to modify
automatically added dependencies.
If the message is issued on panel EQQMARXL delete all unresolved predecessor dependencies.
EQQM223W OPERATION DEADLINE PRECEDES OPERATION INPUT ARRIVAL - ACCEPTED
Explanation: The operation deadline is earlier than the operation input arrival. This is accepted but might not be
what you intend.
System action: None.
User response: None.
EQQM224W OPERATION INPUT ARRIVAL PRECEDES OCCURRENCE - ACCEPTED
Explanation: The operation input arrival date is earlier than the occurrence. This is accepted but might not be what
you intend.
System action: None.
User response: None.
EQQM225W OPERATION DEADLINE LATER THAN OCCURRENCE DEADLINE - ACCEPTED
Explanation: The operation deadline specified is later than occurrence deadline. This is accepted but might not be
what you intend.
System action: None.
User response: None.
EQQM226E DEPENDENCY TYPE MUST BE P OR S
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 16. EQQMnnn Messages
183
EQQM227W Ÿ EQQM237E
EQQM227W A SUCCESSOR DEPENDENCY COULD NOT BE ADDED
Explanation: A dependency to a potential successor operation could not be added because the successor operation
has already started.
System action: If this message is issued when the DEP command has been entered, then unresolved successors
are indicated by a missing (blank) input arrival time. If this message is issued when trying to add an occurrence to the
plan and the RESOLVE REQUIRED indicator is Y, then the occurrence is not added.
User response: If the occurrence should be added to the plan without the successor dependency, change the
RESOLVE REQUIRED indicator to N and retry the add occurrence function.
EQQM228E A DEPENDENCY TO THE OPERATION IS ALREADY DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM229E JCL BROWSE/EDIT CAN ONLY BE SELECTED FOR PROCESSOR WORK STATIONS
Explanation: Data entry error; see “Data Entry Errors” on page 2. It is not allowed to browse or edit JCL for
non-processor operations.
EQQM230E HIGHEST RETURN CODE IS NOT NUMERIC
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM231E SPECIFIED OPERATION IS ALREADY A PREDECESSOR
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM232E SPECIFIED OPERATION IS ALREADY A SUCCESSOR
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM233I THE SPECIFIED OPERATION HAS BEEN ADDED AS A PREDECESSOR
Explanation: The specified operation has been added as a predecessor.
System action: None.
User response: None.
EQQM234I THE SPECIFIED OPERATION HAS BEEN ADDED AS A SUCCESSOR
Explanation: The specified operation has been added as successor.
System action: None.
User response: None.
EQQM235E THE SPECIFIED OPTION MUST BE EITHER Y, N, OR BLANK
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The value of this input field must be Y (for Yes), N (for No), or a blank (for no value). Read the help text for the
panel, and decide which option you want.
EQQM236E VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM237E OPTION FOR DEADLINE WTO MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The option can be Y (yes) or N (no).
184
TME 10 OPC Messages and Codes
EQQM238E Ÿ EQQM246E
EQQM238E YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE
Explanation: You have attempted to access a JCL variable table. To do this, you need at least read authority to the
JCL variable table database.
System action: The system waits for you to respond.
User response: Contact your security administrator if you need to refer to JCL variable table names.
EQQM239E MULTIPLE RESTART POINTS ARE NOT ALLOWED, DUE TO EXTERNAL DEPENDENCIES
Explanation: You selected more than one restart point in the application occurrence being rerun. You cannot use
multiple restart points because the occurrence has external dependencies that would be updated by the rerun.
If you want to use more than one restart point, the application occurrence being rerun must be the only occurrence
whose status will change.
System action: The first restart point that you selected is accepted. All other restart points are cancelled.
User response: If you want to rerun the application occurrence starting from the first restart point, enter Y on the
rerun confirmation panel. Otherwise, enter N.
EQQM240E THE OPERATION SELECTED AS RESTART POINT HAS PENDING PREDECESSORS
Explanation: The operation that you selected as a restart point has at least one predecessor that is pending (not in
the current plan).
Pending predecessors are marked with \P\ in the predecessor type column at the far right of the panel.
System action: The occurrence status is not changed to rerun, but updates made to the JCL are saved.
User response: Select another restart point in the application occurrence, or delete the pending dependencies.
Then, run the occurrence again.
EQQM241I THE OCCURRENCE STATUS HAS NOT BEEN CHANGED
Explanation: The occurrence status has not set to rerun because:
1. The operation that you selected as a restart point has at least one predecessor that is pending (not in the current
plan). The status cannot be set to rerun until you delete the pending dependencies.
2. You entered the cancel command on the EQQMOSTL panel.
System action: The occurrence status is not changed to rerun, but updates made to the JCL are saved.
User response: None.
EQQM242E THE NUMBER OF PARALLEL SERVERS MUST BE 1 FOR CPU OPERATIONS
Explanation: Operations on a computer workstation can only use one parallel server.
System action: The panel is redisplayed and the dialog waits for you to change the number of parallel servers.
User response: Change the number of parallel servers to 1.
EQQM245W THE CATALOG MANAGEMENT ACTION HAS STARTED FOR THIS OPERATION
Explanation: When trying to start an auto recovery action, TME 10 OPC found that there is a catalog management
action in progress.
System action: The automatic recovery request is ignored.
User response: Try again later.
| EQQM246E DEPENDENT OCC NOT FOUND
| Explanation: The dependent occurrence OCC was not found in the current plan.
| User response: Add new predecessor/successor occurrences to the current plan.
Chapter 16. EQQMnnn Messages
185
EQQM250E Ÿ EQQM257I
EQQM250E CURRENT OPERATION STATUS MUST BE A, *, R, W, C, OR E TO BE HELD
Explanation: Only operations in status A, W, R, *, C, or E can be manually held.
System action: The request is ignored.
User response: None.
EQQM251I OPERATION IS ALREADY MANUALLY HELD BY DIALOG
Explanation: The operation has already been set to MANUAL HOLD by an TME 10 OPC dialog user.
System action: The request is ignored.
User response: None.
EQQM252I OPERATION IS NOT MANUALLY HELD BY DIALOG
Explanation: The operation for which the MANUAL RELEASE command was issued, is not Manually HELD by an
TME 10 OPC dialog user request.
System action: The request is ignored.
User response: None.
EQQM253I OPERATION IS PUT IN MANUAL HOLD
Explanation: The operation for which the manual HOLD command was issued is now recognized to be HELD by
TME 10 OPC.
System action: The operation is manually HELD.
User response: None.
EQQM254I OPERATION HAS BEEN MANUALLY RELEASED FROM MANUAL HOLD
Explanation: A previously held operation has been release from hold at an TME 10 OPC dialog user's request.
System action: The operation is released, and may be scheduled by TME 10 OPC.
User response: None.
EQQM255E CURRENT OPERATION STATUS MUST BE A, *, W, C, OR R TO BE NOPED
Explanation: Only operations in status A, W, R, C, or &asteriak. can be no-oped.
System action: The request is ignored.
User response: None.
EQQM256I OPERATION IS ALREADY NOPED BY USER REQUEST
Explanation: The operation for which the NOP command was issued has already been NOPed by a dialog request.
System action: The request is ignored.
User response: None.
EQQM257I OPERATION IS NOT NOPED
Explanation: The operation for which the UN-NOP command was issued, is not currently NOP.
System action: The request is ignored.
User response: None.
186
TME 10 OPC Messages and Codes
EQQM258I Ÿ EQQM265E
EQQM258I OPERATION HAS BEEN NOPED
Explanation: The operation has been recognized as no-oped by TME 10 OPC The operation will not be executed,
and dependent operations may be started as a result.
System action: The operation is indicated as no-oped.
User response: None.
EQQM259I OPERATION NOP HAS BEEN RESET
Explanation: An operation has been successfully reset from its NOP indication at an TME 10 OPC dialog user's
request.
System action: The operation's NOP indication is removed.
User response: None.
EQQM260I OPERATION HAS BEEN EXECUTE INDICATED
Explanation: An operation has been marked as EXECUTE by TME 10 OPC and will be started without regard to the
normal job submission criteria.
System action: Processing continues.
User response: None.
EQQM261E CURRENT OPERATION STATUS MUST BE A, *, OR R TO BE EXECUTED
Explanation: Only operations in status A, R or * can be the subject of an EXECUTE request.
System action: The request is ignored.
EQQM262E YOU DO NOT HAVE AUTHORITY TO USE THE EXECUTE COMMAND
Explanation: To use the function you selected, you must have update authority to the EXECUTE resource.
System action: The request is rejected and the system waits for you to respond.
User response: Contact your security administrator if you need to use the EXECUTE command.
EQQM263E COMMAND VALID ONLY ON COMPUTER AUTOMATIC WORKSTATIONS
Explanation: The workstation on which this operation was scheduled is not a computer type workstation with the
automatic reporting attribute.
System action: The request is ignored.
User response: Issue the command only on computer workstations with the automatic reporting attribute.
EQQM264E THE COMMAND THAT WAS ISSUED IS NOT SUPPORTED
Explanation: The command is not supported by TME 10 OPC.
System action: The request is ignored.
User response: Issue only valid TME 10 OPC commands.
EQQM265E COMMAND SUPPORTED ON AUTOMATIC CPU OR NONREPORTING WORKSTATIONS
Explanation: The command you issued is supported on automatic computer type workstations, or workstations with
the nonreporting attribute.
System action: The request is ignored.
User response: Issue the command only on supported workstations.
Chapter 16. EQQMnnn Messages
187
EQQM266E Ÿ EQQM313E
EQQM266E THERE IS NO ACTIVE WORKSTATION FOR THIS OPERATION
Explanation: The operation is scheduled on a workstation that is inactive. If alternate workstations are specified,
these are also inactive.
System action: The request is ignored.
User response: Issue the EXECUTE command when the workstation, or an alternate workstation, becomes active
again.
EQQM267E STATUS CANNOT BE CHANGED AS THE OPERATION HAS BEEN MANUALLY HELD
Explanation: You cannot request TME 10 OPC to set the next logical status for an operation that has been
manually held.
System action: The request is ignored.
User response: Either set a specific status using the N–x row command, or manually release the operation (MR)
and then reissue the N row command.
EQQM301I WORK STATION UPDATED IN CURRENT PLAN
Explanation: The workstation has been updated in the current plan.
System action: The modify workstation function is terminated.
User response: None.
EQQM302W A WORK STATION IS CURRENTLY BEING UPDATED, TRY LATER
Explanation: You have attempted to modify a workstation, but it is currently being updated by another user.
System action: The system waits for you to respond.
User response: Try again later.
EQQM303E THE REPORTING ATTRIBUTE SPECIFIED MUST BE A, S, C, OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM304E CONTROL ON SERVERS OR RESOURCES MUST BE Y-YES OR N-NO
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM310E OPEN TIME INTERVALS MUST NOT OVERLAP
Explanation: Data entry error; see “Data Entry Errors” on page 2.
It is not allowed to have overlapping open time intervals for the workstation.
EQQM311E INTERVAL START MUST PRECEDE END
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The open interval start time must be earlier than the open interval end time.
EQQM312E START TIME MUST BE SPECIFIED FOR AN INTERVAL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM313E END TIME MUST BE SPECIFIED FOR AN INTERVAL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
188
TME 10 OPC Messages and Codes
EQQM314E Ÿ EQQM322E
EQQM314E VALUE FOR PARALLEL SERVERS MUST BE 0 - 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM315I INTERVAL PREVIEW
Explanation: Table result is merged from modified and planned intervals. The table is built from the modified and
planned intervals according to the workstation.
System action: Processing continues.
User response: The END command will cause the displayed table to be used. ENTER will cause the table to be
displayed without this message.
| EQQM316I PENDING STATUS RESET
|
|
|
|
|
Explanation: The job for which the catalog management action has been invoked, contains no SYSOUT information,
so that only a job level restart is possible. The job level restart does not require any action on the JOB data sets.
However, some data sets (those in flushed steps or those allocated in the job but referenced in previous steps) need
to be checked and removed from the CP before a rerun can be performed. Otherwise, the message EQQM323W
CATALOG MANAGEMENT PENDING will be displayed.
| System action: Processing continues.
| User response: Make sure that the necessary datasets are discarded from the current plan.
EQQM320W DATASET AND JOBLOG INFORMATION ARE BOTH MISSING
Explanation: Information about datasets defined in the JCL and JES joblogs have not been passed back to the
controller. As a result, no catalog management action is possible. There are a number of reasons why you can
receive this message:
Ÿ
Ÿ
Ÿ
Ÿ
CATMGT(NO) was specified, or defaulted, in the OPCOPTS initialization statement when the operation started
The catalog management indicator for the operation specifies N
Dataset information for the operation has been filtered by EQQUX004
The job or started task did not alter the catalog status of any DD defined dataset.
System action: Processing continues.
User response: None.
EQQM321I THE CATALOG MANAGEMENT PROCESS HAS ALREADY BEEN STARTED
Explanation: You have tried to initiate the catalog management process for the current operation. The process has
already been started by TME 10 OPC, and cannot be started again.
System action: The request is ignored.
User response: None.
EQQM322E OPC/ESA CANNOT INITIATE THE CATALOG MANAGEMENT FUNCTION
Explanation: You have tried to initiate catalog management for the current operation, but the process cannot start.
This is because either TME 10 OPC has no contact with the tracker or the catalog management subtask is not active
at the controller.
System action: No catalog management action is initiated for this operation
User response: Contact your systems programmer.
System programmer response: Check whether the tracker at the destination defined for the current workstation is
operational or not. If it is not, retry the process when it becomes available again. Make sure that CATMGT(YES) is
specified on the OPCOPTS initialization statement of the controller, and that the controller, or catalog management
subtask, has been restarted since CATMGT(YES) was specified. Also check that the catalog management subtask
has not been stopped by an MVS modify command, or ended because of an error, after TME 10 OPC was started. If
the problem persists, contact your IBM representative.
Chapter 16. EQQMnnn Messages
189
EQQM323W Ÿ EQQM330I
EQQM323W CATALOG MANAGEMENT IS PENDING FOR THE CURRENT OPERATION
Explanation: You have tried to perform automatic recovery for this operation when there is a deferred catalog
management action defined for this operation.
System action: The system waits for you to respond
User response: Make sure that the action is either performed or discarded before you try to perform automatic
recovery for the operation
EQQM324E CATALOG MANAGEMENT is in progress for oper OP in appl AD.
Explanation: You have tried to restart an operation or rerun an occurrence when there is a catalog management
action in progress.
System action: The request is ignored.
User response: Make sure that the action has ended before you try to perform a rerun or restart.
EQQM325I OPC/ESA HAS BEEN REQUESTED TO START THE CATALOG MANAGEMENT ACTIONS
Explanation: TME 10 OPC has started catalog management actions for the current operation.
System action: The catalog management action will be taken for the current operation.
User response: None.
EQQM326I THE REQUEST TO DISCARD THE CATALOG MANAGEMENT HAS BEEN CANCELLED
Explanation: The DISCARD request has been cancelled by you. No datasets have been deleted from the list of
datasets.
System action: None.
User response: None.
EQQM327I THE CATALOG MANAGEMENT ACTION FOR THIS OPERATION IS DISCARDED
Explanation: The DISCARD request has been accepted, and the catalog management status is set to D (discarded).
System action: The catalog management status is changed to D.
User response: None.
EQQM328E A VALID RESPONSE IS EITHER Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQM329I THE STATUS OF THE CATALOG MANAGEMENT ACTION HAS NOT BEEN DETERMINED
Explanation: The catalog management process has not yet ended. Therefore the status of the datasets is not fully
updated.
System action: Processing continues.
User response: Status for all datasets is available when the catalog management action has ended.
EQQM330I THE CATALOG MANAGEMENT ACTION FOR THE OPERATION HAS BEEN DISCARDED
Explanation: The user has verified a DISCARD command for catalog management. Therefore the catalog
management action has been set to D (discarded) in TME 10 OPC's plan, and no catalog management will be
performed for this operation.
System action: The catalog management action is discarded.
User response: None.
190
TME 10 OPC Messages and Codes
EQQM331E Ÿ EQQM337E
EQQM331E THE ONLY VALID VALUES ARE OCHCDFR ,OCHCYES OR OCHCNO
Explanation: You have entered an incorrect action for the catalog management function.
System action: The system waits for you to respond.
User response: Enter correct value and press enter.
EQQM332I THE CATALOG MANAGEMENT FUNCTION IS NO LONGER ACTIVE
Explanation: The catalog management function has been deactivated after the time that dataset information was
collected for this operation.
System action: The catalog management action is ignored.
User response: Contact your systems programmer.
System programmer response: If you want the catalog management function to be activated, you will have to
change the OPCOPTS keyword CATMGT to YES and restart the controller.
EQQM333W OPC/ESA INITIALLY FOUND INCONSISTENCIES IN THE JCL
Explanation: When TME 10 OPC initially checked the JCL, inconsistencies were found.
System action: The system waits for you to respond
User response: Enter Yes command to accept the step level restart selected or, enter No to reject the restart
setting.
EQQM334I MORE THAN ONE STEP WITH SAME PROCSTEP/STEPNAME
Explanation: The selected stepname/proc stepname occurs more than once in the JCL.
System action: TME 10 OPC will choose the first occurrence of the selected step name and use it as the restart
step.
User response: None.
EQQM335E OPC CAN NOT TAILOR ANY JCL BECAUSE NO RESTART STEP WAS SELECTED
Explanation: To tailor the JCL for step restart, TME 10 OPC needs a step selection.
System action: System waits for you to respond
User response: Select a step or cancel step restart
EQQM336I THE RESTART HAS BEEN CANCELLED FOR THIS OPERATION
Explanation: If the cancel was for a step restart, the JCL for this operation has not been stored in the JS repository
file, because no step selection was made.
System action: None.
User response: None.
EQQM337E NO STEPS WERE SELECTED FOR RESTART
Explanation: You have excluded all steps for the job, so the JCL cannot be created.
System action: The system waits for you to respond.
User response: Make sure that at least one step is selected for the job, and issue the GO command again.
Chapter 16. EQQMnnn Messages
191
EQQM338I Ÿ EQQM343E
EQQM338I OPC/ESA HAS FOUND NO INCONSISTENCIES IN THE JCL FOR A RESTART
Explanation: TME 10 OPC has investigated the JCL for restart and has found no errors. The operation may be
restarted.
System action: None.
User response: Leave the panel with END command to save the JCL and initiate catalog management actions for
the operation, cancel the restart using the CANCEL command.
EQQM339W THE OPERATION CANNOT BE RESTARTED WITHOUT CHANGING THE JCL
Explanation: TME 10 OPC has investigated the JCL for restart and has detected inconsistencies. TME 10 OPC
detects many situations that can cause problems during the step restart, such as; missing instream data, or references
to a temporary dataset created prior to the restart step.
System action: The JCL is displayed. ISPF message lines are inserted by TME 10 OPC to document the
inconsistencies detected.
User response: Either change the JCL, cancel the restart for this operation, or save the JCL after determining that
the inconsistencies reported will not result in a problem during restart.
EQQM340E OCCURRENCE IN A GROUP MUST BE REMOVED BEFORE IT CAN BE DELETED
Explanation: An occurrence that belongs to an occurrence group cannot be deleted.
System action: The system waits for you to respond.
User response: You must remove the occurrence before you can delete it. You can do this by typing the row
command RG on the MODIFYING OCCURRENCES IN THE CURRENT PLAN panel, or the HANDLING OPERATIONS ENDED
IN ERROR panel. Alternatively, you can erase the group ID field on the MODIFYING AN OCCURRENCE IN THE CURRENT
PLAN panel.
EQQM341E OCCURRENCE IN A GROUP MUST BE REMOVED BEFORE IT CAN BE COMPLETED
Explanation: An occurrence that belongs to an occurrence group cannot be completed.
System action: The system waits for you to respond.
User response: You must remove the occurrence before you can complete it. You can do this by typing the row
command RG on the MODIFYING OCCURRENCES IN THE CURRENT PLAN panel, or the HANDLING OPERATIONS ENDED
IN ERROR panel. Alternatively, you can erase the group ID field on the MODIFYING AN OCCURRENCE IN THE CURRENT
PLAN panel.
|
|
|
|
This message can be issued also when you try to complete the last uncompleted operation of an occurrence
belonging to a group. It is issued because the completion of an operation would imply the completion of the
occurrence; however, TME 10 OPC does not allow manual completion of this kind of occurrence before the
occurrence has been removed from the group.
EQQM342E OCCURRENCE IS NOT A MEMBER OF AN OCCURRENCE GROUP
Explanation: The occurrence does not belong to an occurrence group.
System action: The request is rejected.
User response: None.
EQQM343E THE APPLICATION IS NOT A MEMBER OF AN APPLICATION GROUP
Explanation: The application does not belong to an application group.
System action: The request is rejected.
User response: None.
192
TME 10 OPC Messages and Codes
EQQM344W Ÿ EQQM351I
EQQM344W THE APPLICATION IS A MEMBER OF A GROUP. CONSIDER ADDING THE OTHER MEMBERS
Explanation: The application is a member of an application group. This message is issued as a reminder in case
you should also add the other members of the same group to the current plan.
System action: Normal processing continues.
User response: If applicable, create occurrences in the current plan for the other applications in the same group.
EQQM345E ONE OR MORE OCCURRENCES ARE IN USE.
Explanation: One or more of the applications could not be added because another user is adding the same
application to the current plan with the same input arrival date and time. InUse is displayed in the list to indicate the
failing occurrence.
System action: The system waits for you to respond.
User response: Check that Group ID, and Input arrival date and time have been specified correctly. Or, check with
the other user who is creating the same occurrence to determine which of the occurrences should be added.
Alternatilvely, the occurrence can be deleted from the list with the row command D.
EQQM346E ONE OR MORE OCCURRENCES ALREADY EXISTS
Explanation: One or more of the applications could not be added because an occurrence for the same application
already exists in current plan. Exist is displayed in the list to indicate the failing occurrence.
System action: The system waits for you to respond.
User response: Check that Group ID, and Input arrival date and time have been specified correctly. The occurrence
can be deleted from the list with the row command D. Alternatively, the previously added occurrence can be deleted
from the current plan via the MCP dialog.
EQQM347E INSUFFICIENT AUTHORITY TO ADD ONE OR MORE APPLICATIONS
Explanation: One or more of the applications could not be added because the user has no current plan update
authority for the application names. NoAuth is displayed in the list to indicate the failing occurrence.
System action: The system waits for you to respond.
User response: Verify that Group ID has been correctly entered. Alternatively, the occurrence can be deleted from
the list with the row command D.
EQQM349E NO OCCURRENCES TO ADD, OR TERMINATING ERRORS FOUND
Explanation: There are no valid versions of any applications in the application description database for the date and
time specified by the input arrival, or TME 10 OPC has been unable to execute the request.
System action: The system waits for you to respond.
User response: Check that Group ID, and Input arrival date and time have been specified correctly.
EQQM350I ALL ADDED OCCURRENCES HAS BEEN SUCCESSFULLY RELEASED
Explanation: All occurrences in the group have been successfully released.
System action: The occurrences have been released.
User response: None.
EQQM351I ALL ADDED OCCURRENCES HAS BEEN SUCCESSFULLY DELETED
Explanation: The occurrences in the group have been successfully deleted from the current plan.
System action: The occurrences have been deleted from the current plan.
User response: None.
Chapter 16. EQQMnnn Messages
193
EQQM352E Ÿ EQQM357E
EQQM352E SOME ADDED OCCURRENCES COULD NOT BE RELEASED
Explanation: One or more of the applications added to the plan could not be released. Error is displayed in the list
to indicate the failing occurrence.
System action: The system waits for you to respond.
User response: See MLOG for possible error information. The occurrence can be deleted from the list with the row
command.
EQQM353E SOME ADDED OCCURRENCES COULD NOT BE DELETED
Explanation: One or more of the applications added to the plan could not be deleted from the current plan. Error is
displayed in the list to indicate the failing occurrence.
System action: The system waits for you to respond.
User response: See MLOG for possible error information. The occurrence can be deleted from the list with the row
command.
EQQM354I ALL SELECTED OCCURRENCES HAS BEEN SUCCESSFULLY ADDED
Explanation: All occurrences in the group have been successfully added to the current plan, the occurrences will be
held until released by the user.
System action: Processing continues.
User response: Modify the individual occurrences as required and release the group.
EQQM355E SOME SELECTED OCCURRENCES COULD NOT BE ADDED
Explanation: One or more of the occurrences defined in the group could not be added to the current plan. This can
happen because TME 10 OPC was unable to resolve the dependencies for the application.
System action: The occurrence group is added to the current plan, but not all of the occurrences were added.
Problem determination: The TME 10 OPC message log will contain messages which describe the reason why the
individual occurrences could not be added.
User response: The individual occurrences can be added to the plan as members of the existing group.
Alternatively, you can delete the entire occurrence group before the occurrences are released.
EQQM356E GROUP VALID-FROM DATE IS LATER THAN PLAN END MPLENDI
Explanation: The valid-from date of the group you attempted to add to the current plan lies outside the current plan
end.
System action: The request is rejected.
User response: Change the valid-from date of the group definition using the Application Description dialog.
EQQM357E NO VALID GROUP DEFINITION AVAILABLE
Explanation: You attempted to add a group of applications to the current plan but no valid version of the
corresponding group definition could be found.
Possible causes for this error are:
Ÿ The group definition has been deleted from the application description data base
Ÿ The user requesting the group add does not have security access to read the group definition
Ÿ An active group definition is not in effect for the specified input arrival date.
System action: The system waits for you to respond.
User response: Check why the group definition could not be found, correct the error and resubmit the request.
194
TME 10 OPC Messages and Codes
EQQM358W Ÿ EQQM366I
EQQM358W DEP LOOP DETECTED, NOT ALL DEPS RESOLVED WITHIN THE GROUP
Explanation: One or more dependency loops has been found in the occurrence group.
System action: In each loop, the external dependencies for one of the operations has not fully been resolved within
the group. If there are other occurrences, external to the group, in the current plan that matches these dependency
definitions, the dependencies have been resolved to those occurrences. Message EQQM976W is written to the
message log, once for each loop detected.
User response: Check the message log to identify occurrences and operations affected.
EQQM360W WHEN OPC/ESA CHECKED THE JCL IT FOUND JES3 DJC STATEMENTS
Explanation: Restarting this job may interfere with the JES3 dependent job control net.
System action: None.
User response: Verify that the restart does not affect the DJC net and/or change the JCL accordingly.
EQQM361I STATEMENT OVERRIDDEN DUE TO CONFLICT WITH ORIGINAL JCL
Explanation: The statement in the JCL has been modified by TME 10 OPC so that a replacement JCL statement
could be inserted. The original statement is changed to a JCL comment.
System action: Processing continues.
User response: Verify that the step restart selected is correct.
EQQM362E OPC/ESA DIDN'T INSERT COND AS ONE IS ALREADY PRESENT
Explanation: Restarting this operation is not possible due to a COND statement previously defined.
System action: None.
User response: Verify that existing COND statements are valid and amend the JCL accordingly.
EQQM364W A STEP LEVEL RESTART HAS ALREADY BEEN SELECTED FOR THE OPERATION
Explanation: A user has already set a restart step for this operation and the operation has not yet been restarted.
System action: Processing continues.
User response: Verify the step restart previously selected. Change it if necessary.
EQQM365E THE STATEMENT CONTAINS REFER BACK TO STEP PRIOR TO RESTART
Explanation: Restarting this job is not possible due to a refer back that specifies a step that is prior to a restart step.
This would cause a JCL error.
System action: None.
User response: Verify that the step to restart from is correct and amend the JCL accordingly.
EQQM366I STATEMENT FOLLOWS FROM STEP STEPNAME PROC STEP PROCNAME
Explanation: The inconsistency is highlighted by placing the JCL in ISPF note lines that are then preceded with the
proc and step name where the JCL statements were found.
System action: None.
User response: Verify that the data highlighted is in error and amend the JCL accordingly.
Chapter 16. EQQMnnn Messages
195
EQQM368E Ÿ EQQM374W
EQQM368E IF STATEMENT REFERS BACK TO STEP PRIOR TO RESTART STEP
Explanation: Restarting this job could result in unpredictable results as the IF statement refers to a step prior to a
restart step. JCL error.
System action: None.
User response: Verify that the step being referred to is correct and amend the JCL accordingly.
EQQM369E UNABLE TO OVERRIDE JCL AS IT IS IN A NESTED PROCEDURE
Explanation: Restarting this job is not possible as the JCL statement that needs to be overridden is within a nested
procedure.
System action: None.
User response: Update the procedure manually for the duration of this job.
EQQM370W THE JOBLOG FOR THIS OPERATION IS NOT COMPLETE
Explanation: The JESJCL and JESYSMSG joblog files are needed to define a step-level restart. One or both of
these files are missing, and TME 10 OPC cannot rebuild the JCL for step-level restart.
System action: None.
User response: Use the JOB primary command to view the part of the joblog that is present (if any), and use the J
row command in the previous operation list panel to update the JCL accordingly.
EQQM371W THE STATEMENT CONTAINS A DATASET WITH DISPOSITION MOD
Explanation: The JCL statement contains a DISP=MOD for a dataset. This restart may corrupt the contents of this
dataset.
System action: None.
User response: Verify if the step was executed or not. If it was not, ignore this message. If it was executed, verify
that a restart is possible, or change the JCL accordingly.
EQQM372E THE STATEMENT CONTAINS A REFERENCE TO A TEMPORARY DATASET
Explanation: The JCL statement contains a reference to a temporary dataset name that was created in a previous
step. Restarting this job will cause a JCL error.
System action: None.
User response: Change the JCL accordingly.
EQQM373W STEP STATUS IS FLUSH. POSSIBLE INCONSISTENCIES EXIST
Explanation: This step has a status of FLUSH due to a prior error. Restarting from this step may be possible;
however, verification of the JCL for the status of datasets is recommended.
System action: None.
User response: Change the JCL if necessary.
EQQM374W STEP EXECUTION CONDITION TO A PREVIOUS STEP
Explanation: The JCL statement contains a condition statement that refers to a previous step. Restarting this job
could cause steps to be executed that are not supposed to be executed.
System action: None.
User response: Change the COND/IF keyword accordingly if necessary
196
TME 10 OPC Messages and Codes
EQQM375I Ÿ EQQM380W
EQQM375I OPC WILL ATTEMPT TO DELETE THIS DATASET
Explanation: TME 10 OPC will attempt to delete this dataset before this job is restarted.
System action: None.
User response: None.
EQQM376I OPC WILL ATTEMPT TO UNCATALOG THIS DATASET
Explanation: TME 10 OPC will attempt to uncatalog this dataset before this job is restarted.
System action: None.
User response: None.
EQQM377I OPC WILL ATTEMPT TO CATALOG THIS DATASET
Explanation: TME 10 OPC will attempt to catalog this dataset before this job is restarted.
System action: None.
User response: None.
| EQQM378W VERIFY JCL: OPC COULD DELETE WRONG DATASET (IEF377I)
| Explanation: The JCL statement contains a DCB reference to a dataset name that has been referenced by an
| IEF377I message in the joblog. Restarting the job may cause problems as TME 10 OPC will delete only the
| cataloged data sets, and not those that have just been allocated and not cataloged.
| System action: None.
| User response: Change if this could lead to problems, and, if so, remove the involved data sets from the data set
| list suggested by TME 10 OPC for deletion. Then manually make any changes required or alter the JCL if necessary.
EQQM379W THE JCL STATEMENTS CONTAIN AUTOMATIC RECOVERY STATEMENTS
Explanation: TME 10 OPC has found automatic recovery statements in the JCL. Restarting the job without
changing or removing the automatic recovery statements may lead to unpredictable results.
System action: None.
User response: Verify the TME 10 OPC automatic recovery statements. Remove them if necessary.
EQQM380W THE JCL CONTAINS REFERENCES TO INSTREAM DATA THAT IS MISSING
Explanation: The JCL statement contains a reference to instream data that cannot be located. This can occur
because:
Ÿ An error was reported when TME 10 OPC submitted the operation which prevented the JCL from being stored in
the JCL repository.
Ÿ The JCL for this operation has been deleted from the JCL repository.
Ÿ The operation was not submitted by TME 10 OPC and the corresponding data is not available in the JES job log.
Ÿ The data is missing from one of the following; a DD * or DD DATA reference, a JES XMIT or DATASET
statement, or a PASSWORD= keyword on the job card.
System action: Processing continues.
User response: Enter any required instream data.
Chapter 16. EQQMnnn Messages
197
EQQM381I Ÿ EQQM387W
EQQM381I OPC/ESA HAS FOUND NO INCONSISTENCIES IN THE JCL FOR A RESTART
Explanation: TME 10 OPC has investigated the JCL for restart, and has found no errors. The operation may be
restarted.
System action: None.
User response: Leave the panel with END command to save the JCL and initiate catalog management for the
operation, cancel the restart using the CANCEL command, or edit the JCL using JCL primary command.
EQQM382W THE OPERATION CANNOT BE RESTARTED WITHOUT CHANGING THE JCL
Explanation: TME 10 OPC has investigated the JCL for restart, and has found errors. Use the JCL primary to
determine whether JCL updates are required
System action: The system waits for you to respond.
User response: Either edit and change the JCL, or cancel the restart of the operation.
EQQM383E THE ABSOLUTE GDG NUMBER IS MISSING FOR THIS DATASET
Explanation: TME 10 OPC was unable to find the absolute GDG number for the dataset.
System action: None.
User response: Check to ensure that the GDG base exists, and that the GDG level has not been deleted or that the
dataset has not been filtered out by a user exit.
EQQM384W THE RESTART STEP IS INSIDE AN IF/THEN/ELSE CLAUSE
Explanation: Unpredictable results may occur when the selected restart step is within an IF-THEN-ELSE clause.
System action: None.
User response: Check to ensure that the step selected is the correct step and that the IF-THEN-ELSE clause is
understood.
EQQM385E NUMBER OF STEPS FOUND IN THE JOB LOG INCONSISTENT
Explanation: The number of steps found in the job log is not consistent with the number of steps reported by the
tracker when the job ended.
System action: Processing continues.
User response: Contact your system programmer.
System programmer response: Keep a copy of the event dataset from the tracker where the job executed, the
current plan, and the JCL repository, and contact your IBM representative.
EQQM386W THE GDG BASE IS MISSING FOR THIS DATASET
Explanation: TME 10 OPC was unable to find the GDG base for the dataset at job submit time.
System action: None.
User response: Check to ensure that the GDG name is defined correctly. The GDG may be created during the life
time of the job so this may not be an error.
EQQM387W CM ACTION FOR THIS JOB IS OCHCNO SO GDG CANNOT BE RESOLVED
Explanation: The job to be rerun contains GDG datasets but catalog management action for the operation is none.
The absolute GDG value is missing therefore missing and the GDG dataset cannot be resolved.
System action: The JCL is presented to the user with the GDG dataset specification unchanged.
User response: Change the DD statement manually. When using steplevel restart for operations containing GDG
datasets the catalog management action should be set to D or Y (D is recommended).
198
TME 10 OPC Messages and Codes
EQQM388W Ÿ EQQM392E
| EQQM388W VERIFY JCL FOR POSSIBLE INCONSISTENCIES
| Explanation: One of the following situations has occurred:
|
|
Ÿ At least one step staus of FLUSH was detected. Restarting from this step may be possible; however verification
for the status of datasets used in this step is recommended.
|
|
Ÿ At least one IEF377I message was found in the joblog. This means that in the previous run the job successfully
allocated the data set, but did not manage to catalog it.
| System action: None.
|
|
|
|
System programmer response: Change the JCL if necessary. If flushed steps have been detected then
EQQM373W messages will show which ones they are. If there are catalog problems, then EQQM378W messages
will indicate which data sets are involved. See the description for EQQM378W for details on what action should be
taken.
EQQM390I OPC/ESA NEEDS A JOBLOG TO PROCESS THE COMMAND. IT HAS BEEN REQUESTED
Explanation: You have tried to make a catalog management request or browse-joblog request on an TME 10 OPC
system activated for step-level restart and where the needed joblogs will be retrieved at the time of your request.
TME 10 OPC has requested the tracker to retrieve the joblog.
System action: The panel will be redisplayed with this information message.
User response: Wait for the request to complete. Check the joblog-retrieval Status field or wait to get a
TSO-broadcast that the request has Completed. Then reenter your dialog request.
System programmer response: None.
EQQM391I A JOBLOG IS NEEDED TO PROCESS THE COMMAND. IT IS NOT YET RETRIEVED
Explanation: You have tried to make a catalog management or browse-joblog request on an TME 10 OPC system
activated for step-level restart and where the required joblogs will be retrieved at the time of your request. TME 10
OPC has initiated a request to the tracker to retrieve the job log but the request has not yet been processed.
System action: The panel will be redisplayed with this information message.
User response: Wait for the request to complete. Check the joblog-retrieval Status field or wait to get a
TSO-broadcast that the request has Completed. Then reenter your dialog request.
System programmer response: None.
EQQM392E A JOBLOG IS NEEDED TO PROCESS THE COMMAND. COULD NOT BE RETRIEVED
Explanation: You have tried to make a catalog management or browse-joblog request on an TME 10 OPC system
activated for step-level restart and where the required joblogs will be retrieved at the time of your request. TME 10
OPC has initiated a request to the tracker but has received an error return code from the tracker attempting retrieval
of the job log.
System action: If you requested Catalog Management actions or Restart and TME 10 OPC has collected dataset
information, the dataset list panel will be displayed with this error message, rather than the expected Step list panel. If
you requested Browse-Joblog nothing will be displayed.
User response: TME 10 OPC can not perform step-level restart for this job and you can not browse the joblog.
Contact your system programmer to find out why the joblog could not be retrieved.
System programmer response: The TME 10 OPC tracker has not been able to retrieve the SYSOUT for this job.
The tracker tries to retrieve it either by reading held SYSOUT or by calling the joblog-retrieval user exit. Check the
value of the JOBLOGRETRIEVAL keyword. There will be messages in the tracker message log, EQQMLOG, that
help to further diagnose the problem.
Chapter 16. EQQMnnn Messages
199
EQQM393E Ÿ EQQM398W
EQQM393E CATALOG MANAGEMENT IS ONLY ALLOWED FOR OPERATIONS RUNNING ON MVS
Explanation: You have tried to make a catalog management step-level restart request, a joblog has been found but
the joblog is created on a non-MVS platform.
System action: The panel will be redisplayed with this error message.
User response: You will not be able to perform catalog management for this job. Use browse-joblog command to
browse the joblog, or edit the data in the JS-file ("JCL Edit") and resubmit the job to the non-MVS platform.
EQQM394E SELECTED END-STEP MUST BE AFTER SELECTED START-STEP
Explanation: You have tried to make a catalog management step-level restart request with a restart scope, that is a
start- plus end-step for the restart. This is not allowed.
System action: The panel will be redisplayed with this error message.
User response: Correct your definition, that is either specify a new end-step that lies after the start-step or remove
the end-step line-command.
EQQM395E A JOBLOG IS NEEDED TO PROCESS THE COMMAND BUT WAS NOT FOUND
Explanation: You have tried to make a catalog management or browse-joblog request on an TME 10 OPC system
activated for step-level restart. A joblog could not be located for the operation.
System action: If you requested Catalog Management actions or Restart and TME 10 OPC has collected dataset
information, the dataset list panel will be displayed with this error message (rather than the expected Step list panel).
If you requested Browse-Joblog nothing will be displayed.
User response: TME 10 OPC can not perform step-level restart for this job and you can not browse the joblog.
Contact your system programmer to find out why the joblog could not be accessed.
System programmer response: Check if JOBLOGRETRIEVAL(IMMEDIATE) was specified and the job contained
no catalog updates. (IMMEDIATEALL is required to guarantee always to find a joblog, or the STORELOG keyword in
the controller must be set to ALL). Check if the joblog was specified in a class that catalog management is requested
to check. If you are using the archiver interface, check that the archiver still has the SYSOUT for the job. If it does
check the logic of EQQUX010.
EQQM396E EXCLUDE SELECTION COMMAND(S) OUTSIDE RESTART SCOPE
Explanation: You have defined one or more exclude-step row commands (X = Exclude a step from restart) and at
least one of the excluded steps is either before the Start-selection or after the End-selection.
System action: The panel will be redisplayed with this error message.
User response: Correct your definitions by moving the exclude commands inside the Start-End restart scope.
EQQM397E SELECTED STEPS CHANGED - REBUILD JCL
Explanation: You have selected, or excluded, steps without issuing the GO command to build JCL according to the
selected/excluded steps.
System action: The panel will be redisplayed with this error message.
User response: Change the selections, issue the GO command for the current selection, or CANCEL the step restart.
EQQM398W NO STEPS HAVE BEEN SELECTED FOR THIS STEP RESTART
Explanation: You have attempted a step restart without selecting a restart step, or an end step.
System action: If you confirm the restart TME 10 OPC will perform dataset cleanup for the entire job and the
current JCL will be resubmitted without modification.
User response: Either accept the restart with the current JCL or cancel the step level restart on the step-restart
confirmation panel.
200
TME 10 OPC Messages and Codes
EQQM399W Ÿ EQQM403E
EQQM399W CM ACTION SPECIFIED FOR THIS JOB IS OCHCNO
Explanation: The job to be rerun contains GDG datasets but catalog management action for the operation is none.
The absolute GDG value is missing therefore missing and the GDG dataset cannot be resolved.
System action: The JCL is presented to the user with the GDG dataset specification unchanged.
User response: Change the DD statement manually. When using steplevel restart for operations containing GDG
datasets the catalog management action should be set to D or Y (D is recommended).
EQQM400W THE OPERATION HAS NOT BEEN SELECTED FOR RESTART
Explanation: To use the row command just entered, the operation must have been selected previously for restart.
System action: None.
User response: Enter the S (select) row command to select the operation for restart, then enter one of the other
history row commands.
EQQM401W THE DB2 HISTORY DATABASE IS NOT AVAILABLE
Explanation: The database that holds the operation data for old occurrences is not available. Possible reasons are:
|
Ÿ The database has been stopped or abended.
Ÿ The table space holding the data has been closed.
Ÿ The name specified in the DB2SYSTEM keyword in not correct.
System action: DB2 diagnostic messages are written to the TME 10 OPC EQQMLOG dataset.
User response: Contact your system programmer.
System programmer response: Check the EQQMLOG dataset for DB2 messages and take the actions described in
DB2 documentation.
EQQM402W THE OPC/ESA SUBSYSTEM IS NOT CONNECTED TO A DB2 HISTORY DATABASE
Explanation: When processing the request, TME 10 OPC found that:
Ÿ The DB2 system specified in the DB2SYS keyword in the OPCOPTS initialization statement could not be
connected or,
Ÿ the OPERHISTORY keyword was not specified in the OPCOPTS statement.
System action: If TME 10 OPC tried to connect to a DB2 system, DB2 diagnostic messages are written to the
TME 10 OPC EQQMLOG dataset.
User response: Contact your system programmer.
System programmer response: Check the EQQMLOG for DB2 messages and take the actions described in DB2
documentation.
EQQM403E COULD NOT RETRIEVE REQUIRED DATA. DB2 RETURN CODE IS DB2RC
Explanation: TME 10 OPC tried to access data in the DB2 history database but failed to do so. The resulting DB2
messages are written to the TME 10 OPC EQQMLOG dataset. The return code is the sqlcode returned by DB2.
System action: DB2 diagnostic messages are written to the EQQMLOG dataset.
User response: Contact your system programmer.
System programmer response: Check the EQQMLOG dataset for DB2 messages and take the action described in
the DB2 documentation.
Chapter 16. EQQMnnn Messages
201
EQQM404I Ÿ EQQM910E
EQQM404I THE JOB FOR THIS OPERATION MIGHT NOT BE THE ORIGINAL JOB
Explanation: No job for this operation was found in the history database. This job was copied from the EQQJBLIB
file.
System action: Processing continues.
User response: Verify if the job needs to be changed before it is submitted.
EQQM405W THE HISTORY FUNCTION IS NOT ACTIVE
Explanation: You tried to retrieve operations from the history database but the history function is not active on your
TME 10 OPC subsystem.
System action: Processing continues.
User response: Contact your system programmer.
System programmer response: The OPERHISTORY and DB2SYSTEM keywords must be specified on the
BATCHOPTS or OPCOPTS statement to activate the history function. Refer to TME 10 OPC documentation for more
information.
| EQQM406W OCCURRENCE NOT FOUND (OCC) or operation not found (OPER)
| Explanation: The data selected could not be found in the DB2 history database. Either the occurrence is missing
| (OCC is set to x) or the operation record is missing (OPER is set to x). The data may have been deleted after the list
| of occurrences was created.
| System action: The system waits for you to respond.
| User response: Return to the previous panel and re-create the list of occurrences.
| System programmer response: If the problem recurs when the list has been re-created, analyze the messages in
| the TME 10 OPC message log, to determine the cause of the error. If there are no messages, contact your IBM
| representative.
EQQM900E INVALID SUBSYSTEM REQUEST.
SEE EQQDUMP DATA SET
Explanation: Validation of data has failed.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Contact your IBM representative. The dataset in the dialog users EQQDUMP DD
statement contains a snap dump of the attempted request. This is needed for diagnostics.
EQQM910E USER USER NOT AUTHORIZED TO ACCESS RESOURCE: RESOURCE
Explanation: A modify-current-plan request attempted to access the resource RESOURCE, but the user making the
request was not authorized to access the resource.
System action: The request is rejected.
System programmer response: None.
202
TME 10 OPC Messages and Codes
EQQM911E Ÿ EQQM915E
EQQM911E INVALID DEPENDENCY INFO FOR: APPL, OPER, PRED: PRED
Explanation: A modify-current-plan request failed because dependency data has been changed during the dialog
session. The request was attempted for application APPL and operation number OPER. The number of the
predecessor operation is PRED.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: The request contained a reference to a dependency that TME 10 OPC could not find, or
that was invalid. The operation and predecessor numbers are given in hexadecimal form. Use HEX ON when
browsing the TME 10 OPC message log.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM912E INVALID DEPENDENCY PRED TO: APPL, OPER
Explanation: A modify-current-plan request failed because dependency data has been changed during the dialog
session. The application for which the request was attempted is APPL and the operation number is OPER. The
number of the predecessor operation is PRED.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: The request contained a reference to a dependency that TME 10 OPC could not find, or
that was invalid. The operation and predecessor numbers are given in hexadecimal form. Use HEX ON when
browsing the TME 10 OPC message log.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to you IBM representative.
EQQM913E INVALID OPERATION DETAIL REQUEST DETAILED REQUEST: MTD TOTAL REQUEST: MT0
Explanation: A modify-current-plan request failed because the detailed information for an operation update was
invalid.
The failing requests are printed in hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM027E is issued to the dialog user.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it.
EQQM914E REQUEST TO DELETE OPERATION THAT DOES NOT EXIST OPERATION: APPL, IA, OPER
Explanation: A modify-current-plan request to delete an operation failed because the requested operation did not
exist in the occurrence.
The application ID, input arrival date and time, and operation number are listed.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM915E DELETION OF OPERATION OPER IN APPL SPLITS NETWORK
Explanation: A modify-current-plan request to delete an operation failed because the deletion would have split the
occurrence network. The operation to be deleted is identified as application ID APPL and operation number OPER.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
Chapter 16. EQQMnnn Messages
203
EQQM916E Ÿ EQQM920E
EQQM916E REQUEST TO ADD SPECIAL RESOURCE THAT ALREADY EXISTS OPERATION
SPECIAL RESOURCE: SPR
: APPL, OPER
Explanation: A modify-current-plan request to add a special resource failed because the the requested special
resource already exists in the operation. The application ID and operation number are listed together with the special
resource name.
System action: The request is rejected and message EQQM025E is displayed to the dialog user.
User response: Check that the correct special resources are defined for the operation.
EQQM917E TOO MANY PREDECESSORS FOR APPL, OPER
Explanation: A modify-current-plan request would generate too many predecessors to the operation. The operation
for which the request is made is identified as application ID APPL and operation number OPER.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session. The operation
number is given in hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM918E TOO MANY SUCCESSORS FOR APPL, OPER
Explanation: A modify-current-plan request would generate too many successors to an operation. The operation for
which the request is made is identified as application ID APPL and operation number OPER.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session. The operation
number is given in hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM919E PREDECESSOR IS ALSO SUCCESSOR PREDECESSOR: PREDA, PREDO SUCCESSOR : SUCCA,
SUCCO
Explanation: A modify-current-plan request would have caused a loop in the network.
The application IDs and operation number are listed. The operation numbers are given in hexadecimal form. Use
HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM920E EXTERNAL DEPENDENCY ALREADY EXISTS APPLICATION: APPL
PREDECESSOR: PREDA
OPERATION: PREDO
OPERATION: OPER
Explanation: A modify-current-plan request attempted to add a dependency that already exists.
The application IDs and operation numbers are listed. The operation numbers are given in hexadecimal form. Use
HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
204
TME 10 OPC Messages and Codes
EQQM921E Ÿ EQQM925E
EQQM921E DELETE OF INTERNAL PREDECESSOR CONNECTION FAILED, REASON: RS APPLICATION:
APPL, IA, OPERATION: OPER, DEPENDENCY: PREOP
Explanation: A request for current plan modification would result in an invalid occurrence. The following reason
codes (RS) indicate why:
921
922
923
The last internal dependency cannot be deleted.
The delete would have resulted in a split into two networks.
The predecessor specification is not found.
System action: The request is rejected and the requestor is notified of the error with a message.
Problem determination: The last line of the message identifies the occurrence and the internal dependency which
was to be deleted.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM922E REQUEST TO DELETE SPECIAL RESOURCE THAT DOES NOT EXIST OPERATION
OPER SPECIAL RESOURCE: SPR
: APPL,
Explanation: A modify-current-plan request to delete a special resource failed because the the requested special
resource does not exist in the operation. The application ID and operation number are listed together with the special
resource name.
System action: The request is rejected and message EQQM025E is displayed to the dialog user.
User response: Check that the correct special resources are defined for the operation.
EQQM923I JOBLOG FOR JOBN (JOBNUM) ARRIVED
Explanation: You have made a catalog management request or a browse-joblog request on an TME 10 OPC
system activated for step-level restart and where the required joblogs will be retrieved at the time of your request.
TME 10 OPC requested the tracker to retrieve the job log and SYSOUT has been returned to the controller,
System action: The message will be displayed as a TSO broadcast message to the requesting user at the first
interaction after the message is sent.
User response: You can now enter the Catalog Management dialog and make a step-level restart, or you can enter
a browse-joblog command.
EQQM924E INVALID REQUEST TO MCP - REQUEST FOLLOWS REQUEST
Explanation: A modify-current-plan request was invalid.
The request is given in hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM925E PRINT OPERATION HAS NO PREDECESSOR OPERATION: APPL, IA, OPER
Explanation: A modify-current-plan request would have caused a print operation to have no predecessors.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in
hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
Chapter 16. EQQMnnn Messages
205
EQQM926E Ÿ EQQM929W
EQQM926E PRINT OPERATION HAS MORE THAN 1 PREDECESSOR OPERATION: APPL, IA, OPER
Explanation: A modify-current-plan request would have caused a print operation to have more than one
predecessor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in
hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM927E PRINT OPERATION HAS NO CPU PREDECESSOR OPERATION: APPL, IA, OPER
Explanation: A modify-current-plan request would have caused a print operation to not have a computer operation
predecessor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in
hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM928E SETUP OPERATION HAS INVALID SUCCESSOR OPERATION: APPL, IA, OPER
Explanation: A modify-current-plan request would have caused a job setup operation to not have a valid computer
operation successor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in
hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM929W JOBLOG FOR JOBN (JOBNUM) NOT FOUND
Explanation: You have made a catalog management request or a browse-joblog request on an TME 10 OPC
system activated for step-level restart and where the required joblogs will be retrieved at the time of your request.
TME 10 OPC requested the tracker to retrieve the joblog, but the joblog could not be located.
System action: The message will be displayed as a TSO broadcast message to the requesting dialog user at the
first interaction after the message is sent out.
User response: Because no joblog was found, no step-level restart can be performed by TME 10 OPC If dataset
information exists, TME 10 OPC will display a dataset list for you that can be manually changed. If no dataset list
exists TME 10 OPC will accept a job-restart but will not change the JCL or make catalog updates. If you request
joblog browse, nothing will be displayed and an error message issued.
Check with your system programmer why the joblog could not be retrieved.
System programmer response: Check the tracker message log, EQQMLOG, for messages to help diagnose the
problem.
206
TME 10 OPC Messages and Codes
EQQM930E Ÿ EQQM933E
EQQM930E CP MAY BE DESTROYED DUE TO ERRORS DURING MCP UPDATE
Explanation: An error occurred while updating the current plan, causing it to be partially updated.
System action: Processing is terminated for the current request, and message EQQM025E is issued to the dialog
user.
Problem determination: Previous error messages in the TME 10 OPC message log contain additional information
about this error.
System programmer response: See message EQQM936E.
EQQM931W JOBLOG FOR JOBN (JOBNUM) IN ERROR
Explanation: You have made a catalog management or a browse-joblog request on an TME 10 OPC system
activated for step-level restart and where the required joblogs will be retrieved at the time of your request. TME 10
OPC requested the tracker to retrieve the joblog, but error return codes were issued when the tracker tried to retrieve
the joblog.
System action: The message will be displayed as a TSO broadcast message to the requesting dialog user at the
first interaction after the message is sent out.
User response: Because no joblog was found, no step-level restart can be performed by TME 10 OPC. If dataset
information exists, TME 10 OPC will display a dataset list for you that can be manually changed. If no dataset list
exists, TME 10 OPC will accept a job-restart but will not change the JCL or make catalog updates. If you request
joblog browse, nothing will be displayed and an error message issued.
Check with your system programmer why the joblog retrieval request returned an error code.
System programmer response: Check the tracker message log, EQQMLOG, for messages to help diagnose the
problem.
EQQM932E OPERATION OPNUM IS TOO LARGE - MCP UPDATE NOT POSSIBLE
Explanation: A modify-current-plan request was rejected because it would have caused a current plan record to
become larger than the maximum record size in the Current Plan data set.
System action: The Current Plan is not updated, and message EQQM164E is issued to the dialog user.
Problem determination: Determine if maximum record size of the Current Plan is smaller than recommended, or if
the failing operation contains too many special resources or too many dependencies.
System programmer response: If the maximum record size for the Current Plan is too small, reallocate the Current
Plan datasets with a bigger record size; stop TME 10 OPC; copy the Current Plan datasets; and then restart with the
new datasets.
If the failing operation contains many special resources or dependencies, simplify the definition of the operation and
retry the MCP request.
EQQM933E WORK STATION WSNAME NOT FOUND FOR OPERATION: APPL: APPL, IA, OPER
Explanation: A modify-current-plan request specifies an operation on a workstation (WSNAME) that is not defined to
the current plan.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in
hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: None.
Chapter 16. EQQMnnn Messages
207
EQQM934E Ÿ EQQM950E
EQQM934E JOBLOG FOR JOBN (JID) CANCELLED. REISSUE REQUEST
Explanation: You have made a catalog management or a browse-joblog request on an TME 10 OPC system
activated for step-level restart and where the required joblogs will be retrieved at the time of your request. TME 10
OPC has initiated the retrieval request but error return codes were issued by internal TME 10 OPC functions.
This message is normally issued when the communication between the controller and the tracker has resumed after a
failure. TME 10 OPC was unable to stack your request and asks you to reissue it.
System action: The message will be displayed as a TSO broadcast message to the requesting dialog user at the
first interaction after the message is sent out.
User response: Reissue the catalog management or browse joblog request.
EQQM935E WORK STATION WSNAME NOT FOUND IN WQA
Explanation: A modify-current-plan request attempts to update a workstation (WSNAME) that is not defined to the
current plan in the workstation queue area.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
System programmer response: None.
EQQM936E NORMAL MODE MANAGER WILL RESTART FROM CHECKPOINT
Explanation: A serious error related to the current plan dataset has occurred.
System action: The NMM subtask will restart and recreate the current plan dataset.
Problem determination: Use the TME 10 OPC message dataset to investigate the cause of the original error.
System programmer response: If the recovery procedure fails, that is, the NMM is unable to restart, TME 10 OPC
should be cancelled (not stopped). If the subsystem is stopped, the error will extend to the alternate current plan
dataset. If the recovery procedure is successful, TME 10 OPC normal processing can continue.
EQQM937E TURNOVER IN PROCESS AND OCCURRENCE HAS STATUS COMPLETE APPLICATION: APPL
Explanation: An attempt to modify an occurrence with status complete during a turnover has been rejected.
System action: The request is rejected, and either message EQQM027E or message EQQM028I is issued to the
dialog user.
User response: To rerun the occurrence or any of its operations, use the Modify Current Plan dialog to add a new
occurrence. This is necessary because TME 10 OPC will not copy a completed occurrence to the new current plan.
EQQM950E INPUT ARRIVAL NOT WITHIN CURRENT PLAN, ENDS CPE REQUEST
Explanation: A request to modify or create an occurrence on the current plan specifies an input arrival time later
than or equal to the current plan end time. All modifications to the current plan must be earlier than the current plan
end time. The request type is given by REQUEST.
System action: The request is terminated with an error return code.
Problem determination: This message should be followed by another message from the function requesting the
current plan modification.
User response: You may have to extend the current plan to get the failing function to work.
208
TME 10 OPC Messages and Codes
EQQM951E Ÿ EQQM954E
EQQM951E FAILED TO ADD APPLICATION ADID REASON: CANNOT READ CURRENT PLAN RECORD
Explanation: A request to create an occurrence on the current plan failed due to an I/O error.
System action: The request is terminated and the processing continues with the next request.
Problem determination: The message log contains the I/O error message.
User response: Resubmit the job when the problem causing the I/O error has been corrected.
System programmer response: Review the message log of the TME 10 OPC subsystem to determine the cause of
the error. If you cannot determine the cause and the error persists, contact your IBM representative.
EQQM952E FAILED TO ADD APPLICATION ADID REASON: NO UNIQUE INPUT ARRIVAL TIME LEFT IN CP
FOR THIS APPLICATION
Explanation: A request to create an occurrence on the current plan failed because the occurrence already exist. In
the request, no input arrival time was given, which implies that a default input arrival time should be selected. This
default is the current time, consisting of the current date, current hour, and current minute. If an occurrence of the
application with that input arrival time already exists, the next minute is used. If that occurrence also exists, the
following minute is used. This search for an input arrival time continues up to the current plan end time.
System action: The request is terminated and processing continues with the next request.
Problem determination: This message should be followed by another message from the function requesting the
current plan modification.
User response: You may have to extend the current plan to get the failing function to work.
EQQM953E FAILED TO ADD APPLICATION ADID REASON: 'ADD' TIME LATER THAN CURRENT PLAN END
TIME
Explanation: A request to create an occurrence on the current plan failed because the current plan end time has
passed. In the request, no input arrival time was given, which implies that a default input arrival time should be used.
This default is the current time, consisting of the current date, current hour, and current minute. The request is
rejected because the current plan ends before current time.
System action: The request is terminated and processing continues with the next request.
Problem determination: This message should be followed by another message from the function requesting the
current plan modification.
User response: You may have to extend the current plan to get the failing function to work.
EQQM954E FAILED TO ADD APPLICATION ADID NO ACTIVE VERSION OF THE APPLICATION DESCRIPTION
IN THE DATA BASE
Explanation: The TME 10 OPC subsystem has received a request to add an occurrence of application ADID to the
current plan. The application description in the EQQADDS file could not be read (record not found).
System action: The request to add the current plan occurrence is rejected.
Problem determination: If the attempt to add an application was caused by an ETT triggering event, check the ETT
triggering criteria. Make sure that the triggering event points to an active application description.
If the attempt to add an application was caused by a program interface request, check the application name given in
the program interface request.
User response: Correct the errors.
Chapter 16. EQQMnnn Messages
209
EQQM955E Ÿ EQQM971E
EQQM955E FAILED TO ADD APPLICATION ADID CAN NOT READ THE APPLICATION DESCRIPTION FILE
Explanation: The TME 10 OPC subsystem has received a request to add an occurrence of application ADID to the
current plan. The application description file was not open.
System action: The request to add the current plan occurrence is rejected.
Problem determination: The message log should contain a previous message giving the reason why the file is not
open.
User response: Review the message log, and correct any errors.
EQQM956E FAILED TO ADD/MODIFY APPLICATION ADID. OCCURRENCE WITH SAME APPLICATION ID AND
INPUT ARRIVAL EXISTS IN THE LONG-TERM PLAN
Explanation: A request to create or modify an occurrence in the current plan failed because the request specified an
application ID and input arrival date and time that are the same as an existing occurrence in the long-term plan.
System action: The request to create or modify the occurrence in the current plan is rejected.
User response: Change the input arrival date or time, and resubmit the request.
EQQM961E MODIFY CURRENT PLAN REQUEST FAILED, INSUFFICIENT STORAGE. REASON: RS
Explanation: A request to create or modify an occurrence on the current plan failed due to storage allocation failure.
The reason code provides debugging information.
System action: The request is terminated and processing continues with the next request.
Problem determination: This message should be followed by another message from the function requesting the
current plan modification.
System programmer response: Allocate a larger region to the TME 10 OPC subsystem and then restart the
subsystem. If the error persists, contact your IBM representative.
EQQM970W THE POTENTIAL PREDECESSOR RECORD FOR APPLICATION APPL COULD NOT BE UPDATED
THE MAXIMUM NUMBER (1000) OF POTENTIAL SUCCESSOR OPERATIONS HAS BEEN REACHED.
Explanation: The MCP service processor was unable to add any more successor operation entries to a potential
predecessor record. Since the record could not be updated as intended, it now does not define all potential
successors for application appl. If new occurrences of this application will be added by PIF programs or by the ETT
function it will no longer be possible to add all possible successor dependencies automatically.
System action: MCP continues processing the current add occurrence request.
Problem determination: This message indicates that very many different operations in different applications have
defined operations of one application as external predecessors. If the message is unexpected, review the contents of
the AD data base and remove old applications that are no longer used.
User response: When using the MCP dialog to add new occurrences of the application defined by this message the
DEP primary command should be used to verify that successor dependencies have been set up correctly.
EQQM971E FAILED TO ADD APPLICATION ADID. REQUESTING FUNCTION IS FUNC REASON: MAXIMUM
NUMBER OF OCCURRENCES OF THIS APPLICATION REACHED
Explanation: No more occurrences of this application can be added. TME 10 OPC can handle approximately 870
occurrences of each application.
FUNC is the function that requested the add:
E
A
D
Event-triggered tracking
Automatic recovery
Dialog
System action: The create request is rejected.
User response: Change the criteria for event-triggered tracking. Complete or delete occurrences of this application
that are no longer needed. These occurrences will be removed from the plan next time a new plan is produced.
210
TME 10 OPC Messages and Codes
EQQM972E Ÿ EQQM975E
EQQM972E MCP WAS UNABLE TO ADD APPLICATION APPL BECAUSE AN MCP CONTROL BLOCK (MT0)
COULD NOT CONTAIN ALL SUCCESSOR DEPENDENCIES TO APPLICATION SUCC
Explanation: The MCP service processor was unable to add any more successor dependencies to the MT0 block
that is used to define MCP processing. The maximum size of an MT0 block is 32768 bytes.
System action: MCP abandons the attempt to add current occurrence.
Problem determination: This message indicates that very many different operations in different applications have
defined operations in current application as external predecessors. If the message is unexpected, review the contents
of the AD data base and remove old predecessor definitions that should no longer be used.
User response: When using the MCP dialog to add new occurrences of the application defined by this message do
not request MCP to automatically add successor dependencies. The same recommendation applies if the occurrence
is being added as a result of ETT trigger processing or by a PIF program. Instead, add successor dependencies to
the occurrence after it has been added to the plan.
EQQM973I CATALOG MANAGEMENT HAS BEEN DISCARDED FOR THE FOLLOWING OPERATION: APPL:
APPL IA: IAD IAT OPERATION: OPER
Explanation: Changing status from Error to Complete indicates that no catalog management action is needed. The
operation had the catalog management attribute set to deferred.
System action: The action is flagged as discarded for the operation.
User response: None.
EQQM974I CATALOG MANAGEMENT ACTION HAS STARTED FOR THE FOLLOWING OPERATION: APPL:
APPL IA: IAD IAT OPERATION: OPER
Explanation: The catalog management action had already started when the status change request was done.
System action: The catalog management action continues until complete.The action statuses are set accordingly.
The operation status will be changed.
User response: None.
EQQM975E FAILED TO ADD APPLICATION ADID BECAUSE MAXIMUM NUMBER OF OCCURRENCES
REACHED. REQUESTING FUNCTION IS FUNC.
| Explanation: No more occurrences can be added to the Current Plan because the maximum number of
| occurrences—32767 or the number specified in the MAXOCCNUM option of the JTOPTS statement—has been
| reached. ADID identifies the application that failed to be added. FUNC identifies the function that requested the add,
and is one of the following:
A
D
E
P
Automatic Recovery
MCP dialog
Event Triggered Tracking
Program Interface
System action: The request is rejected.
Problem determination: If you use ETT, PIF, or Automatic Recovery, check that these functions are working
correctly. For example, make sure that you do not have an endless ETT loop, where the availability of a special
resource is set to YES by a job that ETT adds, when it detects that this same resource is set to YES. Check the
Current Plan for instances of an unusually high number of occurrences of a particular application. If you see such an
application, look in the application description data base and make sure that the run cycles for the application are
correct. When you specify PREVRES(YES) on the BATCHOPT initialization statement, information about completed
and deleted occurrences is carried forward, for reporting purposes, into a new Current Plan. If your Current Plan
regularly contains a large number of occurrences, and you specify YES for PREVRES, you should consider changing
this value to NO.
User response: Check that the Current Plan does not contain any occurrences that should not be in the plan. If you
find any such occurrences, complete or delete them. Replan the Current Plan to remove all completed and deleted
Chapter 16. EQQMnnn Messages
211
EQQM976W Ÿ EQQM991E
occurrences, and then try to add the occurrence again. If your current plan regularly contains a large number of
occurrences, you should consider shortening the length of the Current Plan in future daily planning runs.
EQQM976W ONE OR MORE OF THE EXTERNAL DEPENDENCIES OF OPER OPER IN APPLICATION ADID
WERE NOT RESOLVED WITHIN THE GROUP
Explanation: A dependency loops in an occurrence group has been detected and eliminated.
System action: At least one of the external dependencies for the operation has not been resolved within the group.
If there are other occurrences, external to the group, in the current plan that matches the operations dependency
definitions, the dependencies have been resolved to those occurrences. Message EQQM358W is issued to the dialog
user.
User response: Check how the dependencies have been resolved and modify if appropriate. The application
descriptions for this group should also be modified in order to avoid this situation.
EQQM990E MCP UPDATE FAILED.
FAILING MTD BELOW: MTD
Explanation: A modify-current-plan request failed because of an error.
The request is given in hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM027E is issued to the dialog user.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM991E ERROR DURING MCP UPDATE.
FAILING MODULE: MODULE
Explanation: A modify current plan request failed. If message EQQM027E is issued to the dialog user, EQQM991 is
followed by the another message which describes the actual error message reported by the modify current plan
module MODULE. If message EQQM028I is issued to the dialog user, no additional message appears.
System action: The request is rejected and either message EQQM027E or EQQM028I is issued to the dialog user.
System programmer response: If you report the error message following this message to your IBM representative.
The information in this message is also required by IBM to diagnose the error.
212
TME 10 OPC Messages and Codes
EQQN000I Ÿ EQQN003E
Chapter 17. EQQNnnn Messages
EQQN000I THE NORMAL MODE MANAGER TASK HAS BEEN REQUESTED TO TERMINATE
Explanation: The Normal Mode Manager has been requested to terminate processing. This request will be
propagated to all active subtasks. The Normal Mode Manager will start its own termination when all subtasks have
ended.
System action: The Normal Mode Manager waits for all subtasks to end. When there are no more active subtasks,
the Normal Mode Manager will back up the current plan dataset and terminate.
Problem determination: If the Normal Mode Manager has not ended within a few minutes, there may be a problem
in one of the subtasks that prevents it from ending normally. If the problem cannot be resolved, cancel the subsystem
started task and request a dump.
System programmer response: None.
EQQN001I REFRESH IS COMPLETE. CURRENT PLAN IS NO LONGER AVAILABLE
Explanation: A current plan refresh request has been processed by the NMM. The current plan dataset has been
closed and the checkpoint dataset has been updated to indicate that no current plan is available. All TME 10 OPC
functions that need access to the current plan dataset are inoperative.
System action: All TME 10 OPC functions that do not need access to the current plan continue processing.
TME 10 OPC administrator response: Schedule a batch job to create a new current plan using only long-term plan
information as input.
EQQN002E THE NMM TASK WAS UNABLE TO READ OR UPDATE CURRENT PLAN OPERATION RECORD
WITH KEY (HEXADECIMAL): F0F3OPRINDEX
Explanation: The NMM was reading the job tracking log dataset during restart from checkpoint, and met an error
accessing a current plan operation record while processing an automatic job recovery event.
System action: The current job tracking event record is not processed. The NMM continues reading the job tracking
log dataset.
Problem determination: Review the preceding messages in the TME 10 OPC message log and SYSLOG datasets
to determine the cause of the error.
System programmer response: Save the message log dataset containing this error message, and the job tracking
log dataset containing the incorrect record. Then contact your IBM representative.
EQQN003E VSAM ABENDED WHILE ATTEMPTING TO CLOSE DDNAME FILE. FOR ADDITIONAL
INFORMATION SEE SYSLOG MESSAGES AND DUMP DATA SET
Explanation: A severe error occurred while closing a VSAM file.
System action: A dump will be generated. The I/O subtask attempts to continue normal termination processing.
Problem determination: Review earlier messages in the TME 10 OPC message log, SYSLOG dataset, and the
dump dataset to determine what caused the close abend.
System programmer response: Save the TME 10 OPC message log and the dump datasets, then contact your
IBM representative.
 Copyright IBM Corp. 1991, 1998
213
EQQN004E Ÿ EQQN006E
EQQN004E VSAM PHYSICAL I/O ERROR. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK. LOAD
MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED
FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME VSAM RETURN CODE IS 12,
REASON CODE IS RSN, KEY IS KEY VSAM MESSAGE: SYNAD
Explanation: A TME 10 OPC subtask or batch job encountered an I/O error when accessing a VSAM dataset.
System action: The action taken by the TME 10 OPC subtask or batch job is given by additional messages that
follow this message in the TME 10 OPC message log. The VSAM message supplies information such as jobname,
stepname, unit address, device type, ddname, RBA, error description and so on.
Problem determination: The MSGAREA and MSGGEN parameters of the RPL macro are used to extract the
relevant information presented in the VSAM message. Use the VSAM return code, reason code, and message to
determine the cause of the error. For more information, refer to the appropriate documentation for the MVS/DFP
product installed on this MVS/ESA system.
System programmer response: Correct the errors and, if necessary, rerun the batch job or restart the TME 10
OPC subsystem.
EQQN005E THE NORMAL MODE MANAGER TASK HAS ABENDED. FOR ADDITIONAL INFORMATION SEE
SYSLOG MESSAGES AND DUMP DATA SET
Explanation: A severe error has occurred in the NMM task.
System action: NMM processing is terminated. A dump is created if a dump dataset is defined. Message
EQQZ045W is issued.
Problem determination: Review the preceding messages in the TME 10 OPC message log and SYSLOG datasets,
and the dump dataset to determine what caused the NMM to abend.
System programmer response: Save the message log dataset containing this error message, the dump dataset,
and the SYSLOG dataset. Then contact your IBM representative.
EQQN006E THE NORMAL MODE MANAGER HAS IGNORED THE FOLLOWING INVALID EVENT RECORD
WHILE PROCESSING THE JOB TRACKING LOG DATA SET DURING RESTART FROM
CHECKPOINT: EXITREC
Explanation: An invalid job tracking event record has been found in the job tracking log dataset. The most likely
error is that the last 4 bytes of the record do not contain the TME 10 OPC identifier EQQ3. It is also possible that the
first 3 characters of the job number field do not contain the character string JOB.
System action: The incorrect job tracking event record is not processed. The NMM continues reading the job
tracking log dataset.
TME 10 OPC administrator response: Note the job name and job number in the exit record. If necessary, set the
correct status for this job manually.
System programmer response: Save the TME 10 OPC message log dataset (EQQMLOG) containing this error
message, and the job tracking log dataset containing the incorrect record. Then contact your IBM representative.
214
TME 10 OPC Messages and Codes
EQQN007E Ÿ EQQN010E
EQQN007E THE FOLLOWING INVALID RECORD WAS ENCOUNTERED WHEN THE NORMAL MODE MANAGER
WAS PROCESSING THE JOB TRACKING LOG DATA SET DURING RESTART FROM CHECKPOINT:
EVENT HEADER: EVNTHDR EVENT RECORD: EXITREC
Explanation: An invalid job tracking event record has been found in the job tracking log dataset. The NMM could
not determine the origin of the event. Each event must come from one of 16 possible event datasets on each
TME 10 OPC node. In the current event record, either the event dataset number or the TME 10 OPC node number
is invalid.
System action: The incorrect job tracking event record is not processed. The NMM continues reading the job
tracking log dataset.
TME 10 OPC administrator response: Note the job name and the job number in the exit record. If necessary, set
the correct status for this job manually.
System programmer response: Save the TME 10 OPC message log dataset containing this error message, and
the job tracking log dataset containing the incorrect record. Then contact your IBM representative.
EQQN008E AN ABEND OCCURRED WHILE PROCESSING THE JOB TRACKING LOG DATA SET DURING
RESTART FROM CHECKPOINT. THE TRACKLOG RECORD HAS BEEN SKIPPED
Explanation: An abend prevented the NMM from finishing its processing of a job tracking event while it read the job
tracking log dataset.
System action: MVS recovery/termination is requested to generate a dump. The NMM attempts to continue normal
operation with the next event queued.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log dataset, and the dump
dataset to determine the cause of the error.
TME 10 OPC administrator response: Note the job name and the job number in the exit record. If necessary, set
the correct status for this job manually.
System programmer response: Save the TME 10 OPC message log dataset containing this error message, and
the job tracking log dataset containing the incorrect record. Then contact your IBM representative.
EQQN009E THE CHECKPOINT DATA SET, DDNAME EQQCKPT, COULD NOT BE OPENED
Explanation: The NMM could not open the checkpoint dataset, which is a required dataset for TME 10 OPC when
OPCHOST(YES) is specified.
System action: NMM initialization is terminated.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Check that ddname EQQCKPT is correctly specified and that the TME 10 OPC
started task is authorized to open the dataset for update. Correct the errors and restart the NMM.
EQQN010E AN I/O ERROR OCCURRED WHILE ATTEMPTING TO UPDATE THE CURRENT JOB TRACKING
LOG DATA SET. SYNAD MESSAGE FOLLOWS:
SYNMSG
FIRST 90 BYTES OF LOG RECORD FOLLOWS:
LOGREC
Explanation: An I/O error occurred when a TME 10 OPC function tried to write a log record to the currently active
job tracking log file.
System action: TME 10 OPC attempts to switch to the next job tracking log file. If this process is successful, the
log record will be written to the next log instead. The NMM subtask is posted to take a backup of the current plan.
TME 10 OPC administrator response: Contact your system programmer.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product
installed on this MVS/ESA system.
Chapter 17. EQQNnnn Messages
215
EQQN011E Ÿ EQQN016I
System programmer response: Scratch and reallocate the job tracking log data set at a suitable moment when
TME 10 OPC is stopped.
EQQN011E A SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE
CURRENT JOB TRACKING LOG DATA SET
Explanation: An abend occurred when an TME 10 OPC function attempted to write a record to the current job
tracking log dataset. If the abend code is SB37 or SD37, then the current job tracking log dataset is too small.
System action: TME 10 OPC attempts to switch to the next job tracking log file. If this process is successful, the
log record will be written to the next log instead. The NMM subtask is posted to take a backup of the current plan.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: If current job tracking log dataset is too small scratch the current data set and
allocate a larger one at a suitable moment when TME 10 OPC is stopped. Instructions can be found in TME 10 OPC
Customization and Tuning.
EQQN012I OPC/ESA JOB TRACKING EVENTS ARE NOW BEING LOGGED ON FILE DDNAME
Explanation: The NMM subtask has switched to the next available job tracking log dataset. This is done after every
current plan backup. If dual logging is requested, the dual log dataset will also switch to the next available dataset.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN013I OPC/ESA JOB TRACKING IS NOW ACTIVE AND CURRENT PLAN DD-NAME IS DDNAME
Explanation: The NMM subtask has started successfully and there is a current plan available.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN014I THE JOB TRACKING LOG DATA SET, DDNAME JTFILE, HAS BEEN USED TO UPDATE THE
CURRENT PLAN. NUMBER EVENTS HAVE BEEN APPLIED TO DD-NAME DDNAME
Explanation: The NMM determined that the current plan dataset could not be used. A new current plan has been
created by starting from the old current plan and reprocessing events logged on the job tracking log dataset.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN015I A VSAM DATA SET WAS SUCCESSFULLY COPIED: FROMDD=FROMDD, TODD=TODD
Explanation: A TME 10 OPC subtask has finished copying a VSAM dataset to a backup dataset.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN016I DDNAME OF CURRENT JCL REPOSITORY DATA SET IS DDNAME
Explanation: The JCL repository dataset name in use after a copy is DDNAME.
System action: TME 10 OPC processing continues.
User response: None.
216
TME 10 OPC Messages and Codes
EQQN017I Ÿ EQQN022I
EQQN017I THE JCL REPOSITORY DATA SET WILL BE COPIED
Explanation: A TME 10 OPC subtask has started to copy the JCL repository dataset because the current one has
reached its maximum size, or because a backup has been requested using the BACKUP TSO command for the JS
resource.
System action: TME 10 OPC processing continues.
User response: None.
EQQN018I VSAM LSR BUFFERS HAVE BEEN SUCCESSFULLY ALLOCATED FOR VSAM FILE DDNAME
NUMBER OF INDEX BUFFERS ARE NINDEX WITH SIZE SINDEX
NUMBER OF DATA BUFFERS ARE NDATA WITH SIZE SDATA
Explanation: A VSAM LSR buffer pool has been successfully built for the file allocated to DDNAME. This message
documents the size of the buffer pool, and can be issued for either EQQCPxDS or EQQTBxDS.
System action: TME 10 OPC continues and will use the new buffer pool for I/O to the file.
Problem determination: If necessary, verify that the size of the buffer pool is reasonable.
System programmer response: None.
EQQN019W VSAM LSR BUFFER ALLOCATION FAILED FOR VSAM FILE DDNAME RETURN CODE FROM
BLDVRP WAS VRPRC REQUESTED NUMBER OF INDEX BUFFERS WAS NINDEX WITH SIZE
SINDEX REQUESTED NUMBER OF DATA BUFFERS WAS NDATA WITH SIZE SDATA
Explanation: TME 10 OPC was unable to build a VSAM LSR buffer pool for the file identified by DDNAME. This
message documents the size of the buffer pool that TME 10 OPC was trying to build and the return code from the
build buffer pool service. The message can be issued for either EQQCPxDS or EQQTBxDS.
System action: TME 10 OPC continues and will use normal VSAM buffering techniques for the file.
Problem determination: Use the VSAM return code to determine the cause of the error. For more information, refer
to the appropriate documentation for the MVS/DFP product installed on this MVS/ESA system.
System programmer response: Correct the error, then restart TME 10 OPC.
EQQN021E VSAM FILE FILE COULD NOT BE COPIED BECAUSE INPUT OR OUTPUT DATA SET COULD NOT
BE OPENED
Explanation: The NMM could not copy the specified file because an error occurred when opening the input or output
datasets.
System action:
The NMM is terminated.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message.
System programmer response: Correct the errors and, if necessary, restart the NMM.
EQQN022I A CURRPLAN(NEW) RESTART REQUEST IS BEING PROCESSED. OPC/ESA WILL START FROM
THE NEW CURRENT PLAN DATA SET, DDNAME=EQQNCPDS, AND APPLY EVENTS FROM THE
ARCHIVED JT LOG DATA SET, DDNAME=EQQJTARC
Explanation: TME 10 OPC will recreate a current plan by copying the new current plan dataset, EQQNCPDS, and
update it using events from the archived job tracking log and from the current job tracking log dataset.
System action: The TME 10 OPC restart process continues.
User response: None.
Chapter 17. EQQNnnn Messages
217
EQQN023I Ÿ EQQN026W
EQQN023I VSAM LSR BUFFERS HAVE BEEN SUCCESSFULLY DELETED FOR VSAM FILE DDNAME
Explanation: TME 10 OPC successfully deleted the buffer pool for the file indicated in the message.
System action: None.
User response: None.
EQQN024W VSAM LSR BUFFER DELETE FAILED FOR VSAM FILE DDNAME RETURN CODE FROM DLVRP
WAS VRPRC
Explanation: TME 10 OPC could not delete the buffer pool for the file indicated in the message.
System action: None.
Problem determination: Use the VSAM return code to determine the cause of the error. For more information, refer
to the appropriate documentation for the MVS/DFP product installed on this MVS/ESA system.
User response: Use the return code to determine the cause of the error, and take appropriate action.
EQQN025E AN ERROR OCCURRED WHILE READING THE JOB TRACKING LOG DATA SET DURING RESTART
FROM CHECKPOINT. THE DATA SET HAS BEEN TRUNCATED
Explanation: The NMM was reading the job tracking log dataset during restart from checkpoint. An abend
prevented it from processing the entire dataset.
System action: MVS recovery/termination is requested to generate a dump. The NMM tries to complete the restart
by treating the error as an end-of-file on the log dataset.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log dataset, and the dump
dataset to determine the cause of the error.
TME 10 OPC administrator response: Review the status of all operations in the current plan. If necessary, set the
correct statuses manually.
System programmer response: Save the message log dataset containing this error message, and the job tracking
log dataset causing the error. Then, contact your IBM representative.
EQQN026W A NEW CURRENT PLAN (NCP) HAS BEEN REJECTED
Explanation: TME 10 OPC has detected that a new current plan (NCP) has been created by a daily plan batch job,
but because TME 10 OPC failed to create a valid backup of the current plan (CP) to be used as input for the batch
job, the NCP is considered bad and will not be used. This message is also issued when the checkpoint dataset
(EQQCKPT) has not been initialized.
System action: TME 10 OPC starts up with the CP that was in use before TME 10 OPC was terminated. If the
EQQCKPT dataset has been reallocated, TME 10 OPC will not permit current plan actions as the old CP cannot
accurately be identified.
Problem determination: Review the message log from the previous TME 10 OPC startup and look for error
messages that could explain why the backup process failed. If the TME 10 OPC backup process failed due to an
open error, the reason could be that another job was using the file.
System programmer response: Ensure that both the CP1 and CP2 data sets are online and available for TME 10
OPC. Rerun the daily plan batch job, to create a new NCP.
If the EQQCKPT dataset has been reallocated specify the JTOPTS keyword CURRPLAN(NEW) option and restart the
TME 10 OPC subsystem.
218
TME 10 OPC Messages and Codes
EQQN027E Ÿ EQQN031E
EQQN027E The Normal Mode Manager is terminating unexpectedly. NMMSTAT is NMMSTAT
Explanation: The Normal Mode Manager is in the process of terminating unexpectedly. The reason for the
termination is documented by NMMSTAT, which can have the following values:
E
A
S
An I/O error has occurred
Virtual storage is exhausted
Termination requested by another TME 10 OPC function.
System action: NMM will terminate all related subtasks. TME 10 OPC will continue to execute, but when the NMM
subtask has terminated current plan functions are not available.
Problem determination: Review the TME 10 OPC message log (EQQMLOG) for preceding error messages which
describe the problem.
User response: Contact your system programmer.
System programmer response: Analyze the preceding messages and take appropriate action to prevent NMM from
terminating. To activate NMM again, issue F ssnm,S=NMM.
EQQN028E CANNOT COPY VSAM FILE INFILE TO FILE FILE MAXIMUM OUTPUT RECORD SIZE IS SMALLER
THAN MAXIMUM INPUT RECORD SIZE
Explanation: The NMM has been requested to copy the specified file but was unable to do so because the
maximum size of records in the output dataset is smaller than the maximum size of records in the input dataset.
System action: The NMM is terminated. Message EQQZ045W is issued.
System programmer response: Reallocate the output dataset so that it has the same maximum record length as
the input dataset. Then try again.
EQQN029E CANNOT COPY VSAM FILE FILE. BUFFER GETMAIN FAILED
Explanation: The NMM has been requested to copy the specified file but is unable to do so because of insufficient
virtual storage.
System action: The NMM subtask is terminated. Message EQQZ045W is issued.
System programmer response: Stop TME 10 OPC, and restart it in a larger region.
EQQN030E ERROR COPYING VSAM FILE. DDNAME = DDNAME, VSAM RC = RC, REASON = RSN
Explanation: The NMM has been requested to copy the VSAM dataset DDNAME but is unable to do so because a
logical VSAM error occurred.
System action: The VSAM copy process is stopped.
Problem determination: Use the VSAM return code and reason code to determine the cause of the error. For more
information, refer to the appropriate documentation for the MVS/DFP product installed on this MVS/ESA system.
System programmer response: Correct the errors and, if necessary, restart the NMM.
EQQN031E I/O ERROR COPYING VSAM FILE. DDNAME = DDNAME, VSAM MSG FOLLOWS ERRMSG
Explanation: The NMM has been requested to copy the VSAM dataset DDNAME but cannot do so because a
VSAM I/O error occurred.
System action: The VSAM copy process is stopped.
Problem determination: Use the VSAM error message to determine the cause of the error. For more information,
refer to the appropriate documentation for the MVS/DFP product installed on this MVS/ESA system.
System programmer response: Correct the errors and, if necessary, restart the NMM.
Chapter 17. EQQNnnn Messages
219
EQQN032E Ÿ EQQN038E
EQQN032E UNABLE TO OPEN OPC/ESA VSAM FILE FILE, VSAM RC = RC, REASON = RSN
Explanation: The TME 10 OPC subsystem or a TME 10 OPC batch job could not open a VSAM dataset.
System action: The messages that follow this message in the message log identify the action taken by the
subsystem or the batch job.
Problem determination: Use the VSAM return code and reason code to determine the cause of the error. For more
information, refer to the appropriate documentation for the MVS/DFP product installed on this MVS/ESA system.
System programmer response: Correct the error, and restart the TME 10 OPC subsystem or batch job.
EQQN033E OPC/ESA VSAM FILE FILE IS INVALIDLY DEFINED
Explanation: After opening a VSAM dataset (FILE), the VSAM I/O subtask determined that the dataset’s attributes
did not agree with the I/O subtask’s expectations for this ddname. For example, an incorrect size of the VSAM key
could cause this message.
System action: The VSAM file is not opened.
Problem determination: Check that the file is correctly specified in the TME 10 OPC started task procedure. Use
the IDCAMS LISTCAT function to determine the attributes of the file. Check that the relative key position is zero and
that the key size is the same as that defined in TME 10 OPC Installation Guide.
System programmer response: Correct the errors, then restart TME 10 OPC.
EQQN034E DAILY PLAN ENDS AFTER FAILURE TO BUILD VSAM LSR POOL, MACRO BLDVRP FAILED WITH
RC=RCODE FOR DDNAME=DDNAME
Explanation: When building a VSAM LSR pool for the file DDNAME, the return code RCODE from BLDVRP macro
indicated that the pool had not been built.
System action: The Daily Plan job is ended without creating a New Current Plan.
Problem determination: For return code = 0008 the request could not complete due to lack of Virtual Storage. The
Daily Plan JOB allocates 100 times 32K VSAM LSR buffers, for the New current plan VSAM file, above 16 M. For
other return codes this is probably a system error.
System programmer response: For return code 0008 make sure that enough virtual storage is available. Review
the REGION parameter in conjunction with the limits in IEALIMIT/IEFUSI exit. Rerun the daily planning job.
For other return codes save the Message log containing the error and contact your IBM representative.
EQQN035I REFRESH REQUEST ISSUED BY tsouser
Explanation: The TSO user tsouser issued an LTP refresh request.
System action: TME 10 OPC processing continues.
System programmer response: None.
EQQN038E OPC/ESA DID NOT GET ENOUGH STORAGE TO BUILD THE TABLE TABLE
Explanation: TME 10 OPC tried to allocate storage to build the specified table but was not able to obtain sufficient
storage.
System action: TME 10 OPC initialization terminates.
System programmer response: Check the region size defined in the TME 10 OPC JCL procedure. Increase the
region size and restart TME 10 OPC.
220
TME 10 OPC Messages and Codes
EQQN043E Ÿ EQQN047W
EQQN043E UNSUCCESSFUL VSAM I/O REQUEST. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS
TASK. LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET
REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME VSAM RETURN
CODE IS 8, REASON CODE IS RSN, KEY IS KEY HEXADECIMAL ZONES HEXKEYZ
HEXADECIMAL DIGITS HEXKEYD
Explanation: A TME 10 OPC subtask encountered an unexpected error when accessing a VSAM dataset.
System action: The messages that follow this message in the TME 10 OPC message log indicate the action taken
by the TME 10 OPC subtask.
Problem determination: If this error condition cannot be reproduced, consider activating a VSAM I/O trace to check
preceding VSAM requests that led up to the error. Note that activating an I/O trace will cause a large amount of
output on the message dataset.
System programmer response: Correct the error and, if necessary, restart the subtask that encountered the error.
EQQN044I A VSAM I/O REQUEST COMPLETED SUCCESSFULLY. DETAILED INFORMATION FOLLOWS:
ACTIVE TASK IS TASK. LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET
+OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME KEY OF
HEXKEYZ HEXADECIMAL DIGITS HEXKEYD
VSAM RECORD IS KEY HEXADECIMAL ZONES
Explanation: This message is issued for all successful VSAM requests in the TME 10 OPC address space when
VSAM I/O tracing is active.
System action: TME 10 OPC processing continues.
System programmer response: None.
EQQN045E INCORRECT VSAM I/O REQUEST. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS TASK.
LOAD MODULE IS MODULE I/O REQUEST IS FROM MODID AT OFFSET +OFFSET REQUESTED
FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME ERROR CAUSE IS: CAUSE
Explanation: A TME 10 OPC subtask or batch job requested VSAM I/O services incorrectly.
System action: The messages that follow this message in the TME 10 OPC message log indicate the action taken
by the TME 10 OPC subtask or batch job.
System programmer response: If necessary, contact your IBM representative.
EQQN046I A LOGICAL VSAM FILE OPERATION WAS COMPLETED. DETAILED INFORMATION FOLLOWS:
ACTIVE TASK IS TASK. LOAD MODULE IS MODULE REQUEST IS FROM MODID AT OFFSET
+OFFSET REQUESTED FUNCTION IS FUNC ON LOGICAL FILE FILE, DDNAME DDNAME
Explanation: This message is issued for all logical VSAM requests in the TME 10 OPC address space when VSAM
I/O tracing is active.
System action: TME 10 OPC processing continues.
System programmer response: None.
EQQN047W OPC/ESA SUBTASK TASK HAS TERMINATED WITHOUT CLOSING LOGICAL FILE FILE, DDNAME
DDNAME. VSAM MAY BE UNABLE TO CLOSE THIS FILE
Explanation: This message is issued by the VSAM I/O subtask during TME 10 OPC termination when a TME 10
OPC subtask ends without closing all of the logical VSAM files that it opened.
System action: The I/O subtask attempts to close the VSAM file.
Problem determination: This message usually indicates that the subtask has terminated abnormally.
System programmer response: Contact your IBM representative.
Chapter 17. EQQNnnn Messages
221
EQQN049I Ÿ EQQN052W
EQQN049I EXCLUSIVE CONTROL VSAM ERROR, RETCODE 8, REASON CODE 0020, WAS CAUSED BY A
RESOURCE CONFLICT WITH OPC/ESA SUBTASK TASK
Explanation: This message contains additional information for a preceding EQQN043E message. It identifies the
TME 10 OPC subtask that has exclusive control of a VSAM control interval that the current TME 10 OPC subtask
needs.
System action: TME 10 OPC processing continues.
System programmer response: Save the TME 10 OPC message log dataset containing this message, then contact
your IBM representative.
EQQN050E A JOB TRACKING LOG DATA SET, DDNAME DDNAME, COULD NOT BE OPENED
Explanation: The normal mode manager could not open the job tracking log dataset DDNAME, which it requires.
System action: The normal mode manager is terminated. Message EQQN107I is issued.
Problem determination: Check that ddname DDNAME is correctly specified and that the TME 10 OPC started task
is authorized to open the dataset for output.
System programmer response: Correct the errors, then restart TME 10 OPC.
EQQN051I A CURRENT PLAN BACKUP PROCESS HAS STARTED. TRIGGER WAS: REASON
Explanation: The normal mode manager has begun updating a current plan dataset in preparation for the creation of
a current plan image copy backup. The reason why TME 10 OPC has initiated the backup is identified by the
REASON defined in the message text. The possible values for REASON are:
BACKUP LIM
The number of events specified in the JTOPTS BACKUP keyword has been reached
BACKUP CMD
The backup was initiated as a result of the TME 10 OPC BACKUP command
CATCH UP
TME 10 OPC has successfully recovered the current plan using job-tracking data
JT ERROR
An error on a job-tracking log has caused TME 10 OPC to switch to the next available JT log
NMM ENDING
The TME 10 OPC controller has been requested to shutdown, or the NMM task has been
requested to stop
DP START
Daily plan turnover phase 1, a daily plan batch extend, replan, trial, or print current period results
process has been started
DP END
Daily plan turnover phase 2, a daily plan extend or replan has created a new current plan which is
being taken over by TME 10 OPC
UNKNOWN
Please take a copy of the EQQJTARC and the EQQMLOG datasets, and report to your IBM
representative.
System action: TME 10 OPC backup processing continues. Current plan activity is suspended until the backup is
complete.
User response: None.
EQQN052W AN OUTSTANDING MCP MODIFY REQUEST HAS BEEN CANCELLED FOR USER USER
REASON IS: REASON. LIST OF AFFECTED OCCURRENCES FOLLOW:
Explanation: An MCP multiple add request did not complete normally. TME 10 OPC has cancelled the wait for the
completing modify request. Operations within such added occurrences may be in held status and must be released
manually.
System action: The wait for the modify request has been cancelled.
User response: Respond as for message EQQX146.
222
TME 10 OPC Messages and Codes
EQQN053W Ÿ EQQN070E
EQQN053W OCCURRENCE occid WITH IA iadate iatime MAY CONTAIN HELD OPERATIONS.
Explanation: An MCP multiple add request did not complete normally. TME 10 OPC has cancelled the wait for the
completing modify request. Operations within the reported occurrence may be in held status and must be released
manually.
System action: The wait for the modify request has been cancelled.
User response: Respond as for message EQQX146.
EQQN056I A CURRENT PLAN COPY PROCESS HAS STARTED
Explanation: The NMM has started to copy a current plan dataset, either because a new current plan has become
available, or because a current plan image copy backup is to be created.
System action: TME 10 OPC processing continues.
System programmer response: None.
EQQN057I A CURRENT PLAN DATA SET WAS SUCCESSFULLY COPIED: FROMDD=FROMDD, TODD=TODD
Explanation: The NMM has finished copying a current plan dataset.
System action: TME 10 OPC processing continues.
System programmer response: None.
EQQN060E INVALID KEYVAL KEYWORD VALUE POSITION IN THE KEYWORD KEYWORD
Explanation: Keyword KEYWORD on the JTOPTS statement contains a valid value KEYVAL, but in an incorrect
position.
System action: The normal mode manager (NMM) terminates.
System programmer response: Correct the error and restart the NMM subtask or the TME 10 OPC subsystem.
Refer to the TME 10 OPC Customization and Tuning for a description of the keyword.
EQQN061E TOO MANY KEYWORD VALUES IN THE KEYWORD KEYWORD
Explanation: Keyword KEYWORD on the JTOPTS statement contains too many values.
System action: The normal mode manager (NMM) terminates.
System programmer response: Correct the error and restart the NMM subtask or the TME 10 OPC subsystem.
Refer to the TME 10 OPC Customization and Tuning for a description of the keyword.
EQQN062E The KEYWORD KEYWORD CONTAINS UNKNOWN KEYWORD VALUE KEYVAL
Explanation: Keyword KEYWORD on the JTOPTS statement contains a value KEYVAL, which is not recognized by
TME 10 OPC.
System action: The normal mode manager (NMM) terminates.
System programmer response: Correct the error and restart the NMM subtask or the TME 10 OPC subsystem.
Refer to the TME 10 OPC Customization and Tuning for a description of the keyword.
EQQN070E KEYVALUE IS NOT A VALID KEYWORD VALUE
Explanation: An invalid keyword value has been defined.
System action: TME 10 OPC uses the default keyword value.
Problem determination: Contact your TME 10 OPC administrator.
TME 10 OPC administrator response: Correct the value for the keyword containing the error and restart TME 10
OPC.
Chapter 17. EQQNnnn Messages
223
EQQN071E Ÿ EQQN083E
EQQN071E AN ATTEMPT TO UPDATE THE NOERROR TABLE HAS FAILED
Explanation: A modify command was entered requesting the noerror table to be updated. One or more errors were
found while processing input NOERROR statements.
System action: The NOERROR table is not changed. TME 10 OPC continues normal processing.
User response: Review earlier error messages in the message log that describe initialization statement processing
errors. Correct all identified errors and reenter the modify command.
EQQN072I THE NOERROR TABLE HAS BEEN SUCCESSFULLY UPDATED.
Explanation: A modify command has caused TME 10 OPC to rebuild the NOERROR table from NOERROR
statements in the parameter library.
System action: TME 10 OPC continues normal processing and is using the updated NOERROR table.
User response: None.
EQQN080I THE LOG ARCHIVER TASK HAS STARTED
Explanation: The Job Tracking Log Archiver task has completed initialization and is ready to perform additional
work.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN081I THE LOG ARCHIVER TASK HAS ENDED
Explanation: The Job Tracking Log Archiver task is ending normally after having been posted to stop processing.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN082E NEXT JOB TRACKING LOG DATA SET, DDNAME DDNAME, IS NOT OPEN
Explanation: TME 10 OPC was unable to use the next job tracking log in a situation where current job tracking log
can no longer be used.
System action: The Normal Mode Manager subtask is stopped and the current plan is no longer available.
Problem determination: Review earlier messages in the message log data set to determine why the next job
tracking log is not open.
User response: Contact your system programmer.
System programmer response: Stop TME 10 OPC. Ensure that TME 10 OPC is authorized to update all job
tracking log data sets defined by currently specified (or defaulted) values of the JTLOGS and DUAL keywords of the
JTOPTS initialization statement. Reallocate any job tracking log data sets that had output errors. After making
necessary corrections, restart TME 10 OPC.
EQQN083E THE JTLOGS KEYWORD MUST SPECIFY A VALUE IN THE RANGE 2 TO 99
Explanation: The value specified for the JTLOGS keyword is not supported.
System action: The Normal Mode Manager subtask terminates.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Correct the JTLOGS specification and then restart TME 10 OPC.
224
TME 10 OPC Messages and Codes
EQQN084E Ÿ EQQN087E
EQQN084E DD STATEMENT IS MISSING FOR A JOB TRACKING LOG DATASET,
DDNAME DDNAME
Explanation: A DD statement needed to support currently specified (or defaulted) values of the JTLOGS and DUAL
keywords of the JTOPTS initialization statement is not defined.
System action: The Normal Mode Manager subtask terminates.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Either change the value defined by the JTLOGS or DUAL keyword or add the
ddname defined by this message to the TME 10 OPC started task procedure. After making the necessary
corrections, restart TME 10 OPC.
EQQN085E UNSUPPORTED ATTEMPT TO REDUCE THE NUMBER OF JOB TRACKING LOGS.
JTLOGS VALUE IS MAXJT, CURRENT JOB TRACKING LOG IS CURJT
Explanation: The value specified for the JTLOGS keyword of the JTOPTS initialization statement is smaller than the
number of the current job tracking log. This is not supported.
System action: The Normal Mode Manager subtask terminates.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Change the JTLOGS specification to a larger value. After making necessary
corrections, restart TME 10 OPC.
EQQN086E UNSUPPORTED ATTEMPT TO REDUCE THE NUMBER OF JOB TRACKING LOGS.
JTLOGS VALUE IS MAXJT, LAST ARCHIVED LOG IS ARCJT
Explanation: The value specified for the JTLOGS keyword of the JTOPTS initialization statement is smaller than the
number of the first not archived job tracking log. This is not supported.
System action: The Normal Mode Manager subtask terminates.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Change the JTLOGS specification to a larger value. After making necessary
corrections, restart TME 10 OPC.
EQQN087E DUAL JOB TRACKING LOG CONTAINS MORE EVENTS THAN PRIMARY JOB TRACKING LOG.
CURRENT JOB TRACKING LOG, DDNAME DDNAME MAY BE INVALID
Explanation: During TME 10 OPC restart it was determined that the dual job tracking log contains more events that
the primary log. This could indicate that the primary log data set is invalid.
System action: The Normal Mode Manager subtask terminates.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: If the primary log data set is in fact invalid, copy the dual log to the primary log. If
instead the dual log data set is invalid, copy the primary log to the dual log. After making necessary corrections,
restart TME 10 OPC.
Chapter 17. EQQNnnn Messages
225
EQQN088E Ÿ EQQN092E
EQQN088E NMM WAS UNABLE TO SWITCH TO NEXT JOB TRACKING LOG DATA SET,
DDNAME DDNAME, BECAUSE IT HAS NOT YET BEEN ARCHIVED.
Explanation: TME 10 OPC was unable to use the next job tracking log in a situation where current job tracking log
can no longer be used.
System action: The Normal Mode Manager subtask is stopped and the current plan is no longer available.
Problem determination: Review earlier messages in the message log data set to determine why the next job
tracking log has not been archived.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Stop TME 10 OPC. Ensure that TME 10 OPC is authorized to update all job
tracking log data sets defined by currently specified (or defaulted) values of the JTLOGS and DUAL keywords of the
JTOPTS initialization statement. Reallocate any job tracking log data sets that had output errors. After making
necessary corrections, restart TME 10 OPC.
EQQN090I THE JOB TRACKING LOG DATA SET DEFINED BY DDNAME DDNAME HAS BEEN COPIED TO THE
JOB TRACKING LOG ARCHIVE DATA SET
Explanation: The Job Tracking Log Archiver task has successfully copied a data set to the archive data set.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN091I THE LOG ARCHIVER TASK WAS UNABLE TO COPY THE DATA SET DEFINED BY DDNAME
DDNAME TO THE JOB TRACKING LOG ARCHIVE DATA SET
Explanation: An error prevented the Job Tracking Log Archiver task from copying a job tracking log data set to the
archive data set.
System action: The Job Tracking Log Archiver task terminates. The current plan updating tasks continue but if the
Log Archiver task problem is not corrected, TME 10 OPC will eventually run out of available job tracking log data sets.
Problem determination: Review earlier messages in the message log data set to determine what prevented the Log
Archiver task from copying current log data set.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Stop TME 10 OPC. Ensure that TME 10 OPC is authorized to read all job
tracking log data sets defined by currently specified (or defaulted) values of the JTLOGS and DUAL keywords of the
JTOPTS initialization statement. Reallocate any job tracking log data sets that had output errors. After making
necessary corrections, restart TME 10 OPC.
EQQN092E AN I/O ERROR OCCURRED WHILE ATTEMPTING TO UPDATE THE JOB TRACKING LOG ARCHIVE
DATA SET. THE ARCHIVER TASK IS ENDING. SYNAD MESSAGE FOLLOWS: SYNMSG
Explanation: An I/O error occurred when the JT log archiver task tried to write a log record to the job tracking
archive log data set.
System action: The JT log archiver task ends. The current plan updating tasks continue but if the JT log archiver
task problem is not corrected, TME 10 OPC will eventually run out of available job tracking log data sets.
TME 10 OPC administrator response: Contact your system programmer.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate decoumentation for the MVS/DFP product
installed on this MVS/ESA system.
System programmer response: Stop TME 10 OPC. If necessary, allocate a new job tracking log archive data set
and copy the old data set to the new data set. After making corrections, restart TME 10 OPC.
226
TME 10 OPC Messages and Codes
EQQN093E Ÿ EQQN101E
EQQN093E AN SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE THE
JOB TRACKING LOG ARCHIVE DATA SET. THE ARCHIVER TASK IS ENDING.
Explanation: An abend occurred when the JT log archiver task tried to write a log record to the job tracking archive
log data set. If the abend code is SB37 or SD37, then the archive dataset is too small.
System action: The JT log archiver task ends. The current plan updating tasks continue but if the JT log archiver
task problem is not corrected, TME 10 OPC will eventually run out of available job tracking log data sets.
Problem determination: Use the abend code to determine what is wrong with the archive data set.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Stop TME 10 OPC. If necessary, allocate a new larger job tracking log archive
data set and copy the old data set to the new data set. After making corrections, restart TME 10 OPC.
EQQN094E AN I/O ERROR OCCURRED WHILE ATTEMPTING TO UPDATE A DUAL JOB TRACKING LOG DATA
SET. SYNAD MESSAGE FOLLOWS:
SYNMSG
Explanation: An I/O error occurred when a TME 10 OPC function tried to write a log record to the currently active
dual job tracking log file.
System action: TME 10 OPC stops logging events to the dual job tracking log data sets. Logging on the primary
job tracking log data sets continues normally.
User response: Contact your system programmer.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product
installed on this MVS/ESA system.
System programmer response: Scratch and reallocate the failing data set at a suitable time when TME 10 OPC is
stopped.
EQQN095E A SEVERE ERROR, SYSTEM ABEND ABEND, OCCURRED WHILE ATTEMPTING TO UPDATE
CURRENT DUAL JOB TRACKING LOG DATA SET
Explanation: An abend occurred when an TME 10 OPC function attempted to write a record to a dual job tracking
log dataset. If the abend code is SB37 or SD37, then the current dual job tracking log dataset is too small.
System action: TME 10 OPC stops logging events to the dual job tracking log data sets. Logging on the primary
job tracking log data sets continues normally.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: If current job tracking log dataset is too small scratch the current dual log data set
and allocate a larger one at a suitable moment when TME 10 OPC is stopped.
EQQN101E THE OPC/ESA MODIFY CURRENT PLAN MODULE, EQQMCTOP, COULD NOT BE LOADED
Explanation: TME 10 OPC could not locate the modify current plan load module EQQMCTOP.
System action: NMM initialization fails.
System programmer response: Make sure that the EQQMCTOP load module is present in a library that can be
reached by TME 10 OPC, then restart the normal mode manager.
Chapter 17. EQQNnnn Messages
227
EQQN102W Ÿ EQQN108E
EQQN102W AN OPC/ESA USER EXIT LOAD MODULE, MODULE, COULD NOT BE LOADED
Explanation: TME 10 OPC could not locate an exit load module.
System action: This exit will not be used by TME 10 OPC.
Problem determination: Check if the module named in this message should be used by TME 10 OPC. Also check
that the module exists in a library that the subsystem started task can reach.
System programmer response: Correct the error, and restart the TME 10 OPC subsystem.
EQQN103E THE OPC/ESA EVENT HANDLER MODULE, EQQEMEVH, COULD NOT BE LOADED
Explanation: TME 10 OPC could not locate the event handler load module EQQEMEVH.
System action: TME 10 OPC initialization fails.
System programmer response: Make sure that the EQQEMEVH load module exists in a library that can be
reached by TME 10 OPC, then restart the TME 10 OPC started task.
EQQN105W NO VALID CURRENT PLAN EXISTS. CURRENT PLAN VSAM I/O IS NOT POSSIBLE
Explanation: The TME 10 OPC checkpoint dataset indicates that no valid current plan exists. All TME 10 OPC
functions that need access to the current plan dataset are inoperative.
System action: The NMM, which has been initialized, takes a new current plan if one is created by a daily plan
create batch job executing on behalf of this subsystem.
Problem determination: If this message was not expected, check that the started task procedure ddname
(EQQCKPT) is correctly specified. Also check that this subsystem is the only TME 10 OPC subsystem that
references this checkpoint dataset.
System programmer response: Correct the errors and, if necessary, restart the NMM.
EQQN106E ERRORS ENCOUNTERED PROCESSING NMM INITIALIZATION STATEMENTS. THE NORMAL
MODE MANAGER TASK WILL TERMINATE
Explanation: The Normal Mode Manager task found at least one error, while processing initialization statements.
System action: Normal Mode Manager initialization fails.
Problem determination: Review the previous messages in the message log dataset to determine the cause of the
problem.
System programmer response: Correct the error, and restart the TME 10 OPC subsystem.
EQQN107I THE NORMAL MODE MANAGER TASK HAS ENDED
Explanation: The Normal Mode Manager task is ending normally after having initialized successfully. Usually, this
message is due to an operator command requesting the TME 10 OPC subsystem to stop.
System action: Normal TME 10 OPC processing continues.
System programmer response: None.
EQQN108E THE NEW CURRENT PLAN DATA SET IS INVALID. A NEW NCP DATA SET MUST BE CREATED.
Explanation: The NMM task found that a new current plan in the NCP data set did not contain any header record.
System action: NMM will not use the contents of the NCP data set.
Problem determination: If a daily planing batch job has just ended check ending conditions for the job. If the error
occurs when TME 10 OPC is starting, verify that the DD statement defining the NCP file is correct, EQQNCPDS.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: If necessary, correct errors in the daily planning input data sets and rerun the daily
planning batch job, or, correct the NCP file definition problems and restart TME 10 OPC.
228
TME 10 OPC Messages and Codes
EQQO001I Ÿ EQQO006E
Chapter 18. EQQOnnn Messages
EQQO001I APPC TASK INITIALIZATION IS COMPLETE
Explanation: The APPC task has completed initialization processing.
System action: Processing continues.
Operator response: None.
EQQO002E APPC TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT APP
Explanation: An abend prevented the APPC task from processing a queue element.
System action: MVS recovery/termination is requested to generate a dump. The APPC task attempts to continue
normal processing.
Problem determination: Review the TME 10 OPC message log dataset, EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Save the MLOG, dump, and EQQDUMP datasets and contact your IBM
representative.
EQQO003E APPC TASK INITIALIZATION FAILED - XCF FAILURE
Explanation: The APPC task has ended due to an XCF failure or request denied by XCF
System action: The APPC task is not started.
Operator response: None.
System programmer response: Ensure the XCF destination names are defined correctly, restart the APPC task
when XCF is available.
EQQO004E APPC TASK INITIALIZATION FAILED - APPC/MVS FAILURE
Explanation: The APPC task has ended due to APPC/MVS failure
System action: The APPC task is not started.
Operator response: Restart the APPC/MVS address space before starting the TME 10 OPC APPC subtask.
EQQO005I INITIALIZATION FAILED - SUBSYSTEM STOP REQUESTED
Explanation: A stop subsystem command was issued while the APPC task was initializing. This caused the subtask
to end.
System action: The TME 10 OPC subsystem continues the shutdown sequence
Operator response: None.
EQQO006E APPC TASK TERMINATED - MVS/APPC SHUTTING DOWN
Explanation: The APPC task has ended due to APPC/MVS ending. All active conversations have been lost.
System action: The APPC task is shutdown.
Operator response: When APPC/MVS is available again, restart the TME 10 OPC APPC subtask.
 Copyright IBM Corp. 1991, 1998
229
EQQO007E Ÿ EQQO011E
EQQO007E THE APPC TASK IGNORED THE FOLLOWING ELEMENT ON THE APPC QUEUE DQE
Explanation: An invalid allocate request, or outbound reply was found on the APPC queue.
System action: Processing continues.
System programmer response: If the element was an allocate request from a user written TP, verify the code in
the TP, otherwise contact your IBM representative.
EQQO008E THE APPC TASK IGNORED THE FOLLOWING INBOUND APPC BUFFER APP
Explanation: An invalid buffer was received.
System action: Processing continues.
System programmer response: If the element was an inbound request buffer from a user written TP, verify the
format of the send buffer in the ATP, otherwise contact your IBM representative.
EQQO009E APPC TASK QUEUE POINTERS ARE DESTROYED, APPQ IS LOST
Explanation: The APPC task abended while processing elements on APPQ because the queue chaining is invalid.
System action: MVS recovery/termination is requested to generate a dump. The APPC task attempts to continue
normal processing.
Problem determination: Review the TME 10 OPC message log dataset. the EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Save the MLOG, dump, and EQQDUMP datasets and contact your IBM
representative.
EQQO010E AN APPC FUNCTION HAS BEEN REQUESTED BUT THE LEVEL OF THE MVS SYSTEM IS NOT
MVS/SP4.2.2 OR HIGHER
Explanation: TME 10 OPC attempted to initialize APPC services, but due to the wrong operating system level, the
attempt failed.
System action: TME 10 OPC continues to initialize without APPC support.
Problem determination: Review the TME 10 OPC initialization statement.
TME 10 OPC administrator response: Remove (or set to NO) the APPCTASK initialization statement.
EQQO011E APPC/MVS INTERFACE MODULE COULD NOT BE LOADED
Explanation: An APPC/MVS interface module was not found in the library search path.
System action: TME 10 OPC continues, but the appc functions as requested by the APPCTASK keyword are
disabled.
System programmer response: Ensure that the APPC/MVS modules is accessible and start TME 10 OPC again.
230
TME 10 OPC Messages and Codes
EQQPH00I Ÿ EQQPH06E
Chapter 19. EQQPnnn Messages
EQQPH00I SERVER TASK HAS STARTED
Explanation: The Server task has started successfully. This task is started by the Server Started task. It is started
by the TME 10 OPC subsystem if APPC(YES) is specified in the OPCOPTS initialization statement.
System action: TME 10 OPC continues processing.
EQQPH01I SERVER TASK ENDED
Explanation: The Server task has been requested to stop and is ending normally.
System action: TME 10 OPC continues processing.
EQQPH02E SERVER NAME IS ALREADY ACTIVE, IT CANNOT START AGAIN
Explanation: An operator START command has been entered for an TME 10 OPC server that is already active.
System action: The second attempt to invoke the server will terminate.
System programmer response: If you want to restart the TME 10 OPC server, first stop it, and then issue the
START command.
EQQPH03I AN ELEMENT ON THE APPC/MVS QUEUE IS OF UNRECOGNIZED TYPE: ELEM
Explanation: TME 10 OPC receives APPC/MVS requests, for example Allocate requests, on the APPC/MVS queue.
The queue element presented in the message is not supported by the server task.
System action: The queue element is deleted from the APPC/MVS queue. It causes no further action.
System programmer response: The message variable ELEM gives dignostics which is expecially useful if there are
other indications on an error in the TME 10 OPC server APPC/MVS communication.
EQQPH05E BUFFER CONTAINS WRONG AMOUNT OF INPUT DATA, OR WRONG VALUES
Explanation: The communication routines of the TME 10 OPC server APPC/MVS receives data for processing by
the server. The buffer of data is validated and does not pass the validation.
System action: The server deallocates the APPC/MVS conversation. The contact between the TME 10 OPC
dialog, or program interface application, and the TME 10 OPC subsystem is thereby broken. The partner of the
APPC/MVS conversation, a dialog user or a program interface application, is informed about the error by message
EQQPH14E and an error return code. An TME 10 OPC dialog user gets message EQQPH14 displayed at the next
terminal action. A program interface application gets message EQQPH14E written to the message log of the program
interface job, and the EQQYCOM call ends with return code 8.
User response: Follow the actions described for message EQQPH14E. If the problem reoccurs, report the error to
your IBM representative.
EQQPH06E A SERVER SUBTASK ABENDED. THE SUBTASK WAS CREATED FOR PROCESSING APPC/MVS
ALLOCATE DATA: FMH5 FMH52
Explanation: The TME 10 OPC server has created a subtask for processing requests from a remote dialog user or
a program interface application. The subtask has abended.
System action: The server deallocates the APPC/MVS conversation. The contact between the TME 10 OPC
dialog, or program interface application, and the TME 10 OPC subsystem is thereby broken. The partner of the
APPC/MVS conversation, a dialog user or a program interface application, is informed about the error by message
EQQPH14E and an error return code. An TME 10 OPC dialog user gets message EQQPH14 displayed at the next
terminal action. A program interface application gets message EQQPH14E written to the message log of the program
interface job, and the EQQYCOM call ends with return code 8.
User response: Perform the actions described for message EQQPH14E. If the problem reoccurs, report the error to
your IBM representative.
 Copyright IBM Corp. 1991, 1998
231
EQQPH10E Ÿ EQQPH13E
EQQPH10E COMMUNICATION WITH USER USER AT LU LU FAILED, APPC/MVS SERVICE VERB REQUESTED
IN STATE STATE RETURN_CODE RC, STATUS_RECEIVED SR, DATA_RECEIVED DR
Explanation: The APPC/MVS communication between a dialog user or program interface application and the
TME 10 OPC server failed. An APPC/MVS service request issued by the server ended with a nonzero return code.
System action: The server deallocates the APPC/MVS conversation. The contact between the TME 10 OPC
dialog, or program interface application, and the TME 10 OPC subsystem is therby broken. The partner of the
APPC/MVS conversation, a dialog user or a program interface application, is informed about the error by message
EQQPH14 and an error return code. An TME 10 OPC dialog user gets message EQQPH14 displayed at the next
terminal action. A program interface application gets message EQQPH14 written to the message log of the program
interface job, and the EQQYCOM call ends with return code 8.
System programmer response: Check the meaning of the APPC/MVS return codes. If the problem reoccurs,
report the error to your IBM representative.
EQQPH11E COMMUNICATION WITH USER USER AT LU LU FAILED, UNEXPECTED COMBINATION OF
RETURN VALUES APPC/MVS SERVICE VERB REQUESTED IN STATE STATE RETURN_CODE RC,
STATUS_RECEIVED SR, DATA_RECEIVED DR
Explanation: The APPC/MVS communication between a dialog user or program interface application and the
TME 10 OPC server failed. An APPC/MVS service request ended with a combination of return values that is not
supported by the communication routines.
System action: The server deallocates the APPC/MVS conversation. The contact between the TME 10 OPC
dialog, or program interface application, and the TME 10 OPC subsystem is therby broken. The partner of the
APPC/MVS conversation, a dialog user or a program interface application, is informed about the error by message
EQQPH14 and an error return code. An TME 10 OPC dialog user gets message EQQPH14 displayed at the next
terminal action. A program interface application gets message EQQPH14 written to the message log of the program
interface job, and the EQQYCOM call ends with return code 8.
System programmer response: Check the meaning of the APPC/MVS return codes. If the problem reoccurs,
report the error to your IBM representative.
EQQPH12E COMMUNICATION WITH USER USER AT LU LU FAILED, INSUFFICIENT VIRTUAL STORAGE
AVAILABLE, DIAGNOSTIC INFO ALT
Explanation: The APPC/MVS communication between a dialog user or program interface application and the
TME 10 OPC server failed because of insufficient storage for the server task.
System action: The server deallocates the APPC/MVS conversation. The contact between the TME 10 OPC
dialog, or program interface application, and the TME 10 OPC subsystem is therby broken. The partner of the
APPC/MVS conversation, a dialog user or a program interface application, is informed about the error by message
EQQPH14 and an error return code. An TME 10 OPC dialog user gets message EQQPH14 displayed at the next
terminal action. A program interface application gets message EQQPH14 written to the message log of the program
interface job, and the EQQYCOM call ends with return code 8.
System programmer response: Stop the server, or the TME 10 OPC Controller if the message is in the Controller
message log, and restart it in a larger region.
EQQPH13E FAILED TO LOAD SERVICE MODULE MOD
Explanation: A dialog user or a program interface application tries to invoke TME 10 OPC remotely. An TME 10
OPC server module required for the remote communication cannot be located.
System action: The system waits for you to respond.
System programmer response: Check that the module is accessable. If the problem reoccurs, report the error to
your IBM representative.
232
TME 10 OPC Messages and Codes
EQQP010E Ÿ EQQP014E
EQQP010E VERB in state STATE failed with RC RC, SR SR, DR DR
Explanation: An APPC/MVS service request issued for server communication failed. The verb VERB was issued
when the conversation was in state STATE. APPC/MVS returned: Return_Code RC, Status_Received SR and
Data_Received DR.
System action: The request is rejected.
User response: Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS
menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT
request. Repeat the dialog action from the TME 10 OPC primary option panel, or rerun the program interface
application.
System programmer response: Check the meaning of the APPC/MVS return codes. Check the message log of the
server for a message explaining the communication loss. If the problem reoccurs, report the error to your IBM
representative.
EQQP011E INSUFFICIENT VIRTUAL STORAGE, DIAGNOSTIC INFO ALT
Explanation: A routine for communication with the server failed because it could not obtain sufficient amount of
virtual storage.
System action: The request is rejected.
User response: Logon to TSO with a larger SIZE parameter value, or rerun the program interface application with a
larger region specified.
EQQP012E APPC/MVS VERB VERB FAILED WITH RC RC, SR SR, DR DR
Explanation: An APPC/MVS service request issued for server communication failed. The verb VERB was issued
when the conversation was in state STATE. APPC/MVS returned: Return_Code RC, Status_Received SR and
Data_Received DR.
System action: The request is rejected.
User response: Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS
menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT
request. Repeat the dialog action from the TME 10 OPC primary option panel, or rerun the program interface
application.
System programmer response: Check the meaning of the APPC/MVS return codes. Check the message log of the
server for a message explaining the communication loss. If the problem reoccurs, report the error to your IBM
representative.
EQQP014E REQUEST FAILED, SEVERE ERROR AT THE SERVER, LU
Explanation: An error occurred at the server.
System action: The dialog or program interface application cannot continue.
System programmer response: Check the message log of the server for a message explaining the error at the
server.
User response: Check that the proper LU name is specified. For the dialog the LU name is set via the OPTIONS
menu. A program interface application sets the LU name through the EQQYPARM parameter file or through the INIT
request. Repeat the dialog action from the TME 10 OPC primary option panel, or rerun the program interface
application.
System programmer response: Check the message log of the server for a message explaining the communication
problem. If the problem reoccurs, report the error to your IBM representative.
Chapter 19. EQQPnnn Messages
233
EQQP015E Ÿ EQQP015E
EQQP015E FAILED TO SET UP COMMUNICATION WITH SERVER LU, RC RC
Explanation: An APPC/MVS Allocate request issued for server communication failed. LU shows the LU name of the
server. RC shows the return code of the Allocate request.
System action: The user cannot start the TME 10 OPC dialog. The INIT request of program interface application
gets return code 8.
User response: Check that the proper LU name is specified and LU is active as well. For the dialog the LU name is
set via the OPTIONS menu. A program interface application sets the LU name through the EQQYPARM parameter
file or through the INIT request. Repeat the dialog action from the TME 10 OPC primary option panel, or rerun the
program interface application.
234
TME 10 OPC Messages and Codes
EQQQ002E Ÿ EQQQ010E
Chapter 20. EQQQnnn Messages
EQQQ002E THE SPECIAL RESOURCE GROUP IS INVALID
Explanation: You have entered a group ID that contains invalid characters.
System action: The request is rejected.
User response: Change the group ID so that is contains any character in the range A–Z, 0–9 or national characters.
EQQQ004E THE ENTRY IS INVALID, ENTER EITHER A OCHCYES OR A ochcno
Explanation: You have entered an invalid character in the field. It must be either a ochcyes or a ochcno.
System action: The request is rejected.
User response: Change the character to a ochcyes or a ochcno.
EQQQ005E THE ENTRY MUST NOT BE BLANK
Explanation: You must not leave this field blank.
System action: The request is rejected.
User response: Change the field to a non-blank value.
EQQQ006E THE ENTRY IS INVALID, ENTER A VALUE IN THE RANGE 1 TO 999999
Explanation: You have entered an invalid quantity in the field. It must be in the range 1—999999.
System action: The request is rejected.
User response: Change the quantity to a valid value.
EQQQ007E THE ENTRY IS INVALID, ENTER OSROEF, osroefs, osroefx, osroek or blank.
Explanation: You have entered an invalid keep on error option.
System action: The request is rejected.
User response: Change the entry to a valid value.
EQQQ008E THE MEMBER NAME IS NOT IN A VALID ISPF FORMAT
Explanation: You have entered an invalid name.
System action: The request is rejected.
User response: Change the name to a format recognised by ISPF.
EQQQ009E THE DAY ENTERED IS INVALID
Explanation: You have entered an invalid day. Enter either a valid day or a valid date.
System action: The request is rejected.
User response: Enter a valid value.
EQQQ010E THE INTERVAL OVERLAPS WITH A PRIOR INTERVAL
Explanation: You have entered a combination of day/date and time that is invalid because it overlaps another
interval.
System action: The request is rejected.
User response: Correct the day/date and/or time.
 Copyright IBM Corp. 1991, 1998
235
EQQQ011E Ÿ EQQQ018W
EQQQ011E THE TO TIME MUST BE GREATER THAN THE FROM TIME
Explanation: You have entered an invalid combination of to and from times.
System action: The request is rejected.
User response: Ensure that the to time is greater than the from time.
EQQQ012E 24.00 IS NOT ALLOWED AS TO TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid to times are 00.00 through 23.59.
EQQQ013W THE SELECTED OPERATION COULD NOT BE FOUND IN THE CURRENT PLAN
Explanation: You have selected to view an operation that no longer exists in the current plan.
System action: The request is rejected.
User response: Refresh the list of operations and choose another.
EQQQ014W THE SELECTED OPERATION IS NO LONGER IN THE QUEUE OR LIST
Explanation: You have requested to delete an operation from the queue or list that is no longer in the list or queue.
System action: The request is rejected.
User response: Refresh the list of operations and select another.
EQQQ015E THE ENTRY IS INVALID, ENTER S OR LEAVE BLANK
Explanation: You have entered an invalid value in the rules field.
System action: The request is rejected.
User response: Change the field to one of the valid values.
EQQQ016E THE ENTRY IS INVALID, ENTER A YEAR IN THE RANGE 1984 TO 1999
Explanation: You have entered an invalid quantity in the field. It must be in the range 1984–1999.
System action: The request is rejected.
User response: Change the year to a valid value.
EQQQ017E THE ENTRY IS INVALID, ENTER A DAY IN THE RANGE 1 TO 366
Explanation: You have entered an invalid day in the field. It must be in the range 1–366.
System action: The request is rejected.
User response: Change the day to a valid value.
EQQQ018W THE PERIOD DOES NOT EXIST
Explanation: You have entered a period that has not been defined.
System action: The panel is redisplayed so that users can press End again in order to confirm that they are aware
that the period does not exist.
User response: Change the period to one that exists, define the period, blank the period field out, or ignore the
warning.
236
TME 10 OPC Messages and Codes
EQQQ019E Ÿ EQQQ028I
EQQQ019E THE ENTRY IS INVALID, ENTER A VALUE IN THE RANGE -999999 TO 999999
Explanation: You have entered an invalid deviation in the field. It must be in the range -999999 to 999999.
System action: The request is rejected.
User response: Change the quantity to a valid value.
EQQQ021E 00.00 IS NOT ALLOWED AS FROM TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid from times are 00.01 through 24.00.
EQQQ022W THE WORK STATION DOES NOT EXIST
Explanation: You have entered the name of a workstation that does not exist.
System action: The panel is redisplayed so that users can press End again in order to confirm that they are aware
that the workstation does not exist.
User response: Change the workstation to one that exists, define the work station, blank the field out, or ignore the
warning.
EQQQ023E THE WORK STATION IS ALREADY INCLUDED
Explanation: You have entered a workstation that has already been defined as connected to the resource.
System action: The request is rejected.
User response: Remove duplicate workstation names.
EQQQ024I THE SPECIAL RESOURCE HAS NO OPERATIONS FOR YOU TO EXAMINE
Explanation: You have attempted to access either the in use list or waiting queue for a special resource and it has
no operations either using or waiting for it.
System action: The request is rejected.
User response: Choose another special resource.
EQQQ025E THE ENTRY IS INVALID, IT MUST BE OCHCYES, ochcno or left blank
Explanation: You have entered an invalid value in the On Error field.
System action: The request is rejected.
User response: Change the field to one of the valid values.
EQQQ026E THE WORK STATION CONTAINS INVALID CHARACTERS
Explanation: You have entered the name of a workstation that contains invalid characters. The first character must
be either a national character, an alphabetic character or one of the TME 10 OPC generic selection characters. The
remainder of the workstation name must consist of alphanumerics, national characters or TME 10 OPC generic
search characters.
System action: The panel is redisplayed forcing the user to change the entry.
User response: Change the workstation to one that contains valid characters.
EQQQ028I NO DEFAULT WS CONNECT LIST HAS BEEN DEFINED
Explanation: You have attempted to access the list of connected workstations that will act as the defaults and none
have been defined.
System action: The request is rejected.
User response: Define a list of connected workstations to be used as defaults if they are required.
Chapter 20. EQQQnnn Messages
237
EQQQ029I Ÿ EQQQ036E
EQQQ029I WS CONNECT LIST NOT DEFINED FOR THIS INTERVAL, DEFAULTS WILL BE USED
Explanation: You have attempted to access the list of connected workstations in an interval for which no list has
been defined. The default connected workstations defined for this special resource will be used instead.
System action: The request is rejected.
User response: Define a list of connected workstations for this interval if the default list should not be used.
EQQQ030I THE SPECIAL RESOURCE HAS NO INTERVALS FOR YOU TO BROWSE
Explanation: You have attempted to access the list of intervals but none have been defined.
System action: The request is rejected.
User response: Define a list of intervals if they are required.
EQQQ031E THE SPECIAL RESOURCE IS BEING UPDATED BY ANOTHER USER
Explanation: You have attempted to access a special resource which is currently locked by another user.
System action: The system waits for you to respond.
User response: Try to update the special resource later.
EQQQ032I THE SPECIAL RESOURCE HAS BEEN SUCCESSFULLY CREATED
Explanation: The special resource has been created and stored.
System action: Processing continues.
User response: None.
EQQQ033I THE SPECIAL RESOURCE HAS BEEN SUCCESSFULLY MODIFIED
Explanation: The special resource has been modified and stored.
System action: Processing continues.
User response: None.
EQQQ034I THE SPECIAL RESOURCE HAS BEEN SUCCESSFULLY DELETED
Explanation: The special resource has been deleted and removed.
System action: Processing continues.
User response: None.
EQQQ035E INVALID ENTRY, ENTER OCHCCNTL, OCHCPLAN, ochcboth, or ochcnone
Explanation: You have entered an invalid value in the usage field.
System action: The request is rejected.
User response: Change the field to one of the valid values.
EQQQ036E YOU ARE NOT AUTHORIZED TO ACCESS THE SR
Explanation: You have attempted to access the special resource MCP (SR) database, but you are not authorized to
access it.
System action: The request is rejected.
User response: If you require access, contact your security administrator.
238
TME 10 OPC Messages and Codes
EQQQ038E Ÿ EQQQ501E
EQQQ038E A SPECIAL RESOURCE WITH THIS NAME ALREADY EXISTS
Explanation: You have attempted to create a special resource which already exists.
System action: The request is rejected.
User response: Change the special resource name to something unique.
EQQQ039E YOU ARE NOT AUTHORIZED TO ACCESS THE RD
Explanation: You have attempted to access the special resource description (RD) database, but you are not
authorized to access it.
System action: The request is rejected.
User response: If you require access, contact your security administrator.
EQQQ040I THE SPECIAL RESOURCE IS NOT CURRENTLY ALLOCATED TO ANY OPERATIONS
Explanation: The special resource has no operations in the current plan that are currently allocating it.
System action: The system waits for you to respond.
User response: The special resource has no in use list. Choose another special resource.
EQQQ041I THERE ARE NO OPERATIONS WAITING TO ALLOCATE THE SPECIAL RESOURCE
Explanation: The special resource has no operations in the current plan that are currently waiting for it.
System action: The system waits for you to respond.
User response: The special resource has no waiting queue. Choose another special resource.
EQQQ043I NO MATCHING SPECIAL RESOURCE(S) FOUND
Explanation: No special resource(s) matched the generic or non-generic search criteria you specified to generate a
list of special resources.
System action: The system waits for you to respond.
User response: Retry using new selection criteria.
EQQQ044W THE SPECIAL RESOURCE WAS NOT FOUND
Explanation: The special resource could not be found.
System action: The request is rejected.
User response: Choose another special resource.
EQQQ500I SPECIAL RESOURCE DATASPACE HAS BEEN SUCCESSFULLY DELETED
Explanation: TME 10 OPC successfully deleted the special resource data space.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQQ501E SPECIAL RESOURCE DATASPACE DELETE FAILED. REASON CODE IS REASON
Explanation: TME 10 OPC could not delete the special resource data space. The storage is not freed.
System action: Normal TME 10 OPC processing continues.
Problem determination: Use the reason code REASON from DSPSERV to determine the cause of the error. Refer
to the MVS/ESA documentation that describes DSPSERV reason codes.
System programmer response: Perform the actions described for the DSPSERV reason code.
Chapter 20. EQQQnnn Messages
239
EQQQ502I Ÿ EQQQ505E
EQQQ502I SPECIAL RESOURCE DATASPACE HAS BEEN CREATED.
SIZE PAGES ARE USED FOR NUM SPECIAL RESOURCE RECORDS
Explanation: A data space has been successfully created for special resource records. SIZE shows the number of
pages (each 4096 bytes) used to create the data space. NUM shows the maximum number of special resource
records that the data space can contain.
TME 10 OPC uses a minimum of 20 pages.
System action: Normal processing continues. TME 10 OPC will use the data space when accessing special
resources.
System programmer response: None.
EQQQ503E SPECIAL RESOURCE DATASPACE CREATION FAILED. REASON CODE IS REASON. SIZE PAGES
WERE REQUESTED FOR NUM SPECIAL RESOURCES
Explanation: TME 10 OPC could not create a data space for special resource storage. Reason code REASON is
set by the DSPSERV service. SIZE shows the number of pages (each 4096 bytes) that TME 10 OPC needed. NUM
shows the number of special resource records that TME 10 OPC wanted to store in the data space.
System action: If the error occurred in batch, the batch program terminates. If the error occurred in the controller
the normal mode manager (NMM) terminates.
Problem determination: Use the reason code REASON from DSPSERV to determine the cause of the error. Refer
to the MVS/ESA documentation that describes DSPSERV reason codes.
System programmer response: Correct the error and restart the NMM subtask. Or resubmit the batch job, if the
error occurred in batch.
EQQQ504I STAT SPECIAL RESOURCE RESNAME HAS BEEN DYNAMICALLY ADDED BY USER
Explanation: A requested special resource RESNAME did not exist in the current plan, but has been dynamically
added to the special resource data space by user or function USER. Status STAT=NEW means that the special
resource did not previously exist in the RD database. Status STAT=OLD means that the special resource had already
been defined. Note that the DYNAMICADD keyword of the RESOPTS statement has no effect if the special resource
already exists in the RD database.
This message can be issued at daily planning, when an operation becomes ready, or when a special resource event
record is processed.
System action: Normal processing continues. TME 10 OPC increases the quantity of a dynamically created special
resource if another operation allocates the special resource with a larger value, or to avoid contention.
User response: None.
EQQQ505E UNSUCCESSFUL DATASPACE ACCESS REQUEST, INFORMATION FOLLOWS:
ACCESS REQUEST IS FROM MODID , REASON CODE IS RSN ,
REQUESTED FUNCTION IS FUNC , INDEX NUMBER IS INDEX
Explanation: An TME 10 OPC subtask encountered an unexpected error when accessing a resource in the
resource data space.
System action: The messages that follow this message in the TME 10 OPC message log indicate the action taken
by the TME 10 OPC subtask.
System programmer response: Correct the error and, if necessary, restart the subtask that encountered the error.
240
TME 10 OPC Messages and Codes
EQQQ506I Ÿ EQQQ510W
EQQQ506I SPECIAL RESOURCE DATASPACE HAS BEEN EXTENDED
SIZE PAGES ARE USED FOR NUM SPECIAL RESOURCE RECORDS
Explanation: A data space for special resource records has been successfully extended. SIZE shows the number of
pages (each 4096 bytes) the data space was extended to. NUM shows the maximum number of special resource
records that the data space can contain.
System action: Normal processing continues. TME 10 OPC will use the data space when accessing special
resources.
System programmer response: None.
EQQQ507I A SPECIAL RESOURCE DATASPACE BACKUP PROCESS HAS STARTED
Explanation: The normal mode manager (NMM) has started a current plan copy process. This copy process causes
a backup of the special resource data space. Updated records in the data space are written the current plan
extension (EQQCXDS) dataset.
System action: Normal processing continues.
System programmer response: None.
EQQQ508I A SPECIAL RESOURCE DATASPACE BACKUP PROCESS HAS ENDED.
NUM RECORDS WERE WRITTEN TO CX
Explanation: The normal mode manager (NMM) has successfully written all updated records in the special resource
data space, to the current plan extension (EQQCXDS) dataset.
System action: Normal processing continues.
System programmer response: None.
EQQQ509E A SPECIAL RESOURCE DATASPACE BACKUP PROCESS HAS FAILED
Explanation: The normal mode manager (NMM) could not write all updated records in the special resource data
space to the current plan extension (EQQCXDS) dataset.
System action: The NMM subtask is terminated.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the reason for this
message.
System programmer response: Correct the error and restart the NMM subtask.
EQQQ510W SPECIAL RESOURCE RESNAME WAS NOT DYNAMICALLY ADDED
Explanation: A Special Resource dynamic add request has been rejected. The reason for this is either:
Ÿ An SRSTAT command specifying a special resource that does not exist and DYNAMICADD is not set to OPER or
NO.
Ÿ A job that refers to a special resource that does not exist is about to be submitted and DYNAMICADD is not set to
EVENT or NO.
System action: Processing continues, any operations that refer to this special resource will not be submitted.
User response: Add the special resource manually or delete the special resource reference from the operation.
System programmer response: None.
Chapter 20. EQQQnnn Messages
241
EQQQ511W Ÿ EQQQ515W
EQQQ511W RESOURCE: RESNAME IS TOO LARGE.
THE LAST INTERVAL USED STARTS AT DATE TIME
Explanation: This message is issued to the message log when a special resource is too large to fit into the CX file.
System action: The special resource record is truncated to fit into the CX file. The start time of the last interval
used in the record is displayed in the message.
User response: Allocate the CX file with a larger record size or change the special resource description to not use
so many intervals.
EQQQ515W OPERATION ADID OPID, JOBN IA IADATE IATIME HAS WAITED FOR
RESOURCE RES FOR CTIME MINUTES
Explanation: This message is issued by the controller when an operation has waited a longer time than specified in
the RESOPTS CONTENTIONTIME parameter value to allocate a given resource. The message variables are:
ADID
OPID
JOBN
IADATE
IATIME
RES
CTIME
Application ID of operation.
Workstation name and operation number.
Jobname of the operation, or blank if no jobname is defined.
Input arrival date of the operation.
Input arrival time of the operation.
Name of the special resource that the operation has requested.
The time now spent on the waiting queue
System action: Processing continues. The operation will remain on the waiting queue for the required resource.
User response: Use the dialog to inspect the special resource queues for the special resource indicated by the
message. Modify the queues or the operations if the situation needs to be corrected.
242
TME 10 OPC Messages and Codes
EQQRM01I Ÿ EQQRM07W
Chapter 21. EQQRMnn Messages
EQQRM01I RODM SUBTASK INITIALIZATION IS COMPLETE
Explanation: The RODM subtask has completed initialization processing.
System action: Processing continues.
Operator response: None.
EQQRM02E RODM SUBTASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT DQE
Explanation: An abend prevented the RODM subtask from processing a queue element.
System action: MVS recovery/termination is requested to generate a dump. The RODM subtask restarts, and
resumes normal processing.
Problem determination: Review the TME 10 OPC message log dataset (EQQMLOG), the diagnostic dataset
(EQQDUMP), and the system dump dataset to determine the cause of the problem.
System programmer response: Save the EQQMLOG, EQQDUMP, and system dump datasets and contact your
IBM representative.
EQQRM03W RODM CONNECT FAILED FOR RODM SUBSYSTEM NAME. RC IS RC. RSN IS RSN
Explanation: A non-zero return code was returned by the RODM system NAME when the RODM subtask called the
RODM API to connect.
System action: The RODM subtask will attempt to connect to this RODM system repeatedly until the connection
succeeds or the RODM subtask is stopped.
System programmer response: Ensure that the RODMSYS keyword is specified correctly, and if so, that the
specified RODM subsystem has started successfully. Refer to the RODM Programming Guide for more information
about return codes and reason codes used by the RODM API.
EQQRM04W RODM CONNECT FAILED DUE TO RODM ERROR FOR SYSTEM
Explanation: The RODM subtask has not been able to connect to the specified RODM system.
System action: The OPCRESOURCE/OPCFIELD specified on the RODMOPTS statement referring to this RODM
subsystem will be set to Inactive, and processing continues. Attempts to connect to this RODM subsystem will be
initiated every 5 minutes.
System programmer response: Ensure that the RODM subsystem is properly initialized.
EQQRM05I INITIALIZATION FAILED - SUBSYSTEM STOP REQUESTED
Explanation: A stop subsystem command was issued while the RODM subtask was initializing. This caused the
subtask to end.
System action: The TME 10 OPC subsystem continues the shutdown sequence.
User response: None.
EQQRM07W THE RODM SUBTASK IGNORED THE FOLLOWING ELEMENT ON THE RODM QUEUE DQE
Explanation: An invalid subscription request was found on the RODM queue.
System action: Processing continues.
System programmer response: Contact your IBM representative.
 Copyright IBM Corp. 1991, 1998
243
EQQRM09E Ÿ EQQRM16I
EQQRM09E RODM SUBTASK QUEUE POINTERS ARE DESTROYED, RODQ IS LOST
Explanation: The RODM subtask abended while processing elements on APPQ because the queue chaining is
invalid.
System action: MVS recovery/termination is requested to generate a dump. The RODM subtask restarts, and
resumes normal processing.
Problem determination: Review the TME 10 OPC message log dataset (EQQMLOG), the diagnostic dataset
(EQQDUMP), and the system dump dataset to determine the cause of the problem.
System programmer response: Save the EQQMLOG, EQQDUMP, and system dump datasets and contact your
IBM representative.
EQQRM11E RODM INTERFACE MODULE EKGUAPI COULD NOT BE LOADED
Explanation: A RODM interface module was not found in the library search path.
System action: TME 10 OPC continues, but the RODM functions as requested by RODMOPTS keywords referring
to this destination are disabled.
System programmer response: Make sure that the RODM interface modules are accessible either via the
LINKLST, or in the STEPLIB concatenation, and restart TME 10 OPC
EQQRM12W OPC RESOURCE UNKNOWN NAME
Explanation: A RODMOPTS statement specifies a resource unknown to TME 10 OPC.
System action: This RODMOPTS statement is ignored. Processing continues. The status will be set to Inactive.
System programmer response: Specify a valid resource name, or add the resource to TME 10 OPC.
EQQRM13E OPC RESOURCE FIELD UNKNOWN NAME
Explanation: A RODMOPTS statement specifies a resource field unknown to TME 10 OPC.
System action: RODM subtask initialization fails and the controller is shutdown.
System programmer response: Specify a valid resource field name and restart the controller.
EQQRM14W RODM OBJECT UNKNOWN NAME
Explanation: A RODMOPTS statement specifies a RODM object unknown to TME 10 OPC.
System action: The OPCRESOURCE/OPCFIELD specified on the RODMOPTS statement referring to this RODM
OBJECT will be set to Inactive and processing continues. New subscription attempts will be performed every 5
minutes.
System programmer response: Specify a valid object name, or add the object to the RODM subsystem.
EQQRM15W RODM OBJECT FIELD UNKNOWN NAME
Explanation: A RODMOPTS statement specifies a RODM field unknown to TME 10 OPC.
System action: The OPCRESOURCE/OPCFIELD specified on the RODMOPTS statement referring to this RODM
FIELD will be set to Inactive and processing continues.
System programmer response: Specify a valid RODM field name or add the field to the object in the RODM
subsystem.
EQQRM16I CONNECTION ESTABLISHED TO RODM SUBSYSTEM: NAME
Explanation: TME 10 OPC has connected to a RODM subsystem.
System action: Processing continues.
User response: None.
244
TME 10 OPC Messages and Codes
EQQRM17W Ÿ EQQRM22W
EQQRM17W CONNECTION LOST TO RODM SUBSYSTEM: NAME
Explanation: TME 10 OPC has lost the connection to a RODM subsystem.
System action: Processing continues. The status for all resources being monitored by the named RODM subsystem
will be set to inactive, and the values of the corresponding TME 10 OPC resource fields will be set according to the
RODMLOST values in the RODMOPTS statements. Attempts to reconnect to this RODM subsystem will be initiated
every 5 minutes.
User response: None.
EQQRM18E INVALID TRANSLATION VALUE TYPE VALUE SPECIFIED FOR OPC RESOUCE NAME
Explanation: A RODMOPTS statement specifies a translate value that is invalid.
System action: RODM subtask initialization fails and the controller is shutdown.
System programmer response: Specify a valid value in the TRANSLATE ordered list and restart the controller.
EQQRM19E INVALID RODMLOST VALUE VALUE SPECIFIED FOR OPC RESOURCE NAME
Explanation: A RODMOPTS statement specifies a RODMLOST value that is invalid.
System action: RODM subtask initialization fails and the controller is shutdown.
System programmer response: Specify a valid value in the RODMLOST keyword and restart the controller.
EQQRM20E DESTINATION UNKNOWN NAME
Explanation: A RODMOPTS statement specifies a destination unknown to TME 10 OPC.
System action: RODM subtask initialization fails and the controller is shutdown.
System programmer response: Specify a valid destination name and restart the controller.
EQQRM21W THE AVAILABILITY OF A SPECIAL RESOURCE CANNOT BE DETERMINED FROM A RODM
OBJECT. RESOURCE NAME IS NAME
Explanation: A RODMOPTS statement specifies that the availability of a special resource should be updated by a
field in a RODM object. TME 10 OPC cannot determine whether the special resource is available or not because the
value of the field is not Y, N, or a value that can be translated to Y or N.
System action: The availability of the special resource is not changed. The RODM subtask continues normal
processing.
System programmer response: Verify that the RODM object has been correctly updated. Verify that the
RODMOPTS statement refers to the correct RODM object.
EQQRM22W A SPECIAL RESOURCE QUANTITY COULD NOT BE DETERMINED FROM A RODM OBJECT.
RESOURCE NAME IS NAME
Explanation: A RODMOPTS statement specifies that a special resource quantity should be updated by a field in a
RODM object. However, the value of the field is not within the valid range of special resource quantities. The valid
range is 0–999 999.
System action: The special resource quantity is not changed. The RODM subtask continues normal processing.
System programmer response: Verify that the RODM object has been correctly updated. Verify that the
RODMOPTS statement refers to the correct RODM object.
Chapter 21. EQQRMnn Messages
245
EQQRM23W Ÿ EQQRM28W
EQQRM23W A SPECIAL RESOURCE DEVIATION COULD NOT BE DETERMINED FROM A RODM OBJECT.
RESOURCE NAME IS NAME
Explanation: A RODMOPTS statement specifies that a special resource deviation quantity should be updated by a
field in a RODM object. However, the value of the field is not within the valid range of special resource deviations.
The valid range is -999999 – 999999.
System action: The special resource quantity is not changed. The RODM subtask continues normal processing.
System programmer response: Verify that the RODM object has been correctly updated. Verify that the
RODMOPTS statement refers to the correct RODM object.
EQQRM24W SUBSCRIBE FOR RODM OBJECT NAME FAILED. RC IS RC, REASON IS RSN
Explanation: A non-zero return code was returned by a RODM system when the RODM subtask called the RODM
API to add a notify subscription.
System action: The RODM subtask continues normally. If the RODM object is modified later, the RODM subtask
will not be notified and the corresponding TME 10 OPC resource will not be updated.
System programmer response: Ensure that the current field in the RODM object has a notify subfield. Refer to
RODM Programming Guide, SC31-6130, for more information about return codes and reason codes used by the
RODM API.
EQQRM25I SUBSCRIBE FOR RODM OBJECT NAME WAS SUCCESSFUL
Explanation: A zero return code was returned by a RODM system when the RODM subtask called the RODM API
to add a notify subscription.
System action: The RODM subtask continues normally. If the RODM class is modified later, the RODM subtask will
be notified and the corresponding TME 10 OPC resource will be updated.
System programmer response: None.
EQQRM26W SUBSCRIBE FOR RODM CLASS NAME FAILED. RC IS RC, REASON IS RSN
Explanation: A non-zero return code was returned by a RODM system when the RODM subtask called the RODM
API to add a notify subscription.
System action: The RODM subtask continues normally. If the RODM class is modified later, the RODM subtask will
not be notified and the corresponding TME 10 OPC resource will not be updated.
System programmer response: Ensure that the current field in the RODM class has a notify subfield. See RODM
Programming Guide, SC31-6130, for more information about return codes and reason codes used by the API.
EQQRM27I SUBSCRIBE FOR RODM CLASS NAME WAS SUCCESSFUL
Explanation: A zero return code was returned by a RODM system when the RODM subtask called the RODM API
to add a notify subscription.
System action: The RODM subtask continues normally. If the RODM class is later modified, the RODM subtask will
be notified and the corresponding TME 10 OPC resource will be updated.
System programmer response: None.
| EQQRM28W SUBSCRIBE FOR RODM OBJECT NAME FAILED. RC IS RC, REASON IS RSN TME 10 OPC WILL
|
RETRY EVERY 3 MINUTES
| Explanation: A nonzero return code was returned by a RODM system when the RODM subtask called the RODM
| API to add a notify subscription for a RODM object.
| System action: The RODM subtask continues normally. TME 10 OPC will try again after three minutes to add the
| notify subscription for the RODM object.
| System programmer response: None.
246
TME 10 OPC Messages and Codes
EQQRM29W Ÿ EQQRM29W
| EQQRM29W SUBSCRIBE FOR RODM CLASS NAME FAILED. RC IS RC, REASON IS RSN OPC/ESA WILL
|
RETRY EVERY 3 MINUTES
| Explanation: A nonzero return code was returned by a RODM system when the RODM subtask called the RODM
| API to add a notify subscription for a RODM class.
| System action: The RODM subtask continues normally. TME 10 OPC will try again after three minutes to add the
| notify subscription for the RODM object.
| System programmer response: None.
Chapter 21. EQQRMnn Messages
247
248
TME 10 OPC Messages and Codes
EQQR000E Ÿ EQQR013E
Chapter 22. EQQRnnn Messages
EQQR000E YOU ARE NOT AUTHORIZED TO ACCESS THE READY LIST
Explanation: You have attempted to access the ready list but you are not authorized to access it.
System action: The requested access to the ready list is rejected.
User response: Contact your security administrator if you require access to the ready list.
EQQR008E YOU ARE NOT AUTHORIZED TO ACCESS THE JS DATA SET
Explanation: You have attempted to access the job setup facility, but you are not authorized to access it.
System action: The requested access to the job setup facility is rejected.
User response: If you only want to browse the JCL, you need read access authority; if you want to update JCL, you
need update access authority. Contact your security administrator.
EQQR010I ERDR ERC£ TERMINATED
Explanation: Event reader ERC processing has completed and control is returned to the TME 10 OPC subsystem.
System action: Event reader ERC processing is terminated.
User response: None.
EQQR011I EVENT READER ERC£ HAS BEEN REQUESTED TO STOP
Explanation: An event reader has been requested to stop while waiting for event data set positioning information to
become available.
System action: The event reader will free all acquired resources and terminate.
System programmer response: None.
EQQR012I ERDR ERC£ RESTARTED
Explanation: Event reader ERC has been restarted. This message is only issued for event readers that service the
NCF application at remote sites. The most likely reason for this is that the event reader is restarted with new event
dataset positions after a CP refresh, or the reader is restarted when an NCF session is reestablished after failure.
System action: Event reader ERC restart processing continues.
User response: None.
EQQR013E ERDR UNABLE TO LOAD MODULE EQQERBEX - INITIALIZATION IS TERMINATED
Explanation: An event reader task was unable to locate the EQQERBEX load module.
System action: The event reader initialization is terminated.
System programmer response: Stop the event readers using the MODIFY command. Make sure that the
EQQERBEX module resides in a load library that is accessible by TME 10 OPC, and then restart the event readers.
 Copyright IBM Corp. 1991, 1998
249
EQQR014W Ÿ EQQR023E
EQQR014W ERDR ERC£ NO VALID HEADER IN EVENT DATA SET WITH DDNAME DDN
Explanation: Event reader ERC encountered a header record that contained invalid information, for example, the
track capacity and the total number of records in the dataset were missing. The most probable reason for this
message is that a new event dataset has been created and it is being formatted by the event writer before usage.
The header record is not updated with the dataset characteristics until the formatting job has completed. This might
take some time if the event dataset is large.
System action: Event reader ERC processing continues. It makes a new attempt to extract valid information from
the header record every 10 seconds. This message is written on the TME 10 OPC message log every two minutes
until a valid header is read, or until the TME 10 OPC subsystem posts a stop request.
Problem determination: If this message appears more than 10 times on the TME 10 OPC message log dataset,
stop the event readers. Check that the DDN ddname connects to the correct event dataset, and if so, find out why
the header record is not valid.
System programmer response: Stop the event readers using the MODIFY command. Correct the error and restart
the event readers.
EQQR015E SEQUENCE NUMBER SEQNO IS ALREADY IN USE BY AN EVENT WRITER SUBTASK
Explanation: At event reader initialization, an event writer was already started with the sequence number specified in
the ERSEQNO keyword of ERDROPTS.
The number specified in the ERSEQNO keyword of ERDROPTS must be unique within the TME 10 OPC subsystem.
System action: The event reader initialization fails. The event reader subtask is terminated.
TME 10 OPC administrator response: Update the ERSEQNO keyword with a unique sequence number, and
restart the event reader subtask.
EQQR021E ERDR ERC£ UNABLE TO OPEN EVENT DATA SET WITH DDNAME DDN
Explanation: Event reader ERC could not open its associated input dataset (ddname DDN).
System action: Event reader ERC processing is terminated.
Problem determination: Verify that the ddname statement associated with this event reader is correctly specified.
The ddname is EQQEVDxx, where xx should be equal to ERC.
System programmer response: Stop the event readers using the MODIFY command. Correct the error, if any, and
then restart the event readers.
EQQR023E ERDR ERC£ RECORDS OVERWRITTEN ON EVENT DATA SET (DDNAME DDN) LR£ EVENTS HAVE
BEEN LOST
Explanation: Event reader ERC# encountered a situation where the event writer overwrites event records not yet
processed by the event reader. Event datasets are used in a wrap-around fashion and for some reason the event
reader cannot keep up with the event writer.
System action: Event reader ERC# processing continues. The event records that were overwritten (LR#) are lost
and cannot be recaptured.
Problem determination: You probably have one of the following:
Ÿ An inadequate event dataset allocation, so that it wraps around too fast.
Ÿ The wait interval (ERWAIT of the ERDROPTS statement) is too long, that is, the event reader waits too long
between successive read attempts.
You should also check the dispatching priority of the reader task, to ensure that its priority is similar to that of the
event writer.
User response: Contact your system programmer.
System programmer response: Stop the event readers using the MODIFY command. Modify the appropriate
parameters and restart the event readers.
250
TME 10 OPC Messages and Codes
EQQR024E Ÿ EQQR029E
EQQR024E ERDR ERC£ TERMINATION DUE TO INITIALIZATION FAILURE
Explanation: Event reader ERC has encountered initialization errors.
System action: Event reader ERC processing is terminated.
Problem determination: This message is preceded by other messages in the TME 10 OPC message log. They
indicate the exact reason for the failure.
System programmer response: Stop the event readers using the MODIFY command. Correct the error, if any, and
then restart the event readers.
EQQR025I ERDR ERC£ STARTED
Explanation: Event reader ERC has successfully completed its initialization processing and is now ready.
System action: Event reader ERC processing continues.
EQQR026E ERDR ERC£ I/O-ERROR ON EVENT DATA SET WITH DDNAME DDN - SYNAD INFORMATION:
SYNADMSG
Explanation: The event reader ERC encountered an I/O error when reading its associated event dataset (ddname
DDN). The event dataset is defined on the DDN ddname statement.
System action: Event reader ERC processing is terminated.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate decoumentation for the MVS/DFP product
installed on this MVS/ESA system.
System programmer response: Correct the error and restart the event readers using the MODIFY command, or
stop TME 10 OPC correct the error and restart TME 10 OPC.
EQQR027E ERDR ERC£ INITIALIZATION FAILED - KEYWORD SPECIFICATION MISSING
Explanation: Event reader ERC found that the KEYWORD keyword was not specified on the ERDROPTS
statement.
System action: Event reader ERC processing is terminated.
System programmer response: Stop the event readers using the MODIFY command. Correct the error, if any, and
then restart the event readers.
EQQR028E ERDR ERC£ INITIALIZATION FAILED - KEYWORD SPECIFICATION INVALID
Explanation: Event reader ERC found that the keyword KEYWORD was not specified correctly on the ERDROPTS
statement. ERC consists of ** if the ERSEQNO keyword specification was in error.
System action: Event reader ERC processing is terminated.
System programmer response: Stop the event readers using the MODIFY command. Correct the error, if any, and
then restart the event readers.
EQQR029E ERDR ERC£ INITIALIZATION FAILED - NO ERDROPTS STATEMENT SPECIFIED
Explanation: Event reader ERC found no ERDROPTS statement in the member (specified on the OPCOPTS
statement) that was to hold initialization parameters for an event reader. ERC consists of ** since no event reader
sequence number available.
System action: Event reader ERC processing is terminated.
Problem determination: The TME 10 OPC message log contains messages that identify the parameter member
that is in error.
System programmer response: Stop the event readers using the MODIFY command. Add a correct ERDROPTS
statement to the member in error, and then restart the event readers.
Chapter 22. EQQRnnn Messages
251
EQQR101E Ÿ EQQR108W
EQQR101E THE LAYOUT RLLAYOUT CANNOT BE ADDED TO THE LAYOUT TABLE
Explanation: The ready list layout table already contains the layout you tried to add.
System action: The ready list layout table is not updated.
User response: You can change the layout name and repeat the request.
EQQR102I THE LAYOUT RLLAYOUT HAS BEEN ADDED TO THE LAYOUT TABLE
Explanation: The layout has been successfully added to the ready list layout table and saved.
System action: The ready list layout table is updated.
User response: None.
EQQR103I THE LAYOUT RLLAYOUT HAS BEEN DELETED FROM THE LAYOUT TABLE
Explanation: The layout has been successfully deleted from the ready list layout table.
System action: The ready list layout table is updated.
User response: None.
EQQR104I THE LAYOUT RLLAYOUT HAS BEEN UPDATED IN THE LAYOUT TABLE
Explanation: The layout has been successfully updated in the ready list layout table.
System action: The ready list layout table is updated.
User response: None.
EQQR105E TO EXIT FROM THIS PANEL, EITHER SELECT A LAYOUT OR CANCEL THE REQUEST
Explanation: A layout is required for the requested ready list display.
System action: The system waits for you to respond.
User response: Select an existing layout or create a new one.
EQQR106E FAILURE TO OPEN THE LAYOUT TABLE
Explanation: TME 10 OPC could not open the ready list layout table.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check that the ISPTLIB dataset contains the EQQRLOUT table.
EQQR107W A DEFAULT LAYOUT CANNOT BE DELETED
Explanation: You have attempted to delete an installation-defined layout but you may not do so. You can delete
only your own layouts.
System action: The request is rejected.
User response: Check that the layout you attempted to delete is the layout you want to delete.
EQQR108W THE LAYOUT RLLAYOUT CANNOT BE FOUND IN THE LAYOUT TABLE
Explanation: The layout rllayout does not exist.
System action: The system waits for you to respond.
User response: Select one of the layouts in the list or create a new one.
252
TME 10 OPC Messages and Codes
EQQR109E Ÿ EQQR201I
EQQR109E THE LAYOUT RLLAYOUT CANNOT BE FOUND IN THE LAYOUT TABLE
Explanation: The layout rllayout does not exist.
System action: The system waits for you to respond.
User response: Select one of the layouts in the list or create a new one.
EQQR110E THE LAYOUT ID MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQR111E SELECT AN ITEM BY SPECIFYING SELECT OR A NUMBER 01-99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQR112E LEAVE BLANK OR SPECIFY OCHCYES OR OCHCNO
Explanation: Data entry error; see “Data Entry Errors” on page 2.
ochcyes is the national language character for Y (yes); ochcno is for N (no).
EQQR120E NO LAYOUT WAS SELECTED, RSRLT IS USED
Explanation: The ready list was to be displayed using the default layout, RSRLT, the layout that was used last time
the ready list was displayed for the same workstation. That layout could not be found and the first layout in the layout
table is used.
System action: The ready list is displayed.
User response: You may change the layout ID if the used layout is not appropriate.
EQQR121E A LAYOUT MUST BE SELECTED TO DISPLAY ERROR LISTS.
Explanation: The Ended in Error List cannot be displayed without a layout ID.
System action: A panel listing the possible layouts is displayed.
User response: Select a layout from the selection list, or specify a valid ID in the layout input field.
EQQR200E INVALID PARAMETER WHEN CALLING MODULE MODNM
Explanation: There is an invalid parameter in the input to the ready list module (module name modnm).
System action: The requested access to a ready list function is rejected.
Problem determination: This message indicates that there is an error in the current panel.
User response: Contact your system programmer.
System programmer response: Check that the panel has not been inadvertently overlayed in the panel library
(ISPPLIB).
EQQR201I RETURN CODE URC WAS RETURNED FROM READY LIST USER EXIT
Explanation: The active exit for this ready list layout ended with a return code greater than or equal to 8.
System action: The status is not changed.
User response: Contact the person responsible for ready list exit to determine the reason for the return code set.
Chapter 22. EQQRnnn Messages
253
EQQR202I Ÿ EQQR403E
EQQR202I SET STATUS REQUEST CANCELLED BY USER EXIT
Explanation: The active exit for this ready list layout has returned a 9 in the status field URNSTAT, which means
cancel the request.
System action: The status is not changed.
User response: None.
EQQR300E PRIORITY MUST BE A NUMBER 1 - 9
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQR302E SELECT THE WORK STATION TO DISPLAY A READY LIST
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQR303E A CHARACTER THAT IS NOT A STATUS CODE IS IN THE CODE STRING
Explanation: A character you have specified as a selection criterion for status codes is not a valid status code.
System action: The system waits for you to respond.
Problem determination: The convention on status codes for the installation is defined in the ISPPLIB library panel
EQQXINIX.
User response: Contact your system programmer.
System programmer response: Check panel EQQXINIX for valid values and reenter.
EQQR400W THERE ARE NO OPERATOR INSTRUCTIONS FOR THIS OPERATION
Explanation: There are no operator instructions for the operation you selected in the ready list.
System action: The system waits for you to respond.
User response: Check your input.
EQQR401W JS AND JOBLIB DATA SETS CONTAIN NO JCL FOR THIS OPERATION
Explanation: There is no JCL for the operation you selected in the ready list.
System action: The system waits for you to respond.
User response: Check your input.
EQQR402W THERE IS A JCL RECORD ON THE JS DATA SET, BUT IT CONTAINS NO JCL
Explanation: There is a JCL record for the operation you selected, but the record does not contain JCL.
System action: The system waits for you to respond.
User response: Check your input.
EQQR403E CHECK JCL RECORD KEY: (JSADID JSIAD JSIAT JSOPNUM)
Explanation: A read failed when trying to read the JCL record with the key JSADID JSIAD JSIAT JSOPNUM. The
key is derived from ISPF variables set up in a panel.
System action: The system waits for you to respond.
Problem determination: This message indicates that there is an error in the current or previous panel.
User response: Contact your system programmer.
System programmer response: Check that the panel has not been inadvertently overlayed in the panel library
(ISPPLIB).
254
TME 10 OPC Messages and Codes
EQQR404E Ÿ EQQR617E
| EQQR404E STORAGE PROBLEMS OCCURRED
| Explanation: In an MCP dialog JCL edit session the Controller returned data that could not be retrieved and
| displayed, because not enough storage had been preallocated to receive it.
| Problem determination: This message indicates that, in the ISPF environment, there is not enough main storage to
| receive and display the JCL modified and returned from the controller.
EQQR600E STATUS ENTERED OR GIVEN BY EXIT MUST BE str, sts, sti, ste, or stc
Explanation: Data entry error; see “Data Entry Errors” on page 2.
str is the national language character for R (ready); sts is for S (started); sti is for I (interrupted); ste is for E
(ended-in-error); and stc is for C (complete).
EQQR602E ENTER OSOPSTS, OSOPSTI, OSOPSTE, OR osopstc
Explanation: Data entry error; see “Data Entry Errors” on page 2.
osopsts is the national language character for S (started); osopsti is for I (interrupted); osopste is for E
(ended-in-error); and osopstc is for C (complete).
EQQR603E ENTER OSOPSTS, OSOPSTE, OR OSOPSTC
Explanation: Data entry error; see “Data Entry Errors” on page 2.
osopsts is the national language character for S (started); osopste is for E (ended-in-error); and osopstc is for C
(completed).
EQQR604E ENTER OSOPSTI, OSOPSTE, OR OSOPSTC
Explanation: Data entry error; see “Data Entry Errors” on page 2.
osopsti is the national language character for I (interrupted); osopste is for E (ended-in-error); and osopstc is for C
(complete).
EQQR615E ONLY OPERATIONS WITH STATUS ARRIVING CAN BE SET TO READY
Explanation: You have attempted to set an operation in the current plan to “ready,” but only operations with status
“arriving” can be set to ready.
System action: The system waits for you to respond.
User response: Enter a valid status or leave blank.
EQQR616W REQUEST TO SET THE STATUS TO STARTED IS IGNORED
Explanation: You have attempted to set an operation in the current plan to “started,” but the operation has already
started.
System action: The request is ignored.
User response: None.
EQQR617E ONLY OPERATIONS WITH THE STATUS STARTED CAN BE INTERRUPTED
Explanation: You have attempted to interrupt an operation that has not yet started. You can interrupt an operation
only if it has already started.
System action: The system waits for you to respond.
User response: Enter a valid status or leave blank.
Chapter 22. EQQRnnn Messages
255
EQQR618W Ÿ EQQR626E
EQQR618W REQUEST TO SET THE STATUS TO ERROR IS IGNORED
Explanation: You have attempted to set an operation in the current plan to ended-in-error status but the operation is
already set to that status.
System action: The request is ignored.
User response: None.
EQQR619W REQUEST TO SET THE STATUS TO COMPLETE IS IGNORED
Explanation: You have attempted to set an operation in the current plan to “complete” status but the operation has
already completed.
System action: The request is ignored.
User response: None.
EQQR620W THE INTERRUPT REQUEST IS IGNORED
Explanation: You have attempted to interrupt an operation in the current plan, but the operation has already been
interrupted.
System action: The request is ignored.
User response: None.
EQQR621E DURATION REQUIRED FOR OPERATIONS THAT HAVE NOT BEEN STARTED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You must specify a duration for operations that have not started.
EQQR622E AN OPERATION WAITING FOR ARRIVAL CANNOT BE RESET
Explanation: You have attempted to reset an operation that is waiting for arrival. This is not allowed.
System action: The system waits for you to respond.
User response: Enter a valid status or leave blank.
EQQR623E AN OPERATION WITH READY STATUS CANNOT BE RESET
Explanation: You have attempted to reset an operation that is ready. This is not allowed.
System action: The system waits for you to respond.
User response: Enter a valid status or leave blank.
EQQR624E OP BEING UPDATED BY ANOTHER USER, REQUEST IS REJECTED, RSNC: XSSRS
Explanation: The operation can either not be read from the current plan or has another status, real duration, or error
code than is displayed. In both cases, the operation has been changed from its condition in the ready list.
System action: The ready list is refreshed and the system waits for you to respond.
User response: Review the operation, and if it is still valid, reenter the request.
EQQR626E THE REQUESTED STATUS CHANGE MUST BE DONE VIA A RESET REQUEST
Explanation: The intended status change is not supported. You must first enter a reset request, then a request to
get the desired status.
System action: The ready list is displayed.
User response: Enter the row command R and then enter N-x, where x is the required status.
256
TME 10 OPC Messages and Codes
EQQR627E Ÿ EQQR651E
EQQR627E RESET OF OSEQ OPERATION MUST BE DONE USING MODIFY CURRENT PLAN DIALOG
Explanation: You attempted to reset an operation with error code OSEQ from the Ready List dialog. This cannot be
done. The error code OSEQ indicates that a job began to execute before all the predecessors to the operation were
complete.
System action: The ready list is displayed.
User response: Reset can be done when all predecessors to the OSEQ operation are complete. To reset the
operation status to Waiting, issue the operation command RERUN from the error list in the Modify Current Plan dialog.
EQQR629E THE JCL IS BEING UPDATED BY ANOTHER USER, REQUEST IS REJECTED
Explanation: You have attempted to update the JCL but it is being updated by another user.
System action: The request is rejected and the system waits for you to respond.
User response: Try again later.
EQQR638E WHEN SETTING STATUS TO OSOPSTI, SPECIFY DURATION OF OPERATION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A duration is required when setting an operation to interrupted status.
EQQR639E WHEN SETTING STATUS TO OSOPSTE, THE TYPE OF ERROR MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
An error type is required when setting the status to osopste, the national language character for E (ended-in-error).
EQQR640I THE JCL FOR THIS OPERATION CONTAINS UNRESOLVED VARIABLES
Explanation: You tried to resolve variables using the Program Interface request JCLPREPA, with SIMTYPE FULL,
and TME 10 OPC found one or more unresolvable variables in the JCL for the operation.
System action: None.
User response: Browse the EQQMLOG dataset for message EQQJ510, that gives you the name of the failing
variable. Correct the failing variable and retry the request.
EQQR650E TOO MANY TABLES WERE DECLARED IN A SEARCH DIRECTIVE
Explanation: The number of tables requested by a SEARCH directive is greater than 16.
Unless GLOBAL and APPL are explicitly excluded (NOGLOBAL and NOAPPL), they contribute to the total even if they
are not specified in the SEARCH directive.
System action: None.
Problem determination: Investigate the TME 10 OPC message log. Look for message EQQJ540.
User response: Contact your system programmer.
System programmer response: Correct the JCL.
EQQR651E A TABLE DIRECTIVE TRIED TO CONCATENATE MORE THAN 16 TABLES
Explanation: A TABLE directive has been encountered when 16 tables are already active.
System action: None.
Problem determination: Investigate the TME 10 OPC message log. Look for message EQQJ541.
User response: Contact your system programmer.
System programmer response: Correct the JCL.
Chapter 22. EQQRnnn Messages
257
EQQR652E Ÿ EQQR658E
EQQR652E A DUPLICATE TABLE NAME WAS ENCOUNTERED IN THE SAME JCL LINE
Explanation: The same table name was encountered twice in an OPC SEARCH directive.
System action: None.
Problem determination: Investigate the TME 10 OPC message log. Look for message EQQJ501.
User response: Contact your system programmer.
System programmer response: Check the OPC directive in the JCL for this operation.
EQQR653E A CONTRADICTORY USE OF STANDARD TABLES WAS ENCOUNTERED
Explanation: An OPC SEARCH directive contains either both GLOBAL and NOGLOBAL, or both APPL and
NOAPPL.
System action: None.
Problem determination: Investigate the TME 10 OPC message log. Look for message EQQJ502.
User response: Contact your system programmer.
System programmer response: Correct the current COMP statement.
EQQR654E JCL MEMBER DEFINED IN A FETCH DIRECTIVE COULD NOT BE RETRIEVED
Explanation: The member specified in an OPC SEARCH directive could not be found.
System action: The system waits for you to respond.
Problem determination: Investigate the TME 10 OPC message log. Look for message EQQJ503.
User response: Try again after a while.
EQQR655E A RECURSIVE VARIABLE SUBSTITUTION WAS ENCOUNTERED IN THE JCL
Explanation: The value of a variable depends on the values of other variables, which in turn depend on its value.
No value can be determined for this variable.
System action: The system waits for you to respond.
Problem determination: Investigate the TME 10 OPC message log. Look for message EQQJ506.
User response: None.
EQQR656E THE VALUE ENTERED DOES NOT MATCH THE VARIABLE'S VERIFICATION RULES
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The value that you entered is invalid according to the validation criteria defined for this variable.
For more information, use the S row command and check if help is defined for the current variable. If no help is
defined, contact the person responsible for variable definitions to see what rules apply to the variable.
EQQR657E A VALUE MUST BE ENTERED FOR THIS VARIABLE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
According to the definition of this variable, a value must be entered.
EQQR658E THE EDIT OPTION CHARACTER MUST BE Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You must enter Y (yes) or N (no).
258
TME 10 OPC Messages and Codes
EQQR659E Ÿ EQQR665E
EQQR659E A SUBSTITUTION CAUSED A STRUCTURAL CHANGE IN AN OPC DIRECTIVE
Explanation: Variable substitution has caused at least one of these changes:
Ÿ
Ÿ
Ÿ
Ÿ
An OPC directive has been created.
The type of an OPC directive has changed.
The keywords of an OPC directive have changed.
An OPC directive has changed to another line type.
System action: The system waits for you to respond.
User response: Use the S row command to see if there is any help for the current variable. If there is no help,
contact the person responsible for JCL variable definitions and maintenance.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ507.
EQQR660E A RECURSIVE SUBSTITUTION OCCURRED IN THE JCL FOR THE OPERATION
Explanation: A closed loop of dependency definitions or variable translations exists.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ508.
EQQR661E THE JCL FOR THIS OPERATION REFERENCED AN UNDEFINED VARIABLE TABLE
Explanation: A table declared in a SEARCH or TABLE directive does not exist.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ509.
EQQR663E A DEPENDENCY RECURSION OF VARIABLES OCCURRED IN THE JCL
Explanation: A closed loop of dependency definitions exists.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ512.
EQQR664E A DEPENDENCY TO A SUBMIT TYPE VARIABLE WAS ENCOUNTERED
Explanation: A setup variable cannot be dependent on a submit variable. Either the variables are defined
incorrectly, or the active table concatenations are incorrect.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ513.
EQQR665E AN INVALID RETURN CODE WAS SET BY A USER EXIT DURING SUBSTITUTION
Explanation: TME 10 OPC received an unexpected return code from an exit.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ514.
Chapter 22. EQQRnnn Messages
259
EQQR666E Ÿ EQQR671E
EQQR666E AN ABEND HAS OCCURRED IN A SUBSTITUTION USER EXIT
Explanation: The user module caused an ABEND, from which TME 10 OPC recovered.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ515.
EQQR667E AN UNRECOVERABLE ABEND HAS OCCURRED IN A SUBSTITUTION USER EXIT
Explanation: The user module caused an ABEND, from which TME 10 OPC could not recover.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ516.
EQQR668E AN INVALID VALUE WAS RETURNED FROM A VARIABLE SUBSTITUTION EXIT
Explanation: The value that the user supplied for the variable violates the verification rules in the variable definition.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ517.
EQQR669E A COMP EXPRESSION THAT EXCEEDS 1024 BYTES IN LENGTH WAS ENCOUNTERED
Explanation: The total length of all fields of a COMP expression, including COMP= and all continuations of the right
side of the expression on subsequent JCL lines, cannot exceed 1024 characters after substitution.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the TME 10 OPC message log and look for message EQQJ542.
EQQR670E A SUBSTITUTION USER EXIT SET ERROR RETURN CODE
Explanation: A substitution exit set return code 8, which interrupted the JCL variable substitution. No further
substitution is done for this operation.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the substitution exit to determine the cause of this return code.
Check the TME 10 OPC message log and look for message EQQJ539.
EQQR671E OPC/ESA WAS UNABLE TO LOAD A USER EXIT
Explanation: TME 10 OPC could not load a substitution or JCL imbed exit.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Check the current load library in the started task JCL, and make sure the exit is
link-edited to the correct library.
Check the TME 10 OPC message log and look for message EQQJ531 or EQQJ615.
260
TME 10 OPC Messages and Codes
EQQR672E Ÿ EQQR675E
EQQR672E A USER EXIT DEFINED WILL NOT BE CALLED. IT IS NOT EXECUTABLE
Explanation: An exit is referred to in variable substitution or JCL tailoring. TME 10 OPC has previously discovered
an abend in this exit and marked it as not executable. This exit will not be called again.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Correct the exit, and restart TME 10 OPC to use the exit again.
Check the TME 10 OPC message log and look for message EQQJ518 or EQQJ617.
EQQR673E SUBSTITUTION ERROR, SEE MSG IN JCL
Explanation: The message is issued to a user in the JCL Setup dialog to indicate that an error has been detected
during variable substitution.
System action: The system waits for you to respond.
Problem determination: Look at the detailed error message that has been inserted into the JCL. You can find the
message by entering ISPF command LOCATE SPECIAL.
User response: Correct the JCL.
EQQR674E A SETUP PHASE DIRECTIVE REFERS TO A SUBMIT VARIABLE
Explanation: Current job contains a JCL processing directive specifying PHASE=SETUP. TME 10 OPC could not
determine what action is requested by the statement because it refers to a JCL variable whose value will be
determined during the submit phase.
System action: The system waits for you to respond.
User response: Enter the JCL Edit dialog and correct the incorrect statement. Then reenter the Ready List dialog
and retry JCL setup for current operation.
EQQR675E AN ERROR OCCURRED DURING JCL-VARIABLE SUBSTITUTION.
Explanation: An error was detected during JCL-variable substitution processing. This message can be issued to a:
Dialog user
In the JCL Setup dialog to indicate that an error has been detected during variable substitution
PIF application In the EQQMLOG for the PIF job when any type of substitution or validation error occurs.
System action: In the dialog, the system waits for you to respond. If the error occurred while using the PIF, the job
is terminated with return code 0008.
Problem determination: In the dialog, look at the detailed error message that has been inserted into the JCL. You
can find the message by entering ISPF command LOCATE SPECIAL.
If you are using the PIF, check the controller message log (EQQMLOG) for messages describing the problem.
User response: Correct the errors and try the request again.
Chapter 22. EQQRnnn Messages
261
262
TME 10 OPC Messages and Codes
EQQSU01I Ÿ EQQSU06E
Chapter 23. EQQSUnn Messages
EQQSU01I THE SUBMIT TASK HAS STARTED
Explanation: The submit task has successfully completed initialization.
System action: Submit task processing starts.
User response: None.
EQQSU02I THE SUBMIT TASK HAS ENDED
Explanation: The submit task has terminated processing normally. An operator has stopped the submit task, or the
TME 10 OPC subsystem has stopped.
System action: The submit task processing terminates.
User response: None.
EQQSU03E THE SUBMIT TASK HAS ENDED DUE TO PROCESSING ERRORS
Explanation: The submit task cannot continue processing due to a severe error.
System action: The submit task processing terminates.
Problem determination: Review previous messages in the TME 10 OPC message log.
System programmer response: Correct the errors and restart the submit task.
EQQSU04E THE SUBMIT TASK INITIALIZATION FAILED, THE TASK IS TERMINATED
Explanation: The submit task could not acquire the resources required for normal operation.
System action: The submit task processing terminates.
Problem determination: Review previous messages in the TME 10 OPC message log.
System programmer response: Correct the errors and restart the submit task.
EQQSU05E THE OPC/ESA INTERNAL READER FILE, DDNAME = EQQBRDS, COULD NOT BE OPENED
Explanation: The submit task could not open the internal reader dataset.
System action: If the error occurs when the submit task is being initialized, the submit task processing terminates
and message EQQSU04 is issued.
If the error occurs when the submit task tries to reopen the internal reader to perform a submit for a user, the submit
task processing continues but the current job is not submitted.
Problem determination: Check that DDNAME EQQBRDS is correctly specified in the startup procedure.
System programmer response: Correct the errors, then restart either the submit task or the TME 10 OPC
subsystem.
EQQSU06E A SEVERE ERROR IN THE SUBMIT TASK HAS CAUSED ONE OR MORE REQUESTS TO BE LOST
Explanation: The submit task abended while processing elements on SUBQ. The chaining of elements on SUBQ
has been corrupted.
System action: MVS recovery/termination is requested to generate a dump. All elements currently on SUBQ are
skipped. The submit task attempts to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset and the dump dataset to determine the
cause of the problem.
System programmer response: Save the MLOG and dump datasets, then contact your IBM representative.
 Copyright IBM Corp. 1991, 1998
263
EQQSU07E Ÿ EQQSU12I
EQQSU07E THE SUBMIT TASK ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: REQUEST
Explanation: An abend prevented the submit task from processing a queue element.
System action: MVS recovery/termination is requested to generate a dump. The submit task attempts to continue
normal processing.
Problem determination: Review the TME 10 OPC message log dataset and the dump dataset to determine the
cause of the problem.
System programmer response: Save the MLOG and dump datasets, then contact your IBM representative.
EQQSU09W JOB JOBNAME(JOBNUM) COULD NOT BE RELEASED. REPEATED RETRIES HAVE FAILED
Explanation: The submit task received a release request for a job, but could not communicate successfully with JES
while trying to release the job from hold.
System action: No more attempts to release the job will be made. Submit task processing continues.
Problem determination: Review the system log, and look for previous JES messages that indicate unusual
conditions.
Operator response: Determine the current status of the job. Release the job manually, if necessary.
EQQSU10E JOB JOBNAME IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE THE SUBMIT EXIT
RETURNED A SUBMITTING USER ID, USER, WHOSE AUTHORITY COULD NOT BE DETERMINED
Explanation: The job submit exit returned a TSO user ID. A job submit environment could not be built for this user
ID, because of an authority error.
System action: The current job is not submitted. Submit task processing continues.
Problem determination: Check that the job submit exit, EQQUX001, returns only valid TSO user IDs.
User response: Submit the job manually, if necessary.
EQQSU11W DDNAME EQQEVDS IS MISSING OR SPECIFIES DD DUMMY
Explanation: The Submit task is starting and does not have access to an Event dataset. The Event dataset header
record (record 0) is used for submit checkpointing, and with no Event dataset available for submit checkpointing,
submit requests may be lost or duplicated.
System action: The Submit task continues processing but will not checkpoint submit requests. The first submit
request received after start up will cause message EQQSU22E to be issued.
Problem determination: Verify the JCL procedure for this TME 10 OPC address space.
System programmer response: Allocate a unique Event dataset to the EQQEVDS dd statement. If this TME 10
OPC address space does not start an event writer subtask, that is EWTRTASK(NO) in OPCOPTS, allocate the Event
dataset with two tracks of space.
EQQSU12I MAX NUMBER OF WORKSTATIONS CHECKPOINTED BY THIS SUBMIT TASK: NNNN
Explanation: The submit task has, using the EQQEVDS dataset LRECL, calculated the maximum number (NNNN)
of workstations that can be checkpointed by this submit task.
System action: Normal processing continues.
Problem determination: This message is information only.
User response: None.
System programmer response: None.
264
TME 10 OPC Messages and Codes
EQQSU13E Ÿ EQQSU21E
EQQSU13E THE OPC/ESA STARTED TASK FILE, DDNAME=EQQSTC, COULD NOT BE OPENED FOR OUTPUT
Explanation: The submit task was unable to open the started task temporary proclib dataset. This file is defined by
the DD statement EQQSTC in the JCL procedure used to start the TME 10 OPC subsystem.
System action: If the error is discovered during the start of TME 10 OPC, the submit task issues message
EQQSU04 and terminates. When the error is discovered during submit of a started task, this message is followed by
message EQQW759W and the submit task stops submitting started tasks.
Problem determination: Check that DD statement EQQSTC is correctly specified in the startup procedure. Verify
that the TME 10 OPC subsystem is authorized to open the temporary proclib dataset for output. If RACF is installed,
determine if the MVS SYSLOG file contains an ICH408 access violation message for the temporary proclib dataset.
System programmer response: Ensure that the TME 10 OPC subsystem is properly authorized to use the
temporary proclib dataset, and that the EQQSTC DD statement is correctly defined, then restart either the submit task
or the TME 10 OPC subsystem.
EQQSU20E UNABLE TO READ EQQEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE ON
WORKSTATION WSNAME
Explanation: The submit task was unable to execute a submit checkpoint request for the reason stated. Request
type can be one of:
J0
J1
J2
WTO
Request for submit checkpoint sequence number
Job submit checkpoint request
STC start checkpoint request
Message checkpoint request.
System action: The submit task continues normal processing.
Problem determination: Review earlier messages in the message log to determine the cause of the error.
System programmer response: If necessary, stop TME 10 OPC, take corrective action, then restart TME 10 OPC.
EQQSU21E UNABLE TO UPDATE EQQEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE ON
WORKSTATION WSNAME
Explanation: The submit task was unable to execute a submit checkpoint request for the reason stated. Request
type can be one of:
J0
J1
J2
WTO
Request for submit checkpoint sequence number
Job submit checkpoint request
STC start checkpoint request
Message checkpoint request.
System action: The submit task continues normal processing.
Problem determination: Review earlier messages in the message log to determine the cause of the error.
System programmer response: If necessary, stop TME 10 OPC, take corrective actions and then restart TME 10
OPC.
Chapter 23. EQQSUnn Messages
265
EQQSU22E Ÿ EQQSU24W
EQQSU22E UNABLE TO ACCESS THE EQQEVDS FILE FOR REQUEST TYPE DQETYPE ON WORKSTATION
WSNAME
Explanation: The submit task was unable to execute a submit checkpoint request for the reason stated. Request
type can be one of:
J0
J1
J2
WTO
Request for submit checkpoint sequence number
Job submit checkpoint request
STC start checkpoint request
Message checkpoint request
System action: The submit task continues normal processing.
Problem determination: Review earlier messages in the message log to determine the cause of the error.
System programmer response: If necessary, stop TME 10 OPC, take corrective actions and then restart TME 10
OPC.
EQQSU23E NO FREE SPACE IN EQQEVDS HEADER RECORD FOR REQUEST TYPE DQETYPE ON
WORKSTATION WSNAME
Explanation: The submit task was unable to execute a submit checkpoint request because all workstation entries in
the the event data set header record are used. Request type can be one of:
J0
J1
J2
WTO
Request for submit checkpoint sequence number
Job submit checkpoint request
STC start checkpoint request
Message checkpoint request
System action: The Submit task continues normal processing.
Problem determination: The maximum number of workstations that can be checkpointed by this EQQEVDS is
indicated in message EQQSU12I. If you have more workstations defined for this destination than can be
checkpointed, you should reallocate the EQQEVDS with a larger logical record length, refer to TME 10 OPC
Installation Guide for more details.
System programmer response: If necessary, stop TME 10 OPC, scratch and reallocate the EQQEVDS with a
larger LRECL and then restart TME 10 OPC.
EQQSU24W WORKSTATION WSNAME IS NOT PRESENT IN THE EQQEVDS HEADER RECORD
Explanation: The Job Submit task could not remove a workstation name from the event data set header record
because the name is not present.
System action: The Job Submit task continues normal processing.
System programmer response: None.
266
TME 10 OPC Messages and Codes
EQQS000E Ÿ EQQS005E
Chapter 24. EQQSnnn Messages
EQQS000E YOU DO NOT HAVE AUTHORITY TO ACCESS THE QUERY CP DIALOG
Explanation: You have attempted to access the Query Current Plan dialog, but you are not authorized to access it.
System action: The request is rejected and the system waits for you to respond.
User response: Contact your security administrator to get access to the Query Current Plan dialog.
EQQS001E AN INVALID MODULE PARAMETER WAS DETECTED
Explanation: There is an invalid parameter in the input to a query current plan module.
System action: The requested access to the query current plan function is rejected.
Problem determination: This message indicates that there is an error in the current panel.
User response: Contact your system programmer.
System programmer response: Check that the panel has not been inadvertently overlaid in the panel library
(ISPPLIB).
EQQS003I THE TRACKER HAS NOT PROVIDED ANY SYSTEM INFORMATION
Explanation: System information is not available for the destination defined for this workstation. Tracker system
information is available only when the TME 10 OPC controller has performed the initial synchronization and
handshaking with the tracker, or Tracker Agent.
System action: None.
User response: The handshaking process may be in progress. Try the request again when the workstation is in
Active status. The message can also indicate an error in the TME 10 OPC configuration.
System programmer response: This message is an indication that handshaking is not completed between the
controller and the tracker, or Tracker Agent. If the destination is Active, that is there is not a communication failure,
the event writer subtask at the indicated destination is not active. If this message is not expected, take appropriate
actions to correct the problem with the tracker, or Tracker Agent.
EQQS004E PROBLEMS ENCOUNTERED ATTEMPTING TO LOCATE SYSTEM INFORMATION
Explanation: The controller encountered an error processing the request for system information. This message is
always an indication of an internal error in TME 10 OPC.
System action: Normal processing continues.
User response: Contact your system programmer. Take note of the workstation name, and the approximate time
when this message was issued.
System programmer response: This message indicates that there is an error either in the processing of the
ROUTOPTS initialization statement, or in the Current Plan (CP) dataset. If TME 10 OPC is operating normally, no
actions need be taken immediately. Take a copy of the active Current Plan dataset, the active job-tracking log, the
job-tracking archive, and the controller message log, then call your IBM representative.
EQQS005E SYSTEM INFORMATION IS ONLY POSSIBLE FOR COMPUTER WORK STATIONS
Explanation: System information is passed to the controller by the tracker, or Tracker Agent executing on a system
destination as specified in the workstation description. System information is only available for computer workstations.
System action: The request rejected.
User response: Choose a computer workstation that represents the system for which you need information.
 Copyright IBM Corp. 1991, 1998
267
EQQS100E Ÿ EQQS107E
EQQS100E THE ONLY VALID VALUES ARE OCHCYES AND OCHCNO
Explanation: An attempt was made to specify an invalid value in the AVAIL column.
System action: The system waits for you to respond.
User response: Enter a correct value in the AVAIL column.
EQQS101E YOU ARE NOT AUTHORIZED TO MODIFY SPECIAL RESOURCES
Explanation: To display an TME 10 OPC panel where special resources can be modified, you need update authority
to the SR resource. You do not have this authority.
System action: The request is rejected.
User response: Contact your security administrator.
EQQS102E SPECIAL RESOURCES ARE BEING UPDATED. TRY LATER
Explanation: Another TME 10 OPC dialog user is currently updating special resources. To avoid overlaying another
user’s changes, only one dialog user can actively modify special resources.
System action: Processing continues.
User response: Try again later.
EQQS103E LEAVE BLANK OR SPECIFY ONE OF OSROEF, OSROEFS, osroefx, or osroek
Explanation: You entered an invalid action code in the On error field for a special resource.
System action: The system waits for you to respond.
User response: Enter a valid value, or leave the field blank.
EQQS104E YOU ARE NOT AUTHORIZED TO BROWSE SPECIAL RESOURCES
Explanation: To display an TME 10 OPC panel where special resources can be shown, you need read authority to
the SR resource. You do not have this authority.
System action: The request is rejected.
User response: Contact your security administrator.
EQQS105E EACH SPECIAL RESOURCE MUST NOT BE DEFINED BY MORE THAN ONE ROW
Explanation: You have modified the table containing special resources so that there is more than one row defining a
special resource. This is not allowed.
System action: The system waits for you to respond.
User response: Delete all duplicate special resource definition rows.
EQQS106E OPC/ESA ENCOUNTERED ERRORS WHEN TRYING TO UPDATE SPECIAL RESOURCES
Explanation: An error occurred while updating special resource information in the TME 10 OPC subsystem.
System action: The updated special resource is not stored.
User response: Review the log dataset for error messages issued at the time of the request. If you cannot
determine the cause of the error and the error persists, contact your IBM representative.
EQQS107E DLF INDICATOR CANNOT BE UPDATED WHILE RESOURCE IS ALLOCATED
Explanation: The update cannot be performed until all operations currently allocating the resource have completed.
System action: The update request is rejected.
User response: Retry the update request later.
268
TME 10 OPC Messages and Codes
EQQS300E Ÿ EQQS309E
EQQS300E PRIORITY MUST BE A NUMBER FROM 1 - 9
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQS301E THE MCP ADDED INDICATOR MUST BE OCHCYES OR OCHCNO
Explanation: Data entry error; see “Data Entry Errors” on page 2.
ochcyes is the national language character for 'Y' (yes); ochcno is the national language character for 'N' (no).
EQQS302E THE RERUN INDICATOR MUST BE OCHCYES OR OCHCNO
Explanation: Data entry error; see “Data Entry Errors” on page 2.
ochcyes is the national language character for 'Y' (yes); ochcno is the national language character for 'N' (no).
EQQS303E AN INVALID STATUS CODE STT WAS FOUND IN THE CODE STRING
Explanation: One or more of the status codes (stt) you specified is not valid.
System action: The system waits for you to respond.
Problem determination: The convention on status codes for the installation is defined in the ISPPLIB library panel
EQQXINIX.
User response: Enter valid status codes.
EQQS304E MOST CRITICAL OCCURRENCE LIST, DO NOT SELECT ON STATUS STT
Explanation: The most critical occurrence list will contain all occurrences which were not completed or deleted. It is
not possible to further restrict the list base on the occurrence status.
System action: The system waits for you to respond.
User response: Remove the status code. If you want selection on status, go back to the CURRENT PLAN AND
STATUS INQUIRY panel and select 1, APPLICATIONS.
EQQS305E CODE MUST BE ONE OF ST1E , ST1D , ST1P or st1a
Explanation: You entered an invalid code for selecting occurrences from the current plan in the “Query Current Plan”
dialog.
System action: The system waits for you to respond.
User response: Enter the correct code.
EQQS306E SELECTION TYPE MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQS307E SELECTION TYPE MUST BE OCHALLP, OCHNONP, ochalls, or ochnons
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQS308E NESTING LEVEL MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQS309E NESTING LEVEL MUST BE 1-999
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 24. EQQSnnn Messages
269
EQQS400I Ÿ EQQS402E
EQQS400I NO ENTRIES WERE SELECTED FOR THE LIST
Explanation: A request for a list of records resulted in an empty list. Either there were no records that matched the
selection criteria or you were not authorized to access those that were found.
System action: None.
User response: None.
EQQS401I NO OPEN INTERVAL SPECIFIED IN THE WORK STATION DEFINITION
Explanation: The workstation description in the current plan has no open interval.
System action: None.
User response: None.
EQQS402E UNABLE TO RETRIEVE CPREC DATA, NO RECORDS FOUND
Explanation: The attempt to read the record cprec from the current plan failed. The current plan record may have
been changed after the list data was displayed.
System action: The system waits for you to respond.
User response: The operation list should be refreshed to reflect the current status of the current plan. For ready
lists and the ended-in-error list, this is done automatically at any dialog request or when ENTER is pressed. For other
operation lists, it is necessary to exit from the list and then display the list again.
270
TME 10 OPC Messages and Codes
EQQTT01I Ÿ EQQTT05E
Chapter 25. EQQTTnn Messages
EQQTT01I THE TCP/IP COMMUNICATION TASK HAS STARTED
Explanation: The TCP/IP communication task has successfully completed initialization.
System action: The TCP/IP communication task processing continues.
User response: None.
EQQTT02I THE TCP/IP COMMUNICATION TASK HAS ENDED
Explanation: The TCP/IP communication task has ended either because the TME 10 OPC controller is in the
process of shutting down or as a result of an operator modify command to terminate this task or a related task.
System action: TME 10 OPC processing continues.
User response: None.
EQQTT03E THE TCP/IP COMMUNICATION TASK HAS ENDED DUE TO PROCESSING ERRORS
Explanation: The TCP/IP communication task has terminated due to processing errors.
Problem determination: Check the TME 10 OPC message log and the dump datasets for additional information
which describes the problem.
System action: Normal TME 10 OPC processing continues.
User response: Contact your systems programmer.
System programmer response: If the cause of the error cannot be determined, take a dump of the TME 10 OPC
address space, retain a copy of the message log and the job tracking datasets, and contact your IBM representative.
EQQTT04E THE TCP/IP COMMUNICATION TASK FAILED TO CONNECT WITH THE MVS TCP/IP ADDRESS
SPACE
Explanation: The TCP/IP communication task has not been able to establish a connection with the TCP/IP address
space.
System action: Normal TME 10 OPC processing continues. Operations scheduled to execute on TCP/IP connected
workstations will not be started.
User response: Contact your systems programmer if the TME 10 OPC controller includes workstations associated
with TCP/IP connected destinations.
System programmer response: Determine why TME 10 OPC was unable to establish the connection to the TCP/IP
address space. When the problem has been corrected restart the TME 10 OPC controller.
EQQTT05E THE TCP/IP COMMUNICATION TASK TERMINATED DUE TO A PROCESSING FAILURE
Explanation: The TCP/IP communication task is terminated because an error occurred either when processing the
initialization statements or in the communication with the TCP/IP address space.
System action: The TCP/IP communication task processing is terminated. If EQQTT05 is preceded by message
EQQTT13 the TCP/IP communication task will be restarted automatically and attempt to restore sessions.
Problem determination: Review previous messages in the TME 10 OPC message log.
User response: Contact your system programmer.
System programmer response: Correct all errors in the ROUTOPTS initialization statements and restart TME 10
OPC.
 Copyright IBM Corp. 1991, 1998
271
EQQTT06E Ÿ EQQTT09E
EQQTT06E A SEVERE ERROR IN THE TCP/IP COMMUNICATION TASK HAS CAUSED ONE OR MORE
REQUESTS TO BE LOST
Explanation: The TCP/IP communication task encountered an error processing elements on the TATQ. As a result,
at least one queue element has been lost.
System action: MVS/ESA recovery/termination is requested to generate a dump. The TCP/IP communication task
attempts to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
TME 10 OPC administrator response: Save the message log, dump and diagnostic datasets, and contact your IBM
representative.
EQQTT07E THE TCP/IP COMMUNICATION TASK ABENDED WHILE PROCESSING THE FOLLOWING
REQUEST: REQUEST
Explanation: An abend prevented the TCP/IP communication task from processing a queue element.
System action: MVS/ESA recovery/termination is requested to generate a dump. The TCP/IP communication task
attempts to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
User response: Contact your system programmer.
System programmer response: Save the message log, dump and diagnostic datasets, and contact your IBM
representative.
EQQTT08E THE TCP/IP COMMUNICATION TASK HAS IGNORED THE FOLLOWING QUEUE ELEMENT:
REQUEST
Explanation: The TCP/IP communication task has detected an invalid queue element on its queue.
System action: The element is discarded from the TCP/IP communication task queue. The task continues normal
processing.
Problem determination: Review the TME 10 OPC message log dataset.
User response: Contact your system programmer.
System programmer response: Save the message log (EQQMLOG) and the current plan (EQQCPxDS) and
contact your IBM representative.
EQQTT09E THE TCP/IP TASK CANNOT START, TRACKER FEATURE IS NOT INSTALLED
Explanation: The TCP/IP communication task could not locate a required load module.
System action: The TCP/IP communication task terminates.
System programmer response: If the AIX tracker feature is not installed, then the ROUTOPTS initialization
statement should not specify the TCP keyword. If the AIX 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.
272
TME 10 OPC Messages and Codes
EQQTT10E Ÿ EQQTT14I
EQQTT10E THE TCP/IP COMMUNICATION TASK ENCOUNTERED AN ERROR WHILE PROCESSING A
REQUEST REQUEST
Explanation: An error was encountered when the TA communication task attempted a REQUEST TCP/IP socket
call.
System action: If any of INIT, BIND, GHID, or LSTN request the TA task will terminate. Any other request type will
cause the TA task to close the session with the corresponding tracker. The session will then be reestablished.
Problem determination: Should the request error cause the TA task to terminate the error cause could be any of
the following:
Ÿ The VMCF address space is not active.
Ÿ The TCP/IP started task is not started.
Ÿ The TCPIPID keyword in the ROUTOPTS statement does not define the name of the TCP/IP started task.
System programmer response: Correct any of the conditions above and restart the TA task. Should the error
reappear, save the message log (EQQMLOG) and contact your IBM representative.
| EQQTT11E AN UNDEFINED TRACKER AT IP ADDRESS IPADDR ATTEMPTED TO CONNECT TO THE
|
CONTROLLER. THE REQUEST IS NOT ACCEPTED
| Explanation: A client with IPaddress IPADDR, which is not specified in the TCP keyword of the ROUTOPTS
| initialization statement, attempted to connect to the TME 10 OPC controller via the TCP/IP link. The connect attempt
is not accepted.
System action: Normal processing continues.
Problem determination: Check the TCP keyword specification in the ROUTOPTS statement and the IPaddresses of
the corresponding trackers, ensure there is a one to one correspondence.
System programmer response: Correct any discrepancy in the ROUTOPTS initialization statement or the Tracker's
configuration file and restart either the TME 10 OPC controller (if ROUTOPTS in error), or the Tracker Agent.
EQQTT12E A TCP/IP BIND REQUEST FAILED BECAUSE PORT PORT IS OCCUPIED
Explanation: An error was encountered when the TA communication task attempted a bind request. The PORT
specified in the TCPIPPORT keyword of the ROUTOPTS initialization statement is already occupied.
System action: The TA task is terminated.
System programmer response: Correct the ROUTOPTS specification and restart the subsystem.
EQQTT13E THE TCP/IP COMMUNICATION TASK LOST THE CONNECTION TO THE TCP/IP ADDRESS SPACE.
Explanation: A severe error occurred in the communication between the TA task and the TCP/IP address space.
System action: The TA task will set all workstations associated with TCP destinations to status Offline. The TA task
will be restarted, and thus attempt to reestablish the connection with the TCP/IP address space and restore sessions.
Problem determination: The TCP/IP address space might have been terminated.
System programmer response: Restart the TCP/IP address space if inactive.
EQQTT14I THE TCP/IP COMMUNICATION TASK WILL WAIT 60 SECONDS BEFORE RESTART
Explanation: The TCP/IP communication task is restarted due to problems in the connection to the TCP/IP address
space. It waits 60 seconds before attempting to establish a new connection.
System action: The TCP/IP communication task processing continues.
User response: None.
Chapter 25. EQQTTnn Messages
273
EQQTT15I Ÿ EQQTT19W
EQQTT15I THE TCP/IP COMMUNICATION TASK HAS BEEN UNABLE TO ESTABLISH A CONNECTION TO THE
TCP/IP ADDRESS SPACE FOR THE LAST 200 SECONDS
Explanation: The TCP/IP communication task is attempting to establish a connection to the TCP/IP started task after
a restart. Attempts are made every 20th second. The message is issued every 10th attempt.
System action: The TCP/IP communication task processing continues.
User response: None.
System programmer response: Make sure that the TCP/IP address space is started.
EQQTT16E THE TA TASK RECEIVED INVALID IDENTIFICATION DATA FROM DESTINATION: LU. VALIDATION
RETURN CODE IS RC
Explanation: The initial data received from a TCP/IP-connected Tracker Agent is not valid.
System action: The TA task will free all resources allocated to this session and close the session.
System programmer response: Verify that the correct Tracker Agent program has been started on the remote
destination and that the program is at a supported maintenance level. Also check that the GMT settings are
synchronized for the controller and the Tracker Agent. After making corrections, restart the partner program.
EQQTT17E TCP KEYWORD VALUE, VAL1, IS TOO LONG (OR MISSING)
Explanation: A workstation destination name specified as a value of the TCP keyword of the ROUTOPTS statement
is incorrect. The destination name is required and must not be greater than eight characters.
System action: Processing of the TCP keyword continues. Message EQQTT18E will be issued when all
destinations have been processed.
System programmer response: Either remove or correct the invalid destination and restart the TME 10 OPC
system.
EQQTT18E AT LEAST ONE TCP DESTINATION IS INCORRECTLY DEFINED
Explanation: The TCP keyword of the ROUTOPTS statement contains one or more incorrectly defined TCP
destinations.
System action: Processing of the current ROUTOPTS statement terminates with a nonzero return code. This
causes TME 10 OPC initialization to fail.
System programmer response: Review earlier error messages to determine the incorrectly defined destination.
Either remove or correct the invalid destination and restart the TME 10 OPC system.
EQQTT19W NO ACTIVITY WITHIN THE TIME-OUT INTERVAL. DEST SESSION CLOSED
Explanation: The TCP/IP-connected Tracker Agent defined as TCP destination DEST has not responded to a submit
request from the controller within the defined time-out interval. The TCPTIMEOUT keyword of the ROUTOPTS
statement defines the time-out interval.
System action: The session is terminated. Workstations that reference the destination are set to Offline status.
System programmer response: Check that the TCP/IP-connected Tracker Agent or the machine where it runs have
not terminated abnormally. Restart the system or the Tracker Agent. If the network is heavily loaded and the Tracker
Agent runs on a remote node with poor end-to-end response, increase the TCPTIMEOUT value to ensure that active
sessions are not inadvertently closed.
274
TME 10 OPC Messages and Codes
EQQT002E Ÿ EQQT015I
Chapter 26. EQQTnnn Messages
EQQT002E END DATE FOR PRINTOUT MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT003W ENTER END AGAIN TO LEAVE OR PRESS ENTER TO PRINT
Explanation: Enter END again to leave without initiating a printout, or press ENTER to initiate the printout.
System action: The system waits for you to respond.
User response: Enter END again or press ENTER.
EQQT005E THE CALENDAR FILE IS SIMULTANEOUSLY BEING UPDATED BY ANOTHER USER
Explanation: The calendar you specified cannot be added because a calendar is simultaneously being added by
another user.
System action: The system waits for you to respond.
User response: Try again later.
EQQT011E THE CALENDAR NAME DOES NOT EXIST
Explanation: The requested calendar was not found in calendar database. Either you entered the wrong name or
the requested calendar has not been created yet.
System action: None.
User response: Enter the correct calendar name, or create the requested calendar.
EQQT012E A CALENDAR NAME MUST BE SPECIFIED
Explanation: You did not specify a calendar name.
System action: None.
User response: Enter the name of the calendar you need.
EQQT013E INVALID PARAMETER INPUT TO MODULE MOD
Explanation: This message indicates a programming error in module mod
System action: The system waits for you to respond.
User response: Contact the system programmer to ensure that the IBM-supplied panel is used.
System programmer response: Ensure that the IBM-supplied panel is being used.
EQQT014E CALENDAR CALENDAR IS BEING UPDATED BY ANOTHER USER
Explanation: You cannot update the calendar because another user is already updating it.
System action: The system waits for you to respond.
User response: Try again later.
EQQT015I A CALENDAR HAS BEEN DELETED
Explanation: This confirms that a calendar has been deleted, and the database was updated accordingly.
System action: None.
User response: None.
 Copyright IBM Corp. 1991, 1998
275
EQQT016E Ÿ EQQT024E
EQQT016E CALENDAR ID IS NOT SPECIFIED
Explanation: A calendar ID must be given.
System action: None.
User response: Enter the calendar ID you need.
EQQT017I A CALENDAR HAS BEEN UPDATED
Explanation: This confirms that a calendar has been updated, and the database was updated accordingly.
System action: None.
User response: None.
EQQT018E CALENDAR CALENDAR NOT CREATED - MAXIMUM NUMBER EXCEEDED
Explanation: The maximum number of calendars, 32768, has been exceeded.
System action: The system waits for you to respond.
User response: Delete a calendar to allow a new one to be added.
EQQT019E DUPLICATE SPECIFIC DATES / WEEKDAYS EXIST IN TABLE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT020I A CALENDAR HAS BEEN ADDED
Explanation: This confirms that a calendar has been added, and the database was updated accordingly.
System action: None.
User response: None.
EQQT021E CALENDAR ID IS MISSING OR INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A calendar ID can be made up of the following characters: A through Z, 0 through 9, and national characters (that is,
#, $, and @). The first character must be alphabetic.
EQQT022E ENTERED CALENDAR ID ALREADY EXISTS
Explanation: The calendar ID you specified already exists in the database.
System action: The system waits for you to respond.
User response: Reselect the calendar ID using MODIFY, or specify another calendar ID if using COPY or CREATE.
EQQT023E SPECIFY WEEK DAY OR SPECIFIC DATE IN USER DEFINED FORMAT
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT024E UNABLE TO READ CALENDAR DESCRIPTION RECORD
Explanation: The calendar description record could not be read because it may have been deleted by another user,
or an error in the calendar description database made it impossible to read the record.
System action: The system waits for you to respond.
User response: Go back to the previous panel and try again. If the error persists, contact your system programmer.
System programmer response: Contact your IBM representative.
276
TME 10 OPC Messages and Codes
EQQT025E Ÿ EQQT106I
EQQT025E WORK DAY END TIME MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT026E SPECIFY A VALID DAY OR DATE IN USER DEFINED FORMAT
Explanation: A valid week day or specific date must be given in the user specified format.
EQQT030E END DATE MUST BE LESS THAN FOUR YEARS FROM CURRENT DATE
Explanation: You specified a time span, from current date to end date, that exceeded four years.
System action: The system waits for you to respond.
User response: Specify an end date less than four years from the current date.
EQQT031E THE END DATE IS PRIOR TO CURRENT DATE
Explanation: You specified an end date that is prior to the current date.
System action: The system waits for you to respond.
User response: Specify an end date that is after the current date.
EQQT100E PARAMETER MUST BE A PERIOD NAME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT101W PERIOD PERIOD IS BEING UPDATED BY ANOTHER USER
Explanation: You cannot access the period PERIOD because it is being updated by another user.
System action: The system waits for you to respond.
User response: Try again later.
EQQT102I A CALENDAR PERIOD HAS BEEN CREATED
Explanation: A calendar period has been created, and the calendar database has been updated accordingly.
System action: None.
User response: None.
EQQT103I A CALENDAR PERIOD HAS BEEN DELETED
Explanation: A calendar period has been deleted from the calendar database.
System action: None.
User response: None.
EQQT106I A CALENDAR PERIOD HAS BEEN UPDATED
Explanation: A calendar period in the calendar database has been updated as specified.
System action: None.
User response: None.
Chapter 26. EQQTnnn Messages
277
EQQT108E Ÿ EQQT121E
EQQT108E PERIOD PERIOD NOT CREATED - ALREADY EXISTS
Explanation: The calendar period PERIOD you specified could not be created because it already exists in the
calendar database.
System action: The system waits for you to respond.
User response: Enter a unique period name. If you want to create versions of an already existing period, you
should use the copy function.
EQQT110E LIST OF ORIGIN DATES CONTAINS DUPLICATES
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT111E ONLY ONE ORIGIN DATE CAN BE SPECIFIED IN CYCLIC PERIODS
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT112E ORIGIN DATE MUST BE SPECIFIED
Explanation: You have not specified an origin date.
System action: The request is rejected.
User response: Specify the required origin date.
EQQT113E INTERVAL INCONSISTENT WITH TYPE OF PERIOD
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT114E CYCLIC TYPE MUST BE ANY OF THE LISTED VALUES
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT115E PERIOD NAME IS MISSING OR INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT116E THE VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQT117E THE VARIABLE TABLE IS NOT DEFINED TO OPC/ESA
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You have tried to define a variable table ID that does not exist in TME 10 OPC's database.
EQQT118E YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE
Explanation: You have attempted to refer to a JCL variable table. To do this, you need read authority to the JCL
variable table database.
System action: The system waits for you to respond.
User response: Contact your security administrator if you need to refer to JCL variable table names.
EQQT121E NON-CYCLIC PERIOD INTERVALS MUST NOT OVERLAP
Explanation: You have entered a period interval origin or end date within an already existing interval.
System action: The request is rejected.
User response: Change the interval origin or end date so that it falls outside other intervals.
278
TME 10 OPC Messages and Codes
EQQT122E Ÿ EQQT307E
EQQT122E NON-CYCLIC PERIOD INTERVAL END DATE MUST NOT PRECEDE ORIGIN DATE
Explanation: The interval end date is prior to the associated origin date.
System action: The request is rejected.
User response: Change the interval end date, or the interval origin date, so that the interval end date is later than
the interval origin date.
EQQT123E INTERVAL END DATE MAY NOT BE SPECIFIED FOR CYCLIC PERIODS
Explanation: You have entered an interval end date for a cyclic period, and this is only allowed for noncyclic
periods.
System action: The request is rejected.
User response: Erase the interval end date specified, or change the period type to noncyclic.
EQQT305E DAY STATUS MUST BE SPECIFIED AS OCHWORK OR OCHFREE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
ochwork is the national language character for 'W' (workday); ochfree is for 'F' (free day).
| EQQT307E CALENDAR MUST CONTAIN AT LEAST ONE WORK DAY
| Explanation: A calendar must contain at least one work day, but the calendar you are trying to create has none.
| System action: No calendar is created. TME 10 OPC processing continues.
| System programmer response: None.
| User response: Make sure that the calendar definition specifies at least one work day, then re-create the calendar.
Chapter 26. EQQTnnn Messages
279
280
TME 10 OPC Messages and Codes
EQQU000E Ÿ EQQU044I
Chapter 27. EQQUnnn Messages
EQQU000E YOU ARE NOT AUTHORIZED TO USE FUNCTION UUFUNC
Explanation: You have attempted to use function uufunc but you are not authorized to do so.
System action: The request is rejected.
User response: Contact your security administrator if you want to use uufunc.
EQQU005I THE REQUEST TO UUFUNC OF UUUSUBS IS HANDLED
Explanation: This confirms that your request has been processed.
System action: The requested action is carried out.
User response: None.
EQQU040E THE SUBTASK HAS TERMINATED
Explanation: The request you have made was not accepted by the subsystem because the NMM has terminated.
System action: The request is rejected.
Problem determination: Review the TME 10 OPC message log for messages concerning the NMM.
User response: Leave the dialog and contact your system programmer.
System programmer response: Check the TME 10 OPC message log for messages which may explain why the
NMM is not available.
EQQU041I THE FUNCTION IS ALREADY ACTIVE AND ENABLED FOR SERVICE
Explanation: You have attempted to activate the function, but it is already active and enabled for service.
System action: None.
User response: None.
EQQU042I THE FUNCTION IS ALREADY INACTIVE AND DISABLED FOR SERVICE
Explanation: You have attempted to deactivate the function, but it is already inactive and disabled for service.
System action: None.
User response: None.
EQQU044I AUTOMATIC RECOVERY UNAVAILABLE: CHECK OPCOPTS INIT. STATEMENT
Explanation: Automatic recovery is unavailable because RECOVERY(NO) is specified on the OPCOPTS
initialization statement.
System action: The request is rejected.
User response: Contact your system programmer if automatic recovery is required.
System programmer response: Change OPCOPTS initialization statement to RECOVERY(YES).
 Copyright IBM Corp. 1991, 1998
281
282
TME 10 OPC Messages and Codes
EQQV000E Ÿ EQQV005E
Chapter 28. EQQVnnn Messages
EQQV000E DUPLICATE NAMES IN THE ROUTOPTS SNA DESTINATIONS
Explanation: At least one name in the SNA keyword destination list in the ROUTOPTS init statement is a duplicate
of an already specified name. These names are the application names of potential session partners and must be
unique.
System action: NCF processing is terminated.
System programmer response: Correct the name(s) in error and then restart the subsystem.
EQQV001I NCF APPLICATION STARTED
Explanation: The NCF task has received control from the TME 10 OPC subsystem and is about to start initialization
processing.
System action: NCF processing continues.
User response: None.
EQQV002E NCF APPLICATION TERMINATED - SETLOGON EXECUTION FAILURE
Explanation: A VTAM SETLOGON macro used for enabling NCF logon processing has failed. The reason for this
failure is defined in detail by message EQQV015E which precedes this message in the TME 10 OPC message log.
System action: NCF processing is terminated.
Problem determination: Review message EQQV015E to determine the exact reason for the failure.
System programmer response: Correct the error(s) and then restart the subsystem.
EQQV003E INITIALIZATION FAILED - SNA DESTINATION NOT SPECIFIED IN TRROPTS
Explanation: In a tracker system, NCF initialization processing failed because no partner application IDs were
specified in the SNAHOST keyword in the TRROPTS statement
System action: NCF processing is terminated.
System programmer response: Add the missing information and restart the subsystem.
EQQV004E NCF APPLICATION TERMINATED - PARAMETER PROCESSING FAILURE
Explanation: NCF initialization processing encountered an error in the parameters defined for it.
System action: NCF processing is terminated.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for the failure.
System programmer response: Correct all errors and then restart the subsystem.
EQQV005E NCF APPLICATION TERMINATED - INITIALIZATION PROCESSING FAILURE
Explanation: NCF initialization processing failed. Messages issued preceding this message define the cause of the
failure.
System action: NCF processing is terminated.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for the failure.
System programmer response: Correct all errors and then restart the subsystem.
 Copyright IBM Corp. 1991, 1998
283
EQQV006I Ÿ EQQV012E
EQQV006I NCF APPLICATION ENDED
Explanation: NCF processing has completed and control is returned to the TME 10 OPC subsystem.
System action: NCF processing is terminated.
User response: None.
EQQV007E INITIALIZATION FAILED - SNA DESTINATION NOT SPECIFIED IN ROUTOPTS
Explanation: In a controller system, NCF initialization processing failed because no partner application IDs were
specified in the SNA keyword in the ROUTOPTS statement.
System action: NCF processing is terminated.
System programmer response: Add the missing information and restart the subsystem.
EQQV008I INITIALIZATION FAILED - SUBSYSTEM STOP REQUESTED
Explanation: NCF received a subsystem stop request while in the initialization phase. NCF was most likely waiting
for some other TME 10 OPC resource to become active.
System action: NCF processing is terminated.
User response: None.
EQQV009E INITIALIZATION FAILED - NCFAPPL KEYWORD NOT SPECIFIED OR INVALID
Explanation: NCF initialization processing failed because the NCFAPPL keyword was not specified or was invalid.
System action: NCF initialization processing is terminated.
System programmer response: Add the missing information and then restart the subsystem.
EQQV010E NIB BUILD PROCESSING FAILED - R15 = R15
R00 = R00
Explanation: The GENCB macro request issued to generate a NIB block did not complete normally.
System action: NCF processing is terminated.
Problem determination: Use the R15 and R00 return codes to determine the cause of the error. For more
information, refer to the appropriate documentation for the VTAM product installed on this MVS/ESA system.
System programmer response: If insufficient main storage was the cause of the failure, increase the region size
and then restart the TME 10 OPC subsystem. For any other cause of the failure, contact your IBM representative.
EQQV011E RPL BUILD PROCESSING FAILED - R15 = R15
R00 = R00
Explanation: The GENCB macro request issued to generate an RPL block did not complete normally.
System action: NCF processing is terminated.
Problem determination: Use the R15 and R00 return codes to determine the cause of the error. For more
information, refer to the appropriate documentation for the VTAM product installed on this MVS/ESA system.
System programmer response: If insufficient main storage was the cause of the failure, increase the region size
and then restart the TME 10 OPC subsystem. For any other cause of the failure, contact your IBM representative.
EQQV012E NIB EXLST BUILD PROCESSING FAILED - R15 = R15
R00 = R00
Explanation: The GENCB macro request issued to generate a NIB EXLST block did not complete.
System action: NCF processing is terminated.
Problem determination: Use the R15 and R00 return codes to determine the cause of the error. For more
information, refer to the appropriate documentation for the VTAM product installed on this MVS/ESA system.
System programmer response: If insufficient main storage was the cause of the failure, increase the region size
and then restart the TME 10 OPC subsystem. For any other cause of the failure, contact your IBM representative.
284
TME 10 OPC Messages and Codes
EQQV013E Ÿ EQQV016E
EQQV013E ACB EXLST BUILD PROCESSING FAILED - R15 = R15
R00 = R00
Explanation: The GENCB macro request issued to generate a ACB EXLST block did not complete normally.
System action: NCF processing is terminated.
Problem determination: Use the R15 and R00 return codes to determine the cause of the error. For more
information, refer to the appropriate documentation for the VTAM product installed on this MVS/ESA system.
System programmer response: If insufficient main storage was the cause of the failure, increase the region size
and then restart the TME 10 OPC subsystem. For any other cause of the failure, contact your IBM representative.
EQQV014E ACB BUILD PROCESSING FAILED - R15 = R15
R00 = R00
Explanation: The GENCB macro request issued to generate the NCF ACB did not complete normally.
System action: NCF processing is terminated.
Problem determination: Use the R15 and R00 return codes to determine the cause of the error. For more
information, refer to the appropriate documentation for the VTAM product installed on this MVS/ESA system.
System programmer response: If insufficient main storage was the cause of the failure, increase the region size
and then restart the TME 10 OPC subsystem. For any other cause of the failure, contact your IBM representative.
EQQV015E VTAM MACRO REQUEST FAILURE - DIAGNOSTIC INFORMATION: NODE= NODE, REQUEST=
X'REQ' (NAMEREQ), RTNCD= X'RC' (DECRC) FDBK2= X'FDBK2' (DFDBK2), SSENSMI= SMI
USENSEI= USEI, SSENSEI= SSEI R00= X'R00', R15= X'R15'
Explanation: An error occurred when a VTAM request was executed or scheduled. The variable items in the
message provide diagnostic information and have the following meanings:
NODE
REQ
NAMEREQ
RC
DECRC
FDBK2
DFDBK2
SMI
USEI
SSEI
R00
R15
NCF application LU-name
VTAM request code in hexadecimal
VTAM request name
RTNCD feedback field value from RPL in hexadecimal
RTNCD feedback field value from RPL in decimal
FDBK2 feedback field value from RPL in hexadecimal
FDBK2 feedback field value from RPL in decimal
System sense modifier information from RPL
User sense information from RPL
System sense information from RPL
Register 0 return code after a VTAM macro request
Register 15 return code after a VTAM macro request.
System action: The action taken depends on the severity of the error situation. NCF attempts to continue
processing, if at all possible. For the most serious errors, such as undefined feedback code, NCF abends with a
dump and user code.
Problem determination: Use the diagnostic information in the message to determine the cause of the error. For
more information, refer to the appropriate documentation for the VTAM product installed on this MVS/ESA system.
System programmer response: Analyze the diagnostic information, and the dump if produced, to determine the
cause of the failure. If this was not a user error, contact your IBM representative.
EQQV016E NAMEREQ REQUEST FAILURE - LU/APPLICATION
NODE NOT FOUND
Explanation: The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE could not
be found. The most likely reason for the failure is an invalid specification of an LU-name in the SNAHOST keyword of
the TRROPTS initialization statement. Or, the name NODE has not been properly defined to VTAM.
System action: NCF processing is terminated.
System programmer response: Review the name specified in the SNAHOST keyword. Make sure that it is correct
and that a counterpart exists in the VTAM definition statements. Correct the items in error and then restart NCF.
Chapter 28. EQQVnnn Messages
285
EQQV017E Ÿ EQQV022E
EQQV017E NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE NOT ACTIVE
Explanation: The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE was not
active.
System action: NCF processing is terminated.
System programmer response: Investigate why NODE suddenly became inactive. Restart NCF when NODE is
active again.
EQQV018E NAMEREQ REQUEST FAILURE - VTAM ERROR, OR NCP/VTAM
. INCOMPATIBILITY
Explanation: The VTAM NAMEREQ request failed to complete successfully because there was an error in VTAM, or
an NCP/VTAM incompatibility. This message is preceded by message EQQV015E in the TME 10 OPC message log.
System action: NCF processing is terminated.
Problem determination: Refer to message EQQV015E to determine the cause of the failure.
System programmer response: Restart NCF when the VTAM errors have been corrected.
EQQV019E SESSION SETUP FAILED - PLU=LU NOT AVAILABLE
Explanation: NCF has not been able to establish a session because either:
Ÿ The TME 10 OPC controller is not started
Ÿ The NCF task in the TME 10 OPC controller is not available
Ÿ The LU specified in the SNAHOST keyword of the TRROPTS initialization is not active or is not defined.
NCF retries every 10 seconds until it is successful, or until the subsystem is stopped, or NCF is deactivated.
System action: NCF continues to attempt to establish the LU-LU session.
System programmer response: Review the name specified in the SNAHOST keyword of the TRROPTS
initialization statement. and make sure that it is the correct one. If it is correct, have the system operator at the
TME 10 OPC controller system activate the required resource.
EQQV020I ACB SUCCESSFULLY CLOSED
Explanation: NCF has been successfully disconnected from VTAM.
System action: NCF termination processing continues.
EQQV021W UNABLE TO CLOSE ACB
Explanation: NCF is unable to successfully disconnect from VTAM.
System action: NCF termination processing continues even though the ACB could not be closed.
Problem determination: Most likely a VTAM error has caused this error. Check the system log for VTAM error
messages that can be related to this failure.
System programmer response: None.
EQQV022E LOGON ATTEMPTED BY UNDEFINED LU/APPLICATION LU - CLSDST ISSUED
Explanation: A session establishment attempt was made by a remote NCF application unknown to this host TME 10
OPC subsystem. This message is only issued for a NCF application at an TME 10 OPC host.
System action: The request for the session is turned down by issuing a CLSDST macro. Processing continues for
the TME 10 OPC host NCF application.
Problem determination: It is most likely that a name in the ROUTOPTS SNA keyword list of names has been
misspelled, or left out entirely.
System programmer response: Stop the NCF subtask for which erroneous specifications have been given. Correct
the specifications on the ROUTOPTS statement and then restart NCF.
286
TME 10 OPC Messages and Codes
EQQV023E Ÿ EQQV028W
EQQV023E LOGON REQUEST FOR LU/APPLICATION LU THAT IS ACTIVE - CLSDST ISSUED
Explanation: A session establishment attempt is made from a remote NCF application that is already in session with
the TME 10 OPC host NCF application. This message is only issued for a NCF application at an TME 10 OPC host.
System action: The request for a session is turned down, and NCF processing continues.
Problem determination: The most likely reason for this error is that more than one remote NCF application has the
same LU-name specified. Check the NCFAPPL keyword of the OPCOPTS statement for all remote NCF applications,
and make sure that they are unique.
System programmer response: Stop all NCF tasks that have incorrect NCFAPPL keyword specifications. Correct
the NCFAPPL specifications and then restart the NCF tasks.
EQQV024I ACB SUCCESSFULLY OPENED
Explanation: NCF has successfully established contact with VTAM, and is ready for further VTAM processing.
System action: NCF processing continues.
User response: None.
EQQV025I ACB OPEN FAILURE (RC=X'RC') - VTAM SHUTTING DOWN
Explanation: NCF was unable to establish contact with VTAM due to an OPEN ACB failure. RC is the ACB error
flag value in hexadecimal.
System action: NCF processing continues.
User response: None.
EQQV026E ACB OPEN FAILURE (RC=X'RC') - NCF IMPROPERLY DEFINED
Explanation: NCF was unable to establish contact with VTAM due to an OPEN ACB failure. RC is the ACB error
flag value in hexadecimal.
System action: NCF processing is terminated.
Problem determination: Use the return code to determine the cause of the error. For more information, refer to the
appropriate documentation for the VTAM product installed on this MVS/ESA system.
System programmer response: Correct the problem and restart TME 10 OPC.
EQQV027E ACB OPEN FAILURE (RC=X'RC') - ABEND 1104 DUE TO SERIOUS ERROR
Explanation: NCF was unable to establish contact with VTAM due to an OPEN ACB failure. RC is the ACB error
flag value in hexadecimal.
System action: NCF processing is abnormally terminated with a dump (abend code 1104).
Problem determination: Use the R15 and R00 return codes to determine the cause of the error. For more
information, refer to the appropriate documentation for the VTAM product installed on this MVS/ESA system.
System programmer response: Analyze the 1104 abend dump. If this was not a user error, contact your IBM
representative.
EQQV028W ACB OPEN FAILED FOR THE LAST 2 MINUTES - VTAM NOT ACTIVE
Explanation: NCF failed to establish contact with VTAM during the last two minutes because VTAM was not active.
NCF attempts to establish contact every 10 seconds until contact is made. This message is issued every two minutes
until contact is made.
System action: NCF continues to attempt to establish contact with VTAM until contact is made, or until the TME 10
OPC subsystem is stopped.
System programmer response: Ask your network operator to activate VTAM.
Chapter 28. EQQVnnn Messages
287
EQQV029I Ÿ EQQV037I
EQQV029I VTAM TERMINATION, OR NCF DEACTIVATION, STOPPED SESSION SETUP ATTEMPTS
Explanation: Session initiation attempts were stopped because VTAM is terminating, or the NCF application was
deactivated.
System action: NCF continues termination processing.
User response: None.
EQQV031I SUBSYSTEM STOP REQUEST TERMINATED SESSION SETUP ATTEMPTS
Explanation: A remote NCF application was in the process of initiating a session when the subsystem was stopped.
System action: NCF termination processing continues.
Operator response: None.
EQQV032I SUBSYSTEM STOP REQUEST TERMINATED ACB OPEN ATTEMPTS
Explanation: NCF was in the process of establishing contact with VTAM when the subsystem was stopped.
System action: NCF termination processing continues.
Operator response: None.
EQQV033E ACB OPEN FAILED FOR THE LAST 2 MINUTES - NCF APPLICATION NOT ACTIVE
Explanation: NCF failed to establish contact with VTAM during the last two minutes because the NCF application
was not activated. NCF attempts to establish contact every 10 seconds until contact is made. This message is
issued every two minutes until contact is established.
System action: NCF continues to attempt to establish contact with VTAM until contact is made, or until the TME 10
OPC subsystem is stopped.
System programmer response: Have the network operator activate the VTAM LUs.
EQQV034E NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE INHIBITED
Explanation: The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE was
inhibited. The most likely reason for the failure is that the cross-domain NCF partner NODE has been deactivated, or
the partner VTAM system has been taken down.
System action: If NAMEREQ is the REQSESS request, then NCF processing continues with session establishment
attempts every 10 seconds. For other VTAM requests, NCF processing is terminated.
System programmer response: Have the network operator activate the VTAM and/or NCF application on the
cross-domain partner system.
EQQV036I SESSION HOME-DEST ESTABLISHED
Explanation: A session has been established between the home application HOME and the destination application
DEST.
System action: NCF processing continues.
Operator response: None.
EQQV037I SESSION HOME-DEST ENDED
Explanation: The session between the home application HOME and the destination application DEST has ended.
System action: NCF processing continues.
Operator response: None.
288
TME 10 OPC Messages and Codes
EQQV038E Ÿ EQQV043E
EQQV038E DESTINATION LU INCONSISTENTLY SPECIFIED
Explanation: A destination that runs TME 10 OPC NCF has been specified on the ROUTOPTS initialization
statement OPCAV1R2 keyword.
System action: NCF processing continues.
System programmer response: Correct the ROUTOPTS initialization statement keyword OPCAV1R2 and restart
TME 10 OPC.
EQQV039E DESTINATION LU NOT SPECIFIED AS OPC/A V1R2 NEC
Explanation: A destination that runs OPC/A Version 1 Release 2 NEC is not specified on the ROUTOPTS
initialization statement OPCAV1R2 keyword.
System action: NCF processing continues.
System programmer response: Correct the ROUTOPTS initialization statement keyword OPCAV1R2 and restart
TME 10 OPC.
EQQV040I CURRENTLY RUNNING WITH 'LU' AS CONTROLLER
Explanation: The NCF in an TME 10 OPC tracker system has received a controller identification.
System action: NCF processing continues.
User response: None.
EQQV041E THE NCF TASK IGNORED THE FOLLOWING ELEMENT ON THE NCF QUEUE DQE
Explanation: An invalid element has been found by the NCF task. Possibly, the first four bytes of the element do
not match the TME 10 OPC character string 'DQE '. (The fourth byte is a blank space.)
If EQQV039E was issued previously, EQQV041E is issued for all elements containing the destination specified in
EQQV039E.
System action: The NCF task does no more processing of the element, but continues normal processing.
System programmer response: If EQQV039E was issued previously, perform the actions described for that
message. Otherwise, save the TME 10 OPC message log dataset containing this error message, and contact your
IBM representative.
EQQV042E THE NCF TASK IGNORED THE FOLLOWING DATA, RECEIVED FROM 'NODE' DQE
Explanation: The receiving NCF task did not recognize the type of data received from the application. This
message is issued once for every invalid receive operation.
System action: NCF processing continues.
System programmer response: Verify that the session parameters specified in the VTAM LOGMODE table are
valid. Especially check that the rusizes are not zero.
If this message occurs during normal execution and the VTAM LOGMODE definitions are correctly specified, contact
your IBM representative.
EQQV043E INVALID RU-SIZE SPECIFIED IN 'LU' SESSION PARAMETERS
Explanation: The rusizes specified in the session parameters are not valid.
System action: NCF processing continues, but the specified session is not established.
System programmer response: Verify that the rusizes specified in the tracker node are valid. If necessary, specify
different rusizes, then stop and restart the tracker NCF.
Chapter 28. EQQVnnn Messages
289
EQQV044E Ÿ EQQV045E
EQQV044E OPNDST FAILURE WHEN CONFIRMING SESSION WITH TRACKER 'LU'
Explanation: The OPNDST macro issued to confirm session establishment between the NCF controller and a
remote tracker failed. The most likely reason for the failure is that there is no active route back to the tracker from the
controller node, or that the VTAM environment of the tracker requesting the session is going down.
System action: NCF processing continues, and the NCF controller logon exit is ready to handle subsequent logon
attempts from the remote tracker.
System programmer response: Have the network operator activate the necessary links to secure an active route
back to the tracker.
EQQV045E THE NCF TASK HAS BEEN CONTACTED BY AN UNKNOWN DESTINATION: LU
Explanation: The NCF task has recognized a session control request from a destination that is not defined in the
ROUTOPTS or TRROPTS initialization statement. One possible reason for this message is that an APPC program is
attempting to allocate a conversation with another APPC program but is mistakenly using the LU name of the NCF
program.
System action: A bind request from an unknown destination is rejected and NCF processing continues normally. If
an APPC program is attempting to allocate a conversation it will get a failing return code from the APPC service
routine.
Problem determination: Use the name of the unknown destination to determine which program and which location
is attempting to access NCF resources.
System programmer response: If the NCF task should support the destination specified in this message then the
ROUTOPTS or TRROPTS initialization statement should be updated and the TME 10 OPC subsystem should be
restarted. If an APPC program is attempting to allocate a conversation with APPC functions in an TME 10 OPC
Controller system, the owner of the APPC program at the remote location should be informed of the LU name to be
used if APPC services are to be provided. This LU name is defined by an APPCPMxx member in the
SYS1.PARMLIB library.
290
TME 10 OPC Messages and Codes
EQQWL10W Ÿ EQQWL15I
Chapter 29. EQQWLnn Messages
EQQWL10W WORK STATION WSID, HAS BEEN SET TO STAT STATUS
Explanation: The status of a workstation has changed. An authorized user may have changed the status. This
message may also be caused by a system failure or by a workstation becoming available again.
System action: The status of the workstation is changed. This may effect the ongoing work.
User response: If you do not want the workstation to have this status, change the status through the TME 10 OPC
dialog.
EQQWL11I ACTIONS ARE: FAILACT, RERACT, STARTACT
Explanation: The previous message, EQQWL12I, identifies which workstation has a new status. This message
documents the actions defined for the workstation.
FAILACT
Represents the restart policy for started operations at this workstation, specified in installation
parameters or by a manual request to vary the workstation status.
RERACT
Represents the reroute actions for ready operations (status A, R, or *) from this point on.
STARTACT
Represents the actions that will be taken when the workstation is made available again, either
automatically or by a manual activate request.
System action: The actions described in this message are performed for operations on the workstation identified in
message EQQWL12I.
User response: If you want different actions, use the MCP dialog to change them.
EQQWL12I WORK STATION WSID IS MANUALLY VARIED TO STATUS STATUS
Explanation: A user has changed the status of a workstation, using the TME 10 OPC dialog. This message is
followed by EQQWL11, which indicates the restart, reroute, and start actions.
System action: The status of the workstation is changed. If the status is changed to failed or offline, a restart or
reroute action may be performed.
User response: Verify that you want the workstation to have this status.
EQQWL13I REROUTING IN EFFECT FOR WORK STATION WSID
Explanation: The workstation indicated in the message is unavailable to receive work. TME 10 OPC will route work
scheduled for this workstation to another workstation.
System action: Operations will not be started on this workstation.
User response: Verify that the workstation should be unavailable.
EQQWL15I REROUTING IS WITHDRAWN
Explanation: Previously, work scheduled for this workstation was routed to another workstation. Now, this
workstation is available again.
This message may follow message EQQWL10W or EQQWL12I.
System action: Work will now be scheduled on this workstation.
User response: None.
 Copyright IBM Corp. 1991, 1998
291
EQQWL21W Ÿ EQQWL30E
EQQWL21W EVENT EVENT IGNORED FOR WORK STATION WSID
Explanation: An event has been received that is not possible because of the status of the workstation.
You cannot change the status of a workstation to the status that it already has. For example, if a workstation already
has failed status, a failure event will produce this message.
System action: The event is ignored. The workstation status does not change.
User response: Verify that the TME 10 OPC status of the workstation is correct. If the status is incorrect, correct it
with the TME 10 OPC dialog.
EQQWL22I WORK STATION IS IN STATUS STAT
Explanation: This message accompanies message EQQWL21W.
System action: None.
User response: None.
EQQWL23W WORK STATION WSID IS PENDING ONLINE. MANUAL ACTION REQUIRED
Explanation: An automatic online event has been received for the destination that this workstation represents.
Either the workstation status is offline and the WSOFFLINE activate action is MANUAL, or the workstation status is
failed and the WSFAILURE activate action is MANUAL.
This message is information only.
System action: The status of the workstation will not change until you activate it manually from the TME 10 OPC
dialog.
User response: If you want to activate the workstation, use the MCP Work Station communication dialog.
EQQWL24W A FAIL EVENT IS IGNORED. WORK STATION XXXX IS ALREADY OFFLINE
Explanation: A failure event has been received for an XCF workstation that has already been set to offline. Since
the offline event was received first, the workstation will not subsequently change status to failure.
System action: The event is ignored. The workstation status does not change. The WSOFFLINE actions will be
taken.
User response: Verify the reasons for the offline and failure events. If you wish different actions to be taken, review
your WSOFFLINE and WSFAILURE keywords and adjust them as necessary.
EQQWL30E LOOP IN ALTERNATE WORK STATIONS. FIRST WS IS: WSID
Explanation: This workstation has been put in reroute mode. This workstation is part of a circular set of alternate
workstations. (For example, workstation A reroutes to B, B to C, and C to A.)
All of the other workstations in the circle are unavailable. Thus, this workstation must reroute messages to itself. This
is impossible.
System action: No rerouting is performed for the workstation indicated in the message. This may affect the
workload to be scheduled for this workstation.
User response: Use the TME 10 OPC dialog to check the alternate workstation names starting with this workstation.
Correct any workstation specifications that are incorrect.
To make the operations scheduled to start on this workstation eligible for TME 10 OPC scheduling, you must perform
manual actions. If no actions are taken, the operations on this workstation remain in RE status until a workstation
available event is received by the TME 10 OPC controller.
292
TME 10 OPC Messages and Codes
EQQWL31E Ÿ EQQWL40W
EQQWL31E REROUTE ATTEMPT OF OPERATION NAMED OP, WITH APPL IA APPL FAILED
Explanation: Rerouting could not be performed for this operation. Either reroute parameters are incorrect, or an
offline or failure situation caused TME 10 OPC to try to reroute an operation that is not reroutable.
System action: The operation remains in the current status. If the workstation that this operation uses is not active,
the operation is not started.
User response: If the operation should be rerouted, change the reroute parameter.
EQQWL32I NO ALTERNATE WORK STATION FOUND
Explanation: This message follows EQQWL31E. It indicates the specific problem.
System action: None.
User response: None.
EQQWL35E RESTART ATTEMPT OF OPERATION OP, IN APPL APPL FAILED
Explanation: This operation was not restarted successfully, because of incorrect restart parameters.
System action: The operation is set to RE status.
User response: Use the MCP dialog to correct the restart parameters for this application or operation.
EQQWL40W OPERATION JOBNAME, OP IS FORCED TO ENDED IN ERROR STATUS
Explanation: A manual vary offline command was issued for the workstation on which this operation has started.
System action: The status of the operation is set to ended-in-error. The operation may be restarted or rerouted.
Any further tracking information for the operation is ignored.
Restarting or rerouting an operation that has already started may cause an integrity problem.
User response: If the TME 10 OPC reroute and restart actions are inappropriate for this operation, either cancel the
operation or change its status through the TME 10 OPC dialog.
Chapter 29. EQQWLnn Messages
293
294
TME 10 OPC Messages and Codes
EQQW000E Ÿ EQQW006E
Chapter 30. EQQWnnn Messages
EQQW000E NO AUTHORITY TO ACCESS THE WORK STATION DESCRIPTION
Explanation: You have attempted to access the workstation description database, but you are not authorized to
access it. Or, you do not have access authority to at least one of the following TME 10 OPC resources that are used
together with the workstation description database: the application description database, the calendar database, or the
operator instruction database.
System action: The request is rejected and the system waits for you to respond.
User response: Contact your security administrator.
EQQW001E NO AUTHORITY TO UPDATE THE WORK STATION DESCRIPTION
Explanation: You have attempted to update the workstation description database, but you are not authorized to
update it. Or, you do not have access authority to at least one of the following TME 10 OPC resources that are used
together with the workstation description database: the application description database, the calendar database, or the
operator instruction database.
System action: The request is rejected and the system waits for you to respond.
User response: Contact your security administrator.
EQQW002I WORK STATION DESCRIPTION HAS BEEN UPDATED
Explanation: This confirms that the workstation description record was updated and added to the workstation
description database.
System action: None.
User response: None.
EQQW003I WORK STATION DESCRIPTION HAS BEEN DELETED
Explanation: This confirms that the workstation description record has been deleted from the workstation description
database.
System action: None.
User response: None.
EQQW004I WORK STATION DESCRIPTION HAS BEEN CREATED
Explanation: This confirms that the workstation description record has been created and added to the workstation
description database.
System action: None.
User response: None.
EQQW005E DESCRIPTION BEING UPDATED BY ANOTHER USER, TRY LATER
Explanation: You cannot update a workstation description which is being updated by another user.
System action: The system waits for you to respond.
User response: Try again later.
EQQW006E DUPLICATE NAME - WORK STATION DESCRIPTION CANNOT BE CREATED
Explanation: You have attempted to create a workstation description with a name that already exists in the
workstation description database.
System action: The system waits for you to respond.
User response: Use another name for the workstation description.
 Copyright IBM Corp. 1991, 1998
295
EQQW007E Ÿ EQQW013E
EQQW007E UNABLE TO READ WORK STATION DESCRIPTION RECORD
Explanation: The workstation description record could not be read because it may have been deleted by another
user, or an error in the workstation description database made it impossible to read the record.
System action: The system waits for you to respond.
User response: Go back to the previous panel and try again. If the error persists, contact your system programmer.
System programmer response: Contact your IBM representative.
EQQW010W THE JCC INCIDENT FILE IS NOT AVAILABLE. ERROR CODE = ERRCODE
Explanation: The JCC incident log dataset cannot be used; error code ERRCODE gives the reason why. The error
codes are:
001
004
005
006
008
009
012
No incident log dataset name was defined in the JCCOPTS statement.
The incident log dataset could not be allocated.
An unrecoverable error occurred writing to the incident work file.
The incident log dataset could not be unallocated.
The incident log dataset could not be opened.
The incident log work dataset could not be opened.
An unrecoverable I/O error occurred writing to the incident log or the incident work dataset.
System action: JCC continues processing without creating any incident records.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message.
System programmer response: Correct all errors and then restart the JCC.
EQQW011I THE EVENT WRITER ENDED NORMALLY
Explanation: The event writer initialization has completed and the event writer has been requested to stop
execution.
System action: TME 10 OPC processing continues.
User response: None.
EQQW012E THE EVENT WRITER TERMINATED BECAUSE OF UNRECOVERABLE ERRORS
Explanation: The event writer initialization has completed but a severe error caused the event writer to stop
execution.
System action: The event writer terminates execution. Message EQQZ045W is issued.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message.
System programmer response: Correct all errors and then restart the event writer.
EQQW013E DISK SPACE WAS EXHAUSTED ON JCC INCIDENT FILE, DDNAME = DDNAME
Explanation: An end-of-volume error has been detected while writing to the incident log (ddname EQQINCFI) or the
incident work (ddname EQQINCWK) dataset.
System action: If the incident log dataset is full, the JCC continues logging to the incident work dataset. If the
incident work dataset is full, the JCC issues message EQQW010W and stops writing incident log records.
System programmer response: If the incident log dataset is full, either allocate a larger dataset, or release space in
the current dataset.
If the incident work dataset is full, make sure that the JCC can allocate the incident log dataset. Empty the work
dataset by copying its contents to the incident log.
Restart the JCC to continue incident logging.
296
TME 10 OPC Messages and Codes
EQQW014E Ÿ EQQW017E
EQQW014E THE JCC TASK ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC
Explanation: An abend prevented the JCC from processing all SYSOUT datasets for a batch job.
System action: MVS recovery/termination is requested to generate a dump. The JCC attempts to continue normal
operation with the next ending job. The current job is put on the ended-in-error list with an error code of JCCE.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to
determine the cause of the error.
Operator response: Note the job name and job number from the exit record. If necessary, set the correct status for
the job manually.
EQQW015E THE JOB COMPLETION CHECKER COULD NOT FIND ANY SYSOUT DATA SETS FOR JOB
JOBNAME(JOBNUM). REPEATED RETRIES HAVE FAILED
Explanation: The JCC has tried to retrieve SYSOUT datasets for a batch job but no datasets have been returned by
the JES.
System action: No more attempts to retrieve SYSOUT datasets are made for the current job. The JCC attempts to
continue normal operation with the next ending job. The current job will be put on the ended-in-error list with an error
code of JCCE.
Problem determination: In a JES3 system, check that the JCC SYSOUT classes are defined as external writer
classes to JES3.
Operator response: Determine the current status of the job. If necessary, set the correct status for the job
manually.
System programmer response: If necessary, correct any incorrectly specified operands in the JCCOPTS statement
and then restart the JCC.
EQQW016E AN UNRECOVERABLE I/O ERROR OCCURRED. SYNAD MESSAGE FOLLOWS: SYNMSG
Explanation: An I/O error occurred when the event writer was updating the event dataset.
System action: The event writer attempts to continue processing.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate decoumentation for the MVS/DFP product
installed on this MVS/ESA system.
System programmer response: Correct all errors and, if necessary, restart the event writer.
EQQW017E THE EVENT WRITER WAS UNABLE TO OPEN THE EVENT DATA SET
Explanation: The event writer could not open its output dataset, ddname = EQQEVDS.
System action: The event writer issues message EQQW062E and terminates.
Problem determination: Check that ddname EQQEVDS is correctly specified and that the TME 10 OPC started
task is authorized to open the dataset for update.
System programmer response: If necessary restart the event writer.
Chapter 30. EQQWnnn Messages
297
EQQW018E Ÿ EQQW023E
EQQW018E SYSOUT CLASS CLASS IS ALREADY BEING PROCESSED BY ANOTHER JCC TASK
Explanation: A JCC task has been requested to process SYSOUT datasets in a SYSOUT class that is already being
processed by another JCC subtask on the same MVS system. The SYSOUT class can only be processed by one
JCC subtask at a time.
System action: JCC initialization is terminated.
Problem determination: The JCC subtask is started when either JCCTASK(YES) or CATMLVL(step) is defined in
the OPCOPTS statement. When the JCC is started for catalog management actions, the class or classes processed
by this JCC can be defined in the CATMCLAS keyword of the JOBOPTS statement. If CATMCLAS is not defined, the
classes checked by the JCC subtask are automatically determined by TME 10 OPC from the MSGCLASS value of
jobs and started tasks executing on this system.
System programmer response: Check the values of JCCOPTS CHKCLASS and OPCOPTS CATMCLAS of all
TME 10 OPC subsystems started on the system. If you use catalog management at step level, consider including the
CATMCLAS keyword to define the held SYSOUT classes used for production processing. Ensure that you do not
start more than one subsystem with CATMLVL(STEP), unless CATMCLASS is defined with different values for each
subsystem. Correct the error and restart the JCC subtask or the TME 10 OPC subsystem.
EQQW019E A SEVERE ERROR IN THE JCC TASK HAS CAUSED ONE OR MORE EVENTS TO BE LOST
Explanation: An abend in the JCC queue processing routine prevented the JCC from processing all queued jobs.
System action: MVS recovery/termination is requested to generate a dump. The JCC attempts to continue
processing.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to
determine the cause of the error.
Operator response: Check the ready list for the computer workstation that is serviced by the abending JCC task.
Check that all operations that have the started status are in fact executing. If necessary, set the correct status for
jobs that are listed as started but have completed execution.
EQQW021E THE EVENT WRITER OUTPUT DATA SET IS TOO SMALL
Explanation: The event writer requires that the event dataset is large enough to contain at least 100 events. The
dataset defined by the EQQEVDS ddname does not fulfill this requirement.
System action: The event writer processing is terminated. Message EQQW062E is issued.
System programmer response: Allocate a larger event dataset. If necessary, restart TME 10 OPC to pick up the
new event dataset.
EQQW022I THE JOB COMPLETION CHECKER ENDED NORMALLY
Explanation: JCC initialization has completed and the JCC has been requested to stop execution.
System action: TME 10 OPC processing continues.
User response: None.
EQQW023E UNEXPECTED SUBSYSTEM REQUEST RETURN CODES FOR JOB JOBNAME(JOBNUM) REQUEST
TYPE: TYPE, R15: R15, SSOBRETN: SSOBRETN
Explanation: An error occurred when the JCC was retrieving information from the JES about job JOBNAME. The
information request is either a status request (request type = CS), or a process SYSOUT request (request type = SO).
R15 and SSOBRETN are return codes from JES. JCC issues this message because there is no code to handle this
combination of return codes.
System action: An incident record is written to the JCC incident log and the job is flagged as having encountered a
JCC error.
Operator response: Set the correct status for the job manually and delete or re-queue SYSOUT datasets for the job
if necessary.
298
TME 10 OPC Messages and Codes
EQQW024E Ÿ EQQW027E
EQQW024E THE EVENT WRITER ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC
Explanation: An abend prevented the event writer from writing an event record to the event dataset.
System action: MVS recovery/termination is requested to generate a dump. The event writer attempts to continue
normal operation with the next event queued.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to
determine the cause of the error.
Operator response: Note the job name and job number from the exit record. If necessary, set the correct status for
the job manually.
EQQW025W THE EVENT WRITER HAS IGNORED THE FOLLOWING INVALID EXIT RECORD:
EXITREC
Explanation: An invalid event record EXITREC has been found by the event writer. The most likely error is that the
last 4 bytes of the record do not contain the TME 10 OPC character string EQQ3. It is also possible that the first 3
characters of the job ID field do not contain the character string JOB. If the last 4 bytes of the record contain the
character string ERA2, an abend has occurred during the event creation, and the event will contain the following
information:
EXRJOBN
EXRJOBID
EXRCREAT
EXRRDATE+1
EXRRTIME
Name of the abending CSECT
Compile date of the abending CSECT
Compile time of the abending CSECT
Abend code (from SDWACMPC)
Offset in CSECT at which the abend occurred
If the last 4 bytes of the record contain the character string ERU2, the event creation has been called by an
unsupported exit, and the event will contain the following information:
EXRJOBN Name of the unsupported exit.
(Refer to TME 10 OPC Diagnosis Guide and Reference, where the EXR control block is defined.)
System action: The event writer terminates processing of the event, but continues normal processing. If the invalid
event was of the ERA2 or ERU2 type (see explanation above), the events are only created if at least 5 minutes have
passed since the last creation of the same type.
Problem determination: If the message is issued for all events (in which case the event dataset will be empty),
check that the EQQSSCMC module and the event writer are at the same release level.
System programmer response: Save the TME 10 OPC message log dataset (EQQMLOG) containing this error
message and contact your IBM representative.
EQQW026I THE JOB COMPLETION CHECKER STARTED
Explanation: JCC initialization has completed and the JCC is about to start processing.
System action: TME 10 OPC processing continues.
User response: None.
EQQW027E THE JOB COMPLETION CHECKER TERMINATED DUE TO UNRECOVERABLE ERRORS
Explanation: An abend has occurred in the JCC task that is not related to the processing of any specific job.
System action: MVS recovery/termination is requested to generate a dump. JCC processing is terminated.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to
determine the cause of the error.
System programmer response: Correct all errors and then restart the JCC.
Chapter 30. EQQWnnn Messages
299
EQQW028E Ÿ EQQW032E
EQQW028E JOB COMPLETION CHECKER INITIALIZATION FAILED
Explanation: The JCC could not acquire all resources required for normal operation. The most likely cause of this
error is that the JCC message library could not be opened or that the library is incorrectly defined. It is also possible
that there was an error in the JCCOPTS statement.
System action: JCC processing is terminated. Message EQQZ045W is issued.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message.
System programmer response: Correct all errors and then restart the JCC.
EQQW029E JCC FOUND INVALID NUMERICS BETWEEN COLUMNS BCOL AND ECOL IN MEMBER MEMBER IN
THE EQQJCLIB MESSAGE TABLE FILE. INCORRECT RECORD FOLLOWS: MSGREC
Explanation: A message table record contains invalid information and cannot be used.
System action: JCC will not use the incorrect message library member. If the member name is EQQGJCCT,
message EQQW063E is issued. In all other cases, the JCC continues processing.
System programmer response: Correct the message table definition error and replace member MEMBER in the
EQQJCLIB message table dataset.
EQQW030I A DISK DATA SET WILL BE FORMATTED, DDNAME = DDNAME
Explanation: TME 10 OPC has started to format an event dataset or a submit/release dataset for the ddname
DDNAME.
System action: TME 10 OPC processing continues.
User response: None.
EQQW031E JCC ALLOCATION OF A SYSOUT DATA SET FAILED FOR JOBNAME(JOBNUM) DYNAMIC
ALLOCATION ERROR CODE: RETC, INFORMATION REASON CODE: RSNC
Explanation: The JCC could not allocate a SYSOUT dataset for the job JOBNAME(JOBNUM). The dynamic
allocation error and information reason codes are given in hexadecimal.
System action: An incident record is written to the JCC incident log and the job is flagged as having encountered a
JCC error. The JCC stops processing the current job.
Problem determination: Use the DYNALLOC return code and reason code to determine the cause of the error. For
more information, refer to the appropriate DYNALLOC documentation for the currently active MVS/ESA system.
Operator response: Check that the correct status is set for the job. If necessary, set the status manually.
System programmer response: Look up the meaning of the dynamic allocation error and information reason codes,
and take appropriate action.
EQQW032E THE JOB COMPLETION CHECKER LIBRARY, DDNAME EQQJCLIB, COULD NOT BE OPENED
Explanation: The JCC could not open a required input dataset, ddname EQQJCLIB.
System action: JCC processing is terminated. Message EQQW028E is issued.
Problem determination: Check that EQQJCLIB is correctly defined and that the TME 10 OPC started task is
authorized to open the dataset.
System programmer response: If necessary, restart the JCC.
300
TME 10 OPC Messages and Codes
EQQW033W Ÿ EQQW038I
EQQW033W JOB JOBNAME(JOBNUM) WILL NOT BE RELEASED. REPEATED RETRIES HAVE FAILED
Explanation: The event writer has received a release command on a submit/release dataset and was not able to
release job JOBNAME(JOBNUM) from hold status.
System action: No more attempts to release the job are made. The event writer processing continues.
Operator response: Determine the current status of the job. If necessary, release the job manually.
EQQW034E LRECL FOR THE JOB COMPLETION CHECKER LIBRARY, DDNAME EQQJCLIB, IS NOT VALID
Explanation: The JCC cannot use the message table library dataset because its logical record length is not 80
bytes.
System action: JCC processing is terminated. Message EQQW028E is issued.
System programmer response: Check that EQQJCLIB is correctly defined. Correct all errors and then restart the
JCC.
EQQW035E JCC UNALLOCATION OF A SYSOUT DATA SET FAILED FOR JOBNAME(JOBNUM) DYNAMIC
ALLOCATION ERROR CODE: RETC, INFORMATION REASON CODE: RSNC
Explanation: An error occurred when the JCC was deallocating a SYSOUT dataset for the job
JOBNAME(JOBNUM). The dynamic allocation error and information reason codes are given in hexadecimal.
System action: An incident record is written to the JCC incident log and the job is flagged as having encountered a
JCC error. The JCC stops processing the job.
Problem determination: Use the DYNALLOC return code and reason code to determine the cause of the error. For
more information, refer to the appropriate DYNALLOC documentation for the currently active MVS/ESA system.
Operator response: Check that the correct status is set for the job. If necessary, set the status manually.
EQQW036E JCC OPEN OF A SYSOUT DATA SET FAILED FOR JOBNAME(JOBNUM) DDNAME: DDNAME,
DSNAME: DSNAME
Explanation: An error occurred when the JCC was trying to open a SYSOUT dataset for the job
JOBNAME(JOBNUM).
System action: An incident record is written to the JCC incident log and the job is flagged as having encountered a
JCC error. The JCC stops processing the job.
Operator response: Check that the correct status is set for the job. If necessary, set the status manually.
System programmer response: Determine the reason for the JCC open failure. Correct all errors.
EQQW037E JCC ABEND CODE ABCODE OPENING A SYSOUT DATA SET FOR JOBNAME(JOBNUM) DDNAME:
DDNAME, DSNAME: DSNAME
Explanation: An serious error occurred when the JCC was trying to open a SYSOUT dataset for the job
JOBNAME(JOBNUM).
System action: An incident record is written to the JCC incident log and the job is flagged as having encountered a
JCC error. The JCC stops processing the job.
Operator response: Check that the correct status is set for the job. If necessary, set the status manually.
System programmer response: Determine the reason for the abend. Correct all errors.
EQQW038I A DISK DATA SET HAS BEEN FORMATTED, DDNAME = DDNAME
Explanation: TME 10 OPC has finished formatting an event dataset or a submit/release dataset for the ddname
DDNAME.
System action: TME 10 OPC processing continues.
User response: None.
Chapter 30. EQQWnnn Messages
301
EQQW039E Ÿ EQQW044E
EQQW039E JCC FOUND BAD HEXADECIMAL VALUE BETWEEN COLUMNS BCOL AND ECOL IN MEMBER
MEMBER IN THE EQQJCLIB MESSAGE TABLE FILE. INCORRECT RECORD FOLLOWS: MSGREC
Explanation: A message table record contains invalid information and cannot be used.
System action: The JCC will not use the incorrect message library member. If the member name is EQQGJCCT,
message EQQW063E is issued. In all other cases, the JCC continues processing.
System programmer response: Correct the message table definition error and replace member MEMBER in the
EQQJCLIB message table dataset.
EQQW040W JOB JOBNAME(JOBNUM) WILL NOT BE RELEASED. RELEASE RECORD IS TOO OLD
Explanation: The event writer found a release request in a submit/release dataset that could not be executed
because the request is older than the limit defined to the event writer by the SKIPTIME and SKIPDATE keywords in
the EWTROPTS statement.
System action: The event writer continues reading the submit/release dataset.
Operator response: If necessary, set the correct status for the job manually.
EQQW041W JCL BATCH WITH FIRST JOB JOBNAME WILL NOT BE SUBMITTED BECAUSE SUBMIT RECORD
IS TOO OLD
Explanation: The event writer found job submit records in a submit/release dataset that could not be processed
because the records were older than the limit defined to the event writer by the SKIPTIME and SKIPDATE keywords
in the EWTROPTS statement.
System action: The event writer continues reading the submit/release dataset.
Operator response: If necessary, resubmit the job.
EQQW042W JCL BATCH WITH FIRST JOB JOBNAME WILL NOT BE SUBMITTED BECAUSE THE EVENT
WRITER DID NOT RECEIVE ALL SUBMIT RECORDS
Explanation: The event writer found job submit records in a submit/release dataset that could not be processed
because some submit records were missing.
System action: The event writer continues reading the submit/release dataset.
Problem determination: Check that only one TME 10 OPC system is updating this submit/release dataset.
Operator response: If necessary, resubmit the job.
EQQW043E THE EVENT WRITER WAS UNABLE TO OPEN THE SUBMIT/RELEASE DATA SET
Explanation: The event writer could not open its input dataset, ddname EQQSUDS.
System action: The event writer issues message EQQW062E and terminates.
Problem determination: Check that ddname EQQSUDS is correctly defined and that the TME 10 OPC started task
is authorized to open the dataset.
System programmer response: If necessary, restart the event writer.
EQQW044E UNEXPECTED ERROR SUBMITTING JOB JOBNAME TO THE JES INTERNAL READER
Explanation: An error occurred when submitting the job JOBNAME to the JES.
System action: TME 10 OPC processing continues.
Operator response: If necessary, submit the job manually.
302
TME 10 OPC Messages and Codes
EQQW045W Ÿ EQQW049E
EQQW045W JCL BATCH WITH FIRST JOB JOBNAME WILL NOT BE SUBMITTED BECAUSE SUBMIT RECORDS
WERE RECEIVED IN INCORRECT ORDER BY THE EVENT WRITER
Explanation: The event writer found job submit records in a submit/release dataset that could not be processed
because the records were not in sequence.
System action: The event writer continues reading the submit/release dataset.
Problem determination: Check that only one TME 10 OPC system is updating this submit/release dataset.
Operator response: If necessary, resubmit the job JOBNAME.
EQQW046E SEQUENCE NUMBER SEQNO IS ALREADY IN USE BY AN EVENT READER SUBTASK
Explanation: At event writer initialization, an event reader was already started with the sequence number specified in
the EWSEQNO keyword of EWTROPTS.
The number specified in the EWSEQNO keyword of EWTROPTS must be unique within the TME 10 OPC subsystem.
System action: The event writer initialization fails. The event writer subtask is terminated.
TME 10 OPC administrator response: Check the ERSEQNO keyword of the ERDROPTS initialization statements
to get a sequence number that is not used. Update the EWSEQNO keyword with a unique sequence number, and
use the TME 10 OPC Modify command to restart the event writer subtask.
EQQW047W SUBMIT/RELEASE RECORDS WERE LOST BECAUSE THE SUBMIT/RELEASE DATA SET
BECAME FILLED WITH UNPROCESSED RECORDS
Explanation: The event writer could not process records in a submit/release dataset as fast as the sending TME 10
OPC system was generating them.
System action: The event writer tries to reposition on the oldest record in the dataset.
Operator response: Determine if any held jobs should be released, and if so, release them manually. Resubmit all
missing jobs.
System programmer response: Allocate a larger submit/release dataset and then restart the event writer.
EQQW048E THE EVENT FILTERING EXIT, EQQUX004, ABENDED AND HAS BEEN DISABLED
Explanation: An abend in the event filtering exit prevented the event writer from writing an event record to the event
dataset.
System action: MVS recovery/termination is requested to generate a dump. The event writer attempts to continue
normal operation with the next event queued but the event filtering exit will not be called again.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to
determine the cause of the error.
Operator response: Note the job name and job number from the exit record. If necessary, set the correct status for
the job manually.
System programmer response: Correct all errors and then restart the event writer.
EQQW049E UNABLE TO FORMAT DATA SET WITH DDNAME DDNAME BECAUSE THE DATA SET IS NOT A
SINGLE EXTENT, DISK RESIDENT, DATA SET
Explanation: TME 10 OPC was unable to format an event dataset or a submit/release dataset for the ddname
DDNAME. A dataset to be formatted must be a disk resident, single extent dataset.
System action: The TME 10 OPC function that uses the dataset fails to initialize correctly.
Operator response: None.
System programmer response: Correct the TME 10 OPC started task procedure and then restart TME 10 OPC.
Chapter 30. EQQWnnn Messages
303
EQQW051E Ÿ EQQW055I
EQQW051E JOB JOBNAME COULD NOT BE SUBMITTED. REASON: AUTHORITY FOR RUSER USER,
SUPPLIED BY USER EXIT EQQUX001, COULD NOT BE DETERMINED
Explanation: A user ID was supplied by the submit exit, EQQUX001, and the job was then sent using the
submit/release dataset to the DRVP macro. The buffer pool was successfully built.
System action: The job is not submitted and normal TME 10 OPC processing continues.
User response: Make sure that the supplied userid is defined to the external security manager.
EQQW052E THE EVENT DATASET, DDNAME DDNAME, LRECL LRECL IS INVALIDLY DEFINED. DATASET IS
NOT USABLE.
Explanation: The event dataset referenced by ddname DDNAME has been allocated with an invalid logical record
length.
System action: Event writer initialization fails.
Problem determination: An event dataset must have a logical record length (LRECL) not less than 100 and not
greater than 32000. Check that the LRECL is within the supported range.
System programmer response: Stop TME 10 OPC, reallocate the dataset and restart TME 10 OPC.
EQQW053E THE SYSOUT ARCHIVING EXIT, EQQUX005, ABENDED AND HAS BEEN DISABLED
Explanation: The sysout archiving exit, EQQUX005, abended while processing a job's SYSOUT dataset. TME 10
OPC has disabled the exit for this type of function for the remainder of the TME 10 OPC session.
System action: MVS recovery/termination is requested to generate a dump. The exit will not be called again for this
particular function but TME 10 OPC processing continues.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to
determine the cause of the error.
System programmer response: Correct the error and, if necessary, restart the JCC subtask using the modify
commands or restart the TME 10 OPC tracker.
EQQW054I THE JOB COMPLETION CHECKER IS BEING STARTED FOR CATALOG MANAGEMENT ACTIONS
Explanation: The job completion checker has been started to perform catalog management step level restart
functions, because the JOBLOGRETRIEVAL keyword in the OPCOPTS initialization statement has been set to a
value other than NONE and the JCC was not requested to be started by initialization statements set by the user. This
message is issued either when TME 10 OPC is started, or when the JCC subtask is started with an MVS modify
command.
System action: The Job Completion Checker is started.
User response: None.
EQQW055I THE JOBLOG FOR JOBNAME JOBNUM DOES NOT CONTAIN ALL DATASETS REQUIRED BY THE
OPC/ESA CATALOG MANAGEMENT FUNCTION
Explanation: The Job Completion Checker has discovered that the joblog for the current job does not contain all
joblog datasets needed by TME 10 OPC. The required datasets are JESJCL and JESYSMSG, and one or both of
them are missing.
System action: The Job Completion Checker processing continues.
System programmer response: Verify that either the JES installation setup or the job does not suppress JESJCL
and/or JESYSMSG files from being created.
304
TME 10 OPC Messages and Codes
EQQW056I Ÿ EQQW063E
EQQW056I JOBNAME JOBNUM HAS NO HELD SYSOUT IN CLASS CLASS
Explanation: The CATMCLAS keyword specifies the SYSOUT class CLASS, but job JOBNAME with job ID
JOBNUM created nonheld output in this class.
System action: The job is tracked as normal, but the joblog cannot be sent to the controller.
Problem determination: If the joblog output for the job is a held SYSOUT class, ensure the most current
EQQSSCMC lmod is active (see the SSCMNAME parameter).
System programmer response:
Ensure that the CATMCLAS keyword specifies only held SYSOUT classes.
EQQW060E SUBMIT/RELEASE SKIP LIMIT DATE OR TIME SKIPLIM IS NOT VALID
Explanation: Initialization of the event writer failed because an operand of the SKIPDATE or SKIPTIME keyword in
the EWTROPTS statement was incorrectly specified.
System action: The event writer processing is terminated.
Problem determination: None.
System programmer response: Correct the operand in the EWTROPTS statement and then restart the event writer.
EQQW061W THE EVENT FILTERING EXIT LOAD MODULE, MODULE, COULD NOT BE LOADED
Explanation: The event writer could not locate the event filtering exit load module, EQQUX004.
System action: The event filtering exit will not be used by the event writer.
Problem determination: None.
System programmer response: If the event filtering exit is meant to be used, make sure that the EQQUX004 load
module is present in a library that can be reached by TME 10 OPC. Correct all errors and, if necessary, restart the
event writer.
EQQW062E EVENT WRITER INITIALIZATION FAILED
Explanation: The event writer could not acquire all resources required for normal operation. The most likely cause
of this error is that the event dataset or a submit/release dataset could not be opened. It is also possible that there
was an error in the EWTROPTS statement.
System action: The event writer processing is terminated. Message EQQZ045W is issued.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message.
System programmer response: Correct all errors and then restart the event writer.
EQQW063E THE JOB COMPLETION CHECKER WAS UNABLE TO BUILD THE GENERAL MESSAGE TABLE
Explanation: An error occurred while processing the JCC general message table. The general message table is
defined by member EQQGJCCT in the library defined by the EQQJCLIB DD statement.
System action: JCC initialization fails.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message.
System programmer response: Correct all errors and then restart the JCC.
Chapter 30. EQQWnnn Messages
305
EQQW064E Ÿ EQQW069E
EQQW064E THE JOB COMPLETION CHECKER WAS UNABLE TO BUILD THE JOB MESSAGE TABLE FOR
JOB JOBNAME(JOBNUM)
Explanation: An error occurred while processing the JCC message table for the specified job. The job message
table is defined by member JOBNAME in the library defined by the EQQJCLIB DD statement.
System action: An incident record is written to the JCC incident log and the job is flagged as having encountered a
JCC error.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message.
Operator response: Set the correct status for the job manually, and if necessary, delete or re-queue SYSOUT
datasets for the job.
System programmer response: Correct all errors in the job message table.
EQQW065I EVENT WRITER STARTED
Explanation: The event writer initialization has completed and the event writer is now about to start processing.
System action: TME 10 OPC processing continues.
User response: None.
EQQW066E JCC WAS UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF EQQJCLIB
Explanation: An error occurred when allocating storage for a job message table.
System action: Message EQQW064E is issued.
Problem determination: None.
System programmer response: Stop TME 10 OPC and then restart it in a larger region.
EQQW067E A SEVERE ERROR IN THE EVENT WRITER HAS CAUSED LOSS OF CSA EVENT BUFFERS
Explanation: An abend in the event writer queue processing routine prevented the event writer from returning all
event buffers to the free chain.
System action: MVS recovery/termination is requested to generate a dump. The event writer attempts to continue
processing.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to
determine the cause of the error.
System programmer response: None.
EQQW068E JCC WAS UNABLE TO FIND MEMBER MEMBER IN EQQJCLIB MESSAGE TABLE FILE
Explanation: The JCC general message table member, EQQGJCCT, could not be found in the library defined by the
EQQJCLIB DD statement.
System action: Message EQQW063E is issued.
System programmer response: Create a JCC general message table and add it to the EQQJCLIB library.
EQQW069E MEMBER MEMBER IN EQQJCLIB MESSAGE TABLE FILE IS EMPTY
Explanation: The JCC message table member MEMBER exists in the library defined by the EQQJCLIB DD
statement, but there are no records in the member.
System action: If the member name is EQQGJCCT, message EQQW063E is issued. In all other cases, the JCC
continues processing.
System programmer response: If necessary, add the correct message table member to the EQQJCLIB library.
306
TME 10 OPC Messages and Codes
EQQW070I Ÿ EQQW074E
EQQW070I THE EW CANNOT REPOSITION AT RESTART POSITION: CYC REC
Explanation: An event writer is started in event reader mode (with an EWSEQNO). The event writer cannot position
on the event dataset with the event dataset position that it has received. The restart position was probably overwritten
when the event dataset wrapped around.
System action: The event writer continues processing as normal.
TME 10 OPC administrator response: The event dataset may be too small. Make sure it is large enough to hold
all the events generated while the connection between the controller and the tracker with the started event writer is
down.
EQQW071I UNKNOWN RECORD TYPE SKIPPED BECAUSE IT IS TOO OLD
Explanation: The event writer encountered an unknown record type when skipping records of the submit/release
dataset that are too old.
System action: The record is skipped.
User response: None.
EQQW072E EVENT WRITER SEQUENCE NUMBER, EWSEQNO, MUST BE 1 TO 16
Explanation: An invalid sequence number was found in the EWSEQNO keyword of an event writer initialization
statement.
System action: TME 10 OPC initialization is terminated.
System programmer response: Change the sequence number to a number from 1 to 16 that is not already used by
an event reader subtask in the same address space.
EQQW073E IT IS NOT VALID TO START AN EVENT WRITER IN EVENT READER MODE WITH THIS TYPE OF
HOST CONNECTION
Explanation: The TME 10 OPC configuration does not support starting an event writer in event reader mode. When
the event writer is started with the EWSEQNO, it will try to pass events directly to the controller. EWSEQNO can only
be used in these circumstances:
Ÿ The event writer is started in the same address space as the controller.
Ÿ XCF connections. The event writer is started at a tracker system connected to the controller using XCF
communication links.
Ÿ SNA connections.. The event writer is started at a tracker system connected to the controller using VTAM.
System action: Event writer initialization terminates.
System programmer response: Remove the EWSEQNO keyword from the EWTROPTS initialization statement.
EQQW074E THE SUBMIT/RELEASE DATA SET WITH DDNAME = DDNAME IS TOO SMALL
Explanation: The submit/release dataset must be large enough to contain 100 records.
System action: The workstation analyzer processing stops. Message EQQW502E is issued.
Problem determination: None.
System programmer response: Stop TME 10 OPC. Allocate a larger submit/release dataset. Start TME 10 OPC
again.
Chapter 30. EQQWnnn Messages
307
EQQW075W Ÿ EQQW101E
EQQW075W THE HEADER RECORD IN FILE DDNAME IS INCOMPATIBLE WITH THE DEVICE TYPE
Explanation: The information in the header record does not match the calculated records per tracks value. This is
normally caused by moving the dataset to a different device type.
Note: This message may be issued if you have reallocated the data set using a method that does not put an end of
file at the beginning of the data set. It can then be ignored.
System action: The dataset is reformatted.
User response: None.
EQQW076W NO CONTROLLER PULSE. EVENT WRITER WILL STOP PULSE DETECTION
Explanation: The message can only be issued when ROUTOPTS PULSE processing is active for Tracker systems
on OPC/ESA Release 3 level or higher. There are two situations that can cause this message to be issued:
1. When handshake processing is in use, each connected Tracker system sends an identification (ID) event to the
controller at the specified interval defined by the PULSE keyword, and the controller responds to the Tracker
system. If the tracker detects that the controller has not responded to two consecutive ID events this message is
issued. This indicates that there is a problem in the controller address space, or that the communication vehicle
has failed.
2. When a tracker has a blank destination, that is when a tracker is started in a separate address space and not
receiving work from the controller, the tracker will wait for two default intervals (2 x 10 minutes) and then issue the
message.
Note: When a tracker is connecting via XCF, this message may be issued without indicating a problem.
System action: The event writer subtask will stop sending handshake events.
System programmer response: If the TME 10 OPC controller address space is active, check the message log
dataset for error messages or communication failures. Restart the controller if required. If the tracker issuing this
message has a blank destination ID, the message can be ignored.
Note that the startup of the tracker and the controller must be synchronized. However, in a DASD environment using
a submit/release dataset for the catalog management function only, the tracker must be started before the controller to
get the pulsing synchronized.
EQQW077E THE SUBMIT/RELEASE DATASET IS NOT INITIALIZED
Explanation: An TME 10 OPC tracker system tried to update the submit/release dataset, ddname EQQSUDS, but
the dataset is not initialized by the controller. This message is only issued when starting with a new submit/release
dataset.
System action: The event writer initialization fails and the subtask terminates.
User response: Stop the tracker and start the controller in order to initialize the submit/release dataset.
EQQW100E WORK STATION NAME IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The first character in a valid name must be an alphabetic character.
EQQW101E WORK STATION TYPE IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid workstation types are: G for general, C for computer, and P for printer workstation.
308
TME 10 OPC Messages and Codes
EQQW102E Ÿ EQQW111E
EQQW102E WORK STATION REPORTING ATTRIBUTE INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid workstation reporting attributes are:
A
Automatic. Reporting is done by a user program for both start and completion of an operation (for example, a
computer workstation).
S
Manual start and completion. The workstation operator reports when work is started and when it is completed
(for example, a data entry workstation).
C
Manual completion only. The workstation operator reports only when work is completed (for example, a login
workstation).
N
Nonreporting. The workstation does not report on work.
EQQW103E WORK STATION SYSOUT ROUTING INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW104E CONTROL ON PARALLEL SERVERS INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The valid input for control on parallel servers is C for control, P for planning, B for both planning and control, or N for
none.
EQQW105E JOB INTERRUPTION ATTRIBUTE INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid job interruption attributes are Y for yes, and N for no.
EQQW106E JOB SETUP ATTRIBUTE IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid job setup attributes are Y for yes, and N for no.
EQQW107E DESTINATION IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
A destination can only be specified for a computer workstation. Enter a valid destination.
EQQW108E VALID WORK STATION TYPES ARE G, C, AND P
Explanation: For the data entry error, the valid workstation types are: G for General, C for Computer, and P for
Printer workstation.
EQQW109E GENERAL OR PRINTER REQUIRED FOR JOB SPLITTABLE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Only a job on a general or printer workstation can be split, not a job on a computer workstation.
EQQW110E JOB SETUP ALLOWED ONLY IF WORK STATION TYPE IS GENERAL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Job setup is allowed if the workstation type is general, but not if the workstation type is computer or printer.
EQQW111E WORK STATION RESOURCE NAME INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 30. EQQWnnn Messages
309
EQQW112E Ÿ EQQW206E
EQQW112E A PLANNING ATTRIBUTE IS REQUIRED, SPECIFY EITHER Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW113E A CONTROL ATTRIBUTE IS REQUIRED, SPECIFY EITHER Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW114E WORK STATION OPEN INTERVAL INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW115E VALID ATTRIBUTES ARE A, S, C, AND N
Explanation: For the data entry error, the valid workstation reporting attributes are: A for Automatic, S for manual
Start/Stop, C for Completion only, and N for Non-reporting.
EQQW116E DESTINATION REQUIRES COMPUTER OR GENERAL TYPE WITH AUTOMATIC ATTR
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW117E WORK STATION NAME IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW118E NO DESCRIPTION IS ALLOWED WHEN STATUS IS STANDARD
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Only days which have status closed or defined can have an entry in the description field.
EQQW200E THE STANDARD DAY IS NOT DEFINED OR IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
At least one open interval must be defined for the standard day. The standard day cannot be defined as closed.
EQQW201E THE OPEN INTERVAL TABLE CONTAINS DUPLICATE ENTRIES
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW202E DAY OR DATE IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW203E OPEN INTERVAL FOR STANDARD DAY IS INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW204E INTERVALS OVERLAP IN THE OPEN INTERVAL TABLE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW205E OPEN INTERVAL END TIME MUST BE LATER THAN THE START TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW206E OPEN INTERVAL START OR END TIME INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
310
TME 10 OPC Messages and Codes
EQQW207E Ÿ EQQW215E
EQQW207E CAPACITY OF PARALLEL SERVERS INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW208E RESOURCE CAPACITY IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW209E THE STANDARD DAY CANNOT BE CLOSED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW210E ALTERNATE WORK STATION ONLY ALLOWED FOR CPU/WTO TYPE WS
Explanation: You cannot specify an alternate workstation because the current workstation is not a computer
workstation or a general workstation with the WTO attribute.
System action: The database is not updated. All changes are ignored.
User response: None.
EQQW211E THE ALTERNATE WS MUST BE OF THE SAME TYPE
Explanation: You specified an alternate workstation that is not defined in the workstation description database as a
computer type workstation.
System action: The database is not updated. All changes are ignored.
User response: Specify the name of a computer type workstation, or alter the attributes of the workstation in the
workstation description database.
EQQW212E THE ALTERNATE WS IS NOT FOUND IN THE WS DATA BASE
Explanation: The alternate workstation that you specified is not defined in the workstation description database.
System action: The database is not updated. All changes are ignored.
User response: Specify the name of an existing computer type workstation, or add the workstation that you specified
to the workstation description database.
EQQW213E THE CURRENT WS CANNOT BE ALTERNATE TO ITSELF
Explanation: The alternate workstation cannot be the current workstation.
System action: The WS status does not change.
User response: Change the alternate workstation name.
| EQQW214E NODE ADDRESS CANNOT BE SET IF ACCESS METHOD NAME IS BLANK
| Explanation: The node address cannot be set if the access method name is blank. To specify a node address
| value, first set the access method name.
| System action: Processing continues. TME 10 OPC waits for your next input.
| User response: Set the access method name, then set the node address.
| EQQW215E PORT NUMBER CANNOT BE SET IF NODE ADDRESS IS BLANK
| Explanation: The port number cannot be set if the node address is blank. To specify a port number value, first set
| the node address.
| System action: Processing continues. TME 10 OPC waits for your next input.
| User response: Set the node address, then set the port number.
Chapter 30. EQQWnnn Messages
311
EQQW216E Ÿ EQQW306E
| EQQW216E ACCESS METHOD CAN BE SET ONLY IF WORKSTATION TYPE IS 'COMPUTER'
| Explanation: You specifed an access method name. Access method is supported only for "Computer" workstations.
| System action: Processing continues. TME 10 OPC waits for your next input.
| User response: Supply a valid workstation type.
| EQQW217E PORT NUMBER MUST BE NUMERIC AND IN THE RANGE 0-32760
| Explanation: You specified a port number value that was not numeric or was greater than 32760. The port number
| must be a numeric value in the range 0–32760.
| System action: Access-method-specific data is not saved.
| User response: Specify a valid port number.
EQQW300I ALL CLOSED WORK STATIONS HAVE BEEN UPDATED
Explanation: This confirms that “all workstations closed” has been updated.
System action: None.
User response: None.
EQQW301E SOME DATES MAY NOT HAVE BEEN UPDATED
Explanation: Due to a failure in the subsystem, some dates may not have been updated as specified.
System action: The system waits for you to respond.
User response: Exit from the MODIFY ALL WORK STATIONS CLOSED, panel and enter the Work Station dialog
option 4, MODIFY CLOSED again to determine which dates were updated and which were not. Enter the necessary
changes, then retry. If the error persists, contact your system programmer.
System programmer response: Review the TME 10 OPC message log for I/O errors that immediately precede this
message. Correct all errors and then restart TME 10 OPC.
EQQW302E ALL WORK STATION CLOSED ISPF TABLE ERROR. NOTHING UPDATED
Explanation: An ISPF table contains duplicate entries.
System action: The changes are not saved.
User response: Contact your system programmer to ensure that the IBM-supplied panel is used.
System programmer response: Ensure that the IBM-supplied panel is being used.
EQQW303E ANOTHER USER IS UPDATING ALL WS CLOSED, TRY LATER
Explanation: You cannot update the all-work-station-closed database because another user is currently updating it.
System action: The system waits for you to respond.
User response: Try again later.
EQQW304E A VALID DATE MUST BE ENTERED AS CLOSE DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW306E BOTH CLOSED-FROM AND CLOSED-TO TIME MUST BE ENTERED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Both the closed-from date and the closed-to date must be specified.
312
TME 10 OPC Messages and Codes
EQQW307E Ÿ EQQW405E
EQQW307E SPECIFIED FROM-TIME LATER THAN TO-TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
User response: Specify a to-time that is later than the from-time.
EQQW308E DUPLICATE WORK STATION CLOSED DATES EXIST IN TABLE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQW309I ALL WORK STATION CLOSED INFO MISSING, NO ACCESS TO DATA BASE
Explanation: Information about whether or not all workstations are closed for this date could not be retrieved
because you do not have access to the all-work-station-closed database.
System action: None.
User response: None.
EQQW400E WTO OPTION ONLY ALLOWED IF WORK STATION TYPE IS GENERAL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The WTO option is allowed if the workstation type is general, but not if the workstation type is computer or printer.
EQQW401E THE WTO OPTION IS MUTUALLY EXCLUSIVE WITH THE SPECIFIED OPTION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The WTO option is not allowed if the workstation option is job setup, task or splittable.
EQQW402E STARTED TASK OPTION ONLY ALLOWED IF WORK STATION TYPE IS CPU
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Started Task option is allowed if the workstation type is Computer, but not if the workstation type is General or Printer.
EQQW403E THE STC OPTION IS MUTUALLY EXCLUSIVE WITH THE SPECIFIED OPTION
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The STC option is not allowed if the workstation option is job setup, WTO, or splittable.
EQQW404E THIS DESTINATION REPRESENTS AN OPC/A V1R2 NEC SYSTEM
Explanation: The destination specified is defined as an OPC/A Version 1 Release 2 NEC system in the ROUTOPTS
initialization statement. Any work that should be transmitted to such a system must be handled by NJE.
System action: The workstation description is not updated.
System programmer response: If TME 10 OPC should initiate work at this destination, an TME 10 OPC tracker
must be started here. The ROUTOPTS initialization statement must be changed to reflect the new system type.
EQQW405E THIS DESTINATION IS NOT KNOWN TO OPC/ESA
Explanation: The destination specified is not defined to TME 10 OPC in the ROUTOPTS initialization statement.
System action: The workstation description is not updated.
User response: Verify that the destination is correctly specified.
System programmer response: All TME 10 OPC tracker systems connected to the controller must defined in the
ROUTOPTS initialization statement.
Chapter 30. EQQWnnn Messages
313
EQQW406E Ÿ EQQW503I
EQQW406E STARTED TASK OPTION INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The option can be Y (yes) or N (no).
EQQW407E WTO OPTION INVALID OR NOT DEFINED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The option can be Y (yes) or N (no).
EQQW500E THE OPC/ESA JCL LIBRARY, DDNAME EQQJBLIB, COULD NOT BE OPENED
Explanation: TME 10 OPC could not open the JCL library (ddname EQQJBLIB) to read a member.
System action: If the failure occurred during job submission the operation extended status is set to error.
Problem determination: Review the preceding messages in the TME 10 OPC message log for a message
describing an error on the EQQJBLIB file.
User response: Contact your system programmer.
System programmer response: Check that the ddname EQQJBLIB is correctly specified and that the task started
by TME 10 OPC is authorized to open the dataset for input. When the error is corrected, stop TME 10 OPC and
then restart it.
EQQW501E LOGICAL RECORD SIZE FOR THE OPC/ESA JCL LIBRARY, DDNAME EQQJBLIB, IS INVALID
Explanation: TME 10 OPC could not read the JCL library (ddname EQQJBLIB) because the logical record length is
not 80 bytes.
System action: If the failure occurred during job submission the operation extended status is set to error.
Problem determination: Check the definition of the EQQJBLIB DD statement.
User response: Contact your system programmer.
System programmer response: Check that the ddname EQQJBLIB is correctly defined. When the error is
corrected, stop TME 10 OPC and then restart it.
EQQW502E WORK STATION ANALYZER INITIALIZATION FAILED
Explanation: The workstation analyzer could not acquire all the resources required for normal operation. The most
likely cause of this error is that the subsystem is being stopped but the Normal Mode Manager subtask has not
started. It is also possible that a submit/release dataset or the EQQJBLIB dataset could not be opened.
System action: If this message was issued while the TME 10 OPC subsystem was being stopped, subsystem
termination continues normally. Otherwise, message EQQZ045W is issued.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact cause
of the error.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW503I THE WORK STATION ANALYZER ENDED NORMALLY
Explanation: This message is issued if the TME 10 OPC subsystem is being stopped and initialization of the
workstation analyzer has completed successfully. This message is also issued if a request has been made by an
operator modify command to stop the workstation analyzer.
System action: If this message was issued while the TME 10 OPC subsystem was being stopped, subsystem
termination continues normally. Otherwise message EQQZ045W is issued.
System programmer response: None.
314
TME 10 OPC Messages and Codes
EQQW505I Ÿ EQQW511E
EQQW505I THE WORK STATION ANALYZER TASK HAS STARTED
Explanation: The initialization of the workstation analyzer has completed and the workstation analyzer is about to
start processing.
System action: TME 10 OPC processing continues.
System programmer response: None.
EQQW506E OPC/ESA WAS UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF
EQQJBLIB
Explanation: The workstation analyzer was attempting to build a VSAM dataset record to be inserted in the JCL
repository dataset, but it was unable to do so because of insufficient virtual storage.
System action: The operation remains in ready status. The workstation analyzer is unable to submit the job to JES.
User response: Submit the job manually.
System programmer response: Stop TME 10 OPC and then restart in a larger region.
EQQW507W OPC/ESA WAS UNABLE TO SAVE JOB MEMBER IN THE JS DATASET FOR APPL. APPL
Explanation: An error occurred when the workstation analyzer was trying to update the JCL repository dataset.
System action: The job will be submitted to JES, but the JCL repository dataset would not be correctly updated.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW510E WS ANALYZER WAS UNABLE TO READ OR UPDATE CURRENT PLAN JNT RECORD FOR: JOB =
JOBNAME, APPLICATION = APPL, INPUT ARRIVAL = ARRTIME
Explanation: The workstation analyzer encountered a VSAM error when reading or updating the current plan
dataset.
System action: The workstation analyzer continues normal processing with the next ready operation.
Problem determination: Review earlier messages in the TME 10 OPC message log and SYSLOG datasets to
determine the exact cause of this error.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW511E WS ANALYZER WAS UNABLE TO RELEASE JOB JOBNAME(JOBNUM) FROM HOLD
Explanation: The workstation analyzer was unable to communicate successfully with JES while trying to release job
JOBNAME(JOBNUM) from hold.
System action: The hold status of the current job is not changed. The workstation analyzer continues normal
processing.
Problem determination: Check that JES is executing normally.
Operator response: Check that the job is still held by JES. If it is, enter an appropriate operator command to
release the job from hold.
Chapter 30. EQQWnnn Messages
315
EQQW512E Ÿ EQQW517E
EQQW512E WS ANALYZER WAS UNABLE TO READ OR UPDATE CURRENT PLAN OPERATION RECORD
WITH KEY (HEXADECIMAL): F0F3OPRINDEX
Explanation: The workstation analyzer encountered a VSAM error when reading or updating the current plan
dataset.
System action: The workstation analyzer continues normal processing with the next ready operation.
Problem determination: Review earlier messages in the TME 10 OPC message log and SYSLOG datasets to
determine the exact cause of this error.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW513E THE SUBMIT/RELEASE DATA SET WITH DDNAME = DDNAME COULD NOT BE OPENED
Explanation: The workstation analyzer could not open a submit/release dataset with the indicated ddname. The
ddname is defined as a submit/release dataset ddname in one of the computer workstations in the current plan
dataset.
System action: The workstation analyzer issues message EQQW502E and is terminated.
Problem determination: Check that the ddname is correctly specified and that the TME 10 OPC started task is
authorized to open the dataset for update.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW514W TOO MANY SUBMIT/RELEASE DATA SETS DEFINED. DDNAME = DDNAME IS IGNORED
Explanation: More than 16 submit/release dataset ddnames are defined in the current plan dataset.
System action: Only the first 16 submit/release ddnames found are used by the workstation analyzer.
Problem determination: Check that all computer workstations have been correctly defined.
System programmer response: Correct all errors found and, if necessary, restart the workstation analyzer.
EQQW515W THE SUBMIT USER EXIT MODULE, EQQUX001, COULD NOT BE LOADED
Explanation: TME 10 OPC could not locate the job submit exit load module EQQUX001.
System action: The job submit exit will not be used by the workstation analyzer.
System programmer response: If the job submit exit is meant to be used, make sure that the EQQUX001 load
module is present in a library that can be reached by TME 10 OPC. Then restart the workstation analyzer.
EQQW516E THE EQQUX002 EXIT COULD NOT OPEN AN INPUT DATA SET TO READ JOB MEMBER
Explanation: The joblib I/O exit was called and gave a return code indicating that it could not open one of its input
datasets.
System action: The job is not submitted by the workstation analyzer as intended. The operation remains in ready
status.
Problem determination: Check that all DD statements needed by the EQQUX002 exit have been correctly defined
and that the TME 10 OPC started task is authorized to open the dataset for input.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW517E OPC/ESA COULD NOT ALLOCATE STORAGE TO PROCESS JOB MEMBER FOR EQQUX002 EXIT
Explanation: The workstation analyzer was building a VSAM dataset record to be inserted in the JCL repository
dataset but it was unable to do so because of insufficient virtual storage.
System action: The operation remains in ready status. The workstation analyzer is unable to submit the job to JES.
User response: Submit the job manually.
System programmer response: Stop TME 10 OPC and then restart it in a larger region.
316
TME 10 OPC Messages and Codes
EQQW518E Ÿ EQQW522E
EQQW518E THE EQQUX002 EXIT COULD NOT FIND JOB MEMBER IN ANY INPUT DATA SET
Explanation: The workstation analyzer was attempting to submit a job to JES for a ready operation on a computer
workstation. However, no JCL for this operation is saved in the JCL repository dataset, and the joblib I/O exit could
not find the job in any input dataset.
System action: The operation remains in ready status. TME 10 OPC assumes that some other function will submit
the job to JES.
Problem determination: Check that all DD statements needed by the EQQUX002 exit have been correctly defined
and that all required members are defined.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW519W THE EQQUX002 EXIT DID NOT RETURN ANY DATA FOR JOB MEMBER
Explanation: The joblib I/O exit was called to retrieve a job to be submitted, but the exit did not return any data.
System action: The job is not submitted by the workstation analyzer as intended. The operation remains in ready
status.
Problem determination: Check that the joblib I/O exit has been correctly installed and that it works properly.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW520E THE EQQUX002 EXIT RETURNED THE FOLLOWING I/O ERROR MESSAGE FOR JOB MEMBER:
PLUSMSG
Explanation: The joblib I/O exit was called to retrieve a job to be submitted, but the exit gave a return code
indicating that an I/O error had occurred on an input dataset.
System action: The job is not submitted by the workstation analyzer as intended. The operation remains in ready
status.
Problem determination: Check that the joblib I/O exit can access all required input datasets and that it works
properly.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart the workstation analyzer.
EQQW521E THE JOBLIB I/O USER EXIT MODULE, EQQUX002, COULD NOT BE LOADED
Explanation: TME 10 OPC could not locate the joblib I/O exit load module, EQQUX002.
System action: The joblib I/O exit will not be used by the workstation analyzer.
User response: If necessary, submit the job manually.
System programmer response: If the joblib I/O exit is meant to be used, make sure that the EQQUX002 load
module is present in a library that can be reached by TME 10 OPC. Then restart the workstation analyzer.
EQQW522E JOB MEMBER RETURNED BY THE EQQUX002 EXIT EXCEEDS MAXIMUM SUPPORTED SIZE
Explanation: The joblib I/O exit was called to retrieve a job to be submitted, but the job returned exceeds the
maximum supported size, which is 256 KB (kilobytes) of data.
System action: The job is not submitted by the workstation analyzer as intended. The operation remains in ready
status.
Problem determination: Check that the joblib I/O exit has been correctly installed and that it works properly.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and then restart the workstation analyzer.
Chapter 30. EQQWnnn Messages
317
EQQW523E Ÿ EQQW529E
EQQW523E JOB MEMBER IN APPLICATION APPL IS TOO LARGE TO BE SAVED ON THE JS DATA SET
Explanation: A job that is about to be submitted to JES is too large to be saved in the JCL repository dataset.
System action: The job will be submitted but the JCL repository data will not be updated.
Problem determination: Use the IDCAMS LISTCAT function to determine the maximum size of records in the
dataset defined by the EQQJSxDS DD statement. Use dialog option 6.6 to determine the current JCL repository.
System programmer response: If necessary, allocate a new JCL repository dataset with a larger maximum record
size. Refer to TME 10 OPC Customization and Tuning for instructions.
| EQQW524E JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE THE EQQUX001
|
EXIT RETURNED A NONZERO ERROR CODE
| Explanation: The job submit exit was called and returned an error code different from '0000'.
| System action: The job is not submitted, and its error status is set to the error code that was returned by the submit
| exit job.
| User response: Check why the submit exit job, EQQUX001, stopped submission.
EQQW525E JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE OF AN ERROR IN
THE JOB CARD
Explanation: TME 10 OPC has been requested to submit a job that has an incorrect job card.
System action: The job is not submitted.
User response: Correct the JCL for this job and use the Modify Current Plan dialog to restart the occurrence at the
failing operation.
EQQW526E JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE NO JOB CARD
COULD BE FOUND
Explanation: TME 10 OPC has been requested to submit a job that does not have a job card.
System action: The job is not submitted.
User response: Correct the JCL for this job and use the Modify Current Plan dialog to restart the occurrence at the
failing operation.
EQQW527W THE JOB CARD OF JOB MEMBER IN APPLICATION APPL SPECIFIES JOB NAME CURNAME. THE
JOB IS SUBMITTED ANYWAY
Explanation: TME 10 OPC has been requested to submit a job whose name is different from the job name of the
current operation.
System action: TME 10 OPC submits the job without any changes.
User response: If the difference in job names is intentional then the message can be ignored. If the message is not
expected then make sure that the operation corresponding to this job has the correct status.
EQQW529E JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE THE JOB CARD
SPECIFIES JOB NAME CURNAME
Explanation: TME 10 OPC has been requested to submit a job that has a different name to that defined by the
corresponding operation. JOBCHECK(SAME) has been defined on the JTOPTS initialization statement.
System action: The job is not submitted.
User response: Change the JCL for this job to use the correct job name and use the MCP dialog to restart the
occurrence at the failing operation.
318
TME 10 OPC Messages and Codes
EQQW532E Ÿ EQQW750W
EQQW532E THE WSA TASK IS TERMINATING DUE TO A SEVERE ERROR. REFER TO THE SYSMDUMP DATA
SET FOR MORE INFORMATION
Explanation: The Work Station Analyzer subtask has encountered a second severe error.
System action: The Work Station Analyzer subtask terminates and a dump of the TME 10 OPC subsystem address
space is generated.
User response: Refer to the SYSMDUMP dataset to determine the cause of the error. If the problem is caused by
either of the exits taken by the Work Station Analyzer, that is by EQQUX001 or by EQQUX002, then the exit must be
updated. After correcting all errors, restart the TME 10 OPC subsystem.
EQQW533E THE WSA TASK WILL ATTEMPT TO RECOVER FROM A SEVERE ERROR. REFER TO THE
SYSMDUMP DATA SET FOR MORE INFORMATION
Explanation: The Work Station Analyzer subtask has encountered a severe error.
System action: The Work Station Analyzer subtask generates a dump of the TME 10 OPC subsystem address
space and attempts to continue normal processing.
User response: Refer to the SYSMDUMP dataset to determine the cause of the error. If the problem is caused by
either of the exits taken by the Work Station Analyzer, that is, by EQQUX001 or by EQQUX002, then the exit must be
updated.
EQQW534E THE WSA TASK HAS DETECTED A LOOP. DOA, CPLREC3P, AND WAP ARE WRITTEN TO MLOG
Explanation: The Work Station Analyzer subtask has tried to start the same operation repeatedly. The associated
DOA, CPLREC3P, and WAP are written to the MLOG. The operation status is set as specified by the
SUBFAILACTION keyword of the JTOPTS statement.
System action: The failing operation is not dispatched, and the Work Station Analyzer subtask continues processing.
Problem determination: Review the MLOG, JT log, and CP to determine the cause of the error.
User response: Contact your system programmer.
System programmer response: This might be a user error or an internal TME 10 OPC error. Keep copies of the
MLOG, JTARC and active JTnn, and CP. If you suspect that this is not a user error, contact your IBM representative.
EQQW539E THE EXECUTE COMMAND FAILED DUE TO INACTIVE WORKSTATION APPL: APPLID IA: IA
OPERATION: OPNO
Explanation: The Work Station Analyzer subtask has detected that there is no active workstation for the actual
operation.
System action: The Work Station Analyzer subtask will reset the execute indicator. The operation will remain in
status Ready and be scheduled as any normal operation.
User response: If an immediate execution of the operation is desired, either the ordinary workstation or, if the
operation is reroutable, the alternate workstation should be activated. The EXECUTE command can then be reissued.
EQQW750W STC STCNAME IS DEFINED AS A SUBSYSTEM THAT IS NOT MANAGED BY JES. OPC/ESA
DOES NOT SUPPORT THIS STC
Explanation: The submittor task cannot start this STC, because it is defined as a subsystem not handled by JES.
System action: The corresponding operation is set to ended-in-error with error code OSUB.
System programmer response: Check the active IEFSSNemin the SYS1.PARMLIB dataset to see if the STC
STCNAME is defined as a subsystem. If it is not defined, contact your IBM representative.
Chapter 30. EQQWnnn Messages
319
EQQW751E Ÿ EQQW755W
EQQW751E THE SUBMITTOR TASK GOT RC IN RETURN CODE FROM THE MGCR MACRO WHEN THE STC
STCNAME WAS ABOUT TO BE STARTED
Explanation: The submittor task cannot start this STC. The MGCR macro (SVC34) failed with the indicated return
code in register 15.
System action: The corresponding operation is set to ended-in-error with error code OSUB.
System programmer response: Contact your IBM representative.
EQQW752W A SUBMIT EVENT RECORD (TYPE I) WILL BE CREATED FOR STC STCID, BUT IT MAY BE TOO
LATE
Explanation: The submittor task has been restarted after ending abnormally. The abnormal termination occurred
immediately after the start command was performed for an STC, before the I event record could be created.
If more than five minutes has passed since the submittor task ended abnormally, the A1 event record is timed out.
TME 10 OPC tracking of the operation will fail.
System action: None.
User response: Check the status of the corresponding operation. Correct it manually, if necessary.
System programmer response: Investigate why the submittor task ended abnormally, and take appropriate action.
EQQW753E STC STCID HAS BEEN STARTED BY OPC/ESA, BUT THE MVS EXIT IEFUJI WAS NEVER OR
INCORRECTLY INVOKED. THE TRACKING WILL FAIL FOR THE STC
Explanation: The submittor task started an STC, but did not receive the expected acknowledgement from the MVS
SMF exit IEFUJI. The tracking of the STC will fail.
System action: None.
User response: Check the status of the corresponding operation. If the status is wrong, correct it manually.
System programmer response: Check that the active SMFPRMxx member in the SYS1.PARMLIB dataset specifies
that IEFUJI is to be invoked for STCs.
Carefully check that the IEFUJI supplied with TME 10 OPC is correctly installed.
EQQW754W THE OPC/ESA STARTED TASK FILE, DDNAME = EQQSTC, COULD NOT BE OPENED
Explanation: The submittor task failed to open EQQSTC, the started task temporary proclib file.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Save the JCL from the failing job or started task.
System programmer response: Add an EQQSTC ddname to your TME 10 OPC start procedure JCL. The ddname
must specify an empty partitioned dataset.
EQQW755W THE OPC/ESA STARTED TASK FILE, DDNAME = EQQSTC, IS NOT A PDS
Explanation: EQQSTC, the started task temporary proclib file, was not allocated as a partitioned dataset.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Save the JCL from the failing job or started task.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
System programmer response: Check that the dataset allocated to the EQQSTC ddname is a partitioned dataset.
320
TME 10 OPC Messages and Codes
EQQW756W Ÿ EQQW759W
EQQW756W THE OPC/ESA STARTED TASK FILE, DDNAME = EQQSTC, IS NOT EMPTY
Explanation: EQQSTC, the started task temporary proclib file, is not empty.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Save the JCL from the failing job or started task.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
System programmer response: Check that the dataset allocated to the EQQSTC ddname is an empty partitioned
dataset.
EQQW757W THE OPC/ESA STARTED TASK FILE, DDNAME = EQQSTC, HAS WRONG LRECL OR WRONG
BLOCK SIZE
Explanation: EQQSTC, the started task temporary proclib file, was allocated with a different record length than 80 or
an invalid block size.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Save the JCL from the failing job or started task.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
System programmer response: Check that the dataset allocated to the EQQSTC ddname is an empty partitioned
dataset with record length 80.
EQQW758W THE SUBMITTOR TASK DETECTED THAT THE STC STCID IS STILL IN JES3 INPUT SERVICE
(STARTING)
Explanation: The started task has not passed the JES3 input service phase.
This message is repeated every ten minutes.
System action: The submittor task will not submit started tasks until the STC has passed JES3 input service, but will
continue to submit batch jobs and WTOs.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Save the SYSLOG from the primary system console.
Ÿ Produce a dynamic console dump of the TME 10 OPC address space. Ensure that CSA is part of the SDUMP
option.
System programmer response: None.
EQQW759W THE SUBMITTOR TASK COULD NOT HANDLE STC STCNAME
Explanation: The started task was queued to the submittor queue, SUBQ. The STC could not be submitted
because of errors (indicated by previous messages).
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Produce a dynamic console dump of the TME 10 OPC address space. Ensure that CSA is part of the SDUMP
option.
User response: Manually set the corresponding operation to the correct status.
System programmer response: Investigate the MLOG, and look for other messages that explain the error.
Chapter 30. EQQWnnn Messages
321
EQQW760E Ÿ EQQW762E
EQQW760E AN I/O ERROR OCCURRED ON THE EQQSTC DATA SET WHEN THE SUBMITTOR TASK WAS
WRITING THE JCL FOR STC STCNAME. THE SYNAD ERROR MESSAGE WAS: SYNMSG
Explanation: The submittor task encountered an input/output error writing to EQQSTC, the started task temporary
proclib file. A SYNAD error routine was given control and issued an error message.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
The corresponding operation is set to status E.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product
installed on this MVS/ESA system.
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
Ÿ Save the SYSLOG from the primary system console.
System programmer response: This is probably a hardware error. Contact your IBM representative.
EQQW761E AN ABEND OCCURRED WHEN THE SUBMITTOR TASK WAS WRITING THE JCL FOR STC
STCNAME ON THE EQQSTC DATA SET. THE ABEND CODE WAS: ABCODE
Explanation: The submittor task got an ABEND when writing EQQSTC, the started task temporary proclib file. An
ABEND exit routine was given control and issued an ABEND code.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
The corresponding operation is set to status E.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
Ÿ Save the SYSLOG from the primary system console.
System programmer response: See MVS/ESA Message Library: System Codes for an explanation of the ABEND
code, and take appropriate action.
EQQW762E AN I/O ERROR OCCURRED ON THE EQQSTC DATA SET WHEN THE SUBMITTOR TASK WAS
STOWING THE MEMBER FOR STC STCNAME. THE SYNAD ERROR MESSAGE WAS: SYNMSG
Explanation: The submittor task encountered an input/output error during a STOW to EQQSTC, the started task
temporary proclib file. A SYNAD error routine was given control and issued an error message.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
The corresponding operation is set to status E.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product
installed on this MVS/ESA system.
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
Ÿ Save the SYSLOG from the primary system console.
System programmer response: This is probably a hardware error. Contact your IBM representative.
322
TME 10 OPC Messages and Codes
EQQW763E Ÿ EQQW766W
EQQW763E AN ABEND OCCURRED WHEN THE SUBMITTOR TASK WAS STOWING THE MEMBER FOR STC
STCNAME ON THE EQQSTC DATA SET. THE ABEND CODE WAS: ABCODE
Explanation: The submittor task got an ABEND when stowing on EQQSTC, the started task temporary proclib file.
An ABEND exit routine was given control and issued an ABEND code.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
The corresponding operation is set to status E.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
Ÿ Save the SYSLOG from the primary system console.
System programmer response: See MVS/ESA Message Library: System Codes for an explanation of the ABEND
code, and take appropriate action.
EQQW764E THE SUBMITTOR TASK GOT AN UNEXPECTED RETURN CODE WHEN STOWING THE MEMBER
NAME FOR STC STCNAME ON THE EQQSTC DATA SET THE RETURN AND REASON CODE WAS
RC
Explanation: The submittor task got an unexpected return code when stowing a member on EQQSTC, the started
task temporary proclib file.
The return code is the content of register 15, and the reason code is the content of register 0 after the STOW macro.
The corresponding operation is set to status E.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
Ÿ Save the SYSLOG from the primary system console.
System programmer response: Use the return code and reason code to determine the cause of the error. For
more information, refer to the documentation about the STOW macro for the currently active MVS/ESA system.
EQQW765E THE SUBMITTOR TASK GOT AN UNEXPECTED RETURN CODE WHEN ISSUING THE MGCR
MACRO FOR STC STCNAME
Explanation: The submittor task got an unexpected return code when the MGCR macro was invoked to start an
STC.
The corresponding operation is set to status E.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
System programmer response: Use the return code and reason code to determine the cause of the error. For
more information, refer to the documentation about the MGCR macro for the currently active MVS/ESA system.
EQQW766W THE EVENT CREATION ROUTINE DETECTED THAT THE JES2 EXIT7 (EQQEXIT) IS ON A LOWER
RDMID LEVEL THAN THE OPC/ESA SUBSYSTEM MODULE EQQZEV2X
Explanation: The level of the EQQEXIT macro in JES2 EXIT7 (OPCAXIT7) is at a lower maintenance level than the
TME 10 OPC subsystem.
System action: The event creation routine continues to create event records. The event records may contain invalid
tracking information, causing the corresponding operation status to be inaccurate.
Operator response: If necessary, set the correct operation status manually.
System programmer response: Apply the EXIT7 again, and make sure that the appropriate maclibs are used in the
SYSLIB concatenation. If you are assembling the OPCAXIT7 outside the JES2 SMP environment, make sure that you
have the SMPMTS dataset concatenated first in the SYSLIB concatenation.
Chapter 30. EQQWnnn Messages
323
EQQW767W Ÿ EQQW770E
EQQW767W THE EVENT CREATION ROUTINE DETECTED THAT THE IATUX29 WAS GENERATED AGAINST A
JES3 LEVEL THAT DOES NOT MATCH THE CURRENT EXECUTING JES3 LEVEL
Explanation: The level of the JES3 macros used to generate the TME 10 OPC IATUX29 does not match the level
of the active JES3 system.
System action: The event creation routine continues to create event records. The event records may contain invalid
tracking information, causing the corresponding operation status to be inaccurate.
Operator response: If necessary, set the correct operation status manually.
System programmer response: Apply the IATUX29 and IATUX19 again, and make sure that the appropriate
maclibs are used in the SYSLIB concatenation. If you are assembling the IATUX29 and IATUX19 outside the JES3
SMP-environment, make sure you have the SMPMTS dataset top concatenated in the SYSLIB concatenation.
EQQW768W AN I/O ERROR OCCURRED ON THE EQQSTC DATA SET WHEN THE SUBMITTOR TASK WAS
READING. THE SYNAD ERROR MESSAGE WAS: SYNMSG
Explanation: The submittor task encountered an input/output error reading the EQQSTC, the started task temporary
proclib file.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
The corresponding operation is set to status E.
Problem determination: The SYNAD routine collects information such as jobname, stepname, unit address, device
type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this
information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product
installed on this MVS/ESA system.
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
Ÿ Save the SYSLOG from the primary system console.
System programmer response: This is probably a hardware error. Contact your IBM representative.
EQQW769W AN ABEND OCCURRED WHEN THE SUBMITTOR TASK WAS READING ON THE EQQSTC DATA
SET. THE ABEND CODE WAS: ABCODE
Explanation: The submittor task got an abend when reading EQQSTC, the started task temporary proclib file.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
The corresponding operation is set to status E.
Problem determination:
Ÿ Save the MLOG from the TME 10 OPC subsystem.
Ÿ Run the AMASPZAP utility specifying ABSDUMP ALL on the dataset, and save the output.
Ÿ Save the SYSLOG from the primary system console.
System programmer response: This is probably a hardware error. Contact your IBM representative.
EQQW770E EQQSTC DDNAME IS MISSING
Explanation: The submittor task could not find the EQQSTC ddname in the JCL.
System action: The submittor task will not submit started tasks, but will continue to submit batch jobs and WTOs.
System programmer response: Add an EQQSTC ddname to the TME 10 OPC JCL procedure and specify an
empty dataset that is allocated on the JES proclib concatenation.
For more information, refer to TME 10 OPC Installation Guide.
324
TME 10 OPC Messages and Codes
EQQW771W Ÿ EQQW777W
EQQW771W THE JCL FOR STC JOBNAME WILL NOT BE SUBMITTED BECAUSE SUBMIT RECORD IS TOO
OLD
Explanation: Started task JCL records in a submit/release dataset are older than the limit defined by the SKIPTIME
and SKIPDATE keywords in the EWTROPTS statement.
System action: The old records are not processed. The event writer continues to read the submit/release dataset.
Operator response: Restart the corresponding operation, if necessary.
EQQW772W THE WTO WITH JOBNAME JOBNAME WILL NOT BE ISSUED BECAUSE SUBMIT RECORD IS TOO
OLD
Explanation: A WTO message in a submit/release dataset is older than the limit defined by the SKIPTIME and
SKIPDATE keywords in the EWTROPTS statement.
System action: The old message is not processed. The event writer continues to read the submit/release dataset.
Operator response: Restart the corresponding operation, if necessary.
EQQW775I APPLICATION: ADID OP£: OPNO WITH INPUT ARRIVAL: IA AND JOBNAME: JOBNM ON WORK
STATION: WSNAME HAS BEEN STARTED. OPERATION TEXT: OPTEXT
Explanation: A WTO operation has been started by TME 10 OPC.
This message is for your information only. It can be intercepted and interpreted in a customer-defined manner.
System action: None.
User response: None.
EQQW776I APPLICATION: ADID OP£: OPNO WITH INPUT ARRIVAL: IA AND JOBNAME: JOBNM ON WORK
STATION: WSNAME HAS PASSED DEADLINE: DEADL OPERATION TEXT: OPTEXT
Explanation: An operation has passed its deadline.
This message is for your information only. It can be intercepted and interpreted in a customer-defined manner, for
example to automate termination.
System action: None.
User response: None.
EQQW777W THE EVENT CREATION ROUTINE DETECTED THAT THE JES2 EXIT7 (EQQEXIT) IS ON A HIGHER
RMID LEVEL THAN THE OPC/ESA SUBSYSTEM MODULE EQQZEV2X
Explanation: The EQQEXIT macro used to generate the currently active JES2 EXIT7 is on a higher maintenance
level than the subsystem module EQQZEV2X.
System action: The event creation routine continues to create event records. The event records may contain invalid
tracking information, causing the corresponding operation status to be inaccurate.
Operator response: If necessary, set the correct operation status manually.
System programmer response: The EQQZEV2X is part of the EQQSSCMC load module, which is normally loaded
during IPL. To activate a new EQQSSCMC—until a planned IPL can be performed—specify
SSCMNAME(EQQSSCMC) in the OPCOPTS initialization statement and restart the tracker address space.
Chapter 30. EQQWnnn Messages
325
EQQW778W Ÿ EQQW779I
EQQW778W EQQEVDS DDNAME IS NOT PRESENT OR SPECIFIES DD DUMMY
Explanation: The submittor task could not find the EQQEVDS DDNAME in the JCL for the TME 10 OPC address
space, or the DDNAME specifies DD DUMMY.
System action: The submittor task will not checkpoint submit requests, but will continue to submit jobs.
System programmer response: It is not mandatory to run a TME 10 OPC address space with the EQQEVDS data
set, i.e. when EWTRTASK(NO) is specified. But you may add this data set to gain the submit checkpointing benefits.
When the data set is used only for submit checkpointing, it can be allocated with the minimum size, which is two
tracks.
EQQW779I NO CHECKPOINTING FOR SUBMITS ON WORKSTATION WSNAME (DQETYPE DQETYPE). WHY
Explanation: The submittor task could not checkpoint a submit request for a DQETYPE (J1=JOB, J2=STC,
WTO=WTO) defined on workstation WSNAME. The reason is defined by WHY, which can be one of the following five
values:
1.
2.
3.
4.
5.
Access to EQQEVDS data set not available
Read failed of EQQEVDS header record
No entries left in the EQQEVDS header record
A delete WS from EVDS failed: WS not found
Write failed for EQQEVDS header record
System action: The submittor task will not checkpoint submit requests, but will continue to submit jobs.
System programmer response: For all messages except 3, other associated messages are present in the MLOG.
Reason 3 indicates that the maximum number of entries (13) that the checkpoint record can hold has been reached.
If this limit has been reached, verify that all 13 workstations that are defined in the record still exist in the current plan.
If the workstations are not in the current plan, the workstation name can be blanked out or zeroed to make the
position eligible for a new workstation. Alternatively, you can delete and reallocate the EQQEVDS data set. The
entries will be built only for workstations in the current plan. TME 10 OPC Customization and Tuning contains
instructions for deleting and reallocating an EVDS data set.
326
TME 10 OPC Messages and Codes
EQQX000E Ÿ EQQX011E
Chapter 31. EQQXnnn Messages
EQQX000E XROW IS NOT A VALID ROW COMMAND
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX001E ZCMD IS NOT A VALID PRIMARY COMMAND
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX002E A ROW CANNOT BE SELECTED INSIDE A BLOCK THAT IS TO BE DELETED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX003E COMMANDS AT START AND END OF REPEAT BLOCK DO NOT MATCH
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Different iteration factors have been given at start and end of a repeat block. Either use the same factor at both start
and end, or set the iteration factor at either start or end only.
EQQX004E A DELETE BLOCK CANNOT BE ENTERED INSIDE A REPEAT BLOCK
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX005E A ROW COMMAND IS FOUND INSIDE A BLOCK THAT IS TO BE DELETED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX006E A BLOCK COMMAND HAS NO MATCHING END
Explanation: Data entry error; see “Data Entry Errors” on page 2.
| EQQX007E ISPF DISPLAY SERVICE FOR PANEL PAN GAVE RC DISPRET
| Explanation: Panel PAN could not be displayed.
| System action: Processing continues.
| System programmer response: Check that the panel is available in the panel library allocated to the TSO session.
| If it is a user-specified JCL EDIT panel, check that the correct name is specified in OPC dialog option 0.6.
EQQX008E XCMD IS NOT A VALID PRIMARY COMMAND
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX009I XSELTR
Explanation: This message is written to the ISPF log dataset when an TME 10 OPC module is loaded or when an
ISPF select is requested by the dialog. The message is used to trace TME 10 OPC activity for a dialog user.
System action: Processing continues.
User response: None.
EQQX010E SPECIFY FORMAT FOR DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX011E YEAR MUST BE SPECIFIED AS YY IN THE DATE FORMAT
Explanation: Data entry error; see “Data Entry Errors” on page 2.
 Copyright IBM Corp. 1991, 1998
327
EQQX012E Ÿ EQQX023E
EQQX012E Y MAY BE SET ONLY ONCE AND ONLY IN YY
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX013E MONTH MUST BE SPECIFIED AS MM IN THE DATE FORMAT
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX014E M MAY BE SET ONLY ONCE AND ONLY IN MM
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX015E DAY MUST BE SPECIFIED AS DD OR DDD IN THE DATE FORMAT
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX016E D MAY BE SET ONLY ONCE AND ONLY IN DD OR DDD
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX017E MONTH CANNOT BE SPECIFIED TOGETHER WITH JULIAN DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX018E THE NAME DOES NOT CONFORM TO THE RULES FOR SUBSYSTEM NAMES
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX019E CENTURY MUST BE SPECIFIED AS TWO ADJACENT CHARACTERS
Explanation: Century is optional. If it is specified, it must be two adjacent characters.
System action: The system waits for you to respond.
User response: If century is used, specify as CC.
EQQX020E VER STATEMENT HAS INVALID SYNTAX
Explanation: An error in the panel has caused invalid syntax in the VER statement.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Contact your IBM representative.
EQQX021E AN INVALID DELIMITER WAS FOUND
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX022E YEAR MUST BE 00 - 99, OR CENTURY WITH YEAR MUST BE 1972 - 2071
Explanation: Year must be specified as 72 to 99 for years 1972 to 1999, or 00 to 71 for years 2000 to 2071. If
century is specified, century and year must be specified as 1972 to 2071.
System action: The panel is redisplayed with this error message.
User response: Enter a value in the supported range.
EQQX023E JULIAN DAY NUMBER IS NOT COMPATIBLE WITH YEAR
Explanation: Data entry error; see “Data Entry Errors” on page 2.
328
TME 10 OPC Messages and Codes
EQQX024E Ÿ EQQX038E
EQQX024E MONTH MUST BE 01 - 12
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX025E DAY IS NOT COMPATIBLE WITH MONTH AND YEAR
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX026E HOUR MUST BE 00 - 24
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX027E MINUTE MUST BE 00 - 59
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX028E MINUTE MUST BE 00 WHEN HOUR IS 24
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX029E YEAR MUST BE SPECIFIED AS 00 TO 99, OR century and year must be 1972 to 2071.
Explanation: Year must be specified as 72 to 99 for years 1972 to 1999 and 00 to 71 for years 2000 to 2071. If
century is specified, century and year must be specified as 1972 to 2071.
System action: The panel is redisplayed with this error message.
User response: Enter a value in the supported range.
EQQX031E SORT ORDER MUST BE A NUMERIC VALUE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX032E DIRECTION MUST BE A - ASCENDING OR D - DESCENDING
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX033E SPECIFY FORMAT FOR TIME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX034E HOURS MUST BE SPECIFIED AS HH IN TIME FORMAT
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX035E H MAY BE SET ONLY ONCE AND ONLY IN HH
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX036E MINUTES MUST BE SPECIFIED AS MM IN TIME FORMAT
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX037E M MAY BE SET ONLY ONCE AND ONLY IN MM
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX038E COLOR MUST BE ONE OF THOSE LISTED ON THE PANEL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 31. EQQXnnn Messages
329
EQQX039E Ÿ EQQX049E
EQQX039E HILITE ATTRIBUTE MUST BE ONE OF THOSE LISTED ON THE PANEL
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX040I THE JOB HAS BEEN SUBMITTED FOR SUBFUNC
Explanation: The job has been submitted.
System action: Normal processing continues.
User response: None.
EQQX041E THE NAME SPECIFIED FOR THE SYSOUT DATA SET IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX042E AT LEAST THE FIRST JOB STATEMENT MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX043E THE EDIT OPTION MUST BE EITHER S OR E
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX044E VALID REPLY IS Y OR N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX045W PRESS ENTER TO GENERATE JCL OR END TO CANCEL
Explanation: Press ENTER to generate the JCL, or enter END to leave the panel without generating the JCL.
System action: The system waits for you to respond.
User response: Press ENTER or enter END.
EQQX046E NEW START DATE < CURRENT END DATE
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX047E YEAR MUST BE 00 - 99, OR CENTURY WITH YEAR MUST BE 1972 - 2071
Explanation: Year must be specified as 72 to 99 for years 1972 to 1999, or 00 to 71 for years 2000 to 2071. If
century is specified, century and year must be specified as 1972 to 2071.
System action: The panel is redisplayed with this error message.
User response: Enter a value in the supported range.
| EQQX048E CORRECT VALUES ARE Y AND N
| Explanation: The only values allowed are Y and N.
| System action: The panel is redisplayed with this error message.
| User response: Enter a value of Y or N.
| EQQX049E INVALID COMBINATION. CONFIRM PANEL MUST BE N WHEN CONSISTENCY CHECK IS N.
| Explanation: The Confirm Panel value is meaningful only if consistency checking has been activated. Therefore, if
| Consistency Check is set to NO, the Confirm Panel value must also be NO.
| System action: The panel is redisplayed with this error message.
| User response: Set the correct value.
330
TME 10 OPC Messages and Codes
EQQX100E Ÿ EQQX114E
EQQX100E ONLY ONE ROW COMMAND CAN BE SPECIFIED ON THIS PANEL
Explanation: It is not allowed to specify more than one row command on this panel.
System action: The system waits for you to respond.
User response: Enter the RESET command to remove all row commands, and then enter one row command.
EQQX101I PENDING APPLICATION DESCRIPTION DOES NOT GIVE OCCURRENCES
Explanation: The Modify LTP One program, which is generated with the L command, will delete any entry of the
pending version of the application and will add any active versions of it. Also, being a Modify LTP One, dependencies
will not be resolved.
System action: Processing continues.
User response: Decide whether to submit the job.
EQQX110E XOPCNM IS NOT A VALID SUBSYSTEM NAME
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You can change the name to a valid subsystem name if you go to the TME 10 OPC main menu and select 0,
OPTIONS.
EQQX111E XOPCNM IS NOT AN ACTIVE OPC/ESA SUBSYSTEM
Explanation: The subsystem (XOPCNM) you selected is not active.
System action: The system waits for you to respond.
User response: Change the subsystem name to a valid name by going to the TME 10 OPC main menu and
selecting 0, OPTIONS. If the name is a valid subsystem name, ask your system programmer to start the subsystem.
System programmer response: Start the subsystem.
EQQX112E NOT ENOUGH STORAGE AVAILABLE
Explanation: A GETMAIN failed at logon to TME 10 OPC because there is not enough storage available.
System action: The system waits for you to respond.
User response: Logon again to TSO with a larger region size.
EQQX113E INCORRECT PARAMETERS TO THE LOGON ROUTINE
Explanation: The logon failed because of incorrect parameters in the input to the logon routine.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX114E OPC/ESA SERVICES REQUIRE TSO/E R2
Explanation: It is not possible to run TME 10 OPC because the prerequisite TSO/E Release 2 system programs are
not installed.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Make sure that TSO/E Release 2 is installed before anyone is allowed to use the
TME 10 OPC dialogs.
Chapter 31. EQQXnnn Messages
331
EQQX115E Ÿ EQQX118E
EQQX115E TSO SERVICE FACILITY RC: XSSRC, RSNC: XSSRS, ABEND: XSSAB
Explanation: The TSO Service facility, IKJEFTSR, which is used for communication between the dialog and the
TME 10 OPC subsystem, gave an error return code. The field RC gives the IKJEFTSR return code (XSSRC):
8
Confirms that the requested function is terminated as a result of the user pressing ATTN (attention).
12
The invoked function has abended; the RSNC field then contains the IKJEFTSR reason code, and the
ABEND field contains the abend code.
20
There is a problem with the IKJEFTSR parameter list; and XSSRS is the reason code for the problem.
System action: The request is rejected.
Problem determination: Use the return code, reason code, and abend code to determine the cause of the error.
For more information, refer to the documentation of IKJEFTSR for the currently active MVS/ESA system.
User response: If the return code is other than 8 (a result of your pressing ATTN), leave the dialog and then try
again. If the error persists, contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX116E ERROR IN SUBSYSTEM INTERFACE, RETURN CODE: XRC
Explanation: An error occurred in the subsystem interface. Return code XRC provides debugging information for
IBM personnel.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX117E ERROR IN EQQMINOR ROUTINE, RETURN CODE: XRC
Explanation: An error, with return code XRC, occurred in the EQQMINOR routine. The return code is returned from
the MVS subsystem interface routine at a subsystem call request.
System action: The request is rejected.
Problem determination: Use the return code to determine the cause of the error. For more information, refer to the
documentation of return codes from the IEFSSREQ macro for the currently active MVS/ESA system.
User response: Contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX118E ERROR IN LOGON ROUTINE. RETURN CODE: XSSRC. REASON CODE XSSRS
Explanation: An error, with return code XSSRC and reason code XSSRS, occurred in the logon routine. Return
code XSSRC and reason code XSSRS provide debugging information for IBM personnel.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
332
TME 10 OPC Messages and Codes
EQQX119E Ÿ EQQX124E
EQQX119E LOGOFF REQUEST REJECTED, USER IS NOT LOGGED ON
Explanation: You have attempted to disconnect a session from TME 10 OPC, but you were not connected.
System action: None.
User response: You can determine why you are logged off in the TME 10 OPC message log. (TME 10 OPC has
been stopped and restarted since you logged on.)
EQQX120E THE EQQMINOR PROGRAM CAN ONLY BE CALLED BY AN APF-AUTHORIZED TASK
Explanation: The EQQMINOR program could not be called by an APF-authorized task because it does not reside in
an APF-authorized library. EQQMINOR is one of a number of TME 10 OPC load modules that must reside in an
APF-authorized library.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Move EQQMINOR to an APF-authorized library.
EQQX121E YOU ARE NOT AUTHORIZED TO REQUEST RESOURCE
Explanation: You have attempted to access (read or update) an TME 10 OPC resource but you are not authorized
to access it. The retrieval and update of data in the TME 10 OPC database is controlled by parameter values in the
AUTHDEF initialization statement, and the definition of RACF resources and the access lists to these resources.
System action: The request is rejected.
User response: Contact your security administrator.
EQQX122E CURRENT SUBSYSTEM REQUEST WAS NOT RECOGNIZED
Explanation: The subsystem interface has been called with an invalid parameter.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX123E XOPCNM IS NOT AN OPC/ESA SUBSYSTEM NAME
Explanation:
XOPCNM may be a subsystem name but it is not a valid TME 10 OPC subsystem name.
System action: The system waits for you to respond.
User response: Enter a valid TME 10 OPC subsystem name.
EQQX124E YOU ARE NOT CONNECTED TO XOPCNM. RESTART FROM PRIMARY PANEL
Explanation: The subsystem XOPCNM has been restarted; you are no longer connected to it.
System action: The system waits for you to respond.
User response: Restart from the primary panel.
Chapter 31. EQQXnnn Messages
333
EQQX125E Ÿ EQQX133E
EQQX125E YOU ARE ALREADY CONNECTED TO OPC/ESA
Explanation: You have attempted to connect your session to TME 10 OPC again but you are already connected to
TME 10 OPC.
System action: The system waits for you to respond.
User response: Log off from TSO and then log on again. If the problem persists, contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX127E USER NOT AUTHORIZED TO REQUEST RESOURCE, RC:XRC, RSNC:XRSN
Explanation: You have attempted to access (read or update) an TME 10 OPC resource but you are not authorized
to access it. The retrieval and update of data in the TME 10 OPC database is controlled by parameter values in the
AUTHDEF initialization statement, and the definition of RACF resources and the access lists to these resources.
System action: The request is rejected.
Problem determination: Use the RACROUTE return code and reason code to determine the cause of the error.
For more information, refer to the appropriate documentation for the security product installed on this MVS/ESA
system.
User response: Contact your security administrator.
EQQX128E YOU ARE NOT AUTHORIZED TO REQUEST RESOURCE MEMBER
Explanation: You have attempted to access (read or update) an TME 10 OPC resource but you are not authorized
to access it. The retrieval and update of data in the TME 10 OPC database is controlled by parameter values in the
AUTHDEF initialization statement, and the definition of RACF resources and the access lists to these resources.
System action: The request is rejected.
User response: Contact your security administrator.
EQQX129E YOU CANNOT DELETE AN ALLOCATED SPECIAL RESOURCE
Explanation: You have attempted to delete a special resource which is allocated for operations currently. This is not
allowed.
System action: The request for a special resource delete is rejected.
User response: Wait till the special resource is released by the operations using it.
EQQX131E NOT ENOUGH STORAGE AVAILABLE FOR OPC/ESA
Explanation: A GETMAIN for storage for the communication area between the dialog and the TME 10 OPC
subsystem failed. The request is for CSA storage, subpool 241.
System action: The request is rejected.
User response: Contact your system programmer. When more CSA storage is available, logon to TSO again.
System programmer response: Ensure that sufficient CSA storage is available.
EQQX133E THE SPECIFIED SUBSYSTEM, XOPCNM, IS ENDING
Explanation: You cannot access subsystem XOPCNM, because it is terminating.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the reason for the subsystem
termination.
334
TME 10 OPC Messages and Codes
EQQX134E Ÿ EQQX139E
EQQX134E REQUESTED SERVICE IS CURRENTLY NOT AVAILABLE
Explanation: Your request to use the general service function could not be granted because the general service
subtask is not active.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine why the general service
subtask is not active.
EQQX135E AN ERROR OCCURRED WHILE POSTING THE SUBSYSTEM
Explanation: Your request to use the general service function could not be granted because the general service
subtask is inaccessible due to an error that occurred in the TME 10 OPC subsystem.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for messages concerning the
general service subtask to determine the cause of the error.
EQQX137E THE LOGICAL VSAM FILE IS NOT DEFINED
Explanation: Your request to use the general service function failed because the logical VSAM file is not defined.
This error indicates that a serious error has occurred in the TME 10 OPC subsystem.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for messages concerning the
general service subtask and the logical file handler to determine the cause of the error.
EQQX138E AN I/O REQUEST SPECIFIES TOO LARGE A VSAM KEY SIZE
Explanation: Your request to use the general service function failed because an I/O request specifies too large a
VSAM key size. This error indicates that a serious error has occurred in the TME 10 OPC subsystem.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for messages concerning the
general service subtask and the logical file handler to determine the cause of the error.
EQQX139E VSAM I/O REQUEST FAILED. RETURN CODE: XSSRC, REASON code: XSSRS
Explanation: Your request to use the general service function resulted in a VSAM I/O that failed. The reason for the
failure is indicated by return code XSSRC and reason code XSSRS, which are the VSAM return and reason codes for
a record management request.
System action: The request is rejected.
Problem determination: Use the VSAM return code and reason code to determine the cause of the error. For more
information, refer to the appropriate documentation for the MVS/DFP product installed on this MVS/ESA system.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for VSAM I/O error messages to
determine the cause of the error.
Chapter 31. EQQXnnn Messages
335
EQQX140E Ÿ EQQX144E
EQQX140E REMAINING STORAGE NOT ENOUGH TO OPEN LOGICAL VSAM FILE
Explanation: Your request to use the general service function failed because the remaining storage is not enough to
open a logical VSAM file.
System action: The request is rejected.
User response: Try again. If the error persists, contact your system programmer.
System programmer response: Allocate a larger region to the TME 10 OPC subsystem and then restart the
subsystem.
EQQX142E VSAM I/O WAS ATTEMPTED ON AN UNOPENED LOGICAL VSAM FILE
Explanation: Your request to use the general service function failed because the VSAM I/O was attempted on an
unopened logical VSAM file. This error indicates that a serious error has occurred in the TME 10 OPC subsystem.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for messages concerning the
general service subtask and the logical file handler to determine the cause of the error.
EQQX143E OPEN WAS REQUESTED FOR ALREADY OPENED LOGICAL VSAM FILE
Explanation: Your request to use the general service function failed because the open request was for an already
opened logical VSAM file. This error indicates that a serious error has occurred in the TME 10 OPC subsystem.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for messages concerning the
general service subtask and the logical file handler to determine the cause of the error.
EQQX144E ERROR IN DB RECORD AT OFFSET OFFS, REASON CODE: XSSRS
Explanation: The subsystem detected an inconsistency in a record it was requested to write.
System action: The request is rejected.
User response: Look in the dump dataset (with ddname EQQDUMP) for further information. This dataset contains a
copy of the record and the position of the error. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
336
TME 10 OPC Messages and Codes
EQQX145E Ÿ EQQX153E
EQQX145E THE SUBSYSTEM PROGRAM IS NOT OF THE CORRECT RELEASE
Explanation: The dialog or TME 10 OPC batch program is from a later release of TME 10 OPC than the TME 10
OPC subsystem. TME 10 OPC checks that the subsystem name specified in your dialog or in the SUBSYS
parameter of the BATCHOPTS batch initialization statement (or its default) matches the name of one of your TME 10
OPC subsystems. If there is a match, TME 10 OPC checks if the dialog or batch program and the TME 10 OPC
subsystem are from the same release of TME 10 OPC. This message is issued only if the subsystem is from an
earlier release than the dialog or batch program.
Problem determination: This message is expected if the TME 10 OPC controller is started using the
BUILDSSX(REBUILD) keyword and the address space is not currently started.
System action: The subsystem request is rejected.
User response: Check on the main panel that you are using the right subsystem. If the message is given by a
batch program, check that the BATCHOPTS initialization statement specifies the right subsystem. If the error persists,
contact your system programmer.
System programmer response: Check that the right subsystem start JCL is used and that the right datasets are
allocated to ISPLLIB. If you cannot determine the cause and if the error persists, contact your IBM representative.
EQQX150E PDF BROWSE/EDIT WORK FILE CONNECT FAILURE - RC = MSGRC
Explanation: The connect to the work dataset used by PDF EDIT or BROWSE failed. Return code MSGRC gives
the reason why.
System action: The function is terminated.
Problem determination: Use the return code to determine the cause of the error. For more information, refer to the
appropriate documentation for the ISPF/PDF product installed on this MVS/ESA system.
User response: Contact your system programmer.
System programmer response: If the return code indicates that this is not a user error, contact your IBM
representative.
EQQX152E PDF BROWSE/EDIT WORK FILE - RC = MSGRC, REASON CODE = MSGEF
Explanation: Dynamic allocation for the PDF BROWSE/EDIT work file failed. Return code MSGRC and reason
code MSGEF give the reason why.
System action: The function is terminated.
Problem determination: Use the DYNALLOC return code and reason code to determine the cause of the error. For
more information, refer to the appropriate DYNALLOC documentation for the currently active MVS/ESA system.
User response: Contact your system programmer.
System programmer response: Determine the cause of the error, and take appropriate action.
EQQX153E PDF BROWSE/EDIT WORK FILE - RC = MSGRC, REASON CODE = MSGEF
Explanation: Dynamic deallocation for PDF BROWSE/EDIT work file failed. Return code MSGRC and reason code
MSGEF give the reason why.
System action: The function is terminated.
Problem determination: Use the DYNALLOC return code and reason code to determine the cause of the error. For
more information, refer to the appropriate DYNALLOC documentation for the currently active MVS/ESA system.
User response: Contact your system programmer.
System programmer response: Determine the cause of the error, and take appropriate action.
Chapter 31. EQQXnnn Messages
337
EQQX161E Ÿ EQQX198E
EQQX161E AN INTERNAL OPC/ESA CONTROL BLOCK IS IN ERROR
Explanation: An internal TME 10 OPC control block is in error.
System action: The system waits for you to respond.
User response: Contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX162E AN AUTHORITY CHECK FAILED, RESOURCE RESOURCE NOT RECOGNIZED
Explanation: You have attempted to access an TME 10 OPC resource but the resource RESOURCE is unknown to
TME 10 OPC. The retrieval and update of data in the TME 10 OPC database is controlled by parameter values in
the AUTHDEF initialization statement, and the definition of RACF resources and the access lists to these resources.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX163E INCORRECT PARAMETER IN GENERAL SERVICE REQUEST
Explanation: Your request for the general service function failed because of an incorrect parameter in the request.
System action: The system waits for you to respond.
User response: Try again. If the error persists, contact your system programmer.
System programmer response: Ensure that the correct load module library is accessed and that the dataset
contains the correct version of the TME 10 OPC modules. If the error persists, collect information in the form of the
sequence of actions leading to this error, and if possible, the data it may be dependent on. Then contact your IBM
representative.
EQQX164E AN ERROR OCCURRED WHILE UPDATING THE RESOURCE DATA SPACE.
Explanation: The request to update a special resource record failed because an error occurred when the general
service task updated the resource data space.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Look for message EQQQ505E in the TME 10 OPC message log, EQQMLOG.
This message contains additional information about the error. If the error persists, collect information in the form of
the sequence of actions leading to this error, and if possible, the data it may be dependent on. Then contact your
IBM representative.
EQQX198E ERROR, RC: XRC, RS: XRSN, FROM SUBSYSTEM RC: XSSRC, RS: XSSRS
Explanation: An TME 10 OPC request fails with an error code which is not recognized by the message module.
XRC, XRSN, XSSRC, and XSSRS provide debugging information for IBM personnel.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
338
TME 10 OPC Messages and Codes
EQQX220E Ÿ EQQX259E
EQQX220E THE INPUT ENTERED IS TOO LONG
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The longest value accepted is HH.MM, where:
HH
MM
The hour, in the range 00–24
The minute
EQQX226E HOUR PART OF DURATION MUST BE A NUMBER BETWEEN 0 AND 99
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX227E OPERATION DURATION MUST BE GREATER THAN 00.00
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX229E OPERATION OP DEADLINE EARLIER THAN OPERATION INPUT ARRIVAL
Explanation: The deadline must be the same as, or later than, the input arrival time.
System action: The request to write the record is rejected.
Problem determination: See the diagnostic file (EQQDUMP) for further information. This file contains a copy of the
record and the position of the error.
User response: Change the deadline or the input arrival time and resubmit the job. If the error persists, contact
your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX258E LOGICAL FILE HANDLER SUPPORT REQUIRED; TASK NOT ACTIVE
Explanation: The request has resulted in a request to the TME 10 OPC subsystem. The request cannot be handled
because the logical file handler is not available.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for messages concerning the
logical file handler. Correct all errors and then restart the TME 10 OPC subsystem.
EQQX259E NORMAL MODE MANAGER SUPPORT REQUIRED; TASK NOT ACTIVE
Explanation: The request has resulted in a request to the TME 10 OPC subsystem. The request cannot be handled
because the Normal Mode Manager is not active.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for messages concerning the
Normal Mode Manager. Correct all errors and then restart the TME 10 OPC subsystem.
Chapter 31. EQQXnnn Messages
339
EQQX260E Ÿ EQQX264E
EQQX260E AN INTERNAL CONTROL BLOCK IS IN ERROR: REASON CODE XSSRS
Explanation: Validation checking of the data received as input to a routine has detected a damaged control block.
Reason code XSSRS provides debugging information. Reason code 102 is given when the dialog code is of an
earlier release than the TME 10 OPC subsystem code.
System action: The request is rejected.
User response: If the reason code in the message is 102, check your ISPLLIB concatenation against the release of
the subsystem you are using. If the error persists, contact your system programmer.
System programmer response: Ensure that the correct load module library is set up to the TME 10 OPC
subsystem and to the user. Check that the library contains the correct version of the TME 10 OPC modules. If the
error persists, collect information in the form of the sequence of actions leading to this error, and if possible, the data it
may be dependent on. Then contact your IBM representative.
EQQX261E NOT ENOUGH STORAGE AVAILABLE: REASON CODE XSSRS
Explanation: The general service subtask has failed to carry out a request due to failure to allocate enough virtual
storage. Reason code XSSRS provides debugging information for IBM personnel.
System action: The request is rejected.
User response: If possible try to limit the storage demand of the request. For example, if this is a request for a list
of operations, choose a narrower selection criteria. If the problem persists, contact your system programmer.
System programmer response: Allocate a larger region to the TME 10 OPC subsystem and then restart the
subsystem. If the error persists, contact your IBM representative.
EQQX262E TIME LIMIT EXCEEDED WHEN TRANSFERRING DATA FROM OR TO THE SUBSYSTEM
Explanation: The request was terminated because the TME 10 OPC subsystem had to wait too long for data to be
transferred to or from the dialog address space. The TME 10 OPC subsystem rejected this request to be able to
service other requests.
System action: The request is rejected.
User response: Try again and if the error persists, contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for messages concerning the
general service subtask and preceding the long delay. Correct all errors and then restart the TME 10 OPC
subsystem.
EQQX264E THE REQUEST TO CHANGE THE OPERATION FAILED, REASON CODE XSSRS
Explanation: Your request to change the status of the operation was rejected by the event manager. Reason code
XSSRS provides debugging information for IBM personnel.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: To determine the cause of the error, review the TME 10 OPC message log and
look for messages concerning the event manager and issued at the time of the request. Correct all errors and then
restart the TME 10 OPC subsystem. If you cannot determine the cause of the error and if the error persists, contact
your IBM representative.
340
TME 10 OPC Messages and Codes
EQQX265E Ÿ EQQX268W
EQQX265E ATTEMPT TO READ A RECORD FAILED, REASON CODE XSSRS
Explanation: The attempt to read a record failed. Reason code XSSRS provides debugging information for IBM
personnel.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log and look for I/O error messages issued at
the time of the request. Correct all errors and then restart the TME 10 OPC subsystem. If the error persists, collect
information in the form of the sequence of actions leading to the error, and if possible, the data it may be dependent
on. Then contact your IBM representative.
EQQX266E A JOBLIB OR PROCLIB RECORD READ FAILED, REASON CODE XSSRS
Explanation: Reason code XSSRS gives the reason for the failure to read a record. The code issued depends on
the type of request.
The reason codes and their meanings are:
1
The TME 10 OPC JCL library dataset (EQQJBLIB) could not be opened. Message EQQW500E in the TME 10
OPC message log, when issued at the time of TME 10 OPC start, further explains the reason for the failure.
2
The TME 10 OPC JCL library dataset (EQQJBLIB) contains records with invalid length. Message EQQW501E in
the TME 10 OPC message log, when issued at the time of TME 10 OPC start, further explains the reason for the
failure.
3
The joblib I/O exit, EQQUX002, was not loaded. Message EQQW521E in the TME 10 OPC message log, when
issued at the time of TME 10 OPC start, further explains the reason for the failure.
4
The joblib I/O exit, EQQUX002, returned return code 241, which indicates that an I/O error has occurred in the exit
routine. Message EQQW520E in the TME 10 OPC message log further explains the reason for the I/O error.
5
The joblib I/O exit, EQQUX002, returned return code 242, which indicates that it could not open one of its input
datasets. Message EQQW516E in the TME 10 OPC message log further explains the reason for the I/O error.
6
The joblib I/O exit, EQQUX002, returned an invalid return code.
System action: An empty JCL member is presented.
User response: You may proceed by editing the empty JCL member. Then you should notify your system
programmer about the error.
System programmer response: To determine the cause of the error, use the reason code and the corresponding
message (if any) in the TME 10 OPC message log. Correct all errors and then restart the TME 10 OPC subsystem.
If the error persists, collect information in the form of the sequence of actions leading to the error, and if possible, the
data it may be dependent on. Then contact your IBM representative.
EQQX267W ACCESS REJECTED, DATA SET USED BY ANOTHER OPC/ESA FUNCTION
Explanation: The record could not be read because the dataset was held for update by another TME 10 OPC
function.
System action: The request is rejected.
User response: Try again later.
EQQX268W UPDATE REJECTED, DATA SET USED BY ANOTHER OPC/ESA FUNCTION
Explanation: The record update could not be carried out because the dataset was held for update by another
TME 10 OPC function.
System action: The request is rejected.
User response: Try again later.
Chapter 31. EQQXnnn Messages
341
EQQX269E Ÿ EQQX300E
EQQX269E THE LTP DATA SET IS BEING USED BY A BATCH FUNCTION, TRY LATER
Explanation: You cannot access the long-term plan dataset because it is being used by a batch function.
System action: The request is rejected.
User response: Try again later.
EQQX270E THE JS DATA SET IS IN USE, TRY LATER
Explanation: You have requested a function that requires access to the JCL repository file, but this file is not
available at the moment.
System action: The request is rejected.
User response: Wait a few seconds and then repeat the request.
EQQX271E A SEVERE ERROR OCCURRED IN THE GENERAL SERVICE TASK
Explanation: Your request to use the general service function could not be granted because a severe error occurred
in the general service subtask.
System action: The request is rejected.
User response: Try again later. If the error persists, contact your system programmer.
System programmer response: To determine the cause of the error, review the TME 10 OPC message log and
look for messages concerning the general service subtask and issued at the time of the request. Correct all errors
and then restart the TME 10 OPC subsystem. If the error persists, collect information in the form of the sequence of
actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM representative.
EQQX274E AN I/O REQUEST SPECIFIES TOO LARGE RECORD SIZE
Explanation: Your request to create or modify a record resulted in the record exceeding the maximum size of the
VSAM record.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Check the record size against the VSAM file definition. For more information, refer
to TME 10 OPC Installation Guide.
EQQX300E AN APPLICATION DESCRIPTION RECORD IS TOO LARGE TO BE SAVED
Explanation: Current AD record is larger than the maximum record size of the AD data base.
System action: The request to write the record is rejected.
Problem determination: Refer to the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. The application may
have to be split into two applications. If you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative. If the current AD record is valid,
it may become necessary to change the maximum record size of the AD file. The recommended way of doing this is
to define a new VSAM cluster similar to the current AD file but with a larger maximum record size. Copy the current
AD file to the new AD file using IDCAMS REPRO. Change all JCL referencing the old AD file to instead reference the
new AD file. Restart the TME 10 OPC controller and retry the failing AD file update request.
342
TME 10 OPC Messages and Codes
EQQX301E Ÿ EQQX304E
EQQX301E THE DB RECORD VERSION VERS IS INVALID
Explanation: The version of the record is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX302E THE APPLICATION ID AD IS INVALID
Explanation: The application ID entered contains invalid characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid application ID and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX303E STATUS AST FOR AD AD IS INVALID
Explanation: The application status is not A or P in the indicated application description.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX304E THE DB VALID-TO DATE VALTO IS INVALID
Explanation: The valid-to date is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid date and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
343
EQQX305E Ÿ EQQX309E
EQQX305E THE RUN CYCLE POINTER IS INVALID
Explanation: The pointer to the next run cycle is invalid. All run cycles must be before the first operation in the
application description record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX306E THE RECORD SIZE DOES NOT INCLUDE THE RUN CYCLE
Explanation: The size of the application description record does not include the run cycles.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX307E OFFSET TO NEXT RUN CYCLE IN RECORD IS INVALID
Explanation: The offset to the next run cycle in the application description record is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX308E THE OPERATION POINTER IS INVALID
Explanation: All operations must be last in the application description record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX309E THE RECORD SIZE DOES NOT INCLUDE OPERATION DATA
Explanation: The size of the application description record does not include operation data.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
344
TME 10 OPC Messages and Codes
EQQX310E Ÿ EQQX313E
EQQX310E OFFSET TO NEXT OPERATION IN RECORD IS INVALID
Explanation: The offset to next operation in the application description record is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX311E THE RECORD SIZE DOES NOT INCLUDE DEPENDENCIES AND SRS
Explanation: The application description record size does not include dependencies and special resources.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX312E THE DB VALID-FROM DATE VALFR IS INVALID
Explanation: The valid-from date entered is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid date and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX313E VALID-FROM DATE VALFR IS LATER THAN VALID-TO DATE VALTO
Explanation: The valid-to date must be later than the valid-from date.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter correct dates and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
345
EQQX314E Ÿ EQQX317E
EQQX314E AUTHORIZATION GROUP AUTHGR IS INVALID
Explanation: Authorization group field contains invalid characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid authorization group name and if the error occurred in batch, resubmit the job. If you
cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX315E OWNER ID IS MISSING IN DB NAME
Explanation: Owner ID is a required input field.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter an owner ID and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX316E LATEST UPDATE DATE LUDATE IS INVALID OR MISSING
Explanation: The date for latest update is invalid or missing.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX317E LATEST UPDATE TIME LUTIME IS INVALID OR MISSING
Explanation: The time for the latest update is invalid or missing.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
346
TME 10 OPC Messages and Codes
EQQX318E Ÿ EQQX321E
EQQX318E APPLICATION PRIORITY PRIO IS INVALID OR MISSING
Explanation: No or an invalid application priority was entered.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid application priority and if the error occurred in batch, resubmit the job. If you cannot
find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
| EQQX319E THE NUMBER OF OPERATIONS IS NOT IN THE RANGE 1 - 255
| Explanation: The number of operations may not be less than one and not more than 255.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX320E THE NUMBER OF RUN CYCLES NRUNC IS INVALID
Explanation: The number of run cycles in the application description record is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX321E THE DB RECORD IDENTIFIER RECID IS INVALID
Explanation: The record identifier is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
347
EQQX322E Ÿ EQQX325E
EQQX322E OFFSET TO FIRST RUN CYCLE IS INVALID IN AD AD
Explanation: The offset to the first run cycle is invalid in the indicated application description record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX323E OFFSET TO FIRST OPERATION IS INVALID IN AD AD
Explanation: The offset to the first operation is invalid in the indicated application description record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX324E INVALID CHARACTERS IN COMMON PART IN AD AD
Explanation: The common part of the indicated application description contains invalid characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX325E INVALID CALENDAR ID CALID IN AD AD
Explanation: An invalid calendar ID was entered in the indicated application description.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid calendar ID and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
348
TME 10 OPC Messages and Codes
EQQX326E Ÿ EQQX329E
EQQX326E THE CALENDAR CALID DOES NOT EXIST
Explanation: The calendar ID entered does not exist in the calendar database.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX327E THE DB VALID-FROM TIME TVALFR INVALID
Explanation: The valid-from time for the indicated record is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid date and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX328E THE DB VALID-TO TIME TVALTO IS INVALID
Explanation: The valid-to time for the indicated record is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid date and if the error occurred in batch, resubmit the job.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX329E THE RUN CYCLE PERIOD RUNPER CANNOT BE FOUND
Explanation: The period entered could not be found in the calendar database.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
349
EQQX330E Ÿ EQQX333E
EQQX330E A POSITIVE RUN DAY OFFSET IS NOT BLANK OR NUMERIC 1 - 999
Explanation: The positive run day offset entered is not blank or a number from 1 to 999.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid offset and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX331E THE FREE DAY SPECIFICATION FDRULE IS INVALID
Explanation: The free day rule entered is not E, 1, 2, 3, or 4.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid free day rule and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX332E THE RUN CYCLE TYPE NEGRC IS INVALID. It must be N, X, R or E
Explanation: Valid run cycle types are:
N
X
R
E
Normal offset-based run cycles
Negative offset-based run cycles
Regular rule-based run cycles
Exception rule-based run cycles.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (ddname EQQDUMP) for further information. This file contains a
copy of the record and the position of the error.
User response: Enter a valid run cycle type and if the error occurred in batch, resubmit the job.
EQQX333E THE INPUT ARRIVAL TIME IAT IS INVALID
Explanation: The input arrival time entered is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid time and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
350
TME 10 OPC Messages and Codes
EQQX334E Ÿ EQQX337E
EQQX334E INVALID RELATIVE DEADLINE DAY DLINER, MUST BE NUMERIC 0 - 99
Explanation: The relative deadline day entered is not a number from 0 to 99.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid relative day and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX335E THE DEADLINE TIME DLINET IS INVALID
Explanation: The deadline time entered is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid time and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX336E INVALID CHARACTERS IN RUN CYCLE SECTION IN AD AD
Explanation: The run cycle section in the indicated application description contains invalid characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX337E THE WORK STATION DESCRIPTION WS DOES NOT EXIST
Explanation: The workstation description for the indicated workstation could not be found in the workstation
database.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
351
EQQX338E Ÿ EQQX341E
EQQX338E INVALID OPERATION NUMBER OP IN AD AD
Explanation: The indicated operation number is invalid in the indicated application description.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid operation number and if the error occurred in batch, resubmit the job. If you cannot
find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX339E THE DURATION OF OPERATION WS OP IS INVALID, DUR
Explanation: The duration time is invalid for the indicated operation.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid duration time and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX340E SMOOTHING FACTOR OF WS OP IS INVALID, SMOOTH, must be 0 - 999
Explanation: The smoothing factor is not a number between 0 and 999.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid smoothing factor and if the error occurred in batch, resubmit the job. If you cannot find
a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX341E FEEDBACK LIMIT OF WS OP IS INVALID, FBLIM, MUST BE 100 - 999
Explanation: The feedback limit is not a number between 100 and 999.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid feedback limit and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
352
TME 10 OPC Messages and Codes
EQQX342E Ÿ EQQX345E
EQQX342E ERROR TRACKING INDICATOR OF WS OP IS INVALID, AEC, MUST BE Y or N
Explanation: The error tracking indicator is not Y (yes) or N (no).
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid value and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX343E THE JOBNAME JOBNAME INVALID IN OPERATION WS OP
Explanation: The job name entered contains invalid characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid job name and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX344E START DAY OF WS OP IS INVALID, STRELD, MUST BE 0 - 99
Explanation: The relative input arrival day of the indicated operation is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid day and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX345E OPERATION WS OP INPUT ARRIVAL TIME IS INVALID
Explanation: The input arrival time of the indicated operation is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid time and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
353
EQQX346E Ÿ EQQX349E
EQQX346E DEADLINE DAY OF WS OP IS INVALID, DLINER, MUST BE 0 - 99
Explanation: The relative deadline day of the indicated operation is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid day and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX347E OPERATION WS OP DEADLINE TIME IS INVALID
Explanation: The relative deadline time of the indicated operation is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid deadline time and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX348E WS RESOURCE USAGE OF WS OP IS INVALID, RWS, MUST BE 0 - 99
Explanation: The amount of workstation resource entered is not a number between 0 and 99.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a number between 0 and 99 and if the error occurred in batch, resubmit the job. If you
cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX349E NUMBER OF PS REQUIRED BY WS OP INVALID, PARSERV, MUST BE 1 - 99
Explanation: The number of parallel servers for the indicated operation is not a number between 1 and 99.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid number and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
354
TME 10 OPC Messages and Codes
EQQX350E Ÿ EQQX353E
EQQX350E NUMBER OF INTERNAL PREDECESSORS NOINPR INVALID IN WS OP
Explanation: The number of internal predecessors is invalid in the operation part of the application description
record for the indicated operation.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX351E NUMBER OF EXTERNAL PREDECESSORS NOEXPR INVALID IN WS OP
Explanation: The number of external predecessors is invalid in the operation part of the application description
record for the indicated operation.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX352E NUMBER OF SPECIAL RESOURCES NOSR INVALID IN WS OP
Explanation: The number of special resources is invalid in the operation part of the application description record for
the indicated operation.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX353E INVALID CHARACTERS IN OPERATION PART IN AD AD
Explanation: The operation part of the indicated application description contains invalid characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
355
EQQX354E Ÿ EQQX357E
EQQX354E WORK STATION PREIWS IS INVALID AS A PREDECESSOR TO WS OP
Explanation: The indicated internal predecessor workstation could not be found in the workstation description
database.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX355E INVALID OPERATION NUMBER IOP IN PREDECESSOR TO WS OP
Explanation: The indicated internal predecessor operation number could not be found.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid operation number and if the error occurred in batch, resubmit the job. If you cannot
find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX356E INVALID TRANSPORT TIME TRTI FOR PREDECESSOR PREIWS IOP
Explanation: The transport time for the indicated internal predecessor is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid transport time and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX357E INVALID CHARACTERS IN PREDECESSOR BLOCK FOR WS OP
Explanation: The predecessor part for the indicated operation contains invalid characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
356
TME 10 OPC Messages and Codes
EQQX358E Ÿ EQQX361E
EQQX358E INVALID AD PREAD IN THE PREDECESSOR FOR WS OP
Explanation: The indicated external predecessor application description could not be found in the AD database.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX359E INVALID WORK STATION PREEWS IN THE PREDECESSOR FOR WS OP
Explanation: The indicated external predecessor workstation could not be found.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX360E INVALID OPERATION NUMBER EOP IN PREDECESSOR FOR WS OP
Explanation: The indicated external predecessor operation number could not be found.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid operation number and if the error occurred in batch, resubmit the job. If you cannot
find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX361E INVALID LTP PRINT OPTION LTPPO IN PREDECESSOR PREEWS EOP
Explanation: The LTP print option in the indicated external predecessor is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid print option and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
357
EQQX362E Ÿ EQQX365E
EQQX362E SPECIAL RESOURCE NAME IS BLANK IN OPERATION WS OP
Explanation: The special resource name for the indicated operation is blank.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a special resource name and if the error occurred in batch, resubmit the job. If you cannot
find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX363E SPECIAL RESOURCE HELD OPTION TYPE HOPT IS INVALID
Explanation: The special resource held option type is not X or S.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid held option type and if the error occurred in batch, resubmit the job. If you cannot find
a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX364E SPECIAL RESOURCE BLOCK CONTAINS INVALID CHARACTERS
Explanation: The special resource part in the application description contains invalid characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX365E DUPLICATE OPERATIONS OP EXIST IN AD AD
Explanation: The indicated application description contains two or more operations with the same operation number.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter unique operation numbers for all operations and if the error occurred in batch, resubmit the
job. If you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
358
TME 10 OPC Messages and Codes
EQQX366E Ÿ EQQX369E
EQQX366E A PREDECESSOR TO OPERATION WS OP DOES NOT EXIST
Explanation: One predecessor for the indicated operation could not be found in the application description record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX367E THERE IS A LOOP IN THE APPLICATION NETWORK
Explanation: The application network contains a loop.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX368E ALL OPERATIONS NOT IN NETWORK IN AD AD
Explanation: All operations are not in the network in the indicated application description.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX369E JOBNAME MISSING FOR OPERATION WS OP
Explanation: The indicated job setup, processor, or print operation has no job name.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid job name and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
359
EQQX370E Ÿ EQQX373E
EQQX370E JOB SETUP OPERATION WS OP HAS NOT A PROCESSOR SUCCESSOR
Explanation: The job setup operation indicated does not have a processor successor.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX371E PRINT OPERATION WS OP HAS NO PREDECESSOR
Explanation: The operation indicated does not have a predecessor. This is required for print operations.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX372E PRINT OPERATION WS OP HAS MORE THAN ONE PREDECESSOR
Explanation: Only one predecessor is allowed for print operations.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX373E PRINT OPERATION WS OP HAS NOT A PROCESSOR PREDECESSOR
Explanation: Print operations must have a processor as predecessor.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
360
TME 10 OPC Messages and Codes
EQQX374E Ÿ EQQX377E
EQQX374E WS OP HAS A PREDECESSOR WITH A DIFFERENT JOBNAME
Explanation: The indicated print operation has a predecessor with a different job name.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Correct the job name and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX375E THE RUN CYCLE VALIDITY END VALTO IS INVALID OR BEFORE/AT the start
Explanation: The entered run cycle valid-to date is invalid, or is not later than the start date.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid date and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX376E A NEGATIVE RUN DAY OFFSET IS NOT BLANK OR NUMERIC 1 - 999
Explanation: The entered negative run day offset is invalid.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid offset and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX377E THE APPLICATION DESCRIPTION AD DOES NOT EXIST
Explanation: The indicated application description does not exist in the AD database.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
361
EQQX378E Ÿ EQQX381E
EQQX378E APPLICATION DESCRIPTION AD HAS NO WS WORK STATION
Explanation: The indicated workstation does not exist in the indicated application description.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX379E APPLICATION DESCRIPTION AD HAS NO OPERATION OP
Explanation: The indicated operation does not exist in the indicated application description.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX380E APPLICATION DESCRIPTION AD HAS NO WS OP operation
Explanation: The indicated operation does not exist in the indicated application description.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and correct the error. If the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX381E RUN CYCLE VALID-FROM DATE VALFR IS INVALID OR MISSING
Explanation: The valid-from date for the run cycle in invalid or missing.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid date and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
362
TME 10 OPC Messages and Codes
EQQX382E Ÿ EQQX385E
EQQX382E APPLICATION ID AD IS NOT BRACKETED DBCS
Explanation: The application identification field is specified to be in DBCS format, which means that it should start
with a shift-out (X'0E') character and end with a shift-in (X'0F') character. Either shift-out or shift-in or both are
missing.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX383E OWNER ID OWNER IS NOT BRACKETED DBCS
Explanation: The owner identification field is specified to be in DBCS format, which means that it should start with a
shift-out (X'0E') character and end with a shift-in (X'0F') character. Either shift-out or shift-in or both are missing.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX384E DBCS FIELD OF APPLICATION ID AD IS BLANK
Explanation: The application identification field is blank, and as it must contain at least one DBCS character, it is
invalid.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX385E APPL ID AD CONTAINS UNPAIRED SHIFT-OUT / SHIFT-IN CHAR
Explanation: The application identification field contains one or more superfluous shift-out or shift-in characters.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
363
EQQX386E Ÿ EQQX389E
EQQX386E OWNER ID OWNER CONTAINS UNPAIRED SHIFT-OUT / SHIFT-IN CHAR
Explanation: The owner identification field contains one or more superfluous shift-out or shift-in characters.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX387E APPLICATION ID AD CONTAINS INVALID DBCS-CHARACTER(S)
Explanation: The field indicated by the cursor contains out-of-range DBCS characters. With the exception of DBCS
blank, X'4040', each byte must be in the range X'41' – X'FE'.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX388E OWNER ID OWNER CONTAINS INVALID DBCS-CHARACTER(S)
Explanation: The field indicated by the cursor contains out-of-range DBCS characters. With the exception of DBCS
blank, X'4040', each byte must be in the range X'41' - X'FE'.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX389E OWNER ID OWNER IS BLANK
Explanation: The owner identification field is blank and, as it must contain at least one DBCS character, it is invalid.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
364
TME 10 OPC Messages and Codes
EQQX390E Ÿ EQQX393E
EQQX390E THE APPLICATION ID WAS NOT SPECIFIED
Explanation: No data has been entered in the application identification field.
System action: An empty field is not accepted.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX391E THE OWNER ID WAS NOT SPECIFIED
Explanation: No data has been entered in the owner identification field.
System action: An empty field is not accepted.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX392E THE APPLICATION ID AD CONTAINS AN ODD NUMBER OF BYTES
Explanation: The application identification field is specified as a Double Byte Character Set (DBCS) field, and
requires two bytes per character. Hence, 2, 4, 6, ..., bytes per character must be entered.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX393E THE OWNER ID OWNER CONTAINS AN ODD NUMBER OF BYTES
Explanation: The owner identification field is specified as a Double Byte Character Set (DBCS) field, and requires
two bytes per character. Hence, 2, 4, 6, ..., bytes per character must be entered.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
365
EQQX394E Ÿ EQQX397E
EQQX394E ALL SPECIAL RESOURCES IN AN OPERATION MUST BE UNIQUE
Explanation: A special resource must have a unique name in an operation.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check for misspellings or delete the duplicate entry. If the error occurred in batch, resubmit the job.
If you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX395E ALL INTERNAL PREDECESSORS IN AN OPERATION MUST BE UNIQUE
Explanation: A duplicate internal predecessor was found in an operation.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Delete the duplicate internal predecessor and, if the error occurred in batch, resubmit the job. If you
cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX396E ALL EXTERNAL PREDECESSORS IN AN OPERATION MUST BE UNIQUE
Explanation: A duplicate external predecessor was found in an operation.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Delete the duplicate external predecessor and, if the error occurred in batch, resubmit the job. If
you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX397E OWNER ID OWNER CONTAINS LOWER CASE CHARACTERS
Explanation: The owner ID cannot contain lowercase characters.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Correct the data and reenter. If the error occurred in batch, resubmit the job. If you cannot find the
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
366
TME 10 OPC Messages and Codes
EQQX398E Ÿ EQQX401E
EQQX398E DUPLICATE POSITIVE RUN DAY OFFSETS WERE FOUND IN A RUN CYCLE
Explanation: All positive run day offsets must be unique in a run cycle.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Delete the duplicates and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX399E DUPLICATE NEGATIVE RUN DAY OFFSETS WERE FOUND IN A RUN CYCLE
Explanation: All negative run day offsets must be unique in a run cycle.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Delete the duplicate run days and if the error occurred in batch, resubmit the job. If you cannot find
a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX400E THE CALENDAR DATA BASE RECORD SIZE IS INVALID
Explanation: The calendar description record may not be larger than 32768 bytes (32KB), or shorter than the size of
the common part of the calendar.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: If the size is too large, the calendar may have to be split into two calendars. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX401E THE CALENDAR ID CALID IS INVALID
Explanation: The calendar ID in the calendar description record contains invalid characters or does not start with a
capital letter or national language characters.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Correct calendar ID and retry. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
367
EQQX402E Ÿ EQQX405E
EQQX402E WORK DAY END TIME IS INVALID OR MISSING
Explanation: Work day end time must be a value of '0000' to '2400' where the first two characters represent the
hour, and the last two characters represent the minutes.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Correct the time and retry. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX403E NUMBER OF WEEKDAYS / SPECIFIC DATES IS INVALID
Explanation: The number of weekday/specific dates has an invalid value in the calendar description record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Investigate the record and correct the error. If you cannot find a valid reason for the error, contact
your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX404E INVALID CHARACTERS IN COMMON SECTION OF CALENDAR
Explanation: An invalid character was found in a reserved field in the common section of the calendar description
record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Investigate the record and correct the error. If you cannot find a valid reason for the error, contact
your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX405E THE RECORD SIZE DOES NOT INCLUDE WEEK DAYS/SPECIFIC DATES
Explanation: The total record size of the calendar description record is too short to contain the common section plus
all week days/specific dates.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Investigate the record and correct the error. If you cannot find a valid reason for the error, contact
your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
368
TME 10 OPC Messages and Codes
EQQX406E Ÿ EQQX409E
EQQX406E A WEEK DAY IN CALENDAR IS INVALID
Explanation: For a week day, the second character in the variable section is blank. The first character has a value
of 1 to 7 which corresponds with Monday to Sunday.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Correct the day and retry. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX407E WEEK DAYS IN CALENDAR ARE NOT IN ASCENDING ORDER
Explanation: Week days are not correctly sorted.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Correct the sequence and retry. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX408E STATUS OF WEEK DAY / SPECIFIC DATE IS NOT WORK NOR FREE
Explanation: The status of week day / specific date in the calendar description record must be W (work) or F (free).
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Correct the error and retry. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX409E A SPECIFIC DATE IN CALENDAR IS INVALID
Explanation: A specific date must have the format YYMMDD where YY is the last two characters in the year, MM is
the month number, and DD is the day in the month.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Correct the date and retry. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages
369
EQQX410E Ÿ EQQX413E
EQQX410E SPECIFIC DATES IN CALENDAR ARE NOT IN ASCENDING ORDER
Explanation: Specific dates are not correctly sorted.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Correct the sequence and retry. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX411E VARIABLE SECTION OF CALENDAR CONTAINS INVALID CHARACTERS
Explanation: An invalid character was found in a reserved field in the variable section of the calendar description
record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Investigate the record and correct the error. If you cannot find a valid reason for the error, contact
your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX412E CANCEL IF LATE IS ONLY ALLOWED FOR TIME JOBS
Explanation: Cancel if late can only be specified for time-dependent jobs.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Specify cancel = no or make the operation time dependent. If the error occurred in batch, resubmit
the job. If you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX413E RELATIVE START DAY IS MISSING FOR WS OP
Explanation: An operation input arrival relative day must be specified if the operation is time dependent.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a relative start day and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
370
TME 10 OPC Messages and Codes
EQQX414E Ÿ EQQX419E
EQQX414E START TIME IS MISSING FOR WS OP
Explanation: An operation input arrival time must be specified if the operation is time dependent.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a start time and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX415E JOBNAME IS MISSING IN OPERATION WS OP
Explanation: Job name must be specified for the computer, printer, and job setup operations.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid job name and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX416E JOB SETUP OPERATION WS OP HAS NO SUCCESSOR WITH same jobname
Explanation: The job setup operation indicated has no successor with the same job name.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check and correct the job names for the computer operations succeeding the indicated operation. If
the error occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system
programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and if the error persists, contact your IBM representative.
EQQX417E THE VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER
Explanation: Data entry error; see “Data Entry Errors” on page 2.
EQQX418E THE VARIABLE TABLE IS NOT DEFINED TO OPC/ESA
Explanation: Data entry error; see “Data Entry Errors” on page 2.
You have tried to define a variable table ID that does not exist in TME 10 OPC's database.
EQQX419E NUMBER OF PARALLEL SERVERS MUST BE 1 FOR OPERATION WS OP
Explanation: The operation specified runs on a computer workstation and can only use one parallel server.
System action: The application description is not updated. Current application description record is printed on the
diagnostic file (ddname EQQDUMP).
User response: Change the number of parallel servers to 1 and, if the error occurred in batch, resubmit the batch
job.
Chapter 31. EQQXnnn Messages
371
EQQX420E Ÿ EQQX424E
EQQX420E REQUEST TYPE REQ IS NOT SUPPORTED
Explanation: An internal parameter list, consisting of a sequence of control blocks, is validated and found to have an
invalid request type.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks.
User response: This is likely to be an internal error. If the error occurs in a program using the program interface
function, do the requests in a different order and rerun.
System programmer response: If you cannot find a valid reason for the error, make the diagnostic file and the
message log available and contact your IBM representative.
EQQX421E THE SPECIFIED CONTROL BLOCK LENGTH LEN IS INVALID
Explanation: An internal parameter list, consisting of a sequence of control blocks, is validated and found to have an
invalid length.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks.
User response: This is likely to be an internal error. If the error occurs in a program using the program interface
function, do the requests in a different order and rerun.
System programmer response: If you cannot find a valid reason for the error, make the diagnostic file and the
message log available and contact your IBM representative.
EQQX422E THE INPUT ARRIVAL DATE IS REQUIRED BUT NOT AVAILABLE
Explanation: The input arrival date is a required parameter in the request. No input arrival date is specified.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Specify input arrival date as an argument in the program interface request.
EQQX423E INPUT ARRIVAL DATE IAD IS INVALID
Explanation: The input arrival date is not a valid internal TME 10 OPC date, in the format YYMMDD.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Correct the invalid date and rerun.
EQQX424E THE INPUT ARRIVAL TIME IS REQUIRED BUT NOT AVAILABLE
Explanation: The input arrival time is a required parameter in the request. No input arrival time is specified.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Specify input arrival time as an argument in the program interface request.
372
TME 10 OPC Messages and Codes
EQQX425E Ÿ EQQX429E
EQQX425E THE REQUEST CONTAINS INCONSISTENT APPLICATION IDS, AD and RAD
Explanation: In the program interface request an application description is given by the data area parameter. The
ID of an application is also given by the arguments parameters. The data area application description ID differs from
the ID given by the arguments.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Either set the data area pointer to zero, or remove the application ID from the arguments parameter
of the program interface request.
EQQX426E EITHER BOTH DEADLINE DATE AND TIME MUST BE GIVEN OR NEITHER DATE NOR TIME
Explanation: If the deadline date is specified, the deadline time must also be specified, and vice versa.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Specify either both deadline date and deadline time, or remove both from the arguments parameter
of the program interface request.
EQQX427E THE DEADLINE DATE DLD IS INVALID
Explanation: The deadline date is not a valid internal TME 10 OPC date, in the format YYMMDD.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Correct the invalid date and rerun.
EQQX428E THE PREDECESSOR INPUT ARRIVAL DATE IS REQUIRED BUT NOT AVAILABLE
Explanation: The predecessor input arrival date is a required parameter in the request. It is not specified.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Specify predecessor input arrival date as an argument in the program interface request.
EQQX429E THE PREDECESSOR INPUT ARRIVAL TIME IS REQUIRED BUT NOT AVAILABLE
Explanation: The predecessor input arrival time is a required parameter in the request. It is not specified.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Specify predecessor input arrival time as an argument in the program interface request.
Chapter 31. EQQXnnn Messages
373
EQQX430E Ÿ EQQX434E
EQQX430E THE PREDECESSOR APPLICATION ID IS REQUIRED BUT NOT AVAILABLE
Explanation: The predecessor application ID is a required parameter in the request. It is not specified.
System action: If this is a request to the program interface function, the request is rejected and control is returned
with the return code set to error.
Problem determination: The diagnostic file (with ddname EQQDUMP) contains a dump of the control blocks
validated when the error was detected.
User response: Specify the predecessor application ID as an argument in the program interface request.
EQQX431E AST IS NOT A VALID STATUS CODE
Explanation: Status AST is not a valid status code. The codes supported are V, T, S, and C.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid status code and resubmit the job. If you cannot find a valid reason for the error,
contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If the
error persists, contact your IBM representative.
EQQX432E AEC IS NOT A VALID CODE FOR ADDING FUNCTION
Explanation: Code AEC specifies an updating function that is not supported.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If the
error persists, contact your IBM representative.
EQQX433E A MAXIMUM OF 100 EXTERNAL PREDECESSORS ARE ALLOWED
Explanation: No more than 100 external predecessors may be specified in an application.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX434E IAD IAT AD CANNOT HAVE A DEPENDENCY ON ITSELF
Explanation: An occurrence cannot be dependent on itself.
System action: A dump of the record is written to the diagnostic file (EQQDUMP).
User response: Check your dependency specifications.
374
TME 10 OPC Messages and Codes
EQQX435E Ÿ EQQX440E
EQQX435E ROW COMMAND IS NOT VALID FOR A PENDING APPLICATION
Explanation:
Calculate and Print run days (A) row command is valid only for application versions that are active.
System action: Request is rejected.
User response: Use these row commands against only active applications.
EQQX436E NO RUNCYCLE OFFSETS HAVE BEEN DEFINED FOR RUNCYCLE PERIOD = RUNPER
Explanation: An attempt was made to save an invalid application description record. The record being saved
contained a runcycle that did not have any runcycle offsets. This is not valid since each runcycle must contain at
least one runcycle offset.
System action: If this message is issued in an TME 10 OPC dialog the dialog waits for you to correct the error. If
the message is issued in an TME 10 OPC batch program additional messages may be issued and the batch program
may terminate. The invalid application description record is not saved.
Problem determination: Review the diagnostic file (ddname EQQDUMP) for further information. Current application
description is printed in the diagnostic file and the position of the invalid value in the record is given.
User response: Enter at least one runcycle offset value.
EQQX437E NEGATIVE RUNDAY SPECIFICATION CONTAINS ERRORS
Explanation: The runday fields in current application description contain embedded blanks and the application
description cannot be saved.
System action: The dialog waits for you to correct the error.
Problem determination: Review the diagnostic file (ddname EQQDUMP) for further information. Current application
description is printed in the diagnostic file and the position of the invalid runday in the record is given.
User response: Enter a valid runday value.
EQQX438E THE RESOURCE QUANTITY IS NOT IN THE RANGE 1 - 999,999
Explanation: The quantity specified for a resource is not within the valid range.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) for further information. Current application
description is printed in the diagnostic file and the position of the invalid resource in the record is given.
User response: Enter a valid resource quantity. If the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
EQQX439E THE ON ERROR FIELD FOR A RESOURCE CONTAINS AN INVALID VALUE
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) for further information. Current application
description is printed in the diagnostic file and the position of the invalid resource specification in the record is given.
User response: Enter a valid On error value. If the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
EQQX440E THE ETT DATA BASE RECORD SIZE IS INVALID
Explanation: The size of the ETT data base record is not acceptable by the system.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) for further information. Current ETT data
base record is printed in the diagnostic file and also the erroneous specification position, in the record, is given.
User response: Contact your system programmer.
Chapter 31. EQQXnnn Messages
375
EQQX441E Ÿ EQQX446E
EQQX441E THE NAME OF THE ETT TRIGGER IS BLANK
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If you cannot find a valid reason for the error, contact your system programmer.
EQQX442E RESERVED FIELDS IN ETT RECORD MUST BE NULL
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If you cannot find a valid reason for the error, contact your system programmer.
EQQX443E THE ALL WORK STATION CLOSED DATA BASE RECORD SIZE IS INVALID
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If you cannot find a valid reason for the error, contact your system programmer.
EQQX444E RESERVED FIELDS IN ALL WORK STATION CLOSED RECORD MUST BE BLANK
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If you cannot find a valid reason for the error, contact your system programmer.
EQQX445E THE PERIOD DATA BASE RECORD SIZE IS INVALID
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If you cannot find a valid reason for the error, contact your system programmer.
EQQX446E THE PERIOD INTERVAL START OR END DATE IS INVALID
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If the error occurred in batch, correct the record and resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
376
TME 10 OPC Messages and Codes
EQQX447E Ÿ EQQX455E
EQQX447E RESERVED FIELDS IN PERIOD RECORD MUST BE BLANK
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If you cannot find a valid reason for the error, contact your system programmer.
EQQX448E PERIOD TYPE MUST BE A, W or N
Explanation: Data entry error; see “Data Entry Errors” on page 2.
| The valid period type values are A, W, and N.
EQQX450E THE WORK STATION DATA BASE RECORD SIZE IS INVALID
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file.
User response: If you cannot find a valid reason for the error, contact your system programmer.
EQQX451E RESERVED FIELDS IN WORK STATION RECORD MUST BE BLANKS
Explanation: The error is detected when you try to validate the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If you cannot find a valid reason for the error, contact your system programmer.
EQQX453E AN INVALID WEEK DAY NAME WAS SPECIFIED
Explanation: The error is detected when validating the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If the error occurred in batch, correct the record and resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
EQQX454E WEEK DAY/SPECIFIC DATES NOT ENTERED IN ASCENDING ORDER
Explanation: The error is detected when validating the record before writing it to the data base.
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current record is printed in the diagnostic file and the position of the invalid field in the record is given.
User response: If the error occurred in batch, correct the record and resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
EQQX455E AN INVALID SPECIFIC DATE WAS SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Chapter 31. EQQXnnn Messages
377
EQQX462E Ÿ EQQX467E
EQQX462E FIELD HIPERBATCH IS INVALID, MUST BE Y OR N
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given.
User response: Enter a valid Hiperbatch value. If the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
EQQX463E FIELD USED FOR IS INVALID, MUST BE N,P,C OR B
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given.
User response: Enter a valid Used For value. If the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
EQQX464E DAY OF WEEK OR DATE INVALID IN FIRST INTERVAL, MUST BE ZERO AND BLANK
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. The first interval contains default values.
User response: If you cannot find a valid reason for the error, contact your IBM representative.
EQQX465E DEFAULT QUANTITY INVALID, MUST BE A POSITIVE VALUE
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given.
User response: Set Defauly Quantity to zero in the common segment of the resource description record. If the error
occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.
EQQX466E DAY OF WEEK IS ZERO AND DATE IS BLANK IN INTERVAL OTHER THAN FIRST
System action: The request to write the record is rejected.
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given.
User response: Day of week or Date must be specified in all but the first interval of a resource description. Set
either Day of week to the value for a week day (1–7) or the value for the Standard day (8). In that case the Date field
should be reset. Or set the Day of week to 0 and the Date to a specific date in the form YYMMDD. If the error
occurred in batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.
EQQX467E DEFAULT AVAILABILITY IS INVALID, MUST BE Y OR N
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given.
User response: Enter a valid Default Avail value. If the error occurred in batch, resubmit the job. If you cannot find
a valid reason for the error, contact your system programmer.
378
TME 10 OPC Messages and Codes
EQQX468E Ÿ EQQX474E
EQQX468E FIELD AVAIL IS INVALID IN INTERVAL IVLID. IT MUST BE Y, N OR BLANK
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day
number (8) or a date, followed by the interval start time.
User response: Enter a valid Avail value. If the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
EQQX470E FIELD WEEK DAY IS INVALID IN INTERVAL IVLID, MUST BE IN RANGE 0-8
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day
number (8) or a date, followed by the interval start time.
User response: Enter a valid Week day value. If the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
EQQX471E BOTH FIELD WEEK DAY AND DATE IN INTERVAL IVLID HAVE A VALUE
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day
number (8) or a date, followed by the interval start time.
User response: Reset either Week day or Date. If the error occurred in batch, resubmit the job. If you cannot find
a valid reason for the error, contact your system programmer.
EQQX472E FIELD DATE IS INVALID IN INTERVAL IVLID, MUST BE IN FORMAT YYMMDD
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day
number (8) or a date, followed by the interval start time.
User response: Enter a Date in format YYMMDD. If the error occurred in batch, resubmit the job. If you cannot find
a valid reason for the error, contact your system programmer.
EQQX473E FIELD FROM TIME IS INVALID IN INTERVAL IVLID, MUST HAVE FORMAT HHMM
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day
number (8) or a date, followed by the interval start time.
User response: Enter From time in format HHMM. If the error occurred in batch, resubmit the job. If you cannot
find a valid reason for the error, contact your system programmer.
EQQX474E FIELD TO TIME IS INVALID IN INTERVAL IVLID, MUST BE IN FORMAT HHMM
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day
number (8) or a date, followed by the interval start time.
User response: Enter To time in format HHMM. If the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
Chapter 31. EQQXnnn Messages
379
EQQX475E Ÿ EQQX502E
EQQX475E FIELD FROM TIME NOT EARLIER THAN TO TIME IN INTERVAL IVLID
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. IVLID identifies the interval by the week day number (1–7), the standard day
number (8) or a date, followed by the interval start time.
User response: Change From time or To time, From time must be earlier than To time. If the error occurred in
batch, resubmit the job. If you cannot find a valid reason for the error, contact your system programmer.
EQQX476E INTERVAL OVERLAP, ANOTHER INTERVAL OVERLAPS INTERVAL IVL
Problem determination: Review the diagnostic file (ddname EQQDUMP) of the TME 10 OPC Controller for further
information. Current resource description is printed in the diagnostic file and the position of the invalid resource
specification in the record is given. IVL identifies the interval by the week day number (1–7), the standard day number
(8) or a date, followed by the interval start time.
User response: Change From and To times in the interval definitions for the identified day. An interval may start on
the same minute as the preceeding interval ends, or later. If the error occurred in batch, resubmit the job. If you
cannot find a valid reason for the error, contact your system programmer.
EQQX500E GROUP DEFINITION ID GRPDEF IS INVALID
Explanation: The group definition ID field contains invalid characters.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot
find the reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause of the error, contact your IBM representative.
EQQX501E GROUP DEF ID GRPDEF NOT IN BRACKETED DBCS FORMAT
Explanation: The group definition ID field should be in DBCS format. That is, it should start with a shift-out (X'0E')
character and end with a shift-in (X'0F') character. Either shift-out or shift-in, or both, are missing.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot
find the reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause of the error, contact your IBM representative.
EQQX502E UNPAIRED SHIFT-OUT OR SHIFT-IN CHARS IN GRPDEF
Explanation: The group definition ID field contains one or more extra shift-out or shift-in characters.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot
find the reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause of the error, contact your IBM representative.
380
TME 10 OPC Messages and Codes
EQQX503E Ÿ EQQX604E
EQQX503E INVALID DBCS-CHARACTER(S) IN GRPDEF
Explanation: The group definition ID field contains out-of-range DBCS characters. With the exception of DBCS
blank, X'4040', each byte must be in the range X'41' to X'FE'.
System action: The data is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the failing record and the position of the error.
User response: Specify a valid group definition ID. If the error occurred in batch, resubmit the job. If you cannot
find the reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause of the error, contact your IBM representative.
EQQX504E ODD NUMBER OF BYTES IN GRPDEF
Explanation: The group definition ID field is spe