What are the new features of Endevor 17.0.00?
Article ID: 46693
Updated On:
Products
Issue/Introduction
When upgrading CA Endevor, customers can jump one or more versions and go directly to the last version of Endevor.
If upgrading from version older, it is recommended to review the Release Notes for all intermediate versions.
This article gives the list of new features and enhancements for Endevor V17.0.
Environment
Releases 17.0
Component: ENDBAS, SCMMNI
Resolution
The Enhancements and New Features for V17.0 are documented below;
Remember, if upgrading from version older, it is recommended to review the Release Notes for all intermediate versions.
If Release Information or notes are needed for versions prior to V17.0, please search for "What are the new features of Endevor" from the Broadcom Support portal or contact CA Endevor Support.
CA Endevor Software Change Manager Version 17.0.00. introduces enhancements, as well as additional features. A brief description of each new feature and enhancement appears next. Further details are provided in the individual guides that make up the documentation set.
The document "Release Information" is attached to this article.
The following major enhancements are included in R17.0:
Customization table changes
The ENCOPTBL and BC1TNEQU customization tables have been changed.
Build SCL Supports Name Masking on Environment Value
On a Batch Environment Administration facility (Batch Admin) Build SCL statement, name-masking (wildcards and placeholders) can be used to specify the Environment value.
Package Selection List Filter for Exec-Failed Status
You can filter the package selection list to easily identify those packages that failed to execute.
Alter Action Updates Master Control File Element Metadata
You can use the Alter action to change Element master record information (Element metadata) in the Master Control File.
Web Services Software Requirements
The Web Services component is updated in the Version 17.0 installation. Java 7 is required.
- RESTful API
The RESTful API enhancement to Web Services enables you to build a RESTful API client program.
- Eclipse-Based UI
The Eclipse-Based UI client application must be reinstalled on all client computers. Reinstalling the client enables it to work with the Web Services component installed with Version 17.0. In addition, the Eclipse Foundation's Eclipse SDK version 4.3 is required.
- Miscellaneous changes:
- The heading on the C1MSGS2 Execution Summary report is changed from FROM INFORMATION to INVENTORY INFORMATION. If your site has implemented its own report-scraping program, you may need to verify whether this change impacts the program.
- The following User Exit 3 changes apply for all actions:
- Users can no longer suppress the SMF option with a User Exit 3 program.
- The SMF record is written before calling the Exit 3 program. So, users can no longer add notes or messages to, or change values in, the SMF record before it is written.
- Layouts of the following records and reports are enhanced to support the Alter action. You see these changes even if you never use the Alter action.
- API LIST SMF response record layouts have changed and their size is increased from Version 16.0. You must reassemble and relink any existing API List SMF programs to pick up the latest version of the API List SMF structures. If you do not, a structure version error is issued and the request fails. Although programs that call other API functions are cross-release compatible, programs that call the API List SMF function are not cross-release compatible and must be reassembled and relinked.
- API LIST Element response record layouts have changed and their size is increased from Version 16.0. If you have existing API programs and you do not recompile them after installing the new release, the response structures produced are identical to the output produced by the previous release. If you plan to use the Alter action and want to use the enhancements to the API LIST Element function, you must relink and recompile existing API programs that use that function. Thirteen fields related to the Alter Action were inserted into the API List Element Response Structure. For descriptions of the new fields, see Information about Alter Action Metadata, in List Element. The new fields were added before the Element area. Therefore the position of the ELMNAMEL and ELMNAME fields has changed. The API Assembler macros and COBOL copybooks are provided in iprfx.iqual.CSIQOPTN for each API function call. For the List Element structure, the structure naming convention is as follows: ExHALELM -- where x is N for Assembler macro and C for COBOL copybook and LELM is for the List Element function. Changes were made to the response structure (ALELM_RS, ALELM-RS) within these two members.
- CSV LIST Element output has changed from Version 16.0. Thirteen fields were added into the CSV List Element function. If you code the NOCSV option, you may need to change any programs that read the record formatted output. CSV output always matches the format of the latest release, because CSV functions call the current Endevor API to produce the output, which is always in sync with the latest release. See the bullet above for details about changes to the output of the API List Element structure for the Assembler macro and the COBOL copybook.
- SMF Reports 40 and 42 have layout changes to support the Alter action and to handle long Element names.
- User Data now appears on Element Master Display Panel.
- The Element Master Display panels now include an Alter Action Section on the last panel. This section displays information about all the Alter actions run against the Element.
- You must recompile your User Exit programs with the new Endevor release libraries as part of your implementation.
Enhancements Added After Version 17.0 GA for Package Ship Security
Enhancements to Package Ship security were introduced with PTF RO78325 in March, 2015. If Web Services has been installed, RO78326 is also required.
This PTF makes the following changes to Package Ship security:
- Alternate ID Previously, the option PACKAGE_SHIP_WITH_ALTID was added to the Optional Features table (ENCOPTBL) to let an API Package Ship request execute under the context of the Alternate ID. This PTF provides the same functionality when performing ship requests from the ISPF Package Shipment panel. Now, if the PACKAGE_SHIP_WITH_ALTID optional feature is enabled, all ship requests (API and ISPF) are performed under the context of the Alternate ID.
- External Security Interface and ISPF Package Ship Requests
- With this change, an External Security Interface (ESI) call is made in foreground for Package Ship requests to build the Package Ship queue, preventing unauthorized access to the ship function on the ISPF panels. Before this change, an ESI call was not made in foreground for building a ship request. If the user was not authorized to perform shipments, the batch ship job failed the ESI authorization check.
- External Security Interface and the API Ship Function With this change, an ESI call is made before the API Ship function is processed, under the context of the USERID.
Additional Information
Attachments
Feedback
