CA Endevor® Software Change Manager · Chapter 1: Welcome 7 What this Release Notes Covers ... SCM User Options Menu is now accessible from the CA Endevor Quick-Edit Option panel

Release Notes Release 15.1.00

CA Endevor® Software Change Manager

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Technologies Product References

This document references the following CA Technologies products:

■ CA Mainframe Software Manager™ (CA MSM)

■ CA Endevor® Software Change Manager (CA Endevor SCM)

■ CA Endevor® Software Change Manager Quick Edit (CA Endevor Quick Edit)

■ CA Common Services for z/OS (CA Common Services)

■ CA Change Manager Enterprise Workbench (CA CMEW)

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://www.ca.com/docs

http://www.ca.com/docs

Documentation Changes

The following documentation updates have been made since the last edition of this documentation:

Release 15.1

■ Conversion Requirements (see page 7)—Added to describe upgrade compatibility.

■ New Features and Enhancements for Release 15.1 (see page 59)—Added this chapter to describe the product changes introduced in Release 15.1.

■ Documentation Set Changes for Release 15.1 (see page 67)—Added to describe the addition of scenario-based knowledge documents to the documentation set.

■ Modified Nonprogram Product Components (see page 69)—Added this appendix to list nonprogram product components that were changed since the last release.

■ Accessibility Features (see page 77)—Added this appendix for the accessibility features.

– Product Enhancements (see page 77)—Added to describe the product features that support accessibility.

Version 15.0 Second Edition

■ Summary of New Features and Enhancements for Version 15.0 (see page 9)—Updated to add the CA MSM Version 04.0.00 feature Software Configuration Service and the component validation report in CSV format.

■ CA MSM (see page 11)—Added to indicate that CA MSM Version 04.0.00 includes the Software Configuration Service (SCS).

■ Create a Component Validation Report in CSV Format (see page 16)—Added to describe this procedure.

Contents 5

Contents

Chapter 1: Welcome 7

What this Release Notes Covers .................................................................................................................................. 7

Conversion Requirements ............................................................................................................................................ 7

Access the Product Page .............................................................................................................................................. 8

Chapter 2: New Features and Enhancements for Version 15.0 9

Summary of New Features and Enhancements for Version 15.0 ................................................................................ 9

Customization Tables Changed After CA Endevor SCM r14 ................................................................................ 11

CA MSM............................................................................................................................................................... 11

Package Element Action Backout ........................................................................................................................ 12

Log Delta Format for Element Types ................................................................................................................... 13

Package Shipment Destinations for XCOM Transmission ................................................................................... 16

Create a Component Validation Report in CSV Format ...................................................................................... 16

CA Endevor Quick Edit Access to the User Options Menu .................................................................................. 17

CA Endevor CA Roscoe Interface Installation Simplified ..................................................................................... 17

Element Registration at Processor Group Level Can Extend to Subsystems ...................................................... 17

CA Endevor SCM Web Services ........................................................................................................................... 20

CA Endevor Integration for the Natural Environment Enhancements ................................................................ 54

Documentation Changes ............................................................................................................................................ 57

Chapter 3: New Features and Enhancements for Release 15.1 59

Summary of New Features and Enhancements for Release 15.1 .............................................................................. 59

Customization Tables Changed After Version 15.0 ............................................................................................. 60

Package Ship for USS Supported Files ................................................................................................................. 61

Eclipse-Based UI Enhancements ......................................................................................................................... 63

How to Install and Configure the Apache Tomcat Server ................................................................................... 65

ELIB Support for Z/OS VSAM Extended Addressability ....................................................................................... 66

BSTCOPY Utility Improvements ........................................................................................................................... 66

Report Formats Consistent ................................................................................................................................. 66

Documentation Set Changes for Release 15.1 ........................................................................................................... 67

Appendix A: Modified Nonprogram Product Components 69

Nonprogram Product Components Modified in Release 15.1 .................................................................................. 69

6 Release Notes

Appendix B: Known Issues 75

Published Fixes for Release 15.1.00 ........................................................................................................................... 75

Appendix C: Accessibility Features 77

Product Enhancements .............................................................................................................................................. 77

Chapter 1: Welcome 7

Chapter 1: Welcome

Welcome to CA Endevor Software Change Manager Release 15.1.00.

This section contains the following topics:

What this Release Notes Covers (see page 7) Conversion Requirements (see page 7) Access the Product Page (see page 8)

What this Release Notes Covers

This release notes provides descriptions of new features and enhancements for Version 15.0 and Release 15.1. In addition, the following are described: changes to the documentation set introduced in Version 15.0 and Release 15.1, conversion requirements, product accessibility features, and how to access the product page and published solutions.

For the latest information, including any updates that may have occurred after publication, see the product page (see page 8).

Conversion Requirements

CA Endevor SCM Release 15.1 is upward-compatible with the Version 12, Version 14, and Version 15.0 product releases; Release 15.1 has no conversion requirements. As always, functionality introduced in a release is not backward-compatible. For example, an older product release cannot use new data created by a new feature in a Master Control File or in Package Control Files.

Access the Product Page

8 Release Notes

Access the Product Page

You can find the latest information about a product through the product page.

To find the CA Endevor SCM product page

1. Click this link to access CA Support: http://ca.com/support

The CA Support page opens.

2. Click Enterprise/Small and Medium Business.

The Support for Business and Partners page opens.

3. Log in and then click Support by Product on the left side of the page.

The Support by Product page opens.

4. Select CA Endevor Software Change Manager in the Select a product field by scrolling to the product name and clicking it.

The CA Endevor Software Change Manager product page opens.




Chapter 2: New Features and Enhancements for Version 15.0


Summary of New Features and Enhancements for Version 15.0 (see page 9) Documentation Changes (see page 57)

Summary of New Features and Enhancements for Version 15.0

A brief description of each feature and enhancement introduced in Version 15.0 appears next. More detailed descriptions follow and further details are provided in the individual guides that make up the documentation set.

■ Customization table changes (see page 11) – The Options table (ENCOPTBL) includes a new option for ACMQ reorganization. After a certain number of file updates, this option issues a console message, instead of running the reorganization utility in batch. This enables the administrator to schedule the reorganization.

■ CA MSM (see page 11) – The Software Configuration Service (SCS) has been added for CA MSM Version 04.0.00.

■ Package Element Action Backout (see page 12) – The output members of a single action within a package can be backed out without backing out the entire package.

■ Log delta format for element Types (see page 13) – A new source management element delta format named log delta is added. This format only stores the last level of an element. Source code changes are not stored in deltas. This format is for very large data files, for which source management is not needed, but an activity log can be helpful.

■ Package shipment destination for the XCOM transmission method (see page 16) – When defining a shipment destination for the package ship feature, you can define a TCP/IP address by specifying an IPNAME and IPPORT.

■ Component validation report in CSV format (see page 16) – The component validation report can be written in CSV format to an external file.

■ CA Endevor Quick Edit access to User Options Menu (see page 17) – The CA Endevor SCM User Options Menu is now accessible from the CA Endevor Quick-Edit Option panel.


10 Release Notes

■ CA Endevor CA Roscoe Interface (see page 17) – To simplify the installation of CA Endevor CA Roscoe Interface, the installation files are delivered in load module format.

■ Element Registration at the processor group level (see page 17) – You can set the processor output Type check to apply at the Subsystem level.

■ CA Endevor SCM Web Services (see page 20) – Internet client applications, including the CA Endevor SCM Eclipse-Based UI (Eclipse-Based UI), can connect to the CA Endevor SCM API using CA Endevor SCM Web Services (Web Services).

■ CA Endevor SCM Eclipse-Based UI – This option was previously named the Eclipse Plug-in and accessed the CA Endevor SCM API through CA Change Manager Enterprise Workbench (CMEW). The Eclipse-Based UI does not require CMEW and instead accesses the CA Endevor SCM API through Web Services. No other changes were made to the functionality. For more information, see CA Endevor SCM Web Services (see page 20). For information about installing this option, see the appendix "CA Endevor SCM Eclipse-Based UI" in the Installation Guide.

■ CA Endevor Integration for the Natural Environment (see page 54) – This option has been enhanced with the following changes. The Transfer action is available in batch. Users can build, save, and edit SCL for all CA Endevor SCM element actions supported by CA Endevor SCM. SCL for batch submission of actions can be built from scratch. When you are building package SCL, you can now import saved SCL objects. Additional package actions are available for package processing.

Important: Beginning with CA Endevor SCM r14, the product data set names were changed to make CA Endevor SCM compatible with CA MSM. For tables showing the new file names introduced with r14 and those delivered prior to r14, see the appendix Installation Data Set Names in the Installation Guide. This information is provided in case you are upgrading from CA Endevor SCM r12 or earlier.



Customization Tables Changed After CA Endevor SCM r14

The following table identifies a change to the ENCOPTBL customization table. This change is included in CA Endevor SCM Version 15.0. No other customization tables were changed after CA Endevor SCM r14.

Customization Table

When Added Option Description

ENCOPTBL r14 PTF ACMQ_REORG_BY_WTO=ON This option is related to the AUTO_ACMQ_FILE_REORG option.

ACMQ_REORG_BY_WTO causes CA Endevor SCM to issue the following WTO message instead of running the automatic file reorganization: 'ACMW000I ACMQ FILE REORGANIZATION RECOMMENDED'

This enables the system administrator to schedule a job to do the ACMQ file reorganization at a time of their choosing.

The default for this option is OFF.

CA MSM

The Software Configuration Service (SCS) has been added for CA MSM Version 4.0. Use this service to configure CA Technologies mainframe products from the software inventory of the driving system to your target enterprise systems.

The SCS guides you through the configuration creation process, and through the manual steps to implement the configuration. The SCS also includes an address space communications service running on each targeted z/OS system.

Note: For more information, see the CA Mainframe Software Manager User Guide.


12 Release Notes

Package Element Action Backout

The Element Action Backout feature lets you back out the output members of a single action within a package, without backing out the entire package. However, if there are multiple actions within the package that produce the same output member, the package is not eligible for Element Action Backout. After output members have been backed out, you can back them in again. Even after output members of an individual element action have been backed out, you can still use the Backout Package or Backin Package options to back out or back in all remaining output members of the package.

Previously, backout could not be selectively applied to a single action. The only backout option was Backout Package, which backs out all output members of a particular package. The Element Action Backout feature is particularly helpful if your package contains many elements that are unrelated to the element action that is the reason for the backout.

In foreground, you can use the new Element Action Backout panel, accessible from the Backout Package panel, to specify the SCL statements you want to back out or back in. In addition, you can view the backout status of each statement on this panel.

On the batch Backout Package statement, you can specify a statement number and element name to indicate the element action you want to back out. Similarly, you can specify a statement number and element name on the Backin Package statement.

The CSV utility's List Package ID function has been updated, so that the extracted package information can indicate that elements have been backed out of the package.PKG BACKED OUT can show a value of E and PKG BACKOUT STATUS can show a value of ELMBACKOUT.

The CONRPT72 Package Detail report now includes an Element Backout Section that lists all members in a package that have been backed out through the Element Action Backout feature. If the entire package is backed out, this section is not included in the report. The BACKOUT status column in reports CONRPT70 Package Summary and CONRPT71 Package Approver is updated to indicate if the Element Action Backout feature has been used on the package.

Note: The Package Backout Information panel, which is accessible from the Backout Package panel, is updated to enable the columns to be sorted properly using the ESORT command. This change includes renaming the DATA SET NAME column to DSNAME.



Note: CA CMEW does not support partially backed out packages. You cannot use CA CMEW to back out any packages that are partially backed out using the Element Action Backout feature. If a package has been partially backed out, the Backout button does not display on the CA CMEW CA Endevor SCM – Package Detail page. On the CA CMEW CA Endevor SCM – Backout Information page a Backout Status column indicates which elements have been backed out or backed in.

The following restrictions on Enterprise packages continue in effect:

■ In CA CMEW, if a package is part of an Enterprise package, you cannot back out the CA Endevor SCM package, you must back out the entire Enterprise package.

■ In CA Endevor SCM, you can back out CA Endevor SCM packages that are part of an Enterprise package. However, if the RESTRICT_BACKOUT option in the Optional Features Table is on, then Enterprise packages can only be backed out using CA CMEW.

Note: When you ship a CA Endevor SCM package, the original outputs are shipped, even if the entire package or some of the elements have been backed out. Similarly, when you ship backouts, the original package backouts are shipped. The backout and backin status of a package has no effect on what gets shipped.

Log Delta Format for Element Types

A new source management element delta format named log delta is added. This format is for very large data files, for which source management is not needed, but an activity log can be helpful.

The log delta format only stores the complete current source of the element in the base library. The element delta file for this format contains only audit activity information by version level. Only the current (last) level can be acted upon by CA Endevor SCM actions. The Change and History display options are not available for this format.

The log delta format is not available for element components. Components are managed by forward and reverse delta formats.

Restrictions apply to converting elements to different formats. However, elements with forward, reverse, or image delta formats can be changed to log delta format when restored (using the Restore action) or transferred from an unload or archived file. You can use the Restore action to restore elements with delta types other than log delta from an archive file into a CA Endevor SCM log delta Type location. This also applies to the Reload utility.


14 Release Notes

The following restrictions apply to the use of the log delta format:

■ An element delta type other than log cannot be moved with or without history, into a log delta type location. This also applies to transfers using the CA Endevor SCM to CA Endevor SCM Transfer action.

■ After a log delta element is created, it cannot be moved into another location that is not managed by a log delta type. This also applies to transfers using the CA Endevor SCM to CA Endevor SCM Transfer action.

■ An element Type definition's delta storage format cannot be changed from log delta format to another format, if sourced elements exist.

■ An element Type definition's delta storage format cannot be changed to log definition from another format, if sourced elements exist. This restriction prevents accidental source history delta deletion. For example, if forward delta elements exist at a location and the Type definition changes to log, the next altering source management activity would convert these elements to log deltas. This action would purge all source history.

Defining Element Types

The Batch Admin SCL syntax for Define Type is updated to add the log delta format option to the Element Delta Format specification. The log option is also available on the Type Definition foreground panel. When defining the log delta format for an element Type definition, you can specify whether CA Endevor SCM is to compress the base and encrypt the name. The regression percent specification must be set to zero.

Viewing Element Information

You can only view the current level of an element that is in log delta format. On the Summary of Levels panel, the browse command can only be issued against the last change level. Change and History element displays are not available for the log delta format. The Source Level Information section in a Browse display shows the same version level information as other delta formats.

The flower box identification areas in element or component browse, change and history panels are updated to contain the delta format type.

The ISPF foreground Element Master display panel and the CA Endevor Quick Edit Master Display panel display an L in the Delta Format field when an element uses the log delta format.

The Conrpt03 report uses L to indicate that elements are stored using the log delta format. The Conrpt07 report uses LOG to indicate that elements are stored using the log delta format.



Impact of the Log Delta Format on Other Features

The log delta enhancement affects various additional CA Endevor SCM features and product options as described next.

API

The API has been updated as follows. The extract element data request (AEELM request structure) can be used to extract an element’s last version level for elements created with the log delta format when the browse format or no format is specified. An error message results if an incorrect version level is specified in the AEELM block. The extract element change and history formats are invalid for log delta element types and, If specified, result in an error message.

Comma Separated Value Utility

The output from the Comma Separated Value(CSV) utility's List Type function has been updated. The heading for the Type delta format is changed to FWD/REV/IMG/LOG ELM DELTA and under this heading the new log delta format is indicated by L.

Restore Action

The option Retain Generate History is added to the Restore action. This option retains the Master Control File information. Without this option, the Restore action reinitializes the generate MCF information. This option when used with the Transfer to Archive action can be useful when converting elements to a new delta type.

The Retain Generate History option can be set using the Set Option and cleared using the Clear Option.

Exits

The Exit request control block was modified to add the Restore action's Retain Generate History option. This affects the $REQPDS assembler control block and the REQUEST-INFO-BLOCK for COBOL copybook. This option is modifiable by Exit 2.

The Exit element control block was modified to add indicators for Full-image delta and log delta formats. This affects the $ELMDS assembler control block, the COBOL copybook SRC-ELEMENT-MASTER-INFO-BLOCK and the COBOL copybook TGT-ELEMENT-MASTER-INFO-BLOCK.

CA Endevor InfoMan Interface Option

The field name RGENHIST is added to the CA Endevor InfoMan Interface to represent the Restore action's Retain Generate History option. RGENHIST represents the REQORGH field located in the $REQPDS control block.


16 Release Notes

CA Endevor SCM Parallel Development Option

The CA Endevor SCM Parallel Development option is of limited value for elements that are stored in log delta format, because only the element's last level is stored. When elements with log delta format are used as input for the Root, Derivation 1, or Derivation 2, then the current (last) level must be specified. If the current level is not specified, an error message results.

CA Endevor Roscoe Interface Option

The CA Endevor Roscoe Interface cannot display change or history element data for elements of log delta format. The browse display option is only valid on the last version level.

Package Shipment Destinations for XCOM Transmission

When defining a shipment destination for the package ship feature, you can define a TCP/IP address by specifying an IPNAME and IPPORT. This option is only valid for the XCOM transmission method.

A valid IPNAME can be one to 63 characters. Previously, only VTAM NODENAMEs could be specified. You can specify an IPNAME or a NODENAME for XCOM transmission, but not both. If you specify an IPNAME, then the one- to five-character IPPORT must be specified. The IPPORT value must match the XCOM SERVPORT specification of the target server.

IPNAME and IPPORT can be specified when defining a remote shipment destination using the Define Destination SCL for Batch Admin, or in foreground using the BUILD - Create/Modify a Destination panels. Inclusion of the IPNAME and IPPORT fields was added to the API List Destination response structure, the CSV List Destination Extracted fields and to the CONRPT73 – List Destination Detail Report.

Create a Component Validation Report in CSV Format

The component validation messages are written to the CAST report. In addition, the component validation report can be written in CSV format to an external file, which must be allocated as fixed block and LRECL 256.

To obtain the component validation messages in CSV format, specify the following in your CAST job:

■ //FPVL$CSV DD DSN=your.csv.output.file



A CSV record is written to the file for each validated component. Each CSV record will contain the following information:

■ Name of the package

■ Component validation error message (if any) for this specific component

■ Name and footprint of the element using the component

■ Name and footprint of the component being validated for this element

CA Endevor Quick Edit Access to the User Options Menu

The CA Endevor SCM User Options Menu is now accessible from CA Endevor Quick Edit. To access the User Options Menu, enter U on the CA Endevor Quick-Edit Option panel.

The User Options Menu can be customized by your CA Endevor SCM administrator to add user-defined functions. As delivered, this option enables you to build, edit, and submit report JCL in foreground. In addition, if your site is licensed for the CA Endevor Automated Configuration Option, you can perform ACM queries from this menu.

CA Endevor CA Roscoe Interface Installation Simplified

The CA Endevor CA Roscoe Interface installation files are now provided in load module format. Although, the source code no longer needs to be assembled and linked at client sites, clients still need to assemble and link the security module and the configuration table.

The BC1JRXIT sample JCL has been updated to assemble and link the initialization user exit module C1RPUX00 into your site’s uprfx.uqual.RSCOLOAD library. With CA Endevor SCM Version 15.0, this module does not get link-edited into C1RPUSER.

Element Registration at Processor Group Level Can Extend to Subsystems

The Element Registration feature at the processor group level can now be set to apply at the Subsystem level. 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. This enhancement extends the restriction to the Subsystem level. The enhancement searches for duplicate element names at the processor group level across Subsystems defined to a specific System. Specific Subsystems can be excluded from the search.


18 Release Notes

Enabling Element Registration for Processor Groups at Subsystem Level

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.

To enable Element Registration for processor groups at the Subsystem level in foreground, set the following parameters:

■ On the System Definition panel, set the following fields:

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 – 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.

■ On the Subsystem Definition panel, to exclude the Subsystem from the check, set the following field:

EXCLUDE FROM DUPLICATE ELEMENT PROC O/P TYPE CHECK=Y – Excludes this Subsystem from the check.

To enable Element Registration for processor groups at the Subsystem level using Batch Administration, set the parameters as follows:

■ In the SCL statement Define System, to create or update a System definition, include the option:

DUPLICATE PROCESSOR OUTPUT TYPE CHECK IS ACTIVE ACROSS SUBSYSTEMS - Extends the check for duplicate processor output Types to all the Subsystems defined to this System. The check compares the current processor output type of the action against all processor output types of all same named elements in the same System, different Subsystems. If any are equal, the current action fails with a registration error.

■ In the SCL statement Define Subsystem, to exclude the Subsystem from the check, set the following field:

EXCLUDE DUPLICATE PROCESSOR OUTPUT CHECK – Excludes this Subsystem from the check.

Note: To activate Element Registration across all Systems at the processor group level, the following parameter must be set in the Optional Features table (ENCOPTBL):

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.

Impact of Element Registration Enhancement on Other Features

Support for Element Registration at the processor group level in Subsystems is provided in the API, CSV utility, and in reports as follows:

■ API List System and List Subsystem Response Data—API functionality is updated to support the Subsystem option for Element Registration at the processor group level as follows:

– The List System function, which extracts System information, is updated to add the following new field to the List System response block.

ALSYS_RS_PREGXSBS - Duplicate element processor output Type check across Subsystems flag. Field length is one character. Value Y for Yes. Value N for No.

– The List Subsystem function, which extracts Subsystem information, is updated to add the following new field to the List Subsystem response block:

ALSYS_RS_PREGEXC - Exclude the Subsystem from the duplicate element processor output Type Check flag. Field length is one character. Value Y for Yes. Value N for No.

■ CSV Utility List System and List Subsystem—The CSV utility is updated to support the Subsystem option for Element Registration at the processor group level as follows:

– The List System function, which extracts MCF System information, is updated to return the following field:

PROC O/P REG ACROSS SBS - Duplicate element processor output type check across subsystems (Y/N)

– The List Subsystem function, which extracts MCF Subsystem information, is updated to return the following field:

EXCLUDE FROM PROC O/P CK - Exclude Subsystem from the Duplicate element processor output type check (Y/N)


20 Release Notes

■ Reports CONRPT07 – System Definition Profile and CONRPT51 – Unload System Definition Profile—The reports CONRPT07 and CONRPT51 are updated to support the Subsystem option for Element Registration at the processor group level.

– The report CONRPT07 – System Definition Profile, has been updated in the following sections.

■ The System information section now includes the following field:

Across SBS - Indicates whether duplicate element processor output type check across subsystems is in effect.

■ The Subsystem information now includes the following field:

EXCLUDE DUP PROC O/P CHK - Indicates whether the Subsystem is excluded from the duplicate element processor output type check.

– The report CONRPT51 – Unload System Definition Profile, now includes the following field:

Across SBS - Indicates whether duplicate element processor output type check across subsystems is in effect.

CA Endevor SCM Web Services

CA Endevor SCM Web Services (Web Services) is a middleware layer that runs in a z/OS USS environment and connects internet client applications to CA Endevor SCM through the CA Endevor SCM API. The CA Endevor SCM Eclipse-Based UI (Eclipse-Based UI) uses Web Services to connect to CA Endevor SCM. In addition, user-written client applications can use Web Services to access CA Endevor SCM. Possible client applications include browser, mobile, anonymous, or Rich Client Platform (RCP) programs.

Client applications communicate with the API using the CA Endevor SCM Software Control Language (SCL). With some restrictions, any valid SCL statement can be sent to the API and the results will be returned to the client. For more information, see submitSCL Operation (see page 52).

How Client Applications Access the CA Endevor SCM API

Web Services is a multithreaded application built with Java2 and the Apache AXIS2J component that enables client applications to communicate with a web service using the Simple Object Access Protocol (SOAP). The client and Web Services communicate using SOAP messages. The messages, requests and responses, are sent over TCP/IP between the client and the HTTP web server.

Web Services is packaged as an AXIS2 archive file (.aar) that is deployed in the HTTP web server under the AXIS2 environment.



The following illustration shows the flow of information between the client, Web Services, and the CA Endevor SCM API.

as sow

As shown in the illustration, client applications access the CA Endevor SCM API through Web Services. This process is described next.

■ The client application formats and sends a SOAP message to the HTTP server based on the definitions in the Web Services Description Library (WSDL) file. The request includes the name of the data source repository (CA Endevor SCM) that the client wants to access. This process uses the following standard technologies:

– XML language – The data format used by web service components. Communications between web service applications are written in XML format.

– Simple Object Access Protocol (SOAP) – An XML-based messaging protocol and encoding format for inter-application communication. SOAP messages are XML messages sent between applications. A SOAP message is a text file written in standard XML format that is enclosed in a SOAP structure. SOAP enables applications to know how to send and interpret the XML data.


22 Release Notes

– Web Services Description Library (WSDL) – A service description protocol. A web service's WSDL file is a dynamic XML file that serves as the interface between a client program and the web service. The Web Service WSDL file describes what CA Endevor SCM operations are available to the client program and the SOAP protocol bindings and message formats required to enable the client to interact with the web service.

If you are using Web Services for a user-written client application, your web developer must create a client stub from the WSDL file. The client stub is responsible for conversion of parameters used in a function call and deconversion of results passed from the server after execution of the function. The client stub interacts with the web service stub. For more information see, User-Written Client Applications (see page 48).

■ Web Services matches the name of the data source requested by the client call to a datasource.cfg file. The datasource.cfg file is stored on the HTTP web server and enables access to the CA Endevor SCM API. The datasource.cfg file identifies the started task procedure that starts the CA Endevor SCM API on the z/OS mainframe where CA Endevor SCM is installed. The CA Common Services CAICCI Spawn facility uses the started task procedure to spawn a started task for every user session.

To enable Web Services to process requests and communicate with the CA Endevor SCM API, the z/OS environment where CA Endevor SCM is installed requires certain CA Common Services components, including the following:

– CAICCI provides a common communications software layer that enables communication between Web Services and CA Endevor SCM API.

– CAIENF must be configured to enable the CAICCI Spawn facility that lets CA Endevor SCM schedule, execute, and monitor a service program on behalf of a Web Services request.



How to Install and Configure Web Services

Important: This topic is specific to Version 15.0. If you are installing Release 15.1, you can use an existing installation of Tomcat or install and configure the Apache Tomcat server included with CA Common Services. For more information about installing Tomcat for Release 15.1, see the appendix "Web Services" in the Release 15.1 Installation Guide.

Note: If you are installing from ESD or tape, additional jobs are required to support USS data sets. For more information, see the Installation Tasks for the Systems Programmer, in the Installation Guide.

Web Services is an application that runs in an HTTP/Application server (Tomcat) and uses Axis2 for SOAP message handling. The installation and configuration of the HTTP/Application server is independent of Web Services. Web Services can be installed into existing implementations of supported servers. For your convenience, the Web Services installation files include the versions of Apache Tomcat and Axis2/Java that are supported and recommended for the implementation of Web Services. To enable Web Services, complete the following steps:

1. Identify the instance or install the following modules in the z/OS USS environment that will host Web Services:

■ Apache Tomcat 6.0.29 – The HTTP web server and application server that hosts Web Services.

■ Apache Axis2/Java 1.5.1 (Axis2J 1.5.1) – The web services engine for the implementation of Simple Object Access Protocol (SOAP) 1.2 and Web Services Description Language (WSDL) 1.1.

For more information, see How to Install and Configure Apache Tomcat Server (see page 24).

2. Configure the CA Common Services components CAICCI and CAIENF in the z/OS environment that hosts the CA Endevor SCM API to enable Web Services to communicate with the CA Endevor SCM API. For more information, see How to Enable CA Common Services for Web Services (see page 29).

3. Create a datasource.cfg file, using ENDEVOR.cfg as a template, for the data source repository (CA Endevor SCM) that Web Services will access. Then deploy the file to your web server. If you are using Tomcat, save the file to this location: /cai/CADeploy/ESCM/tomcat/webapps/endevor. For more information, see How to Create a Datasource.cfg File (see page 34).

4. Configure CA Endevor SCM for Web Services. For more information, see How to Configure CA Endevor SCM for Web Services (see page 41).


24 Release Notes

5. Set up security.

■ Your web server administrator can limit access to Web Services. In addition, access to the CA Endevor SCM API is controlled using the login ID associated with the request. For more information, see Security Software Customization for Web Services (see page 44).

■ As with all standard web services, information is sent in plain text over a network using the HTTP protocol; therefore we recommend using SSL as your communications protocol. For more information, see How to Configure Web Services to Use HTTPS under Tomcat (see page 27).

6. Deploy the Web Services AXIS2 archive file (endevorService.aar) to your web server's JSP container.

7. If you need to enable access for a user-written client application, your application developer must create a client stub using the WSDL file and add the stub to your application. Skip this step, if you only plan to use Web Services for the Eclipse-Based UI. For more information, see User-Written Client Applications (see page 48).

How to Install and Configure the Apache Tomcat Server

Important: This topic is specific to Version 15.0. If you are installing Release 15.1, you can use an existing installation of Tomcat or install and configure the Apache Tomcat server included with CA Common Services. For more information about installing Tomcat for Release 15.1, see the appendix "Web Services" in the Release 15.1 Installation Guide.

Note: This topic discusses the minimum requirements to install and configure Tomcat. For more information, see the Tomcat documentation at http://tomcat.apache.org/tomcat-6.0-doc/index.html.

If an existing installation of Tomcat is not going to be used, install and configure the Apache Tomcat server included with the CA Endevor SCM installation package. Perform the following steps in a UNIX System Services (USS) environment to install and configure the Apache Tomcat server on your z/OS system:

1. Determine configuration parameters.

2. Establish environment variables.

3. Run the installation and configuration script.

4. Edit the Apache Tomcat configuration file.

5. (Optional) Configure Web Services to use HTTPS.

6. Edit the JCL to start the Apache Tomcat server.

7. Start the Apache Tomcat server.

8. Verify the installation and configuration.



Determine Configuration Parameters

Before installing and configuring a new instance of Apache Tomcat server, determine the following configuration parameters.

■ Ensure that you have a unique TCP/IP port number for this instance of Apache Tomcat server to use for communications. Each program on a LPAR using TCP/IP for communications must have a unique port number.

■ Determine the directory into which the latest Java Runtime Environment (JRE) has been installed (for example, /usr/lpp/java/J6.0). Ask your systems programmer for this information.

■ Determine the root directory into which you will install Tomcat and Web Services. The default value is /cai/CADeploy.

Establish Environment Variables

To establish environment variables for the Apache Tomcat Server, edit member WSTOMENV in CSIQJCL to specify the values for INSTALL_HOME and PRODUCT_HOME. Verify that JAVA_HOME has the appropriate value for your site.

INSTALL_HOME points to the instance of Tomcat that has been installed on the system. PRODUCT_HOME points to the instance of Tomcat that will be used to implement Web Services. If there is only one instance of Tomcat, then both variables will have the same value, for example:

INSTALL_HOME=/cai/CADeploy/ESCM

PRODUCT_HOME=/cai/CADeploy/ESCM


26 Release Notes

Run the Installation and Configuration Script

To run the installation and configuration script, the Tomcat .tar file must be exploded in the target path and the Apache Tomcat port number must be edited.

Note: These commands must be executed by a user with super user authority.The value /cai/CAdeploy is the default location for installation. If a different value was used at installation time these commands need to be updated with that value to function correctly.

1. Enter the following commands:

cd /cai/CADeploy/ESCM/tomcat

su

tar xvf ../software/tomcat-6.0.29.tar .

chmod 777 conf

chmod 777 temp

chmod 777 work

cd /cai/CADeploy/ESCM/tomcat/conf/

chmod 777 server.xml

cd /cai/CADeploy/ESCM/tomcat/webapps

tar xvf ../../software/axis2.tar .

This explodes the Apache Tomcat .tar file.

2. Edit server.xml in /cai/CADeploy/ESCM/tomcat/conf to change the server, connector, and redirect port numbers as necessary for your site.

The server.xml file is ASCII encoded and it needs to stay that way. One method to edit the server.xml file is to use ISPFEDIT. To use this method, do the following:

a. Enter the following command on your ISPF panel: TSO ISH

The UNIX System Services ISPF Shell panel opens.

b. Enter the following pathname where server.xml is located and then press Enter: /cai/CADeploy/ESCM/tomcat/conf/

A directory list opens.

c. Enter an E next to server.xml and press Enter.

The server.xml file opens.

d. Make your changes to the file and exit the file.

The file is updated for your site and remains an ASCII encoded file.



How to Configure Web Services to Use HTTPS under Tomcat

You can optionally use HTTPS instead of HTTP for user access. This option lets you specify a user name and password to minimize concerns about the data being exposed in clear text on the network.

To configure Web Services to use HTTPS, follow these steps:

1. Complete the following steps to generate a keystore:

a. In OMVS, enter the following command:

$JAVA_HOME/bin/keytool –genkey -alias tomcat -keyalg RSA

A prompt appears.

b. Specify a password, press Enter, and answer the questions.

■ We recommend using the host name that Tomcat runs on for the CN value so that when you are prompted to accept the certificate, it is clear which server it is coming from.

■ Optionally, specify a different location for the default keystore by replacing /path/to/my/keystore in the following command: $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -keystore /path/to/my/keystore

A default keystore is created in your home directory with one self-signed certificate inside.

2. Update the Apache Tomcat configuration parameters in the server.xml file located in the tomcat_install_dir/conf directory as follows:

a. Uncomment or replace the SSL connector information to specify site-specific values for the port and keystoreFile parameters.

Note: Ensure the keystorePass value matches the password specified in Step 1.

Sample SSL connector data follows:

<!-- Define a SSL HTTP/1.1 Connector on port 8443…

<Connector port="8040" protocol="HTTP/1.1" SSLEnabled="true"

maxThreads="150" scheme="https" secure="true"

clientAuth="false" sslProtocol="TLS"

keystorePass="Y7ssl"

keystoreFile="/ca/.keystore"/>

b. Edit the redirectPort value in the standard HTTP connector information to match the value specified in the SSL connector data:

<Connector port="8080" protocol="HTTP/1.1"

connectionTimeout="20000"

redirectPort="8040" />


28 Release Notes

3. Add the following lines before </web-app> at the end of the web.xml file located in tomcat_install_dir/conf:

<security-constraint>

<web-resource-collection>

<web-resource-name>Tomcat</web-resource-name>

<url-pattern>*.html</url-pattern>

</web-resource-collection>

<user-data-constraint>

<transport-guarantee>CONFIDENTIAL</transport-guarantee>

</user-data-constraint>

</security-constraint>

After you start the Apache Tomcat server, you will be prompted to indicate whether you trust the defined certificate. Click Yes to import it to your trusted certificates.

Note: For more information about trusted certificates, go to Apache Tomcat 6.0 on the Web.

Edit JCL to Start the Apache Tomcat Server

The JCL to start the Apache Tomcat server must be customized.

To edit the JCL to start the Apache Tomcat server, edit the WSTOMSTC member in CSIQJCL as described in the member.

The WSTOMSTC member is customized.

Start the Apache Tomcat Server

After completing the configuration steps, start the Apache Tomcat server for use with Web Services.

To start the Apache Tomcat server, use the WSTOMSTC member in CSIQJCL. Convert this JCL to a started task after the server has been tested.

The Apache Tomcat server is started in its own address space.

Verify Your Apache Tomcat Installation and Configuration

Use this procedure to confirm that you have successfully completed the Apache Tomcat installation and configuration procedures. If at any point you do not see the expected result, confirm that you have completed the Web Services configuration steps as documented. If you cannot identify the issue, contact CA Technical Support.

To verify your Apache Tomcat installation and configuration

1. Open a web browser and enter the Apache Tomcat host name and port in the URL followed by /axis2, and press Enter.

The Apache AXIS2 Welcome web page opens.



2. Click on the Services link.

The AXIS2 Available services page opens. You should see EndevorService listed with Available Operations of getConfigurations and submitSCL. This completes the Web Services installation. .

How to Enable CA Common Services for Web Services

When Web Services starts, the CAICCI SPAWN service invokes a started task to start services for CA Endevor SCM on the CA Endevor SCM host machine. To enable communication between CA Endevor SCM and Web Services, certain CA Common Services components must be installed and configured. This process is comprised of the following steps:

1. Verify that the CA Common Services components CAIRIM, CAIENF, and CAICCI are installed and running on the mainframe. If your site is running CAIENF r12 or higher, a database is not required for Web Services.

2. Enable the CAICCI Spawn facility for Web Services to initiate the started task for Web Services.

3. Find the SYSID for the location where CA Endevor SCM is installed.

4. IPL your system, if necessary. If this is your initial installation of CAICCI components, you do not need to IPL your system after installation. If this is a subsequent installation, you may need to IPL your system. For more information, see the CA Common Services for z/OS Installation Guide.

5. Record the values you used in the prior steps.

Verify that CA Common Services Components Are Running

The CCS components CAIRIM, CAIENF, and CAICCI must be installed and running on your mainframe. If they are not, you must install these services according to the instructions in the CA Common Services for z/OS Installation guide.

To verify whether CAIENF and CAICCI are installed and running

1. Go to the z/OS System Display and Search Facility (SDSF) status display and enter the prefix ENF*.

■ If you do not see ENF* active on your system, contact your systems programmer to start it.

■ If the ENF job is running, go to step 2.

2. Select the ENF job and search for (Find) CAICCI within the job.

– If you find CAICCI, then CAIENF and CAICCI are running. You are done verifying that the CCS components are running. Go to the procedure How to Enable the Started Task for Web Services (see page 30).

– If you do not find CAICCI, then go to step 3.


30 Release Notes

3. Check your site’s CAI.CAIPROC library to see if the ENF member has been modified to run CAICCI at your site.

■ If the ENF member exists, go to the task Customize the ENF Procedure and then have the member started.

■ If the ENF member does not exist, contact your local systems support person to determine the status of CAIRIM, CAIENF, and CAICCI on your system and to help you complete the tasks in the next section.

How to Enable the Started Task for Web Services

Web Services uses the CAICCI SPAWN facility to communicate with the CA Endevor SCM API. Enabling the spawn facility involves adding the spawn parameter file definition (ndvspawn) to the ENF procedure for CAICCI services. The spawn parameter definition file (ndvspawn) specifies the name of the started task JCL (WSEWSSTC) for the CA Endevor SCM API. The WSEWSSTC procedure JCL must be edited to specify the high-level and second-level qualifiers for the CA Endevor SCM data sets. WSEWSSTC is initiated as a started task.

To enable the started task for Web Services, do the following:

1. Customize the ENF Procedure by appending the Web Services spawn parameter file definition named SPNPARMS DD to the ENF PROC JCL. You can find the ENF procedure in the initial CAI.CAIPROC library. However, your system administrator may have copied the procedure to the system PROCLIB. The following JCL is shown as an example to indicate the two lines you must add to the JCL.

//ENF PROC OPTLIB='SYS2.CA90S.PARMLIB',

// ENFDB='SYS2.CA31.ENFDB',

// ENFPARM=ENFPRM31,

// SPNPAR1=SPWNSNMP,

// SPNPARn=ndvspawn,

// CCIPARM=CCIPCA31,

// ENFCMDS=ENFCMD31,

//ENF EXEC PGM=CAS9MNGR,TIME=1440

//CASRT01 DD UNIT=SYSDA,SPACE=(CYL,(5,1))





//SPNPARMS DD DISP=SHR,DSN=&OPTLIB(&SPNPAR1)

// DD DISP=SHR,DSN=&OPTLIB(&SPNPARn)

//SPNPRINT DD SYSOUT=X

//SPNDEBUG DD SYSOUT=X

//SRVDEBUG DD SYSOUT=X

//ENFDB DD DISP=SHR,DSN=&ENFDB

//ENFPARMS DD DISP=SHR,DSN=&OPTLIB(&ENFPARM)

// DD DISP=SHR,DSN=&OPTLIB(&CCIPARM)

//ENFCMDS DD DISP=SHR,DSN=&OPTLIB(&ENFCMDS)

//SYSPRINT DD SYSOUT=X



SPNPARn

Specifies a symbolic for a CAIENF parameter member. Change n to the next available sequential number in the list of parameter files.

ndvspawn

Specifies the spawn parameter file. This member contains the CAICCI SERVICE and PROCESS statements. The SERVICE statement identifies the CA Endevor SCM API. The PROCESS statement identifies the JCL procedure that executes the CA Endevor SCM API.

2. Customize the spawn parameters by editing the CAICCI SERVICE and PROCESS statements in the ndvspawn file. Then save the appropriate file in your site specific CA90S.PARMLIB as member NDVSPAWN.

Note: For sample CCI definitions for Web Services, see the member WSEWSCCI supplied in the installation source library iprfx.iqual.CSIQOPTN.

SERVICE statement

Identifies the CA Endevor SCM API (host application).

PROCESS statement

Identifies the JCL procedure that executes the CA Endevor SCM API.

PROCNAME=WSEWSSTC

Specifies the name of the procedure associated with the CA Endevor SCM API host application that is started by the CAICCI SPAWN service during Web Services processing. The WSEWSSTC value is the name of the started task procedure that is initiated by a SPAWN request.

Note: When Web Services starts, the CAICCI SPAWN service invokes a task to start CA Endevor SCM related services on the CA Endevor SCM host machine. By default, the name of the procedure associated with this started task is WSEWSSTC; however, this name is often changed, for example, to meet site-specific naming or security standards. If you do not know the procedure name at your site, check to see if the default name was retained or consult your system administrator.

Important! Keep the statements in the exact format provided, maintaining spaces and column alignments. For more information about defining and using CAICCI statements, see the CA Common Services documentation.


32 Release Notes

3. Customize the WSEWSSTC started task procedure. Change the parameters as appropriate for your site.

Note: A sample WSEWSSTC procedure is located in the CSIQJCL library delivered with CA Endevor SCM.

Note: If you change the WSEWSSTC member name, be sure to update the PROCNAME value in the CCI PROCESS statement of the SPNPARn file to reflect the new procedure name.

Note: The wsewsstc value is specified in the JOBNAME parameter of the datasource.cfg configuration file.

4. Copy WSEWSSTC into a PROCLIB defined to JES. WSEWSSTC is initiated as a started task.

5. Specifies the CCI host application or process name used to start the CA Endevor SCM API server. This is the CA Endevor SCM mainframe started task procedure

6. If this is your initial install of these CAICCI components, you do not need to IPL your system after installation. If this is a subsequent install, you may need to IPL your system. For more information, see the CA Common Services for z/OS documentation.

Find the CA Endevor SCM SYSID

You must know the SYSID of the system where CA Endevor SCM is installed. Later you will need to enter the SYSID in the datasource.cfg file. For more information, see How to Create a Datasource.cfg File (see page 34).

To find the CA Endevor SCM SYSID, open the CCIPARM file member located in the library &OPTLIB. Find and make a note of the SYSID parameter.

For example, part of a sample CCIPARM file is shown next. In this sample, the name of the SYSID is A31SENF.

000001 *********************************************

000002 ** CA EVENT NOTIFICATION/CCI PARAMETER FILE *

000003 ** ---------------------- *

000004 ** CA-ENF/CCI VERSION 1.1 CONTROL OPTIONS *

000005 *********************************************

000006 SYSID(A31SENF)

000007 PROTOCOL(LU0,A31SENF,01,A31SENF)

000008 PROTOCOL(XES,CCIXES)

000009 PROTOCOL(TCPIP,1202)



Record Your Configuration Values

Record the values you identified while completing the procedures How to Enable the Started Task for Web Services and Find the CA Endevor SCM SYSID. You will use some of these values to populate the datasource.cfg file. Record the following values:

Definition Source Default Value Your Value

Mainframe logon host name:

Specifies the name of the SYSID parameter in your CCIPARM file.

This is also used for the datasource.cfg HostName parameter.

CCIPARM none

CA Endevor SCM mainframe started task procedure:

Specifies the procedure associated with the started task that starts CA Endevor SCM services when Web Services starts. The default name for this procedure (WSEWSSTC) may have been changed to meet site-specific standards.

This is also used for the datasource.cfg JobName parameter.

NDVSPAWN file WSEWSSTC

SPNPARn:

Specifies a symbolic for a CAIENF parameter data set.

Systems administrator

SPNPAR2


34 Release Notes

How to Create a Datasource.cfg File

The datasource.cfg file defines a data source repository (CA Endevor SCM). This file includes configuration and connection information about your CA Endevor SCM installation. The Web Services initialization process scans all .cfg files located in the webapps/endevor folder. Only valid datasource.cfg files are activated.

Edit and save the datasource.cfg file as follows:

1. Use the supplied datasource.cfg file (ENDEVOR.cfg) as a template or create your own configuration file manually in an editor. This file is coded as an XML document. An XML schema describes the requirements of this file. The configuration file must conform to the XML schema. If the file contains errors, Web Services will not activate it. For more information, see ENDEVOR.cfg File Template (see page 35) and XML Schema (see page 36).

Important: The .cfg file is ASCII coded. For more information, see How to Edit ASCII Encoded Files (see page 36).

If you are using the supplied ENDEVOR.cfg file template, you must modify the HostName and JobName parameters. Also, you should edit the Comments parameter specific for your installation. Review the other parameters and, if needed, change them to your preferences. For more information, see ENDEVOR.cfg Parameters (see page 37). All other parameters can be left as defined. If you make other changes to the file, they must conform to the XML schema.

2. Rename the .cfg file to match the value of the Name= parameter coded in the configuration file. The client web service application uses this name to refer to the data source repository.

3. Deploy the file to the following location on your web server: /cai/CADeploy/ESCM/tpv/tomcat/webapps/endevor



ENDEVOR.cfg File Template

The delivered datasource.cfg file is named ENDEVOR.cfg. This file is a template and is ASCII coded. To use this file, you must edit and rename it as appropriate for your site. The template is as follows:

<?xml version="1.0"?>

<DataSource xmlns="http://scm.ca.com/endevor/CFG"

xmlns:cfg="http://scm.ca.endevor"

Name="ENDEVOR" Status="Available"

Message="Welcome to ENDEVOR"

Description="Endevor demo">

<STC HostName="CCIHOST"

JobName="CCISTC"

ProgramName="BC1PAPI0"

Comments="ENDEVOR STC">

<wsParameters Lang="EN"

TimeZone="GMT-6.0"

CodePage="cp1047"

Encoding="cp1047"

CharacterSet="ISO8859-1"

LFSEncoding="ISO8859-1"

ContentType="Text"

Trace="1"

Traced="USERID"/>

</STC>

</DataSource>

Example: Datasource.cfg file for CA Endevor SCM Web Services

This sample datasource.cfg file is named ENWSTST7.cfg. This file enables the CAICCI Spawn facility on the z/OS mainframe to spawn started tasks using the ENWSTST7 started task procedure specified by the JobName parameter. Each started task starts a user session for the program BC1PAPI0 (the CA Endevor SCM API) located on the specified hostname A31SENF.

<?xml version="1.0"?>

<DataSource xmlns="http://scm.ca.com/endevor/CFG"

xmlns:cfg="http://scm.ca.endevor"

Name="ENWSTST7"

Status="Available"

Message="Welcome to ENDEVOR"

Description="Endevor demo">

<STC HostName="A31SENF"

JobName="ENWSTST7"

ProgramName="BC1PAPI0"

Comments="ENDEVOR STC">

<wsParameters Lang="EN"/>

</STC>

</DataSource>


36 Release Notes

enws.xml XML Schema

Your datasource.cfg file must conform to the XML schema. The XML schema defines the required structure, content, and semantics of the file.

The XML schema for the datasource.cfg file consists of the following sets of parameters:

■ DataSource parameters that specify information about the data source repository (CA Endevor SCM).

■ STC parameters that specify the started task and host for the repository.

■ wsParameters that specify default values for data conversion between the client operating environment and the z/OS mainframe that hosts the repository.

Note: The XML schema can be found in the enws.xsd member of the installation library.

How to Edit ASCII Encoded Files

The ENDEVOR.cfg file is an ASCII coded file and it needs to stay that way. One method to edit an ASCII file is to use ISPFEDIT. To use this method, do the following:

1. Enter this command on your ISPF panel: TSO ISH

The UNIX System Services ISPF Shell panel opens.

2. Enter the pathname where the file you want to edit is located and then press Enter. For example, as delivered, the ENDEVOR.xml is located here: /cai/CADeploy/ESCM/tomcat/webapps/endevor/

A directory list opens.

3. Enter an E next to the file you want to edit and press Enter.

The file opens.

4. Make your changes to the file and exit the file.

Your file is edited and remains an ASCII file.



ENDEVOR.cfg Parameters

The ENDEVOR.cfg file contains the following parameters:

■ DataSource parameters – Specify the name of the data source and information about the data source. The parameters are as follows:

Name

Specifies a 1- to 20-character alphanumeric name that identifies the CA Endevor SCM data source that this configuration file applies to.

Note: To be a valid datasource.cfg file, the name of the .cfg file must match the Name= value specified within the file. To connect a user-written client to a data source, the DataSource parameter specified in the client request is matched to the name of the datasource.cfg file.

Status

Specifies whether the service is active. Valid values are 1- to 15-character text strings. Recommended values are Available or Unavailable. This text appears where the data source is listed as a valid data source by the client application.

Message

Specifies any 1- to 100-character message you want for this data source, such as "Welcome to CA Endevor SCM Web Services. Service is open." This text appears where the data source is listed as a valid data source by the client application.

Description

Specifies any 1- to 100-character description you want for this data source, such as "CA Endevor SCM Web Service" This text appears where the data source is listed as a valid data source by the client application.

■ STC parameters – Specify the CCI host where CA Endevor SCM is running, the CCI PROCNAME defined in spawn parameters (the started task procedure to be spawned), and the program name for CA Endevor SCM on the specified host z/OS mainframe.

Hostname

Specifies the one- to eight-character CAICCI hostname associated with the data source. Use the value of SYSID in the CCIPARM file, which is the SYSID of the system where CA Endevor SCM is installed.

Jobname

Specifies the one- to eight-character CAICCI host application or process name used to start the CA Endevor SCM API server. Use the CA Endevor SCM mainframe started task procedure specified in the NDVSPAWN file. Usually, the Jobname is: WSEWSSTC


38 Release Notes

ProgramName

Specifies the one- to eight-character name of the program started by Jobname, which is BC1PAPI0.

Comments

Specifies a 1- to 100-character string that helps identify the data source to users.

■ wsParameters parameters – Specify default values that are appended to the submit call. These parameters detail the handling of the data transported on the Internet from or to CA Endevor SCM.

Important: These values are superseded if values are passed with the submitSCL() call.

Lang

Specifies a two-character language code for the CodePage.

Default: EN.

TimeZone

Specifies the time zone where the data source is located, expressed as a positive or negative offset from GMT+0, for example GMT-6.0. Web Services uses this value to determine the correct time on the z/OS mainframe where the data source resides, for use in messages.

CodePage

Specifies the code page, defined in the mainframe operating system, that CA Endevor SCM is using. The code page is a variation of the Extended Binary Coded Decimal Interchange Code (EBCDIC) that defines how text files are coded on the mainframe.

The CodePage and CharacterSet parameters enable Web Services to translate the plain text information exchanged between the client computer and the API. Plain text information includes SCL commands sent to the API and reports and CSV files extracted from the API.

For information about supported encodings, see: http://download.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html

Default: cp01140

CharacterSet

Specifies the character set used by the client application, for example latin1 or iso8859-1. The CharacterSet value specifies how Web Services is to convert the mainframe code page to and from the alphabet used by the client application. This value is used for conversion of plain text information only. For more information, see the CodePage parameter defined in this topic.

http://download.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html

http://download.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html



LFS.Encoding

Specifies the encoding scheme for CA Endevor SCM elements stored in the client local file system. This value specifies the name of the character set that the Java Virtual Machine uses on Web Services (where text character conversion occurs). This value applies to the exchange of files between the client application and the API. In CA Endevor SCM, these files are associated with an element Type defined with DATA FORMAT=Text.

■ For an Add or Update action of a text file from a local file system to CA Endevor SCM, the data of the text file is converted from the LFS.Encoding scheme into a Unicode alphabet. Then the data is converted into the target character set defined by the Encoding parameter.

■ For a Retrieve action of a text file, the data is converted from the CA Endevor SCM Encoding scheme into the Unicode character set. Then the data is converted into the target character set specified by the LFS.Encoding parameter.

Default: ISO-8859-1

Important! When you Add or Update an element to a file Type defined in CA Endevor SCM as DATA FORMAT=Text, Web Services attempts to translate this file from the code page on the local workstation to the mainframe code page using the character sets defined in the LFS.Encoding and CodePage parameters. All characters in the local code page may not have an appropriate mapping in the host code page. The same consideration applies when retrieving a text element. For files that do not require character set conversion, the Type definition for those files must specify DATA FORMAT=Binary.

Encoding

Specifies the encoding scheme for CA Endevor SCM element. This value is usually the same value as the CodePage.

ContentType

Specifies how CA Endevor SCM reports and queries are exchanged with the Web Services client computer. The default is Text.

Trace

Specifies what to trace. Valid values include a trace level or string value. The default is 0.

Traced

Specifies the user name to be traced. Valid values include:

user-name – Specifies a one- to eight-character user name.

ALL – Specifies all users.


40 Release Notes

How Access to the Data Source Works

Web Services is delivered as an AXIS2 archive file (EndevorService.aar). Tomcat automatically or manually deploys this .aar file. The EndevorService component (also known as a web service end point) has a lifecycle in that it can be started and ended. During the initialization phase, the component scans the webapps/endevor folder and identifies and validates the configuration files *.cfg. If a validation failure occurs, the configuration file is discarded. To add, delete, or modify a .cfg file, the EndevorService.aar component must be stopped and restarted.

The client application or the Eclipse-Based UI connection wizard can access a list of validated data sources. The list includes the description, status, and message extracted from the datasource.cfg file. The EndevorService.aar file contains several files, including a .jar file that is a set of java classes that receive the SOAP envelope. The SOAP message from the client application includes a dataSource parameter in the LoginProperities object. This parameter indicates the data source repository (CA Endevor SCM installation) that the client application wants to access.

A client can have access to more than one validated data source at the same time.

■ There can be more than one valid datasource.cfg file in the webapps/endevor folder. For example, A1.cfg, A2.cfg, B1.cfg, and B2.cfg could access data sources named: A1, A2, B1, and B2.

■ Different datasource.cfg files could specify the same started task on the same or on a different CAICCI host. A requirement of the XML schema is that the name of the .cfg file must match the name of the data source specified by the Name value in the .cfg file. However, the name of the data source does not need to be the same as the started task JobName value specified in the .cfg file.

For example, in the following table, each *.cfg file accesses a data source using the started task on the host computer. All three of these data sources could be available at the same time.

*.cfg Data Source Name Started Task Procedure Host Name

A1.cfg A1 ENWSTST7 usilnj31

A2.cfg A2 ENWSTST7 usilnj11

B1.cfg B1 ENWSTST7 usilcnj31



How to Configure CA Endevor SCM for Web Services

CA Endevor SCM must be configured to support Web Services. Complete the following steps:

■ Set the BATCHID parameter in the TYPE=MAIN section of the C1DEFLTS table to 1. This specifies that the CA Endevor SCM user ID associated with a batch job should be determined by the USER parameter specified on the JOB statement instead of the JOBNAME. For more information about BATCHID, see the CA Endevor Software Change Manager Administration Guide.

■ Configure element Type definitions. For more information, see Support for Element Types (see page 41).

■ (Optional) To optimize the use of your Master Control File (MCF) and Package Dataset, we strongly recommend that you implement IBM VSAM Record Level Sharing Support (RLS).

Support for Element Types

You can add files accessible on a client machine to CA Endevor SCM and retrieve elements from CA Endevor SCM. Web Services transfers files to and from the client application using SOAP attachments. To enable the translation of transferred data, a CA Endevor SCM Type record must be properly defined for each type of data to be managed. The characteristics of binary and text files are described next:

Text files

Web Services defines a text file as one that has line delimiters and requires character translation. You can store text files on the mainframe and browse them in CA Endevor SCM. Detailed change history is stored for text files.

Browsing an element in CA Endevor SCM invokes the EBCDIC-to-ASCII conversion function of CA Endevor SCM; the EBCDIC-to-local file system encoding is not used. However, when you retrieve a text file from CA Endevor SCM, the Web Services server converts EBCDIC from the mainframe.

The CodePage Web Services parameter in the datasource.cfg configuration file defines the character sets for the mainframe and Web Services.

Note: For more information, see Datasource.cfg Parameters (see page 37).

Binary files

Web Services defines a binary file as one that does not have line delimiters or require character translation. Examples of binary files are Microsoft Word documents or Excel spreadsheets. Long names are typically used for naming binary files. Specific file versions can be retrieved through Web Services. You can browse binary files whose content type is recognized by your browser when using Web Services.

Note: For more information on binary files, see the appendix, “Working with Binary Files” in the CA Software Change Manager Administration Guide.


42 Release Notes

How to Define an Element Type for Binary Files

To enable Web Services to transfer binary files using attachments, Type definitions for binary files must be properly configured in CA Endevor SCM. To define a binary Type, complete the following steps:

1. Define the base library. The base library must be an HFS file.

Note: For information on rules concerning HFS setup for long name use, see the appendix “Long Name and HFS File Support” in the CA Endevor Software Change Manager Administration Guide.

2. Define the delta library with the following considerations in mind:

■ The delta PDS record format must be variable blocked.

■ The delta library record length and the type definition source length can be any value (for example, 259, 6024, or 27984) as long as the maximum delta record length is about twice the source length. We recommend a value of 27984.

3. Set the TYPE DEFINITION panel fields to the following values to define a CA Endevor SCM Type record for binary data.

a. Set the FWD/REV/IMG DELTA field to I to specify the Full Image delta storage format for elements of this Type. This suppresses the comparison logic. Each update causes the entire file to be added as a new level.

b. Set the COMPRESS BASE/ENCRYPT NAME field to Y or N. This option specifies whether to encrypt and compress the base form of elements stored in reverse delta format.

c. Set the SOURCE LENGTH field to 13992. This specifies the logical record length in the source statements. Although the maximum allowable value is 32000, the value must not exceed the maximum physical record length in the delta library definition.

d. Set the COMPARE FROM field to 1. This option specifies the position within each statement at which CA Endevor SCM begins comparing to identify changed statements (5 digits in the range 1-32,000).

e. Set the COMPARE TO field to 13992. This option specifies the position within each statement at which CA Endevor SCM stops comparing to identify changed statements.

f. Set the HFS RECFM field to F to specify the fixed length. This specifies the record delimiter used in a HFS file. A record delimiter is necessary due to the nature of HFS files. HFS files contain one large data stream; therefore, a delimiter is used to identify individual records within that data stream. This is also true for elements associated with a type defined as Data Format=Text when the element is transferred between CA Endevor SCM and Web Services. Web Services recognizes and appends the delimiter for the exchanged records.



g. Set the DATA FORMAT field to B for binary. If left blank, the value defaults to B. This deactivates compression and prevents text character conversion from being invoked.

h. Set the FILE EXT field to a valid file extension type (doc, ppt, xls, jar, ear, and so on) or leave it blank. The file extension is used when you are adding files from or retrieving files to a local file directory using Web Services.

How to Define an Element Type for Text Files

To enable Web Services to transfer text files using attachments, Type definitions for text files must be properly configured in CA Endevor SCM. To define a text Type, complete the following steps:

1. Define the base and delta libraries using CA Endevor SCM rules for the specific file type. For more information, see the CA Endevor Software Change Manager Administration Guide.

2. Set TYPE DEFINITION panel fields to the following values to define a CA Endevor SCM Type record for text data.

a. Set the FWD/REV/IMG DELTA field to F for forward or R for reverse to specify the delta storage format.

b. Set the COMPRESS BASE/ENCRYPT NAME field to N for element names that do not exceed eight characters and are uppercase. For other element names, set this field to Y. If set to Y, the base library must be HFS.

c. Set the COMPARE FROM field to a value appropriate for the type of data. For example, COBOL can be 7.

d. Set the SOURCE LENGTH and COMPARE TO fields to values appropriate for the type of data. For example, COBOL SOURCE LENGTH can be 80 and COMPARE TO can be 72.

e. Set the HFS RECFM field to CRLF. This is the linefeed character for Microsoft Windows files. If you do not specify CRLF for text types accessed using local file system support, you will get unexpected results in Windows-based editors.

f. Set the DATA FORMAT field to T for text. This triggers conversion from EBCDIC to local file system encoding.

g. Set the FILE EXT field to the file name extension you want the file type to have on the local machine (cob, jcl, and so on) or leave it blank. FILE EXT is used when you are adding files from or retrieving files to a local directory using Web Services.


44 Release Notes

Security Software Customization for Web Services

You must configure your site’s security software so that all authorized users can initiate WSEWSSTC correctly as a started task. This section provides samples of how to set up this security. These samples are only examples and may not conform to your site’s security standards. Review the following section that discusses the security software used at your site:

■ CA Top Secret

■ CA ACF2

■ IBM RACF

If your site’s security administrator has further questions about setting up started task security, see the product-specific documentation or contact Technical Support for the security software you are using.

Note: Files are compressed, but no data encryption occurs during the transfer of files from the client to the Web Services server. Data communicated between CA Endevor SCM and Web Services is not compressed or encrypted, except for passwords.

Configure CA Top Secret

If your site uses CA Top Secret, you must configure CA Top Secret so that all authorized users can initiate WSEWSSTC correctly as a started task. To configure CA Top Secret, you define a new facility named ENDEVOR, add a new ACID, and give the ACID a MASTFAC definition. You then make this facility the default ACID for the CAICCI-spawned task WSEWSSTC defined earlier in this chapter. Finally, you add all users of Web Services to the ENDEVOR facility.

Note: For more information about completing the following steps, see your CA Top Secret documentation or contact Technical Support for CA Top Secret.

To configure CA Top Secret

1. Define a new facility named ENDEVOR for CA Endevor SCM by adding the following definitions to the CA Top Secret parameter file (specified by the PARMFIELD DD statement):

* USERnn FACILITY FOR

*

FAC(USERnn=NAME=ENDEVOR)

2. Define a new ACID named ENDEVOR by entering the following command:

TSS CRE(ENDEVOR) NAME('endevor userid') TYPE(USER) FAC(STC,ENDEVOR) PAS(NOPW,0)

The NODSNCHK, NORESCHK, and NOSUBCHK bypass attributes on the ENDEVOR ACID may be required. If not, make sure that the ACID is authorized to access all of the files and resources it requires.



3. Give the ENDEVOR ACID a MASTFAC definition by entering the following command:

TSS ADD(ENDEVOR) MASTFAC(ENDEVOR)

4. Assign ENDEVOR as the default ACID for the CAICCI-spawned task WSEWSSTC by entering the following command:

TSS ADD(STC) PROCNAME(WSEWSSTC) ACID(ENDEVOR)

5. Grant each user of Web Services access to the ENDEVOR facility by entering the following command:

TSS ADD(USERID) FAC(ENDEVOR)

Note: For more information about defining a new facility, see your CA Top Secret Control Options Guide. For more information about the CRE and ADD commands, see the CA Top Secret Command Functions Guide.

Configure CA ACF2

If your site uses CA ACF2, you must configure CA ACF2 so that all authorized users can initiate WSEWSSTC correctly as a started task. To configure CA ACF2, you create an STC login, verify that the dataset access is correct, and define a resource class. This section is only a sample of how your site can set up security. For more information about setting up started task security, see your CA ACF2 documentation or contact Technical Support for CA ACF2.

To configure CA ACF2

1. Create an STC logon ID named ENDEVOR for the WSEWSSTC started task by entering the following commands:

ACF

INSERT ENDEVOR NAME(ENDEVOR) STC

2. Verify that the ENDEVOR logon ID is defined with site-specific logon ID fields such as those fields used to create the UID string.

Note: For instructions to create CA ACF2 logon ID records, see the CA ACF2 Administration Guide.

3. Verify that the ENDEVOR logon ID has access to all required datasets by writing CA ACF2 ACCESS rules for the logon ID.

Note: For instructions to write these rules, see the CA ACF2 Administration Guide.


46 Release Notes

4. Define a resource class called FACILITY and assign a resource type code of FAC. Perform these steps to do so:

a. Enter the following commands to create the CLASMAP record for the

FACILITY resource class:

ACF

SET CONTROL(GSO)

INSERT CLASMAP.FAC RESOURCE(FACILITY) RSRCTYP(FAC)

b. Enter the following commands to add the FAC resource type code to the CA-ACF2 GSO INFODIR record:

SET CONTROL(GSO)

CHANGE INFODIR TYPES(R-RFAC)

c. Do one of the following to activate the CLASMAP and the INFODIR record change:

■ Restart the CA-ACF2 address space.

■ Enter the following commands:

F ACF2,REFRESH(CLASMAP)

F ACF2,REFRESH(INFODIR)

Note: For more information about maintaining CA-ACF2 GSO records, see the CA ACF2 Administration Guide.

5. Create a FACILITY resource rule record called ENDEVOR and grant users access to this resource by issuing the following commands:

ACF

SET RESOURCE(FAC)

COMPILE */pds.name

$KEY(ENDEVOR) TYPE(FAC)

UID(user1 uid string) ALLOW

UID(user2 uid string) ALLOW

.......

STORE

6. Enter the following command to rebuild the FAC directory:

F ACF2,REBUILD(FAC)

Note: For instructions to write CA ACF2 resource rules, see the CA ACF2

Administration Guide.



Configure IBM RACF

This section provides basic instructions for customizing IBM RACF to allow the WSEWSSTC started task to initialize correctly. According to the RACF Security Administrator Guide, you can use either of the following methods to define a started task to RACF:

■ Define a new profile to the STARTED class (recommended by IBM)

■ Add a new entry in the started procedures table (ICHRIN03)

Additionally, you must assign a RACF user ID to the started task WSEWSSTC and assign the user ID to a RACF group authorized to initiate started procedures.

To define a RACF user ID for WSEWSSTC, use the ADDUSER command and associate it with your existing started task RACF group, as follows:

ADDUSER user_name DFLTGRP(default_group) OWNER(default_group) NOPASSWORD

user_name

Specifies the name of the new RACF user ID. This name should be the same as the name of the started task member in your PROCLIB that Web Services uses.

default_group

Specifies the default group that contains all system started tasks; for example, STCGROUP.

Note: If you do not know the name of the default group, see your RACF administrator. For detailed information to implement the RACF STARTED class or to modify the started task table (ICHRIN03), see the RACF documentation.

Note: This command is only an example. For more information on using the ADDUSER command, see your RACF administrator.


48 Release Notes

User-Written Client Programs

A user-written client program collects the following information: a login user ID and password for access to a specified CA Endevor SCM repository; an SCL statement with optional wsParameters; and parameters for a SOAP Attachment to transport data to and from Web Services. A client stub is used to convert the parameters passed between the client application and the web server. The program developer must create the client stub from the WSDL published by Web Services so that the program will meet the requirements of the web service.

The client application developer creates a client stub from the WSDL and then incorporates the stub as an import package in the client program. The developer implements the client application's logic above the client stub.

■ For client programs written in Java, the stub is a collection of Java sources grouped in a package. The sources are compiled by the javac compiler into a JAR file. This JAR file is required by the sample code. The program code must include an import statement that refers to the generated packages (this allows the java IDE to make the Loginproperties object available to the application program). The client program can instantiate the stub to invoke the web service. For a client to access the stub, the stub class should be present in the classpath of the client application.

■ For client programs written in C, the stub, in C code, is compiled and the generated header files are required to code the application program. The application program must have the #include structure.h in C++ include wobject.h>

For example, a Java client program instantiates the following objects and populates them with the correct values for a specific request.

■ LoginProperties

■ SCL

■ Attachment

The client stub created from the Web Services WSDL supports the instantiation of these objects. The data in these objects is required by Web Services. The client program populates the objects with the following parameters:

■ LoginProperties object – Contains the following parameters:

DataSource

Specifies the data source repository (CA Endevor SCM) that the client wants to access. This value must match the name of a valid datasource.cfg file accessible by Web Services. For more information, see How to Create a Datasource.cfg File (see page 34) and How Access to the Data Source Works (see page 40).



UserID

Specifies the user ID for access to the CA Endevor SCM API.

Password

Specifies the password for access to the CA Endevor SCM API.

■ SCL object–Contains the following parameters:

Statement

Specifies the SCL statement entered by the user of the client application.

wsParameters

(Optional.) Specifies parameters and values to override wsParameters specified in the datasource.cfg file. These parameters are Lang, TimeZone, CodePage, LSF.Encoding, Encoding, CharacterSet, ContentType, Trace, and Tracer. For more information, see Datasource.cfg File. Parameters (see page 37).

Category

Specifies the type of SCL request. All the SCL specified in a request must be for the same type. Valid values follow:

A – Specifies environment administration actions.

C – Specifies Comma Separated Value (CSV) utility actions.

E – Specifies element actions.

P – Specifies package actions.

S – Specifies package ship actions.

X – Specifies batch ACM Query utility actions.

L – Specifies Add, Update, or Retrieve requests that required local file system (LSF) support. The SCL statements for these actions require the To | From Attachment clause to specify the location on the local client where the data will be transferred to or from.

Note: Use Category E for Add, Update, or Retrieve requests that are not LFS requests (with the Attachment clause) and that use either To | From DSName or To | From Path HFSFile.

Timezone

Specifies the timezone where the client application is located. Web Services uses this value to determine the correct time, on the client side, for use in messages.


50 Release Notes

■ Attachments object – Contains the following parameters:

DD

Specifies the data set on the client side that contains the data being exchanged.

Note: For the base64Binary type, the DATA are coded with the 64Binary translation and manipulated by a data handler or without any translation and appended as a MTOM attachment. The client code is expected to fill the DD property using a data handler (in the case of the 64binary translation) or as MTOM attachment to take advantage of the streaming.

DDName

Specifies the attachment name that references what is being exchanged.

contentType

Specifies the data type being exchanged. Specifies how the data transported by the Attachment objects of the client call are coded. This value informs Web Services how to format the data part of the attachment. ContentType is a standard of the Multipurpose Internet Mail Extensions (MIME) message protocol used by HTTP for complex messages, including messages with file attachments.

Example: Client Program in Java

A Java client program invokes a stub (generated from the WSDL) and runtime (AXIS2J). The sample program code shown next instantiates the loginProperties object, the SCL object, and the Attachments object. The client program populates the objects with the values required for a specific client request.



The request includes the login properties for access to a specified CA Endevor SCM repository. The request also includes the SCL statement and optional parameters, as well as a SOAP Attachment, used to submit an SCL statement and data to Web Services.


52 Release Notes

How to Create a Client Stub for a User-Written Client Application

To enable a user-written client program to access Web Services, the client application developer must create a client stub, using the Web Services WSDL file. Then the client-side stub must be incorporated as an import package into the client program. The stub manages, sends, and receives SOAP messages to communicate with the web service.

■ You can create the client stub manually or using a utility. After Web Services is installed, the WSDL file can be accessed using a web browser and saved as an xml file. There are third-party tools, for example WSDL2Java that can be used to query the WSDL and generate a stub for use in application generation.

The WSDL file for Web Services is located at: http://<servername>:<portnumber>/axis2/services/EndevorService?wsdl.

Replace the <servername>:<portnumber> specifications with the name and port number of the web server where your installation of Web Services resides.

■ After the stub is written or generated, the client stub has to be compiled and the client application's logic implemented above the stub. The client program can instantiate the stub to invoke the web service. For a client to access the stub, the stub class should be present in the classpath of the client application.

submitSCL Operation

Web Services supports the submitSCL operation. Client requests can communicate with the CA Endevor SCM API using the CA Endevor SCM Software Control Language (SCL). With some restrictions, any valid SCL statement can be sent to the CA Endevor SCM API and the results will be returned to the client, providing full access to the repository.

Valid SCL statements for the submitSCL operation for Web Services are subject to certain restrictions.

■ The following actions are not valid:

– &&ACTION

– Archive element

– Copy element

– List member From Archive

– Print member From Archive

– Restore element

– Transfer To Archive

– Transfer From Archive

– Archive Package

– Export Package



■ The parameter DDNAME is generally not supported for Web Services. However, DDNAME C1PRINT is valid on List and Print actions.

Note: The DSName dataset-name parameter is supported.

Instead of the DDName parameter, the Add, Update, and Retrieve actions use SOAP attachments to transport data between the client and the mainframe. For more information, see To | From Attachment Clause on SCL Statement (see page 53).

Note: No footprint information is stored in files retrieved from CA Endevor SCM. Temporary files written to the Web Services server are purged at the start of each new local file system command.

To | From Attachment Clause on SCL Statement

Every web service call (request) from a client application requires a SOAP Attachment object to submit requests and receive responses. If the request transports data between the client and Web Services, the SCL statement must include a From Attachment or To Attachment clause. This clause specifies the name and location of the file on the client side that is being sent from the client or to the client.

The following SCL requests require the From Attachment clause:

■ Element actions Add or Update.

■ Upload of package SCL statements.

The following SCL requests require the To Attachment clause:

■ Element action Retrieve.

■ Fetch of reports.

■ Extract of Comma Separated Value (CSV) data.

To | From Attachment Syntax

Instead of the TO | FROM DDNAME clause on the SCL statement for an Add, Update, or Retrieve action, use the following syntax:

TO|FROM ATTachment attachment-name PATH mypath LFSFILE myfile

To Attachment attachment-name

Specifies the name of the SOAP Attachment object that contains the data that is to be sent from CA Endevor SCM to the client.

From Attachment attachment-name

Specifies the name of the SOAP Attachment object that contains the data that is to be sent from the client to CA Endevor SCM.


54 Release Notes

PATH mypath

Specifies the directory on the client side. For the From Attachment clause, Path is where the source file resides. For the To Attachment clause, Path is where the file is to be saved to.

LFSFILE myfile

Specifies the name of the file in the directory on the client side. For the From Attachment clause, Lfsfile is the name of the source file. For the To Attachment clause, Lfsfile is the name that the received file is saved as.

Example: Add Element Statement with Attachment

The following Add Element statement adds element CCIDRPT2 to Stage 1 of the DEV Environment, EABASE System, UTILITY Subsytem, COBOL Type library. The SOAP Attachment object UPLOADD contains a copy of the content of myfile located at myPath. on the client side. This statement adds the contents of the SOAP Attachment to CA Endevor SCM. The optional Options clause associates the comment "Project myfile' to the element.

ADD ELEMENT CCIDRPT2

FROM ATTACHMENT UPLOADDD PATH myPath LFSFILE myFile

TO ENV DEV SYS EABASE SUB UTILITY TYPE COBOL STAGE NUMBER 1

OPTIONS UPD COMMENT 'Project myFile' .

Example: Retrieve Element Statement with Attachment

The following Retrieve Element statement retrieves element CCIDRPT5 from Stage 1 of the DEV Environment, EABASE System, UTILITY Subsytem, COBOL Type library. A copy of the data that is element CCIDRPT5 is added to the SOAP Attachment object DNLOADD. Web Services send a SOAP message response back to the client. The SOAP message includes Attachment. The client extracts the data from the Attachment and copies it to myfile located at myPath. on the client side.

RETRIEVE ELEMENT CCIDRPT5

FROM ENV DEV SYS EABASE SUB UTILITY TYPE COBOL STAGE NUMBER 1

TO ATTACHMENT DNLOADDD PATH myPath LFSFILE myFile

CA Endevor Integration for the Natural Environment Enhancements

This section contains topics about enhancements to CA Endevor Integration for the Natural Environment.

Note: For information about installing and configuring CA Endevor Integration for the Natural Environment, see the appendix "CA Endevor Integration for the Natural Environment" in the Installation Guide.



Transfer Action

Support is provided for the Transfer action in batch. The Transfer action migrates the specified objects from the From Environment to the To Environment you specify and performs these actions:

■ Determines whether the element is signed out to you. If the element is signed out to someone else, you must set the OVERRIDE SIGNOUT option to Y to transfer the element.

■ Updates the Master Control File (MCF) for the element based on the options specified as part of the transfer.

■ Updates the CCID and Comment fields for the element with the information you provide on the panel.

For more information, see How Transferring an Element Works and Transfer an Element in the chapter "Performing User Tasks" in the Integration for the Natural Environment User Guide.

Saved SCL Objects

This enhancement lets you build, save, and edit SCL for all CA Endevor SCM element actions supported by CA Endevor SCM (Retrieve, Add/Update, Move, Delete, Generate, Sign-in, and Transfer) from the existing elements within CA Endevor SCM, including the building of Add action SCL from Natural, Predict, or error message text objects within a Natural library.

Saved SCL objects contain SCL statements for the batch submission of actions or for import into package SCL and are stored in the Natural library EINESCL as text objects.You can add SCL to the EINESCL library using the Batch SCL enhancement. In addition, template SCL is provided in the EINELIB library for each SCL function. The sample SCL objects are: NATSDIS (display); NATSRET(retrieve); NATSADD (add); NATSMOV (move); NATSDEL (delete); NATSGEN (generate); NATSTRN (transfer); and NATSSGN (signin). Saved SCL objects can be edited outside of CA Endevor SCM by copying the required templates from the EINELIB to the EINESCL library and using the standard Natural editor to modify the copied template members in the EINESCL library.

Saved SCL can be imported for use when creating package SCL. In addition, from the Endevor Saved SCL panel, which is accessible from the CA Endevor SCM Main Menu, you can perform the following tasks:

■ Display all the SCL objects saved in the Natural library EINESCL.

■ Delete a previously saved SCL object.


56 Release Notes

■ Edit a previously saved SCL object. You can add, delete, and modify the SCL lines using standard TSO line commands.

■ Submit a previously saved SCL object for batch processing.

For more information, see Saved SCL Objects, Access Saved SCL Objects, Delete SCL Objects, Edit SCL Objects, and Submit Saved SCL Objects in the chapter "Performing User Tasks" in the Integration for the Natural Environment User Guide.

Batch SCL Statements

SCL for batch submission of actions can be built from scratch using a new option (PF11 SCL) on the Batch Processing Menu. Regardless of whether you build the SCL from scratch or generate the SCL using the batch processing panels accessible from the Batch Processing Menu, you can now use the PF4 (Save) key to save the SCL to a Natural text member in the library EINESCL. Then the SCL can be edited by logging on to the EINESCL library and using the standard Natural editor. In addition, the SCL can be listed, deleted, edited, or submitted from the Saved SCL panel.

Previously, you could use the batch processing panels to generate and submit the SCL statements, but the SCL could not be saved.

For more information, see Submit Actions in Batch in the chapter "Performing User Tasks" in the Integration for the Natural Environment User Guide.

Package SCL Import

When you are building package SCL, you can now import saved SCL objects that exist in the Natural library EINESCL by entering a P on any line of SCL while in Edit mode.

For more information, see Build Package SCL in the chapter "Performing User Tasks" in the Integration for the Natural Environment User Guide.

Package Processing

This enhancement adds the following package actions to CA Endevor SCM package processing. These new options are available from the package selection list on the Endevor Package Processing panel.

■ Reset a package into In-Edit status from any other status, allowing modification of the package.

■ Review a package to approve or deny processing. Not all packages require approval. Status of a package requiring approval is In-Approval and may be in this status after cast, if approval for the package to execute is required.

■ Execute a package in Approved or Exec-Failed status. A package can be in Approved status after cast or after review approval. A package can be in Exec-Failed status if a prior execution of the package failed.



■ Commit a package in Executed status, which removes all backout information from the package.

■ Delete a package in any status.

Previously, CA Endevor SCM package processing was limited to creating, modifying (In-Edit packages only), and casting packages. After a package was cast, all handling of the package had to be done through CA Endevor SCM unless the package was reset to In-Edit status within CA Endevor SCM.

For more information, see Reset a Package, Review a Package, Execute a Package, Commit a Package, and Delete a Package in the chapter "Performing User Tasks" in the Integration for the Natural Environment User Guide.


Guides of the documentation set have been updated to include descriptions of the enhancements and features introduced in Version15.0. In addition, the following changes have been made to the documentation set:

■ The Installation Guide includes new appendices that describe how to install the following components and options:

■ CA Endevor SCM Web Services

■ CA Endevor SCM Eclipse-Based UI

■ CA Endevor Quick Edit Option

■ CA Endevor Integration for the Natural Environment

■ The Quick Edit Option User Guide has been restructured and rewritten for clarity. Information about how to set up this option is located in an appendix in the Installation Guide.

■ A Documentation Changes topic has been added before the Table of Contents in each guide that was updated. The Documentation Changes topic lists topics to which substantive changes were made.

Note: In PDF format, page references identify the first page of the topic in which a change was made. If the topic is long, the actual change may appear on a later page.


58 Release Notes

■ The Integration for the Natural Environment User Guide is included in the CA Endevor SCM Bookshelf. Previously, a separate documentation set and bookshelf was provided for CA Endevor Integration for the Natural Environment. That documentation set was composed of an Options Guide and a Release Notes. The Options Guide was discontinued and its content was transferred to either the Integration for the Natural Environment User Guide or an appendix in the Installation Guide.

Note: When viewing documentation in HTML format, the railroad syntax diagrams can sometimes appear misaligned. Diagram alignment depends on your display settings and the text size your browser is using. Adjust your view settings or text size until the diagrams align correctly. For example, from the Internet Explorer Menu bar, click View, Text Size and then select a different size. PDFs do not have this problem, so you can also view diagrams in the PDF file. Note: Regardless of your view settings, Internet Explorer 6 does not correctly display syntax diagrams.


Chapter 3: New Features and Enhancements for Release 15.1


Summary of New Features and Enhancements for Release 15.1 (see page 59) Documentation Set Changes for Release 15.1 (see page 67)

Summary of New Features and Enhancements for Release 15.1

A brief description of each feature and enhancement introduced in Release 15.1 appears next. More detailed descriptions follow and further details are provided in the individual guides that make up the documentation set.

■ Customization table changes (see page 60)—Several changes appear in the optional features table (ENCOPTBL).

■ Package Ship utility (see page 61)—Packages containing UNIX System Services (USS) supported files (HFS, zFS, and NFS) can be shipped.

■ Eclipse-Based UI (see page 63)—The Eclipse-Based UI has been enhanced to support the CA Endevor SCM Move and Generate actions. In addition, you can set a timeout value for the AXIS2 connection to timeout action requests.

■ Web Services (see page 65)—You can use an existing installation of Apache Tomcat or install and configure the Tomcat server included with CA Common Services. A Tomcat server is not provided with the CA Endevor SCM installation files.

■ ELIB Support for Z/OS VSAM extended addressability (see page 66)—The ELIB data set format supports z/OS VSAM extended addressability for VSAM data sets.

■ BSTCOPY processor utility (see page 66)—BSTCOPY is redesigned to make it more efficient.

■ Reports (see page 66)—Minor reformatting changes have been applied to some reports.


60 Release Notes

Customization Tables Changed After Version 15.0

The following table identifies the customization tables that were changed after Version 15.0, including any changes that are being introduced in Release 15.1.

Note: If you have customized the User Exits table, C1UEXITS, you must re-assemble and link your version of this table to include the new version of the @C1UEXIT macro supplied with Release 15.1.

Customization Table

When Added Option Description

ENCOPTBL V15 PTF: RO33156

MSGSEVERITY_JRCV011=W Lets you change the severity of Point In Time Recovery (PITR) message JRCV011 from an “E” (error) level severity to a “W” (warning) level severity and the return code value from 12 to 5.

Message JRCV011 is issued during PITR when an incomplete transaction is found. Incomplete transactions generally occur when not all of the applicable journal files are included in the recovery process.

ENCOPTBL V15 PTF: RO35964

PACKAGE_SHIP_WITH_ALTID=ON For CA CMEW only. Lets you specify that API Package Ship JCL is submitted to the internal reader under the context of the CA Endevor SCM Alternate ID, when the request is initiated from CA CMEW. The default value is off, meaning the JCL is submitted to the internal reader under the context of the user ID.

ENCOPTBL V15.1 NO_EXCP=ON This option, to turn off EXCP processing for old XA systems, is obsolete and has been removed from the delivered Optional Features table.



Package Ship for USS Supported Files

UNIX System Services (USS) supported files can now be shipped using the Package Ship utility. Files of the Hierarchical File System (HFS), the zSeries File System (zFS), and the Network File System (NFS) are supported. This enhancement includes the following product changes:

■ To create required backout files, include the ENUSSUTL utility in the processor that is associated to the element type of the USS supported files. For more information about ENUSSUTL, see Backout Information for USS Files (see page 62).

■ The Package Ship transmission methods local, XCOM, and Connect Direct now support the shipment of HFS, zFS, and NFS file outputs. For this capability, use the updated JCL members, which are supplied with this release.

■ The Package Ship utility requirement that you create a destination for each remote site to which you plan to ship package outputs includes the following changes for USS supported files:

– Destination—A destination can now be defined as a USS supported path and file name with a path name value of up to a 732 bytes.

– Host and Remote staging areas—When creating the destination, you define a prefix for the staging path names that CA Endevor SCM builds in the first step of the ship utility. For USS supported files, the new Host Path Name Prefix and the Remote Path Name Prefix fields let you specify prefixes of up to 732 bytes.


62 Release Notes

– Mapping rule—The mapping rule maps production USS directories at the host to corresponding production USS directories at the remote site. To create a mapping rule for USS supported files, you use the new CU option on the Create/Modify Destination panel. Both the Host Path Name and Remote Path Name or mask can be up to 768 characters in length.

■ You can modify a mapping rule for USS support files using the new DU option on the Create/Modify Destination panel.

■ You can test a mapping rule for USS support files using the new TU option on the Create/Modify Destination panel.

Note: Batch admin is not available in Release 15.1 for creating USS mapping rules and placing USS staging directory information into package ship destinations. To perform these tasks, use the ISPF interface.

■ The Package Display panel includes a new option BU, which opens a USS Backout Information panel. This panel lets you view each file name and path that was backed out. For more information about this panel, see Display Package Backout Details for USS Supported Files (see page 63).

■ The API function list package backout information is updated to add several new fields to the ALBKO_RS response structure. These fields map the backout data for USS supported files. For more information about this API function, see the topic ALBKO_RS Response Structure Fields in the API Guide.

Note: HFS, zFS, and NFS file outputs do not appear in element component lists.

Note: If you experience problems with the execution of USS commands in the package shipment process, IBM APAR OA39558 addresses several issues regarding the shipment of USS files and the use of a CA Endevor SCM alternate ID. Symptoms include, but are not limited to, the following: messages FSUM9209 and EDC5112I and reason code 0b8c014c.

Note: For more information about the Package Ship utility, see the Package Ship scenario-based knowledge document. You can access this document from the Knowledge Based Article section of the HTML bookshelf.

Backout Information for USS Supported Files

Package outputs for USS supported files can be transmitted to other sites using the Package Ship utility. However, the outputs cannot be shipped unless information is available that enables the outputs to be backed out. To collect this backout information, the processor that is associated to the element type of the USS files must include a job step for the ENUSSUTL utility.

The execution of the ENUSSUTL utility program in a processor copies user-selected USS files to the user-specified USS directory. Then backout files and backout records are created for the USS outputs. If the utility does not execute under a package, or if the package is not backout enabled, backout records and files are not created.



Display Package Backout Details for USS Supported Files

The Package Display panel provides information about a specific package, such as a description of the package, its status, and so on. If a package contains HFS, zFS, or NFS files that were backed out, you can view information about these files.

Follow these steps:

1. Type 1 in the Option field on the Package Options Menu and a fully qualified name in the PACKAGE ID field. Press ENTER.

The Package Display panel opens for the package you specified.

2. Enter BU on the Package Display panel.

The USS Backout Information panel opens, which details each file name and path that was backed out.

Eclipse-Based UI Enhancements

You can now use the Eclipse-Based UI to perform Move or Generate actions. In addition, you can set defaults for the action options and set a timeout value for the Axis2 connection for all the currently available service calls (actions).

Set Action Options Preferences

You can set defaults for the action options, which define how an action is processed. Setting the defaults helps speed up your work. When you perform an action, the defaults are used. However, you can change the defaults when you perform a specific action, if you enable this function in the Action Option Preferences dialog.

The action options for which you can set your preferences (defaults) are as follows:

■ Move

■ Generate

To set your action option preferences

1. Click Window, Preferences from the Eclipse main menu.

2. Click + to expand the Team category in the Preference panel, expand the CA Endevor SCM subcategory, and then select Action Options.

The Action Options defaults dialog opens.

3. Select a tab and complete the fields. Select the Always open CA Endevor SCM Action Option checkbox, if you want to enable the user to changes the defaults when performing an element action. Click OK or Apply to save your changes.

Your preferences are set as the defaults.


64 Release Notes

Move or Generate an Element

The Move and Generate actions can be performed in the Eclipse-Based UI. If the Action Options dialog is enabled, you can change the action option defaults when you move or generate an element. For more information about enabling the Action Options dialog, see Set Action Options Preferences (see page 63).

To Move or Generate an Element without the Action Options dialog enabled

1. Right-click on the element you want to move or generate in the Projects View, Search View, or Element View.

2. Click Move or Generate from the pop-up menu.

The Move or Generate action request is built and submitted to the server. A Progress Information message is displayed until the action completes processing.

Messages display in the CA Endevor SCM Messages Log View indicating whether the action was successful.

To Move or Generate an Element with the Action Options dialog enabled

1. Right click on the element you want to move or generate in the Projects View, Search View, or Element View.

2. Click Move or Generate from the pop-up menu.

The Move Action Options dialog or the Generate Action Options dialog appears with your preferences pre-filled. Change options as necessary.

3. Click OK.

The Move or Generate action request is built and submitted to the server. A Progress Information message is displayed until the action completes processing.

Messages display in the CA Endevor SCM Messages Log View indicating whether the action was successful.



Set AXIS2 Timeout Value

You can set a timeout value for the Axis2 connection for all the currently available service calls (actions). The value you set defines the time period after which the service call will timeout, resulting in a failed request.

To set your AXIS2 timeout value

1. Click Window, Preferences from the Eclipse main menu.

2. Click + to expand the Team category in the Preference panel, expand the CA Endevor SCM subcategory, and then select Connection.

The Connection dialog opens.

3. Enter a value in the Axis2 Timeout field. Click Apply and OK.

Axis2 Timeout

Specifies the timeout value. Valid values are 30 through 999 seconds. The default is 120.

Your timeout value is set.

How to Install and Configure the Apache Tomcat Server

This procedure describes how to build a Tomcat instance and how to deploy Web Services to the Tomcat instance.

Note: This topic discusses the minimum requirements to install and configure Tomcat. For more information, see the Tomcat documentation at http://tomcat.apache.org/tomcat-6.0-doc/index.html.

Perform the following steps in a UNIX System Services (USS) environment to deploy and configure Web Services into an Apache Tomcat server on your z/OS system:

Note: If Tomcat is already installed and configured, you can skip to the step Deploy Web Services to an Existing Tomcat Server.

1. Determine configuration parameters.

2. Establish environment variables.

3. Run the installation and configuration script.

4. Edit the Apache Tomcat configuration file.

5. Edit the JCL to start the Apache Tomcat server.


66 Release Notes

6. Start the Apache Tomcat server.

7. Verify the installation and configuration.

8. Deploy Web Services to an Existing Tomcat Server.

9. (Optional) Configure Web Services to use HTTPS.

Note: For more information about installing and configuring Tomcat, see the appendix "Web Services" in the Installation Guide.

ELIB Support for Z/OS VSAM Extended Addressability

The ELIB data set format supports z/OS VSAM extended addressability (VSAM EA) for VSAM data sets. The extended addressability feature lets you allocate VSAM data sets that are larger than 4 GB. CA Endevor SCM recognizes when extended addressability is enabled for a VSAM ELIB data set and operates accordingly.

Although there is no need to modify CA Endevor SCM to support the VSAM extended addressability EA option, this option must be enabled at your site by your storage administrator. Ask your storage administrator whether z/OS VSAM extended addressability is available for your site and how you can implement it. Your storage administrator assigns the DATACLAS/STORCLAS names to use for extended addressability and may have implemented other restrictions or requirements at your site.

Note: CA Common Services Version 14 (with CA LServ PTF RO47492 applied) is the minimum version required for CA L-Serv support of VSAM EA.

BSTCOPY Utility Improvements

The processor utility BSTCOPY has been redesigned to make it more efficient. In addition, the sequence of the reported copy actions is improved, so that the member select statements line up with the input and output DD statements.

Report Formats Consistent

Some reports have been reformatted for consistency. On all reports, the following now look the same: the format of the date and the location of the date and page number in the heading.

Documentation Set Changes for Release 15.1


Documentation Set Changes for Release 15.1

The guides of the documentation set have been updated to include descriptions of the enhancements and features introduced in Release 15.1. In addition, the following scenario-based knowledge documents are introduced in this release:

■ Concurrent Action Processing—Describes how to set up, use, and manage the performance enhancing feature Concurrent Action Processing.

■ Package Ship—Describes how to set up, use, and manage the Package Ship utility that enables you to ship package outputs from a local site to a remote site.

You can find these scenarios on the bookshelf in the Knowledge Based Article section.


Appendix A: Modified Nonprogram Product Components


Nonprogram Product Components Modified in Release 15.1 (see page 69)

Nonprogram Product Components Modified in Release 15.1

The following list identifies nonprogram product components that were updated after Version 15.0 was made available. If your site has customized any of these members, you may need to reapply your customizations to the updated members. The members are listed under their target library.

■ CSIQCLS0—Target library for CLISTs and ROSCOE RPFs

– C1SR1400

■ CSIQMENU—Target library for ISPF messages

– PKMR31

– PKMR28

– PKMR10

– PKMR35

– PKMR30

– CPTB16

– IMGR25

■ CSIQOPTN—Target library for COBOL copybooks, parameter members, and Assembler macros

– $PBODREQ

– #PSNDVRX

– #PSNWDMS

– #PSNWDMT

– #PSXCOMS

– #PSXCOMT


70 Release Notes

– #RJFCPY1

– #RJFCPY2

– #RJFCPY6

– #RJICPY1

– #RJICPY2

– #RJICPY6

– @C1UEXIT

– BSTTRD06

– ECHALELM

– ENHALBKO

– ENHALELM

– ENHOPT

– ENHOPTNS

– PKGXBLKS

– WSEWSCCI

■ CSIQPENU—Target library for ISPF panels

– CITBKEN0

– CITC1400

– CITC1410

– CITC1420

– CITC1430

– CITC1440

– CITC1450

– CITC1500

– CITC1510

– CITC1520

– CITC1530

– CITC1540

– CITC1550

– CITES020

– CITE3100

– CITHUSS0

– CITMRUL0



– CITM1000

– CITNDVR1

– CITPD200

– CITPD500

– CITPD600

– CITPD700

– CITPD800

– CITP1000

– CITP1100

– CITP1400

– CITP1410

– CITRUSS0

– CITSTDS0

– CITT0000

– CIT15100

– CIT15110

– CIT15120

– CIT15130

– CIT15140

– CIT15150

– C1SES000

– C1SE2100

– C1SE4102

– C1SFC100

– C1SPD10D

– C1SPD20#

– C1SPD20D

– C1SPD20M

– C1SPD50D

– C1SPD50S

– C1SPD60D

– C1SPD70D

– C1SPD70E


72 Release Notes

– C1SPD70F

– C1SPD80C

– C1SPD80D

– C1SPD80M

– C1SPD80T

– C1SP1000

– C1SP1400

– C1SP1410

– C1SP1411

– C1SP1412

– C1SP1413

– C1SP6000

– C1SSEL3

– ENDHEO00

– ENDHEO10

– ENDHEO20

– ENDHEO30

– ENDHE100

– ENDHE110

– ENDHE120

– ENDHE130

– ENDHE131

– ENDHE132

– ENDHE140

– ENDHE141

– ENDHE150

– ENDHE200

– ENDHE210

– ENDHE220

– ENDHE230

– ENDHE240

– ENDHE250

– ENDHE260



– ENDHE265

– ENDHE270

– ENDHE280

– ENDHE290

– ENDHE300

– ENDHE400

– ENDHE900

– ENDHE910

– ENDIEH10

– ENDIEH91

– ENDIEH92

– ENDIEH95

– ENDIEH98

– ENDIEO00

– ENDIEQE1

– ENDIEQE2

– ENDIEQE3

– ENDIE100

– ENDIE110

– ENDIE250

– ENDIE410

– ENDIE500

– ENDIE700

– ENDIE710

– ENDIE900

– ENIP1000

– ENIP3000

– ENIT1010

■ CSIQSAMP—Target library for sample application processors, jobs, elements, and so on

– CICSMAP

– IMSDBD

– JCLCHK


74 Release Notes

– NCPYPRCS

– DFIIMAP

■ CSIQSENU—Target library for ISPF skeleton JCL

– C1BMXBPX

– C1BMXCOM

– C1BMXDEL

– C1BMXEND

– C1BMXHCN

– C1BMXHJC

– C1BMXJOB

– C1BMXNDM

– C1SSPR90

– ENDES000

– ENSP1000

Appendix B: Known Issues 75

Appendix B: Known Issues

Published Fixes for Release 15.1.00

All published fixes are available at Published Solutions on CA Support.


Appendix C: Accessibility Features

CA Technologies is committed to ensuring that all customers, regardless of ability, can successfully use its products and supporting documentation to accomplish vital business tasks. This section outlines the accessibility features that are part of CA Endevor SCM.

Product Enhancements

This section summarizes the accessibility of CA Endevor SCM as tested for Section 508 compliance using a 3270 emulator and the Eclipse user interface. In addition, the accessibility of product documentation and support is described.

3270 Emulator Access

When accessed through a 3270 emulator, CA Endevor SCM offers the following accessibility:

■ All functions can be performed using the keyboard only.

■ The product inherits the following OS accessibility features:

– Sticky keys

– Filter keys

– Toggle keys

– Mouse keys

– Serial keys

Exceptions: The product does not inherit changes to OS contrast settings. This attribute is outside the control of the product, because the user emulator controls this attribute.

■ A well-defined on-screen indication of the current focus is provided programmatically. Use of the Tab key can place the cursor unexpectedly on unprotected fields, which can hinder screen reader accessibility.

■ The application uses user interface elements with visual semantics that are not programmatically available to assistive technology through the emulator. This exception limits accessibility for AT users.

■ Textual information is provided through operating system functions for displaying text.


78 Release Notes

■ Color and contrast are changeable by the user in the emulator; the product inherits these changes. A variety of color combinations that can create various degrees of contrast are available in the emulator: black text on white background, blue text on white background, yellow text on black background.

■ Electronic forms in the product can be completed using the keyboard. However, a screen reader is unable to prompt users to fill in form fields, requiring the screen reader user to examine the textual screen content to determine what fields are present.

■ This product supports the use of Assistive Technology screen readers by blind and visually impaired users. However, screen readers do not have access to user interface element semantics, requiring the user to examine the textual screen content to determine available options, entry fields, keyboard shortcuts, and application responses.

■ This product does not require user hearing or speech.

■ This product can be used in a mouseless, keyboard-only mode. In addition, the product supports OS accessibility features.

Eclipse Access

When accessed through Eclipse, CA Endevor SCM offers the following accessibility:

■ Most functions can be performed using the keyboard only. However, there are exceptions. The following functions cannot be accessed using the keyboard only:

– Some toolbar icons in the Repository View, Project View, CA Endevor SCM Log View.

– Drag and drop views.

– Min and max toolbar icons.

■ The product inherits the following OS accessibility features:

– Filter keys

– Toggle keys

– Serial keys

– High Contrast

Exceptions: The shortcut keys Ctrl+F6 and Ctrl+F7 do not function properly with Sticky keys. Drag-and-drop views cannot be performed with Mouse keys.



■ A well-defined on-screen indication of the current focus is provided programmatically, but with exceptions. The screen reader cannot track focus and focus changes for:

– Toolbar icons in the Views

– Tool tips for toolbar icons in the Views when using Mouse keys

■ The product provides sufficient information about UI elements with the following exceptions.

– Tooltips are not provided for the Project View, Element View and CA SCM Log View.

– The screen reader cannot read the online help icon in the New Repository & Project creation Wizards.

■ Bitmap images have consistent meaning with the following exceptions:

– The same icon is used in different menus for different functions.

– Different icons are used for the same function in views.

– The same icon is used for different functions in different views.

– The same icon is used to represent different views.

– The ASCII art used in element listings is not supported by Assistive technology.

■ Textual information in the product is provided through the operating system. The minimum information listed in the criterion is made available.

■ The product inherits OS settings for color, contrast, and fonts. The contrast ratio is 4.5:1 or greater.

■ In most cases, color coded information is also conveyed by text. However there are exceptions. For example, the images that are used to represent systems, subsystems, environment, and so on, do not have text equivalents.

■ The product does not permit users to adjust color and contrast. However, the product inherits user settings for color and contrast from the OS.

■ Most forms are changeable by users of Assistive Technology. However there are exceptions. For example, the screen reader cannot read error messages in New Repository creation and Project definition forms.

■ The product provides some support for the use of screen readers by blind and visually impaired users, but with exceptions.

■ The product supports the use of screen magnifiers by visually impaired users.

■ This product does not require user hearing or speech.


80 Release Notes

■ Title bars of Application windows and dialogs have titles that describe the topic or purpose. For example:

– Project View, Repository View, Search Map View, Element View windows have titles that describe the purpose.

– The dialog windows for New Repository & Project definition have titles that describe the purpose.

■ Help content uses links and link text that describes the purpose of each link.

■ The application provides headings and labels that describe a topic or purpose. For example:

– The New Repository & Project definition window uses headings and labels that describe the purpose of window and fields.

– The Element View & Log View tabs use headings that describe the purpose of each tab.

■ The screen reader reads text in the correct natural language. For example:

– New Repository & Project definition dialog windows heading and labels are read correctly in the default natural language.

– The text in the online help contents is read correctly in the default natural language.

■ The application provides consistent navigation across views and screens. The navigation through screens for New Repository & Project definition dialogs is consistent.

Product Documentation and Support

CA Endevor SCM documentation and support are provided as follows:

■ Product documentation is available in 508-compliant HTML.

■ Support is available as follows:

– Online and email support for customers with hearing disabilities.

– Telephone support for customers with visual disabilities.

Documents

CA Endevor® Software Change Manager · Chapter 1: Welcome 7 What this Release Notes Covers ... SCM User Options Menu is now accessible from the CA Endevor Quick-Edit Option panel