![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
If started task programs are available to you, this approach is recommended for submitting journal spins because the spin can always execute immediately.
If you decide to use the started task approach and want to offload your journal directly to tape, first ensure that started tasks can issue tape mounts at your site.
2. Specify the name of your started task procedure in the SPINMEMBER Data Object Broker parameter.
3. Customize the SPINxx and SPINSTC members in the JCL data set with OSEMOD to reflect your installation's naming convention. If you are using a started task (SPINOPTION=STC) rather than jobs (SPINOPTION=JOB) for your spins, you must copy the sample SPINSTC member into a data set that is part of your z/OS system PROCLIB concatenation. z/OS will search this concatenation when the Data Object Broker requests a started task journal spin.
The name of the journal spin started task procedure that is being invoked.You must use the sample SPINSTC member in the JCL data set distributed with TIBCO Object Service Broker, and modify it to specify a symbolic JRNLDSN parameter on the EXEC statement. When the Data Object Broker issues the START command to invoke spin processing, the journal data set name specified in the command line is passed to the started task and the appropriate journal data set is offloaded.TIBCO Object Service Broker Parameters for more information about these parameters.TIBCO Object Service Broker for z/OS Installing and Operating for more information about operator commands.TIBCO Object Service Broker for z/OS Utilities for more information about S6BSPJEX and its required parameters.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |