TIBCO Object Service Broker stores physical database descriptions and configuration data in a parameter file called DBDLIB. It is a collection of assembler macro calls that you assemble, link edit, and execute to populate the DBDLIB VSAM data set.
By concentrating all physical system information into one control file, TIBCO Object Service Broker can dynamically allocate data sets and work areas. This simplifies JCL and tuning options.
The DBJCL member of the JCL data set contains sample definitions. Part of the member is shown below. In this sample, the first DB statement defines segment 0 (the MetaStor) and the second and third DB statements define additional segments (segment 1 and 99) created as part of the product install.
DB TYPE=PAGE,ACBS=3,Q3=SEG00,SEGNAME=DBSEG0
DB TYPE=PAGE,ACBS=3,Q3=SEG01,SEGNAME=DBSEG1,ID=1
DB TYPE=PAGE,ACBS=1,Q3=SEG99,SEGNAME=DBSEG99,ID=99,SYSTEM=Y