Previous Topic: Define Symbol Values for BPI JobsNext Topic: The Iterative BPI Process

Best Practice Implementation › How to Perform the Best Practice Implementation › Submit BPI Jobs

Submit BPI Jobs

You run the BPI as a set of jobs that use information in the input tables and the #OPTION member. The first job you submit is the #0SETUP job, which builds the other jobs that you must submit. All the jobs are located in the BPILIB library and must be run in the specified order. Some of these jobs build additional jobs. These additional jobs are submitted automatically, if the #OPTION member SubmitJob parameter is Y. Submit the jobs to complete the set up.

Follow these steps:

  1. Submit the setup job, #0SETUP.

    Checks for the existence of data sets and builds and tailors additional jobs. This job builds nine additional jobs and saves them into the uprfx.uqual.BPILIB library. This job checks for the existence of the CA Endevor SCM site-wide data sets it is about to allocate. If any of the data sets already exist, the job terminates with a return code of 12 and a report is produced to indicate which of the data sets already exists. The purpose of this check is to ensure the data sets are not accidentally deleted.

    The #0SETUP job also builds additional BPI jobs. Jobs that are built by the setup job are also stored into the BPILIB library. The #JOBCARD you coded is copied to the beginning of each of these jobs.

  2. Submit the #1TABLES job.

    This job builds, assembles and link-edits the C1DEFLTS and ESYMBOLS tables. No additional jobs are created by this job. This job also assembles and link-edits the ENCOPTBL and ENDICNFG configuration tables.

  3. Submit the #2LIBRYS job.

    Allocates Endevor Site-wide Data sets. Builds the global type sequence member and saves it into the PARMLIB. This job builds one additional job.

  4. Submit the #3ADMIN job.

    Creates the entire ADMIN Environment. Adds processors and configuration tables. This job builds four or five additional jobs, depending on the allocation specifications.

  5. Submit the #4UNCLM job.

    Creates the entire UNCLMED Environment. This job builds four or five additional jobs, depending on allocation specifications.

  6. Submit the #5ALLOC job.

    Allocates all Endevor Application Data sets. This job builds additional jobs depending on the number of system/subsystem combinations specified in the T#SUBSYS BPI table.

  7. Submit the #6DEFSYS job.

    Defines Systems for the DEV, QAS, PRD, EMER and ARCHIVE Environments. This job builds one additional job.

  8. Submit the #7DEFSUB job.

    Defines Subsystems for the DEV, QAS, PRD, EMER and ARCHIVE Environments. This job builds one additional job.

  9. Submit the #8DEFTYP job.

    Defines Types for the DEV, QAS, PRD, EMER and ARCHIVE Environments. It will also define Processor Symbols for any of the environments specified. This job builds one additional job.

  10. Submit the #9DEFGRP job.

    Defines processor groups for the DEV, QAS, PRD, EMER and ARCHIVE Environments. It will also define processor symbols for any of the environments specified.

  11. Manually delete the uprfx.uqual.BPIWRK library after every iteration of the BPI process.The BPIWRK data set provides no value once the implementation is complete.