TCPIP.DATA statements

Each configuration statement can be preceded by an optional system_name. This permits configuration information for multiple systems to be specified in a single hlq.TCPIP.DATA data set. The system_name is matched against the name of the system on which you are running. The name of the system is specified as part of the VMCF subsystem initialization, as the nodename value on the following parameter and statement:

P= start parameter of the EZAZSSI started procedure
VMCF statement of the IEFSSNxx member of parmlib

For more information about starting VMCF, see Step 3: Configure VMCF and TNF.

The statements are processed in the order they appear in the data set. The following rules apply to this processing:

If the system_name does not match the name of the system, the configuration statement is ignored.
If system_name is blank, the configuration statement is in effect on every system.
If the system_name matches the host's name, the configuration statement that follows it is in effect.
The last statement that matches is effective.

For example, if you have the following three TCPIPJOBNAME statements, MVS6 would look for a TCP/IP cataloged procedure named TCPBTA2, MVSA would look for TCPV3, and all other systems would look for TCPMCWN.

      TCPIPJOBNAME TCPMCWN
MVS6: TCPIPJOBNAME TCPBTA2
MVSA: TCPIPJOBNAME TCPV3

But if you reversed the order, all systems would try to find the procedure named TCPMCWN.

MVS6: TCPIPJOBNAME TCPBTA2
MVSA: TCPIPJOBNAME TCPV3
      TCPIPJOBNAME TCPMCWN

Take special care with those TCPIP.DATA statements that can be specified multiple times, such as the SEARCH, SORTLIST, NSINTERADDR/NAMESERVER, OPTIONS, and LOADDBCSTABLES statements. Because these statements are cumulative, if you specify a system_name value, it might need to be used on all instances of the same statement. Consider the following examples.

Example 1:

                  NSINTERADDR 5.5.5.5  
                  NSINTERADDR 1.1.1.1 
            TN03: NSINTERADDR 1.1.1.1
            TN03: NSINTERADDR 2.2.2.2   
            TN04: NSINTERADDR 3.3.3.3   
            TN04: NSINTERADDR 4.4.4.4

After these TCPIP.DATA statements are processed, the following ordered list of DNS addresses is available:

On TN03:
     5.5.5.5
     1.1.1.1
     1.1.1.1
     2.2.2.2
On TN04:
     5.5.5.5
     1.1.1.1
     3.3.3.3
     4.4.4.4
All others:
     5.5.5.5
     1.1.1.1

Example 2:

            TN03: NSINTERADDR 1.1.1.1
            TN03: NSINTERADDR 2.2.2.2   
            TN04: NSINTERADDR 3.3.3.3   
            TN04: NSINTERADDR 4.4.4.4 
                  NSINTERADDR 5.5.5.5  
                  NSINTERADDR 1.1.1.1

After these TCPIP.DATA statements are processed, the following ordered list of DNS addresses is available:

On TN03:
     1.1.1.1
     2.2.2.2
     5.5.5.5
     1.1.1.1
On TN04:
     3.3.3.3
     4.4.4.4
     5.5.5.5
     1.1.1.1
All others:
     5.5.5.5
     1.1.1.1

A sample TCPIP.DATA data set (TCPDATA) can be found in SEZAINST. For detailed information on each of the statements, see z/OS Communications Server: IP Configuration Reference.