IDC11724I   DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET

Explanation

Some abnormal situations, such as ABENDs or logical errors, can cause a control area (CA) split or CA reclaim to be interrupted. A logical error results in VSAM backing out the CA split that is in progress and returning a nonzero return code to the PUT that caused the CA split. When a CA split is aborted in an abnormal condition, an unreachable new CA (commonly referred to as an orphan CA) can be left behind within the data set. This in itself does not cause a data integrity problem and the data set is fully functional and accessible.

Orphan CAs might have an effect on other programs or functions:
  • The VSAM data set may fill up prematurely when there are a large number of orphan CAs and this may require the data set to be reorganized to reclaim the unusable DASD space.
  • DFSMSdss will not complete a dump of the data set if the VALIDATE parameter is used and results in message ADR970E. Manual intervention is required to create a backup of the data set.
  • IDCAMS EXAMINE INDEXTEST DATATEST generates the IDC11724I message and sets the return code to 4 if only the orphan CA condition is present and no data integrity problems are detected. However, if the EXAMINE also detects data integrity problems, it will also display other messages and will return with return code = 8 (and not 4). Because EXAMINE INDEXTEST DATATEST checks both the index and data components, its return code is more accurate in reflecting the true severity of the situations it detects than that of EXAMINE DATATEST NOINDEXTEST; it is also more thorough in detecting errors. Below are some output examples:
    Example 1
      EXAMINE NAME(xxxxxxxx) INDEXTEST DATATEST                        
    IDC01700I INDEXTEST BEGINS                                               
    IDC11724I DATA COMPONENT CA NOT KNOWN TO 
              SEQUENCE SET                    
    IDC21700I MINOR ERRORS FOUND BY INDEXTEST                                
    IDC01701I DATATEST BEGINS                                                
    IDC11768I [CI SPLIT | CA RECLAIM] IN PROGRESS                            
    IDC01713I DATA CONTROL INTERVAL DISPLAY AT RBA 
              yyy FOLLOWS
    ...
    IDC01714I ERROR LOCATED AT OFFSET zzzzzzzz               
    IDC11724I DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET    
    IDC21703I MINOR ERRORS FOUND BY DATATEST                 
    IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 4
    Example 2
      EXAMINE NAME(xxxxxxxx) INDEXTEST DATATEST                                         
    IDC01700I INDEXTEST BEGINS                                                      
    IDC11718I DATA COMPONENT HIGH-USED RBA IS NOT EQUAL TO CA SIZE
    IDC01702I HIGH-USED RBA/CI IS xx                                                
    IDC01705I CONTROL AREA SIZE IS xxxx                                            
    IDC11711I INDEX CONTROL INTERVAL COUNT ERROR                                    
    IDC01708I 1 CONTROL INTERVALS ENCOUNTERED                                       
    IDC01702I HIGH-USED RBA/CI IS xxx                                                 
    IDC01704I CONTROL INTERVAL SIZE IS xxxx                                          
    IDC11708I HIGH-USED INDEX RBA DOES NOT EQUAL HIGHEST RBA FOUND                  
    IDC01702I HIGH-USED RBA/CI IS xxx                                                
    IDC01706I RBA/CI IS xxx                                                                          
    IDC21701I MAJOR ERRORS FOUND BY INDEXTEST                                       
    IDC01701I DATATEST BEGINS                                                       
    IDC11768I [CI SPLIT | CA RECLAIM] IN PROGRESS                                  
    IDC01713I DATA CONTROL INTERVAL DISPLAY AT RBA xxxx FOLLOWS   
    ...
    IDC01714I ERROR LOCATED AT OFFSET xxxxxxxx                
    IDC11724I DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET     
    IDC21703I MAJOR ERRORS FOUND BY DATATEST                  
    IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
    Note: In cases where the High-used RBA does not equal the highest found RBA (as indicated by IDC11708I in the example above), an IDCAMS VERIFY should be run first and the EXAMINE rerun.
    Similarly, IDCAMS EXAMINE INDEXTEST NODATATEST issues the IDC11724I message and sets return code to 4, or RC=8 if it detects data integrity problems.
  • IDCAMS EXAMINE DATATEST NOINDEXTEST always gives a return code of 8 for message IDC11724I because it does not review the entire index structure and cannot determine if the missing CAs present a data integrity issue or not. EXAMINE DATATEST NOINDEXTEST is faster than DATATEST INDEXTEST, so is better suited to more quickly determine whether or not there are orphan CAs or some other errors that can be found without searching the whole index structure. If errors are found, issue EXAMINE DATATEST INDEXTEST to pinpoint the severity of the situation and to find the complete set of errors. Below is an output example:
      EXAMINE NAME(xxxxxxxx) DATATEST NOINDEXTEST
    IDC01701I DATATEST BEGINS                                  
    IDC11768I [CI SPLIT | CA RECLAIM] IN PROGRESS              
    IDC01713I DATA CONTROL INTERVAL DISPLAY AT RBA 
              yyy FOLLOWS 
    ...
    IDC01714I ERROR LOCATED AT OFFSET zzzzzzzz               
    IDC11724I DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET    
    IDC21703I MAJOR ERRORS FOUND BY DATATEST                 
    IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

System action

Supportive messages display pertinent data, and processing continues.

Programmer response

The dataset has ownership of physical space on the volume that it will never use. To clean up the orphaned CAs, a reorganization of the dataset will need to be done. This corrective action applies to only the RC=4 situations. When RC=8, the data set might be broken and might need to be recovered with a process beyond reorganization.

Source

DFSMSdfp