|
|
This section describes messages issued by the IUCV routine. These messages include T01IU000 through T01IU099.
Explanation Connection to IUCV was established successfully.
Explanation The IUCV connection was shut down normally.
Explanation The connection to IUCV was terminated.
Explanation An unrecognized IUCV is already running.
Recommended Action Bring down the non-Cisco IOS for S/390 IUCV and start the Cisco IOS for S/390 IUCV.
Explanation The IUCV address space has not yet been started.
Recommended Action Start the IUCV address space.
Explanation An ABEND occurred while the SAPI control block was being processed.
| cb_name | Name of control block name that was processing. |
| mod_name | Module name. |
| addr | Address of module. |
Recommended Action Retain the dump and contact Customer Support.
Explanation Cisco IOS for S/390 has recognized that the IUCV subsystem subsysid has terminated. Cisco IOS for S/390 will try to reconnect with a new IUCV address space every 30 seconds. ssss is the 4 character VMCF subsystem name.
Explanation When the ptask is T01AMIUC and the module is IFSPPCEX then Cisco IOS for S/390 was unable to find the ASID for IUCV from the MVS PC tables.
| mod_name | Module name. |
| pc_num | PC number that failed to convert into an ASID. |
| ret_code | Return code from module IFSPPCEX that details the specific error. This could lead to a situation where Cisco IOS for S/390 may not be able to recognize when the IUCV address space is shutting down.
The R15 return code can be one of the following: 0--Success; PC is space switch variety. 4--Success; PC is non-space switched variety. 8--Linkage table origin invalid. 0C--Linkage index value is too large. 10--Linkage index is invalid. 14--PC number is too large. |
Recommended Action Save all job output from the Cisco IOS for S/390 job and contact your local TCP support.
|
|