ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Event is removed from the Job Event list when being executed several times for the same processing date
Article ID: 87377
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Error Message :
Product Version: Dollar.Universe 5.6.0 FX25010
Some jobs having dependency conditions remain indefinitely in status Event Wait, therefore its predecessors were correctly executed previously.
On Job Events, the corresponding Job Event does no longer appear.
When looking at the History Trace of the same Uproc launched in another session / different Management Unit at the same time, the following kind of lines appear showing that the previous Job Event had been purged:
For example:
##############
Start Completion Instructions
09/17/2012 02:30:07 *** NORMAL TASK COMPLETION ***
Session Number Uproc Number M.U. Aut.Proc.Dt Date Time E
RMSS_SIMDY 0001498 RMSA_WASIP 0014790 A_RMSSIM01 915 16092012 16092012 023004 T
RMSS_SIMDY 0001513 RMSA_WASIP 0014978 A_RMSSIM01 915 17092012 17092012 023004 T
*** TOTAL *** - Duration : 00.00:00:04.00 - CPU : 00.00:00:00.17
- PGF : ???? - DIO : ???? - BIO : ????
###############
Patch level detected:Dollar Universe 5.6.0
Product Version: Dollar.Universe 5.6.0 FX25010
Some jobs having dependency conditions remain indefinitely in status Event Wait, therefore its predecessors were correctly executed previously.
On Job Events, the corresponding Job Event does no longer appear.
When looking at the History Trace of the same Uproc launched in another session / different Management Unit at the same time, the following kind of lines appear showing that the previous Job Event had been purged:
For example:
##############
Start Completion Instructions
09/17/2012 02:30:07 *** NORMAL TASK COMPLETION ***
Session Number Uproc Number M.U. Aut.Proc.Dt Date Time E
RMSS_SIMDY 0001498 RMSA_WASIP 0014790 A_RMSSIM01 915 16092012 16092012 023004 T
RMSS_SIMDY 0001513 RMSA_WASIP 0014978 A_RMSSIM01 915 17092012 17092012 023004 T
*** TOTAL *** - Duration : 00.00:00:04.00 - CPU : 00.00:00:00.17
- PGF : ???? - DIO : ???? - BIO : ????
###############
Product Version: Dollar.Universe 5.6.0 FX25010
Some jobs having dependency conditions remain indefinitely in status Event Wait, therefore its predecessors were correctly executed previously.
On Job Events, the corresponding Job Event does no longer appear.
When looking at the History Trace of the same Uproc launched in another session / different Management Unit at the same time, the following kind of lines appear showing that the previous Job Event had been purged:
For example:
##############
Start Completion Instructions
09/17/2012 02:30:07 *** NORMAL TASK COMPLETION ***
Session Number Uproc Number M.U. Aut.Proc.Dt Date Time E
RMSS_SIMDY 0001498 RMSA_WASIP 0014790 A_RMSSIM01 915 16092012 16092012 023004 T
RMSS_SIMDY 0001513 RMSA_WASIP 0014978 A_RMSSIM01 915 17092012 17092012 023004 T
*** TOTAL *** - Duration : 00.00:00:04.00 - CPU : 00.00:00:00.17
- PGF : ???? - DIO : ???? - BIO : ????
###############
Patch level detected:Dollar Universe 5.6.0
Product Version: Dollar.Universe 5.6.0 FX25010
Some jobs having dependency conditions remain indefinitely in status Event Wait, therefore its predecessors were correctly executed previously.
On Job Events, the corresponding Job Event does no longer appear.
When looking at the History Trace of the same Uproc launched in another session / different Management Unit at the same time, the following kind of lines appear showing that the previous Job Event had been purged:
For example:
##############
Start Completion Instructions
09/17/2012 02:30:07 *** NORMAL TASK COMPLETION ***
Session Number Uproc Number M.U. Aut.Proc.Dt Date Time E
RMSS_SIMDY 0001498 RMSA_WASIP 0014790 A_RMSSIM01 915 16092012 16092012 023004 T
RMSS_SIMDY 0001513 RMSA_WASIP 0014978 A_RMSSIM01 915 17092012 17092012 023004 T
*** TOTAL *** - Duration : 00.00:00:04.00 - CPU : 00.00:00:00.17
- PGF : ???? - DIO : ???? - BIO : ????
###############
Cause
Cause type:
By design
Root Cause: By default , Uproc is defined so that only one Job Event is kept for one Single Processing Date.
If the Uproc is launched twice at the same moment, the executions will remove the event created by each launch. As a result, there will be no Event recorded in the Job Event list.
By design
Root Cause: By default , Uproc is defined so that only one Job Event is kept for one Single Processing Date.
If the Uproc is launched twice at the same moment, the executions will remove the event created by each launch. As a result, there will be no Event recorded in the Job Event list.
Environment
OS: All
Resolution
Do not schedule the uproc to launch twice at the same time or change the definition of the uproc to record more than 1 event.
For example:
Memorize all Instances for a Processing Date
and
Remember the last 1 Processing Date.
Fix Status: No Fix
For example:
Memorize all Instances for a Processing Date
and
Remember the last 1 Processing Date.
Fix Status: No Fix
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
