DSNJ073I LOG ARCHIVE UNIT ALLOCATION FAILURE DETECTED, RETURN CODE=nnnn. ALLOCATION OR OFFLOAD OF ARCHIVE LOG DATA SET MAY FAIL.

Explanation

While building the SVC99 text entries to dynamically allocate a new archive log data set, a unit allocation failure was detected. This message is only generated when a trace for IFCID 320 is active. The reason code, indicated by nnnn in the message, further clarifies the problem as follows:
4 (X'04')
The device type (unit name) on which the archive log data set is to be allocated is specified by the user in the Db2 system parameters. No UCBs could be found for the device type (unit name).
8 (X'08')
The device type (unit name) on which the archive log data set is to be allocated is specified by the user in the Db2 system parameters. This device type (unit name) could not be found in the MVS eligible device table (EDT).
32 (X'20')
Db2 was able to obtain a list of devices corresponding to the device type (unit name) specified in ZPARMs. However, it was determined by Db2 that this list contained a mixture of tape and nontape devices.
40 (X'28')
The device type (unit name) specified by the user in ZPARMs is valid. However, no devices are currently associated with the given device type (unit name).
44 (X'2C')
The device type (unit name) specified by the user in ZPARMs is valid. However, no DASD volumes are available with a volume use attribute of 'storage'.
48 (X'30')
The CVT indicates that UCB services are not available.

System action

This message is issued by Db2 after the SVC99 text entries are built, but prior to the allocation of the new archive log data set. As a result of the error, the dynamic allocation of the archive log data set will be attempted using standard default values. The standard default values are generally acceptable; however, the allocation may fail or the subsequent offload may produce undesirable processing results. For example:
  • A return code of 4 or 44 (X'2C') will foretell an allocation error (DSNJ103I) when the SVC99 is issued for the archive data set.
  • Offload processing to tape may fail. Db2 uses a volume count of 20 when allocating to tape, and uses the standard MVS volume count default of 5 volumes when writing to nontape devices. In the case of most of the above errors, it would be impossible for the Db2 subsystem to determine the device type on which the data set is to be allocated. Therefore, the standard MVS default is assumed for the volume count. If the data set is successfully allocated to a tape device, and the volume of data is such that more than five volumes will be used for the archive data set, the offload processing will receive an MVS ABEND 837-08 with message IEC028I when attempting to write to the sixth tape volume.
  • Offload processing to a direct access device may fail. When allocating a new archive log data set on a direct access device, the Db2 subsystem will use a unit count to facilitate multivolume archive data sets. With most of the above errors, it may be impossible for the Db2 subsystem to correctly determine the type of device on which the data set is to be allocated. Therefore, the standard default (1) is assumed for the unit count. If the data set is successfully allocated to a direct access device, and during the offload processing it becomes necessary to extend the data set to another device, the offload processing will receive an MVS B37 (out of space) ABEND, and the archive log data set will be deallocated.

Operator response

Notify the system programmer.

System programmer response

The required action is based on the return code indicated in the message.
4 (X'04') or 8 (X'08')
The most likely cause is an incorrect specification in the archive log ZPARMs (DSNTIPA panel). Correct the DEVICE TYPE field. If the DEVICE TYPE field from the archive log ZPARMs appears to be correct, check the EDT to ensure that the esoteric or generic unit name specified in the ZPARMs is actually in the EDT. Subsequent offload processing will archive the log data which could not be previously archived due to the allocation failure (DSNJ103I).
32 (X'20') or 40 (X'28')
To correct this situation, change the archive log DEVICE TYPE ZPARM to use a device type (unit name) which contains homogenous devices, or modify the device list associated with the device type (unit name) via a system generation to supply a list of homogenous devices.
44 (X'2C')
To correct this situation, issue an MVS mount command to change the volume use attribute of a mounted 'private' volume to 'storage'. If this is a recurring problem, a system generation may be required to add permanently resident volumes with a volume use attribute of 'storage' to the esoteric or generic unit, or ZPARMs may have to be changed to use a different esoteric or generic unit name for the DEVICE TYPE (on the DSNTIPA installation panel).
48 (X'30')
Migrate the operating system to a release level that supports UCB services.