IBM Support

SE61631: MQM400-WAIT STRMQMLSR COMMAND MAY RESULT IN FDC AFTER SEVERAL MINUTES WAITING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • STRMQMLSR port(*DFT) may run long and result in FDC if the
    listener is already running for that port (and interface) if
    the STRMQMLSR job happens to run and end before the job
    performing the command finds the job. It is very time dependent.
    
    The command may take several minutes to complete, typically
    10-15 minutes.
    

Local fix

  • When possible, STRMQMLSR and name the port, even if it is the
    same as *DFT.
    
    Otherwise, this can be ignored. The FDC is noting that the job
    performing the STRMQMLSR command did not find the RUNMQLSR job.
    The FDC will list the submitted RUNMQLSR job and QHST can be
    used to verify the job started and ended.
    
    The STRMQMLSR command will just take time to finish.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    IBM MQ users on IBM i utilizing the STRMQMLSR command
    
    
    Platforms affected:
    IBM iSeries
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If the STRMQMLSR command is used with PORT(*DFT) and the
    listener is already running, IBM MQ will submit a job to attempt
    to start a listener. This submitted job will end immediately, as
    expected. However, the code servicing this submitted job could
    encounter a problem with retrieving the process id because of
    the immediate ending of the job.
    This failure to retrieve the process id can result in unexpected
    delays in processing the STRMQMLSR command, errors in the joblog
    of the job submitting the STRMQMLSR command, as well as an FDC
    similar to this:
    
    | Operating System :- OS400 V7R1M0 |
    | PIDS :- 5724H7226 |
    | LVLS :- 7.0.1.5 |
    | Product Long Name :- WebSphere MQ for i5/OS |
    | Vendor :- IBM |
    | Probe Id :- XC037002 |
    | Application Name :- MQM |
    | Component :- xcsExecProgram |
    | SCCS Info :- lib/cs/unix/as400/amqxprmx.c, 1.107.1.5 |
    | Line Number :- 1228 |
    | Build Date :- Apr 19 2011 |
    | CMVC level :- p701-105-110419 |
    | Activation Group :- 19 (QMQM) (QMQM/AMQOVFYX) |
    | Max File Handles :- 200 |
    | Process :- 00000321 |
    | UserApp :- FALSE |
    | Major Errorcode :- OK |
    | Minor Errorcode :- OK |
    | Probe Type :- INCORROUT |
    | Probe Severity :- 4 |
    | Probe Description :- AMQ6125: An internal WebSphere MQ error
    has occurred. |
    | FDCSequenceNumber :- 0 |
    | Arith1 :- 360000 0x'57e40' |
    | Arith2 :- 0 |
    | Comment1 :- RUNMQLSR |
    | |
    | Comment2 :- QMQM/QMQMJOBD |
    | |
    | |
    +---------------------------------------------------------------
    --------------+
    MQM Function Stack
    xcsExecProgram
    xcsFFST
    
    Failed to start job:
    SPP:0000 :1aefEDP03X SALAM 149553 :3960:0:13
    SPP:0x00003960: D9E4D5D4 D8D3E2D9 4040D8D4 D8D44040 RUNMQLSR
    QMQM
    SPP:0x00003970: 40404040 F1F4F9F5 F9F0 149590
    Job Submission:
    SPP:0000 :1aefEDP03X SALAM 149553 :3ab0:1:13
    SPP:0x00003ab0: D8E2E8E2 61E2C2D4 D1D6C240 D1D6C24D QSYS/SBMJOB
    JOB(
    SPP:0x00003ac0: D9E4D5D4 D8D3E2D9 5D40C3D4 C44DD8E2 RUNMQLSR)
    CMD(QS
    SPP:0x00003ad0: E8E261C3 C1D3D340 D8D4D8D4 61D9E4D5 YS/CALL
    QMQM/RUN
    SPP:0x00003ae0: D4D8D3E2 D9404D40 E77DF6F0 F9F47D40 MQLSR (
    X'6094'
    SPP:0x00003af0: E77DC4F2 C4F9C3F3 C4F4C4F8 C4F4C3F7
    X'D2D9C3D4D8D4C7
    SPP:0x00003b00: C4F9C6F1 F4F0F4F0 F4F0F4F0 F4F0F4F0
    D9F1404040404040
    SPP:0x00003b10: F4F0F4F0 F4F0F4F0 F4F0F4F0 F4F0F4F0
    4040404040404040
    SPP:0x00003b20: to SPP:0x00003b40: suppressed, 3 lines same as
    above
    SPP:0x00003b50: F4F07D40 E77DF6F0 C1F37D40 E77DC5F3 40' X'60A3'
    X'E3
    SPP:0x00003b60: C3F3C4F7 7D40E77D F6F0F9F7 7D40E77D C3D7'
    X'6097' X'
    SPP:0x00003b70: C6F1C6F3 C6F6C6F0 C6F57D40 E77DF6F0 F1F3F6F0F5'
    X'60
    SPP:0x00003b80: F8F27D40 E77DC6F2 C6F5C6F5 7D5D405D 82'
    X'F2F5F5') )
    SPP:0x00003b90: 40D1D6C2 D84D5CD1 D6C2C45D 40D9E3C7 JOBQ(*JOBD)
    RTG
    SPP:0x00003ba0: C4E3C14D 5CD1D6C2 C45D40D6 E4E3D84D DTA(*JOBD)
    OUTQ(
    SPP:0x00003bb0: 5CD1D6C2 C45D40C1 D3E6D4D3 E3E3C8C4 *JOBD)
    ALWMLTTHD
    SPP:0x00003bc0: 4D5CE8C5 E25D40C3 D7E8C5D5 E5E5C1D9 (*YES)
    CPYENVVAR
    SPP:0x00003bd0: 4D5CE8C5 E25D40D1 D6C2C44D D8D4D8D4 (*YES)
    JOBD(QMQM
    SPP:0x00003be0: 61D8D4D8 D4D1D6C2 C45D40D4 E2C7D84D /QMQMJOBD)
    MSGQ(
    SPP:0x00003bf0: 5CD5D6D5 C55D40E4 E2C5D94D D8D4D8D4 *NONE)
    USER(QMQM
    SPP:0x00003c00: 5D40C3E4 D9D3C9C2 4D5CE4E2 D9D7D9C6 )
    CURLIB(*USRPRF
    SPP:0x00003c10: 5D40C9D5 D3D3C9C2 D34D5CD1 D6C2C45D )
    INLLIBL(*JOBD)
    Job Info:
    SPP:0000 :1aefEDP03X SALAM 149553 :3980:2:13
    SPP:0x00003980: 00000000 00000000 00000000 00000000
    ................
    SPP:0x00003990: to SPP:0x000039d0: suppressed, 5 lines same as
    above
    QUSRJOBI Info:
    SPP:0000 :1aefEDP03X SALAM 149553 :3980:2:13
    SPP:0x00003980: 00000000 00000000 00000000 00000000
    ................
    SPP:0x00003990: to SPP:0x000039d0: suppressed, 5 lines same as
    above
    QUSRJOBI Error:
    SPP:0000 :1aefEDP03X SALAM 149553 :3790:3:13
    SPP:0x00003790: 00000030 0000002A C3D7C6F3 C3F5F3F0
    ........CPF3C530
    SPP:0x000037a0: D9E4D5D4 D8D3E2D9 4040D8D4 D8D44040 RUNMQLSR
    QMQM
    SPP:0x000037b0: 40404040 F1F4F9F5 F9F04000 00000000 149590 .....
    

Problem conclusion

  • For IBM MQ 7.1 and higher, the STRMQMLSR command has been
    modified to handle PORT(*DFT) the same way PORT(number) would
    be, if an attempt was made to start an already running listener.
    When a port number is specified, if a listener is already
    running on that port, then a job is NOT submitted for RUNMQLSR.
    This will prevent the scenario of having the job start and end
    immediately and potentially encounter problems with retrieving a
    process id.
    
    For IBM MQ 7.0.1, the STRMQMLSR command cannot be modified via
    fixpack, but the CPF3C53 error message has been removed as a
    condition for continuing to wait in the process id retrieval
    code. This error indicates that the job has already ended and
    will not be available, so it is not necessary to continue to
    wait for it. However, errors will still be logged and an FDC
    indicating the job did not start as requested. This change will
    allow the submitting program to error out immediately, rather
    than in a timed loop.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.14
    v7.1       7.1.0.7
    v8.0       8.0.0.3
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    SE61631

  • Reported component name

    WMQ ISERIES V7

  • Reported component ID

    5724H7226

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-04-03

  • Closed date

    2015-04-15

  • Last modified date

    2016-07-14

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

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

Modules/Macros

  • RCHMGR
    

Fix information

  • Fixed component name

    WMQ ISERIES V7

  • Fixed component ID

    5724H7226

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 April 2020