Best Practice Implementation › How to Perform the Best Practice Implementation › BPI Software Inventory Lifecycle › Configuration Tables

Configuration Tables

CA Endevor SCM configuration table source are delivered in the iprfx.iqual.CSIQSRC deployment library. New C1DEFLTS and ESYMBOLS configuration table source is built by the BPI process, based on information specified in the table input members located in the BPIDATA data set and information specified in the #OPTION member located in the BPILIB data set. None of the other configuration table source is altered by the BPI process.

• BPI job #1TABLES builds the two new tables and creates load modules for the C1DEFLTS, ENCOPTBL, ENDICNFG and ESYMBOLS tables.
• BPI job #3ADMIN builds an inventory location for the tables (ADMIN/ADMIN/ENDEVOR/TABLE/2) and adds and promotes all the configuration tables to that location.

You can modify the source as required after the implementation is complete.

Note: When performing the Best Practice Implementation, we recommend that you set the WARN parameter to YES in the CA Endevor SCM configuration table, BC1TNEQU. When WARN=YES, the ESI warning mode is in effect. Warning mode allows access to resources even if your site security package (RACF, CA ACF2, or CA Top Secret) indicates that access should be denied. You should use ESI Warning Mode when running the Best Practice Implementation. System Management Facility (SMF) messages will indicate any authorization issues with data sets, but will not halt the BPI implementation process. After running the implementation process, you can adjust your security rules and change the WARN parameter to NO, if you prefer not to run CA Endevor SCM in warning mode. For more information about the WARN parameter, see The ESI Warning Mode in the Security Guide.