IP Services: Update /etc configuration files
Description
Some utilities provided by Communications Server require the use of certain configuration files. You are responsible for providing these files if you expect to use the utilities. IBM® provides default configuration files as samples in the /usr/lpp/tcpip/samples directory. Before the first use of any of these utilities, you should copy these IBM-provided samples to the /etc directory (in most cases). You can further customize these files to include installation-dependent information. An example is setting up the /etc/osnmpd.data file by copying the sample file from /usr/lpp/tcpip/samples/osnmpd.data to /etc/osnmpd.data and then customizing it for the installation.
If you customized any of the configuration files that have changed, then you must incorporate the customization into the new versions of the configuration files.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
Element or feature: | Communications Server. |
---|---|
When change was introduced: | Various releases. See Table 2. |
Applies to migration from: | z/OS V2R1 and z/OS V1R13. |
Timing: | Before the first IPL of z/OS V2R2. |
Is the migration action required? | Yes, if you have customized a configuration file (listed in Table 2) that IBM has changed. |
Target system hardware requirements: | None. |
Target system software requirements: | None. |
Other system (coexistence or fallback) requirements: | None. |
Restrictions: | None. |
System impacts: | None. |
Related IBM Health Checker for z/OS® check: | None. |
Steps to take
If you added installation-dependent customization to any of the IBM-provided configuration files listed in Table 2, make the same changes in the new versions of the files by copying the IBM-provided samples to the files shown in the table and then customizing the files.
Utility | IBM-provided sample file | Target location | What changed and when |
---|---|---|---|
Communications Server z/OS UNIX applications | SEZAINST(SERVICES) | /etc/services | In z/OS V2R2, the NCPROUT entry is removed because NCPROUTE is no longer supported. If you update /etc/services, ensure that you also update the ETC.SERVICES data set. |
DCAS | No sample provided | /etc/dcas.conf | In z/OS V2R2, a new TLSV1ONLY keyword is provided to configure SSLv3 protocol for connections secured using the DCAS SSL support. |
File Transfer Protocol Daemon (FTPD) | SEZAINST(FTPSDATA) | /etc/ftp.data | In z/OS V2R1, a configuration statement was provided to specify that a type 119 SMF record of subtype 71 is collected for the FTP daemon configuration information when the FTP daemon starts. |
FTP Server and Client | SEZAINST(FTCDATA) for the client and (FTPSDATA) for the server | /etc/ftp.data | In z/OS V2R2, a new SSLV3 keyword is provided to configure SSLv3 protocol for connections secured using the FTP TLS support. |
Internet Key Exchange Daemon(IKED) | /usr/lpp/tcpip/samples/iked.conf | /etc/security/iked.conf | In z/OS V2R2, a new log level is added for the IKE daemon. |
Policy agent | /usr/lpp/tcpip/samples/pagent.conf | /etc/pagent.conf | In z/OS V2R2, a new ServerSSLv3 keyword is provided to configure SSLv3 protocol for the policy client connecting to the server. |
Sendmail | /usr/lpp/tcpip/samples/sendmail/cf/zOS.cf | /etc/mail/zOS.cf | In z/OS V2R2, a new SSLV3 keyword is provided to configure SSLv3 protocol for connections secured using System SSL. |
SNMP agent | /usr/lpp/tcpip/samples/osnmpd.data | /etc/osnmpd.data | Every release, the value of the sysName MIB object is updated to the current release. |
SNMP agent | /usr/lpp/tcpip/samples/snmpd.conf | /etc/snmpd.conf | In z/OS V2R2, a new privacy protocol value AESCFB128 can be specified on a USM_USER statement to request AES 128-bit encryption. |
z/OS UNIX snmp command | /usr/lpp/tcpip/samples/snmpv2.conf | /etc/osnmp.conf | In z/OS V2R2, a new privacy protocol value AESCFB128 can be specified on a statement for an SNMPv3 user to request AES 128-bit encryption. |
Reference information
For more information about Communications Server configuration files, see z/OS Communications Server: IP Configuration Guide.