Running Multiple Servers with TCP/IP V2R4

   Running Multiple V2R4 Servers

Setting up a second TCPIP (stack) server machine is not too difficult. Replicating the suite of TCP/IP servers, and having the consoles sent to a user ID different from TCPMAINT is possible, but is a more tedious task.

The changes necessary are discussed in Chapter 1 of TCP/IP for VM: Planning and Customization, Version 2 Release 4 (SC31-6082-03). The section of interest is Implications of Assigning Different Server Virtual Machine Names.

Items 1 and 2 in this section are probably of most importance to you; the remainder of the items in this section may not apply, depending on which servers you use in your environment.

TCPIP DATA File Changes

With regard to item number 1, any client that needs to communicate with the second TCPIP server (for example, TCPIP2), must access and reference a copy of the TCPIP DATA file that identifies TCPIP2 as the TCP/IP server, via the TCPIPUSERID statement. If this is not done, an attempt to start up a secondary server (such as FTPSERV2), that is to rely upon the TCPIP2 server, will fail with a "requested port not available" message.

PROFILE TCPIP File Changes

Also, you'll likely need a separate PROFILE TCPIP configuration file to be defined for the TCPIP2 server, so that PORT reservations and/or AUTOLOG monitoring will be performed for the correct set of servers.

Changing the Server "Owner" User ID

Changing the "owner" user ID that receives the consoles of a second suite of TCP/IP for VM server virtual machines is tedious, but necessary, if you want these consoles to be directed to a user ID other than TCPMAINT (perhaps the user ID, TCPMNT2). To do this, you need to create additional copies the server " exit" execs for each secondary server you plan to use (for example, FTPSERV2), and change the OWNER assignment in each exec.

The server exit files are provided as "xxxxxXIT EXEC" files.

The line you need to change in these execs is shown below. Note that this line may differ somewhat from one exec to another: 

 ...
 owner = ''         /* For example, 'TCPUSR8' */
 ...

For example, to have a server console forwarded to the TCPMNT2 user ID, the above line would be changed to: 

 ...
 owner = 'TCPMNT2'  /* For example, 'TCPUSR8' */
 ...

The list of files to modify (based on your use, of course) are:

  • TCPIPXIT EXEC
  • FTPDEXIT EXEC
  • SMTPEXIT EXEC
  • NAMESXIT EXEC
  • REXECXIT EXEC
  • PORTMXIT EXEC
  • NDBPMXIT EXEC
  • NDBSNXIT EXEC
  • SNMPDXIT EXEC
  • SNMPQXIT EXEC
  • NCSLLXIT EXEC
  • NCSGLXIT EXEC
  • ROUTEXIT EXEC
  • LPDEXIT EXEC

The following apply only to the NFS and Kerberos Features:

  • VMNFSXIT EXEC
  • KADMEXIT EXEC
  • KERBEXIT EXEC

The following apply only if Network Station support is installed (V2R4 only):

  • BOOTPXIT EXEC
  • TFTPDXIT EXEC

We recommend that each server exit EXEC is modified after it is copied to a server's 191 disk. We recommend that you also keep non-executable copies of any modified server exits on your respective server 191 disks, to prevent your modifications from being lost in the event an exit file is overlayed, due to service or an inadvertent copy operation.