IBM Support

PI23099: REPEATED CONNECTING / DISCONNECTING SUBSEQUENTLY ISSUE CSQE222E SMDS CFSTRUCT DYNAMIC ALLOCATION FAILED RC 4, RS 04100000

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Joblog shows repeated connections/disconnections occurring to
    structure LARGE prior to the allocation failure.
    Each time the structure is connected, CSQE241I is issued to
    report SMDS has STATUS(ACTIVE) for the structure, and on each
    disconnect it is issued to report SMDS has STATUS(EMPTY):
    CSQE005I !CSQ1 CSQECONN Structure LARGE connected as
    CSQEMQGPCSQL06, version=CCD78C1FD02BAA83 000633B3
    CSQE241I !CSQ1 CSQEDSG2 SMDS(CSQL) CFSTRUCT(LARGE)
    now has STATUS(ACTIVE)
    CSQE241I !CSQ1 CSQEDSG2 SMDS(CSQL) CFSTRUCT(LARGE)
    now has STATUS(EMPTY)
    IXL016I CONNECTOR CSQEMQGPCSQL06 TO STRUCTURE MQGPLARGE
    DISCONNECTING JOB CSQ1MSTR ASID 03B6 REQUESTED DISCONNECT
    REASON=NORMAL.
    CSQE006I !CSQ1 CSQECLOS Structure LARGE connection
    name CSQEMQGPCSQL06 disconnected
    
    However, on the last disconnect before the error there is no
    CSQE241I for STATUS(EMPTY), which suggests the code for
    disconnecting the SMDS datasets is not being executed.
    
    Looking at the CSQE006I messages reporting the structure
    disconnection, I can see that it is normally being issued by
    CSQECLOS, however the final disconnection is issued by
    CSQEOPEN. This suggests an error was detected during open
    processing, but after it had already established a connection
    to the structure.
    
    Looking at the codepath where CSQEOPEN disconnects from the
    structure I can see that it does not make the expected calls
    to disconnect the SMDS datasets, which would explain both the
    lack of CSQE242I message with STATUS(EMPTY) and the
    subsequent allocation failure due to the datasets still being
    in use.
    
     This APAR is raised so CSQEOPEN can be corrected to
    disconnect the SMDS datasets in this situation.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the queue manager connects to a CF *
    *                      structure using SMDS, it fails and      *
    *                      message "IKJ56246I DATA SET DSN NOT     *
    *                      ALLOCATED, FILE IN USE".                *
    *                      Messages CSQE222E, CSQE246I and         *
    *                      CSQE247I are also issued, and the SMDS  *
    *                      dataset is set into STATUS(ALLOCFAIL)   *
    *                      and AVAIL(ERROR).                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During a CSQEOPEN call for a structure, CSQECONN is called to
    connect to the structure. CSQECONN connects to the structure and
    the associated SMDS dataset. CSQEOPEN then encounters an error,
    and disconnects from the structure but not from the SMDS
    dataset, thus leaving the queue manager connected.
    When CSQEOPEN is called again for another connection request,
    it fails to dynamically allocate the SMDS dataset, as it finds
    it is already in use.
    
    Keywords:
    MQSMDS/K
    

Problem conclusion

  • The code in CSQEOPEN was changed to disconnect from the SMDS
    dataset if it disconnects from the CF structure.
    100Y
    CSQEOPEN
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI23099

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-31

  • Closed date

    2014-09-16

  • Last modified date

    2014-11-04

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

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

    UI21364

Modules/Macros

  • CSQEOPEN
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI21364

       UP14/10/02 P F410

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":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 November 2014