TCPNAME parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:TCPNAME parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 10: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V3.1.0</var> | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
The name you assign to the IBM module that provides TCP/IP support for Connect | The name you assign to the IBM module that provides TCP/IP support for Connect<span class="superstar">★</span> for UNIX TCP/IP connections | ||
<ul> | <ul> | ||
<li> | <li> | ||
Latest revision as of 21:17, 20 March 2018
TCP/IP service machine name
Summary
- Default value
- TCPIP
- Parameter type
- User
- Where set
- On User 0's parameter line
- Related products
- All
- Introduced
- Model 204 V3.1.0
Description
The name you assign to the IBM module that provides TCP/IP support for Connect★ for UNIX TCP/IP connections
- Under z/OS, set TCPNAME to the job name of the address space running the IBM TCP/IP module. Under z/OS, this parameter is set to the job name of the TCPIP server address space, which defaults to TCPIP. If this job name differs at all from TCPIP, then set the TCPNAME parameter.
- Under z/VM, set TCPNAME to the VMID of the virtual machine running the IBM TCP/IP module.
-
Under z/VSE, the system programmer can start TCP/IP stacks in one or more z/VSE partitions, and each TCP/IP stack has its own system ID. Use TCPNAME to pass the system ID of the TCP/IP stack in the format:
TCPNAME=00, TCPNAME=01...TCPNAME=nn