Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 The Action Statements : SCHEDULE Statement

SCHEDULE Statement
The SCHEDULE statement enables asynchronous processing to take place. The SCHEDULE statement uses an instance of the @SCHEDULEMODEL table to run a named rule using z/OS JCL, Windows batch programs, or Solaris or scripts.
Usage Notes
If you are using TIBCO Object Service Broker for z/OS, you can use the TO clause to schedule a rule to be sent to a queue for later processing.
By not including the TO clause, you can submit an instance of the @SCHEDULEMODEL table for immediate processing by the operating system.
Refer to Chapter 17, Processing Asynchronously in Batch Mode for information about the @SCHEDULEMODEL table and batch processing.
For the Open Systems platforms, the SCHEDULE statement automatically wraps, within single quotation marks, values that contain spaces or that have a length of zero. The substitution value for a zero-length string continues to be two single quotation marks.
Exceptions
 
Examples
1.
2.
About the Examples
Example 1 submits the PRINT_INVOICE rule immediately for batch processing. The value for its one argument is provided by the INVOICE# field of the INPUT table.
Example 2 send the CLEANUP rule to a queue called WEEKEND. This rule has one argument called LOCATION, and its value is provided by the CITY field of the INPUT table.
See Also
TIBCO Object Service Broker for z/OS Installing and Operating about the use of queues.
TIBCO Object Service Broker for Open Systems Installing and Operating about post installation steps on Solaris for the SCHEDULE statement.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved