Appendix A. MESSAGES
This appendix lists the messages generated by the CA MICS
Analyzer Option for DB2. Some messages are printed on both
the MICSLOG and SAS log 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 a job or job step completed as
expected. If the MICSLOG message does not provide enough i
information, see this appendix for more information. 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. If you still need more
information, see the SAS log to help debug the problem.
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 Analyzer Option for DB2 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 DB200037 reads as
follows:
>>>>> INPUT PROCESSING ERROR
DB2 VERSION %XREL IS NOT SUPPORTED. INPUT RECORD WITH
DB2ID = %DB2ID AND END TIME STAMP = %XENDTS
HAS BEEN REJECTED.
A possible version of the printed message in the MICSLOG
might be:
>>>>> INPUT PROCESSING ERROR
DB2 VERSION 9.5 IS NOT SUPPORTED. INPUT RECORD WITH
DB2ID = D95A AND END TIME STAMP = 29SEP04:15:47:35.00
HAS BEEN REJECTED.
+------------+
| DB200001 |
+------------+
TEXT: >>>>> FIRST INPUT TIMESTAMP THIS RUN=%XENDTS FROM
SYSTEM %ORGSYSID.
TYPE: Information
REASON: List the first input timestamp.
ACTION: None
REFERENCES: None
+------------+
| DB200002 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - PRODUCT SECTION %QWS00PSN
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Product sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200003 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - ADDRESS SPACE SECTION %QWS00R1N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Address Space sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200004 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - INSTRUMENTATION SECTION %QWS00R2N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Instrumentation sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200005 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - IFCID SECTION %QWS00R3N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of IFCID sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200006 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - SYSTEM SERVICES SECTION %QWS00R4N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of System Services sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200007 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - COMMAND SECTION %QWS00R5N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Command sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200008 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - LATCH MANAGER SECTION %QWS00R7N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Latch Manager sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200009 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - RECORD AGENT SECTION %QWS00R8N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Record Agent sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200010 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - STORAGE MANAGER SECTION %QWS00R9N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Storage Manager sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200011 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - TRACE SECTION %QWS00RAN
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Trace sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200012 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - LOG MANAGER SECTION %QWS00RBN
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Log Manager sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200013 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - PRODUCT SECTION %QWS10PSN
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Product sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200014 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - SQL STATEMENT SECTION
%QWS10R1N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of SQL Statement sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200015 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - RECORD BIND SECTION %QWS10R2N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Record Bind sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200016 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - BUFFER MANAGER SECTION
%QWS10R3N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Buffer Manager sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200017 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - DATA MANAGER SECTION %QWS10R4N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Data Manager sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200018 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
ACCOUNTING RECORD - PRODUCT SECTION %QWA01PSN
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Product sections.
ACTION: Verify that the SMF Type 101 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200019 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
ACCOUNTING RECORD - INSTRUMENTATION SECTION
%QWA01R1N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Instrumentation sections.
ACTION: Verify that the SMF Type 101 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200020 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
ACCOUNTING RECORD - SQL STATEMENT SECTION
%QWA01R2N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of SQL Statement sections.
ACTION: Verify that the SMF Type 101 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200021 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
ACCOUNTING RECORD - BUFFER MANAGER SECTION
%QWA01R3N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Buffer Manager sections.
ACTION: Verify that the SMF Type 101 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200022 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
ACCOUNTING RECORD - RECORD LOCK SECTION %QWA01R4N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Record Lock sections.
ACTION: Verify that the SMF Type 101 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200023 |
+------------+
TEXT: >>>>> LAST INPUT TIMESTAMP THIS RUN=%LASTTME FROM
SYSTEM %ORGSYSID
TYPE: Information
REASON: List the last input timestamp.
ACTION: None
REFERENCES: None
+------------+
| DB200024 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - IFC CHECKPOINT SECTION %QWS00R6N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of IFC Checkpoint sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200025 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - RECORD LOCK SECTION %QWS10R5N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of Record Lock sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200026 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - EDM SECTION %QWS10R6N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of EDM sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200027 |
+------------+
TEXT: >>>>> THE FIRST DB2DSY RECORD PROCESSED FOR DB2ID
= %DB2ID END TIME STAMP = %XENDTS HAD A SEQUENCE
NUMBER OF %DSYISEQ. THIS OBSERVATION WILL BE
WRITTEN WITH MISSING VALUES >>>>>
TYPE: Information
REASON: The first value for DSYISEQ is not 1.
ACTION: Verify that SMF records are not missing.
REFERENCES: None
+------------+
| DB200028 |
+------------+
TEXT: >>>>> THE PRIOR DB2DSY RECORD PROCESSED FROM
DB2ID = %LAGDB2ID WITH AN END TIME STAMP =
%XLAGENDT HAD A %SEQDIF INTERVAL DIFFERENCE FROM
THE CURRENT RECORD BEING PROCESSED DB2ID = %DB2ID
END TIME STAMP = %XENDTS. THIS RECORD WILL BE
WRITTEN AS AN ACCUMULATED OBSERVATION IN THE
DB2DSY FILE.
TYPE: Information
REASON: There is a difference between the current
sequence number DSYISEQ and the prior sequence
number LAGISEQ that is greater than 1.
ACTION: Verify that SMF records are not missing.
REFERENCES: None
+------------+
| DB200029 |
+------------+
TEXT: >>>>> MISSING DB2DSY DATA AFTER DB2 SYSTEM
RESTART. THE CURRENT RECORD DB2ID = %DB2ID END
TIME STAMP = %XENDTS WILL BE WRITTEN AS AN
ACCUMULATED OBSERVATION.
TYPE: Information
REASON: SMF data is missing after a DB2 subsystem
restart.
ACTION: Verify that SMF records are not missing.
REFERENCES: None
+------------+
| DB200030 |
+------------+
TEXT: >>>>> THERE IS MORE THAN A ONE DAY DIFFERENCE
BETWEEN THE PRIOR DB2DSY RECORD PROCESSED DB2ID =
%LAGDB2ID END TIME STAMP = %XLAGENDT AND THE
CURRENT RECORD BEING PROCESSED DB2ID = %DB2ID END
TIME STAMP = %XENDTS. THIS OBSERVATION WILL BE
WRITTEN WITH MISSING VALUES >>>>>
TYPE: Information
REASON: There is more than a one-day difference between
the end timestamps of the current and prior
records.
ACTION: Verify that SMF records are not missing.
REFERENCES: None
+------------+
| DB200031 |
+------------+
TEXT: >>>>> THE FIRST DB2DSD RECORD PROCESSED FOR DB2ID
= %DB2ID END TIME STAMP = %XENDTS HAD A SEQUENCE
NUMBER OF %DB2ISEQ. THIS OBSERVATION WILL BE
WRITTEN WITH MISSING VALUES >>>>>
TYPE: Information
REASON: The first value for DSDISEQ is not 1.
ACTION: Verify that SMF records are not missing.
REFERENCES: None
+------------+
| DB200032 |
+------------+
TEXT: >>>>> THE PRIOR DB2DSD RECORD PROCESSED FROM
DB2ID = %LAGDB2ID WITH AN END TIME STAMP =
%XLAGENDT HAD A %SEQDIF INTERVAL DIFFERENCE FROM
THE CURRENT RECORD BEING PROCESSED DB2ID = %DB2ID
END TIME STAMP =%XENDTS. THIS RECORD WILL BE
WRITTEN AS AN ACCUMULATED OBSERVATION IN THE
DB2DSD FILE
TYPE: Information
REASON: There is a difference between the current
sequence number DSDISEQ and the prior sequence
number LAGISEQ that is greater than 1.
ACTION: Verify that SMF records are not missing.
REFERENCES: None
+------------+
| DB200033 |
+------------+
TEXT: >>>>> MISSING DB2DSD DATA AFTER DB2 SYSTEM
RESTART. THE CURRENT RECORD DB2ID = %DB2ID END
TIME STAMP = %XENDTS WILL BE WRITTEN AS AN
ACCUMULATED OBSERVATION
TYPE: Information
REASON: SMF data is missing after a DB2 subsystem
restart.
ACTION: Verify that SMF records are not missing.
REFERENCES: None
+------------+
| DB200034 |
+------------+
TEXT: >>>>> THERE IS MORE THAN A ONE DAY DIFFERENCE
BETWEEN THE PRIOR DB2DSD RECORD PROCESSED DB2ID =
%LAGDB2ID END TIME STAMP = %XLAGENDT AND THE
CURRENT RECORD BEING PROCESSED DB2ID = %DB2ID END
TIME STAMP = %XENDTS. THIS OBSERVATION WILL BE
WRITTEN WITH MISSING VALUES >>>>>
TYPE: Information
REASON: There is more than a one-day difference between
the end timestamps of the current and prior
records.
ACTION: Verify that SMF records are not missing.
REFERENCES: None
+------------+
| DB200035 |
+------------+
TEXT: >>>>> THE NEW START RECORD FOR DB2DDY IS FOR
MVSID: %SYSID
DB2ID: %DB2ID
LOCATION: %DB2RLOCN
END TIME STAMP: %XENDTS
SEQUENCE #: %DB2ISEQ
THIS OBSERVATION WILL BE THE NEW BASE FOR
CALCULATING ALL STATISTICS FOR THIS LOCATION
TYPE: Information
REASON: Identifies the start record for this location.
ACTION: None
REFERENCES: None
+------------+
| DB200036 |
+------------+
TEXT: >>>>> SEQUENCE ERROR FOR PRIOR DB2DDY RECORD
LAST DB2ID: %LAGDB2ID
LAST LOCATION: %LAGRLOCN
END TIME STAMP: %XLAGENDT
LAST SEQUENCE#: %LAGISEQ INDICATING %SEQDIF
STATISTICS RECORD(S) MAY BE MISSING.
NEW SEQUENCE#: %DB2ISEQ
TYPE: Information
REASON: Some Type 100 SMF records are missing.
ACTION: Determine the cause for the missing records.
REFERENCES: None
+------------+
| DB200037 |
+------------+
TEXT: >>>>> INPUT PROCESSING ERROR
DB2 VERSION %XREL IS NOT SUPPORTED. INPUT RECORD
WITH DB2ID = %DB2ID AND END TIME STAMP = %XENDTS
HAS BEEN REJECTED.
TYPE: Error
REASON: SMF records from an unsupported release of DB2
have been encountered.
ACTION: Verify that SMF data being input is from a
supported DB2 release.
REFERENCES: None
+------------+
| DB200038 |
+------------+
TEXT: %INSMFOL SKIPPED SMF RECORDS FROM UNSUPPORTED DB2
RELEASES.
TYPE: Warning
REASON: SMF records from an unsupported release of DB2
have been encountered and skipped.
ACTION: Verify that SMF data being input is from a
supported DB2 release.
REFERENCES: None
+------------+
| DB200039 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
SYSTEM RECORD - DDF SYSTEM STATISTICS SECTION
%QWS00RCN
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of DDF System Statistics data
sections
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200040 |
+------------+
TEXT: NOTE: EITHER THE DSD OR THE DSY FILE IS TURNED
OFF IN THE DAYS TIMESPAN. YOU CANNOT PRODUCE THE
CALENDAR REPORT UNLESS BOTH FILES ARE ACTIVE IN
THE DAYS TIMESPAN.
TYPE: Warning
REASON: The Calendar Report has been requested but the
DB2DSD and DB2DSY files are not active in the
DAYS timespan.
ACTION: Verify that the DB2DSY and DB2DSD files are
active in the DAYS timespan.
REFERENCES: None
+------------+
| DB200041 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - BUFFER MANAGER DATA SHARING
SECTION %QWS10R7N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of group buffer pool sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200042 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
DATA BASE RECORD - SERVICE CONTROLLER DATA
SHARING SECTION %QWS10R8N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of global locking sections.
ACTION: Verify that the SMF Type 100 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200043 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
ACCOUNTING RECORD - BUFFER MANAGER DATA SHARING
SECTION %QWA01R9N
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of buffer manager data sharing
sections.
ACTION: Verify that the SMF Type 101 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200044 |
+------------+
TEXT: !!!!! UNANTICIPATED SECTION COUNT !!!!!
ACCOUNTING RECORD - GLOBAL LOCKING DATA SHARING
SECTION %QWA01RAN
!!!!! UNANTICIPATED SECTION COUNT
TYPE: Error
REASON: Incorrect number of global locking data sharing
sections.
ACTION: Verify that the SMF Type 101 records being input
contain only DB2 data.
REFERENCES: None
+------------+
| DB200049 |
+------------+
TEXT: %WEIRDREC INVALID (NO-HEADER) RECORDS DROPPED
TYPE: Warning
REASON: Some SMF records do not have enough sections to
be processed by CA MICS.
ACTION: No action is needed. CA MICS discards records
that have insufficient data.
REFERENCES: None
+------------+
| DB200050 |
+------------+
TEXT: UNICODE TO EBCDIC TRANSLATION FAILED:
INSUFFICIENT SAS LEVEL
SYSID = %U_SYSID; DB2ID = %U_DB2ID; VARIABLE =
%U_VAR(%U_CNT TIMES).
TYPE: Warning
REASON: During the processing of DB2 Version 8 Release 1
or higher data, the CA MICS Analyzer Option
for DB2 could
not perform Unicode to EBCDIC character
translation because it is not executing at the
minimum SAS 8.02 maintenance level. This message
displays the number of times this condition
occurred for each SYSID, DB2ID, and affected data
element combination.
ACTION: The data element %U_VAR will contain unprintable
characters. Verify that the CA MICS Analyzer
Option for DB2 executes at SAS 8.02 or higher
maintenance level.
REFERENCES: None
+------------+
| DB200051 |
+------------+
TEXT: %CSRERREC RECORDS DROPPED DUE TO CSRCESRV
EXPANSION FAILURE.
TYPE: Warning
REASON: During the processing of DB2 Version 10 Release 1
or higher data, compressed data was detected,
but the call to the CSRCESRV EXPAND function
resulted in a non-zero return code.
ACTION: CA MICS discards compressed records that cannot be
expanded.
REFERENCES: None
+------------+
| DB200100 |
+------------+
TEXT: STARTING DELTA PROCESSING FOR: %FILENAME
TYPE: Information
REASON: The delta calculations for the %FILENAME data
elements have been initiated.
ACTION: None
REFERENCES: None
+------------+
| DB200102 |
+------------+
TEXT: SUSPEND RECORD DELETED DUE TO AGE: SYSID=%SYSID;
DB2ID=%DB2ID; ENDTS=%ENDTS; DB2SUSCT=%DB2SUSCT
TYPE: Information
REASON: Suspend records are deleted from the suspend file
for DB2IDs not encountered for 10 days. Suspend
records hold the values last encountered for a
DB2ID in the DAILY update and are used to
initialize the lag variables for delta
calculations during the next DAILY run. DB2IDs
not encountered for 10 days are considered
decommissioned.
ACTION: None
REFERENCES: None
+------------+
| DB200104 |
+------------+
TEXT: ISEQUENCE RESET: SYSID=%SYSID; DB2ID=%DB2ID;
DB2ISEQ=%DB2ISEQ; ENDTS=%ENDTS
TYPE: Information
REASON: The instrumentation sequence value was 1. The
DB2ID was most likely terminated and restarted.
Lag values are reset for delta calculations.
ACTION: None
REFERENCES: None
+------------+
| DB200106 |
+------------+
TEXT: NO SUSPEND RECORD FOR: SYSID=%SYSID;
DB2ID=%DB2ID; ENDTS=%ENDTS DB2ISEQ=%DB2ISEQ
TYPE: Information
REASON: No suspend record was found to initialize lag
variables for delta calculations. The DB2ID is
probably new. Delta processing will be skipped
for the first record.
ACTION: None
REFERENCES: None
+------------+
| DB200108 |
+------------+
TEXT: OUT OF SEQUENCE: SYSID=%SYSID; DB2ID=%DB2ID;
ENDTS=%ENDTS; DB2ISEQ=%DB2ISEQ; LAGISEQ=%LAGISEQ;
FILE00=%FILE00; SUSPEND=%SUSPEND
TYPE: Warning
REASON: An instrumentation sequence value was less than
the previous value. Normally, the
instrumentation sequence values increment by 1
from record to record. No delta processing can
take place. Lags values are reloaded.
ACTION: If this is a frequent problem, contact the DB2
administrator.
REFERENCES: None
+------------+
| DB200109 |
+------------+
TEXT: DUPLICATE ISEQ: SYSID=%SYSID; DB2ID=%DB2ID;
ENDTS=%ENDTS; DB2ISEQ=%DB2ISEQ; LAGISEQ=%LAGISEQ;
FILE00=%FILE00; SUSPEND=%SUSPEND
TYPE: Warning
REASON: The same instrumentation sequence value was found
on consecutive records. However, the end
timestamp was higher than the previous record.
Delta processing continues. Following are some
possible causes:
o Some other DB2 monitor is recording DB2
performance data to SMF.
o A performance trace was started that
recorded additional records to SMF.
ACTION: Alert the DB2 administrator of this condition.
REFERENCES: None
+------------+
| DB200110 |
+------------+
TEXT: MORE THAN ONE DAY EXISTS BETWEEN CURRENT
AND PREVIOUS OBSERVATIONS:
SYSID=%SYSID; DB2ID=%DB2ID; ENDTS=%XENDTS
LAGENDTS=%XLAGTS; FILE00=%FILE00
SUSPEND=%SUSPEND DB2RLOCN=%DB2RLOCN
TYPE: Warning
REASON: The difference between ENDTS on the current
record and the previous record is greater than 24
hours.
ACTION: Determine if this gap in data is correct or if
data was missing from SMF. Data will not exist
unless the DB2 Address Space was active (up and
running) and recording to SMF. If data was
missing, but is available, you may want to
restore the unit database and rerun the daily
process with all the input data.
REFERENCES: None
+------------+
| DB200111 |
+------------+
TEXT: ONE OR MORE VARIABLES CONTAINED A MISSING VALUE.
FILE=%FILE
THIS MAY BE NORMAL IF VARIABLE IS INACTIVE IN
DB2GENIN OR UNAVAILABLE AT THIS DB2 RELEASE.
REFER TO THE SASLOG FOR THE SPECIFIC VARIABLES.
TYPE: Warning
REASON: Either the temporary variable used to hold the
previous observation's value or the current
observation contains a missing value.
ACTION: This condition may be normal if either the
variable is not available at the release of DB2
that you are processing or the data element has
been deactivated in DB2GENIN. Determine which it
is, and, if this field is available and you
require it, activate it.
REFERENCES: None
+------------+
| DB200112 |
+------------+
TEXT: DURING DELTA PROCESSING, AT LEAST ONE VARIABLE
WOULD HAVE RESULTED IN A NEGATIVE VALUE.
VARIABLE IS SET TO 0. FILE=%FILE
REFER TO THE SASLOG FOR THE SPECIFIC VARIABLES.
TYPE: Warning
REASON: The reason depends on the file noted in the
message text, but is the result of the preceding
observation containing a value greater than that
in the current observation, which is unexpected
in cumulative records.
ACTION: If the file is the DSB, DSY, or DDY files, then
the problem may be in the raw data itself. The
fields are either corrupted, or the field is not
accumulated across intervals as expected. If the
file is the DSD file, then this may be the result
of our attempt to move the buffer pool related
variables to the DSD file. One cause of this may
be that there are more observations in the DSB
file for some buffer pools than others. When
this occurs, remaining observations will contain
a 0 value, and result in this error message.
This may be normal if the buffer pools displayed
in the error message text have been dynamically
deactivated. Refer to the SASLOG for the
specific variables to determine the cause.
REFERENCES: None
+------------+
| DB200199 |
+------------+
TEXT: ENDING DELTA PROCESS FOR: %FILENAME
LAG RELOADS : %RELOADS
INSTRUMENTATION RESETS : %ISEQS
SUSPEND RECORDS AGED : %SUSDELS
MISSING SUSPEND RECORDS : %MISSSUSP
DUPLICATE ISEQS : %DUPISEQ
TYPE: Informational
REASON: Informational processing summary statistics.
ACTION: None
REFERENCES: None
