II11401: OS/390 ENETWORK COMMUNICATION SERVER V2R6: IP PLANNING AND MIGRATION (SC31-8512-01) TCPIPINFO BOOKAPAR

APAR status

• Closed as canceled.

Error description

• OS/390 ENETWORK COMMUNICATION SERVER V2R6: IP PLANNING AND
  MIGRATION (SC31-8512-01) INFO APAR
  

Local fix

• Please check all Informational APARs and our Web site regarding
  the Enterprise Extender function before implementing it in your
  network.
  The other publications affected by Enterprise Extender
  functions are:
  * SNA Implementation Guide
  * SNA Resource Definition Reference
  * SNA Operation
  * SNA Operation Quick Reference
  * SNA Diagnosis
  * SNA Messages
  * SNA Planning and Migration
  
  The IP Planning and Migration Guide for Release 6
  (FIAF9001.BOO) is part of the September, 1998, OS/390
  Collection Kit and is correctly referenced from the OS/390
  V2R6 eNetwork Communications Server bookshelf
  (FIZ0BK02.BKS). However, a downlevel edition of the
  Migration Guide (FIAF9000.BOO) is incorrectly referenced
  from the OS/390 V2R6 Planning and Installation bookshelf
  (E0ZIIN30.BKS). The Planning and Installation bookshelf
  should reference FIAF9001.BOO, not FIAF9000.BOO.
  
  On pages 29, 46, 114, and 239, add the following
  new section:
  TCP/IP AND VTAM CONSIDERATIONS
  TCP/IP shares its Data Link Controls (DLCs) with VTAM. For
  this reason, if you restart VTAM, you must also restart
  TCP/IP.
  
  On pages 36, 87, 160, 251, in the sections, "OS/390 UNIX
  sendmail and OS/390 UNIX Popper," add the following
  information:
  When a started procedure is used to start sendmail, the user
  must be a Superuser (UID(0)) or permitted to BPX.SUPERUSER
  facility authority. Popper is managed by
  the Inetd Generic Listener Program, and the UID associated
  with it needs to have a UID(0) specified in the inetd.conf
  file in the /etc directory.
  
  On pages 51 and 119, in the sections, "Other User IDs
  Requiring OS/390 UNIX Superuser Authority," replace
  the ROUTED, FTPD paragraph with the following:
  FTPD, DNS, sendmail
  When a started procedure is used to start FTPD,
  DNS, or sendmail, the user must be a Superuser (UID(0))
  or permitted to BPX.SUPERUSER facility authority.
  
  On pages 51 and 119, in the sections, "Other User IDs
  Requiring OS/390 UNIX Superuser Authority,"
  replace the OS/390 UNIX REXECD, RSHD, Telnet server
  (TELNETD) with the following:
  OS/390 UNIX REXECD, RSHD, TELNETD, popper
  These daemons are managed by the Inetd Generic Listener
  program, and the user specified in the inetd.conf file
  in the /etc directory must have a UID(0) associated
  with it. For details on inetd, refer OS/390 UNIX
  System Services Planning. For details on individual
  daemons, refer to the OS/390 eNetwork Communications
  Server: IP Configuration Guide.
  
  On page 236, in the section "Migrating from the DB2-
  Based Name Server," add the following information:
  When a started procedure is used to start the DNS
  server, the UID associated with the started procedure
  needs to have Superuser authority (UID(0) in its
  OMVS segment).
  
  On page 36, Chapter 4, "Migrating from CS for OS/390 Version 2
  Release 5," in the section, "OS/390 UNIX sendmail and
  OS/390 UNIX Popper," add the following information:
  For helpful tips on configuring sendmail and popper,
  point your Web browser to http://www.s390.ibm.com/unix/
  apps/sendm.html.
  Add the same information to the sections on sendmail and
  popper in Chapter 5, "Migrating from TCP/IP Version 3
  Release 2"; Chapter 6, "Migrating from TCP/IP Version 3
  Release 1"; and Chapter 11, "Migrating from the OpenEdition
  Feature or from the OpenEdition MVS Applications Feature."
  
  On page 125, Chapter 6, "Migrating from TCP/IP Version 3
  Release 1, in the section, "VMCF Considerations,"
  add the following sentence:
  The TCP/IP resource manager, MVPTTRML, will be added
  dynamically to the system.
  
  On page 223, Chapter 8, "Migrating the Telnet Server and
  Clients," at the beginning of the section, "Changes to
  SMF Record Processing," add the following paragraph:
  In CS for OS/390, SMF user exits are no longer supported.
  See "SMF Exits" on page 110.
  
  On page 283, Appendix A, "Migrating from TCP/IP Version 2
  Release 2.1 to TCP/IP Version 3 Release 1," in the table
  "Changed FTP SITE and LOCSITE Subcommands," enter the
  following information for the UNIT parameter:
  You can specify tape for the FTP server.  You cannot specify
  tape for the FTP client.
  CHAPTER 5, "Migrating from TCP/IP Version 3 Release 2" and
  CHAPTER 6, "Migrating from TCP/IP Version 3 Release 1":
  There has been some confusion around the issue of what level
  of IUCV support is still available in OS/390 V2R6.  The
  following paragraphs should help clarify this issue.
  The IUCV support in TCP/IP Version 3 Release 2 and earlier
  versions consisted of two main sets of services:
    1. "IUCV socket API" services
    2. IUCV/VMCF inter-address space communication services
  
   "IUCV socket API" services
   --------------------------
  
  Beginning with OS/390 Version 2 Release 5, the "IUCV socket
  API" is no longer supported.  The "IUCV socket API" is a subset
  of the IUCV inter-address space communication API. The "IUCV
  socket API" allowed applications to request socket services
  from the TCP/IP protocol stack using the IUCV inter-address
  space communications.
  
  Applications that use this API must be evaluated to determine
  what design and/or code changes are required in order to use
  one of the supported socket interfaces in OS/390 V2R6 and later
  releases.
  Most applications utilizing the "IUCV socket API" tend to be
  written in Assembler. As a result, the most suitable socket API
  choices for these types of applications will probably be one of
  the following:
  
        - The TCP/IP Macro Socket API (EZASMI)
        - OpenEdition Assembler Callable Services API
  
  Note that the only applications that are affected by this
  change are applications that made direct use of the "IUCV
  socket API."
  
   IUCV/VMCF inter-address space communication services
   ----------------------------------------------------
  
  The IUCV/VMCF inter-address space communication API enables
  applications running in the same MVS image to communicate with
  each other without requiring the services of the TCP/IP
  protocol stack.  The VMCF/TNF subsystems provide these services
  which are still available in OS/390 V2R6. Several components
  of TCP/IP in OS/390 V2R6 continue to make some use of these
  services for the purpose of inter-addess space communications.
  These include:
  
  - The "AF_IUCV" domain sockets for the TCP/IP "C" socket
    interface.
  The "AF_IUCV" domain allows applications executing in the same
  OS/390 image and using the TCP/IP "C" socket interface to
  communicate with each other via a socket API but without
  requiring the services of the TCP/IP protocol stack as no
  network flows result in these communications.  This is quite
  different from the more common "AF_INET" domain that allows
  for socket communication over a TCP/IP network. "AF_IUCV"
  sockets continue to be supported in OS/390 V2R6.
  
  An example of a TCP/IP-provided application that exploits
  "AF_IUCV" sockets is the SNMP Query Engine component
  (SQESERVE).
  
  The OpenEdition socket library provides a similar
  functionality to the "AF_IUCV" domain sockets with its
  "AF_UNIX" domain. Users creating new applications should
  consider using "AF_UNIX" domain sockets.
  
  - The PASCAL socket interface also makes use of the IUCV/VMCF
  services for a limited set of inter-address space communication
  flows.
  
  As a result, any applications (provided by IBM or others) that
  use the PASCAL socket API also still have a requirement for the
  VMCF/TNF subsystems. TCP/IP provides several applications and
  commands that exploit these interfaces such as the SMTP, LPD,
  DNS (non-Bind based) servers and the TELNET, PING, TRACERTE,
  HOMETEST, TESTSITE and LPR commands.
  
  Therefore, in OS/390 V2R6 you must continue to configure and
  start the VMCF and TNF subsystems as you did in TCP/IP Version
  3 Release 2. However, since the VMCF/TNF subsystems are no
  longer used to directly communicate with the TCP/IP protocol
  stack in OS/390 V2R6, the amount of CPU they will consume will
  be significantly lower than in TCP/IP V3R2 and V3R1
  environments.
  
  
  CHAPTER 5 "MIGRATING FROM TCP/IP VERSION 3 RELEASE 2"
    Section "Changes to User-Written Applications"
  CHAPTER 6 "MIGRATING FROM TCP/IP VERSION 3 RELEASE 1"
    Section "Changes to User-Written Applications"
  If an application codes the LISTEN socket and the BACKLOG
  parameter is specified as 0 (zero), clients will not be able
  to connect to the server, and TCP/IP ignores any connection
  request for that listener or server. For this reason, the
  value that you specify for the BACKLOG parameter must be a
  number greater than 0.
  
  CHAPTER 5 "MIGRATING FROM TCP/IP VERSION 3 RELEASE 2"
    Section "Mounting the CS for OS/390 HFS"
  CHAPTER 6 "MIGRATING FROM TCP/IP VERSION 3 RELEASE 1"
    Section "Mounting the CS for OS/390 HFS"
  Change the title of this section to "CS for OS/390 HFS."
  Delete the first paragraph and add the following
  information:
  The CS for OS/390 HFS files are contained in the OS/390
  V2R6 HFS. There is not a separate mountpoint for CS for
  OS/390 HFS files.
  
  CHAPTER 6 "MIGRATING FROM TCP/IP VERSION 3 RELEASE 1"
    Section "Changes to User-Written Applications"
  If you are migrating APITYPE=3 socket applications that were
  compiled using the EZASMI macro from TCP/IP Version 3
  Release 1, be sure that PN79652 was applied to the 3.1
  system from which you are migrating, and that the applications
  were corrected to work in accordance with the changes
  documented in that APAR. That APAR introduced important
  changes in the way APITYPE=3 programs work.
  CHAPTER 5 "MIGRATING FROM TCP/IP VERSION 3 RELEASE 2"
   Section: "CS for OS/390 HFS Parts"
  CHAPTER 6 "MIGRATING FROM TCP/IP VERSION 3 RELEASE 1"
   Section: "CS for OS/390 HFS Parts"
  In the tables in these sections, the parts listed as
  residing in /usr/bin/xxx are actually in /bin/xxx.
  For example, the FTP client is in /bin/ftp, not
  /usr/bin/ftp.
  
  In the section:
   Enhancements to Telenet Server Functions Requiring
   implementation Reassessment
  sub-section: Changes to USSMSG Support
  
  The following information is added:
  
  If a user supplied USS table is to be used, it must be
  specified in a library pointed to by the //STEPLIB
  in the TCPIP startup procedure.
  _________________________________________________________
  In the section:
   Changes to CICS Sockets
  the following information is added:
  
  CICS Interface and Listener requires new configuration dataset
  and new transactions.
  EZAO transaction is used instead of CSKE and CSKD to start
  and stop the CICS Interface and Listener.
  _________________________________________________________
  In the sections with:
   Common OS/390 Configuration Problems
  the following information is added:
  
   EZZ4203I OPENEDITION-TCP/IP CONNECTION ERROR FOR
   TCPIP-BPX1SOC,00000003,FFFFFFFF,00000070,112B00B6
  
   These messages usually indicate that both INET and
   CINET FILESYSTYPE have been specified.  Only one should be
   specified; refer to the FILESYSTYPE section in the Unix
   Systems Services Planning Manual for additional information.
  _________________________________________________________
  
  In the section:
  Changes to TCPCONFIG Statement
  
  the discussion about TCPMAXRCVBUFRSIZE now includes the
  following information:
   If you are running FTP, you must code TCPMAXRCVBUFRSIZE
   to be 180K or more.
  *************************************************************
  In Chapter 5, "Migrating from TCP/IP Version 3 Release 2",
  in the section called "Changes to User-Written Applications"
  in the subsection called "Changes to CICS Sockets"
  another bullet is added after the following paragraph:
    A replacement for the CICS interface for TCP/IP Version 3
    Release 2 (Enhanced CICS Sockets Features)was released in
    June, 1997. This feature is now part of CS for OS/390 and
    provides the following enhancements:
  
  The new bullet says:
  
  Module EZACIC12 is new. It performs WLM registration and
  deregistration. In order to ensure that the CICS CSD contains
  all necessary sockets-related resource definitions, a CSD
  upgrade (DFHCSDUP) using member EZACICCT or EZACICPT in
  hlq.SEZAINST should be executed.  Refer to CICS Resource
  Definition Guide for information on DFHCSDUP.
  

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels