OA41284: ALLOW EE XCA GROUPS TO BE DEFINED AND ACTIVATED WITH LARGE NUMBERS OF LINES.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Activating EE XCA groups with a large number of lines results
  in storage shortages.
  

Local fix

• For nonCN groups, break the large GROUP definition into
  smaller GROUP definitions.
  To define a CN GROUP with 1000s of autogenned lines, apply
  the PTF for this APAR first.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All using Enterprise Extender connections.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: EE GROUP defined with large             *
  *                      numbers of autogenned lines             *
  *                      fails during activation.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Sample configuration:
  
  GPIP     GROUP DIAL=YES,ANSWER=ON,ISTATUS=INACTIVE,CALL=INOUT,
                 AUTOGEN=(10000,L,P),DYNPU=YES,VNNAME=IP.VRN1
  
  1) An EE GROUP was defined with an extremely large number of
     autogenned lines.
  2) The operator issued a V NET,ACT,ID=GPIP,ALL to activate all
     the lines defined under this group.
  3) Currently, VTAM initiates ACTLINK processing for all 10,000
     lines simultaneously.
  4) During ACTLINK processing at the line level, each line
     eventually goes into a WAIT state until the PORT performs
     some activation flows.
  5) This wait state causes an 8K CRA buffer to be suspended.
     This suspended PAB also allows another AUNCB (line) PU PAB
     to dispatch.
  6) The next AUNCB PU PAB does the same processing and goes into
     a WAIT state.
  7) This process repeats until the PORT dispatches and resumes
     the suspended AUNCB PU PABs.  If 1000s of lines are activated
     at once, ECSA could become exhausted due to CRA8K buffer
     requirements for this type of processing.  Depending on
     system ECSA availability, this may or may not be an issue on
     your system.
  
  NOTE: When larger number of EE nonCN lines are required, you can
        define multiple GROUPS each defining the same IPADDR.
        Each GROUP can be separately activated to "pace" the
        activation flows during startup.
  
        When defining a connection network (CN) GROUP, then all
        the lines must be defined under a single GROUP with the
        same IPADDR specified.  This APAR may be beneficial to
        you if you define more than 3000 lines in a single
        EE GROUP.
  

Problem conclusion

• This APAR will add "pacing" logic to the activation flows
  to allow an EE GROUP defined with 3000 or more autogenned lines
  to activate more efficiently.  The intent of this new algorithm
  is to reduce the overall ECSA requirements currently required
  to activate a large EE GROUP definition.
  

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:

  UA68410

Modules/Macros

• ISTACCGP ISTACCG1 ISTACCSB ISTAUCAL ISTAUCDL
  ISTAUCFT ISTAUCIS ISTAUCLA ISTAUCLF ISTAUCPF ISTAUCVR ISTAUNCB
  ISTAUVT  ISTDECK1 ISTIPNCB ISTNCSPL ISTRLN
  

Fix information

• Fixed component name

  VTAM V4 MVS/ESA

• Fixed component ID

  569511701

Applicable component levels

• R1D0 PSY UA68410

     UP13/06/10 P F306

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.