There are changes to the following utility programs:
The CSD utility program is enhanced to support new and changed resource types and attributes. See Resource definition (online) changes for details of all the changes to CSD resource definitions that are supported by DFHCSDUP.
If you are sharing the CSD with earlier releases of CICS®, and want to alter definitions that are used only on earlier releases, you must use the latest DFHCSDUP, even if some attributes are obsolete in the latest releases of CICS. To use the latest DFHCSDUP to update obsolete options on resource definitions, specify the COMPAT option in the PARM string to indicate that you want DFHCSDUP to operate in compatibility mode.
The program is enhanced to format additional statistics reports for the new resource types.
These resource types can be coded on the SELECT TYPE and IGNORE TYPE parameters using the keywords
See the CICS Performance Guide for details of statistics data.
The trace formatting utility program is renamed to DFHTU640, where 640 is the level number of CICS. Always ensure you use the trace program with the correct level number for the release of CICS TS that created the trace data set you are formatting.
The program is enhanced to format trace entries written by the new domains and functions. The new identifiers that you can specify to DFHTU640 on the TYPETR parameter for these functional areas are the same as the CETR trace component codes.
See Changes to CETR for a list of these.
The dump formatting utility program is renamed to DFHPD640, where 640 is the level number of CICS. Always ensure you use the dump formatting program with the correct level number for the release of CICS TS that created the dump data set you are formatting.
The dump exit routine for formatting CICS system dumps is enhanced to format the control blocks for the new domains. To select or ignore dump data for any domains, specify the dump component keywords for those domains. The dump component keywords for use with the CICS IPCS dump exit routine are the same as the CETR trace component codes. See Changes to CETR for a list of these.
You can now use the Resource Manager for Enterprise Beans to determine which version of GIOP is advertised in the published IOR for a specific enterprise bean.
For details of the Resource Manager for Enterprise Beans, see the CICS Operations and Utilities Guide.
CICS TS for z/OS, Version 2.3 ships with WebSphere Application Server Version 5. This section describes how the WebSphere® utilities used with CICS differ from their counterparts in WebSphere Application Server Version 4, which was shipped with CICS TS for z/OS, Version 2.2.
The Assembly Toolkit (ATK) and the Application Assembly Tool (AAT) can both be used to deploy enterprise beans for use with CICS TS for z/OS®, Version 2.3. It is recommended that you use the most recent version available to you.
If you are using ATK to deploy your enterprise beans, you can choose the format that is used for saving each ejb-jar file, such as EJB 1.1 or EJB 2.0. It is recommended that where possible, you create deployment descriptors for EJB 1.1.
The AAT supplied with WebSphere Application Server Version 5.0 (but not that supplied with WebSphere Application Server Version 4.0) supports EJB 2.0 JAR files. If you use the WebSphere Version 5.0 AAT to edit an EJB 1.1 ejb-jar file, by default AAT saves the edited file in EJB 1.1 format. However, if you create a new ejb-jar file, AAT saves it in EJB 2.0 format.
Although CICS currently supports only Version 1.1 of the Enterprise JavaBeans specification, it tolerates EJB 2.0 JAR files. It ignores any 2.0-specific features in the deployment descriptor, except for local interfaces. (If you try to deploy an EJB 2.0 JAR file that contains local interfaces, CICS issues an error message and the JAR file becomes unresolved.)
The COS Naming Directory Server supplied with WebSphere Application Server Version 5 differs from that supplied with WebSphere Application Server Version 4. From Version 5 onwards:
The recommended way to specify the location of your name server is on the com.ibm.cics.ejs.nameserver property in the JVM system properties file. If you use the COS Naming Directory Server supplied with WebSphere Application Server Version 5, you should specify the location like this:
com.ibm.cics.ejs.nameserver=iiop://mycsserv.hursley.ibm.com:2809/domain/legacyRoot
For more information, see the CICS System Definition Guide.