SET BUNDLE

Use the SET BUNDLE command to change the status of an installed BUNDLE resource, which represents a CICS® bundle.

SET BUNDLE

Conditions: INVREQ, NOTAUTH, NOTFND

This command is threadsafe.

Description

Use the SET BUNDLE command to change the status of standalone CICS bundles.

The SET BUNDLE command does operate on a CICS bundle that was installed for an application in a single CICS region, but it is not intended for normal management of CICS bundles for applications. For CICS bundles that are installed as part of an application deployed on a platform, in CICS Explorer®, use the Cloud Explorer view in the CICS Cloud perspective to work with the application. Actions that you perform on the application are applied to all the CICS bundles for the application. If you need to troubleshoot the status of an individual CICS bundle for the application, you can also use CICS Explorer to investigate problems with the individual bundles across multiple CICS regions.

A successfully installed CICS bundle can be in an enabled or disabled state, and also in an available or unavailable state, in the CICS regions where it is installed. If the CICS bundle is in a disabled state or in an unavailable state, the resources for the CICS bundle have been dynamically created, but they cannot yet be used.

For a CICS bundle that declares application entry points, you must first enable the bundle, then make it available, to give users access to the resources. When you make the bundle available, CICS gives callers access to the application entry points, which enables them to access all the resources in the CICS bundle.
For a CICS bundle that does not declare application entry points, you only need to enable the bundle. Resources that are not controlled by application entry points are available to users as soon as they are enabled.

Before you uninstall a CICS bundle, you must remove users' access to it and disable it. You can then discard the BUNDLE resource for a standalone CICS bundle, or uninstall the application for which the CICS bundle was installed.

For a CICS bundle that declares application entry points, you must first make the bundle unavailable, then disable it.
For a CICS bundle that does not declare application entry points, you do not need to make the bundle unavailable. You only need to disable it.

You must issue separate SET BUNDLE commands to specify AVAILSTATUS, COPY and ENABLESTATUS. CICS must complete each operation separately to ensure the integrity of the state of the CICS bundle.

Options

AVAILSTATUS(cvda)

Changes the status of the BUNDLE resource that represents the CICS bundle. CVDA values are as follows:

AVAILABLE: CICS gives callers access to the resources identified in the CICS bundle as application entry points, so that they can access all the resources in the CICS bundle.
UNAVAILABLE: CICS removes access to the resources identified in the CICS bundle as application entry points, so callers cannot access any of the private resources in the CICS bundle.

ENABLESTATUS(cvda)

Changes the status of the BUNDLE resource that represents the CICS bundle. CVDA values are as follows:

ENABLED: CICS tries to enable the BUNDLE resource, and to enable the resources that have been dynamically created for the CICS bundle in the CICS region.
DISABLED: CICS tries to disable the resources that have been dynamically created for the CICS bundle in the CICS region, and to disable the BUNDLE resource.

COPY(cvda)

Specifies that the highest semantic version of each OSGi bundle is to be registered with the OSGi framework and used for all subsequent requests. The CVDA value is as follows:

PHASEIN: Determine the highest semantic version of all OSGi bundles in the root directory for the CICS bundle and register that version with the OSGi framework if its not already registered. Any previously registered version is removed from the OSGi framework. The new version will be used for all subsequent service requests but any active requests will continue to use the old version until the request completes.

Conditions

INVREQ

RESP2 values:

4: An invalid CVDA value was specified for ENABLESTATUS.
6: An attempt was made to enable or disable a BUNDLE resource that is in an invalid state.
7: CICS failed to link to the registered bundle callback program.
9: The BUNDLE resource cannot be enabled.
10: An attempt was made to set the availability of a BUNDLE resource that contains no application entry points.
11: An attempt to make the BUNDLE resource available failed because the bundle is not enabled.
12: The BUNDLE resource failed to set the availability of the bundle.
13: An attempt to disable the BUNDLE resource failed because the bundle is not unavailable.
14: An invalid CVDA value was specified for AVAILSTATUS.
15: Both ENABLESTATUS and AVAILSTATUS were specified on the command.
16: The COPY option was specified but the bundle is not enabled.
17: Both COPY and AVAILSTATUS or ENABLESTATUS specified on the same command.
18: An invalid CVDA value was specified for COPY.
19: The COPY option is not allowed as the bundle is part of an installed platform or application. To update a bundle that is deployed as part of an application, see Managing applications.
20: The COPY option was specified but the CICS bundle contains no OSGi bundle references.
21: The COPY(PHASEIN) option was specified but the phasein operation failed.

NOTAUTH

RESP2 values:

100: The user associated with the issuing task is not authorized to use this command.
101: The user associated with the issuing task is not authorized to access this particular resource in the way required by this command.

NOTFND

RESP2 values:

3: The BUNDLE was not found.