OA40579: DO NOT ALLOW ACTIVATION OF LINES UNDER MULTIPLE XCA EE NON-CONNECTION NETWORK GROUPS WHEN DYNPU VALUES CONFLICT.

APAR status

• Closed as fixed if next.

Error description

• Results are unpredictable when multiple XCA non-CN EE GROUP
  statements are coded with conflicting DYNPU values.
  To correct this ambiguity, VTAM will fail all lines being
  activated for a non-CN group when a previous group has been
  activated with a different value for DYNPU.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All using Enterprise Extender connections.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: EE dial-in attempt fails with           *
  *                      PU GEN NOT SUPPORTED error.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem is summarized as follows:
  
  Sample EE XCA major node:
  
  VBUILD TYPE=XCA
  EEPORT   PORT  MEDIUM=HPRIP,SAPADDR=4,
                 CAPACITY=1000M
  EEGROUP1 GROUP DIAL=YES,DYNPU=YES,
                 CALL=INOUT,AUTOGEN=(25,ELN,EPU),ISTATUS=ACTIVE
  EEGROUP2 GROUP DIAL=YES,DYNPU=NO,
                 CALL=INOUT,AUTOGEN=(25,XLN,XPU),ISTATUS=ACTIVE
  
  1) Enterprise Extender was activated with the sample EE XCA
     major node.
  2) EEGROUP1 and EEGROUP2 are both associated with the same
     local static VIPA address.
  3) After being activated, there are 50 lines available for both
     dial-in and dial-out requests.
  4) In this configuration, switched PUs were defined with PATH
     statements that directed VTAM to use lines from EEGROUP2
     when dial-out connections were attempted.
  5) It was assumed that VTAM would use lines from EEGROUP1
     when dial-in connections were attempted.  EEGROUP1 supports
     the generation of dynamic PUs when switched PUs are not
     defined.
  6) At some point, a remote EE partner attempted a dial-in
     request.  It failed with the following messages:
  
     IST680I CONNECTION REQUEST DENIED - ID = cpname
             INVALID NETWORK NAME
     IST1394I CPNAME = netid.cpname      STATION ID = xxxxxxxxxxxx
     IST081I LINE NAME = line, LINE GROUP = group, MAJNOD = majnod
     IST314I END
  
  7) In this case a line from EEGROUP2 was requested which did NOT
     support dynamic PU generation.  This resulted in the
     connection request being rejected.
  
  When non-connection network groups (VNNAME not coded) are
  activated, VTAM queues all lines on a dial-in queue associated
  with the local static VIPA.  VTAM simply pulls the next
  available line from the queue when inbound dial-in requests
  are attempted.  If dynamic PUs are required, DYNPU=YES
  must be coded on all EE groups which are eligible for
  dial-in requests.
  
  When more than one non-connection-network Enterprise Extender
  call-in capable group is defined for a given static VIPA
  (IPADDR), the DYNPU value specified on each of these groups must
  be consistent.  The first line activated from one of these
  groups sets the DYNPU value for non-connection-network dial-in
  operations.  Any subsequent line activation associated with a
  group for the same static VIPA, which has a conflicting DYNPU
  value, will fail activation with sense code x'08490000'.
  

Problem conclusion

Temporary fix

Comments

• This APAR is being closed FIN (Fixed If Next) with concurrence
  from the submitting customer. This means that a fix to this
  APAR is expected be delivered from IBM in a release(if any)
  to be available within the next 36 months.
  
  The change(s) will be included in
  z/OS Communications Server V2R1:
  

APAR Information

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

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

Modules/Macros

• ISTAUCAL ISTAURC  ISTIPNCB
  

Fix information

• Fixed component name

  VTAM V4 MVS/ESA

• Fixed component ID

  569511701

Applicable component levels

• R1D0 PSY

     UP