Best Practice Implementation › How to Perform the Best Practice Implementation › Customize the BPI Input Tables › T#SYMBLS--Symbol Names for All Environments Except ADMIN and UNCLMED

T#SYMBLS--Symbol Names for All Environments Except ADMIN and UNCLMED

The T#SYMBLS table contains all the symbol overrides to be defined for the standard or application environments.

This table contains the symbol overrides to be defined for the standard environments. You must specify the type, processor group, environment, stage, processor type, symbol, and override value for each row in the table. You can wildcard the processor group, environment, and Stg# columns. However, no partial wildcarding is supported for the environment or stage column.

The stage column if wildcarded, will create symbol definitions for stage 1 and stage 2.

The environment column if wildcarded, will create symbol definitions for all environments (DEV, QAS, PRD, EMER) except for ADMIN, UNCLMED, and ARCHIVE. They are excluded because the Administrator environment has symbol creation steps in #3ADMIN, and the Unclaimed and Archive environments set processors to *NOPROC*. However, you may define symbols for any of the environments by creating a unique row for that location in the table, placing the environment name directly in the Envname column. In other words, although the wildcarding feature excludes the Administrator environment, you can still create symbols for that environment using this table, by placing ADMIN in the Envname column.

All symbol definitions with wild carded environments will be created first, followed by specific symbol definitions, allowing for additional flexibility when establishing the symbol rows. There are many processor symbolic overrides being created, as delivered. You can delete or add additional rows to the symbol table as needed.

T#SYSTMS--System Names for Standard or Application Environments

The T#SYSTMS table contains all the environment systems to be implemented. This table comes preset with values from the Endevor Sample Application. All values in the data rows must be entered in upper case character mode except for the description, which can be entered in mixed mode.

This table is related to the T#SUBSYS table. If you add or remove a system row from the T#SYSTMS table, you must add or remove the associated rows in the T#SUBSYS table.

T#TYPES--Types for Non-ADMIN Environments

The T#TYPES table contains the types to be created within the DEV, QAS, PRD, EMER, ARCHIVE and UNCLMED environments.

Do not alter the values in the PROCESS rows. This type is used to hold the CA Endevor SCM processors and must be set to the values provided.

If type definition rows are added or removed from the T#TYPES table, the corresponding row must be added or removed from the T#ALLOC table. The T#GLBSEQ table should also be reviewed to determine if rows must be added or removed from that table.