Installing and setting up the base application

Edit online

Before you can run the base application you must define and populate two VSAM data sets, and install two transaction definitions.

Creating and defining the VSAM data sets

Edit online

The example application uses two KSDS VSAM data sets to be defined and populated. One data set contains configuration information for the example application. The other contains the sales catalog.

Procedure

  1. Locate the JCL to create the VSAM data sets.

    During CICS installation, the JCL is placed in the hlq.SDFHSAMP library:
    • Member DFH$ECNF contains the JCL to generate the configuration data set.
    • Member DFH$ECAT contains the JCL to generate the catalog data set.
  2. Modify the JCL and access method services commands.
    1. Supply a valid JOB card.
    2. Supply a suitable high level qualifier for the data set names in the access method services commands.
      As supplied, the JCL uses a high level qualifier of HLQ.
      The following command defines the catalog file:
      DEFINE CLUSTER (NAME(hlq.EXMPLAPP.catname)-
       TRK(1 1) -
       KEYS(4 0) -
       RECORDSIZE(80,80) -
       SHAREOPTIONS(2 3) -
       INDEXED -
       ) -
       DATA (NAME(hlq.EXMPLAPP.catname.DATA) -
       ) -
       INDEX (NAME(hlq.EXMPLAPP.catname.INDEX) -
       )
      where
      • hlq is a high level qualifier of your choice
      • catname is a name of your choice. The name used in the example application as supplied is EXMPCAT.
      The following command defines the configuration file:
      DEFINE CLUSTER (NAME(hlq.EXMPLAPP.EXMPCONF)-
          TRK(1 1) -
          KEYS(9 0) -
          RECORDSIZE(350,350) -
          SHAREOPTIONS(2 3) -
          INDEXED -
          ) -
          DATA (NAME(hlq.EXMPLAPP.EXMPCONF.DATA) -
          ) -
          INDEX (NAME(hlq.EXMPLAPP.EXMPCONF.INDEX) -
          )
      where hlq is a high level qualifier of your choice.
  3. Run both jobs to create and populate the data sets.
  4. Use the CEDA transaction to create a FILE definition for the catalog file.
    1. Enter the following: CEDA DEF FILE(EXMPCAT)G(EXAMPLE).
      Alternatively, you can copy the FILE definition from CICS supplied group DFH$EXBS.
    2. Enter the following additional attributes:
      • DSNAME(hlq.EXMPLAPP.EXMPCAT)
      • ADD(YES)
      • BROWSE(YES)
      • DELETE(YES)
      • READ(YES)
      • UPDATE(YES)
    3. Use the default values for all other attributes.
  5. Use the CEDA transaction to create a FILE definition for the configuration file.
    1. Enter the following: CEDA DEF FILE(EXMPCONF) G(EXAMPLE).
      Alternatively, you can copy the FILE definition from CICS supplied group DFH$EXBS.
    2. Enter the following additional attributes:
      • DSNAME(hlq.EXMPLAPP.EXMPCONF)
      • ADD(YES)
      • BROWSE(YES)
      • DELETE(YES)
      • READ(YES)
      • UPDATE(YES)
    3. Use the default values for all other attributes.

Defining the 3270 interface

Edit online

The example application is supplied with a 3270 user interface to run the application and to customize it. The user interface consists of two transactions, EGUI and ECFG.

Procedure

Use the CEDA transaction to create TRANSACTION definitions for both transactions.
  1. To define transaction EGUI, enter the following: CEDA DEF TRANS (EGUI) G(EXAMPLE) PROG(DFH0XGUI).
  2. To define transaction ECFG, enter the following: CEDA DEF TRANS (ECFG) G(EXAMPLE) PROG(DFH0XCFG)

Use the default values for all other attributes.
Note: The correct operation of the example application does not depend on the names of the transactions, so you can use different names if you wish.
Alternatively, you can copy the TRANSACTION definitions from CICS supplied group DFH$EXBS.

Completing the installation

Edit online

To complete the installation, install the RDO group that contains your resource definitions.

Procedure

Enter the following command at a CICS terminal: CEDA I G(EXAMPLE).

Results

The application is now ready for use.