Batch Job Submission Portal

Refer to On-Line Batch Submission for detailed explanations about many feaures of online submisssion.

To view a submitted batch job, use Menu > Tools > Batch Job Submission. You are brought to a query portal with options for searching for a Batch Job Submisssion entry.

Once a batch job submission entry has been selected, you are brought to the maintenance portal to view the selected record.

The inline help provides information about several fields. The following points highlight information about some of the fields that may be visible.

The Batch Job Status indicates the current status of the batch job. Refer to Lifecycle of a Batch Job Submission for more information.

Batch Run information will be displayed if the batch job submisssion has an associated run number. Click the link to navigate to the Batch Run tree.

Batch Business Date is only used for background processes that use a date in their processing. For example, a billing process can use the business date to determine which bill cycles should be downloaded. If this parameter is left blank, the system date is used at the time the background process is executed.

Note: Saving a record on this page does not submit the batch job immediately. A special background process will run periodically to find pending records and submit them. Depending on how often the special process checks for pending records and depending on how many other pending records are in the 'queue', there may be a slight lag in submission time. If the desired execution date/time is close to midnight, it is possible that your batch job will run on the day after you submit it. If you have left the business date blank in this case, keep in mind that your business date would be set to the day after you submit the job.

Batch User is the user ID associated with the run of the background process. It may differ from the user who submitted the batch, as described below. Refer to Parameters Supplied to Background Processes for more information about the significance of the user id.

Note: This field defaults to the ID of the current user when adding a new batch job submisssion entry.

Language is used to access language-specific control table values. For example, error messages are presented in this language code.

If you wish the system to notify you when the batch job is complete, enter your Email Address. Refer to Email Notification for more information.

Note: This field defaults to the email address for the current user, if populated on the user record.

The Desired Execution Date/Time defaults to the current date and time. Override this information if you wish the background process to be executed at some future date and time. Refer to Submitting Jobs in the Future for more information.

Thread Count is used to control whether a background processes is run single threaded or in multiple parallel threads. It contains the total number of threads that have been scheduled. For example, if the process has been set up to run in 20 parallel threads, each of the 20 instances receives a thread count of 20. Refer to Running Multi-threaded Processes for more information about populating this field.

Note: Not all processes may be run multi-threaded. Refer to the description of a batch control to find out if multi-threading is supported.

Thread Number should typically be set to 0. Refer to Running Multi-threaded Processes for situations where populating a value other than 0 are warranted.

The Submission User indicates who initiated the batch job. This value is not populated for timed batch jobs or batch jobs submitted via a scheduler. It is only displayed if the field is populated and the submission user is different to the batch user.

The Submission Method indicates how the batch job was initiated. It is visible in the Record Information section. Valid methods include:

  • Online - populated when a user manually creates or manually duplicates a batch job submission.

  • Generated - populated by algorithms that submit a batch job and by 'initiator' batch jobs that submit other batch jobs.

  • Scheduled - populated by the DBMS scheduler.  Note that for other schedulers, it is not advised to use this value as there may be logic and validation related to records created with this value that may not apply to other schedulers.

  • Timed - populated by the batch daemon that submits timed batch jobs.

  • Other - populated when no other value is provided.

Additional values may be added by your implementation. Refer to the lookup SUBMIT_​METH_​FLG for a list of the submission methods supported by your system.

The following fields are shown in the Additional Run Details section:

Override Nbr Records To Commit and Override Max Timeout Minutes. These parameters are optional and override each background process's Standard Commit Records and Standard Cursor Re-Initiation Minutes. (Each background process's Standard Commit Records / Standard Cursor Re-Initiation Minutes should be documented in the detailed description of the batch control record). Note that Max Timeout Minutes corresponds to the Cursor Re-initiation Minutes.

Fastpath: Refer to Parameters Supplied to Background Processes for more information.

The following trace parameters may also be supplied to a background process and are only used during QA and benchmarking.

  • Trace Program Start Turn on this switch if you wish a message to be written whenever a program is started.

  • Trace Program Exit Turn on this switch if you wish a message to be written whenever a program is exited.

  • Trace SQL Turn on this switch if you wish a message to be written whenever an SQL statement is executed.

  • Trace Output Turn on this switch if you wish a message to be displayed for special information logged by the background process.

Note: The information displayed when the trace output switch is turned on depends on each background process. It is possible that a background process displays no special information for this switch.
Note: The location of the output of this trace information is defined by your system administrator at installation time.

If additional parameters have been defined for this background process on the Batch Control page, the Parameter Name, Description, Parameter Value and an indicator of whether or not the parameter is Required are displayed. A Detailed Description of the parameter can be displayed by clicking the arrow next to the description.

When adding a new batch job submisssion entry, if a default parameter value is configured on the batch control configuration, that value is shown and may be overridden. Note that if the parameter value is configured to be Encrypted on the batch control configuration, the value here will be shown encrypted.

Actions

This page has three special actions.

  • Using the Duplicate button opens a window with the selected batch job submisssion details displayed. These fields, including the batch parameter values, may be overidden. Pressing Save will create a new Batch Job Submission entry.

  • Use the Rerun button to rerun the selected batch job. A window opens displaying the details of the batch job submisssion to be rerun. These fields, including the batch parameter values, may be overidden. Pressing Save will create a rerun Batch Job Submission entry.

    Note: Rerun is only intended to be used for background processes that download information that belongs to given run number. It is typically only required if you need to download an historical run (rather than the latest run).

  • Cancel is only applicable for batch job submisssions that are in Pending or Started status and do not have a submission method of Scheduled . The action is not visible for other statuses.