Welcome to the z/OS Communications Server IP Services customization panels for Managed System Infrastructure (msys for Setup). 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 into the LDAP server. 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). msys for Setup displays panels 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 msys for Setup converts into TCP/IP configuration files, configuration statements and parameters. However, if you are familiar with TCP/IP configuration, you will notice that msys for Setup 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
ANONYMOUS
ANONYMOUSFILEACCESS
ANONYMOUSFILETYPEJES
ANONYMOUSFILETYPESEQ
ANONYMOUSFILETYPESQL
ANONYMOUSFTPLOGGING
ANONYMOUSHFSDIRMODE
ANONYMOUSHFSFILEMODE
ANONYMOUSHFSINFO
ANONYMOUSLEVEL
ANONYMOUSLOGINMSG
ANONYMOUSMVSINFO
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 msys for Setup TCP/IP configuration.
The output
msys for Setup 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, msys for Setup analyzes your data for completeness. If it is complete, the data is saved in the LDAP server database. 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'.
Once you have saved a complete configuration, it is marked as 'Customized'. When a configuration is 'Customized' you may include it for update processing. Update is the msys for Setup phase when the customized data is retrieved from the LDAP database and TCP/IP configuration files are created. The configuration files are placed at a specific MVS DASD location you select. In the Basic Settings customization panels, specify the data set name and volume serial of the DASD. This data set must be one to which your administrator user ID has RACF write authority. Specifically, this is the user ID used on the msys for Setup 'Log on to Setup' panel.
Multiple configuration files are saved as members of the data set you specify. 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.
If you specify a data set name and volume serial of a data set that already exists, msys for Setup will determine if it was created by msys for Setup. If it appears to be created by msys for Setup, the data set will be replaced with the new configuration files. If it does not appear to have been created by msys for Setup, then the update will fail and the existing data set will be left intact.
msys for Setup provides an Undo update function. Use of this function will result in the deletion of all TCP/IP data sets created by msys for Setup.
Installation
Once the configuration files are saved, please read the installation instructions for various options on how to proceed.