IBM Tivoli Workload

Scheduler for z/OS 򔻐򗗠򙳰

Messages and Codes

Version 8.2

SC32-1267-00
IBM Tivoli Workload
Scheduler for z/OS 򔻐򗗠򙳰

Messages and Codes

Version 8.2

SC32-1267-00
 Note
Before using this information and the product it supports, read the information in “Notices” on page 475.

First Edition (June 2003)

This edition applies to version 8, release 2, modification 0 of IBM Tivoli Workload Scheduler for z/OS (program
number 5697-WSZ) and to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 1991, 2003. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
 Contents
Preface . . . . . . . . . . . . . . . v Chapter 16. EQQKnnn Messages . . . 151
Who Should Read This Manual . . . . . . . . v
What This Manual Contains . . . . . . . . . v Chapter 17. EQQLnnn Messages . . . 155
Publications . . . . . . . . . . . . . . vi
Publications for IBM Tivoli Workload Scheduler
Chapter 18. EQQMnnn Messages . . . 163
for z/OS . . . . . . . . . . . . . . vi
Publications for IBM Tivoli Workload Scheduler vi
| Using LookAt to Look Up Message Explanations vii Chapter 19. EQQNnnn Messages . . . 209
Accessing Publications Online . . . . . . . vii
Softcopy Collection Kit . . . . . . . . . viii Chapter 20. EQQOnnn Messages . . . 225
Ordering Publications . . . . . . . . . viii
Accessibility . . . . . . . . . . . . . . viii Chapter 21. EQQPnnn Messages . . . 227
Contacting IBM Software Support . . . . . . . ix
Conventions Used in This Manual . . . . . . . ix
What Is New in This Version. . . . . . . . ix
Chapter 22. EQQQnnn Messages . . . 239

Chapter 1. Introduction . . . . . . . . 1 Chapter 23. EQQRMnn Messages . . . 245

Message Format . . . . . . . . . . . . . 1
Where Messages Are Presented . . . . . . . . 1 Chapter 24. EQQRnnn Messages . . . 249
Data Entry Errors . . . . . . . . . . . . . 2
System action . . . . . . . . . . . . . 3 Chapter 25. EQQSUnn Messages . . . 257
User response . . . . . . . . . . . . . 3
Chapter 26. EQQSnnn Messages . . . 261
Chapter 2. EQQATnn Messages . . . . 5
Chapter 27. EQQTTnn Messages . . . 265
Chapter 3. EQQAnnn Messages . . . . 9
Chapter 28. EQQTnnn Messages . . . 269
Chapter 4. EQQCnnn Messages . . . . 27
Chapter 29. EQQUnnn Messages . . . 273
Chapter 5. EQQCLnnn Messages . . . 35
Chapter 30. EQQVnnn Messages . . . 275
Chapter 6. EQQCNnnn Messages . . . 51
Chapter 31. EQQWLnn Messages . . . 281
Chapter 7. EQQDnnn Messages . . . . 55
Chapter 32. EQQWnnn Messages . . . 285
Chapter 8. EQQEXnn Messages . . . . 59
Chapter 33. EQQXnnn Messages . . . 315
Chapter 9. EQQEnnn Messages . . . . 61
Chapter 34. EQQYnnn Messages . . . 363
Chapter 10. EQQFnnn Messages . . . 81
Chapter 35. EQQZnnn Messages . . . 381
Chapter 11. EQQFxxx Messages . . . . 85
Chapter 36. EQQnnnn Messages . . . 409
Chapter 12. EQQGnnn Messages . . . 115
Chapter 37. Abend Codes . . . . . . 461
Chapter 13. EQQHnnn Messages . . . 119
Chapter 38. Reason Codes . . . . . 463
Chapter 14. EQQICnn Messages . . . 125
Chapter 39. Batch Program Codes and
Chapter 15. EQQJnnn Messages . . . 131 Messages . . . . . . . . . . . . . 473
EQQPDLF Batch Program Condition Codes . . . 473

© Copyright IBM Corp. 1991, 2003 iii

EQQPURGE Batch Program WTO Messages . . . 473 OpenSSL License . . . . . . . . . . . 477
Original SSLeay License . . . . . . . . . 478
Notices . . . . . . . . . . . . . . 475 Open Source: SNMP Library . . . . . . . . 479
Open Source: Test . . . . . . . . . . . . 476 Open Source: Time Zone Library . . . . . . . 479
Open Source: OpenSSL . . . . . . . . . . 477 Toolkit of Tivoli Internationalization Services . . . 480
LICENSE ISSUES . . . . . . . . . . . 477 Trademarks . . . . . . . . . . . . . . 480

iv IBM Tivoli Workload Scheduler for z/OS Messages and Codes

Preface
This book describes the messages that are issued by the following components of
Tivoli Workload Scheduler for z/OS.
v Controller
v Tracker
v Server
v Datastore
v Connector

Your workload can run on various platforms, but you control it from a central
z/OS system that runs the Tivoli Workload Scheduler for z/OS controller.

The term scheduler, when used in this book, refers to Tivoli Workload Scheduler for
z/OS.

The term z/OS is used in this guide to mean z/OS and OS/390® operating systems.
Where the term OS/390 appears, the related information applies only to OS/390
operating systems.

The acronym OPC, used in the text of some messages, refers to IBM Tivoli
Workload Scheduler for z/OS.

Who Should Read This Manual

This guide should be used by operators, system or application programmers, or by
anyone who is responsible for controlling or diagnosing problems in IBM Tivoli
Workload Scheduler for z/OS.

What This Manual Contains

This guide contains the following chapters:
v Chapter 1, “Introduction”, on page 1“Introduction”
Contains general information that applies to all product messages.
v Chapter 2, “EQQATnn Messages”, on page 5 through Chapter 36
List the product messages in alphanumeric order.
v Chapter 37, “Abend Codes”, on page 461
Lists Abend Codes.
v Chapter 38, “Reason Codes”, on page 463
Lists the IBM Tivoli Workload Scheduler for z/OS abend codes, in numeric
order.
v Chapter 39, “Batch Program Codes and Messages”, on page 473
Lists the codes and write-to-operator messages generated by IBM Tivoli
Workload Scheduler for z/OS batch programs.

© Copyright IBM Corp. 1991, 2003 v

Publications
This section lists publications in the Tivoli® Workload Scheduler for z/OS library and
any other related documents. It also describes how to access Tivoli publications
online, how to order Tivoli publications, and how to make comments on Tivoli
publications.

Publications for IBM Tivoli Workload Scheduler for z/OS

The following documents are available in the IBM Tivoli Workload Scheduler for
z/OS library:
v Customization and Tuning, SC32-1265
Describes how to customize IBM Tivoli Workload Scheduler for z/OS.
v Diagnosis Guide and Reference, SC32-1261
Provides information to help diagnose and correct possible problems when using
the product.
v General Information, SC32-1256
Describes the benefits of the entire IBM Tivoli Workload Scheduler suite.
v Installation Guide, SC32-1264
Describes how to install IBM Tivoli Workload Scheduler for z/OS.
v IBM Tivoli Job Scheduling Console Release Notes, SC32-1258
Provides information about working with IBM Tivoli Workload Scheduler,
regardless of platform, from a common GUI.
v IBM Tivoli Job Scheduling Console User’s Guide, SC32-1257
Provides information about working with IBM Tivoli Workload Scheduler,
regardless of platform, from a common GUI.
v Licensed Program Specifications, GI11-4208
Provides planning information to plan about IBM Tivoli Workload Scheduler for
z/OS.
v Managing the Workload, SC32-1262
Describes concepts and terminology of IBM Tivoli Workload Scheduler for z/OS
and provides instructions to get you working with the product as soon as
possible.
v Memo to Users, GI11-4209
Provides a summary of changes for the current release of the product.
v Program Directory, GI11-4203
Provided with the IBM Tivoli Workload Scheduler for z/OS installation tape,
describes all of the installation materials and gives installation instructions
specific to the product release level or feature number.
v Programming Interfaces, SC32-1266
Provides information to write application programs.
v Quick Reference, SC32-1268
Provides a quick and easy consultation reference to operate the product.

Publications for IBM Tivoli Workload Scheduler

The following manuals are available in the IBM Tivoli Workload Scheduler library:
v IBM Tivoli Workload Scheduler Planning and Installation Guide, SC32-1273
Describes planning and installing IBM Tivoli Workload Scheduler.
v IBM Tivoli Workload Scheduler Reference Guide, SC32-1274

vi IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 Explains the IBM Tivoli Workload Scheduler command line, understanding how
extended and network agents work, and integrating IBM Tivoli Workload
Scheduler with NetView® and with Tivoli Business System Manager.
v IBM Tivoli Workload Scheduler Troubleshooting and Error Messages, SC32-1275
Interprets IBM Tivoli Workload Scheduler error messages, and provides sources
of information that will help you in solving problems with IBM Tivoli Workload
Scheduler.
v IBM Tivoli Workload Scheduler for Applications User’s Guide, SC32-1278
Describes installing, using, and troubleshooting for the IBM Tivoli Workload
Scheduler extended agents.
v IBM Tivoli Workload Scheduler for Applications Release Notes, SC32-1279
Provides last-minute information about the IBM Tivoli Workload Scheduler
extended agents.
v IBM Tivoli Workload Scheduler AS/400® Limited FTA User’s Guide, SC32-1280
Describes installing, configuring, and using IBM Tivoli Workload Scheduler
fault-tolerant agents on AS/400.
v IBM Tivoli Workload Scheduler Plus Module User’s Guide, SC32-1276
Explains setting up and using the IBM Tivoli Workload Scheduler Plus module.
v IBM Tivoli Workload Scheduler Release Notes, SC32-1277
Explains late-breaking information about IBM Tivoli Workload Scheduler.

| Using LookAt to Look Up Message Explanations

| LookAt is an online facility that lets you look up explanations for most messages
| you encounter, as well as for some system abends and codes. Using LookAt to find
| information is faster than a conventional search because in most cases LookAt goes
| directly to the message explanation.

| You can access LookAt from the Internet at:

| http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/ or from anywhere in
| z/OS or z/OS.e where you can access a TSO/E command line (for example,
| TSO/E prompt, ISPF, z/OS UNIX System Services running OMVS).

| The LookAt Web site also features a mobile edition of LookAt for devices such as
| Pocket PCs, Palm OS, or Linux-based handhelds. So, if you have a handheld
| device with wireless access and an Internet browser, you can now access LookAt
| message information from almost anywhere.

| To use LookAt as a TSO/E command, you must have LookAt installed on your
| host system. You can obtain the LookAt code for TSO/E from a disk on your
| (SK3T-4270) or from the LookAt Web site’s Download link.

Accessing Publications Online

The product CD contains the publications that are in the product library. The
format of the publications is PDF, HTML, or both. To access the publications using
a Web browser, open the infocenter.html file. The file is in the appropriate
publications directory on the product CD.

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli Software Information
Center Web site. The Tivoli Software Information Center is located at the following
Web address:

Preface vii
 http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Click the IBM Tivoli Workload Scheduler for z/OS link to access the product
library.

Note: If you print PDF documents on other than letter-sized paper, select the Fit to
page check box in the Adobe Acrobat Print dialog. This option is available
when you click File → Print. Fit to page ensures that the full dimensions of a
letter-sized page print on the paper that you are using.

Softcopy Collection Kit

All the books in the library, except the licensed publications, are available in
displayable softcopy form in the following collection kits:
v IBM Online Library Omnibus Edition OS/390 Collection Kit, SK2T-6700.
v IBM Online Library z/OS Software Products Collection Kit, SK2T-4270.

You can read the softcopy books on CD-ROMs using these IBM® licensed
programs:
v Softcopy Reader
v BookManager® READ/2
v BookManager READ/DOS
v BookManager READ/6000

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 PDF and HTML on the Web.

Ordering Publications
You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755
v In Canada: 800-426-4968

In other countries, see the following Web site for a list of telephone numbers:

http://www.ibm.com/software/tivoli/order-lit/

Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface.You can also
use the keyboard instead of the mouse to operate all features of the graphical user
interface.

viii IBM Tivoli Workload Scheduler for z/OS Messages and Codes
 For additional information, see the Accessibility Appendix in the IBM Tivoli
Workload Scheduler for z/OS Installation Guide.

Contacting IBM Software Support

If you have a problem with any Tivoli product, you can contact IBM Software
Support. See the IBM Software Support Guide at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support,
depending on the severity of your problem, and the following information:
v Registration and eligibility
v Telephone numbers and e-mail addresses, depending on the country in which
you are located
v Information you must have before contacting IBM Software Support

Conventions Used in This Manual

The manual uses several typeface conventions for special terms and actions. These
conventions have the following meanings:

Information type Style convention Example

Commands All capital letters CREATE
References in the text to All capital letters QUANTITY
fields on panels
Input you should type in Monospace MYAPPLICATION
panel fields
First time new term Italics Application
introduced

What Is New in This Version

The following sections summarize the changes in this version of Tivoli Workload
Scheduler for z/OS.

z/OS Functions
v You can have the local time on a z/OS system change automatically, for
example, for daylight savings time, without having to stop and restart Tivoli
Workload Scheduler for z/OS.
v You can turn the JESLOG SPIN option on or off using the SPIN keyword in the
OPCOPTS statement. By default Tivoli Workload Scheduler for z/OS adds the
JESLOG=NOSPIN parameter to the JOB card when the following conditions
both occur:
– You submit a JCL on a CPU running z/OS Version 1.2 or higher.
– In the OPCOPTS initialization statement, you specify data store or job
completion checker activities.
v To facilitate migration from other scheduling products, Tivoli Workload
Scheduler for z/OS operations now accept a new symbolic name that can be up
to 54 characters long. This operation extended name enables you to represent the
job with something other than the operation number. You can specify the
operation extended name when you define an operation in the database or when

Preface ix
 you copy it into the current plan. You can also use it to filter queries on
operations in the database and current plan.
v You can use a mixed connection (SNA and XCF) between the controller and
allocated data stores.
v A new exit routine, EQQUXPIF, validates changes in an application description
(AD) made using the programming interface (PIF), batch loader (BL), and the
Job Scheduling Console (JSC).
v To increase the virtual storage from 16 MB to 2 GB, the Tivoli Workload
Scheduler for z/OS components have been changed to use 31-bit addressing
mode instead of 24-bit.

End-to-End Functions
v For fault-tolerant workstations, you can continue to use centralized scripts,
which are stored in the JOBLIB data set. With centralized scripts, you can
perform variable substitution, automatic recovery, JCL editing, and job setup (as
for the jobs in the JOBLIB). However, this implies a loss of fault tolerance and
requires downloading the script to the agent every time the job is submitted.
You need to weigh the benefits and disadvantages of using centralized scripts.
v You can use a new syntax to recover non-centralized jobs on distributed agents
automatically when the jobs abend. This recovery is similar to the recovery in
the distributed environment.
v You can use variable substitution for jobs that run on fault-tolerant workstations
and that do not use centralized scripts. Tivoli Workload Scheduler for z/OS
supplied-variable and user-defined variable tables are supported.
v You can enable firewall support and SSL authentication in end-to-end
scheduling.
v You can specify a success condition for each job that determines whether a job is
considered successful or abended.
v You can specify or modify the deadline time for a job or a job stream.
v There are new log files for netman, batchman, mailman, the writer, and the
translator.
v Multiple domain managers can be connected to the controller. This allows
greater flexibility, scalability, and improved performance.
v You can make an application or an operation dependent on the existence of one
or more files before it can begin execution.
v You can activate and deactivate the submission of jobs scheduled in an
end-to-end environment.
v You can enable or disable the auditing trail of a plan.
v You can change the status of distributed agents and switch their domain
manager.
v You can refresh the content of the work directory.
v You can use the ISPF panels to produce an APAR tape that collects end-to-end
data.
v You can use the Job Migration Tool to migrate from tracker agents to distributed
agents.

Server Connectivity
v The server can use APPC and TCP/IP in simultaneous connections with the Job
Scheduling Console, PIF, ISPF panels, and distributed agents.
v When an application is moved to another system in a sysplex environment, for
example, for maintenance of the current system or for a failure, the application

x IBM Tivoli Workload Scheduler for z/OS Messages and Codes

can be reached under the same virtual IP address. Using a dynamic virtual IP
address makes the end-to-end configuration more flexible, because your
application is independent of the TCP/IP stack within the sysplex.

Preface xi
xii IBM Tivoli Workload Scheduler for z/OS 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 Tivoli Workload Scheduler for z/OS
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
IBM Tivoli Workload Scheduler for z/OS messages have the following formats:
where:
EQQFnnnC Text or EQQFFnnC Text or EQQnnnnC Text

EQQ Means that the message was issued by IBM Tivoli Workload Scheduler for
z/OS. The EQQ prefix is used for all IBM Tivoli Workload Scheduler for
z/OS 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:
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.
Text 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:
v 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 IBM Tivoli Workload Scheduler for z/OS
dialog messages that are presented in this area have mixed-case text.
v As one or more records in the IBM Tivoli Workload Scheduler for z/OS
message-log data set. The message log is defined by the EQQMLOG DD
statement. The message log is used by the IBM Tivoli Workload Scheduler for

© Copyright IBM Corp. 1991, 2003 1

 z/OS started task and by IBM Tivoli Workload Scheduler for z/OS’s own batch
jobs. Any message in the message log can also be displayed as a
write-to-operator message.
The format of a IBM Tivoli Workload Scheduler for z/OS message printed in the
message log data set is:
where:
mm/dd HH.MM.SS msgnum TEXT

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.

An example of messages in the IBM Tivoli Workload Scheduler for z/OS

message log follows:

.
.
.
02/21 16.31.11 EQQZ005I IBM Tivoli Workload Scheduler for z/OS SUBTASK
EVENT WRITER IS BEING STARTED
02/21 16.31.13 EQQZ005I IBM Tivoli Workload Scheduler for z/OS SUBTASK
VTAM I/O TASK IS BEING STARTED
02/21 16.31.14 EQQZ005I IBM Tivoli Workload Scheduler for z/OS SUBTASK
JOB SUBMIT TASK IS BEING STARTED
02/21 16.31.16 EQQZ005I IBM Tivoli Workload Scheduler for z/OS
SUBTASK DATA ROUTER TASK IS BEING STARTED
02/21 16.31.17 EQQZ013I NOW PROCESSING PARAMETER LIBRARY MEMBER EWOPTS
02/21 16.31.19 EQQZ015I INIT STATEMENT: EWTROPTS HOLDJOB(NO)
02/21 16.31.26 EQQZ015I INIT STATEMENT: STEPEVENTS(ALL)
02/21 16.31.28 EQQZ015I INIT STATEMENT: RETCODE(LAST)
02/21 16.31.29 EQQZ015I INIT STATEMENT: EWSEQNO(1)
02/21 16.31.30 EQQZ016I RETURN CODE FOR THIS STATEMENT IS: 0000
02/21 16.31.31 EQQZ014I MAXIMUM RETURN CODE FOR PARAMETER MEMBER EWOPTS IS: 000
02/21 16.31.32 EQQV001I NCF APPLICATION STARTED
02/21
. 16.31.33 EQQF001I 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.

2 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

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.

Chapter 1. Introduction 3
4 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 2. EQQATnn Messages
EQQAT00I THE APPC TRACKER TASK HAS EQQAT04E THE APPC TRACKER TASK
STARTED RECEIVED INVALID
IDENTIFICATION DATA FROM
Explanation: The APPC tracker task has started
DESTINATION: LU
successfully. Tivoli Workload Scheduler for z/OS starts
this task if the ROUTOPTS initialization statement Explanation: The initial data received from a partner
defines one or more APPC destinations. APPC program is not valid.
System action: IBM Tivoli Workload Scheduler for System action: The APPC tracker task frees all
z/OS normal processing continues. resources allocated to this APPC conversation. The
partner program sending incorrect data gets a failing
System programmer response: None.
return code from the APPC service routine.
System programmer response: Verify that the correct
EQQAT01I THE APPC TRACKER TASK HAS
partner program has been started on the remote
ENDED
destination and that the program is at a supported
Explanation: The APPC tracker task has been maintenance level. After making corrections, restart the
requested to stop and is ending normally. partner program.

System action: IBM Tivoli Workload Scheduler for

z/OS normal processing continues. EQQAT05I A CONVERSATION WITH AN APPC
TRACKER AT DESTINATION LU HAS
System programmer response: None. ENDED. SEND RECORDS WERE
TRANSMITTED, RCV RECORDS
EQQAT02E THE APPC TRACKER TASK HAS WERE RECEIVED
BEEN CONTACTED BY AN Explanation: A conversation with an APPC tracker is
UNKNOWN DESTINATION: LU ending normally.
Explanation: The APPC tracker task has recognized an System action: IBM Tivoli Workload Scheduler for
inbound attach request from a destination that is not z/OS normal processing continues.
defined in the ROUTOPTS initialization statement.
System programmer response: None.
System action: The APPC tracker task frees all
resources allocated to this APPC conversation. The
partner program that is attempting to start the EQQAT06E THE APPC TRACKER TASK
conversation gets a failing return code from the APPC RECEIVED UNRECOGNIZED DATA
service routine. FROM DESTINATION: LU
System programmer response: If the APPC tracker Explanation: Data received from a partner APPC
task should support the destination specified in this program is not valid.
message, update the ROUTOPTS initialization
System action: The APPC tracker task frees all
statement and restart the IBM Tivoli Workload
resources allocated to this APPC conversation. The
Scheduler for z/OS subsystem.
partner program sending incorrect data gets a failing
return code from the APPC service routine.
EQQAT03E A QUEUE ELEMENT ON THE APPC
System programmer response: Verify that the correct
TRACKER TASK QUEUE IS NOT
partner program has been started on the remote
RECOGNIZED: ELEM
destination and that the program is at a supported
Explanation: An invalid queue element has been maintenance level. After making corrections, restart the
found on the APPC tracker task’s work queue. partner program.

System action: The incorrect queue element is

returned to the APPC tracker task’s free queue without EQQAT07E NO CONVERSATION FOUND FOR
any further processing. OUTBOUND DATA ON THE APPC
TRACKER TASK QUEUE: ELEM
System programmer response: Save the IBM Tivoli
Workload Scheduler for z/OS message log data set Explanation: A queue element has been found on the
containing this message and contact Customer Support. APPC tracker task’s work queue which is not
addressed to any currently active APPC conversation.

© Copyright IBM Corp. 1991, 2003 5

System action: The queue element is returned to the
EQQAT10E SEND TO DESTINATION: LU FAILED
APPC tracker task’s free queue without any further
WITH RETCODE RC IMMEDIATELY
processing.
Explanation: The APPC tracker task received an
System programmer response: Save the IBM Tivoli
immediate nonzero return code from the APPC send
Workload Scheduler for z/OS message log data set
data service routine.
containing this message and contact Customer Support.
System action: The APPC tracker task terminates this
APPC conversation and frees all allocated resources.
EQQAT08E THE APPC TRACKER TASK CANNOT
START, TRACKER FEATURE IS NOT System programmer response: Verify that the partner
INSTALLED program on the remote destination is at a supported
maintenance level. After making corrections, restart the
Explanation: The APPC tracker task could not locate a
partner program.
required load module.
System action: The APPC tracker task is terminated.
EQQAT11E SEND TO DESTINATION: LU FAILED
System programmer response: If the APPC tracker WITH RETCODE RC
feature is not installed, the ROUTOPTS initialization ASYNCHRONOUSLY
statement should not specify the APPC keyword. If the
Explanation: The APPC tracker task received a
APPC tracker feature is installed, make sure that the
nonzero return code from the APPC send data service
IBM Tivoli Workload Scheduler for z/OS subsystem
routine.
can access corresponding load module libraries. After
making the appropriate corrections, restart the IBM System action: The APPC tracker task terminates this
Tivoli Workload Scheduler for z/OS subsystem. APPC conversation and frees all allocated resources.
System programmer response: Verify that the partner
EQQAT09E THE APPC TRACKER TASK program on the remote destination is at a supported
RECEIVED INVALID maintenance level. After making corrections, restart the
IDENTIFICATION DATA FROM partner program.
DESTINATION: LU. VALIDATION
RETURN CODE IS RC
EQQAT12E RECEIVE AND WAIT FROM
Explanation: The initial data received from a partner DESTINATION: LU FAILED WITH
APPC program is not valid. RETCODE RC IMMEDIATELY
System action: The APPC tracker task frees all Explanation: The APPC tracker task received an
resources allocated to this APPC conversation. The immediate nonzero return code from the APPC receive
partner program sending incorrect data gets a failing and wait service routine.
return code from the APPC service routine.
System action: The APPC tracker task terminates this
If the return code is 4, correct the GMT times involved APPC conversation and frees all allocated resources.
using the information in message EQQAT17W, and
System programmer response: Verify that the partner
then restart the partner program.
program on the remote destination is at a supported
Return Code maintenance level. After making corrections, restart the
Explanation partner program.
4 The difference between the host system GMT
value and the tracker system GMT value is EQQAT13E RECEIVE AND WAIT FROM
greater than 60 minutes. This message is DESTINATION: LU FAILED WITH
followed by message EQQAT17W, which RETCODE RC ASYNCHRONOUSLY
shows the different GMT values.
Explanation: The APPC tracker task received a
8 The identification data is invalid for other nonzero return code from the APPC receive and wait
causes to be investigated. service routine.
System programmer response: Verify that the correct System action: The APPC tracker task terminates this
partner program has been started on the remote APPC conversation and frees all allocated resources.
destination and that the program is at a supported
System programmer response: Verify that the partner
maintenance level. If the return code is 4, correct the
program on the remote destination is at a supported
GMT values involved, using the information in
maintenance level. After making corrections, restart the
message EQQAT17W. After making corrections, restart
partner program.
the partner program.

6 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 displayed to determine which system has an incorrect
EQQAT14E IDLE CONVERSATION DELAY ERROR
definition, reset the GMT value where necessary. After
FOR DESTINATION: LU
making corrections, restart the partner program.
Explanation: The APPC tracker task received send
permission from a remote partner program without any
EQQAT21E WRONG NUMBER OF PERIODS IN
data and without the minimum delay required for an
THE ADDR VALUE, VALUE
idle conversation.
Explanation: The ADDR keyword of the APPCROUT
System action: The APPC tracker task terminates this
initialization statement must specify a value containing
APPC conversation and frees all allocated resources.
one period.
System programmer response: Verify that the partner
System action: Processing of the current APPCROUT
program on the remote destination is at a supported
statement terminates with a nonzero return code. This
maintenance level. After making corrections, restart the
causes IBM Tivoli Workload Scheduler for z/OS
partner program.
initialization to fail.
System programmer response: Either remove or
EQQAT15E PREPARE TO RECEIVE FROM
correct the APPCROUT statement and restart the IBM
DESTINATION: LU FAILED WITH
Tivoli Workload Scheduler for z/OS subsystem.
RETCODE RC IMMEDIATELY
Explanation: The APPC tracker task received an
EQQAT22E THE PERIOD IN THE ADDR VALUE,
immediate nonzero return code from the APPC prepare
VALUE, IS INCORRECTLY PLACED
to receive service routine.
Explanation: The ADDR keyword of the APPCROUT
System action: The APPC tracker task terminates this
initialization statement must specify a value containing
APPC conversation and frees all allocated resources.
one period, and that period cannot be placed more than
System programmer response: Verify that the partner eight characters after the beginning of the value or
program on the remote destination is at a supported more than eight characters before the end of the value.
maintenance level. After making corrections, restart the
System action: Processing of the current APPCROUT
partner program.
statement terminates with a nonzero return code. This
causes IBM Tivoli Workload Scheduler for z/OS
EQQAT16E PREPARE TO RECEIVE FROM initialization to fail.
DESTINATION: LU FAILED WITH
System programmer response: Either remove or
RETCODE RC ASYNCHRONOUSLY
correct the APPCROUT statement and restart the IBM
Explanation: The APPC tracker task received a Tivoli Workload Scheduler for z/OS subsystem.
nonzero return code from the APPC prepare to receive
service routine.
EQQAT23E THE VALUE OF THE ADDR
System action: The APPC tracker task terminates this KEYWORD IS MISSING OR TOO
APPC conversation and frees all allocated resources. SHORT
System programmer response: Verify that the partner Explanation: The ADDR keyword of the APPCROUT
program on the remote destination is at a supported initialization statement must specify a value that is not
maintenance level. After making corrections, restart the less than three characters long.
partner program.
System action: Processing of the current APPCROUT
statement terminates with a nonzero return code. This
EQQAT17W THE APPC TRACKER TASK causes IBM Tivoli Workload Scheduler for z/OS
DETECTED AN INVALID initialization to fail.
DIFFERENCE BETWEEN THE
System programmer response: Either remove or
CONTROLLER GMT TIME HOSTGMT
correct the APPCROUT statement and restart the IBM
AND THE TRACKER GMT TIME
Tivoli Workload Scheduler for z/OS subsystem.
TRKGMT
Explanation: This message follows EQQAT09E. It
EQQAT24E THE ADDR KEYWORD IS MISSING
shows the host system GMT value and the tracker
system GMT value. The host system GMT value may Explanation: The current APPCROUT initialization
have been adjusted by the value provided in the statement does not contain an ADDR keyword.
GMTOFFSET parameter of the OPCOPTS statement.
System action: Processing of the current APPCROUT
System action: None. statement terminates with a nonzero return code. This
causes IBM Tivoli Workload Scheduler for z/OS
System programmer response: Use the GMT values
initialization to fail.

Chapter 2. EQQATnn Messages 7

System programmer response: Either remove or names cannot contain periods.
correct the APPCROUT statement and restart the IBM
System action: Processing of the APPC keyword
Tivoli Workload Scheduler for z/OS subsystem.
continues. Message EQQAT34E is issued when all
destinations have been processed.
EQQAT25E THE WORKSTATIONS KEYWORD IS
System programmer response: Either remove or
MISSING
correct the invalid destination and restart the IBM
Explanation: The current APPCROUT initialization Tivoli Workload Scheduler for z/OS subsystem.
statement does not contain a WORKSTATIONS
keyword.
EQQAT32E THE PERIOD IN THE APPC
System action: Processing of the current APPCROUT KEYWORD VALUE, VAL2, IS
statement terminates with a nonzero return code. This INCORRECTLY PLACED
causes IBM Tivoli Workload Scheduler for z/OS
Explanation: A network address specified as a value
initialization to fail.
of the APPC keyword of the ROUTOPTS statement is
System programmer response: Either remove or incorrect. The network address is required and must be
correct the APPCROUT statement and restart the IBM specified as netid.netlu where the netid and netlu
Tivoli Workload Scheduler for z/OS subsystem. names cannot be greater than eight characters.
System action: Processing of the APPC keyword
EQQAT26E WORKSTATION WSN HAS BEEN continues. Message EQQAT34E is issued when all
SPECIFIED MORE THAN ONCE IN A destinations have been processed.
WORKSTATIONS KEYWORD. THIS IS
System programmer response: Either remove or
NOT SUPPORTED
correct the invalid destination and restart the IBM
Explanation: The WORKSTATIONS keyword in Tivoli Workload Scheduler for z/OS subsystem.
current APPCROUT initialization statement contains a
workstation name that has already been specified in a
EQQAT33E APPC KEYWORD VALUE, VAL2, IS
WORKSTATIONS keyword. This is a duplicate
MISSING OR TOO SHORT
definition that is not supported.
Explanation: A network address specified as a value
System action: Processing of the current APPCROUT
of the APPC keyword of the ROUTOPTS statement is
statement terminates with a nonzero return code. This
incorrect. The network address is required and must be
causes IBM Tivoli Workload Scheduler for z/OS
specified as netid.netlu where both netid and netlu
initialization to fail.
are required.
System programmer response: Either remove or
System action: Processing of the APPC keyword
correct the APPCROUT statement and restart the IBM
continues. Message EQQAT34E is issued when all
Tivoli Workload Scheduler for z/OS subsystem.
destinations have been processed.
System programmer response: Either remove or
EQQAT30E APPC KEYWORD VALUE, VAL1, IS
correct the invalid destination and restart the IBM
TOO LONG (OR MISSING)
Tivoli Workload Scheduler for z/OS subsystem.
Explanation: A workstation destination name specified
as a value of the APPC keyword of the ROUTOPTS
EQQAT34E AT LEAST ONE APPC DESTINATION
statement is incorrect. The destination name is required
IS INCORRECTLY DEFINED
and must be not greater than eight characters.
Explanation: The APPC keyword of the ROUTOPTS
System action: Processing of the APPC keyword
statement contains one or more incorrectly defined
continues. Message EQQAT34E is issued when all
APPC destinations.
destinations have been processed.
System action: Processing of the current ROUTOPTS
System programmer response: Either remove or
statement terminates with a nonzero return code. This
correct the invalid destination and restart the IBM
causes IBM Tivoli Workload Scheduler for z/OS
Tivoli Workload Scheduler for z/OS subsystem.
initialization to fail.
System programmer response: Review earlier error
EQQAT31E APPC KEYWORD VALUE, VAL2, MUST
messages to determine the incorrectly defined
CONTAIN EXACTLY ONE PERIOD
destination. Either remove or correct the invalid
Explanation: A network address specified as a value destination and restart the IBM Tivoli Workload
of the APPC keyword of the ROUTOPTS statement is Scheduler for z/OS subsystem.
incorrect. The network address is required and must be
specified as netid.netlu where the netid and netlu

8 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

Chapter 3. EQQAnnn Messages
application entries was generated.
EQQA000E YOU ARE NOT AUTHORIZED TO
ACCESS THE AD DATABASE System action: The request is rejected.
Explanation: You have attempted to access the User response: Return to the application selection
application description (AD) database, but you are not criteria panel and press ENTER to generate a fresh list
authorized to access it. Or, you do not have access of applications.
authority to a minimum of one of the following IBM
Tivoli Workload Scheduler for z/OS resources that are
used together with the AD database: the calendar EQQA006I NO RUNCYCLES FOUND FOR THIS
database, the workstation description database, or in APPLICATION
some cases, the long-term plan data set. Explanation: You have attempted to display the run
System action: The request is rejected. cycles of an application for which no run cycles have
been specified.
User response: If you require access, contact your
security administrator. System action: The request is rejected.
User response: None.
EQQA002E THIS VERSION OF THE
APPLICATION ALREADY EXISTS EQQA009I NO PREDECESSORS FOUND FOR
Explanation: The application already exists with the THIS OPERATION
valid-from date that you specified. Explanation: You have attempted to display the
System action: The system waits for you to respond. predecessors of an operation for which no predecessors
have been specified.
User response: Specify another valid-from date.
System action: The request is rejected.

EQQA003E SELECTED PREDECESSOR IS NOT User response: None.

EXTERNAL
Explanation: The predecessor you selected is not EQQA010E INVALID PARAMETER INPUT TO
external. When defining an external dependency, you MODULE MOD
must specify the application ID of the external Explanation: This message indicates a programming
predecessor before selecting to describe it. error.
System action: The system waits for you to respond. System action: The system waits for you to respond.
User response: Specify the application ID of the User response: Contact your system programmer.
external predecessor.
System programmer response: Contact your system
administrator.
EQQA004E NO MATCHING APPLICATION
DESCRIPTION(S) FOUND
EQQA011I THE APPLICATION IS CREATED
Explanation: No application description matched the
generic or nongeneric search criteria you specified to Explanation: The application has been created and
generate a list of applications. saved in the application description database.

System action: The system waits for you to respond. System action: None.

User response: Retry using new selection criteria. User response: None.

EQQA005E NO MATCHING APPLICATION EQQA012I THE SELECTED APPLICATION IS

DESCRIPTION FOUND MODIFIED

Explanation: You selected an application that does not Explanation: The selected application has been
have a matching application description. In a list of modified and saved in the application description
applications, in either the browse or list function, the database.
application you selected was not found. The application System action: None.
may have been deleted or modified after the list of

© Copyright IBM Corp. 1991, 2003 9

User response: None.
EQQA021I NO SPECIAL RESOURCES FOUND
FOR THIS OPERATION
EQQA013I THE SELECTED APPLICATION IS
Explanation: You have attempted to display the
COPIED
special resources of an operation for which no special
Explanation: The selected application has been copied resources have been defined.
and the copy has been saved in the application
System action: None.
description database.
User response: None.
System action: None.
User response: None.
EQQA022E THE APPLICATION STATUS
SPECIFIED IS NOT VALID
EQQA014I THE SELECTED APPLICATION IS
Explanation: Data entry error.
DELETED
Valid application statuses you can specify as selection
Explanation: The selected application has been deleted
criteria are: A for active, P for pending, or blank for
from the application description database.
both active and pending.
System action: None.
User response: None. EQQA023E PRIORITY MUST BE A NUMBER
FROM 1 - 9
EQQA015E THE NUMBER OF INTERNAL Explanation: Data entry error.
PREDECESSORS IS TOO LARGE
Explanation: You specified too many internal EQQA024E STATUS MUST BE OCHCACT OR
predecessors. OCHCPEND

System action: The system waits for you to respond. Explanation: Data entry error; see “Data Entry Errors”
on page 2.
User response: Delete one or more internal
predecessors.
EQQA025E INPUT DATA IN FIELD IS REQUIRED
EQQA016E THE NUMBER OF EXTERNAL Explanation: Data entry error; see “Data Entry Errors”
PREDECESSORS IS TOO LARGE on page 2.
Explanation: You specified too many external
predecessors. EQQA101E THE VARIABLE TABLE NAME
CONTAINS AN INVALID
System action: The system waits for you to respond. CHARACTER
User response: Delete one or more external Explanation: Data entry error; see “Data Entry Errors”
predecessors. on page 2.
The name of a variable table contains 1 to 16
EQQA017E THE NUMBER OF SPECIAL alphanumeric characters, where the first character is
RESOURCES IS TOO LARGE alphabetic.
Explanation: You specified too many special resources.
System action: The system waits for you to respond. EQQA102E AN APPLICATION WITH THIS ID
ALREADY EXISTS
User response: Delete one or more special resources.
Explanation: You have attempted to create an
application, but the application ID that you specified
EQQA018E OP OP HAS AN EXTERNAL PRED WS already exists in the application description database.
EWS, WHICH IS NOT FOUND
System action: The system waits for you to respond.
Explanation: Operation OP has an external
predecessor workstation (EWS) that does not exist in User response: Enter a unique application ID. If you
the workstation description database. want to create versions of an already existing
application, you should use the copy function.
System action: The system waits for you to respond.
User response: Enter correct data.

10 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 This does not prevent you from updating only one of
EQQA103E THE APPLICATION IS BEING
the items.
UPDATED BY USER USR TRY LATER
System action: The system waits for you to continue.
Explanation: Another user is currently updating the
application you want to update. User response: Select all three items.
System action: The system waits for you to respond.
EQQA110E JOBNAME REQUIRED FOR JOB
User response: Try to update the application later.
SETUP, PRINT, OR COMPUTER WS
Explanation: Data entry error; see “Data Entry Errors”
EQQA104E THE PERIOD NAME DOES NOT
on page 2.
EXIST IN THE CALENDAR
A job name is required for an operation at a job setup,
Explanation: The period name that you specified is
print, or computer workstation.
not defined in the calendar database.
System action: The system waits for you to respond.
EQQA111E YOU HAVE ENTERED AN INVALID
User response: Enter an existing period name, or use VALUE IN THE ONE OF THE WLM
the Calendar dialog to define the period name. FIELDS
Explanation: In the WLM CRITICAL field, the only
EQQA105E YOU ARE NOT AUTHORIZED TO valid values are Y (Yes) and N (No). In the WLM
READ THE JCL VARIABLE TABLE POLICY field, the only valid values are:
DATA BASE
L Long Duration. The job is assisted if it runs
Explanation: You have attempted to refer to a JCL beyond its estimated duration.
variable table. To do this, you need read authority to
D Deadline. The job is assisted if it has not
the JCL variable table database.
finished when its deadline time is reached.
System action: The system waits for you to respond.
S Latest Start Time. The job is assisted if it is
User response: If you need to refer to JCL variable submitted after its latest start time.
table names, contact your security administrator.
C Conditional. An algorithm calculates whether
to apply the Deadline policy or the Latest Start
EQQA106E DEADLINE PRECEDES INPUT Time policy.
ARRIVAL TIME
’’ The scheduler WLM will eventually use the
Explanation: Data entry error; see “Data Entry Errors” policy specified in OPCOPTS.
on page 2.
User response: Enter valid values in the WLM
The deadline must be later than the input arrival time. CRITICAL and POLICY fields.

EQQA107E WORK STATION DOES NOT EXIST IN EQQA116E DURATION TIME IS NOT SPECIFIED
WS DESCRIPTION DATA BASE
Explanation: Data entry error; see “Data Entry Errors”
Explanation: The workstation name that you specified on page 2.
is not defined in the workstation description database.
System action: The system waits for you to respond. EQQA117E 24.00 IS NOT ALLOWED AS INPUT
ARRIVAL TIME
User response: Enter an existing workstation name or
use the Work Station Description dialog to define the Explanation: Data entry error; see “Data Entry Errors”
workstation name. on page 2.
Valid input arrival times are 00.00 through 23.59.
EQQA108W WHEN UPDATING WS NAME, OPR,
EXT AND INT ITEMS MUST ALL BE
EQQA118E 00.00 IS NOT ALLOWED AS
SELECTED
DEADLINE TIME
Explanation: To obtain a correct result, you must
Explanation: Data entry error; see “Data Entry Errors”
select all of:
on page 2.
OPR Workstation name
INT Predecessor ws name Valid deadline times are 00.01 through 24.00.
EXT Predecessor ws name

Chapter 3. EQQAnnn Messages 11

 application. This does not prevent you from saving the
EQQA119W SPECIFIED OPERATION DEADLINE
application description as it is.
EARLIER THAN APPLICATION INPUT
ARRIVAL System action: The input arrival time for the
operation is accepted and the system waits for you to
Explanation: Th operation deadline that you specified
respond.
is earlier than the application input arrival time for the
application. This does not prevent you from saving the User response: Enter END to save the application
application description as it is. description or make the input arrival times consistent.
System action: The operation deadline is accepted and
the system waits for you to respond. EQQA124I SPECIFIED OP DEADLINE LATER
THAN APPLICATION DEADLINE
User response: Enter END to save the application
description or make the deadline and the input arrival Explanation: The operation deadline time that you
time consistent. specified is later than the deadline time for the
application. This does not prevent you from saving the
application description as it is.
EQQA120I SPECIFIED OPERATION INPUT
ARRIVAL LATER THAN System action: The deadline time for the operation is
APPLICATION DEADLINE accepted. The system waits for you to respond.
Explanation: The operation input arrival time that you User response: Enter END to save the application
specified is later than the deadline time for the description or make the deadline times consistent.
application. This does not prevent you from saving the
application description as it is.
EQQA125I NO APPLICATION INPUT ARRIVAL
System action: The input arrival time for the TIME SPECIFIED YET
operation is accepted and the system waits for you to
respond. Explanation: No application input arrival time is
specified for this application. This does not prevent you
User response: Enter END to save the application from saving the application description as it is.
description or make the operation input arrival and the
application deadline consistent. System action: The times specified for the operation
are accepted. The system waits for you to respond.

EQQA121E SPECIFIED OPERATION DEADLINE User response: Enter END to save the application
EARLIER THAN OP INPUT ARRIVAL description, or make the deadline times consistent.

Explanation: Data entry error; see “Data Entry Errors”

on page 2. EQQA126E SPECIFY AT LEAST ONE RUNDAY

The deadline time must be later than the input arrival Explanation: Data entry error; see “Data Entry Errors”
time. on page 2.

EQQA122I SPECIFIED APPLICATION INPUT EQQA127E OUT-OF-EFFECT-FROM DATE

ARRIVAL LATER THAN AN OP PRECEDES IN-EFFECT-FROM DATE
INPUT ARRIVAL Explanation: Data entry error; see “Data Entry Errors”
Explanation: The application input arrival time that on page 2.
you specified is later than an operation input arrival The out-of-effect-from date for a run cycle must be later
time defined in the OPER table. This does not prevent than the in-effect-from date.
you from saving the application description as it is.
System action: The input arrival time for the EQQA132I IA 2400 IS NOT SUPPORTED,
application is accepted and the system waits for you to CHANGED TO 0000 THE DAY AFTER
respond.
Explanation: The occurrence input arrival time
User response: Enter END to save the application specified is out of the prearranged range. Valid input
description or make the input arrival times consistent. arrival times are 00.00 through 23.59. The inout has
therefore been converted to 00.00 the day after.
EQQA123I SPECIFIED OP INPUT ARRIVAL System action: None
EARLIER THAN APPLICATION INPUT
ARRIVAL User response: None

Explanation: The operation input arrival time that you

specified is earlier than the input arrival time for the

12 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQA133I DEADLINE 0000 IS NOT EQQA201E THE VARIABLE TABLE IS NOT
SUPPORTED,CHANGED TO 2400 THE DEFINED TO OPC
DAY BEFORE
Explanation: Data entry error; see “Data Entry Errors”
Explanation: The occurrence deadline specified is out on page 2.
of the prearranged range. Valid deadline times are
You have tried to define a variable table ID that does
00.01 through 24.00. The deadline has therefore been
not exist in IBM Tivoli Workload Scheduler for z/OS’s
converted to 24.00 the day before.
database.
System action: None
User response: None EQQA202E THE RUN CYCLE TYPE IS INVALID,
ENTER EITHER N, X, R OR E
EQQA134E SUPPRESS IF LATE = YES ALLOWED Explanation: Valid run cycle types are:
ONLY WHEN TIME DEPENDENT = N Normal offset-based run cycles.
YES X Negative offset-based run cycles.
R Regular rule-based run cycles.
Explanation: Data entry error; see “Data Entry Errors”
E Exception rule-based run cycles.
on page 2.
System action: The request is rejected.
The SUPPRESS IF LATE option can be YES only when
the TIME DEPENDENT option is specified as YES. User response: Change the run cycle type to one of
the supported values.
EQQA135E THE SMOOTHING FACTOR MUST BE
A NUMBER 0 - 999 EQQA203E THE FREE DAY RULE SPECIFICATION
IS INVALID
Explanation: Data entry error; see “Data Entry Errors”
on page 2. Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA136E THE FEEDBACK LIMIT MUST BE A A valid free day rule specification is any of the
NUMBER 100 - 999 following:
E Free days excluded.
Explanation: Data entry error; see “Data Entry Errors”
1 Run on the closest workday before the free
on page 2.
day.
2 Run on the closest workday after the free day.
EQQA137E DEADLINE WTO IS NOT DEFINED 3 Run on the free day.
OR INVALID 4 Do not run at all.

Explanation: Data entry error; see “Data Entry Errors”

on page 2. EQQA205E THE RUN CYCLE TYPE MUST BE
SPECIFIED
Valid deadline WTO options are Y for Yes, and N for
No. Explanation: Valid run cycle types are:
N Normal offset-based run cycles.
X Negative offset-based run cycles.
EQQA138W OPERATION IA OPIA LESS THAN R Regular rule-based run cycles.
OCCURRENCE IA OCCIA E Exception rule-based run cycles.
Explanation: The operation arrival date is earlier than System action: The request is rejected.
the occurrence. This is accepted, but might not be what
you intend. User response: Change the run cycle type to one of
the supported values.
System action: None.
User response: None. EQQA206E THE FREE DAY RULE MUST BE
SPECIFIED
EQQA200E OPERATION NUMBER MUST BE 1 - Explanation: Data entry error; see “Data Entry Errors”
255 on page 2.
Explanation: Data entry error; see “Data Entry Errors” A valid free day rule specification is any of the
on page 2. following:
E Free days excluded.
1 Run on the closest workday before the free
day.

Chapter 3. EQQAnnn Messages 13

2 Run on the closest workday after the free day.
EQQA214E THE JOB OPTION CHARACTER
3 Run on the free day.
SPECIFIED IS INVALID
4 Do not run at all.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA207E AN IN-EFFECT-FROM DATE MUST BE
SPECIFIED Valid job option characters are Y for yes and N for no.
Explanation: Data entry error; see “Data Entry Errors”
on page 2. EQQA215E THE NUMBER OF PARALLEL
SERVERS MUST BE 1 - 99
EQQA208E AN OUT-OF-EFFECT-FROM DATE Explanation: Data entry error; see “Data Entry Errors”
MUST BE SPECIFIED on page 2.
Explanation: Data entry error; see “Data Entry Errors”
on page 2. EQQA216E THE INPUT ARRIVAL DAY MUST BE
SPECIFIED
EQQA209E THE RUN DAY OFFSET MUST BE A Explanation: Data entry error; see “Data Entry Errors”
NUMBER FROM -999 TO -1 OR 1 TO on page 2.
999
Explanation: Data entry error; see “Data Entry Errors” EQQA217E THE INPUT ARRIVAL DAY MUST BE
on page 2. A NUMBER 0 - 99
Explanation: Data entry error; see “Data Entry Errors”
EQQA210E THE PRINT OPTION MUST BE on page 2.
SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” EQQA218E THE INPUT ARRIVAL TIME MUST BE
on page 2. SPECIFIED
Explanation: Data entry error; see “Data Entry Errors”
EQQA211E THE PRINT OPTION CHARACTER IS on page 2.
INVALID
Explanation: Data entry error; see “Data Entry Errors” EQQA219E THE NUMBER OF PARALLEL
on page 2. SERVERS MUST BE 1 FOR CPU
OPERATIONS
Valid print option characters are A for always and C for
conditionally. Explanation: Operations on a computer workstation
can use only one parallel server.
EQQA212E WHEN TIME DEPENDENT = YES, System action: The panel is redisplayed and the
SUPPRESS IF LATE MUST BE dialog waits for you to change the number of parallel
SPECIFIED servers.
Explanation: Data entry error; see “Data Entry Errors” User response: Change the number of parallel servers
on page 2. to one.
The SUPPRESS IF LATE option must be specified
when the TIME DEPENDENT option is specified as EQQA220E THE DEADLINE DAY MUST BE
YES. SPECIFIED
Explanation: Data entry error; see “Data Entry Errors”
EQQA213E THE WS RESOURCE AMOUNT on page 2.
SPECIFIED MUST BE A NUMBER 0 -
99
EQQA221E THE DEADLINE DAY OFFSET
Explanation: Data entry error; see “Data Entry Errors” SPECIFIED MUST BE A NUMBER 0 -
on page 2. 99
Explanation: Data entry error; see “Data Entry Errors”
on page 2.

14 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQA222E THE DEADLINE TIME MUST BE EQQA231E A PERIOD NAME MUST BE
SPECIFIED SPECIFIED
Explanation: Data entry error; see “Data Entry Errors” Explanation: Data entry error; see “Data Entry Errors”
on page 2. on page 2.

EQQA223E THE JCL EDIT/BROWSE FUNCTION EQQA232E UP TO 24 (12 POSITIVE AND 12

NEEDS A JOBNAME NEGATIVE) RUNDAY OFFSETS ARE
ALLOWED
Explanation: The JCL edit/browse option can be
called only if a jobname has been specified. Explanation: Data entry error; see “Data Entry Errors”
on page 2.
System action: The panel is redisplayed with this
error message.
EQQA233E THE SPECIFIED HIGHEST RETURN
User response: Specify a jobname.
CODE MUST BE A NUMBER 0 - 4095
Explanation: Data entry error; see “Data Entry Errors”
EQQA226E THE OPERATION NUMBER MUST BE
on page 2.
SPECIFIED
Explanation: Data entry error; see “Data Entry Errors”
EQQA234E THE APPLICATION ID IS NOT
on page 2.
SPECIFIED
Explanation: Data entry error; see “Data Entry Errors”
EQQA228E THE SPECIFIED SPECIAL RESOURCE
on page 2.
HELD OPTION IS INVALID
Explanation: Data entry error; see “Data Entry Errors”
EQQA235E THE FIRST CHARACTER IN
on page 2.
APPLICATION ID MUST BE
Valid special resource held options are S for shared and ALPHABETIC
X for exclusive.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA229W OFFSET WRKOFF IS GREATER THAN
PERIOD INTERVAL WRKINT
EQQA236E THERE IS AN INVALID CHARACTER
Explanation: The number that you specified for a IN THE APPLICATION ID
positive or negative run day offset is greater than the
Explanation: Data entry error; see “Data Entry Errors”
period interval value. If the period is type A, no
on page 2.
occurrences are created in the long term plan (LTP) for
this offset. If the period type is W, the message is An application ID can be made up of the following
issued as a warning but occurrences can still be created valid characters: A through Z, 0 through 9, and national
in the LTP. characters (that is, #, $, and @).
System action: The system waits for you to respond.
EQQA237E ENTER THE OWNER ID
User response: Check if the offset value provides the
desired run dates. Correct the value if required. If LTP Explanation: Data entry error; see “Data Entry Errors”
occurrences should be created, and the period type is on page 2.
A, you must change either the period interval value or
the run cycle offset value. Press the END key to save
EQQA238E THE PRIORITY MUST BE A NUMBER
the offset values.
FROM 1 TO 9
Explanation: Data entry error; see “Data Entry Errors”
EQQA230E THE VALID RESPONSE IS Y OR N
on page 2.
FOLLOWED BY ENTER KEY
Explanation: Data entry error; see “Data Entry Errors”
EQQA239E ENTER THE STATUS, A OR P
on page 2.
Explanation: Data entry error; see “Data Entry Errors”
Y deletes the application and N cancels the deletion of
on page 2.
the application.
A stands for active and P for pending.

Chapter 3. EQQAnnn Messages 15

 User response: Use the row command D to delete the
EQQA240E SPECIFY A VALID-FROM DATE
duplicate run day offsets or change the duplicates.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA246E SPECIFY A WORK STATION NAME
Explanation: Data entry error; see “Data Entry Errors”
EQQA241E THE MAXIMUM 4 ACTIVE VERSIONS
on page 2.
ALREADY EXIST
Explanation: You have attempted to enter an active
EQQA247E THE OPERATION TABLE CONTAINS
version of an application description but the maximum
DUPLICATE OPERATION NUMBERS
four active versions of the application description
already exist in the application description database. Explanation: The list of operations cannot contain
duplicate operation numbers.
System action: The system waits for you to respond.
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 User response: Use the row command D to delete the
active versions. duplicate operation numbers or change the duplicates.

EQQA242E THE MAXIMUM 4 PENDING EQQA248E THE PREDECESSOR TABLE

VERSIONS ALREADY EXIST CONTAINS DUPLICATE
PREDECESSORS
Explanation: You have attempted to enter a pending
version of an application description but the maximum Explanation: The list of predecessors cannot contain
four pending versions of the application description duplicate predecessors.
already exist in the application description database.
System action: The system waits for you to respond.
System action: The system waits for you to respond.
User response: Use the row command D to delete the
User response: Reenter with a new application ID, duplicate predecessors or change the duplicates.
valid-from data, or status; or delete one of the four
pending versions.
EQQA249E THE SPECIAL RESOURCE TABLE
CONTAINS DUPLICATE RESOURCES
EQQA243E A PENDING VERSION CANNOT BE
COPIED Explanation: The list of special resources cannot
contain duplicate resources.
Explanation: You have attempted to copy a pending
version of the application description but only an active System action: The system waits for you to respond.
version can be copied. User response: Use the row command D to delete the
System action: The request is rejected and the system duplicate resources or change the duplicates.
waits for you to respond.
User response: Select an active version to copy. EQQA250I AD DOES NOT EXIST IN DATA BASE
Explanation: The specified external predecessor
EQQA244E APPLICATION ID, STATUS, OR application does not exist in the application description
VALID-FROM MUST BE CHANGED database. This does not prevent you from saving the
application as it is.
Explanation: In the copy function, one of the three
key fields (application ID, status, or valid-from key System action: The system waits for you to respond.
fields) must be changed to create a new version of an User response: Either enter END to save the external
existing application description, or a new application predecessor application or change the external
description. predecessor application.
System action: The system waits for you to respond.
User response: Change one of the three key fields. EQQA251E AD DOES NOT EXIST IN DATA BASE,
ENTER WS NAME

EQQA245E THE RUN DAY OFFSET TABLE Explanation: The specified external predecessor
CONTAINS DUPLICATES application does not exist in the application description
database, so the predecessor workstation name cannot
Explanation: The list of run days cannot contain be picked up. Therefore, you must specify the
duplicate offsets. predecessor workstation name.
System action: The system waits for you to respond. System action: The system waits for you to respond.

16 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

User response: Enter the workstation name of the User response: Enter a valid CPU predecessor job
external predecessor. name.

EQQA252I PRED OP DOES NOT EXIST IN EQQA257E THIS VERSIONS VALID-FROM DATE
PREDECESSOR APPLICATION CAN NOT PRECEDE MSGVALF
Explanation: The specified external predecessor Explanation: The application valid-from date for a
operation does not exist in the external predecessor previously defined application description version has
application. This does not prevent you from saving the been modified. The valid-from date now falls within
application as it is. the validity period of another version of this
application description.
System action: The system waits for you to respond.
System action: The system waits for you to respond.
User response: Either enter END to save the external
predecessor operation or change the external User response: Change the valid-from date so that it
predecessor operation. 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 that you specified,
EQQA253E PRED OP DOES NOT EXIST IN
you can copy a version of the application description
PREDECESSOR APPLICATION, ENTER
and specify the required valid-from date.
WS NAME
Explanation: The specified external predecessor
EQQA258I AD HAS PENDING STATUS
operation does not exist in the external predecessor
application, so the predecessor workstation name Explanation: The specified external predecessor
cannot be picked up. Therefore, you must specify the application has pending status. This does not prevent
predecessor workstation name. you from saving the application as it is.
System action: The system waits for you to respond. System action: The system waits for you to respond.
User response: Enter the predecessor workstation User response: Enter END to save the external
name. predecessor application as it is, or change it.

EQQA254E PRINT OPERATION OP MAY HAVE EQQA260E SAME DATE SPECIFIED FOR
ONLY ONE CPU PREDECESSOR IN-EFFECT-FROM AND
OUT-OF-EFFECT-FROM
Explanation: The print operation number (OP) can
have only one CPU internal predecessor. Explanation: Data entry error; see “Data Entry Errors”
on page 2.
System action: The system waits for you to respond.
The out-of-effect-from date must be later than the
User response: Delete all except one of the internal
in-effect-from date.
predecessors.

EQQA261E NO MORE THAN 12 ITEMS CAN BE

EQQA255E JOB SETUP OP OP MUST HAVE THE
SPECIFIED
SAME JOBNAME AS A CPU
SUCCESSOR Explanation: The print function can handle up to 12
print items at a time.
Explanation: The job setup operation number (OP)
must have the same job name as any of its CPU System action: The system waits for you to respond.
successors.
User response: Delete print items so that the total
System action: The system waits for you to respond. does not exceed 12.
User response: Enter a valid CPU successor job name.
EQQA262E NO MORE THAN 5 ITEMS CAN BE
SELECTED
EQQA256E PRINT OP OP MUST HAVE THE
SAME JOBNAME AS THE CPU Explanation: No more than five sort items can be
PREDECESSOR selected to be part of the cross reference list.
Explanation: The print operation number (OP) must System action: The system waits for you to respond.
have the same job name as its CPU predecessor.
User response: Delete sort items so that the total is
System action: The system waits for you to respond. not greater than five.

Chapter 3. EQQAnnn Messages 17

EQQA263E THE SORT ORDER SPECIFIED IS NOT EQQA273E THERE IS AN INVALID CHARACTER
A NUMBER 1 - 5 IN GROUP ID
Explanation: Data entry error; see “Data Entry Errors” Explanation: Data entry error; see “Data Entry Errors”
on page 2. on page 2.
A group ID can be made up of the following valid
EQQA264E THE SPECIFIED SORT ORDER characters: A through Z, 0 through 9, and national
CONTAINS DUPLICATE DIGITS characters (that is, #, $, and @).
Explanation: Data entry error; see “Data Entry Errors”
on page 2. EQQA274E THE FIRST CHARACTER IN
JOBNAME MUST BE ALPHABETIC
EQQA265E THE SPECIFIED SORT ORDER Explanation: Data entry error; see “Data Entry Errors”
SEQUENCE IS INVALID on page 2.
Explanation: Data entry error; see “Data Entry Errors”
on page 2. EQQA275E THE WS RESOURCE AMOUNT MUST
BE SPECIFIED
The digits representing the sort order must be
continuous and start with the digit 1. Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA266E YOU ARE NOT AUTHORIZED TO
READ THE OI DATA BASE EQQA276E THE NUMBER OF PARALLEL
SERVERS MUST BE SPECIFIED
Explanation: You have attempted to read the operator
instruction (OI) database, but you are not authorized to Explanation: Data entry error; see “Data Entry Errors”
read it. on page 2.
System action: The system waits for you to respond.
EQQA277E THE FILTER NUMBER FNR IS NOT
User response: If you require access to the OI
SUPPORTED
database, contact your security administrator
Explanation: This message indicates a programming
error.
EQQA267E YOU ARE NOT AUTHORIZED TO
UPDATE THE OI DATA BASE System action: The system waits for you to respond.
Explanation: You have attempted to update the User response: Contact your system programmer.
operator instruction (OI) database, but you are not
System programmer response: Contact your system
authorized to update it.
administrator.
System action: The system waits for you to respond.
User response: If you require update authority to the EQQA278E THE VERIFICATION NUMBER VNR IS
OI database, contact your security administrator NOT SUPPORTED
Explanation: This message indicates a programming
EQQA271E THERE IS AN INVALID CHARACTER error.
IN JOBNAME
System action: The system waits for you to respond.
Explanation: Data entry error; see “Data Entry Errors”
User response: Contact your system programmer.
on page 2.
System programmer response: Contact your system
A job name can be made up of the following valid
administrator.
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 EQQA279E THE TABLE OF UPDATES CONTAINS
be alphabetic, numeric, and national characters. DUPLICATE UPDATES
Explanation: The table of pending updates cannot
EQQA272E THE FIRST CHARACTER IN GROUP contain duplicate updates.
ID MUST BE ALPHABETIC
System action: The system waits for you to respond.
Explanation: Data entry error; see “Data Entry Errors”
on page 2. User response: Use the row command D to delete the
duplicate updates or change the duplicates.

18 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 User response: If you need to access the WS
EQQA280E THE TABLE CONTAINS DUPLICATE
description database, contact your security
ROWS
administrator.
Explanation: The table cannot contain duplicate rows.
System action: The system waits for you to respond. EQQA286E THE DATA SPECIFIED IS TOO LONG
User response: Use the row command D to delete the Explanation: The data that you have specified for
duplicate row items or change the duplicates. mass updating is longer than the maximum length
allowed for the data item.
EQQA281E NO MORE THAN 25 PENDING System action: The system waits for you to respond.
UPDATES CAN BE SPECIFIED IN
User response: Check the maximum data length
THIS SESSION
allowed and enter the correct data.
Explanation: It is not allowed to specify more than 25
pending updates in this session.
EQQA287E THE CONVERSION NUMBER CNR IS
System action: The system waits for you to respond. NOT SUPPORTED
User response: Use the row command D to delete Explanation: This message indicates a programming
pending updates or cancel the latest pending updates. error.
System action: The system waits for you to respond.
EQQA282E THE SPECIFIED BATCH JOB TYPE
User response: Contact your system programmer.
OPTION IS INVALID
System programmer response: Contact your system
Explanation: Data entry error; see “Data Entry Errors”
administrator.
on page 2.
A valid batch job type is T for trial run or U for
EQQA288E THE RESCALE FACTOR IS NOT
updating run.
SPECIFIED
Explanation: Data entry error; see “Data Entry Errors”
EQQA283E NO UPDATE AUTHORITY TO
on page 2.
APPLICATION DESCRIPTION DATA
BASE
EQQA289E THE RESCALE FACTOR MUST BE A
Explanation: You have attempted to update the
NUMBER 0 - 999
application description database, but you are not
authorized to update it. Explanation: Data entry error; see “Data Entry Errors”
on page 2.
System action: The system waits for you to respond.
User response: If you need to update the application
EQQA290E VALID DATA IS A NUMBER 1 - 99
description database, contact your security
administrator Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA284E YOU ARE NOT AUTHORIZED TO
READ THE CALENDAR DATA BASE EQQA291E VALID DATA IS A NUMBER 0 - 99
Explanation: You have attempted to read the calendar Explanation: Data entry error; see “Data Entry Errors”
database, but you are not authorized to read it. on page 2.
System action: The system waits for you to respond.
EQQA292E VALID DATA IS A NUMBER 100 - 999
User response: If you need access to the calendar
database, contact your security administrator Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA285E YOU ARE NOT AUTHORIZED TO
READ THE WS DESCRIPTION DATA EQQA293E VALID DATA IS A NUMBER 0 - 999
BASE
Explanation: Data entry error; see “Data Entry Errors”
Explanation: You have attempted to read the on page 2.
workstation (WS) description database, but you are not
authorized to read it.
System action: The system waits for you to respond.

Chapter 3. EQQAnnn Messages 19

EQQA294E PERIOD/RULE NAME FILTER IS NOT EQQA302E PREDECESSOR OPERATION PO IS
RELEVANT FOR CURRENT DATA NOT FOUND FOR OPERATION OP
ITEM
Explanation: The predecessor operation (predecessor
Explanation: Data entry error; see “Data Entry Errors” operation number PO) was not found for the operation
on page 2. (operation number OP). An internal predecessor
operation must exist within the application.
EQQA295E JOBNAME FILTER IS NOT RELEVANT System action: The system waits for you to respond.
FOR CURRENT DATA ITEM
User response: Enter an existing operation number.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA303E OPERATION OP IS NOT CONNECTED
TO APPLICATION
EQQA296E WS NAME FILTER IS NOT RELEVANT
Explanation: The operation (operation number OP)
FOR CURRENT DATA ITEM
has no predecessor or successor connections to the
Explanation: Data entry error; see “Data Entry Errors” application.
on page 2.
System action: The system waits for you to respond.
User response: Enter or change an internal
EQQA297E NEITHER JOBNAME NOR WS NAME
predecessor to establish a correct application link.
IS RELEVANT FOR CURRENT DATA
ITEM
EQQA304E OPERATION OP SPECIFIES WORK
Explanation: Data entry error; see “Data Entry Errors”
STATION OPWS, WHICH IS NOT
on page 2.
FOUND
Explanation: The operation (operation number OP) of
EQQA298E FILTER CRITERIA ARE NOT
this application specifies a workstation (workstation
RELEVANT FOR OWNER ID
name OPWS), which was not found in the workstation
Explanation: Data entry error; see “Data Entry Errors” description database.
on page 2.
System action: The system waits for you to respond.
User response: Enter an existing workstation name or
EQQA299I DATA SET NAME GIVEN; SPECIFIED
use the Workstation Description dialog to define the
APPLICATION ID(S) IGNORED
workstation name.
Explanation: When the name of the data set is
specified, it is not necessary to specify the application
EQQA305E DEPENDENCIES INCLUDING
IDs.
OPERATION OP FORM A LOOP
System action: None.
Explanation: A loop was detected in the operation
User response: None. (operation number OP) dependency network which
must be corrected. For example, operation 10 has
operation 5 as its predecessor, and operation 5 has
EQQA300E VALID DATA IS A NUMBER 1 - 255
operation 10 as its predecessor.
Explanation: Data entry error; “Data Entry Errors” on
System action: The system waits for you to respond.
page 2.
User response: Correct the found loop with these
internal predecessors.
EQQA301E THERE MUST BE AT LEAST ONE
OPERATION IN AN APPLICATION
EQQA306E VALID-FROM DATE LATER THAN
Explanation: The application has no operations. You
VALID-TO DATE
must specify at least one operation.
Explanation: Data entry error; see “Data Entry Errors”
System action: The system waits for you to respond.
on page 2.
User response: Specify one or more operations for the
When modifying an application, the valid-from date
application.
cannot be changed to a date later than the valid-to
date.

20 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQA307E OPERATION INPUT ARRIVAL TIME EQQA317E DBCS FIELD CONTAINS UNPAIRED
MUST BE SPECIFIED FOR A TIME SHIFT-OUT / SHIFT-IN CHARACTER
JOB
Explanation: The field indicated by the cursor
Explanation: Data entry error; see “Data Entry Errors” contains one or more superfluous shift-out or shift-in
on page 2. characters.
If the time-dependent job option is specified as YES, an System action: The data is rejected.
operation input arrival time must be specified.
User response: Correct data and reenter.

EQQA308E JOB SETUP OPERATION OP MUST

EQQA318E DBCS PART CONTAINS INVALID
HAVE A CPU SUCCESSOR
DBCS-CHARACTER
Explanation: The job setup operation (operation
Explanation: The field indicated by the cursor
number OP) must have a CPU successor operation.
contains out-of-range DBCS characters. With the
System action: The system waits for you to respond. exception of DBCS blank, X’4040’, each byte must be
within the range X’41’ - X’FE’.
User response: Enter the job setup operation number
as a CPU predecessor number. System action: The data is rejected.
User response: Correct data and reenter.
EQQA309E PRINT OPERATION OP MUST HAVE
A CPU PREDECESSOR
EQQA319E DBCS PART CONTAINS AN ODD
Explanation: The print operation (operation number NUMBER OF BYTES
OP) must have a CPU predecessor operation.
Explanation: The field indicated by the cursor is
System action: The system waits for you to respond. specified as a DBCS field, and requires two bytes per
character.
User response: Enter a CPU operation number as the
predecessor number. System action: The data is rejected.
User response: Correct data and reenter.
EQQA310E FIELD FORMAT SPECIFIED AS DBCS
BUT INPUT NOT BRACKETED DBCS
EQQA400E NO MATCHING JOB
Explanation: Data entry error; see “Data Entry Errors” DESCRIPTION(S) FOUND
on page 2.
Explanation: No job descriptions were found
matching the generic or non-generic search criteria that
EQQA311E DBCS PART OF BRACKETED FIELD IS you specified to generate a list of jobs.
BLANK
System action: The system waits for you to respond.
Explanation: Data entry error; see “Data Entry Errors”
User response: Try again, with different selection
on page 2.
criteria.

EQQA314E THE OWNER ID IS NOT SPECIFIED

EQQA401E NO MATCHING JOB DESCRIPTION
Explanation: Data entry error; see “Data Entry Errors” FOUND
on page 2.
Explanation: The job that you selected from a list does
not have a matching job description. The job may have
EQQA315E FORMAT OF OWNER ID SPECIFIED been deleted or modified after the list of job entries
AS DBCS BUT INPUT NOT was generated.
BRACKETED
System action: The request is rejected.
Explanation: Data entry error; see “Data Entry Errors”
User response: Return to the Job Selection Criteria
on page 2.
panel and press Enter to generate a fresh list of jobs.

EQQA316E DBCS PART OF BRACKETED OWNER

EQQA402I NO RUNCYCLES FOUND FOR THIS
ID FIELD IS INVALID
JOB
Explanation: Data entry error; see “Data Entry Errors”
Explanation: You tried to display the run cycles for a
on page 2.
job for which no run cycles have been specified.
System action: The request is rejected.

Chapter 3. EQQAnnn Messages 21

User response: None.
EQQA410E THE JOB DIALOG CANNOT BE USED
WHEN DBCS IS DEFINED FOR
EQQA403I THE JOB IS CREATED APPLID

Explanation: The job has been created and saved as a Explanation: You have tried to enter the job
job description. description dialog but DBCS bracketed input has been
defined for application IDs in your installation. The
System action: None. application ID of job descriptions must be the same as
User response: None. the job name. Job names cannot be entered in DBCS
bracketed format.

EQQA404I THE SELECTED JOB IS MODIFIED System action: The panel is redisplayed with this
error message.
Explanation: The job has been modified and saved as
a job description. User response: Use the Application Description dialog
instead.
System action: None.
User response: None. EQQA411E WORK STATION MUST BE SPECIFIED
Explanation: Data entry error; see “Data Entry Errors”
EQQA405E THE WS SPECIFIED IS NOT A CPU on page 2.
WS OR A GENERAL WS WITH WTO
SET The workstation pointed to by the cursor must be
entered.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA412E WORK STATION SPECIFIED IS NOT
A VALID JCL PREPARATION WORK
EQQA406E A JOB WITH THIS ID ALREADY STATION
EXISTS
Explanation: Data entry error; see “Data Entry Errors”
Explanation: You tried to create a job with an ID that on page 2.
already exists in the application description database.
The workstation must be a workstation with the JCL
System action: The system waits for you to respond. preparation indicator set to Y.
User response: Enter a unique job ID. If you want to
create a new version of an existing job, use the copy EQQA413E WORK STATION SPECIFIED IS NOT
function. A VALID MANUAL WORK STATION
Explanation: Data entry error; see “Data Entry Errors”
EQQA407E THE JOB IS BEING UPDATED BY on page 2.
ANOTHER USER
The workstation must be a MANUAL workstation.
Explanation: Another user is currently updating the
job that you want to update.
EQQA414E 24.00 NOT ALLOWED AS A
System action: The system waits for you to respond. FROM-RUN TIME
User response: Try again later. Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQA408E THE JOBNAME HAS NOT BEEN
SPECIFIED EQQA415E NO PREDECESSORS FOUND THAT
Explanation: Data entry error; see “Data Entry Errors” MATCH SELECTION CRITERIA
on page 2. Explanation: You tried to select predecessors for a job.
No predecessors were found with the specified
EQQA409I THE SELECTED JOB IS DELETED selection criteria.

Explanation: The selected job has been deleted from System action: The request is rejected.
the job description database. User response: None.
System action: None.
User response: None.

22 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQA416E 00.00 NOT ALLOWED AS A TO-RUN EQQA502E GROUP DEFINITION ID FIELD CAN
TIME BE FILLED IN ONLY WHEN NO RUN
CYCLES
Explanation: Data entry error; see “Data Entry Errors”
on page 2. Explanation: You cannot specify a group definition ID
when run cycles already exist.
EQQA418E FROM-RUN TIME MUST BE System action: The system waits for you to respond.
SPECIFIED
User response: Either erase the data in the group
Explanation: Data entry error; see “Data Entry Errors” definition ID field or delete the run cycles for the
on page 2. application.
Either a run time has been entered or run cycles are
missing. EQQA503E GROUP DEFINITION CANNOT
BELONG TO ANOTHER GROUP
User response: Specify a from-run time.
Explanation: You can specify a group definition ID
only when the application type is A.
EQQA419E INTERNAL PREDECESSORS ARE NOT
ALLOWED FOR JDS System action: The system waits for you to respond.
Explanation: Data entry error; see “Data Entry Errors” User response: Change the application type to A or
on page 2. erase the group definition ID field.
If you are currently defining a job, the application ID
must be completed for a predecessor. EQQA504E APPLICATION TYPE MUST BE
OCHCSTN, OCHCGRP OR BLANK
EQQA500E GROUP DEFINITION CANNOT HAVE Explanation: The selection criteria that you have
OPERATIONS specified contains an invalid application type.
OCHCSTN and OCHCGRP are the national language
Explanation: A group definition cannot contain
characters for ’A’ (applications) and ’G’ (group
operations.
definitions).
System action: The system waits for you to respond.
System action: The system waits for you to respond.
User response: If operations are to be defined in this
User response: Enter the correct characters for
application, change the application type to A.
applications or group definitions, or blank to select
both applications and group definitions.
EQQA501W GROUP DEFINITION APPLGRID
COULD NOT BE FOUND IN AD FILE
EQQA505E TYPE MUST BE OCHCSTN OR
Explanation: The current application description (AD) OCHCGRP
references an application group definition that cannot
Explanation: You have specified an invalid application
be found in the AD database. Either you entered the
type. OCHCSTN and OCHCGRP are the national
wrong name, or the application group has not yet been
language characters for ’A’ (applications) and ’G’
created, or the application group has a pending status
(group definitions).
(not selectable for processing), or you are not
authorized to reference it. If you want to, and if you System action: The system waits for you to respond.
are authorized, you can save the current application
User response: Enter one of the supported application
description while it references an application group that
types.
does not exist. Such an application description is not
used to create occurrences in the long term plan (LTP).
EQQA506I RUN COMMAND NOT ALLOWED.
System action: The system waits for you to respond.
APPLICATION IN A GROUP
User response: If you want the application description CONTAINS NO RUN CYCLE
to be selected by LTP programs, enter the correct group
Explanation: An application that references a group
definition ID, or create the referenced group definition
definition for run cycle information does not itself
with the application status field set to A.
contain run cycles.
System action: The request is rejected.
User response: None.

Chapter 3. EQQAnnn Messages 23

 System action: The system waits for you to respond.
EQQA507I OPER COMMAND NOT ALLOWED. A
GROUP DEFINITION DOES NOT User response: Change the application type to A or
HAVE OPERATIONS blank, or erase the data in the group definition ID field.
Explanation: A group definition (application type=G)
does not contain operations. EQQA513I COMMAND NOT VALID FOR A
GROUP DEFINITION
System action: The request is rejected.
Explanation: Calculate and print rundays, or Modify
User response: None.
long term plan (LTP) can be requested only for
applications.
EQQA508E RUN CYCLES ARE NOT ALLOWED
System action: The request is rejected.
FOR A JOB DESCRIPTION IN A
GROUP User response: None.
Explanation: A job description that references a group
definition for run cycle information cannot itself EQQA514W GROUP DEFINITION HAS NO RUN
contain run cycles. CYCLES
System action: The system waits for you to respond. Explanation: The group definition contains no run
cycle information. Applications that reference this
User response: Either erase the data in the group
group definition are automatically included in the long
definition ID field or delete the run cycles for this job
term plan.
description.
System action: The system waits for you to respond.
EQQA509I NO RUN CYCLES FOR A JOB User response: If you want to use this group
DESCRIPTION IN A GROUP definition to schedule applications, specify run cycle
information.
Explanation: A job description that references a group
definition for run cycle information cannot itself
contain run cycles. EQQA515E CALENDAR CANNOT BE SPECIFIED
FOR A JOB IN A GROUP
System action: The request is rejected.
Explanation: A calendar ID cannot be specified for a
User response: None.
job that references a group definition for run cycle
information.
EQQA510E PRIORITY CANNOT BE SPECIFIED
System action: The system waits for you to respond.
FOR A GROUP DEFINITION
User response: Either erase the data in the calendar
Explanation: You cannot specify priority for a group
ID field or erase the data in the group definition ID
definition.
field.
System action: The system waits for you to respond.
User response: Erase the data in the priority field. EQQA516E NO RUN CYCLES FOR AN
APPLICATION IN A GROUP
EQQA511E CALENDAR CANNOT BE SPECIFIED Explanation: An application that references a group
FOR AN APPLICATION IN A GROUP definition for run cycle information cannot itself
contain run cycles.
Explanation: A calendar ID cannot be specified for an
application that references a group definition for run System action: The request is rejected.
cycle information.
User response: None.
System action: The system waits for you to respond.
User response: Either erase the data in the calendar EQQA520E THE RULE ON WHICH THE RUN
ID field or erase the data in the group definition ID CYCLE IS BASED MUST BE DEFINED
field.
Explanation: A rule-based run cycle (type R or E) was
inserted or replicated in the run cycle table, but no rule
EQQA512E GROUP DEFINITION CANNOT definition was specified.
BELONG TO ANOTHER GROUP
System action: The request is rejected.
Explanation: Group definitions can be specified only
User response: Use the S row command to select the
when the application type is A (application) or blank
Rule Modification panel and define the rule.
(both application and group definition).

24 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 User response: Enter the correct value.
EQQA521E A VALID RULE NAME MUST BE
SPECIFIED
| EQQA534E JOB SETUP NOT AVAILABLE FOR
Explanation: You have not entered a valid rule name.
| NOT CENTRALIZED FTW
A valid rule name hasa maximum of 8 characters,
| OPERATIONS
where the first character is alphabetical and the
remaining characters are alphanumeric or national. | Explanation: A job setup requires, among its
| successors, an operation with the following features:
System action: The request is rejected.
| v The operation must run on a CPU.
User response: Specify a valid rule name.
| v The CPU must not be a fault-tolerant workstation or
| the operation must use centralized script support.
EQQA522E THE RULE NAME MUST BE UNIQUE | v The operation’s jobname must be equal to the job
WITHIN AN AD | setup name.
Explanation: You have specified a rule name that has | In this case, the only operation running on a CPU and
already been defined for a rule-based run cycle for this | having the same jobname is a FTW operation that does
application description. | not use the centralized script support.
System action: The request is rejected. | System action: The request is rejected.
User response: Specify a unique rule name. | User response: Enter the correct value.

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.

EQQA531E INCONSISTENT OPTION WHEN FT

WORKSTATION
Explanation: This option is wrong for a fault-tolerance
workstation. The fault-tolerant workstation requires a
default value.
System action: Request is rejected.
User response: Enter the correct value.

| EQQA532E FTW CANNOT HAVE A JOB SETUP

| AS IMMEDIATE PREDECESSOR
| Explanation: The fault-tolerant workstation does not
| accept a general workstation as a predecessor.
| System action: The request is rejected.
| User response: Enter the correct value.

EQQA533E FTW CANNOT HAVE A PRINT

OPERATION AS IMMEDIATELY
SUCCESSOR
Explanation: The fault-tolerance workstation does not
accept a printer workstation as a predecessor.
System action: Request is rejected.

Chapter 3. EQQAnnn Messages 25

26 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 4. EQQCnnn Messages
Tivoli Workload Scheduler for z/OS and restart it.
EQQC001I THE AUTOMATIC RECOVERY
SUBTASK HAS STARTED
EQQC005E THE AUTOMATIC RECOVERY
Explanation: The automatic job recovery subtask has
INITIALIZATION FAILED, MODULE
been successfully initialized.
EQQCASEM NOT FOUND
System action: Automatic job recovery processing is
Explanation: The initialization of the automatic job
started.
recovery subtask failed because the load module
User response: None. EQQCASEM could not be found in a library that can
be accessed by IBM Tivoli Workload Scheduler for
z/OS.
EQQC002E THE AUTOMATIC RECOVERY
INITIALIZATION FAILED System action: Automatic job recovery initialization is
terminated.
Explanation: The automatic job recovery subtask was
not initialized because there is an error in the AROPTS User response: Contact your system programmer.
initialization statement.
System programmer response: Make sure that the
System action: Automatic job recovery initialization is load module EQQCASEM is present in a library that
terminated. can be accessed by IBM Tivoli Workload Scheduler for
z/OS. Stop the IBM Tivoli Workload Scheduler for
Problem determination: This message is preceded by
z/OS started task and restart it.
a message in the IBM Tivoli Workload Scheduler for
z/OS message log giving the reason for this error
message. EQQC006E HOUR AND MINUTE MUST BOTH BE
TWO-DIGIT NUMBERS
User response: Contact your system programmer.
Explanation: A nonnumeric time value has been
System programmer response: Correct the error in the
specified.
AROPTS initialization statement and restart IBM Tivoli
Workload Scheduler for z/OS. System action: Processing continues.
System programmer response: Reenter a numeric
EQQC003I THE AUTOMATIC RECOVERY time value. .* WTO=YES ROUTE=2
SUBTASK HAS ENDED NORMALLY
Explanation: This message is issued when the IBM EQQC007E AN ABEND OCCURRED IN THE
Tivoli Workload Scheduler for z/OS subsystem is being AUTOMATIC RECOVERY SUBTASK,
stopped by an operator command. IT IS RESTARTED
System action: The IBM Tivoli Workload Scheduler for Explanation: An error has caused the automatic job
z/OS termination processing continues. recovery subtask to end abnormally, but it has been
able to restart.
User response: None.
System action: Automatic job recovery resumes
normal processing, but one or more requests for service
EQQC004E STARTTIME OR ENDTIME OPTION
may have been rejected.
TIME IN AROPTS STATEMENT IS
NOT VALID Problem determination: At abend, a dump is written
to the SYSxDUMP data set.
Explanation: The STARTTIME or ENDTIME option in
the AROPTS initialization statement is not specified in User response: Inform your system programmer about
a valid IBM Tivoli Workload Scheduler for z/OS time the error and, if the error can be reproduced, of the
format. The option TIME must be a 4-digit decimal sequence of dialog requests leading to the error.
number in the format HHMM, where HH is from 00
System programmer response: Collect relevant
through 23, and MM is from 00 through 59.
information about the sequence of events leading to
System action: Automatic job recovery initialization is this error. Make sure that the dump data set and the
terminated. IBM Tivoli Workload Scheduler for z/OS message log
are available for inspection. Contact your system
User response: Correct the STARTTIME or ENDTIME
administrator.
value in the AROPTS initialization statement. Stop IBM

© Copyright IBM Corp. 1991, 2003 27

 cannot be opened, review the earlier messages in the
EQQC008E HOUR MUST BE IN THE RANGE 0 TO
IBM Tivoli Workload Scheduler for z/OS message log.
23
User response: Use the ended-in-error list of the
Explanation: A time value has been specified where
Modify Current Plan dialog to decide whether or not a
the hour number is not valid.
new automatic job recovery attempt should be made
System action: Processing continues. for the job that ended in error.
System programmer response: Reenter the time value System programmer response: Check with your
and specify an hour number in the range 0 through 23. system programmer why the file FILE could not be
opened.
EQQC009E MINUTE MUST BE IN THE RANGE 0
TO 59 EQQC013W AUTOMATIC RECOVERY REQUEST
FAILED, CANNOT ALLOCATE
Explanation: A time value has been specified where
BUFFERS
the minute number is not valid.
Explanation: A storage allocation error prevented
System action: Processing continues.
automatic job recovery from checking whether or not
System programmer response: Reenter the time value recovery should be performed for the job that ended in
and specify a minute number in the range 0 through error. This message may be followed by message
59. EQQC045I with reason code 50, which identifies the job
checked by automatic job recovery.

EQQC011W AUTOMATIC RECOVERY REQUEST System action: No recovery attempt is made and the
FAILED, SERVICE INACTIVE job remains ended in error.

Explanation: Automatic job recovery requires service User response: Use the ended-in-error list of the
from other IBM Tivoli Workload Scheduler for z/OS Modify Current Plan dialog to decide whether or not a
subtasks. When automatic job recovery was initiated to new automatic job recovery attempt should be made
determine whether or not recovery should be for the job that ended in error.
performed for the job that ended in error, the service
System programmer response: Stop IBM Tivoli
SERVICE was down (not available).
Workload Scheduler for z/OS and restart it in a larger
System action: No recovery attempt is made and the region.
job remains ended in error.
Problem determination: To determine why the service EQQC014W AUTOMATIC RECOVERY REQUEST
is not available, review the earlier messages in the IBM FAILED DUE TO I/O ERROR
Tivoli Workload Scheduler for z/OS message log. For
Explanation: An I/O error prevented automatic job
job tracking, consider the messages that mention the
recovery from determining whether or not recovery
normal mode manager.
should be performed for the job that has ended in
User response: Use the ended-in-error list of the error. This message may be followed by message
Modify Current Plan dialog to decide whether or not a EQQC045I with reason code 50, which identifies the job
new automatic job recovery attempt should be made checked by automatic job recovery.
for the job that ended in error.
System action: No recovery attempt is made and the
System programmer response: Check why the service job remains ended in error.
SERVICE was down.
Problem determination: Review the earlier messages
in the IBM Tivoli Workload Scheduler for z/OS
EQQC012W AUTOMATIC RECOVERY REQUEST message log for a message issued for the I/O error.
FAILED, CANNOT OPEN FILE FILE
User response: Use the ended-in-error list of the
Explanation: Automatic job recovery requires access to Modify Current Plan dialog to decide whether or not a
IBM Tivoli Workload Scheduler for z/OS VSAM files. new automatic job recovery attempt should be made
Failure to open one of these files prevented automatic for the job that ended in error.
job recovery from checking whether or not recovery
System programmer response: Refer to the associated
should be performed for the job that ended in error.
I/O error message for guidance.
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

28 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 Scheduler for z/OS found that cleanup actions were in
EQQC020E NO AUTOMATIC RECOVERY
progress.
BECAUSE INVALID CLEAN UP TYPE:
CLNTYP FOR OPERATION OPNO IN System action: The automatic recovery is postponed
APPLICATION ADID until the cleanup actions are complete.
Explanation: An automatic recovery task was User response: None.
executed that has the cleanup type set to the value
specified by CLNTYP. However, the only allowed
values are None or Immediate. EQQC023W NO AUTOMATIC RECOVERY TEST
BECAUSE NO JCL RECORD FOR THE
System action: The automatic recovery is not OPERATION
processed and the cleanup actions are not started
Explanation: The JCL record could not be read. This
System programmer response: Check if the cleanup prevented automatic job recovery from determining
type can be changed to Immediate. 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
EQQC021W NO AUTOMATIC RECOVERY TEST
identifies the job checked by automatic job recovery.
BECAUSE NO ERROR INFORMATION
IN JNT RECORD System action: No recovery attempt is made and the
job remains ended in error.
Explanation: When a job fails, error information about
the failing operation is saved in the job name table Problem determination: Review the IBM Tivoli
(JNT) record. Automatic job recovery was initiated but Workload Scheduler for z/OS message log for
could not determine if recovery should be performed inconsistencies at the time that the job ended in error.
for the failed job because no error information was
available in the JNT record. This message is followed User response: If any recovery actions by automatic
by message EQQC045I with reason code 50, which job recovery were required for the job that failed, the
identifies the job checked by automatic job recovery. actions must be initiated manually. Use the Modify
Current Plan dialog to initiate the actions.
System action: No recovery attempt is made and the
job remains ended in error. System programmer response: Check the IBM Tivoli
Workload Scheduler for z/OS message log for any
Problem determination: Review the IBM Tivoli messages issued at the time that the job ended in error
Workload Scheduler for z/OS message log for to determine why the JCL record could not be read.
inconsistencies at the time that the job ended in error.
Also review the event data set for the completion of the
job. Refer to IBM Tivoli Workload Scheduler for z/OS EQQC024W NO AUTOMATIC RECOVERY TEST
Diagnosis Guide and Reference for the layout of the BECAUSE OPERATION RECORD
record in the event data set. MODIFIED

User response: If any recovery actions by automatic Explanation: Automatic job recovery could not
job recovery were required for the job that failed, the determine whether or not recovery should be
actions must be initiated manually. Use the Modify performed for the job that ended in error because the
Current Plan dialog to initiate the actions. operation record indicates that the operation no longer
has the error status.
If you use automatic job recovery together with the
restart and cleanup functions and have defined the System action: No recovery attempt is made for the
RESSTEP parameter of the RECOVER statement, job that ended in error.
specify STEPEVENTS(ALL) on the EWTROPTS User response: None.
statement. Otherwise automatic job recovery and restart
and cleanup are not invoked.
EQQC025W CLEAN UP ACTION NOT STARTED
System programmer response: Check the IBM Tivoli BECAUSE CP14 RECORD COULD NOT
Workload Scheduler for z/OS message log for any BE READ
messages issued at the time that the job ended in error
to determine why no JNT record exists. Explanation: An automatic recovery task was
executed. The cleanup type was set to Immediate, so it
tried to read the job log record in the current plan to
EQQC022I AUTOMATIC RECOVERY ACTION start the cleanup actions. However, the record was not
POSTPONED FOR OPERATION OPNO found
IN APPLICATION ADID. CLEAN UP
ACTIONS PENDING System action: The recovery attempt stops.

Explanation: When the automatic recovery for this System programmer response: Current plan job log
operation was about to start, IBM Tivoli Workload information records (CP14) are created by the

Chapter 4. EQQCnnn Messages 29

Controller or by non z/OS trackers when a job with a syntactical error was found. This message is
execution is completed. Check the EQQMLOG of the followed by message EQQC045I with reason code 50,
Controller to diagnose the problem. which identifies the job checked by automatic job
recovery.
EQQC026W NO AUTOMATIC RECOVERY TEST System action: No recovery attempt is made and the
BECAUSE JCL MEMBER IS BEING job remains ended in error.
USED
Problem determination: Review the JCL of the
Explanation: Automatic job recovery could not identified operation.
determine whether or not recovery should be
User response: Check the RECOVER statements for
performed for the job that ended in error, because the
syntactical errors. Make sure that the operation is
member on the JCL repository file (ddname EQQJ1SDS
separated from the operands by one or more blanks,
and EQQJS2DS) was being used by another IBM Tivoli
and that the operands are separated by a comma.
Workload Scheduler for z/OS subtask. This message is
When you have found and corrected the error, you can
followed by message EQQC045I with reason code 50,
initiate a new automatic job recovery attempt for the
which identifies the job checked by automatic job
job that ended in error by using the ended-in-error list
recovery.
of the Modify Current Plan dialog.
System action: No recovery attempt is made and the
job remains ended in error.
EQQC029I NO AUTOMATIC RECOVERY
User response: When the EQQJSxDS JCL member is BECAUSE RECOVER STATEMENT
free, you can initiate a new automatic job recovery DOES NOT MATCH THIS ERROR
attempt for the job that ended in error by using the
Explanation: While automatic job recovery was
ended-in-error list of the Modify Current Plan dialog.
checking whether or not recovery should be performed
for a job that ended in error, one or more RECOVER
EQQC027W NO AUTOMATIC RECOVERY statements were found but none matched the current
BECAUSE PROCLIB MEMBER NOT error. This message is followed by message EQQC045I
FOUND with reason code 50, which identifies the job checked
by automatic job recovery.
Explanation: No automatic job recovery could be
performed for the job that ended in error because the System action: No recovery attempt is made and the
RECOVER statement that matched the error specifies a job remains ended in error.
procedure library member that could not be found.
User response: Consider if the error should be
This message is followed by message EQQC045I with
covered in the recovery scheme.
reason code 50, which identifies the job checked by
automatic job recovery.
EQQC044I AUTO RECOVERY OF APPL
System action: No recovery attempt is made and the
ADIDDATE H.M, OP WSNOPJNJID
job remains ended in error.
Explanation: Automatic job recovery actions have
Problem determination: Review the JCL to determine
been taken for the specified occurrence (application
the procedure library member name. The selected
ADID DATE H. M, operation WSN OP, where DATE H.
RECOVER statement is followed by a comment line
M is the occurrence input arrival time). The specified
that gives the member name.
JCL rebuild is made. Restart, application addition, and
User response: Check that the member name is release of successors are in process as specified in the
correctly spelled and that it is available in the RECOVER statement.
EQQPRLIB file. When you have found and corrected
System action: The specified automatic recovery
the error, edit the JCL and insert a % sign in column 4
actions are started up.
of the RECOVER line so as to reconvert the line into a
RECOVER statement. You can initiate a new automatic User response: None.
job recovery attempt for the job that ended in error by
using the ended-in-error list of the Modify Current Plan
dialog. EQQC045I AUTO RECOVERY INFO RS, APPL
ADIDDATE H.M, OP WSNOPJNJID

EQQC028W NO AUTOMATIC RECOVERY TEST Explanation: Automatic job recovery is being

BECAUSE ERROR IN RECOVER performed for the job identified as application ADID
STATEMENT DATE H. M, operation WSN OP, where DATE H. M is
the occurrence input arrival time). This message is
Explanation: While automatic job recovery was issued to keep track of a particular action taken during
checking whether or not recovery should be performed the recovery processing.
for a job that ended in error, a RECOVER statement

30 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

RS is a reason code that stands for a certain error or (RS) indicate the errors or actions, or both, related to
action, or both, related to automatic job recovery. automatic job recovery:
Message EQQC047E has a list of the reason codes and 1 Misplaced IBM Tivoli Workload Scheduler for
their meanings. z/OS recover statement.
2 Incorrect parameter.
System action: The specified automatic recovery
3 Unbalanced parentheses.
actions are started up.
4 Invalid continuation line.
Problem determination: Review the JCL of the 5 Invalid length of parameter value.
identified operation. Identify the recovery actions 6 A parameter appears twice in same recover
described in the RECOVER statement of the JCL. statement.
7 Invalid return code from exit.
User response: Look up the meaning of reason code 8 Terminate return code from exit.
RS in the list given in message EQQC047E. Review the 9 Abandon return code from exit.
action taken and see if it matches the action requested. 10 Invalid restart parameter value. Set Y, YES, N,
If necessary, take the appropriate action. or NO.
11 Procedure library member not found.
EQQC046W AUTO RECOVERY WARNING RS, 12 I/O error.
APPL ADID DATEH.M, OP 13 Unable to load exit routine.
WSNOPJNJID 14 No job statement found.
15 Incorrect job statement. Cannot add restart
Explanation: Automatic job recovery was attempted parameter.
for the job identified as application ADID DATE H. M, 16 Invalid specification of generic code.
operation WSN OP, where DATE H. M is the 17 Loop in the case code lists.
occurrence input arrival time. A problem was 18 Checkpoint name contains special characters.
encountered that inhibited automatic job recovery. 19 Missing stepname.
RS is a reason code that stands for a certain error or 20 Too many values specified in parameter.
action, or both, related to automatic job recovery. 21 Failing OP is outside rerun or successor tree.
Message EQQC047E has a list of the reason codes and 22 External successor in rerun tree is not in the
their meanings. failing tree.
23 Inconsistency with AD of failing occurrence
System action: The operation is left unchanged by (for example, AD no longer exists or is not
automatic job recovery. active).
Problem determination: Review the JCL of the 24 AD of application to add could not be found.
identified operation. Identify the recovery actions 25 Error while using MCP (additional message by
described in the RECOVER statement of the JCL. MCP).
26 Unable to allocate virtual storage.
User response: Look up the meaning of reason code 27 Error detected and handled by other subtask.
RS in the list given in message EQQC047E. Review 28 Improper naming of steps, give all unique
what recovery actions are taken and see if they match names.
the actions requested in the RECOVER statement. If 29 Cannot add restart param. because no
necessary, use the Modify Current Plan dialog to delimiter last job line.
perform the rest of the recovery actions. 30 No information about error in job name table
(JNT).
31 Failing operation record could not be read.
EQQC047E AUTO RECOVERY ERROR RS, APPL
32 Invalid stepname or no step with that name.
ADIDDATE H.M, OP WSNOPJNJID
33 More than one step in JS record with the given
Explanation: Automatic job recovery was attempted name.
for the job identified as application ADID DATE H. M, 34 JS data set in use. Recovery test canceled.
operation WSN OP, where DATE H. M is the 35 JS data set member in use. Recovery test
occurrence input arrival time. An error was canceled.
encountered that inhibited the recovery actions. 36 OP record has been changed. Recovery test
canceled.
RS is a reason code that stands for a certain error or
37 Invalid range.
action, or both, related to automatic job recovery (see
38 No occurrence exists for the specified
Problem determination).
application.
System action: The job remains ended in error and the 39 Recovery actions taken.
extended status of the operation is set to E. The JCL 40 No JS record.
record on the JCL repository data set might have been 41 Restart step not present in the JCL.
updated with information about the error. 42 Step end entries missing in JNT record
(CPLREC04). The error can relate to:
Problem determination: The following reason codes v Nested procedures

Chapter 4. EQQCnnn Messages 31

 v JCL INCLUDE statements System action: No recovery is made and the job
v JCL IF/THEN/ELSE/ENDIF statement remains ended in error. The extended status of the
constructs. operation is set to E.
These JCL statements are restricted by Problem determination: Message EQQC047E has a list
automatic job recovery when used in of the reason codes and their meanings. The JS record
conjunction with the ERRSTEP, RESSTEP, or may have been updated with information about the
STEPCODE parameters of the RECOVER error. Review the JCL of the identified operation.
statement. Identify the recovery actions described in the
43 Parameter not supported when RECOVER statement of the JCL.
STEPEVENTS(ABEND) specified.
User response: Look up the meaning of reason code
44 RESSTEP=% specified but error not related to
RS in the list given in message EQQC047E. Review
a step.
what recovery actions are taken and see if they match
45 A required service function (NMM) has
the actions requested in the RECOVER statement. If
terminated.
necessary, use the Modify Current Plan dialog to
46 No free input arrival time for the application
perform the rest of the recovery actions.
to add.
47 Missing value for parameter.
48 Authorization check requires user ID. EQQC061E AUTOMATIC RECOVERY FAILED, I/O
50 Adding identification data to messages in ERROR
ARTOP.
51 Error in ALTWS parameter. Explanation: Automatic job recovery failed for the job
52 Error in ALTJOB parameter. that ended in error because an I/O error occurred. The
I/O error occurred while the automatic job recovery
User response: Check the RECOVER statements. subtask was determining whether recovery should be
Comment lines that describe the error in detail are performed, or while the recovery actions were being
added to the JCL. When you have found and corrected activated or implemented.
the error, you can use the ended-in-error list of the
Modify Current Plan dialog to initiate a new automatic This message is preceded by a message that describes
job recovery attempt. 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.
EQQC048W AUTO RECOVERY WARNING RS
System action: The job remains ended in error. Some
Explanation: Automatic job recovery was attempted of the intended recovery actions may have been started
for the job that ended in error, but was inhibited up or completed.
because of a problem with reason code RS. This
message differs from EQQC046W in that automatic job Problem determination: Review the JCL of the
recovery was not able to identify the application to be identified operation. Identify the recovery actions
handled. described in the RECOVER statement of the JCL.

System action: No recovery is made and the job User response: When you have found and corrected
remains ended in error. the error, you can initiate a new automatic job recovery
attempt for the job that ended in error by using the
Problem determination: Message EQQC047E has a list ended-in-error list of the Modify Current Plan dialog.
of the reason codes and their meanings. Review the You may have to initiate the recovery actions manually,
JCL of the identified operation. Identify the recovery or you may have to change the RECOVER statement to
actions described in the RECOVER statement of the encompass only the remaining recovery actions.
JCL.
System programmer response: Review the IBM Tivoli
User response: Look up the meaning of reason code Workload Scheduler for z/OS message log for I/O
RS in the list given in message EQQC047E. Review errors that immediately precede this message.
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 EQQC062E AUTOMATIC RECOVERY FAILED,
perform the rest of the recovery actions. NOT ENOUGH VIRTUAL STORAGE -
SIZE

EQQC049E AUTO RECOVERY ERROR RS Explanation: Automatic job recovery failed for the job
that ended in error because of insufficient virtual
Explanation: Automatic job recovery was attempted storage. The failure occurred while the automatic job
for the job that ended in error, but was inhibited recovery subtask was determining whether recovery
because of an error with reason code RS. This message should be performed, or while the recovery actions
differs from EQQC047E in that automatic job recovery were being activated or implemented. SIZE is the
was not able to identify the application to be handled. amount of virtual storage requested.

32 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

This message is followed by message EQQC045I with System action: No recovery attempt is made and the
reason code 50, which identifies the job checked by job remains ended in error.
automatic job recovery.
Problem determination: Check the definition of the
System action: The job remains ended in error. Some ddname EQQPRLIB.
of the intended recovery actions may have been started
User response: Contact your system programmer.
up or completed.
When your system programmer has fixed the problem,
Problem determination: Review the JCL of the you can initiate a new automatic job recovery attempt
identified operation. Identify the recovery actions for the job that ended in error by using the
described in the RECOVER statement. ended-in-error list of the Modify Current Plan dialog.
User response: When you have found and corrected System programmer response: Check that the
the error, you can initiate a new automatic job recovery ddname EQQPRLIB is correctly defined. When the
attempt for the job that ended in error by using the error is corrected, stop IBM Tivoli Workload Scheduler
ended-in-error list of the Modify Current Plan dialog. for z/OS and restart it.
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 IBM Tivoli
Workload Scheduler for z/OS 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 earlier messages
in the IBM Tivoli Workload Scheduler for z/OS
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 IBM Tivoli Workload Scheduler for
z/OS is authorized to open the data set for input.
When the error is corrected, stop IBM Tivoli Workload
Scheduler for z/OS and restart it.

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.

Chapter 4. EQQCnnn Messages 33

34 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 5. EQQCLnnn Messages
was updated in the scheduler’s variable table specified
EQQCL00I PROCESSING: INSTRUCTION
by the INIT instruction.
Explanation: OCL is processing the INSTRUCTION
System action: The scheduler’s processing continues.
instruction
User response: None.
System action: Processing continues.
User response: None.
EQQCL08I OCCURRENCE APPL WAS
COMPLETED
EQQCL02X INSTR INSTRUCTION EXECUTED:
Explanation: OCL processed a COMPL instruction
RC=RETURN_CODE
that completed the occurrence APPL.
Explanation: This message reports the return code
System action: The scheduler’s processing continues.
(RETURN_CODE) of the instruction. X can be one of
the following: User response: None.
I Information (RC=0)
EQQCL09I THE OPERATION WAS COMPLETED:
W Warning (RC=4)
OPNO(OPNUM) APPL(APPL) IA(IADT)
E Error (RC=8)
Explanation: OCL completed the operation OPNUM
System action: The scheduler’s processing continues. within the occurrence APPL with the input arrival date
and time IADT.
User response: None.
System action: The scheduler’s processing continues.
EQQCL03I TRUE CONDITION: IF EXPRESSION User response: None.
Explanation: An IF instruction was specified. OCL
processed the instruction specified in the THEN clause. EQQCL0AI THE OCCURRENCE WAS ADDED:
APPL(APPL) IA(IADT)
System action: The scheduler’s processing continues.
Explanation: OCL added a new occurrence in the
User response: None.
scheduler’s current plan or long term plan. APPL is the
occurrence ID and IADT is the input arrival date and
EQQCL04I TRUE CONDITION: ELSE time.
EXPRESSION
System action: The scheduler’s processing continues.
Explanation: An IF instruction was specified. OCL
User response: None.
processed the instruction specified in the ELSE clause.
System action: The scheduler’s processing continues.
EQQCL0BI A DELETE REQUEST WAS EXECUTED
User response: None. FOR APPLICATION APPL
Explanation: OCL tried to add a new occurrence in
EQQCL05I FALSE CONDITION: IF EXPRESSION the scheduler’s plan, but a problem occurred, so it
issued a DELETE request for the application APPL.
Explanation: The condition specified in the IF
instruction is false. System action: The scheduler’s processing continues.

System action: The scheduler’s processing continues. User response: None.

User response: Verify that the specified keywords are

correct. EQQCL0CI DEFAULT PREDECESSOR
OPERATION IS USED: DEFPREOPNO

EQQCL06I THE DEFAULT VALUE OF VARIABLE Explanation: OCL defined DEFPREOPNO as an

VARNAME WAS UPDATED external predecessor of the operation to be modified.

Explanation: An UPD or SETUPD instruction was System action: The scheduler’s processing continues.
specified. The default value of the variable VARNAME
User response: None.

© Copyright IBM Corp. 1991, 2003 35

EQQCL0DI INTERNAL PREDECESSOR EQQCL0JI SEARCHING FOR OCCURRENCE
PREOPNUM DEFINED TO APPL IN CP
OPERATION OPNUM
Explanation: OCL is searching the occurrence APPL in
Explanation: A new internal predecessor was defined the scheduler’s current plan (CP).
for operation OPNUM.
System action: The scheduler’s processing continues.
System action: The scheduler’s processing continues.
User response: None.
User response: None.
EQQCL0KI TOTAL NUMBER OF MATCHING
EQQCL0EI APPL BELONGS TO GROUP APPLGRP OCCURRENCES: N_OCC
Explanation: Application APPL is associated to the Explanation: OCL found N_OCC occurrences in the
application group APPLGRP. scheduler’s current plan that match the specified
selection parameters.
System action: The scheduler’s processing continues.
System action: The scheduler’s processing continues.
User response: None.
User response: None.
EQQCL0FI THE OCCURRENCE WAS DELETED:
APPL(APPL) IA(IADT) EQQCL0LI OPER. IN ERROR: OPNUM
APPL(APPL) IA(IADT) WS(WSNAME)
Explanation: The occurrence APPL was deleted from
ERR(ERR_CODE)
the scheduler’s current plan.
Explanation: OCL found an ended-in-error operation
System action: The scheduler’s processing continues.
with error code ERR_CODE.
User response: None.
System action: The scheduler’s processing continues.
User response: None.
EQQCL0GI THE OPERATION WAS DELETED:
OPNO(OPNUM) APPL(APPL) IA(IADT)
EQQCL0MI ERROR CODE ERR_CODE MATCHES
Explanation: The operation OPNUM was deleted from
ERR() FOR OPERATION OPNUM
the occurrence APPL with the input arrival date and
time IADT. Explanation: This “output” message reports all the
operations whose error code matches the value that the
System action: The scheduler’s processing continues.
user specified in the ERR() parameter.
User response: None.
System action: The scheduler’s processing continues.
User response: None.
EQQCL0HI OCCURRENCE FOUND IN LTP:
APPL(APPL) IA(IADT)
EQQCL0NI REPLY TO WTOR WAS ISSUED
Explanation: OCL found an occurrence in the long
term plan (LTP) that matches with the specified Explanation: An operator replied to the WTO issued
selection parameters. by OCL.
System action: The scheduler’s processing continues. System action: The scheduler’s processing continues.
User response: None. User response: None.

EQQCL0II DATE IS VALID EQQCL0OI OCCURRENCE FOUND: APPL(APPL)

IA(IADT) STATUS(STATUS)
Explanation: The input date is valid.
Explanation: OCL found an occurrence in the current
System action: OCL calculates about 210 variables,
plan that matches the selection parameters.
based on the input date.
System action: The scheduler’s processing continues.
User response: None.
User response: None.

36 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 User response: None.
EQQCL0PI CMD COMMAND WAS ISSUED
Explanation: OCL issued command CMD, which can
EQQCL0WI JOBNAME WAS CHANGED FOR
be SRSTAT, OPSTAT, or WSSTAT.
OPERATION OPNUM
System action: The scheduler’s processing continues.
Explanation: OCL changed the jobname for operation
User response: None. OPNUM.
System action: The scheduler’s processing continues.
EQQCL0QI OPERATION OPNUM WAS
User response: None.
SUCCESSFULLY MODIFIED
Explanation: OCL modified the operation OPNUM.
EQQCL0XI DEFAULT OPERATION NUMBER IS
System action: The scheduler’s processing continues. USED: DEFOPNO
User response: None. Explanation: OCL uses DEFOPNO as the default
operation number.
EQQCL0RI DELETING THE SPECIAL RESOURCE System action: The scheduler’s processing continues.
FROM OPERATION OPNUM
User response: None.
Explanation: OCL is deleting the special resource
definition from operation OPNUM.
EQQCL0YI PREDECESSOR ADDED TO
System action: The scheduler’s processing continues. OPERATION OPNUM:
PREOPNO(PREOPNUM)
User response: None.
PREAPPL(PREAPPL)
Explanation: OCL added a new predecessor to
EQQCL0SI DELETING THE EXTERNAL
operation OPNUM. PREOPNUM is the predecessor
PREDECESSOR(S) FROM OPERATION
operation, and PREAPPL is the predecessor application
OPNUM
ID.
Explanation: OCL is deleting the external predecessors
System action: The scheduler’s processing continues.
from operation OPNUM.
User response: None.
System action: The scheduler’s processing continues.
User response: None.
EQQCL0ZI NEW DEPENDENCY CREATED FOR
OCCURRENCE APPL:
EQQCL0TI OPERATION STATUS WAS CHANGED PREAPPL(PREAPPL)
TO ’R’: OPNO(opnum)
Explanation: OCL added a new predecessor to
Explanation: OCL modified the status of operation operation OPNUM. PREAPPL is the predecessor
OPNUM. application ID.

System action: The scheduler’s processing continues. System action: The scheduler’s processing continues.

User response: None. User response: None.

EQQCL0UI EXTERNAL PREDECESSOR(S) WILL EQQCL10I PREDECESSOR DELETED:

BE DELETED FROM OPERATION PREOPNO(PREOPNUM)
opnum PREAPPL(PREAPPL) PREIA(IADT)

Explanation: OCL deletes all the external predecessors Explanation: OCL deleted a predecessor definition.
from operation OPNUM. PREOPNUM is the predecessor operation number,
PREAPPL is the occurrence ID, and IADT is the input
System action: The scheduler’s processing continues. arrival date and time.
User response: None. System action: The scheduler’s processing continues.
User response: None.
EQQCL0VI OCCURRENCE APPL IS NOW
STARTED
Explanation: OCL forced the occurrence appl to start.
System action: The scheduler’s processing continues.

Chapter 5. EQQCLnnn Messages 37

 System action: The scheduler’s processing continues.
EQQCL11I SPECIAL RESOURCE ADDED TO
OPERATION OPNUM: RES_NAME User response: None.
Explanation: OCL added a new special resource
definition to operation OPNUM. RES_NAME is the EQQCL17I INTERNAL SUCCESSOR FOUND FOR
name of the special resource. OPERATION OPNUM:
OPNO(S_OPNUM)
System action: The scheduler’s processing continues.
Explanation: OCL found an internal successor for
User response: None.
operation OPNUM. S_OPNUM is the successor
operation number.
EQQCL12I SPECIAL RESOURCE DELETED FROM
System action: The scheduler’s processing continues.
OPERATION OPNUM: RES_NAME
User response: None.
Explanation: OCL deleted a special resource definition
from operation OPNUM RES_NAME is the name of the
special resource. EQQCL18I EXTERNAL PREDECESSOR FOUND:
PREAPPL(APPL) PREIA(IADT)
System action: The scheduler’s processing continues.
Explanation: OCL found an external predecessor.
User response: None.
APPL is the predecessor occurrence ID, and IADT is its
input arrival date and time.
EQQCL13I SUCCESSOR RELEASED FROM
System action: The scheduler’s processing continues.
OPERATION OPNUM:
OPNO(S_OPNUM) APPL(APPL) User response: None.
Explanation: OCL deleted a successor dependency
definition from operation OPNUM. S_OPNUM is the EQQCL19I EXTERNAL PREDECESSOR FOUND:
successor operation number, and APPL is the successor PREOPNO(OPNUM) PREAPPL(APPL)
application ID. PREIA(IADT)
System action: The scheduler’s processing continues. Explanation: OCL found an external predecessor.
OPNUM is the predecessor operation number, APPL is
User response: None.
the predecessor occurrence ID and IADT is its input
arrival date and time.
EQQCL14I OPERATION P_OPNUM WAS
System action: The scheduler’s processing continues.
DEFINED AS AN INTERNAL
PREDECESSOR OF OPERATION User response: None.
OPNUM
Explanation: OCL added a new predecessor to EQQCL1AI N_OCC OCCURRENCES FOUND FOR
operation OPNUM. P_OPNUM is the predecessor APPLICATION APPL
operation number.
Explanation: OCL found N_OCC occurrences of
System action: The scheduler’s processing continues. application APPL in the current plan.
User response: None. System action: The scheduler’s processing continues.
User response: None.
EQQCL15I INTERNAL SUCCESSOR RELEASED:
OPNO(S_OPNUM) APPL(APPL)
EQQCL1BI OPERATION OPNUM WAS ADDED
Explanation: OCL released the internal successor TO OCCURRENCE APPL WITH IA
operation number S_OPNUM in the occurrence APPL. IADT
System action: The scheduler’s processing continues. Explanation: OCL added operation OPNUM to
occurrence APPL.
User response: None.
System action: The scheduler’s processing continues.
EQQCL16I EXTERNAL SUCCESSOR FOUND FOR User response: None.
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.

38 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 User response: None.
EQQCL1CI NUMBER OF NOT COMPLETED
OCCURRENCES: N_OCC
EQQCL41W PROCESS TERMINATED DUE TO A
Explanation: OCL found N_OCC occurrences that are
LABEL INSTRUCTION - HIGHEST
not in Complete status.
RC=LASTRC
System action: The scheduler’s processing continues.
Explanation: OCL processed a LABEL instruction.
User response: None.
System action: OCL processing is terminated with the
highest return code of the processed OCL instructions.
EQQCL1DI EXTERNAL PREDECESSOR DELETED:
User response: None.
PREAPPL(PREAPPL) PREIA(IADT)
Explanation: OCL deleted an external predecessor
EQQCL42W VARIABLE VARNAME WILL BE
definition. PREAPPL is the predecessor occurrence ID,
ADDED TO THE VARIABLE TABLE
and IADT its input arrival date and time.
VARTAB
System action: The scheduler’s processing continues.
Explanation: OCL processed an UPD or SETUPD
User response: None. instruction to modify the value of a variable that does
not exist in the scheduler’s variable table.
EQQCL1EI SPECIAL RESOURCE FOUND FOR System action: OCL adds the variable VARNAME to
OPERATION OPNUM: RES_NAME the variable table VARTAB. OCL processing continues.
Explanation: OCL found a special resource defined to User response: Verify that the variable name specified
operation OPNUM. RES_NAME is the name of the in the UPD or SETUPD instruction is correct.
special resource.
System action: The scheduler’s processing continues. EQQCL43W NO OCCURRENCE TO COMPLETE:
APPL
User response: None.
Explanation: OCL processed a COMPL instruction for
an application occurrence, but no occurrence in a
EQQCL3EI EXTNAME ADDED TO OP OPNUM
noncomplete status was found in the current plan.
OF OCC APPL WITH IA IADT
System action: OCL processing continues.
Explanation: OCL added extended name to operation
OPNUM of occurrence APPL with input arrival time User response: Verify that the selection parameters for
IADT. the application occurrence are correct.
System action: The schedulers processing continues.
EQQCL44W OCCURRENCE NOT FOUND IN THE
User response: None.
CURRENT PLAN: APPL(APPL)
IA(IADT)
| EQQCL3LI EXTNAME ADDED TO OP OPNUM
Explanation: OCL attempted to modify or list the
| OF OCC APPL WITH IA IADT
application occurrence APPL, which does not exist in
| Explanation: OCL added extended name to operation the current plan. IADT is the input arrival date and
| OPNUM of occurrence APPL with input arrival IADT. time used to search for the occurrence.

| System action: The schedulers processing continues. System action: OCL processing continues.

| User response: None. User response: Verify that the selection parameters are
correct.

EQQCL40W THE ROUTINE RETURNED RESULT

RETURN CODE EQQCL45W OCCURRENCE NOT FOUND IN THE
LTP: APPL(APPL) IA(IADT)
Explanation: The value of RESULT is the return code
of the routine. This message is issued when the return Explanation: OCL attempted to modify or list the
code is not zero. application occurrence APPL, which does not exist in
the long term plan (LTP). IADT is the input arrival date
System action: If the return code issued by the called and time used to search for the occurrence.
routine is higher than the highest return code of the
other processed OCL instructions, it is assumed as the System action: OCL processing continues.
highest return code.
User response: Verify that the selection parameters are
OCL processing continues. correct.

Chapter 5. EQQCLnnn Messages 39

 User response: None.
EQQCL46W ONLY OCL INSTRUCTIONS ARE
ACCEPTED: SYSIN_LINE
EQQCL4CW OPERATION OPNUM IS ALREADY IN
Explanation: A non-OCL instructions was specified
NOP STATUS
and the initialization parameter TSOCMD is set to NO.
Explanation: OCL issued a NOP command against an
System action: OCL processing continues.
operation that was already in NOP status.
User response: If you want to be able to specify TSO
System action: OCL processing continues.
commands or REXX instructions other than those of
OCL, set the TSOCMD parameter to YES. User response: None.

EQQCL47W OPER. NOT FOUND OR NOT IN EQQCL4DW EXTERNAL PREDECESSOR(S) FOUND,

ERROR: OPNUM APPL(APPL) IA(IADT) STATUS CANNOT BE CHANGED
Explanation: The application occurrences APPL with Explanation: OCL tried to set an operation to Ready
input arrival date and time IADT does not contain the status, but external predecessors are defined. OCL
selected operation or the selected operation is not in deletes the dependency definitions and tries to set the
error status. operation Ready again.
System action: OCL processing continues. System action: OCL processing continues.
User response: Verify that the selected operation really User response: None.
exists in the application occurrence.

EQQCL4EW OCCURRENCE APPL IS STILL IN

EQQCL48W ERROR CODE ERRCODE DOES NOT WAITING STATUS
MATCH ERRCODE() FOR OPERATION
OPNUM Explanation: OCL tried to force the application
occurrence to start, but it is still in Waiting status.
Explanation: ERRCODE is the error code specified in
the CHKAPPL instruction for operation OPNUM. OCL System action: OCL processing continues.
found the operation OPNUM in error status, but its User response: Verify the conditions that cause the
error code does not match ERRCODE. occurrence to wait. Check the current operation status
System action: OCL processing continues. and extended status, using the scheduler’s dialogs, to
determine more precisely why the application
User response: None. occurrence failed to start.

EQQCL49W OPERATION OPNUM IS NOT IN EQQCL4FW NO OPERATION FOUND TO BE

HOLD STATUS CHANGED
Explanation: OCL tried to release an operation that Explanation: OCL tried to change the jobname
was not manually held. associated with an operation in the current plan, but
the operation was not found.
System action: OCL processing continues.
System action: OCL processing continues.
User response: None.
User response: Verify that the selection parameters are
correct.
EQQCL4AW OPERATION OPNUM IS ALREADY IN
HOLD STATUS
EQQCL4GW PREDECESSOR APPLICATION NOT
Explanation: OCL tried to hold an operation that was
FOUND IN CP: PREAPPL(PREAPPL)
already in HOLD status.
PREIA(PREIADT)
System action: OCL processing continues.
Explanation: PREAPPL is the predecessor application
User response: None. 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
EQQCL4BW OPERATION OPNUM IS NOT IN NOP
occurrence specified in the APPL() keyword, but
STATUS
PREAPPL is not present in the current plan.
Explanation: OCL issued an UNNOP command
System action: OCL processing continues.
against an operation that was not in NOP status.
User response: Verify that the selection parameters are
System action: OCL processing continues.
correct.

40 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 User response: Verify the selection parameters.
EQQCL4HW OPERATION OPNUM DOESN’T
EXISTS
EQQCL4NW NO EXTERNAL PREDECESSOR
Explanation: OCL tried to change or delete an
FOUND FOR THE OCCURRENCE
operation that does not exist in the current plan.
APPL
System action: OCL processing continues.
Explanation: OCL tried to release the external
User response: Verify that the specified keywords are predecessors of occurrence APPL, but no predecessor is
correct. present in the current plan.
System action: OCL processing continues.
EQQCL4IW ALREADY PREDECESSOR:
User response: Verify the selection parameters.
PREOPNUM
Explanation: OCL tried to define a predecessor that is
EQQCL4OW NO SPECIAL RESOURCE FOUND
already defined.
Explanation: OCL tried to delete a special resource
System action: OCL processing continues.
definition, but no special resource is defined to the
User response: Verify that the specified keywords are operation.
correct.
System action: OCL processing continues.
User response: Verify the selection parameters.
EQQCL4JW PREDECESSOR NOT FOUND IN THE
LTP: PREAPPL(PREAPPL)
PREIA(PREIADT) EQQCL4PW NO OPERATION WAS MODIFIED
Explanation: OCL tried to define PREAPPL as a Explanation: OCL did not modify any operation in the
predecessor of the application occurrence specified in occurrence.
the APPL() keyword, but PREAPPL is not present in
the long term plan (LTP). System action: OCL processing continues.

System action: OCL processing continues. User response: Verify the selection parameters.

User response: Verify the selection parameters.

EQQCL4QW OPERATION OPNUM ALREADY
EXISTS
EQQCL4KW NO EXTERNAL SUCCESSOR FOUND
FOR THE OCCURRENCE APPL Explanation: OCL tried to add an operation that
already exists in the occurrence.
Explanation: OCL tried to release the external
successors of the occurrence APPL, but no successor System action: OCL processing continues.
was found for the occurrence. User response: Verify the selection parameters.
System action: OCL processing continues.
User response: None. EQQCL4RW OPERATION DEADLINE LATER
THAN OCCURRENCE DEADLINE -
ACCEPTED: DEADLINE
EQQCL4LW OPERATION OPNUM NOT FOUND:
APPL(APPL) IA(IADT) Explanation: The specified operation deadline is later
than the occurrence deadline, but is accepted.
Explanation: OCL tried to change operation OPNUM,
which does not exist in the current plan. System action: OCL processing continues.

System action: OCL processing continues. User response: Verify that the specified keywords are
correct.
User response: Verify the selection parameters.
EQQCL4SW OPERATION DEADLINE PRECEDES
EQQCL4MW NO INTERNAL SUCCESSOR FOUND OPERATION INPUT ARRIVAL -
FOR OPERATION OPNUM OF THE ACCEPTED: DEADLINE
OCCURRENCE APPL
Explanation: The operation deadline precedes the
Explanation: OCL tried to release the internal operation input arrival, but is accepted.
successors of operation OPNUM, but no successor was
found. System action: OCL processing continues.

System action: OCL processing continues. User response: Verify that the specified keywords are
correct.

Chapter 5. EQQCLnnn Messages 41

EQQCL4TW OPERATION INPUT ARRIVAL EQQCL51E NOT POSSIBLE TO READ THE OCL
PRECEDES OCCURRENCE - PARMLIB
ACCEPTED: IADT
Explanation: OCL was not able to read the
Explanation: The operation input arrival precedes the EQQYRPRM member in the OCL library.
occurrence input arrival, but is accepted.
System action: OCL processing is terminated.
System action: OCL processing continues.
User response: Verify the data set name specified in
User response: Verify that the specified keywords are the OCLPARM ddname.
correct.
EQQCL52E NOT POSSIBLE TO READ THE SYSIN
EQQCL4UW DEPENDENCY ALREADY DEFINED CARD
Explanation: OCL tried to define a predecessor that is Explanation: OCL was not able to read the SYSIN
already defined. DD-card.
System action: OCL processing continues. System action: OCL processing is terminated.
User response: Verify that the specified keywords are User response: Verify the data set specified in the
correct. EQQOCL.SYSIN DD-card.

EQQCL4VW NO PARAMETER WAS SPECIFIED EQQCL53E INVALID SYNTAX: INSTRUCTION

Explanation: No parameter was specified for the Explanation: An invalid instruction was specified in
MODOP instruction. No change is required for the the OCL SYSIN.
operation.
System action: OCL terminates
System action: OCL processing continues.
User response: Correct the instruction and resubmit
User response: Verify the selection parameters. the job.

EQQCL4WW OCCURRENCE ALREADY IN EQQCL54E NOT POSSIBLE TO WRITE THE

COMPLETE STATUS: APPL WITH IA CONTROL CARDS FOR EQQPIFT
IADT PROGRAM
Explanation: OCL tried to complete an occurrence that Explanation: OCL was not able to write the input
was already completed. control cards for the EQQPIFT program.
System action: OCL processing continues. System action: OCL terminates
User response: Verify the selection parameters. User response: Contact Customer Support.

EQQCL4XW OCCURRENCE NOT FOUND IN THE EQQCL55E ERROR DURING THE GETMAIN
CURRENT PLAN: APPL(APPL) REQUEST
Explanation: No occurrence exists in the current plan Explanation: OCL was not able to get the storage for
for application APPL. the PIF session.
System action: OCL processing continues. System action: OCL processing is terminated.
User response: Verify the selection parameters. User response: Contact Customer Support.

EQQCL50E NOT POSSIBLE TO READ THE OCL EQQCL56E PIF INITIALIZATION FAILED FOR
MLIB SUBSYSTEM SUBSYS
Explanation: OCL was not able to read the data set Explanation: OCL was not able to initialize the
referenced by the OCLMLIB DD-card. scheduler’s PIF session.
System action: OCL processing is terminated. System action: OCL processing is terminated.
User response: Verify the data set name specified in User response: Check the scheduler’s subsystem name
the OCLMLIB DD-card. specified in the PARMLIB SUBSYS() parameter or in
the INIT instruction. If the subsystem name is correct
and if the subsystem is active, contact Customer
Support.

42 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQCL57E VARIABLE NAME IS MISSING EQQCL5DE INVALID OPERAND FOR THE PIF
REQUEST: OPERAND
Explanation: The variable name was not specified in
the UPD or SETUPD instruction. Explanation: A PIF request contained an invalid
operand.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Correct the instruction and resubmit
the job User response: Verify that the length of operand is
specified in the SETSTEMS subroutine in the OCL
program.
EQQCL58E PIF TERM REQUEST FAILED
Explanation: OCL was not able to terminate the
EQQCL5EE NOT POSSIBLE TO COMPLETE THE
scheduler’s PIF session.
OCCURRENCE APPL WITH IA IADT
System action: OCL processing is terminated.
Explanation: OCL was not able to complete the
User response: Contact Customer Support. occurrence APPL.
System action: OCL processing is terminated.
EQQCL59E PIF TERM REQUEST FAILED: ERROR
User response: Contact Customer Support.
DURING FREEMAIN
Explanation: OCL was not able to terminate the
EQQCL5FE NOT POSSIBLE TO MODIFY THE
scheduler’s PIF session.
OCCURRENCE APPL WITH IA IADT
System action: OCL processing is terminated.
Explanation: OCL was not able to modify the
User response: Contact Customer Support. occurrence APPL in the current plan.
System action: OCL processing is terminated.
EQQCL5AE PREDECESSOR CAN’T BE EQUAL TO
User response: Contact Customer Support.
THE OPERATION TO BE ADDED
Explanation: OCL was requested to add a new
EQQCL5GE CANNOT COMPLETE OPERATION
operation in an application occurrence, but the
OPNUM of occurrence appl with IA
operation number is equal to its internal predecessor
IADT
operation number.
Explanation: OCL was not able to complete the
System action: OCL processing is terminated.
operation OPNUM in the occurrence APPL with input
User response: If you have specified the DEFOPNO arrival time IADT.
initialization parameter, OCL uses it as a default
System action: OCL processing is terminated.
predecessor operation number. You cannot add an
operation with a number equal to DEFOPNO. User response: Verify if the operation has external
predecessors.
EQQCL5BE NO CURRENT PLAN EXISTS
EQQCL5HE REQUIRED KEYWORD(S) MISSING
Explanation: OCL cannot add or modify occurrences
because the current plan does not exist. Explanation: A required keyword was not specified in
the instruction.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Extend the current plan and resubmit
the job. User response: Correct the instruction and resubmit
the job.
EQQCL5CE NO DEFAULT VALUE FOR VARIABLE
VARNAME EQQCL5IE APPL AND GROUP ARE MUTUALLY
EXCLUSIVE KEYWORDS
Explanation: OCL did not find a value for variable
VARNAME. Explanation: APPL and GROUP keywords were
specified in the same ADD instruction.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Verify that a SET or SETUPD
instruction was specified to set the variable value. User response: Correct the instruction and resubmit
the job.

Chapter 5. EQQCLnnn Messages 43

 User response: Correct the instruction and resubmit
EQQCL5JE OPC SUBSYSTEM ID MUST BE
the job.
SUPPLIED
Explanation: The scheduler’s subsystem ID was not
EQQCL5PE WORKSTATION ID MUST BE
specified.
SPECIFIED
System action: OCL processing is terminated.
Explanation: Workstation ID is a required keyword for
User response: Specify the subsystem ID in the the instruction.
SUBSYS initialization parameter (EQQYRPRM member
System action: OCL processing is terminated.
in the OCL library) or in the INIT instruction.
User response: Correct the instruction and resubmit
the job.
EQQCL5KE NO APPLICATION FOUND FOR THE
GROUP APPLGRP
EQQCLQE WORKSTATION WSNAME NOT
Explanation: OCL tried to add the application group
FOUND IN THE OPC DATABASE
APPLGRP, but no application was defined to the group.
Explanation: Workstation WSNAME is not defined in
System action: OCL processing is terminated.
the scheduler’s Workstation database.
User response: Verify the application group ID.
System action: OCL processing is terminated.
User response: Correct the instruction and resubmit
EQQCL5LE NOT POSSIBLE TO ADD THE
the job.
OCCURRENCE APPL
Explanation: OCL was not able to add the occurrence
EQQCL5RE JOBNAME MUST BE SPECIFIED FOR
APPL.
WORKSTATION WSNAME
System action: OCL processing is terminated.
Explanation: Workstation WSNAME requires the
User response: Contact Customer Support. jobname (job-setup, computer, or printer)
System action: OCL processing is terminated.
EQQCL5ME NOT POSSIBLE TO USE AN IA DATE
User response: Correct the instruction and resubmit
OTHER THAN THE ACTUAL DATE
the job.
Explanation: OCL tried to add an occurrence in the
current or long term plan. An occurrence with the same
EQQCL5SE DATE1 AND DATE2 ARE MUTUALLY
input arrival (IA) already existed, so OCL tried to
EXCLUSIVE KEYWORDS
increment the input arrival time by 1 minute. An error
occurs if the occurrence input arrival time is 23:59. Explanation: You cannot use DATE1 and DATE2
keywords in the same CHKDATE instruction.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Specify an input arrival time other
than 23:59 for the occurrence to be added. User response: Correct the instruction and resubmit
the job.
EQQCL5NE NOT POSSIBLE TO ADD THE
OCCURRENCE WITH IA IADT EQQCL5TE INTERNAL PREDECESSOR DOESN’T
EXIST: PREOPNUM
Explanation: OCL was not able to add the occurrence
with IA IADT. Explanation: OCL tried to add an internal predecessor
that does not exist.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Verify if the occurrence input arrival
date and time is later than the long term plan end time. User response: Check that the PREOPNUM() keyword
refers to an existing operation number. If it does not,
correct the instruction and resubmit the job. If the
EQQCL5OE OPERATION NUMBER MUST BE
PREOPNUM() keyword is not specified, OCL uses the
SPECIFIED
default operation number (initialization parameter
Explanation: The operation number is a required DEFOPNO) as the internal predecessor operation.
keyword for the instruction. Verify that the application contains an operation with
the number equal to the number specified in the
System action: OCL processing is terminated.
DEFOPNO parameter.

44 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQCL5UE INCVALUE VALUE CAN’T BE EQQCL5ZE NOT POSSIBLE TO REMOVE THE
GREATER THAN 30 OCCURRENCE FROM THE
APPLICATION GROUP
Explanation: The value of INCVALUE must be in the
range 1–30. Explanation: OCL tried to remove an occurrence from
the application group before deleting it from the
System action: OCL processing is terminated.
current plan or from the long term plan, but a problem
User response: Specify a correct INCVALUE and occurred.
resubmit the job.
System action: OCL processing is terminated.
User response: Contact Customer Support.
EQQCL5VE THE OPERATION INPUT ARRIVAL
MUST BE IN THE YYMMDDHHMM
FORMAT EQQCL60E NOT POSSIBLE TO DELETE
OCCURRENCE APPL WITH IA IADT
Explanation: OCL found an invalid operation input
arrival date and time. Explanation: OCL tried to delete the occurrence APPL,
but a problem occurred.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Correct the instruction and resubmit
the job. User response: Contact Customer Support.

EQQCL5WE THE OPERATION DEADLINE MUST EQQCL61E NOT POSSIBLE TO DELETE

BE IN THE YYMMDDHHMM OPERATION OPNUM OF
FORMAT OCCURRENCE APPL
Explanation: OCL found an invalid operation deadline Explanation: OCL tried to delete operation OPNUM
date and time. from the occurrence APPL, but a problem occurred.
System action: OCL processing is terminated. System action: OCL processing is terminated.
User response: Correct the instruction and resubmit User response: Contact Customer Support.
the job.
EQQCL62E DATE MUST BE SUPPLIED
EQQCL5XE NOT POSSIBLE TO ADD THE
Explanation: A date must be supplied in the
OPERATION OPNUM IN
CHKDATE instruction.
OCCURRENCE APPL
System action: OCL processing is terminated.
Explanation: OCL tried to insert a new operation in
the application occurrence APPL, but a problem User response: Use the DATE1 or DATE2 keyword
occurred. according with the format of the date and resubmit the
job.
System action: OCL processing is terminated.
User response: Verify if the operation OPNUM
EQQCL63E DATE NOT VALID: DATE LENGTH
already existed in the occurrence. Refer to the error
CANNOT BE > 10
messages in the scheduler’s message log.
Explanation: An invalid date was specified in the
CHKDATE instruction. Valid date formats are
EQQCL5YE NOT POSSIBLE TO DEFINE
YYMMDD, YY/MM/DD, YYYYMMDD,
INTERNAL PRED. PREOPNUM TO
YYYY/MM/DD, DDMMYY, DD/MM/YY,
OPERATION OPNUM
DDMMYYYY, and DD/MM/YYYY.
Explanation: OCL tried to define an internal
System action: OCL processing is terminated.
predecessor to operation OPNUM, but a problem
occurred. User response: Correct the date and resubmit the job.
System action: OCL processing is terminated.
EQQCL64E DATE NOT VALID: DATE LENGTH
User response: Contact Customer Support.
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,

Chapter 5. EQQCLnnn Messages 45

DDMMYYYY, and DD/MM/YYYY. the month specified in the input date.
System action: OCL processing is terminated. System action: OCL processing is terminated.
User response: Correct the date and resubmit the job. User response: Correct the date and resubmit the job.

EQQCL65E DATE NOT VALID: FORMAT NOT EQQCL6BE OCCURRENCE NAME CAN’T BE ’*’
RECOGNIZED
Explanation: An invalid occurrence ID was specified.
Explanation: An invalid date was specified in the
System action: OCL processing is terminated.
CHKDATE instruction. Valid date formats are
YYMMDD, YY/MM/DD, YYYYMMDD, User response: Correct the APPL keyword and
YYYY/MM/DD, DDMMYY, DD/MM/YY, resubmit the job.
DDMMYYYY, and DD/MM/YYYY.
System action: OCL processing is terminated. EQQCL6CE ALERT PARAMETER CAN BE YES OR
NO
User response: Correct the date and resubmit the job.
Explanation: An invalid ALERT keyword was
specified.
EQQCL66E DATE NOT VALID: IT’S NOT IN THE
YYYYMMDD FORMAT System action: OCL processing is terminated.
Explanation: The date supplied is not in the User response: Correct the instruction and resubmit
YYYYMMDD format. the job.
System action: OCL processing is terminated.
EQQCL6DE USER ID MUST BE SPECIFIED FOR
User response: Correct the date and resubmit the job.
ALERTING
Explanation: The USER keyword is required with
EQQCL67E YEAR YEAR MUST BE INCLUDED
ALERT(YES).
BETWEEN 1996 AND 2999
System action: OCL processing is terminated.
Explanation: The date specified in the CHKDATE
instruction is outside the valid range 1996–2999. User response: Correct the instruction and resubmit
the job.
System action: OCL processing is terminated.
User response: Correct the date and resubmit the job.
EQQCL6EE NOT POSSIBLE TO ISSUE THE WTO
Explanation: OCL tried to invoke the IPOWTO
EQQCL68E MONTH MONTH MUST BE
program, but a problem occurred.
INCLUDED BETWEEN 01 AND 12
System action: OCL processing is terminated.
Explanation: The date specified in the CHKDATE
instruction is invalid; it is not in the range 01–12. User response: Make sure that the IPOWTO program
is available to OCL and resumbit the job.
System action: OCL processing is terminated.
User response: Correct the date and resubmit the job.
EQQCL6FE INVALID CMD COMMAND
Explanation: CMD can be only SRSTAT, OPSTAT, or
EQQCL6AE STATUS INVALID: IT CAN BE: C, E, D,
WSSTAT.
P, S, U OR W
System action: OCL processing is terminated.
Explanation: An invalid occurrence status was
specified in the CHKAPPL instruction. User response: Correct the instruction and resubmit
the job.
System action: OCL processing is terminated.
User response: Correct the instruction and resubmit
EQQCL6GE VARIABLE TABLE NOT FOUND IN
the job.
OPC DATABASE
Explanation: The variable table specified in the INIT
EQQCL69E DAY DAY MUST BE INCLUDED
instruction does not exist in the scheduler’s database.
BETWEEN 01 AND LAST_DAY
System action: OCL processing is terminated.
Explanation: The date specified in the CHKDATE
instruction is invalid. The value of day DAY must be in User response: Specify a valid variable table in the
the range 01–LAST_DAY. LAST_DAY is the last day of INIT instruction and resubmit the job.

46 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 User response: Specify the OPNO keyword or the
EQQCL6HE INTERNAL SUCCESSOR OPERATION
default operation number in the initialization parameter
NOT FOUND: S_OPNUM
DEFOPNO.
Explanation: OCL tried to release an internal
successor, but a problem occurred. S_OPNUM is the
EQQCL6NE NOT POSSIBLE TO MODIFY THE
successor operation number.
OPERATION STATUS: OPNO(OPNUM)
System action: OCL processing is terminated.
Explanation: OCL tried to modify the status of
User response: Contact Customer Support. operation OPNUM, but a problem occurred.
System action: OCL processing is terminated.
| EQQCL6IE NOT POSSIBLE TO EXECUTE
User response: Contact Customer Support.
| EQQPIFT PROGRAM
| Explanation: OCL could not run the EQQPIFT
EQQCL6OE NEW JOBNAME IS BLANK
| program.
Explanation: The NEWJOB keyword was not specified
| System action: OCL processing is terminated.
in the CHGJOB instruction.
| User response: Make sure that the EQQPIFT load
System action: OCL processing is terminated.
| module is available to OCL and resubmit the job.
User response: Correct the instruction and resubmit
the job.
EQQCL6JE NEW JOBNAME INVALID OR
MISSING
EQQCL6PE NOT POSSIBLE TO CHANGE THE
Explanation: A valid NEWJOB keyword must be
JOBNAME
specified in the CHGJOB instruction.
Explanation: OCL tried to change the jobname of an
System action: OCL processing is terminated.
operation, but a problem occurred.
User response: Specify a valid NEWJOB keyword and
System action: OCL processing is terminated.
resubmit the job.
User response: Contact Customer Support.
EQQCL6KE CANNOT LIST THE WORKSTATIONS
EQQCL6QE PREDECESSOR OPERATION NOT
Explanation: OCL tried to list the workstations
FOUND: PREOPNUM
defined in the scheduler’s Workstation database, but a
problem occurred. Explanation: OCL tried to add a predecessor that does
not exist
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Contact Customer Support.
User response: Verify the PREOPNO keyword or the
initialization parameter DEFPREOPNO. Correct the
EQQCL6LE NOT POSSIBLE TO MODIFY
instruction and resubmit the job.
OPERATION OPNUM OF
OCCURRENCE APPL
EQQCL6RE NOT POSSIBLE TO MODIFY THE
Explanation: OCL tried to modify operation OPNUM
OPERATION OPNUM
in the occurrence APPL, but a problem occurred.
Explanation: OCl tried to modify operation OPNUM,
System action: OCL processing is terminated.
but a problem occurred.
User response: Refer to the messages in the
System action: OCL processing is terminated.
scheduler’s message log and contact Customer Support.
User response: Contact Customer Support.
EQQCL6ME SPECIFY THE OPNO() KEYWORD OR
SPECIFY THE DEFAULT OPERATION EQQCL6SE CAN’T DEFINE THE PRED. FOR
NUMBER OPERATION OPNUM:
PREOPNO(P_OPNUM) APPL(P_APPL)
Explanation: The OPNO keyword is not specified.
OCL tried to use the default operation number, which Explanation: OCL tried to add a new predecessor to
is not specified in the initialization parameter operation OPNUM.
DEFOPNO. P_OPNUM
The predecessor operation number
System action: OCL processing is terminated.

Chapter 5. EQQCLnnn Messages 47

P_APPL
EQQCL6YE SPECIAL RESOURCE USAGE MUST
The predecessor occurrence ID.
BE SUPPLIED
System action: OCL processing is terminated.
Explanation: RESUSAGE is a required keyword.
User response: Contact Customer Support.
System action: OCL processing is terminated.
User response: Correct the instruction and resubmit
EQQCL6TE CAN’T HAVE A DEPENDENCY ON
the job.
ITSELF: PREAPPL(P_APPL)
PREIA(IADT)
EQQCL6ZE ONERROR ACTION CAN BE Y OR N
Explanation: In the long term plan, an occurrence
cannot have a predecessor with the same occurrence ID Explanation: An invalid ONERROR keyword was
and input arrival date and time. specified.
System action: OCL processing is terminated. System action: OCL processing is terminated.
User response: Correct the instruction and resubmit User response: Correct the instruction and resubmit
the job. the job.

EQQCL6UE NOT POSSIBLE TO CREATE A NEW EQQCL70E NOT POSSIBLE TO ADD THE
DEPENDENCY: PREAPPL(PREAPPL) SPECIAL RESOURCE:
RESNAME(RES_NAME)
Explanation: OCl tried to define a new dependency in
an application occurrence in the long term plan, but a Explanation: OCL tried to add the special resource
problem occurred. RES_NAME, but a problem occurred.
System action: OCL processing is terminated. System action: OCL processing is terminated.
User response: Contact Customer Support. User response: Refer to the messages in the
scheduler’s message log and contact Customer Support.
EQQCL6VE OPERATION NOT FOUND: OPNUM
EQQCL71E OPNO() AND EXCLOP() ARE
Explanation: Operation OPNUM does not exist in the
MUTUALLY EXCLUSIVE KEYWORDS
occurrence to be modified.
Explanation: OPNO and EXCLOP are mutually
System action: OCL processing is terminated.
exclusive keywords.
User response: Verify the OPNO keyword or the
System action: OCL processing is terminated.
default operation number in the initialization parameter
DEFOPNO. Correct the instruction and resubmit the User response: Correct the instruction and resubmit
job. the job.

EQQCL6WE NOT POSSIBLE TO DELETE THE EQQCL72E CAN’T RELEASE THE SUCCESSOR OF
DEPENDENCY DEFINITION OPERATION OPNUM: APPL(S_APPL)
OPNO(S_OPNUM)
Explanation: OCL tried to delete a predecessor, but a
problem occurred. Explanation: OCL tried to release an external
successor of operation OPNUM, but a problem
System action: OCL processing is terminated.
occurred.
User response: Contact Customer Support.
System action: OCL processing is terminated.
User response: Correct the instruction and resubmit
EQQCL6XE SPECIAL RESOURCE NAME MUST BE
the job.
SUPPLIED
Explanation: RESNAME is a required keyword.
EQQCL73E YOU CAN SPECIFY ONLY ONE
System action: OCL processing is terminated. OPERATION NUMBER

User response: Correct the instruction and resubmit Explanation: Only one operation number is accepted
the job. in the OPNO keyword.
System action: OCL processing is terminated.
User response: Correct the instruction and resubmit
the job.

48 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQCL74E DEFAULT OPERATION NUMBER IS EQQCL79E CAN’T DELETE THE SPECIAL
NOT SPECIFIED (DEFOPNO RESOURCE: RES_NAME
PARAMETER) OPNO(OPNUM)
Explanation: OCL is trying to release an internal Explanation: OCL tried to delete the special resource
successor. OCL would use the default operation RES_NAME from the operation OPNUM.
number as an internal predecessor of this operation,
System action: OCL processing is terminated.
but the default operation number was not specified in
the DEFOPNO parameter of the OCL PARMLIB. User response: Contact Customer Support.
System action: OCL processing is terminated.
EQQCL7AE OCCURRENCE ID MUST BE
User response: Specify the DEFOPNO parameter in
SUPPLIED
the OCL PARMLIB.
Explanation: APPL is a required keyword.
EQQCL75E OPNO() CANNOT BE EQUAL TO System action: OCL processing is terminated.
DEFOPNO INITIALIZATION
PARAMETER: OPNUM User response: Correct the instruction and resubmit
the job.
Explanation: OCL is trying to release an internal
successor of operation OPNUM. It would use the
default operation number as an internal predecessor of EQQCL7BE OPC CALENDAR NOT FOUND: CAL
this operation, but the value of OPNO must not be the Explanation: The calendar CAL was not found in the
same as the default operation number. scheduler’s Calendar database.
System action: OCL processing is terminated. System action: OCL processing is terminated.
User response: Correct the instruction and resubmit User response: Correct the instruction anden resubmit
the job. the job.

EQQCL76E REQUIRED KEYWORD(S) MISSING. EQQCL7CE SPECIFY THE PREOPNO() KEYWORD

SPECIFY THE INIT INSTRUCTION OR THE DEFAULT OPERATION
Explanation: The variable table or the scheduler’s NUMBER
subsystem name was not supplied. Explanation: OCL is adding a new operation in an
System action: OCL processing is terminated. application occurrence. It tried to define the internal
predecessor of this operation, but either the PREOPNO
User response: Specify the INIT instruction before the keyword or the default operation number was not
UPD or SETUPD instructions and resubmit the job. specified.
System action: OCL processing is terminated.
EQQCL77E CAN’T DEFINE THE DEFAULT
OPERATION NUMBER OPNUM AS A User response: Specify the PREOPNO keyword or the
PREDECESSOR OF S_OPNUM default operation number in the OCL PARMLIB.

Explanation: OCL tried to add the default operation

number OPNUM as a predecessor of S_OPNUM. EQQCL7DE DATE IS BLANK
S_OPNUM is the internal successor to be released by Explanation: OCL tried to determine whether an input
the RELOP instruction. date corresponds to a free day, but the date is blank.
System action: OCL processing is terminated. System action: OCL processing is terminated.
User response: Correct the instruction and resubmit User response: Contact Customer Support.
the job.

EQQCL7EE VALID VALUES FOR OPCVER ARE 1

EQQCL78E CAN’T RELEASE THE SUCCESSOR AND 2
OPERATION: S_OPNUM
Explanation: The initialization parameter OPCVER is
Explanation: OCL tried to release an internal not either 1 or 2.
successor, but a problem occurred.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Correct the parameter and resubmit
User response: Contact Customer Support. the job.

Chapter 5. EQQCLnnn Messages 49

EQQCL7FE NOT POSSIBLE TO ALLOCATE EQQCL7LE NOT POSSIBLE TO RESOLVE
DATASET: DSNAME(WTOIN) DEPENDENCIES
Explanation: OCL tried to allocate the member Explanation: OCL can not handle versioning and
WTOIN in the data set DSNAME, but a problem dependencies resolution at the same time.
occurred.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Contact Customer Support.
User response: Contact Customer Support.
EQQCLNLE EXTENDED JOB NAME LENGTH
EQQCL7GE VALID VALUES FOR TSOCMD INVALID
PARAMETER ARE YES AND NO
Explanation: The Extended Job Name length must be
Explanation: The initialization parameter TSOCMD is maximum of 54 characters .
not either YES or NO.
System action: OCL processing is terminated.
System action: OCL processing is terminated.
User response: Correct the Extended Job Name length
User response: Correct the parameter and resubmit and resubmit the job.
the job.
EQQCL7LE NOT POSSIBLE TO RESOLVE
EQQCL7HE NOT POSSIBLE TO WRITE THE DEPENDENCIES
MESSAGE ON DATASET:
Explanation: OCL can not handle versioning and
DSNAME(WTOIN)
dependencies resolution at the same time.
Explanation: OCL tried to write the message text of
System action: OCL processing is terminated.
the WTOR in the member WTOIN of data set
DSNAME, but a problem occurred. User response: Contact Customer Support.
System action: OCL processing is terminated.
EQQCL7NE EXTENDED JOB NAME LENGTH
User response: Contact Customer Support.
INVALID
Explanation: The Extended Job Name length must be
EQQCL7IE INVALID PARAMETER OR INVALID
maximum of 54 characters.
VALUE FOR PARAMETER: PREOPNO
System action: OCL processing is terminated .
Explanation: An invalid parameter was specified in
the MODOP instruction. User response: Correct the Extended Job Name length
and resubmit the job.
System action: OCL processing is terminated.
User response: Correct the instruction and resubmit
EQQCL7OE NOT POSSIBLE TO MODIFY
the job.
EXTENDED JOB NAME EXTNAM
Explanation: OCL was not able to add or modify the
EQQCL7JE NOT POSSIBLE TO MODIFY THE
Extended Job Name in the current plan .
OCCURRENCE APPL
System action: OCL processing is terminated.
Explanation: OCL tried to modify the occurrence
APPL, but a problem occurred. User response: Contact Customer Support.
System action: OCL processing is terminated.
User response: Contact Customer Support.

EQQCL7KE CANNOT UPDATE THE LOG

DATASET
Explanation: OCL tried to write a new record in the
log data set, but a problem occurred.
System action: OCL processing is terminated.
User response: Contact Customer Support.

50 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

Chapter 6. EQQCNnnn Messages
EQQCN00I START CLEANUP/RC SIMULATION EQQCN04I PROGR STEPNAME PROCNAME
PROCESS USERCODE
Explanation: EQQCLEAN stand-alone data set Explanation: EQQCLEAN stand-alone data set
cleanup and return code simulation process has been cleanup and return code simulation process simulated
started USERCODE user code for stepname STEPNAME
procstepname PROCNAME step number PROGR.
System action: Cleanup and return code simulation
process continues. System action: Cleanup and return code simulation
process continues.
User response: None.
User response: None.
EQQCN01E STEP NUMBER AND STEP NAME
DON’T MATCH EQQCN05I PROGR STEPNAME PROCNAME
FLUSH
Explanation: The EQQCLEAN stand-alone data set
cleanup and return code simulation process detected a Explanation: EQQCLEAN stand-alone data set
mismatch between the JCL executed and the step list cleanup and return code simulation process simulated a
specified in EQQSIMRC DD. FLUSH for stepname STEPNAME procstepname
PROCNAME step number PROGR.
System action: Cleanup and return code simulation
process ends in error. System action: Cleanup and return code simulation
process continues.
User response: The content of the EQQSIMRC DD or
some JCL lines might have been modified manually User response: None.
after the restart and cleanup process analyzed and
created the submitted JCL. If nobody modified the JCL,
EQQCN06E INVALID PARAMETER IN SYSIN,
contact your System Programmer
PROCESS TERMINATED
System programmer response: Save the JCL and the
Explanation: EQQCLEAN stand-alone data set
message log, then contact Customer Support.
cleanup and return code simulation process received an
invalid parameter.
EQQCN02I PROGR STEPNAME PROCNAME RC
System action: Cleanup and return code simulation
Explanation: EQQCLEAN stand-alone data set process ends in error.
cleanup and return code simulation process simulated
User response: The content of the EQQCLEAN step
RC return code for stepname STEPNAME
might have been modified manually after the restart
procstepname PROCNAME step number PROGR.
and cleanup process analyzed and created the
System action: Cleanup and return code simulation submitted JCL. If nobody modified the JCL, contact
process continues. your System Programmer
User response: None. System programmer response: Save the JCL and the
message log, then contact Customer Support.
EQQCN03I PROGR STEPNAME PROCNAME
ABEND EQQCN07E ERROR IN SVC 26, PROCESS
TERMINATED
Explanation: EQQCLEAN stand-alone data set
cleanup and return code simulation process simulated Explanation: The EQQCLEAN stand-alone data set
ABEND ABEND code for stepname STEPNAME cleanup and return code simulation process kept an
procstepname PROCNAME step number PROGR. error during a SVC 26 operation while checking catalog
information for a data set.
System action: Cleanup and return code simulation
process continues. System action: The cleanup and return code
simulation process ends in error.
User response: None.
Problem determination: Review the JCL message log
data set and the SYSMDUMP data set to determine the
cause of the problem.

© Copyright IBM Corp. 1991, 2003 51

User response: Contact your system programmer. data set to determine the cause of the problem.
System programmer response: If the problem persists User response: Contact your system programmer.
contact Customer support.
EQQCN12I ACTION DEVTYPE DSNAME
EQQCN08E ERROR IN MACRO OBTAIN,
Explanation: The EQQCLEAN stand-alone data set
PROCESS TERMINATED
cleanup and return code simulation process did the
Explanation: The EQQCLEAN stand-alone data set ACTION action on data set DSNAME stored in a
cleanup and return code simulation process kept an DEVTYPE device type.
error during an obtain macro.
System action: Cleanup and return code simulation
System action: The cleanup and return code process continues.
simulation process ends in error.
User response: None.
Problem determination: Review the JCL message log
data set and the SYSMDUMP data set to determine the
EQQCN13I DEL DEVTYPE DSNAME VIA RMM
cause of the problem.
Explanation: The EQQCLEAN stand-alone data set
User response: Contact your system programmer.
cleanup and return code simulation process deletes
System programmer response: If the problem persists data set DSNAME stored on device type DEVTYPE
contact Customer support. using RMM services.
System action: Cleanup and return code simulation
EQQCN09E ERROR IN HSM CALL, PROCESS process continues.
TERMINATED
User response: None.
Explanation: The EQQCLEAN stand-alone data set
cleanup and return code simulation process kept an
EQQCN14E ERROR IN DATA SET CLEANUP: JOB
error asking information to HSM.
STOPPED
System action: The cleanup and return code
Explanation: The EQQCLEAN stand-alone data set
simulation process ends in error.
cleanup and return code simulation process was not
Problem determination: Review the JCL message log able to perform one or more cleanup actions.
data set and the SYSMDUMP data set to determine the
System action: Cleanup and return code simulation
cause of the problem.
process ends in error.
User response: Contact your system programmer.
Problem determination: Review the JCL message log
System programmer response: If the problem persists data set to determine the cause of the problem.
contact Customer support.
User response: Contact your system programmer.

EQQCN10I DEL DEVTYPE DSNAME VIA HSM

EQQCN15I ERROR IN RMM MACRO RET-CODE:
Explanation: The EQQCLEAN stand-alone data set RETURN_CODE REASON:
cleanup and return code simulation process deletes REASON_CODE
data set DSNAME stored on device type DEVTYPE
Explanation: An error occurred during the RMM
using HSM services.
interface process.
System action: Cleanup and return code simulation
System action: Cleanup and return code simulation
process continues
process ends in error.
User response: None.
User response: Contact your system programmer.

EQQCN11I TSO/E MESSAGE: MSGCODE IN

EQQCN16I ALREADY DELETED DSNAME
ACTION PROCESS
Explanation: The EQQCLEAN stand-alone data set
Explanation: The EQQCLEAN stand-alone data set
cleanup and return code simulation process tried to
cleanup and return code simulation process kept a
delete the DSNAME data set but it does not exist. The
return code RC performing ACTION using IDCAMS
data set was probably deleted manually.
services
System action: Cleanup and return code simulation
System action: Cleanup and return code simulation
process continues.
process ends in error.
User response:
Problem determination: Review the JCL message log

52 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQCN17I VOLSER
Explanation: The EQQCLEAN process sends this
message that follows EQQCN12I. It contains the volser
name involved in the cleanup operation.
System action: Cleanup and return code simulation
process continues.
User response: None.

EQQCN19E INVALID SYSIN INPUT: SYSINREC

Explanation: EQQCLEAN program (used for cleanup
and/or return code simulation) has invalid sysin input
data: SYSINREC.
System action: Cleanup and return code simulation
process ends in error and job fails.
User response: The content of EQQSIMRC or
EQQSIMxx DD was incorrectly built by the scheduler.
Contact system administrator.
System programmer response: Save the jcl and the
message log and contact Customer Support.

EQQCN20I EXIT IGNORED DATA SET: dsname

Explanation: The EQQCLEAN program invoked the
user exit EQQUXCAT before executing the cleanup
action for the data set specified by dsname. EQQUXCAT
checked the data set and decided that no action should
be done.
System action: No cleanup action is taken for the
specified data set.
User response: None.

EQQCN21I CLEAN UP DETAILS FOLLOW: details

Explanation: EQQCLEAN program was used by
scheduler to execute clean up and /or restart action.
The variable details will contain all the IDCAMS
messages related to this action.
System action: If an error is detected clean up action
fails otherwise the process continues.
System programmer response: Check the IDCAMS
messages to understand if there was a problem.
User response: None.

EQQCN99I END PROCESS

Explanation: The EQQCLEAN stand-alone data set
cleanup and return code simulation process ends.
System action: None.
User response: None.

Chapter 6. EQQCNnnn Messages 53

54 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 7. EQQDnnn Messages
EQQD000E YOU DO NOT HAVE AUTHORITY TO EQQD008E THE EXTENSION TIME SPECIFIED
ACCESS THE CURRENT PLAN DATA MAY NOT BE > 21 DAYS OR 504
SET HOURS
Explanation: None. Explanation: The extension time that you specified is
greater than 21 days (504 hours), the maximum allowed
extension time.
EQQD001E INVALID VALUE SPECIFIED FOR
REPORT SELECTION System action: The system waits for you to respond.
Explanation: Data entry error; see “Data Entry Errors” User response: Enter a valid extension time.
on page 2.
If you want a report, you must specify a Y. If you do EQQD009E A MINUTE VALUE GREATER THAN
not want a report, you must specify an N. 60 IS NOT ALLOWED
Explanation: Data entry error; see “Data Entry Errors”
EQQD002E START AND END DATES MUST NOT on page 2.
BE THE SAME
Explanation: Data entry error; see “Data Entry Errors” EQQD010E EXTENSION TIME MUST BE IN THE
on page 2. FORM HHHMM
Explanation: Data entry error; see “Data Entry Errors”
EQQD003I ENTER END AGAIN TO EXIT, OR on page 2.
PRESS ENTER TO PRINT
The valid extension time format is HHHMM, where
Explanation: You can either cancel the print request HHH is 000 through 504 and MM is 00 through 59.
and leave this panel by entering END again or print
the specified reports by pressing ENTER.
EQQD011E SPECIFY EITHER EXTENSION OR
System action: The system waits for you to respond. END DATE AND TIME
User response: Enter END or press ENTER. Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQD004E END TIME MUST BE LATER THAN To extend a plan period, you must specify either an
START TIME extension length or an end date and time, but not both.
Explanation: Data entry error; see “Data Entry Errors”
on page 2. EQQD012E END DATE OR EXTENSION LENGTH
MUST BE FILLED IN
EQQD005E END DATE MUST BE LATER THAN Explanation: Data entry error; see “Data Entry Errors”
START DATE on page 2.
Explanation: Data entry error; see “Data Entry Errors” To extend a plan period, you must specify either an
on page 2. end date and time or an extension length.

EQQD006E THE END TIME MUST BE A VALUE EQQD013E A START DATE MUST BE SPECIFIED
00.01 TO 24.00
Explanation: Data entry error; see “Data Entry Errors”
Explanation: Data entry error; see “Data Entry Errors” on page 2.
on page 2.
You must specify a start date because no current plan
exists.
EQQD007E SPECIFY A (ALL DAYS) OR W
(WORKDAYS ONLY)
EQQD014E A CURRENT PLAN ALREADY EXISTS
Explanation: Data entry error; see “Data Entry Errors” FOR THE SPECIFIED PERIOD
on page 2.
Explanation: You specified a start date and time for a
current plan when a current plan already exists.

© Copyright IBM Corp. 1991, 2003 55

System action: The system waits for you to respond.
EQQD141E OPC COULD NOT RETRIEVE
User response: Blank out the start date and time and REQUIRED DATA FROM THE
enter a valid extension length. HISTORY DATABASE.
Explanation: The scheduler tried to access operation
EQQD015E NO CURRENT PLAN EXISTS, SPECIFY data in the DB2® history database but failed. The
START DATE AND TIME reason is described in message EQQD142, which
follows this message.
Explanation: Data entry error; see “Data Entry Errors”
on page 2. System action: Processing continues, but the required
data is not passed to the caller.
To create a current plan, you must specify a start date
and time. User response: Contact your system programmer.
System programmer response: Check message
EQQD016E NO CURRENT PLAN EXISTS, EQQD142.
FUNCTION CANNOT BE USED
Explanation: You have attempted to use a function EQQD142I DB2TXT
that requires the existence of a current plan.
Explanation: This message describes why IBM Tivoli
System action: The system waits for you to respond. Workload Scheduler for z/OS could not access the DB2
history database. It contains messages issued by the
User response: Check why a current plan does not DB2 system.
exist.
System action: Processing continues.
EQQD017E SPECIFIED PERIOD MUST BE User response: Contact your system programmer.
WITHIN CURRENT PLAN PERIOD
System programmer response: Review the messages
Explanation: Data entry error; see “Data Entry Errors” issued by DB2 and take the action described in the DB2
on page 2. documentation.
The start and end times must be within the current
plan start and end times. EQQD143I DB2 SYSTEM DB2 HAS STOPPED.
THE HISTORY FUNCTION IS NOT
AVAILABLE
EQQD018E PLAN START MUST BE EQUAL TO
OR GREATER THAN CURRENT PLAN Explanation: The scheduler has discovered that the
END DB2 system has either stopped or abended. It cannot
support requests for data from the history database.
Explanation: The start of the future trial plan cannot
be before the end of the current plan. System action: Processing continues but the history
function is not available.
System action: The system waits for you to respond.
User response: Contact your system programmer.
User response: Enter a valid start date and time.
System programmer response: Restart the DB2 system
that stopped or abended.
EQQD019E INVALID VALUE SPECIFIED FOR
COPY VSAM USAGE SELECTION
EQQD144I DB2 SYSTEM DB2 IS AVAILABLE
Explanation: Data entry error; see “Data Entry Errors”
on page 2. Explanation: The DB2 system containing the scheduler
history data is available.
User response: To copy VSAM usage data, specify Y.
Otherwise, specify N. System action: Processing continues.
User response: None.
EQQD020E END DATE AND TIME MUST BE
System programmer response: None.
LATER THAN CURRENT PLAN END
Explanation: When extending the current plan, the
EQQD145E OBJECT OBJ COULD NOT BE
end date and time must be later than the end of the
CREATED. REASON FOLLOWS:
current plan.
Explanation: The initialization program tried to create
System action: The system waits for you to respond.
a table, index or an alias in the history database but
User response: Enter an end date and time that is failed. The reason is described in message EQQD142,
later than the current plan end. which follows this message.

56 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

System action: Processing is terminated. JLX3 Joblog status information index 3
User response: Contact your system programmer. System action: Processing is terminated.
System programmer response: Check message User response: Contact your system programmer.
EQQD142.
EQQD148E AN IDENTIFY REQUEST FOR
EQQD146I OBJECT OBJ HAS BEEN CREATED IN CONNECTION TO DB2 WAS
THE HISTORY DATABASE REJECTED. DB2 HAS BEEN STARTED
IN RESTRICTED ACCESS MODE.
Explanation: The initialization program has
successfully created this object in the history database. Explanation: IBM Tivoli Workload Scheduler for z/OS
loses the connection to DB2 because DB2 was started in
System action: Processing continues.
restricted access mode, using ACCESS(MAINT).
User response: None.
System action: Processing continues
User response: Contact your system programmer.
EQQD147E THE SYSIN FILE CONTAINS BAD OR
MISSING PARAMETERS System programmer response: Stop DB2 and restart it
without the ACCESS keyword. To connect IBM Tivoli
Explanation: The initialization program was unable to
Workload Scheduler for z/OS to DB2, as soon as DB2 is
create the history database because some SYSIN
up again, enter the following operator command: /F
parameters are missing or specified incorrectly. The
subsystemname, DB2RETRY
following parameters are required to create the history
database:
EQQD149E THE CAF INTERFACE ROUTINE
DBNAME
FAILED WITH RC
The database name
Explanation: This message explains why IBM Tivoli
MAIN The name of the scheduler history database
Workload Scheduler for z/OS cannot connect with DB2.
main table
It includes the error code issued by the DB2 system.
MAINX
System action: Processing continues.
The main table index name
User response: Contact your system programmer.
OCC The name of the scheduler table that stores
occurrence data System programmer response: Review the return
code issued by DB2 and follow the actions described in
OCCX1
the DB2 documentation.
Occurrence data index 1
OCCX2
Occurrence data index 2
OCCX3
Occurrence data index 3
OPR The name of the scheduler table that stores
operation data
OPRX1 Operation data index 1
OPRX2 Operation data index 2
OPRX3 Operation data index 3
DS The name of the scheduler table that stores
operation data set information
DSX1 Data set information index 1
DSX2 Data set information index 2
DSX3 Data set information index 3
JL The name of the scheduler table that stores
joblog status information
JLX1 Joblog status information index 1
JLX2 Joblog status information index 2

Chapter 7. EQQDnnn Messages 57

58 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 8. EQQEXnn Messages
Scheduler for z/OS processing continues. Operations at
EQQEX01I THE EXTERNAL ROUTER TASK HAS
user-defined workstations are not started.
STARTED
User response: If the controller includes workstations
Explanation: The external router task has successfully
with user-defined destinations, contact your system
completed initialization. The external router task
programmer.
handles the interface to the operation-initiation exit,
EQQUX009, which is used to start operations at System programmer response: Determine why IBM
user-defined destinations. Tivoli Workload Scheduler for z/OS was unable to find
or load the operation-initiation exit, EQQUX009. When
System action: The external router task processing
the problem has been corrected restart the controller.
continues.
User response: None.
EQQEX05E THE EXTERNAL ROUTER HAS
TERMINATED DUE TO AN
EQQEX02I THE EXTERNAL ROUTER TASK HAS INITIALIZATION FAILURE
ENDED
Explanation: The external router task could not
Explanation: The external router task has ended either acquire the resources required for normal operation.
because the controller is in the process of shutting
System action: External router processing is
down or as a result of an operator modify command to
terminated.
terminate this task or a related task.
Problem determination: Review previous messages in
System action: IBM Tivoli Workload Scheduler for
the IBM Tivoli Workload Scheduler for z/OS message
z/OS processing continues.
log.
User response: None.
User response: Contact your system programmer.
System programmer response: Correct all errors and
EQQEX03E THE EXTERNAL ROUTER TASK HAS
restart IBM Tivoli Workload Scheduler for z/OS.
ENDED DUE TO PROCESSING
ERRORS
EQQEX06E A SEVERE ERROR IN THE EXTERNAL
Explanation: The external router task has terminated
ROUTER TASK HAS CAUSED ONE
due to processing errors.
OR MORE REQUESTS TO BE LOST
Problem determination: Check the IBM Tivoli
Explanation: The external router task encountered an
Workload Scheduler for z/OS message log and the
error processing elements on the EXAQ. As a result, at
dump data sets for additional information that
least one queue element has been lost.
describes the problem.
System action: z/OS recovery/termination is
System action: Normal IBM Tivoli Workload
requested to generate a dump. The external router task
Scheduler for z/OS processing continues.
attempts to continue normal processing.
User response: Contact your system programmer.
Problem determination: Review the IBM Tivoli
System programmer response: If the cause of the Workload Scheduler for z/OS message log data set, the
error is due to a problem in the operation-initiation EQQDUMP diagnostic data set, and the dump data set
exit, EQQUX009, correct the error and restart the to determine the cause of the problem.
controller. If the cause of the error cannot be
IBM Tivoli Workload Scheduler for z/OS
determined, take a dump of the IBM Tivoli Workload
administrator response: Save the message log,
Scheduler for z/OS address space, retain a copy of the
diagnostic and dump data sets, and contact Customer
message log and the job tracking data sets and contact
Support.
Customer Support.

EQQEX07E THE EXTERNAL ROUTER TASK

EQQEX04W NO ROUTING FOR USER
ABENDED WHILE PROCESSING THE
DESTINATIONS IS IN EFFECT
FOLLOWING REQUEST REQUEST
Explanation: The external router task has not been
Explanation: An abend prevented the external router
able to load the operation-initiation exit, EQQUX009.
task from processing a queue element.
System action: Normal IBM Tivoli Workload

© Copyright IBM Corp. 1991, 2003 59

System action: z/OS recovery/termination is
requested to generate a dump. The external router task
attempts to continue normal processing.
Problem determination: Review the IBM Tivoli
Workload Scheduler for z/OS message log data set, the
EQQDUMP diagnostic data set, and the dump data set
to determine the cause of the problem.
User response: Contact your system programmer.
System programmer response: Save the message log,
diagnostic and dump data sets, and contact Customer
Support.

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 IBM Tivoli
Workload Scheduler for z/OS message log data set.
User response: Contact your system programmer.
System programmer response: Save the message log
(EQQMLOG) and the current plan (EQQCPxDS) and
contact Customer Support.

60 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

Chapter 9. EQQEnnn Messages
EQQE000I TOTAL NUMBER OF EVENTS EQQE001E ETT FAILED TO ADD ADID FOR
PROCESSED BY THE EVENT TRIGGERING EVENT TRIG I/O
MANAGER TASK IS: NUMEV ERROR READING AD DATA BASE
NUMBER OF EVENTS SINCE THE
Explanation: Event-triggered tracking (ETT) was
PREVIOUS MESSAGE IS: NEWEV
triggered by an event, but could not add the associated
EVENT MANAGER QUEUE LENGTH
application due to an I/O-error on the application
STATISTICS FOLLOW: TOTAL Q1 Q2
description database.
Q5 Q10 Q20 Q50 Q100 >100
CALLSQ1Q2Q3Q4 Q5Q6Q7Q8 System action: The associated application was not
added by ETT, but ETT processing continues normally.
Explanation: This message is issued if the EVENTS
statistics are made active, either by specifying the Problem determination: Review previous messages in
STATMSG(EVENTS) keyword in the JTOPTS the IBM Tivoli Workload Scheduler for z/OS message
initialization statement or by issuing the modify log data set to determine the cause of the error.
command, /F subsys,EVESTA=ON.
User response: Contact your system programmer.
Once activated, this message is regularly issued by the
event manager subtask, until it is deactivated. The System programmer response: Save the message log
interval between two messages is calculated as follows: data set containing this error and contact Customer
Support.
v If STATIM is nonzero (in the initial parm or by
modify command) the message is issued
approximately every n minutes (where n is the EQQE002E ETT FAILED TO ADD ADID FOR
STATIM value), if any events have been processed. TRIGGERING EVENT TRIG FIRST
v Otherwise, if EVELIM is nonzero (in the initial parm OPERATION NOT ON MVS CPU WS,
or by modify command), the message is issued JOBNAME CANNOT BE REPLACED
approximately every n events (where n is the Explanation: Event-triggered tracking (ETT) was
EVELIM value). triggered by an event, but could not add the associated
v Otherwise, the message is issued approximately application since the first operation (that is, the
every n events, where n is half the JTOPTS BACKUP operation with the lowest operation number) was not a
keyword value (default BACKUP is 400). CPU-operation or a non-z/OS CPU operation and
ETT’s Job Name Replace option was specified.
This message shows the total number of events System action: The associated application was not
processed and how many events have been processed added by ETT, but ETT processing continues normally.
since the message was last issued or, if it is the first
time it is issued, since the last time the event manager Problem determination: If the Job Name Replace
processed the events queue. option is used, check the application description (AD)
database to make sure that the first operation in the
The message also contains information about how application to be added is a z/OS CPU-operation. Or,
many events were waiting to be processed each time check the ETT criteria table to make sure that the
the queue processing routine was called. The value correct Job Name Replace option was specified. Or,
below the TOTAL heading gives the total number of check that the CPU workstation for z/OS systems is
times that the event queue was emptied. The values part of the control plan since it might have been added
below the Qx headings give the number of times that to the workstation database after a new control plan
the length of the queue was in a particular interval. For was created.
example, Q50 gives the number of times that the queue User response: Correct the ETT criteria table or the
was between 21 and 50 events. AD database, or both, or get the CPU workstation for
System action: Normal IBM Tivoli Workload z/OS systems into the control plan.
Scheduler for z/OS processing continues. System programmer response: None.
User response: None.

© Copyright IBM Corp. 1991, 2003 61

 plan data set has been referenced. The data values are
EQQE003E ETT FAILED TO ADD ADID FOR
displayed in the message EQQE005I. The values for
TRIGGERING EVENT TRIG FIRST
each heading are:
OPERATION HAS PREDECESSORS,
NAME The name of the IBM Tivoli Workload
JOBNAME CANNOT BE REPLACED
Scheduler for z/OS task for which data was
Explanation: Event-triggered tracking (ETT) was gathered.
triggered by an event, but could not add the associated NEXCL
application since the first operation (that is, the The number of times that the task acquired
operation with the lowest operation number) had exclusive use of the current plan.
internal predecessor operations, and ETT’s Job Name NSHRD
Replace option was specified. The number of times that the task acquired
shared use of the current plan.
System action: The associated application was not
THELD
added by ETT, but ETT processing continues normally.
The total amount of time, in seconds, that the
Problem determination: Check the application task was using the current plan.
description (AD) database to make sure that the first TWAIT The total amount of time, in seconds, that the
operation in the application to be added does not have task was waiting to use the current plan.
any internal predecessor operations. Or, check the ETT AHELD
criteria table to make sure that the correct Job Name The average amount of time, in seconds, that
Replace option was specified. the task was using the current plan.
AWAIT
User response: Correct the ETT criteria table or the The average amount of time, in seconds, that
AD database, or both or get the CPU workstation for the task was waiting to use the current plan.
z/OS systems into the control plan.
System action: Normal IBM Tivoli Workload
System programmer response: None. Scheduler for z/OS processing continues.
User response: None.
EQQE004I CP ENQ LOCK STATISTICS SINCE
PREVIOUS MESSAGE FOLLOW:
NAME NEXCL NSHRD THELD TWAIT EQQE005I NAMENEXCLNSHRDTHELD
AHELD AWAIT TWAITAHELDAWAIT
Explanation: This message is issued if the CP ENQ Explanation: This message is issued together with the
LOCK statistics are active. This can be done either by message EQQE004I. See the explanation for EQQE004I
specifying the STATMSG(CPLOCK) keyword in the for details about when it is issued.
JTOPTS initialization statement or by using the modify
The message contains information about the use of the
command, /F subsys,CPQSTA=ON.
current plan data set by one IBM Tivoli Workload
Once activated, this messages is regularly issued by the Scheduler for z/OS subtask. The descriptions of the
event manager subtask, until it is deactivated. The column headings in the previous message, EQQE004I,
interval between two messages is calculated as follows: also describe the variables in this message.
v If STATIM is nonzero (in the initial parm or by System action: Normal IBM Tivoli Workload
modify command) the message is issued Scheduler for z/OS processing continues.
approximately every n minutes (where n is the
STATIM value), if any events have been processed. User response: None.
v Otherwise, if EVELIM is nonzero (in the initial parm
or by modify command), the message is issued EQQE006I EVENT MANAGER EVENT TYPE
approximately every n events (where n is the STATISTICS FOLLOW: TYPE NTOT
EVELIM value). NNEW TTOT TNEW TAVG NAVG
v Otherwise, the message is issued approximately NSUS
every n events, where n is half the JTOPTS BACKUP Explanation: This message is issued if the EVENTS
keyword value (default BACKUP is 400). statistics are active. This can be done either by
specifying the STATMSG(EVENTS) keyword in the
This message shows that IBM Tivoli Workload JTOPTS initialization statement, or by using the modify
Scheduler for z/OS tasks have referred to the current command, /F subsys,EVESTA=ON.
plan data since the last message was issued, or if it is
the first time it is isuued, since the last time the event Once activated, this message is regularly issued by the
manager processed the events queue. event manager subtask, until it is deactivated. The
interval between two messages is calculated as follows:
The message consists of column headers that describe v If STATIM is nonzero (in the initial parm or by
data indicating how often and in what way the current modify command) the message is issued

62 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 approximately every n minutes (where n is the information about how the event manager subtask
STATIM value), if any events have been processed. processed one type of event. The descriptions of the
v Otherwise, if EVELIM is nonzero (in the initial parm column headings in the previous message, EQQE006I,
or by modify command), the message is issued also describe the variables in this message.
approximately every n events (where n is the System action: Normal IBM Tivoli Workload
EVELIM value). Scheduler for z/OS processing continues.
v Otherwise, the message is issued approximately
User response: None.
every n events, where n is half the JTOPTS BACKUP
keyword value (default BACKUP is 400).
EQQE008I TYPE08
This message consists of column headers that describe Q10Q100Q1000Q5000Q10000>10000
measured values that are displayed in the message R1R2R3R4R5R6
EQQE007I that follows. The measured values contain
Explanation: This message is issued if the WSA
information about the total number of events
statistics are active. This can be done either by
processed, how many have been processed since the
specifying the STATMSG(WSATASK) keyword in the
message was last issued, or, if it is the first time it is
JTOPTS initialization statement, or by using the modify
issued, since the last time the event manager processed
command, /F subsys,WSASTA=ON.
the events queue, and the elapsed time that the event
manager needed to process the events. Once activated, this message is regularly issued by the
event manager subtask, until it is deactivated. The
The values for each heading are: interval between two messages is calculated as follows:
TYPE The event type for which data was gathered. v If STATIM is nonzero (in the initial parm or by
TTOT The total number of events of this type. modify command) the message is issued
NNEW The number of events of this type since the approximately every n minutes (where n is the
last message. STATIM value), if any events have been processed.
TTOT The total time, in seconds, used to process this
v Otherwise, if EVELIM is nonzero (in the initial parm
event type.
or by modify command), the message is issued
TNEW The total time, in seconds, used to process this
approximately every n events (where n is the
event type since the last message.
EVELIM value).
TAVG The average time, in seconds, used to process
an event of this type. v Otherwise, the message is issued approximately
NAVG The average time, in seconds, used to process every n events, where n is half the JTOPTS BACKUP
an event of this type since the last message. keyword value (default BACKUP is 400).
NSUS The number of times that the event manager
could not immediately process an event of this This message shows some statistic information about
type. the operations ready queue list and its handling by the
WSA task since it was last issued, or, if it is the first
Valid values in the TYPE column are: time it is isuued, since the last time the event manager
ALL This line is a total line for all event types. processed the events queue.
1 Reader events.
2 Job start events. The set of variables (R1-R6) gives the number of times
3S Step end events. that the ready list was found to be within a specific
3J Job end events. range, each time the WSA task processed it to select a
3P Job on output queue events. “winner” operation (one to be submitted). For example,
4 Data set print events. R1=10 means that the ready queue list was found 10
5 Job purge events. times to contain n operations, where n< 10.
USER User generated event, EQQUSINT program or
System action: Normal IBM Tivoli Workload
the OPSTAT command.
Scheduler for z/OS processing continues.
OTHR Other events.
User response: None.
System action: Normal IBM Tivoli Workload
Scheduler for z/OS processing continues.
EQQE009I TYPE09VALUE09
User response: None.
Explanation: This message is issued together with
message EQQE008I. See the explanation for EQQE008I
EQQE007I TYPENTOTNNEWTTOT
for details about when it is used.
TNEWTAVGNAVGNSUS
The meanings of VALUE09 are as follows:
Explanation: This message is issued if
V1 Size of the ready list queue when the message
STATMSG(EVENTS) has been specified in the JTOPTS
is issued
initialization statement. The message contains

Chapter 9. EQQEnnn Messages 63

V2 Number of operations whose status changed the IBM Tivoli Workload Scheduler for z/OS started
to ready (R, *, or A) since the last message task.
V3 Number of operations whose status changed
to started since the last message
EQQE013E ETT FAILED TO ADD ADID FOR
V4 Number of operations whose status changed
TRIGGERING EVENT TRIG ERROR
to completed since the last message
DETECTED BY MODIFY CURRENT
V5 Number of times the WSA task was called to
PLAN INTERFACE
select a winner operation since the last
message Explanation: IBM Tivoli Workload Scheduler for z/OS
V6 Number of times the JS VSAM was accessed to was unable to add the application because the modify
read JCL since the last message current plan interface detected an error.
V7 Number of times the JOBLIB PDS was
accessed to read JCL since the last message System action: The associated application was not
V8 Number of times the User Exit 001 was called added by event-triggered tracking (ETT), but ETT
since the last message processing continues normally.
V9 Number of times the User Exit 002 was called Problem determination: Check the IBM Tivoli
since the last message Workload Scheduler for z/OS message log data for
System action: Normal IBM Tivoli Workload EQQMxxx messages (that is, the Modify Current Plan
Scheduler for z/OS processing continues. messages) preceding this message. These messages give
the exact reason why the application could not be
User response: None. added.
User response: Contact your system programmer.
EQQE011E ETT FAILED TO ADD ADID FOR
TRIGGERING EVENT TRIG NO System programmer response: Save the message log
ACTIVE APPLICATION DESCRIPTION data set containing these error messages and contact
IN AD DATABASE Customer Support.

Explanation: Event-triggered tracking (ETT) was

triggered by an event but could not add the associated EQQE014E ETT FAILED TO ADD ADID FOR
application because there was no active application TRIGGERING EVENT TRIG AD
description (AD) in the AD database. DATABASE NOT OPEN

System action: The associated application was not Explanation: Event-triggered tracking (ETT) was
added by ETT, but ETT processing continues normally. triggered by an event but could not add the associated
application since the application description database
Problem determination: Check the ETT criteria to was not open.
make sure that the triggering event identifies an active
application description. System action: The associated application was not
added by ETT, but ETT processing continues normally.
User response: Correct the ETT criteria table or the
AD database. Problem determination: This is a IBM Tivoli
Workload Scheduler for z/OS internal error.

EQQE012E ETT FAILED TO ADD ADID FOR System programmer response: Save the message log
TRIGGERING EVENT TRIG UNABLE data set containing these error messages and contact
TO ALLOCATE NECESSARY Customer Support.
STORAGE
Explanation: IBM Tivoli Workload Scheduler for z/OS EQQE015W ETT CANNOT TRACK JOB JOB EVEN
was unable to allocate storage needed to build the THOUGH APPLICATION APPL HAS
tables required when adding an application BEEN ADDED
(occurrence) to the current plan. Explanation: Event-triggered tracking (ETT) was
System action: The associated application was not unable to track the specified job, even though the
added by event-triggered tracking (ETT), but ETT specified associated application was successfully added.
processing continues normally. System action: The job that triggered the addition of
Problem determination: Check the region size application APPL is not tracked by IBM Tivoli
allocated to the IBM Tivoli Workload Scheduler for Workload Scheduler for z/OS. ETT processing
z/OS started task. continues.

User response: Contact your system programmer. Problem determination: The track keyword of the job
tracking option statement has most likely been defined
System programmer response: Increase the region for so that no tracking should occur.

64 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

User response: Review the tracking options and jcl used for the last run: in this case a step name table
correct if in error. (DCLCPR44) should exist to map the original step
names and the new step names, but no table was
found.
EQQE016I ETT HAS SUCCESSFULLY ADDED
ADID FOR TRIGGERING EVENT TRIG System action: Processing continues without using the
step name table information.
Explanation: Event-triggered tracking (ETT) has
detected a triggering event (TRIG) and has added the System programmer response: Check EQQMLOG to
associated application (ADID) to the current plan. see if some error occured causing missing step name
table for that operation..
System action: Processing continues.
User response: None.
EQQE021E THE EVENT MANAGER WAS
UNABLE TO SET STATUS STATUS
EQQE017I THE ETT FUNCTION IS ACTIVATED FOR JOBNAME(JOBNUM)

Explanation: The event-triggered tracking (ETT) Explanation: The event manager was unable to
function has been activated from the dialog or has been change the status of an operation in the current plan.
started during the controller start up process because
System action: The status of the current operation
ETT(YES) is specified on the JTOPTS initialization
remains unchanged. The event manager continues
statement.
normally by processing the next event.
System action: Processing continues.
Problem determination: Review earlier messages in
User response: None. the IBM Tivoli Workload Scheduler for z/OS message
log to determine which operation is involved. The most
likely cause of this error is an unsuccessful I/O
EQQE018I THE ETT FUNCTION IS operation against the current plan data set.
DEACTIVATED
User response: If the current operation can be
Explanation: The event-triggered tracking (ETT) determined, set the correct status for this operation.
function has been deactivated due to a dialog request
or because the event manager subtask has been System programmer response: Correct all errors and,
requested to terminate. if necessary, restart IBM Tivoli Workload Scheduler for
z/OS.
System action: Processing continues.
User response: None. EQQE022E EVENT MANAGER INITIALIZATION
FAILED
EQQE019I JOBNAME(JOBNUM) WAS NOT Explanation: The event manager could not acquire all
SUBMITTED BY OPC AND resources required for normal operation. The most
TRACK(OPCASUB) OR likely cause of this error is that the subsystem is being
TRACK(JOBOPT) IS ACTIVE, BUT stopped but the normal mode manager subtask has not
THE JOB WILL BE TRACKED started. It is also possible that the JCL repository data
ANYWAY BECAUSE IT BELONGS TO set could not be opened.
AN APPLICATION THAT WAS
ADDED BY ETT System action: If this message is issued while the IBM
Tivoli Workload Scheduler for z/OS subsystem is being
Explanation: Event-triggered tracking (ETT) has a job stopped, subsystem termination continues normally.
on its list of jobs to be tracked, but the specified job has Otherwise, message EQQZ045W is issued.
not been submitted by IBM Tivoli Workload Scheduler
for z/OS. System programmer response: Review previous
messages in the IBM Tivoli Workload Scheduler for
System action: IBM Tivoli Workload Scheduler for z/OS message log to determine the exact reason for
z/OS tracks the job because it belongs to an application this message.
that was added by ETT.
User response: None. EQQE023I THE EVENT MANAGER ENDED
NORMALLY
EQQE020W EXPANDED JCL USED IN LAST RUN Explanation: This message is issued if the IBM Tivoli
BUT NO STEP NAME CHANGE Workload Scheduler for z/OS subsystem is being
TABLE FOUND FOR JOBNUM . stopped and Event Manager initialization has
Explanation: TWS z/OS Controller was checking the completed successfully. The message is also issued if
NOERROR table for an operation having the expanded

Chapter 9. EQQEnnn Messages 65

the Event Manager has been requested to stop by an operation from starting and take appropriate actions to
operator modify command. enable it to start.
System action: Termination processing continues.
EQQE028I LONG DURATION FOR OPERATION
User response: None.
OPERNUM, IN APPLICATION APPL,
IA = ARRTIME
EQQE024E THE EVENT MANAGER
Explanation: This message is issued when a started
TERMINATED BECAUSE OF
operation on a general type workstation has been active
UNRECOVERABLE ERRORS
longer than its estimated duration multiplied by the
Explanation: This message is issued if a serious error feedback limit, divided by 100. For example, if the
that prevents normal operation by the Event Manager feedback limit is 200 and the estimated duration is ten
has been encountered after Event Manager initialization minutes, the message is issued if the operation has
has completed. been active longer than twenty minutes.

System action: Message EQQZ045W is issued. System action: Normal IBM Tivoli Workload
Scheduler for z/OS processing continues.
System programmer response: Review earlier
messages in the IBM Tivoli Workload Scheduler for User response: Investigate why the operation has been
z/OS message log to determine the exact reason for active so long. If possible, take corrective action to
this message. speed up operation processing.

Operator response: If the Event Manager should be

activated, issue an operator modify command to start EQQE029E TRACK (OPCASUB/JOBOPT) IS
the Event Manager again. SPECIFIED, AND AS USER
SUBMITTED JOBNAME(JOBNUM)
OUTSIDE OPC, IT WILL NOT BE
EQQE025I THE EVENT MANAGER HAS TRACKED
STARTED
Explanation: The job is not one that IBM Tivoli
Explanation: Event Manager initialization has Workload Scheduler for z/OS has submitted although
completed successfully and the Event Manager is about it is known to IBM Tivoli Workload Scheduler for z/OS
to start processing. as one that should be tracked. However, because
System action: IBM Tivoli Workload Scheduler for someone submitted the job outside of IBM Tivoli
z/OS processing continues. Workload Scheduler for z/OS’s control, the job is not
tracked.
User response: None.
System action: None.

EQQE026I APPLICATION APPL ENDED IN User response: None.

ERROR EC. OPER = OPERNUM, PRTY
= PRI, IA = IA EQQE030I USER USER CAUSED A NEW SPECIAL
Explanation: This message is issued when an RESOURCE TO BE DEFINED. NAME
operation on a general type workstation has ended in OF NEW RESOURCE IS: RESOURCE
error and the ALERTS initialization statement specifies Explanation: The request to create the new resource
TYPE(ERROROPER). came from: an SRSTAT command, EQQEVPGM using
System action: Normal IBM Tivoli Workload SRSTAT as input, the EQQUSINS subroutine, the
Scheduler for z/OS processing continues. EQQUSIN subroutine, or from the data set triggering
function.
User response: Perform error recovery actions for the
specified operation. System action: Processing continues.
User response: None.
EQQE027I OPERATION OPERNUM, IN
APPLICATION APPL, IA = ARRTIME IS EQQE036I JOB JOBNAME(JNUM), OPERATION
LATE (OPERNUM) ENDED IN ERROR EC.
Explanation: This message is issued when a ready PRTY=PRI, APPL = APPL, WORK
operation on a general type workstation has reached its STATION = WSID, IA = IA
latest start time but has not yet started. Explanation: This message is issued when an
System action: Normal IBM Tivoli Workload operation on a computer or printer workstation has
Scheduler for z/OS processing continues. ended in error and the ALERTS initialization statement
specifies TYPE(ERROROPER).
User response: Investigate what is keeping the

66 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

System action: Normal IBM Tivoli Workload started on the agent but the workstation is unlinked.
Scheduler for z/OS processing continues.
System programmer response: For MVS jobs if the
User response: Perform error recovery actions for the operation status is successful, verify in the message log
current job. that the link to the DESTINATION is active, the
associated submit task is active, events are available on
the associated EQQEVDS dataset, and that an event
EQQE037I JOB JOBNAME(JNUM), OPERATION
reader funcion is active. In a shared DASD
(OPERNUM) IN APPLICATION APPL,
environment, also verify that no hardware reserves, or
IS LATE, WORK STATION = WSID, IA
other contention are locking access to the data set.
= ARRTIME
Explanation: This message is issued when a job has
EQQE040W OPC CANNOT HANDLE JOB
reached its latest start time but has not yet started.
JOBNAME(JOBNUM). THE JOB MAY
System action: Normal IBM Tivoli Workload HAVE TO BE CANCELED
Scheduler for z/OS processing continues.
Explanation: IBM Tivoli Workload Scheduler for z/OS
User response: Investigate what is keeping the job job tracking has encountered an “add job to JES queue”
from starting and take appropriate actions to enable it event for a job whose job name matches job names
to start. 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
EQQE038I LONG DURATION FOR JOB message indicates that jobs with IBM Tivoli Workload
JOBNAME(JNUM), OPERATION Scheduler for z/OS job names are being submitted by
(OPERNUM) IN APPLICATION APPL, non-IBM Tivoli Workload Scheduler for z/OS functions.
WORK STATION = WSID, IA =
ARRTIME System action: IBM Tivoli Workload Scheduler for
z/OS assumes that the job is not a IBM Tivoli
Explanation: This message is issued when a job has Workload Scheduler for z/OS job and does not track
been active longer than its estimated duration the job. If the job was held by a IBM Tivoli Workload
multiplied by the feedback limit, divided by 100. For Scheduler for z/OS job tracking exit it is released.
example, if the feedback limit is 200 and the estimated
duration is ten minutes, the message is issued if the job
Note: Since this job is not handled by IBM Tivoli
has been active longer than twenty minutes. The
Workload Scheduler for z/OS, any dependencies
feedback limit specified on the JTOPTS initialization
this job may have must be manually
statement is used in the calculation.
implemented.
System action: Normal IBM Tivoli Workload
System programmer response: Determine if IBM
Scheduler for z/OS processing continues.
Tivoli Workload Scheduler for z/OS and non-IBM
User response: Investigate why the job has been active Tivoli Workload Scheduler for z/OS jobs are using the
so long. If possible, take corrective action to speed up same job names. Check that all jobs belonging to IBM
the processing of the job. Tivoli Workload Scheduler for z/OS defined
applications are defined in the current plan.

EQQE039I LONG TIME ON INPUT QUEUE FOR

JOB JOBNAME (&&JNUM), OPERATION | EQQE041W THE EVENT MANAGER HAS
(&OPERNUM), APPL = &&APPL, | IGNORED THE FOLLOWING USER
WORK STATION = &&WSID, IA = | DEFINED EVENT RECORD BECAUSE
ARRTIME | THE NEW STATUS IS NOT VALID
| FOR A FTW OPERATION: EXITREC
Explanation: If the ALERTS initialization statement
specifies DURATION, this message is issued when a | Explanation: An invalid user-defined event record has
job or started task has been started by the controller | been found in the event manager work queue. The
but after 10 minutes has not started to operate yet (for | operation specified in the event is a fault-tolerant
MVS jobs no A2/B2 event has been processed), for | workstation operation and the new specified status is
FT-jobs the extended status is waiting for submission | not valid. As a rule, only C and S are accepted. The S
i.e. no event signaling that the job is started on the | value is not allowed if the operation is running or if it
agent has been processed.) | has a recovery job that is running.

System action: Normal IBM Tivoli Workload | System action: The incorrect event record is returned
Scheduler for z/OS processing continues. | to the free queue of the event manager without any
| further processing.
User response: Investigate what is keeping the job
from starting and take appropriate actions to enable it | System programmer response: Determine if any user
to start. For FT-jobs it could be possible that the job is

Chapter 9. EQQEnnn Messages 67

| program generates events that change the status of an operation has predecessor operations that have not yet
| FTW operation. been reported complete.
System action: The status of the operation is not
EQQE042I JOBNAME(JOBNUM) WAS NOT changed. The Event Manager continues normal
SUBMITTED BY OPC BUT WILL BE operation with the next queued event.
TRACKED ANYWAY
System programmer response: Determine if the job
Explanation: The Event Manager has encountered an was submitted outside of IBM Tivoli Workload
event for a job whose job name matches an operation Scheduler for z/OS or if it was held and released
defined in the current plan. However, IBM Tivoli manually. Inform all people concerned about the reason
Workload Scheduler for z/OS did not submit this job. for this message and take appropriate action to make
This message indicates that jobs with IBM Tivoli sure that operations are started only after all
Workload Scheduler for z/OS job names are being predecessors are complete.
submitted by non-IBM Tivoli Workload Scheduler for
Operator response: Determine if predecessors to the
z/OS functions.
current operation have completed. If they have, change
System action: IBM Tivoli Workload Scheduler for their status to complete, and change the status of the
z/OS accepts current job as a IBM Tivoli Workload current operation to started. If they have not, the
Scheduler for z/OS job and continues to track events current job should be entered into hold status, and the
for this job. job should be restarted. After predecessors have
completed, the job should be released from hold.
System programmer response: Determine if IBM
Tivoli Workload Scheduler for z/OS and non-IBM
Tivoli Workload Scheduler for z/OS jobs are using the EQQE045E ERRORS OCCURRED READYING
same job names. If IBM Tivoli Workload Scheduler for SUCCESSOR TO THE FOLLOWING
z/OS and non-IBM Tivoli Workload Scheduler for OPERATION: APPLICATION = APPL,
z/OS jobs are using the same job names, take INPUT ARRIVAL = ARRTIME,
appropriate action to minimize such name conflicts. OPERATION NUMBER = OPNUM THE
Inform IBM Tivoli Workload Scheduler for z/OS FAILURE REASON WAS REASON. THE
application owners that rerunning applications or PROBLEM SUCCESSOR OPERATION:
adding additional work to the job queue should be APPLICATION = SAPPL, INPUT
done using the IBM Tivoli Workload Scheduler for ARRIVAL = SARRTIME, OPERATION
z/OS Modify Current Plan dialog. NUMBER = SOPNUM
Explanation: The scheduler changed the status of an
EQQE043W JOB START OR JOB END EVENT operation to Complete but encountered errors when
RECEIVED FOR JOBNAME(JOBNUM) attempting to set the status to Ready for a successor of
IS NOT CONSISTENT WITH the complete operation.
CURRENT OPC STATUS OF THIS JOB
System action: The status is not changed for any of
Explanation: The Event Manager has received an the successor operations. Processing continues.
event for a job on an automatically reporting computer
System programmer response: Review earlier
workstation that conflicts with the information already
messages in the IBM Tivoli Workload Scheduler for
collected for this operation. For example, a job
z/OS message log to determine the exact reason for
complete event can only occur for a job that has started
this message. Some possible values for reason are:
to execute.
R A VSAM I/O error was encountered when
System action: The status of the operation is not
reading the successor operation. See the
changed. The Event Manager continues normal
message reporting the I/O error for more
operation with the next queued event.
details.
System programmer response: Use console messages
N The successor operation does not list the
in the z/OS SYSLOG data set, or records in an SMF log
predecessor as a dependency.
data set to determine what has happened to this job. If
possible, try to locate the SYSMSG data set for this job. W The workstation name for the successor
operation is not defined in the current plan.
EQQE044W JOBNAME(JOBNUM) MAY HAVE BEEN C The status of the successor operation is
STARTED OUT-OF-ORDER. IF already complete.
REQUIRED, SET CORRECT STATUS
MANUALLY M Setting the status of the successor operation to
Ready failed. Check the message log for
Explanation: The Event Manager has received a job further messages describing the error.
start event for an operation on an automatically
reporting computer workstation. However, this

68 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

All of the reasons above indicate an internal product
EQQE048W JOBNAME(JOBNUM) COULD NOT BE
error. Save a copy of the active current plan, the
RELEASED FROM HOLD BECAUSE
job-tracking archive, and the active job-tracking log.
OF ERRORS ON THE
Contact Customer Support.
SUBMIT/RELEASE FILE WITH
Operator response: Check each successor operation to DDNAME DDNAME
see if all its predecessors are complete. If they are
Explanation: A job that was held by a IBM Tivoli
complete, change the status of the operation to ready
Workload Scheduler for z/OS job tracking exit could
using the MCP dialog.
not be released from hold because an error occurred
while writing the release command to a submit/release
EQQE046W THE EVENT MANAGER WAS data set.
UNABLE TO RELEASE
System action: The hold status of the current job is
JOBNAME(JOBNUM) FROM HOLD
not changed. The Event Manager continues normal
Explanation: The Event Manager was unable to operation with the next queued event.
communicate successfully with JES while trying to
System programmer response: Review earlier
release a job from hold.
messages in the IBM Tivoli Workload Scheduler for
System action: The hold status of the current job is z/OS message log to determine the exact reason for
not changed. The Event Manager continues normal this message.
operation with the next queued event.
Operator response: Check that the job is still held by
System programmer response: Check that JES is JES on the system where it is executing. If it is, enter an
executing normally. appropriate operator command to release the job from
hold.
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. EQQE049W THE EVENT MANAGER HAS
IGNORED THE FOLLOWING USER
DEFINED EVENT RECORD BECAUSE
EQQE047W JOBNAME(JOBNUM) COULD NOT BE NO MATCHING OPERATION COULD
RELEASED FROM HOLD BECAUSE BE FOUND IN CURRENT PLAN:
THE SUBMIT/RELEASE DDNAME EXITREC
DDNAME COULD NOT BE LOCATED
Explanation: An invalid user-defined event record has
Explanation: A job that was held by a IBM Tivoli been found on the Event Manager’s work queue. No
Workload Scheduler for z/OS job tracking exit could operation in the current plan data set could be found
not be released from hold because the “add job to JES that matches the operation defined by the event record.
queue” event was read by an event reader where the
RELDDNAME keyword on the ERDROPTS statement System action: The incorrect event record is returned
defines a ddname that is not defined as a to the Event Manager’s free queue without any further
submit/release ddname for any workstation defined in processing.
the current plan.
System programmer response: Determine if any user
System action: The hold status of the current job is program generates events for an undefined application
not changed. The Event Manager continues normal or for an undefined operation in a known application.
operation with the next queued event.
System programmer response: Determine if the EQQE051W THE EVENT MANAGER HAS
EWTROPTS statement is in error and should be IGNORED THE FOLLOWING USER
corrected or if a new current plan containing an DEFINED EVENT RECORD BECAUSE
additional workstation must be created. THE JOBNAME JOBNAME IS NOT
RECOGNIZED: EXITREC
Operator response: Check that the job is still held by
JES on the system where it is executing. If it is, enter an Explanation: An invalid user-defined event record has
appropriate operator command to release the job from been found on the Event Manager’s work queue. No
hold. job name has been given, but it is required.
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 application or for an
operation without specifying a job name.

Chapter 9. EQQEnnn Messages 69

 event record refers to is in a status that is not
EQQE050W THE MANDATORY ACT OPERAND
compatible with the event record.
HAS NOT BEEN SPECIFIED IN THE
JSUACT COMMAND System action: The incorrect event is returned to the
Event Manager free queue without any further
Explanation: There is no default for the ACT operand,
processing. This error might be a symptom that the
which therefore must be specified (to be sure that a so
Symphony file and the scheduler Current Plan VSAM
important function as the job submission is not
data sets are out of sync.
activated or deactivated incidentally).
| User response: Check that no unsupported manual
System action: The request is rejected.
| action has been performed directly from the TWS
User response: Add the ACT operand with the | agent. Run Symphony Renew to produce a new
desired value to the command. | Symphony file synchronized with the Current Plan

EQQE052E THE ISSUER OF THE JSUACT EQQE055W THE EVENT MANAGER HAS
COMMAND HAS NOT THE IGNORED THE FOLLOWING SUBMIT
REQUIRED UPDATE ACCESS EVENT RECORD BECAUSE NO
AUTHORIZATION TO THE JSUB MATCHING OPERATION WAS
FIXED RESOURCE FOUND IN THE CURRENT PLAN:
EXITREC
Explanation: It is required that the person who issues
the JSUACT command has the proper RACF® Explanation: The Event Manager’s work queue
authorization. contains an incorrect submit event. No operation in the
current plan data set matches the operation defined by
System action: The request is rejected
the event record. This submit event record is created
User response: Enhance the RACF authorization of for work being scheduled on one of the systems in this
the user or ensure that the JSUACT command be issued controller product configuration by another controller
by another user having the correct authorization. having the same name.
System action: The Event Manager continues normal
EQQE053E THE EVENT MANAGER HAS processing.
IGNORED THE FOLLOWING FTW
Problem determination: Check if the current plan has
EVENT RECORD BECAUSE NO
changed significantly since the job defined in the event
MATCHING OCCURRENCE WAS
record was submitted. Check if the submit event is old,
FOUND IN THE CURRENT PLAN:
and was sent by a IBM Tivoli Workload Scheduler for
EXITREC
z/OS subsystem that has been inactive a long time.
Explanation: An invalid event record originated from
System programmer response: If you cannot
a fault-tolerant workstation has been found on the
determine the reason for this message, contact
Event Manager work queue. No occurrence in the
Customer Support.
current plan data set could be found that matches the
occurrence token defined by the event record.
EQQE056W THE EVENT MANAGER HAS
System action: The incorrect event is returned to the
IGNORED THE FOLLOWING
Event Manager free queue without any further
INVALID EVENT RECORD: EXITREC
processing. This error might be a symptom that the
Tivoli Workload Scheduler Symphony file and the Explanation: An invalid event record has been found
Tivoli Workload Scheduler for z/OS Current Plan on the Event Manager’s work queue. The most likely
VSAM data sets are out of sync. error is that the last 4 bytes of the record do not
contain the IBM Tivoli Workload Scheduler for z/OS
| User response: Check if in the Symphony file any
character string EQQE. It is also possible that the first 3
| occurrence is present that is not present in the Current
characters of the job number field do not contain the
| Plan. Run Symphony Renew to produce a new
character string JOB.
| Symphony file synchronized with the Current Plan.
System action: The incorrect event record is returned
to the Event Manager’s free queue without any further
EQQE054E THE EVENT MANAGER HAS
processing.
IGNORED THE FOLLOWING FTW
EVENT RECORD BECAUSE IS NOT IBM Tivoli Workload Scheduler for z/OS
CONSISTENT WITH CURRENT OPC administrator response: Note the job name and job
STATUS OF THIS JOB: EXITREC number in the exit record. If necessary, set the correct
status for this job manually.
Explanation: An invalid event record originated from
a fault-tolerant workstation has been found on the System programmer response: Save the IBM Tivoli
Event Manager work queue. The operation that the Workload Scheduler for z/OS message log data set

70 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

(EQQMLOG) containing this message and contact System programmer response: Determine if the user
Customer Support. program generating the event should reference some
other workstation or if the attributes of the current
workstation should be changed.
EQQE057W AN INVALID EVENT QUEUE ENTRY
HAS CAUSED OPC TO IGNORE THE
FOLLOW. EVENT: EVENT HEADER: EQQE061E THE INPUT DATA SET, DDNAME =
EVNTHDR EVENT RECORD: EXITREC SYSIN, COULD NOT BE OPENED
Explanation: An invalid event queue entry has been Explanation: The EQQEVPGM program could not
found on the Event Manager’s work queue. The Event open the data set referenced by the SYSIN DD
Manager could not determine the origin of the event. statement, the statement was not defined correctly, or
Each event must come from one of sixteen possible no SYSIN DD statement was present.
event data sets on each IBM Tivoli Workload Scheduler
System action: The EQQEVPGM program ends.
for z/OS node. In the current event queue entry, either
the event data set number or the IBM Tivoli Workload User response: Check that the SYSIN DD statement is
Scheduler for z/OS node number is not valid. present and that it is correctly coded. After making
corrections, resubmit the EQQEVPGM batch job.
System action: The incorrect event record is returned
to the Event Manager’s free queue without any further
processing. EQQE062E EQQEVPGM INITIALIZATION
FAILED
System programmer response: Save the IBM Tivoli
Workload Scheduler for z/OS message log data set Explanation: The EQQEVPGM program found one or
containing this message and contact Customer Support. more errors during initialization.
System action: The EQQEVPGM program ends.
EQQE058W THE EVENT MANAGER HAS
IGNORED THE FOLLOWING USER User response: Review the message log data set for
DEFINED EVENT RECORD BECAUSE error messages. Remove the cause of each error and
THE WORK STATION NAME resubmit the EQQEVPGM batch job.
WSNAME IS NOT RECOGNIZED:
EXITREC EQQE063I EQQEVPGM ENDED NORMALLY
Explanation: An invalid user-defined event record has Explanation: The EQQEVPGM program has finished
been found on the Event Manager’s work queue. The processing. No errors were found during execution.
workstation name in the current event record does not
match any workstation definition in the current plan System action: The EQQEVPGM program ends.
data set. User response: None.
System action: The incorrect event record is returned
to the Event Manager’s free queue without any further EQQE064E EQQEVPGM TERMINATED BECAUSE
processing. OF UNRECOVERABLE ERRORS
System programmer response: Determine if any user Explanation: A severe error occurred during execution
program generates events for an undefined workstation of the EQQEVPGM program.
or if a new current plan containing an additional
workstation must be created. System action: The EQQEVPGM program ends.
User response: Review the message log data set and
EQQE059W THE FOLLOWING USER DEFINED the SYSUDUMP data set to determine the cause of the
EVENT RECORD CANNOT BE USED error. After making corrections, resubmit the
BECAUSE WORK STATION WSNAME EQQEVPGM batch job. If you cannot determine the
IS NOT AN AUTOMATICALLY cause of the error and if the error persists, contact
REPORTING WORK STATION: Customer Support.
EXITREC
Explanation: An invalid user-defined event record has EQQE065I THE EQQEVPGM PROGRAM HAS
been found on the Event Manager’s work queue. STARTED
Workstations referenced by user-defined event records Explanation: The EQQEVPGM program has been
must be automatically reporting workstations. The correctly initialized and is about to start generating
current workstation does not have this attribute. events.
System action: The incorrect event record is returned System action: EQQEVPGM processing continues
to the Event Manager’s free queue without any further normally.
processing.

Chapter 9. EQQEnnn Messages 71

User response: None. the necessary corrections and resubmit the
EQQEVPGM batch job.
EQQE066E SUBSYS IS NOT A VALID SUBSYSTEM
NAME. NO EVENT IS CREATED EQQE070E THE SPECIAL RESOURCE NAME
GIVEN IS TOO LONG. MAXIMUM
Explanation: The SUBSYS keyword contains an
SIZE IS 44 CHARACTERS
invalid subsystem name.
Explanation: The special resource name defined by the
System action: The event is not created. The
SRSTAT event definition statement is too long.
EQQEVPGM program continues processing the next
event creation statement. System action: The event is not created. The
EQQEVPGM program continues processing the next
User response: If the event should be created, make
event creation statement.
the necessary corrections and resubmit the
EQQEVPGM batch job. User response: If the event should be created, make
the necessary corrections and resubmit the
EQQEVPGM batch job.
EQQE067E A SUBSYSTEM REQUEST ERROR (R15
= R15) OCCURRED. NO EVENT IS
CREATED EQQE071E A SPECIAL RESOURCE NAME IS
REQUIRED ON THE SRSTAT
Explanation: An error occurred when attempting to
STATEMENT
send an event to a IBM Tivoli Workload Scheduler for
z/OS subsystem. Explanation: The current SRSTAT event definition
statement does not define any special resource name.
System action: The event is not created. The
This name is required.
EQQEVPGM program continues processing the next
event creation statement. System action: The event is not created. The
EQQEVPGM program continues processing the next
User response: If R15 is 4, the SUBSYS keyword does
event creation statement.
not define a IBM Tivoli Workload Scheduler for z/OS
subsystem. If R15 is 8, the SUBSYS keyword either does User response: If the event should be created, make
not define a IBM Tivoli Workload Scheduler for z/OS the necessary corrections and resubmit the
subsystem or it defines a IBM Tivoli Workload EQQEVPGM batch job.
Scheduler for z/OS subsystem that has not been
properly installed. Make the necessary corrections and
EQQE072E YOU ARE NOT AUTHORIZED TO
resubmit the EQQEVPGM batch job. If R15 is 12, 16 or
UPDATE SPECIAL RESOURCES FOR
20, contact Customer Support.
SUBSYSTEM SUBSYS
Explanation: In order to change a special resource for
EQQE068E A SUBSYSTEM ERROR (SSOBRETN =
a IBM Tivoli Workload Scheduler for z/OS subsystem,
RETN) OCCURRED. NO EVENT IS
update authority to the SR resource is necessary. You
CREATED
do not have this authority.
Explanation: An error occurred when attempting to
System action: If you specified SUBSYSTEM(MSTR) in
send an event to a IBM Tivoli Workload Scheduler for
the command, no event is created for this subsystem.
z/OS subsystem.
However, EQQEVPGM tries to create an event for the
System action: The event is not created. The next active IBM Tivoli Workload Scheduler for z/OS
EQQEVPGM program continues processing the next subsystem in this z/OS system. If you are authorized
event creation statement. to update one or more of the IBM Tivoli Workload
Scheduler for z/OS subsystems, the statement return
User response: Contact Customer Support.
code is set to 4. Otherwise, it is set to 8. After scanning
all active IBM Tivoli Workload Scheduler for z/OS
EQQE069E ERRORS ENCOUNTERED IN EVENT subsystems, EQQEVPGM continues processing the next
DEFINITION STATEMENTS. ONE OR event creation statement.
MORE EVENTS HAVE NOT BEEN
If you specified a unique IBM Tivoli Workload
CREATED
Scheduler for z/OS subsystem name instead of MSTR,
Explanation: The EQQEVPGM program found one or no event is created for the subsystem specified. The
more incorrectly coded event definition statements. statement return code is set to 8. The EQQEVPGM
program continues processing the next event creation
System action: The EQQEVPGM program ends. statement.
User response: If the events should be created, make User response: Contact your security administrator.

72 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 SS Is a two-digit second number. It must be in the
EQQE073E YOU ARE NOT AUTHORIZED TO
range 00–59.
UPDATE THE CURRENT PLAN FOR
SUBSYSTEM SUBSYS System action: The event is not created. The
EQQEVPGM program continues processing the next
Explanation: In order to create an operation or
statement.
workstation event for a IBM Tivoli Workload Scheduler
for z/OS subsystem, update authority to the RL User response: If the event should be created, make
resource is necessary. You do not have this authority. the necessary corrections and resubmit the
EQQEVPGM batch job.
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 EQQE076E THE INPUT ARRIVAL TIME
next active IBM Tivoli Workload Scheduler for z/OS SPECIFIED BY THE IA KEYWORD IS
subsystem in this z/OS system. If you are authorized NOT VALID
to update one or more of the IBM Tivoli Workload
Scheduler for z/OS subsystems, the statement return Explanation: The IA keyword contains an invalid
code is set to 4. Otherwise, it is set to 8. After scanning input arrival value. The value must be specified in the
all active IBM Tivoli Workload Scheduler for z/OS format YYMMDDHHMM where:
subsystems, EQQEVPGM continues processing the next YYMMDD
event creation statement. Is the input arrival date:
YY Is the year. It must in the range 72–99
If you specified a unique IBM Tivoli Workload for years 1972 through 1999 or 00–71
Scheduler for z/OS subsystem name instead of MSTR, for years 2000 through 2071.
no event is created for the subsystem specified. The MM Is the month number. It must be in
statement return code is set to 8. The EQQEVPGM the range 01–12.
program continues processing the next event creation DD Is the day number. It must be in the
statement. range 01–31.
HHMM
User response: Contact your security administrator.
Is the input arrival time:
HH Is the hour. It must be in the range
EQQE074E THE EVENT CREATION DATE 00–23.
SPECIFIED BY THE EVDATE MM Is the minute. It must be in the range
KEYWORD IS NOT VALID 00–59.
Explanation: The EVDATE keyword contains an System action: The event is not created. The
invalid date. The date must be specified in the format EQQEVPGM program continues processing the next
YYMMDD where: statement.
YY Is year and must specified as 72 to 99 for years
User response: If the event should be created, correct
1972 to 1999 or 00 to 71 for years 2000 to 2071.
the IA keyword and resubmit the EQQEVPGM batch
MM Is the month number and must be in the range
job.
01 to 12.
DD Is the day number and must be in the range
01 to 31. EQQE077E WORK STATION NAME,
APPLICATION DESCRIPTION OR JOB
System action: The event is not created. The
NAME MUST BE SPECIFIED
EQQEVPGM program continues processing the next
statement. Explanation: The current OPSTAT or WSSTAT event
definition statement does not define any workstation
User response: If the event should be created, correct
name, application description, or job name. These items
the EVDATE keyword and resubmit the EQQEVPGM
are required.
batch job.
System action: The event is not created. Processing
ends if it was invoked by a current TSO command. If
EQQE075E THE EVENT CREATION TIME
the command was invoked by the EQQEVPGM
SPECIFIED BY THE EVTIME
program, processing continues with the next statement.
KEYWORD IS NOT VALID
User response: If the event should be created, make
Explanation: The EVTIME keyword contains an
the necessary corrections and reissue the command.
invalid time-of-day value. The time must be specified
in the format HHMMSS, where:
HH Is a two-digit hour number. It must be in the
range 00–23.
MM Is a two-digit minute number. It must be in
the range 00–59.

Chapter 9. EQQEnnn Messages 73

 failed due to an error when communicating with the
EQQE078E THE EVENT DURATION TIME
IBM Tivoli Workload Scheduler for z/OS subsystem.
SPECIFIED BY THE DURATION
KEYWORD IS NOT VALID System action: The IBM Tivoli Workload Scheduler for
z/OS service requested has not been executed.
Explanation: The DURATION keyword contains an
invalid duration value. Event duration must be User response: Contact your systems programmer.
specified in the format HHMM, where:
HH Is a two-digit hour number. It must be in the System programmer response: If the failing command
range 00–99. contains an error, correct it and retry. If the error cannot
MM Is a two-digit minute number. It must be in be corrected, contact Customer Support for assistance.
the range 00–59.
System action: The event is not created. The EQQE082E THE OPC SUBSYSTEM SUBSYS IS
EQQEVPGM program continues processing the next NOT INITIALIZED. NO EVENT IS
statement. CREATED

User response: If the event should be created, make Explanation: A IBM Tivoli Workload Scheduler for
the necessary corrections and resubmit the z/OS TSO command or EQQEVPGM has failed
EQQEVPGM batch job. because the IBM Tivoli Workload Scheduler for z/OS
subsystem SUBSYS has not been initialized. IBM Tivoli
Workload Scheduler for z/OS subsystems are
EQQE079E KEYWORD KEY HAS AN INVALID initialized during a z/OS IPL.
VALUE
System action: No event is created.
Explanation: The only valid values for the CREATE
and AVAIL keywords are YES, NO, or RESET or Problem determination: Check the system log for
abbreviations of YES, NO, or RESET. error messages issued during IPL that identify why the
IBM Tivoli Workload Scheduler for z/OS subsystem
System action: The event is not created. Processing was not initialized.
ends for current SRSTAT command. If SRSTAT is
invoked by the EQQEVPGM program, processing User response: If the command referred to the wrong
continues with the next statement. subsystem correct the input, and retry the command.

User response: If the event should be created, make System programmer response: If the IBM Tivoli
the necessary corrections and reissue the SRSTAT Workload Scheduler for z/OS subsystem should be
command. initialized the EQQINITF program must be executed
successfully. Ensure EQQINITF is located in a library in
the LNKLSTnn concatenation and IPL the z/OS system.
EQQE080E THE EQQMINOR PROGRAM
ABENDED WITH ABEND CODE
ABEND EQQE083E SUBSYSTEM SUBSYS IS NOT AN OPC
SYSTEM. NO EVENT IS CREATED
Explanation: This message is issued when a IBM
Tivoli Workload Scheduler for z/OS TSO command has Explanation: This message is issued when a IBM
failed due to an error when communicating with the Tivoli Workload Scheduler for z/OS TSO command has
IBM Tivoli Workload Scheduler for z/OS subsystem. failed because the subsystem that was referenced is not
a IBM Tivoli Workload Scheduler for z/OS subsystem.
Problem determination: If necessary, generate a dump
by allocating a SYSxDUMP data set to the TSO user’s System action: None.
address space, or by defining a slip trap, and reissue User response: Correct the command and retry.
the failing command.
User response: Contact your systems programmer. EQQE084E YOU ARE NOT AUTHORIZED TO
System programmer response: If the failing command UPDATE THE SPECIAL RESOURCE
contains an error, correct it and retry. If the error cannot SPECIFIED FOR SUBSYSTEM SUBSYS
be corrected, contact Customer Support for assistance. Explanation: An SRSTAT request to update a special
resource specified for subsystem SUBSYS failed because
EQQE081E R15 RETURN CODE R15 WAS the user making the request was not authorized to
RETURNED BY THE TSO SERVICE update the resource.
FACILITY. RETURN CODE RC, System action: The request is rejected.
REASON CODE RSN WERE ALSO
RETURNED User response: Contact your security administrator if
access is required.
Explanation: This message is issued when a IBM
Tivoli Workload Scheduler for z/OS TSO command has

74 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 User response: If authority is required contact your
EQQE085E RESDS IS NOT A VALID RESOURCE
security administrator.
DATASET NAME, NO EVENT IS
CREATED
EQQE090E EITHER WORKSTATION NAME OR
Explanation: The value specified for the resource data
DESTINATION MUST BE SPECIFIED
set keyword—RESDS was not valid. The keyword
value must be specified as CP or JS. Explanation: The current WSSTAT statement does not
define a workstation name (WSNAME) or a destination
System action: The request is ignored.
ID (DESTINATION). At lease one of WSNAME or
User response: Correct the input and resubmit the DESTINATION must be specified. Both can be
request. specified.
System action: The event is not created. The
EQQE086E THE RESDS KEYWORD MUST BE EQQEVPGM program continues processing any further
SPECIFIED event creation statements.
Explanation: The resource data set keyword—RESDS User response: If the event should be created, make
was not specified. the necessary corrections and reissue the command or
resubmit the EQQEVPGM batch job.
System action: The request is ignored.
User response: Supply the RESDS keyword and a
EQQE091E THE FOLLOWING USER DEFINED
valid value and resubmit the request.
EVENT RECORD CANNOT BE USED
BECAUSE THE OPCTOKEN VALUE IS
EQQE087E YOU ARE NOT AUTHORIZED TO NOT CONSISTENT WITH THE
REQUEST A BACKUP OF THE RESDS VALUE(S) SPECIFIED IN THE ADID,
RESOURCE DATASET SPECIFIED FOR IA, JOBNAME AND/OR OPNUM
SUBSYSTEM SUBSYS KEYWORDS: EXITREC

Explanation: In order to request a backup of a IBM Explanation: An invalid user-defined event record has
Tivoli Workload Scheduler for z/OS resource data set, been found on the Event Manager’s work queue. An
update authority to the BKP fixed resource is required. OPSTAT event definition statement defined an
You do not have this authority. OPCTOKEN value that is not consistent with some or
all of the values specified in the ADID, IA, JOBNAME,
System action: The request is ignored. AND OPNUM keywords. The operation cannot be
User response: If authority is required contact your identified by the scheduler.
security administrator. System action: The incorrect event record is returned
to the Event Manager’s free queue without any further
EQQE088E YOU ARE NOT AUTHORIZED TO processing.
UPDATE THE OPERATION, SUBRES User response: If a new event should be created,
CHECK FAILED AT SUBSYSTEM make the necessary corrections and reissue the
SUBSYS command or resubmit the EQQEVPGM batch job.
Explanation: An OPSTAT requests to update an
operation in subsystem SUBSYS failed because the user EQQE092E THE FOLLOWING USER DEFINED
making the request was not authorized to update the EVENT RECORD CANNOT BE USED
SUBRES subresource. BECAUSE THE CURRENT
System action: The request is rejected. OPERATION STATUS IS NOT
STARTED, READY OR ARRIVING:
User response: If authority is required contact your EXITREC
security administrator.
Explanation: An invalid user-defined event record has
been found on the Event Manager’s work queue. An
EQQE089E YOU ARE NOT AUTHORIZED TO OPSTAT event definition statement specified a new
UPDATE STATUS OF WORKSTATION status of SQ or SS, but the current operation status is
WSNAME FOR SUBSYSTEM SUBSYS not started (S), ready (R), or arriving (A).
Explanation: A WSSTAT request to update the status System action: The incorrect event record is returned
of workstation WSNAME in subsystem SUBSYS failed to the Event Manager’s free queue without any further
because the user making the request was not processing. The operation status is not changed.
authorized to update the RL.WSSTAT subresource.
User response: If a new event should be created,
System action: The request is rejected. make the necessary corrections and reissue the
command or resubmit the EQQEVPGM batch job.

Chapter 9. EQQEnnn Messages 75

EQQE093E THE FOLLOWING USER DEFINED EQQE096E THE STATUS KEYWORD MUST BE
EVENT RECORD CANNOT BE USED SPECIFIED
BECAUSE THE WORKSTATION
Explanation: The current WSSTAT event definition
WSNAME IS NOT A COMPUTER OR
statement does not define any status. This keyword is
WTO WORKSTATION: EXITREC
required.
Explanation: An invalid user-defined event record has
System action: The event is not created. The
been found on the Event Manager’s work queue. An
EQQEVPGM program continues processing the next
event generated by WSSTAT or EQQUSINW specified a
event creation statement.
workstation that is not a computer, or WTO
workstation. User response: If the event should be created, make
the necessary corrections and resubmit the
System action: The incorrect event record is returned
EQQEVPGM batch job.
to the Event Manager’s free queue without any further
processing. The workstation status is not changed.
EQQE097E THE FOLLOWING USER DEFINED
User response: If a new event should be created,
EVENT RECORD CANNOT BE USED
make the necessary corrections and reissue the
BECAUSE THE SPECIFIED TOKEN
command or resubmit the EQQEVPGM batch job.
VALUE DOES NOT MATCH ANY
OPERATION IN THE CURRENT PLAN:
EQQE094E THE FOLLOWING USER DEFINED EXITREC
EVENT RECORD CANNOT BE USED
Explanation: An invalid user-defined event record has
BECAUSE THE WORKSTATION
been found on the Event Manager’s work queue. An
WSNAME DOES NOT MATCH THE
OPSTAT event definition statement defined a TOKEN
DESTINATION DEST: EXITREC
value that does not match any operation in the current
Explanation: An invalid user-defined event record has plan. The operation cannot be identified by the
been found on the Event Manager’s work queue. An scheduler.
WSSTAT event definition statement specified a
System action: The incorrect event record is returned
workstation that did not match the destination
to the Event Manager’s free queue without any further
specified in the event.
processing.
System action: The incorrect event record is returned
User response: If a new event should be created,
to the Event Manager’s free queue without any further
make the necessary corrections and reissue the
processing. The workstation status is not changed.
command or resubmit the EQQEVPGM batch job.
User response: If a new event should be created,
make the necessary corrections and reissue the
EQQE098E THE FOLLOWING USER DEFINED
command or resubmit the EQQEVPGM batch job.
EVENT RECORD CANNOT BE USED
BECAUSE THE CURRENT
EQQE095E THE FOLLOWING USER DEFINED OPERATION STATUS IS SS: EXITREC
EVENT RECORD CANNOT BE USED
Explanation: An invalid user-defined event record has
BECAUSE THE DESTINATION DEST
been found on the Event Manager’s work queue. An
IS NOT SPECIFIED IN THE
OPSTAT event definition statement specifies a new
ROUTOPTS INITIALIZATION
status Q for an operation which has a current status SS.
STATEMENT: EXITREC
This is not allowed
Explanation: An invalid user-defined event record has
System action: The incorrect event record is returned
been found on the Event Manager’s work queue. An
to the Event Manager’s free queue without any further
WSSTAT event definition statement specified a
processing. The workstation status is not changed.
destination which was not specified in the ROUTOPTS
initialization statement. User response: If a new event should be created,
make the necessary corrections and reissue the
System action: The incorrect event record is returned
command or resubmit the EQQEVPGM batch job.
to the Event Manager’s free queue without any further
processing. The workstation status is not changed.
EQQE099E THE FOLLOWING USER DEFINED
User response: If a new event should be created,
EVENT RECORD CANNOT BE USED
make the necessary corrections and reissue the
BECAUSE THE ALTERNATE
command or resubmit the EQQEVPGM batch job.
WORKSTATION WSNAME DOES NOT
EXIST: EXITREC
Explanation: An invalid user-defined event record has
been found on the Event Manager’s work queue. A

76 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

WSSTAT event definition statement specified an System programmer response: Check that the
alternative workstation that did not exist. destination is active. If it is, check that the event writer
at the destination is active.
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. EQQE103W TRACKER SUBS AT DESTINATION
DEST LOST THE FUNC
User response: If a new event should be created,
make the necessary corrections and reissue the Explanation: This message is issued for reporting
command or resubmit the EQQEVPGM batch job. purposes on the controller message log, EQQMLOG,
when the ROUTOPTS PULSE processing is active for
Tracker systems on IBM Tivoli Workload Scheduler for
EQQE100E THE CURRENT WORKSTATION
z/OS release 3 level or higher. The message indicates
WSNAME CANNOT BE USED AS
that the FUNC subtask in the SUBS subsystem on the
ALTERNATE TO ITSELF. REROUTE IS
z/OS system represented in IBM Tivoli Workload
NOT IN EFFECT FOR THE
Scheduler for z/OS by the DEST destination has
WORKSTATION
abnormally terminated.
Explanation: A WSSTAT event definition statement
System action: No action is taken by the controller.
specified an alternative workstation that was the same
as the current workstation. System programmer response: Check the message log
for the indicated Tracker address space and take
System action: Reroute is not in effect for the actual
appropriate actions to restart the failed subtask.
workstation. The workstation status is changed.
User response: None.
EQQE104E KEYWORD KEYW MISSING. IT IS
REQUIRED FOR SUBRESOURCE
EQQE101E KEYWORD KEY HAS AN INVALID SUBRES CHECKING AT SUBSYSTEM
VALUE SUBSYS

Explanation: The only valid values for the Explanation: Authority checking for subresource
QUANTITY and DEVIATION keywords are KEEP, SUBRES is specified in the AUTHDEF statement for
RESET or a numeric value. subsystem SUBSYS. A valid subresource name cannot
be built for protection of the operation when keyword
System action: The event is not created. Processing KEYW is omitted. When EQQEVPGM processes a TSO
ends for current SRSTAT command. If SRSTAT is command, for example, OPINFO, OPSTAT, JSUACT or
invoked by the EQQEVPGM program, processing WSSTAT, it checks the authority of the requestor
continues with the next event creation statement. analyzing the contents of AUTHDEF statements of the
User response: If the event should be created, make scheduler. To do this check it also necessary that a
the necessary corrections and reissue the SRSTAT certain keyword KEYW should be specified in the
command. previous TSO statement.
System action: No event is created for the subsystem
EQQE102W PULSE LOST FROM TRACKER SUBS identified in the message text. If SUBSYSTEM(MSTR)
AT DESTINATION DEST was specified in the input, the request is directed to the
next scheduler subsystem. If event creation failed for
Explanation: This message indicates that handshake one or more subsystems, return code 4 is set. If it failed
processing, the frequency for which is determined by for all subsystems or for a subsystem specifically
the PULSE keyword of the ROUTOPTS statement, has identified in the input, return code 8 is set.
terminated for the indicated Tracker system. When
handshake processing is in use, each connected Tracker System programmer response: Add the keyword and
system sends an identification (ID) event to the resubmit the EQQEVPGM job for the failing subsystem.
controller at the specified interval. If the controller
detects that a Tracker system has missed two EQQE105W DATA STORE FUNCTIONALITY IS
consecutive PULSE intervals, this message is issued. ACTIVE ON CONTROLLER BUT NOT
SUBS is the name of the Tracker (the subsystem name ON TRACKER
for z/OS trackers). DEST is the destination for this
system, as defined in the ROUTOPTS statement. Explanation: The controller is running with
DSTTASK(YES), that is, SYSOUT retrieval is done via
System action: If the destination DEST is defined the Data Store, but a minimum of one tracker is
using shared DASD (submit/release) data set running in an environment where the Data Store is not
communication, this destination is forced Offline by the active.
controller. For other communication methods, no action
is taken. System action: None
User response: Contact your system programmer.

Chapter 9. EQQEnnn Messages 77

 System programmer response: Check that the processing. This error might be a symptom that the
EQQSSCMx level of code is correct. Symphony file and the scheduler Current Plan VSAM
data sets are out of sync.
EQQE106I UNABLE TO UPDATE OPER DOA: | User response: Check if in the Symphony file any
APPL=APPL, INPUT ARR=ARRTIME, | operation is present that is not present in the Current
OPNR=OPNU | Plan. Run Symphony Renew to produce a new
| Symphony File synchronized with the Current Plan.
Explanation: An error occurred during the DOA
updating of the operation.
EQQE110W THE EVENT MANAGER WAS
System action: The extended status passed to
UNABLE TO SET STATUS STATUS
EQQUX007 is set to Z.
FOR OPERATION OPERNUM, IN
User response: None. APPLICATION APPL, IA=ARRTIME.
THE OPERATION IS SET INTO OUT
OF SEQUENCE STATUS
EQQE107I OPC-WLM SUCCESSFULLY
PROMOTED JBNAM: JBNUM IN HI Explanation: An event record, originating from a
PERFORMANCE CLASS fault-tolerant workstation, indicates that an operation
started before predecessors are completed or resources
Explanation: The job promotion process has ended allocated. This error is probably produced by
correctly. The job is now in a higher-performance dependencies added after the job was started on the
service class defined for the scheduler jobs. agent.
System action: None. System action: The operation is set in Error status
User response: None. with error code OSEQ (Out Of Sequence).
User response: Check the status of the job on the
EQQE108E THE EVENT MANAGER HAS agent and, when the predecessors are completed,
IGNORED THE FOLLOWING FTW manually set the operation to the correct status.
EVENT RECORD BECAUSE NO
MATCHING OPERATION COULD BE EQQE120W WRONG TYPE OPERAND WAS
FOUND IN CURRENT PLAN: EXITREC SPECIFIED IN THE JSUACT
Explanation: An invalid event record originated from COMMAND POSSIBLE VALUES ARE
a fault-tolerant workstation has been found on the H=HOST/F=FTW/B=BOTH
Event Manager work queue. No operation in the Explanation: The keyword TYPE on command
current plan data set could be found that matches the JSUACT contains a wrong value. The possible values
operation defined by the event record. are H for Host, F for FTW and B for both
System action: The incorrect event is returned to the environments.
Event Manager free queue without any further System action: The request is rejected.
processing. This error might be a symptom that the
Symphony file and the scheduler Current Plan VSAM User response: Insert the right value.
data sets are out of sync.
| User response: Check if in the Symphony file any EQQE111W THE EVENT MANAGER WAS
| operation is present that is not present in the Current UNABLE TO SET STATUS STATUS
| Plan. Run Symphony Renew to produce a new FOR OPERATION OPERNUM, IN
| Symphony File synchronized with the Current Plan. APPLICATION APPL, IA=ARRTIME.
THE EVENT IS DISCARDED

EQQE109E THE EVENT MANAGER HAS Explanation: An event record, originating from a
IGNORED THE FOLLOWING FTW fault-tolerant workstation, reports a status transition
EVENT RECORD BECAUSE THE that is not compatible with the actual operation status.
WORK STATION NAME WSNAME IS This error is probably produced by setting the status of
NOT RECOGNIZED: EXITREC running jobs manually or by operations already set out
of sequence.
Explanation: An invalid event record originated from
a fault-tolerant workstation has been found on the System action: The event is discarded and the
Event Manager work queue. No workstation in the operation status is left as it is before.
current plan data set could be found that matches the
User response: Check the status of the job on the
workstation defined by the event record.
agent and, when the predecessors are completed,
System action: The incorrect event is returned to the manually set the operation to the correct status.
Event Manager free queue without any further

78 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 EQQE112E THE EVENT MANAGER WAS | EQQE116E WSNAME IS NOT A
UNABLE TO SET STATUS STATUS | FAULT-TOLERANT WORKSTATION.
FOR THE FAULT-TOLERANT | THE COMMAND KEYWORD IS
WORKSTATION WSNAME | INCORRECT
Explanation: An event record, originating from a | Explanation: An event record, originating from a
WSSTAT command, tried to set a status of a | WSSTAT command, used keyword CMD (command) to
fault-tolerant workstation to Failed, which is not | set STATUS or LINK, when the workstation is not a
compatible with the actual workstation type. | fault-tolerant workstation.
System action: The event is discarded and the | System action: The request is rejected.
workstation status is left as it was before.
| User response: None
User response: None.
| EQQE117E WSNAME IS NOT A
| EQQE113W AN ERROR HAS OCCURRED | FAULT-TOLERANT WORKSTATION.
| SENDING THE SCRIPT TO THE | THE MANAGES KEYWORD IS
| DISTRIBUTED AGENT FOR | INCORRECT
| OPERATION OPERATION, IN
| APPLICATION APPL, IA=ARRTIME.
| Explanation: An event record, originating from a
| THE OPERATION STATUS IS RESET
| WSSTAT command, used the MANAGES keyword to
| TO READY
| change the domain, when the workstation is not a
| fault-tolerant workstation.
| Explanation: The submission of operation
| OPERATION in occurrence APPL with Input Arrival | System action: The request is rejected.
| ARRTIME failed while the engine was sending the | User response: None
| script for the operation to the distributed agent.
| System action: The Workstation Analyzer task will | EQQE118E THE EVENT MANAGER HAS
| retry the job submission for a maximum of 10 times. | IGNORED THE FOLLOWING FTW
| User response: If the error persists, contact your | EVENT RECORD BECAUSE IT WAS
| system programmer. | UNABLE TO RETRIEVE RECOVERY
| INFORMATION: EXITREC
| System programmer response: Check the controller
| and the server MLOG for the error causing the failure. | Explanation: An invalid event record coming from a
| fault-tolerant workstation was found in the work queue
| of the Event Manager. No recovery information could
| EQQE114E THE EVENT MANAGER WAS | be found in the current plan record 24 that matches the
| UNABLE TO SET AN ALTERNATE | operation defined by the event record.
| WORKSTATION FOR THE
| FAULT-TOLERANT WORKSTATION
| System action: The incorrect event is returned to the
| WSNAME.
| Event Manager free queue without any further
| processing. This error may be a symptom that the
| Explanation: An event record, originating from a | Symphony file and the scheduler Current Plan VSAM
| WSSTAT command, tried to set alternate workstation | data sets are out of sync.
| for a fault-tolerant workstation. This is not compatible
| with the actual workstation type.
| User response: Check the Symphony file for an
| operation that is not present in the current plan. Run
| System action: The request is discarded. | Symphony Renew to produce a new Symphony File
| and to synchronize it with the current plan.
| User response: None.

| EQQE119E THE FOLLOWING USER DEFINED

| EQQE115E KEYWORDS STATUS, CMD AND
| EVENT RECORD CANNOT BE USED
| MANAGES MUST BE MUTUALLY
| BECAUSE THE ALTERNATE
| EXCLUSIVE
| WORKSTATION WSNAME IS A
| Explanation: An event record, originating from a | FAULT-TOLERANT WORKSTATION.
| WSSTAT command, tried to concurrently use the
| Explanation: An event record for changing the
| STATUS, CMD and MANAGES keywords. This is not
| workstation status, tried to assign a fault-tolerant
| possible. You can only use one of the three.
| workstation as alternate workstation and to reroute
| System action: The request is discarded. | operations with the REROUTE value.

| User response: None. | System action: The request is discarded.

Chapter 9. EQQEnnn Messages 79

| User response: None.
EQQE204I SUBMIT FUNCTION INACTIVATED
FOR ENV
| EQQE119E THE FOLLOWING USER DEFINED
Explanation: The job submit deactivate command has
| EVENT RECORD CANNOT BE USED
been accepted and executed.
| BECAUSE THE ALTERNATE
| WORKSTATION WSNAME IS A System action: None.
| FAULT-TOLERANT WORKSTATION.
User response: None.
| Explanation: An event record for changing the
| workstation status, tried to assign a fault-tolerant
EQQE210I TWS FOR z/OS HAS UPDATED THE
| workstation as alternate workstation and to reroute
GMT OFFSET ON SYSTEM SYSID
| operations with the REROUTE value.
Explanation: On the following system the system time
| System action: The request is discarded.
was changed, TWS for z/OS generated an event to
| User response: None. change it’s GMT offset through the tracker.
System action: The tracker generates the event and
EQQE200W JSUACT REQUEST IGNORED. modifies the GMT offset, on the controller site, if the
SUBTASK HAS TERMINATED. event was created in the same system the controller
will manage it and signal the change in it’s MLOG. If
Explanation: The job submit activate/deactivate
the event was created in another system the controller
command has been ignored because the controller
signals the message on it’s MLOG.
normal mode manager (NMM) task has terminated.
User response: None.
System action: The request is rejected.
User response: Review the message log for messages
EQQE300E FOLLOWING EVENT HAS BEEN
that could explain why NMM is unavailable.
IGNORED BECAUSE REQUEST
TOKEN DID NOT MATCH EXITRC
EQQE201W SUBMIT FUNCTION ALREADY
Explanation: The Event Manager has received an
ACTIVE FOR ENV
event for a restart and cleanup process that does not
Explanation: The job submit activate command has match the token used in the original dialogue request.
been ignored because the job submit function is already
System action: The Event Manager continues normal
active and enabled for service.
operation with the next queued event.
System action: The request is ignored.
System programmer response: Save the message log
User response: None. containing this message and the JT files with the event,
then contact Customer Support.

EQQE202W SUBMIT FUNCTION ALREADY

INACTIVE FOR ENV EQQE301E FOLLOWING EVENT HAS BEEN
IGNORED BECAUSE DOA
Explanation: The job submit deactivate command has OPERATION BLOCK WAS NOT
been ignored because the job submit function is already FOUND EXITREC
inactive and disabled for service.
Explanation: The Event Manager has received an
System action: The request is rejected. event for a restart and cleanup process for which no
User response: None. matching DOA can be found.
System action: The Event Manager continues normal
EQQE203I SUBMIT FUNCTION ACTIVATED FOR operation with the next queued event.
ENV User response: Save the message log containing this
Explanation: The job submit activate command has message and the JT files with the event and then
been accepted and executed. contact Customer Support.

System action: None.

User response: None.

80 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

Chapter 10. EQQFnnn Messages
initialization statement and the initialization statement
EQQF000E DATA ROUTER TASK HAS IGNORED
defined for the member.
AN INVALID QUEUE ELEMENT: DQE
User response: Contact your system programmer.
Explanation: A queue element did not contain the
correct eye catcher or version number. System programmer response: Restart the standby
system as a tracker or update the controller
System action: The data router task does not process
ROUTOPTS statement.
the invalid element, but continues normal processing.
User response: Contact your system programmer.
EQQF004E DATA ROUTER TASK ABENDED
System programmer response: Save the IBM Tivoli WHEN PROCESSING THE
Workload Scheduler for z/OS message log and contact FOLLOWING QUEUE ELEMENT DQE
Customer Support.
Explanation: An abend prevented the data router task
from processing a queue element.
EQQF001I DATA ROUTER TASK
System action: z/OS recovery/termination is
INITIALIZATION IS COMPLETE
requested to generate a dump. The data router task
Explanation: The data router task has successfully attempts to continue normal processing.
completed initialization.
Problem determination: Review the IBM Tivoli
System action: Data router task processing starts. Workload Scheduler for z/OS message log data set, the
EQQDUMP data set, and the SYSMDUMP data set to
User response: None.
determine the cause of the problem.
User response: Contact your system programmer.
EQQF002E DATA ROUTER TASK
INITIALIZATION FAILED System programmer response: Save the message log
and dump data sets and contact Customer Support.
Explanation: The data router task could not acquire
the resources required for normal operation.
EQQF005E DATA ROUTER TASK QUEUE
System action: Data router task processing is
POINTERS ARE DESTROYED, RTRQ
terminated.
IS LOST
Problem determination: Review previous messages in
Explanation: The data router task abended while
the IBM Tivoli Workload Scheduler for z/OS message
processing elements on RTRQ because the queue
log.
chaining is invalid.
User response: Contact your system programmer.
System action: z/OS recovery/termination is
System programmer response: Correct all errors and requested to generate a dump. All elements on RTRQ
restart the data router task. are skipped, but the data router task attempts to
continue normal processing.

EQQF003E MEMBER MEMBER IS DEFINED AS A Problem determination: Review the IBM Tivoli
DESTINATION IN ROUTOPTS BUT IS Workload Scheduler for z/OS message log data set, the
STARTED AS A STANDBY SYSTEM EQQDUMP data set, and the SYSMDUMP data set to
determine the cause of the problem.
Explanation: An XCF member has joined the same
XCF group as the controller. This member was defined IBM Tivoli Workload Scheduler for z/OS
as a tracker in the ROUTOPTS but has been started as administrator response: Save the message log and
a IBM Tivoli Workload Scheduler for z/OS standby dump data sets and contact Customer Support.
subsystem.
System action: IBM Tivoli Workload Scheduler for EQQF006I UNKNOWN XCF MEMBER MEMBER
z/OS does not recognize the joined standby member as HAS JOINED THE GROUP. IT IS
a destination. No communication takes place between IGNORED
the controller and the standby member.
Explanation: A member that is not defined in
Problem determination: Check the ROUTOPTS ROUTOPTS has joined the XCF group.
System action: The controller ignores the joined

© Copyright IBM Corp. 1991, 2003 81

member. No workload or event communication reader task and event writer task
between the controller and the tracker takes place. (when EWSEQNO(n)), to stop reading
from the event data sets or adding to
Problem determination: Check the XCFOPTS
the DRTQ.
initialization statement of the IBM Tivoli Workload
Scheduler for z/OS tracker system and check the DEACTIVATED
ROUTOPTS initialization statement of the controller. The data router task has detected that
the event manager has processed all
IBM Tivoli Workload Scheduler for z/OS
events on the event manager queue
administrator response: Verify that the tracker system
(MGRQ), so the data router task has
has been defined with an XCF member name that
posted each locally attached event
corresponds to the definition in ROUTOPTS. Add the
reader task and event writer task
member name to ROUTOPTS and restart the controller.
(when EWSEQNO(n)), to start reading
from the event data sets or adding to
EQQF007I XCF MEMBER MEMBER HAS JOINED the DRTQ. The data router task has
THE GROUP. THE DESTINATION also built and sent a DQE request
WILL BE REPORTED ACTIVE (type RTQ) to each remote (NCF
and/or XCF) linked tracker, where
Explanation: A IBM Tivoli Workload Scheduler for the remote data router task posts each
z/OS tracker system has joined the same XCF group as attached event reader task and event
the controller. The member is defined as an XCF writer task (when EWSEQNO(n)), to
destination in the ROUTOPTS initialization statement. start reading from the event data sets
System action: The controller reports the destination or adding to the DRTQ.
as active. Work can be scheduled at workstations System action: IBM Tivoli Workload Scheduler for
defining this destination. z/OS processing continues.
User response: None User response: None. This message is for information
only.
EQQF008I XCF MEMBER MEMBER HAS JOINED
THE GROUP AS STANDBY FOR THE EQQF010I INVALID RETURN CODE RETC FROM
OPC CONTROLLER EQQUX009 IS IGNORED
Explanation: A IBM Tivoli Workload Scheduler for Explanation: User exit EQQUX009 passed an invalid
z/OS standby subsystem has joined the same group as return code back to the data router task. The return
the controller. code is ignored.
System action: Controller processing continues as System action: Normal processing continues. The
normal. return code is treated as return code 0.
User response: None User response: Inform your system programmer.
System programmer response: Investigate why
EQQF009I ADAPTIVE PACING ON EVENT EQQUX009 returned an invalid return code.
INFLOW MODE
Explanation: The MODE can be ACTIVATED or EQQF011E THE OPERATION INITIALIZATION
DEACTIVATED. EXIT USRX HAS ABENDED WHILE
ACTIVATED The data router has detected that the PROCESSING OPERATION OPN IN
maximum number of queue elements APPLICATION APPL WITH IA IA
on the event manager queue (MGRQ) SCHEDULED ON WORKSTATION
were already in use when the data WSNAME. THE EXIT IS MARKED AS
router task attempted to add NOT USABLE.
incoming events to the MGRQ. The Explanation: The exit abended while processing. IBM
data router task has posted each Tivoli Workload Scheduler for z/OS does not try to call
locally attached event reader task and it again unless the data router task is restarted. The exit
event writer task (when is flagged as not executable.
EWSEQNO(n)), to stop reading from
the event data sets or adding to the System action: The current operation status is set
DRTQ. The data router task has also according to what is specified in the SUBFAILACTION
built and sent a DQE request (type JTOPTS parameter.
RTQ) to each remote (NCF or XCF)
System programmer response: Correct all errors in
linked tracker, where the remote data
the exit and restart the data router task.
router task posts each attached event

82 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQF012I PROCESSING RETURN CODE RETC EQQF015I XCF TYPE MEMBER MEMBER HAS
FROM EQQUX009 LEFT THE GROUP. REASON: REASON
Explanation: User exit EQQUX009 passed a return Explanation: The XCF link to TYPE with member
code, RETC, that is not 0. The data router task name MEMBER has been disconnected. The REASON is
processes the return codes and continues normal either that the linked IBM Tivoli Workload Scheduler
processing. for z/OS address space terminated or the entire
scheduler system terminated.
System action: The return code is processed as
follows: System action: The transmission of data (such as
4 The current operation status is set according to event records) through the XCF link is postponed. The
the specification in the SUBFAILACTION transmission of data resumes when the XCF member
keyword in the JTOPTS initialization rejoins the group.
statement.
Problem determination: If this message is not
8 The operation status is set according to the
expected, review the message log (EQQMLOG) and the
specification in the SUBFAILACTION keyword
SYSLOG of the linked IBM Tivoli Workload Scheduler
in the JTOPTS initialization statement. All
for z/OS MEMBER to determine the cause of the
workstations specifying the destination are set
outage.
to offline status.
User response: Contact your system programmer.
User response: Inform your system programmer.
System programmer response: This is a IBM Tivoli
System programmer response: Investigate why
Workload Scheduler for z/OS informational message.
EQQUX009 returned the return code.
If this message was expected and:
EQQF013I EXIT EQQUX009 IS NOT LOADED OR v The TYPE indicated CONTROLLER and message
HAS BEEN DISABLED EQQW070I was also issued when the controller was
restarted, you should consider increasing the size of
Explanation: User exit EQQUX009 has not been the tracker’s event data set.
loaded or has abended previously. The operations
v The TYPE indicated TRACKER and message
scheduled to run on a workstation that specifies a
EQQZ035I was also issued when the tracker was
user-defined destination are routed.
restarted, you should consider increasing the size of
System action: The operation status is set according to the ECSA buffer (SYS1.PARMLIB(IEFSSNxx)).
what is specified in the SUBFAILACTION keyword on
the JTOPTS initialization parameter.
| EQQF016E THE TCP/IP TASK QUEUE IS FULL.
User response: Issue a WSSTAT command, or use the | THE DESTINATION WILL BE SET TO
workstation dialog, to vary the destination | OFFLINE STATUS
workstations offline.
| Explanation: The TCP/IP queue is full.
System programmer response: Investigate why
EQQUX009 is not loaded. If a previous abend caused
| System action: The scheduler sets the corresponding
the exit to be disabled, correct the error and stop/start
| operation to the status specified in the
the IBM Tivoli Workload Scheduler for z/OS subsystem
| SUBFAILACTION keyword value in the JTOPTS
to get the exit reloaded.
| initialization statement.
| System programmer response: Try to find out why
EQQF014E THE EXTERNAL ROUTER QUEUE IS
| the TCP/IP task is not processing.
FULL. USER DESTINATION WILL BE
SET TO OFFLINE STATUS
Explanation: The external router queue is full. IBM
Tivoli Workload Scheduler for z/OS sets the destination
to offline status and sets 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.

Chapter 10. EQQFnnn Messages 83

84 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 11. EQQFxxx Messages
(ddname EQQDUMP) for further information.
EQQFA00E VSAM ERROR FUNC: FUNC RC: RC
REASON: REASON User response: Contact your system programmer.
Explanation: A VSAM operation failed. FUNC System programmer response: Contact Customer
specifies which kind of operation, for example, OPEN, Support.
CLOSE, and so on. RC and REASON are the VSAM
return and reason codes.
EQQFA03E BAD PARAMETER - REASON:
System action: If the VSAM error could not be REASON
bypassed the Data Store is terminated. See Chapter 38,
“Reason Codes”, on page 463 for a list of the REASON Explanation: This message describes an internal error
codes. of the Data Store and is addressed to Customer
Support. One or more parameters passed to a called
Problem determination: Refer to the dump data set service are invalid.
(ddname EQQDUMP) for further information. This file
contains a copy of the control block. System action: The involved Data Store task is closed.
If the involved task is either the JES Queue or the
User response: Contact your system programmer. Database task, the Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of
System programmer response: Contact Customer
the REASON codes.
Support.
Problem determination: Refer to the dump data set
(ddname EQQDUMP) for further information. This file
EQQFA01E BAD CONTROL BLOCK REASON: -
contains a copy of the value of the invalid parameter.
REASON: REASON
User response: Contact your system programmer.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer System programmer response: Contact Customer
Support. The first field of the specified control block is Support.
invalid. It does not contain the name of the control
block.
EQQFA04E BAD REQUEST - REASON: REASON
System action: The involved Data Store task is closed.
If the involved task is either the JES Queue or the Explanation: This message describes an internal error
Database task, the Data Store is terminated. See of the Data Store and is addressed to Customer
Chapter 38, “Reason Codes”, on page 463 for a list of Support. The specified address for the control block is
the REASON codes. invalid.

Problem determination: Refer to the dump data set System action: The involved Data Store task is closed.
(ddname EQQDUMP) for further information. This file If the involved task is either the JES Queue or the
contains a copy of the control block. Database task, the Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of
User response: Contact your system programmer. the REASON codes.
System programmer response: Contact Customer Problem determination: Refer to the dump data set
Support. (ddname EQQDUMP) for further information. This file
contains the value of the invalid request field.
EQQFA02E BAD INSTANCE - REASON: REASON User response: Contact your system programmer.
Explanation: This message describes an internal error System programmer response: Contact Customer
of the Data Store and is addressed to Customer Support.
Support. The specified instance address for the called
service is invalid.
EQQFA05E BAD SYSOUT DATABASE - REASON:
System action: The involved Data Store task is closed. REASON
If the involved task is either the JES Queue or the
Database task, the Data Store is terminated. See Explanation: Generally there is a mismatch between
Chapter 38, “Reason Codes”, on page 463 for a list of the primary keys data set and data files, for example,
the REASON codes. the Data Store was started without all the
previously-used data files and containing the sysout
Problem determination: Refer to the dump data set listed by the primary key file.

© Copyright IBM Corp. 1991, 2003 85

System action: The Data Store is terminated. See Problem determination: Refer to the dump data set
Chapter 38, “Reason Codes”, on page 463 for a list of (ddname EQQDUMP) for further information.
the REASON codes.
User response: Contact your system programmer.
Problem determination: Refer to the dump data set
System programmer response: Contact Customer
(ddname EQQDUMP) for further information.
Support.
User response: Contact your system programmer.
System programmer response: Check that, when the EQQFA10E DETACH ERROR - REASON: REASON
Data Store was started, it was pointing to the correct
Explanation: This message describes an internal error
primary key and data files. If no error is found, contact
of the Data Store and is addressed to Customer
Customer Support.
Support. An error occurred when the Data Store
attempted to detach a subtask.
EQQFA06E IS EMPTY - REASON: REASON
System action: The involved Data Store task is closed.
Explanation: This message describes an internal error If the involved task is either the JES Queue or the
of the Data Store and is addressed to Customer Database task, the Data Store is terminated. See
Support. An internal objects list was found to be empty. Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes.
System action: The involved Data Store task is closed.
If the involved task is either the JES Queue or the Problem determination: Review earlier messages in
Database task, the Data Store is terminated. See the Data Store message log and SYSLOG data sets to
Chapter 38, “Reason Codes”, on page 463 for a list of determine the cause of the error.
the REASON codes.
User response: Contact your system programmer.
Problem determination: Refer to the dump data set
System programmer response: If possible correct all
(ddname EQQDUMP) for further information.
errors and restart the Data Store. If the error persists,
User response: Contact your system programmer. contact Customer Support.
System programmer response: Contact Customer
Support. EQQFA11E NOT ACTIVE - REASON: REASON
Explanation: This message describes an internal error
EQQFA07E NOT FOUND - REASON: REASON of the Data Store and is addressed to Customer
Support. A component that should be active was found
Explanation: This message describes an internal error
in an inactive state.
of the Data Store and is addressed to Customer
Support. An internal object was not found by a search System action: The involved Data Store task is closed.
operation. If the involved task is either the JES Queue or the
Database task, the Data Store is terminated. See
System action: The involved Data Store task is closed.
Chapter 38, “Reason Codes”, on page 463 for a list of
If the involved task is either the JES Queue or the
the REASON codes.
Database task, the Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of Problem determination: Refer to the dump data set
the REASON codes. (ddname EQQDUMP) for further information.
Problem determination: Refer to the dump data set User response: Contact your system programmer.
(ddname EQQDUMP) for further information.
System programmer response: Contact Customer
User response: Contact your system programmer. Support.
System programmer response: Contact Customer
Support. EQQFA12E NOT READY - REASON: REASON
Explanation: This message describes an internal error
EQQFA08E NOT INITIALIZED - REASON: of the Data Store and is addressed to Customer
REASON Support. A data file or primary index was found not
ready to be used, for example, not logically open.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer System action: The Data Store is terminated
Support. A data file was not found in an initialized
Problem determination: Refer to the dump data set
state.
(ddname EQQDUMP) for further information.
System action: The Data Store is terminated See
User response: Contact your system programmer.
Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes.

86 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

System programmer response: Contact Customer
EQQFA18E STOP IN PROGRESS
Support.
Explanation: The Data Store has received a command
while closing all the subtasks.
EQQFA13E INTERNAL ERROR - REASON:
REASON System action: The stop command is ignored.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer EQQFA19E COMMAND SYNTAX ERROR
Support. This is a generic internal failure of the
Explanation: The modify command is syntactically
Database task. It can occur during the shutdown of the
incorrect.
Data Store and indicates an internal mismatch. No data
is lost, but its handling can be deferred to the next System action: The modify command is ignored.
startup of the Data Store.
User response: Resubmit the modify command with
System action: The Data Store is terminated. See the correct syntax.
Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes.
EQQFA20E NOT OPEN - REASON: REASON
Problem determination: Refer to the dump data set
(ddname EQQDUMP) for further information. Explanation: This message describes an internal error
of the Data Store and is addressed to Customer
User response: Contact your system programmer. Support. A read or write operation was attempted on a
data file or index that was not previously opened.
System programmer response: Contact Customer
Support. System action: The Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes.
EQQFA14E BAD DATA - REASON: REASON
Problem determination: Refer to the dump data set
Explanation: This message describes an internal error
(with ddname EQQDUMP) for further information.
of the Data Store and is addressed to Customer
Support. A data file or a storage area was found in a User response: Contact your system programmer.
corrupted state.
System programmer response: Contact Customer
System action: The involved Data Store task is closed. Support.
If the involved task is either the JES Queue or the
Database task, the Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of EQQFA21E ERROR IN RPL GENERATION FOR
the REASON codes. VSAM ACCESS - REASON: REASON

Problem determination: Refer to the dump data set Explanation: During an RPL generation, the DIV
(ddname EQQDUMP) for further information. macro returns an error.

User response: Contact your system programmer. System action: The Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of
System programmer response: Use the Recover utility the REASON codes.
to recover the corrupted data file or use the Export
utility to make a copy of the previous backup copy. Problem determination: Review earlier messages in
After the recovery operation, if the problem persists, the Data Store message log and SYSLOG data sets to
contact Customer Support. determine the cause of the error. One possibility is that
there is a DFP error in the Data Store data files or
indexes.
EQQFA17E COMMAND ERROR
User response: Contact your system programmer.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer System programmer response: If possible correct all
Support. An internal error was detected while errors and restart the Data Store. If the error persists,
analyzing a modify comamnd. contact Customer Support.

System action: The modify command is ignored.

EQQFA22E ERROR IN POINT OPERATION ON
User response: Resubmit the modify command with VSAM FILE - REASON: REASON
the correct syntax.
Explanation: During a Point operation, the DIV macro
returns an error.
System action: The Data Store is terminated. See

Chapter 11. EQQFxxx Messages 87

Chapter 38, “Reason Codes”, on page 463 for a list of System action: The Data Store is terminated. See
the REASON codes. Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes.
Problem determination: Review earlier messages in
the Data Store message log and SYSLOG data sets to Problem determination: Refer to the dump data set
determine the cause of the error. One possibility is that (ddname EQQDUMP) for further information.
there is a DFP error in the Data Store data files or
User response: Contact your system programmer.
indexes.
System programmer response: Contact Customer
User response: Contact your system programmer.
Support.
System programmer response: If possible correct all
errors and restart the Data Store. If the error persists,
EQQFA27E INCORRECT PARAMETER IN
contact Customer Support.
MODIFY COMMAND
Explanation: The command could not be processed
EQQFA24E VSAM LOGICAL ERROR IN GET -
because one or more parameters on that command
REASON: REASON
could not be recognized or are out of range.
Explanation: During a Get operation, the DIV macro
System action: The command is ignored.
returns an error.
User response: Change the Modify command and
System action: The Data Store is terminated. See
resubmit the command.
Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes.
EQQFA28E TRANSMISSION ERROR FROM
Problem determination: Review earlier messages in
COMMUNICATION - REASON:
the Data Store message log and SYSLOG data sets to
REASON
determine the cause of the error. One possibility is that
there is a DFP error in the Data Store data files or Explanation: This message describes an internal error
indexes. of the Data Store and is addressed to Customer
Support. There was a generic transmission error in the
User response: Contact your system programmer.
communication subtask.
System programmer response: If possible correct all
System action: The requested data cannot be
errors and restart the Data Store. If the error persists,
transmitted. See Chapter 38, “Reason Codes”, on
contact Customer Support.
page 463 for a list of the REASON codes.
Problem determination: Review earlier messages in
EQQFA25E VSAM PHYSICAL ERROR IN GET -
the Data Store message log and SYSLOG data sets to
REASON: REASON
determine the cause of the error. One possible reason is
Explanation: During a Get operation, the DIV macro a communication failure in the SNA or the XCF
returns an error. communication task due to system resource definition
or an unavailable resource.
System action: The Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of User response: Contact your system programmer.
the REASON codes.
System programmer response: If possible correct all
Problem determination: Review earlier messages in errors and restart the Data Store. If the error persists,
the Data Store message log and SYSLOG data sets to contact Customer Support.
determine the cause of the error. One possibility is that
there is a DFP error in the Data Store data files or
EQQFA30E BAD STATUS - REASON: REASON
indexes.
Explanation: This message describes an internal error
User response: Contact your system programmer.
of the Data Store and is addressed to Customer
System programmer response: If possible correct all Support. An internal object was found in a corrupted
errors and restart the Data Store. If the error persists, state.
contact Customer Support.
System action: The involved Data Store task is closed.
If the involved task is either the JES Queue or the
EQQFA26E NO PARAMETER PASSED - REASON: Database task, the Data Store is terminated. See
REASON Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer Problem determination: Refer to the dump data set
Support. A calling function did not pass all the (ddname EQQDUMP) for further information.
required parameters to the called function.

88 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

User response: Contact your system programmer.
EQQFA37E ALREADY RESERVED - REASON:
System programmer response: Contact Customer REASON
Support.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer
EQQFA32E BAD PAGE - REASON: REASON Support. The Data Store attempted to reserve a
message that was already reserved for processing.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer System action: The involved Data Store task is closed.
Support. The database component detected a data page If the involved task is either the JES Queue or the
in a corrupted state. Database task, the Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of
System action: The Data Store is terminated. See the REASON codes.
Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes. Problem determination: Refer to the dump data set
(ddname EQQDUMP) for further information.
Problem determination: Refer to the dump data set
(ddname EQQDUMP) for further information. User response: Contact your system programmer.

User response: Contact your system programmer. System programmer response: Contact Customer
Support.
System programmer response: Use the Recover utility
to recover the corrupted data file or use the Export
utility to make a copy of the previous backup copy. EQQFA39E ERROR IN ACB GENERATION FOR
After the recovery operation, if the problem persists, VSAM ACCESS - REASON: REASON
contact Customer Support.
Explanation: During an ACB generation, the macro
returns an error.
EQQFA34E NO SPACE AVAILABLE - REASON:
System action: The Data Store is terminated. See
REASON
Chapter 38, “Reason Codes”, on page 463 for a list of
Explanation: There is no more space available in a the REASON codes.
data file or an index file.
Problem determination: Review earlier messages in
System action: The involved Database data file the Data Store message log and SYSLOG data sets to
subtask is closed. Data Store processing continues using determine the cause of the error. One possibility is that
the other data files. If this was the last available data there is a DFP error in the Data Store data files or
file, the Data Store is terminated. indexes.

Problem determination: Refer to the dump data set User response: Contact your system programmer.
(ddname EQQDUMP) for further information. The data
System programmer response: If possible correct all
files or the index files, or both, should be reallocated
errors and restart the Data Store. If the error persists,
with more space and the old data files should be
contact Customer Support.
copied using the IDCAMS Repro utility or the Data
Store Export/Import utility.
EQQFA42E NO DD FOUND - REASON: REASON
EQQFA36E ERROR DURING ENQUEUE - Explanation: In the Data Store startup procedure, all
REASON: REASON the ddnames and the files that are necessary for Data
Store life were not specified.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer System action: The Data Store is terminated See
Support. An enqueue operation failed. Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes.
System action: The involved Data Store task is closed.
If the involved task is either the JES Queue or the User response: Check the Data Store start up
Database task, the Data Store is terminated. See procedure.
Chapter 38, “Reason Codes”, on page 463 for a list of
Problem determination: Refer to the Installation Guide
the REASON codes.
for correct definitions of files.
Problem determination: Refer to the dump data set
(ddname EQQDUMP) for further information.
EQQFA43E VSAM OPEN ERROR - REASON:
User response: Contact your system programmer. REASON
System programmer response: Contact Customer Explanation: During an Open operation, the macro
Support. returns an error.

Chapter 11. EQQFxxx Messages 89

System action: The Data Store is terminated. See
EQQFA46E UNEXPECTED TASK END - REASON:
Chapter 38, “Reason Codes”, on page 463 for a list of
REASON
the REASON codes.
Explanation: A Data Store subtask ended
Problem determination: Review earlier messages in
unexpectedly.
the Data Store message log and SYSLOG data sets to
determine the cause of the error. One possibility is that System action: The involved Data Store task is closed.
there is a DFP error in the Data Store data files or If the involved task is either the JES Queue or the
indexes. Database task, the Data Store is terminated. See
Chapter 38, “Reason Codes”, on page 463 for a list of
User response: Contact your system programmer.
the REASON codes.
System programmer response: If possible correct all
Problem determination: Refer to the dump data set
errors and restart the Data Store. If the error persists,
(ddname EQQDUMP) for further information.
contact your system administrator.
User response: Contact your system programmer.
EQQFA44E GENERIC I/O ERROR - REASON: System programmer response: Contact Customer
REASON Support.
Explanation: During an I/O operation, an error was
detected. EQQFA47E ERROR DURING DYNALLOC
(ALLOCATION) - REASON: REASON
System action: The involved Data Store task is closed.
If the involved task is either the JES Queue or the Explanation: There was an error during a Dynalloc
Database task, the Data Store is terminated. See operation.
Chapter 38, “Reason Codes”, on page 463 for a list of
System action: The involved Data Store task is closed.
the REASON codes.
If the involved task is either the JES Queue or the
Problem determination: Review earlier messages in Database task, the Data Store is terminated. See
the Data Store message log and SYSLOG data sets to Chapter 38, “Reason Codes”, on page 463 for a list of
determine the cause of the error. One possibility is that the REASON codes.
there is a DFP error in the Data Store data files or
Problem determination: Refer to the dump data set
indexes.
(ddname EQQDUMP) for further information.
User response: Contact your system programmer.
User response: Contact your system programmer.
System programmer response: If possible correct all
System programmer response: Contact Customer
errors and restart the Data Store. If the error persists,
Support.
contact Customer Support.

EQQFA48E ERROR DURING SSI REQUEST -

EQQFA45E ATTACH ERROR - REASON: REASON
REASON: REASON
Explanation: This message describes an internal error
Explanation: There was an error during a Dynalloc
of the Data Store and is addressed to Customer
operation.
Support. An error occurred when the Data Store
attempted to attach a subtask. System action: The involved Data Store task is closed.
If the involved task is either the JES Queue or the
System action: The involved Data Store task is closed.
Database task, the Data Store is terminated. See
If the involved task is either the JES Queue or the
Chapter 38, “Reason Codes”, on page 463 for a list of
Database task, the Data Store is terminated. See
the REASON codes.
Chapter 38, “Reason Codes”, on page 463 for a list of
the REASON codes. Problem determination: Refer to the dump data set
(ddname EQQDUMP) for further information.
Problem determination: Review earlier messages in
the Data Store message log and SYSLOG data sets to User response: Contact your system programmer.
determine the cause of the error. One possibility is that
the Data Store is being started in a region that is too System programmer response: Contact Customer
small. Support.

User response: Contact your system programmer.

EQQFA49E ERROR DURING DYNALLOC
System programmer response: If possible correct all (UNALLOCATION) - REASON:
errors and restart the Data Store. If the error persists, REASON
contact Customer Support.
Explanation: This message describes an internal error
of the Data Store and is addressed to Customer

90 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

Support. An error was detected when a Subsystem
EQQFA74W HDRPROCNAME PARAMETER NOT
Interface function was invoked.
SPECIFIED DEFAULTED TO
System action: The Data Store is terminated. See ″PROCSTEP″
Chapter 38, “Reason Codes”, on page 463 for a list of
Explanation: You did not specify the
the REASON codes.
HDRPROCNAME parameter in DSTOPTS. It has been
Problem determination: Refer to the dump data set defaulted to ″PROCSTEP″.
(ddname EQQDUMP) for further information.
System action: Data store continues processing.
User response: Contact your system programmer.
User response: None.
System programmer response: Contact Customer
Support.
EQQFA75W HDRJOBLENGTH PARAMETER NOT
SPECIFIED DEFAULTED TO 21
EQQFA70E NO VALUE ASSIGNED TO SYSDEST
Explanation: You did not specify the
PARAMETER
HDRJOBLENGTH parameter in DSTOPTS. It has been
Explanation: You must specify a valid output defaulted to 21.
destination value in the SYSDEST parameter of
System action: Data store continues processing.
DSTOPTS because there is no default value..
User response: None.
System action: Data store does not start.
User response: Check the command. Correct the error
EQQFA76W HDRSTEPLENGTH PARAMETER NOT
and resubmit the request.
SPECIFIED DEFAULTED TO 30
Explanation: You did not specify the
EQQFA71E SYSDEST IS MANDATORY IN
HDRSTEPLENGTH parameter in DSTOPTS. It has been
DSTOPTS OPTIONS
defaulted to 30.
Explanation: You must specify the SYSDEST (sysout
System action: Data store continues processing.
destination reserved for data store) parameter in
DSTOPTS. User response: None.
System action: Data store does not start.
EQQFA77W HDRPROCLENGTH PARAMETER
User response: Check the command. Correct the error
NOT SPECIFIED DEFAULTED TO 39
and resubmit the request.
Explanation: You did not specify the
HDRPROCLENGTH parameter in DSTOPTS. It has
EQQFA72W HDRJOBNAME PARAMETER NOT
been defaulted to 39.
SPECIFIED DEFAULTED TO
″JOBNAME″ System action: Data store continues processing.
Explanation: You did not specify the HDRJOBNAME User response: None.
parameter in DSTOPTS. It has been defaulted to
″JOBNAME″
EQQFA78E AN INVALID VALUE WAS ASSIGNED
System action: Data store continues processing. TO SYSDEST PARAMETER
User response: None. Explanation: You have specified an invalid value for
the SYSDEST parameter of the DSTOPTS option. It
must be a valid z/OS name.
EQQFA73W HDRSTEPNAME PARAMETER NOT
SPECIFIED DEFAULTED TO System action: Data store does not start.
″STEPNAME″
User response: Check the command. Correct the error
Explanation: You did not specify the HDRSTEPNAME and resubmit the request.
parameter in DSTOPTS. It has been defaulted to
″STEPNAME″.
| EQQFA81I THE DSTHIGHJOBID VALUE USED
System action: Data store continues processing. | NEEDS MVS 64K JOBID SUPPORT
User response: None. | Explanation: The DSTHIGHJOBID value is greater
| than 65534. The MVS system must support 64K Jobid
| values.
| System action: Data store continues processing.

Chapter 11. EQQFxxx Messages 91

 EQQFAR1I WAITING FOR SUBTASK EQQFAR6E INVALID COMBINATION OF
COMPLETION TASKNAME COMMUNICATION PARAMETERS
Explanation: The Data Store is waiting for a subtask Explanation: The combination of communication
completion. This message can occur during the Data parameters is invalid, for example, you have specified
Store shut down. both HOSTCON(SNA) and CTLMEM.
System action: None. System action: The Data Store does not start.
User response: None
EQQFAR7W FAILDEST PARM NOT SPECIFIED:
DEFAULTED TO FAILDEST
EQQFAR2E TASKNAME TASK ABENDED -
RETURN: REASON Explanation: The FAILDEST parameter was not
specified. Default value FAILDEST will be used.
Explanation: The task specified TASKNAME has
abended with reason REASON or is terminated System action: Data store continues processing.
unexpectedly.
System action: The involved Data Store task is closed. EQQFAR8I DATA STORE STATISTICS
If the involved task is either the JES Queue or the
Explanation: A modify command, /F procname,ARSTGN
Database task, the Data Store is terminated.
or /F procname,ARSTKW O=[owner],K=[keyword], has
Problem determination: Review earlier messages in been issued and the data store shows internal statistics
the Data Store message log and SYSLOG data sets to values. This message is followed by one or more
determine the cause of the error. One possibility is that EQQFAR9I messages.
the Data Store is being started in a region that is too
System action: Data store statistics are displayed
small.
User response: None
User response: Contact your system programmer.
System programmer response: If possible correct all
EQQFAR9I DATA STORE STATISTICS NOT
errors and restart the Data Store. If the error persists,
EVALUATED YET
contact Customer Support.
Explanation: A modify command, /F procname,ARSTGN
or /F procname,ARSTKW O=[owner],K=[keyword], has
EQQFAR3I ALL WRITER SUBTASKS ARE
been issued but the data store does not have any
CLOSED
statistic value to display.
Explanation: All active writer subtasks are now
System action: Data store continues processing.
closed.
User response: None.
System action: The Data Store is not able to store
sysout until a minimum of one writer is restarted. To
start some of them, issue the ARMDWR modify EQQFARAI DATA STORE TASKNAME TASK
command. ACTIVE
Explanation: The task indicated by TASKNAME has
EQQFAR4I OPC DATA STORE ENDED been successfully started and is active.
Explanation: All Data Store subtasks have terminated. System action: The Data Store continues processing.
The Data Store subsystem is starting its own
termination process.
EQQFARBE A COMMUNICATION METHOD
System action: The Data Store subsystem frees all MUST BE SPECIFIED (SNA / XCF)
acquired resources and is terminated.
Explanation: You must specify one of the two
methods for communication in DSTOPTS via the
| EQQFAR5W RETRYCOUNTER PARM INVALID OR HOSTCON keyword.
| NOT SPECIFIED: DEFAULTED TO 1
System action: The Data Store does not start.
| Explanation: The RETRYCOUNTER value is invalid or
| missing. A default value of 1 will be used.
EQQFARCE DSTLUNAM / CTLLUNAM ARE
| System action: Data store continues processing. MANDATORY WHEN
HOSTCON(SNA) IS SPECIFIED
Explanation: If HOSTCON(SNA) is required, you
must specify both DSTLUNAM and CTLLUNAM.

92 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

System action: The Data Store does not start.
EQQFARJE DSTHIGHJOBID PARM MUST BE
GREATER THAN DSTLOWJOBID
EQQFARDE DSTGROUP / DSTMEM / CTLMEM PARM.
ARE MANDATORY WHEN
Explanation: You have specified a value for the
HOSTCON(XCF) IS SPECIFIED
DSTHIGHJOBID parameter that is lower than the value
Explanation: If HOSTCON(XCF) is required, you must of the DSTLOWJOBID parameter.
specify all the three parameters.
System action: The Data Store does not start.
System action: The Data Store does not start.
EQQFARKI DATA STORE STATISTICS NOT
EQQFAREE SYSCLASS IS MANDATORY IN EVALUATED YET
DSTOPTS OPTIONS
Explanation: A modify command, /F procname,ARSTGN
Explanation: You must specify the SYSCLASS (sysout or /F procname,ARSTKW O=[owner],K=[keyword], has
class reserved for Data Store) parameter in DSTOPTS. been issued but the Data Store doesn’t have any
statistic value to display.
System action: The Data Store does not start.
System action: Data Store continues processing.

EQQFARFW NWRITER PARM NOT SPECIFIED OR User response: None

OUT OF RANGE (1:16): DEFAULTED
TO 1
| EQQFARKW RETRYCOUNTER PARM INVALID
Explanation: The NWRITER (number of writer tasks) | OR NOT SPECIFIED: DEFAULTED TO
parameter was invalid or not specified. The number of | 1
writers was defaulted to 1.
| Explanation: The RETRYCOUNTER value is invalid or
System action: The Data Store continues processing. | missing. Default value 1 will be used.
| System action: Data Store continues processing.
EQQFARGW MAXSTOL PARM NOT SPECIFIED
OR OUT OF RANGE (0:10000):
EQQFARLW CINTERVAL PARM NOT SPECIFIED
DEFAULTED TO 0
OR OUT OF RANGE (0:1440):
Explanation: The MAXSTOL (maximum number of DEFAULTED TO 0
sysout lines stored in SysDb) parameter was invalid or
Explanation: The CINTERVAL (interval time in
not specified. The maximum number of stored lines
minutes for cleanup) parameter was invalid or not
was defaulted to 0.
specified. The interval time for cleanup was defaulted
System action: The Data Store continues processing. to 0.
System action: The Data Store continues processing.
EQQFARHW MAXSYSL PARM NOT SPECIFIED
OR OUT OF RANGE (0:10000):
EQQFARMW WINTERVAL PARM NOT SPECIFIED
DEFAULTED TO 0
OR OUT OF RANGE (0:3600):
Explanation: The MAXSYSL (maximum number of DEFAULTED TO 30
sysout lines returned to the Controller) parameter was
Explanation: The WINTERVAL (interval time in
invalid or not specified. The maximum number of
seconds for writer) parameter was invalid or not
sysout lines was defaulted to 0.
specified. The interval time for writer was defaulted to
System action: The Data Store continues processing. 30.
System action: The Data Store continues processing.
EQQFARIW QTIMEOUT PARM NOT SPECIFIED
OR OUT OF RANGE (0:360):
EQQFARNW DELAYTIME PARM NOT SPECIFIED
DEFAULTED TO 15
OR OUT OF RANGE (0:1440):
Explanation: The QTIMEOUT (timeout system reader) DEFAULTED TO 1
parameter was invalid or not specified. The timeout
Explanation: The DELAYTIME (maximum delay for
system reader was defaulted to 15.
job permanence in JES queue) parameter was invalid or
System action: The Data Store continues processing. not specified. The parameter was defaulted to 1.
System action: The Data Store continues processing.

Chapter 11. EQQFxxx Messages 93

EQQFAROE REQDEFCLASS MUST BE DIFFERENT EQQFARUW STORESTRUCMETHOD PARM NOT
FROM SYSCLASS SPECIFIED DEFAULTED TO
IMMEDIATE.
Explanation: The REQDEFCLASS (default class for
requeue) parameter must be different from the Explanation: You did not specify a value for
SYSCLASS (sysout class reserved for Data Store) storestrucmethod parameter. The allowed values are :
parameter.
Delayed- Structured information will be archived only
System action: The Data Store does not start. on demand, that is when requested by controller.
Immediate- Structured information will be archived as
EQQFARPE UNABLE TO START TASK BECAUSE soon as possible, when a writer task will be available.
IT IS ALREADY ACTIVE
System action: Value is defaulted to immediate.
Explanation: An operator START command has been Processing continues.
entered for a Data Store task that is already active.
User response: None
System action: The second attempt is terminated.
System programmer response: If you want to restart EQQFARVW DSTREQUEUEDEF PARM NOT
the task, first stop it, and then issue the START SPECIFIED DEFAULTED TO ASIS
command.
Explanation: The DSTREQUEUEDEF parameter was
not specified. The parameter was defaulted to ASIS.
EQQFARQE SYSDEST SPECIFIES A DESTINATION
System action: The Data Store continues processing.
ALREADY IN USE BY ANOTHER
DATA STORE
EQQFARWE STORESTRUCMETHOD (DELAYED)
Explanation: A Data Store has been started with a
NEEDS STOUNSD (YES)
destination that is assigned to another active Data
Store. Explanation: If you specify storestrucmethod as
delayed you must set STOUNSD to yes, because
System action: The second Data Store is terminated.
delayed method needs to find the JOBLOG into the
System programmer response: If you want to restart UDF files in order to extract the structured data.
the second Data Store, first change the SYSDEST in the
System action: Processing is terminated.
initialization parameters.
User response: Set STOUNSD to yes and check that
the UDFXX files are allocated and specified into the
EQQFARRI SUBTASK TASKNAME DIAGNOSE
data store start JCL.
HAS BEEN ACTIVATED
Explanation: The diagnose trace for subtask
EQQFARXE INVALID VALUE SPECIFIED FOR
TASKNAME has been activated
STORESTRUCMETHOD PARAMETER.
System action: The activities of subtask TASKNAME
Explanation: If you specify an invalid value for
are now traced.
parameter storestrucmethod. The allowed values are:
Delayed- Stuctured information will be archived only
EQQFARSI SUBTASK TASKNAME DIAGNOSE
on demand, that is when requested by controller.
HAS BEEN DE-ACTIVATED
Immediate- Structured information will be archived as
Explanation: The diagnose trace for subtask
soon as possible, when a writer task will be available.
TASKNAME has been deactivated.
System action: Processing is terminated.
System action: The activities of subtask TASKNAME
are now traced. User response: Set a valid value.

EQQFARTW CLNPARM PARM NOT SPECIFIED EQQFARYI DSTLOWJOBID PARM NOT

DEFAULTED TO EQQCLNPA SPECIFIED, DEFAULTED TO 1
Explanation: The CLNPARM (cleanup options Explanation: The DSTLOWJOBID parameter was
member name) parameter was not specified. The invalid or not specified. The parameter was defaulted
cleanup options member name was defaulted to to 1.
EQQCLNPA.
System action: The Data Store continues processing.
System action: The Data Store continues processing.

94 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

| EQQFARZI DSTHIGHJOBID PARM NOT EQQFCC5E FN APPLICATION DOES NOT
| SPECIFIED, OR INVALID DEFAULTED RESPOND
| TO hjobid
Explanation: After a close request issued by the Data
| Explanation: The DSTHIGHJOBID parameter was not Store communication task, the Data Store FN subtask
| valid or not specified. The parameter was defaulted to does not respond.
| the hjobid value, where hjobid is one of the following:
System action: The system waits until the subtask is
| v 65534, if the value of DSTHIGHJOBID is greater than closed.
| 65534
| v 9999 otherwise
EQQFCC6I XCF COMMUNICATION WITH
| System action: Data store continues processing CONTROLLER MEMBER MEMBER IS
OFFLINE
EQQFCC0E DATA STORE COMMUNICATION Explanation: The member MEMBER of the XCF
TASK INITIALIZATION FAILED communication with the Controller is offline.
Explanation: The Communication task could not System action: The Data Store cannot communicate
acquire all the resources needed for normal operation. with the Controller.
System action: The Communication task is not started. User response: Check if the Controller is active or if
there are some problems in the XCF connections. One
Problem determination: Review earlier messages in
possibility is that either CTLMEM or DSTGROUP is
the Data Store message log to determine the cause of
incorrectly specified in the DSTOPTS initialization
the error.
statement.
System programmer response: Correct the errors and
restart the communication task.
EQQFCC7I UNABLE TO SEND MESSAGE:
CONTROLLER XCF MEMBER
EQQFCC1I DATA STORE COMMUNICATION MEMBER IS OFFLINE
TASK INITIALIZATION ENDED
Explanation: The XCF Controller member MEMBER is
Explanation: The Communication task has offline.
successfully completed its initialization.
System action: The Data Store cannot communicate
System action: Communication processing starts. with the Controller: sysout cannot be sent back to it.
User response: Check if the Controller is active or if
EQQFCC2I DATA STORE COMMUNICATION there are some problems in the XCF connections. One
TASK ENDED possibility is that CTLMEM is incorrectly specified in
the DSTOPTS initialization statement.
Explanation: The Communication processing has been
completed and control is returned to the Data Store
subsystem. EQQFCC9I XCF MEMBER MEMBER HAS JOINED
THE GROUP GROUP
System action: The Communication task is
terminated. Explanation: A data store or controller FL subtask has
joined the XCF group as defined in the DSTOPTS or
FLOPTS statements.
EQQFCC3I STARTING FN APPLICATION
System action: None
Explanation: The Data Store FN task has received
control from the Data Store communication subtask and User response: None.
is soon to start initialization processing.
System action: Data Store FN processing continues. EQQFCCAI STARTING XCF JOIN
Explanation: The join process between the Data Store
EQQFCC4I CLOSING FN APPLICATION and XCF has been started.

Explanation: The Data Store FN processing has been System action: Normal processing continues.
completed and control is returned to the Data Store
communication task.
System action: Data Store FN processing is
terminated.

Chapter 11. EQQFxxx Messages 95

 System action: The Data Store continues processing.
EQQFCCBI UNABLE TO RETRIEVE JOB
JOBNAME: READER TASK INACTIVE
EQQFCMDI MAXSTOL STORED SYSOUT LINES:
Explanation: The Controller requested the retrieval of
VALUE
the JOB JOBNAME to the Data Store, but the Data Store
Reader subtask is not active. The retrieval cannot be Explanation: This message indicates (by VALUE) the
performed. current value of the MAXSTOL (maximum number of
sysout lines stored in SysDb) parameter.
System action: The request is rejected. Data Store
normal processing continues. System action: The Data Store continues processing.
User response: Start the reader task and resubmit the
request. EQQFCMFI CLEAN UP INTERVAL TIME: VALUE
Explanation: This message indicates (by VALUE) the
EQQFCM1I STOP IN PROGRESS current value of the CINTERVAL (interval time in
minutes for cleanup) parameter.
Explanation: The Data Store command task is
terminating after a stop request. System action: The Data Store continues processing.
System action: The Data Store waits until the
command task is closed. EQQFCMGE AN INCORRECT MODIFY
COMMAND HAS BEEN IGNORED
EQQFCM2I DATA STORE COMMAND TASK IS Explanation: The Data Store has detected an invalid
BEING STARTED modify command.
Explanation: The command task has been successfully System action: The modify command is not processed.
attached.
User response: Enter a valid command.
System action: The Data Store continues processing. If
the startup process is successful, the Command task
issues its own start message. EQQFCMHE MODIFY COMMAND SYNTAX
ERROR

EQQFCM3I DATA STORE COMMAND TASK Explanation: The modify command is syntactically
ENDED incorrect.

Explanation: The command task has been requested to System action: The modify command is not processed.
stop and is ending normally. User response: Enter a valid command.
System action: The command task is terminated and
all other active tasks are closed. EQQFCMIE INVALID MODIFY COMMAND
PARAMETER VALUE
EQQFCMAI NUMBER OF ACTIVE WRITERS: Explanation: The parameter value specified for the
VALUE modify command is incorrect or out of range.
Explanation: This message indicates (by VALUE) the System action: This command is not processed. The
number of writers that are currently running. Data Store continues processing.
System action: The Data Store continues processing. User response: Enter a valid command.

EQQFCMBI WINTERVAL TIME FOR SYSDB EQQFCU1I CLEAN UP TASK STARTED

WRITERS : VALUE
Explanation: The cleanup data store task has been
Explanation: This message indicates (by VALUE) the successfully started. This does not always mean that a
current value of the WINTERVAL (interval time in cleanup policy is running (see message EQQFCU3I).
minutes for writer) parameter.
System action: The Data Store continues processing.
System action: The Data Store continues processing.

EQQFCU2I CLEAN UP TASK ENDED

EQQFCMCI MAXSYSL RETURNED SYSOUT
LINES: VALUE Explanation: The cleanup data store task has been
requested to stop and is terminating normally.
Explanation: This message indicates (by VALUE) the
current value of the MAXSYSL (maximum number of System action: The cleanup task is terminated. Data
sysout lines returned to the Controller) parameter. Store normal processing continues.

96 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

EQQFCU3I CLEAN UP TASK RUNNING | EQQFCU9E STRUCTURED DATA NOT
| AVAILABLE
Explanation: The cleanup data store task is running. A
value other than 0 (zero) was specified for | Explanation: One of the following events has
CINTERVAL. The cleanup policy specified in the | happenned:
CLNPARM member is active. | v A batch utility is processing one of the following
System action: The Data Store and cleanup task | commands:
continue processing. | – DELBOTH
| – DELSTRUC
EQQFCU4I CLEAN UP TASK IN QUIESCE | – EXPBOTH
STATUS | – EXPSTRUC
Explanation: The cleanup task is in a quiescent status | but the structured data files are not available
and is waiting until the cleanup interval time has | (perhaps because they were not specified in the JCL
elapsed. | procedure).
System action: At the end of the cleanup interval | v A batch utility is processing an IMPORT command
time, the cleanup task is reactivated. | by using an export file that contains structured data
| but the structured data files are not available
| (perhaps because they were not specified in the JCL
EQQFCU5E PARAMETER NOT ALLOWED IN
| procedure).
DATA STORE CLEAN UP TASK
| System action: The current command is ignored and
Explanation: A statement (or statements) in
| the following command is processed.
CLNPARM is invalid because it is applicable only to
batch cleanup. | Problem determination: Refer to the diagnostics file
| (ddname EQQDUMP) for further information
System action: The cleanup task is terminated. Data
store normal processing continues. | User response: Check the command and the batch
| utility start JCL. Correct the error and resubmit the
User response: Check the CLNPARM statement (or
| request.
statements). Correct the error and restart the cleanup
task.
EQQFCUAE CMDPAR: PARM-MEMBER IS EMPTY
EQQFCU6I BATCH UTILITY PROCESSING Explanation: No operand is specified in the CMDPAR
STARTED member.
Explanation: The batch program that executes the System action: The batch utility is not started.
batch utilities has been successfully started.
User response: Check the member. Correct the error
System action: None and resubmit the request.

EQQFCU7E PARAMETER PARM NOT ALLOWED EQQFCUBE IMPORT / EXPORT COMMAND

IN BATCH CLEAN UP WITHOUT DDNAME PARAMETER
Explanation: A statement (or statements) in Explanation: The DDNAME parameter was not
CLNPARM is invalid because it is applicable only to specified in an Import or Export statement.
the data store cleanup task.
System action: The request is rejected.
System action: Batch utility processing is terminated.
User response: Check the DDNAME parameter.
User response: Check the CLNPARM statement (or Correct the error and resubmit the utility.
statements). Correct the error and resubmit the utility.
EQQFCUCE PARAMETER CMDPAR NOT
EQQFCU8I BATCH UTILITY PROCESSING ALLOWED
ENDED
Explanation: The CMDPAR parameter is not allowed
Explanation: The program that executes the batch for this statement.
utilities is terminating normally.
System action: The request is rejected.
System action: The batch utility processing is
User response: Check the parameter. Correct the error
terminated. Data Store normal processing continues.
and resubmit the utility.

Chapter 11. EQQFxxx Messages 97

 | System action: The system informs you that the
EQQFCUEE ERROR ON PARAMETER LIBRARY
| export utility has terminated processing of a single
MEMBER CMDPAR
| export command. Normal batch utilities processing
Explanation: An error was found in the CMDPAR | continues.
initial parameter member.
System action: The batch utility is terminated. | EQQFCUKI NUMBER OF SYSOUTS
Previous error messages help you to understand the | IMPORTED: nnn
problem. | NUMBER OF SYSOUTS
| IGNORED: mmm
User response: Check the statement. Correct the error
and resubmit the utility. | Explanation: This message is issued by the Data store
| batch utility to indicate:
EQQFCUFE SYNTAX ERROR IN SEARCH | v The total number of SYSOUTS that were selected
CRITERIA CMDPAR | from the import file and stored in the SYSOUT
| database (nnn)
Explanation: The search condition specified for the
| v The total number of SYSOUTS that were not selected
CMDPAR statement contains a syntax error (or errors).
| from the import file according to the specified filter
System action: The batch utility is terminated. | criteria (mmm)

User response: Check the statement. Correct the error | System action: None.
and resubmit the utility.
EQQFCUMW BAD SYSOUT: SYSOUT KEY
EQQFCUGW NAME EXCEEDS 8 CHARACTERS IMPORTED

Explanation: In the search criteria, you specified a Job Explanation: During a batch import utility, a
name or Job ID that is greater than eight characters. mismatch was detected between the number of records
This is not allowed. written in the import file, for a specific sysout, and the
total number of pages stored in the page prefix. The
System action: The name or ID is truncated to eight incorrect SYSOUT KEY is shown.
characters.
System action: The batch utility does not import the
Problem determination: None. incorrect sysout and continues its normal processing.
User response: To use the correct criteria, change the
statement and resubmit the utility. EQQFCUNI NUMBER OF KEYS EXTRACTED: nnn
Explanation: This message indicates the total number
EQQFCUHW THE IMPORT FILE IS EMPTY of keys selected from the sysout database and written
Explanation: The import batch utility found an empty into an output file by a single batch recover primary
import file. index utility.

System action: The batch utility is terminated. System action: The system informs you that the
recover utility has terminated Normal batch utilities
User response: Check the import file and, if necessary, processing continues.
resubmit the utility.

EQQFCUOW THE HEADER RECORD DOESN’T

| EQQFCUJI NUMBER OF SYSOUTS/RECORDS CONTAIN A VALID IDENTIFIER
| EXPORTED: nnn/mmm
| NUMBER OF SYSOUTS Explanation: The first record of an input file found by
| IGNORED: xxx the import batch utility is not an header record.

| Explanation: This message is issued by the data store System action: The import utility is terminated.
| batch utility to indicate: User response: Check the import file and, if necessary,
| v The total number of SYSOUTS that were selected resubmit the utility.
| from the SYSOUT database and stored in the export
| file (nnn)
EQQFCUPI CLEAN UP ISSUED DELETE REQUEST
| v The total number of records that were selected from FOR NNN SYSOUTS STRUCTURED:
| the SYSOUT database and stored in the export file STR UNSTRUCTURED: UNS
| (mmm)
| v The total number of SYSOUTS that were not selected Explanation: The cleanup task has completed the
| from the SYSOUT database according to the specified deletion of the specified sysouts (NNN) in accordance
| filter criteria (xxx) with the current cleanup policy. STR identifies the

98 IBM Tivoli Workload Scheduler for z/OS Messages and Codes

 number of deleted structured sysout (joblogs structured and the data store is terminated with return code 8.
info) and UNS identifies the number of deleted
Problem determination: No further information is
unstructured sysout (joblogs).
needed to identify this problem.
System action: None
User response: Contact your system programmer.
System programmer response: Correct the error
EQQFCUQI EQQCLNPA MEMBER NOT FOUND
specifying only one DSTUTIL command in the cleanup
Explanation: This message is issued when the parameters member. Then restart data store.
CLNPARM option is not specified in the DSTOPTS
statement. Default member EQQCLNPA is used, but is
EQQFJK1I UNABLE TO WRITE ALL DSID IN
not found in the parameter library.
SYSDB FOR JOB: JOBNMID
System action: The cleanup task is started, but there is
Explanation: After several retries, a writer task was
no active policy.
unable to store all the sysouts in the database for the
User response: Specify the CLNPARM option or add specified job.
the member EQQCLNPA into the parameter library and
Problem determination: Review earlier messages in
restart the cleanup task with the appropriate command.
the Data Store message log and SYSLOG data sets to
determine the cause of the error.
| EQQFCUSE UNSTRUCTURED DATA NOT
System action: The sysouts are not requeued to their
| AVAILABLE
original class. They are kept in the Data Store reserved
| Explanation: One of the following events has class for a next retry until they are correctly processed
| happenned: or removed manually from the reserved class.
| v An online cleanup was processing a DELUNSTR or
User response: Contact your system programmer.
| DELBOTH command, but STOUNSD(N) was
| codified in Data Store (Data Store does not manage System programmer response: If the error persists,
| unstructured data). remove the job manually from the reserved class and
| v A batch utility was processing the DELBOTH, contact Customer Support.
| DELUNSTR, EXPBOTH, or EXPUNSTR command
| but the unstructured data files are not available
| (perhaps they were not specified in the JCL EQQFJK2E DATA STORE JESQUEUE TASK
| procedure). INITIALIZATION FAILED
| v A batch utility was processing an IMPORT command Explanation: The JES queue task could not acquire all
| by using an export file that contains unstructured the resources needed for normal operation.
| data, but the unstructured data files are not available
| (perhaps they were not specified in the JCL System action: The JES queue task is not started and
| procedure). all other active tasks are closed. Data Store is
terminated.
| System action: If the message is issued during the
| online cleanup, the execution of the command is Problem determination: Review earlier messages in
| terminated. The cleanup task waits for another request the Data Store message log to determine the cause of
| and Data Store normal processing continues. If the the error.
| message is issued while the batch utility program is System programmer response: Correct the errors and
| running, the current command is discarded and the restart the Data Store.
| next command is processed.
| Problem determination: Refer to the diagnostics file EQQFJK3I DATA STORE JESQUEUE TASK
| (with ddname EQQDUMP) for further information. INITIALIZATION COMPLETED
| User response: Check the command and the batch Explanation: The JES queue task has successfully
| utility start JCL. Correct the error and resubmit the completed its initialization.
| request.
System action: JES queue processing starts.

EQQFCUTE A SINGLE COMMAND MUST BE

SPECIFIED IN ON LINE DATA STORE EQQFJK4I DATA STORE JESQUEUE TASK
CLEAN UP ENDED

Explanation: During the online cleanup, more than Explanation: The JES queue task has been requested
one command DSTUTIL has been specified, but this to stop and is terminating normally.
isn’t supported in on line mode. System action: The JES queue task is terminated.
System action: No command DSTUTIL is performed

Chapter 11. EQQFxxx Messages 99

EQQFJK5E DATA STORE JESQUEUE TASK | EQQFJKBE SSI CALL ENDED IN ERROR:
ENDED DUE TO AN ERROR
Explanation: The JES queue task has been abnormally
| FUNCTION: SAPIFUNC
stopped.
| RETURN CODE: SRC
| SSOBRETN: SRETN
System action: The JES queue task is terminated and | SSS2REAS: SREAS
all other active tasks are closed. The Data Store is | JOBNAME: SAPIJOBN
terminated. | JOBID: SAPIJBID
Problem determination: Review earlier messages in | Explanation: Data Store invoked the SSI interface to
the Data Store message log to determine the cause of | execute a SAPI function for handling the sysout from
the error. | its reserved destination queue, but this call failed. The
| message displays the following detailed information:
System programmer response: Correct the errors
shown by the earlier messages and restart the Data | SAPIFUNC
Store. | The SAPI function that failed. Possible values
| are:
EQQFJK6I DATA STORE JESQUEUE TASK | SAPI 79 — PUT/GET
WAITING FOR DATABASE TASK | Used to put/get sysouts from spool.
END.
| SAPI 79 — PUT/GET LAST CALL
Explanation: The JES queue has received a stop | Used to close a put/get function.
command, but it has some jobs in its queue and the
database task has to complete the pending requests.
| SAPI 79 — COUNT
| Used to count sysout elements.
System action: The JES queue task waits until the
database task is terminated.
| SAPI 79 — COUNT LAST CALL
| Used to close a count function.

EQQFJK7I DATA STORE JESQUEUE TASK CLOSE

| SAPI 79 — BULK MODIFY
IN PROGRESS : ANALYSING QUEUE
| Used to requeue or purge sysouts.

Explanation: Before closing, the JES queue task

| SAPI 79 — BULK MODIFY LAST CALL
examines its internal queue for the last time to close all
| Used to close a Bulk modify function.
pending situations. | SRC The return code from the SSI call. To learn its
System action: None.
| meaning, refer to the MVS manual that
| describes the specified SAPI function (OS/390
| MVS Using the Subsystem Interface — Return
EQQFJK9I JOBNMID CANNOT BE REQUEUED | Code Information).
TO ORIGINAL CLASS: DEFAULT
CLASS IS USED.
| SRETN The value returned by SAPI in the ssobretn
| field of the SSOB control block. To learn its
Explanation: The original class specified for the | meaning, refer to the MVS manual that
requeue operation is reserved. The requeue operation | describes the specified SAPI function.(OS/390
for the JOBNMID job is forced in the default class. | MVS Using the Subsystem Interface — Output
| Parameters — SSOBRETN Contents).
System action: JES queue processing continues.
| SREAS The value retuned by SAPI in the sss2reas
| field of the SSS2 control block To learn its
EQQFJKAI ORIGINAL CLASS NOT FOUND:
| meaning, refer to the MVS manual that
JOBNMID REQUEUED TO DEFAULT
| describes the specified SAPI function (OS/390
CLASS
| MVS Using the Subsystem Interface — Output
Explanation: The original class specified for the | Parameters — SSS2 Contents).
requeue operation was not found. The requeue
| SAPIJOBN
operation for the JOBNMID job is forced in the default
| The jobname filter criteria used to execute the
class.
| specified SAPI function. It can be blank or it
System action: JES queue processing continues. | can contain a jobname value. The jobname
| value indicates which is the job that causes
| problems to the SAPI function. A blank
| indicates that Data Store issued a SAPI
| function to get all the jobs on its reserved
| queue: in this case, it is not easy to identify
| the job that causes problems (if it is a job and

100 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
| not another kind of error). One of the possible
EQQFJKFI ARCHIVING COMPLETED FOR:
| reasons is a job that lacks the JCT; this can be
JOBNMID
| verified by looking for the $HASP364 message
| on the data store log. Explanation: The archiving process, delayed for ’retry’
or ’delay’ reason, is finally completed.
| SAPIJBID
| The jobid range used as filter criteria for the System action: None.
| specified SAPI function. It has the form
User response: None.
| lowjobid/highjobid. If lowjobid and highjobid
| are equal, they identify the single job that
| causes trouble. If lowjobid and highjobid are | EQQFJKWW ARCHIVING FAILED FOR: JOBNMID.
| different, this means that Data Store issued a | JOB REQUEUED TO FAILD.
| SAPI function to get all the jobs on its
| reserved queue. The SAPIJBID is the used | Explanation: The job identified by JOBNMID exceeded
| range. | the maximum number of archiving attempts (as
| specified by the RETRYCOUNTER keyword). For this
| System action: Data store stops processing the | reason, the job is requeued to the FAILD destination.
| problem job. If the error occurred in the JES queue task,
| data store stops processing completely. If the error | System action: Data store removes the job from the
| occurred in the Writer task, Writer stops processing and | reserved destination queue and requeues it to the
| the job is retried later. | failure destination specified in the FAILDEST keyword..

| User response: Contact your system programmer to

| analyze where the problem originated. EQQFL00E JOB LOG FETCH TASK HAS
IGNORED AN INVALID QUEUE
| System programmer response: See the MVS manual ELEMENT: DQE
| for the explanation of the SAPI function,the return
| code, the SSOB reason code, and the SSS2 reason code. Explanation: A queue element did not contain the
| If a specific jobname jobid is shown in the message, correct eye catcher or version number.
| remove it from the reserved class queue. If no specific System action: The job log fetch task does not process
| jobname appears, look into the reserved class queue the invalid element, but continues normal processing.
| which contains the jobs currently handled by data
| store: a generic SAPI get function was issued with only User response: Contact your system programmer.
| reserved class as the filter criteria. One of the possible System programmer response: Save the Data Store job
| reasons is that a job has no JCT and this can be log task message log and contact Customer Support.
| verifyed by looking for the $HASP364 message in the
| data store log.
EQQFL01I JOB LOG FETCH TASK
INITIALIZATION COMPLETE
EQQFJKDI ARCHIVING IN PROGRESS FOR:
JOBNMID (REASON=RETRY) Explanation: The job log fetch task has successfully
completed its initialization.
Explanation: The archiving process is not completed
yet, but there is no real error: data is still being sent System action: Job log fetch processing is available.
and a retry will be performed.
System action: The data store continues the archiving EQQFL02E JOB LOG FETCH TASK
process. INITIALIZATION FAILED

User response: None. Explanation: The job log fetch task could not acquire
all the resources needed for normal operation.

EQQFJKEI ARCHIVING IN PROGRESS FOR: System action: The job log fetch task is not started
JOBNMID (REASON=DELAY) and all other active tasks are closed.

Explanation: The archiving process is not completed Problem determination: Review earlier messages in
yet, but there is no real error: delay time has been the Data Store message log to determine the cause of
reached (data retry will be performed). the error.

System action: The datastore continues the archiving System programmer response: Correct the errors and
process. restart the submit task.

User response: None.

Chapter 11. EQQFxxx Messages 101

 System programmer response: Correct the error and
EQQFL04E JOB LOG FETCH ABENDED WHEN
restart the FL task
PROCESSING THE FOLLOWING
QUEUE ELEMENT DQE
EQQFL12E SNADEST OR XCFDEST MISSING
Explanation: An abend prevented the job log fetch
task from processing a queue element. Explanation: SNADEST or XCFDEST is not specified
in the FLOPTS statement of the controller initial
System action: z/OS recovery/termination is
parameter statement. One of them is mandatory.
requested to generate a dump. The job log fetch task
attempts to continue normal processing. System action: The FL task does not start.
Problem determination: Review the Data Store System programmer response: Correct the error and
message log data set, the EQQDUMP data set, and the restart the FL task
SYSDUMP data set to determine the cause of the error.
User response: Contact your system programmer. EQQFL13E CONFLICT DETECTED BETWEEN
CTLLUNAM AND SNADEST VALUES
System programmer response: Save the message log
and dump data sets and contact Customer Support. Explanation: The same name is specified in the
FLOPTS statement for the CTLLUNAM and SNADEST
parameters or for the CTLMEM and XCFDEST
EQQFL05E JOB LOG FETCH QUEUE POINTER IS
parameters. Home and destination must have different
DESTROYED. ARCQ IS LOST
names.
Explanation: The job log fetch task abended while
System action: The FL task does not start.
processing elements on the DSCQ because queue
chaining is invalid. System programmer response: Correct the error and
restart the FL task
System action: z/OS recovery/termination is
requested to generate a dump. The job log fetch task
attempts to continue normal processing. EQQFL14E SNADEST SPECIFIED IN XCF
ENVIRONMENT
Problem determination: Review the Data Store
message log data set, the BEX diagnostic data set, and Explanation: SNADEST and DSTGROUP or CTLEM
the dump data set to determine the cause of the are specified together in the FLOPTS statement of the
problem. controller initial parameter statement. They are
mutually exclusive.
User response: Contact your systems programmer.
System action: The FL task does not start.
System programmer response: Save the message log,
BEX and dump data sets, and contact Customer System programmer response: Correct the error and
Support. restart the FL task

EQQFL10E IN XCF ENVIRONMENT BOTH EQQFL15E XCFDEST SPECIFIED IN SNA

DSTGROUP AND CTLMEM ARE ENVIRONMENT
MANDATORY
Explanation: XCFDEST and CTLLUNAM are specified
Explanation: DSTGROUP and CTLMEM are not together in the FLOPTS statement of the controller
specified in the FLOPTS statement of the controller initial parameter statement. They are mutually
initial parameter statement. If you specify the exclusive.
XCFDEST parameter, they are both mandatory.
System action: The FL task does not start.
System action: The Data Store does not start.
System programmer response: Correct the error and
System programmer response: Correct the error and restart the FL task
restart the Data Store.

EQQFL16E MORE THAN ONE DOT FOUND IN

EQQFL11E CTLLUNAM AND DESTINATION PARM
DSTGROUP/CTLMEM ARE
MUTUALLY EXCLUSIVE Explanation: The value of the XCFDEST or SNADEST
parameter in the FLOPTS statement is not valid
Explanation: CTLLUNAM and DSTGROUP or because it contains more than one dot (period) The
CTLMEM parameters are specified together in the period divides the Tracker by Data Store destination
FLOPTS statement of the controller initial parameter names and there must be only one.
statement. They are mutually exclusive.
System action: The FL task does not start.
System action: The FL task does not start.

102 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
System programmer response: Correct the error and System programmer response: Save the scheduler Pre
restart the FL task Submitter task message log and contact Customer
Support.
EQQFL17E AT LEAST ONE DOT MUST BE
SPECIFIED IN DESTINATION PARM EQQFL23E UNEXPECTED LOCAL DATASTORE
SUBTASK END
Explanation: The value of the XCFDEST or SNADEST
parameter in the FLTS statement is not valid because it Explanation: The Joblog Fetch task detected a failure
does not contain a dot (period). The period divides the in the local data store.
Tracker by Data Store destination names and there
System action: The Joblog Fetch task ends abnormally.
must be a minimum of one.
Problem determination: Review the message log data
System action: The FL task does not start.
set and the EQQDUMP data set to determine the cause
System programmer response: Correct the error and of the problem.
restart the FL task
User response: Contact your system programmer.
System programmer response: If the problem persists,
EQQFL18E NO DESTINATION NAME FOUND
save the message log and dump data sets and contact
FOR TRACKER TRACKER
Customer Support.
Explanation: The Controller has requested a job log
from the Data Store, but the Tracker destination name
EQQFL24E ERROR CREATING CP16 QUEUE FOR
is not specified in the SNADEST or XCFDEST
FL SUBTASK
parameter of the FLOPTS statement.
Explanation: An internal Joblog Fetch task error
System action: The request fails.
occurred during construction of an internal queue.
System programmer response: Correct the XCFDEST
System action: The Joblog Fetch task ends abnormally.
or SNADEST parameter and restart the Data Store.
User response: Contact your system programmer.
EQQFL19I DATA STORE DST IS INACTIVE System programmer response: Save the scheduler Pre
Submitter task message log and contact Customer
Explanation: The Controller has requested a job log,
Support.
but the Data Store destination specified in the
SNADEST or XCFDEST parameter of the FLOPTS
statement is currently inactive. EQQFL25E ERROR ADDING OPERATION
TOKEN TO BE DELETED
System action: The request fails.
Explanation: An internal Joblog Fetch task error
System programmer response: Start the appropriate
occurred during an operation on an internal queue.
Data Store and resubmit the request.
System action: The Joblog Fetch task ends abnormally.
EQQFL21E ERROR CREATING DB END WRITE User response: Contact your system programmer.
QUEUE
System programmer response: Save the scheduler Pre
Explanation: An internal Joblog Fetch task error Submitter task message log and contact Customer
occurred when constructing an internal queue. Support.
System action: The Joblog Fetch task ends abnormally.
EQQFL26E ERROR DURING OPERINFO CHECK
User response: Contact your system programmer.
FOR OP TOKEN:OPTOK
System programmer response: Save the scheduler Pre
Explanation: The Joblog Fetch task detected a failure
Submitter task message log and contact Customer
while trying to delete a sysout in the local data store.
Support.
The sysout belongs to the occurence identified by the
token OPTOK. The RC return code indicates the kind of
EQQFL22E ERROR CREATING DB DELETE error:
EVENTS QUEUE v * = 4 → the sysout was not found
Explanation: An internal Joblog Fetch task error v * > 4 → an internal error occurred
occurred when constructing an internal queue.
The cleanup of a local data store is the consequence of
System action: The Joblog Fetch task ends abnormally. a current plan extend or a current plan replan and its
start and end is identified by the messages EQQFL28
User response: Contact your system programmer.

Chapter 11. EQQFxxx Messages 103

and EQQFL29. The sysout to be deleted are the ones System action: The Joblog Fetch task continues the
associated to the occurrences removed by the current processing.
plan batch run.
User response: None.
System action: The Joblog Fetch task continues
System programmer response: None.
processing.
Problem determination: If RC > 4 are detected, check
EQQFL1AE UNEXPECTED FN SUBTASK END
EQQMLOG and EQQDUMP to find further error
messages. Explanation: The FL task has detected an unexpected
end of FN subtask.
User response: Contact your system programmer if
RC > 4 are detected . System action: The FL task ends in error.
System programmer response: If RC > 4 are detected, Problem determination: Review the Data Store
save EQQDUMP and EQQMLOG and contact message log data set, the EQQDUMP data set, and the
Customer Support. SYSMDUMP data set to determine the cause of the
problem
EQQFL27E ERROR DURING OPERINFO CHECK User response: Contact your system programmer
FOR OP TOKEN OPTOK
System programmer response: If the error persists,
Explanation: An internal Joblog Fetch task error save the message log and dump data sets and contact
occurred while an internal queue was being processed. Customer Support.
System action: The Joblog Fetch task ends abnormally.
| EQQFSD0E SYSOUT DATABASE INITIALIZATION
User response: Contact your system programmer.
| FAILED
System programmer response: Save the scheduler
| Explanation: The initialization of the sysout data base
message log and contact Customer Support.
| task failed.

EQQFL28I LOCAL DATA STORE CLEANUP

| System action: If the task is started by data store, data
STARTED
| store ends. If the task is started by the controller, FL
| task is ended.
Explanation: The Joblog Fetch task started the local
data store cleanup process. The cleanup of local data
| User response: Check the previous messages in the
store is the consequence of a current plan extend or
| EQQMLOG to get more information (for example the
current plan replan and its start and end is identified
| message EQQFSF0E).
by the messages EQQFL28 and EQQFL29. The sysout
to be deleted are the ones associated to the occurrences EQQFSD1I SYSOUT DATABASE ERROR
removed by the current plan batch run (the completed HANDLER TASK STARTED
ones).
Explanation: The sysout database error handler task is
System action: The Joblog Fetch task continues the being started.
processing.
System action: The Data Store initialization process
User response: None. continues.
System programmer response: None.
EQQFSD2I SYSOUT DATABASE ERROR
HANDLER TASK ENDED
EQQFL29I LOCAL DATA STORE CLEANUP
ENDED. NUMBER OF OCCURENCE Explanation: The sysout database error handler task
SUCCESSFULLY PROCESSED: SYS has been requested to stop and it has terminated
normally.
Explanation: The Joblog Fetch task ended the local
data store cleanup process. The number of occurence System action: The sysout database error handler task
whose sysout were successfully deleted is indicated by is terminated.
the SYS value. The cleanup of local data store is the
consequence of a current plan extend or current plan
replan and its start and end is identified by the EQQFSD3E DATABASE ERROR HANDLER
messages EQQFL28 and EQQFL29. The sysout to be DETECTED SUBTASK FAILURE
deleted are the ones associated to the occurrences Explanation: The error handler task that coordinates
removed by the current plan batch run (the completed data file activities has detected a subtask failure.
ones).
Problem determination: Review earlier messages in
the Data Store message log and SYSLOG data sets to

104 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
 determine the cause of the error. | System programmer response: Check if the JCL used
| to start data store has the correct number of data file
User response: Contact your system programmer.
| specified: if it doesn’t, change the JCL and restart.
System programmer response: If possible correct all
errors and restart the Data Store. If the error persists,
| EQQFSDAE UNSTRUCTURED DATA REQUIRED
contact Customer Support.
| BUT NO UDFxx VSAM FILE HAS
| BEEN SPECIFIED
EQQFSD4I SYSOUT DATABASE STARTING
| Explanation: Data store initialization failed because
Explanation: The sysout database is being started. | STOUNSD(Y) was specified (for joblog retrieval) but
| the started task JCL did not include any unstructured
System action: The Data Store initialization process | vsam file (identified by ddname UDFxxx).
continues.
| System action: Data store stops processing.
EQQFSD5I SYSOUT DATABASE INITIALIZATION | User response: Allocate and add the UDFxx VSAM
COMPLETE | files, then restart data store.
Explanation: The sysout database has successfully
completed its initialization. | EQQFSDBE STRUCTURED DATA REQUIRED BUT
| NO SDFxx VSAM FILE HAS BEEN
System action: The sysout database is now active. | SPECIFIED
| Explanation: Data store initialization failed because no
EQQFSD6I SYSOUT DATABASE TERMINATING | structured VSAM file was specified in the started task
Explanation: A stop request was issued to close the | JCL. Structured VSAM files (identified by ddname
sysout database. | SDFxx) are always required.

System action: The sysout database is shut down. | System action: Data store stops processing.
| User response: Allocate and add the SDFxx VSAM
EQQFSD7I SYSOUT DATABASE STOPPED | files, then restart data store.
Explanation: A stop request was accepted and
completed by the sysout database. | EQQFSF0E OPEN FAILED FOR DDN FUNCTION:
| FUNC REASON: SS
System action: The sysout database is now stopped.
| Explanation: A Data store SYSOUT database task tried
| to open the data file identified by the ddname DDN
EQQFSD8W WARNING MESSAGES WERE ISSUED | but detected an error: the specific macro used is
DURING OPERATION ON DATA FILE | explained by FUNC while the reason code returned by
DATAFILE | the macro is specified in SS.
Explanation: This message is displayed during the | System action: If the task is started by data store, data
close process of the Data Store and indicates that an | store ends. If the task is started by the controller, the FL
error was found during an operation on the DATAFILE | task is ended.
data file.
| User response: Check the meaning of the macro
Problem determination: Review earlier messages in | reason code. For example, the specified data file could
the Data Store message log and SYSLOG data sets to | be already used by another data store or the started
determine which operation failed or the cause of the | task JCL could contain a duplicate ddname.
error.

EQQFSF1I DATA FILE DATAFILE

| EQQFSD9E DATAFILE NUMBER MISMATCH: INITIALIZATION COMPLETED
| DATFILE NUM:DNUMDATAFILE MAX
| NUM:MNUM Explanation: The initialization process of the
DATAFILE data file task was completed successfully.
| Explanation: Data store detected a datafile number
| mismatch during initialization phase. The primary key System action: The DATAFILE data file can be used to
| information(MNUM) does not match with the number store sysout data.
| of data files (DNUM)
| System action: Data Store stops the processing and
| terminates.
| User response: Contact system programmer to find
| the origin of mismatch.
Chapter 11. EQQFxxx Messages 105
 | activated. It occurs when the storing in the data file of
EQQFSF2I DATA FILE DATAFILE TERMINATION
| the JOBLOG or structured info failed due to problems
COMPLETED
| occurred during the I/O phase (for example when the
Explanation: The DATAFILE data file task termination | data file is full).
process has been completed.
| System action: The archiving will be retried later.
System action: The DATAFILE data file is closed.
| System programmer response: Check the EQQMLOG
| to find messages that may explain the origin of the
EQQFSF3E UNABLE TO ALLOCATE AND | problem.
FORMAT SPACE MAP
Explanation: An error occurred when allocating | EQQFSF7W NO MORE DATAFILE AVAILABLE TO
storage to build and format the space map. | STORE JOBLOG
System action: Data Store initialization is stopped. | Explanation: An error occurred when trying to extend
| the data file. This message is sent when the datafile is
System programmer response: The allocation in the
| the last one.
data file is too small (a minimum of two tracks is
needed). Correct the values in the allocation JCL, | System action: No more datafile available.
reallocate the data file and restart the Data Store.
| System programmer response: Allocate additional
| datafile and restart the Data Store.
EQQFSF4W INVALID PAGE - FILENUMRBN
Explanation: During cleanup an invalid page was | EQQFSF8E DATA FILE DDNAME HEADER PAGE
detected for one of the following reasons: | FILE NUMBER FILNUM MISMATCH
v the RBN is out of range
| Explanation: This message is issued when, at start
v the page status is deleted, but the corresponding bit
| time, the data store database subtask finds incongruent
of the space map is on.
| information in the header page of the data file
| identified by the ddname specified by DDNAME. The
The message shows the data file number FILENUM
| incorrect information is the data file identifier number
and the RBN stored in the page prefix.
| FILNUM.
System action: The cleanup resets the corresponding
| System action: Data store stops processing and
bit of the space map.
| terminates.
| Problem determination: Check the data store started
| EQQFSF5W UNABLE TO EXTEND DATA FILE
| procedure JCL to see which is the data file associated
| DATAFILE- DATA FILE DISABLED
| with the specified DDNAME. Check which are the data
| Explanation: An error occurred when trying to extend | files that have the same FILENUM printing the header
| the data file number DATAFILE. | page of all used data files. Check if among these data
| files there are data files used by another data store:
| System action: The data file was flagged as disabled | This cannot be done.
| and cannot be used to store sysout data. The store
| operations continue on the next available data file. If no
| more data files are available, no more sysout could be EQQFSI1I SECONDARY KEY FILE
| stored. INITIALIZATION COMPLETED

| System programmer response: Perform one of the Explanation: The initialization process of secondary
| following actions: key file task completed successfully.
| v To make more space available, shorten the cleanup
System action: The secondary key file can now be
| task interval (CINTERVAL)
used to store sysout data.
| v Stop the data store, increase the size of the current
| data store files, and restart the data store. User response: None.
| v Allocate additional data files and restart the data
| store.
EQQFSI2I SECONDARY KEY FILE
TERMINATION COMPLETED
| EQQFSF6I UNABLE TO COMPLETE SAVE
Explanation: The secondary key file task termination
| OPERATION - DATA FILE DISABLED
process has completed.
| SAVE WILL BE RETRIED
System action: The secondary key file is now closed.
| Explanation: This message is issued by the sysout DB
| task, which is a data store task started also by the User response: None.
| controller when the restart and cleanup function is

106 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
 System programmer response: Correct the errors and
EQQFSI3I GENERIC I/O ERROR DURING OPEN
restart the submit task.
VSAM FILE
Explanation: The macro returns an error during an
EQQFSR1I DATA STORE READER TASK
OPEN operation.
INITIALIZATION COMPLETED
System action: The data store closes.
Explanation: The reader task has successfully
Problem determination: Review earlier messages in completed its initialization.
the data store message log and the SYSLOG data sets
System action: Reader processing starts.
to determine the exact reason for this message. One
possibility is that the user has an insufficient User response: None.
authorization to the VSAM file.
User response: Contact your system programmer. EQQFSR2I DATA STORE READER TASK ENDED
System programmer response: If possible, correct all Explanation: The reader task has been requested to
errors, then restart data store. If the error persists, stop and is terminating normally.
contact Customer Support.
System action: The reader task is terminated.

EQQFSK1I PRIMARY KEY FILE INITIALIZATION System programmer response: None.

COMPLETED
Explanation: The initialization process of the primary EQQFSR3I DATA STORE IS ATTEMPTING TO
key file task was completed successfully. COMMUNICATE WITH CONTROLLER

System action: The primary key file can be used to Explanation: During a retrieval request processing,
store sysout data. communication was lost between the Controller and the
Data Store. The Data Store retries three times, at
5-second intervals, to retransmit the joblog.
EQQFSK2I PRIMARY KEY FILE TERMINATION
COMPLETED System action: None

Explanation: The primary key file task termination System programmer response: If the error persist,
process has been completed. check the reason for the communication failure.

System action: The primary key file is closed.

EQQFSR4I JOB JOBNMID NOT FOUND NEITHER
IN DATA STORE NOR IN JES QUEUE
EQQFSK3I GENERIC I/O ERROR DURING OPEN
VSAM FILE Explanation: The Reader Task has received a request
for a job that is not stored either on Data Store or on
Explanation: A VSAM Open operation failed. the JES queue. It may happen if the job log has not
been copied into the scheduler destination (see value
System action: The Data Store is terminated.
specified both in DSTDEST parameter of RCLOPTS
Problem determination: Review earlier messages in controller initialization statement and SYSDEST
the Data Store message log and SYSLOG data sets to parameter of DSTOPTS data store initialization
determine the cause of the error. One possibility is that statement). Possible reasons of the failure:
you have insufficient authorization on that VSAM file. v a JCL error produces a log which cannot be copied in
User response: Contact your system programmer. the scheduler destination (e.g. incomplete job log)
v a job is tracked by scheduler but submitted outside,
System programmer response: If possible correct all
for example Event-Triggered Tracking (ETT with
errors and restart the Data Store. If the error persists,
″job-name replace″ option set to Y). In any case the
contact Customer Support.
Reader Task is unable to return the requested job.
System action: The job log retrieval request fails.
EQQFSR0E DATA STORE READER TASK
INITIALIZATION FAILED System programmer response: Correct the JCL to
avoid the error. In case of ETT, you can manually route
Explanation: The reader task could not acquire all the
the job log from the local to the scheduler destination.
resources needed for normal operation.
System action: The reader task is not started.
Problem determination: Review earlier messages in
the Data Store message log to determine the cause of
the error.

Chapter 11. EQQFxxx Messages 107

 the Data Store message log to determine the cause of
EQQFSR5I TIMEOUT REACHED DURING
the error.
SEARCH OF JOB: JOBNMID
System programmer response: Correct the errors and
Explanation: The job log retrieval request reached the
restart the submit task.
maximum allowed time (see QTIMEOUT statement).
The reader is unable to return the requested job.
EQQFSW1I DATA STORE WRITER TASK
System action: The job log retrieval request fails.
INITIALIZATION COMPLETED
Explanation: The writer task has successfully
EQQFSR6I SOME PROBLEMS OCURRED IN
completed its initialization.
WRITE PHASE FOR JOB: JOBNMID,
RETRY LATER System action: Writer processing starts.
Explanation: An internal error was detected during User response: None.
database write phase. Data store was unable to return
the job log identified by JOGNMID.
EQQFSW2I DATA STORE WRITER TASK ENDED
System action: The job log retrieval request fails.
Explanation: The writer task has been requested to
System programmer response: Check the writer stop and is terminating normally.
failure reason.
System action: The writer task is terminated.

EQQFSR7I UNSTR DATA FOR JOB JOBNMID System programmer response: None.
REQUEST BUT NOT ON DB DUE TO
INIT PARAM EQQFSW3I DATA STORE WRITER TASK ENDED
Explanation: The data store reader task is unable to DUE TO AN ERROR
retrieve requested unstructured data because it can not Explanation: The writer task has been abnormally
be stored in the data store database. This because the stopped.
DSTOPST STOUNSTR(N) option is not specified.
System action: The writer task is terminated.
System action: The reader task is unable to retrieve
JOBLOG but continues processing. Problem determination: Review earlier messages in
the Data Store message log to determine the cause of
User response: If you want to retrieve JOBLOG, you the error.
must specify the DSTOPTS STOUNSTR(Y) option in
your data store initialization parameters System programmer response: Correct the errors
shown by the earlier messages and restart the indicated
task.
EQQFSR8I UNABLE TO RETRIEVE JOB JOBNMID
Explanation: Data store reader task is unable to EQQFSW4I JOB: JOBNAME- JOBNAME(DDN)
retrieve requested joblog. INVALID SYSOUT
System action: The reader task is unable to retrieve Explanation: The writer has received an empty data
JOBLOG but continues processing. set (dynamically allocated). DDN is returned to JES, but
Problem determination: Review the data store is always equal to JESMSGLG for the three DSIDs of
message log data set and the EQQDUMP data set to the job log. This message is displayed once for each
determine the cause of the problem. DSID found for the job.

User response: Contact your system programmer. System action: The writer task skips to another job
log that is to be stored.
System programmer response: If the problem persists,
save the message log and dump data sets, then contact System programmer response: None.
Customer Support.
| EQQFSW5W JOB: JOBNMID INCOMPLETE JOBLOG:
EQQFSW0E DATA STORE WRITER TASK | OPERINFO NOT GENERATED
INITIALIZATION FAILED | Explanation: Data store handled an incomplete MVS
Explanation: The writer task could not acquire all the | joblog: not all of the 3 MVS sysouts (JESMSGLG,
resources needed for normal operation. | JESJCL and JESYSMSG) were received. Data store needs
| all the 3 MVS sysouts to build the structured
System action: The writer task is not started. | information (operinfo): it will not be built.
Problem determination: Review earlier messages in | System action: Only unstructured information is
| stored.

108 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
| System programmer response: None.
EQQFV04E FN APPLICATION TERMINATED -
PARAMETER PROCESSING FAILURE
| EQQFSW6W JOB: JOBNMID JOBLOG PARSING Explanation: FN initialization processing encountered
| ERROR: OPERINFO NOT
an error in the parameters defined for it.
| GENERATED. REASON: STRURSN
System action: FN processing is terminated.
| Explanation: This message is issued by the Writer task
| of Data store when the joblog parsing fails and Problem determination: Review earlier messages in
| structured info cannot be built. The related job is the message log to determine the cause of the error.
| identified by JOBNMID and the reason for failing is
System programmer response: Correct all errors and
| explained by STRURSN.
restart the subsystem.
| System action: The structured information is not
| produced. If requested to do so, the unstructured joblog
EQQFV05E FN APPLICATION TERMINATED -
| is archived. The job is deleted from the destination
INITIALIZATION PROCESSING
| queue.
FAILURE
| User response: Check STRURSN to understand the
Explanation: FN initialization processing failed.
| cause of the error.
Messages that are issued preceding this message define
the cause of the error.
EQQFV00E DUPLICATE NAMES IN THE
System action: FN processing is terminated.
DSTOPTS SNA DESTINATIONS
Problem determination: Review earlier messages in
Explanation: A minimum of one name in the SNA
the message log to determine the cause of the error.
keyword destination list of the DSTOPTS initialization
statement is a duplicate of a previously-specified name. System programmer response: Correct all errors and
These names are the application names of potential restart the subsystem.
session partners and must be unique.
System action: FN processing is terminated. EQQFV06I FN APPLICATION ENDED
System programmer response: Correct the name (or Explanation: FN processing has completed and control
names) in error and restart the subsystem. is returned to the IBM Tivoli Workload Scheduler for
z/OS subsystem.
EQQFV01I FN APPLICATION STARTED System action: FN processing is terminated.
Explanation: The FN task has received control from User response: None.
the Data Store subsystem and is soon to start
initialization processing.
EQQFV07E INITIALIZATION FAILED - SNA
System action: FN processing continues. DESTINATION NOT SPECIFIED IN
FLOPTS
User response: None.
Explanation: In a Controller system, FN initialization
processing failed because no partner application IDs
EQQFV02E FN APPLICATION TERMINATED -
were specified in the SNA keyword of the FLOPTS
SETLOGON EXECUTION FAILURE
statement.
Explanation: A VTAM® SETLOGON macro used for
System action: FN processing is terminated.
enabling FN logon processing has failed. The reason for
this error is defined in detail by message EQQFV15E System programmer response: Add the missing
that precedes this message in the message log. information and restart the subsystem.
System action: FN processing is terminated.
EQQFV08I INITIALIZATION FAILED -
Problem determination: Review message EQQFV15E
SUBSYSTEM STOP REQUESTED
to determine the cause of the error.
Explanation: FN received a subsystem stop request
System programmer response: Correct the error (or
while in the initialization phase. FN was most likely
errors) and restart the subsystem.
waiting for some other IBM Tivoli Workload Scheduler
for z/OS resource to become active.
System action: FN processing is terminated.
User response: None.

Chapter 11. EQQFxxx Messages 109

 information, refer to the appropriate documentation for
EQQFV09E INITIALIZATION FAILED - CTLLNAM
the VTAM product installed on this system.
KEYWORD NOT SPECIFIED OR
INVALID System programmer response: If insufficient main
storage was the cause of the error, increase the region
Explanation: FN initialization processing failed
size and restart the IBM Tivoli Workload Scheduler for
because the CTLLUNAM keyword was not specified or
z/OS subsystem. For any other cause of the error,
was invalid.
contact Customer Support.
System action: FN initialization processing is
terminated.
EQQFV13E ACB EXSLT BUILD PROCESSING
System programmer response: Add the missing FAILED - R15 = R15 R00 = R00
information and restart the subsystem.
Explanation: The GENCB macro request that was
issued to generate an ACB EXLST block did not
EQQFV10E NIB BUILD PROCESSING FAILED - complete normally.
R15 = R15 R00 = R00
System action: FN processing is terminated.
Explanation: The GENCB macro request that was
Problem determination: Use the R15 and R00 return
issued to generate a NIB block did not complete
codes to determine the cause of the error. For more
normally.
information, refer to the appropriate documentation for
System action: FN processing is terminated. the VTAM product installed on this system.
Problem determination: Use the R15 and R00 return System programmer response: If insufficient main
codes to determine the cause of the error. For more storage was the cause of the error, increase the region
information, refer to the appropriate documentation for size and restart the IBM Tivoli Workload Scheduler for
the VTAM product installed on this system. z/OS subsystem. For any other cause of the error,
contact Customer Support.
System programmer response: If insufficient main
storage was the cause of the error, increase the region
size and restart the IBM Tivoli Workload Scheduler for EQQFV14E ACB BUILD PROCESSING FAILED -
z/OS subsystem. For any other cause of the error, R15 = R15 R00 = R00
contact Customer Support.
Explanation: The GENCB macro request that was
issued to generate the FN ACB did not complete
EQQFV11E RPL BUILD PROCESSING FAILED - normally.
R15 = R15 R00 = R00
System action: FN processing is terminated.
Explanation: The GENCB macro request that was
Problem determination: Use the R15 and R00 return
issued to generate an RPL block did not complete
codes to determine the cause of the error. For more
normally.
information, refer to the appropriate documentation for
System action: FN processing is terminated. the VTAM product installed on this system.
Problem determination: Use the R15 and R00 return System programmer response: If insufficient main
codes to determine the cause of the error. For more storage was the cause of the error, increase the region
information, refer to the appropriate documentation for size and restart the IBM Tivoli Workload Scheduler for
the VTAM product installed on this system. z/OS subsystem. For any other cause of the error,
contact Customer Support.
System programmer response: If insufficient main
storage was the cause of the error, increase the region
size and restart the IBM Tivoli Workload Scheduler for EQQFV15E VTAM MACRO REQUEST FAILURE -
z/OS subsystem. For any other cause of the error, DIAGNOSTIC INFORMATION:
contact Customer Support. NODE= NODE, REQUEST= X’REQ’
(NAMEREQ), RTNCD= X’RC’ (DECRC)
FDBK2= X’FDBK2’ (DFDBK2),
EQQFV12E NIB EXSLT BUILD PROCESSING
SSENSMI= SMI, USENSEI= USEI,
FAILED - R15 = R15 R00 = R00
SSENSEI=SSEI R00= X’R00’, R15=
Explanation: The GENCB macro request that was X’R15’
issued to generate a NIB EXLST block did not complete
Explanation: An error occurred when a VTAM request
normally.
was executed or scheduled. The variable items in the
System action: FN processing is terminated. message provide diagnostic information and have the
following meanings:
Problem determination: Use the R15 and R00 return NODE FN application LU-name
codes to determine the cause of the error. For more REQ VTAM request code in hexadecimal

110 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
NAMEREQ
EQQFV17E NAMEREQ REQUEST FAILURE -
VTAM request name
LU/APPLICATION NODE NOT
RC RTNCD feedback field value from RPL in
ACTIVE
hexadecimal
DECRC Explanation: The VTAM NAMEREQ request failed to
RTNCD feedback field value from RPL in complete successfully because the LU-name NODE was
decimal not active.
FDBK2 FDBK2 feedback field value from RPL in
System action: The FN processing is terminated.
hexadecimal
DFDBK2 System programmer response: Investigate why NODE
FDBK2 feedback field value from RPL in is inactive. Restart FN when NODE is active again.
decimal
SMI System sense modifier information from RPL
USEI User sense information from RPL EQQFV18E NAMEREQ REQUEST FAILURE -
SSEI System sense information from RPL VTAM ERROR, OR NCP/VTAM
R00 Register 0 return code after a VTAM macro INCOMPATIBILITY
request Explanation: The VTAM NAMEREQ request failed to
R15 Register 15 return code after a VTAM macro complete successfully because there was an error in
request. VTAM or an NCP/VTAM incompatibility. This message
System action: The action taken depends on the is preceded by message EQQFV15E in the IBM Tivoli
severity of the error situation. If at all possible, FN tries Workload Scheduler for z/OS message log.
to continue processing. For the most serious errors, for System action: The FN processing is terminated.
example, undefined feedback code, FN abends with a
dump and user code. Problem determination: Refer to message EQQFV15E
to determine the cause of the failure.
Problem determination: Use the diagnostic
information in the message to determine the cause of System programmer response: Restart FN when the
the error. For more information, refer to the appropriate VTAM errors have been corrected.
documentation for the VTAM product installed on the
system. EQQFV19E SESSION SETUP FAILED - PLU=LU
System programmer response: Analyze the diagnostic NOT AVAILABLE
information and the dump (if produced) to determine Explanation: The FN has not been able to establish a
the cause of the error. If this was not a user error, session for one of the following reasons:
contact Customer Support. v The controller is not started.
v The FN task in the controller is not available.
EQQFV16E NAMEREQ REQUEST FAILURE - v The LU specified in the CTLLUNAME keyword of
LU/APPLICATION NODE NOT FOUND the DSTOPTS initialization is not active or is not
defined.
Explanation: The VTAM NAMEREQ request failed to
complete successfully because the LU-name NODE The FN retries every 10 seconds until it is successful,
could not be found. The most likely reasons for the until the subsystem is stopped, or until the FN is
failure is: deactivated.
v A LU-name is specified incorrectly in the System action: The FN continues to attempt to
CTLLUNAME keyword of the DSTOPTS establish the LU-LU session.
initialization statement
System programmer response: Review the name
v the name NODE has not been properly defined to specified in the CTLLUNAME keyword of the
VTAM. DSTOPTS initialization statement and make sure that it
System action: The FN processing is terminated. is the correct one. If it is correct, ask the system
operator at the controller system to activate the
System programmer response: Review the name required resource.
specified in the CTLLUNAME keyword. Make sure that
it is correct and that a counterpart exists in the VTAM
definition statements. Correct the items in error and EQQFV20I ACB SUCCESSFULLY CLOSED
restart FN. Explanation: The FN has been successfully
disconnected from VTAM.
System action: The FN termination processing
continues.
User response: None.

Chapter 11. EQQFxxx Messages 111

EQQFV21W UNABLE TO CLOSE ACB EQQFV24I ACB SUCCESSFULLY OPENED
Explanation: The FN is unable to successfully Explanation: The FN has successfully established
disconnect from VTAM. contact with VTAM and is ready for further VTAM
processing.
System action: The FN termination processing
continues even though the ACB could not be closed. System action: The FN processing continues.
Problem determination: It is most likely that a VTAM User response: None.
error has caused this error. Check the system log for
VTAM error messages that can be related to this failure.
EQQFV25I ACB OPEN FAILURE (RC=X’RC’) -
System programmer response: Contact your VTAM VTAM SHUTTING DOWN
administrator.
Explanation: The FN was unable to establish contact
with VTAM because of an OPEN ACB failure. RC is the
EQQFV22E LOGON ATTEMPTED BY UNDEFINED ACB error flag value in hexadecimal.
LU/APPLICATION LU- CLSDST
System action: The FN continues processing.
ISSUED
User response: None.
Explanation: A session establishment attempt was
made by a remote FN application unknown to this host
IBM Tivoli Workload Scheduler for z/OS subsystem. EQQFV26E ACB OPEN FAILURE (RC=X’RC’) - FN
This message is issued only for a FN application at a IMPROPERLY DEFINED
IBM Tivoli Workload Scheduler for z/OS host.
Explanation: The FN task was unable to establish
System action: The FN task turns down the request contact with VTAM because of an OPEN ACB failure.
for the session by issuing a CLSDST macro. Processing RC is the ACB error flag value in hexadecimal.
continues for the IBM Tivoli Workload Scheduler for
z/OS host FN application. System action: The FN processing is terminated.

Problem determination: It is most likely that a name Problem determination: Use the return code to
in the DSTOPTS SNA keyword list of names has been determine the cause of the error. For more information,
misspelled or left out entirely. refer to the appropriate documentation for the VTAM
product installed on this z/OS system.
System programmer response: Stop the FN task for
which erroneous specifications have been given. System programmer response: Correct the problem
Correct the specifications in the DSTOPTS statement and restart IBM Tivoli Workload Scheduler for z/OS.
and restart the FN.
EQQFV27E ACB OPEN FAILURE (RC=X’RC’) -
EQQFV23E LOGON REQUEST FOR ABEND 1104 DUE TO SERIOUS
LU/APPLICATION LU THAT IS ERROR
ACTIVE - CLSDST ISSUED Explanation: The FN was unable to establish contact
Explanation: Data store/FN task connection was with VTAM because of an OPEN ACB failure. RC is the
attempted, but the session is already active. ACB error flag value in hexadecimal.

System action: The request for a session is turned System action: The FN processing is abnormally
down and FN task process continues. terminated with a dump (abend code 1104).

Problem determination: The most likely reason for Problem determination: Use the R15 and R00 return
this error is that more the same LU-name was used to codes to determine the cause of the error. For more
define more data stores or SNA connected trackers. information, refer to the appropriate documentation for
Check both the controller FLOPTS definitions the VTAM product installed on this z/OS system.
(CTLLUNAM, SNADEST), the data store DSTOPTS System programmer response: Analyze the 1104
definitions (DSTLUNAM, CTLLUNAM) and the tracker abend dump. If this was not a user error, contact
OPCOPTS definitions (NCFAPPL). Customer Support.
System programmer response: Stop the controller,
data stores, and trackers that have incorrect definitions. EQQFV28W ACB OPEN FAILED FOR THE LAST 2
Correct them, specifying a different LU-name and MINUTES - VTAM NOT ACTIVE
restart them.
Explanation: The FN failed to establish contact with
VTAM during the last two minutes because VTAM was
not active. This message is issued every two minutes
until contact is made.

112 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
System action: The FN continues to attempt to
EQQFV34E NAMEREQ REQUEST FAILURE -
establish contact with VTAM until contact is made or
LU/APPLICATION NODE INHIBITED
until the IBM Tivoli Workload Scheduler for z/OS
subsystem is stopped. Explanation: The VTAM NAMEREQ request failed to
complete successfully because the LU-name NODE was
System programmer response: Ask your network
inhibited. The most likely reason for the failure is that
operator to activate VTAM.
either the cross-domain FN partner NODE has been
deactivated or the partner VTAM system has been
EQQFV29I VTAM TERMINATION, OR FN taken down.
DEACTIVATION, STOPPED SESSION
System action: If NAMEREQ is the REQSESS request,
SETUP ATTEMPTS
the FN continues processing with session establishment
Explanation: Session initiation attempts were stopped attempts every 10 seconds. For other VTAM requests,
because VTAM is terminating or the FN task was FN processing is terminated.
deactivated.
System programmer response: Ask the network
System action: The FN termination processing operator to activate the VTAM or FN application, or
continues. both applications, on the cross-domain partner system.

User response: None.

EQQFV36I SESSION HOME-DEST ESTABLISHED
EQQFV31I SUBSYSTEM STOP REQUEST Explanation: A session has been established between
TERMINATED SESSION SETUP the home application HOME and the destination
ATTEMPTS application DEST.
Explanation: A remote FN application was in the System action: The FN continues processing.
process of initiating a session when the subsystem was
User response: None.
stopped.
System action: The FN termination processing
EQQFV37I SESSION HOME-DEST ENDED
continues.
Explanation: The session between the home
User response: None.
application HOME and the destination application
DEST has ended.
EQQFV32I SUBSYSTEM STOP REQUEST
System action: The FN continues processing.
TERMINATED ACB OPEN ATTEMPTS
User response: None.
Explanation: The FN was in the process of
establishing contact with VTAM when the subsystem
was stopped. EQQFV41E THE FN TASK IGNORED THE
FOLLOWING ELEMENT ON THE FN
System action: The FN termination processing
QUEUE DQE
continues.
Explanation: An invalid element has been found by
User response: None.
the FN task. Possibly, the first four bytes of the element
do not match the IBM Tivoli Workload Scheduler for
EQQFV33E ACB OPEN FAILED FOR THE LAST 2 z/OS character string ’DQE’. (The fourth byte is a
MINUTES - FN APPLICATION NOT blank space.)
ACTIVE
System action: The FN task no longer processes the
Explanation: The FN failed to establish contact with element, but continues normal processing.
VTAM during the last two minutes because the FN
System programmer response: Save the Tivoli
application was not activated. The FN attempts to
Workload Scheduler for z/OS message log data set
establish contact every 10 seconds until contact is
containing this error message and contact Customer
made. This message is issued every two minutes until
Support.
contact is established.
System action: The FN continues to attempt to
EQQFV42E THE FN TASK IGNORED THE
establish contact with VTAM until contact is made or
FOLLOWING DATA, RECEIVED
until the scheduler subsystem is stopped.
FROM ’NODE’ DQE
System programmer response: Ask the network
Explanation: The FN task did not recognize the type
operator to activate the VTAM LUs.
of data received from the application. This message is
issued once for every invalid receive operation.

Chapter 11. EQQFxxx Messages 113

System action: The FN task continues processing
System programmer response: Verify that the session
parameters specified in the VTAM LOGMODE table are
valid. Especially check that the ru-sizes are not zero.
If this message occurs during normal execution and the
VTAM LOGMODE definitions are correctly specified,
contact Customer Support.

EQQFV43E INVALID RU-SIZE SPECIFIED IN ’LU’

SESSION PARAMETERS
Explanation: The ru-sizes specified in the session
parameters are not valid.
System action: The FN continues processing, but the
specified session is not established.
System programmer response: Verify that the ru-sizes
specified are valid. If necessary, specify different
ru-sizes, and stop and restart the FN task.

114 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 12. EQQGnnn Messages
EQQG001I SUBTASK SUBTASK HAS STARTED EQQG004E SUBTASK SUBTASK ABENDED, IT IS
RESTARTED AT RETRYAT
Explanation: The subtask SUBTASK has been
successfully initialized. Explanation: A serious error caused the SUBTASK
subtask to end abnormally. SUBTASK has been able to
System action: Processing for the indicated subtask is
restart, at RETRYAT.
started.
System action: SUBTASK resumes normal processing,
User response: None.
but one or more requests for service may have been
rejected. The dialog user requesting service may or may
EQQG002E INITIALIZATION OF SUBTASK not be informed about the completion or termination of
SUBTASK FAILED. REASON CODE: RS the requests. A dump is created. Message EQQX271E,
when issued, informs the dialog user that the request
Explanation: The indicated subtask could not acquire has failed due to a serious error in SUBTASK. If the
all the resources needed for normal operation. subtask is GENERAL SERVICE, the dialog user must
System action: Processing continues but no requests press “attention” to break the request.
from the dialog or the program interface for IBM Tivoli Problem determination: Review the dump data set to
Workload Scheduler for z/OS can be served. determine what caused the problem.
Problem determination: The message variable RS can User response: Inform the system programmer about
have the following values: the error and, (if the error can be reproduced), of the
02 The main task, the normal mode manager, is sequence of dialog requests leading to the error.
unavailable.
11 The application description file is unavailable. System programmer response: Collect relevant
12 The workstation description file is unavailable. information about the sequence of events leading to
13 The calendar file is unavailable. this error, make the dump data set and the message log
14 The period file is unavailable. available for inspection, and contact Customer Support.
15 The all workstations closed record is
unavailable.
EQQG005E VALIDATION FAILED FOR FILE: FILE,
16 The operator instruction file is unavailable.
REASON: REASON, OFFSET: POS
17 The JCL variables file is unavailable.
18 The resource description file is unavailable. Explanation: The record that was to be written to the
19 The ETT criteria file is unavailable. IBM Tivoli Workload Scheduler for z/OS database was
21 End-to-end input/output queue file is rejected because it was incorrect.
unavailable.
System action: No update to the database is made.
22 End-to-end input/output queue file
initialization failed. Problem determination: FILE gives the database on
which the update was attempted, REASON indicates
User response: Review earlier messages in the IBM
the reason for the failure, and POS indicates the failing
Tivoli Workload Scheduler for z/OS message log to
position in hexadecimal form within the record.
determine the cause of the error.
See Chapter 38, “Reason Codes”, on page 463 for a list
System programmer response: Correct errors shown
of the reason codes and their meanings.
by the earlier messages and restart the subtask
indicated. User response: Look in the dump data set (ddname
EQQDUMP) for further information about the error.
This data set contains the record and the position of the
EQQG003I SUBTASK SUBTASK HAS ENDED
error. If you cannot find a valid reason for the error,
Explanation: This message is issued when the IBM contact your system programmer.
Tivoli Workload Scheduler for z/OS subsystem is being
System programmer response: If you cannot find a
stopped by an operator command.
valid reason for the error, make the dump data set
System action: IBM Tivoli Workload Scheduler for (ddname EQQDUMP) and the message log available
z/OS termination processing continues. for inspection. Contact Customer Support.
User response: None. .* WTO=YES ROUTE=2

© Copyright IBM Corp. 1991, 2003 115

 issued every n minutes, where n is either the value
EQQG006I THE FUNC FUNCTION IS ACTION BY
specified in the JTOPTS keyword STATIM, if it has a
USER
nonzero value, or the default of 30.
Explanation: This message confirms and logs some
It consists of column headers defining the values of the
action taken to a IBM Tivoli Workload Scheduler for
EQQG011I message following.
z/OS function. FUNC is either AUTOMATIC JOB
RECOVERY or JOB SUBMISSION. ACTION is either The following column headers are defined:
ACTIVATED or DEACTIVATED. USER is the user ID TYPE The request for which data was gathered.
of the user who requested the function. The message TOTAL
confirms that the dialog request has been successfully The total number of requests of this type.
accomplished. NEWRQS
The number of requests of this type since the
System action: Processing continues.
last message.
User response: None. .ALARM=YES TOTTIME
The total time, in seconds, used to process this
request.
EQQG008W THE REQUEST FAILED, GENERAL
NEWTIME
SERVICE QUEUING PROBLEM,
The total time, in seconds, used to process this
REASON: XSSRS
request since the last message.
Explanation: The request was rejected because of an TOTAVG
interface problem in the General Service function. The average time, in seconds, used to process
a request of this type.
System action: The system waits for you to respond. NEWAVG
Problem determination: Review the IBM Tivoli The average time, in seconds, used to process
Workload Scheduler for z/OS message log for errors a request of this type since the last message.
related to General Service to determine the cause of the
error. The value in the TYPE column is one of the following
resources:
User response: Try again. If the error persists, contact ALL Total line for all resources
your system programmer. AD Application description
System programmer response: Correct the General AR Automatic recovery
Service error given in the IBM Tivoli Workload PERI Calendar periods
Scheduler for z/OS message log. .ALARM=YES CALE Calendar
WSCL All workstations closed
WSD Workstation description
EQQG009W INSUFFICIENT VIRTUAL STORAGE LTPS Long-term plan
FOR THE COMPLETE LIST, REASON: PLAN Long-term plan status
XSSRS WS Current plan workstation status
Explanation: The requested list could not be displayed WSRL Current plan workstation status requested
because the amount of virtual storage in the dialog from the ready list
address space was not sufficient. RL Current plan ready list
OPER Current plan operation
System action: A partial list is displayed, or no list at OPRL Current plan operation requested from the
all. ready list
User response: If this is a request from a dialog PREP Preparation CPU operations
function in which a selection criterion can be specified, DEPC Dependency operation
change the selection criterion to select fewer items. R3P Current plan operation record
Increase the region size at TSO logon. C3C Current plan occurrences
C3CR Current plan occurrences requested from the
ready list
EQQG010I GENERAL SERVICE REQUEST CP_G Current plan general
STATISTICS FOLLOW: TYPE TOTAL JCL JCL Repository record
NEWRQS TOTTIME NEWTIME JSUB Job submission
TOTAVG NEWAVG JCLA Automatic JCL preparation
JCLP Promptable JCL variables
Explanation: This message is issued if the GENERAL
JCLT JCL tailoring
SERVICE task statistics are active. This can be done
JVAR Tailoring session
either by specifying the STATMSG(GENSERV) keyword
JV JCL variable table
in the JTOPTS initialization statement or with the
RACF Refresh RACF resources
modify command, /F subsys,GENSTA=ON.
SRES Special resources
If any requests have been processed, this message is ETT Event-triggered tracking

116 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
OI Operator instruction for General Service processing, was in a particular
STAT IBM Tivoli Workload Scheduler for z/OS interval. For example, Q20 on the queue size line gives
status record the number of times that the queue size was between
MCP Modify current plan 11 and 20 requests.
DEP Successor candidates
System action: Normal IBM Tivoli Workload
CATM Restart and cleanup
Scheduler for z/OS processing continues.
OTHR All other resources
User response: None.
System action: Normal IBM Tivoli Workload
Scheduler for z/OS processing continues.
EQQG013I TYPETOTSZQ1Q2Q3 Q4Q5Q6Q7Q8
User response: None.
Explanation: This message is issued if the GENERAL
SERVICE task statistics are active. This can be done
EQQG011I TYPENUMRQNEWRQTTOT
either by specifying the STATMSG(GENSERV) keyword
TNEWTAVGNAVG
in the JTOPTS initialization statement or with the
Explanation: This message is issued if the GENERAL modify command, /F subsys,GENSTA=ON.
SERVICE task statistics are active. This can be done
If any requests have been processed, this message is
either by specifying the STATMSG(GENSERV) keyword
issued every n minutes, where n is either the value
in the JTOPTS initialization statement or with the
specified in the JTOPTS keyword STATIM, if it has a
modify command, /F subsys,GENSTA=ON.
nonzero value, or the default of 30.
If any requests have been processed, this message is
In the message text shown above:
issued every n minutes, where n is either the value
nnnnn A 5-digit number.
specified in the JTOPTS keyword STATIM, if it has a
nonzero value, or the default of 30.
This message contains data about the General Service
In the message text shown above: queue size. See the description of message EQQG012I
nnnnn A 5-digit number. for an explanation of what the data values mean.
secs The number of seconds.
System action: Normal IBM Tivoli Workload
Scheduler for z/OS processing continues.
The message contains data about how the general
service subtask processed requests for one resource. See User response: None.
the description of message EQQG010I for an
explanation of what the data values mean.
EQQG014W REQUEST TERMINATED BECAUSE
System action: Normal IBM Tivoli Workload TIME LIMIT IS EXCEEDED
Scheduler for z/OS processing continues.
Explanation: A general service request has terminated
User response: None. because the requesting process: a program interface
(PIF) program or a dialog user, did not respond within
10 minutes.
EQQG012I GENERAL SERVICE QUEUE
STATISTICS FOLLOW: TYPE TOTAL System action: Processing continues.
Q1 Q2 Q5 Q10 Q20 Q50 Q100 >100
User response: None.
Explanation: This message is issued if the GENERAL
SERVICE task statistics are active. This can be done
either by specifying the STATMSG(GENSERV) keyword EQQG015W REQUEST TERMINATED -
in the JTOPTS initialization statement or with the REQUESTOR NO LONGER
modify command, /F subsys,GENSTA=ON. CONNECTED

If any requests have been processed, this message is Explanation: A general service request was terminated
issued every n minutes, where n is either the value because the requesting process: a program interface
specified in the JTOPTS keyword STATIM, if it has a (PIF) program or a dialog user, is no longer connected
nonzero value, or the default of 30. to the general service subtask. The connection can be
lost if the requestor is canceled, or if a dialog user
The message shows the size and delay of the General presses the ATTN (attention) key, after a request for
Service queue since the message was last issued. service has been sent to the controller and before a
response has been received.
The value below the TYPE heading can be either
QUEUE SIZE or QUEUE DELAY. The value below the System action: Processing continues.
TOTAL heading gives the total number of times that
the General Service queue was emptied. The values User response: None. .ALARM=YES
below the Qx headings give the number of times that
either the length of the queue or the time spent waiting

Chapter 12. EQQGnnn Messages 117

 System action: The graph request is ignored.
EQQG100E GDDM® COULD NOT BE LOADED
Processing continues.
Explanation: When requesting a graph, IBM Tivoli
User response: Contact your system programmer.
Workload Scheduler for z/OS could not load GDDM*.
System programmer response: Make sure that the
System action: The graph request is ignored.
ISPLLIB libraries are updated to contain the graph net
Processing continues.
building routines. The name of the routine can be seen
User response: Contact your system programmer. in the ISPF log. See message EQQX009.
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 redisplayed and
prompts you for a correct attribute value.
User response: Correct the invalid attribute.

EQQG107I THE GDDM IS NOT ALLOWED IN

SPLIT SCREEN 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.

EQQG109E NET LOADER MODULE COULD NOT

BE LOADED
Explanation: When requesting a graph, IBM Tivoli
Workload Scheduler for z/OS could not load the net
building routine.

118 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 13. EQQHnnn Messages
EQQH001E THE NETVIEW INTERFACE MODULE EQQH203E THE KEYWORD H20301 APPEARS
CNMNETV COULD NOT BE LOADED TOO MANY TIMES
Explanation: CNMNETV was not found in the library Explanation: A statement is specified with two or
search path. more identical keywords.
System action: IBM Tivoli Workload Scheduler for System action: IBM Tivoli Workload Scheduler for
z/OS continues, but the generic alert functions as z/OS continues to verify the statement, but the
requested in the GENALERT keyword of the ALERT database is not updated.
initialization statement are disabled. Instead, IBM Tivoli
User response: Remove the duplicate keyword and
Workload Scheduler for z/OS generates WTO messages
rerun.
for the error conditions specified in the GENALERT
keyword.
EQQH204E THE STATEMENT H20401 IS
System programmer response: Ensure that the
UNDEFINED
CNMNETV module is accessible and restart IBM Tivoli
Workload Scheduler for z/OS. Explanation: The statement H20401 is not recognized.
System action: Processing of the statement is
EQQH003E SEND GENERIC ALERT TO NETVIEW terminated.
FAILED WITH RC=RC
User response: Correct the invalid statement and
Explanation: Request type 12 sent to the NetView* PPI rerun.
failed.
System action: A WTO is issued instead of the generic EQQH205E THE COMMAND IS MISSING OR
alert. THE FORMAT IS INVALID
System programmer response: Check NetView Explanation: The statement does not start with a valid
documentation for further information. command.
System action: Processing of the statement is
EQQH201W AN INCORRECTLY PLACED COMMA terminated.
AT H20101 IS IGNORED
User response: Add a valid command or correct the
Explanation: You have coded a comma that is not invalid command and rerun.
required at H20101.
System action: The statement is accepted. The EQQH206W A MISSING END OF COMMENT IS
extraneous comma is ignored.Tivoli Workload ASSUMED AT THE END OF THE
Scheduler for z/OS continues verifying the statements. STATEMENT
User response: If you rerun the job, remove the extra Explanation: A start of comment delimiter (/*) has
comma. been detected, without a corresponding end of
comment (*/).
EQQH202W AN INCORRECTLY PLACED COMMA System action: Tivoli Workload Scheduler for z/OS
IN THE PARMSTRING IS IGNORED assumes the comment ends after the control statement.
Explanation: An unnecessary comma is coded in the User response: Add an end of comment (*/) and
parameter. rerun if required.
System action: The parameter is accepted and the
extraneous comma is ignored. The IBM Tivoli Workload EQQH207W A MISSING END QUOTE IS
Scheduler for z/OS continues verifying the commands ASSUMED AT THE END OF THE
STATEMENT
User response: Remove the extra comma and rerun.
Explanation: The quote for this character string is not
closed.
System action: IBM Tivoli Workload Scheduler for

© Copyright IBM Corp. 1991, 2003 119

z/OS assumes the quote ends after the control
EQQH214E TOO MANY LEFT PARENTHESES OR
statement.
AN INVALID VALUE FOUND AT
User response: Add a quote and rerun if required. H21401
Explanation: Too many parentheses are provided at
EQQH208E THE KEYWORDS H20801 AND H20802 H21401 or you have provided an invalid value for a
ARE EXCLUSIVE keyword.

Explanation: Two mutually exclusive keywords are System action: Processing of the statement is
entered on the same statement. terminated.

System action: Processing of the statement is User response: Correct the statement and rerun.
terminated.
User response: Remove one of the keywords and EQQH215E TOO MANY LEFT PARENTHESES ARE
rerun. INSERTED IN THE PARMSTRING
Explanation: Too many left parentheses are provided.
EQQH209E AN INVALID RIGHT PARENTHESIS
System action: Processing of the statement is
WAS FOUND AT H20901
terminated.
Explanation: More right parentheses than left
User response: Remove the extra left parentheses and
parentheses are coded.
rerun.
System action: Processing of the statement is
terminated.
EQQH216E A LEFT PARENTHESIS IS MISSING
User response: Correct the number of parentheses and BEFORE H21601
rerun.
Explanation: A left parenthesis is missing.
System action: Processing of the statement is
EQQH210E TOO MANY VALUES ARE CODED IN
terminated.
THE KEYWORD H21001
User response: Add the missing left parenthesis and
Explanation: The keyword H21001 has too many
rerun.
coded values.
System action: Processing of the statement is
EQQH217E AN INVALID COMMA IS INSERTED
terminated.
IN H21701
User response: Correct the keyword values and rerun.
Explanation: A keyword and its values are separated
by an invalid comma.
EQQH211E AN INVALID VALUE H21101
System action: Processing of the statement is
SPECIFIED OR A KEYWORD IS
terminated.
MISSPELLED
User response: Remove the comma and rerun.
Explanation: Either the value H21101 is not valid for
the keyword or the keyword is misspelled.
EQQH218W A MISSING RIGHT PARENTHESIS IS
System action: Processing of the statement is
ASSUMED AT THE END OF THE
terminated.
STATEMENT
User response: Correct the statement and rerun.
Explanation: The right parenthesis, which should
delimit the end of statement, is missing. Too many
EQQH213E A VALUE IS MISSING AFTER H21301 items might be specified.

Explanation: Not enough keyword values are System action: The processing continues.
specified for H21301.
User response: Specify the keyword and its value in
System action: Processing of the statement is the correct format and rerun.
terminated.
User response: Add the missing keyword value (or EQQH219E THE REQUIRED KEYWORD H21901 IS
values) and rerun. MISSING
Explanation: The keyword H21901 is missing from the
statement.

120 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
System action: Processing of the statement is
EQQH301E NUMERIC FACTOR H30101 EXCEEDS
terminated.
CYCLE H30102 LENGTH
User response: Specify the missing keyword and
Explanation: A numeric factor is out of range.
rerun.
System action: The rule is invalid and is not saved.
EQQH220E A REQUIRED KEYWORD IS MISSING. User response: Correct the numeric factor or cycle
SPECIFY EITHER H22001 OR H22002 specification and rerun.
Explanation: You must specify either H22001 or
H22002. EQQH302E NUMERIC FACTOR H30201 AND
WEEKDAY > CYCLE H30202 LENGTH
System action: Processing of the statement is
terminated. Explanation: A numeric factor combined with a week
day exceeds the period length. The name of a
User response: Specify one of the keywords and
predefined cycle is preceded by two unprintable
rerun.
characters (..).
System action: The rule is invalid and is not saved.
EQQH221E AN INVALID H22101H22102 WAS
FOUND IN THE KEYWORD H22103 User response: Correct the numeric factor or cycle
specification and rerun.
Explanation: The value type H22101 in field H22102
for keyword H22103 is invalid.
EQQH303E THE USER PERIOD H30301 DOES NOT
System action: Processing of the statement is
EXIST
terminated.
Explanation: The specified user period is invalid. The
User response: Specify a valid value and rerun.
name of the scheduler predefined cycles is preceded by
two unprintable characters (..).
EQQH222E AT LEAST ONE KEYWORD MUST BE
System action: The rule is invalid and is not saved.
SPECIFIED FOR STATEMENT H22201
User response: Correct the period specification and
Explanation: You must specify at least one keyword
rerun.
for H22201.
System action: Processing of the statement is
EQQH304E THE CALENDAR H30401 DOES NOT
terminated.
EXIST
User response: Correct the command and rerun.
Explanation: The specified calendar H30401 is invalid.
System action: The rule is invalid and is not saved.
EQQH223E THE EMPTY QUOTED STRING IS
INVALID FOR THE KEYWORD H22301 User response: Correct the calendar specification and
rerun.
Explanation: No values are specified for keyword
H22301.
EQQH305E ORIGIN SHIFT H30501 IS TOO LARGE
System action: Processing of the statement is
FOR THE PERIOD H30502.
terminated.
Explanation: The number specified for origin shift is
User response: Correct the string and rerun.
out of range for period H30501. The name of the
scheduler predefined cycles is preceded by two
EQQH224E REQUIRED KEYWORD(S) MISSING unprintable characters (..).
IN COMMAND H22401
System action: The rule is invalid and is not saved.
Explanation: One or more required keywords were
User response: Correct the origin shift or period
not found in the statement H22401.
specification and rerun.
System action: Processing of the statement is
terminated.
EQQH306W SELECTION OF EVERY AND
User response: Correct the statement and rerun. 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

Chapter 13. EQQHnnn Messages 121

without any numeric factor. This may not be what you
EQQH402W THE PERIOD H40201 HAS NO ORIGIN
intended.
WITHIN RULE VALIDITY.
System action: The system waits for you to respond.
Explanation: The period H40201 has no origin within
User response: Decide whether the rule should be rule validity period.
defined using EVERY or ONLY. Change the selected
System action: No dates are generated.
fields if required. If you are unsure of the affect of
EVERY and ONLY use the GENDAYS command. User response: Correct the period specification or
validity period and rerun.
EQQH308W DUPLICATE VALUE(S) H30801
IGNORED. EQQH501E NUMERIC FACTOR H50101 EXCEEDS
CYCLE H50102 LENGTH
Explanation: You have specified duplicate values.
Only one of the values is used. Explanation: A numeric factor is out of range.
System action: The duplicate value is removed. System action: The rule is invalid and is not saved.
User response: Check the specified values and correct User response: Correct the numeric factor or cycle
them if necessary. specification and rerun.

EQQH309E THE SAVED RULE VALUE HAS BEEN EQQH502E NUMERIC FACTOR H50201
DESTROYED, PLEASE REENTER THE TOGETHER WITH WEEKDAY
INFO EXCEEDS CYCLE H50202 LENGTH
Explanation: The rule value saved on the application Explanation: A numeric factor combined with a week
description database is invalid and cannot be used. day exceeds the period length. The name of a
predefined cycle is preceded by two unprintable
System action: The rule is invalid and must be
characters (..).
reentered before use.
System action: The rule is invalid and is not saved.
Problem determination: The dump data set (ddname
EQQDUMP) contains a dump of the rule value. User response: Correct the numeric factor or cycle
specification and rerun.
User response: Reenter the rule and rerun.

EQQH503E THE USER PERIOD H50301 DOES NOT

EQQH310E UNEXPECTED ERROR IN THE
EXIST
CALENDAR ROUTINE
Explanation: The specified user period is invalid. The
Explanation: The calendar routine used in the rule
name of the scheduler predefined cycles is preceded by
interpretation or date generation has returned an
two unprintable characters (..).
unexpected reason code.
System action: The rule is invalid and is not saved.
System action: Processing of this specific rule cannot
continue. User response: Correct the period specification and
rerun.
Problem determination: The dump data set (ddname
EQQDUMP) contains a dump of the control blocks.
EQQH504E THE CALENDAR H50401 DOES NOT
User response: This is likely to be an internal error. If
EXIST
possible, rerun the request.
Explanation: The specified calendar H50401 is invalid.
System programmer response: If you cannot find a
valid reason for the error, save the dump data set and System action: The rule is invalid and is not saved.
the message log and contact Customer Support.
User response: Correct the calendar specification and
rerun.
EQQH401I NO DATE GENERATED BY THIS
RULE
EQQH505E ORIGIN SHIFT H30501 IS TOO LARGE
Explanation: No date is generated by this rule. FOR THE PERIOD H30502.
System action: No dates are generated. Explanation: The number specified for origin shift is
out of range for period H50501. The name of a
User response: Check the rule and the validity period.
predefined cycle is preceded by two unprintable
characters (..).
System action: The rule is invalid and is not saved.

122 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
User response: Correct the origin shift or period messages for a valid rule, and by up to five error
specification and rerun. messages for an invalid rule.
System action: If ’VALID RULE’ is returned, the date
EQQH509E THE SAVED RULE VALUE HAS BEEN generating rule definition is accepted. If ’INVALID
DESTROYED, PLEASE REENTER THE RULE’ is returned, the rule is rejected.
INFORMATION
User response: If the rule is rejected, correct the rule
Explanation: The rule value saved on the application definition according to the diagnostics provided by the
description database is invalid and cannot be used. messages.
System action: The rule is invalid and must be
reentered before use. EQQH701E EITHER ONLY OR EVERY MUST BE
SELECTED
Problem determination: The dump data set (ddname
EQQDUMP) contains a dump of the rule value. Explanation: ONLY and EVERY are mutually
exclusive and one of them has to be selected for a valid
User response: Reenter the rule and rerun.
rule definition.
System action: The request is rejected.
EQQH510E UNEXPECTED ERROR IN THE
CALENDAR ROUTINE User response: Select one of ONLY and EVERY.
Explanation: The calendar routine used in the rule
interpretation or date generation has returned an EQQH702E MAKE AT LEAST ONE
unexpected reason code. SELECTION/SPECIFICATION FROM
EACH RULE SECTION
System action: Processing of this specific rule cannot
continue. Explanation: You have failed to make at least one
selection/specification from each rule section.
Problem determination: The dump data set (ddname
EQQDUMP) contains a dump of the control blocks. System action: The request is rejected.
User response: This is likely to be an internal error. If User response: Select at least one from each section.
possible, rerun the request.
System programmer response: If you cannot find a EQQH703E THE ENTRY IS INVALID, ENTER
valid reason for the error, save the dump data set and XRSEL OR LEAVE BLANK
the message log and contact Customer Support.
Explanation: You have entered an invalid value in the
selection field.
EQQH511E CALENDARS DATASPACE CREATION
System action: The request is rejected.
FAILED
User response: Change the field to a valid value.
Explanation: An error occurred while the batch
program or the normal mode manager subtask was
trying to create the calendar dataspace. EQQH704E THE ENTRY IS INVALID, ENTER A
DAY IN THE RANGE 1 TO 999
System action: The job or the normal mode manager
is terminated. Explanation: You have entered an invalid day in the
field. It must be in the range 1 to 999.
User response: Contact your system programmer.
System action: The request is rejected.
System programmer response: Review the IBM Tivoli
Workload Scheduler for z/OS message log to determine User response: Change the day to a valid value.
the cause of the error. If you cannot determine the
cause and if the error persists, contact Customer
Support. EQQH705E A PERIOD NAME BEGINS
ALPHABETICALLY, REMAINDER IS
ALPHANUMERIC
EQQH700I HIGHEST RETURN CODE FROM
PARSER IS H70001 Explanation: You have not entered a valid period
name. A valid period name must be maximum of eight
Explanation: This information message is displayed characters, where the first character must be
after parsing a date generating rule. The short message alphabetical and the remaining characters must be
is set to ’VALID RULE’ if the parser returns 04 or alphanumeric or national.
lower, ’INVALID RULE’ for all other return codes. The
return code value is shown in H70001. This message is System action: The request is rejected.
followed by one or more information or warning User response: Specify a valid period name.

Chapter 13. EQQHnnn Messages 123

EQQH706E THE ENTRY IS INVALID, ENTER A EQQH710I NO DATES GENERATED FOR THE
VALUE IN THE RANGE 1 TO 53 INTERVAL IVLFROMIVLTO
Explanation: You have entered an invalid week Explanation: GENDAYS is unable to generate dates
number in the field. It must be in the range 1 to 53. for the rule and interval specified.
System action: The request is rejected. System action: No dates are generated.
User response: Change the week number to a valid User response: Check the rule definitions and other
value. factors that have an impact on date generation, for
example, interval, calendar, user periods, and free day
rule.
EQQH707E THE ENTRY IS INVALID, ENTER A
NUMBER IN THE RANGE 0 TO 999
EQQH711E INTERVAL START IVLFROM IS LATER
Explanation: You have entered an invalid number in
THAN INTERVAL END IVLTO
the field. It must be in the range 0 to 999.
Explanation: The start date of the generating interval
System action: The request is rejected.
is later than the end date.
User response: Change the number to a valid value.
The start date of the interval is the latest of these dates:
v Run cycle in-effect date
EQQH708E H70801 TOGETHER WITH SPECIFIC
v Application description (AD) valid-from date
H70801 SELECTION(S) IS
AMBIGUOUS v 1 January of the current year.

Explanation: Message variable H70801 is DAY, WEEK The end date of the interval is the earliest of these
or MONTH. You have selected one of the following dates:
combinations: v Run cycle out-of-effect date
v DAY together with specific days, for example, v AD valid-to date
WORKDAY, MONDAY, FRIDAY v 31 December of the current year plus three years.
v WEEK together with specific week numbers, for
A maximum of four years can be displayed.
example, WEEK 26 and WEEK 34
v MONTH together with specific months, for example, System action: The request is rejected.
APRIL, AUGUST and DECEMBER. User response: Check the dates, correct any
These specifications are redundant and make the rule inconsistency, and reenter the GENDAYS command.
ambiguous.
System action: The request is rejected. EQQH712E UNABLE TO GENERATE DATES FOR
THE INTERVAL IVLFROMIVLTO
User response: Remove the redundancies to make the
selection unambiguous. Explanation: GENDAYS is not able to generate dates
for the rule because the entire requested interval is
outside the limits of the internal calendar
EQQH709E RULE DEFINITION CANNOT BE
MAPPED, THE RULE MUST BE When the interval is calculated:
REDEFINED v The start date of the interval is the later of the run
cycle in-effect date and the application description
Explanation: The internal representation of a rule
(AD) valid-from date.
cannot be interpreted and the corresponding rule
command cannot be derived from it. This is most likely v The end date of the interval is the earlier of the run
caused by an internal error of the product. cycle out-of-effect date and the AD valid-to date.

System action: The rule command is not mapped and GENDAYS can generate a maximum of four years
rule selections are not shown. starting at 1 January of the current year and ending on
31 December of the current year plus three.
User response: Copy the application description (AD)
temporarily to another AD identification. Update the System action: The request is rejected.
original AD by redefining the erroneous rule so as to User response: Check the dates for the interval,
be able to continue using the original rule or rules. correct any inconsistency, and reenter the GENDAYS
Contact your local system administator to pursue the command.
error analysis using the copied version.

124 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 14. EQQICnn Messages
System programmer response: Correct the errors and
EQQIC00I FILE FILE HAS BEEN CONVERTED
resubmit the file migration batch job.
NCOPY RECORDS COPIED, NUPD
RECORDS UPDATED, NSKIP
RECORDS SKIPPED EQQIC03E LOGICAL RECORD SIZE FOR THE
INPUT DATA SET, DDNAME SYSIN,
Explanation: AVSAM file has been successfully built
IS NOT VALID
from the corresponding file in a different release of IBM
Tivoli Workload Scheduler for z/OS. This message Explanation: The file migration program could not use
documents the number of records copied without the input data set, SYSIN, because its logical record
change, the number of modified records, and the length is not 80 bytes.
number of records in the input file that were not used.
System action: The migration program is terminated.
System action: The migration program continues
processing by reading the next CONVERT statement Problem determination: Check that the SYSIN DD
from the input file. statement exists and is correctly coded.

Problem determination: If there is a problem using System programmer response: Correct the errors and
the output file, verify that the statistical information in resubmit the file migration batch job. If necessary, copy
this message is correct. SYSIN statements to a file that has record size 80 bytes.

System programmer response: None.

EQQIC04E EQQICTOP TERMINATED BECAUSE
OF UNRECOVERABLE ERRORS
EQQIC01E THE INPUT DATA SET, DDNAME =
SYSIN, COULD NOT BE OPENED Explanation: A severe error occurred during the
execution of the file migration program.
Explanation: The file migration program could not
open its input data set. System action: The migration program is terminated.

System action: The migration program is terminated. Problem determination: Review the message log and
the dump data set.
System programmer response: Check that the SYSIN
DD statement exists and is correctly coded. System programmer response: If you cannot
determine the cause of the error, contact Customer
Correct the errors and resubmit the file migration batch Support.
job.
EQQIC05E WRITE OF NEW RECORD FAILED,
EQQIC02E UNABLE TO CONVERT FILE FILE RECORD WITH SAME KEY IS
ALREADY PRESENT
Explanation: The file migration program could not
execute the requested file conversion. This message is Explanation: A VSAM error occurred when writing a
preceded by one or more error messages that describe new record to the output data set. Error codes indicate
the problem. that the output data set contains a record with the
same key as the new record.
System action: The migration program continues
processing by reading the next CONVERT statement System action: The migration program continues
from the input file. processing with the next CONVERT statement, if one is
defined.
Problem determination: Check the previous messages
to determine the cause of the problem. System programmer response: Make sure that the
output data set is empty when the migration starts.
Verify that:
v The output data sets are empty VSAM data sets.
v The output data sets are correctly allocated. EQQIC06W THE OUTPUT DATA SET DOES NOT
v The job executing the migration program is CONTAIN ANY TYPE RECORDS
authorized to update the output data sets.
v The input data sets do not contain errors. | Explanation: The Logical part of the output AD data
v The input data sets are VSAM data sets at the level | set represented by ″type″ (which can be ″application″
specified. | or ″JCL variable table″) or ″all WS closed″ is empty:
v The migration program is authorized to read the | this can be because also the corresponding input is
input data sets.

© Copyright IBM Corp. 1991, 2003 125

| empty or because all the input records could not be
EQQIC09E APPLICATION INDEX RECORD FOR
| converted. AD HAS AN INVALID INPUT
System action: The migration program continues ARRIVAL IA FOR AN OCCURRENCE
processing by reading the next CONVERT statement IN STATUS ST
from the SYSIN file. The return code for the current
Explanation: A current plan application index record
CONVERT statement is set to 4.
CPLREC05, identified in the message text, contains an
| Problem determination: Problem determination: check invalid input arrival date in one of its occurrence data.
| if the warning message can be ignored (because also
System action: The migration program continues
| the input logical part is empty) or determine from the
processing by reading the next CONVERT statement
| previous message why the input records could not be
from the input file. No valid current plan is created.
| converted.
System programmer response: Do one of the
| System programmer response: None. If the input was
following:
| also empty, otherwise perform the action described for
v Update the occurrence with a valid I/A date.
| the messages issued by the migration program before
v If the occurrence status is complete, run two or more
| this one.
CP EXTENDS to delete it from the current plan,
before rerunning the conversion.
EQQIC07E APPLICATION AD WITH INPUT
ARRIVAL IA AND OPERNUM OP#
EQQIC10E THE FILE KEYWORD IS MISSING
THE FOLLOWING SPECIAL
RESOURCES CAUSE EXCEED OF THE Explanation: The current CONVERT statement does
OUTPUT RECORD SIZE: not contain the FILE keyword.
Explanation: During conversion of the current plan System action: The migration program continues
operation record identified in the message text, the processing by reading the next CONVERT statement
migrated output record would be too large to store from the input file.
without modification. At least one special resource
System programmer response: Add the FILE keyword
referenced by the operation cannot be included. The
to the current CONVERT statement and resubmit the
subsequent message EQQIC08I identifies the special
file migration batch job.
resources that cannot fit.
System action: The migration program is terminated.
EQQIC11E A PARAMETER IS REQUIRED FOR
No valid current plan is created.
THE FILE KEYWORD
Problem determination: As each special resource
Explanation: The FILE keyword in the current
entry is expanded by 8 bytes, while the maximum
CONVERT statement does not specify a value.
record size remains the same, it is possible to encounter
this problem. System action: The migration program continues
processing by reading the next CONVERT statement
System programmer response: Start up the previous
from the input file.
release of IBM Tivoli Workload Scheduler for z/OS and
delete any special resource entries from the operation System programmer response: Add a file name value
that are unnecessary. The entries you delete do not to the FILE keyword of the current CONVERT
have to be those identified in EQQIC08I. statement, and resubmit the file migration batch job.

EQQIC08I SR EQQIC12E THE FROMREL KEYWORD IS

MISSING
Explanation: This message is associated with
EQQIC07E. It lists those special resources that could Explanation: The current CONVERT statement does
not fit into the output current plan record. not contain the FROMREL keyword.
System action: The migration program is terminated. System action: The migration program continues
processing by reading the next CONVERT statement
System programmer response: See the description for
from the input file.
message EQQIC07E.
System programmer response: Add the FROMREL
keyword to the current CONVERT statement and
resubmit the file migration batch job.

126 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
EQQIC13E A PARAMETER IS REQUIRED FOR EQQIC17E INPUT LTP OCCURRENCE APPLIA IS
THE FROMREL KEYWORD TOO LARGE TO BE WRITTEN TO
THE OUTPUT FILE
Explanation: The FROMREL keyword in the current
CONVERT statement does not specify a value. Explanation: A long-term plan (LTP) occurrence in the
input LTP file defined to the migration program is too
System action: The migration program continues
large to be written to the output data set. The most
processing by reading the next CONVERT statement
likely reason for this message is that the maximum
from the input file.
record size is larger for the input LTP file than for the
System programmer response: Add a file name value output LTP file.
to the FROMREL keyword of the current CONVERT
System action: The current input LTP record cannot
statement and resubmit the file migration batch job.
be converted to the format of the output file. The
migration program continues processing by reading the
EQQIC14E THE TOREL KEYWORD IS MISSING next record on the input file, but no more records are
written to the output file. The return code for the
Explanation: The current CONVERT statement does current CONVERT command is 8 or higher.
not contain the TOREL keyword.
System programmer response: Determine if the
System action: The migration program continues maximum record size defined for the output LTP file is
processing by reading the next CONVERT statement too small. If it is, reallocate the output LTP file and
from the input file. reexecute the migration program.
System programmer response: Add the TOREL
keyword to the current CONVERT statement and EQQIC18E FROMREL AND TOREL
resubmit the file migration batch job. COMBINATION NOT SUPPORTED
FOR FILE FILE
EQQIC15E A PARAMETER IS REQUIRED FOR Explanation: The file FILE specified in the current
THE TOREL KEYWORD CONVERT statement is not supported by the release
Explanation: The TOREL keyword in the current defined for the FROMREL or TOREL keyword.
CONVERT statement does not specify a value. System action: The migration program continues
System action: The migration program continues processing with the next CONVERT statement, if one is
processing by reading the next CONVERT statement defined.
from the input file. System programmer response: Refer to Installation
System programmer response: Add a file name value Guide for information about the valid combinations.
to the TOREL keyword of the current CONVERT Correct the value in the FILE, FROMREL, or TOREL
statement and resubmit the file migration batch job. keyword of the current CONVERT statement and
resubmit the job.

EQQIC16W INPUT APPLICATION APPL IS TOO

LARGE TO BE WRITTEN TO THE EQQIC36E CURRENT PLAN RECORD OF TYPE
OUTPUT FILE RECID FOR APPLICATION AD WITH
INPUT ARRIVAL IA AND OPERATION
Explanation: An application description (AD) in the NUMBER OPNUM IS NOT VALID,
input AD file defined to the migration program is too TOO HIGH OPERATION NUMBER,
large to be written to the output data set. The most CANNOT BE CONVERTED
likely reason for this message is that the maximum
record size is larger for the input AD file than for the Explanation: The operation number in one of the
output AD file. records in the input file is higher than the range
supported by the IBM Tivoli Workload Scheduler for
System action: The current input AD record is z/OS release to which you are reoccurring to. RECID is
skipped. The migration program continues normal the current plan record type:
processing by reading the next record on the input file. 03 An operation record
The return code for the current CONVERT command is 09 A rerun record
4 or higher. 14 A joblog record.
System programmer response: Determine if the System action: The migration fails without producing
maximum record size defined for the output AD file is a migrated current plan file.
too small. If it is, reallocate the output AD file and
reexecute the migration program. User response: Use the scheduler dialog or the
program interface to update the current plan file being
migrated, making sure that all the operation numbers

Chapter 14. EQQICnn Messages 127

are in the range supported by the release to which you
EQQIC39E AD RECORD FOR APPLICATION AD
are reoccurring to.
WITH OPERATION NUMBER OPNUM
System programmer response: None. IS NOT VALID, TOO HIGH
OPERATION NUMBER, CANNOT BE
CONVERTED PREOP PREAD
EQQIC37E CURRENT PLAN RECORD OF TYPE
RECID FOR APPLICATION AD WITH Explanation: The operation number OPNUM is higher
INPUT ARRIVAL IA IS NOT VALID, than the maximum value supported by the release of
TOO HIGH OCCURRENCE NUMBER, IBM Tivoli Workload Scheduler for z/OS to which you
CANNOT BE CONVERTED are performing the fallback (values higher than 99 were
introduced in Version 2.2.0.). The PREOP and PREAD
Explanation: The occurrence number in one of the variables might be displayed unresolved in the normal
records in the input file is higher than the range case. Alternatively, if the error has been discovered
supported by the IBM Tivoli Workload Scheduler for checking the corresponding section of the input
z/OS release to which you are reoccurring to. RECID is operation, the variables might contain the operation
the current plan record type: number and the application ID of an external
03 An operation record predecessor .
09 A rerun record
14 A joblog record. System action: The fallback fails without producing
the output AD file.
System action: The migration fails without producing
a migrated current plan file. User response: Use the scheduler dialog or the
programming interface to update the AD file input to
User response: Perform daily planning to reduce the the fallback. Ensure that all the operation numbers are
number of occurrences in the current plan being in the range supported by the release to which the
migrated. Set the BATCHOPT parameter PREVRES to output refers.
NO at the replan. If the current plan still has too many
occurrences, do either of the following: System programmer response: None.
v Run IBM Tivoli Workload Scheduler for z/OS until
enough occurrences have been completed.
EQQIC40E INVALID BLKSIZE — THE OUTPUT JS
v Delete occurrences, using the scheduler dialog or the
FILE MUST BE ALLOCATED WITH
program interface.
THE SIZE INCREASED BY 4 BYTES
Repeat the plan.
Explanation: In OPC Version 2.3.0 the record size of
System programmer response: None. the JS files was increased by 4 bytes more than in
previous versions. Check the cluster definition of the
VSAM JS file and increase the minimum and maximum
EQQIC38W RECTYP RECORD FOR OCCURRENCE record size with the same length.
AD AI, OPERATION OPNUM IS TOO
LARGE TO BE WRITTEN TO THE System action: The conversion fails without
OUTPUT FILE producing a converted JS file.

Explanation: A record in the input JS file defined to User response: For conversion from OPC Version 2.2.0
the migration program is too large to be written to the to later versions:
output file. The most likely reason is that the maximum Define the cluster for the output JS file with
record size is larger for the input JS file than for the increased record size
output JS file. Submit the conversion job again

System action: The record that is too large is ignored.

The migration program continues to process normally. EQQIC41E CALENDAR CAL HAS ALL DAYS
The return code for the current CONVERT run is 4 or FREE. AT LEAST ONE WORKDAY IS
higher. REQUIRED
System programmer response: Determine whether the Explanation: Calendar CAL is rejected because it has
maximum record size defined for the JS file is too no work days. It has not been migrated.
small, reallocate the file, and rerun the migration job.
System action: Application descriptions referencing
Calendar CAL are migrated referencing an unexisting
calendar.
User response: Define a consistent Calendar with at
least a work day.

128 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
 EQQIC42E THE NAME OF THE OPC SUBSYSTEM
CONVERTING FROM IS MISSING,
KEYWORD SUBSYSTEM
Explanation: The name of the subsystem converting
from is required when converting history data.
System action: The migration program terminates.
User response: Add the FROMSUBSYSTEM keyword
to the CONVERT statement and resubmit the migration
job.

EQQIC43W THERE IS NO
FROMREL/FROMSUBSYSTEM
OPERATIONS HISTORY DATA
Explanation: The input file to the conversion program
contains no records of the specified release, FROMREL,
and subsystem, FROMSUBSYSTEM.
System action: The migration program terminates.
User response: Check the input file to the conversion
program EQQICTOP.

EQQIC44E OPER OF FILE DDNM FAILED

Explanation: A sequential I/O request failed.
OPER is the operation requested
DDNM is the ddname of a file to be allocated to the
migration program EQQICTOP
System action: The migration program terminates.
User response: Check the file allocations to the
migration program. This message can be preceded by
message EQQ0959 with more information about the
error.

| EQQIC45W INPUT JCL VARIABLE TABLE JVT IS

| TOO LARGE TO BE WRITTEN TO
| THE OUTPUT FILE
| Explanation: A JCL variable table in the input AD file
| defined to the migration program is too large to be
| written to the output data set. The most likely reason
| for 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 the next record on the input file.
| The return code for the current CONVERT command is
| 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.

Chapter 14. EQQICnn Messages 129

130 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 15. EQQJnnn Messages
System action: None.
EQQJ001I ETT ACTIVATION/DEACTIVATION
REQUEST WAS NOT CONFIRMED User response: Contact your IBM Tivoli Workload
Scheduler for z/OS security administrator.
Explanation: You chose not to confirm the original
request. So it was ignored by IBM Tivoli Workload
Scheduler for z/OS. EQQJ007E NOT AUTHORIZED TO UPDATE
ENTRY ETTENAME
System action: None.
Explanation: You have attempted to update the
User response: None.
event-triggered tracking (ett) entry ETTENAME, but
you do not have the necessary authorization.
EQQJ002W ETT ACTIVATION REQUEST
System action: The request is rejected.
IGNORED SINCE ETT ALREADY
ACTIVE User response: Contact your security administrator.
Explanation: The event-triggered tracking (ETT)
function was already active when you requested EQQJ010I YOUR CHANGES HAVE
activation of the function. SUCCESSFULLY UPDATED THE ETT
DATABASE
System action: None.
Explanation: Your modifications to the event-triggered
User response: None.
tracking (ETT) table have successfully updated the ETT
database.
EQQJ003W ETT DEACTIVATION REQUEST
System action: None.
IGNORED SINCE ETT NOT ACTIVE
User response: None.
Explanation: The event-triggered tracking (ETT)
function was not active when you requested
deactivation of the function. EQQJ011E YOUR CHANGES DID NOT UPDATE
THE ETT DATABASE DUE TO
System action: None.
ERRORS
User response: None.
Explanation: Your modifications to the event-triggered
tracking (ETT) table did not update the table data set
EQQJ004I ETT FUNCTION HAS BEEN due to some error in the IBM Tivoli Workload
SUCCESSFULLY ACTIVATED Scheduler for z/OS subsystem.
Explanation: The event-triggered tracking (ETT) System action: None.
activation request has been successfully processed.
User response: Exit from this panel and reenter it to
System action: None. determine which modifications updated the ETT
database. Reenter those modifications that did not take
User response: None.
effect. If the error persist, contact your system
programmer.
EQQJ005I ETT FUNCTION HAS BEEN
System programmer response: Review the IBM Tivoli
SUCCESSFULLY DEACTIVATED
Workload Scheduler for z/OS message log for I/O
Explanation: The event-triggered tracking (ETT) errors pertaining to the table data set. Correct all errors
deactivation request has been successfully processed. and restart IBM Tivoli Workload Scheduler for z/OS.

System action: None.

EQQJ012E YOUR CHANGES TO THE ETT
User response: None. CRITERIA CONTAIN SYNTAX
ERROR(S)
EQQJ006W ETT REQUEST IGNORED DUE TO Explanation: Your changes to the event-triggered
LACK OF PROPER AUTHORIZATION tracking (ETT) criteria contain a syntax error (or errors).
Explanation: You have attempted to use the System action: None.
event-triggered tracking (ETT) function, but you do not
have the necessary authorization. User response: Enter the correct data.

© Copyright IBM Corp. 1991, 2003 131

 User response: Enter the correct data.
EQQJ013E THE ETT CRITERIA IS BEING
UPDATED BY USER USER - TRY
LATER EQQJ023E JOB NAME REPLACEMENT INFO
MUST BE OCHCYES OR OCHCNO
Explanation: Another user is currently updating the
event-triggered tracking (ETT) criteria table. Only one Explanation: OCHCYES and OCHCNO are the
user can access the table at a time. national characters for ’Y’ (yes) and ’N’ (no).
System action: None. System action: The system waits for you to respond.
User response: Try again later. User response: Enter the correct data.

EQQJ014E VALID MATCHING TYPES ARE EQQJ024E JOB NAME REPLACEMENT INFO
OCHCEXA, OCHCPFX AND OCHCSFX MUST BE OCHCNO OR BLANK FOR
RESOURCE EVENT
Explanation: OCHCEXA, OCHCPFX and OCHCSFX
are the national language characters for ’E’ (exact), ’P’ Explanation: You have specified the event to be a
(prefix) and ’S’ (suffix). resource event. You cannot replace job name
information for resource events. IBM Tivoli Workload
System action: None.
Scheduler for z/OS automatically sets this information
User response: Enter the correct matching type. to N (no) for resource events.
OCHCNO is the national character for ’N’ (no).
EQQJ020E AVAILABILITY STATUS CHANGE
System action: None.
INFO MUST BE SPECIFIED FOR
RESOURCE EVENTS User response: None.
Explanation: You have defined a triggering event as a
resource event, but failed to indicate if event-triggered EQQJ025E A VALID NAME OF AN ASSOCIATED
tracking (ETT) triggering should occur only for an APPLICATION MUST BE SPECIFIED
availability status switch from N (no) to Y (yes) or if
ETT triggering should occur whenever the availability Explanation: You must specify the name of a valid
is set to Y. application to be added to the current plan when an
event-triggered tracking (ETT) event matching this
System action: The system waits for you to respond. criteria entry occurs.
User response: If you want the ETT triggered System action: The system waits for you to respond.
application to be added only when the resource is
switched from unavailable to available, specify Y in the User response: Enter correct data.
availability switch field. If you want the application to
be added every time that the resource is set to EQQJ026E VALID VALUES ARE: OCHCYES,
available, regardless of the old status, specify N in the OCHCNO, OCHPRED, OCHSUCC AND
availability switch field. BLANK
Explanation: You have entered a value for the
EQQJ021E ETT EVENT TYPE MUST BE OCHCJOB dependency resolution attribute that is not recognized
OR OCHCRES by the Event-Triggered Tracking dialog. You must
Explanation: OCHCJOB and OCHCRES are the change the value to one of the supported values
national language characters for ’J’ (job) and ’R’ defined by this message.
(resource). System action: The system waits for you to respond.
System action: The system waits for you to respond. User response: Change the dependency resolution
User response: Enter the correct data. value.

EQQJ022E JOB NAME REPLACEMENT INFO EQQJ027E AVAILABILITY STATUS CHANGE

MUST BE SPECIFIED FOR JOB FIELD IS NOT OCHCNO OR BLANK
EVENTS Explanation: You have defined a triggering event as a
Explanation: You have specified the event to be a job reader event, but have specified a character other than
event, but failed to indicate whether the job name in OCHCNO or blank in the availablility switch field. The
the first operation of the added application should be availability status switch is relevant only when the
replaced or not. triggering event is a resource.

System action: The system waits for you to respond. System action: The system waits for you to respond.

132 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
User response: Change the availability switch
EQQJ502E CONTRADICTORY USE OF
indicator for the trigger to OCHCNO or leave the field
STANDARD TABLES AT LINE LINE OF
blank.
SCTN
Explanation: A SEARCH directive of the product
EQQJ028E EACH ETT CRITERIA ROW MUST
contains either both GLOBAL and NOGLOBAL, or
HAVE A UNIQUE EVENT NAME
both APPL and NOAPPL.
WITHIN TYPE
System action: If the error occurs during submit, the
Explanation: You have specified duplicate event
current operation status is set to ended-in-error with
names in the event-triggered tracking (ETT) table.
error code OJCV. Otherwise, the status is not changed.
System action: The system waits for you to respond.
User response: Correct the tailoring directive.
User response: Remove the duplicate entry or make
its name unique.
EQQJ503E ERROR ATTEMPTING TO READ JCL
MEMBER MBR
EQQJ029E AVAILABILITY STATUS CHANGE
Explanation: The member specified in a FETCH
FIELD IS NOT OCHCYES OR OCHCNO
directive of the product could not be found. The
Explanation: You have defined a triggering event as a member name is incorrect or the member cannot be
resource event, but have specified a character other accessed.
than OCHCYES or OCHCNO in the availablility switch
System action: If the error occurs during submit, the
field. The availability status switch must be set when
current operation status is set to ended-in-error with
the triggering event is a resource.
error code OJCV. Otherwise, the status is not changed.
System action: The system waits for you to respond.
User response: Correct the tailoring directive or
User response: If you want the event-triggered ensure that the member is available.
tracking (ETT) application to be added only when the
resource is switched from unavailable to available,
EQQJ504E KEYWORD STRING TOO LONG IN
specify Y in the availability switch field. If you want
OPC DIRECTIVE BEGINNING AT
the application to be added every time the resource is
LINE LINE OF SCTN
set to available, regardless of the old status, specify N
in the availability switch field. Explanation: The third and final string in a directive
of the product contains more than 1024 characters after
substitution, including continuation lines.
EQQJ500E INVALID STRING IN DIRECTIVE AT
LINE LINE OF SCTN System action: If the error occurs during submit, the
current operation status is set to ended-in-error with
Explanation: The predicate for any keyword other
error code OJCV. Otherwise, the status is not changed.
than COMP must:
v Consist of alphanumeric characters User response: Correct the tailoring directive.
v Begin with an alphabetic character.
System action: If the error occurs during submit, the EQQJ505E INVALID KEYWORD COMBINATION
current operation status is set to ended-in-error with IN OPC DIRECTIVE BEGINNING AT
error code OJCV. Otherwise, the status is not changed. LINE LINE OF SCTN
User response: Correct the tailoring directive. Explanation: A directive of the product has at one or
more of these problems:
v Keywords are incompatible with each other.
EQQJ501E DUPLICATE TABLE NAME TBL AT
v Keywords are incompatible with the type of
LINE LINE OF SCTN
directive.
Explanation: The same table name was encountered v Mandatory keywords are missing.
twice in a SEARCH directive of the product.
System action: If the error occurs during submit, the
System action: If the error occurs during submit, the current operation status is set to ended-in-error with
current operation status is set to ended-in-error with error code OJCV. Otherwise, the status is not changed.
error code OJCV. Otherwise, the status is not changed.
User response: Correct the tailoring directive.
User response: Correct the tailoring directive.

Chapter 15. EQQJnnn Messages 133

 | System action: If you are scheduling a JCL
EQQJ506E RECURSIVE SUBSTITUTION AT LINE
| submission, the current operation status is set to
LINE OF SCTN
| ended-in-error with error code OJCV. If you are
Explanation: The value of a variable depends on the | scheduling a not centralized job submission, the
values of other variables, which in turn depend on its | Symphony creation or the addition of the operation
value. No value can be determined for this variable. | fails.
System action: If the error occurs during submit, the | User response: Check the directives or the VARSUB
current operation status is set to ended-in-error with | statement to ensure that the table names are correct.
error code OJCV. Otherwise, the status is not changed. | Use the Variable Definition dialog to ensure that the
| tables exist.
User response: Examine the table definitions of the
variables in the line and eliminate the closed translation
loop. EQQJ510E UNSET VARIABLE VAR AT LINE LINE
OF SCTN
EQQJ507E CHANGE OF STRUCTURE CAUSED Explanation: A non-dependent variable with no value
BY SUBSTITUTION IN DIRECTIVE was encountered in the submit phase or in a JCLPREPA
BEGINNING AT LINE LINE OF SCTN simulation request.
Explanation: Variable substitution has caused one or In the submit phase, or at simulation, these types of
more of these changes: variables can be encountered:
v A directive of the product has been created. v Variables that have already been provided with
v The type of a directive of the product has changed. values
v The keywords of a directive of the product have v Variables that are dependent on other variables
changed. v Variables that do not require a setting (which are
v A directive of the product has changed to another eliminated from the job stream).
line type.
System action: If the error occurs during submit, the
System action: If the error occurs during submit, the current operation status is set to ended-in-error with
current operation status is set to ended-in-error with error code OJCV. Otherwise, the status is not changed.
error code OJCV. Otherwise, the status is not changed.
User response: Either change the variable definition or
User response: Correct the original tailoring directive give the variable a value.
or substitution values.
EQQJ511E JOB JOBNAME IN APPLICATION APPL
EQQJ508E RECURSIVE SUBSTITUTION OF CONTAINS AN OPC CONTROL
LENGTH LINES FROM FROM OF SCTN STATEMENT THAT IS NOT
RECOGNIZED
Explanation: A closed loop of dependency definitions
or variable translations exists. Explanation: The product was unable to submit the
identified job because it contains an incorrectly coded
System action: If the error occurs during submit, the
//*%OPC statement and JCL variable scanning is
current operation status is set to ended-in-error with
active for this job.
error code OJCV. Otherwise, the status is not changed.
System action: The current operation status is set to
User response: Examine the table definitions of the
ended-in-error with error code OJCV.
variables in this section, and eliminate the loop.
User response: Locate the JCL for this job and correct
If this section contains promptable variables, the values
the //*%OPC statement. Use the scheduler dialog to
supplied for these variables may have caused the error.
rerun the operation.

| EQQJ509E TABLE TBL NOT FOUND

EQQJ512E RECURSIVE DEPENDENCY VARIABLE
| Explanation: If TABLE GLOBAL NOT FOUND VAR AT LINE LINE OF SCTN
| message text appears: possible reasons are: Explanation: A closed loop of dependency definitions
| —The user did not explicitly provide tables to be exists.
| searched. System action: If the error occurs during submit, the
| — The user specified some tables to be searched but current operation status is set to ended-in-error with
| none of them are defined in the AD file. error code OJCV. Otherwise, the status is not changed.

| The scheduler tried to search the variable in the global User response: Examine the table definitions of this
| table, but the default global variable table is not variable and the chain on which it is dependent, and
| defined in the AD file. eliminate the closed dependency loop. The loop does

134 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
not necessarily include the variable listed in the
EQQJ516E UNRECOVERABLE ABEND IN USER
message.
EXIT USRX THAT WAS DEFINED FOR
VARIABLE VAR IN TABLE TAB,
EQQJ513E SETUP VARIABLE CHLD DEPENDENT APPLICATION IS ADID, WITH
ON SUBMIT VARIABLE PRNT AT OCCURRENCE INPUT ARRIVAL IAD,
LINE LINE OF SCTN IAT, OPERATION NUMBER IS OPNO

Explanation: A prompt variable cannot be dependent Explanation: The user module caused an abend from
on a submit variable. which IBM Tivoli Workload Scheduler for z/OS could
not recover.
System action: If the error occurs during submit, the
current operation status is set to ended-in-error with System action: If the error occurs during submit, the
error code OJCV. Otherwise, the status is not changed. 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. User response: Correct the user module and restart
IBM Tivoli Workload Scheduler for z/OS.

EQQJ514E RETURN CODE RC FROM USER EXIT

USRX. THE EXIT WAS DEFINED FOR EQQJ517E INVALID VALUE VAL SUPPLIED BY
VARIABLE VAR IN TABLE TAB FOR USER EXIT USRX FOR VARIABLE VAR
APPLICATION ADID, WITH IN TABLE TAB FOR APPLICATION
OCCURRENCE INPUT ARRIVAL IAD, ADID, OCCURRENCE IA IS IAD, IAT,
IAT. THE OPERATION NUMBER IS OPERATION NUMBER IS OPNO
OPNO
Explanation: The value that you supplied for the
Explanation: IBM Tivoli Workload Scheduler for z/OS variable violates the verification rules in the variable
received an unexpected return code from an exit. definition.
System action: If the error occurs during submit, the System action: If the error occurs during submit, the
current operation status is set to ended-in-error with current operation status is set to ended-in-error with
error code OJCV. Otherwise, the status is not changed. error code OJCV. Otherwise, the status is not changed.
User response: Correct the user module, supply a User response: Correct the user module or verification
valid return code, and restart IBM Tivoli Workload criteria. To use the corrected user module, you must
Scheduler for z/OS. restart IBM Tivoli Workload Scheduler for z/OS.

EQQJ515E RECOVERABLE ABEND IN USER EXIT EQQJ518E THE SUBSTITUTION EXIT USRX WAS
USRX THAT WAS DEFINED FOR REFERENCED BY VARIABLE VAR. THE
VARIABLE VAR IN TABLE TAB FOR EXIT WILL NOT BE CALLED AS IT
APPLICATION ADID, INPUT ARRIVAL HAS BEEN MARKED NOT
IS IAD, IAT, OPERATION NUMBER IS EXECUTABLE BY OPC. APPLICATION
OPNO IS ADID, INPUT ARRIVAL IS: IAD, IAT,
AND OPERATION NUMBER IS OPNO
Explanation: The user module caused an abend from
which IBM Tivoli Workload Scheduler for z/OS Explanation: IBM Tivoli Workload Scheduler for z/OS
recovered. has previously discovered an abend in this exit and
marked it as not executable. This exit is not called
System action: If the error occurs during submit, the again.
current operation status is set to ended-in-error with
error code OJCV. Otherwise, the status is not changed. System action: The current operation status is set to
ended-in-error, with error code OJCV.
User response: Correct the user module and restart
IBM Tivoli Workload Scheduler for z/OS. System programmer response: Correct the exit and
restart IBM Tivoli Workload Scheduler for z/OS to
reuse the exit.

Chapter 15. EQQJnnn Messages 135

EQQJ519E OPC DID NOT GET STORAGE EQQJ524E Y/N MUST BE ENTERED IN NUMERIC
ENOUGH TO BUILD JCL RECORD FIELD FOR LIST/RANGE
APPLICATION IS: ADID, OPERATION
Explanation: Because you asked for RANGE
NO IS: OPNO, INPUT ARRIVAL DATE
verification, you must enter Y (yes) or N (no) in the
IS: IAD AND INPUT ARRIVAL TIME
numeric field.
IS: IAT
System action: The system waits for you to respond.
Explanation: IBM Tivoli Workload Scheduler for z/OS
tried to allocate storage for a final build of the JCL User response: Enter the correct value.
record, but the request for storage failed.
System action: The operation status depends on the EQQJ525E THE JCL VARIABLE TABLE HAS BEEN
SUBFAILACTION keyword in the JTOPTS initialization DELETED
statement. The operation can:
v Keep status R or extended status RE Explanation: The current variable table has been
v Get status C (complete) deleted from IBM Tivoli Workload Scheduler for z/OS’s
v Get status E (ended-in-error) with error code OSUF. database.

System programmer response: Make sure that IBM System action: The table is deleted.
Tivoli Workload Scheduler for z/OS is running in a User response: Re-define a variable table if needed, or
large enough region and restart IBM Tivoli Workload check the current definition and specify it in any
Scheduler for z/OS. existing concatenation.

EQQJ520E VALUE LENGTH IS REQUIRED WHEN EQQJ526E CHARACTER CHR IN POSITION PDS
COMPARISON OPERATOR SPECIFIED IS INVALID
Explanation: Because you entered a comparison Explanation: The value entered as a default value
operator, you must enter a value length. does not match the validation pattern defined for the
System action: The system waits for you to respond. variable.

User response: Enter the correct value. System action: The system waits for you to respond.
User response: Enter the correct value.
EQQJ521E COMPARISON OPERATOR
REQUIRED WHEN LENGTH EQQJ527E THE VALUES/RANGES MAY NOT
OPERATOR SPECIFIED CONTAIN IMBEDDED BLANKS
Explanation: Because you entered a value length, you Explanation: You cannot use blanks in a
must enter a comparison operator. LIST/RANGE verification value list.
System action: The system waits for you to respond. System action: The system waits for you to respond.
User response: Enter the correct value. User response: Enter the correct value.

EQQJ522E THE DEFAULT VALUE IS INVALID EQQJ528E THE NUMBER OF VALUES MUST BE
FOR THE VERIFICATION TYPE EVEN FOR RANGE VERIFICATION
Explanation: The default value that you entered does Explanation: You specified an odd number of values
not match the verification rules for the variable. for a range verification.
System action: The system waits for you to respond. System action: The system waits for you to respond.
User response: Enter the correct value. User response: Enter the correct value.

EQQJ523E A VALIDATION PATTERN IS EQQJ529E THE VALUES DEFINING A RANGE

REQUIRED FOR PICT VERIFICATION ARE IN DESCENDING SEQUENCE
Explanation: Because you asked for PICT verification, Explanation: You entered a range that consists of a
you must enter a validation pattern. larger number followed by a smaller number. You must
System action: The system waits for you to respond. specify the smaller number (beginning of the range)
before the larger number (end of the range).
User response: Enter the correct value.
System action: The system waits for you to respond.
User response: Enter the correct value.

136 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
EQQJ530E SCANNING LENGTH EXCEEDED EQQJ533E OPC DIRECTIVE DIR OUT OF
LINE LINE OF SCTN POSITION LINE LINE OF SCTN
Explanation: Substitution of a JCL command has Explanation: There are two possibilities:
caused the command length to exceed 71 characters or v No previous //*%OPC BEGIN directive corresponds
substitution of an in-stream data line has caused the to the current //*%OPC END directive.
in-stream data line to exceed 80 characters. v A //*%OPC BEGIN directive was found previously,
but the current directive is not the corresponding
System action: If the error occurs during submit, the
//*%OPC END directive.
current operation status is set to ended-in-error with
error code OJCV. Otherwise, the status is not changed. System action: If the error occurs during submit, the
current operation status is set to ended-in-error with
System programmer response: If the substitution is
error code OJCV. Otherwise, the status is not changed.
correct, split the command line over two or more lines.
If the problem occurs in an in-stream data line, verify User response: Correct the JCL.
that the ISPF profile option for sequence numbering is
turned off in the JCL job library.
EQQJ534E INVALID VARIABLE VAR LINE LINE
OF SCTN
EQQJ531E OPC WAS UNABLE TO LOAD
Explanation: The name of a variable can contain one
VARIABLE SUBSTITUTION EXIT
to eight alphanumeric characters, where the first
USRX TABLE NAME IS TAB,
character is alphabetic. This message can also be
VARIABLE NAME IS VAR,
reported if a tabular variable, that is, a ?-variable, does
APPLICATION IS ADID,
not include the substitution column position and a
OCCURRENCE IA = IAD, IAT,
default position is not defined in the JCL variable table.
OPERATION NUMBER IS OPNO
System action: If the error occurs during submit, the
Explanation: A variable substitution exit that was
current operation status is set to ended-in-error with
referred to could not be loaded by IBM Tivoli Workload
error code OJCV. Otherwise, the status is not changed.
Scheduler for z/OS.
User response: Correct the JCL or the JCL variable
System action: If you are scheduling a JCL job or a
table as appropriate.
centralized script, the current operation status is set to
ended-in-error with error code OJCV. If you are
scheduling a not centralized job, depending on where EQQJ535E UNDEFINED VARIABLE VAR LINE
you are, Batch or controller: LINE OF SCTN
v The creation of symphony continues but the job is Explanation: A variable that is not predefined by IBM
added in fail status. Tivoli Workload Scheduler for z/OS must appear in a
v The addition of the operation fails. table that is created by the JCL variable dialog and is
included in the current table concatenation.
System programmer response: Check the current load
library in the started task JCL and make sure that the For more information, refer to the description of the
exit is link-edited to the correct library. SEARCH and TABLE directives in Managing the
Workload.
EQQJ532E INVALID OPC EXPRESSION EXPR System action: If the error occurs during submit, the
BEGINNING AT LINE LINE OF SCTN current operation status is set to ended-in-error with
error code OJCV. Otherwise, the status is not changed.
Explanation: The expression must consist of
keyword= where keyword is one of: NAME, ACTION, User response: Correct the JCL.
PHASE, MEMBER, COMP, EXIT.
This message can also be issued if all mandatory EQQJ536E POSITIONAL OVERLAP VARIABLE
keywords have not been specified. VAR LINE LINE OF SCTN
System action: If the error occurs during job submit, Explanation: The tabular variable (?-variable) cannot
the current operation status is set to ended-in-error be assigned the positions specified in the prefix or by
with error code OJCV. Otherwise, the status is not default because part or all of the receiving string is
changed. already occupied.
User response: Correct the JCL. For more information, refer to Managing 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.

Chapter 15. EQQJnnn Messages 137

User response: Correct the JCL.
EQQJ540E MORE THAN 16 TABLES DECLARED
IN SEARCH DIRECTIVE AT LINE LINE
EQQJ537E CALENDAR CAL CANNOT BE OF SCTN
FOUND. SUBSTITUTION FAILED
Explanation: The number of tables requested by a
Explanation: During variable substitution of a job, a SEARCH directive is greater than 16.
function that requires access to a calendar, for example,
Unless GLOBAL and APPL are explicitly excluded
a SETVAR directive asking for an expression involving
(NOGLOBAL and NOAPPL), they contribute to the
arithmetics on calendar days, could not be processed.
total even if they are not specified in the SEARCH
The calendar referenced by the occurrence no longer
directive.
exists.
System action: If the error occurs during submit, the
System action: If the error occurs during job submit,
current operation status is set to ended-in-error with
the current operation status is set to ended-in-error
error code OJCV. Otherwise, the status is not changed.
with error code OJCV. Otherwise, the status is not
changed. User response: Check if all tables are necessary and
correct the JCL.
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 EQQJ541E ATTEMPT TO CONCATENATE MORE
the needed date manually under JCL Edit. THAN 16 TABLES BY TABLE
DIRECTIVE AT LINE LINE OF SCTN
EQQJ538E BEGIN ACTION NOT CLOSED LINE Explanation: A TABLE directive has been encountered
LINE OF SCTN when 16 tables are already active.
Explanation: At the end of the JCL stream, the last System action: If the error occurs during submit, the
//*%OPC BEGIN command has not been closed by a current operation status is set to ended-in-error with
//*%OPC END command. error code OJCV. Otherwise, the status is not changed.
System action: If the error occurs during submit, the User response: Check if all tables are necessary and
current operation status is set to ended-in-error with correct the JCL.
error code OJCV. Otherwise, the status is not changed.
User response: Correct the JCL. EQQJ542E COMP EXPRESSION BEGINNING AT
LINE LINE OF SCTN EXCEEDS 1024
BYTES
EQQJ539E VARIABLE SUBSTITUTION WAS
INTERRUPTED BY SUBSTITUTION Explanation: The total length of all fields of a COMP
EXIT USRX. APPLICATION IS ADID, expression, including COMP= and all continuations of the
INPUT ARRIVAL DATE AND TIME IS right side of the expression on subsequent JCL lines,
IAD, IAT OPERATION NUMBER IS cannot exceed 1024 characters after substitution.
OPNO
System action: If the error occurs during submit, the
Explanation: A substitution exit set a return code of 8, current operation status is set to ended-in-error with
which interrupted the JCL variable substitution. No error code OJCV. Otherwise, the status is not changed.
further substitution is done for this operation.
User response: Correct the JCL.
System action: If you are scheduling a JCL
submission, the current operation status is set to
EQQJ543E COMP EXPRESSION BEGINNING AT
ended-in-error with error code OJCV. If you are
LINE LINE OF SCTN IS NOT WELL
scheduling a not centralized job submission, the
FORMED: EXPR
symphony creation or the addition of the operation
fails. Explanation: The syntax of the COMP keyword is not
correct.
System programmer response: Check the current exits
and determine the reason for return code 8 being System action: The current operation status is set to
passed back. If the exit is changed and you want to ended-in-error with error code OJCV.
reuse it, restart IBM Tivoli Workload Scheduler for
z/OS. 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 directive of the product
using the current COMP keyword.

138 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
 of the COMP keyword, refer to Planning and Scheduling
EQQJ544E COMP EXPRESSION CONTAINS
the Workload
UNBALANCED PARENTHESIS
User response: Correct the JCL for the operation and
Explanation: Parentheses are not used correctly in the
make sure that the COMP keyword is correct.
COMP keyword.
System action: The current operation status is set to
EQQJ548W VARIABLE VAR IN TABLE TABLE
ended-in-error with error code OJCV.
COULD NOT BE UPDATED. REASON
Problem determination: This message is issued IS RSN
together with message EQQJ543E. For an explanation
Explanation: A SAVEVAR directive with
of the COMP keyword, refer to Planning and Scheduling
ERRORACT=CONT was found during variable
the Workload
substitution. IBM Tivoli Workload Scheduler for z/OS
User response: Correct the JCL for the operation and tried to update the default value as requested in the
make sure that the COMP keyword contains the correct SETVAR directive, but it was not possible for one of the
number of parentheses. following reasons:
HELDLOCK
Could not get ENQ lock necessary to access
EQQJ545E COMP EXPRESSION MUST CONTAIN
the variable.
AT LEAST ONE OPERATOR
NOTFOUND
Explanation: The COMP keyword does not contain Variable/table did not exist in the table data
any operators. set
BADVNAME
System action: The current operation status is set to Variable/table is either a IBM Tivoli Workload
ended-in-error with error code OJCV. Scheduler for z/OS-supplied variable or a
Problem determination: This message is issued temporary variable. These variables are never
together with message EQQJ543E. For an explanation saved.
of the COMP keyword, refer to Planning and Scheduling System action: Processing continues. The job is
the Workload submitted as normal, but the next time that the default
User response: Correct the JCL for the operation and value is requested as input to variable substitution, it
make sure that the COMP keyword contains at least does not show the latest updated value.
one operator. User response: The value can be corrected by
allowing a person with update access to the variable
EQQJ546E COMP EXPRESSION CONTAINS TOO table to update the default value manually in the JCL
FEW EQUATION SEPARATING variable dialog.
COMMAS
Explanation: At least one comma is missing in the EQQJ549E A SETUP PHASE DIRECTIVE AT LINE
COMP keyword. LINE OF SCTN REFERS TO A
VARIABLE DEFINED FOR USE AT
System action: The current operation status is set to SUBMIT
ended-in-error with error code OJCV.
Explanation: The current job contains a JCL processing
Problem determination: This message is issued directive specifying PHASE=SETUP. IBM Tivoli
together with message EQQJ543E. For an explanation Workload Scheduler for z/OS could not determine
of the COMP keyword, refer to Planning and Scheduling what action is requested by the statement because it
the Workload refers to a JCL variable whose value is not determined
User response: Correct the JCL for the operation and until the submit phase.
make sure that the COMP keyword is correct. System action: The system waits for you to respond.
User response: Enter the JCL Edit dialog and correct
EQQJ547E COMP EXPRESSION CONTAINS TOO the incorrect statement. Reenter the Ready List dialog
FEW OPERATORS and retry JCL setup for this operation.
Explanation: At least one operator is missing in the
COMP keyword. EQQJ550E CHARACTER CHR IN POSITION POS
System action: The current operation status is set to IS INVALID
ended-in-error with error code OJCV. Explanation: The value entered as a default value
Problem determination: This message is issued does not match the validation pattern defined for the
together with message EQQJ543E. For an explanation variable.
System action: The system waits for you to respond.

Chapter 15. EQQJnnn Messages 139

User response: Enter the correct value.
EQQJ562E OPC WAS UNABLE TO ALLOCATE
STORAGE TO PROCESS MEMBER
EQQJ551E THE VALUE OF THE INDEPENDENT MEMBER OF DDNAME
VARIABLE ALREADY EXISTS
Explanation: IBM Tivoli Workload Scheduler for z/OS
Explanation: The same value of the independent was attempting to build a record in the VSAM data set
variable is given in two different rows of the to be inserted in the JCL repository data set, but it was
dependency table. unable to do so because of insufficient virtual storage.

System action: The system waits for you to respond. System action: The operation remains in Ready status.
IBM Tivoli Workload Scheduler for z/OS is unable to
User response: Correct or delete the values that you submit the job to JES.
entered.
User response: Submit the job manually.

EQQJ553E VALIDATION ERROR AT LINE LINE in System programmer response: Stop IBM Tivoli
JOB SCTN VALUE IS REQUIRED FOR Workload Scheduler for z/OS and restart it in a larger
THE VARIABLE VAR BUT IS DEFINED region.
AS BLANK
Explanation: JCL tailoring is setting a temporary EQQJ563E OPC WAS UNABLE TO FIND
variable by a replacement with a source string. This MEMBER MEMBER IN DDNAME
string is blank, but a value is required. LIBRARY FILE
System action: If the error occurs during submit, the Explanation: IBM Tivoli Workload Scheduler for z/OS
current operation status is set to ended-in-error with was attempting to submit a job to JES for a ready
error code OJCLV. Otherwise, the status is not changed. operation on a computer workstation. However, no JCL
for this operation is saved in the JCL repository data
User response: Check the SETVAR directive from JCL set and the job is not present as a member in the
to find the cause of the error and use JCL Edit for library defined by the EQQJBLIB DD statement.
manual insertion of the missing value.
System action: The operation remains in Ready status.
IBM Tivoli Workload Scheduler for z/OS assumes that
EQQJ560E MORE THAN 16 VARIABLES some other function submits the job to JES.
SPECIFIED IN SAVEVAR DIRECTIVE
AT LINE LINE OF SCTN Problem determination: Check that the EQQJBLIB DD
statement is correctly defined and that all required
Explanation: The number of variables requested to be members are defined.
saved in a SAVEVAR directive is greater than 16.
User response: If necessary, submit the job manually.
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. EQQJ564W MEMBER MEMBER IN DDNAME
LIBRARY FILE IS EMPTY
User response: Split the SAVEVAR directive into
multiple directives. Explanation: The JCL library member exists in the
library defined by the EQQJBLIB DD statement, but
there are no records in the member.
EQQJ561E TEMPORARY VARIABLE NAME VAR
ALREADY USED FOR SUBSTITUTION System action: The operation remains in Ready status.
IN JOB JOBNAME IBM Tivoli Workload Scheduler for z/OS assumes that
some other function submits the job to JES.
Explanation: A SETVAR directive requests creation of
a temporary variable. There has been an earlier Problem determination: Check that the EQQJBLIB DD
reference in the job to the same name and it has been statement is correctly defined and that all required
found in the IBM Tivoli Workload Scheduler for z/OS members are defined.
Variable Table.
User response: If necessary, submit the job manually.
System action: If the error occurs during submit, the
current operation status is set to ended-in-error with
EQQJ565E INVALID VARIABLE OR TABLE
error code OJCV. Otherwise, the status is not changed.
NAME AT LINE LINE OF SCTN
User response: Use another name for your temporary
Explanation: During variable substitution of a job, a
variable.
SAVEVAR directive specified the name of a variable, or
a variable table, with incorrect syntax.
System action: If the error occurs during job submit,

140 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
the current operation status is set to ended-in-error Scheduler for z/OS-supplied variable or a
with error code OJCV. Otherwise, the status is not temporary variable. These variables are never
changed. saved.
User response: Correct the syntax of the variable or User response: The value can be corrected by
variable table. allowing a person with update access to the variable
table to correct the default value manually in the JCL
variable table dialog.
EQQJ566E INVALID REFERENCE TO GLOBAL
TABLE AT LINE LINE OF SCTN
EQQJ569E INVALID REFERENCE TO DYNAMIC
Explanation: During variable substitution of a job, a
FORMAT VARIABLE AT LINE LINE OF
SAVEVAR directive was found that specified only the
SCTN
variable name. The implied table is then the Variable
Substitution global table. However, no GTABLE Explanation: A reference to a dynamic-format variable
keyword has been specified in OPCOPTS. 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 System action: If the error occurs during job submit,
with error code OJCV. Otherwise, the status is not the current operation status is set to ended-in-error
changed. 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 User response: Insert a SETFORM directive in the JCL
variable table in the SAVEVAR statement. earlier than the point where it is referenced.

EQQJ567E THE JCL FOR APPLICATION AD EQQJ570E INVALID DYNAMIC FORMAT

COULD NOT BE INSERTED IN THE JS VARIABLE NAME AT LINE LINE OF
REPOSITORY PHYSICAL RECORD SCTN
SIZE IS TOO SMALL
Explanation: During variable substitution of a job, a
Explanation: The physical record length specified for SETFORM directive was found where the name of the
the JS repository is too small. dynamic-format variable is not a IBM Tivoli Workload
Scheduler for z/OS-supplied dynamic format variable.
System action: The current operation remains in
Ready status. System action: If the error occurs during job submit,
the current operation status is set to ended-in-error
Problem determination: Check the VSAM definitions
with error code OJCV. Otherwise, the status is not
for EQQJS1DS and EQQJS2DS.
changed.
User response: Contact your system programmer.
User response: Correct the variable name in the
System programmer response: Increase the physical SETFORM directive.
record length for EQQJS1DS and EQQJS2DS.
EQQJ571E INVALID FORMAT EXPRESSION IN
EQQJ568E VARIABLE VAR IN TABLE TABLE SETFORM DIRECTIVE AT LINE LINE
COULD NOT BE UPDATED. REASON: OF SCTN
RSN
Explanation: During variable substitution of a job, a
Explanation: A SAVEVAR directive with SETFORM directive was found where the format did
ERRORACT=NOCONT was found during variable not have the proper syntax. Possible errors are:
substitution. IBM Tivoli Workload Scheduler for z/OS v The first characters after the left parenthesis and the
tried to update the default value as requested in the last characters before the right parenthesis of the
SETVAR directive, but it was not possible for one of the expression are not meaningful keywords for the
following reasons: specified dynamic format variable. (For example,
HELDLOCK CCYY, YY, MM, DD, or DDD for a date-related
Could not get ENQ lock necessary to access dynamic variable.)
the variable.
v The whole format expression was searched and no
NOTFOUND
meaningful keywords for the specified
Variable/table did not exist in the variable
dynamic-format variable were found. (For example,
table data set
CCYY, YY, MM, DD, or DDD was not found for a
BADVNAME
date-related dynamic variable.)
Variable/table is either a IBM Tivoli Workload

Chapter 15. EQQJnnn Messages 141

 v IBM Tivoli Workload Scheduler for z/OS variable
EQQJ576E THE EQQUX002 EXIT COULD NOT
substitution characters (&, %, = or ?) are found in the
OPEN AN INPUT DATA SET TO READ
expression.
JOB MEMBER EXIT MESSAGE IS:
System action: If the error occurs during job submit, UX002MSG
the current operation status is set to ended-in-error
Explanation: The joblib I/O exit was called and gave
with error code OJCV. Otherwise, the status is not
a return code indicating that it could not open one of
changed.
its input data sets.
User response: Correct the format expression in the
System action: The job is not submitted by IBM Tivoli
SETFORM directive.
Workload Scheduler for z/OS as intended. The
operation remains in Ready status.
EQQJ572E COMP EXPRESSION CONTAINS
Problem determination: Check that all DD statements
MULTIPLE VALUES FOR
needed by the EQQUX002 exit have been correctly
’EXPRESSION2’
defined and that the IBM Tivoli Workload Scheduler for
Explanation: A COMP expression with operators GT, z/OS started task has (as a minimum) read access to all
GE, LT, or LE only allows one value for expression2. referenced data sets.

System action: If the error occurs during job submit, User response: If necessary, submit the job manually.
the current operation status is set to ended-in-error
System programmer response: Correct all errors and
with error code OJCV. Otherwise, the status is not
restart IBM Tivoli Workload Scheduler for z/OS.
changed.
User response: Correct the JCL for the operation and
EQQJ577E OPC COULD NOT ALLOCATE
make sure that the COMP keyword is correct.
STORAGE TO PROCESS JOB MEMBER
FOR EQQUX002 EXIT
EQQJ573E COMP EXPRESSION CONTAINS
Explanation: IBM Tivoli Workload Scheduler for z/OS
GENERIC SEARCH CHARACTERS
was building a reord in the VSAM data set to be
Explanation: A COMP expression with operators GT, inserted in the JCL repository data set, but it was
GE, LT, or LE does not allow the generic characters * or unable to do so because of insufficient virtual storage.
% in expression2.
System action: The operation remains in Ready status.
System action: If the error occurs during job submit, IBM Tivoli Workload Scheduler for z/OS is unable to
the current operation status is set to ended-in-error submit the job to JES.
with error code OJCV. Otherwise, the status is not
User response: Submit the job manually.
changed.
System programmer response: Stop IBM Tivoli
User response: Correct the JCL for the operation and
Workload Scheduler for z/OS and restart it in a larger
make sure that the COMP keyword is correct.
region.

EQQJ575E ARITHMETIC EXPRESSION

EQQJ578E THE EQQUX002 EXIT COULD NOT
BEGINNING AT LINE LINE OF SCTN
FIND JOB MEMBER IN ANY INPUT
EXCEEDS LIMITS
DATA SET
| Explanation: During variable substitution of a job, the
Explanation: IBM Tivoli Workload Scheduler for z/OS
| calculation of a SETVAR arithmetic expression resulted
was attempting to submit a job to JES for a ready
| in a date value that exceeds IBM Tivoli Workload
operation on a computer workstation. However, no JCL
| Scheduler for z/OS limits. IBM Tivoli Workload
for this operation is saved in the JCL repository data
| Scheduler for z/OS supports dates from 1 January 1984
set, and the joblib I/O exit could not find the job in
| to 31 December 2071. If the expression includes WD,
any input data set.
| the calculated date must fall within the range of three
| years earlier and six years later than the current year. System action: The operation remains in Ready status.
IBM Tivoli Workload Scheduler for z/OS assumes that
System action: If the error occurs during job submit,
some other function submits the job to JES.
the current operation status is set to ended-in-error
with error code OJCV. Otherwise, the status is not Problem determination: Check that all DD statements
changed. needed by the EQQUX002 exit have been correctly
defined and that all required members are defined.
User response: Correct the SETVAR arithmetic
expression. User response: If necessary, submit the job manually.
System programmer response: Correct all errors and
restart IBM Tivoli Workload Scheduler for z/OS.

142 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
EQQJ579W THE EQQUX002 EXIT DID NOT EQQJ582E JOB MEMBER RETURNED BY THE
RETURN ANY DATA FOR JOB EQQUX002 EXIT EXCEEDS MAXIMUM
MEMBER SUPPORTED SIZE
Explanation: The joblib I/O exit was called to retrieve Explanation: The joblib I/O exit was called to retrieve
a job to be submitted, but the exit did not return any a job to be submitted, but the returned job exceeds the
data. maximum supported size, which is 256KB (kilobytes) of
data.
System action: The job is not submitted by IBM Tivoli
Workload Scheduler for z/OS as intended. The System action: The job is not submitted by IBM Tivoli
operation remains in Ready status. Workload Scheduler for z/OS 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 correctly. Problem determination: Check that the joblib I/O exit
has been correctly installed and that it works correctly.
User response: If necessary, submit the job manually.
User response: If necessary, submit the job manually.
System programmer response: Correct all errors and
restart IBM Tivoli Workload Scheduler for z/OS. System programmer response: Correct all errors and
restart IBM Tivoli Workload Scheduler for z/OS.
EQQJ580E THE EQQUX002 EXIT RETURNED THE
FOLLOWING I/O ERROR MESSAGE EQQJ583E JOB MEMBER IN APPLICATION APPL
FOR JOB MEMBER: UX002MSG IS TOO LARGE TO BE SAVED ON
THE JS DATA SET
Explanation: The joblib I/O exit was called to retrieve
a job to be submitted, but the exit gave a return code Explanation: A job that is about to be submitted to
indicating that an I/O error had occurred on an input JES is too large to be saved in the JCL repository data
data set. set.
System action: The job is not submitted by IBM Tivoli System action: The job is submitted, but the JCL
Workload Scheduler for z/OS as intended. The repository data set is not updated.
operation remains in Ready status.
Problem determination: Use the IDCAMS LISTCAT
Problem determination: Check that the joblib I/O exit function to determine the maximum size of records in
can access all required input data sets and that it works the data set defined by the EQQJSDS DD statement.
correctly.
System programmer response: If necessary, allocate a
User response: If necessary, submit the job manually. new JCL repository data set with a larger maximum
record size. Use the IDCAMS REPRO function to copy
System programmer response: Correct all errors and
the old data set into the new data set. Restart IBM
restart IBM Tivoli Workload Scheduler for z/OS.
Tivoli Workload Scheduler for z/OS.

EQQJ581E INVALID TEMPORARY VARIABLE

EQQJ584E JOB MEMBER IN APPLICATION APPL
NAME AT LINE LINE OF SCTN
COULD NOT BE SUBMITTED
Explanation: During variable substitution of a job, a BECAUSE THE EQQUX001 EXIT
SETVAR directive was found where the name of the RETURNED A SUBMITTING USER ID,
temporary variable is incorrect. The possible errors are: USER, WHOSE AUTHORITY COULD
termwidth= NOT BE DETERMINED
v The variable name does not start with a T. Explanation: The job submit exit was called and
v The rest of the variable name contains one or more returned the name of a TSO user on whose behalf the
characters that are not alphanumeric. job submit should be done. An authority error occurred
when trying to build a job submit environment for this
System action: If the error occurs during job submit, user.
the current operation status is set to ended-in-error
with error code OJCV. Otherwise, the status is not System action: The current job is not submitted. IBM
changed. Tivoli Workload Scheduler for z/OS processes the next
read operation.
User response: Correct the name of the temporary
variable. 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,

Chapter 15. EQQJnnn Messages 143

if necessary, restart IBM Tivoli Workload Scheduler for
EQQJ588E JOB MEMBER IN APPLICATION APPL
z/OS.
IS TOO LARGE TO BE SUBMITTED
BY OPC
EQQJ585E INVALID ARITHMETIC EXPRESSION
Explanation: This job exceeds 65 535 records, which is
AT LINE LINE OF SCTN
the limit that IBM Tivoli Workload Scheduler for z/OS
Explanation: During JCL variable substitution, invalid can process.
syntax was found in the arithmetic expression of a
System action: The job is not submitted. The
SETVAR directive.
operation remains in Arriving or Ready status, with
The possible causes for the error are: extended status Error during job submission.
v One or more parentheses missing in the arithmetical
User response: Submit the job outside of IBM Tivoli
expression.
Workload Scheduler for z/OS.
v A valid sign (+ or -) is missing.
v Both plus and minus signs are present in the
expression, but only one sign is allowed. EQQJ590E VARIABLE TABLE NAME CONTAINS
v Invalid variable name. AN INVALID CHARACTER
v Invalid number in the expression. The number must
Explanation: Data entry error; see “Data Entry Errors”
be in the range 1 to 999.
on page 2.
v An invalid type in the expression.
v Erroneous nonblank characters within parentheses.
Any nonblank within parentheses must be part of EQQJ591E THE VARIABLE NAME CONTAINS
the arithmetic expression. AN INVALID CHARACTER
System action: If the error occurs during job submit, Explanation: Data entry error; see “Data Entry Errors”
the current operation status is set to ended-in-error on page 2.
with error code OJCV. Otherwise, the status is not
changed.
EQQJ592E INVALID VALUE. MUST BE Y OR N
User response: Correct the arithmetic expression.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQJ586W TEMPORARY VARIABLE VAR IN
SETVAR DIRECTIVE NOT REFERRED You can enter only Y (for Yes) or N (for No) in this
IN JCL. JOBNAME: JOBNAME field.

Explanation: During variable substitution of a job, a

SETVAR directive was found and created a temporary EQQJ594E THE DEFAULT POSITION MUST BE
variable. The temporary variable was not referred to IN THE RANGE 1-80
anywhere in the JCL. Explanation: Data entry error; see “Data Entry Errors”
System action: This is a warning. Operation status is on page 2.
not changed. The position that you have entered is out of the
User response: Either delete the SETVAR directive or 80-column range for instream data or a JCL line.
make sure that you have a corresponding reference to
the temporary variable in your JCL. EQQJ595E VALUE LENGTH IS REQUIRED WHEN
COMP.OP IS SPECIFIED
EQQJ587W VARIABLE VAR IN SAVEVAR Explanation: Data entry error; see “Data Entry Errors”
DIRECTIVE NOT REFERRED IN JCL on page 2.
JOBNAME IS: JNM
Because you entered a comparison operator, you must
Explanation: During variable substitution of a job, a enter a value length.
SAVEVAR directive was found requesting update of the
default value of a variable. This variable was not
referred to anywhere in the JCL. EQQJ596E COMPARISON OPERATOR
REQUIRED WHEN LENGTH IS
System action: This is a warning. Processing SPECIFIED
continues.
Explanation: Data entry error; see “Data Entry Errors”
User response: Either delete the variable name from on page 2.
the SAVEVAR directive or make sure that you have a
corresponding reference to the variable in the JCL. Because you entered a value length, you must enter a
comparison operator.

144 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
 System programmer response: If the user should have
EQQJ597E THE DEFAULT VALUE IS
this authorization, update the RACF profiles.
INVALIDATED BY THE
VERIFICATION CRITERIA
EQQJ610E THE JCL IMBED EXIT USRX
Explanation: Data entry error; see “Data Entry Errors”
RETURNED RETCODE = RC WHILE
on page 2.
PROCESSING JOB MEMBER IN
The default value that you entered does not comply APPLICATION APPL. THIS RETURN
with the verification rules for the variable. CODE IS NOT SUPPORTED,
RETCODE = 4 IS ASSUMED
EQQJ598E VALIDATION PATTERN IS REQUIRED Explanation: A JCL imbed exit that was referenced in
FOR PICT VERIFICATION a FETCH directive of the current JCL returned an
invalid return code.
Explanation: Data entry error; see “Data Entry Errors”
on page 2. System action: The current operation status is set to
ended-in-error with error code OJCV.
Because you asked for PICT verification, you must
enter a validation pattern. Problem determination: Check the exit and correct
possible errors. It you change the exit and want to
reuse it, restart IBM Tivoli Workload Scheduler for
EQQJ599E NUMERIC MUST BE SPECIFIED FOR
z/OS.
RANGE/LIST VERIFICATION
Explanation: Data entry error; see “Data Entry Errors”
EQQJ611E OPC COULD NOT ALLOCATE
on page 2.
ENOUGH STORAGE TO PROCESS
Because you asked for RANGE or LIST verification, JOB MEMBER IN APPLICATION APPL
you must set the Numeric field to Yes. FOR THE JCL IMBED EXIT USRX
Explanation: IBM Tivoli Workload Scheduler for z/OS
EQQJ604I A DEPENDENCY HAS BEEN was trying to build a JCL record from the data supplied
MODIFIED by the exit defined in a FETCH directive, but it could
not do so because of insufficient virtual storage.
Explanation: The dependency that you modified has
been inserted into the database. System action: The current operation status is set to
ended-in-error with error code OJCV.
System action: None.
System programmer response: Stop IBM Tivoli
User response: None. Workload Scheduler for z/OS and restart it in a larger
region.
EQQJ606I A DEPENDENCY HAS BEEN
CREATED EQQJ612E THE JCL IMBED EXIT USRX COULD
Explanation: The dependency that you created has NOT FIND JOB MEMBER IN ANY
been inserted into the database. INPUT DATA SET

System action: None. Explanation: The exit gave a return code indicating
that the JCL could not be found in the exit’s input data
User response: None. sets.
System action: The current operation status is set to
EQQJ607I A DEPENDENCY HAS BEEN DELETED ended-in-error with error code OJCV.
Explanation: The dependency that you deleted has Problem determination: Check that all DD statements
been removed from the database. needed by the exit have been correctly defined.
System action: None. System programmer response: Correct all errors and
User response: None. restart IBM Tivoli Workload Scheduler for z/OS.

EQQJ609E YOU ARE NOT AUTHORIZED TO EQQJ613E THE JCL IMBED EXIT USRX DID NOT
DELETE THIS JCL VARIABLE TABLE RETURN ANY DATA FOR JOB
MEMBER IN APPLICATION APPL
Explanation: You have tried to delete a JCL variable
table that you are not authorized to delete. Explanation: The exit was called to return JCL to IBM
Tivoli Workload Scheduler for z/OS, but no data was
System action: None. returned.
User response: Contact your system programmer

Chapter 15. EQQJnnn Messages 145

System action: The current operation status is set to
EQQJ617E JOB MEMBER IN APPLICATION APPL
ended-in-error with error code OJCV.
REFERS TO AN UNUSABLE JCL
Problem determination: Check that the exit works IMBED EXIT, USRX. NO DATA CAN
correctly and is correctly installed. BE RETRIEVED USING THIS EXIT

System programmer response: Correct all errors and Explanation: IBM Tivoli Workload Scheduler for z/OS
restart IBM Tivoli Workload Scheduler for z/OS. has previously discovered an abend in this exit and
marked it as not executable. This exit is not called
again.
EQQJ614E THE AMOUNT OF DATA RETURNED
BY THE JCL IMBED EXIT USRX FOR System action: The current operation status is set to
JOB MEMBER IN APPLICATION APPL ended-in-error with error code OJCV.
EXCEEDS THE MAXIMUM AMOUNT
System programmer response: Correct the exit and
SUPPORTED
restart IBM Tivoli Workload Scheduler for z/OS to
Explanation: The exit was called to return JCL to IBM reuse the exit.
Tivoli Workload Scheduler for z/OS, but more than
256KB (kilobytes) of data was returned.
EQQJ618E OPC COULD NOT ALLOCATE
System action: The current operation status is set to STORAGE ENOUGH FOR RECORD
ended-in-error with error code OJCV. READ FROM JS DATA SET.
APPLICATION IS: APPL, JOBNAME IS
Problem determination: Check that the exit works MEMBER
correctly and is correctly installed.
Explanation: IBM Tivoli Workload Scheduler for z/OS
System programmer response: Correct all errors and tried to allocate storage for a record read from the JS
restart IBM Tivoli Workload Scheduler for z/OS. data set, but the request for storage failed.
System action: The operation status depends on the
EQQJ615E THE JCL IMBED EXIT USRX COULD SUBFAILACTION keyword in the JTOPTS initialization
NOT BE LOADED. THE EXIT WILL BE statement. The operation can:
FLAGGED AS NOT USABLE v Keep status R or extended status RE
Explanation: IBM Tivoli Workload Scheduler for z/OS v Get status C (complete)
was unable to load the exit. IBM Tivoli Workload v Get status E (ended-in-error) with error code OSUF.
Scheduler for z/OS does not try to call it again. The System programmer response: Make sure that IBM
exit is flagged as not executable. Tivoli Workload Scheduler for z/OS is running in a
System action: The current operation status is set to large enough region and restart IBM Tivoli Workload
ended-in-error with error code OJCV. Scheduler for z/OS.

Problem determination: Check the JCL FETCH

directive referring to the exit and make sure that the EQQJ702E THE JCL VARIABLE TABLE HAS BEEN
exit is in the current load libraries of the started task DELETED
JCL for IBM Tivoli Workload Scheduler for z/OS. Explanation: The JCL variable table has been removed
System programmer response: Correct all errors and from the IBM Tivoli Workload Scheduler for z/OS
restart IBM Tivoli Workload Scheduler for z/OS. database.
System action: The variable table is deleted.
EQQJ616E THE JCL IMBED EXIT USRX HAS User response: None.
ABENDED WHILE PROCESSING JOB
MEMBER IN APPLICATION APPL. SEE
THE SYSUDUMP DATA SET FOR EQQJ703E THE JCL VARIABLE TABLE IS BEING
MORE INFORMATION. THE EXIT UPDATED BY ANOTHER USER
WILL BE FLAGGED AS NOT USABLE
Explanation: You cannot access the variable table
Explanation: The exit abended while processing. IBM because it is being updated by another user.
Tivoli Workload Scheduler for z/OS does not try to call
System action: The system waits for you to respond.
it again. The exit is flagged as not executable.
User response: Try again later.
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 IBM Tivoli Workload Scheduler for
z/OS.

146 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
EQQJ704E THE JCL VARIABLE TABLE TID EQQJ713E THE NUMBER OF VALUES MUST BE
ALREADY EXISTS EVEN FOR RANGE TYPE
Explanation: You have tried to create a table that Explanation: You specified an odd number of values
already exists. for a range verification.
System action: The system waits for you to respond. System action: The system waits for you to respond.
User response: Enter the correct data and try again. User response: Correct the error and try again.

EQQJ705I THE JCL VARIABLE TABLE HAS BEEN EQQJ714E THE LIST OF VALUES CONTAINS A
REPLACED IN THE DATA BASE BAD VALUE PAIR
Explanation: The JCL variable table has been modified Explanation: One of the pairs of values that you
and successfully updated in the database. specified is in error.
System action: The system waits for you to respond. System action: The system waits for you to respond.
User response: None. User response: Correct the error and try again.

EQQJ706E JCL VARIABLE TABLE ENTRY COULD EQQJ715E THE CHARACTER CHR IN POSITION
NOT BE RETRIEVED POS IS INVALID
Explanation: You have tried to access a JCL variable Explanation: The value that you entered contains a
table that has been deleted since the variable table list character that is not numeric.
was displayed.
System action: The system waits for you to respond.
System action: The system waits for you to respond.
User response: Correct the error and try again.
User response: Check if another user has already
deleted the table.
EQQJ716E ONE VALID VALUE CANNOT
EXCEED 44 POSITIONS
EQQJ707I A JCL VARIABLE DEFINITION HAS
Explanation: You defined as valid a value that
BEEN CREATED
contains more than 44 characters. This is not allowed.
Explanation: A JCL variable definition has been
System action: The system waits for you to respond.
created and inserted in the database.
User response: Correct the error and try again.
System action: None.
User response: None.
EQQJ717E THE DEPENDENT VARIABLE VALUE
IS INVALID FOR THE VERIFICATION
EQQJ708I THE JCL VARIABLE TABLE HAS BEEN TYPE
REPLACED IN THE DATA BASE
Explanation: The dependent value that you entered
Explanation: The JCL variable table has been modified does not comply with the verification rules for the
and successfully replaced in the database. dependent variable.
User response: None. System action: The system waits for you to respond.
System action: None. User response: Enter the correct value.

EQQJ712E THE VARIABLE TO BE DELETED HAS EQQJ800E INVALID VALUE. MUST BE Y, N OR P

DEPENDENCIES
Explanation: Data entry error; see “Data Entry Errors”
Explanation: Another variable is dependent on this on page 2.
variable.
In this field, you can enter only Y (for Yes), N (for No),
System action: None. or P (for Prompt).
User response: To delete this variable, first remove the
dependency. You can reassign the dependency, delete EQQJ801E VALUES/RANGE MUST BE SPECIFIED
the dependency, or delete the dependent variable. FOR RANGE/LIST
Explanation: You specified verification type RANGE
or LIST, but did not specify any values.

Chapter 15. EQQJnnn Messages 147

System action: The system waits for you to respond.
EQQJ810I THERE ARE NO VERIFICATION
User response: Correct the error and try again. CRITERIA DEFINED FOR THIS
VARIABLE

EQQJ802E NUMERIC CAN ONLY BE SPECIFIED Explanation: There are no verification criteria defined
FOR RANGE/LIST VERIFICATION for this variable.

Explanation: You specified a valid numeric field type, System action: None.
but did not specify RANGE or LIST verification.
User response: None.
System action: The system waits for you to respond.
User response: Correct the error and try again. EQQJ811E THE VARIABLE ALREADY EXISTS IN
THE CURRENT VARIABLE TABLE

EQQJ805E INVALID VERIFICATION TYPE Explanation: Data entry error; see “Data Entry Errors”
on page 2.
Explanation: Data entry error; see “Data Entry Errors”
on page 2. You have defined a variable that already exists in this
table.
Valid types are ALPHA, NUM, ENUM, HEX, BIT, PICT,
NAME, DSNAME, RANGE and LIST.
EQQJ812E VARIABLE NAME CONTAINS AN
INVALID CHARACTER
EQQJ806E INVALID VALUE LENGTH
Explanation: Data entry error; see “Data Entry Errors”
Explanation: Data entry error; see “Data Entry Errors” on page 2.
on page 2.
The length must be in the range 1 to 44. EQQJ813E TABLE NAME CONTAINS AN
INVALID CHARACTER
EQQJ807E INVALID COMPARISON OPERATOR Explanation: Data entry error; see “Data Entry Errors”
Explanation: Data entry error; see “Data Entry Errors” on page 2.
on page 2.
Valid operators are: EQQJ814E OWNER ID IS MISSING
Explanation: Data entry error; see “Data Entry Errors”
EQ LT GT LE GE NE NG NL
on page 2.
= < > <= >= ¬= ¬> ¬<

EQQJ815E SUBSTITUTION EXIT NAME

CONTAINS AN INVALID
EQQJ808I THERE ARE NO DEPENDENCIES
CHARACTER
DEFINED FOR THIS VARIABLE
Explanation: Data entry error; see “Data Entry Errors”
Explanation: There are no dependencies defined for
on page 2.
this variable.
System action: None.
EQQJ816E THE MAXIMUM NUMBER OF
User response: None. DEPENDENCIES IS 360
Explanation: You tried to define more than 360
EQQJ809E THE INDEPENDENT VALUE DOES dependencies.
ALREADY EXIST
System action: The system waits for you to respond.
Explanation: You specified a duplicate value for the
User response: Type over the incorrect value and
independent variable.
press Enter.
System action: The system waits for you to respond.
User response: Correct the error and try again. 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.

148 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
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
Specifying Verification Criteria panel.
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.

Chapter 15. EQQJnnn Messages 149

150 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 16. EQQKnnn Messages
User response: Try again later.
EQQK000E VALID-TO SPECIFICATION
PRECEDES VALID-FROM
SPECIFICATION EQQK007E YOU ARE NOT AUTHORIZED TO
ACCESS THE OI DATA BASE
Explanation: Data entry error; see “Data Entry Errors”
on page 2. Explanation: You have attempted to access the
operator instruction (OI) database, but you are not
The valid-to date must be later than the valid-from
authorized to access it.
date.
System action: The system waits for you to respond.
EQQK001E OI ALREADY EXISTS IN OI DATA User response: Contact your security administrator.
BASE
Explanation: You have attempted to create an operator EQQK008E YOU ARE NOT AUTHORIZED TO
instruction (OI) that already exists in the OI database. UPDATE THE OI DATA BASE
System action: The system waits for you to respond. Explanation: You have attempted to update the
operator instruction (OI) database, but you are not
User response: Exit and use the modify function
authorized to update it.
instead of the create function.
System action: The system waits for you to respond.
EQQK002E VALIDITY PERIODS OF TEMPORARY User response: Contact your security administrator.
OIS MUST NOT OVERLAP
Explanation: There is an existing operator instruction EQQK021E BOTH DATE AND TIME MUST BE
(OI) whose validity period overlaps with this SPECIFIED, OR BOTH BLANK
temporary OI. The validity period of a temporary OI is
defined by a valid-from and valid-to specification. The Explanation: Data entry error; see “Data Entry Errors”
validity periods of temporary OIs must not overlap on page 2.
each other.
System action: The system waits for you to respond. EQQK022E THE INPUT FIELD MUST BE ALL
NUMERIC, OR BLANK
User response: Respecify valid-from and valid-to
period limits. Explanation: Data entry error; see “Data Entry Errors”
on page 2.

EQQK003E OPERATOR INSTRUCTION NOT

FOUND IN OI DATA BASE. REFRESH EQQK023W THE OPERATOR INSTRUCTION
YOUR LIST CONTAINS NO TEXT

Explanation: You have attempted to browse, modify, Explanation: The operator instruction (OI) that you
or delete an operator instruction (OI) that no longer selected does not contain any text.
exists in the OI database. Most likely, the OI has been System action: The system waits for you to respond.
deleted by another user after your list of OIs was
created. User response: If this OI should contain text, use the
Operator Instruction dialog to add the desired text.
System action: The system waits for you to respond.
User response: Return to the selection panel, create a EQQK024W IT IS NOT POSSIBLE TO SAVE AN
new list of OIs, and continue your work. OPERATOR INSTRUCTION WITHOUT
TEXT
EQQK004W OPERATOR INSTRUCTION IS IN USE Explanation: An operator instruction must have a
BY USER USR, TRY LATER minimum of one line of text.
Explanation: Another user is currently updating the System action: The system waits for you to respond.
same operator instruction.
User response: Make sure that there is a minimum of
System action: The system waits for you to respond. one line of text or issue the CANCEL command to
terminate the CREATE, COPY, or MODIFY request.

© Copyright IBM Corp. 1991, 2003 151

 System action: None.
EQQK025I THE OI WAS MODIFIED IN THE OI
DATA BASE User response: None.
Explanation: The operator instruction (OI) record was
modified and the OI database was updated. EQQK031E APPLICATION IDENTIFICATION
MUST BE SPECIFIED
System action: None.
Explanation: Data entry error; see “Data Entry Errors”
User response: None.
on page 2.

EQQK026E INVALID PARAMETERS PASSED TO

EQQK032E THE NAME DOES NOT START WITH
THE MODULE
AN ALPHABETIC CHARACTER
Explanation: The parameters passed to the module
Explanation: Data entry error; see “Data Entry Errors”
from the ISPF panels were invalid. This is an internal
on page 2.
IBM Tivoli Workload Scheduler for z/OS error.
System action: The system waits for you to respond.
EQQK033E THE OPERATION NUMBER MUST BE
User response: Contact your system programmer. IN THE RANGE 1 - 255
System programmer response: Contact Customer Explanation: Data entry error; see “Data Entry Errors”
Support. on page 2.

EQQK027I THE OI WAS ADDED TO THE OI EQQK034E THE NAME CONTAINS INVALID
DATA BASE CHARACTER(S)
Explanation: The operator instruction (OI) record was Explanation: Data entry error; see “Data Entry Errors”
added to the OI database. on page 2.
System action: None. A name can be made up of the following valid
characters: A through Z, 0 through 9, and national
User response: None.
characters (that is, #, $, and @).

EQQK028I THE OI WAS NOT MODIFIED IN THE

EQQK035E BOTH VALID-FROM AND VALID-TO
OI DATA BASE
REQUIRED FOR TEMPORARY OIS
Explanation: The operator instruction (OI) record in
Explanation: Data entry error; see “Data Entry Errors”
the OI database was not updated, either because you
on page 2.
canceled your modify request or because no lines
existed in the OI record that you attempted to store. Both a valid-from date and a valid-to date are required
when creating temporary operator instructions (OIs).
System action: None.
User response: None.
EQQK036E THE OPERATION NUMBER
CONTAINS A NON-NUMERIC
EQQK029E THE UPDATE TO THE OI DATA BASE CHARACTER
FAILED
Explanation: Data entry error; see “Data Entry Errors”
Explanation: The operator instruction (OI) record was on page 2.
modifed, but the OI database has not been updated
The operation number must be numeric.
due to a severe error.
System action: The OI database is not updated.
EQQK037E THE OPERATION NUMBER MUST BE
User response: Try to locate the previous error SPECIFIED
messages in the message log and contact your system
Explanation: Data entry error; see “Data Entry Errors”
programmer.
on page 2.

EQQK030I THE OI WAS NOT ADDED TO THE

EQQK038E TIME MISSING IN VALID-FROM OR
OI DATA BASE
VALID-TO SPECIFICATION
Explanation: No operator instruction (OI) record was
Explanation: Data entry error; see “Data Entry Errors”
added to the OI database, either because you canceled
on page 2.
your create request or because no lines existed in the
OI record that you attempted to add. Both date and time are required when specifying a

152 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
valid-from or a valid-to date.
EQQK050E A REMOVAL DATE FOR PURGING
OLD TEMPORARY OIS MUST BE
EQQK039E DATE MISSING IN VALID-FROM OR SPECIFIED
VALID-TO SPECIFICATION
Explanation: Data entry error; see “Data Entry Errors”
Explanation: Data entry error; see “Data Entry Errors” on page 2.
on page 2.
Both date and time are required when specifying a EQQK051I PRESS ENTER TO CREATE REMOVAL
valid-from or a valid-to date. JCL, OR END TO CANCEL
Explanation: You have requested to create JCL for a
EQQK040I OI WAS DELETED FROM OI DATA job to remove operator instructions. You must press
BASE - REQUEST CONFIRMED ENTER to generate the JCL or enter the END command
to cancel your request.
Explanation: The operator instruction (OI) that you
selected was deleted from the OI database, as specified. System action: The system waits for you to respond.

System action: None. User response: Press ENTER or the End PF-key (or
enter the END command).
User response: None.

EQQK052E A VALID DATA SET NAME MUST BE

EQQK041I OI NOT DELETED FROM OI DATA SPECIFIED
BASE - REQUEST NOT CONFIRMED
Explanation: Data entry error; see “Data Entry Errors”
Explanation: The operator instruction (OI) that you on page 2.
selected was not deleted from the OI database. The
initial request was not confirmed.
EQQK053E REPLY MUST BE Y OR N
System action: None.
Explanation: Data entry error; see “Data Entry Errors”
User response: None. on page 2.

EQQK042E OI DELETE REQUEST FAILED DUE EQQK054I PRESS ENTER TO CREATE UPDATE
TO I/O ERROR JCL, OR END TO CANCEL REQUEST
Explanation: The operator instruction (OI) record was Explanation: You have requested to create JCL for a
deleted, but the OI database has not been updated due job to mass update operator instructions. You must
to a severe error. press ENTER to generate the JCL or enter the END
System action: The OI database is not updated. command to cancel your request.

User response: Try to locate the previous error System action: The system waits for you to respond.
messages in the message log and contact your system User response: Press ENTER or the End PF-key (or
programmer. enter the END command).

EQQK043E THE WORK STATION NAME MUST EQQK450E THE APPLICATION DESCRIPTION AD
BE SPECIFIED DOES NOT EXIST
Explanation: Data entry error; see “Data Entry Errors” Explanation: When attempting to create or modify an
on page 2. operarator instruction (OI), the OI data is checked for
validity. A check is made for the corresponding
EQQK044I NO OPERATOR INSTRUCTION operation. The validation failed because the application
MATCHED YOUR SELECTION description AD does not exist.
CRITERIA System action: The system waits for you to respond.
Explanation: No operator instructions matched the User response: Correct the application ID and save
selection criteria that you specified. the OI.
System action: None.
User response: None.

Chapter 16. EQQKnnn Messages 153

EQQK455E APPLICATION DESCRIPTION AD
HAS NO WORK STATION WS
Explanation: When attempting to create or modify an
operator instruction (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
operator instruction (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.

EQQK457E APPLICATION DESCRIPTION AD

HAS NO OPERATION WS OP
Explanation: When attempting to create or modify an
operator instruction (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 WSOP.
System action: The system waits for you to respond.
User response: Correct the operation number and save
the OI.

154 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 17. EQQLnnn Messages
EQQL000E YOU ARE NOT AUTHORIZED TO EQQL004I THE OCCURRENCE IS NOT
ACCESS THE LTP DATA SET UPDATED
Explanation: You have attempted to access the Explanation: The long-term plan (LTP) record for the
long-term plan (LTP) data set, but you are not occurrence was not updated because its content was
authorized. Or, you do not have access authority to at not changed.
least one of the following IBM Tivoli Workload
System action: None.
Scheduler for z/OS resources that are used together
with the LTP data set: the application description User response: None.
database, the calendar database, or the workstation
description database.
EQQL005E LONG-TERM PLAN IS BEING
System action: The system waits for you to respond. UPDATED BY USER USR, TRY LATER
User response: If you require access to the LTP data Explanation: You have attempted to update the
set or to any of the related resources given, contact long-term plan (LTP) data set, but it is being updated
your security administrator. by another user. The LTP data set can only be updated
by one user at a time.
EQQL001E YOU ARE NOT AUTHORIZED TO System action: The system waits for you to respond.
UPDATE THE LTP DATA SET
User response: Try again later.
Explanation: You have attempted to access the
long-term plan (LTP) data set for update but you are
not authorized. Or, you do not have access authority to EQQL006I THE OCCURRENCE IS DELETED
at least one of the following IBM Tivoli Workload Explanation: The long-term plan (LTP) record for the
Scheduler for z/OS resources that are used together occurrence has been deleted from the LTP data set.
with the LTP data set: the application description
database, the calendar database, or the workstation System action: None.
description database. User response: None.
System action: The system waits for you to respond.
User response: If you require access to the LTP data EQQL007I THE OCCURRENCE IS CREATED
set or to any of the related resources given, contact Explanation: A long-term plan (LTP) record for the
your security administrator. occurrence has been added to the LTP data set.
System action: None.
EQQL002I OCCURRENCE IS UPDATED
User response: None.
Explanation: The long-term plan (LTP) record for the
occurrence has been updated.
EQQL008E THE DEPENDENCY IS ALREADY
System action: None. DELETED
User response: None. Explanation: You have tried to delete a dependency
that has already been deleted.
EQQL003I THE OCCURRENCE IS NOT System action: The request is rejected.
UPDATED
User response: None.
Explanation: The long-term plan (LTP) record for the
occurrence was not updated because you canceled your
modify request. EQQL010E EITHER AN END DATE OR AN
EXTENSION LENGTH MUST BE
System action: None. SPECIFIED
User response: None. Explanation: Data entry error; see “Data Entry Errors”
on page 2.

© Copyright IBM Corp. 1991, 2003 155

EQQL011E THE END DATE MUST BE LATER EQQL019E THE PRINT INTERVAL MUST BE
THAN THE CURRENT END DATE WITHIN THE RANGE OF THE LTP
Explanation: The end date specified must be later Explanation: You have specified a print end date or
than the current end date. print start date that is outside the range of the
long-term plan (LTP) start and end dates.
System action: The system waits for you to respond.
System action: The system waits for you to respond.
User response: Display the status of the long-term
plan to view the current end date and reenter a valid User response: Check the displayed LTP start and end
end date. dates and reenter a valid print interval.

EQQL012E AN APPLICATION ID MUST BE EQQL020E THE LTP CANNOT BE LONGER

SPECIFIED THAN FOUR YEARS
Explanation: Data entry error; see “Data Entry Errors” Explanation: The long-term plan (LTP) cannot be
on page 2. greater than four years in length, starting from the date
of the first uncompleted occurrence.
EQQL013E START AND END OF PRINT MUST BE System action: The system waits for you to respond.
SPECIFIED
User response: Enter a valid end date.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQL022E THE EXTENSION LENGTH SHOULD
BE A NUMERIC VALUE FROM 0001
EQQL014E REPORT TYPE MUST BE SPECIFIED TO 1461
Explanation: Data entry error; see “Data Entry Errors” Explanation: Data entry error; see “Data Entry Errors”
on page 2. on page 2.

EQQL015E SORT ORDER MUST BE SPECIFIED EQQL023E EXTENSION LENGTH AND START
DATE CANNOT BE ENTERED
Explanation: Data entry error; see “Data Entry Errors”
TOGETHER
on page 2.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQL016E REPORT TYPE SPECIFIED IS NOT
VALID
EQQL024E EITHER AN END DATE OR AN
Explanation: Data entry error; see “Data Entry Errors”
EXTENSION LENGTH MUST BE
on page 2.
SPECIFIED
Valid report types are F for full report, and D for
Explanation: Data entry error; see “Data Entry Errors”
dependencies only.
on page 2.

EQQL017E SORT ORDER SPECIFIED IS NOT

EQQL025E IF YOU SPECIFY A START DATE YOU
VALID
MUST ALSO SPECIFY AN END DATE
Explanation: Data entry error; see “Data Entry Errors”
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
on page 2.
Valid sort orders are I for input arrival date, O for
owner ID, and A for application ID.
EQQL026E THE END DATE MUST BE LATER
THAN THE CURRENT DATE
EQQL018E PRINT END DATE MUST BE LATER
Explanation: The end date for creation of a long-term
THAN PRINT START DATE
plan (LTP) must be later than the current date.
Explanation: Data entry error; see “Data Entry Errors”
System action: The request is rejected.
on page 2.
User response: Correct the LTP end date and retry.

156 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
EQQL100E THE SPECIFIED DEPENDENCY TYPE EQQL314E A DEADLINE DATE IS REQUIRED
MUST BE P OR S
Explanation: Data entry error; see “Data Entry Errors”
Explanation: Data entry error; see “Data Entry Errors” on page 2.
on page 2.
The dependency type P stands for predecessor and S EQQL315E A DEADLINE TIME IS REQUIRED
stands for successor.
Explanation: Data entry error; see “Data Entry Errors”
on page 2.
EQQL101W THE LTP DATA SET IS EMPTY - ONLY
LTP CREATE ALLOWED
EQQL316E A CURRENT PLAN EXISTS
Explanation: You have attempted to extend the
Explanation: You have attempted to create a long-term
long-term plan (LTP), but there is no LTP.
plan (LTP) without first refreshing the LTP. Occurrences
System action: The system returns you to the in the LTP have been selected by daily planning and
SELECTING LONG TERM PLAN BACKGROUND JOB might have been included in the current plan.
menu so that you can select another function.
System action: The system waits for you to respond.
User response: Select option 7 to create the LTP.
User response: Either select LTP EXTEND or perform
a REFRESH from the Service dialog and request the
EQQL102I NO LISTITEM DEFINED FOR THIS LTP CREATE again.
OCCURRENCE
Explanation: No items matched the selection criteria EQQL317E A START DATE MUST BE SPECIFIED
that you specified for LISTITEM.
Explanation: Data entry error; see “Data Entry Errors”
System action: None. on page 2.
User response: None.
EQQL318E THE END DATE MUST BE LATER
THAN THE START DATE
EQQL310E THE LTP DATA SET IS EMPTY - NO
HEADER FOUND Explanation: Data entry error; see “Data Entry Errors”
on page 2.
Explanation: You have attempted to do one of the
following:
v Submit a long-term plan (LTP) batch job, but there is EQQL319E VALID REPLY IS Y, N, OR BLANK
no header record in the LTP data set
Explanation: Data entry error; see “Data Entry Errors”
v Make a trial plan, but no LTP exists.
on page 2.
System action: The system waits for you to respond.
User response: Select the background job that creates EQQL464E NO COMPUTER OPERATION(S)
a new LTP and try again. FOUND IN APPLICATION
Explanation: Job setup cannot be done because the
EQQL311E AN APPLICATION ID IS REQUIRED application does not contain any computer operations.
Explanation: Data entry error; see “Data Entry Errors” System action: The system waits for you to respond.
on page 2.
User response: Add a computer operation to the
application and try again.
EQQL312E AN INPUT ARRIVAL DATE IS
REQUIRED
EQQL465E DEPENDENCY LTPDERR NOT FOUND
Explanation: Data entry error; see “Data Entry Errors”
Explanation: The specified dependency (LTPDERR)
on page 2.
could not be found in the long-term plan (LTP) data
set.
EQQL313E AN INPUT ARRIVAL TIME IS
System action: The system waits for you to respond.
REQUIRED
User response: Check that the specified dependency is
Explanation: Data entry error; see “Data Entry Errors”
correctly defined.
on page 2.

Chapter 17. EQQLnnn Messages 157

EQQL466E OCCURRENCE HAS SUCCESSOR IN EQQL472E LTPDERR CANNOT HAVE MORE
CURRENT PLAN, CANNOT BE PREDECESSORS
MOVED
Explanation: You have specified too many
Explanation: The run date and run time of the predecessors for this successor operation. The
occurrence cannot be changed because the occurrence maximum number of possible dependencies depends
has a successor that is part of the current plan. on the maximum record size in the long-term plan
(LTP) VSAM file. If the default maximum record size is
System action: The system waits for you to respond.
used, the maximum number of dependencies
User response: Check that the dependency for the (predecessors and successors) is 3574.
occurrence is correct and that you have correctly
System action: The system waits for you to respond.
specified the occurrence.
User response: Review the dependencies for this
successor.
EQQL467E LTPDERR IS ALREADY IN CURRENT
PLAN
EQQL473E MORE DEPENDENCIES DEFINED
Explanation: You have attempted to add a
FOR LTPDERR THAN WILL FIT IN
dependency for an occurrence that is already part of
ONE RECORD
the current plan.
Explanation: You have specified too many
System action: The system waits for you to respond.
dependencies for the current long-term plan (LTP)
User response: Enter a valid dependency. occurrence. The maximum number of possible
dependencies depends on the maximum record size in
the LTP VSAM file. If the default maximum record size
EQQL468E LTPDERR CANNOT HAVE A is used, the maximum number of dependencies is 3574.
DEPENDENCY ON ITSELF
System action: The Long-Term Plan dialog waits for
Explanation: You specified a dependency for an you to respond.
occurrence, but the dependency is on the occurrence
itself. This is not valid. User response: Enter the primary command CANCEL
to return to the calling panel or enter the DELETE row
System action: The system waits for you to respond. command for one or more unnecessary dependencies.
User response: Enter a valid dependency.
EQQL474E MORE OPERATIONS CHANGED FOR
EQQL469E DEPENDENCY ON LTPDERR LTPDERR THAN WILL FIT IN ONE
ALREADY SPECIFIED LTP RECORD

Explanation: You specified a dependency that already Explanation: You have updated too many operations
exists for this occurrence. in the current long-term plan (LTP) occurrence. The
maximum number of changed operations depends on
System action: The system waits for you to respond. the maximum record size in the LTP VSAM file and on
User response: Enter a valid dependency. the number of external dependencies for the current
occurrence.

EQQL471E LTPDERR CANNOT HAVE MORE System action: The Long-Term Plan dialog waits for
SUCCESSORS you to respond.

Explanation: You have specified too many successors User response: Enter the primary command CANCEL
for this predecessor operation. The maximum number to return to the calling panel.
of possible dependencies depends on the maximum
record size in the long-term plan (LTP) VSAM file. If EQQL480E INPUT ARRIVAL TIME: T24.
the default maximum record size is used, the maximum RESPECIFY T00 ON THE FOLLOWING
number of dependencies (predecessors and successors) DAY
is 3574.
Explanation: T24 is not a valid input arrival time.
System action: The system waits for you to respond.
System action: The system waits for you to respond.
User response: Review the dependencies for this
predecessor. User response: Respecify the input arrival time as
suggested (T00).

158 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
 System action: The system waits for you to respond.
EQQL481E DEADLINE TIME: T00. RESPECIFY T24
ON THE PREVIOUS DAY User response: Check why the application description
cannot be found. If the application description has been
Explanation: T00 is not a valid deadline time.
inadvertently deleted, reenter it.
System action: The system waits for you to respond.
User response: Respecify the deadline time as EQQL505E APPLICATION APPL NOT FOUND
suggested (T24).
Explanation: The application (APPL) specified in the
long-term plan (LTP) occurrence was not found in the
EQQL482E PRIORITY MUST BE A NUMBER application description database.
FROM 1 - 9
Possible explanations are:
Explanation: Data entry error; see “Data Entry Errors” v The application description has been deleted from
on page 2. the application description database, but the
corresponding occurrences in the LTP data set have
EQQL487E RUN DATE IS EARLIER THAN THE not deleted.
LTP START DATE LTPSDAY v You do not have read access to the application
description for this application.
Explanation: You specified a run date that is earlier
than the long-term plan (LTP) start date LTPSDAY. This v The application was not active at the input arrival
is not valid. time of the LTP occurrence.

System action: The system waits for you to respond. System action: The system waits for you to respond.

User response: Enter a valid run date. User response: Check why the application description
cannot be found. If the application description has been
inadvertently deleted, reenter it.
EQQL489E NO OCCURRENCE MATCHES THE
SEARCH CRITERIA
EQQL506E DEPENDENT APPLICATION IS NOT
Explanation: No dependent occurrence matched the AVAILABLE IN AD DATA SET
search criteria that you specified to generate a list of
occurrences. Explanation: This occurrence has one or more external
dependencies that are not available to you. The
System action: The system waits for you to respond. dependent application has been deleted from the
User response: Respecify your selection criteria. application description database or you do not have
read access to the application description for the
dependent application.
EQQL498E W._O IS FIRST OPERATION, INPUT
ARRIVAL MUST BE SPECIFIED System action: The system waits for you to respond.

Explanation: Data entry error; see “Data Entry Errors” User response: Check why the application description
on page 2. cannot be found. If the application description has been
inadvertently deleted, reenter it. Check operations with
The first operation (W._O) in an occurrence must have no workstation name and operation number 000.
a specified input arrival time.
EQQL507E RUN DATE SPECIFIED IS LATER
EQQL499E W._O IS THE LAST OPERATION, A THAN THE LTP END LTPEDAY
DEADLINE MUST BE SPECIFIED
Explanation: You specified a run date that is later than
Explanation: Data entry error; see “Data Entry Errors” the long-term plan (LTP) end date.
on page 2.
System action: The system waits for you to respond.
The last operation (W._O) in an occurrence must have a
specified deadline. User response: Enter a run date within the range of
the LTP.

EQQL504E APPLICATION DEPAID NOT FOUND

EQQL509E THE SPECIFIED OCCURRENCE
Explanation: The application (DEPAID) specified in ALREADY EXISTS
the long-term plan (LTP) occurrence was not found in
the application description database. The application Explanation: You specified an occurrence that already
has been deleted from the application description exists.
database or you do not have read access to the System action: The system waits for you to respond.
application description for the dependent application.

Chapter 17. EQQLnnn Messages 159

User response: Change the data to make a new entry type the row command RG on the LONG TERM PLAN
or exit. OCCURRENCES panel or erase the group definition ID
field on the MODIFYING OCCURRENCE DATA panel.
EQQL510E DEADLINE IS EARLIER THAN (OR
EQUAL TO) THE INPUT ARRIVAL EQQL541W APPLICATION IS A MEMBER OF A
GROUP. CONSIDER ADDING THE
Explanation: Data entry error; see “Data Entry Errors”
OTHER MEMBERS
on page 2.
Explanation: The application is a member of an
The deadline date must be later than the input arrival
application group. This message is issued as a reminder
date.
in case you need also to add the other members of the
same group to the long-term plan.
EQQL512E THE VARIABLE TABLE IS NOT
System action: Normal processing continues.
DEFINED TO OPC
User response: If applicable, create occurrences in the
Explanation: Data entry error; see “Data Entry Errors”
long-term plan for the other applications in the same
on page 2.
group.
You have tried to define a variable table ID that does
not exist in IBM Tivoli Workload Scheduler for z/OS’s
EQQL542E OCCURRENCE IS NOT A MEMBER
database.
OF AN OCCURRENCE GROUP
Explanation: The occurrence does not belong to an
EQQL513E THE VARIABLE TABLE NAME
occurrence group.
CONTAINS AN INVALID
CHARACTER System action: The request is rejected.
Explanation: Data entry error; see “Data Entry Errors” User response: Check the occurence definition and
on page 2. correct it.

EQQL514E YOU ARE NOT AUTHORIZED TO EQQL566E INPUT ARRIVAL TIME SPECIFIED
READ THE JCL VARIABLE TABLE PRECEDES THE CP END LTPPNEND,
DATA BASE LTPPNENT
Explanation: You have attempted to refer to a JCL Explanation: You cannot modify, delete, or add an
variable table. To do this, you need read authority to occurrence to the long-term plan (LTP) that has an
the JCL variable table database. input arrival time within the range of the current plan.
System action: The system waits for you to respond. System action: The request is rejected.
User response: If you need to refer to JCL variable User response: Make sure that input arrival is
table names, contact your security administrator. correctly specified. If it is and you still want to process
the occurrence, use the Modify Current Plan dialog
instead.
EQQL530E I/O-ERROR READING CALENDAR.
DEFAULT DAY STATUS USED If you need to delete a dependency to an occurrence in
the current plan, use the Modify Current Plan dialog to
Explanation: An I/O error occurred when reading the
delete the predecessor specification.
calendar database. The default day status is used.
System action: The system waits for you to respond.
EQQL567I LTPCHIAD, LTPCHIAT INPUT ARRIVAL
User response: If the default should not be used, enter OUTSIDE OCCURRENCE TIME LIMIT
the correct data.
Explanation: The operation input arrival date and
time LTPCHIAD, LTPCHIAT is outside the occurrence
EQQL540E OCCURRENCE IN A GROUP MUST time limit.
BE REMOVED BEFORE IT CAN BE
System action: None.
DELETED
User response: None.
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. To do this, either

160 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
 description could not be found.
EQQL568I LTPCHDD, LTPCHDT DEADLINE PAST
OCCURRENCE TIME LIMIT System action: If this is a request to the program
interface function, the request is rejected and control is
Explanation: The operation deadline LTPCHDD,
returned with the return code set to error.
LTPCHDT is outside the occurrence time limit.
User response: Correct the application ID and
System action: None.
resubmit the job.
User response: None.
EQQL706E PREDECESSOR OPERATION
EQQL570I THE INPUT ARRIVAL SPECIFIED IS WSNOPNO DOES NOT EXIST IN AD
LATER THAN THE DEADLINE AD REQUESTED AS PREDECESSOR
TO LTP OCCURRENCE LTOC
Explanation: The operation input arrival date and
time are later than the application deadline. Explanation: The operation WSNOPNO is specified in
a program interface request to set up a dependency
System action: The system waits for you to respond.
between two long-term plan occurrences. The specified
User response: If the input arrival date and time are application description does not contain the operation.
not what you intended, change them.
System action: If this is a request to the program
interface function, the request is rejected and control is
EQQL572E DATE OR TIME IS MISSING FROM returned with the return code set to error.
THE INPUT ARRIVAL
User response: Correct the application ID, workstation
Explanation: Data entry error; see “Data Entry Errors” name, or operation number, and resubmit the job.
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 dump data set (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 dump data set and
the message log available and contact Customer
Support.

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

Chapter 17. EQQLnnn Messages 161

162 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
Chapter 18. EQQMnnn Messages
User response: Resolve the connection problem and
EQQMA02E THE CONNECTOR HAS BEEN
restart the connector.
STOPPED
Explanation: The requested action cannot be
EQQMA07E AN INTERNAL APPLICATION ERROR
performed because the connector has been stopped.
HAS OCCURRED. THIS VERSION OF
System action: None. OPC IS NOT COMPATIBLE WITH THE
FUN FUNCTIONALITY. THE
User response: Start the connector.
CONNECTED OPC VERSION IS X.X.X.
WITH PIF LEVEL Y THE REQUIRED
EQQMA03E THE CODEPAGE CP CANNOT BE OPC VERSION IS A.A.A. WITH PIF
FOUND LEVEL Z

Explanation: The code page that was selected during Explanation: You tried to use a functionality FUN of
the configuration of the connector cannot be found. the product that is not supported by the version of the
connected IBM Tivoli Workload Scheduler for z/OS.
System action: None.
System action: None.
User response: Verify that the code page that you
selected is available. User response: Install the correct version of IBM Tivoli
Workload Scheduler for z/OS or do not use the
functionality FUN.
EQQMA04E THIS VERSION OF OPC CONNECTOR
IS NOT COMPATIBLE WITH THE
CONNECTED OPC. THE CONNECTED EQQMA10E COMMUNICATION ERROR BETWEEN
OPC VERSION IS X.X.X. WITH PIF OPC CONNECTOR AND SERVER
LEVEL Y
Explanation: A communication error has occurred
Explanation: You tried to use a version of the between the connector and the IBM Tivoli Workload
connector that does not support the version of the Scheduler for z/OS server. The messages following
connected IBM Tivoli Workload Scheduler for z/OSIBM describe the error in more detail.
Tivoli Workload Scheduler for z/OS.
System action: None.
System action: None.
User response: Check that the IBM Tivoli Workload
User response: Install the correct version of the Scheduler for z/OS address and port number are set
connector. correctly in the connector and that there are no network
problems between the connector and the z/OS system.

EQQMA05E THE OPC CONNECTOR CANNOT

COMMUNICATE WITH THE OPC EQQMA11E CANNOT ALLOCATE CONNECTION:
SERVER AND RETRIEVE VERSION ID
INFORMATION. User Response: To fix
Explanation: The connector is unable to create a new
the problem, do the following:
connection between the connector and the IBM Tivoli
User response: Workload Scheduler for z/OS server, where ID is the
1. Check configuration of: name of the connection. The messages following
v The connector describe the error in more detail.
v The network System action: None.
v The server
User response: Check that the IBM Tivoli Workload
2. Check that the server is running.
Scheduler for z/OS address and port number are set
3. Restart the connector. correctly in the connector, the z/OS code page is set
correctly in the connector, and there are no network
The reason is: problems between the connector and the z/OS system.
Check that the values set in the connector are valid and
Explanation: The connector cannot obtain the version
that you are authorized to use IBM Tivoli Workload
information from the scheduler due to an error that is
Scheduler for z/OS.
displayed in the message after “The reason is:”.
System action: None.

© Copyright IBM Corp. 1991, 2003 163

 User response: Correct the network problem.
EQQMA12E COMMUNICATION ERROR BETWEEN
OPC CONNECTOR AND SERVER
DURING SEND EQQMA18E REMOTE CONNECTION CLOSED:
CONNID
Explanation: A communication error has occurred
during the send between the connector and the IBM Explanation: The connection between the connector
Tivoli Workload Scheduler for z/OS server. The and the server has been closed.
messages following describe the error in more detail.
System action: None.
System action: None.
User response: Check that the IBM Tivoli Workload
User response: Check that the IBM Tivoli Workload Scheduler for z/OS server is running. If not, correct
Scheduler for z/OS address and port number are set any problems and restart the server.
correctly in the connector and that there are no network
problems between the connector and the z/OS system.
EQQMA19E TIMEOUT OF TIME MS EXCEEDED
FOR CONNID
EQQMA13E COMMUNICATION ERROR BETWEEN
CONNECTOR AND SERVER DURING Explanation: A timeout error occurred for the
RECEIVE connection CONNID, where TIME is the number of
milliseconds (ms) that the socket has waited.
Explanation: A communication error has occurred
during the receive between the connector and the IBM System action: None.
Tivoli Workload Scheduler for z/OS server The User response: Check that the network is working
messages following describe the error in more detail. correctly.
System action: None.
User response: Check that the IBM Tivoli Workload EQQMA20E AN INTERNAL APPLICATION ERROR
Scheduler for z/OS address and port number are set HAS OCCURRED. UNSUPPORTED
correctly in the connector and that there are no network FILTER OF TYPE FILTERTYPE
problems between the connector and the z/OS system. Explanation: The connector has received a filter that is
one of the FILTERTYPE filters, but that is not supported
EQQMA15E INVALID IP ADDRESS: ADDRESS for the record type on which you are filtering.

Explanation: The IP address ADDRESS is invalid. System action: None.

System action: None. User response: Use a supported filter.

User response: Check that the IBM Tivoli Workload

Scheduler for z/OS IP address is set correctly in the EQQMA21E AN INTERNAL APPLICATION ERROR
connector. HAS OCCURRED. UNSUPPORTED
FILTER TYPE

EQQMA16E INVALID IP PORT NUMBER: PORT Explanation: The connector has received a filter that is
not supported for the record type on which you are
Explanation: The IP port number PORT is invalid. filtering.
System action: None. System action: None.
User response: Check that the IBM Tivoli Workload User response: Use a supported filter.
Scheduler for z/OS IP port number is set correctly in
the connector.
EQQMA22E AN INTERNAL APPLICATION ERROR
HAS OCCURRED. THE TYPE RESTYPE
EQQMA17E TCP/IP SOCKET I/O ERROR DURING FOR THE RESOURCE IS INVALID
FUNCTION CALL FOR “CONNID>”,
FAILED WITH ERROR: NUMERROR = Explanation: You cannot filter on resources of type
TEXTERROR RESTYPE.

Explanation: This message gives details of the System action: None.

connection error that has occurred. FUNCTION is the User response: Use a supported resource type.
operation, CONNID is the IP addresses and ports,
NUMERROR is the error number, and TEXTERROR is
the error code description, if available.
System action: None.

164 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
EQQMA23E AN INTERNAL APPLICATION ERROR EQQMA31E AN INTERNAL APPLICATION ERROR
HAS OCCURRED. INVALID HAS OCCURRED. INVALID VALUE
EXTENSION FOUND WHEN EXT WAS VAL FOR FIELD NAME: MUST BE MIN
EXPECTED ≤ NAME ≤ MAX
Explanation: In the structure that the connector has Explanation: The value VAL is not valid for field
received there is an invalid extension. The correct NAME. It must be between MIN and MAX.
extension is EXT.
System action: None.
System action: None.
User response: Specify a correct value for the field.
User response: Correct the type of extension that is
specified to the connector in properties to EXT.
EQQMA32E AN INTERNAL APPLICATION ERROR
HAS OCCURRED. INVALID VALUE
EQQMA24E AN INTERNAL APPLICATION ERROR ″VAL″ FOR FIELD NAME
HAS OCCURRED. EXPECTED
Explanation: The value VAL is not valid for field
PROPERTY NOT FOUND
NAME.
Explanation: In the structure that the connector has
System action: None.
received there is no property, but an extension is
expected. User response: Specify a correct value for the field.
System action: None.
EQQMA33E AN INTERNAL APPLICATION ERROR
User response: Provide the connector with the correct
HAS OCCURRED. INVALID VALUE
extension in the properties.
VAL FOR FIELD NAME
Explanation: The value VAL is not valid for field
EQQMA25E AN INTERNAL APPLICATION ERROR
NAME.
HAS OCCURRED. INVALID
STRUCTURE FOUND WHEN TYPE System action: None.
WAS EXPECTED
User response: Specify a correct value for the field.
Explanation: The expected structure TYPE was not
found in the connector.
EQQMA34E AN INTERNAL APPLICATION ERROR
System action: None. HAS OCCURRED. INVALID ID VALUE
NAME
User response: Correct the data structure that is
passed to the connector. Explanation: The value NAME is not a valid ID.
System action: None.
EQQMA26E AN INTERNAL APPLICATION ERROR
HAS OCCURRED. NO TARGET User response: Specify a correct ID.
WORKSTATION FOUND
Explanation: You specified a job that did not have a EQQMA40E PIF ERROR: ID=MESSID,
target workstation. VARIABLES=VAR1, VAR2, VAR3, VAR4,
VAR5, VAR6, VAR7, VAR8, VAR9, VAR10
System action: None.
Explanation: The connector has received an error from
User response: Specify the target in the job (or job IBM Tivoli Workload Scheduler for z/OS, but the
instance) data structure. message catalog is unavailable. See this manual (
Messages and Codes ) for a description of the error
MESSID. The variables are in the same order as
EQQMA30E AN INTERNAL APPLICATION ERROR
specified in the message.
HAS OCCURRED. INVALID VALUE
FOR FIELD NAME System action: None.
Explanation: The value specified in field NAME is User response: Call Customer Support to notify them
invalid. that this message is missing.
System action: None.
User response: Specify the correct value.

Chapter 18. EQQMnnn Messages 165

EQQMA50E AN INTERNAL APPLICATION ERROR EQQMA61E AN INTERNAL APPLICATION ERROR
HAS OCCURRED. UNEXPECTED HAS OCCURRED. INVALID TIMER
VALUE IN FIELD NAME (IN FILE VALUE (″TIMER″): UNEXPECTED END
FILENAME AT LINE LINENUM) OF STRING
Explanation: The connector has encountered an Explanation: The timer value TIMER is invalid. The
unexpected value in field NAME at line LINENUM of parser has encountered an unexpected end of string.
the file FILENAME.
System action: None.
System action: None.
User response: Correct the value of the timer.
User response: Call Customer Support.
EQQMA62E AN INTERNAL APPLICATION ERROR
EQQMA51E AN INTERNAL APPLICATION ERROR HAS OCCURRED. INVALID TIMER
HAS OCCURRED. UNEXPECTED VALUE (″TIMER″): EXPECTED AN
VALUE “VAL” IN FIELD NAME (IN INTEGER VALUE, FOUND ″FOUND″
FILE FILENAME AT LINE LINENUM)
Explanation: The timer value TIMER is invalid. The
Explanation: The connector has encountered an parser expects an integer value, but found FOUND.
unexpected value VAL in field NAME at line LINENUM
System action: None.
of the file FILENAME.
User response: Correct the value of the timer.
System action: None.
User response: Call Customer Support.
EQQMA63E AN INTERNAL APPLICATION ERROR
HAS OCCURRED. INVALID TIMER
EQQMA52E AN INTERNAL APPLICATION ERROR VALUE (″TIMER″): UNKNOWN
HAS OCCURRED. UNEXPECTED PRIMITIVE FOUND ″FOUND″
VALUE VAL IN FIELD NAME (IN FILE
Explanation: The timer value TIMER is invalid. The
FILENAME AT LINE LINENUM)
parser does not understand FOUND.
Explanation: The connector has encountered an
System action: None.
unexpected value VAL in field NAME at line LINENUM
of the file FILENAME. User response: Correct the value of the timer.
System action: None.
EQQMA64E AN INTERNAL APPLICATION ERROR
User response: Call Customer Support.
HAS OCCURRED. INVALID TIMER
VALUE (″TIMER″): EXPECTED EXP
EQQMA53E AN INTERNAL APPLICATION ERROR FOUND ″FOUND″
HAS OCCURRED. UNEXPECTED
Explanation: The timer value TIMER is invalid. The
VALUE ’VAL’ IN FIELD NAME (IN FILE
parser expects EXP., but found FOUND.
FILENAME AT LINE LINENUM)
System action: None.
Explanation: The connector has encountered an
unexpected value VAL in field NAME at line LINENUM User response: Correct the value of the timer.
of the file FILENAME.
System action: None. EQQMA65E AN INTERNAL APPLICATION ERROR
HAS OCCURRED. INVALID TIMER
User response: Call Customer Support.
VALUE (″TIMER″): MISMATCH WITH
OPC RULES – THE INPUT RULE
EQQMA60E AN INTERNAL APPLICATION ERROR GENERATES ″GEN″ OPC RULE THAT
HAS OCCURRED. INVALID TIMER IS NOT EQUIVALENT. THE TIMER
VALUE (″TIMER″): FOUND ″FOUND″ VALUES DO NOT HAVE ALL THE
COMBINATIONS THAT ARE
Explanation: The timer value TIMER is invalid. The
EQUIVALENT TO THE OPC RULE
parser does not understand FOUND.
Explanation: The timer value TIMER is invalid. An
System action: None.
rule of the product that includes the timer value is
User response: Correct the value of the timer. GEN., but this rule also includes other days that are not
in the timer.
System action: None.

166 IBM Tivoli Workload Scheduler for z/OS Messages and Codes
User response: Correct the value of the timer. User response: Possible reasons are:
1. Maintenance of the connector
EQQMA66E AN INTERNAL APPLICATION ERROR 2. Internal application error
HAS OCCURRED. INVALID TIMER
VALUE: CANNOT CONVERT TO AN
EQQMA81E OPC DOES NOT RECOGNIZE USER
OPC RULE
USERID
Explanation: The parser is unable to convert the timer
Explanation: The user USERID is not authorized to
in a rule of the product.