activate_uc_object in post process can cause endless loop

book

Article ID: 225170

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

In version 11.2 through 12.3, it is possible to create an endless loop in the post process tab; MAX_NESTING_DEPTH is ignored.

Reproduction steps

  1. Create a job object that has the following in the Post Process tab:
    : set &run# = activate_uc_object(&$NAME#)
  2. Run the job

Expected behavior:
As this cannot be done in the pre-process or process tabs which reference the MAX_NESTING_DEPTH, it's expected that the Post Process would work the same way

Actual behavior:
MAX_NESTING_DEPTH is ignored and an infinite loop is created which can put a strain on regular WP processes

Cause

Design issue in 11.2 through 12.3

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

This has been fixed in version 21.

The fix for this involves a new column in the EH table and new code which could potentially destabilize the product and so is not a practice that Broadcom development will follow.

The possibility to create endless loops in this fashion has been in the product since version 11.2 (it was also technically possible before this by using activate_uc_object to activate an object that activated the one activating it) and can be avoided through scripting best practices in version 12.3 and below.