Upgrading applications, platforms, and bundles

If you use platforms, applications, and CICS® bundles, you have some changes to make when you upgrade your version of CICS.

V5.1

Declare application entry points for PROGRAM and LIBRARY resources

From CICS TS 5.2, applications that are deployed on platforms must declare application entry points for all the resources, such as PROGRAM or LIBRARY resources, that are access points to the application. Application entry points control users' access to different versions of an application that is deployed on a platform. An application that defines a PROGRAM or LIBRARY resource cannot be made available to callers in regions later than CICS TS 5.2 regions unless it declares an application entry point for that resource.

Application entry points only control users' access to the resources that are specified in the application entry points. If an application includes any public resources that are not named as application entry points, when the application is installed and enabled, these resources can be accessed by other applications that are installed on the platform or in the CICS region, regardless of the availability status of the application. Private resources for an application version cannot be accessed by other applications.

For information about declaring application entry points, see Defining application entry points in the CICS Explorer product documentation.

V5.1

Make applications and CICS bundles available

From CICS TS 5.2, for applications that are deployed on platforms, you can install and verify the installation of an application version before you make the application version available to users of the platform. As a consequence, you must take an additional step to make available the applications that are deployed on platforms in CICS regions from CICS TS 5.2. After you install and enable the application, perform the Make Available action in the CICS Explorer® to make the application available to users. You can make an installed application version available or unavailable in the Cloud Explorer view, or in the application descriptor editor for installed applications.

From CICS TS 5.2, stand-alone CICS bundles that contain application entry points must also be made available. After you install and enable the CICS bundle, you set the CICS bundle to available. To do this, perform the Make Available action in the CICS Explorer, or use the AVAILSTATUS option on the EXEC CICS SET BUNDLE command. CICS bundles that are deployed with platform bundles, or added to a platform, do not require the Make Available and Make Unavailable actions because these actions are performed on the application entry points for applications.

Before you disable or discard an application that is deployed on a platform in CICS regions from CICS TS 5.2, you must perform the Make Unavailable action in the CICS Explorer . Before you disable or discard a stand-alone CICS bundle that contains application entry points, you must perform the Make Unavailable action in the CICS Explorer , or use the AVAILSTATUS option on the EXEC CICS SET BUNDLE command to set the status of the CICS bundle to UNAVAILABLE.

If your platform includes any CICS regions that are still at CICS TS 5.1, the Make Available and Make Unavailable actions are not required or supported for applications or stand-alone CICS bundles installed in those CICS regions. In CICS TS 5.1 regions, applications or stand-alone CICS bundles are assumed to be available when they are enabled with the Enable action, and unavailable when they are disabled with the Disable action, as was the case for all applications in CICS TS 5.1.

V5.1

Ensure that operation names are unique

Each application entry point names an operation. For example, you can declare application entry points for create, read, update, or delete operations in the application. In CICS regions from CICS TS 5.2, an operation name must now be unique within an application. An application cannot be made available to callers in regions later than CICS TS 5.2 if it contains duplicate operation names. Operation names are case-sensitive, so you can use operation names that are differentiated only by case, such as "browse" and "Browse".

V5.2

If your application has URIMAP resource and URIMAP entry point in different CICS bundles, review the change in availability

If you have applications where the URIMAP resource and URIMAP entry point are in different CICS bundles in the application, you might want to take action to control the availability of the URIMAP resource.

In CICS TS 5.2, the availability of the application does not restrict the work that comes in through the enabled URIMAP resource. So, you can apply or remove the application context by making the application available and unavailable, without affecting the work that runs through the URIMAP. In CICS TS 5.3, the URIMAP resource adheres to the application availability. So, work stops coming through the URIMAP resource when the application is made unavailable.

This behavior is appropriate for most situations. However, if you want to preserve the CICS TS 5.2 behavior of the URIMAP resource that is defined as an entry point (that is, it does not change its availability in line with the availability of the application), then define the URIMAP resource outside the CICS application.



upgrade_platforms.html | Timestamp icon Last updated: Sunday, 4 June 2017