TCPTYPE parameter - Revision history

Tom: /* Description */

2024-02-06T17:11:07Z

Description

← Older revision		Revision as of 17:11, 6 February 2024
Line 39:		Line 39:
	<tr>		<tr>
	<td><b>HPNS</b></td>		<td><b>HPNS</b></td>
	<td>IBM HPNS (High Performance Native Sockets). Note that despite its name, HPNS's performance is not nearly as good as BPX's. </td></tr>		<td>IBM HPNS (High Performance Native Sockets). Note that despite its name, HPNS's performance is not nearly as good as BPX's. No longer supported as of version 7.9 of Model 204. </td></tr>

	<tr>		<tr>
	<td><b>INTERLNK</b></td>		<td><b>INTERLNK</b></td>
	<td>InterLink TCP/IP.</td></tr>		<td>InterLink TCP/IP. No longer supported as of version 7.9 of Model 204.</td></tr>

	<tr>		<tr>

DCameron: /* Description */

2017-09-26T10:00:16Z

Description

← Older revision		Revision as of 10:00, 26 September 2017
Line 15:		Line 15:

	==Description==		==Description==
	This parameter specifies the type of TCP/IP network to which Model 204 is connected.		This parameter specifies the type of [[Janus_TCP/IP_Base\|TCP/IP]] network to which Model 204 is connected.
	Generally, you can let this parameter default (<var>UNKNOWN</var> is default value). Janus then automatically detects the type of TCP/IP you have on your machine, and it resets the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly set.		Generally, you can let this parameter default (<var>UNKNOWN</var> is default value). Janus then automatically detects the type of TCP/IP you have on your machine, and it resets the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly set.

JAL: misc formatting

2016-12-06T22:07:28Z

misc formatting

← Older revision		Revision as of 22:07, 6 December 2016
Line 18:		Line 18:
	Generally, you can let this parameter default (<var>UNKNOWN</var> is default value). Janus then automatically detects the type of TCP/IP you have on your machine, and it resets the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly set.		Generally, you can let this parameter default (<var>UNKNOWN</var> is default value). Janus then automatically detects the type of TCP/IP you have on your machine, and it resets the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly set.

	If you specify type <var>IBM</var> or <var>IBMV6</var>, Janus detects and sets the type of IBM interface it will use, as shown in the table below.		If you specify type <var>IBM</var> or <var>IBMV6</var>, Janus detects and sets the type of IBM interface it will use, as shown in the table below. Only these values invoke auto-detection.

	You can also override auto-detection by explicitly supplying a <var>TCPTYPE</var> parameter value.		You can also override auto-detection by explicitly supplying a <var>TCPTYPE</var> parameter value.
Line 31:		Line 31:
	<td rowspan="5">IPV4 only</td>		<td rowspan="5">IPV4 only</td>
	<td><b>IBM</b></td>		<td><b>IBM</b></td>
	<td>Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPX~~. For CMS, this is IUCV~~. </td></tr>		<td>Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPX. </td></tr>

	<tr>		<tr>
Line 52:		Line 52:
	<td rowspan="2">IPV6 only</td>		<td rowspan="2">IPV6 only</td>
	<td><b>IBMV6</b></td>		<td><b>IBMV6</b></td>
	<td>Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPXV6~~. For CMS, this is IUCVV6~~.		<td>Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPXV6.
	<p>		<p>
	This option is available as of version 7.7 of Model 204.</p></td></tr>		This option is available as of version 7.7 of Model 204.</p></td></tr>
Line 62:		Line 62:

	<tr>		<tr>
	<td rowspan="2">CMS</td>		<td rowspan="4">CMS</td>
	<td>IPV4 only</td>		<td rowspan="2">IPV4 only</td>
			<td><b>IBM</b></td>
			<td>Auto-detect the "best" IBM TCP/IP interface. For CMS, this is IUCV. </td></tr>
			<tr>
	<td><b>IUCV</b></td>		<td><b>IUCV</b></td>
	<td>IBM TCP/IP IUCV (Inter User Communication Vehicle). </td></tr>		<td>IBM TCP/IP IUCV (Inter User Communication Vehicle). </td></tr>

			<tr rowspan="2">
			<td rowspan="2">IPV6 only</td>
			<td><b>IBMV6</b></td>
			<td>Auto-detect the "best" IBM TCP/IP interface. For CMS, this is IUCVV6.
			<p>
			This option is available as of version 7.7 of Model 204.</p></td></tr>

	<tr>		<tr>
	~~<td>IPV6 only</td>~~
	<td><b>IUCVV6</b></td>		<td><b>IUCVV6</b></td>
	<td>IBM TCP/IP IUCV (Inter User Communication Vehicle).		<td>IBM TCP/IP IUCV (Inter User Communication Vehicle).

JAL: clarify default

2016-10-03T19:24:12Z

clarify default

← Older revision		Revision as of 19:24, 3 October 2016
Line 16:		Line 16:
	==Description==		==Description==
	This parameter specifies the type of TCP/IP network to which Model 204 is connected.		This parameter specifies the type of TCP/IP network to which Model 204 is connected.
	Generally, you can ~~leave~~ this parameter ~~at its~~ default value. Janus then automatically detects the type of TCP/IP you have on your machine, and it ~~sets~~ the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly set.		Generally, you can let this parameter default (<var>UNKNOWN</var> is default value). Janus then automatically detects the type of TCP/IP you have on your machine, and it resets the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly set.

	If you specify type <var>IBM</var> or <var>IBMV6</var>, Janus detects and sets the type of IBM interface it will use, as shown in the table below.		If you specify type <var>IBM</var> or <var>IBMV6</var>, Janus detects and sets the type of IBM interface it will use, as shown in the table below.

	You can also override auto-detection by explicitly supplying a <var>TCPTYPE</var> parameter value.		You can also override auto-detection by explicitly supplying a <var>TCPTYPE</var> parameter value.
	The ~~only~~ reason to do this would be if you have multiple TCP/IP stacks installed and you want to force use of the non-preferred stack.		The likely reason to do this would be if you have multiple TCP/IP stacks installed, and you want to force use of the non-preferred stack.

	The valid <var>TCPTYPE</var> values are in the third column below:		The valid <var>TCPTYPE</var> values are in the third column below:

JAL: /* Description */ IPV6 must be explicitly set

2016-09-15T20:06:28Z

Description: IPV6 must be explicitly set

← Older revision		Revision as of 20:06, 15 September 2016
Line 16:		Line 16:
	==Description==		==Description==
	This parameter specifies the type of TCP/IP network to which Model 204 is connected.		This parameter specifies the type of TCP/IP network to which Model 204 is connected.
	Generally, you can leave this parameter at its default value. Janus then automatically detects the type of TCP/IP you have on your machine, and it sets the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly ~~requested~~.		Generally, you can leave this parameter at its default value. Janus then automatically detects the type of TCP/IP you have on your machine, and it sets the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly set.

	If you specify type <var>IBM</var> or <var>IBMV6</var>, Janus detects and sets the type of IBM interface it will use, as shown in the table below.		If you specify type <var>IBM</var> or <var>IBMV6</var>, Janus detects and sets the type of IBM interface it will use, as shown in the table below.

JAL: IPV4 values are default

2016-09-15T20:03:59Z

IPV4 values are default

← Older revision		Revision as of 20:03, 15 September 2016
Line 16:		Line 16:
	==Description==		==Description==
	This parameter specifies the type of TCP/IP network to which Model 204 is connected.		This parameter specifies the type of TCP/IP network to which Model 204 is connected.
	Generally, you can leave this parameter at its default value ~~and let~~ Janus automatically ~~detect~~ the type of TCP/IP you have on your machine.		Generally, you can leave this parameter at its default value. Janus then automatically detects the type of TCP/IP you have on your machine, and it sets the <var>TCPTYPE</var> value accordingly. In this case, IPV4 values are preferred; IPV6 values must be explicitly requested.

	If you specify type <var>IBM</var> or <var>IBMV6</var>, Janus detects and sets the type of IBM interface it will use, as shown in the table below.		If you specify type <var>IBM</var> or <var>IBMV6</var>, Janus detects and sets the type of IBM interface it will use, as shown in the table below.

JAL: update Description for 7.7 and IPV6; put values in table

2016-09-14T00:18:57Z

update Description for 7.7 and IPV6; put values in table

@@ Line 13: / Line 13: @@
 <dd>Before <var class="product">Sirius Mods</var> 6.7
 </dl>
 ==Description==
-This parameter specifies the type of TCP/IP network to which Model 204 is connected.
+This parameter specifies the type of TCP/IP network to which Model&nbsp;204 is connected.
-Generally, you can leave this parameter at its default value and let Janus automatically
+Generally, you can leave this parameter at its default value and let Janus automatically detect the type of TCP/IP you have on your machine.
 detect the type of TCP/IP you have on your machine.
-If you specify type IBM, Janus detects and sets the type of IBM interface it will use:
+<tr>
-* Under CMS, this is always IUCV.
+<tr>
-* Under MVS, Janus will select the IBM interface in the following order: BPX (Unix System Services), HPNS, then IUCV.
+<td>IPV6 only</td>
-* If multiple types are installed, Janus will select the interface in the following order for MVS: BPX, HPNS, IUCV, Interlink, then KNET. For CMS the order is IUCV, then KNET.
+<td><b>IUCVV6</b></td>
-You can always override auto-detection by explicitly supplying a TCPTYPE parameter.
+<tr>
-The only reason to do this would be if you have multiple TCP/IP stacks installed and you
+<td>z/VSE</td>
-want to force use of the non-preferred stack.
+<td>IPV4 only</td>
-The valid TCPTYPE values are:
+Most of the communication with the TCP/IP address space is accomplished with a [[Controlling system operations (CCAIN)#Pseudo subtasks|Pseudo subtask (PST)]].
-<dl>
+Because of this, you may need to increase the <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter by 1 before using Janus.
 [[Category:System parameters]]
 [[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-08-27T16:48:08Z

Automatically generated page update

← Older revision		Revision as of 16:48, 27 August 2013
Line 1:		Line 1:
			{{Template:TCPTYPE parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>
Line 29:		Line 30:
	The valid TCPTYPE values are:		The valid TCPTYPE values are:
	<dl>		<dl>
	<dt>IBM <dd>Specifies IBM TCP/IP. This means to auto-detect the ~~“best”~~ IBM TCP/IP interface. For CMS, this is always IUCV. For MVS, Janus will look for BPX, HPNS, then IUCV.		<dt>IBM <dd>Specifies IBM TCP/IP. This means to auto-detect the “best” IBM TCP/IP interface. For CMS, this is always IUCV. For MVS, Janus will look for BPX, HPNS, then IUCV.
	<dt>BPX <dd>Specifies IBM BPX (Unix System Services) (MVS only).		<dt>BPX <dd>Specifies IBM BPX (Unix System Services) (MVS only).
	<dt>HPNS <dd>Specifies IBM HPNS (High Performance Native Sockets) (MVS only). Note that despite its name, HPNS's performance is not nearly as good as BPX's.		<dt>HPNS <dd>Specifies IBM HPNS (High Performance Native Sockets) (MVS only). Note that despite its name, HPNS's performance is not nearly as good as BPX's.

DmeWiccan: 1 revision

2012-06-22T19:25:06Z

1 revision

New page

==Summary==
<dl>
<dt>Default value
<dd>UNKNOWN
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before <var class="product">Sirius Mods</var> 6.7
</dl>
==Description==
This parameter specifies the type of TCP/IP network to which Model 204 is connected.
Generally, you can leave this parameter at its default value and let Janus automatically
detect the type of TCP/IP you have on your machine.

If you specify type IBM, Janus detects and sets the type of IBM interface it will use:

* Under CMS, this is always IUCV.
* Under MVS, Janus will select the IBM interface in the following order: BPX (Unix System Services), HPNS, then IUCV.
* If multiple types are installed, Janus will select the interface in the following order for MVS: BPX, HPNS, IUCV, Interlink, then KNET. For CMS the order is IUCV, then KNET.

You can always override auto-detection by explicitly supplying a TCPTYPE parameter.
The only reason to do this would be if you have multiple TCP/IP stacks installed and you
want to force use of the non-preferred stack.

The valid TCPTYPE values are:
<dl>
<dt>IBM <dd>Specifies IBM TCP/IP. This means to auto-detect the “best” IBM TCP/IP interface. For CMS, this is always IUCV. For MVS, Janus will look for BPX, HPNS, then IUCV.
<dt>BPX <dd>Specifies IBM BPX (Unix System Services) (MVS only).
<dt>HPNS <dd>Specifies IBM HPNS (High Performance Native Sockets) (MVS only). Note that despite its name, HPNS's performance is not nearly as good as BPX's.
<dt>INTERLNK <dd>Specifies InterLink TCP/IP (MVS only).
<dt>CSI <dd>Specifies Connectivity Systems TCP/IP (VSE only).
</dl>
Most of the communication with the TCP/IP address space is accomplished via a PST.
Because of this, you may need to increase NSUBTKS by 1 before using Janus.

[[Category:System parameters]]
[[Category:Parameters]]

Dessick: Initial edit from system parameters reference

2010-10-05T16:34:00Z

Initial edit from system parameters reference

New page

<dl>
<dt>Default value
<dd>UNKNOWN
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter specifies the type of TCP/IP network to which Model 204 is connected.
Generally, you can leave this parameter at its default value and let Janus automatically
detect the type of TCP/IP you have on your machine.

If you specify type IBM, Janus detects and sets the type of IBM interface it will use:

* Under CMS, this is always IUCV.
* Under MVS, Janus will select the IBM interface in the following order: BPX (Unix System Services), HPNS, then IUCV.
* If multiple types are installed, Janus will select the interface in the following order for MVS: BPX, HPNS, IUCV, Interlink, then KNET. For CMS the order is IUCV, then KNET.

You can always override auto-detection by explicitly supplying a TCPTYPE parameter.
The only reason to do this would be if you have multiple TCP/IP stacks installed and you
want to force use of the non-preferred stack.

The valid TCPTYPE values are:
<dl>
<dt>IBM <dd>Specifies IBM TCP/IP. This means to auto-detect the “best” IBM TCP/IP interface. For CMS, this is always IUCV. For MVS, Janus will look for BPX, HPNS, then IUCV.
<dt>BPX <dd>Specifies IBM BPX (Unix System Services) (MVS only).
<dt>HPNS <dd>Specifies IBM HPNS (High Performance Native Sockets) (MVS only). Note that despite its name, HPNS's performance is not nearly as good as BPX's.
<dt>INTERLNK <dd>Specifies InterLink TCP/IP (MVS only).
<dt>CSI <dd>Specifies Connectivity Systems TCP/IP (VSE only).
</dl>
Most of the communication with the TCP/IP address space is accomplished via a PST.
Because of this, you may need to increase NSUBTKS by 1 before using Janus.

[[Category:System Parameters]]
[[Category:Parameters]]