Follow-Up To Bugs 7317799 And 7317798 (Batch Execution)
Last updated on JULY 15, 2010
Applies to:Oracle Utilities Framework - Version: 2.1.0 to 2.2.0 - Release: 2.1 to 2.2
Information in this document applies to any platform.
A few issues as a follow-up to 7317799 (2.2) and 7317798 (2.1)
1. When a job failed execution, script submitjob did not exit with a non-zero exit code. This made it difficult for job stream control in a batch scheduler.
2. If submitjob or threadpoolworker were started without any command line parameters, a NullPointerException would get thrown.
3. These was a requirement to reference OS environment variables in the properties. Note that this is ONLY for batch – not the system at large.
4. All the system properties should get logged at the start of the run, which would provide valuable information, such as Java version number, platform info, etc., in the event that a failed batch run needs to be investigated.
5. All the logs for batch were spooled to the directory referenced in the SPLOUTPUT environment variable, except for the threadpoolworker log; that went to the SPLSYSTEMLOGS directory and could get overlooked as a source of information. That log file should also be spooled to SPLOUTPUT.
6. The log file name constructed by script submitjob did not contain the batch code. It is possible to run submitjob without specifying a batch code (in which case it will prompt for the batch parameters), but if a batch code is supplied, it should be included in the log file name. For a prompted run, the batch code used for the log file name should be defaulted to a string of the user’s choosing, or “prompt” if not specified
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms