IBM Support

PI20077: RANDOM PROBLEM OCCURS DURING TESTS OF THE MANDATORY PREDECESSOR FEATURE ON TWSZ V9.1 WHERE THE DEPENDENCY CAN NOT BE DELETED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The problem appears while using the Mandatory Predecessor
    feature on TWSz
    v9.1.
    TWSz user defined an application which contains only 2 DUMMY
    operations.
    The first one called FIRST with operation number 001
    The second one is called LAST and has the operation number 255
    For operation FIRST of this application, he defined an external
    dependency and made the LAST operation as external MANDATORY
    PREDECESSOR of the
    operation FIRST as follow:
    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
     EQQABEDP -------------- BROWSING AN EXTERNAL DEPENDENCY
     Command ===>
     View data below:
      Predecessor Description
      Ext application id     : PWSG0T01#SHIFT
      Operation              : DUMY 255
      Description            :
      Print option           : Always
      Dependency Resolution Criteria
      Mandatory resolution     : Control
      (normal dependency only)
      Resolution criteria      : Closest Preceding
    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    Thereafter, he extended his LTP and his CP so that occurrences
    of the
    application are brought into the current plan via the planing
    batchjobs.
    Now sometimes, the added occurrence of this application to the
    current
    plan with the earliest input arrival time stucks in status
    WAITING
    and has the LAST operation as Predecessor as well as Successor
    in the
     same time,
     as example as follow:
     <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
     EQQSPP1L -- PREDECESSORS AND SUCCESSORS TO AN OPERATION
     Type        Operation                    Jobname   Application
    id
            ws   no.     text
     ----   ---  ---    ------               ----
    ---------------
       P         255 **MANDATORY PEND. PRED*
    PWSG0T01#SHIFT
       S    DUMY 255                          LAST
    PWSG0T01#SHIFT
     <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
     If you want to delete the predecessor dependency  with the
    operation
     text
     "**MANDATORY PEND. PRED* " above, the dependency is not deleted
    and when
     you
     return with PF3 to panel:
     EQQMOCLL --------- MODIFYING OCCURRENCES IN THE CURRE
    the short message "NO CHANGE" and indeed the dependency is still
    there
    and not deleted.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: TWS for z/OS 9.1 and 9.2 users               *
    *                 FUNCTION=MCP                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Sometimes the Dialog user cannot        *
    *                      delete a mandatory pending              *
    *                      predecessor of an operation in the CP   *
    ****************************************************************
    * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
    ****************************************************************
    When an operation of an application has as mandatory
    pending predecessor an operation of the same application,
    the dialog user cannot delete the pending predecessor
    from the CP.
    

Problem conclusion

  • The problem occurs because the predecessor is not
    recognized as a mandatory pending.
    912Y
    922Y
    EQQMGCDX
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI20077

  • Reported component name

    TIV WRKLD SCHD

  • Reported component ID

    5697WSZ01

  • Reported release

    912

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-06-16

  • Closed date

    2014-09-12

  • Last modified date

    2016-04-27

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

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

    UI21315 UI21316

Modules/Macros

  • EQQMGCDX
    

Fix information

  • Fixed component name

    TIV WRKLD SCHD

  • Fixed component ID

    5697WSZ01

Applicable component levels

  • R912 PSY UI21315

       UP14/12/06 P F412

  • R922 PSY UI21316

       UP14/12/06 P F412

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":"912","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":"912","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 April 2016