SCREENTHROW and NOSCREENTHROW (JANUS DEFINE parameters): Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
The <var>SCREENTHROW</var> and <var>NOSCREENTHROW</var> parameters are available in Model 204 7.6 and later. | The <var>SCREENTHROW</var> and <var>NOSCREENTHROW</var> parameters are available in Model 204 7.6 and later. | ||
You can override the <var>SCREENTHROW</var> and <var>NOSCREENTHROW</var> parameters on the <var>JANUS DEFINE</var> command on a URL basis using the like-named parameters in [[JANUS WEB SCREEN]] rules. | You can override the <var>SCREENTHROW</var> and <var>NOSCREENTHROW</var> parameters on the <var>JANUS DEFINE</var> command on a URL basis using the like-named parameters in [[JANUS WEB SCREEN]] rules. | ||
After a WebScreenException is thrown, the Janus Web inputs are still available to the application so SCREENTHROW can be used to allow a Janus Web Legacy application to switch modes, by catching a response from a client that is not a response to the 3270 screen read page. | |||
Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports. | ||
Revision as of 20:45, 15 December 2014
Throw or don't throw WebScreenException exceptions on client errors.
SCREENTHROW and NOSCREENTHROW are parameters on JANUS DEFINE, which indicate whether or not WebScreenException exceptions are to be thrown on client errors.
Indicates whether or not WebScreenException exceptions are to be thrown on client errors. NOSCREENTHROW, the default, indicates that WebScreenException exceptions will not be thrown on client errors. When NOSCREENTHROW is used, client errors will typically result in a redisplay of the page in standard Janus Web legacy mode (NOXMLSCREEN) and a user restart in Janus Web Legacy XML mode (XMLSCREEN)
The SCREENTHROW and NOSCREENTHROW parameters are available in Model 204 7.6 and later.
You can override the SCREENTHROW and NOSCREENTHROW parameters on the JANUS DEFINE command on a URL basis using the like-named parameters in JANUS WEB SCREEN rules.
After a WebScreenException is thrown, the Janus Web inputs are still available to the application so SCREENTHROW can be used to allow a Janus Web Legacy application to switch modes, by catching a response from a client that is not a response to the 3270 screen read page.
Valid only for WEBSERV ports.