The Iterative BPI Process

How to Perform a Best Practices Implementation › How to Perform the Best Practice Implementation › The Iterative BPI Process

The Iterative BPI Process

We recommend that you execute the BPI process in iterations. For the first iteration, you might implement one System (or application). This lets you become familiar with how to edit the input tables and how the jobs work. After the first iteration, you could execute the BPI to implement an entire application (an application can consist of multiple Systems and Subsystems). Then you could do additional iterations for each additional application. For the first iteration, you perform all the steps. For subsequent iterations, you re-edit the BPI input tables and then rerun the jobs beginning with job #5ALLOC.

For the first iteration, do the following:

Submit BPISTART.
Complete all the BPI input tables.
Edit the #JOBCARD.
Edit #OPTION to enable symbolic substitution.
Execute the BPI jobs #0SETUP through #9DEFGRP, and submit the additional jobs that get created.

For the second and subsequent iterations, do the following:

Edit the values in the tables.
Execute BPI jobs #5ALLOC through #9DEFGRP, and submit the additional jobs that get created.
Repeat these steps as many times as needed to add all the Systems you want to put under the control of CA Endevor SCM at this time.

Copyright

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.