IBM Support

IJ30836: THE SKD.DURATION.INCLUDENONWORKINGTIME FLAG DOES NOT WORK CORRECTLY.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • With the System Property =1 that is not including the
    Non-Working time as it should. Just The CPM on selected records
    is changing the duration to include the non Working time and
    that is not consistent with the CPM button that doesn't include
    the Non-Working time to the duration
    
    
    Pre Conditions:
    
    One Work Order with  3 Children Work Order linked each work as
    predecessor and inside of each Children Work Order 3 tasks liked
    each other as predecessor with valid duration like 10 hours
    One Calendar with a Shift applied like Day calendar 5 Working
    days and 2 non-working days.
    
    
    Steps to Reproduce:
    
    1. Open the Work Order at the Graphical Scheduling application
    
    2.Setup the Calendar and Shift as define on Pre Requisition
    
    3.Setup the duration (Scheduler Start + Scheduler End) enough
    for the entire period like 6 months
    
    4. Open the Graphical View and click on the CPM button to adjust
     the dates
    
    The CPM is run but the duration value is updated and it should h
    ave remined the same.
    
    Expected Result:
    
    The duration of the Parent Records should be consistent so it
    should not include the Non-Working time or include according to
    the system Property - Just Low-level records should not change
    the duration with the System Property. Except when Inline
    editing, updating the Duration field, editing the end date, and
    adjusting the size of the bar.
    
    Reported in Version:
    
    Graphical Scheduler 7.6.8
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Scheduler users                                              *
    ****************************************************************
    

Problem conclusion

  • Fix has been made to fix....The fix for this APAR is contained
    in the following maintenance package:
    | release\fix pack\interim fix for Release 7.6.1.3 of Base
    Services(Scheduler 768x)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ30836

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    768

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-02-18

  • Closed date

    2021-04-30

  • Last modified date

    2021-04-30

  • 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

    MAXIMO SCHEDULE

  • Fixed component ID

    5724R46SE

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"768"}]

Document Information

Modified date:
01 May 2021