7.5.4.4 Processing for Batch Start

After establishing the required Java environment and initiating various Java processing activities, the Batch Control Utility does the following:

1. The utility verifies that the provided batch name contains only the characters A-Z, a-z, and 0-9 by querying the KDD_PRCSNG_BATCH table. (See the Table 7-11 table
2. The utility determines whether a batch is running by querying the KDD_PRCSNG_BATCH_CONTROL table. The following table describes the KDD_PRCSNG_BATCH_CONTROL table.

   Table 7-12 KDD_PRCSNG_BATCH_CONTROL Table Contents Column

   Column Name	Description
   PRCSNG_BATCH_ID	Current batch process ID.
   PRCSNG_BATCH_NM	Name of the current batch process.
   DATA_DUMP_DT	Current business day. The Calendar Manager Utility places this information in the table.
   EOD_PRCSNG_BATCH_FL	Flag that indicates whether the batch is an end-of-day process (Y or N).

3. The utility records information about the batch in the KDD_PRCSNG_BATCH_HIST table. This table contains a history of all batches that appear by start date and end date.

   Table 7-13 KDD_PRCSNG_BATCH_HIST Table Contents

   Column Name	Description
   PRCSNG_BATCH_ID	Current batch process ID.
   PRCSNG_BATCH_NM	Name of the current batch process.
   DATA_DUMP_DT	Business day on which the batch ran.
   START_TS	Time that the batch started.
   END_TS	Time that the batch ended (if applicable).
   STATUS_CD	Status code that indicates whether the batch is currently running (RUN) or has finished (FIN).

4. The Batch Control Utility logs a message in the <OFSAAI Installed Directory>/ database/ db_tools/logs/batch_control.log file, stating that the batch process has begun.
   Querying the KDD_PRCSNG_BATCH_HIST table for confirmation that the batch has started displays information similar to that in the following Figure. In the last entry, note the appearance of RUN for STATUS_CD and lack of end time in END_TS.

   Figure 7-2 Sample KDD_PRCSNG_BATCH_HIST Table—Batch Start Status