The TCP/IP customization panels collect information to build a simple configuration based on values you provide. Output consists of PROFILE.TCPIP, TCPIP.DATA, PORTS, an omproute.conf file (if applicable), and a TN3270 file (if applicable). Use this worksheet in preparation for filling in data on the customization panels. The numbers in parentheses indicate the maximum field length; asterisks indicate the required fields.
General IP Definitions
Location where you want your IBM TCP/IP Configuration Demo for z/OS generated configuration files to be placed.
Data set name _______________________________
Volume serial _______________________________
Start procedure _______________________________
The member name of the procedure you will use to start the TCP/IP stack.
Default is TCPIP (recommended).
TCP/IP host name (66) _______________________________
TCP/IP domain origin (66) ______________________________________
Data set prefix (dsprefix) that you want to use as the high-level qualifier for dynamic allocation of data sets in this TCP/IP (26) __________________________
IP address of the name server(s) you want to configure
______.______.______.______ (You can specify more than one.)
Port reservations ( you will likely specify more than one.)
Port number __________
Protocol (TCP or UDP) __________
Jobname __________
Network Connections
General
Routing Information
Select which kind of routing you want this TCP/IP configuration to use:
Direct routes only ___
Default routers ___ (You can specify more than one default router.)
IP address of the default router ______.______.______.______
Routing Information Protocol (RIP) ___
Open Shortest Path First (OSPF) ___
Pre-filled Fields
Pre-fill IP address fields with this address ______.______.______.______
(Specify an entire address or just the first one, two or three segments.)
Pre-filled subnet mask ______.______.______.______
(Specify the entire mask or just the first one, two or three segments.)
Devices and Links
There are 13 device types. You can create multiples of each device type; one of each type is given as an example of the information you will need to create that device type.
ATM
ARP servers
ARP server name* (16) _____________________________
If connected by SVC:
IP address* ______.______.______.______
NSAP* (40-digit hex value)
_____________________________________________
If connected by PVC, PVC name* (8) _________________
ATM LIS
LIS name* (16) __________________________
Subnet value* ______.______.______.______
Subnet mask* ______.______.______.______
ATM ARP server name (16) _____________________
ATM device
Device name* (8) __________________
Port name* (8) __________________
Link information (Define one or more links.)
Link type*:
If a PVC, PVC name (8) ______________
If an SVC, LIS name (16) _______________________
Link name* (16) _______________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Translates (You can define more than one.):
Translate's IP address* ______.______.______.______
Translate's physical address* (exactly 40 hex digits)
______________________________
Neighbor(s): Applies to RIP or OSPF routing: this TCP/IP will exchange RIP or
OSPF dynamic routing protocols with a router that directly connects to this link
only if you configure that router's IP address as a RIP or OSPF neighbor
on this link.
- For RIP, IP address of a neighboring router on this link
______.______.______.______
- For OSPF, IP address of a neighboring router on this link
______.______.______.______
Is it eligible to be a designated router? ____
CDLC
Device name* (16) _________________________
Device number* (0000 - FFFF) __________
Link information (Define only one link for this device):
Link name* (16) ________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Address of device at other end of this point-to-point link*
______.______.______.______
CLAW
Device name* (16) __________
Device number* (0000 - FFFF) ______________________
Host name* (8) ______________
Workstation name* (8) _________________
Link information (Define only one link for this device):
Link name* (16) ________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Address of device at other end of this point-to-point link*
______.______.______.______
CTC
Device name* (16) ___________________________
Device number* (0000 - FFFF) __________
Link information (Define only one link for this device):
Link name* (16) ________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Adapter address:* read or write ____
Address of device at other end of this point-to-point link*
_____.______.______.______
HYPERchannel
Device name* (16) __________________________
Device number* (0000 - FFFF) __________
Link information (Define only one link for this device):
Link name* (16) ________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Translations (You can define more than one.):
Translation IP address* ______.______.______.______
Translation physical address* (exactly 12 hex digits)
________________________
Neighbor(s): Applies to RIP or OSPF routing: this TCP/IP will exchange RIP or
OSPF dynamic routing protocols with a router that directly connects to this link
only if you configure that router's IP address as a RIP or OSPF neighbor
on this link.
- For RIP, IP address of a neighboring router on this link
______.______.______.______
- For OSPF, IP address of a neighboring router on this link
______.______.______.______
Is it eligible to be a designated router? ____
LCS or OSA
Device name* (16) ____________________________
Device number* (0000 - FFFF) __________
Link information (Define one or more links.):
Link name* (16) __________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Link number* ____
Protocol*: ETHERNET, 802.3, ETHERor802.3, IBMTR, or FDDI
Translations (You can define more than one.):
Translation IP address* ______.______.______.______
Translation physical address* (exactly 12 hex digits)
_______________________
MPCIPA
Device name* (8) ____________________
Link information (Define only one link for this device):
Link name* (16) _____________________________
IP address* _____._____._____._____
Subnet mask _____._____._____._____
Protocol*: IPAQENET or IPAQTR
MPCOSA
Device name* (8) ____________________
Link information (Define only one link for this device):
Link name* (16) __________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Protocol*: OSAENET or OSAFDDI
Neighbor(s): Applies to RIP or OSPF routing: this TCP/IP will exchange RIP or
OSPF dynamic routing protocols with a router that directly connects to this link
only if you configure that router's IP address as a RIP or OSPF neighbor
on this link.
- For RIP, IP address of a neighboring router on this link
______.______.______.______
- For OSPF, IP address of a neighboring router on this link
______.______.______.______
Is it eligible to be a designated router? ____
MPCPTP
Device name* (8) ____________________
Link information (Define only one link for this device):
Link name* (16) ________________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
SNA LU 0
Device name* (16) ________________________________
Procedure name* (8) ______________________
LU name* (8) ___________________
Link information (Define only one link for this device):
Link name* (16) ____________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Address of device at other end of this point-to-point link*
______.______.______.______
SNA LU 6.2
Device name* (16) ______________________________
Procedure name* (8) ______________________
Link information (Define only one link for this device):
Link name* (8) __________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Address of device at other end of this point-to-point link*
_____._____._____._____
VIPA
Device name* (16) ____________________________
Link information (Define only one link for this device):
Link name* (16) ____________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
X.25 NPSI
Device name* (16) ______________________________
Procedure name* (8) __________________
Link information (Define only one link for this device):
Link name* (16) ____________________________
IP address* ______.______.______.______
Subnet mask ______.______.______.______
Address of device at other end of this point-to-point link*
______.______.______.______
FTP server
Will you use:
FTP ___
Telnet 3270 server
Which port or ports the server should listen on:
Port number(s) ________
Link name or link IP address ________________
The listening port can be qualified by a specific link
Should the port use SSL security ________
If the port is using SSL security
Location of the certificate keyring database ________________
Do you want to use client authentication? ________
Do you want to use express logon? _________
Do you want to select the encryption algorithms? ________
List of SNA logmodes to use with the TN3270 device types. ________________
Inactivity timers
Scan interval ________
Timing mark interval ________
Inactivity timer ________
Do you want SMF connection initiation and termination records? ________
Do you want clients to be able to take over other client's inactive sessions? ________
How do you want to indicate to the server how to connect clients to SNA LUs and applications?
Use default LU pools? ________
Names of the LUs in the default terminal pools ________________
Names of the LUs in the default printer pools ________________
Name of the application for full screen terminal clients ________
Or name of the USS table used to send USSMSG10 to terminal clients ________
Name of application for line mode clients ________
Name of application for printer clients ________
Use client identifiers? ________
Which type of client identifiers do you want to use to identify your clients? ________
User ids
Host names
IP addresses
Link names
Link IP addresses
For each type of client identifier you can define a single entry or a group?
If it is a single entry, what is the name or IP address? ________________
If it is a group,
What is the group name? ________________
What are the entries in the group? ________________
For each client identifier you assign application access?
Name of the application for full screen terminal clients ________
Name of the USS table used to send USSMSG10 to terminal clients ________
Name of the application for line mode clients ________
Name of the application for printer clients ________
For each client identifier you assign SNA LUs. The LUs can be either single LU names or groups of LUs.
If assigning single LUs, what are the LU names? ______________
If assigning groups of LUs
What are the group names? _________________
What are the names of the LUs in the group? ________________
*** IMPORTANT : Configuration Data Search Order ***
TCP/IP offers many alternative locations for the same configuration data. The
components of TCP/IP look through lists of specific DD names, specific
environment variable assignments, or alternative data set names or file names
until the configuration data is found. Throughout this checklist we present an
example location for each configuration file. If these examples do not suit your
local environment, please read Chapter 1, "Configuration Overview", of the IP
Configuration Guide, SC31-8725, to understand the search order for configuration
files used by TCP/IP functions, and to learn how you can accommodate your local
data set and HFS file naming standards.
*** END : Configuration Data Search Order ***
The following steps should help you install TCP/IP.
Copy the generated configuration files
Copy the sample TCP/IP procedure
Copy the sample OMPROUTE procedure
Update your local TSO logon procedures
Copy the syslogd configuration command
Setup when starting a TN3270 Server in its own address space
Security considerations for the FTP server
Update COMMNDxx, IEASYSxx, IVTPRMxx
Define the z/OS UNIX file system parameters for TCP/IP in BPXPRMxx
TCP/IP will produce configuration files using the names of the data set you specified during customization. If you did not specify a data set name, it defaults to TCPIP.CONFIG. The configuration file members are automatically named TCPDATA, PROFILE, OMPROUTE, PORTS, TN3270 and members representing the FTP server and FTP client configurations. If your desired data set name is not the same name you entered during customization, you may copy your configuration file members into your desired data set.
In the following steps we assume that the data set name is TCPIP.CONFIG. If your data set name is different, then substitute TCPIP.CONFIG with your data set name in the rest of these instructions.
Copy the sample TCP/IP procedure from the hlq.SEZAINST(TCPIPROC) to your system or recognized PROCLIB, such as SYS1.PROCLIB, and modify it to suit your local configuration.
For example:
set //PROFILE DD to TCPIP.CONFIG(PROFILE)
set //SYSTCPD DD to TCPIP.CONFIG(TCPDATA)
set the RESOLVER_CONFIG environment variable to TCPIP.CONFIG(TCPDATA)
For more information, please see section 'Configuration Files for the TCP/IP Stack' in the IP Configuration Guide.
Copy the sample OMPROUTE procedure from the hlq.SEZAINST(OMPROUTE) to your system or recognized PROCLIB, such as SYS1.PROCLIB, and modify it to suit your local configuration.
For example, set the ENVAR("_CCE_ENVFILE=DD:xxxx") parameter on the OMPROUTE EXEC statement to point to the DD statement which specifies the location of your omproute environment file:
//OMPROUTE EXEC PGM=OMPROUTE,REGION=4096K,TIME=NOLIMIT, PARM=('POSIX(ON)',
'ENVAR("_CCE_ENVFILE=DD:STDENV")/')
.
.
.
//STDENV DD PATH='/u/usernnn/envcs2'
Then, in your omproute environment file, set the OMPROUTE_FILE environment variable to point to your MVS data set or HFS file containing the configuration data, and set the RESOLVER_CONFIG environment variable to TCPIP.CONFIG(TCPDATA). For example,
RESOLVER_CONFIG = //'TCPIP.CONFIG(TCPDATA)'
OMPROUTE_FILE = //'TCPIP.CONFIG(OMPROUTE)'
For more information, please see section 'Configuring OMPROUTE' in the IP Configuration Guide.
Copy the generated FTP procedure to your recognized PROCLIB, such as SYS1.PROCLIB, and change the data set names to suit your local configuration.
For example make sure the //SYSFTPDD and //SYSTCPD DD statements point to the correct file locations. Also, if you have your own translation table used for FTP control connections, make sure the environment variable, "_FTPXLATE_MSYS=", in the start procedure point to the correct file location.
Update your TSO logon procedures by adding the TCP/IP help data set hlq.SEZAHELP to the //SYSHELP DD concatenation. Optionally, add the //SYSTCPD DD statement to your logon procedures.
For VMCF and TNF, add the following procedure EZAZSSI to your system or recognized PROCLIB, such as SYS1.PROCLIB.
//EZAZSSI PROC P='nodename'
//STARTVT EXEC PGM=EZAZSSI,PARM=&P
//STEPLIB DD DSN=hlq.SEZATCP,DISP=SHR
1. Copy the following syslogd configuration to /etc/syslog.conf
*.* /var/log/syslog.log
2. From the OS/390 UNIX shell, create an empty file to contain the syslogd output, by executing the following command:
touch /var/log/syslog.log
When Telnet is started separately its own address space, set up for the job is necessary.
Copy the generated TNSTART procedure to your recognized PROCLIB, such as SYS1.PROCLIB, and make sure the //PROFILE DD statement points to the correct file location.
Before Telnet can be started, security for the procedure name and the associated user ID must be defined. This discussion assumes RACF is the security subsystem being used. If another security product is used, refer to its manuals for equivalent set up instructions.
The procedure name must be added to the RACF STARTED
class and have the user ID associated with it as follows:
RDEFINE STARTED TN3270*.* STDATA(USER(TN3270))
SETROPTS RACLIST(STARTED) REFRESH
Define a superuser ID to associate with the job name by
adding a user ID to RACF and altering it to superuser status as follows:
ADDUSER TN3270
ALTUSER TN3270 OMVS(UID(0) PROGRAM ('/bin/sh') HOME('/'))
In this example, the user ID name is TN3270. Any name can be used. These two RACF commands can be combined into one command by putting the OMVS parameter on the ADDUSER command line. The add and alter commands are done separately in case the user ID already exists. In that case, the add would fail but the alter would still succeed.
If setting up a superuser ID is not desirable, you can instead permit the user ID to the BPX.SUPERUSER class using the following steps:
Sample statements for adding the procedure to the STARTED class and defining a superuser ID are in hlq.SEZAINST(EZARACF). For more detail about these functions, refer to z/OS UNIX System Services Planning, z/OS Security Server RACF Security Administrator's Guide, and z/OS Security Server RACF Command Language Reference.
The MVS default program property table (PPT) has the Telnet module set up as privileged, non-swappable, non-cancelable, running in key 6, and SYST. These settings give Telnet the same priority as the TCP/IP stack. Either privileged or SYST cause the started job to be assigned to the SYSSTC service class. The priority can be changed by assigning the job name to another service class within the STC subsystem.
Evaluate your environment's security policies carefully, and then either
assign unique UIDs and GIDs to all users and groups
or
set up the default OMVS segments, as follows:
Define a Group ID (GID) to the system to be used as an anchor for a default OMVS group segment with the following RACF command:
ADDGROUP OEDFLTG OMVS(GID(777777))
Define a user ID (UID) to be used as an anchor for the default OMVS user segment by using the following RACF command:
ADDUSER OEDFLTU DFLTGRP(OEDFLTG) NAME('OE DEFAULT USER') OMVS(UID(999999)
HOME('/') PROGRAM('/bin/echo'))
Set up a default for the USER OMVS segment only (that is, create a facility class profile named BPX.DEFAULT.USER and then specify the default UID in the application data field, by using the following RACF commands:
RDEFINE FACILITY BPX.DEFAULT.USER APPLDATA('OEDFLTU')
SETROPTS RACLIST(FACILITY) REFRESH
Authorize the TCP/IP started task user ID by using the following command to assign an OMVS segment to the TCP/IP started task user ID specified as UID=0;
ADDGROUP OMVSGRP OMVS(GID(1))
ADDUSER TCPIP DFLTGRP (OMVSGRP) OMVS(UID(0) HOME('/') PROGRAM('bin/sh'))
RDEFINE STARTED TCPIPROC.* STDATA(USER(TCPIP) GROUP(OMVSGRP))
Grant superuser authority to OMPROUTE:
RDEFINE STARTED OMPROUTE.* STDATA(USER(TCPIP) GROUP(OMVSGRP))
For dynamic routing, enable OMPROUTE RACF authorization for a particular user ID by entering the following commands with the ID of the user or with the ID of the started task to be authorized:
RDEFINE OPERCMDS (MVS.ROUTEMGR.OMPROUTE) UACC(NONE)
PERMIT MVS.ROUTEMGR.OMPROUTE ACCESS(CONTROL) CLASS(OPERCMDS) ID(userid)
SETROPTS RACLIST(OPERCMDS) REFRESH
If you are using an FTP server, consider the following for security:
User IDs
To log into the FTP server, a user ID must have an OS/390 UNIX UID.
MVS Network Access Controls
If PortAccess or NetAccess is used to SAF resource secure TCP ports or networks,
see the NETACCESS statement in OS/390 IBM Communications Server: IP
Configuration Reference for more information.
The FTPD cataloged procedure must be:
Defined to the security program.
Added to the RACF started class facility or the started procedures table. The user ID associated with the FTP server started class must have a UID of 0.
See SEZAINST(EZARACF) for more information on SAF resource requirements needed for FTP.
Terminal Access
The terminal ID passed from FTP to RACF is an 8-byte hexadecimal character
string containing an IP address. RACF interprets this as a terminal logon
address and rejects it if it is not previously defined. For example, the IP
address 163.97.227.17 is translated to X'A361E311'.
Therefore, if the SETROPTS TERMINAL(NONE) setting is used in RACF, you must
define profiles for the IP addresses in class TERMINAL to avoid problems when
trying to FTP to MVS. You must translate all the IP addresses of any clients
connecting to FTP servers to hexadecimal character strings and add them to the
class TERMINAL.
To allow access by all addresses starting with "163", define a profile for all
addresses in the 163.97.227 subnet:
RDEFINE TERMINAL A361E3* UACC(READ)
If your RACF SETROPTS options are TERMINAL(READ), all terminals are allowed access to your system, and you do not have to add extra resource definitions to your RACF data base.
For more information, see OS/390 UNIX System Services Planning and the OS/390 SecureWay Security Server RACF Security Administrator's Guide.
COMMNDxx
Add the following entry to start VMCF and TNF after IPL and before you start
TCP/IP:
COM='S EZAZSSI,P=nodename'
IEASYSxx
Review your CSA and SQA specifications in IEASYSxx and verify that the numbers
allocated are large enough to prevent GETMAIN errors. We recommend:
CSA(3000,250M)
SQA(8,448)
IVTPRMxx
We recommend that you set the CSM requirements in IVTPRMxx as follows:
FIXED MAX(120M)
ECSA MAX(30M)
Make the following updates to your BPXPRMxx parmlib member:
FILESYSTYPE TYPE(INET) ENTRYPOINT(EZBPFINI)
NETWORK
DOMAINNAME(AF_INET)
DOMAINNUMBER(2)
MAXSOCKETS(64000)
TYPE(INET)
Do the following steps to verify your configuration. The commands can be issued from either ISPF option 6 or the UNIX IShell.
Check the syslog for message EZZ4200I TCP/IP Stack Functions Initialization Complete.
PING 127.0.0.1 to verify the loopback address is working.
PING each address in the 'home' list of your TCPIP.PROFILE configuration file.
PING some other node on each link in your configuration.
PING your domain name servers.
NETSTAT command will provide diagnostic information if your configuration does not appear to be working correctly. See Ch. 11 of the IP User's Guide for more information.
Use to designate the ATM ARP server that will resolve ATM ARP requests for a logical IP subnet (LIS). This ATM ARP server returns the ATM physical address (NSAP) associated with an IP address in the LIS. Typically an ATM ARP server is a device connected to the LIS, and typically all other devices in the LIS register their internet and ATM physical addresses with the ATM ARP server. When an ATM device is started, TCP/IP will attempt to establish a connection to the ATM ARP server for any link associated with a device that both specifies a LIS and has a corresponding ATM ARP server defined.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies the ATM ARP server to resolve ARP requests for this LIS; ATMARPSERVER1, for example.
Rules:
An ATM ARP server name has a maximum length of 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Each ATM ARP server connects via a Permanent Virtual Circuit (PVC) or a Switched Virtual Circuit (SVC). Configuration parameters vary depending on the type of connection. Select either PVC or SVC and you will be shown the additional configuration parameters to customize. Note that some ATM ARP server products do not support being used as an ATM ARP server over a PVC connection.
Use to specify the PVC name of the connection to the ATM ARP server; ATMPVC1, for example. This is required only if the connection to the ATM ARP server is a permanent virtual circuit (PVC).
Rules:
A PVC name has a maximum length of 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
This name must match the pvc defined for the ATM port in the ATM native settings in the OSA configuration, which may further restrict the set of valid names.
Use to specify the IP address of the ATM ARP server; 10.1.180.254, for example. This is required only if the connection to the ATM ARP server is a switched virtual circuit (SVC).
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the physical address, or Network Service Access Point (NSAP), of the ATM ARP server; 123456789A123456789B123456789C123456789D, for example. This is required only if the connection to the ATM ARP server is a switched virtual circuit (SVC).
Rules:
Specify a 40-digit hexadecimal value.
Use to describe the characteristics of an ATM logical IP subnet (LIS). All hosts and routers in a given LIS must be in the same subnet, that is, they must have the same subnet mask and the same subnet value. A LIS is a separate administrative ATM entity. Each logical IP subnet operates and communicates independently of other logical IP subnets on the same ATM network.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this ATM logical IP subnet; ATMLIS1, for example.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the subnet value (in dotted decimal notation) that defines this logical IP subnet; 10.1.128.0, for example.
Rules:
The subnet value must be in the subnet mask; that is, any bit in the subnet value that is a one-bit also must be a one-bit in the subnet mask.
Use to specify the subnet mask (in dotted decimal notation) for this Logical IP
Subnet (LIS); 255.255.192.0, for example. The logical AND of the subnet mask and
any IP address in this LIS should result in the subnet value;
255.255.192.0 AND 10.1.180.254 = 10.1.128.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Use to designate the ATM ARP server that will resolve ATM ARP requests for a logical IP subnet (LIS). This ATM ARP server returns the ATM physical address (NSAP) associated with an IP address in the LIS. Typically an ATM ARP server is a device connected to the LIS, and typically all other devices in the LIS register their internet and ATM physical addresses with the ATM ARP server. When an ATM device is started, TCP/IP will attempt to establish a connection to the ATM ARP server for any link associated with a device that both specifies a LIS and has a corresponding ATM ARP server defined. Some ATM ARP server products cannot be used as an ATM ARP server over a PVC connection.
Select an ATM ARP server from this list. If you need to define another ATM ARP server, return to the ATM ARP server panel.
Use to define a link associated with this ATM device. This link will be connected via a Permanent Virtual Circuit (PVC).
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
Use to specify the name by which this TCP/IP identifies this permanent virtual circuit on the ATM network; for example, LINK1.
Rules:
The maximum length is 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
This name must match the name of the PVC defined in the Open Systems Adapter (OSA) configuration in the ATM native settings for the ATM port.
For OSPF and RIP routing, enter the IP address for each router connected via this link.
Use to define a link associated with this ATM device. This link will be connected via a Switched Virtual Circuit (SVC) and will serve a specified Logical IP Subnet (LIS).
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
Select the Logical IP Subnet (LIS) to be served via this link. This parameter is only required for links used as a Switched Virtual Circuit (SVC).
If you need to define another LIS, return to the Logical IP Subnets (LIS) customization panel.
For OSPF and RIP routing, enter the IP address for each router connected via this link.
Use translate to indicate the relationship between an IP address and the physical address on this ATM link.
Use translate to indicate the relationship between an IP address and the physical address on a specified link. You can use translate for ATM, HYPERchannel, Ethernet, FDDI, and token ring hosts for which ARP is not supported. Translate is not valid for virtual devices, or point-to-point devices like CTC.
You can find more detailed help on the following elements of this window:
Use to specify the IP address of the translation; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the network address corresponding to IP address and link name.
Rules:
For ATM, specify a 40-digit hexadecimal value.
Use to designate the ATM ARP server that will resolve ATM ARP requests for a logical IP subnet (LIS). The ATM ARP server returns the ATM physical address (NSAP) associated with an IP address in the LIS. Typically, an ATM ARP server is a device connected to the LIS, and all other devices in the LIS register their internet and ATM physical addresses with the ATM ARP server. When an ATM device is started, TCP/IP will attempt to establish a connection to the ATM ARP server for any link associated with a device that both specifies a LIS and has a corresponding ATM ARP server defined.
Use to specify the name of the asynchronous transfer mode (ATM) device that you use. You can specify multiple links for an ATM device. This allows a single ATM device in more than one logical IP subnet (LIS).
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
The device name must be the OSA name known to MPC and OSA/SF, which may further restrict the set of valid names.
This name, the OSA name, must match the name specified on the transport resource list element (TRLE).
For more information on the TRLE, see the z/OS IBM Communications Server: SNA Resource Definition Reference.
Use to specify the name by which this TCP/IP identifies this Open Systems Adapter (OSA) port; for example, PORT1.
Rules:
The maximum length is 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
This name must match the portname specified on the transport resource list element (TRLE), which may further restrict the set of valid names.
For more information on the TRLE, see the z/OS IBM Communications Server: SNA Resource Definition Reference.
ATM technology provides for both Permanent Virtual Circuits (PVC) and Switched Virtual Circuits (SVC). When customizing ATM devices, the required parameters vary depending on whether you define links using PVC, SVC or both types of connectivity. Select the type of connectivity your links use so that the ATM Wizard can direct you to the proper panels and required parameters.
Use to define a network interface link associated with the ATM device. Multiple links for an ATM device may be defined allowing an ATM device to serve more than one Logical IP Subnet (LIS).
Customization parameters are different for ATM links that are connected via a Switched Virtual Circuit (SVC) or a Permanent Virtual Circuit (PVC). When adding a link you will select whether the link will be an SVC or PVC connection.
You can find more detailed help on the following elements of this window:
Use to define a Switched Virtual Circuit (SVC) link associated with the ATM device.
Customization parameters vary according to the link connectivity, SVC or PVC.
Use to define a Permanent Virtual Circuit (PVC) link associated with the ATM device.
Customization parameters vary according to the link connectivity, SVC or PVC.
Use to describe the characteristics of an ATM logical IP subnet (LIS). All hosts and routers in a given LIS must be in the same subnet, that is, they must have the same subnet mask and the same subnet value. A LIS is a separate administrative ATM entity. Each logical IP subnet operates and communicates independently of other logical IP subnets on the same ATM network.
Welcome to the ATM device customization wizard. Use the NEXT and BACK buttons to navigate through the ATM wizard. At any time you may use the CANCEL button, which will discard any data entered in the ATM wizard and return you to the Devices and links panel.
ATM links are likely to use Switched Virtual Circuit (SVC) connectivity and require ATM ARP servers to provide address resolution. Each ATM SVC link is required to connect to a single Logical IP Subnet (LIS) and each LIS must use the services of an ATM ARP server to provide address resolution. Therefore, defining SVC links differs significantly from defining Permanent Virtual Circuits (PVCs). On the first ATM customization panel you are asked whether you plan to define SVCs, PVCs, or both so that the wizard can direct you to the applicable customization panels.
For more information about ATM ARP servers and LISes see:
Incomplete ATM device configurations
When adding a device, the ATM device configuration wizard will direct you through the customization panels in a manner that will result in a complete configuration. However, it is possible to make changes that result in an incomplete or invalid configuration by navigating using the BACK button or editing a previously-defined ATM device, for example. If this occurs, the wizard will display warning messages specifically stating how the configuration is invalid and how to correct it. Certain incomplete configurations may be saved, but the TCP/IP will remain marked as incomplete.
Use to specify the name and hexadecimal device number of the Channel Data Link Control (CDLC) devices that you use.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the hexadecimal device number of the CDLC device; 6B2, for example. This is also known as the unit address.
Rules:
The device number must be greater than or equal to 0, and less than or equal to FFFF.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
You are defining a point-to-point link and need to specify the IP address of the interface at the other end of the link; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the name and hexadecimal device number of a Common Link Access to Workstation (CLAW) device. Devices that use the CLAW protocol include RISC System/6000 and SP2.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the hexadecimal device number of the RISC System/6000; 6B2, for example. This is also known as the unit address.
Rules:
The device number must be greater than or equal to 0, and less than or equal to FFFF.
TCP/IP also uses device number + 1.
Use to specify a value that defines the name of the host system in the system validation exchange between the TCP/IP code and the workstation code.
Rules:
The maximum length is 8 characters.
Each character of the name can be any non-blank printable character except ; (semicolon).
This name must be the same name that is defined as the CLAW mode HOST name in SMIT on the RISC/6000, which may further restrict the set of valid names.
Use to specify a value for the name of the workstation for the system validation exchange.
Rules:
The maximum length is 8 characters.
Each character of the name can be any non-blank printable character except ; (semicolon).
This value must be the name of the CLAW mode adapter defined in SMIT on the RISC/6000, which may further restrict the set of valid names.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
You are defining a point-to-point link and need to specify the IP address of the interface at the other end of the link; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the name and hexadecimal device number of the Channel-to-Channel (CTC) devices that you use.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the hexadecimal base device number associated with the CTC adapter; 6B2, for example. This is also known as the unit address.
Rules:
The device number must be greater than or equal to 0, and less than or equal to FFFF.
Two numbers are used by TCP/IP: the base device number and the base device number+1. One of the device numbers is used as the READ channel and the other is used as the WRITE channel.
Indicate whether the device number entered is the READ or the WRITE channel.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
You are defining a point-to-point link and need to specify the IP address of the interface at the other end of the link; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
TCP/IP communicates with other hosts through network connectivity devices, which typically control hardware that connects with other hosts via network links. You can Add, Edit or Remove any of the following types of supported devices:
Asynchronous Transfer Mode (ATM)
Channel-to-Channel (CTC)
HYPERchannel
LAN Channel Station (LCS)
Multipath Channel IP Assist-Based Interface Adapter (MPCIPA)
Multipath Channel Point-to-point (MPCPTP)
Multipath Channel Open Systems Adapter (MPCOSA)
Common Link Access to Workstation (CLAW)
Systems Network Architecture Logical Unit Type 0 Link (SNA LU 0)
Systems Network Architecture Logical Unit Type 6.2 Link (SNA LU 6.2)
Virtual Internet Protocol Address (VIPA)
X.25 Network Control Program Packet Switching Interface (X.25 NPSI)
Channel Data Link Control (CDLC)
TCP/IP communicates with other hosts through network connectivity devices, which typically control hardware that connects with other hosts via network links. Select the device type you want to configure. The following types of devices are supported:
Asynchronous Transfer Mode (ATM)
Channel-to-Channel (CTC)
HYPERchannel
LAN Channel Station (LCS)
Multipath Channel IP Assist-Based Interface Adapter (MPCIPA)
Multipath Channel Point-to-point (MPCPTP)
Multipath Channel Open Systems Adapter (MPCOSA)
Common Link Access to Workstation (CLAW)
Systems Network Architecture Logical Unit Type 0 Link (SNA LU 0)
Systems Network Architecture Logical Unit Type 6.2 Link (SNA LU 6.2)
Virtual Internet Protocol Address (VIPA)
X.25 Network Control Program Packet Switching Interface (X.25 NPSI)
Channel Data Link Control (CDLC)
Use to define the IP addresses of one or more name servers in dotted decimal notation.
A maximum of 16 name servers may be defined.
Use to define the name server's IP address in dotted decimal notation.
You can find more detailed help on the following elements of this window:
Use to specify the IP address of a name server; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
After you complete your TCP/IP customization, TCP/IP creates configuration files during the update phase. These configuration files will be placed in a Partitioned Data Set Extended (PDSE) of your choice. Select the name of the PDSe and specify the volume serial of the DASD location.
You can find more detailed help on the following elements of this window:
Use to specify the member name of the procedure used to start the TCP/IP stack. If the name you specify here is not the name you use to start TCP/IP, clients will fail at startup with an irrecoverable IP address communication error. For example, OMPROUTE relies on the value assigned to this parameter to know with which TCP/IP stack to establish a connection. If this value is incorrect, OMPROUTE will fail to start.
You can find more detailed help on the following element of this window:
Use to specify the fully qualified name of the Partitioned Data Set Extended (PDSE) where you will place your TCP/IP configuration files that are created. The GUI will produce configuration files for TCPDATA, PROFILE, OMPROUTE, PORTS, and members for FTP server and FTP client. Therefore, do not include any member names when specifying the data set name. This parameter and the volume serial identify the specific location where the TCP/IP configuration files will reside.
Rules:
A qualified name can contain up to 44 characters, including periods.
A qualified name is formed by concatenating unqualified names. Each unqualified name is called an index.
An index must be separated from the other indices by periods, for example, A.B.Z.
An index can contain up to 8 characters.
The first character of an index must be alphabetic or national (A to Z, $, @, or #).
Each subsequent character of an index must be alphanumeric, national (A to Z, 0 to 9, $, @, or #), or the hyphen (-).
The default data set name is TCPIP.CONFIG.
Use to specify the volume or portion of a storage device where the TCP/IP configuration files are to be created. This parameter, along with the data set name, identify the specific location where the TCP/IP configuration files will reside.
Rules:
The maximum length is six characters.
All characters must be either alphanumeric or national (A to Z, 0 to 9, $, @, or #).
The default will be NULL, which allows for the possibility of creating the data sets on a nonspecific volume if your system is setup to allow for nonspecific volume requests.
Use to specify the member name of the procedure used to start the TCP/IP stack.
Rules:
The default start procedure name is TCPIP.
The maximum length of the start procedure name is 8 characters.
The first character must be one of $@# or an alphabetic letter.
Each subsequent character must be one of -$@# or an alphanumeric.
Use to specify the high-level qualifier for the dynamic allocation of data sets in TCPIP; TCPIP.V2R10, for example.
Rules:
The default high-level qualifier distributed with the system is TCPIP.
The maximum length of the data set prefix is 26 characters.
The data set prefix consists of one or more character strings separated by dots (periods).
The maximum length of a character string is 8 characters.
The first character of a character string must be one of $@# or an alphabetic letter.
Each subsequent character of a character string must be one of -$@# or an alphanumeric.
The last character of the data set prefix must not be a period.
Network users may refer to your host by a fully-qualified name such as myhost.myisp.com, where myhost is the host name and myisp.com is the domain origin.
You can find more detailed help on the following elements of this window:
Use to specify the TCP host name of this z/OS server; for example, MVSADM1.
Rules:
If not specified, defaults to the nodename specified in the IEFSSNxx PARMLIB member.
The maximum length of the host name is 66 characters.
The host name consists of one or more labels separated by dots (periods).
Each label must be at least one character long.
The first character of a label must be alphanumeric.
Each subsequent character of a label must be an alphanumeric or a hyphen.
The last character of the host name must not be a period.
Use to specify the domain origin which is appended to the host name with a period in between. This forms the fully qualified domain name for a host; for example, if MVSADM1 is the host name and YOUR.ISP.COM is the domain origin, then MVSADM1.YOUR.ISP.COM is the fully qualified domain name.
Rules:
The origin name usually has imbedded dots, that is, periods.
The maximum length allowed for domain origin is 66.
The domain origin consists of one or more labels separated by periods.
Each label must be at least one character long.
The first character of a label must be an alphanumeric.
Each subsequent character of a label string must be an alphanumeric or a hyphen.
The last character of the domain origin must not be a period.
Use to specify the name and hexadecimal device number of a HYPERchannel A220 device.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the hexadecimal base device number associated with the HYPERchannel A220 adapter; 6B2, for example. This is also known as the unit address.
Rules:
The device number must be greater than or equal to 0, and less than or equal to FFFF.
Two addresses are used by TCP/IP: the base device number and base device number + 1.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
A translate is required for communication across a HYPERchannel A220 link.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
Use address translation to indicate the relationship between an IP address and the physical address on a specified link. A translation is required for communication across a HYPERchannel A220 link.
For OSPF and RIP routing, enter the IP address for each router connected via this HYPERchannel link.
Use to specify the name and hexadecimal device number of an IBM 8232 LAN Channel Station (LCS) device, an IBM 3172 Interconnect Controller, an IBM 2216 Multiaccess Connector Model 400, an IBM FDDI, Ethernet, Token Ring OSA, or an IBM ATM OSA-2 in LAN emulation mode. Note: Each network interface on the OSA adapter is considered a separate device.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the hexadecimal device number of the LCS or OSA; 6B2, for example. This is also known as the unit address.
Rules:
The device number must be greater than or equal to 0, and less than or equal to FFFF.
Device number+1 is also used by the TCP/IP address space.
Use to define one or more LCS or OSA links.
Use to define an LCS or OSA link.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
Use to specify the relative adapter number on the LCS device, or the port number on the OSA adapter.
Rules:
0 for the first Ethernet adapter in the LCS, 1 for the second Ethernet adapter, and so on.
0 for the first token ring adapter in the LCS, 1 for the second token ring adapter, and so on.
0 for the first FDDI adapter in the LCS, 1 for the second FDDI adapter, and so on.
Use to specify the local area network protocol used on this link.
Ethernet
Standard Ethernet protocol only.
IEEE 802.3
IEEE 802.3 protocol only.
Ethernet or IEEE 802.3
Both standard Ethernet and IEEE 802.3 protocols.
Note: When Ethernet or IEEE 802.3 is specified, ARP packets for both protocols are generated. All devices must be able to process or discard these packets.
IBM Token Ring
Specifies that the link is to an IBM Token Ring.
FDDI
Specifies that the link is to an FDDI network.
Use address translation to indicate the relationship between an IP address and the physical address on this LCS or OSA link.
Use to specify the PORT name contained in the transport resource list element (TRLE) definition for the Queued Direct Input/Output (QDIO) interface. The TRLE must be defined as MPCLEVEL=QDIO. For details on defining a TRLE, see the z/OS IBM Communications Server: SNA Resource Definition Reference.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
The device name must be the PORT name of the LAN adapter defined in a TRLE for a QDIO connection, which may further restrict the set of valid names.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
Ethernet
Indicates that the link uses the IP Assist based interface, belongs to the QDIO family of
interfaces, and uses the Gigabit Ethernet or Fast Ethernet protocol.
IBM Token Ring
Indicates that the link uses the IP Assist based interface, belongs to the QDIO family of
interfaces, and uses the Token Ring protocol.
When defining a Multipath Channel Open Systems Adapter (MPCOSA) connection, use this device to specify the transport resource list element (TRLE) of a High Performance Data Transfer (HPDT) connection. MPCOSA devices have an ARP offload function that offloads all ARP processing to the OSA-2 adapter. TCP/IP cannot display any ARP cache information or ARP counter statistics for these devices because OSA-2 does not provide this data to TCP/IP. MPCOSA devices cannot be configured to accept IP packets destined to an IP address other than the IP address of the OSA-2 adapter. For example, IP packets destined to a Virtual IP Address (VIPA) owned by this TCP/IP will not be delivered by the OSA-2 adapter.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
You need to use OSA/SF to configure the OSA-2 to run in HPDT MPC mode.
The device name must be the name of the TRLE definition that corresponds to the OSA-2 configuration, which may further restrict the set of valid names.
The TRLE is defined in a VTAM TRL major node and must be active to start the device.
For details on defining a TRLE, see the z/OS IBM Communications Server: SNA Resource Definition Reference.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
Ethernet
Specifies that the link is for MPCOSA Fast Ethernet OSA-2.
FDDI
Specifies that the link is for MPCOSA FDDI OSA-2.
For OSPF and RIP routing, enter the IP address for each router connected via this MPCOSA link.
MPCPTP connections allow you to define a single transmission group that uses multiple write-direction and read-direction subchannels. Because each subchannel operates in only one direction, the half-duplex turnaround time that occurs with other channel-to-channel connections is reduced.
When defining a High Performance Data Transfer (HPDT) connection, use this device to specify the name of the transport resource list element (TRLE) definition for the Multipath Channel (MPC) group. Also, the TRLE must be defined as MPCLEVEL=HPDT.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1. For HPFT MPC connections to an IBM 2216 Multiaccess Connector Model 400, an IBM RS/6000, or another z/OS host, the device name must be the TRLE name of an HPDT connection. The TRLE is defined in a VTAM TRL major node and must be active to start the device. For details on defining a TRLE, see the z/OS IBM Communications Server: SNA Resource Definition Reference.
Rules:
The maximum length is 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
The reserved TRLE name IUTSAMEH can be used to bring up an MPCPTP connection between two TCP/IP stacks on the same system without the need for a physical device connection between the two stacks. The reserved TRLE name IUTSAMEH can also be used to define an Enterprise Extender connection to the VTAM instance running on this host. If you are defining an Enterprise Extender connection, the device name must be IUTSAMEH.
VTAM automatically activates the IUTSAMEH TRLE.
For XCF connections, the device name must be the cpname of the target VTAM on the other side of the XCF connection, which may further restrict the set of allowed names. The VTAM ISTLSXCF major node must be active in both nodes to start the device. If connectivity is to a pre-OS/390 V2R8 node, the XCF TRLE must also be active.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
For OSPF and RIP routing, enter the IP address for each router connected via this link.
You can find more detailed help on the following elements of this window:
Use to specify the IP address of an OSPF or RIP router on this link; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Designated
This indicates that this router is eligible to be designated to participate in
OSPF protocol exchanges on behalf of routers on this non-broadcast multi-access
network.
Non-designated
This indicates that this router is not eligible to be designated to participate
in OSPF protocol exchanges on behalf of routers on this non-broadcast
multi-access network.
Use to define the default router's IP address in dotted decimal notation.
You can find more detailed help on the following elements of this window:
Use to specify the IP address of a default router; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
On this panel, you select:
one of four ways for TCP/IP to handle outbound data that is addressed to destinations that are not directly connected to any of the links you are configuring.
a default IP address and subnet mask to save you keystrokes as you configure links. Each link will ask you to configure an IP address and subnet mask which will be initialized using the respective defaults.
You can find more detailed help on the following elements of this window:
It is assumed your installation has already made the network design decision to use default routing or dynamic routing.
The difference between default routing and dynamic routing is whether a routing daemon is used.
Dynamic routing allows a TCP/IP stack to respond to network topology changes.
A daemon is a UNIX term for a background server process.
OMPROUTE is the recommended routing daemon application for z/OS Communications Server IP.
OMPROUTE implements the OSPF protocol described in the RFC 1583 (OSPF Version 2), the OSPF subagent protocol described in RFC 1850, and the RIP protocol described RFC 1058 (RIP Version 1).
If you choose direct routing only, TCP/IP discards any data that is not addressed to a node on a link defined on this host. Otherwise, TCP/IP can send such data to:
A default router you configure statically; this approach eliminates the host's participation in the exchange of routing protocols, but may reduce your ability to route around failed links.
A router selected dynamically by the Routing Information Protocol (RIP) version 1; this older protocol is often available in networks where OSPF has not yet been deployed.
A router selected dynamically by the Open Shortest Path First (OSPF) protocol; this approach is generally the most responsive to network changes.
Use to Add, Edit or Remove a default router using dotted decimal notation.
Specify one, two, three, or four segments of the IP address or subnet mask in decimal notation. These values will save keystrokes, prefilling internet address fields and subnet masks when defining links on subsequent customization panels.
For example you may enter all or a portion of the IP address as:
7.57.157.23 or
7.57.157 or
7.57 or
7
Specify one, two, three, or four segments of the IP address in decimal notation. This value will save keystrokes, prefilling IP address fields when defining links on subsequent customization panels.
For example you may enter all or a portion of the IP address as:
7.57.157.23 or
7.57.157 or
7.57 or
7
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Specify one, two, three, or four segments of the subnet mask in decimal notation. This value will save keystrokes, prefilling subnet mask fields when defining links on subsequent customization panels.
For example you may enter all or a portion of the subnet mask as:
255.255.255.0 or
255.255.255 or
255.255 or
255
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Use to specify the name of the address space running the SNALINK program and the LU name of the 3745 Communications Controller to which an Ethernet or token ring is attached. SNALINK allows TCP/IP to send and receive packets using SNA sessions instead of dedicating physical network hardware (such as a channel-to-channel adapter or a channel connection to a 3745/46 Communication Controller). SNALINK allows an installation to multiplex SNA and IP traffic over the same I/O subchannels, rather than requiring separate subchannels dedicated to VTAM and TCP/IP. While such multiplexing capability may be desirable at some installations, the native TCP/IP CTC and 3745/46 device drivers will likely outperform SNALINK connections. Interaction with the SNALINK address space is very CPU-intensive, and is not required with the native TCP/IP CTC and 3745/46 device drivers. It is therefore important to weigh the multiplexing capability that SNALINK provides against its performance cost, in determining whether to use SNALINK or the native TCP/IP CTC or 3745/46 device drivers. SNALINK communicates with one or more instances of SNALINK at remote nodes, using the SNA LU type 0 protocol.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the name of the SNALINK started procedure that runs on the host end; SNALINK, for example.
Rules:
The maximum length is 8 characters.
The first character of the procedure name must be one of $@# or an alphabetic letter.
Each subsequent character of the procedure name must be one of -$@# or an alphanumeric.
Use to specify the logical unit (LU) name of the remote end; LU000000, for example.
Rules:
The maximum length is 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
The LU name also must be configured in VTAM, which may further restrict the set of valid names.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
There must be only one link for each SNA LU type 0 device statement.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
You are defining a point-to-point link and need to specify the IP address of the interface at the other end of the link; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the name of the started procedure running the SNALINK LU6.2 interface program. The SNALINK LU6.2 cataloged procedure runs a VTAM application program called SNALNK62, which is an interface between the TCPIP address space and the SNA network. SNALNK62 uses SNA LU type 6.2 sessions to pass the TCP/IP data to or from SNALNK62 devices running on other hosts. Examples of SNALNK62 devices include an OS/2 workstation running TCP/IP for OS/2 or a host running TCP/IP for z/OS. There must be only one LINK statement for each SNA LU 6.2 device statement.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the name of the SNALINK started procedure that runs on the host.
Rules:
The maximum length is 8 characters.
The first character must be one of $@# or an alphabetic letter.
Each subsequent character must be one of -$@# or an alphanumeric.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 8 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
You are defining a point-to-point link and need to specify the IP address of the interface at the other end of the link; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Welcome to the IBM TCP/IP Configuration Demo for z/OS. In preparation for customizing TCP/IP, IBM recommends you complete the input worksheet.
Getting Started
TCP/IP customization panels are divided into five categories:
Basic Settings - where you configure:
Location where configuration data sets will reside
Domain origin and host name
Data set prefix
Domain name servers
Port reservations
Network Connections - where you configure:
IP routing method
All device and link information
Telnet 3270 server - where you configure the Telnet 3270 server.
FTP servers - where you configure one or more FTP servers.
FTP clients - where you configure one or more FTP clients.
Navigate through the panels for each of these main categories to enter your configuration data. Once you have completed your customization tasks, select Save from the main TCP/IP customization panel to save the data onto the workstation. You can also select the CANCEL button, which will discard any data you have entered.
To begin, select a category and click the Customize button (or double click on the category). Panels will be displayed specific to that category. Throughout the customization phase, use the OK, Close or Finish buttons to indicate that you have completed configuration data for a panel or set of panels, or use the CANCEL button to discard data.
Push buttons
Click Customize or double click one of the tasks to enter the customization panels.
Click Report to show the current TCP/IP configuration files for TCPIP.DATA, PROFILE.TCPIP, and OMPROUTE. This
includes the TN3270 configuration.
Scope of the TCP/IP configuration
Information is collected allowing for the creation of a simple TCP/IP configurations with simple instances of OMPROUTE, and all device types including static VIPA. To define more complex configurations see "z/OS IBM Communications Server: IP Configuration Guide". Information collected for TN3270 server, FTP servers, and FTP clients is extensive and provides all the options most customers would need.
The panels ask for information that is converted into TCP/IP configuration files, configuration statements and parameters. However, if you are familiar with TCP/IP configuration, you will notice that the configuration demo does not ask for a value for a specific TCP/IP parameter that you are expecting it to. A single query of a data field on a panel may result in multiple TCP/IP configuration statements. For example, you may add a Channel-to-Channel (CTC) device. On the customization panel, information such as the Device name, Device number, Link name, and IP address of the link will be collected. This information will be used to create the DEVICE, LINK, HOME, and the static or dynamic route configuration statements. Whenever possible, existing defaults for configuration parameters are used. The information collected allows for the creation of the following files and configuration statements:
tcp.data
DATASETPREFIX
DOMAINORIGIN
HOSTNAME
NSINTERADDR (may define multiple name servers)
TCPIPJOBNAME
defaults are used for all other configuration statements
profile.tcp
ATMARPSV
ATMLIS (taking the defaults for the ATMLIS options)
ATMPVC
AUTOLOG/ENDAUTOLOG
BEGINROUTES/ENDROUTES ROUTE (for static routes, taking the defaults for all options)
DEVICE and LINK statements - all device types are supported, and defaults are taken whenever available
HOME
PORT
PORTRANGE
START (for all configured devices)
TCPCONFIG RESTRICTLOWPORTS
TRANSLATE
UDPCONFIG RESTRICTLOWPORTS
defaults are used for all other configuration statements
OMPROUTE
OSPF_INTERFACE (when OSPF routing is selected, all defaults are taken)
RIP_INTERFACE (when RIP routing is selected, all defaults are taken)
INTERFACE (when RIP routing is selected, and the device type is static VIPA)
defaults are used for all other configuration statements
TN3270
ALLOWAPPL
BEGINVTAM/ENDVTAM
CLIENTAUTH
CONNTYPE
DEFAULTAPPL
DEFAULTLUS
DEFAULTLUSSPEC
DEFAULTPRT
DEFAULTPRTSPEC
DESTIPGROUP
DROPASSOCPRINTER
ENCRYPTION
EXPRESSLOGON
HNGROUP
INACTIVE
IPGROUP
KEYRING
LINEMODEAPPL
LINKGROUP
LUGROUP
LUMAP
LUSESSIONPEND
MSG07
PORT / SECUREPORT
PRTDEFAULTAPPL
PRTGROUP
PRTMAP
SCANINTERVAL / TIMEMARK
SMFINIT / SMFTERM
SNAEXT
TELNETDEVICE
TELNETGLOBALS/ENDTELNETGLOBALS
TELNETPARMS/ENDTELNETPARMS
TKOSPECLU
USERGROUP
USSTCP
defaults are used for all other TN3270 configuration statements
FTP Servers
ACCESSERRORMSGS
ADMINEMAILADDRESS
ASATRAMS
AUTOMOUNT
AUTORECALL
AUTOTAPEMOUNT
BANNER
BLKSIZE
CCXLATE
CHKPTINT
CIPHERSUITE
CONDDISP
CTRLCONN
DATACLASS
DATATIMEOUT
DB2
DB2PLAN
DCBDSN
DCONNTIME
DEBUGONSITE
DIRECTORY
DIRECTORYMODE
DUMPONSITE
EMAILADDRCHECK
ENCODING
EXTENSIONS
FILETYPE (only SEQ)
FTPKEEPALIVE
FTPLOGGING
HFSINFO
INACTIVE
ISPFSTATS
JESENTRYLIMIT
JESINTERFACELEVEL
JESRECL
JESPUTGETTO
JESRECFM
KEYRING
LISTSUBDIR
LOGINMSG
LRECL
MBDATACONN
MGMTCLASS
MIGRATEVOL
MVSINFO
MVSURLKEY
PASSIVEDATAPORTS
PORTCOMMAND
PORTCOMMANDIPADR
PORTCOMMANDPORT
PDSTYPE
PRIMARY
RDW
RECFM
REPLYSECURITYLEVEL
RETPD
SBDATACONN
SBSUB
SBSUBCHAR
SECONDARY
SECURE_CTRLCONN
SECURE_DATACONN
SECURE_FTP
SECURE_LOGIN
SMF
SMFAPPE
SMFDEL
SMFEXIT
SMFJES
SMFLOGN
SMFREN
SMFRETR
SMFSQL
SMFSTOR
SPACETYPE
SPREAD
SQLCOL
STARTDIRECTORY
STORCLASS
TLSTIMEOUT
TRAILINGBLANKS
TRUNCATE
UCOUNT
UMASK
UNITNAME
VCOUNT
VOLUME
WRAPRECORD
WRTAPEFASTIO
defaults are used for other FTP server configuration statements
FTP Clients
ASATRANS
AUTOMOUNT
AUTORECALL
AUTOTAPEMOUNT
BLKSIZE
CCONNTIME
CCTRANS
CHKPTPREFIX
CHKPTINT
CIPHERSUITE
CLIENTERRCODES
CONDDISP
CTRLCONN
DATACLASS
DATACTTIME
DATATIMEOUT
DB2
DB2PLAN
DCBDSN
DCONNTIME
DIRECTORY
DIRECTORYMODE
ENCODING
EPSV5
EXTENSIONS UTF8
FILTETYPE
FTPKEEPALIVE
FWFRIENDLY
INACTTIME
ISPFSTATS
KEYRING
LISTSUBDIR
LOGCLIENTERR
LRECL
MBDATACONN
MGMTCLASS
MIGRATEVOL
MYOPENTIME
NETRCLEVEL
PDSTYPE
PRIMARY
RDW
RECFM
RESTGET
RETPD
SBDATACONN
SBSUB
SBSUBCHAR
SECONDARY
SECURE_CRTLCONN
SECURE_DATACONN
SECURE_FTP
SECURE_MECHANISM
SOCKSCONFIGFILE
SOCKS configuration file customization support
DIRECT
SOCKSD
SOCKSD4
SPACETYPE
SPREAD
SQLCOL
STORCLASS
TLSTIMEOUT
TRAILINGBLANKS
TRUNCATE
UCOUNT
UMASK
UNITNAME
VCOUNT
VOLUME
WRAPRECORD
WRTAPEFASTIO
defaults are used for other FTP client configuration statements
For TCP/IP to function correctly, corresponding VTAM definitions may be required, which are beyond the scope of the IBM TCP/IP Configuration Demo for z/OS configuration.
The output
The configuration demo marks each TCP/IP configuration as either 'Not customized', 'Customized', or 'Incomplete'. Initially a configuration will be 'Not customized' until you select the Save button on the main TCP/IP customization panel. At that time, your data is analyzed for completeness. If it is complete, the data is saved on your workstation. If it incomplete, specific messages will describe why it is incomplete and how to complete it. You may save incomplete configurations, which will be marked as 'Incomplete'.
To view the configuration files, select the Report button on the main TCP/IP customization panel. All of the configured profiles will be displayed and you can save them to your workstation by selecting the Save button. The FTP configuration files for server and client can be seen by selecting the FTP task and selecting the Customize button. Then from the main FTP table, select the Report button to view the configuration files. The configuration file member names will be TCPDATA, PROFILE, PORTS, TN3270 and OMPROUTE, which represent the TCP/IP configuration files typically known as TCP.DATA, PROFILE.TCP and OMPROUTE. The PORTS and TN3270 files are INCLUDEd from the PROFILE file. Additionally, for each FTP server you define a new configuration file and start procedure will be created as members. You choose the member names when defining the FTP servers. Likewise, for each FTP client you define a new configuration file will be created as member in the data set.
Installation
Once the configuration files are saved, please read the installation instructions for various options on how to proceed.
Use address translation to indicate the relationship between an IP address and the physical address on a specified link. You can use translations for ATM, HYPERchannel, Ethernet, FDDI, and token ring hosts for which ARP is not supported. Address translation is not valid for virtual devices, or point-to-point devices such as CTC.
You can find more detailed help on the following elements of this window:
Use to specify the IP address of the translation; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the network address corresponding to IP address and link name. The format depends on the network type.
Rules:
For ATM NSAP, specify a 40-digit hexadecimal value.
For HYPERchannel, specify a 12-digit hexadecimal number of the form ttxxxxxxhhcc.
tt: The trunk mask. Use values other than FF only when advised to do so by Network Systems Corporation or by a HYPERchannel expert.
xxxxxx: These 6 digits are ignored.
hh: The remote adapter address.
cc: The meaning depends on the type of remote adapter. If the remote adapter is attached to a VM TCP/IP or z/OS TCP/IP system, then cc is the read port address (the lower of the two addresses that are attached to TCP/IP).
For ETHERNET, IBMTR, and FDDI, specify a 12-digit hexadecimal MAC address of the remote adapter.
For Ethernet, the remote host is assumed to use network headers DIX Ethernet format, not the 802.3 format.
For token ring, the translate entry should not contain a token ring source routed bridge path.
Use to specify a virtual device. The Virtual IP Address (VIPA) removes the adapter as a single point of failure by providing an IP address that is associated with a stack without associating it with a specific physical network attachment. Because the virtual device exists only in software, it is always active and never experiences a physical failure.
A VIPA has no single physical network attachment associated with it. It is very useful to define VIPAs so that if a physical adapter loses its connection to the network, application traffic using the failed physical adapter can be rerouted over another interface to the network. To the network, the VIPA address appears to be one hop away from the TCP/IP address space's physical interfaces.
The network sends and receives datagrams to and from the physical interfaces to get to the VIPA address. To the routing network, a VIPA appears to be a host address indirectly attached to the z/OS. When a packet with a VIPA destination reaches the stack, the IP layer recognizes the address and passes it to the protocol layer in the stack.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Only one virtual link can be defined for a virtual device.
More than one virtual device can be defined for multiple virtual IP addresses on one TCP/IP image in one z/OS system.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
Use to specify the name and address of an X.25 NCP Packet Switching Interface (NPSI) program device that you use. NPSI is a way to route SNA-type traffic over X.25 networks.
You can find more detailed help on the following elements of this window:
Use to specify the name by which this TCP/IP identifies this device; for example, DEVICE1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the name of the X.25 NPSI server started procedure; TCPIPX25, for example.
Rules:
The maximum length is 8 characters.
The first character must be one of $@# or an alphabetic letter.
Each subsequent character must be one of -$@# or an alphanumeric.
Use to specify the name by which this TCP/IP identifies this link; for example, LINK1.
Rules:
The maximum length is 16 characters.
Each character must be a non-blank printable character; ,;.= (comma, semicolon, period, or equal sign) are not allowed.
The first character must be one of $@# or an alphanumeric; if it is numeric, the name must not be a hexadecimal number.
Use to specify the IP address of this link, also known as the link's home address; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use to specify the subnet mask (in dotted decimal notation) of the subnet this interface attaches to; 255.255.192.0, for example.
Rules:
The 32-bit subnet mask must be one or more one-bits followed by one or more zero-bits. The subnet mask cannot have any one-bits to the right of any zero-bits. Therefore, a mask of 255.255.192.0 is valid because 255 is 11111111 and 192 is 11000000, but a mask of 255.255.208.0 is not valid because 208 is 11010000.
Entering the subnet mask is optional. If left blank, a subnet mask is generated based on the class of the IP address.
Class A IP addresses begin with a decimal number less than 128. Consequently, a subnet mask of 255.0.0.0 is generated.
Class B IP addresses begin with a decimal number greater than 127 and less than 192. Consequently, a subnet mask of 255.255.0.0 is generated.
Class C IP addresses begin with a decimal number greater than 192. Consequently, a subnet mask of 255.255.255.0 is generated.
You are defining a point-to-point link and need to specify the IP address of the interface at the other end of the link; 10.1.180.254, for example.
Rules:
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Use this panel to configure advanced options.
You can find more detailed help on the following elements of this window:
Do not automatically restart server
Push buttons
Click OK to complete the specification.
Click Cancel to negate any entries you have made on this page.
Click Help to understand more about this panel.
If selected, indicates that the application should not be automatically restarted if it is stopped. The default is to restart the application if it is stopped.
This option is used when two dissimilar applications need to use the same port. You indicate that one application will use the port for data received on a specific IP address. Another application can use the same port, but for data received on a different IP address.
The most common usage of this is with the TN3270 server and the TELNET server. Both are defined by the IETF to use well known port 23. To allow for both to properly function using port 23, you would need to enable the "Bind an IP address" option for one of the two servers.
This option is not valid for port ranges.
This option is available for UDP applications. However, a UDP port cannot be reserved for two different job names. Therefore, the usefulness of this function for UDP applications is limited.
The IP address must be specified in dotted decimal notation, in which a 32-bit IP address is represented as four decimal numbers, one for each 8 bits, separated by dots (periods). Each of the four decimal numbers is greater than or equal to 0 and less than or equal to 255. For example:
00001010 00000001 10110100 11111110 a 32-bit address
10
1
180
254
dotted decimal notation (10.1.180.254)
Select this option to control access to the ports with a security product such as RACF. You must enter a resource name to be used for authorization.
Typically, reserving a port for a specific job name is sufficient. Using the SAF option additionally indicates that the port is reserved for users that are permitted to the RACF resource specified as:
EZB.PORTACCESS.sysname.tcpname.resname
where EZB.PORTACCESS is constant, sysname is the value of the MVS &SYSNAME. system symbolic, tcpname is the name of the procedure used to start the TCP stack, and resname is the resource name you enter in this field.
The resource name must:
be one to eight characters
begin with a letter (A-Z) or national character ($, @, or #)
contain only letters (A-Z), numbers (0-9), national characters ($, @, #), or the hyphen (-)
Share port is used for similar applications to share the same port. When enabled, TCP/IP distributes incoming client connections across the applications. TCP/IP selects the listener with the least number of connections at the time the incoming connection request is received.
If the same port is reserved for multiple job names, share port needs to be specified for only one of the applications. This function is available only for TCP applications when reserving single ports.
Select this option to allow TCP/IP to immediately send acknowledgement of packets received on this TCP port.
This option is only available for TCP applications.
Use this panel to reserve ports for TCP and UDP applications. All currently defined port reservations are shown. Initially, default port reservations are defined for you.
Before you begin, understand the ports your IP applications will need reserved.
Steps
Click Add to reserve a port, where you will enter the port number, job name and protocol.
Click Edit to modify a port that is already reserved. (If you haven't selected a port in the list, the Edit button is disabled.)
Click Remove to unreserve a port. (If you haven't selected a port in the list, the Remove button is disabled.)
You have completed this panel after you have added, edited or removed all your required port reservations.
You can find more detailed help on the following elements of this window:
You can find more detailed information about port reservations:
Push buttons
Click Add... to reserve a new port or port range.
Click Edit... to modify the selected port reservation.
Click Remove to delete the selected port reservation.
IP applications use specific IP ports for sending and receiving data and listening for incoming connect requests. If multiple applications attempt to use the same port, this results in unpredictable behavior and possibly security violations. For applications to perform as expected, you should reserve the ports on behalf of the applications. The port number, the protocol (TCP or UDP), and the job name are required. Once the port is reserved for a specific job name, IP knows to route the inbound data to the application identified by the job name.
Ports reserved for UDP applications are separate and distinct from ports reserved for TCP applications. Therefore, it is legitimate to reserve the same port for a TCP application and a UDP application.
You cannot reserve a UDP port for more than one job name. In general, you should not reserve the same TCP port number for two different job names. This may result in undesirable behavior. There are two exceptions:
Similar applications may use the same port for load balancing. In this case the Advanced option, "Share ports across multiple listeners" must be enabled.
Dissimilar applications may use the same port, but listen on unique incoming IP addresses. In this case the Advanced option, "Bind an IP address" must be enabled. The most common use for this option is with the TN3270 server and the TELNET server. Both are defined by the IETF to use the well known port 23. To allow for this, you would reserve port 23 for both job names, and enable the "Bind an IP address" function for the TELNET server.
You are allowed to reserve the same TCP port for different job names without enabling the "Bind an IP address" or "Share ports across multiple listeners" functions. This is because applications may have the intelligence to handle this at run time. However, reserving the same TCP port for multiple applications is not common and should be done with caution.
When enabled, ports 1 through 1023 are reserved for authorized applications. This can be enabled for UPD and/or TCP applications. When enabled, applications using ports 1 to 1023 must be authorized in one of the following ways:
The port must be explicitly reserved for the job name of the application.
The application must be APF authorized.
The application must be an OMVS superuser (UID(0)).
Use this panel to define basic attributes of a port or port range reservation.
Before you begin, know the port number(s), the application protocol and job name.
Steps
Indicate whether you are reserving a single port or a range of ports and enter the appropriate port number(s).
Select the protocol, either TCP or UDP.
Enter the application's job name or you can indicate the port should be blocked and not available for any application.
Optionally, enter a brief comment.
If you wish to set additional advanced options, use the Advanced Settings... button.
Click OK when you are done.
You have completed this panel after you have entered port number(s), protocol, and job name and clicked on OK.
Fields
Radio Buttons
Click Single to reserve a single port number.
Click Range to reserve multiple consecutive port numbers.
Click TCP to indicate the application uses the TCP protocol.
Click UDP to indicate the application uses the UDP protocol.
Click Job name to reserve the port for the application indicated by its job name.
Click Blocked to block all applications from using the port(s).
Push buttons
Click Advanced Settings to configure additional advanced settings.
Click OK to complete the specification.
Click Cancel to negate any entries you have made on this page.
Click Help to understand more about this panel.
The port number must be an integer from 1 to 65535.
Specify the lowest number in the port range. It must be an integer from 1 to 65535 and must not exceed the Upper value.
Specify the highest number in the port range. It must be an integer from 1 to 65535 and be greater than or equal to the Lower value.
An application is started using a JCL job. This job name represents the started application. To reserve a port for a particular application enter the job name of the application.
The job name must:
be one to eight characters.
begin with a letter (A-Z) or national character ($,@, or #).
contain only letters (A-Z), numbers (0-9), national characters ($,@,#), or the hyphen (-).
There are several special job names:
OMVS indicates the port is reserved for any OE application except those using the Pascal API.
* indicates the port is reserved for any application.
INTCLIEN indicates the port is reserved for the TN3270 server. TCP/IP currently provides two TCP/IP services. If you are using the service that provides TN3270 server configuration then you are not allowed to enter this job name. TN3270 ports are reserved automatically when you configure your TN3270 server.
You can also indicate you want the port blocked from any application use. You indicate this by selecting "Blocked".
The optional comment must contain only letters (A-Z), numbers (0-9), blanks
or any of the following:
> + & ! $ - / | _ < ? ` : # @ ' " ~ { } [ ] \ * ( ) % , . = ;
This is a snapshot of your configuration file typically referred to as "PROFILE.TCPIP".
Push buttons
Click Save to save this configuration file to local disk.
Click Print to print this configuration file.
Click Close to end this panel.
This is a snapshot of your configuration file typically referred to as "OMPROUTE".
Push buttons
Click Save to save this configuration file to local disk.
Click Print to print this configuration file.
Click Close to end this panel.
This is a snapshot of your configuration file typically referred to as "TCPIP.DATA".
Push buttons
Click Save to save this configuration file to local disk.
Click Print to print this configuration file.
Click Close to end this panel.
This is a snapshot of your configuration file containing your port reservation. This file is pointed to by an INCLUDE statement in file PROFILE.TCPIP.
Push buttons
Click Save to save this configuration file to local disk.
Click Print to print this configuration file.
Click Close to end this panel.
This is a snapshot of your configuration file containing your TN3270 server definitions. If you configured the TN3270 server to start automatically with the TCP/IP stack, then this file is pointed to by an INCLUDE statement in file PROFILE.TCPIP. Otherwise, the TN3270 server is configured to start in its own address space and this file is pointed to by the PROFILE DD statement in the TN3270 start procedure.
Push buttons
Click Save to save this configuration file to local disk.
Click Print to print this configuration file.
Click Close to end this panel.
Use this panel to see a display of the Telnet 3270 start procedure. This start procedure can be used to start the Telnet 3270 Server in its own address space.
Push buttons
Click Save to save this file to local disk.
Click Print to print this file.
Click Close to end this panel.