What's new in this version

CICS® IA V5.1 delivers a wide range of important new capabilities:

CICS TS application support

In CICS TS V5.1,you can package applications for deployment into a platform. You can now logically define the various resources that make up a business application in CICS as a single entity and deploy these resources to CICS as a single resource. An application that is defined in this way can be managed as a single entity throughout its lifecycle, making CICS application management faster, easier, and less error prone. For more information, see Applications.

The updated CICS IA V5.1 exits capture Application information and associate them with Dependency Data and Command Flow Data collected.

Improved installation and configuration steps

In CICS IA V5.1 the configuration execution is split into two tasks:
  • Configuring the target DB2® Environment.
  • Configuring the CICS regions in which you want to collect data.
"Cheat sheets" are added to the CICS IA plug-in for CICS Explorer® so you can select the configured output sample JCL jobs for both the DB2 and CICS configurations. The Cheat sheets also guide you through the jobs that must run to complete the tasks when you use the "z/OS® perspective" that in the CICS Explorer.

Threadsafe analysis

The ability to run a batch job to report on the "threadsafe" readiness of a particular program or all programs in a particular region is now a DB2 Stored Procedure and can be started with the CICS IA plug-in for CICS Explorer.

DB2 data lifecycle management

You can now delete your CICS IA data by “collection id” and by CICS TS Application definitions. There is a new section on Data lifecycle management in the User Guide.

Native SQL language stored procedures

In CICS IA V5.1 Beta, you can choose to use native SQL language stored procedures or external SQL language stored procedures. Native SQL Stored Procedures are available in DB2 V91 onwards.

A native SQL language stored procedure is used instead of an external SQL language stored procedure, in that the source code is included within the CREATE PROCEDURE statement. The difference is in the executable procedures, and also in a richer SQL language.

When using a native SQL procedure, the entire executable is contained within DB2. The advantage of this approach is that DB2 can manage these stored procedures directly. The stored procedures run in the DBM1 address space, so there is no need to create a WLM environment to manage the procedures. Because native SQL procedures run under an enclave SRB instead of a TCB, if they are remote, they are also eligible to be run in a System z9® Integrated Information processor (zIIP) if one is available.

Updated exits

CICS IA V5.1 Beta provides CICS exits so that you can collect Dependency, Affinity, and Command Flow data in a CICS TS V5.1 region.


Information Information

Feedback


Timestamp icon Last updated: Friday, 8 February 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//ciuugcsoc51.html