AS400 related uprocs remain in Event Wait due to Remote Job Events not resolved

Products

• CA Automic Dollar Universe

Issue/Introduction

When running multi-node sessions involving an AS400 node and another node (such as Unix/Linux or Windows), Uprocs intermittently remain in "Event Wait" (Attente d'événement) status.

• The expected remote Uproc has already completed successfully on the other node.
• The issue occurs in both directions (AS400 waiting for Linux, or Linux waiting for AS400).
• The behavior is random; the same session may succeed in one execution and fail in the next.
• This has been observed on AS400 versions such as 6.9.23 or 6.10.61.

Environment

Dollar Universe 6.x on AS400

Cause

This issue is caused by a product defect (internal reference DE123381 / DU_AS-7520) where Remote Job Events are intermittently not resolved correctly when executing within the context of a multi-node session on the AS400 platform.

Resolution

Resolution

A fix has been developed and delivered in the following version:

• Dollar Universe AS400 kit version 6.10.63 or higher
  
  Note: As Dollar Universe has reached End of Service (EOS) for AS400 and OpenVMS platforms, this fix is provided as part of the final maintenance kits for these operating systems. For more details on the support lifecycle, refer to the Product Advisory.

Workaround

If an immediate upgrade is not possible, the following configuration changes may mitigate the issue:

1. Modify the multi-node session to have Uprocs succeed each other directly rather than relying on cross-node event dependencies.
2. Manually release the event or force completion of the Uproc in "Event Wait" if the remote job is confirmed as finished.
3. If applicable, using 'Same' user account instead of 'Any' in the condition may work

Additional Information

Public Title: Remote dependency conditions may not be correctly resolved when an AS400 node is involved.

Public Description: A problem has been fixed where a remote dependency condition is not resolved despite the expected Job event being actually created.
This problem occurs between an AS400 node and a non-AS400 node.