Chapter 14: IMS Installation Verification

This chapter takes you step by step through the process of configuring an enterprise server to run IMS applications, and then building and running an IMS application. This is intended both as an introduction to using IMS in Mainframe Transaction Option (MTO), and as an Installation Verification Procedure (IVP) to confirm that the IMS support is correctly installed.

IVP Overview

The IVP is based around a demonstration program called Mfdemo, which is installed into $COBDIR/demo/MTO-IMS/IVP by default. Mfdemo is a system for capturing and maintaining table data. The tables are organized by table element within table name. The tables eliminate the program maintenance associated with traditional Data Division tables. The following source members are used by this application:

Before Running the IVP

This section describes the steps you need to perform before you can run the IVP. These steps are split into three sections:

Preparing the IVP

Although the Mfdemo application is supplied with Server Express, you need to perform a number of operations on the source files before you can run it. These operations are:

These operations are defined in the following sections.

Compiling the COBOL Programs

To compile the COBOL programs that comprise the Mfdemo application:

  1. In a command prompt, navigate to the folder containing Mfdemo's source files.
  2. Enter the following commands:
    cobol demo001b dialect(vsc24) noflag anim noobj charset(ascii) outdd"sysout 121 r e";
    cobol cdlidemo dialect(mf) osvs cicsecm noflag charset(ascii) anim noobj;
    cobol execdemo dialect(mf) cicsecm execdli noflag charset(ascii) anim noobj;
    cobol demo001t dialect(vsc24) noflag charset(ascii) anim noobj;
    cobol rghtjust dialect(mf) charset(ascii) anim noobj;
    

This creates an intermediate code (.int) and dictionary (.idy) file for each COBOL program.

Generating the MFSs

Mfdemo includes three MFS files (demo90.mfs, demo91.mfs and demo92.mfs) that you need to generate. To generate theses MFSs:

  1. Enter the following command :
    mfims mfsgen demo90.mfs nocls
    mfims mfsgen demo91.mfs nocls
    mfims mfsgen demo92.mfs nocls

Note: Because you are generating all of the MFSs in the current folder you could have used the Windows for command to simplify this operation:

for %i in (*.mfs) do mfims mfsgen %i nocls

In addition to the .mid, .mod, .dif and .dof files, generating the MFSs produces imsconfg.dat and imsconfg.idx. These files contain system configuration data and must not be edited, moved or deleted.

Generating the DBD

Mfdemo includes one DBD file (demo03dd.dbd) that you need to generate. To generate the DBD:

  1. Enter the following command:
    mfims dbdgen demo03dd.dbd nocls echo(enderr,0,50)

Creating the DBD gens produces the following files:

Note: If dbdgen2.dat does not exist when you generate a DBD you see message DBDUT0U35U ("File not found DBDGEN2.DAT"). This message is for information only, and dbdgen2.dat is created.

These files contain DBD source information that has been extracted and formatted into a smaller structure optimized for faster access during execution. These files are indexed files and can contain information for one or more generated DBD members. Do not edit, move or delete these files.

Generating the PSB

Once you have generated the DBD you need to generate the PSB. To generate Mfdemo's single PSB file (demo001t.psb):

  1. Enter the following command:
    mfims psbgen demo001t.psb nocls echo(enderr,0,50)

Generating the PSB produces the following file:

Note: If psbgen3.dat does not exist when you generate a PSB you see message DBDUT0U35U ("File not found PSBGEN3.DAT"). This message is for information only, and psbgen3.dat is created.

These files contain PSB source information that has been extracted and formatted into a smaller structure optimized for faster access during execution. These files are indexed files and can contain one or more generated PSB members. Do not edit, move or delete these files.

Loading the Database

Next you need to load the databases that Mfdemo uses.

  1. Enter the following command:
    mfims imsdbu load demo03dd nocls

Updating the Resource Definition File

IMS support includes two new transactions, /CIC and /IMS, that you use to switch enterprise servers to CICS and IMS modes respectively. In order for these new transactions to be available you need to update your resource definition file using the caspcupg command as follows:

caspcupg

See the section Adding IMS-specific Resource Definitions in the chapter Configuring MTO-enabled Enterprise Servers for IMS in your Mainframe Transaction Option Configuration and Administration Guide for more information on the caspcupg command.

Configuring an Enterprise Server for the IVP

To enable IMS support in an enterprise server, you need to:

  1. Create an MTO-enabled enterprise server.
  2. Enable IMS for the enterprise server.
  3. Enable JCL for the enterprise server.
  4. Specify the location of files produced by gens.
  5. Specify the system initialization table (SIT) to use.
  6. Define a message processing region.

The sections below walk you through these tasks.

Creating an MTO-enabled Enterprise Server

To create an MTO-enabled enterprise server:

  1. On the Home page of Enterprise Server Administration, click Add at the bottom of the table of servers.
  2. On the first Add Server page:
    1. Type IMSIVP in Server Name.
    2. Click Micro Focus Enterprise Server with Mainframe Transaction Option
    3. Click Next.
  3. On the second Add Server page:
    1. In the Creation Options group, check Create TN3270 listener, specify a port number in using port and ensure Create ISC listener is not checked.
    2. Type Server for IMS IVP in Description.
    3. Click Add.
  4. The Home page is redisplayed, and a row for the IMSIVP enterprise server is shown in the table of servers.

Enabling IMS for an Enterprise Server

To enable IMS support for the IMSIVP enterprise server:

  1. Click Edit next to the IMSIVP row in the table of servers.
  2. The Edit page that appears contains a hierarchy of tabs. Click the Server, Properties, MTO, IMS and General tabs.
  3. Ensure that Mainframe Transaction Option enabled is checked, then check IMS enabled.

    This specifies that the IMSIVP enterprise server can use the IMS support. Don't click Apply yet as there is more to do on this page.

Specifying the Location of Required Files

You need to specify the directory where the files produced by DBDGENs, IMSGENs, MFSGENs and PSBGENs are created, and where the application and database files are located.

  1. In the GEN file directory field, specify the name of the folder containing the Mfdemo application files. By default this is $COBDIR/demo/MTO-IMS/IVP.
  2. Click Apply.
  3. Click the Server, Properties, MTO, IMS, TM and General tabs.
  4. In the MFS path field, specify the name of the folder containing the Mfdemo application files.
  5. Enter the same information in the Application Path and the Transaction definition file directory fields.
  6. Click Apply to save the change.
  7. Click the Server, Properties, MTO, IMS, and DB tabs.
  8. In the Database path field, specify the name of the folder containing the Mfdemo application files.
  9. Click Apply to save the change.

Enabling JCL for an Enterprise Server

JCL support is required for any IMS-enabled enterprise server that needs a message processing region to start whenever the enterprise server starts. You will define such a message processing region later, so you need to enable JCL support for IMSIVP.

To enable JCL support for the IMSIVP enterprise server:

  1. Click the Server, Properties, MTO, JES and General tabs.
  2. Check Job Entry Subsystem enabled.
  3. Click Apply.

Specifying the SIT

You have now created the IMSIVP enterprise server and enabled it to use IMS and JCL, but you now need to specify that it uses a CICS SIT. You need to specify a SIT even though Mfdemo does not contain any CICS for two reasons:

To specify that the IMSIVP enterprise server uses the supplied SIT IMSSIT:

  1. Click the Server, Properties, MTO and CICS tabs.
  2. Specify IMSSIT in System Initialization Table. Leave the other fields blank as Mfdemo doesn't use CICS.
  3. Click Apply to save your change.
  4. Click Home to return to the Home page of Enterprise Server Administration.

Defining an Automatic Message Processing Region

To run an IMS application in an enterprise server you need at least one specialized service execution process (SEP) called a message processing region (MPR). To specify that a message processing region starts each time an enterprise server starts you need to in a resource group that is specified by the startup list in the SIT used by the enterprise server.

In the section Specifying the SIT you specified that the IMSIVP enterprise server uses IMSSIT. IMSSIT specifies the IMSSTRT startup list, and the IMSSTRT startup list specifies the IMSGRP resource group, so you can add the MPR definition to IMSGRP. You use ESMAC to add the MPR definition to IMSGRP. ESMAC is only available when the enterprise server is running, so first you must start the IMSIVP enterprise server.

  1. In the table of servers on the Home page of Enterprise Server Administration, click Start in IMSIVP's Current Status column. The value in Current Status changes to "Starting" and if you have Show local console checked on the Edit Server page, the enterprise server console daemon window appears indicating the progress of the process of starting the server.
  2. After starting IMSIVP, wait a few seconds and then click the Refresh button on the Enterprise Server Administration Home page. Do this repeatedly until the Current Status column shows Started.
  3. In the Current Status column of the entry for IMSIVP, click Details.
  4. The Details page that appears contains a hierarchy of tabs. Make sure the Server and Control tabs are selected, and click ES Monitor & Control.
  5. In the dropdown list under Resources on the ESMAC menu, select by Group
  6. Click Groups, then click Details on the row for IMSGRP.
  7. Click JES.
  8. Specify the following values in the fields:
    Field Value
    NameIMSMPR
    DescriptionMPR
    Type IMS MPR
    Classes 001
  9. Click Add.
  10. Click Group List.
  11. Click Home to return to the Home page of Enterprise Server Administration.

Restarting the Enterprise Server

To make the enterprise server pick up the configuration changes you made in ESMAC you have to stop it and restart it.

  1. In the table of servers on the Home page of Enterprise Server Administration, click Stop in IMSIVP's Current Status column.
  2. Click OK to confirm that you want to stop it.
  3. After a few seconds click Refresh on the Home page. The value in Current Status changes to "Stopped".
  4. In the table of servers on the Home page of Enterprise Server Administration, click Start in IMSIVP's Current Status column.
  5. You can confirm that MTO and IMS are enabled by watching the startup messages in the Console Daemon window. Messages should also appear indicating that the message processing region has started.

Running the IVP

To start the demonstration application:

  1. Start a TN3270 emulator.
  2. Specify the following connection information. Note that field names could vary depending on the 3270 emulator you are using.
    Field Value
    Host name The name of the computer the enterprise server is running on. This is localhost if it is the current machine.
    Port The number you specified for the field using port in the section Creating an MTO-enabled Enterprise Server.
  3. Connect.
  4. Specify a user id and password, then press Enter. If you have not configured Enterprise Server security you can use the user SYSAD with password SYSAD.
  5. Press Clear (3270 key).
  6. Enter MFDEMO (with a trailing space).

The following sections describe the demonstration program and how you navigate through its screens.

Mfdemo Screen Entries

For the screens which follow, enter the characters which are shown in green.

Note: Each table you add must have a unique table ID.

The "Add Testdept Table" Screen in Transaction MFDEMO

Figure 14-1: The "Add Testdept Table" Screen in Transaction MFDEMO

Press Enter when you have finished entering data on a screen.

On the screens that follow press Tab to move to the next field. Press Shift+Tab to move to the previous field.

The "Add Testdept Elements" Screen

Figure 14-2: The "Add Testdept Elements" Screen

The "Change Testdept Table" Screen

Figure 14-3: The "Change Testdept Table" Screen

The "Change Testdept Elements" Screen

Figure 14-4: The "Change Testdept Elements" Screen

The "Add Testers Table" Screen

Figure 14-5: The "Add Testers Table" Screen

The "Add Testers Elements" Screen

Figure 14-6: The "Add Testers Elements" Screen

The "End Transaction" Screen

Figure 14-7: The "End Transaction" Screen

The "MFDEMO - ENDED" Screen

Figure 14-8: The "MFDEMO - ENDED" Screen


Copyright © 2006 Micro Focus (IP) Ltd. All rights reserved.