IBM Support

PI39141: IF A ZCENTRIC WORKSTATION IN OFFLINE STATUS IS MANUALLY VARIED ACTIVE AND THEN A CP EXTEND IS RUN A PROCESSING LOOP MIGHT OCCUR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A processing loop with thousands of event "2R" involved may
    be seen if a zcentric workstation is manually varied to ACTIVE
    status and then a CP EXTEND is run before the workstation gets
    set back to OFFLINE status.
    .
    The following recreate scenario has been used to produce the
    processing loop:
    .
    (1) The zcentric agent associated with a zcentric workstation
    definition is started (./StartUpLwa)
    (2) Some jobs are run using this zcentric workstation
    (3) The zcentric agent is shut down (./ShutDownLwa)
    (4) Additional jobs are submitted to the workstation
    (5) After some time these messages are seen in the controller
        EQQMLOG:
    EQQHT15E THE HTTP CLIENT FAILED TO PROCESS A REQUEST FOR
    DESTINATION zzzzzz
    EQQHT43I CLIENT FAILED TO OPEN. ERROR 1128 WHILE OPENING
    CONNECTION TO SERVER (HOSTNAME='n.nn.nnn.nn' -
    EQQHT43I PORT='ppppp'): 'EDC8128I Connection refused.'
    EQQWL10W WORK STATION wwww HAS BEEN SET TO OFFLINE  STATUS
    .
    (6) Within a few minutes the 5.5 dialog panel EQQMWSLL will
        show the zcentric workstation status as O (OFFLINE)
    (7) The workstation is manually varied back to A (ACTIVE)
        status and then within a few seconds a CP EXTEND is
        submitted (the CP EXTEND must start while the zcentric
        workstation is still in "A" status
    (8) The processing loop occurs.  If the zcentric agent is
        started again (./StartUpLwa) the loop will be terminated
    

Local fix

  • Do NOT vary a zcentric workstation to status ACTIVE (A)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All TWS for z/OS 851, 860, 910,920           *
    *                 zCentric users                               *
    *                 FUNCTION=zCentric                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Manual variation of the zCentric WS     *
    *                      status, can result in a submission      *
    *                      retry loop.                             *
    ****************************************************************
    * RECOMMENDATION: To fix:                                      *
    *                 - APPLY THE PTF FIXING THIS APAR             *
    *                 To Circumvent:                               *
    *                 - Avoid the manual status change of the      *
    *                   zCentric WS, if the Agent is down.         *
    *                 - Activate the zCentric Agent to interrupt   *
    *                   the retry loop.                            *
    ****************************************************************
    A processing loop with thousands of event "2R" created may
    be seen if a zCentric workstation is manually varied to ACTIVE
    status and then a CP EXTEND is run before the workstation gets
    set automatically back to OFFLINE status (since the Agent is
    actually down)
    The operations to be started on that Agent are indefinitely set
    to ready status after the failure in attempting to submit them.
    

Problem conclusion

  • zCentric code has been changed in order to properly manage the
    WS status. Moreover in this situation it might also occur that
    an operation supposed to end with JCLI is set to ready and
    retried.
    512Y
    602Y
    912Y
    922Y
    EQQEMQJS
    EQQZHTCL
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

  • ×**** PE16/04/18 PTF IN ERROR. SEE APAR PI60470  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI39141

  • Reported component name

    TIV WRKLD SCHD

  • Reported component ID

    5697WSZ01

  • Reported release

    512

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-04-15

  • Closed date

    2016-03-11

  • Last modified date

    2016-04-18

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

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

    UI33897 UI33898 UI33899 UI33900

Modules/Macros

  • EQQEMQJS EQQZHTCL
    

Fix information

  • Fixed component name

    TIV WRKLD SCHD

  • Fixed component ID

    5697WSZ01

Applicable component levels

  • R512 PSY UI33897

       UP16/03/17 P F603 ¢

  • R602 PSY UI33898

       UP16/03/17 P F603 ¢

  • R912 PSY UI33899

       UP16/03/17 P F603 ¢

  • R922 PSY UI33900

       UP16/03/17 P F603 ¢

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"512","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"512","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
18 April 2016