Previous Topic: SNT00143Next Topic: SNT00145


SNT00144

+-----------------+
| S N T 0 0 1 4 4 |
+-----------------+

TEXT:        SMF TYPE 39 INVALID DATE CONDITION FOUND
             %DATELINE
             INPUT RECORD NUMBER: %_N_
             SMF END TIME STAMP : %CHAR_TS

             where DATELINE may be one of the below:

              1) RTM START TIME STAMP GT END TIME STAMP
              2) RTM START TIME STAMP LE ZERO
              3) RTMENDTS GT CURRENT DATE/TIME
              4) RTMENDTS LE ZERO
              5) ACT START TIME STAMP GT END TIME STAMP
              6) ACT START TIME STAMP LE ZERO
              7) ACTENDTS GT CURRENT DATE/TIME
              8) ACTENDTS LE ZERO

             where _N_ is the input (relative) record number.

             where CHAR_TS is the SMF timestamp of the input
             record causing the message to appear.

TYPE:        Warning

REASON:      There appears to be some problems with the
             timestamp fields in the Accounting and
             Availability data section of the SMF type 39
             records.  To date, we have seen the start
             timestamp equal to zero in some records, and
             greater than the end timestamp in other records.
             These incorrect timestamps have been found in
             both Tivoli Netview and CA NetMaster versions of
             the type 39 record.

             There have not been any incorrect date problems
             found in the RTM data section, but the date
             checks were added there for safety.

             The message text, specifically the DATELINE
             value above, explains the condition found.

ACTION:      In cases 1, 2, 5, and 6 above, the CA MICS
             Network Analyzer will reset the start timestamp
             equal to the end timestamp for the appropriate
             data section (RTM or ACT).  For cases 3, 4, 7,
             and 8 above, the end timestamp will be set equal
             to the current timestamp minus one day, in an
             attempt to put the record close to what would
             normally be the previous day's input time range.

             It is recommended that the appropriate vendor
             (Tivoli for Netview or CA for CA NetMaster) be
             contacted regarding this problem.  The message
             text will help you isolate the records having
             the problems.

REFERENCES:  None