WSFQUERY (JANUS DEFINE parameter) - Revision history

JAL: RKTools replaces UL/SPF

2015-10-23T20:46:57Z

RKTools replaces UL/SPF

← Older revision		Revision as of 20:46, 23 October 2015
Line 7:		Line 7:
	If all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling <var class="product">Model 204</var> 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 all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling <var class="product">Model 204</var> 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 <var class="product">Model 204</var> 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.		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 <var class="product">Model 204</var> command line and editor, and many <var class="product">[[RKTools]]</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 <var class="product">[[Janus Telnet Server]]</var>, is available as of <var class="product">Sirius Mods</var> Version 6.9 and later.		This parameter, like the <var class="product">[[Janus Telnet Server]]</var>, is available as of <var class="product">Sirius Mods</var> Version 6.9 and later.

JALWiccan: Automatically generated page update

2013-04-16T22:28:07Z

Automatically generated page update

← Older revision		Revision as of 22:28, 16 April 2013
Line 1:		Line 1:
	<span class="pageSubtitle"~~><section begin="desc" /~~>Write Structured Field Query~~<section end="desc" />~~</span>		<span class="pageSubtitle">Write Structured Field Query</span>

	<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 20:38, 2 March 2012

2012-03-02T20:38:51Z

← Older revision		Revision as of 20:38, 2 March 2012
Line 3:		Line 3:
	<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	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 &~~amp;~~mdash; Model 2 (24 by 80), Model 3 (32 by 80), Model 4 (43 by 80), or Model 5 (27 by 132). <var class="product">Model 204</var> and many clients support more or less arbitrary geometries, but <var class="product">Model 204</var> cannot detect a non-standard geometry on a telnet client without the <var>WSFQUERY</var> 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). <var class="product">Model 204</var> and many clients support more or less arbitrary geometries, but <var class="product">Model 204</var> 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 <var class="product">Model 204</var> 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 all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling <var class="product">Model 204</var> 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.

JALWiccan: 1 revision

2012-03-02T20:19:50Z

1 revision

← Older revision	Revision as of 20:19, 2 March 2012
(No difference)

JAL2 at 20:19, 2 March 2012

2012-03-02T20:19:48Z

← Older revision		Revision as of 20:19, 2 March 2012
Line 3:		Line 3:
	<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	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). <var class="product">Model 204</var> and many clients support more or less arbitrary geometries, but <var class="product">Model 204</var> cannot detect a non-standard geometry on a telnet client without the <var>WSFQUERY</var> 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 &mdash; Model 2 (24 by 80), Model 3 (32 by 80), Model 4 (43 by 80), or Model 5 (27 by 132). <var class="product">Model 204</var> and many clients support more or less arbitrary geometries, but <var class="product">Model 204</var> 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 <var class="product">Model 204</var> 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 all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling <var class="product">Model 204</var> 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.
Line 9:		Line 9:
	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 <var class="product">Model 204</var> 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.		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 <var class="product">Model 204</var> 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 <var class="product">[[Janus Telnet Server]]</var>, 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 <var class="product">Sirius Mods</var> Version 6.9 and later.

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

JAL2 at 18:09, 2 March 2012

2012-03-02T18:09:46Z

← Older revision		Revision as of 18:09, 2 March 2012
Line 3:		Line 3:
	<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	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 &~~amp;~~mdash; Model 2 (24 by 80), Model 3 (32 by 80), Model 4 (43 by 80), or Model 5 (27 by 132). <var class="product">Model 204</var> and many clients support more or less arbitrary geometries, but <var class="product">Model 204</var> cannot detect a non-standard geometry on a telnet client without the <var>WSFQUERY</var> 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). <var class="product">Model 204</var> and many clients support more or less arbitrary geometries, but <var class="product">Model 204</var> 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 <var class="product">Model 204</var> 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 all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling <var class="product">Model 204</var> 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.

JALWiccan: 1 revision

2012-03-01T21:15:18Z

1 revision

← Older revision	Revision as of 21:15, 1 March 2012
(No difference)

JALWiccan: 1 revision

2012-03-01T21:15:13Z

1 revision

← Older revision		Revision as of 21:15, 1 March 2012
Line 3:		Line 3:
	<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	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.		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 &mdash; Model 2 (24 by 80), Model 3 (32 by 80), Model 4 (43 by 80), or Model 5 (27 by 132). <var class="product">Model 204</var> and many clients support more or less arbitrary geometries, but <var class="product">Model 204</var> 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 <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 all connecting clients will be using the standard geometries, the tn3270 protocol correctly sends the model number, telling <var class="product">Model 204</var> 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 <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.		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 <var class="product">Model 204</var> 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 <var class="product">[[Janus Telnet Server]]</var>, 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.

JALWiccan: 1 revision

2012-02-29T23:08:42Z

1 revision

← Older revision	Revision as of 23:08, 29 February 2012
(No difference)

JALWiccan: 1 revision

2012-02-29T23:08:37Z

1 revision

← Older revision		Revision as of 23:08, 29 February 2012
Line 3:		Line 3:
	<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>WSFQUERY</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	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.		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 <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 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.