IBM Support

PI82953: ABEND0C4 0C4-00000010 RLMC PEER CSQJPBE1 CSQJL002 CSQJDS01

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABN=0C4-00000010,U=SYSOPR,C=yyyyy.900.RLMC-PEER
    EST,M=CSQJPBE1, LOC=CSQJL002.CSQJDS01+0000xxxxK
    The 0C4 in CSQJDS01 occurs when a queue-manager detects that a
    peer's active log datasets have been defined with SHAREOPTIONS
    less than (2 3), as indicated by message CSQJ250I. An MMSRV
    DISCONNECT is issued by CSQJDS02 after the CSQJ250I message, but
    subsequent processing in CSQJPB01 tries to issue another MMSRV
    DISCONNECT which fails (and results in a S0B0 RC24 dump), and
    then there is an attempt to report the failure via message
    CSQJ104E. However, there is a problem with the parameters
    passed to CSQJDS1B for issuing the message (R7 does not contain
    the address of an LRB4) which results in an 0C4.
    

Local fix

  • Ensure all active log datasets for queue-managers in a
    queue-sharing group are defined with SHAREOPTIONS(2,3).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: In a queue-sharing group, an attempt to *
    *                      read a peer's log dataset created with  *
    *                      incorrect SHAREOPTIONS can generate     *
    *                      abend 0C4 in CSQJDS01 and abends S0B0   *
    *                      or S978 in Media Manager Services.      *
    ****************************************************************
    In a queue-sharing group, if a queue-manager is unable to read a
    peer's log dataset due to incorrect SHAREOPTIONS, then message
    CSQJ250I is issued. However, subsequent processing by CSQJPB01
    incorrectly issues a Media Manager DISCONNECT although a
    DISCONNECT has already been issued, resulting in abend S0B0 RC24
    issued by ICYMMSRV or S978 RC4. There is an attempt to report
    the failing DISCONNECT via message CSQJ104E but there is an
    error in the parameters passed to CSQJDS1B, resulting in an 0C4
    abend in CSQJDS01.
    

Problem conclusion

  • CSQJPB01 has been changed to pass the correct parameters to
    CSQJDS1B to issue message CSQJ104E.
    
    CSQJDS01 has been changed to indicate that LOG dataset has
    been disconnected preventing later disconnect attempts.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI82953

  • Reported component name

    MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-12

  • Closed date

    2017-06-20

  • Last modified date

    2017-09-02

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

    PI82248

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

    UI48171

Modules/Macros

  • CSQJDS02 CSQJPB01
    

Fix information

  • Fixed component name

    MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI48171

       UP17/08/10 P F708

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 September 2017