Release Notes

Enterprise Common Components 17.02

January 3, 2019
What’s New

Enterprise Common Components (ECC) is comprised of the following main components: Host Communications Interface (HCI),Compuware Shared Services (CSS), License Management System (LMS), Compuware Mainframe Services Controller (CMSC), and Base Services.

Enhancements released January 3, 2019
Completed Removal of CLF

Compuware no longer supports or issues new licenses for the Central License Facility (CLF) beginning January 1, 2019.

Enhancements released October 1, 2018
ENF Listener Implemented

To reduce HCI/Topaz system utilization, an ENF Listener for Event 78 or Event 70 has been implemented to receive ENF events when jobs end and to push NOTIFY messages to Topaz users. This process greatly reduces CPU utilization in the HCI address space.

zAdviser Enablement

Added and enhanced functionality to collect usage data, create SMF records of this data, and provide those records to Enterprise Common Components to upload for analysis within zAdviser. zAdviser measures the quality, velocity and efficiency of mainframe development. Refer to the Enterprise Common Components Advanced Configuration Guide for parameter descriptions on how to configure and enable the creation of zAdviser records.

Discontinued Support for Central License Facility (CLF) Licensing

Compuware will no longer support or issue new licenses for the Central License Facility (CLF) beginning January 1, 2019.

Enhancements released June 28, 2018
HCIPlex Feature

HCIPlex enables adminstrators to setup an HCI with an associated port number, then have a large number of users be able to connect to them, using that same port number, without needing to consider task or memory constraints within the HCI.

Enhancements released April 2, 2018
Support for CMSC PARMLIB “Simple Deploy”

Installers want to avoid customizing CLIST, REXX, or ISPF panels, so ECC has implemented Compuware’s CMSC PARMLIB “Simple Deploy” feature. You can configure the CMSC PARMLIB member DDSNnnnn (initial default is DDSN00, or the specified default in your site’s CMSC start-up) with the DDNAMEs and DATASET NAMEs of all Compuware products, such as File-AID, Xpediter/TSO, Abend-AID, etc. A template DDSN00 member can be found in the Enterprise Common Components (ECC) SLCXCNTL library. This implementation requires ECC Release 17.02 with all current maintenance applied. Please refer to the Enterprise Common Components Installation and Configuration Guide for more information about this feature.

Enhancements released January 4, 2018
Parmlib Display Utility

Using a TSO command, the utility displays the contents of any Version 2 Parmlib member stored in memory and the name of the dataset from which the parameters were loaded.

Enhancements released Oct 2, 2017
Compuware PARMLIB Version Two

Compuware PARMLIB members are now validated before being stored in the CMSC, ensuring that when a Compuware product retrieves parameters, they are valid.

Compuware PARMLIB Enhancements

CMSC MODIFY command notification. When a command is issued to the CMSC the command and CMSC output are written to ULOG. This can be displayed by entering "ULOG" in SDSF.

The CMSC PARMLIB,DISPLAY command has been enhanced to display the PARMLIB members in the CMSC and the time they were last updated. This output can be viewed in ULOG.

Wildcard Prevention in Topaz Workbench

A new parameter, DISABLE_HLQ_WILDCARD has been added to the HCI. By specifying "YES", users of Topaz Workbench are restricted from creating a filter with a wildcard in the high level qualifier.

Enhancements released June 28, 2017
License Simplification

LMS version checking has been removed for all LIMITED_TERM licenses. You can now upgrade your Compuware mainframe products without having to get a new license file from Compuware.

ISPW Communications

Single sign is now supported for ISPW in the HCI. Three new parameters have been added to accommodate HCI support for ISPW communication; ISPW_HOST, ISPW_PORT, and ISPW_CTNAME.

Enhancements released April 3, 2017
Embedded Source Support

Compuware Shared Services (CSS) can now provide Embedded Source Support (ESS), allowing DDIO information to be stored directly in a program’s load module.

CSS and DDIO Overview

Compuware Shared Services (CSS) is an integral component of many Compuware mainframe products. CSS provides storage, retrieval, and maintenance for Abend-AID reports, source listings, and transaction dump information in datasets called DDIO files .

Shared directories and their attached databases are also types of DDIO files that can be used to more efficiently maintain information and activity within these files. CSS also provides language processing support for COBOL, PL/I, Assembler, and C.

The following products currently use CSS:

  Abend-AID

  Abend-AID for CICS

  Compuware Workbench/Topaz Workbench

  Enterprise Common Components

  Xpediter/CICS

  Xpediter/TSO and Xpediter/IMS

  Xpediter/Code Coverage

  Strobe

Older product versions do not support ESS. To use ESS with the above products, the version released in April, 2017 must be installed.

ESS Enabled in CSS

The COBOL Language Processor (LP) in CSS now provides a convenient new option called Embedded Source Support. Instead of storing the COBOL compiler listing and other program data in a VSAM or sequential DDIO file, ESS places those records in the NOLOAD segment(s) of the actual application module.

The primary benefit when using ESS is that the symbolic information for any given program will never get lost because it’s now embedded within the load module’s NOLOAD segment(s). NOLOAD segments, as indicated by their name, are not loaded at execution time. This in turn means that Compuware products will always be able to provide full source support (for COBOL V5.1 and higher) without the need for administering an additional set of source listing DDIO files, whether they are in standard DDIO, shared directory, or database format.

ESS Usage Notes

The following considerations apply to the use of ESS:

  Currently, the //CWPDDIO DD is required when using ESS even though no DDIO file will be created (that is, NODDIO is specified in the COBOL language processor command, either explicitly or by default). The dataset name specified in the DDNAME must be a valid DDIO file (This file will be opened and validated). However, if only ESS--and not DDIO--is selected, nothing will be written to //CWPDDIO DD. A future CSS/ESS change is planned to eliminate this requirement.

  ESS is only available for COBOL programs and the IBM Enterprise COBOL compilers starting with V5.1

  IBM Enterprise COBOL V5.1 and higher require the use of a PDSE for executable binary libraries.

  All previous DDIO functionality remains unchanged and in place.

  ESS is an additional option that can be used instead of DDIO.

  ESS and DDIO commands are independent and can be used separately or combined.

  Data records written (using the ESS option) to the load module are identical to the DDIO records written to DDIO files. Therefore, load module size increase will approximate the size of the DDIO file member in the listing DDIO files. A complete conversion to the ESS option eliminates the need for DDIO files, eliminating the need for additional DASD.

  Compuware products that take advantage of source support have been updated to first look for the ESS records and, if they are found, will not search any further for a DDIO file.

  If the ESS records are not found, the existing DDIO file search mechanism as currently implemented will be used.

Enhancements released January 4, 2017
LMS Disaster Recovery Improvements

For LMS Centralized Licensing Facility (CLF) environments running in a Disaster Recovery mode, a single emergency password, EMERGENCY, is entered in the server’s parameters to enable licensing for the duration of the emergency password. This password is propagated to all connected clients.

ECC Zero Administration Serviceability

To reduce the manual steps involved in installing, configuring and maintaining our web-based products, the HCI will send configuration information to CES automatically. Two new CMSC parameters, CES_HOST and CES_PORT, are required to enable this functionality.

CMSC Secure Connection Support

The CMSC can be configured to send REST calls to a CES configured with HTTPS client certificates for SSL level client authentication. Three new CMSC parameters, CES_SSL_KEYRING, CES_SSL_KEYDB and CES_SSL_KEYSTH, are required to enable this functionality.

Topaz Total Test Support

In support of the Topaz Total Test unit testing solution, the HCI will transfer binary data to and from the mainframe. This read/write functionality will pertain to sequential datasets of various record formats.

Topaz Alias Dataset Support

The HCI will enable the passing of alias dataset names to the Topaz Workbench where they will be fully supported and no longer display only.

Enhancements released October 1, 2016
CMSC API Support

Enhanced to support communication to CES, currently utilized by ISPW for the ISPW Web Interface.  Two new CMSC parameters, CES_PORT and CES_HOSTNAME, as well as an OMVS segment definition for the CMSC are required to enable this functionality.

HCI Configuration Migration Utility

If you are upgrading from HCI Release 3.0 to Release 17.02, Compuware provides a utility that converts HCI Release 3.0 XML parameters and their associated CSS TP configuration parameters into a PARMLIB member for use with the current ECC Release.

Technical Notes
EMCS_CONSOLE_NAME Parameter Changes

For HCIPlex, only dynamic console names are supported. If the EMCS_CONSOLE_NAME parameter is specified for an HCIPlex, the value will be ignored and forced to a dynamic console name. Also, the IBM Console Removal Service (CNZM1ERF) is now used to remove consoles so that they no longer persist. Finally, users no longer need to specify the EMCS_CONSOLE_NAME parameter to avoid the persistent console name issue. These changes should benefit all users regardless of whether an HCIPlex is being used. The EMCS_CONSOLE_NAME parameter may continue to be used to specify a fixed console name if a HCIPlex is not being used.

Abend-AID 12.04 Considerations

If you are upgrading to ECC 17.02 but not upgrading Abend-AID, see the “Special ECC 17.02 Upgrade Considerations with Abend-AID 12.04” section in the ECC Installation and Customization Guide.

PTF CXR119A Implications on iStrobe SQLAF On Demand

PTF CXR119A changes the way traffic is handled in the HCI. As a result of applying this PTF, an upgrade to CES/iStrobe to release 17.2.3 or higher is required to use SQLAF On Demand.

Known Issues

No issues

 

Doc. OCT2018