IBM Support

PH02709: STEP CONFIGURATIONS' TIMEOUT VALUE IS TREATED AS MILLISECONDS INSTEAD OF MINUTES

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

  • When configuring a step, based on the description in the user
    interface, the value for step's timeout should be entered in
    minutes. However, this value is treated as milliseconds by the
    server. This results in steps timing out prematurely.
    

Local fix

  • Enter the timeout value in milliseconds, even though the
    description mentions minutes. However, once this issue is fixed,
    the value must be changed back to minutes to avoid setting a
    very large timeout value.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When configuring a step, based on the description in the     *
    * user                                                         *
    * interface, the value for step's timeout should be entered in *
    * minutes. However, this value is treated as milliseconds by   *
    * the                                                          *
    * server. This results in steps timing out prematurely.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This issue has been fixed in UrbanCode Build 6.1.3.3. A
    cumulative patch for this fix is also available for UrbanCode
    Build versions 6.1.3.0 through 6.1.3.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH02709

  • Reported component name

    URBANCODE BUILD

  • Reported component ID

    5725P5700

  • Reported release

    613

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-09-11

  • Closed date

    2018-10-01

  • Last modified date

    2018-10-01

  • 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

    URBANCODE BUILD

  • Fixed component ID

    5725P5700

Applicable component levels

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

Document Information

Modified date:
01 October 2018