Batch - Maximum Error Parameter Is Always Treated As A Required Field Even If It Is Not. (Doc ID 605536.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Utilities Framework - Version: 2.1.0 and later   [Release: 2.1 and later ]
Information in this document applies to any platform.

Symptoms

The Maximum Error parameter (for a batch program) is always treated as a required field even if it is
optional. This causes the batch program to raise an error when the Maximum Error parameter does
not have a value and halts the current run.

Note: This error occurs when executing the batch using the interactive batch run method. However,
this error is not raised when running the batch program through the batch submission page.

ERROR
Category: 11001
Number: 101
Text: Message Parameter Text field missing
Description: A mandatory field has been left blank. Please enter a value and retry your request.

STEPS
The issue can be reproduced at will with the following steps:
1. Run a batch program using the interactive batch run (calling the PRM file).
2. Make sure that the PRM file has a MAX_ERROR parameter and enter a null / blank value.
3. Ensure Batch Control Parameter from the Batch Control Page has the Maximum Error parameter set to optional.
4. Run the Batch Program by calling the splbatch.cmd from the console.

Cause

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