|
|
T01CO011I
This chapter describes messages issued by the commutator service routine. These messages include T01CO000 through T01CO999.
Explanation This message is confirmation that the shutdown request was received. The task group initiates orderly shutdown procedures.
Explanation The task group is ready to terminate. The shutdown procedures either completed in an orderly manner or were forced by another shutdown command.
Explanation Failure to activate Ptask name, normally APILOGTA.
Recommended Action This is an internal problem. Notify Customer Support.
Explanation Ptask name terminated abnormally. This may be a transient condition which resulted in an ABEND, in which case recovery will be successful.
Recommended Action If the condition persists after a recovery attempt, notify Customer Support.
This message is a confirmation of a Ptask activation.
Explanation This message is a confirmation of a Ptask termination.
Explanation During startup, synchronizing various activity levels resulted in a controlled wait loop for another component to reach a required state. No action is necessary and message T01CO008I displays when the startup process is resumed.
Explanation This message indicates that commutator startup is resumed after waiting for some other event. This message follows T01CO007I.
step_name or reply 'NO' Explanation A mount is required for a data set on magnetic tape. This allows the operator to cancel a tape mount request before the mount time expires. It can be used, for example, when a requested tape volume cannot be located.
Recommended Action Mount the tape on the indicated device or reply NO to cancel the request if the tape cannot be mounted.
Explanation This message is displayed at 30 second intervals if the tape mount request from message T01CO009I times out. A cancellation option is made available if the requested tape cannot be mounted.
T01CO011IExplanation A mount is required for a data set on magnetic tape. This allows the operator to cancel a tape mount request before the mount time expires. It can be used, for example, when a requested tape volume cannot be located.
Recommended Action Mount the tape on the indicated device or reply NO to cancel the request if the tape cannot be mounted.
NO ACSSCB POINTER IN ACCOM Explanation The ACSSCB pointer in control block ACCOM does not exist. The pointer has been overlaid with zeros. Cisco IOS for S/390 cannot use its subsystem interface and ABENDs with a user 2007.
Recommended Action Save all output from the job. Contact Customer Support. Restart the Cisco IOS for S/390 job.
ACSSCB PTR NOT AN ASCB Explanation The ACSSCB pointer in control block ACCOM does not point to a valid ACSB. Cisco IOS for S/390 cannot use its subsystem interface and ABENDs with a user 2107.
Recommended Action Save all output from the job. Contact Customer Support. Restart the Cisco IOS for S/390 job.
LOAD FAILED FOR CHAR/DBCS TRANSLATION MODULE modExplanation The attempt to load the specified module, mod, as single or double byte character set translation table failed.
Recommended Action Verify that the character set name has been created and is a valid table.
VALIDATION FAILED FOR CHAR/DBCS TRANSLATION MODULE modExplanation An invalid character set translation table (mod) has been specified or defined. This table may have been created incorrectly or was not created for the specified transopt (single or double).
Recommended Action Verify character set matches the translation mode.
Explanation This message appears immediately before an ABEND issued by the ACLOAD routine in ACCOM when a PLOAD macro specifies a module (module) not usable for subsequent processing. Unless local modifications are made to the Cisco IOS for S/390 distribution libraries, this message should only appear during testing, not in a product environment.
The code of the subsequent ABEND identifies the reason:
| 706 | The module is linked as non-executable. |
| C06 | The module is not found in the correct library, or is linked to be either overlay or scatter. |
| D06 | An error occurred during the BLDL process. |
Recommended Action The Cisco IOS for S/390 LOAD library must be in the STEPLIB DD statement of the Cisco IOS for S/390 startup JCL. If the ABEND code is a D06 and the module name is ARPAINIT, probably the LOAD library was not placed into (or was removed from) the STEPLIB DD statement in the startup JCL.
In most cases a relink with the correct attributes corrects this condition. The D06 ABEND is triggered by system action, and may require the assistance of a system programmer to resolve.
Explanation A user attempts to sign on to external security and receives a return code higher than an 8 from a RACROUTE-RACINIT sign-on attempt. The only valid return codes from RACROUTE-RACINIT are 0, 4, and 8. The bad return code could be generated from an external security exit or module ACSECPC. Cisco IOS for S/390 ABENDs the ptask with an 0C1.
Recommended Action Save all output from the job. Contact Customer Support. ACC personnel can tell the user how to display RACROUTE-RACINIT return codes in the JOB log.
ACEE FOR VALIDATED USER DID NOT OCCUR Explanation A ptask is attempting to perform a RACROUTE-RACINIT TYPE=DELETE function and does not have a valid ACEE address in its SECACEE field. The ptask ABENDs with an X'307'.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check for any SVC dumps that may have been issued. Check the JOB log and WTO logs for related messages. If you are using P-services to create an application, check the program logic of the failing ptask. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390applications, contact Customer Support. ACC personnel can tell you how to display RACROUTE-RACINIT return codes in the JOB logs
|
|