IBM Support

PH61423: MQ Z/OS: IF CSQUDLQH RUNS IN OMVS, A TRACE FILE IS ALWAYS PRODUCED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you run the Dead Letter Queue (DLQ) handler program
    CSQUDLQH in OMVS, a trace file named DD:CSQUDBG is always
    produced in the current OMVS directory, for example the home
    directory. If the utility runs for an extended time,
    the file will grow large.
    
    To run the utility this way, the following commands were used:
    
      export STEPLIB=xxx.SCSQANLE:xxx.SCSQAUTH:xxx.SCSQLOAD
    
        where xxx is the MQ HLQ
    
      touch CSQUDLQH
    
      chmod 755 CSQUDLQH
    
      chmod +t CSQUDLQH
    
      echo "INPUTQM(yyyy) INPUTQ(dlqname) WAIT(30)
      RETRYINT(3)\nREASON(MQRC_Q_FULL) ACTION(RETRY)
      RETRY(2) CONVERT(NO)" | CSQUDLQH
    
        where yyyy is the QMGR.  These last 3 lines are all part
        of one command.  It had to be split due to space
        limitations in the APAR text.
    

Local fix

  • Run the utility in batch
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 3 Modification 0 and                 *
    *                 Release 4 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When running the Dead Letter Queue      *
    *                      (DLQ) handler utility in USS, a trace   *
    *                      file named 'DD:CSQUDBG' is always       *
    *                      created and traced to even without the  *
    *                      required debug DD statement specified.  *
    ****************************************************************
    The code which handles the Dead Letter Queue (DLQ) handler
    utility trace option doesn't explicitly check for the debug DD
    statement when the utility is run in USS. This results in the
    trace file 'DD:CSQUDBG' always being created and traced to when
    the utility is run in USS.
    

Problem conclusion

  • The code has been changed to explicitly check for the debug
    DD statement when the Dead Letter Queue (DLQ) handler utility is
    run in USS to prevent the trace file always being created and
    traced to. An environment variable has also been added to
    provide the option to enable trace under IBM support direction
    when the utility is run in USS.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH61423

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-05-20

  • Closed date

    2024-08-06

  • Last modified date

    2024-10-03

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

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

    UI97929 UI97930

Modules/Macros

  • CSQUODQU
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R300 PSY UI97930

       UP24/09/25 P F409

  • R400 PSY UI97929

       UP24/09/25 P F409

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":"BU048","label":"IBM Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"300","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
03 October 2024