|
|
This section describes messages issued by the IUCV routine. These messages include T02IU000 through T02IU099.
Explanation The TCP/IP IUCV address space has successfully completed all initialization steps and is ready to process IUCV requests. The subsystem interface named subsys_name has been activated.
Explanation The TCP/IP IUCV address space has successfully completed the termination process and can no longer process IUCV requests.
Explanation The TCP/IP IUCV address space has failed to initialize. The reason code identifies what caused the failure.
| 4 | IUVT allocation failed |
| 8 | SSCVT allocation failed |
| 12 | VMCF allocation failed |
| 16 | IUVX allocation failed |
| 20 | ASVB allocation failed |
| 24 | IASB pool header load failed |
| 28 | EORA pool header load failed |
| 32 | PTPA pool header load failed |
| 36 | IUMS pool header load failed |
| 40 | Subsystem name already active |
Recommended Action Allocation failures are generally due to insufficient storage in either the private area of the address space, or in CSA. Make sure sufficient storage exists.
Pool header load failures are generally due to either insufficient storage in the private area of the address space or the module could not be located. Pool header module names have the format T02LxxxP, where xxx is the first three characters of the pool name (e.g. pool header for IASB is T02LIASP).
Explanation During termination processing, an attempt was made to release storage being used for the VMCF_CVT. The VMCF_CVT is allocated in common storage. rsn_code is the return code from the Storage Release service.
Recommended Action Check the return code from the Storage Release service and take the appropriate action.
|
|