TCPTYPE parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
 
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:TCPTYPE parameter subtitle}}
==Summary==
==Summary==
<dl>
<dl>
Line 12: Line 13:
<dd>Before <var class="product">Sirius Mods</var> 6.7
<dd>Before <var class="product">Sirius Mods</var> 6.7
</dl>
</dl>
==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&nbsp;204 is connected.
Generally, you can leave this parameter at its default value and let Janus automatically
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.
detect the type of TCP/IP you have on your machine.
 
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.
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:
<table>
<tr class="head"><th>Operating system</th><th>Network version</th><th>Value</th><th>Meaning</th></tr>
 
<tr>
<td rowspan="7">z/OS</td>
<td rowspan="5">IPV4 only</td>
<td><b>IBM</b></td>
<td>Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPX. </td></tr>
 
<tr>
<td><b>BPX</b></td>
<td>IBM BPX (Unix System Services). </td></tr>
 
<tr>
<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. No longer supported as of version 7.9 of Model&nbsp;204. </td></tr>
 
<tr>
<td><b>INTERLNK</b></td>
<td>InterLink TCP/IP. No longer supported as of version 7.9 of Model&nbsp;204.</td></tr>
 
<tr>
<td><b>IUCV</b></td>
<td>IBM TCP/IP IUCV (Inter User Communication Vehicle). </td></tr>
 
<tr>
<td rowspan="2">IPV6 only</td>
<td><b>IBMV6</b></td>
<td>Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPXV6.
<p>
This option is available as of version 7.7 of Model&nbsp;204.</p></td></tr>


If you specify type IBM, Janus detects and sets the type of IBM interface it will use:
<tr>
<td><b>BPXV6</b></td>
<td>IBM BPX (Unix System Services). <p>
This option is available as of version 7.7 of Model&nbsp;204.</p></td></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 rowspan="4">CMS</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 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>IBM TCP/IP IUCV (Inter User Communication Vehicle). </td></tr>


You can always override auto-detection by explicitly supplying a TCPTYPE parameter.
<tr rowspan="2">
The only reason to do this would be if you have multiple TCP/IP stacks installed and you
<td rowspan="2">IPV6 only</td>
want to force use of the non-preferred stack.
<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&nbsp;204.</p></td></tr>


The valid TCPTYPE values are:
<tr>
<dl>
<td><b>IUCVV6</b></td>
<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.
<td>IBM TCP/IP IUCV (Inter User Communication Vehicle).
<dt>BPX <dd>Specifies IBM BPX (Unix System Services) (MVS only).
<p>
<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.
This option is available as of version 7.7 of Model&nbsp;204.</p></td></tr>
<dt>INTERLNK <dd>Specifies InterLink TCP/IP (MVS only).
 
<dt>CSI <dd>Specifies Connectivity Systems TCP/IP (VSE only).
<tr>
</dl>
<td>z/VSE</td>
Most of the communication with the TCP/IP address space is accomplished via a PST.
<td>IPV4 only</td>
Because of this, you may need to increase NSUBTKS by 1 before using Janus.
<td><b>CSI</b></td>  
<td>Connectivity Systems TCP/IP. </td></tr>
</table>
 
Most of the communication with the TCP/IP address space is accomplished with a [[Controlling system operations (CCAIN)#Pseudo subtasks|Pseudo subtask (PST)]].
Because of this, you may need to increase the <var>[[NSUBTKS parameter|NSUBTKS]]</var> parameter by 1 before using Janus.


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

Latest revision as of 17:11, 6 February 2024

Type of TCP/IP server address space

Summary

Default value
UNKNOWN
Parameter type
System
Where set
User 0 CCAIN parameters
Related products
All
Introduced
Before Sirius Mods 6.7

Description

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

If you specify type IBM or IBMV6, 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 TCPTYPE parameter value. 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 TCPTYPE values are in the third column below:

Operating systemNetwork versionValueMeaning
z/OS IPV4 only IBM Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPX.
BPX IBM BPX (Unix System Services).
HPNS 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.
INTERLNK InterLink TCP/IP. No longer supported as of version 7.9 of Model 204.
IUCV IBM TCP/IP IUCV (Inter User Communication Vehicle).
IPV6 only IBMV6 Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPXV6.

This option is available as of version 7.7 of Model 204.

BPXV6 IBM BPX (Unix System Services).

This option is available as of version 7.7 of Model 204.

CMS IPV4 only IBM Auto-detect the "best" IBM TCP/IP interface. For CMS, this is IUCV.
IUCV IBM TCP/IP IUCV (Inter User Communication Vehicle).
IPV6 only IBMV6 Auto-detect the "best" IBM TCP/IP interface. For CMS, this is IUCVV6.

This option is available as of version 7.7 of Model 204.

IUCVV6 IBM TCP/IP IUCV (Inter User Communication Vehicle).

This option is available as of version 7.7 of Model 204.

z/VSE IPV4 only CSI Connectivity Systems TCP/IP.

Most of the communication with the TCP/IP address space is accomplished with a Pseudo subtask (PST). Because of this, you may need to increase the NSUBTKS parameter by 1 before using Janus.

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=TCPTYPE_parameter&oldid=120052"