Creating a sample initial IT configuration

To try out the scenario in your own environment, set up a platform, and deploy a CICS® application on the platform. The CICS application consists of programs stored in a data set that is included in a dynamic program LIBRARY concatenation. The program that is declared as an application entry point for the application is run by a CICS transaction from a CICS terminal.

About this task

To see an example of a suitable environment and application for this scenario, watch the video Provisioning application updates with no loss of service, which is available on the CICS product website. Figure 1 shows the projects that were set up to create the environment and application for the demonstration:
Figure 1. Projects used for the demonstration
In the Project Explorer view, the projects addProgram.app, addProgram.app_my.demo.platform_binding, addProgram.platform.resources, addprogram.resources, and my.demo.platform are shown. The project addProgram.platform.resources is expanded to show a TRANSACTION resource definition called ADDP.transaction, and the META-INF folder for the project. The project addprogram.resources is expanded to show a PROGRAM resource definition called ADDPG1.program, a PROGRAM resource definition called ADDPROG.program, a LIBRARY resource definition called LIB1.library, and the META-INF folder for the project.
addProgram.app
The CICS application project for the demonstration application.
addProgram.app_my.demo.platform_binding
The CICS application binding project for the demonstration application.
addProgram.platform.resources
A CICS bundle containing the TRANSACTION resource definition for the transaction that runs the demonstration application. This CICS bundle is deployed with the platform bundle.
addprogram.resources
A CICS bundle containing the LIBRARY and PROGRAM resource definitions and the application entry point declaration for the demonstration application.
my.demo.platform
The platform bundle for the demonstration platform.

Procedure

  1. Set up a platform that includes at least one CICS region where you can deploy the application. For the full process to configure a platform, see Setting up a platform. For a scenario example of the process to configure a platform, see the scenario topic Configuring the platform in Scenario: Deploying an application to a platform. For the CICS application used in this application update scenario, you do not need to create JVMSERVER and TCPIPSERVICE resources as described in the final steps of the instructions for that application deployment scenario.
  2. Create the original version of the CICS application, and use CICS Explorer® to create CICS bundles containing the application resources.
    1. Include an easily identifiable bug in the original version of the application. For example, include an error in the output that is displayed to the user. The bug will be fixed in the updated version of the application.
    2. Store the programs for the application in a Partitioned Data Set (PDS) or Partitioned Data Set Extended (PDSE) on z/OS®. You can use the z/OS Explorer to create and work with data sets. For more information, see Working with data sets in IBM Explorer for z/OS V3.0.0 product documentation.
    3. Use CICS Explorer to create a LIBRARY resource definition in a CICS bundle for a dynamic program LIBRARY concatenation that references your data set or data sets. LIBRARY resources are supported as private resources for applications, so they are suitable for use in multi-versioned applications. The same resource name and resource definition are used in the new version of the application, and CICS manages all the instances of the resource. For instructions on how to create CICS resources in a CICS bundle project, see Working with bundles in the CICS Explorer product documentation.
    4. Use CICS Explorer to create PROGRAM resource definitions in the same CICS bundle for the programs for your application. PROGRAM resources are also supported as private resources for applications, so the same resource names and resource definitions can be used in the new version of the application.
    5. Declare one PROGRAM resource as an entry point for your application. Application entry points control users' access to the resources in a multi-versioned application. For instructions on how to define an application entry point in a CICS bundle, see Working with bundles in the CICS Explorer product documentation.
    Tip: In the application used in the demonstration, the LIBRARY and PROGRAM resource definitions and the application entry point declaration are packaged in the same CICS bundle, but the application would function in the same way if they were all packaged in different CICS bundles.
  3. Create a TRANSACTION resource to define a transaction to run the application, and deploy it in the CICS regions that are part of the platform.
    1. Use CICS Explorer to create the TRANSACTION resource in a CICS bundle. For instructions to create CICS resources in a CICS bundle project, see Working with bundles in the CICS Explorer product documentation.
    2. Add the CICS bundle to the platform, deploying it in the region types that contain the CICS regions where you can deploy the application. For instructions to deploy CICS bundles at the level of the platform, see Working with bundles in the CICS Explorer product documentation.
    3. In the CICS bundle where you created the application resources, define the TRANSACTION resource as a dependency, or import. For instructions to define a dependency for a bundle, see Working with bundles in the CICS Explorer product documentation.
    TRANSACTION resources are not supported for multi-versioning in CICS TS Version 5.2, but resources of any type can be defined as a dependency, or import, for a multi-versioned application. The application presents a warning if a resource defined as a dependency is unavailable in a CICS region. Deploying the TRANSACTION resource separately from the application, and associating it with the application as a dependency, means that the resource is checked before the application is enabled. However, as the resource is not managed together with the application, it does not need to be changed when you update the application.
  4. Use CICS Explorer to create an application bundle that packages the CICS bundle, or bundles, containing the LIBRARY and PROGRAM resource definitions and the application entry point declaration for the application. Then create an application binding to deploy the CICS bundles for the application to the region types in the platform. For a scenario example of the process to package an application for deployment on a platform, see Scenario: Deploying an application to a platform. For the full process to package an application for deployment on a platform, see Packaging applications for deployment.
  5. Use CICS Explorer to export the application and application binding to the platform home directory on z/OS UNIX, and create an application definition during the export process. Then install and enable the original version of the application on your platform. Check that the application was installed correctly, then make it available. You can use the instructions in the scenario topic Deploying the new version of the application also to deploy the original version of the application. For the full process to install and enable an application on a platform and make it available, see Installing an application on a platform.
  6. Verify that the original version of the application runs as expected. In a CICS terminal, enter the name of the transaction that you created for the application, and confirm the output from the application.


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