To schedule a rule for direct batch processing, use the SCHEDULE statement in your rule without the TO clause. This causes an instance from the table @SCHEDULEMODEL to be submitted for processing when the rule is run. The instance submitted can contain any z/OS JCL, Windows batch program, or Solaris script. If the JCL, batch program, or script invokes TIBCO Object Service Broker, the Data Object Broker must be operational.
The @SCHEDULEMODEL table is parameterized by the data parameters OPERATING_SYSTEM and MODELNAME. By default the system searches for the @SCHEDULEMODEL instance that matches your operating system environment and has the name of the scheduled rule as the value for the model name. If this instance does not exist, the *DEFAULT* model for your operating environment, which is one of the models shipped with TIBCO Object Service Broker, is sent for processing.
When you execute the SCHED_RPT25 rule, a search is made for the table instance @SCHEDULEMODEL(
operating system, INCOME_TAX). If it is found, TIBCO Object Service Broker submits it; otherwise, TIBCO Object Service Broker submits the instance @SCHEDULEMODEL
(operating system, *DEFAULT*) for processing.