Best Practice Implementation › How to Perform the Best Practice Implementation › Run BPISTART

Run BPISTART

To start the Best Practice Implementation, you edit and submit the job, BPISTART.

Follow these steps:

1. Set the WARN parameter to YES in the CA Endevor SCM configuration table, BC1TNEQU.

   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.

2. Locate BPISTART in the iprfx.iqual.CSIQJCL library.
3. (Optional) Edit the SET LBPRFX=uprfx.uqual statement in BPISTART to override the uprfx and uqual values specified in the BC1JJB03 installation job.
4. Add a valid job card statement and submit the BPISTART job for execution.

   This job does the following:

   • Allocates the BPI libraries: uprfx.uqual.BPIDATA, uprfx.uqual.BPILIB, uprfx.uqual.BPIPRCR, and uprfx.uqual.BPIWRK.

     Note: These libraries will be modified during the BPI process. The delivered libraries will not be modified and thus will be available for backup if the BPI process needs to be restarted for any reason.

   • Copies delivered and tailored members into the BPIDATA, BPILIB and BPIPRCR libraries.

   The following libraries are created with the uprfx.uqual values specified in the BPISTART job:

   • uprfx.uqual.BPIDATA— Contains all the default input table members. This is a copy of the iprfx.iqual.CSIQDATA library. These tables are used to define the inventory structure (environments, systems, subsystems, types, processor groups, and so on.) to the BPI process jobs.
   • uprfx.uqual.BPILIB— Contains several members copied from other installation libraries, JCL members built by the BPI process such as job #1TABLES - #9DEFTYP and several other files that are built by the BPI process, including the C1DEFLTS and ESYMBOLS configuration table source. This is the library the user works from to execute the BPI process jobs.
   • uprfx.uqual.BPIPRCR— Contains the source for the delivered BPI CA Endevor SCM processors. They are added into the Administrator environment by the #3ADMIN BPI job.
   • uprfx.uqual.BPIWRK— Contains temporary and intermediate members built by one of the BPI jobs or steps and passed to another job or step later in the process. Examples include the SCL built by the process to DEFINE SYSTEMs and SUBSYSTEMs. Other members are placed into this library for support purposes in case any issues arise.