Upgrade TCPIP220, Subset VM220:
This SUBSET contains installation information for TCP/IP Version 2
Release 2 Modification 0 for VM.
Change Summary
Date Last
Changed Section
1. 97/01/27 INSTALLATION INFORMATION
2. 95/03/09 DOCUMENTATION CHANGES
3. 97/01/27 GENERAL INFORMATION
4. 95/12/14 SERVICE RECOMMENDATIONS
5. 95/05/08 CROSS PRODUCT DEPENDENCIES
Service Recommendation Summary
DATE APAR PTF VOLID COMMENTS
12 95/12/14 PN76063 UN85411 1000 HIPER USING ' LPR (CC ' TO PRINT
11 95/11/14 PN76752 UN84078 1000 HIPER VM TCP/IP (XA) I/O ERROR
10 95/07/14 PN72517 ITEM DELETED 95/09/27
9 95/05/24 PN71174 UN77245 1000 HIPER AMPX054I MESSAGE LPR
8 95/05/24 PN71174 UN77287 1000 HIPER AMPX054I MESSAGE LPR
7 93/01/25 PN34230 UN35443 9401 FTP GET COMMAND FAILS WITH
6 92/12/23 PN31912 UN33162 9401 SUPERSEDED PTFS NOT HANDLED
5 92/11/26 PN28724 UN31624 9401 NETSTAT TELNET DISPLAY
4 92/07/09 PN18900 UN24094 9401 FTP CLIENT HANGS WHEN DOING A
3 92/04/10 PN17716 UN19085 9401 ADD CLAW (COMMON LINK ACCESS
2 92/03/25 PN16801 UN17773 9401 NOTE EXEC FOR SMTP SENDS ALL
1. 92/03/20 PN16954 UN17639 9401 SERVICE EXEC DOES NOT SUPPORT
This section contains changes relevant to the installation of the
product, or to its Program Directory.
16. 95/03/09 When customizing PROFILE TCPIP, the TRANSFORM parameter
should not be specified as part of the
INTERNALCLIENTPARMS statement unless the Sim3270
emulation program (provided by Simware, Inc.) is
installed. The TNSIMHPI TEXT file, referenced in the
description of the TRANSFORM parameter, is supplied by
Simware.
15. 95/02/06 Figure 15 in Chapter 3 of "TCP/IP for VM: Planning and
Customization" (SC31-6082-01), p. 37, is incomplete.
- The MACHINE 370 statement is missing. The REXECD
virtual machine is required to be in 370 mode.
- The following statements should be added to the REXECD
server directory entry:
IUCV ANY
OPTION MAXCONN 255
14. 94/01/19 ITEM UPDATED 97/01/27
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). For non-VM/ESA
systems, this should be accomplished via the following
command:
CP SET MIH OFF
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).
13. 94/01/07 Effective 11/19/93, the TCP/IP for VM product tapes were
replaced at ISMD boulder. The tapes contain all TCP/IP
maintenance thru July 1993. Customers who order the
product after this date will not need to install the
previous two year's PTFs.
However, there are several special items that customers
should be aware of; these are:
1) The Service Document that describes how to install
PTFs -- the document for Service exec (S5735FAL EXEC)
-- is in Tape File 1 of the BASE tape; it's named
either SERVDOC LIST1403 or SERVDOC LIST3820. The
Service exec is also in Tape File 1 of the base tape.
2) A S5735FAL PTFSUMM file is included on the tape for
two reasons -- to provide:
a) customers information as to which APARs have been
included in the code.
b) information required for the Service exec to
determine which PTFs have been applied to the
system.
This file is in Tape File 3 (the "Server Common" file
for the TCPMAINT 591 disk) of the base tape.
Customers should move this file from the 592 disk to
their PTF staging disk, for future service
installation.
3) APAR PN47819 provides a central repository for all
documentation updates to the TCP/IP for VM manuals.
This APAR is basically a rollup of all the Memo To
Users that were shipped with previous PTFs. Customers
are encouraged to obtain the PTF for this APAR, so
that one central document is available which describes
new functions and parameters added over the previous
two years. The PTF for this APAR supplies both a
FALDOC LIST3820 file and a FALDOCA LIST1403 file.
NOTE: This PTF is not included on the refreshed SDO
product tape.
12. 93/08/11 During a continuation of a partial install, the following
files must be available on the installation work disk:
I5735AFL EXEC U5735FAL EXEC V5735FAL EXEC
S5735FAL EXEC I5735FAL 022013C 5735FAL CONFIG
If not present, the installation exec will fail with a
01E message.
NOTE:
Some of these execs may have been updated by the
application of PTFs. Therefore, re-loading files from
the Base Feature tape will replace any updated execs with
their original counterparts. To avoid this problem when
performing a partial install, one possible solution is to
store any modified copies of the above execs elsewhere,
and then replace the base-level copies (that result after
the VMFPLC2 LOAD command completes) with the previously
saved (current) copies.
Another option would be to manually copy only the needed
Product Identifier files to the installation work disk.
11. 93/03/18 When using SDO to install TCP/IP for VM, the HISTORY and
PTFSUMM files required for future TCP/IP maintenance will
not be created. Until the 6/93 SDO refresh is available,
it's recommended that the Service exec (S5735FAL EXEC) be
used to apply maintenance.
10. 93/02/12 For the VMNFS server to work in a RACF environment,
the VERIFYPW module must be NUCXLOADed within the VMNFS
server machine. This can be accomplished by adding the
following statement:
NUCXLOAD VERIFYPW RPIVAL
to the 'Prelude' section of the VMNFS initialization exit
(VMNFSXIT EXEC).
9. 93/02/11 The size of the 2C1 disk may need to be increased when
installing multiple PTFs at one time. The Program
Directory indicates 50 cylinders are required for the 2C1
disk; this is true only when installing TCP/IP for VM
without maintenance.
8. 92/10/30 During the installation process, it is the customer's
responsibility to attach network devices to the TCPIP
virtual machine. 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.
7. 92/02/28 The only virtual machines that will exploit VM/XA
capabilities are the TCPIP and SMTP machines (for the SMTP
machine, APAR PN65563 is required). When TCPIP and SMTP
are defined as XA (or ESA) mode machines, the respective
TCPIPXA and SMTPXA modules will be used.
While the SNALNKA and X25IPI virtual machines can be IPLed
in XA mode to run in a GCSXA environment, they will not
utilize any addressing above the 16 Meg line.
NOTE: The REXECD server is required to be a 370 mode
machine. This requirement also applies to the SMTP
machine, if APAR PN65563 has not been applied.
6. 92/01/14 The softcopy Memo To Users (I5735FAL MEMO) shipped with
some tapes is incorrect. For certain tapes, the Version
2 Release 1 Memo has been provided, rather than the
Version 2 Release 2 Memo.
The correct version of the I5735FAL MEMO file is dated
11/25/91. The softcopy V2R2 Memo To Users should be a
duplicate of the hardcopy Program Directory. The
following tapes contain the wrong memos:
- BASE: Tapes 1 and 2 of the 1600 BPI version only. (The
BASE tape for all other media have the correct Memo.)
- EXAMPLES: Tapes for ALL media.
- SOURCE: Tapes 1 and 2 of the 1600 BPI version only.
(The SOURCE tape for all other media have the correct
Memo.)
- KERBEROS: US and Non-US versions, tapes for ALL media.
- NFS: Tapes for ALL media.
The TEXT tape sent to all customers has the correct Memo.
Therefore, the correct Memo To Users for V2R2 can be
loaded from the TEXT tape, if necessary.
5. 92/01/14 The sample TCPIP directory file, TCPIP DIRMODEL, provided
with TCP/IP for VM is missing option BMX, and has an
incorrect MAXCONN value. The incorrect entry is:
OPTION ECMODE MAXCONN 255 DIAG98
The correct entry should be:
OPTION ECMODE BMX MAXCONN 1024 DIAG98
If the incorrect OPTION statement is used, TCPRUN EXEC
will issue a CP DEFINE CHANNELS BMX command and re-ipl
the TCPIP virtual machine. An indication that the BMX
option is missing will be the following message:
SEL channels defined; redefining as BMX.
NOTE: The sample directory in "TCP/IP for VM Planning
and Customization" (SC31-6082-01) is correct. Only
the sample on the tape is incorrect.
Section 6.1.2 of the Program Directory refers to sample
DIRMODEL profiles. The GCSUSER DIRMODEL and ADM_SERV
DIRMODEL profiles contain incorrect INCLUDE entries.
The GCSUSER DIRMODEL contains the line: INCLUDE CMSUSER
The INCLUDE should be: INCLUDE GCSUSER
The ADM_SERV DIRMODEL contains the line: INCLUDE TCSERVE
The INCLUDE should be: INCLUDE CMSUSER
4. 92/01/10 When processing configuration files, TCPIP and its
associated applications parse records based on
configuration "tokens"; each non-blank entry between
blanks constitutes a token. If a configuration file
containing sequence numbers (usually in columns 73-80, if
present) is processed by TCPIP -- or its applications --
the sequence numbers will be construed as configuration
"tokens", and will cause unpredictable results.
Also, when beginning a comment in configuration files, at
least one blank must follow the comment delimiter.
3. 92/01/10 When the X Window GDDM interface (GDDMXD/VM) is installed,
the INSTGDXD EXEC invokes a GDDM exec to rebuild the GDDM
shared segments. You should be familiar with how GDDM
has been installed on your system before you install
GDDMXD/VM, so that the correct responses can be provided
in response to prompts regarding the GDDM product.
2. 92/01/10 The 9370 integrated Ethernet adapter is not supported for
use with the NFS. This is documented in "TCP/IP for VM
Planning and Customization" (SC31-6082-01) on page 265.
1. 92/01/10 ITEM UPDATED 97/01/27
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)
This section outlines major errors in the product's published
documentation.
7. 95/03/09 Chapter 13 of "TCP/IP for VM: Planning and Customization"
(SC31-6082-01), p. 241, indicates that SNALINK is
automatically started by PROFILE GCS when GCS is
initialized. This is incorrect; SNALINK is not
automatically started when TCP/IP for VM is installed.
Like other applications that run in the GCS environment,
the SNALNKA virtual machine needs to be AUTOLOGGed by an
appropriate resource, as is done for other machines in
the GCS group (VTAM, RSCS, etc.).
Also, if any segments in the GCS group are RESTRICTED
(VM/ESA only), a NAMESAVE statement must be included in
the SNALNKA directory for those segments.
6. 94/03/24 The Memo To Users file shipped with UN53379 contains a
documentation error. Under the portion: PTF INSTALLATION,
it lists two files:
FALDOC LIST3820 and FALDOC LIST1403.
This is incorrect and should read:
FALDOC LIST3820 and FALDOCA LIST1403.
5. 93/11/11 The ASSORTEDPARMS statement documentation in
Chapter 5 of "TCP/IP for VM: Planning and Customization"
(SC31-6082-01), p. 77, is incomplete. The (new) PDSM
and NOUDPQUEUELIMIT parameters are not discussed. For
more information about these parameters, refer to DOC
APAR PN39515.
4. 92/10/30 Page 212 of the "TCP/IP for VM Planning and Customization"
book (SC31-6082-01) requires the following changes in the
first paragraph:
1) The NAMESRV exit exec is incorrectly identified as
NAMEDXIT EXEC; the correct name is: NAMESXIT EXEC.
2) The default nameserver configuration file is
incorrectly identified as NSMAIN CONFIG; the correct
file names is: NSMAIN DATA.
3) The sentence:
"However, you can use a different configuration file
by modifying the global variable TCPSTART in the
NAMEDXIT EXEC file and specifying the name of the
configuration file as an argument to the NSMAINT
command."
should be changed to:
"However, you can use a different configuration file
by setting the 'parms' variable in the NAMESXIT EXEC
to the name of the configuration file you wish to
use."
3. 92/10/30 Page 131 of the "TCP/IP for VM Planning and Customization"
book (SC31-6082-01) implies that the C/370 runtime
library is required for SMTP. This is incorrect -- the
SMTP virtual machine does not need access to C/370
runtime library.
2. 92/10/06 Chapter 2 of "TCP/IP for VM: Planning and Customization"
(SC31-6082-01), p. 21, "Software Environment"; the
following "Note" is not accurate:
Note: The C and Pascal Libraries each include the
corresponding compiler.
Additional clarification
- For C/370, the compiler and library are offered only as
separate products; having one of these products does
not imply that its counterpart is available. This
applies to Version 1 and Version 2 of C/370.
- For Pascal, The library and compiler can be purchased
together, or the library can be bought separately. The
two products involved are:
5668-717 -- VS/Pascal Library
5668-767 -- VS/Pascal Compiler and Library
1. 92/02/26 The content of several README files is incorrect or
inaccurate. The following changes should be noted:
In the NDB README file:
- The reference to "TCP/IP for VM: Installation Guide"
should be interpreted to mean "TCP/IP Version 2
Release 2 for VM: Planning and Customization." Also,
the chapter named "Configuring the Network Database
(NDB) System" is Chapter 21, not Chapter 20.
- The reference to Page 289 in the Planning and
Customization publication should be a reference to
Page 311 of the Same publication.
In the PROGREF README file:
- All references to "TCP/IP Version 2 for VM:
Programmer's Reference" should be interpreted to mean
"TCP/IP Version 2 Release 2 for VM: Programmer's
Reference."
- The reference to Page 352 in the Planning and
Customization publication should be a reference to
Page 373 of the same publication.
- References to the file XT REMAP (XT@REMAP) are in
terms of the "Include" statement within the header
file. The file exists on disk as HT@REMAP H, not
XT@REAMP.H.
In the SMTP README file:
- The reference to Page 134 in the Planning and
Customization publication should be a reference to
Page 145 in the same publication. Similarly, the
reference to the example on Page 147 of the same
publication should be a reference to Page 160.
Also, the following documentation changes should be
noted:
- The FTPSERVE virtual machine description -- Chapter 3
of of "TCP/IP for VM: Planning and Customization"
(SC31-6082-01), pp. 32-33 -- contains some extraneous
statement descriptions for ALLOW and ANY (both of these
statements relate to IUCV). These statements are not
applicable to the FTPSERVE virtual machine.
- Page 214 of of of "TCP/IP for VM: Planning and
Customization" (SC31-6082-01), the syntax diagram
describing the format of a resource record (used as
input for the NSDBLOAD MODULE) is incorrect. The
correct diagram is;
>>--name--+---+--+-----+--recordtype--recorddata---><
| | | |
-ttl- -class-
The parameter descriptions are not affected by this
change.
THIS SECTION CONTAINS GENERAL INFORMATION, I.E., HINTS/TIPS.
33. 95/05/26 ITEM UPDATED 97/01/27
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
32. 95/02/22 The PN60371 level SMTP MODULE does not truncate or strip
trailing blanks in mail as part of its processing. As a
result, mail handling problems may arise when mail is
processed at its destination. Symptoms of such problems
include records from the mail 'body' being forwarded as
RFC 822 header records, or an extraneous BSMTP QUIT in
the mail body.
These problems may be especially prevalent for mail
generated via OfficeVision (or PROFS).
If these problems are encountered, you should obtain and
apply APAR PN66607. However, note that after applying this
APAR, problems related to the continued presence of blanks
may persist. This may be the case if mail is being
forwarded to SMTP in NETDATA or DISKDUMP format, because
blank lines or trailing blanks remain "as is" when outbound
mail arrives in either of these formats.
31. 95/02/06 ITEM UPDATED 96/02/19
Slave (or end-user) virtual machines that are used to
execute REXEC commands are autologged by by the REXECD
server as part of the the REXEC function. Due to the
way the REXEC function is implemented, the following
restrictions exist for any virtual machine that is used
as a "slave":
- A secondary console cannot exist for a slave machine.
If a secondary console is defined for these virtual
machines, REXECD will not be able to send the output
back to the REXEC client; when this is the case, the
REXEC client will usually hang as well.
- Access to the TCPMAINT 592 (Client code) minidisk
must be provided (i.e., via the machine's PROFILE
EXEC) during autologging of the slave.
- Commands to be executed within a "slave" machine
must not require user intervention in order to
complete.
NOTE: Please refer to APAR PN78579 for more information
about using REXEC and configuring REXECD, as this
APAR provides revised documentation on these topics.
30. 94/06/01 The following files were originally shipped on the wrong
disk, and were serviced (via a PTF) onto another disk.
They should be erased from the original disk (listed
below), as they will not be adequately maintained by PUT
tapes or PTFs. These files may also need to be erased
from the PTF Staging disk, following the application of a
PUT Tape.
Original PTFed
Filename Filetype Erase from Disk Feature Feature
-------- -------- ----------------- -------- -------
CMALLHL H OWNER_SOURCE_DISK 5735FALE 5735FALA
CBISSDI ASSEMBLE OWNER_SOURCE_DISK 5735FALE 5735FALA
NSACQ CSQL OWNER_SRVCOM_DISK 5735FALA 5735FALE
Correct Disk (After PUT/PTF Application)
----------------------------------------
OWNER_CLICOM_DISK
OWNER_SAMPLE_SOURC
OWNER_SOURCE_DISK
29. 94/02/15 The PUT install EXEC supplied with the TCP/IP for VM
9401 PUT tape does not correctly update the S5735FAL
PTFSUMM and S5735FAL PTFSUPED files. As a result, errors
may be encountered if/when additional corrective service
is applied.
To correct this problem, customers should obtain the
corrective service supplied for APAR PN52380. This APAR
supplies an updated exec that will correctly maintain the
PTFSUMM and PTFSUPED files. The Memo To Users, supplied
with the APAR corrective service, contains instructions
for installing the 9401 PUT tape with this updated exec.
28. 93/12/17 When a 370 mode TCPIP virtual machine is run on VM/ESA
2.0 and Offload is in use, storage problems may arise
when using the following default:
DATABUFFERPOOLSIZE 160 28672
Specifically, an ABEND80A may occur; this ABEND results
from the inability of the TCPIP virtual machine to
acquire the buffers as specified in the PROFILE TCPIP
configuration file.
This may be avoided by either reducing the "buffer_size"
value from 28672 to 8192, or running TCPIP in an XA or
ESA mode virtual machine, so that the TCPIPXA MODULE is
used.
27. 93/11/11 A VMFMSG EXEC is supplied as part of TCP/IP for VM. The
naming of this file duplicates that of a VMFMSG EXEC
supplied as part of VM/SES (SES). To avoid problems, the
TCP/IP-supplied VMFMSG EXEC should be renamed to: TCPMSG
EXEC.
26. 93/09/02 Except for TCPIPXA and SMTPXA (SMTPXA is provided via APAR
PN65563), TCP/IP for VM applications are released to run in
370 mode and are linked AMODE24 RMODE24. When TCP/IP
applications are run in ESA (or XA) mode machines, a "User
Abend 2052" (ABENDU2052) error may occur; this error
usually occurs because the C/370 Named Saved Segment (DCSS)
has been defined above the 16M line. To avoid this
problem, the C/370 Named Saved Segment must either be
re-defined below the 16M line or the affected applications
must be run in a 370 mode machine, so that C/370 LOADLIBs
are used.
Note that some client applications -- such as DIG and
NSLOOKUP -- will run in ESA (or XA) mode, if they are
re-linked with AMODE 31 RMODE 31.
25. 93/05/07 The NSUSERID statement can be included in the TCPIP DATA
file. This statement allows an alternate user ID to be
specified for the name server. The syntax of this
statement is:
>>--NSUSERID-- user_id --><
24. 93/03/29 The Verification exec (V5735FAL EXEC) requires the
C/370 runtime library in order to execute; this exec
will fail when the library is not on a linked disk.
23. 93/02/10 When attempting to install service for TCP/IP for VM,
errors may occur due to insufficient temporary disk
space. The error will be indicated by messages:
116E Error loading file <file num> from PTF tape to
temporary disk.
Return Code = <rc> from the VMFPLC2 LOAD command.
Terminating PTF processing.
The underlying cause of the error can be:
1) The system does not have sufficient temporary disk
space available.
2) The PTF tape file contains a large number of PTFs,
and the amount of data in a tape file exceeds the
maximum temporary space requested by the Service
exec.
The maximum amount of temporary storage the Service exec
(S5735FAL EXEC) will attempt to obtain is 120 cylinders
of 3380 storage. (Other device types can be used if
available, and the maximum space requested will be
equivalent to 120 3380 cylinders.) If insufficient disk
space is available on the system, the Service exec will
decrement the storage request by 10 cylinders and try to
obtain the storage again.
In order to install a PTF tape for which a tape file
cannot be loaded into 120 cylinders, customers must
modify the Service exec (S5735FAL EXEC) to change the
maximum amount of space requested during the PTF
installation process. This change should be made in the
routine: Get_Tdisk
For example, to increase the storage obtained for 3380
devices, locate the statement:
t3380_dasd = '3380' /* Suffix for 3380 Tdisk */
Then, change the assignment of '120' in the line:
t3380.1 = 120 /* 120 3380 cyls */
to:
t3380.1 = xxx /* 120 3380 cyls */
where "xxx" is the amount of space the Service exec is to
obtain.
This same type of process can be used to change the
amount of space obtained for other device types. All of
the device types and storage request sizes are in routine
Get_Tdisk. Editing the appropriate line within this
routine will change the space requirements requested by
the Service exec.
NOTE: Attempts to install ALL PTF maintenance for
TCP/IP for VM may require a TEMP disk size
greater than 200 cylinders.
22. 92/11/18 When configuring an RS/6000 ip connection with the Block
Multiplexer (BMX) adapter, customers should refer to ASKQ
documents Q604637 and G010305. These items describe BMX
adapter problems, configuration problems, and also
provide configuration specific information.
21. 92/10/30 Page 266 of the (R220) "Planning and Customization" book
(SC31-6082) implies that a clean copy of the VMNFS
HISTORY file is on the VMNFS 195 disk. This will be true
only if the VMMNFS HISTORY file is copied from VMNFS 191
disk to the VMNFS 195 disk prior to running VMNFS.
20. 92/10/26 The TCPIPXA module may experience random and
unpredictable errors when executed due to changes in
the way CMS handled loadlibs that were linkedited using
the default options. If your CMS is at level PUT 9105,
or later, or if you have installed the PTF applicable to
your operating system level from the following list, then
a VS/Pascal APAR fix must be applied to your system if
you intend to use the TCPIPXA module.
- For product identifier 5749DMS00
APAR: VM46544
Text: CMS Fails to Reload Loadlib Marked Nonreusable
PTF : UV53615
- For product identifier 566430802
APAR: VM47435
Text: CMS Fails to Reload Loadlib Marked Nonreusable
PTF : UM18392
- For product identifier 568411201 (VM/ESA 1.0)
APAR: VM47436
Text: CMS Fails to Reload Loadlib Marked Nonreusable
PTF : UM18385
- For product identifier 568411201 (VM/ESA 1.1)
NOTE: The changes in VM APAR VM47436 (see above) are
incorporated into the base VM/ESA 1.1 release.
These APARs address a problem whereby DMSSLN did not
check The link flags to see if a loadlib is reusable or
not. A loadlib that was linkedited using the default
options, was treated by CMS as being a reusable loadlib,
when the default is nonreentrant and nonreusable. The
corrective service for the APARs remedies this incorrect
behavior by having DMSSLN now check if the object
previously loaded was loaded out of a loadlib. If so,
the attributes of the object will be checked and if the
object is not reentrant reusable, it will be reloaded.
For the required VS/Pascal service, if you have both the
compiler and library installed (product number 5668-767),
the applicable APAR is PN17249 (PTF UN23639). If you
have only the library (product number 5668-717), the
applicable APAR is PN15809 (PTF UN23833). These ptfs
provide a modified VS/Pascal installation exec which
ensures that the run time Libraries are built with the
reentrant / reusable attributes.
Failure to apply the applicable VS/Pascal APAR fix will
result in random and unpredictable errors when the TCPPXA
MODULE is used in conjunction with the old Pascal runtime
library.
19. 92/10/20 TCP/IP for VM PTF tapes may contain a cover letter that
eludes to installing the PTFs with either the VMFMERGE or
a RENAME exec. TCP/IP PTFs should be loaded from tape
with the TCP/IP-supplied Service exec (S5735FAL EXEC),
and not via the VMFMERGE or RENAME execs. For additional
information about completing the installation of a PTF,
refer to the file appropriate PTFnnnnn MEMO on the
TCPMAINT 2C1 disk (where "nnnnn" is a PTF number).
18. 92/10/15 When a nameserver is not in use, 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 received when
attempting to start SMTP:
Invalid value nn specified for RCPTRESPONSEDELAY.
Default used.
("nn" in this message will be value specified as part of
the RCPTRESPONSEDELAY statement.)
17. 92/07/16 ITEM DELETED 97/01/13
16. 92/06/26 When installing TCP/IP for VM under a RACF environment, the
ADM_SERV virtual machine must be renamed in order to
define it to RACF, because the underscore character ("_")
is undefinable to RACF. When this is the case, the value
"ADM_SERV" must also be changed to "ADMSERV" for the
following:
- PROFILE TCPIP: The ADM_SERV name must be changed in
the AUTOLOG and PORT statements to reflect "ADMSERV".
- VMKERB directory entry: The example definition for
this machine has a LINK statement to the ADM_SERV 191
minidisk. This LINK statement should be changed to
reflect "ADMSERV".
- TCPRUN EXEC: the routine for setting up the Kerberos
administrator has the line:
default_command = 'ADM_SERV'
This should be changed to:
default_command = 'ADMSERV'
15. 92/04/13 The TCP/IP for VM APARs PN16954 (PTF UN17639) and PN31912
(UN33162) make the Service exec (S5735FAL EXEC)
compatible with the way PTFs are shipped for TCP/IP for
VM. The PTFs contain additional documentation regarding
the TCP/IP for VM service process including all messages
and codes generated by the Service exec. This
information is included in both LIST1403 and LIST3820
formats. All customers should print and review this
documentation.
14. 92/03/03 The FTPSERVE virtual machine must have WRITE access to
its 191 minidisk. If WRITE access is lacking, a DIR
command issued to the server will produce the following
messages:
AMPX055I and DMSABE141T Abend User 041
When a DIR command is received from a remote workstation,
FTPSERVE builds a file on its 191 disk, then transfers
this file to the remote station. Therefore, the WRITE
access is required.
13. 92/01/10 IUCV buffer list support does not work correctly in some
partial receive situations. See attached APAR VM40028.
12. 92/01/10 VM/IS users, when installing from the TCPMAINT user ID,
MUST know the MULT link passwords for the TCP/IP for VM
product minidisks. One reason you may not be installing
from TCPMAINT is if you are using INSTPKG, which runs
DIRECGEN. DIRECGEN updates your directory to reflect the
new TCP/IP for VM product minidisks. First, consult the
PROGPROD PARMLIST file to see if any minidisk entries for
TCP/IP have password parameters. If a minidisk has a
password parameter, note the MULT password. If a
minidisk does not have a password parameter, the default
MULT password as created by DIRECGEN is:
"M" concatenated with the first seven letters of the
minidisk user ID.
For example, the MULT password generated for the TCPMAINT
191 minidisk would be: MTCPMAIN
11. 92/01/10 VM/IS, users when installing from the TCPMAINT user ID,
MUST have link access to the TCPIP minidisks referenced
in the Installation & Maintenance manual.
10. 92/06/05 Customers who have both of the following products
installed -- Netview FTP V1 (568404801) and TCP/IP for VM
2.3.0 (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 a 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.
9. 92/01/10 During the initialization of the TCPIP server, the
following error message:
"Invalid link name in GATEWAY statement"
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 should be left blank.
8. 92/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:
MSGTCPPRS007E - Error encountered in reading the profile.
7. 92/01/10 Systems that use a BUS-TECH ELC2 control unit in 8232
emulation mode should upgrade the control unit microcode
to Version 2.3. If this microcode is not at the 2.3
level, the NETSTAT DEV command will show a status of
"Error" for the BTI control unit.
When this is the case, The ROUTED server will not
initialize the interface to the BTI controller, due to
the "Error" status.
6. 92/01/10 ITEM UPDATED 97/01/13
RSCS Version 3 Release 1 (V3 R1) includes new
configuration features, such as embedded files, new
configuration statements, such as LINKDEF, and allows
additional comment delimiters ('/*' and '*/') to be used.
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). However, SMTPRSCS cannot process RSCS V3 R1
embedded files, its new configuration definitions, or the
additional comment delimiters. In order to correctly run
SMTPRSCS you must:
1) create a separate file for use with SMTPRSCS, which is
based on the newer-format RSCS V3 R1 configuration
file. The new file should not include embedded files
or any new RSCS Release V3 R1 configuration statements
or comments.
-or-
2) continue to use the RSCS Version 2 configuration file
format with RSCS V3 R1. RSCS V3 R1 will configure
correctly using configuration files that conform to
the RSCS Version 2 format.
5. 92/01/10 Several client functions (such as FTP, Telnet, NETSTAT)
may require additional loader tables to be defined before
they can be used. If an attempt to execute a client
function terminates with a loader table overflow error,
additional loader tables need to be allocated prior to
executing the client. To avoid this, issue the following
command prior to invoking the program:
SET LDRTBLS nn
where "nn" is a suitable value. A value of 20 should be
sufficient in most cases, though a higher value may be
required for some machines.
4. 92/01/10 When using TCP/IP for VM with a CETI device, and TCPIP
is running in an ESA or XA mode machine, ABENDUNT001
errors may be encountered. This type of error will often
arise if the PDSM parameter was not specified with the
ASSORTEDPARMS statement in the PROFILE TCPIP
configuration file.
3. 92/01/10 Users running SMTP with TCP/IP for VM Version 1, could
change the default method of mail delivery performed by
SMTP, by modifying the TCP/IP-supplied SENDFILE exec.
This was done by modifying the call to SMTPCHEK (within
SENDFILE EXEC) to specify the order for which a host name
should be searched (i.e., RSCS before TCP), or to change
the default method of mail delivery for unknown host
names. A default of either TCP or RSCS could be
specified.
To accomplish this with TCP/IP for VM Version 2, you'll
need to make a local modification to the supplied SMTPRES
EXEC. To change the current mail delivery default (TCP)
to RSCS, modify lines 109 and 110 of the SMTPRES EXEC
from:
/* ------ Default to sending it to SMTP to handle----*/
return ruser rnode ctcp
to:
/* ------ Default to sending it to RSCS to handle----*/
return ruser rnode crscs
NOTE: If you change the default mail delivery mode prior
to running the Verification exec (V5735FAL EXEC), the
verification of SMTP is likely to fail.
This may occur because the Verification exec sends a
"test" file to "logon_id" at LOOPBACK, via SENDFILE. If
SMTPRES is modified such that the default delivery method
is RSCS, the "test" file will be sent to the RSCS host
'LOOPBACK', which will likely be construed as an invalid
host. This problem can be avoided by;
1) not changing the default delivery method until after
the verification process is Complete.
2) changing the the SENDFILE statement in the
Verification exec (at about line 312) to send the
file to your TCP/IP hostname instead of 'LOOPBACK'.
2. 92/01/10 The following restriction exists when running AIX/370
and TCP/IP for VM on the same machine. You cannot Telnet
from the AIX/370 console to the VM system. This is a
restriction caused by the console 3270 capability of
AIX/370. If a user Telnets into AIX/370 from the
network, the Telnet to VM will work.
1. 92/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.
12 95/12/14 PROBLEM: (PN76063) USING ' LPR (CC ' TO PRINT A FILE
RECEIVED WITH ' PIPE ', THE CHANNEL COMMAND
X'01'IN THE 1ST COLUMN IS
MODULES/MACROS: LPR VTCP220J
USERS AFFECTED: All users of LPR
RECOMMENDATION: INSTALL UN85411 ON VOLID 1000
11 95/11/14 PROBLEM: (PN76752) VM TCP/IP (XA) I/O ERROR WHEN TALKING TO
CLAW DEVICE
MODULES/MACROS: TCPIP TCPIPXA TCTOCLAW
VTCP220J
USERS AFFECTED: All users of CLAW device type on XA mode
TCPIP machines.
RECOMMENDATION: INSTALL UN84078 ON VOLID 1000
10 95/07/14 ITEM DELETED 95/09/27
9 95/05/24 PROBLEM: (PN71174) AMPX054I MESSAGE LPR FILETYPE LISTING
MODULES/MACROS: LPR VTCP220J
USERS AFFECTED: User's who have applied UN73700, UN73701,
or UN73702 for LPR.
RECOMMENDATION: INSTALL UN77245 ON VOLID 1000
8 95/05/24 PROBLEM: (PN71174) AMPX054I MESSAGE LPR FILETYPE LISTING
MODULES/MACROS: LPR VTCP220J
USERS AFFECTED: User's who have applied UN73700, UN73701,
or UN73702 for LPR.
RECOMMENDATION: INSTALL UN77287 ON VOLID 1000
7. 93/01/25 PROBLEM: (PN34230) FTP GET command fails with message
AMPX019I Fixed point divide by zero exception.
USERS AFFECTED: All FTP server virtual machines running
on CMS Release 9 (VM/ESA Release 2)
RECOMMENDATION: INSTALL UN35443 ON VOLID 9401
6. 92/12/23 PROBLEM: (PN31912) Superseded PTFs not handled by the
Service exec, S5735FAL.
USERS AFFECTED: All VM TCP/IP users
RECOMMENDATION: INSTALL UN33162 ON VOLID 9401
5. 92/11/26 PROBLEM: (PN28724) NETSTAT TELNET display truncates
'Logical Device Status' field
USERS AFFECTED: All users of NETSTAT TELNET command
RECOMMENDATION: INSTALL UN31624 ON VOLID 9401
4. 92/07/09 PROBLEM: (PN18900) FTP client hangs when doing a GET of
a file from AS/400 and the file exceeds the
AS/400'S limit of 16Meg bytes
USERS AFFECTED: All FTP users
RECOMMENDATION: INSTALL UN24094 ON VOLID 9401
3. 92/04/10 PROBLEM: (PN17716) Add CLAW (Common Link Access to
Workstation) support
USERS AFFECTED: All TCP/IP users
RECOMMENDATION: INSTALL UN19085 ON VOLID 9401
2. 92/03/25 PROBLEM: (PN16801) NOTE EXEC for SMTP sends all mail to
RSCS. none of the notes are being sent to SMTP
for delivery via TCPIP.
USERS AFFECTED: All SMTP users
RECOMMENDATION: INSTALL UN17773 ON VOLID 9401
1. 92/03/20 PROBLEM: (PN16954) Service exec does not support
multiple release IDs
USERS AFFECTED: All TCP/IP users
RECOMMENDATION: INSTALL UN17639 ON VOLID 9401
This section contains information that is dependent upon another
product other than this subset ID.
3. 95/05/08 INTERDEPENDENT PRODUCT: All Users of the TCP/IP Offload
Feature
PROBLEM: (PN67615) Offload application on 3172 hangs with
no apparent error symptoms.
USERS AFFECTED: All Users of the TCP/IP Offload Feature
RECOMMENDATION: INSTALL UN74512 ON VOLID 1000
2. 92/01/10 INTERDEPENDENT PRODUCT: VM/SP CMS R5
NFS, NAMESERVER and REXECD service machines require SVC
204 support for execution. SVC 204 was added in CMS
5.6. VM APAR VM34760 is available to retrofit this SVC
to CMS Release 5. It's included on the 8903 and 8904
PUT levels for CMS.
1. 92/01/10 INTERDEPENDENT PROCUTD: All VM/XA SP Users
PROBLEM: (VM41357) Using TCPIP TELNET Under VM put level
9002 results in error message:
TELNET requires 327x type terminal.
USERS AFFECTED: All VM/XA SP users
RECOMMENDATION: INSTALL UM14713 ON VOLID 9004 (R120)
INSTALL UM14714 ON VOLID 9004 (R121)
* APARs Follow (If Any) *
PTF Include List
UN77245 UN77287 UN84078 UN85411
PTF Exclude List
PE APAR List
PN39515 PN67240 PN76063 PN89872
End of Upgrade TCPIP220
, Subset VM220
, as of 2019/08/08.
|