M204.1968: Difference between revisions
No edit summary |
m (add link) |
||
| Line 1: | Line 1: | ||
{{Template:M204.1968 skeleton}} | {{Template:M204.1968 skeleton}} | ||
<P> | <P> | ||
A Horizon statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>[[ | A [[Horizon]] statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM|DEFINE PROCESS]]</var> command. The process is automatically closed, the SNA Communications Server (also known as VTAM) | ||
session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">token0</var>. This error is most likely to occur when a process expects a reply from the partner | session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">token0</var>. This error is most likely to occur when a process expects a reply from the partner | ||
(as in RECEIVE or CONFIRM) and does not receive one within the time limit. </P> | (as in RECEIVE or CONFIRM) and does not receive one within the time limit. </P> | ||
| Line 9: | Line 9: | ||
<p> | <p> | ||
<b>System manager response:</b> Determine whether or not an SNA Communications Server session was ever established for the conversation. If not, try to determine why a session could not be established with the remote LU. Otherwise, obtain the audit | <b>System manager response:</b> Determine whether or not an SNA Communications Server session was ever established for the conversation. If not, try to determine why a session could not be established with the remote LU. Otherwise, obtain the audit | ||
trail, any audit information available from the remote LU, and an SNA Communications Server trace, and contact [[Contacting Rocket Software Technical Support|Technical Support]]. </p> | trail, any audit information available from the remote LU, and an SNA Communications Server trace, and contact [[Contacting Rocket Software Technical Support|Technical Support]]. | ||
</p> | |||
{{Template:M204.1968 footer}} | {{Template:M204.1968 footer}} | ||
<!-- skeleton as it was in pdf/PROCESS TIMED OUT WAITING FOR COMPLETION OF VTAM_function /--> | <!-- skeleton as it was in pdf/PROCESS TIMED OUT WAITING FOR COMPLETION OF VTAM_function /--> | ||
Revision as of 21:06, 26 March 2018
M204.1968 Process timed out waiting for completion of token
A Horizon statement failed to complete in the length of time specified by the TIMEOUT parameter of the DEFINE PROCESS command. The process is automatically closed, the SNA Communications Server (also known as VTAM)
session is terminated, and the Horizon statement ends with $Status codes of 53-2. The SNA Communications Server request that timed out is identified by token0. This error is most likely to occur when a process expects a reply from the partner
(as in RECEIVE or CONFIRM) and does not receive one within the time limit.
Response: Make sure that the value of the TIMEOUT parameter on the DEFINE PROCESS command is reasonable. Take into account the length of time the partner process may need to be compiled and to perform whatever processing is necessary before sending its reply. If you are confident that the TIMEOUT parameter is reasonable, contact the system manager.
System manager response: Determine whether or not an SNA Communications Server session was ever established for the conversation. If not, try to determine why a session could not be established with the remote LU. Otherwise, obtain the audit trail, any audit information available from the remote LU, and an SNA Communications Server trace, and contact Technical Support.
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=0 | Sets batch (single user) return code |
| CLASS=I | Information class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter |
| AUDITER | Writes the message with line type ER to the audit trail |
| COUNT | Increments the error count (ERCNT) parameter |
| NOTERM | Does not display the message on the user's terminal |