IBM Support

PM39626: QUEUE LTERM NAME(DFSTCF) DATA(LOAD XXXXXXXX) IS PLACED ON THE SHARED QUEUE AND CAN BE PROCESSED BY ANY SYSTEM IN THE GROUP.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the QUEUE LTERM NAME(DFSTCF) command issued on one IMS
    in shared queue environment, the command output go to another
    IMS in the shared queue.
    .
    Before the QUEUE LTERM NAME(DFSTCF) command, a display of the
    LTERM DFSTCF shows the following:
    R 868,/DIS LTERM DFSTCF
    IEE600I REPLY TO 868 IS;/DIS LTERM DFSTCF
    DFS000I     LTERM     ENQCT   DEQCT    QCT   IMSA
    DFS000I     DFSTCF        9       9      0  STATIC   IMSA
    DFS000I     *10111/154836*   IMSA
    870 DFS996I *IMS READY*  IMSA
    R 869,/DIS LTERM DFSTCF
    IEE600I REPLY TO 869 IS;/DIS LTERM DFSTCF
    DFS000I     LTERM     ENQCT   DEQCT    QCT   IMSB
    DFS000I     DFSTCF        5       5      0  STATIC   IMSB
    DFS000I     *10111/154842*   IMSB
    871 DFS996I *IMS READY*  IMSB
    .
    Then the QUEUE LTERM NAME(DFSTCF) command issued on IMSB.
    Response for: QUEUE LTERM NAME(DFSTCF) DATA(LOAD ...
    Lterm    MbrName    CC
    DFSTCF   IMSB        0
    .
    After the command, a display of the LTERM DFSTCF shows
    the ENQCT/DEQCT for IMSA incremented from 9 to 10.
    R 870,/DIS LTERM DFSTCF
    IEE600I REPLY TO 870 IS;/DIS LTERM DFSTCF
    DFS000I     LTERM     ENQCT   DEQCT    QCT   IMSA
    DFS000I     DFSTCF       10      10      0  STATIC   IMSA
    DFS000I     *10111/155336*   IMSA
    872 DFS996I *IMS READY*  IMSA
    R 871,/DIS LTERM DFSTCF
    IEE600I REPLY TO 871 IS;/DIS LTERM DFSTCF
    DFS000I     LTERM     ENQCT   DEQCT    QCT   IMSB
    DFS000I     DFSTCF        5       5      0  STATIC   IMSB
    DFS000I     *10111/155340*   IMSB
    873 DFS996I *IMS READY*  IMSB
    .
    We need to treat LTERM DFSTCF the same way as DFSTCFI that
    resolved by APAR PQ59806.
    .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V11 users of QUE LTERM NAME(DFSTCF)  *
    *                 DATA(LOAD xxxxxx) in a SharedQ environment.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: QUE LTERM NAME(DFSTCF) DATA(LOAD xxxx)  *
    *                      is placed on the shared queue & can be  *
    *                      processed by any IMS in the group.      *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    When Type-2 command QUEUE LTERM NAME(DFSTCF) DATA(LOAD xxxxxxxx)
    is issued & LTERM DFSTCF has a status of PSTOP the load request
    is routed to another IMS within the shared queue group.  /PSTOP
    LTERM DFSTCF is the method used to stop TCO and /START LTERM
    DFSTCF is the method to restart TCO.  By routing the QUEUE LTERM
    NAME(DFSTCF) DATA(LOAD xxxxxxxx) command to another IMS within
    the shared queue group the method of stopping TCO is
    circumvented.   The result is executing IMS commands on an IMS
    system other than the IMS system the commands are intended for.
    If the load request is for a DFSTCF member which does not exit
    on the IMS executing the load a DFS3345E message is generated.
    
    The Time Control Option (TCO) is intended to be a local function
    and should not be routed to another IMS within a shared queue
    group.
    

Problem conclusion

  • GEN:
    KEYWORDS: CMDQUE MSGDFS3345E MSGDFS3379E
    
    *** END IMS KEYWORDS ***
    DFSIQU20 is changed to check if the LTERM is a TCO LTERM and if
    so the load is placed on the local queue rather than the shared
    queue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM39626

  • Reported component name

    IMS V11

  • Reported component ID

    5635A0200

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-05-19

  • Closed date

    2011-06-06

  • Last modified date

    2011-07-05

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

    PM17558

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

    UK68491

Modules/Macros

  • DFSIQU20
    

Fix information

  • Fixed component name

    IMS V11

  • Fixed component ID

    5635A0200

Applicable component levels

  • R100 PSY UK68491

       UP11/06/07 P F106

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":"100","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 July 2011