TCPTYPE parameter: Difference between revisions
m (→Description: IPV6 must be explicitly set) |
m (clarify default) |
||
| 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 | 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 | 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: | ||
Revision as of 19:24, 3 October 2016
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.
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 system | Network version | Value | Meaning |
|---|---|---|---|
| z/OS | IPV4 only | IBM | Auto-detect the "best" IBM TCP/IP interface. For z/OS, this is BPX. For CMS, this is IUCV. |
| 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. | ||
| INTERLNK | InterLink TCP/IP. | ||
| 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. For CMS, this is IUCVV6.
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 | IUCV | IBM TCP/IP IUCV (Inter User Communication Vehicle). |
| IPV6 only | 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.