IBM Support

IJ40060: COMPLIANCESTARTCRONTASK INSTANCE NOT CREATED FOR SKDPROJECTID>999

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

  • The ComplianceStartCronTask instance does not get created unless
    you change the Schedule Frequency value in Graphical
    Scheduling's Compliance tab. This is happening for projects with
    SKDPROJECTID>999
    
    STEPS TO REPRODUCE:
    
    Go to Cron Task Setup application and select record
    SKDComplianceStartCronTask
    There is no existing instance for this crontask.
    In Work Order Tracking, create a WO record for a Location. In
    Plans tab and Labor subtab, enter a Craft for a number of
    hours.
    Save and approve the WO.
    Create a saved query for this WO.
    In Graphical Scheduling, create a new Schedule and Calendar =
    DAY.
    The Start Date (system date) and End Date (Sysdate + 14 days)
    are populated automatically.
    Do Copy Query and reference the saved query for this WO.
    Save the Schedule record.
    Click on the Compliance tab and Details sub-tab.
    Enter:
    Schedule Compliance Start Date = enter system date
    Duration = 2
    Duration Units = WEEKS
    Schedule Compliance End Date = is populated automatically with
    system date + 2 weeks
    Check the Cron Active? box.
    Save the Schedule record.
    Schedule Frequency = 1d,0,0,0,,,,,, and leave it
    unchanged.
    Do NOT click on Start Compliance button.
    Go back to Cron Task Setup application and select
    SKDComplianceStartCronTask: there is NO new instance created
    for it.
    
    RESULT:
    A new instance does not get created for ComplianceStartCronTask
    unless you change the Schedule Frequency value from its default
    of 1d,0,0,0,,,,,, in Graphical Scheduling's Compliance tab
    
    EXPECTED RESULTS:
    The Schedule Frequency value in Graphical Scheduling's
    Compliance tab should be either empty initially or updated
    automatically to match the values from the Duration and Duration
    Units fields, so that the ComplianceStartCronTask
    instance gets created thanks to the Schedule Frequency's correct
    value.
    
    REPORTED IN VERSION:
    Maximo Asset Management  7.6.1.1
    

Local fix

  • Go back to the Schedule record.
    Open the dialog for Schedule Frequency field and change to
    'Every 14 Days' to match the Duration and Duration Units values.
    
    This time, Schedule Frequency = 14d,0,0,0,,,,,,
    Save the record.
    Go to Cron Task Setup: this time, a new instance has been
    created for SKDComplianceStartCronTask.
    

Problem summary

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

Problem conclusion

  • The fix for this APAR will be contained in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ40060

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-05-16

  • Closed date

    2022-10-08

  • Last modified date

    2022-10-08

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

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

Document Information

Modified date:
08 October 2022