Appendix A: MESSAGES › 9.2 DAILY Update Processing Flow › SNT00142

SNT00142

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

TEXT:        AN INVALID CONDITION OCCURRED DURING PROCESSING
             %MSGCOND

             where MSGCOND may be one of the following:

             1) INVALID SMF 38 SUB TYPE FOUND IN SNTNET3
             2) INVALID SMF 28 SUB TYPE FOUND IN SNTNET3
             3) INVALID SMF 28 SUB TYPE FOUND IN SNTNPS3
             4) INVALID SMF RECORD FOUND IN SNTNET3
             5) INVALID SMF RECORD FOUND IN SNTNPS3
             6) SMF 28 RCD SESSION DATA OFFSETS INCORRECT
             7) INVALID TIME STAMP FOUND IN SNTNLD4

TYPE:        Warning

REASON:      Messages 1, 2, and 3:  Only certain NPM record
             subtypes are used for processing both the old
             SMF 38 records and the newer SMF 28 records.
             Under normal circumstances, the unnecessary
             subtypes are filtered or dropped as soon as they
             are recognized in the daily job.  These messages
             appear if an incorrect subtype is found after it
             should have been dropped.

             Messages 4 and 5 appear if an incorrect SMF
             record number is found in module SNTNET3 or
             SNTNPS3 after the filtering process.

             Message 6 appears if the proper SMF 28 data
             sessions are not available.

             Message 7 appears if an invalid timestamp is
             found in module SNTNLD4 while processing NetView
             Session Monitor or CA NetMaster SMF 39 records.

ACTION:      None of the above messages should normally
             occur.  If they do, CA MICS network processing
             must have encountered an invalid input record
             and deleted it.  If you receive many of these
             messages, or you suspect that there are serious
             errors in your input data, contact CA Technical
             Support at http://ca.com/support.

REFERENCES:  None