TCP/IP Function Level 310 Preventive Service Planning
(PSP) Bucket
**> Last update: 14 Dec 2001 **> Synch'd w/RETAIN: 31 Mar 2002 *********************** * SUBSET VM310 * *********************** This SUBSET contains installation information for TCP/IP Function Level 310 for VM/ESA Version 2 Release 3.0. ************************************************************************ * C H A N G E S U M M A R Y * ************************************************************************ Date Last Changed Section 1. 2001/01/25 Installation Information 2. 1998/09/13 Documentation Changes 3. 1998/04/01 General Information 4. 2001/12/14 Service Recommendations See Subset 0101RSU 5. yyyy/mm/dd Cross Product Dependencies Service Recommendation Summary DATE APAR PTF VOLID COMMENTS 1. 1998/03/31 PQ14175 UQ16101 1000 HIPER SMTP Names List Processing ************************************************************************ * SECTION 1. I N S T A L L A T I O N I N F O R M A T I O N * ************************************************************************ This section contains changes relevant to the installation of the product, or to its Program Directory. 8. 2001/01/25 Prior to performing installation and service tasks, ensure that the PROFILE EXEC invoked by the TCP/IP installation user ID (P735FALQ) contains (at a minimum) the 'ACCESS' and 'SET LDRTBLS' statements that follow: /* TCP/IP Installation User ID PROFILE EXEC */ 'ACCESS 5E5 B' /* Acquire SES 5E5 disk */ 'ACCESS 51D D' /* Acquire SES 515 disk */ 'SET LDRTBLS 25' /* Avoid LDRTBL problems */ Exit These statements (in conjunction with the supplied CP directory entry for the P735FALQ installation user ID) will establish the minimal environment necessary to install and service the TCP/IP Feature as described in the TCP/IP FL310 Program Directory. 7. 1999/10/28 For customers who plan to use the VM NFS sever, note the following: In order for NFS clients to access files or directories in the CMS Shared File System (SFS), the NFS server must have SFS file pool administrator authority. Each NFS server that will provide such access must be listed on the ADMIN statement in the SFS file pool server's DMSPARMS file. For details on SFS file pool configuration and administrator authority, see "VM/ESA SFS and CRR Planning, Administration, and Operation" 6. 1999/05/11 The supplied sample TCP/IP configuration file (PROFILE STCPIP) contains a PRIMARYINTERFACE in comment form: ; ------------------------------- ; Primary interface Definition ; ------------------------------- ; PRIMARYINTERFACE ETH1 Note that the placement of this statement within this sample file is not correct; this statement must appear after the HOME statement if/when it is used. 5. 1998/06/18 Customers who plan to use an External Security Manager (ESM) different from the IBM Resource Access Control Facility (RACF), such as VMSECURE from Sterling Software Inc., should review Informational APAR II11256 for additional information about configuring TCP/IP servers in such an environment. 4. 1998/05/06 For customers who plan to use the X.25 Interface and need to configure/use the X25IPI server, note the following: Due to changes made for Function Level 310 that affect startup of the X25IPI server, X25IPI commands cannot be successfully issued from the X25IPI server console. To correct this problem, the following changes are required: Make the following changes to the supplied X25IPI GCS file: 1) Change the load command from "X25IPI" to "X25": 'LOADCMD X25 XNX25CMD' 2) Change the start command to use this new command name: 'X25 START XNX25IPI' Then, use "X25" (instead of "X25IPI") as the command name for all commands issued from the X25IPI server console, as is currently described in the product documentation. If necessary, see APAR PQ14349 for additional information about this problem. 3. 1998/04/29 For customers installing the TC/IP DES Feature for VM/ESA, note the following changes to Section 6.5 of the Program Directory: * In Section 6.5.1, Step 4, the TCP/IP DES Feature tape should be mounted and used (the reference to the TCP/IP Source Feature tape is not correct). * In Section 6.5.3.2, Step 2, the 5735FALQ PPF name and TCPIP (or TCPIPSFS) component ID are used for two VMFBLD commands; because of this, the VMSES PARTCAT is updated such that the affected modules are associated with this PPF name and component, rather than with the DES Feature PPF name (5735FALR) and component (KERBDES or KERBDESSFS). If left unchanged, these PARTCAT entries will cause the TCP2PROD command (as documented in Step 7 of Section 6.5.4.1) to fail, with the following error reported: ... Issuing command: ACCESS 591 C Copying file(s) to: TCPMAINT 591 KERBEROS MODULE J --> = = C The following command failed: VMFCOPY KERBEROS MODULE J = = N (SPRODID 5735FALR%KERBDES PRODID 5735FALR%KERBDES OLDDATE REPLACE Rc = 4 TCP2PROD processing completed: {Date} -- {Time} Rc = 8 ... To avoid this problem, and to resolve the PARTCAT entry conflict, the following steps should be performed: 1) Prior to invoking TCP2PROD during DES Feature installation (Step 7 of Section 6.5.4.1 of the Program Directory), the following VMFSIM command should be issued (note that the lines below comprise a single command): vmfsim modify vmses partcat {fm-492} tdata :partid des txtlib :prodid 5735falq%tcpip (replace where: {fm-492} is the file mode of the P735FALQ 492 minidisk. 2) The TCP2PROD command issued during Step 7 of Section 6.5.4.1 should be (again, the lines below comprise a single command): tcp2prod 5735falq {tcpip|tcpipsfs} 5735falr kerbrun (setup Note: These same steps are applicable to Step 8 of Section 7.4.3.1 (DES Feature Service) of the Program Directory. * Also in Section 6.5.3.2, the command shown in Step 3 should be "vmfview build", not "vmfview install". 2. 1994/01/19 Item Updated 1998/04/01 Missing interrupt conditions for I/O operations involving devices dedicated to the TCPIP virtual machine should be detected, but *not* dealt with. For VM/ESA, the default MIH setting of OFF will accomplish this. (This default is in effect when MIH is not specified on the user directory OPTION statement or the SET MIH command is not issued within a virtual machine). However, when MIH OFF is in effect, CP issues HCPMHT2150I messages to the operator, to indicate that an I/O operation was started but the MIH interval expired before the device sent an interrupt. In some instances, these messages may flood the OPERATOR console. Use of the 'OFF' parameter of a related command, CP SET MITIME, can prevent excessive HCPMHT2150I messages related to TCPIP from appearing on the OPERATOR console. This command controls the time interval at which a specified device is checked for missing interrupts. To reduce occurrences of HCPMHT2150I messages, use the following command. Note that only the device(s) dedicated to the TCPIP server should be specified with this command. CP SET MITIME rdev1-rdev2 OFF The CP SET MITIME command should be issued within an "exit" exec, identified by an ":Exit." tag that is defined for the TCPIP server entry in a locally created DTCPARMS file. 1. 1992/01/10 Item Updated 1998/04/01 Prior to installing TCP/IP for VM, it's recommended that you review the following information, if you're not familiar with TCP/IP protocols and functions: * "TCP/IP Tutorial and Technical Overview", (GG24-3376-04). This book provides an overview of TCP/IP, and may help prevent many installation and configuration errors. Additional textbook references that may be useful are: * "TCP/IP Illustrated, Volume 1: The Protocols," Richard W. Stevens, Addison-Wesley, Reading, Massachusetts, 1994. ISBN: 0-201-63346-9 (SR28-5586-00) * "Internetworking with TCP/IP Volume I:Principles, Protocols, and Architecture," Douglas E. Comer, Prentice Hall, Englewood Cliffs, New Jersey, 1991. ISBN: 0-13-216987-8 (SC31-6144-00) * "DNS and BIND in a Nutshell," Paul Albitz & Cricket Liu, O'Reilly & Associates, Sebastopol, California, 1992. ISBN: 1-56592-010-4 (SR28-4970-00) ************************************************************************ * SECTION 2. D O C U M E N T A T I O N C H A N G E S * ************************************************************************ This section outlines major errors in the product's published documentation. 2. 1998/09/13 The following errors exist in "TCP/IP Function Level 310 Planning and Customization" (SC24-5847-00): Chapter 1, "Planning Considerations" Page Error / Correction ---- --------------------------------------------------- 2/3 The descriptions for the FTP, LPD and REXEC severs in the "Server Functions" section include the following sentence: You can also specify unique start-up parameters and customize the server environment by modifying the "xxxxXIT" EXEC procedure. where "xxxxXIT" is either FTPDEXIT, LPDEXIT, or REXECXIT. References to these EXECs should be ignored, as these files are no longer supplied or used with TCP/IP Function Level 310. Server customization should be accomplished using DTCPARMS file entries, as described in Chapter 5, "Methods of Server Configuration." 1. 1998/04/01 The following errors exist in the "TCP/IP Function Level 310 User's Guide" (SC24-5848-00): Chapter 10, "Using Remote Printing Commands" Page Error / Correction ---- --------------------------------------------------- 139 The LPRSET syntax diagram is not correct. The correct syntax follows: >>--LPRSET--.---------------.--------------------------> '-printer--host-' >-.------------------------.-------------------------->< '--(--.---------------.--' |--REset--------| '--| Options |--' Options: |--.-----------.--.-------.--.---------.--.-------.----> |-Permanent-| |-TRace-| '-Version-' '-Query-' '-SESsion---' '-TYpe--' >-.---------------------------------.-.--------------.-> '-NIckname--name-.--------------.-' |-SYnchronous--| '-TAg--usertag-' '-ASynchronous-' >--.-----------------------------.--.----------------.-| '-RScs--.-linkid,nodeid------| '-SERver--rscsid-' |-linkid@nodeid------| '-linkid--at--nodeid-' ************************************************************************ * SECTION 3. G E N E R A L I N F O R M A T I O N * ************************************************************************ This section contains general information, i.e., hints/tips. 8. 1998/04/01 APAR PQ12478, through its associated PTF, UQ99310, is used as the ordering mechanism for the current level of the TCP/IP Function Level 310 RSU. This APAR/PTF will be updated during every RSU cycle to indicate the level which is currently available through ISMD service. The RSU can be ordered upon request by contacting the Level 2 support group, or through the SRD (Service Request & Delivery) function of IBMLink/ServiceLink. Please see the text of APAR PQ99310 for more information, if necessary. 7. 1995/05/26 Item Updated 1996/12/20 Several TCP/IP for VM functions are Pascal-based, and use VMCF communications to communicate with the TCPIP server. Therefore, these functions cannot be reliably used in conjunction with other applications that use VMCF communications (such as the CMS Utility, WAKEUP); doing so may produce intermittent hangs during processing other unpredictable results. The TCP/IP Pascal-base functions for which such problems may arise are: FTP HOMETEST LPQ LPR LPRM NETSTAT OBEYFILE PING REXEC TELNET TESTSITE TFTP See CMS Utilities APAR VM58540 for more information about problems when using FTP in conjunction with WAKEUP. 6. 1992/11/18 Item Updated 1996/12/20 When configuring an RS/6000 IP connection with the Block Multiplexer (BMX) adapter, customers should refer to ASKQ documents Q604637 (Title -- Howto AIX: Troubleshoot Block Multiplexer Adapter Initial Configuration Problems). This item describes BMX adapter problems, configuration problems, and also provides configuration specific information. 5. 1992/01/10 During the initialization of the TCPIP server, the following error message: Line nnn: Unknown link name in GATEWAY cmd will be displayed when a LINK statement can't be found for a corresponding "link_name" value, that was specified on a previously encountered GATEWAY entry. This error may occur for one of the following reasons: - a data entry error when creating the entry, - a problem with the GATEWAY entry itself. This error message will also appear if a GATEWAY entry specifies a 0 for both the "subnet_mask" *and* "subnet_value" fields. This problem arises because processing for the current GATEWAY entry is terminated when a "subnet_mask" field of 0 is encountered; the additional 0 specified as the "subnet_value" will then be construed as the start of the next GATEWAY entry (or configuration file statement). Therefore, whenever a "subnet_mask" value of 0 is used, the associated "subnet_value" field must be left blank. 4. 1992/01/10 Invalid or incorrect values specified with the HOME and GATEWAY parameters can prevent the TCPIP server from processing further parameters associated with these statements -- even though remaining parameters may be valid. The only indication that this type of problem may exist is the following message: Error encountered in readingTCPIP * : 3. 1992/10/15 Item Updated 1996/12/20 When a nameserver is not used, and only a HOSTS LOCAL file is used for host resolution, the TCPIP DATA configuration file will not contain an NSINTERADDR statement. When this is the case, ensure the SMTP CONFIG file does not contain a RCPTRESPONSEDELAY statement. Otherwise, the following error will be reported when attempting to start SMTP: Invalid value nn specified for RCPTRESPONSEDELAY. Default used. Note that regardless of whether or not a RCPTRESPONSEDELAY statement is present, the default value of 60 seconds will be used to delay responses to RCPT commands ("nn" in this message will be value specified as part of the RCPTRESPONSEDELAY statement.) 2. 1992/01/10 Item Updated 1998/04/01 With RSCS Version 3 Release 1 (V3 R1), enhanced configuration features, such as embedded files, new configuration statements (such as LINKDEFINE), and the ability to use additional comment delimiters ('/*' and '*/') are available for configuring RSCS. For example: IMBED fn ft /* RSCS V3 R1 style comments */ The TCP/IP for VM program, SMTPRSCS, uses the RSCS CONFIG file to build an RSCS host table file (SMTPRSCS HOSTINFO). SMTPRSCS can process RSCS V3 R1 embedded files, its new configuration definitions, or the additional comment delimiters. However, if "generic routing" is used in your environment (as from using a "ROUTE *" statement), you still need to identify -- with respect to SMTPRSCS -- any additional RSCS host names that are relevant to your RSCS network, which are not in RSCS CONFIG configuration file. To do this, you can create a separate file to be used as input for the SMTPRSCS program. For example, a file named TCP-RSCS CONFIG, that contains: IMBED RSCS CONFIG ROUTE nodeid1 ROUTE nodeid2 : where each ROUTE statement must have two tokens -- "ROUTE" and a nodeid name of an additional RSCS node to be identified for use by the SMTP server. 1. 1992/01/10 When appropriate, the support center will open informational APARs covering various aspects of TCP/IP for VM. These APARs will cover installation and maintenance specific information, information on using the product, and other information that will often assist the customer. Customers can search for these APARs by using The product component ID (5735FAL00) and the keyword TCPIPINFO. It's recommended that customers using TCP/IP for VM review these APARs for information specific to their needs. ************************************************************************ * SECTION 4. S E R V I C E R E C O M M E N D A T I O N S * ************************************************************************ 2. 2001/12/14 See Subset 0101RSU for service recommendations 1. 1998/03/3 Problem: (PQ14175) SMTP Names List Processing can Cause SMTP To Abend Recommendation: Install UQ16101 on Volid 1000 ************************************************************************ * SECTION 5. C R O S S P R O D U C T D E P E N D E N C I E S * ************************************************************************ This section contains information that is dependent upon another product other than this subset ID. It also contains information dealing with migration and product coexistence. This item contains no records. 1. yyyy/mm/dd Interdependent Product: Problem: Users Affected: Recommendation: Install xxxxxxx on Volid xxxx ************************************************************************ * I N F O R M A T I O N A L / D O C U M E N T A T I O N * * APARs Follow (If Any) * ************************************************************************ ------------------------------------------------------------------------ PTF Include List: UQ16101 UQ48154 ------------------------------------------------------------------------ PTF Exclude List: This item contains no records. ------------------------------------------------------------------------ PE APAR List: This item contains no records. ------------------------------------------------------------------------ Pending PE APAR List: This item contains no records.