XMLSCREEN and NOXMLSCREEN (JANUS DEFINE parameters): Difference between revisions
m (Created page with "{{DISPLAYTITLE:XMLSCREEN and NOXMLSCREEN}} <span class="pageSubtitle"><section begin="desc" />Present or don't present legacy screens as non-HTML XML<section end="desc" /></span>...") |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:XMLSCREEN and NOXMLSCREEN}} | {{DISPLAYTITLE:XMLSCREEN and NOXMLSCREEN}} | ||
<span class="pageSubtitle" | <span class="pageSubtitle">Present or don't present legacy screens as non-HTML XML</span> | ||
<var>XMLSCREEN</var> and <var>XMLNOSCREEN</var> are parameters on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. | <var>XMLSCREEN</var> and <var>XMLNOSCREEN</var> are parameters on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. | ||
Revision as of 22:28, 16 April 2013
Present or don't present legacy screens as non-HTML XML
XMLSCREEN and XMLNOSCREEN are parameters on JANUS DEFINE, which defines and sets characteristics of a Janus port.
Indicates whether or not Janus Web Legacy screens will be be sent as XML with field names but no formatting information, or as XHTML with formatting tags so that the screens are viewable as a browser pages but without field names. NOXMLSCREEN, the default, specifies that Janus Web Legacy Support converts 3270 screens to XHTML. While this is nice if the intent is for the pages to appear on a browser, it's not very convenient if the screens/pages are to be processed by some other program. Specifying XMLSCREEN enables Janus Web Legacy XML Support which provides a much nicer interface for external programs to process legacy 3270 screens.
The XMLSCREEN and NOXMLSCREEN parameters are available in Sirius Mods Version 8.1 and later.
You can override the XMLSCREEN and NOXMLSCREEN parameters on the JANUS DEFINE command on a URL basis using the like-named parameters in JANUS WEB SCREEN rules.
Valid only for WEBSERV ports.