IBM Support

PI85059: PROCESS SUCCEEDING EVEN THOUGH AGENT IS OFFLINE

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

  • If an agent is offline it will not be detected before the
    process starts. This will occur when an agent is mapped to a
    component resource in the
    resource tree and the application process expects all agents to
    be online before the process starts and would not otherwise
    update that resource except through an operational process.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If an agent is offline it will not be detected before the    *
    * process starts. This will occur when an agent is mapped to a *
    * component resource in the                                    *
    * resource tree and the application process expects all agents *
    * to                                                           *
    * be online before the process starts and would not otherwise  *
    * update that resource except through an operational process.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A fix is available in IBM UrbanCode Deploy 7.0.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI85059

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-26

  • Closed date

    2018-08-08

  • Last modified date

    2018-08-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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 August 2018