|
|
|
The following reason codes describe errors that occurred while reading or extracting segments from a block of SMF data:
I/O error on CAIJSSMF. Message CAJS951I gives information on the nature of the error. The GETCB is SNAP'd to help locate the exact block where the error occurred. Processing resumes with the next block. (However, processing terminates after three consecutive I/O errors.)
The block descriptor word at the beginning of a block of SMF data contains a length value less than 9. The GETCB and the block are SNAP'd. Processing resumes with the next block.
The segment descriptor word at the beginning of a block of SMF data contains a length value less than 4. The GETCB and the block are SNAP'd. Processing resumes with the next block.
The segment descriptor word of the segment being extracted from a block of SMF data contains a length value indicating that the segment extended beyond the end of the block. (The probable cause is a truncated block.) The GETCB and the block are SNAP'd. Processing resumes with the next block.
The following reason codes describe errors that occurred while attempting to assemble segments into a complete logical record in the program work area:
The span control bits in the first segment to be moved to the work area indicated that it was not the first segment of a record. The GETCB and the segment are SNAP'd. Processing resumes with the next segment.
The span control bits in the current segment indicate that it is the first or only segment of a record; however, no final segment has yet been encountered for the partial record currently being assembled in the program work area. The GETCB, the segment, and the contents of the work area are all SNAP'd. Processing resumes with the current segment.
The current segment cannot be assembled into the program work area because the work area is too small. (See note 2 in the section Notes on Common Problems in this chapter for a discussion of how to control the size of the work area.) Processing resumes with the next segment.
A discontinuity has occurred on the input file before an end segment has been encountered for the logical record currently being assembled in the work area. The most probable cause of the discontinuity is that a block has been SNAP'd for reasons A through D above.
A discontinuity can also occur during data set switching for concatenated input if the LRECL value for the new data set is larger than the existing work area size. (When this happens, the work area must be freed and reallocated. The GETCB is SNAP'd, along with the contents of the work area, if possible. Processing resumes with the next segment.
End-of-file has been reached before an end segment has been encountered for the logical record currently being assembled in the work area. The GETCB and the contents of the work area are SNAP'd. Processing continues as if normal end-of-file had been reached.
The following reason codes indicate that a data exception or other program check has occurred in the course of processing an SMF record, or that invalid or inconsistent data has been detected in the record. In each case, the RCAREA and the SMF record in question are SNAP'd and processing resumes with the next logical record.
If a user SMF input exit is being used to reconstruct SMF records in a work area, both the original record and the reconstructed record are SNAP'd.
The SNAP'd SMF record(s) should be checked against the record descriptions in the IBM SMF Reference Manual.
A program check has occurred during mainline CA JARS processing. This should never occur. If it does, contact CA Technical Support for assistance. For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.
A program check has occurred while validating the information in the current record. Probable cause is an invalid Julian date in the record.
A program check has occurred while extracting information from the current record. Probable cause is an invalid Julian date in the record.
A program check has occurred while the user SMF input exit had control. Interrupt information stored in the RCAREA can be of use in locating the cause of the problem.
Invalid data has been detected while validating an SMF record. Possible causes include: a record length shorter than the allowable minimum for that record type; inconsistencies in the internal length fields that define subsections of certain record types; or, for SMF type 6, SMF6SBS is X'0000'.
Invalid data has been detected while extracting data from an SMF record. The probable cause is an inconsistency in the internal length fields of the record.
An error has occurred while attempting to normalize a time/date stamp in a record relative to the Reader Start Date for the job. The difference between the two dates is greater than 50 days, either positive or negative, indicating probable erroneous data.
The SMF buffer date on a record has exceeded the expiration date of your version of the CA Job Accounting Report System. If the problem continues to occur, contact CA Technical Support. For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.
The CMF record does not match any of the Data Dictionaries provided.
Record too short. Record is SNAP'd and rejected.
Unknown subtype in SMF30 header.
Unknown subtype in SMF30 subsystem section.
Invalid subtype in SMF30 subsystem section.
SMF30-1 record did not contain an ID section.
SMF30 record did not contain required sections.
SMF30-5 record did not contain an ID section.
Subsystem section missing from SMF30 record.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |