Best Practice Implementation › How to Perform the Best Practice Implementation › Customize the BPI Input Tables › Input Table Format Rules

Input Table Format Rules

When you edit an input table, make sure to conform to the following rules.

• Heading row
  • One heading row (single asterisk in column 1) must exist in each table.
  • The heading row must be coded prior to any data rows.
  • The format of the delivered heading rows must not be changed in any way.
• Data rows
  • All values in the data rows must be entered in upper case mode unless otherwise stated.
  • All values are required unless otherwise stated.
  • The data in the data rows must be placed in the same columns as the field literal in the heading row.
• Comment rows
  • Comment rows can be added anywhere within the table source by placing asterisks in columns 1-2 of a row. When detected the row is ignored.

T#ADMALL--Allocations for Admin Environment

The T#ADMALL table allocates data sets for the ADMIN environment. This table enables the creation of the following data sets for each element type listed in the table.

• One DELTA, LISTLIB, LLISTLIB, LOADLIB, and OBJLIB library for each element type for the ADMIN environment.
• One base library for each element type for each system, subsystem, environment, stage. Each base library has the following name format:

  adminprfx. .&C1SY..&C1SU..&C1EN(1,3)&C1S#.typename 
  

  typename

  Specifies a language version.

Edit this table as follows:

1. Add or remove element type rows to include the language types used at your site. The type names appear in the table Node column.
2. Do not change the type names for PROCESS, TABLE, DELTA, LISTLIB, LLISTLIB, LOADLIB or OBJLIB, because these have a specific meaning to CA Endevor SCM and must not be altered. For these types, unless you are changing the format of the DELTA, LISTLIB, or LLISTLIB libraries, limit your changes to the Sizeunit, Primary, Secondary and Directory.
3. (Optional.) If you want to define ELIB BDAM data sets for DELTA, LISTING, and LLISTING data sets, specify the following values:

   Note: The #OPTION member DELTA and LISTLIB data set format must be the same as the format specified in the T#ADMALL member. By default, the DELTA, LISTLIB and LLISTLIB are created as ELIB BDAM. You can leave them as is, or change them to PDS or PDSE by editing the table.

   Note: For more information about ELIB BDAM data sets, see the Administration Guide.

   • PrimPages—Specifies the number of primary pages for the ELIB initialization program to allocate. The value of this parameter is placed into the ALLOCATE PAGES parameter;

     ALLOCATE PAGES = (&PrimPages,&SecdryPages)
     

   • SecdryPages—Specifies the number of secondary pages for the ELIB initialization program to allocate.. The value of this parameter is placed into the ALLOCATE PAGES parameter;

     ALLOCATE PAGES = (&PrimPages,&SecdryPages)
     

   • ResrvePages—Specifies the number of pages for the ELIB initialization program to reserve. The value of this parameter is placed into the RESERVE PAGES parameter;

     RESERVE PAGES = &ResrvePages
     

   • DirPages—Specifies the number of directory pages for the ELIB initialization program to allocate.. The value of this parameter is placed into the DIRECTORY PAGES parameter;

     DIRECTORY PAGES = &DirPages  
     

Important: The same types must be listed in the T#ADMALL andT#ADMTYP tables. If you add or remove type rows from any of these tables, you must make a corresponding change to the other tables.

T#ADMSUB--SubSystem Names for ADMIN Environment

The T#ADMSUB table specifies the name of the subsystems for the ADMIN environment. The delivered table specifies the following:

• System: ADMIN.
• Subsystem: ENDEVOR.
• Description: CA Endevor SCM tables and processors.

Usually, no change is needed to this table.

Important: The system names must be the same in each of these tables: T#ADMSYS and T#ADMSUB. If you add or remove a system row from the T#ADMSYS table, you must add or remove the associated rows in the T#ADMSUB table.

T#ADMSYS--System Names for ADMIN Environment

This table specifies the ADMIN environment systems to be implemented. The delivered table specifies the following:

• System: ADMIN.
• Description: CA Endevor SCM administration.

The system name is used to build the following processor output libraries.

Important: The first system referenced in the table is used to build the processor output library names.

As delivered the following tables will be built:

adminprfx.ADMIN.PROCESS.ADM1.LOADLIB

adminprfx.ADMIN.PROCESS.ADM1.LISTLIB

adminprfx.ADMIN.PROCESS.ADM2.LOADLIB

adminprfx.ADMIN.PROCESS.ADM2.LISTLIB

system_name

Specifies the name of the system in the ADMIN environment.

Usually, no change is needed to this table.

Important: The system names must be the same in these tables: T#ADMSYS and T#ADMSUB. If you add or remove a system row from the T#ADMSYS table, you must add or remove the associated rows in the T#ADMSUB table.

T#ADMTYP--Types for the ADMIN Environment

This T#ADMTYP table specifies the type definitions to be created in the ADMIN environment.

Edit this table as follows:

1. Add or remove element type rows to include the language types used at your site.
2. Do not change the type names for PROCESS or TABLE, because CA Endevor SCM uses these to hold the CA Endevor SCM processors and configuration tables and these must be set to the values provided.

Important: The first processor group listed for each type is used as the default processor group for that type.

Important: The same types must be listed in the T#ADMALL andT#ADMTYP tables. If you add or remove type rows from any of these tables, you must make a corresponding change to the other tables.

T#ALLOC--Allocations for Non-ADMIN Environments

The T#ALLOC table allocates data sets for all environments except the ADMIN environment. The UNCLMED environment and the PRD environments apply an allocation factor specified in #OPTION to the values specified in this table.

This table enables the creation of the following data sets for each element type defined in the T#TYPES table.

• One DELTA, LISTLIB, LLISTLIB, LOADLIB, and OBJLIB library for each element type for the application or standard environment.
• One base library for each element type for each system, subsystem, environment, stage. Each base library has the following name format:

  aprfx. .&C1SY..&C1SU..&C1EN(1,3)&C1S#.typename 
  

typename

Specifies a language version.

Edit this table as follows:

1. Add or remove element type rows to include the language types used at your site. The type names appear in the table Node column.
2. Do not change the type names for PROCESS, TABLE, DELTA, LISTLIB, LLISTLIB, LOADLIB or OBJLIB, because these have a specific meaning to CA Endevor SCM and must not be altered. For these types, unless you are changing the format of the DELTA, LISTLIB, or LLISTLIB libraries, limit your changes to the Sizeunit, Primary, Secondary and Directory.
3. (Optional.) Specify the following values, if you want to define ELIB BDAM data sets for DELTA, LISTING, and LLISTING data sets: (ELIB BDAM is the default.)
   • PrimPages— Specifies the number of primary pages for the ELIB initialization program to allocate. The value of this parameter is placed into the ALLOCATE PAGES parameter;

     ALLOCATE PAGES = (&PrimPages,&SecdryPages)
     

   • SecdryPages— Specifies the number of secondary pages for the ELIB initialization program to allocate. The value of this parameter is placed into the ALLOCATE PAGES parameter;

     ALLOCATE PAGES = (&PrimPages,&SecdryPages)
     

   • ResrvePages— Specifies the number of pages for the ELIB initialization program to reserve. The value of this parameter is placed into the RESERVE PAGES parameter;

     RESERVE PAGES = &ResrvePages
     

   • DirPages— Specifies the number of directory pages for the ELIB initialization program to allocate.. The value of this parameter is placed into the DIRECTORY PAGES parameter;

     DIRECTORY PAGES = &DirPages  
     

Note: The #OPTION member affects the UNCLMED environment and the PRD environments as follows:

• The ProductionSizeFactor specified in the #OPTION member in the uprfx.uqual.BPILIB library is applied to the production environment allocations, by the #5ALLOC job, when building the allocation statements. For example, if you specify a Primary value of 50 for the ASMPGM base library and the ProductionSizeFactor value is 3, the data set is allocated with 150 primary cylinders. This factor is also applied to the Secondary and Directory columns when processing the production environment. The ProductionSizeFactor is skipped when allocating ELIB DELTAs or LISTINGs.
• The UnclaimedSizeFactor specified in the #OPTION member in the uprfx.uqual.BPILIB library is applied to the unclaimed environment allocations, by the #4UNCLM job, when building the allocation statements. For example, if you specify a Primary value of 40 for the ASMPGM base library and the UnclaimedSizeFactor value is 3, the data set is allocated with 120 primary cylinders. This factor is also applied to the Secondary and Directory columns when processing the unclaimed environment. The UnclaimedSizeFactor is skipped when allocating ELIB DELTAs or LISTINGs.

T#ENVMTS--Environment and Stage Names

The T#ENVMTS table specifies the environments and stages to be created.

As delivered the implementation creates the following environments and stages:

Edit this table as follows:

1. Add or remove environment rows to include the environments used at your site. All values in the data rows must be entered in upper case character mode. The first three characters of the environment name are used to build data set names. Therefore, the first three characters of the names must be unique across environments. If the environment names do not contain three characters, a pad character ($) is added to the environment name when allocating the data sets for that environment.
2. Do not change the environments names for ADMIN, PRD, UNCLMED, or ARCHIVE, unless you have business reason to do so. If you change these, you must also change the name in the O#ENVMTS REXX member, located in the uprfx.uqual.BPILIB data set. The purpose of this member is to identify which of the environments is the administrator, production, unclaimed element and archive element environments.
3. If you decide you do not need the UNCLMED environment, comment out the UNCLMED row in this table prior to executing the #1TABLES job. Job #1TABLES builds the C1DEFLTS table.

   Note: Also skip the execution of the #4UNCLM job.

T#GLBSEQ--Global Type Sequence Member

The T#GLBSEQ table contains the information required to create the global type sequence member, GLBLTYPE in the uprfx.uqual.PARMLIB. CA Endevor SCM uses this PARMLIB member to determine the order of type processing. This table is used in conjunction with the T#ADMTYP and T#TYPES tables. If data rows are added or removed from these tables, the T#GLBSEQ should also be reviewed to see if changes are required.

Only types that must be executed in a specific sequence should be included in this table. Types such as JCL and PROCS should not be included in this table. Following this rule will result in more efficient through put from the current action processing feature.

T#LIBRYS--Allocations for Site-Wide Data Sets

The T#LIBRYS table allocates CA Endevor SCM data sets that are used site-wide. The purpose of this model is to identify the fully qualified names of these data sets. The values in the Node column are used as the last qualifier of the fully qualified data set name as shown next:

• ACMROOT—ACM root and data sets.
• ACMXREF— Cross-reference data sets.
• ELMCATL—element catalog data sets.
• ELMCATL.EINDEX—element catalog index data sets.
• PACKAGE—Package file.
• PARMLIB—Parameter library.
• MCF—Master Control File for each environment-stage combination.

Do not add or remove any rows from this table, however, you should review the type of data set specified in the MODEL column and the data set size attributes.

It is highly recommended that you do not change the Node, MODEL or TBLOUT values in this table. DO NOT change the MCF name. If you have a business reason to change one of the other node names, you must also change the name in the O#LIBRYS REXX model, located in the iprfx.iqual.CSIQCLS0 data set.

T#SUBSYS--Subsystem Names for All Environments Except All Standard or Application Environments

The T#SUBSYS table names the Subsystems for each System and provides a description of each Subsystem for all environments except the ADMIN and UNCLMED environments.

Edit this table as follows:

1. Change the default to the Systems and Subsystems appropriate for your business model.
2. Add or remove corresponding rows in the T#SYSTMS table, if you changed the T#SUBSYS table in step 1.

Note: The default subsystem names match the sample application.