| CA Technologies |
4.0 Installation Considerations
4.1 Special Considerations
4.2 Documentation Installation
4.3 CA 2E Change Management Option
4.4 Toolkit Pre-compile Processor
6.0 Known Issues
6.1 Web Option Limitations
6.2 HTML Bookshelf Search Results
8.0 Documentation
8.1 HTML Bookshelf
Welcome to the CA 2E Readme. This readme contains issues and other information discovered after publication. For a complete list of the known issues and details about how the features and enhancements effects your system, see the Release Notes for Release 8.6.
Release 8.6.00
| Product | Fix Level | Data Level | Model Level |
|---|---|---|---|
| CA 2E | 1547 | 128 | 49 |
| CA 2E Toolkit | 1081 | ||
| CA 2E Web Option | 399 | 104 |
CA 2E and Web Option require IBM i (i5/OS) version V5R4 or higher.
Web Services Support requires IBM i (i5/OS) version V5R4 or higher.
Additional V5R4 PTFs are required. For more information, see the Chapter "Web Service Creation", section "Required IBM PTFs" in the Building Applications guide.
For instructions about installing or upgrading, see the Installation Guide.
There are three different methods for installing or upgrading the Web Option product: a new installation, an upgrade from r8.5, and an upgrade from versions older than r8.5. Locate the appropriate section for your situation in the Web Option User Guide.
For instructions about installation tasks required for the Web Services Support feature, see the Release Notes, or the Web Service Support section in the Installation Guide.
You can install the CA Release 8.6 documentation set to a Windows PC. See the section HTML Bookshelf for installation instructions.
If you are also upgrading to a new release of CA 2E Change Management Option, you need to contact MKS Support to get the required MKS Security codes for that release.
In CA 2E r8.5, we modified the 1E program YBRTP2R to use a modified version of data area YBRTPXA. If you are upgrading to Release 8.6 from a version older than r8.5, and you want to use your existing 1E data library, you need to delete YBRTPXA from this library. Afterwards, run YCRTY1DTA with your existing library to create a new version of this data area, and then, if necessary, change it to specify any values you previously used.
Failure to address this data area YBRTPXA difference could result in a number of 2E environmental issues including:
CA 2E Release 8.6 uses the same licensing codes used for the CA 2E r8.1 GA release; if you already have a license for r8.1 GA, you do not need to obtain a new license for Release 8.6.
The following are known issues for CA 2E 8.6.00:
A limitation exists with Web Option where it can display a Just-In-Time (JIT) page, even if a skeleton was previously generated for the screen. This limitation only occurs when:
For example, if a window function WinFun (with a confirm prompt) displays, and then, as a result of action on the WinFun page, a different function SelFun is displayed. In this case, when the user leaves SelFun, WinFun is immediately redisplayed with the confirm prompt, and the WinFun page displays in JIT mode.
This limitation occurs because although Web Option is able to determine that a confirm prompt (in its own window) is being displayed, it is unable to retrieve required details of the underlying window, such as its original window offset and attributes, which are required to process field offsets.
This limitation does not effect full-screen functions. It does not effect window functions that initially display without the confirm prompt and then redisplay with the confirm prompt when the user presses Enter.
There are two workarounds to this limitation:
Note: If a window function displays in JIT mode, this is only while the confirm prompt is displayed.When the window function displays without the confirm prompt, the generated skeleton is used. If the window function displays in JIT mode, normal application functionality is retained. However, functions specific to the generated skeleton, such as drop-down lists, are not available.
When you perform a search in the HTML bookshelf, search results for PDF files return summaries with errant HTML code showing under the result. This is a known problem with the indexing software, but does not affect search results and links to the individual guides.
The list of published fixes can be located in the Release Notes and on the CA Support website: http://ca.com/support.
Updated guides for this product are available at http://ca.com/support.
This release contains the CA HTML Bookshelf, which is HTML help system that provides access to all deliverables in the product documentation set, regardless of the file format. The HTML Bookshelf features include:
You must install the HTML Bookshelf separately from the product installation.
To install the HTML Bookshelf
If the CA 2E r8.6 bookshelf was previously installed, setup.exe first uninstalls the bookshelf. After the uninstall process completes, click setup.exe a second time to install the bookshelf.
If the CA 2E r8.6 bookshelf is not currently installed, setup.exe installs the bookshelf to the following location:
Programs > CA > CA 2E r8.6 > Bookshelf
Note: You can also download and extract the CA 2E bookshelf.ZIP file from CA Support Online. To extract the content of a .ZIP file, use an archive program such as WinZip or StuffIt, and choose to extract the content to a local folder. Once extracted, open the Bookshelf folder and click the bookshelf.html file.
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following:
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.
If you would like 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.
Copyright © 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.