II08794: VTAM V4R3 NETWORK IMPLEMENTATION GUIDE DOCUMENTATION CHANGES

APAR status

• Closed as canceled.

Error description

• VTAMINFO TPINFO 569511701 R301
  This information apar was created to contain the changes to the
  VTAM 4.3 Network Implementation Guide SC31-6548-00.
  .
   In the 4.3 Network Implementation Guide page 127 under the
  title Generic Resource Requirements the following item should be
  added as one of the bullets. The OLU host of a session
  initiation to a generic resource must support Name Translation.
  For VTAM version 4 and above the TRANSLAT Start option must
  include USERVAR. For Version 3.4.2 and below RACALIAS must
  include USERVAR in ISTRACON.
     On page 125 under the title "Defining Your Network with
  USERVARs" but under the sub heading of "The following applies
  regardless whether you use USERVARS with XRF" add the following
  bullet. The OLU host of a session initiation as well as the host
  that is resolving the USERVAR name must support Name
  Translation. For VTAM version 4 and above the TRANSLAT Start
  option must include USERVAR. For VTAM Version 3.4.2 and below
  RACALIAS must include USERVAR in ISTRACON.
  .
  Chapter 4
  Page 309.  In the paragraph headed "Enabling Communication
  Controller Channels for Activation", ignore the sentences
  beginning with "For a communication controller..." to the
  end of the paragraph.
  Also, on page 309, in the second paragraph, the last sentence
  is erroneous, which begins "The channel-enable switches should
  be turned off only when a communication cotroller must be
  loaded...". This sentence applied only to a d/t3705 environment
  which is obsolete.
  On pages 347-8, under ISTVTCOS, the following explanation will
  be added:
  Note: Downstream PUs and their LUs will be assigned the same VR
  as their boundary node for their SSCP-PU and SSCP-LU sessions.
  For example, when an SSCP-PU session is being established for a
  physical unit off of an NCP, the VR that was chosen for the
  NCP's SSCP-PU session will also be used for the downstream's
  SSCP-PU session.
  .
  Page 526. Chapter 9 Tuning VTAM for your Environment. Table 41
       I/O Buffer Size and Buffers Per Page. Should have these
       table values updated to reflect the following corrections:
   ______________________________________________________________
  Number of Buffers  Range of Buffer Sizes  Range of Buffer Sizes
  Per Page           for MVS with 4K        for MVS using data
                     Paging                 encryption facility
                                            with 4K paging
  ______________________________________________________________
  1                  4000-1958              3998-1951
  ______________________________________________________________
  4                 933-726                 926-719
  ______________________________________________________________
  24                77 - 70                 70 - 64
  ______________________________________________________________
  25                69 - 64                 {blank}
  ______________________________________________________________
  26                {blank}                 {blank}
  Page 527. Chapter 9 Table 41 (Page 2 of 2) I/O buffer size and
       Number of Buffers per Page should be totally deleted since
       they are not valid in an MVS/ESA environment.
  

Local fix

• In Chapter 4, "Getting Started with VTAM - Detail", in
  the section on "Establishing and Controlling SNA Ses-
  sions", in the subsection on "Automatic Logons", in the
  subsection on "Reallocation of Autologon Sessions", in
  the subsection "Conditions for Reallocation", change
  the third bullet to the following:
  When an active session between a secondary logical unit
  and its controlling application program terminates, the
  VTAM that owns the secondary logical unit decides whether
  to reallocate the controlling session based on the type
  of termination request or UNBIND that is received.  The
  controlling session is not reallocated if the termination
  request or UNBIND type indicate normal termination.  If
  the session was terminated using the VARY TERM command
  with either TYPE=UNCOND or TYPE=FORCE, the controlling
  session is reallocated if a session path exists at that
  time between the two logical units.  To avoid redriving
  the session, issue VARY TERM TYPE=COND instead.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is being closed CAN to make it visible.
  

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