search cancel

Multinode conditions not being resolved after uxpurevt

book

Article ID: 214993

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Problem with resolving multinode conditions after uxpurevt execution caused by XA records "update date" being in the past.

Use case when job requests for update of XA record in u_fmev60.dta:
- if XA record already exists then the "update date" remains the same in central
- if XA record does not exist then new record is created with current "update date" in central

Uxpurevt issue scenario:
If the XA entry exists in u_fmev60.dta file for the next job requesting it, the "update date" won't be updated.
So during execution of uxpurevt and purging after 4 days the XA entry which remain older than 4 days will be purged so most current scheduled batch can not start.

Resolution

Update to a fix version listed below or a newer version if available.

Fix version(s): 
Component: Application.Server
Dollar Universe 6.10.71

Additional Information

The correction made is that even if the XA exists for the next job requesting it, the "update date" will be... updated.