DFS3744A FORMATTING OF ALL NEW ADS(S) FAILED FOR AREA=areaname REASON CODE=nn
Explanation
The Create utility, DBFUMRI0, in its format phase,
failed to format all of the area data sets (ADS) of the named area
because of error code nn. The reason code nn can
be one of the following values:
- Code (dec)
- Meaning
- 01
- Area lock failed.
- 02
- The DBRC interface failed. Reading the ADS list from the RECON data set or writing the ADS list onto the RECON data set failed.
- 04
- The formatting of all new ADSs failed.
- 05
- An internal command to stop an ADS failed because of a system error (area lock or notify failure).
- 06
- The VSAM control block (RPL) manipulation and MODCB RPL failed.
- 07
- The data set verification failed and this message is issued when:
- Defined control interval (CI) size is inconsistent with the DBD parameter.
- Insufficient space is defined for the new ADS.
- 08
- The dynamic allocation or opening of the new ADS for formatting failed. You can also receive this error when the VSAM cluster was not defined.
- 09
- The storage GETMAIN for the VSAM control block (RPL) work area failed.
- 0A
- The AREA has EEQE.
System action
The Fast Path utility being used terminates.
Programmer response
Ensure that all newly issued ADSs are stopped
among all the subsystems. If they are not stopped, enter the /STOP
ADS command to stop the area data set globally. When this
action is done, take the following action:
- Code (dec)
- Meaning
- 01
- Rerun the job.
- 02
- Ensure that the area record exists in the DBRC RECON data set and rerun the job.
- 03
- Remove EQE from the current active ADSs using the offline Database Recovery utility, DFSURDB0. When this action is done, rerun the job.
- 04
- Define another VSAM data set for any new ADS, and rerun the job.
- 05
- Rerun the job.
- 06
- Rerun the job.
- 07
- Define another VSAM data set with the correct control interval size and space and rerun the job.
- 08
- The application program terminates when the dependent region abends. After preparing the tracing facilities for lock, rerun the job. One possible cause is that the VSAM cluster was not defined.
- 09
- Rerun the job.
- 0A
- Remove EQE from the current active ADS using the offline database recovery utility, DFSURDB0. Then rerun the job.