DFS0842I OSAM DATASET CANNOT BE EXTENDED, REASON=X, Z,dbdname
ddname, dsname

Explanation

OSAM was unable to extend the named data set. A two line message each numbered DFS0842I is issued. The first line indicates why the data set is not extendable. It also contains the dbdname. The second line contains the ddname and the dsname.

In the message text:
X
The reason code that identifies the error condition
Z
The hexadecimal error subcode
dbdname
The database name
ddname
The data definition name
dsname
The data set name
The following reason codes (X) identify error conditions detected by DFSDBH10. The first word in the description is the label name where the error was detected. Conditions 1, 2, and 3 occur only in a data sharing environment when the data set was extended on another subsystem. The subsystem with the error was unable to perform a similar extension.
X reason code - set by module DFSDBH10
Error condition
1
LCREAT10: Pseudo data set extension failed.
2
DSXT0350: The volume serial number for the new extent does not match the volume serial number broadcast by the extending subsystem.
3
DSXT0360: An error occurred while processing an OSAM TCLOSE function for the data set. A TCLOSE is the closing and reopening of the data set to acquire new extent information.
4
Not used.
5

LCREAT30: An attempt to allocate another extent for the data set using the OSAM end-of-volume routine failed. The data set could not be extended.

6
LCREAT40: An attempt to obtain a buffer for the requested block failed. This problem might have been caused by I/O errors on one of the OSAM data sets that share the same set of buffers.
7
LCREAT70: An I/O error was received during the format logical cylinder operation.
The following reason codes (X) identify error conditions detected by DFSDBH1M. The first word in the description is the label name where the error was detected. Condition A occurs only in a data sharing environment when the data set was extended to another subsystem. The subsystem with the error was unable to perform a similar extension.
X reason code - set by module DFSDBH1M
Error condition
A
LCREAT10: Pseudo data set extension failed.
B
LCREAT31: Failed to allocate an MMCLP control block.
C
LCREAT3C: Failed to allocate an MMSPL control block.
D
LCREAT3E: Call to OSAM Media Manager end-of-volume routine failed.
E
LCREAT32: An attempt to obtain a buffer for the requested block failed. This problem might be caused by I/O errors on one of the OSAM data sets that share the same set of buffers.
F
LCREA300: Failed to allocate an MMRQ control block.
G
LCREAT45: An attempt to obtain a buffer for the requested block failed. This problem might be caused by I/O errors on one of the OSAM data sets that share the same set of buffers.
H
LCREA610: Failed to allocate an MMCLP control block.
I
LCREA620: Failed to allocate an MMRQ control block.
J
LCREAT70: An I/O error was received during the format logical cylinder operation.
K
LCREAT78: Failed to allocate an MMCLP control block.
L
LCREAT7C: Failed to allocate an MMSPL control block.
M
LCREAT7F: CATUPDT request failed.
N
DSXT0165: Failed to allocate an MMCLP control block.
O
DSXT016C: Failed to allocate an MMSPL control block.
P
DSXT016E: UPDATECB request failed.
Q
DSXT0352: Failed to allocate an MMCLP control block.
R
DSXT035C: Failed to allocate an MMSPL control block.
S
DSXT0360: UPDATECB request failed.

Z subcode is returned in DCBWRK1+3 by modules DFSAOSF0, DFSAOS10, DFSAOSFM, DFSAOS1M and DFSDBH1M. This subfield of the message is only used for a message that contains reason codes 5 or D.

Z subcode (hex) - set by module DFSAOSFM:
Meaning
01
Invalid EOV request.
02
Call to DFSMMCL0 failed.
03
DCB is not open.
04
Data set is not extendable, or secondary allocation is not permitted.
05
Could not build authorized copy of MMCLP.
06
Could not find an authorized copy of MMP.
07
DCB is a DD dummy data set.
08
Data control block (DCB) marked unusable.
Z subcode (hex) - set by module DFSAOS1M:
Meaning
21
DCB is a DD dummy data set.
22
DCB is not open.
Z subcode (hex) - set by module DFSDBH1M:
Meaning
31
EOV call to DFSMMCL0 failed.
The following subcodes (Z) identify error conditions detected by DFSAOSF0 and DFSAOS10. The Z subcode is returned in DCBWRK1+3, and is used to identify error conditions associated with reason code 5.
Z subcode (hex) - set by module DFSAOSF0:
Meaning
01
Data control block (DCB) marked unusable.
02
DCB is DD dummy data set.
03
DCB is not open.
04
Data extension block (DEB) has reached maximum size.
05
Data set not extendable, or secondary allocation is not permitted.
06
Insufficient volumes.
07
An error occurred while locating the current volumes extents. The return code from the OSPLIT subroutine is 4 in register 15.
08
An error occurred while converting an OSAM data extension block (DEB) to an MVS DEB. The return code from the OSDEB subroutine is 4 in register 15.
09
An error occurred while constructing an OSAM DEB. The return code from the OSAMDEB subroutine is 4 in register 15.
0A
DEB/DCB validation check failed.
0B
This call is not for an EOV call request.
0C
An error occurred while locating the current volumes extensions. The return code from the OSPLIT subroutine is 8 in register 15.
0D
An error occurred while converting an OSAM data extension block (DEB) to an MVS DEB. The return code from the OSDEB subroutine is 8 in register 15.
0E
An error occurred while constructing an OSAM DEB. The return code from the OSAMDEB subroutine is 8 in register 15.
0F
Error releasing a captured unit control block (UCB).
Z subcode (hex) - set by module DFSAOS10:
Meaning
20
End-of-volume (EOV) is already pending.
21
I/O error was encountered
22
DCB was DD dummy data set. It was detected by DFSAOS10.
23
DCB was not open. It was detected by DFSAOS10.
24
Error acquiring new extent.
30
Error formatting logical cylinder.

System action

For condition 1, 2, or 3, the application program pseudoabends with abend 0842. For the other conditions, processing continues and message DFS0845I might follow.

Operator response

(master terminal) Notify the IMS system programmer or database administrator of the condition.

Programmer response

Take the following actions:
  • If data set extend error 1, 2, or 3 occurs in a data sharing environment, ensure that all the volumes of the database are shared among the subsystems and that a path exists to all volumes.
  • If data set extend error 5 occurs, add additional space or reduce the number of DASD extents, by reorganizing the database or recovering the database with larger space parameters. After an extend error 5, if an OSAM data set cannot be opened because it extends beyond the OSAM-supported maximum number of extents, you might need an intermediate utility step when opening the data set to allow the system to release the unused extents. For example, use an ADRDSSU job with RELEASE, or a copy utility such as IEBGENER with a dummy input data set and the OSAM data set as output, specifying DISP=MOD and SPACE=(xxx,(primary,secondary),RLSE). For information about extends, see Using OSAM as the access method.
  • If I/O errors were encountered, follow the actions defined in message DFS0451I or DFS0451A.

Problem determination

3, 4, 5, 17

Module

DFSDBH40 and DFSDBH4M