This section contains the following topics:
Controlling Duplicate Element Names at the System and Subsystem Level
Controlling Duplicate Element Names at the Processor Group Level
The element registration feature enables you to choose whether you want to restrict the use of the same element name. Duplicate element names can be problematic; however, there are situations where they are desirable - for example, the same element name is used for a program as well as its JCL.
When you define a system, CA Endevor SCM provides two options that enable you to allow or disallow duplicate element names. One option enables you to control the use of duplicate element names across subsystems within the system. The other option enables you to control the use of duplicate element names at the processor group level within the system. Both ways of controlling duplicate element names can be made to apply across systems.
Note: Verify you are using the same message severity level for the system in each environment where the system appears. If you do not, element actions may behave in an unpredictable manner. Similarly, if element registration is activated for a system, make sure it is activated in each environment in which it appears.
The Element Registration option enables you to control whether duplicate element names are allowed across subsystems within a system. During action processing, when the subsystem associated with the element is validated, CA Endevor SCM checks the option to see if duplicate element names are allowed.
By default, element name registration is defined at the system level on the system definition. You can also specify the element name registration options you want to apply to element name registration across systems. This is an optional feature you can activate in the optional features table ENCOPTBL by turning on the option REGISTER_ACROSS_SYSTEMS. If this option is turned on, CA Endevor SCM ignores the element name registration setting on the system definitions.
There are two sets of parameters that you can use to control duplicate element names at the system and subsystem level:
The System Definition parameters Duplicate Element Name Check and Msg Severity Lvl, govern this option. You can specify the following parameter values:
The same element name exists within another subsystem under the same system; the action is terminated and an error message is issued.
The same element name exists within another subsystem under the same system; the action is performed and a caution message is issued.
The same element name exists within another subsystem under the same system; the action is performed and a warning message is issued.
Note: The System Definition panel displays the parameter values in the Duplicate Element Name Check and Msg Severity Lvl fields.
If you turn on the optional feature REGISTER_ACROSS_SYSTEMS in ENCOPTBL, then CA Endevor SCM issues a message if an element is added or created and another element with the same name exists in another unmapped system/subsystem. If the option is set to E as follows: REGISTER_ACROSS_SYSTEMS=(ON,E), then you cannot create an element with the same name unless it is in the map of an existing element. A setting of C or W allows you to create a duplicate element, but a warning or caution message is issued.
Regardless of whether the option is set to E, C, or W, element name registration restricts the use of the same element name no matter its type. With this option turned off, elements with the same name can only exist in the same system/subsystem or in another system (no matter the subsystem). With this option turned on, elements with the same element-name (no matter the type) can only exist if one maps to the other.
When this option is turned on, CA Endevor SCM ignores all option settings for element name registration at the system definitions. The option-severity set in ENCOPTBL will rule over all systems in all the environments no matter what the element name registration option settings in the system definitions contain. If the REGISTER_ACROSS_SYSTEMS option is set to OFF, or is not activated in ENCOPTBL, then the settings on the system definition are used to determine what rules apply. This option has no impact on the way element registration works at the processor group level. You can continue to define elements with the same name in the same system/subsystem if the Duplicate Proc O/P Type check settings allow this.
Element Registration at the processor group level lets you control whether two elements with the same name, but with different element Types, can exist in the same System when both elements are associated to processors groups with the same processor output Type. The restriction can be set to all Systems or within a specific System. The purpose of the option is to prevent unintentional overlays of processor output library members that have the same name.
During action processing, if the element already exists at the target location within the same System under a different Type with the same output Type, the action is terminated or a warning message issued. This also occurs if an element with the same name and processor output Type, but different Type, already exists in a different System, provided the optional feature to check across Systems is enabled in ENCOPTBL.
Optionally, the search can extend to the Subsystem level. In this case, the searches for duplicate element names at the processor group level extends across Subsystems defined to a specific System. Specific Subsystems can be excluded from the search.
The Element Registration feature for processor groups can be enabled in a System definition to apply to all Subsystems within the System. To exclude any Subsystem, the Subsystem definition must be set to exclude it from the search. The administrator can set the options for the System and Subsystem definitions in foreground or batch. For more information about Batch Administration, see Define System Syntax and Define Subsystem Syntax in the SCL Reference Guide.
To enable Element Registration at the processor group level, perform the following steps:
DUP PROC O/P TYP=Y – 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 .
ACROSS SBS=Y – (Optional) 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.
MSG LEV - Specifies the message severity level when the check finds a duplicate. Valid values are:
W (Warning) – The action is performed and a warning message is issued.
C (Caution) – The action is performed and a caution message is issued.
E (Error) – The action is not performed and an error message is issued. The default.
This activates Element Registration for processor groups for the System you are updating on the System Definition panel. If you specify ACROSS SBS=Y, the check will extend to the Subsystems defined to this System.
EXCLUDE FROM DUPLICATE ELEMENT PROC O/P TYPE CHECK=Y – Excludes this Subsystem from the check.
ENHOPT ELM_REG_CHK_OUTPTYPE_ACROSS_SYSTEMS=ON
Note: For processor groups, you can define an output Type or use the default output Type. The default processor output Type is a concatenation of the element Type and the processor group name. Using the default can help you avoid duplicates.
After enabling the processor group option, you need to define the output type. The default output type is a concatenation of the element type and processor group names. Using the default value ensures there are no registration conflicts. Alternatively, you can define the output type using the Processor Group Definition panel. The output type field, PROCESSOR O/P TYPE, is 16-characters long. The output type is copied to the element catalog record segment when the element is added or updated.
You can implement the processor group option for selected inventory. For the inventory that should not be checked, leave the output value as it is originally set; that is, a concatenation of the element type and processor group names. Using the default value ensures there are no registration conflicts.
Note: For more information about processor groups, see the Extended Processors Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|