MSIR.0605 Connection being debugged lost - Revision history

JALWiccan: Automatically generated page update

2017-03-03T23:33:23Z

Automatically generated page update

← Older revision		Revision as of 23:33, 3 March 2017
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]]

JALWiccan: Automatically generated page update

2016-07-11T20:51:01Z

Automatically generated page update

← Older revision		Revision as of 20:51, 11 July 2016
Line 3:		Line 3:
	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>.		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>.

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

JALWiccan: Automatically generated page update

2015-08-13T16:03:41Z

Automatically generated page update

← Older revision		Revision as of 16:03, 13 August 2015
Line 3:		Line 3:
	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>.		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]] [[Category:MSIR.0600 - MSIR.0799]]

JAL at 23:15, 22 April 2014

2014-04-22T23:15:08Z

← Older revision		Revision as of 23:15, 22 April 2014
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 "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.		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 $~~Web_done~~, or a $~~Web_procSend~~ without a MORE.		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]]

DmeWiccan: Automatically generated page update

2013-04-19T17:46:13Z

Automatically generated page update

← Older revision		Revision as of 17:46, 19 April 2013
Line 3:		Line 3:
	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.		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.

	[[Category:Sirius Mods ~~Messages~~]]		[[Category:Sirius Mods messages]]

Admin: 1 revision

2010-11-09T16:41:35Z

1 revision

← Older revision	Revision as of 16:41, 9 November 2010
(No difference)

198.242.244.47: Created page with "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..."

2010-11-09T14:53:54Z

Created page with "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..."

New page

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.

[[Category:Sirius Mods Messages]]