Appendix A. MESSAGES
This appendix lists the messages generated by the TSO
Analyzer. The messages are printed on both the MICSLOG and
SASLOG data sets. When reviewing the output of a job, first
look at the MICSLOG data set because it will contain fewer
lines of information, thus making it easier to see whether or
not a job or job step completed as expected. If the MICSLOG
message does not provide enough information, consult this
appendix for more information about the message. If you
still need more information, consult the SASLOG to help debug
the problem.
The format of a MICSLOG message is
hh:mm:ss.hs cccnnnnns ttttttttttttttttttttttttttttttttttt
where:
hh:mm:ss.hs is the time that the message was issued.
cccnnnnns is the message identifier. The message
identifier consists of three parts:
ccc three letter component identifier
nnnnn the message number
s the severity identifier, where I is
an informational message, W indicates
a warning, and E indicates an error
ttt...ttt: is the message text. If the text spans more
than one line, the message identifier is
repeated.
The remainder of this appendix shows the MICSLOG messages
produced for the TSO Analyzer. In addition to the message
identifier and text, this section presents the reason for the
message, suggests actions to take to resolve the problem, and
refers you to additional sources of information to help you
understand the problem and its resolution.
+-----------------+
| T S O 0 0 0 9 7 |
+-----------------+
TEXT: __________________________________________________.
TYPE: Information
REASON: The text of this message will vary from program
to program and will contain general information
about the processing being done at that moment in
time. The information in the message should be
self-explanatory and should not require any
additional supporting documentation. This
message differs from TSO00098 and TSO00099, in
that it is used when the information is to be
written only on the MICSLOG.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 0 9 8 |
+-----------------+
TEXT: __________________________________________________.
TYPE: Information
REASON: The text of this message will vary from program
to program and will contain general information
about the processing being done at that moment in
time. The information in the message should be
self-explanatory and should not require any
additional supporting documentation. This
message differs from TSO00097 and TSO00099, in
that it is used when the information is to be
written only on the SASLOG.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 0 9 9 |
+-----------------+
TEXT: __________________________________________________.
TYPE: Information
REASON: The text of this message will vary from program
to program and will contain general information
about the processing being done at that moment in
time. The information in the message should be
self-explanatory and should not require any
additional supporting documentation. This
message differs from TSO00097 and TSO00098, in
that it is used when the information is to be
written to both the MICSLOG and SASLOG.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 1 0 0 |
+-----------------+
TEXT: FIRST INPUT TIMESTAMP THIS RUN=________ FROM SYSTEM
_________.
TYPE: Information
REASON: The TIMESTAMP and SYSTEM ID shown in the message
are from the first valid record. This identifies
the starting point of the data processed in the
DAY010 step.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 1 0 1 |
+-----------------+
TEXT: COMMAND RECORD NOT DEFINED IN GENLIB(TSOGENIN)
INPUTSOURCE STATEMENT.
TYPE: Error
REASON: The SMF Record Type of the TSO/MON Command
Records being input to this DAY010 update does
not match the Command Record type specified on
the INPUTSOURCE statement in the TSOGENIN member
of sharedprefix.MICS.GENLIB.
ACTION: Correct the specification of the SMF record type
number used for the TSO/MON Command Records in
sharedprefix.MICS.GENLIB(TSOGENIN). Then rerun
the DAY010 step.
REFERENCES: TSO Analyzer Guide, Section 7.2.4
+-----------------+
| T S O 0 0 1 0 2 |
+-----------------+
TEXT: SYSTEM RECORD NOT DEFINED IN GENLIB(TSOGENIN)
INPUTSOURCE STATEMENT.
TYPE: Error
REASON: The SMF Record Type of the TSO/MON System Records
being input to this DAY010 update does not match
the System Record type specified on the
INPUTSOURCE statement of the TSOGENIN member of
sharedprefix.MICS.GENLIB.
ACTION: Correct the specification of the SMF record type
number used for the TSO/MON System Records in
sharedprefix.MICS.GENLIB(TSOGENIN). Then rerun
the DAY010 step.
REFERENCES: TSO Analyzer Guide, Section 7.2.4
+-----------------+
| T S O 0 0 1 0 4 |
+-----------------+
TEXT: INVALID COMMAND OR SYSTEM RECORD
TYPE: Error
REASON: The SMF record type of the input record is not
one of the valid TSO/MON record types as
specified on the INPUTSOURCE statement in
sharedprefix.MICS.GENLIB(TSOGENIN).
ACTION: Verify the specification of the TSO/MON record
types on the INPUTSOURCE statement in
sharedprefix.MICS.GENLIB(TSOGENIN) and correct
them if necessary. Also verify that the correct
input file is being processed. Rerun the DAY010
update step after corrections have been made.
REFERENCES: TSO Analyzer Guide, Section 7.2.4
+-----------------+
| T S O 0 0 1 0 5 |
+-----------------+
TEXT: DATA PRIOR TO TSO/MON VERSION 5.0 NOT SUPPORTED
TYPE: Error
REASON: The TSO/MON input records were created using a
release of TSO/MON earlier than Release 5.0.
Data from TSO/MON releases earlier than Release
5.0 cannot be processed by CA MICS.
ACTION: Use TSO/MON input records created using TSO/MON
Release 5.0 or higher in the next DAY010 update.
REFERENCES: TSO Analyzer Guide, Section 1.6
+-----------------+
| T S O 0 0 1 0 7 |
+-----------------+
TEXT: USER DELETED ____ DRU OBSERVATIONS VIA USRSDRU EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRSDRU exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 1 0 8 |
+-----------------+
TEXT: USER DELETED ____ TSI OBSERVATIONS VIA USRSTSI EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRSTSI exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 1 0 9 |
+-----------------+
TEXT: USER DELETED ____ TSA OBSERVATIONS VIA USRSTSA EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRSTSA exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 1 1 0 |
+-----------------+
TEXT: THE TSMLINK LOAD DATA SET NAME IS -- ______________
TYPE: Information
REASON: This message identifies the TSO/MON load data set
containing the TSMPARMS routine, which is used to
find the Command Table used in the DAY010 update.
ACTION: Verify that the data set specified contains an up
to date version of TSMPARMS.
REFERENCES: None
+-----------------+
| T S O 0 0 1 1 1 |
+-----------------+
TEXT: THE TSO/MON COMMAND TABLE MEMBER NAME REQUESTED IS
-- ________
TYPE: Information
REASON: This message identifies the TSO/MON Command Table
member name to be used in the DAY010 update.
ACTION: Verify the table name. Unpredictable command
abbreviation translations can occur if you use an
obsolete or incorrect command table.
REFERENCES: None
+-----------------+
| T S O 0 0 1 1 2 |
+-----------------+
TEXT: ERROR ENCOUNTERED DURING OPEN OF TSMLINK
TYPE: Error
REASON: The data set specified in the TSMLINK DD
statement of the DAY010 update could not be
opened.
ACTION: If the TSO/MON load data set is not in your
normal library setup, you must specify a TSMLINK
DD statement that references a data set
containing a current version of the TSMPARMS
program.
REFERENCES: TSO Analyzer Guide, Section 7.3.2
+-----------------+
| T S O 0 0 1 1 3 |
+-----------------+
TEXT: THE TSO/MON COMMAND TABLE WAS FOUND IN DATA SET
TYPE: Information
REASON: This message identifies the data set containing
the TSO/MON Command Table used in the DAY010
update.
ACTION: Verify that the data set used was the correct
one. Use of an obsolete or incorrect command
table may cause unpredictable translation of
command abbreviations.
REFERENCES: None
+-----------------+
| T S O 0 0 1 1 9 |
+-----------------+
TEXT: TSO/MON COMMAND TABLE PROCESSING ENDED
TYPE: Information
REASON: This message indicates that the TSO/MON Command
Table was successfully located, opened,
processed, and closed in this DAY010 update.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 1 3 0 |
+-----------------+
TEXT: ERRORS FOUND ON INPUT PARAMETERS. CORRECT AND
RESUBMIT.
TYPE: Error
REASON: At least one error encountered during validation
of the TSOOPS member of the PARMS library.
ACTION: Correct the error(s) listed in other messages in
the MICSLOG and rerun TSOPGEN.
REFERENCES: None
+-----------------+
| T S O 0 0 2 0 0 |
+-----------------+
TEXT: USER DELETED ____ TSU OBSERVATIONS VIA USRSTSU EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRSTSU exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 2 0 1 |
+-----------------+
TEXT: USER DELETED ____ TSO OBSERVATIONS VIA USRSTSO EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRSTSO exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 2 0 2 |
+-----------------+
TEXT: USER DELETED ____ TSC OBSERVATIONS VIA USRSTSC EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRSTSC exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 2 0 3 |
+-----------------+
TEXT: USER DELETED ____ _BI OBSERVATIONS VIA USRS_BI EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRS_BI exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 2 0 4 |
+-----------------+
TEXT: USER DELETED ____ _BU OBSERVATIONS VIA USRS_BU EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRS_BU exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 2 0 5 |
+-----------------+
TEXT: USER DELETED ____ _BC OBSERVATIONS VIA USRS_BC EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRS_BC exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 2 0 6 |
+-----------------+
TEXT: USER DELETED ____ _BD OBSERVATIONS VIA USRS_BD EXIT
TYPE: Information
REASON: This is the number of observations that were
deleted by the user-specified instructions in the
USRS_BD exit.
ACTION: None
REFERENCES: None
+-----------------+
| T S O 0 0 5 0 0 |
+-----------------+
TEXT: DAYS TSO_TA INPUT/OUTPUT FILE STATISTICS
TYPE: Information
REASON: This is the first of several messages which list
the input/output observation counts for the
TSO_TA file created in this DAY010 update.
ACTION: None
REFERENCES: Messages TSO00500 to TSO00505 describe the
input/output statistics for the TSO_TA file,
which is inactive by default. If you
activate the file, messages TSO00500,
TSO00501, TSO00504, and TSO00505 will be
produced. Messages TSO00502 and TSO00503
will be produced only if observations are
deleted under the conditions described by
those messages.
You can use the totals shown in these
messages to account for all observations
processed to create the TSO_TA file:
TSO00502 TERMID missing deletes +
TSO00503 USER specified deletes =
TSO00504 total number of deletes
TSO00501 total observations read -
TSO00504 total number of deletes =
TSO00505 total TSO_TA observations kept
+-----------------+
| T S O 0 0 5 0 1 |
+-----------------+
TEXT: TOTAL TSOTSU OBSERVATIONS READ -------- _______
TYPE: Information
REASON: This messages shows the number of observations
read from the TSOTSU file that were used to
create observations in the TSO_TA file.
ACTION: None
REFERENCES: See the references for message TSO00500.
+-----------------+
| T S O 0 0 5 0 2 |
+-----------------+
TEXT: TERMID/LINETYPE MISSING, DELETE ------- _______
TYPE: Information
REASON: This message shows the number of observations
deleted from the TSO_TA file due to missing
termid and/or line type.
ACTION: None
REFERENCES: See the note in the REFERENCES section of
message TSO00500.
+-----------------+
| T S O 0 0 5 0 3 |
+-----------------+
TEXT: USER DELETED VIA USRS_TA EXIT --------- _______
TYPE: Information
REASON: This message shows the number of observations
that were deleted from the TSO_TA file due to
user request.
ACTION: None
REFERENCES: See the note in the REFERENCES section of
message TSO00500.
+-----------------+
| T S O 0 0 5 0 4 |
+-----------------+
TEXT: TOTAL TSO_TA OBSERVATIONS DELETED ----- _______
TYPE: Information
REASON: This message shows the total number of
observations that were deleted from the TSO_TA
file.
ACTION: None
REFERENCES: See the note in the REFERENCES section of
message TSO00500.
+-----------------+
| T S O 0 0 5 0 5 |
+-----------------+
TEXT: TOTAL TSO_TA OBSERVATIONS KEPT -------- _______
TYPE: Information
REASON: This message shows the number of observations
that were written to the TSO_TA file.
ACTION: None
REFERENCES: See the note in the REFERENCES section of
message TSO00500.
+-----------------+
| T S O 0 0 6 0 0 |
+-----------------+
TEXT: ERROR ENCOUNTERED DURING LOAD OF TSO/MON COMMAND
TABLE -- RETURN CODE IS ___
TYPE: Error
REASON: An error occurred while loading the TSO/MON
Command Table into memory.
ACTION: Notify the TSO/MON System Administrator.
REFERENCES: None
+-----------------+
| T S O 0 0 6 0 4 |
+-----------------+
TEXT: TSMPARMS DD STATEMENT IS MISSING
TYPE: Error
REASON: The TSMPARMS DD statement was not present in the
JCL for the DAY010 update. Note: TSMPARMS is
required to locate the Command Table.
ACTION: Include a TSMPARMS DD statement that references a
data set that contains a valid TSO/MON Command
Table.
REFERENCES: TSO Analyzer Guide, Section 7.3.2
+-----------------+
| T S O 0 0 6 0 8 |
+-----------------+
TEXT: ERROR ENCOUNTERED DURING OPEN OF TSMPARMS
TYPE: Error
REASON: The data set specified in the TSMPARMS DD
statement of the DAY010 update could not be
opened.
ACTION: Include a TSMPARMS DD statement that references a
data set containing a valid TSO/MON Command
Table.
REFERENCES: TSO Analyzer Guide, Section 7.3.2
+-----------------+
| T S O 0 0 6 1 2 |
+-----------------+
TEXT: COMMAND TABLE (________) NOT FOUND IN TSMPARMS
TYPE: Error
REASON: The data set specified in the TSMPARMS DD
statement of the DAY010 update step did not
contain the requested Command Table.
ACTION: Check with your TSO/MON System Administrator to
verify that you are using the proper TSMPARMS
data set and/or Command Table suffix number.
REFERENCES: TSO Analyzer Guide, Section 7.3.2
+-----------------+
| T S O 0 0 6 1 6 |
+-----------------+
TEXT: SYNTAX ERROR WHILE PARSING THE TSO/MON COMMAND
TABLE
TYPE: Error
REASON: The TSO/MON Command Table specified contains
syntax errors.
ACTION: Ensure that you have specified the correct
Command Table suffix number. If correct, notify
the TSO/MON System Administrator.
REFERENCES: TSO Analyzer Guide, Section 7.3.2
+-----------------+
| T S O 0 0 6 2 0 |
+-----------------+
TEXT: GETMAIN FAILURE WHILE PROCESSING THE TSO/MON
COMMAND TABLE
TYPE: Error
REASON: The TSO/MON TSMPARMS utility program used to load
the Command Table failed to obtain memory to hold
the table.
ACTION: Increase the region size parameter on the DAY010
step and restart the DAILY job.
REFERENCES: None
+-----------------+
| T S O 0 0 6 2 4 |
+-----------------+
TEXT: TSMCMD CALL PARAMETER LIST IS INVALID
TYPE: Error
REASON: One of the variables needed in the TSMCMD CALL
statement is invalid. It may be missing, the
wrong length, not a character element, or in the
wrong order.
ACTION: Contact your CA MICS System Administrator.
REFERENCES: None
+-----------------+
| T S O 0 0 6 2 8 |
+-----------------+
TEXT: COMMAND ABBREVIATION (__) NOT FOUND IN COMMAND
TABLE
TYPE: Information
REASON: The command abbreviation could not be found in
the TSO/MON Command Table. A maximum of 25
messages will be shown. At termination, another
message will be shown with the total number of
command abbreviations not found.
ACTION: The command name is set to *UNKNOWN. Check to
see if you are using the same Command Table being
used by TSO/MON. Notify the TSO/MON System
Administrator.
REFERENCES: None
