Predefining CCIDs

Predefining CCIDs allows you to perform the following:

Validate CCIDs entered by users against the predefined CCIDs.
Associate user IDs or specific inventory areas with certain CCIDs.

You can predefine CCIDs in one of the following ways:

Define a CCID definition data set within CA Endevor SCM.
Use a product such as IBM Tivoli Information Management for z/OS; CA Endevor SCM provides an interface for this product.
Create your own file; CA Endevor SCM provides a user exit capability so you can define your own CCID definition file.

This section contains information about CCID validation in CA Endevor SCM and about the CCID definition data set that you can define within CA Endevor SCM.

CCID Validation

If you have predefined CCIDs, the CCID definition file is read into memory at CA Endevor SCM start-up. Any changes made to the definition file during a CA Endevor SCM work session do not take effect until you exit CA Endevor SCM and then re-enter the system.

CCID validation processing takes effect at the time an action is performed. That is, a batch action could be built (using the batch or package construction screens), but denied at execution time.

If the system you are working with is defined with CCID required, then a valid CCID must be specified for all actions requiring a CCID. If the system you are working with is not defined with CCID required, then the CCID will not be validated and any value including no CCID (spaces) for the action is allowed.

CCID validation applies only to specific actions. This processing is not applicable with the LIST or PRINT actions, because you cannot specify a CCID for these actions. In addition, CCID validation is not performed for the MERGE action.

Note: CCID validation performed by CA Endevor SCM can be used as a secondary validation mechanism that is invoked if a no match condition is found in the CA Endevor SCM InfoMan Interface. For more information, see the InfoMan Interface Administration Guide.

CCID Definition Data Set

You can define and maintain CCIDs in a sequential file that you identify in the Defaults Table. This file is optional. It allows you to predefine CCIDs and associate each CCID, if you choose, with user IDs and/or CA Endevor SCM inventory areas.

When a CCID is specified in a CA Endevor SCM action, CA Endevor SCM validates that CCID against the contents of this data set. It determines whether or not the user is authorized to use the specified CCID in conjunction with the inventory area against which the action is being performed.

You must maintain the definition file using either the ISPF (or any other) text editor or by creating the file from your existing project management system. The definition file must be a card-image data set (80-byte, fixed-format records).

The format of the records in the CCID definition file is variable; the records may be comments ("comment lines") or definitions ("definition lines"). CCIDs are required on every definition line; optionally, a TSO user and/or CA Endevor SCM element identification information (environment, system, subsystem, element name, type, and stage) can be given.

Create a CCID Definition Data Set

To create a CCID definition data set

Specify a CCID data set name in the Defaults Table.
Note: When you create the sequential file, be sure to specify a data set name in the format: project.dataset.type, where type is a unique value. This causes the ISPF editor to use a unique profile for the data set.
Allocate that data set (using standard ISPF data set utilities).
Initialize the data set by copying member SAMPCIPO from the iprfx.iqual.CSIQJCL library into the allocated data set.
SAMPCIPO is a sample CCID definition data set that is distributed with the CA Endevor SCM system. You can use SAMPCIPO to build a data set appropriate to the needs of your organization.

The Purpose of a Sequential Data Set

There are two reasons why a sequential data set is used for CCID definition:

A sequential data set allows you to use the standard ISPF text editor for editing.
A sequential data set allows you to off-load project management information from an existing application (such as IBM Tivoli Information Management for z/OS) and construct the data set using an application program.

Note: To assist in the building of the application program, an assembler macro has been supplied with the system. The macro can be found in the installation source library (iprfx.iqual.CSIQOPTN) built during Step 1 of the CA Endevor SCM installation process. The member name of the macro is $CIPOREC.

If you want to write a program to create a CCID definition data set, use the record layout specified in $CIPOREC, using your own data.

Editing the File Using the ISPF Text Editor

Setting up a CCID definition file as a sequential file allows you to use the ISPF text editor to edit the file, as follows.

First, enter the following primary commands:

TABS ON; CAPS ON; NULLS OFF

Second, set your tab positions as follows:

This figure illustrates how tab positions should be set to edit a CCID definition file.

Using the CCID Definition Data Set

The CCID definition data set can be used for the following:

To register the names of CCIDs. The CCID definition data set can also contain user and/or element identification data.
As a secondary or backup CCID validation mechanism, in conjunction with the CA Endevor SCM InfoMan interface.
If a CCID gets a "no match" condition from the CA Endevor SCM InfoMan interface, CA Endevor SCM uses the CCID definition data set to check further. If the interface recognizes the CCID, then CA Endevor SCM bypasses the CCID check.

Using the CCID definition feature with this additional information can assist you in project management. You can create multiple lines in the CCID definition data set for each valid CCID. For a given CCID value, these successive lines specify either the users allowed to work under this CCID, the inventory items/areas which may be worked on, or both.

For example, assume that a site has two projects: TAX-CHNG-89 and NEW-COMPPLAN. Only people in the Development Department (TSO user IDs: DEVxxx) are allowed to perform changes as part of these projects. The inventory areas for the changes are as follows:

Environment = DEMO
Stage number = 1
Systems for TAX-CHNG-89 = PAYROLL and ACCOUNTG
Systems for NEW-COMPPLAN = PAYROLL and PERSONEL

The CCID definition file would be coded as:

This figure illustrates how to code a CCID definition file.

Sample CCID Definition Data Set

The following is a sample CCID definition data set.

This figure illustrates a sample CCID definition data set.

The following coding conventions apply to this data set:

Any line that begins with an asterisk (*) in column 1 is considered a comment line.
Every non-comment line is considered a definition line, and must specify a CCID. The CCID field is always required.
All other fields on a definition line are optional. If any field is left blank (such as the SUBSYSTEM field for the first five lines listed in the previous sample), it is ignored.
Name masks (for example, ZSX* or simply * in the previous sample) can be used in any of the optional fields. Imbedded asterisks are not allowed.

A description of each field and its card position are shown in the data set that follows:

CCID (3): The name of the CCID. The name must be fully specified, defining a valid CCID. This value must be specified on every definition line. The same CCID may appear on multiple lines.
Userid (16): (Optional) If used, only the users whose user ID is specified (whether by full name or with the use of a name mask) may use the CCID indicated on this line.
Environ (25): (Optional) Environment name. If used, only elements in the environment specified (whether by full name or with the use of a name mask) can be updated under the CCID indicated on this line.
# (34): (Optional) Stage number. If used, only elements in the stage specified (either 1, 2, or *) can be updated under the CCID indicated on this line.
System (36): (Optional) System name. If used, only elements in the system specified (whether by full name or with the use of a name mask) can be updated under the CCID indicated on this line.
Subsys (45): (Optional) Subsystem name. If used, only elements in the subsystem specified (whether by full name or with the use of a name mask) can be updated under the CCID indicated on this line.
Type (54): (Optional) Element type. If used, only elements of the type specified (whether by full name or with the use of a name mask) can be updated under the CCID indicated on this line.
Element (63): (Optional) Element name. If used, only elements whose names are specified (whether by full name or with the use of a name mask) can be updated under the CCID indicated on this line.