IBM Support

IV96647: READING BASED PM SCHEDULS SET TO ONE TIME ONLY DO NOT SEEM TO BE WORKING CORRECTLY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When creating a Reading Based PM Schedule with an Action
    occurrence set to One Time Only I would expect that only one
    task would be created when that rule is met.  We are finding
    that it is creating a task every time you enter a reading that
    exceeds that threshold.
    
     So if I enter a reading today and it is above 170 for example,
    then I expect a work task to be generated,
    If I enter a subsequent reading and it is still above 170 the
    system generates a work task again, then this is not "One Time
    Only" this is more as "Any Time".
    

Local fix

  • No
    

Problem summary

  • The One Time Only option selected for Action Occurrence on
    Reading Based PM Schedule needs to create the work tasks only
    one time when the condition is met.
    Technical Note:
    Workflow Builder
    triPMReadingLog - triCreate - triPMReading : The workflow has
    been modified to move the logic for One Time Only Action
    Occurrence into the new workflow mentioned below.
    triPMReadingLog - Synchronous - One Time Only Action Occurrence
    : A new workflow has been created to check all the conditions
    for One Time Only Action Occurrence. This workflow is called
    inside the above workflow.
    

Problem conclusion

  • The Reading Based PM Schedules are are not working as expected
    when the Action Occurrence is selected as One Time Only. The
    issue has been resolved by modifying the workflow for One Time
    Only selection. And the worktasks are now created only one time
    when the condition is met.
    This is targeted to the 1h2017 Application/OM Release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV96647

  • Reported component name

    TRI APP PLTFM R

  • Reported component ID

    5725F26RE

  • Reported release

    350

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-26

  • Closed date

    2017-06-10

  • Last modified date

    2017-06-10

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

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

Modules/Macros

  • 999
    

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"350","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
30 March 2022