IBM Support

PM07794: DYNAMIC CRITICAL PATH: DEADLINE HANDLING ENHANCEMENT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • The current product design does not allow users to condition
    late processing to the deadlines of critical jobs
    .
    This APAR will improve and the calculation of critical path by
    considering ONLY the deadline of the critical target job itself.
    For all non-critical predecessors of a critical job, an
    operation-level deadline will be simulated beyond the end of
    the tail plan.  The change will be activated at customer option,
    through a two new parameters to the BATCHOPT initialization
    statement, IGNOREDEADL(YES|NO), and TIMEDEPCHK(YES|NO).
    .
    This APAR creates new messages EQQ3165I, EQQ5010I and EQQ5011I.
    CPH
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL TWS for z/OS 8.3.0, 8.5.0 and            *
    *                 8.5.1 USERs who run with Dynamic             *
    *                 Critical Path.                               *
    *                                                              *
    *                 FUNCTION=DP,MCP,CPH                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Users are forced to specify             *
    *                      deadlines when defining                 *
    *                      applications. To run with an            *
    *                      effective late processing in a          *
    *                      critical network, users are expected    *
    *                      to have, for each job table entry,      *
    *                      a deadline that comes after             *
    *                      (or at the same time) respect           *
    *                      to the deadline of the critical         *
    *                      job. This setting is needed to          *
    *                      have the latest start times             *
    *                      calculated accordingly with what        *
    *                      is specified for critical jobs.         *
    *                      As a manual action, this activity       *
    *                      is not easy for customers, as           *
    *                      their networks can be very huge.        *
    *                      .                                       *
    *                      In addition, the Estimated Start Time   *
    *                      for each job entry is initialized       *
    *                      by the Planned Start Time of the        *
    *                      operation in the CP. Planned Start      *
    *                      Times are calculated by Daily Plan      *
    *                      batch by always referring to Input      *
    *                      Arrival Times even for operations       *
    *                      that are not time dependent.            *
    ****************************************************************
    * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
    ****************************************************************
    To run with an effective late processing in a critical
    network, users are expected to have, for each job table entry,
    a deadline that comes after (or at the same time) respect
    to the deadline of the critical job. This setting is needed to
    have the latest start times calculated accordingly with what
    is specified for critical jobs.
    .
    In addition, Planned Start Times, used to initialize
    Estimated Start Times for critical job table entries,
    are calculated batch by always referring to Input
    Arrival Times even for operations that are not time dependent.
    

Problem conclusion

Temporary fix

Comments

  • Two new parameters have been added to be specified in
    BATCHOPT:
    IGNOREDEADL to automatically move deadlines for any
    not critical and not suppress-if-late operation
    to the CP tail end.
    .
    TIMEDEPCHK to calculate planned start times for operations
    that are not time dependent starting from
    the beginning of the extend/re-plan interval instead
    of starting from Input Arrival Time. In addition, dynamic
    addition of critical job entries has been changed to
    initialize the estimated start times to the current time
    instead of using Input Arrival Times, in case of
    operations that are not time dependent.
    

APAR Information

  • APAR number

    PM07794

  • Reported component name

    TIV WRKLD SCHD

  • Reported component ID

    5697WSZ01

  • Reported release

    300

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-02-17

  • Closed date

    2011-04-28

  • Last modified date

    2012-07-06

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

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

    UK66978 UK66979 UK66980 UK67060 UK67061 UK67062 UK67135 UK67138
    UK67159 UK67160 UK67161 UK67162 UK67163 UK67164 UK67165 UK67166
    UK67167

Modules/Macros

  • DCLBCA   DCLBOPT  DCLCPR01 DCLCPR3P DCLMCA
    DCLMIO   EQQBOPTX EQQCPHAN EQQDPCES EQQDPEND EQQDPLOP EQQDPNNH
    EQQDPNWT EQQDPOES EQQDPOLU EQQDPOOP EQQDPTIL EQQMABTX EQQMAOPX
    EQQMARXX EQQMCBTX EQQMCCLX EQQMCCTX EQQMCDLX EQQMCDTX EQQMCOCX
    EQQMCSTX EQQMCTOP EQQMC1UP EQQMC3CH EQQMC3LO EQQMC3UP EQQMGAOX
    EQQMGOOX EQQMGQDX EQQMG3QX EQQMLOCX EQQMMADX EQQMMAIX EQQMMCCX
    EQQMMDMX EQQMMDPX EQQMMDXX EQQMMGEX EQQMMJOX EQQMMJRQ EQQMMOAX
    EQQMMODX EQQMMOMX EQQMMOPX EQQMMOUX EQQMMSRX EQQMMTIP EQQMMTIX
    EQQMMUFX EQQMMXDX EQQMOBTX EQQMOCWX EQQMOPCX EQQMOUSX EQQMOVDX
    EQQMOVPX EQQMOVSX EQQM0LOG EQQM0LRI EQQPDFDL EQQRGJSX EQQSTINI
    EQQ316   EQQ501
    

Publications Referenced
SC32126503SC32126504SC32126505SC32126703SC32126704
SC32126705    

Fix information

  • Fixed component name

    TIV WRKLD SCHD

  • Fixed component ID

    5697WSZ01

Applicable component levels

  • R3A1 PSY UK67060

       UP11/05/24 P F105

  • R3A2 PSY UK67061

       UP11/05/24 P F105

  • R3A3 PSY UK67062

       UP11/05/24 P F105

  • R3A4 PSY UK67135

       UP11/05/24 P F105

  • R300 PSY UK66978

       UP11/05/24 P F105

  • R302 PSY UK67138

       UP11/05/24 P F105

  • R5A1 PSY UK67159

       UP11/05/24 P F105

  • R5A2 PSY UK67160

       UP11/05/24 P F105

  • R5A3 PSY UK67161

       UP11/05/24 P F105

  • R5A4 PSY UK67162

       UP11/05/24 P F105

  • R5E1 PSY UK67163

       UP11/05/24 P F105

  • R5E2 PSY UK67164

       UP11/05/24 P F105

  • R5E3 PSY UK67165

       UP11/05/24 P F105

  • R5E4 PSY UK67166

       UP11/05/24 P F105

  • R500 PSY UK66979

       UP11/05/24 P F105

  • R502 PSY UK67167

       UP11/05/24 P F105

  • R510 PSY UK66980

       UP11/05/24 P F105

  • R512 PSY UK67168

       UP11/05/24 P F105

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

Document Information

Modified date:
06 July 2012