![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
If a segment is nearing its data capacity, you can use one of two procedures to add one or more page data sets to the segment:
1. Use backup and restore utilities along with segment balance. This is the recommended method especially if the segment has many tables.TIBCO Object Service Broker for z/OS Utilities and TIBCO Object Service Broker for z/OS Managing Backup and Recovery for specific information about the utilities mentioned in the following sections.From the system console, issue the following command replacing nn with the segment number:
1. Edit the JCL for S6BTLBPS (Backup Page Data Sets utility) and change the SEG#=0 parameter to indicate the segment to be backed up.Task C Verify the backup is goodUse S6BBRPTR (Batch Pointer Check utility) to check the backup. If any errors are detected, correct the problems before continuing. Once you have obtained a clean backup, save the backup for the expansion of the segment and recovery, in case it is needed.
1. Edit the JCL for S6BBRPTR and change PARM=’SEGMENT=01,HDR’ to the segment number that is being processed.
2. In the same JCL, change the //BACKUP DD statement to point to the backup created in Task B.
1. Edit OSB.INSTALL(S6A5DBDG) to increase the number of data sets by incrementing the ACBS=n parameter for the segment.
1.
2. Create a job OSB.INSTALL(S6A3ATMP) modelled after OSB.INSTALL(S6A3ALOC) and include only 1 IDCAMS step that contains the new DEFINE CLUSTER statements:
4. Using the JCL in OSB.INSTALL(S6A5FRMT) as a model, create a member OSB.INSTALL(S6A5FTMP) to format the segment's data sets using the S6BTLFPS utility. Include a DD statement for each new page data set within the segment:
Task G Verify the expanded data set
At this point the expanded segment can be used by the Data Object Broker by skipping to Task M, Shutdown the Data Object Broker; however, we recommend that S6BBRBAL (Segment Balance utility) be used to balance the data across all the segment's page data sets. This will distribute I/O for new data across all page data sets, yielding better performance.S6BBRBAL (Segment Balance utility) takes your backup and creates a new backup data set reflecting evenly populated page data sets.
1. Edit the JCL for S6BBRBAL by customizing the PARM settings and data set names for DD statements NEWARC and OLDARC.Task I Verify the balanced segment
1. Edit the OSB.INSTALL(S6A3ATMP) member created in Modify your segment allocations and change the IDCAMS SYSIN statement to point to OSB.INSTALL(SPLXSEGn) or OSB.INSTALL(SPLXSGnn). This defines the data sets comprising the segment being expanded.
2. Ensure that this job only contains one step and that the member contains DELETE and DEFINE CLUSTER statements for all existing and new segment page data sets.
4. Edit job OSB.INSTALL(S6A5FTMP) from Task E, Modify your segment allocations and include //DD1,2,,,n DD statements for each page data set in the segment.
1. Edit the JCL for S6BTLRPS changing the PARM='SEG=nn' to specify the segment being restored by S6BTLRPS.
2.
1.
Make sure that you use new backup names so that previous backups are not overwritten. This is especially important for the backup created in Task B, Perform a backup of the segment which is the fallback backup for this entire procedure.
The timestamps created by S6BBRBAL for relocated pages are expressed in UTC. If you are running your system with page time stamping "OFFSET=LOCAL" rather than "OFFSET=UTC", then you must observe the following.
• If your local time is a positive offset from UTC (you are ahead of UTC locally) then you must be very careful to purge old page images that might exist in the spin, merge and if you use continuous backup, the backup files. Restart your continuous backup from a freshly created backup using S6BTLBPS. You may bring the target segments back online immediately after using S6BBRBAL.
• If your local time is a negative offset from UTC (you are behind UTC locally) then you should not bring the target segments back online until the local time has caught up to the UTC at which S6BBRBAL ran. For instance, if your local time is -2 hours from UTC and S6BBRBAL is run at 13:00:00 UTC then you should not bring the segment back online until after 13:00:00 local time (15:00:00 UTC) is reached. Failure to do this may corrupt future continuous backups.Refer to TIBCO Object Service Broker for z/OS Utilities for detailed information concerning recovery and S6BBRBAL.For detailed information about shutting down TIBCO Object Service Broker, refer to TIBCO Object Service Broker for z/OS Installing and Operating.From the system console, issue the command to start the Data Object Broker. You may need to bring the expanded segment online, using DBONLINE. Example:For information about starting TIBCO Object Service Broker, see TIBCO Object Service Broker for z/OS Installing and Operating.Procedure 1: Using Backup and Restore Utilities is the recommended procedure but if your segment does not have many tables you may find it more convenient to use the unload and load utilities instead.From the system console, issue the following command, replacing nn with the segment number:Edit the JCL for S6BTLBPS (Backup Page Data Sets utility) and change the SEG#=0 parameter to indicate the segment to be backed up. Submit the job to create the backup.Use S6BBRPTR (Batch Pointer Check utility) to check the backup. If any errors are detected, correct the problems before continuing. Once you have obtained a clean backup, save the backup for the expansion of the segment and recovery.
1. Edit the JCL for S6BBRPTR and change PARM=’SEGMENT=01,HDR’ to the segment number that is being processed.
2. In the same JCL, change the //BACKUP DD statement to point to the backup created in Task B.Use S6BBRULHB (Batch Unload utility) to unload the table data. For each table to be unloaded from the segment, you must prepare control statement information using the BATCHUNLD_CARDS tool. For details, see TIBCO Object Service Broker Shareable Tools.
1. Edit OSB.INSTALL(S6A5DBDG) to increase the number of data sets by incrementing the ACBS=n parameter for the segment.
1.
2. Create a job OSB.INSTALL(S6A3ATMP) modelled after OSB.INSTALL(S6A3ALOC) and include only 1 IDCAMS step that contains the new DEFINE CLUSTER statements:
4. Using the JCL in OSB.INSTALL(S6A5FRMT) as a model, create a member OSB.INSTALL(S6A5FTMP) to format the segment's data sets using utility S6BTLFPS. Include a DD statement for each new page data set within the segment:
Use S6BBBRTBL (Batch Load utility) to load the table data. For each table to be loaded from the segment, prepare control statement information using the BATCHLOAD_CARDS tool. For details, see TIBCO Object Service Broker Shareable Tools.Edit the JCL for S6BTLBPS (Backup Page Data Sets utility) and change the SEG#=0 parameter to indicate the segment to be backed up. Submit the job to create the backup.Use S6BBRPTR (Batch Pointer Check utility) to check the backup. If errors are detected, correct the problems before continuing. Once you have obtained a clean backup, save the backup for the expansion of the segment and recovery.
1. Edit the JCL for S6BBRPTR and change PARM=’SEGMENT=01,HDR’ to the segment number that is being processed.
2. For details, see TIBCO Object Service Broker for z/OS Installing and Operating.From the system console, issue the command to start the Data Object Broker. You may need to bring the expanded segment online, using DBONLINE. Example:For details, see TIBCO Object Service Broker for z/OS Installing and Operating.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |