Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Preparing For Promotions : @PROM_CONSTANTS Table

@PROM_CONSTANTS Table
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.
Sample Occurrence NODE123AA of @PROM_CONSTANTS

 
--- SINGLE OCCURRENCE EDITOR ---
EDITING TABLE : @PROM_CONSTANTS
TABLE TYPE : TDS
COMMAND ==>
------------------------------------------------------------------------------
NODENAME : NODE123AA
CH_PREFIX : HURQA.CH
SUFFIX : .UPGRADE
RESTRICT_RIGHTS : U
EXE_LIB : VXPX
DEV_LIB : SITE
ALLOC_DATASET :
SAVE_APPLY_LOG : N
SAVE_BACKOUT_LOG: N
SAVE_EXTRACT_LOG: N
SAVE_REFRESH_LOG: N
PFKEYS: 1=HELP 2=DOCUMENTATION 3=SAVE 12=CANCEL 13=PRINT 22=DELETE

 
Explanations of the various environment parameters follow.
Nodename
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.
Environment Access Rights
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
You could decide to set up restrictive rights at first and then switch over to non-restrictive, or vice-versa.
RESTRICT_RIGHTS Field
Valid values are U, G, and S:
If the developer has the rights on a screen, report, table, table instance, or other object, no one else can modify that object.
In a group-restrictive environment, promotion rights are associated with a library name. The security permissions for a library define the promotions group. If the developer has access to a particular library, they are a member of the promotions group for that library. All members of the promotions group share the rights to the objects associated with that library.
Although one developer has rights to an object, other developers can modify that same object and save their changes. However, they are warned that the promotion rights are held by someone else.
For more information about promotion rights and environment access, refer to Promotion Environment and User Access Considerations.
File Naming Conventions and Data Set Allocation
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.
CH_PREFIX
This field contains the leading filename qualifiers for files that are to hold change requests. On non-z/OS platforms, it is used to create the directory name.
SUFFIX
This field contains the trailing portion of the names for files that are to hold change requests.
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:
USR40.CH1539.UPGRADE
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.
ALLOC_DATASET
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.
Promotion Rules Libraries
EXE_LIB
Specify the library in the target system that is to hold rules specified for execution at the time of the promotion.
DEV_LIB
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.
Promotion Message Logs
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.
PTF Maintenance and the @PROM_CONSTANTS Table
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.
See Also
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.

1
Rules differ from other objects in terms of rights and access to modify objects. Refer to Chapter 9, Promotion Rights for more information.


Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved