![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
All DASD space requirements are based on single‑density 3390‑type DASD devices. The TIBCO Object Service Broker data sets are placed on devices that fall into two physical groups: non-VSAM data sets and VSAM data sets, over a range of volumes represented by symbolic variables in OSEMOD ($VOLUM01$-$VOLUM15$).Data sets used by TIBCO Object Service Broker online processing are distributed over a number of symbolic volume names to optimize DASD performance. Other performance recommendations are listed below:
• The Data Object Broker consists of six key operational data sets that should be placed on separate DASD for performance and data integrity reasons. They are the MetaStor, redolog, cache, journals, audit log, and contingency log data sets.
• The redolog and cache data sets should be placed on a DASD with low I/O activity. Otherwise these data sets are good candidates for cache DASD controllers.
• Use load balancing channel and device I/O when positioning MetaStor page data sets and journals, since they have high I/O activity.Consider decreasing the default data set sizes for some TIBCO Object Service Broker components due to DASD constraints. The following table lists the space allocations for some components and specifies which member in the CNTL data set to modify. For more information on the CNTL members, refer to Modify Data Sets to Accommodate DASD Constraints.
Default Number of Cylinders (3390 Device) Minimum Number of Cylinders (3390 Device) SPLXSEG1 referenced with last name qualifiers $SEG1NAM$.PAGEx in the DASD space allocation tables. Audit log segment (default: segment 99) SPLXREDO (DPLXREDO for duplex redologs).
If required, use the following tables to further adjust data sets for size and for different devices. The tables contain the following information:
• Column one contains the low-level qualifiers of the TIBCO Object Service Broker data set name.
• Column two contains the CNTL member that allocates the data sets during the install process.
• Column four contains the primary and secondary (3390) space allocation. Data sets allocated in tracks are rounded up to the next cylinder. Totals are computed (not including extents) for symbolic volumes that have more than one data set allocated.
• Column five contains the symbolic DASD volume serial number where you intend to allocate the data sets.
• Column six designates the volume as VSAM or non-VSAM. If you do not need to make this distinction at your site, this designator can be ignored.
Member Name 3390 Default Pri/Sec (CYLS) Symbolic Volume $SEG0NAM$.PAGE1 $SEG1NAM$.PAGE1 $SEG99NAM$.PAGE1 $SEG0NAM$.PAGE2 $SEG0NAM$.PAGE3 $SEG1NAM$.PAGE3 SPLXREDO or DPLXREDO OSRUN or OSRUNSTC
The ARCHLOG data set must reside within a single extent. A block size of half a track is recommended to ensure that you can save the largest group of records expected. For information on estimating size requirements, refer to the OSBTLFAL (Format ARCHLOG) utility in TIBCO Object Service Broker for z/OS Utilities. Before first use, the file must be formatted using OSBTLFAL.
Member Name 3390 Default Pri/Sec (CYLS) Symbolic Volume
Member Name 3390 Default Pri/Sec (CYLS) Symbolic Volume
Member Name 3390 Default Pri/Sec (CYLS) Symbolic Volume non-VSAM (PDSE) non-VSAM (PDSE) non-VSAM (PDSE) The Pagestore consists of up to 256 segments. Each segment has 1 to 128 data sets. A TDS (Table Data Store) data set can hold 507,904 x 4 KB pages. Given these parameters, the potential capacity of a segment is approximately 496 gigabytes.TIBCO Object Service Broker Application Administion and TIBCO Object Service Broker for z/OS Managing Backup and Recovery for more information about segments and modifying the size of your Pagestore.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |