The following best practices make CA Endevor SCM easier to use and let you take advantage of advanced features.
Set session parameters to values that help your specific development process, instead of leaving the parameters set to the default values in the delivered software.
We recommend the following best practices.
Business Value:
Most of the common session parameters that can be set are in the ENDICNFG table. While these values can be set at installation time, they should be reviewed occasionally to ensure that they still reflect your site's needs. Each of these values results in a default value being displayed when the developer enters a panel that has a corresponding field. Whereas the developer can typically change the value as necessary, most developers will want the default value to correspond to the process that makes the most sense for their site.
Additional Considerations:
We recommend setting the following ENDICNFG parameters:
Set this parameter to Y to ensure that the Return command (typically PF4) will not exit CA Endevor SCM, but will return a user to the CA Endevor SCM Primary Options panel, thus facilitating the user's ability to navigate within CA Endevor SCM.
Set this parameter to Y so that all packages, by default, will be created sharable. This ensures that future maintenance against the packages can be conducted when it needs to be done.
Set this parameter to N so that you have a backup in case there is an issue with the transfer process.
Business Value:
This parameter indicates whether an element that you have caused to be fetched should be signed out to you, if it is not already signed out to someone else.This parameter will come into play with Add (Fetch), Generate (Copyback), Move (Fetch), Transfer (Fetch), Search and Replace (Fetch), and QuickEdit.
Business Value:
The user defaults should reflect the needs of the individual user. As delivered, the DISPLAY MSGS WHEN RC GE value is set to 0, which causes CA Endevor SCM to display messages for every action performed by the developer. Setting the value greater than 4 causes CA Endevor SCM to restrict the display of messages until an actual error is encountered, so the developer will not be distracted by informational messages.
More Information:
For more information see Set User Preferences in the User Guide.
Business Value:
The ISPF session parameters should correspond to the processes that make the most sense for your site to make development more efficient and save programmer's time.
Review the Optional Features table, ENCOPTBL, with every release and service pack to check for new or changed options.
Business Value:
The table provides you with a simple, easy-to-use mechanism to customize the product for use at your site. This facility enables you to configure your implementation of CA Endevor SCM by specifying which features you want to activate. Checking the ENCOPTBL table will help keep you up-to-date with the latest optional features and how they can affect your implementation.
Additional Considerations:
The source member ENCOPTBL is found in the installation TABLES file. We recommend activating the following options:
This option enables data set name place holders within processor concatenations to assist with processor execution. It lets CA Endevor SCM ignore (bypass the allocation of) data set slots in processor data set concatenations.
If this option is activated and you specify IGNORE as the first six characters of a data set name within a processor, when CA Endevor SCM executes the processor, it examines the first six characters and, if it finds IGNORE, it does not allocate the data set for execution in the processor. In effect, CA Endevor SCM ignores the data set.
This feature was developed to address the need for empty or null data sets within a processor, which act as place holders for valid libraries, depending on the stage at which the processor is being executed without requiring the processor to allocate a null data set.
This option causes the package processing routines to lock the elements that are contained in a package when the package is cast. This prevents elements from being changed while the package is awaiting approval.
This option causes the type definition defaults to change from Forward/encrypted base to Reverse/unencrypted for the element as well as the component list.
This option causes an ISPF confirmation panel to display when the element name is omitted and Y is specified for the search map list option. Significant delays can occur building an element selection list for all elements across multiple environments.
This option overrides the default logic that forces any processor step containing an INTRDR specification to run under the USERID. If this option is set on, then the processor step runs under the alternate ID. This ensures that jobs submitted to the internal reader run under the security context of the alternate ID.
Important! This option is ignored if ALTID=N is specified on the exec card of the processor step. In this case, the step runs under the USERID.
This option causes an ISPF confirmation panel to display when the package ID is omitted from the package panel. Omission of the package ID can cause significant delays in the construction of the package selection list.
This option reserves the other dataset name field in each user's profile for the C1SD4000 (footprint display), C1SF1000 (add/update) and C1SF2000 (retrieve) panels after each use. This option issues the ISPF command to save the panel field in the user’s profile, resolving to the last entry upon each display of the panel.
Use Change Control Identifiers (CCIDs) to group and manipulate similar kinds of change activity. For example, a number of different elements (COBOL copy members, COBOL programs, and so on) could be included in the same change request.
Business Value:
By tagging each change with a common CCID (such as FIX01), every change made for a change request is categorized as belonging to that CCID. Subsequently, the CCID can be used to identify and manipulate all the elements within the change request. CCIDs ensure accurate reporting, ease of package creation, and the maintenance of an audit trail.
Additional Considerations:
CCIDs can be used to integrate with the product CA Service Desk Manager.
Restrict access to read only for the data set high level qualifiers used by CA Endevor SCM and to the files owned by the product, and allow only the CA Endevor SCM Alternate ID, CA Endevor SCM administrators and systems programmers to have higher access levels. These include the Master Control File, Package Master, and so on, as well as the base, delta, and output files.
Business Value:
Allowing read access to anyone while restricting write and update access to the CA Endevor SCM Alternate ID protects the CA Endevor SCM owned content while enabling all work activity to proceed without limitations.
|
Copyright © 2014 CA.
All rights reserved.
|
|