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

Inventory Structure

The CA Endevor SCM inventory structure allows you to do the following:

• Work with program modules without having to know where they are physically located, or how they are compiled.
• List all the program components that make up an application, regardless of type.
• Determine the locations of an element simply by entering the element name on a display screen.
• Act on a cross section of your program inventory. For example, CA Endevor SCM allows you to list all COBOL code in your shop, or promote an entire new release of the payroll application with a single command.

With the BPI, a predefined inventory structure is included. The structure (environments, systems, subsystems, types, and so on) is outlined in rows within table file members.

Understanding the Inventory Structure components

The BPI provides the following default definitions for the inventory structure components.

Environments

The default environment names are delivered in the BPI input table, T#ENVMTS. Each data row consists of the environment name and stage information.

Note: BPI REXX member, O#ENVMTS located in BPILIB must be kept in sync with T#ENVMTS.

The rows in these tables are used to build the software change lifecycle (established within the C1DEFLTS table), the CA Endevor SCM configuration tables, and to build SCL members. You specify what environments you want to create, the environment stage names, and the entry stage for that environment. Also, you specify how the these are mapped— the next environment to map to and the next stage of that environment to map to.

Systems

The default system names are delivered in members T#ADMSYS and T#SYSTMS. Each data row consists of a system name and a description. T#ADMSYS is used solely for the ADMIN environment. The ADMIN environment, as delivered, will contain one system and subsystem. It is required that you keep the administrative environment. The BPI defaults to creating the first ADMIN system specified in T#ADMSUB as the main repository of all the CA Endevor SCM processors and configuration tables that the remaining application systems use. The system name for the Processor Output Libraries will default to the first system specified in T#ADMSYS. You may choose to add additional systems to the ADMIN environment, by adding additional rows to the T#ADMSYS table.

T#SYSTMS table is used by all the environments defined in the T#ENVMTS table except for Administrator and Unclaimed environments. That includes the Development, Quality Assurance, Production, Emergency, and Archive environments in the delivered table.

This T#SYSTMS table is related to the T#SUBSYS table. If you add or remove a system row from the T#SYSTMS table, you must add or remove the associated row(s) in the T#SUBSYS table.

The system definition defaults delivered with the BPI are listed below:

• Next System – defaults to the current system
• Comments Required
• CCID Required
• Duplicate Element Check is Not Active
• Duplicate Processor Output Check is Active— Severity Level is ‘E’
• Element Jump Acknowledgment Required
• Signout is Active
• Signout Dataset Validation is Not Active

Subsystems

The default subsystem names are delivered in members T#ADMSUB and T#SUBSYS. Each row consists of a system name, subsystem name and a description. Any system specified in T#SUBSYS must match a system specified in T#SYSTMS. Any system specified in T#ADMSUB must match a system specified in T#ADMSYS

The delivered subsystem definition specifies that the Next Subsystem defaults to the current subsystem.

Types

The default type names are delivered in members T#ADMTYP and T#TYPES. The T#ADMTYP member is used to define types for the Administrator environment and the T#TYPES member is used to define types for the Development, Quality Assurance, Production, Emergency, Unclaimed, and Archive environments. The length of the data in each row of these members is 200 characters. Each row consists of a type name, processor group name, generate, move and delete processor names, foreground allowed flag, language, panvalet and librarian source languages, compare from and compare to columns, element delta format, and type and processor group descriptions. When a type is defined during the BPI process, the first processor group listed for each type will be the default processor group.

Note: If the BPI process is executed and your site did not purchase the Extended Processor option, the implementation will fail at the point when the DEFINE TYPE PROCESS action is executed. The execution of this action will result in a return code of 12 when CA Endevor SCM performs a check against the PROC parameter value in the C1DEFLTS configuration table and determines this option is not activated.

The type definition defaults delivered with the BPI are listed below:

• Do Not Expand Includes
• Element Delta Format is Reverse
• Do Not Compress Base
• Regression Threshold is 80
• Regression Severity is Caution
• Do Not Consolidate Element Levels
• Consolidate Elements at Level 96
• Number of Element Levels to Consolidate 0
• Do Not Consolidate Components Levels
• Consolidate Components at Level 96
• Component Delta Format Reverse
• Number of Component Levels to Consolidate 0
• HFS Recfm NL

Note: The Regression Percentage Threshold is automatically set to 80, except for LOG or IMAGE delta formats, where it is set to 0.

Processor Groups

The processor group and processor names are included in members T#ADMTYP and T#TYPES along with the type attributes.

One exception to the naming standard is for the special Endevor processor group used by the type PROCESS. The name of this processor group is PROCESS.

The processor group definition defaults delivered with the BPI are listed below:

• Move Action Uses Move Processor
  • If the entry stage of the environment is stage 1, then it will use the Generate processor. The production environment will always use the Move processor
• Transfer Action Uses Move Processor
• Allow or Do Not Allow Foreground Execution
  • The Allow or Do Not Allow is specified in the T#ADMTYP and T#TYPES table. The Unclaimed and Archive environments will use Allow for all types
• Processor Output Type
• Generate/Move/Delete Processors
  • The processor names will be taken from the T#TYPES table, except for type PROCESS, which will always use the Endevor processor names. The Unclaimed and Archive environments set all processor values to *NOPROC* for all types

Processor Symbols

Processor group symbol overrides are created in #3ADMIN and #9DEFGRP, to coincide with the delivered BPI processors in CSIQSAMP. There are two tables within the #3ADMIN JCL that define what symbols need to be created for the administrator environment. The standard environments use the T#SYMBLS table. Processor symbols can be a length of eight characters and the override values can be up to 65 characters. As delivered, there are processor symbol overrides required since a single processor is shared across multiple processor groups. You will have the flexibility to change or add to the delivered processor symbol definitions by editing #3ADMIN or T#SYMBLS.

The processor symbols definition defaults delivered with the BPI are listed below: