DSNJ103I csect-name LOG ALLOCATION ERROR DSNAME=dataset-name, ERROR STATUS=status-indicator, SMS REASON CODE=ssssssss

Explanation

The log manager encountered an error while it attempted to allocate the specified active or archive log data set.

csect-name
The name of the control section that issued the message.
dataset-name
The name of the data set.
status-indicator
The error reason code that is returned by MVS dynamic allocation (SVC99). This value consists of a 2-byte error code (S99ERROR) followed by a 2-byte information code (S99INFO) from the SVC99 request block.
ssssssss
If available, more SMS reason code information from S99ERSN, which is a field of S99RBX. ssssssss is displayed if the S99ERROR code indicates an SMS allocation error (97xx).

This message might be preceded by message DSNJ073I.

System action

For active log data sets, if the error is encountered during log manager initialization, Db2 startup is terminated. If two copies of the active log data sets are defined, this message is displayed only once.

For archive log data sets, if two copies of the archive log data sets are defined, processing continues on the remaining archive log data set.

Operator response

Notify the system programmer.

System programmer response

If the status-indicator value is '17080000', the site might have one or more active log data sets defined in the BSDS, but not allocated on DASD. To correct the situation, print the contents of the current active log data set inventory by using the print log map (DSNJU004) utility. Then, take one of the following actions:

  • For each active log data set that is listed in the BSDS, but not allocated on DASD, allocate the active log data set by using access method services. The access method services command syntax for active log data sets can be found in installation job DSNTIJIN.
  • Use the DSNJU003 utility DELETE statement to delete the errant active log data set name. Then, use the DSNJU003 utility NEWLOG statement to add the correct name to the active log data set inventory. The name that is specified on the NEWLOG statement must be the same as the name of the actual Db2 active log data set that is allocated on DASD.
If the problem occurred because the MVS task I/O table (TIOT) did not have enough space, an allocation error occurs. In this case, perform the following actions to maximize the size of the TIOT and to minimize the amount of TIOT space that each data set uses:
  1. Set the MVS TIOT size to 64K in the ALLOCxx PARMLIB member.
  2. Specify NON_VSAM_XTIOT=YES in the DEVSUPxx PARMLIB member to enable Db2 to use the MVS extended task I/O table (XTIOT) when allocating offload data sets.
  3. Specify a dynamic volume count (DVC) of 0 for any SMS data set class that is used to allocate a Db2 BSDS, active log, or secondary log data set.
  4. Reallocate any existing BSDS, active log, or secondary log data sets that were allocated with a DVC greater than 0.
If the problem occurred during Db2 initialization and that data set is an active log data set, take one of the following actions:
  • Resolve the error (status-indicator) that is associated with the active log data set
  • Provide another copy of the active log data set by using access method services (AMS)
  • Update the BSDS by using the change log inventory (DSNJU003) utility
  • Restart Db2
For archive log data sets, take one of the following actions:
  • If the problem occurred during allocation with the intent to write the data set, no immediate action is required. However, failure to resolve the error (status-indicator) might eventually cause the available space in the active log to be exhausted (DSNJ111E), because all future offloads might fail due to the same error.
  • If the problem occurred during allocation with the intent to read the data set, determine the problem. Use the DSNJU003 utility DELETE statement to delete the archive log data set from the BSDS archive log inventory. Then, use the DSNJU003 utility NEWLOG statement to add the data set back to the archive log inventory with the correct volume and device.