How to avoid error message IDI8301E NO MORE SPACE FOR DATA IN DATA SPACE

Products

• Database Analyzer (IMS Tools)
• Database Analyzer for IMS for z/OS
• DATABASE MANAGEMENT SOLUTIONS FOR IMS FOR Z/OS

Issue/Introduction

When full pointer checking is requested for huge data bases containing different data base datasets, the data space being used for checking may
not be large enough, resulting in Database Analyzer abending with error message IDI8301E.

Resolution

For full pointer checking these are the execution options normally being used with Database Analyzer:

1. FUNCTION=ANALYZEALL,DBDNAME=maindbd
   
   When using these options all pointers of all related data base datasets will be checked - including index key values, with the exception of Logical Parent Concatenated Key values for logical related data bases (checking these values requires option LPCKCHECK=Y).
   
   For huge data bases or complex logical relationships the data space being used for checking by default may not be large enough, resulting in error message IDI8301E and Database Analyzer abending.
   
   When this happens use execution option MULTIPSPACE=Y to force DBA to use additional sets of data spaces for pointer checking:
   
   
2. FUNCTION=ANALYZEALL,DBDNAME=maindbd,MULTISPACE=Y
   
   In the rare situation that these data spaces are still not large enough to enable all necessary pointer checking, separate the index key checking, to one index data base per job step. The first step should perform no index key checking, then the subsequent steps perform index key checking for each individual index data base:
   
   
   1. FUNCTION=ANALYZEALL,DBDNAME=maindbd,MULTISPACE=Y,INDEXKEYCHECK=N
      
      
   2. FUNCTION=ANALYZE,DBDNAME=indexdbd1,MULTISPACE=Y,INDEXKEYCHECK=Y,POINTERCHECK=CROSSDBD
      
      
   3. FUNCTION=ANALYZE,DBDNAME=indexdbd2,MULTISPACE=Y,INDEXKEYCHECK=Y,POINTERCHECK=CROSSDBD etc.

If DBA still should abend with error message IDI8301E, please contact support for further advices how to check all necessary pointers.