IBM Support

IV62216: VALIDFROM DOES NOT SELECT THE DAY CORRECTLY HAVING 2 JOB STEAMS WITH THE SAME NAME AND -1 WORKDAYS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Environment:
    MDM: TWS 8.5.1 GA
    
    Replication steps:
    1. Define a calendar with the first of the month.
    ONEDAY
      "First of the month"
    09/01/2013 10/01/2013 11/01/2013 12/01/2013 01/01/2014
    02/01/2014 03/01/2014 04/01/2014 05/01/2014 06/01/2014
    07/01/2014 08/01/2014 09/01/2014 10/01/2014 11/01/2014
    12/01/2014
    
    2. Define 2 job steams with the same name and validfrom.
    The later validfrom is defined on the day which is calculated
    as "ON" day with -1 WORKDAYS.
    
    Calendar ONEDAY : 06/01/2014.
    Since May 31 is Saturday, "06/01/2014 -1 WORKDAY" is  May 30.
    
    SCHEDULE DR851#JSVALIDFM VALIDFROM 01/10/2014
    ON RUNCYCLE RULE1 ONEDAY -1 WORKDAYS
    :
    DR851#JOB001
    END
    
    SCHEDULE DR851#JSVALIDFM VALIDFROM 05/30/2014
    ON RUNCYCLE RULE1 ONEDAY -1 WORKDAYS
    :
    DR851#JOB002
    END
    
    3. Confirm on Run Cycle Preview that May 30 is not selected as
    a planned date.
    
    
    OK case 1:
    June 1 is selected as plan day correctly.
    
    Calendar day: 06/01/2014
    SCHEDULE DR851#JSVALIDF1 VALIDFROM 01/10/2014
    ON RUNCYCLE RULE1 ONEDAY
    :
    DR851#JOB001
    END
    
    SCHEDULE DR851#JSVALIDF1 VALIDFROM 06/01/2014
    ON RUNCYCLE RULE1 ONEDAY
    :
    DR851#JOB002
    END
    
    OK case 2:
    May 31 is selected as plan day correctly.
    
    Calendar day: 06/01/2014
    "06/01/2014 -1 DAYS is  May 31.
    
    SCHEDULE DR851#JSVALIDF2 VALIDFROM 01/10/2014
    ON RUNCYCLE RULE1 ONEDAY -1 DAYS
    :
    DR851#JOB001
    END
    
    SCHEDULE DR851#JSVALIDF2 VALIDFROM 05/31/2014
    ON RUNCYCLE RULE1 ONEDAY -1 DAYS
    :
    DR851#JOB002
    END
    
    Note:
    The issue occurs if the first day of the month is Saturday or
    Sunday.
    

Local fix

  • Define a specific job steam to run on the missing day.
    

Problem summary

  • The issue occurs in this case:
    - define a calendar with a set of days
    - define a runcycle that uses the calendar and has the rule
    "Offset: -1 WORKDAYS"
    - define a JOBSTREAM that uses the RUNCYCLE and has a VALIDFROM
    value
    If the VALIDFROM value coincide with one of the calculated
    runcycle instances than that instance is not used.
    E.g.
    Set the calendar defined on the day 01/06/2014, called CAL1
    Set a runcycle RC1 that uses CAL1 with the OFFSET -1 WORKDAYS
    Set the JobStream JS1 with VALIDFROM 30/05/2014.
    The RUNCYCLE is calculated as 01/06/2014 - 1 WORKDAYS that
    should be 31/05/2014. But the 31/05/2014 is sunday so
    30/05/2014 is taken.
    The value 30/05/2014 is the same as the VALIDFROM value. In this
    case TWS is excluding that runcycle instance.
    
    Managing the case in which the runcycle instance coincide with
    the validfrom.
    

Problem conclusion

  • This apar will be fixed  8.6.0-TIV-TWS-FP0005,
    8.5.1-TIV-TWS-FP0006, 8.5.0-TIV-TWS-FP0006 and
    9.1.0-TIV-TWS-FP0002, 9.2.0-TIV-TWS-FP0002.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV62216

  • Reported component name

    TIV WKLD SCHDL

  • Reported component ID

    5698WKB85

  • Reported release

    8L5

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-02

  • Closed date

    2014-08-29

  • Last modified date

    2016-11-07

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

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

Fix information

  • Fixed component name

    TIV WKLD SCHDL

  • Fixed component ID

    5698WKB85

Applicable component levels

  • R8L5 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8L5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
07 November 2016