XMLSCREEN and NOXMLSCREEN (JANUS DEFINE parameters): Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
m (add displaytitle)
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:
<span class="pageSubtitle">Present or don't present legacy screens as non-HTML XML</span>
<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 <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.  


Indicates whether or not <var class="product">[[Janus Web Legacy Support|Janus Web Legacy]]</var> 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. <var>NOXMLSCREEN</var>, the default, specifies that <var class="product">Janus Web Legacy Support</var> 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 <var class="product">[[Janus Web Legacy XML Support]]</var> which provides a much nicer interface for external programs to process legacy 3270 screens.
These parameters indicate the output format of 3270 screens that <var class="product">[[Janus Web Legacy Support]]</var> converts:
<ul>
<li><var>XMLSCREEN</var> specifies that screens are sent as XML with field names but no formatting information. </li>
 
<li><var>NOXMLSCREEN</var>, the default, specifies that screens are sent as XHTML with formatting tags, so the screens are viewable as browser pages but without field names. </li>
</ul>
 
Using <var>NOXMLSCREEN</var> to convert 3270 screens to XHTML is suitable if the intent is for the pages to appear on a browser, but this is not very convenient if the screen content is to be processed by some other program. Using <var>XMLSCREEN</var> enables <var class="product">[[Janus Web Legacy XML Support]]</var>, which provides a much nicer interface for external programs to process legacy 3270 screens.


The <var>XMLSCREEN</var> and <var>NOXMLSCREEN</var> parameters are available in <var class="product">Sirius Mods</var> Version 8.1 and later.  
The <var>XMLSCREEN</var> and <var>NOXMLSCREEN</var> parameters are available in <var class="product">Sirius Mods</var> Version 8.1 and later.  


You can override the <var>XMLSCREEN</var> and <var>NOXMLSCREEN</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>XMLSCREEN</var> and <var>NOXMLSCREEN</var> parameters on the <var>JANUS DEFINE</var> command on a URL basis using the like-named parameters in <var>[[JANUS WEB SCREEN]]</var> rules.  


Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports.
Valid only for <var>[[JANUS DEFINE#type|WEBSERV]]</var> ports.


==See also==
==See also==
<ul>
<li>[[XMLSCREENFIELD and NOXMLSCREENFIELD (JANUS_DEFINE_parameters)|XMLSCREENFIELD and NOXMLSCREENFIELD]] </li>
<li>[[XMLNULLSCANCEL and XMLNULLSSEND (JANUS DEFINE parameters)|XMLNULLSCANCEL and XMLNULLSSEND]] </li>
<li>[[XMLNULLSSTRIP and XMLNULLSBLANK (JANUS DEFINE parameters)|XMLNULLSSTRIP and XMLNULLSBLANK]] </li>
<li>[[List of Janus commands]] </li>


<ul>
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]] </li>
<li>[[List of Janus commands]]
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]]
</ul>
</ul>


[[Category:JANUS DEFINE parameters|XMLSCREEN and NOXMLSCREEN]]
[[Category:JANUS DEFINE parameters|XMLSCREEN and NOXMLSCREEN]]

Latest revision as of 00:16, 8 June 2016

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.

These parameters indicate the output format of 3270 screens that Janus Web Legacy Support converts:

  • XMLSCREEN specifies that screens are sent as XML with field names but no formatting information.
  • NOXMLSCREEN, the default, specifies that screens are sent as XHTML with formatting tags, so the screens are viewable as browser pages but without field names.

Using NOXMLSCREEN to convert 3270 screens to XHTML is suitable if the intent is for the pages to appear on a browser, but this is not very convenient if the screen content is to be processed by some other program. Using 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.

See also

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=XMLSCREEN_and_NOXMLSCREEN_(JANUS_DEFINE_parameters)&oldid=84525"