WSFQUERY (JANUS DEFINE parameter): Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
Line 1: Line 1:
{{DISPLAYTITLE:WSFQUERY}}
<span class="pageSubtitle"><section begin="desc" />Write Structured Field Query<section end="desc" /></span>
<span class="pageSubtitle"><section begin="desc" />Write Structured Field Query<section end="desc" /></span>


WSFQUERY is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].
<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].


This parameter indicates that Janus is to issue a "Write Structured Field Query" request to any telnet client that connects to it. This is useful if a connecting client is not using one of the standard screen geometries -- Model 2 (24 by 80), Model 3 (32 by 80), Model 4 (43 by 80), or Model 5 (27 by 132). ''Model 204'' and many clients support more or less arbitrary geometries, but ''Model 204'' cannot detect a non-standard geometry on a telnet client without the WSFQUERY option.  
This parameter indicates that Janus is to issue a "Write Structured Field Query" request to any Telnet client that connects to it. This is useful if a connecting client is not using one of the standard screen geometries -- Model 2 (24 by 80), Model 3 (32 by 80), Model 4 (43 by 80), or Model 5 (27 by 132). ''Model 204'' and many clients support more or less arbitrary geometries, but ''Model 204'' cannot detect a non-standard geometry on a telnet client without the <var>WSFQUERY</var> option.  


If all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling ''Model 204'' the screen geometry. However, even if there are no non-standard screen sizes connecting to a Janus TNSERV port, there is little harm in specifying the WSFQUERY parameter, other than the slight delay in the WSF query being sent, and the response received.  
If all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling ''Model 204'' the screen geometry. However, even if there are no non-standard screen sizes connecting to a Janus <var>[[JANUS DEFINE#type|TNSERV]]</var> port, there is little harm in specifying the <var>WSFQUERY</var> parameter, other than the slight delay in the WSF query being sent, and the response received.  


If the 3270 clients at a site support arbitrary geometries, it might be well worth experimenting with them, as there is no particular reason that any of the standard geometries are ideally suited to a particular workstation. The ''Model 204'' command line and editor, and many ''[[UL/SPF]]'' applications, take advantage of all the space available on non-standard geometry 3270 emulators. To enable support for arbitrary 3270 geometries, the SIRTERM system parameter's X'01' bit must be set.  
If the 3270 clients at a site support arbitrary geometries, it might be well worth experimenting with them, as there is no particular reason that any of the standard geometries are ideally suited to a particular workstation. The ''Model 204'' command line and editor, and many <var class="product">[[ULSPF|UL/SPF]]</var> applications, take advantage of all the space available on non-standard geometry 3270 emulators. To enable support for arbitrary 3270 geometries, the <var>[[SIRTERM parameter|SIRTERM]]</var> system parameter's X'01' bit must be set.  


This parameter, like the Janus Telnet Server, is available as of ''[[Sirius Mods]]'' Version 6.9 and later.  
This parameter, like the <var class="product">[[Janus Telnet Server]]</var>, is available as of ''Sirius Mods'' Version 6.9 and later.  


Valid only for TNSERV ports.
Valid only for <var>TNSERV</var> ports.


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


See: [[List of Janus commands]] | [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].


[[Category:JANUS DEFINE parameters|WSFQUERY]]
[[Category:JANUS DEFINE parameters|WSFQUERY]]

Revision as of 22:05, 28 February 2012

<section begin="desc" />Write Structured Field Query<section end="desc" />

WSFQUERY is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port. See the List of JANUS DEFINE parameters.

This parameter indicates that Janus is to issue a "Write Structured Field Query" request to any Telnet client that connects to it. This is useful if a connecting client is not using one of the standard screen geometries -- Model 2 (24 by 80), Model 3 (32 by 80), Model 4 (43 by 80), or Model 5 (27 by 132). Model 204 and many clients support more or less arbitrary geometries, but Model 204 cannot detect a non-standard geometry on a telnet client without the WSFQUERY option.

If all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling Model 204 the screen geometry. However, even if there are no non-standard screen sizes connecting to a Janus TNSERV port, there is little harm in specifying the WSFQUERY parameter, other than the slight delay in the WSF query being sent, and the response received.

If the 3270 clients at a site support arbitrary geometries, it might be well worth experimenting with them, as there is no particular reason that any of the standard geometries are ideally suited to a particular workstation. The Model 204 command line and editor, and many UL/SPF applications, take advantage of all the space available on non-standard geometry 3270 emulators. To enable support for arbitrary 3270 geometries, the SIRTERM system parameter's X'01' bit must be set.

This parameter, like the Janus Telnet Server, is available as of Sirius Mods Version 6.9 and later.

Valid only for TNSERV ports.

See also