DFS0762I OSAM (TAPE | DASD) (READ | WRITE) ERROR - FUNC=aa STATUS=bb, cc, dddd, eeee, ffff


or

OSAM UNIT=gggg FAILING CCW=hh,,ii,jjjj IOSEEK=kkk...kk LOG=llll


or

OSAM DSN=...............

Explanation

An OSAM I/O error was encountered. A two- or three-line message, each numbered DFS0762I, is generated:
  • The first line indicates (1) whether the I/O operation was directed to a tape or to a direct-access device, (2) whether the I/O operation was READ or WRITE, (3) the OSAM operation type, and (4) the ending status of the operation.
  • The second line indicates (1) the 4-character UNIT name, (2) the failing channel command word, (3) if the device is direct access, the full disk address associated with the I/O operation, and (4) the IMS log record types under which OSAM I/O control blocks were logged.
    Note: The second line is not displayed if the I/O operation was not started.
  • The third line shows the name of the data set on which the error was located.
The variable fields are defined as follows:
FUNC=aa
The OSAM operation type - defined as follows:
01 Read-specific OSAM block
02 Reserved
03 read multiple OSAM buffers
*
04 Scan for file mark
05 Reserved
06 Reserved
*
07 STAE
08 Write specific OSAM block
09 Reserved
*
0A Write queued buffers
*
0B Write sequential block
*
0C Format logical cylinder
*
0D Write file mark
0E Reserved
*
0F Format extent
*
10 REDRIVE after EOV
*
11 REDRIVE after DDR SWAP
*
12 Post tape RRQ in error
13 Virtual format logical cylinder

(* Indicates internal functions.)

STATUS=bb
The IOSB/IOB completion code used to post the operation complete.
cc
The DECB status code (DECBSTAT) is defined as follows:
01 Undefined operation code
02 DCB not open
03 IDAL translation error
04 Channel program protection error
05 Incorrect length error (bad DCBBUFL)
06 Permanent I/O ERROR
07 DCB specified as DD Dummy
08 RBN conversion error
09 RBN beyond current end of data set
0A End-of-file reached
0B Caller not authorized for call type
0C Unable to obtain channel program work area
0D No space to add block to data set
0E Associated chained block I/O error
0F Reserved
10 Unable to allocate an IOSB from the OSAM I/O storage pool
11 DEB/DCB validity check error
12 I/O prevented
13 Write queue errors (buffer prefix contains status)
14 Buffer ignored due to previous error
15 Chained read error (buffer prefix has status)
16 Reserved
17 Invalid block/buffer count
18 Buffer prefix chained out of sequence
19 Tape I/O error-try DDR SWAP
1A Write attempted to a read-only data set
1B I/O request terminated abnormally because of program check or machine check in IOS or appendage.
1C Channel program check
1D Record not found
1E DCB already closing
1F Nonzero return code from page fix routine
20 Channel program translate error
21 Media Manager error
22 Encryption buffer storage request error
23 DFSAOSFM error
24 Unable to allocate MMCLP control block
25 Unable to allocate MMRQ control block
dddd
The unit and channel status of the CSW
eeee
The residual byte count of the failing CCW.
ffff
The first two sense bytes if the unit status in the CSW indicates unit check. If a unit check is not indicated, periods (.) are displayed.
Remember: If the I/O operation was not started, the character string I/O NOT STARTED is displayed instead of the status bytes, the residual byte counts, and the first two sense bytes.
UNIT=gggg
The 4-character unit name associated with the device.
FAILING CCW=
hh Operation code
ii Flags
jjjj Byte count
Note: If it is determined that the CCW address is invalid, that is, causes a program check if used, the character string UNKNOWN is displayed instead of the selected CCW fields. The paired comma indicates the absence of the data/IDAL address.
IOSEEK=kkk..k
The full disk address of the form MBBCCHHR. This field is displayed only for direct-access devices.
LOG=llll
The IMS log record types under which the OSAM I/O control blocks were logged.
6201
Only an X'6201' record was logged.
6202
Both an X'6201' and an X'6202' record were logged.
6203
All three types of records were logged.
GERR
X'6201' and X'6202' records were logged, but an attempt to log an X'6203' record failed because of a GETMAIN error.
LERR
X'6201' and X'6202' records were logged, but an attempt to log an X'6203' record failed because of a logging error.

System action

Processing continues. If the I/O error involves a user database, messages DFS0451I follow. See the explanation for that message.

Operator response

Issue the /START DATABASE command, see if errors are resolved.

Module

DFSAOS80