TCP/IP V2 R4 Corrective Service Memo
Corrective Service for TCP/IP V2 R4 for VM
The PTFs contained on this tape are in VMSES/E format, and must be
installed using VMSES/E commands. Product-specific instructions for
installing this service can be found in Chapter 7, "Service
Instructions" of the Program Directory for TCP/IP V2 R4 for VM and
Features.
+--- IMPORTANT NOTE! ------------------------------------------------+
| |
| Before this service can be applied to your system, additional |
| resources may need to be allocated for TCP/IP for VM. Depending |
| on the content of the PTF you've received, you may need to: |
| |
| DEFINE ADDITIONAL USER IDS AND MINIDISKS |
| INCREASE DELTA (2D2) MINIDISK STORAGE |
| |
+--------------------------------------------------------------------+
If you are applying the following corrective service to obtain TCP/IP
V2 R4 for VM support for the IBM NETWORK STATION:
APAR (INITIAL PTF) DESCRIPTION
PQ01770 (UQ03096) Network Station Support - BOOTPD / TFTPD
Function
PQ05644 (UQ06739) Network Station Support - Client Code
Function (This APAR/PTF supersedes
PQ02301/UQ03142)
PQ05305 (UQ15557) Network Station Support - DHCPD Server
Support
be certain you review the information in "IBM Network Station Support
Requirements" BEFORE you continue with the installation of this
service.
NOTE: Additional APARs and PTFs for IBM Network Station Client Code
may be available which should be applied instead of, or in addition to
PQ05644 (PTF UQ06739). To determine if such maintenance is available
or required, contact the VM/ESA CMS IBM Network Station support group.
Additional information can also be found on the VM/ESA IBM Network
Station home page on the World Wide Web. The URL for this home page
is:
http://www.vm.ibm.com/networkstation/
+--- NOTE -----------------------------------------------------------+
| |
| PTFs associated with IBM NETWORK STATION support (for example, |
| PTFs UQ03096, UQ06739 and UQ15557) ARE APPLICABLE TO ONLY VM/ESA |
| VERSION 2 RELEASE 1.0, OR LATER. If you have received these PTFs |
| and are using TCP/IP for VM on VM/ESA Version 1 Release 2.2, you |
| should create and maintain an EXCLUDE list so these PTFs are not |
| applied to your system. See the VMSES/E Introduction and |
| Reference for more information about creating and using an EXCLUDE |
| list. |
| |
+--------------------------------------------------------------------+
Chapter 7, "Service Instructions," of the Program Directory for TCP/IP
V2 R4 for VM and Features, describes the procedure to install
Corrective (COR) service for TCP/IP V2 R4 for VM.
The VMSES/E component of:
o VM/ESA Version 2 Release 1.0, or later.
o VM/ESA Version 1 Release 2.2
is required to install and service TCP/IP V2 R4 for VM.
NOTE: To become more familiar with service using VMSES/E, you should
read the introductory chapters of the VMSES/E Introduction and
Reference manual before you begin the service procedure for TCP/IP V2
R4 for VM. This manual also contains the command syntax for the
VMSES/E commands listed in the Program Directory.
VMSES/E Service Process Overview
The following is a brief description of the main steps in servicing
TCP/IP V2 R4 for VM using VMSES/E:
o Merging Service
Use the VMFMRDSK command to clear the alternate apply disk before
receiving new service. This allows you to easily remove the new
service if a serious problem is found.
o Receiving Service
The VMFREC command receives service from the delivery media and
places it on the Delta disk.
o Applying Service
The VMFAPPLY command updates the version vector table (VVT), which
identifies the service level of all the serviced parts. In
addition, AUX files are generated from the VVT for parts that
require them.
o Reapplying Local Service (if applicable)
All local service (mods) must be entered into the software
inventory to allow VMSES/E to track the changes and build them
into the system. Refer to Chapter 7 of the VM/ESA Service Guide
for this procedure.
o Building New Levels
The build task generates the serviced level of an object and
places the new object on a test BUILD disk.
o Placing the New Service into Production
Once the service is satisfactorily tested it should be put into
production by copying the new service to the production disks.
Customized files that have been serviced must be customized again.
----------------------------------------
IBM Network Station Support Requirements
TCP/IP V2 R4 for VM support for the IBM Network Station is provided
through the following corrective service:
APAR (INITIAL PTF) DESCRIPTION
PQ01770 (UQ03096) Network Station Support - BOOTPD / TFTPD
Function
PQ05644 (UQ06739) Network Station Support - Client Code
Function (This APAR/PTF supersedes
PQ02301/UQ03142)
PQ04280 (UQ05061) Network Station Support - TCPRUN BFS
Directory / README Updates
PQ05305 (UQ15557) Network Station Support - DHCPD Server
Support
The sections that follow describe new and changed DASD storage and
user ID requirements for TCP/IP V2 R4 for VM; these changes must be in
effect before you can apply the corrective service previously
identified.
Information about how to configure the BOOTPD and TFTPD servers, and
how to process the IBM Network Station "Client Code," is provided in
the following README files, which have been updated via APAR PQ04280:
o "BOOTPD README"
o "TFTPD README"
o "NSTATION README" (This file has been updated by APAR PQ05644, and
possibly later APARs).
Information about how to configure the DHCPD server is provided in:
o "DHCPD README"
NOTES:
1. The TCP/IP V2 R4 for VM BOOTPD and TFTPD server functions,
available through APAR PQ01770, and the DHCPD function provided
through APAR PQ05305 are provided specifically to support the IBM
Network Station.
2. The IBM Network Station support provided by the corrective service
identified above requires VM/ESA Version 2 Release 1.0, or later,
and the Byte File System (BFS) support provided by these releases
of VM/ESA.
3. The information herein is provided as a supplement to that
contained in the TCP/IP for VM Program Directory, and should be
retained for future reference.
Operating System Requirements
Before you install TCP/IP V2 R4 for VM support for the IBM Network
Station, the following CMS service must be installed:
o For VM/ESA Version 2 Release 1.0:
"VM61080" (Initial PTF: UM28330)
"VM61480" (Initial PTF: UM28656)
o For VM/ESA Version 2 Release 2.0:
"VM61080" (Initial PTF: UM28331)
"VM61480" (Initial PTF: UM28657)
NOTE: APAR VM61480 is required if DHCPD server support will be used.
TCP/IP Program Requirements
Before you can use DHCPD server support, the following TCP/IP service
must be installed:
o For VM/ESA Version 2 Release 1.0:
"PQ13330" (Initial PTF: UQ15381)
DASD Storage Requirements for IBM Network Station Support
TCP/IP for VM support for the IBM Network Station requires additional
minidisks to be defined, and the size of some existing minidisks to be
increased. See the following tables for detailed information about
these requirements.
+--- FORMATTING REMINDER --------------------------------------------+
| |
| All new minidisks that you add for IBM Network Station support |
| must be formatted before you install the corrective service |
| provided by PTF UQ03096. |
| |
+--------------------------------------------------------------------+
DASD Storage Requirements for New Target Minidisks
+---------------------------------------------------------------------------+
| Table 1. New DASD Storage Requirements for Target Minidisks - IBM Network |
| Station Support |
+-----------+---------+-------------+--------+--------+---------------------+
| | | STORAGE IN | | | |
| | | CYLINDERS | | | USAGE |
| MINIDISK | +------+------+ | +---------------------+
| OWNER | DEFAULT | | | FB-512 | SFS 4K | DEFAULT SFS |
| (USER ID) | ADDRESS | DASD | CYLS | BLOCKS | BLOCKS | DIRECTORY NAME |
+-----------+---------+------+------+--------+--------+---------------------+
| P735FALK | 493 | 3390 | 64 | 91200 | 11400 | Test build disk for |
| | | 3380 | 76 | | | IBM Network Station |
| | | 9345 | 76 | | | Client Code (3*) |
| | | | | | | |
+-----------+---------+------+------+--------+--------+---------------------+
| BOOTPD | 191 | 3390 | 2 | 2400 | _____ | BOOTPD user ID 191 |
| | | 3380 | 2 | | | minidisk (2*) |
| | | 9345 | 2 | | | |
+-----------+---------+------+------+--------+--------+---------------------+
| TFTPD | 191 | 3390 | 2 | 2400 | _____ | TFTPD user ID 191 |
| | | 3380 | 2 | | | minidisk |
| | | 9345 | 2 | | | |
+-----------+---------+------+------+--------+--------+---------------------+
| DHCPD | 191 | 3390 | 2 | 2400 | _____ | DHCPD user ID 191 |
| | | 3380 | 2 | | | minidisk (2*) |
| | | 9345 | 2 | | | |
+-----------+---------+------+------+--------+--------+---------------------+
NOTES:
1. Cylinder values defined in this table are based on a 4K block
size. FB-512 block and SFS values are derived from the 3380
cylinder values in this table. FBA minidisk sizes are shown in
512-byte blocks; these minidisks should be CMS formatted at 1K
size.
11400 4K blocks are needed for SFS install, including the IBM
Network Station Client Code (10 4K blocks without the IBM Network
Station Client Code).
2. Additional storage may need to be allocated for the BOOTPD and/or
DHCPD 191 minidisk, depending on the number of IBM Network Station
clients in your environment.
3. An SFS directory can be used in place of this minidisk. The
default SFS directory name specified for the TCPIPSFS component
is:
VMSYS:P735FALK.TCPIP.BUILDNWS
DASD Storage Requirements for Existing Minidisks
+---------------------------------------------------------------------------+
| Table 2. Additional DASD Storage Requirements for Existing Minidisks - |
| IBM Network Station Support |
+-----------+---------+-------------+--------+--------+---------------------+
| | | STORAGE IN | | | |
| | | CYLINDERS | | | USAGE |
| MINIDISK | +------+------+ | +---------------------+
| OWNER | DEFAULT | | | FB-512 | SFS 4K | DEFAULT SFS |
| (USER ID) | ADDRESS | DASD | CYLS | BLOCKS | BLOCKS | DIRECTORY NAME |
+-----------+---------+------+------+--------+--------+---------------------+
| P735FALK | 2D2 | 3390 | 67 | 96480 | 12060 | Contains serviced |
| | | 3380 | 81 | | | files. (3*, 4*) |
| | | 9345 | 81 | | | |
+-----------+---------+------+------+--------+--------+---------------------+
| P735FALK | 491 | 3390 | 4 | 5280 | _____ | Test build disk for |
| | | 3380 | 5 | | | server code. This |
| | | 9345 | 5 | | | code will be copied |
| | | | | | | to a production disk|
| | | | | | | (TCPMAINT 591), so |
| | | | | | | that disk will also |
| | | | | | | require this amount |
| | | | | | | of free space. |
+-----------+---------+------+------+--------+--------+---------------------+
| TCPMAINT | 198 | 3390 | __ | _____ | _____ | Contains config. |
| | | 3380 | __ | | | files for clients |
| | | 9345 | __ | | | and servers. (2*) |
+-----------+---------+------+------+--------+--------+---------------------+
| TCPMAINT | 591 | 3390 | 4 | 5280 | _____ | Production build |
| | | 3380 | 5 | | | disk for server |
| | | 9345 | 5 | | | code. |
+-----------+---------+------+------+--------+--------+---------------------+
NOTES:
1. Cylinder values defined in this table are based on a 4K block
size. FB-512 block and SFS values are derived from the 3380
cylinder values in this table. FBA minidisk sizes are shown in
512-byte blocks; these minidisks should be CMS formatted at 1K
size.
12060 4K blocks are needed for SFS install, including the IBM
Network Station Client Code (660 4K blocks without the IBM Network
Station Client Code).
2. For the TCPMAINT 198 minidisk, the changes required for IBM
Network Station support are negligible.
3. Additional storage will need to be allocated for the P735FALK 2D2
minidisk if you plan to maintain more than two distinct PTF-level
copies of the NSTATION TARBIN file in your environment.
4. An SFS directory can be used in place of this minidisk. The
default SFS directory name specified for the TCPIPSFS component
is:
VMSYS:P735FALK.TCPIP.DELTA
Byte File System (BFS) Storage Requirements
The Byte File System (BFS) is used to maintain the various files that
the TFTPD daemon loads down to the IBM Network Stations. These files
(the "Client Code"), are provided via APAR PQ05644 as a system "tar"
file, NSTATION TARBIN. You will need to ensure sufficient BFS file
space is available to accept these files when the NSTATION TARBIN file
is "exploded," or processed. The space required for the resulting
"Client Code" files is approximately 8000 4K blocks.
User ID Requirements
TCP/IP for VM support for the IBM Network Station requires additional
user IDs to be defined -- BOOTPD (possibly DHCPD as well) and TFTPD.
Sample directory entries for these user IDs follow:
USER BOOTPD BOOTPD 32M 32M G
INCLUDE CMSUSER
MACHINE XC
OPTION QUICKDSP SVMSTAT
LINK TCPMAINT 591 591 RR
LINK TCPMAINT 592 592 RR
LINK TCPMAINT 198 198 RR
USER TFTPD TFTPD 64M 64M G
INCLUDE CMSUSER
POSIXINFO UID 0 GID 0
MACHINE XC
OPTION QUICKDSP SVMSTAT APPLMON
LINK TCPMAINT 591 591 RR
LINK TCPMAINT 592 592 RR
LINK TCPMAINT 198 198 RR
USER DHCPD DHCPD 64M 64M G
INCLUDE CMSUSER
MACHINE XC
OPTION QUICKDSP SVMSTAT
LINK TCPMAINT 591 591 RR
LINK TCPMAINT 592 592 RR
LINK TCPMAINT 198 198 RR
Changed User ID Requirements
The P735FALK user ID directory entry and PROFILE EXEC must be modified
to account for several requirements associated with IBM Network
Station support. These changes are described in the following
sections.
P735FALK Directory Entry Requirements
The P735FALK directory entry changes required include:
o additional LINK statements to new product minidisks, identified in
Table 1.
o a LINK statement for the MAINT 193 minidisk
o increased virtual storage, to allow for processing of the IBM
Network Station Client Code
o adding a POSIXINFO statement for POSIX "superuser" capability
See the OpenExtensions for VM/ESA User's Guide and VM/ESA Planning and
Administration for more information about defining user IDs as POSIX
"superusers."
An abbreviated sample P735FALK directory entry which highlights the
changes previously described follows:
USER P735FALK P735FALK 16M 64M BG
INCLUDE CMSUSER
POSIXINFO UID 0 GID 0
...
LINK BOOTPD 191 273 MR
LINK TFTPD 191 275 MR
LINK DHCPD 191 278 MR
LINK MAINT 193 193 RR
...
Other P735FALK user ID Requirements
To allow for processing of the IBM Network Station Client Code files,
the P735FALK user ID must be given administrator authority for the BFS
file pool in which these files are installed. See VM/ESA File Pool
Planning, Administration and Operation for details about SFS/BFS file
pool configuration and administrator authority.
To ensure that the TFTPD server module will correctly build, verify
that the DMSPSLU TXTLIB, provided by APAR VM61080, is available. The
following command can be used to accomplish this:
global txtlib dmspslu
Changes to the P735FALK PROFILE EXEC are necessary as well, so that
the CMS LOADBFS EXEC, used to process the NSTATION TARBIN file, will
be present in the CMS search order. To accomplish this, update the
PROFILE EXEC to include the following statement:
'ACCESS 193' fm
where fm is an available file mode, for example, "O".
Server Run-time and Configuration Files
Several new server-related files are provided with the support for the
IBM Network Station. These files are indicated in Table 3 and Table
4. As with other product and configuration files, these new files are
processed by the TCP2PROD exec in conjunction with the 5735FALK
CATALOG file. An updated 5735FALK CATALOG is provided with APARs
PQ01770 and PQ05305 which will process these new files.
Table 3 lists the name and location of the server runtime files
provided by APARs PQ01770 and PQ05305, and the names and location of
these files after they've been placed into production. The servers
which use a given file have been identified as well.
+---------------------------------------------------------------------------+
| Table 3. Files to Copy into Production - IBM Network Station Support |
+------------+--------------+--------------------+-------------------+------+
| P735FALK | P735FALK | ORIGINAL FILE NAME | PRODUCTION FILE |SERVER|
| TEST DISK | LINK ADDRESS | / FILE TYPE | NAME / FILE TYPE |MDISK |
+------------+--------------+--------------------+-------------------+------+
| 491 | 273 | BOOTPPRO EXEC | PROFILE EXEC |BOOTPD|
| | | | | 191 |
+------------+--------------+--------------------+-------------------+------+
| 491 | 274 | TFTPDPRO EXEC | PROFILE EXEC |TFTPD |
| | | | | 191 |
+------------+--------------+--------------------+-------------------+------+
| 491 | 278 | DHCPDPRO EXEC | PROFILE EXEC |DHCPD |
| | | | | 191 |
+------------+--------------+--------------------+-------------------+------+
Table 4 lists the name and location of the sample files provided by
APAR PQ01770, and the names and location of these files after they've
customized. The servers which use a given file have been identified
as well.
+---------------------------------------------------------------------------+
| Table 4. Files to Customize - IBM Network Station Support |
+------------+--------------+--------------------+-------------------+------+
| SAMPLE | CONFIGURED | SAMPLE FILE NAME | CONFIGURED FILE |SERVER|
| DISK | DISK | / FILE TYPE | NAME / FILE TYPE | |
+------------+--------------+--------------------+-------------------+------+
| 591 | 198 | BOOTPXIT EXEC | no change |BOOTPD|
| 591 | 198 | BOOTPTAB SAMPLE | ETC BOOTPTAB |BOOTPD|
| 591 | 198 | TFTPDXIT EXEC | no change |TFTPD |
| 591 | 198 | DHCPDXIT EXEC | no change |DHCPD |
+------------+--------------+--------------------+-------------------+------+
Service Considerations
Maintaining Multiple NSTATION TARBIN (TARnnnnn) Files
The increased DASD storage requirements for the P735FALK 2D2 minidisk,
identified in Table 2 of "DASD Storage Requirements for Existing
Minidisks," are sufficient to maintain two distinct PTF-level copies
of the NSTATION TARBIN file. (The separate levels of this file are
maintained as NSTATION TARnnnnn, where nnnnn is a PTF number. For
example, NSTATION TAR05250.) If you want to maintain more than two
such copies of this file, you will need to increase the P735FALK 2D2
storage accordingly.
Pre-Service Processing
Before you receive corrective service that affects the NSTATION TARBIN
file, you need to ensure sufficient 2D2 minidisk space is available to
receive an updated copy of this file. This is especially true as the
NSTATION TARBIN file is serviced over time.
Assuming that the P735FALK 2D2 minidisk has been sufficiently
increased to maintain two copies of this file at a given time, you
will need to erase the OLDEST PTF-level copy of this file from this
minidisk. Use the following command to list the various PTF-level
copies of the NSTATION TARBIN file:
FILELIST NSTATION TAR* fm-delta
where fm-delta is the file mode of the P735FALK 2D2 minidisk. After
you have erased the appropriate NSTATION TARnnnnn file, you then can
continue the service process with the step, "Receive the Service," as
described in the TCP/IP for VM Program Directory.
New and Changed Files - IBM Network Station Support
New Files - PQ01770
Files which have been added to TCP/IP V2 R4 for VM via APAR PQ01770
are listed below. These new files provide the BOOTPD and TFTPD
function necessary to support the IBM Network Station.
o BOOTPD Files
BOOTPD $EXEC/EXEC BOOTPD HELP
BOOTPPRO $EXEC/EXEC BOOTPD README
BOOTPXIT $EXEC/EXEC
BOOTPTAB SAMPLE
o TFTPD Files
TFTPDPRO $EXEC/EXEC TFTPD HELP
TFTPDXIT $EXEC/EXEC TFTPD README
TFTPD MODULE
The TFTPD MODULE (built locally) is comprised of the following:
TFTCMD TEXT TFTCON TEXT TFTDFL TEXT TFTHLP TEXT
TFTINI TEXT TFTIPM TEXT TFTLFL TEXT TFTMAIN TEXT
TFTPFL TEXT TFTQRY TEXT TFTRFL TEXT TFTTIM TEXT
TFTTOK TEXT TFTTRC TEXT TFTTRM TEXT TFTUID TEXT
TFTWFL TEXT TFTXLT TEXT
o TFTPRP MACLIB (built locally)
TFTANCBK COPY TFTBIND COPY TFTCDBK COPY TFTCLIBK COPY
TFTCONST COPY TFTDBKBK COPY TFTDGRBK COPY TFTFILBK COPY
TFTMONBK COPY TFTPFLBK COPY TFTSRPBK COPY TFTTIMBK COPY
TFTUIDBK COPY TFTXMIBK COPY
o IBM Network Station - Related Files
NSTATION TARBIN ("dummy" file only)
NSTATION README
NSTATION $LOADBFS/LOADBFS
o Message Repositories
TCPUME REPOS/TEXT
TCPUMEB REPOS/TEXT
o VMSES/E-related Files
TCPBLTRP $EXEC/EXEC
TCPBL493 $EXEC/EXEC
New Files - PQ02301
Files which have been added to TCP/IP V2 R4 for VM via APAR PQ02301
are listed below. These new files provide the IBM Network Station
Client Code files, which run within the IBM Network Station, and
information about installing these files in the Byte File System
(BFS).
NSTATION TARBIN
New Files - PQ05305
Files which have been added to TCP/IP V2 R4 for VM via APAR PQ05305
are listed below. These new files provide the DHCPD function for
support of the IBM Network Station.
o DHCPD Files
DHCPD $EXEC/EXEC DHCPD HELP
DHCPDPRO $EXEC/EXEC DHCPD README
DHCPDXIT $EXEC/EXEC
o Message Repositories
TCPUME REPOS/TEXT
TCPUMEB REPOS/TEXT
o VMSES/E-related Files
TCPBLTRP $EXEC/EXEC
TCPBL493 $EXEC/EXEC
Changed Files - PQ01770
o Server-related Files
TCPRUN $EXEC/EXEC
o VMSES/E-related Files
5735FALK $PPF TCPBLM91 $EXEC/EXEC
5735FALK PRODPART TCPBL491 $EXEC/EXEC
5735FALK CATALOG
Changed Files - PQ05644
Files which have been changed via APAR PQ05644 are listed below.
NSTATION TARBIN
NSTATION README
Changed Files - PQ05305
o Server-related Files
TCPRUN $EXEC/EXEC
o Message Repositories
TCPUME REPOS/TEXT
TCPUMEB REPOS/TEXT
o VMSES/E-related Files
5735FALK $PPF TCPBL491 $EXEC/EXEC
5735FALK PRODPART 5735FALK CATALOG