Use the @PROM_CONSTANTS table to set up the promotion environment (file allocation parameters, rights restrictions, and library names). Edit the table in the Single Occurrence Editor. There should be an occurrence for each TIBCO Object Service Broker location or node name used in the promotion system.
Type a valid TIBCO Object Service Broker location or source node name in the Nodename field. This location has a specific set of promotion environment parameters.
You must identify the type of user access rights allowed on the TIBCO Object Service Broker location in question. Access rights can be set as restricted or non-restricted.
A restrictive environment is appropriate if only one person (user-restrictive) or one group (group-restrictive) is responsible for an object at any given time. Promotion rights are enforced by the tools used to define objects (such as the Table Definer) and edit data (such as the Table Editor). If a developer uses these tools, no one else can modify the object in question as only the developer has rights.
1
The Promotion system uses the following file naming parameters when using external files to store objects associated with each change request:
CH_PREFIX,
SUFFIX, and
ALLOC_DATASET. If the Promotion system operates across multiple systems, these naming parameters must be identical on all systems.
Be aware of any file naming restrictions that apply to the platform where you are operating. For example, in z/OS, data set qualifiers cannot be longer than eight characters and cannot start with a number.
If you are doing external backups or extractions, the qualifiers on the files named in this occurrence of the @PROM_CONSTANTS table should be appropriate to the requirements of the external security system. In particular, the external ID of the administrator (regardless of the level) must have read and write access to the external files used by the Promotion system.
The file or data set name is derived by concatenating the value of CH_PREFIX, the change request number, and the contents of the
SUFFIX field. For example, the data set name for change request number of 1539 would be:
The values of CH_PREFIX and
SUFFIX are used only when change requests originate from
NODENAME. If
NODENAME is not used as a source of change requests, these two fields can contain nulls.
Type Y or N in this field to indicate whether data set pre-allocation is required. This is applicable only where extractions are done for target promotions. A z/OS platform must be set to Y; platforms other than z/OS must be set to N.
Specify the library that is to receive the rules that a change request includes. This would be the installation rules library that is, by default, SITE. Rules marked for deletion in a change request are removed from the specified library, along with rules extracted for a consolidated change.
The Promotion system uses the settings in the fields below to identify which (if any) messages to save in @PROM_LOGS. These messages are used by the Query Promotions Information option.
Before you can apply maintenance updates (PTFs) to your TIBCO Object Service Broker system, an entry in the @PROM_CONSTANTS table is required. This required occurrence is shipped with each system.
TIBCO Object Service Broker for z/OS Installing and Operating or
TIBCO Object Service Broker for Open Systems Installing and Operating for your operating environment for more information about maintenance updates and the @PROM_CONSTANTS table.