DSNJ104I csect-name RECEIVED ERROR STATUS nnn FROM macro-name FOR DSNAME dsname

Explanation

Db2 encountered an error while issuing macro macro-name.

More information about each error status nnn value follows:

  • Start of changeIf macro-name is CATALOG, and the target data set is an archive log data set, nnn is the return code from an unsuccessful SVC 26 (CATALOG) call. dsname is the name of the archive log data set that Db2 attempted to allocate.End of change
  • If macro-name is CLOSE, and the target data set is an archive log data set, nnn is the TCB completion code for an abend received during CLOSE processing. This abend is normally preceded by an IEC210I or IEC212I message that defines the error.
  • Start of changeIf macro-name is DSNJCLOC or DSNPCLOC, nnn is the return code from a call to DSNJCLOC or DSNPCLOC. dsname is the name of the archive log data set that Db2 attempted to access. See Recovering from temporary resource failure for more information.End of change
  • Start of changeIf macro-name is DSNPHRCL, nnn is the return code after Db2 failed to recall a log data set that was migrated by DFSMShsm. dsname is the name of the data set.End of change
  • If macro-name is EDTINFO or UCBLOOK, the first two bytes of nnn contain the return code and the second two bytes of nnn contain the reason code that are returned from the call.
  • Start of changeIf macro-name begins with MMSRV or MMCALL, nnn is the error information that is returned by media manager services. If an MMSRV CATUPDT failure occurs during truncation an active log data set, the log data set is unavailable to Db2, and the status of the log data set is flagged as STOPPED in the BSDS. Message DSNJ104I is preceded by an IEC161I message for a VSAM OPEN error, and by an IEC251I message for a VSAM CLOSE error.End of change
  • If macro-name is OPEN and the target data set is a VSAM data set, nnn is the return code in the error field of the access method services control block. Refer to the appropriate VSAM publication for a definition of these values. Message DSNJ104I is preceded by an IEC161I message that defines the error that occurred.
  • If macro-name is OPEN and the target data set is a non-VSAM data set, nnn is zero. Message DSNJ104I is preceded by an IEC143I message that defines the error that occurred.
  • Start of changeIf macro-name is RDJFCB, nnn is the return code from the RDJFCB call. See Reading and Modifying a Job File Control Block (RDJFCB Macro) for more information on RDJFCB.End of change

If you suspect an error in Db2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.

System action

If this condition is encountered during log manager initialization, Db2 startup is terminated. If the error occurs later, and the data set is needed for offload or for input operations, Db2 processing continues. If a second copy of the data is available, Db2 attempts to allocate and open the second data set.

If the data set is needed as an active log data set, the log manager attempts to retry the failing request. If the retry fails, the Db2 subsystem is terminated.

Operator response

Notify the system programmer.

System programmer response

If the error occurred during initialization, correct the problem so that the data set is available, or provide another copy of the data set, and change the BSDS data sets to point to the new data set.

If the error occurred during Db2 processing, review the return code. Take the appropriate action to correct the problem so that the data set can be used at a later time, or use the change log inventory utility (DSNJU003) to remove the data set entry from the BSDS.

If the error was received from EDTINFO or UCBLOOK, and the allocation of the archive log data set fails, verify that the archive UNIT names are correct in the UNIT and UNIT2 subsystem parameters.