VTAM® issues this message when an attempt to send an RU on the SSCP-SSCP session is held because the session has been in a pacing held state longer than three seconds.
This message will continue to be issued at 3-second intervals, for as long as attempts are made to send RUs on the SSCP-SSCP session and the session remains in a pacing held state.
sscpname is the name of the partner SSCP in session with this VTAM.
Processing continues.
Issue VTAM commands to help identify any network problems. Examples would be DISPLAY NET,ROUTE,BLOCKED and DISPLAY NET,ROUTE,HELD to determine status of the virtual routes. Contact the operator of the partner sscpname to issue similar commands and to coordinate network problem determination. If the problem persists, take a dump of the VTAM ASID by issuing a MODIFY vtamproc,CSDUMP and save the log for problem determination. To attempt to recover this SSCP-SSCP session, deactivate and reactivate the session.
If a VR held or blocked condition was indicated, setting the VOSDEACT VTAM start option to YES will cause a VR to be deactivated if a VR out of sequence condition occurs. A VR out of sequence condition could result in a hung VR, if VOSDEACT is set to NO. Use the log and dump information for problem determination.
2
3