IBM Support

PQ51208: EZZ6649I NOT ABLE TO CREATE GROUP XXXX

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DNS issuing message EZZ6649I message indicating a group
    can not be created or connections only being routed to one
    system when multiple systems are registered.  DNS will not
    create th group or route the work because not all the IP
    addresses for the TCPIP stacks are registered with WLM.
    The IP address was deregistered when the device for the IP
    address was stopped.  However, when the device was
    restarted, the IP address is not registered again.  The WLM
    registration is called from routine Send_LinkTrap.  This
    routine is not being called when the device activates
    because the DIFSAP_RetryCount is non-zero.  This prevents a
    SNMP Linkup trap being sent and WLM from being updated with
    the active IP addresses.  The DIFSAP_RetryCount is non-zero
    because we have entered recovery code, due to a CM_CLEAR_IND
    being returned from the device.
    .
    VERIFICATION STEPS:
    1) A dns -d 11 trace will show message no intersect when
       trying to process a group.  The list of IP addresses from
       TCPIP will also lose an IP address when the device is
       restarted.
    2) A Ctrace with options IOCTL,VTAM, CLAW will show a call
       to WLM Registration when the device stops.  However,
       there will not be another call to WLM Registration
       when the device starts again.  When the device starts,
       ctrace record Device Initialization Complete will be
       written.  The DIF prior to that will show a non-zero
       value at offset 112, the DIFSAP_RetryCount.
    .
    Additional Symptoms
    SNMP traps not being sent for device activation
    DNS/WLM balancing not occurring
    .
    KEYWORDS:
    DNS CLAW device wlm tcpip
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release 2 IP:             *
    *                 CLAW and WLM                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Following a device failure a CLAW       *
    *                      device may not be re-registered with    *
    *                      WLM after successful connection         *
    *                      recovery.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    While executing CM_CLEAR_IND connection recovery logic for a
    CLAW device, EZBIFIRE, an automatic recovery timer, initiated an
    additional recovery attempt. The additional recovery processing
    resulted in a failure to invoke WLM registration logic which
    also performs a DNS update. A named message:EZZ6649E named: WLM
    group not created indicated a problem with a member of that
    particular group. All connections were routed to a single
    system.
    +-------------------------------------------------------------+
    + Please check our Communications Server for OS/390 homepages +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

  • EZBIFIRE's device connection recovery logic is amended to
    correctly invoke the WLM registration operation after
    successful connection versus SAP recovery processing.
    
    * Cross Reference between External and Internal Names
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ51208

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    120

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2001-08-06

  • Closed date

    2001-08-10

  • Last modified date

    2001-10-02

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

    PQ49263

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

    UQ56868

Modules/Macros

  • EZBIFIUT
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R120 PSY UQ56868

       UP01/09/17 P F109

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"120","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"120","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 October 2001