Best Practice Implementation › How to Perform the Best Practice Implementation › Review Prerequisites

Review Prerequisites

Before attempting the Best Practice Implementation (BPI), verify that the following prerequisites are complete.

Verify that CA Endevor SCM is properly installed at your site. For more information about the installation steps, see the Installation Tasks for the Systems Programmer in the "Overview" chapter in the Installation Guide. Proper installation has the following requirements:

• The CA Common Services components CA LMP and CAIRIM for product licensing and authorization must be installed and customized.

  Note: The components CAIENF and CAICCI are not required for the BPI. However, these components are required if you want to use CA Endevor SCM with the Concurrent Action Processing feature, the Web Services component, or the companion product CA CMEW. CAIENF and CAICCI can be configured after you complete the BPI.

• NDVRC1 must be authorized.
• BC1JJB03 must have been executed.
• The load modules contained in iprfx.iqual.CSIQAUTH and iprfx.iqual.CSIQAUTU (and optionally iprfx.iqual.CSIQLOAD) must reside in a system-authorized library. You can use one of the following methods to make sure that the load modules are in a system-authorized library:
  • Copy the members from iprfx.iqual.CSIQAUTH and iprfx.iqual.CSIQAUTU libraries to an existing authorized library.
  • Authorize iprfx.iqual.CSIQAUTH and iprfx.iqual.CSIQAUTU.
  • Copy members from iprfx.iqual.CSIQAUTH and iprfx.iqual.CSIQAUTU (and optionally iprfx.iqual.CSIQLOAD) to an existing authorized LINKLIST library.
  • Copy members from iprfx.iqual.CSIQAUTH and iprfx.iqual.CSIQAUTU (and optionally iprfx.iqual.CSIQLOAD) to an existing LPA library.
  • Define the iprfx.iqual.CSIQAUTH and iprfx.iqual.CSIQAUTU (and optionally iprfx.iqual.CSIQLOAD) data sets as LINKLIST or LPA libraries themselves.
• Define CA Endevor SCM to the ISPF Environment.
• If your site has multiple CPUs sharing DASD, you must define queue names. If you are using Unicenter CA-MIM Resource Sharing or IBM Global Resource Serialization (GRS), include the queue names in the appropriate Global Resource Queue Name Table.
• If CA ACF2 is the security software used at your site, modify the TSO Command Limiting Facility to allow ISPTLIB commands (ACMQ, BC1PACMI, ESORT, EONLY, EM, QM, and so on).

The following BPI installation considerations apply depending on how CA Endevor SCM is configured at your site:

• The Best Practice Implementation assumes your site is licensed for the following product options:
  • CA Endevor Extended Processors
  • CA Endevor Automated Configuration
• All steps described in the chapter "Configuring Your Product” in the Installation Guide must be performed. The following exceptions apply to the steps in the Configuring Your Product chapter:
  • If you use LINKLIST or LPA libraries for the CSIQAUTH/CSIQAUTU data sets, you will need to tailor the jobs created by the BPI process prior to submission. Remove, or comment out, the STEPLIB DD statements from the job members created in the BPILIB library before submitting the job.
  • If you use LINKLIST or LPA libraries for the CSIQLOAD data set, you will need to tailor the jobs created by the BPI process prior to submission. Remove, or comment out, the STEPLIB and CONLIB DD statements from the job members created in the BPILIB library before submitting the job.

The person performing the BPI needs the following general knowledge of the mainframe environment and a basic understanding of the CA Endevor SCM.

• You need a working knowledge of the mainframe environment, the z/OS mainframe operating system, the Time Sharing Option facility (TSO), and the Interactive System Productivity Facility (ISPF).
• Become familiar with the basic CA Endevor SCM concepts. For more information, see the Installation Guide and the Administration Guide.
• Become familiar with the Best Practice Implementation concepts. For more information about the BPI concepts, see the BPI Software Inventory Lifecycle.

Note: For more information about terms used in this guide, see the Glossary in the User Guide.