EP212 CATALOG CHAIN ERRORS, PLEASE DO NOT CANCEL/EP213 RECORD aaaaaaaaaa CHAINED FROM bbbbbbbbbb POINTS BACK TO cccccccccc
Article ID: 26474
Updated On:
Products
Issue/Introduction
Receiving the following messages during the daily TSIDUTIL BACKUP job:
EP212 CATALOG CHAIN ERRORS, PLEASE DO NOT CANCEL EP213 RECORD aaaaaaaaaa CHAINED FROM bbbbbbbbbb POINTS BACK TO cccccccccc
Environment
Component: EPIC-Disk Management
Cause
This can happen if a job was flushed or canceled while the catalog is being updated.
Resolution
TSIDTECH is provided to help correct catalog chaining errors identified by error messages EP212 and EP213.
Verify that the address in the CHAINBLD ADDR= field is taken from the Chained from address in the EP213 error message.
Example
EP213 RECORD 00000_____ CHAINED FROM 000008330F POINTS BACK TO 0000000000
// JOB TSIDTECH // OPTION LOG // EXEC TSIDTECH CHAINBLD ADDR=08330F /* /&
Additional Information
************************************** * IMPORTANT - PLEASE READ CAREFULLY! * **************************************
Since the purpose of the TSIDTECH program is to detect and potentially correct catalog chaining errors, the catalog is read without using any of the forward record pointers. Since the relative version number of a generation is not maintained within the catalog but is determined by the relative position of a record within a chain of records, positioning must be determined using an alternate method and it is possible that a dataset may be presented with the generations in other than the correct version order. For example, this condition can occur when a generation receives its position within a chain as a result of a TSIDONL onload or as a result of a maintenance TRANSFER function.
Therefore, it is very important and entirely the users responsibility that, after rechaining has been accomplished using data produced by the TSIDTECH program, the user verify that the dataset contains only those generations expected and those generations are presented in the expected version order.
Feedback
