II11663: NCP LUDRPOOL NUMILU AND NUMTYP2 HOW TO CODE FOR DLUR LUS

APAR status

• Closed as canceled.

Error description

• VTAMINFO TPINFO 569511701 R301 R401 R411 R501
  This information apar was created to provide information on
  coding the NCP parameters LUDRPOOL, NUMILU, and NUMTYP2 for
  DLUR LUs.
  
  Sites using a local NCP for network access need to adjust the
  LUDRPOOL definition as they add additional dependent LUs to
  their remote CP.  The proper value to adjust is NUMILU.  The
  following provides increasing levels of detail on how to code
  the proper values for the LUDRPOOL NUMILU and NUMTYP2 values,
  along with  AUXADDR and ADDSESS values.  The PUDRPOOL is also
  discussed.
  
  What to code for each resource
  
  First is a summary for those who just want to know what to code
  for each network resource.
  
  For each adjacent CP to which VTAM will establish CP-CP
  sessions, add one to NUMILU (If the CP is not defined in the NCP
  as an LU with LOCADDR=0) and one to AUXADDR.
  
  For each DLUR node
  
  If CP-CP sessions will also be established add one to AUXADDR
  and one to ADDSESS.
  
  If CP-CP sessions will not be established add one to NUMILU (If
  the CP is not defined in the NCP as an LU with LOCADDR=0) add
  one to AUXADDR.
  
  For each DLUR served LU which will have an LU-LU session, add
  one to NUMILU.
  
  For each Independent LU, add one to NUMILU for the first session
  (if the LU is not already defined in the NCP with LOCADDR=0).
  Add one one to AUXADDR for each additional session where this
  ILU is a PLU.  Add one to ADDSESS for each additional session
  where the ILU is secondary.  Note,  if the first session is
  established with the LU as primary then you need to add one to
  AUXADDR to allocate an address for the LU if it will be the
  secondary LU for any sessions.
  
  PUs which are supported by DLUR do not use a PUDRPOOL value.
  
  
  Detailed listing of the use of each keyword
  
  Following is a list of sessions which use a NUMILU value (Note,
  defining the CP in the NCP as an LU with LOCADDR=0 will
  preallocate the necessary control blocks corresponding to one
  NUMILU value) :
  
     The CP-CP session between VTAM and the remote CP, where the
     CP is the Primary end of the session.
     The VTAM Conloser DLUS-DLUR session, if VTAM does not have
     CP-CP sessions with the DLUR.  If VTAM does have CP-CP
     sessions with the DLUR then this session will use an AUXADDR
     value.
     A DLUR owned LU, only when it is in session.  Note, many
     customer sites have defined additional LUs which do not
     really exist, or that do exist, but do not actually get in
     session.  The important number is how many LUs will
     establish LU-LU sessions.
     An Independent LU connected to NCP boundary function, which
     does not have an LU statement in the NCP with LOCADDR=0.
  
  
  Following is a list of sessions which use an AUXADDR value:
  
     The CP-CP session between VTAM and the remote CP, where VTAM
     is the Primary.
     The VTAM Conloser DLUS-DLUR session, if VTAM does have CP-CP
     sessions with the DLUR.  If VTAM does not have CP-CP sessions
     with the DLUR then this session will use a NUMILU value.
     Each additional session established by an Independent LU
     where the ILU is the primary LU.
     The first session established by an ILU where the ILU is the
     secondary LU, if the ILU already has sessions where it is the
     primary LU.  Additional sessions where the ILU is the
     secondary only need an ADDSESS value.
  
  
  Following is a list of sessions which use an ADDSESS value:
  
     The VTAM Conwinner DLUS-DLUR session.
     Each additional session established by an Independent LU
     where the ILU is the secondary LU.
  
  
  Following is a list of sessions which use a NUMTYP2  value:
  
     Dependent LUs which are supported by the NCP boundary
     function and are not defined in the NCP, such as Token Ring
     connected devices.  NCP does not provide boundary support for
     DLUR served LUs, so they are not part of this value.
  
  
  Following is a list of sessions which use a PUDRPOOL  value:
  
     PUs added to NCP over and above those which were defined.
     NCP does not provide boundary support for DLUR served PUs,
     so they are not part of this value.
  
  
  Technical background
  
  For those interested, the following provides the technical
  background for the above recommendation.
  
  Control blocks
  LUB - This control block is used to represent an LU.  There is
  one common LUB pool for all LU types.
  LNB - This control block represents an LU network address.
  LND - This control block represents a Dependent LU.  It actually
  consists of an LNB, an SSCP-LU BSB, an LU-LU BSB, and a BXI.
  BSB - This control block is used to represent a session.
  BXI - This is another session control block.
  LTX - This is a session control block for NUMTYP1 LU's.
  
  Keyword   Control bolcks allocated
  NUMILU    LUB, LNB, ILU BSB, BXI
  NUMTYP1   LUB, LND (which is actually an LNB, an SSCP-LU BSB, an
  LU-LU BSB, a BXI, and an LTX)
  NUMTYP2   LUB, LND (which is actually an LNB, an SSCP-LU BSB, an
  LU-LU BSB, and a BXI)
  ADDSESS   ILU BSB, BXI
  AUXADDR   LNB, ILU BSB, BXI
  
  Sense codes related to shortages in these pools
  
  NCP will issue sense code 08821nnn for shortages related to the
  control block pools allocated for the above keywords.  Following
  is a table showing the pool represented by the nnn value.  The
  keyword(s) which resulted in the problem are included.
  
  Sense code     Control Block Pool             Keyword
    08821001     BSB Boundary Session Block   NUMILU, ADDSESS,
                 (for ILU)                    AUXADDR
    08821002     CUB PU DR Pool               PUDRPOOL
    08821005     LNB LU Node Block (for ILU)  NUMILU, AUXADDR
    08821006     LND LU Node Block (for DLU)  NUMTYP1, NUMTYP2
    08821007     LTX pool (for DLU)           NUMTYP1
    08821008     LUB pool (LU DR pool)        NUMILU, NUMTYP1,
                                              NUMTYP2
    08821020     BXI pool (for DLU)           NUMTYP1, NUMTYP2
    08821021     BXI pool (for ILU)           NUMILU, ADDSESS,
                                              AUXADDR
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

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

  II11656

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

Fix information

Applicable component levels