IBM Support

IJ03926: GRAPHICAL SCHEDULING - NON-INTERRUPTIBLE SUCCESSOR SHOULD BE SCHEDULED AT START OF WORKING TIME, NOT OFFSET.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In
    this case when the predecessor finishes in non-working
    time, the successor is not scheduled when it should be at the
    start of the next working shift, but rather gets delayed by the
    same number of hours that the predecessor works in the
    non-working time.
    
    If the predecessor works 3 hours in the non-working time, the
    successor does not start when it should at 7am, the shift
    start, but is offset  by those 3 hours and starts at 10am.
    
    STEPS TO REPRODUCE:
    
    1. Create a WO with two tasks. Interruptible
    should not be checked on either task or the WO.
    2. Give Task 10 a duration  of 3 and Task 20 a duration of 4.
    3. Make the first task, 10,  a predecessor of the second task,
    20, with a FS relationship of 0 lag.
    4. On the WO, set the scheduled start to the next Monday at
    7:00 AM and  finish date to that same date at 2:00 PM
    5. Create a Schedule using the DAY calendar, DAY shift, and
    have  Restrict Work To Dates unchecked.
    6. Work Query for the schedule should be for  the WO
    you created in Step 1
    7. Save
    8. Open Gantt View tab.
    9. Using the Gantt, drag Task 10  so that it's Start is 1 hour
    from the end of the working time, 2pm, and its Finish is 2
    hours into the non-working time, at 5pm.
    10. Calculate the schedule dates by clicking the toolbar icon
    labelled Perform Critical Path Method on All Rows.
    
    You will see that Task 10 is scheduled where you placed it,
    with a Start of 2pm and a Finish 3 hours later at 5pm.
    Task 20 has to wait for the start of the next working shift at
    7am but is instead offset 2 hours into the working shift and
    starts at 9am.
    
    This was fixed in some source code already and is referenced by
    RTC request 298057.     That fix needs to get ported into the
    Interim Fixes as requested.
    

Local fix

  • (none)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of the Graphical Scheduling in Scheduler 7.6.5         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * NON-INTERRUPTIBLE SUCCESSOR SHOULD BE   SCHEDULED AT START   *
    * OF WORKING TIME, NOT OFFSET.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A code fix has been delivered to address this issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ03926

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    765

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-05

  • Closed date

    2018-02-06

  • Last modified date

    2018-02-06

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

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

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    MAXIMO SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

  • R765 PSY

       UP



Document information

More support for: Maximo Asset Management Scheduler

Software version: 765

Reference #: IJ03926

Modified date: 06 February 2018