messages and codespublib.boulder.ibm.com/tividd/td/tws/sh19-4548-01/en_us/...v chapter 38, “reason...
TRANSCRIPT
-
IBM
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
Version
8.1
(Maintenance
Release
October
2003)
SH19-4548-01
���
-
IBM
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
Version
8.1
(Maintenance
Release
October
2003)
SH19-4548-01
���
-
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices”
on
page
465.
Refreshed
Edition
(October
2003)
This
refreshed
edition
applies
to
version
8,
release
1,
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.
-
Contents
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Who
Should
Read
This
Guide
.
.
.
.
.
.
.
. v
What
This
Guide
Contains
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Publications
for
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Accessing
Publications
Online
.
.
.
.
.
.
. vi
Softcopy
Collection
Kit
.
.
.
.
.
.
.
.
. vii
Ordering
Publications
.
.
.
.
.
.
.
.
.
. vii
Using
LookAt
to
Look
Up
Message
Explanations
vii
Contacting
IBM
Software
Support
.
.
.
.
.
. viii
Conventions
Used
in
This
Guide
.
.
.
.
.
.
. viii
APARs
Resolved
in
This
Manual
.
.
.
.
.
.
. viii
Chapter
1.
Introduction
.
.
.
.
.
.
.
. 1
Message
Format
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Where
Messages
Are
Presented
.
.
.
.
.
.
.
. 1
Data
Entry
Errors
.
.
.
.
.
.
.
.
.
.
.
.
. 2
System
action
.
.
.
.
.
.
.
.
.
.
.
.
. 3
User
response
.
.
.
.
.
.
.
.
.
.
.
.
. 3
Chapter
2.
EQQATnn
Messages
.
.
.
. 5
Chapter
3.
EQQAnnn
Messages
.
.
.
. 9
Chapter
4.
EQQCnnn
Messages
.
.
.
. 27
Chapter
5.
EQQCLnnn
Messages
.
.
. 35
Chapter
6.
EQQCNnnn
Messages
.
.
. 51
Chapter
7.
EQQDnnn
Messages
.
.
.
. 55
Chapter
8.
EQQEXnn
Messages
.
.
.
. 59
Chapter
9.
EQQEnnn
Messages
.
.
.
. 61
Chapter
10.
EQQFnnn
Messages
.
.
. 81
Chapter
11.
EQQFxxx
Messages
.
.
.
. 85
Chapter
12.
EQQGnnn
Messages
.
.
. 115
Chapter
13.
EQQHnnn
Messages
.
.
. 119
Chapter
14.
EQQICnn
Messages
.
.
. 125
Chapter
15.
EQQJnnn
Messages
.
.
. 133
Chapter
16.
EQQKnnn
Messages
.
.
. 151
Chapter
17.
EQQLnnn
Messages
.
.
. 155
Chapter
18.
EQQMnnn
Messages
.
.
. 163
Chapter
19.
EQQNnnn
Messages
.
.
. 207
Chapter
20.
EQQOnnn
Messages
.
.
. 223
Chapter
21.
EQQPnnn
Messages
.
.
. 225
Chapter
22.
EQQQnnn
Messages
.
.
. 237
Chapter
23.
EQQRMnn
Messages
.
.
. 243
Chapter
24.
EQQRnnn
Messages
.
.
. 247
Chapter
25.
EQQSUnn
Messages
.
.
. 255
Chapter
26.
EQQSnnn
Messages
.
.
. 259
Chapter
27.
EQQTTnn
Messages
.
.
. 263
Chapter
28.
EQQTnnn
Messages
.
.
. 267
Chapter
29.
EQQUnnn
Messages
.
.
. 271
Chapter
30.
EQQVnnn
Messages
.
.
. 273
Chapter
31.
EQQWLnn
Messages
.
.
. 279
Chapter
32.
EQQWnnn
Messages
.
.
. 283
Chapter
33.
EQQXnnn
Messages
.
.
. 311
Chapter
34.
EQQYnnn
Messages
.
.
. 359
Chapter
35.
EQQZnnn
Messages
.
.
. 377
Chapter
36.
EQQnnnn
Messages
.
.
. 405
Chapter
37.
Abend
Codes
.
.
.
.
.
. 451
Chapter
38.
Reason
Codes
.
.
.
.
. 453
Chapter
39.
Batch
Program
Codes
and
Messages
.
.
.
.
.
.
.
.
.
.
.
.
. 463
EQQPDLF
Batch
Program
Condition
Codes
.
.
. 463
EQQPURGE
Batch
Program
WTO
Messages
.
.
. 463
iii
||||||||||
-
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 465
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 466
iv
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
Tracker
Agent
for
OS/2®
enabler
v
Tracker
Agent
for
OS/400®
enabler
v
Tracker
Agent
for
AIX®
enabler
v
Tracker
Agent
for
HP-UX
enabler
v
Tracker
Agent
for
Sun
Solaris
enabler
v
Tracker
Agent
for
Digital
VAX/Alpha
enabler
v
Tracker
Agent
for
Digital
OpenVMS
enabler
v
Tracker
Agent
for
Pyramid
MIPS
ABI
v
Tracker
Agent
for
System/390®
Open
Edition
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
Tivoli
Workload
Scheduler
for
z/OS.
Who
Should
Read
This
Guide
This
book
should
be
used
by
operators,
system
or
application
programmers,
or
by
anyone
who
is
responsible
for
controlling
or
diagnosing
problems
in
Tivoli
Workload
Scheduler
for
z/OS.
What
This
Guide
Contains
This
guide
contains
the
following
chapters:
v
Chapter
1,
“Introduction,”
on
page
1
Contains
general
information
that
applies
to
all
product
messages.
v
Chapters
2
through
Chapter
37
List
the
product
messages
in
alphanumeric
order.
v
Chapter
38,
“Reason
Codes,”
on
page
453
Lists
the
Tivoli
Workload
Scheduler
for
z/OS
abend
codes,
in
numeric
order.
v
Chapter
39,
“Batch
Program
Codes
and
Messages,”
on
page
463
Lists
the
codes
and
write-to-operator
messages
generated
by
Tivoli
Workload
Scheduler
for
z/OS
batch
programs.
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
Tivoli
Workload
Scheduler
for
z/OS
The
following
table
lists
the
publications
in
the
Tivoli
Workload
Scheduler
for
z/OS
library.
Table
1.
List
of
Publications
Task
Publication
Order
number
Planning
Tivoli
Workload
Scheduler
for
z/OS
Licensed
Program
Specifications
GH19-4540
Understanding
the
Tivoli
Workload
Scheduling
Suite
General
Information
GH19-4539
Learning
concepts
and
terminology
Getting
Started
SH19-4542
Using
the
Java™
GUI
Tivoli
Job
Scheduling
Console
Guide
Users’
Guide
SH19-4552
Using
the
Java
GUI
Tivoli
Job
Scheduling
Console
Release
Notes
GI10-5781
Installing
Tivoli
Workload
Scheduler
for
z/OS
Installation
Guide
SH19-4543
Customizing
and
tuning
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
SH19-4544
Planning
and
scheduling
the
workload
Planning
and
Scheduling
the
Workload
SH19-4546
Controlling
and
monitoring
the
current
plan
Controlling
and
Monitoring
the
Workload
SH19-4547
Writing
application
programs
Programming
Interfaces
SH19-4545
Quick
reference
Quick
Reference
GH19-4541
Diagnosing
failures
Diagnosis
Guide
and
Reference
LY19-6410
Accessing
Publications
Online
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:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
Click
the
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.
vi
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
|
||||
|
|
||||
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
-
Softcopy
Collection
Kit
All
the
books
in
the
Tivoli
Workload
Scheduler
for
z/OS
library,
except
the
licensed
publications,
are
available
in
displayable
softcopy
form
on
CD-ROM
in
the
following
Softcopy
Collection
Kit:
v
OS/390,
SK2T-6951
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
softcopy
only.
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/
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.
Preface
vii
|
||||
||||||
|||||
|
|
|
|||
|
|
|
|
|
|
||||
||||
||||
|||
http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/
-
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
Guide
The
guide
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
fields
on
panels
All
capital
letters
QUANTITY
Input
you
should
type
in
panel
fields
Monospace
MYAPPLICATION
First
time
new
term
introduced
Italics
Application
APARs
Resolved
in
This
Manual
The
following
table
lists
all
the
APARs
affecting
error
messages
contained
in
this
manual.
Table
2.
APAR
NUMBER
IMPACTED
MESSAGE
PQ56193
EQQM938W
PQ57606
EQQFA81I,
EQQFCU9E,
EQQFCUSE,
EQQFCUJI,
EQQFCUKI,
EQQFSDAE,
EQQFSDBE,
EQQFSW5W,
EQQFSW6W,
EQQZ096W
PQ58622
EQQR674E
PQ58629
EQQY807E
PQ58860
EQQFAR5W,
EQQFAR7W,
EQQFJKBE,
EQQFJKGW
PQ61374
EQQZ227E
PQ61530
EQQX146E
PQ62074
EQQIC45W
PQ62783
EQQZ008E
PQ63058
EQQE056W
PQ63396
EQQZ228E
viii
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
|
||
|
||
|
||
|
http://techsupport.services.ibm.com/guides/handbook.html
-
Table
2.
(continued)
PQ63565
EQQE036I,
EQQE037I,
EQQE038I,
EQQE039I
PQ63594
EQQW531E
PQ63712
EQQIC06W
PQ65045
EQQW791W
PQ65470
EQQ3003E
PQ65556
EQQ0390E,
EQQ3120E,
EQQ3127I,
EQQ3105I,
EQQ3106I,
EQQ3107I
PQ65970
EQQM654I
PQ65995
EQQN111I,
EQQ3087I
PQ66373
EQQFARUW,
EQQFARWE,
EQQFARXE
PQ67699
EQQFA72E,
EQQFA73E,
EQQFA74E,
EQQFA75E,
EQQFA76E,
EQQFA77E,
EQQZ096W
PQ68074
EQQZ194W
PQ68608
EQQM655E,
EQQM656E
PQ68665
EQQE020W,
EQQM657I
PQ68825
EQQZ220W
PQ69047
EQQPH28I
PQ70507
EQQM208E
PQ71093
EQQL505E
Preface
ix
-
x
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
Tivoli
Workload
Scheduler
for
z/OS
messages
have
the
following
formats:
where:
EQQ
Means
that
the
message
was
issued
by
Tivoli
Workload
Scheduler
for
z/OS.
The
EQQ
prefix
is
used
for
all
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
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
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
Tivoli
Workload
Scheduler
for
z/OS
started
task
and
EQQFnnnC
Text
or
EQQFFnnC
Text
or
EQQnnnnC
Text
1
-
by
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
Tivoli
Workload
Scheduler
for
z/OS
message
printed
in
the
message
log
data
set
is:
where:
mm/dd
Is
the
current
date,
given
as
a
2-digit
month
number
and
a
2-digit
day-of-month
number.
For
example,
02/03
means
February
3.
HH.MM.SS
Is
the
current
time-of-day:
HH
Is
the
hour,
starting
from
midnight,
in
the
range
00–23.
MM
Is
the
minute
of
the
current
hour,
in
the
range
00–59.
SS
Is
the
second
of
the
current
minute,
in
the
range
00–59.
msgnum
Is
the
message
number
in
the
format
described
in
“Message
Format”
on
page
1.
TEXT
Is
the
message
text
in
uppercase.
An
example
of
messages
in
the
Tivoli
Workload
Scheduler
for
z/OS
message
log
follows:
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.
mm/dd
HH.MM.SS
msgnum
TEXT
...02/21
16.31.11
EQQZ005I
Tivoli
Workload
Scheduler
for
z/OS
SUBTASK
EVENT
WRITER
IS
BEING
STARTED
02/21
16.31.13
EQQZ005I
Tivoli
Workload
Scheduler
for
z/OS
SUBTASK
VTAM
I/O
TASK
IS
BEING
STARTED
02/21
16.31.14
EQQZ005I
Tivoli
Workload
Scheduler
for
z/OS
SUBTASK
JOB
SUBMIT
TASK
IS
BEING
STARTED
02/21
16.31.16
EQQZ005I
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
...
2
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
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
-
Chapter
2.
EQQATnn
Messages
EQQAT00I
THE
APPC
TRACKER
TASK
HAS
STARTED
Explanation:
The
APPC
tracker
task
has
started
successfully.
Tivoli
Workload
Scheduler
for
z/OS
starts
this
task
if
the
ROUTOPTS
initialization
statement
defines
one
or
more
APPC
destinations.
System
action:
Tivoli
Workload
Scheduler
for
z/OS
normal
processing
continues.
System
programmer
response:
None.
EQQAT01I
THE
APPC
TRACKER
TASK
HAS
ENDED
Explanation:
The
APPC
tracker
task
has
been
requested
to
stop
and
is
ending
normally.
System
action:
Tivoli
Workload
Scheduler
for
z/OS
normal
processing
continues.
System
programmer
response:
None.
EQQAT02E
THE
APPC
TRACKER
TASK
HAS
BEEN
CONTACTED
BY
AN
UNKNOWN
DESTINATION:
LU
Explanation:
The
APPC
tracker
task
has
recognized
an
inbound
attach
request
from
a
destination
that
is
not
defined
in
the
ROUTOPTS
initialization
statement.
System
action:
The
APPC
tracker
task
frees
all
resources
allocated
to
this
APPC
conversation.
The
partner
program
that
is
attempting
to
start
the
conversation
gets
a
failing
return
code
from
the
APPC
service
routine.
System
programmer
response:
If
the
APPC
tracker
task
should
support
the
destination
specified
in
this
message,
update
the
ROUTOPTS
initialization
statement
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT03E
A
QUEUE
ELEMENT
ON
THE
APPC
TRACKER
TASK
QUEUE
IS
NOT
RECOGNIZED:
ELEM
Explanation:
An
invalid
queue
element
has
been
found
on
the
APPC
tracker
task’s
work
queue.
System
action:
The
incorrect
queue
element
is
returned
to
the
APPC
tracker
task’s
free
queue
without
any
further
processing.
System
programmer
response:
Save
the
Tivoli
Workload
Scheduler
for
z/OS
message
log
data
set
containing
this
message
and
contact
Customer
Support.
EQQAT04E
THE
APPC
TRACKER
TASK
RECEIVED
INVALID
IDENTIFICATION
DATA
FROM
DESTINATION:
LU
Explanation:
The
initial
data
received
from
a
partner
APPC
program
is
not
valid.
System
action:
The
APPC
tracker
task
frees
all
resources
allocated
to
this
APPC
conversation.
The
partner
program
sending
incorrect
data
gets
a
failing
return
code
from
the
APPC
service
routine.
System
programmer
response:
Verify
that
the
correct
partner
program
has
been
started
on
the
remote
destination
and
that
the
program
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
EQQAT05I
A
CONVERSATION
WITH
AN
APPC
TRACKER
AT
DESTINATION
LU
HAS
ENDED.
SEND
RECORDS
WERE
TRANSMITTED,
RCV
RECORDS
WERE
RECEIVED
Explanation:
A
conversation
with
an
APPC
tracker
is
ending
normally.
System
action:
Tivoli
Workload
Scheduler
for
z/OS
normal
processing
continues.
System
programmer
response:
None.
EQQAT06E
THE
APPC
TRACKER
TASK
RECEIVED
UNRECOGNIZED
DATA
FROM
DESTINATION:
LU
Explanation:
Data
received
from
a
partner
APPC
program
is
not
valid.
System
action:
The
APPC
tracker
task
frees
all
resources
allocated
to
this
APPC
conversation.
The
partner
program
sending
incorrect
data
gets
a
failing
return
code
from
the
APPC
service
routine.
System
programmer
response:
Verify
that
the
correct
partner
program
has
been
started
on
the
remote
destination
and
that
the
program
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
EQQAT07E
NO
CONVERSATION
FOUND
FOR
OUTBOUND
DATA
ON
THE
APPC
TRACKER
TASK
QUEUE:
ELEM
Explanation:
A
queue
element
has
been
found
on
the
APPC
tracker
task’s
work
queue
which
is
not
addressed
to
any
currently
active
APPC
conversation.
5
-
System
action:
The
queue
element
is
returned
to
the
APPC
tracker
task’s
free
queue
without
any
further
processing.
System
programmer
response:
Save
the
Tivoli
Workload
Scheduler
for
z/OS
message
log
data
set
containing
this
message
and
contact
Customer
Support.
EQQAT08E
THE
APPC
TRACKER
TASK
CANNOT
START,
TRACKER
FEATURE
IS
NOT
INSTALLED
Explanation:
The
APPC
tracker
task
could
not
locate
a
required
load
module.
System
action:
The
APPC
tracker
task
is
terminated.
System
programmer
response:
If
the
APPC
tracker
feature
is
not
installed,
the
ROUTOPTS
initialization
statement
should
not
specify
the
APPC
keyword.
If
the
APPC
tracker
feature
is
installed,
make
sure
that
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem
can
access
corresponding
load
module
libraries.
After
making
the
appropriate
corrections,
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT09E
THE
APPC
TRACKER
TASK
RECEIVED
INVALID
IDENTIFICATION
DATA
FROM
DESTINATION:
LU.
VALIDATION
RETURN
CODE
IS
RC
Explanation:
The
initial
data
received
from
a
partner
APPC
program
is
not
valid.
System
action:
The
APPC
tracker
task
frees
all
resources
allocated
to
this
APPC
conversation.
The
partner
program
sending
incorrect
data
gets
a
failing
return
code
from
the
APPC
service
routine.
If
the
return
code
is
4,
correct
the
GMT
times
involved
using
the
information
in
message
EQQAT17W,
and
then
restart
the
partner
program.
Return
Code
Explanation
4
The
difference
between
the
host
system
GMT
value
and
the
tracker
system
GMT
value
is
greater
than
60
minutes.
This
message
is
followed
by
message
EQQAT17W,
which
shows
the
different
GMT
values.
8
The
identification
data
is
invalid
for
other
causes
to
be
investigated.
System
programmer
response:
Verify
that
the
correct
partner
program
has
been
started
on
the
remote
destination
and
that
the
program
is
at
a
supported
maintenance
level.
If
the
return
code
is
4,
correct
the
GMT
values
involved,
using
the
information
in
message
EQQAT17W.
After
making
corrections,
restart
the
partner
program.
EQQAT10E
SEND
TO
DESTINATION:
LU
FAILED
WITH
RETCODE
RC
IMMEDIATELY
Explanation:
The
APPC
tracker
task
received
an
immediate
nonzero
return
code
from
the
APPC
send
data
service
routine.
System
action:
The
APPC
tracker
task
terminates
this
APPC
conversation
and
frees
all
allocated
resources.
System
programmer
response:
Verify
that
the
partner
program
on
the
remote
destination
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
EQQAT11E
SEND
TO
DESTINATION:
LU
FAILED
WITH
RETCODE
RC
ASYNCHRONOUSLY
Explanation:
The
APPC
tracker
task
received
a
nonzero
return
code
from
the
APPC
send
data
service
routine.
System
action:
The
APPC
tracker
task
terminates
this
APPC
conversation
and
frees
all
allocated
resources.
System
programmer
response:
Verify
that
the
partner
program
on
the
remote
destination
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
EQQAT12E
RECEIVE
AND
WAIT
FROM
DESTINATION:
LU
FAILED
WITH
RETCODE
RC
IMMEDIATELY
Explanation:
The
APPC
tracker
task
received
an
immediate
nonzero
return
code
from
the
APPC
receive
and
wait
service
routine.
System
action:
The
APPC
tracker
task
terminates
this
APPC
conversation
and
frees
all
allocated
resources.
System
programmer
response:
Verify
that
the
partner
program
on
the
remote
destination
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
EQQAT13E
RECEIVE
AND
WAIT
FROM
DESTINATION:
LU
FAILED
WITH
RETCODE
RC
ASYNCHRONOUSLY
Explanation:
The
APPC
tracker
task
received
a
nonzero
return
code
from
the
APPC
receive
and
wait
service
routine.
System
action:
The
APPC
tracker
task
terminates
this
APPC
conversation
and
frees
all
allocated
resources.
System
programmer
response:
Verify
that
the
partner
program
on
the
remote
destination
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
6
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
-
EQQAT14E
IDLE
CONVERSATION
DELAY
ERROR
FOR
DESTINATION:
LU
Explanation:
The
APPC
tracker
task
received
send
permission
from
a
remote
partner
program
without
any
data
and
without
the
minimum
delay
required
for
an
idle
conversation.
System
action:
The
APPC
tracker
task
terminates
this
APPC
conversation
and
frees
all
allocated
resources.
System
programmer
response:
Verify
that
the
partner
program
on
the
remote
destination
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
EQQAT15E
PREPARE
TO
RECEIVE
FROM
DESTINATION:
LU
FAILED
WITH
RETCODE
RC
IMMEDIATELY
Explanation:
The
APPC
tracker
task
received
an
immediate
nonzero
return
code
from
the
APPC
prepare
to
receive
service
routine.
System
action:
The
APPC
tracker
task
terminates
this
APPC
conversation
and
frees
all
allocated
resources.
System
programmer
response:
Verify
that
the
partner
program
on
the
remote
destination
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
EQQAT16E
PREPARE
TO
RECEIVE
FROM
DESTINATION:
LU
FAILED
WITH
RETCODE
RC
ASYNCHRONOUSLY
Explanation:
The
APPC
tracker
task
received
a
nonzero
return
code
from
the
APPC
prepare
to
receive
service
routine.
System
action:
The
APPC
tracker
task
terminates
this
APPC
conversation
and
frees
all
allocated
resources.
System
programmer
response:
Verify
that
the
partner
program
on
the
remote
destination
is
at
a
supported
maintenance
level.
After
making
corrections,
restart
the
partner
program.
EQQAT17W
THE
APPC
TRACKER
TASK
DETECTED
AN
INVALID
DIFFERENCE
BETWEEN
THE
CONTROLLER
GMT
TIME
HOSTGMT
AND
THE
TRACKER
GMT
TIME
TRKGMT
Explanation:
This
message
follows
EQQAT09E.
It
shows
the
host
system
GMT
value
and
the
tracker
system
GMT
value.
The
host
system
GMT
value
may
have
been
adjusted
by
the
value
provided
in
the
GMTOFFSET
parameter
of
the
OPCOPTS
statement.
System
action:
None.
System
programmer
response:
Use
the
GMT
values
displayed
to
determine
which
system
has
an
incorrect
definition,
reset
the
GMT
value
where
necessary.
After
making
corrections,
restart
the
partner
program.
EQQAT21E
WRONG
NUMBER
OF
PERIODS
IN
THE
ADDR
VALUE,
VALUE
Explanation:
The
ADDR
keyword
of
the
APPCROUT
initialization
statement
must
specify
a
value
containing
one
period.
System
action:
Processing
of
the
current
APPCROUT
statement
terminates
with
a
nonzero
return
code.
This
causes
Tivoli
Workload
Scheduler
for
z/OS
initialization
to
fail.
System
programmer
response:
Either
remove
or
correct
the
APPCROUT
statement
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT22E
THE
PERIOD
IN
THE
ADDR
VALUE,
VALUE,
IS
INCORRECTLY
PLACED
Explanation:
The
ADDR
keyword
of
the
APPCROUT
initialization
statement
must
specify
a
value
containing
one
period,
and
that
period
cannot
be
placed
more
than
eight
characters
after
the
beginning
of
the
value
or
more
than
eight
characters
before
the
end
of
the
value.
System
action:
Processing
of
the
current
APPCROUT
statement
terminates
with
a
nonzero
return
code.
This
causes
Tivoli
Workload
Scheduler
for
z/OS
initialization
to
fail.
System
programmer
response:
Either
remove
or
correct
the
APPCROUT
statement
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT23E
THE
VALUE
OF
THE
ADDR
KEYWORD
IS
MISSING
OR
TOO
SHORT
Explanation:
The
ADDR
keyword
of
the
APPCROUT
initialization
statement
must
specify
a
value
that
is
not
less
than
three
characters
long.
System
action:
Processing
of
the
current
APPCROUT
statement
terminates
with
a
nonzero
return
code.
This
causes
Tivoli
Workload
Scheduler
for
z/OS
initialization
to
fail.
System
programmer
response:
Either
remove
or
correct
the
APPCROUT
statement
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT24E
THE
ADDR
KEYWORD
IS
MISSING
Explanation:
The
current
APPCROUT
initialization
statement
does
not
contain
an
ADDR
keyword.
System
action:
Processing
of
the
current
APPCROUT
statement
terminates
with
a
nonzero
return
code.
This
causes
Tivoli
Workload
Scheduler
for
z/OS
initialization
to
fail.
Chapter
2.
EQQATnn
Messages
7
-
System
programmer
response:
Either
remove
or
correct
the
APPCROUT
statement
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT25E
THE
WORKSTATIONS
KEYWORD
IS
MISSING
Explanation:
The
current
APPCROUT
initialization
statement
does
not
contain
a
WORKSTATIONS
keyword.
System
action:
Processing
of
the
current
APPCROUT
statement
terminates
with
a
nonzero
return
code.
This
causes
Tivoli
Workload
Scheduler
for
z/OS
initialization
to
fail.
System
programmer
response:
Either
remove
or
correct
the
APPCROUT
statement
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT26E
WORKSTATION
WSN
HAS
BEEN
SPECIFIED
MORE
THAN
ONCE
IN
A
WORKSTATIONS
KEYWORD.
THIS
IS
NOT
SUPPORTED
Explanation:
The
WORKSTATIONS
keyword
in
current
APPCROUT
initialization
statement
contains
a
workstation
name
that
has
already
been
specified
in
a
WORKSTATIONS
keyword.
This
is
a
duplicate
definition
that
is
not
supported.
System
action:
Processing
of
the
current
APPCROUT
statement
terminates
with
a
nonzero
return
code.
This
causes
Tivoli
Workload
Scheduler
for
z/OS
initialization
to
fail.
System
programmer
response:
Either
remove
or
correct
the
APPCROUT
statement
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT30E
APPC
KEYWORD
VALUE,
VAL1,
IS
TOO
LONG
(OR
MISSING)
Explanation:
A
workstation
destination
name
specified
as
a
value
of
the
APPC
keyword
of
the
ROUTOPTS
statement
is
incorrect.
The
destination
name
is
required
and
must
be
not
greater
than
eight
characters.
System
action:
Processing
of
the
APPC
keyword
continues.
Message
EQQAT34E
is
issued
when
all
destinations
have
been
processed.
System
programmer
response:
Either
remove
or
correct
the
invalid
destination
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT31E
APPC
KEYWORD
VALUE,
VAL2,
MUST
CONTAIN
EXACTLY
ONE
PERIOD
Explanation:
A
network
address
specified
as
a
value
of
the
APPC
keyword
of
the
ROUTOPTS
statement
is
incorrect.
The
network
address
is
required
and
must
be
specified
as
netid.netlu
where
the
netid
and
netlu
names
cannot
contain
periods.
System
action:
Processing
of
the
APPC
keyword
continues.
Message
EQQAT34E
is
issued
when
all
destinations
have
been
processed.
System
programmer
response:
Either
remove
or
correct
the
invalid
destination
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT32E
THE
PERIOD
IN
THE
APPC
KEYWORD
VALUE,
VAL2,
IS
INCORRECTLY
PLACED
Explanation:
A
network
address
specified
as
a
value
of
the
APPC
keyword
of
the
ROUTOPTS
statement
is
incorrect.
The
network
address
is
required
and
must
be
specified
as
netid.netlu
where
the
netid
and
netlu
names
cannot
be
greater
than
eight
characters.
System
action:
Processing
of
the
APPC
keyword
continues.
Message
EQQAT34E
is
issued
when
all
destinations
have
been
processed.
System
programmer
response:
Either
remove
or
correct
the
invalid
destination
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT33E
APPC
KEYWORD
VALUE,
VAL2,
IS
MISSING
OR
TOO
SHORT
Explanation:
A
network
address
specified
as
a
value
of
the
APPC
keyword
of
the
ROUTOPTS
statement
is
incorrect.
The
network
address
is
required
and
must
be
specified
as
netid.netlu
where
both
netid
and
netlu
are
required.
System
action:
Processing
of
the
APPC
keyword
continues.
Message
EQQAT34E
is
issued
when
all
destinations
have
been
processed.
System
programmer
response:
Either
remove
or
correct
the
invalid
destination
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
EQQAT34E
AT
LEAST
ONE
APPC
DESTINATION
IS
INCORRECTLY
DEFINED
Explanation:
The
APPC
keyword
of
the
ROUTOPTS
statement
contains
one
or
more
incorrectly
defined
APPC
destinations.
System
action:
Processing
of
the
current
ROUTOPTS
statement
terminates
with
a
nonzero
return
code.
This
causes
Tivoli
Workload
Scheduler
for
z/OS
initialization
to
fail.
System
programmer
response:
Review
earlier
error
messages
to
determine
the
incorrectly
defined
destination.
Either
remove
or
correct
the
invalid
destination
and
restart
the
Tivoli
Workload
Scheduler
for
z/OS
subsystem.
8
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
-
Chapter
3.
EQQAnnn
Messages
EQQA000E
YOU
ARE
NOT
AUTHORIZED
TO
ACCESS
THE
AD
DATABASE
Explanation:
You
have
attempted
to
access
the
application
description
(AD)
database,
but
you
are
not
authorized
to
access
it.
Or,
you
do
not
have
access
authority
to
a
minimum
of
one
of
the
following
Tivoli
Workload
Scheduler
for
z/OS
resources
that
are
used
together
with
the
AD
database:
the
calendar
database,
the
workstation
description
database,
or
in
some
cases,
the
long-term
plan
data
set.
System
action:
The
request
is
rejected.
User
response:
If
you
require
access,
contact
your
security
administrator.
EQQA002E
THIS
VERSION
OF
THE
APPLICATION
ALREADY
EXISTS
Explanation:
The
application
already
exists
with
the
valid-from
date
that
you
specified.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Specify
another
valid-from
date.
EQQA003E
SELECTED
PREDECESSOR
IS
NOT
EXTERNAL
Explanation:
The
predecessor
you
selected
is
not
external.
When
defining
an
external
dependency,
you
must
specify
the
application
ID
of
the
external
predecessor
before
selecting
to
describe
it.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Specify
the
application
ID
of
the
external
predecessor.
EQQA004E
NO
MATCHING
APPLICATION
DESCRIPTION(S)
FOUND
Explanation:
No
application
description
matched
the
generic
or
nongeneric
search
criteria
you
specified
to
generate
a
list
of
applications.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Retry
using
new
selection
criteria.
EQQA005E
NO
MATCHING
APPLICATION
DESCRIPTION
FOUND
Explanation:
You
selected
an
application
that
does
not
have
a
matching
application
description.
In
a
list
of
applications,
in
either
the
browse
or
list
function,
the
application
you
selected
was
not
found.
The
application
may
have
been
deleted
or
modified
after
the
list
of
application
entries
was
generated.
System
action:
The
request
is
rejected.
User
response:
Return
to
the
application
selection
criteria
panel
and
press
ENTER
to
generate
a
fresh
list
of
applications.
EQQA006I
NO
RUNCYCLES
FOUND
FOR
THIS
APPLICATION
Explanation:
You
have
attempted
to
display
the
run
cycles
of
an
application
for
which
no
run
cycles
have
been
specified.
System
action:
The
request
is
rejected.
User
response:
None.
EQQA009I
NO
PREDECESSORS
FOUND
FOR
THIS
OPERATION
Explanation:
You
have
attempted
to
display
the
predecessors
of
an
operation
for
which
no
predecessors
have
been
specified.
System
action:
The
request
is
rejected.
User
response:
None.
EQQA010E
INVALID
PARAMETER
INPUT
TO
MODULE
MOD
Explanation:
This
message
indicates
a
programming
error.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Contact
your
system
programmer.
System
programmer
response:
Contact
your
system
administrator.
EQQA011I
THE
APPLICATION
IS
CREATED
Explanation:
The
application
has
been
created
and
saved
in
the
application
description
database.
System
action:
None.
User
response:
None.
EQQA012I
THE
SELECTED
APPLICATION
IS
MODIFIED
Explanation:
The
selected
application
has
been
modified
and
saved
in
the
application
description
database.
System
action:
None.
9
-
User
response:
None.
EQQA013I
THE
SELECTED
APPLICATION
IS
COPIED
Explanation:
The
selected
application
has
been
copied
and
the
copy
has
been
saved
in
the
application
description
database.
System
action:
None.
User
response:
None.
EQQA014I
THE
SELECTED
APPLICATION
IS
DELETED
Explanation:
The
selected
application
has
been
deleted
from
the
application
description
database.
System
action:
None.
User
response:
None.
EQQA015E
THE
NUMBER
OF
INTERNAL
PREDECESSORS
IS
TOO
LARGE
Explanation:
You
specified
too
many
internal
predecessors.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Delete
one
or
more
internal
predecessors.
EQQA016E
THE
NUMBER
OF
EXTERNAL
PREDECESSORS
IS
TOO
LARGE
Explanation:
You
specified
too
many
external
predecessors.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Delete
one
or
more
external
predecessors.
EQQA017E
THE
NUMBER
OF
SPECIAL
RESOURCES
IS
TOO
LARGE
Explanation:
You
specified
too
many
special
resources.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Delete
one
or
more
special
resources.
EQQA018E
OP
OP
HAS
AN
EXTERNAL
PRED
WS
EWS,
WHICH
IS
NOT
FOUND
Explanation:
Operation
OP
has
an
external
predecessor
workstation
(EWS)
that
does
not
exist
in
the
workstation
description
database.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Enter
correct
data.
EQQA021I
NO
SPECIAL
RESOURCES
FOUND
FOR
THIS
OPERATION
Explanation:
You
have
attempted
to
display
the
special
resources
of
an
operation
for
which
no
special
resources
have
been
defined.
System
action:
None.
User
response:
None.
EQQA022E
THE
APPLICATION
STATUS
SPECIFIED
IS
NOT
VALID
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
Valid
application
statuses
you
can
specify
as
selection
criteria
are:
A
for
active,
P
for
pending,
or
blank
for
both
active
and
pending.
EQQA023E
PRIORITY
MUST
BE
A
NUMBER
FROM
1
-
9
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
EQQA024E
STATUS
MUST
BE
OCHCACT
OR
OCHCPEND
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
EQQA025E
INPUT
DATA
IN
FIELD
IS
REQUIRED
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
EQQA101E
THE
VARIABLE
TABLE
NAME
CONTAINS
AN
INVALID
CHARACTER
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
The
name
of
a
variable
table
contains
1
to
16
alphanumeric
characters,
where
the
first
character
is
alphabetic.
EQQA102E
AN
APPLICATION
WITH
THIS
ID
ALREADY
EXISTS
Explanation:
You
have
attempted
to
create
an
application,
but
the
application
ID
that
you
specified
already
exists
in
the
application
description
database.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Enter
a
unique
application
ID.
If
you
want
to
create
versions
of
an
already
existing
application,
you
should
use
the
copy
function.
10
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
-
EQQA103E
THE
APPLICATION
IS
BEING
UPDATED
BY
USER
USR
TRY
LATER
Explanation:
Another
user
is
currently
updating
the
application
you
want
to
update.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Try
to
update
the
application
later.
EQQA104E
THE
PERIOD
NAME
DOES
NOT
EXIST
IN
THE
CALENDAR
Explanation:
The
period
name
that
you
specified
is
not
defined
in
the
calendar
database.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Enter
an
existing
period
name,
or
use
the
Calendar
dialog
to
define
the
period
name.
EQQA105E
YOU
ARE
NOT
AUTHORIZED
TO
READ
THE
JCL
VARIABLE
TABLE
DATA
BASE
Explanation:
You
have
attempted
to
refer
to
a
JCL
variable
table.
To
do
this,
you
need
read
authority
to
the
JCL
variable
table
database.
System
action:
The
system
waits
for
you
to
respond.
User
response:
If
you
need
to
refer
to
JCL
variable
table
names,
contact
your
security
administrator.
EQQA106E
DEADLINE
PRECEDES
INPUT
ARRIVAL
TIME
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
The
deadline
must
be
later
than
the
input
arrival
time.
EQQA107E
WORK
STATION
DOES
NOT
EXIST
IN
WS
DESCRIPTION
DATA
BASE
Explanation:
The
workstation
name
that
you
specified
is
not
defined
in
the
workstation
description
database.
System
action:
The
system
waits
for
you
to
respond.
User
response:
Enter
an
existing
workstation
name
or
use
the
Work
Station
Description
dialog
to
define
the
workstation
name.
EQQA108W
WHEN
UPDATING
WS
NAME,
OPR,
EXT
AND
INT
ITEMS
MUST
ALL
BE
SELECTED
Explanation:
To
obtain
a
correct
result,
you
must
select
all
of:
OPR
Workstation
name
INT
Predecessor
ws
name
EXT
Predecessor
ws
name
This
does
not
prevent
you
from
updating
only
one
of
the
items.
System
action:
The
system
waits
for
you
to
continue.
User
response:
Select
all
three
items.
EQQA110E
JOBNAME
REQUIRED
FOR
JOB
SETUP,
PRINT,
OR
COMPUTER
WS
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
A
job
name
is
required
for
an
operation
at
a
job
setup,
print,
or
computer
workstation.
EQQA111E
YOU
HAVE
ENTERED
AN
INVALID
VALUE
IN
THE
ONE
OF
THE
WLM
FIELDS
Explanation:
In
the
WLM
CRITICAL
field,
the
only
valid
values
are
Y
(Yes)
and
N
(No).
In
the
WLM
POLICY
field,
the
only
valid
values
are:
L
Long
Duration.
The
job
is
assisted
if
it
runs
beyond
its
estimated
duration.
D
Deadline.
The
job
is
assisted
if
it
has
not
finished
when
its
deadline
time
is
reached.
S
Latest
Start
Time.
The
job
is
assisted
if
it
is
submitted
after
its
latest
start
time.
C
Conditional.
An
algorithm
calculates
whether
to
apply
the
Deadline
policy
or
the
Latest
Start
Time
policy.
’’
The
scheduler
WLM
will
eventually
use
the
policy
specified
in
OPCOPTS.
User
response:
Enter
valid
values
in
the
WLM
CRITICAL
and
POLICY
fields.
EQQA116E
DURATION
TIME
IS
NOT
SPECIFIED
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
EQQA117E
24.00
IS
NOT
ALLOWED
AS
INPUT
ARRIVAL
TIME
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
Valid
input
arrival
times
are
00.00
through
23.59.
EQQA118E
00.00
IS
NOT
ALLOWED
AS
DEADLINE
TIME
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
Valid
deadline
times
are
00.01
through
24.00.
Chapter
3.
EQQAnnn
Messages
11
-
EQQA119W
SPECIFIED
OPERATION
DEADLINE
EARLIER
THAN
APPLICATION
INPUT
ARRIVAL
Explanation:
Th
operation
deadline
that
you
specified
is
earlier
than
the
application
input
arrival
time
for
the
application.
This
does
not
prevent
you
from
saving
the
application
description
as
it
is.
System
action:
The
operation
deadline
is
accepted
and
the
system
waits
for
you
to
respond.
User
response:
Enter
END
to
save
the
application
description
or
make
the
deadline
and
the
input
arrival
time
consistent.
EQQA120I
SPECIFIED
OPERATION
INPUT
ARRIVAL
LATER
THAN
APPLICATION
DEADLINE
Explanation:
The
operation
input
arrival
time
that
you
specified
is
later
than
the
deadline
time
for
the
application.
This
does
not
prevent
you
from
saving
the
application
description
as
it
is.
System
action:
The
input
arrival
time
for
the
operation
is
accepted
and
the
system
waits
for
you
to
respond.
User
response:
Enter
END
to
save
the
application
description
or
make
the
operation
input
arrival
and
the
application
deadline
consistent.
EQQA121E
SPECIFIED
OPERATION
DEADLINE
EARLIER
THAN
OP
INPUT
ARRIVAL
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
The
deadline
time
must
be
later
than
the
input
arrival
time.
EQQA122I
SPECIFIED
APPLICATION
INPUT
ARRIVAL
LATER
THAN
AN
OP
INPUT
ARRIVAL
Explanation:
The
application
input
arrival
time
that
you
specified
is
later
than
an
operation
input
arrival
time
defined
in
the
OPER
table.
This
does
not
prevent
you
from
saving
the
application
description
as
it
is.
System
action:
The
input
arrival
time
for
the
application
is
accepted
and
the
system
waits
for
you
to
respond.
User
response:
Enter
END
to
save
the
application
description
or
make
the
input
arrival
times
consistent.
EQQA123I
SPECIFIED
OP
INPUT
ARRIVAL
EARLIER
THAN
APPLICATION
INPUT
ARRIVAL
Explanation:
The
operation
input
arrival
time
that
you
specified
is
earlier
than
the
input
arrival
time
for
the
application.
This
does
not
prevent
you
from
saving
the
application
description
as
it
is.
System
action:
The
input
arrival
time
for
the
operation
is
accepted
and
the
system
waits
for
you
to
respond.
User
response:
Enter
END
to
save
the
application
description
or
make
the
input
arrival
times
consistent.
EQQA124I
SPECIFIED
OP
DEADLINE
LATER
THAN
APPLICATION
DEADLINE
Explanation:
The
operation
deadline
time
that
you
specified
is
later
than
the
deadline
time
for
the
application.
This
does
not
prevent
you
from
saving
the
application
description
as
it
is.
System
action:
The
deadline
time
for
the
operation
is
accepted.
The
system
waits
for
you
to
respond.
User
response:
Enter
END
to
save
the
application
description
or
make
the
deadline
times
consistent.
EQQA125I
NO
APPLICATION
INPUT
ARRIVAL
TIME
SPECIFIED
YET
Explanation:
No
application
input
arrival
time
is
specified
for
this
application.
This
does
not
prevent
you
from
saving
the
application
description
as
it
is.
System
action:
The
times
specified
for
the
operation
are
accepted.
The
system
waits
for
you
to
respond.
User
response:
Enter
END
to
save
the
application
description,
or
make
the
deadline
times
consistent.
EQQA126E
SPECIFY
AT
LEAST
ONE
RUNDAY
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
EQQA127E
OUT-OF-EFFECT-FROM
DATE
PRECEDES
IN-EFFECT-FROM
DATE
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
The
out-of-effect-from
date
for
a
run
cycle
must
be
later
than
the
in-effect-from
date.
EQQA132I
IA
2400
IS
NOT
SUPPORTED,
CHANGED
TO
0000
THE
DAY
AFTER
Explanation:
The
occurrence
input
arrival
time
specified
is
out
of
the
prearranged
range.
Valid
input
arrival
times
are
00.00
through
23.59.
The
inout
has
therefore
been
converted
to
00.00
the
day
after.
System
action:
None
User
response:
None
12
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes
-
EQQA133I
DEADLINE
0000
IS
NOT
SUPPORTED,CHANGED
TO
2400
THE
DAY
BEFORE
Explanation:
The
occurrence
deadline
specified
is
out
of
the
prearranged
range.
Valid
deadline
times
are
00.01
through
24.00.
The
deadline
has
therefore
been
converted
to
24.00
the
day
before.
System
action:
None
User
response:
None
EQQA134E
SUPPRESS
IF
LATE
=
YES
ALLOWED
ONLY
WHEN
TIME
DEPENDENT
=
YES
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
The
SUPPRESS
IF
LATE
option
can
be
YES
only
when
the
TIME
DEPENDENT
option
is
specified
as
YES.
EQQA135E
THE
SMOOTHING
FACTOR
MUST
BE
A
NUMBER
0
-
999
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
EQQA136E
THE
FEEDBACK
LIMIT
MUST
BE
A
NUMBER
100
-
999
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
EQQA137E
DEADLINE
WTO
IS
NOT
DEFINED
OR
INVALID
Explanation:
Data
entry
error;
see
“Data
Entry
Errors”
on
page
2.
Valid
deadline
WTO
options
are
Y
for
Yes,
and
N
for
No.
EQQA138W
OPERATION
IA
OPIA
LESS
THAN
OCCURRENCE
IA
OCCIA
Explanation:
The
operation
arrival
date
is
earlier
than
the
occurrence.
This
is
accepted,
but
might
not
be
what
you
intend.
System
action:
None.
User
response:
None.
EQQA200E
OPERATION
NUMBER
MUST
BE
1
-
255
Explanation:
Data
entry
error;
see
“Data
Entry