![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
With this procedure, you can move your Data Object Broker data sets from one type of DASD device to another, while maintaining data integrity and preventing loss of data.
• Determine whether there are in-doubt transactions pending confirmation from external service providers. To do this, use the S6BTLADM (Administration Menu) utility. Clear all pending transactions prior to migrating to new DASD.Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about the Administration menu.
• For all the Data Object Broker system files including the Pagestore Segment 0 and the Audit Log segment, you must bring the Data Object Broker down with a normal, successful shutdown. If the shutdown terminates abnormally, restart and shut down the Data Object Broker until you get a normal, successful shutdown.
• For the user-data Pagestore segments (those segments other than Segment 0 and the Audit Log segment), you can simply vary offline the segments to be moved.
•
Format/ Restore Allocate with The Data Object Broker must be successfully shut down. The Data Object Broker must be successfully shut down. The Data Object Broker must be successfully shut down. Contingency log The Data Object Broker must be successfully shut down. Does not require formatting if recovery of data set from backup is performed. There must be no pointer check errors.Use only provided backup and restore utilities.The Data Object Broker must be successfully shut down (Segment 0 and ACCESSLOG segment) or segments must be varied offline (user-data segments).If the Data Object Broker terminated successfully with all pending transactions cleared, you can do the following, according to the detail that follows:
• You can delete the CACHEx, REDOLOG, JRNLx, and contingency log data sets, then reallocate and reformat them on a new device.
• You can back up the RESOURCE data set and the data sets for the Pagestore segment 0 and ACCESSLOG segment and restore them to the new device.
If the Data Object Broker did not shutdown successfully, do not attempt to migrate any data sets to new DASD. If you do, data integrity problems can occur.
When the Data Object Broker is shutdown normally, you can delete and reallocate these data sets with IEFBR14. Re‑initialize the data sets using the S6BTLFCA utility. You must also delete, reallocate, and reformat the redolog.
When the Data Object Broker is shutdown normally, you can delete and reallocate a new redolog data set. Use the S6BTLFRL utility to reformat the new data set. You must also delete, reallocate, and reformat the cache data sets.
When the Data Object Broker is shutdown normally, you can run SPINxx jobs to copy any data held within the journal data sets. At this point, you can delete the old journal data sets and allocate new data sets using IDCAMS. Alternatively, you can perform new backups of all segment data sets and simply delete and redefine the new journals.
Use the S6BTLADM (Administration Menu) utility to determine if in-doubt transactions are pending confirmation from external service providers. Clear all pending transactions and shut down the Data Object Broker (ensuring a successful shutdown) prior to migrating to the new device. Refer to TIBCO Object Service Broker for z/OS Installing and Operating for information about the Administration menu.
The S6BTLBRM (Resource Management Online Backup) utility (if the Data Object Broker is running); IDCAMS (if the Data Object Broker is down) Restore with You can use the S6BTLBRM utility to backup the contents of the online resource file to a flat file. If the Data Object Broker is not running, you can use the IDCAMS REPRO command to copy the contents to a flat file. In either case, the flat file should be RECFM=FB with a LRECL=128.You can use the IDCAMS DELETE and DEFINE cluster commands in the JCL sample (S6A6POST in the OSB.INSTALL data set) as guides to deleting and reallocating this file to another volume. Run the equivalent of JCL in the RESTRSCE member in the JCL data set to restore your resource data set from your previous backup, which was taken using either the S6BTLBRM utility or IDCAMS.
The S6BTLUPS (Unload Page Data Set to Backup) utility, which you can run in parallel under many jobs to speed up backups. Restore with When the Data Object Broker is shutdown normally, you can perform the procedure in Pagestore Migration.
The S6BTLUPS (Unload Page Data Set to Backup) utility, which you can run in parallel under many jobs to speed up backups. Restore with After varying offline the segments you want to move or shutting down the Data Object Broker normally, you can perform the procedure that follows.
1. Take a backup of the segment whose data files you want to migrate, using one of the S6BTLBPS (Back Up Page Data Sets) utility or the S6BTLUPS (Unload a Page Data Set to Backup) utility.
2. If using the S6BTLUPS utility, consolidate the backup images using the equivalent of a SORT/MERGE step.You must do this because each backup invocation can create a separate backup data set. You must consolidate these data sets into a standard, single, backup data set sorted by segment, page number, and so on. See step #4. in Steps in the Continuous Backup Illustration for details.
4. If problems are reported by the S6BBRPTR utility, correct the errors before proceeding. Take another backup and run the S6BBRPTR utility again. Validation of the integrity of your data files, can require running the S6BBRPTR utility more than once.
7. Restore the data sets using the previous clean backup from step #1. or step #4. using the S6BTLRPS (Restore TDS Segment) utility.
Utilities such as IDCAMS are incompatible with the structure of the Pagestore data sets. You must not use them to move or reformat the page data sets. These data sets cannot be processed at the VSAM logical record level.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |