TCP/IP V2 R4 Preventive Service Planning
(PSP) Bucket
**> Last update: 17 Apr 2000 **> Synch'd w/RETAIN: 08 Jun 2000 *********************** * SUBSET VM240 * *********************** This SUBSET contains installation information for TCP/IP Version 2 Release 4 Modification 0 for VM. ************************************************************************ * C H A N G E S U M M A R Y * ************************************************************************ Date Last Changed Section 1. 1998/05/21 Installation Information 2. 1997/06/20 Documentation Changes 3. 1999/12/07 General Information 4. 2000/04/17 Service Recommendations See Subset 9801RSU / 0001RSU 5. 1996/12/20 Cross Product Dependencies Service Recommendation Summary DATE APAR PTF VOLID COMMENTS 1. yyyy/mm/dd xxnnnnn xxnnnnn nnnn N/A ************************************************************************ * 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. 14. 1998/05/21 In Section 6.2.3, "Install TCP/IP V2R4" of the Program Directory, step 8 provides instructions for installing the optional sample files (using either the TCPIPSAMP or the TCPIPSFSSAMP component). Because the majority of these samples are dependent upon C Language-based VM TCP/IP components, its recommended that these sample files be installed only if TCP/IP for VM has been installed using either the TCPIP or TCPIPSFS component. Should you want to install the optional sample files for use with either the TCPIPNOC or TCPIPSFSNOC components, a PPF override file will need to be created and used, which creates TCPIPSAMPNOC or TCPIPSFSSAMPNOC override components for the TCPIPNOC or TCPIPSFSNOC components. 13. 1998/01/05 Item Updated 1998/01/16 When RSU or corrective (COR) service is applied, please NOTE THE FOLLOWING: When the TCP2PROD command is invoked with a 'CONFIG' operand (that is, TCPCONFIG, NFSCONFIG or KERBCONFIG), existing configured files that reside on the TCPMAINT 591, 592 and 198 minidisks will be overlayed by their non-configured sample counterparts. (Files for which corresponding CATALOG entries have been 'bypassed' are not affected.) Thus, it's recommended that the TCP2PROD command be invoked with a 'CONFIG' operand ONLY when the TCP/IP base product, or one of its features is initially installed, as indicated in sections 6.2.5.1, 6.4.4.1 and 6.5.4.1 or 6.6.4.1. APAR PQ11677 (PTF UQ13189) is available to address this problem. 12. 1998/01/05 Within various sections of the Program Directory there are several occurrences of the following command sequence: link maint 5e5 5e5 rr access 5e5 d link maint 51d 51d rr access 51d d (In most instances, this sequence is used to establish the proper VMSES/E environment prior to invoking the TCP2PROD command to copy files into production -- during product installation and service). The access filemode indicated for the MAINT 5E5 minidisk (shown as filemode D above) is not correct. The MAINT 5E5 minidisk should always be accessed as filemode B. 11. 1997/06/20 Item Updated 1998/01/27 The wildcard entry in the :TCPRUN. section of the 5735FALK CATALOG that's used to copy files to the NCS 195 minidisk is not apparent in the base-level copy of this file. Also, an update intended to clarify this entry (added as part of the updates for APAR PQ01770) was incorrectly associated with entry used to process files for the TCPMAINT 491 minidisk. For reference, the first three entries in the :TCPRUN. section of this files should be: :TCPRUN. * Test Production Files New Used By * Disk Disk To Copy Filename Server: * ----- ---------- ------- -------- --------- &BLD1Z &BLD0Z * * = = All &BLD3Z &BLD2Z * * = = All &BLD7Z &DISK13 * * = = NCS (195) ... Note that with regard to their use by the TCP2PROD exec, the entries are correct; only the comments for these entries are in error. To avoid processing files for the NCS 195 minidisk, the "&BLD7Z" entry is one that should be bypassed; the "&BLD1Z" and "&BLD3Z" entries should remain. 10. 1997/05/13 Section 3.0, "Program Support," of the Program Directory (Dated 12 December 1996) has been updated to reflect changes to the release numbers associated with the TCP/IP for VM NFS, Kerberos US, and Kerberos WT Features. The relevant changes to Figures 15 and 16 of this section are: Figure 15. PSP Upgrade and Subset ID ------------------------------------ COMPID Release Upgrade Subset Component Name --------- ------- -------- ------ --------------------- ... 5735FAL00 241 TCPIP240 VM240 Kerberos US Feature 5735FAL00 242 TCPIP240 VM240 Kerberos WT Feature 5735FAL00 243 TCPIP240 VM240 NFS Feature ... Figure 16. Component IDs ------------------------ COMPID Release Component Name FESN --------- ------- -------------------- ------- ... 5735FAL00 241 Kerberos US Feature 0461035 5735FAL00 242 Kerberos WT Feature 0461035 5735FAL00 243 NFS Feature 0461035 ... 9. 1997/04/01 Item Updated 1997/06/20 If you intend to use TCP/IP for VM Version 2 Release 4 to support the IBM Network Station, the following APARs/PTFs must be applied to your system: APAR (PTF Number) Description ----------------- ---------------------------------- PQ01770 (UQ03096) Network Station Support: BOOTPD / TFTPD Function PQ02301 (UQ03142) Network Station Support: Client Code Function PQ04280 (UQ05061) Network Station Support - TCPRUN BFS Directory / README Updates However, BEFORE you apply, build and use the function provided by the above service, additional CMS service and TCP/IP resources must be in place on your system. Please see the TCP/IP for VM Corrective Service Memo, "IBM Network Station Support - New and Changed Product Requirements", for detailed information about the requirements associated with this service. 8. 1997/03/13 For customers installing the NFS Feature: The VMNFS MODULE will not initialize in an environment where the Language Environment runtime library Named Saved Segment is defined above the 16M line. The following code segment may be used to allow the VMNFS server to run in such an environment. NOTE: Any virtual machine which makes use of this circumvention should be restricted to a maximum storage size of 16M. Otherwise, the EDCZV and EDCZ24 load modules may continue to load above the 16M line, and Abend 2052 problems may persist. /* VMLECIRC EXEC */ /*------------------------------------------------------*/ /* Language Environment (LE) Saved Segment Work-around. */ /*------------------------------------------------------*/ /* The commands defined below via the stem variable */ /* "cmd." will prevent use of the LE Runtime Library */ /* saved segment, when this this has been defined above */ /* the 16M line. Since the LE LOADLIB and TXTLIB will */ /* be loaded within the virtual machine using this code */ /* segment, additional virtual storage (up to 16M) may */ /* need to be defined. */ /* --------------------------------------------------- */ /* Notes: */ /* * It's recommended that these statements be invoked */ /* from the "Postlude" section of a C-dependent */ /* server's initialization exit. One possible */ /* solution is to use this code segment in a */ /* stand-alone exec, and invoke the exec via an */ /* 'EXEC' statement (for example, 'EXEC VMLECIRC') */ /* * The minidisk(s) where the Language Environment */ /* LOADLIB and TXTLIB reside must be included in the */ /* server's CMS search order so that these files are */ /* available. */ /* * Appropriate error recovery actions should be */ /* included, in accordance with local requirements. */ /*------------------------------------------------------*/ /* Address 'COMMAND' */ Parse Source src_string Parse Upper Var src_string . . . . exc_mode inv_name . mprfx = '>'inv_name':' LE_SegBypass: /*------------------------------------------------------*/ /* Drop any existing relevant nucleus extensions. */ /*------------------------------------------------------*/ cmd.1 = 'NUCXDROP SCEE' cmd.2 = 'NUCXDROP SCEEX' /* Required GLOBALs ----------------------------------- */ cmd.3 = 'GLOBAL LOADLIB SCEERUN' cmd.4 = 'GLOBAL TXTLIB SCEELKED CMSLIB' /* Establish the required C environment --------------- */ cmd.5 = 'SEGMENT PURGE SCEE' cmd.6 = 'SEGMENT PURGE SCEEX' cmd.7 = 'FILEDEF EDC DISK SCEERUN LOADLIB * (PERM' cmd.8 = 'NUCXLOAD EDCZV EDCZV EDC (SYSTEM' cmd.9 = 'NUCXLOAD EDCZ24 EDCZ24 EDC (SYSTEM' cmd.10 = 'FILEDEF EDC CLEAR' cmd.0 = 10 /*------------------------------------------------------*/ /* Issue the required commands, and indicate errors, */ /* as appropriate. */ /*------------------------------------------------------*/ Do indx=1 to cmd.0 /* Issue the command */ cmd.indx cmd_rc = rc /* Error Recovery, as appropriate */ If (cmd_rc ^= 0) Then Do /* Nucleus extensions nonexistent */ If (cmd_rc = 28) & (indx <= 2) Then Nop Else Do Say mprfx "RC =" cmd_rc "from" cmd.indx End End End /* Do indx = 1 to cmd.0 */ Return 0 7. 1996/02/17 Item Updated 1998/02/20 For customers installing the NFS Feature: The 5735FALL CATALOG file contains an entry in the :NFSCONFIG. section which is not correct; this entry causes the (sample) VMNFSMON EXEC to be overlayed with the content of the VMNFSXIT EXEC. The entry: &BLD0Z &BLD4Z VMNFSXIT EXEC VMNFSMON EXEC VMNFS should be: &BLD0Z &BLD4Z VMNFSXIT EXEC = = VMNFS The VMNFS server will initialize with the incorrect execs in place, but it will erroneously issue the following message: Unrecognized argument ""; aborting server startup. After which, all MOUNT requests are rejected. To prevent over-writing the (sample) VMNFSMON EXEC, this entry must be corrected before you invoke the TCP2PROD EXEC to place configured NFS Feature files into production, as described in section 6.4.4.2 of the Program Directory. 6. 1996/12/20 Item Updated 1998/04/14 NOTE: If you are running VM/ESA 1.2.2, the following APARs must be applied to your system, for the VMFSIM commands described within this entry to be effective: VM60074 and VM60857 When installing TCP/IP for VM, and any of its features, the System-Level Requisite Table (VM SYSREQT) needs to be manually updated due to a missing :SUP. tag in the Base and feature PRODPART files. When you perform the "Plan Your Installation" steps described in the Program Directory -- Steps 6.2.3, 6.4.3, and 6.5.3 or 6.6.3 -- issue the following commands (as indicated) *after* the command: VMFINS INSTALL PPF(NOMEMO NOLINK has completed. Repeat this command for each "compname" value indicated below. (Note that the command shown below spans two lines due to formatting restrictions): VMFSIM MODIFY VM SYSREQT D TDATA :PRODID prodid1%compname :SUP prodid2 where prodid1, compname, and prodid2 are: For the TCP/IP Use: for VM: prodid1 compname prodid2 -------------- --------- ---------- --------- Base Product: 5735falk tcpip 5735falf 5735falk tcpipsfs 5735falf 5735falk tcpipnoc 5735falf 5735falk tcpisfsnoc 5735falf NFS Feature: 5735fall vmnfs 5735falg 5735fall vmnfssfs 5735falg Kerberos US: 5735faln vmkerb 5735fali 5735faln vmkerbsfs 5735fali Kerberos WT: 5735falp vmkerb 5735falj 5735falp vmkerbsfs 5735falj 5. 1996/12/20 The provided softcopy SCEXIT SEXEC does not match the sample documented in Appendix A, "Telnet Session Connection Exit" of the "TCP/IP for VM: Planning and Customization" book (SC31-6082-03). The sample documented in Appendix A is the correct version. Note that in this sample, the following line: vaddr = '2'|| D2X(d4) /* 200-2FF */ should be: vaddr = '2'|| D2X(ip4) /* 200-2FF */ 4. 1994/01/19 Item Updated 1996/12/20 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 This commands should be issued within the the "Prelude" section of the TCPIP server initialization exit (TCPIPXIT EXEC). 3. 1992/10/30 During the installation process, customers must ensure network devices are attached to the TCPIP virtual machine through appropriate means. This can be accomplished by: 1) adding the appropriate 'DEDICATE' control statements to the TCPIP virtual machine's directory entry. -or- 2) modifying the "Prelude" section of the TCPIP server initialization exit (TCPIPXIT EXEC), so that the appropriate 'ATTACH' commands are issued for the devices in use. 2. 1992/01/10 Item Updated 1996/12/20 When processing configuration files, TCPIP and its associated applications parse records based on configuration "tokens"; each non-blank entry between blanks constitutes a token. When comments are created, at least one blank must follow the comment delimiter for most configuration files. Also, if a configuration file contains sequence numbers (usually in columns 73-80, if present) or other unrecognized tokens, unpredictable results may occur if that file is processed by TCPIP or its applications. 1. 1992/01/10 Item Updated 1996/12/20 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-03). 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. 1996/12/20 Item Updated 1996/06/20 The following errors exist in the "TCP/IP for VM: User's Guide" (SC31-6081-03): Chapter 2, "Transferring Files Using FTP:" Page Error / Correction ---- --------------------------------------------------- 31 The first paragraph in the Examples section refers to a "minidisk_password" parameter; this parameter is not supported - please disregard this reference. Chapter 6, "Monitoring the TCP/IP Network:" Page Error / Correction ---- --------------------------------------------------- 103 The section "RPCINFO Command Format" should include the following text, ahead of the RPCIFNO syntax diagram: RPCINFO requires SCEERUN LOADLIB to be globally available. You should ensure that: 1. The IBM Language Environment for MVS & VM can be accessed 2. SCEERUN is included in your GLOBAL LOADLIB list. Chapter 8, "Using the Network File System Commands:" Page Error / Correction ---- --------------------------------------------------- 114, Several sample OS/2 mount commands are incorrectly 118 illustrated. In all examples, the host name name "gdlvm7" should be preceded by a single space. 118 The second External Security Manager (ESM) example contains an error. The string: "...harpman,user id=elwood" should be: "...harpman,userid=elwood" 118 The last example, indicating a syntax error, is missing a line. The last line of this example should be: RPC_CANT_DECODE_ARGS 123 The SMSG Query command syntax is not correctly illustrated. The correct syntax is: |--Query---.---------.------------------| | | '--qtype--' 1. 1996/12/20 The following errors exist in the "TCP/IP for VM: Planning and Customization" (SC31-6082-03): Chapter 17, "Configuring the Network File System:" Page Error / Correction ---- --------------------------------------------------- 255 Disregard the following note: Note: The ES/9370 Integrated Ethernet adapter is not supported for use with NFS. The adapter cited is supported; however, due to the data transfer mechanism used by this adapter, NFS performance may be degraded in some environments. ************************************************************************ * 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. 17. 1999/12/07 Customers who apply service that includes updates for the SMTP server (SMTP MODULE) should ensure that outdated NOTE/ADDRBLOK file pairs are removed from the SMTP 191 disk prior to server initialization using the newly serviced module. The presence of NOTE/ADDRBLOK files that are several weeks, months (and in extreme cases, over one year) old can cause the SMTP server to enter a loop when it attempts to process old pieces of mail during initialization. 16. 1999/04/22 Due to packaging considerations, several IBM Network Station server support APARs/PTFs are now prerequisites for PTF UQ27174 (the PTF for the SMTP "spamming" and Source Route control APAR, PQ04382). Before this maintenance is received and applied, additional steps must be performed if the TCP/IP V2R4 IBM Network Station support PTFs are not already installed on your system. More information about this topic is available on the VM TCP/IP home page, via this URL: http://www.ibm.com/s390/vm/related/tcpip 15. 1996/06/20 When service for the TCP/IP for VM Base is placed into production, files associated with any installed TCP/IP for VM features are also copied to the TCPMAINT 591 minidisk; this includes the CATALOG files associated with each feature. These feature files are copied due to use of a wild card entry in the 5735FALK CATALOG file, which is used to process files targeted to the TCPMAINT 591 minidisk. However, only CATALOG files that reside on the TCPMAINT 491 minidisk (or the Local Modification) disk are used when files are placed into production. Thus, any such files that exist on the TCPMAINT 591 minidisk can be disregarded. 14. 1996/12/20 Item Updated 1997/01/14 APAR PN92441, through its associated PTF, UN99824, is used as the ordering mechanism for the current level of the TCP/IP 2.4.0 Program Directory. This APAR/PTF will be updated when significant changes are made to this document. An updated Program Directory (if available) can be ordered upon request by contacting the Level 2 support group, or or through the SRD (Service Request & Delivery) function of IBMLink/ServiceLink. Please see the text of APAR PN92441 for more information, if necessary. 13. 1996/12/20 When installing TCP/IP for VM Version 2 Release 4, its recommended that you also apply the latest available Recommended Service Upgrade (RSU). APAR PN92440, through its associated PTF, UN99924, is used as the ordering mechanism for the current level of the TCP/IP 2.4.0 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 or through the SRD (Service Request & Delivery) function of IBMLink/ServiceLink. Please see the text of APAR PN92440 for more information, if necessary. 12. 1996/08/01 Item Updated 1996/12/20 When planning for the installation of TCP/IP for VM Version 2 Release 4, note that some functions now make use of CMS Callable Services Library (CSL) routines. The FTP client and SRVRFTP modules are the most notable functions that require CSL routines. 11. 1995/05/26 Item Updated 1996/12/20 Many TCP/IP for VM functions are Pascal-based, and use VMCF communications to communicate with the TCPIP server. Therefore, these functions cannot be 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. (See CMS Utilities APAR VM58540 for more information -- this APAR discusses problems when using FTP in conjunction with WAKEUP). 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 10. 1995/02/22 Item Updated 1996/12/20 Mail which arrives at the SMTP machine via a TCP connection (the TCP/IP network) will be delivered to recipients without modification, with one exception: mail destined for VM mail recipients will be delivered such that null lines will be replaced by a line with a single blank. Mail which arrives at the SMTP machine via a batch SMTP (BSMTP) connection may be modified, based on the source of the mail, as follows: * Mail that arrives from a source whose structure preserves and does not pad blanks -- NETDATA and DMSDDL format files from SPOOL -- will be delivered to as noted above: only null lines replaced by a line with a single blank; existing blanks will be passed on to the recipient. * For mail that arrives from a source which may introduce extra blanks -- PUNCH, PRINT, and MSG (OfficeVision or Profs) format files from SPOOL -- ALL trailing blanks are removed from each line. 9. 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. 8. 1992/10/15 Item Updated 1998/04/14 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.) 7. 1992/07/16 Item Deleted 1997/01/13 6. 1992/06/05 Customers who have both of the following products installed -- Netview FTP Version 1 (568404801) and TCP/IP for VM Version 2 Release 4 (5735FAL00) -- may encounter problems due to FTP-related naming conflicts. Netview FTP V1 uses "FTP" as the default name for operator commands, while TCP/IP for VM provides an FTP client module with the name "FTP". When using the FTP-related function respective to a given product, ensure the appropriate product disks are linked and accessed, as required. 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 reading TCPIP * : 3. 1992/01/10 Item Updated 1998/04/14 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. 2. 1992/01/10 Item Deleted 1998/04/14 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 * ************************************************************************ 1. 2000/04/17 See Subsets 9801RSU and 0001RSU for service recommendations ************************************************************************ * 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. 2. 1996/12/20 Interdependent Product: All TC/PIP for VM Customers using FTPSERVE Problem: (VM60747) Multitasking and access problems in OpenExtensions BFS client Users Affected: OpenExtensions users and SFS/BFS filepool administrators under VM/ESA 2.1.0. Recommendation: Install UM28185 on VOLID 1000 1. 1995/04/07 Interdependent Product: All TCP/IP for VM Customers Problem: (VM59220) VMFBDMOD GLOBAL TXTLIB not reset or restored, which causes problems, possibly abends, during Build processing. Users Affected: All TCP/IP for VM Users Recommendation: Install the appropriate VMSES/E Service: UM27039 (VM/ESA 122) ************************************************************************ * 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: This item contains no records. ------------------------------------------------------------------------ PTF Exclude List: This item contains no records. ------------------------------------------------------------------------ PE APAR List: This item contains no records. ------------------------------------------------------------------------ Pending PE APAR List: PN92441