This manual explains all the error, warning, and information messages, as well as
the user abend codes and reason codes, that TME 10 OPC issues.
The messages are listed in alphanumeric order by message identifier. To help you
find messages, the range of messages on a particular page is shown at the top of
the page.
Message Format
TME 10 OPC messages have the following formats:
EQQ
FnnnC Text
or EQQ
FFnnC Text
or EQQ
nnnnC Text
where:
EQQ Means that the message was issued by TME 10 OPC. The
EQQ prefix is used for all TME 10 OPC messages.
F
or
FF
Identifies the function that issued the message.
nn
,
nnn
, or
nnnn
Is the message number
C
Is the message severity code, with one of these values:
IInformation message. Processing continues and, in
almost all cases, no action by the user is required.
WWarning message. Processing continues and, in most
cases, no action by the user is required.
EError 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:
In the “long message” area on an Interactive System Productivity Facility (ISPF)
panel. This message is displayed if you enter HELP after a message is issued
in the “short message” area on the panel. The ISPF long message area is
normally the third line on the ISPF panel. All TME 10 OPC dialog messages
that are presented in this area have mixed-case text.
As one or more records in the TME 10 OPC message-log dataset. The
message log is defined by the EQQMLOG DD statement. The message log is
used by the TME 10 OPC started task and by TME 10 OPC's own batch jobs.
Any message in the message log can also be displayed as a write-to-operator
message.
Copyright IBM Corp. 1991, 1998 1