The TCP/IP customization panels collect information to build a simple configuration based on values you provide. Ouput 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 TCP/IP msys for Setup 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) __________________________
Internet 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.)
Internet 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:
Internet 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) _______________________________
Internet address* ______.______.______.______
Subnet mask ______.______.______.______
Translates (You can define more than one.):
Translate's internet 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 internet 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) ________________________
Internet 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) ________________________
Internet 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) ________________________
Internet 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) ________________________
Internet address* ______.______.______.______
Subnet mask ______.______.______.______
Translations (You can define more than one.):
Translation internet 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 internet 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) __________________________
Internet address* ______.______.______.______
Subnet mask ______.______.______.______
Link number* ____
Protocol*: ETHERNET, 802.3, ETHERor802.3, IBMTR, or FDDI
Translations (You can define more than one.):
Translation internet address* ______.______.______.______
Translation physical address* (exactly 12 hex digits)
_______________________
MPCIPA
Device name* (8) ____________________
Link information (Define only one link for this device):
Link name* (16) _____________________________
Internet address* _____._____._____._____
Subnet mask _____._____._____._____
Protocol*: IPAQENET or IPAQTR
MPCOSA
Device name* (8) ____________________
Link information (Define only one link for this device):
Link name* (16) __________________________
Internet 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 internet 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) ________________________________
Internet 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) ____________________________
Internet 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) __________________
Internet 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) ____________________________
Internet address* ______.______.______.______
Subnet mask ______.______.______.______
X.25 NPSI
Device name* (16) ______________________________
Procedure name* (8) __________________
Link information (Define only one link for this device):
Link name* (16) ____________________________
Internet 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 idetifier 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? ________________