DFS2843E DATASET service FAILED FOR ds_type, RC=rrrrrrrr/ssssssss
DSN=dsn
SYNAD BUFFER FOLLOWS: dev#,devtype,DD name,operation,,block number,access method

Explanation

A data set failure occurred.

The third line of this message, which begins with SYNAD BUFFER FOLLOWS, is displayed only when passed on by the BSAM data set access method. When the line is displayed, it contains the contents of the SYNAD buffer, including the device number, the device type, the DDname, the operation attempted, the error description, the block number, and the access method, which is BSAM. For information about the mapping and meaning of the SYNAD buffer, see the description for the SYNADAF macro. BSAM might or might not return the SYNAD buffer, depending upon the error.

In the message text:
service
The service that failed, which can be:
  • OPEN
  • CLOSE
  • READ
  • WRITE
ds_type
Identifies the online change data set specified in the DFSCGxxx PROCLIB member.
rrrrrrrr
The return code from the MVS/DFP service. This return code is not displayed when the SYNAD buffer is displayed.
ssssssss
The reason code from the MVS/DFP service. This reason code is not displayed when the SYNAD buffer is displayed.
dsn
The name of the data set.

If an OM command encounters this error, this message is sent to the OM output exit as an unsolicited message.

If IMS initialization or IMS restart encounters this error, this message is sent to the system console.

If a utility encounters this error, this message is sent to the utility's job log.

System action

The system action depends on the IMS function that encountered the error:
  • IMS initialization fails with abend 2800, subcode X'0002' or X' 0003'.
  • IMS restart fails with abend 2801, subcode X'0002' or X'0003'.
  • IMS online change commands are rejected.

Operator response

Correct the data set problem and try IMS initialization, IMS restart, or the online change command again.

If the error description of the DFS2843 message contains the text WRNG.LEN.RECORD, the OLCSTAT data set might not have been allocated correctly. Verify that you allocated the OLCSTAT data set with an end of file (EOF) mark. If you used IEFBR14 to allocate the OLCSTAT data set, it does not have an EOF mark and cannot be read. You must allocate the OLCSTAT data set with an EOF mark to correct this problem. You can use IEBGENER or the ALLOCATE function of ISPF utilities to allocate the OLCSTAT data set

Module

DFSIIOC0, DFSIQ040, DFSOLC00, DFSROLC0