GAVRDM32 Erreur GADATPRO plus 600 populating exchange in Optional Tasks with multinode Session
Article ID: 267891
Updated On:
Products
Issue/Introduction
On an Environment where there is a session that starts on one node and then switches to another node using an Optional Task that also changes the Submission Account, after some change in the Tasks, the Session stops executing of the first node and does not continue on the second node.
The following kind of errors appear in the universe.log of the node:
| 2023-05-31 13:59:59 |ERROR|X|IO |pid=26072.6| GAVRDM32 | Erreur GADATPRO
| 2023-05-31 14:59:59 |WARN |X|IO |pid=26072.6| owls_fla_item_populate_su | empty S.A
| 2023-05-31 15:59:59 |ERROR|X|IO |pid=26072.9| o_module_exc_cycle_emissi | Error 600 populating exchange data
| 2023-05-31 16:01:59 |ERROR|X|IO |pid=26072.9| o_module_exc_cycle_emissi | Error 600 populating exchange data
It seems this is related to the Processing Date calculation of the Optional Task but we don't see where the problem is.
A new multinode session using the same Management Units work correctly, it's just some Tasks that are affected, how can this be fixed?
Environment
Release : 6.x and 7.x
Component: Dollar Universe Application Server (Node)
Context: Multinode Session using Optional Tasks to switch the Submission Account or change the Scheduling of the next Uproc in the Session.
Cause
Wrong configuration of the Optional Task, it was found that its Functional Period was set to Weekly instead of Daily, probably due to a wrong update/import.
Resolution
Recreate or update the Optional Tasks associated to the impacted Session by setting the same Start Time and Rule as the Main Task solved the issue.
Feedback
