In my oppinion, these new tools for analysing and troubleshooting batch jobs are the most important enhancement we got, talking in day-by-day situations. For us, developers and JDE technicians, to have a tool that can provide dynamic logging or statistics in execution time on server is a big advance.
Three are the main enhancements for Batch processing as follow:
- Audit Data - Detail how a batch job was submitted and statistics when finished
- Dynamic Logging - Turn detailed log on/off while a batch job is processing on server
- Introspection - Display statistics regarding the state of a batch job while it's running
Below a sample screen shots with these features. You may click the picture to zooming in.
Here we have the "Execution Detail" row exit from Work Submitted Jobs to launch the new Audit Detail application for JDE jobs at "P", "D" or "E" status. It's real! I told "P" status!! Let's check:
Once in Execution Detail application, we can chose the following options:
- Introspection Data
- Audit Data
- Processing Options
- Data Selection
- Data Sequencing
- Report Interconnect
- SQL Statement
I'll describe only the options number 1 & 2. Let's start by the number 2:
This is the default screen when we got the Work Submitted Jobs screen, with the difference that we have the options: "Debug Logging Status" and "Introspection Status" as you can see in the picture below. Audit data displays details about how a batch job was submitted and how it completed. Audit information is captured for all UBE's.
This powerful tool allow us to monitor in execution time any Job to get for example the current event, current code line number, last BSFN called. This will improve the tracking for problems, we can now check in real time the execution of a job running on server. I think this breaks a big paradigm in JDE and will allow us to have a more precise diagnostics of the batch flow in case of problem.
Turn the Introspection "ON" while the UBE is running, displays current statistics. Refresh button reload statistics and "Turn Logging On" to generate debug logs, if logging not turned on when UBE was submitted.
Let me know if you want more information about this feature!
In this weekend I'll prepare a post in how to install the OC4J web server in the JDE Demo 9.0.