E9.2 Orchestrator monitor logs nothing from studio

[EricGagne]

Hi List,

We are currently testing 9.2.8.3 for a planned upgrade from 9.2.7.4. When running an orchestration from the studio nothing gets logged, no record added to F980060. I can't find anything about this issue online. We tried different settings in the monitoring options but it made no difference.

Is this a change that JDE made or are we missing something in our configuration ?

 

[DaveWagoner]

9283 is fascinating when it comes to looking for orch exceptions. if you're trying to see them from tasks/menus, it's *poof* gone! you need to manually fastpath to P980060, because all the orch exception tasks now lead to stateful orch monitoring P980040. Just in case that's it.

If your actual orch exceptions is empty after running some, I'm guessing it's a config issue and you might be more fruitful posting your question in cnc area?

 

[BetoJDE]

9283 is fascinating when it comes to looking for orch exceptions. if you're trying to see them from tasks/menus, it's *poof* gone! you need to manually fastpath to P980060, because all the orch exception tasks now lead to stateful orch monitoring P980040. Just in case that's it.

If your actual orch exceptions is empty after running some, I'm guessing it's a config issue and you might be more fruitful posting your question in cnc area?

Added to this remember that in 9.2.8.2 also include the custom login https://www.jdelist.com/community/threads/orchestration-run-options-monitoring.59127/ and that use new aplication and table(s), maybe someting is missing for the CNC team

 

[EricGagne]

Our issue at least for 9.2.8.3 was fixed this morning. There was a bit of confusion in this. I was told yesterday that in our JDE Pay system which is on 9.2.8.3 already, orchestrations are logged only when called from outside, not from the studio.

But in our current tests it was not logging anything. Somehow the CNC fixed it this morning and now it logs everything, studio or external call. So problem fixed though I have no idea how exactly.

There is something interesting though. When the F980060 table started filling up, it got 105 records in 3 seconds and that's all the orchestrations we ran since yesterday. It looks like JDE buffers or caches this somehow until it can be written to the table.

 

[MFreitag]

Somehow the CNC fixed it this morning and now it logs everything, studio or external call. So problem fixed though I have no idea how exactly.

Can you ask them what they did? Might be useful - thanks!

 

[JohnDanter2]

I didn't think ORCH studio calls were logged either.
Same as the step logging thats now available

So I'd like to know what they did too