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


Chapter 4 Understanding Journal Processing : Spinning Journals Using Batch Jobs

Spinning Journals Using Batch Jobs
By default, journal spins are executed as batch jobs and are generally used by those who are not authorized to use started tasks.
Recommendation
If you decide to execute your journal spins as batch jobs, it is recommended that you use a cataloged procedure for the spin JCL. There are two benefits to using cataloged procedures:
If you have multiple TIBCO Object Service Broker systems, you can keep all your journal spin procedures in one central procedure library.
Customization
Complete the following steps:
1.
Specify the data set name from which spin jobs are submitted by entering the name as a value in the SPINDSNAME Data Object Broker parameter.
It must be an existing partitioned data set containing member names set by the SPINMEMBER parameter.
2.
3.
JCL for journals 1 and 2 is located in members SPIN01, SPIN02, and others of the JCL data set.
4.
By default, the SPINOPTION Data Object Broker parameter is set to JOB. When the Data Object Broker starts up, it reads and stores in memory the spin JCL from a data set specified in the SPINDSNAME parameter and members specified in the SPINMEMBER parameter. When a spin is triggered, the saved spin JCL is submitted to the system by the internal reader.
See Also
TIBCO Object Service Broker Parameters for more information about Data Object Broker parameters.
TIBCO Object Service Broker for z/OS Utilities for more information about S6BSPJEX and its required parameters.

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