This section describes how to define a new system.
To define a new system, select option 3 on the Environment Options Menu, and press Enter. CA Endevor SCM displays the System Request panel.
From the System Request panel, follow this procedure to define a new system or access an existing system:
Note: For more information about option K, see Cloning System, Subsystem, and Type Definitions.
If an option is not entered, CA Endevor SCM displays a list of the existing systems. You can select a system for editing, press Enter and proceed to step 5.
Note: A different panel, specific to clone processing, is returned if you request clone processing.
The following information illustrates how the use of the System Definition panel varies by processing option:
Display the system definition.
View the system definition and verify that you want to delete it. Press End if you want to cancel the delete request.
Define a new system.
Change an existing system definition.
Once you have entered the necessary information on the panel, press Enter to perform the requested processing.
This section describes the panel fields.
As shown in the following information, the first three fields on the System Definition panel identify the environment:
(Display-only) Name of the current environment.
(Display-only) Name of the next environment on the map.
(Display-only) Name of the current system.
Name of the system this system maps to in the next environment. You can enter or change the name in this field when you access this panel in create or update mode.
Descriptive title for the system (1-50 characters).
(Display-only) This field identifies the date, time, and user ID of the last user to update the system. When creating a new system definition this field is blank.
Note: If you are planning to change system names across your map and to use package component validation, see the Packages Guide for information about the potential impact of these name changes on package component validation functions.
The following information describes the General Options fields:
Indicates whether there must be a comment for actions against this system. Acceptable values are:
Each action must have a comment.
Default. Comments are not required for actions.
Indicates whether there must be CCIDs for actions against this system. Acceptable values are:
Each action must have a CCID.
Default. CCIDs are not required for actions.
Indicates whether users must specify ACKNOWLEDGE ELM JUMP=Y on the Move panel when jumping elements. Acceptable values are:
User must specify ACKNOWLEDGE ELM JUMP=Y.
Default. User does not have to specify ACKNOWLEDGE ELM JUMP=Y.
Note: Jumping occurs when you move an element from one stage to another on a map route, and a version of the element exists at an intermediate stage that is not part of the map route.
The following fields on the System Definition panel identify the auto age level retention options available at the system level. Using these fields, you can activate auto age driven level retention for elements, components, or both.
Indicates whether the element change levels are to be managed by age.
Default. Age managed change levels are not in effect.
Age managed change levels are in effect.
Indicates the length of time, in months, that change levels are to be kept. For reverse (image) deltas, expired levels are dropped. For forward deltas, expired levels are incorporated into the base. When age retention is on, allowable values are 1 through 999 and the default is 999 months. Zero must be specified when age level retention is off. Removal of change levels only occurs when an element is moved or added to the end of system map route location.
Indicates whether the component change levels are to be managed by age.
Default. Age managed change levels are not in effect.
Age managed change levels are in effect.
Indicates the length of time, in months, that change levels are to be kept. For reverse (image) deltas, expired levels are dropped. For forward deltas, expired levels are incorporated into the base. When age retention is on, allowable values are 1 through 999 and the default is 999 months. Zero must be specified when age level retention is off. Removal of change levels only occurs when an element is moved or added to the end of system map route location.
Note: The auto age level retention options for elements and components can only be switched on or off on the system definition. If these options are activated at the system level, auto consolidation options on the type definitions are ignored for all types under the system.
The Element Registration Check Options fields contain definitions of the element registration features in effect for this System. This section of the System Definition panel includes the following fields:
Specifies whether the duplicate element name check feature is active. Valid values are:
CA Endevor SCM checks to see if the element name is used in any other Subsystems within this System.
CA Endevor SCM does not check for the same element name in other Subsystems. The default.
Specifies the error message severity level if CA Endevor SCM is checking for duplicate element names within the system. Valid values are:
If the same element name exists within another subsystem under the same system, the action is performed and a caution message is issued.
If the same element name exists within another subsystem under the same system, the action is performed and a warning message is issued.
If the same element name exists within another subsystem under the same system, the action is terminated and an error message is issued.
Note: This field must be blank if DUP ELEMENT NAME is set to No.
Specifies whether CA Endevor SCM checks element names across types and processors groups for the same processor output type. A conflict occurs if you attempt to add or create an element and an element with the same name and processor output Type exists in the same System, with a different Type.
CA Endevor SCM checks if duplicate element names with the same processor output type exist within the same system, but are a different type.
CA Endevor SCM does not check if duplicate element names with the same processor output type exist within the same or different systems.
Extends the check for duplicate processor output Types to all the Subsystems defined to this System. The check compares the processor output Type of the current action against all processor output Types of all same named elements in the different Subsystems of the same System. If any are equal, the current action fails with a registration error.
Specifies the processor output registration check message severity level.
An element with the same name and processor output type but different type exists within the same system. The action is performed and a caution message is issued.
An element with the same name and processor output type but different type exists within the same system. The action is performed and a warning message is issued.
An element with the same name and processor output type but different type exists within the same system. The action is terminated and an error message is issued.
Note: This field must be blank if the Duplicate Proc O/P Type Check feature is set to N.
These fields contain definitions of the signin/signout functions in effect for the system. The following information describes the Signin/Signout Options fields:
Acceptable values are:
The signin/signout facility is in use for this system.
The signin/signout facility is not is use.
Note: If signin/signout is set to N, the signout userid field is still updated. If you set this to Y, an ESMPTBL is present, and an element signout is overridden, CA Endevor SCM searches the table for the user ID that the element is signed out to. If a match is found, an email is addressed to the signout user. If no match is found, no email is sent. For more information about the Email Notification facility, see the appendix "Using the Email Notification Facility."
Acceptable values are:
The data set validation facility is in use for this system.
The data set validation facility is not in use.
When an element is retrieved, a "retrieve to" data set name (and member name if the data set is a library) is placed in the element master record.
When an ADD or UPDATE action is performed against an element, CA Endevor SCM compares the "retrieve to" data set name (and member name if applicable) to the source input data set and member name specified for the action.
These fields contain the date and time of the most recent backup of the system. They appear on the System Definition panel in display and delete modes only. These fields are display-only fields. The following information describes the Last System Backup fields:
Date of most recent system backup.
Time of most recent system backup.
These fields contain the names of the processor load and list libraries for the system. The following information describes the Processor Translation Output Libraries fields:
Name of the Stage 1 processor load library for this system. This load library must be different from the load library for Stage 2.
Name of the Stage 1 processor listing library for this system. This listing library must be different from the listing library for Stage 2.
Name of the Stage 2 processor load library for this system. If this load library is the same as the load library for Stage 1, CA Endevor SCM issues a warning message.
Name of the Stage 2 processor listing library for this system. If this listing library is the same as the listing library for Stage 1, CA Endevor SCM issues a warning message.
Note: To locate an element's processor, CA Endevor SCM always searches the Stage 1 load library first followed by the Stage 2 load library. The search order is the same, regardless of the element's location.
|
Copyright © 2013 CA.
All rights reserved.
|
|