Previous Topic

Next Topic

Book Contents

Book Index

Messages DIG900 through DIG9xx

This group includes messages for the IOA (infrastructure) product.

DIG901I UTILITY IOADIG STARTED

Explanation: This information message indicates the normal start of the IOADIG utility. The IOADIG utility performs IOA Access Method data file integrity checking.

Corrective Action: No action is required.

DIG902S WARNING: RBA INCONSISTENT AT BLOCK= blk RECORD= rec

Explanation: An RBA error was detected by the IOADIG utility while checking the rec record of the input IOA Access Method data file. This message indicates the specific block and record that contain the error.

The IOADIG utility continues executing.

Corrective Action: Rerun the IOADIG utility with ACT set to W to correct the error. If the error remains, save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you continue to encounter problems with the IOA Access Method files, see the section on reorganizing the IOA Access Method File in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG903S HEADER CORRUPT. POINTER TO START OF FREE RECORD CHAIN INVALID

Explanation: An error was detected by the IOADIG utility in the header of the input IOA Access Method data file.

The IOADIG utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG904I NO FREE RECORDS DETECTED. CHECK NOT REQUIRED

Explanation: This information message indicates normal termination of data file integrity checking by the IOADIG utility when the file to be checked is full.

Corrective Action: No action is required.

DIG905S INTEGRITY CHECK ENDED ABNORMALLY. FREE RECORD CHAIN CREATION FAILED

Explanation: The IOADIG utility is unable to perform integrity checking on the requested IOA Access Method data file.

The IOADIG utility terminates with a condition code of 32.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG906I CHECK COMPLETED NORMALLY. ERRORS CORRECTED

Explanation: This information message indicates that the IOADIG utility ended normally, and errors were corrected successfully.

Corrective Action: No action is required.

DIG907I DATABASE INTEGRITY CHECK ENDED OK: NO ERRORS DETECTED

Explanation: This information message indicates that the IOADIG utility ended and no errors were detected.

Corrective Action: No action is required.

DIG908S NUMBER OF FREE RECORDS IN HEADER DOES NOT MATCH THE ACTUAL NUMBER OF FREE RECORDS

Explanation: The IOADIG utility detected in the header of the IOA Access Method data file that the number of free records in the data file and the number of free records recorded in the header record are not the same.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG909S ACTIVE RECORD ENCOUNTERED IN FREE RECORD CHAIN

Explanation: The IOADIG utility detected an active record in the free record chain of the IOA Access Method data file.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG90AS INVALID FREE LIST POINTER ENCOUNTERED

Explanation: The IOADIG utility detected an invalid free list pointer while integrity checking the IOA Access Method data file. One or more records pointed to by the free list pointer are not free records.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG90BS CROSS-LINKED FREE RECORDS ENCOUNTERED

Explanation: The IOADIG utility detected a recursive pointer error in the free record chain while integrity checking the IOA Access Method data file.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG90CS INVALID RECORD ID IN THE RECORD HEADER

Explanation: The IOADIG utility detected an invalid record ID in the data file header while integrity checking the IOA Access Method data file.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG90DS FREE RECORD OUT OF CHAIN AT BLOCK= blk RECORD= rec

Explanation: While integrity checking the IOA Access Method data file, the IOADIG utility detected a free record that is not in the free record chain.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG90ES INSUFFICIENT STORAGE TO RUN UTILITY

Explanation: The IOADIG utility requires more storage to perform an integrity check on the IOA Access Method data file.

The utility terminates with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the utility.

DIG90FS OPEN OF FILE FAILED

Explanation: The IOA Access Method data file for which integrity checking was requested cannot be opened. Possible causes are causes:

The IOADIG utility terminates with a condition code of 16.

Corrective Action: Correct the JCL and rerun the job. If the error persists, notify your INCONTROL administrator.

DIG911S ERROR DETECTED: BLOCK= blk RECORD= rec

Explanation: The IOADIG utility detected an error in the rec record in the blk block.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG912S POINTER TO THIS RECORD IS AT BLOCK= blk RECORD= rec

Explanation: The IOADIG utility detected an error in a pointer at the rec record in the blk block.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG913I DATABASE INTEGRITY ERRORS DETECTED. TO CORRECT, SPECIFY "FUNC=W"

Explanation: This information message indicates that the IOADIG utility detected one or more integrity errors.

The utility terminates with a return code of 32.

Corrective Action: To correct the errors, rerun the IOADIG utility after setting the FUNC parameter to W. If the problem persists, save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG914S ERROR OPENING SYSPRINT

Explanation: An error occurred while opening the SYSPRINT DD statement. The DD statement is probably missing.

The IOADIG utility terminates with a return code of 8.

Corrective Action: Notify your INCONTROL administrator.

DIG916S DATABASE INTEGRITY ERRORS DETECTED

Explanation: The IOADIG utility detected one or more integrity errors.

The IOADIG utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG917S WARNING: INCORRECT RBA IN BLOCK blk

Explanation: The IOADIG utility detected an invalid Relative Block Address (RBA) in the blk block.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG918S WARNING: INCORRECT RECORD ID IN BLOCK blk

Explanation: The IOADIG utility detected an invalid record ID in the block identified in the message.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG919S HEADER CORRUPT: INCORRECT {BLOCK SIZE | RECORD LENGTH | DATASET NAME}

Explanation: The IOA Access Method data file header does not contain the correct block size, record length, or data set name information (as indicated in the wording of the message). The error was detected by the IOADIG utility.

The utility stops executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG920S QUANTUM NOT IN ASCENDING ORDER - PROBLEM NOT CORRECTED

Explanation: The values specified for the QUANT1, QUANT2 and QUANT3 parameters are not in ascending order. These parameters are used with variable record length IOA Access Method Database file components for managing free space areas when new records are written. They must correlate with the BLKSIZE parameter as follows: QUANT1 < QUANT2 < QUANT3 < BLKSIZE.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG921S WARNING: INCORRECT FREE SPACE COUNTER IN BLOCK blk

Explanation: The free space counter in the blk block is not accurate. This error was detected by the IOADIG utility.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG922S WARNING: INCORRECT RECORD ORDER IN BLOCK blk

Explanation: One or more records are out of sequence in the block identified in the message. This error was detected by the IOADIG utility.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG923S WARNING: INCORRECT RECORD COUNTER IN BLOCK blk

Explanation: The IOADIG utility detected that the record counter in the blk block is not accurate.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG924W WARNING: INCORRECT FREE SPACE QUANTUM FOR BLOCK blk

Explanation: The IOADIG utility detected that the amount of free space designated for the blk block is incorrect. These parameters are used with variable record length IOA Access Method Database file components for managing free space areas when new records are written. They must correlate with the BLKSIZE parameter as follows: QUANT1 < QUANT2 < QUANT3 < BLKSIZE.

The utility continues executing.

Corrective Action: Check that all started tasks or jobs in Control-D or Control-V that are working with user files are running on LPARs which are synchronized by software such as GRS or MIM.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG925S HEADER CORRUPTED: INCORRECT TYPE IN RECORD ZERO

Explanation: The IOADIG utility detected that the record type recorded in the IOA Access Method data file header record is incorrect.

The utility continues executing.

Corrective Action: Save the output of the job. Create a copy of the IOA Access Method index and data files by means of the IEBGENER utility, and contact BMC Customer Support. Include all the extents of the files.

If you encounter more problems with the IOA Access Method files, refer to the section that describes IOA Access Method file reorganization in the INCONTROL for z/OS Administrator Guide to learn how to reorganize the files.

DIG926S DYNAMIC ALLOCATION ERROR OF EXTENT= dsn RC= rc REASON= rsc

Explanation: The IOADIG utility detected an error during allocation of an extent.

The utility terminates with a return code of 12.

Corrective Action: For a description of the reason code received, refer to the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, report the reason code to BMC Customer Support.

DIG927I INTEGRITY CHECKED OK FOR DATASET dsn

Explanation: This information message indicates that the IOADIG utility did not find any integrity problems in the dsn data set.

The utility continues executing.

Corrective Action: No action is required.

DIG928I DATABASE INTEGRITY CHECKED OK: NO ERRORS DETECTED

Explanation: This information message indicates the normal end of the IOADIG utility. No errors were detected.

The utility terminates with a return code of 0.

Corrective Action: No action is required.

DIG929I INTEGRITY CHECKED OK FOR MAIN DATASET

Explanation: This information messages indicates that the IOADIG utility found no errors in the main data set.

Corrective Action: No action is required.

DIG92AS DEALLOCATION ERROR FOR DATASET dsn

Explanation: The IOADIG utility detected an error during deallocation of an extent of the dsn data set.

The utility terminates with a return code of 12.

Corrective Action: For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, report the reason code to BMC Customer Support.

DIG92BS FOR DSN=

Explanation: This message is the header for other messages which indicate the relevant data set names.

Corrective Action: No action is required.

DIG92CS INVALID PARAMETER, VALID PARAMETERS ARE ACT=R/W, TYPE=F/V

Explanation: An invalid parameter was passed to the IOADIG utility.

Valid values for the ACT parameter:

Valid values for the ACT parameter:

The utility terminates with a return code of 24.

Corrective Action: Rerun the IOADIG utility after setting its parameters to valid values.

DIG92DI INPUT PARAMETERS ARE

Explanation: This information message is the header for a list of input parameters.

Corrective Action: No action is required.

DIG92ES DATASET NAME dsn IN CONTROL BLOCK IS TOO LONG

Explanation: This message indicates that the IOADIG utility detected that the dataset name (dsn), in the control block of the IOA Access Method data file, is longer then 38 bytes.

The utility terminates with a condition code of 16.

Corrective Action: Use the following procedure:

  1. Save the output of the job.
  2. Use the IEBGENER utility to create a copy of the IOA Access Method index and data files. Be sure to include all the extents of the files.
  3. Contact BMC Customer Support.

If you encounter more problems with the IOA Access Method files, see the INCONTROL for z/OS Administrator Guide for information on how to reorganize the files.

Parent Topic

DIG messages