MSIR.0605 Connection being debugged lost: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Automatically generated page update)
 
Line 4: Line 4:


{{Template:MSIR.0605 footer}}
{{Template:MSIR.0605 footer}}
[[Category:Sirius Mods messages]] [[Category:MSIR.0600 - MSIR.0799]]
[[Category:MSIR.0600 - MSIR.0799]]

Latest revision as of 23:33, 3 March 2017

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.


Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
CANCELCancels the user's request
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages