Permanent insufficient resource: Receiver cannot act on the request because resources required to
honor the request are permanently unavailable. The sender should not try again immediately
because the situation is not transient. This error can occur if MAXBFRU is either not read
because of a coding error or not coded.
Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0000
- For LU 6.2, transaction program not available, no retry: The FMH-5 Attach command specifies a
transaction program that the receiver is unable to start. The condition is not
temporary. The sender should not try again immediately. This sense data is sent only
in FMH-7.
For non-LU 6.2, no additional information is specified.
- 0001
- Request not processed: Processing an ACTLINK request, and read
buffers not allowed. The ACTLINK request will not be processed.
- 0002
- Creating allocation exception: The receiver is unable to create
the specified data object as a result of an insufficient storage condition
that occurred at allocation time.
- 0003
- Replacing allocation exception: The receiver is unable to replace
the specified data object as a result of an insufficient storage condition
that occurred at allocation time.
- 0006
- Data-object storing exception: The receiver is unable to store
the specified data object as a result of an insufficient storage condition
that occurred during the storing process.
- 0007
- Data-object classification code not supported: The receiver
is unable to satisfy the allocation requirements of the specified
data-object classification code.
- 0008
- Volume not mounted: The receiver is unable to perform the requested
allocation/storing operation because the required volume is not mounted.
- hnnn
- Where h ≥ 8; that is, the high-order bit in Byte
2 is set to one. The 15 low-order bits of Bytes 2 and 3 contain a
binary count that indexes (zero-origin) the first byte of the field
found to be in error.