Appendix A. MESSAGES
This appendix lists all messages generated by the CA MICS
Hardware and SCP Analyzer. Some messages are generated
during the processing of the control statements, while others
are caused by various conditions in the data found during the
processing. The messages are listed in ascending numerical
sequence and include the full text of the message, the type,
the reason for the message, appropriate user action, and
applicable references to documentation.
The following type codes are used to categorize the messages:
Information Designates a note that documents a CA MICS
option or potentially important feature in
the data.
Warning Designates a condition in either the date or
the control statements that does not affect
CA MICS Hardware and SCP Analyzer operation,
but that may lead to unexpected results.
Error Designates that a problem has been
encountered with a control statement that
will prevent a successful run of the
product. Execution is stopped after all
control statements are processed.
The message text often includes references to information
that is contained in a control statement or values of
permanent or temporary variables created during CA MICS
processing. In the description below, the message text
contains a word beginning with a percent sign (%), which
indicates that a value will be substituted into the text at
execution time. For example, message RMF00104 reads as
follows:
SHORT RECORD DROPPED:
SYSID: %SYSID ORGSYSID: %ORGSYSID
END TIME STAMP: %ENDTSCH
RECORD TYPE: %SMFRTYPE
A possible version of the printed message in the MICSLOG
might be:
SHORT RECORD DROPPED:
SYSID: SYS1 ORGSYSID: SYS1
END TIME STAMP: 10SEP90:15:00:00.00
RECORD TYPE: 78
+------------+
| RMF00100 |
+------------+
TEXT: First input timestamp this run %ENDTSCH from
system %ORGSYSID
TYPE: Information
REASON: The TIMESTAMP and SYSTEM ID shown in the message
are from the first valid record read by DYRMFFMT.
This identifies the starting point of the data
processed in the DAY020 step.
ACTION: None
REFERENCES: None
+------------+
| RMF00101 |
+------------+
TEXT: Unknown RMF version found in input data.
CA MICS will continue processing this data as
though it was from %RMFLEVEL.
RMF version encountered in data: %RMFVER
CA MICS highest known RMF version: %RMFLEVEL
TYPE: Warning
REASON: Data from an unknown version of RMF has been
read. It will be processed as though it were
from the latest known version.
ACTION: Contact CA Technical Support.
REFERENCES: None
+------------+
| RMF00102 |
+------------+
TEXT: Unexpected swap placement sections found in type
71 paging activity record:
SYSID: %SYSID ORGSYSID: %ORGSYSID End time
stamp: %ENDTSCH
TYPE: Information
REASON: A swap placement section for an undefined swap
reason was encountered in DAY020.
ACTION: Contact CA Technical Support.
REFERENCES: None
+------------+
| RMF00103 |
+------------+
TEXT: %WRK_FILE user exit dropped %WRK_SKIP obs.
TYPE: Information
REASON: The user-defined exit USRSfff caused a number of
records to be dropped from the fff file.
ACTION: None
REFERENCES: None
$SCOL
+------------+
| RMF00104 |
+------------+
TEXT: Short record dropped:
type=%SMFRTYPE, SYSID=%SYSID,
ORGSYSID=%ORGSYSID, time stamp=%ENDTSCH.
%MSGTEXT
TYPE: Warning
REASON: An error in writing the RMF records has caused a
short record. It will be ignored and processing
will continue.
ACTION: If this is a one-time occurrence, it is not
a matter of great concern. If it happens
repeatedly, you should investigate for possible
corruption of your SMF records.
REFERENCES: None
+------------+
| RMF00106 |
+------------+
TEXT: Obsolete RMF version found in input data.
CA MICS will not process records prior to the
lowest RMF version supported.
RMF version encountered in data: %RMFVER
Lowest supported RMF version: %RMFMNLVL
TYPE: Information
REASON: Data from an obsolete version of RMF has been
read. The data will be dropped.
ACTION: Remove the obsolete RMF records from the DAILY
processing.
REFERENCES: None
+------------+
| RMF00108 |
+------------+
TEXT: A truncated, malformatted or non-RMF record has
been detected in the input file before initial
checkpoint processing. MICSLOG messages showing
counts of records read, processed, and deleted
will be incorrect. RMF00109W message(s) will
follow for each bad record.
TYPE: Warning
REASON: CA MICS must be able to read the SYSID and
timestamp of each RMF input record in order to
begin checkpoint processing. CA MICS determined
that an input record was either from a non-RMF
source, or was too short to contain the SYSID or
timestamp.
This message is issued only for the first bad
record detected. Message RMF00109W is issued for
each bad record.
ACTION: Investigate source of damaged or non-RMF records.
REFERENCES: None
+------------+
| RMF00109 |
+------------+
TEXT: Invalid record count: %WEIRDREC Input file
relative record number: %_N_
TYPE: Warning
REASON: CA MICS issues this message each time it
encounters a record that is from a non-RMF source
or is too short to contain a SYSID or timestamp.
Also, see message RMF00108W.
ACTION: Investigate the source of the damaged or non-RMF
records.
REFERENCES: None
+------------+
| RMF00111 |
+------------+
TEXT: There are %MSGVAR Coupling Facility Cache Data
Sections than expected in a spanned 74_4 record.
Potential data corruption in HARCFH file for:
SYSPLEX: %SYSPLEX SYSNAME: %SYSNAME
SYSID: %SYSID CFYSYSNM: %CFYSYSNM
CFYCFNM: %CFYCFNM ENDTS: %ENDTSCH
TYPE: Warning
REASON: This message is issued if there is a mismatch
(%MSGVAR can take the values "more" or "less")
between the actual number of cache data sections
available in a continuation type 74 subtype 4
Coupling Facility record, and the total number of
sections expected for all cache structures
belonging to the original record.
The data will be processed but there is a
potential corruption in the HARCFH file for all
observations identified by the key sequence
reported in the message.
ACTION: Contact CA Technical Support.
REFERENCES: None
+------------+
| RMF00112 |
+------------+
TEXT: Some unsupported spanned SMF %SMFRTYPE subtype
%RCDSUBTP records were found in the input data.
TYPE: Warning
REASON: This message is issued if there are broken
records in the input data for which support has
not been validated yet. These are records that
required continuation records because the raw
data would not fit in a single 32 KB record. The
data will be processed as if they were standard
(not spanned) records.
ACTION: Contact CA Technical Support.
REFERENCES: None
+------------+
| RMF00113 |
+------------+
TEXT: Some SMF type 113 Hardware Instrumentation
Record(s) discarded because no suspend record(s)
available to perform delta processing
Record (normally one record per logical
SYSID Count processor assigned to LPAR)
----- ------
TYPE: Warning
REASON: This message appears if any SMF type 113 interval
records are encountered that required delta
processing, but there was no HARCMX suspend file
record available. The records are discarded.
This message should only be seen if SMF type 113
records for a particular LPAR are input into a
DAILY update DAY020 step for the first time, and
the first record encountered for a LPAR processor
was a HISINTYP='INTER' or 'LAST' record, meaning
that delta processing was required to determine
the true interval values.
The HARCMX file maintains suspend records to
allow delta processing to span DAILY update runs.
If this message appears, and the SMF type 113
data does not contain data from new LPARS,
investigation is warranted.
ACTION: Contact CA Technical Support.
REFERENCES: None
+------------+
| RMF00114 |
+------------+
TEXT: %BSYS %BCOUNT
TYPE: Warning
REASON: This message provides SYSID values and record
counts for message RMF00113.
ACTION: Refer to message RMF00113.
REFERENCES: None
+------------+
| RMF00115 |
+------------+
TEXT: Some SMF type 113 Hardware Instrumentation
Record(s) discarded because the delta processing
of the counter fields yielded negative values.
Record
SYSID Count
----- ------
TYPE: Warning
REASON: This message appears if, during the normal delta
processing that subtracts the counter value of
the previous interval record from the current
interval record counter value, resulted in a
negative value.
There is no way to determine if the problem was
due to a raw data field overflow, or because an
IPU was varied offline, then online again. The
true interval value cannot be determined, so the
IPU level record is discarded.
More details about the first 50 records deleted
can be found in the DAY020 SASLOG by searching
for the text string "RMF00115".
ACTION: This message should not be seen frequently, but
if it is, contact CA Technical Support.
REFERENCES: None
+------------+
| RMF00116 |
+------------+
TEXT: %BSYS %BCOUNT
TYPE: Warning
REASON: This message provides SYSID values and record
counts for message RMF00115.
ACTION: Refer to message RMF00115.
REFERENCES: None
+------------+
| RMF00125 |
+------------+
TEXT: HARPHY DAYS time span setting of Y is not allowed
HARPHY DAYS time span has been set to E.
TYPE: Warning
REASON: The HARPHY DAYS timespan setting must be 'E' in
order to invoke the #PHYDSUM routine. The HARPHY
DAYS timespan setting is set to 'E' by RMFCGEN
and processing continues.
ACTION: None
REFERENCES: None
+------------+
| RMF00126 |
+------------+
TEXT: DETAIL time span is not supported for HARPHY
and has been turned off.
TYPE: Warning
REASON: The HARPHY file does not support the DETAIL
timespan.
ACTION: None
REFERENCES: None
+------------+
| RMF00130 |
+------------+
TEXT: RMFCGEN file dependency check beginning.
TYPE: Information
REASON: RMFCGEN is starting to check file dependencies.
ACTION: None
REFERENCES: None
+------------+
| RMF00131 |
+------------+
TEXT: RMFCGEN file dependency check successful.
TYPE: Information
REASON: The Analyzer's file dependencies were met.
ACTION: None
REFERENCES: None
+------------+
| RMF00132 |
+------------+
TEXT: RMFCGEN file dependency not met:
%FD_FIL1 has been deactivated.
%FD_FIL2 is active but needs %FD_FIL1 also
active.
You must either activate %FD_FIL1 or
deactivate %FD_FIL2 before rerunning RMFCGEN.
TYPE: Error
REASON: In tailoring RMFGENIN, a file was deactivated
that is required for a file that is active.
ACTION: Either reactivate the required file or deactivate
the dependent file in RMFGENIN; then rerun
RMFCGEN.
REFERENCES: Section 10.1.6
+------------+
| RMF00133 |
+------------+
TEXT: RMFCGEN file dependency check error(s).
TYPE: Error
REASON: File dependencies were not met.
ACTION: Review the MICSLOG and correct the errors
reported. Rerun RMFCGEN.
REFERENCES: None
+------------+
| RMF00135 |
+------------+
TEXT: RMFCGEN file dependency not met:
PHY is active but requires both DVA and IPU to
be active, therefore, PHY has been turned off
in all time spans.
RMFCGEN processing will continue.
TYPE: Warning
REASON: File dependencies were not met.
ACTION: None
REFERENCES: None
+------------+
| RMF00210 |
+------------+
TEXT: Reporting environment:
CPU Model: %CPUMOD
MVS Level: %MVSLEVEL
RMF Version: %RMFVER
TYPE: Information
TYPE: Information
REASON: The CPU model, MVS level, and RMF version are
reported by the Hardware and SCP Analyzer.
ACTION: None
REFERENCES: None
+------------+
| RMF00220 |
+------------+
TEXT: File %FFF is not set to ESSENTIAL ALL.
Reports may contain missing or incomplete
values.
TYPE: Warning
REASON: A postprocessor report that is being run
requires the use of CA MICS file %FFF, which has
been defined with ESSENTIAL element options of
INITIAL or ONLY. The reports may contain missing
or incomplete values.
ACTION: For information on ESSENTIAL element options,
see the reference listed below.
REFERENCES: PIOM, Section 2.3.1.8
+------------+
| RMF00400 |
+------------+
TEXT: Validating PARMS member RMFOPS.
TYPE: Information
REASON: This message is generated at the start of the
validation of prefix.MICS.PARMS(RMFOPS) during
execution of RMFPGEN.
ACTION: None
REFERENCES: Section 7.3.1
+------------+
| RMF00401 |
+------------+
TEXT: %LINE
Keyword not recognized: %KEYWORD
TYPE: Error
REASON: An invalid keyword was encountered in the line
printed with the error message.
ACTION: Correct the invalid keyword and rerun RMFPGEN.
REFERENCES: Section 7.3
+------------+
| RMF00402 |
+------------+
TEXT: %LINE
SYSID is not 1 to 4 chars in length.
SYSID=%KEYWORD2
TYPE: Error
REASON: The SYSID specified was greater than four
characters in length in the RMFOPS OPTIONS or
DEFAULT statement.
ACTION: Correct the invalid SYSID in
prefix.MICS.PARMS(RMFOPS) and rerun RMFPGEN.
REFERENCES: Section 7.3.1
+------------+
| RMF00403 |
+------------+
TEXT: The maximum number of SYSIDs has been exceeded.
Contact CA Technical Support.
TYPE: Error
REASON: The number of unique SYSID specifications exceeds
the maximum allowed in the RMFOPS statements.
ACTION: Contact CA Technical Support.
REFERENCES: Section 7.3.1
+------------+
| RMF00404 |
+------------+
TEXT: %LINE
The trace option must be "NONE", "INTVL", or
"SET". "%VARX" is invalid.
TYPE: Error
REASON: The only option specified in an RMFOPS OPTIONS
statement must be NONE, INTVL, or SET. The
character string shown in the error message was
found instead.
ACTION: Correct the invalid OPTION specification in
prefix.MICS.PARMS(RMFOPS) and rerun RMFPGEN.
REFERENCES: Section 7.3.1
+------------+
| RMF00405 |
+------------+
TEXT: Required statement not found.
Statement type=OPTIONS
TYPE: Error
REASON: The RMFOPS member of the PARMS library must
contain at least one OPTIONS statement.
ACTION: Add the required OPTION statement to
prefix.MICS.PARMS(RMFOPS) and rerun RMFPGEN.
REFERENCES: Section 7.3.1
+------------+
| RMF00406 |
+------------+
TEXT: Error(s) were found in RMFOPS PARMs definition.
RMFPGEN aborted. Correct the error(s) and
rerun RMFPGEN.
TYPE: Error
REASON: At least one error was encountered during
validation of the RMFOPS member of the PARMS
library.
ACTION: Correct the errors listed in other messages in
the MICSLOG and rerun RMFPGEN.
REFERENCES: Section 7.3.1
+------------+
| RMF00407 |
+------------+
TEXT: RMFOPS validation completed successfully.
TYPE: Information
REASON: This message is generated at the successful
completion of the RMFOPS PARMS member validation
process.
ACTION: None
REFERENCES: Section 7.3.1
+------------+
| RMF00410 |
+------------+
TEXT: Validating PARMS member RMFPHYDE.
TYPE: Information
REASON: This message is generated at the start of the
validation of prefix.MICS.PARMS(RMFPHYDE) during
execution of RMFPGEN.
ACTION: None
REFERENCES: Section 7.3.1
+------------+
| RMF00411 |
+------------+
TEXT: A DEFAULT, CPC, DEV, or LDV statement must
precede user data element assignment statements.
RMFPHYDE statement in error:
%ERR_STMT
TYPE: Error
REASON: This message is generated when a user data
element is encountered that is not preceded by a
valid DEFAULT, CPC, DEV, or LDV statement.
ACTION: Reposition the statement in error so it follows
a DEFAULT, CPC, DEV, or LDV statement and rerun
RMFPGEN.
REFERENCES: Section 7.3.1
+------------+
| RMF00412 |
+------------+
TEXT: User data element assignment statements
must be specified in the form:
dataelem = value
RMFPHYDE statement in error:
%ERR_STMT
TYPE: Error
REASON: This message is generated when a user data
element assignment statement is incorrectly
specified.
ACTION: Correct the statement in error and rerun RMFPGEN.
REFERENCES: Section 7.3.1
+------------+
| RMF00413 |
+------------+
TEXT: Data element: %NF_VAR specified on data element
assignment statement was not found in RMFGENIN
for file HARPHY.
RMFPHYDE statement in error:
%ERR_STMT
TYPE: Error
REASON: This message is generated when a user data
element assignment statement's specified data
element was not present in RMFGENIN when the last
RMFCGEN was run.
ACTION: Correct the statement in error and rerun RMFPGEN.
REFERENCES: Section 7.3.1
+------------+
| RMF00414 |
+------------+
TEXT: Data element: %NF_VAR specified on data element
assignment statement was not assigned a numeric
value.
RMFPHYDE statement in error:
%ERR_STMT
TYPE: Error
REASON: This message is generated when a user data
element assignment statement's specified data
element is numeric, but the value specified is
numeric.
ACTION: Correct the statement in error and rerun RMFPGEN.
REFERENCES: Section 7.3.1
+------------+
| RMF00418 |
+------------+
TEXT: RMFPHYDE validation completed successfully.
TYPE: Information
REASON: This message is generated at the successful
completion of the RMFPHYDE PARMS member
validation process.
ACTION: None
REFERENCES: Section 7.3.1
+------------+
| RMF00419 |
+------------+
TEXT: GENERATION COMPLETED FOR $RMFPHY FORMAT.
TYPE: Information
REASON: This message is generated at the successful
creation of the $RMFPHY Format.
ACTION: None
REFERENCES: Section 7.3.1
+------------+
| RMF00420 |
+------------+
TEXT: RMFPGEN Internal error, array limit exceeded.
Contact CA Technical Support.
TYPE: Error
REASON: An internal logic error has occurred.
ACTION: Contact CA Technical Support.
REFERENCES: None
+------------+
| RMF00421 |
+------------+
TEXT: Existing prefix.MICS.PARMS(RMFPHYDE) member
found.
Its data will be combined with new data
detected in this run to create the new
prefix.MICS.PARMS(RMFPHYDU) member.'
TYPE: Information
REASON: This message is generated when an existing
prefix.MICS.PARMS(RMFPHYDE) is found.
ACTION: None
REFERENCES: None
+------------+
| RMF00422 |
+------------+
TEXT: prefix.MICS.PARMS(RMFPHYDU) member successfully
generated.
TYPE: Information
REASON: This message is generated at the successful
creation of the prefix.MICS.PARMS(RMFPHYDU)
member.
ACTION: None
REFERENCES: None
+------------+
| RMF99999 |
+------------+
TEXT: %MSGTEXT
TYPE: Information
REASON: Prints a line in the MICSLOG.
ACTION: None
REFERENCES: None
