MSIR.0605 Connection being debugged lost: Difference between revisions
(Automatically generated page update) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
A statement that requires an open connect to a client (such as a $Web function or a Print statement) was invoked but the connection being debugged via JANUSDEBUG was closed. This statement is the equivalent of a | A statement that requires an open connect to a client (such as a $Web function or a <var>Print</var> statement) was invoked but the connection being debugged via <var>JANUSDEBUG</var> was closed. This statement is the equivalent of a <code>M204.0564 CONNECTION TO USER LOST (PHONE WAS HUNG UP</code> message when the request is not being run under <var>JANUSDEBUG</var>. Since the primary connection for a <var>JANUSDEBUG</var> thread is the 3270 thread, MSIR.0605 is issued in place of M204.0564 to prevent the 3270 thread from being restarted because a browser closed a connection. | ||
This message could either because the client (most often a browser) closed the connection before it received a response or because of an application error that performs a web function after sending the response to the browser, that is, after it issued a <var>$Web_Done</var>, or a <var>$Web_ProcSend</var> without a <var>MORE</var>. | |||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] | ||
Revision as of 23:15, 22 April 2014
A statement that requires an open connect to a client (such as a $Web function or a Print statement) was invoked but the connection being debugged via JANUSDEBUG was closed. This statement is the equivalent of a M204.0564 CONNECTION TO USER LOST (PHONE WAS HUNG UP message when the request is not being run under JANUSDEBUG. Since the primary connection for a JANUSDEBUG thread is the 3270 thread, MSIR.0605 is issued in place of M204.0564 to prevent the 3270 thread from being restarted because a browser closed a connection.
This message could either because the client (most often a browser) closed the connection before it received a response or because of an application error that performs a web function after sending the response to the browser, that is, after it issued a $Web_Done, or a $Web_ProcSend without a MORE.