IWS Jobs with Nested Run-Cycle Conditions Fail to Forecast in Automation Analytics & Intelligence

Products

• Automation Analytics & Intelligence

Issue/Introduction

In Automation Analytics & Intelligence, certain IWS (IBM Workload Scheduler) jobs do not appear in the forecast, even when the IWS-MX data pipeline is otherwise healthy and other jobstreams are forecasting normally.

Reviewing the logs (specifically the jaws.log) may show the following warning repeatedly: WARN [IWSZStartTimeCalculator] Trying to cast com.termalabs.common.hibernate.jaws.JobCondConj class to CalendarCondition for job [JobName].

Environment

Product: Automation Analytics & Intelligence 

Component: IWS Connector

Version(s): All versions prior to 26.0

Cause

The IWSZStartTimeCalculator component in Automation Analytics & Intelligence is designed to calculate job start times based on run-cycle conditions. It currently lacks the logic to recurse into nested run-cycle conditions.

When a job’s run cycle nests three levels deep (for example, stacking an AND condition with an inner OR condition, or multiple nested AND-conjunctions), the internal code attempts an invalid class cast, fails to recurse into the nested object, and drops that branch of dates. If that nested branch contained the only valid start time for the job, the job effectively loses its start time, resulting in no forecast. This issue is deterministic and affects any job containing compound run-cycle logic.

Resolution

This issue is identified as a product defect and is resolved in Automation Analytics & Intelligence Version 26.0.

To address this, ensure your environment is upgraded to release 26.0 or later once it is available.