DFS057I REQUESTED BLOCK NOT AVAILABLE: blockname RC = reason

Explanation

MFS cannot fetch the control blocks required to process an output message or to process the /FORMAT request. blockname in the message identifies the block that could not be fetched and is either the MOD or the DOF name. If it is the DOF name, the first two bytes of the name are the device type and features printed in hexadecimal. For an interpretation of these two bytes, see Format library member selection.

The reason code reason indicates the type of failure that occurred:
Code (hex)
  Meaning
04
The indicated block name was not found in the active format data set library. The following conditions can cause this reason code to be produced:
  • There is a misspelled message output descriptor (MOD) name or the MOD does not exist in the active format data set library.
  • A device output format (DOF) for the specified MOD with the device type and feature indicated does not exist in the active format data set library.
08
There is a permanent I/O error in the active format data set library.
0C
The main storage space required for the MOD or DOF, or both, is greater than the maximum space currently available in the message format buffer pool. Alternatively, no fetch request elements (FREs) were available. This return code is issued only by prefetch routines, not by immediate fetch routines.
14
A MOD block was to be fetched. The fetched block was not a MOD.
18
The MOD block fetched was compiled before Release 1.1.1 of IMS.
1C
The MOD and DOF fetched were incompatible (not compiled at the same time). The use of z/OS® utilities to alter the active format data set library can cause this problem.
20
The MOD or DOF contains an invalid field. This problem can be caused by modification of, or damage to, the format or test format library.
24
The requested MOD or DOF is too large for the message format buffer pool (MFBP). The MFBP must be increased. Notify the system programmer.
28
The DOF and CIB screen sizes are incompatible. This problem occurs only for 3270-AN device types. The screen size defined for system definition was different from the size in the device characteristics table, DFSUDTOX. The system programmer should ensure that the correct device characteristics table is used.
38
The MOD is not available because use of the MOD causes the HIOP storage pool to be overwritten.
78
The DOF is not available because use of the DOF causes the HIOP storage pool to be overwritten.

System action

Since the requested blocks were not available, IMS formatted and sent the message using the 'default block error message format (DFSMO3)', and then dequeued the message.

If TRACE is set on for this NODE/PTERM, an X'67' record is created on the IMS log with the ID of "FERR".

Operator response

(master terminal) Take the following action to correct the errors:

For reason code 20:

Stop using the transactions using the MOD or the DOF, or both, for a time sufficient to allow the blocks to be replaced by others in the Message Format. Try the failing transaction again. If the error persists, the block was destroyed in the FORMAT or TFORMAT library, an error was compiled into the block, or there is an error in one of the MFS online modules. If the error does not recur, data was overlaid in the message format buffer pool. In both cases, the X'67' log record contains helpful information.

For reason codes 38 and 78:

Stop using the transactions using the MOD, the DOF, or both until the blocks can be replaced. The MOD or DOF and its format set must be recompiled and then replaced using the online change process. The invalid block might have been destroyed in the FORMAT library, an error might have been compiled into the block, or an error exists in one of the MFS online modules.

Two X'67' log records are written to the IMS log. The first record has an ID of MTRP and has information useful for diagnosing the reason for potential overwrite. The second record has an ID of FERR and records the unavailability of the MOD or DOF.

Programmer response

Take the following action to correct the errors.

For reason code 04:
  • Ensure that the MOD name provided from the application program, by the previous Message Input Description (MID) NXT= parameter, or in a /FORMAT command is spelled correctly and that the MOD exists in the active format data set library.
  • Ensure that the DOF exists in the active format data set library with the device type and features of the terminal receiving the error message. If the MOD specifies the IGNORE option, the DOF must have the IGNORE feature specified.

For reason code 0C:

Use the MFS utility to determine the combined size of the MOD and DOF. Increase the space available for format blocks in the message format buffer pool using the "HHH" parameter on the IMS control region EXEC statement.

For reason codes 14 and 1C:

Reprocess the message source definition using the MFS Language utility.

For reason code 18:

The MFS libraries from previous versions cannot be used. All message and format source definitions must be recompiled using the MFS Language utility.

Problem determination

5, 14, 16

Module

DFSCFEO0