![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The Data Object Broker can be executed from either a batch job or a started task. You can do further customizations to its operating environment.Data Object Broker initialization parameters are read in at startup. Review each parameter and ensure its value is appropriate for your site. Most parameters should be acceptable as provided.
Use OSRUN to start the Data Object Broker as a batch job. It is identical to S6A8DOB in <HLQ>.<INSTVER>.OSB.JOBS. Customize further as required. Use OSRUNSTC to start the Data Object Broker as a started task. Customize further as required and move it to a system procedure library.
Use USER to log in as a typical TIBCO Object Service Broker user or developer. Customize further as required. Use ADMIN to perform operational functions. Customize further as required. During normal Data Object Broker operations, journal data sets become full and require copying. The process of varying a full journal offline, copying its contents, and resetting its status is referred to as a spin. Journals contain modified data pages that have been checkpointed. The spin process copies pages from the journal to a DASD generation data group. Members SPIN01 and SPIN02 in the JCL data set are used to perform this task. SPIN01 dumps journal 1 and SPIN02 dumps journal 2. Before starting the Data Object Broker, you must customize the JCL that you plan to use to spin the journals. How you modify the JCL is determined by whether you run the spins as batch jobs or as started tasks.
• SPINDSNAME=<HLQNONV>.<INSTVER>.JCL (contains SPIN01 & SPIN02) If SPINxx JCL requires modification, you can shut down and restart the Data Object Broker to make the changes take effect, or you can issue the following Data Object Broker operator command:This refreshes the JCL in memory for the specified journal number without requiring that the Data Object Broker be restarted. The SPINLOADJCL command can be truncated to SPINLOAD. For more information on Data Object Broker operator commands, refer to Commands to Control a Data Object Broker.
Review the PROC and customize further as required. Move it to a system procedure library. If SPINSTC JCL is modified, JCL takes effect the next time a START SPINSTC command is issued The SPINMRG job is automatically submitted by the SPINxx jobs when the GDG limit of the journal spinouts is reached. This limit is set by OSEMOD variable $SPINLIM$, which has a default value of 2. A spinout GDG is created whenever a journal fills up and the corresponding SPINxx job is submitted. For example, with a $SPINLIM$ default of 2, SPIN01 runs when journal 1 fills up then SPIN02 runs when journal 2 fills up. Job SPIN02 will then release SPINMRG.
BKUPCON is released by a SPINMRG job. It is verified in Chapter 3, Performing Postinstallation Tasks.
The S6BBRHDW member in the JCL data set contains JCL to run the S6BBRHDW (CPU Capabilities Report) utility, to report on the availability of the hardware instructions required to run TIBCO Object Service Broker for z/OS.Produce the CPU Capabilities Report. It should end with RC=0. If the report shows that your system is missing instructions, then it will have some restrictions in running this version of the software; contact TIBCO Support to resolve the issue.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |