TCP/IP Function Level 320 Preventive Service Planning
(PSP) Bucket
**> Last update: 06 Mar 2002
**> Synch'd w/RETAIN: 14 Oct 2002
***********************
* SUBSET VM320 *
***********************
This SUBSET contains installation information for TCP/IP Function
Level 320 for VM/ESA Version 2 Release 4.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. 1999/09/13 Documentation Changes
3. 2002/03/06 General Information
4. 2001/06/27 Service Recommendations - See Subsets 0002RSU or 0101RSU
5. yyyy/mm/dd 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.
5. 2001/01/25 Prior to performing installation and service tasks,
ensure that the PROFILE EXEC invoked by the TCP/IP
installation user ID (P735FALW) 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 P735FALW installation user ID)
will establish the minimal environment necessary to
install and service the TCP/IP Feature as described in
the TCP/IP FL320 Program Directory.
4. 1999/11/22 Customers who plan to use the LPD server (LPSERVE), note
the following. If/when the LPD server is initialized
without having modified the sample LPD CONFIG
configuration file, this server will likely fail and
report the following error:
Could not spool PRINTER TO POSIXPRT. Return code
was 53
The errors reported above prevent server startup.
TCRUN1015I Server ended with RC=40 at hh:mm:ss on
This error results from an attempt to direct SPOOL output
to a 'POSIXPRT' user ID (that in all likelihood, does not
exist), due to the presence of the 'SPOOL= TO POSIXPRT'
entry in the POSIXPRT service definition. To avoid this
error, modify the sample LPD CONFIG file prior to its use
and specify services and parameters that are appropriate
for your environment.
3. 1999/07/22 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.
2. 1999/07/22 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. 1999/07/22 Prior to installing the TCP/IP feature for VM/ESA, you
may find it useful to review the content of the following
ITSO Redbooks if you're not familiar with TCP/IP
protocols, functions and networking principles:
* "TCP/IP Tutorial and Technical Overview",
(GG24-3376)
* "The Basics of IP Network Design",
(SG24-2580)
* "OS/390 eNetwork Communications Server V2R5 TCP/IP
Implementation Guide, Volume 1: Configuration and
Routing",
(SG24-5227)
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.
1. 1999/07/22 Item Updated 1999/09/13
The following errors exist in "TCP/IP Function Level
320 Planning and Customization" (SC24-5847-01):
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 3, "TCP/IP Server
Configuration."
Chapter 2, "Installation Requirements for TCP/IP"
Page Error / Correction
---- ---------------------------------------------------
14 The TCP/IP feature requirements listed under the
"Software Environment" heading indicate that VM/ESA
Version 2 Release 3.0, and the Language Environment
supplied with this level of VM/ESA are required to
run TCP/IP Function Level 320. This is not
correct; VM/ESA Version 2 Release 4.0 and its
corresponding Language Environment are required.
************************************************************************
* 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.
9. 2002/03/06 When TCP/IP server exit samples are customized to meet
the needs of your installation, note that commands
which make use of TCP/IP services should *not* be used
within any of these exits.
TCP/IP server exits to which this limitation applies
are:
TCP/IP Server Supported Exits
-------------- -----------------------------
TCP/IP (Stack) SCEXIT PMEXIT
DNS VALIDUSR
FTP FTPEXIT CHKIPADR
NFS VMNFSCMS VMNFSMON VMNFSSMG
SMTP SMTPCMDX SMTPFWDX SMTPVERX
UFT UFTCMDX UFTNSLKX
Examples of programs and functions that should not be
utilized are:
* PING, NSLOOKUP, REXEC
* TCP/IP-oriented CMS PIPE stages and Rexx Sockets APIs
* Local or third-party applications that use TCP/IP
socket interfaces or other services
For the TCP/IP stack server, doing so creates a
situation where the stack is required to provide TCP/IP
services to itself, at which point internal interrupt
handling and blocking issues then arise. For other
TCP/IP servers, similar problems can result, not just
with VMCF or IUCV communication interrupt handling, but
also with TCP/IP connection management.
Attempts to make use of a secondary TCP/IP "worker"
stack to provide the desired information will also
encounter the same problems just described, regardless
of the servers involved.
Thus, care must be taken to ensure that all commands or
programs invoked within a TCP/IP server exit do not
adversely affect the operation of that server. This
includes not just TCP/IP-oriented commands, but those
which can cause CMS storage management changes,
extended wait conditions, or that otherwise adversely
affect server performance. Without such care,
unpredictable results or other operational errors can
and may occur.
8. 1999/07/22 APAR PQ25525, through its associated PTF, UQ99320, is
used as the ordering mechanism for the current level of
the TCP/IP Function Level 320 RSU. This APAR/PTF will be
updated during every RSU cycle to indicate the RSU level
that 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. Please see the text of
APAR PQ25525 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 also use VMCF
communications (such as the CMS Utility, WAKEUP); doing
so may produce intermittent hangs during processing or
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 reading TCPIP * :
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, and 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 the 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 *
************************************************************************
1. 2001/06/27 See Subset 0002RSU or 0101RSU 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. 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:
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:
This item contains no records.