Downloading and installing the CICS Deployment Assistant plug-in
To
download the CICS® Deployment
Assistant plug-in from the download website:
- Click the CICS Deployment
Assistant plug-in download link.
- Save the compressed file in a temporary directory. Do NOT extract
the file. The CICS Explorer® extracts
the contents automatically.
To install the CICS Deployment
Assistant plug-in in the CICS
Explorer:
- Start the CICS Explorer.
- Click Help on the CICS Explorer menu bar and click Install
New Software in the menu. The Install window
is displayed.
- Click Add. The Add Repository window
is displayed.
- Click Archive. The Repository
archive window is displayed.
- Locate and select the CICS Deployment
Assistant plug-in compressed file you downloaded previously, and click Open.
- Click OK in the Add Repository window.
The window closes and the tool is displayed in the Software Updates
and Add-ons window.
- Click Select All, and then click Next.
- In the Install window, confirm the installation
by clicking Next.
- Review the license and select the relevant check box. Click Finish to
complete the installation, or Cancel if you
do not accept the license terms.
- If you accepted the license, the CICS Deployment
Assistant plug-in is installed into the CICS Explorer. You are prompted to
restart the CICS Explorer to
ensure that the CICS DA plug-in starts in a clean environment.
Back to Contents
Getting started
If
you are not familiar with CICS Deployment Assistant, you can read
the Getting Started information in the help documentation. Click to display the information
to get you started.
Back to
Contents
Known issues and limitations
The
following limitations exist in CICS Deployment Assistant V5.1:
- If you run discovery, and later change the APPLID of a managed
CICS region but do not change the SYSID, then the next time you run
discovery, the CICS region is shown twice. The region with the new
APPLID is shown as an unmanaged CICS region. The region with the old
APPLID is shown as a managed CICS region. To resolve the problem you
must delete both regions from the model, and then run discovery again.
- When a region is cloned, if the data set names of the new region
are longer than the data set names of the original region, it is possible
that the generated JCL might be invalid. The clone operation completes
successfully, but you might get a JCL error when the region is started.
The JCL error occurs when one or more lines that contain the longer
data set names, now exceed the 72 character limitation. The problem
can be resolved by manually editing any such generated JCL lines.
Back to Contents