106
Explanation
An error occurred during processing of a LINK(X), LOAD, ATTACH(X), or XCTL(X) macro.
An error was detected by the control program when it attempted to fetch the requested program into virtual storage. The return code in register 15 identifies the error; see accompanying messages IEW4005I, CSV031I, and CSV028I to determine the reason code. For PMLOADER internal errors not listed, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.
- Code
- Explanation
- 0B
- An error occurred during FETCH processing or in one of the routines that gets control as a result of FETCH processing.
- 0C
- Not enough storage was available for FETCH to get storage for the module or control blocks.
- Code
- Explanation
- 04
- No storage for DATD.
- 08
- No storage for data extent block (DEB).
- 0C
- No storage for I/O supervisor block (IOSB).
- 10
- No storage for EXLIST.
- 14
- No storage for module.
- 18
- Unable to fix storage.
- 0D
- The control program found an incorrect record type in the load module.
- 0E
- The control program found an incorrect address in the load module.
- Code
- Explanation
- 20
- Error converting TTR. One of the following occurred:
- A job opened a data set with DISP=SHR, and another job updates the data set causing the extents in the data set to increase.
- An error occurred in an application program, for example, while retrieving a directory entry using build link-list (BLDL) from one DCB and passing that entry and a different DCB to the LOAD or LINK macro.
- 24
- Block is outside of the module.
- 28
- The address constant location is incorrect.
- 2C
- LOAD from a VIO data set was requested while using ADDR64 or ADRNAPF64 and specifying a target area above the 2GB bar. That is not supported.
- 0F
- Either an uncorrectable I/O error occurred, or an error in the load module caused the channel
program to fail. See the accompanying IEW message for a description of the data set error.
- Code
- Explanation
- 40
- I/O error on a PDS.
- 44
- Error on a virtual DS.
- 48
- Seek address outside extent.
- 4C
- Possible program-controlled interrupt (PCI) logic error.
- 10
- The control program detected a relocation error in the load module.
- 28
- Internal error occurred during fetch processing.
System action
The task is ended unless ERRET was specified on the macro. The system issues message CSV011I.
Operator response
Notify the system programmer.
System programmer response
For a return code of:
- X'0F', resubmit the job. Then have the operator enter a START GTF command specifying
tape output, MODE=EXT and TIME=YES. Have the operator reply TRACE=IO in response to message AHL100A.
Format the output with the IPCS GTFDATA subcommand.
- X'0B', X'0D', X'0E' (reason code of X'24' or X'28'), X'28', or if the problem persists, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center.
Programmer response
For a return code of:
- X'0C' with a reason code of:
- X'14', increase the region size.
- X'04', X'08', or X'10' try decreasing the region size. If the problem recurs, notify the system programmer.
- X'0D', or X'0E' (reason code of X'24' or X'28'), ensure that the load module was not altered so that it is no longer valid. If the load module is valid, then notify the system programmer.
- X'0E' (reason code of X'20'), if the error occurred because a different job updated the data set extents, then restart the job so that the extent list is updated (if the error occurred with the LINKLIST, the system must be IPLed to fix the problem).
Source
Contents supervision (CSV)