Summary of CA 2E Change Management Features

Managing Model Objects › Components of CA 2E Change Management › Summary of CA 2E Change Management Features

Summary of CA 2E Change Management Features

The following table summarizes CA 2E change management features. For each feature, the table shows whether the feature is provided as part of CA 2E's change control facilities or by CM and where to find more information about the feature.

Feature	CA 2E Change Control Facility	CM Change Management	Where Documented
Work with Model Objects Utility	Yes	Yes	This chapter, Working with Model Object Lists section
Model User Profile	Yes	Yes	This chapter, Model Profile section
impact Analysis Utilities	Yes	Yes	This chapter, Model Object Audit Information section
Model Object Change Tracking
Model Object List Processing	Yes	Yes	This chapter, Model Object Lists section
Redirect Function References	Yes	Yes	This chapter, Working with Versions of Functions and Messages section, Making a Version Current section
Versions of Functions and Messages	Yes	Yes	This chapter, Working with Versions of Functions and Messages section
Session List	Yes	Yes	This chapter, Model Object Lists section, Session Lists section
Global Browse-only Access to Model	Yes	Yes	Administrator Guide
Copying Model Objects Between Models	Yes	Yes	This chapter, Editing Model Object Lists section, Copying Model Objects section, Admin-istrator Guide, and the Command Reference
Check Out	No	Yes	CM User Guide
Automated Version Control	No	Yes	CM User Guide
Access Control	No	Yes	CM User Guide
Automated Rollback of Functions and Messages	No	Yes	CM User Guide
Automated Concurrent Development	No	Yes	CM User Guide
Authority to Model Object Lists	No	Yes	CM User Guide
Promotion Capabilities	No	Yes	CM User Guide
Analysis of Context of Change and Rollback	No	Yes	CM User Guide

New Features of CA 2E r8.7 and Implementer 11.0 + PTC Patch 948724

CA 2E r8.7 with Implementer 11.0 and PTC patch 948724 now allows you to do the following tasks:

Promote *DDL-based objects from one environment to another.
Convert between *DDS and *DDL generation modes for objects in Production. You can check out *DDS PFs / LFs, convert them to *DDL tables / indexes and promote the new *DDL objects. You can check out *DDL tables / indexes, convert them to *DDS PFs / LFs and promote the *DDS objects to Production.

During the promotion request creation involving *DDL objects, a *DDL table takes the YSQLPF object code and a *DDL index takes the YSQLLF object code.

CM does not support "promotion with compile" for SQL-based access paths. The only way to promote them is with "promotion with moving as a 3GL object." When attempting to promote *DDL objects, this same process is followed.

For more information, see the Implementer 11.0 documentation for patch 948724 https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS176520.

Limitations:

For CM Promotion of DDL Objects (Not Switched from DDS):
- If the database is implemented with YSQLVNM = *SQL, irrespective of generation mode as *SQL/*DDL, the promotion of "physical file"/"table" access paths is not successful.
For CM promotion of DDL objects (DDS to DDL Conversion):
- When attempting a *DDS to *DDL / *DDL to *DDS conversion, you must generate the *DDS / *DDL objects into the same object library.
- The new CM functionality only caters to *DDS to *DDL / *DDL to *DDS conversions. *DDS to *SQL / *SQL to *DDS conversions are not supported. We recommend you not to carry out a *DDS to *SQL / *SQL to *DDS conversion.