![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Managing change requests involves more than promotion. The following are additional tasks that could be required:You must consider the preparation requirements for each change request that is eligible for promotion.When you select the Manage Accepted Requests option from the Remote Promotions menu, a screen similar to the one below appears.
The various line commands available on this screen and their use are explained in the remaining sections of this chapter.You can use any Object Manager primary commands to vary the displayed list. Refer to TIBCO Object Service Broker Getting Started for more information on standard primary commands and PF key usage.When you unaccept a change request, you return it to the control of its creator. If applicable, the change request can be re-submitted when the problem or situation is resolved.To return a change request to its developer, type U (unaccept) and press Enter at the command line. The status of the change request becomes U (unaccepted).If you are running TIBCO Object Service Broker on a z/OS platform, you must allocate your data sets before promoting your change requests. This must be done before you use any of the following functions:
•
• To allocate your files, type S (allocate) and press Enter at the command line. The status of the change request remains unchanged.Altering the backup parameters affects the TDS data to be impacted by the change request. For general information about backups, refer to Chapter 2, Preparing For Promotions.To alter the backup parameters for the change request you selected, type K (backup) and press Enter at the command line. Refer to Chapter 3, Source Promotions for details on this process.
Without a backup, you cannot back out changes to table data due to a promotion.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |